|
|
|
|
| # **O-RAN O2 Interface General Aspects and Principles** --- |
|
|
| **This is a re-published version of the attached final specification.** |
|
|
| For this re-published version, the prior versions of the IPR Policy will apply, except that the previous requirement for Adopters (as defined in the earlier IPR Policy) to agree to an O-RAN Adopter License Agreement to access and use Final Specifications shall no longer apply or be required for these Final Specifications after 1st July 2022. |
|
|
| 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 on this site for your personal use, or copy the material on this site 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 O2 Interface General Aspects and Principles** --- |
|
|
| Copyright © 2022 by the O-RAN ALLIANCE e.V. |
|
|
| By using, accessing or downloading any part of this O-RAN specification document, including by copying, saving, distributing, displaying or preparing derivatives of, you agree to be and are bound to the terms of the O-RAN Adopter License Agreement contained in the Annex ZZZ of this specification. All other rights reserved. |
|
|
| O-RAN ALLIANCE e.V. |
| Buschkauler Weg 27, 53347 Alfter, Germany |
| Register of Associations, Bonn VR 11238 |
| VAT ID DE321720189 |
|
|
| 1 |
|
|
| # Revision History |
|
|
| | Date | Revision | Author | Description | |
| |------------|----------|--------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------| |
| | 2020.05.29 | 00.01.00 | Joey Moloney (Ericsson)<br>David Kinsey (AT&T)<br>Raghavendra Mahalingappa (Ericsson)<br>Torbjorn Keisu (Ericsson) | Baseline version of General Aspects and Principles Specification<br><br>Content added to Sections 2.1, 3.1, & 3.2 | |
| | 2020.07.03 | 00.01.01 | Joey Moloney (Ericsson)<br>Raghavendra Mahalingappa (Ericsson) | O2 Introduction added to 2.1 and ETSI information added to 2.5 | |
| | 2020.07.03 | 00.01.02 | Joey Moloney (Ericsson)<br>Raghavendra Mahalingappa (Ericsson)<br>David Kinsey (AT&T) | O-Cloud Monitoring Service content added to 3.3 | |
| | 2020.07.03 | 00.01.03 | Joey Moloney (Ericsson)<br>Raghavendra Mahalingappa (Ericsson)<br>David Kinsey (AT&T) | O-Cloud Provisioning content added to 3.4 | |
| | 2020.07.03 | 00.01.04 | Joey Moloney (Ericsson)<br>Raghavendra Mahalingappa (Ericsson) | O-Cloud Software Management content added to 3.5 | |
| | 2020.07.03 | 00.01.05 | Joey Moloney (Ericsson)<br>Raghavendra Mahalingappa (Ericsson)<br>Udi Schwager (Wind River) | O-Cloud LCM content added to 3.6 | |
| | 2020.07.03 | 00.01.06 | Joey Moloney (Ericsson)<br>Raghavendra Mahalingappa (Ericsson) | O-Cloud Deployment LCM content added to 3.7 | |
| | 2020.07.07 | 00.01.07 | David Kinsey (AT&T) | Deployment definition added to 1.3.1 | |
| | 2020.07.10 | 00.01.08 | Joey Moloney (Ericsson) | Updated based on review comments | |
| | 2020.07.17 | 00.01.09 | Joey Moloney (Ericsson) | Updated based on further review comments | |
| | 2020.07.29 | 01.00.00 | Joey Moloney (Ericsson)<br>Lucian Suci (Orange) | Approved version for publication | |
| | 2021.06.22 | 01.00.01 | Joey Moloney (Ericsson) | Fault concepts content added to 3.5.2 | |
| | 2021.06.22 | 01.00.02 | Joey Moloney (Ericsson) | DMS clarification content added to 2.2.1 and Annex A (Informative): O-Cloud and IMS Initialization | |
| | 2021.07.02 | 01.00.03 | Joey Moloney (Ericsson) | Updated to align with 3GPP specification and to include comments received | |
| | 2021.07.05 | 01.00.04 | Joey Moloney (Ericsson) | Correction to the incorrect statement about the smallest resource | |
|
|
| | | | | | |
| |------------|----------|-------------------------|-------------------------------------------------------------------| |
| | 2021.11.15 | 01.01.01 | Joey Moloney (Ericsson) | DMS Principles content updated in 3.7 and sub-section 3.7.2 added | |
| | 2021.11.15 | 01.01.02 | Joey Moloney (Ericsson) | Performance concepts content added to 3.5.3 | |
| | 2021.11.15 | 01.01.03 | Joey Moloney (Ericsson) | O-Cloud Provisioning concepts added to 3.4.3 | |
|
|
| # Table of Contents |
|
|
| | | | | |
| |----|-------------------------------------------------------------------------|----| |
| | 1 | Revision History..... | 2 | |
| | 2 | Chapter 1. Introduction..... | 7 | |
| | 3 | 1.1 Scope ..... | 7 | |
| | 4 | 1.2 References..... | 7 | |
| | 5 | 1.3 Definitions and Abbreviations ..... | 8 | |
| | 6 | 1.3.1 Definitions..... | 8 | |
| | 7 | 1.3.2 Abbreviations ..... | 8 | |
| | 8 | Chapter 2. General Aspects ..... | 10 | |
| | 9 | 2.1 Introduction to O2..... | 10 | |
| | 10 | 2.2 Alignment with O-RAN Architecture..... | 10 | |
| | 11 | 2.2.1 Alignment with Overall Architecture ..... | 10 | |
| | 12 | 2.2.2 Alignment with OAM Architecture ..... | 12 | |
| | 13 | 2.3 Technology Independence ..... | 12 | |
| | 14 | 2.4 General Requirements..... | 12 | |
| | 15 | 2.5 Relationship with Existing Standards and Open Source Solutions..... | 12 | |
| | 16 | 2.5.1 ETSI NFV ..... | 13 | |
| | 17 | 2.5.2 IETF ..... | 14 | |
| | 18 | 2.5.3 3GPP ..... | 14 | |
| | 19 | 2.5.4 Kubernetes ..... | 14 | |
| | 20 | 2.5.5 OpenStack ..... | 14 | |
| | 21 | 2.5.6 ONAP/OSM ..... | 14 | |
| | 22 | Chapter 3. O2 Interface General Principles..... | 15 | |
| | 23 | 3.1 O-Clouds..... | 15 | |
| | 24 | 3.2 O-Cloud Inventory..... | 16 | |
| | 25 | 3.2.1 Infrastructure Inventory..... | 16 | |
| | 26 | 3.2.2 Logical Inventory ..... | 16 | |
| | 27 | 3.2.3 Deployment Inventory..... | 17 | |
| | 28 | 3.3 O-Cloud Monitoring Service ..... | 17 | |
| | 29 | 3.3.1 General Capabilities ..... | 18 | |
| | 30 | 3.4 O-Cloud Provisioning ..... | 19 | |
| | 31 | 3.4.1 Affinity, Anti-Affinity, Quorum Diversity Rules..... | 19 | |
| | 32 | 3.4.2 O-Cloud Capacity and Availability ..... | 20 | |
| | 33 | 3.4.3 O-Cloud Provisioning Basic Concepts..... | 20 | |
| | 34 | 3.5 O-Cloud Software Management ..... | 26 | |
| | 35 | 3.5.1 General Capabilities ..... | 27 | |
| | 36 | 3.5.2 O-Cloud Fault Management Concepts ..... | 27 | |
| | 37 | 3.5.3 O-Cloud Performance Basic Concepts..... | 31 | |
| | 38 | 3.6 O-Cloud Life Cycle Management..... | 33 | |
| | 39 | 3.7 O-Cloud Deployment Life Cycle Management ..... | 34 | |
| | 40 | 3.7.1 General Capabilities ..... | 35 | |
| | 41 | 3.7.2 Deployment Management Services..... | 35 | |
| | 42 | Annex A (Informative): O-Cloud and IMS Initialization..... | 36 | |
| | 43 | UML sequence diagram for O-Cloud and IMS initialization ..... | 36 | |
| | 44 | Annex ZZZ O-RAN Adopter License Agreement..... | 37 | |
| | 45 | Section 1: DEFINITIONS ..... | 38 | |
| | 46 | Section 2: COPYRIGHT LICENSE..... | 38 | |
| | 47 | Section 3: FRAND LICENSE..... | 38 | |
| | 48 | Section 4: TERM AND TERMINATION ..... | 39 | |
| | 49 | Section 5: CONFIDENTIALITY ..... | 39 | |
| | 50 | Section 6: INDEMNIFICATION ..... | 39 | |
| | 51 | Section 7: LIMITATIONS ON LIABILITY; NO WARRANTY ..... | 39 | |
| | 52 | Section 8: ASSIGNMENT ..... | 40 | |
| | 53 | Section 9: THIRD-PARTY BENEFICIARY RIGHTS ..... | 40 | |
| | 54 | Section 10: BINDING ON AFFILIATES ..... | 40 | |
| | 55 | | | |
|
|
| | | | | |
| |---|---------------------------|----| |
| | 1 | Section 11: GENERAL ..... | 40 | |
| | 2 | | | |
|
|
| # Table of Figures |
|
|
| | | | | |
| |----|---------------------------------------------------------------------------|----| |
| | 1 | | | |
| | 2 | Figure 2.2-1 O-Cloud IMS and DMS Relationships to SMO ..... | 10 | |
| | 3 | Figure 2.2-2 O2 RP Service Based-Interfaces ..... | 11 | |
| | 4 | Figure 3.1-1 O-Cloud Planes ..... | 15 | |
| | 5 | Figure 3.2-1 O-Cloud Infrastructure Inventory..... | 16 | |
| | 6 | Figure 3.2-2 Logical Clouds ..... | 17 | |
| | 7 | Figure 3.3-1 Telemetry Types ..... | 18 | |
| | 8 | Figure 3.4-1 Diagram of kinds of Resources and examples of Resources..... | 21 | |
| | 9 | Figure 3.5-1 Parallel Reporting & Alarm Correlation ..... | 30 | |
| | 10 | Figure 3.5-2 Concept of Fault Domains ..... | 31 | |
| | 11 | Figure 3.7-1 O2 Deployment LCM Services ..... | 35 | |
| | 12 | | | |
|
|
| # Chapter 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 OAM 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 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. |
| - 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. |
|
|
| - [1] 3GPP TR 21.905: “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Vocabulary for 3GPP Specifications” |
| - [2] O-RAN Architecture Description Version 2.0 |
| - [3] O-RAN Operations and Maintenance Architecture Version 3.0 |
| - [4] O-RAN Operations and Maintenance Interface Version 3.0 |
| - [5] O-RAN Cloud Architecture and Deployment Scenarios for O-RAN Virtualized RAN Version 2.1 |
| - [6] ONAP VES Event Listener Specification version 7.2 – May 2020 |
| - [7] RFC 6241, “Network Configuration Protocol (NETCONF)”, IETF, June 2011 |
| - [8] RFC 7950, “The YANG 1.1 Data Modeling Language”, IETF, August 2016 |
| - [9] SP 800-145, "The NIST Definition of Cloud Computing", NIST, September 2011 |
| - [10] 3GPP TS 29.501 "5G System; Principles and Guidelines for Services Definition; Stage 3 (Release 16)", September 2020 |
| - [11] ETSI GS NFV-SOL 013 v3.3.1 "Protocols and Data Models; Specification of common aspects for RESTful NFV MANO APIs", September 2020 |
| - [12] ETSI GS NFV-SOL 015 v1.1.1 "Protocols and Data Models; Specification of Patterns and Conventions for RESTful NFV-MANO APIs", January 2020 |
|
|
| - [13] O-RAN Orchestration Use Cases and Requirements for O-RAN Virtualized RAN Version 2.1 |
| - [14] 3GPP TS28.550 Management and orchestration; Performance assurance Version 17 |
| - [15] 3GPP TS28.531 Management and orchestration; Provisioning Version 17 |
| - [16] ETSI SOL003 Zero-touch network and Service Management (ZSM); End-to-end management and orchestration of network slicing |
|
|
| ## 1.3 Definitions and Abbreviations |
|
|
| ### 1.3.1 Definitions |
|
|
| - 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. |
| - NF Deployment Descriptor:** A completed data model which provides an O-Cloud the necessary information to create a deployment. |
| - 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. |
| - 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. |
|
|
| ### 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]. |
|
|
| | | | |
| |---------|---------------------------------------------------------| |
| | FCAPS | Fault, Configuration, Accounting, Performance, Security | |
| | HATEOAS | Hypermedia as the Engine of Application State | |
| | MANO | Management and Orchestration | |
| | MnS | Management Service | |
| | MOC | Managed Object Class | |
| | MOI | Managed Object Instance | |
| | O-RAN | Open Radio Access Network | |
| | ONAP | Open Network Automation Platform | |
|
|
| | | | | |
| |---|-----|--------------------------------------| |
| | 1 | OSM | Open Source Mano | |
| | 2 | RAN | Radio Access Network | |
| | 3 | TR | Technical Report | |
| | 4 | TS | Technical Specification | |
| | 5 | SMO | Service Management and Orchestration | |
|
|
| # Chapter 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. |
|
|
| #### O-Cloud IMS & DMS relationships to SMO |
|
|
|  |
|
|
| Diagram illustrating O-Cloud IMS & DMS relationships to SMO. The SMO (Service Management & Orchestration) is at the top, containing NFO and FOCOM. NFO connects to multiple DMS (Deployment Management Services) and IMS (Integration Management Services) within the O-Cloud. FOCOM connects to DMS and IMS. The O-Cloud is divided into two main sections: 'O-Cloud' (left) and 'O-Cloud' (right). The left section shows DMS instances with 'Resource Lease' blocks, connected to 'IMS owned and managed' resources, which are further divided into 'Resource Pools' (e.g., Resource Pool 1 @ Location X, Resource Pool 2 @ Location Y, Resource Pool 3 @ Location Z, Resource Pool n @ Location Z) and 'Physical Resources'. The right section shows a single DMS instance connected to an IMS, which is also connected to 'Physical Resources'. |
|
|
| **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. |
|
|
|  |
|
|
| Figure 2.2-2 O2 RP Service Based-Interfaces diagram. The diagram shows the Service Provider Functionality (SMO) separated from the O-Cloud by a dashed line representing the O2 interface. The SMO contains three main components: Federated O-Cloud Orchestration and Management (FOCOM), Network Function Orchestrator (NFO), and OAM Function. The O-Cloud contains two main components: Infrastructure Management Services (IMS) and Deployment Management Services (DMS). The O2 interface is split into two parts: O2ims (connecting FOCOM to IMS) and O2dms (connecting NFO and OAM Function to DMS). A yellow callout box points to the dashed line with the text 'Separation of Concerns boundary'. |
|
|
| **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 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. |
| - **OAM Functions:** The OAM Functions are responsible for FCAPS management of O-RAN managed entities. In the context of O2 they may be one of the functional blocks for which a callback is provided in order to receive faults and/or performance data from a subscription for O2ims or O2dms procedures. |
|
|
| - **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 superceded in the O2 Specification as the interface evolves. |
|
|
| | 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 Specification: |
|
|
| - SOL004 standard is used for VNF and PNF packages |
| - SOL007 standard is used for NS package |
| - SOL001 standard is used to describe VNF, PNF, and NS in TOSCA |
| - SOL003 standard is used for VNF Package Management, LCM and Monitoring |
| - SOL005 standard is used for NS/PNF/VNF Package Management, LCM and Monitoring |
| - SOL006 standard is used to describe VNF, PNF, and NS in YANG |
| - SOL002 standard is used for VNF/VNFC-level EM triggered scenarios (LCM, Fault, Performance, Configuration) |
| - ETSI Package and communication security are supported / API security are supported (SEC022 GS) |
| - IFA 029 Enhancements of the NFV architecture towards "Cloud-native" and "PaaS" |
| - IFA040 CISM OS container compute management service interface requirements (ongoing) |
| - ETSI IFA 005/006 covers topics Software Image Management, Virtual Resource Management (Information, Quota, Capacity, Change Notification, and Reservation) Virtual Resource Performance Management, Virtual Resource Fault Management and NFP |
|
|
| The O2 interfaces will generally follow ETSI GS NFV-SOL 013 [11] section 8 for interface security. Further refinements will be based on recommendations from the STG and are FFS. |
|
|
| Other sections of SOL 13 [11] are still under review and are therefore FFS. |
|
|
| 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. |
|
|
| #### 1 2.5.2 IETF |
|
|
| 2 For Future Study. |
|
|
| #### 3 2.5.3 3GPP |
|
|
| 4 The O2 interface is composed of services provided by the SMO and service provided by the O-Cloud. This closely |
| 5 resemble the Reference Points and Service Based Interface (SBI) definitions described in 3GPP TS 29.501[10]. Therefore, |
| 6 this specification follows the intent of the practices defined in [10] but has modified it from its intended 5G Core |
| 7 implementation to align with the O-RAN O2 interface. |
|
|
| #### 8 2.5.4 Kubernetes |
|
|
| 9 For Future Study. |
|
|
| #### 10 2.5.5 OpenStack |
|
|
| 11 For Future Study. |
|
|
| #### 12 2.5.6 ONAP/OSM |
|
|
| 13 For Future Study. |
|
|
| # Chapter 3. O2 Interface General Principles |
|
|
| This section describes the general approach to solving common problems with managing a cloud and the deployments which execute on it. |
|
|
| ## 3.1 O-Clouds |
|
|
| O-RAN clouds are described in [5] as a distributed cloud composed of O-Cloud [Resource] Pools (as shown as white clouds in the diagram below) where each pool is a collection of O-Cloud Nodes at a specific location. An O-Cloud Node is the basic computational resource designator and can be commonly thought of as a server. 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 into resources which are assigned for a specific use by the O-Cloud Management Software according to a blueprint. As a general concept the cloud is divided into three planes, however the control and management plane described below may be merged or use common tools and therefore may act as or be one plane. |
|
|
| - Management Plane: O-Cloud Nodes in this plane host the software which is responsible for managing the O-Cloud |
| - Control Plane: O-Cloud Nodes in this plane are responsible for hosting the software which manages the resources assigned in the deployment plane to specific deployment instances |
| - Deployment Plane: O-Cloud Nodes in this plane are used to host "Service Model" Deployments |
|
|
|  |
|
|
| The diagram illustrates the O-Cloud architecture across three planes: Management Plane (top, green), Control Plane (middle, yellow), and Deployment Plane (bottom, orange). The background shows a world map. Various implementation types are indicated by blue callout boxes with arrows pointing to specific server stacks (O-Cloud Nodes): |
|
|
| - Medium Regional Implementations:** Points to a server stack in the Management Plane. |
| - Dedicated to a Plane:** Points to a server stack in the Control Plane. |
| - Shared Across Planes:** Points to a large stack of servers spanning the Control and Deployment Planes. |
| - Small Edge Implementations:** Points to a server stack in the Deployment Plane. |
| - Large Central Implementations:** Points to a large stack of servers in the Deployment Plane. |
| - Distributed Geography:** Points to a server stack in the Deployment Plane. |
|
|
| Diagram of O-Cloud Planes showing three stacked layers: Management Plane (green), Control Plane (yellow), and Deployment Plane (orange). The diagram illustrates various implementation types: Medium Regional Implementations, Dedicated to a Plane, Shared Across Planes, Small Edge Implementations, Large Central Implementations, and Distributed Geography. Each plane contains server icons representing O-Cloud Nodes. |
|
|
| Figure 3.1-1 O-Cloud Planes |
|
|
| ## 3.2 O-Cloud Inventory |
|
|
| From the perspective of the SMO, O-Cloud Inventory consists of the physical infrastructure used to create the O-Cloud, the logical clouds which it provides as interfaces for deployments, and the inventory of deployments using the logical cloud. The SMO is responsible for financial accounting of physical 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. |
|
|
| ### 3.2.1 Infrastructure Inventory |
|
|
| Infrastructure inventory is passed between the SMO and the O-Cloud over the O2ims. An O-Cloud Node 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. The O-Cloud Node Identifier must be immutable. |
|
|
| The IMS will add O-Cloud Nodes to the relevant O-Cloud Resource Pools when they are powered on and ready to be provisioned as a resource. The IMS then allocates them to a plane according to its policies and sends the O-Cloud Node characteristics to the SMO. |
|
|
| The SMO receives O-Cloud Node startup events and updates its inventory accordingly. The O-Cloud Node Identifier is matched with invoice data in order to provide financial asset tracking requirements. 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. The diagram shows a hierarchical structure. At the top is a light blue box labeled 'Service Provider Functionality' containing a darker blue box labeled 'FOCOM'. Below this is a dashed horizontal line. Underneath the dashed line are three green boxes, each labeled 'Cloud Provider Functionality'. Inside each green box is a smaller dark green box labeled 'O2 Cloud Provider Infrastructure Management Services'. Above each green box, the text 'O2ims' is written with a vertical line connecting it to the box. To the left of the first green box, an orange arrow points upwards, labeled 'Physical/Logical Inventory'. To the right of the last green box, an orange arrow points downwards, labeled 'Maintenance Schedules'. |
|
|
| Figure 3.2-1 O-Cloud Infrastructure Inventory |
|
|
| ### 3.2.2 Logical Inventory |
|
|
| The SMO will need to know the composition of an ME in terms of its MFs as described in the O-RAN OAM Architecture [3]. This cannot be derived from the deployments and therefore is not addressed by the O2 interface. This data should be contained in the ME configuration and should be collected over the O1 interface [4]. |
|
|
| The O-Cloud itself must have one or more DMS available within its distributed footprint. These could be based on virtual technologies (Kubernetes/Docker, Open Stack, etc.) used, and/or O-Cloud pool locations. Each DMS endpoint provides an O2dms interface and is inventoried by the SMO as a logical cloud. The logical cloud is used by the SMO in order to select the O-Cloud to be used for a deployment during the cloud selection process. |
|
|
|  |
|
|
| Figure 3.2-2 Logical Clouds diagram. The diagram shows a Service Provider Functionality layer at the top, containing an NFO (Network Function Orchestrator) block. Below this is a dashed line representing a 'Separation of Concerns boundary'. Underneath the boundary are two main sections: 'Cloud Provider Functionality' on the left and 'Cloud Provider Functionality' on the right. The left section contains 'O2 OpenStack DMS Plug In' and 'O2 Kubernetes DMS Plug In', with a 'Resource Pool Location' cloud icon below them. The right section contains 'O2 Hybrid Location 2 DMS Plug In' and 'O2 Hybrid Location 3 DMS Plug In', with 'Resource Pool Location 2' and 'Resource Pool Location 3' cloud icons below them. A yellow callout box points to the NFO, stating: '2 O-Cloud Instances with a total of 3 Resource Pools look like 4 logical clouds to the SMO for VNF Homing and NF Orchestration'. Another yellow callout box points to the dashed line, stating: 'Separation of Concerns boundary'. A third yellow callout box points to the 'O2 Hybrid Location 2 DMS Plug In' and 'O2 Hybrid Location 3 DMS Plug In' blocks, stating: 'Plug In end point appears as logical cloud to NFO'. A fourth yellow callout box points to the 'Resource Pool Location 2' and 'Resource Pool Location 3' cloud icons, stating: 'Resource Pool with a global unique location ID'. A fifth yellow callout box points to the 'O2 OpenStack DMS Plug In' and 'O2 Kubernetes DMS Plug In' blocks, stating: 'Homing Policy and Cloud Capabilities match Descriptor types with O2-D endpoint'. A sixth yellow callout box points to the 'Resource Pool Location 2' and 'Resource Pool Location 3' cloud icons, stating: 'Distributed O-Cloud Instance'. |
|
|
| Figure 3.2-2 Logical Clouds |
|
|
| ### 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 |
|
|
| 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 a stack of three layers: Managed Element (top, blue), Deployment (middle, green), and Infrastructure (bottom, yellow). Managed Element contains four 'Deployment' icons (orange circles with gear icons). Deployment contains four server rack icons. Infrastructure contains four server rack icons. Three arrows point left from the layers: 'Managed Element Telemetry' from the top layer, 'Deployment Telemetry' from the middle layer, and 'Infrastructure Telemetry' from the bottom layer. |
|
|
| **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 |
|
|
| 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. The O-Cloud resources are deployed flexibly to match the O-RAN Cloudified Network Function's fluctuating demands. The O-Cloud resources typically scale up to accommodate spikes in usage and scale down when demands decrease. O-Cloud Provisioning offers 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 |
|
|
| Support for the following functionalities are FFS: |
|
|
| - Subscriptions |
| - Flavor Management |
| - Server Group Management |
| - Capabilities Discovery |
| - Switch Fabric Management |
| - Quota Management |
| - Resource Performance Management |
| - Virtual Resource Performance Management |
|
|
| ### 3.4.1 Affinity, Anti-Affinity, Quorum Diversity Rules |
|
|
| 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 server or a server 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 (Server or Server 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 Operations shall be able to apply Affinity, Anti-Affinity, Quorum Diversity rules |
|
|
| 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 |
|
|
| ### 3.4.2 O-Cloud Capacity and Availability |
|
|
| O-Cloud Resources are allocated to a DMS for use and each DMS may have a different distribution of Capacity, and Availability. The Capacity is the number of Resources allocated or reserved to an O-Cloud. The Capacity may be larger than the sum of physical resources due to allowed oversubscription in the O-Cloud. The Availability of an O-Cloud is the Capacity minus the allocated and reserved resources. |
|
|
| #### 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 Availability |
|
|
| ### 3.4.3 O-Cloud Provisioning Basic Concepts |
|
|
| 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 modeling, and information modeling. |
|
|
| 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 |
|
|
| A *resource* is defined in a O-cloud infrastructure as one that may be provisioned and managed through an abstraction. O-Cloud infrastructure have two kinds of resources: physical and logical resources. A physical resource is defined as a kindof resource that has a manifestation in the real world. A logical resource is defined as a kindof 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. |
|
|
|  |
|
|
| Figure 3.4-1 Diagram of kinds of Resources and examples of Resources. The diagram shows three main categories of resources: Managed O-Cloud Service, Logical Resource, and Physical Resource. Each category has a list of examples. Managed O-Cloud Service examples are Boot Service, Upgrade Service, and Management Svc. Logical Resource examples are Container Cluster, OS Cluster, and Underlay Network. Physical Resource examples are Server Hardware, Accelerator HW, and RAN Hardware. The Logical Resource and Physical Resource categories are grouped under '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 |
|
|
| 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 illustrating Resource Views seen as different actor's perspective. A central purple cube labeled 'RESOURCE' is viewed through four magnifying glasses. The top view is labeled 'Workload' (red circle with a robot icon). The left view is labeled 'FOCOM (SMO)' (yellow circle with a robot icon). The right view is labeled 'NFO (SMO)' (blue circle with a robot icon). The bottom view is labeled 'Infrastructure Manager' (green circle with a robot icon). A callout box on the right states: '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 Provider. |
|
|
| Note: The cloud infrastructure manager (green) is often implemented 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 the 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 resources that are requested by an SMO, according to SMO objectives from the pool of Abstracted Resources. When requests are fulfilled, the bookkeeping of Assigned 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 kinds 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 as 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, this can change 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. |
|
|
|  |
|
|
| ``` |
| |
| graph TD |
| subgraph SMO [Service Management Orchestrator (SMO)] |
| FOCOM((FOCOM)) -- Assignments --> NEO((NEO)) |
| end |
| FOCOM -- Objectives --> IMS |
| subgraph IMS_Box [IMS] |
| IMS_Label[IMS] |
| IMS_Text[Provisioning Abstracted resources] |
| AR[Abstracted Resources] |
| RP[Resource Pool] |
| PR[Physical Resource] |
| LR[Logical Resource] |
| MOS[Managed O-Cloud Service] |
| end |
| subgraph DMS_Box [DMS] |
| DMS_Label[DMS] |
| DMS_Text[Prepare, Place, Scale workloads on assigned resources] |
| AR2[Assigned Resources] |
| end |
| RP -- Cluster Creation --> AR2 |
| NEO --> DMS_Label |
| |
| ``` |
|
|
| Figure 3.4-2 Resource Views – Abstracted & Assigned Resources. The diagram illustrates the flow of resource management within the Service Management Orchestrator (SMO). At the top, the SMO contains FOCOM and NEO components. FOCOM sends 'Assignments' to NEO. FOCOM also sends 'Objectives' to the IMS (Integrated Management System). The IMS provisions 'Abstracted Resources' from a 'Resource Pool' containing 'Physical Resource', 'Logical Resource', and 'Managed O-Cloud Service'. These are then sent via 'Cluster Creation' to the DMS (Data Management System), which prepares, places, and scales workloads on the assigned resources. The DMS also receives direct input from NEO. |
|
|
| Figure 3.4-2 Resource Views – Abstracted & Assigned Resources |
|
|
| #### 3.4.3.4 Hardware Layer Concepts |
|
|
| ##### 3.4.3.4.1 Computer System |
|
|
| A Computer System is defined to be a physical or composed system capable of perform computations that is Underlay-Network connected. A Computer System can run any major Operating System with or without Virtualization and/or Container support functionality. See diagram 4: “Hardware Layer Concepts” |
|
|
| 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. |
|
|
|  |
|
|
| Figure 3.4-3 Hardware Layer Concepts diagram. The diagram shows a hierarchical hardware layer structure. At the top is a light blue rounded rectangle labeled 'Computer Systems' with two server icons. Below it is a light yellow rounded rectangle labeled 'Underlay Network' with a network switch icon. A blue line connects the 'Underlay Network' to the 'Computer Systems'. To the right of the 'Underlay Network' is a blue rounded rectangle labeled 'Gateway' with a router icon. A blue line connects the 'Underlay Network' to the 'Gateway'. |
|
|
| Figure 3.4-3 Hardware Layer Concepts |
|
|
| ##### 3.4.3.4.2 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. |
|
|
| #### 3.4.3.5 Execution Environment Layer Concepts |
|
|
| ##### 3.4.3.5.1 Operating System (OS) |
|
|
| An Operating system is 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. |
|
|
| ##### 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. This is Cloud infrastructure internal representation that could be manifested as an O-Cloud Node once exposed over O2ims as an Abstracted Resource. (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.”). |
|
|
| ##### 3.4.3.5.5 Overlay Network |
|
|
| An Overlay Network is a logical network interconnect enabling Compute Nodes to communicate with each other within their Cluster and with the gateway(s) connected to networks outside of the data center. |
|
|
| ##### 3.4.3.5.6 Compute Cluster |
|
|
| A Compute Cluster is a selected set of Computer Systems that are physically interconnected through an Underlay Network and that can be used to setup a Node Cluster (as defined below). |
|
|
|  |
|
|
| Figure 3.4-4 Execution Environment Layer Concepts. The diagram illustrates the execution environment layers. The top layer, 'Compute Cluster', contains two 'Compute Nodes'. Each node consists of an 'OS Instance' (represented by a Linux logo) and 'Computer Systems' (represented by server icons). The bottom layer, 'Overlay Network', is connected to the 'Compute Cluster' and is linked to a 'Physical Underlay' network, which is represented by computer icons. Arrows indicate the flow of data and connectivity between these components. |
|
|
| Figure 3.4-4 Execution Environment Layer Concepts |
|
|
| ##### 3.4.3.5.7 Node Cluster |
|
|
| A Node Cluster is a set of Overlay Network interconnected Compute Nodes of a specific type. The following are four types of Node Clusters. |
|
|
| 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. |
|
|
| ## 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 two types of software which needs to be managed on the O2 Interface: |
|
|
| - The O-Cloud Infrastructure Software, it is described in the CADS [5] |
| - The O-RAN Cloudified Network Function 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 FFS |
| - 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 |
| - Security/Certificates, the details are FFS |
|
|
| Business Capabilities: |
|
|
| - Network Operations shall be able to perform the Software Image Management of O-RAN Cloudified Network Function |
|
|
| Functional Capabilities: |
|
|
| - O-Cloud shall provide Add Software Images of O-RAN Cloudified Network Function to O-Cloud repository |
| - O-Cloud shall provide Delete Software Images of O-RAN Cloudified Network Function from O-Cloud repository |
| - O-Cloud shall provide Update Software Images of O-RAN Cloudified Network Function to O-Cloud repository |
| - O-Cloud shall provide Query Software Images of O-RAN Cloudified Network Function from O-Cloud repository |
| - O-Cloud shall provide Software Image properties information of O-RAN Cloudified Network Function. |
| - SoftwareImageId, Vendor, and Version |
|
|
| ### 3.5.2 O-Cloud Fault Management Concepts |
|
|
| 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 maybe 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.5.2.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.5.2.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 Fault 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 fault notifications. |
|
|
| #### 3.5.2.3 Notifications |
|
|
| Fault notifications originate from the O-cloud infrastructure. There is a relationship between the subscription and notification. When a condition occurs within the IMS that warrants a fault notification an event is issued towards clients that have subscribed to receive such a type of notification or event. |
|
|
| For example, a user could receive alerts on a fault dashboard GUI based on cloud IMS fault notifications. |
|
|
| #### 3.5.2.4 Parallel Reporting |
|
|
| A fault occurrence on an O-Cloud resource should be reported through IMS. DMS resource faults are associated with a workload. It is possible that multiple resources can associate with a workload, whereby one fault might trigger a fault notification on IMS, DMS and O1. Due to the nature of the subscribe/notify mechanism for fault 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 fault 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 fault raised on IMS. |
|
|
| #### 3.5.2.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.5.2.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 a fault which has been reported to a client, such as the SMO, the fault data is replicated within the fault notification to provide details and information of the fault. Thus, the fault information now exists in multiple places both in the IMS and the entity receiving the fault 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 fault against the current faults on the O-Cloud resource? The answer is 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 it had previously sent a fault notification, and then later returns to service, potentially the information at the client and the O-Cloud resource may have different fault 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. |
|
|
| #### 3.5.2.7 Fault Dictionary |
|
|
| A fault dictionary is a reference that can be provided by an O-Cloud vendor which details the faults that can be emitted from O-Cloud resources. The fault dictionary defines conditions that could be reported by the O-Cloud so that the SMO could act on those. The desirable goal is commonality of the fault dictionaries across O-Clouds even though they will differ to some degree by implementation. |
|
|
| For example, the fault dictionary could be used for a variety of purposes. It might help a user decode the meaning of a fault notification. As another example, a fault dictionary could allow for fault signatures or patterns to be identified which may constitute a condition which requires a coordinated response. |
|
|
| #### 3.5.2.8 Queries |
|
|
| In the IMS case, the SMO (client) can issue a specific fault query towards to IMS (publisher) related to the O-Cloud resources and resource pool. 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, a fault query is a message which is expecting a response message from the IMS which matches the selection criteria. In the DMS case, the fault query is expecting a response from the DMS. |
|
|
| For example, the client may request status of a specific type of fault, or new active alarms conditions. The O-Cloud resource would reply to the query by responding with database on the parameters of the query (e.g. IDs or severity). |
|
|
| #### 3.5.2.9 Filtering |
|
|
| It is expected that the client, such as the SMO, can query for specific kinds of faults or groups of faults 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 resource. 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.5.2.10 Fault Logging |
|
|
| Fault logging may be part of the general event logging and is a concept where faults are stored at the O-Cloud resource (the *source of truth*) for a configured amount of time. IMS provisioning should be able to configure the amount of time that logs stored for. The concept of fault logging and storing faults allows a client, algorithm, or user to query for the fault log and analyze those faults. The faults should be timestamped with a common time format and clock source. 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. |
|
|
| For example, fault from an O-Cloud resource could be stored in a log for 1 week. |
|
|
| #### 3.5.2.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.5.2.12 Alarm Correlation |
|
|
| In Concept #4 with 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 fault 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 fault events to identify common root causes. |
|
|
| 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. |
|
|
|  |
|
|
| **PARALLEL REPORTING & ALARM CORRELATION** |
|
|
| *Correlation occurs at the management layer (SMO) because it has a view of alarms coming from parallel reporting through O1, O2dms and O2ims pathways.* |
|
|
| ``` |
| |
| graph TD |
| subgraph Management |
| SMO[SMO] |
| SMO --- FOCOM[FOCOM] |
| SMO --- NFO[NFO] |
| end |
| subgraph Applications |
| Apps[Applications] |
| end |
| subgraph DMS_Workloads |
| Workloads[Workloads] |
| end |
| subgraph IMS_Resources |
| Servers[IMS Resources] |
| end |
| Apps -- O1 --> SMO |
| Workloads -- O2dms --> SMO |
| Servers -- O2ims --> SMO |
| |
| ``` |
|
|
| Diagram illustrating Parallel Reporting & Alarm Correlation. The diagram shows a stack of layers: Management (SMO), Applications, DMS Workloads, and IMS Resources. The SMO layer contains FOCOM and NFO components. The Applications layer contains an Applications box. The DMS Workloads layer contains a Workloads box. The IMS Resources layer contains a row of server racks. Arrows indicate reporting paths: O2ims from IMS Resources to SMO, O2dms from Workloads to SMO, and O1 from Applications to SMO. |
|
|
| Figure 3.5-1 Parallel Reporting & Alarm Correlation |
|
|
| #### 3.5.2.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.5.2.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. A large black box at the top is labeled 'FAULT DOMAIN'. Below it, a text box states 'A Fault Domain is a "unit of failure"'. The main diagram shows three horizontal rows of server racks. Each row is enclosed in a red rectangular border and labeled 'Fault Domain' in red text to the right. On the left, a green box labeled 'IMS Resources' has two arrows pointing to the first two rows. A smaller green box labeled 'Individual IMS Resource' has an arrow pointing to a single server rack within the first row. |
|
|
| Figure 3.5-2 Concept of Fault Domains |
|
|
| #### 3.5.2.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.5.2.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.5.3 O-Cloud Performance Basic Concepts |
|
|
| 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. |
|
|
|  |
|
|
| ``` |
| |
| graph TD |
| SMO[Service Management Orchestrator SMO] |
| subgraph OCloud [O-Cloud] |
| OR1[O-Cloud Resource] |
| OR2[O-Cloud Resource] |
| MT((Measurement Taken)) |
| MR((Measurement Report)) |
| end |
| OR1 --> MT |
| OR2 --> MT |
| MT --> MR |
| MR -- "Measurement Sent" --> SMO |
| |
| ``` |
|
|
| Figure 3.5-3 Performance Measurement Reporting diagram. The diagram shows a Service Management Orchestrator (SMO) at the top, receiving a 'Measurement Sent' message from the O-Cloud. The O-Cloud contains O-Cloud Resources, which generate 'Measurement Taken' data (represented by a gauge icon). This data is then processed into a 'Measurement Report' (represented by a document icon) and sent to the SMO. |
|
|
| Figure 3.5-3 Performance Measurement Reporting |
|
|
| #### 3.5.3.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.5.3.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.5.3.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.5.3.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.5.3.5 Performance Management (PM) Job |
|
|
| 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, TS28.531. ETSI SOL003. |
|
|
| 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. |
|
|
| #### 3.5.3.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.5.3.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.5.3.8 Performance Dictionary |
|
|
| A performance dictionary is a reference that is provided by a resource type vendor. A PM dictionary provides information on performance metrics or KPIs that are relevant to that resource type. The Performance (PM) Dictionary would be onboarded when a new resource type is added; and that resource type would come with an associated a PM dictionary. The PM dictionary for a resource type includes all measurements supported by the 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. The PM dictionary for a resource type it might have all measurements that it supports including standardized measurements. |
|
|
| ## 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 FFS. |
|
|
| ## 3.7 O-Cloud Deployment Life Cycle Management |
|
|
| 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 O-RAN Cloudified Network Functions. The following capabilities will be provided: |
|
|
| - Deploy, which deploys O-RAN Cloudified Network Functions on O-Cloud with necessary O-Cloud resources. |
| - Terminate, which terminates O-RAN Cloudified Network Functions on O-Cloud with releasing associated O-Cloud resources. |
| - Scale, which scales functional behavior and resources of O-RAN Cloudified Network Functions to support services. There is different variance in scaling: |
|
|
| - Horizontal Scaling provides dynamic functional scaling of O-RAN Cloudified Network Functions' behavior by Scale in/Out. This scaling can have different invoke actors such as O-Cloud and SMO. |
| - Vertical Scaling provides dynamic resource scaling of O-RAN Cloudified Network Functions by Scale Up/Down. The details are FFS. |
| - Heal, which provides the ability to recover/mitigate the O-RAN Cloudified Network Functions' abnormal behaviour in the network. The details are FFS. |
| - Health Check. The details are FFS. |
| - Diagnostic. The details are FFS. |
|
|
|  |
|
|
| Figure 3.7-1 O2 Deployment LCM Services diagram. The diagram shows the interaction between Service Provider Functionality (SMO) and Cloud Provider Functionality (O-Cloud). The SMO layer includes Federated O-Cloud Orchestration and Management (FOCOM), Network Function Orchestrator (NFO), and OAM Function. The O-Cloud layer includes Infrastructure Management Services (IMS) and Deployment Management Services (DMS). A dashed line separates the two layers, labeled 'Separation of Concerns boundary'. Arrows indicate the flow of O2 and O2dms services. A legend on the right lists the capabilities: Deploy, Terminate, Scale, Heal, Health Check, and Diagnostic. |
|
|
| Figure 3.7-1 O2 Deployment LCM Services |
|
|
| ### 3.7.1 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 Deploying an O-RAN O-RAN Cloudified NF instance |
| 2. O-Cloud supports Terminating an O-RAN Cloudified NF instance |
| 3. O-Cloud supports Horizontal Scaling (in and out) of an O-RAN Cloudified NF instance |
| 4. O-Cloud supports Healing of an O-RAN Cloudified Network Function instance, this is FFS. |
| 5. O-Cloud supports Querying information about an O-RAN Cloudified NF instance |
| 6. O-Cloud supports Querying status of LCM operations |
| 7. O-Cloud supports Upgrading of any or all components of an O-RAN Cloudified NF instance |
|
|
| ### 3.7.2 Deployment Management Services |
|
|
| The O-Cloud provides services over the O2dms interface to allow an SMO to trigger the functional capabilities specified in Section 3.7.1. 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 3.7.1. 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 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 3.7.1. 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. |
|
|
| # Annex A (Informative): O-Cloud and IMS Initialization |
|
|
| This specification 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. |
|
|
| This document does not define how O-Cloud with IMS services come into being. So, the above steps are provided for informational purposes only. |
|
|
| ## UML sequence diagram for O-Cloud and IMS initialization |
|
|
| ``` |
| @startuml |
| Autonumber |
| skinparam sequenceArrowThickness 2 |
| skinparam ParticipantPadding 5 |
| skinparam BoxPadding 10 |
| |
| Box "Personnel" #lightblue |
| Actor CPM as "Site Administrator" |
| End box |
| |
| Box "Service Management & Orchestration Framework" #gold |
| participant SMO as "FOCOM" |
| ``` |
|
|
| ``` |
| |
| end box |
| Box "O-Cloud Platform" #lightseagreen |
| participant IMS as "O-Cloud Genesis Server" |
| End box |
| |
| CPM -> SMO: Instantiate O-Cloud IMS |
| |
| SMO -> IMS: Setup Server |
| Note over IMS |
| Install Operating System and any necessary SW |
| End note |
| |
| IMS -> SMO: initial Server Ready |
| |
| SMO -> IMS: Install Basic IMS |
| Note over IMS |
| Install initial IMS |
| End note |
| |
| IMS -> SMO: IMS Cloud Infrastructure Resource Management services is ready |
| |
| SMO -> CPM: Initial O-Cloud is Ready |
| == End Use Case == |
| @enduml |
| |
| ``` |
|
|
|  |
|
|
| Sequence diagram showing O-Cloud and IMS Initialization. The diagram involves three main lifelines: Personnel (Site Administrator), Service Management & Orchestration Framework (FOCOM), and O-Cloud Platform (O-Cloud Genesis Server). The process starts with the Site Administrator sending a message '1 Instantiate O-Cloud IMS' to FOCOM. FOCOM then sends '2 Setup Server' to the O-Cloud Genesis Server. The O-Cloud Genesis Server performs an internal action 'Install Operating System and any necessary SW' and then sends '3 initial Server Ready' back to FOCOM. FOCOM sends '4 Install Basic IMS' to the O-Cloud Genesis Server, which performs an internal action 'Install initial IMS'. The O-Cloud Genesis Server then sends '5 IMS Cloud Infrastructure Resource Management services is ready' back to FOCOM. Finally, FOCOM sends '6 Initial O-Cloud is Ready' back to the Site Administrator. The diagram is divided into two sections by a horizontal line labeled 'End Use Case'. |
|
|
| Figure A-1 O-Cloud and IMS Initialization |
|
|
| # Annex ZZZ O-RAN Adopter License Agreement |
|
|
| BY DOWNLOADING, USING OR OTHERWISE ACCESSING ANY O-RAN SPECIFICATION, ADOPTER AGREES TO THE TERMS OF THIS AGREEMENT. |
|
|
| This O-RAN Adopter License Agreement (the “Agreement”) is made by and between the O-RAN Alliance and the entity that downloads, uses or otherwise accesses any O-RAN Specification, including its Affiliates (the “Adopter”). |
|
|
| This is a license agreement for entities who wish to adopt any O-RAN Specification. |
|
|
| ## Section 1: DEFINITIONS |
|
|
| 1.1 “Affiliate” means an entity that directly or indirectly controls, is controlled by, or is under common control with another entity, so long as such control exists. For the purpose of this Section, “Control” means beneficial ownership of fifty (50%) percent or more of the voting stock or equity in an entity. |
|
|
| 1.2 “Compliant Implementation” means any system, device, method or operation (whether implemented in hardware, software or combinations thereof) that fully conforms to a Final Specification. |
|
|
| 1.3 “Adopter(s)” means all entities, who are not Members, Contributors or Academic Contributors, including their Affiliates, who wish to download, use or otherwise access O-RAN Specifications. |
|
|
| 1.4 “Minor Update” means an update or revision to an O-RAN Specification published by O-RAN Alliance that does not add any significant new features or functionality and remains interoperable with the prior version of an O-RAN Specification. The term “O-RAN Specifications” includes Minor Updates. |
|
|
| 1.5 “Necessary Claims” means those claims of all present and future patents and patent applications, other than design patents and design registrations, throughout the world, which (i) are owned or otherwise licensable by a Member, Contributor or Academic Contributor during the term of its Member, Contributor or Academic Contributorship; (ii) such Member, Contributor or Academic Contributor has the right to grant a license without the payment of consideration to a third party; and (iii) are necessarily infringed by a Compliant Implementation (without considering any Contributions not included in the Final Specification). A claim is necessarily infringed only when it is not possible on technical (but not commercial) grounds, taking into account normal technical practice and the state of the art generally available at the date any Final Specification was published by the O-RAN Alliance or the date the patent claim first came into existence, whichever last occurred, to make, sell, lease, otherwise dispose of, repair, use or operate a Compliant Implementation without infringing that claim. For the avoidance of doubt in exceptional cases where a Final Specification can only be implemented by technical solutions, all of which infringe patent claims, all such patent claims shall be considered Necessary Claims. |
|
|
| 1.6 “Defensive Suspension” means for the purposes of any license grant pursuant to Section 3, Member, Contributor, Academic Contributor, Adopter, or any of their Affiliates, may have the discretion to include in their license a term allowing the licensor to suspend the license against a licensee who brings a patent infringement suit against the licensing Member, Contributor, Academic Contributor, Adopter, or any of their Affiliates. |
|
|
| ### Section 2: COPYRIGHT LICENSE |
|
|
| 2.1 Subject to the terms and conditions of this Agreement, O-RAN Alliance hereby grants to Adopter a nonexclusive, nontransferable, irrevocable, non-sublicensable, worldwide copyright license to obtain, use and modify O-RAN Specifications, but not to further distribute such O-RAN Specification in any modified or unmodified way, solely in furtherance of implementations of an ORAN Specification. |
|
|
| 2.2 Adopter shall not use O-RAN Specifications except as expressly set forth in this Agreement or in a separate written agreement with O-RAN Alliance. |
|
|
| ### Section 3: FRAND LICENSE |
|
|
| 3.1 Members, Contributors and Academic Contributors and their Affiliates are prepared to grant based on a separate Patent License Agreement to each Adopter under Fair Reasonable And Non-Discriminatory (FRAND) terms and conditions with or without compensation (royalties) a nonexclusive, non-transferable, irrevocable (but subject to Defensive Suspension), non-sublicensable, worldwide patent license under their Necessary Claims to make, have made, use, import, offer to sell, lease, sell and otherwise distribute Compliant Implementations; provided, however, that such license shall not extend: (a) to any part or function of a product in which a Compliant Implementation is incorporated that is not itself part of the Compliant Implementation; or (b) to any Adopter if that Adopter is not making a reciprocal grant to Members, Contributors and Academic Contributors, as set forth in Section 3.3. For the avoidance of doubt, the foregoing licensing commitment includes the distribution by the Adopter’s distributors and the use by the Adopter’s customers of such licensed Compliant Implementations. |
|
|
| 3.2 Notwithstanding the above, if any Member, Contributor or Academic Contributor, Adopter or their Affiliates has reserved the right to charge a FRAND royalty or other fee for its license of Necessary Claims to Adopter, then Adopter |
|
|
| is entitled to charge a FRAND royalty or other fee to such Member, Contributor or Academic Contributor, Adopter and its Affiliates for its license of Necessary Claims to its licensees. |
|
|
| 3.3 Adopter, on behalf of itself and its Affiliates, shall be prepared to grant based on a separate Patent License Agreement to each Members, Contributors, Academic Contributors, Adopters and their Affiliates under Fair Reasonable And Non-Discriminatory (FRAND) terms and conditions with or without compensation (royalties) a nonexclusive, non-transferable, irrevocable (but subject to Defensive Suspension), non-sublicensable, worldwide patent license under their Necessary Claims to make, have made, use, import, offer to sell, lease, sell and otherwise distribute Compliant Implementations; provided, however, that such license will not extend: (a) to any part or function of a product in which a Compliant Implementation is incorporated that is not itself part of the Compliant Implementation; or (b) to any Members, Contributors, Academic Contributors, Adopters and their Affiliates that is not making a reciprocal grant to Adopter, as set forth in Section 3.1. For the avoidance of doubt, the foregoing licensing commitment includes the distribution by the Members', Contributors', Academic Contributors', Adopters' and their Affiliates' distributors and the use by the Members', Contributors', Academic Contributors', Adopters' and their Affiliates' customers of such licensed Compliant Implementations. |
|
|
| ### Section 4: TERM AND TERMINATION |
|
|
| 4.1 This Agreement shall remain in force, unless early terminated according to this Section 4. |
|
|
| 4.2 O-RAN Alliance on behalf of its Members, Contributors and Academic Contributors may terminate this Agreement if Adopter materially breaches this Agreement and does not cure or is not capable of curing such breach within thirty (30) days after being given notice specifying the breach. |
|
|
| 4.3 Sections 1, 3, 5 - 11 of this Agreement shall survive any termination of this Agreement. Under surviving Section 3, after termination of this Agreement, Adopter will continue to grant licenses (a) to entities who become Adopters after the date of termination; and (b) for future versions of ORAN Specifications that are backwards compatible with the version that was current as of the date of termination. |
|
|
| ### Section 5: CONFIDENTIALITY |
|
|
| Adopter will use the same care and discretion to avoid disclosure, publication, and dissemination of O-RAN Specifications to third parties, as Adopter employs with its own confidential information, but no less than reasonable care. Any disclosure by Adopter to its Affiliates, contractors and consultants should be subject to an obligation of confidentiality at least as restrictive as those contained in this Section. The foregoing obligation shall not apply to any information which is: (1) rightfully known by Adopter without any limitation on use or disclosure prior to disclosure; (2) publicly available through no fault of Adopter; (3) rightfully received without a duty of confidentiality; (4) disclosed by O-RAN Alliance or a Member, Contributor or Academic Contributor to a third party without a duty of confidentiality on such third party; (5) independently developed by Adopter; (6) disclosed pursuant to the order of a court or other authorized governmental body, or as required by law, provided that Adopter provides reasonable prior written notice to O-RAN Alliance, and cooperates with O-RAN Alliance and/or the applicable Member, Contributor or Academic Contributor to have the opportunity to oppose any such order; or (7) disclosed by Adopter with O-RAN Alliance's prior written approval. |
|
|
| ### Section 6: INDEMNIFICATION |
|
|
| Adopter shall indemnify, defend, and hold harmless the O-RAN Alliance, its Members, Contributors or Academic Contributors, and their employees, and agents and their respective successors, heirs and assigns (the "Indemnitees"), against any liability, damage, loss, or expense (including reasonable attorneys' fees and expenses) incurred by or imposed upon any of the Indemnitees in connection with any claims, suits, investigations, actions, demands or judgments arising out of Adopter's use of the licensed O-RAN Specifications or Adopter's commercialization of products that comply with O-RAN Specifications. |
|
|
| ### Section 7: LIMITATIONS ON LIABILITY; NO WARRANTY |
|
|
| EXCEPT FOR BREACH OF CONFIDENTIALITY, ADOPTER'S BREACH OF SECTION 3, AND ADOPTER'S INDEMNIFICATION OBLIGATIONS, IN NO EVENT SHALL ANY PARTY BE LIABLE TO ANY OTHER PARTY OR THIRD PARTY FOR ANY INDIRECT, SPECIAL, INCIDENTAL, PUNITIVE OR CONSEQUENTIAL DAMAGES RESULTING FROM ITS PERFORMANCE OR NON-PERFORMANCE UNDER THIS AGREEMENT, |
|
|
| IN EACH CASE WHETHER UNDER CONTRACT, TORT, WARRANTY, OR OTHERWISE, AND WHETHER OR NOT SUCH PARTY HAD ADVANCE NOTICE OF THE POSSIBILITY OF SUCH DAMAGES. |
|
|
| O-RAN SPECIFICATIONS ARE PROVIDED “AS IS” WITH NO WARRANTIES OR CONDITIONS WHATSOEVER, WHETHER EXPRESS, IMPLIED, STATUTORY, OR OTHERWISE. THE O-RAN ALLIANCE AND THE MEMBERS, CONTRIBUTORS OR ACADEMIC CONTRIBUTORS EXPRESSLY DISCLAIM ANY WARRANTY OR CONDITION OF MERCHANTABILITY, SECURITY, SATISFACTORY QUALITY, NONINFRINGEMENT, FITNESS FOR ANY PARTICULAR PURPOSE, ERROR-FREE OPERATION, OR ANY WARRANTY OR CONDITION FOR O-RAN SPECIFICATIONS. |
|
|
| ### Section 8: ASSIGNMENT |
|
|
| Adopter may not assign the Agreement or any of its rights or obligations under this Agreement or make any grants or other sublicenses to this Agreement, except as expressly authorized hereunder, without having first received the prior, written consent of the O-RAN Alliance, which consent may be withheld in O-RAN Alliance’s sole discretion. O-RAN Alliance may freely assign this Agreement. |
|
|
| ### Section 9: THIRD-PARTY BENEFICIARY RIGHTS |
|
|
| Adopter acknowledges and agrees that Members, Contributors and Academic Contributors (including future Members, Contributors and Academic Contributors) are entitled to rights as a third-party beneficiary under this Agreement, including as licensees under Section 3. |
|
|
| ### Section 10: BINDING ON AFFILIATES |
|
|
| Execution of this Agreement by Adopter in its capacity as a legal entity or association constitutes that legal entity’s or association’s agreement that its Affiliates are likewise bound to the obligations that are applicable to Adopter hereunder and are also entitled to the benefits of the rights of Adopter hereunder. |
|
|
| ### Section 11: GENERAL |
|
|
| This Agreement is governed by the laws of Germany without regard to its conflict or choice of law provisions. |
|
|
| This Agreement constitutes the entire agreement between the parties as to its express subject matter and expressly supersedes and replaces any prior or contemporaneous agreements between the parties, whether written or oral, relating to the subject matter of this Agreement. |
|
|
| Adopter, on behalf of itself and its Affiliates, agrees to comply at all times with all applicable laws, rules and regulations with respect to its and its Affiliates’ performance under this Agreement, including without limitation, export control and antitrust laws. Without limiting the generality of the foregoing, Adopter acknowledges that this Agreement prohibits any communication that would violate the antitrust laws. |
|
|
| By execution hereof, no form of any partnership, joint venture or other special relationship is created between Adopter, or O-RAN Alliance or its Members, Contributors or Academic Contributors. Except as expressly set forth in this Agreement, no party is authorized to make any commitment on behalf of Adopter, or O-RAN Alliance or its Members, Contributors or Academic Contributors. |
|
|
| In the event that any provision of this Agreement conflicts with governing law or if any provision is held to be null, void or otherwise ineffective or invalid by a court of competent jurisdiction, (i) such provisions will be deemed stricken from the contract, and (ii) the remaining terms, provisions, covenants and restrictions of this Agreement will remain in full force and effect. |
|
|
| Any failure by a party or third party beneficiary to insist upon or enforce performance by another party of any of the provisions of this Agreement or to exercise any rights or remedies under this Agreement or otherwise by law shall not be construed as a waiver or relinquishment to any extent of the other parties’ or third party beneficiary’s right to assert or rely upon any such provision, right or remedy in that or any other instance; rather the same shall be and remain in full force and effect. |
|
|
| 1 |
|
|
| 2 |
