Internet DRAFT - draft-cds-overviews
draft-cds-overviews
Internet Engineering Task Force Eui-Nam Huh
Internet-Draft Kyung Hee University
CDNI Working Group Ga-Won Lee
Intended status: Informational Kyung Hee University
Expires: JUN 17, 2018 Yunkon Kim
Kyung Hee University
Jintaek Kim
Consortium of Cloud Computing Research
DEC 18, 2017
Cloud-based data providing service definition, concept, and use-cases
draft-cds-overviews-00
Abstract
The standard defines terminologies and describes ecosystem for cloud-
based data providing service. In order to build unified data
environment from the dispersed data, data providing service is
necessary for big data service. Therefore, this standard contributes to
form common data providing ecosystem.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on August 16, 2017.
Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved. This document is subject to
BCP 78 and the IETF Trust's Legal Provisions Relating to IETF
Documents (http://trustee.ietf.org/license-info) in effect on the
date of publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction -------------------------------------------------
2. Terminologies ------------------------------------------------
3. Abbreviation -------------------------------------------------
4. Overview of cloud-based data providing service ---------------
4.1. Concept of cloud-based data providing service ------
4.2. Definition of cloud-based data providing service ---
4.3. Model of cloud-based data providing service --------
4.4. Role classification of cloud-based data providing
service --------------------------------------------
5. Use-cases of cloud-based data providing service --------------
1. Introduction
This standard proposes concept, definition, and use-case of cloud-based
data providing service for big data service. First, the scope and
definition of data providing service are described. Second, ecosystem
model and role classification are illustrated. Finally, use-cases for
explaining data providing service are proposed.
2. Terminologies
2.1 Data generator
The data generator generates data, provides metadata to data broker,
and provides API to the data refiner to access data.
2.2 Data broker
The data broker brokerages data between the data generator and the
data customer.
2.3 Data refiner
The data refiner refines data, which is from the data generator, and
delivers data to the data customer.
2.4 Data customer
The data customer uses data, which is provided by the data providing
service.
3. Abbreviation
To be defined
4. Overview of cloud-based data providing service
4.1. Concept of cloud-based data providing service
Data is dispersed in different administration domain. For this reason,
it is hard to search data in big data area, which highly needs data.
This situation decreases the data availability. In order to increase
the data availability, an interface is needed to brokerage data in
different administartion domain and to search data in single access
point. For example, a user finds data which is in different
administration domain, while it is still hard to use the data. That is
because data type and access methods are different. A data customer
uses different methods to access data, and also the data may have
different type, so that a data customer does extra works, such as
converting, filtering. Thus, an interface is required to refine data
in various administration domain in order to provide the customized
data. Above all, this standard to build unified interface for
searching and requesting data is required.
4.2. Definition of cloud-based data providing service
The data providing service is a service to brokerage metadata in order
to search data in a unified interface and to refine data in order to
provide user customized data as user's request. For this, the data
providing service brokerages metadata, which is provided by the data
generator. A data customer searches data by the data providing service
easily. And also, as user's request, the data refiner refines and
provides data to data customer.
4.3. Model of cloud-based data providing service
This is a concept model. The concept model is described by roles
related with the data providing service, such as data generator, data
broker, data refiner, data customer.
-----------------
| Cloud-based |
| Data Providing |
| Service |
data | --------------- | data catalogue
---------->|| Data Broker ||-------------
| info | --------------- | |
| | user | ^ |<---------- |
| | req- | | user | | |
-------------- | est | |custo-| -----------------
| Data | | | |mized | | Data |
| Generator | | | | data | | user |
-------------- | v | | -----------------
| ^ ^ | data | --------------- | ^ | | ^
| | | -------->|| Data Refiner || data | | | |
| | | data | --------------- |------ | | |
| | ---------- | | data | | |
| | request | |<-------- | |
| | ----------------- request(by API)| |
| ------------------------------------------------ |
| data request (by API) |
-----------------------------------------------------
data
4.4. Role classification of cloud-based data providing service
4.4.1 Data generator
The data generator creates and supplies data. To supply data, the
data generator provides metadata for searching data to the data
broker and provides API for accessing data to the data refiner.
Activities of the data generator are follows
- Data management (Creation, store, deletion)
- Metadata provisioning (Metadata creation, metadata publish,
access policy management)
NOTE - Metadata: detailed information of data (e.g., origin, type,
creation time, and etc.)
4.4.2 Data provision providing service
4.4.2.1 Data broker
The data broker brokerages metadata between the data generators and
the data customers to search data.
Activities of the data broker are follows.
- Metadata provisioning (Metadata collection, search, update)
- Providing catalogue
- Data brokering (the data generator - the data customer, the data
generator - the data refiner, the data refiner - the data customer)
- User requirement management
4.4.2.2 Data refiner
The data refiner refines data, which is ingested from the data
generater, and delivers the refined data to the data customer.
Activities of the data refiner are follows.
- Data processing by the data customer's requirements (Transforming,
filtering, and de-noising)
- Data integration by the data customer's requirements (Combining,
forming, coordinating, and blending)
- Refined data management
4.4.3 Data customer
The data customer requests and uses data through searching data by
data catalogue provided by the data broker.
Activities of the data customer are follows.
- Use data (Data request, use)
- User's feedback (Question, grade, and etc.)
5. Use-cases of cloud-based data providing service
- Data catalogue service
- Public data provisioning service
- Data generator policy management service
- Data generator-user data delivery service
- Data filtering service
- User feedback
Appendix A. Acknowledgements
This draft was supported by Institute for Information & communications
Technology Promotion(IITP) grant funded by the Korea government(MSIT)
(2015-0-00240,Cloud Storage Brokering Technology for Data-Centric
Computing Standardization)
Authors' Addresses
Eui-Nam Huh
Computer Science and Engineering Department, Kyung Hee University
Yongin, South Korea
Phone: +82 (0)31 201 3778
Email: johnhuh@khu.ac.kr
Ga-Won Lee
Computer Science and Engineering Department, Kyung Hee University
Yongin, South Korea
Phone: +82 (0)31 201 2454
Email: gawon@khu.ac.kr
Yunkon Kim
Computer Science and Engineering Department, Kyung Hee University
Yongin, South Korea
Phone: +82 (0)31 201 2454
Email: ykkim@khu.ac.kr
Jintaek Kim
Consortium of Cloud Computing Research, Seoul, South Korea
Phone: +82 (0)2 2052 0156
Email: jtkim@cccr.ir.kr