ETSI TS 103 655-2 V1.1.1 (2021-02)

Reconfigurable Radio Systems (RRS); Radio Interface Engine (RIE); Part 2: Architecture

DTS/RRS-0149-2

General Information

• Status: Not Published
• Technical Committee: RRS 1 - RRS System Aspects & Cognitive functionalities
• Current Stage: 12 - Completion
• Due Date: 08-Mar-2021
• Completion Date: 26-Feb-2021

Standards Content (Sample)

ETSI TS 103 655-2 V1.1.1 (2021-02)






TECHNICAL SPECIFICATION
Reconfigurable Radio Systems (RRS);
Radio Interface Engine (RIE);
Part 2: Architecture

---------------------- Page: 1 ----------------------
2 ETSI TS 103 655-2 V1.1.1 (2021-02)



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

Tel.: [phone]  Fax: [phone]

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

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

© ETSI 2021.
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

---------------------- Page: 2 ----------------------
3 ETSI TS 103 655-2 V1.1.1 (2021-02)
Contents
Intellectual Property Rights . 4
Foreword . 4
Modal verbs terminology . 4
Introduction . 4
1 Scope . 6
2 References . 6
2.1 Normative references . 6
2.2 Informative references . 6
3 Definition of terms, symbols and abbreviations . 6
3.1 Terms . 6
3.2 Symbols . 6
3.3 Abbreviations . 7
4 Architectural Reference Model for Radio Interface Engine . 7
4.1 Introduction . 7
4.2 Architecture Reference Model (Option 1) . 7
4.3 Architecture Reference Model (Option 2) . 9
4.4 Architecture Reference Model (Option 3) . 9
4.5 Mapping of Architectural Components to the system requirements . 10
5 Reference Points . 11
6 Service Access Points . 12
6.1 Introduction . 12
6.2 SAPs required for RIEF_SAP . 12
6.3 SAPs required for RIEF_LINK_SAP . 12
6.4 SAPs required for IN_LINK_SAP . 12
6.5 SAPs required for INF_VAL_SAP . 12
7 High level operating procedures . 13
7.1 Procedures for Network requesting information from Radio Interface Engine Function (Option 1) . 13
7.2 Procedures for Network requesting information from Radio Interface Engine Function (Option 2) . 13
7.3 Procedures for Network requesting information from Radio Interface Engine Function (Option 3) . 14
History . 15


ETSI

---------------------- Page: 3 ----------------------
4 ETSI TS 103 655-2 V1.1.1 (2021-02)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (https://ipr.etsi.org/).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
Foreword
This Technical Specification (TS) has been produced by ETSI Technical Committee Reconfigurable Radio Systems
(RRS).
The present document is part 2 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 gathers and manages access to context information in a technology neutral way with the
objective to optimize the configuration of any radio interface.
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.
In ETSI TS 103 655-1 [1], the performance requirements are defined which comprise communication as well as context
information indicators. Context information includes positioning performance indicators and is proposed in 3GPP R16
where positioning relevant KPIs are identified [i.2]. 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: 4 ----------------------
5 ETSI TS 103 655-2 V1.1.1 (2021-02)
The present document builds on ETSI TR 103 587 [i.1], as well as ETSI TS 103 655-1 [1], defines the corresponding
Radio Interface Engine system architecture.

ETSI

---------------------- Page: 5 ----------------------
6 ETSI TS 103 655-2 V1.1.1 (2021-02)
1 Scope
The scope of the present document is to define the Radio Interface Engine related system architecture. The work is
based on the system requirements defined in ETSI TS 103 655-1 [1], and the feasibility study including Use Cases
defined in ETSI TR 103 587 [i.1].
2 References
2.1 Normative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found at
https://docbox.etsi.org/Reference.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are necessary for the application of the present document.
[1] ETSI TS 103 655-1: "Reconfigurable Radio Systems (RRS); Radio Interface Engine (RIE); Part 1:
Technical 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 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.
TM
[i.3] IEEE 802.2 : "ISO/IEEE International Standard - Information processing systems - Local area
networks - Part 2: Logic Link Control".
3 Definition of terms, symbols and abbreviations
3.1 Terms
Void.
3.2 Symbols
Void.
ETSI

---------------------- Page: 6 ----------------------
7 ETSI TS 103 655-2 V1.1.1 (2021-02)
3.3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
GNSS Global Navigation Satellite System
LLC Logical Link Control
MAC Medium Access Control
PER Packet Error Rates
PHY Physical Layer
QoS Quality of Service
RAT Radio Access Technology
RIE Radio Interface Engine
RIEF Radio Interface Engine Function
RLC Radio Link Control
RSS Radio Signal Strength
SAP Service Access Point
WD Wireless Device
4 Architectural Reference Model for Radio Interface
Engine
4.1 Introduction
The present clause introduces three options for the architectural reference model for the Radio Interface Engine. One of
the three options shall be selected for implementation:
• Option 1: A general basic approach of an architecture reference model is proposed including the Radio
Interface Engine Function (RIEF), Information Functions and the lower layers of the related communication
systems which are accessing to the RIEF. No Information Validation Function is introduced.
• Option 2: The general basic approach of an architecture reference model is complemented by an Information
Validation Function which allows to verify the validity of acquired context information.
• Option 3: A variant of option 2 is introduced. The Information Validation Function is part of the RIEF.
4.2 Architecture Reference Model (Option 1)
The Radio Interface engine is interacting with Layer-1 (physical layer), and Layer-2 (medium access control layer) as
well as logical link control (LLC) layers such as IEEE 802.2 [i.3] LLC or 3GPP Radio Link Control (RLC).
P
Information A
S
P
_
A
K
S
Function 1 N
I _
L F
_ Layer 3 and above
E
I
N
(e.g. location)
I R
Radio
Interface
...
LLC_RLC_SAP
LLC_RLC_SAP
Engine
Function
P
A P
S
Network 1 A
Information
P _ S
(RIEF)
K _ Network N
A
S N K
I
_ (e.g., 3GPP
Function K N
L .
I
K
_
L
(e.g., WiFi)
N F
_
I
E
F
L I Rel. 14)
(e.g. wireless E
_
R I
N R
I
context)

Figure 1: Option 1 - general basic approach
ETSI

---------------------- Page: 7 ----------------------
8 ETSI TS 103 655-2 V1.1.1 (2021-02)
The various building blocks and Service Access Points (SAP) are as follows:
• The "Information Function" components 1, 2, …, K gather cognitive context information of potential interest
to a communication component. The information may include information such as localization information
(e.g. GNSS information), information of wireless context (e.g. which Radio Access Technologies (RATs) are
TM TM TM
present (LTE , WiFi , 5G , etc.), which Quality-of-Service is provided by specific RATs (e.g. Radio
Signal Strength (RSS) measurements, observed Packet Error Rates (PER), observed round-trip latencies, etc.).
• The "Radio Interface Engine Function" (RIEF) component is interacting with the "Information Function"
components through the "IN_LNK_SAP" Service Access Point. RIEF typically requests information (pull
mode) from a specific "Information Function" component and then obtains the result. Alternatively, the
information may be provided by the respective "Information Function" component without a specific request
(push mode), for example when a specific event is happening (e.g. observed QoS metrics such as
RSS/PER/latency is changing, etc.).
...