em at the receiver side of a low-bandwidth/capacity-limited link. The use of header compression has a well-established history in transport of IP-based payloads over capacity-limited wireless links where more bandwidth efficient transport methods are required. The Internet Engineering Task Force (IETF) 2 has developed several header compression proto- cols that are widely used in telecommunication systems. The header compression mechanism used in 3GPP LTE and NR standards is based on IETF RFC 5795, ROHC framework. The IP together with transport protocols such as TCP or UDP and application layer protocols (e.g., RTP) are described in the form of payload headers. The information carried in the header helps the applications to communicate over large distances connected by multiple links or hops in the network. This information consists of source and destination addresses, ports, protocol identi- fiers, sequence numbers, error checksums, etc. Under nominal conditions, most of the informa- tion carried in packet-headers remains the same or changes in specific patterns. By observing the fields that remain constant or change in specific patterns, it is possible either not to send them in each packet, or to represent them in a smaller number of bits than would have been orig- inally required. This process is referred to as header compression. The PDCP sublayer, at the transmit side, performs encryption of IP packets to protect user privacy, and additionally for the control-plane messages, performs integrity protection to ensure that control messages originate from the correct source and can be authenticated. At the receiver side the PDCP performs the corresponding decryption and decompression oper- ation. The PDCP further discards duplicate PDUs and performs in-sequence delivery of the packets. Upon handover, the undelivered downlink PDUs will be forwarded by the PDCP sublayer of the source gNB to peer entity of the target gNB for delivery to the UE. The PDCP entity in the device will also handle retransmission of all up