ETSI TS 102 968-2016 Reconfigurable Radio Systems (RRS) System requirements for Reconfigurable Radio Systems operating in IMT-Bands and GSM-Bands for intra-operator scenarios (V1 1.pdf

《ETSI TS 102 968-2016 Reconfigurable Radio Systems (RRS) System requirements for Reconfigurable Radio Systems operating in IMT-Bands and GSM-Bands for intra-operator scenarios (V1 1.pdf》由会员分享，可在线阅读，更多相关《ETSI TS 102 968-2016 Reconfigurable Radio Systems (RRS) System requirements for Reconfigurable Radio Systems operating in IMT-Bands and GSM-Bands for intra-operator scenarios (V1 1.pdf（11页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TS 102 968 V1.1.1 (2016-11) Reconfigurable Radio Systems (RRS); System requirements for Reconfigurable Radio Systems operating in IMT-Bands and GSM-Bands for intra-operator scenarios TECHNICAL SPECIFICATION ETSI ETSI TS 102 968 V1.1.1 (2016-11)2 Reference DTS/RRS-01012 Keywords CRS, GSM, IMT,

2、radio, requirements, SDR, 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 do

3、cument can be downloaded 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

4、case of any existing or 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 doc

5、ument may be subject to 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:/

6、portal.etsi.org/People/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 mo

7、dified without the written authorization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2016. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefi

8、t of its Members. 3GPPTM and LTE are Trade Marks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 102 968 V1.1.1 (2016-11)3 Contents Intellectual Property Rights 4

9、g3Foreword . 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 . 6g34 Requirement Organization and Format 6g34.1 Requirement Organization 6g34.2 Requirement Fo

10、rmat . 7g35 Working assumptions . 7g36 Functional Requirements 8g36.1 Radio and Hardware Processing Resources Reconfiguration Requirements 8 g36.1.1 R-FUNC-RHR-01: Reconfiguration for each RAT 8g36.1.2 R-FUNC-RHR-02: Reconfiguration between RATs 8g36.2 Requirements for functions supporting reconfigu

11、ration . 8g36.2.1 R-FUNC-REC-01: Gathering and processing function 8g36.2.2 R-FUNC-REC-02: Support of trigger events for reconfiguration. 8g36.2.3 R-FUNC-REC-03: Support for reconfiguration function . 9g36.2.4 R-FUNC-REC-04: Support for execution function 9g36.2.5 R-FUNC-REC-05: Support of learning

12、function 9g36.2.6 R-FUNC-REC-06: Support of information provisioning function . 9g36.3 MDs mobility and connectivity management requirements . 9g36.3.1 R-FUNC-MOB-01: Mobility management of the MDs 9g36.3.2 R-FUNC-MOB-02: Connectivity management of the MDs . 9g3History 11g3ETSI ETSI TS 102 968 V1.1.

13、1 (2016-11)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 000 314: “Intellec

14、tual 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.org/). Pursuant to the ETSI IPR Policy, no investigation, includin

15、g 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 Technical Specification (TS) has b

16、een produced by ETSI Technical Committee Reconfigurable Radio Systems (RRS) Modal verbs terminology 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

17、 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 TS 102 968 V1.1.1 (2016-11)5 1 Scope The scope of the present document is to define the system requirements for Recon

18、figurable Radio Systems operating in GSM and IMT bands for intra-operator scenarios. These requirements are derived from the use cases described in ETSI TR 103 063 i.1. The present document considers the system requirements only for intra-operator scenarios for which the spectrum resources are assig

19、ned to and managed by a single operator. Requirement categories are: Requirements for Radio and Hardware Processing Resources Reconfiguration. Requirements for functions supporting reconfiguration. Requirements for mobile device mobility and connectivity management. 2 References 2.1 Normative refere

20、nces 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 (including any amendments) applies. Ref

21、erenced 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 long term validity. The following referen

22、ced 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 references, only the cited version applies. For

23、 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 referenced documents are not necessary f

24、or the application of the present document but they assist the user with regard to a particular subject area. i.1 ETSI TR 103 063: “Reconfigurable Radio Systems (RRS); Use Cases for Reconfigurable Radio Systems operating in IMT bands and GSM bands for intra-operator scenarios“. ETSI ETSI TS 102 968

25、V1.1.1 (2016-11)6 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply: cognitive radio system: radio system employing technology that allows the system to obtain knowledge of its operational and geographical environment,

26、 established policies and its internal state; to dynamically and autonomously adjust its operational parameters and protocols according to its obtained knowledge in order to achieve predefined objectives; and to learn from the results obtained Reconfigurable Radio Systems (RRS): generic term for rad

27、io systems encompassing Software Defined and/or Cognitive Radio Systems software defined radio: radio transmitter and/or receiver employing a technology that allows the RF operating parameters including, but not limited to, frequency range, modulation type, or output power to be set or altered by so

28、ftware, excluding changes to operating parameters which occur during the normal pre-installed and predetermined operation of a radio according to a system specification or standard use case: description of a system from a users perspective NOTE 1: Use cases treat a system as a black box, and the int

29、eractions with the system, including system responses, are perceived as from outside the system. Use cases typically avoid technical jargon, preferring instead the language of the end user or domain expert. NOTE 2: Use cases should not be confused with the features/requirements of the system under c

30、onsideration. A use case may be related to one or more features/requirements, a feature/requirement may be related to one or more use cases. NOTE 3: A brief use case consists of a few sentences summarizing the use case. 3.2 Abbreviations For the purposes of the present document, the following abbrev

31、iations apply: DSP Digital Signal Processor FPGA Field Programmable Gate Array HPR Hardware Processing Resource IMT International Mobile Telecommunications MD Mobile Device QoS Quality of Service RAT Radio Access Technology RBS Reconfigurable Base Station RF Radio Frequency 4 Requirement Organizatio

32、n and Format 4.1 Requirement Organization The present document is structured such that a level 2 section is dedicated to the requirements associated with a single category. The overall structure is shown in figure 4.1. ETSI ETSI TS 102 968 V1.1.1 (2016-11)7 Figure 4.1: Overall requirements structure

33、 4.2 Requirement Format A letter code system is defined which makes a unique identification of each requirement R-. It should be constructed as follows: R-: Standard requirement prefix. -: Code Category FUNC Functional aspects PERF Performance aspects : Requirement group identifier. A letter code wi

34、ll 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-FUNC-QOS-01. 5 Working assumptions ETSI TR 103 063 i.1 describes how Reconfigurable Radio Systems can be exploited in IMT bands

35、and GSM bands (i.e. licensed spectrums allocated to IMT and GSM systems) to increase the efficiency of the radio resource management in the intra-operator scenarios for which the spectrum resources are assigned to and managed by a single operator. The list of Use Cases described in ETSI TR 103 063 i

36、.1 is reported hereafter: Radio Resource optimization. Spectrum refarming. Upgrading a pre-existing RAT and deploying a new RAT to a pre-existing network. Addition of multiple standards modes. LTE pico/femto cell reconfiguration. Functional requirements category (FUNC)g90g286g395g437g349g396g286g373

37、g286g374g410g400g3g296g381g396g3g90g258g282g349g381g3g258g374g282g3g44g258g396g282g449g258g396g286g3g87g396g381g272g286g400g400g349g374g336g3g90g286g400g381g437g396g272g286g400g3g90g286g272g381g374g296g349g336g437g396g258g410g349g381g374g90g286g395g437g349g396g286g373g286g374g410g400g3g296g381g396g3

38、g296g437g374g272g410g349g381g374g400g3g400g437g393g393g381g396g410g349g374g336g3g396g286g272g381g374g296g349g336g437g396g258g410g349g381g374g90g286g395g437g349g396g286g373g286g374g410g400g3g296g381g396g3g373g381g271g349g367g286g3g282g286g448g349g272g286g3g373g381g271g349g367g349g410g455g3g258g374g28

39、2g3g272g381g374g374g286g272g410g349g448g349g410g455g3g373g258g374g258g336g286g373g286g374g410ETSI ETSI TS 102 968 V1.1.1 (2016-11)8 Cognition Enabler. It has to be noted that each Use Case does not necessarily require fulfilling all the system requirements but only the ones related to the specific S

40、cenarios. Furthermore the requirements related to MD has to be intended as a means to fully benefit from the depicted RRS operations in which even non-reconfigurable multi-mode MDs can be fully supported. 6 Functional Requirements 6.1 Radio and Hardware Processing Resources Reconfiguration Requireme

41、nts 6.1.1 R-FUNC-RHR-01: Reconfiguration for each RAT The system shall support the reconfiguration of both the Hardware Processing Resources (HPRs) and the Radio Resources (RRs) for each supported RAT. Explanation: The system should be able to perform resource reconfiguration of both the hardware pr

42、ocessing resources and the radio resources for each supported RAT. The radio resources assigned to each supported RAT can be dynamically modified, which includes bandwidth, frequencies, power levels, spectrum masks, etc. Meanwhile, the percentage of hardware processing resources devoted to each supp

43、orted RAT should be dynamically modified. For example, sufficient HPR should be configured to a RAT when a new channel is assigned to it. NOTE: HPR indicates the hardware of the reconfigurable node (e.g. constituted by DSPs and FPGAs) that is used to run the software that implements the specific RAT

44、s functionalities (e.g. Base Band operations). The RF part is supposed to be separate and managed by specific modules (e.g. Radio Units (RUs) able to support more RATs at the same time with sufficient power capacity in order to respect the RF requirements of any single RAT i.1. 6.1.2 R-FUNC-RHR-02:

45、Reconfiguration between RATs The system shall support reconfiguration of both HPRs and RRs between different RATs. Explanation: The system can re-configure multiple RATs with flexibility in terms of the percentage of HPRs and RRs between different RATs according to the status of the network. 6.2 Req

46、uirements for functions supporting reconfiguration 6.2.1 R-FUNC-REC-01: Gathering and processing function The system shall support a gathering and processing function to gather and process certain radio related metrics and parameters. Explanation: After having gathered radio related metrics and para

47、meters, the gathering and processing function may process them to make decisions on reconfiguration in order to optimize radio performance. The identification of the radio related metrics and parameters which can be used for reconfiguration purposes may vary according the specific use case. These ar

48、e expected to include traffic variations, channel bandwidth, interference, transmit power, QoS, etc. 6.2.2 R-FUNC-REC-02: Support of trigger events for reconfiguration The system shall support trigger events for reconfiguration. Explanation: Trigger events are described by certain parameters (e.g. t

49、hresholds, hysteresis, etc.) in order to define the condition under which an event is happening. When one or more events occur, the system starts to evaluate the need for a possible reconfiguration. ETSI ETSI TS 102 968 V1.1.1 (2016-11)9 6.2.3 R-FUNC-REC-03: Support for reconfiguration function The system shall support a reconfiguration function to make decisions for radio resource reconfiguration and inform RBSs to perform the reconfiguration e.g. triggered by events in clause 6.2.2. Explanation: The reconfiguration function shall make