Open RA Flashcards by Egipot CD

It is where the radio frequency
signals are transmitted, received, amplified, and digitized

Radio Unit

How well did you know this?

Not at all

Perfectly

It manages RAN procedures for a
UE that are operated in near‐real‐time granularities, ranging from 10 ms to
1

Centralized Unit (CU)

How well did you know this?

Not at all

Perfectly

It is responsible for the RRC and packet data
convergence protocol‐control plane (PDCP‐C) layers of the RAN protocol
stack, dealing with connectivity, mobility, signaling radio bearer
management, and UE/bearer context establishment RAN procedures for a
UE

Centralized Unit – Control Plane (CU-CP)

How well did you know this?

Not at all

Perfectly

It is responsible for the service data adaptation protocol
(SDAP) and PDCP‐user plane (PDCP‐U) layers of the RAN protocol stack,
dealing with the establishment of Data Radio Bearer (DRB) for a UE and
the multiplexing of quality‐of‐service (QoS) flows for the UE‐subscribed IP
Protocol Data Unit (PDU) session to the DRBs

Centralized Unit - User Plane (CU-UP)

How well did you know this?

Not at all

Perfectly

It assigns the 5G QoS Class identification (5QI) for each QoS Flow of a PDU

/ assigns a standardized 5QI value when setting up or modifying a QoS Flow.

core network session management functions (SMFs)

How well did you know this?

Not at all

Perfectly

Connects O-RU and O-DU in ORAN

Open Fronthaul interface

How well did you know this?

Not at all

Perfectly

Interface between the SMO/Non‐RT RIC and the Near‐RT RIC for
non‐real‐time RAN control and optimization

The A1 interface allows
Non‐RT RIC to set the policies in the Near‐RT RIC, receive policy
feedback, and deliver Enrichment Information (EI) to the Near‐RT RIC

How well did you know this?

Not at all

Perfectly

Interface between the Near‐RT RIC and a RAN component, such as O‐gNB, O‐CU, O‐CU‐CP, O‐CU‐UP, O‐DU, or any
combination of those

This interface enables a rich set of E2 Services,
supplied by E2 Nodes to the Near‐RT RIC. The services allow:
Subscription for delivery of network performance data in near‐real
time from the E2 Nodes, with granularity level of network nodes,
cells, slices, individual UEs, and individual QoS Flows
Subscription for near‐real‐time notifications on the events in E2
Nodes, with granularity level of events related to network nodes,
cells, slices, individual UEs, individual QoS Flows, and transfer of
individual protocol messages over RAN interfaces
Sending near‐real‐time control commands to E2 Nodes
Setting policies in the E2 Nodes that prescribe reaction of the E2
Node to internal events

How well did you know this?

Not at all

Perfectly

Interface between the SMO framework and O‐RAN managed
elements, for OAM/FCAPS management.

For the O1 interface, the
management services are defined in line with the corresponding 3GPP
network management specifications. The O1 management information
models essentially are extensions of the corresponding 3GPP
management information models

How well did you know this?

Not at all

Perfectly

Interface used by the SMO and/or O‐DU for OAM
management of the O‐RU

Open FH M‐Plane interface

How well did you know this?

Not at all

Perfectly

Interface between the SMO framework and the O‐Cloud for
management of O‐Cloud

How well did you know this?

Not at all

Perfectly

Interface used for exposure of the analytics data generated by the
Near‐RT RIC

How well did you know this?

Not at all

Perfectly

O‐gNB components (4)

O-RU, O-DU, CU-CP, CU-UP

How well did you know this?

Not at all

Perfectly

It supports Fault, Configuration, Accounting, Performance, Security management capabilities (FCAPS) interface to O‐RAN Network Functions, policy‐based A1 interface to the Near‐RT RIC, O2 interface to O‐Cloud for cloud management and orchestration, and OFH M‐Plane interface for management of the O‐RU

Service Management and Orchestration (SMO) framework

How well did you know this?

Not at all

Perfectly

an SMO
component, which is capable of non‐real‐time control of the Near‐RT
RIC via the A1 interface

Non‐Real‐Time Radio Intelligent Controller (Non‐RT RIC)

How well did you know this?

Not at all

Perfectly

an O‐
RAN function, capable of control and optimization of O‐RAN components in near‐real time via the E2 interface.

Near‐Real‐Time Radio Intelligent Controller (Near‐RT RIC)

How well did you know this?

Not at all

Perfectly

policy‐based interface between the Non‐RT RIC and the Near‐RT RIC for non‐real‐time control and optimization

How well did you know this?

Not at all

Perfectly

management interface between the SMO framework and O‐RAN managed elements, supporting OAM/FCAPS management

How well did you know this?

Not at all

Perfectly

interface between the O‐DU and the O‐RU;
includes Control Plane, User Plane, and Synchronization Plane

Open Fronthaul (OFH)

How well did you know this?

Not at all

Perfectly

interface for O‐Cloud management between the SMO framework and the O‐Cloud

How well did you know this?

Not at all

Perfectly

Difference in architecture split between 3GPP and ORAN

additional Open FrontHaul
(OFH) interface between O‐RAN Distributed Unit
(O‐DU) and O‐RAN Radio Unit (O‐RU)

How well did you know this?

Not at all

Perfectly

allows better adjustment of the RAN behavior to the local environment, resulting in better control and optimization of the network

RAN programmability

How well did you know this?

Not at all

Perfectly

enables
monitoring and control of the RAN components O‐CU (O‐CU‐CP, O‐CU‐UP) and O‐DU in near‐real time

Near‐RT RIC

How well did you know this?

Not at all

Perfectly

NEs that help enable RAN Programmability (3) by introducing additional layer of intelligence

in Service Management and Orchestration (SMO)
framework, Non‐RT RIC and Near‐RT RIC controllers

How well did you know this?

Not at all

Perfectly

New in ORAN, where the Open RAN components can be hosted

Integrated cloud (O-Cloud)

A central manager, which can manage both RAN components and the underlying O‐Cloud.

SMO

Interface that enables FCAPS management of RAN components

O1 interface

Interface that enables policy management of the Near‐RT RIC

A1 interface

Interface that enables management of the cloud where all or some of O‐RAN network functions are hosted (O‐Cloud)

O2 interface

used for control of the RAN Network Functions and of the Near‐RT RIC

Non‐Real‐Time Radio Intelligent Controller (Non‐RT RIC)

can request other SMO components to collect specific network performance measurements via the O1 interface. After the collection of the measurements is completed, the Non‐RT RIC can retrieve the collected information

Non‐Real‐Time Radio Intelligent Controller (Non‐RT RIC)

can use AI/ML training/inference, and can provide ML model management services

Non‐Real‐Time Radio Intelligent Controller (Non‐RT RIC)

implement RAN control/optimization algorithms and may implement other functions, such as management of database where network information is stored

rApp applications hosted in Non-RT RIC

may implement AI/ML services exposed to other rApps, to Non‐RT RIC, Near‐RT RIC, and other RAN components

rApp applications hosted in Non-RT RIC

connects rApps to Non-RT RIC framework (rApps enablers)

The component that provides necessary support to rApps via the R1 interface

Non‐RT RIC Framework

This component provides to rApps support for collection of OAM‐level network performance data (O1) and for non‐real‐time network control and optimization actions via the A1, O1, O2, and Open FH M‐Plane interfaces

Non‐RT RIC Framework

a logical function, used for control and optimization of RAN components in near‐real time

Near-RT RIC

provides to the Near‐RT RIC a guidance for RAN control and optimization in the form of “A1 Policies” via the A1 interface. The policies, in particular, may set the optimization goals

Near-RT RIC

Other Non-RT RIC data that is sent to Near-RT RIC from other sources

Enrichment Information (EI).

It supports near‐real‐time data collection and control, which can be used for optimization

E1 services

a cloud platform customized for virtualized Open RAN, i.e. hardware and software that provide computing, networking, and storage capabilities for the RAN network functions hosted by the cloud

O-Cloud

interface allows Non‐RT RIC to set the policies in the Near‐RT RIC, receive policy feedback, and deliver Enrichment Information (EI) to the Near‐RT RIC

provide necessary support for rApps; may be placed inside or outside the Non‐RT RIC

rApps enablers

is driving intelligent RAN optimization in non‐real‐time domain by setting A1 policies to the Near‐RT RIC

Non‐RT RIC

receives via OAM the high‐level goals (intents) and monitors the Performance Management (PM) information (“counters”) received by the SMO via the O1 interface.

Non-RT RIC

can act toward the Near‐RT RIC by setting or modifying A1 Policies. For example, such action may be to modify the A1 Policy in the part of QoS targets for certain category of UEs

Non-RT RIC

What composes an A1 Policy (2 main)

Scope Statement and Policy statement/goals (policy objectives, resource statements)

format of info that is transferred between the Non‐RT RIC and Near‐RT RIC

JSON encoded

statement identifies the objects, to which the policy statements are applied, such as individual UEs, UE groups, QoS Flows, network slice instances, and cells

Scope Statement of an A1 Policy

It interprets the A1 policy as a guidance: within the policy scope (e.g. a group of UEs), reach the Policy objectives (e.g. UE level guaranteed bit rate), while satisfying the conditions specified in the Resource statements (e.g. prioritize use of certain cells over use of other cells).

Near-RT RIC

describes the A1 policy; it contains a “scope” attribute (ScopeIdentifier object) and one or more of policy objective and policy resources statements.

PolicyObject

it identifies a specific policy instance

policyId

QoS parameters, defined in 3GPP TS 23.501 (give 3 examples)

Guaranteed Flow Bit Rate, Maximum Flow Bit Rate, Packet Delay Budget, Priority Level

QoE parameters (give 3 examples)

Mean Opinion Score (MOS) e.g. video MOS or proprietary, Initial Buffering time, Rebuffering Frequency for video session, Stall Ratio

UE Level Objectives / UE level QoE parameters with reference to 3GPP definitions in such specifications as 3GPP TS 28.552 and 3GPP TS 38.314. (give 3 examples)

average DL/UL UE throughput, DL/UL Packet delay, DL and UL Packet loss rate, DL/UL reliability

SliceSLAObjectives attribute type defines Slice SLA targets per GSMA NG.116

Maximum Number of UEs, Maximum number of PDU sessions, Downlink maximum throughput per UE, Guaranteed downlink throughput quota, Maximum data rates supported by all UEs together in the network slice in DL and UL Maximum data rates supported by the network slice per UE in DL and UL Maximum delay for DL and UL packets in ms Maximum DL and UL PDCP SDU level packet loss rate Minimum DL and UL reliability

Load balancing Objectives attribute defines Load balancing objectives (3GPP TS 28.552

Target PRB usage in percentage of the total PRBs in the cell. Covered PRB usage types include mean/peak DL/UL PRBs used for data traffic, either total in the cell or per network slice (per S‐NSSAI), where slicing is applied. The target for PRB usage, in percent Mean and peak DL and UL PRBs used for data traffic Mean and peak DL and UL PRBs used for data traffic per S‐NSSAI

Traffic Steering Preference (TSP) Resources Describes restrictions or priorities, which change the traffic scheduling comparatively to the way it would be with default behavior. (give 2 examples)

set of cells to be avoided or forbidden for certain kind of traffic, set of cells preferred as primary cells for Dual Connectivity

Load Balancing Resources (give 1 example)

set of cells, to which the traffic can be offloaded

maximum delay of the start of the video playback from the initiation of the playback by the user

Initial Buffering

calculated as ratio of the number of stalling events to the length of the media

Rebuffing frequency

total duration of the stalling events divided by the total media length

Stall ratio

This data can be used by the Non‐RT RIC and Near‐RT RIC for improvement of RAN control/optimization capabilities

Enrichment Information (EI)

The component that can collect near‐real‐time RAN data from E2 Nodes; UE level and cell level information is supported

Near-RT RIC

The component that can receive near‐real‐time notifications of events in the E2 Nodes

Near-RT RIC

The component that can perform near‐real‐time control and optimization actions toward E2 Nodes

Near-RT RIC

The components connected to the Near‐RT RIC via E2 interface

"E2 Nodes" can be O-CUCP, O-CUUP, O-DU

every E2 Node can be connected to only one Near‐RT RIC - TRUE OR FALSE?

True

multiple E2 Nodes can be connected to same Near‐RT RIC - TRUE OR FALSE?

True

2 categories of functions of the E2 protocol

RIC Services and RIC support functions (O‐RAN.WG3.E2GAP‐R003‐v05.00

Name 5 functions of RIC Services (also called E2 services), provided by the E2 Node to the Near‐RT RIC

REPORT, INSERT, CONTROL, POLICY, and QUERY

Examples of RIC functional procedures

- Related to subscription are RIC Subscription, RIC Subscription Modification, RIC Subscription Delete, RIC Subscription Delete Required, RIC Subscription Modification Required. - Common procedures: RIC Control, RIC Indication, and RIC Query

E2 service function that is used to expose RAN control and UE context related info

E2 REPORT service

E2 service function that is used to suspend RAN control related call processes

E2 INSERT service

E2 service function that is used to resume or initialte RAN control related call processes (such as modify RAN config and/or E2 service-related UE context info)

E2 CONTROL service

E2 service function that is used to modify the behavior of RAN control related processes

E2 Policy services

E2 service function that is used to request and retrieve RAN and/or UE related info

E2 Query service

E2SM-RC

E2 Service Model RAN Control

Open RA Flashcards

(80 cards)