PDAP Layer Header Compression for 5G QoS
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In 5G systems, the addition of a new protocol layer complicates the implementation of header compression functions for the Robust Header Compression (RoHC) entity, as it can only recognize regular TCP/IP headers, and there is no existing solution to support header compression under this architecture without affecting the RoHC protocol entity's functions.
Innovation Solution
A method for data transmission that involves compressing headers using the Packet Data Adaption Protocol (PDAP) or Packet Data Convergence Protocol (PDCP) layer, adding a PDAP or PDCP header to the data packet, and transmitting it to a lower layer, allowing the new architecture to support header compression by configuring a compression entity at the PDAP or PDCP layer.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a new protocol layer (PDAP) is added above the PDCP layer to support 5G QoS functionality, then the system can provide enhanced QoS indication mechanisms, but the RoHC entity can no longer recognize headers and header compression cannot be implemented
Solution Approach 1:
The patent segments the protocol stack by placing the RoHC entity at the PDAP layer rather than the PDCP layer. This segmentation allows the new PDAP layer to handle QoS functionality while the RoHC entity independently processes header compression at the appropriate layer boundary, resolving the conflict between new protocol requirements and existing compression capabilities.
Solution Approach 2:
The PDAP layer acts as an intermediary between the new QoS requirements and the existing RoHC compression mechanism. By positioning the RoHC entity within PDAP and using PDCP as the transport layer, the patent creates an intermediary structure that preserves header compression functionality while enabling new QoS capabilities through the PDAP header format.
2Adaptability or versatility
If a PDAP layer is introduced with its own header format, then QoS functionality is enhanced, but the receiving RoHC entity cannot identify where the IP packet payload stops and where the PDAP header starts
Solution Approach 1:
The patent applies preliminary action by performing header compression on IP packets before they are encapsulated in the PDAP layer. The RoHC entity at the PDAP layer compresses the IP header first, then the compressed result is placed in the PDAP PDU. This preliminary compression action eliminates the boundary identification problem because the RoHC entity processes only the IP header portion before PDAP encapsulation.
Solution Approach 2:
The patent changes the dimensional organization of the protocol stack by making the RoHC entity a sub-module of PDAP rather than PDCP. This dimensional reorganization allows the compression function to operate at the correct logical layer boundary, where it can properly identify IP packet boundaries even when PDAP headers are present in the transmitted data stream.
Data Source
Figure 1~2
Figure 3~4
Figure 5~6
AI summary
A method for data transmission and a terminal are provided, to solve a problem in a 5G system about how to implement a header compression function under an architecture where a new protocol layer is added. The method includes: compressing, for a data packet with a header, the header by a Packet Data Adaption Protocol PDAP layer or a Packet Data Convergence Protocol PDCP layer to obtain a data packet with the compressed header; and adding a PDCP header into the data packet with the compressed header and transmitting a data packet with the compressed header and the PDCP header to a lower layer. In the architecture where the PDAP layer is added, the header compression is implemented through the PDAP layer or the PDCP layer, so that the new architecture where the PDAP layer is added is capable of supporting the header compression function.