I-AName of the Independent Evaluation Group



Radiocommunication Study GroupsReceived:12 February 2020?Source: Trans-Pacific Evaluation Group (TPCEG)Document 5D/94-E14 February 2020English onlyTECHNOLOGY ASPECTSIndustrial Technology Research Institute, Inc. (ITRI)Final evaluation Report from Trans-Pacific Evaluation Group on the IMT-2020 proposal in Documents IMT-2020/3(Rev.4)(“3GPP” under STEP 3 of the IMT-2020 PROCESS)This document describes the final evaluation results and activities identified for IMT-2020 candidate technology submissions in Documents IMT-2020/3(Rev.4) from Trans-Pacific Evaluation Group (TPCEG).TPCEG was formed by ITRI Inc., and a registered Independent Evaluation Group (IEG) committing in participating in the process of IMT-2020 evaluation. The proponents of TPCEG coming from trans-pacific area, including Taiwan Association of Information and Communication Standards (TAICS) and other research units. TPCEG has initiated the evaluation work after the ITU-R event, Workshop on IMT-2020 terrestrial radio interfaces, in October 2017. During the period from October 2017 (the 28th meeting of Working Party 5D) to December 2019 (the 33rd meeting of Working Party 5D), the collaboration between TPCEG proponents has been designated for evaluating the IMT-2020 candidate technology submissions. At the TPCEG meeting in December 2019, evaluation and study results are for the (S)RITs submitted by 3GPP have been reviewed by proponents. With the coordination of ITRI Inc., TPCEG concludes the IMT-2020 evaluation work with this final evaluation report.The attached evaluation report consists of 3 Parts:–Part I: Administrative Aspects of Trans-Pacific Evaluation Group.–Part II: Technical Aspects of the work in Trans-Pacific Evaluation Group.–Part III: Conclusion.Attachment: 1AttachmentPart I: Administrative Aspects of Trans-Pacific Evaluation GroupI-AName of the Independent Evaluation GroupThe Independent Evaluation Group is called Trans-Pacific Evaluation Group (TPCEG).I-BIntroduction and background of Trans-Pacific Evaluation GroupTPCEG is an international, non-profit, technology-neutral study group formed by ITRI as an independent evaluation group with the aim of analyzing and evaluating IMT-2020 (S)RIT proposals.The mission is to promote growth of wireless broadband through collecting and disseminating information that increases public awareness of industry’s products and services.The study group targets on:–Evaluating candidate IMT-2020 technologies against ITU-R criteria–Coordinating and sharing information and results with proponents and other evaluation groups–Examining and verifying simulation results–Preparing evaluation report for candidate (S)RITs.In Phase 1 from 2017 to 2018, TPCEG invited the proponents form Trans-Pacific region to join evaluation work on IMT-2020 evaluation. With the contributions form TAICS proponents and the coordination from ITRI, an initial evaluation report and an interim report are submitted to ITU-R at WP5D meetings in 18th September 2018 and 10th December 2019.In Phase 2 from 2019 to 2020, TPCEG keeps updating research results with more evaluation data and conclude the evaluation work with this final report. This final evaluation report is provided for ITU-R at WP5D#34 meeting in February 2020.I-CMethod of WorkTPCEG is a study group with contribution-driven working model. All TPCEG official announcement are sent to the proponents through email reflector. Contributions can be submitted through mail, mutual visit, and teleconference, and the evaluation results will be discussed with the coordination of ITRI Inc. All evaluation reports will be provided to ITU-R WP5D after being reviewed and confirmed by TPCEG proponents in official meetings. Since October 2017, TPCEG sent liaisons to interested parties for calling study results of IMT-2020 evaluation. With the submissions from proponents, TPCEG issued a call for question, comments, calibration and results, and held a meeting on 2nd December 2019. During the meeting, TPCEG proponents reviewed all the submitted evaluation results and drafted an interim evaluation report.TPCEG representatives also work with other ITU-R Independent Evaluation Groups, and have collaboration meetings since 2017. TPCEG starts to call for participation in ITU-R workshop on IMT-2020 terrestrial radio interfaces, which is held in 4th October, Munich, Germany, and shares its activities and plan with other evaluation groups. TPCEG also invites organizations and academic units in Trans-Pacific region to join our works after the workshop. During the year of 2018, TPCEG have received liaisons from Taiwan Association of Information and Communication Standards (TAICS) with studies and evaluation results for 3GPP (S)RIT proposals. In October 2018, TPCEG also have collaboration with WWRF by sharing evaluation status in WWRF#41 meeting. In 2019, TPCEG exchanges the evaluation activities and plans with 5G-IA, 5GMF, TTA, and WWRF in the 6th Annual 5G Huddle in conjunction with WWRF #42 meeting in Tokyo. In December 2019, TPCEG receives liaison with evaluation study from TAICS. With the additional evaluation results, TPCEG submits an interim evaluation report to ITU-R WP?5D #33.TPCEG continues collaborating with other independent evaluation groups and provide this final evaluation report by updating the research and evaluation results in ITU-R WP?5D #34 meeting. I-DAdministrative Contact DetailsTPCEG ModeratorTzu-Ming Lin (ITRI International Inc.)tmlin@ I-ETechnical Contact DetailsTing-Yu Yeh (Industrial Technology Research Institute, ITRI)tingyuyeh@.twKelvin Chou (MediaTek Inc., MTK)kelvin.chou@Jen-Yi Pan (National Chung-Cheng University, NCCU)jypan@ccu.edu.twKuang-Hao Liu (National Cheng-Kung University, NCKU)khliu@mail.ncku.edu.twHuan-Chun Wang (National Taiwan University of Science and Technology, NTUST)hcwang@mail.ntust.edu.twI-FOther pertinent administrative information.The official website of Trans-Pacific Evaluation Group is overview of Trans-Pacific Evaluation Group is provided in the presentation of Workshop on IMT-2020 terrestrial radio interfaces.The information about the 5G simulator can be found at: , and more details can be found in:I-GStructure of this ReportThis Report is structured according to the proposed structure and consists of 3 Parts:–Part I: Administrative Aspects of Trans-Pacific Evaluation Group–Part II: Technical Aspects of the work in Trans-Pacific Evaluation Group–Part III: ConclusionPart II: Technical aspects of the work of the Independent Evaluation Group:II-AWhat candidate technologies or portions of the candidate technologies this IEG is or might anticipate evaluating?In this report, final results are presented for the 3GPP submissions for IMT-2020, including the LTE and NR component RIT. The evaluation works of analytic, inspection, and simulation are anticipated.It should be noted that other submissions endorsing 3GPP component RITs, e.g. the submissions of Korea, China, and some parts of TSDSI and ETSI/DECT, have been concluded as technically identical to 3GPP submission. With the observations, this evaluation is also valid for the LTE and NR component RITs in those submission.Table II-A.1Summary of evaluation methodologiesCharacteristic for evaluationHigh-level assessment methodEvaluation methodology in this Evaluation ReportRelated section of ReportsITU-R M.2410-0 and ITU-R M.2411-0Peak data rateAnalyticalPart II, II-E.1Report ITU-R M.2410-0, § 4.1Peak spectral efficiencyAnalyticalPart II, II-E.2Report ITU-R M.2410-0, § 4.2User experienced data rateAnalytical for single band and single layer;Simulation for multi-layer Part II, II-E.3Report ITU-R M.2410-0, § 4.35th percentile user spectral efficiencySimulationPart II, II-E.4Report ITU-R M.2410-0, § 4.4Average spectral efficiencySimulation Part II, II-E.5Report ITU-R M.2410-0, § 4.5Area traffic capacityAnalyticalPart II, II-E.6Report ITU-R M.2410-0, § 4.6User plane latencyAnalyticalPart II, II-E.7Report ITU-R M.2410-0, § 4.7.1Control plane latencyAnalyticalPart II, II-E.8Report ITU-R M.2410-0, § 4.7.2Connection densitySimulationPart II, II-E.9Report ITU-R M.2410-0, § 4.8Energy efficiencyInspectionPart II, II-E.10Report ITU-R M.2410-0, § 4.9ReliabilitySimulationPart II, II-E.11Report ITU-R M.2410-0, § 4.10MobilitySimulationPart II, II-E.12Report ITU-R M.2410-0, § 4.11Mobility interruption timeAnalyticalPart II, II-E.13Report ITU-R M.2410-0, § 4.12BandwidthInspectionPart II, II-E.14Report ITU-R M.2410-0, § 4.13Support of wide range of servicesInspectionPart II, II-E.15Report ITU-R M.2411-0, § 3.1Supported spectrum band(s)/range(s)InspectionPart II, II-E.16Report ITU-R M.2411-0, § 3.2II-BConfirmation of utilization of the ITU-R evaluation guidelines in Report ITUR M.2412TPCEG confirms that the evaluation guidelines provided in Report ITU-R M.2412-0 have been utilized.II-CDocumentation of any additional evaluation methodologies that are or might be developed by the Independent Evaluation Group to complement the evaluation guidelinesThe following additional evaluation methodologies have been applied by this Evaluation Group:–Updating of already available link-level and system-level simulators according to the submitted RITs and SRITs as well as to ITU-R requirements.–These link-level and system-level simulators have been calibrated with respect to externally available results.II-DVerification as per Report ITU-R M.2411 of the compliance templates and the self-evaluation for each candidate technology as indicated in A)This final evaluation report is summarizing the available evaluation results by end February 2020. These results confirm most of the self-evaluation of the proponent 3GPP. After the evaluation and study, some issues are observed with comments for specific technical performance metrics. The overall assessments are provided in Part II, II-F.II-EAssessment as per Reports ITU-R M.2410, ITU-R M.2411 and ITU-R M.2412 for each candidate technology as indicated in A)This section contains the evaluation results received from TPCEG proponents, which are reviewed and harmonized in TPCEG meetings and used to summarize the evaluation results for quantitative assessment on 3GPP proposals on LTE RIT and NR RIT. All evaluation results were generated by following the IMT2020 evaluation methodology. Table II-E.1 shows the different sources of the evaluation results correspond to contributors from the different affiliations.Table II-E.1Sources of the evaluation resultsSource 1ITRISource 2MEDIATEKSource 3NCCUSource 4NCKUSource 5NTUSTNote that ITRI, NCCU, NCKU, and NTUST adopt “WiSE” system level simulator to conduct the results while MTK use in-house simulator for the evaluation. The more detail information of WiSE simulator is overviewed in Annex A-4, and all the methodologies, assumption, and configurations are summarized in Annex A-1, A-2 and A-3.In the following sub-sections, details on–Detailed analysis/assessment and evaluation by the IEGs of the compliance templates submitted by the proponents per the Report ITU-R M.2411 section 5.2.4;–Provide any additional comments in the templates along with supporting documentation for such comments;–Analysis of the proponent’s self-evaluation by the IEG;are provided.II-E.1Peak data rateII-E.1.1NR peak data rateBased on the calculation of peak spectral efficiency in Section II-E.2, the analysis of peak data rate for NR and LTE cases are shown in this section. In order to meet the peak data rate requirement of IMT-2020, different bandwidth and SCS combinations require different minimum number of CC.II-E.1.1.1DownlinkThe DL peak data rate for NR is shown in Table II-E.1.5Table II-E.1.5Peak data rate for NR DL casesDuplexingSCS [kHz]Per CC BW (MHz)Peak data rate per CC (Gbit/s)Aggregated peak data rate over 16 CCs (Gbit/s)Required DL bandwidth to meet the requirement (MHz)Req. (Gbit/s)FDDFR115502.401638.425641720301004.860077.76412601004.764676.2336420TDD (DDDSU)FR115501.824929.1984548301003.693659.0976542601003.618257.8912553FR2602005.45387.24873412040010.923174.768733II-E.1.1.2UplinkThe UL peak data rate for NR is shown in Table II-E.1.6.Table II-E.1.6Peak data rate for NR UL casesDuplexingSCS [kHz]Per CC BW (MHz)Peak data rate per CC (Gbit/s)Aggregated peak data rate over 16 CCs (Gbit/s)Required UL bandwidth to meet the requirement (MHz)Req. (Gbit/s)FDDFR115501.237919.806440410301002.503240.0512400601002.475039.6405TDD (DDDSU)*FR115500.26714.27361872301000.548.641852601000.5348.5441873FR2602001.005916.09519881204002.011832.1891988Note: For TDD case, the performance can meet ITU-R requirement with sufficient bandwidth support or adopting full uplink frame structure.II-E.1.2LTE peak data rateII-E.1.2.1DownlinkThe DL peak data rate for LTE is shown in Table II-E.1.7.Table II-E.1.7Peak data rate for LTE DL casesDuplexingPer CC BW (MHz)Peak data rate per CC (Gbit/s)Aggregated peak data rate over 32 CCs (Gbit/s)Req. (Gbit/s)FDD200.887628.420TDD (DDDSU)200.67421.568II-E.1.2.2UplinkThe UL peak data rate for LTE is shown in Table II-E.1.8.Table II-E.1.8Peak data rate for LTE UL casesDuplexingPer CC BW (MHz)Peak data rate per CC (Gbit/s)Aggregated peak data rate over 32 CCs (Gbit/s)Req. (Gbit/s)FDD200.424613.587210TDD (DDDSU)*200.0842.688Note: For TDD case, the performance can meet ITU-R requirement with sufficient bandwidth support or adopting full uplink frame structure.II-E.1.3Assessment of peak data rateWith the investigation and research in this section, TPCEG concluded as followed:–3GPP NR RIT can fulfill the requirement of downlink cases for both FDD and TDD. Besides, uplink cases for both FDD and TDD can also be fulfilled with sufficient bandwidth support or adopting full uplink frame structure.–3GPP LTE RIT can fulfill the requirement of downlink cases for both FDD and TDD. Besides, uplink cases for both FDD and TDD can also be fulfilled with sufficient bandwidth support or adopting full uplink frame structure.II-E.2Peak spectral efficiencyII-E.2.1NR peak spectral efficiencyII-E.2.1.1DownlinkThe peak spectral efficiency for NR in FR1 and FR2 for FDD and TDD are shown in Table II-E.2.1 and II-E-2.2 respectively. For TDD, the DL/UL configurations of DDDSU are evaluated. From the tables, the spectral efficiency of larger bandwidth is larger than that of small bandwidth since the guard band ratio is more efficient with larger bandwidth. Similar reason can be explained for the more spectral efficiency of smaller SCS. Also, it can be seen that NR fulfils the peak spectral efficiency requirements of 30 bits/s/Hz for DL for both FR1 and FR2 and all supported SCS and BW combinations.Table II-E.2.1 Peak spectral efficiency for NR FDD DL casesSCS [kHz]5 MHz10 MHz15 MHz20 MHz25 MHz30 MHz40 MHz50 MHz60 MHz80 MHz90 MHz100 MHzReq.FR11540.574444.347445.733146.425946.841647.118847.914348.0323----303032.383739.076642.685343.598544.933345.229146.497046.898547.765048.174448.410748.59973060-32.383738.223439.218841.355642.780143.669644.990245.875346.981747.350547.645530Table II-E.2.2 Peak spectral efficiency for NR TDD DL cases (DDDSU; αj=0.7643)SCS [kHz]5 MHz10 MHz15 MHz20 MHz25 MHz30 MHz40 MHz50 MHz60 MHz80 MHz90 MHz100 MHzReq.FR11539.963543.871345.339946.074146.514746.808447.622547.7534----303031.852838.562542.224643.170944.542344.866746.166346.588447.465847.892148.133548.32673060-31.852837.751538.746940.907342.347543.263044.616045.524246.659447.037847.340530SCS [kHz]50 MHz100 MHz200 MHz400 MHzReq.FR26034.114635.154235.6740-3012031.823334.335835.264835.729330II-E.2.1.2UplinkThe UL peak spectral efficiency for NR in FR1 and FR2 for FDD and TDD are shown in Table II-E.2.3 and II-E.2.4 respectively. From the tables, it can be seen that NR fulfils the peak spectral efficiency requirements of 15 bits/s/Hz for UL for both FR1 and FR2 and all supported SCS and BW combinations.Table II-E.2.3 Peak spectral efficiency for NR FDD UL casesSCS [kHz]5 MHz10 MHz15 MHz20 MHz25 MHz30 MHz40 MHz50 MHz60 MHz80 MHz90 MHz100 MHzReq.FR11522.858723.811424.129024.287824.38324.446524.755224.757----153020.036021.94123.188123.352823.81823.823224.287824.38324.752324.86924.960025.03221560-20.03621.917821.941522.68923.188123.352823.81824.129024.51724.646424.749915Table II-E.2.4 Peak spectral efficiency for NR TDD UL cases (DDDSU; αj=0.2357)SCS [kHz]5 MHz10 MHz15 MHz20 MHz25 MHz30 MHz40 MHz50 MHz60 MHz80 MHz90 MHz100 MHzReq.FR11520.872321.774422.075122.225422.315622.375822.660922.6640----153018.228320.032421.193721.354421.786821.795122.225422.315622.655722.765922.849322.91601560-18.228319.991020.032420.729221.193721.354421.786822.075122.435422.555522.651615SCS [kHz]50 MHz100 MHz200 MHz400 MHzReq.FR26021.301621.326421.3389-1512020.604821.301621.326421.338915II-E.2.2LTE peak spectral efficiencyII-E.2.2.1DownlinkThe DL peak spectral efficiency for LTE are provided in Table E-2.5. For LTE TDD, the DL/UL configuration DDDSU is evaluated.Table II-E.2.5 Peak spectral efficiency for LTE FDD and TDD DL casesDuplexing15 kHz SCS5 MHz10 MHz15 MHz20 MHzReq. (bit/s/Hz)FDDFR1256QAM43.696044.153144.305544.381730TDD (DDDSU)FR1256QAM43.292043.847544.032744.1253II-E.2.2.2UplinkThe UL peak spectral efficiency for LTE are provided in Table 3-9. For LTE TDD, the DL/UL configuration DDDSU is evaluated.Table II-E.2.6 Peak spectral efficiency for LTE FDD and TDD UL casesDuplexing15 kHz SCS5 MHz10 MHz15 MHz20 MHzReq. (bit/s/Hz)FDDFR1256QAM21.177221.212921.224821.230815TDD (DDDSU)FR1256QAM17.842617.905117.925917.9364II-E.2.3Assessment of peak spectral efficiencyWith the investigation and research in this section, TPCEG concluded as followed:–3GPP NR RIT can fulfill the requirement of downlink and uplink for both FDD and TDD cases. ––3GPP LTE RIT can fulfill the requirement of downlink and uplink for both FDD and TDD cases. II-E.3User experienced data rateII-E.3.1Evaluation for NR and LTE RITsBased on the simulation results of 5th percentile user spectral efficiency in Section II-E.4, the evaluation results of User Experienced Data Rate for LTE and NR in Dense Urban-eMBB test environments are analysed and shown in Table II-E.3.1 to Table II-E.3.4. Note that the values in brackets denote the required bandwidth for achieving the data rate.Note that more detailed information can be found in Annex A-3.Table II-E.3.1Evaluation Result of Dense Urban – eMBB (Configuration A, Downlink)TXRU mappingTx schemeNumerologyDuplexingITRI -LTEITRI -NRMTK -NRNCCU - NRNCKU - NRNTUST - NRgNB: 16T = (8,8,2,1,1;1,8)UE: 2R=(1,1,2,1,1;1,1)SU-MIMO Type I Codebook15kHz SCSFDD101.35839 (210M)gNB: 16T = (8,8,2,1,1;1,8)UE: 4R=(1,2,2,1,1;1,2)SU-MIMO Type I Codebook15kHz SCSFDD101.557 (200M)gNB: 32T = (8,16,2,1,1;1,16)UE: 4R=(1,2,2,1,1;1,2)SU-MIMO Type I Codebook15kHz SCSFDD104.50132 (220M)gNB: 32T = (8,8,2,1,1;2,8)UE: 2R=(1,1,2,1,1;1,1)SU-MIMO Type I Codebook15kHz SCSFDD101.55904 (440M)gNB: 32T = (8,8,2,1,1;2,8)UE: 4R = (1,2,2,1,1; 1,2)MU-MIMO Type I Codebook15kHz SCSFDD103.25952 (210M)gNB: 32T = (8,8,2,1,1;2,8)UE: 4R = (1,2,2,1,1; 1,2)SU-MIMO Class A Codebook15kHz SCSFDD101.51196 (440M)gNB: 32T = (8,8,2,1,1;2,8)UE: 4R = (1,2,2,1,1; 1,2)SU-MIMO Type I Codebook15kHz SCSFDD103.32495 (270M)101.0672 (260M)103.691 (200M)101.6 (200M)gNB: 32T = (8,8,2,1,1;2,8)UE: 4R = (1,2,2,1,1; 1,2)SU-MIMO Class A Codebook15kHz SCSTDD,DDDSU100.6927252 (440M)gNB: 32T = (8,8,2,1,1;2,8)UE: 4R = (1,2,2,1,1; 1,2)SU-MIMO Non-codebook based15kHz SCSTDD,DDDSU101.0720002 (320M)100.7775 (290M)Table II-E.3.2Evaluation Result of Dense Urban – eMBB (Configuration A, Uplink)TXRU mappingTx schemeNumerologyDuplexingITRI -LTEITRI -NRMTK-NRNCCU - NRNCKU - NRNTUST - NRgNB: 16R = (8,8,2,1,1;1,8)UE: 2T=(1,1,2,1,1;1,1)SU-MIMO Type I Codebook15kHz SCSFDD52.30995 (110M)gNB: 16R = (8,8,2,1,1;1,8)UE: 4T=(1,2,2,1,1;1,2)SU-MIMO Type I Codebook15kHz SCSFDD52.53193 (110M)gNB: 32R = (8,16,2,1,1;1,16)UE: 4T=(1,2,2,1,1;1,2)SU-MIMO Type I Codebook15kHz SCSFDD54.79496 (110M)gNB: 32R = (8,8,2,1,1;2,8)UE: 2T=(1,1,2,1,1;1,1)SU-MIMO Type I Codebook15kHz SCSFDD52.56262 (110M)gNB: 32R = (8,8,2,1,1;2,8)UE: 4T = (1,2,2,1,1; 1,2)SU-MIMO LTE 4Tx Codebook15kHz SCSFDD52.53525 (150M)gNB: 32R = (8,8,2,1,1;2,8)UE: 4T = (1,2,2,1,1; 1,2)SU-MIMO Type I Codebook15kHz SCSFDD50.21679 (130M)50.67132 (140M)53.73434 (110M)gNB: 32R = (8,8,2,1,1;2,8)UE: 4T = (1,2,2,1,1; 1,2)SU-MIMO LTE 4Tx Codebook15kHz SCSTDD,DDDSU50.6963877 (600M)gNB: 32R = (8,8,2,1,1;2,8)UE: 4T = (1,2,2,1,1; 1,2)SU-MIMO Type I Codebook15kHz SCSTDD,DDDSU50.7655049 (530M)50.6044500 (550M)gNB: 32R = (8,8,2,1,1;2,8)UE: 4T=(1,2,2,1,1;1,2)SU-MIMOType I Codebook15kHz SCSTDD,DDDSU50.112699 (690M)Table II-E.3.3Evaluation Result of Dense Urban – eMBB (Configuration B, Downlink)TXRU mappingTx schemeNumerologyDuplexingITRI -LTEITRI -NRMTK-NRNCCU - NRNCKU - NRNTUST - NRgNB: 32T = (8,8,2,1,1;4,4)UE: 4R=(1,2,2,1,1;1,2)SU-MIMO Type I Codebook60kHz SCS FDD101.52205 (350M)gNB: 8T = (4,8,2,2,2;1,1)UE: 2R=(2,4,2,1,2;1,1)SU-MIMO Type I Codebook60kHz SCS FDD102.16152 (360M)gNB: 8T = (4,8,2,2,2; 1,1)UE: 4R = (2,4,2,1,2; 1,2)SU-MIMO Non-codebook based60kHz SCS TDDDDDSU100.0176343 (5120M)100.091209282 (3140M)100.0219952 (3680M)Table II-E.3.4Evaluation Result of Dense Urban – eMBB (Configuration B, Uplink)TXRU mappingTx schemeNumerologyDuplexingITRI -LTEITRI -NRMTK-NRNCCU - NRNCKU - NRNTUST - NRgNB: 32R = (8,8,2,1,1;4,4)UE: 4T=(1,2,2,1,1;1,2)SU-MIMO Type I Codebook 60kHz SCS, FDD50.53374 (180M)gNB: 8R = (4,8,2,2,2;1,1)UE: 2T=(2,4,2,1,2;1,1)SU-MIMO Type I Codebook 60kHz SCS, FDD50.69447 (190M)gNB: 8R = (4,8,2,2,2; 1,1)UE: 4T = (2,4,2,1,2; 1,2)SU-MIMO Type I Codebook60kHz SCS TDDDDDSU50.00826876 (13270M)50.034859266 (12970M)50.0233118 (8140M)II-E.3.2Assessment of user experienced data rateWith the investigation and research in this section, TPCEG concluded as followed:?3GPP NR RIT can fulfill the requirement for all the cases of Dense Urban test environment when sufficient bandwidth is adopted. ?3GPP NR RIT can fulfill the requirement for the cases with configuration A of Dense Urban test environment when sufficient bandwidth is adopted. Table II-E.3.5Assessment of User Experienced Data RateTest EnvironmentConfigurationLTENRDense UrbanA (4GHz)Downlink◎◎Uplink◎◎B (30GHz)Downlink－◎Uplink－◎◎ : Fulfill　　　○ : Fulfill with aggressive configurations　　　※ : Issue FoundedII-E.45th percentile user spectral efficiencyII-E.4.1Evaluation for NR and LTE RITsBased on the configuration and assumption in Annex A-2, the technical performance of 5th User Spectral Efficiency for LTE and NR in Indoor Hotspot-eMBB, Dense Urban-eMBB, and Rural-eMBB test environment are evaluated and shown in Table II-E.4.1 to Table II-E.4.16. In order to investigate and verify the technical performance of LTE and NR RIT, different combinations of 3GPP features, i.e. MIMO schemes, are evaluated.Note that more detailed information can be found in Annex A-3.Table II-E.4.1 Evaluation Result of Indoor Hotspot – eMBB (Configuration A, Downlink)Antenna ConfigurationTXRU mappingTx schemeNumerologyDuplexingITRI -LTEITRI -NRMTK-NRNCCU - NRNCKU - NRNTUST - NR12 TRPgNB: 32T = (4,4,2,1,1;4,4)UE: 2R=(1,1,2,1,1;1,1)SU-MIMO,Type I codebook15kHzFDD0.44478312 TRPgNB: 32T= (4,4,2,1,1;4,4)UE:2R=(1,1,2,1,1;1,1)MU-MIMO, Type II Codebook15kHzFDD0.3312 TRPgNB: 32T= (4,4,2,1,1;4,4)UE:4R=(1,2,2,1,1;1,2)MU-MIMO,Type I codebook15kHzFDD0.45639912 TRPgNB: 32T= (4,4,2,1,1;4,4)UE:4R=(1,2,2,1,1;1,2)SU-MIMO ClassA Codebook15kHzFDD0.21544112 TRPgNB: 32T= (4,4,2,1,1;4,4)UE:4R=(1,2,2,1,1;1,2)SU-MIMO,Type I codebook15kHzFDD0.3146940.3390.4599020.31136 TRPgNB: 32T = (8,16,2,1,1;2,8)UE: 2R=(1,1,2,1,1;1,1)SU-MIMO,Type I codebook15kHzFDD0.5216836 TRPgNB: 32T = (8,16,2,1,1;2,8)UE:4R =(1,2,2,1,1;1,2)MU-MIMO,Type I codebook15kHzFDD0.56073636 TRPgNB: 32T = (8,16,2,1,1;2,8)UE:4R =(1,2,2,1,1;1,2)SU-MIMO ClassA Codebook15kHzFDD0.27619436 TRPgNB: 32T = (8,16,2,1,1;2,8)UE:4R =(1,2,2,1,1;1,2)SU-MIMO,Type I codebook15kHzFDD0.3832910.35150.50717112 TRPgNB: 32T= (4,4,2,1,1;4,4)UE:4R=(1,2,2,1,1;1,2)SU-MIMO ClassA Codebook15kHzTDD,DDDSU0.19942512 TRPgNB: 32T= (4,4,2,1,1;4,4)UE:4R=(1,2,2,1,1;1,2)SU-MIMO,Non-codebook based15kHzTDD,DDDSU0.4425290.31112 TRPgNB: 32T= (4,4,2,1,1;4,4)UE:4R=(1,2,2,1,1;1,2)SU-MIMO,Non-codebook based30kHzTDD,DDDSU0.33236 TRPgNB: 32T = (8,16,2,1,1;2,8)UE:4R =(1,2,2,1,1;1,2)SU-MIMO,Non-codebook based15kHzTDD,DDDSU0.4803730.42136 TRPgNB: 32T = (8,16,2,1,1;2,8)UE:4R =(1,2,2,1,1;1,2)SU-MIMO ClassA Codebook15kHzTDD,DDDSU0.349816Table II-E.4.2 Evaluation Result of Indoor Hotspot – eMBB (Configuration A, Uplink)Antenna ConfigurationTXRU mappingTx schemeNumerologyDuplexingITRI -LTEITRI -NRMTK-NRNCCU - NRNCKU - NRNTUST - NR12 TRPgNB: 32R = (4,4,2,1,1;2,4)UE: 2T=(1,1,2,1,1;1,1)SU-MIMO,Type I codebook15kHzFDD0.5712 TRPgNB: 32R = (4,4,2,1,1;4,4)UE: 2T=(1,1,2,1,1;1,1)SU-MIMO,Type I codebook15kHzFDD0.44572812 TRPgNB: 32R= (4,4,2,1,1;4,4)UE:4T=(1,2,2,1,1;1,2)SU-MIMO LTE 4Tx Codebook15kHzFDD0.2102812 TRPgNB: 32R= (4,4,2,1,1;4,4)UE:4T=(1,2,2,1,1;1,2)SU-MIMO,Type I codebook15kHzFDD0.2807930.220.4544210.19636 TRPgNB: 32R = (8,16,2,1,1;2,8)UE:4T =(1,2,2,1,1;1,2)SU-MIMO,Type I codebook15kHzFDD0.2933540.2870.48099836 TRPgNB: 32R= (8,16,2,1,1;2,8)UE: 2T=(1,1,2,1,1;1,1)SU-MIMO,Type I codebook15kHzFDD0.48210436 TRPgNB: 32R = (8,16,2,1,1;2,8)UE:4T =(1,2,2,1,1;1,2)SU-MIMO LTE 4Tx Codebook15kHzFDD0.25335812 TRPgNB: 32R = (4,4,2,1,1;4,4)UE:4T=(1,2,2,1,1;1,2)SU-MIMO,Type I codebook15kHzTDD,DDDSU0.3293370.21412 TRPgNB: 32R = (4,4,2,1,1;4,4)UE:4T=(1,2,2,1,1;1,2)SU-MIMO LTE 4Tx Codebook15kHzTDD,DDDSU0.20545436 TRPgNB: 32R = (8,16,2,1,1;2,8)UE:4T =(1,2,2,1,1;1,2)SU-MIMO,Type I codebook15kHzTDD,DDDSU0.282540.28636 TRPgNB: 32R = (8,16,2,1,1;2,8)UE:4T =(1,2,2,1,1;1,2)SU-MIMO LTE 4Tx Codebook15kHzTDD,DDDSU0.19720412 TRPgNB: 32R = (4,4,2,1,1;4,4)UE:4T=(1,2,2,1,1;1,2)SU-MIMO,Type I codebook30kHzTDD,DDDSU0.249Table II-E.4.3 Evaluation Result of Indoor Hotspot – eMBB (Configuration B, Downlink)Antenna ConfigurationTXRU mappingTx schemeNumerologyDuplexingITRI-NRMTK-NRNCCU - NRNCKU - NRNTUST - NR12 TRPgNB: 32T = (4,4,2,1,1;4,4)UE: 4R=(1,2,2,1,1;1,2)SU-MIMO Type I Codebook60kHZ SCSFDD0.36119712 TRPgNB: 32T = (4,4,2,1,1;4,4)UE: 4R=(4,4,2,1,1;1,2)SU-MIMO Type I Codebook60kHZ SCSFDD0.34272812 TRPgNB: 32T = (4,4,2,1,1;4,4)UE: 8R=(2,4,2,1,2;1,2)MU-MIMO Type II Codebook60kHZ SCSFDD0.40812 TRPgNB: 8T = (16,8,2,1,1;2,2)UE: 4R=(1,2,2,1,1;1,2)SU-MIMO Type I Codebook60kHZ SCSFDD0.33645436 TRPgNB: 32T = (8,16,2,1,1;2,8)UE: 4R=(1,2,2,1,1;1,2)SU-MIMO Type I Codebook60kHZ SCSFDD0.33445412 TRP gNB: 8T= (4,8,2,1,1;2,2)UE: 4R=(2,4,2,1,2; 1,1)SU-MIMONon-Codebook based60kHZ SCSTDD,DDDSU0.59912 TRPgNB: 32T= (4,4,2,1,1;4,4)UE: 8R= (2,4,2,1,2; 1,2)SU-MIMO Non-codebook based60kHZ SCSTDD,DDDSU0.6144840.4817712 TRPgNB: 32T= (8,8,2,1,1;4,4)UE: 8R= (2,4,2,1,2; 1,2)SU-MIMO Non-codebook based60kHZ SCSTDD,DDDSU0.78053736 TRPgNB: 32T= (4,4,2,1,1;4,4)UE: 8R= (2,4,2,1,2; 1,2)SU-MIMO Non-codebook based60kHZ SCSTDD,DDDSU0.536184Table II-E.4.4Evaluation Result of Indoor Hotspot – eMBB (Configuration B, Uplink)Antenna ConfigurationTXRU mappingTx schemeNumerologyDuplexingITRI-NRMTK-NRNCCU - NRNCKU - NRNTUST- NR12 TRPgNB: 32R = (4,4,2,1,1;4,4)UE: 4T=(1,2,2,1,1;1,2)SU-MIMO Type I Codebook60kHZ SCSFDD0.27833312 TRPgNB: 32R = (4,4,2,1,1;4,4)UE: 4T=(4,4,2,1,1;1,2)SU-MIMO Type I Codebook60kHZ SCSFDD0.26214412 TRPgNB: 32R = (4,4,2,1,1;4,4)UE: 8T=(2,4,2,1,2;1,2)SU-MIMO Type I Codebook60kHZ SCSFDD0.40512 TRPgNB: 8R = (16,8,2,1,1;2,2)UE: 4T=(1,2,2,1,1;1,2)SU-MIMO Type I Codebook60kHZ SCSFDD0.29046436 TRPgNB: 32R = (8,16,2,1,1;2,8)UE: 4T=(1,2,2,1,1;1,2)SU-MIMO Type I Codebook60kHZ SCSFDD0.27633912 TRP gNB: 8T= (4,8,2,1,1;2,2)UE: 4R=(2,4,2,1,2; 1,1)SU-MIMONon-Codebook based60kHZ SCSTDD,DDDSU0.19612 TRPgNB: 32R= (4,4,2,1,1;4,4)UE: 4T= (2,4,2,1,1; 1,2)SU-MIMO Type I Codebook60kHZ SCSTDD,DDDSU0.3644560.29928512 TRPgNB: 32R= (4,4,2,1,1;4,4)UE: 4T= (2,4,2,1,2; 1,2)SU-MIMO Type I Codebook60kHZ SCSTDD,DDDSU0.3614140.33636 TRPgNB: 32R= (4,4,2,1,1;4,4)UE: 4T= (2,4,2,1,1; 1,3)SU-MIMO Type I Codebook60kHZ SCSTDD,DDDSU0.317430.329224Table II-E.4.5Evaluation Result of Indoor Hotspot – eMBB (Configuration C, Downlink)Antenna ConfigurationTXRU mappingTx schemeNumerologyDuplexingITRI- NRMTK-NRNCCU - NRNCKU - NRNTUST - NR12 TRPgNB: 32T = (8,16,2,1,1;4,4)UE: 4R=(2,4,2,1,2;1,2) SU-MIMO Type I Codebook60kHZ SCSFDD0.42481412 TRPgNB: 32T= (4,4,2,1,1;4,4)UE: 8R= (2,4,2,1,2; 1,2) MU-MIMO Type II Codebook60kHZ SCSFDD0.47112 TRPgNB: 8T = (8,16,2,1,1;2,2)UE: 2R=(2,4,2,1,1;1,1) SU-MIMO Type I Codebook60kHZ SCSFDD0.3997212 TRPgNB: 32T= (4,4,2,1,1;4,4)UE: 8R= (2,4,2,1,2; 1,2)SU-MIMO Type I Codebook60kHZ SCSTDD,DDDSU0.8440940.599692?12 TRPgNB: 32T= (8,16,2,1,1;4,4)UE: 8R= (2,4,2,1,2; 1,2)SU-MIMO Type I Codebook60kHZ SCSTDD,DDDSU0.790012?12 TRPgNB: 8T = (4,16,2,1,1;4,4)UE: 4R = (2,4,2,1,2; 1,1)SU-MIMONon-codebook based60kHZ SCSTDD,DDDSU0.60536 TRPgNB: 32T= (4,4,2,1,1;4,4)UE: 8R= (2,4,2,1,2; 1,2)SU-MIMO Type I Codebook60kHZ SCSTDD,DDDSU0.824964Table II-E.4.6 Evaluation Result of Indoor Hotspot – eMBB (Configuration C, Uplink)Antenna ConfigurationTXRU mappingTx schemeNumerologyDuplexingITRI-NRMTK-NRNCCU - NRNCKU - NRNTUST - NR12 TRPgNB: 32R = (8,16,2,1,1;4,4)UE: 4T=(2,4,2,1,2;1,2) SU-MIMO Type I Codebook60kHZ SCSFDD0.36408912 TRPgNB: 8R = (8,16,2,1,1;2,2)UE: 2T=(2,4,2,1,1;1,1) SU-MIMO Type I Codebook60kHZ SCSFDD0.37248912 TRPgNB: 32R= (4,4,2,1,1;4,4)UE: 4T= (2,4,2,1,1; 1,2)SU-MIMO Type I Codebook60kHZ SCSTDD,DDDSU0.33452612 TRPgNB: 32R= (4,4,2,1,1;4,4)UE: 8T= (2,4,2,1,2; 1,2)SU-MIMO Type I Codebook60kHZ SCSTDD,DDDSU0.39744212 TRPgNB: 32R= (8,16,2,1,1;4,4)UE: 8T= (2,4,2,1,2; 1,2)SU-MIMO Type I Codebook60kHZ SCSTDD,DDDSU0.470.35712 TRPgNB: 8R = (4,16,2,1,1;4,4)UE: 4T = (2,4,2,1,2; 1,1)SU-MIMONon-codebook based60kHZ SCSTDD,DDDSU?0.12936 TRPgNB: 32R= (4,4,2,1,1;4,4)UE: 4T= (2,4,2,1,1; 1,3)SU-MIMO Type I Codebook60kHZ SCSTDD,DDDSU0.414448?Table II-E.4.7 Evaluation Result of Dense Urban – eMBB (Configuration A, Downlink)TXRU mappingTx schemeNumerologyDuplexingITRI -LTEITRI -NRMTK-NRNCCU - NRNCKU - NRNTUST - NRgNB: 16T = (8,8,2,1,1;1,8)UE: 4R=(1,2,2,1,1;1,2)SU-MIMO Type I Codebook15kHz SCSFDD0.482659gNB: 32T = (8,16,2,1,1;1,16)UE: 4R=(1,2,2,1,1;1,2)SU-MIMO Type I Codebook15kHz SCSFDD0.507785gNB: 32T = (8,8,2,1,1;2,8)UE: 2R=(1,1,2,1,1;1,1)SU-MIMO Type I Codebook15kHz SCSFDD0.475006gNB: 32T = (8,8,2,1,1;2,8)UE: 4R = (1,2,2,1,1; 1,2)MU-MIMO Type I Codebook15kHz SCSFDD0.230816gNB: 32T = (8,8,2,1,1;2,8)UE: 4R = (1,2,2,1,1; 1,2)SU-MIMO Class A Codebook15kHz SCSFDD0.230709?gNB: 32T = (8,8,2,1,1;2,8)UE: 4R = (1,2,2,1,1; 1,2)SU-MIMO Type I Codebook15kHz SCSFDD0.491712gNB: 32T = (8,8,2,1,1;2,8)UE: 4R = (1,2,2,1,1; 1,2)SU-MIMO Type I Codebook15kHz SCSFDD0.3826850.388720.5184550.508gNB: 32T = (8,8,2,1,1;2,8)UE: 4R= (1,2,2,1,1; 1,2)MU-MIMO, Type II Codebook15kHz SCSFDD0.4?gNB: 32T = (8,8,2,1,1;2,8)UE: 4R = (1,2,2,1,1; 1,2)SU-MIMO Class A Codebook15kHz SCSTDD,DDDSU0.302268gNB: 32T = (8,8,2,1,1;2,8)UE: 4R = (1,2,2,1,1; 1,2)SU-MIMO Non-codebook based15kHz SCSTDD,DDDSU0.4171840.459Table II-E.4.8 Evaluation Result of Dense Urban – eMBB (Configuration A, Uplink)TXRU mappingTx schemeNumerologyDuplexingITRI -LTEITRI -NRMTK-NRNCCU - NRNCKU - NRNTUST - NRgNB : 16R = (8,8,2,1,1;1,8);UE : 2T = (1,1,2,1,1; 1,1)SU-MIMO Type I Codebook15kHz SCSFDD0.490.475545gNB: 16R = (8,8,2,1,1;1,8)UE: 4T=(1,2,2,1,1;1,2)SU-MIMO Type I Codebook15kHz SCSFDD0.477563gNB: 32R = (8,16,2,1,1;1,16)UE: 4T=(1,2,2,1,1;1,2)SU-MIMO Type I Codebook15kHz SCSFDD0.498136gNB: 32R = (8,8,2,1,1;2,8)UE: 2T=(1,1,2,1,1;1,1)SU-MIMO Type I Codebook15kHz SCSFDD0.477842gNB: 32R = (8,8,2,1,1;2,8)UE: 4T = (1,2,2,1,1; 1,2)SU-MIMO LTE 4Tx Codebook15kHz SCSFDD0.350235?gNB: 32R = (8,8,2,1,1;2,8)UE: 4T = (1,2,2,1,1; 1,2)SU-MIMO Type I Codebook15kHz SCSFDD0.3862830.361938?0.488494gNB: 32R = (8,8,2,1,1;2,8)UE: 4T = (1,2,2,1,1; 1,2)SU-MIMO LTE 4Tx Codebook15kHz SCSTDD,DDDSU0.347855?gNB: 32R = (8,8,2,1,1;2,8)UE: 4T = (1,2,2,1,1; 1,2)SU-MIMO Type I Codebook15kHz SCSTDD,DDDSU0.3943350.37879gNB: 32R = (8,8,2,1,1;2,8)UE: 4T=(1,2,2,1,1;1,2)SU-MIMOType I Codebook15kHz SCSTDD,DDDSU0.299Table II-E.4.9 Evaluation Result of Dense Urban – eMBB (Configuration B, Downlink)TXRU mappingTx schemeNumerologyDuplexingITRI -LTEITRI -NRMTK-NRNCCU - NRNCKU - NRNTUST - NRgNB: 8T = (4,8,2,2,2; 1,1)UE: 4R = (2,4,2,1,2; 1,2)SU-MIMO Non-codebook based60kHz SCS TDDDDDSU0.0258020.0421030.0359Table II-E.4.10Evaluation Result of Dense Urban – eMBB (Configuration B, Uplink)TXRU mappingTx schemeNumerologyDuplexingITRI -LTEITRI -NRMTK-NRNCCU - NRNCKU - NRNTUST - NRgNB: 8R = (4,8,2,2,2; 1,1)UE: 4T = (2,4,2,1,2; 1,2)SU-MIMO Type I Codebook60kHz SCS TDDDDDSU0.01551470.0158820.0253Table II-E.4.11Evaluation Result of Rural– eMBB (Configuration A, Downlink)TXRU mappingTx schemeNumerologyDuplexingITRI-LTEITRI-NRMTK-NRNCCU - NRNCKU - NRNTUST- NRgNB : 8T = (8,4,2,1,1;1,4);UE : 2R = (1,1,2,1,1; 1,1)MU-MIMO,Type II Codebook15kHz SCSFDD0.128gNB : 8T = (8,4,2,1,1;1,4);UE : 2R = (1,1,2,1,1; 1,1)MU-MIMO Type I Codebook15kHz,SCSFDD0.492289gNB : 8T = (8,4,2,1,1;1,4);UE : 2R = (1,1,2,1,1; 1,1)SU-MIMO Class A Codebook15kHz,SCSFDD0.275462gNB : 8T = (8,4,2,1,1;1,4);UE : 2R = (1,1,2,1,1; 1,1)SU-MIMO Type I Codebook15kHz,SCSFDD0.1702570.495195gNB: 16T = (8,4,2,1,1;2,4)UE: 1R=(1,1,1,1,1;1,1)SU-MIMO Type I Codebook15kHz,SCSFDD0.489989gNB: 16T = (8,4,2,1,1;2,4)UE: 2R=(1,1,2,1,1;1,1)SU-MIMO Type I Codebook15kHz,SCSFDD0.50473gNB: 16T = (8,4,2,1,1;2,4)UE: 4R=(1,2,2,1,1;1,2)SU-MIMO Type I Codebook15kHz,SCSFDD0.3870170.494gNB: 8T = (16,8,2,1,1;2,2)UE: 1R=(1,1,1,1,1;1,1)SU-MIMO Type I Codebook15kHz,SCSFDD0.538422gNB: 8T = (8,4,2,1,1;1,4)UE: 4R=(1,2,2,1,1;1,2)SU-MIMO Type I Codebook15kHz,SCSFDD0.524gNB : 16T = (8,4,2,1,1;2,4);UE : 4R = (1,2,2,1,1; 1,2)SU-MIMONon-Codebook based15kHz SCSTDD,DDDSU0.423533gNB : 8T = (8,4,2,1,1;1,4);UE : 2R = (1,1,2,1,1; 1,1)SU-MIMO Non-Codebook15kHz SCSTDD,DDDSU0.1654270.4798gNB : 8T = (8,4,2,1,1;1,4);UE : 2R = (1,1,2,1,1; 1,1)SU-MIMOClass A Codebook15kHz,SCSTDD,DDDSU0.323954Table II-E.4.12 Evaluation Result of Rural– eMBB (Configuration A, Uplink)TXRU mappingTx schemeNumerologyDuplexingITRI-LTEITRI-NRMTK-NRNCCU - NRNCKU - NRNTUST- NRgNB : 8R = (8,4,2,1,1;1,4);UE : 1T = (1,1,1,1,1; 1,1)SU-MIMO Type I Codebook15kHz SCSFDD0.224gNB : 16R = (8,4,2,1,1;2,4);UE : 4T = (1,2,2,1,1; 1,2)SU-MIMO LTE 2Tx Codebook15kHz,SCSFDD0.290422?gNB : 8R = (8,4,2,1,1;1,4);UE : 2T = (1,1,2,1,1; 1,1)SU-MIMO Type I Codebook15kHz,SCSFDD0.0709360.482104gNB: 16R = (8,4,2,1,1;2,4)UE: 1T=(1,1,1,1,1;1,1)SU-MIMO Type I Codebook15kHz,SCSFDD0.465gNB: 16R = (8,4,2,1,1;2,4)UE: 2T=(1,1,2,1,1;1,1)SU-MIMO Type I Codebook15kHz,SCSFDD0.532272gNB: 16R = (8,4,2,1,1;2,4)UE: 4T=(1,2,2,1,1;1,2)SU-MIMO Type I Codebook15kHz,SCSFDD0.3058260.553gNB: 8R = (16,8,2,1,1;2,2)UE: 1T=(1,1,1,1,1;1,1)SU-MIMO Type I Codebook15kHz,SCSFDD0.470741gNB: 8R = (8,4,2,1,1;1,4)UE: 4T=(1,2,2,1,1;1,2)SU-MIMO Type I Codebook15kHz,SCSFDD0.482gNB : 16R = (8,4,2,1,1;2,4);UE : 4T = (1,2,2,1,1; 1,2)SU-MIMO Type I Codebook15kHz SCSTDD,DDDSU0.30115gNB : 8R = (8,4,2,1,1;1,4);UE : 2T = (1,1,2,1,1; 1,1)SU-MIMO Type I Codebook15kHz SCSTDD,DDDSU0.0718380.070992gNB : 16R = (8,4,2,1,1;2,4);UE : 4T = (1,2,2,1,1; 1,2)SU-MIMOLTE 2Tx Codebook15kHz,SCSTDD,DDDSU0.305628Table II-E.4.13 Evaluation Result of Rural– eMBB (Configuration B, Downlink)TXRU mappingTx schemeNumerologyDuplexingITRI-LTEITRI-NRMTK-NRNCCU - NRNCKU - NRNTUST- NRgNB: 32T = (8,16,2,1,1;1,16)UE: 4R=(1,2,2,1,1;1,2)SU-MIMO Type I Codebook15kHz SCSFDD0.4277710.4282370.520385gNB: 32T = (8,8,2,1,1;2,8)UE: 2R=(1,1,2,1,1;1,1)SU-MIMO Type I Codebook15kHz SCSFDD0.532272gNB: 32T = (8,8,2,1,1;2,8)UE: 4R = (1,2,2,1,1; 1,2)SU-MIMO Class A Codebook15kHz SCSFDD0.292282?gNB: 32T = (8,8,2,1,1;2,8)UE: 4R = (1,2,2,1,1; 1,2)SU-MIMO Class A Codebook15kHz SCS TDD,DDDSU0.3256528?gNB: 32T = (8,8,2,1,1;2,8)UE: 4R = (1,2,2,1,1; 1,2)SU-MIMO Non-Codebook15kHz SCS TDD,DDDSU0.4160910.4458380.417Table II-E.4.14 Evaluation Result of Rural– eMBB (Configuration B, Uplink)TXRU mappingTx schemeNumerologyDuplexingITRI-LTEITRI-NRMTK-NRNCCU - NRNCKU - NRNTUST- NRgNB: 32R = (8,16,2,1,1;1,16)UE: 4T=(1,2,2,1,1;1,2)SU-MIMO Type I Codebook15kHz SCSFDD0.532948gNB: 32R = (8,8,2,1,1;2,8)UE: 2T=(1,1,2,1,1;1,1)SU-MIMO Type I Codebook15kHz SCSFDD0.525459gNB: 32R = (8,8,2,1,1;2,8)UE: 4T = (1,2,2,1,1; 1,2)SU-MIMO Type I Codebook 15kHz SCSFDD0.1708090.0977864gNB: 32R = (8,8,2,1,1;2,8)UE: 4T = (1,2,2,1,1; 1,2)SU-MIMOLTE 4Tx Codebook15kHz SCSFDD0.176055gNB: 32R = (8,8,2,1,1;2,8)UE: 4T = (1,2,2,1,1; 1,2)SU-MIMO Type I Codebook 15kHz SCS TDD,DDDSU0.141680.1132040.153gNB: 32R = (8,8,2,1,1;2,8)UE: 4T = (1,2,2,1,1; 1,2)SU-MIMOLTE 4Tx Codebook15kHz SCS TDD,DDDSU0.15916Table II-E.4.15Evaluation Result of Rural– eMBB (Configuration C, Downlink)TXRU mappingTx schemeNumerologyDuplexingITRI-LTEITRI-NRMTK-NRNCCU - NRNCKU - NRNTUST - NRgNB: 8T = (8,4,2,1,1;1,4);UE: 4R = (1,2,2,1,1; 1,2)MU-MIMO, Type II codebook15 kHz SCSFDD0.12gNB: 16T = (8,4,2,1,1;2,4)UE: 1R=(1,1,1,1,1;1,1)SU-MIMO Type I Codebook15kHz,SCSFDD0.552609gNB: 16T = (8,4,2,1,1;2,4)UE: 2R=(1,1,2,1,1;1,1)SU-MIMO Type I Codebook15kHz,SCSFDD0.462947gNB: 16T = (8,4,2,1,1;2,4)UE: 4R=(1,2,2,1,1;1,2)MU-MIMO Type I Codebook15kHz,SCSFDD0.49344gNB: 16T = (8,4,2,1,1;2,4)UE: 4R=(1,2,2,1,1;1,2)SU-MIMO Type I Codebook15kHz,SCSFDD0.504123gNB: 8T = (8,4,2,1,1;1,4)UE: 1R=(1,1,1,1,1;1,1)SU-MIMO Type I Codebook15kHz,SCSFDD0.530253gNB: 8T = (8,4,2,1,1;1,4)UE: 2R=(1,1,2,1,1;1,1)SU-MIMO Type I Codebook15kHz,SCSFDD0.47127gNB: 8T = (8,4,2,1,1;1,4);UE: 4R = (1,2,2,1,1; 1,2)MU-MIMO Type I Codebook15kHz,SCSFDD0.503518gNB: 8T = (8,4,2,1,1;1,4);UE: 4R = (1,2,2,1,1; 1,2)SU-MIMO Class A Codebook15kHz,SCSFDD0.275619gNB: 8T = (8,4,2,1,1;1,4);UE: 4R = (1,2,2,1,1; 1,2)SU-MIMO Type I Codebook15kHz,SCSFDD0.3687170.4020.502312gNB: 8T = (8,4,2,1,1;1,4);UE: 4R = (1,2,2,1,1; 1,2)SU-MIMO Non-Codebook15kHz SCS TDD,DDDSU0.4202980.4070.261gNB: 8T = (8,4,2,1,1;1,4);UE: 4R = (1,2,2,1,1; 1,2)SU-MIMO Class A Codebook15kHz,SCSTDD,DDDSU0.330157Table II-E.4.16Evaluation Result of Rural– eMBB (Configuration C, Uplink)TXRU mappingTx schemeNumerologyDuplexingITRI-LTEITRI-NRMTK-NRNCCU - NRNCKU - NRNTUST - NRgNB: 16R = (8,4,2,1,1;2,4)UE: 1T=(1,1,1,1,1;1,1)SU-MIMO Type I Codebook15kHz SCS FDD0.461928gNB: 16R = (8,4,2,1,1;2,4)UE: 2T=(1,1,2,1,1;1,1)SU-MIMO Type I Codebook15kHz SCS FDD0.455903gNB: 16R = (8,4,2,1,1;2,4)UE: 4T=(1,2,2,1,1;1,2)SU-MIMO Type I Codebook15kHz SCS FDD0.460913gNB: 8R = (8,4,2,1,1;1,4)UE: 1T=(1,1,1,1,1;1,1)SU-MIMO Type I Codebook15kHz SCS FDD0.0960.460407gNB: 8R = (8,4,2,1,1;1,4)UE: 2T=(1,1,2,1,1;1,1)SU-MIMO Type I Codebook15kHz SCS FDD0.4534638gNB: 8R = (8,4,2,1,1;1,4);UE: 4T = (1,2,2,1,1; 1,2)SU-MIMO Type I Codebook15kHz SCS FDD0.2459490.2170.452949gNB: 8R = (8,4,2,1,1;1,4);UE: 4T = (1,2,2,1,1; 1,2)SU-MIMO LTE 4Tx Codebook15kHz,SCSFDD0.231291gNB: 8R = (8,4,2,1,1;1,4);UE: 4T = (1,2,2,1,1; 1,2)SU-MIMO Type I Codebook15kHz SCS TDD,DDDSU0.2394430.2394430.117gNB: 8R = (8,4,2,1,1;1,4);UE: 4T = (1,2,2,1,1; 1,2)SU-MIMO LTE 4Tx Codebook15kHz,SCSTDD,DDDSU0.252252II-E.4.2Assessment of 5th percentile user spectral efficiencyWith the investigation and research in this section, TPCEG concluded as followed:?3GPP NR RIT can fulfill the requirement with the configuration cases in all Indoor Hotspot, all Rural, and partial of Dense Urban test environments. For the case of configuration B in Dense Urban test environment, there are performance issues found.?3GPP LTE RIT can fulfill the requirement with the configuration cases in all Rural and partial of Dense Urban test environments. For configuration A case in Indoor Hotpot test environment, LTE RIT can still fulfill the requirement with aggressive configurations.Table II-E.4.17Assessment of User Experienced Data RateTest EnvironmentConfigurationLTENRIndoor HotspotA (4GHz)Downlink○◎Uplink○◎B (30GHz)Downlink－◎Uplink－◎C (70GHz)Downlink－◎Uplink－◎Dense UrbanA (4GHz)Downlink◎◎Uplink◎◎B (30GHz)Downlink－※(1)Uplink－※(1)RuralA (4GHz)Downlink◎◎Uplink◎◎B (30GHz)Downlink－◎Uplink－◎C (700MHz)Downlink◎◎Uplink◎◎◎ : Fulfill　　　○ : Fulfill with aggressive configurations　　　※ : Issue FoundedNote 1: Base on the self-Evaluation from 3GPP, NR RIT can still fulfil the requirement if the penetration loss condition changed from “20% high loss, 80% low loss” to “100% low loss.”II-E.5Average spectral efficiencyII-E.5.1Evaluation for NR and LTE RITsBased on the configuration and assumption in Annex A-2, the technical performance of Average Spectral Efficiency for LTE and NR in Indoor Hotspot-eMBB, Dense Urban-eMBB, and Rural-eMBB test environment are shown in Table II-E.5.1 to Table II-E.5.16. In order to investigate and verify the technical performance of LTE and NR RIT, different combinations of 3GPP features, i.e. MIMO schemes, are evaluated.Note that more detailed information can be found in Annex A-3.Table II-E.5.1 Evaluation Result of Indoor Hotspot – eMBB (Configuration A, Downlink)Antenna ConfigurationTXRU mappingTx schemeNumerologyDuplexingITRI -LTEITRI -NRMTK-NRNCCU - NRNCKU - NRNTUST - NR12 TRPgNB: 32T = (4,4,2,1,1;4,4)UE: 2R=(1,1,2,1,1;1,1)SU-MIMO,Type I codebook15kHzFDD7.5778212 TRPgNB: 32T= (4,4,2,1,1;4,4)UE:2R=(1,1,2,1,1;1,1)MU-MIMO, Type II Codebook15kHzFDD11.1212 TRPgNB: 32T= (4,4,2,1,1;4,4)UE:4R=(1,2,2,1,1;1,2)MU-MIMO,Type I codebook15kHzFDD10.850112 TRPgNB: 32T= (4,4,2,1,1;4,4)UE:4R=(1,2,2,1,1;1,2)SU-MIMO ClassA Codebook15kHzFDD7.0490812 TRPgNB: 32T= (4,4,2,1,1;4,4)UE:4R=(1,2,2,1,1;1,2)SU-MIMO,Type I codebook15kHzFDD9.861510.348.58879.2336 TRPgNB: 32T = (8,16,2,1,1;2,8)UE: 2R=(1,1,2,1,1;1,1)SU-MIMO,Type I codebook15kHzFDD10.067936 TRPgNB: 32T = (8,16,2,1,1;2,8)UE:4R =(1,2,2,1,1;1,2)MU-MIMO,Type I codebook15kHzFDD11.131936 TRPgNB: 32T = (8,16,2,1,1;2,8)UE:4R =(1,2,2,1,1;1,2)SU-MIMO ClassA Codebook15kHzFDD8.4056636 TRPgNB: 32T = (8,16,2,1,1;2,8)UE:4R =(1,2,2,1,1;1,2)SU-MIMO,Type I codebook15kHzFDD11.378511.34411.164712 TRPgNB: 32T= (4,4,2,1,1;4,4)UE:4R=(1,2,2,1,1;1,2)SU-MIMO ClassA Codebook15kHzTDD,DDDSU7.9854212 TRPgNB: 32T= (4,4,2,1,1;4,4)UE:4R=(1,2,2,1,1;1,2)SU-MIMO,Non-codebook based15kHzTDD,DDDSU11.347411.86412 TRPgNB: 32T= (4,4,2,1,1;4,4)UE:4R=(1,2,2,1,1;1,2)SU-MIMO,Non-codebook based30kHzTDD,DDDSU10.45736 TRPgNB: 32T = (8,16,2,1,1;2,8)UE:4R =(1,2,2,1,1;1,2)SU-MIMO,Non-codebook based15kHzTDD,DDDSU12.660813.01736 TRPgNB: 32T = (8,16,2,1,1;2,8)UE:4R =(1,2,2,1,1;1,2)SU-MIMO ClassA Codebook15kHzTDD,DDDSU9.12108Table II-E.5.2 Evaluation Result of Indoor Hotspot – eMBB (Configuration A, Uplink)Antenna ConfigurationTXRU mappingTx schemeNumerologyDuplexingITRI -LTEITRI -NRMTK-NRNCCU - NRNCKU - NRNTUST - NR12 TRPgNB: 32R = (4,4,2,1,1;2,4)UE: 2T=(1,1,2,1,1;1,1)SU-MIMO,Type I codebook15kHzFDD8.5612 TRPgNB: 32R = (4,4,2,1,1;4,4)UE: 2T=(1,1,2,1,1;1,1)SU-MIMO,Type I codebook15kHzFDD6.0450512 TRPgNB: 32R= (4,4,2,1,1;4,4)UE:4T=(1,2,2,1,1;1,2)SU-MIMO LTE 4Tx Codebook15kHzFDD6.656912 TRPgNB: 32R= (4,4,2,1,1;4,4)UE:4T=(1,2,2,1,1;1,2)SU-MIMO,Type I codebook15kHzFDD7.676098.26.854537.53136 TRPgNB: 32R = (8,16,2,1,1;2,8)UE: 2T=(1,1,2,1,1;1,1)SU-MIMO,Type I codebook15kHzFDD9.2735236 TRPgNB: 32R = (8,16,2,1,1;2,8)UE:4T =(1,2,2,1,1;1,2)SU-MIMO,Type I codebook15kHzFDD9.270429.4539.99292436 TRPgNB: 32R = (8,16,2,1,1;2,8)UE:4T =(1,2,2,1,1;1,2)SU-MIMO LTE 4Tx Codebook15kHzFDD7.1770612 TRPgNB: 32R = (4,4,2,1,1;4,4)UE:4T=(1,2,2,1,1;1,2)SU-MIMO,Type I codebook15kHzTDD,DDDSU7.445667.40512 TRPgNB: 32R = (4,4,2,1,1;4,4)UE:4T=(1,2,2,1,1;1,2)SU-MIMO LTE 4Tx Codebook15kHzTDD,DDDSU6.506812 TRPgNB: 32R = (4,4,2,1,1;4,4)UE:4T=(1,2,2,1,1;1,2)SU-MIMO,Type I codebook30kHzTDD,DDDSU8.68636 TRPgNB: 32R = (8,16,2,1,1;2,8)UE:4T =(1,2,2,1,1;1,2)SU-MIMO,Type I codebook15kHzTDD,DDDSU7.827278.82736 TRPgNB: 32R = (8,16,2,1,1;2,8)UE:4T =(1,2,2,1,1;1,2)SU-MIMO LTE 4Tx Codebook15kHzTDD,DDDSU6.1286Table II-E.5.3Evaluation Result of Indoor Hotspot – eMBB (Configuration B, Downlink)Antenna ConfigurationTXRU mappingTx schemeNumerologyDuplexingITRI-NRMTK-NRNCCU - NRNCKU - NRNTUST - NR12 TRPgNB: 32T = (4,4,2,1,1;4,4)UE: 4R=(1,2,2,1,1;1,2)SU-MIMO Type I Codebook60kHZ SCSFDD8.5685712 TRPgNB: 32T = (4,4,2,1,1;4,4)UE: 4R=(4,4,2,1,1;1,2)SU-MIMO Type I Codebook60kHZ SCSFDD8.4497112 TRPgNB: 32T = (4,4,2,1,1;4,4)UE: 8R=(2,4,2,1,2;1,2)MU-MIMO Type II Codebook60kHZ SCSFDD12.6912 TRPgNB: 8T = (16,8,2,1,1;2,2)UE: 4R=(1,2,2,1,1;1,2)SU-MIMO Type I Codebook60kHZ SCSFDD10.210536 TRPgNB: 32T = (8,16,2,1,1;2,8)UE: 4R=(1,2,2,1,1;1,2)SU-MIMO Type I Codebook60kHZ SCSFDD8.88070612 TRP gNB: 8T= (4,8,2,1,1;2,2)UE: 4R=(2,4,2,1,2; 1,1)SU-MIMO Non-codebook based60kHZ SCSTDD,DDDSU11.6612 TRPgNB: 32T= (4,4,2,1,1;4,4)UE: 8R= (2,4,2,1,2; 1,2)SU-MIMO Non-codebook based60kHZ SCSTDD,DDDSU13.876913.254712 TRPgNB: 32T= (8,8,2,1,1;4,4)UE: 8R= (2,4,2,1,2; 1,2)SU-MIMO Non-codebook based60kHZ SCSTDD,DDDSU16.709136 TRPgNB: 32T= (4,4,2,1,1;4,4)UE: 8R= (2,4,2,1,2; 1,2)SU-MIMO Non-codebook based60kHZ SCSTDD,DDDSU12.4368Table II-E.5.4Evaluation Result of Indoor Hotspot – eMBB (Configuration B, Uplink)Antenna ConfigurationTXRU mappingTx schemeNumerologyDuplexingITRI-NRMTK-NRNCCU - NRNCKU - NRNTUST-NR12 TRPgNB: 32R = (4,4,2,1,1;4,4)UE: 4T=(1,2,2,1,1;1,2)SU-MIMO Type I Codebook60kHZ SCSFDD7.6087212 TRPgNB: 32R = (4,4,2,1,1;4,4)UE: 4T=(4,4,2,1,1;1,2)SU-MIMO Type I Codebook60kHZ SCSFDD6.9356812 TRPgNB: 32R = (4,4,2,1,1;4,4)UE: 8T=(2,4,2,1,2;1,2)SU-MIMO Type I Codebook60kHZ SCSFDD10.1712 TRPgNB: 8R = (16,8,2,1,1;2,2)UE: 4T=(1,2,2,1,1;1,2)SU-MIMO Type I Codebook60kHZ SCSFDD8.7012836 TRPgNB: 32R = (8,16,2,1,1;2,8)UE: 4T=(1,2,2,1,1;1,2)SU-MIMO Type I Codebook60kHZ SCSFDD8.3450912 TRP gNB: 8T= (4,8,2,1,1;2,2)UE: 4R=(2,4,2,1,2; 1,1)SU-MIMONon-Codebook based60kHZ SCSTDD,DDDSU5.19912 TRPgNB: 32R= (4,4,2,1,1;4,4)UE: 4T= (2,4,2,1,1; 1,2)SU-MIMO Type I Codebook60kHZ SCSTDD,DDDSU10.41959.957612TRPgNB: 32R= (8,8,2,1,1;4,4)UE: 8T= (2,4,2,1,2; 1,2)SU-MIMO Type I Codebook60kHZ SCSTDD,DDDSU9.5798936 TRPgNB: 32R= (4,4,2,1,1;4,4)UE: 4T= (2,4,2,1,1; 1,3)SU-MIMO Type I Codebook60kHZ SCSTDD,DDDSU9.415879.684198.89Table II-E.5.5Evaluation Result of Indoor Hotspot – eMBB (Configuration C, Downlink)Antenna ConfigurationTXRU mappingTx schemeNumerologyDuplexingITRI- NRMTK-NRNCCU - NRNCKU - NRNTUST - NR12 TRPgNB: 32T = (8,16,2,1,1;4,4)UE: 4R=(2,4,2,1,2;1,2) SU-MIMO Type I Codebook60kHZ SCSFDD15.323212 TRPgNB: 32T= (4,4,2,1,1;4,4)UE: 8R= (2,4,2,1,2; 1,2) MU-MIMO Type II Codebook60kHZ SCSFDD12.86912 TRPgNB: 8T = (8,16,2,1,1;2,2)UE: 2R=(2,4,2,1,1;1,1) SU-MIMO Type I Codebook60kHZ SCSFDD11.742612 TRPgNB: 32T= (4,4,2,1,1;4,4)UE: 8R= (2,4,2,1,2; 1,2)SU-MIMO Non-codebook based60kHZ SCSTDD,DDDSU16.834214.051812 TRPgNB: 32T= (8,16,2,1,1;4,4)UE: 8R= (2,4,2,1,2; 1,2)SU-MIMO Non-codebook based60kHZ SCSTDD,DDDSU16.644112 TRPgNB: 8T = (4,16,2,1,1;4,4)UE: 4R = (2,4,2,1,2; 1,1)SU-MIMONon-codebook based60kHZ SCSTDD,DDDSU11.54836 TRPgNB: 32T= (4,4,2,1,1;4,4)UE: 8R= (2,4,2,1,2; 1,2)SU-MIMO Non-codebook based60kHZ SCSTDD,DDDSU18.2067Table II-E.5.6Evaluation Result of Indoor Hotspot – eMBB (Configuration C, Uplink)Antenna ConfigurationTXRU mappingTx schemeNumerologyDuplexingITRI-NRMTK-NRNCCU - NRNCKU - NRNTUST - NR12 TRPgNB: 32R = (8,16,2,1,1;4,4)UE: 4T=(2,4,2,1,2;1,2) SU-MIMO Type I Codebook60kHZ SCSFDD12.361412 TRPgNB: 8R = (8,16,2,1,1;2,2)UE: 2T=(2,4,2,1,1;1,1) SU-MIMO Type I Codebook60kHZ SCSFDD11.863612 TRPgNB: 32R= (4,4,2,1,1;4,4)UE: 4T= (2,4,2,1,1; 1,2)SU-MIMO Type I Codebook60kHZ SCSTDD,DDDSU11.354512 TRPgNB: 32R= (4,4,2,1,1;4,4)UE: 8T= (2,4,2,1,1; 1,2)SU-MIMO Type I Codebook60kHZ SCSTDD,DDDSU10.12712 TRPgNB: 32R= (8,16,2,1,1;4,4)UE: 8T= (2,4,2,1,2; 1,2)SU-MIMO Type I Codebook60kHZ SCSTDD,DDDSU11.438?11.3612 TRPgNB: 8R = (4,16,2,1,1;4,4)UE: 4T = (2,4,2,1,2; 1,1)SU-MIMONon-codebook based60kHZ SCSTDD,DDDSU?4.70336 TRPgNB: 32R= (4,4,2,1,1;4,4)UE: 4T= (2,4,2,1,1; 1,3)SU-MIMO Type I Codebook60kHZ SCSTDD,DDDSU11.6149Table II-E.5.7Evaluation Result of Dense Urban – eMBB (Configuration A, Downlink)TXRU mappingTx schemeNumerologyDuplexingITRI-LTEITRI-NRMTK-NRNCCU - NRNCKU - NRNTUST- NRgNB: 16T = (8,8,2,1,1;1,8)UE: 2R=(1,1,2,1,1;1,1)SU-MIMO Type I Codebook15kHz SCSFDD8.40802gNB: 16T = (8,8,2,1,1;1,8)UE: 4R=(1,2,2,1,1;1,2)SU-MIMO Type I Codebook15kHz SCSFDD11.326gNB: 32T = (8,16,2,1,1;1,16)UE: 4R=(1,2,2,1,1;1,2)SU-MIMO Type I Codebook15kHz SCSFDD12.362gNB: 32T = (8,8,2,1,1;2,8)UE: 2R=(1,1,2,1,1;1,1)SU-MIMO Type I Codebook15kHz SCSFDD9.26461gNB: 32T = (8,8,2,1,1;2,8)UE: 4R = (1,2,2,1,1; 1,2)MU-MIMO Type I Codebook15kHz SCSFDD13.2295gNB: 32T = (8,8,2,1,1;2,8)UE: 4R = (1,2,2,1,1; 1,2)SU-MIMO Class A Codebook15kHz SCSFDD8.94097?gNB: 32T = (8,8,2,1,1;2,8)UE: 4R = (1,2,2,1,1; 1,2)SU-MIMO Type I Codebook15kHz SCSFDD13.632913.906612.634114.233gNB: 32T = (8,8,2,1,1;2,8)UE: 4R= (1,2,2,1,1; 1,2)MU-MIMO, Type II Codebook15kHz SCSFDD11.39?gNB: 32T = (8,8,2,1,1;2,8)UE: 4R = (1,2,2,1,1; 1,2)SU-MIMO Class A Codebook15kHz SCSTDD,DDDSU10.564gNB: 32T = (8,8,2,1,1;2,8)UE: 4R = (1,2,2,1,1; 1,2)SU-MIMO Non-codebook based15kHz SCSTDD,DDDSU15.243315.767Table II-E.5.8Evaluation Result of Dense Urban Rural – eMBB (Configuration A, Uplink)TXRU mappingTx schemeNumerologyDuplexingITRI-LTEITRI-NRMTK-NRNCCU - NRNCKU - NRNTUST- NRgNB : 16R = (8,8,2,1,1;1,8);UE : 2T = (1,1,2,1,1; 1,1)SU-MIMO Type I Codebook15kHz SCSFDD8.536.41486gNB: 16R = (8,8,2,1,1;1,8)UE: 4T=(1,2,2,1,1;1,2)SU-MIMO Type I Codebook15kHz SCSFDD7.36996gNB: 32R = (8,16,2,1,1;1,16)UE: 4T=(1,2,2,1,1;1,2)SU-MIMO Type I Codebook15kHz SCSFDD9.08383gNB: 32R = (8,8,2,1,1;2,8)UE: 2T=(1,1,2,1,1;1,1)SU-MIMO Type I Codebook15kHz SCSFDD7.97483gNB: 32R = (8,8,2,1,1;2,8)UE: 4T = (1,2,2,1,1; 1,2)SU-MIMO LTE 4Tx Codebook15kHz SCSFDD9.53707gNB: 32R = (8,8,2,1,1;2,8)UE: 4T = (1,2,2,1,1; 1,2)SU-MIMO Type I Codebook15kHz SCSFDD11.720911.25819.66735gNB: 32R = (8,8,2,1,1;2,8)UE: 4T = (1,2,2,1,1; 1,2)SU-MIMO LTE 4Tx Codebook15kHz SCSTDD,DDDSU9.76821gNB: 32R = (8,8,2,1,1;2,8)UE: 4T = (1,2,2,1,1; 1,2)SU-MIMO Type I Codebook15kHz SCSTDD,DDDSU10.978910.306gNB: 32R = (8,8,2,1,1;2,8)UE: 4T=(1,2,2,1,1;1,2)SU-MIMOType I Codebook15kHz SCSTDD,DDDSU8.354Table II-E.5.9Evaluation Result of Dense Urban – eMBB (Configuration B, Downlink)TXRU mappingTx schemeNumerologyDuplexingITRI-NRMTK-NRNCCU - NRNCKU - NRNTUST- NRgNB: 32T = (8,8,2,1,1;4,4)UE: 4R=(1,2,2,1,1;1,2)SU-MIMO Type I Codebook60kHz SCS FDD9.19746gNB: 8T = (4,8,2,2,2;1,1)UE: 2R=(2,4,2,1,2;1,1)SU-MIMO Type I Codebook60kHz SCS FDD8.67726gNB: 8T = (4,8,2,2,2; 1,1)UE: 4R = (2,4,2,1,2; 1,2)SU-MIMO Non-codebook based60kHz SCS TDDDDDSU9.183516.70917.9372Table II-E.5.10Evaluation Result of Dense Urban – eMBB (Configuration B, Uplink)TXRU mappingTx schemeNumerologyDuplexingITRI-NRMTK-NRNCCU - NRNCKU - NRNTUST- NRgNB: 32R = (8,8,2,1,1;4,4)UE: 4T=(1,2,2,1,1;1,2)SU-MIMO Type I Codebook 60kHz SCS, FDD5.73887gNB: 8R = (4,8,2,2,2;1,1)UE: 2T=(2,4,2,1,2;1,1)SU-MIMO Type I Codebook 60kHz SCS, FDD6.88379gNB: 8R = (4,8,2,2,2; 1,1)UE: 4T = (2,4,2,1,2; 1,2)SU-MIMO Type I Codebook60kHz SCS TDDDDDSU7.501727.044526.063Table II-E.5.11Evaluation Result of Rural – eMBB (Configuration A, Downlink)TXRU mappingTx schemeNumerologyDuplexingITRI-LTEITRI-NRMTK-NRNCCU - NRNCKU - NRNTUST- NRgNB : 8T = (8,4,2,1,1;1,4);UE : 2R = (1,1,2,1,1; 1,1)MU-MIMO,Type II Codebook15kHz SCSFDD5.64gNB : 16T = (8,4,2,1,1;2,4);UE : 4R = (1,2,2,1,1; 1,2)SU-MIMO Class A Codebook15kHz,SCSFDD10.4004gNB : 8T = (8,4,2,1,1;1,4);UE : 2R = (1,1,2,1,1; 1,1)MU-MIMO Type I Codebook15kHz,SCSFDD9.18912gNB : 8T = (8,4,2,1,1;1,4);UE : 2R = (1,1,2,1,1; 1,1)SU-MIMO Type I Codebook15kHz,SCSFDD9.401088.98573gNB: 16T = (8,4,2,1,1;2,4)UE: 1R=(1,1,1,1,1;1,1)SU-MIMO Type I Codebook15kHz,SCSFDD5.19901gNB: 16T = (8,4,2,1,1;2,4)UE: 2R=(1,1,2,1,1;1,1)SU-MIMO Type I Codebook15kHz,SCSFDD9.87647gNB: 16T = (8,4,2,1,1;2,4)UE: 4R=(1,2,2,1,1;1,2)SU-MIMO Type I Codebook15kHz,SCSFDD14.91719.36gNB: 8T = (16,8,2,1,1;2,2)UE: 1R=(1,1,1,1,1;1,1)SU-MIMO Type I Codebook15kHz,SCSFDD5.02025gNB: 8T = (8,4,2,1,1;1,4)UE: 4R=(1,2,2,1,1;1,2)SU-MIMO Type I Codebook15kHz,SCSFDD8.02gNB : 8T = (8,4,2,1,1;1,4);UE : 2R = (1,1,2,1,1; 1,1)SU-MIMO Non-Codebook15kHz SCSTDD,DDDSU9.8799411.6014gNB : 16T = (8,4,2,1,1;2,4);UE : 4R = (1,2,2,1,1; 1,2)SU-MIMOClass A Codebook15kHz,SCSTDD,DDDSU11.5833gNB: 16T = (8,4,2,1,1;2,4)UE: 4R=(1,2,2,1,1;1,2)SU-MIMO Type I Codebook15kHz,SCSTDD,DDDSU16.2195Table II-E.5.12Evaluation Result of Rural – eMBB (Configuration A, Uplink)TXRU mappingTx schemeNumerologyDuplexingITRI-LTEITRI-NRMTK -NRNCCU - NRNCKU - NRNTUST- NRgNB : 8R = (8,4,2,1,1;1,4);UE : 1T = (1,1,1,1,1; 1,1)SU-MIMO Type I Codebook15kHz SCSFDD4.5gNB : 16R = (8,4,2,1,1;2,4);UE : 4T = (1,2,2,1,1; 1,2)SU-MIMO LTE 2Tx Codebook15kHz,SCSFDD9.3021?gNB : 8R = (8,4,2,1,1;1,4);UE : 2T = (1,1,2,1,1; 1,1)SU-MIMO Type I Codebook15kHz,SCSFDD9.041728.62443gNB: 16R = (8,4,2,1,1;2,4)UE: 1T=(1,1,1,1,1;1,1)SU-MIMO Type I Codebook15kHz,SCSFDD5.67638gNB: 16R = (8,4,2,1,1;2,4)UE: 2T=(1,1,2,1,1;1,1)SU-MIMO Type I Codebook15kHz,SCSFDD10.1495gNB: 16R = (8,4,2,1,1;2,4)UE: 4T=(1,2,2,1,1;1,2)SU-MIMO Type I Codebook15kHz,SCSFDD11.837310.4gNB: 8R = (16,8,2,1,1;2,2)UE: 1T=(1,1,1,1,1;1,1)SU-MIMO Type I Codebook15kHz,SCSFDD5.5952gNB: 8R = (8,4,2,1,1;1,4)UE: 4T=(1,2,2,1,1;1,2)SU-MIMO Type I Codebook15kHz,SCSFDD8.82gNB : 16R = (8,4,2,1,1;2,4);UE : 4T = (1,2,2,1,1; 1,2)SU-MIMO Type I Codebook15kHz SCSTDD,DDDSU11.8337gNB : 8R = (8,4,2,1,1;1,4);UE : 2T = (1,1,2,1,1; 1,1)SU-MIMO Type I Codebook15kHz SCSTDD,DDDSU8.38696gNB : 16R = (8,4,2,1,1;2,4);UE : 4T = (1,2,2,1,1; 1,2)SU-MIMOLTE 2Tx Codebook15kHz,SCSTDD,DDDSU9.806357.215Table II-E.5.13 Evaluation Result of Rural – eMBB (Configuration B, Downlink)TXRU mappingTx schemeNumerologyDuplexingITRI-LTEITRI-NRMTK-NRNCCU - NRNCKU - NRNTUST - NRgNB: 32T = (8,16,2,1,1;1,16)UE: 4R=(1,2,2,1,1;1,2)SU-MIMO Type I Codebook15kHz SCSFDD14.691214.98713.7512gNB: 32T = (8,8,2,1,1;2,8)UE: 2R=(1,1,2,1,1;1,1)SU-MIMO Type I Codebook15kHz SCSFDD14.2035gNB: 32T = (8,8,2,1,1;2,8)UE: 4R = (1,2,2,1,1; 1,2)SU-MIMO Class A Codebook15kHz SCSFDD10.0495?gNB: 32T = (8,8,2,1,1;2,8)UE: 4R = (1,2,2,1,1; 1,2)SU-MIMO Class A Codebook15kHz SCS TDD,DDDSU10.838?gNB: 32T = (8,8,2,1,1;2,8)UE: 4R = (1,2,2,1,1; 1,2)SU-MIMO Non-Codebook15kHz SCS TDD,DDDSU15.559215.896915.495Table II-E.5.14 Evaluation Result of Rural – eMBB (Configuration B, Uplink)TXRU mappingTx schemeNumerologyDuplexingITRI-LTEITRI-NRMTK-NRNCCU - NRNCKU - NRNTUST - NRgNB: 32R = (8,16,2,1,1;1,16)UE: 4T=(1,2,2,1,1;1,2)SU-MIMO Type I Codebook15kHz SCSFDD11.2257gNB: 32R = (8,8,2,1,1;2,8)UE: 2T=(1,1,2,1,1;1,1)SU-MIMO Type I Codebook15kHz SCSFDD11.7435gNB: 32R = (8,8,2,1,1;2,8)UE: 4T = (1,2,2,1,1; 1,2)SU-MIMO Type I Codebook 15kHz SCSFDD13.209610.4989gNB: 32R = (8,8,2,1,1;2,8)UE: 4T = (1,2,2,1,1; 1,2)SU-MIMOLTE 4Tx Codebook15kHz SCSFDD10.2188gNB: 32R = (8,8,2,1,1;2,8)UE: 4T = (1,2,2,1,1; 1,2)SU-MIMO Type I Codebook 15kHz SCS TDD,DDDSU12.69639.913899.721gNB: 32R = (8,8,2,1,1;2,8)UE: 4T = (1,2,2,1,1; 1,2)SU-MIMOLTE 4Tx Codebook15kHz SCS TDD,DDDSU10.4111Table II-E.5.15Evaluation Result of Rural – eMBB (Configuration C, Downlink)TXRU mappingTx schemeNumerologyDuplexingITRI-LTEITRI-NRMTK-NRNCCU - NRNCKU - NRNTUST - NRgNB: 8T = (8,4,2,1,1;1,4);UE: 4R = (1,2,2,1,1; 1,2)MU-MIMO, Type II codebook15 kHz SCSFDD8.11gNB: 16T = (8,4,2,1,1;2,4)UE: 1R=(1,1,1,1,1;1,1)SU-MIMO Type I Codebook15kHz,SCSFDD5.28185gNB: 16T = (8,4,2,1,1;2,4)UE: 2R=(1,1,2,1,1;1,1)SU-MIMO Type I Codebook15kHz,SCSFDD9.73906gNB: 16T = (8,4,2,1,1;2,4)UE: 4R=(1,2,2,1,1;1,2)MU-MIMO Type I Codebook15kHz,SCSFDD14.3168gNB: 16T = (8,4,2,1,1;2,4)UE: 4R=(1,2,2,1,1;1,2)SU-MIMO Type I Codebook15kHz,SCSFDD14.1458gNB: 8T = (8,4,2,1,1;1,4)UE: 1R=(1,1,1,1,1;1,1)SU-MIMO Type I Codebook15kHz,SCSFDD5.26592gNB: 8T = (8,4,2,1,1;1,4)UE: 2R=(1,1,2,1,1;1,1)SU-MIMO Type I Codebook15kHz,SCSFDD9.24839gNB: 8T = (8,4,2,1,1;1,4);UE: 4R = (1,2,2,1,1; 1,2)MU-MIMO Type I Codebook15kHz,SCSFDD13.5597gNB: 8T = (8,4,2,1,1;1,4);UE: 4R = (1,2,2,1,1; 1,2)SU-MIMO Class A Codebook15kHz,SCSFDD10.0217gNB: 8T = (8,4,2,1,1;1,4);UE: 4R = (1,2,2,1,1; 1,2)SU-MIMO Type I Codebook15kHz,SCSFDD14.656615.141913.0369gNB: 8T = (8,4,2,1,1;1,4);UE: 4R = (1,2,2,1,1; 1,2)SU-MIMO Non-Codebook15kHz SCS TDD,DDDSU15.594115.937611.493gNB: 8T = (8,4,2,1,1;1,4);UE: 4R = (1,2,2,1,1; 1,2)SU-MIMO Class A Codebook15kHz,SCSTDD,DDDSU10.9934Table II-E.5.16 Evaluation Result of Rural – eMBB (Configuration C, Uplink)TXRU mappingTx schemeNumerologyDuplexingITRI-LTEITRI-NRMTK-NRNCCU - NRNCKU - NRNTUST - NRgNB: 16R = (8,4,2,1,1;2,4)UE: 1T=(1,1,1,1,1;1,1)SU-MIMO Type I Codebook15kHz SCS FDD4.46738gNB: 16R = (8,4,2,1,1;2,4)UE: 2T=(1,1,2,1,1;1,1)SU-MIMO Type I Codebook15kHz SCS FDD6.38119gNB: 16R = (8,4,2,1,1;2,4)UE: 4T=(1,2,2,1,1;1,2)SU-MIMO Type I Codebook15kHz SCS FDD7.5349gNB: 8R = (8,4,2,1,1;1,4)UE: 1T=(1,1,1,1,1;1,1)SU-MIMO Type I Codebook15kHz SCS FDD4.063.88578gNB: 8R = (8,4,2,1,1;1,4)UE: 2T=(1,1,2,1,1;1,1)SU-MIMO Type I Codebook15kHz SCS FDD4.89954gNB: 8R = (8,4,2,1,1;1,4);UE: 4T = (1,2,2,1,1; 1,2)SU-MIMO Type I Codebook15kHz SCS FDD6.47146.455.89071gNB: 8R = (8,4,2,1,1;1,4);UE: 4T = (1,2,2,1,1; 1,2)SU-MIMO LTE 4Tx Codebook15kHz,SCSFDD5.4062gNB: 8R = (8,4,2,1,1;1,4);UE: 4T = (1,2,2,1,1; 1,2)SU-MIMO Type I Codebook15kHz SCS TDD,DDDSU6.100676.100675.52gNB: 8R = (8,4,2,1,1;1,4);UE: 4T = (1,2,2,1,1; 1,2)SU-MIMO LTE 4Tx Codebook15kHz,SCSTDD,DDDSU5.6875II-E.5.2Assessment of average spectral efficiencyWith the investigation and research in this section, TPCEG concluded as followed:–3GPP NR RIT can fulfill the requirement with the configuration cases in all Indoor Hotspot, all Dense Urban, and all Rural test environments. –3GPP LTE RIT can fulfill the requirement with the configuration cases in partial Dense Urban, and all Rural test environments. For configuration A case in Indoor Hotpot test environment, LTE RIT can still fulfill the requirement with aggressive configurations.Table II-E.5.17Assessment of User Experienced Data RateTest EnvironmentConfigurationLTENRIndoor HotspotA (4GHz)Downlink○◎Uplink○◎B (30GHz)Downlink－◎Uplink－◎C (70GHz)Downlink－◎Uplink－◎Dense UrbanA (4GHz)Downlink◎◎Uplink◎◎B (30GHz)Downlink－◎Uplink－◎RuralA (4GHz)Downlink◎◎Uplink◎◎B (30GHz)Downlink◎◎Uplink◎◎C (700MHz)Downlink◎◎Uplink◎◎◎ : Fulfill　　　○ : Fulfill with aggressive configurations　　　※ : Issue FoundedII-E.6Area traffic capacityII-E.6.1Evaluation for NR and LTE RITsBased on the simulation results of average spectral efficiency in Section II-E.5, the technical performance of Area Traffic Capacity for LTE and NR in Indoor Hotspot-eMBB test environments are analysed and shown in Table II-E.6.1 to Table II-E.6.3. Note that the values in brackets denote the required bandwidth to achieve the capacity.Note that more detailed information can be found in Annex A-3.Table II-E.6.1 Evaluation Result of Indoor Hotspot– eMBB (Configuration A, Downlink)Antenna ConfigurationTXRU mappingTx schemeNumerologyDuplexingITRI -LTEITRI -NRMTK-NRNCCU - NRNCKU - NRNTUST - NR12TRPgNB: 32T = (4,4,2,1,1;4,4)UE: 2R=(1,1,2,1,1;1,1)SU-MIMO,Type I codebook15kHzFDD10.0027224 (660M)12TRPgNB: 32T= (4,4,2,1,1;4,4)UE:4R=(1,2,2,1,1;1,2)MU-MIMO,Type I codebook15kHzFDD10.199094 (470M)12TRPgNB: 32T= (4,4,2,1,1;4,4)UE:4R=(1,2,2,1,1;1,2)SU-MIMO ClassA Codebook15kHzFDD10.009693 (710M)12TRPgNB: 32T= (4,4,2,1,1;4,4)UE:4R=(1,2,2,1,1;1,2)SU-MIMO,Type I codebook15kHzFDD10.05873 (510M)10.1332 (490M)10.134666 (590M)10.153 (550M)36TRPgNB: 32T = (8,16,2,1,1;2,8)UE: 2R=(1,1,2,1,1;1,1)SU-MIMO,Type I codebook15kHzFDD10.269258 (170M)36TRPgNB: 32T = (8,16,2,1,1;2,8)UE:4R =(1,2,2,1,1;1,2)MU-MIMO,Type I codebook15kHzFDD10.01871 (150M)36TRPgNB: 32T = (8,16,2,1,1;2,8)UE:4R =(1,2,2,1,1;1,2)SU-MIMO ClassA Codebook15kHzFDD10.086792 (200M)36TRPgNB: 32T = (8,16,2,1,1;2,8)UE:4R =(1,2,2,1,1;1,2)SU-MIMO,Type I codebook15kHzFDD10.24065 (150M)10.2096 (150M)10.04823 (150M)12TRPgNB: 32T= (4,4,2,1,1;4,4)UE:4R=(1,2,2,1,1;1,2)SU-MIMO ClassA Codebook15kHzTDD,DDDSU10.035964 (830M)12TRPgNB: 32T= (4,4,2,1,1;4,4)UE:4R=(1,2,2,1,1;1,2)SU-MIMO,Non-codebook based15kHzTDD,DDDSU10.137517 (590M)10.0601(560M)36 TRPgNB: 32T = (8,16,2,1,1;2,8)UE:4R =(1,2,2,1,1;1,2)SU-MIMO,Non-codebook based15kHzTDD,DDDSU10.352331 (180M)10.0522 (170M)36TRPgNB: 32T = (8,16,2,1,1;2,8)UE:4R =(1,2,2,1,1;1,2)SU-MIMO ClassA Codebook15kHzTDD,DDDSU10.358354 (250M)12TRPgNB: 32T= (4,4,2,1,1;4,4)UE:4R=(1,2,2,1,1;1,2)SU-MIMO,Non-codebook based30kHzTDD,DDDSU10.1337(640M)Table II-E.6.2Evaluation Result of Indoor Hotspot– eMBB (Configuration B, Downlink)Antenna ConfigurationTXRU mappingTx schemeNumerologyDuplexingITRI -LTEITRI -NRMTK-NRNCCU - NRNCKU - NRNTUST - NR12TRPgNB: 32T = (4,4,2,1,1;4,4)UE: 4R=(1,2,2,1,1;1,2)SU-MIMO Type I Codebook60kHZ SCSFDD10.1109126 (590M)12TRPgNB: 32T = (4,4,2,1,1;4,4)UE: 4R=(4,4,2,1,1;1,2)SU-MIMO Type I Codebook60kHZ SCSFDD10.139652 (600M)12TRPgNB: 8T = (16,8,2,1,1;2,2)UE: 4R=(1,2,2,1,1;1,2)SU-MIMO Type I Codebook60kHZ SCSFDD10.00629 (490M)36 TRPgNB: 32T = (8,16,2,1,1;2,8)UE: 4R=(1,2,2,1,1;1,2)SU-MIMO Type I Codebook60kHZ SCSFDD10.12400484 (190M)12 TRP gNB: 8T= (4,8,2,1,1;2,2)UE: 4R=(2,4,2,1,2; 1,1)SU-MIMO Non-codebook based60kHZ SCSTDD,DDDSU10.06367604 (570M)12TRPgNB: 32T= (4,4,2,1,1;4,4)UE: 8R= (2,4,2,1,2; 1,2)SU-MIMO Non-codebook based60kHZ SCSTDD,DDDSU10.08595295 (480M)10.03513(500M)12TRPgNB: 32T= (8,8,2,1,1;4,4)UE: 8R= (2,4,2,1,2; 1,2)SU-MIMO Non-codebook based60kHZ SCSTDD,DDDSU10.120367(400M)36TRPgNB: 32T= (4,4,2,1,1;4,4)UE: 8R= (2,4,2,1,2; 1,2)SU-MIMO Non-codebook based60kHZ SCSTDD,DDDSU10.16917338 (180M)Table II-E.6.3Evaluation Result of Indoor Hotspot– eMBB (Configuration C, Downlink)Antenna ConfigurationTXRU mappingTx schemeNumerologyDuplexingITRI -LTEITRI -NRMTK-NRNCCU - NRNCKU - NRNTUST - NR12 TRPgNB: 32T = (8,16,2,1,1;4,4)UE: 4R=(2,4,2,1,2;1,2)SU-MIMO Type I Codebook60kHZ SCSFDD10.113312 (330M)12 TRPgNB: 8T = (8,16,2,1,1;2,2)UE: 2R=(2,4,2,1,1;1,1)SU-MIMO Type I Codebook60kHZ SCSFDD10.098636 (430M)12 TRPgNB: 32T= (4,4,2,1,1;4,4)UE: 8R= (2,4,2,1,2; 1,2)SU-MIMO Non-codebook based60kHZ SCSTDD,DDDSU10.19613826 (400M)10.0003007 (470M)12 TRPgNB: 32T= (8,16,2,1,1;4,4)UE: 8R= (2,4,2,1,2; 1,2)SU-MIMO Non-codebook based60kHZ SCSTDD,DDDSU10.0809984(400M)12 TRPgNB: 8T = (4,16,2,1,1;4,4)UE: 4R = (2,4,2,1,2; 1,1)SU-MIMONon-codebook based60kHZ SCSTDD,DDDSU10.141869328 (580M)36 TRPgNB: 32T= (4,4,2,1,1;4,4)UE: 8R= (2,4,2,1,2; 1,2)SU-MIMO Non-codebook based60kHZ SCSTDD,DDDSU10.7517482 (130M)II-E.6.2Assessment of area traffic capacityWith the investigation and research in this section, TPCEG concluded as followed:–3GPP NR RIT can fulfill the requirement for all the downlink cases of Indoor Hotspot test environment when sufficient bandwidth is adopted. –3GPP LTE RIT can fulfill the requirement for the downlink case with configuration A of Indoor Hotspot test environment when sufficient bandwidth is adopted.Table II-E.6.4Assessment of User Experienced Data RateTest EnvironmentConfigurationLTENRIndoor HotspotA (4GHz)Downlink◎◎B (30GHz)Downlink－◎C (70GHz)Downlink－◎◎ : Fulfill　　　○ : Fulfill with aggressive configurations　　　※ : Issue FoundedII-E.7User plane latencyII-E.7.1Definition and RequirementAs defined in Report ITU-R M.2410, user plane latency is the contribution of the radio network to the time from when the source sends a packet to when the destination receives it (in ms).This requirement is defined for the purpose of evaluation in the eMBB and URLLC usage scenarios.The minimum requirements for user plane latency are:–4 ms for eMBB–1 ms for URLLC assuming unloaded conditions (i.e. a single user) for small IP packets (e.g. 0 byte payload + IP header), for both downlink and uplink.II-E.7.2Analysis for NRThe evaluation of NR user plane latency is based on the procedure illustrated Figure 5.7.1.1.1-1 in TR 37.910 v2.0.0.Based on the DL user plane procedure and assumptions given in Table 5.7.1.1.1-1, a variety of configurations and UE capabilities are evaluated for NR. For NR FDD and TDD, DL user plane latency with various configuration are evaluated, and the following results are investigated and endorsed.Table II-E.7.1.1DL user plane latency for NR FDD (ms)DL user plane latency – NR FDDUE capability 1UE capability 2SCSSCS15 kHz30 kHz60 kHz120 kHz15 kHz30 kHz60 kHzResource mapping Type AM=4 (4OS non-slot)p=01.370.760.540.341.000.550.36p=0.11.580.870.640.401.120.650.41M=7 (7OS non-slot)p=01.490.820.570.361.120.610.39p=0.11.700.930.670.421.250.710.44M=14 (14OS slot)p=02.131.140.720.441.800.940.56p=0.12.431.290.820.512.001.040.63Resource mapping Type BM=2 (2OS non-slot)p=00.980.560.440.290.490.290.23p=0.11.160.670.520.350.600.350.28M=4 (4OS non-slot)p=01.110.630.470.310.660.370.27p=0.11.300.740.560.360.780.450.32M=7 (7OS non-slot)p=01.300.720.520.330.930.510.34p=0.11.490.830.610.391.080.590.40Table II-E.7.1.2DL user plane latency for NR TDD (ms) (Frame structure: DDDSU)DL user plane latency – NR TDD (DDDSU)UE capability 1UE capability 2SCSSCS15 kHz30 kHz60 kHz15 kHz30 kHz60 kHzResource mapping Type AM=4 (4OS non-slot)p=01.570.860.581.180.650.40p=0.11.951.050.701.560.840.50M=7 (7OS non-slot)p=01.690.920.611.300.710.43p=0.12.071.110.731.670.900.53M=14 (14OS slot)p=02.381.260.781.991.060.60p=0.12,781.460.932.371.250.70Resource mapping Type BM=2 (2OS non-slot)p=01.160.650.480.660.390.27p=0.11.520.830.591.020.570.36M=4 (4OS non-slot)p=01.280.710.510.820.470.31p=0.11.640.900.631.170.650.40M=7 (7OS non-slot)p=01.490.820.561.100.610.38p=0.11.861.010.691.470.800.47Table II-E.7.1.3DL user plane latency for NR TDD (ms) (Frame structure: DSUUD)DL user plane latency – NR TDD (DSUUD)UE capability 1UE capability 2SCSSCS15 kHz30 kHz60 kHz120 kHz15 kHz30 kHz60 kHzResource mapping Type AM=4 (4OS non-slot)p=01.931.040.680.411.560.820.48p=0.12.371.260.780.481.991.040.59M=7 (7OS non-slot)p=02.051.10.710.431.690.880.53p=0.12.491.320.830.52.131.10.64M=14 (14OS slot)p=02.741.440.880.512.391.230.7p=0.13.191.6610.582.831.450.81Resource mapping Type BM=2 (2OS non-slot)p=01.470.810.560.351.010.540.36p=0.11.91.020.670.411.430.750.47M=4 (4OS non-slot)p=01.590.870.590.371.160.620.4p=0.12.011.080.70.431.580.830.5M=7 (7OS non-slot)p=01.830.990.650.41.470.770.48p=0.12.261.20.760.461.90.990.58Table II-E.7.1.4DL user plane latency for NR TDD (ms) (Frame structure: DUDU)DL user plane latency – NR TDD (DU)UE capability 1UE capability 2SCSSCS15 kHz30 kHz60 kHz120 kHz15 kHz30 kHz60 kHzResource mapping Type AM=4 (4OS non-slot)p=01.831.000.640.401.470.770.48p=0.12.041.110.730.481.660.870.52M=7 (7OS non-slot)p=01.941.040.650.411.590.830.50p=0.12.161.160.750.491.790.930.55M=14 (14OS slot)p=02.611.380.830.502.291.180.68p=0.12.961.550.960.582.491.290.78Resource mapping Type BM=2 (2OS non-slot)p=01.270.710.510.330.760.420.30p=0.11.460.810.610.390.990.530.36M=4 (4OS non-slot)p=01.460.800.560.350.980.540.36p=0.11.650.910.660.411.220.650.41M=7 (7OS non-slot)p=01.710.930.630.381.320.710.44p=0.11.911.030.730.461.550.810.50Based on the UL user plane procedure and assumptions given in Table 5.7.1.1.2-1, a variety of configurations and UE capabilities are evaluated for NR. For NR FDD and TDD, UL user plane latency with various configuration are evaluated, and the following results are investigated and endorsed.Table II-E.7.1.5UL user plane latency for NR FDD with grant free transmission (ms)UL user plane latency (Grant free) – NR FDDUE capability 1UE capability 2SCSSCS15 kHz30 kHz60 kHz120 kHz15 kHz30 kHz60 kHzResource mapping Type AM=4 (4OS non-slot)p=01.570.860.590.371.200.650.41p=0.11.781.010.690.431.390.750.47M=7 (7OS non-slot)p=01.680.910.610.381.300.700.43p=0.11.891.060.710.441.500.800.49M=14 (14OS slot)p=02.151.150.730.441.800.940.56p=0.12.451.300.840.512.001.060.63Resource mapping Type BM=2 (2OS non-slot)p=00.960.550.440.280.520.300.24p=0.11.140.650.520.340.620.360.28M=4 (4OS non-slot)p=01.310.720.520.330.790.430.30p=0.11.500.840.610.390.960.550.37M=7 (7OS non-slot)p=01.400.770.550.341.020.550.36p=0.11.600.890.630.401.190.640.42M=14 (14OS slot)p=02.141.140.740.441.810.930.56p=0.12.441.300.840.512.011.030.63Table II-E.7.1.6UL user plane latency for NR TDD with grant free transmission (ms) (Frame structure: DDDSU)UL user plane latency – NR TDD (DDDSU)UE capability 1UE capability 2SCSSCS15 kHz30 kHz60 kHz15 kHz30 kHz60 kHzResource mapping Type AM=4 (4OS non-slot)p=03.571.861.083.181.650.90p=0.1-2.111.213.681.901.03M=7 (7OS non-slot)p=03.681.911.113.291.710.93p=0.1-2.161.233.791.961.05M=14 (14OS slot)p=0-2.161.233.791.961.05p=0.1-2.411.36-2.211.18Resource mapping Type BM=2 (2OS non-slot)p=02.581.360.832.081.100.63p=0.13.071.600.952.571.350.75M=4 (4OS non-slot)p=03.121.630.972.661.390.77p=0.13.621.881.093.151.640.90M=7 (7OS non-slot)p=03.231.690.992.841.480.82p=0.13.721.931.123.331.730.94Table II-E.7.1.7UL user plane latency for NR TDD with grant free transmission (ms) (Frame structure: DSUUD)UL user plane latency – NR TDD (DSUUD)UE capability 1UE capability 2SCSSCS15 kHz30 kHz60 kHz120 kHz15 kHz30 kHz60 kHzResource mapping Type AM=4 (4OS non-slot)p=02.741.390.850.52.381.220.70p=0.13.221.640.970.562.771.460.82M=7 (7OS non-slot)p=02.841.490.910.532.491.280.73p=0.13.341.741.030.592.971.520.85M=14 (14OS slot)p=03.341.741.030.592.991.530.85p=0.13.841.991.150.673.471.770.98Resource mapping Type BM=2 (2OS non-slot)p=01.8610.660.41.390.730.46p=0.12.311.230.780.461.850.960.57M=4 (4OS non-slot)p=02.341.240.780.461.910.990.58p=0.12.811.470.90.522.381.220.7M=7 (7OS non-slot)p=02.441.290.810.472.091.080.63p=0.12.911.530.920.542.561.310.75M=14 (14OS slot)p=03.341.741.030.592.991.530.85p=0.13.821.981.150.673.471.770.97Table II-E.7.1.8UL user plane latency for NR TDD with grant free transmission (ms) (Frame structure: DUDU)UL user plane latency – NR TDD (DU)UE capability 1UE capability 2SCSSCS15 kHz30 kHz60 kHz120 kHz15 kHz30 kHz60 kHzResource mapping Type AM=4 (4OS non-slot)p=02.041.090.710.421.680.870.53p=0.12.241.280.800.491.870.970.57M=7 (7OS non-slot)p=02.141.140.730.421.790.930.55p=0.12.361.340.830.501.991.030.60M=14 (14OS slot)p=02.641.390.860.502.291.180.68p=0.13.041.601.010.582.491.280.78Resource mapping Type BM=2 (2OS non-slot)p=01.290.710.520.330.800.440.31p=0.11.470.820.620.391.000.540.36M=4 (4OS non-slot)p=01.660.900.610.381.120.590.39p=0.11.861.040.720.441.420.750.47M=7 (7OS non-slot)p=01.770.960.640.391.390.730.46p=0.11.971.090.750.451.600.830.51M=14 (14OS slot)p=02.641.390.860.502.291.180.68p=0.13.041.591.010.582.491.280.78II-E.7.2Analysis for LTEThe evaluation of LTE user plane latency is based on the procedure illustrated Figure 5.7.1.2.1-1 in TR 37.910 v2.0.0.Based on the DL user plane procedure and assumptions given in Table 5.7.1.2.1-1, a variety of configurations and UE capabilities are evaluated for LTE. For LTE FDD and TDD, DL user plane latency with various configuration are evaluated, and the following results are investigated and endorsed.Table II-E.7.2.1DL user plane latency for LTE FDDTTI durationError probabilityDL UP latency (ms)2OSp=00.63p=0.10.733OSp=00.94p=0.11.10Mixed 2OS/3OSp=00.75p=0.10.887OSp=02.20p=0.12.58Table II-E.7.2.2user plane latency for LTE TDDTTI durationCriterionError probabilityDL UP latency (ms)DSUDD (Cfg.1)DSUUD (Cfg.2)7OSAverage casep=02.552.69p=0.13.103.14Best casep=02.002.00p=0.12.402.40Based on the UL user plane procedure and assumptions given in Table 5.7.1.2.2-1, a variety of configurations and UE capabilities are evaluated for LTE. For LTE FDD and TDD, UL user plane latency with various configuration are evaluated, and the following results are investigated and endorsed.Table II-E.7.2.3UL user plane latency for LTE FDDTTI durationError probabilityUL UP latency (ms)2OSp=00.63p=0.10.733OSp=00.94p=0.11.10Mixed 2OS/3OSp=00.75p=0.10.887OSp=02.20p=0.12.58Table II-E.7.2.4UL user plane latency for LTE TDDTTI durationCriterionError probabilityUL UP latency (ms)DSUDD (Cfg.1)DSUUD (Cfg.2)7OSAverage casep=0-3.26p=0.1-3.73Best casep=02.002.00p=0.12.452.40II-E.7.4Assessment of user plan latencyWith the analysis in this section, TPCEG concluded as followed:–3GPP NR RIT can fulfill the requirement. –3GPP LTE RIT can fulfill the requirement.II-E.8Control plane latencyII-E.8.1Definition and RequirementAs defined in Report ITU-R M.2410, control plane latency refers to the transition time from a most “battery efficient” state (e.g. Idle state) to the start of continuous data transfer (e.g. Active state).Control plane latency refers to the transition time from a most “battery efficient” state (e.g. Idle state) to the start of continuous data transfer (e.g. Active state).This requirement is defined for the purpose of evaluation in the eMBB and URLLC usage scenarios.The minimum requirement for control plane latency is 20 ms. Proponents are encouraged to consider lower control plane latency, e.g. 10 ms.II-E.8.2Analysis for NRThe evaluation of NR control plane latency is based on the procedure illustrated Figure 5.7.2.1-1 in TR 37.910 v2.0.0.Based on the control plane procedure and assumptions given in Table 5.7.2.1-1, a variety of configurations and UE capabilities are evaluated for NR. For NR FDD and TDD, control plane latency with various configuration are evaluated, and the following results are investigated and endorsed.Table II-E.8.2.1Control plane latency for NR FDD (ms)(a) PRACH length = 2 OFDM symbolsResource mapping typeNon-slot durationUE capability 1UE capability 215kHz SCS30kHz SCS60kHz SCS120kHz SCS15kHz SCS30kHz SCS60kHz SCSType AM =415.413.112.311.715.012.812.1(4OS non-slot)M =715.613.412.411.715.213.212.2(7OS non-slot)Type BM=213.312.011.811.313.011.911.6(2OS non-slot)M =413.812.312.011.513.412.111.7(4OS non-slot)M =714.712.812.211.614.312.612.0(7OS non-slot)(b) PRACH length = 6 OFDM symbolsResource mapping typeNon-slot durationUE capability 1UE capability 215kHz SCS30kHz SCS60kHz SCS120kHz SCS15kHz SCS30kHz SCS60kHz SCSType AM =4(4OS non-slot)15.613.512.411.715.113.012.1M =7(7OS non-slot)15.813.612.511.715.313.112.2Type BM=2(2OS non-slot)13.712.311.911.413.412.011.7M =4(4OS non-slot)14.212.512.011.513.912.311.8M =7(7OS non-slot)15.313.012.311.614.812.812.1(c) PRACH length=1msResource mapping typeNon-slot durationUE capability 1UE capability 215kHz SCS30kHz SCS15kHz SCS30kHz SCSType AM =416.313.616.313.6(4OS non-slot)M =716.514.316.514.3(7OS non-slot)M =14(14OS slot)17.014.517.014.5Type BM=214.112.913.812.7(2OS non-slot)M =4(4OS non-slot)14.713.314.312.9M =7(7OS non-slot)15.813.815.013.3Table II-E.8.2.2Control plane latency for NR TDD (ms)(a) PRACH length = 2 OFDM symbolsResource mapping typeNon-slot durationUE capability 1UE capability 215kHz SCS30kHz SCS15kHz SCS30kHz SCSType AM =4(4OS non-slot)17.914.017.914.0M =7(7OS non-slot)18.114.418.114.2Type BM=2(2OS non-slot)16.813.416.813.4M =4(4OS non-slot)17.213.617.213.6M =7(7OS non-slot)17.613.817.613.8(b) PRACH length=1msResource mapping typeNon-slot durationUE capability 1UE capability 215kHz SCS15kHz SCSType AM =4(4OS non-slot)18.318.3M =7(7OS non-slot)18.518.5Type BM=2(2OS non-slot)17.117.1M =4(4OS non-slot)17.617.6M =7(7OS non-slot)18.018.0II-E.8.3Analysis for LTEThe evaluation of LTE control plane latency is based on the procedure illustrated Figure 5.7.2.2-1 in TR 37.910 v2.0.0.Based on the control plane procedure and assumptions given in Table 5.7.2.2-1, a variety of configurations and UE capabilities are evaluated for NR. Besides FDD, control plane latency for LTE TDD with various configuration are evaluated, and the following results are investigated and endorsed.Table II-E.8.3.1Control plane latency of LTE TDD for DL data transferStepAverage CP Latency for DL data transfer[ms]Config 0Config 1Config 2Config 3Config 4Config 5Config 6100000002111111133222.7222.54111111154.85.45.84.85.75.94.56111111173333333.38111111194333333.8100000000Total delay [ms]18.817.417.817.517.717.918.1Notes:1The description of each component is the same as in Table 5.7.2.2-1. TDD frame structure configuration 0~6 are defined in TS36.211.2For step 1, the procedure for transition from a most “battery efficient” state has yet not begun, hence this step is not relevant for the latency of the procedure which is illustrated by a '0' in the above.3For step 3, the eNB processing delay is 2ms as in FDD. Additional delay due to waiting for DL subframe is included. The delay value is the average delay taken over the starting subframes when the procedure is initiated under the corresponding TDD configuration.4For step 5, the UE processing delay is 4 ms as in FDD, see LS in R2-1806411. Additional delay due to waiting for UL subframe is included. The delay value is the average delay taken over the starting subframes when the procedure is initiated under the corresponding TDD configuration.5For step 7, the eNB processing delay (L2 and RRC) has been reduced to 3 ms as in FDD. Additional delay due to waiting for DL subframe is included. The delay value is the average delay taken over the starting subframes when the procedure is initiated under the corresponding TDD configuration.6For step 9 for DL data transfer, only the processing delay in the UE (L2 and RRC) is considered as in FDD. Additional delay due to waiting for DL subframe for receiving DL grant is included. The delay value is the average delay taken over the starting subframes when the procedure is initiated under the corresponding TDD configuration.7For step 10, the beginning of this subframe is considered to be "the start of continuous data transfer", hence this step is not relevant for the latency of the procedure which is illustrated by a '0' in the above.Table II-E.8.3.2Control plane latency of LTE TDD for UL data transferStepDescriptionCP Latency for UL data transfer[ms]for the following casesConfig 0, Starting Subframe = 2,7Config 1, Starting Subframe = 2,7Config 3, Starting Subframe = 1, 2Config 4, Starting Subframe = 2Config 6, Starting Subframe = 2,71Delay due to RACH scheduling period (1TTI)02Transmission of RACH Preamble13Preamble detection and processing in eNB24Transmission of RA response15UE Processing Delay (decoding of scheduling grant, timing alignment and C-RNTI assignment + L1 encoding of RRC Connection Resume Request)46Transmission of RRC Connection Resume Request17Processing delay in eNB (L2 and RRC)38Transmission of RRC Connection Resume19Processing delay in UE of RRC Connection Resume including grant reception710Transmission of RRC Connection Resume Complete and UP data 0Total delay [ms]20Notes:1TDD frame structure configuration 0~6 are defined in TS36.211. The delay value is for the given starting subframes under the corresponding TDD configuration.2For step 1, the procedure for transition from a most “battery efficient” state has yet not begun, hence this step is not relevant for the latency of the procedure which is illustrated by a '0' in the above.3For step 3, the eNB processing delay is 2ms as in FDD. Additional delay due to waiting for DL subframe is 0 for the given starting subframes under the corresponding TDD configuration. 4For step 5, the UE processing delay is 4 ms as in FDD, see LS in R2-1806411. Additional delay due to waiting for UL subframe is 0 for the given starting subframes under the corresponding TDD configuration.5For step 7, the eNB processing delay (L2 and RRC) has been reduced to 3 ms as in FDD. Additional delay due to waiting for DL subframe is 0 for the given starting subframes under the corresponding TDD configuration.6For step 9 for UL data transfer, the processing delay is considered as in FDD. Additional delay due to waiting for DL subframe for receiving UL grant is 0 for the given starting subframes under the corresponding TDD configuration.7For step 10, the beginning of this subframe is considered to be "the start of continuous data transfer", hence this step is not relevant for the latency of the procedure which is illustrated by a '0' in the above.II-E.8.4Assessment of control plan latencyWith the analysis in this section, TPCEG concluded as followed:–3GPP NR RIT can fulfill the requirement. –3GPP LTE RIT can fulfill the requirement.II-E.9Connection densityII-E.9.1Evaluation for NR and LTE RITsThe connection density results for NR and LTE are shown in Tables II-E.9.1 and Table II-E.9.2 for two traffic arrival patterns. From the results in the two tables, it can be seen that NR RIT and LTE RIT fulfil the connection density requirements of 1,000,000 devices/km2 with the configuration of 500m ISD and 1732m ISD.Note that more detailed information can be found in Annex A-3.Table II-E.9.1 Evaluation Result of Connection Density (Configuration A, 500m ISD, Uplink)TXRU mappingTx schemeNumerologyDuplexingTrafficITRI-LTE(NB IoT)ITRI-NRgNB: 2R = (8,1,2,1,1; 1,1)UE: 1T=1T, (1,1,1,1,1; 1,1)1x8 SU-MIMOType I codebook15kHz, SCSFDD1 message/2 hours/device41,144,27240,154,329gNB: 2R = (8,1,2,1,1; 1,1)UE: 1T=1T, (1,1,1,1,1; 1,1)1x8 SU-MIMOType I codebook15kHz SCSFDD1 message/day/device493,731,267481,851,947Table II-E.9.2Evaluation Result of Connection Density (Configuration B, 1732m ISD, Uplink)TXRU mappingTx schemeNumerologyDuplexingTrafficITRI-LTE(NB-IoT)ITRI-NRgNB: 2R = (8,1,2,1,1; 1,1)UE: 1T=1T, (1,1,1,1,1; 1,1)1x8 SU-MIMOType I codebook15kHz, SCSFDD1 message/2 hours/device1,404,6971,746,033gNB: 2R = (8,1,2,1,1; 1,1)UE: 1T=1T, (1,1,1,1,1; 1,1)1x8 SU-MIMOType I codebook15kHz SCSFDD1 message/day/device16,856,369.0020,952,390II-E.9.2Assessment of connection densityWith the investigation and research in this section, TPCEG concluded as followed:–3GPP NR RIT can fulfill the requirement in mMTC test environments.–3GPP LTE RIT can fulfill the requirement in mMTC test environments.Table II-E.9.3Assessment of Connection DensityTest EnvironmentConfigurationLTENRmMTCA (700 MHz)500m ISD◎◎B (700 MHz)1732 ISD◎◎◎ : Fulfill　　　○ : Fulfill with aggressive configurations　　　※ : Issue FoundedII-E.10Energy efficiencyII-E.10.1Definition and RequirementAs defined in Report ITU-R M.2410, network energy efficiency is the capability of a RIT/SRIT to minimize the radio access network energy consumption in relation to the traffic capacity provided. Device energy efficiency is the capability of the RIT/SRIT to minimize the power consumed by the device modem in relation to the traffic characteristics. The RIT/SRIT shall have the capability to support a high sleep ratio and long sleep duration. Proponents are encouraged to describe other mechanisms of the RIT/SRIT that improve the support of energy efficient operation for both network and device.The sleep ratio is the fraction of unoccupied time resources (for the network) or sleeping time (for the device) in a period of time corresponding to the cycle of the control signaling (for the network) or the cycle of discontinuous reception (for the device) when no user data transfer takes place. The sleep duration is the continuous period of time with no transmission (for network and device) and reception (for the device).Energy efficiency of the network and the device can relate to the support for the following two aspects:a)Efficient data transmission in a loaded case;b)Low energy consumption when there is no data.This requirement is defined for the purpose of evaluation in the eMBB usage scenario.II-E.10.2Analysis for NRThe evaluation of NR energy efficiency is based on the procedure illustrated Section 5.8 in TR 37.910 v2.0.0.Based on the transmission process and assumptions given in Figure 5.8.1.1-1 and Figure 5.8.2.1.1-1 in TR 37.910 v2.0.0., the performance for a variety of sleep ratio and sleep duration are evaluated for NR. For network and device sides, energy efficiency with various configuration are evaluated, and the following results are investigated and endorsed.Table II-E.10.2.1NR network sleep ratio in slot levelSSB configurationSSB set periodicity PSSBSCS [kHz]Number of SS/PBCH block per SSB set, L5ms10ms20ms40ms80ms160ms15kHz 180.00%90.00%95.00%97.50%98.75%99.38%280.00%90.00%95.00%97.50%98.75%99.38%30kHz 195.00%97.50%98.75%99.38%99.69%99.84%480.00%90.00%95.00%97.50%98.75%99.38%120kHz 890.00%95.00%97.50%98.75%99.38%99.69%1680.00%90.00%95.00%97.50%98.75%99.38%240kHz 1690.00%95.00%97.50%98.75%99.38%99.69%3280.00%90.00%95.00%97.50%98.75%99.38%Table II-E.10.2.2NR network sleep ratio in symbol levelSSB configurationSSB set periodicity PSSBSCS [kHz]Number of SS/PBCH block per SSB set, L5ms10ms20ms40ms80ms160ms15kHz 193.57%96.43%97.86%98.93%99.46%99.73%287.14%92.86%95.71%97.86%98.93%99.46%30kHz 196.79%98.21%98.93%99.46%99.73%99.87%487.14%92.86%95.71%97.86%98.93%99.46%120kHz 894.29%97.14%98.57%99.29%99.64%99.82%1688.57%94.29%97.14%98.57%99.29%99.64%240kHz 1694.29%97.14%98.57%99.29%99.64%99.82%3288.57%94.29%97.14%98.57%99.29%99.64%Table II-E.10.2.3NR network sleep duration (ms) in slot levelSSB configurationSSB set periodicity PSSBSCS [kHz]Number of SS/PBCH block per SSB set, L5ms10ms20ms40ms80ms160ms15kHz 14.009.0019.0039.0079.00159.0024.009.0019.0039.0079.00159.0030kHz 14.509.5019.5039.5079.50159.5044.009.0019.0039.0079.00159.00120kHz 84.509.7218.9239.0378.97158.99164.009.8818.7739.0578.96158.99240kHz 164.509.8618.9039.0478.97158.99324.009.9418.7639.0678.96158.99Table II-E.10.2.4NR device sleep ratio in slot level (for idle / inactive mode)Paging cycle NPC_RF *10 (ms)SCS(kHz)SSB LSSB reception time(ms)SSB cycle (ms)Number of SSB burst setRRM measurement time per DRX (ms)Transition time(ms)Sleep ratioRRC-Idle/Inactive320240321--13.51095.5%25601521--131099.5%25601521160231093.2%Table II-E.10.2.5NR device sleep ratio in slot level (for connected mode)DRX cycle TSC_ms * MSC (ms)Number of SSB burst setDRX-onDurationTimer(ms)RRM measurement time per DRX (ms)Transition time(ms)Sleep ratioRRC-Connected320123.51095.2%32011031092.8%2560110031095.6%102401160031084.2%II-E.10.3Analysis for LTEThe evaluation of LTE energy efficiency is based on the procedure illustrated Section 5.8 in TR 37.910 v2.0.0.Based on the transmission process and assumptions given in Figure 5.8.1.2-1 in TR 37.910 v2.0.0., the performance for a variety of sleep ratio and sleep duration are evaluated for LTE. For network and device sides, energy efficiency with various configuration are evaluated, and the following results are investigated and endorsed.Table II-E.10.3.1LTE network sleep ratio in subframe levelCell typeSleep ratioFeMBMS/Unicast-mixed cell80%MBMS-dedicated cell93.75%Table II-E.10.3.2LTE network sleep duration (ms) in subframe levelCell typeSleep duration (ms)FeMBMS/Unicast-mixed cell4.00MBMS-dedicated cell39.00Table II-E.10.3.3LTE device sleep ratio in subframe level (for idle mode)Paging cycle NPC_RF *10 (ms)Synchronization reception time per cycle (ms)Synchronization cycle (ms)Number ofsynchronizationRRM measurement time per DRX (ms)Transition time (ms)DL/UL subframe ratioSleep ratioRRC-Idle320210*1610193.1%320210*2610190.0%2560210*1610199.1%2560210*2610198.8%Table II-E.10.3.3Table 5.8.2.2.1-2 LTE device sleep ratio in subframe level (for connected mode)DRX cycle TCYCLE_SF (ms)Synchronization reception time (ms)Synchronization cycle(ms)Number of synchronizationPDCCH reception time (ms)RRM measurement time per DRX (ms)DL/UL subframe ratioSleep ratioRRC-Connected3202--1106191.9%32021021060.585.6%25602--11006195.5%2560210210060.591.2%102402--116006184.2%II-E.10.4Assessment of energy efficiencyWith the analysis in this section, TPCEG concluded as followed:–3GPP NR RIT can fulfill the requirement. –3GPP LTE RIT can fulfill the requirement.II-E.11ReliabilityII-E.11.1Evaluation for NR and LTE RITsThe reliability results for NR are shown in Tables II-E.11.1 to Table II-E.11.4 for uplink and downlink cases. From the results in the four tables, it can be seen that NR RIT fulfils the reliability requirements by sustaining higher reliability than 1-10-5.Note that more detailed information can be found in Annex A-3.Table II-E.11.1Evaluation Result of Reliability (Configuration A, Downlink)TXRU mappingTx schemeNumerologyDuplexingITRI-LTEITRI-NRgNB: 8T = (8,4,2,1,1;1,4)UE: 4R=(1,2,2,1,1;1,2)8x4 SU-MIMO Type I Codebook15kHz, SCSFDD99.99929997%Table II-E.11.2Evaluation Result of Reliability (Configuration A, Uplink)TXRU mappingTx schemeNumerologyDuplexingITRI-LTEITRI-NRgNB: 8R = (8,4,2,1,1;1,4)UE: 1T=(1,1,2,1,1;1,1)1x8 SU-MIMO Type I Codebook15kHz, SCSFDD99.99999%Table II-E.11.3Evaluation Result of Reliability (Configuration B, Downlink)TXRU mappingTx schemeNumerologyDuplexingITRI-LTEITRI-NRgNB: 2Tx (8,1,2,1,1;1,1)UE: 2Rx (1,1,2,1,1;1,1)2x2 SU-MIMOType I codebook15kHz, SCSFDD99.99929998%Table II-E.11.4Evaluation Result of Reliability (Configuration B, Uplink)TXRU mappingTx schemeNumerologyDuplexingITRI-LTEITRI-NRgNB: 8R = (8,1,2,1,1;1,4)UE: 1T=(1,1,1,1,1;1,1)1x8 SU-MIMO Type I codebook15?kHz, SCSFDD99.99999984%II-E.11.2Assessment of reliabilityWith the investigation and research in this section, TPCEG concluded as followed:–3GPP NR RIT can fulfill the requirement in URLLC test environments.–Further evaluation results are needed to confirm the performance of 3GPP LTE RIT.Table II-E.11.5Assessment of ReliabilityTest EnvironmentConfigurationLTENRURLLCA (4?GHz)Downlink－◎Uplink－◎B (700 MHz)Downlink－◎Uplink－◎◎ : Fulfill　　　○ : Fulfill with aggressive configurations　　　※ : Issue FoundedII-E.12MobilityII-E.12.1Evaluation for NR and LTE RITsBased on the configuration and assumption in Annex A, the evaluation results of Mobility in Indoor Hotspot-eMBB, Dense Urban-eMBB, and Rural-eMBB test environment are shown in II-E-12.1 to II-E.12.4. From the results in the four tables, it can be seen that NR and LTE RITs fulfil the mobility requirements of different spectral efficiency with the configuration of particular speeds.Note that more detailed information can be found in Annex A-3.Table II-E.12.1 Evaluation Result of Mobility (Indoor, Configuration A, 4GHz)TXRU mappingTx schemeNumerologyDuplexingITRI -NRITRI- LTENLOSLOSNLOSLOSgNB: 8R = (4,4,2,1,1;,1,4)UE: 1T = (1,1,1,1,1;1,1)1 X 8 SU-MIMOType I codebook15?kHzFDD1.65051.53151.67871.66204Table II-E.12.2 Evaluation Result of Mobility (Dense Urban, Configuration A, 4GHz)TXRU mappingTx schemeNumerologyDuplexingITRI -NRITRI- LTENLOSLOSNLOSLOSgNB: 8R = (8,4,2,1,1;1,4)UE: 1T = (1,1,1,1,1;1,1)1 X 8 SU-MIMOType I codebook15?kHzFDD2.0692.006482.20322.13055Table II-E.12.3 Evaluation Result of Mobility (Rural, Configuration A, 700MHz)TXRU mappingTx schemeNumerologyDuplexingITRI -NRITRI- LTENLOSLOSNLOSLOSgNB: 4R = (8,2,2,1,1;1,2)UE: 1T = (1,1,1,1,1;1,1)1 X 4 SU-MIMOType I codebook15?kHz(120?km/h)FDD3.46853.46853.81433.8143gNB: 4R = (8,2,2,1,1;1,2)UE: 1T = (1,1,1,1,1;1,1)1 X 4 SU-MIMOType I codebook30?kHz(500?km/h)FDD3.46763.43383.0813.11574Table II-E.12.4 Evaluation Result of Mobility (Rural, Configuration B, 4GHz)TXRU mappingTx schemeNumerologyDuplexingITRI-NRITRI-LTENLOSLOSNLOSLOSgNB: 4R = (8,2,2,1,1;1,2)UE: 1T = (1,1,1,1,1;1,1)1 X 4 SU-MIMOType I codebook15?kHz(120?km/h)FDD2.0922.0922.08472.0847gNB: 4R = (8,2,2,1,1;1,2)UE: 1T = (1,1,1,1,1;1,1)1 X 4 SU-MIMOType I codebook30?kHz(500?km/h)FDD1.0451.0451.03931.0393II-E.12.2Assessment of mobilityWith the investigation and research in this section, TPCEG concluded as followed:–3GPP NR RIT can fulfil the requirements for Indoor Hotspot, Dense Urban, and Rural scenario test environments in eMBB Scenario.–3GPP LTE RIT can fulfil the requirements for Indoor Hotspot, Dense Urban, and Rural scenario test environments in eMBB Scenario.Table II-E.12.5Assessment of MobilityTest EnvironmentConfigurationLTENRIndoor HotspotA (4GHz)10 km/h◎◎Dense UrbanA (4GHz)30 km/h◎◎RuralA (700 MHz)120 km/h◎◎500 km/h◎◎B (4GHz)120 km/h◎◎500 km/h◎◎◎ : Fulfill　　　○ : Fulfill with aggressive configurations　　　※ : Issue FoundedII-E.13Mobility interruption timeII-E.13.1Definition and RequirementAs defined in Report ITU-R M.2410, the Mobility interruption time is the shortest time duration supported by the system during which a user terminal cannot exchange user plane packets with any base station during transitions.The mobility interruption time includes the time required to execute any radio access network procedure, radio resource control signalling protocol, or other message exchanges between the mobile station and the radio access network, as applicable to the candidate RIT/SRIT.The minimum requirement for mobility interruption time is 0 ms. This requirement is defined for the purpose of evaluation in the eMBB and URLLC usage scenarios.II-E.13.2Analysis for NRThe evaluation of NR mobility interruption time is based on the procedure in Section 5.10 in TR 37.910 v2.0.0.For NR RIT, the mobility interruption time in various scenario are evaluated, and the following results are investigated and endorsed.For DL data transmission during UE mobility, gNB can configure different beams for this UE at different slots. It ensures appropriate transmit beam allocation to the UE for continuous DL transmission. Therefore, DL data packet transmission is kept during beam pair switching at different slots.For UL data transmission, PUSCH is sent using the beam configured by SRI (SRS resource indicator) by gNB. Accordingly, an appropriate gNB-side beam is selected for UL data reception. gNB may select different beams at different slots depending on the UE mobility. Therefore, UL data packet transmission is kept during beam pair switching at different slots.With beam mobility, the UE can always exchange user plane packets with gNB during the mobility transitions. Therefore, 0ms mobility interruption time is achieved by NR for this scenario.Besides, the UE can always exchange user plane packets with the gNB during transitions during CA mobility procedures when the data transmission between the UE and the PCell is kept. Therefore, 0?ms mobility interruption time is achieved by NR also for this case.II-E.13.3Analysis for LTEFor LTE RIT, the mobility interruption time in various scenario are evaluated, and the following results are investigated and endorsed.In Make-Before-Break handover, the connection to the source eNB is not released until DL synchronization is completed at the target eNB. For intra-frequency handover case, a dual RX UE can receive data from the source eNB and tracking RS from the target at the same time, while synchronizing with target eNB. Nevertheless, the UE releases the serving cell before performing the RACH procedure.Besides, if the source eNB, target eNB and UE are synchronized, the UE may be able to obtain the target eNB timing advance (TA) without explicit TA command, so that a RACH-less handover can be applied: in some scenarios such as no or negligible UE TA difference between the source and target eNB, the UE can use its original TA for the source eNB to transmit the data to the target eNB. In this case, the delay of the RACH procedure can be avoided.By combining Make-Before-Break and RACH-less handover for a dual RX UE in the scenario where there is no or negligible UE TA difference between the source and the target cell, the 0ms mobility interruption time is achieved by LTE for the PCell mobility scenario.Furthermore, during the DC mobility procedures, the UE can always exchange user plane packets with MeNB during transitions. Therefore, 0ms mobility interruption time is also achieved by LTE for the DC mobility scenario.II-E.13.4Assessment of mobility interruption timeWith the analysis in this section, TPCEG concluded as followed:–3GPP NR RIT can fulfill the requirement. –3GPP LTE RIT can fulfill the requirement.II-E.14BandwidthII-E.14.1Definition and RequirementAs defined in Report ITU-R M.2410, the minimum requirement on supported bandwidth is the maximum aggregated system bandwidth. The bandwidth may be supported by single or multiple radio frequency (RF) carriers. The bandwidth capability of the RIT/SRIT is defined for the purpose of IMT-2020 evaluation.The requirement for bandwidth is at least 100 MHz.The RIT/SRIT shall support bandwidths up to 1 GHz for operation in higher frequency bands (e.g. above 6 GHz).The RIT/SRIT shall support scalable bandwidth. Scalable bandwidth is the ability of the candidate RIT/SRIT to operate with different bandwidths.II-E.14.2Inspection for NRAccording to Section 5.3.2 of TS 38.104, the maximum bandwidth related to specific sub-carrier spacing (SCS) and frequency range (FR) for a component carrier is provided. Besides, according to Section 6.4 of TS38.331, carrier aggregation of up to sixteen component carriers is supported by NR Rel-15. Accordingly, the NR capability of maximum aggregated system bandwidth is presented in Table 8.1.1-1 TR 37.910. It is observed that the maximum aggregated bandwidth for FR 1 is 800?MHz to 1 600 MHz; while for FR 2, the maximum aggregated bandwidth is 3 200 MHz to 6?400 MHz. Therefore, the bandwidth requirement of at least 100 MHz is met by NR Rel-15 under all frequency ranges for all sub-carrier spacing values.Table II-E.14.2 NR capability on bandwidthSCS [kHz]Maximum bandwidth for one component carrier (MHz)Maximum number of component carriers for carrier aggregationMaximum aggregated bandwidth (MHz)FR11550168003010016160060100161600FR260200163200120400166400II-E.14.3Inspection for LTEAccording to Section 5.6 of TS36.101, the maximum bandwidth of a component carrier is 20 MHz for LTE. Besides, according to Section 6.4 of TS 36.331, carrier aggregation of up to thirty-two component carriers is supported by LTE Rel-15. Accordingly, LTE Rel-15 reaches the capability of maximum aggregated system bandwidth of 640 MHz. Therefore, the bandwidth requirement of at least 100 MHz is met by LTE Rel-15.Table II-E.14.3 LTE capability on bandwidthMaximum bandwidth for one component carrier (MHz)Maximum number of component carriers for carrier aggregationMaximum aggregated bandwidth (MHz)2032640II-E.14.4Assessment of control plan latencyWith the inspection in this section, TPCEG concluded as followed:–3GPP NR RIT can fulfill the requirement. –3GPP LTE RIT can fulfill the requirement.II-E.15Support of wide range of servicesII-E.15.1Inspection for NR and LTE RITsThe ITU-R requirements on “support of wide range of services” are given in M.2410:–Enhanced Mobile Broadband (eMBB). –Ultra-reliable and low latency communications (URLLC).–Massive machine type communications (mMTC).Diverse services and applications for the three usage scenarios are envisaged, as shown in Fig. 2 in Recommendation ITU-R M.2083.IMT-2020 RIT/SRIT shall support a wide range of services across different usage scenarios, for which the evaluation methodology is found in § 7.3.3 of Report ITU-R M.2412-0.These results will be provided in the conclusion for Part III after all other characteristics have been investigated and evaluated.II-E.15.2Assessment of support of wide range of servicesWith the inspection in this section, TPCEG concluded as followed:–3GPP NR RIT can fulfill the requirement. -3GPP LTE RIT can fulfill the requirement.II-E.16Supported spectrum bandsII-E.16.1Definition and RequirementThe ITU-R requirements on “supported spectrum bands are” are given in M.2410:–450-470 MHz (see No. 5.286AA of the Radio Regulations (RR))–470-698 MHz (see RR Nos. 5.295, 5.308, 5.296A)–694/698-960 MHz (see RR Nos. 5.313A, 5.317A)–1 427-1 518 MHz (see RR Nos. 5.341A, 5.346, 5.341B, 5.341C, 5.346A)–1 710-2 025 MHz (see RR Nos. 5.384A, 5.388)–2 110-2 200 MHz (see RR No. 5.388)–2 300-2 400 MHz (see RR No. 5.384A)–2 500-2 690 MHz (see RR No. 5.384A)–3 300-3 400 MHz (see RR Nos. 5.429B, 5.429D, 5.429F)–3 400-3 600 MHz (see RR Nos. 5.430A, 5.431B, 5.432A, 5.432B, 5.433A)–3 600-3 700 MHz (see RR No. 5.434)–4 800-4 990 MHz (see RR Nos. 5.441A, 5.441B).Frequency arrangements for these bands identified before WRC-15 are incorporated in Recommendation ITU-R M.1036-5. Work on frequency arrangements for the frequency bands that were identified by WRC-15 is currently ongoing in ITU-R. Recommendation ITU-R M.2083 indicates a need of higher frequency bands to support the different usage scenarios with a requirement of several hundred MHz up to at least 1 GHz bandwidth corresponding wider and contiguous spectrum ability. Further, the development of IMT 2020 is expected to enable new use cases and applications associated with radio traffic growth.Besides, spectrum requirement as defined in Report ITU-R M.2411 include:–the capability of being able to utilize at least one frequency band identified for IMT in the ITU Radio Regulations, and–the capability of being able to utilize the higher frequency range/band(s) above 24.25?GHz (NOTE: In the case of the candidate SRIT, at least one of the component RITs need to fulfil this requirement.)II-E.16.2Inspection for NRThe following frequency bands are currently specified, in accordance with spectrum requirements defined by Report ITU-R M.2411-0. Introduction of other ITU-R IMT identified bands are not precluded in the future. 3GPP technologies are also defined as appropriate to operate in other frequency arrangements and bands. Table II-E.16.3.1Supported spectrum bands for NRa) 450-6000 MHzNR operating bandUplink (UL) operating bandBS receive / UE transmitFUL_low – FUL_highDownlink (DL) operating bandBS transmit / UE receiveFDL_low – FDL_highDuplex Moden11920 MHz – 1980 MHz2110 MHz – 2170 MHzFDDn21850 MHz – 1910 MHz1930 MHz – 1990 MHzFDDn31710 MHz – 1785 MHz1805 MHz – 1880 MHzFDDn5824 MHz – 849 MHz869 MHz – 894 MHzFDDn72500 MHz – 2570 MHz2620 MHz – 2690 MHzFDDn8880 MHz – 915 MHz925 MHz – 960 MHzFDDn12699 MHz – 716 MHz729 MHz – 746 MHzFDDn20832 MHz – 862 MHz791 MHz – 821 MHzFDDn251850 MHz – 1915 MHz1930 MHz – 1995 MHzFDDn28703 MHz – 748 MHz758 MHz – 803 MHzFDDn342010 MHz – 2025 MHz2010 MHz – 2025 MHzTDDn382570 MHz – 2620 MHz2570 MHz – 2620 MHzTDDn391880 MHz – 1920 MHz1880 MHz – 1920 MHzTDDn402300 MHz – 2400 MHz2300 MHz – 2400 MHzTDDn412496 MHz – 2690 MHz2496 MHz – 2690 MHzTDDn501432 MHz – 1517 MHz1432 MHz – 1517 MHzTDDn511427 MHz – 1432 MHz1427 MHz – 1432 MHzTDDn661710 MHz – 1780 MHz2110 MHz – 2200 MHzFDDn701695 MHz – 1710 MHz1995 MHz – 2020 MHzFDDn71663 MHz – 698 MHz617 MHz – 652 MHzFDDn741427 MHz – 1470 MHz1475 MHz – 1518 MHzFDDn75N/A1432 MHz – 1517 MHzSDLn76N/A1427 MHz – 1432 MHzSDLn773300 MHz – 4200 MHz3300 MHz – 4200 MHzTDDn783300 MHz – 3800 MHz3300 MHz – 3800 MHzTDDn794400 MHz – 5000 MHz4400 MHz – 5000 MHzTDDn801710 MHz – 1785 MHzN/ASULn81880 MHz – 915 MHzN/ASULn82832 MHz – 862 MHzN/ASULn83703 MHz – 748 MHzN/ASULn841920 MHz – 1980 MHzN/ASULn861710 MHz – 1780 MHzN/ASULb) 24?250-52?600 MHzNR operating bandUplink (UL) and Downlink (DL) operating bandBS transmit/receiveUE transmit/receiveFUL_low – FUL_highFDL_low – FDL_highDuplex Moden25726500 MHz – 29500 MHzTDDn25824250 MHz – 27500 MHzTDDn26037000 MHz – 40000 MHzTDDn26127500 MHz – 28350 MHzTDDII-E.16.3Inspection for LTEThe following frequency bands are currently specified, in accordance with spectrum requirements defined by Report ITU-R M.2411-0. Introduction of other ITU-R IMT identified bands are not precluded in the future. 3GPP technologies are also defined as appropriate to operate in other frequency arrangements and bands. Table II-E.16.3.2Supported spectrum bands for LTE, 450 – 6000 MHz:LTE (EUTRA) Operating BandUplink (UL) operating bandBS receive, UE transmitDownlink (DL) operating bandBS transmit, UE receiveDuplex ModeFUL_low – FUL_highFDL_low – FDL_high11920 MHz–1980 MHz2110 MHz–2170 MHzFDD21850 MHz–1910 MHz1930 MHz–1990 MHzFDD31710 MHz–1785 MHz1805 MHz–1880 MHzFDD41710 MHz–1755 MHz2110 MHz–2155 MHzFDD5824 MHz–849 MHz869 MHz–894MHzFDD61830 MHz–840 MHz875 MHz–885 MHzFDD72500 MHz–2570 MHz2620 MHz–2690 MHzFDD8880 MHz–915 MHz925 MHz–960 MHzFDD91749.9 MHz–1784.9 MHz1844.9 MHz–1879.9 MHzFDD101710 MHz–1770 MHz2110 MHz–2170 MHzFDD111427.9 MHz–1447.9 MHz1475.9 MHz–1495.9 MHzFDD12699 MHz–716 MHz729 MHz–746 MHzFDD13777 MHz–787 MHz746 MHz–756 MHzFDD14788 MHz–798 MHz758 MHz–768 MHzFDD17704 MHz–716 MHz734 MHz–746 MHzFDD18815 MHz–830 MHz860 MHz–875 MHzFDD19830 MHz–845 MHz875 MHz–890 MHzFDD20832 MHz–862 MHz791 MHz–821 MHzFDD211447.9 MHz–1462.9 MHz1495.9 MHz–1510.9 MHzFDD223410 MHz–3490 MHz3510 MHz–3590 MHzFDD2312000 MHz–2020 MHz2180 MHz–2200 MHzFDD241626.5 MHz–1660.5 MHz1525 MHz–1559 MHzFDD251850 MHz–1915 MHz1930 MHz–1995 MHzFDD26814 MHz–849 MHz859 MHz–894 MHzFDD27807 MHz–824 MHz852 MHz–869 MHzFDD28703 MHz–748 MHz758 MHz–803 MHzFDD29N/A717 MHz–728 MHzFDD130152305 MHz–2315 MHz2350 MHz–2360 MHzFDD31452.5 MHz–457.5 MHz462.5 MHz–467.5 MHzFDD32N/A1452 MHz–1496 MHzFDD1331900 MHz–1920 MHz1900 MHz–1920 MHzTDD342010 MHz–2025 MHz2010 MHz–2025 MHzTDD351850 MHz–1910 MHz1850 MHz–1910 MHzTDD361930 MHz–1990 MHz1930 MHz–1990 MHzTDD371910 MHz–1930 MHz1910 MHz–1930 MHzTDD382570 MHz–2620 MHz2570 MHz–2620 MHzTDD391880 MHz–1920 MHz1880 MHz–1920 MHzTDD402300 MHz–2400 MHz2300 MHz–2400 MHzTDD412496 MHz2690 MHz2496 MHz2690 MHzTDD423400 MHz–3600 MHz3400 MHz–3600 MHzTDD433600 MHz–3800 MHz3600 MHz–3800 MHzTDD44703 MHz–803 MHz703 MHz–803 MHzTDD451447 MHz–1467 MHz1447 MHz–1467 MHzTDD465150 MHz–5925 MHz5150 MHz–5925 MHzTDD1475855 MHz–5925 MHz5855 MHz–5925 MHzTDD1483550 MHz–3700 MHz3550 MHz–3700 MHzTDD493550 MHz–3700 MHz3550 MHz–3700 MHzTDD1501432 MHz–1517 MHz1432 MHz-1517 MHzTDD1511427 MHz–1432 MHz1427 MHz-1432 MHzTDD1523300 MHz–3400 MHz3300 MHz-3400 MHzTDD651920 MHz–2010 MHz2110 MHz–2200 MHzFDD661710 MHz–1780 MHz2110 MHz–2200 MHzFDD167N/A738 MHz–758 MHzFDD168698 MHz–728 MHz753 MHz–783 MHzFDD69N/A2570 MHz–2620 MHzFDD1701695 MHz–1710 MHz1995 MHz–2020 MHzFDD171663 MHz–698 MHz617 MHz–652 MHzFDD72451 MHz–456 MHz461 MHz–466 MHzFDD73450 MHz–455 MHz460 MHz–465 MHzFDD741427 MHz–1470 MHz1475 MHz–1518 MHzFDD75N/A1432 MHz–1517 MHzFDD176N/A1427 MHz–1432 MHzFDD185698 MHz–716 MHz728 MHz–746 MHzFDDNOTE 1: See details in Table 8.2.2-1 in TS 36.101.II-E.16.4Assessment of supported spectrum bandsWith the inspection in this section, TPCEG concluded as followed:–3GPP NR RIT can fulfill the requirement. –3GPP LTE RIT can fulfill the requirement.II-FQuestions and feedback to WP 5D and/or the proponents or other IEGsThe minimum requirements of 3GPP NR RIT in the test environment of Dense Urban-eMBB for configuration B (30?GHz) cannot meet the requirement as specified in Report ITU-R M.2410-0. However, 3GPP NR RIT can still fulfil the requirement if the penetration loss condition is changed from “20% high loss, 80% low loss” to “100% low loss,” base on the self-Evaluation from 3GPP.II-GIn the interim report, kindly provide the proposed next steps towards the final report to be sent to WP 5D for the February 2020 meetingThis report is submitted as complete and final.Part III: ConclusionIII-ACompleteness of submissionTrans-Pacific Evaluation Group finds that the submission from 3GPP, Korea, and China are ‘complete’ according to ITU-R Acknowledgements to proponents, i.e.?5D/TEMP/792?(3GPP), 5D/TEMP/795?(Korea), and 5D/TEMP/791?(China), under Step 3 of the IMT-2020 process.III-BCompliance with requirementsThese are the main conclusions on the Trans-Pacific Evaluation Group evaluation of the evaluated proposal. The overall assessments are summarized in Table III-B.1 with referring the related sections for evaluations details.The other compliance templates for service, spectrum, and technical performance are also elaborated in this section.III-B.1Overall complianceTable III-B.1Trans-Pacific Evaluation Group assessment of compliance with requirementsCharacteristic for evaluationTPCEG assessment for NR RITTPCEG assessment for LTE RITSectionPeak data rateRequirements fulfilledRequirements fulfilledPart II-E.1Peak spectral efficiencyRequirements fulfilledRequirements fulfilledPart II-E.2User experienced data rateRequirements fulfilledRequirements fulfilledPart II-E.35th percentile user spectral efficiencyRequirements fulfilled Requirements fulfilledPart II-E.4Average spectral efficiencyRequirements fulfilledRequirements fulfilledPart II-E.5Area traffic capacityRequirements fulfilledRequirements fulfilledPart II-E.6User plane latencyRequirements fulfilledRequirements fulfilledPart II-E.7Control plane latencyRequirements fulfilledRequirements fulfilledPart II-E.8Connection densityRequirements fulfilledRequirements fulfilledPart II-E.9Energy efficiencyRequirements fulfilledRequirements fulfilledPart II-E.10ReliabilityRequirements fulfilledNot applicablePart II-E.11MobilityRequirements fulfilledRequirements fulfilledPart II-E.12Mobility interruption timeRequirements fulfilledRequirements fulfilledPart II-E.13BandwidthRequirements fulfilledRequirements fulfilledPart II-E.14Support of wide range of servicesRequirements fulfilledRequirements fulfilledPart II-E.15Supported spectrum band(s)/range(s)Requirements fulfilledRequirements fulfilledPart II-E.16III-B.2Detailed compliance templatesIII-B.2.1 Compliance template for servicesProvision of compliance template for services (Section 5.2.4.1 of Report ITU-R M.2411)Service capability requirementsEvaluator’s comments5.2.4.1.1Support for wide range of servicesIs the proposal able to support a range of services across different usage scenarios (eMBB, URLLC, and mMTC)?: YES / NOSpecify which usage scenarios (eMBB, URLLC, and mMTC) the candidate RIT or candidate SRIT can support.(1)Both LTE RIT and NR RIT can support the usage scenario of eMBB, mMTC, and URLLC with the evaluation results in this evaluation report.(1)Refer to the process requirements in IMT-2020/2.III-B.2.2 Compliance template for spectrumSpectrum capability requirementsEvaluator’s comments5.2.4.2.1Frequency bands identified for IMTIs the proposal able to utilize at least one frequency band identified for IMT in the ITU Radio Regulations?: YES / NOSpecify in which band(s) the candidate RIT or candidate SRIT can be deployed.Both LTE RIT and NR RIT can support the frequency bands identified for IMT with the evaluation results in this evaluation report.5.2.4.2.2Higher Frequency range/band(s)Is the proposal able to utilize the higher frequency range/band(s) above 24.25 GHz?: YES / NOSpecify in which band(s) the candidate RIT or candidate SRIT can be deployed.Details are provided in Section II-E.16.Both LTE RIT and NR RIT can support the higher frequency range/band(s) with the evaluation results in this evaluation report.III-B.2.3 Compliance template for technical performanceIII-B.2.3.1 NR RIT ResultsMinimum technical performance requirements item (5.2.4.3.x), units, and ReportITU-R M.2410-0 section reference(1)CategoryRequired valueValue(2)Requirement met?Comments(3)Usage scenarioTest environmentDownlink or uplink5.2.4.3.1Peak data rate (Gbit/s)(4.1)eMBB-Downlink2038.42~174.76YesNoc.f.II-E.1Uplink104.27~40.5YesNo5.2.4.3.2Peak spectral efficiency (bit/s/Hz)(4.2)eMBB-Downlink3031.8~48.6YesNoc.f.II-E.2Uplink1520~25.3YesNo5.2.4.3.3User experienced data rate (Mbit/s)(4.3)eMBBDense Urban – eMBBDownlink100>100(5)YesNoc.f.II-E.3Not fulfilled in config-B, c.f. explanationUplink50>50(5)YesNo5.2.4.3.45th percentile user spectral efficiency (bit/s/Hz)(4.4)eMBBIndoor Hotspot – eMBBDownlink0.30.31~0.84YesNoc.f.II-E.4Uplink0.210.19~0.48YesNoeMBBDense Urban – eMBBDownlink0.2250.02~0.51YesNoc.f.II-E.4Not fulfilled in config-B, c.f. explanationUplink0.150.015~0.49YesNoeMBBRural – eMBBDownlink0.120.12~0.53YesNoc.f.II-E.4Uplink0.0450.07~0.55YesNo5.2.4.3.5Average spectral efficiency (bit/s/Hz/ TRxP)(4.5)eMBBIndoor Hotspot – eMBBDownlink9 7.5~18.2YesNoc.f.II-E.5Uplink6.75 5.19~12.3YesNoeMBBDense Urban – eMBBDownlink7.8 8.4~16.7YesNoc.f.E-II.5Not fulfilled in Config-B, c.f. explanationUplink5.4 5.7~11.7YesNoeMBBRural – eMBBDownlink3.3 5~16.2YesNoc.f.E-II.5Uplink1.6 4~13.2YesNoc.f.E-II.55.2.4.3.6Area traffic capacity (Mbit/s/m2)(4.6)eMBBIndoor-Hotspot – eMBBDownlink10>10(5)YesNoc.f.E-II.65.2.4.3.7User plane latency(ms)(4.7.1)eMBB-Uplink and Downlink4<4YesNoc.f.E-II.7URLLC-Uplink and Downlink1<1YesNoc.f.E-II.75.2.4.3.8Control plane latency (ms)(4.7.2)eMBB--20<20YesNoc.f.E-II.8URLLC--20<20YesNoc.f.E-II.85.2.4.3.9Connection density (devices/km2)(4.8)mMTCUrban Macro – mMTCUplink1 000 000 >1 000 000YesNoc.f.E-II.95.2.4.3.10Energy efficiency(4.9)eMBB--Capability to support a high sleep ratio and long sleep durationSupportYesNoc.f.E-II.105.2.4.3.11Reliability(4.10)URLLCUrban Macro –URLLCUplink or Downlink1-10?5 success probability of transmitting a layer 2 PDU (protocol data unit) of size 32 bytes within 1 ms in channel quality of coverage edge> 1-10?5YesNoc.f.E-II.115.2.4.3.12Mobility classes(4.11)eMBBIndoor Hotspot – eMBBUplinkStationary, PedestrianSupportYesNoc.f.E-II.12eMBBDense Urban – eMBBUplinkStationary, Pedestrian,Vehicular (up to 30 km/h)SupportYesNoc.f.E-II.12eMBBRural – eMBBUplinkPedestrian, Vehicular, High speed vehicularSupportYesNoc.f.E-II.125.2.4.3.13MobilityTraffic channel link data rates (bit/s/Hz)(4.11)eMBBIndoor Hotspot – eMBBUplink1.5 (10?km/h)1.5315~1.6505YesNoc.f.E-II.13eMBBDense Urban – eMBBUplink1.12 (30?km/h)2.0048~2.069YesNoc.f.E-II.13eMBBRural – eMBBUplink0.8 (120?km/h)2.092~3.4685YesNoc.f.E-II.130.45 (500?km/h)1.045~3.4676YesNoc.f.E-II.135.2.4.3.14Mobility interruption time (ms) (4.12)eMBB and URLLC--00YesNoc.f.E-II.145.2.4.3.15Bandwidth and Scalability(4.13)---At least 100?MHzSupportYesNoc.f.II-E.16Up to 1?GHzSupportYesNoc.f.II-E.16Support of multiple different bandwidth values(4)SupportYesNoc.f.II-E.16(1) As defined in Report ITU-R M.2410-0.(2) According to the evaluation methodology specified in Report ITU-R M.2412-0.(3)Proponents should report their selected evaluation methodology of the Connection density, the channel model variant used, and evaluation configuration(s) with their exact values (e.g. antenna element number, bandwidth, etc.) per test environment, and could provide other relevant information as well. For details, refer to Report ITU-R M.2412-0, in particular, § 7.1.3 for the evaluation methodologies, § 8.4 for the evaluation configurations per each test environment, and Annex 1 on the channel model variants.(4)Refer to § 7.3.1 of Report ITU-R M.2412-0.(5)With sufficient bandwidthIII-B.2.3.1 LTE RIT ResultsMinimum technical performance requirements item (5.2.4.3.x), units, and ReportITU-R M.2410-0 section reference(1)CategoryRequired valueValue(2)Requirement met?Comments(3)Usage scenarioTest environmentDownlink or uplink5.2.4.3.1Peak data rate (Gbit/s)(4.1)eMBB-Downlink2021.56~28.4YesNoc.f.II-E.1Uplink102.688~13.5872YesNo5.2.4.3.2Peak spectral efficiency (bit/s/Hz)(4.2)eMBB-Downlink3043.292~44.38YesNoc.f.II-E.2Uplink1517.842~21.23YesNo5.2.4.3.3User experienced data rate (Mbit/s)(4.3)eMBBDense Urban – eMBBDownlink100>100(5)YesNoc.f.II-E.3Not fulfilled in config-B, c.f. explanationUplink50>50(5)YesNo5.2.4.3.45th percentile user spectral efficiency (bit/s/Hz)(4.4)eMBBIndoor Hotspot – eMBBDownlink0.30.19~0.34YesNoc.f.II-E.4Uplink0.210.19~0.25YesNoeMBBDense Urban – eMBBDownlink0.2250.23~0.3YesNoc.f.II-E.4Not fulfilled in config-B, c.f. explanationUplink0.150.36~0.49YesNoeMBBRural – eMBBDownlink0.120.27~0.32 YesNoc.f.II-E.4Uplink0.0450.15~0.3YesNo5.2.4.3.5Average spectral efficiency (bit/s/Hz/ TRxP)(4.5)eMBBIndoor Hotspot – eMBBDownlink9 7~9.12YesNoc.f.II-E.5Uplink6.75 6.12~7.17YesNoeMBBDense Urban – eMBBDownlink7.8 7.9~16.7YesNoc.f.E-II.5Not fulfilled in Config-B, c.f. explanationUplink5.4 5.7~11.72YesNoeMBBRural – eMBBDownlink3.3 10~11.5YesNoc.f.E-II.5Uplink1.6 5.4~10.4YesNoc.f.E-II.55.2.4.3.6Area traffic capacity (Mbit/s/m2)(4.6)eMBBIndoor-Hotspot – eMBBDownlink10>10(5)YesNoc.f.E-II.65.2.4.3.7User plane latency(ms)(4.7.1)eMBB-Uplink and Downlink4<4YesNoc.f.E-II.7URLLC-Uplink and Downlink1<1YesNoc.f.E-II.75.2.4.3.8Control plane latency (ms)(4.7.2)eMBB--20<20YesNoc.f.E-II.8URLLC--20<20YesNoc.f.E-II.85.2.4.3.9Connection density (devices/km2)(4.8)mMTCUrban Macro – mMTCUplink1 000 000 >1 000 000YesNoc.f.E-II.95.2.4.3.10Energy efficiency(4.9)eMBB--Capability to support a high sleep ratio and long sleep durationSupportYesNoc.f.E-II.105.2.4.3.11Reliability(4.10)URLLCUrban Macro –URLLCUplink or Downlink1-10?5 success probability of transmitting a layer 2 PDU (protocol data unit) of size 32 bytes within 1 ms in channel quality of coverage edgeNot AvailableYesNoc.f.E-II.115.2.4.3.12Mobility classes(4.11)eMBBIndoor Hotspot – eMBBUplinkStationary, PedestrianSupportYesNoc.f.E-II.12eMBBDense Urban – eMBBUplinkStationary, Pedestrian,Vehicular (up to 30 km/h)SupportYesNoc.f.E-II.12eMBBRural – eMBBUplinkPedestrian, Vehicular, High speed vehicularSupportYesNoc.f.E-II.125.2.4.3.13MobilityTraffic channel link data rates (bit/s/Hz)(4.11)eMBBIndoor Hotspot – eMBBUplink1.5 (10?km/h)1.662~1.6787YesNoc.f.E-II.13eMBBDense Urban – eMBBUplink1.12 (30?km/h)2.1305~2.2032YesNoc.f.E-II.13eMBBRural – eMBBUplink0.8 (120?km/h)2.0847~3.8143YesNoc.f.E-II.130.45 (500?km/h)1.0393~3.1157YesNoc.f.E-II.135.2.4.3.14Mobility interruption time (ms) (4.12)eMBB and URLLC--00YesNoc.f.E-II.145.2.4.3.15Bandwidth and Scalability(4.13)---At least 100?MHzSupportYesNoc.f.II-E.16Up to 1?GHzSupportYesNoc.f.II-E.16Support of multiple different bandwidth values(4)SupportYesNoc.f.II-E.16(1) As defined in Report ITU-R M.2410-0.(2) According to the evaluation methodology specified in Report ITU-R M.2412-0.(3)Proponents should report their selected evaluation methodology of the Connection density, the channel model variant used, and evaluation configuration(s) with their exact values (e.g. antenna element number, bandwidth, etc.) per test environment, and could provide other relevant information as well. For details, refer to Report ITU-R M.2412-0, in particular, § 7.1.3 for the evaluation methodologies, § 8.4 for the evaluation configurations per each test environment, and Annex 1 on the channel model variants.(4)Refer to § 7.3.1 of Report ITU-R M.2412-0.(5)With sufficient bandwidthIII-B.3 Number of test environments meeting all IMT-2020 requirementsIII-B.3.1NR RIT AssessmentThis report concludes that NR RIT can fulfill IMT-2020 requirements specified in Report ITU-R M.2410 for three usage scenario with five test environments: –Indoor Hotspot-eMBB–Dense Urban-eMBB–Rural-eMBB–Urban Macro-mMTC–Urban Macro-URLLC This conclusion is supported by the assessments in Table III-B.3.1, which shows the summary of the evaluation results and study in Part II.Table III-B.3.1Trans-Pacific Evaluation Group assessments for NR RITeMBB, Indoor HotspoteMBB, Dense UrbaneMBB, RuralmMTCUrban MacroURLLCUrban MacroCFG ACFG BCFG CCFG ACFG BCFG ACFG BCFG C--1Peak Data Rate◎◎◎2Peak spectral efficiency◎◎◎3User Experienced Data Rate◎◎45th percentile user spectral efficiency◎◎◎◎※◎◎◎5Average spectral efficiency◎◎◎◎◎◎◎◎6Area Traffic Capacity◎◎◎7Energy efficiency◎◎◎8Mobility◎N/AN/A◎N/A◎◎N/A9User plane latency◎◎◎◎10Control plane latency◎◎◎◎11Mobility interruption time◎◎◎◎12Reliability◎13Connection density◎Fulfilled Test Environment◎ : Fulfilled　　　N/A : Not Available　　　※ : Issue Founded　　　: Checked and FulfilledIII-B.3.2LTE RIT AssessmentThis report concludes that LTE RIT can fulfil IMT-2020 requirements specified in Report ITU-R M.2410 for two usage scenario with four test environments: –Indoor Hotspot-eMBB–Dense Urban-eMBB–Rural-eMBB–Urban Macro-mMTCThis conclusion is supported by the assessments in Table III-B.3.2, which shows the summary of the evaluation results and study in Part II.Table III-B.3.2Trans-Pacific Evaluation Group assessments for LTE RITeMBB, Indoor HotspoteMBB, Dense UrbaneMBB, RuralmMTCUrban MacroURLLCUrban MacroCFG ACFG BCFG CCFG ACFG BCFG ACFG BCFG C1Peak Data Rate◎◎◎2Peak spectral efficiency◎◎◎3User Experienced Data Rate◎N/A45th percentile user spectral efficiency◎N/AN/A◎N/A◎◎◎5Average spectral efficiency◎N/AN/A◎N/A◎◎◎6Area Traffic Capacity◎N/AN/A7Energy efficiency◎◎◎8Mobility◎N/AN/A◎N/A◎◎N/A9User plane latency◎◎◎◎10Control plane latency◎◎◎◎11Mobility interruption time◎◎◎◎12ReliabilityN/A13Connection density◎Fulfilled Test Environment◎ : Fulfilled　　　N/A : Not Available　　　※ : Issue Founded　　　: Checked and FulfilledIII-DSummary of the Evaluation ReportWhich test environments have been considered in the Final Evaluation Report? What is outcome of the evaluation?III-D.1Evaluation Summary for NR RITFor 3GPP NR RIT, the performances of all the requirements specified in Report ITU-R M.2410 are evaluated and checked in this report. The evaluation results show that all the evaluated performances can fulfil the minimum technical requirements.Test environmentDoes the Evaluation Report indicate that the minimum technical performance requirements are met in the test environment? Indoor Hotspot-eMBB Yes No Partial evaluation Dense Urban-eMBB Yes No Partial evaluation Rural-eMBB Yes No Partial evaluation Urban Macro–mMTC Yes No Partial evaluation Urban Macro–URLLC Yes No Partial evaluationIII-D.2Evaluation Summary for LTE RIT For 3GPP LTE RIT, the performances of most the requirements specified in Report ITU-R M.2410 are evaluated and checked in this report. This evaluation results do not endorse the performance of Reliability for LTE RIT in Urban Macro-URLLC test environment. Besides that, the evaluation results show that the evaluated performances of LTE RIT in the test environments of Indoor Hotspot-eMBB, Dense Urban-eMBB, Rural-eMBB, and Urban Macro-mMTC, can fulfil the minimum technical requirements.Test environmentDoes the Evaluation Report indicate that the minimum technical performance requirements are met in the test environment? Indoor Hotspot-eMBB Yes No Partial evaluation Dense Urban-eMBB Yes No Partial evaluation Rural-eMBB Yes No Partial evaluation Urban Macro–mMTC Yes No Partial evaluation Urban Macro–URLLC Yes No Partial evaluationAnnex A Evaluation Methodology, Assumption, and ConfigurationA-1Evaluation MethodologyA-1.1Peak Spectral Efficiency and Peak Data RateA-1.1.1IntroductionAccording to Report ITU-R M.2412, more detailed evaluation methodologies are defined. Also, in Report ITU-R M.2410, the minimum requirements of peak spectral efficiency and peak data rate are provide and summarized in Table A-1.1.1.Table A-1.1.1The requirements of peak spectral efficiency and peak data ratePerformance MetricEvaluation MethodScenarioMinimum RequirementDownlinkUplinkPeak Spectral Efficiency (bits/s/Hz)AnalyticalN/A.3015Peak Data Rate (Gbit/s)N/A.2010In this section, we briefly review the analytical evaluation methodology for peak spectral efficiency and peak data rate, the evaluation results of peak spectral efficiency and peak data rate for both NR and LTE component RITs are provided.A-1.1.2Methodology for Peak Data Rate and Spectral Efficiency EvaluationBesides the definitions and evaluation methodologies in Report ITU-R M.2412, there was also discussion in 3GPP RAN1 RP-172172. 3GPP has discussed the approximate data rate for a given number of aggregated component carriers in a band or band combination. It could be a starting point for potential peak data calculation. The calculation method is show as follows:whereinJ is the number of aggregated component carriers in a band or band combinationRmax is the highest coding rateFor the j-th CC, is the maximum number of layers is the maximum modulation order is the scaling factorThe scaling factor can at least take the values 1 and 0.75 is signalled per band and per band per band combination as per UE capability signalling is the numerology (as defined in TS38.211)is the average OFDM symbol duration in a subframe for numerology , i.e. . Note that normal cyclic prefix is assumed is the maximum RB allocation in bandwidth with numerology, as given in TR 38.817-01 section 4.5.1 (to be eventually defined in TS 38.101), where is the UE supported maximum bandwidth in the given band or band combinationis the overhead calculated as the average ratio of the number of REs occupied by L1/L2 control, Synchronization Signal, PBCH, reference signals and guard period (for TDD), etc. with respect to the total number of REs in effective bandwidth time product as given by αj is the normalized scalar considering the DL/UL ratio; for FDD αj=1 for DL and UL; and for TDD and other duplexing αj for DL and UL is calculated based on the DL/UL configuration. The peak spectral efficiency can be derived from the peak data equation for a specific component carrier and its corresponding bandwidth:The NR transmission bandwidth configuration NRB for each BS channel bandwidth and subcarrier spacing is specified in Table A-1.1.2 for FR1 and Table A-1.1.3 for FR2.Table A-1.1.2NR Transmission bandwidth configuration NRB for FR1SCS [kHz]BS / UE Channel bandwidths [MHz]510152025304050607018090110015255279106133160216270N/AN/AN/AN/AN/A3011243851657810613316218921724527360N/A111824313851657993107121135NOTE 1: 70MHz and 90MHz are defined only as BS channel bandwidths in release 15.Table A-1.1.3NR Transmission bandwidth configuration NRB for FR2SCS [kHz]BS / UE Channel bandwidths [MHz]501002004006066132264N/A1203266132264The LTE transmission bandwidth configuration NRB for each BS channel bandwidth and subcarrier spacing is specified in Table A-1.1.4.Table A-1.1.4LTE Transmission bandwidth configuration NRBSCS [kHz]BS / UE Channel bandwidths [MHz]510152015255075100The detailed assumptions are provided in Annex A-2.2 and A-2.3.A-1.2Area Traffic Capacity and User Experienced Data RateA-1.2.1IntroductionAccording to Report ITU-R M.2412, more detailed evaluation methodologies are defined. Also, in Report ITU-R M.2410, the minimum requirements of area traffic capacity and user experienced data rate are provide and summarized in Table A-1.2.1 and Table A-1.2.2 respectively.Table A SEQ Table \* ARABIC \s 1 1.2.1The requirement of area traffic capacityTest environmentDownlink (Mbit/s)Indoor Hotspot – eMBB10Table A1.2.2 The requirements of user experienced data rateTest environmentDownlink (Mbit/s)Uplink (Mbit/s)Dense Urban – eMBB10050In Report ITU-R M.2410, the definition for area traffic capacity and user experienced data rate are shown as follows.Carea = ρ × W × SEavgwhereinρ is the TRxP density (TRxP/m2);W is the channel bandwidth;SEavg is the average spectral efficiency as defined in subsection 4.5 in Report ITU-R M.2410.Ruser = W × SEuserwhereinW is the channel bandwidth;SEuser is the 5th percentile user spectral efficiency as defined in subsection 4.4 in Report ITU-R M.2410.In this section, we briefly review the analytical evaluation methodology for area traffic capacity and user experienced data rate, the evaluation results of area traffic capacity and user experienced data rate for both NR and LTE are provided.A-1.2.2Methodology for Area Traffic Capacity EvaluationAccording to the Figure 1 illustrated in Report ITUR?M.2412, The Indoor Hotspot eMBB deployment is shown in Figure A-1.2.1. Figure A-1.2.1 Indoor Hotspot sites layoutBased on this deployment scenario 12 cell sites are deployed over an indoor area of S=120×(15+20+15)=6000 m2. For the case where we have 1 TRxP per cell site i.e., 12 TRxP deployment, we have ρ=12 TRxP/6000 m2=0.002 TRxP/m2 and for the case of 3 TRxP per cell-site i.e., 36 TRxP deployment, we have 36 TRxP/6000 m2=0.006 TRxP/m2.Based on the corresponding simulation results of SEavg, W, ρ for a deployment scenario, the evaluation results of area traffic capacity for Indoor Hotspot-eMBB test environments are analysed and shown in Table II-E.6.1 to Table II-E.6.3. Note that the values in brackets denote the required bandwidth to achieve the target area traffic capacity for downlink.A-1.2.3Methodology for User Experienced Data RateBased on the corresponding simulation results of SEuser, W for a deployment scenario, the evaluation results of user experienced data rate for Dense Urban-eMBB test environments are analysed and shown in Table II-E.3.1 to Table II-E.3.4. Note that the values in brackets denote the required bandwidth to achieve the target user experienced data rate for downlink and uplink.A-2Evaluation Assumptions and Configuration A-2.1 Base line ConfigurationTable A-2.1Configuration for Indoor Hotspot-eMBBIndoor HotspotITU-R M.2412Configuration AConfiguration BConfiguration CCarrier Frequency4 GHz30 GHz70 GHzTransmit Power per TRxP24 dBm for 20 MHz21 dBm for 10 MHz23 dBm for 80 MHz20 dBm for 40 MHz21 dBm for 80 MHz18 dBm for 40 MHzUE Power Class23dBm23dBm21dBmISD20m20m20mNumber of antenna elements per TRxPUp to 256 Tx/RxUp to 256 Tx/RxUp to 1024 Tx/RxNumber of UE antenna elementsUp to 8 Tx/RxUp to 32 Tx/RxUp to 64 Tx/RxUE speeds of interest100% indoor, 3 km/h100% indoor, 3 km/h100% indoor, 3 km/hBS/UE antenna element gain5/0 dBi5/5 dBi5/5 dBiSimulation bandwidth20 MHz for TDD, 10 MHz+10 MHz for FDD80 MHz for TDD, 40 MHz+40 MHz for FDD80 MHz for TDD, 40 MHz+40 MHz for FDDTable A-2.2Configuration for Dense Urban-eMBBDense UrbanITU-R M.2412 (Evaluation)Configuration AConfiguration BConfiguration C (for Multi-Band Case)Carrier Frequency1 layer (Macro) with 4 GHz1 layer (Macro) with 30 GHz4 GHz and 30 GHz available in macro and micro layers (1 or 2 layers)Transmit Power per TRxP44 dBm for 20 MHz, 41 dBm for 10 MHz40 dBm for 80 MHz, 37 dBm for 40 MHz4GHz30GHz44 dBm for 20 MHz; 41 dBm for 10 MHz (Ma)33 dBm for 20 MHz; 30 dBm for 10 MHz (Mi)40 dBm for 80 MHz; 37 dBm for 40 MHz (Ma)33 dBm for 80 MHz; 30 dBm for 40 MHz (Mi)UE Power Class23dBm23dBm23dBm (for Both)Penetration Loss20% high loss, 80% low loss20% high loss, 80% low loss20% high loss, 80% low lossISD200m200m200m (Macro)Number of antenna elements per TRxPUp to 256 Tx/RxUp to 256 Tx/RxUp to 256 Tx/RxNumber of UE antenna elementsUp to 8 Tx/RxUp to 32 Tx/RxUp to 8/32 Tx/Rx (for 4/30GHz)UE speeds of interest80% indoor, 3 km/h, 20% outdoor, 30 km/h80% indoor, 3 km/h, 20% outdoor, 30 km/h80% indoor, 3 km/h, 20% outdoor, 30 km/hBS/UE antenna element gain8/0 dBi8/5 dBi8/0 dBi8/5 dBiSimulation bandwidth20 MHz for TDD, 10 MHz+10 MHz for FDD80 MHz for TDD, 40 MHz+40 MHz for FDD20 MHz for TDD, 10 MHz+10 MHz for FDD80 MHz for TDD, 40 MHz+40 MHz for FDDTable A-2.3Configuration for Rural-eMBBRuralITU-R M.2412Configuration AConfiguration BConfiguration C (LMLC)Carrier Frequency700 MHz4 GHz700MHzTransmit Power per TRxP49 dBm for 20 MHz46 dBm for 10 MHz49 dBm for 20 MHz46 dBm for 10 MHz49 dBm for 20 MHz46 dBm for 10 MHzUE Power Class23dBm23dBm23dBmPenetration Loss100 low loss100 low loss100 low lossISD1732m1732m6000mNumber of antenna elements per TRxPUp to 64 Tx/RxUp to 256 Tx/RxUp to 64 Tx/RxNumber of UE antenna elementsUp to 4 Tx/RxUp to 8 Tx/RxUp to 4 Tx/RxUE speeds of interest50% indoor, 3 km/h, 50% outdoor, 120 km/h50% indoor, 3 km/h, 50% outdoor, 120/500 km/h40% indoor, 3 km/h, 40%/20% outdoor, 3/30 km/hBS/UE antenna element gain8/0 dBi8/0 dBi8/0 dBiSimulation bandwidth20 MHz for TDD, 10 MHz+10 MHz for FDD20 MHz for TDD, 10 MHz+10 MHz for FDD20 MHz for TDD, 10 MHz+10 MHz for FDDA-2.2Evaluation Assumption for NRA-2.2.1NR DownlinkTable A-2.4 NR Parameters for DL peak spectral efficiency and peak data rate evaluationParametersValuesRemarksMax. number of layersFor FR1: 8For FR2: 6Highest modulation order8256QAMScaling factor of modulation 1Max. coding rate Rmax948/1024 = 0.92580, 1, 2, 3SCS = 2μ×15 kHzSee Table 8.1.1-2 for FR1 and FR2 for specific component carrier bandwidth and SCS.The maximum number of RBs for the specific component carrier bandwidth and SCS is used.Table A-2.5 Overhead assumption for NR DL evaluationApplied duplexingFR1FR2OHFDD, TDD (DDDSU)PDCCH: CORESET of 24 PRBs (4 CCE) in every slot 12 RE/PRB/slotTRS burst of 2 slots with periodicity of 20ms and occupies 52 PRBs12 RE/PRB/20 msDMRS: Type 2, 16 RE/PRB/slot for 8 layersCSI-RS: 8 CSI-RS ports with periodicity of 20ms8 RE/PRB/20 ms1 SS/PBCH blocks (SSB) per 20ms; one SSB occupies 960REs = 4 OFDM symbols × 20 PRB × 12 REs/PRB NOTE1: if the channel bandwidth is less than the bandwidth of SSB, then SSB is not transmitted and the overhead of SS/PBCH block is zero.NOTE2: If the channel bandwidth is less than TRS bandwidth, the TRS bandwidth is assumed to be equal to the channel bandwidth.PDCCH: CORESET of 24 PRBs (4 CCE) in every slot12 RE/PRB/slotTRS burst of 2 slots with periodicity of 10ms and occupies 52 PRBs12 RE/PRB/slotDMRS: Type 2, 12 RE/PRB/slot for 6 layers CSI-RS: 8 CSI-RS ports with periodicity of 10ms 8 RE/PRB/10 ms8 SSB per 20ms; one SSB occupies 960REs = 4 OFDM symbols × 20 PRB × 12 REs/PRBPTRS: 1 port, frequency density is 4 PRB, and time domain density is 1 symbolCSI-RS for BM: 1 CSI-RS port with periodicity of 10ms2 RE/PRB/10msNOTE: If the channel bandwidth is less than TRS bandwidth, the TRS bandwidth is assumed to be equal to the channel bandwidth.A-2.2.2 NR UplinkTable A-2.6 NR Parameters for UL peak spectral efficiency and peak data rate evaluationParametersValuesRemarksMax. number of layers4Highest modulation order8256QAMScaling factor of modulation 1Max. coding rate Rmax948/1024 = 0.92580, 1, 2, 3SCS = 2μ×15 kHzSee Table 8.1.1-2 for FR1 and FR2 for specific component carrier bandwidth and SCS.The maximum number of RBs for the specific component carrier bandwidth and SCS is used.Table A-2.7 Overhead assumption for NR UL evaluationApplied duplexingFR1FR2OHFDD, TDD (DDDSU)PUCCH: short PUCCH with 1 PRB and 1 symbol in every UL slot; 12 RE/slotDMRS: Type I, one complete symbol; 12 RE/PRB/slot SRS: 1 symbol with periodicity of 10ms for FDD; 1 symbol with periodicity of 20ms for TDDPUCCH: short PUCCH with 1 PRB and 1 symbol in every UL slot; 12 RE/slotDMRS: Type I, one complete symbol; 12 RE/PRB/slot SRS: 1 symbol with periodicity of 5msPTRS: 2 ports PTRS, frequency density is 4 PRB, and time domain density is 1 symbolA-2.3 Evaluation Assumption for LTEA-2.3.1 LTE DownlinkTable A-2.8 LTE Parameters for DL peak spectral efficiency and peak data rate evaluationParametersValuesRemarksMax. number of layers8Highest modulation order810256QAM1024QAMScaling factor of modulation 1Max. coding rate RmaxAccording to Transport block size (TBS) table defined in TS36.213See Table 8.1.2-2 for specific component carrier bandwidth.The maximum number of RBs for the specific component carrier bandwidth is used.Table A-2.9 Overhead assumption for LTE DL evaluationApplied duplexingFR1OH FDD, TDDPBCH: 240 RE per 10ms (not include CRS)PSS/SSS: 288 RE per 10msPDCCH: 1 complete symbolsCRS: 1 port for non-MBSFN; 6 RE/PRB; 0 port for MBSFN.DMRS: 8ports, 24RE per PRBMBSFN: 6 subframes for MBSFN for FDD; 4 subframes for MBSFN for TDD.A-2.3.2 LTE UplinkTable A-2.10 LTE Parameters for UL peak spectral efficiency and peak data rate evaluationParametersValuesRemarksMax. number of layers4Highest modulation order8256QAMScaling factor of modulation 1Max. coding rate RmaxAccording to Transport block size (TBS) table defined in TS36.213See Table 8.1.2-2 for specific component carrier bandwidth.The maximum number of RBs for the specific component carrier bandwidth is used.Table A-2.11Overhead assumption for LTE UL evaluationApplied duplexingFR1OH FDD, TDDPUCCH: 2 PRBs and 14 symbolsDMRS: 2 complete symbolsSRS: 1 symbol per 10msA-3Details of Evaluation Configurations and Results1Indoor Hotspot-eMBB2Dense Urban-eMBB3Rural-eMBB4Urban Macro-mMTC5Urban Macro-URLLC6MobilityA-4System Level Simulator CalibrationITRI has developed a system level simulator (SLS), named “WiSE”, to evaluate the metrics that need SLS simulation results such as 5th percentile user spectral efficiency, average spectral efficiency, mobility, connection density and reliability. WiSE simulator has been calibrated via Self evaluation calibration and the results are well aligned with other 3GPP companies. Part of the calibration results are shown in Figure A-4.1 to Figure A-4.4. The detailed simulation results can be found in Annex A-3. Currently, WiSE is equipped with NR R15 functions and has finished all the evaluation for eMBB, mMTC and URLLC. For interested companies, the free trial version of WiSE simulator can also be downloaded from that the calibration results of MEDIATEK are also aligned with 3GPP companies, and included in the curves of 3GPP RAN1 Members.Figure A-4.1Indoor Hotspot-eMBB CalibrationFigure A-4.2Dense Urban-eMBB CalibrationFigure A-4.3Rural-eMBB CalibrationFigure A-4.4Urban Macro-URLLC Calibration______________ ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download