THE INSTITUTE OF ELECTRONICS, INFORMATION AND COMMUNICATION ENGINEERS TECHNICAL REPORT OF IEICE. 657 8531 1 1 E-mail: {shintaro,koupe,okushi}@ws.cs.kobe-u.ac.jp, {shinsuke,masa-n}@cs.kobe-u.ac.jp Scallop4SC SCALable LOgging Platform for Smart City Scallop4SC Key-Value Store Scallop4SC Scallop4SC API 2 2 API Scallop4SC API A study of services using large-scale house log in Smart city Shintaro YAMAMOTO, Kouhei TAKAHASHI, Akihiro OKUSHI, Shinsuke MATSUMOTO, Abstract and Masahide NAKAMURA Kobe University Rokkoudai-cho 1 1, Nada-ku, Kobe, Hyogo, 657 8531 Japan E-mail: {shintaro,koupe,okushi}@ws.cs.kobe-u.ac.jp, {shinsuke,masa-n}@cs.kobe-u.ac.jp Smart city is a next-generation city planning. In the smart city, some value-added services such as energy saving and optimization of traffic are provided using wide variety of logs collected from various appliances and sensors. In our previous work, we have been proposed and developed a smart city platform, called Scallop4SC that supports collecting and processing the extremely large-scale log data. This system stores variety of logs on key-value store, and supports the statistical processing of the logs on Hadoop. This paper tackles two remaining challenges in Scallop4SC: designing a meta-data scheme for smart city configuration information, designing a Scallop4SFC-APIs for accessing stored logs and meta-data. We discuss with some concrete smart city services with a focus on two types of services: the energy saving and the improvement in quality of life. Based on the discussion, we consider what meta-data and APIs are required to realize the smart city services. Key words Smart city, house log, Scallop4SC, smart city configuration information, API 1. [1], [2] Scallop4SC SCALable LOgging Platform for Smart City [3] Scallop4SC 4 1
P1: P2: P3: P4: P1 P3 API Scallop4SC API [3] P1 P2 Hadoop [4] HBase [5] Scallop4SC HBase HBase Key Value Hadoop Scallop4SC P3 P4 API 2 API API 2. 2. 1 IT [1], [2] 2. 2 3 1 Energy 2 Device 3 Environment 2. 3 Scallop4SC Scallop4SC SCALable LOgging Platform for Smart CityScallop4SC 1 Scallop4SC HBase KVS Hadoop Scallop4SC API Scallop4SC 4 P1: HBase KVS KVS P2: Hadoop Hadoop P3: KVS RDB RDB KVS P4: P1 P3 API 2
ロガー 分 散 KVS Log Table 1 ロガー ロガー ロガー RDB Scallop4SC Scallop4SC API API スマートシティサービス 分 散 処 理 システム Configuration information Scallop4SC P1 API API API P2 API API API API P3 API RDB API 2. 4 P3 Scallop4SC API P2 2 API 3. 3. 1 QoL: Quality of Life QoL 2 3. 2 3. 2. 1 14.9% 20% 1 3. 2. 2 3. 2. 3 ENG1: ENG2: ENG3: 3
ENG4: 3. 3 QoL 3. 3. 1 2. 2 3 QoL 3. 3. 2 QoL 3. 3. 3 QoL QOL1: & QOL2: QOL3: QOL4: QOL5: QOL6: QOL7: 4. 3. Scallop4SC API 4. 1 2 ER ER [6] [ ] 3 1 House 3 2 Device 2 3 Person 2 1 3 4
都 市 都 市 ID, 都 市 名,その 他 都 市 情 報 個 人 個 人 ID, 氏 名,その 他 個 人 情 報, 世 帯 ID CT001, 神 戸 市 六 甲 台 町, P000001, 中 村 匡 秀,,CT001- H00001 P000002, 山 本 晋 太 郎,,CT001- H00001 P000003, 高 橋 昂 平,,CT001- H00001 P000004, 大 櫛 章 裕,,CT001-H00001 住 宅 都 市 ID, 住 宅 ID, 住 所, 間 取 り 図, 種 別,その 他 住 宅 情 報 世 帯 世 帯 ID, 世 帯 主,[ 都 市 ID, 住 宅 ID],その 他 世 帯 情 報 F000001, P000001,CT-001-H00001, CT001-H00001, 神 戸 市 灘 区 六 甲 台 町 1-1システム 棟 中 村 研 究 室,, 大 学 研 究 室, 部 屋 都 市 ID, 住 宅 ID, 部 屋 ID, 部 屋 名,その 他 部 屋 情 報 CT001-H00001-R001, 学 生 部 屋 S101, 機 器 機 器 ID, 機 器 クラスID,[ 都 市 ID, 住 宅 ID, 部 屋 ID], 呼 称, 購 入 年 月 日, 購 入 価 格,( 使 用 開 始 日 ) DEV123456789,DC0001,CT-001-H00001-R001,リビングのテレビ,2010-07-01,368,000,2010-07-08 機 器 クラス 機 器 クラスID, 製 造 者, 型 番, 商 品 名, 種 別, 仕 様,その 他 機 器 クラス 情 報 DC0001, パナソニック, TH58PZ-800, VIERA(ビエラ),テレビ,, 2 1. ID 2. Log Status Configration Operation Type Energy Device Environment Type Energy Device Environment Type House Device Person exec 3 4. 2 API set get set get set get method,parameter API term,room,user term,room,user term,room,user 3. API API 5 API Log: API Status: API Configuration: API Operation: API Calculation: API 2. 2 3 Log Status 2 Configuration API Operation Calculation Hadoop API 4 API Calculation API 3 API 4 API Type 3 3 set get 2 API API 3. API 1 1 ENG1: Configuration.Device.get(houseID) ID Log.Energy.get(deviceID) 5
ID Type ENG1: Configration Device get house Log Energy get device Log Energy get house, term ENG2: Configration Device get city Log Energy get device Log Energy get city, term ENG3: Log Energy get city, term ENG4: Status Device get house Status Environment get house QOL1: & Status Environment get device Configration House get house QOL2: Log Environment get house, term Log Device get house, term QOL3: QOL4: Log Device get house QOL5: Log Device get house, term Log Environment get house, term QOL6: Configration Device get device Log Energy get device QOL7: Configration Device get device Log Device get house, device, term 1 API Log.Energy.get(houseID, term) 5. Scallop4SC API 2 API QoL 2 API API RDB API web API C 24500079, B 23300009 [1] Robert G. Hollands. Will the real smart city please stand up? City: analysis of urban trends, culture, theory, policy, action, Vol. 12, No. 3, pp. 303 320, 2008. [2] Arun Mahizhnan. Smart cities: The singapore case. Cities, Vol. 16, pp. 13 18, 1999. [3],,,.., 111, pp. 207 212, March 2012. [4] D. Borthakur. The hadoop distributed file system: Architecture and design, 2007. [5] Ankur Khetrapal and Vinay Ganesh. Hbase and hypertable for large scale distributed storage systems, 2006. [6].., 2008. 6