IP Library Granted Patent US 6,901,352
Granted Patent B2
US 6,901,352 · App. 10/610,426 · Granted May 31, 2005

Method and apparatus for improved inspection and classification of attributes of a workpiece

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 6,901,352
App. No.
10/610,426
Granted
May 31, 2005
Kind
B2
Abstract

A generic, scalable consumer subsystem/producer subsystem interface controller for exchanging data between at least one producer subsystem configured to produce a set of services characterized in a producer generated data set, and at least on consumer subsystem configured to consume the set of services, including an object-oriented producer application program interface configured for use on a multi-threaded, client-server operating system, wherein producer routines are configured to: initialize producer server objects maid producer client objects; receive requests for data from a consumer subsystem via the producer client objects; send acknowledgments to a consumer subsystem in response to requests from the consumer subsystem via the producer server objects; send data to a consumer subsystem in response to requests from the consumer subsystem via the producer server objects; and wherein consumer routines are configured to: initialize consumer server objects and consumer client objects; send requests for data to a producer subsystem via the consumer server objects; receive acknowledgments from a producer subsystem in response to requests from the producer subsystem via the consumer client objects; and, receive data from a producer subsystem in response to requests from the producer subsystem via the consumer client objects.

Claims (27)

1. A generic, scalable consumer subsystem/producer subsystem interface controller for exchanging data between at least one producer subsystem configured to produce a set of services characterized in a producer generated data set, and at least one consumer subsystem configured to consume the set of services, comprising:

an object-oriented producer application program interface (API) configured for use on a multi-threaded, client-server operating system, comprising producer routines configured to:

initialize producer server objects and producer client objects;

receive requests for data from a consumer subsystem via said producer client objects;

send acknowledgments to a consumer subsystem in response to requests from the consumer subsystem via said producer server objects;

send data to a consumer subsystem in response to requests from the consumer subsystem via said producer server objects; and

an object-oriented consumer application program interface (API) configured for use on a multi-threaded, client-server operating system, comprising consumer routines configured to:

initialize consumer server objects and consumer client objects;

send requests for data to a producer subsystem via said consumer server objects;

receive acknowledgments from a producer subsystem in response to requests from the producer subsystem via said consumer client objects; and

receive data from a producer subsystem in response to requests from the producer subsystem via said consumer client objects.

2. The subsystem interface of claim 1 wherein at least one of the consumer subsystems comprises a consumer server having a producer subscription to data from at least one of the producer subsystems, the producer API further comprising a first producer server thread configured to first initialize a producer client object and then to reply to the producer subscription by connecting to the consumer server.

3. The subsystem interface of claim 2 wherein the producer API is further configured to generate a new producer server thread for connection to a consumer server upon connection of the first producer server thread to the consumer server.

4. The subsystem interface of claim 3 wherein:

producer server threads are listed on a subscribe table accessible by consumer servers;

each producer server thread is disconnectable from a consumer server; and

upon disconnection of a producer server thread from a consumer server, the disconnected producer server thread is removed from the subscribe table.

5. The subsystem interface of claim 2 wherein the consumer API further comprises a plurality of consumer server threads each configured to create a dedicated connection to a producer subsystem.

6. A generic, scalable method for controlling the exchange of data in a consumer/producer system between at least one producer subsystem configured to produce a set of services characterized in a producer generated data set, and at least one consumer subsystem configured to consume the set of services, comprising:

initializing producer server objects and producer client objects within an object-oriented producer application program interface (API) configured for use on a multi-threaded, client-server operating system;

receiving requests for data from a consumer subsystem via at least one of the initialized producer client objects;

sending acknowledgments to a consumer subsystem in response to requests from the consumer subsystem using at least one of the producer server objects;

sending data to a consumer subsystem in response to requests from the consumer subsystem using at least one of the producer server objects;

initialize consumer server objects and consumer client objects within an object-oriented consumer application program interface (API) configured for use on a multi-threaded, client-server operating system;

sending requests for data to a producer subsystem using at least one of the consumer server objects;

receiving acknowledgments from a producer subsystem in response to requests from the producer subsystem using at least one of the consumer client objects; and

receiving data from a producer subsystem in response to requests from the producer subsystem using at least one of the consumer client objects.

Assignments (14)
SECURITY INTEREST Recorded Apr 2, 2015
From: WELLS FARGO BANK, NATIONAL ASSOCIATION
To: USNR/KOCKUMS CANCAR COMPANY
Reel/Frame 035392/0925 →
SECURITY AGREEMENT Recorded Jan 28, 2014
From: USNR/KOCKUMS CANCAR COMPANY
To: WELLS FARGO BANK, NATIONAL ASSOCIATION
Reel/Frame 032132/0979 →
RELEASE OF SECURITY INTEREST Recorded Dec 16, 2013
From: CNM ACQUISITION LLC
To: KOCKUMS CANCAR CO.
Reel/Frame 031819/0509 →
RELEASE OF SECURITY INTEREST Recorded Dec 14, 2013
From: CNM ACQUISITION LLC
To: KOCKUMS CANCAR CO.
Reel/Frame 031816/0752 →
AMALGAMATION Recorded Jul 30, 2010
From: CAE INC.; CAE ELECTRONICS LTD./CAE ELECTRONIQUE LTEE.
To: CAE INC.
Reel/Frame 024767/0442 →
AMALGAMATION Recorded Jul 30, 2010
From: CAE ELECTRONICS LTD./CAE ELECTRONIQUE LTEE.; CAE NEWNES LTD.; CAE SCREENPLATES INC./TAMIS CAE INC.
To: CAE ELECTRONICS LTD./CAE ELECTRONIQUE LTEE.
Reel/Frame 024767/0384 →
CHANGE OF NAME Recorded Jul 29, 2010
From: NEWNES MACHINE LTD.
To: CAE NEWNES LTD.
Reel/Frame 024755/0639 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 29, 2010
From: WOODS, STEVE C.; MCGUIRE, MICHAEL; OGLOFF, HARRY; SKOCIC, ZVONIMIR; JOHNSON, EMERIC
To: NEWNES MACHINES LTD.
Reel/Frame 024755/0610 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 21, 2009
From: COE NEWNES/MCGEHEE, INC.
To: USNR/KOCKUMS CANCAR COMPANY
Reel/Frame 022575/0162 →
SECURITY AGREEMENT Recorded Feb 13, 2007
From: COE NEWNES/MCGEHEE, INC.
To: BANK OF NEW YORK
Reel/Frame 018884/0465 →
SECURITY AGREEMENT Recorded Aug 4, 2005
From: COE NEWNES/MCGEHEE ULC
To: ABLECO FINANCE LLC
Reel/Frame 016353/0498 →
CHANGE OF NAME Recorded Aug 4, 2005
From: COE NEWNES/MCGEHEE ULC
To: COE NEWNES/MCGEHEE INC.
Reel/Frame 016353/0537 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 3, 2003
From: CAE INC.
To: CAE WOOD PRODUCTS G.P.
Reel/Frame 014437/0444 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 3, 2003
From: CAE WOOD PRODUCTS G.P.
To: COE NEWNES/MCGEHEE ULC
Reel/Frame 014437/0460 →