aboutsummaryrefslogtreecommitdiffstats
path: root/adapters/mso-vnfm-adapter/mso-vnfm-adapter-ext-clients/src/main/resources/SOL003-VNFLifecycleManagementNotification-API.json
blob: d3b6ebaa7e27121e7a2665b13338f71d3d8df32a (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
1174
1175
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186
1187
1188
1189
1190
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228
1229
1230
1231
1232
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284
1285
1286
1287
1288
1289
1290
1291
1292
1293
1294
1295
1296
1297
1298
1299
1300
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340
1341
1342
1343
1344
1345
1346
1347
1348
1349
1350
1351
1352
1353
1354
1355
1356
1357
1358
1359
1360
1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
1381
1382
1383
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396
1397
1398
1399
1400
1401
1402
1403
1404
1405
1406
1407
1408
1409
1410
1411
1412
1413
1414
1415
1416
1417
1418
1419
1420
1421
1422
1423
1424
1425
1426
1427
1428
1429
1430
1431
1432
1433
1434
1435
1436
1437
1438
1439
1440
1441
1442
1443
1444
1445
1446
1447
1448
1449
1450
1451
1452
1453
1454
1455
1456
1457
1458
1459
1460
1461
1462
1463
1464
1465
1466
1467
1468
1469
1470
1471
1472
1473
1474
1475
1476
1477
1478
1479
1480
1481
1482
1483
1484
1485
1486
1487
1488
1489
1490
1491
1492
1493
1494
1495
1496
1497
1498
1499
1500
1501
1502
1503
1504
1505
1506
1507
1508
1509
1510
1511
1512
1513
1514
1515
1516
1517
1518
1519
1520
1521
1522
1523
1524
1525
1526
1527
1528
1529
1530
1531
1532
1533
1534
1535
1536
1537
1538
1539
1540
1541
1542
1543
1544
1545
1546
1547
1548
1549
1550
1551
1552
1553
1554
1555
1556
1557
1558
1559
1560
1561
1562
1563
1564
1565
1566
1567
1568
1569
1570
1571
1572
1573
1574
1575
1576
1577
1578
1579
1580
1581
1582
1583
1584
1585
1586
1587
1588
1589
1590
1591
1592
1593
1594
1595
1596
1597
1598
1599
1600
1601
1602
1603
1604
1605
1606
1607
1608
1609
1610
1611
1612
1613
1614
1615
1616
1617
1618
1619
1620
1621
1622
1623
1624
1625
1626
1627
1628
1629
1630
1631
1632
1633
1634
1635
1636
1637
1638
1639
1640
1641
1642
1643
1644
1645
1646
1647
1648
1649
1650
1651
1652
1653
1654
1655
1656
1657
1658
1659
1660
1661
1662
1663
1664
1665
1666
1667
1668
1669
1670
1671
1672
1673
1674
1675
1676
1677
1678
1679
1680
1681
1682
1683
1684
1685
1686
1687
1688
1689
1690
1691
1692
1693
1694
1695
1696
1697
1698
1699
1700
1701
1702
1703
1704
1705
1706
1707
1708
1709
1710
1711
1712
1713
1714
1715
1716
1717
1718
1719
1720
1721
1722
1723
1724
1725
1726
1727
1728
1729
1730
1731
1732
1733
1734
1735
1736
1737
1738
1739
1740
1741
1742
1743
1744
1745
1746
1747
1748
1749
1750
1751
1752
1753
1754
1755
1756
1757
1758
1759
1760
1761
1762
1763
1764
1765
1766
1767
1768
1769
1770
1771
1772
1773
1774
1775
1776
1777
1778
1779
1780
1781
1782
1783
1784
1785
1786
1787
1788
1789
1790
1791
1792
1793
1794
1795
1796
1797
1798
1799
1800
1801
1802
1803
1804
1805
1806
1807
1808
1809
1810
1811
1812
1813
1814
1815
1816
1817
1818
1819
1820
1821
1822
1823
1824
1825
1826
1827
1828
1829
1830
1831
1832
1833
1834
1835
1836
1837
1838
1839
1840
1841
1842
1843
1844
1845
1846
1847
1848
1849
1850
1851
1852
1853
1854
1855
1856
1857
1858
1859
1860
1861
1862
1863
1864
1865
1866
1867
1868
1869
1870
1871
1872
1873
1874
1875
1876
1877
1878
1879
1880
1881
1882
1883
1884
1885
1886
1887
1888
1889
1890
1891
1892
1893
1894
1895
1896
1897
{
  "swagger" : "2.0",
  "info" : {
    "description" : "SOL003 - VNF Lifecycle Management Notification interface\n\nIMPORTANT: Please note that this file might be not aligned to the current version of the ETSI Group Specification it refers to. In case of discrepancies the published ETSI Group Specification takes precedence.\n\nIn clause 4.3.2 of ETSI GS NFV-SOL 003 v2.4.1, an attribute-based filtering mechanism is defined. This mechanism is currently not included in the corresponding OpenAPI design for this GS version. Changes to the attribute-based filtering mechanism are being considered in v2.5.1 of this GS for inclusion in the corresponding future ETSI NFV OpenAPI design.\nPlease report bugs to https://forge.etsi.org/bugzilla/buglist.cgi?component=Nfv-Openapis&list_id=61&product=NFV&resolution=\n",
    "version" : "1.1.1",
    "title" : "SOL003 - VNF Lifecycle Management Notification interface",
    "license" : {
      "name" : "ETSI Forge copyright notice",
      "url" : "https://forge.etsi.org/etsi-forge-copyright-notice.txt"
    }
  },
  "basePath" : "/so/vnfm-adapter/v1/",
  "schemes" : [ "https" ],
  "consumes" : [ "application/json" ],
  "produces" : [ "application/json" ],
  "paths" : {
    "/lcn/VnfLcmOperationOccurrenceNotification" : {
      "post" : {
        "description" : "Notify\n\nThe POST method delivers a notification from the server to the client.\n",
        "parameters" : [ {
          "in" : "body",
          "name" : "VnfLcmOperationOccurrenceNotification",
          "description" : "A notification about on-boarding of a VNF package.",
          "required" : true,
          "schema" : {
            "$ref" : "#/definitions/VnfLcmOperationOccurrenceNotification"
          }
        }, {
          "name" : "Authorization",
          "in" : "header",
          "description" : "The authorization token for the request. Reference: IETF RFC 7235\n",
          "required" : false,
          "type" : "string"
        }, {
          "name" : "Content-Type",
          "in" : "header",
          "description" : "The MIME type of the body of the request. Reference: IETF RFC 7231\n",
          "required" : true,
          "type" : "string"
        } ],
        "responses" : {
          "204" : {
            "description" : "No Content\nThe notification was delivered successfully.\n",
            "headers" : {
              "WWW-Authenticate" : {
                "type" : "string",
                "description" : "Challenge if the corresponding HTTP request has not provided authorization, or error details if the corresponding HTTP request has provided an invalid authorization token.\n"
              }
            }
          },
          "400" : {
            "description" : "Bad Request\nIf the request is malformed or syntactically incorrect (e.g. if the request URI contains incorrect query parameters or a syntactically incorrect payload body), the API producer shall respond with this response code. The \"ProblemDetails\" structure shall be provided, and should include in the \"detail\" attribute more information about the source of the problem.\n\n ---\n\nIf the request contains a malformed access token, the API producer should respond with this response. The details of the error shall be returned in the WWW-Authenticate HTTP header, as defined in IETF RFC 6750 and IETF RFC 7235. The ProblemDetails structure may be provided.\n\n ---\n\nIf there is an application error related to the client's input that cannot be easily mapped to any other HTTP response code (\"catch all error\"), the API producer shall respond with this response code.The \"ProblemDetails\" structure shall be provided, and shall include in the \"detail\" attribute more information about the source of the problem.\n",
            "headers" : {
              "Content-Type" : {
                "type" : "string",
                "description" : "The MIME type of the body of the response."
              },
              "WWW-Authenticate" : {
                "type" : "string",
                "description" : "Challenge if the corresponding HTTP request has not provided authorization, or error details if the corresponding HTTP request has provided an invalid authorization token.\n"
              }
            },
            "schema" : {
              "type" : "object",
              "required" : [ "detail", "status" ],
              "properties" : {
                "type" : {
                  "type" : "string",
                  "format" : "URI",
                  "description" : "A URI reference according to IETF RFC 3986 [5] that identifies the problem type. It is encouraged that the URI provides human-readable documentation for the problem (e.g. using HTML) when dereferenced. When this member is not present, its value is assumed to be \"about:blank\".\n"
                },
                "title" : {
                  "type" : "string",
                  "description" : "A short, human-readable summary of the problem type. It should not change from occurrence to occurrence of the problem, except for purposes of localization. If type is given and other than \"about:blank\", this attribute shall also be provided. A short, human-readable summary of the problem type.  It SHOULD NOT change from occurrence to occurrence of the problem, except for purposes of localization (e.g., using proactive content negotiation; see [RFC7231], Section 3.4).\n"
                },
                "status" : {
                  "type" : "integer",
                  "description" : "The HTTP status code for this occurrence of the problem. The HTTP status code ([RFC7231], Section 6) generated by the origin server for this occurrence of the problem.\n"
                },
                "detail" : {
                  "type" : "string",
                  "description" : "A human-readable explanation specific to this occurrence of the problem.\n"
                },
                "instance" : {
                  "type" : "string",
                  "format" : "URI",
                  "description" : "A URI reference that identifies the specific occurrence of the problem. It may yield further information if dereferenced.\n"
                }
              },
              "description" : "The definition of the general \"ProblemDetails\" data structure from IETF RFC 7807 [19] is reproduced inthis structure. Compared to the general framework defined in IETF RFC 7807 [19], the \"status\" and \"detail\" attributes are mandated to be included by the present document, to ensure that the response contains additional textual information about an error. IETF RFC 7807 [19] foresees extensibility of the \"ProblemDetails\" type. It is possible that particular APIs in the present document, or particular implementations, define extensions to define additional attributes that provide more information about the error. The description column only provides some explanation of the meaning to Facilitate understanding of the design. For a full description, see IETF RFC 7807 [19].\n"
            }
          },
          "401" : {
            "description" : "Unauthorized\nIf the request contains no access token even though one is required, or if the request contains an authorization token that is invalid (e.g. expired or revoked), the API producer should respond with this response. The details of the error shall be returned in the WWW-Authenticate HTTP header, as defined in IETF RFC 6750 and IETF RFC 7235. The ProblemDetails structure may be provided.\n",
            "headers" : {
              "Content-Type" : {
                "type" : "string",
                "description" : "The MIME type of the body of the response."
              },
              "WWW-Authenticate" : {
                "type" : "string",
                "description" : "Challenge if the corresponding HTTP request has not provided authorization, or error details if the corresponding HTTP request has provided an invalid authorization token.\n"
              }
            },
            "schema" : {
              "type" : "object",
              "required" : [ "detail", "status" ],
              "properties" : {
                "type" : {
                  "type" : "string",
                  "format" : "URI",
                  "description" : "A URI reference according to IETF RFC 3986 [5] that identifies the problem type. It is encouraged that the URI provides human-readable documentation for the problem (e.g. using HTML) when dereferenced. When this member is not present, its value is assumed to be \"about:blank\".\n"
                },
                "title" : {
                  "type" : "string",
                  "description" : "A short, human-readable summary of the problem type. It should not change from occurrence to occurrence of the problem, except for purposes of localization. If type is given and other than \"about:blank\", this attribute shall also be provided. A short, human-readable summary of the problem type.  It SHOULD NOT change from occurrence to occurrence of the problem, except for purposes of localization (e.g., using proactive content negotiation; see [RFC7231], Section 3.4).\n"
                },
                "status" : {
                  "type" : "integer",
                  "description" : "The HTTP status code for this occurrence of the problem. The HTTP status code ([RFC7231], Section 6) generated by the origin server for this occurrence of the problem.\n"
                },
                "detail" : {
                  "type" : "string",
                  "description" : "A human-readable explanation specific to this occurrence of the problem.\n"
                },
                "instance" : {
                  "type" : "string",
                  "format" : "URI",
                  "description" : "A URI reference that identifies the specific occurrence of the problem. It may yield further information if dereferenced.\n"
                }
              },
              "description" : "The definition of the general \"ProblemDetails\" data structure from IETF RFC 7807 [19] is reproduced inthis structure. Compared to the general framework defined in IETF RFC 7807 [19], the \"status\" and \"detail\" attributes are mandated to be included by the present document, to ensure that the response contains additional textual information about an error. IETF RFC 7807 [19] foresees extensibility of the \"ProblemDetails\" type. It is possible that particular APIs in the present document, or particular implementations, define extensions to define additional attributes that provide more information about the error. The description column only provides some explanation of the meaning to Facilitate understanding of the design. For a full description, see IETF RFC 7807 [19].\n"
            }
          },
          "403" : {
            "description" : "Forbidden\nIf the API consumer is not allowed to perform a particular request to a particular resource, the API producer shall respond with this response code. The \"ProblemDetails\" structure shall be provided.  It should include in the \"detail\" attribute information about the source of the problem, and may indicate how to solve it.\n",
            "headers" : {
              "Content-Type" : {
                "type" : "string",
                "description" : "The MIME type of the body of the response."
              }
            },
            "schema" : {
              "type" : "object",
              "required" : [ "detail", "status" ],
              "properties" : {
                "type" : {
                  "type" : "string",
                  "format" : "URI",
                  "description" : "A URI reference according to IETF RFC 3986 [5] that identifies the problem type. It is encouraged that the URI provides human-readable documentation for the problem (e.g. using HTML) when dereferenced. When this member is not present, its value is assumed to be \"about:blank\".\n"
                },
                "title" : {
                  "type" : "string",
                  "description" : "A short, human-readable summary of the problem type. It should not change from occurrence to occurrence of the problem, except for purposes of localization. If type is given and other than \"about:blank\", this attribute shall also be provided. A short, human-readable summary of the problem type.  It SHOULD NOT change from occurrence to occurrence of the problem, except for purposes of localization (e.g., using proactive content negotiation; see [RFC7231], Section 3.4).\n"
                },
                "status" : {
                  "type" : "integer",
                  "description" : "The HTTP status code for this occurrence of the problem. The HTTP status code ([RFC7231], Section 6) generated by the origin server for this occurrence of the problem.\n"
                },
                "detail" : {
                  "type" : "string",
                  "description" : "A human-readable explanation specific to this occurrence of the problem.\n"
                },
                "instance" : {
                  "type" : "string",
                  "format" : "URI",
                  "description" : "A URI reference that identifies the specific occurrence of the problem. It may yield further information if dereferenced.\n"
                }
              },
              "description" : "The definition of the general \"ProblemDetails\" data structure from IETF RFC 7807 [19] is reproduced inthis structure. Compared to the general framework defined in IETF RFC 7807 [19], the \"status\" and \"detail\" attributes are mandated to be included by the present document, to ensure that the response contains additional textual information about an error. IETF RFC 7807 [19] foresees extensibility of the \"ProblemDetails\" type. It is possible that particular APIs in the present document, or particular implementations, define extensions to define additional attributes that provide more information about the error. The description column only provides some explanation of the meaning to Facilitate understanding of the design. For a full description, see IETF RFC 7807 [19].\n"
            }
          },
          "404" : {
            "description" : "Not Found\nIf the API producer did not find a current representation for the resource addressed by the URI passed in the request, or is not willing to disclose that one exists, it shall respond with this response code.  Specifically in case of this task resource, the reason can also be that the task is not supported for the VNF LCM operation occurrence represented by the parent resource, and that the task resource consequently does not exist. The \"ProblemDetails\" structure may be provided, including in the \"detail\" attribute information about the sourceof the problem, e.g. a wrong resource URI variable.\n",
            "headers" : {
              "Content-Type" : {
                "type" : "string",
                "description" : "The MIME type of the body of the response."
              }
            },
            "schema" : {
              "type" : "object",
              "required" : [ "detail", "status" ],
              "properties" : {
                "type" : {
                  "type" : "string",
                  "format" : "URI",
                  "description" : "A URI reference according to IETF RFC 3986 [5] that identifies the problem type. It is encouraged that the URI provides human-readable documentation for the problem (e.g. using HTML) when dereferenced. When this member is not present, its value is assumed to be \"about:blank\".\n"
                },
                "title" : {
                  "type" : "string",
                  "description" : "A short, human-readable summary of the problem type. It should not change from occurrence to occurrence of the problem, except for purposes of localization. If type is given and other than \"about:blank\", this attribute shall also be provided. A short, human-readable summary of the problem type.  It SHOULD NOT change from occurrence to occurrence of the problem, except for purposes of localization (e.g., using proactive content negotiation; see [RFC7231], Section 3.4).\n"
                },
                "status" : {
                  "type" : "integer",
                  "description" : "The HTTP status code for this occurrence of the problem. The HTTP status code ([RFC7231], Section 6) generated by the origin server for this occurrence of the problem.\n"
                },
                "detail" : {
                  "type" : "string",
                  "description" : "A human-readable explanation specific to this occurrence of the problem.\n"
                },
                "instance" : {
                  "type" : "string",
                  "format" : "URI",
                  "description" : "A URI reference that identifies the specific occurrence of the problem. It may yield further information if dereferenced.\n"
                }
              },
              "description" : "The definition of the general \"ProblemDetails\" data structure from IETF RFC 7807 [19] is reproduced inthis structure. Compared to the general framework defined in IETF RFC 7807 [19], the \"status\" and \"detail\" attributes are mandated to be included by the present document, to ensure that the response contains additional textual information about an error. IETF RFC 7807 [19] foresees extensibility of the \"ProblemDetails\" type. It is possible that particular APIs in the present document, or particular implementations, define extensions to define additional attributes that provide more information about the error. The description column only provides some explanation of the meaning to Facilitate understanding of the design. For a full description, see IETF RFC 7807 [19].\n"
            }
          },
          "405" : {
            "description" : "Method Not Allowed\nIf a particular HTTP method is not supported for a particular resource, the API producer shall respond with this response code. The \"ProblemDetails\" structure may be omitted in that case.\n",
            "headers" : {
              "Content-Type" : {
                "type" : "string",
                "description" : "The MIME type of the body of the response."
              }
            },
            "schema" : {
              "type" : "object",
              "required" : [ "detail", "status" ],
              "properties" : {
                "type" : {
                  "type" : "string",
                  "format" : "URI",
                  "description" : "A URI reference according to IETF RFC 3986 [5] that identifies the problem type. It is encouraged that the URI provides human-readable documentation for the problem (e.g. using HTML) when dereferenced. When this member is not present, its value is assumed to be \"about:blank\".\n"
                },
                "title" : {
                  "type" : "string",
                  "description" : "A short, human-readable summary of the problem type. It should not change from occurrence to occurrence of the problem, except for purposes of localization. If type is given and other than \"about:blank\", this attribute shall also be provided. A short, human-readable summary of the problem type.  It SHOULD NOT change from occurrence to occurrence of the problem, except for purposes of localization (e.g., using proactive content negotiation; see [RFC7231], Section 3.4).\n"
                },
                "status" : {
                  "type" : "integer",
                  "description" : "The HTTP status code for this occurrence of the problem. The HTTP status code ([RFC7231], Section 6) generated by the origin server for this occurrence of the problem.\n"
                },
                "detail" : {
                  "type" : "string",
                  "description" : "A human-readable explanation specific to this occurrence of the problem.\n"
                },
                "instance" : {
                  "type" : "string",
                  "format" : "URI",
                  "description" : "A URI reference that identifies the specific occurrence of the problem. It may yield further information if dereferenced.\n"
                }
              },
              "description" : "The definition of the general \"ProblemDetails\" data structure from IETF RFC 7807 [19] is reproduced inthis structure. Compared to the general framework defined in IETF RFC 7807 [19], the \"status\" and \"detail\" attributes are mandated to be included by the present document, to ensure that the response contains additional textual information about an error. IETF RFC 7807 [19] foresees extensibility of the \"ProblemDetails\" type. It is possible that particular APIs in the present document, or particular implementations, define extensions to define additional attributes that provide more information about the error. The description column only provides some explanation of the meaning to Facilitate understanding of the design. For a full description, see IETF RFC 7807 [19].\n"
            }
          },
          "406" : {
            "description" : "Not Acceptable\nIf the \"Accept\" HTTP header does not contain at least one name of a content type that is acceptable to the API producer, the API producer shall respond with this response code. The \"ProblemDetails\" structure may be omitted in that case.        \n",
            "headers" : {
              "Content-Type" : {
                "type" : "string",
                "description" : "The MIME type of the body of the response."
              }
            },
            "schema" : {
              "type" : "object",
              "required" : [ "detail", "status" ],
              "properties" : {
                "type" : {
                  "type" : "string",
                  "format" : "URI",
                  "description" : "A URI reference according to IETF RFC 3986 [5] that identifies the problem type. It is encouraged that the URI provides human-readable documentation for the problem (e.g. using HTML) when dereferenced. When this member is not present, its value is assumed to be \"about:blank\".\n"
                },
                "title" : {
                  "type" : "string",
                  "description" : "A short, human-readable summary of the problem type. It should not change from occurrence to occurrence of the problem, except for purposes of localization. If type is given and other than \"about:blank\", this attribute shall also be provided. A short, human-readable summary of the problem type.  It SHOULD NOT change from occurrence to occurrence of the problem, except for purposes of localization (e.g., using proactive content negotiation; see [RFC7231], Section 3.4).\n"
                },
                "status" : {
                  "type" : "integer",
                  "description" : "The HTTP status code for this occurrence of the problem. The HTTP status code ([RFC7231], Section 6) generated by the origin server for this occurrence of the problem.\n"
                },
                "detail" : {
                  "type" : "string",
                  "description" : "A human-readable explanation specific to this occurrence of the problem.\n"
                },
                "instance" : {
                  "type" : "string",
                  "format" : "URI",
                  "description" : "A URI reference that identifies the specific occurrence of the problem. It may yield further information if dereferenced.\n"
                }
              },
              "description" : "The definition of the general \"ProblemDetails\" data structure from IETF RFC 7807 [19] is reproduced inthis structure. Compared to the general framework defined in IETF RFC 7807 [19], the \"status\" and \"detail\" attributes are mandated to be included by the present document, to ensure that the response contains additional textual information about an error. IETF RFC 7807 [19] foresees extensibility of the \"ProblemDetails\" type. It is possible that particular APIs in the present document, or particular implementations, define extensions to define additional attributes that provide more information about the error. The description column only provides some explanation of the meaning to Facilitate understanding of the design. For a full description, see IETF RFC 7807 [19].\n"
            }
          },
          "500" : {
            "description" : "Internal Server Error\nIf there is an application error not related to the client's input that cannot be easily mapped to any other HTTP response code (\"catch all error\"), the API producer shall respond withthis response code. The \"ProblemDetails\" structure shall be provided, and shall include in the \"detail\" attribute more information about the source of the problem.\n",
            "headers" : {
              "Content-Type" : {
                "type" : "string",
                "description" : "The MIME type of the body of the response."
              }
            },
            "schema" : {
              "type" : "object",
              "required" : [ "detail", "status" ],
              "properties" : {
                "type" : {
                  "type" : "string",
                  "format" : "URI",
                  "description" : "A URI reference according to IETF RFC 3986 [5] that identifies the problem type. It is encouraged that the URI provides human-readable documentation for the problem (e.g. using HTML) when dereferenced. When this member is not present, its value is assumed to be \"about:blank\".\n"
                },
                "title" : {
                  "type" : "string",
                  "description" : "A short, human-readable summary of the problem type. It should not change from occurrence to occurrence of the problem, except for purposes of localization. If type is given and other than \"about:blank\", this attribute shall also be provided. A short, human-readable summary of the problem type.  It SHOULD NOT change from occurrence to occurrence of the problem, except for purposes of localization (e.g., using proactive content negotiation; see [RFC7231], Section 3.4).\n"
                },
                "status" : {
                  "type" : "integer",
                  "description" : "The HTTP status code for this occurrence of the problem. The HTTP status code ([RFC7231], Section 6) generated by the origin server for this occurrence of the problem.\n"
                },
                "detail" : {
                  "type" : "string",
                  "description" : "A human-readable explanation specific to this occurrence of the problem.\n"
                },
                "instance" : {
                  "type" : "string",
                  "format" : "URI",
                  "description" : "A URI reference that identifies the specific occurrence of the problem. It may yield further information if dereferenced.\n"
                }
              },
              "description" : "The definition of the general \"ProblemDetails\" data structure from IETF RFC 7807 [19] is reproduced inthis structure. Compared to the general framework defined in IETF RFC 7807 [19], the \"status\" and \"detail\" attributes are mandated to be included by the present document, to ensure that the response contains additional textual information about an error. IETF RFC 7807 [19] foresees extensibility of the \"ProblemDetails\" type. It is possible that particular APIs in the present document, or particular implementations, define extensions to define additional attributes that provide more information about the error. The description column only provides some explanation of the meaning to Facilitate understanding of the design. For a full description, see IETF RFC 7807 [19].\n"
            }
          },
          "503" : {
            "description" : "Service Unavailable\nIf the API producer encounters an internal overload situation of itself or of a system it relies on, it should respond with this response code, following the provisions in IETF RFC 7231 [13] for the use of the \"Retry-After\" HTTP header and for the alternative to refuse the connection. The \"ProblemDetails\" structure may be omitted.\n",
            "headers" : {
              "Content-Type" : {
                "type" : "string",
                "description" : "The MIME type of the body of the response."
              }
            },
            "schema" : {
              "type" : "object",
              "required" : [ "detail", "status" ],
              "properties" : {
                "type" : {
                  "type" : "string",
                  "format" : "URI",
                  "description" : "A URI reference according to IETF RFC 3986 [5] that identifies the problem type. It is encouraged that the URI provides human-readable documentation for the problem (e.g. using HTML) when dereferenced. When this member is not present, its value is assumed to be \"about:blank\".\n"
                },
                "title" : {
                  "type" : "string",
                  "description" : "A short, human-readable summary of the problem type. It should not change from occurrence to occurrence of the problem, except for purposes of localization. If type is given and other than \"about:blank\", this attribute shall also be provided. A short, human-readable summary of the problem type.  It SHOULD NOT change from occurrence to occurrence of the problem, except for purposes of localization (e.g., using proactive content negotiation; see [RFC7231], Section 3.4).\n"
                },
                "status" : {
                  "type" : "integer",
                  "description" : "The HTTP status code for this occurrence of the problem. The HTTP status code ([RFC7231], Section 6) generated by the origin server for this occurrence of the problem.\n"
                },
                "detail" : {
                  "type" : "string",
                  "description" : "A human-readable explanation specific to this occurrence of the problem.\n"
                },
                "instance" : {
                  "type" : "string",
                  "format" : "URI",
                  "description" : "A URI reference that identifies the specific occurrence of the problem. It may yield further information if dereferenced.\n"
                }
              },
              "description" : "The definition of the general \"ProblemDetails\" data structure from IETF RFC 7807 [19] is reproduced inthis structure. Compared to the general framework defined in IETF RFC 7807 [19], the \"status\" and \"detail\" attributes are mandated to be included by the present document, to ensure that the response contains additional textual information about an error. IETF RFC 7807 [19] foresees extensibility of the \"ProblemDetails\" type. It is possible that particular APIs in the present document, or particular implementations, define extensions to define additional attributes that provide more information about the error. The description column only provides some explanation of the meaning to Facilitate understanding of the design. For a full description, see IETF RFC 7807 [19].\n"
            }
          }
        }
      }
    },
    "/lcn/VnfIdentifierCreationNotification" : {
      "post" : {
        "description" : "Notify\n\nThe POST method delivers a notification from the server to the client.\n",
        "parameters" : [ {
          "in" : "body",
          "name" : "VnfIdentifierCreationNotification",
          "description" : "A notification about the creation of a VNF identifier and the related VNF instance resource.\n",
          "required" : true,
          "schema" : {
            "$ref" : "#/definitions/VnfIdentifierCreationNotification"
          }
        }, {
          "name" : "Authorization",
          "in" : "header",
          "description" : "The authorization token for the request. Reference: IETF RFC 7235\n",
          "required" : false,
          "type" : "string"
        }, {
          "name" : "Content-Type",
          "in" : "header",
          "description" : "The MIME type of the body of the request. Reference: IETF RFC 7231\n",
          "required" : true,
          "type" : "string"
        } ],
        "responses" : {
          "204" : {
            "description" : "No Content\nThe notification was delivered successfully.\n",
            "headers" : {
              "WWW-Authenticate" : {
                "type" : "string",
                "description" : "Challenge if the corresponding HTTP request has not provided authorization, or error details if the corresponding HTTP request has provided an invalid authorization token.\n"
              }
            }
          },
          "400" : {
            "description" : "Bad Request\nIf the request is malformed or syntactically incorrect (e.g. if the request URI contains incorrect query parameters or a syntactically incorrect payload body), the API producer shall respond with this response code. The \"ProblemDetails\" structure shall be provided, and should include in the \"detail\" attribute more information about the source of the problem.\n\n ---\n\nIf the request contains a malformed access token, the API producer should respond with this response. The details of the error shall be returned in the WWW-Authenticate HTTP header, as defined in IETF RFC 6750 and IETF RFC 7235. The ProblemDetails structure may be provided.\n\n ---\n\nIf there is an application error related to the client's input that cannot be easily mapped to any other HTTP response code (\"catch all error\"), the API producer shall respond with this response code.The \"ProblemDetails\" structure shall be provided, and shall include in the \"detail\" attribute more information about the source of the problem.\n",
            "headers" : {
              "Content-Type" : {
                "type" : "string",
                "description" : "The MIME type of the body of the response."
              },
              "WWW-Authenticate" : {
                "type" : "string",
                "description" : "Challenge if the corresponding HTTP request has not provided authorization, or error details if the corresponding HTTP request has provided an invalid authorization token.\n"
              }
            },
            "schema" : {
              "type" : "object",
              "required" : [ "detail", "status" ],
              "properties" : {
                "type" : {
                  "type" : "string",
                  "format" : "URI",
                  "description" : "A URI reference according to IETF RFC 3986 [5] that identifies the problem type. It is encouraged that the URI provides human-readable documentation for the problem (e.g. using HTML) when dereferenced. When this member is not present, its value is assumed to be \"about:blank\".\n"
                },
                "title" : {
                  "type" : "string",
                  "description" : "A short, human-readable summary of the problem type. It should not change from occurrence to occurrence of the problem, except for purposes of localization. If type is given and other than \"about:blank\", this attribute shall also be provided. A short, human-readable summary of the problem type.  It SHOULD NOT change from occurrence to occurrence of the problem, except for purposes of localization (e.g., using proactive content negotiation; see [RFC7231], Section 3.4).\n"
                },
                "status" : {
                  "type" : "integer",
                  "description" : "The HTTP status code for this occurrence of the problem. The HTTP status code ([RFC7231], Section 6) generated by the origin server for this occurrence of the problem.\n"
                },
                "detail" : {
                  "type" : "string",
                  "description" : "A human-readable explanation specific to this occurrence of the problem.\n"
                },
                "instance" : {
                  "type" : "string",
                  "format" : "URI",
                  "description" : "A URI reference that identifies the specific occurrence of the problem. It may yield further information if dereferenced.\n"
                }
              },
              "description" : "The definition of the general \"ProblemDetails\" data structure from IETF RFC 7807 [19] is reproduced inthis structure. Compared to the general framework defined in IETF RFC 7807 [19], the \"status\" and \"detail\" attributes are mandated to be included by the present document, to ensure that the response contains additional textual information about an error. IETF RFC 7807 [19] foresees extensibility of the \"ProblemDetails\" type. It is possible that particular APIs in the present document, or particular implementations, define extensions to define additional attributes that provide more information about the error. The description column only provides some explanation of the meaning to Facilitate understanding of the design. For a full description, see IETF RFC 7807 [19].\n"
            }
          },
          "401" : {
            "description" : "Unauthorized\nIf the request contains no access token even though one is required, or if the request contains an authorization token that is invalid (e.g. expired or revoked), the API producer should respond with this response. The details of the error shall be returned in the WWW-Authenticate HTTP header, as defined in IETF RFC 6750 and IETF RFC 7235. The ProblemDetails structure may be provided.\n",
            "headers" : {
              "Content-Type" : {
                "type" : "string",
                "description" : "The MIME type of the body of the response."
              },
              "WWW-Authenticate" : {
                "type" : "string",
                "description" : "Challenge if the corresponding HTTP request has not provided authorization, or error details if the corresponding HTTP request has provided an invalid authorization token.\n"
              }
            },
            "schema" : {
              "type" : "object",
              "required" : [ "detail", "status" ],
              "properties" : {
                "type" : {
                  "type" : "string",
                  "format" : "URI",
                  "description" : "A URI reference according to IETF RFC 3986 [5] that identifies the problem type. It is encouraged that the URI provides human-readable documentation for the problem (e.g. using HTML) when dereferenced. When this member is not present, its value is assumed to be \"about:blank\".\n"
                },
                "title" : {
                  "type" : "string",
                  "description" : "A short, human-readable summary of the problem type. It should not change from occurrence to occurrence of the problem, except for purposes of localization. If type is given and other than \"about:blank\", this attribute shall also be provided. A short, human-readable summary of the problem type.  It SHOULD NOT change from occurrence to occurrence of the problem, except for purposes of localization (e.g., using proactive content negotiation; see [RFC7231], Section 3.4).\n"
                },
                "status" : {
                  "type" : "integer",
                  "description" : "The HTTP status code for this occurrence of the problem. The HTTP status code ([RFC7231], Section 6) generated by the origin server for this occurrence of the problem.\n"
                },
                "detail" : {
                  "type" : "string",
                  "description" : "A human-readable explanation specific to this occurrence of the problem.\n"
                },
                "instance" : {
                  "type" : "string",
                  "format" : "URI",
                  "description" : "A URI reference that identifies the specific occurrence of the problem. It may yield further information if dereferenced.\n"
                }
              },
              "description" : "The definition of the general \"ProblemDetails\" data structure from IETF RFC 7807 [19] is reproduced inthis structure. Compared to the general framework defined in IETF RFC 7807 [19], the \"status\" and \"detail\" attributes are mandated to be included by the present document, to ensure that the response contains additional textual information about an error. IETF RFC 7807 [19] foresees extensibility of the \"ProblemDetails\" type. It is possible that particular APIs in the present document, or particular implementations, define extensions to define additional attributes that provide more information about the error. The description column only provides some explanation of the meaning to Facilitate understanding of the design. For a full description, see IETF RFC 7807 [19].\n"
            }
          },
          "403" : {
            "description" : "Forbidden\nIf the API consumer is not allowed to perform a particular request to a particular resource, the API producer shall respond with this response code. The \"ProblemDetails\" structure shall be provided.  It should include in the \"detail\" attribute information about the source of the problem, and may indicate how to solve it.\n",
            "headers" : {
              "Content-Type" : {
                "type" : "string",
                "description" : "The MIME type of the body of the response."
              }
            },
            "schema" : {
              "type" : "object",
              "required" : [ "detail", "status" ],
              "properties" : {
                "type" : {
                  "type" : "string",
                  "format" : "URI",
                  "description" : "A URI reference according to IETF RFC 3986 [5] that identifies the problem type. It is encouraged that the URI provides human-readable documentation for the problem (e.g. using HTML) when dereferenced. When this member is not present, its value is assumed to be \"about:blank\".\n"
                },
                "title" : {
                  "type" : "string",
                  "description" : "A short, human-readable summary of the problem type. It should not change from occurrence to occurrence of the problem, except for purposes of localization. If type is given and other than \"about:blank\", this attribute shall also be provided. A short, human-readable summary of the problem type.  It SHOULD NOT change from occurrence to occurrence of the problem, except for purposes of localization (e.g., using proactive content negotiation; see [RFC7231], Section 3.4).\n"
                },
                "status" : {
                  "type" : "integer",
                  "description" : "The HTTP status code for this occurrence of the problem. The HTTP status code ([RFC7231], Section 6) generated by the origin server for this occurrence of the problem.\n"
                },
                "detail" : {
                  "type" : "string",
                  "description" : "A human-readable explanation specific to this occurrence of the problem.\n"
                },
                "instance" : {
                  "type" : "string",
                  "format" : "URI",
                  "description" : "A URI reference that identifies the specific occurrence of the problem. It may yield further information if dereferenced.\n"
                }
              },
              "description" : "The definition of the general \"ProblemDetails\" data structure from IETF RFC 7807 [19] is reproduced inthis structure. Compared to the general framework defined in IETF RFC 7807 [19], the \"status\" and \"detail\" attributes are mandated to be included by the present document, to ensure that the response contains additional textual information about an error. IETF RFC 7807 [19] foresees extensibility of the \"ProblemDetails\" type. It is possible that particular APIs in the present document, or particular implementations, define extensions to define additional attributes that provide more information about the error. The description column only provides some explanation of the meaning to Facilitate understanding of the design. For a full description, see IETF RFC 7807 [19].\n"
            }
          },
          "404" : {
            "description" : "Not Found\nIf the API producer did not find a current representation for the resource addressed by the URI passed in the request, or is not willing to disclose that one exists, it shall respond with this response code.  Specifically in case of this task resource, the reason can also be that the task is not supported for the VNF LCM operation occurrence represented by the parent resource, and that the task resource consequently does not exist. The \"ProblemDetails\" structure may be provided, including in the \"detail\" attribute information about the sourceof the problem, e.g. a wrong resource URI variable.\n",
            "headers" : {
              "Content-Type" : {
                "type" : "string",
                "description" : "The MIME type of the body of the response."
              }
            },
            "schema" : {
              "type" : "object",
              "required" : [ "detail", "status" ],
              "properties" : {
                "type" : {
                  "type" : "string",
                  "format" : "URI",
                  "description" : "A URI reference according to IETF RFC 3986 [5] that identifies the problem type. It is encouraged that the URI provides human-readable documentation for the problem (e.g. using HTML) when dereferenced. When this member is not present, its value is assumed to be \"about:blank\".\n"
                },
                "title" : {
                  "type" : "string",
                  "description" : "A short, human-readable summary of the problem type. It should not change from occurrence to occurrence of the problem, except for purposes of localization. If type is given and other than \"about:blank\", this attribute shall also be provided. A short, human-readable summary of the problem type.  It SHOULD NOT change from occurrence to occurrence of the problem, except for purposes of localization (e.g., using proactive content negotiation; see [RFC7231], Section 3.4).\n"
                },
                "status" : {
                  "type" : "integer",
                  "description" : "The HTTP status code for this occurrence of the problem. The HTTP status code ([RFC7231], Section 6) generated by the origin server for this occurrence of the problem.\n"
                },
                "detail" : {
                  "type" : "string",
                  "description" : "A human-readable explanation specific to this occurrence of the problem.\n"
                },
                "instance" : {
                  "type" : "string",
                  "format" : "URI",
                  "description" : "A URI reference that identifies the specific occurrence of the problem. It may yield further information if dereferenced.\n"
                }
              },
              "description" : "The definition of the general \"ProblemDetails\" data structure from IETF RFC 7807 [19] is reproduced inthis structure. Compared to the general framework defined in IETF RFC 7807 [19], the \"status\" and \"detail\" attributes are mandated to be included by the present document, to ensure that the response contains additional textual information about an error. IETF RFC 7807 [19] foresees extensibility of the \"ProblemDetails\" type. It is possible that particular APIs in the present document, or particular implementations, define extensions to define additional attributes that provide more information about the error. The description column only provides some explanation of the meaning to Facilitate understanding of the design. For a full description, see IETF RFC 7807 [19].\n"
            }
          },
          "405" : {
            "description" : "Method Not Allowed\nIf a particular HTTP method is not supported for a particular resource, the API producer shall respond with this response code. The \"ProblemDetails\" structure may be omitted in that case.\n",
            "headers" : {
              "Content-Type" : {
                "type" : "string",
                "description" : "The MIME type of the body of the response."
              }
            },
            "schema" : {
              "type" : "object",
              "required" : [ "detail", "status" ],
              "properties" : {
                "type" : {
                  "type" : "string",
                  "format" : "URI",
                  "description" : "A URI reference according to IETF RFC 3986 [5] that identifies the problem type. It is encouraged that the URI provides human-readable documentation for the problem (e.g. using HTML) when dereferenced. When this member is not present, its value is assumed to be \"about:blank\".\n"
                },
                "title" : {
                  "type" : "string",
                  "description" : "A short, human-readable summary of the problem type. It should not change from occurrence to occurrence of the problem, except for purposes of localization. If type is given and other than \"about:blank\", this attribute shall also be provided. A short, human-readable summary of the problem type.  It SHOULD NOT change from occurrence to occurrence of the problem, except for purposes of localization (e.g., using proactive content negotiation; see [RFC7231], Section 3.4).\n"
                },
                "status" : {
                  "type" : "integer",
                  "description" : "The HTTP status code for this occurrence of the problem. The HTTP status code ([RFC7231], Section 6) generated by the origin server for this occurrence of the problem.\n"
                },
                "detail" : {
                  "type" : "string",
                  "description" : "A human-readable explanation specific to this occurrence of the problem.\n"
                },
                "instance" : {
                  "type" : "string",
                  "format" : "URI",
                  "description" : "A URI reference that identifies the specific occurrence of the problem. It may yield further information if dereferenced.\n"
                }
              },
              "description" : "The definition of the general \"ProblemDetails\" data structure from IETF RFC 7807 [19] is reproduced inthis structure. Compared to the general framework defined in IETF RFC 7807 [19], the \"status\" and \"detail\" attributes are mandated to be included by the present document, to ensure that the response contains additional textual information about an error. IETF RFC 7807 [19] foresees extensibility of the \"ProblemDetails\" type. It is possible that particular APIs in the present document, or particular implementations, define extensions to define additional attributes that provide more information about the error. The description column only provides some explanation of the meaning to Facilitate understanding of the design. For a full description, see IETF RFC 7807 [19].\n"
            }
          },
          "406" : {
            "description" : "Not Acceptable\nIf the \"Accept\" HTTP header does not contain at least one name of a content type that is acceptable to the API producer, the API producer shall respond with this response code. The \"ProblemDetails\" structure may be omitted in that case.        \n",
            "headers" : {
              "Content-Type" : {
                "type" : "string",
                "description" : "The MIME type of the body of the response."
              }
            },
            "schema" : {
              "type" : "object",
              "required" : [ "detail", "status" ],
              "properties" : {
                "type" : {
                  "type" : "string",
                  "format" : "URI",
                  "description" : "A URI reference according to IETF RFC 3986 [5] that identifies the problem type. It is encouraged that the URI provides human-readable documentation for the problem (e.g. using HTML) when dereferenced. When this member is not present, its value is assumed to be \"about:blank\".\n"
                },
                "title" : {
                  "type" : "string",
                  "description" : "A short, human-readable summary of the problem type. It should not change from occurrence to occurrence of the problem, except for purposes of localization. If type is given and other than \"about:blank\", this attribute shall also be provided. A short, human-readable summary of the problem type.  It SHOULD NOT change from occurrence to occurrence of the problem, except for purposes of localization (e.g., using proactive content negotiation; see [RFC7231], Section 3.4).\n"
                },
                "status" : {
                  "type" : "integer",
                  "description" : "The HTTP status code for this occurrence of the problem. The HTTP status code ([RFC7231], Section 6) generated by the origin server for this occurrence of the problem.\n"
                },
                "detail" : {
                  "type" : "string",
                  "description" : "A human-readable explanation specific to this occurrence of the problem.\n"
                },
                "instance" : {
                  "type" : "string",
                  "format" : "URI",
                  "description" : "A URI reference that identifies the specific occurrence of the problem. It may yield further information if dereferenced.\n"
                }
              },
              "description" : "The definition of the general \"ProblemDetails\" data structure from IETF RFC 7807 [19] is reproduced inthis structure. Compared to the general framework defined in IETF RFC 7807 [19], the \"status\" and \"detail\" attributes are mandated to be included by the present document, to ensure that the response contains additional textual information about an error. IETF RFC 7807 [19] foresees extensibility of the \"ProblemDetails\" type. It is possible that particular APIs in the present document, or particular implementations, define extensions to define additional attributes that provide more information about the error. The description column only provides some explanation of the meaning to Facilitate understanding of the design. For a full description, see IETF RFC 7807 [19].\n"
            }
          },
          "500" : {
            "description" : "Internal Server Error\nIf there is an application error not related to the client's input that cannot be easily mapped to any other HTTP response code (\"catch all error\"), the API producer shall respond withthis response code. The \"ProblemDetails\" structure shall be provided, and shall include in the \"detail\" attribute more information about the source of the problem.\n",
            "headers" : {
              "Content-Type" : {
                "type" : "string",
                "description" : "The MIME type of the body of the response."
              }
            },
            "schema" : {
              "type" : "object",
              "required" : [ "detail", "status" ],
              "properties" : {
                "type" : {
                  "type" : "string",
                  "format" : "URI",
                  "description" : "A URI reference according to IETF RFC 3986 [5] that identifies the problem type. It is encouraged that the URI provides human-readable documentation for the problem (e.g. using HTML) when dereferenced. When this member is not present, its value is assumed to be \"about:blank\".\n"
                },
                "title" : {
                  "type" : "string",
                  "description" : "A short, human-readable summary of the problem type. It should not change from occurrence to occurrence of the problem, except for purposes of localization. If type is given and other than \"about:blank\", this attribute shall also be provided. A short, human-readable summary of the problem type.  It SHOULD NOT change from occurrence to occurrence of the problem, except for purposes of localization (e.g., using proactive content negotiation; see [RFC7231], Section 3.4).\n"
                },
                "status" : {
                  "type" : "integer",
                  "description" : "The HTTP status code for this occurrence of the problem. The HTTP status code ([RFC7231], Section 6) generated by the origin server for this occurrence of the problem.\n"
                },
                "detail" : {
                  "type" : "string",
                  "description" : "A human-readable explanation specific to this occurrence of the problem.\n"
                },
                "instance" : {
                  "type" : "string",
                  "format" : "URI",
                  "description" : "A URI reference that identifies the specific occurrence of the problem. It may yield further information if dereferenced.\n"
                }
              },
              "description" : "The definition of the general \"ProblemDetails\" data structure from IETF RFC 7807 [19] is reproduced inthis structure. Compared to the general framework defined in IETF RFC 7807 [19], the \"status\" and \"detail\" attributes are mandated to be included by the present document, to ensure that the response contains additional textual information about an error. IETF RFC 7807 [19] foresees extensibility of the \"ProblemDetails\" type. It is possible that particular APIs in the present document, or particular implementations, define extensions to define additional attributes that provide more information about the error. The description column only provides some explanation of the meaning to Facilitate understanding of the design. For a full description, see IETF RFC 7807 [19].\n"
            }
          },
          "503" : {
            "description" : "Service Unavailable\nIf the API producer encounters an internal overload situation of itself or of a system it relies on, it should respond with this response code, following the provisions in IETF RFC 7231 [13] for the use of the \"Retry-After\" HTTP header and for the alternative to refuse the connection. The \"ProblemDetails\" structure may be omitted.\n",
            "headers" : {
              "Content-Type" : {
                "type" : "string",
                "description" : "The MIME type of the body of the response."
              }
            },
            "schema" : {
              "type" : "object",
              "required" : [ "detail", "status" ],
              "properties" : {
                "type" : {
                  "type" : "string",
                  "format" : "URI",
                  "description" : "A URI reference according to IETF RFC 3986 [5] that identifies the problem type. It is encouraged that the URI provides human-readable documentation for the problem (e.g. using HTML) when dereferenced. When this member is not present, its value is assumed to be \"about:blank\".\n"
                },
                "title" : {
                  "type" : "string",
                  "description" : "A short, human-readable summary of the problem type. It should not change from occurrence to occurrence of the problem, except for purposes of localization. If type is given and other than \"about:blank\", this attribute shall also be provided. A short, human-readable summary of the problem type.  It SHOULD NOT change from occurrence to occurrence of the problem, except for purposes of localization (e.g., using proactive content negotiation; see [RFC7231], Section 3.4).\n"
                },
                "status" : {
                  "type" : "integer",
                  "description" : "The HTTP status code for this occurrence of the problem. The HTTP status code ([RFC7231], Section 6) generated by the origin server for this occurrence of the problem.\n"
                },
                "detail" : {
                  "type" : "string",
                  "description" : "A human-readable explanation specific to this occurrence of the problem.\n"
                },
                "instance" : {
                  "type" : "string",
                  "format" : "URI",
                  "description" : "A URI reference that identifies the specific occurrence of the problem. It may yield further information if dereferenced.\n"
                }
              },
              "description" : "The definition of the general \"ProblemDetails\" data structure from IETF RFC 7807 [19] is reproduced inthis structure. Compared to the general framework defined in IETF RFC 7807 [19], the \"status\" and \"detail\" attributes are mandated to be included by the present document, to ensure that the response contains additional textual information about an error. IETF RFC 7807 [19] foresees extensibility of the \"ProblemDetails\" type. It is possible that particular APIs in the present document, or particular implementations, define extensions to define additional attributes that provide more information about the error. The description column only provides some explanation of the meaning to Facilitate understanding of the design. For a full description, see IETF RFC 7807 [19].\n"
            }
          }
        }
      }
    },
    "/lcn/VnfIdentifierDeletionNotification" : {
      "post" : {
        "description" : "Notify\n\nThe POST method delivers a notification from the server to the client.\n",
        "parameters" : [ {
          "in" : "body",
          "name" : "VnfIdentifierDeletionNotification",
          "description" : "A notification about the deletion of a VNF identifier and the related VNF instance resource.\n",
          "required" : true,
          "schema" : {
            "$ref" : "#/definitions/VnfIdentifierDeletionNotification"
          }
        }, {
          "name" : "Authorization",
          "in" : "header",
          "description" : "The authorization token for the request. Reference: IETF RFC 7235\n",
          "required" : false,
          "type" : "string"
        }, {
          "name" : "Content-Type",
          "in" : "header",
          "description" : "The MIME type of the body of the request. Reference: IETF RFC 7231\n",
          "required" : true,
          "type" : "string"
        } ],
        "responses" : {
          "204" : {
            "description" : "No Content\nThe notification was delivered successfully.\n",
            "headers" : {
              "WWW-Authenticate" : {
                "type" : "string",
                "description" : "Challenge if the corresponding HTTP request has not provided authorization, or error details if the corresponding HTTP request has provided an invalid authorization token.\n"
              }
            }
          },
          "400" : {
            "description" : "Bad Request\nIf the request is malformed or syntactically incorrect (e.g. if the request URI contains incorrect query parameters or a syntactically incorrect payload body), the API producer shall respond with this response code. The \"ProblemDetails\" structure shall be provided, and should include in the \"detail\" attribute more information about the source of the problem.\n\n ---\n\nIf the request contains a malformed access token, the API producer should respond with this response. The details of the error shall be returned in the WWW-Authenticate HTTP header, as defined in IETF RFC 6750 and IETF RFC 7235. The ProblemDetails structure may be provided.\n\n ---\n\nIf there is an application error related to the client's input that cannot be easily mapped to any other HTTP response code (\"catch all error\"), the API producer shall respond with this response code.The \"ProblemDetails\" structure shall be provided, and shall include in the \"detail\" attribute more information about the source of the problem.\n",
            "headers" : {
              "Content-Type" : {
                "type" : "string",
                "description" : "The MIME type of the body of the response."
              },
              "WWW-Authenticate" : {
                "type" : "string",
                "description" : "Challenge if the corresponding HTTP request has not provided authorization, or error details if the corresponding HTTP request has provided an invalid authorization token.\n"
              }
            },
            "schema" : {
              "type" : "object",
              "required" : [ "detail", "status" ],
              "properties" : {
                "type" : {
                  "type" : "string",
                  "format" : "URI",
                  "description" : "A URI reference according to IETF RFC 3986 [5] that identifies the problem type. It is encouraged that the URI provides human-readable documentation for the problem (e.g. using HTML) when dereferenced. When this member is not present, its value is assumed to be \"about:blank\".\n"
                },
                "title" : {
                  "type" : "string",
                  "description" : "A short, human-readable summary of the problem type. It should not change from occurrence to occurrence of the problem, except for purposes of localization. If type is given and other than \"about:blank\", this attribute shall also be provided. A short, human-readable summary of the problem type.  It SHOULD NOT change from occurrence to occurrence of the problem, except for purposes of localization (e.g., using proactive content negotiation; see [RFC7231], Section 3.4).\n"
                },
                "status" : {
                  "type" : "integer",
                  "description" : "The HTTP status code for this occurrence of the problem. The HTTP status code ([RFC7231], Section 6) generated by the origin server for this occurrence of the problem.\n"
                },
                "detail" : {
                  "type" : "string",
                  "description" : "A human-readable explanation specific to this occurrence of the problem.\n"
                },
                "instance" : {
                  "type" : "string",
                  "format" : "URI",
                  "description" : "A URI reference that identifies the specific occurrence of the problem. It may yield further information if dereferenced.\n"
                }
              },
              "description" : "The definition of the general \"ProblemDetails\" data structure from IETF RFC 7807 [19] is reproduced inthis structure. Compared to the general framework defined in IETF RFC 7807 [19], the \"status\" and \"detail\" attributes are mandated to be included by the present document, to ensure that the response contains additional textual information about an error. IETF RFC 7807 [19] foresees extensibility of the \"ProblemDetails\" type. It is possible that particular APIs in the present document, or particular implementations, define extensions to define additional attributes that provide more information about the error. The description column only provides some explanation of the meaning to Facilitate understanding of the design. For a full description, see IETF RFC 7807 [19].\n"
            }
          },
          "401" : {
            "description" : "Unauthorized\nIf the request contains no access token even though one is required, or if the request contains an authorization token that is invalid (e.g. expired or revoked), the API producer should respond with this response. The details of the error shall be returned in the WWW-Authenticate HTTP header, as defined in IETF RFC 6750 and IETF RFC 7235. The ProblemDetails structure may be provided.\n",
            "headers" : {
              "Content-Type" : {
                "type" : "string",
                "description" : "The MIME type of the body of the response."
              },
              "WWW-Authenticate" : {
                "type" : "string",
                "description" : "Challenge if the corresponding HTTP request has not provided authorization, or error details if the corresponding HTTP request has provided an invalid authorization token.\n"
              }
            },
            "schema" : {
              "type" : "object",
              "required" : [ "detail", "status" ],
              "properties" : {
                "type" : {
                  "type" : "string",
                  "format" : "URI",
                  "description" : "A URI reference according to IETF RFC 3986 [5] that identifies the problem type. It is encouraged that the URI provides human-readable documentation for the problem (e.g. using HTML) when dereferenced. When this member is not present, its value is assumed to be \"about:blank\".\n"
                },
                "title" : {
                  "type" : "string",
                  "description" : "A short, human-readable summary of the problem type. It should not change from occurrence to occurrence of the problem, except for purposes of localization. If type is given and other than \"about:blank\", this attribute shall also be provided. A short, human-readable summary of the problem type.  It SHOULD NOT change from occurrence to occurrence of the problem, except for purposes of localization (e.g., using proactive content negotiation; see [RFC7231], Section 3.4).\n"
                },
                "status" : {
                  "type" : "integer",
                  "description" : "The HTTP status code for this occurrence of the problem. The HTTP status code ([RFC7231], Section 6) generated by the origin server for this occurrence of the problem.\n"
                },
                "detail" : {
                  "type" : "string",
                  "description" : "A human-readable explanation specific to this occurrence of the problem.\n"
                },
                "instance" : {
                  "type" : "string",
                  "format" : "URI",
                  "description" : "A URI reference that identifies the specific occurrence of the problem. It may yield further information if dereferenced.\n"
                }
              },
              "description" : "The definition of the general \"ProblemDetails\" data structure from IETF RFC 7807 [19] is reproduced inthis structure. Compared to the general framework defined in IETF RFC 7807 [19], the \"status\" and \"detail\" attributes are mandated to be included by the present document, to ensure that the response contains additional textual information about an error. IETF RFC 7807 [19] foresees extensibility of the \"ProblemDetails\" type. It is possible that particular APIs in the present document, or particular implementations, define extensions to define additional attributes that provide more information about the error. The description column only provides some explanation of the meaning to Facilitate understanding of the design. For a full description, see IETF RFC 7807 [19].\n"
            }
          },
          "403" : {
            "description" : "Forbidden\nIf the API consumer is not allowed to perform a particular request to a particular resource, the API producer shall respond with this response code. The \"ProblemDetails\" structure shall be provided.  It should include in the \"detail\" attribute information about the source of the problem, and may indicate how to solve it.\n",
            "headers" : {
              "Content-Type" : {
                "type" : "string",
                "description" : "The MIME type of the body of the response."
              }
            },
            "schema" : {
              "type" : "object",
              "required" : [ "detail", "status" ],
              "properties" : {
                "type" : {
                  "type" : "string",
                  "format" : "URI",
                  "description" : "A URI reference according to IETF RFC 3986 [5] that identifies the problem type. It is encouraged that the URI provides human-readable documentation for the problem (e.g. using HTML) when dereferenced. When this member is not present, its value is assumed to be \"about:blank\".\n"
                },
                "title" : {
                  "type" : "string",
                  "description" : "A short, human-readable summary of the problem type. It should not change from occurrence to occurrence of the problem, except for purposes of localization. If type is given and other than \"about:blank\", this attribute shall also be provided. A short, human-readable summary of the problem type.  It SHOULD NOT change from occurrence to occurrence of the problem, except for purposes of localization (e.g., using proactive content negotiation; see [RFC7231], Section 3.4).\n"
                },
                "status" : {
                  "type" : "integer",
                  "description" : "The HTTP status code for this occurrence of the problem. The HTTP status code ([RFC7231], Section 6) generated by the origin server for this occurrence of the problem.\n"
                },
                "detail" : {
                  "type" : "string",
                  "description" : "A human-readable explanation specific to this occurrence of the problem.\n"
                },
                "instance" : {
                  "type" : "string",
                  "format" : "URI",
                  "description" : "A URI reference that identifies the specific occurrence of the problem. It may yield further information if dereferenced.\n"
                }
              },
              "description" : "The definition of the general \"ProblemDetails\" data structure from IETF RFC 7807 [19] is reproduced inthis structure. Compared to the general framework defined in IETF RFC 7807 [19], the \"status\" and \"detail\" attributes are mandated to be included by the present document, to ensure that the response contains additional textual information about an error. IETF RFC 7807 [19] foresees extensibility of the \"ProblemDetails\" type. It is possible that particular APIs in the present document, or particular implementations, define extensions to define additional attributes that provide more information about the error. The description column only provides some explanation of the meaning to Facilitate understanding of the design. For a full description, see IETF RFC 7807 [19].\n"
            }
          },
          "404" : {
            "description" : "Not Found\nIf the API producer did not find a current representation for the resource addressed by the URI passed in the request, or is not willing to disclose that one exists, it shall respond with this response code.  Specifically in case of this task resource, the reason can also be that the task is not supported for the VNF LCM operation occurrence represented by the parent resource, and that the task resource consequently does not exist. The \"ProblemDetails\" structure may be provided, including in the \"detail\" attribute information about the sourceof the problem, e.g. a wrong resource URI variable.\n",
            "headers" : {
              "Content-Type" : {
                "type" : "string",
                "description" : "The MIME type of the body of the response."
              }
            },
            "schema" : {
              "type" : "object",
              "required" : [ "detail", "status" ],
              "properties" : {
                "type" : {
                  "type" : "string",
                  "format" : "URI",
                  "description" : "A URI reference according to IETF RFC 3986 [5] that identifies the problem type. It is encouraged that the URI provides human-readable documentation for the problem (e.g. using HTML) when dereferenced. When this member is not present, its value is assumed to be \"about:blank\".\n"
                },
                "title" : {
                  "type" : "string",
                  "description" : "A short, human-readable summary of the problem type. It should not change from occurrence to occurrence of the problem, except for purposes of localization. If type is given and other than \"about:blank\", this attribute shall also be provided. A short, human-readable summary of the problem type.  It SHOULD NOT change from occurrence to occurrence of the problem, except for purposes of localization (e.g., using proactive content negotiation; see [RFC7231], Section 3.4).\n"
                },
                "status" : {
                  "type" : "integer",
                  "description" : "The HTTP status code for this occurrence of the problem. The HTTP status code ([RFC7231], Section 6) generated by the origin server for this occurrence of the problem.\n"
                },
                "detail" : {
                  "type" : "string",
                  "description" : "A human-readable explanation specific to this occurrence of the problem.\n"
                },
                "instance" : {
                  "type" : "string",
                  "format" : "URI",
                  "description" : "A URI reference that identifies the specific occurrence of the problem. It may yield further information if dereferenced.\n"
                }
              },
              "description" : "The definition of the general \"ProblemDetails\" data structure from IETF RFC 7807 [19] is reproduced inthis structure. Compared to the general framework defined in IETF RFC 7807 [19], the \"status\" and \"detail\" attributes are mandated to be included by the present document, to ensure that the response contains additional textual information about an error. IETF RFC 7807 [19] foresees extensibility of the \"ProblemDetails\" type. It is possible that particular APIs in the present document, or particular implementations, define extensions to define additional attributes that provide more information about the error. The description column only provides some explanation of the meaning to Facilitate understanding of the design. For a full description, see IETF RFC 7807 [19].\n"
            }
          },
          "405" : {
            "description" : "Method Not Allowed\nIf a particular HTTP method is not supported for a particular resource, the API producer shall respond with this response code. The \"ProblemDetails\" structure may be omitted in that case.\n",
            "headers" : {
              "Content-Type" : {
                "type" : "string",
                "description" : "The MIME type of the body of the response."
              }
            },
            "schema" : {
              "type" : "object",
              "required" : [ "detail", "status" ],
              "properties" : {
                "type" : {
                  "type" : "string",
                  "format" : "URI",
                  "description" : "A URI reference according to IETF RFC 3986 [5] that identifies the problem type. It is encouraged that the URI provides human-readable documentation for the problem (e.g. using HTML) when dereferenced. When this member is not present, its value is assumed to be \"about:blank\".\n"
                },
                "title" : {
                  "type" : "string",
                  "description" : "A short, human-readable summary of the problem type. It should not change from occurrence to occurrence of the problem, except for purposes of localization. If type is given and other than \"about:blank\", this attribute shall also be provided. A short, human-readable summary of the problem type.  It SHOULD NOT change from occurrence to occurrence of the problem, except for purposes of localization (e.g., using proactive content negotiation; see [RFC7231], Section 3.4).\n"
                },
                "status" : {
                  "type" : "integer",
                  "description" : "The HTTP status code for this occurrence of the problem. The HTTP status code ([RFC7231], Section 6) generated by the origin server for this occurrence of the problem.\n"
                },
                "detail" : {
                  "type" : "string",
                  "description" : "A human-readable explanation specific to this occurrence of the problem.\n"
                },
                "instance" : {
                  "type" : "string",
                  "format" : "URI",
                  "description" : "A URI reference that identifies the specific occurrence of the problem. It may yield further information if dereferenced.\n"
                }
              },
              "description" : "The definition of the general \"ProblemDetails\" data structure from IETF RFC 7807 [19] is reproduced inthis structure. Compared to the general framework defined in IETF RFC 7807 [19], the \"status\" and \"detail\" attributes are mandated to be included by the present document, to ensure that the response contains additional textual information about an error. IETF RFC 7807 [19] foresees extensibility of the \"ProblemDetails\" type. It is possible that particular APIs in the present document, or particular implementations, define extensions to define additional attributes that provide more information about the error. The description column only provides some explanation of the meaning to Facilitate understanding of the design. For a full description, see IETF RFC 7807 [19].\n"
            }
          },
          "406" : {
            "description" : "Not Acceptable\nIf the \"Accept\" HTTP header does not contain at least one name of a content type that is acceptable to the API producer, the API producer shall respond with this response code. The \"ProblemDetails\" structure may be omitted in that case.        \n",
            "headers" : {
              "Content-Type" : {
                "type" : "string",
                "description" : "The MIME type of the body of the response."
              }
            },
            "schema" : {
              "type" : "object",
              "required" : [ "detail", "status" ],
              "properties" : {
                "type" : {
                  "type" : "string",
                  "format" : "URI",
                  "description" : "A URI reference according to IETF RFC 3986 [5] that identifies the problem type. It is encouraged that the URI provides human-readable documentation for the problem (e.g. using HTML) when dereferenced. When this member is not present, its value is assumed to be \"about:blank\".\n"
                },
                "title" : {
                  "type" : "string",
                  "description" : "A short, human-readable summary of the problem type. It should not change from occurrence to occurrence of the problem, except for purposes of localization. If type is given and other than \"about:blank\", this attribute shall also be provided. A short, human-readable summary of the problem type.  It SHOULD NOT change from occurrence to occurrence of the problem, except for purposes of localization (e.g., using proactive content negotiation; see [RFC7231], Section 3.4).\n"
                },
                "status" : {
                  "type" : "integer",
                  "description" : "The HTTP status code for this occurrence of the problem. The HTTP status code ([RFC7231], Section 6) generated by the origin server for this occurrence of the problem.\n"
                },
                "detail" : {
                  "type" : "string",
                  "description" : "A human-readable explanation specific to this occurrence of the problem.\n"
                },
                "instance" : {
                  "type" : "string",
                  "format" : "URI",
                  "description" : "A URI reference that identifies the specific occurrence of the problem. It may yield further information if dereferenced.\n"
                }
              },
              "description" : "The definition of the general \"ProblemDetails\" data structure from IETF RFC 7807 [19] is reproduced inthis structure. Compared to the general framework defined in IETF RFC 7807 [19], the \"status\" and \"detail\" attributes are mandated to be included by the present document, to ensure that the response contains additional textual information about an error. IETF RFC 7807 [19] foresees extensibility of the \"ProblemDetails\" type. It is possible that particular APIs in the present document, or particular implementations, define extensions to define additional attributes that provide more information about the error. The description column only provides some explanation of the meaning to Facilitate understanding of the design. For a full description, see IETF RFC 7807 [19].\n"
            }
          },
          "500" : {
            "description" : "Internal Server Error\nIf there is an application error not related to the client's input that cannot be easily mapped to any other HTTP response code (\"catch all error\"), the API producer shall respond withthis response code. The \"ProblemDetails\" structure shall be provided, and shall include in the \"detail\" attribute more information about the source of the problem.\n",
            "headers" : {
              "Content-Type" : {
                "type" : "string",
                "description" : "The MIME type of the body of the response."
              }
            },
            "schema" : {
              "type" : "object",
              "required" : [ "detail", "status" ],
              "properties" : {
                "type" : {
                  "type" : "string",
                  "format" : "URI",
                  "description" : "A URI reference according to IETF RFC 3986 [5] that identifies the problem type. It is encouraged that the URI provides human-readable documentation for the problem (e.g. using HTML) when dereferenced. When this member is not present, its value is assumed to be \"about:blank\".\n"
                },
                "title" : {
                  "type" : "string",
                  "description" : "A short, human-readable summary of the problem type. It should not change from occurrence to occurrence of the problem, except for purposes of localization. If type is given and other than \"about:blank\", this attribute shall also be provided. A short, human-readable summary of the problem type.  It SHOULD NOT change from occurrence to occurrence of the problem, except for purposes of localization (e.g., using proactive content negotiation; see [RFC7231], Section 3.4).\n"
                },
                "status" : {
                  "type" : "integer",
                  "description" : "The HTTP status code for this occurrence of the problem. The HTTP status code ([RFC7231], Section 6) generated by the origin server for this occurrence of the problem.\n"
                },
                "detail" : {
                  "type" : "string",
                  "description" : "A human-readable explanation specific to this occurrence of the problem.\n"
                },
                "instance" : {
                  "type" : "string",
                  "format" : "URI",
                  "description" : "A URI reference that identifies the specific occurrence of the problem. It may yield further information if dereferenced.\n"
                }
              },
              "description" : "The definition of the general \"ProblemDetails\" data structure from IETF RFC 7807 [19] is reproduced inthis structure. Compared to the general framework defined in IETF RFC 7807 [19], the \"status\" and \"detail\" attributes are mandated to be included by the present document, to ensure that the response contains additional textual information about an error. IETF RFC 7807 [19] foresees extensibility of the \"ProblemDetails\" type. It is possible that particular APIs in the present document, or particular implementations, define extensions to define additional attributes that provide more information about the error. The description column only provides some explanation of the meaning to Facilitate understanding of the design. For a full description, see IETF RFC 7807 [19].\n"
            }
          },
          "503" : {
            "description" : "Service Unavailable\nIf the API producer encounters an internal overload situation of itself or of a system it relies on, it should respond with this response code, following the provisions in IETF RFC 7231 [13] for the use of the \"Retry-After\" HTTP header and for the alternative to refuse the connection. The \"ProblemDetails\" structure may be omitted.\n",
            "headers" : {
              "Content-Type" : {
                "type" : "string",
                "description" : "The MIME type of the body of the response."
              }
            },
            "schema" : {
              "type" : "object",
              "required" : [ "detail", "status" ],
              "properties" : {
                "type" : {
                  "type" : "string",
                  "format" : "URI",
                  "description" : "A URI reference according to IETF RFC 3986 [5] that identifies the problem type. It is encouraged that the URI provides human-readable documentation for the problem (e.g. using HTML) when dereferenced. When this member is not present, its value is assumed to be \"about:blank\".\n"
                },
                "title" : {
                  "type" : "string",
                  "description" : "A short, human-readable summary of the problem type. It should not change from occurrence to occurrence of the problem, except for purposes of localization. If type is given and other than \"about:blank\", this attribute shall also be provided. A short, human-readable summary of the problem type.  It SHOULD NOT change from occurrence to occurrence of the problem, except for purposes of localization (e.g., using proactive content negotiation; see [RFC7231], Section 3.4).\n"
                },
                "status" : {
                  "type" : "integer",
                  "description" : "The HTTP status code for this occurrence of the problem. The HTTP status code ([RFC7231], Section 6) generated by the origin server for this occurrence of the problem.\n"
                },
                "detail" : {
                  "type" : "string",
                  "description" : "A human-readable explanation specific to this occurrence of the problem.\n"
                },
                "instance" : {
                  "type" : "string",
                  "format" : "URI",
                  "description" : "A URI reference that identifies the specific occurrence of the problem. It may yield further information if dereferenced.\n"
                }
              },
              "description" : "The definition of the general \"ProblemDetails\" data structure from IETF RFC 7807 [19] is reproduced inthis structure. Compared to the general framework defined in IETF RFC 7807 [19], the \"status\" and \"detail\" attributes are mandated to be included by the present document, to ensure that the response contains additional textual information about an error. IETF RFC 7807 [19] foresees extensibility of the \"ProblemDetails\" type. It is possible that particular APIs in the present document, or particular implementations, define extensions to define additional attributes that provide more information about the error. The description column only provides some explanation of the meaning to Facilitate understanding of the design. For a full description, see IETF RFC 7807 [19].\n"
            }
          }
        }
      }
    }
  },
  "definitions" : {
    "lcnVnfLcmOperationOccurrenceNotification_changedInfo_vimConnectionInfo" : {
      "required" : [ "id", "vimType" ],
      "properties" : {
        "id" : {
          "type" : "string",
          "description" : "An identifier with the intention of being globally unique.\n"
        },
        "vimId" : {
          "type" : "string",
          "description" : "An identifier with the intention of being globally unique.\n"
        },
        "vimType" : {
          "type" : "string",
          "description" : "Discriminator for the different types of the VIM information. The value of this attribute determines the structure of the \"interfaceInfo\" and \"accessInfo\" attributes, based on the type of the VIM. The set of permitted values is expected to change over time as new types or versions of VIMs become available. The ETSI NFV registry of VIM-related information provides access to information about VimConnectionInfo definitions for various VIM types. The structure of the registry is defined in Annex C of SOL003.\n"
        },
        "interfaceInfo" : {
          "type" : "object",
          "description" : "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions  defined in clause 4 of IETF RFC 7159. \n",
          "properties" : { }
        },
        "accessInfo" : {
          "type" : "object",
          "description" : "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions  defined in clause 4 of IETF RFC 7159. \n",
          "properties" : { }
        },
        "extra" : {
          "type" : "object",
          "description" : "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions  defined in clause 4 of IETF RFC 7159. \n",
          "properties" : { }
        }
      },
      "description" : "This type represents parameters to connect to a VIM for managing the resources of a VNF instance. This structure is used to convey VIM-related parameters over the Or-Vnfm interface. Additional parameters for a VIM may be configured into the VNFM by means outside the scope of the present document, and bound to the identifier of that VIM.\n",
      "example" : {
        "vimType" : "vimType",
        "vimId" : "vimId",
        "extra" : "{}",
        "interfaceInfo" : "{}",
        "id" : "id",
        "accessInfo" : "{}"
      }
    },
    "lcnVnfLcmOperationOccurrenceNotification_computeResource" : {
      "required" : [ "resourceId", "vimConnectionId" ],
      "properties" : {
        "vimConnectionId" : {
          "type" : "string",
          "description" : "An identifier with the intention of being globally unique.\n"
        },
        "resourceProviderId" : {
          "type" : "string",
          "description" : "An identifier with the intention of being globally unique.\n"
        },
        "resourceId" : {
          "type" : "string",
          "description" : "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n"
        },
        "vimLevelResourceType" : {
          "type" : "string",
          "description" : "Type of the resource in the scope of the VIM or the resource provider.\n"
        }
      },
      "description" : "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance. Information about the resource is available from the VIM.\n",
      "example" : {
        "resourceId" : "resourceId",
        "vimConnectionId" : "vimConnectionId",
        "vimLevelResourceType" : "vimLevelResourceType",
        "resourceProviderId" : "resourceProviderId"
      }
    },
    "lcnVnfLcmOperationOccurrenceNotification_affectedVnfcs" : {
      "required" : [ "changeType", "computeResource", "id", "vduId" ],
      "properties" : {
        "id" : {
          "type" : "string",
          "description" : "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n"
        },
        "vduId" : {
          "type" : "string",
          "description" : "An identifier that is unique within a VNF descriptor.\n"
        },
        "changeType" : {
          "type" : "string",
          "description" : "Signals the type of change. Permitted values: * ADDED * REMOVED * MODIFIED * TEMPORARY For a temporary resource, an AffectedVnfc structure exists as long as the temporary resource exists.\n",
          "enum" : [ "ADDED", "REMOVED", "MODIFIED", "TEMPORARY" ]
        },
        "computeResource" : {
          "$ref" : "#/definitions/lcnVnfLcmOperationOccurrenceNotification_computeResource"
        },
        "metadata" : {
          "type" : "object",
          "description" : "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions  defined in clause 4 of IETF RFC 7159. \n",
          "properties" : { }
        },
        "affectedVnfcCpIds" : {
          "type" : "array",
          "description" : "Identifiers of CP(s) of the VNFC instance that were affected by the change.  Shall be present for those affected CPs of the VNFC instance that are associated to an external CP of the VNF instance. May be present for further affected CPs of the VNFC instance.\n",
          "items" : {
            "type" : "string",
            "description" : "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n"
          }
        },
        "addedStorageResourceIds" : {
          "type" : "array",
          "description" : "References to VirtualStorage resources that have been added. Each value refers to a VirtualStorageResourceInfo item in the VnfInstance that was added to the VNFC. It shall be provided if at least one storage resource was added to the VNFC.\n",
          "items" : {
            "type" : "string",
            "description" : "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n"
          }
        },
        "removedStorageResourceIds" : {
          "type" : "array",
          "description" : "References to VirtualStorage resources that have been removed. The value contains the identifier of a VirtualStorageResourceInfo item that has been removed from the VNFC, and might no longer exist in the VnfInstance. It shall be provided if at least one storage resource was removed from the VNFC.\n",
          "items" : {
            "type" : "string",
            "description" : "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n"
          }
        }
      },
      "description" : "This type provides information about added, deleted, modified and temporary VNFCs.  \n",
      "example" : {
        "addedStorageResourceIds" : [ "addedStorageResourceIds", "addedStorageResourceIds" ],
        "metadata" : "{}",
        "changeType" : "ADDED",
        "affectedVnfcCpIds" : [ "affectedVnfcCpIds", "affectedVnfcCpIds" ],
        "id" : "id",
        "vduId" : "vduId",
        "computeResource" : {
          "resourceId" : "resourceId",
          "vimConnectionId" : "vimConnectionId",
          "vimLevelResourceType" : "vimLevelResourceType",
          "resourceProviderId" : "resourceProviderId"
        },
        "removedStorageResourceIds" : [ "removedStorageResourceIds", "removedStorageResourceIds" ]
      }
    },
    "lcnVnfLcmOperationOccurrenceNotification_changedExtConnectivity" : {
      "required" : [ "id", "resourceHandle" ],
      "properties" : {
        "id" : {
          "type" : "string",
          "description" : "An identifier with the intention of being globally unique.\n"
        },
        "resourceHandle" : {
          "$ref" : "#/definitions/lcnVnfLcmOperationOccurrenceNotification_computeResource"
        },
        "extLinkPorts" : {
          "type" : "array",
          "description" : "Link ports of this VL.\n",
          "items" : {
            "$ref" : "#/definitions/lcnVnfLcmOperationOccurrenceNotification_extLinkPorts"
          }
        }
      },
      "example" : {
        "resourceHandle" : {
          "resourceId" : "resourceId",
          "vimConnectionId" : "vimConnectionId",
          "vimLevelResourceType" : "vimLevelResourceType",
          "resourceProviderId" : "resourceProviderId"
        },
        "extLinkPorts" : [ {
          "resourceHandle" : {
            "resourceId" : "resourceId",
            "vimConnectionId" : "vimConnectionId",
            "vimLevelResourceType" : "vimLevelResourceType",
            "resourceProviderId" : "resourceProviderId"
          },
          "id" : "id",
          "cpInstanceId" : "cpInstanceId"
        }, {
          "resourceHandle" : {
            "resourceId" : "resourceId",
            "vimConnectionId" : "vimConnectionId",
            "vimLevelResourceType" : "vimLevelResourceType",
            "resourceProviderId" : "resourceProviderId"
          },
          "id" : "id",
          "cpInstanceId" : "cpInstanceId"
        } ],
        "id" : "id"
      }
    },
    "lcnVnfLcmOperationOccurrenceNotification_error" : {
      "required" : [ "detail", "status" ],
      "properties" : {
        "type" : {
          "type" : "string",
          "format" : "URI",
          "description" : "A URI reference according to IETF RFC 3986 [5] that identifies the problem type. It is encouraged that the URI provides human-readable documentation for the problem (e.g. using HTML) when dereferenced. When this member is not present, its value is assumed to be \"about:blank\".\n"
        },
        "title" : {
          "type" : "string",
          "description" : "A short, human-readable summary of the problem type. It should not change from occurrence to occurrence of the problem, except for purposes of localization. If type is given and other than \"about:blank\", this attribute shall also be provided. A short, human-readable summary of the problem type.  It SHOULD NOT change from occurrence to occurrence of the problem, except for purposes of localization (e.g., using proactive content negotiation; see [RFC7231], Section 3.4).\n"
        },
        "status" : {
          "type" : "integer",
          "description" : "The HTTP status code for this occurrence of the problem. The HTTP status code ([RFC7231], Section 6) generated by the origin server for this occurrence of the problem.\n"
        },
        "detail" : {
          "type" : "string",
          "description" : "A human-readable explanation specific to this occurrence of the problem.\n"
        },
        "instance" : {
          "type" : "string",
          "format" : "URI",
          "description" : "A URI reference that identifies the specific occurrence of the problem. It may yield further information if dereferenced.\n"
        }
      },
      "description" : "The definition of the general \"ProblemDetails\" data structure from IETF RFC 7807 [19] is reproduced inthis structure. Compared to the general framework defined in IETF RFC 7807 [19], the \"status\" and \"detail\" attributes are mandated to be included by the present document, to ensure that the response contains additional textual information about an error. IETF RFC 7807 [19] foresees extensibility of the \"ProblemDetails\" type. It is possible that particular APIs in the present document, or particular implementations, define extensions to define additional attributes that provide more information about the error. The description column only provides some explanation of the meaning to Facilitate understanding of the design. For a full description, see IETF RFC 7807 [19].\n",
      "example" : {
        "instance" : "instance",
        "detail" : "detail",
        "type" : "type",
        "title" : "title",
        "status" : 0
      }
    },
    "VnfLcmOperationOccurrenceNotification" : {
      "type" : "object",
      "required" : [ "_links", "id", "isAutomaticInvocation", "notificationStatus", "notificationType", "operation", "operationState", "subscriptionId", "timeStamp", "vnfInstanceId", "vnfLcmOpOccId" ],
      "properties" : {
        "id" : {
          "type" : "string",
          "description" : "An identifier with the intention of being globally unique.\n"
        },
        "notificationType" : {
          "type" : "string",
          "description" : "Discriminator for the different notification types. Shall be set to \"VnfLcmOperationOccurrenceNotification\" for this notification type.\n",
          "enum" : [ "VnfLcmOperationOccurrenceNotification" ]
        },
        "subscriptionId" : {
          "type" : "string",
          "description" : "An identifier with the intention of being globally unique.\n"
        },
        "timeStamp" : {
          "type" : "string",
          "format" : "date-time",
          "description" : "Date-time stamp.  Representation: String formatted according to IETF RFC 3339.\n"
        },
        "notificationStatus" : {
          "type" : "string",
          "description" : "Indicates whether this notification reports about the start of a lifecycle operation or the result of a lifecycle operation. Permitted values: * START: Informs about the start of the VNF LCM operation\n  occurrence.\n* RESULT: Informs about the final or intermediate result of the VNF\n  LCM operation occurrence.\n",
          "enum" : [ "START", "RESULT" ]
        },
        "operationState" : {
          "type" : "string",
          "description" : "Value | Description ------|------------ STARTING | The LCM operation is starting. PROCESSING | The LCM operation is currently in execution. COMPLETED | he LCM operation has been completed successfully. FAILED_TEMP | The LCM operation has failed and execution has stopped, but the execution of the operation is not considered to be closed. FAILED | The LCM operation has failed and it cannot be retried or rolled back, as it is determined that such action won't succeed. ROLLING_BACK | The LCM operation is currently being rolled back. ROLLED_BACK | The LCM operation has been successfully rolled back, i.e. The state of the VNF prior to the original operation invocation has been restored as closely as possible.\n",
          "enum" : [ "STARTING", "PROCESSING", "COMPLETED", "FAILED_TEMP", "FAILED", "ROLLING_BACK", "ROLLED_BACK" ]
        },
        "vnfInstanceId" : {
          "type" : "string",
          "description" : "An identifier with the intention of being globally unique.\n"
        },
        "operation" : {
          "type" : "string",
          "description" : "Value | Description ------|------------ INSTANTIATE | Represents the \"Instantiate VNF\" LCM operation.    SCALE | Represents the \"Scale VNF\" LCM operation. SCALE_TO_LEVEL | Represents the \"Scale VNF to Level\" LCM operation. CHANGE_FLAVOUR | Represents the \"Change VNF Flavour\" LCM operation. TERMINATE | Represents the \"Terminate VNF\" LCM operation. HEAL | Represents the \"Heal VNF\" LCM operation. OPERATE | Represents the \"Operate VNF\" LCM operation. CHANGE_EXT_CONN | Represents the \"Change external VNF connectivity\" LCM operation. MODIFY_INFO | Represents the \"Modify VNF Information\" LCM operation.     \n",
          "enum" : [ "INSTANTIATE", "SCALE", "SCALE_TO_LEVEL", "CHANGE_FLAVOUR", "TERMINATE", "HEAL", "OPERATE", "CHANGE_EXT_CONN", "MODIFY_INFO" ]
        },
        "isAutomaticInvocation" : {
          "type" : "boolean",
          "description" : "Set to true if this VNF LCM operation occurrence has been triggered by an automated procedure inside the VNFM  (i.e. ScaleVnf / ScaleVnfToLevel triggered by auto-scale, or HealVnf triggered by auto-heal). Set to false otherwise.\n"
        },
        "vnfLcmOpOccId" : {
          "type" : "string",
          "description" : "An identifier with the intention of being globally unique.\n"
        },
        "affectedVnfcs" : {
          "type" : "array",
          "description" : "Information about VNFC instances that were affected during the lifecycle operation. Shall be present if the \"notificationStatus\" is set to \"RESULT\" and the operation has performed any resource modification. Shall be absent otherwise. This attribute contains information about the cumulative changes to virtualised resources that were performed so far by the VNF LCM operation occurrence and by any of the error handling procedures for that operation occurrence.\n",
          "items" : {
            "$ref" : "#/definitions/lcnVnfLcmOperationOccurrenceNotification_affectedVnfcs"
          }
        },
        "affectedVirtualLinks" : {
          "type" : "array",
          "description" : "Information about VL instances that were affected during the lifecycle operation. Shall be present if the \"notificationStatus\" is set to \"RESULT\" and the operation has performed any resource modification. Shall be absent otherwise. This attribute contains information about the cumulative changes to virtualised resources that were performed so far by the VNF LCM operation occurrence and by any of the error handling procedures for that operation occurrence.\n",
          "items" : {
            "$ref" : "#/definitions/lcnVnfLcmOperationOccurrenceNotification_affectedVirtualLinks"
          }
        },
        "affectedVirtualStorages" : {
          "type" : "array",
          "description" : "Information about virtualised storage instances that were affected during the lifecycle operation. Shall be present if the \"notificationStatus\" is set to \"RESULT\" and the operation has performed any resource modification. Shall be absent otherwise. This attribute contains information about the cumulative changes to virtualised resources that were performed so far by the VNF LCM operation occurrence and by any of the error handling procedures for that operation occurrence.\n",
          "items" : {
            "$ref" : "#/definitions/lcnVnfLcmOperationOccurrenceNotification_affectedVirtualStorages"
          }
        },
        "changedInfo" : {
          "$ref" : "#/definitions/lcnVnfLcmOperationOccurrenceNotification_changedInfo"
        },
        "changedExtConnectivity" : {
          "type" : "array",
          "description" : "Information about changed external connectivity, if this notification represents the result of a lifecycle operation occurrence. Shall be present if the \"notificationStatus\" is set to \"RESULT\" and the \"operation\" is set to \"CHANGE_EXT_CONN\".  Shall be absent otherwise.\n",
          "items" : {
            "$ref" : "#/definitions/lcnVnfLcmOperationOccurrenceNotification_changedExtConnectivity"
          }
        },
        "error" : {
          "$ref" : "#/definitions/lcnVnfLcmOperationOccurrenceNotification_error"
        },
        "_links" : {
          "$ref" : "#/definitions/lcnVnfLcmOperationOccurrenceNotification__links"
        }
      },
      "description" : "This type represents a VNF lifecycle management operation occurrence notification, which informs the receiver of changes in the VNF lifecycle caused by a VNF LCM operation occurrence. The support of the notification is mandatory. This notification shall be triggered by the VNFM when there is a change in the VNF lifecycle caused by a VNF LCM operation occurrence, including: * Instantiation of the VNF * Scaling of the VNF instance (including auto-scaling) * Healing of the VNF instance (including auto-healing) * Change of the state of the VNF instance (i.e. Operate VNF) * Change of the deployment flavour of the VNF instance * Change of the external connectivity of the VNF instance * Termination of the VNF instance * Modification of VNF instance information and/or VNF configurable\n  properties through the \"PATCH\" method on the \"Individual VNF instance\"\n  resource.\nIf this is the initial notification about the start of a VNF LCM operation occurrence, it is assumed that the notification is sent by the VNFM before any action (including sending the grant request) is taken as part of the LCM operation. Due to possible race conditions, the \"start\" notification, the grant request and the LCM operation acknowledgment can arrive in any order at the NFVO, and the NFVO shall be able to handle such a situation. If this is a notification about a final or intermediate result state of a VNF LCM operation occurrence, the notification shall be sent after all related actions of the LCM operation that led to this state have  been executed. The new state shall be set in the VnfLcmOpOcc resource before the notification about the state change is sent.\n",
      "example" : {
        "notificationStatus" : "START",
        "affectedVirtualLinks" : [ {
          "metadata" : "{}",
          "networkResource" : {
            "resourceId" : "resourceId",
            "vimConnectionId" : "vimConnectionId",
            "vimLevelResourceType" : "vimLevelResourceType",
            "resourceProviderId" : "resourceProviderId"
          },
          "changeType" : "ADDED",
          "virtualLinkDescId" : "virtualLinkDescId",
          "id" : "id"
        }, {
          "metadata" : "{}",
          "networkResource" : {
            "resourceId" : "resourceId",
            "vimConnectionId" : "vimConnectionId",
            "vimLevelResourceType" : "vimLevelResourceType",
            "resourceProviderId" : "resourceProviderId"
          },
          "changeType" : "ADDED",
          "virtualLinkDescId" : "virtualLinkDescId",
          "id" : "id"
        } ],
        "affectedVirtualStorages" : [ {
          "metadata" : "{}",
          "virtualStorageDescId" : "virtualStorageDescId",
          "changeType" : "ADDED",
          "id" : "id",
          "storageResource" : {
            "resourceId" : "resourceId",
            "vimConnectionId" : "vimConnectionId",
            "vimLevelResourceType" : "vimLevelResourceType",
            "resourceProviderId" : "resourceProviderId"
          }
        }, {
          "metadata" : "{}",
          "virtualStorageDescId" : "virtualStorageDescId",
          "changeType" : "ADDED",
          "id" : "id",
          "storageResource" : {
            "resourceId" : "resourceId",
            "vimConnectionId" : "vimConnectionId",
            "vimLevelResourceType" : "vimLevelResourceType",
            "resourceProviderId" : "resourceProviderId"
          }
        } ],
        "affectedVnfcs" : [ {
          "addedStorageResourceIds" : [ "addedStorageResourceIds", "addedStorageResourceIds" ],
          "metadata" : "{}",
          "changeType" : "ADDED",
          "affectedVnfcCpIds" : [ "affectedVnfcCpIds", "affectedVnfcCpIds" ],
          "id" : "id",
          "vduId" : "vduId",
          "computeResource" : {
            "resourceId" : "resourceId",
            "vimConnectionId" : "vimConnectionId",
            "vimLevelResourceType" : "vimLevelResourceType",
            "resourceProviderId" : "resourceProviderId"
          },
          "removedStorageResourceIds" : [ "removedStorageResourceIds", "removedStorageResourceIds" ]
        }, {
          "addedStorageResourceIds" : [ "addedStorageResourceIds", "addedStorageResourceIds" ],
          "metadata" : "{}",
          "changeType" : "ADDED",
          "affectedVnfcCpIds" : [ "affectedVnfcCpIds", "affectedVnfcCpIds" ],
          "id" : "id",
          "vduId" : "vduId",
          "computeResource" : {
            "resourceId" : "resourceId",
            "vimConnectionId" : "vimConnectionId",
            "vimLevelResourceType" : "vimLevelResourceType",
            "resourceProviderId" : "resourceProviderId"
          },
          "removedStorageResourceIds" : [ "removedStorageResourceIds", "removedStorageResourceIds" ]
        } ],
        "_links" : {
          "subscription" : {
            "href" : "http://example.com/aeiou"
          },
          "vnfLcmOpOcc" : {
            "href" : "http://example.com/aeiou"
          },
          "vnfInstance" : {
            "href" : "http://example.com/aeiou"
          }
        },
        "operationState" : "STARTING",
        "notificationType" : "VnfLcmOperationOccurrenceNotification",
        "error" : {
          "instance" : "instance",
          "detail" : "detail",
          "type" : "type",
          "title" : "title",
          "status" : 0
        },
        "timeStamp" : "2000-01-23T04:56:07.000+00:00",
        "vnfInstanceId" : "vnfInstanceId",
        "vnfLcmOpOccId" : "vnfLcmOpOccId",
        "changedInfo" : {
          "vnfProductName" : "vnfProductName",
          "metadata" : "{}",
          "extensions" : "{}",
          "vimConnectionInfo" : [ {
            "vimType" : "vimType",
            "vimId" : "vimId",
            "extra" : "{}",
            "interfaceInfo" : "{}",
            "id" : "id",
            "accessInfo" : "{}"
          }, {
            "vimType" : "vimType",
            "vimId" : "vimId",
            "extra" : "{}",
            "interfaceInfo" : "{}",
            "id" : "id",
            "accessInfo" : "{}"
          } ],
          "vnfdVersion" : "vnfdVersion",
          "vnfProvider" : "vnfProvider",
          "vnfConfigurableProperties" : "{}",
          "vnfPkgId" : "vnfPkgId",
          "vnfdId" : "vnfdId",
          "vnfInstanceName" : "vnfInstanceName",
          "vnfInstanceDescription" : "vnfInstanceDescription",
          "vnfSoftwareVersion" : "vnfSoftwareVersion"
        },
        "changedExtConnectivity" : [ {
          "resourceHandle" : {
            "resourceId" : "resourceId",
            "vimConnectionId" : "vimConnectionId",
            "vimLevelResourceType" : "vimLevelResourceType",
            "resourceProviderId" : "resourceProviderId"
          },
          "extLinkPorts" : [ {
            "resourceHandle" : {
              "resourceId" : "resourceId",
              "vimConnectionId" : "vimConnectionId",
              "vimLevelResourceType" : "vimLevelResourceType",
              "resourceProviderId" : "resourceProviderId"
            },
            "id" : "id",
            "cpInstanceId" : "cpInstanceId"
          }, {
            "resourceHandle" : {
              "resourceId" : "resourceId",
              "vimConnectionId" : "vimConnectionId",
              "vimLevelResourceType" : "vimLevelResourceType",
              "resourceProviderId" : "resourceProviderId"
            },
            "id" : "id",
            "cpInstanceId" : "cpInstanceId"
          } ],
          "id" : "id"
        }, {
          "resourceHandle" : {
            "resourceId" : "resourceId",
            "vimConnectionId" : "vimConnectionId",
            "vimLevelResourceType" : "vimLevelResourceType",
            "resourceProviderId" : "resourceProviderId"
          },
          "extLinkPorts" : [ {
            "resourceHandle" : {
              "resourceId" : "resourceId",
              "vimConnectionId" : "vimConnectionId",
              "vimLevelResourceType" : "vimLevelResourceType",
              "resourceProviderId" : "resourceProviderId"
            },
            "id" : "id",
            "cpInstanceId" : "cpInstanceId"
          }, {
            "resourceHandle" : {
              "resourceId" : "resourceId",
              "vimConnectionId" : "vimConnectionId",
              "vimLevelResourceType" : "vimLevelResourceType",
              "resourceProviderId" : "resourceProviderId"
            },
            "id" : "id",
            "cpInstanceId" : "cpInstanceId"
          } ],
          "id" : "id"
        } ],
        "id" : "id",
        "subscriptionId" : "subscriptionId",
        "isAutomaticInvocation" : true,
        "operation" : "INSTANTIATE"
      }
    },
    "lcnVnfLcmOperationOccurrenceNotification_extLinkPorts" : {
      "required" : [ "id", "resourceHandle" ],
      "properties" : {
        "id" : {
          "type" : "string",
          "description" : "An identifier with the intention of being globally unique.\n"
        },
        "resourceHandle" : {
          "$ref" : "#/definitions/lcnVnfLcmOperationOccurrenceNotification_computeResource"
        },
        "cpInstanceId" : {
          "type" : "string",
          "description" : "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n"
        }
      },
      "description" : "This type represents information about a link port of an external VL, i.e. a port providing connectivity for the VNF to an NS VL. \n",
      "example" : {
        "resourceHandle" : {
          "resourceId" : "resourceId",
          "vimConnectionId" : "vimConnectionId",
          "vimLevelResourceType" : "vimLevelResourceType",
          "resourceProviderId" : "resourceProviderId"
        },
        "id" : "id",
        "cpInstanceId" : "cpInstanceId"
      }
    },
    "VnfIdentifierCreationNotification" : {
      "type" : "object",
      "required" : [ "_links", "id", "notificationType", "timeStamp", "vnfInstanceId" ],
      "properties" : {
        "id" : {
          "type" : "string",
          "description" : "An identifier with the intention of being globally unique.\n"
        },
        "notificationType" : {
          "type" : "string",
          "description" : "Discriminator for the different notification types. Shall be set to \"VnfIdentifierCreationNotification\" for this notification type.\n",
          "enum" : [ "VnfIdentifierCreationNotification" ]
        },
        "subscriptionId" : {
          "type" : "string",
          "description" : "An identifier with the intention of being globally unique.\n"
        },
        "timeStamp" : {
          "type" : "string",
          "format" : "date-time",
          "description" : "Date-time stamp.  Representation: String formatted according to IETF RFC 3339.\n"
        },
        "vnfInstanceId" : {
          "type" : "string",
          "description" : "An identifier with the intention of being globally unique.\n"
        },
        "_links" : {
          "$ref" : "#/definitions/lcnVnfLcmOperationOccurrenceNotification__links"
        }
      },
      "description" : "This type represents a VNF identifier creation notification, which informs the receiver of the creation of a new VNF instance resource and the associated VNF instance identifier. This notification shall be triggered by the VNFM when it has created a VNF instance resource and the associated VNF instance identifier.\n",
      "example" : {
        "timeStamp" : "2000-01-23T04:56:07.000+00:00",
        "vnfInstanceId" : "vnfInstanceId",
        "_links" : {
          "subscription" : {
            "href" : "http://example.com/aeiou"
          },
          "vnfLcmOpOcc" : {
            "href" : "http://example.com/aeiou"
          },
          "vnfInstance" : {
            "href" : "http://example.com/aeiou"
          }
        },
        "id" : "id",
        "notificationType" : "VnfIdentifierCreationNotification",
        "subscriptionId" : "subscriptionId"
      }
    },
    "lcnVnfLcmOperationOccurrenceNotification__links_vnfInstance" : {
      "required" : [ "href" ],
      "properties" : {
        "href" : {
          "type" : "string",
          "format" : "url",
          "description" : "URI of the referenced resource.\n"
        }
      },
      "description" : "This type represents a link to a resource.\n",
      "example" : {
        "href" : "http://example.com/aeiou"
      }
    },
    "lcnVnfLcmOperationOccurrenceNotification_changedInfo" : {
      "properties" : {
        "vnfInstanceName" : {
          "type" : "string",
          "description" : "If present, this attribute signals modifications of the \"vnfInstanceName\" attribute in \"VnfInstance\".\n"
        },
        "vnfInstanceDescription" : {
          "type" : "string",
          "description" : "If present, this attribute signals modifications of the \"vnfInstanceDescription\" attribute in \"VnfInstance\".\n"
        },
        "vnfConfigurableProperties" : {
          "type" : "object",
          "description" : "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions  defined in clause 4 of IETF RFC 7159. \n",
          "properties" : { }
        },
        "metadata" : {
          "type" : "object",
          "description" : "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions  defined in clause 4 of IETF RFC 7159. \n",
          "properties" : { }
        },
        "extensions" : {
          "type" : "object",
          "description" : "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions  defined in clause 4 of IETF RFC 7159. \n",
          "properties" : { }
        },
        "vimConnectionInfo" : {
          "type" : "array",
          "description" : "If present, this attribute signals modifications of certain entries in the \"vimConnectionInfo\" attribute array in \"VnfInstance\".\n",
          "items" : {
            "$ref" : "#/definitions/lcnVnfLcmOperationOccurrenceNotification_changedInfo_vimConnectionInfo"
          }
        },
        "vnfPkgId" : {
          "type" : "string",
          "description" : "An identifier with the intention of being globally unique.\n"
        },
        "vnfdId" : {
          "type" : "string",
          "description" : "An identifier with the intention of being globally unique.\n"
        },
        "vnfProvider" : {
          "type" : "string",
          "description" : "If present, this attribute signals modifications of the \"vnfProvider\" attribute in \"VnfInstance\". If present, this attribute (which depends on the value of the \"vnfPkgId\" attribute) was modified implicitly following a request to modify the \"vnfPkgId\" attribute, by copying the value of this attribute from the VNFD in the VNF Package identified by the \"vnfPkgId” attribute.\n"
        },
        "vnfProductName" : {
          "type" : "string",
          "description" : "If present, this attribute signals modifications of the \"vnfProductName\" attribute in \"VnfInstance\". If present, this attribute (which depends on the value of the \"vnfPkgId\" attribute) was modified implicitly following a request to modify the \"vnfPkgId\" attribute, by copying the value of this attribute from the VNFD in the VNF Package identified by the \"vnfPkgId” attribute.\n"
        },
        "vnfSoftwareVersion" : {
          "type" : "string",
          "description" : "A Version.\n"
        },
        "vnfdVersion" : {
          "type" : "string",
          "description" : "A Version.\n"
        }
      },
      "description" : "This type represents attribute modifications that were performed on an \"Individual VNF instance\" resource. The attributes that can be included consist of those requested to be modified explicitly in the \"VnfInfoModificationRequest\" data structure, and additional attributes of the \"VnfInstance\" data structure that were modified implicitly e.g. when modifying the referenced VNF package.\n",
      "example" : {
        "vnfProductName" : "vnfProductName",
        "metadata" : "{}",
        "extensions" : "{}",
        "vimConnectionInfo" : [ {
          "vimType" : "vimType",
          "vimId" : "vimId",
          "extra" : "{}",
          "interfaceInfo" : "{}",
          "id" : "id",
          "accessInfo" : "{}"
        }, {
          "vimType" : "vimType",
          "vimId" : "vimId",
          "extra" : "{}",
          "interfaceInfo" : "{}",
          "id" : "id",
          "accessInfo" : "{}"
        } ],
        "vnfdVersion" : "vnfdVersion",
        "vnfProvider" : "vnfProvider",
        "vnfConfigurableProperties" : "{}",
        "vnfPkgId" : "vnfPkgId",
        "vnfdId" : "vnfdId",
        "vnfInstanceName" : "vnfInstanceName",
        "vnfInstanceDescription" : "vnfInstanceDescription",
        "vnfSoftwareVersion" : "vnfSoftwareVersion"
      }
    },
    "lcnVnfLcmOperationOccurrenceNotification_affectedVirtualStorages" : {
      "required" : [ "changeType", "id", "storageResource", "virtualStorageDescId" ],
      "properties" : {
        "id" : {
          "type" : "string",
          "description" : "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n"
        },
        "virtualStorageDescId" : {
          "type" : "string",
          "description" : "An identifier that is unique within a VNF descriptor.\n"
        },
        "changeType" : {
          "type" : "string",
          "description" : "Signals the type of change. Permitted values: * ADDED * REMOVED * MODIFIED * TEMPORARY For a temporary resource, an AffectedVirtualStorage structure exists as long as the temporary resource exists.\n",
          "enum" : [ "ADDED", "REMOVED", "MODIFIED", "TEMPORARY" ]
        },
        "storageResource" : {
          "$ref" : "#/definitions/lcnVnfLcmOperationOccurrenceNotification_computeResource"
        },
        "metadata" : {
          "type" : "object",
          "description" : "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions  defined in clause 4 of IETF RFC 7159. \n",
          "properties" : { }
        }
      },
      "description" : "This type provides information about added, deleted, modified and temporary virtual storage resources.\n",
      "example" : {
        "metadata" : "{}",
        "virtualStorageDescId" : "virtualStorageDescId",
        "changeType" : "ADDED",
        "id" : "id",
        "storageResource" : {
          "resourceId" : "resourceId",
          "vimConnectionId" : "vimConnectionId",
          "vimLevelResourceType" : "vimLevelResourceType",
          "resourceProviderId" : "resourceProviderId"
        }
      }
    },
    "lcnVnfLcmOperationOccurrenceNotification__links" : {
      "required" : [ "subscription", "vnfInstance" ],
      "properties" : {
        "vnfInstance" : {
          "$ref" : "#/definitions/lcnVnfLcmOperationOccurrenceNotification__links_vnfInstance"
        },
        "subscription" : {
          "$ref" : "#/definitions/lcnVnfLcmOperationOccurrenceNotification__links_vnfInstance"
        },
        "vnfLcmOpOcc" : {
          "$ref" : "#/definitions/lcnVnfLcmOperationOccurrenceNotification__links_vnfInstance"
        }
      },
      "description" : "This type represents the links to resources that a notification can contain.\n",
      "example" : {
        "subscription" : {
          "href" : "http://example.com/aeiou"
        },
        "vnfLcmOpOcc" : {
          "href" : "http://example.com/aeiou"
        },
        "vnfInstance" : {
          "href" : "http://example.com/aeiou"
        }
      }
    },
    "VnfIdentifierDeletionNotification" : {
      "type" : "object",
      "required" : [ "_links", "id", "notificationType", "timeStamp", "vnfInstanceId" ],
      "properties" : {
        "id" : {
          "type" : "string",
          "description" : "An identifier with the intention of being globally unique.\n"
        },
        "notificationType" : {
          "type" : "string",
          "description" : "Discriminator for the different notification types. Shall be set to \"VnfIdentifierDeletionNotification\" for this notification type.\n",
          "enum" : [ "VnfIdentifierDeletionNotification" ]
        },
        "subscriptionId" : {
          "type" : "string",
          "description" : "An identifier with the intention of being globally unique.\n"
        },
        "timeStamp" : {
          "type" : "string",
          "format" : "date-time",
          "description" : "Date-time stamp.  Representation: String formatted according to IETF RFC 3339.\n"
        },
        "vnfInstanceId" : {
          "type" : "string",
          "description" : "An identifier with the intention of being globally unique.\n"
        },
        "_links" : {
          "$ref" : "#/definitions/lcnVnfLcmOperationOccurrenceNotification__links"
        }
      },
      "description" : "This type represents a VNF identifier deletion notification, which informs the receiver of the deletion of a new VNF instance resource and the associated VNF instance identifier. This notification shall be triggered by the VNFM when it has deleted a VNF instance resource and the associated VNF instance identifier.\n",
      "example" : {
        "timeStamp" : "2000-01-23T04:56:07.000+00:00",
        "vnfInstanceId" : "vnfInstanceId",
        "_links" : {
          "subscription" : {
            "href" : "http://example.com/aeiou"
          },
          "vnfLcmOpOcc" : {
            "href" : "http://example.com/aeiou"
          },
          "vnfInstance" : {
            "href" : "http://example.com/aeiou"
          }
        },
        "id" : "id",
        "notificationType" : "VnfIdentifierDeletionNotification",
        "subscriptionId" : "subscriptionId"
      }
    },
    "lcnVnfLcmOperationOccurrenceNotification_affectedVirtualLinks" : {
      "required" : [ "changeType", "id", "networkResource", "virtualLinkDescId" ],
      "properties" : {
        "id" : {
          "type" : "string",
          "description" : "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n"
        },
        "virtualLinkDescId" : {
          "type" : "string",
          "description" : "An identifier that is unique within a VNF descriptor.\n"
        },
        "changeType" : {
          "type" : "string",
          "description" : "Signals the type of change. Permitted values: * ADDED * REMOVED * MODIFIED * TEMPORARY * LINK_PORT_ADDED * LINK_PORT_REMOVED For a temporary resource, an AffectedVirtualLink structure exists as long as the temporary resource exists.\n",
          "enum" : [ "ADDED", "REMOVED", "MODIFIED", "TEMPORARY", "LINK_PORT_ADDED", "LINK_PORT_REMOVED" ]
        },
        "networkResource" : {
          "$ref" : "#/definitions/lcnVnfLcmOperationOccurrenceNotification_computeResource"
        },
        "metadata" : {
          "type" : "object",
          "description" : "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions  defined in clause 4 of IETF RFC 7159. \n",
          "properties" : { }
        }
      },
      "description" : "This type provides information about added, deleted, modified and temporary VLs.\n",
      "example" : {
        "metadata" : "{}",
        "networkResource" : {
          "resourceId" : "resourceId",
          "vimConnectionId" : "vimConnectionId",
          "vimLevelResourceType" : "vimLevelResourceType",
          "resourceProviderId" : "resourceProviderId"
        },
        "changeType" : "ADDED",
        "virtualLinkDescId" : "virtualLinkDescId",
        "id" : "id"
      }
    }
  },
  "externalDocs" : {
    "description" : "ETSI GS NFV-SOL 003 V2.4.1",
    "url" : "http://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/02.04.01_60/gs_NFV-SOL003v020401p.pdf"
  }
}