《3GPP TR38.875 RedCap NR设备 R17.docx》由会员分享，可在线阅读，更多相关《3GPP TR38.875 RedCap NR设备 R17.docx（129页珍藏版）》请在课桌文档上搜索。
1、3GPPTR38.875V17.0,0(2021-03)TechnicalReport3rdGenerationPartnershipProject;TechnicalSpecificationGroupRadioAccessNetwork;StudyonsupportofreducedcapabilityNRdevices(Release17)为配Thepresentdocumenthasbeendevelopedwithinthe3rdGenerationPartnershipProjeci(3GPP)andmaybefurtherelaboratedforthepurposesof3GP
2、P.Thepresentdocumenthasnotbeensubjecttoanyapprovalprocessbythe3GPPOrganizationalPartnersandshallnotbeimplemented.ThisSpeciHcationisprovidedforfuturedevelopmentworkwithin3GPPonly.TheOrganizationalPartnersacceptnoliabilityforanyuseofthisSpecification.SpecificationsandReportsforimplementationofthe3GPPs
3、ystemshouldbeobtainedviathe3GPPOrganizationalPartnersPublicationsOffices.3GPPPostaladdress3GPPsupportofficeaddress650RoutedesLucioles-SophiaAntipolisValbonne-FRANCETel.:+33492944200Fax:+33493654716Internethttp:/www.3gpp.orgCOPyrightNOtifiCatiOnNopartmaybereproducedexceptasauthorizedbywrittenpermissi
4、on.Thecopyrightandtheforegoingrestrictionextendtoreproductioninallmedia.2021,3GPPOrganizationalPartners(ARIB,ATIS,CCSA,ETSI,TSDSLTTA,TTC).Allrightsreserved.UMTSisaTradeMarkofETSIregisteredforthebenefitofitsmembers3GPPisaTradeMarkofETSlregisteredforthebenefitofitsMembersandofthe3GPPOrganizationalPart
5、nersLTEisaTradeMarkofETSIregisteredforthebenefitofitsMembersandofthe3GPPOrganizationalPartnersGSMandtheGSMlogoareregisteredandownedbytheGSMAssociationContentsForeword41 Scope62 References63 Definitionsofterms,symbolsandabbreviations73.1 Terms73.2 Symbols73.3 Abbreviations74 Introduction75 Studyobjec
6、tives86 Evaluationmethodology96.1 EvaluationmethodologyforUEcomplexityreduction96.2 EvaluationmethodologyforUEpowersaving106.3 Evaluationmethodologyforcoveragerecovery146.4 Evaluationmethodologyfornetworkcapacityandspectralefficiency167 UEcomplexityreductionfeatures177.1 IntroductiontoUEcomplexityre
7、ductionfeatures177.2 ReducednumberofUERxZTxantennas177.2.1 Descriptionoffeature177.2.2 AnalysisofUEcomplexityreduction187.2.3 Analysisofperformanceimpacts207.2.4 AnalysisofcoexistencewithlegacyUEs207.2.5 Analysisofspecificationimpacts217.3 UEbandwidthreduction217.3.1 Descriptionoffeature217.3.2 Anal
8、ysisofUEcomplexityreduction217.3.3 Analysisofperformanceimpacts227.3.4 AnalysisofcoexistencewithlegacyUEs237.3.5 Analysisofspecificationimpacts237.4 Half-duplexFDDoperation237.4.1 Descriptionoffeature237.4.2 AnalysisofUEcomplexityreduction247.4.3 Analysisofperformanceimpacts247.4.4 Analysisofcoexist
9、encewithlegacyUEs257.4.5 Analysisofspecificationimpacts257.5 RelaxedUEprocessingtime257.5.1 Descriptionoffeature257.5.2 AnalysisofUEcomplexityreduction267.5.3 Analysisofperformanceimpacts277.5.4 AnalysisofcoexistencewithlegacyUEs277.5.5 Analysisofspecificationimpacts277.6 RelaxedmaximumnumberofMIMOl
10、ayers287.6.1 Descriptionoffeature287.6.2 AnalysisofUEcomplexityreduction287.6.3 Analysisofperformanceimpacts297.6.4 AnalysisofcoexistencewithlegacyUEs297.6.5 Analysisofspecificationimpacts297.7 Relaxedmaximummodulationorder297.7.1 Descriptionoffeature297.7.2 AnalysisofUEcomplexityreduction307.7.3 An
11、alysisofperformanceimpacts317.7.4 AnalysisofcoexistencewithlegacyUEs327.7.5 Analysisofspecificationimpacts327.8 CombinationsofUEcomplexityreductionfeatures327.8.1 Descriptionoffeaturecombinations327.8.2 AnalysisofUEcomplexityreduction327.8.3 Analysisofperformanceimpacts337.8.4 Analysisofcoexistencew
12、ithlegacyUEs347.8.5 Analysisofspecificationimpacts348 UEpowersavingfeatures348.1 IntroductiontoUEpowersavingfeatures348.2 ReducedPDCCHmonitoring358.2.1 Descriptionoffeature358.2.2 AnalysisofUEpowersaving358.2.3 Analysisofperformanceimpacts398.2.4 AnalysisofcoexistencewithlegacyUEs488.2.5 Analysisofs
13、pecificationimpacts488.3 ExtendedDRXforRRCInactiveand/orIdle488.3.1 Descriptionoffeature488.3.2 AnalysisofUEpowersaving498.3.3 AnalysisofupperandlowerboundofextendedDRXcycles498.3.4 AnalysisofmechanismsforextendedDRX508.4 RRMrelaxationforstationarydevices518.4.1 Descriptionoffeature518.4.2 RRMrelaxa
14、tioninRRCJDLEandRRCJNACTIVE518.4.3 RRMrelaxationinRRC_CONNECTED548.4.4 AnalysisofUEpowersaving559 Coveragerecovery569.1 Introductiontocoveragerecovery569.2 Coveragerecoveryevaluation569.2.1 Urbanscenarioat2.6GHz569.2.2 Ruralscenarioat0.7GHz589.2.3 Urbanscenarioat4GHz609.2.4 Indoorscenarioat28GHz629.
15、2.5 Summaryofcoveragerecoveryevaluation649.3 CoveragerecoveryforPUSCH659.3.1 Descriptionofcoveragerecoveryfeatures659.3.2 AnalysisofcoexistencewithlegacyUEs659.3.3 Analysisofspecificationimpacts659.4 CoveragerecoveryforPDSCH659.4.1 Descriptionofcoveragerecoveryfeatures659.4.2 Analysisofcoexistencewi
16、thlegacyUEs669.4.3 Analysisofspecificationimpacts669.5 CoveragerecoveryforPDCCH669.5.1 Descriptionofcoveragerecoveryfeatures669.5.2 AnalysisofcoexistencewithlegacyUEs669.5.3 Analysisofspecificationimpacts671()Definitionandconstrainingofreducedcapabilities671.1 1Definitionofreducedcapabilities671.2 2
17、Constrainingofreducedcapabilities691.2.1 1Descriptionoffeature6911 UEidentificationandaccessrestrictions7011.1 UEidentification7011.1.1 Descriptionoffeature7011.2 Accessrestrictions7511.2.1 Descriptionoffeature7511.2.2 Cellbarring7511.2.3 Unifiedaccesscontrol7511.2.4 RRCconnectionreject7611.2.5 Anal
18、ysisofcoexistencewithlegacyUEs7611.2.6 Analysisofspecificationimpacts7612 Impacttonetworkcapacityandspectralefficiency7613 Conclusionsandrecommendations77Annex A: UEpowersavingresults80A.lUEpowersavingresultsforFRl80A.2UEpowersavingresultsforFR283Annex B: PDCCHblockingrateresults85BJPDCCHblockingrat
19、eresultsforFRl85Annex C: B.2PDCCHblockingrateresultsforFR292Annex D: 1.inkbudgetevaluationresults96C.lUrbanscenarioat2.6GHz96C.2Ruralscenarioat0.7GHz101C.3Urbanscenarioat4GHz106C.4Indoorscenarioat28GHz110Annex E: System-levelsimulationevaluationresults115Annex F: Companyinputstopowersavingevaluation
20、inRAN2124E.lExtendedDRXforRRCInactiveand/orIdle124E.l.lPowersavingevaluationin8124E.1.2Powersavingevaluationin9126E.2RRMrelaxationforstationarydevices128E.2.1RRMrelaxationevaluationin9128E.2.2RRMrelaxationinidle/inactivemodeforservingcellin10128Annex G: Changehistory133ForewordThisTechnicalReporthas
21、beenproducedbythe3rdGenerationPartnershipProject(3GPP).ThecontentsofthepresentdocumentaresubjecttocontinuingworkwithintheTSGandmaychangefollowingformalTSGapproval.ShouldtheTSGmodifythecontentsofthepresentdocument,itwillbere-releasedbytheTSGwithanidentifyingchangeofreleasedateandanincreaseinversionnu
22、mberasfollows:Versionx.y.zwhere:xthefirstdigit:1 presentedtoTSGforinformation;2 presentedtoTSGforapproval;3 orgreaterindicatesTSGapproveddocumentunderchangecontrol.ytheseconddigitisincrementedforallchangesofsubstance,i.e.technicalenhancements,corrections,updates,etc.Zthethirddigitisincrementedwhened
23、itorialonlychangeshavebeenincorporatedinthedocument.Inthepresentdocument,modalverbshavethefollowingmeanings:shallindicatesamandatoryrequirementtodosomethingshallnotindicatesaninterdiction(prohibition)todosomethingTheconstructionsshallandshallnotareconfinedtothecontextofnormativeprovisions,anddonotap
24、pearinTechnicalReports.Theconstructionsmustand,mustnotarenotusedassubstitutesforshalland,shallnot.Theiruseisavoidedinsofaraspossible,andtheyarenotusedinanormativecontextexceptinadirectcitationfromanexternal,referenced,non-3GPPdocument,orsoastomaintaincontinuityofstylewhenextendingormodifyingtheprovi
25、sionsofsuchareferenceddocument.shouldindicatesarecommendationtodosomethingshouldnotindicatesarecommendationnottodosomethingmayindicatespermissiontodosomethingneednotindicatespermissionnottodosomethingTheconstruction,maynotisambiguousandisnotusedinnormativeelements.Theunambiguousconstructionsmightnot
26、orshallnotareusedinstead,dependinguponthemeaningintended.canindicatesthatsomethingispossiblecannotindicatesthatsomethingisimpossibleTheconstructionscanandcannotarenotsubstitutesformayandneednot.willindicatesthatsomethingiscertainorexpectedtohappenasaresultofactiontakenbyanagencythebehaviourofwhichis
27、outsidethescopeofthepresentdocumentwillnotindicatesthatsomethingiscertainorexpectednottohappenasaresultofactiontakenbyanagencythebehaviourofwhichisoutsidethescopeofthepresentdocumentmightindicatesalikelihoodthatsomethingwillhappenasaresultofactiontakenbysomeagencythebehaviourofwhichisoutsidethescope
28、ofthepresentdocumentmightnotindicatesalikelihoodthatsomethingwillnothappenasaresultofactionUkenbysomeagencythebehaviourofwhichisoutsidethescopeofthepresentdocumentInaddition:is(oranyotherverbintheindicativemood)indicatesastatementoffactisnot(oranyothernegativeverbintheindicativemood)indicatesastatem
29、entoffactTheconstructionsisandisnotdonotindicaterequirements.1 ScopeThisdocumentcapturesthefindingsfromthestudyitem,SludyonsupportofreducedcapabilityNRdevices2.ThestudyincludesidentificationandstudyofpotentialUEcomplexityreductiontechniquesandUEpowersavingandbatterylifetimeenhancementsforreducedcapa
30、bilityUEsinapplicableusecases,functionalitythatwillenabletheperformancedegradationofsuchcomplexityreductiontobemitigatedorlimited,principlesforhowtodefineandconstrainsuchreducedcapabilities,andfunctionalitythatwillallowdeviceswithreducedcapabilitiestobeexplicitlyidentifiabletonetworksandnetworksoper
31、atorsandallowoperatorstorestricttheiraccessifdesired.ThescopeofthestudyincludessupportforallFR1FR2bandsforFDDandTDDandcoexistencewithRel-15/16UEs.ThisstudyfocusesonSAmodeandsingleconnectivity.ThescopeofthestudydoesnotincludeLPWAusecases.2 ReferencesThefollowingdocumentscontainprovisionswhich,through
32、referenceinthistext,constituteprovisionsofthepresentdocument.- Referencesareeitherspecific(identifiedbydateofpublication,editionnumber,versionnumber,etc.)ornon-specific.- Foraspecificreference,subsequentrevisionsdonotapply.- Foranon-specificreference,thelatestversionapplies.Inthecaseofareferencetoa3
33、GPPdocument(includingaGSMdocument),anon-specificreferenceimplicitlyreferstothelatestversionofthatdocumentinthesameReleaseasthepresentdocument.1 3GPPTR21.9()5:Vocabularyfor3GPPSpecifications.2 3GPPRP-201677:RevisedSIDonsupportofreducedcapabilityNRdevices.3 3GPPR1-2009293:FLsummaryonRedCapevaluationre
34、sults.4 3GPPTR36.888:Studyonprovisionoflow-costMachine-TypeCommunications(MTC)UserEquipments(UEs)basedonLTE.5 3GPPTR38.830:StudyonNRcoverageenhancements,.6 3GPPTR38.840:StudyonUserEquipment(UE)powersavinginNR.7 3GPPR1-070674:LTEphysicallayerframeworkforperformanceverification,Orange,ChinaMobile,KPN,
35、NTTDoCoMo,Sprint,T-Mobile,Vodafone,TelecomItalia.8 3GPPR2-2009116:FurtherconsiderationsforeDRX,MediaTek.9 3GPPR2-2009620:RedCappowersavingenhancementst,Ericsson.10 3GPPR2-2100459:TPforTR38875onevaluationforRRMrelaxation,vivo,GuangdongGenius.11 3GPPR2-2101257:RRMmeasurementrelaxationforRedCapUE,Huawe
36、i,HiSiIicon.12 3GPPTS36.300:EvolvedUniversalTerrestrialRadioAccess(E-UTRA)andEvolvedUniversalTerrestrialRadioAccessNetwork(E-UTRAN);Overalldescription;Stage2.3 Definitionsofterms,symbolsandabbreviations3.1 TermsForthepurposesofthepresentdocument,thetermsgiveninTR21.9051andthefollowingapply.Atermdefi
37、nedinthepresentdocumenttakesprecedenceoverthedefinitionofthesameterm,ifany,inTR21.9051.RedCapUE:Forconvenienceonly,aRedCapUEreferstoanNRUEwithreducedcapabilitieswithdetailsdescribedherein.3.2 SymbolsForthepurposesofthepresentdocument,thefollowingsymbolsapply:3.3 AbbreviationsForthepurposesoftheprese
38、ntdocument,theabbreviationsgiveninTR21.90511andthefollowingapply.Anabbreviationdefinedinthepresentdocumenttakesprecedenceoverthedefinitionofthesameabbreviation,ifany,inTR21.9051.4 IntroductionTheusagescenariosthathavebeenidentifiedfor5Gareenhancedmobilebroadband(eMBB),massivemachine-typecommunicatio
39、n(mMTC),andUltra-ReliableandLowLatencycommunication(URLLC).Yetanotheridentifiedareaistimesensitivecommunication(TSC).Inparticular,mMTC,URLLCandTSCareassociatedwithnovelIoTusecasesthataretargetedinverticalindustries.ItisenvisagedthateMBB,mMTC,URLLCandTSCusecasesmayallneedtobesupportedinthesamenetwork
40、.Inthe3GPPstudyonself-evaluationtowardsIMT-2020submissionitwasconfirmedthatNB-IoTandLTE-MTC(a.k.a.eMTC)fulfiltheIMT-2020requirementsformMTCandcanbecertifiedas5Gtechnologies.ForURLLCsupport,URLLCfeatureswereintroducedinRelease15forbothLTEandNR,andNRURLLCisfurtherenhancedinRelease16withintheenhancedUR
41、LLC(eURLLC)andIndustrialIoTworkitems.Rel-16alsointroducedsupportforTime-SensitiveNetworking(TSN)and5GintegrationforTSCusecases.1. Oneimportantobjectiveof5Gistoenableconnectedindustries.5Gconnectivitycanserveascatalystfornextwaveofindustrialtransformationanddigitalization,whichimproveflexibility,enha
42、nceproductivityandefficiency,reducemaintenancecost,andimproveoperationalsafety.Devicesinsuchenvironmentincludee.g.pressuresensors,humiditysensors,thermometers,motionsensors,accelerometers,actuators,etc.Itisdesirabletoconnectthesesensorsandactuatorsto5Gradioaccessandcorenetworks.Themassiveindustrialw
43、irelesssensornetwork(IWSN)usecasesandrequirementsdescribedinTR22.804,TS22.104,TR22.832andTS22.261includenotonlyURLLCserviceswithveryhighrequirements,butalsorelativelylow-endSerViCeSwiththerequirementofsmalldeviceformfactors,and/orbeingcompletelywirelesswithabatterylifeofseveralyears.Therequirementsf
44、ortheseservicesarehigherthanLPWA(i.e.LTE-MTC/NB-IoT)butlowerthanURLLCandeMBB.2. Similartoconnectedindustries,5Gconnectivitycanserveascatalystforthenextwavesmartcityinnovations.Asanexample,TR22.804describessmartcityusecaseandrequirementsforthat.Thesmartcityverticalcoversdatacollectionandprocessingtom
45、oreefficientlymonitorandcontrolcityresources,andtoprovideservicestocityresidents.Especially,thedeploymentofsurveillancecamerasisanessentialpartofthesmartcitybutalsooffactoriesandindustries.3. Finally,wearablesusecaseincludessmartwatches,rings,eHealthrelateddevices,andmedicalmonitoringdevicesetc.Onec
46、haracteristicfortheusecaseisthatthedeviceissmallinsize.Asabaseline,therequirementsforthesethreeusecasesare:Genericrequirements:- Devicecomplexity:Mainmotivationforthenewdevicetypeistolowerthedevicecostandcomplexityascomparedtohigh-endeMBBandURLLCdevicesofRel-15Rel-16.Thisisespeciallythecaseforindust
47、rialsensors.- Devicesize:Requirementformostusecasesisthatthestandardenablesadevicedesignwithcompactformfactor.- Deploymentscenarios:SystemshouldsupportallFR1FR2bandsforFDDandTDD.Usecasespecificrequirements:1. Industrialwirelesssensors:ReferenceusecasesandrequirementsaredescribedinTR22.832andTS22.104:Communicationserviceavailabilityis99.99%andend-to-endlatencylessthan100ms.Thereferen
