2020-01-30: New work: Notification via O1 need to be clarified if this means VES or something else. As this is too cumbersome I suggest to drop this from the O1 notification from this feature.  The internal notification should remain (as this is only minor additional effort with SDL support for notifications). I updated the title accordingly and extracted O1 notifications into RIC-172. We can change back if we want to include notifications.

The list of known gNBs is a REST API now including connection state (existing REST might be good enough even if it means iterating in ping-pong calls over all gNBs in the GNB list (by gNB ID).

For the O1 mediator work talk to Antti's team.

If the interface for getting the gNBs/eNBs is SDL(RNIB, then the interface should be SDL notifications. So that we can implement something useful on top of this we might also need notifications for gNB added/removed.

This is needed as input for RIC-172 (presenting notifications via O1 (which is part of overall O-RAN-SC healthcheck use case)), but also for xApps to efficiently get informed if gNBs connect/disconnect.