Capability to build multiple application views from a single system model

• US 8,701,021 B2
• Filed: 07/31/2006
• Issued: 04/15/2014
• Est. Priority Date: 07/31/2006
• Status: Active Grant

• Current Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Original Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Inventors: Kumar, Jeetendra, Neisen, Peter, Gobbak, Nataraj Kumar, Pareed, Yahya, Vadnais, Kevin, Fresk, Jeffrey Sean, Knosp, Joseph, Boam, Matthew M.
• Primary Examiner(s): PHANTANA ANGKOOL, DAVID
• Application Number:
  US11/496,319
• Publication Number:
  US 20080065739A1
• Time in Patent Office: 2,815 Days
• Field of Search: 715/760, 715/761
• US Class Current: 715/760
• CPC Class Codes: G06F 16/9577 Optimising the visualization of content, e.g. distillation of HTML documents
• CPC Class Codes: H04L 43/0817 by checking functioning
• CPC Class Codes: H04L 67/125 involving control of end-device applications over a network
• CPC Class Codes: H04N 1/00344 with a management, maintenance, service or repair apparatus monitoring H04N1/00002
• CPC Class Codes: H04N 2201/0039 Connection via a network
• CPC Class Codes: H04N 2201/0072 Detecting the status of a connected apparatus

Abstract

An embedded marker system includes a plurality of devices communicatively coupled to a single system model. The system further includes a plurality of application views configured to communicate with the system model to obtain status and configuration data associated with one of the plurality of devices.

Claims

1. A system, comprising:

a plurality of devices, at least one of said plurality of devices configured to perform a print function;

a single system model communicatively coupled to said plurality of devices, said single system model comprising a central database configured to dynamically store all status and configuration data for each device in said plurality of devices, said status and application data comprising current error messages of each device; and

a plurality of application views, each said application view being configured to independently communicate only with said central database of said system model to obtain status and configuration data associated with one of said plurality of devices, wherein said central database only distributes error messages to a particular application view making a request and only distributes error messages for a device that said particular application view controls; and

wherein said central database does not mass distribute error messages to all application views.

2. The system of claim 1, further including at least one user interface configured to initiate an application on at least one of said plurality of devices.

3. The system of claim 2, wherein said at least one user interface is configured to display status information and error messages associated with a given device.

4. The system of claim 1, further including a data interface for communicatively coupling each of said plurality of application views to said single system model.

5. The system of claim 4, wherein said data interface is a software bus protocol.

6. The system of claim 1, wherein said plurality of application views includes an application infrastructure from at least one of a control panel, a printer job language, a single function printer, and a printer mode language.

7. The system of claim 1, wherein said plurality of devices includes at least one of a printing device, a scanning device, a faxing device, and a digital sending device.

8. The system of claim 1, wherein said central database is unable to distinguish a first application view from a second application view.

9. The system of claim 1, wherein a first device function is executed independently of a second device function.

10. The system of claim 1, wherein said plurality of application views are configured to implement an application associated with said one of said plurality of devices independently of a status of another of said plurality of devices.

11. The system of claim 1, further comprising a resource analyzer to detect a state of each of said plurality of devices and report said state to said central database.

12. An electronic device, comprising:

a plurality of application views;

a single system model communicatively coupled to said plurality of application views, said single system model comprising a central database configured to store all status and configuration data for said electronic device;

wherein said plurality of application views are configured to obtain status and configuration data only from said central database of said single system model to execute a device function independent of a status of another device function, wherein at least one of the device functions includes a print function; and

wherein said plurality of application views are decoupled from said single system model to permit addition and modification of application views without affecting said single system model and wherein a portion of said status data is displayed to a user by a control panel.

13. The device of claim 12, wherein said plurality of application views are independently communicatively coupled to at least one user interface.

14. The device of claim 13, wherein said at least one user interface is configured to receive status and error messages related to a given device function.

15. The device of claim 12, wherein said device functions include at least one of printing, faxing, scanning, and emailing.

16. The device of claim 12, wherein said plurality of application views includes an application infrastructure from at least one of a control panel, a printer job language, a single function printer, and a printer mode language.

17. The device of claim 12, wherein said central database is unable to distinguish a first application view from a second application view such that said central database distributes error data requested by a particular application view only to that particular application view.

18. The device of claim 12, wherein said central database is to distribute error data requested by a particular application view only to that application view and does not mass distribute status and configuration data to all application views.

19. A method comprising:

initiating a first device function through a first application view from a first user interface;

obtaining, through said first application view and only from a central database of a single system model, error data relating to malfunctions of said first device function;

initiating a second device function through a second application view from a second user interface; and

obtaining, through said second application view and only from said central database of said single system model, error data relating to malfunctions of said second device function;

wherein said central database only distributes error data requested by a particular application view to that application view and does not mass distribute status and configuration data to all application views; and

wherein at least one of said first and second device functions includes a print function, and said second device function is executed independently of a status of said first device function.

20. The method of claim 19, wherein said second device function is executed if an error occurs with said first device function when said second device function is not the same as said first device function.

21. The method of claim 19, wherein said second device function is not executed if an error occurs with said first device function when said second device function is the same as said first device function.

22. The method of claim 19, wherein said first application view is the same as said second application view.

23. The method of claim 19, wherein said plurality of devices includes at least one of a printing, faxing, scanning, and emailing device.

24. The method of claim 19, further comprising storing all status and configuration data for each of said device functions in said central database of said single system model.