Connectivity Framework Annex C : Assessment Template : oneM2M
C . 6.3 Usage Viewpoint
C . 6.3.3 Applications ( Section 6.3.3 )
C . 6.3.4 Typical
Usage ( Section 2.2 )
C . 6.3.5 Operations ( Section 2.3.8 )
C . 6.3.6 Security ( Section 2.3.5 )
A general statement of the typical applications that rely on this connectivity technology and the reason for using the connectivity technology .
oneM2M has commercial deployments home automation applications and is being actively developed for applications in the automotive and smart-city domains . Reasons for using oneM2M include :
• Ease of Integration : The RESTful architectural approach used by oneM2M allows the definition of common and extensible data models for seamless Information Technology ( IT )/ Operational Technology ( OT ) interoperability .
• Performance efficiency and scalability : oneM2M implementations allow for deployment configurations that place processing at locations where it can be used in the most efficient manner . This allows for localization of messaging traffic to affected area networks . When properly architected , oneM2M-based systems can achieve near-linear scalability .
• Advanced security : oneM2M defines a comprehensive security model for segment and end-to-end authentication , encryption , access control and logging capabilities to enable secure data connectivity end-to-end in an IoT system .
• QoS-enabled : Determination of how a CSE treats , in terms of message delivery , is configurable based on a rich set of delivery policies including policies that allow the underlying network to be tuned to the message delivery characteristics of communicating applications .
• Scalable discovery : For large-scale dynamic systems , oneM2M is in the process of developing automated onboarding and discovery of applications .
• Applicability : oneM2M can transparently address applications that require data to be exchange between applications that transit through a CSE . Implementations are available for embedded , mobile , web , enterprise and cloud applications .
• Future proof : The oneM2M specification enables end-to-end vendor interoperability and eases IoT system development and integration through fully open , future-proof APIs with no vendor lock in .
What function or where in the system this technology is typically used ?
• Registration and Service Subscription ( Device and application onboarding and discovery ): Used in infrastructure CSE .
• Discovery of resources : Used in all CSEs .
• Service charging and accounting : Used in the infrastructure CSE .
• Data plane ( data collection ; subscription and notifications , data delivery , group management ): Used in all CSEs .
• Management plane ( administration of applications and CSEs , device management ): Used in Infrastructure CSEs .
• Integration with the underlying network layer services : Used in the Infrastructure CSEs .
Can one monitor , manage , and dynamically replace elements of the connectivity function ?
oneM2M service layer provides the capability to monitor and manage applications and CSEs . These components are the building blocks of any oneM2M deployment . What are the system security implications of this connectivity technology ?
oneM2M service layer defines a security model to authenticate applications and CSEs . All communication can be securely encrypted as a segment or end-to-end using the underlying network layer security mechanisms ( e . g ., TLS , DTLS ). The security model is applied on top of the network layer .
IIC : PUB : G5 : V1.0 : PB : 20170228 - 86 -