6.7 Communication Management Requirements
Table13: Communication Management Requirements
| Requirement ID | Description | Release |
|---|---|---|
| CMR-001 | The oneM2M System shall provide to M2M Applications a communication service which provides buffering of messages to/from M2M Gateway/Device/ Infrastructure Domain. | Implemented in Rel-1 |
| CMR-002 | The oneM2M System shall be able to support forwarding buffered messages depending on communication policies and based on service preference associated with the buffered messages. | Implemented in Rel-1 |
| CMR-003 | The oneM2M System shall enable an M2M Application to send a communication request with the following service preference: QoS parameters, including delay tolerance, for initiating the delivery of data; categorizing communication requests into different levels of priority or QoS classes. |
Implemented in Rel-1 |
| CMR-004 | The oneM2M System shall be able to support concurrent processing of messages within M2M Gateways and/or M2M Devices from different sources with awareness for the service preference associated with the messages while observing the provisioned communication policies. | Implemented in Rel-1 |
| CMR-005 | The oneM2M System shall be able to maintain context associated with M2M sessions (e.g. security context or network connectivity context during the interruption of the session). | Partially implemented (see note 1) |
| CMR-006 See REQ-2015-0564R02 |
The oneM2M System shall support the ability for applications to categorize requested communications (priority, importance, etc.), so that the oneM2M System can adapt its actual communications (scheduling, aggregation, compression, etc.) by taking this categorization into account. | Implemented in Rel-1 |
| CMR-007 See REQ-2015-0564R02 |
The oneM2M System shall support configurable communication policies that will define its communication patterns. Such policies shall take into account information received from the Underlying Network (such as information referred to in OPR-004) as well as information received from the Applications (such as the information referred to in OPR-005 or categorization of communications requested by the applications). | Partially Implemented (see note 2) |
| CMR-008 See REQ-2015-0564R02 |
The oneM2M System shall support data aggregation based on communication policies when exchanging data between the M2M Gateway/Device/Infrastructure Domain. | Implemented in Rel-1 |
| CMR-009 See REQ-2015-0564R02 |
The oneM2M System should support data compression based on communication policies when exchanging data between the M2M Gateway/Device/Infrastructure Domain. | Not Implemented |
| CMR-010 See REQ-2015-0564R02 |
The oneM2M System shall support an additional randomized delay of communications, based on communication policies, when exchanging data between the M2M Gateway/Device/Infrastructure Domain. | Implemented in Rel-2 |
| CMR-011 See REQ-2015-0564R02 |
The oneM2M System shall be able to monitor its own usage of the Underlying Networks over given periods of time: attempted communications, failed attempts and successful attempts. | Implemented in Rel-2 |
| CMR-012 See REQ-2015-0564R02 |
The oneM2M System shall be able to restrict its own usage of the Underlying Networks, based on communication policies and on its monitored usage of them, when exchanging data between the M2M Gateway/Device/Infrastructure Domain. | Implemented in Rel-2 |
| CMR-013 See REQ-2015-0564R02 |
The oneM2M System shall be able to refrain from using its own usage of the Underlying Networks, based on a time-based back-off procedure configurable in communication policies, when exchanging data between the M2M Gateway/Device/Infrastructure Domain. | Implemented in Rel-2 |
| CMR-014 See REQ-2015-0564R02 |
The oneM2M System shall be able to restrict its own usage of the Underlying Networks, based on communication policies and on the date and time, when exchanging data between the M2M Gateway/Device/Infrastructure Domain. | Implemented in Rel-1 |
| CMR-015 See REQ-2015-0601R01 |
The oneM2M System shall be able to identify a series of data (e.g. Time Series Data) and indicate individual data belonging to this series. | Implemented in Rel-2 |
| CMR-0016 See REQ-2017-0001R03 |
The oneM2M system shall support the data to be transmitted to IoT platform with strict timing and packet loss requirements, determined by the application(s). | Not Implemented |
| CMR-0017 See REQ-2017-0001R03 |
The oneM2M system shall support the data to be transmitted from IoT platform to subscribed devices with highest priority, with strict timing and packet loss requirements, determined by the application(s). | Not Implemented |
| CMR-0018 See REQ-2017-0001R03 |
The oneM2M System shall be able to detect and report the missing data in time series, for each source of time sensitive data which is sent to the IoT platform. | Implemented in Rel-2 |
| CMR-0019 See REQ-2017-0001R03 |
The oneM2M System shall be able to detect and report the missing data in time series, for each time sensitive application receiving data. | Implemented in Rel-2 |
| CMR-0020 See REQ-2018-0001 |
The M2M System shall be able to distinguish between the raw dataflow and the configuration/control flow for the purpose of authentication (see note 3). |
NOTE 1: Long lived security context and registration is covered, M2M Sessions are not covered.
NOTE 2: CMDH policies (application side) is implemented, information from the Underlying Network can be utilized but the method for provisioning via Mcn is not covered.
NOTE 3: The configuration flow is the one used to set-up and configure the entity (e.g. node). The flows are distinguished from a logical point of view.