Samsung · Filed Apr 29, 2026 · Published Oct 15, 2026

Samsung Files Patent for Keeping AI Chatbots Quick When Many People Ask at Once

When a chatbot server runs out of memory, somebody's answer has to wait. Samsung's patent application lays out a cost formula for deciding whose.

A server juggles incoming questions from multiple users by dividing its fast memory into manageable blocks to speed up responses. Drawing from patent filing US 2026/0319838 A1.
A server juggles incoming questions from multiple users by dividing its fast memory into manageable blocks to speed up responses.
See all 14 drawings from this filing ↓
Publication number US 2026/0319838 A1 US20260319838A1
Applicant SAMSUNG ELECTRONICS CO., LTD.
Filing date Apr 29, 2026
Publication date Oct 15, 2026
Inventors Wooyeon LEE, Youri JEONG, Taegeon UM, Jeongho SHIN
US classification 718/102
Status when we published Waiting for an examiner (Jun 10, 2026)
Parent application is a Continuation of PCTKR2026095576 (filed 2026-04-06)
Document 20 claims

What Samsung's AI request-juggling patent does

You type a question into an AI chatbot and the answer stalls halfway through a sentence. Somewhere, a server is juggling your request along with many others from strangers, and it has run out of room on its graphics chip to hold everyone's work at once.

Samsung's patent application describes a way to decide who gets bumped. The server moves a paused conversation's working notes out to slower, roomier memory, then brings them back when it's that person's turn. The key is picking the right conversation to pause, by weighing how long the move takes, how much it slows everyone else, and how much more room that conversation will need soon.

The moving also happens in the background while the chip keeps writing answers, so nobody sits waiting for the shuffle.

From the filing · CLAIM 1
… performing swap cost-aware scheduling, wherein the generating of the response to each of the plurality of requests comprises generating tokens that constitute the response to each of the plurality of requests through a decoding operation managed by a scheduler …

Translation: The system manages heavy traffic by carefully calculating the cost of moving data in and out of memory.

How the server picks what to pause and resume

A chatbot server keeps each conversation's running context in a KV cache (a stored copy of the text so far, so the model doesn't re-read everything for every new word). That cache lives in blocks of graphics chip (GPU) memory, and the chip only has so many. The claims cover a scheduler that, at every step of generating tokens (the word-sized pieces that make up a reply), decides which paused request to bring back (swap in) and which running request to push out to ordinary CPU memory (swap out).

The decision runs in a set order:

  • Pick a paused request to swap in, scored by how long the transfer takes, how long it has waited, its remaining processing time, and the latency target (the response time the service promises).
  • Count the memory blocks needed for the running requests plus that one.
  • If free blocks fall short, score each running request's swap-out cost: transfer delay, lost overall speed, and how much memory it will want later.
  • Swap out the lowest-cost request, switch contexts, and keep generating tokens.

The weights on those three costs shift with how busy the server is and how full its memory is.

The dependent claims add extras. Swaps can run in the background, interleaved with token generation. Only part of a request may be swapped out, since blocks already copied to CPU memory can simply be dropped. And a new request can get a partial prefill (starting its prep work on just a slice) when only a few free blocks remain. The filing's example is a request needing five blocks when three are free.

From the filing · THE ABSTRACT
… determining a request to be swapped out from among the requests being executed, based on the swap-out cost, switching contexts by performing swap-in and swap-out …

Translation: It decides which user tasks to temporarily pause to free up space for incoming questions.

What this means for waiting on AI answers

If you use AI chatbots, the practical stake is how long you wait when the service is busy. The filing says its goal is to cut delays and make better use of limited chip memory, two things every large chatbot service has to balance. A smarter way to decide whose work gets parked could mean fewer stalls mid-answer when many people are asking at once.

The other beneficiary is whoever runs the servers. GPU memory is one of the scarcest and priciest parts of serving an AI model, so squeezing more requests into the same hardware matters to the people paying for it. The filing describes this as server-side software and names no specific Samsung product, so treat it as infrastructure work for now.

Samsung's 61st filing we've tracked since June in the AI chip wars builds on ideas like keeping chips from going idle and moving data with light.

Editorial take

The problem here is real and expensive. AI chatbots run on chips with a fixed amount of fast memory, and every extra user competes for it. When memory runs short, someone's answer slows down. Anyone who has watched a chatbot crawl at a busy hour has felt the result.

Samsung's fix matches that problem well: a bookkeeping formula that weighs the price of every move before making it, instead of simply bumping whoever arrived last. It is a sensible, narrow answer to a narrow, costly problem, and it does not try to be more than that.

The text we read includes no measured results, so how much waiting it would save is unknown. As a document, it reads as competent server plumbing: useful if it works, and invisible to you if it does.

Get our take in your Top Stories

Liked this breakdown? Add Patentlyze as a preferred source on Google, and our plain-English take shows up more often in your Top Stories the next time Samsung patent news breaks.

There are more where this came from

We read every patent application Big Tech publishes and send you the ones worth knowing. Plain English, free, every week.

The drawings

14 drawing sheets from US 2026/0319838 A1 · click any drawing to enlarge

Managing memory for incoming user requests, drawing sheet 1 from US 2026/0319838 A1
Sheet 1 Managing memory for incoming user requests
Computer server components, drawing sheet 2 from US 2026/0319838 A1
Sheet 2 Computer server components
Steps for generating quick text responses, drawing sheet 3 from US 2026/0319838 A1
Sheet 3 Steps for generating quick text responses
How the server swaps active data, drawing sheet 4 from US 2026/0319838 A1
Sheet 4 How the server swaps active data
Memory state tracking stages, drawing sheet 5 from US 2026/0319838 A1
Sheet 5 Memory state tracking stages
Memory swapping and data flow stages, drawing sheet 6 from US 2026/0319838 A1
Sheet 6 Memory swapping and data flow stages
Calculating cost to offload memory, drawing sheet 7 from US 2026/0319838 A1
Sheet 7 Calculating cost to offload memory
Deciding when to bring memory back, drawing sheet 8 from US 2026/0319838 A1
Sheet 8 Deciding when to bring memory back
Show the other 6 sheets
Samsung Files Patent for Keeping AI Chatbots Quick When Many People Ask at Once patent drawing, sheet 9
Sheet 9
Samsung Files Patent for Keeping AI Chatbots Quick When Many People Ask at Once patent drawing, sheet 10
Sheet 10
Samsung Files Patent for Keeping AI Chatbots Quick When Many People Ask at Once patent drawing, sheet 11
Sheet 11
Samsung Files Patent for Keeping AI Chatbots Quick When Many People Ask at Once patent drawing, sheet 12
Sheet 12
Samsung Files Patent for Keeping AI Chatbots Quick When Many People Ask at Once patent drawing, sheet 13
Sheet 13
Samsung Files Patent for Keeping AI Chatbots Quick When Many People Ask at Once patent drawing, sheet 14
Sheet 14
Browse all the drawings 14 drawing sheets
Patent filing page

Source. Full patent text and figures from the official USPTO publication PDF.
Reader comments

Be the first to weigh in

Start the discussion

Real name or a handle, either is fine. Comments are read by a person before they appear, so allow a little time. Keep it about the filing.