Amdocs (Israel) Limited v. Openet Telecom, Inc.

841 F.3d 1288, 120 U.S.P.Q. 2d (BNA) 1527, 2016 U.S. App. LEXIS 19593, 2016 WL 6440387
Court of Appeals for the Federal Circuit·Decided November 1, 2016·No. 2015-1180·Published·Cited by 183 cases

Opinions

Dissenting opinion filed by Circuit Judge REYNA.

PLAGER, Circuit Judge.

This is a patent case, in which the outcome turns on the application of the ‘abstract idea’ test, a judicially-created limitation on patent eligibility under § 101 of the Patent Act, 35 U.S.C. § 101.

Plaintiff-Appellant Amdocs (Israel) Limited (“Amdocs”) sued Defendants-Ap-pellees Openet Telecom, Inc. and Openet Telecom Ltd. (collectively, “Openet”) for infringing four U.S. Patents, Nos. 7,631,-065 (“’065 patent”); 7,412,510 (“’510 patent”); 6,947,984 (“’984 patent”); and 6,836,-797 (“’797 patent”). In the wake of Alice Corp. v. CLS Bank International, — U.S. -, 134 S.Ct. 2347, 189 L.Ed.2d 296 (2014), the district court granted Openet’s motion for judgment on the pleadings, finding that the patents were not directed to patent eligible subject .matter under § 101. Amdocs appeals.

For the reasons we shall explain, we reverse and remand for further proceedings.

[1291]*1291BACKGROUND

Prosecution History and Technology

Although we need not recapitulate every detail of these patents, we describe them sufficiently for purposes of this opinion. Additional background is available in our opinion from the prior appeal in this case. See Amdocs (Israel) Ltd. v. Openet Telecom, Inc., 761 F.3d 1329, 1331-36 (Fed. Cir. 2014) (‘Amdocs I”).

The patents in suit concern, inter alia, parts of a system designed to solve an accounting and billing problem faced by network service providers. Each patent descends from U.S. Patent Application No. 09/442,876, which issued as U.S. Patent No. 6,418,467. One of the patents in suit, the ’797 patent, issued as a result of a continuation-in-part application, while the other three patents issued as a result of continuation applications.

The ’065 patent concerns a system, method, and computer program for merging data in a network-based filtering and aggregating platform as well as a related apparatus for enhancing networking accounting data records. The ’510 patent concerns a system, method, and computer program for reporting on the collection of network usage information. The ’984 patent concerns a system and accompanying method and computer program for reporting on the collection of network usage information from a plurality of network devices. The ’797 patent concerns a system, method, and computer program for generating a single record reflecting multiple services for accounting purposes.

Each patent’s written description describes the same system, which allows network service providers to account for and bill for internet protocol (“IP”) network communications. The system includes network devices; information source modules (“ISMs”); gatherers; a central event manager (“CEM”); a central database; a user interface server; and terminals or clients. See, e.g., ’065 patent at 4:29-33, 43-54.

Network devices represent any devices that could be included on a network, including application servers, and also represent the source of information accessed by the ISMs. Id. at 5:10-26. The ISMs act as an interface between the gatherers and the network devices and enable the gatherers to collect data from the network devices. Id. at 5:33-35. The ISMs represent modular interfaces that send IP usage data in real time from network devices to gatherers. Id. at 5:35-39. Gatherers can be hardware and software installed on the same network segment as a network device or on an application server itself to minimize the data traffic impact on a network; gatherers “gather the information from the ISMs.” Id. at 6:54, 58-64. Gatherers also normalize data from the various types of ISMs and serve as a distributed filtering and aggregation system. Id. at 7:5-8. The CEM provides management and control of the ISMs and gatherers, and the CEM can perform several functions including performing data merges to remove redundant data .Id. at 8:13-67. The central database is the optional central repository of the information collected by the system and is one example of a sink for the data generated by the, system. Id. at 9:1-5. The user interface server allows multiple clients or terminals to access the system, and its primary purpose is to provide remote and local platform independent control for the system. Id. at 10:5-12.

Importantly, these components are arrayed in a distributed architecture that minimizes the impact on network and system resources. Id. at 3:56-65. Through this distributed architecture, the system minimizes network impact by collecting and processing data close to its source. Id. The system includes distributed data gathering, filtering, and enhancements that en[1292]*1292able load distribution. Id. at 4:33-42. This allows data to reside close to the information sources, thereby reducing congestion in network bottlenecks, while still allowing data to be accessible from a central location. Id. at 4:36-39. Each patent explains that this is an advantage over prior art systems that stored information in one location, which made it difficult to keep up with massive record flows from the network devices and which required huge databases. See, e.g., id. at 4:39-42.

Procedural History

In 2010, Amdocs sued Openet for patent infringement in the United States District Court for the Eastern District of Virginia. Amdocs asserted that Openet infringed claims 1, 4, 7, 13, and 17 of the ’066 patent; claims 16, 17, and 19 of the ’610 patent; claims 1, 2, 7, 8, and 13 of the ’984 patent; and claims 1, 2, 7, 8, and 19 of the ’797 patent.

In its answer and counterclaim, Openet alleged invalidity, unenforceability, and non-infringement. The parties filed motions addressing claim construction and summary judgment. The district court granted Openet’s motion for summary judgment of non-infringement and Am-docs’s motion for summary judgment of no inequitable conduct. Upon motions of the parties, which the court granted, certain claim constructions were made. However, the court denied the parties’ motions for summary judgment with respect to validity. The court later issued an opinion explaining its bases for its non-infringement and inequitable conduct summary judgment rulings, while also providing its claim constructions. Amdocs appealed the trial court’s judgment to this court.

On appeal, we affirmed two claim constructions and vacated and modified another construction. We approved of the district court’s construction of “enhance” to mean “to apply a number of field enhancements in a distributed fashion.” Amdocs I, 761 F.3d at 1338-40. In so doing, we approved of the district court’s “reading the ⅛ a distributed fashion’ and the ‘close to the source’ of network information requirements into the term ‘enhance.’ ” Id. at 1340. We also approved of the construction of “completing” to mean “enhance a record until all required fields have been populated.” Id.

However, we vacated the district court’s construction of “single record represents each of the plurality of services” as “one record that includes customer usage data for each of the plurality of services used by the customer on the network” but not including records that aggregated usage data. Id.

Free access — add to your briefcase to read the full text and ask questions with AI

Amdocs (Israel) Limited v. Openet Telecom, Inc., 841 F.3d 1288, 120 U.S.P.Q. 2d (BNA) 1527, 2016 U.S. App. LEXIS 19593, 2016 WL 6440387 (Fed. Cir. 2016).

841 F.3d 1288 (Amdocs (Israel) Limited v. Openet Telecom, Inc.) — published by Counsel Stack Legal Research, free access to 12M+ legal documents.

Related