# US 11,910,223 B2 · Packet data converge protocol protocol data unit pre-processing > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 11,910,223 B2 - Document ID: US11910223B2 - Status: Granted - Kind: B2 - Application number: 17/850,752 - Filed: 2022-06-27 - Published: 2022-10-13 - Granted: 2024-02-20 - Earliest claimed: 2017-04-26 - Assignees: Motorola Mobility LLC - Applicants: Motorola Mobility LLC - Inventors: Joachim Loehr; Prateek Basu Mallick; Ravi Kuchibhotla - Web page: https://patentgrep.com/patent/US11910223B2 ## CPC - H04W 28/0205: {at the air interface (dynamic wireless traffic scheduling H04W72/12)} - H04L 69/324: in the data link layer [OSI layer 2], e.g. HDLC - H04W 28/0252: {per individual bearer or channel (dynamic wireless traffic scheduling H04W72/12)} - H04W 28/065: {using assembly or disassembly of packets} - H04W 28/082: among bearers or channels - H04W 72/23: in the downlink direction of a wireless link, i.e. towards a terminal - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract For pre-processing Packet Data Converge Protocol (PDCP) Protocol Data Units (PDU), a method receives a configuration of a reference uplink grant. In response to receiving the configuration of the reference uplink grant, the method calculates a preprocessing threshold of PDU for preprocessing by a Radio Link Control (RLC)/Medium Access Control (MAC) for each of one or more radio bearers. ## Claims ### Claim 1 An apparatus for wireless communication at a device, the apparatus comprising: a processor performing: submitting, from a packet data convergence protocol (PDCP) to a radio link control (RLC) entity, one or more radio link control (RLC) service data units (SDUs); generating, by the RLC entity, one or more RLC protocol data units (PDUs) based in part on the one or more RLC SDUS, wherein each respective RLC PDU associated each respective RLC SDU comprises an RLC header; receiving, by the RLC entity, an indication from the PDCP entity to discard at least one RLC SDU associated with at least one generated RLC PDU of the one or more generated RLC PDUs; discarding, by the RLC entity, the at least one RLC SDU based in part on the received indication from the PDCP entity; and reassigning a respective sequence number associated with one or more subsequent generated RLC PDUs based in part on the at least one discarded RLC SDU. ### Claim 2 (depends on 1) The apparatus of claim 1, the processor further performing: determining a lack of submitting to a medium access control (MAC) entity the at least one RLC SDU or a segment of the at least one RLC SDU, wherein discarding the at least one RLC SDU is based in part on the lack of submitting to the MAC entity the at least one RLC SDU or the segment of the at least one RLC SDU. ### Claim 3 (depends on 1) The apparatus of claim 1, the processor further performing: storing, in a memory associated with the device, the one or more generated RLC PDUs. ### Claim 4 (depends on 1) The apparatus of claim 1, wherein the RLC entity performs data transfer in a mode selected from the group consisting of Transparent Mode (TM), Unacknowledged Mode (UM) or Acknowledged Mode (AM). ### Claim 5 (depends on 4) The apparatus of claim 4, wherein the RLC entity in TM is either a transmitting TM RLC entity or a receiving TM RLC entity. ### Claim 6 (depends on 4) The apparatus of claim 4, wherein the RLC entity in UM is either a transmitting UM RLC entity or a receiving UM RLC entity. ### Claim 7 (depends on 4) The apparatus of claim 4, wherein the RLC entity in AM is either a transmitting AM RLC entity or a receiving UM RLC entity. ### Claim 8 A method of wireless communication at a device, the method comprising: submitting, from a packet data convergence protocol (PDCP) to a radio link control (RLC) entity, one or more radio link control (RLC) service data units (SDUs); generating, by the RLC entity, one or more RLC protocol data units (PDUs) based in part on the one or more RLC SDUS, wherein each respective RLC PDU associated each respective RLC SDU comprises an RLC header; receiving, by the RLC entity, an indication from the PDCP entity to discard at least one RLC SDU associated with at least one generated RLC PDU of the one or more generated RLC PDUs; discarding, by the RLC entity, the at least one RLC SDU based in part on the received indication from the PDCP entity; and reassigning a respective sequence number associated with one or more subsequent generated RLC PDUs based in part on the at least one discarded RLC SDU. ### Claim 9 (depends on 8) The method of claim 8, further comprising: determining a lack of submitting to a medium access control (MAC) entity the at least one RLC SDU or a segment of the at least one RLC SDU, wherein discarding the at least one RLC SDU is based in part on the lack of submitting to the MAC entity the at least one RLC SDU or the segment of the at least one RLC SDU. ### Claim 10 (depends on 8) The method of claim 8, further comprising: storing, in a memory associated with the device, the one or more generated RLC PDUs. ### Claim 11 (depends on 8) The method of claim 8, wherein the RLC entity performs data transfer in a mode selected from the group consisting of Transparent Mode (TM), Unacknowledged Mode (UM) or Acknowledged Mode (AM). ### Claim 12 (depends on 11) The method of claim 11, wherein the RLC entity in TM is either a transmitting TM RLC entity or a receiving TM RLC entity. ### Claim 13 (depends on 11) The method of claim 11, wherein the RLC entity in UM is either a transmitting UM RLC entity or a receiving UM RLC entity. ### Claim 14 (depends on 11) The method of claim 11, wherein the RLC entity in AM is either a transmitting AM RLC entity or a receiving UM RLC entity. ### Claim 15 A program product for wireless communication at a device, the program product comprising a non-transitory computer readable storage medium that stores code executable by a processor, the executable code comprising code to perform: submitting, from a packet data convergence protocol (PDCP) to a radio link control (RLC) entity, one or more radio link control (RLC) service data units (SDUs); generating, by the RLC entity, one or more RLC protocol data units (PDUs) based in part on the one or more RLC SDUS, wherein each respective RLC PDU associated each respective RLC SDU comprises an RLC header; receiving, by the RLC entity, an indication from the PDCP entity to discard at least one RLC SDU associated with at least one generated RLC PDU of the one or more generated RLC PDUs; discarding, by the RLC entity, the at least one RLC SDU based in part on the received indication from the PDCP entity; and reassigning a respective sequence number associated with one or more subsequent generated RLC PDUs based in part on the at least one discarded RLC SDU. ### Claim 16 (depends on 15) The program product of claim 15, code further performing: determining a lack of submitting to a medium access control (MAC) entity the at least one RLC SDU or a segment of the at least one RLC SDU, wherein discarding the at least one RLC SDU is based in part on the lack of submitting to the MAC entity the at least one RLC SDU or the segment of the at least one RLC SDU. ### Claim 17 (depends on 15) The program product of claim 15, code further performing: storing, in a memory associated with the device, the one or more generated RLC PDUs. ### Claim 18 (depends on 15) The program product of claim 15, wherein the RLC entity performs data transfer in a mode selected from the group consisting of Transparent Mode (TM), Unacknowledged Mode (UM) or Acknowledged Mode (AM). ### Claim 19 (depends on 18) The program product of claim 18, wherein the RLC entity in TM is either a transmitting TM RLC entity or a receiving TM RLC entity. ### Claim 20 (depends on 18) The program product of claim 18, wherein the RLC entity in UM is either a transmitting UM RLC entity or a receiving UM RLC entity.