Communication Systems Department EURECOM Unleashing the potential of open-source in the 5G arena

Transcription

1 OAI NB-IoT/eMTC Activities Communication Systems Department EURECOM Unleashing the potential of open-source in the 5G arena

2 Summary Overview for NB-IoT and emtc Current team, Objectives and progress RRC work (Bologna/EURECOM) Overview of NB-IoT PHY (B-COM) MAC interfaces and functions (NTUST/EURECOM)

3 Objectives and Team Strong interest identified for bringing NB-IoT into OAI OAI could become tool to test NB-IoT enb or UE quickly Will do interband, guardband (combined with embb) and isolated solution Interconnected with OAI EURECOM=> build MEC IoT applications Test NB-IoT / LTE interop on common enb What is needed New Rel 13/14 physical channels to be implemented (simpler than LTE) one -PRB version of LTE L2 stack, largely the same Main work in RRC layer Openair-CN extensions in support of NB-IoT (SCEF for non-ip applications)

4 Objectives and team Current NB-IoT team Ray Cheng (NTUST) Eric HSIEH (NTUST) Nick Ho (NTUST) Calvin Hsu (NTUST) Kenny Chen (NTUST) Xavier Liu (NTUST) Alan Lee (NTUST) Michele Paffetti (UBologna) Rodolphe Legouable (B-COM) Matthieu Kanj (B-COM) Vincent Savaux (B-COM)

5 Objectives and team Weekly meetings (Tuesdays 10h30 CET, webex) Physical meeting with B-COM/Orange/Nokia/TCL : 14/03/2017 git repo: gitlab.eurecom.fr/oai/openairinterface5g, branch develop-nb-iot Synchronized regularly with main develop branch Merge requests handled by B-COM into develop-nb-iot Main targets for NB-IoT enb functionality by July 2017 Integration with openaircn (added functionality in MME) Integration with Nokia µcore Testing with first COTS devices NFAPI NB-IoT interface Implementation will be aligned with small-cell forum NFAPI. This is currently already finalized. We will receive the reference implementation from Cisco. UE in second phase, discussions with one IP vendor on UE implementation in community. Interested parties should speak up. UE L1 will be done to test L1 enb Main targets for emtc Rel 14 enb physical channels and procedures starting in July 2017 Collaboration with Orange (Egypt and France) Starting point for NR phase 2 (5GMTC)

6 RRC NB-IoT Overview and Differences Reduced set of RRC procedures: No connected mode mobility (handover and measurement reporting) No Dual Connectivity No MBMS (Rel.13) Same RRC state as in LTE: RRC_CONNECTED & RRC_IDLE Signaling radio bearer are partly re-used from LTE: o SRB0 for RRC messages transmitted over the CCCH logical channel o New signaling radio bearer SRB1bis implicitly configured with SRB1 using the same configuration, however without the PDCP SRB1 takes the role of the SRB1 until security is activated o There is no SRB2 defined Subset of the SIBs defined for NB-IoT with a reduced and/or modified set of information elements: o Basic: MIB-NB (new design): schedulinginfosib1, SystemInfoValueTag, ab-enabled SIB1-NB, SIB2-NB, SIB3-NB (Actually implemented in OAI), SIB4-NB,.. o NB-IoT (Rel ): SIB15-NB, SIB20-NB, SIB22-NB (not supposed to be implemented in OAI) System information acquisition and change procedure is only applied in the RRC_IDLE state. Same RRC Connection Establishment/Reestablishmen/Release and Paging procedure as in LTE Need to implement paging here + RRCConnectionReestablishment RRC Connection Reconfiguration: Multi Carrier Configuration (non-anchor carrier) No mobilitycontrolinfo (handover not supported) New RRC Connection Resume/Suspension procedures signaling reduction for reestablishing RRC connection (also in regular LTE)

7

8 Reduce d set of SI New SRB1bi s MaxDR B-NB = 2 RLC-AM only New MIB- NB Design

9 OAI Initial RRC Connection Establishment

10 Start Using SRB1

11 RRC Interfaces

12 RRC Status RRC ASN.1 messages (Rel-14) integrated MIB,SIB (1,2,3) RRCConnectionRequest extraction RRCConnectionSetup generation RRCConnectionSetupComplete extraction RRCConnectionReject generation ULInformationTransfer extraction DLInformationTransfer generation UECapabilityEnquiry generation UECapabilityInformation extraction SecurityModeCommand generation SecurityModeComplete extraction RRCConnectionRelease generation RRCConnectionReconfiguration generation RRCConnectionResume generation (*** new) RRCConnectionResumeRequest extraction (***new) RRCConnectionReestablishmentRequest extraction RRCConnectionReestalishment generation (***to be added) RRCConnectionReestablishmentReject generation Paging-NB (***to be added) State machine from LTE enb refitted for NB-IoT Interfaces with lower layers (PDCP,RLC,MAC) defined and integrated Still some issues with SRB1bis Transparent interfaces (BCCH,CCCH) implemented directly between MAC and RRC (i.e. no PDCP/RLC transparent mode) Paging needs to be implemented still (will push to LTE at the same time)

13 B-COM PRESENTATION

14 MAC/PHY Interfaces FAPI P7 FAPI P5 Follow a FAPI-compatible interface => integrate with NFAPI solution provided by Cisco in OAI

15 Adaptation of OAI MAC-PHY primitives

16 MAC/PHY interface is defined MAC Scheduler will be implemented in May in parallel to completion of L1 procedures L1 status DL : NPSS / NSSS and Reference signals completed DL : NPBCH under implementation DL : NPDCCH, NPDSCH nothing yet UL : nothing yet Unitary simulators to be finished first => basic UE implementation enb NB-IoT procedures in parallel to MAC scheduler

17 Conclusions There will be NB-IoT in OAI very soon Testing will be possible as of August COTS UEs? RF platforms UE Anything should be ok Please provide an indication of community interest in this activity, some industrial interest is there