Connectivity Framework Annex C: Assessment Template: oneM2M
C. 6.5 Implementation Viewpoint C. 6.5.1 System Architecture Considerations
Peer-to-Peer vs. Broker:
( Section 4.2.1.1)
Data-Centric vs. Device / App-Centric:( Section 4.2.1.2)
Explicit vs. Implicit Governance:( Section 4.2.1.3)
C. 6.5.2 Data Considerations
Content-Based Selection( Section 4.2.2.1)
Time-Based Selection( Section 4.2.2.2)
C. 6.5.3 Performance Considerations
Real-Time( Section 4.2.3.1)
Latency and Jitter vs. Throughput
( Section 4.2.3.2)
Does the connectivity framework require running a special process or broker?
Yes – oneM2M service layer requires applications to connect to a CSE to communicate with other applications. The target applications are not required to be connected to the same CSE as the source applications. CSEs are connected in a hierarchical tree topology with a root CSE( i. e., IN-CSE) that is in the domain of the M2M service provider.
Does the application code( or business logic) have to be aware of the other endpoints in order to participate in information exchange?
No, the application does not have to be aware of other endpoints to participate in an information exchange. Applications interact directly with the data-object resources organized by the owning application and never directly with each other. Is the governance explicit and shareable?
With the exception that oneM2M has defined the domain of data types and resources used by applications and CSE, oneM2M service layer does not require the governance to be implicit, and allows system architects to choose the style of governance including how data-object resources are structured and identified.
Can a content-filter specify the data subset of interest?
Yes, oneM2M service layer provides a number of content-filters that can be used for discovery of resources( e. g., time, size, content type, user defined, semantic criteria). Can sub-sampling specify the data subset of interest?
Yes, oneM2M service layer has a number of filters for time-based selection based on creation, modification and expiration times. In oneM2M there is a specialized content based resource, called timeSeries, which provides various criteria for collection( sampling) and reporting of data.
Does the connectivity technology support real-time data distribution? Is the latency deterministic( smaller jitter is better)?
To date, the real-time data distribution performance of oneM2M deployments have not been documented and made publicly available. Real-time characterization is not currently available. How does the latency and jitter change with throughput? What limits the throughput?
To date, the latency and jitter aspects of throughput of oneM2M deployments have not been documented and made publicly available. Latency and jitter characterization is not currently available.
IIC: PUB: G5: V1.0: PB: 20170228- 91-