Book and Manual Test
 |
|
|---|---|
| Lightweight Machine to Machine Technical Specification | |
| Draft Version 1.0 – 07 May 2014 | |
| Open Mobile Alliance | |
| OMA-TS-LightweightM2M-V1_0-20140507-D | |
Use of this document is subject to all of the terms and conditions of the Use Agreement located at http://www.openmobilealliance.org/UseAgreement.html.
Unless this document is clearly designated as an approved specification, this document is a work in process, is not an approved Open Mobile Alliance™ specification, and is subject to revision or removal without notice.
You may use this document or any part of the document for internal or educational purposes only, provided you do not modify, edit or take out of context the information in this document in any manner. Information contained in this document may be used, at your sole risk, for any purposes. You may not use this document in any other manner without the prior written permission of the Open Mobile Alliance. The Open Mobile Alliance authorizes you to copy this document, provided that you retain all copyright and other proprietary notices contained in the original materials on any copies of the materials and that you comply strictly with these terms. This copyright permission does not constitute an endorsement of the products or services. The Open Mobile Alliance assumes no responsibility for errors or omissions in this document.
Each Open Mobile Alliance member has agreed to use reasonable endeavors to inform the Open Mobile Alliance in a timely manner of Essential IPR as it becomes aware that the Essential IPR is related to the prepared or published specification. However, the members do not have an obligation to conduct IPR searches. The declared Essential IPR is publicly available to members and non-members of the Open Mobile Alliance and may be found on the “OMA IPR Declarations” list at http://www.openmobilealliance.org/ipr.html. The Open Mobile Alliance has not conducted an independent IPR review of this document and the information contained herein, and makes no representations or warranties regarding third party IPR, including without limitation patents, copyrights or trade secret rights. This document may contain inventions for which you must obtain licenses from third parties before making, using or selling the inventions. Defined terms above are set forth in the schedule to the Open Mobile Alliance Application Form.
NO REPRESENTATIONS OR WARRANTIES (WHETHER EXPRESS OR IMPLIED) ARE MADE BY THE OPEN MOBILE ALLIANCE OR ANY OPEN MOBILE ALLIANCE MEMBER OR ITS AFFILIATES REGARDING ANY OF THE IPR’S REPRESENTED ON THE “OMA IPR DECLARATIONS” LIST, INCLUDING, BUT NOT LIMITED TO THE ACCURACY, COMPLETENESS, VALIDITY OR RELEVANCE OF THE INFORMATION OR WHETHER OR NOT SUCH RIGHTS ARE ESSENTIAL OR NON-ESSENTIAL.
THE OPEN MOBILE ALLIANCE IS NOT LIABLE FOR AND HEREBY DISCLAIMS ANY DIRECT, INDIRECT, PUNITIVE, SPECIAL, INCIDENTAL, CONSEQUENTIAL, OR EXEMPLARY DAMAGES ARISING OUT OF OR IN CONNECTION WITH THE USE OF DOCUMENTS AND THE INFORMATION CONTAINED IN THE DOCUMENTS.
© 2014 Open Mobile Alliance Ltd. All Rights Reserved.Used with the permission of the Open Mobile Alliance Ltd. under the terms set forth above.
Contents
1.Scope 9
2.References 10
2.1Normative References 10
2.2Informative References 11
3.Terminology and Conventions 12
3.1Conventions 12
3.2Definitions 12
3.3Abbreviations 12
4.Introduction 13
4.1Version 1.0 14
5.Interfaces 15
5.1Bootstrap Interface 16
5.1.1 Bootstrap Information 16
5.1.2 Bootstrap Modes 17
5.1.3 Bootstrap Sequence 19
5.1.4 Bootstrap Security 19
5.2Client Registration Interface 20
5.2.1 Register 20
5.2.2 Update 23
5.2.3 De-register 23
5.3Device Management & Service Enablement Interface 23
5.3.1 Read 25
5.3.2 Discover 25
5.3.3 Write 26
5.3.4 Write Attributes 26
5.3.5 Execute 27
5.3.6 Create 27
5.3.7 Delete 28
5.4Information Reporting Interface 28
5.4.1 Observe 29
5.4.2 Notify 29
5.4.3 Cancel Observation 31
6.Identifiers and Resources 32
6.1Resource Model 32
6.2Identifiers 33
6.2.1 Endpoint Client Name 34
6.2.2 Reusable Resources 35
6.3Data Formats for Transferring Resource Information 35
6.3.1 Plain Text 35
6.3.2 Opaque 35
6.3.3 TLV 35
6.3.4 JSON 39
7.Security 41
7.1UDP Channel Security 41
7.1.1 Pre-Shared Keys 42
7.1.2 Raw Public Key Certificates 42
7.1.3 X.509 Certificates 43
7.1.4 “NoSec” mode 44
7.2SMS Channel Security 44
7.2.1 SMS “NoSec” mode 45
7.2.2 SMS Secured Packet Structure mode 45
7.3Access Control 47
7.3.1 Access Control Object 47
7.3.2 Authorization 50
8.Transport Layer Binding and Encodings 52
8.1Required Features 52
8.2URI Identifier & Operation Mapping 52
8.2.1 Firewall/NAT 52
8.2.2 Bootstrap Interface 53
8.2.3 Registration Interface 54
8.2.4 Device Management & Service Enablement Interface 55
8.2.5 Information Reporting Interface 57
8.3Queue Mode Operation 58
8.4Update Trigger Mechanism 61
8.5Response Codes 62
8.6Transport Bindings 64
8.6.1 UDP Binding 64
8.6.2 SMS Binding 64
Appendix A.Change History (Informative) 65
A.1Approved Version History 65
A.2Draft/Candidate Version 1.0 History 65
Appendix B.Static Conformance Requirements (Normative) 71
B.1SCR for LWM2M Client 71
B.1.1 Bootstrap Interface 71
B.1.2 Client Registration 71
B.1.3 Device Management and Service Enablement Interface 72
B.1.4 Information Reporting 72
B.1.5 Data Format 73
B.1.6 Security 73
B.1.7 Mechanism 73
B.1.8 Objects 74
B.2SCR for LWM2M Server 74
B.2.1 Bootstrap Interface 74
B.2.2 Client Registration 74
B.2.3 Device Management and Service Enablement Interface 75
B.2.4 Information Reporting 75
B.2.5 Data Format 75
B.2.6 Security 75
B.2.7 Mechanism 76
B.2.8 Objects 76
Appendix C.Data Types (Normative) 77
Appendix D.LWM2M Object Template and Guidelines (Normative) 78
D.1Object Template 78
D.2Open Mobile Naming Authority (OMNA) Guidelines 79
D.2.1 Object Registry 79
D.2.2 Resource Registry 79
Appendix E.LWM2M Objects defined by OMA (Normative) 80
E.1LWM2M Object: LWM2M Security 80
E.1.1 UDP Channel Security: Security Key Resource Format 83
E.1.2 SMS Payload Security: Security Key Resource Format 83
E.1.3 Unbootstrapping 83
E.2LWM2M Object: LWM2M Server 84
E.3LWM2M Object: Access Control 85
E.3.1 Object Instance Configurations 86
E.4LWM2M Object: Device 87
E.5LWM2M Object: Connectivity Monitoring 91
E.6LWM2M Object: Firmware Update 93
E.6.1 Firmware Update Consideration 95
E.7LWM2M Object: Location 95
E.8LWM2M Object: Connectivity Statistics 95
Appendix F.Example LWM2M Client (Informative) 97
Appendix G.Storage of LWM2M Bootstrap Information on the Smartcard (Normative) 102
G.1File structure 102
G.2Bootstrap Information on UICC (Activated in 3G Mode) 102
G.2.1 Access to the file structure 102
G.2.2 Files Overview 103
G.2.3 Access Method 103
G.2.4 Access Conditions 103
G.2.5 Requirements on the 3G UICC 103
G.3Files Description 103
G.3.1 Object Directory File, EF ODF 103
G.3.2 Bootstrap Data Object Directory File, EF DODF-bootstrap 104
G.3.3 EF LWM2M_Bootstrap 104
Appendix H.Secure channel between Smartcard and LWM2M Device Storage for secure Bootstrap Data provisioning (Normative) 106
Figures
Figure 1: The overall architecture of the LWM2M Enabler. 12
Figure 2: The protocol stack of the LWM2M Enabler. 13
Figure 3: Bootstrap 14
Figure 4: Client Registration 14
Figure 5: Device Management and Service Enablement 14
Figure 6: Information Reporting 15
Figure 7: Procedure of Client Initiated Bootstrap 17
Figure 8: Procedure of Server Initiated Bootstrap 18
Figure 9: Client Registration Interface example flows. 19
Figure 10: Example flows of Device Management & Service Enablement Interface 23
Figure 12: Example of Minimum and Maximum periods in an Observation. 29
Figure 13: Relationship between LWM2M Client, Object, and Resources 31
Figure 14: Example of Supported operations and Associated Access Control Object Instance 32
Figure 15: TLV nesting 36
Figure 17: Example of Client initiated Bootstrap exchange. 52
Figure 18: Example of Server initiated Bootstrap exchange. 53
Figure 20: Example of Device Management & Service Enablement interface exchanges. 56
Figure 21: Example of Object Creation and Deletion. 56
Figure 22: Example of an Information Reporting exchange. 57
Figure 23: Example of Device Management & Service Enablement interface exchanges for Queue Mode. 59
Figure 24: Example of an Information Reporting exchange for Queue Mode. 60
Figure 25: Example of Device Management & Service Enablement interface exchanges for Queue Mode with SMS Registration Update Trigger. 61
Figure 26: 3G UICC File Structure and Bootstrap data location 102
Tables
Table 1: Relationship of operations and interfaces 15
Table 2: Bootstrap Information List 16
Table 3: Registration parameters 20
Table 4: Behaviour with Current Transport Binding and Mode 22
Table 5: Update parameters 22
Table 7: Discover parameters 24
Table 9: Write Attributes parameters 26
Table 10: Execute parameters 26
Table 11: Create parameters 27
Table 12: Delete parameters 27
Table 13: Observe parameters 28
Table 14: Notify parameters 29
Table 15: LWM2M Identifiers 33
Table 16: TLV format and description 35
Table 17: JSON format and description 39
Table 18: Operation to Method and URI Mapping 52
Table 19: Operation to Method and URI Mapping 53
Table 20: Operation to Method Mapping 55
Table 21: Operation to Method Mapping 57
Table 23: LWM2M Objects defined by OMA LWM2M 1.0 79
Table 24: Object Instances of the example 96
Table 25: LWM2M Security Object [0] 96
Table 26: LWM2M Security Object [1] 96
Table 27: LWM2M Security Object [2] 97
Table 28: LWM2M Server Object [1] 97
Table 29: LWM2M Server Object [2] 97
Table 30: Access Control Object [0] (for the LWM2M Server Object) 98
Table 31: Access Control Object [1] (for the LWM2M Server Object) 98
Table 32: Access Control Object [2] (for the Device Object) 98
Table 33: Access Control Object [3] (for the Connectivity Monitoring Object) 99
Table 34: Access Control Object [4] (for the Firmware Update Object) 99