Overview

The capacity of the Internet to support smart-devices…making the Internet not just a repository for information or for human interactive functions, but allowing machines to communicate with each other for automated, pre-programmed or event-driven functions, has grown beyond any initial expectations. Lighting, HVAC, kitchen appliances, security cameras, automobiles and a multitude of other household and commercial systems together participate in a globally interconnected scheme of functionality. MAvMEC (Managed Activation via Media Embedded Commands) provides an on-ramp to this vast landscape allowing viewed media content to participate in ways yet to be imagined.

Work-FLow

IoT producer manually assigns events to control channels. For example with football, Touchdown on CH-1, Redzone on CH-2, Score turn-around on CH-3, Home team is leading on CH-4, Away team is leading on CH-5, Time-Out called on CH-6, etc. These can further be configured as steady-state or for momentary for each occurrence. The channel assignments are published as a standard or announced on a per-game basis and published on the League, Network or the www.iotpath.net website. Once the events are assigned to a channel by the IoT Producer, the system can take in either GPI, network based or manually entered commands to initiate the channel’s activity.

At the receiving end, the consumer or sports-bar can assign the channels to a variety of controlled devices. Initially, these commands would be extracted out of proprietary hardware units that would be configured by the user to control lighting systems, audio systems or visual display screens. As the system matures, the need for the proprietary hardware units would be eliminated as the functionality would become embedded as a feature in the actual Lighting, sound, or video equipment. Further integration would allow a MAvMEC bridge to interface with the end-user’s existing smart-device network to augment systems already under IoT control. Of Course, at any time, the end user can enable or disable the functions.

System Elements

• IoTPath Software operated by the IoT Producer used to define the event/action map and to enter live, real-time event triggers.
• Hardware Encoder to insert the command data generated by the IoTPath application.
• Hardware Decoder to accept the media signal and convert to command actions.
• Software user interface allowing end-user to accept/decline/redefine event trigger actions.

Examples

Examples area

Results

Results area