1、 ETSI EN 302 969 V1.2.1 (2014-11) Reconfigurable Radio Systems (RRS); Radio Reconfiguration related Requirements for Mobile Devices EUROPEAN STANDARD ETSI ETSI EN 302 969 V1.2.1 (2014-11) 2Reference REN/RRS-0210 Keywords CRS, mobile, SDR ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - F
2、RANCE 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 The present document may be made available in
3、 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 prevail
4、ing 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 d
5、ocuments 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: http:/portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced or utilized in any form or by an
6、y 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.
7、 European Telecommunications Standards Institute 2014. 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 Members and of the 3GPP Organizational
8、Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI EN 302 969 V1.2.1 (2014-11) 3Contents Intellectual Property Rights 5g3Foreword . 5g3Modal verbs terminology 5g31 Scope 6g32 References 6g32.1 Normative references . 6g32.2 Informative references 6g3
9、3 Definitions and abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 8g34 Requirement Organization and Methodology 8g34.1 Requirement Organization 8g34.2 Requirement Format . 9g34.3 Requirement Formulation . 10g35 Working assumptions . 10g35.1 Assumptions . 10g35.1.1 Mobile Device Reconfigura
10、tion Classes . 10g36 Functional Requirements 13g36.1 Requirements on RAT Link Support and Management . 13g36.1.1 R-FUNC-RAT01 Function for MDRC-1 to MDRC-7 13g36.1.2 R-FUNC-RAT02 Function for MDRC-1 to MDRC-7 13g36.1.3 R-FUNC-RAT03 Function for MDRC-1 to MDRC-7 13g36.1.4 R-FUNC-RAT04 Function for MD
11、RC-1 to MDRC-7 14g36.1.5 R-FUNC-RAT05 Function for MDRC-1 to MDRC-7 14g36.1.6 R-FUNC-RAT06 Function for MDRC-1 to MDRC-7 14g36.2 Radio Application Requirements . 14g36.2.1 R-FUNC-RA-01 Radio Applications Support for MDRC-1 to MDRC-7 14g36.2.2 R-FUNC-RA-02 Composition for MDRC-1 to MDRC-7 14g36.2.3 R
12、-FUNC-RA-03 Concurency for MDRC-1 to MDRC-7 14g36.2.4 R-FUNC-RA-04 Data for MDRC-1 to MDRC-7 . 14g36.2.5 R-FUNC-RA-05 Context Information for MDRC-1 to MDRC-7 14g36.2.6 R-FUNC-RA-06 Pipelining for MDRC-2 to MDRC-7 15g36.3 Radio Application Functional Block Requirements . 15g36.3.1 R-FUNC-FB-01 Imple
13、mentation for MDRC-2 to MDRC-7 15g36.3.2 R-FUNC-FB-02 Execution for MDRC-2 to MDRC-7 . 15g36.3.3 R-FUNC-FB-03 Side Effects for MDRC-2 to MDRC-7 16g36.3.4 R-FUNC-FB-04 Shared Data for MDRC-2 to MDRC-7 16g36.3.5 R-FUNC-FB-05 Concurrency for MDRC-2 to MDRC-7 . 16g36.3.6 R-FUNC-FB-06 Extendability for M
14、DRC-2 to MDRC-7 16g36.4 Mobile Device Reconfiguration Requirements 16g36.4.1 R-FUNC-MDR-01 Platform-specific Executable Code for MDRC-2, MDRC-3 or MDRC-4 . 16g36.4.2 R-FUNC-MDR-02 Platform-independent Source Code or IR for MDRC-5, MDRC-6 or MDRC-7 . 17g36.4.3 R-FUNC-MDR-03 Radio Configuration of Pla
15、tform MDRC-1 to MDRC-7 . 17g36.4.4 R-FUNC-MDR-04 Radio Programming for MDRC-1 to MDRC-7 . 17g36.4.5 R-FUNC-MDR-05 Dynamic Execution for MDRC-4, and MDRC-7 17g36.4.6 R-FUNC-MDR-06 Independency on Memory Model for MDRC-1 to MDRC-7 17g36.4.7 R-FUNC-MDR-07 Code for MDRC-2 to MDRC-7 . 17g36.4.8 R-FUNC-MD
16、R-08 IR Format for MDRC-5 to MDRC-7 . 18g36.4.9 R-FUNC-MDR-09 Timing Constraints for MDRC-1 to MDRC-7 18g36.4.10 R-FUNC-MDR-10 Platform Independency for MDRC-5 to MDRC-7 18g36.4.11 R-FUNC-MDR-11 Radio Application for MDRC-5 to MDRC-7 18g36.4.12 R-FUNC-MDR-12 Function Granularity for MDRC-1 to MDRC-7
17、 18g3ETSI ETSI EN 302 969 V1.2.1 (2014-11) 46.4.13 R-FUNC-MDR-13 Radio Virtual Machine for MDRC-2 to MDRC-7 . 18g36.4.14 R-FUNC-MDR-14 RadioVirtual Machine Structure for MDRC-2 to MDRC-7 18g36.4.15 R-FUNC-MDR-15 Selection of Radio Virtual Machine Protection Class for MDRC-2 to MDRC-7 18g36.5 Radio F
18、requency(RF) Transceiver Requirements 20g36.5.1 R-FUNC-RFT-01 RF Configuration for MDRC-1 to MDRC-7 . 20g36.5.2 R-FUNC-RFT-02 Extendibility for multiple-antenna system for MDRC-1 to MDRC-7 . 20g36.5.3 R-FUNC-RFT-03 Capability of multiple frequency bands for MDRC-1 to MDRC-7 . 20g36.5.4 R-FUNC-RFT-04
19、 Reconfigurability of RF Transceiver for MDRC-1 to MDRC-7 . 20g36.5.5 R-FUNC-RFT-05 Interoperability of radio resources for MDRC-2 to MDRC-7 . 20g36.5.6 R-FUNC-RFT-06 Testability of radio equipment for MDRC-1 to MDRC-7 . 20g36.5.7 R-FUNC-RFT-07 Unified representation of control information for MDRC-
20、1 to MDRC-7 . 20g36.5.8 R-FUNC-RFT-08 Unified representation of data payload for MDRC-1 to MDRC-7 21g36.5.9 R-FUNC-RFT-09 Selection of RF Protection Class for MDRC-1 to MDRC-7 . 21g3History 22g3ETSI ETSI EN 302 969 V1.2.1 (2014-11) 5Intellectual Property Rights IPRs essential or potentially essentia
21、l 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
22、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
23、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 tr
24、ansposition dates Date of adoption of this EN: 10 November 2014 Date of latest announcement of this EN (doa): 28 February 2015 Date of latest publication of new National Standard or endorsement of this EN (dop/e): 31 August 2015 Date of withdrawal of any conflicting National Standard (dow): 31 Augus
25、t 2015 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
26、). “must“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI EN 302 969 V1.2.1 (2014-11) 61 Scope The scope of the present document is to define the high level system requirements for reconfigurable Mobile Devices enabling the provision of Radio Applic
27、ations. The work will be based on the Use Cases defined in TR 103 062 i.1 and TR 102 944 i.2. 2 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-spec
28、ific 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 http:/docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were val
29、id at the time of publication, ETSI cannot guarantee their long term validity. 2.1 Normative references The following referenced documents are necessary for the application of the present document. Not applicable. 2.2 Informative references The following referenced documents are not necessary for th
30、e 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
31、Radio Systems (RRS); Use Cases for Baseband Interfaces for Unified Radio Applications of Mobile Device“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply: Functional Block (FB): function needed for real-time implement
32、ation of Radio Application(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 Radio Application(s). NOTE 2: Functional blocks are categorized
33、 into standard functional blocks and user defined functional blocks. In more details: 1) Standard functional blocks can be shared by many Radio Applications. For example, Forward Error Correction (FEC), Fast Fourier Transform (FFT)/Inverse Fast Fourier Transform (IFFT), (de)interleaver, Turbo coding
34、, Viterbi coding, Multiple Input Multiple Output (MIMO), Beamforming, etc are the typical category of standard functional block. ETSI ETSI EN 302 969 V1.2.1 (2014-11) 72) User defined functional blocks include those functional blocks that are dependent upon a specific Radio Application. They are use
35、d to support special function(s) required in a specific Radio Application 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
36、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. network coding: technique in which transmitted data is encoded and decoded to improve network performance Radio Application (RA): so
37、ftware 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: Radio applications might have different forms of representation. They are represe
38、nted as: square4 source codes including Radio Library calls of Radio Library native implementation and Radio HAL calls; square4 Intermediate Representations (IRs) including Radio Library calls of Radio Library native implementation and radio HAL calls; square4 Executable codes for a particular radio
39、 platform. radio library: library of Standard Functional Blocks (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
40、 typed and visible for Radio Application developers. NOTE 2: An SFB is implemented through a Radio Hardware Abstraction Layer (HAL) when the SFB is implemented on dedicated HW accelerators. Radio HAL is part of ROS. Radio Virtual Machine (RVM): abstract machine supporting reactive and concurrent exe
41、cutions NOTE: A Radio Virtual Machine 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 cap
42、abilities providing support for radio reconfiguration NOTE: Reconfigurable Mobile Devices include but are not limited to: Smartphones, Feature Phones, Tablets, Laptops. resources: Hardware Resources that a Radio Application needs in active state NOTE 1: Resources are provided by the reconfigurable M
43、obile Device (MD), to be used by the Radio Applications when they are active. Radio Applications provide their Resource needs (e.g. using operational states) so that the multiradio computer may judge whether these Resources are available, in order to ensure non-conflicting operation with other Radio
44、 Applications. Resources may or may not be shared in the reconfigurable MD. NOTE 2: Resources may include processors, accelerators, memory, Radio Frequency circuitry, etc. ETSI ETSI EN 302 969 V1.2.1 (2014-11) 83.2 Abbreviations For the purposes of the present document, the following abbreviations a
45、pply: ASIC Application Specific Integrated Circuit BER Bit Error Rate CAT Category CR Cognitive Radio DoA Direction of ArrivalFB Functional Block FEC Forward Error Correction FFT Fast Fourier Transform HAL Hardware Abstraction Layer IR Intermediate Representation LTE Long Term Evolution MAC Media Ac
46、cess Control MD Mobile Device MDRC Mobile Device Reconfiguration Class MIMO Multi-Input Multi-Output MU-MIMO Multi User- Multi-Input Multi-Output PER Packet Error Rate PMI Precoding Matrix Indicator RA Radio Application RAT Radio Access Technology RF Radio Frequency RI Rank Indicator ROS Radio Opera
47、ting System RRS Reconfigurable Radio Systems RSSI Received Signal Strength Indication RVM Radio Virtual Machine Rx Receive SDR Software Defined Radio SFB Standard Functional Block SINR Signal to Interference-plus-Noise Ratio SU-MIMO Single User- Multi-Input Multi-Output Tx Transmit UDFB User Defined
48、 Functional Block WiFi Wireless Fidelity 4 Requirement Organization and Methodology This clause is containing the description of how the requirements are organized and the related format. 4.1 Requirement Organization As shown in Figure 1, all requirements described in the present document belong to
49、one single category (the functional requirements category). Requirements are, in turn, organized into groups. ETSI ETSI EN 302 969 V1.2.1 (2014-11) 9Figure 1: Overall requirements structure 4.2 Requirement Format A letter code system is defined which makes a unique identification of each requirement R-. Each requirement is constructed as follows: R-: Standard requirement prefix Code Category FUNC Functional aspects : Requirement group identifier. A letter code will be used for this identifier. The three first letters will give the identifier of the group
