...
| draw.io Diagram | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
netconfnode-state-provider (netconfnode-state-API)
- the base is a Service which provides a Netconfnode-state-API by using a netconf-change-listener
- on top of this service several devicemanagers which can register a callback function for a connected netconfnode
- the devicemanager can then decide if it wants to keep the netconfsession (based on capabilities) and register a notification listener on this or it wants to ignore it
- Listener for
- NetconfNodeConnectListener (Monitored states: connected/not connected and hello response available)
- NetconfNodeStateListener (Create, delete, change .. gets all related indications)
- DeviceMonitor
- ConnectionLog
...
| draw.io Diagram | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Devicemanager
| draw.io Diagram | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Device
A device with netconf/yang interface. The device provides during netcnf startup a list with all specifications implemented. This could be ONF Core model, O-RAN or other.
Devicemanager can start related service bundles for the supported specifications.
NetconfNetworkElementService
The specific devecemanagers for ONF, O-RAN or 3GPP devices need a registration in the devicemanager. The interface NetconfNetworkElementService allows to register a factory class.
The factory class is called in case of new mounted device, if a Netconf session has started. The information received with the "hello" answer is forwarded to the Factory. The factory can decide to start an instance of a specific handler object to manage the new device.
DeviceManagerService centralized services
Devicemanager provides base services to the specific devicemanager bundles. This kind of services are marked with interface DeviceManagerService.
The DeviceManagerServiceProvider containes getters for individual services described by list.
| Name | Description |
|---|---|
| AaiService (D) | Device registration and unregistration for AAI Service. |
| EquipmentService (D) | Write equipment of device into internal database. |
EventHandlingService  | Provide status changes of a device to update database and notify web client. |
| FaultService (D) | Provide Fault status changes to update database and notify web client. |
| MaintenanceService (D) | Use centralized maintenance service for a device. |
| NetworkElementService | Exchange data with device. |
| NotificationService (D) | Forward NetconfNotification to devicemanager |
| PerformanceManager(D) | Register device for centralised PM Service. Device needs to implement PerformanceDataProvider |
| DeviceManagerService | Marker of interface for NetworkElement. |
| DeviceManagerServiceProvider | Provides access to services |
NetworkElementService device specific providers
Technology specific device handlers are providing abstract information for centralized devicemanager services.
| Name | Description |
|---|---|
| PerformanceDataProvider | Provide 15min and 24h performance recordes |
| DeviceMonitoredNe | Used by central devicemonitor |
| InventoryProvider | Provide inventory information of device |
| NetworkElement | Top level interface of a device representation |
| NetworkElementService | Marker for interface provided to devicemanager |
Notification-service
- the notification-service provides the messages for the websevice cluster, so that GUI clients can be informed about changes
- Netconfnode-state-API originated message:
- ObjectCreationNotification (mountpoint created)
- ObjectDeletionNotification (mountpoint deleted)
- AttributeValueChangedNotification (mountpoint connection status change)
- devicemanager originated messages:
- ProblemNotification (Microwave model ProblemNotification)
...