Tech-invite3GPPspecsSIPRFCs
Overview21222324252627282931323334353637384‑5x

Content for  TS 28.515  Word version:  16.0.0

Top   Top   Up   Prev   None
0…   5…   6…

 

6  Specification level requirementsWord‑p. 8

6.1  Requirements

6.1.1  Requirements for Itf-N

REQ-NFV_FM_Itf-N-FUN-1
IRPAgent shall have the capability to send VNF application alarms to IRPManager.
REQ-NFV_FM_Itf-N-FUN-2
IRPAgent should have the capability to send VNF instance related virtualized resource alarms to IRPManager.
REQ-NFV_FM_Itf-N-FUN-3
The existing AlarmIRP should be reused as much as possible.

6.1.2  Requirements for Os-Ma-nfvo

None.

6.1.3  Requirements for Ve-Vnfm-em

REQ-NFV_FM_Ve-Vnfm-em-FUN-1
The Ve-Vnfm-em reference point shall support a capability allowing VNFM to notify EM the VNF and/or VNFC instance related virtualized resource failure reports, in which information (e.g. VM Identifier, vNIC/vPORT Identifier) of faulty VNF and/or VNFC instance is included.
REQ-NFV_FM_Ve-Vnfm-em-FUN-2
The Ve-Vnfm-em reference point shall support a capability allowing VNFM to notify EM and other authorized consumers who can play the role of EM, the virtualization-specific aspect failure reports, in which information of faulty VNF and VNFC instance(s) is included.
REQ-NFV_FM_Ve-Vnfm-em-FUN-3
The Ve-Vnfm-em reference point shall support the EM to send to VNFM a request to execute the VNF Healing of a virtualized network function indicating the corresponding healing procedure and VNFC instance(s).
REQ-NFV_FM_Ve-Vnfm-em-FUN-4
The Ve-Vnfm-em reference point shall support a capability allowing EM to subscribe/unsubscribe to VNF and VNFC instance related alarm notification provided by the VNFM.
Up

6.1.4  Requirements for Ve-Vnfm-vnf

REQ-NFV_FM_Ve-Vnfm-vnf-FUN-1 The Ve-Vnfm-vnf reference point shall support the capability for the VNF virtualization-specific component to notify about faulty virtualization-specific aspects to VNFM.

6.2  Actor roles

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

6.3  Telecommunications resources

See telecom resources of each use case in clause 6.4.

6.4  Use casesWord‑p. 9

6.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
EM or NM correlates NE alarms.
VNFM notifies virtualized resource alarms to EM.
EM sends VNF application failure reports and VNF instance related virtualized failure reports to NM.
Telecom resources
NM, EM, VNFM
Assumptions
3GPP management system (EM, NM) can get VNF application alarms of the faulty NE. 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)
EM sends VNF application failure reports of a fault NE to NM.
Step 2 (M)
VNFM sends VNF instance related virtualized failure reports to EM, in which information of the failed VNF instance is included. EM reports VNF instance related virtualized failure reports to NM.
NOTE: Sequence of step 1 and step 2 may be reversed.
Step 3 (M)
Based on the virtualized resource failure reports sent from VNFM and VNF application alarms, EM or NM makes the alarm correlation.
Ends when
Ends when all steps identified above are successfully completed or when an exception occurs.
Exceptions
One of the steps identified above fails.
Post Conditions
Failure reports of a faulty NE are reported and correlated by 3GPP management system.
Traceability
REQ-NFV_FM_Itf-N-FUN-1, REQ-NFV_FM_Itf-N-FUN-2, REQ-NFV_FM_Ve-Vnfm-em-FUN-1

Up

6.4.2  VNF Healing through operation request to VNFM by EM

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

Goal
To recover the faulty virtualization-specific aspect of a virtualized network function by executing a VNF Healing through an operation request to VNFM by EM and notify about the execution of the VNF healing through reference point Ve-Vnfm-em.
Actors and Roles
EM requests the VNFM to execute the VNF healing based on the information included in the request.
Telecom resources
EM.
VNFM.
VNF.
Assumptions
EM is subscribed to VNF lifecycle change notifications from the VNFM.
Pre-conditions
The subject VNF instance is not being healed at the moment.
Begins when
A faulty virtualization-specific aspect of the VNF has been notified to EM.
Step 1 (M)
EM determines that VNF Healing is needed.
Step 2 (M)
EM requests the VNFM to execute the VNF Healing with indication of VNF Components to recover and indication of the healing procedure to execute with input parameters as required.
Step 3 (O)
VNFM sends to EM a notification about the start of the VNF healing execution.
Step 4 (M)
The VNFM executes the procedure to heal the VNF instance.
Step 5 (M)
VNFM sends to EM a notification about the end and the result of the VNF Healing execution.
Ends when
All the steps identified above are successfully completed.
Exceptions
The VNF Healing procedure in step 4 fails.
Post-conditions
The faulty virtualization-specific aspect of the VNF is recovered.
Traceability
REQ-NFV_FM_Ve-Vnfm-em-FUN-3

Up

6.4.3  Virtualization-specific aspect failure detection and notification by VNFMWord‑p. 10
Use Case Stage
Evolution / Specification
<<Uses>> Related use

Goal
To notify the EM about a virtualization-specific failure of a virtualized network function through Ve-Vnfm-em reference point.
Actors and Roles
VNF virtualization-specific component.
Telecom resources
EM.
VNFM.
VNF.
Assumptions
- VNFM receives virtualised resource fault reports from VIM.
- VNF application-specific fault is reported to the EM.
- EM is subscribed to VNF-related virtualization fault reports from the VNFM.
Pre-conditions
N/A
Begins when
The virtualization-specific failure is detected by the VNF virtualization-specific component.
Step 1 (M)
VNF virtualization-specific component sends virtualization-specific fault notification to VNFM over Ve-Vnfm-vnf reference point.
Step 2 (M)
VNFM creates VNF virtualization-related fault report about the VNF and its VNF Components.
Step 3 (M)
VNFM sends the VNF virtualization-related fault report to the EM over Ve-Vnfm-em reference point.
Ends when
All the steps identified above are successfully completed.
Exceptions
Post-conditions
The EM is notified about the virtualization-specific failure of the subject VNF.
Traceability
REQ-NFV_FM_Ve-Vnfm-vnf-FUN-1, REQ-NFV_FM_Ve-Vnfm-em-FUN-2

Up

6.4.4  Virtualization-specific aspect failure detection and notification by EMWord‑p. 11
Use Case Stage
Evolution / Specification
<<Uses>> Related use

Goal
To notify the EM about a virtualization-specific failure of a virtualized network function.
Actors and Roles
VNF virtualization-specific component
Telecom resources
EM.
VNFM.
VNF.
Assumptions
- VNF application-specific fault is reported to the EM.
- EM is subscribed to VNF-related virtualization fault reports.
Pre-conditions
N/A
Begins when
The virtualization-specific failure is detected by the VNF virtualization-specific component.
Step 1 (M)
VNF virtualization-specific component sends virtualization-specific fault notification to EM.
Ends when
All the steps identified above are successfully completed.
Exceptions
Post-conditions
The EM is notified about the virtualization-specific failure of the subject VNF.
Traceability

Up

6.4.5  NE alarm reporting in the context of NFV

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

Goal
To send or notify NE alarms in a mobile network that includes virtualized network functions.
Actors and Roles
EM reports NE alarms to NM.
NFV MANO functional entity VNFM notifies VNF instance alarms related to virtualized resource to 3GPP management system EM.
Telecom resources
VNFM, EM, NM
Assumptions
EM can detect VNF application alarms of the faulty NE, and
VNFM can get virtualized resource alarms, identify the corresponding VNF instance and notify the corresponding VNF instance alarm to EM.
Pre conditions
N/A
Begins when
There is a failure which impacts the NE application and/or the corresponding virtualized resources.
Step 1 (M)
EM detects VNF application alarm(s) of a faulty NE.
Step 2 (M)
If there is virtualized resource alarm(s), VNFM notifies the corresponding VNF instance alarm(s) with related virtualized resource information to EM.
Step 3 (M)
EM reports the NE application alarm(s) and/or the VNF instance alarm(s) sent from VNFM to NM over Itf-N.
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
NE alarms are sent from EM to NM.
Traceability
REQ-NFV_FM_Itf-N-FUN-3

Up

6.4.6  Virtualization-specific aspect failure notification by VNFMWord‑p. 12
Use Case Stage
Evolution / Specification
<<Uses>> Related use

Goal
To notify authorized consumer who can play the role of EM about virtualization-specific aspect alarms.
Actors and Roles
The consumer
Telecom resources
VNFM
Assumptions
The consumer that requires the VNF-related virtualization fault information produced by VNFM, has a subscription to receive such information,
Pre-conditions
N/A
Begins when
VNFM is aware of a VNF virtualization-specific aspect problem.
Step 1 (M)
VNFM creates an alarm record.
Step 2 (M)
VNFM sends the alarm record to the consumer(s) which has subscribed to receiving such information.
Ends when
All the steps identified above are successfully completed.
Exceptions
Post-conditions
The consumer(s) has received the virtualization-specific aspects failure information.
Traceability
REQ-NFV_FM_Ve-Vnfm-em-FUN-2

Up

$  Change historyWord‑p. 13

Up   Top