throbber
UNITED STATES PATENT AND TRADEMARK OFFICE
`
`
`
`
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`
`
`
`
`ENFORA, INC., NOVATEL WIRELESS SOLUTIONS, INC., and NOVATEL
`WIRELESS, INC.
`Petitioners
`
`v.
`
`M2M SOLUTIONS LLC
`Patent Owner
`
`
`
`
`
`Case IPR2015-01670 (Patent No. 8,648,717 B2)
`
`Case IPR2015-01672 (Patent No. 8,648,717 B2)
`
`
`
`
`
`RESPONSE TO THE BOARD’S DECEMBER 15, 2015 ORDER
`
`
`
`
`
`
`
`

`
`
`
`I.
`
`INTRODUCTION
`The Board’s Question: In Paper No. 9, the Board requested the Parties’
`
`positions as to whether the challenged claims’ “processing module” limitation
`
`“should be interpreted as a means-plus-function limitation” (herein “MPFL”) and
`
`“if so, how the limitation should be interpreted.” Paper No. 9 at 2.
`
`Petitioners’ Answer: Under the Broadest Reasonable Interpretation (“BRI”)
`
`standard, the limitation need not be interpreted as a MPFL. Moreover, even if it
`
`were interpreted as a MPFL, the underlying structure can be considered to be a
`
`general purpose computer that can perform the claimed authentication, which has
`
`no practical effect on the invalidity analyses of the Petitions.
`
`II. A DISTRICT COURT HAS FOUND THAT THE IDENTIFIED
`LIMITATION IS NOT SUBJECT TO SECTION 112(6), BOTH
`BEFORE AND AFTER WILLIAMSON
`A. The Williamson Standard
`When claims are asserted in district court, claim construction is governed by
`
`the standard set forth in Phillips v. AWH Corp., 415 F.3d 1303 (Fed. Cir. 2005).
`
`Under the Phillips rubric, the Federal Circuit “has long recognized the importance
`
`of the presence or absence of the word ‘means.’” Williamson v. Citrix Online,
`
`LLC, 792 F.3d 1339, 1348 (Fed. Cir. 2015). Where the limitation does not include
`
`“means,” there is a presumption that § 112, ¶ 6 does not apply, which can only be
`
`overcome “if the challenger demonstrates that the claim term fails to ‘recite
`
`sufficiently definite structure’ or else recites ‘function without reciting sufficient
`1
`IPR2015-01670 (8,648,717 B2)
`Response To Board’s
`IPR2015-01672 (8,648,717 B2)
`December 15, 2015 Order
`
`
`

`
`
`
`structure for performing that function.’” Id. (quoting Watts v. XL Sys., Inc., 232
`
`F.3d 877, 880 (Fed. Cir. 2000)). The essential inquiry is “whether the words of the
`
`claim are understood by persons of ordinary skill in the art to have a sufficiently
`
`definite meaning as the name for structure.” Id. (citing Greenberg v. Ethicon
`
`Endo-Surgery, Inc., 91 F.3d 1580, 1583 (Fed. Cir. 1996)).
`
`B.
`
`The District of Delaware Has Found That The “Processing
`Module” Limitation is Not a MPFL
`
`As discussed in Section II(B)(2) of the Petitions, M2M has brought actions
`
`based on two of the ’717 Patent’s ancestors, the ’197 Patent (Ex. 1008)1 and the
`
`’010 Patent (Ex. 1010). The “processing module” limitation is found (with some
`
`variation in language) in the asserted claims of each patent, and similar terms used
`
`within the same patent family should be similarly construed. See In re Rambus
`
`Inc., 694 F.3d 42, 48 (Fed. Cir. 2012).
`
`In these district court actions, Defendants proposed that the “processing
`
`module” limitations were MPFLs under the Phillips standard. Ex. 1022, p. 68.2
`
`The Court disagreed, construing those limitations as “components or units of a
`
`computer program” (Ex. 1023, p. 12) and citing a number of district court opinions
`
`finding “module” to be sufficient structure to avoid § 112, ¶ 6. Id. at 13.
`
`
`1 Cites to “Ex.” are to Exhibits in both IPR proceedings unless otherwise indicated.
`
`2 The matters identified in Section II(B)(1) of the Petitions have been stayed.
`
`IPR2015-01670 (8,648,717 B2)
`IPR2015-01672 (8,648,717 B2)
`
`
`2
`
`Response To Board’s
`December 15, 2015 Order
`
`

`
`
`
`Defendants sought reconsideration in view of Williamson, arguing that
`
`“module” was a well-known substitute for “means” and the limitation as a whole
`
`was consistent with traditional MFPLs.3 The Court affirmed its construction.4
`
`Exs. 1038 (670) and 1037 (672) at pp. 2 and 5-9.
`
`As part of the determination of whether the limitation has “sufficiently
`
`definite meaning as the name for structure” (Williamson 792 F.3d at 1348), the
`
`Court first cited the Federal Circuit’s instruction that, in computer implemented
`
`inventions, “‘[s]tructure may [] be provided by describing the claim limitation's
`
`operation .... [which] is more than just its function; it is how the function is
`
`achieved in the context of the invention.” Exs. 1038 (670) and 1037 (672) at p. 6
`
`(citing Apple Inc. v. Motorola, Inc., 757 F.3d 1286, 1299 (Fed. Cir. 2014)).
`
`While the Court noted that the “processing module” limitation itself might
`
`not provide the requisite structure, the remaining claim limitations did describe a
`
`particular authentication algorithm with sufficient detail. Exs. 1038 (070) and
`
`1037 (072) at p. 7. Specifically, the Court found that the “‘processing module’
`
`3 In the 670 and 672 IPR proceedings, Defendants’ Motion for Reconsideration is
`
`Exs. 1035 and 1034, respectively; M2M’s Opposition is Exs. 1036 and 1035,
`
`respectively; and Defendants’ Reply is Exs. 1037 and 1036, respectively.
`
`4 In the 670 and 672 IPR proceedings, the Court’s Order is Exs. 1038 and 1037,
`
`respectively.
`
`IPR2015-01670 (8,648,717 B2)
`IPR2015-01672 (8,648,717 B2)
`
`
`3
`
`Response To Board’s
`December 15, 2015 Order
`
`

`
`
`
`limitation expressly explains how this authenticating function is to be performed
`
`… [i.e.,] ‘by determining if the at least one transmission contains the coded
`
`number.’” Id. at 8. The Court seemed particularly convinced in this regard by
`
`M2M’s expert declaration that “the entire claim limitation recites sufficient
`
`structure for a person of skill in the art to be ‘able to write a software program for
`
`implementing such an algorithm for use in a wireless data module ...’” and also
`
`noted that Defendants presented no contrary expert testimony. Id. at 7-8. No such
`
`expert testimony is in the record here, either.
`
`Thus, the Court concluded that § 112 ¶6 does not apply. Id. at 9.
`
`III. THE LIMITATION IS NOT A MPFL UNDER MPEP § 2181
`In addition to the analysis under Williamson and Phillips set forth above,
`
`MPEP § 2181(I) specifies a particular MPFL analysis using the BRI standard.
`
`First, one looks at whether “means” or an equivalent “nonce term” is used. MPEP
`
`§ 2181(I)(A). Here, “means” is not used, and “processing module” is not one of
`
`the “nonce terms” listed in MPEP § 2181(I)(A). Second, one looks to see if the
`
`limitation recites “the function it performs as opposed to the specific structure,
`
`material, or acts that perform the function.” MPEP § 2181(I)(B). As discussed
`
`above, the Court found that “by determining if at least one transmission contains a
`
`coded number” provides sufficient computational structure. Exs. 1038 (670) and
`
`1037 (672) at p. 8. Third, if the limitation is generic and functional, one confirms
`
`IPR2015-01670 (8,648,717 B2)
`IPR2015-01672 (8,648,717 B2)
`
`
`4
`
`Response To Board’s
`December 15, 2015 Order
`
`

`
`
`
`that it is not “modified by sufficiently definite structure ...” MPEP § 2181(I)(C).
`
`Here, this third step is unnecessary in view of the result of the second step.
`
`This analysis would show that the “processing module” is not a MPFL. That
`
`is confirmed by the fact that the limitation appears throughout the ‘717 Patent
`
`family, and has never been considered a MPFL. See e.g., Exs. 1003, 1007, 1009,
`
`1011, 1013, 1015, 1016, 1018, 1020, and 1021.
`
`IV. EVEN IF THE LIMITATION WERE FOUND TO BE A MPFL, IT
`WOULD HAVE NO PRACTICAL EFFECT ON THE PETITIONS
`
`The Federal Circuit has confirmed that, for computer-implemented MPFLs,
`
`the corresponding structure of the specification may be a “general purpose
`
`computer” (“GPC”) if no special algorithm is required. Apple, 757 F.3d at 1298.
`
`Here, nothing in the record shows the need for anything beyond a GPC. The parts
`
`of the references compared to the “processing module” in the Petitions also show
`
`GPCs (e.g., gateway 20 of Whitely, SMS interfaces in Ardalan, and units 16, 216
`
`of Kennedy). Thus, even if the challenged claims are limited to implementations
`
`on a GPC, the cited references still disclose such an arrangement, i.e., the Petitions
`
`would still show invalidity of the challenged claims.
`
`V. CONCLUSION
`The phrase identified by the Board need not be interpreted as a MPFL under
`
`the BRI standard and, even if it were, the underlying structure can be considered to
`
`be a general purpose computer, which has no practical effect on the Petitions.
`
`IPR2015-01670 (8,648,717 B2)
`IPR2015-01672 (8,648,717 B2)
`
`
`5
`
`Response To Board’s
`December 15, 2015 Order
`
`

`
`Respectfully submitted,
`/Christopher W. Kennerly/
`Christopher W. Kennerly (Reg. No. 40,675)
`Paul Hastings LLP
`chriskennerly@paulhastings.com
`1117 S. California Avenue
`Palo Alto, California 94304
`Phone: 1.650.320.1800
`Fax: 1.650.320.1900
`
`Naveen Modi (Reg. No. 46,224)
`Timothy P. Cremen (Reg. No. 50,855)
`Paul Hastings LLP
`naveenmodi@paulhastings.com
`timothycremen@paulhastings.com
`875 15th Street, N.W.
`Washington, DC 20005
`Phone: 1.202.551.1700
`Fax: 1.202.551.1705
`
`Counsel for Enfora, Inc., Novatel Wireless
`Solutions, Inc., and Novatel Wireless, Inc.
`
`
`
`
`
`
`Dated: January 6, 2016
`
`
`
`IPR2015-01670 (8,648,717 B2)
`IPR2015-01672 (8,648,717 B2)
`
`
`6
`
`Response To Board’s
`December 15, 2015 Order
`
`

`
`
`
`CERTIFICATE OF SERVICE
`
`I hereby certify that on this 6th day of January 2016, a copy of the foregoing
`
`Response to the Board’s December 15, 2015 Order was served by e-mail on the
`
`following counsel of record for Patent Owner, M2M Solutions Inc.:
`
`Jeffrey N. Costakos - jcostakos@foley.com
`
`Michelle A. Moran - mmoran@foley.com
`
`
`
`
`
`Dated: January 6, 2016
`
`
`
`
`
`By:
`
`
`
`/Christopher W. Kennerly/
`Christopher W. Kennerly
`Reg. No. 40,675
`
`
`
`Counsel for Petitioner
`
`
`
`IPR2015-01670 (8,648,717 B2)
`IPR2015-01672 (8,648,717 B2)
`
`
`7
`
`Response To Board’s
`December 15, 2015 Order

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