Scribd Logo
Upload

Welcome to Scribd!

  • 515 views

    Open RAN Architecture

    Uploaded by

    RAHUL
    Open RAN allows for multi-vendor interoperability in radio access networks by separating hardware and software functions. In Open RAN, lower layer radio functions are handled by distributed units near cell sites while higher layer functions are managed in a centralized pool located closer to multiple cell sites. This architecture enables network flexibility through virtualization and configurable hardware and software defined functions.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd

    Open RAN Architecture

    Uploaded by

    RAHUL
    515 views3 pages
    Open RAN allows for multi-vendor interoperability in radio access networks by separating hardware and software functions. In Open RAN, lower layer radio functions are handled by distributed units near cell sites while higher layer functions are managed in a centralized pool located closer to multiple cell sites. This architecture enables network flexibility through virtualization and configurable hardware and software defined functions.

    Original Description:

    Open RAN Architecture

    Original Title

    1. Open RAN architecture

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Open RAN allows for multi-vendor interoperability in radio access networks by separating hardware and software functions. In Open RAN, lower layer radio functions are handled by distributed units near cell sites while higher layer functions are managed in a centralized pool located closer to multiple cell sites. This architecture enables network flexibility through virtualization and configurable hardware and software defined functions.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    515 views3 pages

    Open RAN Architecture

    Uploaded by

    RAHUL
    Open RAN allows for multi-vendor interoperability in radio access networks by separating hardware and software functions. In Open RAN, lower layer radio functions are handled by distributed units near cell sites while higher layer functions are managed in a centralized pool located closer to multiple cell sites. This architecture enables network flexibility through virtualization and configurable hardware and software defined functions.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    of 3
    At a glance
    Powered by AI
    Open RAN enables the use of multi-vendor hardware and software by splitting RAN functions. It aims to reduce costs, improve flexibility and introduce AI capabilities.

    Open RAN splits key RAN functions among different nodes - the radio unit (RU), distributed unit (DU) and centralized unit (CU) to manage different services and applications.

    In Open RAN, the RU is connected to the DU via the Open fronthaul interface (eCIPRI). The DU and CU communicate using the F1-c interface for control plane and F1-u interface for user plane.

    Open RAN-

    Open here refers to something which is not a proprietary of an individual or a company. It


    (Something) can be Hardware, Software, interface, API, source code etc.

    So, Open RAN (O-RAN) is a radio access network where hardware from any equipment supplier can
    be used with software, API, source code, interface etc. from other different suppliers. Open RAN
    enable multi supplier interoperability, decrease time to market, improve performance and introduce
    intelligence using AI/ML (Artificial Intelligence/Machine Learning). Open RAN split key RAN functions
    among different nodes such as radio unit (RU), distributed unit (DU) and centralized unit (CU) to
    manage different services and applications (real time and non-real time). Network Function
    Virtualization plays a major role in Open RAN.

    RAN evolution in Network-

    RAN has evolved over time to make a flexible and software configurable network to support
    different characteristics of the types of services that 5G system envisages. RAN functionalities split
    between Distributed unit (DU) and Centralized unit (CU) in O-RAN. There can be two different
    interfaces assigned between DU and CU – one for Control plane (F1-c interface) and another for User
    plane (F1-u interface). This evolved architecture requires separation of general-purpose hardware
    and specialized network hardware. The functionality of general-purpose hardware is suitable for
    network functions virtualization (NFV), whereas the specialized hardware in the RAN will become
    dynamically configurable.

    In O-RAN, lower layer functionality is separated from higher layer. Lower layer functions (phy, mac,
    rlc) are kept at DU whereas higher layer functions (pdcp, rrc, sdap) are kept in pool for multiple sites
    at a hub location (within few Kms of cell sites), known as central unit as shown below –
    Basic Open RAN architecture-

    In O-RAN, Radio unit (RU) connected to DU via Open fronthaul interface (eCIPRI). This “eCIPRI over
    fiber” fronthaul has capability to achieve 1ms latency and 100Gbps data rate.

    All Network elements (Managed Elements) and their instances (Managed functions) communicates
    with manager using management interface. This manager provides management services such as –

    • Fault Supervision

    • Performance Assurance & Provisioning

    • Trace Management

    • File Management

    • Software Management

    • Communication Surveillance

    • Start and Registration of a Physical Network Function (PNF)

    • Instantiation and Termination of a Virtualized Network Function (VNF)


    • Scaling Management Services for VNF

    Service Management and Orchestration Framework is responsible for the management and
    orchestration of the managed elements under its span of control. The framework can for example
    be a third-party Network Management System (NMS) or orchestration platform.

    Service Management and Orchestration Framework must provide an integration fabric and data
    services for the managed functions. The integration fabric enables interoperation and
    communication between managed functions within the O-RAN domain. Data services provide
    efficient data collection, storage and movement capabilities for the managed functions. In order to
    implement multiple OAM architecture options together with RAN service modelling, the modelling
    of different OAM deployment options and OAM services (integration fabric etc.) must be supported
    by SMO.

    Non-Real Time Radio Intelligent Controller (non-RT RIC) is a part of the Service Management &
    Orchestration Framework and communicates to the near-RT RIC using the A1 interface.

    Non-RT control functionality (> 1s) and near-Real Time (near-RT) control functions (< 1s) are
    decoupled in the RIC. Non-RT functions include service and policy management, RAN analytics and
    model-training for some of the near-RT RIC functionality, and non-RT RIC optimization.

    O1 is the interface between the O-RAN Managed Element and the management entity.

    The O1 OAM Interface includes implementation of Fault, Configuration, Accounting, Performance,


    Security (FCAPS) functions, File management and software management functions to ME (s)
    virtualized and physical alike. In the case of virtualized Network Elements (NEs), the interface
    describes standardized interfaces for orchestration and monitoring of the infrastructure resource
    used to deploy the software as a separate entity. In the case of pure monolithic architectures with
    fully integrated hardware and software, the hardware is reported with the software.

    You might also like