Standard

Cloud Customer Architecture for Enterprise Social Collaboration describes how to leverage social collaboration tools to harness ideas, exchange information, and increase the speed of innovation across the business.
 
This cloud reference architecture was written for enterprise Information Technology (IT) and business decision makers to assist in understanding the technical capabilities and integration requirements necessary to deliver Enterprise Social Collaboration solutions. It is a vendor-neutral and best practices approach to describe the flows and relationships between business capabilities, functional areas, and architectural components delivered as a cloud solution.
 
This whitepaper discusses how social collaboration solutions can be applied to different industries and aligned with key business initiatives.

Cloud Customer Architecture for e-Commerce describes how to support e-Commerce solutions using cloud computing. The reference architecture contains a detailed view of the components, subcomponents and relationships for a cloud-based e-Commerce solution.
 
This whitepaper describes the flows and relationships between business capabilities and architectural components for e-Commerce applications that use cloud computing infrastructure, platforms and/or services. The elements of the architecture are used to instantiate an e-Commerce system using private, public, or hybrid cloud deployment models. Applications comprising the core components may be delivered as a service, from on-premises, or hosted.
 
A runtime scenario is outlined with deployment

SCOPE: This Recommendation specifies an architectural framework for machine learning in future networks including IMT-2020. A set of architectural requirements is presented, which in turn leads to specific architectural components needed to satisfy these requirements. This Recommendation also describes an architectural framework for integration of such components into future networks including IMT-2020 and guidelines for applying this architectural framework in a variety of technology-specific underlying networks.

Recommendation Y.3172 (06/19) - Approved in 2019-06-22

SCOPE: The present document covers the Radio Access Architecture and Interface aspects of the study item “New Radio Access Technology” [1]. The purpose of this TR is to record the discussion and agreements that arise in the specification of the “New Radio Access Technology” from an Access Architecture and Interface specification point of view.

The DSP0263 specification describes the model and protocol for management interactions between a cloud Infrastructure as a Service (IaaS) Provider and the Consumers of an IaaS service. The basic resources of IaaS (machines, storage, and networks) are modeled with the goal of providing Consumer management access to an implementation of IaaS and facilitating portability between cloud implementations that support the specification. This document specifies a Representational State Transfer (REST)-style protocol using HTTP. However, the underlying model is not specific to HTTP, and it is possible to map it to other protocols as well.  

CIMI addresses the management of the life cycle of an infrastructure provided by a Provider. CIMI does not extend beyond infrastructure management to the control of the applications and services that the Consumer chooses to run on the infrastructure provided as a service by the Provider. Although CIMI may be to some extent applicable to other cloud service models, such as Platform as a Service (PaaS) or Storage as a Service ("SaaS"), these uses are outside the design goals of CIMI.

This document makes use of the common meta-model used by CIM, the Common Information Model to describe the CIMI logical model. This is defined in DSP004, CIM Infrastructure Specification 2.7.

Transformation of the CIMI CIM into CIM metamodel conformant representations enables access of the services defined by CIMI in CIM-based environments. Such environments encompass a broad range of supported operating systems, languages, platforms, protocols, and other technologies.

This specification describes transformations in a manner that enables any CIM metamodel conformant representation. This document will utilize MOF for examples of such transformations.

The Open Virtualization Format (OVF) Specification describes an open, secure, efficient and extensible format for the packaging and distribution of software to be run in virtual systems. The OVF package enables the authoring of portable virtual systems and the transport of virtual systems between virtualization platforms. This version of the specification (2.1) is intended to allow OVF 1.x tools to work with OVF 2.x descriptors in the following sense:

• Existing OVF 1.x tools should be able to parse OVF 2.x descriptors.
• Existing OVF 1.x tools should be able to give warnings/errors if dependencies to 2.x features are required for correct operation.

If a conflict arises between the schema, text, or tables, the order of precedence to resolve the conflicts is schema; then text; then tables. Figures are for illustrative purposes only and are not a normative part of the standard.

A table may constrain the text but it shall not conflict with it.

The profile conforms to the cited CIM Schema classes where used. Any requirements contained in the cited CIM Schema classes shall be met. If a conflict arises the CIM Schema takes precedence.
The profile conforms to the cited OVF XML Schema. It may constrain the schema but it shall not conflict with it. If a conflict arises the OVF XML Schema takes precedence.
 
This standard is also published as ISO/IEC 17203:2017

Concerns over cloud provider security remain one of the top inhibitors to adoption of cloud deployment models. Potential consumers of cloud deployments need assurance that the security policies they require on their applications are consistently managed and enforced “in the cloud” as they would be in their enterprise.
A cloud provider’s ability to provide specific audit event, log, and report information on a per-tenant and application basis is essential. It is apparent that in order to meet these customer expectations, cloud providers must provide standard mechanisms for their tenant customers to self-manage and self-audit application security that includes information about the provider’s hardware, software, and network infrastructure used to run specific tenant applications.
A proven method to address such needs is to develop open standards to enable information sharing. Specifically, this specification provides a data format and interface definitions that support the federation of normative audit event data to and from cloud providers in the form of customized reports and logs. This specification also defines a means to attach domain-specific identifiers, event classification values, and tags that can be used to dynamically generate customized logs and reports for cloud subscribers or customers.
Adoption of this and other open standards by cloud providers’ management platforms would go far to instill greate trust in “cloud hosted applications” and be a significant step forward in fulfilling the promise of an open cloud marketplace.

SCOPE: The aim of this Technical Report is to study and specify how to collect data and how to feedback data analytics to the network functions.

This document makes use of the common meta-model used by CADF, the Cloud Audit Data Federation to describe the events used by the OpenStack Cloud Management Platform.
 
The document DSP0262 defines the CADF model.

In order to promote the wide spread adoption of OVF it is important that software vendors have confidence in the ability to build an OVF that can be deployed on a set of target virtualization platforms (aka hypervisors). To this end it is useful to define additional constraints and requirements on the OVF package to enable automated deployment and portability. Interoperability, i.e., the ability to be deployed on target virtualization platforms, is also enhanced.
The Open Virtualization Format standard defines conformance requirements, but these are not sufficient for the use cases that this specification addresses. Conformance can be done by inspection, checking for the ovf:required tag in the OVF and noting the conformance level as specified in the standard.
Software developers need guidelines for what needs to be included in each section of the environment file to ensure that a deployment function is capable of deploying the OVF.

The Cloud Data Management Interface defines the functional interface that applications will use to create, retrieve, update and delete data elements from the Cloud. As part of this interface the client will be able to discover the capabilities of the cloud storage offering and use this interface to manage containers and the data that is placed in them. In addition, metadata can be set on containers and their contained data elements through this interface.
 
This interface is also used by administrative and management applications to manage containers, accounts, security access and monitoring/billing information, even for storage that is accessible by other protocols. The capabilities of the underlying storage and data services are exposed so that clients can understand the offering.
 
The CDMITM International Standard specifies the interface to access cloud storage and to manage the data stored therein. This International Standard applies to developers who are implementing or using cloud storage. It documents how to access cloud storage and to manage the data stored there.
 
This standard is also published as ISO/IEC 17826:2016.