MCData Client Protocol Selection for Short Data Service
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing mission critical data (MCData) communication systems face challenges in efficiently managing short data service (SDS) communications due to inappropriate method selection by MCData clients, leading to additional latency and suboptimal performance.
Innovation Solution
A method and system for managing SDS communication in MCData systems, which involves determining pre-determined criteria for transmitting one-to-one or group standalone SDS messages, determining data size, and selecting the appropriate protocol (signaling control plane or media plane) based on the data size to optimize communication.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of time
If the originating MCData client does not select appropriate method, then additional latency is introduced due to extra round trips, but the system complexity increases due to need for protocol selection mechanisms
Solution Approach 1:
The patent applies preliminary action by having the MCData client pre-select the appropriate transport protocol (TCP or UDP) and method (SDP offer/answer or direct send) before initiating SDS message transmission. The client evaluates message characteristics (size, urgency, reliability requirements) and proactively chooses the optimal transmission path, avoiding latency caused by server rejections and retry mechanisms. This upfront decision-making eliminates unnecessary round trips while maintaining manageable system complexity through client-side intelligence.
2Reliability
If TCP protocol is used for SDS message transmission, then reliability is improved, but the transmission speed decreases due to connection establishment overhead
Solution Approach 1:
The patent implements dynamics by making the transport protocol selection adaptive rather than static. The MCData client dynamically chooses between TCP and UDP protocols based on real-time message characteristics: TCP is selected for messages requiring high reliability (larger messages, important operational data), while UDP is chosen for time-sensitive messages where speed is critical. This dynamic adaptation allows the system to optimize the reliability-speed trade-off for each individual message, preventing the always-use-TCP approach from unnecessarily slowing down urgent communications.
Solution Approach 2:
The patent applies parameter changes by modifying the transport layer parameters (protocol type, connection state) based on message parameters (size, priority, content type). The client adjusts transmission parameters such as whether to establish a TCP connection beforehand or use connectionless UDP, depending on the specific message requirements. This parameter-based adaptation enables the system to achieve high reliability when needed while maintaining high speed for urgent messages, resolving the contradiction between reliability and transmission speed.
3Speed
If UDP protocol is used for SDS message transmission, then transmission speed is improved, but reliability deteriorates due to lack of connection management
Solution Approach 1:
The patent uses the SDP (Session Description Protocol) mechanism as an intermediary to compensate for UDP's lack of connection management. When using UDP for fast transmission, the SDP offer/answer exchange serves as a preliminary coordination step that establishes transmission parameters and expectations. This intermediary mechanism provides a degree of reliability assurance without the full overhead of TCP connection management, allowing the system to achieve fast transmission speeds while maintaining adequate reliability through SDP-mediated coordination.
4Reliability
If SDP offer and answer exchange is performed before SDS message transmission, then compatibility and reliability are improved, but latency increases due to additional round trips
Solution Approach 1:
The patent applies preliminary action by performing the SDP offer/answer exchange in advance during session establishment, so that the transmission path and parameters are predetermined. Once the SDP handshake is complete, subsequent SDS messages can be transmitted directly without repeating the SDP exchange, eliminating setup latency for each individual message. This upfront preparation ensures compatibility and reliability while avoiding repeated round trips, as the communication channel is pre-configured and validated.
Solution Approach 2:
The patent implements periodic action by performing SDP offer/answer exchange only when necessary (e.g., when session parameters change, new participants join, or transmission conditions change), rather than before every single message. This periodic re-negotiation maintains compatibility and reliability when needed while minimizing latency by avoiding unnecessary SDP exchanges for routine message transmissions, thus resolving the contradiction between reliability and setup latency.
Data Source
AI summary
Embodiments herein provide a method for managing short data service (SDS) communication in a mission critical data (MCData) communication system. The method includes determining, by a transmitting MCData UE, whether a pre-determined criteria is met for transmitting a one-to-one standalone SDS message or a group standalone SDS message to receiving MCData UE (s). Further, the method includes determining data size of the one-to-one standalone SDS message or group standalone SDS message. Furthermore, the method includes transmitting the one-to-one standalone SDS message to the receiving MCData UE for one-to-one communication or group communication using one of a signaling control plane and a media plane based the determined data size of the one-to-one standalone SDS message or group standalone SDS message.