NB-IOT04 LTE NB-IOT Feature Presentation PA2

1、Feature number: FAJ 801 1000 (Base package) License number: CXC 401 2081 Feature status: MI17A (new),Narrowband IoT Access,Introduction NB-IoT specification, 3GPP Release 13 Feature Description RAN product Dependencies Feature Benefits Limitations Configuration Management Performance Monitoring Refe

2、rences,Content,Introduction,Technologies addressing the Massive MTC use cases,MODULE COST/ PERFORMANCE,COVERAGE/BATTERY,LTE CAT-1 (with EC, PSM, eDRX),LTE CAT-M1 (with EC, PSM, eDRX),EC-GSM-IoT PSM + eDRX,NB-IOT + PSM + eDRX,Unlicensed LPWA,100 bps,1 Mbps,10 Mbps,10+ years,10 km,10s kbps,$5,$25,$10,

3、Use case DIVERSITY,Cellular for Massive IoT | Ericsson AB 2016 | May 2016,NB-IoT targets the low-end “Massive MTC” scenario: Low device cost/complexity:10 years Capacity: 40 devices per household, 55k devices per cell Uplink report latency :10 seconds,NB-IoT Design Targets,IntroductionRel-13 NB-IoT

4、Features,Enhanced coverage Provides at least 20 dB coverage enhancement (mandatory for UE) Throughput requirements by RAN4 requirements New RAN/EPC functionality DoNAS mandatory in UE RRC suspend/resume optional for release 13 UEs Idle mode eDRX mandatory for release 13 UEs,New radio i/f New channel

5、s Reduced peak rate Single receive antenna Half duplex FDD option Reduced UE bandwidth (180 KHz) New UE power class 20 dBm (optional) instead of 23 dBm max power,IntroductionNB-IoT support,* DL system peak rate: 0.23 Mbps *UL system peak rate: 0.25 Mbps,M2M access technology contained in 200 kHz wit

6、h 3 deployments modes: Stand-alone operation Operation in LTE “guard band Operation within wider LTE carrier (aka in-band) L1: FDD only & half-duplex UEs NPSS/NSSS, NPBCH, NPDCCH, NPDSCH over 180 kHz (1 PRB) Preamble based Random Access on 3.75 kHz NPUSCH on single-tone (15 kHz or 3.75 kHz) or multi

7、-tone (n*15 kHz) L2/L3: Single-process, adaptive and asynchronous HARQ for both UL and DL Data over NAS, or data over user plane with RRC Suspend/Resume System Information similar to eMTC/eDRX Paging similar to eMTC/eDRX, with DRX cycles up to 3h in Idle mode Multi-PRB support,NB-IoT overview,200kHz

8、,200kHz,200kHz,LTE,LTE,LTE,GSM,STAND ALONE,GUARD BAND,INBAND,All NB-IoT physical channels are prefixed with an “N” (NPBCH, NPDCCH, ) The following LTE channels have no direct corresponding channel in NB-IoT: PCFICH NPDCCH covers an entire subframe in subframes carrying NPDCCH so no need to indicate

9、number of OFDM symbols for NPDCCH Legacy PDCCH region indicated for in-band deployment in LTE carrier PHICH Only asynchronous adaptive HARQ for NPUSCH PUCCH ACK/NACK transmitted on NPUSCH format 2 ACK/NACK for NPUSCH is signaled via New Data Indicator in DCI Random Access required for transmission o

10、f Scheduling Request (SR),Supported physical channels,1-ms subframes and 10-ms radio frames is the same as in LTE. NPSS/NSSS resolve time difference to 80 ms. NPBCH transmitted in subframe 0 in every radio frame. 1024 10-ms radio frames indicated by SFN, and 1024 SFN periods indicated by Hyper-SFN.,

11、NPSS/NSSS/NPBCHTime-Frequency Allocation,NPBCH subframe,NPSS subframe,NSSS subframe,Block 0,Block 1,Block 7,640 ms,80 ms,1 ms,Sync subframe,Stand-alone/Guard-band,In-band,frequency,frequency,NPBCH subframe,Stand-alone/Guard-band,In-band,frequency,frequency,1 PRB,NPSS/NSSS/NPBCH resource mapping,Cros

12、s-subframe scheduling only Since NPDCCH scheduling NPDSCH in the same subframe is not supported. UEs monitor NPDCCH which contains scheduling information Scheduling information part of DCI DCI Format N0: uplink grant DCI Format N1: downlink assignment NPDSCH/NPUSCH repetition level dynamically confi

13、gurable Repetition level indicated in DCI Time offset, relative to NPDCCH, indicated in DCI Single-process, adaptive and asynchronous HARQ for both UL & DL (NPUSCH & NPDSCH),Data transmissions,Carries Downlink Control Information (DCI) Dynamically time multiplexed with NPDSCH Min offset for NPDSCH/P

14、USCH is 4 subframes. Two CCEs per subframe Maximum aggregation level (AL) is 2 AL2 can be used together with repetition Repetition to enhance coverage 1,2,4,8,16,32,64,128,256,512,1024,2048 repetitions supported,NPDCCH,1 subframe,Stand-alone/Guard-band,In-band,frequency,frequency,1 PRB,Data is sent

15、over the control-plane without establishing a data radio bearer No DRBs are set-up in RAN Therefore eNB does not see difference between NAS data and NAS signaling (similar to SMS). No PDCP support No AS security & header-compression. QoS: No AS prioritization differentiation MME changes required,Dat

16、a-over-NAS (DoNAS),SGW,Max DL user bit-rate,Assumptions (3GPP agreements) The maximum TBS for NPDSCH is 680 bits The start of UL A/N transmission is =12ms later than the end of NPDSCH transmission The start of NPDSCH transmission is =4ms later than the end of its associated DL assignment Max DL user

17、 throughput The latency is given by the min period between two NPDCCHs, 32 ms Max downlink user bit-rate (Inband) is then equal to 680 (bits) / 32 (ms) = 21.25 (kbps),Assumptions (3GPP agreements) For sending max TBS =1000 bits (500 QPSK symbols), it takes at least 4 subframes. The start of NPUSCH t

18、ransmission is =8ms later than the end of NPDCCH transmission The UE wont look for any NPDCCH until 3 ms after previous NPUSCH transmission Max UL user throughput The latency is given by the min period between two NPDCCHs, 16 ms. Max uplink user bit-rate is then equal to 1000 (bits) / 16 (ms) = 62.5

19、 (kbps),Max UL user bit-rate,NB-IoT core part completed in June 2016 Final working group meetings held 23-27 May in Nanjing NB-IoT performance part to be completed in September 2016 Additional RAN4 ad-hoc last week of June to progress performance parts NB-IoT rel-14 started and planned to finish Q1

20、2017,NB-IoT status in 3GPP,ASN.1 freeze,2014,2015,ASN.1 freeze,Rel-12,Rel-13,ASN.1 freeze,2016,2017,ASN.1 freeze,Rel-14,Major updates to RAN1/RAN2/RAN3 core specifications in Rel-13 RAN1 36.211, 36.212, 36.213, 36.201 RAN2 36.300, 36.304, 36.306, 36.321, 36.331 RAN3 36.413 RAN approved Rel-13 NB-IoT

21、 CRs (RAN#72, June 2016,Dependency to Standards,Introductionhigh Level NB-IoT/LTE Differences,Introductionhigh Level NB-IoT/LTE Differences,Scheduling Information reporting (Buffer status report, Scheduling Request) New “BSR” for Msg3 by combining and shortening BSR+PHR Legacy BSR is used after Msg3

22、 (only short BSR format) SR only supported through Random Access Connected mode DRX Built on legacy/eMTC but simplified Adapted to variable transmission times due to repetitions and deployment modes Support for coverage enhancements. NB-IoT supports up to 3 CE levels (PRACH configurations),Most func

23、tions needed for NB-IoT as the same as LTE, with some adaptations/simplifications Reduced number of logical channels CCCH, DCCH, and 0, 1 or 2 DTCHs Error correction through HARQ Asynchronous adaptive HARQ only, for both UL and DL Single HARQ process Logical channel prioritization Only strict LCH pr

24、iority supported, no prioritized bit rate,NB-IoT MAC,Feature DEscription,Repetitions ensures increased coverage NPRACH, NPDCCH, NPDSCH, NPUSCH, NPBCH Paging, System Information Based on RSRP measurements the UE selects an NPRACH resource with suitable number of repetitions The repetition levels of t

25、he early messages would be aligned to the selection of NPRACH resource After Msg3 has been received link adaptation can adjust to the link and select repetition levels for NPDCCH/NPDSCH/NPUSCH accordingly,Coverage VS REpetitions,Activation of CE level 0 in cell Broadcast of system information (MIB,

26、SIBs) related to the CE level (e.g. number of repetitions) to NB-IOT UEs One NPRACH resource with one associated repetition level, which may not suite all UEs in different coverage equally well NPDCCH Common search space applicable for the early messages aligned with the repetition level for NPRACH

27、UE specific scheduling Received energy on Msg3 input to link adaptation Link adaptation may select max repetition level according to less or more coverage (NPDCCH User specific Search Space) The max repetition level is sent to UE in Msg4 Dynamic scheduling for NPDCCH and NPDSCH can use a lower repet

28、ition level ( max repetition level),Feature DescriptionCoverage,Only one CE level 0, determines number of repetitions for early messages Later messages use repetition levels according to LA,Activation of several CE levels in cell Broadcast of system information (MIB, SIBs) related to the CE levels (

29、e.g. number of repetitions) A UE in bad coverage (based on RSRP measurements) can now select NPRACH resource according to a CE level (representing a certain number of repetitions) NPDCCH Common search space applicable for the early messages Msg 2 (RAR), Msg 3 (RRC Setup Req) and Msg 4 all use CE lev

30、el 1 aligned with the repetition level for selected CE level (associated to the selected NPRACH) UE specific scheduling Received energy on Msg3 input to link adaptation Link adaptation may select max repetition level according to less or more coverage (NPDCCH User specific Search Space) The max repe

31、tition level is sent to UE in Msg4 Dynamic scheduling for NPDCCH and NPDSCH can use a lower repetition level ( max repetition level),Feature DescriptionCoverage differentiation (Not in MI17A),CE level 1 uses more repetitions for early messages to obtain improved coverage,CE level 0 needs less repeti

32、tions for early messages since UE in good coverage,Inband deploymentValid Anchor-PRB indices (downlink),Assuming Inband operation in host LTE cell,Inband deploymentValid Anchor-PRB indices (downlink),Assuming NB-IoT Inband operation together with Cat-M operation in host LTE cell,The eNB upper limit

33、of connected users is shared between legacy (LTE) and NB-IoT users Capacity in terms of connected users is not limited for NB-IoT Amount of radio resources allowed for use by NB-IoT users upper limited in MI17A Maximum one NB-IoT cell (1 PRBs) for transmission of NPDCCH and NPDSCH Maximum one NB-IoT

34、 cell (1 PRBs) for transmission of NPUSCH Assumed to be enough for low load of connected NB-IoT users,CapacityNB-IOT Capacity,In L17A, NB-IoT claims the 3GPP air interface resources related to the DL PRB and UL PRB such that no legacy scheduling is expected to happen on the associated resource eleme

35、nts in the 3GPP resource grid The NB-IoT PRB resource is allocated as long the NbiotCell is unlocked, the resources is borrowed from LTE cell (EUtranCellFDD) in case of Inband deployment In addition, BB resources that represent how the DU can handle the traffic are to some extent shared with legacy

36、LTE existing on the same DU Uplink DU resources shared with legacy LTE (DL DU resources are reserved),Impact on LTE Resources,UEs not required to perform intra/inter-frequency measurements when the serving cell is above measurement threshold IDLE mode cell re-selection is based on ranking, no priori

37、ty based supported Network sharing up to 6 PLMNs is supported No inter-RAT mobility supported since this is not included in Rel-13 No connected mode mobility supported, since UE measurement reporting is not supported in Rel-13 UE that triggers radio link failure will trigger a new RRC connection est

38、ablishment Before this the UE performs cell selection MI17A supports below SIBs to support idle mode mobility SIB3-NB: Information/Parameters for intra-frequency and inter-frequency cell reselections SIB5-NB: Information on inter-frequency neighboring cells,Idle MODE Mobility,Note: NB-IoT cell has a

39、n own cell type, NbiotCell MO, which minimize the impact on LTE features Combined cell No impact on legacy LTE deployment. NB-IoT will only support one SectorCarrier of the LTE combined cell. Ericsson Lean Carrier (ELC) Minimal impact on LTE ELC performance. ELC will not mute CRS transmitted in the

40、NB-IoT Cell (PRB). eMBMS We will not support eMBMB and NB-IoT on same carrier (LTE inband cell) in MI17A.,Dependency to Other features,OSS OSS O17A supports NB-IoT MME IP-based DoNAS (Data over NAS) support Dependency for paging for NB-IoT UEs Coverage Enhancements support (extended range of CN time

41、rs) RU (Radio Unit) Software updates only IB power boosting and SA/GB require new type approval UE Support for Rel-13 NB-IoT UE,Dependency to Other Network Elements,Leverage existing 4G network asset Leverage existing 4G network asset Support of access from low complexity NB-IoT UEs in existing LTE

42、deployments (Inband deployments) Possibility to coexist in existing GSM spectrum where we can deploy a NB-IoT carrier (Standalone deployment) reusing existing HW (DU, RU) Enhanced coverage of 10-15 dB for NB-IoT UEs,Benefits and gains,All Macro DUS31/41 and Baseband 5212/5216 supported Max number of

43、 cells as in legacy (LTE + NB-IoT cells adds together) Max one Inband cell per LTE legacy host cell One Standalone cell per radio port Guardband not supported in MI17A No support for 1.4 MHz LTE bandwidth (not specified by 3GPP) Only Anchor carrier support (i.e. no NB-IoT multi-carrier scheduling) N

44、o support for 3.75 kHz NPUSCH No legacy DRB (user plane) not supported in MI17A Only longer cyclic prefix for RA preambles supported to obtain greater coverage (we dont expect this to be a capacity bottle-neck in MI17A) Only one repetition level defined for random access preambles (ideally 3GPP allo

45、ws for 3 levels) No support for DL transmission gaps HD-FDD support only (all FDD users treated as Half Duplex),Limitations,Configuration management,Feature activation The licensing MO instance name is NarrowbandIoTAccess Configure a new cell including the type defined in nbIotCellType, Inband and G

46、uardband require a host LTE cell reference eutranCellRef PCI you can select the same or different from LTE By default, CE level 0 is activated. Additional activation of CE levels using parameter coverageEnhancementLevel,Configuration ManagementFeature Activation,NB-iot Mo classes,EUtranCellFDD,eNBFu

47、nction,EUtraNetwork,SectorCarrier,RFBranch,SectorEquipmentFunction,AntennaUnitGroup,EutranCellRelation,EUtranFrequency,EutranFreqRelation,LTE,NB-IOT,NBIOTCell,Each EUtranFDD cell may be host for one NbIot inband cell in L17A,An eNodeB may have multiple NbIot cells,In the L17A release, one sector car

48、rier per NbIot cell is supported.,An attribute is used to set the type of deployment (inband/guardband/standalone),The attribute set is the union of attributes needed for the different deployments.,Frequency relation info as attributes in the NbIotCell MO,NBIOT inband deployment,EUtranCellFDD,eNBFun

49、ction,EUtraNetwork,SectorCarrier,RFBranch,SectorEquipmentFunction,AntennaUnitGroup,EutranCellRelation,EUtranFrequency,EutranFreqRelation,LTE,NB-IOT,NBIOTCell,eNBFunction manages the common radio resources,PCI may be identical to PCI of EUtranCellFDD,Each EUtranFDD cell may be host for one NbIot inba

50、nd cell in L17A,Each EUtranFDD cell may be host for one NbIot inband cell in L17A,One sectorcarrier per NbIot cell in L17A. The EutranFDD sector carriers are reused.,NBIOTCell,NBIOTCell,NBIOT stand alonedeployment,eNodeBFunction,LTE,NB-IOT,NBIOTCell,DL + UL Bandwidth 200 kHz EARFCN equals the center

51、 of the GSM frequency gap,GSM Frequency Gap Configured,SectorCarrier,RFBranch,SectorEquipmentFunction,AntennaUnitGroup,The eNodeBFunction could be shared with an EUtraNetwork here as well, but the Eutra and NB-Iot networks are unaware of each other,Multiple cells PCI configured manually as part of c

52、ell planning.,The NbIot standalone cells have their own sector carriers,In the L17A release, one sector carrier per NbIot cell is supported.,Array of frequency information in NbIotCell MO Downscaled variant of CellRelation and FrequencyRelation MOs used for EUtranCellFDD NbIotFrequencyInfo Frequency

53、: The frequency (of cell itself or neighbor cell) qRxLevMin: Minimum RSRP for cell reselection pMax: Pcomp at cell reselection qQualMin: As defined in 3GPP 36.304 qOffsetFreq: tReselection: cell reselection timer,Frequency relaTION info (MOM),NB-IoT cell attributes (1),Configuration ManagementMOM at

54、tributes (1),NB-IoT cell attributes (2),Configuration ManagementMOM attributes (2),NB-IoT cell attributes (3),Configuration ManagementMOM attributes (3),Paging attributes and RRC attributes,Configuration ManagementMOM attributes (4),Performance Monitoring,Accessibility counters measuring RRC Establi

55、shment Success Rate Random access counters measuring Random Access success Rate Cell availability counters measuring partial cell availability Data volume counters measuring data volume Physical resource counters measuring packed data channel utilization Radio channel quality counters measuring sign

56、al to noise ratio and pathloss HARQ counters measuring successful/unsuccessful HARQ transmissions UE context release counters used for measuring the retainability (legacy retainability KPIs not applicable for DoNAS) Paging counters measuring the paging performance Counter for no of connected IoT use

57、rs on eNB level,Performance managementoverview of pmcounters,PmcountersAccessability,Pmcountersretainability,Note: Legacy retainability KPIs not applicable for DoNAS,Pmcounterscell availability and paging,PmcountersRandom access, HARQ, data volume,Pmcountersphysical resource and radio channel qualit

58、y,New KPIs: The following legacy KPI formulas are applicable for NB-IoT, with the corresponding pmCounters defined for the NbIotCell Initial E-RAB Establishment Success Rate (not in 17A) Random Access Success Rate Partial Cell Availability Legacy LTE KPIs: No impact,KPIs,Cell trace,OSS-RC,ENM,eNodeB

59、,CTR Def,CTR Event data,Filter: Cell UE fraction,LTE cells,NB-IoT cells,Events data for LTE cells and NB-IoT cells are mixed, unless separate events apply Separation of LTE and NB-IoT cells can be done eNodeB G1 and G2 behaves in same way regarding this.,Nbiot alarms 1(2),Nbiot alarms 2(2),CPI References UD TBD 3GPP References Refer to “Dependency to Standards” Other References White paper: Cellular Networks for Massive IoT,References,Remove the backup slides before embedding the feature presentation into the cust