← Latest papers
💻 computer science

FLUID: From Ephemeral IDs to Multimodal Semantic Codes for Industrial-Scale Livestreaming Recommendation

FLUID is a novel, ID-free recommendation framework for industrial-scale livestreaming that replaces traditional item embeddings with discrete hierarchical multimodal codes (LUCID) to overcome persistent cold-start challenges, achieving significant performance gains across a global user base of over one billion.

Original authors: Xinhang Yuan, Zexi Huang, Anjia Cao, Xudong Lu, Zikai Wang, Penghao Zhou, Chang Liu, Wentao Guo, Qinglei Wang

Published 2026-05-22
📖 5 min read🧠 Deep dive

Original authors: Xinhang Yuan, Zexi Huang, Anjia Cao, Xudong Lu, Zikai Wang, Penghao Zhou, Chang Liu, Wentao Guo, Qinglei Wang

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Imagine you are running a massive, 24/7 global talent show. Every few minutes, a new act steps onto the stage, performs for about 45 minutes, and then vanishes forever. This is livestreaming.

Now, imagine you are the bouncer (the recommendation system) trying to decide which act to show to the next million people walking through the door.

The Old Problem: The "Name Tag" That Expires Too Fast

In most recommendation systems (like for movies or products), the system gives every item a unique ID number (like a permanent name tag). It learns what people like about that ID over months or years. If you watch a lot of "Action Movie #123," the system learns to show you more of it.

But in livestreaming, this breaks down. A live room only exists for 45 minutes.

  • By the time the system has learned enough about "Live Room #999" to recommend it well, the show is already over.
  • The room is always in a state of "cold start" (unknown).
  • The system keeps trying to memorize the ID, but the ID is useless the moment the stream ends. It's like trying to memorize a phone number for a party that ends before you finish dialing.

The Solution: FLUID (The "Content Translator")

The authors created a new system called FLUID. Instead of relying on the fleeting ID number, FLUID ignores the ID entirely and focuses on what the content actually looks and sounds like.

Here is how it works, using a simple analogy:

1. The "Universal Translator" (Cross-Domain Encoder)

Imagine a super-smart translator who has studied both short, polished movies (like TikTok videos) and long, messy live shows.

  • The Problem: Live shows are noisy and chaotic. If you only train the translator on live shows, they get confused.
  • The Fix: The authors trained their translator on both types of content. Because short videos are high-quality and plentiful, the translator learns the "language" of visuals and speech very well. It then applies this knowledge to the messy live shows.
  • The Output: Instead of a messy ID number, the translator converts every 2-minute chunk of a live show into a semantic code (a set of digital "tags" or "words" describing the content). They call this LUCID.
    • Example: Instead of "Room ID 555," the system sees: [Swimming, Pool, Blue Water, Laughing].

2. The "Stable Identity" vs. The "Flash Moment"

A live stream changes fast. One minute the host is chatting; the next, they are singing.

  • Slice-Level LUCID: This captures the current 2-minute moment (e.g., "Singing right now").
  • Room-Level LUCID: This captures the overall vibe of the whole show (e.g., "This is a comedy talk show").
  • The system uses both: the "flash moment" to catch immediate interest, and the "stable identity" to know who the host really is.

3. The "Late Fusion" Strategy (The Big Change)

In old systems, the ID number was the boss. The content description was just a sidekick. The system would look at the ID, ignore the description, and make a decision.

  • FLUID's Move: FLUID fires the ID. It removes the ID number from the candidate list completely.
  • Instead, it treats the "Slice Code" and "Room Code" as the main characters.
  • The Metaphor: Imagine the bouncer used to check a guest list (the ID). Now, the bouncer ignores the list entirely and just looks at the guest's outfit and behavior (the content codes) to decide if they fit the party.

4. The "Staged Warmup" (The Safety Net)

You can't just fire the ID overnight. The system is used to relying on it. If you pull the rug out, the whole building collapses.

  • Stage 1: Add the "Slice Code" (the current moment) alongside the old ID. Let the system get used to it.
  • Stage 2: Slowly turn down the volume on the old ID until it's silent.
  • Stage 3: Add the "Room Code" (the stable identity) to fill the gap left by the ID.
  • This ensures the system doesn't panic and keeps learning smoothly.

The Results: Why It Matters

When they tested this on a platform with over 1 billion users, the results were clear:

  • Better Recommendations: People watched more high-quality content (+0.55% more "Quality Watch Duration").
  • New Stars Found: New, unknown rooms got more views (+2.05% Cold-Start Views) because the system wasn't stuck on old, familiar IDs.
  • Happier Users: People stayed on the app longer (+0.05% Active Hours).

The Big Takeaway

The paper argues that for things that disappear quickly (like livestreams), trying to memorize their "names" (IDs) is a waste of time. Instead, you should teach the system to understand the content itself so well that it doesn't need the name tag at all. FLUID proves that when you stop relying on the ID, you can actually find better, fresher content for your users.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →