Search Results
O1 and O2 Interfaces. The O1 interface connects the SMO to the RAN managed elements. These include the near real-time RIC, O-CU, O-DU, O-RU, and the open evolved NodeB (O-eNB).
A set of three E2 specifications present corrections and minor enhancements to their corresponding v2.0. Support of E2 removal, clarifications on multiple TNLA handling, and definition of UE identity over the E2 interface are provided. O-RAN Near-Real-Time RAN Intelligent Controller E2 Service Model (E2SM) KPM v2.01
- WG1: Use Cases and Overall Architecture Workgroup
- WG4: The Open Fronthaul Interfaces Workgroup
- WG5: The Open F1/W1/E1/X2/Xn Interface Workgroup
- WG6: The Cloudification and Orchestration Workgroup
- WG7: The White-Box Hardware Workgroup
- Wg8: Stack Reference Design Workgroup
- WG9: Open X-Haul Transport Workgroup
- WG10: OAM Work Group
- SFG: Security Focus Group
- Tifg: Test and Integration Focus Group
O-RAN Architecture Description v5.0
The O-RAN Architecture Description document specifies the overall architecture of O-RAN. It describes all of the O-RAN functions and relevant interfaces that connect these functions. This version enhances the functional architecture of the Non-RT RIC by elaborating the relationship between rApps, R1 interface, Non-RT RIC framework and SMO framework. It introduces the concept of ‘anchored’ vs. ‘non-anchored’ functionality within the SMO and Non-RT RIC frameworks. It also provides a high level...
O-RAN Slicing Architecture v5.0
This document describes O-RAN slicing related use cases, requirements and architecture. Along with requirements and a reference slicing architecture, slicing related impact to O-RAN functions and interfaces is also captured. This version includes addition of O-NSSI (O-RAN Network Slice Subnet Instance) modification procedure and the Annex on transport network slicing use cases and roadmap.
O-RAN Use Cases Analysis Report v6.0
This document describes potential O-RAN use cases at a very high level, emphasizing how the use cases are enabled by the O-RAN architecture along with basic input data expectations and resulting actions. This version includes additions to QoE Optimization use case.
O-RAN Open Fronthaul Management Plane Specification v7.0
This document describes O-RAN Open Fronthaul M-Plane Specification, which defines the Management Plane of the Open Fronthaul Interface as well as the associated YANG models. In this version there are several clarifications and new capabilities including External antenna delay handling, TD-RSSI measurement capability & FTPES based file transfer.
O-RAN Fronthaul Interoperability Test Specification (IOT) v5.0
This document describes O-RAN Open Fronthaul IOT Specification, which defines tests to validate the ability for O-DU and O-RU equipment to operate together using the Open Fronthaul Interface. In this version there are several clarifications and a few new capabilities, most significantly a down-selected profile list of test configurations for mMIMO.
O-RAN Fronthaul Control, User and Synchronization Plane Specification v7.0
This document describes O-RAN Open Fronthaul CUS-Plane Specification, which defines the Control Plane, User Plane and Synchronization Plane of the Open Fronthaul Interface. In this version there are several clarifications and a few new capabilities, most significantly External Antenna Delay handling, 2-step delay measurement, 3GPP R16 PRRACH formats and new section extensions 19 & 20 for improved efficiency.
O-RAN NR C-plane profile v5.0
The scope of C-Plane profile spec is to further clarify (i.e. profile) for each RAN node the expected behavior (still within the scope of the 3GPP specifications), e.g. usage of IEs for each use case, general behavior of each node, etc. C-Plane profile spec contains profiles of X2/F1/Xn C-Plane procedure for EN-DC use cases, NR-SA use cases and NR-DC use cases. This version of the C-Plane profile spec mainly introduces: 1. 11 new use cases (2 EN-DC cases, 7 NR-SA cases, and 2 NR-DC cases) 2...
O-RAN O1 Interface specification for O-CU-UP and O-CU-CP v1.0 including Yang models
The scope of O-CU O1 Interface spec is to specify the interface that links O-CU-CP and O-CU-UP to the Service Management and Orchestration (SMO) framework. It is focused on O-CU management operations, performance counters, fault supervision, software management, and configuration parameters for O-CU. This version of O-CU O1 spec is a baseline spec that mainly includes: 1. O-CU performance management counters 2. O-CU security handling Information and Data Models
O-RAN O1 Interface specification for O-DU v2.0 including YANG models and AnnexD
The scope of O-DU O1 Interface spec is to specify the interface that links O-DU to the Service Management and Orchestration (SMO) framework. It is focused on O-DU management operations, performance counters, fault supervision, software management, synchronization management, and configuration parameters for O-DU. This version of O-DU O1 spec mainly introduces: 1. Updates to O-DU PM counters and DL/UL PRB differentiation to support Slicing use-cases 2. Security requirements update (TLS and NAC...
O-RAN Cloud Architecture and Deployment Scenarios for O-RAN Virtualized RAN v2.02
This document specifies the O-RAN cloud architecture (O-Cloud) along with the requirements of an O-Cloud. This document also specifies the various scenarios and use cases for O-RAN deployment. This version introduces LLS-C1 in the time synchronization architecture, besides adding the requirement for the cloud platform to support traffic isolation for an application. This version also extends the Scenario E for macrocell deployment where the O-DUs and O-RUs are co-located at the cell site, but...
O-RAN Acceleration Abstraction Layer FEC Profiles v1.0
This document details the AAL specification consisting of the description of the interface, information model requirements to implement an AALi, for the AAL_PUSCH_FEC and AAL_PDSCH_FEC Profiles. This version only includes stage 2 aspects of the specification (i.e., requirements, definition of input and output parameters, and optional vs mandatory items). The stage 3 spec, i.e., a header file, will be released after procedural matters relating to treatment of non-O-RAN license material (e.g.,...
O-RAN Orchestration Use Cases and Requirements for O-RAN Virtualized RAN v2.01
This document specifies use cases and associated requirements for the management and orchestration of O-RAN virtualized RAN. This version incorporates use case updates to support network slicing and common application lifecycle management, and adds use cases for reset/recovery and fault subscribe/notify/query to support additional management functionality.
O-RAN Hardware Reference Design Specification for Indoor Picocell (FR1) with Split Architecture Option 8 v3.0
This is the O-RAN WG7 Hardware Reference Design Specification for Indoor Picocell FR1 with Split Architecture Option 8 (V2). It describes one white box hardware reference design example for indoor deployments. In this version you will find: 1. Added FHM terminologies 2. Added Informative/Normative verbiage 3. Added Enterprise Microcell deployment scenario
O-RAN Hardware Reference Design Specification for Indoor Picocell (FR1) with Split Architecture Option 7-2 v3.0
This is the O-RAN WG7 Hardware Reference Design Specification for Indoor Picocell FR1 with Split Architecture Option 7-2 (V2). It describes one white box hardware reference design example for indoor deployments. Major revision in this version are as follows: 1. FHM terminologies added 2. Informative/Normative verbiage added 3. Compliant to Indoor Picocell Hardware Architecture and Requirement (FR1 Only) v01.00 4. Revisions to the O-RU architecture figures and added explanation text included
O-RAN Deployment Scenarios and Base Station Classes v3.0
The document specifies a high-level architecture and hardware design for an Indoor Picocell using the Split Option 6 deployment scenario as specified in the Deployment Scenarios and Base Station Classes document. Major revision in this version are as follows: 1. FHM terminologies added 2. Informative/Normative verbiage added
O-RAN Stack Interoperability Test Specification v2.0
The O-RAN WG8 Stack Interoperability Test Specification provides interoperability test cases of O-CU and O-DU for end to end call flows. This version contains new O1 and E2 Test Cases.
O-RAN Base Station O-DU and O-CU Software Architecture and APIs v4.0
The O-RAN WG8 Base Station O-CU and O-DU Architecture and APIs specification provides the reference architecture, design and APIs for O-CU and O-DU implementation. The specification details the functional block of O-CU and O-DU, including messages across L1, L2 and L3 layers and call flows. This version contains: 1. L2 APIs: Corrections and new APIs 2. MAC-Scheduler single API for DL scheduling information and L2 API corrections 3. mMIMO configuration/functionalities 4. Beamforming configurat...
O-RAN Xhaul Packet Switched Architectures and Solutions v2.0
The document is intended to describe best practices for O-RAN transport based on end-to-end packet switching technology. Version 02.00 provides an enhancement to address the need for transport network slicing that was agreed with WG1 as part of slicing feature plan phase 1.
O-RAN Management Interface for Transport Network Elements v2.0
The document is intended to describe best practices for O-RAN transport Network Element (TNE) management interfaces. Version 02.00 provides the following enhancements to version 01.00: 1. IP/Ethernet enhancement agreed with WG1 as part of slicing feature plan phase 1 2. Optical access for point-to-point interfaces and WDM-PON
O-RAN Xhaul Transport Testing v1.01
This document defines the testing requirements for an Open Xhaul transport infrastructure. It is based on Xhaul Transport Requirement document, Packet Switched Architectures and Solutions document, the WDM-based Fronthaul Transport, and Synchronization Architecture and Solution documents.
O-RAN Operations and Maintenance Architecture v5.0
The O-RAN OAM Architecture identifies management services, managed elements, functions and applications supported in O-RAN, including the interworking between SMO and O-RAN O-Cloud management components. Requirements are derived from end-to-end OAM use cases, including the initial provisioning of O-RAN service across VNFs and PNFs and the collection of measurement data. This version adds an end-to-end use case for configuration provisioning as well as updates for alignment with the O-RAN Arch...
O-RAN Operations and Maintenance Interface Specification v5.0
The O1 interface defines management services supported by O-RAN managed elements and provides an interface between these managed elements and the SMO. In this version of the O1 interface we introduce the following enhancements. 1. Provisioning: Update Provisioning Section of O1 specification to contain only the NETCONF command that is used for the specific procedure and remove the NETCONF commands executed before and after the procedure. The full scenario is in the OAM Architecture Document....
O-RAN Security Protocols Specifications v2.0
This document specifies security protocols as to be used for O-RAN compliant implementation. It adds IPSec, DTLS and TLS 1.2 and TLS 1.3 alignment with 3GPP TS33.210 from V1.0 version.
O-RAN Security Threat Modeling and Remediation Analysis 2.0
This document specifies the O-RAN Security Threat Modeling and Remediation Analysis. It identifies assets to be protected, analyzes the O-RAN components for vulnerabilities, examines potential threats associated with those vulnerabilities and provides security principles, which stakeholders should address when building a secure end-to-end O-RAN system. From V1.0 it adds a risk assessment that aims to assess the criticality of threats based on their potential impacts.
O-RAN Security Requirements Specifications v1.0
This document specifies the Security Requirements per O-RAN Interface and per O-RAN component.
O-RAN Certification and Badging Processes and Procedures v2.0 include template table of records
This document describes the certification and badging processes and associated detail technical procedures that Open Testing and Integration Centre (OTIC) and various other testing entities should adopt. Changes from the previous version include: 1. Clarification of certification/badging objectives in Chapter 2 & test result sharing in Chapter 3 2. Alignment with the updated Conformance and IOT specs from WG4 and WG5 in Chapter 4 & 5 3. Inclusion of custom IOT profile in the badging process i...
O-RAN End-to-end Test Specification v2.0
This test specification is focused on validating the end-to-end system functionality, performance, and key features of the O-RAN system as a black box, incl. testing of application-level services (data, voice, video) as experienced by end-user, testing of end-to-end radio access network security, load and stress testing. Future versions of this specification may add additional chapters for test cases on timing and synchronization, operations, administration, and maintenance (OAM), and other c...
O-RAN Criteria and Guidelines of Open Testing and Integration Centre v3.0
This document describes the essential criteria and guidelines (guiding principles) from process, organization, space and technical perspective on the qualified Open Testing and Integration Centre (OTIC). This version changes the format of the document from a technical specification to a process document, updates the OTIC application approval process (Chapter 4), adds the Hosting agreement (Annex C) and extends the OTIC application form with OTIC host self-declaration (Annex A).
Feb 15, 2022 · It opens up new interfaces including A1/O1/O2/E2. It specifies aspects of RAN virtualization. It also standardizes F1/W1/E1/X2/Xn interfaces already covered by 3GPP but the intention is to complement 3GPP standards. For example, O-RAN specifies profiles. What's the O-RAN architecture?
How vascular injury limits oxygen delivery. Adaptive Contrast vs Standard EWOT. This video clip review how your body reacts differently from LiveO2 Adaptive Contrast vs. Standard EWOT. What will LiveO2 do for you. LiveO2 Protocols. Health Optimization. Recovery Support. Performance. Personal Coaching.
Percent Oxygen (O2) analysis, best compromise between long life and fast response 12 months E -2 C57283-E2 Long life cell for use is the model 3290 (for use in unattended air liquefaction nitrogen skids) 24 months InstaTrace B71875
Oxygen reduction reaction. In chemistry, the oxygen reduction reaction refers to the reduction half reaction whereby O 2 is reduced to water or hydrogen peroxide. In fuel cells, the reduction to water is preferred because the current is higher. The oxygen reduction reaction is well demonstrated and highly efficient in nature. [1] [2] Stoichiometry.
