Tech-invite3GPPspecsSIPRFCs
Overview21222324252627282931323334353637384‑5x

Content for  TS 28.515  Word version:  16.0.0

Top   Top   Up   Prev   Next
0…   5…   6…

 

5  Business level requirements

5.1  Requirements

REQ-NFV_FM-CON-1
The faulty virtualization-specific aspect of a virtualized network function shall be able to be recovered.
REQ-NFV_FM-CON-2
3GPP management system shall be able to get VNF application fault reports about a faulty NE.
REQ-NFV_FM-CON-3
3GPP management system shall be able to get VNF virtualization-related fault reports from NFV-MANO.
REQ-NFV_FM-CON-4
The content of the fault information from VNF application fault reports and VNF virtualization-related fault reports shall enable 3GPP management system to correlate VNF application fault(s) with VNF virtualization-related fault(s).
REQ-NFV_FM-CON-5
EM shall be able to send to VNFM a request to recover the faulty virtualization-specific aspect of a virtualized network function.
Up

5.2  Actor roles

See actors and roles of each use case in clause 5.4.

5.3  Telecommunications resources

See telecom resources of each use case in clause 5.4.

5.4  High-level use casesWord‑p. 7

5.4.1  NE alarm correlation in the context of NFV

Use Case Stage
Evolution / Specification
<<Uses>> Related use

Goal
To correlate NE alarms in a mobile network that includes virtualized network functions.
Actors and Roles
3GPP management system (EM, NM) correlates NE alarms.
NFV MANO functional entity VNFM notifies virtualized resource alarms to 3GPP management system.
Telecom resources
VNFM, 3GPP management system (EM, NM)
Assumptions
- 3GPP management system can get VNF application alarms of the faulty NE, and
- VNFM can get virtualized resource alarms and identify the corresponding VNF instance.
Pre conditions
N/A
Begins when
There is a new failure which may impact the virtualized resource and the corresponding NE application
Step 1 (M)
3GPP management system gets VNF application alarm(s) of a faulty NE. VNFM gets virtualized resource alarm(s) and notifies the corresponding VNF instance related virtualized resource alarm(s) to 3GPP management system.
Step 2 (M)
Based on the virtualized resource alarm(s) sent from VNFM and those VNF application alarms reported from NE, 3GPP management system makes alarm correlation.
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 virtualized resource alarm(s) and VNF application alarm(s) are correlated by 3GPP management system.
Traceability
REQ-MAMO_FM-CON-3, REQ-MAMO_FM-CON-4, REQ-MAMO_FM-CON-5

Up

5.4.2  NFVI Maintenance coordination

Use Case Stage
Evolution / Specification
<<Uses>> Related use

Goal
To avoid the unwanted impact to VNF application from NFVI maintenance
Actors and Roles
NM, NFVO, VNFM, VIM
Telecom resources
NFVO, VNFM VIM, NFVI
Assumptions
There is an agreement that NFV-MANO system should get permission from NM before scheduled NFVI maintenance, managed by NFV-MANO, can start.
Pre conditions
N/A
Begins when
NFVO receives a notification from VIM informing about NFVI maintenance impacting the VRs (Virtualised Resources) that are used by a NS instance (e.g. the subordinative VNF instances and Virtual Links).
Step 1 (M)
NFVO informs NM about the NFVI maintenance.
Step 2 (M)
NM confirms the NFVI maintenance positively or not positively.
Step 3 (M)
NFVO acts according to the response from NM.
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
NFVI maintenance activity has been coordinated between NM and NFVO.
Traceability
FFS

Up


Up   Top   ToC