See Online documentation.
Media Communications Mesh, or MCM, is a distributed network framework designed for real-time transmission of multimedia data, such as video, audio, or ancillary over managed IP networks. It leverages the Media Transport Library that implements SMPTE ST 2110 Suite of Standards transmission protocols to ensure professional-grade media streaming, commonly used in broadcast and production environments. MCM integrates data and control planes to efficiently manage media traffic and network topology, providing developers with an SDK for creating connections to send and receive media streams. It supports advanced features like multipoint groups for scalable distribution and bridges for compatibility with external networks, aiming to enhance performance and reduce latency in media transfers.
Consider the following environment as a simple example of a live video broadcast scenario, e.g. a sports event live stream
graph TB
cam1([Video Camera
CAM1])
net <===>|Video ST 2110-20
239.192.0.1
+
Audio ST 2110-30
239.192.0.2| cam1
cam2([Video Camera
CAM2])
net <===>|Video ST 2110-20
239.192.0.3
+
Audio ST 2110-30
239.192.0.4| cam2
mon1([Programme Monitor])
net <===>|Video ST 2110-22
239.192.5.1
+
Audio ST 2110-30
239.192.5.2| mon1
mon2([Replay Monitor])
net <===>|Video ST 2110-22
239.192.5.3| mon2
subgraph net [Network]
direction TB
switch1(". . .")
switch2(100 Gbit/s Multicast Network Switch)
switch3(". . .")
switch4(100 Gbit/s Multicast Network Switch)
switch5(". . .")
switch6(100 Gbit/s Multicast Network Switch)
switch7(". . .")
end
subgraph control-node [Control Plane Node]
agent(Mesh Agent)
end
subgraph node1 [Worker Node 1]
direction TB
subgraph node1.proxy [Media Proxy]
node1.proxy.group1(Multipoint
Group
239.192.0.1)
node1.proxy.group2(Multipoint
Group
239.192.0.3)
node1.proxy.group3(Multipoint
Group
239.192.5.1)
node1.proxy.group4(Multipoint
Group
239.192.0.2)
node1.proxy.group5(Multipoint
Group
239.192.0.4)
node1.proxy.group6(Multipoint
Group
239.192.5.2)
end
subgraph app-A [Microservice A]
app-A.proc(Multiviewer Pipeline)
app-A.proc <==> app-A.data
app-A.proc <==> app-A2.data
app-A.proc <==> app-A3.data
app-A.data([Video
Stream
CAM1])
app-A.sdk((SDK))
app-A.data <==>|Input| app-A.sdk
app-A2.data([Video
Stream
CAM2])
app-A2.sdk((SDK))
app-A2.data <==>|Input| app-A2.sdk
app-A3.data([Video
Stream
Multiviewer])
app-A3.sdk((SDK))
app-A3.data <==>|Output| app-A3.sdk
end
app-A.sdk <==> node1.proxy.group1
app-A2.sdk <==> node1.proxy.group2
app-A3.sdk <==> node1.proxy.group3
subgraph app-B [Microservice B]
app-B.proc(Audio Mixer Pipeline)
app-B.proc <==> app-B.data
app-B.proc <==> app-B2.data
app-B.proc <==> app-B3.data
app-B.data([Audio
Stream
CAM1])
app-B.sdk((SDK))
app-B.data <==>|Input| app-B.sdk
app-B2.data([Audio
Stream
CAM2])
app-B2.sdk((SDK))
app-B2.data <==>|Input| app-B2.sdk
app-B3.data([Mixed
Audio
Stream])
app-B3.sdk((SDK))
app-B3.data <==>|Output| app-B3.sdk
end
app-B.sdk <==> node1.proxy.group4
app-B2.sdk <==> node1.proxy.group5
app-B3.sdk <==> node1.proxy.group6
end
subgraph node2 [Worker Node 2]
direction TB
subgraph node2.proxy [Media Proxy]
node2.proxy.group1(Multipoint
Group
239.192.0.1)
node2.proxy.group2(Multipoint
Group
239.192.0.3)
node2.proxy.group3(Multipoint
Group
239.192.5.3)
end
subgraph app-C [Microservice C]
app-C.proc(Video Recorder)
app-C.proc <==> app-C.data
app-C.proc <==> app-C2.data
app-C.data([Video
Stream
CAM1])
app-C.sdk((SDK))
app-C.data <==>|Input| app-C.sdk
app-C2.data([Video
Stream
CAM2])
app-C2.sdk((SDK))
app-C2.data <==>|Input| app-C2.sdk
end
app-C.sdk <==> node2.proxy.group1
app-C2.sdk <==> node2.proxy.group2
subgraph app-D [Microservice D]
app-D.proc(Video Replay)
app-D.proc <==> app-D.data
app-D.data([Video
Stream])
app-D.sdk((SDK))
app-D.data <==>|Output| app-D.sdk
end
app-D.sdk <==> node2.proxy.group3
end
node1 <===>|Control Plane + Data Plane| net
node2 <===>|Control Plane + Data Plane| net
net <--->|Control Plane| agent
The above diagram shows the topology established in the Mesh cluster according to the configuration requested by microservices that use SDK API.
In that diagram there are
- 2x video cameras supporting SMPTE ST 2110
- CAM 1
- CAM 2
- 2x video monitors supporting SMPTE ST 2110
- Programme monitor
- Replay monitor
- Media Communications Mesh cluster
- Control plane node
- Mesh Agent
- Worker Node 1
- Microservice A – Multiviewer pipeline
- Microservice B – Audio mixer pipeline
- Worker Node 2
- Microservice C – Video recorder
- Microservice D – Video replay
- Control plane node
- Network multicast switch based infrastructure
- Media Stream – Continuous flow of multimedia data, such as video, audio, or ancillary, that is transmitted over the network.
- SMPTE ST 2110 – Suite of standards developed by the Society of Motion Picture and Television Engineers (SMPTE) for professional media streaming over managed IP networks. It is designed to facilitate the transport of video, audio, and ancillary data in real-time formats, which is widely used in broadcast and production environments. See the SMPTE ST 2110 documentation.
- Mesh – Media Communications Mesh, a distributed multi-node network framework for transmitting media streams in real-time.
- Data Plane – Layer of functions responsible for the transmission of media data through the Mesh.
- Control Plane – Layer of functions responsible for managing and configuring the Mesh topology, components, and media traffic.
- Client – SDK API structure handling resource allocation flow in the Mesh. Once initialized, the client allows creating connections to the Mesh.
- Connection – SDK API structure handling data plane communication with the Mesh. An established connection allows sending or receiving media stream traffic in buffers.
- Tx connection – Sender mode connection to the Mesh.
- Rx connection – Receiver mode connection to the Mesh.
- Buffer – SDK API structure for handling a single piece of data transfered in a media stream. Buffers carry payload and metadata.
- Payload – Single piece of media stream data, e.g. a video frame, an audio packet, or blob data.
- Metadata – Arbitrary user metadata that can be carried in every buffer in an active connection.
- Multicast Group – Network switch configuration for a set of nodes or devices that are interested in receiving a specific stream of multicast data.
- Multipoint Group – Scalable distributed mechanism for sending media traffic within the Mesh to multiple receivers running on multiple nodes leveraging
the zero-copy mechanism to reduce latency. A multipoint group can have one sender and multiple receivers.
- One sender – a Tx connection or an ingress bridge.
- Multiple receivers – Rx connections or egress bridges.
- Bridge – Mesh software entity that handles import or export of media traffic between the Mesh and the external network.
- Ingress Bridge – Bridge that receives media stream data from an SMPTE ST 2110 or RDMA connection and sends it to a multipoint group.
- Egress Bridge – Bridge that receives media stream data from a multipoint group and sends it to an SMPTE ST 2110 or RDMA connection.
- NIC – Network interface card, e.g. Intel® Ethernet Controller E810-C.
- DPDK – Data Plane Development Kit, a set of libraries and drivers designed to accelerate packet processing workloads running on general-purpose CPUs. See the DPDK documentation.
- MTL – Media Transport Library, a DPDK-based library providing support for SMPTE ST 2110 media transport protocols. See the MTL documentation.
Latest release: 25.03
- SDK API modes of operation
- Receiver mode – Rx connection to Mesh.
- Sender mode – Tx connection to Mesh.
- Rx/Tx connection types
- SMPTE ST 2110
- SMPTE ST 2110-20 Uncompressed Video
- SMPTE ST 2110-22 Compressed Video (JPEG XS)
- SMPTE ST 2110-30 Uncompressed Audio (PCM)
- Multipoint Group
- Supports attaching user metadata to every buffer in Mesh.
- SMPTE ST 2110
- Payload types
- Video
- Resolution up to FullHD 1920 x 1080
- Frame rate up to 60 FPS
- Audio
- Channels
- 1, 2, 4, etc.
- Formats
- PCM 16-bit
- PCM 24-bit
- Sample rates
- 48000 Hz
- 96000 Hz
- Channels
- Blob
- Supported in SDK only.
- Not supported in the FFmpeg plugin.
- Video
- Payload types
- Video
- Resolution up to 4K 4096 x 2160.
- Audio
- Sample rates
- 44100 Hz
- Sample rates
- Video
- SDK – Software Development Kit in the form of a library providing SDK API to access Media Communications Mesh.
- Library file name:
libmcm_dp.so - Header file to include:
mesh_dp.h - SDK overview
- SDK API description
- Code examples
- Library file name:
- Media Proxy – Core data plane transmission handling component running on every node in the Mesh. SDK API establishes connections with Media Proxy to send and receive media streams.
- Supported streaming options
- SMPTE ST 2110-20 Uncompressed Video
- SMPTE ST 2110-22 Compressed Video (JPEG XS)
- SMPTE ST 2110-30 Uncompressed Audio (PCM)
- RDMA for inter-node communication
- Executable file name:
media_proxy - For command line arguments, see the Media Proxy documentation.
- Supported streaming options
- Mesh Agent – Control plane component responsible for establishing appropriate traffic topology in the Mesh according to user app requests. It handles the life cycle of connections and multipoint groups, configures egress and ingress bridges of SMPTE ST 2110 and RDMA types, and collects Media Proxy metrics.
- Executable file name:
mesh-agent - For command line arguments, see the MeshAgent documentation.
- Executable file name:
- FFmpeg MCM Plugin – Device plugin for FFmpeg utilizing SDK API to create connections to the Mesh and send or receive media streams.
- Supports video and audio streams.
- Allows multiple Mesh connections running in the same FFmpeg instance.
- For command line arguments, see the FFmpeg MCM Plugin documentation.
Follow the Setup Guide to navigate through the setup, build, and install process.
For guidance on running Media Communication Mesh, see Runbook.
See Performance Notes to learn how to tune the connection configuration for the best performance.
-
There is a bug with the default docker.io package installation (version 20.10.25-0ubuntu1~22.04.2) with Ubuntu 22.04.3 LTS. The
USERcommand andchowncommand do not work as expected. It is preferred to install thedocker-cepackage, following an instruction from Docker Docs. -
The Authentication function of the Media Proxy interfaces is under development.
If you encounter any issues or need assistance, there are several ways to seek support
- Update NIC firmware and drivers – Check for your NIC firmware and/or drivers update: Intel® Ethernet Linux Driver Repositories.
- Project documents – Search for solutions in the Project documents.
- Discussions – Ask questions and seek help in the Discussions section on the project's GitHub page.
- Report an issue – Report bugs and specific issues by submitting them on the Issues page of the project's GitHub repository. Before submitting an issue, please check the existing documentation and discussions to avoid duplication and streamline the support process.
We are here to help, so do not hesitate to reach out to us if you need assistance.
![@dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=64&v=4){kind=small}
