Below is the update for: Section 7.4 Monitoring & Management

— Existing —
This section addresses data collection and event processing functionality that is directly dependent on the interfaces provided by the xNFs’ APIs. These can be in the form of asynchronous interfaces for event, fault notifications, and autonomous data streams. They can also be synchronous interfaces for on-demand requests to retrieve various performance, usage, and other event information. It should be understood that events are well structured packages of information, identified by an eventName, which are communicated to subscribers who are interested in the eventName. Events are simply a way of communicating well-structured packages of information to one or more instances of an Event Listener service.
The target direction for xNF interfaces is to employ APIs that are implemented utilizing standardized messaging and modeling protocols over standardized transports. Virtualized environments present a tremendous opportunity to eliminate the need for proprietary interfaces for xNF provider equipment while removing the traditional boundaries between Network Management Systems and Element Management Systems. Additionally, virtualized NFs provide the ability to instrument networking applications by creating event records to test and monitor end-to-end data flow through the network, similar to what physical or virtual probes provide without the need to insert probes at various points in the network. The xNF providers must be able to provide the aforementioned set of required data directly to the ONAP collection layer using standardized interfaces.
— End - Existing —

• • • Update ***
      This section addresses data collection and event processing functionality that is directly dependent on the interfaces provided by the VNF or PNF’s APIs. These can be in the form of asynchronous interfaces for event, fault notifications, and autonomous data streams. They can also be synchronous interfaces for on-demand requests to retrieve various performance, usage, and other event information. It should be understood that events are well structured packages of information, identified by an eventName, which are communicated to subscribers who are interested in the eventName. Events are simply a way of communicating well-structured packages of information to one or more instances of an Event Listener service.
      The target direction for VNF or PNF interfaces is to employ APIs that are implemented utilizing standardized messaging and modeling protocols over standardized transports. Standardized environments (physical, virtual or hybrid) present a tremendous opportunity to eliminate the need for proprietary interfaces for VNF or PNF provider equipment while removing the traditional boundaries between Network Management Systems and Element Management Systems. Additionally, virtualized NFs provide the ability to instrument networking applications by creating event records to test and monitor end-to-end data flow through the network, similar to what physical or virtual probes provide without the need to insert probes at various points in the network. The VNF or PNF providers must be able to provide the aforementioned set of required data directly to the ONAP collection layer using standardized interfaces.
    • End - Update ***