MWDI Enhancement implementation version 2.1.0

[KarthikeyanV-TechM]

Release Specification of MicroWaveDeviceInventory v2.1.0 · openBackhaul/MicroWaveDeviceInventory

1. A configurable list of attributes/subclasses to be excluded from the quality measurement process
   might also require some small changes to the implementation.
   I assume that the filter list was hardcoded before, but now we have profileInstance qualityMeasurementExclusions.
   So this would need to be used instead of the hardcoded list.
   Refer: Add profile instance for attributes to be ignored during quality measurement #1519

2. Different approach for deriving the deviceType (use equipment-augment/device-model-name instead of air-interface-capability information and regex), vendor mapping adjusted accordingly
   I would expect that the new regex mappings are already working, as for this just the contents of already existing profileInstance vendorFromDeviceTypeMapping needed to be changed, no new profile was added.
   Refer: Change input source for deviceType mapping #1482

3. Add the timestamp of the last complete ControlConstruct update to the respective ControlConstruct
   is the new change to be implemented we talked about last week.
   Refer: Date information for deciding about replication #1554

Implementation Tasks:

• MWDI Enhancement Implementation - Configurable list of attributes/subclasses to be excluded from the quality measurement process #1560
• MWDI Enhancement Implementation - Different approach for deriving the deviceType #1561
• MWDI Enhancement Implementation - Add the timestamp of the last complete ControlConstruct update to the respective ControlConstruct #1562

---

Spec Commit link
More details in the mail below from Katharina:

Hi Karthikeyan,

I published the new MWDI release 2.1.0_spec:

Release Specification of MicroWaveDeviceInventory v2.1.0 · openBackhaul/MicroWaveDeviceInventory

While creating the release description I noticed that this point:
a configurable list of attributes/subclasses to be excluded from the quality measurement process
might also require some small changes to the implementation.
I assume that the filter list was hardcoded before, but now we have profileInstance qualityMeasurementExclusions.
So this would need to be used instead of the hardcoded list.

For the 2nd item
different approach for deriving the deviceType (use equipment-augment/device-model-name instead of air-interface-capability information and regex), vendor mapping adjusted accordingly
I would expect that the new regex mappings are already working, as for this just the contents of already existing profileInstance vendorFromDeviceTypeMapping needed to be changed, no new profile was added.

The 3rd item
adds the timestamp of the last complete ControlConstruct update to the respective ControlConstruct
is the new change to be implemented we talked about last week.

Br
Katharina