name: ROHC
full_form: RObust Header Compression
context: If ROHC is configured, the ROHC protocol generates two types of output packets: - ROHC compressed packets, each associated with one PDCP SDU; - standalone packets not associated with a PDCP SDU, i.e. interspersed ROHC feedback. A ROHC compressed packet is associated with the same PDCP SN and COUNT value as the related PDCP SDU. The header compression is not applicable to the SDAP header and the SDAP Control PDU if included in the PDCP SDU. For DAPS bearers, the PDCP entity shall perform the header compression for the PDCP SDU using the ROHC protocol either configured for the source cell or configured for the target cell, based on to which cell the PDCP SDU is transmitted. Interspersed ROHC feedback are not associated with a PDCP SDU. They are not associated with a PDCP SN and are not ciphered. NOTE 1: If the MAX_CID number of ROHC contexts are already established for the compressed flows and a new IP flow does not match any established ROHC context, the compressor should associate the
description: RObust Header Compression (ROHC) is a protocol used in telecommunications to compress packet headers, reducing overhead and improving efficiency. It operates on IP flows and generates compressed packets associated with PDCP SDUs or standalone feedback packets.
explanation: The text explicitly states ROHC as a protocol that compresses headers within IP flows, aligning with the definition of a protocol as a set of rules governing data transmission.
section_title: 5.7.4Header compression using ROHC
biotag_Context: O,B-Protocol,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,B-Protocol,O,O,B-Protocol,O,O,O,O,O,O,O,B-Protocol,B-Message,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,B-Protocol,O,B-Connection,O,O,O,O,B-Protocol,O,O,B-Technology,O,O,B-Protocol,O,O,O,O,O,O,O,O,B-Protocol,B-Parameter,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,B-Parameter,O,O,O,B-Protocol,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,B-Protocol,B-Message,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O
biotag_Description: B-Protocol,I-Protocol,I-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O