ETSI EN 303 095 V1.2.1 (2015-06)
Reconfigurable Radio Systems (RRS); Radio Reconfiguration related Architecture for Mobile Devices
Reconfigurable Radio Systems (RRS); Radio Reconfiguration related Architecture for Mobile Devices
REN/RRS-0211
Radijski sistemi z možnostjo preoblikovanja (RRS) - Preoblikovanje radia glede na arhitekturo za mobilne naprave
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
Buy Standard
Standards Content (Sample)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Radijski sistemi z možnostjo preoblikovanja (RRS) - Preoblikovanje radia glede na arhitekturo za mobilne napraveReconfigurable Radio Systems (RRS); Radio Reconfiguration related Architecture for Mobile Devices33.060.01Radijske komunikacije na splošnoRadiocommunications in generalICS:Ta slovenski standard je istoveten z:EN 303 095 V1.2.1SIST EN 303 095 V1.2.1:2015en,fr,de01-oktober-2015SIST EN 303 095 V1.2.1:2015SLOVENSKI
STANDARD
SIST EN 303 095 V1.2.1:2015
ETSI EN 303 095 V1.2.1 (2015-06) Reconfigurable Radio Systems (RRS); Radio Reconfiguration related Architecture for Mobile Devices
EUROPEAN STANDARD SIST EN 303 095 V1.2.1:2015
ETSI ETSI EN 303 095 V1.2.1 (2015-06) 2
Reference REN/RRS-0211 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 http://portal.etsi.org/tb/status/status.asp 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.
© European Telecommunications Standards Institute 2015. All rights reserved.
DECTTM, PLUGTESTSTM, UMTSTM and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM and LTE™ are Trade Marks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association. SIST EN 303 095 V1.2.1:2015
ETSI ETSI EN 303 095 V1.2.1 (2015-06) 3 Contents Intellectual Property Rights . 4 Foreword . 4 Modal verbs terminology . 4 1 Scope . 5 2 References . 5 2.1 Normative references . 5 2.2 Informative references . 5 3 Definitions, symbols and abbreviations . 5 3.1 Definitions . 5 3.2 Symbols . 7 3.3 Abbreviations . 8 4 Architectural Reference Model for Reconfigurable Mobile Devices . 9 4.1 Introduction . 9 4.2 Reconfigurable Mobile Devices - Architecture Components for Radio Reconfiguration . 9 4.2.1 High level description . 9 4.2.2 Communication Services Layer (CSL) . 11 4.2.3 Radio Control Framework (RCF) . 11 4.2.4 Unified Radio Application (URA) . 12 4.2.5 Architectural Components System Requirements mapping . 12 4.3 Reconfigurable Mobile Devices - Architecture Reference Model for Multiradio Applications . 12 4.3.1 High level description . 12 4.3.2 Reference Model System Requirements mapping . 13 4.4 Reconfigurable Mobile Devices - Radio Computer . 14 4.4.1 High level description . 14 4.4.2 Radio Computer System Requirement Mapping . 16 4.5 Reconfigurable Mobile Devices - the Radio Virtual Machine . 17 4.5.1 Radio Virtual Machine basic principles . 17 4.5.2 RVM System Requirement Mapping . 18 4.6 Reconfigurable Mobile Devices - Unified Radio Applications . 18 4.6.1 Introduction. 18 4.6.2 Distribution and Installation of RAP . 18 4.6.3 Operational Structure of URA . 24 4.6.4 URA System Requirement Mapping . 27 5 Reference Points . 28 5.1 Introduction . 28 5.2 Reference Points required for Installation/uninstallation and creating/deleting an instance of a URA . 29 5.3 Reference Points required for list checking of URA . 30 5.4 Reference Points required for activation/deactivation of URA . 30 5.5 Reference Points required for transferring context information . 31 5.6 Reference Points required for creating data flow and sending/receiving user data . 31 6 Reconfigurable MD high level operating procedures . 32 6.1 Procedures for installation/uninstallation and creating/deleting instance of a URA . 32 6.2 Procedures for list checking of URA . 34 6.3 Procedures for activation/deactivation of URA . 35 6.4 Procedures for transferring context information . 36 6.5 Procedure for creating data flow and sending/receiving user data . 38 History . 42
SIST EN 303 095 V1.2.1:2015
ETSI ETSI EN 303 095 V1.2.1 (2015-06) 4 Intellectual Property Rights IPRs essential or potentially essential to the present document 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 (http://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. 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: 18 June 2015 Date of latest announcement of this EN (doa): 30 September 2015 Date of latest publication of new National Standard or endorsement of this EN (dop/e):
31 March 2016 Date of withdrawal of any conflicting National Standard (dow): 31 March 2016
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. SIST EN 303 095 V1.2.1:2015
ETSI ETSI EN 303 095 V1.2.1 (2015-06) 5 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 reference document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found at http://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.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 reference 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". 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. SIST EN 303 095 V1.2.1:2015
ETSI ETSI EN 303 095 V1.2.1 (2015-06) 6 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. 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. 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. SIST EN 303 095 V1.2.1:2015
ETSI ETSI EN 303 095 V1.2.1 (2015-06) 7 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: 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. 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, 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: M1 Number of SFBs implemented on Radio computer M2 Number of SFBs implemented on hardware accelerators SIST EN 303 095 V1.2.1:2015
ETSI ETSI EN 303 095 V1.2.1 (2015-06) 8 3.3 Abbreviations For the purposes of the present document, the following abbreviations apply: AOT Ahead-Of-Time AP Application Processor 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 MD Mobile Device MDRC Mobile Device Reconfiguration Class MIMO Multi-Input-Multi-Output MPM Mobility Policy Manager MRC MultiRadio Controller MURI MUltiRadio Interface OS Operating System RA Radio Application RAP Radio Application Package RC Radio Controller RCF Radio Control Framework RCM Radio Connection Manager RF Radio Frequency RM Resource Manager ROS Radio Operating System RPI Radio Programming Interface RRFI Reconfigurable Radio Frequency Interface RVM Radio Virtual Machine SDR Software Defined Radio SFB Standard Functional Block SW SoftWare TX/RX Transmission/Reception UDFB User Defined Functional Block URA Unified Radio Applications URAI Unified Radio Applications Interface WLAN Wireless Local Area Network SIST EN 303 095 V1.2.1:2015
ETSI ETSI EN 303 095 V1.2.1 (2015-06) 9 4 Architectural Reference Model for Reconfigurable Mobile Devices 4.1 Introduction The present deliverable describes those elements of a mobile device which are related to the software radio reconfiguration only. For this reason, whenever we talk about "architecture" we refer only 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 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. 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. SIST EN 303 095 V1.2.1:2015
ETSI ETSI EN 303 095 V1.2.1 (2015-06) 10
Figure 4.1: Reconfigurable Mobile Device Architecture Components for Radio Reconfiguration 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 Class Required CSL Entities Required RCF Entities Required Interfaces MDRC-0 None None None MDRC-1 Administrator, Mobility Policy Manager, Networking Stack, Monitor Configuration Manager, Radio Connection Manager, Flow Controller MURI MDRC-2, MDRC-5 Administrator, Mobility Policy Manager, Networking Stack, Monitor Configuration Manager, Radio Connection Manager, Multi-Radio Controller, Flow Controller MURI, URAI, RRFI MDRC-3, MDRC-6 Administrator, Mobility Policy Manager, Networking Stack, Monitor Configuration Manager, Radio Connection Manager, Multi-Radio Controller, Flow Controller MURI, URAI, RRFI MDRC-4, MDRC-7 Administrator, Mobility Policy Manager, Networking Stack, Monitor Configuration Manager, Radio Connection Manager, Multi-Radio Controller, Resource Manager, Flow Controller MURI, URAI, RRFI
The following clauses describe in more details the identified components as well as the related logical entities. SIST EN 303 095 V1.2.1:2015
ETSI ETSI EN 303 095 V1.2.1 (2015-06) 11 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. • 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. 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
...
ETSI EN 303 095 V1.2.1 (2015-06)
EUROPEAN STANDARD
Reconfigurable Radio Systems (RRS);
Radio Reconfiguration related Architecture for Mobile Devices
---------------------- Page: 1 ----------------------
2 ETSI EN 303 095 V1.2.1 (2015-06)
Reference
REN/RRS-0211
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
http://portal.etsi.org/tb/status/status.asp
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.
© European Telecommunications Standards Institute 2015.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.
TM
3GPP and LTE™ are Trade Marks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI
---------------------- Page: 2 ----------------------
3 ETSI EN 303 095 V1.2.1 (2015-06)
Contents
Intellectual Property Rights . 4
Foreword . 4
Modal verbs terminology . 4
1 Scope . 5
2 References . 5
2.1 Normative references . 5
2.2 Informative references . 5
3 Definitions, symbols and abbreviations . 5
3.1 Definitions . 5
3.2 Symbols . 7
3.3 Abbreviations . 8
4 Architectural Reference Model for Reconfigurable Mobile Devices . 9
4.1 Introduction . 9
4.2 Reconfigurable Mobile Devices - Architecture Components for Radio Reconfiguration . 9
4.2.1 High level description . 9
4.2.2 Communication Services Layer (CSL) . 11
4.2.3 Radio Control Framework (RCF) . 11
4.2.4 Unified Radio Application (URA) . 12
4.2.5 Architectural Components System Requirements mapping . 12
4.3 Reconfigurable Mobile Devices - Architecture Reference Model for Multiradio Applications . 12
4.3.1 High level description . 12
4.3.2 Reference Model System Requirements mapping . 13
4.4 Reconfigurable Mobile Devices - Radio Computer . 14
4.4.1 High level description . 14
4.4.2 Radio Computer System Requirement Mapping . 16
4.5 Reconfigurable Mobile Devices - the Radio Virtual Machine . 17
4.5.1 Radio Virtual Machine basic principles . 17
4.5.2 RVM System Requirement Mapping . 18
4.6 Reconfigurable Mobile Devices - Unified Radio Applications . 18
4.6.1 Introduction. 18
4.6.2 Distribution and Installation of RAP . 18
4.6.3 Operational Structure of URA . 24
4.6.4 URA System Requirement Mapping . 27
5 Reference Points . 28
5.1 Introduction . 28
5.2 Reference Points required for Installation/uninstallation and creating/deleting an instance of a URA . 29
5.3 Reference Points required for list checking of URA . 30
5.4 Reference Points required for activation/deactivation of URA . 30
5.5 Reference Points required for transferring context information . 31
5.6 Reference Points required for creating data flow and sending/receiving user data . 31
6 Reconfigurable MD high level operating procedures . 32
6.1 Procedures for installation/uninstallation and creating/deleting instance of a URA . 32
6.2 Procedures for list checking of URA . 34
6.3 Procedures for activation/deactivation of URA . 35
6.4 Procedures for transferring context information . 36
6.5 Procedure for creating data flow and sending/receiving user data . 38
History . 42
ETSI
---------------------- Page: 3 ----------------------
4 ETSI EN 303 095 V1.2.1 (2015-06)
Intellectual Property Rights
IPRs essential or potentially essential to the present document 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 (http://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.
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: 18 June 2015
Date of latest announcement of this EN (doa): 30 September 2015
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 31 March 2016
Date of withdrawal of any conflicting National Standard (dow): 31 March 2016
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
---------------------- Page: 4 ----------------------
5 ETSI EN 303 095 V1.2.1 (2015-06)
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
reference document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://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.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
reference 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".
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.
ETSI
---------------------- Page: 5 ----------------------
6 ETSI EN 303 095 V1.2.1 (2015-06)
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.
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.
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.
ETSI
---------------------- Page: 6 ----------------------
7 ETSI EN 303 095 V1.2.1 (2015-06)
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: 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.
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,
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
1
M Number of SFBs implemented on hardware accelerators
2
ETSI
---------------------- Page: 7 ----------------------
8 ETSI EN 303 095 V1.2.1 (2015-06)
3.3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
AOT Ahead-Of-Time
AP Application Processor
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
MD Mobile Device
MDRC Mobile Device Reconfiguration Class
MIMO Multi-Input-Multi-Output
MPM Mobility Policy Manager
MRC MultiRadio Controller
MURI MUltiRadio Interface
OS Operating System
RA Radio Application
RAP Radio Application Package
RC Radio Controller
RCF Radio Control Framework
RCM Radio Connection Manager
RF Radio Frequency
RM Resource Manager
ROS Radio Operating System
RPI Radio Programming Interface
RRFI Reconfigurable Radio Frequency Interface
RVM Radio Virtual Machine
SDR Software Defined Radio
SFB Standard Functional Block
SW SoftWare
TX/RX Transmission/Reception
UDFB User Defined Functional Block
URA Unified Radio Applications
URAI Unified Radio Applications Interface
WLAN Wireless Local Area Network
ETSI
---------------------- Page: 8 ----------------------
9 ETSI EN 303 095 V1.2.1 (2015-06)
4 Architectural Reference Model for Reconfigurable
Mobile Devices
4.1 Introduction
The present deliverable describes those elements of a mobile device which are related to the software radio
reconfiguration only. For this reason, whenever we talk about "architecture" we refer only 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 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.
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.
ETSI
---------------------- Page: 9 ----------------------
10 ETSI EN 303 095 V1.2.1 (2015-06)
Figure 4.1: Reconfigurable Mobile Device Architecture Components for Radio Reconfiguration
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.
ETSI
---------------------- Page: 10 ----------------------
11 ETSI EN 303 095 V1.2.1 (2015-06)
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.
• 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.
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 concur
...
Draft ETSI EN 303 095 V1.2.1 (2015-02)
EUROPEAN STANDARD
Reconfigurable Radio Systems (RRS);
Radio Reconfiguration related Architecture for Mobile Devices
---------------------- Page: 1 ----------------------
2 Draft ETSI EN 303 095 V1.2.1 (2015-02)
Reference
REN/RRS-0211
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
http://portal.etsi.org/tb/status/status.asp
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.
© European Telecommunications Standards Institute 2015.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.
TM TM
3GPP and LTE are Trade Marks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI
---------------------- Page: 2 ----------------------
3 Draft ETSI EN 303 095 V1.2.1 (2015-02)
Contents
Intellectual Property Rights . 4
Foreword . 4
Modal verbs terminology . 4
1 Scope . 5
2 References . 5
2.1 Normative references . 5
2.2 Informative references . 5
3 Definitions, symbols and abbreviations . 5
3.1 Definitions . 5
3.2 Symbols . 8
3.3 Abbreviations . 8
4 Architectural Reference Model for Reconfigurable Mobile Devices . 9
4.1 Introduction . 9
4.2 Reconfigurable Mobile Devices - Architecture Components for Radio Reconfiguration . 9
4.2.1 High level description . 9
4.2.2 Communication Services Layer (CSL) . 11
4.2.3 Radio Control Framework (RCF) . 11
4.2.4 Unified Radio Application (URA) . 12
4.2.5 Architectural Components System Requirements mapping . 12
4.3 Reconfigurable Mobile Devices - Architecture Reference Model for Multiradio Applications . 12
4.3.1 High level description . 12
4.3.2 Reference Model System Requirements mapping . 13
4.4 Reconfigurable Mobile Devices - Radio Computer . 14
4.4.1 High level description . 14
4.4.2 Radio Computer System Requirement Mapping . 16
4.5 Reconfigurable Mobile Devices - the Radio Virtual Machine . 17
4.5.1 Radio Virtual Machine basic principles . 17
4.5.2 RVM System Requirement Mapping . 18
4.6 Reconfigurable Mobile Devices - Unified Radio Applications . 18
4.6.1 Introduction. 18
4.6.2 Distribution and Installation of RAP . 18
4.6.3 Operational Structure of URA . 24
4.6.4 URA System Requirement Mapping . 27
5 Reference Points . 28
5.1 Introduction . 28
5.2 Reference Points required for Installation/uninstallation and creating/deleting an instance of a URA . 29
5.3 Reference Points required for list checking of URA . 30
5.4 Reference Points required for activation/deactivation of URA . 30
5.5 Reference Points required for transferring context information . 31
5.6 Reference Points required for creating data flow and sending/receiving user data . 31
6 Reconfigurable MD high level operating procedures . 32
6.1 Procedures for installation/uninstallation and creating/deleting instance of a URA . 32
6.2 Procedures for list checking of URA . 34
6.3 Procedures for activation/deactivation of URA . 35
6.4 Procedures for transferring context information . 36
6.5 Procedure for creating data flow and sending/receiving user data . 37
History . 42
ETSI
---------------------- Page: 3 ----------------------
4 Draft ETSI EN 303 095 V1.2.1 (2015-02)
Intellectual Property Rights
IPRs essential or potentially essential to the present document 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 (http://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.
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", "may not", "need", "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
---------------------- Page: 4 ----------------------
5 Draft ETSI EN 303 095 V1.2.1 (2015-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
reference document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://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.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
reference 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".
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
ETSI
---------------------- Page: 5 ----------------------
6 Draft ETSI EN 303 095 V1.2.1 (2015-02)
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.
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.
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.
ETSI
---------------------- Page: 6 ----------------------
7 Draft ETSI EN 303 095 V1.2.1 (2015-02)
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 library: library of SFB that is provided by a platform vendor in a form of platform-specific executable code
NOTE 1: SFBs implement reference codes of functions which are typical for radio signal processing. They are not
atomic and their source codes are typed and visible for RA developers.
NOTE 2: 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.
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,
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].
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
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.
ETSI
---------------------- Page: 7 ----------------------
8 Draft ETSI EN 303 095 V1.2.1 (2015-02)
3.2 Symbols
For the purposes of the present document, the following symbols apply:
M Number of SFBs implemented on Radio computer
1
Number of SFBs implemented on hardware accelerators
M
2
3.3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
AOT Ahead-Of-Time
AP Application Processor
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
MD Mobile Device
MDRC Mobile Device Reconfiguration Class
MIMO Multi-Input-Multi-Output
MPM Mobility Policy Manager
MRC MultiRadio Controller
MURI MUltiRadio Interface
OS Operating System
RA Radio Application
RAP Radio Application Package
RC Radio Controller
RCF Radio Control Framework
RCM Radio Connection Manager
RF Radio Frequency
RM Resource Manager
ROS Radio Operating System
RPI Radio Programming Interface
RRFI Reconfigurable Radio Frequency Interface
RVM Radio Virtual Machine
SDR Software Defined Radio
SFB Standard Functional Block
SW SoftWare
TX/RX Transmission/Reception
UDFB User Defined Functional Block
URA Unified Radio Applications
URAI Unified Radio Applications Interface
WLAN Wireless Local Area Network
ETSI
---------------------- Page: 8 ----------------------
9 Draft ETSI EN 303 095 V1.2.1 (2015-02)
4 Architectural Reference Model for Reconfigurable
Mobile Devices
4.1 Introduction
The present deliverable describes those elements of a mobile device which are related to the software radio
reconfiguration only. For this reason, whenever we talk about "architecture" we refer only 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 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.
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.
ETSI
---------------------- Page: 9 ----------------------
10 Draft ETSI EN 303 095 V1.2.1 (2015-02)
The above mentioned interfaces are not covered by the present document.
Figure 4.1: Reconfigurable Mobile Device Architecture Components for Radio Reconfiguration
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.
ETSI
---------------------- Page: 10 ----------------------
11 Draft ETSI EN 303 095 V1.2.1 (2015-02)
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.
• 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.
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 control
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.