Abstract: A transmitter device may be configured to perform to robust header compression optimization to improve channel throughput. In some aspects, the transmitter device may establish a first base context between the transmitter device and a receiver device, wherein a first context identifier is assigned to the first base context, establish a replication context between the devices, wherein the replication context is derivable from the first base context and a second context identifier is assigned to the replication context, and identify a new context. Further, the transmitter device may reassign the first context identifier to the new context, disassociate the second context identifier from the first context identifier, establish a second base context between the devices, wherein a third context identifier is assigned to the second base context, and associate, based on the replication context being derivable from the second base context, the second context identifier to the third context identifier.

Abstract: In one aspect, a method of wireless communication includes determining a number of bytes in a compressed queue and a number of bytes in an uncompressed queue. The method also includes transmitting a buffer status report (BSR) indicating at least the number of bytes in the compressed queue. The method includes receiving an uplink grant indicating one or more uplink grant resources and a number of bytes allocated for the one or more uplink grant resources. The method also includes generating a transport block (TB) based on the uplink grant and the BSR and from data of at least the compressed queue, wherein the TB includes one or more compressed packets and one or more uncompressed packets. The method further includes transmitting a PUSCH transmission including the TB during an uplink grant resource of the one or more uplink grant resources. Other aspects and features are also claimed and described.

Abstract: A wireless communication utilizes robust header compression efficiently with improved improvements in packet data convergence protocol configuration for increasing channel throughput. A user equipment (UE) receives a configuration indicating a first listing of header generic options that are supported between the UE and a first base station. The UE obtains a first packet including a first uncompressed header that indicates header parameters. The UE determines whether the header parameters in the first uncompressed header corresponds to at least one header generic option in the first listing of header generic options. The UE communicates the first packet that may have a first compressed header based on a first header compression profile or an uncompressed header depending on whether the header parameters in the first uncompressed header corresponds to at least one header generic option in the first listing of header generic options.

Abstract: A wireless communication utilizes robust header compression efficiently with improved improvements in packet data convergence protocol configuration for increasing channel throughput. A user equipment (UE) receives a configuration indicating a first listing of header generic options that are supported between the UE and a first base station. The UE obtains a first packet including a first uncompressed header that indicates header parameters. The UE determines whether the header parameters in the first uncompressed header corresponds to at least one header generic option in the first listing of header generic options. The UE communicates the first packet that may have a first compressed header based on a first header compression profile or an uncompressed header depending on whether the header parameters in the first uncompressed header corresponds to at least one header generic option in the first listing of header generic options.

Abstract: In one aspect, a method of wireless communication includes determining a number of bytes in a compressed queue and a number of bytes in an uncompressed queue. The method also includes transmitting a buffer status report (BSR) indicating at least the number of bytes in the compressed queue. The method includes receiving an uplink grant indicating one or more uplink grant resources and a number of bytes allocated for the one or more uplink grant resources. The method also includes generating a transport block (TB) based on the uplink grant and the BSR and from data of at least the compressed queue, wherein the TB includes one or more compressed packets and one or more uncompressed packets. The method further includes transmitting a PUSCH transmission including the TB during an uplink grant resource of the one or more uplink grant resources. Other aspects and features are also claimed and described.

Abstract: Various aspects include methods for Transmission Control Protocol (TCP)/Internet Protocol (IP) (TCP/IP) packet transmission and compression of headers for TCP/IP packet transmission. Various embodiments may include a packet data convergence protocol (PDCP) layer of a processing device applying least significant bit (LSB) encoding to a TCP Timestamp (TS) option of a TCP/IP packet using an offset parameter of zero to generate a compressed header in response to determining that a TCP TS field of the TCP/IP packet and a TCP TS field of a last TCP/IP packet transmitted have a same value. In some embodiments, a Timestamp Value (TSVal) field or a Timestamp Echo Reply (TSEcho) field of the TCP TS option of the compressed header may have a size of one byte.

Abstract: Various aspects include methods for Transmission Control Protocol (TCP)/Internet Protocol (IP) (TCP/IP) packet transmission and compression of headers for TCP/IP packet transmission. Various embodiments may include a packet data convergence protocol (PDCP) layer of a processing device applying least significant bit (LSB) encoding to a TCP Timestamp (TS) option of a TCP/IP packet using an offset parameter of zero to generate a compressed header in response to determining that a TCP TS field of the TCP/IP packet and a TCP TS field of a last TCP/IP packet transmitted have a same value. In some embodiments, a Timestamp Value (TSVal) field or a Timestamp Echo Reply (TSEcho) field of the TCP TS option of the compressed header may have a size of one byte.

Abstract: Systems, methods, and computing platforms for context identifier allocation for data packet header compression are provided. Exemplary implementations may: obtain a first packet of a stream to be sent using a header compression protocol; determine a context identifier (CID) to associate with the stream based, at least in part, on a packet type of the first packet; generate a compressed header for the first packet according to the header compression protocol and based on the determined CID; and transmit the first packet with the compressed header.

Abstract: Methods, systems, and devices for wireless communication are described. Different robust header compression (RoHC) schemes may be used when a change in a header extension flag between packets of a communication session is determined. For example, a transmitting device may determine a value of a header extension flag in a packet has changed with respect to header extension flags in preceding packets. Upon detecting the change in the header extension flag, the device may compress the header using different RoHC schemes. For instance, the device may compress the header by reverting to an initialization and refresh (IR) state. Additionally or alternatively, the device may compress the header using a compression profile that refrains from compressing a certain portion of the header. In some cases, the RoHC scheme used for compressing the header may be based on how frequently the value of the extension flag changes between packets.

Abstract: A recovery mechanism for robust header compression (ROHC) is disclosed for wireless communication systems. The ROHC recovery mechanism may allow a receiver and/or transmitter in the wireless systems to establish or reestablish a context of a packet transmission session when an initialization and refresh message is lost. In the ROHC recovery mechanism, upon receiving a compressed packet that is not associated with a context, a receiver sends a message to a transmitter suggesting the transmitter to transition to another mode. Upon receiving a subsequent packet transmission that is not associated with a context, the receiver sends another message indicating that a context has not been established or has been lost. The transmitter may then send the receiver necessary information to establish a context for the packet transmission session.

Abstract: Methods, systems, and devices may implement a header repair mechanism to deal with a loss of successive compressed headers (e.g., due to radio interface). The present methods and apparatus exploit the fact that once a correct timestamp (TS) from a previous decompression success (called “last successfully decomp_TS”) is known, another (e.g., a subsequent) TS should be in the form: last successfully decomp_TS+n*min_TS_STRIDE, where n is a positive integer if the estimated sequence number (SN) is higher than the last successfully decompressed SN, and a negative integer if the estimated SN is lower than the last successfully decompressed SN, and min_TS_STRIDE is the expected minimum TS increment, which is known and directly related to the medium sample rate and frame rate, for example.

Abstract: Methods, systems, and devices for wireless communication are described. Different robust header compression (RoHC) schemes may be used when a change in a header extension flag between packets of a communication session is determined. For example, a transmitting device may determine a value of a header extension flag in a packet has changed with respect to header extension flags in preceding packets. Upon detecting the change in the header extension flag, the device may compress the header using different RoHC schemes. For instance, the device may compress the header by reverting to an initialization and refresh (IR) state. Additionally or alternatively, the device may compress the header using a compression profile that refrains from compressing a certain portion of the header. In some cases, the RoHC scheme used for compressing the header may be based on how frequently the value of the extension flag changes between packets.

Abstract: Methods, systems, and devices may implement a header repair mechanism to deal with a loss of successive compressed headers (e.g., due to radio interface). The present methods and apparatus exploit the fact that once a correct timestamp (TS) from a previous decompression success (called “last successfully decomp_TS”) is known, another (e.g., a subsequent) TS should be in the form: last successfully decomp_TS+n*min_TS_STRIDE, where n is a positive integer if the estimated sequence number (SN) is higher than the last successfully decompressed SN, and a negative integer if the estimated SN is lower than the last successfully decompressed SN, and min_TS_STRIDE is the expected minimum TS increment, which is known and directly related to the medium sample rate and frame rate, for example.

Abstract: A recovery mechanism for robust header compression (ROHC) is disclosed for wireless communication systems. The ROHC recovery mechanism may allow a receiver and/or transmitter in the wireless systems to establish or reestablish a context of a packet transmission session when an initialization and refresh message is lost. In the ROHC recovery mechanism, upon receiving a compressed packet that is not associated with a context, a receiver sends a message to a transmitter suggesting the transmitter to transition to another mode. Upon receiving a subsequent packet transmission that is not associated with a context, the receiver sends another message indicating that a context has not been established or has been lost. The transmitter may then send the receiver necessary information to establish a context for the packet transmission session.