# US 2025/0168260 A1 · Methods and apparatus for differential quality of service (qos) handling of packets within a same service stream

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2025/0168260 A1
- Document ID: US20250168260A1
- Status: Published application
- Kind: A1
- Application number: 19/028,981
- Filed: 2025-01-17
- Published: 2025-05-22
- Earliest claimed: 2022-08-09
- Assignees: Huawei Technologies Co., Ltd.
- Applicants: Huawei Technologies Co., Ltd.
- Inventors: Yunsong Yang
- Web page: https://patentgrep.com/patent/US20250168260A1

## CPC

- H04L 69/22: Parsing or analysis of headers
- H04L 47/32: by discarding or delaying data units, e.g. packets or frames
- H04L 47/34: ensuring sequence integrity, e.g. using sequence numbers
- H04L 67/55: Push-based network services
- H04L 69/04: Protocols for data compression, e.g. ROHC
- H04L 69/40: for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection (management of faults, events, alarms or notifications in data switching networks H04L41/06)
- H04W 28/02: Traffic management, e.g. flow control or congestion control
- H04W 28/0268: {using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR] (negotiating SLA or negotiating QoS H04W28/24)}
- H04W 80/02: Data link layer protocols
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

According to embodiments, the first PDCP entity receives a PDCP DU from an associated upper layer. The first PDCP entity processes the PDCP SDU with the COUNT value to produce a first PDCP data PDU. The first PDCP entity determines a need to abandon transmission of the first PDCP data PDU. The first PDCP entity discards the first PDCP data PDU. The first PDCP entity notifies a second PDCP entity of a second device about COUNT information related to one or more discarded COUNT values. The one or more discarded COUNT values are associated with one or more discarded PDCP data PDUs. The one or more discarded PDCP data PDUs include the first PDCP data PDU. The second PDCP entity is a peer PDCP entity of the first PDCP entity for processing data received from the first device.

## Claims

### Claim 1

A method, comprising:
receiving, by a first packet data convergence protocol (PDCP) entity of a first device, a PDCP service data unit (SDU) from an associated upper layer of the first PDCP entity;
associating, by the first PDCP entity, a COUNT value with the PDCP SDU;
processing, by the first PDCP entity, the PDCP SDU with the COUNT value to produce a first PDCP data protocol data unit (PDU);
determining, by the first PDCP entity, a need to abandon transmission of the first PDCP data PDU;
discarding, by the first PDCP entity, the first PDCP data PDU based on the determining; and
notifying, by the first PDCP entity, a second PDCP entity of a second device about COUNT information related to one or more discarded COUNT values, the one or more discarded COUNT values being associated with one or more discarded PDCP data PDUs, the one or more discarded PDCP data PDUs including the first PDCP data PDU, the second PDCP entity being a peer PDCP entity of the first PDCP entity for processing data received from the first device.

### Claim 2 (depends on 1)

The method of claim 1, the notifying the second PDCP entity of the second device comprising:
sending, by the first PDCP entity to the second PDCP entity, the COUNT information in a PDCP control PDU.

### Claim 3 (depends on 2)

The method of claim 2, the COUNT information indicating a first discarded COUNT (FDC) value, the FDC value being a smallest COUNT value among the one or more discarded COUNT values.

### Claim 4 (depends on 3)

The method of claim 3, the COUNT information further including a bitmap indicating additionally discarded COUNT values, the one or more discarded COUNT values including the FDC value and the additionally discarded COUNT values, each bit in the bitmap corresponding to a unique COUNT value among a sequence of contiguous COUNT values, the sequence of contiguous COUNT values immediately following the FDC value numerically and comprising the additionally discarded COUNT values, the each bit in the bitmap carrying either a first value indicating that a corresponding COUNT value is associated with a discarded PDCP data PDU or a second value indicating that the corresponding COUNT value is unassociated with any of the discarded PDCP data PDUs.

### Claim 5 (depends on 3)

The method of claim 3, the COUNT information further indicating a total number of additionally discarded COUNT values, the one or more discarded COUNT values including the FDC value and a number of contiguous COUNT values immediately following the FDC value numerically, the number being equal to the total number.

### Claim 6 (depends on 2)

The method of claim 2, the COUNT information indicating a last discarded COUNT (LDC) value and that any COUNT values smaller than the LDC value and having not been received yet, upon being notified, are to be considered as among the one or more discarded COUNT values, the LDC value being a largest COUNT value among the one or more discarded COUNT values.

### Claim 7 (depends on 2)

The method of claim 2, the COUNT information indicating a first resumed COUNT (FRC) value and that any COUNT values smaller than the FRC value and having not been received yet, upon being notified, are to be considered as among the one or more discarded COUNT values, the FRC value being associated with a second PDCP data PDU, the second PDCP data PDU being an earliest PDCP PDU to be transmitted to the second PDCP entity when the transmission to the second PDCP entity is resumed, and the FRC value being a smallest COUNT value used after the transmission to the second PDCP entity is resumed and being greater than any of the one or more discarded COUNT values.

### Claim 8 (depends on 2)

The method of claim 2, the COUNT information indicating a hyper frame number (HFN) value of a first resumed COUNT (FRC) value, the FRC value being associated with a second PDCP data PDU, the second PDCP data PDU being an earliest PDCP data PDU to be transmitted to the second PDCP entity when the transmission to the second PDCP entity is resumed, and the FRC value being a smallest COUNT value used after the transmission to the second PDCP entity is resumed and being greater than any of the one or more discarded COUNT values, and the HFN value being a value expressed by a pre-specified number of most significant bits of the FRC value.

### Claim 9 (depends on 1)

The method of claim 1, the first device being one of a user equipment (UE) or a base station, and the second device being the other of the UE or the base station.

### Claim 10 (depends on 1)

The method of claim 1, the first device and the second device being peer UEs.

### Claim 11

A method, comprising:
receiving, by a first packet data convergence protocol (PDCP) entity of a first device from a second PDCP entity of a second device, COUNT information related to one or more discarded COUNT values, the one or more discarded COUNT values respectively associated with one or more PDCP data protocol data units (PDUs) that have been discarded by the second PDCP entity, the second PDCP entity being a peer PDCP entity of the first PDCP entity for processing data for transmission to the first device;
receiving, by the first PDCP entity from the second PDCP entity, a PDCP data PDU;
processing, by the first PDCP entity, the PDCP data PDU to produce a PDCP service data unit (SDU) based on the COUNT information; and
delivering, by the first PDCP entity, the PDCP SDU to an associated upper layer.

### Claim 12 (depends on 11)

The method of claim 11, the COUNT information being received in a PDCP control PDU.

### Claim 13 (depends on 12)

The method of claim 12, the COUNT information indicating a first discarded COUNT (FDC) value, the FDC value being a smallest COUNT value among the one or more discarded COUNT values.

### Claim 14 (depends on 13)

The method of claim 13, the COUNT information further including a bitmap indicating additionally discarded COUNT values, the one or more discarded COUNT values including the FDC value and the additionally discarded COUNT values, each bit in the bitmap corresponding to a unique COUNT value among a sequence of contiguous COUNT values, the sequence of contiguous COUNT values immediately following the FDC value numerically and comprising the additionally discarded COUNT values, the each bit in the bitmap carrying either a first value indicating that a corresponding COUNT value is associated with a corresponding discarded PDCP PDU or a second value indicating that the corresponding COUNT value is unassociated with any of the discarded PDCP PDUs.

### Claim 15 (depends on 14)

The method of claim 14, further comprising:
updating, by the first PDCP entity, a state variable RX_NEXT of the first PDCP entity to be equal to a sum of one and the largest COUNT value among the one or more discarded COUNT values in response to determining that the sum is greater than an RX_NEXT value prior to the updating.

### Claim 16 (depends on 14)

The method of claim 14, further comprising:
updating, by the first PDCP entity, a state variable RX_DELIV of the first PDCP entity to be equal to a sum of one and the largest COUNT value among the one or more discarded COUNT values.

### Claim 17 (depends on 14)

The method of claim 14, further comprising:
updating, by the first PDCP entity, a state variable RX_DELIV of the first PDCP entity to be equal to a smallest COUNT value satisfying all of being greater than an RX_DELIV value prior to the updating, being greater than or equal to a sum of one and the largest COUNT value among the one or more discarded COUNT values, and a PDCP SDU associated with which has not been delivered to upper layer associated with the first PDCP entity yet and is still waited for.

### Claim 18 (depends on 13)

The method of claim 13, the COUNT information further indicating a total number of additionally discarded COUNT values, the one or more discarded COUNT values including the FDC value and a number of contiguous COUNT values immediately following the FDC value numerically, the number being equal to the total number indicated, the method further comprising:
determining, by the first PDCP entity, a largest COUNT value among the one or more discarded COUNT values to be equal to a sum of the FDC value and the total number indicated by the COUNT information.

### Claim 19 (depends on 12)

The method of claim 12, the COUNT information indicating a last discard COUNT (LDC) value, the LDC value being a largest COUNT value among the one or more discarded COUNT values.

### Claim 20 (depends on 12)

The method of claim 12, the COUNT information indicating a first resumed COUNT (FRC) value, the FRC value being associated with a second PDCP data PDU, the second PDCP data PDU being an earliest PDCP data PDU to be transmitted by the second PDCP entity upon being notified, and the FRC value being a smallest COUNT value to be used in transmitting a next PDCP data PDU by the second PDCP entity upon notifying the first PDCP entity, the method further comprising:
updating, by the first PDCP entity, a state variable RX_NEXT of the first PDCP entity to be equal to the FRC value indicated by the COUNT information in response to determining that the FRC value is greater than an RX_NEXT value prior to the updating.

### Claim 21 (depends on 12)

The method of claim 12, the COUNT information indicating a hyper frame number (HFN) value of a first resumed COUNT (FRC) value, the FRC value being associated with a second PDCP data PDU, the second PDCP data PDU being an earliest PDCP data PDU to be transmitted from the second PDCP entity upon being notified, and the FRC value being a smallest COUNT value to be used in transmitting a next PDCP data PDU by the second PDCP entity upon notifying the first PDCP entity.

### Claim 22 (depends on 11)

The method of claim 11, further comprising:
determining, by the first PDCP entity, that the one or more PDCP PDUs associated with the one or more discarded COUNT values are discarded.

### Claim 23 (depends on 11)

The method of claim 11, further comprising:
considering, by the first PDCP entity, the one or more PDCP PDUs associated with the one or more discarded COUNT values as if having been received and delivered to upper layer associated with the first PDCP entity.

### Claim 24 (depends on 11)

The method of claim 11, the first device being one of a user equipment (UE) or a base station, and the second device being the other of the UE or the base station.

### Claim 25 (depends on 11)

The method of claim 11, the first device and the second device being peer UEs.

### Claim 26

A first device comprising:
at least one processor; and
a non-transitory computer readable storage medium storing instructions that, when executed by the at least one processor, cause a first packet data convergence protocol (PDCP) entity of the first device to perform operations including:
receiving a PDCP service data unit (SDU) from an associated upper layer of the first PDCP entity;
associating a COUNT value with the PDCP SDU;
processing the PDCP SDU with the COUNT value to produce a first PDCP data protocol data unit (PDU);
determining a need to abandon transmission of the first PDCP data PDU;
discarding the first PDCP data PDU based on the determining; and
notifying a second PDCP entity of a second device about COUNT information related to one or more discarded COUNT values, the one or more discarded COUNT values being associated with one or more discarded PDCP data PDUs, the one or more discarded PDCP data PDUs including the first PDCP data PDU, the second PDCP entity being a peer PDCP entity of the first PDCP entity for processing data received from the first device.

### Claim 27

A first device comprising:
at least one processor; and
a non-transitory computer readable storage medium storing instructions that, when executed by the at least one processor, cause a first packet data convergence protocol (PDCP) entity of the first device to perform operations including:
receiving, from a second PDCP entity of a second device, COUNT information related to one or more discarded COUNT values, the one or more discarded COUNT values respectively associated with one or more PDCP data protocol data units (PDUs) that have been discarded by the second PDCP entity, the second PDCP entity being a peer PDCP entity of the first PDCP entity for processing data for transmission to the first device;
receiving, from the second PDCP entity, a PDCP data PDU;
processing the PDCP data PDU to produce a PDCP service data unit (SDU) based on the COUNT information; and
delivering the PDCP SDU to an associated upper layer without waiting for the one or more PDCP data PDUs associated with the one or more discarded COUNT values.
