RTP - Real-Time Transport Protocol
Our RTP is designed to provide fully re-entrant modules to allow multiple RTP streams to be processed concurrently.
FEATURES
- Functions are C-callable.
- Multi-channel capable.
- Support of RTP version 2 protocol as defined in RFC 3550
- Independence from underlying protocol stack.
- Minimum count of consecutively increasing sequence numbers prior to playout.
- Built in jitter buffer
- Secure variants include support for:
Authentication Types: HMAC-SHA and MD5 | Key Definition Schemes: PSK, MKI, and FT
Encryption types: CM, F8 - Automatic timestamp synchronization.
- Multiple independent RTP streams
- Re-entrant routines callable by multiple processing threads
AVAILABILITY
ADT RTP is available off the shelf on the following Platforms: Other configurations are available upon request.
| Platform |
|---|
| ARMv7 Cortex-A8 / A9 / A12 / A15 / A17 |
| ARMv7 Cortex-M3 / M4 / M7 |
| ARMv8 Cortex-A53 / A57 |
| ARM9e |
| ARM11 |
DESCRIPTION
Adaptive Digital Technologies’ Real Time Protocol (RTP) software provides transport layer functionality for real-time applications communicating over an IP network. This product also contains a built in, configurable, jitter buffer to compensate for network delays, out-of-order packets, and lost packets.
Adaptive Digital’s implementation of the RTP protocol is designed to provide fully re-entrant modules to allow multiple RTP streams to be processed concurrently. User supplied callback and support routines are used to allow the RTP software to be easily adapted to the application environment. Memory allocation for the packets stored within the jitter buffer is dynamic and is accomplished via a call to a user definable memory allocation support routine. To allow flexibility in interfacing with differing network stack mechanisms, the mechanism to send data over the network is accomplished via a user definable callback routine.
The built-in jitter buffer provides a storage mechanism for inbound packets. The RTP module stores incoming packets into the jitter buffer at the time of reception. The jitter buffer uses the RTP header timestamp and sequence number to position out-of-order packets correctly within the jitter buffer. Packets remain stored in the jitter buffer until they are ready for delivery to the receiving application.
For complete information about RTP Protocol see http://www.adaptivedigital.com/product/protocol_stacks/rtp.htm
SPECIFICATIONS
ARM® DEVICESRTP ARM Cortex-A8/A9/A15
CPU UTILIZATION & MEMORY REQUIREMENTS
All Memory usage is given in units of byte.
| Direction | MIPS | Program Memory | Data Memory |
|---|---|---|---|
| Tx | .20 | 8.6K | 172 |
| Rx | .20 |
RTP ARMv7M Cortex-M3/4
MEMORY REQUIREMENTS
All Memory usage is given in units of byte.
| Direction | Program Memory | Data Memory | Instance Data Memory |
|---|---|---|---|
| RTP | 6.4 K | 108 | 200 |
| RTP + RTCP | 15.7 K | 124 | 660 |
CPU UTILIZATION
| RTP Function10 msec | Average MIPS* | ||
|---|---|---|---|
| 10 msec | 20 msec | 30 msec | |
| Tx | 0.13 | 0.08 | 0.06 |
| Rx | 0.22 | 0.12 | .09 |
*Actual MIPS will vary dependent upon: packet size, frame rate, and application supplied callback routines.
RTP ARM9E / ARM11
CPU UTILIZATION & MEMORY REQUIREMENTS
All Memory usage is given in units of byte.
| Direction | MIPS | Program Memory | Data Memory |
|---|---|---|---|
| Tx | .20 | 8.6K | 172 |
| Rx | .10 |