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

3GPP TR 36.788 V1.0.0 (2018-06)Technical Report3rd 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)23Keywords5G-Radio3GPPPostal address3GPP support office address650 Route des Lucioles - Sophia AntipolisValbonne - FRANCETel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16InternetCopyright NotificationNo 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 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 AssociationContentsForeword51Scope62References63Definitions, symbols and abbreviations63.1Definitions63.2Symbols63.3Abbreviations64Background74.1Justification74.2Objective75V2X scenarios in Rel-1585.1V2X operating scenarios85.2 Operating bands and channel arrangement95.2.1 Channel bandwidth for V2X Communication Channel bandwidth for intra-band contiguous operation Channel bandwidth for inter-band operation96Co-existence study117Transmit characteristics117.1 64QAM over PC5117.1.1 MPR for single carrier for power class 3117.1.2 MPR for single carrier for power class 2127.1.3 MPR for 10MHz+10MHz for power class 3127.1.4 A-MPR for 64QAM137.2 Intra-band scenario137.2.1 Transmit power Maximum output power UE maximum output power for modulation / channel bandwidth137.2.2 Output RF spectrum emissions Spectrum emission mask ACLR Spurious emission147.2.3 Transmit intermodulation147.3 Inter-band scenario147.3.1 General TX requirements147.3.2 Configured transmitted power for V2X148Receiver characteristics148.1 64QAM over PC5148.1.1 Maximum input level148.2 Intra-band contiguous scenario158.2.1 REFSENS158.2.2 Maximum input level158.2.3 Adjacent Channel Selectivity (ACS)158.2.4 Blocking characteristics In-band blocking Out-of-band blocking178.2.5 Spurious response178.2.6 Intermodulation characteristics188.2.7 RX spurious emissions188.2.8 Receiver image188.3 Inter-band scenario188.3.1 General RX requirements18Annex A: Change history20ForewordThis 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 for all changes of substance, i.e. technical enhancements, corrections, updates, etc.zthe third digit is incremented when editorial only changes have been incorporated in the document.1ScopeThe 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).2ReferencesThe 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.13GPPTR21.905: Vocabulary for 3GPP Specifications.2RP-170798: New WID on 3GPP V2X Phase 2.3Definitions, symbols and abbreviations3.1DefinitionsFor the purposes of the present document, the terms and definitions given in TR21.9051 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR21.9051.3.2SymbolsVoid.3.3AbbreviationsFor the purposes of the present document, the abbreviations given in TR21.9051 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR21.9051.ProSeProximity based ServicesPSBCHPhysical Sidelink Broadcast CHannelPSCCHPhysical Sidelink Control CHannelPSDCHPhysical Sidelink Discovery CHannelPSSPrimary Synchronization SignalPSSCHPhysical Sidelink Shared CHannelPSSSPrimary Sidelink Synchronization SignalSSSSecondary Synchronization SignalSSSSSecondary Sidelink Synchronization Signal V2VVehicle to VehicleV2XVehicle to Anything4Background4.1JustificationTo 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.2ObjectiveThe 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, RAN4a) 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, RAN43. 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”. RAN45. Specify necessary RRM core requirements. RAN4In 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.5V2X scenarios in Rel-155.1V2X operating scenariosRAN4 focus on V2X operating scenarios as below in V2X phase 2 WI due to interested operator service scenarios.- 1st priority V2X operating scenariosn Intra-band multi-carrier operation in Band 47 (PC5) with 23dBm output power: 20MHz+10MHzn 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 scenariosn Intra-band multi-carrier operation in Band 47 (PC5) with 23dBm output power: 10MHz+10MHz+10MHzn 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 scenariosn Intra-band multi-carrier operation in Band 47 (PC5) with 26dBm output power: 10MHz+10MHzn 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 arrangement5.2.1 Channel bandwidth for V2X Communication Channel bandwidth for intra-band contiguous operationV2X 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 20MHz40MHz aggregated bandwidth. Then the Table 5.6G.1-3 can be updated as below:Table -1 V2X bandwidth classes and corresponding nominal guard bandsV2X Bandwidth ClassAggregated Transmission Bandwidth ConfigurationNumber of contiguous CCNominal Guard Band BWGBANRB,agg 1001a1 BWChannel(1) - 0.5Df1 (NOTE 2)B25 NRB,agg 10020.05 max(BWChannel(1),BWChannel(2) - 0.5Df1C100 NRB,agg 20020.05 max(BWChannel(1),BWChannel(2) - 0.5Df1C1100 NRB,agg 20030.05 max(BWChannel(1),BWChannel(2) - 0.5Df1D200 NRB,agg 3003NOTE 3E300 NRB,agg 4004NOTE 3F400 NRB,agg 5005NOTE 3I700 NRB,agg 8008NOTE 3NOTE 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 -2. Table -2 V2X intra-band multi-carrier and CA configurationsV2X multi-carrier and CA configuration / Bandwidth combination setV2X multi-carrier and CA ConfigurationV2X multi-carrier and CA Configuration for TXComponent carriers in order of increasing carrier frequencyMaximum aggregated bandwidth MHzBandwidth combination setChannel bandwidths for carrier MHzChannel bandwidths for carrier MHzChannel bandwidths for carrier MHzChannel bandwidths for carrier MHzChannel bandwidths for carrier MHzV2X_47BV2X_47B1010200V2X_47CV2X_47C10203002010V2X_47C1V2X_47B101010300 Channel bandwidth for inter-band operationFor V2X inter-band con-current operation, the V2X Communication channel bandwidths for each operating band is specified in Table -1 for Rel-15.Table -1: Inter-band con-current V2X configurations and bandwidth combination setsV2X con-current band Configuration V2X con-current band Configuration for TX E-UTRA or V2X operating Bands1.4MHz3MHz5MHz10MHz15MHz20MHzMaximum bandwidth MHzBandwidth combination setV2X_3A-47BV2X_3A-47A,V2X_47B3YesYesYesYesYesYes40047See V2X_47B Bandwidth combination set 0 in Table -2V2X_5A-47BV2X_5A-47A, V2X_47B5YesYes30047See V2X_47B Bandwidth combination set 0 in Table -2V2X_7A_47BV2X_7A_47A,V2X_47B7YesYesYesYes40047See V2X_47B Bandwidth combination set 0 in Table -2V2X_8A-47BV2X_8A-47A,V2X_47B8YesYesYesYes30047See V2X_47B Bandwidth combination set 0 in Table -2V2X_20A-47BV2X_20A-47A, V2X_47B20YesYesYesYes40047See V2X_47B Bandwidth combination set 0 in Table -2V2X_34A-47BV2X_34A-47A,V2X_47B34YesYesYes35047See V2X_47B Bandwidth combination set 0 in Table -2V2X_39A-47BV2X_39A-47A,V2X_47B39YesYesYesYes40047See V2X_47B Bandwidth combination set 0 in Table -2V2X_41A-47BV2X_41A-47A,V2X_47B41YesYesYesYes40047See V2X_47B Bandwidth combination set 0 in Table -2V2X_3A-47CV2X_3A-47A,V2X_47C3YesYesYesYesYesYes50047See V2X_47C Bandwidth combination set 0 in Table -2V2X_5A-47CV2X_5A-47A, V2X_47C5YesYes40047See V2X_47C Bandwidth combination set 0 in Table -2V2X_7A_47CV2X_7A_47A,V2X_47C7YesYesYesYes50047See V2X_47C Bandwidth combination set 0 in Table -2V2X_8A-47CV2X_8A-47A,V2X_47C8YesYesYesYes40047See V2X_47C Bandwidth combination set 0 in Table -2V2X_20A-47CV2X_20A-47A, V2X_47C20YesYesYesYes50047See V2X_47C Bandwidth combination set 0 in Table -2V2X_34A-47CV2X_34A-47A,V2X_47C34YesYesYes45047See V2X_47C Bandwidth combination set 0 in Table -2V2X_39A-47CV2X_39A-47A,V2X_47C39YesYesYesYes50047See V2X_47C Bandwidth combination set 0 in Table -2V2X_41A-47CV2X_41A-47A,V2X_47C41YesYesYesYes50047See V2X_47C Bandwidth combination set 0 in Table -2500V2X_3A-47C1V2X_3A-47A,V2X_47