Defines descriptors of virtual compute resources to be used by the VNF.
References to Vdus that are part of this group.
Describes external interface(s) exposed by this VNF enabling connection with a VL.
Describes CPU, Memory and acceleration requirements of the Virtualisation Container realising this Vdu.
Describes storage requirements for a VirtualStorage instance attached to the virtualisation container created from virtualComputeDesc defined for this Vdu. support:
Describes the software image which is directly loaded on the virtualisation container realising this Vdu. NOTE: More software images can be attached to the virtualisation container using VirtualStorage resources.
Identifies a flavour within a VnfVirtualLinkDesc.
Defines the internal VLD along with additional data which is used in this DF. NOTE 1: This allows for different VNF internal topologies between DFs. NOTE 2: virtualLinkProfile needs to be provided for all VLs that the CPs of the VDUs in the VDU profiles connect to.
Uniquely references a VLD.
Reference to the internal Virtual Link Descriptor (VLD) to which CPs instantiated from this external CP Descriptor (CPD) connect.
An Anfd (Allotted Network Function Descriptor) is designed to run on top of some sharable NetworkFunction. It si therefore related to the NfD at design time. The NetworkFunctionDesc can be designed to have some number (zero to many).
An AnfInstance (Allotted Network Function Instance) runs on top of some sharable NetworkFunction. The NetworkFunctionInstance can have some number (zero to many) of AnfInstances running on it.
Describes the associated elements of a VNFD for a certain purpose during VNF lifecycle management. A few quick observations 1. Using integer for number. Jessie: Created a primitive called Number which is a superset of integer and real. 2. created a datatype called enum. Deleted enum. Created "enums" where needed. 3. Seems like we are just using ETSI (beyound what we have in the works). Jessie: It appears that way. 4. Is monitoring param a class or a data type? Jessie: It is a datatype. Due to it's relationship to event, maybe a class?? 5. Class versus datatype?? ResourceDesc??? . can protocol be enumerated? - yes. Values? Change addrestype to enumeration . Change L2addressData and l3addressData to 0..1 given "only present...." definition orchestration Status - Pending, Created, Active... - Christina will query. . onboardedVnfPkgInfoId - need class for VnfPkg? Yes - probably need more discussion - tied to vnf model and internal model. Vnf Instance related to vnf descriptor or onboarding pkg descriptor Will not try to push this out into R3 - save for R4 ONAP has a VirtualLinkDesc, not NetworkLink or LinkDesc This will probably need to move to common Attributes in violet - not necessary in Infomodell - can be retrieved from Vnfd. Attributes in beige - added or changed AnfInstanceRunsOnSharableNfInstance represents the "ProvidedBy". The Uses relationship is covered by the service instance expressing the sharable infrasturcture capability which has a relationship to the sharable resource. The ANF instance also has a relationship to the same sharable resource. - Pnfs cannot run on a Vnf or Anf - Pnfs cannot run on Pnfs, etc. Only one of OsContainerDesc or VirtualComputeDesc per VDU A Vnfd, or VNF Descriptor, is template which describes a VNF in terms of deployment and operational behaviour requirements. It also contains connectivity, interface and virtualised resource requirements. Identifier of this VNFD information element. This attribute shall be globally unique. NOTE: The VNFD Identifier shall be used as the unique identifier of the VNF Package that contains this VNFD. Any modification of the content of the VNFD or the VNF Package shall result in a new VNFD Identifier. Provider of the VNF and of the VNFD. Name to identify the VNF Product. Invariant for the VNF Product lifetime. Software version of the VNF. This is changed when there is any change to the software that is included in the VNF Package. Identifies the version of the VNFD. Human readable name for the VNF Product. Can change during the VNF Product lifetime. Human readable description of the VNF Product. Can change during the VNF Product lifetime. Identifies VNFM(s) compatible with the VNF described in this version of the VNFD. Use the name of micro-service of the vnfm drive. For vendor specific VNFM, the value composes of "vendorname" and "vnfmdriver", e.g. "mycompanyvnfmdriver"; for generic VNFM, the value is "gvnfmdriver". Information about localization languages of the VNF (includes e.g. strings in the VNFD). Refer to ISO936 https://www.iso.org/iso-639-language-codes.html NOTE: This allows to provide one or more localization languages to support selecting a specific localization language at VNF instantiation time. Information about localization languages of the VNF (includes e.g. strings in the VNFD). Refer to ISO936 https://www.iso.org/iso-639-language-codes.html NOTE: This allows to provide one or more localization languages to support selecting a specific localization language at VNF instantiation time. Virtualisation Deployment Unit. Defines descriptors of virtual compute resources to be used by the VNF when each of the VNFC instances of the VNF is intended to be deployed in a single VM. Defines descriptors of virtual storage resources to be used by the VNF. Defines descriptors of container compute resources to be used by the VNF when the VDUs of the VNF are realized by a set of OS Containers sharing the same host and same networking namespace. Defines descriptors of software images to be used by the VNF. NOTE: This shall be used to describe both the software image loaded on the virtualization container used to realize a VDU and the software images to be stored on VirtualStorage resources (e.g., volumes) attached to a virtualization container. Represents the type of network connectivity mandated by the VNF provider between two or more CPs which includes at least one internal CP. Defines security group rules to be used by the VNF. Describes external interface(s) exposed by this VNF enabling connection with a VL. Describes virtual IP addresses to be shared among instances of connection points. Describes a virtual connection point allowing to access a set of VNFC instances (based on their respective VDUs). Describes specific DF(s) of a VNF with specific requirements for capacity and performance. Describes the configurable properties of the VNF (e.g. related to auto scaling and auto healing). Defines the VNF-specific extension and metadata attributes of the VnfInfo that are writeable via the ModifyVnfInfo operation. Includes a list of events and corresponding management scripts performed for the VNF. Declares the VNF indicators that are supported by this VNF. Rule that determines when a scaling action needs to be triggered on a VNF instance e.g. based on certain VNF indicator values or VNF indicator value changes or a combination of VNF indicator value(s) and monitoring parameter(s). Information used for performing the change of the current VNF Package. More than one VNF Package Change Info construct is possible to cater the possibility that changes of the current VNF Package can be performed for different source VNFDs. Provides information used for the coordination in VNF LCM operations. Identifies the MCIOP(s) in the VNF package, used in containerized workload management, when the VNF is realized by a set of OS containers. The Virtualisation Deployment Unit (VDU) is a construct supporting the description of the deployment and operational behavior of a VNFC. A VNFC instance created based on the VDU maps to a single instance of atomic deployable unit, represented by a single VM for hypervisor-based virtualisation, or represented by one or a set of OS containers for OS virtualisation . A VNFC will only be in one VNFDesc. If a vendor wants to use the VNFC in mupliple VNFDesc (their product) they can do so, but it will be 'repeated'. Unique identifier of this Vdu in VNFD. Human readable name of the Vdu. Human readable description of the Vdu. Boot order of valid boot devices. "key/name" indicates the the boot index "value" references a descriptor from which a valid boot device is created e.g. VirtualStorageDesc from which a VirtualStorage instance is created. NOTE: If no boot order is defined the default boot order defined in the VIM or NFVI shall be used. Describes constraints on the NFVI for the VNFC instance(s) created from this Vdu. For example, aspects of a secure hosting environment for the VNFC instance that involve additional entities or processes. "key/name" includes "AvailabilityZone", "HostAggregates". NOTE: These are constraints other than stipulating that a VNFC instance has access to a certain resource, as a prerequisite to instantiation. The attributes virtualComputeDesc and virtualStorageDesc define the resources required for instantiation of the VNFC instance. Defines the virtualised resources monitoring parameters on VDU level. Describes the information (e.g. URL) about the scripts, config drive metadata, etc. which can be used during Vdu booting process. Describes the configurable properties of all VNFC instances based on this VDU. Contains a string or a URL to a file contained in the VNF package used to customize a virtualised compute resource at boot time. The bootData may contain variable parts that are replaced by deployment specific values before being sent to the VIM. NOTE: The parameters of each variable part shall be declared in the VnfLcmOperationsConfiguration information element as "volatile" parameters available to the bootData template during the respective VNF lifecycle management operation execution and/or in the extension attribute of the VnfInfoModifiableAttributes information element as "persistent" parameters available to the bootData template during the lifetime of the VNF instance. For VNF lifecycle management operations resulting in multiple VNFC instantiations, the VNFM supports the means to provide the appropriate parameters to appropriate VNFC instances Experimental Describes network connectivity between a VNFC instance (based on this Vdu) and an internal Virtual Link (VL). Describes CPU, Memory and acceleration requirements of the Virtualisation Container realising this Vdu. Describes CPU, memory requirements and limits, and software images of the OS Containers realizing this Vdu corresponding to OS Containers sharing the same host and same network namespace. Each unique identifier is referenced only once within one VDU. Describes storage requirements for a VirtualStorage instance attached to the virtualisation container created from virtualComputeDesc defined for this Vdu. Describes the software image which is directly loaded on the virtualisation container realising this Vdu. NOTE: More software images can be attached to the virtualisation container using VirtualStorage resources. The SwImageDesc information element describes requested additional capability for a particular VDU. Such a capability may be for acceleration or specific tasks. Storage not necessarily related to the compute, may be Network Attached Storage (NAS) The identifier of this software image. The name of this software image. The version of this software image. The provider of this software image. If not present the provider of the software image is assumed to be same as the VNF provider. The container format describes the container file format in which software image is provided. The disk format of a software image is the format of the underlying disk image. The minimal RAM requirement for this software image. The value of the "size" attribute of VirtualMemoryData of the Vdu referencing this SwImageDesc shall not be smaller than the value of minRam. The minimal disk size requirement for this software image. The value of the "size of storage" attribute of the VirtualStorageDesc referencing this SwImageDesc shall not be smaller than the value of minDisk. The size of the software image. Identifies the operating system used in the software image. This attribute may also identify if a 32 bit or 64 bit software image is used. Identifies the virtualisation environments (e.g. hypervisor) compatible with this software image. This is a reference to the actual software image. The reference can be relative to the root of the VNF Package or can be a URL The VduProfile describes additional instantiation data for a given VDU used in a DF. Minimum number of instances of the VNFC based on this VDU that is permitted to exist for this flavour. Shall be zero or greater. Maximum number of instances of the VNFC based on this VDU that is permitted to exist for this flavour. Shall be zero or greater. Specifies affinity or anti-affinity rules applicable between the virtualization containers (e.g. virtual machines) to be created based on this VDU. When the cardinality is greater than 1, both affinity rule(s) and anti-affinity rule(s) with different scopes (e.g. "Affinity with the scope resource zone and anti-affinity with the scope NFVI node") are applicable to the virtualization containers (e.g. virtual machines) to be created based on this VDU. When the cardinality is greater than 1, both affinity rule(s) and anti-affinity rule(s) with different scopes (e.g. "Affinity with the scope resource zone and anti-affinity with the scope NFVI node") are applicable to the virtualization containers (e.g. virtual machines) to be created based on this VDU. Identifier(s) of the affinity or anti-affinity group(s) the VDU belongs to. NOTE: Each identifier references an affinity or anti-affinity group which expresses affinity or anti-affinity relationships between the virtualisation container(s) (e.g. virtual machine(s)) to be created using this VDU and the virtualisation container(s) (e.g. virtual machine(s)) to be created using other VDU(s) in the same group. Watchdog action to be triggered by the VIM for the VNF in case the heart beat fails, e.g. reset or hard shutdown, etc. Timeout value for the VNFM to wait before the successful booting up of the VDU. VNFD needs to specify the security group name {security_groups} for each VDU. Additional expansion requirements for Infrastructure layer, e.g. HA property (Host Aggregate ). The VirtualComputeDesc information element supports the specification of requirements related to virtual compute resources. Unique identifier of this VirtualComputeDesc in the VNFD Specifies requirements for additional capabilities. These may be for a range of purposes. One example is acceleration related capabilities. Specifies compute requirements. The virtual memory of the virtualised compute. The virtual CPU(s) of the virtualised compute. The associated logical node requirements. The local or ephemeral disk(s) of the virtualised compute. The VirtualStorageDesc information element supports the specifications of requirements related to persistent virtual storage resources. Ephemeral virtual storage is specified in VirtualComputeDesc information element. Unique identifier of this VirtualStorageDesc in the VNFD. Type of virtualised storage resource (BLOCK, OBJECT, FILE). Size of virtualised storage resource (e.g. size of volume, in GB). Specifies the details of block storage. It shall be present when the "typeOfStorage" attribute is set to "BLOCK". It shall be absent otherwise. Specifies the details of object storage. It shall be present when the "typeOfStorage" attribute is set to "OBJECT". It shall be absent Specifies the details of file storage. It shall be present when the "typeOfStorage" attribute is set to "FILE". It shall be absent otherwise. Indicating whether a vDisk is a shared volume in VNFD. Describe storage Qos requirements. Describe volume type. Indicates whether the virtual storage descriptor shall be used as template, i.e. if the virtual storage resource shall be instantiated per VNFC instance. If the value is true (default), a persistent virtual storage resource shall be instantiated for each VNFC instance that is based on a VDU referring to this virtual storage descriptor. If the value is false, a single persistent virtual storage resource shall be instantiated with a lifetime independent of the lifetime of individual VNFC instances based on a VDU referring to this virtual storage descriptor. A VduCpd information element is a type of Cpd and describes network connectivity between a VNFC instance (based on this VDU) and an internal VL. Bitrate requirement on this CP. Describes the name of the vNIC this CP attaches to, e.g. eth0. It will be configured during the Vdu booting process. Describes the order to create the vNIC within the scope of this Vdu. Describes the type of the virtual network interface realizing the CPs instantiated from this CPD. This is used to determine which mechanism driver(s) to be used to bind the port. VALUES: • NORMAL • MACVTAP • DIRECT • BAREMETAL • VIRTIO-FORWARDER • DIRECT-PHYSICAL • SMART-NIC Additional values of the attribute for VDUs realized by one or set of OS containers: • BRIDGE • IPVLAN • LOOPBACK • MACVLAN • PTP • VLAN • HOST-DEVICE Specifies requirements on a virtual network interface realising the CPs instantiated from this CPD. Define the port anti-affinity group ID for each SR-IOV type vNIC. Multiple vNICs in the same anti-affinity group must belong to the same virtual network, and the number of vNICs in the same anti-affinity group cannot exceed two. VNFD needs to specify the security group name {security_groups} for each vNic. VNFD needs to specify whether to enable security group for the vNic. Describe the Qos requirements of the VduCpd. Reference(s) of the Virtual Link Descriptor to which this Connection Point Descriptor(s) connects. For specifying floating IP(s) to be shared among Cpds, which are reserved for vnfReservedCpd described in the VNFD. The VnfDf describes a specific deployment version of a VNF. Identifier of this DF within the VNFD. Human readable description of the DF. This attribute references the "instantiationLevel" entry which defines the default instantiation level for this DF. It shall be present if there are multiple "instantiationLevel" entries. Specifies the virtualised resource related performance metrics to be tracked by the VNFM. Defines the internal VLD along with additional data which is used in this DF. NOTE 1: This allows for different VNF internal topologies between DFs. NOTE 2: virtualLinkProfile needs to be provided for all VLs that the CPs of the VDUs in the VDU profiles connect to. Describes the various levels of resources that can be used to instantiate the VNF using this flavour. Examples: Small, Medium, Large. If there is only one "instantiationLevel" entry, it shall be treated as the default instantiation level for this DF. Specifies affinity or anti-affinity relationship applicable between the virtualisation containers (e.g. virtual machines) to be created using different VDUs or internal VLs to be created using different VnfVirtualLinkDesc(s) in the same affinity or anti-affinity group. NOTE: In the present specification, including either VDU(s) or VnfVirtualLinkDesc(s) into the same affinity or anti-affinity group is supported. Extension to support including both VDU(s) and VnfVirtualLinkDesc(s) into the same affinity or anti-affinity group is left for future specification. The scaling aspects supported by this DF of the VNF. scalingAspect shall be present if the VNF supports scaling. Describes additional instantiation data for the VDUs used in this flavor. Declares the VNF indicators that are supported by this VNF (specific to this DF). Indicates which interfaces the VNF produces and provides additional details on how to access the interface endpoints. Describes additional instantiation data for the MCIOPs used in this deployment flavour. This attribute shall be present if the DF references (via the vduProfile) containerized workloads based on a MCIOP. A VnfExtCpd is a type of Cpd and describes an external interface, a.k.a external CP, exposed by this VNF enabling connection with a VL. When the VnfExtCpd is mapped to a VduCpd, the values for the attributes type, subType and description shall be identical for both elements. References the internal Virtual Link Descriptor (VLD) to which CPs instantiated from this external CP Descriptor (CPD) connect. One and only one of the following attributes shall be present: intVirtualLinkDesc or intCpd or vipCpd. References the internal VDU CPD which is used to instantiate internal CPs. These internal CPs are, in turn, exposed as external CPs defined by this external CPD. One and only one of the following attributes shall be present: intVirtualLinkDesc or intCpd or vipCpd. References the VIP CPD which is used to instantiate CPs to hold virtual IP addresses. These CPs are, in turn, exposed as external CPs defined by this external CPD. One and only one of the following attributes shall be present: intVirtualLinkDesc or intCpd or vipCpd . Specifies requirements on a virtual network interface realising the CPs instantiated from this CPD. NOTE: In case of referencing an intCpd via its identifier, the virtualNetworkInterfaceRequirements attribute of the referenced intCpd applies. References the Virtual CPD which is used to describe a virtual connection point allowing to access a set of VNFC instances (based on their respective VDUs). The VnfIndicator information element defines the indicator the VNF supports. Unique identifier. The human readable name of the VnfIndicator. Defines the allowed values or value ranges of this indicator. Describe the source of the indicator. This tells the consumer where to send the subscription request. The VirtualLinkDescFlavour describes additional instantiation data for a given internal VL used in a DF. QoS of the VL. Identifies a flavour within a VnfVirtualLinkDesc. This class specifies requirements on a virtual network interface. Provides a human readable name for the requirement. Provides a human readable description of the requirement. Indicates whether fulfilling the constraint is mandatory (TRUE) for successful operation or desirable (FALSE). The network interface requirements. An element from an array of key-value pairs that articulate the network interface deployment requirements This references (couples) the CPD with any logical node I/O requirements (for network devices) that may have been created. Linking these attributes is necessary so that so that I/O requirements that need to be articulated at the logical node level can be associated with the network interface requirements associated with the CPD. The InstantiationLevel class describes a given level of resources to be instantiated within a DF in term of the number of VNFC instances to be created from each VDU. All the VDUs referenced in the level shall be part of the corresponding DF and their number shall be within the range (min/max) for this DF. Uniquely identifies a level with the DF. Human readable description of the level. Represents for each aspect the scale level that corresponds to this instantiation level. scaleInfo shall be present if the VNF supports scaling. Indicates the number of instance of this VDU to deploy for this level. Specifies bitrate requirements applicable to virtual links created from particular virtual link descriptors for this level. NOTE: If not present, it is assumed that the bitrate requirements can be derived from those specified in the VduCpd instances applicable to the internal VL. If present in both the InstantiationLevel and the VduCpd instances applicable to the internal VL, the highest value takes precedence. The VduLevel information element indicates for a given VDU in a given level the number of instances to deploy. Number of instances of VNFC based on this VDU to deploy for an instantiation level or for a scaling delta. Uniquely identifies a VDU. A VipCpd is a type of Cpd and describes a requirement to allocate one or a set of virtual IP addresses. A VipCpd inherits from the Cpd Class . All attributes of the Cpd are also attributes of the VipCpd. When intCpds are indicated, instances of VduCps created from those intCpds share the addresses created from the VipCpd. When vnfExtCpds are indicated, instances of VnfExtCps created from those vnfExtCpds share the addresses created from the VipCpd. References the internal VDU CPD which is used to instantiate internal CPs. These internal CPs share the virtual IP addresses allocated when a VipCp instance is created from the VipCpd. References the VNF external CPD which is used to instantiate external CPs. These external CPs share the virtual IP addresses allocated when a VipCp instance is created from the VipCpd. It indicates the function the virtual IP address is used for. Describes an external CP exposed by a VNF. An implementation of an NF that can be deployed on a Network Function Virtualisation Infrastructure (NFVI). name to identify the VNF Product, invariant for the VNF Product lifetime provider of the VNF model Software version of the VNF. This is changed when there is any change to the software that is included in the VNF package identifier of the specific VNF package on which the VNF instance is based availability zone information of the VNF instance indicator for whether the resource is considered operational. Valid values are in-service-path and out-of-service-path. whether the VNF instance is instantiated oam ip address, ipv4 oam ip address, ipv6 information specific to an instantiated VNF instance, e.g., vm information whether the VNF instance is in maintenance mode, if yes, DCAE will not observe alarms/traps, etc. Indicates whether the closed loop function is enabled or disabled. whether this VNF is accessed using SSH indicator for whether autoHeal and autoScale is enabled Identifier of the policy which has the naming logic for this VNF instance Identifier of the policy which provides homing conditions. Relatonship to the VNF components that are part of this VNF. Relationship to the VNF descriptor Relationship to VnfVirtualLink IP address between VNF and VNFM. An internal component of a VNF providing a VNF Provider a defined sub-set of that VNF's functionality, with the main characteristic that a single instance of this component maps 1:1 against a single Virtualisation Container. identifier of the NFC instance short code of the NFC instance description of the NFC instance identifier of the model of the NFC instance layer-3 interface addresses, ipv4 layer-3 interface addresses, ipv6 operating status of the VM valid value example: STARTED (POWER_ON), STOPPED (POWER_OFF) whether the NFC instance is in maintenance mode, if yes, DCAE will not observe alarms/traps, etc. whether closed loop function is enabled An intelligent or human readable name of the vnfc instance. Multiple names are possible. Reference to the connection points of the vnfc Identifier of the policy which has the naming logic for this VNFC instance English description of network function component that the specific VNFC deployment is providing. indicator for whether the resource is considered operational. Valid values are in-service-path and out-of-service-path. whether the VNFC instance is instantiated Whether closed loop capabilities are enabled for this or not. Reference to the VDU An Anfd is the (Allotted Network Function) is a template which describes an ANF in terms of deploymnet and operational behaviour requiremnets. The VirtualLinkProfile describes additional instantiation data for a given VL used in a DF. Uniquely identifies this VirtualLinkProfile class Specifies affinity or anti-affinity rules applicable between the VLs based on this VnfVirtualLinkDesc. When the cardinality is greater than 1, both affinity rule(s) and anti-affinity rule(s) with different scopes are applicable to the VLs based on this VnfVirtualLinkDesc. Specifies the minimum bitrate requirements for a VL instantiated according to this profile. Specifies the minimum bitrate requirements for a VL instantiated according to this profile. Identifies a flavour within the VnfVirtualLinkDesc. Identifies an affinity or anti-affinity group the VLs instantiated according to the VlProfile belong to. NOTE : Each identifier references an affinity or anti-affinity group which expresses affinity or anti-affinity relationship between the VL(s) using this VirtualLinkProfile and the VL(s) using other VirtualLinkProfile(s) in the same group. Uniquely references a VLD. Specifies the protocol data for a VL instantiated according to this profile. Cardinality 0 is used when no protocol data needs to be specified. The ScalingAspect class describes the details of an aspect used for horizontal scaling. Unique identifier of this aspect in the VNFD. Human readable name of the aspect. Human readable description of the aspect. A graph of logical links connecting NF nodes,where at least one node is a VNF, for the purpose of describing traffic flow between these network functions Identier of this Vnffg class. Identifier of the constituent NFs of the VNFFG Identifier(s) of the constituent VL instance(s) of the VNFFG. Identifiers of the CP instances attached to the constituent VNFs and PNFs or the sap instances of the VNFFG. NOTE: It indicates an exhaustive list of all the CP instances and SAP instances of the VNFFG. Information on the NFPs of this VNFFG. A software image This information element describes compute, memory and I/O requirements that are to be associated with the logical node of infrastructure. The logical node requirements are a sub-component of the VDU level requirements. As an example for illustration purposes, a logical node correlates to the concept of a NUMA cell in libvirt terminology. Identifies this set of logical node requirements. The logical node-level compute, memory and I/O requirements. An array of key-value pairs that articulate the deployment requirements. This could include the number of CPU cores on this logical node, a memory configuration specific to a logical node (e.g. such as available in the Linux kernel via the libnuma library) or a requirement related to the association of an I/O device with the logical node. Represents the type of network connectivity mandated by the VNF vendor between two or more Connection Points which includes at least one Internal Connection Point. Specifies the virtualised resource related performance metrics on VLD level to be tracked by the VNFM. Describes a specific flavour of the VL with specific bitrate requirements. Security group rule specifies the matching criteria for the ingress and/or egress traffic to/from the visited connection points. If an ingress traffic is accepted, the corresponding egress response shall be allowed, regardless of the security group rules on the egress direction. If an egress traffic is allowed, the corresponding ingress response shall be accepted, regardless of the security group rules on the ingress direction. The design of security group rule follows a permissive model where all security group rules applied to a CP are dealt with in an "OR" logic fashion, i.e. the traffic is allowed if it matches any security group rule applied to this CP. Identifier of the security group rule. Human readable description of the security group rule The direction in which the security group rule is applied. Indicates the protocol carried over the Ethernet layer. Indicates the protocol carried over the IP layer. Permitted values: any protocol defined in the IANA protocol registry, e.g. TCP, UDP, ICMP, etc. See https://www.iana.org/assignments/protocol-numbers/protocol-numbers.xhtml Note: IFA011 defines this as an enum, but as the list is not complete, made this a string. Indicates minimum port number in the range that is matched by the security group rule. If a value is provided at design-time, this value may be overridden at run-time based on other deployment requirements or constraints. Indicates maximum port number in the range that is matched by the security group rule. If a value is provided at design-time, this value may be overridden at run-time based on other deployment requirements or constraints. An Allotted Network Function Instance is a network function provided (or allotted) by some service instance. The allotted network function may be incorporated into the topology of some consuming service like other network functions. Link back to more information in the controller Concurrency value Orchestration status Indicator for whether the resource is considered operational Store the id of the access provider of this allotted-resource. Store the id of the access client of this allotted-resource. Store the id of the access topology of this allotted-resource. Store the id of the access node of this allotted-resource. Store the id of the access ltp of this allotted-resource. Store the cvlan of this allotted-resource. Store the vpn-name of this allotted-resource. The VnfInterfaceDetails information element specifies the details of an interface produced by the VNF on the Ve-Vnfm reference point. References one or more CPDs from which to instantiate external CPs through which interface endpoints on the VNF side can be reached by the VNFM. Provide additional data to access the interface endpoint (e.g. API URI prefix). Specifies an interface produced by the VNF. The ChecksumData information element supports providing information about the result of performing a checksum operation over some arbitrary data. Species the algorithm used to obtain the checksum value. Contains the result of applying the algorithm indicated by the algorithm attribute to the data to which this ChecksumData refers. A VnfPackageChangeInfo information element describes the processes and rules to be used for performing the resource related tasks while assisting the "change current VNF Package" to change a VNF instance to a different VNF Package (destination package). When creating a VNF package, the VNF vendor can include VnfPackageChangeInfo information elements in the package which allow the package to act as a source package or as a destination package for a modification in relation to another package, which has been created earlier or at the same time. To populate a VnfPackageChangeInfo information element and the underlying related information elements, knowledge of both the source package and the destination package is required. Information to identify the source and destination VNFD for the change, and the related deployment flavours. References the ChangeCurrentVnfPackageOpConfig information element that defines the valid additional parameters for the change. Specifies the type of modification resulting from transitioning from srcVnfdId to dstVnfdId. The possible values are: UP - indicating that the destination VNF version is newer than the source version, DOWN - indicating that the destination VNF version is older than the source version. A VNF provider may define additional information to qualify further the change between the two versions, such as "VNF upgrade", "VNF update", "VNF downgrade", etc. Mapping information related to identifiers of components in source VNFD and destination VNFD that concern to the change process. References a lifecycle management script that is executed as part of this "change current VNF Package" process. References applicable VNF LCM operation coordination actions. Identifies the deployment flavour in the destination VNF package for which this change applies. The flavour ID is defined in the destination VNF package. This information element defines the sets of information needed for a coordination action in a VNF lifecycle management operation. Identifies the specific VNF LCM operation coordination action. Human readable description of the coordination action. Specifies the type of the endpoint exposing the LCM operation coordination such as other operations supporting or management systems (e.g. an EM) or the VNF instance. Allowed values: • MGMT: coordination with other operation supporting management systems. • VNF: coordination with the VNF instance. Indicates the coordination stage during the VNF LCM operation. Input information needed by the external coordinating entity. A VirtualCpd is a type of Cpd and describes a requirement to create a virtual connection point allowing the access to a number of VNFC instances (based on their respective VDUs). References the VDU(s) which implement this service. Additional service identification data of the VirtualCp exposed to NFV-MANO. The OsContainerDesc information element describes the members properties of a set of co-located container compute resources when these are realizing a VDU. Unique identifier of this OsContainerDesc in the VNFD. Number of CPU resources requested for the container (e.g. in milli-CPU-s) Amount of memory resources requested for the container (e.g. in MB). Size of ephemeral storage resources requested for the container (e.g. in GB). An array of key-value pairs of extended resources required by the container. Number of CPU resources the container can maximally use (e.g. in milli-CPU). Amount of memory resources the container can maximum use (e.g. in MB). Size of ephemeral storage resources the container can maximum use (e.g. in GB). Describes the software image realizing this OS container. Contains a string or a URL to a file contained in the VNF package used to customize a container resource at boot time. The bootData may contain variable parts that are replaced by deployment specific values before being sent. Links to virtualStorageDesc-s of the Vdu. The storages represented by the linked VirtualStorageDesc-s are attached to the OS Container as volumes. Shall be present in case the OS container requires storage resources. Specifies the virtualised resource related performance metrics on the OsContainerDesc level to be tracked by the VNFM A Managed Container Infrastructure Object Package (MCIOP) is a hierarchical aggregate of information objects for OS container management and orchestration. Multiple MCIOPs can be included in a VNF Package. The MciopProfile information element provides properties of the MCIOP which are used during deployment of containerized workloads based on a MCIOP, associated to a VNF deployment flavour. Identifies the MCIOP in the VNF package. Indicates the order in which this MCIOP shall be deployed in relation to other MCIOPs. A lower value specifies an earlier deployment. References the affinity or anti-affinity group(s) the MCIOP belongs to. List of VDUs which are associated to this MCIOP and which are deployed using this MCIOP. This information element describes requested additional capability for a particular VDU. Such a capability may be for acceleration or specific tasks. Indicates whether the requested additional capability is mandatory for successful operation. Identifies a requested additional capability for the VDU. Identifies the minimum version of the requested additional capability. Identifies the preferred version of the requested additional capability. Identifies specific attributes, dependent on the requested additional capability type. The VirtualMemoryData information element supports the specification of requirements related to virtual memory of a virtual compute resource. Amount of virtual Memory (e.g. in MB). The memory core oversubscription policy in terms of virtual memory to physical memory on the platform. The cardinality can be 0 during the allocation request, if no particular value is requested. Array of key-value pair requirements on the memory for the VDU. It specifies the memory allocation to be cognisant of the relevant process/core allocation. The cardinality can be 0 during the allocation request, if no particular value is requested. The VirtualCpuData information element supports the specification of requirements related to virtual CPU(s) of a virtual compute resource. CPU architecture type. Examples are x86, ARM. The cardinality can be 0 during the allocation request, if no particular CPU architecture type is requested. Number of virtual CPUs. Minimum virtual CPU clock rate (e.g. in MHz). The cardinality can be 0 during the allocation request, if no particular value is requested. The CPU core oversubscription policy e.g. the relation of virtual CPU cores to physical CPU cores/threads. The cardinality can be 0 during the allocation request, if no particular value is requested. Array of key-value pair requirements on the Compute (CPU) for the VDU. The virtual CPU pinning configuration for the virtualised compute resource. The VirtualCpuPinningData information element supports the specification of requirements related to the virtual CPU pinning configuration of a virtual compute resource. The policy can take values of "static" or "dynamic". In case of "static" the virtual CPU cores are requested to be allocated to logical CPU cores according to the rules defined in virtualCpuPinningRules. In case of "dynamic" the allocation of virtual CPU cores to logical CPU cores is decided by the VIM. (e.g.: SMT (Simultaneous Multi-Threading) requirements). A list of rules that should be considered during the allocation of the virtual CPUs to logical CPUs in case of "static" virtualCpuPinningPolicy. This information element provides a means to define in the VNFD attributes that represent the configurable properties of a VNF. Configurable properties can be standardized as listed below (e.g. related to auto scaling, auto healing and interface configuration), or can be VNF-specific as defined by the VNF provider. For a VNF instance, the value of these properties can be queried and modified through the VNFM, using the Query VNF and Modify VNF Information operations. Modifying these values affects directly the configuration of an existing VNF instance. If a configurable property is defined in the VNFD, an initial value may be defined as well. It permits to enable (TRUE)/disable (FALSE) the auto-scaling functionality. NOTE: A cardinality of "0" indicates that configuring this present VNF property is not supported. It permits to enable (TRUE)/disable (FALSE) the auto-healing functionality. NOTE: A cardinality of "0" indicates that configuring this present VNF property is not supported. Contains information enabling access to the NFV-MANO interfaces produced by the VNFM (e.g. URIs and credentials) Contains information to enable discovery of the authorization server protecting access to VNFM interface Contains information to enable discovery of the authorization server to validate the access tokens provided by the VNFM when the VNFM accesses the VNF interfaces, if that functionality (token introspection) is supported by the authorization server. This datatype defines the VNF-specific extension and metadata attributes of the VnfInfo that are writeable via the ModifyVnfInfo operation. All additional VNF-specific attributes of VnfInfo that affect the lifecycle management of a VNF instance. For each VNF instance, these attributes are stored persistently by the VNFM and can be queried and modified through the VNFM. These attributes are intended to be consumed by the VNFM or by the lifecycle management scripts during the execution of VNF lifecycle management operations. Modifying these values has no direct effect on the VNF instance; however, modified values can be considered during subsequent VNF lifecycle management operations, which means that the modified values can indirectly affect the configuration of the VNF instance. Additional VNF-specific attributes of VnfInfo that provide metadata describing the VNF instance and that are defined by the VNF provider. See note 2. For each VNF instance, these attributes are stored persistently by the VNFM and can be queried and modified through the VNFM. These attributes are intended to provide information to functional blocks external to the VNFM and will not be used by the VNFM or the VNF lifecycle management scripts when executing lifecycle management operations. Modifying these attributes has no effect on the VNF instance. It only affects the attribute values stored by the VNFM. Describes VNF lifecycle event(s) or an external stimulus detected on a VNFM reference point. Describes the transition VNF lifecycle event(s) that cannot be mapped to any of the enumerated values defined for the event attribute. NOTE: At least one of these two attributes shall be included. Information to locate a VNF LCM script (e.g. written in a DSL as specified in requirement VNF_PACK.LCM.001) triggered to react to one of the events listed in the event attribute. Defines the domain specific language (i.e. the type) of script that is provided. Types of scripts could include bash, python, etc. Array of KVP requirements with the key as the parameter name and the value as the parameter that need to be passed as an input to the script. NOTE: The scriptInput values are passed to the scripts in addition to the parameters received in the operation invocation request or indicator value change. Specifies the virtualized resource related performance metric to be tracked by the VNFM, e.g. for auto-scaling purposes. The VNFM collects the values of performance metrics identified by this information element from the VIM(s) using one or more locally initiated PM Jobs. These values can be used as inputs to auto-scaling rules. Unique identifier of the monitoring parameter. Human readable name of the monitoring parameter. Identifies the virtualized resource performance metric. An attribute that describes the periodicity at which to collect the performance information. This information element provides a means to define additional VNF-specific attributes that represent the configurable properties of a VNFC. For a VNFC instance, the values of these properties can be queried and modified through the VNFM. Modifying these values affects directly the configuration of an existing VNFC instance. It provides VNFC configurable properties that can be modified using the ModifyVnfInfo operation. Describes the type of VNIC to which a CP attaches. The ScaleInfo information element represents a scale level for a particular scaling aspect. Reference to the scaling aspect. The scale level, greater than or equal to 0 Defines the CPU pinning policy. Describes VNF lifecycle event(s) or an external stimulus detected on a VNFM reference point. Describes the source of the indicator. Specifies the periodicity at which the producer will collect performance information. Note: at the end of each reportingPeriod, the producer will inform the consumer about availability of the performance data collected for each completed collection period during this reportingPeriod. While the exact definition of the types for collectionPeriod and reportingPeriod is left for further specification, it is recommended that the reportingPeriod be equal or a multiple of the collectionPeriod. In the latter case, the performance data for the collection periods within one reporting period would be reported together. The VirtualLinkBitRateLevel information element specifies bitrate requirements applicable to a virtual link instantiated from a particular VnfVirtualLinkDesc. Uniquely identifies a VnfVirtualLinkDesc Bitrate requirements for an instantiation level or bitrate delta for a scaling step. Provisioning status, used as a trigger for operational monitoring of this resource by service assurance systems. Indicator for whether the resource is considered operational. Valid values are in-service-path and out-of-service-path. This information element is a cont operations, structured by operation. The VnfIndicatorData datatype identifies a VNF indicator in a VNFD. Identifies a VNFD. Identifies a VNF indicator within the VNFD. Specifies the details of the block storage resource. Size of virtualised storage resource in GB. An array of key-value pairs that articulate the storage deployment requirements. Indicates if the storage supports rdma. Software image to be loaded on the VirtualStorage resource created based on this VirtualStorageDesc. Shall be absent when used for virtual disks. The ObjectStorageData information element specifies the details of object storage resource. Max size of virtualised storage resource in GB. The FileStorageData information element specifies the details of file storage resource. Size of virtualised storage resource in GB. The shared file system protocol (e.g. NFS, CIFS). Reference of the internal VLD which this file storage connects to. The attached VDUs shall connect to the same internal VLD. Unique identifier of the storage Qos in VNFD. Name of storage QoS. Consumer type. Describe qualities of Qos：total_bytes_sec、total_iops_sec. Unique identifier of volume type in VNFD. Name of volume type. Backend volume name of cinder. The VirtualLinkProtocolData describes the protocol layer and associated protocol data for a virtual link One of the values of the attribute layerProtocol of the ConnectivityType IE. Specifies the L2 protocol data for this virtual link. Shall be present when the associatedLayerProtocol attribute indicates a L2 protocol and shall be absent otherwise. Specifies the L3 protocol data for this virtual link. Shall be present when the associatedLayerProtocol attribute indicates a L3 protocol and shall be absent otherwise. The QoS as applied to the vnf. Ingress or egress traffic The VersionSelector information element allows to identify the source and destination VNFDs (and implicitly, VNF packages) for a "change current VNF Package", as well as the applicable source deployment flavour. The triplet (srcVnfdId, srcFlavourId, dstVnfdId) uniquely determines a change. Identifier of the source VNFD and the source VNF package. Identifier of the destination VNFD and the destination VNF package Identifier of the deployment flavour in the source VNF package for which this modification applies. With respect to a "change current VNF Package" process, a ComponentMapping information element defines a mapping between the identifier of a components or property in the source VNFD and the identifier of the corresponding component or property in the destination VNFD. Examples for components are VDUs, VLDs, etc., and an example for a property is a scaling aspect of the VNF. The type of component or property. Possible values differentiate whether changes concern to some VNF component (e.g. VDU, internal VLD, etc.) or property (e.g. a Scaling Aspect, etc.). Identifier of the component or property in the source VNFD. Identifier of the component or property in the destination VNFD. Human readable description of the component changes. This information element describes the additional service data of the VirtualCp used to expose properties of the VirtualCp to NFV-MANO. If the VirtualCp is exposed by a VNF component realized by one or a set of OS containers, the properties are mirrored from the declarative descriptor of the corresponding MCIO where available. Service port numbers exposed by the VirtualCp. Service matching information exposed by the VirtualCp NOTE: This attribute shall only be present if additional information is needed to identify the service termination within the VNF, such as for example a url path information in an HTTP request required to allow a single VirtualCp IP address to be used for several HTTP based services that use the same portnumber. This information element describes the service identifying port properties exposed by the VirtualCp. The name of the port exposed by the VirtualCp. The L4 protocol for this port exposed by the VirtualCp. VALUES: • TCP • UDP • SCTP The L4 port number exposed by the VirtualCp. Specifies whether the port attribute value is allowed to be configurable.