throbber
FORD MOTOR COMPANY v. PAICE, LLC, ET AL.
`
`NEIL HANNEMANN
`
`April 7, 2015
`
`Prepared for you by
`
`Bingham Farms/Southfield • Grand Rapids
`Ann Arbor • Detroit • Flint • Jackson • Lansing • Mt. Clemens • Saginaw
`
`1
`
`PAICE 2211
`Ford v. Paice & Abell
`IPR2015-00792
`
`

`
`
`NEIL HANNEMANNNEIL HANNEMANN
`
`April 7, 2015April 7, 2015
`
`
`
`Page 1Page 1
`
` UNITED STATES PATENT AND TRADEMARK OFFICE
` BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
` FORD MOTOR COMPANY, :
` Petitioner, :
` v. : IPR Case No:
` PAICE LLC & ABELL FOUNDATION, : IPR2014-00571
` INC., :
` Patent Owner. :
` :
`- - - - - - - - - - - - - - - - -x
`
` Oral Deposition of NEIL HANNEMANN
` Washington, DC
` Tuesday, April 7, 2015
` 9:58 a.m.
`
`Job No.: 79874
`Pages: 1 - 145
`Reported By: Rebecca Stonestreet, RPR, CRR
`
`1
`2
`
`345
`
`6
`7
`8
`9
`10
`11
`12
`13
`14
`15
`16
`17
`18
`19
`20
`21
`22
`23
`24
`25
`
`2
`
`

`
`
`NEIL HANNEMANNNEIL HANNEMANN
`
`April 7, 2015April 7, 2015
`
`
`
`Page 112Page 112
`
`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
`
`other commands?
` A That's correct.
` Q It says: "Acceleration, direction,
`deceleration." Right?
` A Yes.
` Q And then it's got those five data input --
`data inputs, rather, that are going into the
`microprocessor controller in that cover page figure.
`Right?
` A That's correct.
` Q So do you agree, then, that in this '970
`patent, the microprocessor is going to determine how much
`torque the motor provides, or the engine provides at any
`given time?
` MR. LIVEDALEN: Objection. Vague.
` A Well, this describes that it performs that
`function, but it doesn't describe how it's doing it.
` Q Do you agree that when the microprocessor in
`the '970 patent is determining how much torque the motor
`and/or the engine should be generating, it's doing so
`based on what the microprocessor concludes is required at
`that point in time?
` MR. LIVEDALEN: Objection. Vague, calls for
`speculation.
` A Well, yeah, the microprocessor -- basically,
`
`3
`
`

`
`
`NEIL HANNEMANNNEIL HANNEMANN
`
`April 7, 2015April 7, 2015
`
`
`
`Page 113Page 113
`
`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
`
`you're asking if the microprocessor would perform as it's
`intended to, as it's programmed to. And yeah, however
`it's programmed is what it will do.
` Q So however it's programmed, to determine the
`amount of torque required from the motor and/or the
`engine, that's how it's going to make that determination
`when it's driving down the road. Correct?
` MR. LIVEDALEN: Same objection.
` A Right. There's many ways that it could do
`that, and what's missing in the '970 patent is any
`reference of using the road load to make that
`determination.
` Q In the '970 patent, when a microprocessor
`determines how much torque is required from the motor end
`or the engine, do you agree it does it instantaneously,
`or in real time?
` MR. LIVEDALEN: Objection. Vague, foundation.
` A You know, I don't recall if I ever read in
`here if they disclosed it was real time or not. So I
`guess I just don't know that.
` Q Would a person of skill in the art know that
`when a microprocessor is determining how much torque is
`required, they generally do it based on instantaneous
`conditions?
` MR. LIVEDALEN: Objection. Vague, foundation,
`
`4

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