SIST EN 303 681-2 V1.1.2:2020
(Main)Reconfigurable Radio Systems (RRS) - Radio Equipment (RE) information models and protocols for generalized software reconfiguration architecture - Part 2: generalized Reconfigurable Radio Frequency Interface (gRRFI)
Reconfigurable Radio Systems (RRS) - Radio Equipment (RE) information models and protocols for generalized software reconfiguration architecture - Part 2: generalized Reconfigurable Radio Frequency Interface (gRRFI)
The present document defines an information model and protocol for generalized reconfigurable radio frequency
interface for reconfigurable REs except for reconfigurable mobile devices which are covered in [i.7] to [i.12]. The work
is based on the Use Cases defined in ETSI TR 103 585 [i.1], on the system requirements defined in ETSI
EN 303 641 [1] and on the radio reconfiguration related architecture for reconfigurable RE defined in ETSI
EN 303 648 [i.2].
The present document will be based on ETSI EN 303 146-2 [i.10] and provide a generalized interface definition for the
generalized Reconfigurable Radio Frequency Interface.
Radijski sistemi z možnostjo preoblikovanja (RRS) - Informacijski modeli in protokoli za radijsko opremo (RE) za splošno arhitekturo preoblikovanja programske opreme - 2. del: Splošni spremenljivi radiofrekvenčni vmesnik (gRRFI)
General Information
Standards Content (Sample)
Draft ETSI EN 303 681-2 V1.1.2 (2020-03)
EUROPEAN STANDARD
Reconfigurable Radio Systems (RRS);
Radio Equipment (RE) information models and protocols
for generalized software reconfiguration architecture;
Part 2: generalized Reconfigurable
Radio Frequency Interface (gRRFI)
2 Draft ETSI EN 303 681-2 V1.1.2 (2020-03)
Reference
REN/RRS-0229
Keywords
interface, radio, SDR
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
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 Draft ETSI EN 303 681-2 V1.1.2 (2020-03)
Contents
Intellectual Property Rights . 4
Foreword . 4
Modal verbs terminology . 4
1 Scope . 5
2 References . 5
2.1 Normative references . 5
2.2 Informative references . 5
3 Definition of terms, symbols and abbreviations . 6
3.1 Terms . 6
3.2 Symbols . 8
3.3 Abbreviations . 8
4 Introduction . 8
5 System Identification . 10
5.1 Radio Computer Structure . 10
5.2 URA . 12
5.3 RF Transceiver . 12
5.4 RF Interfaces . 12
5.5 Radio Computer RF System Requirement Mapping . 12
6 Notational Tools . 13
6.1 Notational Tool for Information Model Classes . 13
6.2 Notational Tool for Interface Classes . 13
7 Information Model for Radio Computer . 13
7.1 Radio Computer . 13
7.2 Class Definitions for Information Model . 16
8 Interface Definition . 21
8.1 Interface Overview . 21
8.2 Spectrum Control Services . 24
8.2.1 Overview on Spectrum Control Services . 24
8.2.2 Messages for Spectrum Control Services . 24
8.3 Power Control Services . 25
8.3.1 Overview on Power Control Services . 25
8.3.2 Messages for Power Control Services . 25
8.4 Antenna Management Services . 25
8.4.1 Overview on Antenna Management Services . 25
8.4.2 Messages for Antenna Management Services. 26
8.5 Tx/Rx Chain Control Services. 26
8.5.1 Overview on Tx/Rx Chain Control Services . 26
8.5.2 Messages for Tx/Rx Chain Control Services . 26
8.6 RVM Protection Services . 27
8.6.1 Overview on RVM Protection Services . 27
8.6.2 Messages for RVM Protection Services . 28
8.7 Class Definitions for Interface . 28
Annex A (informative): Abstract Data Definitions . 31
Annex B (informative): gRRFI Qualification Methods for Validation . 35
History . 36
ETSI
4 Draft ETSI EN 303 681-2 V1.1.2 (2020-03)
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 draft European Standard (EN) has been produced by ETSI Technical Committee Reconfigurable Radio Systems
(RRS), and is now submitted for the combined Public Enquiry and Vote phase of the ETSI standards EN Approval
Procedure.
The present document is part 2 of a multi-part deliverable covering the Radio Equipment (RE) information models and
protocols, as identified below:
Part 1: "generalized Multiradio Interface (gMURI)";
Part 2: "generalized Reconfigurable Radio Frequency Interface (gRRFI)";
Part 3: "generalized Unified Radio Application Interface (gURAI)";
Part 4: "generalized Radio Programming Interface (gRPI)".
Proposed national transposition dates
Date of latest announcement of this EN (doa): 3 months after ETSI publication
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 6 months after doa
Date of withdrawal of any conflicting National Standard (dow): 6 months after doa
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
5 Draft ETSI EN 303 681-2 V1.1.2 (2020-03)
1 Scope
The present document defines an information model and protocol for generalized reconfigurable radio frequency
interface for reconfigurable REs except for reconfigurable mobile devices which are covered in [i.7] to [i.12]. The work
is based on the Use Cases defined in ETSI TR 103 585 [i.1], on the system requirements defined in ETSI
EN 303 641 [1] and on the radio reconfiguration related architecture for reconfigurable RE defined in ETSI
EN 303 648 [i.2].
The present document will be based on ETSI EN 303 146-2 [i.10] and provide a generalized interface definition for the
generalized Reconfigurable Radio Frequency Interface.
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 EN 303 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 585: "Reconfigurable Radio Systems (RRS); Radio Equipment (RE) reconfiguration
use cases".
[i.2] ETSI EN 303 648: "Reconfigurable Radio Systems (RRS); Radio Equipment (RE) reconfiguration
architecture".
[i.3] IEEE 1900.4™-2009: "IEEE Standard for Architectural Building Blocks Enabling Network-
Device Distributed Decision Making for Optimized Radio Resource Usage in Heterogeneous
Wireless Access Networks". ®
[i.4] DigRFSM Working Group: "MIPI Alliance Specification for DigRFSM v4".
[i.5] Recommendation ITU-T X.680: "Information technology - Abstract Syntax Notation One
(ASN.1): Specification of basic notation".
[i.6] 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
6 Draft ETSI EN 303 681-2 V1.1.2 (2020-03)
[i.7] ETSI EN 302 969: "Reconfigurable Radio Systems (RRS); Radio Reconfiguration related
Requirements for Mobile Devices".
[i.8] ETSI EN 303 095: "Reconfigurable Radio Systems (RRS); Radio reconfiguration related
architecture for Mobile Devices (MD)".
[i.9] ETSI EN 303 146-1: "Reconfigurable Radio Systems (RRS); Mobile Device (MD) information
models and protocols; Part 1: Multiradio Interface (MURI)".
[i.10] ETSI EN 303 146-2: "Reconfigurable Radio Systems (RRS); Mobile Device (MD) information
models and protocols; Part 2: Reconfigurable Radio Frequency Interface (RRFI)".
[i.11] ETSI EN 303 146-3: "Reconfigurable Radio Systems (RRS); Mobile Device (MD) information
models and protocols; Part 3: Unified Radio Application Interface (URAI)".
[i.12] ETSI EN 303 146-4: "Reconfigurable Radio Systems (RRS); Mobile Device (MD) information
models and protocols; Part 4: Radio Programming Interface (RPI)".
[i.13] ETSI EN 303 681-1: "Reconfigurable Radio Systems (RRS); Radio Equipment (RE) information
models and protocols for generalized software reconfiguration architecture; Part 1: generalized
Multiradio Interface (gMURI)".
[i.14] ETSI EN 303 681-3: "Reconfigurable Radio Systems (RRS); Radio Equipment (RE) information
models and protocols for generalized software reconfiguration architecture; Part 3: generalized
Unified Radio Application Interface (gURAI)".
[i.15] ETSI EN 303 681-4: "Reconfigurable Radio Systems (RRS); adio Equipment (RE) information
models and protocols for generalized software reconfiguration architecture; Part 4: generalized
Radio Programming Interface (gRPI)".
3 Definition of terms, symbols and abbreviations
3.1 Terms
For the purposes of the present document, the following terms apply:
association: logical communication link to a Radio Access Network or a peer equipment
NOTE 1: Typically, some control signalling is necessary to maintain the association. No user data transfer may
occur with only an association present, but a data flow may be established into an association for this
purpose.
NOTE 2: Peer equipment is any communication counterpart of a reconfigurable Radio Equipment. It can be
reached by establishing a logical communication link (i.e. an association) between the reconfigurable
Radio Equipment and peer equipment.
channel: designated part of the information transfer capability having specified characteristics, provided at the user
network interface
NOTE: It is the over-the-air wireless propagation channel which is used to convey an information signal from
transmitter to receiver. This definition is specified in ETSI EN 303 648 [i.2].
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.
link: connection from one location to another through a given Radio Access Technology for the purpose of transmitting
and receiving digital information
NOTE: Each Link is conveyed over a given Channel.
ETSI
7 Draft ETSI EN 303 681-2 V1.1.2 (2020-03)
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 (RC): part of Radio Equipment working under ROS control and on which RAs are executed
NOTE: A Radio Computer typically includes programmable processors, hardware accelerators, peripherals,
software, etc. RF part is considered to be part of peripherals.
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), Multiradio Controller (MRC) and Resource Manager (RM) which is
typically part of OS.
Radio Equipment (RE): "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".
NOTE: The definition above is as defined in the Radio Equipment Directive, Article 2(1)(1) [i.6].
Radio Frequency (RF) transceiver: part of radio platform converting, for transmission, baseband signals into radio
signals, and, for reception, radio signals into baseband signals
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
radio platform 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 components, hardware accelerators, RF transceiver, and antenna(s)
NOTE: A Radio Platform is a piece of hardware capable of generating RF signals or receiving RF signals. 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.
Radio Virtual Machine (RVM): abstract machine which supports reactive and concurrent executions
NOTE: An 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 mobile device: mobile device with radio communication capabilities providing support for radio
reconfiguration
NOTE: Reconfigurable mobile devices include but are not limited to: smartphones, feature phones, tablets, and
laptops.
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.
ETSI
8 Draft ETSI EN 303 681-2 V1.1.2 (2020-03)
3.2 Symbols
Void.
3.3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ACK ACKnowledgement
ACKM ACKnowledgement with Modification
AP Application Processor
ASIC Application-Specific Integrated Circuit
ASN.1 Abstract Syntax Notation One
BBIC Base-Band Integrated Circuit
BLER Block Error Rate
CSL Communication Services Layer
EU European Union
gMURI generalized Multiradio Interface
gRPI generalized Radio Programming Interface
gRRFI generalized Reconfigurable Radio Frequency Interface
gURAI generalized Unified Radio Applications Interface
MIMO Multiple Input Multiple Output
MPM Mobility Policy Manager
NACK Negative ACKnowledgement
OOB Out Of Band
OS Operating System
RA Radio Application
RAN Radio Access Network
RAP Radio Application Package
RAT Radio Access Technology
RC Radio Computer
RCF Radio Control Framework
RCID Radio Computer Identification
RE Radio Equipment
RERC Radio Equipment Reconfiguration Class
RF Radio Frequency
RFIC Radio Frequency Integrated Circuit
ROS Radio Operating System
RRFI Reconfigurable Radio Frequency Interface
RVM Radio Virtual Machine
RX Reception
SINR Signal to Interference plus Noise Ratio
TR Technical Report
UML Unified Modeling Language
URA Unified Radio Applications
4 Introduction
A reconfigurable RE is capable of running multiple radios simultaneously, changing the set of radios by loading new
Radio Application Packages (RAP) and setting their parameters. All Radio Applications (RAs) are called Unified Radio
Applications (URAs) when they exhibit a common behaviour from the reconfigurable RE's point of view in ETSI
EN 303 648 [i.2]. In order to run multiple URAs, the reconfigurable RE will include Communication Services Layer
(CSL), Radio Control Frameworks (RCFs), Radio Platforms and 4 sets of interfaces for their interconnection.
ETSI
9 Draft ETSI EN 303 681-2 V1.1.2 (2020-03)
Figure 4.1: Four sets of interfaces for reconfigurable RE
Figure 4.1 illustrates the reconfigurable RE architecture with the 4 sets of interfaces, i.e.:
• gMURI for interfacing CSL and RCF (in ETSI EN 303 681-1 [i.13]).
• gRRFI for interfacing URA and RF Transceiver, which is the scope of the present document.
• gURAI for interfacing URA and RCF (in ETSI EN 303 681-3 [i.14]).
• gRPI for allowing an independent and uniform production of RAs (in ETSI EN 303 681-4 [i.15]).
The present document defines gRRFI.
ETSI
10 Draft ETSI EN 303 681-2 V1.1.2 (2020-03)
<< in t e rf a ce >>
IgM U R I
<< in t e rf a ce >>
IgRRF I
RadioComputer
<< in t e rf a ce >>
IgU R AI
<< in t e rf a ce>>
IgR PI
Figure 4.2: UML class diagram for RC interfaces
Figure 4.2 illustrates UML class diagram for RC interfaces. The reconfigurable RE may be seen as RCs where
individual URAs are engineered as software entities in ETSI EN 303 648 [i.2].
The present document is organized as follows:
• clause 5 describes the system identification;
• clause 6 describes the notational tool for defining both information model classes and interface classes;
• clause 7 describes the information model for RC; and
• clause 8 describes the interface definition.
While UML is used for defining the information model and protocol related to gRRFI, other modelling languages could
be used as well.
5 System Identification
5.1 Radio Computer Structure
Figure 5.1 illustrates how URA and RF Transceiver interacts with each other using gRRFI.
ETSI
11 Draft ETSI EN 303 681-2 V1.1.2 (2020-03)
Figure 5.1: Interconnection between URA and RF Transceiver
using gRRFI for reconfigurable RE
As shown in figure 5.1, gRRFI can support up to 5 kinds of services depending on the applicable RERC [1].
A Reconfigurable RE shall support all the services as required by the corresponding RERC as shown in table 5.1 and
fully detailed in clause 8 of the present document. In case that a reconfigurable RE supports multiple RERCs, the
concerned reconfigurable RE shall support all the services as defined in table 5.1.
Table 5.1: Required services of gRRFI according to each RERC
Radio Equipment Antenna
Spectrum Power Control Tx/Rx Chain RVM Protection
Reconfiguration Management
Control services services Control services services
Class services
RERC-0 No No No No No
RERC-1 Yes Yes No No Yes
Yes
RERC-2, RERC-5 Yes Yes Yes Yes
(see note)
RERC-3, RERC-6 Yes Yes Yes Yes Yes
RERC-4, RERC-7 Yes Yes Yes Yes Yes
NOTE: Among the various Tx/Rx Chain Control services, only the service related with Tx/Rx timing is required in this
case.
A corresponding summary of the services is given below:
• Spectrum Control services
- These services are used to set up spectrum-related parameters such as carrier frequency, bandwidth,
sampling frequency, etc. that will be determined according to the URAs they are related to.
• Power Control services
- These services are used to set up RF power-related parameters such as maximum transmit (Tx) power
level, Tx power level per antenna, receive (Rx) gain, etc. Specific power schemes which have to be
controlled according to the communication circumstance around the reconfigurable RE are also included
in the Power Control services.
• Antenna Management services
- These services are used to determine the antenna configuration. Antenna radiation pattern, antenna gain,
antenna direction, sector configuration, polarization, frequency range, etc. are some factors to be
considered in the Antenna Management services.
NOTE: Antenna Management services depend on the configurability of the antenna.
ETSI
12 Draft ETSI EN 303 681-2 V1.1.2 (2020-03)
• Tx/Rx Chain Control services
- These services are used to provide parameters related to real-time control of the RF transceiver chain.
Parameters to be controlled using the Tx/Rx Chain Control services include (but are not limited to) Tx
start/stop time, Rx start/stop time, spectrum- and/or power-related values.
• RVM Protection services
- These services are used to provide parameters related to the selection of RVM protection class.
Parameters to be controlled using the RVM Protection services include (but are not limited to) selection
and/or request of RF protection class as well as, RF Front-end indication of input data signals
modification.
The clauses 5.2 to 5.4 describe the components/entities shown in figure 5.1.
5.2 URA
RAs need to be subject to a common reconfiguration, multiradio execution and resource sharing strategy framework
(depending on the concerned RERC). Since all RAs exhibit a common behaviour from the reconfigurable RE
perspective, those RAs are called URAs [i.8].
5.3 RF Transceiver
RF Transceiver, which includes transceiver chain(s), is part of the radio platform in RC that transforms, in Tx mode, the
baseband signal to radio signal, and in Rx mode, the radio signal to baseband signal.
5.4 RF Interfaces
The RF Interfaces depicted in figure 5.1 denote digital interfaces which define the physical interconnections between
SM
base-band and RFIC (Radio Frequency Integrated Circuit), for example, the DigRF specification defining the
interface between an RFIC and a BBIC (Base-Band Integrated Circuit) in a radio equipment. gRRFI defined in the
present document complements such RF interfaces by defining services which are required for reconfigurable REs.
5.5 Radio Computer RF System Requirement Mapping
The Radio Computer components above described shall support the RF system requirements shown in table 5.2 and
described in clause 6.5 of ETSI EN 303 641 [1].
NOTE: The transceiver requirements defined in clauses 6.5.5, 6.5.6 and 6.5.8 of ETSI EN 303 648 [i.2] are not
related to the RF Interface defined in the present document and therefore do not appear in table 5.2.
Table 5.2: Mapping of RC Components to the system requirements described in ETSI EN 303 641 [1]
Entity/Component/Unit System Requirements [1] Comments
Unified Radio Applications R-FUNC-RFT-02 The requirement is described in clause 6.5.2 of [1].
RF Transceiver R-FUNC-RFT-03 The requirement is described in clause 6.5.3 of [1].
R-FUNC-RFT-04 The requirement is described in clause 6.5.4 of [1].
Reconfigurable RF Interface R-FUNC-RFT-01, The requirement is described in clauses 6.5.1 and
R-FUNC-RFT-07 6.5.7 of [1].
R-FUNC-RFT-09 The requirement is described in clause 6.5.9 of [1].
ETSI
13 Draft ETSI EN 303 681-2 V1.1.2 (2020-03)
6 Notational Tools
6.1 Notational Tool for Information Model Classes
In the present document, information model classes are used as defined in annex B.1 of IEEE 1900.4-2009 [i.3].
6.2 Notational Tool for Interface Classes
Table 6.1 shows a template for defining interface classes for gRRFI. Each interface class for gRRFI will be defined in
clause 8.7 in accordance with the template shown in table 6.1.
Table 6.1: Template for defining Interface Classes
Class[(abstract class)]
OPERATIONS
Return type: Value type:
The template fields in table 6.1 are described below.
• is the name of the Class as it appears in the corresponding model. Additional information is also
included in case the class in question has been specified as an abstract one.
• OPERATIONS field describes the operations that have been defined in the class. More specifically:
- identifies the name of an operation, as it is included in the class definition.
- identifies the type of return value at the corresponding operation. Details related to the
ASN.1 module are specified in annex B of the present document.
- identifies the access levels for member functions: public, private, protected.
7 Information Model for Radio Computer
7.1 Radio Computer
Figure 7.1 shows the UML class diagram for RC classes related to gRRFI which are required to support Software
Reconfiguration.
ETSI
14 Draft ETSI EN 303 681-2 V1.1.2 (2020-03)
<>
IgR RF I
Radio Co mpu te r
- RCID: Name Type
RCMe asure m ents
R CC apabi lit i es
-listOfActiveMeasurements:
1 -listOfSupportedOptions: RCOptions
ActiveMeasurementsList
-listOfSupportedRadioInterfaces:
RadioInterfaces
-listOfSupportedChannels: ChannelIDs
-hardwareProfile: HardwareInfo
-softwareProfile: SoftwareInfo
R CC onfi gurat io n
Ch an ne l
0.*
Ch ann e lPr ofil e
Link
-channelID: NameType
0.*
-channelFrequecyRange:
FrequencyRange
-radioInterface:
RadioInterface
RFC onf iguration -cellID: NameType
L ink Pro file
-linkID: NameType
-cellID: NameType
-associatedChannelID:
Ch ann e lMe as ur em en t s
Tx P at h
OptiaonlObjectName
-linkDirection : Direction -listOfChannelMeasurements:
-txStartTime: TxStartTime
0,1
ChannelMeasurementsList
-CarrierFrequecy: Frequency
-txStopTime: TxStopTime
-nominalRFPower: -appliedMeasurementConfiguration:
AnaloguePower C on fig ura t io nMe s u re men t s
-samplingRate: SamplingRate
RxPath
-bandwidth: Bandwidth
-rxStartTime: RxStartTime
Antenn a
-rxStopTime: RxStopTime
1.*
L ink M e asure m ent s
-receiveBLER: RxBLER
-trasmitPower: TxPower Antenn aProfi le
-receiveSINR: RxSINR
-antennaID:
-transmittedBits: TxBits
NameType
Figure 7.1: UML class diagram for RC classes related to gRRFI
The RC classes related to gRRFI are defined as follows:
• RadioComputer
- This class contains all URA(s) related information about resources and interactions related to hardware
and software of a reconfigurable RE, for example, computational/spectral resource usage, collection of
context information, channel measurement results, etc.
ETSI
15 Draft ETSI EN 303 681-2 V1.1.2 (2020-03)
• RCCapabilities
- This class contains information about RC capabilities including hardware, software, transmission and
measurement capabilities such as supported RATs and maximum transmission power. Each instance of
RadioComputer class shall have only one instance of RCCapabilities class as a member.
• Channel
- This class contains one radio channel that may or may not be used by an active radio link. Each instance
of RadioComputer class can have zero, one or several instances of Channel class as members (0.*). In
case of an active radio link, at least one Channel class is available.
• ChannelProfile
- This class contains general information about the radio channel such as channel ID, centre frequency,
bandwidth, and used RAT. Each instance of Channel class shall have only one instance of Channel
Profile class as a member.
• ChannelMeasurements
- This class contains current measurements (instantaneous measurement data and related metadata) and the
applied measurement configuration related to this radio channel such as interference and load
measurements. Each instance of Channel class shall have only one instance of ChannelMeasurements
class as a member.
• Antenna
- This class contains information about antenna selection. Each instance of Link class shall have at least
one instance of Antenna class as a member (1.*).
• AntennaProfile
- This class contains general information about this antenna, such as antenna port, applicable frequency
range and antenna gain. Each instance of Antenna class shall have only one instance of AntennaProfile
class as a member.
• RCConfiguration
- This class contains information about the current configuration of RC. Each instance of RadioComputer
class shall have only one instance of RCConfiguration class as a member.
• Link
- This class contains information about one active URA and the corresponding connection between the
reconfigurable RE and the Radio Access Network (RAN). Each instance of RCConfiguration class has
zero, one or several instances of Link class as members (0.*). Each instance of Link class is associated
with one instance of Channel class.
• LinkProfile
- This class contains general information about this active connection, for example, link Identification
(ID), serving cell ID, channel used, etc. Each instance of Link class shall have only one instance of
LinkProfile class as a member.
• LinkMeasurements
- This class contains current measurements (instantaneous measurement data and related metadata) related
to this active connection, such as Block Error Rate (BLER), power, and Signal to Interference plus Noise
Ratio (SINR) measurements. Each instance of Link class shall have only one instance of
LinkMeasurements class as a member.
• RFConfiguration
- This class contains information about the configuration of the RF transceiver. Each instance of Link class
shall have only one instance of RFConfiguration class as a member.
ETSI
16 Draft ETSI EN 303 681-2 V1.1.2 (2020-03)
• TxPath
- This class contains information about one transmit path. Each instance of RFConfiguration class has zero
or one instance of TxPath class as a member (0,1).
• RxPath
- This class contains information about one receive path. Each instance of RFConfiguration class shall
have only one instance of RxPath class as a member.
• RCMeasurements
- This class contains current measurements (instantaneous measurement data and related metadata) related
to reconfigurable RE such as battery capacity, user mobility, RE location determination, and connection
history information. Each instance of RadioComputer class shall have only one instance of
RCMeasurements class as a member.
NOTE: The Channel Class is separate from the Link Class, but the Channel Measurements may be based on any
RE configuration which may or may not be used for the final Link Configuration.
7.2 Class Definitions for Information Model
Each class of RC can be defined using the template presented in clause 6.1 and in accordance with the UML diagram of
figure 7.1 which specifies the relations among all the classes of RC. RC classes defined in this way are shown in
tables 7.1 to 7.15.
Table 7.1: RadioComputer Class
Class RadioComputer
This class contains all URA related information about resources and interactions related to hardware
and software of a reconfigurable RE.
DERIVED FROM
ATTRIBUTES
Value type: Possible access: Default value:
RCID
Field Read-Write Not specified
This attribute describes ID of a Radio Computer.
CONTAINED IN
RCCapabilities [1], RCConfiguration [1], RCMeasurements [1],
CONTAINS
Channel [0.*]
SUPPORTED EVENTS
ETSI
17 Draft ETSI EN 303 681-2 V1.1.2 (2020-03)
Table 7.2: RCCapabilities Class
Class RCCapabilities
This class contains information about RC capabilities including hardware, software, transmission and
measurement capabilities.
DERIVED FROM
ATTRIBUTES
Value type: Possible access: Default value:
listOfSupportedOptions
RCOptionsList Read-Write Not specified
This attribute describes a list of supported options.
Value type: Possible access: Default value:
listOfSupportedRadioInterfaces
RadioInterfacesList Read-Write Not specified
This attribute describes radio interfaces supported by this RC.
Value type: Possible access: Default value:
listOfSupportedChannels
ChannelIDsList Read-Write Not specified
This attributes describes frequency channels supported by this RC.
Value type: Possible access: Default value:
hardwareProfile
HardwareInfo Read-Write Not specified
This attributes describes hardware capabilities of this RC.
Value type: Possible access: Default value:
softwareProfile
SoftwareInfo Read-Write Not specified
This attributes describes software capabilities of this RC.
CONTAINED IN RadioComputer
CONTAINS
SUPPORTED EVENTS
Table 7.3: Channel Class
Class Channel
This class describes one frequency channel that may or may not have active connections on it.
DERIVED FROM
ATTRIBUTES
CONTAINED IN RadioComputer
CONTAINS ChannelProfile [1], ChannelMeasurements [1], Antenna [1.*]
SUPPORTED EVENTS
Table 7.4: ChannelProfile Class
Class ChannelProfile
This class contains general information about this frequency channel.
DERIVED FROM
ATTRIBUTES
Value type: Possible access: Default value:
channelID
NameType Read Not specified
This attribute describes ID of channel.
Value type: Possible access: Default value:
channelFrequencyRange
FrequencyRange Read Not specified
This attribute describes a value of channel frequency range.
Value type: Possible access: Default value:
radioInterface
RadioInterface Read Not specified
This attribute describes a radio interface.
Value type: Possible access: Default value:
cellID
NameType Read Not specified
This attribute describes ID of connected cell.
CONTAINED IN Channel
CONTAINS
SUPPORTED EVENTS
ETSI
18 Draft ETSI EN 303 681-2 V1.1.2 (2020-03)
Table 7.5: ChannelMeasurements Class
Class ChannelMeasurements
This class contains current measurements related to this frequency channel.
DERIVED FROM
ATTRIBUTES
Default
Value type: Possible access:
listOfChannelMeasurements value:
ChannelMeasurementsList Read
Not specified
This attribute describes a list of channel measurements.
Default
Value type: Possible access:
appliedMeasurementsConfiguration value:
ConfigurationMeasurements Read
Not specified
This attribute describes configuration option of the RE, e.g. which Antenna(s) have been used, which
RF front-end(s) have been used, etc.
CONTAINED IN Channel
CONTAINS
SUPPORTED EVENTS
Table 7.6: Antenna Class
Class Antenna
This class contains information about antenna selection.
DERIVED FROM
ATTRIBUTES
CONTAINED IN Channel
AntennaProfile [1]
CONTAINS
SUPPORTED EVENTS
Table 7.7: AntennaProfileClass
Class AntennaProfile
This class contains general information about this antenna.
DERIVED FROM
ATTRIBUTES
Value type: Possible access: Default value:
antennaID
NameType Read Not specified
This attribute describes ID of antenna.
CONTAINED IN Antenna
CONTAINS
SUPPORTED EVENTS
Table 7.8: RCConfigurationClass
Class RCConfiguration
This class contains information about the current configuration of RC.
DERIVED FROM
ATTRIBUTES
RadioComputer
CONTAINED IN
CONTAINS Link [0.*]
SUPPORTED EVENTS
ETSI
19 Draft ETSI EN 303 681-2 V1.1.2 (2020-03)
Table 7.9: LinkClass
Class Link
This class contains information about one active Radio Application and corresponding connection
between Reconfigurable Radio terminal and RANs.
DERIVED FROM
ATTRIBUTES
CONTAINED IN RCConfiguration
CONTAINS LinkProfile [1], LinkMeasurements [1], RFConfiguration [1]
SUPPORTED EVENTS
Table 7.10: LinkProfileClass
Class LinkProfile
This class contains general information about this active connection.
DERIVED FROM
ATTRIBUTES
Value type: Possible access: Default value:
linkID
NameType Read Not specified
This attribute describes ID of link about activated connection.
Value type: Possible access: Default value:
cellID
NameType Read-Write Not specified
This attribute describes ID connected cell.
Value type: Possible access: Default value:
associatedChannelID
OptionalObjectName Read-Add-Remove Not specified
This attribute describes ID of associated channel.
Value type: Possible access: Default value:
linkDirection
Direction Read Not specified
This attribute describes a direction of link.
Value type: Possible access: Default value:
carrierFrequency
FrequencyRange Read-Write Not specified
This attribute describes a value of carrier frequency.
Value type: Possible access: Default value:
nominalRFPower
AnaloguePower Read Not specified
This attribute describes a value of nominal power.
Value type: Possible access: Default value:
samplingRate
SamplingRate Read-Write Not specified
This attribute describes a value of sampling rate.
Value type: Possible access: Default value:
bandwidth
Bandwidth Read-Write Not specified
Th
...
EUROPEAN STANDARD
Reconfigurable Radio Systems (RRS);
Radio Equipment (RE) information models and protocols
for generalized software reconfiguration architecture;
Part 2: generalized Reconfigurable
Radio Frequency Interface (gRRFI)
2 ETSI EN 303 681-2 V1.1.2 (2020-06)
Reference
REN/RRS-0229
Keywords
interface, radio, SDR
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
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 EN 303 681-2 V1.1.2 (2020-06)
Contents
Intellectual Property Rights . 4
Foreword . 4
Modal verbs terminology . 4
1 Scope . 5
2 References . 5
2.1 Normative references . 5
2.2 Informative references . 5
3 Definition of terms, symbols and abbreviations . 6
3.1 Terms . 6
3.2 Symbols . 8
3.3 Abbreviations . 8
4 Introduction . 8
5 System Identification . 10
5.1 Radio Computer Structure . 10
5.2 URA . 12
5.3 RF Transceiver . 12
5.4 RF Interfaces . 12
5.5 Radio Computer RF System Requirement Mapping . 12
6 Notational Tools . 13
6.1 Notational Tool for Information Model Classes . 13
6.2 Notational Tool for Interface Classes . 13
7 Information Model for Radio Computer . 13
7.1 Radio Computer . 13
7.2 Class Definitions for Information Model . 16
8 Interface Definition . 21
8.1 Interface Overview . 21
8.2 Spectrum Control Services . 24
8.2.1 Overview on Spectrum Control Services . 24
8.2.2 Messages for Spectrum Control Services . 24
8.3 Power Control Services . 25
8.3.1 Overview on Power Control Services . 25
8.3.2 Messages for Power Control Services . 25
8.4 Antenna Management Services . 25
8.4.1 Overview on Antenna Management Services . 25
8.4.2 Messages for Antenna Management Services. 26
8.5 Tx/Rx Chain Control Services. 26
8.5.1 Overview on Tx/Rx Chain Control Services . 26
8.5.2 Messages for Tx/Rx Chain Control Services . 26
8.6 RVM Protection Services . 27
8.6.1 Overview on RVM Protection Services . 27
8.6.2 Messages for RVM Protection Services . 28
8.7 Class Definitions for Interface . 28
Annex A (informative): Abstract Data Definitions . 31
Annex B (informative): gRRFI Qualification Methods for Validation . 35
History . 36
ETSI
4 ETSI EN 303 681-2 V1.1.2 (2020-06)
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 European Standard (EN) has been produced by ETSI Technical Committee Reconfigurable Radio Systems (RRS).
The present document is part 2 of a multi-part deliverable covering the Radio Equipment (RE) information models and
protocols, as identified below:
Part 1: "generalized Multiradio Interface (gMURI)";
Part 2: "generalized Reconfigurable Radio Frequency Interface (gRRFI)";
Part 3: "generalized Unified Radio Application Interface (gURAI)";
Part 4: "generalized Radio Programming Interface (gRPI)".
National transposition dates
Date of adoption of this EN: 22 June 2020
Date of latest announcement of this EN (doa): 30 September 2020
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 31 March 2021
Date of withdrawal of any conflicting National Standard (dow): 31 March 2021
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
5 ETSI EN 303 681-2 V1.1.2 (2020-06)
1 Scope
The present document defines an information model and protocol for generalized reconfigurable radio frequency
interface for reconfigurable REs except for reconfigurable mobile devices which are covered in [i.7] to [i.12]. The work
is based on the Use Cases defined in ETSI TR 103 585 [i.1], on the system requirements defined in ETSI
EN 303 641 [1] and on the radio reconfiguration related architecture for reconfigurable RE defined in ETSI
EN 303 648 [i.2].
The present document will be based on ETSI EN 303 146-2 [i.10] and provide a generalized interface definition for the
generalized Reconfigurable Radio Frequency Interface.
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 EN 303 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 585: "Reconfigurable Radio Systems (RRS); Radio Equipment (RE) reconfiguration
use cases".
[i.2] ETSI EN 303 648: "Reconfigurable Radio Systems (RRS); Radio Equipment (RE) reconfiguration
architecture".
[i.3] IEEE 1900.4™-2009: "IEEE Standard for Architectural Building Blocks Enabling Network-
Device Distributed Decision Making for Optimized Radio Resource Usage in Heterogeneous
Wireless Access Networks". ®
[i.4] DigRFSM Working Group: "MIPI Alliance Specification for DigRFSM v4".
[i.5] Recommendation ITU-T X.680: "Information technology - Abstract Syntax Notation One
(ASN.1): Specification of basic notation".
[i.6] 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
6 ETSI EN 303 681-2 V1.1.2 (2020-06)
[i.7] ETSI EN 302 969: "Reconfigurable Radio Systems (RRS); Radio Reconfiguration related
Requirements for Mobile Devices".
[i.8] ETSI EN 303 095: "Reconfigurable Radio Systems (RRS); Radio reconfiguration related
architecture for Mobile Devices (MD)".
[i.9] ETSI EN 303 146-1: "Reconfigurable Radio Systems (RRS); Mobile Device (MD) information
models and protocols; Part 1: Multiradio Interface (MURI)".
[i.10] ETSI EN 303 146-2: "Reconfigurable Radio Systems (RRS); Mobile Device (MD) information
models and protocols; Part 2: Reconfigurable Radio Frequency Interface (RRFI)".
[i.11] ETSI EN 303 146-3: "Reconfigurable Radio Systems (RRS); Mobile Device (MD) information
models and protocols; Part 3: Unified Radio Application Interface (URAI)".
[i.12] ETSI EN 303 146-4: "Reconfigurable Radio Systems (RRS); Mobile Device (MD) information
models and protocols; Part 4: Radio Programming Interface (RPI)".
[i.13] ETSI EN 303 681-1: "Reconfigurable Radio Systems (RRS); Radio Equipment (RE) information
models and protocols for generalized software reconfiguration architecture; Part 1: generalized
Multiradio Interface (gMURI)".
[i.14] ETSI EN 303 681-3: "Reconfigurable Radio Systems (RRS); Radio Equipment (RE) information
models and protocols for generalized software reconfiguration architecture; Part 3: generalized
Unified Radio Application Interface (gURAI)".
[i.15] ETSI EN 303 681-4: "Reconfigurable Radio Systems (RRS); adio Equipment (RE) information
models and protocols for generalized software reconfiguration architecture; Part 4: generalized
Radio Programming Interface (gRPI)".
3 Definition of terms, symbols and abbreviations
3.1 Terms
For the purposes of the present document, the following terms apply:
association: logical communication link to a Radio Access Network or a peer equipment
NOTE 1: Typically, some control signalling is necessary to maintain the association. No user data transfer may
occur with only an association present, but a data flow may be established into an association for this
purpose.
NOTE 2: Peer equipment is any communication counterpart of a reconfigurable Radio Equipment. It can be
reached by establishing a logical communication link (i.e. an association) between the reconfigurable
Radio Equipment and peer equipment.
channel: designated part of the information transfer capability having specified characteristics, provided at the user
network interface
NOTE: It is the over-the-air wireless propagation channel which is used to convey an information signal from
transmitter to receiver. This definition is specified in ETSI EN 303 648 [i.2].
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.
link: connection from one location to another through a given Radio Access Technology for the purpose of transmitting
and receiving digital information
NOTE: Each Link is conveyed over a given Channel.
ETSI
7 ETSI EN 303 681-2 V1.1.2 (2020-06)
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 (RC): part of Radio Equipment working under ROS control and on which RAs are executed
NOTE: A Radio Computer typically includes programmable processors, hardware accelerators, peripherals,
software, etc. RF part is considered to be part of peripherals.
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), Multiradio Controller (MRC) and Resource Manager (RM) which is
typically part of OS.
Radio Equipment (RE): "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".
NOTE: The definition above is as defined in the Radio Equipment Directive, Article 2(1)(1) [i.6].
Radio Frequency (RF) transceiver: part of radio platform converting, for transmission, baseband signals into radio
signals, and, for reception, radio signals into baseband signals
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
radio platform 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 components, hardware accelerators, RF transceiver, and antenna(s)
NOTE: A Radio Platform is a piece of hardware capable of generating RF signals or receiving RF signals. 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.
Radio Virtual Machine (RVM): abstract machine which supports reactive and concurrent executions
NOTE: An 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 mobile device: mobile device with radio communication capabilities providing support for radio
reconfiguration
NOTE: Reconfigurable mobile devices include but are not limited to: smartphones, feature phones, tablets, and
laptops.
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.
ETSI
8 ETSI EN 303 681-2 V1.1.2 (2020-06)
3.2 Symbols
Void.
3.3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ACK ACKnowledgement
ACKM ACKnowledgement with Modification
AP Application Processor
ASIC Application-Specific Integrated Circuit
ASN.1 Abstract Syntax Notation One
BBIC Base-Band Integrated Circuit
BLER Block Error Rate
CSL Communication Services Layer
EU European Union
gMURI generalized Multiradio Interface
gRPI generalized Radio Programming Interface
gRRFI generalized Reconfigurable Radio Frequency Interface
gURAI generalized Unified Radio Applications Interface
MIMO Multiple Input Multiple Output
MPM Mobility Policy Manager
NACK Negative ACKnowledgement
OOB Out Of Band
OS Operating System
RA Radio Application
RAN Radio Access Network
RAP Radio Application Package
RAT Radio Access Technology
RC Radio Computer
RCF Radio Control Framework
RCID Radio Computer Identification
RE Radio Equipment
RERC Radio Equipment Reconfiguration Class
RF Radio Frequency
RFIC Radio Frequency Integrated Circuit
ROS Radio Operating System
RRFI Reconfigurable Radio Frequency Interface
RVM Radio Virtual Machine
RX Reception
SINR Signal to Interference plus Noise Ratio
TR Technical Report
UML Unified Modeling Language
URA Unified Radio Applications
4 Introduction
A reconfigurable RE is capable of running multiple radios simultaneously, changing the set of radios by loading new
Radio Application Packages (RAP) and setting their parameters. All Radio Applications (RAs) are called Unified Radio
Applications (URAs) when they exhibit a common behaviour from the reconfigurable RE's point of view in ETSI
EN 303 648 [i.2]. In order to run multiple URAs, the reconfigurable RE will include Communication Services Layer
(CSL), Radio Control Frameworks (RCFs), Radio Platforms and 4 sets of interfaces for their interconnection.
ETSI
9 ETSI EN 303 681-2 V1.1.2 (2020-06)
Figure 4.1: Four sets of interfaces for reconfigurable RE
Figure 4.1 illustrates the reconfigurable RE architecture with the 4 sets of interfaces, i.e.:
• gMURI for interfacing CSL and RCF (in ETSI EN 303 681-1 [i.13]).
• gRRFI for interfacing URA and RF Transceiver, which is the scope of the present document.
• gURAI for interfacing URA and RCF (in ETSI EN 303 681-3 [i.14]).
• gRPI for allowing an independent and uniform production of RAs (in ETSI EN 303 681-4 [i.15]).
The present document defines gRRFI.
ETSI
10 ETSI EN 303 681-2 V1.1.2 (2020-06)
<< in t e rf a ce >>
IgM U R I
<< in t e rf a ce >>
IgRRF I
RadioComputer
<< in t e rf a ce >>
IgU R AI
<< in t e rf a ce>>
IgR PI
Figure 4.2: UML class diagram for RC interfaces
Figure 4.2 illustrates UML class diagram for RC interfaces. The reconfigurable RE may be seen as RCs where
individual URAs are engineered as software entities in ETSI EN 303 648 [i.2].
The present document is organized as follows:
• clause 5 describes the system identification;
• clause 6 describes the notational tool for defining both information model classes and interface classes;
• clause 7 describes the information model for RC; and
• clause 8 describes the interface definition.
While UML is used for defining the information model and protocol related to gRRFI, other modelling languages could
be used as well.
5 System Identification
5.1 Radio Computer Structure
Figure 5.1 illustrates how URA and RF Transceiver interacts with each other using gRRFI.
ETSI
11 ETSI EN 303 681-2 V1.1.2 (2020-06)
Figure 5.1: Interconnection between URA and RF Transceiver
using gRRFI for reconfigurable RE
As shown in figure 5.1, gRRFI can support up to 5 kinds of services depending on the applicable RERC [1].
A Reconfigurable RE shall support all the services as required by the corresponding RERC as shown in table 5.1 and
fully detailed in clause 8 of the present document. In case that a reconfigurable RE supports multiple RERCs, the
concerned reconfigurable RE shall support all the services as defined in table 5.1.
Table 5.1: Required services of gRRFI according to each RERC
Radio Equipment Antenna
Spectrum Power Control Tx/Rx Chain RVM Protection
Reconfiguration Management
Control services services Control services services
Class services
RERC-0 No No No No No
RERC-1 Yes Yes No No Yes
Yes
RERC-2, RERC-5 Yes Yes Yes Yes
(see note)
RERC-3, RERC-6 Yes Yes Yes Yes Yes
RERC-4, RERC-7 Yes Yes Yes Yes Yes
NOTE: Among the various Tx/Rx Chain Control services, only the service related with Tx/Rx timing is required in this
case.
A corresponding summary of the services is given below:
• Spectrum Control services
- These services are used to set up spectrum-related parameters such as carrier frequency, bandwidth,
sampling frequency, etc. that will be determined according to the URAs they are related to.
• Power Control services
- These services are used to set up RF power-related parameters such as maximum transmit (Tx) power
level, Tx power level per antenna, receive (Rx) gain, etc. Specific power schemes which have to be
controlled according to the communication circumstance around the reconfigurable RE are also included
in the Power Control services.
• Antenna Management services
- These services are used to determine the antenna configuration. Antenna radiation pattern, antenna gain,
antenna direction, sector configuration, polarization, frequency range, etc. are some factors to be
considered in the Antenna Management services.
NOTE: Antenna Management services depend on the configurability of the antenna.
ETSI
12 ETSI EN 303 681-2 V1.1.2 (2020-06)
• Tx/Rx Chain Control services
- These services are used to provide parameters related to real-time control of the RF transceiver chain.
Parameters to be controlled using the Tx/Rx Chain Control services include (but are not limited to) Tx
start/stop time, Rx start/stop time, spectrum- and/or power-related values.
• RVM Protection services
- These services are used to provide parameters related to the selection of RVM protection class.
Parameters to be controlled using the RVM Protection services include (but are not limited to) selection
and/or request of RF protection class as well as, RF Front-end indication of input data signals
modification.
The clauses 5.2 to 5.4 describe the components/entities shown in figure 5.1.
5.2 URA
RAs need to be subject to a common reconfiguration, multiradio execution and resource sharing strategy framework
(depending on the concerned RERC). Since all RAs exhibit a common behaviour from the reconfigurable RE
perspective, those RAs are called URAs [i.8].
5.3 RF Transceiver
RF Transceiver, which includes transceiver chain(s), is part of the radio platform in RC that transforms, in Tx mode, the
baseband signal to radio signal, and in Rx mode, the radio signal to baseband signal.
5.4 RF Interfaces
The RF Interfaces depicted in figure 5.1 denote digital interfaces which define the physical interconnections between
SM
base-band and RFIC (Radio Frequency Integrated Circuit), for example, the DigRF specification defining the
interface between an RFIC and a BBIC (Base-Band Integrated Circuit) in a radio equipment. gRRFI defined in the
present document complements such RF interfaces by defining services which are required for reconfigurable REs.
5.5 Radio Computer RF System Requirement Mapping
The Radio Computer components above described shall support the RF system requirements shown in table 5.2 and
described in clause 6.5 of ETSI EN 303 641 [1].
NOTE: The transceiver requirements defined in clauses 6.5.5, 6.5.6 and 6.5.8 of ETSI EN 303 648 [i.2] are not
related to the RF Interface defined in the present document and therefore do not appear in table 5.2.
Table 5.2: Mapping of RC Components to the system requirements described in ETSI EN 303 641 [1]
Entity/Component/Unit System Requirements [1] Comments
Unified Radio Applications R-FUNC-RFT-02 The requirement is described in clause 6.5.2 of [1].
RF Transceiver R-FUNC-RFT-03 The requirement is described in clause 6.5.3 of [1].
R-FUNC-RFT-04 The requirement is described in clause 6.5.4 of [1].
Reconfigurable RF Interface R-FUNC-RFT-01, The requirement is described in clauses 6.5.1 and
R-FUNC-RFT-07 6.5.7 of [1].
R-FUNC-RFT-09 The requirement is described in clause 6.5.9 of [1].
ETSI
13 ETSI EN 303 681-2 V1.1.2 (2020-06)
6 Notational Tools
6.1 Notational Tool for Information Model Classes
In the present document, information model classes are used as defined in annex B.1 of IEEE 1900.4-2009 [i.3].
6.2 Notational Tool for Interface Classes
Table 6.1 shows a template for defining interface classes for gRRFI. Each interface class for gRRFI will be defined in
clause 8.7 in accordance with the template shown in table 6.1.
Table 6.1: Template for defining Interface Classes
Class[(abstract class)]
OPERATIONS
Return type: Value type:
The template fields in table 6.1 are described below.
• is the name of the Class as it appears in the corresponding model. Additional information is also
included in case the class in question has been specified as an abstract one.
• OPERATIONS field describes the operations that have been defined in the class. More specifically:
- identifies the name of an operation, as it is included in the class definition.
- identifies the type of return value at the corresponding operation. Details related to the
ASN.1 module are specified in annex B of the present document.
- identifies the access levels for member functions: public, private, protected.
7 Information Model for Radio Computer
7.1 Radio Computer
Figure 7.1 shows the UML class diagram for RC classes related to gRRFI which are required to support Software
Reconfiguration.
ETSI
14 ETSI EN 303 681-2 V1.1.2 (2020-06)
<>
IgR RF I
Radio Co mpu te r
- RCID: Name Type
RCMe asure m ents
R CC apabi lit i es
-listOfActiveMeasurements:
1 -listOfSupportedOptions: RCOptions
ActiveMeasurementsList
-listOfSupportedRadioInterfaces:
RadioInterfaces
-listOfSupportedChannels: ChannelIDs
-hardwareProfile: HardwareInfo
-softwareProfile: SoftwareInfo
R CC onfi gurat io n
Ch an ne l
0.*
Ch ann e lPr ofil e
Link
-channelID: NameType
0.*
-channelFrequecyRange:
FrequencyRange
-radioInterface:
RadioInterface
RFC onf iguration -cellID: NameType
L ink Pro file
-linkID: NameType
-cellID: NameType
-associatedChannelID:
Ch ann e lMe as ur em en t s
Tx P at h
OptiaonlObjectName
-linkDirection : Direction -listOfChannelMeasurements:
-txStartTime: TxStartTime
0,1
ChannelMeasurementsList
-CarrierFrequecy: Frequency
-txStopTime: TxStopTime
-nominalRFPower: -appliedMeasurementConfiguration:
AnaloguePower C on fig ura t io nMe s u re men t s
-samplingRate: SamplingRate
RxPath
-bandwidth: Bandwidth
-rxStartTime: RxStartTime
Antenn a
-rxStopTime: RxStopTime
1.*
L ink M e asure m ent s
-receiveBLER: RxBLER
-trasmitPower: TxPower Antenn aProfi le
-receiveSINR: RxSINR
-antennaID:
-transmittedBits: TxBits
NameType
Figure 7.1: UML class diagram for RC classes related to gRRFI
The RC classes related to gRRFI are defined as follows:
• RadioComputer
- This class contains all URA(s) related information about resources and interactions related to hardware
and software of a reconfigurable RE, for example, computational/spectral resource usage, collection of
context information, channel measurement results, etc.
ETSI
15 ETSI EN 303 681-2 V1.1.2 (2020-06)
• RCCapabilities
- This class contains information about RC capabilities including hardware, software, transmission and
measurement capabilities such as supported RATs and maximum transmission power. Each instance of
RadioComputer class shall have only one instance of RCCapabilities class as a member.
• Channel
- This class contains one radio channel that may or may not be used by an active radio link. Each instance
of RadioComputer class can have zero, one or several instances of Channel class as members (0.*). In
case of an active radio link, at least one Channel class is available.
• ChannelProfile
- This class contains general information about the radio channel such as channel ID, centre frequency,
bandwidth, and used RAT. Each instance of Channel class shall have only one instance of Channel
Profile class as a member.
• ChannelMeasurements
- This class contains current measurements (instantaneous measurement data and related metadata) and the
applied measurement configuration related to this radio channel such as interference and load
measurements. Each instance of Channel class shall have only one instance of ChannelMeasurements
class as a member.
• Antenna
- This class contains information about antenna selection. Each instance of Link class shall have at least
one instance of Antenna class as a member (1.*).
• AntennaProfile
- This class contains general information about this antenna, such as antenna port, applicable frequency
range and antenna gain. Each instance of Antenna class shall have only one instance of AntennaProfile
class as a member.
• RCConfiguration
- This class contains information about the current configuration of RC. Each instance of RadioComputer
class shall have only one instance of RCConfiguration class as a member.
• Link
- This class contains information about one active URA and the corresponding connection between the
reconfigurable RE and the Radio Access Network (RAN). Each instance of RCConfiguration class has
zero, one or several instances of Link class as members (0.*). Each instance of Link class is associated
with one instance of Channel class.
• LinkProfile
- This class contains general information about this active connection, for example, link Identification
(ID), serving cell ID, channel used, etc. Each instance of Link class shall have only one instance of
LinkProfile class as a member.
• LinkMeasurements
- This class contains current measurements (instantaneous measurement data and related metadata) related
to this active connection, such as Block Error Rate (BLER), power, and Signal to Interference plus Noise
Ratio (SINR) measurements. Each instance of Link class shall have only one instance of
LinkMeasurements class as a member.
• RFConfiguration
- This class contains information about the configuration of the RF transceiver. Each instance of Link class
shall have only one instance of RFConfiguration class as a member.
ETSI
16 ETSI EN 303 681-2 V1.1.2 (2020-06)
• TxPath
- This class contains information about one transmit path. Each instance of RFConfiguration class has zero
or one instance of TxPath class as a member (0,1).
• RxPath
- This class contains information about one receive path. Each instance of RFConfiguration class shall
have only one instance of RxPath class as a member.
• RCMeasurements
- This class contains current measurements (instantaneous measurement data and related metadata) related
to reconfigurable RE such as battery capacity, user mobility, RE location determination, and connection
history information. Each instance of RadioComputer class shall have only one instance of
RCMeasurements class as a member.
NOTE: The Channel Class is separate from the Link Class, but the Channel Measurements may be based on any
RE configuration which may or may not be used for the final Link Configuration.
7.2 Class Definitions for Information Model
Each class of RC can be defined using the template presented in clause 6.1 and in accordance with the UML diagram of
figure 7.1 which specifies the relations among all the classes of RC. RC classes defined in this way are shown in
tables 7.1 to 7.15.
Table 7.1: RadioComputer Class
Class RadioComputer
This class contains all URA related information about resources and interactions related to hardware
and software of a reconfigurable RE.
DERIVED FROM
ATTRIBUTES
Value type: Possible access: Default value:
RCID
Field Read-Write Not specified
This attribute describes ID of a Radio Computer.
CONTAINED IN
RCCapabilities [1], RCConfiguration [1], RCMeasurements [1],
CONTAINS
Channel [0.*]
SUPPORTED EVENTS
ETSI
17 ETSI EN 303 681-2 V1.1.2 (2020-06)
Table 7.2: RCCapabilities Class
Class RCCapabilities
This class contains information about RC capabilities including hardware, software, transmission and
measurement capabilities.
DERIVED FROM
ATTRIBUTES
Value type: Possible access: Default value:
listOfSupportedOptions
RCOptionsList Read-Write Not specified
This attribute describes a list of supported options.
Value type: Possible access: Default value:
listOfSupportedRadioInterfaces
RadioInterfacesList Read-Write Not specified
This attribute describes radio interfaces supported by this RC.
Value type: Possible access: Default value:
listOfSupportedChannels
ChannelIDsList Read-Write Not specified
This attributes describes frequency channels supported by this RC.
Value type: Possible access: Default value:
hardwareProfile
HardwareInfo Read-Write Not specified
This attributes describes hardware capabilities of this RC.
Value type: Possible access: Default value:
softwareProfile
SoftwareInfo Read-Write Not specified
This attributes describes software capabilities of this RC.
CONTAINED IN RadioComputer
CONTAINS
SUPPORTED EVENTS
Table 7.3: Channel Class
Class Channel
This class describes one frequency channel that may or may not have active connections on it.
DERIVED FROM
ATTRIBUTES
CONTAINED IN RadioComputer
CONTAINS ChannelProfile [1], ChannelMeasurements [1], Antenna [1.*]
SUPPORTED EVENTS
Table 7.4: ChannelProfile Class
Class ChannelProfile
This class contains general information about this frequency channel.
DERIVED FROM
ATTRIBUTES
Value type: Possible access: Default value:
channelID
NameType Read Not specified
This attribute describes ID of channel.
Value type: Possible access: Default value:
channelFrequencyRange
FrequencyRange Read Not specified
This attribute describes a value of channel frequency range.
Value type: Possible access: Default value:
radioInterface
RadioInterface Read Not specified
This attribute describes a radio interface.
Value type: Possible access: Default value:
cellID
NameType Read Not specified
This attribute describes ID of connected cell.
CONTAINED IN Channel
CONTAINS
SUPPORTED EVENTS
ETSI
18 ETSI EN 303 681-2 V1.1.2 (2020-06)
Table 7.5: ChannelMeasurements Class
Class ChannelMeasurements
This class contains current measurements related to this frequency channel.
DERIVED FROM
ATTRIBUTES
Default
Value type: Possible access:
listOfChannelMeasurements
value:
ChannelMeasurementsList Read
Not specified
This attribute describes a list of channel measurements.
Default
Value type: Possible access:
appliedMeasurementsConfiguration value:
ConfigurationMeasurements Read
Not specified
This attribute describes configuration option of the RE, e.g. which Antenna(s) have been used, which
RF front-end(s) have been used, etc.
CONTAINED IN Channel
CONTAINS
SUPPORTED EVENTS
Table 7.6: Antenna Class
Class Antenna
This class contains information about antenna selection.
DERIVED FROM
ATTRIBUTES
CONTAINED IN Channel
CONTAINS AntennaProfile [1]
SUPPORTED EVENTS
Table 7.7: AntennaProfileClass
Class AntennaProfile
This class contains general information about this antenna.
DERIVED FROM
ATTRIBUTES
Value type: Possible access: Default value:
antennaID
NameType Read Not specified
This attribute describes ID of antenna.
CONTAINED IN Antenna
CONTAINS
SUPPORTED EVENTS
Table 7.8: RCConfigurationClass
Class RCConfiguration
This class contains information about the current configuration of RC.
DERIVED FROM
ATTRIBUTES
CONTAINED IN RadioComputer
CONTAINS Link [0.*]
SUPPORTED EVENTS
ETSI
19 ETSI EN 303 681-2 V1.1.2 (2020-06)
Table 7.9: LinkClass
Class Link
This class contains information about one active Radio Application and corresponding connection
between Reconfigurable Radio terminal and RANs.
DERIVED FROM
ATTRIBUTES
CONTAINED IN RCConfiguration
CONTAINS LinkProfile [1], LinkMeasurements [1], RFConfiguration [1]
SUPPORTED EVENTS
Table 7.10: LinkProfileClass
Class LinkProfile
This class contains general information about this active connection.
DERIVED FROM
ATTRIBUTES
Value type: Possible access: Default value:
linkID
NameType Read Not specified
This attribute describes ID of link about activated connection.
Value type: Possible access: Default value:
cellID
NameType Read-Write Not specified
This attribute describes ID connected cell.
Value type: Possible access: Default value:
associatedChannelID
OptionalObjectName Read-Add-Remove Not specified
This attribute describes ID of associated channel.
Value type: Possible access: Default value:
linkDirection
Direction Read Not specified
This attribute describes a direction of link.
Value type: Possible access: Default value:
carrierFrequency
FrequencyRange Read-Write Not specified
This attribute describes a value of carrier frequency.
Value type: Possible access: Default value:
nominalRFPower
AnaloguePower Read Not specified
This attribute describes a value of nominal power.
Value type: Possible access: Default value:
samplingRate
SamplingRate Read-Write Not specified
This attribute describes a value of sampling rate.
Value type: Possible access: Default value:
bandwidth
Bandwidth Read-Write Not specified
This attribute describes a value of bandwidth.
CONTAINED IN Link
CONTAINS
SUPPORTED EVENTS
ETSI
20 ETSI EN 303 681-2 V1.1.2 (2020-06)
Table 7.11
...
SLOVENSKI STANDARD
01-september-2020
Radijski sistemi z možnostjo preoblikovanja (RRS) - Informacijski modeli in
protokoli za radijsko opremo (RE) za splošno arhitekturo preoblikovanja
programske opreme - 2. del: Splošni spremenljivi radiofrekvenčni vmesnik (gRRFI)
Reconfigurable Radio Systems (RRS) - Radio Equipment (RE) information models and
protocols for generalized software reconfiguration architecture - Part 2: generalized
Reconfigurable Radio Frequency Interface (gRRFI)
Ta slovenski standard je istoveten z: ETSI EN 303 681-2 V1.1.2 (2020-06)
ICS:
33.060.01 Radijske komunikacije na Radiocommunications in
splošno general
35.200 Vmesniška in povezovalna Interface and interconnection
oprema equipment
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
EUROPEAN STANDARD
Reconfigurable Radio Systems (RRS);
Radio Equipment (RE) information models and protocols
for generalized software reconfiguration architecture;
Part 2: generalized Reconfigurable
Radio Frequency Interface (gRRFI)
2 ETSI EN 303 681-2 V1.1.2 (2020-06)
Reference
REN/RRS-0229
Keywords
interface, radio, SDR
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
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 EN 303 681-2 V1.1.2 (2020-06)
Contents
Intellectual Property Rights . 4
Foreword . 4
Modal verbs terminology . 4
1 Scope . 5
2 References . 5
2.1 Normative references . 5
2.2 Informative references . 5
3 Definition of terms, symbols and abbreviations . 6
3.1 Terms . 6
3.2 Symbols . 8
3.3 Abbreviations . 8
4 Introduction . 8
5 System Identification . 10
5.1 Radio Computer Structure . 10
5.2 URA . 12
5.3 RF Transceiver . 12
5.4 RF Interfaces . 12
5.5 Radio Computer RF System Requirement Mapping . 12
6 Notational Tools . 13
6.1 Notational Tool for Information Model Classes . 13
6.2 Notational Tool for Interface Classes . 13
7 Information Model for Radio Computer . 13
7.1 Radio Computer . 13
7.2 Class Definitions for Information Model . 16
8 Interface Definition . 21
8.1 Interface Overview . 21
8.2 Spectrum Control Services . 24
8.2.1 Overview on Spectrum Control Services . 24
8.2.2 Messages for Spectrum Control Services . 24
8.3 Power Control Services . 25
8.3.1 Overview on Power Control Services . 25
8.3.2 Messages for Power Control Services . 25
8.4 Antenna Management Services . 25
8.4.1 Overview on Antenna Management Services . 25
8.4.2 Messages for Antenna Management Services. 26
8.5 Tx/Rx Chain Control Services. 26
8.5.1 Overview on Tx/Rx Chain Control Services . 26
8.5.2 Messages for Tx/Rx Chain Control Services . 26
8.6 RVM Protection Services . 27
8.6.1 Overview on RVM Protection Services . 27
8.6.2 Messages for RVM Protection Services . 28
8.7 Class Definitions for Interface . 28
Annex A (informative): Abstract Data Definitions . 31
Annex B (informative): gRRFI Qualification Methods for Validation . 35
History . 36
ETSI
4 ETSI EN 303 681-2 V1.1.2 (2020-06)
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 European Standard (EN) has been produced by ETSI Technical Committee Reconfigurable Radio Systems (RRS).
The present document is part 2 of a multi-part deliverable covering the Radio Equipment (RE) information models and
protocols, as identified below:
Part 1: "generalized Multiradio Interface (gMURI)";
Part 2: "generalized Reconfigurable Radio Frequency Interface (gRRFI)";
Part 3: "generalized Unified Radio Application Interface (gURAI)";
Part 4: "generalized Radio Programming Interface (gRPI)".
National transposition dates
Date of adoption of this EN: 22 June 2020
Date of latest announcement of this EN (doa): 30 September 2020
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 31 March 2021
Date of withdrawal of any conflicting National Standard (dow): 31 March 2021
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
5 ETSI EN 303 681-2 V1.1.2 (2020-06)
1 Scope
The present document defines an information model and protocol for generalized reconfigurable radio frequency
interface for reconfigurable REs except for reconfigurable mobile devices which are covered in [i.7] to [i.12]. The work
is based on the Use Cases defined in ETSI TR 103 585 [i.1], on the system requirements defined in ETSI
EN 303 641 [1] and on the radio reconfiguration related architecture for reconfigurable RE defined in ETSI
EN 303 648 [i.2].
The present document will be based on ETSI EN 303 146-2 [i.10] and provide a generalized interface definition for the
generalized Reconfigurable Radio Frequency Interface.
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 EN 303 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 585: "Reconfigurable Radio Systems (RRS); Radio Equipment (RE) reconfiguration
use cases".
[i.2] ETSI EN 303 648: "Reconfigurable Radio Systems (RRS); Radio Equipment (RE) reconfiguration
architecture".
[i.3] IEEE 1900.4™-2009: "IEEE Standard for Architectural Building Blocks Enabling Network-
Device Distributed Decision Making for Optimized Radio Resource Usage in Heterogeneous
Wireless Access Networks". ®
[i.4] DigRFSM Working Group: "MIPI Alliance Specification for DigRFSM v4".
[i.5] Recommendation ITU-T X.680: "Information technology - Abstract Syntax Notation One
(ASN.1): Specification of basic notation".
[i.6] 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
6 ETSI EN 303 681-2 V1.1.2 (2020-06)
[i.7] ETSI EN 302 969: "Reconfigurable Radio Systems (RRS); Radio Reconfiguration related
Requirements for Mobile Devices".
[i.8] ETSI EN 303 095: "Reconfigurable Radio Systems (RRS); Radio reconfiguration related
architecture for Mobile Devices (MD)".
[i.9] ETSI EN 303 146-1: "Reconfigurable Radio Systems (RRS); Mobile Device (MD) information
models and protocols; Part 1: Multiradio Interface (MURI)".
[i.10] ETSI EN 303 146-2: "Reconfigurable Radio Systems (RRS); Mobile Device (MD) information
models and protocols; Part 2: Reconfigurable Radio Frequency Interface (RRFI)".
[i.11] ETSI EN 303 146-3: "Reconfigurable Radio Systems (RRS); Mobile Device (MD) information
models and protocols; Part 3: Unified Radio Application Interface (URAI)".
[i.12] ETSI EN 303 146-4: "Reconfigurable Radio Systems (RRS); Mobile Device (MD) information
models and protocols; Part 4: Radio Programming Interface (RPI)".
[i.13] ETSI EN 303 681-1: "Reconfigurable Radio Systems (RRS); Radio Equipment (RE) information
models and protocols for generalized software reconfiguration architecture; Part 1: generalized
Multiradio Interface (gMURI)".
[i.14] ETSI EN 303 681-3: "Reconfigurable Radio Systems (RRS); Radio Equipment (RE) information
models and protocols for generalized software reconfiguration architecture; Part 3: generalized
Unified Radio Application Interface (gURAI)".
[i.15] ETSI EN 303 681-4: "Reconfigurable Radio Systems (RRS); adio Equipment (RE) information
models and protocols for generalized software reconfiguration architecture; Part 4: generalized
Radio Programming Interface (gRPI)".
3 Definition of terms, symbols and abbreviations
3.1 Terms
For the purposes of the present document, the following terms apply:
association: logical communication link to a Radio Access Network or a peer equipment
NOTE 1: Typically, some control signalling is necessary to maintain the association. No user data transfer may
occur with only an association present, but a data flow may be established into an association for this
purpose.
NOTE 2: Peer equipment is any communication counterpart of a reconfigurable Radio Equipment. It can be
reached by establishing a logical communication link (i.e. an association) between the reconfigurable
Radio Equipment and peer equipment.
channel: designated part of the information transfer capability having specified characteristics, provided at the user
network interface
NOTE: It is the over-the-air wireless propagation channel which is used to convey an information signal from
transmitter to receiver. This definition is specified in ETSI EN 303 648 [i.2].
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.
link: connection from one location to another through a given Radio Access Technology for the purpose of transmitting
and receiving digital information
NOTE: Each Link is conveyed over a given Channel.
ETSI
7 ETSI EN 303 681-2 V1.1.2 (2020-06)
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 (RC): part of Radio Equipment working under ROS control and on which RAs are executed
NOTE: A Radio Computer typically includes programmable processors, hardware accelerators, peripherals,
software, etc. RF part is considered to be part of peripherals.
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), Multiradio Controller (MRC) and Resource Manager (RM) which is
typically part of OS.
Radio Equipment (RE): "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".
NOTE: The definition above is as defined in the Radio Equipment Directive, Article 2(1)(1) [i.6].
Radio Frequency (RF) transceiver: part of radio platform converting, for transmission, baseband signals into radio
signals, and, for reception, radio signals into baseband signals
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
radio platform 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 components, hardware accelerators, RF transceiver, and antenna(s)
NOTE: A Radio Platform is a piece of hardware capable of generating RF signals or receiving RF signals. 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.
Radio Virtual Machine (RVM): abstract machine which supports reactive and concurrent executions
NOTE: An 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 mobile device: mobile device with radio communication capabilities providing support for radio
reconfiguration
NOTE: Reconfigurable mobile devices include but are not limited to: smartphones, feature phones, tablets, and
laptops.
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.
ETSI
8 ETSI EN 303 681-2 V1.1.2 (2020-06)
3.2 Symbols
Void.
3.3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ACK ACKnowledgement
ACKM ACKnowledgement with Modification
AP Application Processor
ASIC Application-Specific Integrated Circuit
ASN.1 Abstract Syntax Notation One
BBIC Base-Band Integrated Circuit
BLER Block Error Rate
CSL Communication Services Layer
EU European Union
gMURI generalized Multiradio Interface
gRPI generalized Radio Programming Interface
gRRFI generalized Reconfigurable Radio Frequency Interface
gURAI generalized Unified Radio Applications Interface
MIMO Multiple Input Multiple Output
MPM Mobility Policy Manager
NACK Negative ACKnowledgement
OOB Out Of Band
OS Operating System
RA Radio Application
RAN Radio Access Network
RAP Radio Application Package
RAT Radio Access Technology
RC Radio Computer
RCF Radio Control Framework
RCID Radio Computer Identification
RE Radio Equipment
RERC Radio Equipment Reconfiguration Class
RF Radio Frequency
RFIC Radio Frequency Integrated Circuit
ROS Radio Operating System
RRFI Reconfigurable Radio Frequency Interface
RVM Radio Virtual Machine
RX Reception
SINR Signal to Interference plus Noise Ratio
TR Technical Report
UML Unified Modeling Language
URA Unified Radio Applications
4 Introduction
A reconfigurable RE is capable of running multiple radios simultaneously, changing the set of radios by loading new
Radio Application Packages (RAP) and setting their parameters. All Radio Applications (RAs) are called Unified Radio
Applications (URAs) when they exhibit a common behaviour from the reconfigurable RE's point of view in ETSI
EN 303 648 [i.2]. In order to run multiple URAs, the reconfigurable RE will include Communication Services Layer
(CSL), Radio Control Frameworks (RCFs), Radio Platforms and 4 sets of interfaces for their interconnection.
ETSI
9 ETSI EN 303 681-2 V1.1.2 (2020-06)
Figure 4.1: Four sets of interfaces for reconfigurable RE
Figure 4.1 illustrates the reconfigurable RE architecture with the 4 sets of interfaces, i.e.:
• gMURI for interfacing CSL and RCF (in ETSI EN 303 681-1 [i.13]).
• gRRFI for interfacing URA and RF Transceiver, which is the scope of the present document.
• gURAI for interfacing URA and RCF (in ETSI EN 303 681-3 [i.14]).
• gRPI for allowing an independent and uniform production of RAs (in ETSI EN 303 681-4 [i.15]).
The present document defines gRRFI.
ETSI
10 ETSI EN 303 681-2 V1.1.2 (2020-06)
<< in t e rf a ce >>
IgM U R I
<< in t e rf a ce >>
IgRRF I
RadioComputer
<< in t e rf a ce >>
IgU R AI
<< in t e rf a ce>>
IgR PI
Figure 4.2: UML class diagram for RC interfaces
Figure 4.2 illustrates UML class diagram for RC interfaces. The reconfigurable RE may be seen as RCs where
individual URAs are engineered as software entities in ETSI EN 303 648 [i.2].
The present document is organized as follows:
• clause 5 describes the system identification;
• clause 6 describes the notational tool for defining both information model classes and interface classes;
• clause 7 describes the information model for RC; and
• clause 8 describes the interface definition.
While UML is used for defining the information model and protocol related to gRRFI, other modelling languages could
be used as well.
5 System Identification
5.1 Radio Computer Structure
Figure 5.1 illustrates how URA and RF Transceiver interacts with each other using gRRFI.
ETSI
11 ETSI EN 303 681-2 V1.1.2 (2020-06)
Figure 5.1: Interconnection between URA and RF Transceiver
using gRRFI for reconfigurable RE
As shown in figure 5.1, gRRFI can support up to 5 kinds of services depending on the applicable RERC [1].
A Reconfigurable RE shall support all the services as required by the corresponding RERC as shown in table 5.1 and
fully detailed in clause 8 of the present document. In case that a reconfigurable RE supports multiple RERCs, the
concerned reconfigurable RE shall support all the services as defined in table 5.1.
Table 5.1: Required services of gRRFI according to each RERC
Radio Equipment Antenna
Spectrum Power Control Tx/Rx Chain RVM Protection
Reconfiguration Management
Control services services Control services services
Class services
RERC-0 No No No No No
RERC-1 Yes Yes No No Yes
Yes
RERC-2, RERC-5 Yes Yes Yes Yes
(see note)
RERC-3, RERC-6 Yes Yes Yes Yes Yes
RERC-4, RERC-7 Yes Yes Yes Yes Yes
NOTE: Among the various Tx/Rx Chain Control services, only the service related with Tx/Rx timing is required in this
case.
A corresponding summary of the services is given below:
• Spectrum Control services
- These services are used to set up spectrum-related parameters such as carrier frequency, bandwidth,
sampling frequency, etc. that will be determined according to the URAs they are related to.
• Power Control services
- These services are used to set up RF power-related parameters such as maximum transmit (Tx) power
level, Tx power level per antenna, receive (Rx) gain, etc. Specific power schemes which have to be
controlled according to the communication circumstance around the reconfigurable RE are also included
in the Power Control services.
• Antenna Management services
- These services are used to determine the antenna configuration. Antenna radiation pattern, antenna gain,
antenna direction, sector configuration, polarization, frequency range, etc. are some factors to be
considered in the Antenna Management services.
NOTE: Antenna Management services depend on the configurability of the antenna.
ETSI
12 ETSI EN 303 681-2 V1.1.2 (2020-06)
• Tx/Rx Chain Control services
- These services are used to provide parameters related to real-time control of the RF transceiver chain.
Parameters to be controlled using the Tx/Rx Chain Control services include (but are not limited to) Tx
start/stop time, Rx start/stop time, spectrum- and/or power-related values.
• RVM Protection services
- These services are used to provide parameters related to the selection of RVM protection class.
Parameters to be controlled using the RVM Protection services include (but are not limited to) selection
and/or request of RF protection class as well as, RF Front-end indication of input data signals
modification.
The clauses 5.2 to 5.4 describe the components/entities shown in figure 5.1.
5.2 URA
RAs need to be subject to a common reconfiguration, multiradio execution and resource sharing strategy framework
(depending on the concerned RERC). Since all RAs exhibit a common behaviour from the reconfigurable RE
perspective, those RAs are called URAs [i.8].
5.3 RF Transceiver
RF Transceiver, which includes transceiver chain(s), is part of the radio platform in RC that transforms, in Tx mode, the
baseband signal to radio signal, and in Rx mode, the radio signal to baseband signal.
5.4 RF Interfaces
The RF Interfaces depicted in figure 5.1 denote digital interfaces which define the physical interconnections between
SM
base-band and RFIC (Radio Frequency Integrated Circuit), for example, the DigRF specification defining the
interface between an RFIC and a BBIC (Base-Band Integrated Circuit) in a radio equipment. gRRFI defined in the
present document complements such RF interfaces by defining services which are required for reconfigurable REs.
5.5 Radio Computer RF System Requirement Mapping
The Radio Computer components above described shall support the RF system requirements shown in table 5.2 and
described in clause 6.5 of ETSI EN 303 641 [1].
NOTE: The transceiver requirements defined in clauses 6.5.5, 6.5.6 and 6.5.8 of ETSI EN 303 648 [i.2] are not
related to the RF Interface defined in the present document and therefore do not appear in table 5.2.
Table 5.2: Mapping of RC Components to the system requirements described in ETSI EN 303 641 [1]
Entity/Component/Unit System Requirements [1] Comments
Unified Radio Applications R-FUNC-RFT-02 The requirement is described in clause 6.5.2 of [1].
RF Transceiver R-FUNC-RFT-03 The requirement is described in clause 6.5.3 of [1].
R-FUNC-RFT-04 The requirement is described in clause 6.5.4 of [1].
Reconfigurable RF Interface R-FUNC-RFT-01, The requirement is described in clauses 6.5.1 and
R-FUNC-RFT-07 6.5.7 of [1].
R-FUNC-RFT-09 The requirement is described in clause 6.5.9 of [1].
ETSI
13 ETSI EN 303 681-2 V1.1.2 (2020-06)
6 Notational Tools
6.1 Notational Tool for Information Model Classes
In the present document, information model classes are used as defined in annex B.1 of IEEE 1900.4-2009 [i.3].
6.2 Notational Tool for Interface Classes
Table 6.1 shows a template for defining interface classes for gRRFI. Each interface class for gRRFI will be defined in
clause 8.7 in accordance with the template shown in table 6.1.
Table 6.1: Template for defining Interface Classes
Class[(abstract class)]
OPERATIONS
Return type: Value type:
The template fields in table 6.1 are described below.
• is the name of the Class as it appears in the corresponding model. Additional information is also
included in case the class in question has been specified as an abstract one.
• OPERATIONS field describes the operations that have been defined in the class. More specifically:
- identifies the name of an operation, as it is included in the class definition.
- identifies the type of return value at the corresponding operation. Details related to the
ASN.1 module are specified in annex B of the present document.
- identifies the access levels for member functions: public, private, protected.
7 Information Model for Radio Computer
7.1 Radio Computer
Figure 7.1 shows the UML class diagram for RC classes related to gRRFI which are required to support Software
Reconfiguration.
ETSI
14 ETSI EN 303 681-2 V1.1.2 (2020-06)
<>
IgR RF I
Radio Co mpu te r
- RCID: Name Type
RCMe asure m ents
R CC apabi lit i es
-listOfActiveMeasurements:
1 -listOfSupportedOptions: RCOptions
ActiveMeasurementsList
-listOfSupportedRadioInterfaces:
RadioInterfaces
-listOfSupportedChannels: ChannelIDs
-hardwareProfile: HardwareInfo
-softwareProfile: SoftwareInfo
R CC onfi gurat io n
Ch an ne l
0.*
Ch ann e lPr ofil e
Link
-channelID: NameType
0.*
-channelFrequecyRange:
FrequencyRange
-radioInterface:
RadioInterface
RFC onf iguration -cellID: NameType
L ink Pro file
-linkID: NameType
-cellID: NameType
-associatedChannelID:
Ch ann e lMe as ur em en t s
Tx P at h
OptiaonlObjectName
-linkDirection : Direction -listOfChannelMeasurements:
-txStartTime: TxStartTime
0,1
ChannelMeasurementsList
-CarrierFrequecy: Frequency
-txStopTime: TxStopTime
-nominalRFPower: -appliedMeasurementConfiguration:
AnaloguePower C on fig ura t io nMe s u re men t s
-samplingRate: SamplingRate
RxPath
-bandwidth: Bandwidth
-rxStartTime: RxStartTime
Antenn a
-rxStopTime: RxStopTime
1.*
L ink M e asure m ent s
-receiveBLER: RxBLER
-trasmitPower: TxPower Antenn aProfi le
-receiveSINR: RxSINR
-antennaID:
-transmittedBits: TxBits
NameType
Figure 7.1: UML class diagram for RC classes related to gRRFI
The RC classes related to gRRFI are defined as follows:
• RadioComputer
- This class contains all URA(s) related information about resources and interactions related to hardware
and software of a reconfigurable RE, for example, computational/spectral resource usage, collection of
context information, channel measurement results, etc.
ETSI
15 ETSI EN 303 681-2 V1.1.2 (2020-06)
• RCCapabilities
- This class contains information about RC capabilities including hardware, software, transmission and
measurement capabilities such as supported RATs and maximum transmission power. Each instance of
RadioComputer class shall have only one instance of RCCapabilities class as a member.
• Channel
- This class contains one radio channel that may or may not be used by an active radio link. Each instance
of RadioComputer class can have zero, one or several instances of Channel class as members (0.*). In
case of an active radio link, at least one Channel class is available.
• ChannelProfile
- This class contains general information about the radio channel such as channel ID, centre frequency,
bandwidth, and used RAT. Each instance of Channel class shall have only one instance of Channel
Profile class as a member.
• ChannelMeasurements
- This class contains current measurements (instantaneous measurement data and related metadata) and the
applied measurement configuration related to this radio channel such as interference and load
measurements. Each instance of Channel class shall have only one instance of ChannelMeasurements
class as a member.
• Antenna
- This class contains information about antenna selection. Each instance of Link class shall have at least
one instance of Antenna class as a member (1.*).
• AntennaProfile
- This class contains general information about this antenna, such as antenna port, applicable frequency
range and antenna gain. Each instance of Antenna class shall have only one instance of AntennaProfile
class as a member.
• RCConfiguration
- This class contains information about the current configuration of RC. Each instance of RadioComputer
class shall have only one instance of RCConfiguration class as a member.
• Link
- This class contains information about one active URA and the corresponding connection between the
reconfigurable RE and the Radio Access Network (RAN). Each instance of RCConfiguration class has
zero, one or several instances of Link class as members (0.*). Each instance of Link class is associated
with one instance of Channel class.
• LinkProfile
- This class contains general information about this active connection, for example, link Identification
(ID), serving cell ID, channel used, etc. Each instance of Link class shall have only one instance of
LinkProfile class as a member.
• LinkMeasurements
- This class contains current measurements (instantaneous measurement data and related metadata) related
to this active connection, such as Block Error Rate (BLER), power, and Signal to Interference plus Noise
Ratio (SINR) measurements. Each instance of Link class shall have only one instance of
LinkMeasurements class as a member.
• RFConfiguration
- This class contains information about the configuration of the RF transceiver. Each instance of Link class
shall have only one instance of RFConfiguration class as a member.
ETSI
16 ETSI EN 303 681-2 V1.1.2 (2020-06)
• TxPath
- This class contains information about one transmit path. Each instance of RFConfiguration class has zero
or one instance of TxPath class as a member (0,1).
• RxPath
- This class contains information about one receive path. Each instance of RFConfiguration class shall
have only one instance of RxPath class as a member.
• RCMeasurements
- This class contains current measurements (instantaneous measurement data and related metadata) related
to reconfigurable RE such as battery capacity, user mobility, RE location determination, and connection
history information. Each instance of RadioComputer class shall have only one instance of
RCMeasurements class as a member.
NOTE: The Channel Class is separate from the Link Class, but the Channel Measurements may be based on any
RE configuration which may or may not be used for the final Link Configuration.
7.2 Class Definitions for Information Model
Each class of RC can be defined using the template presented in clause 6.1 and in accordance with the UML diagram of
figure 7.1 which specifies the relations among all the classes of RC. RC classes defined in this way are shown in
tables 7.1 to 7.15.
Table 7.1: RadioComputer Class
Class RadioComputer
This class contains all URA related information about resources and interactions related to hardware
and software of a reconfigurable RE.
DERIVED FROM
ATTRIBUTES
Value type: Possible access: Default value:
RCID
Field Read-Write Not specified
This attribute describes ID of a Radio Computer.
CONTAINED IN
RCCapabilities [1], RCConfiguration [1], RCMeasurements [1],
CONTAINS
Channel [0.*]
SUPPORTED EVENTS
ETSI
17 ETSI EN 303 681-2 V1.1.2 (2020-06)
Table 7.2: RCCapabilities Class
Class RCCapabilities
This class contains information about RC capabilities including hardware, software, transmission and
measurement capabilities.
DERIVED FROM
ATTRIBUTES
Value type: Possible access: Default value:
listOfSupportedOptions
RCOptionsList Read-Write Not specified
This attribute describes a list of supported options.
Value type: Possible access: Default value:
listOfSupportedRadioInterfaces
RadioInterfacesList Read-Write Not specified
This attribute describes radio interfaces supported by this RC.
Value type: Possible access: Default value:
listOfSupportedChannels
ChannelIDsList Read-Write Not specified
This attributes describes frequency channels supported by this RC.
Value type: Possible access: Default value:
hardwareProfile
HardwareInfo Read-Write Not specified
This attributes describes hardware capabilities of this RC.
Value type: Possible access: Default value:
softwareProfile
SoftwareInfo Read-Write Not specified
This attributes describes software capabilities of this RC.
CONTAINED IN RadioComputer
CONTAINS
SUPPORTED EVENTS
Table 7.3: Channel Class
Class Channel
This class describes one frequency channel that may or may not have active connections on it.
DERIVED FROM
ATTRIBUTES
CONTAINED IN RadioComputer
CONTAINS ChannelProfile [1], ChannelMeasurements [1], Antenna [1.*]
SUPPORTED EVENTS
Table 7.4: ChannelProfile Class
Class ChannelProfile
This class contains general information about this frequency channel.
DERIVED FROM
ATTRIBUTES
Value type: Possible access: Default value:
channelID
NameType Read Not specified
This attribute describes ID of channel.
Value type: Possible access: Default value:
channelFrequencyRange
FrequencyRange Read Not specified
This attribute describes a value of channel frequency range.
Value type: Possible access: Default value:
radioInterface
RadioInterface Read Not specified
This attribute describes a radio interface.
Value type: Possible access: Default value:
cellID
NameType Read Not specified
This attribute describes ID of connected cell.
CONTAINED IN Channel
CONTAINS
SUPPORTED EVENTS
ETSI
18 ETSI EN 303 681-2 V1.1.2 (2020-06)
Table 7.5: ChannelMeasurements Class
Class ChannelMeasurements
This class contains current measurements related to this frequency channel.
DERIVED FROM
ATTRIBUTES
Default
Value type: Possible access:
listOfChannelMeasurements
value:
ChannelMeasurementsList Read
Not specified
This attribute describes a list of channel measurements.
Default
Value type: Possible access:
appliedMeasurementsConfiguration value:
ConfigurationMeasurements Read
Not specified
This attribute describes configuration option of the RE, e.g. which Antenna(s) have been used, which
RF front-end(s) have been used, etc.
CONTAINED IN Channel
CONTAINS
SUPPORTED EVENTS
Table 7.6: Antenna Class
Class Antenna
This class contains information about antenna selection.
DERIVED FROM
ATTRIBUTES
CONTAINED IN Channel
CONTAINS AntennaProfile [1]
SUPPORTED EVENTS
Table 7.7: AntennaProfileClass
Class AntennaProfile
This class contains general information about this antenna.
DERIVED FROM
ATTRIBUTES
Value type: Possible access: Default value:
antennaID
NameType Read Not specified
This attribute describes ID of antenna.
CONTAINED IN Antenna
CONTAINS
SUPPORTED EVENTS
Table 7.8: RCConfigurationClass
Class RCConfiguration
This class contains information about the current configuration of RC.
DERIVED FROM
ATTRIBUTES
CONTAINED IN RadioComputer
CONTAINS Link [0.*]
SUPPORTED EVENTS
ETSI
19 ETSI EN 303 681-2 V1.1.2 (2020-06)
Table 7.9: LinkClass
Class Link
This class contains information about one active Radio Application and corresponding connection
between Reconfigurable Radi
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...