MPRTP Header Extension Preservation and Security
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current Multipath Real-Time Transport Protocol (MPRTP) is incompatible with RTP header extensions not following RFC 5285, lacks mechanisms for applying encryption and authentication keys to MPRTP subflow packets, and does not provide a translator for RTP or Secure-Real Time Transport Protocol (SRTP) streams, leading to issues with header extension preservation and security across multiple delivery pathways.
Innovation Solution
The implementation of header extension preservation, security, and protocol translation for MPRTP, which allows the use of RTP headers not conforming to RFC 5285, applies the same encryption and authentication keys to all MPRTP subflow packets, and provides an MPRTP translator to preserve SRTP encryption and authentication, ensuring secure and reliable transmission across multiple pathways.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If MPRTP uses standard RTP header extensions following RFC 5285, then compatibility with existing RTP systems is improved, but flexibility to use custom header extensions is reduced
Solution Approach 1:
The patent introduces an MPRTP translator as an intermediary component that sits between non-compliant RTP sources and the MPRTP system. The translator intercepts RTP packets with non-RFC 5285 header extensions, strips or modifies these extensions, and forwards the cleaned packets into the MPRTP system. This mediator approach allows the system to accept flexible custom headers while maintaining internal compatibility standards.
Solution Approach 2:
The patent segments the RTP processing system into distinct functional components: an MPRTP translator layer that handles header normalization, an MPRTP core layer that processes standardized packets, and separate authentication/encryption layers. This segmentation allows each component to operate with its own header format requirements, enabling both flexibility at the edge and compatibility in the core.
2Reliability
If MPRTP applies separate encryption and authentication keys to each subflow packet, then security for individual pathways is improved, but complexity of key management increases
Solution Approach 1:
The patent merges the authentication and encryption key management across all MPRTP subflows by applying the same security context to multiple delivery pathways. Instead of maintaining separate key sets for each subflow, the system establishes a unified security context that is reused across all subflows, reducing key management complexity while maintaining security through the aggregation of multiple transport paths.
Solution Approach 2:
The patent creates a universal security context that serves multiple subflows simultaneously. The same authentication and encryption keys are designed to work across different delivery pathways, making the security mechanism multi-functional rather than path-specific. This universal approach simplifies key distribution and management while providing coordinated security across the entire MPRTP session.
3Reliability
If MPRTP translator preserves SRTP encryption and authentication, then security integrity is improved, but processing overhead increases
Solution Approach 1:
The patent applies authentication signatures and encryption preservation as preliminary actions during the MPRTP translation process. By establishing security contexts and applying authentication tags early in the translation pipeline, before packets are forwarded to their destination, the system ensures security integrity is maintained without requiring additional processing stages. The security processing is integrated into the initial translation operation rather than being a separate subsequent step.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Systems, methods, and devices of the various embodiments provide for header extension preservation, security, authentication, and/or protocol translation for Multipath Real-Time Transport Protocol (MPRTP). Various embodiments include methods that may be implemented in a processor of a computing device for MPRTP transmission of Real-Time Transport Protocol (RTP) packets. Various embodiments may include receiving an RTP packet in which the received RTP packet may be part of an RTP stream that may be protected using secure RTP (SRTP), and applying an authentication signature to the RTP packet to authenticate an MPRTP header extension separate from a body of the RTP packet. Various embodiments may include sending and/or receiving MPRTP subflows of an MPRTP session in which a same security context may be applied across all MPRTP subflows of the MPRTP session.