Dynamic Data Relaying Service for IoT Devices
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current 3GPP Proximity Services (ProSe) framework for device-to-device relaying is burdensome and not well-suited for dynamic communications involving small data transmissions, requiring high overhead and persistent pairing, which is inefficient for applications like IoT devices with varying link quality.
Innovation Solution
A dynamic data relaying service that dynamically pairs remote and relay devices on a per-packet basis, using peer-to-peer authentication and low overhead procedures, allowing devices to negotiate relaying without server involvement, and using existing Layer 2 UE-to-network relay architecture for efficient data forwarding.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If current 3GPP ProSe framework is used for device-to-device relaying, then device pairing and authentication can be established, but high overhead and persistent pairing requirements make it burdensome and inefficient for dynamic communications with small data transmissions
Solution Approach 1:
The patent segments the relaying procedure into distinct phases: a lightweight discovery phase where devices advertise and discover relaying capabilities, and a data transmission phase where actual relaying occurs. This segmentation eliminates the need for persistent pairing by separating the authentication overhead from the data transmission process, allowing devices to engage in rapid, dynamic relaying without maintaining continuous paired connections.
Solution Approach 2:
The patent implements dynamic relaying where devices can transition between direct communication and relayed communication modes based on real-time link quality conditions. The system dynamically selects whether to use direct device-to-device links or relay through intermediate devices, adapting to changing network conditions without requiring re-pairing or complex protocol negotiations, thus reducing overhead while maintaining reliability.
2Reliability
If persistent pairing is required for device-to-device relaying, then authentication is ensured, but latency increases and efficiency decreases for sparse best-effort communications
Solution Approach 1:
The patent performs authentication and capability exchange in advance during the discovery phase, before actual data transmission begins. Devices exchange authentication tokens and relaying capability information upfront, allowing subsequent data transmissions to proceed without repeated authentication handshakes. This preliminary action significantly reduces latency for sparse communications while maintaining security and reliability.
Solution Approach 2:
The patent employs lightweight, temporary authentication tokens and discovery messages that are valid only for the duration of a specific relaying transaction. Instead of maintaining persistent authenticated sessions, devices use disposable authentication credentials for each relaying operation, minimizing the time overhead associated with authentication while ensuring security. These short-living authentication objects are discarded after use, eliminating the latency of maintaining persistent paired connections.
3Reliability
If high overhead procedures are used for device pairing, then secure relaying is established, but productivity decreases for IoT devices with varying link quality
Solution Approach 1:
The patent applies different levels of authentication and security procedures based on local conditions and device types. For trusted IoT devices with stable link quality, the system uses simplified authentication mechanisms, while for devices with varying or poor link quality, more robust security procedures are applied. This localized quality approach ensures secure relaying where needed while maximizing productivity for devices that can operate with lighter overhead, thereby improving overall system efficiency.
Data Source
Figure 1~2
Figure 3~7
Figure 4
AI summary
A method for dynamically relaying data includes receiving an advertisement for dynamic relaying services from a relay device, establishing a first device-to-device (D2D) connection with the relay device in accordance with the advertisement, transmitting a data packet to the relay device using the first D2D connection, and releasing the first D2D connection automatically after transmitting the data packet.