The DeviceMode sets the context of the service for which the engaged Example devices and the service stack modules purport to operate.

Primarily, it reflects what kind of situation the Example system is designed for. The DeviceMode may be set by the service provider who then assembles useful Example devices and a suite of service stack apps calibrated to perform what needs to be done to serve the set mode. Or it may be set by the end user from a mobile app which gained legitimate access to both the sensor network and the service layer software stack.

Once the DeviceMode is set, it propagates through the service stack, filters relevant Example devices by querying their CaptureMode and DeviceMode compatibility matrix. Either the A.I. or human admin may finalize on their configurations, assign more detailed DeviceMode to each device according to its capability, location, etc. For Example devices which are designed completely agnostic of any notion of DeviceMode, they will go through more rigorous queries by the service stack, checking their attributes and functionalities to determine compatibility.

The DeviceMode also controls the broad behavior of the service analytics stack as well as how it processes and archives the data stream. It is also plausible that dedicated end-user app ecosystem grows around some popular DeviceModes. The DeviceMark manager creates a DeviceMark using a set of Device-defining criteria as dictated by the set DeviceMode, and when a DeviceMark is generated it records under what DeviceMode it is created. Therefore, even if their overall data structure remains the same, the way DeviceMarks are presented and consumed in the end-user App may be dramatically different.