throbber
UNITED STATES PATENT AND TRADEMARK OFFICE
`
`UNITED STATES DEPARTMENT OF COMMERCE
`United States Patent and Trademark Office
`Address: COMMISSIONERFORPATENTS
`P.O. Box 1450
`Alexandria, Virginia 22313-1450
`www.uspto.gov
`
`APPLICATION NO.
`
`FILING DATE
`
`FIRST NAMED INVENTOR
`
`ATTORNEY DOCKET NO.
`
`CONFIRMATION NO.
`
`90/014,834
`
`08/25/2021
`
`8122141
`
`125737.538655
`
`8070
`
`10/05/2023
`
`7590
`ERNEST D. BUFF
`ERNEST D. BUFF & ASSOCIATES
`231 SOMERVILLE ROAD
`BEDMINSTER, NJ 07921
`
`EXAMINER
`
`FERRIS III, FRED 0
`
`ART UNIT
`
`PAPER NUMBER
`
`3992
`
`MAIL DATE
`
`DELIVERY MODE
`
`10/05/2023
`
`PAPER
`
`Please find below and/or attached an Office communication concerning this application or proceeding.
`
`The time period for reply, if any, is set in the attached communication.
`
`PTOL-90A (Rev. 04/07)
`
`Petitioner's Exhibit 1117
`IPR2022-01413 - Page 001
`
`

`

`RECORD OF ORAL HEARING
`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`Ex parte WAG ACQUISITION, LLC
`
`Appeal 2023-002525 (Reexamination Control 90/014,833)
`Appeal 2023-003028 (Reexamination Control 90/014,836)
`Appeal 2023-003319 (Reexamination Control 90/014,834)
`Technology Center 3900
`
`Oral Hearing Held: September 18, 2023
`
`Before JOHN A. JEFFERY, ERIC B. CHEN, and
`BRIAN J. MCNAMARA, Administrative Patent Judges.
`
`APPEARANCES:
`
`ON BEHALF OF THE APPELLANTS:
`
`RONALD ABRAMSON, ESQUIRE
`Liston Abramson LLP
`The Chrysler Building
`405 Lexington Avenue, 46th Floor
`New York, New York 10174
`
`The above-entitled matter came on for hearing on Monday, September
`18, 2023, commencing at 1:00 p.m., at the U.S. Patent and Trademark
`Office, 600 Dulany Street, Alexandria, Virginia.
`
`Petitioner's Exhibit 1117
`IPR2022-01413 - Page 002
`
`

`

`Appeal 2023-002525 (Reexamination Control 90/014,833)
`Appeal 2023-003028 (Reexamination Control 90/014,836)
`Appeal 2023-003319 (Reexamination Control 90/014,834)
`
`PROCEEDINGS
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`JUDGE CHEN: Okay, Mr. Abramson, welcome to the board. This is
`
`Judge Chen, and with me today are Judges Jeffery and McNamara. Before
`
`we get started,just a few administrative matters. Number one, if you're not
`
`speaking, please mute yourself. Number two -- number two, please identify
`
`yourself each time you speak. This helps the court reporter prepare an
`
`accurate transcript. Number three, we have the entire record before us,
`
`including demonstratives.
`
`If you are identifying demonstrative by page number, please provide a
`
`few seconds for us to access that document. And lastly, please be aware that
`
`members of the public may be listening in on this oral hearing. That being
`
`said, please state your name and law form for the record.
`
`MR. ABRAMSON: Ronald Abramson, Liston Abramson LLP.
`
`JUDGE CHEN: Okay. Thank you, Mr. Abramson. You have about 20
`
`minutes, and you may begin. And just initially for, excuse me. This is
`
`Appeal Number 2023-002525. Mr. Abramson, you may begin when you're
`
`ready. And we would ask that you -- we're particularly interested in the Hill
`
`reference with respect to this appeal. So, if you need a few minutes to
`
`organize your notes, we can provide that for you.
`
`MR. ABRAMSON: Yeah, the notice I got was all three appeals
`
`combined, so we're doing them one by one. Which one are we -- which one
`
`is this?
`
`JUDGE CHEN: Okay, this is 2023-2525. Do you have -- we can be
`
`flexible here. Do you want to address -- is there any particular order you'd
`
`2
`
`Petitioner's Exhibit 1117
`IPR2022-01413 - Page 003
`
`

`

`Appeal 2023-002525 (Reexamination Control 90/014,833)
`Appeal 2023-003028 (Reexamination Control 90/014,836)
`Appeal 2023-003319 (Reexamination Control 90/014,834)
`
`1
`
`2
`
`like to proceed in?
`
`MR. ABRAMSON: Well, let's just make sure we have on the table here,
`
`3 we have three reexaminations that are on appeal here. And you go by the
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`patent number. There's an '839 patent, there's a '141 patent, and there's an
`
`'011 patent. Let's see which appeal --
`
`ruDGE CHEN: Sorry. Excuse me, okay, I'm going by appeal
`
`number. So, calendar number one would be the -- is the '011 patent.
`
`MR. ABRAMSON: Yeah. And then we also have the '141 and the
`
`'839.
`
`ruDGE CHEN: Okay, which one would you like to do first?
`
`MR. ABRAMSON: I was planning on starting with the '839. And let
`
`12 me tell you what I think the deal number is. It says this appearing --
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`mDGE CHEN: You're going by patent numbers; is that correct?
`
`MR. ABRAMSON: Yeah--yeah. Jeez -- I don't even know what--
`
`says Appeal Number --
`
`mDGE CHEN: '839.
`
`MR. ABRAMSON: Yeah, it says 3028. It's 2023-3028.
`
`mDGE CHEN: Okay, you want to do that one first?
`
`MR. ABRAMSON: Yeah, I think that's going to take the most time.
`
`mDGE CHEN: 3028.
`
`MR. ABRAMSON: Yes, 3028. Correct. And then --
`
`mDGE CHEN: Okay. That is --
`
`MR. ABRAMSON: -- by process of elimination. I don't know what
`
`the last one is but --
`
`3
`
`Petitioner's Exhibit 1117
`IPR2022-01413 - Page 004
`
`

`

`Appeal 2023-002525 (Reexamination Control 90/014,833)
`Appeal 2023-003028 (Reexamination Control 90/014,836)
`Appeal 2023-003319 (Reexamination Control 90/014,834)
`
`JUDGE CHEN: Okay, so 3028 is calendar number three, and this is --
`
`that's the one with the Chen reference; is that correct? And the Chen
`
`prosecution history?
`
`MR. ABRAMSON: Correct.
`
`JUDGE CHEN: Okay, so in the interest of flexibility, we shall begin
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6 with Appeal Number 2023-003028.
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`MR. ABRAMSON: Thank you.
`
`JUDGE CHEN: Okay, so you may begin when ready.
`
`MR. ABRAMSON: Okay, so the three appeals today involve expired
`
`patents. The patents and reexamination cover two separately claimed
`
`embodiments derived from a common disclosure. And right now, we're
`
`addressing one of those that -- that the different -- two different
`
`embodiments may be referred to as push and pull. There's a common
`
`concept behind the two embodiments which is in this process of streaming,
`
`how do you quickly pre-establish on the client side of the connection a
`
`buffer of streaming media data elements? In the simplest formulation,
`
`17 media could be streamed by simply continuously pushing it out over the
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`connection to the client at about the rate that it'll be played back. Simplest
`
`concept is just send it over the line at the same rate that it's going to be
`
`played back, the client receives it and plays it back, and that's it.
`
`JUDGE CHEN: Mr. Abramson, this is Judge Chen. Just a brief
`
`question. Is push or pull actually claimed?
`
`MR. ABRAMSON: No, not in those terms, no. But it's a concept that
`
`underlies that's the way people refer to these things. They're not claimed
`
`terms. But I'm just giving you a little background here. You know, in the
`
`4
`
`Petitioner's Exhibit 1117
`IPR2022-01413 - Page 005
`
`

`

`Appeal 2023-002525 (Reexamination Control 90/014,833)
`Appeal 2023-003028 (Reexamination Control 90/014,836)
`Appeal 2023-003319 (Reexamination Control 90/014,834)
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`simplest formulation, you push things at the playback rate, everything is
`
`great because client gets it at the playback rate and plays it back. But in
`
`practice, over the internet, things are not that simple. The Internet -- the
`
`Internet sends the constituent elements of a stream individually but sends
`
`each one only on a best efforts basis.
`
`So, because of that, the Internet is subject to irregularity in delivering
`
`a stream of data, any stream of data. That's just inherent in the Internet. So,
`
`as the '839 patent explains, it was known that having a buffer, establishing a
`
`buffer on the client side to receive elements, could provide limited
`
`10
`
`protection against delivery disruptions like a gas tank. But that in itself
`
`11 would be effective only for so long that the accumulated amount of the
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`disruption as streaming went on was less than the size of the buffer. Once
`
`you used up that buffer, you are out there without a buffer. There's no way
`
`to -- there's no way to replenish it if the elements are just arriving at the rate
`
`you're going to play it. Once you've used up that buffer, you're done. Any
`
`further interruptions is going to result in dropout.
`
`As the '839 patent explained, there were such buffers, but they were
`
`not -- they were not effective for the duration of streaming. The result of
`
`doing it in the prior art way was first of all, there was a startup delay to first
`
`build up the client-side buffer before beginning playback and repeated
`
`delays during playback for rebuffering. What was not known at the time
`
`22 was a simple mechanism to establish a robust client-side buffer in the first
`
`23
`
`24
`
`25
`
`place without having a long buffering delay before playback, as well as how
`
`to quickly rebuild that buffer without repeated buffering interruptions if the
`
`buffer became depleted during the course of streaming.
`
`5
`
`Petitioner's Exhibit 1117
`IPR2022-01413 - Page 006
`
`

`

`Appeal 2023-002525 (Reexamination Control 90/014,833)
`Appeal 2023-003028 (Reexamination Control 90/014,836)
`Appeal 2023-003319 (Reexamination Control 90/014,834)
`
`1
`
`The '839 patent claims a push implementation for such a
`
`2 mechanism. And I'm using the word push here, just conceptually, so you
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`can separate it from the other embodiments that we'll discuss in the other
`
`appeals, which we call pull. So far, we've been talking about a client-side
`
`buffer. The only buffer I've mentioned so far is a client-side buffer. But the
`
`'839 patent starts with preloading a buffer on the server side. What's that
`
`about? In the case of a live stream, that fully loaded buffer, if you're
`
`receiving a live stream, that fully loaded buffer can already exist 100 percent
`
`9 when the user connects to the stream. It's just coming in continuously to a
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`broadcast station when a user connects. The server already has a full buffer
`
`because the stream has been coming in live. If you're working from
`
`prerecorded media and you're serving it on demand, when the player wants
`
`to see a program, you do have to load the server buffer, but that can be done
`
`at discrete speed, which is much faster than playback rate. It's not a
`
`significant delay.
`
`So, either way, live or prerecorded, it is practicable to start with a full
`
`buffer and to do so with little, if any delay. So, this reexamination concerns
`
`claim 2 of the '839 patent. However, by dependency, claim 1 is part of
`
`claim 2. So, I will go over claim 1 first. Claim l's preamble posits both a
`
`user system assumed to have a user buffer as well as a server having a server
`
`buffer. Claim 1 recites as its first method step, loading the server buffer
`
`22 with streaming media data elements. Per the '839 patent, the connection
`
`23
`
`24
`
`between the server and the user will have a capacity much faster than the
`
`playback rate.
`
`6
`
`Petitioner's Exhibit 1117
`IPR2022-01413 - Page 007
`
`

`

`Appeal 2023-002525 (Reexamination Control 90/014,833)
`Appeal 2023-003028 (Reexamination Control 90/014,836)
`Appeal 2023-003319 (Reexamination Control 90/014,834)
`
`1
`
`The citations are in our brief, I can refer them to you if you
`
`2 want. When the user connects, the initial buffer load in this step can be sent
`over to the client side as fast as the connection will allow, as claim 1
`
`3
`
`4
`
`5
`
`states. And the next thing in claim 1, "sending an initial amount of
`
`streaming media data elements to the user system and an initial sending rate
`
`6 more rapid than the playback rate." And further, as recited in claim 1, the
`
`7
`
`8
`
`9
`
`initial amount, I'm quoting again, "the initial amount of streaming media
`
`data elements and the initial sending rate are sufficient for the user system to
`
`begin playing back the streaming media while the user buffer continues to
`
`10
`
`fill." That much of claim 1 takes care of the fast startup. Now we tum to
`
`11 what happens after a streaming startup and claim 1 continues.
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`JUDGE JEFFERY: Counsel, excuse me. This is Judge Jeffery here. I
`
`have one question about claim 1 while we're on the subject. In line 1 it says
`
`a method for distributing streaming media via the interact that should be
`
`Internet, right?
`
`MR. ABRAMSON: Yes. Nobody ever disputed that.
`
`JUDGE JEFFERY: Okay, I just want to clarify the record.
`
`MR. ABRAMSON: No, thank you. Now I tum to what happens after
`
`streaming startup. "thereafter," that's after this initial amount is sent faster
`
`than your playback rate, to fill -- well, to get -- for the user system, the user
`
`system can begin to play. Now we go, "thereafter sending further stream
`
`22 media data elements to the user system at about the playback rate and filling
`
`23
`
`24
`
`the server buffer or moving a data window through the server buffer at about
`
`the playback rate."
`
`7
`
`Petitioner's Exhibit 1117
`IPR2022-01413 - Page 008
`
`

`

`Appeal 2023-002525 (Reexamination Control 90/014,833)
`Appeal 2023-003028 (Reexamination Control 90/014,836)
`Appeal 2023-003319 (Reexamination Control 90/014,834)
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`So, after that initial burst thereafter we're sending further elements at
`
`about the playback rate while we're refilling the server buffer at the
`
`playback rate. So it adds -- it adds, "wherein the further streaming media
`
`data elements are received at about the playback rate by the user system if
`
`there are no interruptions between the transmission of, excuse me, in the
`
`transmission of streaming media data elements between the server and the
`
`user system." So, taking together the words following thereafter describe a
`
`pass-through situation after startup. In effect, a pipeline of media flowing at
`
`the playback rate so long as there are no interruptions in transmission.
`
`The words filling the server buffer at about the playback rate reflect
`
`elements coming into this pipeline at about the playback rate. Absent
`
`interruptions, these elements are passed through and then received at the
`
`playback rate. This is referred -- this is referred to in specification as a
`
`steady state. Specification uses the word steady state to describe that
`
`situation after startup without interruptions. Finally, claim 1 recites the step
`
`of the server detecting the interruptions have occurred. So, claim 1 itself
`
`does not get into what to do about the interruptions.
`
`Claim 2, as I said, claim 2 is a claim that's subject to this
`
`reexamination. Claim 2 reads, "the method of claim 1 further comprising
`
`sending to the user system unsent streaming media data elements in the
`
`server buffer at a sending rate more rapid than the playback rate." A key
`
`issue on this appeal is claim construction. First, let me address what's not
`
`disputed, sending rate. The term sending rate. The specification states that
`
`the server buffer 14 sends data by delivering it to the transport
`
`25 mechanism. In column 8, Patent Owner construes sending rate to be the rate
`
`8
`
`Petitioner's Exhibit 1117
`IPR2022-01413 - Page 009
`
`

`

`Appeal 2023-002525 (Reexamination Control 90/014,833)
`Appeal 2023-003028 (Reexamination Control 90/014,836)
`Appeal 2023-003319 (Reexamination Control 90/014,834)
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`at which media data elements are handed from the server buffer to the
`
`server's underlying transport mechanism.
`
`The Patent Owner does not understand the examiner to disagree with
`
`this. There's a similar statement at page 6 of the answer where he says
`
`sending elements means delivering them from the server buffer to the
`
`server's transport mechanism. Don't believe there's any dispute on
`
`that. Then we get to unsend streaming media data elements. And there's no
`
`clear dispute on this term either, since the server buffer sends data by
`
`delivering it to the transport mechanism. Unsent simply means data in the
`
`server buffer that hasn't been delivered to the transport mechanism.
`
`Now, what is disputed? What is actually disputed? The Patent
`
`12 Owner, and I'll address this at length, but the Patent Owner position is that
`
`13
`
`14
`
`15
`
`16
`1 7
`
`18
`
`19
`
`20
`
`21
`
`claim 2 requires that all unsent elements that are sent from the server buffer
`
`are sent at a sending rate that is more rapid than the playback rate. That is,
`
`Patent Owner's position is that taking into account the undisputed meaning
`
`of the term sending rate, claim 2 imposes the following further limitation on
`claim 1, which is that whenever elements in the server buffer are delivered
`
`by an internal process to the transport, this handoff occurs more rapidly than
`
`the playback rate.
`
`The examiner's interpretation is that claim 2 is met by merely sending
`
`any unsent elements at any time from the server buff er at a sending rate
`
`22 more rapid than the playback rate. The examiner would interpret claim 2 as
`if it had been written the method of claim 1 further comprising sending to
`
`23
`
`24
`
`25
`
`the user system any one or more unsent streaming media data elements in
`
`the server buffer at a sending rate more rapid than the playback rate. The
`
`9
`
`Petitioner's Exhibit 1117
`IPR2022-01413 - Page 0010
`
`

`

`Appeal 2023-002525 (Reexamination Control 90/014,833)
`Appeal 2023-003028 (Reexamination Control 90/014,836)
`Appeal 2023-003319 (Reexamination Control 90/014,834)
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`examiner arrives at this because he contends the Patent Owner's
`
`interpretation of claim 2 would contradict its parent claim, claim 1. The
`examiner argues that the parent claim, claim 1 already provides a class of
`
`elements which the server deals with by sending those elements at about the
`
`playback rate and that if claim 2 required that all elements were sent at a
`
`sending rate more rapid than that, claim 2 would contradict claim 1. On that
`
`basis he rejects Patent Owner's construction.
`
`Patent Owner responds that no such contradiction exists because the
`
`provisions of claim 1 that the examiner relies on to make this argument use
`
`different wording to address transmission rates which in the respective
`
`context of the two claims mean two different things. It is not that the same
`
`12 words in the two claims mean different things, it is that different words in
`
`13
`
`14
`
`15
`
`16
`
`1 7
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`the two claims mean different things. So ideally claim 1 limitation speaks to
`
`sending further elements and claim 2 speaks to the sending rate of the
`
`elements that happen to be in the server buffer from the server buffer.
`
`Words in the server buffer are in claim 2, not in that clause from claim
`
`1. The term sending in what has been referred to as limitation two of claim
`
`1, which is the thereafter clause that I mentioned earlier, is broader and in
`
`the context in which this word is used in claim 1. Sending it about the
`
`playback rate which is tied to filling the server buffer at about the playback
`
`rate refers to a throughput of elements during the steady state and
`
`significantly, this includes elements which during the steady state are not yet
`
`in the server buffer. The procession of elements in the steady state is sent at
`
`the playback rate which of course matches the speed at which they are
`
`arriving at the server buffer to be sent in the first place. The clause does not
`
`10
`
`Petitioner's Exhibit 1117
`IPR2022-01413 - Page 0011
`
`

`

`Appeal 2023-002525 (Reexamination Control 90/014,833)
`Appeal 2023-003028 (Reexamination Control 90/014,836)
`Appeal 2023-003319 (Reexamination Control 90/014,834)
`
`1 use the word -- the clause in question in claim 1 does not use the word,
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`1 7
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`"sending rate." Clause before it dealing with the transfer of the initial buffer
`
`load does use the word sending rate just like claim 2 does. But there --
`
`ruDGE CHEN: Mr. Abramson, this is Judge Chen. Just a brief
`
`clarification. So, unsent, is there any antecedent basis for the term unsent in
`
`claim 2 and claim 1? In other words, claim 1 does not recite the term
`
`unsent, does it?
`
`MR. ABRAMSON: No.
`
`ruDGE CHEN: Excuse me, is that no?
`
`MR. ABRAMSON: That's a no.
`
`ruDGE CHEN: Okay, so what -- so the unsent data in claim 2, your
`argument is that that refers to the last clause in claim 1; is that correct?
`
`MR. ABRAMSON: No, my argument is it does not refer to that. It does
`
`not refer to that. I'll get into that --
`
`mDGE CHEN: Okay.
`
`MR. ABRAMSON: -- why it doesn't refer to that. Does not refer to
`
`that. It just simply refers to sending is the act of these elements in the server
`
`buffer to the transport unsent or elements that haven't been handed, or
`
`elements in the server buffer that haven't been handed off. That's what I'm
`
`saymg.
`
`mDGE CHEN: So, to clarify, you're saying that there's no --so claim
`
`2 could be interpreted to modify both the last -- the last limitation in claim
`
`1. The last limitation reciting the words if any interruptions and the initial
`
`filling of the buff er; is that right?
`
`MR. ABRAMSON: Yes, sir.
`
`11
`
`Petitioner's Exhibit 1117
`IPR2022-01413 - Page 0012
`
`

`

`Appeal 2023-002525 (Reexamination Control 90/014,833)
`Appeal 2023-003028 (Reexamination Control 90/014,836)
`Appeal 2023-003319 (Reexamination Control 90/014,834)
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`1 7
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`JUDGE CHEN: So it's both?
`
`MR. ABRAMSON: Yes, all three as a matter of fact. Initial filling, the
`
`further ones that are sent out to playback. And although a claim 1 doesn't
`
`say what happens if things are detected, if lost or missing packets are
`
`detected, but unsent means anything in the server buffer that hasn't been
`
`handed to transport. It would cover all of those things.
`
`JUDGE CHEN: Okay, thank you for that clarification. You may
`
`continue.
`
`MR. ABRAMSON: Okay, so the clause in claim 1, when it talks about
`
`sending further elements at about the playback rate, doesn't use the word
`
`sending rate. Clause before it does use the word sending rate just like claim
`
`2 does. So, the -- it's different terminology. Sending rate is particular to
`
`claim 2, and the first clause of claim 1 does not appear in the clause that the
`
`examiner is focusing on. It means a different thing.
`
`So, in both cases where the words sending rate more rapid than the
`
`playback rate are used, which is for the initial amount in claim 1 and in
`
`claim 2, it is tied to the sending rate of elements that are in the server
`
`buffer. Claim 1, the first thing happens is we load the server buffer and
`
`claim 2 actually recites in the server buffer. The rate of handing those
`
`elements to the server's transport mechanism. Thus, the throughput of the
`
`stream, looking at the moving set of elements, including those that are not
`
`yet in the server buffer, may be at about the playback rate.
`
`Indeed, it'll be at about the playback rate because the very same
`
`clause of claim 1 recites that these elements only arrive at the server buffer
`
`at the playback rate. So I could analogize this to a class of school kids out
`
`12
`
`Petitioner's Exhibit 1117
`IPR2022-01413 - Page 0013
`
`

`

`Appeal 2023-002525 (Reexamination Control 90/014,833)
`Appeal 2023-003028 (Reexamination Control 90/014,836)
`Appeal 2023-003319 (Reexamination Control 90/014,834)
`
`1
`
`2
`
`3
`
`on an organized walk across city blocks. They move across the blocks at a
`
`steady pace and pacing, but momentarily pause and then go more quickly to
`
`get across the street. Their transit, or overall transit, is at a steady pace, but
`
`4 while in the street itself, they move faster than the steady pace to get out of
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`the street.
`
`To take the analogy further, say one kid trips on the curb at the far
`
`side, causing the queue to back up behind him into the street. When he gets
`
`up and out of the way the other kids in the street all follow quickly to clear
`
`out the crosswalk. That's a rough analogy to what process we're referring
`
`to. Turning back to our streaming media, the elements that land in the server
`
`buff er during the steady state part of the process may at the same time be
`
`dispatched therefrom at the full line rate of the transport mechanism. In the
`
`claim 1 context, this is not contradictory because where the line speed is
`
`faster than the rate of arrival of the elements, there will simply be gaps of
`
`time between the arrival of elements at the feed of the server buffer.
`
`Claim 1 does not address whether the body of each element is sent out
`
`of the buffer at or faster than the playback rate. Claim 2 focuses on this and
`
`does address it. It says that in the case of claim 2, each element that lands in
`
`the server buffer is delivered to the transport more rapidly than the playback
`
`rate. In other words, its elements are, for example, for instance, if you had
`
`1,500 byte elements, which would be 12,000 bits and the media is encoded
`
`at 24,000 bits per second, this is an example out of the patents, there'd be
`
`two elements per second at normal playback. The stream arrives at two
`
`elements which 3,000 bits per second into the server buffer.
`
`13
`
`Petitioner's Exhibit 1117
`IPR2022-01413 - Page 0014
`
`

`

`Appeal 2023-002525 (Reexamination Control 90/014,833)
`Appeal 2023-003028 (Reexamination Control 90/014,836)
`Appeal 2023-003319 (Reexamination Control 90/014,834)
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`Under claim 1, the elements could be handed to the transport, could be
`
`handed to the transport at the same 3,000 bits per second, just like the kids
`
`rushing across the street. But they can also be handed to the transport in any
`
`speed higher than that. In other words, they can arrive at 3,000 bits per
`
`second and you can send them out of the buffer at 3,000 bits per
`
`second. But the rate limiting step here is the arrival at the buffer. You can
`
`send it at any faster speed than that. Claim 2 says, in fact, to send it at faster
`
`speeds than that. Claim 1 does not specify that.
`
`Claim 2 further requires, in our example, that the elements, once they
`
`are in the server buffer, be handed to the transport more rapidly than the
`
`playback rate. So, there's no contradiction there. The Patent Owner argues
`
`that the examiner's overly broad interpretation of claim 1 --
`
`JUDGE CHEN: Mr. Abramson, this is Judge Chen. You've passed
`
`about 20 minutes. Just also a question on one of the examiner's
`
`rejections. The examiner stated that -- stated that cited a portion of the Chen
`
`reference stating that there could be packet drops in interruptions and when
`
`these interruptions are detected, I'm paraphrasing, of course, that these
`
`packets are sent as quickly as possible and cites to a portion in the Chen file
`
`history and refers to the embodiment of the -- I'm going to make sure I get
`
`this term correct. But the watermark analogy. Do you have any
`
`argumentation as why that rejection is improper?
`
`MR. ABRAMSON: Yeah, because it depends upon the -- the claim
`
`construction that it depends upon is that it's sending some elements faster
`
`than the playback rate. And the problem with that, as I was just about to get
`
`into, is that construction, some elements doesn't distinguish claim 1 because
`
`14
`
`Petitioner's Exhibit 1117
`IPR2022-01413 - Page 0015
`
`

`

`Appeal 2023-002525 (Reexamination Control 90/014,833)
`Appeal 2023-003028 (Reexamination Control 90/014,836)
`Appeal 2023-003319 (Reexamination Control 90/014,834)
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`claim 1 already sends some elements faster than the playback rate. There's
`
`just no -- there's no narrower -- that construction is no narrower than claim
`
`1. You've picked a different example to infringe it, but that construction
`
`doesn't comply with section 112 because it does not further narrow claim 1.
`
`Examiner tries to get around this by saying, well, it has to be limited
`
`to other elements that are already recited in claim 1. But he hasn't cited any
`
`basis for that. He tried to make an argument based on the prosecution
`
`history, which talks about original claim 2. The problem with that is that the
`
`issued claim 2 was original claim 3, which depended from claim 1, not from
`
`claim 2. So, it's very clear from that sequence of events that claim 2 is not
`
`directed at the unsent elements in claim 1. Examiner acknowledged that at
`
`the beginning. It's just not -- that's not -- he later --
`
`ruDGE CHEN: Mr. Abramson, this is how I'm seeing the examiner's
`
`position. In claim 1, once there are interruptions detected, there is no
`
`recitation of how quickly those are sent to the client; is that correct?
`
`MR. ABRAMSON: There's no recitation of anything -- of it doing
`
`anything with those. It says detecting and then that's it. There's no
`
`recitation in claim 1 of it doing anything with those.
`
`mDGE CHEN: Okay, so you're just merely detecting it and then
`nothing happens, that's claim 1?
`
`MR. ABRAMSON: As far as claim 1 goes.
`
`mDGE CHEN: Okay, but one of the examiner's interpretations is that,
`
`23 well, once we detect it, we're going to send them as quickly as possible. I
`
`24 mean, why is that improper?
`
`25
`
`MR. ABRAMSON: Because that's only sending some elements faster
`
`15
`
`Petitioner's Exhibit 1117
`IPR2022-01413 - Page 0016
`
`

`

`Appeal 2023-002525 (Reexamination Control 90/014,833)
`Appeal 2023-003028 (Reexamination Control 90/014,836)
`Appeal 2023-003319 (Reexamination Control 90/014,834)
`
`1
`
`than the playback rate. And if you interpret claim 2 to say that the further
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`limitation it imposes is sending some elements faster than the playback rate,
`
`that does not distinguish claim 1.
`
`JUDGE CHEN: Okay. Now is there a recitation that in claim 2 that you
`
`have to send all the elements?
`
`MR. ABRAMSON: Yeah, that's our -- that's our interpretation is that
`
`you have to send all the elements, otherwise you have to send all the
`
`elements. And the examiner is trying to come up with an interpretation
`
`9 where you don't have to send all the elements, but his formulation does not
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`distinguish claim 1.
`
`ruDGE CHEN: Now, is that-- now is that interpretation of all the
`
`elements being sent, is that based on the Federal Circuit remand decision for
`
`a similar case?
`
`MR. ABRAMSON: No. No, the remand decision was on the '141.
`
`JUDGE CHEN: Okay, just to be clear.
`
`MR. ABRAMSON: Had nothing to do with it. Then that was the pull
`
`limitation. Totally different animal.
`
`JUDGE CHEN: Okay, where, sorry. Where in claim 2 is it say sending
`
`all?
`
`MR. ABRAMSON: That is implicit in claim 2.
`
`JUDGE CHEN: But it is unrecited? But is it unrecited?
`
`MR. ABRAMSON: It is unsent in the unsent. It says, "the best of claim
`
`1 further comprising sending unsent elements in the server buffer faster to
`
`playback rate." If you construe that to mean what the examiner says it
`
`25 means, which is to send any elements from the -- from the server buffer
`
`16
`
`Petitioner's Exhibit 1117
`IPR2022-01413 - Page 0017
`
`

`

`Appeal 2023-002525 (Reexamination Control 90/014,833)
`Appeal 2023-003028 (Reexamination Control 90/014,836)
`Appeal 2023-003319 (Reexamination Control 90/014,834)
`
`1 during the course of transmission faster than the playback rate that does not
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`distinguish claim 1. You need a construction, you know, in order to reject
`
`this claim over a piece of prior art you need a construction of the claim to
`
`begin with, and he doesn't have one. The only construction he has that
`
`ensnares Chen is a construction that also is coextensive with claim 1.
`
`ruDGE CHEN: All right, so the way I'm seeing one of the examiner's
`
`rejections is that the very last limitation of claim 1 that recites, if any
`
`interruptions, you previously stated that nothing is done. There's no
`
`recitation as to what happens once these interruptions a

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