throbber
IPR2018-0043
`Patent 9,454,748
`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`__________________
`
`UNIFIED PATENTS INC.
`Petitioner
`
`v.
`
`FALL LINE PATENTS, LLC
`Patent Owner
`__________________
`
`Case IPR2018-00043
`Patent 9,454,748
`__________________
`
`PATENT OWNER’S MOTION REGARDING REAL PARTY IN INTEREST
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`

`

`IPR2018-0043
`Patent 9,454,748
`THE BOARD SHOULD CONSIDER PATENT OWNER’S REAL-
`PARTY-IN-INTEREST ARGUMENTS
`
`A.
`
`Patent Owner Timely Challenged Petitioner’s Identification of the
`Real Parties in Interest
`
`Petitioner Unified Patents, Inc. is required to identify all real parties in
`
`I.
`
`
`
`interest in its petition for inter partes review. See, 35 U.S.C. § 312(a)(2). In its
`
`Preliminary Response, Patent Owner Fall Line Patents, LLC argued that Petitioner
`
`has failed to identify all real parties in interest to this IPR. Paper 5 at 28-33. Patent
`
`Owner presented evidence showing that Petitioner’s clients (also referred to as
`
`members) should be named as real parties in interest. Id. That argument and
`
`supporting evidence was rejected by the Board. Paper 6 at 10-11.
`
`From its opening brief, Patent Owner has maintained that Petitioner has not
`
`satisfied its statutory obligation to identify all real parties in interest. Patent
`
`Owner’s arguments and supporting evidence remain the same, and the Board
`
`should consider these arguments.
`
`B.
`
`Patent Owner Has Not Waived Its Challenge
`
`Patent Owner has not waived its argument that Petitioner has failed to
`
`identify all the real parties in interest to this IPR. The waiver argument appears to
`
`be based on a sentence in the Scheduling Order: “The patent owner is cautioned
`
`that any arguments for patentability not raised in the response will be deemed
`
`waived.” Paper 7 at 3 (emphasis added). That warning, however, clearly states that
`
`
`
`1
`
`

`

`IPR2018-0043
`Patent 9,454,748
`only certain arguments are waived: those pertaining to patentability. Whether
`
`Petitioner has named all real parties in interest in no way affects the patentability
`
`of the ‘748 Patent. Instead, it goes to whether Petitioner has satisfied the statutory
`
`requirements for challenging an issued patent using the inter partes review
`
`procedure. Thus, the real-party-in-interest argument cannot be waived pursuant to
`
`this clause in the scheduling order because it is not an argument for patentability.
`
`Furthermore, the Board has stated that the requirement to identify all real
`
`parties in interest cannot be waived. See, Motorola Mobility LLC v. Intellectual
`
`Ventures II LLC, IPR2014-00504, Paper 12 at 8 (PTAB Sep. 10, 2014) (“We agree
`
`with Patent Owner that identification of all real parties-in-interest is an express
`
`statutory requirement that cannot be waived.”).
`
`II.
`
`
`
`
`
`FEDERAL CIRCUIT PRECEDENT SHOWS THAT PETITIONER
`HAS FAILED TO NAME ALL REAL PARTIES IN INTEREST
`
`A. The Board Used the Wrong Standard
`After this IPR was instituted, and after Patent Owner filed its Response, the
`
`Federal Circuit held that the Board had been applying an “unduly restrictive test
`
`for determining whether a person or entity is a ‘real party in interest.’”
`
`Applications in Internet Time, LLC v. RPX Corp., 897 F.3d 1336, 1339 (Fed. Cir.
`
`2018) (“AIT”). In that case, petitioner RPX Corporation’s petition identified RPX
`
`as the sole real party in interest. Id. The patent owner in that case challenged this
`
`allegation and, after taking additional discovery, presented facts showing that a
`
`
`
`2
`
`

`

`IPR2018-0043
`Patent 9,454,748
`client of RPX should also be listed as a real party in interest. Id. The Board
`
`rejected the patent owner’s argument and instituted the IPR. Id. at 1342.
`
`On appeal, the Federal Circuit addressed whether “the Board relied on an
`
`erroneous understanding of the term ‘real party in interest’” in the context of IPR
`
`petitions. Id. at 1344. The court analyzed “the meaning of the term ‘real party in
`
`interest’ in the context of the AIA” by examining the relevant common law and
`
`applicable statutory history. Id. at 1346-1351. The Federal Circuit concluded that
`
`the real-party-in-interest analysis “demands a flexible approach that takes into
`
`account both equitable and practical considerations, with an eye toward
`
`determining whether the non-party is a clear beneficiary that has a preexisting,
`
`established relationship with the petitioner.” (emphasis added) Id. at 1351.
`
`The Federal Circuit then highlighted two facts pertaining to the petitioner: 1)
`
`“RPX, unlike a traditional trade association, is a for-profit company whose clients
`
`pay for its portfolio of ‘patent risk solutions,’” and 2) “one of its ‘strategies’ for
`
`transforming the patent market is ‘the facilitation of challenges to patent validity.”
`
`Id. at 1351. The court found that those two facts alone where sufficient to imply
`
`that the clients were clear beneficiaries with a preexisting relationship and real
`
`parties in interest. Id. at 1351-52.
`
`Those same two facts apply to Petitioner Unified Patents in this IPR. First,
`
`Petitioner is a for-profit company that collects subscription fees from its clients in
`
`
`
`3
`
`

`

`IPR2018-0043
`Patent 9,454,748
`order to “track any NPE activity and NPE risks.” Ex. 2003 at 4. Second, one of
`
`Petitioner’s strategies to deter NPE activity is via USPTO challenges, such as this
`
`IPR. Ex. 2004 at 3. Therefore. using the analytical framework set forth in AIT, it is
`
`clear that the Petitioner in this IPR is not the only real party in interest.1
`
`After the AIT case, the Federal Circuit addressed which party has the burden
`
`of persuasion in the real-party-in-interest analysis and how the Board had applied
`
`that burden. Worlds Inc. v. Bungie, Inc., 903 F.3d 1237, 1241 (Fed. Cir. 2018). In
`
`that case, the Federal Circuit first affirmed that the petitioner has the burden to
`
`show that it “complied with the statutory requirement to identify all the real parties
`
`in interest.” Id. at 1242. The court also agreed that it was practical for a petitioner’s
`
`initial identification to be “accepted unless and until disputed by a patent owner,”
`
`but did not view this as a presumption. Id. at 1243.
`
`The court then analyzed what a patent owner must do to sufficiently dispute
`
`the issue. Id. at 1244. The Board had previously explained that a patent owner must
`
`“provide[] sufficient rebuttal evidence that reasonably brings into question the
`
`
`1 The court discussed other facts pertaining to the particular relationship between
`
`RPX and its client, but did not hold that additional facts were necessary for a non-
`
`party to be a real party in interest. AIT, 897 F.3d at 1352 (“This implication
`
`becomes stronger when one considers the discovery produced in this case.”).
`
`
`
`4
`
`

`

`IPR2018-0043
`Patent 9,454,748
`accuracy of a petitioner’s identification of the real parties in interest” for the
`
`burden to remain with petitioners. Id. But the Federal Circuit “disagree[d] with the
`
`use of a presumption in this context” because by presuming that a petitioner’s
`
`identification of the real parties in interest was correct, the Board was improperly
`
`shifting the burden to patent owners. Id.
`
`Similarly, in this IPR, the Board incorrectly presumed the accuracy of
`
`Petitioner’s identification of the real parties in interest and, therefore, improperly
`
`shifted the burden of persuasion to Patent Owner. In the Institution Decision, the
`
`Board stated that “Patent Owner has not provided sufficient evidence to reasonably
`
`bring into question the accuracy of Petitioner's identification.” Paper 6 at 11. This
`
`is the same application of a presumption that was rejected in Worlds.
`
`B.
`
`Petitioner Has Failed to Satisfy the Statutory Requirements
`
`When applying the correct standard for determining the real parties in
`
`interest and keeping the burden on Petitioner, it is clear that Petitioner has not met
`
`the statutory requirement to identify all real parties in interest. Unlike other IPR
`
`petitions filed by Petitioner, and as stated in the Preliminary Response, Petitioner
`
`has provided no evidence to support its assertion that it is the only real party in
`
`interest. Paper 5 at 31-32. Petitioner has offered only a bare statement in the
`
`petition, which Patent Owner has disputed with evidence showing that Petitioner’s
`
`clients are also real parties in interest.
`
`
`
`5
`
`

`

`
`Dated: January 11, 2019
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`IPR2018-0043
`Patent 9,454,748
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Respectfully submitted,
`
`__/Michael D. Ellis/__
`Michael D. Ellis
`Reg. No. 72,628
`Counsel for Patent Owner
`
`
`
`6
`
`

`

`CERTIFICATE OF SERVICE
`
`
`
`Pursuant to 37 C.F.R. § 42.6, the undersigned certifies that on January 11,
`
`2019, the foregoing document was served via email on counsel for Petitioner:
`
`IPR2018-0043
`Patent 9,454,748
`
`HAYNES AND BOONE, LLP
`David O’Brien (David.obrien.ipr@haynesboone.com)
`Raghav Bajaj (Raghav.bajaj.ipr@haynesboone.com)
`David McCombs (David.mccombs.ipr@haynesboone.com)
`
`UNIFIED PATENTS INC.
`Jonathan Stroud (jonathan@unifiedpatents.com)
`Roshan Mansinghani (roshan@unifiedpatents.com)
`Jonathan Bowser (jbowser@unifiedpatents.com)
`
`
`__/Michael D. Ellis/___
`Michael D. Ellis
`Counsel for Patent Owner
`Reg. No. 72,628
`
`
`
`
`
`

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