throbber
U.S. Patent No. 8,894,066
`Notice of Identification of Improper New Material
`
`
`
`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`____________
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`____________
`
`RUBICON COMMUNICATIONS, LP
`Petitioner,
`
`v.
`
`LEGO A/S
`Patent Owner.
`____________
`
`Case IPR2016-01187
`Patent 8,894,066
`
`NOTICE OF IDENTIFICATION OF
`
`IMPROPER NEW MATERIAL
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`

`

`37 C.F.R. § 42.23(b) limits a reply to “only respond to arguments raised in
`
`the corresponding opposition . . . .” “‘Respond’ in the context of 37 C.F.R.
`
`§ 42.23(b) does not mean embark in a new direction with a new approach as
`
`compared to the position originally taken in the Petition.” Duk San Neolux Co. v.
`
`Idemitsu Kosan Co., Case IPR2016-00148, slip op. at 20 (PTAB March 29, 2017)
`
`(Paper 35). The Board has emphasized that it “will not attempt to sort proper from
`
`improper portions of the reply. Examples of indications that a new issue has been
`
`raised in a reply include new evidence necessary to make out a prima facie case for
`
`the . . . unpatentability of an original . . . claim, and new evidence that could have
`
`been presented in a prior filing.” Office Patent Trial Practice Guide, 77 Fed. Reg.
`
`48,756, 48,767 (Aug. 14, 2012). See also Intelligent Bio-Systems, Inc. v. Illumina
`
`Cambridge, Ltd., 821 F.3d 1359, 1369 (Fed. Cir. 2016) (“Unlike district court
`
`litigation . . . the expedited nature of IPRs bring with it an obligation for petitioners
`
`to make their case in their petition to institute.”); Wasica Fin. GmbH v. Cont'l
`
`Auto. Sys., 853 F.3d 1272, 1286 (Fed. Cir. 2017) (“Rather than explaining how its
`
`original petition was correct, [petitioner’s] subsequent arguments amount to an
`
`entirely new theory of prima facie obviousness absent from the petition.”).
`
`Patent Owner identifies the following new arguments and evidence in
`
`Petitioner’s Reply (Paper 72):
`
`
`
`
`
`.
`
`
`
`
`
`

`

`•
`
`Petitioner raises new arguments regarding contextual or “inherent” features
`
`or requirements of the cited references. See, e.g., Reply at 7–8 (casing), 9–10
`
`(casing), 15–16 (hand grip section), 23–24 (exterior shell), 28–29 (tactile
`
`manipulation). Petitioner did not make arguments based on context or inherency in
`
`the Petition. Petitioner relies on new evidence not cited or discussed in the
`
`Petition, offered by way of Kesan Decl. (Ex. 1036), to raise these new arguments.
`
`See Kesan Decl. ¶¶ 43–44, 57–58, 71–72, 78; see also Ex. 1044.
`
`•
`
`Petitioner raises new arguments regarding “predictable results” of
`
`combining Philo, Building Robots, and a cellular telephone. Compare Reply at 19,
`
`with Petition at 31. Petitioner relies on the following evidence not cited or
`
`discussed in the Petition. See Kesan Decl. ¶¶ 65, 67.
`
`•
`
`Petitioner raises new arguments regarding the “premise” of the ’066 Patent
`
`and Claim 7 and the role of a cellular telephone. Compare Reply at 18–19, with
`
`Petition at 31. Petitioner relies on the following evidence not cited or discussed in
`
`the Petition. See Kesan Decl. ¶¶ 61–65; Ex. 1041; Ex. 1042; Ex. 1043.
`
`•
`
`Petitioner raises new arguments regarding what elements in Philo are
`
`“configured to conformably fit around a portion of a controller.” Compare Reply
`
`at 10–11, with Petition at 8–9, 26. Petitioner relies on the following evidence not
`
`cited or discussed in the Petition: Ex. 1017 at 12–13; Kesan Decl. ¶¶ 43–47.
`
`•
`
`
`
`.
`
`Petitioner raises new arguments regarding “changes in response to the user’s
`
`
`
`
`
`

`

`keypress to select a difficulty level.” Compare Reply at 13–14, with Petition at
`
`25–26. Petitioner relies on the following evidence not cited or discussed in the
`
`Petition: Ex. 1017 at 12–13; Kesan Decl. ¶ 53.
`
`•
`
`Petitioner raises new arguments regarding Claim 5 and “hand grip section.”
`
`Compare Reply at 15–16, with Petition at 29. Petitioner relies on the following
`
`evidence not cited or discussed in the Petition. See Kesan Decl. ¶¶ 56–58.
`
`•
`
`Petitioner raises new arguments regarding “tactile manipulation.” Compare
`
`Reply at 27–29, with Petition at 43. Petitioner relies on paragraph [0019] and
`
`FIGs. 1 and 2 of Anderson, not cited or discussed in the Petition with respect to
`
`Claim 4. See also Kesan Decl. ¶ 78.
`
`•
`
`Petitioner raises new arguments regarding the structural relationship
`
`between the putative “controller” and “casing” in Anderson. Compare Reply at
`
`22–26, with Petition at 40. Petitioner relies on FIGs. 4 and 6 of Anderson,
`
`previously not discussed in the Petition. See also Kesan Decl. ¶¶ 70–73, 75–76.
`
`•
`
`Petitioner raises new arguments regarding construction of terms not
`
`discussed in the Petition, including at least “a portion” and “tactile.” See Reply at
`
`12, 14, 26. Petitioner relies on the following evidence not cited or discussed in the
`
`Petition. See Kesan Decl. ¶¶ 35–37, 47, 55, 77; Ex. 1038; Ex. 1039; Ex. 1040.
`
` Respectfully submitted,
`
`Dated: September 22, 2017
`
`/Andrew M. Riddles/
`
` Andrew M. Riddles (Reg. No. 31,657)
`
`
`
`.
`
`
`
`
`
`

`

`CERTIFICATE OF SERVICE
`
`
`
`Pursuant to 37 C.F.R. § 42.6(e), the undersigned certifies that on September
`
`22, 2017, a true and correct copy of the foregoing, via UPS Overnight, was served
`
`on the following counsel of record:
`
`
`
`
`Anthony M. Petro
`Dean M. Munyon
`Ryan T. Beard
`Geoffrey W. Heaven
`1120 S. Capital of Texas Hwy.
`Building 2, Suite 300
`Austin, Texas 78746
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`/ Andrew M. Riddles /
`
`
`
`
`Andrew M. Riddles
`Registration No. 31,657
`ariddles@daypitney.com
`
`Elizabeth A. Alquist
`Admitted Pro Hac Vice
`eaalquist@daypitney.com
`
`Day Pitney LLP
`7 Times Square
`New York, NY 10036
`Tel: (212) 297-5855
`Fax: (203) 202-3896
`Counsel for Patent Owner
`
`
`
`.
`
`
`
`
`
`

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