Doc# oneM2M-REQ-2015-0640-TR-0018_Overview_of_Potential_Requirements
1
2
3
I NPUT C ONTRIB UTION
Meeting ID*
REQ 19
Title:*
TR-0018_Overview of Potential Requirements
Source:*
Miao Jiang, Hitachi, miaojiang@hitachi.cn
Lu Geng, Hitachi, lgeng@hitachi.cn
Uploaded Date:*
2015-08-27
Document(s)
WI-0028 - Industrial Domain Enablement
Impacted*
oneM2M-TR-0018- Industrial Domain Enablement -V0_3_0
Intended purpose of
Decision
document:*
Discussion
Information
Other <specify>
Decision requested or
recommendation:*
<A concise statement of the decision required or the recommended action to
be taken>
Template Version:23 February 2015 (Dot not modify)
4
5
oneM2M Notice
6
7
8
9
The document to which this cover statement is attached is submitted to oneM2M. Participation in, or attendance at, any
activity of oneM2M, constitutes acceptance of and agreement to be bound by terms of the Working Procedures and the
Partnership Agreement, including the Intellectual Property Rights (IPR) Principles Governing oneM2M Work found in
Annex 1 of the Partnership Agreement.
10
11
12
This contribution summarizes potential requirements from all industrial use cases collected in TR-0018
“Industrial Domain Enablement”.
13
© 2015 oneM2M Partners
Page 1 (of 2)
Doc# oneM2M-REQ-2015-0640-TR-0018_Overview_of_Potential_Requirements
14
7
15
16
Potential requirements from all industrial use cases collected in this technical report are summarized
as follows,
17
18
1.
2.
3.
4.
5.
6.
7.
8.
46
The oneM2M System shall be able to support mechanism for the M2M Devices and/or
Gateways to report their geographical location information to M2M Applications.
Note: From use case 6.4 “Aircraft construction and maintenance”; Supported by OSR-047.
43
44
45
The oneM2M system shall be able to share data collection policies among multiple M2M
Devices/Gateways within an M2M application service, or among different M2M application
services. (OSR-097)
Note: From use case 6.3 “Data Process for Inter-factory manufacturing”; CR to TS-0002 agreed as REQ2015-0583R01.
39
40
41
42
The oneM2M System shall be able to provide the M2M applications with status information
received from the Underlying Network. (OPR-008)
Note: From use case 6.2; CR to TS-0002 agreed as REQ-2015-0550R03.
35
36
37
38
The oneM2M System shall be able to support receipt of the status information of the
Underlying Network if supported by the Underlying Network. (OPR-007)
Note: From use case 6.2; CR to TS-0002 agreed as REQ-2015-0550R03.
32
33
34
The oneM2M System shall be able to detect and report the missing data in time series. (OSR076)
Note: From use case 6.2; CR to TS-0002 agreed as REQ-2015-0546R01.
29
30
31
The oneM2M System shall be able to collect, store time series data. (OSR-075)
Note: From use case 6.2 “Integrity of Data Collection Monitoring”; CR to TS-0002 agreed as REQ-20150546R01.
25
26
27
28
The oneM2M system shall allow the update, modification, or deletion of data collection
policies within an M2M application. (OSR-082)
Note: From use case 6.1; CR to TS-0002 agreed as REQ-2015-0553R02.
23
24
The oneM2M System shall be able to collect data that is broadcast (e.g. in industrial bus
systems) according to data collection policies. (OSR-081)
Note: From use case 6.1 “An industrial use case for on-demand data collection for factories”; CR to TS0002 agreed as REQ-2015-0553R02.
19
20
21
22
Overview of Potential Requirements
9.
The oneM2M System shall support the ability for single or multiple M2M Applications to
interact with a single or multiple M2M Devices/Gateways (application in the device/gateway).
Note: From use case 6.4; Supported by OSR-009.
47
48
10. The oneM2M system shall be able to identify a series of data (e.g. time series data) and
indicate individual data belong to this series. (CMR-015)
49
50
Note: From use case 6.5 “Real Time Data Collection”; CR to TS-0002 agreed as REQ-2015-0601R01 and
REQ-2015-0635.
51
52
11. The oneM2M system shall be able to transmit data according to priority.
Note: From use case 6.5; Supported by CMR-003.
© 2015 oneM2M Partners
Page 1 (of 2)
Doc# oneM2M-REQ-2015-0640-TR-0018_Overview_of_Potential_Requirements
53
54
55
12. The oneM2M system shall support classification of application data by oneM2M applications
into various security levels that are specified by oneM2M and support the mapping of these
levels to applicable security capabilities. (SER-045)
56
57
Note: From use case 6.6 “Data Encryption in Industrial Domain”; CR to TS-0002 agreed as REQ-20150604R02.
58
59
13. The oneM2M System shall support the inclusion of M2M Application’s QoS preference in
service requests to Underlying Networks
60
61
62
63
64
Note: From use case 6.7 “QoS/QoI monitoring in industrial domain”; Supported by OSR-038.
14. The oneM2M System shall provide the capability for monitoring and describing data streams
with associated attributes e.g. data freshness, accuracy, sampling rate, data integrity. (OSR092)
Note: From use case 6.7; CR to TS-0002 agreed as REQ-2015-0629.
65
66
© 2015 oneM2M Partners
Page 1 (of 2)