ETSI TS 103 648 V1.1.1 (2020-01)

Reconfigurable Radio Systems (RRS); Radio Equipment (RE) reconfiguration architecture

DTS/RRS-0221

General Information

• Status: Published
• Publication Date: 13-Jan-2020
• Technical Committee: RRS 2 - REA - Reconfigurable Radio Equipment Architecture
• Current Stage: 12 - Completion
• Due Date: 08-Jan-2020
• Completion Date: 14-Jan-2020

Standards Content (Sample)

TECHNICAL SPECIFICATION
Reconfigurable Radio Systems (RRS);
Radio Equipment (RE) reconfiguration architecture

2 ETSI TS 103 648 V1.1.1 (2020-01)

Reference
DTS/RRS-0221
Keywords
architecture, radio, SDR
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
The present document can be downloaded from:
http://www.etsi.org/standards-search
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI
deliverable is the one made publicly available in PDF format at www.etsi.org/deliver.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© ETSI 2020.
All rights reserved.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.

3GPP™ and LTE™ are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and
of the oneM2M Partners. ®
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI
3 ETSI TS 103 648 V1.1.1 (2020-01)
Contents
Intellectual Property Rights . 5
Foreword . 5
Modal verbs terminology . 5
1 Scope . 6
2 References . 6
2.1 Normative references . 6
2.2 Informative references . 6
3 Definition of terms, symbols and abbreviations . 7
3.1 Terms . 7
3.2 Symbols . 9
3.3 Abbreviations . 9
4 Architectural Reference Model for Reconfigurable Radio Equipment . 11
4.1 Introduction . 11
4.2 Reconfigurable Radio Equipment - Architecture Components for Radio Reconfiguration . 11
4.2.1 High level description . 11
4.2.2 Communication Services Layer (CSL) . 13
4.2.3 Radio Control Framework (RCF) . 15
4.2.4 Unified Radio Application (URA) . 16
4.2.5 Architectural Components System Requirements mapping . 16
4.3 Reconfigurable Radio Equipment - Architecture Reference Model for Multiradio Applications . 17
4.3.1 High level description . 17
4.3.2 Reference Model System Requirements mapping . 18
4.4 Reconfigurable Radio Equipment - radio computer . 18
4.4.1 High level description . 18
4.4.2 radio computer System Requirement Mapping. 20
4.5 Reconfigurable Radio Equipment - the Radio Virtual Machine . 20
4.5.1 Radio Virtual Machine basic principles . 20
4.5.2 RVM System Requirement Mapping . 21
4.6 Reconfigurable Radio Equipment - Unified Radio Applications . 21
4.6.1 Introduction. 21
4.6.2 Distribution and Installation of RAP . 21
4.6.3 Operational Structure of URA . 25
4.6.4 URA System Requirement Mapping . 28
4.7 Security architecture for reconfigurable Radio Equipment . 29
4.7.1 Description . 29
4.7.2 Security Components System Requirements mapping . 30
5 Reference Points . 31
5.1 Introduction . 31
5.2 Reference Points required for Installation/uninstallation and creating/deleting an instance of a URA . 32
5.3 Reference Points required for list checking of URA . 32
5.3.1 Reference Points required for updating instance of URA . 33
5.3.2 Reference Points required for configuring URA parameters . 33
5.4 Reference Points required for activation/deactivation of URA . 34
5.5 Reference Points required for transferring context information . 34
5.6 Reference Points required for creating data flow and sending/receiving user data . 35
5.7 Reference Points required for radio environment measurements . 36
5.8 Reference Points required for reporting discovered peer equipment . 36
5.9 Reference Points required for flexible data flow . 37
5.10 Reference Points required for data flow control . 37
5.11 Reference Points required for synchronizing radio time . 38
5.12 Reference Points required for control of reconfigurable RF transceiver . 38
5.13 Reference points required for security functions . 39
6 Reconfigurable RE high level operating procedures . 41
6.0 Introduction . 41
ETSI
4 ETSI TS 103 648 V1.1.1 (2020-01)
6.1 Procedures for installation/uninstallation and creating/deleting instance of a URA . 41
6.2 Procedures for list checking of URA . 45
6.2.1 Procedures for updating instance of URA . 46
6.2.2 Procedures for configuring URA parameters . 49
6.3 Procedures for activation/deactivation of URA . 50
6.4 Procedures for transferring context information . 51
6.5 Procedure for creating data flow and sending/receiving user data . 53
6.6 Procedures for radio environment measurements . 58
6.7 Procedure for reporting discovered peer equipment . 59
6.8 Procedure for flexible data flow . 59
6.9 Procedure for data flow control . 60
6.10 Procedure for synchronizing radio time . 62
6.11 Procedure for control of reconfigurable RF transceiver . 63
6.12 Procedure for RE Configuration Policy endorsement, distribution and validation . 71
6.13 Procedure for configuration enforcement . 73
6.14 Procedures for long-term management . 75
Annex A (informative): Distributed Computations on Multiple radio computers . 81
A.0 Introduction . 81
A.1 Procedures of RA Distributed Installation on Multiple radio computers . 81
History . 82

ETSI
5 ETSI TS 103 648 V1.1.1 (2020-01)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (https://ipr.etsi.org/).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
Foreword
This Technical Specification (TS) has been produced by ETSI Technical Committee Reconfigurable Radio Systems
(RRS).
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.

ETSI
6 ETSI TS 103 648 V1.1.1 (2020-01)
1 Scope
The scope of the present document is to define the radio reconfiguration related architecture for reconfigurable Radio
Equipment. The work is based on the system requirements defined in ETSI TS 103 641 [1] and the Use Cases defined
in ETSI TR 103 062 [i.1], ETSI TR 102 944 [i.2] and ETSI TR 103 585 [i.3].
2 References
2.1 Normative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found at
https://docbox.etsi.org/Reference.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are necessary for the application of the present document.
[1] ETSI TS 103 641: "Reconfigurable Radio Systems (RRS); Radio Equipment (RE) reconfiguration
requirements".
2.2 Informative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are not necessary for the application of the present document but they assist the
user with regard to a particular subject area.
[i.1] ETSI TR 103 062: "Reconfigurable Radio Systems (RRS) Use Cases and Scenarios for Software
Defined Radio (SDR) Reference Architecture for Mobile Device".
[i.2] ETSI TR 102 944: "Reconfigurable Radio Systems (RRS); Use Cases for Baseband Interfaces for
Unified Radio Applications of Mobile Device".
[i.3] ETSI TR 103 585: "Reconfigurable Radio Systems (RRS); Radio Equipment (RE) reconfiguration
use cases".
[i.4] ETSI EN 303 095: "Reconfigurable Radio Systems (RRS); Radio reconfiguration related
architecture for Mobile Devices (MD)".
[i.5] Recommendation ITU-T M.60: "Maintenance Terminology and Definitions".
[i.6] ETSI TS 103 436: "Reconfigurable Radio Systems (RRS); Security requirements for
reconfigurable radios".
[i.7] ETSI TR 103 087: "Reconfigurable Radio Systems (RRS); Security related use cases and threats".
[i.8] Directive 2014/53/EU of the European Parliament and of the Council of 16 April 2014 on the
harmonisation of the laws of the Member States relating to the making available on the market of
Radio Equipment and repealing Directive 1999/5/EC.
ETSI
7 ETSI TS 103 648 V1.1.1 (2020-01)
3 Definition of terms, symbols and abbreviations
3.1 Terms
For the purposes of the present document, the following terms apply:
Baseband Parameter Aggregation (BPA): unit collecting all the context information to be transferred to the monitor
NOTE: The BPA unit converts the context information into metric(s) such that a minimum bandwidth is
consumed during the procedure of transferring the context information to the monitor. Those metrics may
include Received Signal Strength Indication (RSSI) measurement, multi-RAT performance metrics, etc.
broadcast identifier (broadcast ID): identifier linking a data packet to all available radio computers
Communication Services Layer (CSL): layer related to communication services supporting generic applications
NOTE: A communication services layer supports generic applications like Internet access. In the present
document, it consists of Administrator, Mobility Policy Manager (MPM), Networking stack and Monitor.
computational resources: part of Radio Equipment hardware working under OS control and on which Applications,
among others, are executed
configcodes: result of compiling the source codes of a Radio Application (RA), which is either configuration codes of
Radio Virtual Machine (RVM) or executable codes for a particular target platform
NOTE: In the case when RA provider makes a high level code based on a target platform, a result of compiling
RA source codes is configcodes which is executable on the target platform. In the other case, when RA
provider makes a high level code without considering a target platform, a result of front-end compiling of
RA source codes is an Intermediate Representation (IR) which should be back-end compiled for operating
on a specific target platform.
data flow: logical channel between Flow Controller (FC) and an Unified Radio Applications (URA) created by FC to
send to or receive data elements (octets, packets or other granularity) from URA
distributed computations: computational model in which components located on networked computers communicate
and coordinate their actions by passing messages interacting with each other in order to achieve a common goal
environmental information: set of values that can affect the execution of RAs on a radio computer
NOTE: Environmental Information consists of information related to the execution of RA(s), such as Buffer
Overflow, Resource Allocation, etc.
Functional Block (FB): function needed for real-time implementation of RA(s)
NOTE 1: A functional block includes not only the modem functions in Layer1 (L1), Layer2 (L2), and Layer 3 (L3)
but also all the control functions that should be processed in real-time for implementing given RA(s).
NOTE 2: Functional blocks are categorized into Standard Functional Blocks (SFBs) and User Defined Functional
Blocks (UDFBs). In more details:
1) SFB can be shared by many RAs. For example, Forward Error Correction (FEC), Fast Fourier
Transform (FFT)/Inverse Fast Fourier Transform (IFFT), (de)interleaver, Turbo coding, Viterbi
coding, Multiple Input Multiple Output (MIMO), Beamforming, etc. are the typical category of
standard functional block.
2) UDFB include those functional blocks that are dependent upon a specific RA. They are used to
support special function(s) required in a specific RA or to support a special algorithm used for
performance improvement. In addition, a user defined functional block can be used as a baseband
controller functional block which controls the functional blocks operating in baseband processor in
real-time and to control some context information processed in real-time.
NOTE 3: Each functional block has its unique name, Input, Output and properties.
ETSI
8 ETSI TS 103 648 V1.1.1 (2020-01)
multicast identifier (multicast ID): identifier linking a data packet to a group of radio computers
NOTE: A group of radio computers consists of at least two radio computers. The way for implementing the radio
computer grouping is the choice of the manufacturers.
peer equipment: any communication counterpart of a reconfigurable Radio Equipment
NOTE: The peer equipment can be reached by establishing a (logical) communications link (i.e. an association)
between the reconfigurable Radio Equipment and peer equipment. Examples of peer equipment include
Wide Local Area Network (WLAN) access points, Internet Protocol (IP) access nodes, etc.
Radio Application (RA): software which enforces the generation of the transmit RF signals or the decoding of the
receive RF signals
NOTE 1: The Software is executed on a particular radio platform or an RVM as part of the radio platform.
NOTE 2: RAs might have different forms of representation. They are represented as:
 Source codes including Radio Library calls of Radio Library native implementation and Radio
HAL calls.
 IRs including Radio Library calls of Radio Library native implementation and radio HAL calls.
 Executable codes for a particular radio platform.
radio computer: part of Radio Equipment working under ROS control and on which RAs are executed
NOTE 1: A radio computer typically includes programmable processors, hardware accelerators, peripherals,
software, etc. RF part is considered to be part of peripherals.
NOTE 2: The Radio Platform is the hardware part of the radio computer.
Radio Control Framework (RCF): control framework which, as a part of the OS, extends OS capabilities in terms of
radio resource management
NOTE: RCF is a control framework which consists of Configuration Manager (CM), Radio Connection Manager
(RCM), Flow Controller (FC) and Multiradio Controller (MRC). The Resource Manager (RM) is
typically part of OS.
Radio Controller (RC): functional component of RA for transferring context information from corresponding RAs to
monitor
NOTE: A RC, which may operate in computational resources in non real-time, accesses RAs which operates in
radio computer in real time. The monitor, to which the context information is transferred using RC,
provides context information to Administrator and/or Mobility Policy Manager (MPM) for application(s)
to be performed using the context information, for example, terminal-centric configuration.
Radio Equipment (RE): As defined in the Radio Equipment Directive, Article 2(1)(1) [i.8].
NOTE: Excerpt from the Radio Equipment Directive: "'radio equipment' means an electrical or electronic
product, which intentionally emits and/or receives radio waves for the purpose of radio communication
and/or radiodetermination, or an electrical or electronic product which must be completed with an
accessory, such as antenna, so as to intentionally emit and/or receive radio waves for the purpose of
radio communication and/or radiodetermination".
radio frequency transceiver (RF transceiver): part of Radio Platform converting, for transmission, baseband signals
into radio signals, and, for reception, radio signals into baseband signals
radio library: library of SFB that is provided by a platform vendor in a form of platform-specific executable code
NOTE 1: SFBs implement reference codes of functions which are typical for radio signal processing. They are not
atomic and their source codes are typed and visible for RA developers.
NOTE 2: A SFB is implemented through a Radio Hardware Abstraction Layer (HAL) when the SFB is
implemented on hardware accelerators. Radio HAL is part of ROS.
ETSI
9 ETSI TS 103 648 V1.1.1 (2020-01)
Radio Operating System (ROS): any appropriate OS empowered by RCF
NOTE: ROS provides RCF capabilities as well as traditional management capabilities related to management of
RP such as resource management, file system support, unified access to hardware resources, etc.
radio platform: part of Radio Equipment hardware which relates to radio processing capability, including
programmable hardware components, hardware accelerators, RF transceiver and antenna(s)
NOTE 1: A Radio Platform is a piece of hardware capable of generating RF signals or receiving RF signals,
including Base-Band and RF processing. By nature, it is heterogeneous hardware including different
processing elements such as fixed accelerators, e.g. Application-Specific Integrated Circuit (ASIC), or
reconfigurable accelerators, e.g. FPGAs, etc.
NOTE 2: In case of multiple radio computers, there is an independent Radio Platform for each of the radio
computers.
radio reconfiguration: reconfiguration of parameters related to air interface
Radio Virtual Machine (RVM): abstract machine which supports reactive and concurrent executions
NOTE: A RVM may be implemented as a controlled execution environment which allows the selection of a
trade-off between flexibility of base band code development and required (re-)certification efforts.
reconfigurable Radio Equipment: Radio Equipment with radio communication capabilities providing support for
radio reconfiguration
NOTE: Reconfigurable Radio Equipment includes Smartphones, Feature phones, Tablets, Laptops, Connected
Vehicle communication platform, Network platform, IoT device, etc.
reference point: conceptual point at the conjunction of two non-overlapping functions that can be used to identify the
type of information passing between these functions
NOTE: This definition is introduced by Recommendation ITU-T M.60 [i.5].
routing entity: entity which directs network packets from their source toward their destination through intermediate
network nodes by specific packet forwarding mechanisms
NOTE 1: In the present document, source and destination relate either to CSL or radio computers.
NOTE 2: The directing of packets may include decision making and physical routing.
shadow radio platform: platform where configcodes can be directly executed when it corresponds to the target radio
platform or, when it corresponds to an RVM, compiled and executed
NOTE: If the shadow radio platform is equivalent to the target radio platform, then a front-end compiler will
generate the executable code for the target radio platform and configcodes are equivalent to the
executable code for that radio platform.
unicast identifier (unicast ID): identifier linking a data packet to a specific radio computer
Unified Radio Application (URA): Radio Application which complies with the reconfigurable RE framework defined
in the present document
3.2 Symbols
For the purposes of the present document, the following symbols apply:
M Number of SFBs implemented on Radio computer
M Number of SFBs implemented on hardware accelerators
3.3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
AOT Ahead-Of-Time
ETSI
10 ETSI TS 103 648 V1.1.1 (2020-01)
API Application Programming Interface
ASF Administrator Security Function
ASIC Applications-Specific Integrated Circuit
BBU BaseBand Unit
BE Back End
BPA Baseband Parameter Aggregation
CII Context Information Interface
CM Configuration Manager
C-RAN Cloud-Radio Access Network
CSL Communication Services Layer
FC Flow Controller
FEC Forward Error Correction
FFT Fast Fourier Transform
FM File Manager
FPGA Field Programmable Gate Array
GGSN Gateway GPRS Support Node
gMURI generalized MUltiRadio Interface
gRPI generalized Radio Programming Interface
gRRFI generalized Reconfigurable Radio Frequency Interface
gURAI generalized Unified Radio Applications Interface
GPRS General Packet Radio Service
GPS Global Positioning System
HAL Hardware Abstraction Layer
HW HardWare
ICIC Inter-Cell Interference Coordination
ID IDentification
IFFT Inverse Fast Fourier Transform
IP Internet Protocol
IR Intermediate Representation
JIT Just-In-Time
KMS Key Management System
MAC Medium Access Control
MIMO Multi-Input-Multi-Output
MPM Mobility Policy Manager
MRC MultiRadio Controller
MURI MUltiRadio Interface
OEM Original Equipment Manufacturer
OS Operating System
RA Radio Application
RAN Radio Access Network
RAP Radio Application Package
RAT Radio Access Technology
RC Radio Controller
RCF Radio Control Framework
RCM Radio Connection Manager
RE Radio Equipment
RERC Radio Equipment Reconfiguration Class
RF Radio Frequency
RM Resource Manager
ROS Radio Operating System
RPI Radio Programming Interface
RRFI Reconfigurable Radio Frequency Interface
RRH Remote Radio Head
RRS-CM RRS Configuration Manager
RRS-CP RRS Configuration Provider
RVM Radio Virtual Machine
SDN Software-Defined Networking
SDR Software Defined Radio
SFB Standard Functional Block
SW SoftWare
TAD Transfer of Authority Document
TX/RX Transmission/Reception
ETSI
11 ETSI TS 103 648 V1.1.1 (2020-01)
UDFB User Defined Functional Block
URA Unified Radio Applications
URAI Unified Radio Applications Interface
WLAN Wireless Local Area Network
4 Architectural Reference Model for Reconfigurable
Radio Equipment
4.1 Introduction
The present deliverable describes those elements of a Radio Equipment which is related to the software radio
reconfiguration only. For this reason, the usage of the term "architecture" is limited to those elements and not to the
overall HW/SW architecture of a Radio Equipment which is out of the scope of the present document.
The present document is organized as follows:
• Clause 4.2 describes the reconfigurable Radio Equipment architecture in term of its components and entities.
• Clause 4.3 describes the architecture reference model for multiradio applications.
• Clause 4.4 describes the "radio computer".
• Clause 4.5 describes the Radio Virtual Machine as part of the architecture.
• Clause 4.6 describes the Unified Radio Application.
• Clause 4.7 describes the security architecture for reconfigurable Radio Equipment.
• Clause 5 describes the (logical) interfaces between the identified components/entities.
• Clause 6 lists the operating procedures of a reconfigurable Radio Equipment.
• Clause 4 includes a list of Tables mapping the system requirements as defined in [1] to the different
entities/components/units which have been identified. In general, according to the Radio Equipment
Reconfiguration Class (RERC) [1], all the related mandatory functional requirements described in [1] shall be
implemented.
4.2 Reconfigurable Radio Equipment - Architecture
Components for Radio Reconfiguration
4.2.1 High level description
Figure 4.2.1-1 shows the reconfigurable Radio Equipment architectural components related to the radio reconfiguration
as well as the related entities. The main difference between the mobile device architecture [i.4] and the generalized
Radio Equipment architecture defined in the present document is that a mobile device includes only one radio
computer, while the generalized Radio Equipment may include one or more radio computers. As shown in
Figure 4.2.1-1, the following components can be identified:
• Communication Services Layer (CSL):
- 4 logical entities: Administration, Mobility Policy Manager, Networking Stack and Monitor.
• Radio Control Framework (RCF):
- 5 logical entities: Configuration Manager, Radio Connection Manager, Multi-Radio Controller, Resource
Manager and Flow Controller.
• Unified Radio Applications (URA).
• Radio Platform (consisting of RF transceiver(s), Baseband(s), etc.).
ETSI
12 ETSI TS 103 648 V1.1.1 (2020-01)
NOTE: When the Radio Platform consists of multiple baseband processors and/or RF transceivers, the
reconfigurable Radio Equipment architecture supports the computational/spectral load balancing.
These 4 components consist of Software (CSL, RCF) and/or Hardware (Radio Platform) entities and they shall be
interconnected through well-defined interfaces as follows:
• Generalized Multiradio Interface (gMURI) between CSL and RCF.
• Generalized Unified Radio Application Interface (gURAI) between RCF and URA.
• Generalized Reconfigurable Radio Frequency Interface (gRRFI) between URA and RF transceiver(s).
The above mentioned interfaces are not covered by the present document.

NOTE: Interfaces gMURI, gURAI and gRRFI in Figure 4.2.1-1 are used to interconnect components of different
stakeholders.
Figure 4.2.1-1: Reconfigurable Radio Equipment Architecture Components for Radio Reconfiguration
For each components, the required entities depend on the RERC [1]. A Reconfigurable Radio Equipment shall support
all the components and their entities as required by the corresponding RERC as shown in Table 4.2.1-1. In case that a
Reconfigurable Radio Equipment supports multiple RERCs, the concerned Reconfigurable Radio Equipment shall
support all the components and entities related to the highest supported RERC.
Table 4.2.1-1: Required Components of the Reconfigurable Radio Equipment Architecture
in function of the Radio Equipment Reconfiguration Class
Radio Equipment
Reconfiguration Required CSL Entities Required RCF Entities Interfaces
Class
RERC-0 None None None
RERC-1 Administrator, Mobility Policy Configuration Manager, Radio gMURI
Manager, Networking Stack, Connection Manager, Flow
Monitor Controller
RERC-2, RERC-5 Administrator, Mobility Policy Configuration Manager, Radio gMURI, gURAI, gRRFI
Manager, Networking Stack, Connection Manager, Multi-
Monitor Radio Controller, Flow
Controller
RERC-3, RERC-6 Administrator, Mobility Policy Configuration Manager, Radio gMURI, gURAI, gRRFI
Manager, Networking Stack, Connection Manager, Multi-
Monitor Radio Controller, Flow
Controller
RERC-4, RERC-7 Administrator, Mobility Policy Configuration Manager, Radio gMURI, gURAI, gRRFI
Manager, Networking Stack, Connection Manager, Multi-
Monitor Radio Controller, Resource
Manager, Flow Controller
The following clauses describe in more details the identified components as well as the related logical entities.
ETSI
13 ETSI TS 103 648 V1.1.1 (2020-01)
4.2.2 Communication Services Layer (CSL)
The CSL is a layer related to communication services providing multiradio and non-radio functionalities. The typical
examples of communication services related to multiradio functionalities are management for activating corresponding
radio application or controlling data flows for each radio application. The typical example of communication services
related to non-radio functionalities is Internet access using TCP (Transmission Control Protocol) and IP (Internet
Protocol). A Radio Equipment shall support one or multiple radio computers. The CSL shall assign a Unicast ID,
Multicast ID or Broadcast ID which is linking a data packet to a specific radio computer, a group of radio computers or
all available radio computers respectively.
NOTE 1: In the present document, the scope of applications has been extended from Mobile Devices [i.4] to Radio
Equipment including one or multiple radio computers. Consequently, the assignment of a Unicast ID,
Multicast ID or Broadcast ID is added in the present document. In the case of [i.4], such IDs were not
required, because only a single radio computer is supported.
The CSL shall be interconnected with all radio computers through a routing entity.
NOTE 2: The implementation of the routing entity and its interfaces is the choice of the manufacturer and thus out
of scope of the present document.
Figure 4.2.2-1 is a conceptual diagram showing the routing of the CSL data packets to the corresponding radio
computer (and vice versa, i.e. from radio computer to CSL) in the case of unicast. The routing entity interprets the
Unicast ID and forwards the data packets from the CSL to the corresponding radio computer (i.e. address translation is
performed) and vice versa (i.e. from radio computer to CSL).
Figure 4.2.2-2 is a conceptual diagram showing the routing of the CSL data packets to the corresponding radio
computers in the case of multicast. The routing entity interprets the multicast ID and forwards the data packets from the
CSL to the corresponding radio computers (i.e. address translation is performed). For the reverse link (i.e. from
radio computer to CSL), unicast is applied.
Figure 4.2.2-3 is a conceptual diagram showing the routing of the CSL data packets to the corresponding radio
computers in the case of broadcast. The routing entity interprets the broadcast ID and forwards the data packets from
the CSL to the all available radio computers. For the reverse link (i.e. from radio computer to CSL), unicast is applied.

Figure 4.2.2-1: Conceptual diagram showing the routing of the CSL message(s) to the corresponding
radio computer(s) and the routing of each radio computer's information to the CSL in the case of
unicast transmission
ETSI
14 ETSI TS 103 648 V1.1.1 (2020-01)

Figure 4.2.2-2: Conceptual diagram showing the routing of the CSL message(s) to the corresponding
radio computer(s) in the case of multicast transmission

Figure 4.2.2-3: Conceptual diagram showing the routing of the CSL message(s) to the corresponding
radio computer(s) in the case of broadcast transmission
ETSI
15 ETSI TS 103 648 V1.1.1 (2020-01)
CSL includes the following 4 entities:
• Administrator entity
- The Administrator entity shall include at least functions to request installation or uninstallation of URA,
and creating or deleting instances of URA. This should include the provision of information about the
URA, their status, etc. In addition, the Administrator entity shall include two sub-entities:
 the Administrator Security Function (ASF); and
 the RRS Configuration Manager (RRS-CM).
NOTE 1: In case that a snapshot function is required, the Administrator entity may store relevant RAPs, their
configuration parameters and information on the URA installation and execution history. When required,
the same steps can be executed by the Administrator entity to fall back to a previous snapshot.
• Mobility Policy Manager (MPM) entity
- The MPM shall include at least functions for monitoring of the radio environments and RE capabilities,
to request activation or deactivation of URA, and to provide information about the URA list. It shall also
make selection among different radio access technologies and discover peer communication equipment
and arrangement of associations. In addition, the MPM may request a computational/spectral load
balancing among baseband processors and RF transceivers in radio platform when the number of
baseband processors and RF transceivers in radio platform exceeds one.
NOTE 2: The additional functionality regarding load balancing is required, e.g. in the case of distributed
computations.
- Explanation: The requirement for computational and/or spectral resources varies depending on the
situation of each base station in the case of network application. For example, the required traffic of each
base station can rapidly and unexpectedly vary due to natural disasters, sports games, accidents, etc.
- Explanation: When the reconfigurable Radio Equipment is shared with multiple stakeholders,
e.g. multiple network operators share a single network infrastructure; the policy of using both
computational and spectral resources may have to be controlled for a desired performance requirement at
each operation.
• Networking stack entity
- The Networking stack entity shall include at least functions for sending and receiving of user data.
- The Networking stack entity shall translate the radio computer ID to a target network address and vice
versa.
• Monitor entity
- The Monitor entity shall include at least functions to transfer information from URA to user or proper
destination entity in RE. In addition, in case that distributed computation is applied, the Monitor shall
receive the computational/spectral resource usage status.
4.2.3 Radio Control Framework (RCF)
The RCF provides a generic environment for the execution of URA, and a uniform way of accessing the functionality of
the radio computer and individual RAs. RCF provides services to CSL via the generalized Multiradio Interface
(gMURI).
The RCF includes the following 5 entities for managing URA [i.2]:
• Configuration Manager (CM) entity
- The CM shall include at least functions for installing/uninstalling and creating/deleting instances of URA
as well as management of and access to the radio parameters of the URA.
ETSI
16 ETSI TS 103 648 V1.1.1 (2020-01)
• Radio Connection Manager (RCM) entity
- The RCM shall include at least functions for activating/deactivating URA according to user requests, and
to management of user data flows, which can also be switched from one RA to another.
• Flow Controller (FC) entity
- The FC shall include at least functions for sending and receiving of user data packets and controlling the
flow of signalling packets.
• Multiradio Controller (MRC) entity
- The MRC shall include at least functions to schedule the requests for radio resources issued by
concurrently executing URA, and to detect and manage the interoperability problems among the
concurrently executed URA. In addition, in case that distributed computation is applied, the MRC shall
include a function to report spectral resource usage status.
• Resource Manager (RM) entity
- The RM shall include at least functions to manage the computational resources, to share them among
simultaneously active URA, and to guarantee their real-time execution. In addition, in case that
distributed computation is applied, RM shall include a function to report computational resource usage
status.
4.2.4 Unified Radio Application (URA)
As described in clause 4.2.3, the RCF, which represents functionalities provided by the radio computer, requires all RAs
to be subject to a common reconfiguration, multiradio execution and resource sharing strategy framework (depending
on the concerned RERC). Since all RAs exhibit a
...