What changed

The Federal Circuit affirmed § 101 invalidity for AR software claims tied to location-based content selection and rendering in NantWorks, LLC v. Niantic, Inc. The practical signal is narrow: conventional computer components, tiles, sensors, or asserted efficiency benefits do not supply an inventive concept when the core claim remains an abstract information-filtering idea.

For AI/IP teams, the opinion is not an AI-specific eligibility rule. It is a useful checkpoint for software portfolios where the claimed value may be expressed as choosing, ranking, routing, filtering, or displaying content based on inputs.

The eligibility hinge for software and AI-adjacent claims

The operational hinge is the gap between a useful information workflow and a claimed technical improvement. A claim may describe valuable product behavior—location-aware content, recommendation logic, content routing, or more efficient presentation—but that alone may not answer the § 101 problem if the implementation rests on conventional computing elements.

The source signal is especially relevant where a draft claim or asserted claim depends on:

  • selecting content based on user, location, sensor, or contextual data;
  • rendering selected content in an AR, mobile, or software environment;
  • describing efficiency or usability benefits without tying them to a claimed technical mechanism; or
  • naming common computing components as the implementation layer.

The review should therefore focus less on whether the feature is commercially important and more on whether the patent record explains what changed technically and where that change appears in the claims.

Review questions for invention intake and drafting

For pending AI, AR, recommendation, and content-routing applications, counsel can use the opinion as a prompt for a short eligibility review before filing, continuation strategy, or assertion analysis.

Ask:

  1. What is the asserted technical improvement?

Can the team describe the improvement as more than better information selection, filtering, or display?

  1. Where is the improvement in the claim?

Is the technical mechanism actually recited, or is it only described as an intended result or product benefit?

  1. Which elements are conventional?

Identify claim elements that are merely standard computing components, sensors, tiles, rendering steps, or environment descriptions.

  1. Are performance benefits tied to mechanism?

If the specification describes efficiency, latency, relevance, or presentation benefits, does it connect those benefits to a claimed technical arrangement rather than to the abstract workflow?

  1. Is the claim centered on information filtering?

If the claim’s core contribution is selecting which content to show, route, recommend, or render, assess whether the application has enough technical detail to support a narrower claim position.

  1. Does the specification support fallback positions?

Confirm whether the disclosure supports claims directed to concrete implementation details, not just broad functional outcomes.

Portfolio and assertion controls

A practical response is not to abandon software or AI-adjacent claims. It is to add a documented checkpoint.

For new filings, require the invention disclosure to identify the technical problem, the technical mechanism, and the claim elements that implement that mechanism. Avoid relying solely on product value statements such as improved relevance, efficient presentation, or better user experience.

For pending applications, review independent claims that mainly describe input collection, selection logic, and output rendering. Consider whether the record supports amendments that tie benefits to a specific technical implementation.

For continuations, use the continuation plan to preserve narrower technical positions where the original disclosure supports them. The NantWorks signal is most useful when applied early, before the portfolio is locked into broad information-processing language.

For assertion review, test the claim against the same record: what is the non-conventional technical contribution, and how will the patent owner explain it without relying on ordinary computing components or the desirability of the result?

Contract and diligence implications

This also belongs in IP diligence for AI and software transactions. When evaluating acquired patents, licensed portfolios, or indemnity positions, ask whether key assets depend on broad content-selection or rendering claims. If so, request the claim charts, prosecution history analysis, and technical-improvement narrative before assigning enforcement or freedom-to-operate value to those assets.

For product-side teams, the takeaway is documentation discipline. If engineers identify a genuine technical mechanism that improves a system, capture that evidence early. If the feature is primarily a rule for choosing, filtering, or presenting information, counsel should know that before investing in broad patent claims or assertion theories.

Caveat

This signal comes from a Federal Circuit opinion concerning AR/location-based software claims. It should not be treated as a new AI-specific doctrine or as a complete eligibility playbook. Its value is as a concrete review trigger for software claims whose inventive story may otherwise collapse into information filtering on conventional computing infrastructure.