1 Scope
2 References
3 Definitions
3.1 Terms defined elsewhere
3.2 Terms defined in this Recommendation
3.3 Abbreviations and acronyms
4 Conventions
5 Architecture model
5.1 General concepts
5.2 Architecture reference model
6 oneM2M architecture aspects
6.1 Configurations supported by oneM2M architecture
6.2 Common services functions
6.3 Security aspects
6.4 Intra-M2M SP communication
6.5 Inter-M2M SP communication
6.6 M2M service subscription
7 M2M entities and object identification
7.1 M2M identifiers
7.2 M2M-SP-ID, CSE-ID, App-ID and AE-ID and resource identifier
formats
7.3 M2M identifiers lifecycle and characteristics
8 Description and flows of reference points
8.1 General communication flow scheme on Mca and Mcc reference
points
8.2 Procedures for accessing resources
8.3 Procedures for interaction with underlying networks
8.4
Connection request
8.5 Device
management
9 Resource management
9.0 Overview
9.1 General principles
9.2 Resources
9.3 Resource addressing
9.4 Resource structure
9.5 Resource type specification conventions
9.6 Resource types
10 Information flows
10.1 Basic procedures
10.2 Resource type-specific procedures
10.3 Notification procedures
11 Trust enabling architecture
11.0 Overview
11.1 Enrolling M2M nodes and M2M applications for oneM2M services
11.2 M2M Initial provisioning procedures
11.3 M2M operational security procedures
11.4 Functional architecture specifications for end-to-end security
procedures
11.5 Functional architecture specifications for dynamic
authorization
12 Information recording
12.1 M2M infrastructure node (IN) information recording
12.2 Offline charging
Annex A – Void
Annex B – Void
Annex C – Void
Annex D – <mgmtObj> Resource instances description
D.1 oneM2M management functions
D.2 Resource firmware
D.3 Resource software
D.4 Resource memory
D.5 Resource areaNwkInfo
D.6 Resource areaNwkDeviceInfo
D.7 Resource battery
D.8 Resource deviceInfo
D.9 Resource deviceCapability
D.10 Resource reboot
D.11 Resource eventLog
D.12 Resource cmdhPolicy
Annex E – Void
Annex F – Void
Annex G – Void
Annex H – Void
Annex I – Void
Annex J – Void
Annex K – Syntaxes for content based discovery of <contentInstance>
K.1 Introduction
K.2 'jsonpath' query syntax
Annex L – oneM2M Specification update and maintenance control procedure
Page
Appendix I – Mapping of requirements with CSFs
Appendix II – oneM2M system and 3GPP MTC underlying network interworking
II.1 3GPP MTC underlying network introduction
II.2 3GPP MTC functionality
II.3 ASN/MN-CSE initiated connectivity establishment
II.4 Serving IN-CSE initiated connectivity establishment
II.5 Connectivity between oneM2M service layer and 3GPP underlying
network
II.6 Connectivity establishment procedures
Appendix III – Interworking between oneM2M system and 3GPP2 underlying
networks
III.1 General concepts
III.2 M2M communication models
III.3 3GPP2 Architectural reference model for M2M
III.4 Communication between oneM2M service layer and 3GPP2 underlying
network
III.5 Information flows
Appendix IV – Void
Appendix V – CSE minimum provisioning
Appendix VI – Interworking/Integration of non-oneM2M solutions and
protocols
VI.1 Introduction
VI.2 Interworking with non-oneM2M solutions through specialized
interworking applications
VI.3 Interworking versus integration of non-oneM2M solutions
VI.4 Entity-relation representation of non-IP based M2M area network
Appendix VII – Void
Appendix VIII – Object identifier based M2M device identifier
VIII.1 Overview of object identifier
VIII.2 OID based M2M device identifier
VIII.3 Example of M2M device ID based on OID
Appendix IX – Resource addressing examples
IX.1 Example resource tree
IX.2 Valid resource IDs
Bibliography