Retrieval

Series guide. This article is the bounded-memory thematic survey. Start with the development-history hub for the six-path map, read the ReKV note for the exact-archive baseline, and use the pipeline survey for the stage-by-stage architecture. A streaming Video-LMM has to make decisions before it knows which detail a future user will care about. ReKV avoids write-time eviction or compression by storing every generated visual KV block, then retrieves a small subset after the question is known. This does not recover unsampled pixels or information absent from those model states. Fixed-state methods make the opposite trade: they evict, merge, or summarize history during the stream so that memory no longer grows with video duration. ...

Series guide. This is the development-history hub for my streaming Video-LMM notes. For a stage-by-stage systems view, see the pipeline survey. For dataset and protocol details, see the benchmark index. The complete reading map is at the end of this article. Calling a model streaming no longer identifies one technical problem. One paper may process a causal video prefix but retain every historical KV block. Another may keep a fixed cache but permanently forget old evidence. A proactive assistant may know the user’s request before the stream begins, while a delayed question-answering system must decide what to preserve before any question is known. A benchmark may measure the age of remembered evidence without measuring whether the implementation can keep up with a live camera. ...

Paper: OASIS: On-Demand Hierarchical Event Memory for Streaming Video Reasoning PDF: CVPR 2026 Open Access Code: Solus-sano/OASIS Core Idea OASIS is a training-free external memory and agentic RAG system for streaming video. It organizes the past into an online event hierarchy, reasons from a small working context by default, and retrieves historical keyframes only when the MLLM decides that more evidence is needed. The method can be summarized as: short/medium visual working memory + an online tree of event summaries and keyframes + prompt-based history routing + planned-query retrieval. ...

Paper: WeaveTime: Streaming from Earlier Frames into Emergent Memory in VideoLLMs Preprint (earlier title: Stream from Earlier Frames): arXiv:2602.22142 PDF: CVPR 2026 Open Access Supplement: CVPR 2026 Supplementary Material Project: WeaveTime Code: zhangyl4/weavetime Series guide. PCDF bounds when and how much history is read, not how much ReKV-style history is stored. See the bounded-memory survey for the resource comparison and the development-history hub for the complete series. Core Idea WeaveTime can be summarized as: ReKV-style historical visual KV memory + temporal-order SFT + uncertainty-gated coarse-to-fine retrieval. ...

Paper: MuKV: Multi-Grained KV Cache Compression for Long Streaming Video Question-Answering Proceedings: CVPR 2026 Open Access Code: IMBALDY/MuKV Series guide. A fixed per-question read can still sit on a growing multi-grained archive. See the bounded-memory survey for that accounting and the development-history hub for the complete series. Background Long streaming VideoQA has a simple but painful constraint: the video keeps arriving, while the future user questions are unknown. KV-cache methods such as ReKV make this setting more practical. Instead of recomputing historical video tokens when a question arrives, the model can prefill the video stream in advance, store the visual KV cache, retrieve the relevant cache blocks later, and answer with much lower online cost. ...

Paper: ViG-RAG: Video-aware Graph Retrieval-Augmented Generation via Temporal and Semantic Hybrid Reasoning PDF: AAAI Proceedings PDF Code: AI-Researcher-Team/ViG-RAG Background Long-video RAG is harder than text RAG because video evidence is not just a list of documents. Useful information may be distributed across: visual scenes; speech transcripts; entities and events; temporal order; uncertain or noisy observations. If we simply split the video into independent chunks and retrieve by static text similarity, two problems appear: ...

Paper: AdaVideoRAG: Omni-Contextual Adaptive Retrieval-Augmented Efficient Long Video Understanding Code: xzc-zju/AdaVideoRAG Background Long-video understanding is hard because the useful evidence is sparse, long-range, and often spread across multiple modalities: visual content; speech; scene text; temporal relations. RAG is a natural fit here. Instead of feeding the whole video to the MLLM every time, the system can first build a searchable memory, retrieve relevant evidence, and then answer with a smaller context. But a fixed VideoRAG pipeline is not ideal. Easy questions may not need retrieval at all, while hard questions may need structured graph reasoning. ...

Series guide. This article is the stage-by-stage architecture map. Start with the development-history hub for the six research paths, and use the benchmark index for evaluation settings and protocols. Related papers: ReKV: Paper / Code StreamKV: Paper / Code InfiniPot-V: Paper / Code StreamMem: Paper LiveVLM: Paper / Code StreamingTOM: Paper / Code rLiVS: Paper / Code Core Question All of these papers are trying to solve the same systems problem: When a video stream keeps arriving, the user question is not known yet, and GPU memory is limited, how should a Video-LLM process the stream, compress memory, retrieve evidence, and generate an answer with low latency? ...

Paper: LiveVLM: Efficient Online Video Understanding via Streaming-Oriented KV Cache and Retrieval Code: sjtu-zhao-lab/LiveVLM Acceptance: DAC 2026 program Version note. This article follows the substantially revised arXiv v2 (2026-04-23) / DAC 2026 method: Vision Sink Bucketing and Position-agnostic KV Retrieval. The 2025 v1 used a different chunk-compression and FIFO mechanism; its results should not be mixed with the v2 design. Series guide. For the distinction between bounded VSB state and query-time PaR reads, see the bounded-memory survey. The development-history hub places LiveVLM in the complete series. ...

Paper: StreamKV: Streaming Video Question-Answering with Segment-based KV Cache Retrieval and Compression Code: sou1p0wer/StreamKV Background Streaming video question-answering (StreamingVQA) requires a model to continuously process incoming video, preserve useful historical context, and answer questions online with low latency. ReKV showed that video QA can be reformulated as retrieve relevant KV caches first, then answer with the retrieved KV. But it still has several weaknesses: It uses uniform segmentation, which may cut through semantic boundaries. It keeps essentially the whole historical visual context, so memory usage is still large. Its retrieval strategy is not flexible enough, especially when the useful information is distributed differently across layers. Core Idea StreamKV extends the ReKV line in two directions at the same time: ...