6.2 Management Requirements
Table 2: Management Requirements
| Requirement ID | Description | Release |
|---|---|---|
| MGR-001 | The oneM2M System shall be able to support management and configuration of M2M Gateways/ Devices including resource constrained M2M Devices. | Implemented in Rel-1 |
| MGR-002 | The oneM2M System shall provide the capability to discover the M2M Area Networks including information about devices on those networks and the parameters (e.g. topology, protocol) of those networks. | Implemented in Rel-1 |
| MGR-003 | The oneM2M System shall be able to provide the capability to maintain and describe the management Information Model of devices and parameters (e.g. topology, protocol) of M2M Area Networks. | Implemented in Rel-1 |
| MGR-004 | The oneM2M System shall support common means to manage devices enabled by different management technologies (e.g. OMA DM, BBF TR069). | Implemented in Rel-1 |
| MGR-005 | The oneM2M System shall provide the capability to manage multiple devices in a grouped manner. | Implemented in Rel-1 |
| MGR-006 | The oneM2M System shall provide the capability for provisioning and configuration of devices in M2M Area Networks. | Implemented in Rel-1 |
| MGR-007 | The oneM2M System shall provide the capability for monitoring and diagnostics of M2M Gateways/Devices in M2M Area Networks. | Implemented in Rel-1 |
| MGR-008 | The oneM2M System shall provide the capability for software management of devices in M2M Area Networks. | Implemented in Rel-1 |
| MGR-009 | The oneM2M System shall provide the capability for rebooting and/or resetting of M2M Gateways/Devices and other devices in M2M Area Networks. | Implemented in Rel-1 |
| MGR-010 | The oneM2M System shall provide the capability for authorizing devices to access M2M Area Networks. | Implemented in Rel-1 |
| MGR-011 | The oneM2M System shall provide the capability for modifying the topology of devices in M2M Area Networks, subject to restriction based on M2M Area Network policies. | Implemented in Rel-1 |
| MGR-012 | Upon detection of a new device the M2M Gateway shall be able to be provisioned by the M2M Service Infrastructure with an appropriate configuration which is required to handle the detected device. | Partially implemented (see note) |
| MGR-013 | Void. | |
| MGR-014 | The oneM2M System shall be able to retrieve events and information logged by M2M Gateways/ Devices and other devices in M2M Area Networks. | Implemented in Rel-1 |
| MGR-015 | The oneM2M System shall be able to support firmware management (e.g. update) of M2M Gateways/ Devices and other devices in M2M Area Networks. | Implemented in Rel-1 |
| MGR-016 | The oneM2M System shall be able to retrieve information related to the Static and Dynamic Device/Gateway Context for M2M Gateways/Devices as well as Device Context for other devices in M2M Area Networks. | Implemented in Rel-1 |
| MGR-017 | The oneM2M System shall be capable of correlating Access Management elements provided by the technology specific Device Management Protocols to Access Management elements used by the oneM2M System. | Implemented in Rel-1 |
| MGR-018 See REQ-2015-0555R02 |
The M2M Service Infrastructure shall be able to accept standardized configuration settings from an external configuration server to allow the M2M Devices to register. | Not implemented |
| MGR-019 See REQ-2015-0555R02 |
The M2M Device shall be able to accept standardized configuration settings from an external configuration server in order to register to the oneM2M System. | Not implemented |
NOTE: In Rel-1 no detection mechanism exists, but once an M2M Device is known at the Gateway it can be configured via the GW through DM.