throbber
Case 6:21-cv-00642-ADA Document 33 Filed 01/14/22 Page 1 of 14
`
`IN THE UNITED STATES DISTRICT COURT
`WESTERN DISTRICT OF TEXAS
`WACO DIVISION
`
`FLYPSI, INC. (D/B/A FLYP),
`
`
`Plaintiff,
`
`
`
`Civil Action No. 6:21-cv-642-ADA
`
`
` JURY TRIAL DEMANDED
`
`
`
`
`v.
`
`DIALPAD, INC.,
`
`
`Defendant.
`
`
`
`
`
`DEFENDANT DIALPAD, INC.’S REPLY CLAIM CONSTRUCTION BRIEF
`
`
`
`

`

`Case 6:21-cv-00642-ADA Document 33 Filed 01/14/22 Page 2 of 14
`
`Table of Contents
`
`
`Page
`
`
`INTRODUCTION ......................................................................................................................... 1
`I.
`ARGUMENT ..................................................................................................................... 1
`A.
`Claim Terms For Construction .............................................................................. 1
`1.
`“primary telephone number” ...................................................................... 1
`2.
`“voice channel” .......................................................................................... 3
`Indefiniteness ......................................................................................................... 6
`1.
`The terms “switch” and “switch … associated with” are indefinite .......... 6
`CONCLUSION .................................................................................................................. 9
`
`B.
`
`II.
`
`
`
`
`
`-i-
`
`
`
`

`

`Case 6:21-cv-00642-ADA Document 33 Filed 01/14/22 Page 3 of 14
`
`TABLE OF AUTHORITIES
`
`
`
`Page(s)
`
`
`
`Cases
`
`Astrazeneca AB v. Mut. Pharm. Co.,
`384 F.3d 1333 (Fed. Cir. 2004)..................................................................................................6
`
`Dynamic Applet Techs., LLC v. Mattress Firm, Inc.,
`2018 U.S. Dist. LEXIS 216894 .................................................................................................8
`
`GPNE Corp. v. Apple, Inc.,
`830 F.3d 1365, 1370 (Fed. Cir. 2016)........................................................................................3
`
`Greenberg v. Ethicon Endo-Surgery, Inc.,
`91 F.3d 1580, 1583 (Fed. Cir. 1996)..........................................................................................9
`
`ICU Med., Inc. v. Alaris Med. Sys., Inc.,
`558 F.3d 1368 (Fed. Cir. 2009)..................................................................................................3
`
`Nautilus, Inc. v. Biosig Instruments, Inc.,
`134 S. Ct. 2120, 2124 (2014) .....................................................................................................8
`
`Thorner v. Sony Computer Entertainment America LLC,
`669 F.3d 1362 (Fed.Cir.2012)....................................................................................................5
`
`Trs. of Columbia Univ. in the City of N.Y. v. Symantec Corp.,
`811 F.3d 1359 (Fed. Cir. 2016)..............................................................................................5, 6
`
`VirnetX, Inc. v. Cisco Sys., Inc.,
`767 F.3d 1308 (Fed. Cir. 2014)..................................................................................................3
`
`Watts v. XL Sys., Inc.,
`232 F.3d 877 (Fed.Cir.2000)......................................................................................................9
`
`Williamson v. Citrix Online, LLC,
`792 F.3d 1339 (Fed. Cir. 2015)..................................................................................................9
`
`Other Authorities
`
`Dictionary of Computing (6th ed. 2008)..........................................................................................8
`
`ii
`
`

`

`Case 6:21-cv-00642-ADA Document 33 Filed 01/14/22 Page 4 of 14
`
`
`
`INTRODUCTION
`
`In its brief, Flypsi provides background on itself, sets forth in entirety two patent claims,
`
`and asserts that all meaning is self-evident from the claims. Flypsi also provides a “rebuttal”
`
`declaration from its expert that does not provide constructions, but instead argues that claim
`
`terms in dispute are “not limited” and do not require construction because a POSITA, not a jury,
`
`knows the meaning. Flypsi provided no extrinsic evidence in the form of an expert declaration
`
`when extrinsic evidence was due.
`
`As explained in the opening brief and below, the claim terms “primary telephone
`
`number” and “voice channel” that Dialpad put forward for construction should be construed
`
`because their specific meaning is established by the intrinsic record.
`
`With respect to “switch” and “… associated with,” identified by Dialpad as indefinite
`
`during the claim construction process, Flypsi has not proposed a construction. Without settling
`
`on a single meaning, Dr. Nettles identifies wide ranging definitions of “switch” from hardware to
`
`software. He does not identify or define what the “associations” are. By leaving both terms
`
`undefined, there is an indefiniteness problem with identifying what is the “switch” in any given
`
`network and what the nature of the association is during an infringement analysis.
`
`
`
`I.
`
`ARGUMENT
`
`A.
`
`Claim Terms For Construction
`
`1.
`
`“primary telephone number”
`
`‘770 Patent claim 1, 4
`‘105 Patent claims 1, 2, 10 and 11
`‘094 patent claims 1
`‘554 patent claims 1
`
`Dialpad’s Modified Proposed
`Construction
`
`Flypsi’s Proposed Construction
`
`1
`
`
`
`

`

`Case 6:21-cv-00642-ADA Document 33 Filed 01/14/22 Page 5 of 14
`
`
`
`
`
`A telephone number or identifier that is
`assigned to a handset or mobile device at
`activation.
`
`Undefined plain and ordinary meaning.
`
`Flypsi argues that “primary telephone number” should not be construed as “assigned… at
`
`activation” because while, “quite often, a primary telephone number is assigned at the time of
`
`activation,” “[a]ll major carriers, however, allow a user to change his or her primary phone
`
`number at some point after activation.” Flypsi Responsive Br. at 10. “It would be
`
`impermissible to limit the claims only to the number assigned the time of activation.” Id.
`
`Flypsi recognizes that the telephone number assigned at activation by a carrier, such as
`
`Verizon, is a primary telephone number, but quarrels with the construction because a primary
`
`telephone number can be assigned by the carrier at times other than “activation.” To
`
`accommodate primary telephone number assignments after activation, the construction can be
`
`revised to: “A telephone number or identifier that is assigned to a handset or mobile device.”
`
`The patent specifications use the term “primary telephone number” 28 times and
`
`“secondary telephone number” 63 times to carefully distinguish one from the other. Not
`
`construing the term would eliminate any difference between primary telephone numbers and
`
`secondary telephone numbers, as those terms are used in the claims. Flypsi fails to address this
`
`point, and asserts that “primary telephone number” does not need to be construed because the
`
`patentee did not act as a lexicographer.
`
`Contrary to Flypsi’s assertion, the patentees’ extensive usage of the term “primary
`
`telephone number” is consistent only with a telephone number assignment to a handset or
`
`mobile device. The secondary telephone numbers are “added” to a primary telephone number,
`
`see U.S. Patent No. 9,667,770 (Exhibit 1 to Dialpad Opening Br.) at Figure 2, which is also
`
`2
`
`

`

`Case 6:21-cv-00642-ADA Document 33 Filed 01/14/22 Page 6 of 14
`
`
`
`described as one or more secondary telephone numbers being “referenced to a primary
`
`telephone number for the handset,” Id. at 5:1-2. This formulation is consistent throughout.
`
`Courts have recognized that when a patent “repeatedly and consistently” characterizes a
`
`claim term in a particular way, it is proper to construe the claim term in accordance with that
`
`characterization. See, e.g. , VirnetX, Inc. v. Cisco Sys., Inc. , 767 F.3d 1308, 1318 (Fed. Cir.
`
`2014) ; ICU Med., Inc. v. Alaris Med. Sys., Inc., 558 F.3d 1368, 1374–75 (Fed. Cir. 2009). See
`
`also GPNE Corp. v. Apple, Inc., 830 F.3d 1365, 1370 (Fed. Cir. 2016) (Prost, C.J.) (affirming a
`
`construction of “device” as being a “pager” in view of consistent disclosure in the specification
`
`where “the words ‘pager’ and ‘pager units’ appear in the specification over 200 times, and, apart
`
`from the Abstract, the specification repeatedly and exclusively uses these words to refer to the
`
`devices in the patented system.”). Here, likewise, primary telephone number repeatedly and
`
`consistently is used in the specification to refer to the telephone number assigned to the mobile
`
`device or handset, and it should be construed accordingly.
`
`2.
`
`“voice channel”
`
`‘770 Patent claim 1, 4, and 6
`‘105 Patent claims 1, 2, 4, 5 and 8
`
`Dialpad’s Proposed Construction
`
`Flypsi’s Proposed Construction
`
`A communications path used for voice
`information and voice calls.
`
`Undefined plain and ordinary meaning.
`
`
`
`Flypsi argues in its responsive brief that no construction of “voice channel” is needed
`
`and that the specification should not be used to inform the meaning of the term. Yet, it
`
`acknowledges that the specification “makes clear that such channels [CDMA, GSM, and like
`
`governed standards (like LTE and the more recent 5G)] are considered voice channels when
`
`used to carry voice.” Fypsi Responsive Br. at 13. In fact, the specification evidences an explicit
`
`3
`
`

`

`Case 6:21-cv-00642-ADA Document 33 Filed 01/14/22 Page 7 of 14
`
`
`
`definition of “voice channel.” And, the repeated use of voice channel reinforces that definition
`
`by implication.
`
`In the specification, a full paragraph is devoted to data and voice channels, which
`
`includes language that both parties quote:
`
`The communications between the server 100 and the handset 340 over the
`Internet 316 may utilize IP as a protocol opposed to protocols used to
`establish communications according to CDMA, GSM, or like standards.
`Such IP governed communications are referred to herein as being
`conducted over a "data channel.” Conversely, communications between
`the Switch 110 and the handset over the PSTN 310 may be transmitted
`and received in accordance with CDMA, GSM or like standards as
`opposed to using IP. Such CDMA, GSM or like governed
`communications, when used to carry voice information, are referred
`to herein as being conducted over a “voice channel.”
`
`’770] Patent, at 4:35-46 (Emphasis added). This paragraph distinguishes between a data channel
`
`and a voice channel. Flypsi’s expert argues that usage of “may” in the above paragraph means
`
`that voice channel is “not limited.” Nettles Decl. at ¶ 35. But, neither Flypsi nor its expert
`
`addresses the definitional nature of the last sentence. The last sentence is definitional and uses
`
`voice channel to refer to a communications path (such as CDMA, GSM or like governed
`
`communications) when used to carry voice information.
`
`Similarly, there are dozens of statements in the specification that calls are made and
`
`connected using a voice channel:
`
`• “incoming and outgoing calls, which are ultimately connected using a voice
`channel.” ’770 Patent, at Abstract.
`• “transmitting a voice call associated with the call handling information between the
`handset and the Switch using a voice channel provided in accordance with a Voice
`channel protocol, e.g., in accordance with CDMA or GSM, 3G, 4G, LTE or like
`future protocol channels standards.” Id. at 1:45-50.
`• “If the call is accepted in step 414, however, the handset application may
`automatically cause the handset 340 to call the bridge telephone number in step
`422 over a voice channel.” Id. at 6:62-65.
`• See also Id. at 6:62-65, 6:65-67, 6:67-7:6, 8:6-8:8, 8:8-8:11, 8:12-8:15, 9:32-35, 9:35-
`37, 9:40-42, 9:49-51.
`
`4
`
`

`

`Case 6:21-cv-00642-ADA Document 33 Filed 01/14/22 Page 8 of 14
`
`
`
`The specification thus makes clear by definition and implication that the voice channel is
`
`used for calls and voice information. By contrast, the data channel carries information that may
`
`be used to make telephone calls using the voice channel. See Id. at Abstract (“A data channel
`
`connection with the telephone handset may provide pre-call information to set up incoming and
`
`outgoing calls which are ultimately connected using a voice channel.” This is entirely consistent
`
`with the claims. See ‘770 Patent, claim 1 (“likewise accepting the incoming call by connecting
`
`with the switch over the at least one voice channel”), ‘105 Patent (Exhibit 2 to Dialpad Opening
`
`Br.), claim 1 (“establishing a voice channel connection between the handset and the switch as a
`
`result of the handset calling the switch using the bridge telephone number.”)
`
`Flypsi cites Thorner v. Sony Computer Entertainment America LLC, 669 F.3d 1362
`
`(Fed.Cir.2012) for the proposition that “‘only two exceptions to [the] general rule’ that claim
`
`terms are construed according to their plain-and-ordinary meaning are when the patentee (1) acts
`
`as his/her own lexicographer or (2) disavows the full scope of the claim term either in the
`
`specification or during prosecution.” Flypsi Responsive Br. at 12. However, as recently
`
`explained in, The Trustees Of Columbia University In The City Of New York v. Symantec
`
`Corporation, “[o]ur case law does not require explicit redefinition or disavowal.” Trs. of
`
`Columbia Univ. in the City of N.Y. v. Symantec Corp., 811 F.3d 1359, 1363 (Fed. Cir. 2016).
`
`“Thus, we reject Columbia's argument that the presumption of plain and ordinary meaning ‘can
`
`be overcome in only two circumstances: [when] the patentee has expressly defined a term or has
`
`expressly disavowed the full scope of the claim in the specification and the prosecution history.’”
`
`Id. at 1364. “As our en banc opinion in Phillips made clear, ‘a claim term may be clearly
`
`redefined without an explicit statement of redefinition’ and ‘even when guidance is not provided
`
`in explicit definitional format, the specification may define claim terms by implication such that
`
`5
`
`

`

`Case 6:21-cv-00642-ADA Document 33 Filed 01/14/22 Page 9 of 14
`
`
`
`the meaning may be found in or ascertained by a reading of the patent documents.’” Id. at 1363.
`
`See also Astrazeneca AB v. Mut. Pharm. Co., 384 F.3d 1333 (Fed. Cir. 2004) (The patentee
`
`“seems to suggest that lexicography requires a statement in the form ‘I define __ to mean _ ,’
`
`but such rigid formalism is not required.”).
`
`Here, the specifications provide an explicit definition of voice channel and define it by
`
`implication. Dialpad’s proposed construction most closely captures the meaning of the term in
`
`the specification and claims.
`
`The “rebuttal” expert declaration provided does not address the explicit definition in the
`
`specification as such, or the many instances in which voice channel is defined by implication.
`
`Thus, it is exactly the type of extrinsic evidence that is not helpful to claim construction.
`
`
`
`B.
`
`Indefiniteness
`
`1.
`
`The terms “switch” and “switch … associated with” are indefinite
`
`‘770 Patent Clam 1
`‘105 Patent Claim 1, 2
`‘994 Patent Claim 1
`‘554 Patent Claim 1
`
`
`
`
`
`
`
`Dialpad’s Proposed Construction
`
`Flypsi’s Proposed Construction
`
`
`
`Undefined plain and ordinary meaning.
`
`
`
`Indefinite.
`
`
`
`
`6
`
`

`

`Case 6:21-cv-00642-ADA Document 33 Filed 01/14/22 Page 10 of 14
`
`
`
`Flypsi has not provided itself, or via its expert, any construction of “switch” or “switch
`
`… associated with” claim language. Dialpad asserts that the “switch” and “switch …
`
`associated with” claim language is indefinite.
`
` The “switch … associated with” claim language is indefinite because (a) it is unclear
`
`structurally what the switch is and (b) it is unclear where or how an association is made. ‘770
`
`patent, claim 1 (“the switch being associated with a bridge telephone number”); ‘105 patent and
`
`‘094 patent, claim 1 (“a switch associated with the server”); and ‘554 patent, claim 1:
`
`(“automatically associating the telephone access number with a switch associated with the
`
`server”).
`
`Plaintiff argues that “switch” refers to a class of structures and that “those structures are
`
`ordinarily associated with other elements on the network, including bridges, servers, and
`
`telephone numbers. Flypsi Responsive Br. at 23. Flypsi further asserts that associated with is a
`
`common phrase not needing construction. Id. at 20.
`
`Rather than ascribing a definite construction to “switch” and “switch … associated
`
`with,” Plaintiff and its expert cite a variety of extrinsic references seeking to show a switch is a
`
`class of structures which covers a variety of elements from mechanical devices, to electrical
`
`devices to software. Nettles Decl. at ¶¶ 48-49. Some example descriptions provided by Flypsi
`
`include “Ex. O at FLYP0004336 (‘Switches flexibly connect transmitters and receivers across
`
`networks of interconnected links, thereby allowing network resources to be shared by large
`
`numbers of end users. … There are a number of types of switches.’)”, “Ex. P (describing time-
`
`division digital switching systems)”, “Ex. Q at 0042 (describing call routing as employing ‘any
`
`number of network elements including routers, switches, hubs, etc.’)”, and “Any of various
`
`communication techniques that provide point to point transmission between dynamically
`
`7
`
`

`

`Case 6:21-cv-00642-ADA Document 33 Filed 01/14/22 Page 11 of 14
`
`
`
`changing data sources and sinks.” – A Dictionary of Computing (6th ed. 2008) (FLYP0004338).
`
`Flypsi Responsive Br. at 18; Nettles Decl. at ¶ 49. After listing various descriptions of switches
`
`from the various sources without further explanation, Plaintiff’s expert Dr. Nettles draws a
`
`conclusion that “a POSITA would be familiar with the concept of a switch.” Nettles Decl. at ¶
`
`51. He does not explain which “switch” description would fit his understanding of the switch
`
`from the asserted patents. He identifies no exemplary switch structure in the patent
`
`specifications. And, he identifies no language explaining how any association is made described
`
`in the patent specification, or what the nature of it is.
`
`Claims are indefinite under 35 U.S.C. § 112 (b) when they “fail to inform, with
`
`reasonable certainty, those skilled in the art about the scope of the invention.” Nautilus, Inc. v.
`
`Biosig Instruments, Inc., 134 S. Ct. 2120, 2124 (2014). The “switch … associated with” claim
`
`language is indefinite because a POSITA has no way of determining the true association or the
`
`type of network device Flypsi allges is the switch. This is similar to Dynamic Applet Techs.,
`
`LLC v. Mattress Firm, Inc. 2018 U.S. Dist. LEXIS 216894 (“[T]he claim scope is not reasonably
`
`certain because nothing prevents Plaintiff from strategically drawing boundaries in its analysis of
`
`an accused system.”). Accordingly, the claims should be found indefinite.
`
`There is a separate question of indefiniteness under section 112. The standard is
`
`“whether the words of the claim are understood by persons of ordinary skill in the art to have a
`
`sufficiently definite meaning as the name for structure.” Williamson v. Citrix Online, LLC, 792
`
`F.3d 1339, 1348 (Fed. Cir. 2015) (citing Greenberg v. Ethicon Endo-Surgery, Inc., 91 F.3d 1580,
`
`1583 (Fed. Cir. 1996)). “When a claim term lacks the word ‘means,’ the presumption can be
`
`overcome and § 112, para. 6 [or § 112(f)] will apply if the challenger demonstrates that the claim
`
`term fails to ‘recite sufficiently definite structure’ or else recites ‘function without reciting
`
`8
`
`

`

`Case 6:21-cv-00642-ADA Document 33 Filed 01/14/22 Page 12 of 14
`
`
`
`sufficient structure for performing that function.’” Williamson, 792 F.3d at 1348 citing (Watts v.
`
`XL Systems, Inc., 232 F.3d 877, 880 (Fed. Cir. 2001)).
`
`Here, Flypsi’s expert has identified possible definitions of “switch” from a mechanical
`
`actuator, to a network element, to a piece of software. This matches Dialpad’s extrinsic
`
`evidence, and establishes that switch does not have a definite meaning for conveying structure.
`
`Accordingly, the “switch … associated with” claim language requires reference to the patent
`
`specification to identify structure corresponding to the “associated with” function pursuant to 35
`
`U.S.C. § 112. Neither Flypsi nor its expert undertook to identify where the “associated with”
`
`function is described in the specification. It is not. Similarly, neither Flypsi nor its expert
`
`identified the corresponding switch structure in the specification, or any description in the
`
`specification, of where or how the association takes place.
`
`Accordingly, the “switch … associated with” claim language should be treated as means
`
`plus function claim language that is indefinite because it lacks structure corresponding to the
`
`“associated with” function in the specification.
`
`
`
`II.
`
`CONCLUSION
`
`For the foregoing reasons, Dialpad’s claim constructions should be adopted.
`
`
`
`Dated: January 14, 2021
`
`
`
`/s/ Elizabeth M. Chiaviello
`Elizabeth M. Chiaviello
`Texas Bar No. 24088913
`elizabeth.chiaviello@morganlewis.com
`MORGAN, LEWIS & BOCKIUS LLP
`1717 Main Street, Suite 3200
`Dallas, Texas 75201-7347
`T. (214) 466-4000
`F. (214) 466-4001
`
`Robert C. Bertin*
`
`9
`
`

`

`Case 6:21-cv-00642-ADA Document 33 Filed 01/14/22 Page 13 of 14
`
`D.C. Bar No. 469582
`robert.bertin@morganlewis.com
`MORGAN, LEWIS & BOCKIUS LLP
`1111 Pennsylvania Avenue, NW
`Washington, D.C. 20004
`Telephone: (202) 739-3000
`Facsimile: (202) 739-3001
`*Admitted pro hac vice
`Attorneys for Dialpad, Inc.
`
`
`
`
`
`
`
`10
`
`

`

`Case 6:21-cv-00642-ADA Document 33 Filed 01/14/22 Page 14 of 14
`
`
`
`CERTIFICATE OF SERVICE
`
`I hereby certify that a copy of the foregoing document was filed electronically in
`
`compliance with Local Rule CV-5. Therefore, this document was served on all counsel who are
`
`deemed to have consented to electronic service. Administrative Policies and Procedures for
`
`Electronic Filing in Civil and Criminal Cases, Western District of Texas, Section 14.
`
`
`
`/s/ Elizabeth M. Chiaviello
`Elizabeth M. Chiaviello
`
`
`11
`
`

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