Connectivity Framework Annex C: Assessment Template: oneM2M
C. 6.5 Implementation Viewpoint C. 6.5.4 Scalability Considerations
Data Objects( Section 4.2.4.1)
Apps( Section 4.2.4.2)
C. 6.5.5 Availability Considerations
Redundancy( Section 4.2.5.1)
Recovery( Section 4.2.5.2)
C. 6.5.6 Deployment Considerations
Platforms Constraints( Section 4.2.6.1)
Incremental Upgrades
( Section 4.2.6.2)
Can the connectivity framework effectively handle an increasing number of data objects? What limits data object size?
Yes, oneM2M service layer can handle an increasing number of data-objects; however, the size of the object identifiers is limited by the size of string data type and that defines an upper bound on the maximum number of data objects.
There is no theoretical limit on the data-object size. In practice, it will be limited by the amount of memory available on a host or the constraints of the underlying transport.
Can the connectivity framework effectively support interface evolution for an increasing number of distributed application components?
Yes, oneM2M service layer can effectively support interface evolution for an increasing number of distributed application components. Application components are loosely coupled--they interact with resources in CSEs not with each other; the interfaces are dataoriented and can evolve independently. Applications are in complete control of how the data-object resources are organized and identified.
Can the connectivity framework support continuous availability over a defined systemrelevant time period?
Yes, as a service layer oneM2M does not place constraints on the availability of CSEs or applications. CSEs can use standard techniques for redundancy( load-balancers, clusters, virtualized environments). Can the connectivity framework support recovery when fault conditions occur?
Yes, oneM2M service layer can support recovery when fault conditions occur. It accomplishes this by informing applications of errors and by allowing applications to change the behavior of how the system treats communication with endpoints.
Does the connectivity framework support the operating system( OS), the CPU and the resource constraints on the platform( s) being used?
Yes, oneM2M service layer does not require a specific type of OS, CPU or even the database management system. oneM2M has been architected to work with constrained devices in mind. Does the connectivity framework facilitate incremental upgrades?
Yes, the oneM2M service layer does not place constraints on the upgradability of CSEs or applications. CSEs can use standard techniques for upgrading the CSE( load-balancers, clusters, virtualized environments).
IIC: PUB: G5: V1.0: PB: 20170228- 92-