Page 32 - Cloud computing: From paradigm to operation

1 Framework and requirements for cloud computing

3.1.15 inter-cloud computing [ITU-T Y.3511]: The paradigm for enabling the interworking between two or
more cloud service providers.
NOTE – Inter-cloud computing is also referred as inter-cloud.

3.1.16 network as a service (NaaS) [ITU-T Y.3500]: Cloud service category in which the capability provided
to the cloud service customer is transport connectivity and related network capabilities.

3.1.17 party [ITU-T Y.3500]: Natural person or legal person, whether or not incorporated, or a group of
either.

3.1.18 platform as a service (PaaS) [ITU-T Y.3500]: Cloud service category in which the cloud capabilities
type provided to the cloud service customer is a platform capabilities type.

3.1.19 resource management [ITU-T Y.3520]: The most efficient and effective way to access, control,
manage, deploy, schedule and bind resources when they are provided by service providers and requested by
customers.

3.1.20 role [ITU-T Y.3502]: A set of activities that serves a common purpose.
3.1.21 service level agreement (SLA) [ITU-T Y.3500]: Documented agreement between the service provider
and customer that identifies services and service targets.
NOTE 1 – A service level agreement can also be established between the service provider and a supplier, an internal
group or a customer acting as a supplier.
NOTE 2 – A service level agreement can be included in a contract or another type of documented agreement.

3.1.22 virtual desktop [ITU-T Y.3503]: An environment for accessing end user's desktop functions remotely.
NOTE – Examples of end user's desktop functions can include desktop interface functions for applications, data access
functions for multimedia data, and control functions for input/output (I/O) devices.

3.2 Terms defined in this Recommendation

This Recommendation defines the following term:
3.2.1 trusted cloud service: A cloud service that satisfies a set of requirements such as transparency for
governance, management and security so that a cloud service customer (CSC) can be confident in using the
cloud service.
NOTE 1 – The set of requirements will vary depending on the involved cloud service customer, the nature of the cloud
service and the governing jurisdiction.
NOTE 2 – The set of requirements could also be related to additional cross-cutting aspects [ITU-T Y.3502] such as
performance, resiliency, reversibility, SLAs, etc.
NOTE 3 – Transparency means that the cloud service provider (CSP) should commit to the CSC that they have
appropriate and clear control and reporting mechanisms for governance, management and security, such as SLA
commitments, online announcements, data handling policies, etc.

4 Abbreviations and acronyms
This Recommendation uses the following abbreviations and acronyms:

API Application Programming Interface
BDaaS Big Data as a Service
CaaS Communication as a Service

CPU Central Processing Unit
CSC Cloud Service Customer

CSN Cloud Service Partner
CSP Cloud Service Provider

DaaS Desktop as a Service

24