You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

Date

Attendees

Informed

Goals

  • Share information

Discussion items

TimeItemWhoNotes
5minCDS

CDS - Controller Design Studio useful links by Dongho (thanks)

15minInfo

ONAP/O-RAN-SC Plugfest

  • first week from December in Seoul
  • it will be an O-RAN-SC event 

Use cases

1. PNF PnP

  • VES message: pnfRegsitration
  • ONAP most of the ONAP components.  


2. PM Bulk (file)

  • VES message for "File Ready"
  • PM upload via SFTP

3. Basic fault

  • existing VES domain "fault" to be used.

4. Basic config Config via NetConf, updated to the controller via VES. 
-- WG4 O-RU, FH (M-Plane) - NetConf Notification -> ONAP model-driven DMaaP Agent (notification)
-- WG5 O-DU, VES message from the beginning - O1 -Architecture.

5. OOF-SON -> Sandeep Shah was pushed to Release B

- VES Notifications

Objective


The objective is showing O1 interface between ONAP and real equipment.

In OWL is equipment available from NEC, AltioStar, Huawei and software-defined radios, which could be used. 

Under discussion the support of real equipment integrated via DT-Could in Prag (e.g. ZTE) and OSNL. (see June demo)








below to be deleted
50minmd-DMaaP-Agent@allmodel-driven DMaaP Agent
10minO-RAN-SCMartin Skorupski

Feedback from O-RAN-SC


Action items

  • No labels