Developer Guides: Difference between revisions
No edit summary |
No edit summary |
||
Line 20: | Line 20: | ||
<ul><li>[[3GPP|3GPP interworking example (soon)]]</ul> | <ul><li>[[3GPP|3GPP interworking example (soon)]]</ul> | ||
<ul><li>[[SDT|Smart Device Template based implementation (soon)]]</ul> | <ul><li>[[SDT|Smart Device Template based implementation (soon)]]</ul> | ||
oneM2M has worked on a series of developer guides, proposing a guideline for application developers who want to use functionalities offered by an oneM2M service platform. | |||
When implementing a standard, it is frequently requested from software developer community to get some tutorials describing for basic use cases, some procedures and scenarios, including diagrams, message flows, message traces samples, resource description samples, etc.. … | |||
Such document would be helpful in software development to provide overall understanding of the main functions offered by the oneM2M architecture, before going more deeply into the analysis of the oneM2M standards. | |||
Use cases examples | |||
TR-0025 : Light control using HTTP binding : TR-0025 | |||
TR-0034 : Temperature Monitoring using CoAP binding : TR-0034 | |||
TR-0035 : Device Management example: TR-0035 | |||
TR-0037 : Smart farm example using MQTT binding : TR-0037 | |||
TR-0038 : Implementing security : TR-0038 | |||
TR-0039 : Interworking proxy using SDT : TR-0039 | |||
TR-0045 : Implementing semantics : TR-0045 |
Revision as of 16:47, 12 March 2019
oneM2M has worked on a series of developer guides, propsing a guideline for application developers who want to use functionalities offered by an oneM2M service platform. When implementing a standard, it is frequently requested from software developer community to get some tutorials describing for basic use cases, some procedures and scenarios, including diagrams, message flows, message traces samples, resource description samples, etc.. … Such document would be helpful in software development to provide overal understanding of the main functions offered by the oneM2M architecture, before going more deeply into the analysis of the oneM2M standards.
oneM2M sample use cases
Use cases examples
oneM2M has worked on a series of developer guides, proposing a guideline for application developers who want to use functionalities offered by an oneM2M service platform.
When implementing a standard, it is frequently requested from software developer community to get some tutorials describing for basic use cases, some procedures and scenarios, including diagrams, message flows, message traces samples, resource description samples, etc.. …
Such document would be helpful in software development to provide overall understanding of the main functions offered by the oneM2M architecture, before going more deeply into the analysis of the oneM2M standards.
Use cases examples
TR-0025 : Light control using HTTP binding : TR-0025
TR-0034 : Temperature Monitoring using CoAP binding : TR-0034
TR-0035 : Device Management example: TR-0035
TR-0037 : Smart farm example using MQTT binding : TR-0037 TR-0038 : Implementing security : TR-0038
TR-0039 : Interworking proxy using SDT : TR-0039
TR-0045 : Implementing semantics : TR-0045