XMPP Message Distribution Network Protocol

When a user interacts with the Players of a Digital Signage Display rollout from the CMS module (or MCP content manager), it generates messages (commands) that must reach efficiently all the Players to be processed.

Some examples of these messages can be "playback order of a channel", "updating the contents of a basket" (playlist), or a "new programming to update the scheduler", etc...

Once these messages have been received and processed, Players must report back to CMS the accurate current status of the processed actions.

Both types of command traffic (CMS-> Players and Players-> CMS) actually pass through the distribution system to reach its destination efficiently.

MCP uses a XMPP network (Extensible Messaging and Presence Protocol) for sending these messages. XMPP network allows Player visibility over routers, proxies, gateways and other intermediate network systems, which often obscure the trace routes to a host (in our case a Player)

The connections to the XMPP network may be encrypted using TCP + SSL using certificates to authenticate clients and servers if necessary. May accompany the authentication against the XMPP server with challenges based on USB tokens, username and password pairs or other similar security elements.

XMPP networks may consist of multiple federated servers, ensuring that you always have a high-availability and highly scalable message transport network.

Other communication solutions based on XMPP, as GoogleTalk, have already demonstrated the efficiency of this technology, which allows fully routable million nodes for sending and receiving messages.

The XMPP messaging distribution network together with the P2P file sharing system, ensure that your MCP Digital Signage channels will be Ultra-scalable.

Other MCP Features: