throbber
FINANCIAL SYSTEMS TECHNOLOGY
`(INTELLECTUAL PROPERTY) PTY. LTD.
`and FINANCIAL SYSTEMS TECHNOLOGY
`PTY. LTD.,
`
`
`
`
`
`CDW LLC and INTERNATIONAL
`BUSINESS MACHINES CORPORATION,
`
`
`
`
`
`
`v.
`
`
`
`
`
`
`
`
`
`
`
`Plaintiffs,
`
`Defendants.
`
`IN THE UNITED STATES DISTRICT COURT
`FOR THE NORTHERN DISTRICT OF ILLINOIS
`EASTERN DIVISION
`
`
`Civil Action No. 1:11-cv-08729
`
`Hon. Virginia M. Kendall
`Mag. Judge Sheila M. Finnegan
`
`
`
`
`
`FINANCIAL SYSTEMS TECHNOLOGY (INTELLECTUAL PROPERTY)
`PTY. LTD. AND FINANCIAL SYSTEMS TECHNOLOGY PTY. LTD.'S
`LOCAL PATENT RULE 4.1 IDENTIFICATION OF CLAIM
`TERMS TO BE CONSTRUED AND PROPOSED CONSTRUCTIONS
`
`Pursuant to Local Patent Rule 4.1, plaintiffs Financial Systems Technology (Intellectual
`
`Property) Pty. Ltd. and Financial Systems Technology Pty. Ltd. (collectively, "FST") hereby
`
`provide their identification of claim terms to be construed by the Court along with proposed
`
`constructions for such terms as they appear in the asserted claims of United States Patent
`
`Nos. RE40,520 and RE40,526 ("the patents-in-suit").
`
`FST's proposed constructions are provided in Exhibit A attached hereto. To the extent
`
`that FST does not provide a proposed construction of any term or phrase appearing in any
`
`asserted claim of the patents-in-suit, FST relies on the plain and ordinary meaning of such term
`
`or phrase for the purposes of claim construction. FST specifically reserves the right to provide a
`
`proposed construction or identification of a term's plain and ordinary meaning in response to
`
`proposed constructions offered by IBM. FST also reserves the right to offer additional,
`
`alternative or revised claim constructions based upon IBM's identification of claim terms for
`
`construction and proposed claim constructions.
`
`
`
`

`

`
`
`
`
`
`
`
`
`
`
`
`
`
`Respectfully submitted,
`
`/s/ Robert A. Conley
`Raymond P. Niro
`Dean D. Niro
`Patrick F. Solon
`Dina M. Hayes
`Robert A. Conley
`Oliver D. Yang
`NIRO, HALLER & NIRO
`181 W. Madison, Suite 4600
`Chicago, IL 60602
`(312) 236-0733
`Fax: (312) 236-3137
`rniro@nshn.com; dniro@nshn.com
`solon@nshn.com; hayes@nshn.com;
`rconley@nshn.com; oyang@nshn.com
`
`Robert S. Bramson (pro hac vice)
`BRAMSON & PRESSMAN
`1100 E. Hector Street , Suite 410
`Conshohocken, PA 19428
`(610) 260-4444
`Fax: (610) 260-4445
`rbramson@b-p.com
`
`Attorneys for Financial Systems Technology
`(Intellectual Property) Pty. Ltd. and Financial
`Systems Technology Pty. Ltd.
`
`- 2 -
`
`
`
`

`

`
`
`CERTIFICATE OF SERVICE
`
`The undersigned hereby certifies that on November 30, 2012 the foregoing
`
`FINANCIAL SYSTEMS TECHNOLOGY (INTELLECTUAL PROPERTY)
`PTY. LTD. AND FINANCIAL SYSTEMS TECHNOLOGY PTY. LTD.'S
`LOCAL PATENT RULE 4.1 IDENTIFICATION OF CLAIM
`TERMS TO BE CONSTRUED AND PROPOSED CONSTRUCTIONS
`
`
`was served upon the following counsel of record via electronic transmission.
`
`Kenneth R. Adamo
`kradamo@kirkland.com
`William E. Devitt
`wdevitt@kirkland.com
`Meredith Zinanni
`meredith.zinanni@kirkland.com
`Joel R. Merkin
`joel.merkin@kirkland.com
`Eugene Goryunov
`egoryunov@kirkland.com
`Kirkland & Ellis LLP
`300 North LaSalle Street
`Chicago, IL 60654
`
`Attorneys for International Business Machines Corporation
`
`
`
`
`
`/s/ Robert A. Conley
`Attorneys for Financial Systems Technology
`(Intellectual Property) Pty. Ltd. and Financial
`Systems Technology Pty. Ltd.
`NIRO, HALLER & NIRO
`
`
`
`
`
`
`
`

`

`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`EXHIBIT A
`
`EXHIBIT A
`
`

`

`No. Term
`1
`table
`
`record
`entity
`entity definition table
`
`entity type
`
`entity type record
`
`entity instance table
`entity instance record
`relation
`relation definition table
`
`FST'S PROPOSED CLAIM CONSTRUCTIONS
`
`FST's Proposed Construction
`permanent structure of a relational database which stores queryable and updatable data
`in rows and columns
`set of data stored in a single row of a table
`anything about which information can be stored in a database record
`relational database table that defines one or more entity types and stores one or more
`entity type records
`identification of a class of entity data, said identification being uniquely defined in the
`entity definition table
`record in an entity definition table, said record containing, as two separate attributes, an
`entity type and a table identifier of an entity instance table
`relational database table that stores one or more entity instance records
`record in an entity instance table, said record constituting an instance of an entity type
`logical link between entities
`relational database table that defines one or more relation types and stores one or more
`relation type records
`identification of a class of relation data, said identification being uniquely defined in the
`relation definition table
`record in a relation definition table, said record containing, as two separate attributes, a
`relation type and a table identifier of a relation instance table
`relational database table that stores one or more relation instance records
`record in a relation instance table, said record constituting an instance of a relation type,
`said instance containing, as two separate attributes, an identifier of a first entity and an
`identifier of a second entity, and where said first and second entities are stored in tables
`separate from the relation instance table
`record that describes a search path, said description including a relation
`search path record
`relational database table that stores search path records
`inquiry definition table means
`abbreviated results gathering means memory area that gathers data from one or more relational database tables and stores a
`subset of attributes from one or more entities, said entity attributes being obtained by
`execution of a search path record
`
`relation type
`
`relation type record
`
`relation instance table
`relation instance record
`
`2
`3
`4
`
`5
`
`6
`
`7
`8
`9
`10
`
`11
`
`12
`
`13
`14
`
`15
`16
`17
`
`
`
`

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