throbber
IN THE UNITED STATES DISTRICT COURT
`FOR THE SOUTHERN DISTRICT OF TEXAS
`HOUSTON DIVISION
`

`
`§§
`
`§§
`
`§ CIVIL ACTION NO. H-18-2108

`
`§§
`

`
`ALARM.COM INC. and
`ICN ACQUISITION, LLC,
`
`v.
`
`IPDATATEL, LLC,
`
`Plaintiffs,
`
`Defendant.
`
`MEMORANDUM AND OPINION
`
`This patent-infringement case involves home-security technology for “smart” devices, such
`
`as cellular phones and tablets. Before home-security systems incorporated cellular and smartphone
`
`technologies, they relied on telephone lines to relay data. Applications, or “apps,” now allow users
`
`to activate and receive alarms, open doors, unlock windows, and receive alerts on various devices,
`
`wirelessly. This case arises out of the development of that technology.
`
` Alarm.com Inc. and a wholly owned subsidiary, ICN Acquisition, LLC, sued ipDataTel,
`
`LLC in August 2017, alleging that it infringed U.S. Patent Nos. 7,113,090; 7,633,385; 7,956,736;
`
`8,478,871; and 9,141,276. (Docket Entry No. 1 at ¶ 11). Alarm.com seeks injunctive relief and
`
`damages. (Id. at ¶ 82). ipDataTel denies infringement and alleges that the patents are invalid.
`
`(Docket Entry No. 98 at 2).
`
`The parties have asked the court to construe eight terms in the ’385, ’736, and ’276 patents.
`
`Alarm.com filed a claim-construction brief, ipDataTel responded, and Alarm.com replied. (Docket
`
`Entries Nos. 93, 100, 105). The court held a Markman hearing in September 2018, at which counsel
`
`argued their competing constructions. (Docket Entry No. 117). Based on the parties’ claim-
`
`1
`
`IPDATATEL EXHIBIT 1044
`ipDataTel, LLC v. ICN Acquisition LLC; IPR2018-01820
`
`

`

`construction briefs, counsels’ arguments, the record, and the applicable law, the court construes the
`
`eight disputed terms. The constructions and the reasons for them are set out in detail below.
`
`I.
`
`Background
`
`Alarm.com was incorporated in Delaware in 2000. It introduced its first wireless home-
`
`security system in 2003. (Docket Entry No. 46 at ¶ 15). Alarm.com describes itself as “a leading
`
`technology provider for connected home services,” including “interactive security” and “remote
`
`video monitoring,” “energy management,” and “home automation.” (Id. at ¶ 13). Alarm.com’s
`
`technology connects smart devices into one system, controlled by a smart-phone app, using a cloud-
`
`based platform that integrates the alarm system with different types of devices. Current examples
`
`of these devices include an iPad, a cell phone, a smart watch, Apple TV, and Amazon Echo. The
`
`platform is sold and supported by “a nationwide network of licensed and authorized Security and
`
`Smart Home service providers.” (Id. at ¶ 14). Alarm.com operates in North and South America and
`
`Australia. (Id. at ¶ 16). Coplaintiff ICN owns many of the patents-in-suit. (Id. at ¶ 17).
`
`ipDataTel was incorporated in Texas in 2007. (Id. at ¶ 18). ipDataTel manufactures devices
`
`for home security and operates data centers for internet operations and applications, offering
`
`“interactive security capabilities” similar to Alarm.com. (Id. at ¶¶ 19–20). ipDataTel markets its
`
`products throughout the United States. (Id. at ¶ 22).
`
`Alarm.com alleges that it and ipDataTel are direct competitors in the “home security or home
`
`automation market. The[] patents-in-suit . . . give Alarm.com a competitive edge.” (Docket Entry
`
`No. 102 at 9:11–15). Alarm.com alleges that ipDataTel infringes five patents related to
`
`Alarm.com’s home-security technology. (Docket Entry No. 46 at ¶ 12).
`
`2
`
`IPDATATEL EXHIBIT 1044
`ipDataTel, LLC v. ICN Acquisition LLC; IPR2018-01820
`
`

`

`A.
`
`The Patents
`
`i.
`
`The ’090 Patent
`
`This patent for a “System and Method for Connecting Security Systems to a Wireless
`
`Device” issued in September 2006. (Id. at ¶ 24 (citing U.S. Patent No. 7,113,090)). Before this
`
`patent, security systems consisted of a panel and sensors installed in a home. The panel had a
`
`keypad to control the system through a central monitor, which would detect “state changes” from
`
`sensors. (Id. at ¶ 26). Alarm.com recognized that this system could not relay other changes, such
`
`as opening or closing a door or window, and could not relay intrusions, when the system was not
`
`armed. (Id. at ¶ 27). The ability to detect and relay this information turns a home-security system
`
`into a kind of “nanny cam,” enabling a homeowner to monitor, for example, when his adolescent
`
`children return from a night out, or what time a housekeeper arrives and leaves. The patented
`
`technology allows both an unarmed and armed system to transmit these kinds of events or intrusions
`
`to a database through a modem. (Id. at ¶ 28). Alarm.com alleges that this type of information
`
`transmission was a dramatic shift from prior systems, which recognized only “alarm events” and did
`
`so only when the system was armed. (Id. at ¶ 30). This added capability increased the amount of
`
`data, which the system processed and stored. (Id. at ¶ 33).
`
`The patented technology also allows users to create notification preferences. (Id. at ¶ 34).
`
`Prior systems would call the homeowner’s landline telephone and, if no one answered, alert the local
`
`police. (Id. at ¶ 36). Under the ’090 patented technology, the user can choose which notifications
`
`are sent and how—for example, by email, text message, or telephone call. (Id. at ¶ 41). The user
`
`can also select multiple people to receive notifications before the system contacts the police. (Id.
`
`at ¶ 43).
`
`3
`
`IPDATATEL EXHIBIT 1044
`ipDataTel, LLC v. ICN Acquisition LLC; IPR2018-01820
`
`

`

`ii.
`
`The ’385 and ’736 Patents
`
`These patents, both entitled “Method and System for Communicating With and Controlling
`
`an Alarm System From a Remote Server,” (U.S. Patent Nos. 7,633,385 and 7,956,736), issued in
`
`December 2009 and June 2011. (Docket Entry No. 46 at ¶¶ 47–48). The ’736 patent is a
`
`continuation of the ’385 patent. Both “provide an upgrade unit that allows a user to keep an existing
`
`legacy alarm system rather than replacing that system.” (Id. at ¶ 49).
`
`Before the ’385 and ’736 patents issued, a user had to remove and replace a system to modify
`
`or upgrade it. (Id. at ¶ 50). A “legacy alarm system” usually had a controller connected to sensors
`
`throughout the house. The controller was connected to a central monitoring system, usually by a
`
`phone line. (Id. at ¶ 55). The user controlled the system through a keypad, which connected to the
`
`alarm controller through a “keypad bus.” (Id. at ¶ 58). This system communicated with the external
`
`monitoring service only through the phone line, which was vulnerable to being cut. Alarm.com
`
`refers to this vulnerability as a “single point of failure.” (Id. at ¶ 17). Another drawback of legacy
`
`systems was that they could send information only out to the monitoring system and could not
`
`receive information. (Id. at ¶ 63). The integrated communication system allowed for two-way
`
`cellular communication using a security panel, but installing the integrated system required
`
`removing the entire “legacy alarm system.” (Id. at ¶ 65).
`
`These patents address those shortcomings. Users can upgrade a legacy system without
`
`replacing it, by connecting a new communications unit with the keypad bus. (Id. at ¶ 69). The
`
`communications unit transmits and receives information through the existing security panel, without
`
`replacing the whole system. The communications unit also connects with a remote server to allow
`
`the user to control the system from outside the house. (Id. at ¶ 72).
`
`4
`
`IPDATATEL EXHIBIT 1044
`ipDataTel, LLC v. ICN Acquisition LLC; IPR2018-01820
`
`

`

`iii.
`
`The ’871 Patent
`
`This patent, “Gateway Registry Methods and Systems,” issued in July 2013. (U.S. Patent
`
`No. 8,478,871). The ’871 patent uses a “gateway” in conjunction with a “gateway registry” by
`
`assigning a unique serial number to the gateway for the gateway registry to identify. This method
`
`“improves the operation and efficiency of the gateway server.” (Docket Entry No. 46 at ¶ 80). A
`
`“gateway” is a “device that acts as a ‘gate’ between two networks. It may be a router, firewall,
`
`server, or other device that enables traffic to flow in and out of the network.” Gateway, THE TECH
`
`TERMS COMPUTER DICTIONARY (Oct. 8, 2018), https://techterms.com/definition/gateway.
`
`iv.
`
`The ’276 Patent
`
`The ’276 patent, “Integrated Interface for a Mobile Device,” issued in September 2015.
`
`(U.S. Patent No. 9,141,276). It concerns the mobile app a consumer uses to control a home-security
`
`system remotely. (Docket Entry No. 46 at ¶ 84). The app software allows any smartphone or
`
`similar device to synchronize the device to the security system. (Id. at ¶ 86).
`
`B.
`
`ipDataTel’s Knowledge of the Patents
`
`Alarm.com alleges that ipDataTel knew of the patents no later than the date the complaint
`
`was served. Alarm.com alleges that ipDataTel either actually knew of, or was willfully blind to, the
`
`patents even before the lawsuit, noting that Alarm.com’s website “prominently displays” the patents
`
`and that the two companies directly compete. (Docket Entry No. 46 at ¶ 96). Alarm.com alleges
`
`that ipDataTel researched iControl Networks, Inc., which previously owned four of the
`
`patents—’385, ’736, ’871, and ’276—and that ipDataTel and iControl are both members of the Z-
`
`Wave Alliance and had directly competed for customers. (Id. at ¶98). Alarm.com alleges that
`
`ipDataTel “affirmatively investigated” iControl’s patent portfolio. (Id.). Alarm.com alleges that
`
`5
`
`IPDATATEL EXHIBIT 1044
`ipDataTel, LLC v. ICN Acquisition LLC; IPR2018-01820
`
`

`

`ipDataTel gained knowledge of the patents through several earlier lawsuits, including: a 2013
`
`lawsuit Alarm.com brought against Telular Corporation for infringement of the ’090 patent; a 2004
`
`lawsuit against Zonoff, Inc. related to the ’871 patent; a second suit against Zonoff in 2015 for
`
`infringement of the ’385, ’736, and ’276 patents; and a 2017 suit against SecureNet Technologies
`
`LLC and Protect America, Inc. related to the ’090, ’385, and ’276 patents. (Id. at ¶¶ 100–102).
`
`Alarm.com also alleges that ipDataTel knew of the patents through a publication called “Security
`
`Industry Monitor,” which contained information about them starting in March 2014. (Id. at ¶ 103).
`
`C.
`
`The Disputed Terms
`
`The parties initially disputed 25 terms across the 5 patents. (Docket Entry No. 59-1). The
`
`parties now disagree on only 8 terms, in the ’385, ’736, and ’276 patents. The disputed terms the
`
`court is asked to construe are:
`
`1.
`
`2.
`
`3.
`
`4.
`
`5.
`
`select a communication mode [of the plurality of communication modes]
`(’385 Patent, Claim 1);
`
`means for performing a first pre-determined response (’736 Patent, Claim 12);
`
`means for receiving a first set of data over a network from an alarm system
`communication unit, wherein the first set of data comprises keypad bus
`information, the keypad bus information corresponds to a signal on a keypad
`bus of an alarm system controller, and the keypad bus of the alarm system
`controller provides communication between an alarm processor of the alarm
`system controller, a keypad processor, and the alarm system communication
`unit (’736 Patent, Claim 12);
`
`means for storing a set of responses to keypad bus information, wherein the
`keypad bus information comprises one of a plurality of events and conditions
`reported on the alarm system controller keypad bus, and each response of the
`set of responses corresponds to an event or condition of the plurality of events
`and conditions (’736 Patent, Claim 15);
`
`means for selecting the pre-determined response to the keypad bus
`information in the first set of data from the set of responses (’736 Patent,
`Claim 15);
`
`6
`
`IPDATATEL EXHIBIT 1044
`ipDataTel, LLC v. ICN Acquisition LLC; IPR2018-01820
`
`

`

`6.
`
`7.
`
`8.
`
`custom-built for the mobile device (’276 Patent, Claims 2 and 14);
`
`performing . . . a synchronization to associate the mobile device with the
`monitoring system (’276 Patent, Claims 1 and 13); and
`
`synchronization (’276 Patent, all asserted claims).
`
`II.
`
`The Legal Standards
`
`A.
`
`Claim Construction
`
`The “claims of a patent define the invention to which the patentee is entitled the right to
`
`exclude.” Phillips v. AWH Corp., 415 F.3d 1303, 1312 (Fed. Cir. 2005) (en banc) (quoting
`
`Innova/Pure Water, Inc. v. Safari Water Filtration Sys., Inc., 381 F.3d 1111, 1115 (Fed. Cir. 2004)).
`
`“[T]he construction of a patent, including terms of art within its claim, is exclusively within the
`
`province of the court.” Markman v. Westview Instruments, Inc., 517 U.S. 370, 372 (1996). Claim
`
`terms are “generally given their ordinary and customary meaning,” defined as “the meaning that the
`
`term would have to a person of ordinary skill in the art in question at the time of the invention.”
`
`Phillips, 415 F.3d at 1312–13 (quoting Vitronics Corp. v. Conceptronic, Inc., 90 F.3d 1576, 1582
`
`(Fed. Cir. 1996)). That is, a person who will “read the words used in the patent documents with an
`
`understanding of their meaning in the field, and [has] knowledge of any special meaning and usage
`
`in the field.” Id. at 1313 (quoting Multiform Desiccants, Inc. v. Medzam, Ltd., 133 F.3d 1473, 1477
`
`(Fed. Cir. 1998)); see also Medrad, Inc. v. MRI Devices Corp., 401 F.3d 1313, 1319 (Fed. Cir. 2005)
`
`(cautioning courts not to interpret claim terms “in a vacuum” (quotation omitted)).
`
`Claim construction begins with the claim language. Aptalis Pharmatech, Inc. v. Apotex Inc.,
`
`718 F. App’x 965, 968 (Fed. Cir. 2018). The court looks first “to the words of the claims
`
`themselves, both asserted and nonasserted, to define the scope of the patented invention,” Vitronics,
`
`7
`
`IPDATATEL EXHIBIT 1044
`ipDataTel, LLC v. ICN Acquisition LLC; IPR2018-01820
`
`

`

`90 F.3d at 1582, and construes the claim terms in the context of the surrounding claim language.
`
`Accord ACTV, Inc. v. Walt Disney Co., 346 F.3d 1082, 1088 (Fed. Cir. 2003) (“[T]he context of the
`
`surrounding words of the claim also must be considered in determining the ordinary and customary
`
`meaning of those terms.”); Lexion Med., LLC v. Northgate Techs., Inc., 641 F.3d 1352, 1356–57
`
`(Fed. Cir. 2011). When the words in the context of the surrounding claim language make the
`
`ordinary meaning readily apparent, claim construction “involves little more than the application of
`
`the widely accepted meaning of commonly understood words.” Phillips, 415 F.3d at 1314.
`
`Patent-ese is notoriously clumsy and awkward, which makes construction more challenging.
`
`If the “ordinary and customary” meaning is unclear, the court moves from the words in the claims,
`
`viewed in context of the patent, to “the intrinsic evidence of record, i.e., the patent itself, including
`
`the claims, the specification and, if in evidence, the prosecution history.” Vitronics, 90 F.3d at 1582.
`
`Courts review the “specification to determine whether the inventor has used any terms in a manner
`
`inconsistent with their ordinary meaning.” Id. The Federal Circuit has repeatedly stated that
`
`“claims ‘must be read in view of the specification, of which they are a part.’” Phillips, 415 F.3d at
`
`1315 (quoting Markman v. Westview Instruments, Inc., 52 F.3d 967, 979 (Fed. Cir. 1995), aff’d, 517
`
`U.S. 370 (1996)). The specification, a “‘concordance for the claims,’” id. (quoting Autogiro Co. of
`
`Am. v. United States, 384 F.2d 391, 397–98 (Ct. Cl. 1967)), is the “best source for understanding
`
`a technical term.” Id. (quoting Multiform Desiccants, 133 F.3d at 1478).1 “[T]he specification may
`
`reveal an intentional disclaimer, or disavowal, of claim scope by the inventor.” Id. (citing SciMed
`
`1 See also Metabolite Labs., Inc. v. Lab. Corp. of Am. Holdings, 370 F.3d 1354, 1360 (Fed. Cir. 2004)
`(“In most cases, the best source for discerning the proper context of claim terms is the patent specification
`wherein the patent applicant describes the invention.”). When the specification “reveal[s] a special definition
`given to a claim term by the patentee that differs from the meaning it would otherwise possess . . . the
`inventor’s lexicography governs.” Phillips, 415 F.3d at 1316 (citing CCS Fitness, Inc. v. Brunswick Corp.,
`288 F.3d 1359, 1366 (Fed. Cir. 2002)).
`
`8
`
`IPDATATEL EXHIBIT 1044
`ipDataTel, LLC v. ICN Acquisition LLC; IPR2018-01820
`
`

`

`Life Sys., Inc. v. Advanced Cardiovascular Sys., Inc., 242 F.3d 1337, 1343–44 (Fed. Cir. 2001)); see
`
`also Thorner v. Sony Comput. Entm’t Am. LLC, 669 F.3d 1362, 1365 (Fed. Cir. 2012) (claim
`
`construction may deviate from the ordinary meaning of a disputed term only if: (1) “a patentee sets
`
`out a definition and acts as his own lexicographer”; or (2) “the patentee disavows the full scope of
`
`a claim term, either in the specification or during prosecution”).
`
`“The construction that stays true to the claim language and most naturally aligns with the
`
`patent’s description of the invention will be[] the correct construction.” Phillips, 415 F.3d at 1316
`
`(quoting Renishaw PLC v. Marposs Società per Azioni, 158 F.3d, 1243, 1250 (Fed. Cir. 1998)).
`
`“There is a fine line between construing the claims in light of the specification and improperly
`
`importing a limitation from the specification into the claims.” Retractable Techs., Inc. v. Becton,
`
`Dickinson & Co., 653 F.3d 1296, 1305 (Fed. Cir. 2011). Courts must “capture the scope of the
`
`actual invention, rather than strictly limit the scope of claims to disclosed embodiments or allow the
`
`claim language to become divorced from what the specification conveys is the invention.” Id.
`
`“[A] court ‘should also consider the patent’s prosecution history, if it is in evidence.’”
`
`Phillips, 415 F.3d at 1317 (quoting Markman, 52 F.3d at 980); see also Typhoon Touch Techs., Inc.
`
`v. Dell, Inc., 659 F.3d 1376, 1381 (Fed. Cir. 2011) (“[T]he specification is the primary source for
`
`determining what was invented and what is covered by the claims, elucidated if needed by the
`
`prosecution history.”). “[T]he prosecution history can often inform the meaning of the claim
`
`language by demonstrating how the inventor understood the invention and whether the inventor
`
`limited the invention in the course of prosecution, making the claim scope narrower than it would
`
`otherwise be.” Phillips, 415 F.3d at 1317 (citing Vitronics, 90 F.3d at 1582–83). The prosecution
`
`history includes “all express representations made by or on behalf of the applicant to the examiner
`
`9
`
`IPDATATEL EXHIBIT 1044
`ipDataTel, LLC v. ICN Acquisition LLC; IPR2018-01820
`
`

`

`to induce a patent grant, or . . . to reissue a patent . . . includ[ing] amendments to the claims and
`
`arguments made to convince the examiner that the claimed invention meets the statutory
`
`requirements of novelty, utility, and nonobviousness.” Standard Oil Co. v. Am. Cyanamid Co., 774
`
`F.2d 448, 452 (Fed. Cir. 1985); see also Sanofi-Aventis Deutschland GmbH v. Genentech, Inc., 473
`
`F. App’x 885, 888 (Fed. Cir. 2012) (“We have held that an otherwise broadly defined term can be
`
`narrowed during prosecution through arguments made to distinguish prior art.”) (citing Phillips, 415
`
`F.3d at 1317).
`
`“The doctrine of prosecution disclaimer is well established in Supreme Court precedent,
`
`precluding patentees from recapturing through claim interpretation specific meanings disclaimed
`
`during prosecution.” Omega Eng’g, Inc. v. Raytek Corp., 334 F.3d 1314, 1323 (Fed. Cir. 2003); see
`
`also SanDisk Corp. v. Memorex Prods., Inc., 415 F.3d 1278, 1286 (Fed. Cir. 2005). The doctrine
`
`applies even if the disclaimers were not necessary to make the invention patentable. See Uship
`
`Intellectual Props., LLC v. United States, 714 F.3d 1311, 1315 (Fed. Cir. 2013) (“We find no
`
`support for [the] proposition that prosecution disclaimer applies only when applicants attempt to
`
`overcome a claim rejection. Our cases broadly state that an applicant’s statements to the [United
`
`States Patent and Trademark Office] characterizing its invention may give rise to a prosecution
`
`disclaimer.”); cf. Southwall Techs., Inc. v. Cardinal IG Co., 54 F.3d 1570, 1583 (Fed. Cir. 1995)
`
`(“Estoppel extends beyond the basis of patentability. . . . Clear assertions made during prosecution
`
`in support of patentability, whether or not actually required to secure allowance of the claim, may
`
`also create an estoppel.”) (citing Tex. Instruments, Inc. v. United States Int’l Trade Comm’n, 988
`
`F.2d 1165, 1173 (Fed. Cir. 1993)).2 Prosecution disclaimer does not apply “where the alleged
`
`2 “There is a clear line of distinction between using the contents of the prosecution history to reach
`an understanding about disputed claim language and the doctrine of prosecution history estoppel which
`‘estops’ or limits later expansion of the protection accorded by the claim to the patent owner under the
`
`10
`
`IPDATATEL EXHIBIT 1044
`ipDataTel, LLC v. ICN Acquisition LLC; IPR2018-01820
`
`

`

`disavowal of claim scope is ambiguous.” Omega Eng’g, 334 F.3d at 1324; see also id. at 1325
`
`(“[W]e have required the alleged disavowing statements to be both so clear as to show reasonable
`
`clarity and deliberateness and so unmistakable as to be unambiguous evidence of disclaimer.”
`
`(citations omitted)). Only when “the patentee has unequivocally disavowed a certain meaning to
`
`obtain his patent [does] the doctrine of prosecution disclaimer attach[ ] and narrow[ ] the ordinary
`
`meaning of the claim congruent with the scope of the surrender.” Id. at 1324.
`
`Courts may also “rely on extrinsic evidence, which ‘consists of all evidence external to the
`
`patent and prosecution history, including expert and inventor testimony, dictionaries, and learned
`
`treatises.’” Phillips, 415 F.3d at 1317 (quoting Markman, 52 F.3d at 980). Although extrinsic
`
`evidence “can shed useful light on the relevant art, it is less significant than the intrinsic record in
`
`determining the legally operative meaning of claim language.” Zircon Corp. v. Stanley Black &
`
`Decker, Inc., 452 F. App’x 966, 972–73 (Fed. Cir. 2011) (quotations omitted). Extrinsic evidence
`
`is generally “less reliable than the patent and its prosecution history” because it is “not part of the
`
`patent” and was not created in patent prosecution: “extrinsic publications may not be written by or
`
`for skilled artisans”; and expert reports and testimony created later, for litigation, may “suffer from
`
`doctrine of equivalents when the claims have been purposefully amended or distinguished over relevant prior
`art to give up scope. . . . [T]he two uses of the prosecution history must not be confused.” Biodex Corp. v.
`Loredan Biomedical, Inc., 946 F.2d 850, 862 (Fed. Cir. 1991) (quotations omitted); see also Ballard Med.
`Prods. v. Allegiance Healthcare Corp., 268 F.3d 1352, 1358–59 (Fed. Cir. 2001) (distinguishing the two);
`Spectrum Int’l, Inc. v. Sterilite Corp., 164 F.3d 1372, 1378 n.2 (Fed. Cir. 1998) (same). “Just as prosecution
`history estoppel may act to estop an equivalence argument under the doctrine of equivalents, positions taken
`before the [Patent and Trademark Office] may bar an inconsistent position on claim construction.” Ballard
`Med. Prods., 268 F.3d at 1359 (quoting Cybor Corp. v. FAS Techs., Inc., 138 F.3d 1448, 1457 (Fed. Cir.
`1998)) (alteration omitted). When the accused infringer argues that the prosecution history results in a
`narrowing of a claim’s scope, there is no difference, and the Federal Circuit has refused to reverse based on
`references to estoppel. See id. at 1359 (“Because the substance of the district court’s analysis was sound, we
`disregard the fact that the court used the term ‘prosecution history estoppel’ in an unconventional manner.”);
`Biodex Corp., 946 F.2d at 862–63 (observing that “Biodex is technically correct in asserting that the doctrine
`of prosecution history estoppel is ‘irrelevant’ to determination of literal claim scope,” but upholding the
`district court because prosecution history is relevant to claim interpretation).
`
`11
`
`IPDATATEL EXHIBIT 1044
`ipDataTel, LLC v. ICN Acquisition LLC; IPR2018-01820
`
`

`

`bias not present in intrinsic evidence.” Phillips, 415 F.3d at 1318. A court must use “sound
`
`discretion” in admitting and using extrinsic evidence. Id. at 1319; see also Seattle Box Co., Inc. v.
`
`Indus. Crating & Packing, Inc., 731 F.2d 818, 826 (Fed. Cir. 1984) (“A trial judge has sole
`
`discretion to decide whether or not [s]he needs, or even just desires, an expert’s assistance to
`
`understand a patent. We will not disturb that discretionary decision except in the clearest case.”).
`
`“[E]xtrinsic evidence may be useful to the court, but it is unlikely to result in a reliable
`
`interpretation of patent claim scope unless considered in the context of the intrinsic evidence.”
`
`Phillips, 415 F.3d at 1319. Although a court may consider extrinsic evidence, it must not relegate
`
`the intrinsic evidence to a mere “check on the dictionary meaning of a claim term.” Id. at 1320–21
`
`(noting that relying on dictionaries “too often” causes “the adoption of a dictionary definition . . .
`
`divorced from the context of the written description”). “The sequence of steps used by the judge
`
`in consulting various sources is not important; what matters is for the court to attach the appropriate
`
`weight to be assigned to those sources in light of the statutes and policies that inform patent law.”
`
`Id. at 1324 (citing Vitronics, 90 F.3d at 1582).
`
`These claim-construction rules must be applied to the record in this case, including the
`
`tutorial counsel jointly provided the court, the arguments counsel presented during the Markman
`
`hearing, and the documents.
`
`B.
`
`Indefiniteness
`
`Under 35 U.S.C. § 112(2), a patent “specification shall conclude with one or more claims
`
`particularly pointing out and distinctly claiming the subject matter which the inventor . . . regards
`
`as the invention.” The Federal Circuit has explained:
`
`The primary purpose of the definiteness requirement is to ensure that the claims are
`written in such a way that they give notice to the public of the extent of the legal
`
`12
`
`IPDATATEL EXHIBIT 1044
`ipDataTel, LLC v. ICN Acquisition LLC; IPR2018-01820
`
`

`

`protection afforded by the patent, so that interested members of the public, e.g.,
`competitors of the patent owner, can determine whether or not they infringe. That
`determination requires a construction of the claims according to the familiar canons
`of claim construction.
`
`Oakley, Inc. v. Sunglass Hut Int’l, 316 F.3d 1331, 1340 (Fed. Cir. 2003) (citing All Dental Prodx,
`
`LLC v. Advantage Dental Prods., 309 F.3d 774, 779–80 (Fed. Cir. 2002) (citations omitted)). “One
`
`of those canons is that claims are construed as one skilled in the art would understand them in light
`
`of the specification of which they are a part.” Id. at 1340–41 (citing Orthokinetics, Inc. v. Safety
`
`Travel Chairs, Inc., 806 F.2d 1565, 1575 (Fed. Cir. 1986)).
`
`A determination of claim indefiniteness is a legal conclusion reached by the court performing
`
`its duty as the “construer of patent claims.” Tech. Licensing Corp. v. Videotek, Inc., 545 F.3d 1316,
`
`1338 (Fed. Cir. 2008) (citing Personalized Media Commc’ns, LLC v. Int’l Trade Comm’n, 161 F.3d
`
`696, 705 (Fed. Cir. 1998)). “To the extent there are any factual findings upon which a trial court’s
`
`indefiniteness conclusion depends, they must be proven by the challenger by clear and convincing
`
`evidence.” Id. (citing Intel Corp. v. VIA Techs., Inc., 319 F.3d 1357, 1366 (Fed. Cir. 2003)).
`
`C.
`
`Means-Plus-Function Claims
`
`Section 112(6) provides that “[a]n element in a claim for a combination may be expressed
`
`as a means or step for performing a specified function without the recital of structure, material, or
`
`acts in support thereof, and such claim shall be construed to cover the corresponding structure,
`
`material, or acts described in the specification and equivalents thereof.” 35 U.S.C. § 112(6). A
`
`means-plus-function claim format allows a patentee to “describe an element of his invention by the
`
`result accomplished or the function served, rather than describing the item or element to be used.”
`
`Warner-Jenkinson Co., Inc. v. Hilton Davis Chem. Co., 520 U.S. 17, 27 (1997). A patentee’s use
`
`13
`
`IPDATATEL EXHIBIT 1044
`ipDataTel, LLC v. ICN Acquisition LLC; IPR2018-01820
`
`

`

`of the word “means” in a claim element that recites a function creates a presumption that the element
`
`is drafted in means-plus-function format. Id.; TriMed, Inc. v. Stryker Corp., 514 F.3d 1256, 1259
`
`(Fed. Cir. 2008). This presumption can be rebutted if the claim recites sufficient structure to
`
`accomplish the functions identified in the claim. Welker Bearing Co. v. PHD, Inc., 550 F.3d 1090,
`
`1096 (Fed. Cir. 2008).
`
`“Sufficient structure exists when the claim language specifies the exact structure that
`
`performs the functions in question without need to resort to other portions of the specification or
`
`extrinsic evidence for an adequate understanding of the structure.” TriMed, 514 F.3d at 1259–60.
`
`A claim recites sufficiently definite structure if it has “an understood meaning in the art” that
`
`connotes enough structure to fall outside § 112(6) or if it is “used in common parlance or by persons
`
`of skill in the pertinent art to designate structure, even if the term covers a broad class of structures.”
`
`Aspex Eyewear, Inc. v. Altair Eyewear, Inc., 288 F. App’x 697, 703 (Fed. Cir. 2008) (quotation
`
`omitted). If a claim includes a means-plus-function limitation, failure to disclose adequate structure
`
`corresponding to the claimed function results in invalidity for indefiniteness. In re Dossell, 115 F.3d
`
`942, 946 (Fed. Cir. 1997); see also Budde v. Harley-Davidson, Inc., 250 F.3d 1369, 1376 (Fed. Cir.
`
`2001) (“For a court to hold that a claim containing a means-plus-function limitation lacks a
`
`disclosure of structure in the patent specification that performs the claimed function, necessarily
`
`means that the court finds the claim in question indefinite, and thus invalid.”); Cardiac Pacemakers,
`
`Inc. v. St. Jude Med., Inc., 296 F.3d 1106, 1114 (Fed. Cir. 2002); Aristocrat Techs. Austl. PTY Ltd.
`
`v. Int’l Game Tech., 521 F.3d 1328, 1331 (Fed. Cir. 2008).
`
`If means-plus-function analysis applies, a court first determines what the claimed function
`
`is and then determines the corresponding structures disclosed in the specification that perform that
`
`14
`
`IPDATATEL EXHIBIT 1044
`ipDataTel, LLC v. ICN Acquisition LLC; IPR2018-01820
`
`

`

`function. Welker Bearing, 550 F.3d at 1097; Minks v. Polaris Indus., Inc., 546 F.3d 1364, 1377
`
`(Fed. Cir. 2008); Tex. Dig. Sys., Inc. v. Telegenix, Inc., 308 F.3d 1193, 1208 (Fed. Cir. 2002).
`
`“Structure disclosed in the specification qualifies as corresponding structure if the intrinsic evidence
`
`clearly links or associates that structure to the function recited in the claim.” Williamson v. Citrix
`
`Online, LLC, 792 F.3d 1339, 1352 (Fed. Cir. 2015). Whether the written description adequately sets
`
`forth structure corresponding to the claimed function must be considered from the perspective of a
`
`person skilled in the art. Intel Corp., 319 F.3d at 1365–66 (citing Budde, 250 F.3d at 1376). The
`
`question is not whether one skilled in the art would be capable of implementing a structure to
`
`perform the function, but whether that person would understand the written description itself to
`
`disclose such a structure. Biomedino, LLC v. Waters Techs. Corp., 490 F.3d 946, 953 (Fed. Cir.
`
`2007) (citing Med. Instrumentation & Diagnostics Corp. v. Elekta AB, 344 F.3d 1205, 1212 (Fed.
`
`Cir. 2003)).
`
`The Federal Circuit has made clear that disclosing a general-purpose computer capable of
`
`running specialized software, without more, does not supply sufficient structure for means-plus-
`
`function claims involving a computer that must be specially programmed to perform a specific set
`
`of functions. See WMS Gaming, Inc. v. Int’l Game Tech., 184 F.3d 1339, 1349 (Fed. Cir. 1999).
`
`The structure that the specification must disclose is “not the general purpose computer, but rather
`
`the special purpose computer programmed to perform the disclosed algorithm.” Id.; see also Harris
`
`Corp. v. Ericsson, Inc., 417 F.3d 1241, 1253 (Fed. Cir. 2005) (“A computer-implemented means-
`
`plus-function term is limited to the corresponding structure disclosed in the specification and
`
`equivalents thereof, and the corresponding structure is the algorithm.”); Gobeli Research Ltd. v.
`
`Apple Comput., Inc., 384 F. Supp. 2d 1016, 1022 (E.D. Tex. 2005) (“The Federal Circuit has made
`
`15
`
`IPDATATEL EXHIBIT 1044
`ipDataTel, LLC v. ICN Acquisition LLC; IPR2018-01820
`
`

`

`clear that when software is linked to the disclosed function, the structure for performing the function
`
`is limited to the algorithm disclose

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket