Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 38.323  Word version:  18.0.0

Top   Top   Up   Prev   Next
1…   4…   5…   5.4…   5.8…   5.13…   6…   6.2.3…   7…   A…   B…

 

6.2.3  Control PDUp. 38

6.2.3.1  Control PDU for PDCP status reportp. 38

Figure 6.2.3.1-1 shows the format of the PDCP Control PDU carrying one PDCP status report. This format is applicable for UM DRBs, AM DRBs (including sidelink DRBs for unicast) and AM MRBs.
Reproduction of 3GPP TS 38.323, Fig. 6.2.3.1-1: PDCP Control PDU format for PDCP status report
Up

6.2.3.2  Control PDU for interspersed ROHC feedbackp. 39

Figure 6.2.3.2-1 shows the format of the PDCP Control PDU carrying one interspersed ROHC feedback. This format is applicable for UM DRBs, AM DRBs (including sidelink DRBs for unicast), UM MRBs and AM MRBs.
Reproduction of 3GPP TS 38.323, Fig. 6.2.3.2-1: PDCP Control PDU format for interspersed ROHC feedback
Up

6.2.3.3  Control PDU for EHC feedback |R16|p. 39

Figure 6.2.3.3-1 shows the format of the PDCP Control PDU carrying one EHC feedback. This format is applicable for UM DRBs, AM DRBs, UM MRBs and AM MRBs.
Reproduction of 3GPP TS 38.323, Fig. 6.2.3.3-1: PDCP Control PDU format for EHC feedback
Up

6.2.3.4  Control PDU for UDC feedback |R17|p. 40

Figure 6.2.3.4-1 shows the format of the PDCP Control PDU carrying one UDC feedback. This format is applicable for AM DRBs.
Reproduction of 3GPP TS 38.323, Fig. 6.2.3.4-1: PDCP Control PDU format for UDC feedback
Up

6.3  Parametersp. 40

6.3.1  Generalp. 40

If not otherwise mentioned in the definition of each field then the bits in the parameters shall be interpreted as follows: the left most bit string is the first and most significant and the right most bit is the last and least significant bit.
Unless otherwise mentioned, integers are encoded in standard binary encoding for unsigned integers. In all cases the bits appear ordered from MSB to LSB when read in the PDU.

6.3.2  PDCP SNp. 40

Length:
12 or 18 bits as indicated in Table 6.3.2-1. The length of the PDCP SN is configured by upper layers (pdcp-SN-SizeUL, pdcp-SN-SizeDL, or sl-PDCP-SN-Size in TS 38.331).
Length Description
12SRBs, UM DRBs, AM DRBs (including sidelink SRBs and sidelink DRBs), UM MRBs and AM MRBs
18UM DRBs, AM DRBs (including sidelink DRBs for unicast), UM MRBs and AM MRBs
Up

6.3.3  Datap. 40

Length:
Variable
This field includes one of the followings:
  • Uncompressed PDCP SDU (user plane data, or control plane data);
  • Compressed PDCP SDU (user plane data only).

6.3.4  MAC-Ip. 40

Length:
32 bits
This field carries a message authentication code calculated as specified in clause 5.9.
For SRBs for Uu interface, the MAC-I field is always present. If integrity protection is not configured, the MAC-I field is still present but should be padded with padding bits set to 0.
For sidelink SRB1, SRB2 and SRB3, the MAC-I field is present only when the sidelink SRB1, SRB2 and SRB3 are configured with integrity protection.
For DRBs (including sidelink DRBs for unicast), the MAC-I field is present only when the DRB is configured with integrity protection.
Up

6.3.5  COUNTp. 41

Length:
32 bits
The COUNT value is composed of a HFN and the PDCP SN. The size of the HFN part in bits is equal to 32 minus the length of the PDCP SN.
Reproduction of 3GPP TS 38.323, Fig. 6.3.5-1: Format of COUNT
Up

6.3.6  Rp. 41

Length:
1 bit
Reserved. In this version of the specification reserved bits shall be set to 0. Reserved bits shall be ignored by the receiver.

6.3.7  D/Cp. 41

Length:
1 bit
This field indicates whether the corresponding PDCP PDU is a PDCP Data PDU or a PDCP Control PDU.
Bit Description
0Control PDU
1Data PDU

6.3.8  PDU typep. 41

Length:
3 bits
This field indicates the type of control information included in the corresponding PDCP Control PDU.
Bit Description
000PDCP status report
001Interspersed ROHC feedback
010EHC feedback
011UDC feedback
100-111Reserved
Up

6.3.9  FMCp. 41

Length:
32 bits
First Missing COUNT. This field indicates the COUNT value of the first missing PDCP SDU within the reordering window, i.e. RX_DELIV.

6.3.10  Bitmapp. 42

Length:
Variable. The length of the bitmap field can be 0.
This field indicates which SDUs are missing and which SDUs are correctly received in the receiving PDCP entity. The bit position of Nth bit in the Bitmap is N, i.e., the bit position of the first bit in the Bitmap is 1.
Bit Description
0PDCP SDU with COUNT = (FMC + bit position) modulo 232 is missing.
1PDCP SDU with COUNT = (FMC + bit position) modulo 232 is correctly received.
Up

6.3.11  Interspersed ROHC feedbackp. 42

Length:
Variable
This field contains one ROHC packet with only feedback, i.e. a ROHC packet that is not associated with a PDCP SDU as defined in clause 5.7.4.

6.3.12  SDU Type |R16|p. 42

Length:
3 bits
PDCP SDU type, i.e. Layer-3 Protocol Data Unit type as specified in [13] and [18]. PDCP entity may handle the SDU differently per SDU Type, e.g. ROHC is applicable to IP SDU but not Non-IP SDU, Ethernet SDU, Unstructured SDU and ARP SDU.
Bit Description
000IP
001Non-IP
010Ethernet
011Unstructured
100ARP
101-111Reserved
Up

6.3.13  KNRP-sess ID |R16|p. 42

Length:
16 bits
KNRP-sess Identity as specified in TS 33.536.
For the SLRB that does not need integrity and ciphering protection, the UE shall set KNRP-sess ID to "0" in the PDCP PDU header.

6.3.14  FE |R17|p. 42

Length:
1 bit
Indication of whether checksum error is detected or not. Value '1' means checksum error is detected and the UE shall reset the compression buffer.
Bit Description
0No Error
1Checksum Error Notification

Up   Top   ToC