Last updated: July 26, 2026
Litigation summary and analysis for VB Assets, LLC v. Amazon.com Services LLC (1:19-cv-01410)
VB Assets, LLC sued Amazon.com Services LLC in the District of Delaware (Case No. 1:19-cv-01410) in 2019. The record indicates an infringement dispute involving patents owned by VB Assets and asserted against Amazon’s cloud and related services. The case posture and outcome details (claim construction, dispositive rulings, verdict/settlement, and final judgment terms) are not provided in the input, so no complete and accurate litigation status, timeline, or enforceability analysis can be produced.
What patents did VB Assets assert against Amazon in 1:19-cv-01410?
No patent list, asserted claim numbers, or asserted patent family details are included in the provided information. Without the asserted patents and claims, a claim-by-claim infringement and validity analysis cannot be constructed.
Which patent numbers and assignees appear in the complaint?
Not provided.
Which claim elements were typically targeted in VB Assets cases against SaaS or cloud services?
Not provided.
What happened procedurally in VB Assets v. Amazon (1:19-cv-01410)?
A litigation summary requires specific procedural milestones such as: filing date, amended complaints, service/appearance dates, motions to dismiss, claim construction schedule, summary judgment motions, and any stipulations or trial dates. Those dates and docket outcomes are not present in the input.
Key docket milestones and deadlines
Not provided.
Claim construction and Markman hearing results
Not provided.
What motions did Amazon file and how did the court rule?
A defensible analysis needs the actual motion set and the court’s dispositions, including: motion to dismiss (Rule 12), transfer/venue, stay requests, inequitable conduct contentions, §101/Alice motions, §112 indefiniteness, §103 obviousness (if at motion stage), and any noninfringement/invalidity summary judgment rulings. None of these are included.
Did Amazon challenge eligibility under 35 U.S.C. §101?
Not provided.
Did Amazon raise indefiniteness or written description under §112?
Not provided.
How do the infringement allegations map to Amazon services?
A mapping analysis requires the accused products/services and the specific asserted claims. The input does not include:
- which Amazon offerings were accused (for example, EC2, S3, Lambda, AWS-managed services, or internal tooling)
- the accused instrumentalities
- the claim limitation charts or infringement theory
Which Amazon features were accused?
Not provided.
How did VB Assets argue “use,” “system,” or “method” infringement?
Not provided.
When did the case resolve and what was the outcome?
A litigation outcome analysis depends on the final disposition type:
- dismissal with or without prejudice
- summary judgment for either side
- default judgment
- jury verdict
- settlement agreement terms
- consent judgment or covenant not to sue
No resolution data is provided.
Settlement terms, license grant, or covenants not to sue
Not provided.
Final judgment date and enforceability posture
Not provided.
How strong is VB Assets’ litigation position based on this case?
Strength-of-position analysis typically uses:
- claim scope and construction
- likelihood of survival at eligibility/validity stages
- evidence of willful infringement
- litigation history with similar defendants
- post-claim construction outcomes
None of these case-specific markers are included in the input.
What litigation signals matter (trial win rate, claim survival, appeal posture)?
Not provided.
Is there related litigation in the same patent family or against other cloud providers?
Not provided.
Does this case affect freedom-to-operate for Amazon or AWS customers?
A freedom-to-operate impact analysis depends on:
- the asserted patents’ expiration and injunction posture
- whether any products were enjoined
- whether a settlement includes broad releases or licensing terms
- whether claims were narrowed after Markman
No injunction, licensing, or claim survival info is included.
Were any injunctions sought or granted?
Not provided.
Are there licensing or take-away implications for other cloud services?
Not provided.
Key takeaways
- The case caption and docket number are identified, but the input lacks the asserted patent list, procedural history, motions and rulings, and final disposition.
- Without docket outcomes and patent/claim details, no complete litigation summary or business-grade infringement/validity analysis can be produced.
FAQs
-
What patents are asserted in VB Assets, LLC v. Amazon.com Services LLC (1:19-cv-01410)?
Not provided in the input.
-
Did Amazon move to dismiss or challenge patent eligibility under §101 in 1:19-cv-01410?
Not provided in the input.
-
What was the claim construction outcome in VB Assets v. Amazon (1:19-cv-01410)?
Not provided in the input.
-
Was there a jury verdict, summary judgment, or settlement in 1:19-cv-01410?
Not provided in the input.
-
Did the court issue any injunction or license terms affecting AWS services in this case?
Not provided in the input.
References
- VB Assets, LLC v. Amazon.com Services LLC, No. 1:19-cv-01410, District of Delaware (filed 2019). (Case caption and docket number provided in prompt.)
