throbber
INTER PARTES REVIEW
`U.S. PATENT NO. 7,280,097
`
`O R A L A R G U M E N T, M A R . 3 0 , 2 0 1 6
`
`
`
`Sony Computer Entertainment America LLC v. Aplix IP Holdings Corporation
`Case IPR2015-00729; U.S. Patent No. 7,280,097
`
`Petitioner’s DX-1
`
`
`
`

`
`‘097 PATENT - ABSTRACT
`‘O97 PATENT - ABSTRACT
`
`Ex. 1001 at Abstract
`Ex. 1001 of Abs’rro<:’r
`
`Petitioner’s DX-2
`
`
`
`

`
`‘097 PATENT – EXEMPLARY CLAIM
`
`Ex. 1001 at Claim 1
`
`Petitioner’s DX-3
`
`
`
`

`
`INSTITUTED GROUNDS
`
`•  Claims 1-4, 7, 8, 13, 14, 16-28, 21, 23-29, 31, and 34-38 obvious over
`Mollinari and Nishiumi
`•  Claims 6, 22, and 32 obvious over Mollinari, Nishiumi, and Tu
`•  Claims 10-12 obvious over Kerr and Lum
`•  Claims 5, 9, 19, and 30 anticipated by Shima
`
`•  PO’s Challenges in Response
`•  Claim Construction
`•  Nishiumi and Tu are not analogous art
`•  Prior art missing limitations
`
`Paper 13, Institution Decision at 14; Paper 21, Response
`
`Petitioner’s DX-4
`
`
`
`

`
`HAND-HELD HOST DEVICE
`
`•  The term hand-held host device must at least include laptops,
`because the inventors of the ‘097 Patent described it that way.
`
`Paper 26, Reply at 10-11; Ex. 1001 at 14:36-42
`
`Petitioner’s DX-5
`
`
`
`

`
`HAND-HELD HOST DEVICE
`
`Paper 26, Reply at 10-11; Ex. 1001 at Claims 27, 38
`
`Petitioner’s DX-6
`
`
`
`

`
`PATENT OWNER’S VIEW
`
`•  Inclusion of laptops in specification is a “typo.”
`
`•  But “where claims can reasonably [be] interpreted
`to include a specific embodiment, it is incorrect to
`construe the claims to exclude that embodiment,
`absent probative evidence [to] the contrary.”
`•  Oatey Co. v. IPS Corp., 514 F.3d 1271, 1277 (Fed. Cir. 2008).
`•  See also In re Katz, 639 F.3d 1303, 1324 (Fed. Cir. 2011)
`(“there is a strong presumption against a claim construction
`that excludes a disclosed embodiment.”).
`
`Ex. 1041, 3rd Lim Tr. At 113:12-121:21; Paper 26, Reply at 9-11
`
`Petitioner’s DX-7
`
`
`
`

`
`INPUT CONTROLLER
`
`•  The term input controller is not limited to devices
`that interpret signals before transmitting to the host
`•  The claims just require the input controller to
`generate and relay an input signal:
`
`Ex. 1001 at Claim 1
`
`Petitioner’s DX-8
`
`
`
`

`
`PATENT OWNER’S VIEW
`
`•  The input controller must “interpret input data and
`convert it to an input signal ready to be mapped to
`control functions of a software application.”
`•  But this requirement is not in the claims.
`•  And the specification includes an embodiment where the
`interpretation occurs at the host, not the input controller.
`
`Paper 21, Response at 27-29; Ex. 1001 at 11:41-46
`
`Petitioner’s DX-9
`
`
`
`

`
`INPUT ELEMENT ON A SURFACE
`
`•  The term “input element” should be understood to
`include any input or selection type known to one of
`skill in the art, just as the ‘097 Patent describes.
`
`Ex. 1001 at 18:27-31
`
`Petitioner’s DX-10
`
`
`
`

`
`PATENT OWNER’S VIEW
`
`•  Input elements must be limited to “structure[s]
`designed to be interacted with by way of direct
`contact with the thumb or finger.”
`•  But this requirement is not in the claims.
`
`
`
`Paper 21, Response at 29-30; Ex. 1001 at Claim 2
`
`Petitioner’s DX-11
`
`
`
`

`
`CONFIGURED TO OPTIMIZE A
`BIOMECHANICAL EFFECT
`•  The term should be defined to mean exactly what
`the inventors of the ‘097 Patent defined it to mean.
`
`Ex. 1001, at Abstract
`
`Petitioner’s DX-12
`
`
`
`

`
`PATENT OWNER’S VIEW
`
`•  The term requires pinching or squeezing.
`
`•  But this is not required by the claims.
`
`•  And limiting the term to pinching or squeezing is at-odds
`with the explicit definition provided by the ‘097 Patent itself.
`
`Paper 21, Response at 30-31
`
`Petitioner’s DX-13
`
`
`
`

`
`PRIOR ART - MOLLINARI
`
`Ex. 1003 at Fig. 1a
`
`Petitioner’s DX-14
`
`
`
`

`
`PRIOR ART - NISHIUMI
`PRIOR ART - NISI-IIUMI
`
`Ex. 1004 at Figs. 7, 8
`EX- 1004 C” H95 7/ 8
`
`Pe’ri’rioner’s DX—15
`Petitioner’s DX-15
`
`
`
`

`
`NISHIUMI – SAME FIELD OF ENDEAVOR
`
`•  The field of endeavor should be defined to include
`at least “hand-held input devices for interacting
`with electronic devices”
`
`Ex. 1001 at 1:11-18
`
`Petitioner’s DX-16
`
`
`
`

`
`NISHIUMI – SAME FIELD OF ENDEAVOR
`
`•  Not limited to hand-held hosts like cellular phones
`
` •
`
`  Indeed, PO has accused Sony game controllers of
`infringement in the related district court litigation
`
`Ex. 1001 at 19:42-48; Paper 26, Reply at 4; Ex. 2005 at ¶¶ 18, 20, 53
`
`Petitioner’s DX-17
`
`
`
`

`
`NISHIUMI – REASONABLY PERTINENT
`
`•  Nishiumi describes a Nintendo controller with a
`joystick (i.e., analog input)
`•  Inventors expressly stated a desire to include analog
`input features from commercial game controllers
`
`Ex. 1001 at 5:8-17; see also generally Ex. 1004
`
`Petitioner’s DX-18
`
`
`
`

`
`PRIOR ART – TU
`
`Ex. 1005 at Fig. 4
`
`Petitioner’s DX-19
`
`
`
`

`
`TU – SAME FIELD OF ENDEAVOR
`
`•  Tu describes a game controller, i.e., a hand-held
`input device for interacting with electronic devices
`
`Ex. 1005 at [0033]
`
`Petitioner’s DX-20
`
`
`
`

`
`TU – REASONABLY PERTINENT
`
`•  Tu describes the same problem as the ‘097 Patent
`
`Compare Ex. 1001 at 12:30-36 with Ex. 1005 at [0012]
`
`Petitioner’s DX-21
`
`
`
`

`
`MOLLINARI-NISHIUMI
`
`•  PO’s Arguments
`•  1. No motivation to combine
`•  2. Mollinari does not disclose the claimed input controller
`
`•  Motivation to Combine
`•  Including input elements on the rear and side of a device
`was an obvious design choice with predictable results
`
`Paper 21, Response at 33-36; see also Ex. 1009, Welch Decl. at ¶¶ 41-45
`
`Petitioner’s DX-22
`
`
`
`

`
`MOLLINARI-NISHIUMI
`
`•  Input Controller
`•  PO alleges that the claims exclude raw unstructured data,
`and that Mollinari teaches only raw unstructured data
`•  In reality, neither the claims nor Mollinari say this
`
`Ex. 1001 at Claim 1
`
`Petitioner’s DX-23
`
`
`
`

`
`MOLLINARI-NISHIUMI
`
`•  Input Controller – Mollinari:
`
`Ex. 1003 at 10:36-11:7
`
`Petitioner’s DX-24
`
`
`
`

`
`MOLLINARI-NISHIUMI
`
`•  Input Controller – Dr. Welch:
`
`Ex. 1039 at ¶ 27
`
`Petitioner’s DX-25
`
`
`
`

`
`MOLLINARI-NISHIUMI-TU
`
`•  Tu teaches rapid text input for claims 6, 22, and 32
`•  PO contends Tu’s text entry would not work with a host that
`had a hardware interface like a keypad
`•  PO also contends that Tu’s text entry would not work on
`screens smaller than a “generous television screen”
`
`•  Tu explicitly teaches otherwise:
`
`Paper 21, Response at 40-41; Ex. 1005 at [0033]
`
`Petitioner’s DX-26
`
`
`
`

`
`KERR-LUM
`
`•  Claims 10-12 are obvious over Kerr-Lum
`•  PO criticizes the combination because Kerr fails to articulate
`“what kind of ‘processing’ it might perform”
`
`•  Claims 10-11 do not recite a processor; claim 12 requires:
`
`•  That is what Kerr describes:
`
`Paper 21, Response at 41-44; Ex. 1001 at Claim 12; Ex. 1007 at [0087]
`
`Petitioner’s DX-27
`
`
`
`

`
`KERR-LUM
`
`•  PO also asserts:
`•  “[N]othing in Kerr discloses or suggests that Processor 805
`‘stores and executes instructions relating to firmware or a
`gaming application’”
`
`•  None of the claims require this:
`
`Paper 21, Response at 44; Ex. 1001 at Claims 10-12
`
`Petitioner’s DX-28
`
`
`
`

`
`KERR-LUM
`
`•  In any event, Kerr discloses a processor with memory and
`executing firmware and gaming functions
`
` •
`
`  Further, a PHOSITA would have understood that in order to
`receive an act on instructions, a processor would store them
`•  See Ex. 1039 at ¶¶ 46-47
`
`Ex. 1007 at [0087]-[0088]
`
`Petitioner’s DX-29
`
`
`
`

`
`KERR-LUM
`
`•  Finally, PO asserts that Kerr fails to disclose an input controller
`
`•  But Kerr explicitly describes monitoring operating states of
`buttons and transferring that data to a wireless phone:
`
` •
`
`  A PHOSITA would have understood that state monitoring is one
`of the more important roles of an input controller
`•  See Ex. 1039 at ¶ 29
`
`Paper 21, Response at 44-45; Ex. 1007 at [0089]
`
`Petitioner’s DX-30
`
`
`
`

`
`SHIMA
`
`•  Shima anticipates claims 5, 9, 19, and 30
`•  For example, compare claim 5 and Shima:
`
`Ex. 1001 at Claim 5; Ex. 1006 at Figs. 3, 4
`
`Petitioner’s DX-31
`
`
`
`

`
`SHIMA
`
`•  PO contends that the device described in Shima is
`not used with a hand-held host
`•  This is a claim construction issue, because there is no dispute
`that Shima discloses using the device with a laptop
`•  And as discussed before, the ‘097 Patent defines and claims
`the term hand-held host to include a laptop
`
`•  PO contends that the device described in Shima
`does not teach three surfaces with input assemblies
`•  Again this is a claim construction issue, and the claims do
`not require direct contact with fingers or a thumb
`•  The mouse device in Shima is an input element on a surface
`
`Paper 21, Response at 46-53; Paper 26, Reply at 23-25; Ex. 1006 at Figs. 3, 4
`
`Petitioner’s DX-32
`
`
`
`

`
`SHIMA
`
`•  Finally, PO contends that the device
`disclosed in Shima is not optimized
`•  Again this is a claim construction issue
`•  In the ‘097 Patent, this means: including,
`on one surface, input element(s)
`manipulatable by the user’s thumbs or
`fingers and, on another surface, input
`element(s) manipulatable by the user’s
`fingers
`•  Shima discloses a device that meets this
`limitation
`
`Paper 21, Response at 54-56; Paper 26, Reply at 23-25; Ex. 1006 at Figs. 3, 4
`
`Petitioner’s DX-33
`
`
`
`

`
`INTER PARTES REVIEW
`U.S. PATENT NO. 7,932,892
`
`O R A L A R G U M E N T, M A R . 3 0 , 2 0 1 6
`
`
`
`Sony Computer Entertainment America LLC v. Aplix IP Holdings Corporation
`Case IPR2015-00730; U.S. Patent No. 7,932,892
`
`Petitioner’s DX-34
`
`
`
`

`
`INSTITUTED GROUNDS
`
`•  Claims 1-4, 6, and 7 obvious over Mollinari and Nishiumi
`•  Claim 11 obvious over Mollinari and Jacobi
`•  Claim 5 obvious over Mollinari, Nishiumi, and Tu
`•  Claims 8-10 obvious over Kerr and Lum
`
` •
`
`  Substantial overlap with the issues in the ‘097 Proceeding
`•  No need for claim construction and analysis related to Shima
`•  One unique issue: combination of Mollinari and Jacobi for Claim 11
`
`Paper 11, Institution Decision at 18
`
`Petitioner’s DX-35
`
`
`
`

`
`MOLLINARI-JACOBI
`
`•  Jacobi teaches the concepts of claim 11:
`
`Compare Ex. 1001 at Claim 11 with Ex. 1005 at ¶ [0030]
`
`Petitioner’s DX-36
`
`
`
`

`
`MOLLINARI-JACOBI
`
`•  PO asserts that there would have been no reason to
`modify the controller disclosed in Mollinari
`•  But Jacobi describes embodiments
`integrated into remote controls:
`
`Paper 19, Response at 35-38; Ex. 1003 at Fig. 1a; Ex. 1005 at [0017]
`
`Petitioner’s DX-37
`
`
`
`

`
`U.S. Patent No. 7,280,097
`IPR2015-00729
`CERTIFICATE OF SERVICE ON PATENT OWNER
`UNDER 37 C.F.R. § 42.6
`
`Pursuant to 37 C.F.R. § 42.6(e), the undersigned certifies that on March 25, 2016
`the foregoing Petitioner’s Demonstrative Exhibits was served via electronic filing with
`the Board on the following counsel of record for Patent Owner:
`
`Michael Mauriel, USPTO Reg. No. 44,226
`Sherman W. Kahn (pro hac vice)
`MAURIEL KAPOUYTIAN WOODS LLP
`15 West 26th Street, Floor 7
`New York, NY 10010
`Telephone: (212) 529-5131 Ex. 101
`Facsimile:
`(212) 529-5132
`E-mail:
`mmauriel@mkwllp.com
`
`
`skahn@mkwllp.com
`
`Robert J. Gilbertson (pro hac vice)
`Sybil L. Dunlop (pro hac vice)
`X. Kevin Zhao (pro hac vice)
`GREENE ESPEL PLLP
`222 South Ninth Street, Ste. 2200
`Minneapolis, MN 55402
`Telephone: (612) 373-0830
`Facsimile:
`(612) 373-0929
`E-mail:
`bgilbertson@greeneespel.com
`
`
`sdunlop@greeneespel.com
`
`
`kzhao@greeneespel.com
`
`Jason Bartlett (pro hac vice)
`MAURIEL KAPOUYTIAN WOODS LLP
`1517 North Point Street, #454
`San Francisco, CA 94123
`Telephone: (415) 992-3420
`Facsimile: (415) 992-3421
`E-mail:
`JBartlett@mkwllp.com
`
`
`
`

`
`U.S. Patent No. 7,280,097
`IPR2015-00729
`
`
`
`Respectfully submitted,
`
`ERISE IP, P.A.
`
`
`
`
`
`
`
`BY: /s/ Abran J. Kean
`
`
`
`Eric A. Buresh, Reg. No. 50,394
`
`Abran J. Kean, Reg. No. 58,540
`
`
`
`
`
`ATTORNEYS FOR PETITIONER
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Dated: March 25, 2016

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