Goal

EM requests to create a VNF identifier.

Actors and Roles

EM

Telecom resources

VNFM

Assumptions

N/A

Pre-conditions

NFVO is running.

Begins when

EM decides to request to create a VNF identifier.

Step 1 (M)

EM sends a request to VNFM to create the VNF identifier (see clause 7.2.2 [8])

Step 2 (M)

VNFM returns vnfInstanceId to EM to indicate the creation of VNF identifier (see clause 7.2.2.3 [8])

Ends when

Ends when EM receives the vnfInstanceId.

Exceptions

One of the steps identified above fails.

Post-conditions

The VNF identifier is created.

Traceability

REQ-NFV_LCM_Ve-Vnfm-em-FUN-9

Goal

Create a VNF instance based on the local needs of the EM (e.g. for VNF validation prior to deployments in production environment).

Actors and Roles

EM

Telecom resources

VNFM

Assumptions

The association of the new VNF instance to a NS instance enabling the VNF LCM granting operations and VR management is out of scope of 3GPP.

Pre-conditions

The VNF Package for the VNF instantiation is enabled and is available to the VNFM.

EM is subscribed to the VNF LCM notifications (see clause 7.3.2 [8]).

Begins when

EM decides to instantiate a new VNF instance.

Step 1 (M)

EM requests VNFM to create a new VNF instance Identifier (see clause 7.2.2 [8]) using the VNFD Id to identify the VNF Package to be used for instantiation.

Step 2 (M)

VNFM responds to EM with new VNF instance Identifier

Step 3 (M)

EM requests VNFM to instantiate the new VNF (see clause 7.2.3 [8]).

Step 4 (M)

VNFM responds to EM with the operation result containing the lifecycle operation occurrence Id

Step 5 (M)

VNFM sends the VNF lifecycle change notification to EM indicating the start of VNF instantiation procedure (see clause 7.3.3 [8]).

Step 6 (M)

VNFM sends the VNF lifecycle change notification to EM indicating the success or failure of the VNF instantiation, when the VNF instantiation procedure is completed (see clause 7.3.3 [8]).

Ends when

Ends when all mandatory steps identified above are successfully completed or when an exception occurs.

Exceptions

One of the steps identified above fails.

Post-conditions

A new VNF instance is instantiated but not associated to any NS (.see NOTE in clause 7.2.3.4 in [8]).

Traceability

REQ-NFV_LCM_Ve-Vnfm-em-FUN-1, REQ-NFV_LCM_Ve-Vnfm-em-FUN-2.

Goal

Enable NM to add a VNF instance to a NS via Os-Ma-nfvo reference point.

Actors and Roles

NM

Telecom resources

NM, NFVO

Assumptions

N/A

Pre-conditions

The VNF Package for the VNF instantiation is enabled.

Begins when

NM decides to instantiate a VNF instance that is part of an NS.

Step 1 (M)

NM sends a request to NFVO to instantiate a VNF instance as part of the update of a NS (see clause 7.3.3 in ETSI GS NFV-IFA 013 [6]) and the VNF parameters/values, including those captured in vendor specific name value pairs, carried by such request are only related to VNF virtualization aspects and are not VNF application specific..

Step 2 (M)

NFVO sends the NS Lifecycle Change notification to NM indicating the addition of the VNF instance (see clause 5.3.3 [6]), when the VNF instantiation procedure is completed.

Ends when

Ends when NM receives the notification from NFVO indicating the VNF instance has been successfully instantiated.

Exceptions

One of the steps identified above fails.

Post-conditions

A new VNF instance is instantiated.

Traceability

REQ-NFV_LCM_Os-Ma-nfvo-FUN-16, REQ-NFV_LCM_Os-Ma-nfvo-FUN-18

Goal

To expand/contract a VNF instance by scaling the VNF instance through operation request to VNFM by EM, and notify about the execution of the VNF instance scaling through reference point Ve-Vnfm-em.

Actors and Roles

EM detects whether a scaling execution is needed and requests the VNFM to execute the VNF scaling.

Telecom resources

EM.

VNFM.

VNF

Assumptions

EM is subscribed to VNF lifecycle change notifications from the VNFM.

See note 1.

Pre-conditions

The subject VNF instance is not being scaled at the moment. VNFM does not have any auto-scaling scripts or the policy for auto-scaling is not in used or active (see note 2).

Begins when

EM detected the need (e.g., triggered by MO attribute value modification from NM) to scale and have determined the scaling action (expand/contract).

Step 1 (M)

EM sends the VNFM a request to scale a VNF with an indication of the type of VNF Components to scale, and value of scaling.

Step 2 (M)

VNFM sends to EM a notification about the start of the VNF scaling execution.

Step 3 (M)

The VNFM executes the procedure to scale the VNF instance.

Step 4 (M)

VNFM sends to EM a notification about the end of the VNF scaling execution.

Ends when

All the steps identified above are successfully completed.

Exceptions

Post-conditions

The VNF instance has been scaled (expansion/contraction).

Traceability

REQ-NFV_LCM_Ve-Vnfm-em-FUN-3, REQ-NFV_LCM_Ve-Vnfm-em-FUN-4

NOTE 1: In the case where VNF scaling is triggered by MOI attribute value changes, the IRPManager (Operator) is aware of the MO attributes whose value changes can trigger VNF scaling actions. How the IRPManager (Operator) knows the names of the MO attributes whose value change can trigger VNF scaling is out of scope of this specification (e.g. could be stated in NRM attribute definitions or in product documentation).

Goal

Enable EM to terminate a VNF instance which is no longer needed for testing and integration purpose.

Actors and Roles

EM

Telecom resources

VNFM

Assumptions

The VNF instance being terminated does not participate in any NS (see note 1).

Pre-conditions

The VNF instance to be terminated is no longer needed. The VNF instance has been instantiated (see NOTE in clause 7.2.3.4 in [8]) by the EM.

Begins when

EM decides to terminate a VNF instance.

Step 1 (M)

EM sends the request (see clause 5.2.1.1 [8]), to VNFM via Ve-Vnfm-em reference point to terminate the identified VNF instance.

Step 2 (M)

VNFM sends the VNF lifecycle change notification to EM indicating the start of VNF termination procedure (see clause 5.2.1.2 [8]).

Step 3 (M)

VNFM sends the VNF lifecycle change notification to EM indicating the result (e.g. success or failure) of VNF termination, when the VNF termination procedure is completed (see clause 5.2.1.2 [8]).

Ends when

Ends when all mandatory steps identified above are successfully completed or when an exception occurs.

Exceptions

One of the steps identified above fails.

Post-conditions

The VNF instance is terminated.

Traceability

REQ-NFV_LCM_Ve-Vnfm-em-FUN-6, REQ-NFV_LCM_Ve-Vnfm-em-FUN-7

NOTE 1: Participation of the VNF instance in a NS is not known to the EM/VNFM and could only be determined by the NFVO (e.g. during granting operation). Potential negative impact to the NS instance can be prevented by the granting operation.

Goal

Enable NM to delete a VNF instance from a NS via Os-Ma-nfvo reference point.

Actors and Roles

NM

Telecom resources

NM, NFVO

Assumptions

N/A

Pre-conditions

The VNF instance to be terminated is no longer needed,

Begins when

NM decides that VNF instance is no longer needed as part of the NS.

Step 1 (M)

NM sends a request to NFVO to remove a VNF instance from a NS instance (see clauses 5.3.2 [6]).

Step 2 (M)

NFVO sends the NS Lifecycle Change notification to NM indicating the removal of the VNF instance (see clauses 5.3.3 [6]).

Ends when

Ends when the VNF instance is removed from NS.

Exceptions

One of the steps identified above fails.

Post-conditions

The VNF is removed from NS.

Traceability

REQ-NFV_LCM_Os-Ma-nfvo-FUN-17, REQ-NFV_LCM_Os-Ma-nfvo-FUN-18

Goal

To monitor by EM the lifecycle changes of one or more VNF instance(s).

Actors and Roles

EM subscribes to and receives VNF lifecycle change notifications.

Telecom resources

EM.

VNFM.

VNF.

Assumptions

Pre-conditions

VNFM is running.

Begins when

EM determines to monitor VNF lifecycle changes on one or more managed VNF instance(s).

Step 1 (M)

EM requests a subscription to VNFM to receive VNF lifecycle change notifications regarding one or more managed VNF instance(s).

Step 2 (M)

VNFM creates a subscription and acknowledges the creation of the subscription to EM.

Step 3 (M)

VNFM monitors the lifecycles of the identified managed VNF instance(s).

Step 4 (M)

VNFM creates a VNF lifecycle change notification including information: identity the managed VNF instance, the type of lifecycle change including the beginning or the end of the procedure affecting the lifecycle changes.

Step 5 (M)

VNFM sends to EM the VNF lifecycle change notification(s).

Ends when

EM unsubscribes to VNF lifecycle change notification regarding the managed VNF instance(s).

Exceptions

Post-conditions

EM has information about VNF lifecycle changes of the one or more managed VNF instance(s).

Traceability

REQ-NFV_LCM_Ve-Vnfm-em-FUN-4, REQ-NFV_LCM_Ve-Vnfm-em-FUN-5

Goal

Enable/Disable the auto-scaling of a VNF instance (e.g.needed for testing and integration purposes).

Actors and Roles

EM

Telecom resources

VNFM

Assumptions

The auto-scaling is supported.

In cases where NM is aware of the VNF instance (e.g. it was instantiated by NM request), it is expected that NM is made aware of the of auto-scaling enable/disable flag value change resulting from this Use Case.

Pre-conditions

Begins when

EM decides to enable/disable the auto-scaling of a VNF instance.

Step 1 (M)

EM requests VNFM to enable/disable the auto-scaling of a VNF instance.

Step 2 (M)

VNFM notifies EM of the completion result of enabling/disabling the auto-scaling of the subject VNF instance.

Ends when

Ends when all steps identified above are completed or when an exception occurs.

Exceptions

One of the steps identified above fails.

Post-conditions

The auto-scaling of the VNF instance is enabled/disabled.

Traceability

REQ-NFV_LCM_Ve-Vnfm-em-FUN-8

Goal

To retrieve by EM from VNFM, information of a subject VNF instance.

Actors and Roles

EM queries the VNF instance information.

Telecom resources

EM.

VNFM.

VNF.

Assumptions

N/A

Pre-conditions

N/A

Begins when

EM determines to retrieve certain information about the subject VNF instance.

Step 1 (M)

EM sends a request to VNFM over the Ve-Vnfm-em reference point querying certain information about the subject VNF instance.

Step 2 (M)

VNFM sends to EM over the Ve-Vnfm-em reference point the information requested about the subject VNF instance.

Ends when

Ends when all steps identified above are completed or when an exception occurs.

Exceptions

One of the steps identified above fails.

Post-conditions

EM has the information about the subject VNF instance.

Traceability

REQ-NFV_LCM-CON-16, REQ-NFV_LCM_Ve-Vnfm-em-FUN-10

Goal

To retrieve by NM through NFVO information about a subject VNF instance as part of the query of a NS. Such information about a subject VNF instance is maintained by NFV-MANO (see clause 9.4.2 in ETSI GS NFV-IFA 008 [5]).

Actors and Roles

NM queries the information about a subject VNF instance which is part of NS instance.

Telecom resources

NM.

NFVO.

VNFM.

Assumptions

N/A

Pre-conditions

The subject VNF instance is part of the NS instance.

Begins when

NM determines to retrieve certain information about the subject VNF instance.

Step 1 (M)

As part of query of a NS, NM sends a request to NFVO over the Os-Ma-nfvo reference point querying certain information about the subject VNF instance (see clause 7.3.6 in ETSI GS NFV-IFA 013 [7]).

Step 2 (M)

NFVO sends to NM over the Os-Ma-nfvo reference point the information requested about the subject VNF instance.

Ends when

Ends when all steps identified above are completed or when an exception occurs.

Exceptions

One of the steps identified above fails.

Post-conditions

NM has the information about the subject VNF instance.

Traceability

REQ-NFV_LCM-CON-17, REQ-NFV_LCM_Os-Ma-nfvo-FUN-36

Goal

To request by NM the modification of non-application information and non-application configuration attribute(s) of a subject VNF instance. Such information about a subject VNF instance is managed by NFV-MANO (see clause 9.4.2 in ETSI GS NFV-IFA 008 [5]), for which certain attributes are writable/modifiable (see clauses 7.2.11 and 7.4.2 in ETSI GS NFV-IFA 008 [5]), e.g. VNF instance name, VNF external connectivity.

Actors and Roles

NM requests modifying the non-application information and non-application configuration attributes of the VNF instance which is part of the NS instance.

Telecom resources

NM.

NFVO.

VNFM.

Assumptions

N/A

Pre-conditions

The subject VNF instance is part of the NS instance.

Begins when

NM determines to modify certain non-application information and/or non-application configuration attribute(s) managed by NFV-MANO about the subject VNF instance that is part of an identified NS instance.

Step 1 (M)

NM sends a request to NFVO over the Os-Ma-nfvo reference point to modify the needed non-application attribute(s) about the subject VNF instance as part of the NS update operation (see clause 7.3.5 in ETSI GS NFV-IFA 013 [7]).

Step 2 (M)

NFVO sends an acknowledgement of the NS update request to the NM.

Step 3 (M)

NFVO sends to NM an NS Lifecycle Change notification about the start of the NS update execution (see clause 7.4.3 in ETSI GS NFV-IFA 013 [7]).

Step 4 (M)

NFVO executes the procedure to update the NS instance.

Step 5 (M)

NFVO sends to NM the NS Lifecycle Change notification to indicate the completion of the modification of requested attributes of the VNF instance as part of NS update (see clause 7.4.3 in ETSI GS NFV-IFA 013 [7]).

Ends when

Ends when all steps identified above are completed or when an exception occurs.

Exceptions

One of the steps identified above fails.

Post-conditions

The non-application information and/or non-application configuration attribute(s) managed by NFV-MANO of the subject VNF instance has been modified.

Traceability

REQ-NFV_LCM-CON-18, REQ-NFV_LCM-CON-19, REQ-NFV_LCM_Os-Ma-nfvo-FUN-37, REQ-NFV_LCM_Os-Ma-nfvo-FUN-38

Goal

VNF Package on-boarding

Actors and Roles

NM

Telecom resources

NM.NFVO

Assumptions

– The VNF Package is supplied by the NM

– On-boarding is triggered by the NM

Pre-conditions

NFVO is running.

NM is operational.

The NM possesses a VNF Package which is not on-boarded yet

Begins when

NM layer determines the need for on-boarding of the VNF Package

Step 1 (M)

NM sends a request to the NFVO on the VNF package on-boarding as specified in [6]

Step 2 (M)

NFVO processes the VNF Package and on-boarding proceeds

Step 3 (M)

NFVO acknowledges to the NM successful package on-boarding.

Exceptions

Post-conditions

The VNF Package is on-boarded.

Traceability

REQ-NFV_LCM_Os-Ma-nfvo-FUN-3

Goal

Enable a previously disabled VNF Package instance, allowing again its use for instantiation of new VNF with this package.

Actors and Roles

NM.

Telecom resources

NM, NFVO.

Assumptions

Enablement is triggered by the NM.

Pre-conditions

A VNF Package is in the "Disabled, Not in use" or "Disabled, In use" state.

Begins when

NM determines the need for enabling of the VNF Package.

Step 1 (M)

NM sends a request to the NFVO to enable the VNF package.

Step 2 (M)

NFVO processes the request and enables the VNF Package.

Step 3 (M)

NFVO acknowledges to the NM successful enablement of the VNF package.

Exceptions

Post-conditions

The VNF Package is enabled and available for use for instantiation of new VNF(s) with this package.

Traceability

Goal

VNF Package disabling.

Actors and Roles

NM.

Telecom resources

NM, NFVO.

Assumptions

Disabling is triggered by the NM.

Pre-conditions

A VNF Package is on-boarded, available for use for instantiation of new VNF instance(s) and is not marked as deletion pending

Begins when

NM layer determines the need for disabling of the VNF Package.

Step 1 (M)

NM sends a request to the NFVO to disable the VNF package

Step 2 (M)

NFVO processes the request and disables the VNF Package.

Step 3 (M)

NFVO acknowledges to the NM successful operation of disabling the VNF package.

Exceptions

Post-conditions

The VNF Package is on-boarded, disabled and cannot be used for instantiation of new VNF instance(s) with this package.

Traceability

Goal

VNF Package deleting.

Actors and Roles

NM.

Telecom resources

NM, NFVO.

Assumptions

Deletion is triggered by the NM.

Pre-conditions

The VNF Package is in "Disabled, Not in use" state defined in [6], clause D1.2

Begins when

NM layer determines the need for deletion of the VNF Package.

Step 1 (M)

NM sends a request to the NFVO to delete the VNF package as specified in [6], clause 7.7.5.

Step 2 (M)

NFVO processes the request and deletes the VNF Package.

Step 3 (M)

NFVO indicates to the NM the result of the operation.

Exceptions

One of the steps identified above fails.

Post-conditions

The VNF Package is deleted.

Traceability

Goal

Delete VNF Package

Actors and Roles

NM.

Telecom resources

NM, NFVO.

Assumptions

NM has an active subscription at the NFVO for notifications on deletion of the VNF Package.

Deletion of the VNF Package is triggered by the NM.

Pre-conditions

A VNF Package is in “Disabled, In use” state as defined in [6], Annex D.

Begins when

NM layer determines the need for deletion of the VNF Package.

Step 1 (M)

NM sends a request to the NFVO to delete the VNF package as specified in [6], clause 7.7.5.

Step 2 (M)

NFVO processes the request and moves the VNF Package to the “Deletion Pending” state.

Step 3 (M)

NFVO responds to the NM with notification of the result of the Delete VNF Package operation indicating that the VNF Package is now marked as delete pending.

Step 4 (M)

After the last VNF terminated, the NFVO deletes the VNF Package and sends VNF Package change notification that indicates deletion of the VNF Package.

Step 5 (M)

NM receives the notification on deletion.

Exceptions

Post-conditions

The VNF Package is deleted and no further operations with the package are possible.

Traceability

Goal

Abort VNF Package deletion.

Actors and Roles

NM.

Telecom resources

NM, NFVO.

Assumptions

Deletion of the VNF Package was earlier triggered by the NM when the VNF Package was in use.

Pre-conditions

A VNF Package is in "Deletion Pending" state defined in [6], Annex D.

Begins when

When the VNF Package is in use, the NM layer determines the need for abort of the deletion of the VNF Package e.g. because of expected further use of the package.

Step 1 (M)

NM sends a request to the NFVO to abort deletion of the VNF package as specified in [6], clause 7.7.12.

Step 2 (M)

NFVO processes the request and moves the VNF Package to the "Disabled, In use" state.

Step 3 (M)

NFVO sends a response message to the NM.

Exceptions

Post-conditions

The VNF Package deletion is aborted and the VNF Package is in the "Disabled, In use" state.

Traceability

Goal

Obtain properties of the VNF Package.

Actors and Roles

NM.

Telecom resources

NM, NFVO.

Assumptions

VNF Package querying is triggered by the NM.

Pre-conditions

A VNF Package is on-boarded

Begins when

NM layer determines the need for querying of the VNF Package.

Step 1 (M)

NM layer sends a request to the NFVO to query the VNF package as specified in [6], clause 7.7.6

Step 2 (M)

NFVO processes the request.

Step 3 (M)

NFVO acknowledges to the NM layer successful operation and returns the result of the operation.

Exceptions

Post-conditions

The NM layer possesses up-to-date information of the VNF Package,

Traceability

Goal

In case when the VNF Package has been on-boarded by another NM layer entity, fetch a whole VNF Package.

Actors and Roles

NM.

Telecom resources

NM, NFVO.

Assumptions

Fetch operation is triggered by the NM layer entity.

Pre-conditions

Begins when

NM layer entity determines the need for fetching a whole VNF Package.

Step 1 (M)

NM sends a fetch request to the NFVO to obtain the whole VNF Package using the VNFD identifier assigned by the VNF provider, as specified in [6], clause 7.7.9 or the identifier of information held by the NVFO about the VNF Package as specified in [6], clause 7.7.10.

Step 2 (M)

NFVO sends to the NM the fetch response that contains information requested by the NM.

Exceptions

Post-conditions

The NM possesses the requested information.

Traceability

Goal

Fetch selected artefacts of the VNF Package.

Actors and Roles

NM.

Telecom resources

NM, NFVO.

Assumptions

Fetch operation is triggered by the NM layer entity.

Pre-conditions

The VNF Package is on-boarded.

Begins when

NM layer entity determines the need for fetching selected artefacts contained in the VNF package.

Step 1 (M)

The NM queries the NFVO for the VNF Package Information

Clause 6.4.2.7: Use case for VNF Package querying

Step 2 (M)

The NFVO responds to the NM with the result of the query that contains the VNF Package information

Clause 6.4.2.7: Use case for VNF Package querying

Step 3 (M)

NM sends a fetch request to the NFVO to obtain the selected artefacts contained in the VNF package as specified in [6], clause 7.7.11. The artefacts are addressed using access information obtained in response to the Query On-boarded VNF Package Information operation.

Step 4 (M)

NFVO sends to the NM the fetch response that contains copy of the artefacts requested by the NM.

Exceptions

Post-conditions

The NM possesses the requested information.

Traceability

Goal

NM to receive notifications related to changes of VNF Packages sent by the NFVO.

Actors and Roles

NFVO.

Telecom resources

NM, NFVO.

Assumptions

NM has an active subscription at the NFVO for certain notifications related to changes of VNF Packages such as VNF Package on-boarding and VNF Package Change notifications. The subscription includes a filter for selecting the VNF Package(s) and related change notifications.

Pre-conditions

Begins when

There is a change in the VNF Package that triggers a notification matching the filter in the subscription, see [6], clause 7.7.8.

Step 1 (M)

NFVO sends the notification on the change, to the NM.

Step 2 (M)

The NM receives the notification.

Exceptions

Post-conditions

The NM possesses information carried by the received notification.

Traceability

Goal

To subscribe with a filter for the notifications related to changes of VNF Packages sent by the NFVO.

Actors and Roles

NM.

Telecom resources

NM, NFVO.

Assumptions

Subscription is triggered by the NM layer.

Pre-conditions

Begins when

NM layer determines the need to subscribe with a filter for the notifications related to changes of VNF Packages sent by the NFVO.

Step 1 (M)

NM sends to the NFVO request for subscription to certain notifications related to changes of certain VNF Package(s) as specified in [6], clause 7.7.7.

Step 2 (M)

NFVO responds to the NM with the result of the operation indicating if the subscription has been successful or not, and, in the case of success, identification of the subscription realized.

Exceptions

Post-conditions

In the case of successful subscription, the NM is registered to receive notifications related to changes of VNF Packages sent by the NFVO and matching the filter

Traceability

Goal

To instantiate a NS with necessary input parameterization through operation request from NM on the Os-Ma-nfvo reference point in order to honour specific NS usage, e.g. geographical location, capacity, etc.

Actors and Roles

NM requests the NS instantiation

Telecom resources

NM.

NFVO

Assumptions

NS may contain VNFs, PNFs and nested NSs.

Pre-conditions

The VNF Package(s) of the VNF(s) to be instantiated as part of the NS are on-boarded.

The NSD for the NS instantiation is on-boarded.

A NS instance identifier and an associated instance of a NsInfo information element have been created.

PNFDs for PNF constituents of NS have been on-boarded.

Clause 6.4.2.1: Use case for VNF Package on-boarding

Clause 6.4.4.1: Use case for Network Service Descriptor (NSD) On-boarding.

Clause 6.4.3.12: Create NS Identifier

Begins when

NM determines (e.g., by operator request) that a new NS needs to be instantiated honouring certain usage and input requirements.

Step 1 (M)

NM sends to NFVO a request to instantiate the new NS indicating in the request information about the target NSD and additional parameterization for the specific NS to instantiate (see clause 7.3.3 in ETSI GS NFV-IFA013 [6]).

In case the NS instantiation request required VNF(s) instantiation or configuration, the VNFs’ parameters/values, including those captured in vendor specific name value pairs, carried by such request are only related to VNF virtualization aspects and are not VNF application specific.

Step 2 (M)

NFVO sends to NM a notification about the start of the NS instantiation (see clause 7.4.3 in ETSI GS NFV-IFA 013 [6]).

Step 3 (M)

NFVO executes with rest of NFV-MANO system the instantiation of the NS.

Step 4 (M)

NFVO sends to NM a notification about the results of the NS instantiation execution (see clause 7.4.3 in ETSI GS NFV-IFA 013 [6]).

Ends when

All the steps identified above are successfully completed.

Exceptions

One of the steps identified above fails.

Post-conditions

A new NS is instantiated.

Traceability

REQ-NFV_LCM_Os-Ma-nfvo-FUN-1

Goal

Interconnect specific external CPs of specific VNF instances by adding them to a new NS.

Actors and Roles

NM

Telecom resources

NFVO

Assumptions

NM is subscribed for NS LCM notifications

Pre-conditions

The VNF instances being interconnected already exist (have been instantiated) and do not belong to the same NS instance.

A NS instance identifier and an associated instance of a NsInfo information element have been created.

Clause 6.4.3.12: Create NS Identifier

Begins when

NM determines (e.g. by operator’s request) the need for interconnecting the VNF instances that do not belong to the same NS.

Step 1 (M)

NM sends a request to the NFVO to instantiate a new NS instance by adding existing VNF instances to it and creating new instances of VL connecting specific external CPs of specific VNF instances belonging to this NS instance.

Step 2 (M)

NFVO returns to the NM lifecycleOperationOccurrenceId and processes the request.

Step 3 (M)

NFVO sends to NM Lifecycle Change Notification indicating start of the operation.

Step 4 (M)

NFVO sends to NM Lifecycle Change Notifications indicating progress of the operation.

Step 5 (M)

NFVO sends to NM Lifecycle Change Notification indicating result of the operation.

Ends when

All the steps identified above are successfully completed.

Exceptions

One of the steps identified above fails.

Post-conditions

The new NS instance has been created with identified VNF instances interconnected according to the operator’s needs

Traceability

REQ-NFV_LCM_Os-Ma-nfvo-FUN-26

Goal

Interconnect specific SAPs of specific NS instances by adding them to a new NS.

Actors and Roles

NM

Telecom resources

NFVO

Assumptions

NM is subscribed for NS LCM notifications

Pre-conditions

The NS instances with SAPs being interconnected already exist (have been instantiated) and do not belong to the same NS instance.

A NS instance identifier and an associated instance of a NsInfo information element have been created.

Clause 6.4.3.12: Create NS Identifier

Begins when

NM determines (e.g. by operator’s request) the need for interconnecting the NS instances that do not belong to the same NS.

Step 1 (M)

NM sends a request to the NFVO to instantiate a new NS instance by adding existing NS instances to it and creating new instances of VL connecting specific SAPs of specific nested NS instances belonging to this NS instance.

Step 2 (M)

NFVO returns to the NM lifecycleOperationOccurrenceId and processes the request.

Step 3 (M)

NFVO sends to NM Lifecycle Change Notification indicating start of the operation.

Step 4 (M)

NFVO sends to NM Lifecycle Change Notifications indicating progress of the operation.

Step 5 (M)

NFVO sends to NM Lifecycle Change Notification indicating result of the operation.

Ends when

All the steps identified above are successfully completed.

Exceptions

One of the steps identified above fails.

Post-conditions

The new NS instance has been created with identified nested NS instances interconnected according to the operator’s needs

Traceability

REQ-NFV_LCM_Os-Ma-nfvo-FUN-27

Goal

Enable NM to terminate a NS instance

Actors and Roles

NM.

Telecom resources

NFVO.

Assumptions

NS termination is triggered by the NM.

Pre-conditions

NS instance(s) exist..

NFVO is running.

NM is operational

Begins when

NM determines to terminate a NS instance.

Step 1 (M)

NM sends a request to the NFVO to terminate a NS instance.

Step 2 (M)

NFVO terminates the NS instance and all those VNF instances associated only with the NS instance

Step 3 (M)

NFVO sends to the NM the result of the operation.

Exceptions

Post-conditions

In case of success, the NS instance has been terminated and all those VNF instances associated only with this NS instance have been terminated.

Traceability

REQ-NFV_LCM_Os-Ma-nfvo-FUN-6

Goal

Enable NM to obtain information on one or more NS instance(s)

Actors and Roles

NM.

Telecom resources

NFVO.

Assumptions

NS querying is triggered by the NM.

Pre-conditions

One or more NS instance(s) exist.

NFVO is running.

NM is operational

Begins when

NM determines to query one or more NS instance(s).

Step 1 (M)

NM sends a request to the NFVO to query one or more NS instance(s) with queryFilter specifying identifiers and attributeSelector providing a list of attribute names of NS.

Step 2 (M)

NFVO processes the request.

Step 3 (M)

NFVO send to the NM the result of the operation.

Exceptions

Post-conditions

The NM possesses up-to-date information of the NS instance(s)

Traceability

REQ-NFV_LCM_Os-Ma-nfvo-FUN-7

Goal

To scale a VNF instance by scaling the NS instance through operation request to NFVO by NM, and notify about the execution of the NS instance scaling through reference point Os-Ma-nfvo.

Actors and Roles

NM detects whether a scaling execution is needed and requests the NFVO to execute the NS scaling.

Telecom resources

NM, NFVO

Assumptions

Pre-conditions

The subject NS instance is not being scaled at the moment.

Begins when

NM detected the need to scale and have determined the scaling target VNF instance(s) and action (i.e. addition, expansion, contraction or removal).

Step 1 (M)

NM sends the NFVO a request to scale a NS with an indication of the target VNF instance to scale, type of scaling and value of scaling as necessary.

Step 2 (M)

The NFVO sends to NM a notification about the start of the NS scaling execution.

Step 3 (M)

The NFVO executes the procedure to scale the NS instance.

Step 4 (M)

NFVO sends to NM a notification about the end of the NS scaling execution.

Ends when

All the steps identified above are successfully completed.

Exceptions

Post-conditions

The NS instance has been scaled.

Traceability

REQ-NFV_LCM_Os-Ma-nfvo-FUN-8, REQ-NFV_LCM_Os-Ma-nfvo-FUN-11

Goal

The network operator through 3GPP management system can decide the time when and has the capacity to update the NS instance to correspond to a different NSD version when such update synchronization has not automatically been performed by the NFVO.

Actors and Roles

NM.

Telecom resources

NFVO

Assumptions

The NM is subscribed to NS lifecycle change notifications from the NFVO.

Pre-conditions

The NS to update is instantiated.

The new NSD version is available to the NM.

Clause 6.4.3.1.1: Use case of NS instantiation

Begins when

NM determines to update the existing NS instance, e.g., due to changes in its VNF instances.

Step 1 (M)

The NSD instance is updated with the new NSD version (see clause 7.2.5 in ETSI GS NFV-IFA 013 [6]).

Clause 6.4.4.7: Use case for updating NSD instance

Step 2 (M)

The NS instance is associated to the newly on-boarded NSD version.

Note: The automatic update synchronization by NFVO is set to false (see clause 8.3.4.19 in ETSI GS NFV-IFA 013 [6]).

Clause 6.4.3.6: Use case for associating a new NSD version to an NS instance as part of NS update

Step 3 (M)

NM sends a request to NFVO to update the NS instance with the necessary update information, e.g., addition, removal or modification of existing VNF instances part of the NS instance (see clause 7.3.5 in ETSI GS NFV-IFA 013 [6]).

Step 4 (M)

NFVO acknowledges the NS instance update request providing information to identify the lifecycle operation occurrence (see clause 7.3.5 in ETSI GS NFV‑IFA 013 [6]).

Step 5 (M)

NFVO sends to NM a notification indicating the start of the NS update lifecycle changes. The notification identifies the NS instance affected for the lifecycle change, the lifecycle operation occurrence and the type of lifecycle operation (see clause 8.3.2.2 in ETSI GS NFV-IFA 013 [6]).

Step 6 (M)

NFVO sends to NM a notification indicating the end result of the NS update lifecycle changes. The notification identifies the NS instance affected for the lifecycle change, the lifecycle operation occurrence, the type of lifecycle operation and information about the entities part of the NS instance affected by the lifecycle change (see clause 8.3.2.2 in ETSI GS NFV-IFA 013 [6]).

Ends when

Ends when all steps identified above are completed or when an exception occurs.

Exceptions

One of the steps identified above fails.

Post-conditions

The NS instance has been updated to correspond to the different NSD version.

Traceability

REQ-NFV_LCM_Os-Ma-nfvo-FUN-9, REQ-NFV_LCM_Os-Ma-nfvo-FUN-17, REQ-NFV_LCM_Os-Ma-nfvo-FUN-20

Goal

The network operator through 3GPP management system has the capacity to associate an existing NS instance to a different NSD version as part of NS update, so that the NS instance lifecycle management and NS instance updates can be performed according to the different NSD version.

Actors and Roles

NM.

Telecom resources

NFVO

Assumptions

N/A

Pre-conditions

The different NSD version to associate the NS instance to is already on-boarded.

Clause 6.4.4.7: Use case for updating NSD instance.

Begins when

NM determines to associate the different NSD version to the existing NS instance.

Step 1 (M)

NM sends a request to the NFVO as part of NS update to associate the different NSD version to the NS instance by providing the identifier of the on-boarded different version and indication of whether the NS instance will be automatically synchronized to the new NSD by the NFVO (see clause 8.3.4.15 in ETSI GS NFV-IFA 013 [6]).

Note: The present use case does not elaborate in the additional steps that can occur when automatic synchronization is performed.

Step 2 (M)

NFVO acknowledges to the NM the successful NS update operation (see clause 7.3.5 in ETSI GS NFV-IFA 013 [6]).

Ends when

Ends when all steps identified above are completed or when an exception occurs.

Exceptions

One of the steps identified above fails.

Post-conditions

The NS instance is associated to the different NSD version.

Traceability

REQ- NFV_LCM_Os-Ma-nfvo-FUN-22

Goal

Interconnect specific external CPs of specific VNF instances.

Actors and Roles

NM

Telecom resources

NFVO

Assumptions

NM is subscribed for NS LCM notifications

Pre-conditions

The VNF instances being interconnected already exist (have been instantiated) and belong to the same NS instance.

Begins when

NM determines (e.g. by operator’s request) the need for interconnecting the VNF instances.

Step 1 (M)

NM sends a request to the NFVO to update the NS instance by creating a new instance of VL with specific external CPs of specific VNF instances belonging to this NS instance.

Step 2 (M)

NFVO returns to the NM lifecycleOperationOccurrenceId and processes the request.

Step 3 (M)

NFVO sends to NM Lifecycle Change Notification indicating start of the operation.

Step 4 (M)

NFVO sends to NM Lifecycle Change Notifications indicating progress of the operation.

Step 5 (M)

NFVO sends to NM Lifecycle Change Notification indicating result of the operation.

Ends when

All the steps identified above are successfully completed.

Exceptions

One of the steps identified above fails.

Post-conditions

The identified VNF instances are interconnected according to the operator’s needs

Traceability

REQ-NFV_LCM_Os-Ma-nfvo-FUN-23

Goal

Add an existing VNF instances to the existing NS instance.

Actors and Roles

NM

Telecom resources

NFVO

Assumptions

NM is subscribed for NS LCM notifications

Pre-conditions

The VNF instance being added already exist (has been instantiated) and does not belong to this NS instance.

The VNFD (VNF type) of the VNF instance being added is already known to the NSD of the NS where the VNF instance is being added to.

The DF of the VNF instance being added matches one of the VNF profiles in the NSD of the NS where the VNF instance is being added to.

Begins when

NM determines (e.g. by operator’s request) the need for adding an existing VNF instance to an existing NS instance.

Step 1 (M)

NM sends a request to the NFVO to update the NS instance by adding the existing instance of VNF and if needed, with VNF profile to be used for this VNF instance (see [6] clauses 7.3.5 and 8.3.4.3).

Step 2 (M)

NFVO returns to the NM lifecycleOperationOccurrenceId and processes the request.

Step 3 (M)

NFVO sends to NM Lifecycle Change Notification indicating start of the operation.

Step 4 (M)

NFVO sends to NM Lifecycle Change Notifications indicating progress of the operation.

Step 5 (M)

NFVO sends to NM Lifecycle Change Notification indicating result of the operation.

Ends when

All the steps identified above are successfully completed.

Exceptions

One of the steps identified above fails.

Post-conditions

The identified VNF instances have been added to the NS instance according to the operator’s needs

Traceability

REQ-NFV_LCM_Os-Ma-nfvo-FUN-24

Goal

Add new Service Access Point exposing specific external CP of a specific VNF instance.

Actors and Roles

NM

Telecom resources

NFVO

Assumptions

NM is subscribed for NS LCM notifications

Pre-conditions

The VNF instance who’s external CP is being exposed as SAP already exists (has been instantiated) and belongs to the same NS instance where the new SAP is being added.

Begins when

NM determines (e.g. by operator’s request) the need for exposing a specific VNF external CP as a new SAP.

Step 1 (M)

NM sends a request to the NFVO to update the NS instance by creating a new instance of SAP exposing specific external CP of a specific VNF instance belonging to this NS instance.

Step 2 (M)

NFVO returns to the NM lifecycleOperationOccurrenceId and processes the request.

Step 3 (M)

NFVO sends to NM Lifecycle Change Notification indicating start of the operation.

Step 4 (M)

NFVO sends to NM Lifecycle Change Notifications indicating progress of the operation.

Step 5 (M)

NFVO sends to NM Lifecycle Change Notification indicating result of the operation.

Ends when

All the steps identified above are successfully completed.

Exceptions

One of the steps identified above fails.

Post-conditions

The identified external CP of the identified VNF instance is exposed as a new SAP according to the operator’s needs

Traceability

REQ-NFV_LCM_Os-Ma-nfvo-FUN-25

Goal

Enable NM to obtain the lifecycle change notifications on one or more NS instance(s).

Actors and Roles

NM receives NS lifecycle change notifications.

Telecom resources

NFVO

Assumptions

Pre-conditions

NFVO is running.

NM subscribed for the notifications related to NS lifecycle changes.

Begins when

NFVO monitors the lifecycles of the identified NS instance and the NS lifecycle is changed

Step 1 (M)

NFVO creates NS lifecycle change notification including information: identity of the NS instance, the type of lifecycle change including the beginning or the end of the procedure affecting the lifecycle changes.

Step 2 (M)

NFVO sends to NM the NS lifecycle change notifications.

Ends when

NM unsubscribes to NS lifecycle change notification.

Exceptions

Post-conditions

NM has information about the lifecycle changes of the one or more managed NS instance(s).

Traceability

REQ-NFV_LCM_Os-Ma-nfvo-FUN-20

Goal

To subscribe by NM the lifecycle changes on one or more NS instance(s).

Actors and Roles

NM subscribes NS instance lifecycle change notifications.

Telecom resources

NFVO

Assumptions

Pre-conditions

NFVO is running.

NM is operational

Begins when

NM determines to subscribe lifecycle changes on one or more NS instance(s).

Step 1 (M)

NM requests a subscription to NFVO to receive the lifecycle change notifications regarding one or more NS instance(s).

Step 2 (M)

NFVO creates a subscription and acknowledges the creation of the subscription to NM.

Ends when

All the steps identified above are successfully completed.

Exceptions

Post-conditions

NM is subscribed to lifecycle changes of the one or more managed NS instance(s).

Traceability

REQ-NFV_LCM_Os-Ma-nfvo-FUN-19

Goal

To create a NS instance identifier and associated instance of a NsInfo information element to enable further NS instantiation.

Actors and Roles

NM requests creation of the NS Identifier

Telecom resources

NM.

NFVO

Assumptions

Pre-conditions

The NSD is on-boarded.

Begins when

NM determines (e.g., by operator request) that a new NS instance identifier, and an associated instance of a NsInfo information element are needed to enable NS instantiation based on the NSD.

Step 1 (M)

NM sends to NFVO a Create NS Identifier request with reference to the NSD and additional information like NS name (see clause 7.3.2 in ETSI GS NFV-IFA013 [6]).

Step 2 (M)

NFVO creates the NS Identifier and the associated instance of NsInfo information element and sends the response to the NM

Ends when

All the steps identified above are successfully completed.

Exceptions

One of the steps identified above fails.

Post-conditions

A new NS instance identifier and an associated instance of a NsInfo information element are created and can be used in further NS instantiation.

Traceability

REQ-NFV_LCM_Os-Ma-nfvo-FUN-29

Goal

To delete the NS instance identifier and the associated instance of a NsInfo information element after the NS instance termination.

Actors and Roles

NM requests deletion of the NS instance identifier.

Telecom resources

NM, NFVO

Assumptions

Pre-conditions

NS instance is terminated.

Begins when

NM determines (e.g., by operator request) that the NS instance identifier and the associated instance of NsInfo information element of the terminated NS instance are needed to be deleted.

Step 1 (M)

NM sends to NFVO a Delete NS Identifier request (see clause 7.3.8 in ETSI GS NFV-IFA013 [6]).

Step 2 (M)

NFVO deletes the NS Identifier and sends the response to the NM.

Ends when

All the steps identified above are successfully completed.

Exceptions

One of the steps identified above fails.

Post-conditions

The NS instance identifier are deleted.

Traceability

REQ-NFV_LCM_Os-Ma-nfvo-FUN-35

Goal

Add an existing PNF to the existing NS instance.

Actors and Roles

NM

Telecom resources

NFVO

Assumptions

NM is subscribed to receive the NS LCM notifications.

Pre-conditions

The PNF being added already exist and does not belong to this NS instance.

The PNFD of the PNF being added is already known to the NSD of the NS where the PNF is being added to.

Begins when

NM determines (e.g. by operator’s request) the need for adding an existing PNF to an existing NS instance.

Step 1 (M)

NM sends a request to the NFVO to update the NS instance by adding the existing PNF (see [6] clauses 7.3.5).

Step 2 (M)

NFVO returns to the NM lifecycleOperationOccurrenceId and processes the request

Step 3 (M)

NFVO sends to NM Lifecycle Change Notification indicating start of the operation.

Step 4 (M)

NFVO sends to NM Lifecycle Change Notifications indicating progress of the operation.

Step 5 (M)

NFVO sends to NM Lifecycle Change Notification indicating result of the operation.

Ends when

All the steps identified above are successfully completed.

Exceptions

One of the steps identified above fails.

Post-conditions

The identified PNF has been added to the NS instance according to the operator’s needs.

Traceability

REQ-NFV_LCM_Os-Ma-nfvo-FUN-x

Goal

Add an existing VNF instance to a NS with connectivity to other VNF instance or PNF.

Actors and Roles

NM

Telecom resources

NFVO

Assumptions

NM is subscribed to receive the NS LCM notifications.

Pre-conditions

A VNF instance has been instantiated.

Begins when

NM determines (e.g. by operator’s request) to add an existing VNF instance to a NS with connectivity to other VNF instance or PNF.

Step 1 (M)

NM sends a request to the NFVO to add an existing VNF instance to a NS (see clause 7.3.5 in [6]) with VNF instance identifier and connectivity information for the external CP instances.

Step 2 (M)

NFVO returns to the NM lifecycleOperationOccurrenceId and processes the request

Step 3 (M)

NFVO sends to NM Lifecycle Change Notification indicating start of the operation.

Step 4 (M)

NFVO sends to NM Lifecycle Change Notifications indicating progress of the operation.

Step 5 (M)

NFVO sends to NM Lifecycle Change Notification indicating result of the operation.

Ends when

All the steps identified above are successfully completed.

Exceptions

One of the steps identified above fails.

Post-conditions

The existing VNF instance has been added with connectivity to other VND instance or PNF in the NS.

Traceability

REQ-NFV_LCM_Os-Ma-nfvo-FUN-x

Goal

Add external connectivity to a PNF or VNF instance.

Actors and Roles

NM

Telecom resources

NFVO

Assumptions

NM is subscribed to receive the NS LCM notifications.

Pre-conditions

A PNF or VNF instance has been added or instantiated in an NS instance without the external connectivity, or a new external connectivity is needed due to PNF or VNF upgrade.

Begins when

NM determines (e.g. by operator’s request) that it is necessary to add the external connectivity to an existing PNF or VNF instance.

Step 1 (M)

NM sends a request to the NFVO to update the NS instance (see clause 7.3.5 in [6]) to add the external connectivity to an existing PNF or VNF instance.

Step 2 (M)

NFVO returns to the NM lifecycleOperationOccurrenceId and processes the request

Step 3 (M)

NFVO sends to NM Lifecycle Change Notification indicating start of the operation.

Step 4 (M)

NFVO sends to NM Lifecycle Change Notifications indicating progress of the operation.

Step 5 (M)

NFVO sends to NM Lifecycle Change Notification indicating result of the operation.

Ends when

All the steps identified above are successfully completed.

Exceptions

One of the steps identified above fails.

Post-conditions

The external connectivity has been added to the PNF or VNF instance according to the operator’s needs.

Traceability

REQ-NFV_LCM_Os-Ma-nfvo-FUN-x

Goal

Add a virtual link to a NS instance.

Actors and Roles

NM

Telecom resources

NFVO

Assumptions

NM is subscribed to receive the NS LCM notifications.

Pre-conditions

The NS where the virtual link is to be added has been instantiated.

The virtual link descriptor and virtual link profile for the virtual link to be added are available in the NSD either on-boarded previously or updated.

Begins when

NM determines (e.g. by operator’s request) that it is necessary to add a virtual link to an existing NS instance.

Step 1 (M)

NM sends a request to the NFVO to update the NS instance (see clause 7.3.5 in [6]) to add a virtual link.

Step 2 (M)

NFVO returns to the NM lifecycleOperationOccurrenceId and processes the request

Step 3 (M)

NFVO sends to NM Lifecycle Change Notification indicating start of the operation.

Step 4 (M)

NFVO sends to NM Lifecycle Change Notifications indicating progress of the operation.

Step 5 (M)

NFVO sends to NM Lifecycle Change Notification indicating result of the operation.

Ends when

All the steps identified above are successfully completed.

Exceptions

One of the steps identified above fails.

Post-conditions

A virtual link has been added to the NS instance according to the operator’s needs.

Traceability

REQ-NFV_LCM_Os-Ma-nfvo-FUN-x

Goal

Change external connectivity to a PNF or VNF instance.

Actors and Roles

NM

Telecom resources

NFVO

Assumptions

NM is subscribed to receive the NS LCM notifications.

Pre-conditions

A PNF or VNF instance has been added or instantiated in an NS instance.

Begins when

NM determines (e.g. by operator’s request) that it is necessary to change the external connectivity to an existing PNF or VNF instance.

Step 1 (M)

NM sends a request to the NFVO to update the NS instance (see clause 7.3.5 in [6]) to change the external connectivity to an existing PNF or VNF instance.

Step 2 (M)

NFVO returns to the NM lifecycleOperationOccurrenceId and processes the request

Step 3 (M)

NFVO sends to NM Lifecycle Change Notification indicating start of the operation.

Step 4 (M)

NFVO sends to NM Lifecycle Change Notifications indicating progress of the operation.

Step 5 (M)

NFVO sends to NM Lifecycle Change Notification indicating result of the operation.

Ends when

All the steps identified above are successfully completed.

Exceptions

One of the steps identified above fails.

Post-conditions

The external connectivity has been changed to the PNF or VNF instance according to the operator’s needs.

Traceability

REQ-NFV_LCM_Os-Ma-nfvo-FUN-x

Goal

Add VNF forwarding graph to a NS instance.

Actors and Roles

NM

Telecom resources

NFVO

Assumptions

NM is subscribed to receive the NS LCM notifications.

Pre-conditions

An NS instance, containing the VNF instances and all necessary components (e.g. VLs, CPs, SAPs, …) to form a VNFFG, has been instantiated,

VNFFGD for the VNFFG to be added already exists.

Begins when

NM determines (e.g. by operator’s request) that it is necessary to add a VNFFG to a NS instance.

Step 1 (M)

NM sends a request to the NFVO to update the NS instance (see clause 7.3.5 in [6]) by adding a VNFFG to a NS instance.

Step 2 (M)

NFVO returns to the NM lifecycleOperationOccurrenceId and processes the request

Step 3 (M)

NFVO sends to NM Lifecycle Change Notification indicating start of the operation.

Step 4 (M)

NFVO sends to NM Lifecycle Change Notifications indicating progress of the operation.

Step 5 (M)

NFVO sends to NM Lifecycle Change Notification indicating result of the operation.

Ends when

All the steps identified above are successfully completed.

Exceptions

One of the steps identified above fails.

Post-conditions

The VNFFG has been added to the NS instance according to the operator’s needs.

Traceability

REQ-NFV_LCM_Os-Ma-nfvo-FUN-x

Goal

Update VNF forwarding graph in a NS instance.

Actors and Roles

NM

Telecom resources

NFVO

Assumptions

NM is subscribed to receive the NS LCM notifications.

Pre-conditions

An NS instance with VNFFG already exists,

VNFFGD for the VNFFG to be updated already exists.

Begins when

NM determines (e.g. by operator’s request) that it is necessary to update the VNFFG in a NS instance.

Step 1 (M)

NM sends a request to the NFVO to update the VNFFG (e.g. addition, deletion, and modification of NFP) in a NS instance via the NS update operation (see clause 7.3.5 in [6]).

Step 2 (M)

NFVO returns to the NM lifecycleOperationOccurrenceId, and the idenfifier of new NFP if the update is to add a NFP to the existing VNFFG, and processes the request.

Step 3 (M)

NFVO sends to NM Lifecycle Change Notification indicating start of the operation.

Step 4 (M)

NFVO sends to NM Lifecycle Change Notifications indicating progress of the operation.

Step 5 (M)

NFVO sends to NM Lifecycle Change Notification indicating result of the operation.

Ends when

All the steps identified above are successfully completed.

Exceptions

One of the steps identified above fails.

Post-conditions

The VNFFG has been updated to the NS instance according to the operator’s needs.

Traceability

REQ-NFV_LCM_Os-Ma-nfvo-FUN-x

Goal

NSD On-boarding

Actors and Roles

NM

Telecom resources

NM, NFVO

Assumptions

NSD on-boarding is triggered by the NM layer

Pre-conditions

NFVO is running.

NM layer is operational.

The NM layer possesses the NSD

Begins when

NM layer determines the need for on-boarding of the NSD

Step 1 (M)

NM layer sends a request to the NFVO on the NSD on-boarding as specified in [6], clause 7.2.2.

Step 2 (M)

NFVO processes the request and on-boarding proceeds.

Step 3 (M)

NFVO acknowledges to the NM layer successful NSD on-boarding.

Exceptions

Post-conditions

The NSD is on-boarded.

Traceability

REQ-NFV_LCM_Os-Ma-nfvo-FUN-14, REQ-NFV_LCM_Os-Ma-nfvo-FUN-15

Goal

NS Descriptor instance enabling

Actors and Roles

NM

Telecom resources

NM, NFVO

Assumptions

NS Descriptor instance enabling is triggered by the NM layer

Pre-conditions

NFVO is running.

NM layer is operational.

There is a NS Descriptor instance in one of the following states: “Disabled, In use” or “Disabled, Not in use” defined in [6], clause D2.2

Begins when

NM layer determines the need for enabling the NS Descriptor instance

Step 1 (M)

NM layer sends a request to the NFVO on enabling the NS Descriptor instance as specified in [6], clause 7.2.3.

Step 2 (M)

NFVO processes the request and enables the NS Descriptor instance

Step 3 (M)

NFVO acknowledges to the NM layer successful enablement of the NS Descriptor instance.

Exceptions

Post-conditions

The NS Descriptor instance is enabled.

Traceability

Goal

NS Descriptor instance disabling

Actors and Roles

NM

Telecom resources

NM, NFVO

Assumptions

NS Descriptor instance disabling is triggered by the NM layer

Pre-conditions

NFVO is running.

NM layer is operational.

There is a NS Descriptor instance in one of the states “Enabled, In use” or “Enabled, Not in use” defined in [6], clause D2.2

Begins when

NM layer determines the need for disabling the NS Descriptor instance

Step 1 (M)

NM layer sends a request to the NFVO on disabling the NS Descriptor instance as specified in [6], clause 7.2.4.

Step 2 (M)

NFVO processes the request and disables the NS Descriptor instance

Step 3 (M)

NFVO acknowledges to the NM layer successful disabling of the NS Descriptor instance

Exceptions

Post-conditions

The NS Descriptor instance is disabled

Traceability

Goal

Enable NM to obtain information on one or more NS Descriptors (NSDs)

Actors and Roles

NM.

Telecom resources

NFVO.

Assumptions

NSD querying is triggered by the NM.

Pre-conditions

One or more NSDs are on-boarded.

NFVO is running.

NM is operational

Begins when

NM determines to query one or more NSD(s).

Step 1 (M)

NM sends a request to the NFVO to query one or more NSD(s), with the filter defining the NSDs on which the query applies, and the attribute selector providing a list of attribute names of the NSD(s), according to [6], clause 7.2.7

Step 2 (M)

NFVO processes the request.

Step 3 (M)

NFVO sends to the NM the result of the operation.

Exceptions

Post-conditions

The NM possesses the requested information on the NSD(s)

Traceability

Goal

Delete one or more NS Descriptor(s) that are in use.

Actors and Roles

NM

Telecom resources

NM, NFVO

Assumptions

Deletion of the NS Descriptor (NSD) is triggered by the NM layer

Pre-conditions

NFVO is running.

NM layer is operational.

There are one or several NSD(s) in the state “Disabled, In use” defined in [6], clause D2.2

Begins when

NM layer determines the need for deletion of the NSDs

Step 1 (M)

NM layer sends a request to the NFVO on deletion of the NSDs as specified in [6], clause 7.2.6.

Step 2 (M)

NFVO processes the request and transfers the NSDs into the Deletion Pending state.

Step 3 (M)

NFVO responds to the NM layer with the result of the operation including indication that the NSDs are marked as delete pending.

Step 4 (M)

After the last NS associated with certain NSD is terminated, the NFVO deletes the NSD.

Exceptions

Post-conditions

The NSDs are deleted

Traceability

Goal

Delete one or more NS Descriptor(s), a single version of an NSD or all versions.

Actors and Roles

NM.

Telecom resources

NM, NFVO

Assumptions

Deletion of the NS Descriptor (NSD) is triggered by the NM layer

Pre-conditions

NFVO is running.

NM layer is operational.

There is a group of NSD(s) to be deleted that are all in the state “Disabled, Not in use” as defined in [6], clause D2.2

Begins when

NM layer determines the need for deletion of the group of the NSD(s).

Step 1 (M)

NM layer sends a request to the NFVO on deletion of the NSD(s) as specified in [6], clause 7.2.6.

Step 2 (M)

NFVO processes the request and deletes the NSD(s).

Step 3 (M)

NFVO responds to the NM layer with the result of the operation.

Exceptions

Post-conditions

The NSD(s) are deleted

Traceability

Goal

The network operator through 3GPP management system has the capacity to update an on-boarded NSD instance on the NFVO. An NSD update creates a new NSD version and the previous on-boarded versions of the NSD are not modified (see clause 7.2.5.1 in ETSI GS NFV-IFA 013 [6]).

Actors and Roles

NM.

Telecom resources

NFVO

Assumptions

N/A

Pre-conditions

The NSD to update has been on-boarded.

Clause 6.4.4.1: Use case for NS Descriptor (NSD) On-boarding

Begins when

NM determines to update the existing on-boarded NSD.

Step 1 (M)

NM sends a request to the NFVO to update the NSD by providing the identifier of the existing on-boarded version of the NSD to update, the new NSD version, and optionally additional user defined data (see clause 7.2.5 in ETSI
GS NFV-IFA 013 [6]).

Step 2 (M)

NFVO acknowledges to the NM the successful NSD update providing the identifier of the newly on-boarded NSD version (see clause 7.2.5 in ETSI GS NFV-IFA 013 [6]).

Ends when

Ends when all steps identified above are completed or when an exception occurs.

Exceptions

One of the steps identified above fails.

The NSD to update is in deletion pending state.

The new NSD version does not correspond to be a different version of the existing on-boarded NSD to update.

Post-conditions

The newly NSD version is on-boarded.

Traceability

REQ- NFV_LCM_Os-Ma-nfvo-FUN-21

Goal

Update the user defined data in the NS Descriptor

Actors and Roles

NM

Telecom resources

NM, NFVO

Assumptions

NS Descriptor update is triggered by the NM layer

Pre-conditions

NFVO is running.

NM layer is operational.

There is an onboarded NS Descriptor (NSD).

Begins when

NM layer determines the need for update of the user defined data in the NSD.

Step 1 (M)

NM layer sends a request to the NFVO on update of the user defined data in the NSD as specified in [6], clause 7.2.5.

Step 2 (M)

NFVO processes the request and updates the NSD resulting in update of the user defined data of the NSD.

Step 3 (M)

NFVO sends response message to the NM layer, indicating successful NSD update.

Exceptions

Post-conditions

The NSD is updated.

Traceability

Goal

Enable the NM to subscribe with a filter for the notifications related to changes of one or several NSDs, sent by the NFVO

Actors and Roles

NM.

Telecom resources

NM, NFVO.

Assumptions

Pre-conditions

NFVO is operational.

NM is operational.

Begins when

NM determines a need in subscription to notifications on changes of certain NSD(s).

Step 1 (M)

NM sends a request to the NFVO, according to [6], clause 7.2.12.

The request contains the input filter for selecting the NSD(s) and the related change notifications to subscribe to. This filter can contain information about specific types of changes to subscribe to, or attributes of the NsdInfo.

Step 2 (M)

NFVO processes the request and registers the NM to receive notifications about changes of NSD(s).

Step 3 (M)

NFVO sends to the NM the result of the operation.

Exceptions

Post-conditions

The NM is registered to receive notifications about changes of the NSD(s).

Traceability

REQ- NFV_LCM_Os-Ma-nfvo-FUN-33

Goal

Enable the NM to receive notifications related to NSD management changes, sent by the NFVO.

Actors and Roles

NM.

Telecom resources

NM, NFVO.

Assumptions

Pre-conditions

NFVO is operational.

NM is operational.

The NM is subscribed to notifications related to management changes of NSD instances matching the filter defined at the time of the subscription.

Begins when

NFVO monitors the NSD instances matching the filter and detects the management change in one of the NSD instances.

Step 1 (M)

NFVO sends to the NM the notification according to [6], clause 7.2.13.

Exceptions

Post-conditions

The NM received the notification.

Traceability

REQ- NFV_LCM_Os-Ma-nfvo-FUN-34

Goal

Enable NM to perform On-board PNFD operation.

Actors and Roles

NM.

Telecom resources

NM, NFVO.

Assumptions

PNFD on-boarding is triggered by the NM.

Pre-conditions

NFVO is running.

NM is operational.

Begins when

NM determines a need in on-boarding a PNFD to make it available for use by NS Descriptors (NSDs).

Step 1 (M)

NM sends a PNFD on-board request to the NFVO, according to [6], clause 7.2.8. The request contains the PNFD to be on-boarded.

Step 2 (M)

NFVO processes the request and on-boards the PNFD.

Step 3 (M)

NFVO sends to the NM the result of the operation.

Exceptions

Post-conditions

The PNFD is on-boarded and available for use by NS Descriptors.

Traceability

REQ-NFV_LCM_Os-Ma-nfvo-FUN-x

Goal

Enable NM to create a new version of already on-boarded PNFD using Update PNFD operation.

Actors and Roles

NM.

Telecom resources

NM, NFVO.

Assumptions

Pre-conditions

NFVO is operational.

NM is operational.

The old version of the PNFD is on-boarded.

Begins when

NM determines a need in creation of a new version of already on-boarded PNFD using Update PNFD operation.

Step 1 (M)

NM sends a Update PNFD request to the NFVO, according to [6], clause 7.2.9. The request contains the PNFD to be created as a new version of the existing PNFD.

Step 2 (M)

NFVO processes the request and creates a new version of the PNFD

Step 3 (M)

NFVO sends to the NM the result of the operation.

Exceptions

Post-conditions

The new version of the PNFD is created and available for use by NS Descriptors.

Traceability

REQ- NFV_LCM_Os-Ma-nfvo-FUN-28

Goal

Enable NM to update the user defined data on PNFD using Update PNFD. operation.

Actors and Roles

NM.

Telecom resources

NM, NFVO.

Assumptions

Pre-conditions

NFVO is operational.

NM is operational.

PNFD is on-boarded.

Begins when

NM determines a need in updating the user defined data on PNFD using Update PNFD operation.

Step 1 (M)

NM sends a Update PNFD request to the NFVO, according to [6], clause 7.2.9. The request contains the user defined data to be updated and does not contain new PNFD to be created.

Step 2 (M)

NFVO processes the request and updates the user defined data on the PNFD.

Step 3 (M)

NFVO sends to the NM the result of the operation.

Exceptions

Post-conditions

The user defined data on the PNFD is updated.

Traceability

REQ- NFV_LCM_Os-Ma-nfvo-FUN-30

Goal

Enable NM to delete the PNFDs.

Actors and Roles

NM.

Telecom resources

NM, NFVO.

Assumptions

Pre-conditions

NFVO is operational.

NM is operational.

The PNFD(s) are on-boarded and not in use in any of the NSs that are in the active or NOT_INSTANTIATED state.

Begins when

NM determines a need in deletion of the PNFD(s).

Step 1 (M)

NM sends a Delete PNFD request to the NFVO, according to [6], clause 7.2.10. The request contains

– identification of the on-boarded instance(s) of the PNFD(s) to be deleted.

– indication if the delete operation is to be applied on all versions of these PNFD instances.

Step 2 (M)

NFVO processes the request and deletes the PNFD(s) as requested.

Step 3 (M)

NFVO sends to the NM the result of the operation.

Exceptions

Post-conditions

The PNFD(s) are deleted as requested.

Traceability

REQ- NFV_LCM_Os-Ma-nfvo-FUN-31

Goal

Enable NM to query the NFVO concerning details of one or more PNFDs.

Actors and Roles

NM.

Telecom resources

NM, NFVO.

Assumptions

Pre-conditions

NFVO is operational.

NM is operational.

The PNFD(s) are on-boarded.

Begins when

NM determines a need in querying of the PNFD(s).

Step 1 (M)

NM sends a Query PNFD request to the NFVO, according to [6], clause 7.2.11. The request contains

– Filter conditions to select the PNFDs on which the query applies, based on attributes of the PNFDs

– A list of attribute names of the PNFD. If present, only these attributes are returned for the instances of PNFD matching the filter. If absent, the complete PNFD instances are returned.

Step 2 (M)

NFVO processes the request and provides the requested information.

Step 3 (M)

NFVO sends to the NM the result of the operation.

Exceptions

Post-conditions

The information on the PNFDs provided to the NM as requested.

Traceability

REQ- NFV_LCM_Os-Ma-nfvo-FUN-32

Date

Meeting

TDoc

CR

Rev

Cat

Subject/Comment

New version

2017-06

SA#76

SP-170504

0001

1

F

Moving LCM supported use cases and requirements from TS 28.510

14.1.0

2017-06

SA#76

SP-170504

0002

2

F

VNF application software update

14.1.0

2018-03

SA#79

SP-180059

0004

1

F

Scope extension

14.2.0

2018-03

SA#79

SP-180059

0005

1

F

Use case of NS instantiation

14.2.0

2018-03

SA#79

SP-180059

0006

1

F

Use cases of PNF addition, removal, and modification

14.2.0

2018-06

SA#80

SP-180417

0009

2

B

Add use case of adding VNF instance to a NS with connectivity

15.0.0

2018-06

SA#80

SP-180417

0010

2

B

Add use case of adding external connectivity to a PNF or VNF instance

15.0.0

2018-06

SA#80

SP-180417

0011

2

B

Add use case of adding NS virtual link to a NS instance

15.0.0

2018-06

SA#80

SP-180417

0013

2

B

Add use case of changing external connectivity to a PNF or VNF instance

15.0.0

2018-06

SA#80

SP-180417

0014

2

B

Adding requirement for PNFD on-boarding use case

15.0.0

2018-06

SA#80

SP-180417

0016

1

B

Use case and requirement of adding VNFFG to a NS instance

15.0.0

2018-06

SA#80

SP-180417

0017

1

B

Use case and requirement of updating VNFFG in a NS instance

15.0.0

2020-07

–

–

–

–

–

Update to Rel-16 version (MCC)

16.0.0

2022-03

–

–

–

–

–

Update to Rel-17 version (MCC)

17.0.0