Reliable transport offloaded to network devices

US12199888B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-12199888-B2
Application numberUS-202418425968-A
CountryUS
Kind codeB2
Filing dateJan 29, 2024
Priority dateFeb 3, 2021
Publication dateJan 14, 2025
Grant dateJan 14, 2025

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

Examples described herein relate to offload reliable transport management to a network interface device and store packets to be resent, based on received packet receipt acknowledgements (ACKs), into one or more kernel space queues that are also accessible in user space.

First claim

Opening claim text (preview).

The invention claimed is: 1. An apparatus comprising: at least one processor; at least one memory comprising instructions stored thereon, that if executed by the at least one processor, cause the at least one processor to: offload reliable transport management to a network interface device, wherein the reliable transport management is based on quick User Datagram Protocol (UDP) Internet Connections (QUIC) and wherein the network interface device is to perform header split to copy a packet header and a packet payload to different destinations and based on received packet receipt acknowledgements (ACKs), track packets to be resent, by access to one or more kernel space queues that are also accessible in user space. 2. The apparatus of claim 1 , wherein the at least one memory compris es instructions stored thereon, that if executed by the at least one processor, cause the at least one processor to: identify descriptors available for reuse into the one or more kernel space queues that are also accessible in user space. 3. The apparatus of claim 1 , wherein content stored in the one or more kernel space queues are also accessible in user space without copying from memory accessible to user space to a memory accessible kernel space. 4. The apparatus of claim 1 , wherein: a socket is to connect a service with a driver for the network interface device, the one or more kernel space queues are associated with the socket, and at least one of the one or more kernel space queues comprises a waiting queue for received packet receipt acknowledgements (ACKs). 5. The apparatus of claim 1 , wherein the one or more kernel space queues are based on an Address Family of an eXpress Data Path (AF_XDP) queue framework. 6. The apparatus of claim 1 , wherein: at least one of the one or more kernel space queues is to identify one or more packets for which one or more ACKs have been received. 7. The apparatus of claim 1 , wherein the at least one processor is to execute a service that is to request transmission of at least one packet that is subject to receipt of an ACK. 8. The apparatus of claim 1 , comprising the network interface device to transmit at least one packet based on a request from the at least one processor. 9. A non-transitory computer-readable medium comprising instructions stored thereon, that if executed by one or more processors, cause the one or more processors to: offload reliable transport management to a network interface device, wherein the reliable transport management is based on quick User Datagram Protocol (UDP) Internet Connections (QUIC) and wherein the network interface device is to perform header split to copy a packet header and a packet payload to different destinations. 10. The non-transitory computer-readable medium of claim 9 , comprising instructions stored thereon, that if executed by one or more processors, cause the one or more processors to: track packets to be resent, based on received packet receipt acknowledgements (ACKs), into one or more kernel space queues that are also accessible in user space, wherein the one or more kernel space queues that are also accessible in user space are to identify descriptors available for reuse. 11. The non-transitory computer-readable medium of claim 10 , wherein: a socket is to connect a service with a driver for the network interface device, the one or more kernel space queues are associated with the socket, and at least one of the one or more kernel space queues comprises a waiting queue for received packet receipt acknowledgements (ACKs). 12. The non-transitory computer-readable medium of claim 10 , wherein: the one or more kernel space queues are based on an Address Family of an express Data Path (AF_XDP) queue framework. 13. An apparatus comprising: a network interface device comprising circuitry to perform offloaded reliable transport for packet transmission based on a queue framework comprising one or more kernel space queues that are also accessible in user space, wherein the reliable transport is based on quick User Datagram Protocol (UDP) Internet Connections (QUIC) and wherein the circuitry is to perform header split to copy a packet header and a packet payload to different destinations. 14. The apparatus of claim 13 , wherein the one or more kernel space queues that are also accessible in user space are to track packets to be resent, based on received packet receipt acknowledgements (ACKs). 15. The apparatus of claim 13 , wherein: the network interface device is to re-transmit a packet based on non-receipt of an acknowledgement (ACK) of packet receipt. 16. The apparatus of claim 13 , wherein: at least one of the one or more kernel space queues is to identify at least one available descriptor that is available to associated with a received packet. 17. The apparatus of claim 13 , wherein the network interface device comprises circuitry to: based on receipt of a packet having a sequence number corresponding to a non-received packet sequence number, provide access to one or more packet payloads associated with one or more received packet sequence numbers. 18. The apparatus of claim 13 , wherein the network interface device comprises one or more of: a network interface controller (NIC), a smart NIC, an infrastructure processing unit (IPU), and/or a data processing unit (DPU). 19. The apparatus of claim 13 , comprising a server comprising at least one processor that is to execute a service that is to request transmission of at least one packet that is subject to receipt of an acknowledgement (ACK). 20. The apparatus of claim 13 , comprising a server comprising at least one processor that is to execute a service that is to process at least one payload of at least one packet associated with a received packet sequence number.

Assignees

Inventors

Classifications

  • by ensuring the integrity of packets received through redundant connections · CPC title

  • Resequencing · CPC title

  • H04L47/34Primary

    ensuring sequence integrity, e.g. using sequence numbers · CPC title

  • Arrangements for simultaneous transmit and receive, e.g. simultaneous reading/writing from/to the storage element · CPC title

  • implementing delay-aware scheduling · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US12199888B2 cover?
Examples described herein relate to offload reliable transport management to a network interface device and store packets to be resent, based on received packet receipt acknowledgements (ACKs), into one or more kernel space queues that are also accessible in user space.
Who is the assignee on this patent?
Intel Corp
What technology area does this patent fall under?
Primary CPC classification H04L47/34. Mapped technology areas include Electricity.
When was this patent published?
Publication date Tue Jan 14 2025 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 12 related publications on this page (citations in our corpus or others sharing the same primary CPC).