Methods and systems for imaging device display standardization

• US 7,920,101 B2
• Filed: 09/22/2005
• Issued: 04/05/2011
• Est. Priority Date: 10/08/2004
• Status: Expired due to Fees

• 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: Stevens, Mark Liu, Yamamura, Shinichi, Lum, Joey P.
• Primary Examiner(s): Mengistu; Amare
• Assistant Examiner(s): ZHOU, HONG
• Application Number:
  US11/233,270
• Publication Number:
  US 20060077444A1
• Time in Patent Office: 2,021 Days
• Field of Search: 345 11- 13, 345 21- 23, 345/102, 715/221, 715/235, 715/204, 715/255, 358 111- 118, 358/1.9
• US Class Current: 345/2.1
• CPC Class Codes: G03G 15/502 relating to the structure of the control menu, e.g. pop-up menus, help screens
• CPC Class Codes: G03G 15/5087 for receiving image data
• CPC Class Codes: G03G 2215/00109 Remote control of apparatus, e.g. by a host
• CPC Class Codes: G06F 21/41 where a single sign-on provides access to a plurality of computers
• CPC Class Codes: G06F 21/84 output devices, e.g. displays or monitors
• CPC Class Codes: G06K 15/00 Arrangements for producing a permanent visual presentation of the output data , e.g. computer output printersprinting or plotting combined with another operation, e.g. with conveying, G06K17/00
• CPC Class Codes: G06K 15/005 only locally
• 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/00352 Input means H04N1/00411 takes precedence; input arrangements for computers G06F3/00
• CPC Class Codes: H04N 1/32561 using a programmed control device, e.g. a microprocessor
• 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
• CPC Class Codes: H04N 2201/3221 of a job number or identification, e.g. communication number

Abstract

Aspects of the present invention relate to systems, methods and devices for imaging device display standardization. Some aspects relate to the integration of imaging-device-independent display information with imaging-device-dependent formatting information that may be resident on the imaging device. Some aspects relate to integration of application-specific template data with imaging-device-specific formatting data.

Claims

1. A method for forming display information for an imaging device (IDev) display, said method comprising:

receiving application menu data from a remote computing device (RCD) with a web service module on said IDev, wherein said application menu data is in the form of a markup language message, wherein said application menu data registers a remote application on said RCD with said IDev via a device management application programming interface (API) such that input received on an IDev user interface (UI) is routed to said remote application on said RCD, wherein said remote application may be activated by a selection on said IDev UI and wherein said device management API allows said remote application on said RCD to obtain and set IDev device status settings, IDev device configuration options, IDev web page settings, IDev key operator programs, IDev job status data, IDev click counts, IDev data security settings and IDev reboot functions;

displaying said application menu data on a display of said IDev;

receiving an application selection as user input on said IDev UI, in response to said displaying;

sending an indication of said application selection from said web service on said IDev to a template server application (TSA) at said RCD;

receiving IDev-independent display information from said remote application;

integrating said IDev-independent display information with IDev-dependent formatting information residing on the IDev to form IDev display data, wherein said IDev-dependent formatting information relates to an IDev display dimension and an IDev user interface (UI) configuration such that said integrating formats said IDev-independent display information for display on said IDev display with said IDev display dimension and configures said IDev UI to receive input in relation to said IDev-independent display information;

displaying said integrated display information on said IDev UI;

receiving user input at said IDev UI in response to said displaying; and

sending said user input to said remote application.

2. The method of claim 1 wherein said formatting comprises formatting a markup-language page.

3. The method of claim 1 wherein said IDev-independent display information conforms to a syntactic profile.

4. The method of claim 1 wherein said IDev-dependent formatting information further comprises at least one of the attributes selected from a set consisting of layout and display attributes.

5. The method of claim 1 wherein said receiving is, at least partially, accomplished with an HTTP request.

6. A method for imaging device display standardization, said method comprising:

receiving application menu data from a remote computing device (RCD) with a web service module on said IDev, wherein said application menu data is in the form of a markup language message, wherein said application menu data registers a remote application on said RCD with said IDev via a device management application programming interface (API) such that input received on an IDev user interface (UI) is routed to said remote application on said RCD, wherein said remote application may be activated by a selection on said IDev UI and wherein said device management API allows said remote application on said RCD to obtain and set IDev device status settings, IDev device configuration options, IDev web page settings, IDev key operator programs, IDev job status data, IDev click counts, IDev data security settings and IDev reboot functions;

displaying said application menu data on a display of said IDev;

receiving an application selection as user input on said IDev UI, in response to said displaying;

sending an indication of said application selection from said web service on said IDev to a template server application (TSA) at said RCD;

receiving said application selection from said IDev at said TSA;

matching said application selection from said IDev with application-specific template field data (ASTFD) and a form ID with said TSA;

sending said ASTFD and said form ID to said IDev from said TSA;

receiving said ASTFD and said form ID at said IDev from said TSA; and

integrating said ASTFD with a stored form identified by said form ID to generate an integrated page;

wherein said stored form relates to an IDev display dimension and an IDev user interface (UI) configuration such that said integrating formats said ASTFD for display on an IDev display with said IDev display dimension and configures said IDev UI to receive input in relation to said ASTFD;

displaying said integrated page on said IDev display;

receiving user input at said IDev UI in response to said displaying; and

sending said user input to said remote application.

7. A method as described in claim 6 wherein said sending is at least partially accomplished with an HTTP request.

8. A method as described in claim 6 wherein said stored form resides on said IDev.

9. A method as described in claim 6 wherein said stored form resides on a remote computing device (RCD).

10. A method as described in claim 6 wherein said application-specific template field data (ASTFD) is formatted in a markup language.

11. A method as described in claim 6 wherein said form ID is an XHTML form reference.

12. A method as described in claim 6 wherein said form ID is sent separately from said ASTFD.

13. A method as described in claim 6 wherein said integrated page is formatted in a markup language.

14. A method for imaging device display standardization, said method comprising:

receiving application menu data from a remote computing device (RCD) with a web service module on said IDev, wherein said application menu data is in the form of a markup language message, wherein said application menu data registers a first remote application on said RCD with said IDev via a device management application programming interface (API) such that input received on an IDev user interface (UI) is routed to said first remote application on said RCD, wherein said first remote application may be activated by a selection on said IDev UI and wherein said device management API allows said first remote application on said RCD to obtain and set IDev device status settings, IDev device configuration options, IDev web page settings, IDev key operator programs, IDev job status data, IDev click counts, IDev data security settings and IDev reboot functions;

displaying said application menu data on a display of said IDev;

receiving a first application selection as user input on said IDev UI, in response to said displaying;

sending an indication of said first application selection from said web service on said IDev to a template server application (TSA) at said RCD, said indication having the purpose of accessing said first remote application;

receiving said indication of said first application selection from said IDev at said TSA;

identifying a first application-specific template field data (ASTFD) and a first form ID associated with said first application selection;

retrieving said first ASTFD and said first form ID;

sending said first ASTFD and said first form ID from said TSA to said IDev;

receiving said first ASTFD and said first form ID at said IDev; and

integrating said first ASTFD with a first stored form identified by said first form ID to form a first integrated page, wherein said first stored form relates to an IDev display dimension and an IDev user interface (UI) configuration such that said integrating formats said ASTFD for display on an IDev display with said IDev display dimension and configures said IDev UI to receive input in relation to said ASTFD;

sending said first integrated page to said IDev;

displaying said first integrated page on said IDev display;

receiving first user input at said IDev UI in response to said displaying said first integrated page;

sending said first user input to said remote application;

sending a second application selection from an IDev to a template server application (TSA), said selection having the purpose of accessing a second remote application;

receiving said second application selection from said IDev at said TSA;

identifying a second application-specific template field data (ASTFD) and a second form ID associated with said second application selection;

retrieving said second ASTFD and said second form ID;

sending said second ASTFD and said second form ID from said TSA to said IDev;

receiving said second ASTFD and said second form ID at said IDev;

integrating said second ASTFD with a second stored form identified by said second form ID to form a second integrated page, wherein said second stored form relates to a second IDev display dimension and a second IDev user interface (UI) configuration such that said integrating formats said second ASTFD for display on an IDev display with said second IDev display dimension and configures said IDev UI to receive input in relation to said second ASTFD;

displaying said second integrated page on said IDev display;

receiving second user input at said IDev UI in response to said displaying said second integrated page; and

sending said second user input to said second remote application.