4.6 PNFD procedures

28.5263GPPLife Cycle Management (LCM) for mobile networks that include virtualized network functionsProceduresRelease 17Telecommunication managementTS

4.6.1 PNFD on-boarding

Figure 4.6.1-1 depicts a procedure for on-boarding a PNFD in the NFVO, making it available to be used by NSDs.

1. NM sends OnboardPnfdRequest to NFVO with pnfd parameter representing the PNFD to be on-boarded and list of userDefinedData key-value pairs providing user defined data for the PNFD (see clause 7.2.8 [5]).

2. NFVO sends OnboardPnfdResponse to NM with the pnfdInfoId identifier of the on-boarded instance of the PNFD (see clause 7.2.8.4 [5]).

Figure 4.6.1-1: PNFD on-boarding procedure

4.6.2 PNFD updating

Figure 4.6.2-1 depicts a procedure for updating a PNFD, creating a new version of already on-boarded PNFD. The procedure can also be used to update the userDefinedData of an existing PnfInfo information element without creating a new version of the PNFD. The previous versions of the PNFD are not modified.

1. NM sends UpdatePnfdRequest to NFVO with pnfdInfoId parameter representing the identifier of on-boarded PNFD to be updated, an optional (only present if the PNFD itself is updated) pnfd parameter representing the new PNFD to be created and list of userDefinedData key-value pairs optional parameter representing the user defined data to be updated (for existing keys, the value is replaced). At least one of the two parameters (pnfd or userDefinedData) needs to be present. If pnfd is not present, the operation is used only to update existing or add additional user defined data using the userDefinedData parameter (see clause 7.2.9 [5]).

2. NFVO sends UpdatePnfdResponse to NM with pnfdInfoId parameter representing the identifier of the updated PNFD to indicate the result of the operation (see clause 7.2.9.4 [5]).

Figure 4.6.2-1: PNFD updating procedure

4.6.3 PNFD deletion

Figure 4.6.3-1 depicts a procedure for deletion of one or more PNFD(s). A PNFD can only be deleted when there is no NS (in the active or NOT_INSTANTIATED state) using it. It is not possible to instantiate NSs that include a PNFD in deletion pending state.

1. NM sends DeletePnfdRequest to NFVO with list of pnfdInfoId parameter representing the identifier(s) of on-boarded PNFD(s) to be deleted and an optional applyOnAllVersions parameter indicating if the delete operation is to be applied on all versions of this PNFD. By default, if applyOnAllVersions parameter is not present, the request applies only on the current PNFD version. (see clause 7.2.10 [5]).

2. NFVO sends DeletePnfdResponse to NM with list of deletedPnfdInfoId parameter representing the identifier(s) of deleted PNFD(s) to indicate the result of the operation (see clause 7.2.10.4 [5]).

Figure 4.6.3-1: PNFD deletion procedure

4.6.4 PNFD querying

Figure 4.6.4-1 depicts a procedure to query the NFVO concerning details of one or more PNFDs.

1. NM sends QueryPnfdRequest to NFVO with filter and attributeSelector used to filter the PNFD(s) on which the query applies, based on the attributes of PnfdInfo and select the information attributes of PnfdInfo that are requested to be returned (see clause 7.2.11 [5]).

2. NFVO sends QueryPnfdResponse to NM with parameter queryResult providing the information of the on‑boarded PNFD matching the input filter that is selected according to attributeSelector (see clause 7.2.11.4 [5]).

Figure 4.6.4-1: PNFD querying procedure

Annex A (informative):
Change history

Change history
Date	Meeting	TDoc	CR	Rev	Cat	Subject/Comment	New version
2018-03	SA#79	SP-180059	0002	1	F	Scope extension	14.1.0
2018-03	SA#79	SP-180059	0004	1	F	Procedures of PNF addition, removal, and modification	14.1.0
2018-06	–	–	–	–	–	Update to Rel-15 version (MCC)	15.0.0
2018-12	SA#82	SP-181040	0014	1	F	Add a procedure to associate an VNF instance with a VNF profile	15.1.0
2018-12	SA#82	SP-181040	0015	1	F	Add a procedure to associate an PNF with a PNF profile	15.1.0
2020-07	–	–	–	–	–	Update to Rel-16 version (MCC)	16.0.0
2022-03	–	–	–	–	–	Update to Rel-17 version (MCC)	17.0.0