throbber
Trials@uspto.gov
`571-272-7822
`
`Paper 33
`Entered: January 19, 2022
`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`_________________
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`_________________
`
`XILINX, INC. and
`TAIWAN SEMICONDUCTOR MANUFACTURING CO. LTD.,
`Petitioner
`
`v.
`
`ARBOR GLOBAL STRATEGIES LLC,
`Patent Owner.
`_________________
`
`IPR2020-01567 (Patent 7,126,214 B2)
`IPR2020-01568 (Patent 7,282,951 B2)
`IPR2020-01570 (Patent RE 42,035)
`IPR2020-01571 (Patent 6,781,226 B2)
`_________________
`
`Record of Oral Hearing
`Held Virtually: December 3, 2021
`_________________
`
`Before KARL D. EASTHOM, BARBARA A. BENOIT and
`SHARON FENICK, Administrative Patent Judges.
`
`
`
`

`

`IPR2020-01567 (Patent 7,126,214 B2)
`IPR2020-01568 (Patent 7,282,951 B2)
`IPR2020-01570 (Patent RE 42,035)
`IPR2020-01571 (Patent 6,781,226 B2)
`
`APPEARANCES:
`
`ON BEHALF OF THE PETITIONER:
`
`
`KENNETH W. DARBY, JR., ESQ.
`DAVID M. HOFFMAN, ESQ.
`Fish & Richardson, P.C.
`111 Congress Avenue, Suite 810
`Austin, Texas 78701
`(512) 226-8126 (K. Darby)
`(512) 226-8154 (D. Hoffman)
`k.darby@fr.com
`hoffman@fr.com
`
`JEFFREY SHNEIDMAN, Ph.D.
`Fish & Richardson, P.C.
`One Marina Park Drive
`Boston, Massachusetts 02210-1878
`(617) 542-7045
`shneidman@fr.com
`ptabinbound@fr.com
`
`and
`
`JAMES GLASS, ESQ.
`Quinn Emanuel Urquhat & Sullivan, LLP
`51 Madison Avenue, 22nd Floor
`New York, New York 10010
`(212) 849-7142
`jimglass@quinnemanuel.com
`
`ZIYONG LI, ESQ.
`Quinn Emanuel Urquhat & Sullivan, LLP
`50 California Street, 22nd Floor
`San Francisco, California 94111
`(415) 875-6373
`seanli@quinnemanuel.com
`
`
`
`
`
`
`
`
`2
`
`

`

`IPR2020-01567 (Patent: 7,126,214 B2)
`IPR2020-01568 (Patent: 7,282,951 B2)
`IPR2020-01570 (Patent: RE 42,035)
`IPR2020-01571 (Patent: 6,781,226 B2)
`
`ON BEHALF OF THE PATENT OWNER:
`
`
`
`
`JONATHAN S. CAPLAN, ESQ.
`JEFFREY H. PRICE, ESQ.
`Kramer Levin Naftalis & Frankel, LLP
`1177 Avenue of the Americas
`New York, New York 10036
`(212) 715-9488 (J. Caplan)
`(212) 715-7502 (J. Price)
`jcaplan@kramerlevin.com
`jprice@kramerlevin.com
`
`and
`
`JAMES HANNAH, ESQ.
`JENNA FULLER
`Kramer Levin Naftalis & Frankel, LLP
`990 Marsh Road
`Menlo Park, CA 94025
`(650) 752-1712 (J. Hannah)
`(650)752-1728 (J. Fuller)
`jhannah@kramerlevin.com
`jfuller@kramerlevin.com
`
`
`
`The above-entitled matter came on for hearing on Friday, December
`
`3, 2021, commencing at 9:00 a.m. EST, via Video Teleconference.
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`3
`
`
`

`

`IPR2020-01567 (Patent: 7,126,214 B2)
`IPR2020-01568 (Patent: 7,282,951 B2)
`IPR2020-01570 (Patent: RE 42,035)
`IPR2020-01571 (Patent: 6,781,226 B2)
`
`
`
`PROCEEDINGS
`
`
`
`
`
`9:00 a.m.
`
`JUDGE EASTHOM: Good morning. This is Judge Easthom and
`
`with me is Judges Benoit and Fenick. This is case Xilinx Inc. and Taiwan
`
`Semiconductor Manufacturing Company, Ltd., versus Arbor Global
`
`Strategies, LLC.
`
`The case numbers are IPR 2020-01567, -01568, -01570, and -01571.
`
`The patents in respective order are patent 7,126,214 B2, 7,282,951 B2,
`
`Reissue 42,035 E, and then 6,781,226 B2. Who do we have on the record
`
`for Petitioner?
`
`MR. SHNEIDMAN: Good morning, Your Honors. This is Jeffrey
`
`Shneidman of Fish & Richardson and I am joined here today on behalf of
`
`Petitioner Xilinx by my co-counsel David Hoffman and Kenneth Darby.
`
`JUDGE EASTHOM: Welcome, gentlemen. So, Mr. Shneidman,
`
`will you be presenting first or for most of it?
`
`MR. SHNEIDMAN: Yes, sir, that is correct.
`
`JUDGE EASTHOM: Great, okay, and then who do we have for
`
`Patent Owner?
`
`MR. HANNAH: Good morning, Your Honor. This is James
`
`Hannah on behalf of Arbor, and with me is Jeffrey Price and Jenna Fuller,
`
`and Mr. Price will be taking the lead on the argument today.
`
`JUDGE EASTHOM: Okay.
`
`MR. PRICE: Good morning, Your Honors.
`
`JUDGE EASTHOM: Good morning, Mr. Price, and Mr. Hannah,
`
`and Ms. Fuller. Okay, just a few ground rules really quickly. I think you’re
`
`4
`
`
`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
`
`

`

`IPR2020-01567 (Patent: 7,126,214 B2)
`IPR2020-01568 (Patent: 7,282,951 B2)
`IPR2020-01570 (Patent: RE 42,035)
`IPR2020-01571 (Patent: 6,781,226 B2)
`
`all familiar with the procedure here. I just want to make sure that everybody
`
`
`
`knows that first of all, we’re very grateful for your flexibility in conducting
`
`this video hearing telephonically. We know it’s a departure from our past
`
`practices, but we’re sort of used to it now.
`
`Still, our primary concern is that you all have the right to be heard,
`
`so anytime during this proceeding that anything goes awry, if you can’t hear
`
`or you can’t see, please let us know immediately if you can. There are some
`
`numbers you can call if you totally get cut off. For example, one of them is
`
`571-272-6666 or you can call the Board at 571-272-9797.
`
`And please, when you’’re not speaking, please mute yourself, and
`
`when you first start speaking, introduce yourself or at least the first few
`
`times until the court reporter and everybody gets used to you. I think your
`
`name will show up, so maybe we don’’t need to do that except for the first
`
`time. If the court reporter wants to let us know, that would be helpful if they
`
`can’’t tell who is speaking.
`
`But other than that, we can see the entire records, including
`
`demonstratives, so, and when you refer to them, please give us the name and
`
`clearly the slide number and the page number, and then just pause a couple
`
`seconds so that we can turn to it and we know where you’’re going.
`
`And then just a matter of bookkeeping, Petitioner is going to go first.
`
`They have the burden of proof. Patent Owner will go next to rebut that case,
`
`and then any rebuttal time that Petitioner reserves, then Petitioner can then
`
`address Patent Owner’s arguments, and then Patent Owner can address
`
`Petitioner in sur-reply arguments.
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`5
`
`
`

`

`IPR2020-01567 (Patent: 7,126,214 B2)
`IPR2020-01568 (Patent: 7,282,951 B2)
`IPR2020-01570 (Patent: RE 42,035)
`IPR2020-01571 (Patent: 6,781,226 B2)
`
`
`
`
`Then also, the panel wanted to make sure that everybody is aware,
`
`and I’’m sure you are, that with three of the patents, the Board issued final
`
`written decisions last week, and those involved patent 7,282,951 and that
`
`case was IPR2020-01021, and then the reissue patent, RE42,035 E, we
`
`issued a final written decision in IPR2020-01020, and then in the 6,781,226
`
`B2 patent, we issued a final written decision in IPR2020-01022.
`
`So, during the hearings, we could probably refer to those as the 1021
`
`case, the 1020 case, and the 1022 case, and we did issue claim construction
`
`in those cases. We would be interested for the parties to know what they
`
`feel about those going forward here. I think there’’s a big overlap with what
`
`’you’re going to be arguing here. The art is different and we understand
`
`that.
`
`So, with that, does anybody have any questions? Why don’’t we ask
`
`you, Petitioner?
`
`MR. SHNEIDMAN: No questions, Your Honor.
`
`JUDGE EASTHOM: Okay, how about, okay, Mr. Price, do you
`
`have any questions?
`
`MR. PRICE: No, Your Honor.
`
`JUDGE EASTHOM: Okay, and I’’m sorry, Mr. Price, you’’re going
`
`to be speaking first, is that right? I just want to --
`
`MR. PRICE: No, Your Honor, I won’’t be speaking first.
`
`JUDGE EASTHOM: Mr. Hannah would. Okay, I’’m sorry. I got
`
`my notes --
`
`MR. PRICE: I’m sorry, it’’s Mr. Shneidman.
`
`JUDGE EASTHOM: No, I mean --
`
`6
`
`
`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
`
`

`

`IPR2020-01567 (Patent: 7,126,214 B2)
`IPR2020-01568 (Patent: 7,282,951 B2)
`IPR2020-01570 (Patent: RE 42,035)
`IPR2020-01571 (Patent: 6,781,226 B2)
`
`
`
`
`MR. PRICE: Mr. Shneidman will be speaking.
`
`JUDGE EASTHOM: Mr. Shneidman will be speaking for
`
`Petitioner, but for Patent Owner, it will be Mr. Price, right? Okay, sorry
`
`about that. I got it. Okay, Mr. Shneidman, you may begin.
`
`MR. SHNEIDMAN: Great, thank you, Your Honors. Again, this is
`
`Jeffrey Shneidman of Fish & Richardson on behalf of Petitioner Xilinx for
`
`these matters. I would like to reserve 40 minutes of my time today for
`
`rebuttal.
`
`And I’’m glad Your Honors raised the final written decisions that
`
`concern three of the patents in today’s cases that were issued in the Samsung
`
`v. Arbor matters last week. I do want to be sure to address today how the
`
`Board’s claim constructions in those matters reinforces the strength of
`
`Xilinx’s position in these matters before you today, and so I want to make
`
`sure that our position on that is considered as part of the record.
`
`Now, we have submitted a slide deck, Exhibit 1109, in all of the
`
`matters, and if you have that open, Exhibit 1109, I am not going to go
`
`through every demonstrative slide, but I do plan today on hitting what I
`
`believe are the core issues and disputes, but, of course, if the Board has
`
`questions on certain items, I’m happy to jump to discuss what you want to
`
`discuss today.
`
`So, I’’ll pause to see if there are any initial questions, and if not, I
`
`would ask you to turn to slide seven.
`
`So, by the time that the Huppenthal patents were filed starting in
`
`2001, there was already considerable related relevant prior art in the field,
`
`and even beyond the art at issue, at direct issue in these proceedings as the
`
`7
`
`
`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
`
`

`

`IPR2020-01567 (Patent: 7,126,214 B2)
`IPR2020-01568 (Patent: 7,282,951 B2)
`IPR2020-01570 (Patent: RE 42,035)
`IPR2020-01571 (Patent: 6,781,226 B2)
`
`grounds, references like Koyanagi disclosed 100,000 distributed
`
`
`
`interconnections between layers of a 3D stack for the purpose of
`
`acceleration.
`
`References like Bertin 1998 shown here on the top showed a
`
`programmable array stackable with a memory connected with a plurality of
`
`contact points, and references like Casselman in the lower left here taught an
`
`FPGA stacked with a microprocessor and memory and data shared between
`
`those layers.
`
`Xilinx’’s expert, Dr. Franzon, published a survey paper in 1998
`
`which was titled “A Review of 3D Packaging Technology” that addressed
`
`and summarized many of the issues that the Huppenthal patents claimed as
`
`points of purported novelty.
`
`So, many variations on this theme have been done and were known
`
`to the POSITA, and were summarized at length by both Dr. Franzon and
`
`others, but Dr. Franzon, in his expert reports, and his declarations, and his
`
`1998 survey paper.
`
`So, there can be no question that had the inventors put the relevant
`
`prior art before the Patent Office, that none of these challenge claims would
`
`have issued.
`
`I can turn to slide nine. We lay out here on slide nine the disputes at
`
`issue in these trials. Now, it’s notable that most of the examiner’s original
`
`reasons for allowance on these patents has nothing to do with the disputes
`
`before the Board today.
`
`As one example, Arbor has not alleged that there is any missing
`
`element from the 035 patent claims 1 through 22, 31, 34, 35, or 37. Now,
`
`8
`
`
`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
`
`

`

`IPR2020-01567 (Patent: 7,126,214 B2)
`IPR2020-01568 (Patent: 7,282,951 B2)
`IPR2020-01570 (Patent: RE 42,035)
`IPR2020-01571 (Patent: 6,781,226 B2)
`
`yes, Arbor is challenging the sufficiency of the motivation to combine, but
`
`
`
`Arbor is not challenging that any element is missing in the prior art from
`
`these 26 claims.
`
`So, the alleged disputes that Arbor raises are not really inventive
`
`aspects. In most cases, they are claim elements with literally a couple of
`
`words in support in the specification with no explanation. They were
`
`commonly understood and readily found features in the prior art.
`
`Now, I’m going to walk through several of these disputes starting
`
`with the accelerate terms, which we identify as Issue 1A under the
`
`Zavracky-Chiricescu-Akasaka ground, and this is a dispute relevant to the
`
`claims in the 214, 951, and 035 patents as shown in this chart.
`
`So, if we could turn to slide 22? So, slide 22 shows the
`
`representative claim language in the 035 patent, independent claim 23 and
`
`its dependent claim 24. And in general across the disputes today, I’m going
`
`to be focusing on the examples from 035 and the 226 patents because
`
`Arbor’s responses in the 951 and the 214 are largely subsets of the
`
`arguments in these two cases. My arguments, of course, are applicable to all
`
`of the proceedings.
`
`On slide 23, I summarize Xilinx’s reasoning as to this issue. Now,
`
`the first key point is that Arbor assumes and addresses these claims only
`
`using its own erroneous claim construction. Arbor chose not to address the
`
`Board’s institution decision claim construction and Arbor did not address
`
`Petitioner’s plain and ordinary meaning of these accelerate terms.
`
`Second, the Petitioner showed that the Zavracky-Chiricescu-Akasaka
`
`combination provides this claim element under any reasonable construction
`
`9
`
`
`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
`
`

`

`IPR2020-01567 (Patent: 7,126,214 B2)
`IPR2020-01568 (Patent: 7,282,951 B2)
`IPR2020-01570 (Patent: RE 42,035)
`IPR2020-01571 (Patent: 6,781,226 B2)
`
`based on the specification, claims, and file history of these patents. Now,
`
`
`
`I’’m going to go through the Board’s construction as it was discussed in the
`
`recent Samsung 951 opinion in a moment.
`
`Third, even though Arbor’s attacks assume its own incorrect
`
`construction for these accelerate terms, even using Arbor’s construction,
`
`Arbor does not, excuse me, put forward a fair presentation of the evidence in
`
`the record, and I’’m going to talk a little bit about that.
`
`If you could turn with me to slide 25, I briefly want to address claim
`
`construction. Now, I know the Board has spent considerable time on this
`
`issue and I’m going to focus on the Board’s construction issued last week in
`
`a moment, but I want to make a few points about Arbor’s position because it
`
`goes to the credibility of Arbor’’s current expert.
`
`In these matters, Arbor has taken the position that these accelerate
`
`terms are plain meaning terms, but has also stated that the terms require a
`
`wide configuration data port. And just a brief point here is that the claim
`
`language says no such thing. It does not mention a wide configuration data
`
`port. It’s not a requirement of these claims.
`
`And on slide 26, we lay out how Arbor, in parallel proceedings, has
`
`taken a litany of different positions as to the plain and ordinary meaning of
`
`these accelerate terms. So, Arbor has cited the memory and using the
`
`memory as an intermediary buffer that is as a cache for providing the claim
`
`elements.
`
`Arbor has cited the short interconnects to the memory die. Arbor has
`
`cited the stacking techniques generally as providing the acceleration
`
`elements. Arbor has cited close proximity of the interconnects to the
`
`10
`
`
`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
`
`

`

`IPR2020-01567 (Patent: 7,126,214 B2)
`IPR2020-01568 (Patent: 7,282,951 B2)
`IPR2020-01570 (Patent: RE 42,035)
`IPR2020-01571 (Patent: 6,781,226 B2)
`
`memory die as providing the claim elements, and Arbor has stated that any
`
`
`
`speed increase over what the speed would otherwise be without the memory
`
`array is the claimed acceleration or meets the claimed acceleration elements.
`
`So, turning to slide 27, Arbor has an expert supporting each of these
`
`positions in the parallel proceeding and the positions are in the record. This
`
`is Dr. Darveaux, I believe. His are in the record as Exhibit 1074, along with
`
`Arbor’s prior briefing taking those positions, which are Exhibits 1072 and
`
`1073, and the Board can see from the timeline that Arbor took these
`
`positions after Xilinx filed the petitioner in the present cases.
`
`And from the public docket, we can see that the District Court
`
`accepted Arbor’s arguments, and the District Court’s claim construction
`
`order is Exhibit 2005 in the 1570 IPR for the 035 patent, for example.
`
`Now, if we turn to slide 30, I want to address the Board’s
`
`construction and the recent Samsung 951 decision where the, quote,
`
`functional to accelerate limitations were construed as, quote, a number of
`
`vertical contacts distributed throughout the surface of and traversing the
`
`memory die in a vertical direction, vias, to allow multiple short paths for
`
`data transfer between the memory and processor.
`
`And for clarity, we understand that when the Board wrote the word
`
`processor in the Samsung 951 final written decision that the Board was
`
`referencing the programmable array that is programmable as the processing
`
`element that’s recited in some of the 951 claims, and that interpretation is
`
`clear from the record, the claim language itself, and how the parties, you
`
`know, interpreted the acceleration claim elements in that matter.
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`11
`
`
`

`

`IPR2020-01567 (Patent: 7,126,214 B2)
`IPR2020-01568 (Patent: 7,282,951 B2)
`IPR2020-01570 (Patent: RE 42,035)
`IPR2020-01571 (Patent: 6,781,226 B2)
`
`
`
`
`And what I’m saying here is that all the acceleration claims at issue
`
`across the patents, there’s some programmable logic that is doing some
`
`processing, and so I just wanted to flag that issue now for the Board so the
`
`Board can avoid any ambiguity in the claim construction.
`
`And so, for clarity, in the 951 patent, we understand the Board’s
`
`construction to be a number of vertical contacts distributed throughout the
`
`surface of and traversing the memory die in a vertical direction, vias, to
`
`allow short paths for data transfer between the memory and programmable
`
`array.
`
`And in the 035 and 985 patent, we understand the Board’s
`
`construction to be a number of vertical contacts distributed throughout the
`
`surface of and traversing the memory die in a vertical direction, vias, to
`
`allow multiple short paths for data transfer between the memory and field
`
`programmable data array because those are the processing elements that are
`
`referenced, but regardless of the way it’s stated, including if the Board keeps
`
`its original processor language, the Zavracky-Chiricescu-Akasaka
`
`combination provides that limitation.
`
`Zavracky describes interlayer connections that provide for vertical
`
`communication. Such communications, sorry, such connections, you can
`
`see, can be placed anywhere on the die and therefore are not limited to
`
`placement on the outer periphery.
`
`Chiricescu further confirms that interpretation of Zavracky, stating
`
`that Zavracky, quote, allows us to build chips with vertical metal
`
`interconnections, i.e., interlayer vias, placed anywhere on the chip.
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`12
`
`
`

`

`IPR2020-01567 (Patent: 7,126,214 B2)
`IPR2020-01568 (Patent: 7,282,951 B2)
`IPR2020-01570 (Patent: RE 42,035)
`IPR2020-01571 (Patent: 6,781,226 B2)
`
`
`
`
`And Akasaka teaches the exchange of signals between upper and
`
`lower active circuit layers through via poles in 3D integrated circuits, and
`
`that there can be tens of thousands of such connections.
`
`So, on slide 31, I’ve extracted here some of the acceleration
`
`teachings of Zavracky, Chiricescu, and Akasaka, and to read some of the
`
`quotes from these references, Zavracky’s approach accelerates
`
`communication between the dies and the chip by way of, quote, smaller
`
`delays and higher speed circuit performance. The arrangement results in
`
`reduced memory time, increasing the speed of the entire system.
`
`Chiricescu teaches significantly improved FPGA reconfiguration
`
`time, and Akasaka describes high-speed performance that is associated with
`
`shorter interconnection delay in parallel processing.
`
`And these are just some of the quotes from these references, and we,
`
`of course, go into more detail in our briefing, but the point here is that Xilinx
`
`shows that the combination teaches the claim elements under any reasonable
`
`construction, and that includes the Board’s construction of, quote, a number
`
`of vertical contacts distributed throughout the surface of and traversing the
`
`memory die in a vertical direction, vias, to allow multiple short paths for
`
`data transfer between the memory and processor or programmable array,
`
`field programmable data array. The point there is just the processing
`
`element.
`
`JUDGE EASTHOM: Mr. Shneidman, I was wondering what you
`
`think about -- there was some -- it seemed like the parties agreed to a certain
`
`extent in the 1021 and 1022 cases that because you have all of these vias that
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`13
`
`
`

`

`IPR2020-01567 (Patent: 7,126,214 B2)
`IPR2020-01568 (Patent: 7,282,951 B2)
`IPR2020-01570 (Patent: RE 42,035)
`IPR2020-01571 (Patent: 6,781,226 B2)
`
`are short and also in parallel, they’re physically in parallel, that they enable
`
`
`
`parallel processing.
`
`Is that -- and so, although that’s not in the claim construction, it’s
`
`sort of part and parcel of what, I think, Patent Owner is arguing, that you
`
`need some kind of parallel processing or parallel data transfer to happen. Do
`
`you agree with that and do you think that you’ve shown that?
`
`MR. SHNEIDMAN: Yes, so the patent speaks of a parallelism in
`
`loading the configuration cells themselves if you look at where parallelism
`
`appears in the specification. You know, I understand the Patent Owner
`
`believes that it’s required to have parallel access, simultaneous parallel
`
`access and not just direct connections throughout the entire system really.
`
`You know, we have shown that. You know, our view is that we’ve
`
`shown all of the potential reasonable constructions here, but in particular, to
`
`the extent that parallelism and simultaneity of access is required, we detailed
`
`that in our Petitioner reply, for example, going through and explaining how,
`
`if parallelism is required in terms of simultaneity throughout the system,
`
`then that is shown by the prior art.
`
`Now, you know, from memory, I do want to recall that the patent
`
`speaks of being able to do loading of buffer cells, for example, as one
`
`example, while the FPGA is in operation, and so while the FPGA is in
`
`operation implies that there’s sort of some ticking going on, some additional
`
`advancement in clock cycles.
`
`So, you know, it’s certainly clear that there is direct connections
`
`required. I think Figure 3 versus Figure 5 shows that, but in terms of, you
`
`14
`
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`

`

`IPR2020-01567 (Patent: 7,126,214 B2)
`IPR2020-01568 (Patent: 7,282,951 B2)
`IPR2020-01570 (Patent: RE 42,035)
`IPR2020-01571 (Patent: 6,781,226 B2)
`
`know, squaring, I know, you know, having read the transcript in the 1020
`
`
`
`and 1021, the parallelism is sort of assumed, and I suppose what we’re
`
`saying is under any construction, including the parallel construction, the art
`
`that we have put together in the petitions does show that.
`
`JUDGE EASTHOM: And do you agree that -- I think we made
`
`some findings, the Board did, in 1021 and 1022. A lot of it was in footnotes,
`
`some of it was, because it wasn’t totally an issue, but it seems like it’s
`
`rearing its head a little more here maybe, but it seems like -- I think Patent
`
`Owner agrees that bandwidth, increasing bandwidth is another way of saying
`
`parallel connections, but I don’t know how you feel about that or --
`
`MR. SHNEIDMAN: I think that’s a fairly fair characterization. Dr.
`
`Franzon testifies that the combination increases bandwidth, I think area wide
`
`interconnections such as taught by Akasaka, you know, and to jump ahead a
`
`little bit, for example, Trimberger in providing discussions of simultaneity
`
`and bit access. That really is getting to bandwidth. That’s getting to --
`
`JUDGE EASTHOM: I mean, I understand it’s dependent on the
`
`clock, right, according to, I think it was Dr. Chakrabarty in the 1021 and
`
`1029 hearings, but if the clock rate’s the same and you have more parallel
`
`connections, then the bandwidth goes up is the way I understand it.
`
`MR. SHNEIDMAN: I think that’s a fair statement, Your Honor.
`
`There a little bit of informality in the way some of these terms tend to be
`
`used in the art, and frankly, maybe a little sloppiness, but I believe that, you
`
`know, getting to bandwidth is a form of acceleration and increased
`
`bandwidth, that certainly if you can push more data through in one clock
`
`cycle, you can process that data faster.
`
`15
`
`
`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
`
`

`

`IPR2020-01567 (Patent: 7,126,214 B2)
`IPR2020-01568 (Patent: 7,282,951 B2)
`IPR2020-01570 (Patent: RE 42,035)
`IPR2020-01571 (Patent: 6,781,226 B2)
`
`
`JUDGE EASTHOM: Okay, thank you.
`
`
`
`MR. SHNEIDMAN: All right, so unless there are further questions,
`
`I’d like to move to slide 38. Now, Arbor only did its analysis under its
`
`faulty wide configuration data port construction, and so our view is the
`
`response is really, frankly, nonresponsive. With that said, we rebutted
`
`each of Arbor’s attacks on this element anyway, and unless the Board has
`
`questions, I just want to highlight the second issue on this slide which is
`
`described at slide 40 because it’s a bigger concern in these proceedings.
`
`So, on slide 40, Arbor is not accurate in how it describes Xilinx’s
`
`expert’s testimony, and here on slide 40 is an example. At his deposition,
`
`Xilinx’s expert, Dr. Franzon, was asked about preloading memory cells in
`
`the context of the Trimberger reference. In other words, how does data get
`
`to the on-chip memory within the 3D chip in the first place?
`
`And Dr. Franzon, in his testimony, says the data comes from, quote,
`
`an off-chip memory. That is data that’s contained in the DRAM from
`
`outside of the 3D chip. That has nothing to do with the internals of the 3D
`
`chip. It has nothing to do with Chiricescu, and Arbor incorrectly cites this
`
`testimony to say that Dr. Franzon admitted something about Chiricescu and
`
`Chiricescu’s RLB BUS. He did not.
`
`The Board can confirm for itself by reference to the index of Dr.
`
`Franzon’s deposition transcript that Arbor did not ask a single question
`
`about Chiricescu in the transcript except warm-up questions to see if he was
`
`familiar with the reference, and the word RLB or RLB BUS is not
`
`mentioned once in the transcript. So, all of these supposed admissions on
`
`the left of the slide are just made up.
`
`16
`
`
`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
`
`

`

`IPR2020-01567 (Patent: 7,126,214 B2)
`IPR2020-01568 (Patent: 7,282,951 B2)
`IPR2020-01570 (Patent: RE 42,035)
`IPR2020-01571 (Patent: 6,781,226 B2)
`
`
`
`
`On slide 41, we can see also that Arbor’s argument and criticism is
`
`factually incorrect. Specifically, Arbor argues that Chiricescu uses a narrow
`
`data port and does not use Zavracky’s interconnections for communication.
`
`It’s an odd argument because Chiricescu literally states that it uses
`
`Zavracky’s interlayer vias to connect the three separate layers and
`
`Chiricescu describes no other way of connecting the layers.
`
`More importantly, Xilinx is asserting a combination argument. That
`
`is even Zavracky provides, quote, a number of vertical contacts distributed
`
`throughout the surface of and traversing the memory die in a vertical
`
`direction, vias, to allow multiple short paths for data transfer between the
`
`memory and processing element, processor FPGA programmable array, and
`
`that teaching is further amplified by Chiricescu and Akasaka, so Arbor’s
`
`attacks are simply not correct and they are not attacking the relevant
`
`combination.
`
`So, in sum, our view is that the accelerate claims are taught by the
`
`combination, including under the Board’s construction issued last week in
`
`these terms. So, unless the Board has more questions on that, I’m going to
`
`switch gears to the other claims affected by the construction and the
`
`Samsung decisions involving the means plus function terms.
`
`For that, we want to go to slide 74. So, if you turn to slide 74, I want
`
`to discuss the one clock cycle means plus function limitations, and this is
`
`relevant only to the 226 patent.
`
`So, on slide 75, I show the means plus function claims at issue, and
`
`the limitations at dispute here are claim 13’s means for reconfiguring the
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`17
`
`
`

`

`IPR2020-01567 (Patent: 7,126,214 B2)
`IPR2020-01568 (Patent: 7,282,951 B2)
`IPR2020-01570 (Patent: RE 42,035)
`IPR2020-01571 (Patent: 6,781,226 B2)
`
`programmable array within one clock cycle and claim 22’s means for
`
`
`
`updating the plurality of configuration logic box within one clock cycle.
`
`Now, as laid out in the papers, there is no dispute as to the function
`
`here for these claims. There is a dispute as to whether it is the
`
`corresponding structure for the functions of reconfiguring the programmable
`
`array within one clock cycle and updating the plurality of configuration logic
`
`cells within one clock cycle.
`
`So, if we move forward two slides to slide 77, the combination
`
`asserted here is Zavracky-Chiricescu-Akasaka, with the additional reference
`
`of Trimberger. Trimberger describes memory, quote, accessible so that the
`
`entire configuration of the FPGA can be changed in a single cycle.
`
`Now, on slide 78, Trimberger is describing memory as a memory
`
`plane which is comprised of cells that is instantaneously swapped to update
`
`programmable array configuration cells.
`
`On slide 79, first in the lower left, we see the description that the
`
`CLB configuration cells are connected to memory cells, and the
`
`configuration cells are part of the logic and interconnect array on the model
`
`shown on the right-hand side, which is Figure 1 of Trimberger. The memory
`
`cells are located in the plane on the configuration SRAM in the picture and
`
`there are 100,000 bit lines.
`
`Now, I’ll pause to note that this is similar to the connectivity taught
`
`in other references known to the POSITA. For example, Koyanagi also
`
`taught 10 to the 5 or 100,000 interconnections, and Akasaka taught tens of
`
`thousands of connections.
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`18
`
`
`

`

`IPR2020-01567 (Patent: 7,126,214 B2)
`IPR2020-01568 (Patent: 7,282,951 B2)
`IPR2020-01570 (Patent: RE 42,035)
`IPR2020-01571 (Patent: 6,781,226 B2)
`
`
`
`
`So, one of the relevant teachings in Trimberger is the structure of
`
`how to connect the memory cells to the configuration logic cells so that the
`
`FPGA is configured in one clock cycle, and to quote from Dr. Franzon’s
`
`original report, Exhibit 1002 in all of the matters, which is paragraph 254,
`
`Trimberger teaches, quote, how to direct the connectivity permitted by
`
`Akasaka’s distributed contact points and Zavracky and Chiricescu’s teaching
`
`of contact points anywhere.
`
`JUDGE EASTHOM: Mr. Shneidman, are you arguing that the
`
`updated simultaneously, is that for all 100,000 bits on slide 79? You have a
`
`quote?
`
`MR. SHNEIDMAN: Yes, Your Honor, if I understand your
`
`question, you’ll see in the lower right --
`
`JUDGE EASTHOM: Yeah, okay, so that would be a parallel
`
`reconfiguration?
`
`MR. SHNEIDMAN: Correct, what’s happening is, okay, so if you
`
`see in the picture, there’s MC8 that’s highlighted in yellow on slide 79?
`
`JUDGE EASTHOM: Yes.
`
`MR. SHNEIDMAN: And that is one cell of many cells that is on a
`
`plane, one of these planes, and then what happens is in one clock cycle,
`
`there’s 100,000 of these blue, colored in blue bit lines that’s connecting the
`
`MC8 to the logic and interconnect array, and so what happens, as you can
`
`see in the lower right, the quote from Exhibit 1006, is when the device is
`
`flash reconfigured, and by flash, they mean quickly, all bits in the logic and
`
`interconnec

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