TS 28.528
Life Cycle Management (LCM)
for Mobile Networks that include
Virtualized Network Functions –
Stage 3

3GPP‑Page ETSI‑search CONTENT_↓

V17.0.0 (PDF) 2022/03 9 p.

V16.0.0 2020/06 9 p.

V15.1.0 2018/12 9 p.

V14.1.0 2017/12 9 p.

Rapporteur:: Mr. Andrianov, Anatoly
Nokia Germany

Content for TS 28.528 Word version: 17.0.0

0 Introduction 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.525:

Telecommunication management; Life Cycle Management (LCM) for mobile networks that include virtualized network functions; Requirements

TS 28.526:

Telecommunication management; Life Cycle Management (LCM) for mobile networks that include virtualized network functions; Procedures

TS 28.527:

Telecommunication management; Life Cycle Management (LCM) for mobile networks that include virtualized network functions; Stage 2

TS 28.528:

Telecommunication management; Life Cycle Management (LCM) for mobile networks that include virtualized network functions; Stage 3

1 Scope p. 5

The present document is the Life Cycle Management (LCM) stage 3 specification for mobile networks that include virtualized network functions.

2 References p. 5

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; Concept, architecture and requirements for mobile networks that include virtualized network functions".

[3]

ETSI GS NFV-SOL 002 (V2.3.1): "Network Function Virtualisation (NFV) Release 2; Protocols and Data Models; RESTful protocols specification for the Ve-Vnfm Reference Point".

[4]

ETSI GS NFV-SOL 005 ( V2.5.1): "Network Functions Virtualisation (NFV); Protocols and Data Models; RESTful protocols specification for the Os-Ma-Nfvo Reference Point".

3 Definitions and abbreviations p. 5

3.1 Definitions p. 5

For the purposes of the present document, the terms and definitions given in TR 21.905, 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.

3.2 Abbreviations p. 5

For the purposes of the present document, the abbreviations given in TR 21.905, 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.

4 Data model and interface definitions p. 5

4.1 Os-Ma-nfvo p. 5

For Os-Ma-nfvo NSD management, the following shall be used:

the RESTful API URI structure and supported content formats specified in clause 4.2 of ETSI GS NFV-SOL 005 [4], and
the RESTful API common procedures specified in clause 4.3 of ETSI GS NFV-SOL 005 [4], and
the RESTful API common data types specified in clause 4.4 of ETSI GS NFV-SOL 005 [4], and
the NSD management RESTful API resource structure, methods, resources and data model specified in clause 5 of ETSI GS NFV-SOL 005 [4].

For Os-Ma-nfvo NS lifecycle management, the following shall be used:

the RESTful API URI structure and supported content formats specified in clause 4.2 of ETSI GS NFV-SOL 005 [4], and
the RESTful API common procedures specified in clause 4.3 of ETSI GS NFV-SOL 005 [4], and
the RESTful API common data types specified in clause 4.4 of ETSI GS NFV-SOL 005 [4], and
the NS LCM RESTful API resource structure, methods, resources and data model specified in clause 6 of ETSI GS NFV-SOL 005 [4].

For Os-Ma-nfvo NS lifecycle change notification, the following shall be used:

the RESTful API URI structure and supported content formats specified in clause 4.2 of ETSI GS NFV-SOL 005 [4], and
the RESTful API common procedures specified in clause 4.3 of ETSI GS NFV-SOL 005 [4], and
the RESTful API common data types specified in clause 4.4 of ETSI GS NFV-SOL 005 [4], and
the NS lifecycle change notification RESTful API resource structure, methods, resources and data model specified in clause 7 of ETSI GS NFV-SOL 005 [4].

For Os-Ma-nfvo VNF package management, the following shall be used:

the RESTful API URI structure and supported content formats specified in clause 4.2 of ETSI GS NFV-SOL 005 [4], and
the RESTful API common procedures specified in clause 4.3 of ETSI GS NFV-SOL 005 [4], and
the RESTful API common data types specified in clause 4.4 of ETSI GS NFV-SOL 005 [4], and
the VNF package management RESTful API resource structure, methods, resources and data model specified in clause 10 of ETSI GS NFV-SOL 005 [4].

4.2 Ve-Vnfm-em p. 6

For Ve-Vnfm-em VNF lifecycle management, the following shall be used:

the RESTful API URI structure and supported content formats specified in clause 4.2 of ETSI GS NFV-SOL 002 [3], and
the RESTful API common procedures specified in clause 4.3 of ETSI GS NFV-SOL 002 [3], and
the RESTful API common data types specified in clause 4.4 of ETSI GS NFV-SOL 002 [3], and
the VNF LCM RESTful API resource structure, methods, resources, data model and handling of errors specified in clause 5 of ETSI GS NFV-SOL 002 [3].

TS 28.528 Life Cycle Management (LCM) for Mobile Networks that include Virtualized Network Functions – Stage 3