IP Manager application manages user input via IP remote. The purpose of IP Remote Control is to allow managed gateways and clients to be controlled via a wired or wireless internet protocol connection.

High end 3rd party remote control systems need to connect to set top boxes (STBs). In order to do that, the STBs need to allow generalized key commands enter the RDK via IP over MoCA, then convert those commands into IR commands, sending them along to the IR manager as if they were coming from the IR remote.

The IP Remote Control allows programmable controllers with an IP interface to control devices.

Here's an overview of the major components involved:

This shows:

  1. A vendor normally provides an IP remote control or application for a device.
  2. The vendor also provides a device, sometimes called a NUK, that the remote or application communicate with using IP protocol.
  3. The nook connects to devices it controls using IP. In this case, one of those devices would be a set-top box (STB).
  4. The user of the remote or app triggers commands. Those commands transmit as codes over the IP connection all the way to a receiving application on the STB.
  5. The STB maps the code to RF4CE commands. Those commands route to the application as if they were normal RF remote control commands.
  • No labels