1、 ETSI EN 303 095 V1.2.1 (2015-06) Reconfigurable Radio Systems (RRS); Radio Reconfiguration related Architecture for Mobile Devices EUROPEAN STANDARD 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
2、 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 enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice The present document can be downloaded from: http:/www.etsi.org/standards-search The present docume
3、nt 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
4、 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 stat
5、us 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 reproduc
6、ed 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 e
7、xtend to reproduction in all media. European Telecommunications Standards Institute 2015. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand 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 Memb
8、ers and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI EN 303 095 V1.2.1 (2015-06) 3 Contents Intellectual Property Rights 4g3Foreword . 4g3Modal verbs terminology 4g31 Scope 5g32 References 5g32.1 Normative references
9、 . 5g32.2 Informative references 5g33 Definitions, symbols and abbreviations . 5g33.1 Definitions 5g33.2 Symbols 7g33.3 Abbreviations . 8g34 Architectural Reference Model for Reconfigurable Mobile Devices . 9g34.1 Introduction 9g34.2 Reconfigurable Mobile Devices - Architecture Components for Radio
10、Reconfiguration 9g34.2.1 High level description . 9g34.2.2 Communication Services Layer (CSL) . 11g34.2.3 Radio Control Framework (RCF) . 11g34.2.4 Unified Radio Application (URA) 12g34.2.5 Architectural Components System Requirements mapping 12g34.3 Reconfigurable Mobile Devices - Architecture Refe
11、rence Model for Multiradio Applications . 12g34.3.1 High level description . 12g34.3.2 Reference Model System Requirements mapping 13g34.4 Reconfigurable Mobile Devices - Radio Computer . 14g34.4.1 High level description . 14g34.4.2 Radio Computer System Requirement Mapping 16g34.5 Reconfigurable Mo
12、bile Devices - the Radio Virtual Machine . 17g34.5.1 Radio Virtual Machine basic principles 17g34.5.2 RVM System Requirement Mapping 18g34.6 Reconfigurable Mobile Devices - Unified Radio Applications 18g34.6.1 Introduction. 18g34.6.2 Distribution and Installation of RAP 18g34.6.3 Operational Structu
13、re of URA 24g34.6.4 URA System Requirement Mapping 27g35 Reference Points . 28g35.1 Introduction 28g35.2 Reference Points required for Installation/uninstallation and creating/deleting an instance of a URA 29g35.3 Reference Points required for list checking of URA 30g35.4 Reference Points required f
14、or activation/deactivation of URA 30g35.5 Reference Points required for transferring context information . 31g35.6 Reference Points required for creating data flow and sending/receiving user data 31g36 Reconfigurable MD high level operating procedures 32g36.1 Procedures for installation/uninstallati
15、on and creating/deleting instance of a URA 32g36.2 Procedures for list checking of URA 34g36.3 Procedures for activation/deactivation of URA 35g36.4 Procedures for transferring context information . 36g36.5 Procedure for creating data flow and sending/receiving user data . 38g3History 42g3ETSI ETSI
16、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 0
17、00 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 investig
18、ation, 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 (
19、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 (
20、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
21、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 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
22、 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 public
23、ation 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
24、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 docum
25、ent. 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 re
26、ferences, 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 follow
27、ing 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 Mobil
28、e 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
29、 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
30、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
31、-RAT performance metrics, etc. 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 o
32、f 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
33、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 so
34、urce 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 ex
35、ecution 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 sho
36、uld 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 Transf
37、orm (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
38、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
39、-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 Soft
40、ware 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: square4 source codes including Radio Library calls of Radio Library native implementation and Radio HAL calls; square4 IRs inclu
41、ding Radio Library calls of Radio Library native implementation and radio HAL calls; square4 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
42、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 Configur
43、ation Manager (CM), Radio Connection Manager (RCM), Flow Controller (FC) and Multiradio Controller (MRC). The Resource Manager (RM) is typically part of OS. ETSI ETSI EN 303 095 V1.2.1 (2015-06) 7 Radio Controller (RC): functional component of RA for transferring context information from correspondi
44、ng 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 Manage
45、r (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 baseba
46、nd 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 dev
47、elopers. 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 managem
48、ent 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 transcei
49、ver, 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 bas
