Organisation internationale de normalisation

Text copied from the last version of the report in order to guideline the work on MIoT:

MIoT should expose timing information MIoT should expose location information (from the use case of fire surveillance system) MIoT should be able to implement specific image processing algorithms and provides codes with respect to a detected situation Defined some classes for image processing IoTs that we care about video camera microphone display (visual, auditory, olfactory, haptic) media storage media analyzers MIoT camera Sensing MPEG-V camera sensor (5 types already defined: color, depth, stereoscopic, thermo, spectrum) Some local Processing and support from a processing unit Compression (MPEG-4 video) Feature extraction and their transmission Face feature extraction (MPEG-7) Gesture recognition (MPEG-U ++) Feature extraction for arbitrary textures (CDVS) Color, shape, contour, texture pattern, motion trajectory, … (MPEG-7) Fire Full processing Send compact commands to outside, depending on the application; some commands can be standardized Sensors & Actuators may become Engines (Active components, xxx) (we should add APIs on top of MPEG-V s&a), therefore, they become IoTs. Some of them are MIoTs. We can add some processing capabilities for some of them, from low processing (sampling, compression, ..) to high processing (interpretation, analysis, …). We can also build aggregates of MIoTs and IoTs and wearable are an example of these aggregates. Alternatives MIoT as a new part in MPEG-V containing the APIs Not so appropriate for MIoTs that don't have sensing or actuating (like media analyzers or media storage) MIoT like MPEG-M engines Not so appropriate because the MPEG-M engines are usually complex A new project One layer contains individual MIoTs A second layer aggregates individual MIoTs, eventually with other IoTs A particular class of this layer is the wearable Another class is the large scale systems (e.g. multi-cam surveillance systems)

• 
  Output documents:
  

• 
  Overview, context and objectives of Media-centric IoTs and Wearables (Marius) 3w
  
• 
  Conceptual model, architecture and use cases for Media-centric IoTs and Wearables (Mihai and Sang) 3w
  
• 
  Draft requirements for Media-centric IoTs and Wearables (Sang and Mihai) 3w
  
  • 
    E.g. Category MIoT Camera
    
  • 
    E.g. Category glasses
    
  • 
    …
    

• 
  M-IoTW Ahg Mandate
  
  • 
    Improve and clarify the area of M-IoTW
    
  • 
    Identify and document additional use cases for M-IoTW
    
  • 
    Refine requirements for M-IoTW
    
  • 
    Prepare material for CfP (e.g. scope, evaluation criteria, data set)
    
  • 
    Investigate IoT Architectures for specific domains and how MIoTW will interwork with them
    
  • 
    Identify the list of MPEG technologies related to M-IoTW
    
  • 
    Identify key organizations in IoT and Wearables and the status of their work
    
  • 
    Analyse the Working Draft of Information technology— Internet of Things Reference Architecture (IoT RA) and submit initial comments for their next meeting
    

1.