T1 E1 Receive Multiframe Streaming Over UDP
UDP Multiframe Streaming Architecture simplifies access to T1 E1 data by streaming it as UDP packets, allowing client applications to easily receive and reconstruct the original data.
Request a Demo / Quote BrochureOverview
The T1 E1 Receive Multiframe Streaming Over UDP solution provides a robust and cost-effective architecture for processing T1 E1 data using UDP Multiframe Streaming (UMS). Designed for both hardware-based and software-based systems, this solution supports flexible data streaming configurations, enabling simplified application development across multiple programming languages. It is ideal for high-performance data capture, processing, and analysis.
As an alternative to GL’s API, the UDP multiframe streaming architecture extends access to raw data on GL’s T1 E1 interface, with the UDP server converting T1 E1 data streams into UDP datagrams and streaming them to a specified port. Client applications on the receiving end can listen to the streams and convert the packets back to T1 E1 frames. Updates to the Error Insertion Application ensure consistent operation in the following scenarios: Cross-port Tx (Framed), Cross-port Normal (Framed), Cross-port Tx (Unframed), and Cross-port Normal (Unframed).
UMS operates seamlessly with both hardware-based T1 E1 solutions using GL cards and software-based T1 E1 solutions like the T1 E1, T3 E3 Analyzer. The T1 E1 GlComInterface (GCI) library supports streaming received multiframes over UDP in three modes:
- Data Only: Sends data for each T1 E1 channel to a separate UDP port
- Headers and Data: Streams one T1 E1 multiframe per UDP datagram, either to a single or multiple UDP ports
- Optimized Buffered Data: Sends multiple multiframes with headers in a single UDP datagram to the same client UDP port
Data structures use Intel byte order (least significant byte first). For T1 ESF, E1 CCS, and E1 CAS, data is sent multiframe-aligned if synchronization is achieved on the T1 E1 line.
When headers are included, they provide critical information such as:
- High-speed port number
- Low-speed (T1 E1) channel number
- Bytes preceding the multiframe to detect data loss
In cases where multiframe alignment is achieved, data is sent on multiframe boundaries; otherwise, unaligned octets equivalent to the multiframe size are transmitted.
Key Features
- Data-only streaming to multiple UDP endpoints
- Header and data streaming to one or more UDP endpoints
- Optimized buffered streaming with multiple headers and multiframes in a single UDP datagram
- Handles T1 E1 data reception and UDP packet transmission via an INI file-controlled server
- Supports high-speed configuration
- INI file supports T1 E1 port settings, clock settings, framing options, loopback modes, and termination modes
- Allows setup of UDP destination IP addresses and ports
- Includes parameters like port numbers, channel indices, byte counts, timing data, and alarm indicators
- Ensures precise multiframe alignment during data transmission
- Works with various programming languages, simplifying client application development
- Includes a sample C++ client for quick integration
- Features intuitive options to Start, Stop, Save, Load, and Default configurations
- Allows easy setup of T1 E1 port settings, headers, and destination parameters
- Supports efficient data transmission using Intel byte order
- Optimized for high-speed GL T1 E1 Analyzer, with support for single-mode and multi-mode optical interfaces
- Enables real-time testing, monitoring, and analysis of T1 E1 data streams
- Ideal for high-performance data capture and transmission
UDP Message Structure
There are three possible ways to organize multiframes in a UDP datagram:
- One MF per UDP Datagram, with only MF data (no header)
- One MF per UDP Datagram, with both header and MF data
- Sequence of multiple MF headers/data per UDP Datagram: HDR1, MF1, HDR2, MF2, filling the entire datagram
Streaming Multiframe Data Only
The application streams one multiframe per UDP datagram to multiple client UDP endpoints (address/port), allowing the UDP ports to be shared by multiple applications. Each UDP datagram contains a sequential block of multiframe data octets with no additional structure. For T1 systems, the datagrams are 576 bytes long, each containing 24 ESF frames. For E1 systems with CCS or CAS, the datagrams are 512 bytes long and include 16 E1 frames. In the case of unframed E1, the datagrams consist of 512 bytes of unaligned data.

Sending Data only to Multiple UDP Endpoints
Streaming One Header and Multiframe per UDP
The application streams both data and headers, with each UDP datagram containing one header and one multiframe. This data can be sent to a single client application on a specific UDP endpoint (address/port) or to multiple UDP endpoints. The header within each UDP datagram provides additional information, including physical-level alarm details, timing data, flags, and other critical metadata. This capability ensures efficient communication and enhances data interpretation for client applications.

Streaming Headers and MF Data to Single UDP one MF per UDP Datagram
The application supports streaming headers and data to multiple UDP endpoints, with each UDP datagram containing a header and a single multiframe of data. The header includes essential metadata such as physical-level alarm information, timing details, and flags, ensuring comprehensive and accurate data delivery to client applications.

Streaming Header and Data, one MF per DG to multiple UDP Endpoints
Streaming Multiple Header/Multiframe Data Pairs per UDP
In this configuration UDP is used in optimal way. The performance may improve depending on your network setup. The difference of the buffer UDP datagrams is that they can contain sequence of up to 64k header/data pairs filling the entire UDP Datagram. All UDP traffic is sent to a single UDP port.

Streaming Multiple Header/MF Data per UDP DG to Single UDP Endpoint
UDP Streaming Server of T1 E1 Received Multiframes
The UDP streaming server simplifies the development of applications that process received T1 E1 data in various programming languages. GL’s T1 E1 configuration and data reception are managed by the receive server, which is controlled through an INI file. The application must configure the INI file to set up T1 E1 in the appropriate mode and specify the destination for transmitting UDP packets containing T1 or E1 multiframes. Once configured, the application simply receives UDP datagrams with T1 E1 multiframes.
For high-speed GL cards, such as the T1 E1, an additional high-speed configuration file-driven server application is available, also controlled via a configuration file.

T1 E1 Streaming Server
Receive Multiframe Streaming Over UDP Interface
The "Receive Multiframe Streaming Over UDP" application designed to configure and manage T1 E1 data streaming over UDP. It offers options to select T1 E1 ports, define header fields, and set destination UDP address and port details. The interface also includes options to specify header configurations such as sending time, alarm information, and data grouping preferences (e.g., one multiframe or multiple multiframes per UDP datagram).
Displays real-time statistics for selected T1 E1 ports, including the number of received bytes, skipped bytes, and UDP port configurations. Control buttons such as Start, Stop, Load, Save, Default, and Exit provide an easy way to manage the streaming session and configurations. This tool is ideal for real-time monitoring and streaming of T1 E1 multiframes to specified UDP endpoints.

Receive Multiframe Streaming Over UDP User Interface
Resources
Item | Description |
---|---|
XX672 | T1 E1 Recieve Superframe/Multiframe Streaming Over UDP |
Item | Related Hardware |
PTE001 | tProbe™ Dual T1 E1 Laptop Analyzer |
FTE001 | QuadXpress T1 E1 Main Board (Quad Port) |
ETE001 | OctalXpress T1 E1 Daughter boards (Octal Port) |
XTE001 | Dual Express (PCIe) T1 E1 Boards |
TTE001 | tScan16™ T1 E1 Boards |