4.4 NS Instance procedures

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

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

4.4.1 NS Instance instantiation

Figure 4.4.1-1 depicts the procedure of an NS instantiation initiated through the Os-Ma-nfvo reference point (see clause 7.3.3 [5]). The procedure includes the steps of creating first the corresponding NS instance identifier.

1. NM sends to NFVO a CreateNsIdentifierRequest with parameters nsdId, nsName, and nsDescription to create an NS instance identifier (nsInstanceId) and an associated instance of an NsInfo information element (see clause 7.3.2.2 [5]).

2. NFVO sends to NM a CreateNsIdentifierResponse with parameter nsInstanceId identifying the instance of the NS that has been created (see clause 7.3.2.3 [5]).

3. NFVO sends to subscribers a Notify (see clause 7.4.3 [5]) carrying NsIdentifierCreationNotification information element with attribute nsInstanceId to indicate the NS instance idenfier creation (see clause 8.3.2.9 [5]).

4. NM sends to NFVO an InstantiateNsRequest with parameters nsInstanceId and flavourId. Additional parameters can be provided including sapData, pnfInfo, locationConstraints, additionalParamsForNs, additionalParamForVnf, startTime, nsInstantiationLevelId, and additionalAffinityOrAntiAffinityRule. In addition, if the NS instantiation includes reusing existing VNF instances and/or NS instances, parameters vnfInstanceData and nestedNsInstanceId are provided, respectively. See clause 7.3.3.2 [5].

5. NFVO sends to NM an InstantiateNsResponse with parameter lifecycleOperationOccurrenceId providing the identifier of the NS lifecycle operation occurrence (see clause 7.3.3.3 [5]).

6. NFVO sends to NM a Notify (see clause 7.4.3 [5]) carrying an NsLifecycleChangeNotification information element with attributes nsInstanceId, lifecycleOperationOccurrenceId, operation = "NsInstantiation", and notificationType = "start" to indicate the start of the NS instantiation (see clause 8.3.2.2 [5]).

7. NFVO sends to NM a Notify (see clause 7.4.3 [5]) carrying an NsLifecycleChangeNotification information element with attributes nsInstanceId, lifecycleOperationOccurrenceId, operation = "NsInstantiation", and notificationType = "result" to indicate the end result of the NS instantiation. According to the results of the NS instantiation, additional information is provided in the notification with parameters affectedVnf, affectedPnf, affectedVl, affectedVnffg, affectedNs and affectedSap (see clause 8.3.2.2 [5]).

NFVO

3. Notify

5. InstantiateNsResponse

6. Notify

7. Notify

1. CreateNsIdentifierRequest

2. CreateNsIdentifierResponse

4. InstantiateNsRequest

Figure 4.4.1-1: NS instantiation

4.4.2 NS Instance termination

Figure 4.4.2-1 depicts the procedure of an NS instance termination initiated through the Os-Ma-Nfvo reference point (see clause 7.3.7 [5]).

1. NM sends to NFVO a TerminateNsRequest with parameter nsInstanceId and terminateTime (see clause 7.3.7 [5]).

2. NFVO sends to NM a TerminateNsResponse with parameter lifecycleOperationOccurrenceId providing the identifier of the NS lifecycle operation occurrence (see clause 7.3.7.3 [5]).

3. NFVO sends to NM a Notify (see clause 7.4.3 [5]) carriying an NsLifecycleChangeNotification information element with attributes nsInstanceId, lifecycleOperationoccurrenceId, operation = “TerminationNs”, and “notificationType” = “start’ to indicate the start of the NS termination (see clause 8.3.2.2 [5]).

Figure 4.4.2-1: NS instance termination

4.4.3 NS Instance querying

4.4.3.1 Query NS instance information through Os-Ma-nfvo

Figure 4.4.3.1-1 depicts the procedure of NS querying through the Os-Ma-nfvo reference point (see clause 7.3.6 in [5]) used also to query information about the constituents of the NS instance, including VNF instances.

1. NM sends to NFVO a QueryNsRequest with parameters filter and attributeSelector used to filter the NS instances on which the query applies, based on attributes of the NS instance and select the information attributes that are requested to be returned (see clause 7.3.6.2 [5]).

In particular, the filter can be set to select certain VNF instances(s) that are part of an NS, by providing their identifiers with the attributeSelector set to select certain attributes of the VNF instances.

2. NFVO sends to NM a QueryNsResponse with parameter queryNsResult providing the information that is selected according to parameters filter and attributeSelector (see clause 7.3.6.3 [5]).

NFVO

1. QueryNsRequest

2. QueryNsResponse

Figure 4.4.3.1-1: Query NS instance information through Os-Ma-nfvo

4.4.4 NS Instance scaling

Figure 4.4.4-1 depicts a procedure for NS Instance scaling. Scaling an NS instance can be performed by explicitly adding/removing existing VNF instances to/from the NS instance, by leveraging on the abstraction mechanism provided by the NS scaling aspects and NS levels information elements declared in the NSD or by scaling individual VNF instances (as described by the Use Case 6.4.3.4 in [3]) that are part of the NS itself. When adding VNFs and nested NSs – already existing or not – to the NS to be scaled, the NFVO shall follow the indications provided by the dependencies attribute, as specified in the corresponding NSD.

1. NM sends ScaleNsRequest to NFVO with nsInstanceId parameter identifying the NS Instance being scaled, scaleType parameter with possible values [SCALE_NS, SCALE_VNF]indicating the type of scaling to be performed, list of scaleNsData providing necessary scale information when scaleType = SCALE_NS or list of scaleVnfData providing necessary scale information when scaleType = SCALE_VNF and scaleTime indicating the scale time of the NS if it’s not expected to start immediately (see clause 7.3.4 [5]).

2. NFVO sends ScaleNsResponse to NM with the lifecycleOperationOccurrenceId identifier of the NS lifecycle operation occurrence (see clause 7.3.4.4 [5]).

3. NFVO sends to NM a Notify (see clause 7.4.3 [5]) carrying an NsLifecycleChangeNotification information element with attributes nsInstanceId, lifecycleOperationOccurrenceId, operation = "ScaleNs", and notificationType = "start" to indicate the start of the NS scale (see clause 8.3.2.2 [5]).

4. NFVO sends to NM a Notify (see clause 7.4.3 [5]) carrying an NsLifecycleChangeNotification information element with attributes nsInstanceId, lifecycleOperationOccurrenceId, operation = "ScaleNs", notificationType = "result" to indicate the result of NS scale. Per the changes in the NS instance performed because of the NS scale, additional information is provided in the notification with parameters affectedVnf, affectedPnf, affectedVl, affectedVnffg, affectedNs and affectedSap (see clause 8.3.2.2 [5]).

Figure 4.4.4-1: NS Instance scaling procedure

4.4.5 NS Instance updating

4.4.5.1 NS update to associate an NS instance to a different NSD version

Figure 4.4.5.1-1 depicts the procedure of NS update to associate an NS instance to a different NSD version.

1. NM sends to NFVO an UpdateNsRequest with parameters nsInstanceId, updateType = "AssociateNewNsdVersion", assocNewNsdVersionData, and updateTime to associate a new NSD version to the NS instance (see clause 7.3.5.2 [5]). The assocNewNsdVersionData contains the parameter newNsdId, and can include in addition the parameter sync to indicate whether the NS instance should be automatically synchronized to the new NSD by the NFVO.

2. NFVO sends to NM an UpdateNsResponse with parameter lifecycleOperationOccurrenceId providing the identifier of the NS lifecycle operation occurrence (see clause 7.3.5.3 [5]).

3. NFVO sends to NM a Notify (see clause 7.4.3 [5]) carrying an NsLifecycleChangeNotification information element with attributes nsInstanceId, lifecycleOperationOccurrenceId, operation = "UpdateNs", and notificationType = "start" to indicate the start of the NS update (see clause 8.3.2.2 [5]).

4. NFVO sends to NM a Notify (see clause 7.4.3 [5]) carrying an NsLifecycleChangeNotification information element with attributes nsInstanceId, lifecycleOperationOccurrenceId, operation = "UpdateNs", notificationType = "result" to indicate the end result of NS update. According to the changes in the NS instance performed as a result of the NS update, additional information is provided in the notification with parameters affectedVnf, affectedPnf, affectedVl, affectedVnffg, affectedNs and affectedSap (see clause 8.3.2.2 [5]).

NFVO

1. UpdateNsRequest

2. UpdateNsResponse

3. Notify

4. Notify

Figure 4.4.5.1-1: NS update to associate an NS instance to a different NSD version

4.4.5.2 Modifying VNF instance information through Os-Ma-nfvo

Figure 4.4.5.2-1 depicts the procedure of modifying VNF instance information through the Os-Ma-nfvo reference point (see clause 7.3.5 [5]).

1. NM sends to NFVO an UpdateNsRequest with parameters nsInstanceId, updateType = "ModifyVnfInformation", modifyVnfInfoData, and updateTime to modify the VNF instance information (see clause 7.3.5.2 [5]). The modifyVnfInfoData contains the parameters that are needed for VNF instance information modification, namely vnfInstanceId, and list of newValues (see clause 8.3.4.17 [5]).

2. NFVO sends to NM an UpdateNsResponse with parameter lifecycleOperationOccurrenceId providing the identifier of the NS lifecycle operation occurrence (see clause 7.3.5.3 [5]).

3. NFVO sends to NM a Notify (see clause 7.4.3 [5]) carrying an NsLifecycleChangeNotification information element with attributes nsInstanceId, lifecycleOperationOccurrenceId, operation = "UpdateNs", and notificationType = "start" to indicate the start of the NS update that includes the VNF instance information modification (see clause 8.3.2.2 [5]).

4. NFVO sends to NM a Notify (see clause 7.4.3 [5]) carrying an NsLifecycleChangeNotification information element with attributes nsInstanceId, lifecycleOperationOccurrenceId, operation = "UpdateNs", notificationType = "result" to indicate the end result of NS update that includes the VNF instance information modification, and affectedVnf providing information about the VNF instance whose information has been modified, including vnfInstanceId, vnfdId, vnfProfileId, vnfName and changeType = "information modified" (see clauses 8.3.2.2 and 8.3.2.3 [5]).

NFVO

1. UpdateNsRequest

2. UpdateNsResponse

3. Notify

4. Notify

Figure 4.4.5.2-1: Modifying VNF instance information through Os-Ma-nfvo

4.4.5.3 Modifying VNF instance configuration through Os-Ma-nfvo

Figure 4.4.5.3-1 depicts the procedure of modifying VNF instance configuration through the Os-Ma-nfvo reference point (see clause 7.3.5 [5]).

1. NM sends to NFVO an UpdateNsRequest with parameters nsInstanceId, updateType = “ModifyVnfConfig”, modifyVnfConfigData, and updateTime to modify the VNF instance configuration (see clause 7.3.5.2 [5]). The modifyVnfConfigData contains the parameters that are needed for VNF instance configuration modification, namely vnfInstanceId, list of vnfConfigurationData and list of extVirtualLink (see clause 8.3.4.18 [5]).

2. NFVO sends to NM an UpdateNsResponse with parameter lifecycleOperationOccurrenceId providing the identifier of the NS lifecycle operation occurrence (see clause 7.3.5.3 [5]).

3. NFVO sends to NM a Notify (see clause 7.4.3 [5]) carrying an NsLifecycleChangeNotification information element with attributes nsInstanceId, lifecycleOperationOccurrenceId, operation = "UpdateNs", and notificationType = "start" to indicate the start of the NS update that includes the VNF instance configuration modification (see clause 8.3.2.2 [5]).

4. NFVO sends to NM a Notify (see clause 7.4.3 [5]) carrying an NsLifecycleChangeNotification information element with attributes nsInstanceId, lifecycleOperationOccurrenceId, operation = "UpdateNs", notificationType = "result" to indicate the end result of the NS update that includes the VNF instance configuration modification, and affectedVnf providing information about the modified VNF instance whose configuration has been modified, including vnfInstanceId, vnfdId, vnfProfileId, vnfName and changeType = "configuration modified" (see clauses 8.3.2.2 and 8.3.2.3 [5]).

Figure 4.4.5.3-1: Modifying VNF instance configuration through Os-Ma-nfvo

4.4.5.4 NS update to add a PNF to the NS instance

Figure 4.4.5.4-1 depicts the procedure of NS update to add a PNF to the NS instance (see clause 7.3.5 [5]). It is assumed that the PNFD of the PNF to be added has been on-boarded, and the NS where the PNF instances are to be added has been instantiated.

1. NM sends to NFVO an UpdateNsRequest (see clause 7.3.5 of [5]) with the following parameters (see clause 7.3.5.2 of [5]) to on-board the NSD:

– nsInstanceId: the identifier of the NS instance being updated.

– updateType = “AddPnf” to indicate the type of update operation.

– addPnfData: the PNF information that contain the following attributes (see clause 8.3.4.32.2 of [5]):

> pnfId: the identifier of the PNF;

> pnfName: human readable name of the PNF;

> pnfdId: identifier (reference to) the PNFD related to this PNF;

> pnfProfileId: identifier (reference to) the PNF Profile to be used for this PNF;

> cpData: information of the external CP of the PNF.

2. NFVO sends to NM an UpdateNsResponse (see clause 7.3.5 of [5]) with the attribute lifecycleOperationOccurrenceId that is the identifier of the NS lifecycle operation occurrence.

3. NFVO sends to NM a Notify (see clause 7.4.3 [5]) carrying an NsLifecycleChangeNotification information element with attributes nsInstanceId, lifecycleOperationOccurrenceId, operation = "NsUpdate", and notificationType = "start" to indicate the start of the NS instantiation (see clause 8.3.2.2 [5]).

Figure 4.4.5.4-1: NS update to add a PNF to the NS instance

4.4.5.5 NS update to modify a PNF in the NS instance

Figure 4.4.5.5-1 depicts the procedure of NS update to modify the PNF to the NS instance (see clause 7.3.5 [5]). It is assumed that the NS where the PNF instances are to be modified has been instantiated.

1. NM sends to NFVO an UpdateNsRequest (see clause 7.3.5 of [5]) with the following parameters (see clause 7.3.5.2 of [5]) to on-board the NSD:

– nsInstanceId: the identifier of the NS instance being updated.

– updateType = "ModifyPnf" to indicate the type of update operation.

– modifyPnfData: the PNF information that contain the following attributes (see clause 8.3.4.33.2 of [5]):

> pnfId: the identifier of the PNF;

> pnfName: human readable name of the PNF;

> cpData: information of the external CP of the PNF.

2. NFVO sends to NM an UpdateNsResponse (see clause 7.3.5 of [5]) with the attribute lifecycleOperationOccurrenceId that is the identifier of the NS lifecycle operation occurrence.

3. NFVO sends to NM a Notify (see clause 7.4.3 [5]) carrying an NsLifecycleChangeNotification information element with attributes nsInstanceId, lifecycleOperationOccurrenceId, operation = "NsUpdate", and notificationType = "start" to indicate the start of the NS instantiation (see clause 8.3.2.2 [5]).

Figure 4.4.5.5-1: NS update to modify a PNF in the NS instance

4.4.5.6 NS update to remove a PNF from the NS instance

Figure 4.4.5.6-1 depicts the procedure of NS update to remove the PNF from the NS instance (see clause 7.3.5 [5]). It is assumed that the NS where the PNF instances are to be removed has been instantiated.

1. NM sends to NFVO an UpdateNsRequest (see clause 7.3.5 of [5]) with the following parameters (see clause 7.3.5.2 of [5]) to on-board the NSD:

– nsInstanceId: the identifier of the NS instance being updated.

– updateType = “RemovePnf” to indicate the type of update operation.

– removePnfId: the identifier of the PNF(s) in the NS instance that are to be removed.

2. NFVO sends to NM an UpdateNsResponse (see clause 7.3.5 of [5]) with the attribute lifecycleOperationOccurrenceId that is the identifier of the NS lifecycle operation occurrence.

3. NFVO sends to NM a Notify (see clause 7.4.3 [5]) carrying an NsLifecycleChangeNotification information element with attributes nsInstanceId, lifecycleOperationOccurrenceId, operation = "NsUpdate", and notificationType = "start" to indicate the start of the NS instantiation (see clause 8.3.2.2 [5]).

Figure 4.4.5.6-1: NS update to remove a PNF from the NS instance

4.4.5.7 NS update to associate an VNF instance with a VNF profile

Figure 4.4.5.7-1 contains a procedure to show how the connectivity of a VNF instance can be added or changed by associating such VNF instance with a new or updated VnfProfile that includes the NS virtual link information. It is assumed that the NSD with the new or updated VnfProfile has been uploaded to the NFVO, and the NSD has been associated with the NS containg such VNF instance, according to clause 4.4.5.1.

Figure 4.4.5.7-1: Associate an VNF instance with a VNF profile

1. NM sends to NFVO an UpdateNsRequest (see clause 7.3.5 [5]) with parameters nsInstanceId, updateType = "AssocVnfWithVnfProfile", vnfInstanceId and vnfProfileId to associate the VNF instance with the VNF profile.

2. NFVO sends to NM an UpdateNsResponse (see clause 7.3.5 [5]) with the attribute lifecycleOperationOccurrenceId that is the identifier of the NS lifecycle operation occurrence.

3. NFVO sends to NM a Notify (see clause 7.4.3 [5]) carrying an NsLifecycleChangeNotification information element with attributes nsInstanceId, lifecycleOperationOccurrenceId, operation = "NsUpdate", and notificationType = "start" to indicate the start of the NS update.

4.4.5.8 NS update to associate an PNF with a PNF profile

Figure 4.4.5.8-1 contains a procedure to show how the connectivity of a PNF can be added or changed by associating such PNF with a new or updated PnfProfile that includes the NS virtual link information. It is assumed that the NSD with the new or updated PnfProfile has been uploaded to the NFVO, and the NSD has been associated with the NS containg such PNF, according to clause 4.4.5.1.

Figure 4.4.5.8-1: Associate an PNF with a PNF profile

1. NM sends to NFVO an UpdateNsRequest (see clause 7.3.5 [5]) with parameters nsInstanceId, updateType = "AssocPnfWithPnfProfile", pnfId and pnfProfileId to associate the PNF instance with the PNF profile.

2. NFVO sends to NM an UpdateNsResponse (see clause 7.3.5 [5]) with the attribute lifecycleOperationOccurrenceId that is the identifier of the NS lifecycle operation occurrence.

3. NFVO sends to NM a Notify (see clause 7.4.3 [5]) carrying an NsLifecycleChangeNotification information element with attributes nsInstanceId, lifecycleOperationOccurrenceId, operation = "NsUpdate", and notificationType = "start" to indicate the start of the NS update.

4.4.6 Subscription regarding NS Instance lifecycle changes

The Figure 4.4.6-1 depicts a procedure of subscription to NS instance lifecycle change notifications

1. NM sends SubscribeRequest message to NFVO with input parameter filter described in 7.4.2.2 [5] used for selecting the notifications, which can be on the NS instance(s) of interest or other attributes of the notification, to subscribe for the notifications sent by the NFVO supported on the NS lifecycle change notification interface.

2. NFVO sends SubscribeResponse message to NM to indicate if the subscription has been successful or not with a standard success/error result. Output parameter subscriptionId is specified in 7.4.2.3 [5] to provide the identifier of the subscription realized. After successful subscription, the consumer (NM) is registered to receive notifications supported on the NS lifecycle change notification interface. For a particular subscription, only notifications matching the filter will be delivered to the consumer (see clause 7.4.2.4 [5]).

Figure 4.4.6-1: Subscribing to NS lifecycle change notifications through Os-Ma-nfvo

4.4.7 Create NS Instance identifier

Figure 4.4.7-1 depicts a procedure for creation of an NS instance identifier, and an associated instance of an NsInfo information element, identified by that identifier, in the NOT_INSTANTIATED state without instantiating the NS or doing any additional lifecycle operation(s). It allows the immediate return of an NS instance identifier that can be used in subsequent lifecycle operations, such as the Instantiate NS operation (see NS state model in clause D.3 [5]).

1. NM sends CreateNsIdentifierRequest to NFVO with nsdId parameter referencing the NSD used to create this NS instance, nsName parameter providing human readable name of the NS instance and nsDescription parameter providing human readable description of the NS instance (see clause 7.3.2 [5]).

2. NFVO sends CreateNsIdentifierResponse to NM with the nsInstanceId identifier of the instance of a NS that has been created (see clause 7.3.2.4 [5]).

Figure 4.4.7-1: Create NS Instance identifier procedure

4.4.8 Delete NS Instance identifier

Figure 4.4.8-1 depicts the procedure of an NS instance identifier deletion initiated through the Os-Ma-Nfvo reference point (see clause 7.3.8 [5]).

1. NM sends to NFVO a DeleteNsRequest with parameter nsInstanceId to delete the NS instance identifier (see clause 7.3.8.2 [5]).

2. NFVO sends to NM a DeleteNsResponse (see clause 7.3.8.2 [5]).

3. NFVO sends to NM a Notify (see clause 7.4.3 [5]) carrying NsIdentifierObjectDeletionNotification information element with attributes nsInstanceId to indicate the result of the NS instance identifier deletion (see clause 8.3.2.10 [5]).

Figure 4.4.8-1: NS instance identifier deletion

4.4.9 Procedure for the Notify operation for notifications to NM

The Figure 4.4.9-1 depicts a procedure of notification on NS instance lifecycle change notifications

1. NFVO sends Notify message to NM according to 7.4.3 [5]. This operation distributes to subscribers the notifications supported on the NS lifecycle changes notification interface. In order to receive notifications, the consumer (NM) has to perform an explicit Subscribe operation beforehand.

Figure 4.4.9-1: Procedure for the Notify operation

The following notifications can be notified/sent by this operation:

– NsLifecycleChangeNotification. See clause 8.3.2.2 [5] with the list of attributes in the Table 8.3.2.2.3-1 [5].

– NsIdentifierCreationNotification. See clause 8.3.2.9 [5] with the attribute nsInstanceId per Table 8.3.2.9.3-1 [5].

– NsIdentifierDeletionNotification. See clause 8.3.2.10 [5] with the attribute nsInstanceId per Table 8.3.2.10.3-1.