4. ICT devices like phones, tablets, laptops and other mobile devices
5. Office equipment like printers and meeting systems
#### 4.2.2 Controller design
The product is a network controller.
@@ -2770,9 +2768,19 @@ This document is not perfect.
## Notes on 4.1.4 ICT device management
The chapter [4.1.4 ICT device management](#414-ict-device-management) does not have a use-case included.
ICT device management use-case highlights how there are multiple controlling entities involved in a device manamagement.
The ownership of those changes is partial and the product usability and the experience what the user ends up having, is sum of all parts.
Analogy could be made to game modding, or software plugin development.
The core is stable, but the extension crashes the system.
This document lacks a clear ownership separation and expectation setting how NMS should aknowledge the existense of other controllers.
Ownership transfer is undefined.
Stacking multiple controlling entities into a device is an operative environment design choice, but does this make the device issuing enterprise the integrator?
How much of the original manufacturer responsibility of providing updates is inherited?
How this settles in with the expected use of the product?
The following work could be a direction worth exploring:
In the greater scheme of device management, the following work could be a direction worth exploring:
* The Open Mobile Alliance (OMA) Device Management protocol [OMADM] and LightweightM2M architecture [LWM2M]
* BroadBand Forum (BBF) CPE WAN Management protocol [TR-069] developed extensive specifications to facilitate Device Management over wireless and wireline telecommunication network respectively
