1、 ETSI EN 302 969 V1.3.1 (2018-05) Reconfigurable Radio Systems (RRS); Radio Reconfiguration related requirements for Mobile Devices G1G2G3G4G5G1G6G7G8G9G10G6G7G11G6G3G11G8ETSI ETSI EN 302 969 V1.3.1 (2018-05) 2 Reference REN/RRS-0215 Keywords CRS, mobile, SDR ETSI 650 Route des Lucioles F-06921 Soph
2、ia 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 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 pr
3、esent 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 ver
4、sions 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
5、current status of this and other ETSI documents is available at https:/portal.etsi.org/TB/ETSIDeliverableStatus.aspx If you find errors in the present document, please send your comment to one of the following services: https:/portal.etsi.org/People/CommiteeSupportStaff.aspx Copyright Notification N
6、o 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 f
7、oregoing restriction extend to reproduction in all media. ETSI 2018. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are trademarks of ETSI registered for the benefit of its Members. 3GPPTM and LTETMare trademarks of ETSI registered for the benefit of its Members and of the 3GPP Or
8、ganizational Partners. oneM2M logo is protected for the benefit of its Members. GSMand the GSM logo are trademarks registered and owned by the GSM Association. ETSI ETSI EN 302 969 V1.3.1 (2018-05) 3 Contents Intellectual Property Rights . 5G1Foreword 5G1Modal verbs terminology . 5G11 Scope . 6G12 R
9、eferences . 6G12.1 Normative references . 6G12.2 Informative references . 6G13 Definitions and abbreviations 6G13.1 Definitions . 6G13.2 Abbreviations 8G14 Requirement organization and methodology . 8G14.0 General 8G14.1 Requirement organization 8G14.2 Requirement format . 9G14.3 Requirement formula
10、tion 10G15 Working assumptions 10G15.1 Assumptions .10G15.1.1 Mobile device reconfiguration classes 10G16 Functional requirements 13G16.1 Requirements on RAT link support and management 13G16.1.1 R-FUNC-RAT01 Function for MDRC-1 to MDRC-7 13G16.1.2 R-FUNC-RAT02 Function for MDRC-1 to MDRC-7 13G16.1.
11、3 R-FUNC-RAT03 Function for MDRC-1 to MDRC-7 13G16.1.4 R-FUNC-RAT04 Function for MDRC-1 to MDRC-7 13G16.1.5 R-FUNC-RAT05 Function for MDRC-1 to MDRC-7 13G16.1.6 R-FUNC-RAT06 Function for MDRC-1 to MDRC-7 13G16.2 Radio application requirements 14G16.2.0 General 14G16.2.1 R-FUNC-RA-01 Radio Applicatio
12、ns Support for MDRC-1 to MDRC-7 .14G16.2.2 R-FUNC-RA-02 Composition for MDRC-1 to MDRC-7 14G16.2.3 R-FUNC-RA-03 Concurrency for MDRC-1 to MDRC-7 14G16.2.4 R-FUNC-RA-04 Data for MDRC-1 to MDRC-7 .14G16.2.5 R-FUNC-RA-05 Context Information for MDRC-1 to MDRC-7 14G16.2.6 R-FUNC-RA-06 Pipelining for MDR
13、C-2 to MDRC-7 .14G16.3 Radio Application functional block requirements 15G16.3.1 R-FUNC-FB-01 Implementation for MDRC-2 to MDRC-7.15G16.3.2 R-FUNC-FB-02 Execution for MDRC-2 to MDRC-7 15G16.3.3 R-FUNC-FB-03 Side Effects for MDRC-2 to MDRC-7 15G16.3.4 R-FUNC-FB-04 Shared Data for MDRC-2 to MDRC-7 15G
14、16.3.5 R-FUNC-FB-05 Concurrency for MDRC-2 to MDRC-7 .15G16.3.6 R-FUNC-FB-06 Extendibility for MDRC-2 to MDRC-7 .15G16.4 Mobile device reconfiguration requirements 16G16.4.1 R-FUNC-MDR-01 Platform-specific Executable Code for MDRC-2, MDRC-3 or MDRC-4 .16G16.4.2 R-FUNC-MDR-02 Platform-independent Sou
15、rce Code or IR for MDRC-5, MDRC-6 or MDRC-7 .16G16.4.3 R-FUNC-MDR-03 Radio Configuration of Platform MDRC-1 to MDRC-7 .16G16.4.4 R-FUNC-MDR-04 Radio Programming for MDRC-1 to MDRC-7 .16G16.4.5 R-FUNC-MDR-05 Dynamic Execution for MDRC-4, and MDRC-7 17G16.4.6 R-FUNC-MDR-06 Independency on Memory Model
16、 for MDRC-1 to MDRC-7 17G16.4.7 R-FUNC-MDR-07 Code for MDRC-2 to MDRC-7 .17G16.4.8 R-FUNC-MDR-08 IR Format for MDRC-5 to MDRC-7 .17G16.4.9 R-FUNC-MDR-09 Timing Constraints for MDRC-1 to MDRC-7 .17G16.4.10 R-FUNC-MDR-10 Platform Independency for MDRC-5 to MDRC-7 17G16.4.11 R-FUNC-MDR-11 Radio Applica
17、tion for MDRC-5 to MDRC-7 17G1ETSI ETSI EN 302 969 V1.3.1 (2018-05) 4 6.4.12 R-FUNC-MDR-12 Function Granularity for MDRC-1 to MDRC-7 17G16.4.13 R-FUNC-MDR-13 Radio Virtual Machine for MDRC-2 to MDRC-7 .17G16.4.14 R-FUNC-MDR-14 RadioVirtual Machine Structure for MDRC-2 to MDRC-7 18G16.4.15 R-FUNC-MDR
18、-15 Selection of Radio Virtual Machine Protection Class for MDRC-2 to MDRC-7 18G16.5 Radio Frequency(RF) transceiver requirements .19G16.5.0 General 19G16.5.1 R-FUNC-RFT-01 RF Configuration for MDRC-1 to MDRC-7 .19G16.5.2 R-FUNC-RFT-02 Extendibility for multiple-antenna system for MDRC-1 to MDRC-7 .
19、19G16.5.3 R-FUNC-RFT-03 Capability of multiple frequency bands for MDRC-1 to MDRC-7 .20G16.5.4 R-FUNC-RFT-04 Reconfigurability of RF Transceiver for MDRC-1 to MDRC-7 .20G16.5.5 R-FUNC-RFT-05 Interoperability of radio resources for MDRC-2 to MDRC-7 .20G16.5.6 R-FUNC-RFT-06 Testability of radio equipm
20、ent for MDRC-1 to MDRC-7 .20G16.5.7 R-FUNC-RFT-07 Unified representation of control information for MDRC-1 to MDRC-7 .20G16.5.8 R-FUNC-RFT-08 Unified representation of data payload for MDRC-1 to MDRC-7 20G16.5.9 R-FUNC-RFT-09 Selection of RF Protection Class for MDRC-1 to MDRC-7 .20G16.6 Security re
21、quirements .21G16.6.0 General 21G16.6.1 R-FUNC-SEC-01 REConfPol-RAP-Security .21G16.6.2 R-FUNC-SEC-02 Administration-Security 21G16.6.3 R-FUNC-SEC-03 Secure Management 21G16.6.4 R-FUNC-SEC-04 Root of Trust .21G1History . 22G1ETSI ETSI EN 302 969 V1.3.1 (2018-05) 5 Intellectual Property Rights Essent
22、ial patents IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs);
23、 Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (https:/ipr.etsi.org/). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been car
24、ried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Trademarks The present document may include trademarks and/or tradenames whi
25、ch are asserted and/or registered by their owners. ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does not constitute an e
26、ndorsement by ETSI of products, services or organizations associated with those trademarks. Foreword This European Standard (EN) has been produced by ETSI Technical Committee Reconfigurable Radio Systems (RRS). National transposition dates Date of adoption of this EN: 17 May 2018 Date of latest anno
27、uncement of this EN (doa): 31 August 2018 Date of latest publication of new National Standard or endorsement of this EN (dop/e): 28 February 2019 Date of withdrawal of any conflicting National Standard (dow): 28 February 2019 Modal verbs terminology In the present document “shall“, “shall not“, “sho
28、uld“, “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. E
29、TSI ETSI EN 302 969 V1.3.1 (2018-05) 6 1 Scope The scope of the present document is to define the high level system requirements for reconfigurable Mobile Devices enabling the provision of Radio Applications. The work will be based on the Use Cases defined in ETSI TR 103 062 i.1 and ETSI TR 102 944
30、i.2. 2 References 2.1 Normative references References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (
31、including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found at https:/docbox.etsi.org/Reference/. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their lon
32、g term validity. The following referenced documents are necessary for the application of the present document. Not applicable. 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 reference
33、s, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following re
34、ferenced 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 Dev
35、ice“. i.2 ETSI TR 102 944: “Reconfigurable 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 (F
36、B): function needed for real-time implementation 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)
37、. ETSI ETSI EN 302 969 V1.3.1 (2018-05) 7 NOTE 2: Functional blocks are categorized 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 T
38、ransform (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) User defined functional blocks include those functional blocks that are dependent up
39、on a specific Radio Application. They are used 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
40、 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. network coding: technique in which transmitted data is encoded and decoded to improve n
41、etwork performance 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: Radio applications might have differ
42、ent forms of representation. They are represented as: G1 source codes including radio library calls of radio library native implementation and Radio HAL calls; G1 Intermediate Representations (IRs) including radio library calls of radio library native implementation and radio HAL calls; G1 Executabl
43、e codes for a particular radio 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 ato
44、mic and their source codes are 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 supporti
45、ng reactive and concurrent executions 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 devi
46、ce with radio communication capabilities 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 p
47、rovided by the reconfigurable Mobile 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-conflic
48、ting operation with other Radio 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.3.1 (2018-05) 8 3.2 Abbreviations For the purposes of the present documen
49、t, the following abbreviations apply: ASIC Application Specific Integrated Circuit BER Bit Error Rate CAT CATegory CR Cognitive Radio FB Functional Block FEC Forward Error Correction FFT Fast Fourier Transform HAL Hardware Abstraction Layer IR Intermediate Representation LTE Long Term Evolution MAC Media Access 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 Freq
