ETSI GR MEC 022-2018 Multi-access Edge Computing(MEC) Study on MEC Support for V2X Use Cases (V2 1 1).pdf

《ETSI GR MEC 022-2018 Multi-access Edge Computing(MEC) Study on MEC Support for V2X Use Cases (V2 1 1).pdf》由会员分享，可在线阅读，更多相关《ETSI GR MEC 022-2018 Multi-access Edge Computing(MEC) Study on MEC Support for V2X Use Cases (V2 1 1).pdf（19页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI GR MEC 022 V2.1.1 (2018-09) Multi-access Edge Computing (MEC); Study on MEC Support for V2X Use Cases Disclaimer The present document has been produced and approved by the Multi-access Edge Computing (MEC) ETSI Industry Specification Group (ISG) and represents the views of those members who pa

2、rticipated in this ISG. It does not necessarily represent the views of the entire ETSI membership. GROUP REPORT ETSI ETSI GR MEC 022 V2.1.1 (2018-09) 2 Reference DGR/MEC-0022V2X.Support Keywords MEC, V2X ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax:

3、 +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 electronic versi

4、ons 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 prevailing document is t

5、he 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 documents is avail

6、able 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 any form or by a

7、ny 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 reproduction in all media

8、. 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 protected for the

9、benefit of its Members. GSMand the GSM logo are trademarks registered and owned by the GSM Association. ETSI ETSI GR MEC 022 V2.1.1 (2018-09) 3 Contents Intellectual Property Rights 4g3Foreword . 4g3Modal verbs terminology 4g31 Scope 5g32 References 5g32.1 Normative references . 5g32.2 Informative r

10、eferences 5g33 Definitions and abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 6g34 Overview 6g35 Use cases 6g35.1 Introduction 6g35.2 V2X use case group “safety“ 7g35.2.1 Description 7g35.2.2 Recommendations . 7g35.2.3 Evaluation . 8g35.3 V2X use case group “convenience“ 8g35.3.1 Descript

11、ion 8g35.3.2 Recommendations . 8g35.3.3 Evaluation . 9g35.4 V2X use case group “advanced driving assistance“ . 9g35.4.1 Description 9g35.4.2 Recommendations . 9g35.4.3 Evaluation . 10g35.5 V2X use case group “vulnerable road user“ . 10g35.5.1 Description 10g35.5.2 Recommendations . 10g35.5.3 Evaluat

12、ion . 11g36 Key issues and solutions. 11g36.1 Key issue 1: mobility and QoE support 11g36.1.1 Introduction. 11g36.1.2 Solution 1-1: predictive QoS support . 12g36.1.2.1 Description 12g36.1.2.2 Gap analysis 13g36.2 Key issue 2: low latency communication support with multi-operator operation 13g36.2.1

13、 Introduction. 13g36.2.2 Solution 2-1: shared underlying network 14g36.2.2.1 Description 14g36.2.2.2 Gap analysis 14g36.2.3 Solution 2-2: independent underlying network . 15g36.2.3.1 Description 15g36.2.3.2 Gap analysis 15g36.3 Key issue 3: communication traffic coordination with vehicles . 16g36.3.

14、1 Introduction. 16g36.3.2 Solution 3-1: inform communication traffic congestion to vehicles . 16g36.3.2.1 Description 16g36.3.2.2 Gap analysis 17g37 Conclusion and Recommendations 17g37.1 Prioritized V2X use cases . 17g37.2 Consolidated recommendations 17g37.3 Recommendations for future work . 18g3H

15、istory 19g3ETSI ETSI GR MEC 022 V2.1.1 (2018-09) 4 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, is publicly available for ETSI members and n

16、on-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.org/). P

17、ursuant 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 present

18、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 right to use or reproduce any trademark and/or t

19、radename. 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 Group Report (GR) has been produced by ETSI Industry Specification Group (ISG) Multi-access Edge Computing (

20、MEC). 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“ and “must not“ are NOT allowed i

21、n ETSI deliverables except when used in direct citation. ETSI ETSI GR MEC 022 V2.1.1 (2018-09) 5 1 Scope The present document focuses on identifying the MEC features to support V2X applications. It collects and analyses the relevant V2X use cases (including the findings from external organizations),

22、 evaluates the gaps from the defined MEC features and functions, and identifies the new requirements including new features and functions. When necessary, this may include identifying new multi-access edge services or interfaces, as well as changes to existing MEC services or interfaces, data models

23、, application rules and requirements. It will also recommend the necessary normative work to close these gaps if identified. 2 References 2.1 Normative references Normative references are not applicable in the present document. 2.2 Informative references References are either specific (identified by

24、 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. NOTE: While any hyperlinks included in this clause we

25、re 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 particular subject area. i.1 National Highway Traffic Safety Administration

26、(NHTSA) / Department of Transportation (DOT), “Federal Motor Vehicle Safety Standards; V2V Communications“. NOTE: Available at: https:/www.gpo.gov/fdsys/granule/FR-2017-01-12/2016-31059 i.2 ETSI TR 102 638: “Intelligent Transport Systems (ITS); Vehicular Communications; Basic Set of Applications; De

27、finitions“. i.3 3GPP TR 22.885: “Study on LTE support for Vehicle to Everything (V2X) services“. i.4 ETSI GS MEC 012: “Mobile Edge Computing (MEC); Radio Network Information API“. i.5 ETSI GS MEC 013: “Mobile Edge Computing (MEC); Location API“. i.6 ETSI GR MEC 018: “Mobile Edge Computing (MEC); End

28、 to End Mobility Aspects“. i.7 5G Automotive Association (5GAA) White Paper: “Toward fully connected vehicles: Edge computing for advanced automotive communications“. NOTE: Available at http:/5gaa.org/wp-content/uploads/2017/12/5GAA_T-170219-whitepaper-EdgeComputing_5GAA.pdf. i.8 ETSI GS MEC 001: “M

29、ulti-access Edge Computing (MEC); Terminology“. i.9 ETSI GS MEC 002: “Multi-access Edge Computing (MEC); Phase 2: Use Cases and Requirements“. i.10 ETSI TS 123 285: “Universal Mobile Telecommunications System (UMTS); LTE; Architecture enhancements for V2X services (3GPP TS 23.285)“. ETSI ETSI GR MEC

30、 022 V2.1.1 (2018-09) 6 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in ETSI GS MEC 001 i.8. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in ETSI GS MEC 001 i.8 and the following apply

31、: 5G Fifth Generation API Application Programming Interface IMA Intersection Movement Assist LS Location Service MNO Mobile Network Operator OEM Original Equipment Manufacturer OSS Operational Support System PER Packet Error Rate PLMN Public Land Mobile Network QoE Quality of Experience QoS Quality

32、of Service QW Queue WarningRAB Radio Access Bearer RAN Radio Access Network RAT Radio Access Technology RNI Radio Network Information RNIS Radio Network Information Service TNL Transport Network LayerV2I Vehicle-to-Infrastructure V2V Vehicle-to-Vehicle V2X Vehicle-to-EverythingVRU Vulnerable Road Us

33、er WLAN Wireless Local Area Network 4 Overview The present document identifies the MEC features in order to enable the necessary support for V2X applications. Clause 5 collects and analyses the relevant V2X use cases (including the findings from external organizations). The recommendations on the se

34、rvices and features are identified for each use case. Evaluation is provided for each recommendation to identify the issues to be solved. Clause 6 discusses the key issues and the corresponding solutions and further identifies the gaps from the existing MEC functions and features. Clause 7 concludes

35、 the study with the prioritized V2X use cases to be supported in this phase, and the consolidated recommendations. The recommendations for necessary normative work are provided in order to close the identified gaps. 5 Use cases 5.1 Introduction This clause discusses four use case groups that are com

36、monly known to the V2X communities i.7, namely “safety“, “convenience“, “advanced driving assistance“ and “vulnerable road user“. ETSI ETSI GR MEC 022 V2.1.1 (2018-09) 7 5.2 V2X use case group “safety“ 5.2.1 Description The V2X use case group “Safety“ includes several different types of use cases (r

37、elevant to MEC) to support road safety using the vehicle-to-infrastructure (V2I) communication in addition to the vehicle-to-vehicle (V2V). Intersection Movement Assist (IMA) This type of use cases was specifically listed in the US DOT NHTSA publication 2016-0126 i.1, and ETSI TR 102 638 i.2. The ma

38、in purpose of IMA is to warn drivers of vehicles approaching from a lateral direction at an intersection. IMA is designed to avoid intersection crossing crashes, the most severe crashes based on the fatality counts. Intersection crashes include intersection, intersection-related, driveway/alley, and

39、 driveway access related crashes. Figure 5.2.1-1 illustrates two typical scenarios: a) intersection collision warning, and b) intersection management. a) intersection collision warning b) intersection management Figure 5.2.1-1: V2X “safety“ use cases Queue Warning (QW) i.3 In a lot of situations, a

40、queue of vehicles on the road may pose a potential danger and cause delay of traffic, e.g. when a turning queue extends to other lanes. Using the V2I service, the queue information can be made available to other drivers beforehand. This minimizes the likelihood of crashes and allows for mitigation a

41、ctions. 5.2.2 Recommendations This group of V2X use cases requires the support of roadside infrastructure for the V2V and V2I communications. In the case that the Multi-access Edge Computing system is used to provide the V2X support, the related recommendations on the services and features enabled i

42、n the system include: R-5.2.2-1 It is recommended that the MEC system provides feedback information from the network to the vehicle in support of V2X functions, predicting whether a communication channel is currently reliable or not (e.g. in terms of fulfilling latency requirements and 100 % packet

43、arrival). R-5.2.2-2 It is recommended that the MEC system provides interoperability by supporting V2X information exchange among road users connected through different access technologies or networks or mobile operators. R-5.2.2-3 It is recommended that the MEC system enables multi-operator operatio

44、n for V2X mobiles/users to provide service continuity across access network coverage nationwide and across borders of different operators networks. R-5.2.2-4 It is recommended that the MEC systems provide interoperability in a multi-operator scenario, enabling MEC apps in different systems to commun

45、icate securely with each other, in order to enable synchronization in multi-operator systems also in absence of cellular coverage (outside of 3GPPTMdomain). ETSI ETSI GR MEC 022 V2.1.1 (2018-09) 8 R-5.2.2-5 It is recommended that the MEC system provides interoperability in a multi-operator scenario,

46、 enabling MEC apps to communicate securely with the V2X-related 3GPPTMcore network logical functions (e.g. V2X control function) and gathering PC5 i.10 V2X relevant information (e.g. PC5 configuration parameters) from 3GPPTMnetwork. 5.2.3 Evaluation R-5.2.2-1 In current MEC system, the RNI API can p

47、rovide up-to-date radio network information to the service consumer, i.e. the V2X functions. However, current QoS-related information in RNI API is not sufficient in order to allow necessary prediction regarding the QoS performance (e.g. latency, throughput, reliability). Therefore, potential enhanc

48、ements on RNI API for the prediction should be considered including both relevant measurements in RAN or processed results for the prediction. This enhanced service could also be provided by a new API. R-5.2.2-2 In current MEC definition, MEC system includes not only 3GPPTMaccess, but also other non

49、-3GPPTMaccess. Therefore the MEC system is RAT agnostic and will be enhanced for multi-access if needed. There is no need to consider the different access networks within an operators system in this study. Moreover, the information exchange among MEC system from different operators may require potential enhancement on the horizontal communication for the MEC system. R-5.2.2-3 The operator network is normally region specific or country specific. The V2X service requires a seamless coverage of the commu