throbber
Paper 79
`Entered: April 2, 2014
`
`RECORD OF ORAL HEARING
`
`
`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`
`
`
`
`APPLE INC.
`Petitioner
`
`v.
`
`ACHATES REFERENCE PUBLISHING, INC.
`Patent Owner
`
`
`
`Case IPR2013-00080 (Patent 6,173,403)
`Case IPR2013-00081 (Patent 5,982,889)
`
`
`
`Oral Hearing Held: February 26, 2014
`
`
`
`Before HOWARD B. BLANKENSHIP, JUSTIN T. ARBES, and GREGG
`I. ANDERSON, Administrative Patent Judges.
`
`
`

`
`
`
`
`
`
`
`
`APPEARANCES:
`
`ON BEHALF OF THE PETITIONER:
`
`JEFFREY P. KUSHAN, ESQUIRE
`JOSEPH A. MICALLEF, ESQUIRE
`Sidley Austin, LLP
`1501 K Street, N.W.
`Washington, D.C. 20005
`
`
`
`
`
`
`
`
`ON BEHALF OF THE PATENT OWNER:
`
`
`
`
`
`
`
`
`
`
`
`VINCENT E. McGEARY, ESQUIRE
`Gibbons, P.C.
`One Gateway Center
`Newark, New Jersey 07102-5310
`BRAD D. PEDERSEN, ESQUIRE
`Patterson, Thuente, Pedersen, P.A.
`4800 IDS Center, 80 South 8th Street
`Minneapolis, Minnesota 55402
`
`
`The above-entitled matter came on for hearing on Wednesday,
`
`February 26, 2014, commencing at 2:11 p.m., at the U.S. Patent and
`
`Trademark Office, 600 Dulany Street, Alexandria, Virginia 22314.
`
`

`
`Case IPR2013-00080 (Patent 6,173,403)
`Case IPR2013-00081 (Patent 5,982,889)
`
`
`
`
`
`P R O C E E D I N G S
`
`- - - - -
`
`
`
`JUDGE ARBES: This is the oral hearing in two cases, Cases IPR
`
`2013-80 and 2013-81 involving Patent 6,173,403 and Patent 5,982,889.
`
`
`
`
`
`
`
`Would counsel please state your names for the record?
`
`MR. KUSHAN: Jeff Kushan and Joe Micallef for Petitioner Apple.
`
`MR. PEDERSEN: Brad Pedersen and Vincent McGeary for the
`
`Patent Owner Achates.
`
`
`
`JUDGE ARBES: Per the Board's trial hearing order in these cases,
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`each party will have 90 minutes total time to present for the two cases. You
`
`11
`
`can allocate that time however you would like. The order of presentation
`
`12
`
`will be that counsel for the Petitioner will go first regarding the challenged
`
`13
`
`claims in the 80 case. You may reserve time for rebuttal.
`
`14
`
`
`
`The Patent Owner will then respond with respect to the challenged
`
`15
`
`claims in the 80 case. The Petitioner can then use rebuttal time for that one.
`
`16
`
`We will then take a short break and then proceed in the exact same manner
`
`17
`
`for the 81 case.
`
`18
`
`
`
`A couple of reminders before we begin, to ensure that the transcript is
`
`19
`
`clear, because we have one judge in the Denver office, we would ask the
`
`20
`
`parties to please try to remember to refer to your demonstratives by slide
`
`21
`
`number so the record is complete. And, also, if you can stay near the
`
`22
`
`podium so that the judge in the other office can hear you.
`
`23
`
`
`
`Do the parties have copies of the demonstratives that you will be
`
`24
`
`using today?
`
` 3
`
`
`
`
`

`
`Case IPR2013-00080 (Patent 6,173,403)
`Case IPR2013-00081 (Patent 5,982,889)
`
`MR. KUSHAN: Yes, Your Honor. May I approach?
`
`JUDGE ARBES: Yes, please.
`
`MR. KUSHAN: These are the demonstratives. I also was going to
`
`
`
`
`
`
`
`
`
`ask that we provide you with a copy of the one exhibit that's under seal so
`
`you have it accessible. If that's okay, I can leave it with you. These are our
`
`copies for the panel.
`
`
`
`MR. McGEARY: Your Honor, we don't have an extra copy of the
`
`demonstrative exhibits.
`
`
`
`JUDGE ARBES: That's fine. Counsel for the Petitioner, you can go
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`first. And would you like to reserve time for rebuttal? And, if so, how
`
`11
`
`much?
`
`12
`
`
`
`MR. KUSHAN: We would like to reserve about half of our time for
`
`13
`
`rebuttal. And we will take it somewhat as we go to the second proceeding.
`
`14
`
`
`
`Thank you very much. Today's hearing is going to focus on two
`
`15
`
`patents in a fairly crowded field of technology with a fair amount of prior
`
`16
`
`art. And before we get into the details, it is important to appreciate that the
`
`17
`
`patents that we are dealing with concern a technique, which essentially takes
`
`18
`
`a set of information and uses a conventional encryption technique as an aid
`
`19
`
`to transfer the files securely.
`
`20
`
`
`
`When you look at the patents, they employ very well in very
`
`21
`
`established encryption and other techniques that have been in the prior art
`
`22
`
`for a fair amount of time. And as we go through the issues, you will see that
`
`23
`
`the claims are, in fact, going to be fairly, clearly obvious or anticipated by
`
`24
`
`that prior art.
`
` 4
`
`
`
`
`

`
`Case IPR2013-00080 (Patent 6,173,403)
`Case IPR2013-00081 (Patent 5,982,889)
`
`So we move to Slide 2. These are the grounds that we are going to be
`
`
`
`
`
`addressing. And I am also going to be taking up the grounds based on Pettitt
`
`and Beetcher. And my colleague Mr. Micallef will be taking up the grounds
`
`based on Ginter. If we go to Slide 3.
`
`
`
`The first issue I would like to address is the finding of anticipation by
`
`Pettitt. This is Claim 1. It has been found anticipated. And what we did in
`
`our petition was outline that there were two distinct authentication codes in
`
`the Pettitt scheme. And if you see on the bottom here in our '403 petition at
`
`Pages 26 and 27, we explain how the Pettitt scheme works.
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`
`
`In Pettitt, there is an encrypted reply envelope, which is created.
`
`11
`
`Inside that encrypted reply envelope are a number of items and information.
`
`12
`
`One of them is called the digital authorization certificate. I will call that the
`
`13
`
`DAC for short. In the process, this encrypted reply envelope is sent through
`
`14
`
`a chain down to a reseller. And then when the reseller receives that, it
`
`15
`
`decrypts it and recovers the information inside the envelope.
`
`16
`
`
`
`The encrypted reply envelope is also signed with the digital signature
`
`17
`
`of the LCH, license clearinghouse. Once it's decrypted at the reseller, the
`
`18
`
`contents are then passed on to the user. And those contents, including the
`
`19
`
`DAC, are used to install the software.
`
`20
`
`
`
`This demonstration in Pettitt -- as I said, this is from our petition. We
`
`21
`
`have very clearly identified that there were actually two authentication codes
`
`22
`
`in the Pettitt scheme. One was the LCH digital signature. And if we go to
`
`23
`
`Slide 8, this is one of the statement of facts we included with our petition in
`
`24
`
`81 where we set out our position with the digital authorization certificate as
`
`25
`
`an authentication code supported by evidence of Mr. Schneier.
`
` 5
`
`
`
`
`

`
`Case IPR2013-00080 (Patent 6,173,403)
`Case IPR2013-00081 (Patent 5,982,889)
`
`JUDGE ARBES: What's your position on Pettitt regarding the
`
`
`
`
`
`assertions in the petition in the 80 case? It seems to have to do a lot with the
`
`assertion in the body of the petition that the LCH's digital signature is the
`
`first candidate authentication code. That's what's referred to on Page 27 of
`
`the petition. And while this was in the statement of facts, it is not in the
`
`body of the petition itself. Can you address that?
`
`
`
`MR. KUSHAN: Well, if I could go back to Slide 3. This passage is
`
`actually from our petition proffer. And the way we organized our petition
`
`was to outline a number of material facts that we felt were going to
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`demonstrate the evidence constituting anticipation or obviousness of the
`
`11
`
`patent claims. And then we relied on the statement of facts as well as our
`
`12
`
`explanations of how the scheme worked to demonstrate the evidence that is
`
`13
`
`making out the case for anticipation.
`
`14
`
`
`
`So we feel like we clearly conveyed that there were two
`
`15
`
`authentication codes being distributed in the scheme. And I also would note
`
`16
`
`that I think that was fairly communicated because the Patent Owner in its
`
`17
`
`opposition -- first of all, it is stated in one of its oppositions. We can go to
`
`18
`
`Slide 76. This is in the '889 proceeding. This is them responding to our
`
`19
`
`position in their opposition. And you can see number two is the DAC.
`
`20
`
`
`
`And if you go to Slide 6. When they responded to the '403 patent,
`
`21
`
`what they did was identified a passage that we extensively discussed, both in
`
`22
`
`our petition and in our expert report. And you can see they are quoting this
`
`23
`
`passage where it is showing what's inside the reply envelope. And, again,
`
`24
`
`this is a particular passage we discussed demonstrating that there is another
`
`25
`
`authentication code inside the reply envelope.
`
` 6
`
`
`
`
`

`
`Case IPR2013-00080 (Patent 6,173,403)
`Case IPR2013-00081 (Patent 5,982,889)
`
`JUDGE ARBES: So is it the Petitioner's position, then, that both are
`
`
`
`
`
`the first candidate authentication code? Digital authorization certificate and
`
`the LCH digital signature.
`
`
`
`
`
`MR. KUSHAN: Yes.
`
`JUDGE ARBES: What is the argument, then, and what is your
`
`position as to why the LCH digital signature is the first candidate
`
`authentication code?
`
`
`
`MR. KUSHAN: Sure. So the LCH digital signature -- first of all, a
`
`digital signature is an authentication code as the Patent Owner has contended
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`that term is to be construed. And what we pointed out in our petition was
`
`11
`
`that with respect to the LCH digital signature, that is decrypted to recover
`
`12
`
`the information. It is actually appended to the reply envelope and sent along
`
`13
`
`with it. And through this action of transfer and decryption and unpacking of
`
`14
`
`that reply envelope, you recover that authentication code, which is the digital
`
`15
`
`signature. And then you are going to use that to verify that the message that
`
`16
`
`it accompanies is authentic in the reply envelope.
`
`17
`
`
`
`JUDGE ARBES: It is not part of the reply envelope itself, though, is
`
`18
`
`it?
`
`19
`
`
`
`MR. KUSHAN: I think it is intended. It is used to sign the encrypted
`
`20
`
`reply envelope. So it is transferred with the data set that is the reply. So it is
`
`21
`
`not disassociated from it.
`
`22
`
`23
`
`
`
`
`
`JUDGE ARBES: How do we know that from the reference?
`
`MR. KUSHAN: Well, that's essentially how digital signatures work.
`
`24
`
`You take -- and, in fact, if you go to the -- we didn't provide you with a
`
`25
`
`demonstrative about this. But in the Pettitt scheme, it explains that the LCH
`
` 7
`
`
`
`
`

`
`Case IPR2013-00080 (Patent 6,173,403)
`Case IPR2013-00081 (Patent 5,982,889)
`
`
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`digital signature is bundled with the reply envelope and transferred. And
`
`then when that entire data set comes to the reseller, the reseller takes the
`
`digital signature and verifies that the encrypted reply envelope is authentic.
`
`So it is moving and carrying along with the data that is the encrypted reply
`
`envelope. And we can -- I think we outlined that in more detail in our
`
`papers, but we can drill down, if you wish.
`
`
`
`But I think at the bottom, what we see is that we put out a very clear
`
`position, I think, in our papers that the DAC is an authentication code inside
`
`the reply envelope. In their opposition in one of the proceedings, they take
`
`10
`
`issue with that. And in the other proceeding, this one with '403, they didn't.
`
`11
`
`So you can readily find on the basis of your finding of anticipation that the
`
`12
`
`authentication code is the DAC. It is meeting the requirements of
`
`13
`
`anticipation of Claim 1, which is the ground you instituted on over Pettitt.
`
`14
`
`
`
`If we can go to Slide 9. And, again, we feel like it has been fairly
`
`15
`
`clearly understood by the Petitioner and by the Patent Owner that the digital
`
`16
`
`authorization certificate is an authentication code in Pettitt. One of the
`
`17
`
`issues we did address in Wang's declaration was whether he viewed a DAC
`
`18
`
`to be a digital signature. And he answered yes. And then he confirmed that
`
`19
`
`a digital signature inherently will function to authenticate data, which meets
`
`20
`
`the requirement for an authentication code.
`
`21
`
`
`
`Now, in the recent production of e-mails, we actually were able to see
`
`22
`
`that Dr. Wang didn't really seriously contest the idea that a digital
`
`23
`
`authorization certificate is an authentication code. And I direct you to
`
`24
`
`Exhibit 1067. This is under seal. So that's in the handout I gave you. The
`
`25
`
`quote that we pointed you to in the observations is him recognizing that the
`
` 8
`
`
`
`
`

`
`Case IPR2013-00080 (Patent 6,173,403)
`Case IPR2013-00081 (Patent 5,982,889)
`
`
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`idea that the digital authorization certificate is not an authentication is not
`
`really a viable argument.
`
`
`
`So I would like to move on to the next ground. Go to Slide 11. The
`
`next issue was that the Board found that Claims 2, 4, 5, 7, and 9 are obvious,
`
`based on Pettitt and Beetcher. And in this finding, the Board recognized that
`
`it would have been obvious to modify the Pettitt scheme, which is if the
`
`Board found distributes a single product, to distribute multiple products.
`
`
`
`And the Board's finding relied on testimony from Mr. Schneier and
`
`from the arguments we presented in our petition that you could adapt the
`
`10
`
`Pettitt scheme to distribute multiple products. And the combination of
`
`11
`
`Pettitt with Beetcher was the basis for this.
`
`12
`
`
`
`If you go to Slide 12, this is some of the reasoning that Mr. Schneier
`
`13
`
`provided as to why a person of skill would have considered it obvious to
`
`14
`
`modify Pettitt to distribute multiple products. He is pointing out that you
`
`15
`
`can just adapt it to use over multiple indicia.
`
`16
`
`
`
`Now, importantly, the Patent Owner didn't challenge Mr. Schneier's
`
`17
`
`testimony at his deposition. And so as you sit and review the evidence, this
`
`18
`
`is evidence that is supporting the original finding of obviousness, which
`
`19
`
`really hasn't been disputed.
`
`20
`
`
`
`Dr. Wang, when he put in his declaration, he provided -- he kind of
`
`21
`
`addressed a different question about where there is another reason why a
`
`22
`
`person of skill would combine the Pettitt and Beetcher schemes. If you can
`
`23
`
`go to Slide 13. This is a quote out of his declaration, Exhibit 2014. And
`
`24
`
`with the way we look at this, he is basically confirming that there is a
`
`25
`
`different reason why a person would combine Pettitt and Beetcher. And he
`
` 9
`
`
`
`
`

`
`Case IPR2013-00080 (Patent 6,173,403)
`Case IPR2013-00081 (Patent 5,982,889)
`
`
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`is pointing out that a person would recognize Pettitt has a problem. It
`
`doesn't prevent illegal copying once the software has been installed. And
`
`then he is pointing out that Beetcher solves that problem.
`
`
`
`And the second thing he does with this observation, he confirms that it
`
`is no big deal. It's no technical impediment to integrating the two schemes
`
`so they can work together. So that's what I have to say about the second
`
`ground.
`
`
`
`The next ground, Slide 22, this was a finding that Claim 17 and 19 are
`
`anticipated by Beetcher. And in their opposition, the Patent Owner really
`
`10
`
`only challenged one aspect of the Board's finding of anticipation. And that
`
`11
`
`was this one section I have highlighted in red. It's the element of Claim 17
`
`12
`
`that says the token is encrypted with the string before it is stored.
`
`13
`
`
`
`And essentially the Patent Owner and its expert failed to appreciate
`
`14
`
`that the teaching in Beetcher is that the product key table, which is the
`
`15
`
`element that we have pointed to as anticipating, is something called an
`
`16
`
`encoded product key table.
`
`17
`
`
`
`If you go to Slide 26, at the top of the page, this is an excerpt from
`
`18
`
`Dr. Wang's deposition. He is acknowledging that he didn't pay attention to
`
`19
`
`the name encoded in the sentence that says, "It is an encoded product key
`
`20
`
`table." And this is important because the Patent Owner's position is that our
`
`21
`
`argument was that storing an unencoded product key table was what we
`
`22
`
`were arguing met the requirement of the claim. We didn't argue that. We
`
`23
`
`argued that the encoded product key table is an encrypted product. And we
`
`24
`
`reached that conclusion by our analysis of our expert, Mr. Schneier, who
`
`
`10
`
`
`

`
`Case IPR2013-00080 (Patent 6,173,403)
`Case IPR2013-00081 (Patent 5,982,889)
`
`
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`pointed out that Beetcher uses the word encoded and encrypted
`
`interchangeably to mean the same thing.
`
`
`
`So I asked their witness Dr. Wang about how he read Beetcher. And
`
`he agreed that Beetcher uses these terms interchangeably. And so when our
`
`expert looked at the Beetcher reference and saw the encoded product key
`
`description, he read that as the encrypted product key table. And so under
`
`the theory of what the claim requires, encrypting that product key table
`
`satisfies the element of an encrypted token.
`
`
`
`This was the only ground and the only theory they advanced to refute
`
`10
`
`the finding of the Board of anticipation of Claims 17 and 19. We just think
`
`11
`
`that the evidence from their witness on cross-examination demonstrates that
`
`12
`
`we met our burden for showing it was anticipated.
`
`13
`
`
`
`The next topic I would like to address -- go to Slide 27. This is a
`
`14
`
`finding that Claims 1 through 12 were obvious, based on Beetcher and two
`
`15
`
`different references. And what the Board found here, it found two
`
`16
`
`distinctions from the Claims 1 through 12 relative to Beetcher. One was that
`
`17
`
`the entitlement key in the Beetcher scheme, the Board found was not an
`
`18
`
`authentication code. And what it did was it looked at another reference,
`
`19
`
`Ginter, and found that Ginter provided the idea of modifying the entitlement
`
`20
`
`key with a digital signature.
`
`21
`
`
`
`If you can go to Slide 30. Actually, go to 29. So the first theory that
`
`22
`
`the Patent Owner advances to respond to this issue of integrating the digital
`
`23
`
`signature into the entitlement key was that basically an argument that Ginter
`
`24
`
`doesn't show that you recover the PERC, which is an analogous element in
`
`
`11
`
`
`

`
`Case IPR2013-00080 (Patent 6,173,403)
`Case IPR2013-00081 (Patent 5,982,889)
`
`
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`Ginter, from an encrypted delivery mechanism or item. And they argued
`
`that that meant that you should combine Ginter with Beetcher.
`
`
`
`And what we observed is that their theory that the PERC is not
`
`recovered by encryption is actually refuted by the actual text of Ginter. And
`
`this is in Exhibit 1005 at paper 67. And if you look at the item 2843, that's
`
`the step where the traveling object comes in decrypted from it is the
`
`recovery of the PERC. So we think the first theory they advance that it is
`
`not showing recovery of the PERC by decryption is simply refuted by the
`
`evidence that is relied on.
`
`10
`
`
`
`The second theory that they advanced -- if you go to Page 30 or Slide
`
`11
`
`30. This is an excerpt from their opposition in the '403 case.
`
`12
`
`
`
`JUDGE ARBES: I'm sorry. Counsel, can we go back to the exhibit
`
`13
`
`before that? Why would a person of ordinary skill in the art substitute the
`
`14
`
`entitlement key feature or substitute in the digital signature as taught by
`
`15
`
`Ginter? What's the reason why a person of ordinary skill in the art would
`
`16
`
`want to do that?
`
`17
`
`
`
`MR. KUSHAN: It is to improve the security of the scheme. Digital
`
`18
`
`signatures were widely used in 1997. When our expert looked at the
`
`19
`
`Beetcher scheme, they saw a very analogous use of a digital signature to
`
`20
`
`enhance the security of a token or third element that's functioning to be a
`
`21
`
`verification mechanism. And he said, well, that would have been obvious to
`
`22
`
`improve that by using a digital signature.
`
`23
`
`
`
`JUDGE ARBES: And given how the authentication code is used in
`
`24
`
`the claim as part of a launch code, why would a digital signature be useful in
`
`25
`
`that particular scenario?
`
`
`12
`
`
`

`
`Case IPR2013-00080 (Patent 6,173,403)
`Case IPR2013-00081 (Patent 5,982,889)
`
`MR. KUSHAN: Well, and we have expanded again on our papers a
`
`
`
`
`
`number of different reasons that Mr. Schneier found this to be obvious.
`
`Again, part of it is that when you are using a system that's designed to
`
`securely transfer into a verification mechanism data that you are using to be
`
`the value that you are checking, it can always be improved by different
`
`techniques. And one very common technique was the digital signature.
`
`
`
`The other finding he made was that it would be really insignificant to
`
`add that level of security into the Beetcher scheme. It doesn't really disrupt
`
`how it works. It is not adding a lot of data into the scheme. So it can be
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`captured and integrated relatively easily.
`
`11
`
`
`
`And we will get into this and add that topic as somewhat engaged by
`
`12
`
`the next slide, Slide 30. In their opposition, the Patent Owner advanced this
`
`13
`
`theory. This is a theory that they argued, which is corresponding in
`
`14
`
`Dr. Wang's declaration. But, basically, they argued that a person wouldn't
`
`15
`
`have integrated a digital signature into the Beetcher scheme because adding
`
`16
`
`that digital signature data into the entitlement key would make it impractical.
`
`17
`
`And the reason they found it impractical is that they said, well, if you look at
`
`18
`
`Beetcher, it is envisioning essentially about a 16-character ASCII string.
`
`19
`
`That's their hypothetical. They felt that that would be reasonable to read
`
`20
`
`over the phone to a user and have the user type that in as part of the
`
`21
`
`installation process.
`
`22
`
`
`
`But then they drew a contrast. And they said if you added a digital
`
`23
`
`signature to the entitlement key, it would double or triple the size of that
`
`24
`
`entitlement key. And what that means is that it's going from 16 to 32 or 48
`
`25
`
`characters would cross some line that makes it unobvious. Now, when we --
`
`
`13
`
`
`

`
`Case IPR2013-00080 (Patent 6,173,403)
`Case IPR2013-00081 (Patent 5,982,889)
`
`
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`this was supported by evidence from their expert Dr. Wang. So we took up
`
`the issue of this hypothetical with Dr. Wang in his deposition.
`
`
`
`If you can go to Slide 31, this is kind of the conclusion of the
`
`discussion. We presented him with the example of the Windows XP
`
`installer. And there is a telephone activation process in the Windows XP
`
`installer program. Under that sequence, he walked through the steps and
`
`confirmed them during his deposition. In that sequence, the user can in one
`
`scenario be required to hear 42 digits read to them over the phone and type
`
`in 42 digits into the Windows XP installer to authenticate. And he
`
`10
`
`confirmed that's what happens in that sequence. And then he also confirmed
`
`11
`
`Windows XP is one of the world's most widely used software products on
`
`12
`
`the planet. And it has been installed more than a billion times.
`
`13
`
`
`
`And, basically, we look at that time and conclude in their theory that
`
`14
`
`going from 16 to 32 characters would not be viable and essentially refuted
`
`15
`
`by the experience of Windows XP.
`
`16
`
`
`
`JUDGE ARBES: How do you address that? Where in the papers do
`
`17
`
`they acknowledge that Windows XP was 2001? How do you account for the
`
`18
`
`time difference? We are talking about 1997.
`
`19
`
`
`
`MR. KUSHAN: Right. So the theory you see them advance isn't
`
`20
`
`really something that's going to turn on a user's perspective in 1997 versus
`
`21
`
`2001. The theory they are advancing is that there is too many characters to
`
`22
`
`type in. They are basically saying 16 is okay; 32 is too many. And that's not
`
`23
`
`something that would make any sense to delineate between 1997 and 2001.
`
`24
`
`
`
`People didn't become familiar or accommodating with a greater
`
`25
`
`number of characters between those two dates. So the premise of their
`
`
`14
`
`
`

`
`Case IPR2013-00080 (Patent 6,173,403)
`Case IPR2013-00081 (Patent 5,982,889)
`
`
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`argument is that it is just too many characters to type in if you go past 16.
`
`And so we think that Windows XP testimony, which we are not offering as
`
`prior art, we are offering it up as just refuting of the theory that they are
`
`advancing that it's too many characters to type in.
`
`
`
`JUDGE ARBES: If you were to substitute in a digital signature into
`
`the system of Beetcher, how would a person type that into the computer?
`
`Beetcher obviously is, according to the patent, it is 16 characters that they
`
`type into the computer. A digital signature wouldn't operate the same way,
`
`right? You just type in a set of characters.
`
`10
`
`
`
`MR. KUSHAN: It would. I mean, we went through the hypothetical
`
`11
`
`in some detail with Dr. Wang. And I can pull up his deposition transcript, if
`
`12
`
`you wish. But what we demonstrated through the cross-examination of
`
`13
`
`Dr. Wang is that if you took a 128-bit digital signature, that would add 16
`
`14
`
`characters to the string that's already there, which is 16 characters from the
`
`15
`
`entitlement key. And that ends up being 32 characters. And that's the basic
`
`16
`
`level of a digital signature -- 128 bits. And he confirmed my math, which
`
`17
`
`was very important. But we basically were taking their hypothetical and
`
`18
`
`used that 128-bit example to show that would be integration of a digital
`
`19
`
`signature.
`
`20
`
`
`
`JUDGE ARBES: And that could be done in ASCII or you could just
`
`21
`
`type that into the computer?
`
`22
`
`
`
`MR. KUSHAN: Yes. The last thing I am going to touch on before I
`
`23
`
`turn it over to Mr. Micallef is a second difference that we found relative to
`
`24
`
`Beetcher. If you can go to Slide 32. And, basically, the Board found that in
`
`25
`
`the Beetcher scheme, the entitlement key is checked essentially at runtime
`
`
`15
`
`
`

`
`Case IPR2013-00080 (Patent 6,173,403)
`Case IPR2013-00081 (Patent 5,982,889)
`
`
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`after the software has been copied over. And we, in consultation with our
`
`expert, found that it would have been obvious to modify that scheme to
`
`essentially check the entitlement key as you are installing the software
`
`instead of checking it after it has been loaded onto a computer. This is
`
`something we set out pretty clear at Page 26 of our petition.
`
`
`
`And that was supported by a number of paragraphs of Mr. Schneier's
`
`declaration. And I have quoted 367 here. But, basically, the upshot is that a
`
`person of skill from the perspective of Mr. Schneier would have considered
`
`it obvious to modify the Beetcher scheme to capture the entitlement key and
`
`10
`
`to basically change the design of when it is checked so as to do that while
`
`11
`
`you are installing the software.
`
`12
`
`
`
`Again, this testimony from Mr. Schneier and this theory that we
`
`13
`
`advanced really wasn't tested at his deposition. And what we see in their
`
`14
`
`opposition essentially is kind of a theory that rests on, I think, a weak legal
`
`15
`
`foundation. Their arguments are essentially Beetcher works fine; we don't
`
`16
`
`need to modify Beetcher. So a person of skill wouldn't have any motivation
`
`17
`
`to change the Beetcher design.
`
`18
`
`
`
`For example, to install or check the entitlement key during the
`
`19
`
`installation process. And we think that really rests on the theory that has
`
`20
`
`been refuted by recent case law on obviousness. I think the standard that
`
`21
`
`you would say if you have to define a specific motivation to amend or
`
`22
`
`change the system, that's really not a viable basis for making the argument
`
`23
`
`for non-obviousness when you find another reason to adapt a system.
`
`
`16
`
`
`

`
`Case IPR2013-00080 (Patent 6,173,403)
`Case IPR2013-00081 (Patent 5,982,889)
`
`And from the testimony of Mr. Schneier, he is identifying this is
`
`
`
`
`
`basically a simple design change. You would just enter the entitlement key
`
`at a certain point earlier in the sequence.
`
`
`
`JUDGE ARBES: Counsel, doesn't Beetcher really have nothing to do
`
`with the installation of the software? I understand that Beetcher sends a
`
`generic CD out to everyone. And how they install it doesn't matter to the
`
`system that they are concerned about. So why would a person of ordinary
`
`skill in the art modify that for the installation?
`
`
`
`MR. KUSHAN: Well, Beetcher obviously does the check at runtime.
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`And that's one of the values of the Beetcher system. But when the person
`
`11
`
`looks at the prior art and thinks openly about whether you could adapt it to
`
`12
`
`relatively simply design changes, what immediately comes to mind is
`
`13
`
`another alternative. You capture the entitlement at the point of installation.
`
`14
`
`You have to get the entitlement into the scheme in Beetcher somehow. And
`
`15
`
`you can easily do that through the step or you are installing it.
`
`16
`
`
`
`You have the software on media. And it has to go from media to your
`
`17
`
`hard drive before you can use it. And you could either capture the
`
`18
`
`entitlement at that point when you are transferring during the installation
`
`19
`
`process, which is illustrated in the technique of Bohannon, or you can do it
`
`20
`
`at a later point in time. And our expert believed that kind of design choice
`
`21
`
`was relatively simple and obvious.
`
`22
`
`
`
`So we think on these grounds, the evidence really hasn't been
`
`23
`
`seriously disputed that supports the finding of unpatentability. I would like
`
`24
`
`to turn over the podium to my colleague Mr. Micallef to take over on the
`
`25
`
`Ginter issue unless you have any other questions.
`
`
`17
`
`
`

`
`Case IPR2013-00080 (Patent 6,173,403)
`Case IPR2013-00081 (Patent 5,982,889)
`
`JUDGE ANDERSON: Counsel, before you do that, I would like to
`
`
`
`
`
`follow up on this issue about the DAC.
`
`
`
`
`
`MR. KUSHAN: Sure.
`
`JUDGE ANDERSON: The claim says, "Encrypt the launch code with
`
`a string to recover a first candidate authentication code." And so looking at
`
`the claim language specifically, what's your evidence that the DAC is
`
`recovered as a result of decrypting the launch code?
`
`
`
`MR. KUSHAN: So can you go to Slide 3? So in the Pettitt scheme,
`
`there are a number of data elements that are kind of taken together and
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`encrypted as a set. And that becomes the encrypted reply envelope. The
`
`11
`
`DAC is one of those data elements that's inside that encrypted rely envelope.
`
`12
`
`That encrypted rely envelope is then sent down to a reseller. And you go
`
`13
`
`through a distributor and directly to the reseller. And when the reseller gets
`
`14
`
`the encrypted replay envelope, it will decrypt the reply envelope and the
`
`15
`
`recovery contents. So now the contents are in unencrypted form as those
`
`16
`
`same data elements. Those data elements and then passed to the user and
`
`17
`
`used to install the software. And in Pettitt directly, it cites to DAC and the
`
`18
`
`master key for encrypting the software container to do that installation.
`
`19
`
`
`
`JUDGE ANDERSON: And where is that in your evidence? Is that in
`
`20
`
`the Schneier report?
`
`21
`
`
`
`MR. KUSHAN: Sure. If you could go to -- let's take a look at Slide
`
`22
`
`4. For example, we have discussed this in Paragraph 470 of Mr. Schneier's
`
`23
`
`report. This is where he is using the contents of the reply envelope after
`
`24
`
`they have been decrypted to do the installation.
`
`
`18
`
`
`

`
`Case IPR2013-00080 (Patent 6,173,403)
`Case IPR2013-00081 (Patent 5,982,889)
`
`And, also, we did go through the sequence of Pettitt with Dr. Wang.
`
`
`
`
`
`If you can go to the next slide. So this is a passage from Dr. Wang's
`
`deposition where we are working through kind of what the Pettitt scheme is.
`
`And he is confirming here that there are six items of information inside the
`
`encrypted reply envelope. This is a passage at Exhibit 2034, Page 235, 6
`
`through 19. And then subsequent to the step is the decryption step. I am not
`
`sure I have that as a demonstrative. But I would be happy to perhaps take
`
`that up on our rebuttal if you want to follow up.
`
`
`
`MR. MICALLEF: Good afternoon, Your Honors. My name is
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`Joe Micallef for the Petitioner. I am going to be dealing with the grounds
`
`11
`
`that are

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