爱立信-2023-RedCap - expanding the 5G device ecosystem for consumers and industries调研报告

EricssonWhitePaper

GFTL-23:000064Uen

February2023

RedCap-

expanding

the5Gdevice

ecosystemfor

consumersand

industries

RedCap-expandingthe5Gdeviceecosystemforconsumersandindustries3

Introduction

February2023

Introduction

Sincethenumberofpersonalsmartphonesubscriptionsislimitedbythesizeofthehuman

population,thenumberofInternetofThings(IoT)devicesispredictedtohaveastronger

growththansmartphonesubscriptionsinthecomingyears.TheIoTsegmentserved

bycellularnetworkscanbedividedintoMassiveIoT,BroadbandIoT,CriticalIoT,and

IndustrialAutomationIoT,whereBroadbandIoTisforecastedtoconstitute60percentof

thecellularIoTconnectionsbytheendof2028[1].BroadbandIoTincludesbothwide-

areaandlocal-areausecasesthatrequirehigherthroughput,lowerlatency,andlarger

datavolumesthanwhatMassiveIoTtechnologiescansupport.Theseusecasesinclude,

forexample,smartwearablesandindustrialsensors.Inthepast,BroadbandIoTusecases

wereoftenservedby4Glong-termevolution(LTE)devicecategories1and4.Thedevice

complexity,andhencethedevicecost,hassofarbeentoohighfor5GNewRadio(NR)tobe

suitedtoBroadbandIoT,whichmotivatedtheintroductionofreducedcapability(RedCap)

5GNRdevicesin3GPPRelease17[2].

Figure1illustratesdifferent4G/5Gdevicetypes.Atthelowend,thereistheNB-IoTdevice

category(Cat-NB1)andtheLTE-Mdevicecategory(Cat-M1),whichbothsupportrelatively

lowdataratessuitableforMassiveIoTusecases.Since3GPPRelease15,bothNB-IoT

andLTE-Mfulfillthe5Gmassivemachine-typecommunications(mMTC)requirements

andarethereforecomponentsofboth4Gand5G.Atthehighend,bothLTEandNRhave

devicetypesforhighpeakratesfordemandingusecases.Inbetweenthelowandthe

highend,LTEoffersseveraldevicecategories(thatis,Cat-1/2/3/4),andRedCapprovides

correspondingNR-baseddevicetypesforthismid-rangesegment.

RedCap-expandingthe5Gdeviceecosystemforconsumersandindustries4

Introduction

February2023

Peak

datarate

LegacyNR

HigherLTE

categories

LTECategory4

LTECategory3Rel-17RedCap

LTECategory2

LTECategory1Rel-18RedCap

LTE-McategoryM1

NB-IoTcategoryNB1

4G5G

Figure1:Illustrationof4Gand5Gdevicetypes.

ThesimplestRedCapdevice,thatis,aRedCapdevicewiththelowestpossiblecomplexity,

isexpectedtoreducethemodemcomplexitybyabout65percentforlow-ormid-band

(FR1)devices,andbyabout50percentforhigh-band(FR2)devices,whilehighenough

peakdataratesaremaintainedtostillservemoredemandingIoTusecases.ARedCap

deviceequippedwithmoreadvanced(butnotmandatory)capabilitiescansupportmuch

higherpeakrates.Forexample,aRedCapdevicewithtworeceiveantennabranchesand

downlinkmultiple-inputmultiple-output(MIMO)layerscansupporttwiceashighdownlink

peakratesasthesimplestRedCapdevice,sincethisallowsdual-streamtransmissionsover

twoMIMOlayers.

TheotheraspectwhichisneededtofulfillIoTrequirementsislowenergyconsumption,

andthishasbeenenabledbytheintroductionofextendeddiscontinuousreception(eDRX)

cyclesandrelaxationsforradioresourcemanagement(RRM)monitoring(ontopofthe

Release16measurementrelaxationswhichcanalsobesupportedbyRedCapdevices).In

combination,theintroducedfeaturesprovideasubstantialcomplexityreductionandan

extendedbatterylifeforRedCapdeviceswhichenableNRtoefficientlyaddressBroadband

IoTusecasesrangingfromfactoryautomationandIndustry4.0tolow-endaugmented

reality(AR)andvirtualreality(VR)applications.

RedCap-expandingthe5Gdeviceecosystemforconsumersandindustries5

Usecasesandmarketpotential

February2023

Usecasesand

marketpotential

TheintroductionofRedCapwillenableasinglenetwork,i.e.,a5Gstandalonenetwork

consistingofbothRANandcorenetwork,toaddressavarietyofusecasesforindustry

digitalizationandbusinesstransformation.Furthermore,RedCapwillhelpexpandthe5G

ecosystemandconnectsignificantlymoredevicesto5Gnetworks.Thisincludesupgrading

theLTE-basednetworksthathavebeendeployedtoprovideglobalIoTcoverage.Withthe

introductionofRedCap,asmoothmigrationtoNRforsupportingsuchusecasescanthen

beaccomplishedwithouttheneedfornetworkdeploymentswithmultipleRATs.

ExamplesofusecasesthatwillbeaddressedbyRedCapdevicesincludewearables

suchassmartwatches,wearablemedicaldevices,andlow-endAR/VRglasses,video

surveillance,industrialsensors,smartgrids,andsoon(seeFigure2).Theseusecaseshave

ahugemarketpotential,worthtensofbillionsofdollars.Forexample,theglobalend-user

spendingonwearablesalonewasestimatedtobeUSD81.5billionin2021,anincrease

of18percentcomparedto2020,andisestimatedtoincreasetoUSD94billionin2022,

accordingtoGartner[3].Forindustrialapplications,RedCapservicescanproviderobust

wirelessconnectivityandseamlessmobilitysupportthrough5Gnetworksforindustrial

CameraSmartgridIndustrialsensor

SmartglassesWearableHealthmonitoring

RedCap

Figure2:RepresentativeRedCapusecases.

RedCap-expandingthe5Gdeviceecosystemforconsumersandindustries6

Usecasesandmarketpotential

February2023

devicesenablingcost-efficientIndustry4.0transformation.

EachaddressableRedCapusecasehasitsownsetofrequirementswhich,comparedto

regular5GNRdevices,islessdemandingintermsofdataratesandlatency,yetmore

stringentwhenitcomestodevicecost/complexityandpowerconsumption.However,the

batteryliferequirementsforRedCapusecasesarerelativelyrelaxedcomparedtothose

ofmMTCusecases.Infact,asillustratedinFigure3,RedCapisdesignedtoefficiently

supportusecaseswhoserequirementsfallbetweenthemoreextremerequirements

definedformMTC,ultra-reliablelow-latencycommunications(URLLC),andenhanced

mobilebroadband(eMBB).However,RedCapdevicesmayalsobesuitableformoderate

(lessextreme)mMTC/URLLC/eMBBusecases.Forexample,whencomparingRedCap

requirementswitheMBB,URLLC,andmMTCusecases,thefollowingcanbenoted[2]:

•Latency:ThetargetforURLLCisabout1ms,whileforRedCapusecasesitislessthan

100msforindustrialsensorsandlessthan500msforvideosurveillance.However,these

areminimumrequirements,anditisworthnotingthatRedCapdevicescaninfactachieve

muchbetterlatencythanthis.

•Datarates:ThetargetpeakrateforeMBBisupto20Gbpsindownlinkand10Gbpsin

uplink,whileforthemostdemandingRedCapusecases(e.g.,wearables)itisupto150

Mbpsindownlinkand50Mbpsinuplink.

•Batterylife:ThetargetformMTCis10to15yearsbatterylife,whileforRedCapuse

casesitisafewyearsforindustrialsensorsandonetotwoweeksforwearables.Again,

theseareminimumrequirements,andRedCapdevicesmaybeabletoachievealonger

batterylife.

WithRedCapanditsevolution,5Gcanefficientlyaddressmid-tierBroadbandIoTusecases

inadditiontothethreekeyusagescenarios(eMBB,URLLC,mMTC)usinganyavailable

5Gspectrum,bothtime-divisionduplex(TDD)andfrequency-divisionduplex(FDD),inall

(low/mid/high)frequencybands.OuranalysisshowsthatRedCapcansufficientlymeet

requirementsofvariousBroadbandIoTusecasesintermsofdatarates,latency,battery

life,andsmallformfactors.ComparedtoLTEdevicecategory4,RedCapofferssimilardata

rateswithimprovedlatencyandpotentialsupportforvarious5GNRfeaturesincluding

enhancedpositioning(importantforpersonaltrackers),millimeter-waveoperationswith

advancedbeamformingsupport,andnetworkslicing.

Highdatarate

eMBB

URLLC

mMTC

RedCap

LowcostandlongbatterylifeLowlatency

Figure3:RedCaprequirementscomparedtoeMBB,URLLC,andmMTC.

RedCap-expandingthe5Gdeviceecosystemforconsumersandindustries7

Reducingdevicecostandcomplexity

February2023

Reducing

devicecostand

complexity

Today,manyofthetargetedusecasesforRedCapcanbeservedbylow-endLTEdevices,

whichhavesubstantiallylowerdevicehardwarerequirementsthanthesimplestNRdevice.

Therefore,asmentionedintheIntroduction,theneedtointroducealower-complexityNR

devicetypewithreducedcapabilitiesroughlycorrespondingtothecapabilitiesofalow-end

LTEdevicehasbeenidentified.

TheNRmodemcost/complexityreductionisaccomplishedbyusingthetechniques

summarizedinTable1below[2].Inthetable,the“Simplestregular5Gdevice”corresponds

toabasic5GNRdevicesuchasasmartphonewithonlytheminimumcapabilitiesthatare

mandatorytosupportforsuchadevice,whereasthe“SimplestRedCapdevice”corresponds

toabasicRedCapdevicewithonlytheminimumcapabilitiesthataremandatorytosupport

foraRedCapdevice,andthe“MostadvancedRedCapdevice”correspondstoaRedCap

devicewiththemostadvanced(butoptional)capabilitiesthatcanbeimplemented.

Ouranalysisshowsthat,comparedtothesimplestregular5Gdevice,thetechniquesin

Table1canhelptoreducethebill-of-materialscostforthesimplestRedCapdeviceby

about65percentinlow/mid(FR1)frequencybandsandbyabout50percentinhigh(FR2)

frequencybands.Furthermore,thereductioninthenumberofreceiveantennabranchescan

alsohelptoreducethephysicalsizeofthedevice.

TherecanbeRedCapdeviceswithcapabilitiesin-betweenthoseofthesimplestandthe

mostadvancedRedCapdevices.Forexample,aRedCapdevicecansupporttwodownlink

MIMOlayerswithoutsupporting256quadratureamplitudemodulation(QAM)inthe

RedCap-expandingthe5Gdeviceecosystemforconsumersandindustries8

Reducingdevicecostandcomplexity

February2023

downlink.However,aRedCapdevicecannotsupporttransmit/receivebandwidthslarger

than20MHzforlow/midfrequencybandsormorethan100MHzforhighfrequency

bands.Also,itcannotsupportfeaturesandcapabilitiesrelatingtocarrieraggregation,dual

connectivity,morethantworeceiveantennabranches,morethantwodownlinkMIMO

layers,morethanonetransmitantennabranch,ormorethanoneuplinkMIMOlayer.

InadditiontothosetechniqueslistedinTable1,afewoptionalcomplexityreduction

techniquesforthehigherlayersoftheradioprotocolstackhavealsobeenintroducedfor

RedCapdevices.Theseincludeareductioninthemaximumnumberofdataradiobearers

from16to8,areductioninsequencenumberlengthforpacketdataconvergenceprotocols

(PDCP)andradio-linkcontrol(RLC)layersfrom18bitsto12bits,andmakingautomatic

neighborrelationfunctionalityanoptionalcapability.Thehigher-layercomplexityreduction

techniquesmentionedinthisparagrapharenotexpectedtoimpactthepeakdatarate.

Table1:Comparisonofthesimplestregular5Gdevicewiththesimplest

andthemostadvancedRedCapdevice.

Low/mid(FR1)frequencybandsHigh(FR2)frequencybands

SimplestMostSimplestSimplestMostSimplest

regular5GadvancedRedCapregular5GadvancedRedCap

deviceRedCapdevicedeviceRedCapdevice

devicedevice

Maximum

transmit/receive100MHz20MHz20MHz200MHz100MHz100MHz

bandwidth

Supportednumber2antenna

2or4

ofreceiveantennabranches,

(dependingon

branchesand2122butonly

thefrequency

downlinkMIMO1MIMO

band)

layerslayer

Supportednumber

oftransmit

antennabranches111111

anduplinkMIMO

layers[Note1]

DevicepowerPC3PC3PC7

PC3PC3PC3

class(PC)[Note2][Note2][Note3]

Maximum

downlink256QAM256QAM64QAM64QAM256QAM64QAM

modulationorder

Maximumuplink

modulationorder64QAM256QAM64QAM64QAM256QAM64QAM

[Note1]

TDDor

TDDorfull-TDDorfull-

Duplexoperationhalf-duplexTDDTDDTDD

duplexFDDduplexFDD

FDD

Note1:ThiscapabilityhasnotbeenrelaxedforRedCapUEs.Ithasbeenincludedinthetableforthe

sakeofcompleteness.

Note2:PC3inFR2isassociatedwithhandhelddevices.

Note3:PC7isalowerpowerclassthanPC3,andtherefore,ithaslowerradiatedpowerandlower

referencesensitivityrequirementsthanPC3.Consequently,RedCapdevicessupportingPC7canbe

equippedwithfewerantennaelementsand/orpanelsthanthatofdevicessupportingPC3.

RedCap-expandingthe5Gdeviceecosystemforconsumersandindustries9

Reducingdevicecostandcomplexity

February2023

1,400Downlink

Uplink

970

645

580

Mbps

355

230225235240

190175

120130

8590

455035

SimplestMostadvancedSimplestSimplestMostadvancedSimplestSimplestMostadvancedSimplest

regular5GRedCapRedCapregular5GRedCapRedCapregular5GRedCapRedCap

devicedevicedevicedevicedevicedevicedevicedevicedevice

FR1FDDFR1TDDFR2TDD

(withDL/ULsplit60%/40%)(withDL/ULsplit60%/40%)

Figure4:Comparisonofachievablepeakdataratesindifferentbandsforthesimplestregular

5Gdevice,themostadvancedRedCapdevice,andthesimplestRedCapdevice.

ThecomplexityreductionsinTable1wouldimpacttheachievablepeakdatarate,and

forthesimplestRedCapdevice,theresultingpeakdataratesindownlink/uplinkare

approximately:

•85/90Mbpsinlow(FR1FDD)bands,assuming15kHzsubcarrierspacing,andthatthe

devicesupportsfull-duplexFDD.Thepeakrateswillbelowerforhalf-duplexFDDdevices

astheycannottransmitandreceiveatthesametime.

•50/35Mbpsinmid(FR1TDD)bands,assuming30kHzsubcarrierspacinganda

downlink/uplinksplitof60/40percent.

•240/175Mbpsinhigh(FR2TDD)bands,assuming120kHzsubcarrierspacinganda

downlink/uplinksplitof60/40percent.

Thesepeakratesaresufficienttofulfilltherequirementsofmostoftheintendedusecases

forRedCap.AmoreadvancedRedCapdevicecansupportahigherpeakrate,whichcould

beusefulforlow-endAR/VRusecases.Figure4showsacomparisonofthemaximum

achievablepeakdataratesindifferentbandsforthesimplestregular5Gdevice,themost

advancedRedCapdevice,andthesimplestRedCapdevice.

Inprinciple,thedevicescansupportanevenlowerpeakdataratethanthoseshownin

Figure4byreportingadown-scaledpeakrateusingso-calledpeakratescalingfactor.For

example,theRedCapdevicesareonlyrequiredtosupportpeakratesindownlink/uplinkof

approximately55/60Mbps(ratherthan85/90Mbps)inFDDbands.

RedCap-expandingthe5Gdeviceecosystemforconsumersandindustries10

Addressingdiversebatteryliferequirements

February2023

Addressing

diversebattery

liferequirements

SomeofthetargetedRedCapusecaseshavemorestringentrequirementsondevicebattery

lifecomparedto5Gusecasesingeneral.Also,asdescribedearlier,thedifferentRedCap

usecaseshavedifferentdevicebatteryliferequirements.Therefore,thesolutionsfor

devicebatterylifeimprovementneedtoaccountforsuchdiverserequirements.Tomeetthe

requirements,RedCapsupportsreduceddeviceactivitiesintermsofdownlinkmonitoring

andmobilitymeasurements,asoutlinedbelow.

Extendeddiscontinuousreceptionmechanism

Thekeytoextendbatterylifeisthediscontinuousreception(DRX)mechanism.Thisisa

mechanismwhereadeviceturnsoffitsreceivercircuitryoverperiodsoftimetosavepower.

In5G,thenetworkcanconfigureadevicewithDRXcyclesthatcanvaryfromafewhundred

millisecondstoafewseconds(upto2.56seconds),dependingonthedownlinklatency

requirements.ThisvaluerangehasbeenextendedinRelease17byintroducingeDRXfor

RedCapdevices.ThevaluerangeforeDRXcyclesisuptoabout3hoursfordevicesinRadio

resourcecontrol(RRC)Idlemodeand10.24secondsfordevicesinRRCInactivemode.This

rangeisthesameasfortheexistingMassiveIoTtechnologyNB-IoTand,therefore,the

relativepowersavingscouldinprinciplebeaslargeforRedCapasforNB-IoT.

ThepotentialdrawbackwitheDRXistheincreaseddownlinklatencysincethedevice

cannotresponduntiltheendofthesleepcycle.Thedevicewakesuplessfrequently

whenconfiguredwitheDRXcyclesandisnotmandatedtomonitorpagingmessagesand

notificationsduringthesleepcycles.However,sinceRedCapusecasesdonothaveas

RedCap-expandingthe5Gdeviceecosystemforconsumersandindustries11

Addressingdiversebatteryliferequirements

February2023

stringentlatencyrequirementsaseMBBorURLLCusecases,latencycanpotentiallybe

traded-offforbatterylifeimprovement.

Furthermore,thedevicecannotstayinasleepstatewhenthereisdataactivityintheuplink.

Therefore,themorefrequentthedatatransmissionsareintheuplink,thesmallerthe

improvementsareinbatterylife.

Inconsequence,themagnitudeofimprovementinbatterylifedependsonhowoftenthe

devicehassomethingtotransmitintheuplinkandhowmuchtimethedevicecanspendina

sleepstateduringthesleepcycles.ThisisdemonstratedinFigure5wheredifferentaverage

uplinkdatainterarrivaltimes(IATs)areillustratedbydifferentcurvesandonecanobserve

thatimprovementinbatterylifeincreaseswiththelengthoftheeDRXsleepcycleforRRC

Idlemode.

Batterylife80

improvement

(byfactorofX)

70

60

50

40

30

20

10

0

0.010.1110100

eDRXsleepcycle(minutes)

1minIAT5minIAT15minIAT60minIAT180minIAT

Figure5.DevicebatterylifeimprovementasafunctionofeDRXsleepcyclelengthfordifferent

datainterarrivaltimes(IATs).

Thegainisthereforethebiggestforadevicewithveryrelaxeddownlinklatency

requirements,suchthataneDRXcycleofclosetothreehourscanbeconfigured,andwith

veryinfrequentdatatransmissionintheuplink.Withthevaluerangeconsideredinthese

evaluations,thegainis,forexample,thelargestforatwo-houreDRXcyclewithdata

transmissionactivityintheuplinkonaverageeverythreehours,inwhichcasethebattery

lifecanbeextendedby80timescomparedtoanon-eDRXcase.

InRelease18,themaximaleDRXcyclelengthinRRCInactivewillalsobeextendedto

aboutthreehours[4]togiveasimilargaintothatofeDRXinRRCIdle.

RedCap-expandingthe5Gdeviceecosystemforconsumersandindustries12

Addressingdiversebatteryliferequirements

February2023

RRMmeasurementrelaxationforRedCapdevices

Toachievethebestperformance,bothforthedeviceitselfandforthenetworkasawhole,

itmustbeensuredthatthedeviceconnectstothebasestationwiththestrongestsignal

strength.Forthisreason,devicesperformRRMmobilitymeasurementsondownlinksignals

broadcastedbythebasestation.Thisconsumesenergyinthedevicesincethereceiver,and

sometimesalsothetransmitterneedstobekeptactive.Onewaytoextenddevicebattery

lifeistorelaxtherequirementstoallowRedCapdevicestoperformthemeasurements

lessfrequently.Forthispurpose,itisrecommendedtoapplyrelaxedcellmonitoring(also

knownasrelaxedmeasurements)whichallowsthedevicetomeasurelessoftenbasedon

theoperatingscenarios.Theoperatingscenariosarecharacterizedbythemobilityandthe

locationofthedeviceinthecell.

Ingeneral,all5Gdevicescanbeoperatedindifferentactivitystates,suchasthetwolow

activitystates(RRCIdleandRRCInactive)andthehighactivitystate(RRCConnected).

InRRCIdleandRRCInactivestates,therelaxedmeasurementsintroducedinRelease16

NRforregular5Gdevicesallowthedevicetomeasurelessoftenorinsomecasesnotto

measureatallontheneighborcellswhenthedeviceisoperatingunderlimitedmobility

orwhenitisnotlocatedatthecellborder.Therelaxedmeasurementsintroducedfor

RedCapinRelease17allowevenfurtherrelaxationandsupportsnewrelaxationscenarios

comparedtotheRelease16relaxation.Forexample,therelaxationfactorsandperiod

oftimetonotperformanymeasurementsonneighborcellsareextended,andmoreover,

relaxationinstationaryscenarioisintroducedforRedCap.Thisimprovesthebatterylifeof

theRedCapdevice.

Furthermore,eDRXcanbeconfiguredforaRedCapdeviceinRRCIdleorRRCInactive

statestogetherwithrelaxedmeasurements.Thisenablesthedevicetoimproveitsbattery

lifemorethanwhatcanbeachievedwithonlyRRMmeasurementrelaxation.

InRRCConnectedstate,thereisnosolutiontosupportrelaxedRRMmonitoringfor

regular5Gdevices.SolutionsareintroducedforRedCaptoidentifylowmobilityscenarios

andreporttheresulttothenetwork.Thisinformationservesasabasisforthenetwork

tofindsuitablemeasurementconfigurationsinthedevicetoachievefurtherbatterylife

improvements.

Itisexpectedthattheserelaxedmeasurementmethodswillenablethelongerdevice

batteryliferequiredtoservesomeoftheRedCapusecases.

RedCap-expandingthe5Gdeviceecosystemforconsumersandindustries13

NetworkdeploymentaspectsforRedCapdevices

February2023

Network

deployment

aspectsfor

RedCapdevices

Itisimportantthatdifferentdevicetypescanco-existefficientlywithinthesamecellsinthe

samenetwork.Thereisapotentialriskthatreducingthebandwidthornumberofantennas

oftheRedCapdeviceswillhaveundesiredimpactsbothontheperformanceoftheRedCap

devicesthemselvesaswellasonother(non-RedCap)devices.Ifdesired,thenetworkcan

baraccesstoacellforallRedCapdevicesorforasubsetofthem(specifically,RedCap

deviceswithasinglereceiveantennabranchand/orRedCapdevicesnotsupporting

full-duplexoperations).However,asdescribedinthefollowingsubsections,itisgenerally

possibletosupportefficientcoexistencebetweendifferentdevicetypeswithoutsignificant

negativeimpactontheoverallnetworkperformance.

EnsuringgoodcoverageforRedCapdevicesinanefficientway

Inacellularnetwork,itisimportanttoensuregoodcoverageforalldevices.Foradeviceto

havegoodcoverage,itneedstobeabletoreceiveandtransmitmultipledatachannelsand

controlchannelsindownlinkanduplink.

Forlow-to-midfrequencybands(FR1),sinceaRedCapdevicehasreducedbandwidthand

areducednumberofreceiveantennabranches,theperformanceofdownlinkchannelsmay

RedCap-expandingthe5Gdeviceecosystemforconsumersandindustries14

NetworkdeploymentaspectsforRedCapdevices

February2023

beimpacted.However,weexpectthattheRedCapdevicewillachievesimilarcoverageas

aregular5Gdevice.Thereasonisthat,evenwiththereducedcapabilities,theperformance

ofdownlinkchannelsofaRedCapdeviceisbetterthanthebottleneck(weakest)channel

oftheregular5Gdevice.Thebottleneckchanneldeterminesthecoverageofthecell.For

aregular5Gdevice,thebottleneckchannelistypicallytheuplinkdatachannel(PUSCH).

Therefore,theremaynotbeaneedforredimensioningexisting5Gnetworkspriorto

RedCapdeployment.

Forhighfrequencybands(FR2),thenumberofreceiveantennabrancheshasnotbeen

reducedfortheRedCapdevice.Also,theRedCapdevicesupportsarelativelylarge

bandwidthof100MHzinFR2.Basedontheseconsiderations,theRedCapdeviceis

expectedtoachievesimilarcoverageastheregular5Gdevice.However,asshowninTable

1,theRedCapdevicecansupportalowerpowerclassinFR2.Thisreducestheradiated

powerrequirementsintheuplinkandthereferencesensitivityrequirementsinthedownlink.

Therefore,thecoverageofsomeoftheuplinkanddownlinkchannelsmaybeimpacted

fordevicesusingthelowerpowerclass.However,itisexpectedthatthecoveragecanbe

recoveredusingtraditionaltechniques,suchasretransmissionsfordatachannels.

ItisalsodesiredtoensurecoverageforRedCapdeviceswithoutincreasingtherequired

radioresourcesfordownlinktransmissionsunnecessarily.Forthenetwork