# US 2025/0097768 A1 · Assistance information for disaggregated network nodes > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2025/0097768 A1 - Document ID: US20250097768A1 - Status: Published application - Kind: A1 - Application number: 18/468,155 - Filed: 2023-09-15 - Published: 2025-03-20 - Earliest claimed: 2023-09-15 - Assignees: QUALCOMM Incorporated - Applicants: QUALCOMM Incorporated - Inventors: Toru UCHINO; Prasad Reddy KADIRI; Bharat SHRESTHA; Umesh PHUYAL; Alberto RICO ALVARINO; Sitaramanjaneyulu KANAMARLAPUDI - Web page: https://patentgrep.com/patent/US20250097768A1 ## CPC - H04W 28/06: Optimizing {the usage of the radio link}, e.g. header compression, information sizing {, discarding information (system modifying transmission characteristic according to link quality by modifying frame length H04L1/0007; dynamic adaptation of the packet size for flow control or congestion control H04L47/365)} - H04W 80/02: Data link layer protocols - H04W 72/20: Control channels or signalling for resource management - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) ## Abstract Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a distributed unit (DU) of a network node may receive, from one or more of a user equipment (UE), a central unit (CU) of the network node, or another network node, assistance information, wherein the assistance information indicates one or more of: robust header compression (ROHC) feedback information, uplink data related information, packet reordering timer information, congestion related information, session control information, or radio resource control (RRC) message information. The DU may perform an action associated with the UE based at least in part on the assistance information. Numerous other aspects are described. ## Claims ### Claim 1 An apparatus for wireless communication at a distributed unit (DU) of a network node, comprising: one or more memories; and one or more processors coupled to the one or more memories, the one or more processors configured to cause the DU to: receive, from one or more of a user equipment (UE), a central unit (CU) of the network node, or another network node, assistance information, wherein the assistance information indicates one or more of: robust header compression (ROHC) feedback information, uplink data related information, packet reordering timer information, congestion related information, session control information, or radio resource control (RRC) message information; and perform an action associated with the UE based at least in part on the assistance information. ### Claim 2 (depends on 1) The apparatus of claim 1, wherein the one or more processors, to cause the DU to perform the action, are configured to cause the DU to: transmit, to the UE, an uplink grant indicating a transport block size (TBS) associated with a first header packet, in relation to an uplink grant indicating a TBS associated with a second header packet, based at least in part on the ROHC information. ### Claim 3 (depends on 1) The apparatus of claim 1, wherein the one or more processors are further configured to cause the DU to: receive, during a bearer setup procedure with the CU, a configuration associated with receiving the ROHC information. ### Claim 4 (depends on 1) The apparatus of claim 1, wherein the ROHC information indicates one or more of: a feedback type including an acknowledgement (ACK) or a negative acknowledgement (NACK), UE related identity information associated with the UE, an indication of whether downlink data is a packet data convergence protocol (PDCP) data packet data unit (PDU) or a PDCP control PDU, a PDCP control PDU type based at least in part on the downlink data being the PDCP control PDU, a timestamp, an indication of whether an uplink packet size will change, an expected uplink packet size, a difference of the uplink packet size from a previous uplink packet size, or a recommended transport block size (TBS). ### Claim 5 (depends on 1) The apparatus of claim 1, wherein the ROHC information is associated with a New Radio (NR) user plane data packet data unit (PDU) format, and the ROHC information is associated with a voice packet or a non-voice packet configured with ROHC. ### Claim 6 (depends on 1) The apparatus of claim 1, wherein the ROHC information indicates one or more of: a number of packets transmitted with a specific ROHC header, a time period associated with the number of packets transmitted with the full ROHC header, or an indication of an applicability to an initial ROHC context establishment, an ROHC context update, an ROHC context resynchronization, or an ROHC context repair. ### Claim 7 (depends on 1) The apparatus of claim 1, wherein the ROHC information is received from the UE, the ROHC information is received in a periodic manner or in an event triggered manner, and the ROHC information is signaled in accordance with a prohibit timer. ### Claim 8 (depends on 1) The apparatus of claim 1, wherein the ROHC information is received from the CU, the ROHC information includes static information, the ROHC information includes dynamic information associated with a UE uplink ROHC behavior, and the dynamic information is received in a periodic manner or in an event triggered manner. ### Claim 9 (depends on 1) The apparatus of claim 1, wherein the assistance information indicates one or more of: an identification of a stream, a UE identifier (ID), a flow ID, a bearer ID, a radio link control (RLC) entity ID, an RLC channel ID, an RLC bearer ID, or a logical channel ID. ### Claim 10 (depends on 1) The apparatus of claim 1, wherein the assistance information indicates one or more of: a cause value associated with an expected expiry of a packet data convergence protocol (PDCP) reordering timer, or a request for additional uplink resources. ### Claim 11 (depends on 1) The apparatus of claim 1, wherein: the uplink data related information is received from the UE, the CU, or the other network node, the uplink data related information is associated with multimedia traffic, and the uplink data related information indicates one or more of: an expected periodicity of uplink data, an expected uplink data size, or a period of change to a periodicity of uplink data; and the one or more processors, to cause the DU to perform the action, are configured to cause the DU to: receive uplink data from the UE based at least in part on the uplink data related information. ### Claim 12 (depends on 1) The apparatus of claim 1, wherein the one or more processors, to cause the DU to perform the action, are configured to cause the DU to: control a scheduling for the UE, a bearer, or a logical channel based at least in part on the packet reordering timer information, wherein the packet reordering timer information is associated with a medium access control (MAC) retransmission or a radio link control (RLC) retransmission to avoid an expiry of a packet data convergence protocol (PDCP) reordering timer. ### Claim 13 (depends on 12) The apparatus of claim 12, wherein: the packet reordering timer information is received from the CU and includes a PDCP reordering timer value used by the CU; and the one or more processors, to cause the DU to perform the action, are configured to cause the DU to: maintain a PDCP reordering timer status based at least in part on a received uplink PDCP packet data unit (PDU); provide uplink resources for the UE, the bearer or the logical channel based at least in part on an expected expiry of the PDCP reordering timer; and trigger an RLC status report transmission to request the UE to perform an RLC retransmission in an uplink direction. ### Claim 14 (depends on 12) The apparatus of claim 12, wherein the one or more processors are further configured to cause the DU to: receive, from the CU and based at least in part on a trigger, an indication of a PDCP reordering timer status or a request for an uplink resource assignment, wherein the trigger is based at least in part on a periodic timer expiry or an event trigger; and the one or more processors, to cause the DU to perform the action, are configured to cause the DU to: provide uplink resources for the UE, the bearer or the logical channel based at least in part on an expected expiry of the PDCP reordering timer; and trigger an RLC status report transmission to request the UE to perform an RLC retransmission in an uplink direction. ### Claim 15 (depends on 1) The apparatus of claim 1, wherein: the congestion related information is received from the UE, the CU, or the other network node based at least in part on a trigger for sending the congestion related information, and the congestion related information indicates one or more of: a packet data convergence protocol (PDCP) discard occurrence in an uplink direction, congestion resolution information, or transmission control protocol (TCP) acknowledgements (ACKs) transmitted in a downlink direction, and the one or more processors, to cause the DU to perform the action, are configured to cause the DU to: provide uplink resources for the UE, a bearer, or a logical channel based at least in part on the congestion related information. ### Claim 16 (depends on 15) The apparatus of claim 15, wherein the congestion related information is received in response to one of: a packet discard, a certain time period having elapsed from a time when a packet arrived in a UE buffer, or a detection of an upper layer in recovering a packet loss through a slow-start or a duplicate ACK (DUPACK) recovery phase. ### Claim 17 (depends on 1) The apparatus of claim 1, wherein: the session control information is received from the UE, the CU, or the other network node and indicates one or more of: an expected period of time to complete a session control procedure, an expected number of control packets to complete the session control procedure, or a cause value associated with a session start, a session resume, a session release, or a session termination; and the one or more processors, to cause the DU to perform the action, are configured to cause the DU to: provide uplink resources for the UE, a bearer, or a logical channel based at least in part on the session control information. ### Claim 18 (depends on 1) The apparatus of claim 1, wherein: the RRC message information is received from the CU and indicates one or more of: an expected processing time of an RRC message, or an RRC message type; and the one or more processors, to cause the DU to perform the action, are configured to cause the DU to: provide, to the UE, an uplink grant to receive an RRC complete message, wherein a timing to provide the uplink grant is based at least in part on the expected processing time of the RRC message. ### Claim 19 A method of wireless communication performed by a distributed unit (DU) of a network node, comprising: receiving, from one or more of a user equipment (UE), a central unit (CU) of the network node, or another network node, assistance information, wherein the assistance information indicates one or more of: robust header compression (ROHC) feedback information, uplink data related information, packet reordering timer information, congestion related information, session control information, or radio resource control (RRC) message information; and performing an action associated with the UE based at least in part on the assistance information. ### Claim 20 (depends on 19) The method of claim 19, wherein performing the action comprises: transmitting, to the UE, an uplink grant indicating a transport block size (TBS) associated with a first header packet, in relation to an uplink grant indicating a TBS associated with a second header packet, based at least in part on the ROHC information. ### Claim 21 (depends on 19) The method of claim 19, wherein the ROHC information indicates one or more of: a feedback type including an acknowledgement (ACK) or a negative acknowledgement (NACK), UE related identity information associated with the UE, an indication of whether downlink data is a packet data convergence protocol (PDCP) data packet data unit (PDU) or a PDCP control PDU, a PDCP control PDU type based at least in part on the downlink data being the PDCP control PDU, a timestamp, an indication of whether an uplink packet size will change, an expected uplink packet size, a difference of the uplink packet size from a previous uplink packet size, or a recommended transport block size (TBS). ### Claim 22 (depends on 19) The method of claim 19, wherein the ROHC information indicates one or more of: a number of packets transmitted with a specific ROHC header, a time period associated with the number of packets transmitted with the full ROHC header, or an indication of an applicability to an initial ROHC context establishment, an ROHC context update, an ROHC context resynchronization, or an ROHC context repair. ### Claim 23 (depends on 19) The method of claim 19, wherein: the ROHC information is received from the UE, the ROHC information is received in a periodic manner or in an event triggered manner, and the ROHC information is signaled in accordance with a prohibit timer; the ROHC information is received from the CU, the ROHC information includes static information, the ROHC information includes dynamic information associated with a UE uplink ROHC behavior, and the dynamic information is received in a periodic manner or in an event triggered manner; or the ROHC information is associated with a voice packet or a non-voice packet configured with ROHC. ### Claim 24 (depends on 19) The method of claim 19, wherein: the uplink data related information is received from the UE, the CU, or the other network node, the uplink data related information is associated with multimedia traffic, and the uplink data related information indicates one or more of: an expected periodicity of uplink data, an expected uplink data size, or a period of change to a periodicity of uplink data; and performing the action comprises: receiving uplink data from the UE based at least in part on the uplink data related information. ### Claim 25 (depends on 19) The method of claim 19, wherein performing the action comprises: controlling a scheduling for the UE, a bearer, or a logical channel based at least in part on the packet reordering timer information, wherein the packet reordering timer information is associated with a medium access control (MAC) retransmission or a medium access control (MAC) retransmission or a radio link control (RLC) retransmission to avoid an expiry of a packet data convergence protocol (PDCP) reordering timer. ### Claim 26 (depends on 25) The method of claim 25, wherein: the packet reordering timer information is received from the CU and includes a PDCP reordering timer value used by the CU; and performing the action comprises: maintaining a PDCP reordering timer status based at least in part on a received uplink PDCP packet data unit (PDU); providing uplink resources for the UE, the bearer or the logical channel based at least in part on an expected expiry of the PDCP reordering timer; and triggering an RLC status report transmission to request the UE to perform an RLC retransmission in an uplink direction. ### Claim 27 (depends on 25) The method of claim 25, further comprising: receiving, from the CU and based at least in part on a trigger, an indication of a PDCP reordering timer status or a request for an uplink resource assignment, wherein the trigger is based at least in part on a periodic timer expiry or an event trigger; and performing the action comprises: providing uplink resources for the UE, the bearer or the logical channel based at least in part on an expected expiry of the PDCP reordering timer; and triggering an RLC status report transmission to request the UE to perform an RLC retransmission in an uplink direction. ### Claim 28 (depends on 19) The method of claim 19, wherein: the congestion related information is received from the UE, the CU, or the other network node based at least in part on a trigger for sending the congestion related information, the congestion related information is received in response to one of: a packet discard, a certain time period having elapsed from a time when a packet arrived in a UE buffer, or a detection of an upper layer in recovering a packet loss through a slow-start or a duplicate ACK (DUPACK) recovery phase, and the congestion related information indicates one or more of: a packet data convergence protocol (PDCP) discard occurrence in an uplink direction, congestion resolution information, or transmission control protocol (TCP) acknowledgements (ACKs) transmitted in a downlink direction, and performing the action comprises: providing uplink resources for the UE, a bearer, or a logical channel based at least in part on the congestion related information. ### Claim 29 A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising: one or more instructions that, when executed by one or more processors of a distributed unit (DU) of a network node, cause the DU to: receive, from one or more of a user equipment (UE), a central unit (CU) of the network node, or another network node, assistance information, wherein the assistance information indicates one or more of: robust header compression (ROHC) feedback information, uplink data related information, packet reordering timer information, congestion related information, session control information, or radio resource control (RRC) message information; and performing an action associated with the UE based at least in part on the assistance information. ### Claim 30 An apparatus for wireless communication, comprising: means for receiving, from one or more of a user equipment (UE), a central unit (CU), or another network node, assistance information, wherein the assistance information indicates one or more of: robust header compression (ROHC) feedback information, uplink data related information, packet reordering timer information, congestion related information, session control information, or radio resource control (RRC) message information; and performing an action associated with the UE based at least in part on the assistance information.