Tech-invite3GPPspecsSIPRFCs
Overview21222324252627282931323334353637384‑5x

Content for  TS 28.515  Word version:  16.0.0

Top   Top   None   None   Next
0…   5…   6…

 

0  IntroductionWord‑p. 4
The present document is part of a TS-family covering the 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management, as identified below:
TS 28.515
"Fault Management (FM) for mobile networks that include virtualized network functions; Requirements".
TS 28.516
"Fault Management (FM) for mobile networks that include virtualized network functions; Procedures".
TS 28.517
"Fault Management (FM) for mobile networks that include virtualized network functions; Stage 2".
TS 28.518
"Fault Management (FM) for mobile networks that include virtualized network functions; Stage 3".
Up

1  ScopeWord‑p. 5
The present document (together with the relevant requirements described in [2], [3], [4] and [5]) specifies the requirements applicable to Fault Management (FM) of mobile networks that include virtualized network functions.

2  References

The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
  • References are either specific (identified by date of publication, edition number, version number, etc.) or non specific.
  • For a specific reference, subsequent revisions do not apply.
  • For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1]
TR 21.905: "Vocabulary for 3GPP Specifications".
[2]
TS 28.500: "Telecommunication management; Management concept, architecture and requirements for mobile networks that include virtualized network functions".
[3]
TS 32.101: "Telecommunication management; Principles and high level requirements".
[4]
TS 32.102: "Telecommunication management; Architecture".
[5]
TS 32.111-1: "Telecommunication management; Fault Management; Part 1: 3G fault management requirements".
[6]
ETSI GS NFV-IFA 010 (V2.2.1): "Network Functions Virtualisation (NFV); Management and Orchestration; Functional Requirements Specification".
Up

3  Definitions and abbreviations

3.1  Definitions

For the purposes of the present document, the terms and definitions given in TR 21.905 and in TS 28.500 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 or in TS 28.500.
Up

3.2  Abbreviations

For the purposes of the present document, the abbreviations given in TR 21.905 and in TS 28.500 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 or in TS 28.500.
VM
Virtual Machine
vNIC
virtual Network Interface Card
vPORT
virtual Port
Up

4  Concepts and backgroundWord‑p. 6

4.1  Fault Management in the context of NFV

Fault Management functionality traditionally includes fault detection, generation of alarms, clearing of alarms, alarm forwarding and filtering, storage and retrieval of alarms, correlation of alarms and events, alarm root cause analysis and fault recovery. With introduction of virtualized network functions (VNFs) into mobile networks, Fault Management functionality is distributed over different functional blocks. These different functional blocks may be located at different levels such as NFV Infrastructure (NFVI) level, NE level, NFV Management and Orchestration level and 3GPP network management level.
The decoupling of software from hardware by means of virtualization changes the way in which the faults were managed in non-virtualized NE deployments:
  • Physical hardware faults of NFVI are detected by NFVI and corrected jointly with the support from NFV-MANO. Only information about those faults (e.g. faults corresponding to the virtualized resources) that affect the proper functioning of VNF needs to be provided to 3GPP management system.
  • VNF-related virtualized resource fault information needs to be sent from NFV-MANO to 3GPP management system, and then 3GPP management system can take some necessary actions.
  • VNF application fault information needs to be sent from the VNF instance to the corresponding 3GPP management system that is responsible for taking some necessary actions.
  • VNF virtualization-specific fault information is detected by VNF and needs to be sent from the VNF instance to both the VNFM and the corresponding 3GPP management system so that they can take necessary actions accordingly.
Up

Up   Top   ToC