How Software Developers Keep Track of API Versions Automatically
A system that automatically tags software building blocks with version data to prevent developers from accidentally breaking code when updating operating systems.
Original patent title: “API lifecycle platform and version management”
A system that automatically tags software building blocks with version data to prevent developers from accidentally breaking code when updating operating systems. Granted to Microsoft Technology Licensing LLC in 2017 with 17 claims and 8 forward citations.
Key facts
Coverage
What does this patent actually cover?
This patent describes a way to automate the tracking of Application Programming Interfaces (APIs). APIs are the sets of rules that allow different software programs to talk to each other. The system attaches metadata—essentially digital labels—to specific parts of the API, such as structures or interfaces. These labels record exactly which version and platform introduced or changed a specific piece of code. When a developer builds a new version of the operating system, the system checks these labels against a set of rules to ensure that any changes don't break existing, already-compiled software.
The gap
What does this patent NOT cover?
- Does not cover manual version tracking where developers update documentation without automated metadata.
- Does not cover runtime API versioning that happens while the software is actively running.
- Does not cover general source code version control systems like Git or SVN.
- Does not cover API versioning logic that is not tied to specific operating system platforms.
These exclusions are unique to PatentBrief — derived from the actual claim language, not patent-office boilerplate.
What made this novel
The innovation lies in moving versioning rules into the build process itself, using metadata automatically extracted from description files, rather than relying on human developers to remember which API parts are safe to change.
Schematic visualization of the patent's claim structure. Hand-drawn diagrams in progress for each landmark patent.
Where you've seen this
Real-world examples
Microsoft Windows SDK development tools
Automated build pipelines for large-scale operating systems
Cross-platform software development kits
Why it matters
The bigger picture
Managing APIs across multiple operating system versions is a massive headache for companies like Microsoft. If an update changes a core API, it can crash thousands of third-party apps. This patent provides a formal, automated way to enforce 'backward compatibility,' which is essential for maintaining trust with developers who build on top of an OS.
Filed
June 7, 2013
Granted
November 28, 2017
Market context
Who's building on this
Companies in this space
Microsoft remains the primary entity utilizing these methods within their Windows development ecosystem. Other large-scale platform providers, such as Apple and Google, employ similar automated build-time checks to manage their own massive API surfaces, though their specific implementations may differ.
Market impact
This technology supports the stability of massive software ecosystems. By automating the enforcement of versioning rules, it reduces the likelihood of 'breaking changes' that frustrate developers, thereby helping maintain the long-term viability of complex operating system platforms.
Claim 1 — Plain English
What this patent covers
This patent describes a way to automate the tracking of Application Programming Interfaces (APIs). APIs are the sets of rules that allow different software programs to talk to each other. The system attaches metadata—essentially digital labels—to specific parts of the API, such as structures or interfaces. These labels record exactly which version and platform introduced or changed a specific piece of code. When a developer builds a new version of the operating system, the system checks these labels against a set of rules to ensure that any changes don't break existing, already-compiled software.
The clever bit
The innovation lies in moving versioning rules into the build process itself, using metadata automatically extracted from description files, rather than relying on human developers to remember which API parts are safe to change.
What it does not cover
- Does not cover manual version tracking where developers update documentation without automated metadata.
- Does not cover runtime API versioning that happens while the software is actively running.
- Does not cover general source code version control systems like Git or SVN.
- Does not cover API versioning logic that is not tied to specific operating system platforms.
Patent timeline
Application submitted to the patent office
Application published, typically 18 months after filing
Patent officially issued
PatentBrief Score
Impact Score
Strong
Citation count
19/40
Early citations
Claim breadth
11/20
Broad claimsclaimsThe numbered statements at the end of a patent that legally define what the inventor owns.Read more →
Recency
10/20
Granted 5–10 years ago
Assignee scale
20/20
Major company or institution
PatentBrief Impact Score — based on citation count, claim breadth, recency, and assignee scale. Not a legal assessment.
Heuristic Value Estimate
What this patent might be worth
$87K – $280K
Midpoint $175K · 7.0 yr remaining · industry ×1.6
Heuristic only — blends forward/backward citation counts, claim scope, time remaining, litigation history, and CPC-derived industry baseline. Real valuations need a professional appraisal.
The original legal language
Original claims
17 claims as filed with the patent office.
Concepts involved
Citations
Patent lineage
Cite this patent
Messmer, W., Osterman, L., & Rector, B. (2017). How Software Developers Keep Track of API Versions Automatically (U.S. Patent No. 9,830,146). U.S. Patent and Trademark Office. https://patentbrief.org/patent/us/9830146/visual-studio-code
Auto-generated from the patent record. Double-check author order and the issue date against the official USPTO document before submitting.
Embed
Add this patent to your site
Drop this plain-English patent card into any blog post or article — free, no signup. It always links back to the full breakdown here.
<div data-patentlens-widget data-patent-number="US9830146"></div> <script src="https://patentbrief.org/embed.js" async></script>
Stay in the loop
Get a weekly digest of new patents.
One email per week. No spam. Unsubscribe anytime.
Keep exploring
Related patents you should know
US 4683195 · 1987
How to Make Billions of Copies of a DNA Segment
This patent describes the Polymerase Chain Reaction (PCR), a method to rapidly create many copies of a specific piece of DNA or RNA, enabling its detection and analysis.
Cetus Corp
US 8697359 · 2014
How to Edit Genes in Human Cells Using an Engineered CRISPR System
This patent describes an engineered CRISPR-Cas9 system for precisely cutting DNA in eukaryotic cells to change how genes work, opening the door for gene editing in complex organisms.
Massachusetts Institute of Technology
US 7657849 · 2010
How the iPhone's Slide-to-Unlock Gesture Works
Apple's 2010 patent describes unlocking a device by dragging a specific graphical image across the touchscreen along a predefined path, a gesture that became iconic with the original iPhone.
Apple Inc
US 4733665 · 1988
How Doctors Implant a Permanent Stent Using a Balloon
This patent describes the method for placing a permanent, expandable wire mesh tube inside a blood vessel or other body tube using a balloon-tipped catheter to widen it and keep it open.
Expandable Grafts Partnership
US 4965188 · 1990
How to Make Many Copies of a DNA Piece with Heat
This patent describes the Polymerase Chain Reaction (PCR) method, a technique to make millions of copies of a specific DNA segment using a heat-resistant enzyme and repeated temperature changes.
Cetus Corp
US 4235871 · 1980
How to Encapsulate Active Materials in Lipid Bubbles Efficiently
This patent describes a method for trapping biologically active substances inside tiny, multi-layered fat bubbles called liposomes, using a specific water-in-oil emulsion and gel-forming process to improve how much material gets captured.
Individual
More to explore
More in Software & Internet
US 4405829 · 1983 · Massachusetts Institute of Technology
How RSA Public-Key Encryption Keeps Digital Messages Secret
US 6285999 · 2001 · Leland Stanford Junior University
How Websites Get Ranked by Importance
US 5960411 · 1999 · Amazon com Inc
How Amazon's One-Click Ordering Works for Online Purchases
US 7669123 · 2010 · Facebook Inc
Displaying Friends' Activities in a Social Network Feed
New to patents?
Common Questions
Frequently Asked Questions
What does How Software Developers Keep Track of API Versions Automatically cover?
A system that automatically tags software building blocks with version data to prevent developers from accidentally breaking code when updating operating systems.
Who owns patent US 9830146?
Microsoft Technology Licensing LLC owns this patent, granted in 2017.
When does this patent expire?
This patent is expected to expire on November 28, 2037, when the invention enters the public domain.
What is patent US 9830146 cited by?
This patent has been cited by 8 later patents that build on its ideas.
What problem does this patent solve?
Managing APIs across multiple operating system versions is a massive headache for companies like Microsoft. If an update changes a core API, it can crash thousands of third-party apps. This patent provides a formal, automated way to enforce 'backward compatibility,' which is essential for maintaining trust with developers who build on top of an OS.
What does this patent NOT cover?
Does not cover manual version tracking where developers update documentation without automated metadata.
Same assignee
More from Microsoft Technology Licensing LLC
Patent monitoring