4

M CORD_OAI_Discussion_20161025

Rohit Gupta edited this page 2016-10-25 19:18:25 +02:00

Table of Contents

• Agenda
• Discussion on demo story
• Attendees
• Next Steps
• Next Meeting

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

Agenda

• To discuss short term plan towards MWC 2017
• MWC-OIA-M_CORD show cases
• List of Software Components; ( XOS, ONOS, EPC VMs , Portals, etc)
• List of HW components: ( Servers, switches, RRU, UE, Test tools, etc.)
• Demo Story: Lets detail out what will be the story for the DEMO at MWC and who from each side will be driving the story and collateral?
• Demo details & logistics ( Location of the demo, Equipment’s, Frequency bands, etc.)

Discussion on demo story

TOM:

• Clarify the short term use case of MWC
• Clarify the Use Case (long term)
• 3GPP proposal for IoT connection-less services to remove GTP. Potential demo for MWC
  • EURECOM approach suggested: Use of OVS
• FlexRAN does not include API for PHY Layer. It only has API for MAC layer
• Integrate with mFAPI, dynamic loading of PHY layers
• Clarify the phone: OAI UE - > synergies with NB-IoT project, COTS Phone
• How to bring different RRC/RRU split into the picture
  • Currently USRP is stable
  • LimeSDR/OAI needs some work on driver stability. Replicate testbench for LimeSDR
  • EURECOM will get LimeSDR PCIe version and USB3 version
• Interested in dynamic orchestration of BBU/RRH
• First integration : with ONOS
• Second integration: with XOS, can be some other platform(?)
• Clarify the bands:
• Integration of OAI RAN w/ Radisys 3rd party EPC
• Interface between BBU/RRU is not standardized
• Next step: start integration w/ ONOS on implementating interface in eNB agent

Attendees

• ATT
• ON.Lab
• Orange
• TCL
• EURECOM

Next Steps

Next Meeting

• Phone meetings
• F2F meeting proposal