Connectivity Framework Annex C: Assessment Template: oneM2M
C. 6.4 Functional Viewpoint C. 6.4.2 Core Transport Layer Functions
Messaging Protocol( Section 5.1.1)
Communication Modes( Section 5.1.2)
Endpoint Addressing
( Section 5.1.3)
Connectedness( Section 5.1.4)
Prioritization( Section 5.1.5)
Timing & Synchronization( Section 5.1.6)
Message Security( Section 5.1.7)
Does it require UDP or TCP? What are the salient aspects of the messaging protocol? What are the message size limitations? What are the usage assumptions? Is it optimized for certain message requirements?
The oneM2M service layer runs on top of multiple transport protocols that are based on IP( i. e., CoAP, HTTP, Web Sockets, MQTT). oneM2M messages do not have a defined size limitation but are either limited by the underlying transport protocol ' s limitation( e. g., HTTP, Content-Length, MQTT 256Meg) or uses the underlying protocols( e. g., CoAP block) mechanisms for message fragmentation and reassembly. Which communication modes does it support?
oneM2M service layer supports both unicast( default) and multicast( when available by the underlying transport) for group-based operations.
Describe the transport endpoints. How are the endpoints addressed? What are the limitations, if any, on the number of endpoints?
oneM2M service layer is a RESTful architecture where all resources are addressed using URIs, this includes the endpoints represented by applications and CSEs. The URIs can be defined within the address space of the M2M service provider or they can be globally unique id( GUID). Endpoints follow the addressing scheme defined in the oneM2M specification. Does it require a connected circuit between the endpoints? Summarize the salient aspects.
No, oneM2M service layer is a RESTful client / server architecture and does not require a connected circuit between the application endpoints. oneM2M does require endpoints to register with CSE ' s to which it connects, but the registration is not reliant on a connected connection between the endpoints. Does it provide a means to prioritize messages? Summarize the salient aspects.
Yes, oneM2M service layer provides communication QoS policies to determine the priority of delivering request( e. g., recipient, time-of-day, capacity limits). Does it provide the ability to synchronize time? Summarize the salient aspects.
No, oneM2M service layer does not provide a way to synchronize time between endpoints. In oneM2M systems this is typically accomplished using a separate time synchronization protocol. Does it provide mechanisms for message security? Summarize the salient aspects.
Yes, oneM2M service layer provides mechanisms for message security. It provides support for authentication of endpoints either end-to-end or endpoint-to-CSE, message encryption( both end-to-end or endpoint-to-CSE), and message integrity.
IIC: PUB: G5: V1.0: PB: 20170228- 90-