10 Handling of unknown, unforeseen and erroneous protocol data
25.3223GPPRadio Link Control (RLC) protocol specificationRelease 17TS
Errors and the handling of errors defined in this clause are normative.
10.1 Erroneous Sequence Number
A STATUS PDU or Piggybacked STATUS PDU including "erroneous Sequence Number" is a STATUS PDU or Piggybacked STATUS PDU that contains:
– a LIST, BITMAP or RLIST SUFI in which the "Sequence Number" of at least one AMD PDU that is negatively acknowledged is outside the interval VT(A)"Sequence Number"< VT(S); or
– an ACK SUFI in which "LSN" is outside the interval VT(A)"LSN" VT(S).
If an AM RLC entity receives a STATUS PDU or a Piggybacked STATUS PDU including "erroneous Sequence Number", it shall:
– discard the STATUS PDU or the Piggybacked STATUS PDU;
– if inter-Node B Multiflow operation is not configured by higher layers, initiate the RLC reset procedure (see subclause 11.4).
10.2 Inconsistent status indication
If an AM RLC entity receives a STATUS PDU or a Piggybacked STATUS PDU that indicates different status for the same AMD PDU, it shall:
– discard the STATUS PDU or the Piggybacked STATUS PDU.
10.3 Invalid PDU format
If an UM or AM RLC entity receives a RLC PDU that contains reserved or invalid values (see subclause 9.2), it shall:
– discard the RLC PDU.
10.4 RLC PDU with CRC error
If an UM or AM RLC entity receives a RLC PDU with an error indication, it shall:
– discard the RLC PDU.
If a TM RLC entity receives a RLC PDU with an error indication, it shall:
– if "Delivery of Erroneous SDUs" is configured:
– process the RLC PDU according to subclause 11.1.3;
– otherwise:
– discard the RLC PDU.