12.6 Collection of M2M System data

12.6.1 Description

M2M Service Providers have a need to provide the Application Service Providers with data and analysis related to the behavior of the M2M System as well as the service provider supplied components of the M2M System (e.g. Device Gateway) M2M Operators face two problems.

M2M Service Providers can utilize the methods of Big Data by collecting M2M System data for the behavior of the M2M System as well as data from M2M System components provided by the Service Provider.

In this scenario, the data is collected from M2M Gateways and Devices provided by the M2M Service Provider. The M2M System data that is collected from the M2M Devices and Gateways can be described as:

• M2M System Behavior
• Component Properties

M2M System Behavior: Data related to the operation of the M2M Applications within the M2M System.

Types of data that is to be collected includes information related Messages transmittal and reception (e.g. bytes, response times, event time).

Component Properties: Data related to the Service Provider supplied components as the component is in use by the M2M System (e.g. location, speed of the component, other anonymous data).

With this data, the M2M Service Provide can provide:

1. Analysis of the data without knowledge of content of the Application's data.
2. Insights into the operation of the M2M Applications. For example, the M2M Service Provider can infer the "correct" state of the application or the network status changes, by the analysis of the data, and then trigger some kinds of optimization mechanisms.

12.6.2 Source

oneM2M-REQ-2013-0279R04 Collection of non-application data

12.6.3 Actors

• Front-end data-collection equipment (e.g. M2M Devices and Gateways) :
• Management Platform (e.g. M2M Service Provider's Platform)
• Monitor Centre (e.g. M2M Application's Platform)
• M2M System Data Collection Centre

12.6.4 Pre-conditions

None

12.6.5 Triggers

• Time trigger: collecting data at a specific time;
• Position trigger: collecting data when position changed;
• Behavior trigger: collecting data when certain behavior happened

12.6.6 Normal Flow

1. The M2M Device and Gateway collects M2M System data.
2. Once a trigger is activated, the M2M Devices and Gateway sends the M2M System data to the M2M System Data Collection Centre.

12.6.7 Alternative Flow

None

12.6.8 Post-conditions

None

12.6.9 High Level Illustration

!

Figure 12.6.9-1 Vehicle Operation Management System

• Vehicle Operation Management System provide users a new telecommunications business with remote collection, transmission, storage, processing of the image and alarm signals.
• Front-End Data Collection Equipment include Front-End 3G camera, Electronic Station, Car DVR, costumed car GPS, WCDMA wireless routers and other equipment.
• Management Platform with business management function, include:
  • Forwarding, distribution, or storage of images
  • Linkage process of alarms
  • Management and maintenance of the vehicle status data.
• Monitor Centre: consists of TV wall, soft / hardware decoder, monitor software, etc.
• Vehicle State Data Demand Department: such as auto 4S shop, vehicle repair shop, vehicle management centre, automobile and parts manufacturers, government regulatory platform, etc.
• M2M System Data Collection Centre: use built-in data collectors resided in Network Equipment, M2M Platform, Costumed M2M Modules and Costumed M2M Terminal Devices to collect M2M System data.

12.6.10 Potential Requirements

Figure 12.6.10-1 M2M System Data Collection Processing Flow

1. M2M System should support M2M System data collection.
   As illustrated in Figure 12.6.10-1, we suggest that M2M System data collector should reside in:
   • M2M Service Providers' Platform
   • M2M Network Equipment
   • M2M Devices and Gateways
   • M2M Communication Module