...
"nfVendorName":"Wipro"
"eventCategory: "PCICollision" (or) "PCIConfusion"
},
"faultFields":{
...
"alarmCondition":"RanPciCollisionConfusionOccurred",
"eventCategory: "PCICollision" (or) "PCIConfusion",
"eventSourceType":"other",
...
"vfStatus":"Active",
"alarmAdditionalInformation":{//This is not needed now
"networkId":"NTWK005",
"collisions":"1",//This is not needed now
"confusions":"1"
}
}
}
}
Impacts
Enhancement | Impact details |
|---|
Use the above updated layout for further processing | - SON-Handler MS: Receive and process the message.
- RAN-Sim: Generate the message.
Note: To be checked if VES 7.2 spec shall be used (and any impacts due to using it). VES 7.2 schema |
Send 1 alarm for each collision/confusion | - SON-Handler MS: Time/count to wait before triggering OOF to be fine-tuned
- RAN-Sim: Generate separate alarm onset messages. Alarm messages also have to be stored in DB and used when sending alarm-clear notification.
|
Send 1 alarm clear message for each collision/confusion getting cleared (eventSeverity: NORMAL) | - SON-Handler MS: Clean up local DB only upon receipt of alarm cleared notification
- SON-Handler MS: We have to maintain an interim state wherein alarm was received and handled (but alarm-clear is not yet received) to differentiate it from alarm-received and not handled case. Enhancement: There should be a timeout for this interim state, which should correspond to the timeout for (n)ack from Policy for the CL. Upon expiry of the timer, it should be moved to "alarm-received and not handled state".
- RAN-Sim: Send alarm clear message upon receipt of config update from ONAP, after verifying that the problem is resolved. Clear the local DB entry.
|
Components Impacts:
SON Handler MS
RAN-SIM + Honeycomb