3GPP TR 36.885 V2.0.0 (2016-05)Technical Report3rd Generation Partnership Project;Technical Specification Group Radio Access Network;Study on LTE-based V2X Services;(Release 14)The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP.The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.This Report is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification.Specifications and Reports for implementation of the 3GPP TM system should be obtained via the 3GPP Organizational Partners Publications Offices.3GPP TR 36.885 V2.0.0 (2016-05)62Release 14Keywords3GPPPostal address3GPP support office address650 Route des Lucioles - Sophia AntipolisValbonne - FRANCETel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16Internethttp:/www.3gpp.orgCopyright NotificationNo part may be reproduced except as authorized by written permission.The copyright and the foregoing restriction extend to reproduction in all media. 2013, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC).All rights reserved.UMTS is a Trade Mark of ETSI registered for the benefit of its members3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational PartnersLTE is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational PartnersGSM and the GSM logo are registered and owned by the GSM AssociationContentsForeword4Introduction51Scope62References63Definitions, symbols and abbreviations73.1Definitions73.2Symbols83.3Abbreviations84V2X operation scenarios84.1Scenario 184.1.1General Description84.1.2Operation Aspects94.2Scenario 2104.2.1General Description104.2.2Operation Aspects114.3Scenario 3124.3.1General Description124.3.2Operation Aspects135Technical support for V2V145.1PC5 interface145.1.1Resource allocation155.1.2Handling high Doppler case185.1.3Synchronization195.2Uu interface206Technical support for V2I/N246.1PC5 interface246.2Uu interface247Technical support for V2P247.1PC5 interface247.2Uu interface258Architecture and high level procedures for V2X258.1Local Breakout for V2X258.2MBMS for V2X268.2.1 Delivery of V2x Messages via MBMS268.2.2Support of small and variable areas in V2X278.2.3Localized MBMS318.3 Multiple Operator support in V2X349Evaluation results359.1Capacity analysis359.1.1PC5-based V2V359.1.2 Uu-based V2V369.1.3Uu-based V2I/N379.1.4PC5-based V2I/N389.1.5PC5-based V2P409.2Latency Analysis439.2.1Evaluation of overall latency439.2.2Observations549.3Power consumption analysis5510Coexistence with DSRC/IEEE 802.11p in the same channel6011Conclusions60Annex A: Evaluation methodology62A.1 System level simulation assumptions62A.1.1 Evaluation scenarios62A.1.2 UE drop and mobility model64A.1.3 eNB and RSU deployment67A.1.4 Channel model69A.1.5 Traffic model71A.1.6 Performance metric73A.2 Link level simulation assumptions74Annex B: Detailed evaluation results for PC5-based V2V75B.1 Simulation assumptions75B.2 Simulation results83Annex C: Detailed evaluation results for Uu-based V2V105C.1 Simulation assumptions105C.2 Simulation results113Annex D: Detailed evaluation results for Uu-based V2I/N130D.1 Simulation assumptions130D.2 Simulation results132Annex E: Detailed evaluation results for PC5-based V2I/N135E.1 Simulation assumptions135E.2 Simulation results141Annex F: Detailed evaluation results for PC5-based V2P170F.1 Simulation assumptions170F.2 Simulation results177Annex G: Details of latency analysis207G.1 Scenarios for latency analysis207G.1.1 Latency decomposition of scenarios207G.2 Analysis of latency component209G.2.1 Scheduling policy and parameter values209G.2.2 Analysis of each component210Annex H: Traffic Characteristics of CAM218Annex I: Change history219ForewordThis Technical Report has been produced by the 3rd Generation Partnership Project (3GPP).The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:Version x.y.zwhere:xthe first digit:1presented to TSG for information;2presented to TSG for approval;3or greater indicates TSG approved document under change control.ythe second digit is incremented f