ETSI EN 303 146-4-2017 Reconfigurable Radio Systems (RRS) Mobile Device (MD) information models and protocols Part 4 Radio Programming Interface (RPI) (V1 1 2).pdf

《ETSI EN 303 146-4-2017 Reconfigurable Radio Systems (RRS) Mobile Device (MD) information models and protocols Part 4 Radio Programming Interface (RPI) (V1 1 2).pdf》由会员分享，可在线阅读，更多相关《ETSI EN 303 146-4-2017 Reconfigurable Radio Systems (RRS) Mobile Device (MD) information models and protocols Part 4 Radio Programming Interface (RPI) (V1 1 2).pdf（39页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI EN 303 146-4 V1.1.2 (2017-04) Reconfigurable Radio Systems (RRS); Mobile Device (MD) information models and protocols; Part 4: Radio Programming Interface (RPI) EUROPEAN STANDARD ETSI ETSI EN 303 146-4 V1.1.2 (2017-04) 2 Reference REN/RRS-0214 Keywords architecture, mobile, radio, SDR, softwar

2、e, system 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 enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice The present document can be downloade

3、d 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

4、 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

5、 revision or change of status. Information on the current status of this and other ETSI documents is available at https:/portal.etsi.org/TB/ETSIDeliverableStatus.aspx If you find errors in the present document, please send your comment to one of the following services: https:/portal.etsi.org/People/

6、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 writ

7、ten authorization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2017. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPT

8、M and LTE are Trade Marks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. oneM2M logo is protected for the benefit of its Members GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI EN 303 146-4 V1.1.2 (2017-04) 3 Con

9、tents Intellectual Property Rights 4g3Foreword . 4g3Modal verbs terminology 4g31 Scope 5g32 References 5g32.1 Normative references . 5g32.2 Informative references 5g33 Definitions and abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 7g34 Introduction 8g35 System Requirement Mapping . 10g36

10、Radio Virtual Machine specification 10g36.1 Concept of RVM 10g36.2 Elementary RVM (eRVM) . 11g36.3 RVM Hierarchy 15g36.4 Data types . 17g36.4.1 Types and Values 17g36.4.2 Run-Time Data . 17g36.5 Arithmetic. 17g36.6 Exceptions 17g36.7 Control, Synchronization and Execution 17g36.8 Operations with Mem

11、ory 18g36.9 RVM run-time environment . 18g37 Configcodes for RVM 19g37.0 Introduction 19g37.1 Configcodes generation 19g37.2 Binary format for Configcodes . 20g37.3 XML schema for Configcodes . 24g38 Radio Library . 30g38.0 Introduction 30g38.1 Reference Radio Library 30g38.2 Native Radio Library 31

12、g39 Loading, Linking and Initialization 32g310 Compiling for RVM (Front-End Compilation) 33g3Annex A (informative): Mapping between XML and Binary 34g3Annex B (informative): SFB Candidate . 35g3Annex C (informative): Replacement of selected components of an existing RAT 37g3Annex D (informative): In

13、troducing new SFBs . 38g3History 39g3ETSI ETSI EN 303 146-4 V1.1.2 (2017-04) 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 membe

14、rs and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (https:/ipr.etsi.

15、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

16、present document. Foreword This European Standard (EN) has been produced by ETSI Technical Committee Reconfigurable Radio Systems (RRS). The present document is part 4 of a multi-part deliverable. Full details of the entire series can be found in part 1 i.3. National transposition dates Date of adop

17、tion of this EN: 10 April 2017 Date of latest announcement of this EN (doa): 31 July 2017 Date of latest publication of new National Standard or endorsement of this EN (dop/e): 31 January 2018 Date of withdrawal of any conflicting National Standard (dow): 31 January 2018 Modal verbs terminology In t

18、he 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 deliv

19、erables except when used in direct citation. ETSI ETSI EN 303 146-4 V1.1.2 (2017-04) 5 1 Scope The scope of the present document is to define the Radio Programming Interface (RPI) for mobile device reconfiguration. The work is based on the Use Cases defined in ETSI TR 102 944 i.1, on the system requ

20、irements defined in ETSI EN 302 969 1 and on the radio reconfiguration related architecture for mobile devices defined in ETSI EN 303 095 i.2. Furthermore, the present document complements the mobile device information models and protocols related to the Multiradio Interface ETSI EN 303 146-1 i.3, t

21、o the Reconfigurable Radio Frequency Interface ETSI EN 303 146-2 i.4 and to the Unified Radio Application Interface ETSI EN 303 146-3 i.5. 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.

22、 For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found at https:/docbox.etsi.org

23、/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 Syste

24、ms (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 r

25、eferences, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are not necessary for the applicat

26、ion of the present document but they assist the user with regard to a particular subject area. i.1 ETSI TR 102 944: “Reconfigurable Radio Systems (RRS); Use Cases for Baseband Interfaces for Unified Radio Applications of Mobile Device“. i.2 ETSI EN 303 095 (V1.2.1): “Reconfigurable Radio Systems (RR

27、S); Radio Reconfiguration related Architecture for Mobile Devices“. i.3 ETSI EN 303 146-1: “Reconfigurable Radio Systems (RRS); Mobile Device Information Models and Protocols; Part 1: Multiradio Interface (MURI)“. i.4 ETSI EN 303 146-2: “Reconfigurable Radio Systems (RRS); Mobile Device (MD) informa

28、tion models and protocols; Part 2: Reconfigurable Radio Frequency Interface (RRFI)“. i.5 ETSI EN 303 146-3: “Reconfigurable Radio Systems (RRS); Mobile Device (MD) information models and protocols; Part 3: Unified Radio Application Interface (URAI)“. ETSI ETSI EN 303 146-4 V1.1.2 (2017-04) 6 3 Defin

29、itions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply: Abstract Processing Element (APE): abstracts computational resource that executes any computations downloaded from Radio Library NOTE: APE is connected with input and output

30、DOs. APE is reactive. Any computations are started if all input DOs are filled with real data. basic operations: operations either provided by the Radio Library and/or UDFB Set to eRVM or by the Radio Library and/or RVM/eRVM Configcodes to RVM NOTE: Each Basic Operation is mapped to a corresponding

31、APE in the case of eRVM or mapped to a corresponding APE or RVM/eRVM in the case of RVM. data flow chart: reactive data flow computational model consisting of data and operators where data are connected with operators NOTE: Operators abstract computations. They are triggered by full data. Results of

32、 operator computations are written in connected output data if they are empty. Data Object (DO): typeless token abstracting any type of data NOTE: DO provides a container for storing data. It can be empty if no data in the container or it can be full if there is data in the container. DO is allocate

33、d in the infinite and flat memory. Any RVM has access to this memory. One or a few APEs from RVM can be connected with DO. DO acknowledges connected APEs about its status whether it empty or full. dynamic operation: operation that is performed by allocating the computational resources during run-tim

34、e for each APE required executing the given operation NOTE 1: The resources are deallocated upon completion of the corresponding operation. NOTE 2: Dynamic operation is available only in the case of MDRC-7 defined in ETSI EN 302 969 1. In other words, dynamic operation is needed when RA requires the

35、 dynamic resource sharing. native radio library: library providing platform-specific description of each SFB that represents the target platform hardware port configuration: specification of the number of APEs inputs and outputs radio library authority: authority empowered to decide which components

36、 can be registered as new SFBs NOTE: Any suitable organization can take the role of a Radio Library Authority. The choice of the organization is beyond the scope of the present document. Radio Virtual Machine (RVM): abstract machine that supports reactive and concurrent executions NOTE: A RVM may be

37、 implemented as a controlled execution environment that allows the selection of a trade-off between flexibility of base band code development and required (re-)certification efforts. Radio Virtual Machine Runtime Environment (RVM RE): software that allows running Radio Applications that might be Con

38、figcodes or executable codes reference radio library: library providing normative definition of each SFB NOTE: There may be multiple such Reference Radio Libraries. For a given RA, a unique Reference Radio Library is used. ETSI ETSI EN 303 146-4 V1.1.2 (2017-04) 7 Software Intermediate Representatio

39、n (SWIR): RA representation as data flow chart NOTE: SWIR file contains information on all terminal objects, their parameters (cost, implement function, size, etc.) and connections (links, access type, source and destination). terminal operation: operation that will always be executed without any ot

40、her interruption NOTE 1: Furthermore, terminal operation cannot be decomposed into smaller operations. NOTE 2: “Terminal operations“ are equivalent to “atomic operations“, but additionally it indicates that a hierarchy is being used in which the “terminal operations“ are on the lowest level of hiera

41、rchy and they can be part of another operation. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: AOT Ahead-Of-Time APE Abstract Processing Element ASF Abstract Switch Fabric CC Configcodes Counter CSL Communication Services Layer CU Control UnitDO Data O

42、bject eRVM Elementary RVM eSFB Elementary SFB FB Functional BlockFBRI FB Reusability Index FFT Fast Fourier Transform HD Hardware DimensionHW Hardware ID Identification IFFT Inverse Fast Fourier Transform IR Intermediate RepresentationJIT Just-In-Time LCF Last Configuration Flag MD Mobile Device MUR

43、I MUltiRadio Interface NAF Next Address FlagNAPE Number of Abstract Processing Elements NCAO Next Configcode Address Offset NDO Number of Data Objects RA Radio Application RAP Radio Application Package RAT Radio Access Technology RCF Radio Control Framework RE Runtime Environment RF Radio Frequency

44、RLA Radio Library Authority ROS Radio Operating System RPI Radio Programming Interface RRFI Reconfigurable Radio Frequency Interface RVM Radio Virtual Machine RVM RE RVM Runtime Environment SD Software Dimension SFB Standard Functional Block SWIR SoftWare Intermediate Representation UDFB User Define

45、d Functional Block UML Unified Modeling LanguageURA Unified Radio Applications URAI Unified Radio Applications Interface XML eXtensible Markup Language ETSI ETSI EN 303 146-4 V1.1.2 (2017-04) 8 4 Introduction A reconfigurable MD is capable of running multiple radios simultaneously and of changing th

46、e set of radios by loading new Radio Application Package (RAP). All Radio Applications (RAs) are called Unified Radio Applications (URAs) when they exhibit a common behaviour from the reconfigurable MDs point of view i.2. In order to run multiple URAs, the reconfigurable MD will include Communicatio

47、n Services Layer (CSL), Radio Control Framework (RCF), Radio Platform and 4 sets of interfaces for their interconnection. Figure 4.1: Four sets of interfaces for Reconfigurable MD Figure 4.1 illustrates the Reconfigurable MD architecture with the 4 sets of interfaces, i.e.: MURI for interfacing CSL

48、and RCF i.2; RRFI for interfacing URA and RF Transceiver i.3; URAI for interfacing URA and RCF i.2; RPI for allowing an independent and uniform production of RAs. The present document defines RPI. ETSI ETSI EN 303 146-4 V1.1.2 (2017-04) 9 g90g258g282g349g381g18g381g373g393g437g410g286g396g1092g1092g

49、349g374g410g286g396g296g258g272g286g1093g1093g47g68g104g90g47g1092g1092g349g374g410g286g396g296g258g272g286g1093g1093g47g90g90g38g47g1092g1092g349g374g410g286g396g296g258g272g286g1093g1093g47g90g87g47g1092g1092g349g374g410g286g396g296g258g272g286g1093g1093g47g104g90g4g47Figure 4.2: UMLclass diagram for Radio Computer interfaces Figure 4.2 illustrates UMLclass diagram for Radio Computer interfaces. The reconfigurable MD may be seen as a Radio Computer where individual URAs are engineered as software entities i.2. The present doc