{
	"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 \"Individual VNF LCM operation occurrence\"  resource before the notification about the state change is sent. * NOTE 1:\tShall be present if the \"notificationStatus\" is set to \"RESULT\", the \"verbosity\" attribute is set\n          to \"FULL\" and the operation has performed any resource modification. Shall be absent otherwise.\n          This attribute contains information about the cumulative changes to virtualised resources that\n          were performed so far by the VNF LCM operation occurrence and by any of the error handling\n          procedures for that operation occurrence.\n  NOTE 2:\tFor a particular affected VL, there shall be as many \"AffectedVirtualLink\" entries as needed\n          for signalling the different types of changes, i.e. one per virtual link and change type.\n          For instance, in the case of signaling affected VL instances involving the addition of a particular\n          VL instance with links ports, one \"AffectedVirtualLink\" entry signals the addition of the VL by using\n          the \"changeType\" attribute of \"AffectedVirtualLink\" structure equal to \"ADDED\", and another\n          \"AffectedVirtualLink\" entry signals the addition of VNF link ports of the VL by using the\n          \"changeType\" equal to \"LINK_PORT_ADDED\".\n",
	"type": "object",
	"required": [
		"id",
		"notificationType",
		"subscriptionId",
		"timeStamp",
		"notificationStatus",
		"operationState",
		"vnfInstanceId",
		"operation",
		"isAutomaticInvocation",
		"vnfLcmOpOccId",
		"_links"
	],
	"properties": {
		"id": {
			"description": "An identifier with the intention of being globally unique.\n",
			"type": "string"
		},
		"notificationType": {
			"description": "Discriminator for the different notification types. Shall be set to \"VnfLcmOperationOccurrenceNotification\" for this notification type.\n",
			"type": "string",
			"enum": [
				"VnfLcmOperationOccurrenceNotification"
			]
		},
		"subscriptionId": {
			"description": "An identifier with the intention of being globally unique.\n",
			"type": "string"
		},
		"timeStamp": {
			"description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
			"type": "string",
			"format": "date-time"
		},
		"notificationStatus": {
			"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",
			"type": "string",
			"enum": [
				"START",
				"RESULT"
			]
		},
		"operationState": {
			"description": "STARTING: The LCM operation is starting. PROCESSING: The LCM operation is currently in execution. COMPLETED: The 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",
			"type": "string",
			"enum": [
				"STARTING",
				"PROCESSING",
				"COMPLETED",
				"FAILED_TEMP",
				"FAILED",
				"ROLLING_BACK",
				"ROLLED_BACK"
			]
		},
		"vnfInstanceId": {
			"description": "An identifier with the intention of being globally unique.\n",
			"type": "string"
		},
		"operation": {
			"description": "The enumeration LcmOpType defines the permitted values to represent  VNF lifecycle operation types in VNF lifecycle management operation  occurrence resources and VNF lifecycle management operation occurrence  notifications.  It shall comply with the provisions defined in table 5.5.4.5-1.\nValue | 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. CREATE_SNAPSHOT | Represents the \"Create VNF Snapshot\" LCM operation. REVERT_TO_SNAPSHOT | Represents the ΓÇ£Revert-To VNF Snapshot\" LCM operation. CHANGE_VNFPKG | Represents the \"Change current VNF package\" LCM operation.\n",
			"type": "string",
			"enum": [
				"INSTANTIATE",
				"SCALE",
				"SCALE_TO_LEVEL",
				"CHANGE_FLAVOUR",
				"TERMINATE",
				"HEAL",
				"OPERATE",
				"CHANGE_EXT_CONN",
				"MODIFY_INFO",
				"CREATE_SNAPSHOT",
				"REVERT_TO_SNAPSHOT",
				"CHANGE_VNFPKG"
			]
		},
		"isAutomaticInvocation": {
			"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",
			"type": "boolean"
		},
		"verbosity": {
			"description": "The enumeration LcmOpOccNotificationVerbosityType provides values to control the verbosity of LCM operation occurrence notifications. * FULL: This signals a full notification which contains all change details. * SHORT: This signals a short notification which omits large-volume change details to reduce the size of data to\n         be sent via the notification mechanism.\n",
			"type": "string",
			"enum": [
				"FULL",
				"SHORT"
			]
		},
		"vnfLcmOpOccId": {
			"description": "An identifier with the intention of being globally unique.\n",
			"type": "string"
		},
		"affectedVnfcs": {
			"description": "Information about VNFC instances that were affected during the lifecycle operation. See note 1.\n",
			"type": "array",
			"items": {
				"description": "This type provides information about added, deleted, modified and temporary VNFCs.\n",
				"type": "object",
				"required": [
					"id",
					"vduId",
					"changeType",
					"computeResource"
				],
				"properties": {
					"id": {
						"description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
						"type": "string"
					},
					"vduId": {
						"description": "An identifier that is unique within a VNF descriptor.\n",
						"type": "string"
					},
					"vnfdId": {
						"description": "An identifier with the intention of being globally unique.\n",
						"type": "string"
					},
					"changeType": {
						"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",
						"type": "string",
						"enum": [
							"ADDED",
							"REMOVED",
							"MODIFIED",
							"TEMPORARY"
						]
					},
					"computeResource": {
						"required": [
							"resourceId"
						],
						"type": "object",
						"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",
						"properties": {
							"vimConnectionId": {
								"description": "An identifier with the intention of being globally unique.\n",
								"type": "string"
							},
							"resourceProviderId": {
								"description": "An identifier with the intention of being globally unique.\n",
								"type": "string"
							},
							"resourceId": {
								"description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
								"type": "string"
							},
							"vimLevelResourceType": {
								"description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
								"type": "string"
							}
						}
					},
					"metadata": {
						"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 keyvalue pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 8259. In the following example, a list of key-value pairs with four keys (\"aString\", \"aNumber\", \"anArray\" and \"anObject\") is provided to illustrate that the values associated with different keys can be of different type.\n",
						"type": "object"
					},
					"affectedVnfcCpIds": {
						"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",
						"type": "array",
						"items": {
							"description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
							"type": "string"
						}
					},
					"addedStorageResourceIds": {
						"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",
						"type": "array",
						"items": {
							"description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
							"type": "string"
						}
					},
					"removedStorageResourceIds": {
						"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",
						"type": "array",
						"items": {
							"description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
							"type": "string"
						}
					}
				}
			}
		},
		"affectedVirtualLinks": {
			"description": "Information about VL instances that were affected during the lifecycle operation. See note 1 and note 2.\n",
			"type": "array",
			"items": {
				"description": "This type provides information about added, deleted, modified and temporary VLs, and added or removed VNF link ports.\nNOTE:\tWhen signalling the addition (LINK_PORT_ADDED) or removal (LINK_PORT_REMOVED) of VNF link ports, \n      the \"networkResource\" attribute refers to the affected virtual link instance, not the link port \n      instance. The resource handles of the affected VNF link ports can be found by dereferencing the \n      identifiers in the \"vnfLinkPortIds\" attribute.\n",
				"type": "object",
				"required": [
					"id",
					"vnfVirtualLinkDescId",
					"changeType",
					"networkResource"
				],
				"properties": {
					"id": {
						"description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
						"type": "string"
					},
					"vnfVirtualLinkDescId": {
						"description": "An identifier that is unique within a VNF descriptor.\n",
						"type": "string"
					},
					"vnfdId": {
						"description": "An identifier with the intention of being globally unique.\n",
						"type": "string"
					},
					"changeType": {
						"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. When signalling the addition (LINK_PORT_ADDED) or removal (LINK_PORT_REMOVED) of VNF link ports, the \"networkResource\" attribute refers to the affected virtual link instance, not the link port instance. The resource handles of the affected VNF link ports can be found by dereferencing the identifiers in the \"vnfLinkPortIds\" attribute.\n",
						"type": "string",
						"enum": [
							"ADDED",
							"REMOVED",
							"MODIFIED",
							"TEMPORARY",
							"LINK_PORT_ADDED",
							"LINK_PORT_REMOVED"
						]
					},
					"networkResource": {
						"required": [
							"resourceId"
						],
						"type": "object",
						"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",
						"properties": {
							"vimConnectionId": {
								"description": "An identifier with the intention of being globally unique.\n",
								"type": "string"
							},
							"resourceProviderId": {
								"description": "An identifier with the intention of being globally unique.\n",
								"type": "string"
							},
							"resourceId": {
								"description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
								"type": "string"
							},
							"vimLevelResourceType": {
								"description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
								"type": "string"
							}
						}
					},
					"vnfLinkPortIds": {
						"description": "Identifiers of the link ports of the affected VL related to the change. Each identifier references a  \"VnfLinkPortInfo\" structure.\nShall be set when changeType is equal to \"LINK_PORT_ADDED\" or \"LINK_PORT_REMOVED\", and the related  \"VnfLinkPortInfo\" structures are present (case \"added\") or have been present (case \"removed\") in the  \"VnfVirtualLinkResourceInfo\" or \"ExtManagedVirtualLinkInfo\" structures that are represented by the  \"vnfVirtualLinkResourceInfo\" or \"extManagedVirtualLinkInfo\" attribute in the \"VnfInstance\" structure.  See note.\n",
						"type": "array",
						"items": {
							"description": "An identifier that is unique within a VNF descriptor.\n",
							"type": "string"
						}
					},
					"metadata": {
						"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 keyvalue pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 8259. In the following example, a list of key-value pairs with four keys (\"aString\", \"aNumber\", \"anArray\" and \"anObject\") is provided to illustrate that the values associated with different keys can be of different type.\n",
						"type": "object"
					}
				}
			}
		},
		"affectedExtLinkPorts": {
			"description": "Information about external VNF link ports that were affected during the lifecycle operation. See note 1.\n",
			"type": "array",
			"items": {
				"description": "This type provides information about added and deleted external link ports (link ports attached to external virtual links).\n",
				"type": "object",
				"required": [
					"id",
					"changeType",
					"extCpInstanceId",
					"resourceHandle"
				],
				"properties": {
					"id": {
						"description": "An identifier with the intention of being globally unique.\n",
						"type": "string"
					},
					"changeType": {
						"description": "Signals the type of change. Permitted values: -\tADDED -\tREMOVED\n",
						"type": "string",
						"enum": [
							"ADDED",
							"REMOVED"
						]
					},
					"extCpInstanceId": {
						"description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
						"type": "string"
					},
					"resourceHandle": {
						"required": [
							"resourceId"
						],
						"type": "object",
						"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",
						"properties": {
							"vimConnectionId": {
								"description": "An identifier with the intention of being globally unique.\n",
								"type": "string"
							},
							"resourceProviderId": {
								"description": "An identifier with the intention of being globally unique.\n",
								"type": "string"
							},
							"resourceId": {
								"description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
								"type": "string"
							},
							"vimLevelResourceType": {
								"description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
								"type": "string"
							}
						}
					}
				}
			}
		},
		"affectedVirtualStorages": {
			"description": "Information about virtualised storage instances that were affected during the lifecycle operation. See note 1.\n",
			"type": "array",
			"items": {
				"description": "This type provides information about added, deleted, modified and temporary virtual storage resources.\n",
				"type": "object",
				"required": [
					"id",
					"virtualStorageDescId",
					"changeType",
					"storageResource"
				],
				"properties": {
					"id": {
						"description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
						"type": "string"
					},
					"virtualStorageDescId": {
						"description": "An identifier that is unique within a VNF descriptor.\n",
						"type": "string"
					},
					"vnfdId": {
						"description": "An identifier with the intention of being globally unique.\n",
						"type": "string"
					},
					"changeType": {
						"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",
						"type": "string",
						"enum": [
							"ADDED",
							"REMOVED",
							"MODIFIED",
							"TEMPORARY"
						]
					},
					"storageResource": {
						"required": [
							"resourceId"
						],
						"type": "object",
						"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",
						"properties": {
							"vimConnectionId": {
								"description": "An identifier with the intention of being globally unique.\n",
								"type": "string"
							},
							"resourceProviderId": {
								"description": "An identifier with the intention of being globally unique.\n",
								"type": "string"
							},
							"resourceId": {
								"description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
								"type": "string"
							},
							"vimLevelResourceType": {
								"description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
								"type": "string"
							}
						}
					},
					"metadata": {
						"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 keyvalue pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 8259. In the following example, a list of key-value pairs with four keys (\"aString\", \"aNumber\", \"anArray\" and \"anObject\") is provided to illustrate that the values associated with different keys can be of different type.\n",
						"type": "object"
					}
				}
			}
		},
		"changedInfo": {
			"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. * NOTE:\tIf present, this attribute (which depends on the value of the \"vnfdId\" attribute)\n          was modified implicitly following a request to modify the \"vnfdId\" attribute, by\n          copying the value of this attribute from the VNFD in the VNF Package identified\n          by the \"vnfdId\" attribute.\n",
			"type": "object",
			"properties": {
				"vnfInstanceName": {
					"description": "If present, this attribute signals modifications of the \"vnfInstanceName\" attribute in \"VnfInstance\" as defined in clause 5.5.2.12..\n",
					"type": "string"
				},
				"vnfInstanceDescription": {
					"description": "If present, this attribute signals modifications of the \"vnfInstanceDescription\" attribute in \"VnfInstance\", as defined in clause 5.5.2.12..\n",
					"type": "string"
				},
				"vnfConfigurableProperties": {
					"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 keyvalue pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 8259. In the following example, a list of key-value pairs with four keys (\"aString\", \"aNumber\", \"anArray\" and \"anObject\") is provided to illustrate that the values associated with different keys can be of different type.\n",
					"type": "object"
				},
				"metadata": {
					"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 keyvalue pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 8259. In the following example, a list of key-value pairs with four keys (\"aString\", \"aNumber\", \"anArray\" and \"anObject\") is provided to illustrate that the values associated with different keys can be of different type.\n",
					"type": "object"
				},
				"extensions": {
					"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 keyvalue pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 8259. In the following example, a list of key-value pairs with four keys (\"aString\", \"aNumber\", \"anArray\" and \"anObject\") is provided to illustrate that the values associated with different keys can be of different type.\n",
					"type": "object"
				},
				"vnfdId": {
					"description": "An identifier with the intention of being globally unique.\n",
					"type": "string"
				},
				"vnfProvider": {
					"description": "If present, this attribute signals modifications of the \"vnfProvider\" attribute in \"VnfInstance\". See note.\n",
					"type": "string"
				},
				"vnfProductName": {
					"description": "If present, this attribute signals modifications of the \"vnfProductName\" attribute in \"VnfInstance\". See note.\n",
					"type": "string"
				},
				"vnfSoftwareVersion": {
					"description": "A version.\n",
					"type": "string"
				},
				"vnfdVersion": {
					"description": "A version.\n",
					"type": "string"
				},
				"vnfcInfoModifications": {
					"description": "If present, this attribute signals modifications of certain entries in the \"vnfcInfo\" attribute array in the \"instantiatedVnfInfo\" attribute of \"VnfInstance\", as defined in clause 5.5.2.12.\n",
					"type": "array",
					"items": {
						"description": "This type represents modifications of an entry in an array of \"VnfcInfo\" objects. * NOTE:\tThe attribute \"id\" in this data type represents the same identifier as the attribute\n          \"vnfcInstanceId\" in other related data types in the present document. For reasons of backward\n          compatibility, this misalignment is not corrected.\n",
						"type": "object",
						"required": [
							"id",
							"vnfcConfigurableProperties"
						],
						"properties": {
							"id": {
								"description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
								"type": "string"
							},
							"vnfcConfigurableProperties": {
								"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 keyvalue pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 8259. In the following example, a list of key-value pairs with four keys (\"aString\", \"aNumber\", \"anArray\" and \"anObject\") is provided to illustrate that the values associated with different keys can be of different type.\n",
								"type": "object"
							}
						}
					}
				}
			}
		},
		"affectedVipCps": {
			"description": "Information about virtual IP CP instances that were affected during the execution of the lifecycle management operation, if this notification represents the result of a lifecycle management operation occurrence. Shall be present if the \"notificationStatus\" is set to \"RESULT\", the \"verbosity\" attribute is set to \"FULL\" and the operation has made any changes to the VIP CP instances of the VNF instance. Shall be absent otherwise. Only information about VIP CP instances that have been added, deleted or modified shall be provided.\n",
			"type": "array",
			"items": {
				"description": "This type provides information about added, deleted and modified virtual IP CP instances.\n",
				"type": "object",
				"required": [
					"cpInstanceId",
					"cpdId",
					"changeType"
				],
				"properties": {
					"cpInstanceId": {
						"description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
						"type": "string"
					},
					"cpdId": {
						"description": "An identifier that is unique within a VNF descriptor.\n",
						"type": "string"
					},
					"vnfdId": {
						"description": "An identifier with the intention of being globally unique.\n",
						"type": "string"
					},
					"changeType": {
						"description": "Signals the type of change. Permitted values: -\tADDED -\tREMOVED -\tMODIFIED\n",
						"type": "string",
						"enum": [
							"ADDED",
							"REMOVED",
							"MODIFIED"
						]
					}
				}
			}
		},
		"changedExtConnectivity": {
			"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\" has made any change of the external  connectivity of the VNF instance. Shall be absent otherwise.\n",
			"type": "array",
			"items": {
				"description": "This type represents information about an external VL. It shall comply with the provisions defined in table 5.5.3.2-1.\nNOTE:\tThis attribute reflects the current configuration information that has resulted from merging into this attribute \n      the \"VnfExtCpData\" information which was passed as part of the \"ExtVirtualLinkData\" structure in the input of the \n      most recent VNF LCM operation such as \"InstantiateVnfRequest\", \"ChangeExtVnfConnectivityRequest\", \"ChangeVnfFlavourRequest\" \n      or \"ChangeCurrentVnfPkgRequest\", or in the Grant response. If applying such change results in an empty list of \n      \"currentVnfExtCpData\" structure instances, the affected instance of \"ExtVirtualLinkInfo\" shall be removed from its \n      parent data structure.\n",
				"type": "object",
				"required": [
					"id",
					"resourceHandle",
					"currentVnfExtCpData"
				],
				"properties": {
					"id": {
						"description": "An identifier with the intention of being globally unique.\n",
						"type": "string"
					},
					"resourceHandle": {
						"required": [
							"resourceId"
						],
						"type": "object",
						"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",
						"properties": {
							"vimConnectionId": {
								"description": "An identifier with the intention of being globally unique.\n",
								"type": "string"
							},
							"resourceProviderId": {
								"description": "An identifier with the intention of being globally unique.\n",
								"type": "string"
							},
							"resourceId": {
								"description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
								"type": "string"
							},
							"vimLevelResourceType": {
								"description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
								"type": "string"
							}
						}
					},
					"extLinkPorts": {
						"description": "Link ports of this VL.\n",
						"type": "array",
						"items": {
							"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. It shall comply with the provisions defined in table 5.5.3.9-1.\nNOTE 1:\tThe use cases UC#4 and UC#5 in Annex A.4 of ETSI GS NFV-IFA 007 provide examples for such a configuration. NOTE 2:\tThe value of \"trunkResourceId\" is scoped by the value of \"vimConnectionId\" in the \"resourceHandle\" attribute.\n",
							"type": "object",
							"required": [
								"id",
								"resourceHandle"
							],
							"properties": {
								"id": {
									"description": "An identifier with the intention of being globally unique.\n",
									"type": "string"
								},
								"resourceHandle": {
									"required": [
										"resourceId"
									],
									"type": "object",
									"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",
									"properties": {
										"vimConnectionId": {
											"description": "An identifier with the intention of being globally unique.\n",
											"type": "string"
										},
										"resourceProviderId": {
											"description": "An identifier with the intention of being globally unique.\n",
											"type": "string"
										},
										"resourceId": {
											"description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
											"type": "string"
										},
										"vimLevelResourceType": {
											"description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
											"type": "string"
										}
									}
								},
								"cpInstanceId": {
									"description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
									"type": "string"
								},
								"secondaryCpInstanceId": {
									"description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
									"type": "string"
								},
								"trunkResourceId": {
									"description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
									"type": "string"
								}
							}
						}
					},
					"currentVnfExtCpData": {
						"description": "Allows the API consumer to read the current CP configuration information for the connection of external CPs  to the external virtual link. See note.\n",
						"type": "array",
						"items": {
							"description": "This type represents configuration information for external CPs created. * NOTE 1: \tIn case this identifier refers to a CPD with trunking enabled, the external CP instances created\n              from this CPD will represent ports in a trunk.\n* NOTE 2: \tWithin one VNF instance, all VNFC instances created from a particular VDU have the same external\n              connectivity. Thus, given a particular value of the \"cpdId\" attribute, there shall be one\n              \"cpConfig\" entry for each VNFC instance that has been or can be created from a VDU which includes\n              a CPD identified by the \"cpdId\" attribute. If the cpConfig represents a subport in a trunk,\n              all \"cpConfig\" entries in this list shall have the same segmentationId, which means they are\n              connected to the same set of external VLs via the trunk.\n* NOTE 3: \tThe map entry value shall be set to \"null\" in order to delete a \"VnfExtCpConfig\" entry identified\n              by a particular key value from the map, i.e. for the disconnection of an existing external\n              CP instance addressed by cpInstanceId in the deleted map entry from a particular external\n              virtual link, and deletion of that instance in case it represents a subport. Deleting the\n              last key from the map removes the affected instance of the \"VnfExtCpData\" structure from\n              its parent data structure.\n",
							"type": "object",
							"required": [
								"cpdId"
							],
							"properties": {
								"cpdId": {
									"description": "An identifier that is unique within a VNF descriptor.\n",
									"type": "string"
								},
								"cpConfig": {
									"description": "Map of instance data that need to be configured on the CP instances created from the respective CPD. The key of the map which identifies the individual VnfExtCpConfig entries is managed by the API consumer. The entries shall be applied by the VNFM according to the rules of JSON Merge Patch (see IETF RFC 7396). See note 2 and note 3.\n",
									"type": "object",
									"additionalProperties": {
										"description": "This type represents an externally provided link port or network address information per instance of an external connection point. In case a link port is provided, the VNFM shall use that link port when connecting the external CP to the external VL. In a link port is not provided, the VNFM shall create a link port on the external VL, and use that link port to connect the external CP to the external VL. * NOTE: The following conditions apply to the attributes \"linkPortId\" and \"cpProtocolData\":\n    1)  Void.\n    2)  At least one of the \"linkPortId\" and \"cpProtocolData\" attributes shall be present for an external\n        CP instance representing a subport that is to be created, or an external CP instance that is to be\n        created by creating the corresponding VNFC or VNF instance during the current or a subsequent LCM\n        operation, or for an existing external CP instance that is to be re-configured or added to a\n        particular external virtual link.\n    3)  If the \"linkPortId\" attribute is absent, the VNFM shall create a link port.\n    4)  If the \"cpProtocolData\" attribute is absent, the \"linkPortId\" attribute shall be provided referencing\n        a pre created link port, and the VNFM can use means outside the scope of the present document to obtain\n        the pre-configured address information for the connection point from the resource representing\n        the link port.\n    5)  If both \"cpProtocolData\" and \"linkportId\" are provided, the API consumer shall ensure that the\n        cpProtocolData can be used with the pre-created link port referenced by \"linkPortId\".\n",
										"anyOf": [{
												"required": [
													"linkPortId"
												]
											},
											{
												"required": [
													"cpProtocolData"
												]
											}
										],
										"type": "object",
										"properties": {
											"parentCpConfigId": {
												"description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
												"type": "string"
											},
											"linkPortId": {
												"description": "An identifier with the intention of being globally unique.\n",
												"type": "string"
											},
											"createExtLinkPort": {
												"description": "Indicates to the VNFM the need to create a dedicated link port for the external CP. If set to True, the VNFM shall create a link port. If set to False, the VNFM shall not create a link port. This attribute is only applicable for external CP instances without a floating IP address that expose a VIP CP instance for which a dedicated IP address is allocated. It shall be present in that case and shall be absent otherwise.\n",
												"type": "boolean"
											},
											"cpProtocolData": {
												"description": "Parameters for configuring the network protocols on the link port that connects the CP to a VL. See note.\n",
												"type": "array",
												"items": {
													"description": "This type represents network protocol data. * NOTE:\tThis attribute allows to signal the addition of further types of layer and protocol\n          in future versions of the present document in a backwards-compatible way. In the current\n          version of the present document, only IP over Ethernet is supported.\n",
													"type": "object",
													"required": [
														"layerProtocol"
													],
													"properties": {
														"layerProtocol": {
															"description": "Identifier of layer(s) and protocol(s). See note.\n",
															"type": "string",
															"enum": [
																"IP_OVER_ETHERNET"
															]
														},
														"ipOverEthernet": {
															"description": "This type represents network address data for IP over Ethernet. * NOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. * NOTE 2:\tExactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present. * NOTE 3:\tIf the CP instance represents a subport in a trunk, segmentationId shall be present.\n          Otherwise it shall not be present.\n* NOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the actual\n          network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header\n          of the packets or it may be an identifier used between the application and the NFVI networking\n          infrastructure to identify the network sub-interface of the trunk port in question. In the latter\n          case the NFVI infrastructure will map this local segmentationId to whatever segmentationId is\n          actually used by the NFVIΓÇÖs transport technology.\n",
															"type": "object",
															"anyOf": [{
																	"required": [
																		"macAddress"
																	]
																},
																{
																	"required": [
																		"ipAddresses"
																	]
																}
															],
															"oneOf": [{
																	"required": [
																		"fixedAddresses"
																	]
																},
																{
																	"required": [
																		"numDynamicAddresses"
																	]
																},
																{
																	"required": [
																		"ipAddressRange"
																	]
																}
															],
															"properties": {
																"macAddress": {
																	"description": "A MAC address. Representation: string that consists of groups of two hexadecimal digits, separated by hyphens or colons.\n",
																	"type": "string",
																	"format": "MAC"
																},
																"segmentationType": {
																	"description": "Specifies the encapsulation type for the traffics coming in and out of the trunk subport. Permitted values: -\tVLAN: the subport uses VLAN as encapsulation type. -\tINHERIT: the subport gets its segmentation type from the network itΓÇÖs connected to. This attribute may be present for CP instances that represent subports in a trunk and shall be absent otherwise. If this attribute is not present for a subport CP instance, default value VLAN shall be used.\n",
																	"type": "string",
																	"enum": [
																		"VLAN",
																		"INHERIT"
																	]
																},
																"segmentationId": {
																	"description": "Identification of the network segment to which the CP instance connects to. See note 3 and note 4.\n",
																	"type": "string"
																},
																"ipAddresses": {
																	"description": "List of IP addresses to assign to the CP instance. Each entry represents IP address data for fixed or dynamic IP address assignment per subnet. If this attribute is not present, no IP address shall be assigned. See note 1.\n",
																	"type": "array",
																	"items": {
																		"type": "object",
																		"required": [
																			"type"
																		],
																		"properties": {
																			"type": {
																				"description": "The type of the IP addresses. Permitted values: IPV4, IPV6.\n",
																				"type": "string",
																				"enum": [
																					"IPV4",
																					"IPV6"
																				]
																			},
																			"fixedAddresses": {
																				"description": "Fixed addresses to assign (from the subnet defined by \"subnetId\" if provided). See note 2.\n",
																				"type": "array",
																				"items": {
																					"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
																					"type": "string",
																					"format": "IP"
																				}
																			},
																			"numDynamicAddresses": {
																				"description": "Number of dynamic addresses to assign (from the subnet defined by \"subnetId\" if provided). See note 2.\n",
																				"type": "integer"
																			},
																			"addressRange": {
																				"description": "An IP address range to be used, e.g. in case of egress connections. In case this attribute is present, IP addresses from the range will be used. See note 2.\n",
																				"type": "object",
																				"required": [
																					"minAddress",
																					"maxAddress"
																				],
																				"properties": {
																					"minAddress": {
																						"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
																						"type": "string",
																						"format": "IP"
																					},
																					"maxAddress": {
																						"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
																						"type": "string",
																						"format": "IP"
																					}
																				}
																			},
																			"subnetId": {
																				"description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
																				"type": "string"
																			}
																		}
																	}
																}
															}
														}
													}
												}
											}
										}
									}
								}
							}
						}
					}
				}
			}
		},
		"modificationsTriggeredByVnfPkgChange": {
			"description": "This type represents attribute modifications that were performed on an \"Individual VNF instance\" resource  when changing the current VNF package. The attributes that can be included consist of those requested to  be modified explicitly in the \"ChangeCurrentVnfPkgRequest\" data structure, and additional attributes of the  \"VnfInstance\" data structure that were modified implicitly during the operation. The \"ModificationsTriggeredByVnfPkgChange\" data type shall comply with the provisions defined in table 5.5.3.21-1.\nNOTE 1:\tThis attribute represents the delta (semantics as per IETF RFC 7396, JSON Merge Patch) between the value \n        of the attribute at the start of the \"Change current VNF package\" operation and the value of the attribute \n        at its completion.\nNOTE 2:\tIf present, this attribute (which depends on the value of the \"vnfdId\" attribute) was modified implicitly \n        during the related operation and contains a copy of the value of the related attribute from the VNFD in the \n        VNF Package identified by the \"vnfdId\" attribute.\n",
			"type": "object",
			"properties": {
				"vnfConfigurableProperties": {
					"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 keyvalue pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 8259. In the following example, a list of key-value pairs with four keys (\"aString\", \"aNumber\", \"anArray\" and \"anObject\") is provided to illustrate that the values associated with different keys can be of different type.\n",
					"type": "object"
				},
				"metadata": {
					"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 keyvalue pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 8259. In the following example, a list of key-value pairs with four keys (\"aString\", \"aNumber\", \"anArray\" and \"anObject\") is provided to illustrate that the values associated with different keys can be of different type.\n",
					"type": "object"
				},
				"extensions": {
					"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 keyvalue pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 8259. In the following example, a list of key-value pairs with four keys (\"aString\", \"aNumber\", \"anArray\" and \"anObject\") is provided to illustrate that the values associated with different keys can be of different type.\n",
					"type": "object"
				},
				"vnfdId": {
					"description": "An identifier with the intention of being globally unique.\n",
					"type": "string"
				},
				"vnfProvider": {
					"description": "If present, this attribute signals the new value of the \"vnfProvider\" attribute in \"VnfInstance\". See note 2.\n",
					"type": "string"
				},
				"vnfProductName": {
					"description": "If present, this attribute signals the new value of the \"vnfProductName\" attribute in \"VnfInstance\". See note 2.\n",
					"type": "string"
				},
				"vnfSoftwareVersion": {
					"description": "A version.\n",
					"type": "string"
				},
				"vnfdVersion": {
					"description": "A version.\n",
					"type": "string"
				}
			}
		},
		"error": {
			"description": "The definition of the general \"ProblemDetails\" data structure from IETF RFC 7807 is reproduced inthis structure. Compared to the general framework defined in IETF RFC 7807, 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 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.\n",
			"type": "object",
			"required": [
				"status",
				"detail"
			],
			"properties": {
				"type": {
					"description": "A URI reference according to IETF RFC 3986 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",
					"type": "string",
					"format": "URI"
				},
				"title": {
					"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",
					"type": "string"
				},
				"status": {
					"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",
					"type": "integer"
				},
				"detail": {
					"description": "A human-readable explanation specific to this occurrence of the problem.\n",
					"type": "string"
				},
				"instance": {
					"description": "A URI reference that identifies the specific occurrence of the problem. It may yield further information if dereferenced.\n",
					"type": "string",
					"format": "URI"
				}
			}
		},
		"_links": {
			"description": "This type represents the links to resources that a notification can contain.\n",
			"type": "object",
			"required": [
				"vnfInstance",
				"subscription"
			],
			"properties": {
				"vnfInstance": {
					"description": "This type represents a link to a resource in a notification, using an absolute or relative URI.\n",
					"type": "object",
					"required": [
						"href"
					],
					"properties": {
						"href": {
							"description": "String formatted according to IETF RFC 3986.\n",
							"type": "string"
						}
					}
				},
				"subscription": {
					"description": "This type represents a link to a resource in a notification, using an absolute or relative URI.\n",
					"type": "object",
					"required": [
						"href"
					],
					"properties": {
						"href": {
							"description": "String formatted according to IETF RFC 3986.\n",
							"type": "string"
						}
					}
				},
				"vnfLcmOpOcc": {
					"description": "This type represents a link to a resource in a notification, using an absolute or relative URI.\n",
					"type": "object",
					"required": [
						"href"
					],
					"properties": {
						"href": {
							"description": "String formatted according to IETF RFC 3986.\n",
							"type": "string"
						}
					}
				}
			}
		}
	}
}