ETSI TS 102 969-2012 Reconfigurable Radio Systems (RRS) Radio Reconfiguration related Requirements for Mobile Devices《可重组无线电系统(RRS) 移动设备的无线电重组相关要求(版本1 1 1)》.pdf

《ETSI TS 102 969-2012 Reconfigurable Radio Systems (RRS) Radio Reconfiguration related Requirements for Mobile Devices《可重组无线电系统(RRS) 移动设备的无线电重组相关要求(版本1 1 1)》.pdf》由会员分享，可在线阅读，更多相关《ETSI TS 102 969-2012 Reconfigurable Radio Systems (RRS) Radio Reconfiguration related Requirements for Mobile Devices《可重组无线电系统(RRS) 移动设备的无线电重组相关要求(版本1 1 1)》.pdf（20页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TS 102 969 V1.1.1 (2012-03) Reconfigurable Radio Systems (RRS); Radio Reconfiguration related Requirements for Mobile Devices Technical Specification ETSI ETSI TS 102 969 V1.1.1 (2012-03)2Reference DTS/RRS-02006 Keywords CRS, mobile, SDR ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Ced

2、ex - 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 Individual copies of the present document can be downloaded from: http:/www.etsi.org The present docume

3、nt may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the PD

4、F 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/statu

5、s.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 except as authorized by written permission. The copyright and the foregoing restriction extend

6、 to reproduction in all media. European Telecommunications Standards Institute 2012. 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 a

7、nd of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 102 969 V1.1.1 (2012-03)3Contents Intellectual Property Rights 5g3Foreword . 5g31 Scope 6g32 References 6g32.1 Normative references . 6g32.2 Informative references 6

8、g33 Definitions and abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 7g34 Requirement Organization and Methodology 7g34.1 Requirement Organization 7g34.2 Requirement Format . 8g34.3 Requirement Formulation . 8g35 Working assumptions . 9g35.1 Assumptions . 9g35.1.1 Mobile Device Reconfigurat

9、ion Classes . 9g36 Functional Requirements 12g36.1 Requirements on RAT Link Support and Management . 12g36.1.1 R-FUNC-RAT01 Function for MDRC-1 to MDRC-7 12g36.1.2 R-FUNC-RAT02 Function for MDRC-1 to MDRC-7 12g36.1.3 R-FUNC-RAT03 Function for MDRC-1 to MDRC-7 12g36.1.4 R-FUNC-RAT04 Function for MDRC

10、-1 to MDRC-7 12g36.1.5 R-FUNC-RAT05 Function for MDRC-1 to MDRC-7 12g36.1.6 R-FUNC-RAT06 Function for MDRC-1 to MDRC-7 12g36.1.7 R-FUNC-RAT07 Function for MDRC-1 to MDRC-7 12g36.2 Base Band Interface Requirements. 12g36.2.1 R-FUNC-BBI-01 Composition for MDRC-1 to MDRC-7 . 12g36.2.2 R-FUNC-BBI-02 Dat

11、a for MDRC-1 to MDRC-7 13g36.2.3 R-FUNC-BBI-03 Context Information for MDRC-1 to MDRC-7 . 13g36.2.4 R-FUNC-BBI-04 Interface Type for MDRC-2 to MDRC-7 13g36.2.5 R-FUNC-BBI-05 Pipelining for MDRC-2 to MDRC-7 . 13g36.2.6 R-FUNC-BBI-06 Transferring of Context Information for MDRC-1 to MDRC-7 13g36.2.7 R

12、-FUNC-BBI-07 Support for Multi-antenna Technologies for MDRC-1 to MDRC-7 13g36.2.8 R-FUNC-BBI-08 Access to Device-internal Radio Context Information for MDRC-1 to MDRC-7 . 13g36.3 Base Band Function Block requirements . 14g36.3.1 R-FUNC-FB-01 Implementation for MDRC-2 to MDRC-7 14g36.3.2 R-FUNC-FB-0

13、2 Function Block for MDRC-2 to MDRC-7 . 14g36.3.3 R-FUNC-FB-03 Normative Library for MDRC-2 to MDRC-7 14g36.3.4 R-FUNC-FB-04 Execution for MDRC-2 to MDRC-7 . 15g36.3.5 R-FUNC-FB-05 Side Effects for MDRC-2 to MDRC-7 15g36.3.6 R-FUNC-FB-06 Shared Data for MDRC-2 to MDRC-7 15g36.3.7 R-FUNC-FB-07 Concur

14、rency for MDRC-2 to MDRC-7 . 15g36.3.8 R-FUNC-FB-08 User Defined Function Block for MDRC-2 to MDRC-7 . 15g36.3.9 R-FUNC-FB-09 Extendability for MDRC-2 to MDRC-7 15g36.4 Mobile Device Reconfiguration Requirements 15g36.4.1 R-FUNC-MDR-01 Platform-specific Executable Code for MDRC-2, MDRC-3 or MDRC-4 .

15、 15g36.4.2 R-FUNC-MDR-02 Platform-independent Source Code or IR for MDRC-5, MDRC-6 or MDRC-7 . 16g36.4.3 R-FUNC-MDR-03 Radio Configuration of Platform MDRC-1 to MDRC-7 . 18g36.4.4 R-FUNC-MDR-04 Radio Programming Interface for MDRC-1 to MDRC-7 18g36.4.5 R-FUNC-MDR-05 Concurrent Execution for MDRC-1 t

16、o MDRC-7 18g36.4.6 R-FUNC-MDR-06 Dynamic Execution for MDRC-3, MDRC-4, MDRC-6 and MDRC-7 . 18g36.4.7 R-FUNC-MDR-07 Formal Verification for MDRC-1 to MDRC-7 19g36.4.8 R-FUNC-MDR-08 Independency on Memory Model for MDRC-1 to MDRC-7 19g3ETSI ETSI TS 102 969 V1.1.1 (2012-03)46.4.9 R-FUNC-MDR-09 IR Forma

17、t for MDRC-5 to MDRC-7 . 19g36.4.10 R-FUNC-MDR-10 Timing Constraints for MDRC-1 to MDRC-7 19g36.4.11 R-FUNC-MDR-11 Intermediate Representation for MDRC-5 to MDRC-7 19g36.4.12 R-FUNC-MDR-12 Unified Radio Application for MDRC-1 to MDRC-7 . 19g36.4.13 R-FUNC-MDR-13 Function Granularity for MDRC-1 to MD

18、RC-7 19g37 Conclusions 19g3History 20g3ETSI ETSI TS 102 969 V1.1.1 (2012-03)5Intellectual 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

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

20、). 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 pres

21、ent document. Foreword This Technical Specification (TS) has been produced by ETSI Technical Committee Reconfigurable Radio Systems (RRS). ETSI ETSI TS 102 969 V1.1.1 (2012-03)61 Scope The scope of the present document is to define the system requirements for reconfiguring the radios in mobile devic

22、es. The work will be based on the Use Cases defined in TR 103 062 i.1, TR 102 839 i.2 and TR 102 944 i.3. 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.

23、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 clau

24、se were valid 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 neces

25、sary 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 839: “Reco

26、nfigurable Radio Systems (RRS); Multiradio Interface for Software Defined Radio (SDR) Mobile Device Architecture and Services“. i.3 ETSI TR 102 944: “Reconfigurable Radio Systems (RRS); Use Cases for Baseband Interfaces for Unified Radio Applications of Mobile Device“. 3 Definitions and abbreviation

27、s 3.1 Definitions For the purposes of the present document, the following terms and definitions apply: resource: resource that radio application needs in active state, which includes processor and accelerator loads, memory usage, interconnect bandwidth occupation, Radio Frequency (RF) circuitry, etc

28、. NOTE: Resources are provided 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 orde

29、r to ensure non-conflicting operation with other radio applications. Resources may or may not be shared in the MD. ETSI ETSI TS 102 969 V1.1.1 (2012-03)73.2 Abbreviations For the purposes of the present document, the following abbreviations apply: ASIC Application Specific Integrated Circuit BBI Bas

30、eBand Interface BER Bit Error Rate BPA Baseband Parameter Aggregation CAT CategoryCII Context Information Interface CR Cognitive Radio DoA Direction of ArrivalFEC Forward Error Correction FFT Fast Fourier Transform IP Internet Protocol IR Intermediate Representation MAC Media Access Control MD Mobil

31、e Device MDRC Mobile Device Reconfiguration Classes MIMO Multi-Input Multi-Output MU-MIMO Multi User-MIMO PER Packet Error Rate PMI Precoding Matrix Indicator RAI Radio Application Interface RAT Radio Access Technology RF Radio Frequency RI Rank Indicator RPI Radio Programming Interface RRS Reconfig

32、urable Radio Systems RSSI Received Signal Strength Indication Rx Recieve SDR Software Defined Radio SINR Signal to Interference-plus-Noise Ratio SU-MIMO Single User-MIMO Tx Transmit URA Unified Radio Application 4 Requirement Organization and Methodology This clause is containing the description of

33、how the requirements are organised and the format of the requirement. 4.1 Requirement Organization The present document is structured such that a level 1 section is dedicated to the requirements associated with a single category. The requirements should be partitioned into groups of related category

34、 to assist understanding. The overall structure is shown in figure 4.1.1. ETSI ETSI TS 102 969 V1.1.1 (2012-03)8Figure 4.1.1: Overall requirememts structure 4.2 Requirement Format A letter code system is defined which makes a unique identification of each requirement R-. It should be constructed as

35、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. : Requirement identifier within requirement group; range 01 = 99. EXAMPLE: R-F

36、UNC-QOS-01 4.3 Requirement Formulation A requirement formulation is defined which makes a unique way to formulate it. It will be built as follows: Title: Description: The description of the requirement shall be formulated using one of the following terms. As described into the ETSI Terms resource al

37、location mechanism within separate application is not specified. ETSI ETSI TS 102 969 V1.1.1 (2012-03)103) MDRC-2: Radio applications use pre-defined static resources MDRC-2 implements multiple radio applications but no dynamic resource management is available. The radio applications for MDRC-2 come

38、 from a single radio application package which is normally provided by a MD vendor or SDR chipset manufacturer. In this scenario, we assume that software radio components in the radio application package are provided in platform-specific executable code. The rule for resource allocation for multiple

39、 applicationsg3A1, A2, , ANg3can be formulated as follows: Aig3450 Ri, ig35471, ., N, where Ridenotes resource allocated for application Ai, if i j so that Ri Rj then such applications cannot be run concurrently, all other combinations are allowed; resource allocation mechanism within separate appli

40、cation is not specified. 4) MDRC-3: Radio applications have static resource requirements For MDRC-3, a resource budget is defined for each radio application. This budget contains a static resource measure that represents the worst-case resource usage of the application, generated at radio applicatio

41、n compile-time. If an application is being started, the resource manager installed in MD of MDRC-3 checks its resource budget and the sum of all resource budgets of already running applications, and admits the new application only if the resources can still be guaranteed for all running applications

42、. In this scenario, we assume that software radio components in the radio application package are provided in platform-specific executable code. The rule for resource allocation for multiple applicationsg3A1, A2, , ANg3can be formulated as follows: Ai R(Ai), where R denotes total resources to be sha

43、red and R(Ai) denotes a part of R allocated for Ai; if for i1, i2, ., iM g35471, ., N, M N, R(Ai1) R(Ai2) . R(AiM) R then applications Ai1, Ai2, , AiMcan be run concurrently; resource allocation mechanism within separate application is not specified. 5) MDRC-4: Radio applications have dynamic resour

44、ce requirements This scenario assumes a similar resource manager in MD as for MDRC-3, but in addition the radio applications have now varying resource demands based on their current type of activity. Applications have separate operational states for different types of activity, and a resource budget

45、 is assigned to each operational state. In this scenario, we assume that software radio components in the radio application package are provided in platform-specific executable code. Resource management for MDRC-4 can be formulated as follows. Multiple applicationsg3A1, A2, , ANg3can be run and each

46、 applicationg3Aig3is divided into tasks t1(Ai), t2(Ai), ., tk(Ai). Resource allocation is provided by the resource manager in MD for each task tj(Ai) R(tj(Ai). The rule for task running is exactly the same as for MDRC-3 except that each application should be replaced by corresponding task. Therefore

47、, if for i1, i2, ., iM g35471, ., N, M N, R(tj1(Ai1) R(tj2(Ai2) . R(tjL(AiM) R then tasks tj1(Ai1), tj2(Ai2), ., tjL(AiM) can be run concurrently; resource allocation mechanism within separate task is not specified. 6) MDRC-5: Radio applications use pre-defined static resources, on-device compilatio

48、n of Software Radio Components This class corresponds to MDRC-2 with the difference that all or part of the software radio components are provided in the radio application package as platform-independent source code or platform-independent Intermediate Representation (IR), which is compiled on the M

49、D itself. It particularly means that MD should include a proper compiler in order to convert the source code or IR of the software radio components into an executable code that runs on a given modem chip of MD. It is assumed that the methods of radio programming and the tools to support this category have become sufficiently standardized so that third-party vendors may create radio applications and activate them to different platforms with relative ease. Formal description for resource manage