3GPP — the Third Generation Partnership Project — is easy to misunderstand. It sounds like a regulatory body, but it isn't. It sounds like a consortium of researchers, but that's not quite right either. It is, in the most accurate description, a sustained technical negotiation between the companies that build the world's wireless infrastructure, mediated by a formal process for converting engineering proposals into global standards.
The output of this process — the Technical Specifications that define LTE, 5G NR, and their successors — is what gets implemented in every smartphone, every base station, every IoT module deployed at scale. And embedded within those specifications, at every level from the physical layer to the core network, are the fingerprints of the companies whose engineers wrote the proposals that shaped them.
Standards are not discovered. They are negotiated. And negotiation leaves traces — in working group minutes, in technical proposals, and eventually in patent claims.
How a technical proposal becomes a standard
The process works roughly like this: a company's engineers identify a technical problem — say, how to efficiently allocate radio resources in a multi-user MIMO scenario — and develop a solution. They submit a technical proposal to the relevant 3GPP working group (RAN1, RAN2, SA2, and so on). The working group discusses, modifies, debates alternatives, and eventually either adopts the proposal, merges it with others, or rejects it. What gets adopted becomes part of the specification.
The company that submitted the winning proposal has, at this point, done something strategically important: they've contributed a technical solution that the entire industry is now obligated to implement. And if they've filed a patent on that solution — which most large contributors do, systematically — they now hold a Standard Essential Patent: a patent that cannot be designed around, because the standard itself mandates the behavior it covers.
The SEP landscape
The SEP ecosystem in telecom is enormous. Billions of dollars in licensing revenue flow annually through declarations of essentiality, FRAND (Fair, Reasonable, and Non-Discriminatory) licensing negotiations, and — when those negotiations fail — litigation. The companies with the largest declared SEP portfolios — Huawei, Qualcomm, Ericsson, Nokia, Samsung — have spent decades building positions through active participation in standards development.
Working with SEPs requires navigating two distinct technical layers simultaneously. The first is the standard itself: what does the specification say, and what technical behavior does it mandate? The second is the patent: what does the claim cover, and does the mandated behavior fall within that coverage? Both layers require genuine technical fluency — one in telecommunications engineering, one in patent claim construction.
Why this matters beyond telecom
The 3GPP model — where standards development and IP accumulation happen in parallel — is increasingly the norm in technology, not the exception. Wi-Fi, Bluetooth, video compression (HEVC, AV1, VVC), USB, display standards — all of these involve standards bodies where companies simultaneously shape technical outcomes and build IP portfolios around the decisions they influence.
Understanding how this works is not just useful for telecom analysts. It's a mental model for understanding how technical power consolidates in any industry where interoperability standards matter — which, in the connected world, is nearly all of them.