TR 36.788 V1.0.0 (2018-06) Vehicle-to-Everything (V2X) Phase 2 User Equipment (UE) radio transmission and reception

《TR 36.788 V1.0.0 (2018-06) Vehicle-to-Everything (V2X) Phase 2 User Equipment (UE) radio transmission and reception》由會員分享，可在線閱讀，更多相關(guān)《TR 36.788 V1.0.0 (2018-06) Vehicle-to-Everything (V2X) Phase 2 User Equipment (UE) radio transmission and reception（23頁珍藏版）》請?jiān)谘b配圖網(wǎng)上搜索。

3GPP TR 36.788 V1.0.0 (2018-06) Technical Report 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Vehicle-to-Everything (V2X) Phase 2; User Equipment (UE) radio transmission and reception (Release 15) 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.788 V1.0.0 (2018-06) 23 Keywords 5G-Radio 3GPP Postal address 3GPP support office address 650 Route des Lucioles - Sophia Antipolis Valbonne - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Internet http://www.3gpp.org Copyright Notification No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. 2016, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). All rights reserved. UMTS? is a Trade Mark of ETSI registered for the benefit of its members 3GPP? is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners LTE? is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners GSM and the GSM logo are registered and owned by the GSM Association Contents Foreword 5 1 Scope 6 2 References 6 3 Definitions, symbols and abbreviations 6 3.1 Definitions 6 3.2 Symbols 6 3.3 Abbreviations 6 4 Background 7 4.1 Justification 7 4.2 Objective 7 5 V2X scenarios in Rel-15 8 5.1 V2X operating scenarios 8 5.2 Operating bands and channel arrangement 9 5.2.1 Channel bandwidth for V2X Communication 9 5.2.1.1 Channel bandwidth for intra-band contiguous operation 9 5.2.1.2 Channel bandwidth for inter-band operation 9 6 Co-existence study 11 7 Transmit characteristics 11 7.1 64QAM over PC5 11 7.1.1 MPR for single carrier for power class 3 11 7.1.2 MPR for single carrier for power class 2 12 7.1.3 MPR for 10MHz+10MHz for power class 3 12 7.1.4 A-MPR for 64QAM 13 7.2 Intra-band scenario 13 7.2.1 Transmit power 13 7.2.1.1 Maximum output power 13 7.2.1.2 UE maximum output power for modulation / channel bandwidth 13 7.2.2 Output RF spectrum emissions 13 7.2.2.1 Spectrum emission mask 13 7.2.2.2 ACLR 13 7.2.2.3 Spurious emission 14 7.2.3 Transmit intermodulation 14 7.3 Inter-band scenario 14 7.3.1 General TX requirements 14 7.3.2 Configured transmitted power for V2X 14 8 Receiver characteristics 14 8.1 64QAM over PC5 14 8.1.1 Maximum input level 14 8.2 Intra-band contiguous scenario 15 8.2.1 REFSENS 15 8.2.2 Maximum input level 15 8.2.3 Adjacent Channel Selectivity (ACS) 15 8.2.4 Blocking characteristics 16 8.2.4.1 In-band blocking 16 8.2.4.1 Out-of-band blocking 17 8.2.5 Spurious response 17 8.2.6 Intermodulation characteristics 18 8.2.7 RX spurious emissions 18 8.2.8 Receiver image 18 8.3 Inter-band scenario 18 8.3.1 General RX requirements 18 Annex A: Change history 20 Foreword This 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.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. 1 Scope The present document is the Technical Report on V2X phase 2 for LTE. The purpose of the present document is to study the radio requirements on V2X phase 2 based on LTE sidelink as part of the Rel-15 work item. The normative requirements resulting from the present document will be addressed in the applicable release 15 Technical Specifications (TS). 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. - References are either specific (identified by date of publication, edition number, version number, etc.) or nonspecific. - For a specific reference, subsequent revisions do not apply. - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document. [1] 3GPPTR21.905: "Vocabulary for 3GPP Specifications". [2] RP-170798: " New WID on 3GPP V2X Phase 2". 3 Definitions, symbols and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in TR21.905[1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR21.905[1]. 3.2 Symbols Void. 3.3 Abbreviations For the purposes of the present document, the abbreviations given in TR21.905[1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR21.905[1]. ProSe Proximity based Services PSBCH Physical Sidelink Broadcast CHannel PSCCH Physical Sidelink Control CHannel PSDCH Physical Sidelink Discovery CHannel PSS Primary Synchronization Signal PSSCH Physical Sidelink Shared CHannel PSSS Primary Sidelink Synchronization Signal SSS Secondary Synchronization Signal SSSS Secondary Sidelink Synchronization Signal V2V Vehicle to Vehicle V2X Vehicle to Anything 4 Background 4.1 Justification To expand the LTE platform to the automotive industry, the initial standard on support of V2V services was completed in Sep 2016. Further enhancements that focusing on additional V2X operation scenarios leveraging the cellular infrastructure, also for inclusion in Release 14, was completed in March 2017. Currently, SA1 is working on enhancement of 3GPP support for V2X services in FS_eV2X. SA1 had identified 25 use cases for advanced V2X services and they are categorized into four use case groups: vehicles platooning, extended sensors, advanced driving and remote driving. The detailed description of each use case group is provided as below. The consolidated requirements for each use case group are captured in TR 22.886. Based on the input from FS_eV2X as well as potential inputs from RAN, SA1 will generate a set of normative requirements for Release 15. 1. Vehicles Platoonning enables the vehicles to dynamically form a platoon travelling together. All the vehicles in the platoon obtain information from the leading vehicle to manage this platoon. These information allow the vehicles to drive closer than normal in a coordinated manner, going to the same direction and travelling together. 2. Extended Sensors enables the exchange of raw or processed data gathered through local sensors or live video images among vehicles, road site units, devices of pedestrian and V2X application servers. The vehicles can increase the perception of their environemnt beyond of what their own sensors can detect and have a more broad and holistic view of the local situation. High data rate is one of the key characteristics. 3. Advanced Driving enables semi-automated or full-automated driving. Each vehicle and/or RSU shares its own perception data obtained from its local sensors with vehicles in proximity and that allows vehicles to synchronize and coordinate their trajectories or manoeuvres. Each vehicle shares its driving intention with vehicles in proximity too. 4. Remote Driving enables a remote driver or a V2X application to operate a remote vehicle for those passengers who cannot drive by themselves or remote vehicles located in dangerous environments. For a case where variation is limited and routes are predictable, such as public transportation, driving based on cloud computing can be used. High reliability and low latency are the main requirements. In Release 15, it is expected to enhance the Cellular-based V2X services (V2V, V2I/N, and V2P) to support advanced V2X services as identified in TR 22.886 in a holistic and complementary manner to Release 14 V2X, which will involve both Uu interface and PC5 interface. 4.2 Objective The motivation of this work item is to specify 3GPP V2X Phase 2 to support advanced V2X services as identified in SA1 TR 22.886. The specified technologies should be backward compatible with Release 14 V2X for the delivery of safety messages (i.e. CAM/DENM messages). The detailed objectives of this work item are as follows: 1. Specify solutions for the following PC5 functionalities, which can co-exist in the same resource pools as Rel-14 functionality and use the same scheduling assignment format (which can be decoded by Rel-14 UEs), without causing significant degradation to Rel-14 PC5 operation compared to that of Rel-14 UEs: [RAN1, RAN2, RAN4] a) Carrier aggregation (up to 8 PC5 carriers); Inter- and intra-band multi-carrier was finished in Rel-14 as below, multiple carriers and carrier aggregation may have difference in resource allocation. Need to wait RAN1 study. b) 64QAM; c) Reduce the maximum time between packet arrival at Layer 1 and resource selected for transmission; d) Radio resource pool sharing between UEs using mode 3 and UEs using mode 4; 2. Study the feasibility and gain of PC5 operation with Transmit Diversity, assuming this PC5 functionality would co-exist in the same resource pools as Rel-14 functionality and use the same scheduling assignment format (which can be decoded by Rel-14 UEs), without causing significant degradation to Rel-14 PC5 operation compared to that of Rel-14 UEs, and specify this PC5 functionality if justified. [RAN1, RAN2, RAN4] 3. Study the feasibility and gain of PC5 operation with Short TTI, assuming this PC5 functionality would co-exist in the same resource pools as Rel-14 functionality with and without using the same scheduling assignment format, and provide RAN1 observations and recommendations to RAN by RAN#77. [RAN1, RAN2] a) A following decision for normative work is up to consensus at RAN. 4. Specify necessary RF requirements for the specified PC5 functionalities in Band 47, where not covered by the Rel-15 work item “V2X new band combinations for LTE”. [RAN4] 5. Specify necessary RRM core requirements. [RAN4] In this work item, no new numerology, waveform, and channel coding will be considered. Based on the feedback from SA2 on LS “Support of Unicast and Groupcast transmission over PC5 for eV2X”, the scope of this work item may be further updated. 5 V2X scenarios in Rel-15 5.1 V2X operating scenarios RAN4 focus on V2X operating scenarios as below in V2X phase 2 WI due to interested operator service scenarios. - 1st priority V2X operating scenarios n Intra-band multi-carrier operation in Band 47 (PC5) with 23dBm output power: 20MHz+10MHz n For combinations of intra-band multi-carrier operation in Band 47 (PC5) as above and inter-band con-current operation in a licensed band (Uu) - 2nd priority V2X operating scenarios n Intra-band multi-carrier operation in Band 47 (PC5) with 23dBm output power: 10MHz+10MHz+10MHz n For combinations of intra-band multi-carrier operation in Band 47 (PC5) as above and inter-band con-current operation in a licensed band (Uu) - 3rd priority V2X operating scenarios n Intra-band multi-carrier operation in Band 47 (PC5) with 26dBm output power: 10MHz+10MHz n For combinations of intra-band multi-carrier operation in Band 47 (PC5) as above and inter-band con-current operation in a licensed band (Uu) n Intra-band multi-carrier operation in Band 47 (PC5) with 26dBm output power: 20MHz+10MHz, 10MHz+10MHz+10MHz For combinations of intra-band multi-carrier operation in Band 47 (PC5) as above and inter-band con-current operation in a licensed band (Uu) 5.2 Operating bands and channel arrangement 5.2.1 Channel bandwidth for V2X Communication 5.2.1.1 Channel bandwidth for intra-band contiguous operation V2X Bandwidth Class is specified in Table 5.6G.1-3 for V2X intra-band contiguous multi-carrier operation in TS 36.101. For new scenarios in Rel-15, new V2X bandwidth class needs to be introduced. For 20MHz+10MHz, bandwidth class C in CA can be reused for V2X with 2 contiguous CCs. But for 10MHz+10MHz+10MHz, no bandwidth class in CA is applicable. Bandwidth class C1 can be introduced for this scenario with 3CCs supporting 20MHz~40MHz aggregated bandwidth. Then the Table 5.6G.1-3 can be updated as below: Table 5.2.1.1-1 V2X bandwidth classes and corresponding nominal guard bands V2X Bandwidth Class Aggregated Transmission Bandwidth Configuration Number of contiguous CC Nominal Guard Band BWGB A NRB,agg ≤ 100 1 a1 BWChannel(1) - 0.5Df1 (NOTE 2) B 25 < NRB,agg ≤ 100 2 [0.05 max(BWChannel(1),BWChannel(2)) - 0.5Df1] C 100 < NRB,agg ≤ 200 2 [0.05 max(BWChannel(1),BWChannel(2)) - 0.5Df1] C1 100 < NRB,agg ≤ 200 3 [0.05 max(BWChannel(1),BWChannel(2)) - 0.5Df1] D 200 < NRB,agg ≤ 300 3 NOTE 3 E 300 < NRB,agg ≤ 400 4 NOTE 3 F 400 < NRB,agg ≤ 500 5 NOTE 3 I 700 < NRB,agg ≤ 800 8 NOTE 3 NOTE 1: BWChannel(j), j = 1, 2, 3, 4 is the channel bandwidth of an E-UTRA component carrier according to Table 5.6-1 and Df1 = Df for the downlink with Df the subcarrier spacing while Df1 = 0 for the uplink. NOTE 2: a1 = 0.16/1.4 for BWChannel(1) = 1.4 MHz whereas a1 = 0.05 for all other channel bandwidths. NOTE 3: Applicable for later releases. For V2X contiguous multi-carrier and CA operation, the V2X Communication channel bandwidths for each operating band is specified in Table 5.2.1.1-2. Table 5.2.1.1-2 V2X intra-band multi-carrier and CA configurations V2X multi-carrier and CA configuration / Bandwidth combination set V2X multi-carrier and CA Configuration V2X multi-carrier and CA Configuration for TX Component carriers in order of increasing carrier frequency Maximum aggregated bandwidth [MHz] Bandwidth combination set Channel bandwidths for carrier [MHz] Channel bandwidths for carrier [MHz] Channel bandwidths for carrier [MHz] Channel bandwidths for carrier [MHz] Channel bandwidths for carrier [MHz] V2X_47B V2X_47B 10 10 20 0 V2X_47C V2X_47C 10 20 30 0 20 10 V2X_47C1 V2X_47B 10 10 10 30 0 5.2.1.2 Channel bandwidth for inter-band operation For V2X inter-band con-current operation, the V2X Communication channel bandwidths for each operating band is specified in Table 5.2.1.2-1 for Rel-15. Table 5.2.1.2-1: Inter-band con-current V2X configurations and bandwidth combination sets V2X con-current band Configuration V2X con-current band Configuration for TX E-UTRA or V2X operating Bands 1.4 MHz 3 MHz 5 MHz 10 MHz 15 MHz 20 MHz Maximum bandwidth [MHz] Bandwidth combination set V2X_3A-47B V2X_3A-47A, V2X_47B 3 Yes Yes Yes Yes Yes Yes 40 0 47 See V2X_47B Bandwidth combination set 0 in Table 5.2.1.1-2 V2X_5A-47B V2X_5A-47A, V2X_47B 5 Yes Yes 30 0 47 See V2X_47B Bandwidth combination set 0 in Table 5.2.1.1-2 V2X_7A_47B V2X_7A_47A, V2X_47B 7 Yes Yes Yes Yes 40 0 47 See V2X_47B Bandwidth combination set 0 in Table 5.2.1.1-2 V2X_8A-47B V2X_8A-47A, V2X_47B 8 Yes Yes Yes Yes 30 0 47 See V2X_47B Bandwidth combination set 0 in Table 5.2.1.1-2 V2X_20A-47B V2X_20A-47A, V2X_47B 20 Yes Yes Yes Yes 40 0 47 See V2X_47B Bandwidth combination set 0 in Table 5.2.1.1-2 V2X_34A-47B V2X_34A-47A, V2X_47B 34 Yes Yes Yes 35 0 47 See V2X_47B Bandwidth combination set 0 in Table 5.2.1.1-2 V2X_39A-47B V2X_39A-47A, V2X_47B 39 Yes Yes Yes Yes 40 0 47 See V2X_47B Bandwidth combination set 0 in Table 5.2.1.1-2 V2X_41A-47B V2X_41A-47A, V2X_47B 41 Yes Yes Yes Yes 40 0 47 See V2X_47B Bandwidth combination set 0 in Table 5.2.1.1-2 V2X_3A-47C V2X_3A-47A, V2X_47C 3 Yes Yes Yes Yes Yes Yes 50 0 47 See V2X_47C Bandwidth combination set 0 in Table 5.2.1.1-2 V2X_5A-47C V2X_5A-47A, V2X_47C 5 Yes Yes 40 0 47 See V2X_47C Bandwidth combination set 0 in Table 5.2.1.1-2 V2X_7A_47C V2X_7A_47A, V2X_47C 7 Yes Yes Yes Yes 50 0 47 See V2X_47C Bandwidth combination set 0 in Table 5.2.1.1-2 V2X_8A-47C V2X_8A-47A, V2X_47C 8 Yes Yes Yes Yes 40 0 47 See V2X_47C Bandwidth combination set 0 in Table 5.2.1.1-2 V2X_20A-47C V2X_20A-47A, V2X_47C 20 Yes Yes Yes Yes 50 0 47 See V2X_47C Bandwidth combination set 0 in Table 5.2.1.1-2 V2X_34A-47C V2X_34A-47A, V2X_47C 34 Yes Yes Yes 45 0 47 See V2X_47C Bandwidth combination set 0 in Table 5.2.1.1-2 V2X_39A-47C V2X_39A-47A, V2X_47C 39 Yes Yes Yes Yes 50 0 47 See V2X_47C Bandwidth combination set 0 in Table 5.2.1.1-2 V2X_41A-47C V2X_41A-47A, V2X_47C 41 Yes Yes Yes Yes 50 0 47 See V2X_47C Bandwidth combination set 0 in Table 5.2.1.1-2 50 0 V2X_3A-47C1 V2X_3A-47A, V2X_47B 3 Yes Yes Yes Yes Yes Yes 50 0 47 See V2X_47C1 Bandwidth combination set 0 in Table 5.2.1.1-2 V2X_5A-47C1 V2X_5A-47A, V2X_47B 5 Yes Yes 50 0 47 See V2X_47C1 Bandwidth combination set 0 in Table 5.2.1.1-2 V2X_7A_47C1 V2X_7A_47A, V2X_47B 7 Yes Yes Yes Yes 50 0 47 See V2X_47C1 Bandwidth combination set 0 in Table 5.2.1.1-2 V2X_8A-47C1 V2X_8A-47A, V2X_47B 8 Yes Yes Yes Yes 40 0 47 See V2X_47C1 Bandwidth combination set 0 in Table 5.2.1.1-2 V2X_20A-47C1 V2X_20A-47A, V2X_47B 20 Yes Yes Yes Yes 50 0 47 See V2X_47C1 Bandwidth combination set 0 in Table 5.2.1.1-2 V2X_34A-47C1 V2X_34A-47A, V2X_47B 34 Yes Yes Yes 45 0 47 See V2X_47C1 Bandwidth combination set 0 in Table 5.2.1.1-2 V2X_39A-47C1 V2X_39A-47A, V2X_47B 39 Yes Yes Yes Yes 50 0 47 See V2X_47C1 Bandwidth combination set 0 in Table 5.2.1.1-2 V2X_41A-47C1 V2X_41A-47A, V2X_47B 41 Yes Yes Yes Yes 50 0 47 See V2X_47C1 Bandwidth combination set 0 in Table 5.2.1.1-2 50 0 6 Co-existence study 7 Transmit characteristics 7.1 64QAM over PC5 Requirements specific to 64QAM include MPR. For MPR, simulation needs to be run for 64QAM to meet general LTE ACLR, SEM, EVM requirements for both single carrier and intra-band contiguous multi-carrier operation. 7.1.1 MPR for single carrier for power class 3 Based on the simulation results, the allowed Maximum Power Reduction (MPR) for 64QAM for power class 3 can be specified as follows: Table 7.1.1-1: Maximum Power Reduction (MPR) for power class 3 V2X Communication (Contiguous PSCCH and PSSCH transmission) Modulation Channel bandwidth / Transmission bandwidth (NRB) MPR (dB) 1.4 MHz 3.0 MHz 5 MHz 10 MHz 15 MHz 20 MHz QPSK - - ≤ 1.5 16 QAM - - ≤ 2 64 QAM - - ≤ 3 For transmissions with PSCCH and PSSCH in non-adjacent resource blocks in single component carrier, the allowed Maximum Power Reduction (MPR) for the maximum output power shall be as specified as follows MPR = CEIL {MA, 0.5} Where MA is defined for QPSK, 16QAM and 64QAM as follows MA = 4.5 ; 0.00< A ≤ 0.2 5.25 –3.7