ETSI TS 103 655-1 V1.2.1 (2022-09)

Reconfigurable Radio Systems (RRS); Radio Interface Engine (RIE); Part 1: Technical requirements

RTS/RRS-0153

General Information

• Status: Not Published
• Technical Committee: RRS 1 - RRS System Aspects & Cognitive functionalities
• Current Stage: 12 - Completion
• Due Date: 30-Sep-2022
• Completion Date: 22-Sep-2022

Standards Content (Sample)

ETSI TS 103 655-1 V1.2.1 (2022-09)






TECHNICAL SPECIFICATION
Reconfigurable Radio Systems (RRS);
Radio Interface Engine (RIE);
Part 1: Technical requirements

---------------------- Page: 1 ----------------------
2 ETSI TS 103 655-1 V1.2.1 (2022-09)

Reference
RTS/RRS-0153
Keywords
mobile, radio, requirements, system

ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - APE 7112B
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° w061004871

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
If you find a security vulnerability in the present document, please report it through our
Coordinated Vulnerability Disclosure Program:
https://www.etsi.org/standards/coordinated-vulnerability-disclosure
Notice of disclaimer & limitation of liability
The information provided in the present deliverable is directed solely to professionals who have the appropriate degree of
experience to understand and interpret its content in accordance with generally accepted engineering or
other professional standard and applicable regulations.
No recommendation as to products and services or vendors is made or should be implied.
No representation or warranty is made that this deliverable is technically accurate or sufficient or conforms to any law
arranty is made of merchantability or fitness
and/or governmental rule and/or regulation and further, no representation or w
for any particular purpose or against infringement of intellectual property rights.
In no event shall ETSI be held liable for loss of profits or any other incidental or consequential damages.

Any software contained in this deliverable is provided "AS IS" with no warranties, express or implied, including but not
limited to, the warranties of merchantability, fitness for a particular purpose and non-infringement of intellectual property
rights and ETSI shall not be held liable in any event for any damages whatsoever (including, without limitation, damages
for loss of profits, business interruption, loss of information, or any other pecuniary loss) arising out of or related to the use
of or inability to use the software.
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 2022.
All rights reserved.

ETSI

---------------------- Page: 2 ----------------------
3 ETSI TS 103 655-1 V1.2.1 (2022-09)
Contents
Intellectual Property Rights . 4
Foreword . 4
Modal verbs terminology . 4
Introduction . 5
1 Scope . 6
2 References . 6
2.1 Normative references . 6
2.2 Informative references . 6
3 Definition of terms, symbols and abbreviations . 7
3.1 Terms . 7
3.2 Symbols . 7
3.3 Abbreviations . 8
4 Requirement Organization and Methodology . 8
4.1 Requirement Organization. 8
4.2 Requirement Format . 9
4.3 Requirement Formulation . 9
5 Working Assumptions . 9
6 Functional System Requirements . 10
6.1 Requirements for radio and hardware processing resources . 10
6.1.1 R-FUNC-RHR-01: Reconfiguration for each WD . 10
6.1.2 R-FUNC-RHR-02: Reconfiguration between WDs . 10
6.2 Requirements for functions supporting the reconfiguration . 10
6.2.1 R-FUNC-REC-01: Gathering and processing function . 10
6.2.2 R-FUNC-REC-02: Support of trigger events for reconfiguration. 10
6.2.3 R-FUNC-REC-03: Support for reconfiguration function . 11
6.2.4 R-FUNC-REC-04: Support for execution function . 11
6.2.5 R-FUNC-REC-05: Support of learning function . 11
6.2.6 R-FUNC-REC-06: Support of information provisioning function . 11
6.3 Requirements for mobile device mobility and connectivity management . 11
6.3.1 R-FUNC-MOB-01: Mobility management of the WDs . 11
6.3.2 R-FUNC-MOB-02: Connectivity management of the WDs . 12
6.3.3 R-FUNC-MOB-03: Scalability of connections of the WDs . 12
6.3.4 R-FUNC-MOB-04: Support of authentication . 12
7 Key Performance Requirements . 12
7.1 Key Performance Indicators for Communications . 12
7.1.1 R-PERF-KPI-COM-01: Selecting the best PHY/MAC of the communication system . 12
7.1.2 R-PERF-KPI-COM-02: Reliability of the communication link. 13
7.1.3 R-PERF-KPI-COM-03: Selection of power compliant processing units . 13
7.1.4 R-PERF-KPI-COM-04: Preselecting relevant sensor data . 13
7.2 Key Performance Indicators for Context Information . 13
7.2.1 R-PERF-KPI-CON-01: Accuracy of the localization estimation. 13
7.2.2 R-PERF-KPI-CON-02: Integrity of the localization performance. 13
7.2.3 R-PERF-KPI-CON-03: Geometric constellation of WD . 13
7.2.4 R-PERF-KPI-CON-04: Sensor reliability . 14
7.2.5 R-PERF-KPI-CON-05: Spectrum requirements . 14
7.2.6 R-PERF-KPI-CON-06: Waveform adaptations . 14
7.2.7 R-PERF-KPI-CON-07: Location methods . 14
7.2.8 R-PERF-KPI-CON-08: Horizontal and vertical accuracy performance . 14
Annex A (informative): RIE Instantiation of Location-Based Spectrum Sharing . 15
History . 18


ETSI

---------------------- Page: 3 ----------------------
4 ETSI TS 103 655-1 V1.2.1 (2022-09)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The declarations
pertaining to these essential IPRs, if any, are 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 Directives including the ETSI IPR Policy, no investigation regarding the essentiality of IPRs,
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.
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.
Foreword
This Technical Specification (TS) has been produced by ETSI Technical Committee Reconfigurable Radio
Systems (RRS).
The present document is part 1 of a multi-part deliverable covering the Radio Interface Engine (RIE), as identified
below:
Part 1: "Technical requirements";
Part 2: "Architecture".
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.
Introduction
The radio interface engine comprises context information and communication needs to improve both depending on the
demands. In ETSI TR 103 587 [i.1], several use cases are identified and described that are used as base for the
requirements of the radio interface engine. The concept demands requirements for a future architecture of the radio
interface engine. The requirements are split into two categories: the functional and the performance requirements. The
functional requirements consist of three groups. These are the radio and hardware processing resources, the functions
that are supporting the reconfiguration and the mobile device mobility and connectivity management.
ETSI

---------------------- Page: 4 ----------------------
5 ETSI TS 103 655-1 V1.2.1 (2022-09)
The performance requirements comprise communication as well as context information indicators. Context information
includes positioning performance indicators and is proposed in 3GPP TR 22.872 [i.2] where positioning relevant KPIs
are identified. The context information performance KPIs steer the potential of the radio interface engine to improve
and reach the communication performance requirements of the network.

ETSI

---------------------- Page: 5 ----------------------
6 ETSI TS 103 655-1 V1.2.1 (2022-09)
1 Scope
The present document specifies the system requirements for Reconfigurable Radio Systems operating in different
environments and bands to apply the concept of the radio interface engine that is introduced in ETSI TR 103 587 [i.1]
together with use cases comprising different key performance indicators in radio systems.
The documented key performance indicators are described and followed by the requirements on the wireless systems
which are structured in the following requirement categories:
• Requirements for radio and hardware processing resources.
• Requirements for functions supporting the reconfiguration.
• Requirements for mobile device mobility and connectivity management.
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.
Not applicable.
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 587: "Reconfigurable Radio Systems (RRS); Feasibility study of a Radio Interface
Engine (RIE)".
[i.2] 3GPP TR 22.872 (V16.1.0): "Study on positioning use cases (Release 16)", SA WG1.
[i.3] ETSI TS 103 154 (V1.1.1): "Reconfigurable Radio Systems (RRS); System requirements for
operation of Mobile Broadband Systems in the 2 300 MHz - 2 400 MHz band under Licensed
Shared Access (LSA)".
[i.4] TEDDI database: TErms and Definitions Database Interactive (TEDDI).
NOTE: Available at https://webapp.etsi.org/Teddi/.
[i.5] Void.
ETSI

---------------------- Page: 6 ----------------------
7 ETSI TS 103 655-1 V1.2.1 (2022-09)
[i.6] ETSI TS 103 652-1: "Reconfigurable Radio Systems (RRS); evolved Licensed Shared Access
(eLSA); Part 1: System requirements".
3 Definition of terms, symbols and abbreviations
3.1 Terms
For the purposes of the present document, the following terms apply:
allowance zone: geographical area within which a radio equipment is allowed to operate radio transmitters on its
assigned spectrum resource
NOTE 1: An allowance zone is defined using specific measurement quantities and thresholds, e.g. a maximum field
strength level expressed in dBµ V/m/MHz, along the border of its geographical area.
NOTE 2: An allowance zone is normally applicable for a defined frequency range and time period.
NOTE 3: The term of "allowance zone" as used here is an extension of the term used in [i.6].
exclusion zone: geographical area within which only designated incumbent technologies are allowed to have active
radio transmitters
NOTE 1: An exclusion zone is normally applicable for a defined frequency range and time period.
NOTE 2: The term of "exclusion zone" as used here is an extension of the term used in [i.6].
incumbent: current holder of spectrum rights of use
protection zone: geographical area within which incumbent receivers will not be subject to harmful interference caused
by unauthorized radio equipment transmissions
NOTE 1: A protection zone is defined using specific measurement quantities and thresholds (e.g. a mean field
strength that does not exceed a defined value in dBµ V/m/MHz at a defined receiver antenna height above
ground level). A protection zone is normally applicable for a defined frequency range and time period.
NOTE 2: The term of "protection zone" as used here is an extension of the term used in [i.6].
radio equipment: product or relevant component thereof capable of communication by means of the emission and/or
reception of radio waves utilizing the spectrum allocated to terrestrial/space radio communication
NOTE: This definition is taken from the TEDDI database [i.4].
restriction zone: geographical area within an allowance zone where a radio equipment has to operate under certain
additional restrictive conditions (e.g. maximum EIRP limits and/or constraints on antenna parameters)
NOTE 1: A restriction zone is normally applicable for a defined frequency range and time period.
NOTE 2: The term of "restriction zone" as used here is an extension of the term used in [i.3].
spectrum resource: resource or set of resources defined in time, space and frequency domains
3.2 Symbols
Void.
ETSI

---------------------- Page: 7 ----------------------
8 ETSI TS 103 655-1 V1.2.1 (2022-09)
3.3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
3GPP 3G (mobile) Partnership Project
COM Communications
CON Context
dBµ deciBel relative to one microvolt
EIRP Effective Isotropic Radiated Power
EU European Union
FPGA Field Programmable Gate Array
FUNC Functional aspects
GNSS Global Navigation Satellite System
GPP General Purpose Processor
HPR Hardware Processing Resources
ID IDentifier
KPI Key Performance Indicator
LB Location-Based
LTE-U Long Term Evolution-Unlicensed
MAC Message Authentication Code
MOB Mobility aspects
PERF Performance aspects
PHY PHYsical layer
QoS Quality of Service
RBS Random Binary Sequence
RE Radio Equipment
REC Reconfiguration aspects
R-FUNC Requirements Function
RHR Radio and Hardware Resources
RIE Radio Interface Engine
R-PERF Performance Requirements
RR Radio Resources
RRS Reconfigurable Radio Systems
TEDDI TErms and Definitions Database Interactive
TR Technical Report
TS Technical Specification
WD Wireless Device
Wi-Fi Wireless Fidelity
4 Requirement Organization and Methodology
4.1 Requirement Organization
The requirements are organized into two categories. Category one defines the function requirements and category two
the performance requirements. Both categories are further split up into different groups. Figure 1 visualizes the
categories and its enclosed groups.
ETSI

---------------------- Page: 8 ----------------------
9 ETSI TS 103 655-1 V1.2.1 (2022-09)

Figure 1: Requirements Operations
4.2 Requirement Format
A letter code is defined to uniquely identify each requirement R. It is constructed as follows:
• R-:standard requirement prefix.
• :
Code Category
FUNC Functional aspects
PERF Performance aspects

• : Requirement group identifier. A three letter code will be used for this identifier.
• : Requirement identifier within requirement group; range 01  99.
EXAMPLE: R-FUNC-RHR-01: Requirements-Function-Radio_and_Hardware_Resources_01.
4.3 Requirement Formulation
A requirement is formulated in such a way that it is uniquely defined. It is built as follows:
• Title: </br> 5 Working Assumptions</br> The working assumptions described below are based on ETSI TR 103 587 [i.1]. There a radio interface engine is</br> defined to comprise the following use cases which all rely on context information, such as current and predictive</br> location information of the wireless device:</br> • Decision making based on context information of either the mobile device or the base station identifying if a</br> single or multiple links are best.</br> ETSI</br> </br> ---------------------- Page: 9 ----------------------</br> 10 ETSI TS 103 655-1 V1.2.1 (2022-09)</br> • User circumstance trigger context information management that adapts the communication KPIs.</br> • Considering context information to download and install a different PHY/MAC protocol of wireless devices.</br> • Tracking context information to decide where the processing unit shall be executed.</br> • Considering context information to adapt PHY and MAC to improve the location estimation of the WD</br> iteratively further.</br> Relevant performance indicators are categorized in two groups:</br> • Communications performance indicators, such as data rate, latency, spectrum and power efficiency.</br> • Context information performance indicators, such as waveform, location accuracy, integrity of sensor data,</br> and used spectrum for ranging and outdated sensor data.</br> 6 Functional System Requirements</br> 6.1 Requirements for radio and hardware processing resources</br> 6.1.1 R-FUNC-RHR-01: Reconfiguration for each WD</br> The system shall support the reconfiguration of both the Hardware Processing Resources (HPR) and the Radio</br> Resources (RR) for each supported Wireless Device (WD).</br> Explanation: The system should be able to perform resource reconfiguration of both the hardware processing</br> resources and the radio resources for each supported WD. The radio resources assigned to each</br> supported WD can be dynamically modified, which includes bandwidth, frequencies, power levels,</br> spectrum masks, etc. Meanwhile, the percentage of hardware processing resources devoted to each</br> supported WD should be dynamically modified. For example, sufficient HPR should be</br> configured to a WD when a new channel is assigned to it.</br> 6.1.2 R-FUNC-RHR-02: Reconfiguration between WDs</br> The system shall support reconfiguration of both HPR and RR between different WDs.</br> Explanation: The system can reconfigure multiple WDs with flexibility in terms of the percentage of HPR and</br> RR between different WDs according to the status of the network.</br> 6.2 Requirements for functions supporting the reconfiguration</br> 6.2.1 R-FUNC-REC-01: Gathering and processing function</br> The system shall support a gathering and processing function to gather and process radio related metrics and</br> parameters.</br> Explanation: After having gathered radio related metrics and parameters, the gathering and processing function</br> may process them to make decisions on reconfiguration in order to optimize radio performance.</br> The identification of the radio related metrics and parameters which can be used for</br> reconfiguration purposes may vary according the specific use case. These are expected to include</br> traffic variations, channel bandwidth, interference, transmit power and QoS.</br> 6.2.2 R-FUNC-REC-02: Support of trigger events for reconfiguration</br> The system shall support trigger events for reconfiguration.</br> ETSI</br> </br> ---------------------- Page: 10 ----------------------</br> 11 ETSI TS 103 655-1 V1.2.1 (2022-09)</br> Explanation: Trigger events are described by certain parameters (e.g. thresholds, hysteresis) in order to define</br> the condition under which an event is happening. When one or more events occur, the system</br> starts to evaluate the need for a possible reconfiguration.</br> 6.2.3 R-FUNC-REC-03: Support for reconfiguration function</br> The system shall support a reconfiguration function to make decisions for radio resource reconfiguration and inform</br> RBSs to perform the reconfiguration e.g. triggered by events in clause 6.2.2.</br> Explanation: The reconfiguration function shall make radio resource reconfiguration decisions such as,</br> reconfiguration time, reconfigured RATs, frequency bands allocation and adding/dropping carrier</br> frequencies at RBSs.</br> 6.2.4 R-FUNC-REC-04: Support for execution function</br> The system shall support the execution function in order to perform the reconfiguration.</br> Explanation: The system WDs should support mechanisms in order to be reconfigured according to the</br> reconfiguration decision of the reconfiguration function.</br> EXAMPLE: An example is to exchange location estimates between WDs to improve the estimation process on</br> the receiver itself.</br> 6.2.5 R-FUNC-REC-05: Support of learning function</br> The system shall support a learning function to improve and optimize the reconfiguration decisions.</br> Explanation: For example, the learning capability may consist in monitoring the performance of the system after</br> each reconfiguration and verifying whether the decisions meet or not the reconfiguration target.</br> Another possibility is to learn about the causes that trigger a particular reconfiguration by</br> memorizing the situation; if such causes happen again, the reconfiguration that should be</br> performed is already known.</br> 6.2.6 R-FUNC-REC-06: Support of information provisioning function</br> The system shall support an information provisioning function to provide updated network configuration information to</br> the appropriate system devices.</br> Explanation: After a reconfiguration, the information related to the new network configuration and policies are</br> expected to be efficiently provided to the system devices (only the ones affected by the</br> reconfiguration) in order to minimize the control plane overhead due to the reconfiguration.</br> 6.3 Requirements for mobile device mobility and connectivity</br> management</br> 6.3.1 R-FUNC-MOB-01: Mobility management of the WDs</br> The system shall guarantee the mobility management of the WDs.</br> Explanation: Network reconfiguration (e.g. change of WD in currently used band or starting operations in a new</br> band using a WD already deployed or a new WD) may imply the change of radio parameters, such</br> as neighbour cells relation information (e.g. the neighbour cells IDs, the neighbour cells operating</br> frequency, etc.) affecting the cell selection/reselection of WDs in idle mode. The mobility</br> management is guaranteed by providing such updated information to the WDs.</br> ETSI</br> </br> ---------------------- Page: 11 ----------------------</br> 12 ETSI TS 103 655-1 V1.2.1 (2022-09)</br> 6.3.2 R-FUNC-MOB-02: Connectivity management of the WDs</br> The system shall manage the connectivity of the WDs during the reconfiguration.</br> Explanation: When a WD is in connected mode and operating on radio resources that may be reconfigured, an</br> appropriate decision has to be evaluated by the system in order to maintain the connectivity of the</br> involved WDs. In the following, different examples of approaches are depicted according to the</br> WDs capabilities:</br> In order to support connectivity of WDs that are only able to operate on WD "a" in band "x",</br> sufficient radio resource in band "x" may be maintained for WD "a" in band "x". In order to</br> support WDs capable of operating on WD "a" or WD "b" in band "x" and which are in connected</br> mode on WD "a" in band "x", it may be evaluated if the connectivity currently provided to the</br> WDs on WD "a" could be provided also on WD "b" performing handover from WD "a" to WD "b"</br> before the reconfiguration from WD "a" to WD "b" on band "x".</br> In order to</br> <b>...</b>