Skip to end of metadata
Go to start of metadata


 | 9am PST |  noon EST | 17:00 UTC | 18:00 CET | 21:30 IST 

new ZOOM:
Meeting ID: 890 6970 8424

Let's see how this works (wink)
in case of trouble you find us also on Slack



Discussion items


Next meetings: 

2021-02-24: John Keeney

2021-03-03: Martin Skorupski

2021-03-10: John Keeney

2021-03-17: Martin Skorupski


Time for the slot is critical


Status reports:


Lasse Kaihlavirta

DMaaP A1 Policy Service
Why? just as a common service to share info from Non-RT-RIC to other µServices.

Hieu Nguyen

  1. non-rt-ric communicates via AI to near-rt-ric - with A1-Adapter
  2. non-rt-ric communicates via AI to near-rt-ric - without A1-Adapter

Why A1-Adapter? and not direct? → centralize - load balancing  - integration point -

HTTP proxy: used only for direct communication to Near-RT-RIC


O-DU - OAM interfacing

mini - SMO for dev - provide link to docker compose


00:??Use Case


OSC Proposed e2e integration use case: O-RU FH connection recovery

<bridge dropped recording stopped at this point. Most participants reconnected once bridge started again>

  • Topology ??: (contd)
    • John Keeney Lots of options for how this should be done properly in ONAP.
    • Swaminathan Seetharaman ONAP usecases already have some plans for this e.g. slicing, oof,  etc
    • Andy Mayer A model should be agreed in ONAP. Lots of previous discussions in ONAP - e.g. what goes in A&AI and CPS ... but that was a while ago.
    • Martin Skorupski SDNR has some topology model too - not standards based.
    • @Sven John Keeney Martin Skorupski Lots of issues with different topology models ... and most existing hierarchical models break down in a 5G/CloudRan environment
    • Lots of work ... Andy Mayer Martin Skorupski Can create a JIRA in ONAP MODCOM ...
    • ... but will keep it simple here for this use case.
  • @? Will other O1 usecases be effected? Martin Skorupski i No. O1 functions continue as before.
  • Martin Skorupski Please add feedback if any

Action items