Updates requested by gh7896

— Existing —

The current version of the data model supports the following technology independent event records:

• Fault - the Fault Record, describing a condition in the Fault domain, contains information about device failures. The fault event provides data such as the entity experiencing a fault, the severity, resulting status, etc.
• Heartbeat - the Heartbeat Record provides an optional structure for communicating information about device health. Heartbeat records would only have the Common Event Header block. An optional heartbeat domain is available to specify information such as heartbeat interval and recommended action upon missing heartbeat interval. Heartbeat avoids the need to ping a device. A communication failure can be determined via missing heartbeat events being delivered to DCAE and appropriate action (e.g. restart VM, rebuild xNF or create ticket) can be taken by DCAE CLAMP.
• Measurements - the Measurements Record contains information about xNF and xNF resource structure and its condition to help in the management of the resources for purposes of capacity planning, elastic scaling, performance management and service assurance. These are soft alarms providing an opportunity for proactive maintenance.
• Notification - the Notification Record provides a structure for communicating notification information from the NF. It can contain notification information related to the current operational state that is reported by the NF. As an example, when cards or port name of the entity have changed state. (e.g., offline -> online) Other use cases include notification of file ready for collection using Bulk Data Transfer or notification on configuration changes to a device.
• Other - the Other Record defines fields for events that do not have a defined domain but are needed to be collected and sent to DCAE. This record provides a mechanism to convey a complex set of fields (possibly nested or opaque) and is purely intended to address miscellaneous needs such as addressing time-to-market considerations or other proof-of-concept evaluations. Hence, use of this record type is discouraged and should be minimized. (Note: the Other domain could be used to create and test new domain ideas.)
• pnfRegistration - the pnfRegistration Record provides a structure for registration of a physical network function. The pnfRegistration Record can contain information about attributes related to the physical network function including serial number, software revision, unit type and vendor name.
• State Change - the State Change Record provides a structure for communicating information about data flow through the xNF. The State Change Record can contain information about state change related to physical device that is reported by the xNF. As an example, when cards or port name of the entity that has changed state. Note: The Notification Domain can also communicate similar information.
• Syslog - the Syslog Record provides a structure for communicating any type of information that may be logged by the xNF. It can contain information about system internal events, status, errors, etc. It is recommended that low volume control or session logs are communicated via a push mechanism, while other large volume logs should be sent via file transfer.
• Threshold Crossing Alert - the Threshold Crossing Alert (TCA) Record provides a structure for communicating information about threshold crossing alerts. It uses data from the Measurement or a similar domain to watch for a Key Performance Indicator (KPI) threshold that has been crossed. TCA provides alert definitions and types, actions, events, timestamps and physical or logical details.

— End - Existing —

• • • Update ***
      The current version of the data model supports the following technology independent event records:

• fault - the fault record, describing a condition in the fault domain, contains information about device failures. The fault event provides data such as the entity experiencing a fault, the severity, resulting status, etc.
• heartbeat - the heartbeat record provides an optional structure for communicating information about device health. Heartbeat records would only have the Common Event Header block. An optional heartbeat domain is available to specify information such as heartbeat interval and recommended action upon missing heartbeat interval. Heartbeat avoids the need to ping a device. A communication failure can be determined via missing heartbeat events being delivered to DCAE and appropriate action (e.g. restart VM, rebuild VNF or PNF or create ticket) can be taken by DCAE CLAMP.
• measurement - the measurement record contains information about VNF or PNF and VNF or PNF resource structure and its condition to help in the management of the resources for purposes of capacity planning, elastic scaling, performance management and service assurance. These are soft alarms providing an opportunity for proactive maintenance.
• notification - the notification record provides a structure for communicating notification information from the VNF or PNF. The notification record can contain notification information related to the current operational state that is reported by the VNF or PNF. As an example, when cards or port name of the entity have changed state. (e.g., offline -> online) Other use cases include notification of file ready for collection using Bulk Data Transfer or notification on configuration changes to a device.
• other - the other record defines fields for events that do not have a defined domain but are needed to be collected and sent to DCAE. This record provides a mechanism to convey a complex set of fields (possibly nested or opaque) and is purely intended to address miscellaneous needs such as addressing time-to-market considerations or other proof-of-concept evaluations. Hence, use of this record type is discouraged and should be minimized. (Note: the other domain could be used to create and test new domain ideas.)
• perf3gpp - the perf3gpp record provides a structure for communicating information that supports 3GPP defined performance metrics. The perf3gpp record can contain information from vendors, including measurement name, measurement family, measured object class, description, collection method, value ranges, unit of measure, triggering conditions and other measurement information.
• pnfRegistration - the pnfRegistration record provides a structure for registration of a physical network function. The pnfRegistration record can contain information about attributes related to the physical network function including serial number, software revision, unit type and vendor name.
• stateChange - the stateChange record provides a structure for communicating information about data flow through the VNF or PNF. The stateChange record can contain information about state change related to physical device that is reported by the VNF or PNF. As an example, when cards or port name of the entity that has changed state. Note: The notification domain can also communicate similar information.
• syslog - the syslog record provides a structure for communicating any type of information that may be logged by the VNF or PNF. It can contain information about system internal events, status, errors, etc. It is recommended that low volume control or session logs are communicated via a push mechanism, while other large volume logs should be sent via file transfer.
• thresholdCrossingAlert - the thresholdCrossingAlert (TCA) record provides a structure for communicating information about threshold crossing alerts. It uses data from the measurement or a similar domain to watch for a Key Performance Indicator (KPI) threshold that has been crossed. TCA provides alert definitions and types, actions, events, timestamps and physical or logical details.

• • • End - Update ***