throbber
Case 6:21-cv-00815-ADA Document 47 Filed 04/29/22 Page 1 of 12
`
`IN THE UNITED STATES DISTRICT COURT
`WESTERN DISTRICT OF TEXAS
`WACO DIVISION
`
`WAG ACQUISITION, L.L.C.,
`
`Case No. 6:21-cv-00815-ADA
`
`Plaintiff,
`
`v.
`
`AMAZON.COM, INC., AMAZON WEB
`SERVICES, INC., and AMAZON.COM
`SERVICES LLC.,
`
`Defendants.
`
`JURY TRIAL DEMANDED
`
`PLAINTIFF’S SUR-REPLY CLAIM CONSTRUCTION BRIEF
`
`Amazon / WAG Acquisition
`Exhibit 1013
`Page 1
`
`

`

`Case 6:21-cv-00815-ADA Document 47 Filed 04/29/22 Page 2 of 12
`
`TABLE OF CONTENTS
`
`
`
`
`
`I.
`
`II.
`
`
`
`
`A.
`B.
`C.
`D.
`
`DISPUTED CONSTRUCTIONS ....................................................................... 1
`“the media source” (’594 Patent, claims 1, 6, 11) ................................................. 1
`Patent, claims 1, 5, 9) ............................................................................................ 4
`claims 1, 5, 9) ........................................................................................................ 4
`construction proposed) .......................................................................................... 5
`CONCLUSION .................................................................................................... 7
`
`“playback rate” (’594 Patent, claims 1, 6, 11; ’824 Patent, claims 1, 5, 9; ’636
`
`“data rate” (’594 Patent, claims 1, 6, 11; ’824 Patent, claims 1, 5, 9; ’636 Patent,
`
`“as required to maintain about a predetermined number of media data elements”
`(’594 Patent, claims 1, 6, 11) (alleged indefinite, but with alternate (disputed)
`
`
`
`i
`
`Amazon / WAG Acquisition
`Exhibit 1013
`Page 2
`
`

`

`Case 6:21-cv-00815-ADA Document 47 Filed 04/29/22 Page 3 of 12
`
`
`
`TABLE OF AUTHORITIES
`
`Cases
`
`PAGE(S)
`
`
`Multiform Desiccants, Inc. v. Medzam, Ltd.,
`
`133 F.3d 1473 (Fed. Cir. 1998).......................................................................................... 1
`
`Oatey Co. v. IPS Corp.,
`
`514 F.3d 1271 (Fed. Cir. 2008).......................................................................................... 3
`
`Ortho-McNeil Pharm., Inc. v. Caraco Pharm. Labs., Ltd.,
`
`476 F.3d 1321 (Fed. Cir. 2007).......................................................................................... 5
`
`
`
`
`
`ii
`
`Amazon / WAG Acquisition
`Exhibit 1013
`Page 3
`
`

`

`Case 6:21-cv-00815-ADA Document 47 Filed 04/29/22 Page 4 of 12
`
`TABLE OF DISPUTED TERMS AND CONSTRUCTIONS
`
`WAG’s Proposed
`Constructions
`
`Amazons’s Proposed
`Constructions
`
`Item
`
`Item 1: “as required to
`maintain about a
`predetermined number of
`media data elements”
`
`ʼ594 Patent, claims 1, 6, 11.
`Item 2: “playback rate”
`
`’594 Patent, claims 1, 6, 11;
`’824 Patent, claims 1, 5, 9;
`’636 Patent, claims 1, 5, 9.
`Item 3: “data rate”
`
`’594 Patent, claims 1, 6, 11;
`’824 Patent, claims 1, 5, 9;
`’636 Patent, claims 1, 5, 9.
`Item 7: “the media source”
`
`ʼ594 Patent, claims 1, 6, 11.
`
`Plain and ordinary meaning.
`
`Indefinite under § 112.
`
`Plain and ordinary meaning.
`
`
`A rate at which the data is
`encoded for playback to a
`user.
`
`Plain and ordinary meaning.
`
`
`Plain and Ordinary Meaning
`
`The actual rate at which the
`data connection delivers data
`to the [media player /
`requesting user system] at any
`given time.
`The storage device or live
`source device from which the
`streaming material originates.
`
`iii
`
`Amazon / WAG Acquisition
`Exhibit 1013
`Page 4
`
`

`

`Case 6:21-cv-00815-ADA Document 47 Filed 04/29/22 Page 5 of 12
`
`I.
`
`DISPUTED CONSTRUCTIONS1
`
`A. “the media source” (’594 Patent, claims 1, 6, 11)
`
`The ’594 Patent, in its preamble, recites “a media source.” The word “source” is
`
`commonly understood to refer to a facility from which something comes or can be obtained. As
`
`argued in WAG’s Responsive Brief, on its face, this can be any source of media, i.e., any
`
`upstream source from which media comes.
`
`For methods and systems for a “media player to receive and play an audio or video
`
`program,” which is the subject matter of the claims of the ’594 Patent, the media source is
`
`wherever that player gets its media, regardless of where the media originated. That is the plain
`
`meaning of the term media source – the source of the media for the player in question.
`
`Contrary to Amazon’s argument (Amazon Reply Br. at 1), WAG is not re-writing the
`
`claims. The source of a player’s media is what sends media to the player. The player is not at all
`
`concerned with the original place from which the media may have originated, but rather just
`
`where it gets the media to play.
`
`Amazon’s interpretation that the “media source” must be the device that “originates” the
`
`media does not reflect the ordinary meaning of the word “source,” but rather a special, limited
`
`interpretation.
`
`However, any special meaning assigned to a term “must be sufficiently clear in the
`
`specification that any departure from common usage would be so understood by a person of
`
`experience in the field of the invention.” Multiform Desiccants, Inc. v. Medzam, Ltd., 133 F.3d
`
`1473, 1477 (Fed. Cir. 1998).
`
`1 WAG contends that, unless otherwise noted, the Disputed Terms may be construed consistently
`across the Asserted Patents.
`
`Plaintiff’s Sur-Reply Claim Construction Brief (Amazon)
`
` Page 1
`
`Amazon / WAG Acquisition
`Exhibit 1013
`Page 5
`
`

`

`Case 6:21-cv-00815-ADA Document 47 Filed 04/29/22 Page 6 of 12
`
`Amazon argues that the specification effectively redefined the term “source” as a result
`
`of having references to a server that captures data from a live performance as a “media source.”
`
`However, the mere fact that the specification refers in some examples to an originating
`
`source as a “media source” does not constitute a limiting definition of the term.
`
`Amazon would have the Court lose sight of the fact that the disclosure refers to two types
`
`of media, one being of a realtime nature (or live), and the other from a nonrealtime source such
`
`as a disk file. ’594 Patent, 5:33-38. The disclosure thus gives examples of two types of sources
`
`(as “source” is ordinarily understood). For example, it shows server 12, which acts as a source of
`
`media to user computer 18, as well as computer system 28, which originates live content and
`
`serves as a source to server 12. Id., 12:59-67. In the case of pre-recorded content, the description
`
`states that the server computer simply reads it from disk. Id., 8:2.
`
`The same disclosure goes on to refer to server 12 as “transmit[ting] the media data to one
`
`or more user computers 18.” Id., 13:24-25. Significantly (e.g., id., 11:7-19), the disclosure also
`
`refers to server 12 as a “source server,” clearly a usage of “source” in its ordinary sense, not
`
`limited as Amazon argues. Arguing that a “source server” that transmits media data to user
`
`computers is not a “media source” to those computers is splitting hairs far too finely for a
`
`limiting claim construction, especially one based on importing a limitation from the
`
`specification.
`
`Further, specifically with regard to the pull embodiment, the specification refers to a
`
`“media source” as a facility that performs “sequentially numbering the media data elements.” Id.,
`
`14:43-45. However, as in the earlier disclosure at 12:59-67, it is “[t]he server buffer manager, or
`
`the media source” that does this numbering—making clear that in the case of prerecorded media
`
`on disk, there need not be a separate “media source” that originates data. Id. In either case
`
`Plaintiff’s Sur-Reply Claim Construction Brief (Amazon)
`
` Page 2
`
`Amazon / WAG Acquisition
`Exhibit 1013
`Page 6
`
`

`

`Case 6:21-cv-00815-ADA Document 47 Filed 04/29/22 Page 7 of 12
`
`(separate “media source” or not), the description of the same embodiment goes on to say “the
`
`user computer transmits a request to the server to send one or more data elements, specifying the
`
`serial numbers of the data elements. The server responds by sending the requested data
`
`elements.” Id., 14:51-54. This is plainly a request by the client for media elements, and a
`
`response by the server sending the same—with the “server” thereby acting as a “source” of the
`
`media to the user computer, as that term is ordinarily understood.
`
` Amazon’s construction would also exclude disclosed embodiments (e.g., id., 12:59-67,
`
`14:51-54), where a relaying server acts as the source to the client (which performs no differently
`
`under the claims of the ’594 Patent depending on the “originality” of the source). See also id.,
`
`2:48-49 (“The media data is delivered by a server computer, which has available to it the source
`
`of the media data, such as by a connection to a radio station.”), 3:67-4:5 (addressing the pull
`
`embodiment, and stating that “the server may operate by … receiving requests from the user
`
`system for media data elements; and … sending media data elements to the user system
`
`responsive to said requests”), 6:42-44, 7:37-49 (moving “data window” on the server as the
`
`original source of the media), 7:51-54 (where the server receives the media from a real-time
`
`source), 8:1-2, 8:36-40. The argument appears to be that WAG was doing this to affirmatively
`
`limit the claims to the subject matter that pulls from the content originator. However, “it is
`
`incorrect to construe the claims to exclude … embodiment[s], absent probative evidence [to] the
`
`contrary” (Oatey Co. v. IPS Corp., 514 F.3d 1271, 1276-77 (Fed. Cir. 2008)), and Amazon’s
`
`evidence of particular examples of specific types of media “sources” are countered by other
`
`usages of the term that are not so limited. There is also no compelling (or indeed at all moving)
`
`linguistic basis for Amazon’s limited construction that would outweigh the numerous intrinsic
`
`Plaintiff’s Sur-Reply Claim Construction Brief (Amazon)
`
` Page 3
`
`Amazon / WAG Acquisition
`Exhibit 1013
`Page 7
`
`

`

`Case 6:21-cv-00815-ADA Document 47 Filed 04/29/22 Page 8 of 12
`
`indicators that the claims in question cover a process of pull-based streaming from any type of
`
`Internet source.
`
`Amazon’s construction also does not make sense for pre-recorded media. Where is it
`
`“originated” for purposes of this claim (and why would it be material so long as the server can
`
`access a copy)?
`
`In sum, Amazon’s proposed construction is an improper attempt to import a limitation
`
`from the specification into the claims.
`
`B. “playback rate” (’594 Patent, claims 1, 6, 11; ’824 Patent, claims 1, 5, 9; ’636 Patent,
`claims 1, 5, 9)
`
`Amazon’s proposed construction is a reasonable example of the prevalent usage of this
`
`term, except that the patent regarded this rate more as “the” rate at which data is encoded for
`
`playback to a user, rather than “a” rate.
`
`Since claim construction should preferably not depend on the details of technological
`
`implementation, and since the experts do not consider this term difficult to apply, the Court
`
`should simply adopt plain and ordinary meaning for this term.
`
`C. “data rate” (’594 Patent, claims 1, 6, 11; ’824 Patent, claims 1, 5, 9; ’636 Patent,
`claims 1, 5, 9)
`
`There are two rate-related aspects to these claims, which concern (a) the capacity of the
`
`connection (this limitation), and (b) the rate at which the connection is actually utilized to send
`
`or receive data (a separate limitation addressed by Amazon’s co-defendant, Google). Amazon’s
`
`construction of the “data rate” limitation would blur the two limitations, incorrectly putting
`
`considerations of “actual rate” “and any given time” into a limitation that on its face addresses a
`
`characteristic of the connection itself. The disclosure relates “data rate” to “bandwidth” (e.g.,
`
`’824 patent, 4:38-41), and addresses the “bandwidth capacity” of the data connection (id., 5:7-
`
`12; 4:47-49). The issue is simply how a POSITA would quantify the bandwidth of the given
`
`Plaintiff’s Sur-Reply Claim Construction Brief (Amazon)
`
` Page 4
`
`Amazon / WAG Acquisition
`Exhibit 1013
`Page 8
`
`

`

`Case 6:21-cv-00815-ADA Document 47 Filed 04/29/22 Page 9 of 12
`
`connection, a matter of plain and ordinary meaning. The other limitation (sending/receiving
`
`(depending on the claim) the media data elements “as fast as the connection will allow”), is a
`
`separate issue, not to be conflated with this limitation.
`
`D. “as required to maintain about a predetermined number of media data elements”
`(’594 Patent, claims 1, 6, 11) (alleged indefinite, but with alternate (disputed)
`construction proposed)
`
`As discussed in WAG’s Responsive Brief, “about” is interpreted in the technological
`
`context and depends on the underlying technological facts. See Ortho-McNeil Pharm., Inc. v.
`
`Caraco Pharm. Labs., Ltd., 476 F.3d 1321, 1326 (Fed. Cir. 2007).
`
`The purpose of maintaining “about a predetermined number of media data elements” in
`
`the user device buffer is clear. It is to ensure continuous playback. This is the context in the
`
`disclosure encompassing different types of media elements that may be queued up in a buffer,
`
`which could add up to aggregate totals (for the buffer level) that can vary, within bounds
`
`understood by a person of ordinary skill in the art. Amazon’s hyperbole aside, Mr. Teruya has
`
`provided testimony regarding how a person of ordinary skill in the art would read this term in the
`
`context of the asserted claims and the full intrinsic record. D.I. 38-1 (“Teruya Decl.”) ¶¶ 27-29.
`
`Variable Bit Rate encoding is disclosed in the specification. See ’594 Patent, 4:64-67
`
`(“Variable Bit Rate encoding uses a variable number of bits to represent sounds or video, with
`
`more bits required for complex material (e.g., symphonic sounds or action scenes) than for
`
`simple sounds, silence, or still scenes.”). The specification states: “Statements in this
`
`specification concerning ‘constant’ data rates and the like should be understood as subject to
`
`appropriate variation where VBR-encoded data may be involved.” Id., 5:3-6.
`
`As disclosed in the ’594 Patent, the object of the invention is to ensure “continuous and
`
`uninterrupted playback.” ’594 Patent, 4:6-12. This encompasses variably as well as constant
`
`encoded media, and the claims deal with this factor as well.
`
`Plaintiff’s Sur-Reply Claim Construction Brief (Amazon)
`
` Page 5
`
`Amazon / WAG Acquisition
`Exhibit 1013
`Page 9
`
`

`

`Case 6:21-cv-00815-ADA Document 47 Filed 04/29/22 Page 10 of 12
`
`As discussed in WAG’s Responsive Brief, the purpose of the buffers in the ’594 Patent,
`
`including the user-side buffer, is to ensure a steady flow of media for continuous playback. The
`
`disclosure states:
`
`As data is played out, the next sequential data elements are requested from the server in
`such a fashion as to approximately maintain the predetermined number of data elements
`in the user’s buffer.
`
`Id., 15:15-18. “Approximately” is equivalent to the claim term “about.” The player seeks to keep
`
`approximately about a predetermined number of media data elements in its buffer. There is a
`
`range in this process, because the size of the individual data elements in the buffer can vary. This
`
`consequence yields the “about.”
`
`Depending on the encoding scheme, there are typical, known bounds to the variation
`
`between bitrates in complicated / high bitrate portions of the media, such as the “action scenes”
`
`versus less complicated / low bitrate portions of the media, such as still scenes. The differential is
`
`a result of the encoding and is known to a POSITA, or easily determined from the specification
`
`for the encoding scheme or a sampling of typical content so encoded. This is the basis for the
`
`variability required in the “about a predetermined number of media data elements,” and it is a
`
`well-understood variation.
`
`Amazon makes the argument that the number of media data elements stored in the buffer
`
`is not necessarily related to the size of each element. Amazon Reply Br. at 7. This may be true if
`
`one is free to arbitrarily shrink the encoding, but this directly reduces reproduction quality. In the
`
`real world, where quality of the presentation is also sought to be maximized, the size and number
`
`of elements are obviously interrelated, as the entire purpose is to maintain a buffer sufficient to
`
`avoid running out of media due to irregular reception, while maintaining the highest quality
`
`possible. This is why the specification considers this a factor, and Amazon cannot explain it
`
`away by contrived argument.
`
`Plaintiff’s Sur-Reply Claim Construction Brief (Amazon)
`
` Page 6
`
`Amazon / WAG Acquisition
`Exhibit 1013
`Page 10
`
`

`

`Case 6:21-cv-00815-ADA Document 47 Filed 04/29/22 Page 11 of 12
`
`Thus, in the context of the claim and the entire record, when read by a POSITA, the term
`
`“about” has known bounds, based on the variability of the size of the media data elements due to
`
`the VBR encoding.
`
`A POSITA would understand this term. See Teruya Decl. ¶¶ 27-29.
`
`II.
`
`CONCLUSION
`
`For the foregoing reasons, the Court should construe each of the above-noted limitations
`
`to have its plain and ordinary meaning, which interpretation is consistent with the internal
`
`language of the claims themselves and the specification.
`
`
`
`
`Dated: April 29, 2022
`
`
`
`
`
`
`
`HALEY & OLSON, P.C.
`100 North Ritchie Road, Suite 200
`Waco, Texas 76712
`Tel: (254) 776-3336
`Fax: (254) 776-6823
`By: /s/ Brandon R. Oates
`Brandon R. Oates
`State Bar No. 24032921
`Email: boates@haleyolson.com
`
`
`OF COUNSEL:
`LISTON ABRAMSON LLP
`The Chrysler Building
`405 Lexington Ave, 46th Floor
`New York, New York 10174
`Tel: (212) 257-1630
`Ronald Abramson (Admitted pro hac vice)
`David G. Liston (Admitted pro hac vice)
`Ari J. Jaffess (Admitted pro hac vice)
`Alex G. Patchen (Admitted pro hac vice)
`M. Michael Lewis (Admitted pro hac vice)
`Gina K. Kim (State Bar No. 24097937)
`Email: docket@listonabramson.com
`
`
`Attorneys for Plaintiff WAG Acquisition, L.L.C.
`
`Plaintiff’s Sur-Reply Claim Construction Brief (Amazon)
`
` Page 7
`
`Amazon / WAG Acquisition
`Exhibit 1013
`Page 11
`
`

`

`Case 6:21-cv-00815-ADA Document 47 Filed 04/29/22 Page 12 of 12
`
`
`
`CERTIFICATE OF SERVICE
`
`The undersigned certifies that the foregoing document was filed electronically with the
`
`Clerk of Court using the CM/ECF system which will send notification of such filing to all
`
`counsel of record on April 29, 2022.
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`/s/ Brandon R. Oates .
`BRANDON R. OATES
`
`
`
`Amazon / WAG Acquisition
`Exhibit 1013
`Page 12
`
`

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