throbber
Case 6:20-cv-00272-ADA Document 91 Filed 03/22/23 Page 1 of 13
`
`IN THE UNITED STATES DISTRICT COURT
`FOR THE WESTERN DISTRICT OF TEXAS
`WACO DIVISION
`
`VOIP-PAL.COM, INC.,
`
`
`
`Plaintiff,
`
`v.
`
`CASE NO. 6:20-cv-00272-ADA
`
`AMAZON.COM, INC.,
`AMAZON.COM SERVICES LLC, and
`AMAZON WEB SERVICES, INC.,
`
`
`
`
`
`Defendants.
`
`
`
`AMAZON’S RESPONSE IN OPPOSITION TO PLAINTIFF VOIP-PAL.COM’S
`OPPOSED MOTION FOR PARTIAL RECONSIDERATION OF THE COURT’S
`CLAIM CONSTRUCTION ORDER
`
`161420276
`
`

`

`Case 6:20-cv-00272-ADA Document 91 Filed 03/22/23 Page 2 of 13
`
`TABLE OF CONTENTS
`
`PAGE
`
`I.
`
`II.
`
`INTRODUCTION .............................................................................................. 1
`
`LEGAL STANDARD ......................................................................................... 1
`
`III.
`
`ARGUMENT ...................................................................................................... 2
`
`A.
`
`The Court’s Construction Applies the Definition of “Routing
`Message” in the Specification, and VoIP-Pal’s Recycled
`Arguments Fail to Demonstrate Any Error. ............................................ 2
`
`1.
`
`2.
`
`None of VoIP-Pal’s References to the Specification
`Demonstrate any Error with the Court’s Claim
`Construction. ............................................................................... 3
`
`VoIP-Pal’s “Claim Differentiation” Argument Was
`Correctly Rejected by the Court. ................................................ 6
`
`IV.
`
`CONCLUSION ................................................................................................... 8
`
`
`
`
`
`161420276
`
`-i-
`
`

`

`Case 6:20-cv-00272-ADA Document 91 Filed 03/22/23 Page 3 of 13
`
`TABLE OF AUTHORITIES
`
`PAGE(S)
`
`CASES
`
`AstraZeneca Pharms. LP v. Handa Pharms., LLC,
`No. A-10-CA-259-LY, 2010 WL 11506721 (W.D. Tex. July 27, 2010) ..................................7
`
`Krim v. pcOrder.com, Inc.,
`212 F.R.D. 329 (W.D. Tex. 2002) .............................................................................................7
`
`Marine Polymer Techs. Inc. v. HemCon, Inc.,
`672 F.3d 1350 (Fed. Cir. 2012)..................................................................................................6
`
`Unification Techs. LLC v. Micron Tech., Inc.,
`No. 6:20-cv-00500-ADA, 2021 WL 9950497 (W.D. Tex. July 16, 2021) ................................2
`
`World Class Tech. Corp. v. Ormco Corp.,
`769 F.3d 1120 (Fed. Cir. 2014)..............................................................................................6, 7
`
`
`
`161420276
`
`-ii-
`
`

`

`Case 6:20-cv-00272-ADA Document 91 Filed 03/22/23 Page 4 of 13
`
`
`
`I.
`
`INTRODUCTION
`
`In its motion for reconsideration, VoIP-Pal fails to identify any change in law, any new
`
`facts, or any manifest error of law or fact. Instead, VoIP-Pal rehashes its prior arguments and asks
`
`the Court to reach a different conclusion. That is not a proper basis for reconsideration.
`
`The Court correctly held that the “routing message” in the ’606 patent1 is defined to include
`
`a time-to-live field, and VoIP-Pal has not demonstrated any error in that holding. VoIP-Pal once
`
`again relies instead on inaccurate or incomplete descriptions of the patent specification, and it
`
`repeats the claim differentiation argument that it raised for the first time at oral argument and
`
`Amazon nevertheless refuted by walking through the multiple differences between the ’606 pa-
`
`tent’s claims and those of VoIP-Pal’s other related patents.
`
`Remarkably, VoIP-Pal also argues that the parties “did not focus their arguments on
`
`whether the TTL field should be excluded from the final construction of ‘routing message.’” (Mot.
`
`at 2.) But that was the central disputed issue for the only claim limitation argued at the Markman
`
`hearing, with counsel for both parties and the Court extensively discussing the time-to-live field.
`
`(See, generally, Ex. A (Markman hearing transcript).)2 The Court decided that issue in Amazon’s
`
`favor, and VoIP-Pal has identified no basis to disturb that ruling.
`
`VoIP-Pal’s motion for reconsideration should therefore be denied.
`
`II.
`
`LEGAL STANDARD
`
`In addressing another motion to reconsider a claim construction order, this Court noted that
`
`a court “should not revisit its prior decisions in the absence of extraordinary circumstances such
`
`
`1 U.S. Patent No. 10,218,606.
`2 Unless otherwise noted, all Exhibits referenced herein refer to the Declaration of Daniel T.
`Shvodian in Support of Amazon’s Response in Opposition to Plaintiff VoIP-Pal.com’s Opposed
`Motion for Partial Reconsideration of Claim Construction Order.
`
`161420276
`
`-1-
`
`

`

`Case 6:20-cv-00272-ADA Document 91 Filed 03/22/23 Page 5 of 13
`
`
`
`as where the initial decision was clearly erroneous and would work a manifest injustice.” Unifi-
`
`cation Techs. LLC v. Micron Tech., Inc., No. 6:20-cv-00500-ADA, 2021 WL 9950497, at *1 (W.D.
`
`Tex. July 16, 2021) (internal quotation omitted). Instead, reconsideration is “an extraordinary
`
`remedy that should be used sparingly,” and motions for reconsideration “are not the proper vehicle
`
`for rehashing evidence, legal theories, or arguments that could have been offered or raised before
`
`entry of judgment.” Id. (internal quotations omitted.) Furthermore, “[a] motion that repeats pre-
`
`viously advanced arguments and case law that was available at the time of the original briefing is
`
`insufficient to justify revisiting an issued order.” Id.
`
`III. ARGUMENT
`
`A.
`
`The Court’s Construction Applies the Definition of “Routing Message” in the
`Specification, and VoIP-Pal’s Recycled Arguments Fail to Demonstrate Any
`Error.
`
`As Amazon explained in its Opening Claim Construction Brief (ECF No. 65 at 11) and at
`
`the oral argument (Ex. A at 4:12-5:23), the ’606 patent defines “routing message” by stating that
`
`a “generic” routing message has three non-optional fields – a callee username field, a route field,
`
`and a time-to-live field (’606 patent at 21:47-60; id. at Fig. 15). A generic routing message does
`
`not describe just a single embodiment but rather indicates the characteristics of all routing mes-
`
`sages. (ECF No. 65 at 11-12.) Consistent with that definition, Amazon demonstrated that every
`
`embodiment of the invention in the ’606 patent disclosed a routing message that contained all three
`
`of those non-optional fields. Amazon further demonstrated that while the Summary of the Inven-
`
`tion repeatedly used permissive language to describe different features, the Summary did not use
`
`permissive language when describing that the routing message contains those three required fields.
`
`(Ex. A at 6:11-7:6.)
`
`The parties fully briefed this issue, with Amazon submitting opening and reply briefs (ECF
`
`No. 65 at 11-13; ECF No. 71 at 6-7) and VoIP-Pal submitting response and sur-reply briefs (ECF
`
`161420276
`
`-2-
`
`

`

`Case 6:20-cv-00272-ADA Document 91 Filed 03/22/23 Page 6 of 13
`
`
`
`No. 69 at 13-15; ECF No. 72 at 6-7.) The issue was also discussed extensively at the Markman
`
`hearing. (See generally Ex. A (discussing throughout the hearing whether “routing message” in-
`
`cludes a time-to-live field).) At the conclusion of that hearing, the Court held that “the construction
`
`of ‘routing message’ should include a message that includes a callee username, a route field and a
`
`time to live field.” (Id. at 25:25-26:3.) In asking the Court to revisit that ruling, VoIP-Pal does no
`
`more than reiterate the same arguments it presented—and the Court rejected—the first time
`
`around.
`
`1.
`
`None of VoIP-Pal’s References to the Specification Demonstrate any
`Error with the Court’s Claim Construction.
`
`VoIP-Pal first argues that the time-to-live field “concerns a billing-related concept, inde-
`
`pendent from the callee and route fields.” (Mot. at 4.) Even if that were true,3 it would not change
`
`that “routing message” is defined to contain all three fields, that the summary of the invention says
`
`that it contains all three fields, and that every disclosed embodiment of a routing message contains
`
`all three fields. The invention made and conveyed to the public through the specification controls
`
`when construing the claims.
`
`VoIP-Pal next asserts that the time to live is not an essential aspect of routing a call and
`
`that “there is an entire section of the specification devoted to determining TTL that has nothing to
`
`do with routing.” (Mot. at 4.) As support for that assertion, VoIP-Pal cites 28:45-31:40 of the
`
`’606 patent. (Id. at n.14.) But immediately following that section of the specification is a discus-
`
`sion of how to calculate the “cost per second” for a call. (’606 patent at 31:41-34:51.) The time
`
`
`3 VoIP-Pal’s assertion that a call’s time to live is independent of the route is not true because
`calculating the time to live for a particular call depends in part on the route of the call and the costs
`per second for communicating over that route. (See, e.g., ’606 patent at 30:47-64 (explaining that
`the time to live depends, in part, on the cost per second for a call); id. at 31:41-61 (explaining that
`cost per second depends on the route).)
`
`161420276
`
`-3-
`
`

`

`Case 6:20-cv-00272-ADA Document 91 Filed 03/22/23 Page 7 of 13
`
`
`
`to live depends, in part, on the cost per second for a call (’606 patent at 30:47-64) and the cost per
`
`second depends, in part, on the call route (see, e.g., id. at 31:41-46). Thus, contrary to VoIP-Pal’s
`
`assertion, there is a direct relationship between the time to live and the route.
`
`VoIP-Pal then incorrectly asserts that the time-to-live field is used only in one embodiment
`
`of the invention. (Mot. at 4.) But as Amazon demonstrated previously, every embodiment of a
`
`“routing message” disclosed in the patent includes a time-to-live field4, for example:
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`4 The ’606 patent does not disclose a single embodiment of a routing message that excludes a
`time-to-live field or states that it is optional. While not every single mention of a routing message
`in the specification is followed by the statement that it contains a time-to-live field, that does not
`constitute a disclosure of an embodiment lacking a time-to-live field.
`
`161420276
`
`-4-
`
`

`

`Case 6:20-cv-00272-ADA Document 91 Filed 03/22/23 Page 8 of 13
`
`
`
`
`(See also ’606 patent at 6:1-11, 11:45-50, 12:1-4, 12:19-21, 21:11-29, 21:47-51, 21:61-22:2,
`
`
`
`25:11-60, 27:31-43 (all discussing a routing message that includes the time-to-live field).)
`
`While VoIP-Pal points out that some calls may be free (Mot. at 4-5), the patent never says
`
`that a routing message for such calls can exclude a time-to-live field. Instead, the ’606 patent
`
`explains that the time-to-live field for such calls is set to its maximum value, effectively placing
`
`no limit on the call’s duration. (See, e.g., ’606 patent at 21:10-29, 28:60-66, 29:66-30:1, 30:40-
`
`45, Fig. 8A (block 350), Fig. 16, Fig. 33A (block 702).) That routing messages for free calls still
`
`include a time-to-live field further confirms that the field is a non-optional part of the “routing
`
`message.” VoIP-Pal argues that the specification does not discuss “computing” the time to live in
`
`a section titled “Subscriber to Subscriber Calls Between Different Nodes” (Mot. at 5), but that is
`
`misleading because the time to live for such intra-network calls does not need to be computed.
`
`Instead, as with the other free calls, the specification explains that time to live for such a call is set
`
`to the maximum value (’606 patent at 21:24-29), once again confirming that the time-to-live field
`
`is a non-optional part of every routing message.
`
`Finally, VoIP-Pal quotes another portion of the specification, asserting that it shows the
`
`time-to-live field is not used to route a message. (Mot. at 5-6 (quoting ’606 patent at 27:40-59).)
`
`That part of the specification begins “Referring back to FIG. 1, the routing message whether of the
`
`type shown in FIG. 16, 25 or 32, is received at the call controller . . . .” (’606 patent at 27:40-42).
`
`As shown in the figures above, each of those routing messages in Figures 16, 25, and 32 includes
`
`161420276
`
`-5-
`
`

`

`Case 6:20-cv-00272-ADA Document 91 Filed 03/22/23 Page 9 of 13
`
`
`
`a time-to-live field, thus further confirming that the time to live field is a non-optional portion of
`
`the “routing message.”
`
`2.
`
`VoIP-Pal’s “Claim Differentiation” Argument Was Correctly
`Rejected by the Court.
`
`While VoIP-Pal did not raise a claim differentiation argument in either of its Markman
`
`briefs (see ECF No. 69 at 13-15; ECF No. 72 at 6-7), it did raise such an argument at the Markman
`
`hearing. (Ex. A at 15:4-6 (“And Your Honor, we recognize that we are -- that what I’ve just
`
`showed is effectively a claim differentiation argument.”).) At the hearing, Amazon refuted VoIP-
`
`Pal’s untimely claim differentiation argument by demonstrating that there were other limitations
`
`added in the cited dependent claims, thus completely undercutting VoIP-Pal’s argument that the
`
`time-to-live field was the basis for differentiating the independent and dependent claims. (Ex. A
`
`at 23:7-24:5.) World Class Tech. Corp. v. Ormco Corp., 769 F.3d 1120, 1125-26 (Fed. Cir. 2014)
`
`(holding that claim differentiation did not apply where the dependent claim contained other limi-
`
`tations on its scope); see also Marine Polymer Techs., Inc. v. HemCon, Inc., 672 F.3d 1350, 1359
`
`(Fed. Cir. 2012) (“[C]laim differentiation is not a hard and fast rule and will be overcome by a
`
`contrary construction dictated by the written description or prosecution history.”) (internal quota-
`
`tion omitted).
`
`In its motion for reconsideration, VoIP-Pal rehashes this same argument. Just as it did at
`
`the Markman hearing (Ex. A at 14:20-25; Ex. B at slides 10-11), VoIP-Pal points to independent
`
`claim 1 and dependent claim 18 of U.S. Patent No. 9,179,005 (“the ’005 patent”). (Mot. at 7-8.)
`
`But claim 18 of the ’005 patent recites that the routing message contains both a “time value” (which
`
`is the time to live) and a “timeout value,” which holds a different time measurement. (Mot. at 8
`
`(quoting claim 18 of the ’005 patent).) Because claim 18 recites the additional “timeout value,”
`
`which is not one of the mandatory fields of the generic routing message, VoIP-Pal’s argument that
`
`161420276
`
`-6-
`
`

`

`Case 6:20-cv-00272-ADA Document 91 Filed 03/22/23 Page 10 of 13
`
`
`
`the time-to-live limitation must differentiate the inventions recited in claims 1 and 18 fails. World
`
`Class Tech., 769 F.3d at 1125-26.
`
`In its slides for the Markman hearing, VoIP-Pal also quoted the entirety of claim 1 of U.S.
`
`Patent No. 11,171,864 (“the ’864 patent”), though VoIP-Pal’s counsel chose not to address that
`
`claim during the argument. (Ex. B at slide 12.) In its motion for reconsideration, VoIP-Pal now
`
`addresses claim 1 of the ’864 patent to argue that the claims of that patent “are specifically directed
`
`to producing a routing message that includes a TTL field for holding a maximum allowable time
`
`for a communications session to be conducted.” (Mot. at 7.) But claim 1 recites much more than
`
`just that,5 as it sets forth a detailed method for calculating the time to live. (Ex. B at slide 12.)
`
`That the ’864 patent claims a detailed method for calculating the time to live provides no support
`
`for VoIP-Pal’s argument that the time-to-live field is not a mandatory part of the “routing message”
`
`recited in the ’606 patent.
`
`VoIP-Pal also improperly presents for the first time (Mot. at 6-7) a list of titles from patents
`
`related to the ’606 patent and a written opinion of the PCT international searching authority, all of
`
`which was available to VoIP-Pal at the time of the original briefing. AstraZeneca Pharms. LP v.
`
`Handa Pharms., LLC, No. A-10-CA-259-LY, 2010 WL 11506721, at *1 (W.D. Tex. July 27,
`
`2010) (“As various district court judges have eloquently stated, motions to reconsider based on
`
`recycled arguments only serve to waste the resources of the court, and are not the proper vehicle
`
`to rehash old arguments or advance legal theories that could have been presented earlier.”) (in-
`
`ternal quotations omitted, emphasis added); Krim v. pcOrder.com, Inc., 212 F.R.D. 329, 331 (W.D.
`
`Tex. 2002) (explaining that motions for reconsideration “serve a narrow purpose: to permit a party
`
`
`5 While VoIP-Pal’s motion quotes just a small portion of claim 1 of the ’864 patent (Mot. at 7-
`8), the entirety of the claim sets forth a detailed method of calculating the time to live, as shown
`in VoIP-Pal’s Markman hearing slides (Ex. B at 12).
`
`161420276
`
`-7-
`
`

`

`Case 6:20-cv-00272-ADA Document 91 Filed 03/22/23 Page 11 of 13
`
`
`
`to correct manifest errors of law or fact, or to present newly discovered evidence”) (emphasis
`
`added). The titles of the various patents and the fact that some of the patents, such as the ’864
`
`patent, recite detailed methods for calculating the time to live, in no way refutes that the time to
`
`live is a mandatory part of the “routing message.” Similarly, that the PCT opinion divided the
`
`claims into groups, including claims directed to:
`
`• “a call routing controller for facilitating communications between callers and
`callees in a communications system comprising a plurality of nodes in which,
`in response to initiation of a call, uses call classification criteria to classify the
`call as a public network call or a private network call, and produces accordingly
`a routing message;” and
`
`• “determining a time to permit a communication session to be conducted, the
`determination based on calculating a cost per unit time, a participant’s billing
`pattern, and the quotient of a funds balance held by the participant.”
`
`(ECF No. 89-4 at 3.) That the later claims were directed to a detailed method of calculating a time
`
`to live does not mean that the routing message does not include a mandatory time-to-live field, and
`
`nothing in that PCT document suggests that the international authority construed any term, much
`
`less did so according to U.S. patent law.
`
`IV. CONCLUSION
`
`VoIP-Pal’s motion for reconsideration just repackages arguments the Court has already
`
`rejected. VoIP-Pal has not identified any basis for the Court to revisit its construction of “routing
`
`message,” nor has it identified any error in that construction. VoIP-Pal’s motion should be denied.
`
`
`
`161420276
`
`-8-
`
`

`

`Case 6:20-cv-00272-ADA Document 91 Filed 03/22/23 Page 12 of 13
`
`
`
`Dated: March 22, 2023
`
`
`
`
`
`
`Respectfully submitted,
`
`/s/ Daniel T. Shvodian
`
`M. Craig Tyler, Bar No. 00794762
`Perkins Coie LLP
`500 W 2nd St, Suite 1900
`Austin, TX 78701-4687
`Tel. No. 737.256.6113
`Fax No. 737.256.6300
`
`Daniel T. Shvodian, Admitted Pro Hac Vice
`Christopher Kelley, Admitted Pro Hac Vice
`Perkins Coie LLP
`3150 Porter Drive
`Palo Alto, CA 94304-1212
`Tel. No. 650.838.4300
`Fax No. 650.838.4350
`
`ATTORNEYS FOR DEFENDANTS
`Amazon.com, Inc.; Amazon.com Services
`LLC; and Amazon Web Services, Inc.
`
`161420276
`
`-9-
`
`

`

`Case 6:20-cv-00272-ADA Document 91 Filed 03/22/23 Page 13 of 13
`
`
`
`CERTIFICATE OF SERVICE
`
`The undersigned hereby certifies that a true and correct copy of the above and foregoing
`
`document has been served March 22, 2023 to all counsel of record, via the Court’s CM/ECF
`
`system.
`
`
`
`/s/ Daniel T. Shvodian
`Daniel T. Shvodian
`
`
`
`161420276
`
`

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