D2D Receiving Terminal Compressed Header Decoding Timing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In D2D proximity services, the timing difference between receiving and transmitting entities in mobile communication systems leads to failures in decoding compressed headers, causing erroneous data reception, especially in scenarios where the receiving entity is formed after the transmitting entity.
Innovation Solution
The receiving terminal holds the data unit with a compressed header for a predetermined period and forms a feedback transmitting entity to inform the transmitting terminal of decoding failures, allowing the transmission of non-compressed headers, and the transmitting terminal uses compressed headers only in unicast D2D communication to prioritize overhead reduction.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of substance
If header compression technology is used in D2D proximity service, then overhead of the header is reduced, but decoding failure occurs when receiving entity is formed after transmitting entity
Solution Approach 1:
The transmitting terminal transmits non-compressed headers before transmitting compressed headers. This preliminary action ensures that the receiving terminal has the necessary context information (non-compressed header) available in advance to successfully decode the subsequent compressed headers, even when the receiving entity is formed after the transmitting entity.
Solution Approach 2:
The non-compressed header acts as an intermediary that bridges the timing gap between entity formation and data reception. By providing the full header information first, it enables the receiving terminal to establish the necessary context before receiving compressed headers, resolving the decoding failure issue caused by timing differences.
2Loss of time
If compressed header is used immediately without waiting for receiving entity formation, then communication timing is improved, but decoding failure occurs
Solution Approach 1:
The transmitting terminal performs preliminary transmission of non-compressed headers to establish context information before transmitting compressed headers. This allows the receiving terminal to form the receiving entity and decode headers successfully without introducing significant communication delay.
Solution Approach 2:
The header transmission is segmented into two phases: first transmitting non-compressed headers to establish context, then transmitting compressed headers for efficient data transmission. This segmentation resolves the timing conflict by separating the context establishment phase from the efficient data transmission phase.
3Reliability
If non-compressed header is transmitted before compressed header, then decoding reliability is improved, but header overhead increases temporarily
Solution Approach 1:
Non-compressed headers are transmitted preliminarily to establish context, but only temporarily. After the receiving terminal decodes the context, subsequent headers use compression, so the overhead increase is limited to the initial phase only.
Solution Approach 2:
The non-compressed header is discarded after serving its purpose of establishing context for the receiving terminal. The receiving terminal recovers the necessary information from the non-compressed header and then uses this recovered context to efficiently decode subsequent compressed headers, minimizing long-term overhead.
Data Source
AI summary
A receiving terminal includes: a receiver configured to receive a data unit configured by data and a header, from the transmitting terminal in the D2D communication; and a controller configured to hold the data unit including a compressed header for a predetermined period even if decoding the compressed header is failed when the compressed header is used as the header. In the D2D communication, a timing at which a receiving entity is formed in the receiving terminal differs from a timing at which a transmitting entity is formed in the transmitting terminal.