Content for TS 28.510 Word version: 17.0.0
5 Business level requirements
5.1 Requirements
5.2 Actor roles
5.3 Telecommunications resources
5.4 High-level use cases
5 Business level requirements p. 6
5.1 Requirements p. 6
REQ-NFV_CM-CON-1
EM shall be able to perform necessary virtualized network function configuration due to the VNF lifecycle management from VNFM:
- Add the VNF as managed node after VNF instantiation.
- Remove the VNF from managed nodes after VNF termination.
- Configure the VNF after some VNF LCM operations (i.e. instantiation).
- Re-configure the VNF after some VNF LCM operations (e.g. scaling, update/upgrade, etc.).
3GPP management system shall have a capability to create MO(s) corresponding to a VNF instance.
REQ-NFV_CM-CON-3
3GPP management system shall have a capability to configure the MO(s) corresponding to a VNF instance.
REQ-NFV_CM-CON-4
Void
REQ-NFV_CM-CON-5
Void
REQ-NFV_CM-CON-6
Void
REQ-NFV_CM-CON-7
Void
REQ-NFV_CM-CON-8
3GPP management system shall have a capability to delete MOI(s) related to a VNF instance.
REQ-NFV_CM-CON-9
NM shall have a capability retrieving views of virtualized NEs from various management systems (e.g. EM, NFVO).
REQ-NFV_CM-CON-10
3GPP management system shall have a capability to manage bulk creation of MOIs representing NEs whose software components are designed to run on NFVI.
5.2 Actor roles p. 7
See detailed actors and roles for each use case in clause 5.4.
5.3 Telecommunications resources p. 7
See detailed telecommunication resources for each use case in clause 5.4.
5.4 High-level use cases p. 7
5.4.1 Create Managed Object for Network Element in the context of NFV p. 7
| Use Case Stage | Evolution/Specification | <<Uses>> Related use |
|---|---|---|
| Goal | To create Managed Object (MO) for a new NE that includes virtualized network functions. | |
| Actors and Roles | 3GPP management system (EM, NM) creates MO for NE. NFV MANO system instantiates VNF instance and configures VNF non-application specific parameters for VNF instance. | |
| Telecom resources | NFV MANO system (NFVO, VNFM), 3GPP management system (EM, NM) | |
| Assumptions | NFV MANO system has already instantiated a VNF instance using the related VNF Package. | |
| Pre conditions | N/A | |
| Begins when | Operator has decided to create MO for a new NE. | |
| Step 1 (M) | 3GPP management system adds the VNF instance as a NE MO. 3GPP management system can configure the VNF instance with application specific parameters during the creation process of NE MO. | |
| 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 MO for a new NE is added into 3GPP management system and is ready for further configuration management (e.g. new or additional application-specific parameters configuration can happen). | |
| Traceability | REQ-NFV_CM-CON-2, REQ-NFV_CM-CON-3 |
5.4.2 Delete MOI(s) for Network Element in the context of NFV p. 8
| Use Case Stage | Evolution/Specification | <<Uses>> Related use |
|---|---|---|
| Goal | To delete MOI(s) for a NE that includes virtualized network function. | |
| Actors and Roles | 3GPP management system (EM, NM) deletes MOI(s) for NE. | |
| Telecom resources | 3GPP management system (EM, NM). | |
| Assumptions | The MOI(s) for the NE to be deleted has been created. | |
| Pre conditions | The NE services have been released. | |
| Begins when | Operator has decided to delete the MOI(s) for a NE. | |
| Step 1 (M) | 3GPP management system deletes the MOI(s) for the subject NE. | |
| 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 MOI(s) for the NE are deleted. | |
| Traceability | REQ-NFV_CM-CON-8 |
5.4.3 Update the configuration parameters corresponding to the subject VNF instance (application part) after a VNF instance is scaled p. 8
| Use Case Stage | Evolution/Specification | <<Uses>> Related use |
|---|---|---|
| Goal | Update the configuration parameters corresponding to the subject VNF instance (application part) after the VNF is scaled. | |
| Actors and Roles | 3GPP management system (EM, NM). | |
| Telecom resources | NFV MANO (NFVO, VNFM), 3GPP management system (EM, NM) | |
| Assumptions | ||
| Pre-conditions | ||
| Begins when | 3GPP management system is aware that the VNF instance has been scaled and determines the configuration parameters need to be updated. | |
| Step 1 (M) | 3GPP management system updates the configuration parameters corresponding to the subject VNF instance (application part). | |
| 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 configuration parameters corresponding to the subject VNF instance (application part) are updated. | |
| Traceability | REQ-NFV_CM-CON-3 |
5.4.4 Retrieve virtualized NE information by NM p. 9
| Use Case Stage | Evolution/Specification | <<Uses>> Related use |
|---|---|---|
| Goal | NM updates its view of its managed virtualized NEs. | |
| Actors and Roles | NM | |
| Telecom resources | EM, NFVO. | |
| Assumptions | None | |
| Pre-conditions | None | |
| Begins when | NM determines a need to update its view of its managed VNFs. | |
| Step 1 (M) | NM requests NFVO to provide information of VNFs (see clause 7.3.6 in ETSI GS NFV-IFA 013 [7]. NM requests EM to provide information of virtualized NEs. This information is VNF application-specific. | |
| Step 2 (M) | NFVO responds with the information requested. NM updates its view of its managed virtualized NE, EM responds to NM with the information requested. | |
| 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 to update its view of its managed virtualized NEs. | |
| Traceability | REQ-NFV_CM-CON-9, |
