name: PID
full_form: Packet ID
context: In subclause 5.1.10.2 it was stated that the CID field in the ROHC packet format could be 0, 1 or 2 octets in length. Large CID spaces are not typically required for terminals in the wireless scenario. It is possible to include the CID value on the PDCP layer instead of ROHC headers. In 3GPP Release 99, the PDCP layer can be configured to introduce a PDCP header or not to introduce a PDCP header. The PDCP header is typically required for HC protocols that require link layer (i.e. the layer that 'carries' HC) identification of the HC packet types. 3GPP Release'99 includes only one HC protocol (RF2507) and this requires link level identification of the HC packet formats. Header compression protocols that do not require link layer identification do not require PDCP to include a PDCP header. ROHC is one such protocol. PDCP configured to support only ROHC would typically be configured not to introduce a PDCP header. With the introduction of an additional HC protocol to the suite of HC
description: The Packet ID (PID) is a parameter used in the PDCP sublayer to identify different types of header compression protocols and packet types within a protocol. It is utilized to map PID values to various packet types, with specific rules governing its assignment and usage.
explanation: The context describes PID as a configurable value used for differentiation between protocols and packet types within the PDCP sublayer. Its specific mapping rules solidify its classification as a parameter.
section_title: 5.1.1	Mapping of PID values
biotag_Context: O,O,O,O,O,O,O,O,B-Parameter,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,B-Protocol,O,O,O,B-Protocol,O,O,B-Organization,B-Specification,O,O,B-Protocol,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,B-Protocol,O,O,B-Protocol,O,O,O,O,O,B-Technology,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Technology,O,O,B-Organization,O,O,O,O,B-Technology,O,O,O,O,O,O,O,O,O,O,B-Technology,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,B-Protocol,O,B-Protocol,O,O,O,O,B-Protocol,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,B-Technology,O,O,O,O,O,B-Technology
biotag_Description: O,B-Parameter,I-Parameter,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O