Version: Frankfurt and later

Overview

A specific devicemanager 

• Contains device specific yang model
• Manages device lifecycle from state "Mounted&Connected" to "NotMounted"
• Get initial data of device
• Provides mapping of specific device information into the data-provider model of dataprovider service
• Does notification handling
  • Enable notifications in device
  • Handle incomming notification by converting and sending to different destinations like ODLUX, VES, dataprovider.

A specific devicemanager uses a devicemanager core. The term "devicemanager" is used in the meaning of devicemanager core. 

Interfaces of specific devicemanager 

A specific devicemanager imports two bundles to get access to a device and to services for NETCONF/YANG devices:

• sdnr-wt-devicemanager-model
  • NetconfNetworkElementService: Registration of specific devicemanager factory
  • DeviceManagerServiceProvider: services for NETCONF/YANG devices
• sdnr-wt-netconfnode-state-service-model
  • NetconfAccessor : get access to a device

sdnr-wt-netconfnode-state-service-model

Provides NetconfAccessor interface:

• Exchange data with device
• Get capabilities
• Setup notification listeners

sdnr-wt-devicemanager-model

NetconfNetworkElementService

• Register factory class of specific devicemanager
• Callback create(NetconfAccessor acessor, DeviceManagerServiceProvider serviceProvider) is called if device is connected.
• Creates SpecificNetowrkElement implementing NetworkElement interface for devicemanager service callbacks.

DeviceManagerServiceProvider to get services:

• DataProvider to exchange data with database
  • Inventory
• Common services (e.g.)
  • Fault management
  • Event Handling
  • Collect performance data
  • Device connection monitoring

The DataProvider interface provides access to the internal database. 

• Exchange data with database
• Data schema/model definition
  • Faults
  • Inventory
  • PerformanceData
  • ConnectionData