Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x
Top   in Index   Prev   Next

TR 28.834
Study on management of cloud-native Virtualized Network Functions (VNF)

V18.0.1 (Wzip)  2023/06  22 p.
Rapporteur:
Miss cao, guangjing
China Mobile Com. Corporation

full Table of Contents for  TR 28.834  Word version:  18.0.1

each clause number in 'red' refers to the equivalent title in the Partial Content
Here   Top
1Scope  p. 7
2References  p. 7
3Definitions of terms, symbols and abbreviations  p. 8
3.1Terms  p. 8
3.2Symbols  p. 8
3.3Abbreviations  p. 8
4Concepts and background  p. 8
5Potential use cases and requirements  p. 9
5.1Use case# 1: Configuration of the cloud-native VNF using generic OAM functions  p. 9
5.1.1Description  p. 9
5.1.2Issues  p. 9
5.1.3Potential requirements  p. 9
5.2Use case# 2: Traffic management of the cloud-native VNF using generic OAM functions  p. 9
5.2.1Description  p. 9
5.2.2Issues  p. 9
5.2.3Potential requirements  p. 10
5.3Use case# 3: Performance monitoring of the cloud-native VNF using generic OAM functions  p. 10
5.3.1Description  p. 10
5.3.2Issues  p. 10
5.3.3Potential requirements  p. 10
5.4Use case# 4: Failure of VNFC within cloud-native VNF  p. 10
5.4.1Description  p. 10
5.4.2Potential requirements  p. 11
5.5Use case# 5: NF creation as a cloud native VNF  p. 11
5.5.1Description  p. 11
5.5.2Issues  p. 12
5.5.3Potential requirements  p. 12
5.6Use case# 6: Scaling of cloud-native VNF  p. 12
5.6.1Description  p. 12
5.6.2Issues  p. 12
5.6.3Potential requirements  p. 12
5.7Use case# 7: Healing of cloud-native VNF  p. 12
5.7.1Description  p. 12
5.7.2Issues  p. 13
5.7.3Potential requirements  p. 13
5.8Use case# 8: VNF package update of the cloud-native VNF  p. 13
5.8.1Description  p. 13
5.8.2Issues  p. 14
5.8.3Potential requirements  p. 14
5.9Use case# 9: VNF package management of the cloud-native VNF  p. 14
5.9.1Description  p. 14
5.9.2Issues  p. 14
5.9.3Potential requirements  p. 14
6Potential solutions  p. 15
6.1Potential solution for management of the cloud-native VNF using generic OAM functions  p. 15
6.1.1Introduction  p. 15
6.1.2Description  p. 15
6.2Potential impact of allocation of functionality about generic OAM functions  p. 15
6.2.1Introduction  p. 15
6.2.2ETSI GR NFV-EVE 019 Solution A  p. 15
6.2.3ETSI GR NFV-EVE 019 Solution B1  p. 16
6.2.4ETSI GR NFV-EVE 019 Solution B2  p. 17
6.2.5ETSI GR NFV-EVE 019 Solution C  p. 18
6.3Potential solution for cloud native VNF creation with ETSI NFV MANO  p. 18
6.3.1Introduction  p. 18
6.3.2Description  p. 19
6.4Potential solution for scaling of cloud-native VNF with ETSI NFV MANO  p. 19
6.4.1Introduction  p. 19
6.4.2Description  p. 19
6.5Potential solution for healing of cloud-native NFV  p. 20
6.5.1Solution for healing of cloud-native NFV with ETSI NFV MANO  p. 20
6.5.1.1Introduction  p. 20
6.5.1.2Description  p. 20
6.5.2Solution for healing of cloud-native NFV with ETSI NFV VNFM  p. 20
6.5.2.1Introduction  p. 20
6.5.2.2Description  p. 20
6.6Potential solution for cloud-native VNF package management with ETSI NFV MANO  p. 20
6.6.1Introduction  p. 20
6.6.2Description  p. 20
7Conclusions and recommendations  p. 21
7.1General  p. 21
7.2Issue on NF creation as a cloud native VNF  p. 21
7.3Issue on Scaling of cloud-native VNF  p. 21
7.4Issue on healing of cloud-native VNF  p. 21
7.5Issue on VNF package management of the cloud-native VNF  p. 21
$Change history  p. 22

Up   Top