Embedding MQTT messages in media streams
This disclosure provides embedding a messaging channel directly into a media stream, where messages delivered via the embedded messaging channel are the extracted at a client media player. An advantage of embedding a message is that it can be done in a single ingest point and then passes transparently through a CDN architecture, effectively achieving message replication using the native CDN media delivery infrastructure.
1. An information delivery system, comprising:
a message broker executed in first hardware and including an application programming interface (API) configured to:
receive information that specifies a locator associated with a media stream, and a message conforming to a message transport protocol, wherein the message transport protocol is MQ Telemetry Transport (MQTT); and
selectively forward the message for embedding into the media stream;
an ingest component executed in second hardware and including software configured to:
receive the media stream for delivery via Hypertext Transfer Protocol (HTTP) over Transmission Control Protocol (TCP);
receive the message forwarded by the message broker; and
embed the message into the media stream; and
an edge server executing in third hardware and including additional software configured to:
receive the media stream having the message embedded therein; and
responsive to receipt of a request from a client, the request being associated with the locator, deliver the media stream with the message embedded therein to the client.
2. The information delivery system as described in claim 1 wherein the message conforming to the message transport protocol has a quality of service (QoS) attribute.
3. The information delivery system as described in claim 2 wherein the QoS attribute is a QoS0 (at most once) attribute, thereby avoiding unintended latency for the media stream.
4. The information delivery system as described in claim 1 wherein the media stream is pushed to the edge server from the ingest component.
5. The information delivery system as described in claim 4 wherein a second request from the client pulls the media stream from the edge server.
6. The information delivery system as described in claim 1 wherein the message is embedded into the media stream in association with a timestamp that identifies a given time when the message is to be displayed or processed at the client.
7. The information delivery system as described in claim 1 wherein the message is associated with a messaging topic specified in the information received at the message broker.
8. The information delivery system as described in claim 1 wherein the media stream is delivered via chunked transfer encoding and the message is an MQTT quality of service at most once (QoS0) message.
9. The information delivery system as described in claim 1 further including an MQTT client executing on the client.
10. The information delivery system as described in claim 9 wherein the MQTT client is configured to extract the message and cause it to be rendered at a given time in timed synchronization with a portion of the media stream based on a timestamp associated with the message.
11. The information delivery system as described in claim 10 wherein the timestamp is specified in the information received by the message broker.
12. The information delivery system as described in claim 1 wherein the media stream is a continuous media packaged according to a Common Media Application Format (CMAF).
13. The information delivery system as described in claim 1 wherein the edge server is further configured to return an MQTT message to the message broker.
14. The information delivery system as described in claim 1 wherein the media stream is a live stream, and wherein the ingest component receives the media stream substantially in real-time as the media stream is published.
15. The information delivery system as described in claim 14 wherein the message is received from the message broker and embedded into the live stream substantially in real-time.