Protocol Analysis

Protocol Analysis

1 2 3 4 5 6 7 8 9 This Specification is provided for future development work within oneM2M only. The Partners accept no 10 liability for any use of this Specification. 11 The present document has not been subject to any approval process by the oneM2M Partners Type 1. 12 Published oneM2M specifications and reports for implementation should be obtained via the oneM2M 13 Partners' Publications Offices. 14 15 16 © oneM2M Partners Type 1 (ARIB, ATIS, CCSA, ETSI, TIA, TTA, TTC) Page 1 of 107 This is a draft oneM2M document and should not be relied upon; the final version, if any, will be made available by oneM2M Partners Type 1. 17 About oneM2M 18 The purpose and goal of oneM2M is to develop technical specifications which address the 19 need for a common M2M Service Layer that can be readily embedded within various 20 hardware and software, and relied upon to connect the myriad of devices in the field with 21 M2M application servers worldwide. 22 More information about oneM2M may be found at: http//www.oneM2M.org 23 Copyright Notification 24 No part of this document may be reproduced, in an electronic retrieval system or otherwise, 25 except as authorized by written permission. 26 The copyright and the foregoing restriction extend to reproduction in all media. 27 © 2014, oneM2M Partners Type 1 (ARIB, ATIS, CCSA, ETSI, TIA, TTA, TTC). 28 All rights reserved. 29 Notice of Disclaimer & Limitation of Liability 30 The information provided in this document is directed solely to professionals who have the 31 appropriate degree of experience to understand and interpret its contents in accordance with 32 generally accepted engineering or other professional standards and applicable regulations. 33 No recommendation as to products or vendors is made or should be implied. 34 NO REPRESENTATION OR WARRANTY IS MADE THAT THE INFORMATION IS 35 TECHNICALLY ACCURATE OR SUFFICIENT OR CONFORMS TO ANY STATUTE, 36 GOVERNMENTAL RULE OR REGULATION, AND FURTHER, NO 37 REPRESENTATION OR WARRANTY IS MADE OF MERCHANTABILITY OR 38 FITNESS FOR ANY PARTICULAR PURPOSE OR AGAINST INFRINGEMENT OF 39 INTELLECTUAL PROPERTY RIGHTS. NO oneM2M PARTNER TYPE 1 SHALL BE 40 LIABLE, BEYOND THE AMOUNT OF ANY SUM RECEIVED IN PAYMENT BY 41 THAT PARTNER FOR THIS DOCUMENT, WITH RESPECT TO ANY CLAIM, AND IN 42 NO EVENT SHALL oneM2M BE LIABLE FOR LOST PROFITS OR OTHER 43 INCIDENTAL OR CONSEQUENTIAL DAMAGES. oneM2M EXPRESSLY ADVISES 44 ANY AND ALL USE OF OR RELIANCE UPON THIS INFORMATION PROVIDED IN 45 THIS DOCUMENT IS AT THE RISK OF THE USER. 46 47 © oneM2M Partners Type 1 (ARIB, ATIS, CCSA, ETSI, TIA, TTA, TTC) Page 2 of 107 This is a draft oneM2M document and should not be relied upon; the final version, if any, will be made available by oneM2M Partners Type 1. 48 Contents 49 Contents .............................................................................................................................................................. 3 50 1 Scope ........................................................................................................................................................ 8 51 2 References ................................................................................................................................................ 8 52 2.1 Informative references ....................................................................................................................................... 8 53 3 Abbreviations and acronyms .................................................................................................................. 12 54 3.1 Abbreviations ................................................................................................................................................... 12 55 3.2 Acronyms ......................................................................................................................................................... 12 56 4 Conventions, ........................................................................................................................................... 14 57 5 M2M Related Protocols Overview ......................................................................................................... 14 58 5.1 Analysis of Design Styles ................................................................................................................................ 14 59 5.1.1 RESTful Style protocols ............................................................................................................................. 14 60 5.1.1.1 REST Style ........................................................................................................................................... 14 61 5.1.1.2 RESTful Protocols ................................................................................................................................ 15 62 5.2 Data Description Standards.............................................................................................................................. 15 63 5.2.1 XML Schema Definition Language (XSD) ................................................................................................ 15 64 6 Analysis of Protocols ............................................................................................................................. 15 65 6.1 CoAP - Constrained Application Protocol ....................................................................................................... 15 66 6.1.1 Background ................................................................................................................................................ 15 67 6.1.2 Status .......................................................................................................................................................... 16 68 6.1.2.1 Current Status ....................................................................................................................................... 16 69 6.1.2.2 Ongoing IETF Activity ......................................................................................................................... 16 70 6.1.3 Category and Architectural Style ............................................................................................................... 17 71 6.1.4 Intended use ............................................................................................................................................... 17 72 6.1.5 Deployment Trend ..................................................................................................................................... 18 73 6.1.6 Key features ............................................................................................................................................... 18 74 6.1.7 Protocol Stack ............................................................................................................................................ 19 75 6.1.8 Data Model ................................................................................................................................................. 20 76 6.1.9 Security ...................................................................................................................................................... 20 77 6.1.10 Dependencies ............................................................................................................................................. 20 78 6.1.11 Benefits and Constraints ............................................................................................................................. 20 79 6.1.11.1 Benefits ................................................................................................................................................. 20 80 6.2.11.2 Constraints ............................................................................................................................................ 21 81 6.1.12 Support of oneM2M requirements ............................................................................................................. 21 82 6.1.12.1 Fully Supported Requirements ............................................................................................................. 21 83 6.1.12.2 Partially Supported Requirements ........................................................................................................ 21 84 6.2 MQTT - Message Queuing Telemetry Transport ............................................................................................ 21 85 6.2.1 Background ................................................................................................................................................ 21 86 6.2.2 Status .......................................................................................................................................................... 22 87 6.2.3 Category and Architectural Style ............................................................................................................... 22 88 6.2.4 Intended use ............................................................................................................................................... 22 89 6.2.5 Deployment Trend ..................................................................................................................................... 22 90 6.2.6 Key features ..............................................................................................................................................

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    107 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us