Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Meeting Recording

...

Chat File


Attendance

Please enter you name and company. Tag yourself using LF ID User Name. Don't have an LF ID yet? Go here: https://myprofile.lfx.linuxfoundation.org/.

...

  • Infrastructure
    • Core - Free5GC currently installed at Kaloom
    • Orchestration - common orchestrator?
      • EMCO as default orchestrator (Yogen proposal)
      • ONAP to set policy
    • RAN - GXC currently installed at Kaloom
    • End to End Slicing
    • Security (stretch goal?) - Lead Muddasar (Mitre)? Resources- Periton Labs
      • Queue this up for 09/06 - Muddasar
  • Labs
    • Kaloom
    • UNH
    • Wavelabs
    • Dallas- Ganesh
    • Question- where are should the IBM models deployed?
      • IBM lab requires connectivity to other labs
      • Moving models to another location requires re-training
  • Edge Use Case(s)
    • Visual Inspection at the edge. Leads - Satish (IBM)? Ganesh/Tunde (Kaloom)?
      • IoT Device Authentication- resources- Periton Labs
        • Slicing (integration)
      • Fixed IoT device
      • Common orchestrator - ONAP/EMCO
      • Mobile IoT device (stretch goal?)
    • Massive IoT emulator - to demonstrate the system can handle millions of IoT devices
    • Traffic Routing (stretch goal?) - what does the Use Case look like?
    • Packet Filtering (stretch goal?) - what does the Use Case look like?
    • Yogen thoughts:
      • a) Dynamic and static slicing is already been demonstrated in early version, using eMBB in last Oct/Nov.
        though it's not completely dynamic but mix of static and dynamic factors.
        b) In current state of art, static slicing for URLLC and demonstrating GenX RU/DU/CU compliant with O-RAN
        and UE device from IBM will be value add.
        • One can characterize this effort to show case following values:
          1. O-RAN compliant RAN stack.
          2. URLLC use case demonstration with static slicing.
          3. Transport slicing (if required).
          4. 5G enabling AI/ML MEC application in edge location.




Work Stream Updates


Architecture & Adjacent Communities

...