throbber
Google Inc. v. Fujinomaki
`Patent Owner’s Presentation
`IPR2016-01522
`(joined with IPR 2017-01017)
`
`November 28, 2017
`
`GOOGLE INC., ET AL. v. RYUJIN FUJINOMAKI
`FUJINOMAKI EX2005 – 1
`Patent Owner’s Demonstrative Slides
`IPR2016-01522
`
`

`

`Claim Construction
`The ‘8923 Patent
`
`IDCTU
`
`’493 Patent Claim 1
`
`UPCU
`
`Transmitter for transmitting an ID code signal at a constant
`
`Transmitter
`
`for
`
`transmitting the confirmation signal at a
`
`power level to the UPCU
`
`constant power level to the IDCTU
`
`Receiver for receiving a confirmation signal from the UPCU
`
`Receiver for receiving the ID code signal from the IDCTU
`
`Activating an alarm mechanism when the strength of the
`
`While the strength of the ID code signal received from the IDCTU
`
`confirmation signal received from the UPCU is below a
`
`is at or above a predetermined value: maintaining the electronic
`
`predetermined value
`
`device (cell phone) in an operational state; and
`
`When the signal strength of the ID code signal
`
`is below a
`
`predetermined value: disabling the electronic device (cellular
`
`phone)
`
`PO Resp., Paper 20 at 24-25
`
`2
`
`GOOGLE INC., ET AL. v. RYUJIN FUJINOMAKI
`FUJINOMAKI EX2005 – 2
`Patent Owner’s Demonstrative Slides
`IPR2016-01522
`
`

`

`Claim Construction
`The ‘8923 Patent
`
`Petitioner’s Reply, Paper 21 at 2
`
`3
`
`GOOGLE INC., ET AL. v. RYUJIN FUJINOMAKI
`FUJINOMAKI EX2005 – 3
`Patent Owner’s Demonstrative Slides
`IPR2016-01522
`
`

`

`Claim Construction
`The ‘8923 Patent
`
`Ex. 1001, 493 Patent at 5:58-67
`
`4
`
`GOOGLE INC., ET AL. v. RYUJIN FUJINOMAKI
`FUJINOMAKI EX2005 – 4
`Patent Owner’s Demonstrative Slides
`IPR2016-01522
`
`

`

`Claim Construction
`The ‘8923 Patent
`
`Ex. 1001, 493 Patent at 6:58-7:20
`
`5
`
`GOOGLE INC., ET AL. v. RYUJIN FUJINOMAKI
`FUJINOMAKI EX2005 – 5
`Patent Owner’s Demonstrative Slides
`IPR2016-01522
`
`

`

`Claim Construction
`The ‘8923 Patent
`
`Identification Code Signal
`
`a signal that contains information representing the
`1) the phone number of the electronic device, 2) an
`ID number or signal indicative of other information
`about the owner of the electronic device, or 3) any
`number or code peculiar to the electronic device,
`and that is transmitted regularly and periodically
`
`PO Resp., Paper 20 at 12
`
`6
`
`GOOGLE INC., ET AL. v. RYUJIN FUJINOMAKI
`FUJINOMAKI EX2005 – 6
`Patent Owner’s Demonstrative Slides
`IPR2016-01522
`
`

`

`Claim Construction
`The ‘8923 Patent
`
`Confirmation Signal
`
`a signal that contains information representing the
`1) the phone number of the electronic device, 2) an
`ID number or signal indicative of other information
`about the owner of the electronic device, or 3) any
`number or code peculiar to the electronic device,
`and that is transmitted regularly and periodically
`
`PO Resp., Paper 20 at 12
`
`7
`
`GOOGLE INC., ET AL. v. RYUJIN FUJINOMAKI
`FUJINOMAKI EX2005 – 7
`Patent Owner’s Demonstrative Slides
`IPR2016-01522
`
`

`

`Yamamoto
`The ‘8923 Patent
`
`Petitioner’s Reply, Paper 21 at 6 (annotated
`by Patent Owner with green highlight)
`
`8
`
`GOOGLE INC., ET AL. v. RYUJIN FUJINOMAKI
`FUJINOMAKI EX2005 – 8
`Patent Owner’s Demonstrative Slides
`IPR2016-01522
`
`

`

`Yamamoto
`The ‘8923 Patent
`
`Petitioner’s Reply, Paper 21 at 18 6 (annotated
`by Patent Owner with green highlight)
`
`9
`
`GOOGLE INC., ET AL. v. RYUJIN FUJINOMAKI
`FUJINOMAKI EX2005 – 9
`Patent Owner’s Demonstrative Slides
`IPR2016-01522
`
`

`

`Yamamoto
`The ‘8923 Patent
`
`PO Resp., Paper 20 at 38, Ex. 2004, 45:22-46:3
`
`10
`
`GOOGLE INC., ET AL. v. RYUJIN FUJINOMAKI
`FUJINOMAKI EX2005 – 10
`Patent Owner’s Demonstrative Slides
`IPR2016-01522
`
`

`

`Google Inc. v. Fujinomaki
`Patent Owner’s Presentation
`
`November 28, 2017
`
`GOOGLE INC., ET AL. v. RYUJIN FUJINOMAKI
`FUJINOMAKI EX2005 – 11
`Patent Owner’s Demonstrative Slides
`IPR2016-01522
`
`

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