Internet DRAFT - draft-ds-functional-architecture
draft-ds-functional-architecture
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: Aug 16, 2017 Yunkon Kim
Kyung Hee University
Jintaek Kim
Consortium of Cloud Computing Research
Feb 15, 2017
Data providing service requirements and functional architecture
draft-ds-functional-architecture-00
Abstract
The standard describes concept and characteristics of data providing
service. To derive functional architecture, requirements are described
on the perspective of providing and using data.
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. Terms and Abbreviation--------------------------------------------
3. Data Providing Service Requirements-------------------------------
3.1 Data Management Requirements----------------------------------
3.2 Data Policy Management Requirements---------------------------
3.3 Data Provision Requirements-----------------------------------
4. Data Providing Service Functional Architecture--------------------
5. References--------------------------------------------------------
1. Introduction
Unstructured data is continuously increased from IoT devices such as
smart phones, tablets, and wearable devices with mobile and social
network services (SNS). With increasing of unstructured data, Big
data services have been already appeared to drive the traditional
process-oriented computing paradigm to data-centric computing
paradigm. In data centric computing environment, Data Providing
System might be realized by core technology. In this circumstance,
the importance of data providing has emerged.
In order to provide data, these various data need to be provisioned
with low complexity and high availability. Provisioned data can be
provided to data users by user's requests. Moreover, the environment
which data users can search data is necessary. This environment might
contribute to form a virtuous circle which shared data is used to
create new service. Therefore, this standard defines data providing
service requirements and functional architecture to support data
management and accessibility.
2. Terms and Abbreviation
- DG : Data Generator
- DB : Data Broker
- DR : Data Refiner
- DPS : Data Providing Service
- DC : Data Customer
3. Data Providing Service Requirements
Data providing service can be divided into 3 parts : data management,
data policy management, and data provision. Requirements condition is
as follows :
- M : Mandatory
- R : Recommended
- O : Optional
3.1 Data Management Requirements
In table 3-1, requirements of data generator(DG) and data broker(DB)
is defined for data management.
[Table 3-1] Data management Requirements
----------------------------------------------------------------------
| Role | Requirements | Role | M/R/O |
|(subject)| |(object)| |
|---------|-------------------------------------------|--------|-------|
| DG | data management(generate, store, delete) | | M |
|---------|-------------------------------------------|--------|-------|
| DG | data information provisioning | | M |
| | (generate, publishing, API management) | | |
|---------|-------------------------------------------|--------|-------|
| DG | semantic data information generation | | M |
|---------|-------------------------------------------|--------|-------|
| DG | data access and preserve history | | M |
|---------|-------------------------------------------|--------|-------|
| DPS:DB | data information provisioning | | |
| | (collect, search, update, API management) | | M |
|---------|-------------------------------------------|--------|-------|
| DPS:DB | collect of data information in | | |
| | heterogeneous management domain | | M |
|---------|-------------------------------------------|--------|-------|
| DPS:DB | brokage of data information in | | |
| | heterogeneous management domain | | M |
|---------|-------------------------------------------|--------|-------|
| DPS:DB | collect heterogeneous form (formal, | | |
| | non-formal, antiformal) data information | | R |
|---------|-------------------------------------------|--------|-------|
| DG, | | | |
| DPS:DB | real-time data update | | O |
|---------|-------------------------------------------|--------|-------|
| DPS:DB | data information management using ontology| | O |
|---------|-------------------------------------------|--------|-------|
| DPS:DB | user feedback management | | O |
----------------------------------------------------------------------
3.2 Data Policy Management Requirements
In table 3-2, requirements of data generator(DG) and data broker(DB)
is defined for data policy management.
[Table 3-2] Data Policy management Requirements
----------------------------------------------------------------------
| Role | Requirements | Role | M/R/O |
|(subject)| |(object)| |
|---------|-------------------------------------------|--------|-------|
| DG | establishment of data and data publishing | | |
| | policy | | M |
|---------|-------------------------------------------|--------|-------|
| DG | establishment of data management policy | | M |
|---------|-------------------------------------------|--------|-------|
| DG | establishment of data information | | M |
| DPS:DB | provisioning policy | | |
----------------------------------------------------------------------
3.3 Data Provision Requirements
In table 3-3, requirements of data generator(DG), data broker(DB) and
data refiner(DR) is defined for data management.
[Table 3-3] Data management Requirements
----------------------------------------------------------------------
| Role | Requirements | Role | M/R/O |
|(subject)| |(object)| |
|---------|-------------------------------------------|--------|-------|
| DG | data update pushing |DPS, DC | O |
|---------|-------------------------------------------|--------|-------|
| DG | provide data access and history |DPS, DC | R |
|---------|-------------------------------------------|--------|-------|
| DG | provide data through APIs | DPS:DB | O |
| DPS:DB | | DC | |
|---------|-------------------------------------------|--------|-------|
| DPS:DB | provide data catalogue for data browsing | DC | M |
|---------|-------------------------------------------|--------|-------|
| DPS:DB | using standard protocol for data and data | | R |
| | information brokering (e.g., RESTful API) | | |
|---------|-------------------------------------------|--------|-------|
| DPS:DB | provide user customized UI (e.g., most | DC | O |
| | often viewed data, recommendation, etc.) | | |
|---------|-------------------------------------------|--------|-------|
| DPS:DB | provide user feedback interface | | O |
|---------|-------------------------------------------|--------|-------|
| DPS:DR | data process(Transforming, filtering, and | | M |
| | de-noising) according to user's request | | |
|---------|-------------------------------------------|--------|-------|
| DPS:DR | processing of heterogeneous form(formal, | | R |
| |non-formal, antiformal) data information | | |
|---------|-------------------------------------------|--------|-------|
| DPS:DR | data integration (combining, forming, | | R |
| | coordinating, blending) according to | | |
| | user's request | | |
|---------|-------------------------------------------|--------|-------|
| DPS:DR | refined data storing and preserving | | O |
----------------------------------------------------------------------
4. Data Providing Service Functional Architecture
Based on role of data providing service, function of data generator,
data broker, and data refiner is shown in table 4-1.
Data generator manages original data, and provides meta-data
management and provisioning of original data. Data broker provides
catalogue of stored original data to user, and manages user data
access. It is possible that refine data based on user's request as an
option which provided by data refiner. Data policy management is
'cross-cutting aspect', that is, common functionality of all data
providing service role.
[Table 4-1] Data providing service function overview
----------------------------------------------------------------------
| role of | function |
| data providing service | |
|------------------------|---------------------------------------------|
| Data Generator | - meta-data management |
| | - data management |
| | - meta-data policy management |
| | - data policy management |
|------------------------|---------------------------------------------|
| | | - data brokering |
| | Data | - meta-data management |
| | Broker | - data access management |
| Data | | - data access management |
| Providing | | - data policy management |
| Service |------------|---------------------------------------------|
| | Data | - data refining |
| | Refiner | - data policy management |
----------------------------------------------------------------------
[Figure 4-1] Data providing service functional architecture
-------------------------------------
| Data Generator |
| |
| --------------------------------- |
| | Meta-data management | |
| | | |
| | ------------- ------------- | |
| || Generate | | Store || |
| | ------------- ------------- | |
| | ------------------------------- | |
| || Povisioning || |
| || ------------ ------------ || |--------
| ||| Update | | Search ||| | |
| || ------------ ------------ || | |
| | ------------------------------- | | |
| --------------------------------- | |
| --------------------------------- | |
| | Data management | | |
| | | | |
| | --------------- ------------- | | |
| || Generate data | | Collect data|| | |
| | --------------- ------------- | | |
| | ------------------------------- | | |
| || Store data || | |
| | ------------------------------- | | |
| --------------------------------- | |
------------------------------------- |
|
|
|
------------------------------------- | ---------------
| Data Refiner | | | Data Policy |
| | | | Management |
| --------------------------------- | | | |
| | Data refining | | | | |
| | | | | | ------------- |
| | ------------------------------- | | | || ||
| || Heterogeneous data management || | | || Data & ||
| || -------------- ------------ || | | || Meta-data ||
| ||| transforming | | Filtering ||| | | || ||
| || -------------- ------------ || | | || Search / ||
| || ----------------------------- || | | || Publish / ||
| ||| De-noising || | | || Access ||
| || ------------------------------ | | | || policy ||
| | ------------------------------- | | | || management ||
| | | | | || ||
| | ------------------------------- | |--------|------| ------------- |
| || Refined data storing || | | | |
| | ------------------------------- | | | | |
| | | | | | |
| | ------------------------------- | | | ---------------
| || Data integration || | |
| || ------------- ------------- || | |
| ||| Combining | | Forming ||| | |
| || ------------- ------------- || | |
| || -------------- ------------ || | |
| ||| Coordinating | | blending ||| | |
| || -------------- ------------ || | |
| | ------------------------------- | | |
| --------------------------------- | |
------------------------------------- |
|
|
|
|
------------------------------------- |
| Data Broker | |
| | |
| --------------------------------- | |
| | Data brokering | | |
| | | | |
| | ------------------------------- | | |
| || Store history(search/browing) || | |
| | ------------------------------- | | |
| | ------------------------------- | | |
| || Feedback management || | |
| || ---------- ---------------- || | |
| ||| Quaring | | Result storing ||| | |
| || ---------- ---------------- || | |
| | ------------------------------- | | |
| | ------------------------------- | | |
| || Catalogue management || | |
| || ---------- -------- ------- || | |
| ||| Generate || Browse || Search||| | |
| || ---------- -------- ------- || | |
| || -------------- ------------ || | |
| ||| Publish | | Update ||| | |
| || -------------- ------------ || | |
| | ------------------------------- | | |
| --------------------------------- | |
| | |
| --------------------------------- |--------
| | Meta-data management | |
| | | |
| | -------------- ------------ | |
| || Generate | | Store || |
| | -------------- ------------ | |
| | ------------------------------- | |
| || Provisioning || |
| || -------- --------- -------- || |
| ||| Update || Collect || Search ||| |
| || -------- --------- -------- || |
| | ------------------------------- | |
| --------------------------------- |
| |
| --------------------------------- |
| | Data access management | |
| | | |
| | ------------------------------- | |
| || API management || |
| | ------------------------------- | |
| | ------------------------------- | |
| || Access authority management || |
| | ------------------------------- | |
| | ------------------------------- | |
| || Access/use history storing || |
| | ------------------------------- | |
| --------------------------------- |
-------------------------------------
5. References
[1] ITU-T Y.3600, Big data : Cloud computing based requirements and
capabilities, 2015
Appendix A. Acknowledgements
This draft is supported by Institute for Information & communications
Technology Promotion(IITP) grant funded by the Korea government(MSIP)
(R0127-16-1044, 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.or.kr
