# US 2019/0246310 A1 · Pdcp packet-based ddds frame transmission

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

- Number: US 2019/0246310 A1
- Document ID: US20190246310A1
- Status: Published application
- Kind: A1
- Application number: 16/299,389
- Filed: 2019-03-12
- Published: 2019-08-08
- Earliest claimed: 2018-04-06
- Assignees: Intel Corporation
- Applicants: Intel Corporation
- Inventors: Jaemin Han; Yujian Zhang; Sudeep K. Palat; Alexander Sirotkin
- Web page: https://patentgrep.com/patent/US20190246310A1

## CPC

- H04W 28/0263: {involving mapping traffic to individual bearers or channels, e.g. traffic flow template [TFT]}
- H04W 28/04: Error control
- H04W 80/02: Data link layer protocols
- H04W 88/085: {Access point devices with remote components}
- H04W 92/12: between access points and access point controllers
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

Systems and methods of providing feedback when a specific PDU is successfully delivered or transmitted are described. The node hosting PDCP entity indicates triggering of a DDDS frame from the remote corresponding node. Rather than immediately triggering transmission of a DDDS frame, the node hosting PDCP entity indicates triggering based on successful delivery of a PDU having a specific SN, as long as in-sequence delivery or transmission of PDUs up to the specific SN was successful. The DDDS frame is transmitted once the corresponding node determines that the PDU having the SN was successfully delivered or transmitted. After reporting by the DDDS frame, the QoS flow associated with the PDUs is remapped from a source DRB to a target DRB.

## Claims

### Claim 1

An apparatus of a node, the apparatus comprising:
processing circuitry arranged to:
determine, from a Downlink (DL) User Data Frame received from another node hosting a New Radio (NR) Packet Data Convergence Control (PDCP) entity, whether to report, based on a NR PDCP packet data unit (PDU) sequence number (SN), that a NR PDCP PDU having the NR PDCP PDU SN has been successfully delivered to a user equipment (UE);
determine, from feedback received from the UE in response to transmission of the NR PDCP PDU to the UE, that the NR PDCP PDU was successfully delivered to the UE; and
in response to a determination that the NR PDCP PDU was successfully delivered to the UE, generate, for transmission to the other node, a DL Data Delivery Status (DDDS) frame that indicates successful delivery of the NR PDCP PDU to the UE; and
a memory configured to store the NR PDCP PDU SN.

### Claim 2 (depends on 1)

The apparatus of claim 1, wherein to determine whether to report that the NR PDCP PDU has been successfully delivered to the UE, the processing circuitry is arranged to:
determine that the DL User Data Frame contains a report delivered parameter that indicates a presence of a DL report NR PDCP PDU SN parameter;
extract a SN of the DL report NR PDCP PDU SN parameter or a SN of the NR PDCP PDU; and
determine that the SN of the DL report NR PDCP PDU SN parameter or the SN of the NR PDCP PDU are the NR PDCP PDU SN.

### Claim 3 (depends on 2)

The apparatus of claim 2, wherein the report delivered parameter is provided in one of the first two octets of the DL User Data Frame.

### Claim 4 (depends on 3)

The apparatus of claim 3, wherein the report delivered parameter is provided in a fifth most significant bit of the one of the first two octets.

### Claim 5 (depends on 2)

The apparatus of claim 2, wherein the DL report NR PDCP PDU SN parameter is 3 octets provided between a discarded block size octet and padding in the DL User Data Frame.

### Claim 6 (depends on 1)

The apparatus of claim 1, wherein the other node is a central unit of a 5th generation NodeB (gNB) and the node is a distributed unit of the gNB.

### Claim 7 (depends on 6)

The apparatus of claim 6, wherein the central unit is remote from the distributed unit.

### Claim 8 (depends on 1)

The apparatus of claim 1, wherein the NR PDCP PDU is transmitted from the node to a remote radio head (RRH) for delivery to the UE.

### Claim 9 (depends on 1)

The apparatus of claim 1, wherein generation of the DDDS frame is dependent on successful delivery of the NR PDCP PDU and is not generated by polling indicated by the DL User Data Frame.

### Claim 10 (depends on 1)

The apparatus of claim 1, wherein the processing circuitry is arranged to generate the DDDS frame only when all PDCP PDU SNs up to the NR PDCP PDU SN have been successfully delivered in-sequence to the UE.

### Claim 11 (depends on 1)

The apparatus of claim 1, wherein the NR PDCP PDU is a last NR PDCP PDU of a to-be-remapped Quality of Service (QoS) flow.

### Claim 12 (depends on 1)

The apparatus of claim 1, wherein the processing circuitry comprises:
a baseband processor configured to encode transmissions to, and decode transmissions from, the other node.

### Claim 13

A non-transitory computer-readable storage medium that stores instructions for execution by one or more processors of a node, the one or more processors to configure the node to, when the instructions are executed:
receive a Downlink (DL) User Data Frame from another node hosting a New Radio (NR) Packet Data Convergence Control (PDCP) entity, an indication to trigger feedback to the other node indicating successful delivery of the specific NR PDCP PDU to a user equipment (UE),
receive a NR PDCP PDU from the other node;
transmit the NR PDCP PDU toward the UE;
determine that the NR PDCP PDU was successfully delivered to the UE based on feedback from the UE;
determine that the NR PDCP PDU is the specific NR PDCP PDU; and
in response to determining that the specific NR PDCP PDU has been successfully delivered, transmit to the other node, a DL Data Delivery Status (DDDS) frame that indicates successful delivery of the NR PDCP PDU to the UE.

### Claim 14 (depends on 13)

The medium of claim 13, wherein:
the specific NR PDCP PDU is determined by a NR PDCP PDU sequence number (SN) of the NR PDCP PDU, and
the instructions, when executed, further configure the node to determine whether to report that the specific NR PDCP PDU has been successfully delivered to the UE by:
determining that the DL User Data Frame contains a report delivered parameter that indicates a presence of a DL report NR PDCP PDU SN parameter;
extracting a DL report NR PDCP PDU SN of the DL report NR PDCP PDU SN parameter; and
determining that the DL report NR PDCP PDU SN and the NR PDCP PDU SN of the successfully delivered NR PDCP PDU are the same.

### Claim 15 (depends on 14)

The medium of claim 14, wherein:
the report delivered parameter is provided in a fifth most significant bit of one of the first two octets of the DL User Data Frame, and
the DL report NR PDCP PDU SN parameter is 3 octets provided between a discarded block size octet and padding in the DL User Data Frame.

### Claim 16 (depends on 13)

The medium of claim 13, wherein the other node is a central unit of a 5th generation NodeB (gNB) and the node is a distributed unit of the gNB that is remote from the distributed unit.

### Claim 17 (depends on 13)

The medium of claim 13, wherein the instructions, when executed, further configure the node to avoid triggering transmission of the DDDS frame based on polling indicated by the DL User Data Frame.

### Claim 18 (depends on 13)

The medium of claim 13, wherein the instructions, when executed, further configure the node to generate the DDDS frame only when all PDCP PDU SNs up to the NR PDCP PDU SN have been successfully delivered in-sequence to the UE.

### Claim 19

An apparatus of a central unit of a 5th generation NodeB (gNB), the apparatus comprising:
processing circuitry arranged to:
generate, for transmission to a distributed unit of the gNB, a Downlink (DL) User Data Frame that comprises:
a report delivered parameter that indicates a presence of a DL report New Radio (NR) Packet Data Convergence Control (PDCP) packet data unit (PDU) sequence number (SN) parameter in the DL User Data Frame, and
the DL report NR PDCP PDU SN parameter, which indicates a DL report NR PDCP PDU SN, and
decode a DL Data Delivery Status (DDDS) frame from the distributed unit that indicates in-sequence successful delivery of PDCP PDUs having SN up to the DL report NR PDCP PDU SN to a user equipment (UE); and
a memory configured to store the DL report NR PDCP PDU SN.

### Claim 20 (depends on 19)

The apparatus of claim 19, wherein:
the report delivered parameter is provided in a fifth most significant bit of one of the first two octets of the DL User Data Frame, and
the DL report NR PDCP PDU SN parameter is 3 octets provided between a discarded block size octet and padding in the DL User Data Frame.
