System Architecture and Terminology
The overall system architecture for the RoSE framework is depicted in the figure below and comprises Sensory Effect Metadata, Sensory Device Capabilities, Sensory Device Commands, User Sensory Preferences, and a so-called RoSE Engine which generates output data based on its input data. It is important to note that the Sensory Effect Metadata, Sensory Device Capabilities, Sensory Device Commands, and User Sensory Preferences are within the scope of standardization and, thus shall be normatively specified. On the other side, the RoSE Engine as well as Provider entities and Consumer Devices are informative and are left open for industry competition.
Provider: an entity that acts as the source of the Sensory Effect Metadata (e.g., broadcaster, …)
RoSE Engine: an entity that takes the Sensory Effect Metadata, the Sensory Device Capabilities and the User Sensory Preferences as inputs and generates Sensory Device Commands based those (e.g., a commercial product like the amBX engine).
Consumer Devices: entities that act as the sink of the Sensory Commands and act as the source of Sensory Device Capabilities. Additionally, entities that provide User Sensory Preferences are also referred to as Consumer Devices. Note: Sensory Devices are sub-set of Consumer Devices. Example: Fans, Lights, scent devices, human input devices such as a TV set with a remote control (for preferences).
Sensory Effect Metadata: it defines the description schemes and descriptors to represent Sensory Effects (e.g., XML schema, …).
Sensory Effect: a Sensory Effect is an effect to augment feeling by stimulating human sensory organs in a particular scene of a multimedia application (e.g., scent, wind, light, …).
Sensory Effect Delivery Format: a standard that defines means for transporting Sensory Effect Metadata. Note: This could be combined with the Audio/Video delivery format. Example: MPEG2-TS payload format, file format, RTP payload format, …
Sensory Device Capability: it defines the description schemes and descriptors to represent the characteristics of Sensory Devices (e.g., XML schema, ...).
Sensory Device: a Sensory Device is a device by which the corresponding Sensory Effect can be made (e.g., lights, fans, heater, fan, …).
Sensory Device Capability Delivery Format: a standard that defines means for transporting Sensory Device Capabilities (e.g., HTTP, UPnP, …).
Sensory Device Command: it defines the description schemes and descriptors to control Sensory Devices (e.g., XML schema, ...).
Sensory Device Command Delivery Format: a standard that defines means for transporting Sensory Device Commands (e.g., HTTP, UPnP, …).
User Sensory Preferences: it defines the description schemes and descriptors to represent user preferences with respect to rendering of Sensory Effects (e.g., XML schema, ...).
User Sensory Preferences Delivery Format: a standard that defines means for transporting User Sensory Preferences (e.g., HTTP, UPnP, …).
The current call focuses on Sensory Effect Metadata, Sensory Device Capabilities, Sensory Device Commands, and User Sensory Preferences.
RoSE Engine: an entity that takes the Sensory Effect Metadata, the Sensory Device Capabilities and the User Sensory Preferences as inputs and generates Sensory Device Commands based those (e.g., a commercial product like the amBX engine).
Consumer Devices: entities that act as the sink of the Sensory Commands and act as the source of Sensory Device Capabilities. Additionally, entities that provide User Sensory Preferences are also referred to as Consumer Devices. Note: Sensory Devices are sub-set of Consumer Devices. Example: Fans, Lights, scent devices, human input devices such as a TV set with a remote control (for preferences).
Sensory Effect Metadata: it defines the description schemes and descriptors to represent Sensory Effects (e.g., XML schema, …).
Sensory Effect: a Sensory Effect is an effect to augment feeling by stimulating human sensory organs in a particular scene of a multimedia application (e.g., scent, wind, light, …).
Sensory Effect Delivery Format: a standard that defines means for transporting Sensory Effect Metadata. Note: This could be combined with the Audio/Video delivery format. Example: MPEG2-TS payload format, file format, RTP payload format, …
Sensory Device Capability: it defines the description schemes and descriptors to represent the characteristics of Sensory Devices (e.g., XML schema, ...).
Sensory Device: a Sensory Device is a device by which the corresponding Sensory Effect can be made (e.g., lights, fans, heater, fan, …).
Sensory Device Capability Delivery Format: a standard that defines means for transporting Sensory Device Capabilities (e.g., HTTP, UPnP, …).
Sensory Device Command: it defines the description schemes and descriptors to control Sensory Devices (e.g., XML schema, ...).
Sensory Device Command Delivery Format: a standard that defines means for transporting Sensory Device Commands (e.g., HTTP, UPnP, …).
User Sensory Preferences: it defines the description schemes and descriptors to represent user preferences with respect to rendering of Sensory Effects (e.g., XML schema, ...).
User Sensory Preferences Delivery Format: a standard that defines means for transporting User Sensory Preferences (e.g., HTTP, UPnP, …).
The current call focuses on Sensory Effect Metadata, Sensory Device Capabilities, Sensory Device Commands, and User Sensory Preferences.
No comments:
Post a Comment