Litigation Details for Amdocs (Israel) Limited v. Openet Telecom, Inc. (Fed. Cir. 2014)

« Back to Dashboard

Amdocs (Israel) Limited v. Openet Telecom, Inc. (Fed. Cir. 2014)

Docket		Date Filed	2014-12-05
Court	Court of Appeals for the Federal Circuit	Date Terminated	2016-11-01
Cause		Assigned To
Jury Demand		Referred To
Patents	10,004,750
Link to Docket	External link to docket

Details for Amdocs (Israel) Limited v. Openet Telecom, Inc. (Fed. Cir. 2014)

Date Filed	Document No.	Description	Snippet	Link To Document
2014-12-05				External link to document

Amdocs (Israel) Limited v. Openet Telecom, Inc. | 15-1180 Litigation Summary and Patent Analysis

Last updated: August 29, 2026

Amdocs prevailed at the Federal Circuit in a major patent-eligibility appeal involving software for collecting, processing, enhancing, and storing telecommunications network-usage data. The court reversed the Eastern District of Virginia’s summary judgment that all four asserted patents were invalid under 35 U.S.C. § 101. The Federal Circuit held that the claims, viewed as ordered combinations, recited a specific distributed architecture that provided an inventive solution to a telecommunications-network problem. The decision did not determine infringement, damages, claim construction beyond the eligibility issue, or validity under §§ 102, 103, or 112. [1]

What was Amdocs v. Openet about?

Amdocs sued Openet over software used by telecommunications carriers to process network-accounting information. The accused technology collected usage data from network devices, consolidated information from multiple sources, enhanced the data, and stored or processed it for billing, accounting, and network-management purposes.

The dispute involved four Amdocs patents:

Patent	General subject matter	Federal Circuit result
U.S. Patent No. 6,836,797	Processing network-usage information using a distributed architecture	Claims held patent-eligible
U.S. Patent No. 6,947,984	Collecting and processing network-usage information	Claims held patent-eligible
U.S. Patent No. 7,412,510	Network-accounting data processing	Claims held patent-eligible
U.S. Patent No. 7,631,065	Generating consolidated records for network services	Claims held patent-eligible

Amdocs alleged that Openet’s telecommunications software infringed claims covering systems and methods for gathering network data, combining data associated with multiple services, applying enhancement functions, and storing the resulting information.

Which patents did Amdocs assert against Openet?

The asserted patent family addressed related telecommunications billing and network-accounting functions. The Federal Circuit analyzed representative claims from each patent rather than treating the claims as a single undifferentiated group.

U.S. Patent No. 6,836,797

The ’797 patent concerned processing network-usage information through components that gathered, enhanced, and stored data. The claims required a distributed architecture in which processing functions were allocated among different network components.

U.S. Patent No. 6,947,984

The ’984 patent addressed collection of network-usage information from network devices. The claimed system gathered data, filtered or aggregated it, enhanced the information, and stored it for later use.

U.S. Patent No. 7,412,510

The ’510 patent covered processing network-accounting information from multiple sources. Its claims required collecting usage records, consolidating information, and processing the resulting data within the claimed architecture.

U.S. Patent No. 7,631,065

The ’065 patent addressed generating a single record reflecting multiple services used by a customer. The claimed system used network-usage records, an enhancement component, a database, and a central application server.

The patents were directed to telecommunications infrastructure rather than a pharmaceutical product. There was no FDA approval, Orange Book listing, Paragraph IV certification, biosimilar pathway, or Hatch-Waxman exclusivity issue in this case.

What did the district court decide?

The district court granted Openet summary judgment that the asserted claims were invalid under § 101. The court treated the claims as directed to the abstract idea of collecting, organizing, and processing information.

The district court applied the two-step framework later formalized in Alice Corp. v. CLS Bank International:

1. Determine whether the claims are directed to an abstract idea, law of nature, or natural phenomenon.
2. If so, determine whether the claim elements, individually or as an ordered combination, add an inventive concept sufficient to transform the claim into a patent-eligible application. [2]

The district court concluded that the claims were directed to the abstract idea of processing information and that the recited computer components did not supply an inventive concept. It therefore found the claims ineligible without reaching infringement or other invalidity defenses.

Why did the Federal Circuit reverse the § 101 judgment?

The Federal Circuit reversed because it found that the claims were directed to a specific technological solution rather than merely to the abstract idea of collecting and manipulating data.

The appellate court emphasized four technical characteristics.

The claims required a distributed architecture

The claimed systems did not merely recite a result such as “process network data.” They required particular components performing defined functions within a distributed telecommunications environment.

The Federal Circuit focused on the interaction among:

• Network devices that generated usage information;
• Gathering components that collected the information;
• Enhancement components that added context or additional data;
• Databases or storage elements;
• Central application servers or processing systems.

The court concluded that this arrangement imposed meaningful structural and functional limitations.

The claims addressed a telecommunications-network problem

Amdocs’ patents addressed the practical problem of processing large volumes of network-usage data from multiple sources. The claimed architecture allowed data to be enhanced and processed close to the source before being transmitted to a centralized system.

The Federal Circuit characterized this as a technological improvement in network accounting and data processing. The claims were not directed solely to a business practice implemented on generic computers.

The ordered combination mattered

The Federal Circuit rejected an element-by-element analysis that disregarded the combined architecture. Even if individual components such as databases, servers, and processors were known, the court held that the claimed combination could supply the inventive concept.

The decision stated that the patents disclosed a “distributed architecture” with “specialized components” that provided a technological solution to the problem of massive data processing. [1]

The specification supported the technical character of the claims

The patent specifications described how the components operated together. The Federal Circuit used that disclosure to assess whether the claims recited a genuine technological improvement.

This approach distinguished the case from claims that merely instruct a user to apply an abstract method on conventional computing equipment.

How did Amdocs compare with Alice, DDR Holdings, and other § 101 cases?

Case	Core issue	Result	Relevance to Amdocs
Alice Corp. v. CLS Bank	Financial transactions implemented on generic computers	Claims ineligible	Generic computer implementation is insufficient
DDR Holdings LLC v. Hotels.com	Solving a specific Internet-centric problem	Claims eligible	Amdocs similarly relied on a technical problem and solution
Enfish LLC v. Microsoft Corp.	Self-referential database architecture	Claims eligible	Supports treating software architecture as a technological improvement
BASCOM Global Internet Services v. AT&T Mobility	Internet filtering using a particular arrangement	Claims eligible at pleading stage	Ordered combinations can provide an inventive concept
Amdocs v. Openet	Distributed telecommunications data-processing architecture	Claims eligible	Specific network architecture distinguished the claims from abstract data processing

The Federal Circuit’s decision fit within a line of cases holding that software claims may be eligible when they improve the operation of a computer or network, even if they involve data collection and analysis.

The decision did not establish that all telecommunications billing software is patent-eligible. Its reasoning depended on the specific claim limitations, the disclosed architecture, and the claimed interaction among the components.

What was the Federal Circuit’s holding in Amdocs v. Openet?

The Federal Circuit held that the representative claims of all four patents were patent-eligible under § 101 and reversed the district court’s summary judgment.

The court’s analysis can be summarized as follows:

Patent	Abstract-idea analysis	Inventive-concept analysis	Outcome
’797	Claims were not abstract when viewed as a whole, or at minimum included a technological application	Distributed architecture and specialized processing components supplied sufficient substance	Eligible
’984	Claims addressed network-usage collection in a defined system	Claimed components operated together in a nonconventional arrangement	Eligible
’510	Claims were directed to processing network-accounting data through a specific architecture	The combination of data-gathering and enhancement functions was sufficient	Eligible
’065	Claims recited generation of consolidated service records using specified system components	The architecture provided a nonconventional technical solution	Eligible

The Federal Circuit remanded the case for further proceedings. The ruling was therefore a procedural and legal victory for Amdocs, but it was not a final infringement judgment.

Did the decision determine whether Openet infringed?

No. The Federal Circuit decided only the § 101 eligibility issue presented on appeal. It did not decide:

• Whether Openet’s products practiced each asserted claim;
• Whether the claims were anticipated under § 102;
• Whether the claims were obvious under § 103;
• Whether the patents satisfied written-description, enablement, or definiteness requirements under § 112;
• Whether Amdocs was entitled to damages or an injunction;
• Whether any asserted claims were enforceable.

The remand reopened the case for proceedings consistent with the appellate opinion. The eligibility ruling removed one threshold defense but did not eliminate Openet’s remaining litigation defenses.

How strong was Amdocs’ patent position after the appeal?

Amdocs’ position improved materially on patent eligibility. The Federal Circuit’s opinion gave Amdocs favorable authority for arguing that its patents claimed a concrete telecommunications architecture rather than an abstract information-processing method.

The strength of the estate after the decision had limits:

Strength factor	Assessment
§ 101 eligibility	Strong appellate result
Claim specificity	Meaningful architectural limitations supported eligibility
Infringement certainty	Not decided in the appeal
Prior-art exposure	Not resolved
Claim scope	Dependent on construction of distributed processing and enhancement limitations
Remedies	Not determined
Commercial leverage	Increased because Openet could no longer rely on § 101 as an automatic dispositive defense

The appellate decision was particularly useful in licensing or settlement discussions because it eliminated an invalidity ruling that would otherwise have removed the asserted patents from the case.

The opinion did not establish that the entire Amdocs patent portfolio was valid or enforceable. It addressed only the claims and issues before the court.

What litigation risks remained for Openet after the reversal?

Openet retained several potential defenses and case-management options:

1. Noninfringement based on the architecture of its accused products.
2. Claim-construction arguments concerning gathering, enhancement, storage, and distributed processing.
3. Anticipation and obviousness challenges based on earlier telecommunications billing systems.
4. Written-description and enablement arguments.
5. Definiteness challenges involving functional claim language.
6. Damages challenges concerning apportionment and the economic value of the claimed features.
7. Possible challenges to patent-term status, ownership, or enforceability, depending on the individual patent record.

The Federal Circuit’s decision made the § 101 issue more difficult for Openet but did not compel a finding of infringement.

What was the commercial impact of the case?

Amdocs develops software used by telecommunications carriers for billing, customer management, service assurance, and network operations. Openet competed in adjacent telecommunications software markets, including policy management and network data processing.

The case had commercial significance because the asserted patents covered functions closely tied to carrier monetization and usage accounting. A finding of infringement could have affected:

• Deployment of Openet software by telecommunications carriers;
• Licensing negotiations;
• Product redesign;
• Customer indemnification obligations;
• Competitive positioning in network-accounting and mediation software.

The public appellate decision did not establish a damages amount, royalty rate, injunction, settlement payment, or revenue allocation. No reliable revenue exposure can be quantified from the Federal Circuit opinion alone.

What was the final legal status of the case?

The Federal Circuit’s November 2016 decision reversed the district court’s § 101 judgment and remanded the matter. The reported appellate outcome was favorable to Amdocs on patent eligibility.

The decision did not report a final merits judgment on infringement or damages. The publicly reported appellate record also did not establish a final settlement term or commercial license between the parties. Any later district-court disposition would need to be evaluated separately from the reported Federal Circuit opinion.

Key Takeaways

• Amdocs sued Openet over four telecommunications network-accounting patents.
• The Eastern District of Virginia found the asserted claims invalid under § 101.
• The Federal Circuit reversed and held the representative claims patent-eligible.
• The decisive factor was the claimed distributed architecture and interaction among specialized processing components.
• The ruling relied on the ordered combination of limitations, not on generic computer implementation.
• The court did not decide infringement, damages, anticipation, obviousness, enablement, definiteness, or enforceability.
• The case has no FDA, Orange Book, Paragraph IV, biosimilar, or pharmaceutical-exclusivity component.
• The decision strengthened Amdocs’ litigation and licensing position but did not establish that the patents would survive every remaining validity defense.

FAQs About Amdocs v. Openet

What court decided Amdocs v. Openet?

The U.S. Court of Appeals for the Federal Circuit decided the appeal under docket No. 15-1180. The underlying case originated in the U.S. District Court for the Eastern District of Virginia.

What statutory provision was central to the appeal?

The appeal focused on 35 U.S.C. § 101, which governs patent-eligible subject matter. The Federal Circuit applied the Alice two-step framework.

Did Amdocs win the entire lawsuit?

No. Amdocs won the Federal Circuit appeal concerning patent eligibility. The court did not enter a final infringement or damages judgment.

Are the Amdocs patents software patents?

Yes. The patents covered software-implemented telecommunications data-processing systems and methods. The Federal Circuit treated the claimed distributed architecture as a technological arrangement rather than a purely abstract information-processing concept.

Does Amdocs v. Openet prevent invalidating software patents under § 101?

No. The decision is fact- and claim-specific. It supports eligibility where software claims recite a specific technological architecture and a nonconventional arrangement of components, but it does not make all software claims patent-eligible.

References

1. Amdocs (Israel) Ltd. v. Openet Telecom, Inc., 841 F.3d 1288 (Fed. Cir. 2016).

2. Alice Corp. Pty. Ltd. v. CLS Bank International, 573 U.S. 208 (2014).

3. DDR Holdings, LLC v. Hotels.com, L.P., 773 F.3d 1245 (Fed. Cir. 2014).

4. Enfish, LLC v. Microsoft Corp., 822 F.3d 1327 (Fed. Cir. 2016).

5. BASCOM Global Internet Services, Inc. v. AT&T Mobility LLC, 827 F.3d 1341 (Fed. Cir. 2016).