idnits 2.17.1 draft-ds-functional-architecture-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 1) being 391 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack a Security Considerations section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There is 1 instance of too long lines in the document, the longest one being 1 character in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (Feb 15, 2017) is 2624 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- -- Looks like a reference, but probably isn't: 'Table 3-1' on line 104 -- Looks like a reference, but probably isn't: 'Table 3-2' on line 142 -- Looks like a reference, but probably isn't: 'Table 3-3' on line 160 -- Looks like a reference, but probably isn't: 'Table 4-1' on line 206 -- Looks like a reference, but probably isn't: 'Figure 4-1' on line 226 == Unused Reference: '1' is defined on line 350, but no explicit reference was found in the text Summary: 4 errors (**), 0 flaws (~~), 3 warnings (==), 6 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Engineering Task Force Eui-Nam Huh 2 Internet-Draft Kyung Hee University 3 CDNI Working Group Ga-Won Lee 4 Intended status: Informational Kyung Hee University 5 Expires: Aug 16, 2017 Yunkon Kim 6 Kyung Hee University 7 Jintaek Kim 8 Consortium of Cloud Computing Research 9 Feb 15, 2017 11 Data providing service requirements and functional architecture 12 draft-ds-functional-architecture-00 14 Abstract 16 The standard describes concept and characteristics of data providing 17 service. To derive functional architecture, requirements are described 18 on the perspective of providing and using data. 20 Status of This Memo 22 This Internet-Draft is submitted in full conformance with the 23 provisions of BCP 78 and BCP 79. 25 Internet-Drafts are working documents of the Internet Engineering 26 Task Force (IETF). Note that other groups may also distribute 27 working documents as Internet-Drafts. The list of current Internet- 28 Drafts is at http://datatracker.ietf.org/drafts/current/. 30 Internet-Drafts are draft documents valid for a maximum of six months 31 and may be updated, replaced, or obsoleted by other documents at any 32 time. It is inappropriate to use Internet-Drafts as reference 33 material or to cite them other than as "work in progress." 35 This Internet-Draft will expire on August 16, 2017. 37 Copyright Notice 39 Copyright (c) 2017 IETF Trust and the persons identified as the 40 document authors. All rights reserved. This document is subject to 41 BCP 78 and the IETF Trust's Legal Provisions Relating to IETF 42 Documents (http://trustee.ietf.org/license-info) in effect on the 43 date of publication of this document. Please review these documents 44 carefully, as they describe your rights and restrictions with respect 45 to this document. Code Components extracted from this document must 46 include Simplified BSD License text as described in Section 4.e of 47 the Trust Legal Provisions and are provided without warranty as 48 described in the Simplified BSD License. 50 Table of Contents 52 1. Introduction------------------------------------------------------ 54 2. Terms and Abbreviation-------------------------------------------- 56 3. Data Providing Service Requirements------------------------------- 57 3.1 Data Management Requirements---------------------------------- 58 3.2 Data Policy Management Requirements--------------------------- 59 3.3 Data Provision Requirements----------------------------------- 61 4. Data Providing Service Functional Architecture-------------------- 63 5. References-------------------------------------------------------- 65 1. Introduction 66 Unstructured data is continuously increased from IoT devices such as 67 smart phones, tablets, and wearable devices with mobile and social 68 network services (SNS). With increasing of unstructured data, Big 69 data services have been already appeared to drive the traditional 70 process-oriented computing paradigm to data-centric computing 71 paradigm. In data centric computing environment, Data Providing 72 System might be realized by core technology. In this circumstance, 73 the importance of data providing has emerged. 74 In order to provide data, these various data need to be provisioned 75 with low complexity and high availability. Provisioned data can be 76 provided to data users by user's requests. Moreover, the environment 77 which data users can search data is necessary. This environment might 78 contribute to form a virtuous circle which shared data is used to 79 create new service. Therefore, this standard defines data providing 80 service requirements and functional architecture to support data 81 management and accessibility. 83 2. Terms and Abbreviation 85 - DG : Data Generator 86 - DB : Data Broker 87 - DR : Data Refiner 88 - DPS : Data Providing Service 89 - DC : Data Customer 91 3. Data Providing Service Requirements 93 Data providing service can be divided into 3 parts : data management, 94 data policy management, and data provision. Requirements condition is 95 as follows : 96 - M : Mandatory 97 - R : Recommended 98 - O : Optional 100 3.1 Data Management Requirements 101 In table 3-1, requirements of data generator(DG) and data broker(DB) 102 is defined for data management. 104 [Table 3-1] Data management Requirements 105 ---------------------------------------------------------------------- 106 | Role | Requirements | Role | M/R/O | 107 |(subject)| |(object)| | 108 |---------|-------------------------------------------|--------|-------| 109 | DG | data management(generate, store, delete) | | M | 110 |---------|-------------------------------------------|--------|-------| 111 | DG | data information provisioning | | M | 112 | | (generate, publishing, API management) | | | 113 |---------|-------------------------------------------|--------|-------| 114 | DG | semantic data information generation | | M | 115 |---------|-------------------------------------------|--------|-------| 116 | DG | data access and preserve history | | M | 117 |---------|-------------------------------------------|--------|-------| 118 | DPS:DB | data information provisioning | | | 119 | | (collect, search, update, API management) | | M | 120 |---------|-------------------------------------------|--------|-------| 121 | DPS:DB | collect of data information in | | | 122 | | heterogeneous management domain | | M | 123 |---------|-------------------------------------------|--------|-------| 124 | DPS:DB | brokage of data information in | | | 125 | | heterogeneous management domain | | M | 126 |---------|-------------------------------------------|--------|-------| 127 | DPS:DB | collect heterogeneous form (formal, | | | 128 | | non-formal, antiformal) data information | | R | 129 |---------|-------------------------------------------|--------|-------| 130 | DG, | | | | 131 | DPS:DB | real-time data update | | O | 132 |---------|-------------------------------------------|--------|-------| 133 | DPS:DB | data information management using ontology| | O | 134 |---------|-------------------------------------------|--------|-------| 135 | DPS:DB | user feedback management | | O | 136 ---------------------------------------------------------------------- 138 3.2 Data Policy Management Requirements 139 In table 3-2, requirements of data generator(DG) and data broker(DB) 140 is defined for data policy management. 142 [Table 3-2] Data Policy management Requirements 143 ---------------------------------------------------------------------- 144 | Role | Requirements | Role | M/R/O | 145 |(subject)| |(object)| | 146 |---------|-------------------------------------------|--------|-------| 147 | DG | establishment of data and data publishing | | | 148 | | policy | | M | 149 |---------|-------------------------------------------|--------|-------| 150 | DG | establishment of data management policy | | M | 151 |---------|-------------------------------------------|--------|-------| 152 | DG | establishment of data information | | M | 153 | DPS:DB | provisioning policy | | | 154 ---------------------------------------------------------------------- 156 3.3 Data Provision Requirements 157 In table 3-3, requirements of data generator(DG), data broker(DB) and 158 data refiner(DR) is defined for data management. 160 [Table 3-3] Data management Requirements 161 ---------------------------------------------------------------------- 162 | Role | Requirements | Role | M/R/O | 163 |(subject)| |(object)| | 164 |---------|-------------------------------------------|--------|-------| 165 | DG | data update pushing |DPS, DC | O | 166 |---------|-------------------------------------------|--------|-------| 167 | DG | provide data access and history |DPS, DC | R | 168 |---------|-------------------------------------------|--------|-------| 169 | DG | provide data through APIs | DPS:DB | O | 170 | DPS:DB | | DC | | 171 |---------|-------------------------------------------|--------|-------| 172 | DPS:DB | provide data catalogue for data browsing | DC | M | 173 |---------|-------------------------------------------|--------|-------| 174 | DPS:DB | using standard protocol for data and data | | R | 175 | | information brokering (e.g., RESTful API) | | | 176 |---------|-------------------------------------------|--------|-------| 177 | DPS:DB | provide user customized UI (e.g., most | DC | O | 178 | | often viewed data, recommendation, etc.) | | | 179 |---------|-------------------------------------------|--------|-------| 180 | DPS:DB | provide user feedback interface | | O | 181 |---------|-------------------------------------------|--------|-------| 182 | DPS:DR | data process(Transforming, filtering, and | | M | 183 | | de-noising) according to user's request | | | 184 |---------|-------------------------------------------|--------|-------| 185 | DPS:DR | processing of heterogeneous form(formal, | | R | 186 | |non-formal, antiformal) data information | | | 187 |---------|-------------------------------------------|--------|-------| 188 | DPS:DR | data integration (combining, forming, | | R | 189 | | coordinating, blending) according to | | | 190 | | user's request | | | 191 |---------|-------------------------------------------|--------|-------| 192 | DPS:DR | refined data storing and preserving | | O | 193 ---------------------------------------------------------------------- 195 4. Data Providing Service Functional Architecture 196 Based on role of data providing service, function of data generator, 197 data broker, and data refiner is shown in table 4-1. 198 Data generator manages original data, and provides meta-data 199 management and provisioning of original data. Data broker provides 200 catalogue of stored original data to user, and manages user data 201 access. It is possible that refine data based on user's request as an 202 option which provided by data refiner. Data policy management is 203 'cross-cutting aspect', that is, common functionality of all data 204 providing service role. 206 [Table 4-1] Data providing service function overview 207 ---------------------------------------------------------------------- 208 | role of | function | 209 | data providing service | | 210 |------------------------|---------------------------------------------| 211 | Data Generator | - meta-data management | 212 | | - data management | 213 | | - meta-data policy management | 214 | | - data policy management | 215 |------------------------|---------------------------------------------| 216 | | | - data brokering | 217 | | Data | - meta-data management | 218 | | Broker | - data access management | 219 | Data | | - data access management | 220 | Providing | | - data policy management | 221 | Service |------------|---------------------------------------------| 222 | | Data | - data refining | 223 | | Refiner | - data policy management | 224 ---------------------------------------------------------------------- 226 [Figure 4-1] Data providing service functional architecture 228 ------------------------------------- 229 | Data Generator | 230 | | 231 | --------------------------------- | 232 | | Meta-data management | | 233 | | | | 234 | | ------------- ------------- | | 235 | || Generate | | Store || | 236 | | ------------- ------------- | | 237 | | ------------------------------- | | 238 | || Povisioning || | 239 | || ------------ ------------ || |-------- 240 | ||| Update | | Search ||| | | 241 | || ------------ ------------ || | | 242 | | ------------------------------- | | | 243 | --------------------------------- | | 244 | --------------------------------- | | 245 | | Data management | | | 246 | | | | | 247 | | --------------- ------------- | | | 248 | || Generate data | | Collect data|| | | 249 | | --------------- ------------- | | | 250 | | ------------------------------- | | | 251 | || Store data || | | 252 | | ------------------------------- | | | 253 | --------------------------------- | | 254 ------------------------------------- | 255 | 256 | 257 | 258 ------------------------------------- | --------------- 259 | Data Refiner | | | Data Policy | 260 | | | | Management | 261 | --------------------------------- | | | | 262 | | Data refining | | | | | 263 | | | | | | ------------- | 264 | | ------------------------------- | | | || || 265 | || Heterogeneous data management || | | || Data & || 266 | || -------------- ------------ || | | || Meta-data || 267 | ||| transforming | | Filtering ||| | | || || 268 | || -------------- ------------ || | | || Search / || 269 | || ----------------------------- || | | || Publish / || 270 | ||| De-noising || | | || Access || 271 | || ------------------------------ | | | || policy || 272 | | ------------------------------- | | | || management || 273 | | | | | || || 274 | | ------------------------------- | |--------|------| ------------- | 275 | || Refined data storing || | | | | 276 | | ------------------------------- | | | | | 277 | | | | | | | 278 | | ------------------------------- | | | --------------- 279 | || Data integration || | | 280 | || ------------- ------------- || | | 281 | ||| Combining | | Forming ||| | | 282 | || ------------- ------------- || | | 283 | || -------------- ------------ || | | 284 | ||| Coordinating | | blending ||| | | 285 | || -------------- ------------ || | | 286 | | ------------------------------- | | | 287 | --------------------------------- | | 288 ------------------------------------- | 289 | 290 | 291 | 292 | 293 ------------------------------------- | 294 | Data Broker | | 295 | | | 296 | --------------------------------- | | 297 | | Data brokering | | | 298 | | | | | 299 | | ------------------------------- | | | 300 | || Store history(search/browing) || | | 301 | | ------------------------------- | | | 302 | | ------------------------------- | | | 303 | || Feedback management || | | 304 | || ---------- ---------------- || | | 305 | ||| Quaring | | Result storing ||| | | 306 | || ---------- ---------------- || | | 307 | | ------------------------------- | | | 308 | | ------------------------------- | | | 309 | || Catalogue management || | | 310 | || ---------- -------- ------- || | | 311 | ||| Generate || Browse || Search||| | | 312 | || ---------- -------- ------- || | | 313 | || -------------- ------------ || | | 314 | ||| Publish | | Update ||| | | 315 | || -------------- ------------ || | | 316 | | ------------------------------- | | | 317 | --------------------------------- | | 318 | | | 319 | --------------------------------- |-------- 320 | | Meta-data management | | 321 | | | | 322 | | -------------- ------------ | | 323 | || Generate | | Store || | 324 | | -------------- ------------ | | 325 | | ------------------------------- | | 326 | || Provisioning || | 327 | || -------- --------- -------- || | 328 | ||| Update || Collect || Search ||| | 329 | || -------- --------- -------- || | 330 | | ------------------------------- | | 331 | --------------------------------- | 332 | | 333 | --------------------------------- | 334 | | Data access management | | 335 | | | | 336 | | ------------------------------- | | 337 | || API management || | 338 | | ------------------------------- | | 339 | | ------------------------------- | | 340 | || Access authority management || | 341 | | ------------------------------- | | 342 | | ------------------------------- | | 343 | || Access/use history storing || | 344 | | ------------------------------- | | 345 | --------------------------------- | 346 ------------------------------------- 348 5. References 350 [1] ITU-T Y.3600, Big data : Cloud computing based requirements and 351 capabilities, 2015 353 Appendix A. Acknowledgements 355 This draft is supported by Institute for Information & communications 356 Technology Promotion(IITP) grant funded by the Korea government(MSIP) 357 (R0127-16-1044, Cloud Storage Brokering Technology for Data-Centric 358 Computing Standardization) 360 Authors' Addresses 362 Eui-Nam Huh 363 Computer Science and Engineering Department, Kyung Hee University 364 Yongin, South Korea 366 Phone: +82 (0)31 201 3778 367 Email: johnhuh@khu.ac.kr 369 Ga-Won Lee 370 Computer Science and Engineering Department, Kyung Hee University 371 Yongin, South Korea 373 Phone: +82 (0)31 201 2454 374 Email: gawon@khu.ac.kr 376 Yunkon Kim 377 Computer Science and Engineering Department, Kyung Hee University 378 Yongin, South Korea 380 Phone: +82 (0)31 201 2454 381 Email: ykkim@khu.ac.kr 383 Jintaek Kim 384 Consortium of Cloud Computing Research, Seoul, South Korea 386 Phone: +82 (0)2 2052 0156 387 Email: jtkim@cccr.or.kr