throbber
IN THE UNITED STATES PATENT AND TRADEMARK OFFICE
`
`
`
`In the Inter Partes Review of:
`
`U.S. Patent No. RE40,520
`Filed: June 14, 2005
`Issued: September 23, 2008
`Inventor(s): Doktor, Karol
`Assignee: Financial Systems
`Technology (Intellectual Property) Pty.
`Ltd.
`Title: EASILY EXPANDABLE DATA
`PROCESSING SYSTEM AND
`METHOD
`Mail Stop Inter Partes Review
`Commissions for Patents
`P.O. Box 1450
`Alexandria, VA 22313-1450
`
`
`Trial Number: To Be Assigned
`
`
`Attorney Docket No:
`
`
`
`Panel: To Be Assigned
`
`
`
`SUBMISSION PURSUANT TO 35 U.S.C. § 301 AND 37 C.F.R. § 1.501 IN
`SUPPORT OF PETITION FOR INTER PARTES REVIEW OF
`U.S. PATENT NO. RE40,520
`
`
`
`

`

`Submission Pursuant to 35 U.S.C. § 301 and 37 C.F.R. § 1.501 in Support of
`Petition for Inter Partes Review of U.S. Patent No. RE40,520
`
`Pursuant to 35 U.S.C. § 301 and 37 C.F.R. § 1.501, International Business
`
`Machines Corporation (“IBM”) offers this Submission Pursuant to 35 U.S.C. § 301
`
`and 37 C.F.R. § 1.501 in Support of Petition for Inter Partes Review of U.S. Patent
`
`No. RE40,520 (“Submission”) regarding: (1) prior art that bears on the
`
`patentability of claims 10–13 and 15–16 of U.S. Patent No. RE40,520 (“the ’520
`
`Patent”); and (2) statements that the patent owner, Financial Systems Technology
`
`(Intellectual Property) Pty. Ltd. (“FST”) has filed with this Office and in Federal
`
`court proceedings regarding the scope of claims 10–13 and 15–16 of the ’520
`
`Patent. IBM files this Submission in connection with, and as Exhibit 1003 to, its
`
`Petition for Inter Partes Review Under 37 C.F.R. § 42.100 of U.S. Patent No.
`
`RE40,520 (“Petition”).
`
`I.
`
`PRIOR ART BEARING ON THE PATENTABILITY OF CLAIMS 10-
`13 AND 15-16 OF U.S. PATENT NO. RE40,520
`
`Pursuant to 35 U.S.C. § 301(a)(1) and 37 C.F.R. § 1.501(a)(1), IBM
`
`identifies the following prior art that it believes bears on the patentability of claims
`
`10–13 and 15–16 of the ’520 Patent:
`
`• James P. Davis, et al., EDICT - An Enhanced Relational Data Dictionary:
`
`Architecture and Example (“Davis”) (Ex. 1006)1
`
`
`1 All exhibit numbers given herein reference the Appendix of Exhibits attached to
`the Petition.
`
`
`
`1
`
`

`

`Submission Pursuant to 35 U.S.C. § 301 and 37 C.F.R. § 1.501 in Support of
`Petition for Inter Partes Review of U.S. Patent No. RE40,520
`• Stephanie Cammarata, et al., Extending a Relational Database with Deferred
`
`Referential Integrity Checking and Intelligent Joins (“Cammarata”) (Ex.
`
`1007)
`
`• U.S. Patent No. 4,868,733 to Fujisawa, et al. (“Fujisawa”) (Ex. 1008)
`
`• U.S. Patent No. 5,206,951 to Khoyi, et al. (“Khoyi”) (Ex. 1009)
`
`As required by 37 C.F.R. § 1.501(b)(1), the pertinence of this prior art to
`
`claims 10–13 and 15–16 of the ’520 Patent is explained in Section V of the
`
`Petition, and in particular, the manner of applying this prior art to claims 10–13
`
`and 15–16 of the ’520 Patent may be found in the claim-by-claim analysis of
`
`Section V.E of the Petition.
`
`II.
`
`STATEMENTS ABOUT THE SCOPE OF CLAIMS 10–13 AND 15–16
`OF U.S. PATENT NO. RE40,520 FILED IN A PROCEEDING
`BEFORE A FEDERAL COURT OR THE OFFICE
`
`Pursuant to 35 U.S.C. § 301(a)(2) and 37 C.F.R. § 1.501(a)(2), IBM
`
`identifies the following statements made by FST in which FST took a position on
`
`the scope of claims 10–13 and 15–16 of the ’520 Patent and that were filed in a
`
`proceeding before a Federal court or this Office.
`
`FST v. IBM Claim Constructions and Infringement Contentions
`
`FST directly took a position on the scope of claims 10–13 and 15–16 of the
`
`’520 Patent when it made statements in its currently pending litigation against IBM
`
`about how certain claim terms that appear in those claims should be construed.
`
`
`
`2
`
`

`

`Submission Pursuant to 35 U.S.C. § 301 and 37 C.F.R. § 1.501 in Support of
`Petition for Inter Partes Review of U.S. Patent No. RE40,520
`
`(Ex. 1010, FST’s Local Patent Rule 4.1 Identification of Claim Terms to be
`
`Construed and Proposed Constructions.) Additionally, FST implicitly took a
`
`position on the scope of claims 10–13 and 15–16 of the ’520 Patent when it made
`
`statements about how the accused IBM products allegedly infringe those claims.
`
`(Ex. 1032, FST’s Local Patent Rule 3.1 Final Infringement Contentions for the
`
`’520 Patent.) As required by 37 C.F.R. § 1.501(a)(3), IBM identifies the
`
`following:
`
`37 C.F.R. § 1.501(a)(3)(i), Forum: FST filed these statements during the
`
`district court litigation captioned Financial Systems Technology (Intellectual
`
`Property) Pty. Ltd. and Financial Systems Technology Pty. Ltd. v. International
`
`Business Machines Corporation, Case No. 1:11-cv-08729 (U.S. District Court for
`
`the Northern District of Illinois, Eastern Division).
`
`37 C.F.R. § 1.501(a)(3)(ii), Specific Documents:
`
` FST made these
`
`statements about the scope of claims 10–13 and 15–16 of the ’520 Patent in the
`
`following documents: (1) Local Patent Rule 4.1 Identification of Claim Terms to
`
`be Construed and Proposed Constructions (Ex. 1010); and (2) FST’s Local Patent
`
`Rule 3.1 Final Infringement Contentions for the ’520 Patent (Ex. 1032).
`
`37 C.F.R. § 1.501(a)(3)(iii), How Statement is a Position on the Scope of
`
`Any Claim: In proposing how the district court should construe certain terms that
`
`appear in claims 10-13 and 15-16 of the ’520 Patent, FST was taking a direct
`
`
`
`3
`
`

`

`Submission Pursuant to 35 U.S.C. § 301 and 37 C.F.R. § 1.501 in Support of
`Petition for Inter Partes Review of U.S. Patent No. RE40,520
`
`position about the scope of those claims. (See Ex. 1010.) FST’s infringement
`
`contentions are an implicit statement about the scope of those claims. By saying
`
`that certain features or functionalities of the IBM accused products allegedly
`
`infringe a limitation of claims 10-13 and 15-16, FST is stating that the scope of
`
`that claim limitation is such that it would encompass that feature or functionality.
`
`(See Ex. 1032.)
`
`An explanation of the pertinence of these statements and how to apply them
`
`to claims 10–13 and 15–16 of the ’520 Patent, as required by 37 C.F.R.
`
`§ 1.501(b)(1), may be found in Section IV.C of the Petition.
`
`FST v. Oracle Claim Constructions
`
`FST also took a position on the scope of claims 10–13 and 15–16 of the ’520
`
`Patent when it made statements in a prior district court proceeding about how
`
`certain claim terms that appear in those claims should be construed. (Ex. 1011,
`
`Local Patent Rule 4.3 Joint Claim Construction and Pre-Hearing Statement.) As
`
`required by 37 C.F.R. § 1.501(a)(3), IBM identifies the following:
`
`37 C.F.R. § 1.501(a)(3)(i), Forum: FST filed these statements during the
`
`district court litigation captioned Financial Systems Technology (Intellectual
`
`Property) Pty. Ltd. and Financial Systems Technology Pty. Ltd. v. Oracle
`
`Corporation, Case No. 2:08-cv-371 (U.S. District Court for the Eastern District of
`
`Texas, Marshall Division).
`
`
`
`4
`
`

`

`Submission Pursuant to 35 U.S.C. § 301 and 37 C.F.R. § 1.501 in Support of
`Petition for Inter Partes Review of U.S. Patent No. RE40,520
`
`37 C.F.R. § 1.501(a)(3)(ii), Specific Documents:
`
` FST made these
`
`statements proposing construction for certain terms of claims 10–13 and 15–16 of
`
`the ’520 Patent in the following documents2: (1) Local Patent Rule 4.3 Joint Claim
`
`Construction and Pre-Hearing Statement (Ex. 1011, Ex. A at 1–7); (2) FST
`
`Opening Claim Construction Brief (Ex. 1028 at 1–2, 4–16); (3) FST’s Reply in
`
`Support of its Opening Claim Construction Brief (Ex. 1029 at 1–8); and (4)
`
`Transcript of the October 7, 2010 Claim Construction Hearing (Ex. 1030).
`
`37 C.F.R. § 1.501(a)(3)(iii), How Statement is a Position on the Scope of
`
`Any Claim: In proposing how the district court should construe certain terms that
`
`appear in claims 10–13 and 15–16 of the ’520 Patent, FST was taking a direct
`
`position about the scope of those claims.
`
`An explanation of the pertinence of these statements and how to apply them
`
`to claims 10–13 and 15–16 of the ’520 Patent, as required by 37 C.F.R.
`
`§ 1.501(b)(1), may be found in Section IV.C of the Petition.
`
`Reexamination Proceedings
`
`FST also took a position on the scope of claims 10–13 and 15–16 of the ’520
`
`Patent when it made statements to the Office about the scope of the term “entity
`
`
`2 While FST may have filed additional documents or evidence in which such
`statements were addressed, IBM is not aware of any such documents or
`evidence, as it was not a party to that district court proceeding. IBM presents
`here the publicly available documents that include these statements.
`
`
`
`5
`
`

`

`Submission Pursuant to 35 U.S.C. § 301 and 37 C.F.R. § 1.501 in Support of
`Petition for Inter Partes Review of U.S. Patent No. RE40,520
`
`type record.” As required by 37 C.F.R. § 1.501(a)(3), IBM identifies the
`
`following:
`
`37 C.F.R. § 1.501(a)(3)(i), Forum: FST filed these statements during
`
`reexamination proceedings before the Office in response to an Office Action dated
`
`March 5, 2009.
`
`37 C.F.R. § 1.501(a)(3)(ii), Specific Documents:
`
` FST made these
`
`statements about the scope of the term “abbreviated results” in a Response dated
`
`June 4, 2009. (Ex. 1025.)
`
`37 C.F.R. § 1.501(a)(3)(iii), How Statement is a Position on the Scope of
`
`Any Claim: In stating that one of ordinary skill in the art would understand that
`
`“entity type” and “entity instance table” were two separate attributes, FST was
`
`taking a direct position about the scope of the term “entity instance record” in
`
`claims 10–13 and 15–16 of the ’520 Patent.
`
`An explanation of the pertinence of this statement and how to apply it to
`
`claims 10–13 and 15–16 of the ’520 Patent, as required by 37 C.F.R. § 1.501(b)(1),
`
`may be found in Section IV.C of the Petition.
`
`
`
`6
`
`

`

`Submission Pursuant to 35 U.S.C. § 301 and 37 C.F.R. § 1.501 in Support of
`Petition for Inter Partes Review of U.S. Patent No. RE40,520
`
`
`
`Date: December 12, 2012
`
`
`
`
`
`
`
`
`
`Respectfully submitted,
`
` /s/ Joel R. Merkin
`Kenneth R. Adamo (Reg. No. 27299)
`Joel R. Merkin (Reg. No. 58600)
`KIRKLAND & ELLIS LLP
`300 North LaSalle Street
`Chicago, Illinois 60654
`P: 312.862.2000; F: 312.862.2200
`kenneth.adamo@kirkland.com
`joel.merkin@kirkland.com
`Attorneys For Petitioners
`
`7
`
`

`

`Submission Pursuant to 35 U.S.C. § 301 and 37 C.F.R. § 1.501 in Support of
`Petition for Inter Partes Review of U.S. Patent No. RE40,520
`
`CERTIFICATE OF SERVICE
`
`The undersigned hereby certifies that a copy of the foregoing Submission
`
`Pursuant to 35 U.S.C. § 301 and 37 C.F.R. § 1.501 in Support of Petition for Inter
`
`Partes Review of U.S. Patent No. RE40,520 was served on December 12, 2012 via
`
`FedEx delivery directed to the attorney of record for the patent at the following
`
`address:
`
`Scott A. McKeown
`OBLON, SPIVAK, MCCLELLAND MAIER & NEUSTADT LLP
`1940 Duke Street
`Alexandria, VA 22314
`
` copy was also served via messenger delivery on:
`
` A
`
`Robert A. Conley
`NIRO, HALLER & NIRO, LTD.
`181 West Madison Street, Suite 4600
`Chicago, IL 60602-4515
`
`
`
`
`
`
` /s/ Joel R. Merkin
`Joel R. Merkin
`
`
`
`
`
`
`
`

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