Methods and systems for imaging device accounting server redundancy

• US 8,237,946 B2
• Filed: 07/29/2005
• Issued: 08/07/2012
• Est. Priority Date: 10/08/2004
• Status: Active Grant

• Current Assignee: Sharp Kabushiki Kaisha (Hon Hai Precision Industry Co., Ltd.)
• Original Assignee: Sharp Laboratories of America Incorporated (Hon Hai Precision Industry Co., Ltd.)
• Inventors: Lovat, David J., Zhang, Hanzhong
• Primary Examiner(s): Haskins, Twyler
• Assistant Examiner(s): RODRIGUEZ, LENNIN ROBINSON
• Application Number:
  US11/192,870
• Publication Number:
  US 20060077435A1
• Time in Patent Office: 2,566 Days
• Field of Search: 358 111- 118, 714/4
• US Class Current: 358/1.14
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/55 Push-based network services
• CPC Class Codes: H04N 1/00204 with a digital computer or a digital computer system, e.g. an internet server programmed control between transmitter and receiver or between image input and image output device H04N1/32561
• CPC Class Codes: H04N 1/00244 with a server, e.g. an internet server fax-servers or the like for store and forward H04N1/324
• CPC Class Codes: H04N 1/00352 Input means H04N1/00411 takes precedence; input arrangements for computers G06F3/00
• CPC Class Codes: H04N 1/00464 using browsers, i.e. interfaces based on mark-up languages
• CPC Class Codes: H04N 1/00503 Customising to a particular machine or model, machine function or application
• CPC Class Codes: H04N 2201/0039 Connection via a network
• CPC Class Codes: H04N 2201/0049 By wire, cable or the like
• CPC Class Codes: H04N 2201/0075 by a user operated remote control device, e.g. receiving instructions from a user via a computer terminal or mobile telephone handset
• CPC Class Codes: H04N 2201/0094 Multifunctional device, i.e. a device capable of all of reading, reproducing, copying, facsimile transception, file transception

Abstract

Aspects of the present invention relate to systems, methods and devices for maintaining imaging device (IDev) accounting data in the event that an imaging device'"'"'s primary accounting server becomes unavailable. Some aspects relate to the use of a lightweight accounting backup server (LABS) that may reside on an imaging device, a networked computer or another computing device for the purpose of storing and communication accounting data when a primary accounting server fails.

Claims

1. A method for maintaining imaging device (IDev) accounting data in the event of a primary accounting server failure, said method comprising:

listing a regional lightweight accounting back-up server (LABS) on an LABS list accessible to a plurality of IDevs within a geographical region, wherein said LABS is an application running on a network computing device, said LABS maintaining a financial accounting record of jobs performed by users of said IDevs with user accounts when a primary accounting server (PAS) is unavailableto said IDevs and wherein said LABS list consists of a listing of addresses for a plurality of network devices with LABS capability available only to said plurality of IDevs within said geographical region;

monitoring a network for IDev availability requests from said LABS;

receiving an availability request at said LABS from one of said IDevs whose PAS has become unavailable;

responding to said request by sending an availability confirmation to said one of said IDevs;

receiving IDev activity data from said one of said IDevs; and

maintaining a temporary IDev activity log(TIAL) comprising said IDev activity data wherein said TIAL comprises a financial accounting record of jobs performed by users of said one of said IDevs with user accounts.

2. A method as described in claim 1 wherein said LABS is not the primary function of said network computing device.

3. A method as described in claim 1 wherein said availability request and said activity data are received in a single message from said IDev.

4. A method as described in claim 1 wherein said IDev activity data comprises user account data associated with IDev function activity.

5. A method as described in claim 1 wherein said IDev activity data comprises user account data associated with remote application activity accessed through said IDev.

6. A method as described in claim 1 wherein said IDev activity data comprises user account data, IDev function activity and remote application activity data for remote applications accessed through said IDev.

7. A system for maintaining imaging device (IDev) accounting data in the event of a primary accounting server failure, said system comprising:

a) a regional lightweight accounting back-up server (LABS) list accessible to a plurality of IDevs within a geographical region, wherein said LABS is an application running on a network computing device, said LABS maintaining a financial accounting record of jobs performed by users of said IDevs with user accounts when a primary accounting server PAS is unavailable to said IDevs and wherein said LABS list consists of a listing of addresses for a plurality of network devices with LABS capability available only to IDevs in said geographical region;

b) a lightweight accounting back-up server (LABS) application running on a network computing device, wherein said network computing device is listed on said LABS list, said LABS application comprising;

i) a monitor for monitoring a network for IDev availability requests;

ii) a request receiver for receiving an availability request from one of said IDevs whose PAS has become unavailable;

iii) a sender for sending an availability confirmation to said one of said IDevs;

iv) a data receiver for receiving IDev activity data from said one of said IDevs; and

v) a logger for maintaining a temporary IDev activity log(TIAL) comprising said IDev activity data, wherein said TIAL comprises a financial accounting record of jobs performed by users of said one of said IDevs with user accounts.

8. A system as described in claim 7 wherein said LABS is capable of running on a network computing device as a background application.

9. A system as described in claim 7 wherein said request receiver and said data receiver are integrated and may receive a single message from said IDev, said message comprising said availability request and said activity data.

10. A system as described in claim 7 wherein said IDev activity data comprises user account data associated with IDev function activity.

11. A system as described in claim 7 wherein said IDev activity data comprises user account data associated with remote application activity accessed through said IDev.

12. A system as described in claim 7 wherein said IDev activity data comprises user account data, IDev function activity and remote application activity data for remote applications accessed through said IDev.