throbber
UNITED STATES PATENT AND TRADEMARK OFFICE
`
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`
`APPLE INC.,
`Petitioner
`
`v.
`
`
`
`IMMERSION CORPORATION
`Patent Owner
`
`U.S. Patent No. 8,773,356
`Filing Date: January 31, 2012
`Issue Date: July 8, 2014
`Title: Method and Apparatus for Providing Tactile Sensations
`
`
`Case IPR2016-01381
`
`
`
`PETITIONER’S RESPONSE TO PATENT OWNER’S CORRECTED
`MOTION FOR OBSERVATION ON CROSS EXAMINATION
`
`
`
`
`Mail Stop Patent Board
`Patent Trial and Appeal Board
`P.O. Box 1450
`Alexandria, VA 22313-1450
`
`
`
`
`WEST\278046993.1
`
`

`

`
`
`
`Petitioner Apple Inc. submits the following responses to Patent Owner’s
`
`Corrected Motion for Observation (Paper No. 28) regarding the August 14, 2017
`
`deposition of Petitioner’s expert, Dr. Patrick Baudisch (Exhibit 2013).
`
`1. Observation #1
`
`Patent Owner’s selected portion of Dr. Baudisch’s testimony (Exhibit 2013
`
`at 54:3-13), that Rosenberg 737 does not “exclude” networked computing, does not
`
`support Patent Owner’s new argument that networked computing is “present” in
`
`Rosenberg 737, and is not relevant to the fact that Exhibit 2007 does not use a
`
`lookup table because it merely communicates information directly to another user.
`
`See Reply at 16-17 and Exhibit 1025 at ¶ 20.
`
`2. Observation #2
`
`Patent Owner’s selected portion of Dr. Baudisch’s testimony (Exhibit 2013
`
`at 52:13-53:3; 54:15-21), that he is aware of networked computer gaming, does not
`
`support Patent Owner’s new argument that networked computer gaming is
`
`“present” in Rosenberg 737, and is not relevant to the fact that Exhibit 2007 does
`
`not use a lookup table because it merely communicates information directly to
`
`another user. See Reply at 16-17 and Exhibit 1025 at ¶ 20.
`
`3. Observation #3
`
`Patent Owner’s selected portion of Dr. Baudisch’s testimony (Exhibit 2013
`
`at 12:9-23) includes Dr. Baudisch’s testimony that he assumes that a noun can
`
`WEST\278046993.1
`
`
`1
`
`

`

`
`
`serve as an adjective in “some examples.” See Exhibit 2013 at 12:11-12. This
`
`testimony does not support, and actually refutes, Patent Owner’s new assertion that
`
`Dr. Baudisch did not consider the “possibility” that “interaction” was an adjective.
`
`4. Observation #4
`
`Patent Owner’s selected portion of Dr. Baudisch’s testimony (Exhibit 2013
`
`at 16:10-17:6) regarding the open-ended nature of “comprising” confirms the
`
`breadth of the “based at least in part on” limitation. See Reply at 4; Exhibit 1025
`
`at ¶ 9.
`
`5. Observation #5
`
`Patent Owner’s selected portion of Dr. Baudisch’s testimony (Exhibit 2013
`
`at 19:2-5; 23:20-23:3), regarding his understanding of the meaning of the label
`
`“embodiment” in the specification, is not relevant to the stated issue, i.e., that
`
`certain disclosed embodiments are within the scope of the claim under Petitioner’s
`
`proposed construction and excluded by Patent Owner’s proposed construction. See
`
`Reply at 6-7 and Exhibit 1025 at ¶ 10. As Dr. Baudisch testified, “I certainly did
`
`analyze which parts of disclosure would be included or excluded, depending on
`
`particular constructions of claim 1.” Ex. 2013 at 25:2-6.
`
`6. Observation #6
`
`Patent Owner’s selected portion of Dr. Baudisch’s testimony (Exhibit 2013
`
`at 25:12-19), regarding whether claim 1 necessarily encompasses all disclosed
`
`WEST\278046993.1
`
`
`2
`
`

`

`
`
`embodiments, is not relevant to the stated issue, i.e., that certain disclosed
`
`embodiments (e.g., the dwell to select embodiment) are within the scope of the
`
`claim under Petitioner’s proposed construction and excluded by Patent Owner’s
`
`proposed construction. See Reply at 6-7 and Exhibit 1025 at ¶ 10. As Dr.
`
`Baudisch testified, “I certainly did analyze which parts of disclosure would be
`
`included or excluded, depending on particular constructions of claim 1.” Ex. 2013
`
`at 25:2-6; 75:11-25.
`
`7. Observation #7
`
`Patent Owner’s selected portion of Dr. Baudisch’s testimony (Exhibit 2013
`
`at 37:2-11; 39:6-10) is not relevant to the stated issue, i.e., that certain disclosed
`
`embodiments (e.g., Figure 8 and accompanying text and function failure
`
`embodiments) are within the scope of the claim under Petitioner’s proposed
`
`construction and excluded by Patent Owner’s proposed construction. See Reply at
`
`6-7 and Exhibit 1025 at ¶ 10. As Dr. Baudisch testified, “I certainly did analyze
`
`which parts of disclosure would be included or excluded, depending on particular
`
`constructions of claim 1.” Ex. 2013 at 25:2-6; 83:17-25.
`
`8. Observation #8
`
`Patent Owner’s selected portion of Dr. Baudisch’s testimony (Exhibit 2013
`
`at 67:7-17) includes the answer “Yes, that would be my understanding. If you look
`
`at the literature in touchscreens broadly, you realize that, typically, the screen is
`
`WEST\278046993.1
`
`
`3
`
`

`

`
`
`redesigned in a way that targets on the screen are enlarged so as to make
`
`acquisition using a touch easier.” This testimony supports the arguments and
`
`testimony at Reply at 15 and Exhibit 1025 at ¶ 18. Patent Owner’s new argument
`
`that Rosenberg 737 also discloses that in “some” embodiments the PDA screen
`
`could have more or different functionality is not relevant to the stated issue.
`
`9. Observation #9
`
`Patent Owner’s selected portion of Dr. Baudisch’s testimony (Exhibit 2013
`
`at 58:25-59:10; 161:13-18), regarding other embodiments in Rosenberg 737, is not
`
`relevant to the stated issue, which is directed to the menu selection embodiment in
`
`Rosenberg 737. See Reply at 15 and Exhibit 1025 at ¶ 18. Additionally, as Dr.
`
`Baudisch testified, the additional teachings of Rosenberg 737 relate to functionality
`
`that would be digitized, sequenced, and quantized such that the rate of change
`
`would be “very moderate” for the computer. Exhibit 2013 at 61:25-62:12.
`
`10. Observation #10
`
`Patent Owner’s selected portion of Dr. Baudisch’s testimony (Exhibit 2013
`
`at 64:13-20), that he could not recall pointing out in his declarations where
`
`nonlinear equations were “needed” is not relevant to the stated issue, as the stated
`
`issue is obviousness, not inherency. See Reply at 15 and Exhibit 1025 at ¶ 16.
`
`
`
`
`
`WEST\278046993.1
`
`
`4
`
`

`

`
`
`
`11. Observation #11
`
`Patent Owner’s selected portions of Dr. Baudisch’s testimony (Exhibit 2013
`
`at 72:2-4; 74:8-75:3) are not relevant to the stated issue that “using a lookup table
`
`can often be faster (i.e., more efficient) than calculating . . . .” See Reply at 15 Ex.
`
`1025 at ¶ 15. As Dr. Baudisch testified immediately between the two portions
`
`selected by Patent Owner, the relative efficiencies of these known design choices
`
`are implementation dependent and “If we talk about in the very abstract, those
`
`computations can certainly be made. In contrast, the ’737 patent, for example, is
`
`very different in the fact they could not be done with this computation. That would
`
`much be - - would be much more amenable to a lookup table.” Exhibit 2013 at
`
`73:5-25. Moreover, the testimony selected by Patent Owner relates to present-day
`
`high-end processors, not processors at date of invention which could take much
`
`longer. See Exhibit 2013 at 74:8-75:3.
`
`12. Observation #12
`
`Patent Owner’s selected portion of Dr. Baudisch’s testimony (Exhibit 2013
`
`at 66:13-17) improperly truncates Dr. Baudisch’s answers by starting on the last
`
`line of an answer. The full citation is Exhibit 2013 at 66:3-17, including the
`
`testimony “[w]hether to compute something on the fly or whether to precompute it
`
`is always an option for any engineer in software. And it’s always something you
`
`consider. And I think in this particular case, the ’737 offers a good number of
`
`WEST\278046993.1
`
`
`5
`
`

`

`
`
`qualities that would actually suggest that you want to use a lookup table”, such that
`
`the full testimony supports the stated issue that a lookup table was an obvious
`
`design choice. As Dr. Baudisch repeatedly testified, he believed the lookup tables
`
`were an obvious design choice in the context of Rosenberg 737. Exhibit 2013 at
`
`65:2-66:13; 78:18-79:4; 87:13-89:4. See Reply at IV.A and IV.B and Sections
`
`IV.B and IV.C of Exhibit 1025.
`
`Dated: September 5, 2017
`
`Respectfully Submitted,
`
`
`
`
`
` /James M. Heintz/
`James M. Heintz
`Reg. No. 41,828
`DLA Piper LLP (US)
`11911 Freedom Drive, Suite 300
`Reston, VA 20190
`Apple-Immersion-IPRs@dlapiper.com
`Phone: 703-773-4148
`Fax: 703-773-5200
`
`Brian Erickson
`Reg. No. 48,895
`DLA Piper LLP (US)
`401 Congress Avenue, Suite 2500
`Austin, TX 78701
`Brian.erickson@dlapiper.com
`Phone: 512-457-7059
`Fax: 512-721-2263
`
`Attorneys for Petitioner Apple Inc.
`
`WEST\278046993.1
`
`
`6
`
`

`

`
`
`
`CERTIFICATE OF SERVICE
`
`The undersigned hereby certifies that a copy of the foregoing Petitioner’s
`
`Response to Patent Owner’s Corrected Motion for Observation on Cross
`
`Examination was served on September 5, 2017, via electronic mail, per agreement
`
`of the parties, to counsel at the following addresses:
`
`Michael R. Fleming
`IRELL & MANELLA LLP
`1800 Avenue of the Stars, Suite 900
`Los Angeles, CA 90067-4276
`
`mfleming@irell.com
`ImmersionIPR@irell.com
`
`Crawford Maclain Wells
`IRELL & MANELLA LLP
`1800 Avenue of the Stars, Suite 900
`Los Angeles, CA 90067
`
`mwells@irell.com
`
`Babak Redjaian
`IRELL & MANELLA LLP
`1800 Avenue of the Stars, Suite 900
`Los Angeles, CA 90067-4276
`
`bredjaian@irell.com
`ImmersionIPR@irell.com
`
`
`
`
`Dated: September 5, 2017
`
`Respectfully Submitted,
`
`
`
` /James M. Heintz/
`James M. Heintz
`Reg. No. 41,828
`DLA Piper LLP (US)
`11911 Freedom Drive, Suite 300
`Reston, VA 20190
`Apple-Immersion-IPRs@dlapiper.com
`Phone: 703-773-4148
`Fax: 703-773-5200
`
`Brian Erickson
`Reg. No. 48,895
`
`WEST\278046993.1
`
`
`7
`
`

`

`
`
`
`
`
`
`
`DLA Piper LLP (US)
`401 Congress Avenue, Suite 2500
`Austin, TX 78701
`Brian.erickson@dlapiper.com
`Phone: 512-457-7059
`Fax: 512-721-2263
`
`Attorneys for Petitioner Apple Inc.
`
`WEST\278046993.1
`
`
`8
`
`

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