throbber
Case 1:16-cv-00455-RGA Document 271-1 Filed 09/12/17 Page 1 of 7 PageID #: 19962
`Case 1:16-cv-00455-RGA Document 271-1 Filed 09/12/17 Page 1 of 7 PagelD #: 19962
`
`
`
`
`
`
`
`
`
`EXHIBIT 1
`EXHIBIT 1
`
`

`

`Case 1:16-cv-00455-RGA Document 271-1 Filed 09/12/17 Page 2 of 7 PageID #: 19963
`
`1
`
`UNITED STATES DISTRICT COURT
`FOR THE DISTRICT OF DELAWARE
`
`CA NO. 16-453-RGA,
`16-454-RGA, 16-455-RGA
`
`July 10, 2017
`
`9:04 o'clock a.m.
`
`: : : : : : : : : :
`
`ACCELERATION BAY LLC,
`
`Plaintiff,
`
`v.
`
`ACTIVISION BAY INC, et al.,
`
`Defendants,
`.............................
`
`TRANSCRIPT OF MARKMAN HEARING
`BEFORE THE HONORABLE RICHARD G. ANDREWS
`UNITED STATES DISTRICT JUDGE
`
`APPEARANCES:
`
`For Plaintiff:
`
`POTTER, ANDERSON & CORROON
`BY: PHILIP A. ROVNER, ESQ
`BY: ALAN R. SILVERSTEIN, ESQ
`
`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
`
`

`

`Case 1:16-cv-00455-RGA Document 271-1 Filed 09/12/17 Page 3 of 7 PageID #: 19964
`
`77
`
`doesn't carry any weight?
`MR. ANDRE: I've not seen a case either way on that. I
`mean, it would lead to an amazing practice. The petitioners
`intentionally would not rely on the proper structure.
`So the PTAB would say, we can't construe them, and then
`they would argue in the District Court, ah, they're indefinite,
`because the PTAB couldn't construe them.
`You can't let them have control of the process and then
`do it poorly, and then punish the patent owner for doing that.
`THE COURT: The IPR procedure is only designed to
`address 102 and 103, right, and not 112?
`MR. ANDRE: That's correct.
`THE COURT: Okay.
`MR. ANDRE: So with that in mind, I think we're all on
`the same page.
`I think you've taken the breadth of my knowledge out at
`this point. I'm going to let Mr. Hannah start going through the
`terms and they can bounce through the terms very quickly that
`way.
`
`THE COURT: All right.
`MR. HANNAH: Thank you, your Honor.
`We'll start with the means for connecting term.
`This is in the '344 and '966 patent. The parties
`agreed essentially with regards to the function here.
`And I think it's clear from the case law, what is
`
`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
`
`10:56:40
`
`10:56:57
`
`10:57:05
`
`10:57:15
`
`10:57:32
`
`

`

`Case 1:16-cv-00455-RGA Document 271-1 Filed 09/12/17 Page 4 of 7 PageID #: 19965
`
`78
`
`required in the spec is that someone of skill in the art has to
`be able to recognize and identify the structure, so they can
`program a software program in order to perform the necessary
`steps of the algorithm.
`And then I think the easiest way is to just look at the
`means for connecting is to see what the patent talks about. It
`talks about the connect routine.
`I think that is the clearest example and it's provided
`out all throughout the '966 and the '344 patent.
`And it specifically says that Figure 8 is a flow
`diagram illustrating the process of the connect routine in one
`embodiment. It's talking exactly about the means for connecting
`and how that works.
`And it goes through what this routine is.
`If you look through this portion that we provided in
`the specification, it says this routine is perhaps a channel
`type or a channel instance. It identifies broadcast channel.
`Routine also has some additional information.
`When the connection is established, the callback
`routine is invoked to notify the application program.
`And when this process invokes a routine, it's in a
`connection seek state. I mean, it goes through the algorithm
`step-by-step in terms of what is required by the means for
`connecting. And it specifically calls it a connect routine in
`the specification.
`
`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
`
`10:57:49
`
`10:58:10
`
`10:58:21
`
`10:58:36
`
`10:58:51
`
`

`

`Case 1:16-cv-00455-RGA Document 271-1 Filed 09/12/17 Page 5 of 7 PageID #: 19966
`
`79
`
`THE COURT: And, so, the structure -- so you're
`submission for structure has a lot of other stuff besides that
`portion of the specification?
`MR. HANNAH: Yes. And, your Honor, the reason we did
`this is because other judges have liked this. We proposed some
`means-plus-functions in unrelated cases.
`And, frankly, we had a judge come back to ask us, how
`am I supposed to just give these citations to the jury.
`Give me something that I can actually read to the jury
`and then put the citations in that.
`So that is why we adopted this format. We think it's a
`little cleaner and easier for a jury to understand, but the
`algorithm is what's in the citations that are provided.
`THE COURT: Well, so it's probably good for me, even if
`I decide to do what you're suggesting there, which sounds
`reasonable. What is good for me is, for you to be, I think,
`very specific about what the algorithm is, right?
`You've got a lot of verbiage here.
`And, so, for the connecting, are you saying that the
`portions that you just showed me, which I think that's in column
`-- whatever it is -- Column 18, Lines 3 to 18 of the '966
`patent, that is the algorithm?
`MR. HANNAH: Yes, your Honor.
`So, if you look at -- so I'm just going back to the
`construction on Slide 22 -- and you'll see for the '966 that's
`
`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
`
`10:59:21
`
`10:59:40
`
`10:59:57
`
`11:00:15
`
`11:00:36
`
`

`

`Case 1:16-cv-00455-RGA Document 271-1 Filed 09/12/17 Page 6 of 7 PageID #: 19967
`
`80
`
`exactly what we've identified.
`So we go 18:3 through 19:22, because the connect
`routine and the connect algorithm actually spans that entire
`column.
`
`And then we identified Figures 3 and 3B based on the
`case law that says that you can illustrate that algorithm and
`diagrams.
`
`And then we have another citation to Column 5, Column
`32 through 50 -- I means Lines 32 through 52, which also
`describes the connect routine.
`So we tried to find where it described the connect
`routine. That's where the algorithm is discussed.
`The rest of it is just to be a summary, to make it more
`about jury friendly, that we found was helpful for the case.
`THE COURT: Can you just show me 3A and 3B?
`MR. HANNAH: Sure.
`So, if you look in the specification, and then to 3A
`and 3B, it is describing how the nodes are actually being
`connected.
`THE COURT: So is that Figure 3A or Figures 3A and 3B?
`MR. HANNAH: Yeah, 3A and 3B right here.
`And then the other citation that we have --
`THE COURT: Okay.
`So you would agree that 3A and 3B by themselves don't
`possibly give an algorithm.
`
`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
`
`11:00:49
`
`11:01:09
`
`11:01:26
`
`11:02:10
`
`11:02:28
`
`

`

`Case 1:16-cv-00455-RGA Document 271-1 Filed 09/12/17 Page 7 of 7 PageID #: 19968
`
`81
`
`MR. HANNAH: No, the specification is describing 3A and
`3B, so we also identified those.
`THE COURT: Okay.
`MR. HANNAH: And then I would say if you want to look
`just to the figures, probably the best description is -- if I
`remember correctly from memory -- is 9 -- or, no, it's Figure 8.
`I believe this is describing the connect routine.
`As I was describing early, it talks about how it
`receives the channel type, the channel instance, and it's going
`to go through and it's going to apply the broadcast channel
`based on that. It's going to -- the columns -- the description
`of this figure shows the algorithm. This description of this
`figure and how it goes through.
`So I think it's just in combination. So we've we put
`everything in there that is describing this -- is describing the
`algorithm.
`In terms of the words to use, I would point to, as I
`did before, Column 18, and it goes up through 19, Line 2 I
`believe.
`
`THE COURT: Okay. All right.
`I want to hear from other side.
`MR. HANNAH: Sure.
`MR. MURRAY: Your Honor, Michael Murray.
`So before I dig into this, I just want to respond to a
`couple of things that plaintiff's counsel talked about.
`
`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
`
`11:02:41
`
`11:03:06
`
`11:03:26
`
`11:03:40
`
`11:04:00
`
`

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