5 UNITED STATES DISTRICT COURT WESTERN DISTRICT OF WASHINGTON 6 AT SEATTLE
7 DOGGYPHONE LLC, NO. 2:19-cv-1901-BJR Plaintiff,
8 v. CLAIM CONSTRUCTION ORDER 9 TOMOFUN, LLC, Defendant 10
11 12 I. INTRODUCTION At issue in this case is the construction of several disputed claim terms of U.S. Patent No. 13 9,723,813 (“the ’813 patent”), owned by Plaintiff DoggyPhone LLC. Plaintiff has accused 14 Defendant Tomofun LLC of infringing that patent. Having reviewed the parties’ claim 15 construction briefs and responses, and having held a Markman claim construction hearing, the 16 Court rules as follows. 17 18 II. BACKGROUND The ’813 patent provides a system for facilitating remote human-pet communication, and 19 is referred to as an “Internet Canine Communication System,” or “ICCS.” The patent abstract 20 states, “[t]he ICCS may include a base station or similar device that is configured to deliver 21 treats to a dog and to transmit audio/visual communication between the dog and a remote client 22 23
24 CLAIM CONSTRUCTION ORDER
25 1 || device operated by a human user.” ’813 Patent, p. 1. Figures 7 and 8, below, illustrate certain 2 ||example embodiments of the patent:
6 "Ke \ ate \ Coe ep e | BY : xX i“
9 we
10 Defendant Tomofun manufactures and sells the interactive pet camera device known as 1] ll the “Furbo,” which DoggyPhone claims infringes the ’813 patent. According to Tomofun, the 12 Furbo is a “Dog Camera that enables a user to remotely see their pet, talk to their pet, and toss 13 || treats to their pet,” via an app on the user’s mobile device. Def.’s Opening Cl. Constr. Br. 14 (“Def.’s Br.”) at 7. This is a Furbo: 15 16 17 18 > 19 © “= 20 . ——— 2] DoggyPhone has asserted Claim 7 of the ’813 Patent against Tomofun. Claim 7 recites 22 the following, with the disputed claim terms at issue in this litigation italicized: 23 24 CLAIM CONSTRUCTION ORDER
25 ||
a treat bin; 2 a food dispenser that dispenses treats from the treat bin; an audio device; 3 a delivery module that: receives a treat delivery command; and 4 in response to the received treat delivery command: dispenses via the food dispenser at least one treat from the 5 treat bin; plays via audio device an audio signal that notifies the 6 pet of availability of a treat; and receives input from the pet; and 7 a control that transmits to the delivery module a treat delivery command, 8 wherein the system: in response to a first communication command received 9 from a user, transmits to the delivery module the treat delivery command; 10 plays at least one of live audio or video received from the user of a remote client device; and 11 transmits to the remote client device at least one of live audio or video of the pet, wherein the system begins 12 transmission to the remote client device of at least one of the audio or video of the pet in response to input 13 from the pet.
14 ’813 Patent, col. 12:15-39. The parties have represented that there are six disputed terms, 15 one of which contains two sub-parts, all discussed in more detail below. Generally, as to all 16 disputed terms, DoggyPhone argues that the Court should construe the terms to have their “plain 17 and ordinary meaning,” as understood by a person of ordinary skill in the art in light of the 18 patent. Tomofun’s position as to the first two terms—“food dispenser” and “delivery module”— 19 is that they are subject to “means treatment” under 35 U.S.C. § 112(f) and, lacking the requisite 20 structure, are indefinite. For the remaining disputed terms, Tomofun asks for narrowing 21 constructions, based on what it argues is intrinsic and extrinsic evidence, including the patent 22 specification and prosecution history. 23
25 2 court-approved stipulation in February 2021 pending resolution of Tomofun’s petition for inter 3 partes review (IPR). The Patent Trial and Appeal Board (PTAB) denied that petition and a 4 motion for reconsideration of that denial, and the stay was lifted in January 2022. Both sides 5 submitted opening claim construction briefs and responses, and on June 24, 2022, the Court held 6 a Markman claim construction hearing, at which counsel presented oral argument. See Transcript 7 of 6/24/22 Markman Hr’g, Dkt. No. 50 (“Tr.”). 8 III. DISCUSSION 9 A. Legal Framework for Patent Claim Construction 10 “When the parties raise an actual dispute regarding the proper scope of [the] claims, the 11 court, not the jury, must resolve that dispute.” Markman v. Westview Instruments, Inc., 52 F.3d
12 979 (Fed. Cir. 1995) (en banc) (holding that claim construction is a matter of law). “The purpose 13 of claim construction is to ‘determin[e] the meaning and scope of the patent claims asserted to be 14 infringed.’” O2 Micro Int'l Ltd. v. Beyond Innovation Tech. Co., Ltd., 521 F.3d 1351, 1360 (Fed. 15 Cir. 2008) (quoting Markman, 52 F.3d at 976). 16 “It is a bedrock principle of patent law that the claims of a patent define the invention to 17 which the patentee is entitled the right to exclude.” Innova/Pure Water, Inc. v. Safari Water 18 Filtration Sys., Inc., 381 F.3d 1111, 1115 (Fed. Cir. 2004) (citations omitted); Markman, 52 F.3d 19 at 980 (“The written description part of the specification itself does not delimit the right to 20 exclude. That is the function and purpose of claims.”). “To the extent possible, claim terms are 21 given their ordinary and customary meaning, as they would be understood by one of ordinary
22 skill in the art in question at the time of the invention.” Intervet Inc. v. Merial Ltd., 617 F.3d 23
25 2 patentee sets out a definition and acts as his own lexicographer, or (2) when the patentee 3 disavows the full scope of a claim term either in the specification or during prosecution.” 4 Thorner v. Sony Comput. Entm't Am. LLC, 669 F.3d 1362, 1365 (Fed. Cir. 2012) (citing 5 Vitronics, 90 F.3d at 1580). 6 The analysis of any disputed claim terms begins with the intrinsic evidence of record. 7 Vitronics, 90 F.3d at 1582. Intrinsic evidence includes the specification, which “is always highly 8 relevant to the claim construction analysis. Usually, it is dispositive; it is the single best guide to 9 the meaning of a disputed term.” Id.; Phillips v. AWH Corp., 415 F.3d 1303, 1315 (Fed. Cir. 10 2005) (“This court and its predecessors have long emphasized the importance of the specification 11 in claim construction.”). However, “although the specification often describes very specific
12 embodiments of the invention, we have repeatedly warned against confining the claims to those 13 embodiments.” Phillips, 415 F.3d at 1323; see Comark Communications, Inc. v. Harris Corp., 14 156 F.3d 1182, 1186–87 (Fed.Cir. 1998) (“there is sometimes a fine line between reading a claim 15 in light of the specification, and reading a limitation into the claim from the specification”). The 16 Federal Circuit has acknowledged “that the distinction between using the specification to 17 interpret the meaning of a claim and importing limitations from the specification into the claim 18 can be a difficult one to apply in practice.” Id. 19 B. Means-Plus-Function Claiming: Terms 1 and 2 20 1. Legal Framework of Means-Plus-Function Claiming 21 Of the six disputed terms at issue, Tomofun argues that two are “means-plus-function”
22 terms that must be analyzed under 35 U.S.C. § 112(f). That statute provides that: 23
25 performing a specified function without the recital of structure, material, or acts in 2 support thereof, and such claim shall be construed to cover the corresponding structure, material, or acts described in the specification and equivalents thereof. 3 35 U.S.C. § 112(f). Congress’s intent in enacting the statute was to strike “a balance in 4 allowing patentees to express a claim limitation by reciting a function to be performed rather than 5 by reciting structure for performing that function, while placing specific constraints on how such 6 a limitation is to be construed, namely, by restricting the scope of coverage only to the structure, 7 materials, or acts described in the specification as corresponding to the claimed function and 8 equivalents thereof.” Williamson v. Citrix Online, LLC, 792 F.3d 1339, 1347-48 (Fed. Cir. 2015). 9 Whether Section 112(f) applies is a question of law for the court, dependent upon 10 “whether the words of the claim are understood by persons of ordinary skill in the art to have a 11 sufficiently definite meaning as the name for structure.” Williamson, 792 F.3d at 1346, 1348. In 12 making that determination, courts “look first to intrinsic evidence, and then, if necessary, to the 13 extrinsic evidence.” Egenera, Inc. v. Cisco Sys., Inc., 972 F.3d 1367, 1373 (Fed. Cir. 2020) 14 (quotation omitted). Courts ask whether the disputed term, “as the name for structure, has a 15 reasonably well understood meaning in the art.” Greenberg v. Ethicon Endo-Surgery, Inc., 91 16 F.3d 1580, 1583 (Fed. Cir. 1996). 17 The Federal Circuit “has long recognized the importance of the presence or absence of the 18 word ‘means,’ [and] the use of the word ‘means’ in a claim element creates a rebuttable 19 presumption that § 112, para. 6 applies.”1 Williamson, 792 F.3d at 1348. On the other hand, if the 20 term “means” is absent from a claim element, then there is a rebuttable presumption that Section 21 22 1 Paragraph 6 of 35 U.S.C. § 112 was replaced by § 112(f) when the Leahy–Smith America Invents Act (“AIA”), 23 Pub.L. No. 112–29, 125 Stat. 284 (2011) took effect on September 16, 2012.
25 2 ultimately control whether the statute applies. Id. “For example, generic terms such as 3 ‘mechanism,’ ‘element,’ ‘device,’ and other verbal constructs may be used in a claim in a manner 4 that is tantamount to using the word ‘means’ because they typically do not connote sufficiently 5 definite structure and therefore may invoke [the means-plus-function statute].” Egenera, 972 F.3d 6 at 1373 (quotations omitted). “Such terms may amount to generic terms or black box recitations 7 of structure or abstractions. Or a term may amount to a coined nonce word—that is, a word 8 invented for one occasion only.” Id. (cleaned up). If that is the case, then Section 112(f) applies 9 because the claim term is “simply a generic substitute for ‘means.’” Id. at 1375. “What is 10 important is ... that the term, as the name for structure, has a reasonably well understood meaning 11 in the art.” Greenberg, 91 F.3d at 1583.
12 Where, as here, the word “means” is not present, the rebuttable presumption that Section 13 112(f) does not apply can be overcome “if the challenger demonstrates that the claim term fails to 14 recite sufficiently definite structure or else recites function without reciting sufficient structure for 15 performing that function.” Williamson, 792 F.3d at 1348 (cleaned up). “If the presumption against 16 means-plus-function interpretation is overcome, [the court] must identify the claimed function 17 and then determine what structure, if any, disclosed in the specification corresponds to the 18 claimed function.” Egenera, 972 F.3d at 1373 (quotation omitted). 19 2. Term 1: “a food dispenser that dispenses treats from the treat bin” 20 Tomofun argues that the phrase “food dispenser” in Claim 7 is means-plus-function 21 claiming that must be construed in light of Section 112(6). However, because the term does not
22 include the word “means,” the presumption is that it is not a means-plus-function term, and 23
25 2 above, it can do so by demonstrating “that the claim term fails to recite sufficiently definite 3 structure or else recites function without reciting sufficient structure for performing that 4 function.” Id. 5 Tomofun argues that a “food dispenser” is merely a functional claim, defined by its 6 function, i.e., a means of dispensing food, and that the term provides no definite structure that is 7 associated with that function. The Court disagrees. The word “dispenser” is not a “verbal 8 construct” as Tomofun argues, or a “generic term” one could simply substitute in this context for 9 “mechanism,” “element,” or “device.” Egenera, Inc., 972 F.3d at 1373. As DoggyPhone argues, 10 the word “dispenser” is similar to the words “brake,” “clamp,” or “filter,” in that it has taken on a 11 structural dimension signifying more than merely the function it performs. With the added
12 modification “food,” particularly in the context of this patent, which pertains to dog food, the term 13 connotes an amount of structure sufficient to defy means-plus-function treatment. The additional 14 phrase “that dispenses treats from the treat bin,” contained in the claim itself, adds still more 15 structure to the term. The Court concludes the term recites sufficiently definite structure such that 16 Section 112(f) does not apply, and, in the absence of a proposed alternative, adopts 17 DoggyPhone’s construction of the “plain and ordinary meaning” of the term. 18 3. Term 2: “a delivery module that: receives a treat delivery command . . .” 19 Again, because the term does not use the word “means,” it is Tomofun’s burden of 20 demonstrating that Section 112(f) applies. As to this term, however, the Court is persuaded that 21 Section 112(f) does apply. As the Williamson court noted, “‘module’ is a well-known nonce word
22 that can operate as a substitute for ‘means’ in the context of § 112, para. 6.” 792 F.3d at 1350. 23
25 2 to speculate as to what that structure might be. The Court therefore concludes that the term is a 3 means-plus-function term, and that Section 112(f) applies. 4 Once a court has determined that Section 112(f) applies, the inquiry is twofold: “First, the 5 court must determine the claimed function. Second, the court must identify the corresponding 6 structure in the written description of the patent that performs the function.” Williamson, 792 F.3d 7 at 1348. If a court cannot associate the claimed functions with any “corresponding structure, 8 material, or acts described in the specification,” the claim term is indefinite. Noah Sys., Inc. v. 9 Intuit Inc., 675 F.3d 1302, 1312 (Fed. Cir. 2012). In this case, the claim at issue recites four 10 functions associated with the delivery module: it (1) receives a treat delivery command; (2) 11 dispenses a treat from the treat bin; (3) plays an audio signal to notify the pet of the treat; and (4)
12 receives input from the pet. ’813 Patent, col. 12:19-26. 13 The Court concludes that the specification provides sufficient “structure, material, or acts” 14 corresponding to each of these functions. 35 U.S.C. §112(f). As to the first function, the delivery 15 module “receives a treat delivery command” “via various input devices of the ICCS 100, 16 including the training button 116, Wi-Fi antenna 126, Ethernet port 128, or the like.” Id., col. 17 3:27-29. Buttons and antennae are undeniably and definitely structural, as Figures 1 and 2 18 illustrate. As to the second claimed function, the delivery module dispenses treats using, “e.g., 19 including one or more of a carousel, slide, bin, actuator, motor[] for delivering treats,”2 again 20 describing certain acts and structural elements that correspond to the treat delivery function. Id., 21 col. 6:49-52; see also Figs. 3 and 4 (illustrating “treat compartments” and “treat passage” of
22 2 In addition, as the Court notes supra, “food dispenser” (in the context of dogs, functionally a synonym for “treat 23 dispenser”) connotes sufficiently definite structure.
25 2 module will “initiate a sound (e.g., play an audio signal, ring a bell, cause a local or remote audio 3 device to output a sound) to notify the pet of the presence of a treat in the food tray, and stop 4 playing the audio signal when the pet accesses the food tray to obtain the treat.” Id., col. 9:16-21. 5 Again, these examples all connote definite acts and structure. As to the fourth claimed function, 6 receiving input, “[a]n input may include pushing an activation cover 110 . . . [or] a response lever 7 or panel configured to make it easy for the dog to push with nose or paw, detecting motion (e.g., 8 via a motion detector of the ICCS), detecting a sound (e.g., a bark detected via a microphone of 9 the ICCS), detecting heat (e.g., via an infrared sensor), or the like.” Id., col. 5:9-15. The Court 10 concludes that the text in the specification, combined with the corresponding illustrations, 11 sufficiently describes the “structure, material, or acts” corresponding to each of the functions
12 recited in the claim term, saving the term from indefiniteness. 35 U.S.C. § 112(f). 13 C. Disputed Constructions: Terms 3-6 14 As to each of the four remaining disputed claim terms at issue, Plaintiff urges a “plain and 15 ordinary” meaning, as understood by a person of ordinary skill in the art. The burden rests with 16 Tomofun to demonstrate that its proposed constructions are required by the claim language, the 17 specification, or other intrinsic or extrinsic factors. See Teleflex, Inc. v. Ficosa N. Am. Corp., 299 18 F.3d 1313, 1327 (Fed. Cir. 2002) (referencing the “‘heavy presumption’ that a claim term takes 19 on its ordinary meaning”). 20 1. Term 3: “a treat delivery command” and “the treat delivery command” 21 DoggyPhone argues that the plain and ordinary meaning of a/the “treat delivery
22 command” should control. Tomofun seeks construction of the phrase to mean a (or the) “single 23
25 2 that causes all three of the delivery module functions that follow: dispensing food, playing an 3 audio signal, and receiving input from the pet. DoggyPhone, in contrast, urges that the person of 4 ordinary skill in the art would understand the term to mean a “compilation or series of signals that 5 together make up the ‘treat delivery command,’” causing these functions. Pl.’s Opening Cl. 6 Constr. Br. (“Pl.’s Br.”) at 15. 7 Tomofun has not argued that the term would be misunderstood by a person of ordinary 8 skill in the art, and it is undisputed that the claim itself does not use the word “single.” However, 9 Tomofun claims that “single” is implied in the grammatical structure of the claim, and that certain 10 example embodiments in the specification repeatedly indicate that the appropriate construction of 11 the term includes the limitation “singular.” It also claims that DoggyPhone relied on the phrase
12 “single received delivery command” in obtaining and defending the ’813 patent, and that 13 DoggyPhone should be held to that construction. 14 The Court concludes that while Tomofun’s proposed construction based on the 15 grammatical structure of the claim—what Tomofun referred to in the Markman hearing as the 16 “gut logic read of the claim”—is plausible, there is nothing about the claim language itself that 17 would require construction of the phrase to mean a/the “single treat delivery command.” See Tr. 18 at 37:17. As the Federal Circuit has noted, depending on the context, “a” does not necessarily 19 indicate singular. In re Varma, 816 F.3d 1352, 1362 (Fed. Cir. 2016) (“‘a’ sometimes is non- 20 restrictive as to number, permitting the presence of more than one of the objects following that 21 indefinite article.”).
22 Tomofun also argues that the specification “consistently describes a single command.” 23
25 2 or limitations from the specification into a claim. Intervet, 617 F.3d at 1287 (“Construing the 3 claims in light of the specification does not . . . imply that limitations discussed in the 4 specification may be read into the claims. It is therefore important not to confuse exemplars or 5 preferred embodiments in the specification that serve to teach and enable the invention with 6 limitations that define the outer boundaries of claim scope.”). Additionally, the Court notes that 7 the specification also includes reference to other embodiments in which the treat carousel may 8 rotate (and deliver treats) in response to decidedly plural “signals, commands, or other indications 9 received via various input devices.” ’813 Patent, col. 3:21-28. 10 The Court also concludes that Tomofun has not met its burden of demonstrating a “clear 11 and unambiguous disavowal” of the term’s plain and ordinary meaning in obtaining or defending
12 the patent. See Aylus Networks, Inc. v. Apple Inc., 856 F.3d 1353, 1359 (Fed. Cir. 2017) (“[F]or 13 prosecution disclaimer to attach, our precedent requires that the alleged disavowing actions or 14 statements made during prosecution be both clear and unmistakable.”) (quoting Omega Eng'g, 15 Inc, v. Raytek Corp., 334 F.3d 1314, 1325-26 (Fed. Cir. 2003)). In overstating its claim that 16 DoggyPhone “repeatedly argued that the claimed functions of the delivery module are caused by a 17 single treat delivery command,” Tomofun only highlights the absence of any actual disavowal in 18 the prosecution history. Def.’s Br. at 15. DoggyPhone did use the phrase “a single received 19 command” in the context of distinguishing prior art in prosecution. (’813 FH, 10/28/2014 Appeal 20 Brief, Ex. 3 to Def.’s Br. at 39-40). However, use of that phrase came in the context of a more 21 general discussion that included what the command caused (i.e., a “sequence of multiple
22 functions”), and was not focused on whether or not it was necessary for the command causing 23
25 2 DoggyPhone’s construction. Similarly, while Tomofun argues that DoggyPhone “implicitly 3 asserted” the narrower construction in response to Tomofun’s IPR petition, an “implicit assertion” 4 also does not meet the “express relinquishment” standard that the law requires. Def.’s Br. at 16; 5 see Omega Eng'g, 334 F.3d at 1323 (“claim terms carry their full ordinary and customary 6 meaning,” unless patentee “expressly relinquished claim scope during prosecution.”). 7 In short, Tomofun has failed to show that the term should be construed to include the 8 “single” limitation, or to have anything other than its plain and ordinary meaning. 9 2. Term 4: “a control that transmits to the delivery module a treat delivery command” 10 Tomofun’s proposed construction would substitute “a computing device that includes a 11 user actuated mechanism, such as a button, switch, or touchscreen” for “control.” DoggyPhone 12 rejects that construction, arguing that a person of ordinary skill in the art, with the help of the 13 intrinsic record, would understand a “control” to be “of any form or nature, including but not 14 limited to a user actuated mechanism as part of a computer device, a physical button, switch or 15 touchscreen, a virtual control, or a series of signals,” so long as that control can, as claimed, 16 “transmit to the delivery module a treat delivery command.” Pl.’s Br. at 16. DoggyPhone argues 17 Tomofun’s construction improperly imports limitations on what was actually claimed. 18 Tomofun, in turn, argues that its proposed construction “is consistent with the 19 requirements of the claims” and “the intrinsic evidence,” citing the patent claims, references in the 20 specification, and statements made in prosecution, that it says support this position. Def.’s Br. at 21 23. That a proposed construction be “consistent with” the intrinsic evidence, however, is not the 22 standard. Tomofun must overcome the starting presumption that a person of ordinary skill in the 23
25 2 do so. See Phillips, 415 F.3d at 1316. Furthermore, nothing in the specification requires the 3 limiting construction, and Tomofun has not pointed to any disavowal of the claim term in 4 prosecution that would require its construction. Under these circumstances, the plain and ordinary 5 meaning controls. See Thorner v. Sony Computer Ent. Am. LLC, 669 F.3d 1362, 1367 (Fed. Cir. 6 2012) (“The patentee is free to choose a broad term and expect to obtain the full scope of its plain 7 and ordinary meaning unless the patentee explicitly redefines the term or disavows its full 8 scope.”). 9 Tomofun’s proposed construction is not only unnecessary; it is also improper. 10 DoggyPhone points out that the proposed construction would unjustifiably exclude certain 11 embodiments referenced in the patent, such as a voice-activated control and, as DoggyPhone
12 asserted at the Markman hearing, would “tak[e] out anything that’s not mechanical.” Tr. at 52:3- 13 4; see ’813 Patent, col. 7:43-49 (“During the communication session, the user may press keys or 14 other input controls that generate sounds or issue a voice command word, that are configured . . . 15 to perform certain functions, such as deliver a treat.”). And, while Tomofun’s proposed 16 construction uses the phrase “including but not limited to” with reference to examples of several 17 mechanisms, the Court agrees with DoggyPhone that such wording could cause jury confusion as 18 to whether the claim is somehow limited to the category of explicitly listed mechanisms following 19 that phrase, which would not be consistent with the specification. In short, Tomofun has failed to 20 demonstrate its construction is allowed, let alone required, in construing the meaning of the term 21 “control.”
22 /// 23
25 from the user of a remote client device” and “transmits to the remote client 2 device at least one of live audio or video of the pet” and (b) “in response to input from the pet” 3 a. “live audio or video” 4 Tomofun asks the Court to construe the term “live audio or video” to mean “audio or 5 video that is transmitted at the time of occurrence, not from a recording” the first time the term 6 occurs in the claim, and “audio or video of the pet at the time of occurrence, not from a 7 recording” the second time. DoggyPhone contends that the term “live audio or video” may be 8 given its plain and ordinary meaning, which does not include the strict limitation—which 9 nowhere occurs in the claim itself—that the audio or video be played or transmitted “at the time 10 of occurrence” and “not from a recording.” DoggyPhone contends that a person of ordinary skill 11 in the art understands that the term “live audio or video” would not include these requirements. It 12 is commonly understood, DoggyPhone argues, that “(1) there is no such thing as “real time,” 13 because there is always a lag caused by transmission over space, (2) time-shifting of “live” audio 14 or video is commonplace; and (3) all modern transmission and playback technologies rely on 15 buffering video/audio in memory, where it is recorded temporarily prior to being transmitted or 16 displayed.” Pl.’s Br. at 20. 17 Support for DoggyPhone’s position is found in the intrinsic evidence. Adopting 18 Tomofun’s construction is impermissible because it would exclude the embodiments described in 19 the specification, “given that all media transmissions are buffered and therefore recorded.” Pl.’s 20 Br. at 21. The Background of the ’813 Patent explicitly links “live audio and video” with 21 technology that a person of ordinary skill would understand transmits images, by necessity, not at 22 the time of recording. See ’813 Patent, Background, 1:23-25 (referencing “[l]ow cost Internet 23
25 2 feeds over the Internet”). 3 Moreover, DoggyPhone is not claiming as unreasonably broad a meaning of “live” as 4 Tomofun portrays. See Def.’s Resp. Br. at 1 (“DoggyPhone asserts that the plain and ordinary 5 meaning of “live” means recorded and retrieved at any time, without restriction.”). A person of 6 ordinary skill in the art would understand the term “live”—in the context of the technology 7 described in the embodiments—to mean essentially at the same time, while allowing for slight 8 time delays, buffering, and playback as required by the limitations of the known technology (and 9 physics). See also Tr. at 63:18-19 (“transmitted live” commonly understood to mean “sent . . at 10 or about the time that it's captured”). Within the context of the patent—on which a person of 11 ordinary skill in the art would be required to rely—“live” is also still bound by the requirement
12 that transmission of audio and video enable communication between pet and owner: in other 13 words, at essentially, but not necessarily precisely, the same time. 14 Tomofun argues that “[t]echnical and common usage dictionaries unanimously support” 15 its construction. Def.’s Br. at 21. But resort to such extrinsic evidence is improper and 16 unnecessary where, as here, the intrinsic evidence supports the patentee’s construction. The Court 17 therefore declines to adopt Tomofun’s proposed construction and holds that the term “live video 18 and audio” may be given its plain and ordinary meaning as set forth herein. 19 b. “in response to input from the pet” 20 Tomofun asks the Court to construe the term “in response to input from the pet” in Claim 21 7 to mean “triggered by input from the pet.” The original term, however, is not ambiguous, and
22 was not disavowed in prosecution or the IPR proceedings, and would easily be understood by a 23
25 2 with “in response to” several times in the IPR proceeding, it also used, at least once, the phrase 3 “triggered or otherwise causally connected,” making it fairly explicit that “in response to” need 4 not be strictly construed to mean “triggered.” See Pat. Owner’s Prelim. Resp. at 16, Ex. 5 to 5 Def.’s Br. Tomofun has failed to overcome the presumption that “in response to input from the 6 pet” is properly construed to have its plain and ordinary meaning. 7 4. Term 6: “in response to the received treat delivery command: dispenses via the food dispenser at least one treat from the treat bin; plays via the audio device an 8 audio signal that notifies the pet of availability of a treat; and receives input from the pet” 9 Again, DoggyPhone proposes that the term be construed using its plain and ordinary 10 meaning. Tomofun asks the Court to construe the term to mean: 11 the received single treat delivery command triggering each of: 12 operation of the food dispenser to dispense at least one treat from the treat bin; operation of the audio device to play an audio signal that notifies the pet of 13 availability of a treat; and operation of at least one component of the treat delivery module to receive input 14 from the pet.
15 This construction, according to Tomofun, is “clearer.” Tomofun argues that the claim as 16 written could mean that the delivery module receives input from the pet in response to the treat 17 delivery command; and, since whether the pet provides such input in response to the command “is 18 subject to the pet’s whims and ultimately unknowable,” the plain and ordinary meaning of the 19 claim is indefinite. Def.’s Br. at 21 (citing Intellectual Ventures I LLC v. T-Mobile USA, 902 F.3d 20 1372, 1381 (Fed. Cir. 2018) (term that “depends on the unpredictable vagaries of any one 21 person’s opinion is indefinite”)). It claims that its construction “clarifies that what must be 22 responsive to the treat delivery command is the delivery module, not the pet.” Id. 23
25 2 nonsensical construction. As written, it is adequately clear that it is the delivery module, not the 3 pet, that must be responsive to the delivery command. It is the delivery module, after all, that is 4 doing the receiving. And whether a trained dog will provide that input in response to the promise 5 of a treat is less subject to whim than Tomofun suggests. 6 While the plain and ordinary meaning of the claim is clear, Tomofun, for its part, has not 7 provided any support from the specification or prosecution history that would require its proposed 8 construction. The plain and ordinary meaning of the term as written, being sufficiently definite 9 and not clearly disavowed in prosecution, is the appropriate construction. 10 IV. CONCLUSION 11 For the foregoing reasons, the Court construes the disputed claims to have their plain and
12 ordinary meaning, as set forth above. 13 DATED this 12th day of August, 2022. 14 A 15 16 B arbara Jacobs Rothstein U.S. District Court Judge 17 18 19 20 21 22 23