ETSI TR 103 585-2018 Reconfigurable Radio Systems (RRS) Radio Equipment Reconfiguration Use Cases (V1 1 1).pdf

1、 ETSI TR 103 585 V1.1.1 (2018-02) Reconfigurable Radio Systems (RRS); Radio Equipment Reconfiguration Use Cases TECHNICAL REPORT ETSI ETSI TR 103 585 V1.1.1 (2018-02) 2 Reference DTR/RRS-0216 Keywords software, use case ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4

2、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 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 prevaili

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

5、cuments 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 No part may be reproduced or utilized in

6、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 foregoing restriction extend to reproduct

7、ion 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 Organizational Partners. oneM2M logo is pr

8、otected for the benefit of its Members. GSMand the GSM logo are trademarks registered and owned by the GSM Association. ETSI ETSI TR 103 585 V1.1.1 (2018-02) 3 Contents Intellectual Property Rights 5g3Foreword . 5g3Modal verbs terminology 5g3Introduction 5g31 Scope 6g32 References 6g32.1 Normative r

9、eferences . 6g32.2 Informative references 6g33 Abbreviations . 6g34 Radio Equipment Reconfiguration Use Cases . 7g34.1 Overview 7g34.2 Use Case “Smartphone Radio Reconfiguration“ 7g34.2.0 General 7g34.2.1 Scenario “Optimize the operation of Smartphone“ . 7g34.2.2 Stakeholders 8g34.2.3 Information Fl

10、ow 8g34.2.3.1 Information Flows for Scenario “Optimize the operation of Smartphone“ . 8g34.3 Use Case “Connected Vehicle Radio Reconfiguration“ . 9g34.3.0 General 9g34.3.1 Scenario “Upgrade of Feature-Set“ . 9g34.3.2 Scenario “Addressing Vulnerabilities“ . 9g34.3.3 Stakeholders 9g34.3.4 Information

11、Flow 10g34.3.4.1 Information Flows for Scenario “Upgrade of feature-Set“ and “Addressing Vulnerabilities“ 10g34.4 Use Case “Network Radio Reconfiguration“ . 11g34.4.0 General 11g34.4.1 Scenario “Single-Entity Network Radio Reconfiguration“ . 11g34.4.2 Scenario “Multiple-Entities Network Radio Reconf

12、iguration“ . 11g34.4.3 Stakeholders 11g34.4.4 Information Flow 12g34.4.4.1 Information Flows for Scenario “Single-Entity Network Radio Reconfiguration“ . 12g34.4.4.2 Information Flows for Scenario “Multiple-Entities Network Radio Reconfiguration“ . 13g34.5 Use Case “IoT Device Reconfiguration“ 14g34

13、.5.0 General 14g34.5.1 Scenario “Optimization by pre-provisioning of a RA at manufacture time“ 14g34.5.2 Scenario “Optimization by downloading of a RA from Radio Apps Store“ . 14g34.5.3 Stakeholders 14g34.5.4 Information Flow 15g34.5.4.1 Information Flows for Scenario “Optimization by pre-provisioni

14、ng of a RA at manufacture time“ 15g34.5.4.2 Information Flows for Scenario “Optimization by downloading of a RA from Radio Apps Store“ . 16g34.6 Use Case “Radio Reconfiguration through an external Component“ . 16g34.6.0 General 16g34.6.1 Scenario “Standalone external components“ 17g34.6.2 Scenario “

15、Host dependent external component“ . 17g34.6.3 Stakeholders 17g34.6.4 Information Flows 18g34.6.4.1 Information Flows for Scenario “Standalone external components“. 18g34.6.4.2 Information Flows for Scenario “Host dependent external component“ . 22g34.7 Use Case “Bug-fix and security updates“ . 23g3

16、4.7.1 Introduction. 23g34.7.2 Scenario “Automated Updates“ 23g34.7.3 Scenario “Manual Updates“ 23g34.7.4 Stakeholders 23g34.7.5 Information Flows 24g3ETSI ETSI TR 103 585 V1.1.1 (2018-02) 4 4.7.5.1 Information Flows for Scenario “Automated Updates“ 24g34.7.5.2 Information Flows for Scenario “Manual

17、Updates“ 25g3Annex A: Change History . 26g3History 27g3ETSI ETSI TR 103 585 V1.1.1 (2018-02) 5 Intellectual Property Rights Essential patents IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The information pertaining to these essential IPRs, if any,

18、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 to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on t

19、he ETSI Web server (https:/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 existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may

20、be, or may become, essential to the present document. Trademarks The present document may include trademarks and/or tradenames which 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 righ

21、t to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks. Foreword This Technical Report (TR) has been produced by ETSI Technical Commit

22、tee Reconfigurable Radio Systems (RRS). Modal verbs terminology In the present document “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

23、“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. Introduction The present document provides use cases for radio equipment reconfiguration through software. It extends the use cases defined in i.7 for mobile device reconfiguration to the more generic framewor

24、k of radio equipment reconfiguration. ETSI ETSI TR 103 585 V1.1.1 (2018-02) 6 1 Scope The scope of the present document is to define use cases for radio equipment reconfiguration through software. 2 References 2.1 Normative references Normative references are not applicable in the present document.

25、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 references, the latest version of the referenced document (including any am

26、endments) 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 application of the present document but they assist the user with regard to a part

27、icular subject area. i.1 ETSI EN 302 969 (V1.2.1): “Reconfigurable Radio Systems (RRS); Radio Reconfiguration related Requirements for Mobile Devices“. i.2 ETSI EN 303 095 (V1.2.1): “Reconfigurable Radio Systems (RRS); Radio Reconfiguration related Architecture for Mobile Devices“. i.3 ETSI EN 303 1

28、46-1 (V1.2.1): “Reconfigurable Radio Systems (RRS); Mobile Device Information Models and Protocols; Part 1: Multiradio Interface (MURI)“. i.4 ETSI EN 303 146-2 (V1.2.1): “Reconfigurable Radio Systems (RRS); Mobile Device (MD) information models and protocols; Part 2: Reconfigurable Radio Frequency I

29、nterface (RRFI)“. i.5 ETSI EN 303 146-3 (V1.2.1): “Reconfigurable Radio Systems (RRS); Mobile Device (MD) information models and protocols; Part 3: Unified Radio Application Interface (URAI)“. i.6 ETSI EN 303 146-4 (V1.2.1): “Reconfigurable Radio Systems (RRS); Mobile Device (MD) information models

30、and protocols; Part 4: Radio Programming Interface (RPI)“. i.7 ETSI TR 103 062 (V1.1.1): “Reconfigurable Radio Systems (RRS); Use Cases and Scenarios for Software Defined Radio (SDR) Reference Architecture for Mobile Device“. 3 Abbreviations For the purposes of the present document, the following ab

31、breviations apply: FFT Fast Fourier Transform FPGA Field Programmable Gate Array IoT Internet of Things LLC Logic Link Control MURI Multi Radio InterfaceNR New Radio RA Radio Application RadioApps Radio Application Store RAP Radio Application Package RAT Radio Access Technology ETSI ETSI TR 103 585

32、V1.1.1 (2018-02) 7 RLC Radio Link Control RRS Reconfigurable Radio Systems SDR Software Defined Radio SW SoftWare USB Universal Serial Bus V2X Vehicle to Everything 4 Radio Equipment Reconfiguration Use Cases 4.1 Overview This clause provides some use cases of the SW reconfiguration and related equi

33、pment-specific application scenarios. Use cases considered in this clause are as follows. Use Case “Smartphone Radio Reconfiguration“ in clause 4.2. Use Case “Connected Vehicle Radio Reconfiguration“ in clause 4.3. Use Case “Network Radio Reconfiguration“ in clause 4.4. Use Case “IoT Device Reconfig

34、uration“ in clause 4.5. Use Case “Radio Reconfiguration through an external Component“ in clause 4.6. Use Case “Bug-fix and security updates“ in clause 4.7. NOTE: Use Cases given in clauses 4.2, 4.3, 4.4, 4.5 and 4.6 are design Use Cases; the Use Case given in clause 4.7 is a Use Case for achieving

35、a defined purpose. 4.2 Use Case “Smartphone Radio Reconfiguration“ 4.2.0 General The average lifetime of smartphones is substantially shorter ( 2 years) compared to other radio equipment ( 2 years) such as vehicles, base stations, etc. Since smartphones are also generic computing platforms, they are

36、 subject to gradual obsolescence - in terms of computing power - when new use cases and software-based solutions become available. Therefore, radio reconfiguration use cases corresponding to the evolution of communication standards do not seem to be a major factor in the case of smartphones. Rather,

37、 the scenario of optimizing the operation of smartphones in accordance to the functional blocks in a given Radio Application code that might be downloaded from RadioApp Stores will be the main factor determining the use case of the smartphone radio reconfiguration. In this context however, minor upd

38、ates to Radio Applications remain critical in order to provide technical corrections and address security vulnerabilities. RadioApps, provided as the ETSI SW Reconfiguration solutions, extend or modify existing radio features and define solutions for technical, certification and security needs. 4.2.

39、1 Scenario “Optimize the operation of Smartphone“ In this scenario, the operation of smartphone is optimized using an RA code corresponding to the required functional block(s) of desired communication protocol(s) downloaded from RadioApp Store upon users request. For example, a LTE smartphone user c

40、ould update his/her RA code of LTE protocol with a new FFT functional block which, for instance, utilizes less computational resources compared to the FFT functional block in the given RA code in order to save the computational complexity. The optimization of smartphone operation is achieved in gene

41、ral by replacing some functional blocks with new ones or the entire RA code with a new one. ETSI ETSI TR 103 585 V1.1.1 (2018-02) 8 4.2.2 Stakeholders End users: the users of the smartphones accessing internet and other similar mobile data services. Network operators: - operate and maintain the requ

42、ired infrastructure; - might provide information on the availability of new RAP(s) to the end users; might provide the new RAP(s) to the end users. Software Manufacturer: may provide new RAP(s) for optimizing the operation of smartphone. National Regulatory Authority: provides framework for certific

43、ation of new RAP(s) provided by software manufacturers. 4.2.3 Information Flow 4.2.3.1 Information Flows for Scenario “Optimize the operation of Smartphone“ g94g373g258g396g410g393g346g381g374g286g4g272g272g286g400g400g69g286g410g449g381g396g364g94g381g296g410g449g258g396g286g3g68g258g374g437g296g25

44、8g272g410g437g396g286g396Provide new RAP(s)g39g286g374g286g396g258g410g286g3g374g286g449g3g90g4g87g894g400g895Request download of new RAP(s)Provide new RAP(s)g90g286g272g381g374g296g349g336g437g396g286g3g449g349g410g346g374g286g449g3g90g4g87g894g400g895ACK/NACK for new RAP(s)g104g393g367g381g258g282

45、g3g374g286g449g3g90g4g87g894g400g895g3g381g374g3g90g258g282g349g381g3g4g393g393g400g3g94g410g381g396g286g90g286g336g437g367g258g410g349g381g374g4g282g373g349g374g349g400g410g396g258g410g349g381g374Request network access with new RAP(s)Grant network accessg18g381g373g393g367g286g410g349g381g374g3g381

46、g296g3g374g286g410g449g381g396g364g3g258g272g272g286g400g400g3g449g349g410g346g3g374g286g449g3g90g4g87g894g400g895g90g286g395g437g349g396g286g282g3g349g374g296g381g396g373g258g410g349g381g374g3g349g400g3g396g286g272g286g349g448g286g282g853g3g449g346g349g272g346g3g349g400g3g374g286g272g286g400g400g25

47、8g396g455g3g296g381g396g3g410g346g286g3g396g286g336g437g367g258g410g381g396g455g3g296g396g258g373g286g449g381g396g364Figure 4.2.3.1-1: Information Flow for Scenario “Optimize the operation of Smartphone“ ETSI ETSI TR 103 585 V1.1.1 (2018-02) 9 Note that the RAP(s) shown in figure 4.2.3.1-1 is for fu

48、nctional block(s) of desired communication protocol(s) or entire RAT. NOTE: The “required information“ for the Regulation Administration is issued by a suitable source. In this Use Case, no assumption on the responsible party for regulatory compliance is made. 4.3 Use Case “Connected Vehicle Radio R

49、econfiguration“ 4.3.0 General Since the lifetime of automotive communication components is substantially longer ( 10 years) compared to smartphones ( 2 years), it seems to be necessary for the communication platform in a vehicle to cope with the new communication standard through the SW reconfiguration. The challenge is to ensure that a radio communications component remains relevant over the entire life-time of a vehicle, i.e. 10 years and beyond. It is almost certain that a V2X framework feature-set will evolve within this period. SW Rec