The rapid growth of the M2M and IoT market can only really succeed with standardisation – a means of guaranteeing seamless operability for developers who are building applications with data from multiple different sources or deploying devices that use a plethora of communication technologies.
This is why GCF has partnered with the leading global standardisation body for oneM2M, to provide a certification programme that facilitates interoperability and standardisation for IoT applications where performance, reliability and security are critical. It provides access to a simplified interface for all certification requirements.
Upcoming oneM2M certification releases will include support for:
- Industrial domain enablement: real time data collection, redundancy and fault tolerance, enablers for analytics
- Home domain enablement: home appliance information models, ontologies and mapping to existing standards
- Interworking between oneM2M architecture and 3GPP Rel-16 architecture for service capability exposure, and vehicular domain enablement for 3GPP C-V2X
- Dynamic authorisations and end-to-end security: device onboarding and provisioning
- Semantic interoperability: base ontology, link to domain specific ontologies, semantic description and discovery
- oneM2M as a generic interworking framework: OMA lightweight M2M, OIC, AllJoyn etc.
With 5G happening now and the prolific growth of IoT connectivity, oneM2M certification is critical to the standardisation of converging technologies from multiple industries.
The purpose and goal of oneM2M is to develop technical specifications which address the need for a common M2M service layer that can be readily embedded within various hardware and software, and relied up on to connect the myriad of devices in the field with M2M application servers worldwide.
To hear more about this initiative and to get involved in shaping the programme please reach out to the GCF team
Guidance on oneM2M applications
oneM2M Application Developer Guides: http://www.onem2m.org/developer-guides
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 documents 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.
oneM2M Application-ID Registry hosted by iconectiv.com: http://www.onem2m.org/developers-corner/tools/app-id-registry
oneM2M protocols require unique identification of oneM2M applications. The use of non-standard identifiers and proprietary formats for identifying software applications makes interconnection extremely difficult, as well as not necessarily being unique. It also prevents effective tracking and reporting necessary for service fulfilment and billing.