O-RAN Architecture

and Use Cases

Marcin Dryjański, Ph.D.

SIGCOM, SnT, University of Luxembourg, Seminar, 14.05.2021

Marcin Dryjanski

Co-Founder of RIMEDO Labs

Working within 5G area since 2012

5G RAN Architect at Huawei R&D

Ph.D. on RRM, Senior IEEE Member

Consultant & Technical Trainer

Book ”From LTE to LTE-A Pro and 5G”

Outline

Introduction

O-RAN Overview

O-RAN Architecture
O-RAN
RAN Intelligent Controller (RIC)

O-RAN Use Cases Overview

Traffic Steering Use Case

rimedolabs.com
Introduction

rimedolabs.com
5G Architecture
5GC Control Plane

N6

5GC
User Plane

rimedolabs.com
Open RAN – Network Transformation
Core
Network CN
(CN)

Open RAN

CU

RIC
Traditional RAN
DU

• Disaggregation
Open FH
• Open Ecosystem
• Open Interfaces RU
• Decoupling HW from SW
• Intelligent management

rimedolabs.com
What is Open RAN?

„Closed” RAN Open RAN

RRH BBU
5GC
RRH BBU
RAN CN OSS
RRH BBU
EPC
RRH BBU

COTS (Linux / VM)

Single vendor Multi-vendor

rimedolabs.com
 O-RAN Timeline/History

2021 – March
O-RAN Alliance
2020 – May releases second
Open RAN Policy set of
2020 – Feb Coalition was specifications
O-RAN Alliance formed
2019 – July sets up
SCF enabled O- partnership with
2019 – Feb RAN ecosystem TIP
Rakuten deploys with nFAPI
2018 - Feb World’s first V-
O-RAN Alliance RAN network
2017 formed (from
First Open RAN xRAN Forum and
2016 trials in LATAM C-RAN Alliance)
Telecom Infra
Project (TIP) was
formed
xRAN Forum was
formed

rimedolabs.com
List of Abbreviations
5GC 5G Core Network O-eNB O-RAN evolved NodeB
5QI 5G QoS Indicator ONF Open Networking Foundation
AMF Access and Mobility Function O-RAN Open RAN
API Application Programming Interface O-RU O-RAN Radio Unit
CA Cell Association OSC O-RAN Software Community
CN Core Network PDCP Packet Data Convergence Protocol
CP Control Plane PHY Physical Layer
CU Central Unit PM Performance Measurements
D/A Digital to analog QoS Quality of Service
DU Distributed Unit R/W Read/Write
FCAPS Fault, Configuration, Accounting, Performance, Security RA Resource Allocation
FH Fronthaul RAN Radio Access Network
gNB next-generation NodeB RFE Radio Front-End
I/F Interface RIC RAN Intelligent Controller
LLS Lower-Layer Split RLC Radio Link Control
MAC Medium Access Control RRC Radio Resource Control
MANO Management and Orchestration RRM Radio Resource Management
MBB Mobile Broadband RT Real-Time
Mgmt Management RU Remote/Radio-Unit
ML Machine Learning SDAP Service Data Adaptation Protocol
NG-RAN Next Generation RAN SD-RAN Software Defined RAN
nRT near Real Time SM Spectrum Management
O-CU-CP O-RAN Central Unit Control Plane SMO Service Management and Orchestration
O-CU-UP O-RAN Central Unit User Plane S-NSSAI Single - Network Slice Selection Assistance ID
O-DU O-RAN Distributed Unit SON Self-Organizing Networks
TS Traffic Steering
UE User Equipment
UPF User Plane Function
xApp Application to be placed at nRT RIC

rimedolabs.com
O-RAN Overview

rimedolabs.com
 Open-RAN
Non-RT RIC

A1

near-RT RAN Intelligent Controller (RIC)

E2 E2 E2

N2
to AMF RRC PDCP-C

O-CU-CP

Sched.
N3
to UPF SDAP PDCP-U RLC MAC PHY D/A & RFE

O-CU-UP O-DU O-RU

rimedolabs.com
E2 Node
 O-RAN Defined Entities
System supporting orchestration of O-RAN SMO
components
Logical node enabling Non-RT control/optimization of RAN
elements and resources, AI/ML workflow, and policy-based
Non-RT RIC guidance of applications/features in nRT RIC

Application designed to run on nRT RIC:

• likely to consist of one or more µ-services
• identifies data to consume and provide

xApp

xApp

xApp
• independent of the nRT RIC
• may be provided by 3rd party. Logical node enabling nRT control/optimization of RAN
elements and resources via fine-grained data collection
and actions over E2. May include AI/ML workflow.
near-RT RIC
Logical node hosting SDAP and UP part of PDCP

Logical node hosting RLC/MAC/High-PHY layers based on

Logical node hosting RRC and CP part of PDCP O-CU-CP O-CU-UP O-DU LLS

Cloud Computing platform comprising: O-RU Logical node hosting Low-PHY layer (FFT/iFFT, PRACH
• PHY infra nodes to host O-RAN fcns (e.g. nRT extraction) and RF based on LLS
RIC, O-DU),
• Supporting SW components (e.g. OS, VM O-Cloud
Monitor, Container Runtime)
• MANO functions

rimedolabs.com
Based on defs from: O-RAN Alliance Specifications
 Relevant Entities & Relations
• MANO • SMO & Non-RT RIC • Exemplar Platform for
• CU-CP/CU-UP • near-RT RIC O-RAN Based on
• DU • A1, E2, O1, O2, Open FH Specific Design Choices
• E1, F1-C, F1-U • O-RAN LLS

ONF SD-RAN TIP RAN

Intelligence and
O-RAN Automation (RIA)
O-RAN Software
Alliance Community subgroup
3GPP Specifications (OSC)
Standards Use RICs to develop & deploy
Other features AI/ML based xApps for RAN use
cases (SON, RRM, MMIMO)

Other features

Reference Designs Exemplar Platforms Use Case Development

Notes:
• There is also Open RAN Policy Coalition to promote policies that will advance the adoption of O-RAN concept rimedolabs.com
• Other entities may show up, like cloud platforms for placing O-RAN / interoperatibility testing / „xApp stores”
 O-RAN Alliance WGs
WG1 • UC, arch, slicing, security Focus: identify/study use cases and
overall architecture

WG2 • Non-RT RIC, A1

Focus: optimization and automation on
RRM using RIC, definition of RIC
WG3 • Near-RT RIC, E2 architecture

WG4 • Open FH (IEEE1914, eCPRI, CPRI)

Focus: open interfaces to acheive
interoperability between different RAN
WG5 • Open F1, W1, E1, X2, Xn HW and SW vendors

WG6 • Cloudification and Orchestration

Focus: commoditization, virtualization
WG7 • Whitebox HW reference design and modularization/decoupling of RAN
SW and HW, referece design

WG8 • Stack reference design (CU/DU)

Focus: new transport network based on
WG9 • Open X-Haul (FH, MH, BH) new architectures and end user service
requirements for FH, MH and BH

WG10 • OAM Focus: OAM framework including

requirements, architecture O1 interface

Note: Specifications are at different maturity levels, e.g. (as of April 2021):
• FH control, user and synchronization specification is considered stable (version 5.0)
• O1 SMO data models, O2 cloud management interface and security specifications haven't been specified yet.
As of today it is impossible to build an end-to-end, standardized O-RAN compliant system. One can build a partially compliant system, which would rimedolabs.com
have proprietary components (requiring pairwise agreements between involved parties).
O-RAN Virtual Exhibition
 O-RAN Software Community (OSC)
OSC is a collaboration between O-RAN ALLIANCE and Linux Foundation to support the creation of RAN software.

O-RAN Central Unit (OCU) - reference

implementation of RRC, SDAP, PDCP, F1AP
module and API between

O-DU High (ODUHIGH) and O-DU Low

(ODULOW) - functional blocks developped
RIC Applications (RICAPP) -
according to O-RAN and 3GPP specification
open source sample xAPPs

O-RAN OSC
Projects
near-RT RAN Intelligent
Controller (RIC) - initial RIC
Currently available:
Platform to support xAPPs
Cherry Release (12.2020) Service Management and Orchestration
(SMO) – onboarding of rApps running on
NRT RIC, xApps running on nRT RIC

Non-RT RIC (NONRTRIC) – incl. non-RT

RRM, procedure optimization, policies
and AI/ML models to support operation
of nRT RIC functions
Notes: There are additional supporting projects, like,
rimedolabs.com
Simulations (SIM), Integration and test (INT), or Infrastructure (INF)
O-RAN Resources

• O-RAN Alliance Whitepaper

• O-RAN Specifications
• O-RAN SC (Cherry Release)
• SD-RAN / ONF
• SD-RAN Presentation
• SD-RAN Whitepaper

rimedolabs.com
Selected O-RAN Alliance Specifications
Spec name
O-RAN.WG1.O-RAN-Architecture-Description-
v02.00
O-RAN.WG1.OAM-Architecture-v03.00
O-RAN.WG3.RICARCH-v01.00
O-RAN.WG1.Use-Cases-Detailed-Specification-
v03.00
O-RAN.WG3.E2GAP-v01.01
O-RAN-WG2.A1GAP-v02.00
O-RAN.WG2.A1AP-v02.00
O-RAN.WG1.O1-Interface.0-v03.00
Title
O-RAN Architecture Description
O-RAN Operations and
Maintenance Architecture
Near-RT RIC Architecture
Use Cases Detailed Specification
Near-Real-time RIC Architecture
& E2 General Aspects and
Principles
A1 interface: General Aspects
and Principles
A1 interface: Application Protocol
O-RAN Operations and
Maintenance Interface
Specification
Contents
O-RAN definitions, architecture,
interfaces, block diagrams
OAM use cases, OAM architecture
nRT RIC Architecture, APIs for xApps,
requirements
Use cases background, entities involved,
solutions, required data
nRT RIC Functional allocation,
architecture and support functions, E2
principles and functions, service model
A1 service architecture and functions, A1
signalling procedures, protocol structure
A1 services, API definitions, Open API
specification, JSON objects (e.g. for TS
policy)
Management services (privisioning, fault
supervision, performance assurance,
etc.)
rimedolabs.com
O-RAN Architecture

rimedolabs.com
O-RAN Architecture SMO
Control Loops

Non RT
Non-RT RIC >1s

policy, enrichment
Open FH
O1 info, ML model mgmt A1 O2
M-Plane
(O1 FFS)
policy feedback

xAPP

xAPP

xAPP

xAPP
platform resources
FCAPS for O-RU: and workload
SW mgmt, CM, PM, FM, to Near-RT RIC management
File mgmt, installation (scaling, FCAPS, SW
near-RT RIC mgmt, resource
create/delete)
E2 E2 E2 E2

to O-eNB NG-c to 5GC (AMF) near RT

O-eNB
O-CU-CP to eNB / en-gNB,
<1s
to O-CU-CP gNB / ng-eNB >= 10 ms
X2-c, Xn-c
E1
monitor, suspend /
stop, override or
FCAPS control via policies
NG-u to 5GC (UPF)
config, reconfig, to O-CU-UP
discovery, registration,
O-CU-UP to eNB / en-gNB, gNB
data collection / ng-eNB
versioning, monitoring
and feedback X2-u, Xn-u
F1-c F1-u
performance &
resource updates
O-DU

RT (O-DU Scheduler)
Open FH I/F < 10 ms

O-RU

O-Cloud rimedolabs.com
O-RAN Implementation Options (1/2)
Disaggregated Network Functions Aggregated O-CU-CP, O-CU-CP, O-DU

SMO SMO
Non-RT RIC Non-RT RIC
O1

A1 O2 O1 A1 O2

near-RT RIC near-RT RIC

E2 E2 E2 E2

O-CU-CP O-CU-CP

E1

O-CU-UP O-CU-UP
E2 Node E2 Node
F1-c F1-u

O-DU O-DU

Open FH Open FH Open FH Open FH

M-Plane M-Plane
O-RU O-RU

O-Cloud O-Cloud

rimedolabs.com
O-RAN Implementation Options (2/2)
Aggregated near-RT RIC, O-CU-CP, O-CU-CP All Nodes Aggregated

SMO SMO
Non-RT RIC Non-RT RIC
O1
O2 O1 O2
A1 A1

near-RT RIC near-RT RIC

O-CU-CP O-CU-CP

O-CU-UP O-CU-UP

F1-c F1-u E2

O-DU O-DU

Open FH Open FH
M-Plane
O-RU O-RU

O-Cloud O-Cloud

rimedolabs.com
O-RAN near-RT RIC

rimedolabs.com
 O-RAN nRIC – Internal Architecture
SMO

Non-RT RIC

A1

near-RT RIC
A1 Termination

xApp 1 xApp 1 … xApp N

merges subscriptions from different
xApps and provides unified data message interaction amongst Near-RT RIC internal
distribution to xApps Messaging Infrastructure functions

xApp
Conflict Mgmt
resolves potentially overlapping or Subscription Security security scheme for the xApps
Mitigation services
conflicting requests from multiple xApps Mgmt

Shared Data Layer • Fault, configuration management, and

R/W of RAN/UE information performance management
E2 Termination • Life-cycle management of xApps
Database • Logging, tracing and metrics collection and
transfer to external system for evaluation

E2

E2 Node(s) rimedolabs.com
Based on defs from: O-RAN Alliance Specifications
 nRT RIC Implementation Options

Centralized near-RT RIC Distributed near-RT RIC

SMO SMO
Non-RT RIC Non-RT RIC

A1 A1 A1 A1 A1 A1

near- near- near- near-

near-RT RIC near-RT RIC RT RIC RT RIC RT RIC RT RIC
One near-RT RIC entity
consisting of one on more
E2 E2 E2 E2 E2 E2 E2 logical near-RT RICs E2 E2 E2 E2

O-CU- O-CU- O-CU- O-CU- O-CU- O-CU-

O-DU O-DU O-eNB O-DU O-eNB
CP UP CP UP CP UP

near-RT RIC serving gNB near-RT RIC serving gNB and eNB

rimedolabs.com
Based on defs from: O-RAN Alliance Specifications
 E2: Key Performance Measurements

5GC

N2 N3

near-RT RIC

E2

O-CU- O-CU-
CP UP

E2 Node E2 Node
O-DU

1. E2 Node provides performance E2 Node

measurement (PM) Reports using „Key 2. Example: O-DU Measurement message:
Performance Measurement” function • PM container carry DL total available PRBs, UL total available PRBs, per PLMN
DU measurement for NG-RAN 5G SA deployment.
• Optional transparent container can be used to carry other cell-related IEs.

rimedolabs.com
Based on: ORAN-WG3.E2SM-KPM-v01.00.00
 E2 KPM – O-DU Measurement for 5G Example
PM Container O-DU PM container

O-DU Measurement Format for 5GC

rimedolabs.com
Source: ORAN-WG3.E2SM-KPM-v01.00.00
O-RAN Use Cases

rimedolabs.com
 O-RAN Use Cases

Low Cost RAN Whitebox Hardware (Impacted: RAN Sharing (Impacted: Non-RT RIC, nRT RIC,
O-DU, O-RU) O-CU, O-DU)

Traffic Steering (Impacted: Non-RT RIC, RAN Slice SLA Assurance (Impacted:
nRT RIC, O-CU) Non-RT RIC, nRT RIC, O-CU, O-DU)

Phase I Phase II
Context Based Dynamic Handover
QoE Optimization (Impacted: Non-RT
Management for V2X (Impacted:
RIC, nRT RIC, O-CU)
Non-RT RIC, nRT RIC, O-CU)

Flight Path Based Dynamic UAV

Massive MIMO Optimization (Impacted:
Resource Allocation (Impacted: Non-RT
Non-RT RIC, nRT RIC, O-CU)
RIC, nRT RIC, O-CU)

Radio Resource Allocation for UAV

QoS Based Resource Optimization (Impacted:
Applications (Impacted: Non-RT RIC, nRT RIC,
Non-RT RIC, nRT RIC, O-CU)
O-CU)

rimedolabs.com
Based on: O-RAN Alliance WP (O-RAN Use Cases and Deployment Scenarios)
O-RAN Traffic Steering Use Case

rimedolabs.com
 O-RAN Traffic Steering – Use Case Description
Challenge:
• Typical TS mechanisms:
• use radio conditions of cell by treating all UEs in the same way with average
values,
• are limited to adjusting the cell reselection, handover parameters, cell priorities.

?
Aims/Objectives:
• Customization of UE-centric strategies and proactive optimization by predicting
network condition
TS – directs traffic • Allow operators to specify different objectives for traffic management: by optimizing
to specific cell(s)
the network/UE performance, achieving balanced cell load, etc.
• Allow operators to flexibly configure desired optimization policies, utilize right
performance criteria, leverage ML to enable intelligent and proactive TS control.

Realization: Required data:

• RIC to control the adaptation of diverse scenarios and objectives. • Measurement reports - RSRP/RSRQ/CQI of serving and neighbor cells, cell quality
• Non-RT RIC and nRT RIC control TS strategies through AI/ML learning thresholds, measurement gaps on per-UE/layer/freq basis, etc.,

from data collected by O1 I/F from O-CU and O-DU • Connection and mobility/HO stats - indication of successful and failed HOs, etc.,
• Cell load stats – # active users/connections, # scheduled active users per TTI, PRB
utilization, etc.,
• Per UE performance stats – PDCP thrpt, RLC/MAC latency, etc.

rimedolabs.com
Based on: O-RAN.WG2.Use-Case-Requirements-v02.00
 O-RAN TS Use Case – Node Responsibilities

• Defines and updates policies - to guide the behavior of TS xApp in nRT RIC (e.g. optimization objectives to
SMO •
guide carrier/band preferences for UE/UE-group)
Performs statistical analysis to provide enrichment info for nRT RIC to assist TS function (e.g., RF fingerprint
based on UE meas. report like RSRP/RSRQ/CQI info for serving/neighboring cells)
Non-RT RIC • Comunicates policies and enrichment info (e.g. RF fingerprints) to nRT RIC & measurement configuration
parameters to RAN nodes.

• A1 policy – declarative policy to enable Non-RT RIC to guide nRT RIC on steering the behavior of RAN fcns
towards stated objectives
• A1 enrichment info – additional info used by nRT RIC collected at SMO/non-RT RIC from non-network data
or from NFs

A1
xApp
TS

• Interprets and enforces policies from Non-RT RIC

Uses enrichment info to optimize control function, e.g., nRT RIC can use RF fingerprint to predict inter-freq
near-RT RIC •
cell measurement based on the intra-freq cell measurement to speed up TS reduced signaling overhead

• Control messages
E2

E2 E2 E2 • Collects and transmits data with required granularity to SMO over O1

Node Node Node • Executes actions

rimedolabs.com
Based on: O-RAN.WG2.Use-Case-Requirements-v02.00
 A1: TS Policies

SMO
Non-RT RIC
A1 Policy can relate to:
• Single/group UE ID
• Slice ID
xApp

• QoS ID
TS

• Cell ID e.g. which cell shall

near-RT RIC be preferred

E2 E2 E2

E2 E2 E2
Node Node Node

rimedolabs.com
Based on: O-RAN.WG2.A1AP-v02.00
 A1: TS Policies Examples

SMO
Non-RT RIC
A1
xApp
TS

near-RT RIC

E2 E2 E2

E2 E2 E2
Node Node Node

rimedolabs.com
Based on: O-RAN.WG2.A1AP-v02.00
 O-RAN TS Use Case Example - Scenario
• Understands requirements of characteristics of services
• Decides:
UE 1: • Voice and CP connection on low band (covered by Cell
• Belong to S-NSSAI=1 B – PCell)
• Have voice connection (5QI=1) • MBB connection preferably on higher band (covered by
• Have MBB connection (5QI=9) small cell C and D – SCells), avoid low bands (Cell A only
• Enters area covered by 4 freq. bands for coverage)
gNB 1:
• Low Bands
gNB 2: • Narrow BW Non-RT RIC
• High Bands • Low Latency
• Wide BW Policies for allocation of CP and UP for
• High Latency different services, identified by 5QI are
A1 sent to any cell of concern, e.g. where the
UE resides and may move

xApp
UE 1

TS
near-RT RIC
Cell D Cell C
Cell B Cell A
E2 E2

E2 E2
Node Node

MBB cells

CP & Voice Cell

rimedolabs.com
Based on: O-RAN.WG2.Use-Case-Requirements-v02.00
 O-RAN TS Use Case – Example Scenario
Non-RT RIC To acheive the behavior, two policies provided via A1

Policy 1: steering voice service to be served by Cell B Policy 2: steering MBB service to be served by Cell C/D

A1
xApp
TS

nRT RIC needs to locate the UE and enforce policy near-RT RIC
rimedolabs.com
Based on: O-RAN.WG2.Use-Case-Requirements-v02.00
 O-RAN TS Use Case – Example Scenario Result

xApp
TS
Near-RT RIC
Control msg for UE1:
• Handover to Cell B (PCell)
E2 • Add Cell A (SCell) for 5QI=1
• Add SCG Cell C (SCell) for 5QI=9
E2
Node

• Cell B: PCell/CP
• Cell A: SCell/Voice

• Cell C: SCell/MBB

Cell D Cell C
Cell B Cell A

MBB cells

CP & Voice Cell

rimedolabs.com
Based on: O-RAN.WG2.Use-Case-Requirements-v02.00
Summary

rimedolabs.com
Using O-RAN Approach

Allows adding intelligence to network with external entities

Allows control of RAN behavior by declarative policies (intents)

Allows combination of various applications to realize objectives

O-RAN
Allows hierarchical and modular approach to resource management

Ends up in allowing flexible and modular RAN

Allows defining RRM applications (xApps) per use case basis

rimedolabs.com
Your trusted partner in: Let’s keep in touch!
LTE, 5G & Beyond, RRM,
Wi-Fi, IoT, O-RAN,
RIMEDO Labs
ul. Polanka 3

Private Mobile Networks.

61-131 Poznan, Poland

info@rimedolabs.com
rimedolabs.com

Marcin Dryjanski
marcin.dryjanski@rimedolabs.com
 Check out our blog! Subscribe to our newsletter!

https://rimedolabs.com/blog https://bit.ly/3rj0DG5
Home - RIMEDO Labs
Who We Are? Dynamic Spectrum Sharing

Radio Resource Management

5G
Wi-Fi Wireless Private Mobile Networks
RIMEDO Labs specializes in providing the best quality
and substantive consulting, implementation and R&D 6G Systems
IoT
services in the field of modern wireless systems. Ultra Dense Networks
LTE
We implement this through an individual and open Novel Wireless Concepts
approach to the client, constantly improving the team
operationally and substantively, updating knowledge
and a unique combination of science and business
applications. #Research
RIMEDO Labs is a spin-off from the Poznan University of #Engineering
#Consulting
Technology, Poland from the Institute of
Radiocommunications.

rimedolabs.com
 Applied Research
The areas of our specialization
cover wireless systems (like LTE,
5G, 6G, IoT, Wi-Fi), spectrum
sharing and management, radio
resource management, AI for
wireless systems and private
mobile networks. We offer our
expertise as part of consortiums
for EU and National funded
projects (like Horizon 2020, Horizon
Europe, NCBR, etc.). We can take
part in those projects as leader,
partner or subcontractor.
Consulting
Having extensive experience in
the field of modern wireless
systems we offer high quality
consulting and advisory services
delivered by our seasoned
engineers and consultants.
RIMEDO Labs Consulting include
cover, among others the following
items: radio planning and site
surveys, technology forecasting,
preparation of feasibility studies,
systems architecting, wireless
systems patent analysis,
standards tracking, or expert/R&D
team outsourcing.
Training
Our training services include
online and on-site courses,
conferences, meetups or
workshops tailored to customer’s
needs and requirements. The
topics, which are covered by us
include: 4G, 5G and beyond, IoT,
Wi-Fi, spectrum management,
radio resource management,
private networks, design, planning
and troubleshooting of wireless
systems, artificial intelligence for
wireless systems. Our top-class
instructors combine scientific and
educational background with
practical experience. We speak
about the systems we design.
Technical Content Delivery
We provide technical contents for
external training or consultancy
companies delivered as training
materials, technical documents,
dedicated research papers,
books, book chapters, slides,
reports or raw materials for
further processing. The material
can be developed as insights
onto a specific feature or aspect
within wireless systems area,
including topics like: LTE, 5G and
beyond, Wi-Fi, IoT, shared
spectrum, AI, etc. The educational
content, can be also delivered in
the form of virtual radio labs.
rimedolabs.com
The information contained herein is the property of RIMEDO and is provided only if it is not disclosed, directly or indirectly to a
third party, or used for purposes other than those for which it was prepared.

ETSI is the copyright holder of LTE, LTE-Advanced and LTE Advanced Pro and 5G Logos. LTE is a trade mark of ETSI. RIMEDO is
authorized to use the LTE, LTE-Advanced, LTE-Advanced Pro and 5G logos and the acronym LTE.

All information discussed in the document is provided "as is" and RIMEDO makes no warranty that this information is fit for
purpose. Users use this information at their own risk and responsibility.

© 2021 RIMEDO sp. z o.o. All rights reserved.