ETSI EN 303 095 V1.3.1 (2018-05)
Reconfigurable Radio Systems (RRS); Radio reconfiguration related architecture for Mobile Devices (MD)
Reconfigurable Radio Systems (RRS); Radio reconfiguration related architecture for Mobile Devices (MD)
REN/RRS-0216
Radijski sistemi z možnostjo preoblikovanja (RRS) - Preoblikovanje radia glede na arhitekturo za mobilne naprave (MD)
Področje uporabe tega dokumenta zajema opredelitev preoblikovanja radia glede na arhitekturo za mobilne naprave z možnostjo preoblikovanja. Delo bo temeljilo na sistemskih zahtevah iz dokumenta ETSI EN 302 969 [1] ter primerih uporabe iz dokumentov ETSI TR 103 062 [i.1] in ETSI TR 102 944 [i.2].
General Information
Standards Content (Sample)
Draft ETSI EN 303 095 V1.2.9 (2018-02)
EUROPEAN STANDARD
Reconfigurable Radio Systems (RRS);
Radio reconfiguration related architecture
for Mobile Devices (MD)
2 Draft ETSI EN 303 095 V1.2.9 (2018-02)
Reference
REN/RRS-0216
Keywords
architecture, mobile, 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 only prevailing document is the
print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat.
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 2018.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.
TM TM
3GPP and LTE are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M logo is protected for the benefit of its Members. ®
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI
3 Draft ETSI EN 303 095 V1.2.9 (2018-02)
Contents
Intellectual Property Rights . 5
Foreword. 5
Modal verbs terminology . 5
1 Scope . 6
2 References . 6
2.1 Normative references . 6
2.2 Informative references . 6
3 Definitions, symbols and abbreviations . 7
3.1 Definitions . 7
3.2 Symbols . 9
3.3 Abbreviations . 9
4 Architectural Reference Model for Reconfigurable Mobile Devices . 10
4.1 Introduction. 10
4.2 Reconfigurable Mobile Devices - Architecture Components for Radio Reconfiguration . 11
4.2.1 High level description . 11
4.2.2 Communication Services Layer (CSL) . 12
4.2.3 Radio Control Framework (RCF). 13
4.2.4 Unified Radio Application (URA) . 13
4.2.5 Architectural Components System Requirements mapping . 13
4.3 Reconfigurable Mobile Devices - Architecture Reference Model for Multiradio Applications . 14
4.3.1 High level description . 14
4.3.2 Reference Model System Requirements mapping . 16
4.4 Reconfigurable Mobile Devices - Radio Computer . 16
4.4.1 High level description . 16
4.4.2 Radio Computer System Requirement Mapping . 18
4.5 Reconfigurable Mobile Devices - the Radio Virtual Machine . 19
4.5.1 Radio Virtual Machine basic principles . 19
4.5.2 RVM System Requirement Mapping . 20
4.6 Reconfigurable Mobile Devices - Unified Radio Applications . 20
4.6.1 Introduction . 20
4.6.2 Distribution and Installation of RAP . 20
4.6.3 Operational Structure of URA . 26
4.6.4 URA System Requirement Mapping . 29
4.7 Security architecture for reconfigurable mobile devices. 30
4.7.1 Description . 30
4.7.2 Security Components System Requirements mapping . 31
5 Reference Points . 32
5.1 Introduction. 32
5.2 Reference Points required for Installation/uninstallation and creating/deleting an instance of a URA . 33
5.3 Reference Points required for list checking of URA . 33
5.4 Reference Points required for activation/deactivation of URA. 34
5.5 Reference Points required for transferring context information . 34
5.6 Reference Points required for creating data flow and sending/receiving user data. 35
5.7 Reference Points required for radio environment measurements . 36
5.8 Reference Points required for reporting discovered peer equipment . 36
5.9 Reference Points required for flexible data flow . 37
5.10 Reference Points required for data flow control . 37
5.11 Reference Points required for synchronizing radio time . 38
5.12 Reference Points required for control of reconfigurable RF transceiver . 38
5.13 Reference points required for security functions . 39
6 Reconfigurable MD high level operating procedures . 41
6.1 Procedures for installation/uninstallation and creating/deleting instance of a URA . 41
6.2 Procedures for list checking of URA . 45
ETSI
4 Draft ETSI EN 303 095 V1.2.9 (2018-02)
6.3 Procedures for activation/deactivation of URA . 46
6.4 Procedures for transferring context information . 48
6.5 Procedure for creating data flow and sending/receiving user data . 49
6.6 Procedures for radio environment measurements . 54
6.7 Procedure for reporting discovered peer equipment . 55
6.8 Procedure for flexible data flow . 56
6.9 Procedure for data flow control . 57
6.10 Procedure for synchronizing radio time . 58
6.11 Procedure for control of reconfigurable RF transceiver. 60
6.12 Procedure for RE Configuration Policy endorsement, distribution, and validation . 68
6.13 Procedure for configuration enforcement . 70
6.14 Procedures for long-term management . 72
History . 78
ETSI
5 Draft ETSI EN 303 095 V1.2.9 (2018-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 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.
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
6 Draft ETSI EN 303 095 V1.2.9 (2018-02)
1 Scope
The scope of the present document is to define the radio reconfiguration related architecture for reconfigurable Mobile
Devices. The work will be based on the system requirements defined in ETSI EN 302 969 [1] and the Use Cases
defined in ETSI TR 103 062 [i.1] and ETSI TR 102 944 [i.2].
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 302 969 (V1.2.9): "Reconfigurable Radio Systems (RRS); Radio Reconfiguration related
Requirements for Mobile Devices".
2.2 Informative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are not necessary for the application of the present document but they assist the
user with regard to a particular subject area.
[i.1] ETSI TR 103 062: "Reconfigurable Radio Systems (RRS) Use Cases and Scenarios for Software
Defined Radio (SDR) Reference Architecture for Mobile Device".
[i.2] ETSI TR 102 944: "Reconfigurable Radio Systems (RRS); Use Cases for Baseband Interfaces for
Unified Radio Applications of Mobile Device".
[i.3] Recommendation ITU-T M.60: "Maintenance Terminology and Definitions".
[i.4] ETSI TS 103 436: "Reconfigurable Radio Systems (RRS); Security requirements for
reconfigurable radios".
[i.5] ETSI TR 103 087: "Reconfigurable Radio Systems (RRS); Security related use cases and threats in
Reconfigurable Radio Systems".
ETSI
7 Draft ETSI EN 303 095 V1.2.9 (2018-02)
3 Definitions, symbols and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply:
Application Processor (AP): part of mobile device hardware working under OS control and on which User
Applications, among others, are executed
Baseband Parameter Aggregation (BPA): unit collecting all the context information to be transferred to the monitor
NOTE: The BPA unit converts the context information into metric(s) such that a minimum bandwidth is
consumed during the procedure of transferring the context information to the monitor. Those metrics may
include Received Signal Strength Indication (RSSI) measurement, multi-RAT performance metrics, etc.
communication services layer: 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.
configcodes: result of compiling the source codes of a Radio Application (RA), which is either configuration codes of
Radio Virtual Machine (RVM) or executable codes for a particular target platform
NOTE: In the case when RA provider makes a high level code based on a target platform, a result of compiling
RA source codes is configcodes which is executable on the target platform. In the other case, when RA
provider makes a high level code without considering a target platform, a result of front-end compiling of
RA source codes is an Intermediate Representation (IR) which should be back-end compiled for operating
on a specific target platform.
data flow: logical channel between Flow Controller (FC) and a Unified Radio Applications (URA) created by FC to
send to or receive data elements (octets, packets or other granularity) from URA
environmental information: set of values that can affect the execution of RAs on a Radio Computer
NOTE: Environmental information consists of information related to the execution of RA(s), such as Buffer
Overflow, Resource Allocation, etc.
Functional Block (FB): function needed for real-time implementation of RA(s)
NOTE 1: A functional block includes not only the modem functions in Layer1 (L1), Layer2 (L2), and Layer 3 (L3)
but also all the control functions that should be processed in real-time for implementing given RA(s).
NOTE 2: Functional blocks are categorized into Standard Functional Blocks (SFBs) and User Defined Functional
Blocks (UDFBs). In more details:
1) SFB can be shared by many RAs. For example, Forward Error Correction (FEC), Fast Fourier
Transform (FFT)/Inverse Fast Fourier Transform (IFFT), (de)interleaver, Turbo coding, Viterbi
coding, Multiple Input Multiple Output (MIMO), Beamforming, etc. are the typical category of
standard functional block.
2) UDFB include those functional blocks that are dependent upon a specific RA. They are used to
support special function(s) required in a specific RA or to support a special algorithm used for
performance improvement. In addition, a user defined functional block can be used as a baseband
controller functional block which controls the functional blocks operating in baseband processor in
real-time and to control some context information processed in real-time.
NOTE 3: Each functional block has its unique name, Input, Output, and properties.
peer equipment: any communication counterpart of a reconfigurable radio equipment
NOTE: The peer equipment can be reached by establishing a (logical) communications link (i.e. an association)
between the reconfigurable radio equipment and peer equipment. Examples of peer equipment include
Wide Local Area Network (WLAN) access points, Internet Protocol (IP) access nodes, etc.
ETSI
8 Draft ETSI EN 303 095 V1.2.9 (2018-02)
Radio Application (RA): software which enforces the generation of the transmit RF signals or the decoding of the
receive RF signals
NOTE 1: The software is executed on a particular radio platform or an RVM as part of the radio platform.
NOTE 2: RAs might have different forms of representation. They are represented as:
Source codes including Radio Library calls of Radio Library native implementation and Radio
HAL calls.
IRs including Radio Library calls of Radio Library native implementation and radio HAL calls.
Executable codes for a particular radio platform.
radio computer: part of mobile device hardware working under ROS control and on which RAs are executed
NOTE: A Radio Computer typically include programmable processors, hardware accelerators, peripherals, 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) and Multiradio Controller (MRC). The Resource Manager (RM) is
typically part of OS.
Radio Controller (RC): functional component of RA for transferring context information from corresponding RAs to
monitor
NOTE: An RC, which may operate in an application processor in non real-time, accesses RAs which operates in
Radio Computer in real time. The monitor, to which the context information is transferred using RC,
provides context information to Adminstrator and/or Mobility Policy Manager (MPM) for application(s)
to be performed using the context information, for example, terminal-centric configuration.
Radio Frequency Transceiver (RF Transceiver): part of radio Platform converting, for transmission, baseband
signals into radio signals, and, for reception, radio signals into baseband signals
Radio Library (RL): library of SFB that is provided by a platform vendor in a form of platform-specific executable
code
NOTE 1: SFBs implement reference codes of functions which are typical for radio signal processing. They are not
atomic and their source codes are typed and visible for RA developers.
NOTE 2: An SFB is implemented through a Radio Hardware Abstraction Layer (HAL) when the SFB is
implemented on hardware accelerators. Radio HAL is part of ROS.
Radio Operating System (ROS): any appropriate OS empowered by RCF
NOTE: ROS provides RCF capabilities as well as traditional management capabilities related to management of
RP such as resource management, file system support, unified access to hardware resources, etc.
radio platform: part of mobile device 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.
ETSI
9 Draft ETSI EN 303 095 V1.2.9 (2018-02)
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.
reference point: conceptual point at the conjunction of two non-overlapping functions that can be used to identify the
type of information passing between these functions
NOTE: This definition is introduced by Recommendation ITU-T M.60 [i.3].
shadow radio platform: platform where configcodes can be directly executed when it corresponds to the target radio
platform or, when it corresponds to an RVM, compiled and executed
NOTE: If the Shadow radio platform is equivalent to the target radio platform, then a front-end compiler will
generate the executable code for the target radio platform and configcodes are equivalent to the
executable code for that radio platform.
3.2 Symbols
For the purposes of the present document, the following symbols apply:
M Number of SFBs implemented on Radio computer
M Number of SFBs implemented on hardware accelerators
3.3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
AOT Ahead-Of-Time
AP Application Processor
ASF Administrator Security Function
ASIC Applications-Specific Integrated Circuit
BE Back End
BPA Baseband Parameter Aggregation
CM Configuration Manager
CSL Communication Services Layer
FC Flow Controller
FEC Forward Error Correction
FFT Fast Fourier Transform
FM File Manager
FPGA Field Programmable Gate Array
GGSN Gateway GPRS Support Node
GPRS General Packet Radio Service
GPS Global Positioning System
HAL Hardware Abstraction Layer
HW HardWare
ID Identification
IFFT Inverse Fast Fourier Transform
IP Internet Protocol
IR Intermediate Representation
JIT Just-In-Time
KMS Key Management System
MAC Medium Access Control
MD Mobile Device
MDRC Mobile Device Reconfiguration Class
MIMO Multi-Input-Multi-Output
MPM Mobility Policy Manager
MRC MultiRadio Controller
MURI MUltiRadio Interface
ETSI
10 Draft ETSI EN 303 095 V1.2.9 (2018-02)
OEM Original Equipment Manufacturer
OS Operating System
RA Radio Application
RAP Radio Application Package
RAT Radio Access Technology
RC Radio Controller
RCF Radio Control Framework
RCM Radio Connection Manager
RF Radio Frequency
RL Radio Library
RM Resource Manager
ROS Radio Operating System
RPI Radio Programming Interface
RRFI Reconfigurable Radio Frequency Interface
RRS Reconfigurable Radio Systems
RRS-CA Reconfigurable Radio Systems Configuration Authority
RRS-CM RRS Configuration Manager
RRS-CP RRS Configuration Provider
RVM Radio Virtual Machine
SDR Software Defined Radio
SFB Standard Functional Block
SW SoftWare
TAD Transfer of Authority Document
TX/RX Transmission/Reception
UDFB User Defined Functional Block
URA Unified Radio Applications
URAI Unified Radio Applications Interface
WLAN Wireless Local Area Network
4 Architectural Reference Model for Reconfigurable
Mobile Devices
4.1 Introduction
The present document describes those elements of a mobile device which are related to the software radio
reconfiguration only. For this reason,the usage of the term "architecture" is limited to those elements and not to the
overall HW/SW architecture of a mobile device which is out of the scope of the present document.
The present document is organized as follows:
Clause 4.2 describes the reconfigurable mobile device architecture in term of its components and entities.
Clause 4.3 describes the architecture reference model for multiradio applications.
Clause 4.4 describes the "Radio Computer".
Clause 4.5 describes the Radio Virtual Machine as part of the architecture.
Clause 4.6 describes the Unified Radio Application.
Clause 4.7 describes the security architecture for reconfigurable mobile devices.
Clause 5 describes the (logical) interfaces between the identified components/entities.
Clause 6 lists the operating procedures of a reconfigurable mobile devices.
Clause 4 includes a list of tables mapping the system requirements as defined in ETSI EN 302 969 [1] to the different
entities/components/units which have been identified. In general, according to the MDRC [1] the reconfigurable mobile
device belongs to, all the related mandatory functional requirements described in ETSI EN 302 969 [1] shall be
implemented.
ETSI
11 Draft ETSI EN 303 095 V1.2.9 (2018-02)
4.2 Reconfigurable Mobile Devices - Architecture Components
for Radio Reconfiguration
4.2.1 High level description
Figure 4.1 shows the reconfigurable mobile device architectural components related to the radio reconfiguration as well
as the related entities. As shown in the figure, the following components can be identified:
Communication Services Layer (CSL):
- 4 logical entities: Administration, Mobility Policy Manager, Networking Stack and Monitor.
Radio Control Framework (RCF):
- 5 logical entities: Configuration Manager, Radio Connection Manager, Multi-Radio Controller, Resource
Manager and Flow Controller.
Unified Radio Applications (URA).
Radio Platform (consisting of RF Transceiver, Baseband, etc.).
These 4 components consist of Software (CSL, RCF) and/or Hardware (radio platform) entities and they shall be
interconnected through well defined interfaces as follows:
Multiradio Interface (MURI) between CSL and RCF.
Unified Radio Application Interface (URAI) between RCF and URA.
Reconfigurable Radio Frequency Interface (RRFI) between URA and RF Transceiver.
The above mentioned interfaces are not covered by the present document.
Figure 4.1: Reconfigurable mobile device architecture components for radio reconfiguration
ETSI
12 Draft ETSI EN 303 095 V1.2.9 (2018-02)
For each component, the required entities depend on the MDRC [1]. A Reconfigurable Mobile Device shall support all
the components and their entities as required by the corresponding MDRC as shown in Table 4.1. In case that a
Reconfigurable Mobile Device supports multiple MDRCs, the concerned Reconfigurable Mobile Device shall support
all the components and entities related to the highest supported MDRC.
Table 4.1: Required Components of the Reconfigurable Mobile Device Architecture
in function of the Mobile Device Reconfiguration Class
Mobile Device
Reconfiguration Required CSL Entities Required RCF Entities Required Interfaces
Class
MDRC-0 None None None
MDRC-1 Administrator, Mobility Policy Configuration Manager, Radio MURI
Manager, Networking Stack, Connection Manager, Flow
Monitor Controller
MDRC-2, MDRC-5 Administrator, Mobility Policy Configuration Manager, Radio MURI, URAI, RRFI
Manager, Networking Stack, Connection Manager, Multi-
Monitor Radio Controller, Flow
Controller
MDRC-3, MDRC-6 Administrator, Mobility Policy Configuration Manager, Radio MURI, URAI, RRFI
Manager, Networking Stack, Connection Manager, Multi-
Monitor Radio Controller, Flow
Controller
MDRC-4, MDRC-7 Administrator, Mobility Policy Configuration Manager, Radio MURI, URAI, RRFI
Manager, Networking Stack, Connection Manager, Multi-
Monitor Radio Controller, Resource
Manager, Flow Controller
The following clauses describe in more details the identified components as well as the related logical entities.
4.2.2 Communication Services Layer (CSL)
The CSL is a layer related to communication services supporting both generic applications and specific applications
related to multiradio applications. CSL includes the following 4 entities:
Administrator entity
The Administrator entity shall include at least functions to request installation or uninstallation of URA, and
creating or deleting instances of URA. This typically includes the provision of information about the URA,
their status, etc. Furthermore, the Administrator includes two sub-entities: the Administrator Security Function
(ASF) and the RRS Configuration Manager (RRS-CM).
NOTE: In case that a snapshot function is required, the Administrator entity may store relevant RAPs, their
configuration parameters and information on the URA installation and execution history. When required,
the same steps can be executed by the Administrator entity to fall back to a previous snapshot.
Mobility Policy Manager (MPM) entity
The MPM shall include at least functions for monitoring of the radio environments and MD capabilities, to
request activation or deactivation of URA, and to provide information about the URA list. It shall also make
selection among different radio access technologies and discover peer communication equipment and
arrangement of associations.
Networking stack entity
The Networking stack entity shall include at least functions for sending and receiving of user data.
Monitor entity
The Monitor entity shall include at least functions to transfer information from URA to user or proper
destination entity in MD.
ETSI
13 Draft ETSI EN 303 095 V1.2.9 (2018-02)
4.2.3 Radio Control Framework (RCF)
The RCF provides a generic environment for the execution of URA, and a uniform way of accessing the functionality of
the Radio Computer and individual RAs. RCF provides services to CSL via the Multiradio Interface (MURI).
The RCF includes the following 5 entities for managing URA [i.2]:
Configuration Manager (CM) entity
The CM shall include at least functions for installing/uninstalling and creating/deleting instances of URA as
well as management of and access to the radio parameters of the URA.
Radio Connection Manager (RCM) entity
The RCM shall include at least functions for activating/deactivating URA according to user requests, and to
management of user data flows, which can also be switched from one RA to another.
Flow Controller (FC) entity
The FC shall include at least functions for sending and receiving of user data packets and controlling the flow
of signalling packets.
Multiradio Controller (MRC) entity
The MRC shall include at least functions to schedule the requests for radio resources issued by concurrently
executing URA, and to detect and manage the interoperability problems among the concurrently executed
URA.
Resource Manager (RM) entity
The RM shall include at least functions to manage the computational resources, to share them among
simultaneously active URA, and to guarantee their real-time execution.
4.2.4 Unified Radio Application (URA)
As described in clause 4.2.3, the RCF, which represents functionalities provided by the Radio Computer, requires all
RAs to be subject to a common reconfiguration, multiradio execution and resource sharing strategy framework
(depending on the concerned MDRC). Since all RAs exhibit a common behaviour from the reconfigurable MD
perspective, those RAs are called URAs. The services relate to activation and deactivation, peer equipment discovery
and maintenance of communication over user data flows are provided at Unified Radio Application Interface (URAI),
which is an interface between URA and RCF.
4.2.5 Architectural Components System Requirements mapping
The logical entities above described are mapped to the system requirements described in ETSI EN 302 969 [1] as shown
in Table 4.2.
ETSI
14 Draft ETSI EN 303 095 V1.2.9 (2018-02)
Table 4.2: Mapping of Architectural Components to the system requirements
described in ETSI EN 302 969 [1]
Entity/Component/Unit System Requirements [1] Comments
Administrator R-FUNC-MDR-01, The reconfigurable MD configuration is performed
R-FUNC-MDR-02, through downloading of the RAP into the
R-FUNC-SEC-01, reconfigurable MD and its installation. The
R-FUNC-SEC-02 requirements are described in clauses 6.4.1, 6.4.2,
and 6.6 of ETSI EN 302 969 [1]
Mobility Policy Manager R-FUNC-RAT–04, RAP into the reconfigurable MD and its installation.
R-FUNC-MDR-03 The requirements are described in clauses 6.1.4 and
6.4.3 of ETSI EN 302 969 [1]
Networking stack R-FUNC-RA-04, Management of data flows is required for basic
R-FUNC-RAT–05 TX/RX operation. The requirement is described in
Flow Control
clause 6.2.4 of ETSI EN 302 969 [1]
Monitor R-FUNC-RA-05 The RC in RA ensures the availability of context
information. The requirement is described in
clause 6.2.5 of ETSI EN 302 969 [1]
Configuration Manager R-FUNC-MDR-03 The radio configuration of a reconfigurable MD is
realized with the activation of URA. The requirement
Radio Connection Manager
is described in clause 6.4.3 of ETSI EN 302 969 [1]
Multiradio Controller R-FUNC-RAT–01, The proposed Mobile Device Architecture is suitable
R-FUNC-RAT–02, to support Multiple (parallel) connections to
R-FUNC-RAT–03, (heterogeneous) RATs. The requirements are
R-FUNC-RAT–05, described in clauses 6.1.1 and 6.1.2 of
R-FUNC-RAT–06 ETSI EN 302 969 [1]
Resource Manager R-FUNC-MDR-05 In case of dynamic resource sharing, the resource
allocation is performed in run time. The requirements
is described in clause 6.4.5 of ETSI EN 302 969 [1]
4.3 Reconfigurable Mobile Devices - Architecture Reference
Model for Multiradio Applications
4.3.1 High level description
Figure 4.2 exemplifies a Reconfigurable MD architecture reference model for multiradio applications. As shown in the
figure, the reconfigurable MD architecture shall include at least a Radio Computer. In the example of Figure 4.2, the
red-dotted part belongs to either Radio Computer or Application Processor depending on the specific implementation.
ETSI
15 Draft ETSI EN 303 095 V1.2.9 (2018-02)
User
Application
•••
Application
Driver OS
Processor
Vendor
MURI
specific
Communication
Services Layer
URAI
Radio Controller
•••
•••
Function Block
Unified Radio Applications
Radio
Radio
Radio Control Framework*
OS
*Radio Control Framework includes
Computer
Normative
following components:
as defined
• Configuration Manager (CM)
• Radio Connection Manager (RCM)
Radio Platform Driver in the
• Flow Controller (FC)
present
• Multiradio Controller (MRC)
Radio Platform • Resource Manager (RM) document
Programmable Dedicated
RF transceiver Antenna
Hardware Hardware
Radio Spectrum
Figure 4.2: Reconfigurable Mobile Device (MD) architecture Reference
Model for multiradio applications
In the example of Figure 4.2, the operation of Application Processor is performed by a given Operating System (OS),
which is preferably performed on non-real-time bases, whereas Radio Computer's operation is performed by another
OS, which should support real-time operations of URA. The OS of Radio Computer is referred to as Radio OS (ROS) in
the present document.
The AP includes the following components:
A Driver which has the purpose of activating the hardware devices (such as camera, speaker, etc.) on a given
MD.
A non-real time OS for execution of Administrator, MPM, Networking stack and Monitor which are part of
the CSL as above described. For multiradio applications the OS may include RCF (Application Processor
part).
The Radio Controller (RC) in Radio Application (RA) sending context information to the Monitor and
send/receive data to/from Networking stack.
The Radio Computer shall include the following components:
ROS is a real-time Operating System.
A radio platform driver which is a hardware driver for the ROS to interact with the radio platform hardware.
The 5 entities of the RCF, specified in clause 4.2.3, are classified into two groups. One group relates to real-
time execution and the other group to non-real-time execution as shown in Figure 4.2. Which entities of RCF
interface relate to real-time and non-real-time execution, can be determined by each vendor.
ETSI
RA.1
RA.2
App 1
RA.3
App 2
App 3
RA.N
App M
16 Draft ETSI EN 303 095 V1.2.9 (2018-02)
4.3.2 Reference Model System Requirements mapping
The architecture reference model above described is mapped to the system requirements described in ETSI
EN 302 969 [1] as shown in Table 4.3.
Table 4.3: Mapping of Reference Model to the system requirements described in ETSI EN 302 969 [1]
Entity/Component/Unit System Requirements [1] Comments
Application Processor R-FUNC-RA-05 The Radio Controller in RA ensures the availability of
(vendor specific) context information. The requirement is described in
clause 6.2.5 of ETSI EN 302 969 [1]
Radio Computer R-FUNC-MDR-09, ROS enables management of timing constraints and
R-FUNC-RA-06 provides interface between URA and radio platform.
The requirements are described in clauses 6.4.9 and
6.2.6 of ETSI EN 302 969 [1]
4.4 Reconfigurable Mobile Devices - Radio Computer
4.4.1 High level description
The System Architecture for a Radio Computer is illustrated in Figure 4.3 and Figure 4.4. Some of the entities included
in the figures below may be located externally (in the "Cloud") in order to off-load processing from the concerned
Mobile Devices. As example, the Back End compiler in Figure 4.3 is moved into the "Cloud" as illustrated in
Figure 4.4.
Radio Apps
Source code
Multi Radio Interface (MURI)
Radio Control Framework
Radio
Unified Radio
Storage
Front-end
Radio Library Application
normative description
Compiler Radio Apps Interface (URAI)
configcode
Shadow
configcode
RVM Radio Library
BE
Radio Platform
implementation native implementation Compiler
Radio OS
Radio Programming Interface
HW Radio Platform
RF part
Radio Apps
package
Radio Computer
upload
Radio Apps
Store
Figure 4.3: System architecture for Radio Computer where Radio Library and Back End (BE)
compiler are included within the Radio Computer
ETSI
17 Draft ETSI EN 303 095 V1.2.9 (2018-02)
Vendor’s Radio Reconfiguration Service
Radio Apps
Source code
BE
Radio Library
native
Compiler
implementation
Multi Radio Interface (MURI)
Front-end
request
Unified Radio
Compiler Application
Radio
Interface (URAI)
Storage
download
RVM
implementation
Shadow
Radio Apps
configcode
Radio Platform
exe code
Radio Library
native
implementation
Radio OS
request
Radio Programming Interface
download
HW Radio Platform
Radio Apps
RF part
package
Radio Computer
upload
Radio Apps
Store
Figure 4.4: System architecture for Radio Computer where Radio Library and BE compiler
are provided at a cloud outside the Radio Computer
Certification is required for Configcodes.
The Radio Computer shall provide communication capabilities for reconfigurable MDs and shall consist of:
ROS including RCF.
URA configuration codes (configcodes), which are:
- Executable codes for MDRC-2. MDRC-3 and MDRC-4.
- Source codes or IR for MDRC-5, MDRC-6 and MDRC-7.
Radio Virtual Machine (RVM) for MDRC-5, MDRC-6 and MDRC-7.
Radio Library Native Implementation for MDRC-5, MDRC-6 and MDRC-7 when URA configcodes is
compiled within MD, or when URA configcodes is compiled in a cloud with dynamic linking.
Radio platform.
URA Configcodes shall be executable codes for MDRC-2, MDRC-3 and MDRC-4, or shall be interpreted by the RVM
for MDRC-5, MDRC-6 and MDRC-7.
For MDRC-2, MDRC-3 and MDRC-4, a front-end compiler shall generate the executable code for the target platform
and configcodes are equivalent to the executable code for that target platform. Hence, Radio Library native
implementation and Back-end Compiler shown with the dotted line in Figure 4.3 is not required in the Radio Computer.
ETSI
18 Draft ETSI EN 303 095 V1.2.9 (2018-02)
The RVM (see also clause 4.4) is an Abstract Machine which is capable of executi
...
EUROPEAN STANDARD
Reconfigurable Radio Systems (RRS);
Radio reconfiguration related architecture
for Mobile Devices (MD)
2 ETSI EN 303 095 V1.3.1 (2018-05)
Reference
REN/RRS-0216
Keywords
architecture, mobile, 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 only prevailing document is the
print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat.
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 2018.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.
TM TM
3GPP and LTE are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M logo is protected for the benefit of its Members. ®
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI
3 ETSI EN 303 095 V1.3.1 (2018-05)
Contents
Intellectual Property Rights . 5
Foreword . 5
Modal verbs terminology . 5
1 Scope . 6
2 References . 6
2.1 Normative references . 6
2.2 Informative references . 6
3 Definitions, symbols and abbreviations . 7
3.1 Definitions . 7
3.2 Symbols . 9
3.3 Abbreviations . 9
4 Architectural Reference Model for Reconfigurable Mobile Devices . 10
4.1 Introduction . 10
4.2 Reconfigurable Mobile Devices - Architecture Components for Radio Reconfiguration . 11
4.2.1 High level description . 11
4.2.2 Communication Services Layer (CSL) . 12
4.2.3 Radio Control Framework (RCF) . 13
4.2.4 Unified Radio Application (URA) . 13
4.2.5 Architectural Components System Requirements mapping . 13
4.3 Reconfigurable Mobile Devices - Architecture Reference Model for Multiradio Applications . 14
4.3.1 High level description . 14
4.3.2 Reference Model System Requirements mapping . 16
4.4 Reconfigurable Mobile Devices - Radio Computer . 16
4.4.1 High level description . 16
4.4.2 Radio Computer System Requirement Mapping . 18
4.5 Reconfigurable Mobile Devices - the Radio Virtual Machine . 19
4.5.1 Radio Virtual Machine basic principles . 19
4.5.2 RVM System Requirement Mapping . 20
4.6 Reconfigurable Mobile Devices - Unified Radio Applications . 20
4.6.1 Introduction. 20
4.6.2 Distribution and Installation of RAP . 20
4.6.3 Operational Structure of URA . 26
4.6.4 URA System Requirement Mapping . 29
4.7 Security architecture for reconfigurable mobile devices . 30
4.7.1 Description . 30
4.7.2 Security Components System Requirements mapping . 31
5 Reference Points . 32
5.1 Introduction . 32
5.2 Reference Points required for Installation/uninstallation and creating/deleting an instance of a URA . 33
5.3 Reference Points required for list checking of URA . 33
5.4 Reference Points required for activation/deactivation of URA . 34
5.5 Reference Points required for transferring context information . 34
5.6 Reference Points required for creating data flow and sending/receiving user data . 35
5.7 Reference Points required for radio environment measurements . 36
5.8 Reference Points required for reporting discovered peer equipment . 36
5.9 Reference Points required for flexible data flow . 37
5.10 Reference Points required for data flow control . 37
5.11 Reference Points required for synchronizing radio time . 38
5.12 Reference Points required for control of reconfigurable RF transceiver . 38
5.13 Reference points required for security functions . 39
6 Reconfigurable MD high level operating procedures . 41
6.1 Procedures for installation/uninstallation and creating/deleting instance of a URA . 41
6.2 Procedures for list checking of URA . 45
ETSI
4 ETSI EN 303 095 V1.3.1 (2018-05)
6.3 Procedures for activation/deactivation of URA . 46
6.4 Procedures for transferring context information . 48
6.5 Procedure for creating data flow and sending/receiving user data . 49
6.6 Procedures for radio environment measurements . 54
6.7 Procedure for reporting discovered peer equipment . 55
6.8 Procedure for flexible data flow . 56
6.9 Procedure for data flow control . 57
6.10 Procedure for synchronizing radio time . 58
6.11 Procedure for control of reconfigurable RF transceiver . 60
6.12 Procedure for RE Configuration Policy endorsement, distribution, and validation . 68
6.13 Procedure for configuration enforcement . 70
6.14 Procedures for long-term management . 72
History . 78
ETSI
5 ETSI EN 303 095 V1.3.1 (2018-05)
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).
National transposition dates
Date of adoption of this EN: 17 May 2018
Date of latest announcement of this EN (doa): 31 August 2018
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 28 February 2019
Date of withdrawal of any conflicting National Standard (dow): 28 February 2019
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI
6 ETSI EN 303 095 V1.3.1 (2018-05)
1 Scope
The scope of the present document is to define the radio reconfiguration related architecture for reconfigurable Mobile
Devices. The work will be based on the system requirements defined in ETSI EN 302 969 [1] and the Use Cases
defined in ETSI TR 103 062 [i.1] and ETSI TR 102 944 [i.2].
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 302 969 (V1.3.1): "Reconfigurable Radio Systems (RRS); Radio Reconfiguration related
requirements for Mobile Devices".
2.2 Informative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are not necessary for the application of the present document but they assist the
user with regard to a particular subject area.
[i.1] ETSI TR 103 062: "Reconfigurable Radio Systems (RRS) Use Cases and Scenarios for Software
Defined Radio (SDR) Reference Architecture for Mobile Device".
[i.2] ETSI TR 102 944: "Reconfigurable Radio Systems (RRS); Use Cases for Baseband Interfaces for
Unified Radio Applications of Mobile Device".
[i.3] Recommendation ITU-T M.60: "Maintenance Terminology and Definitions".
[i.4] ETSI TS 103 436: "Reconfigurable Radio Systems (RRS); Security requirements for
reconfigurable radios".
[i.5] ETSI TR 103 087: "Reconfigurable Radio Systems (RRS); Security related use cases and threats in
Reconfigurable Radio Systems".
ETSI
7 ETSI EN 303 095 V1.3.1 (2018-05)
3 Definitions, symbols and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply:
Application Processor (AP): part of mobile device hardware working under OS control and on which User
Applications, among others, are executed
Baseband Parameter Aggregation (BPA): unit collecting all the context information to be transferred to the monitor
NOTE: The BPA unit converts the context information into metric(s) such that a minimum bandwidth is
consumed during the procedure of transferring the context information to the monitor. Those metrics may
include Received Signal Strength Indication (RSSI) measurement, multi-RAT performance metrics, etc.
communication services layer: 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.
configcodes: result of compiling the source codes of a Radio Application (RA), which is either configuration codes of
Radio Virtual Machine (RVM) or executable codes for a particular target platform
NOTE: In the case when RA provider makes a high level code based on a target platform, a result of compiling
RA source codes is configcodes which is executable on the target platform. In the other case, when RA
provider makes a high level code without considering a target platform, a result of front-end compiling of
RA source codes is an Intermediate Representation (IR) which should be back-end compiled for operating
on a specific target platform.
data flow: logical channel between Flow Controller (FC) and a Unified Radio Applications (URA) created by FC to
send to or receive data elements (octets, packets or other granularity) from URA
environmental information: set of values that can affect the execution of RAs on a Radio Computer
NOTE: Environmental information consists of information related to the execution of RA(s), such as Buffer
Overflow, Resource Allocation, etc.
Functional Block (FB): function needed for real-time implementation of RA(s)
NOTE 1: A functional block includes not only the modem functions in Layer1 (L1), Layer2 (L2), and Layer 3 (L3)
but also all the control functions that should be processed in real-time for implementing given RA(s).
NOTE 2: Functional blocks are categorized into Standard Functional Blocks (SFBs) and User Defined Functional
Blocks (UDFBs). In more details:
1) SFB can be shared by many RAs. For example, Forward Error Correction (FEC), Fast Fourier
Transform (FFT)/Inverse Fast Fourier Transform (IFFT), (de)interleaver, Turbo coding, Viterbi
coding, Multiple Input Multiple Output (MIMO), Beamforming, etc. are the typical category of
standard functional block.
2) UDFB include those functional blocks that are dependent upon a specific RA. They are used to
support special function(s) required in a specific RA or to support a special algorithm used for
performance improvement. In addition, a user defined functional block can be used as a baseband
controller functional block which controls the functional blocks operating in baseband processor in
real-time and to control some context information processed in real-time.
NOTE 3: Each functional block has its unique name, Input, Output, and properties.
peer equipment: any communication counterpart of a reconfigurable radio equipment
NOTE: The peer equipment can be reached by establishing a (logical) communications link (i.e. an association)
between the reconfigurable radio equipment and peer equipment. Examples of peer equipment include
Wide Local Area Network (WLAN) access points, Internet Protocol (IP) access nodes, etc.
ETSI
8 ETSI EN 303 095 V1.3.1 (2018-05)
Radio Application (RA): software which enforces the generation of the transmit RF signals or the decoding of the
receive RF signals
NOTE 1: The software is executed on a particular radio platform or an RVM as part of the radio platform.
NOTE 2: RAs might have different forms of representation. They are represented as:
Source codes including Radio Library calls of Radio Library native implementation and Radio
HAL calls.
IRs including Radio Library calls of Radio Library native implementation and radio HAL calls.
Executable codes for a particular radio platform.
radio computer: part of mobile device hardware working under ROS control and on which RAs are executed
NOTE: A Radio Computer typically include programmable processors, hardware accelerators, peripherals, 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) and Multiradio Controller (MRC). The Resource Manager (RM) is
typically part of OS.
Radio Controller (RC): functional component of RA for transferring context information from corresponding RAs to
monitor
NOTE: An RC, which may operate in an application processor in non real-time, accesses RAs which operates in
Radio Computer in real time. The monitor, to which the context information is transferred using RC,
provides context information to Adminstrator and/or Mobility Policy Manager (MPM) for application(s)
to be performed using the context information, for example, terminal-centric configuration.
Radio Frequency Transceiver (RF Transceiver): part of radio Platform converting, for transmission, baseband
signals into radio signals, and, for reception, radio signals into baseband signals
Radio Library (RL): library of SFB that is provided by a platform vendor in a form of platform-specific executable
code
NOTE 1: SFBs implement reference codes of functions which are typical for radio signal processing. They are not
atomic and their source codes are typed and visible for RA developers.
NOTE 2: An SFB is implemented through a Radio Hardware Abstraction Layer (HAL) when the SFB is
implemented on hardware accelerators. Radio HAL is part of ROS.
Radio Operating System (ROS): any appropriate OS empowered by RCF
NOTE: ROS provides RCF capabilities as well as traditional management capabilities related to management of
RP such as resource management, file system support, unified access to hardware resources, etc.
radio platform: part of mobile device 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.
ETSI
9 ETSI EN 303 095 V1.3.1 (2018-05)
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.
reference point: conceptual point at the conjunction of two non-overlapping functions that can be used to identify the
type of information passing between these functions
NOTE: This definition is introduced by Recommendation ITU-T M.60 [i.3].
shadow radio platform: platform where configcodes can be directly executed when it corresponds to the target radio
platform or, when it corresponds to an RVM, compiled and executed
NOTE: If the Shadow radio platform is equivalent to the target radio platform, then a front-end compiler will
generate the executable code for the target radio platform and configcodes are equivalent to the
executable code for that radio platform.
3.2 Symbols
For the purposes of the present document, the following symbols apply:
M Number of SFBs implemented on Radio computer
M Number of SFBs implemented on hardware accelerators
3.3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
AOT Ahead-Of-Time
AP Application Processor
ASF Administrator Security Function
ASIC Applications-Specific Integrated Circuit
BE Back End
BPA Baseband Parameter Aggregation
CM Configuration Manager
CSL Communication Services Layer
FC Flow Controller
FEC Forward Error Correction
FFT Fast Fourier Transform
FM File Manager
FPGA Field Programmable Gate Array
GGSN Gateway GPRS Support Node
GPRS General Packet Radio Service
GPS Global Positioning System
HAL Hardware Abstraction Layer
HW HardWare
ID Identification
IFFT Inverse Fast Fourier Transform
IP Internet Protocol
IR Intermediate Representation
JIT Just-In-Time
KMS Key Management System
MAC Medium Access Control
MD Mobile Device
MDRC Mobile Device Reconfiguration Class
MIMO Multi-Input-Multi-Output
MPM Mobility Policy Manager
MRC MultiRadio Controller
MURI MUltiRadio Interface
ETSI
10 ETSI EN 303 095 V1.3.1 (2018-05)
OEM Original Equipment Manufacturer
OS Operating System
RA Radio Application
RAP Radio Application Package
RAT Radio Access Technology
RC Radio Controller
RCF Radio Control Framework
RCM Radio Connection Manager
RF Radio Frequency
RL Radio Library
RM Resource Manager
ROS Radio Operating System
RPI Radio Programming Interface
RRFI Reconfigurable Radio Frequency Interface
RRS Reconfigurable Radio Systems
RRS-CA Reconfigurable Radio Systems Configuration Authority
RRS-CM RRS Configuration Manager
RRS-CP RRS Configuration Provider
RVM Radio Virtual Machine
SDR Software Defined Radio
SFB Standard Functional Block
SW SoftWare
TAD Transfer of Authority Document
TX/RX Transmission/Reception
UDFB User Defined Functional Block
URA Unified Radio Applications
URAI Unified Radio Applications Interface
WLAN Wireless Local Area Network
4 Architectural Reference Model for Reconfigurable
Mobile Devices
4.1 Introduction
The present document describes those elements of a mobile device which are related to the software radio
reconfiguration only. For this reason,the usage of the term "architecture" is limited to those elements and not to the
overall HW/SW architecture of a mobile device which is out of the scope of the present document.
The present document is organized as follows:
Clause 4.2 describes the reconfigurable mobile device architecture in term of its components and entities.
Clause 4.3 describes the architecture reference model for multiradio applications.
Clause 4.4 describes the "Radio Computer".
Clause 4.5 describes the Radio Virtual Machine as part of the architecture.
Clause 4.6 describes the Unified Radio Application.
Clause 4.7 describes the security architecture for reconfigurable mobile devices.
Clause 5 describes the (logical) interfaces between the identified components/entities.
Clause 6 lists the operating procedures of a reconfigurable mobile devices.
Clause 4 includes a list of tables mapping the system requirements as defined in ETSI EN 302 969 [1] to the different
entities/components/units which have been identified. In general, according to the MDRC [1] the reconfigurable mobile
device belongs to, all the related mandatory functional requirements described in ETSI EN 302 969 [1] shall be
implemented.
ETSI
11 ETSI EN 303 095 V1.3.1 (2018-05)
4.2 Reconfigurable Mobile Devices - Architecture Components
for Radio Reconfiguration
4.2.1 High level description
Figure 4.1 shows the reconfigurable mobile device architectural components related to the radio reconfiguration as well
as the related entities. As shown in the figure, the following components can be identified:
• Communication Services Layer (CSL):
- 4 logical entities: Administration, Mobility Policy Manager, Networking Stack and Monitor.
• Radio Control Framework (RCF):
- 5 logical entities: Configuration Manager, Radio Connection Manager, Multi-Radio Controller, Resource
Manager and Flow Controller.
• Unified Radio Applications (URA).
• Radio Platform (consisting of RF Transceiver, Baseband, etc.).
These 4 components consist of Software (CSL, RCF) and/or Hardware (radio platform) entities and they shall be
interconnected through well defined interfaces as follows:
• Multiradio Interface (MURI) between CSL and RCF.
• Unified Radio Application Interface (URAI) between RCF and URA.
• Reconfigurable Radio Frequency Interface (RRFI) between URA and RF Transceiver.
The above mentioned interfaces are not covered by the present document.
Figure 4.1: Reconfigurable mobile device architecture components for radio reconfiguration
ETSI
12 ETSI EN 303 095 V1.3.1 (2018-05)
For each component, the required entities depend on the MDRC [1]. A Reconfigurable Mobile Device shall support all
the components and their entities as required by the corresponding MDRC as shown in Table 4.1. In case that a
Reconfigurable Mobile Device supports multiple MDRCs, the concerned Reconfigurable Mobile Device shall support
all the components and entities related to the highest supported MDRC.
Table 4.1: Required Components of the Reconfigurable Mobile Device Architecture
in function of the Mobile Device Reconfiguration Class
Mobile Device
Reconfiguration Required CSL Entities Required RCF Entities Required Interfaces
Class
MDRC-0 None None None
MDRC-1 Administrator, Mobility Policy Configuration Manager, Radio MURI
Manager, Networking Stack, Connection Manager, Flow
Monitor Controller
MDRC-2, MDRC-5 Administrator, Mobility Policy Configuration Manager, Radio MURI, URAI, RRFI
Manager, Networking Stack, Connection Manager, Multi-
Monitor Radio Controller, Flow
Controller
MDRC-3, MDRC-6 Administrator, Mobility Policy Configuration Manager, Radio MURI, URAI, RRFI
Manager, Networking Stack, Connection Manager, Multi-
Monitor Radio Controller, Flow
Controller
MDRC-4, MDRC-7 Administrator, Mobility Policy Configuration Manager, Radio MURI, URAI, RRFI
Manager, Networking Stack, Connection Manager, Multi-
Monitor Radio Controller, Resource
Manager, Flow Controller
The following clauses describe in more details the identified components as well as the related logical entities.
4.2.2 Communication Services Layer (CSL)
The CSL is a layer related to communication services supporting both generic applications and specific applications
related to multiradio applications. CSL includes the following 4 entities:
• Administrator entity
The Administrator entity shall include at least functions to request installation or uninstallation of URA, and
creating or deleting instances of URA. This typically includes the provision of information about the URA,
their status, etc. Furthermore, the Administrator includes two sub-entities: the Administrator Security Function
(ASF) and the RRS Configuration Manager (RRS-CM).
NOTE: In case that a snapshot function is required, the Administrator entity may store relevant RAPs, their
configuration parameters and information on the URA installation and execution history. When required,
the same steps can be executed by the Administrator entity to fall back to a previous snapshot.
• Mobility Policy Manager (MPM) entity
The MPM shall include at least functions for monitoring of the radio environments and MD capabilities, to
request activation or deactivation of URA, and to provide information about the URA list. It shall also make
selection among different radio access technologies and discover peer communication equipment and
arrangement of associations.
• Networking stack entity
The Networking stack entity shall include at least functions for sending and receiving of user data.
• Monitor entity
The Monitor entity shall include at least functions to transfer information from URA to user or proper
destination entity in MD.
ETSI
13 ETSI EN 303 095 V1.3.1 (2018-05)
4.2.3 Radio Control Framework (RCF)
The RCF provides a generic environment for the execution of URA, and a uniform way of accessing the functionality of
the Radio Computer and individual RAs. RCF provides services to CSL via the Multiradio Interface (MURI).
The RCF includes the following 5 entities for managing URA [i.2]:
• Configuration Manager (CM) entity
The CM shall include at least functions for installing/uninstalling and creating/deleting instances of URA as
well as management of and access to the radio parameters of the URA.
• Radio Connection Manager (RCM) entity
The RCM shall include at least functions for activating/deactivating URA according to user requests, and to
management of user data flows, which can also be switched from one RA to another.
• Flow Controller (FC) entity
The FC shall include at least functions for sending and receiving of user data packets and controlling the flow
of signalling packets.
• Multiradio Controller (MRC) entity
The MRC shall include at least functions to schedule the requests for radio resources issued by concurrently
executing URA, and to detect and manage the interoperability problems among the concurrently executed
URA.
• Resource Manager (RM) entity
The RM shall include at least functions to manage the computational resources, to share them among
simultaneously active URA, and to guarantee their real-time execution.
4.2.4 Unified Radio Application (URA)
As described in clause 4.2.3, the RCF, which represents functionalities provided by the Radio Computer, requires all
RAs to be subject to a common reconfiguration, multiradio execution and resource sharing strategy framework
(depending on the concerned MDRC). Since all RAs exhibit a common behaviour from the reconfigurable MD
perspective, those RAs are called URAs. The services relate to activation and deactivation, peer equipment discovery
and maintenance of communication over user data flows are provided at Unified Radio Application Interface (URAI),
which is an interface between URA and RCF.
4.2.5 Architectural Components System Requirements mapping
The logical entities above described are mapped to the system requirements described in ETSI EN 302 969 [1] as shown
in Table 4.2.
ETSI
14 ETSI EN 303 095 V1.3.1 (2018-05)
Table 4.2: Mapping of Architectural Components to the system requirements
described in ETSI EN 302 969 [1]
Entity/Component/Unit System Requirements [1] Comments
Administrator R-FUNC-MDR-01, The reconfigurable MD configuration is performed
R-FUNC-MDR-02, through downloading of the RAP into the
R-FUNC-SEC-01, reconfigurable MD and its installation. The
R-FUNC-SEC-02 requirements are described in clauses 6.4.1, 6.4.2,
and 6.6 of ETSI EN 302 969 [1]
Mobility Policy Manager R-FUNC-RAT–04, RAP into the reconfigurable MD and its installation.
R-FUNC-MDR-03 The requirements are described in clauses 6.1.4 and
6.4.3 of ETSI EN 302 969 [1]
Networking stack R-FUNC-RA-04, Management of data flows is required for basic
R-FUNC-RAT–05 TX/RX operation. The requirement is described in
Flow Control
clause 6.2.4 of ETSI EN 302 969 [1]
Monitor R-FUNC-RA-05 The RC in RA ensures the availability of context
information. The requirement is described in
clause 6.2.5 of ETSI EN 302 969 [1]
Configuration Manager R-FUNC-MDR-03 The radio configuration of a reconfigurable MD is
realized with the activation of URA. The requirement
Radio Connection Manager
is described in clause 6.4.3 of ETSI EN 302 969 [1]
Multiradio Controller R-FUNC-RAT–01, The proposed Mobile Device Architecture is suitable
R-FUNC-RAT–02, to support Multiple (parallel) connections to
R-FUNC-RAT–03, (heterogeneous) RATs. The requirements are
R-FUNC-RAT–05, described in clauses 6.1.1 and 6.1.2 of ETSI
R-FUNC-RAT–06 EN 302 969 [1]
Resource Manager R-FUNC-MDR-05 In case of dynamic resource sharing, the resource
allocation is performed in run time. The requirements
is described in clause 6.4.5 of ETSI EN 302 969 [1]
4.3 Reconfigurable Mobile Devices - Architecture Reference
Model for Multiradio Applications
4.3.1 High level description
Figure 4.2 exemplifies a Reconfigurable MD architecture reference model for multiradio applications. As shown in the
figure, the reconfigurable MD architecture shall include at least a Radio Computer. In the example of Figure 4.2, the
red-dotted part belongs to either Radio Computer or Application Processor depending on the specific implementation.
ETSI
15 ETSI EN 303 095 V1.3.1 (2018-05)
User
1 2 3
M
p p p
p Application
p p p
p
Application
A A A
A
Driver OS
Processor
Vendor
MURI
specific
Communication
Services Layer
URAI
Radio Controller
1 2 3
. . . N
.
A A A
A
R R R R
Function Block
Unified Radio Applications
Radio
Radio
Radio Control Framework*
OS
*Radio Control Framework includes
Computer
Normative
following components:
as defined
• Configuration Manager (CM)
Radio Platform Driver Radio Connection Manager (RCM) in the
Flow Controller (FC)
present
Multiradio Controller (MRC)
Radio Platform Resource Manager (RM)
document
Programmable Dedicated
RF transceiver Antenna
Hardware Hardware
Radio Spectrum
Figure 4.2: Reconfigurable Mobile Device (MD) architecture Reference
Model for multiradio applications
In the example of Figure 4.2, the operation of Application Processor is performed by a given Operating System (OS),
which is preferably performed on non-real-time bases, whereas Radio Computer's operation is performed by another
OS, which should support real-time operations of URA. The OS of Radio Computer is referred to as Radio OS (ROS) in
the present document.
The AP includes the following components:
• A Driver which has the purpose of activating the hardware devices (such as camera, speaker, etc.) on a given
MD.
• A non-real time OS for execution of Administrator, MPM, Networking stack and Monitor which are part of
the CSL as above described. For multiradio applications the OS may include RCF (Application Processor
part).
• The Radio Controller (RC) in Radio Application (RA) sending context information to the Monitor and
send/receive data to/from Networking stack.
The Radio Computer shall include the following components:
• ROS is a real-time Operating System.
• A radio platform driver which is a hardware driver for the ROS to interact with the radio platform hardware.
• The 5 entities of the RCF, specified in clause 4.2.3, are classified into two groups. One group relates to real-
time execution and the other group to non-real-time execution as shown in Figure 4.2. Which entities of RCF
interface relate to real-time and non-real-time execution, can be determined by each vendor.
ETSI
16 ETSI EN 303 095 V1.3.1 (2018-05)
4.3.2 Reference Model System Requirements mapping
The architecture reference model above described is mapped to the system requirements described in ETSI
EN 302 969 [1] as shown in Table 4.3.
Table 4.3: Mapping of Reference Model to the system requirements described in ETSI EN 302 969 [1]
Entity/Component/Unit System Requirements [1] Comments
Application Processor R-FUNC-RA-05 The Radio Controller in RA ensures the availability of
(vendor specific) context information. The requirement is described in
clause 6.2.5 of ETSI EN 302 969 [1]
Radio Computer R-FUNC-MDR-09, ROS enables management of timing constraints and
R-FUNC-RA-06 provides interface between URA and radio platform.
The requirements are described in clauses 6.4.9 and
6.2.6 of ETSI EN 302 969 [1]
4.4 Reconfigurable Mobile Devices - Radio Computer
4.4.1 High level description
The System Architecture for a Radio Computer is illustrated in Figure 4.3 and Figure 4.4. Some of the entities included
in the figures below may be located externally (in the "Cloud") in order to off-load processing from the concerned
Mobile Devices. As example, the Back End compiler in Figure 4.3 is moved into the "Cloud" as illustrated in
Figure 4.4.
Radio Apps
Source code
Multi Radio Interface (MURI)
Radio Control Framework
Radio
Unified Radio
Storage
Front-end
Radio Library Application
normative description Radio Apps Interface (URAI)
Compiler
configcode
Shadow
configcode 단추
RVM Radio Library BE
Radio Platform
im plem entat io n
native implementation Com pi le r
Radio OS
Radio Programming Interface
HW Radio Platform
RF part
Radio Apps
package
Radio Computer
upload
Radio Apps
Store
Figure 4.3: System architecture for Radio Computer where Radio Library and Back End (BE)
compiler are included within the Radio Computer
ETSI
17 ETSI EN 303 095 V1.3.1 (2018-05)
Vendor’s Radio Reconfiguration Service
Radio Apps
Source code
BE
Radio Library
native
Compiler
implementation
Multi Radio Interface (MURI)
Front-end
request
Unified Radio
Compiler Application
Radio
Interface (URAI)
Storage
download
RVM
implementation
Shadow
Radio Apps
configcode
단추
Radio Platform
exe code
Radio Library
native
implementation
Radio OS
request
Radio Programming Interface
download
HW Radio Platform
Radio Apps
RF part
package
Radio Computer
upload
Radio Apps
Store
Figure 4.4: System architecture for Radio Computer where Radio Library and BE compiler
are provided at a cloud outside the Radio Computer
Certification is required for Configcodes.
The Radio Computer shall provide communication capabilities for reconfigurable MDs and shall consist of:
• ROS including RCF.
• URA configuration codes (configcodes), which are:
- Executable codes for MDRC-2. MDRC-3 and MDRC-4.
- Source codes or IR for MDRC-5, MDRC-6 and MDRC-7.
• Radio Virtual Machine (RVM) for MDRC-5, MDRC-6 and MDRC-7.
• Radio Library Native Implementation for MDRC-5, MDRC-6 and MDRC-7 when URA configcodes is
compiled within MD, or when URA configcodes is compiled in a cloud with dynamic linking.
• Radio platform.
URA Configcodes shall be executable codes for MDRC-2, MDRC-3 and MDRC-4, or shall be interpreted by the RVM
for MDRC-5, MDRC-6 and MDRC-7.
For MDRC-2, MDRC-3 and MDRC-4, a front-end compiler shall generate the executable code for the target platform
and configcodes are equivalent to the executable code for that target platform. Hence, Radio Library native
implementation and Back-end Compiler shown with the dotted line in Figure 4.3 is not required in the Radio Computer.
ETSI
18 ETSI EN 303 095 V1.3.1 (2018-05)
The RVM (see also clause 4.4) is an Abstract Machine which is capable of executing configcodes and it is independent
of the hardware. The implementation of an RVM is target Radio Computer specific and it includes the Back-end
Compiler which mig
...
SLOVENSKI STANDARD
01-september-2018
Radijski sistemi z možnostjo preoblikovanja (RRS) - Preoblikovanje radia glede na
arhitekturo za mobilne naprave (MD)
Reconfigurable Radio Systems (RRS) - Radio reconfiguration related architecture for
Mobile Devices (MD)
Ta slovenski standard je istoveten z: ETSI EN 303 095 V1.3.1 (2018-05)
ICS:
33.060.01 Radijske komunikacije na Radiocommunications in
splošno general
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
EUROPEAN STANDARD
Reconfigurable Radio Systems (RRS);
Radio reconfiguration related architecture
for Mobile Devices (MD)
2 ETSI EN 303 095 V1.3.1 (2018-05)
Reference
REN/RRS-0216
Keywords
architecture, mobile, 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 only prevailing document is the
print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat.
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 2018.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.
TM TM
3GPP and LTE are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M logo is protected for the benefit of its Members. ®
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI
3 ETSI EN 303 095 V1.3.1 (2018-05)
Contents
Intellectual Property Rights . 5
Foreword . 5
Modal verbs terminology . 5
1 Scope . 6
2 References . 6
2.1 Normative references . 6
2.2 Informative references . 6
3 Definitions, symbols and abbreviations . 7
3.1 Definitions . 7
3.2 Symbols . 9
3.3 Abbreviations . 9
4 Architectural Reference Model for Reconfigurable Mobile Devices . 10
4.1 Introduction . 10
4.2 Reconfigurable Mobile Devices - Architecture Components for Radio Reconfiguration . 11
4.2.1 High level description . 11
4.2.2 Communication Services Layer (CSL) . 12
4.2.3 Radio Control Framework (RCF) . 13
4.2.4 Unified Radio Application (URA) . 13
4.2.5 Architectural Components System Requirements mapping . 13
4.3 Reconfigurable Mobile Devices - Architecture Reference Model for Multiradio Applications . 14
4.3.1 High level description . 14
4.3.2 Reference Model System Requirements mapping . 16
4.4 Reconfigurable Mobile Devices - Radio Computer . 16
4.4.1 High level description . 16
4.4.2 Radio Computer System Requirement Mapping . 18
4.5 Reconfigurable Mobile Devices - the Radio Virtual Machine . 19
4.5.1 Radio Virtual Machine basic principles . 19
4.5.2 RVM System Requirement Mapping . 20
4.6 Reconfigurable Mobile Devices - Unified Radio Applications . 20
4.6.1 Introduction. 20
4.6.2 Distribution and Installation of RAP . 20
4.6.3 Operational Structure of URA . 26
4.6.4 URA System Requirement Mapping . 29
4.7 Security architecture for reconfigurable mobile devices . 30
4.7.1 Description . 30
4.7.2 Security Components System Requirements mapping . 31
5 Reference Points . 32
5.1 Introduction . 32
5.2 Reference Points required for Installation/uninstallation and creating/deleting an instance of a URA . 33
5.3 Reference Points required for list checking of URA . 33
5.4 Reference Points required for activation/deactivation of URA . 34
5.5 Reference Points required for transferring context information . 34
5.6 Reference Points required for creating data flow and sending/receiving user data . 35
5.7 Reference Points required for radio environment measurements . 36
5.8 Reference Points required for reporting discovered peer equipment . 36
5.9 Reference Points required for flexible data flow . 37
5.10 Reference Points required for data flow control . 37
5.11 Reference Points required for synchronizing radio time . 38
5.12 Reference Points required for control of reconfigurable RF transceiver . 38
5.13 Reference points required for security functions . 39
6 Reconfigurable MD high level operating procedures . 41
6.1 Procedures for installation/uninstallation and creating/deleting instance of a URA . 41
6.2 Procedures for list checking of URA . 45
ETSI
4 ETSI EN 303 095 V1.3.1 (2018-05)
6.3 Procedures for activation/deactivation of URA . 46
6.4 Procedures for transferring context information . 48
6.5 Procedure for creating data flow and sending/receiving user data . 49
6.6 Procedures for radio environment measurements . 54
6.7 Procedure for reporting discovered peer equipment . 55
6.8 Procedure for flexible data flow . 56
6.9 Procedure for data flow control . 57
6.10 Procedure for synchronizing radio time . 58
6.11 Procedure for control of reconfigurable RF transceiver . 60
6.12 Procedure for RE Configuration Policy endorsement, distribution, and validation . 68
6.13 Procedure for configuration enforcement . 70
6.14 Procedures for long-term management . 72
History . 78
ETSI
5 ETSI EN 303 095 V1.3.1 (2018-05)
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).
National transposition dates
Date of adoption of this EN: 17 May 2018
Date of latest announcement of this EN (doa): 31 August 2018
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 28 February 2019
Date of withdrawal of any conflicting National Standard (dow): 28 February 2019
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI
6 ETSI EN 303 095 V1.3.1 (2018-05)
1 Scope
The scope of the present document is to define the radio reconfiguration related architecture for reconfigurable Mobile
Devices. The work will be based on the system requirements defined in ETSI EN 302 969 [1] and the Use Cases
defined in ETSI TR 103 062 [i.1] and ETSI TR 102 944 [i.2].
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 302 969 (V1.3.1): "Reconfigurable Radio Systems (RRS); Radio Reconfiguration related
requirements for Mobile Devices".
2.2 Informative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are not necessary for the application of the present document but they assist the
user with regard to a particular subject area.
[i.1] ETSI TR 103 062: "Reconfigurable Radio Systems (RRS) Use Cases and Scenarios for Software
Defined Radio (SDR) Reference Architecture for Mobile Device".
[i.2] ETSI TR 102 944: "Reconfigurable Radio Systems (RRS); Use Cases for Baseband Interfaces for
Unified Radio Applications of Mobile Device".
[i.3] Recommendation ITU-T M.60: "Maintenance Terminology and Definitions".
[i.4] ETSI TS 103 436: "Reconfigurable Radio Systems (RRS); Security requirements for
reconfigurable radios".
[i.5] ETSI TR 103 087: "Reconfigurable Radio Systems (RRS); Security related use cases and threats in
Reconfigurable Radio Systems".
ETSI
7 ETSI EN 303 095 V1.3.1 (2018-05)
3 Definitions, symbols and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply:
Application Processor (AP): part of mobile device hardware working under OS control and on which User
Applications, among others, are executed
Baseband Parameter Aggregation (BPA): unit collecting all the context information to be transferred to the monitor
NOTE: The BPA unit converts the context information into metric(s) such that a minimum bandwidth is
consumed during the procedure of transferring the context information to the monitor. Those metrics may
include Received Signal Strength Indication (RSSI) measurement, multi-RAT performance metrics, etc.
communication services layer: 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.
configcodes: result of compiling the source codes of a Radio Application (RA), which is either configuration codes of
Radio Virtual Machine (RVM) or executable codes for a particular target platform
NOTE: In the case when RA provider makes a high level code based on a target platform, a result of compiling
RA source codes is configcodes which is executable on the target platform. In the other case, when RA
provider makes a high level code without considering a target platform, a result of front-end compiling of
RA source codes is an Intermediate Representation (IR) which should be back-end compiled for operating
on a specific target platform.
data flow: logical channel between Flow Controller (FC) and a Unified Radio Applications (URA) created by FC to
send to or receive data elements (octets, packets or other granularity) from URA
environmental information: set of values that can affect the execution of RAs on a Radio Computer
NOTE: Environmental information consists of information related to the execution of RA(s), such as Buffer
Overflow, Resource Allocation, etc.
Functional Block (FB): function needed for real-time implementation of RA(s)
NOTE 1: A functional block includes not only the modem functions in Layer1 (L1), Layer2 (L2), and Layer 3 (L3)
but also all the control functions that should be processed in real-time for implementing given RA(s).
NOTE 2: Functional blocks are categorized into Standard Functional Blocks (SFBs) and User Defined Functional
Blocks (UDFBs). In more details:
1) SFB can be shared by many RAs. For example, Forward Error Correction (FEC), Fast Fourier
Transform (FFT)/Inverse Fast Fourier Transform (IFFT), (de)interleaver, Turbo coding, Viterbi
coding, Multiple Input Multiple Output (MIMO), Beamforming, etc. are the typical category of
standard functional block.
2) UDFB include those functional blocks that are dependent upon a specific RA. They are used to
support special function(s) required in a specific RA or to support a special algorithm used for
performance improvement. In addition, a user defined functional block can be used as a baseband
controller functional block which controls the functional blocks operating in baseband processor in
real-time and to control some context information processed in real-time.
NOTE 3: Each functional block has its unique name, Input, Output, and properties.
peer equipment: any communication counterpart of a reconfigurable radio equipment
NOTE: The peer equipment can be reached by establishing a (logical) communications link (i.e. an association)
between the reconfigurable radio equipment and peer equipment. Examples of peer equipment include
Wide Local Area Network (WLAN) access points, Internet Protocol (IP) access nodes, etc.
ETSI
8 ETSI EN 303 095 V1.3.1 (2018-05)
Radio Application (RA): software which enforces the generation of the transmit RF signals or the decoding of the
receive RF signals
NOTE 1: The software is executed on a particular radio platform or an RVM as part of the radio platform.
NOTE 2: RAs might have different forms of representation. They are represented as:
Source codes including Radio Library calls of Radio Library native implementation and Radio
HAL calls.
IRs including Radio Library calls of Radio Library native implementation and radio HAL calls.
Executable codes for a particular radio platform.
radio computer: part of mobile device hardware working under ROS control and on which RAs are executed
NOTE: A Radio Computer typically include programmable processors, hardware accelerators, peripherals, 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) and Multiradio Controller (MRC). The Resource Manager (RM) is
typically part of OS.
Radio Controller (RC): functional component of RA for transferring context information from corresponding RAs to
monitor
NOTE: An RC, which may operate in an application processor in non real-time, accesses RAs which operates in
Radio Computer in real time. The monitor, to which the context information is transferred using RC,
provides context information to Adminstrator and/or Mobility Policy Manager (MPM) for application(s)
to be performed using the context information, for example, terminal-centric configuration.
Radio Frequency Transceiver (RF Transceiver): part of radio Platform converting, for transmission, baseband
signals into radio signals, and, for reception, radio signals into baseband signals
Radio Library (RL): library of SFB that is provided by a platform vendor in a form of platform-specific executable
code
NOTE 1: SFBs implement reference codes of functions which are typical for radio signal processing. They are not
atomic and their source codes are typed and visible for RA developers.
NOTE 2: An SFB is implemented through a Radio Hardware Abstraction Layer (HAL) when the SFB is
implemented on hardware accelerators. Radio HAL is part of ROS.
Radio Operating System (ROS): any appropriate OS empowered by RCF
NOTE: ROS provides RCF capabilities as well as traditional management capabilities related to management of
RP such as resource management, file system support, unified access to hardware resources, etc.
radio platform: part of mobile device 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.
ETSI
9 ETSI EN 303 095 V1.3.1 (2018-05)
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.
reference point: conceptual point at the conjunction of two non-overlapping functions that can be used to identify the
type of information passing between these functions
NOTE: This definition is introduced by Recommendation ITU-T M.60 [i.3].
shadow radio platform: platform where configcodes can be directly executed when it corresponds to the target radio
platform or, when it corresponds to an RVM, compiled and executed
NOTE: If the Shadow radio platform is equivalent to the target radio platform, then a front-end compiler will
generate the executable code for the target radio platform and configcodes are equivalent to the
executable code for that radio platform.
3.2 Symbols
For the purposes of the present document, the following symbols apply:
M Number of SFBs implemented on Radio computer
M Number of SFBs implemented on hardware accelerators
3.3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
AOT Ahead-Of-Time
AP Application Processor
ASF Administrator Security Function
ASIC Applications-Specific Integrated Circuit
BE Back End
BPA Baseband Parameter Aggregation
CM Configuration Manager
CSL Communication Services Layer
FC Flow Controller
FEC Forward Error Correction
FFT Fast Fourier Transform
FM File Manager
FPGA Field Programmable Gate Array
GGSN Gateway GPRS Support Node
GPRS General Packet Radio Service
GPS Global Positioning System
HAL Hardware Abstraction Layer
HW HardWare
ID Identification
IFFT Inverse Fast Fourier Transform
IP Internet Protocol
IR Intermediate Representation
JIT Just-In-Time
KMS Key Management System
MAC Medium Access Control
MD Mobile Device
MDRC Mobile Device Reconfiguration Class
MIMO Multi-Input-Multi-Output
MPM Mobility Policy Manager
MRC MultiRadio Controller
MURI MUltiRadio Interface
ETSI
10 ETSI EN 303 095 V1.3.1 (2018-05)
OEM Original Equipment Manufacturer
OS Operating System
RA Radio Application
RAP Radio Application Package
RAT Radio Access Technology
RC Radio Controller
RCF Radio Control Framework
RCM Radio Connection Manager
RF Radio Frequency
RL Radio Library
RM Resource Manager
ROS Radio Operating System
RPI Radio Programming Interface
RRFI Reconfigurable Radio Frequency Interface
RRS Reconfigurable Radio Systems
RRS-CA Reconfigurable Radio Systems Configuration Authority
RRS-CM RRS Configuration Manager
RRS-CP RRS Configuration Provider
RVM Radio Virtual Machine
SDR Software Defined Radio
SFB Standard Functional Block
SW SoftWare
TAD Transfer of Authority Document
TX/RX Transmission/Reception
UDFB User Defined Functional Block
URA Unified Radio Applications
URAI Unified Radio Applications Interface
WLAN Wireless Local Area Network
4 Architectural Reference Model for Reconfigurable
Mobile Devices
4.1 Introduction
The present document describes those elements of a mobile device which are related to the software radio
reconfiguration only. For this reason,the usage of the term "architecture" is limited to those elements and not to the
overall HW/SW architecture of a mobile device which is out of the scope of the present document.
The present document is organized as follows:
Clause 4.2 describes the reconfigurable mobile device architecture in term of its components and entities.
Clause 4.3 describes the architecture reference model for multiradio applications.
Clause 4.4 describes the "Radio Computer".
Clause 4.5 describes the Radio Virtual Machine as part of the architecture.
Clause 4.6 describes the Unified Radio Application.
Clause 4.7 describes the security architecture for reconfigurable mobile devices.
Clause 5 describes the (logical) interfaces between the identified components/entities.
Clause 6 lists the operating procedures of a reconfigurable mobile devices.
Clause 4 includes a list of tables mapping the system requirements as defined in ETSI EN 302 969 [1] to the different
entities/components/units which have been identified. In general, according to the MDRC [1] the reconfigurable mobile
device belongs to, all the related mandatory functional requirements described in ETSI EN 302 969 [1] shall be
implemented.
ETSI
11 ETSI EN 303 095 V1.3.1 (2018-05)
4.2 Reconfigurable Mobile Devices - Architecture Components
for Radio Reconfiguration
4.2.1 High level description
Figure 4.1 shows the reconfigurable mobile device architectural components related to the radio reconfiguration as well
as the related entities. As shown in the figure, the following components can be identified:
• Communication Services Layer (CSL):
- 4 logical entities: Administration, Mobility Policy Manager, Networking Stack and Monitor.
• Radio Control Framework (RCF):
- 5 logical entities: Configuration Manager, Radio Connection Manager, Multi-Radio Controller, Resource
Manager and Flow Controller.
• Unified Radio Applications (URA).
• Radio Platform (consisting of RF Transceiver, Baseband, etc.).
These 4 components consist of Software (CSL, RCF) and/or Hardware (radio platform) entities and they shall be
interconnected through well defined interfaces as follows:
• Multiradio Interface (MURI) between CSL and RCF.
• Unified Radio Application Interface (URAI) between RCF and URA.
• Reconfigurable Radio Frequency Interface (RRFI) between URA and RF Transceiver.
The above mentioned interfaces are not covered by the present document.
Figure 4.1: Reconfigurable mobile device architecture components for radio reconfiguration
ETSI
12 ETSI EN 303 095 V1.3.1 (2018-05)
For each component, the required entities depend on the MDRC [1]. A Reconfigurable Mobile Device shall support all
the components and their entities as required by the corresponding MDRC as shown in Table 4.1. In case that a
Reconfigurable Mobile Device supports multiple MDRCs, the concerned Reconfigurable Mobile Device shall support
all the components and entities related to the highest supported MDRC.
Table 4.1: Required Components of the Reconfigurable Mobile Device Architecture
in function of the Mobile Device Reconfiguration Class
Mobile Device
Reconfiguration Required CSL Entities Required RCF Entities Required Interfaces
Class
MDRC-0 None None None
MDRC-1 Administrator, Mobility Policy Configuration Manager, Radio MURI
Manager, Networking Stack, Connection Manager, Flow
Monitor Controller
MDRC-2, MDRC-5 Administrator, Mobility Policy Configuration Manager, Radio MURI, URAI, RRFI
Manager, Networking Stack, Connection Manager, Multi-
Monitor Radio Controller, Flow
Controller
MDRC-3, MDRC-6 Administrator, Mobility Policy Configuration Manager, Radio MURI, URAI, RRFI
Manager, Networking Stack, Connection Manager, Multi-
Monitor Radio Controller, Flow
Controller
MDRC-4, MDRC-7 Administrator, Mobility Policy Configuration Manager, Radio MURI, URAI, RRFI
Manager, Networking Stack, Connection Manager, Multi-
Monitor Radio Controller, Resource
Manager, Flow Controller
The following clauses describe in more details the identified components as well as the related logical entities.
4.2.2 Communication Services Layer (CSL)
The CSL is a layer related to communication services supporting both generic applications and specific applications
related to multiradio applications. CSL includes the following 4 entities:
• Administrator entity
The Administrator entity shall include at least functions to request installation or uninstallation of URA, and
creating or deleting instances of URA. This typically includes the provision of information about the URA,
their status, etc. Furthermore, the Administrator includes two sub-entities: the Administrator Security Function
(ASF) and the RRS Configuration Manager (RRS-CM).
NOTE: In case that a snapshot function is required, the Administrator entity may store relevant RAPs, their
configuration parameters and information on the URA installation and execution history. When required,
the same steps can be executed by the Administrator entity to fall back to a previous snapshot.
• Mobility Policy Manager (MPM) entity
The MPM shall include at least functions for monitoring of the radio environments and MD capabilities, to
request activation or deactivation of URA, and to provide information about the URA list. It shall also make
selection among different radio access technologies and discover peer communication equipment and
arrangement of associations.
• Networking stack entity
The Networking stack entity shall include at least functions for sending and receiving of user data.
• Monitor entity
The Monitor entity shall include at least functions to transfer information from URA to user or proper
destination entity in MD.
ETSI
13 ETSI EN 303 095 V1.3.1 (2018-05)
4.2.3 Radio Control Framework (RCF)
The RCF provides a generic environment for the execution of URA, and a uniform way of accessing the functionality of
the Radio Computer and individual RAs. RCF provides services to CSL via the Multiradio Interface (MURI).
The RCF includes the following 5 entities for managing URA [i.2]:
• Configuration Manager (CM) entity
The CM shall include at least functions for installing/uninstalling and creating/deleting instances of URA as
well as management of and access to the radio parameters of the URA.
• Radio Connection Manager (RCM) entity
The RCM shall include at least functions for activating/deactivating URA according to user requests, and to
management of user data flows, which can also be switched from one RA to another.
• Flow Controller (FC) entity
The FC shall include at least functions for sending and receiving of user data packets and controlling the flow
of signalling packets.
• Multiradio Controller (MRC) entity
The MRC shall include at least functions to schedule the requests for radio resources issued by concurrently
executing URA, and to detect and manage the interoperability problems among the concurrently executed
URA.
• Resource Manager (RM) entity
The RM shall include at least functions to manage the computational resources, to share them among
simultaneously active URA, and to guarantee their real-time execution.
4.2.4 Unified Radio Application (URA)
As described in clause 4.2.3, the RCF, which represents functionalities provided by the Radio Computer, requires all
RAs to be subject to a common reconfiguration, multiradio execution and resource sharing strategy framework
(depending on the concerned MDRC). Since all RAs exhibit a common behaviour from the reconfigurable MD
perspective, those RAs are called URAs. The services relate to activation and deactivation, peer equipment discovery
and maintenance of communication over user data flows are provided at Unified Radio Application Interface (URAI),
which is an interface between URA and RCF.
4.2.5 Architectural Components System Requirements mapping
The logical entities above described are mapped to the system requirements described in ETSI EN 302 969 [1] as shown
in Table 4.2.
ETSI
14 ETSI EN 303 095 V1.3.1 (2018-05)
Table 4.2: Mapping of Architectural Components to the system requirements
described in ETSI EN 302 969 [1]
Entity/Component/Unit System Requirements [1] Comments
Administrator R-FUNC-MDR-01, The reconfigurable MD configuration is performed
R-FUNC-MDR-02, through downloading of the RAP into the
R-FUNC-SEC-01, reconfigurable MD and its installation. The
R-FUNC-SEC-02 requirements are described in clauses 6.4.1, 6.4.2,
and 6.6 of ETSI EN 302 969 [1]
Mobility Policy Manager R-FUNC-RAT–04, RAP into the reconfigurable MD and its installation.
R-FUNC-MDR-03 The requirements are described in clauses 6.1.4 and
6.4.3 of ETSI EN 302 969 [1]
Networking stack R-FUNC-RA-04, Management of data flows is required for basic
R-FUNC-RAT–05 TX/RX operation. The requirement is described in
Flow Control
clause 6.2.4 of ETSI EN 302 969 [1]
Monitor R-FUNC-RA-05 The RC in RA ensures the availability of context
information. The requirement is described in
clause 6.2.5 of ETSI EN 302 969 [1]
Configuration Manager R-FUNC-MDR-03 The radio configuration of a reconfigurable MD is
realized with the activation of URA. The requirement
Radio Connection Manager
is described in clause 6.4.3 of ETSI EN 302 969 [1]
Multiradio Controller R-FUNC-RAT–01, The proposed Mobile Device Architecture is suitable
R-FUNC-RAT–02, to support Multiple (parallel) connections to
R-FUNC-RAT–03, (heterogeneous) RATs. The requirements are
R-FUNC-RAT–05, described in clauses 6.1.1 and 6.1.2 of ETSI
R-FUNC-RAT–06 EN 302 969 [1]
Resource Manager R-FUNC-MDR-05 In case of dynamic resource sharing, the resource
allocation is performed in run time. The requirements
is described in clause 6.4.5 of ETSI EN 302 969 [1]
4.3 Reconfigurable Mobile Devices - Architecture Reference
Model for Multiradio Applications
4.3.1 High level description
Figure 4.2 exemplifies a Reconfigurable MD architecture reference model for multiradio applications. As shown in the
figure, the reconfigurable MD architecture shall include at least a Radio Computer. In the example of Figure 4.2, the
red-dotted part belongs to either Radio Computer or Application Processor depending on the specific implementation.
ETSI
15 ETSI EN 303 095 V1.3.1 (2018-05)
User
1 2 3
M
p p p
p Application
p p p
p
Application
A A A
A
Driver OS
Processor
Vendor
MURI
specific
Communication
Services Layer
URAI
Radio Controller
1 2 3
. . . N
.
A A A
A
R R R R
Function Block
Unified Radio Applications
Radio
Radio
Radio Control Framework*
OS
*Radio Control Framework includes
Computer
Normative
following components:
as defined
• Configuration Manager (CM)
Radio Platform Driver Radio Connection Manager (RCM) in the
Flow Controller (FC)
present
Multiradio Controller (MRC)
Radio Platform Resource Manager (RM)
document
Programmable Dedicated
RF transceiver Antenna
Hardware Hardware
Radio Spectrum
Figure 4.2: Reconfigurable Mobile Device (MD) architecture Reference
Model for multiradio applications
In the example of Figure 4.2, the operation of Application Processor is performed by a given Operating System (OS),
which is preferably performed on non-real-time bases, whereas Radio Computer's operation is performed by another
OS, which should support real-time operations of URA. The OS of Radio Computer is referred to as Radio OS (ROS) in
the present document.
The AP includes the following components:
• A Driver which has the purpose of activating the hardware devices (such as camera, speaker, etc.) on a given
MD.
• A non-real time OS for execution of Administrator, MPM, Networking stack and Monitor which are part of
the CSL as above described. For multiradio applications the OS may include RCF (Application Processor
part).
• The Radio Controller (RC) in Radio Application (RA) sending context information to the Monitor and
send/receive data to/from Networking stack.
The Radio Computer shall include the following components:
• ROS is a real-time Operating System.
• A radio platform driver which is a hardware driver for the ROS to interact with the radio platform hardware.
• The 5 entities of the RCF, specified in clause 4.2.3, are classified into two groups. One group relates to real-
time execution and the other group to non-real-time execution as shown in Figure 4.2. Which entities of RCF
interface relate to real-time and non-real-time execution, can be determined by each vendor.
ETSI
16 ETSI EN 303 095 V1.3.1 (2018-05)
4.3.2 Reference Model System Requirements mapping
The architecture reference model above described is mapped to the system requirements described in ETSI
EN 302 969 [1] as shown in Table 4.3.
Table 4.3: Mapping of Reference Model to the system requirements described in ETSI EN 302 969 [1]
Entity/Component/Unit System Requirements [1] Comments
Application Processor R-FUNC-RA-05 The Radio Controller in RA ensures the availability of
(vendor specific) context information. The requirement is described in
clause 6.2.5 of ETSI EN 302 969 [1]
Radio Computer R-FUNC-MDR-09, ROS enables management of timing constraints and
R-FUNC-RA-06 provides interface between URA and radio platform.
The requirements are described in clauses 6.4.9 and
6.2.6 of ETSI EN 302 969 [1]
4.4 Reconfigurable Mobile Devices - Radio Computer
4.4.1 High level description
The System Architecture for a Radio Computer is illustrated in Figure 4.3 and Figure 4.4. Some of the entities included
in the figures below may be located externally (in the "Cloud") in order to off-load processing from the concerned
Mobile Devices. As example, the Back End compiler in Figure 4.3 is moved into the "Cloud" as illustrated in
Figure 4.4.
Radio Apps
Source code
Multi Radio Interface (MURI)
Radio Control Framework
Radio
Unified Radio
Storage
Front-end
Radio Library Application
normative description Radio Apps Interface (URAI)
Compiler
configcode
Shadow
configcode 단추
RVM Radio Library BE
Radio Platform
im plem entat io n
native implementation Com pi le r
Radio OS
Radio Programming Interface
HW Radio Platform
RF part
Radio Apps
package
Radio Computer
upload
Radio Apps
Store
Figure 4.3: System architecture for Radio Computer where Radio Library and Back End (BE)
compiler are included within the Radio Computer
ETSI
17 ETSI EN 303 095 V1.3.1 (2018-05)
Vendor’s Radio Reconfiguration Service
Radio Apps
Source code
BE
Radio Library
native
Compiler
implementation
Multi Radio Interface (MURI)
Front-end
request
Unified Radio
Compiler Application
Radio
Interface (URAI)
Storage
download
RVM
implementation
Shadow
Radio Apps
configcode
단추
Radio Platform
exe code
Radio Library
native
implementation
Radio OS
request
Radio Programming Interface
download
HW Radio Platform
Radio Apps
RF part
package
Radio Computer
upload
Radio Apps
Store
Figure 4.4: System architecture for Radio Computer where Radio Library and BE compiler
are provided at a cloud outside the Radio Computer
Certification is required for Configcodes.
The Radio Computer shall provide communication capabilities for reconfigurable MDs and shall consist of:
•
...
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...