Common use of Orchestration Clause in Contracts

Orchestration. Req.O1: MUST provide an ETSI MANO compliant abstraction to media service providers. This aligns the provisioning of media services with emerging platform concepts and standards in the relevant infrastructure segment, i.e. the ETSI work on NFV. (linked to all use cases in Section 4) • Req.O2: MUST support placement of computational and/or storage capacity based on different parameters (e.g., quality, location). This requirement addresses the multi-POP nature of the infrastructure, i.e. the exposure of resources in several/many locations of the infrastructure, not just in a centralized single location. In such case, placement is linked to specific locality and capability of the POP. (linked to all use cases in Section 4.1)

Orchestration.  Req.O1: MUST provide an ETSI MANO compliant abstraction to media service providers. This aligns the provisioning of media services with emerging platform concepts and standards in the relevant infrastructure segment, i.e. the ETSI work on NFV. (linked to all use cases in Section 4) •  Req.O2: MUST support placement of computational and/or storage capacity based on different parameters (e.g., quality, location). This requirement addresses the multi-POP nature of the infrastructure, i.e. the exposure of resources in several/many locations of the infrastructure, not just in a centralized single location. In such case, placement is linked to specific locality and capability of the POP. (linked to all use cases in Section 4.1)