Requirements (oneM2M TS-0002-v1.0.1)

1 Scope
The present document contains an informative functional role model and normative technical requirements for oneM2M.
2 References
2.1 Normative references
References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies.
The following referenced documents are necessary for the application of the present document.
[1] 3GPP TS 22.368: “Service requirements for Machine-Type Communications (MTC); Stage 1”.
[2] oneM2M TR-0008: “Security Analysis”.
2.2 Informative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies.
The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area.
[i.1] oneM2M Drafting Rules.
NOTE: Available at http://member.onem2m.org/Static_pages/Others/Rules_Pages/oneM2M-Drafting-Rules V1_0.doc.
[i.2] oneM2M TS-0011: “Common Terminology”.
[i.3] 3GPP2 S.R0146: “M2M System Requirements”.
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions are given in oneM2M TS-0011 [i.2].
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
CHA Continua Health Alliance
GSMA Global System for Mobile Communications Association
HSM Hardware Security Module
OMA Open Mobile Alliance
QoS Quality of Service
SMS Short Message Service
USSD Unstructured Supplementary Service Data
WAN Wide Area Network
4 Conventions
The keywords “shall”, “shall not”, “should”, “should not”, “may”, “need not” in the present document are to be interpreted as described in the oneM2M Drafting Rules [i.1].
Note: according to oneM2M Drafting Rules [i.1] in order to mandate a feature in the oneM2M System but allow freedom to the individual deployment whether to use it or not subsequently requirements are often formulated like:
“The oneM2M System shall support a mechanism [function, capability…] to …”, or
“…shall be able to …”.
This does not mandate usage of the required feature in a M2M Solution.