← Latest papers
💻 computer science

A Survey on Complexity Measures of Pseudo-Random Sequences

This survey reviews four decades of research on various complexity measures for assessing the randomness of pseudo-random sequences, including linear, quadratic, and maximum-order complexities, and explores their relationships with other metrics like Lempel-Ziv, expansion, 2-adic, and correlation measures.

Original authors: Chunlei Li

Published 2026-04-15
📖 6 min read🧠 Deep dive

Original authors: Chunlei Li

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 trying to build a secure vault for your most valuable secrets. To do this, you need a master key that looks completely random—so random that no one can guess the next number in the sequence. This is the world of cryptography, and the "randomness" of these keys is everything.

This paper is a survey report written by Chunlei Li, a researcher from the University of Bergen. It's like a comprehensive guidebook that reviews the last 40 years of research on how to measure just how "random" a sequence of numbers (bits) really is.

Here is the breakdown of the paper using simple analogies:

1. The Problem: The Fake Randomness

In the digital world, computers aren't naturally random. They are like very fast, very predictable robots. If you tell a robot to "pick a number," it will always pick the same one if you start it the same way.

To make them act random, we use Pseudo-Random Bit Generators (PRBGs). Think of these as "randomness machines."

  • The Goal: The machine should produce a stream of bits (0s and 1s) that looks exactly like a coin flip.
  • The Danger: If the machine is too predictable, a hacker can figure out the pattern, guess the next bit, and break your encryption.

2. The Solution: Measuring "Complexity"

How do we know if a sequence is truly random or just a clever trick? We need a Complexity Meter. The paper reviews different types of meters used to test these sequences.

Think of a sequence of numbers as a recipe.

  • Low Complexity: The recipe is simple. "Add 1, then add 1, then add 1." (e.g., 1, 2, 3, 4...). Anyone can guess the next number. This is bad for security.
  • High Complexity: The recipe is a 50-page novel with no pattern. You have to read the whole thing to understand it, and you can't guess the next word without knowing the previous ones. This is good for security.

The paper focuses on three main types of "Complexity Meters":

A. Linear Complexity (The Simplest Test)

Imagine you are trying to predict the next number in a line of people.

  • The Test: Can you predict the next person just by looking at the immediate previous people in a straight line?
  • The Tool: This uses a Linear Feedback Shift Register (LFSR). Think of this as a simple machine with a few gears. If the gears are small, the machine is easy to reverse-engineer.
  • The Verdict: If the machine needed to generate the sequence is small, the sequence is weak. If it needs a huge machine, it's strong. This is the most famous test and is used in standard security checks.

B. Quadratic Complexity (The "Slightly Complicated" Test)

Sometimes, a sequence looks random to the simple machine but has a hidden pattern that requires a slightly more complex machine to crack.

  • The Test: Instead of just adding numbers, the machine is allowed to multiply them too. It's like upgrading from a basic calculator to a scientific one.
  • The Verdict: If a sequence can be generated by a machine that does simple math (multiplication included), it's still not random enough for high-security needs.

C. Maximum-Order Complexity (The "Ultimate" Test)

This is the hardest test. It asks: "What is the absolute smallest machine, of any kind (no matter how weird the math is), that can produce this sequence?"

  • The Test: Imagine a detective trying to find the shortest set of instructions to recreate a crime scene.
  • The Twist: The paper notes a funny paradox: A sequence can be mathematically complex (hard to generate) but statistically terrible (not random at all).
    • Analogy: Imagine a sequence that is 0, 0, 0, 0, 0, 1. It is very hard to generate because the machine has to remember to output five zeros and then a one. But it's obviously not random because it's just zeros!
    • The Lesson: High complexity doesn't always mean good randomness. You need a mix of high complexity and good statistical behavior (like having an equal number of 0s and 1s).

3. The "Other" Meters

The paper also mentions other ways to measure randomness, comparing them to the main three:

  • Lempel-Ziv Complexity: This is like a compression test. If you can zip up a file and make it tiny, the file had a lot of patterns (low randomness). If the file stays huge after zipping, it's very random.
  • 2-adic Complexity: This is a specialized test for machines that handle "carries" (like when you add 1 to 9 and get 10). It's a different flavor of math but checks the same thing.
  • Correlation Measures: This checks if the sequence has any "echoes." If you see a pattern repeat itself with a slight delay, the sequence is weak.

4. What Did the Author Find?

Chunlei Li summarizes that:

  1. Linear Complexity is the best understood. We know how to calculate it, how to build sequences with high complexity, and how to test them.
  2. Maximum-Order Complexity is getting there. We have good algorithms to calculate it, but the math is tricky.
  3. Quadratic Complexity and others are still a bit of a mystery. We have some tools, but we don't fully understand the "statistical behavior" (how they act on average) yet.

The Big Takeaway

Building a secure encryption key is like building a maze.

  • Linear Complexity checks if the maze has a simple, straight path.
  • Quadratic/Maximum-Order Complexity checks if there are hidden loops or secret tunnels.

The paper tells us that while we are getting better at designing mazes that are hard to solve (high complexity), we still need more research to ensure those mazes don't have obvious dead ends or boring patterns (statistical flaws).

In short: This paper is a map of the "Randomness Landscape," showing us which tools we have to measure security, which tools are rusty, and where we need to build new bridges for the future of cryptography.

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 →