4 Data model and interface definitions
28.5283GPPLife Cycle Management (LCM) for mobile networks that include virtualized network functionsRelease 17Stage 3Telecommunication managementTS
4.1 Os-Ma-nfvo
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
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].
Annex A (informative):
Change history
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2018-01 |
SA#78 |
SP-170964 |
0001 |
1 |
F |
Update the references to ETSI NFV SOL specifications |
14.1.0 |
|
2018-06 |
SA#80 |
SP-180417 |
0002 |
1 |
B |
Scope extension to cover RAN |
15.0.0 |
|
2018-12 |
SA#82 |
SP-181041 |
0003 |
– |
F |
Fix outdated reference |
15.1.0 |
|
2020-07 |
– |
– |
– |
– |
– |
Update to Rel-16 version (MCC) |
16.0.0 |
|
2022-03 |
– |
– |
– |
– |
– |
Update to Rel-17 version (MCC) |
17.0.0 |