1. Introducing concept of M2M-application data modeling Group Name: MAS Source: FUJITSU Meeting Date: 2015-07-20 Agenda Item: Semantics and Device Configuration

2. Topic Summary MAS group discussed on modeling device capabilities deeply, but I also think modeling M2M-application data is also needed. Modeling device capability is describing ‘source’ of M2M data collection. Modeling M2M-application data is aiming to describe ‘destination’ of M2M data collection. 2

3. Use Case: IoT @home IoT Platform HEMS Application Home Automation Application Adaptor + Interests on: Energy Consumption, Switch-Status Interests on: Switch-status, SW-control, Place 3

4. Potential Problem IoT Platform HEMS Application Home Automation Application Adaptor + Interests on: Energy Consumption, Switch-Status Interests on: Switch-status, SW-control, Place May not have remote-control capability May not be compatible with others Could be Propriety Solution 4

5. Assumed use of IoT Platform HEMS Application Home Automation Application Adaptor + Interests on: Energy Consumption, Switch-Status Interests on: Switch-status, SW-control, Place Containers for HEMS Containers for HA They can be separated 5

6. Example use of data model DevicePlatformService App RESISTER (with available data components ) NOTIFY (available data components) Request to configure Device (desired data components) Configure Device Setting (desired data components) CREATE to store collected data from Device CREATE at instructed 6 Apply setting to produce desired data

7. Proposals Adding (producing) data modeling in scope of MAS discussion Adding potential requirement regarding ‘data modeling’ 7

8. Potential Requirements M2M Platform shall be able to collect data from M2M Device, with specifying desired data components. M2M Devices shall be able to provide available data components. 8