PDCP STATUS REPORTS USING SEQUENCE NUMBERS OR SEQUENCE NUMBER OFFSETS

• US 20180241509A1
• Filed: 12/26/2015
• Published: 08/23/2018
• Est. Priority Date: 08/21/2015
• Status: Active Grant

• Current Assignee: Intel Corporation
• Original Assignee: Intel IP Corporation (Intel Corporation)
• Inventors: Phuyal, Umesh, Kugler, Martin, Himayat, Nageen, Sirotkin, Alexander
• Granted Patent: US 10,554,340 B2
• Time in Patent Office: Days
• CPC Class Codes: H04L 1/1614 using bitmaps
• CPC Class Codes: H04L 1/1628 List acknowledgements, i.e. the acknowledgement message consisting of a list of identifiers, e.g. of sequence numbers H04L1/1614 takes precedence
• CPC Class Codes: H04L 47/34 ensuring sequence integrity, e.g. using sequence numbers
• CPC Class Codes: H04W 28/04 Error control
• CPC Class Codes: H04W 28/082 among bearers or channels
• CPC Class Codes: H04W 72/12 Wireless traffic scheduling
• CPC Class Codes: H04W 84/12 WLAN [Wireless Local Area Networks]

Abstract

A user equipment device (UE) may create efficient Packet Data Convergence Protocol (PDCP) status reports. The UE may receive PDCP packets from multiple radio access technologies (RATs) using the same bearer or same RAT using split bearers. The UE may identify packets that the UE should have received but did not, and may create a status report based on the sequence numbers (SNs) of the packets that the UE failed to receive or based on the SNs of the successful packets. The report may include the SNs of the packets, in addition to a bit-length of the SNs and/or a starting point of the SNs in the status report. Alternatively, the report may include the SN of a first packet that the UE failed to receive and offset values (relative to the SN of the first packet) for the other packets that the UE failed/succeed to receive.

Claims

1. A communication device comprising circuitry to:

receive packets, corresponding to a single radio bearer, from network devices corresponding to distinct radio access technologies (RATs);

identify, based on the packets, sequence numbers (SNs) of missed packets that were not received by the device;

create, based on the SNs, a report that identifies the missed packets; and

communicate the report to one of the network devices.

2. The communication device of claim 1, wherein, to create the report, the circuitry is to:

include each of the SNs in the report.

3. The communication device of claim 2, wherein, to create the report, the circuitry is to:

indicate, in the report, a bit length of each of the SNs.

4. The communication device of claim 2, wherein, to create the report, the circuitry is to:

indicate, in the report, a start location of each of the SNs.

5. The communication device of claim 1, wherein, to create the report, the circuitry is to:

determine a number of packets between a first packet of the missed packets and a last packet of the missed packets,

include a SN of the first packet in the report, and

indicate a number of packets between the first packet and each of a remainder of missed packets.

6. The communication device of claim 5, wherein, to create the report, the circuitry is to:

determine, based on the number of packets between the first packet of the missed packets and a last packet of the missed packets, a number of bytes required to represent the number of packets between the first packet and each of the remainder of the missed packets, and

for each of the remainder of the missed packets, use the required number of bytes to indicate the number of packets between the first packet and each of the remainder of the missed packets.

7. The communication device of claim 1, wherein the circuitry is to:

determine a value representing a number of received packets relative to a number of missed packets;

determine whether the value exceeds a preselected threshold;

when the value exceeds the preselected threshold,

identify the missed packets by including, in the report, only the SNs of the received packets; and

when the value does not exceed the preselected threshold,

identify the missed packets by including, in the report, only the SNs of the missed packets.

8. A user equipment device (UE), comprising:

an antenna to communicate with a wireless telecommunications network; and

circuitry to;

receive, from a wireless telecommunications network, a plurality of Packet Data Convergence Protocol (PDCP) packets, associated with one radio bearer, via a plurality of disparate radio access technologies;

identify at least one PDCP packet that should have been received, by the UE, with the plurality of PDCP packets but was not;

create a PDCP status report that includes a sequence number (SN) of the at least one PDCP packet;

communicate the PDCP status report to the wireless telecommunications network.

9. The UE of claim 8, wherein:

the plurality of disparate RATs includes an evolved Node B (eNB) of the wireless telecommunications network and an access point (AP) of a wireless local area network (WLAN), and

the PDCP status report is communicated to the eNB.

10. The UE of claim 8, wherein, to create the PDCP status report, the circuitry is to:

indicate, within the PDCP status report, a protocol data unit (PDU) type describing the PDCP status report as at least one of;

a PDCP status report that includes one SN for each of the at least one PDCP packet;

a PDCP status report that includes at least one reserved bit to indicate a start location, within the PDCP status report, of the at least one SN;

a PDCP status report with 12-bit SNs;

a PDCP status report with 15-bit SNs;

a PDCP status report with SNs that are greater than 15 bits;

or

a PDCP status report with SN offset values.

11. The UE of claim 8, wherein:

the at least one PDCP packet includes multiple PDCP packets, and

to create the PDCP status report, the circuitry is to;

include, in a first missing SN field of the PDCP status report, an SN of a first PDCP packet, of the multiple PDCP packets.

12. The UE of claim 11, wherein, to create the PDCP status report, the circuitry is to:

include SNs for each of a remainder of the multiple PDCP packets in subsequent fields of the PDCP status report.

13. The UE of claim 11, wherein, to create the PDCP status report, the circuitry is to:

identify offset values, corresponding to a difference between the SN of the first PDCP packet and each SN of a remainder of the multiple PDCP packets, and

include the offset values in the PDCP status report.

14. The UE of claim 13, wherein, to create the PDCP status report, the circuitry is to:

determine a number of bits required to represent each of the offset values,

define each of the offset values using the number of bits determined, and

indicate, in the PDCP status report, the number of bits required to represent each of the offset values.

15. A non-transitory computer readable medium containing program instructions for causing one or more processors to:

receive packets, corresponding to a single radio bearer, from network devices corresponding to distinct radio access technologies (RATs);

identify, based on the packets, sequence numbers (SNs) of missed packets that were not received by the device;

create, based on the SNs, a report that identifies the missed packets; and

communicate the report to one of the network devices.

16. The non-transitory compute readable medium of claim 15, wherein, to create the report, the instructions cause the one or more processors to:

include each of the SNs in the report.

17. The non-transitory compute readable medium of claim 16, wherein, to create the report, the instructions cause the one or more processors to:

indicate, in the report, a bit length of each of the SNs.

18. The non-transitory compute readable medium of claim 16, wherein, to create the report, the instructions cause the one or more processors to:

indicate, in the report, a start location of each of the SNs.

19. The non-transitory compute readable medium of claim 15, wherein, to create the report, the instructions cause the one or more processors to:

determine a number of packets between a first packet of the missed packets and a last packet of the missed packets,

include a SN of the first packet in the report, and

indicate a number of packets between the first packet and each of a remainder of missed packets.

20. The non-transitory compute readable medium of claim 15, wherein, to create the report, the instructions cause the one or more processors to:

determine, based on the number of packets between the first packet of the missed packets and a last packet of the missed packets, a number of bytes required to represent the number of packets between the first packet and each of the remainder of the missed packets, and

for each of the remainder of the missed packets, use the required number of bytes to indicate the number of packets between the first packet and each of the remainder of the missed packets.

21. A user equipment device (UE), comprising:

an antenna to communicate with a wireless telecommunications network; and

circuitry to;

receive, from a wireless telecommunications network, a plurality of Packet Data Convergence Protocol (PDCP) packets, associated with one radio bearer, via split bearers of the same radio access technology;

identify at least one PDCP packet that should have been received, by the UE, with the plurality of PDCP packets but was not;

create a PDCP status report that includes a sequence number (SN) of the at least one PDCP packet;

communicate the PDCP status report to the wireless telecommunications network.

22. The UE of claim 21, wherein, to create the PDCP status report, the circuitry is to:

indicate, within the PDCP status report, a protocol data unit (PDU) type describing the PDCP status report as at least one of;

a PDCP status report that includes one SN for each of the at least one PDCP packet;

a PDCP status report that includes at least one reserved bit to indicate a start location, within the PDCP status report, of the at least one SN;

a PDCP status report with 12-bit SNs;

a PDCP status report with 15-bit SNs;

a PDCP status report with SNs that are greater than 15 bits;

or

a PDCP status report with SN offset values.

23. The UE of claim 21, wherein:

the at least one PDCP packet includes multiple PDCP packets, and

to create the PDCP status report, the circuitry is to;

include, in a first missing SN field of the PDCP status report, an SN of a first PDCP packet, of the multiple PDCP packets.