WARNING! Gitlab maintenance operation scheduled for Monday, 20 April between 12:00 and 14:00 (CET). During this time window, short service interruptions (less than 5 minutes) may occur. Thank you in advance for your understanding.
Title:Network Functions Virtualisation (NFV); Protocols and Data Models; Specification of protocol and data model solutions for PIM services
Spec Number:NFV-SOL 026
Version:v0.0.8
Version:v0.0.9
Date:2025-11
Release:5
Work Item:DGS/NFV-SOL026
@@ -1406,7 +1406,10 @@ The procedure consists of the following steps as illustrated in figure 9.4.8-1.
1. When generating a performance report according to the configured PmJob (*MetricReportDefinition*) as part of the created subscription, an event of type *MetricReport* gets triggered. As a result of this, the PIM generates a notification that includes the performance report and sends it in the body of a POST request to the notification target URI which the API consumer had registered as part of the subscription request.
<<<<<<< HEAD
**Postcondition:** None.
**Error handling:** None.
## 9.5 Resources
### 9.5.1 Introduction
@@ -1555,7 +1558,7 @@ The URI query parameters, request and response bodies, and response codes of the
### 9.5.8 Resource: Subscriptions
This resource represents subscriptions related to performance management of physical resources and can be used to retrieve a collection of already created subscription resources as well as to create a new individual subscription resource. This resource can also be used to create a PmJob in the form of a subscription for receiving performance reports asynchronoulsy as notifications.
This resource represents subscriptions related to performance management of physical resources and can be used to retrieve a collection of already created subscription resources as well as to create a new individual subscription resource. This resource can also be used to create a PmJob in the form of a subscription for receiving performance reports asynchronously as notifications.
Table 9.5.8-1 specifies the supported HTTP methods for this resource and maps them against the PIM service interface requirements as specified in ETSI GS NFV-IFA 053 [\[1\]](#_ref_1).
@@ -1633,11 +1636,6 @@ The URI query parameters, request and response bodies, and response codes of the
## 9.6 Data model
The request and response data structures of the physical resource performance management service interface are defined in the Redfish® data model specification [\[3\]](#_ref_3).
=======
**Postcondition:** None.
**Error handling:** None.
>>>>>>> 8d782de (add postcondition and error handling fields in notification related flows)
# 10 Physical resource fault management service interface
@@ -1781,6 +1779,7 @@ The procedure consists of the following steps as illustrated in figure A.5-1.
|October 2025|V0.0.6|Implements following contributions:<br/>NFVSOL(25)000335, NFVSOL(25)000336, NFVSOL(25)000337, NFVSOL(25)000338|
|November 2025|V0.0.7|The first version created using the SOL026 repository on ETSI Forge, no technical changes on top of v0.0.6|
|November 2025|V0.0.8|Implements following contributions:<br/>NFVSOL(25)000393, NFVSOL(25)000402, NFVSOL(25)000404|
|November 2025|V0.0.9|Implements following contributions:<br/>NFVSOL(25)000411r1, NFVSOL(25)000412|
