US20030208558A1 - Embedding web access functionality into a device for user interface functions - Google Patents

Abstract

Web access functionality is embedded in a device to enable low cost widely accessible and enhanced user interface functions for the device. A web server in the device provides access to the user interface functions for the device through a device web page. A network interface in the device enables access to the web page by a web browser such that a user of the web browser accesses the user interface functions for the device through the web page.

Description

BACKGROUND OF THE INVENTION
• 1. Field of Invention[0001]
• The present invention pertains to the field of user interfaces for devices. More particularly, this invention relates to embedding web access functionality into devices to provide enhanced and widely accessible user interface functions.[0002]
• 2. Art Background[0003]
• A wide variety of devices including office equipment, home-based equipment, and lab equipment, as well as a variety of other types of devices commonly provide device specific user interface functions. Such devices may also be referred to as gadgets. Office equipment includes, for example, printers, fax machines, copiers, and various types of communication and telephony devices. Home-based devices include home entertainment equipment such as televisions and video and audio players and recorders as well as security systems, automobiles, appliances, thermostats, and hot tubs. Lab equipment includes measurement devices such as oscilloscopes, spectrum analyzers and other types of measurement equipment as well as networking equipment.[0004]
• The user-interface mechanisms of such devices commonly include relatively simple and low cost user input and display mechanisms. Such simple mechanisms may include, for example, light emitting elements such as LED/LCD elements as well as various types of simple input buttons or switches. Such simple mechanisms are typically constructed to be low cost to minimize the overall cost of such devices. In addition, such mechanisms are usually compact and enable relatively small sizes for such devices. Unfortunately, such simple user interface mechanisms severely limit the range and flexibility of the user interface functions provided by such devices.[0005]
• The user-interface functions of such a device may be enhanced by the implementation of a screen-based user interface mechanism within the device. For example, such a device may include a display screen, and a rendering processor along with appropriate software for generating a rich graphical user interface suitable for the particular type of device. However, such screen displays and rendering mechanisms are usually expensive and increase the overall cost of the device. Such high costs are typically unsuitable for lower cost devices targeted for a relatively large mass market. Moreover, display screens and associated hardware may be too bulky for the size constraints of many devices.[0006]
• A screen-based user interface may be provided for a device using an external computer system. For example, the device may be connected to the computer system through either a standard connection such as a serial or parallel port connection or through a specialized hardware interface. The external computer system usually executes a set of software for communication and user interface to the device. The external computer system may implement a screen-based user interface for the device. The external computer system may also execute web server software that enables external web browsers to access the computer system and in turn the user interface of the device.[0007]
• Unfortunately, such an external computer system greatly increases the cost of providing a screen-base user interface for a device. In addition, such prior computer system based solutions usually require the development of specialized software for each particular type of device. Moreover, such specialized software for a particular device from a particular manufacturer must typically be developed for differing types of computer system platforms. Such a variety of differing software for differing platforms greatly complicates the task of providing support for the devices. Furthermore, the development and support costs of such a variety of software usually increase the overall cost of providing a screen based user interface for such devices.[0008]
SUMMARY OF THE INVENTION
• A solution for providing widely accessible, low cost, and enhanced user interface functions for a device is disclosed. The solution involves embedding web access functionality into the device including a web server that provides a device web page. The device includes an embedded network interface that enables access to the device web page by a web browser. A user of the web browser accesses the user interface functions for the-device through the device web page. The-web server functionality may be implemented with existing circuitry in a device, such as an exiting processor, memory, and input/output circuitry that normally perform device-specific functions, thereby avoiding the extra cost and space required for dedicated web server hardware for the device.[0009]
• The web server functionality embedded in the device enables device user interface access via a variety of communication mechanisms including the world wide web portion of the Internet. The costs of providing screen based user interface mechanisms are exported away from the device and do not require an external computer to provide a device web server. The methods and mechanisms disclosed herein provide screen based user-friendly interfaces to a wide variety of devices without the necessity to develop expensive hardware and software applications for differing devices. The present methods and mechanisms employ web technology so that access to a device user interface is independent of the computer system platform employed and independent of the web browser software executed and independent of the location of the user.[0010]
• The user interface information is packaged using the Hyper-Text Markup Language (HTML) and is transported according to the Hyper-Text Transfer Protocol (HTTP). The HTML and HTTP protocols enable communication with existing web browsers independent of the platform that executes the web browser. The present techniques avoid the need of an industry-wide Application Programming Interface (API) to unify the control and use of equipment.[0011]
• Other features and advantages of the present invention will be apparent from the detailed description that follows.[0012]
BRIEF DESCRIPTION OF THE DRAWINGS
• The present invention is described with respect to particular exemplary embodiments thereof and reference is accordingly made to the drawings in which:[0013]
• FIGS. 1[0014]a-1billustrate a device with embedded web access functionality that provides device-specific user interface functions through a device web page;
• FIG. 2 shows a home-based network that enables a web browser to access the user interface functions through the device web page;[0015]
• FIG. 3 illustrates an example device web page for a printer device;[0016]
• FIG. 4 shows a large organization network or intranet that enables access to the device web pages of differing devices;[0017]
• FIG. 5 illustrates access to device web pages through the Internet world-wide web.[0018]
DETAILED DESCRIPTION
• FIG. 1[0019]aillustrates adevice10 with embedded web access functionality that provides device-specific user interface functions. Thedevice10 includes anetwork interface12 and aweb server14 along with amonitor16. Thenetwork interface12 enables communication via acommunication path22. Themonitor16 controls various device-specific functions of thedevice10 and monitors a set of information pertaining to-thedevice10 via a control/monitor path20. Theweb server14 provides web server functions to web clients via thecommunication path22. Theweb server14 provides web server functions according to the Hyper-Text Transfer Protocol (HTTP).
• The[0020]web server14 receives HTTP commands through thenetwork interface12 that specify a predetermined Universal Resource Locator (URL) for thedevice10. The HTTP commands may be used by web clients to read information from thedevice10 such as device status information. The HTTP commands may also be used to transfer information to thedevice10 such as information that controls the functions or operating states of thedevice10. Such HTTP commands include HTTP GET, HTTP POST, and HTTP PUT commands.
• In response to an HTTP command targeted for the[0021]device10, theweb server14 generates aweb page18 that defines a set of user interface functions for thedevice10. Theweb page18 is a Hypertext Markup Language (HTML) file. Thenetwork interface12 transfers theweb page18 to a requesting HTTP client via thecommunication path22.
• The[0022]web server14 generates theweb page18 dynamically to reflect the updated state of the information pertaining to thedevice10 that is maintained by themonitor16. Theweb page18 may also define control buttons according to the HTTP protocol that enable various control functions for thedevice10 to be initiated from a web client via thecommunication path22. Theweb page18 may contain text, images, multimedia files, forms, tables or any object type supported by the HTTP and HTML protocols.
• In addition, the[0023]web page18 may contain one or more URLs that specify additional web pages located within thedevice10. Theweb page18 may also contain one or more URLs that specify additional web pages located elsewhere, i.e. external to thedevice10. The additional web pages external to thedevice10 may be located, for example, on a local communication network or on the Internet world wide web.
• The[0024]device10 represents a wide variety of devices including devices such as printers, fax machines, copiers, communication and telephony devices, home entertainment devices such as televisions, video and audio devices as well as appliances such as refrigerators and washing machines, security systems, automobiles, and hot tubs. Thedevice10 also represents a variety of measurement instruments including oscilloscopes, and spectrum analyzers and other types of measurement devices. In addition, thedevice10 represents a variety of computer peripheral devices including mass storage units such as rotating media storage units.
• The[0025]communication path22 represents any communication means that is capable of transferring HTML files according to the HTTP web protocol. Thecommunication path22 may be realized by a wide variety of communication mechanisms including local area networks, telephone lines including cellular telephone links, serial communication links, parallel communication links, power line communication links, and radio and infrared communication links. Thecommunication path22 may also be a direct Internet connection to the world-wide web.
• FIG. 1[0026]bis a hardware block diagram of thedevice10. Thedevice10 includes aprocessor200, amemory210, a set of device-specific hardware300 along with a set of input/output circuitry220 that enables communication via thecommunication path22. Theprocessor200 performs device-specific functions for thedevice10 in combination with the device-specific hardware300. Theprocessor200 is also employed to provide web server functionality in thedevice10. In one embodiment, theprocessor200 stores theweb page18 in thememory210 which may also be used to store information associated with normal device-specific functions.
• In one embodiment, the[0027]device10 is a printer device wherein theprocessor200 and thememory210 preform image rendering functions and the device-specific hardware300 includes printer hardware and associated circuitry and wherein the input/output circuitry220 provides network access to theprinter device10. The web server functionality is embedded into theprinter device10 by providing software or firmware for theprocessor200 and by utilizing space available in thememory210 and by using the existing input/output circuitry220 such as Ethernet circuitry to transfer HTML files.
• In another embodiment, the[0028]device10 is a video player/recorder wherein theprocessor200 and thememory210 perform functions for reading video and audio information from and writing video and audio information to a storage media such as magnetic tape or an optical storage media. The device-specific hardware300 includes media actuation hardware such as motors and magnetic heads and associated circuitry for reading and imparting information onto the storage media. The web server functionality is embedded into thevideo device10 by providing software or firmware for theprocessor200 and by utilizing space available in thememory210 and by adding the input/output circuitry220 to thevideo device10.
• In yet another embodiment, the[0029]device10 is a washing machine wherein theprocessor200 and thememory210 preform functions for controlling wash cycles. The device-specific hardware300 includes hardware such as motors, valves, sensors, and associated circuitry. The web server functionality is embedded into thewashing machine10 by providing software or firmware for theprocessor200 and by utilizing space available in thememory210 and by adding the input/output circuitry to thevideo device10.
• The web server functionality for the[0030]device10 includes software executed by theprocessor200 that services the HTTP protocol and that generates HTML formatted files. Theweb page18 in one embodiment is stored in thememory210 or may be generated on the fly. Theprocessor200 also executes communication software that drives the input/output circuitry220 and provides the functionality of thenetwork interface12. In addition, theprocessor200 executes software that performs control and information monitoring and-logging functions of themonitor16.
• In another embodiment, the web server functions of the[0031]device10 are implemented on a single integrated circuit chip including a processor and memory for holding software for servicing the HTTP protocol. In such an embodiment, the hardware portion of thenetwork interface12 may be implemented on the same integrated circuit chip as the processor or may be external to that chip.
• In yet another embodiment, the web server functions of the[0032]device10 are implemented with a state machine.
• In another embodiment, the[0033]device10 is a controller module or control computer contained in an automobile. The input/output circuitry220 such as cellular transmitter/receiver circuitry enables a web browser to access control and status information for the automobile which is contained in theweb page18.
• In another embodiment, the[0034]device10 is a mass storage device such as a disk drive or CD-ROM drive. The input/output circuitry220 such as local area network interface circuitry enables a web browser to access control and status information for the mass storage device which is contained in theweb page18.
• In yet another embodiment, the[0035]device10 is a home-entertainment device such as an audio system. The input/output circuitry220 such as infrared communication circuitry or power line communication circuitry enables a web browser such as a home computer to access control and status information for the audio system which is contained in theweb page18.
• The[0036]memory210 may be a static memory such as read-only memory, a flash memory, or a disk drive or may be a volatile memory such as a random access memory. The web page may be stored in the static memory or the random access memory in the HTML format or may be generated on the fly without being stored in thedevice10.
• FIG. 2 shows a home-based[0037]network30 that enables aweb browser40 to access the user interface functions of thedevice10. The home-basednetwork30 may be implemented with a variety of communication mechanisms suitable for a home including power line communication links, twisted pair communication links, radio frequency communication links, and infrared communication links.
• The[0038]web browser40 includes adisplay42 for generating visual objects including text, images,multimedia objects, and graphical user interface objects. Theweb browser40 includes aselection device44 that enables a user to select objects and URL links rendered on thedisplay42. Theweb browser40 may also include an audio capability that enables rendering of audio information to the user.
• The home-based[0039]network30 may also enable communication among a set of devices50-52. The devices50-52 may include devices such as home appliances, home security systems, home entertainment devices, air-conditioning systems and hot-tubs. Any of the devices50-52 that implement the device web page mechanisms disclosed herein may provide device specific user interface web pages to theweb browser40 via the home-basednetwork30.
• The[0040]web browser40 may be embodied in a computer system that executes a set of web browser software. Such a computer system with web browser functionality may be realized by any one of a variety of available computer system platforms including Windows platforms, Macintosh platforms, Unix platforms as well as any other platform capable of executing web browser software that provides HTTP client functions and that renders HTML files.
• The[0041]web browser40 may-also be embodied in a variety of other devices that provide HTTP client functions and that render HTML files. Such devices include specialized hardware designed for television or telephone systems as well as low cost web browser devices and network computers.
• A user accesses and controls the user interface functions of the[0042]device10 using theweb browser40. The user enters a URL corresponding to thedevice10 into theweb browser40. In response, theweb browser40 transfers an HTTP command which includes the entered URL over the home-basednetwork30. Thedevice10 receives the HTTP command via thecommunication path22 and recognizes the URL contained therein.
• In one embodiment, the information for the[0043]web page18 is periodically updated by theprocessor200 and is stored in HTML format in thememory210. In such an embodiment, theprocessor200 reads theweb page18 from thememory210 in response to the HTTP command and transfers theweb page18 to theweb browser40 via the home basednetwork30.
• In an alternative embodiment, the[0044]processor200 generates theweb page18 on the fly in response to the HTTP command from theweb browser40. In such an embodiment, theprocessor200 obtains information pertaining to the device from the device-specific hardware300 after receiving the HTTP command and recognizing the URL contained therein. Theprocessor200 formats the information into the HTML format that defines theweb page18 and transfers the HTML formatted information to theweb browser40 via the home basednetwork30.
• The HTML file is transferred according to the HTTP protocol which specifies the URL corresponding to the[0045]web browser40. Theweb browser40 receives the HTML file and renders theweb page18 on thedisplay42.
• The following is an example HTML file that defines the[0046]web page18 in an embodiment wherein thedevice10 is a printer device.
• <TITLE>Printer Home Page</TITLE>[0047]
• <H1>home page for[0048]device10</H1>
• <HR>[0049]
• The following information pertains to the[0050]device10 which in this example is a printer
• <table border>[0051]
• <caption>Printer with a URL</caption>[0052]
• <TR>[0053]
• <TD>Printer Name</TD>Portdv9</TD>[0054]
• </TR>[0055]
• <TR>[0056]
• <TD>Administrator</Tl><TD>Mr. John Doe</TD>[0057]
• <TR>[0058]
• <TD>Location</TD><TD>[0059]Building 1U</TD>
• </TR>[0060]
• </TABLE>[0061]
• <P>[0062]
• <A HREF=“http://www.hpsc.com”>Service Contract</A>[0063]
• <P>[0064]
• <A HREF=“http://www.hpsupl.com”>Supplies ordering</A>[0065]
• <P>[0066]
• <A HREF=“http://www.hpl.hp.com”>Future Products</A>[0067]
• <P>[0068]
• <HR>[0069]
• FIG. 3 illustrates the[0070]web page18 for the example HTML file shown above wherein thedevice10 is a printer. Theweb page18 is rendered on thedisplay42 by theweb browser40 in response to the example HTML code set forth above. Theweb page18 includes apage title70, aheader section60, a set ofASCII text62, atable section64, and a set of hyperlinks66-68.
• The[0071]page title70 is defined by the HTML <TITLE>Printer Home Page</TITLE> coding shown above. Theheader section60 is defined by the HTML code <H1>Home Page fordevice10</H1>in the HTML file shown above. TheASCII text62 is the ASCII text contained in the HTML file shown above. Thetable section64 is defined with coding in the HTML file shown above and provides information pertaining to the printer including a printer name, an administrator, and a location for the printer.
• The hyperlinks[0072]66-68 defined in the HTML file shown above direct theweb browser40 to other web pages for various printer support functions. For example, thehyperlink66 “Service Contract” may be selected by the user with theselection device44 to direct theweb browser40 to the URL “http://www.hpsc.com” for information regarding printer service contracts. Similarly,hyperlinks67 and68 provide links to web pages for ordering printer supplies and obtaining information for future printer products from the manufacturer of theprinter device10.
• The[0073]web page18 for the printer may also include manuals, parts lists, and other associated publications. These publication may be stored within thedevice10 in, for example, a nonvolatile memory, or may be referenced elsewhere via hyperlinks contained in theweb page18. These publications contain dynamic information such as updated manuals as well as new and updated software driver routines for thedevice10.
• FIG. 4 shows a[0074]large organization network80 that enables access to the device web pages of thedevice10 and the devices50-52. Thelarge organization network80 may be referred to as an Intranet and may be implemented with a variety of communication mechanisms including local area networks connected together by various types of communication links.
• Any one or more of a set of computer systems[0075]90-92 coupled to thelarge organization network80 may access the device web pages of thedevices10 and50-52. The computer systems90-92 may execute one or more of a variety of available web browser software or may have web browser functions built in.
• A user of one of the computer systems[0076]90-92 enters a URL corresponding to the desired one of thedevices10 and50-52 into the corresponding web browser application. In response, the particular web browser application as an HTTP client transfers an HTTP command that specifies the desired URL over thelarge organization network80. The device specified by the HTTP command recognizes the URL contained therein. In response, the targeted device transfers an HTML file that defines its device web page vialarge organization network80. The transfer of the HTML file specifies the URL of the originating HTTP client computer system from among the computer systems90-92. The originating HTTP client computer system recognizes its URL and receives and then renders the device web page to the user.
• FIG. 5 illustrates access to device web pages through a direct Internet connection to the world-[0077]wide web100. Theweb page18 of thedevice10 may be accessed by any web client on the world-wide web100 including theweb browser40.
• In addition, a[0078]communication system102 functions as a communication bridge between the world-wide web100 and alocal area network120 and acommunication system104 functions as a communication bridge between the world-wide web100 and ahome base network130. As a consequence, any other HTTP clients coupled to thelocal area network120 or the home-base network130 may access the device web pages in adevice108, adevice106, or thedevice10. In addition, theweb browser40 or any HTTP client on the world-wide web100 may access the device web pages of thedevices106 and108.
• The embedded web server functionality described herein enables a variety of widely accessible device interrogation and control functions for a particular device as well as for sets of devices. For example, a web page may be embedded into each washing machine of a chain of Laundromats wherein an operator from an office computer can determine the machines that require servicing and schedule daily service routing to the Laundromats accordingly.[0079]
• The foregoing detailed description of the present invention is provided for the purposes of illustration and is not intended to be exhaustive or to limit the invention to the precise embodiment disclosed. Accordingly, the scope of the present invention is defined by the appended claims.[0080]

Claims (32)

What is claimed is:

1. A web access mechanism embedded in a device, comprising:

web server that generates a device web page wherein the device web page provides a set of user interface functions for the device;

network interface that enables access to the device web page by a web browser such that a user of the web browser accesses the user interface functions for the device through the device web page.

2. The web access mechanism ofclaim 1, wherein the web server receives an HTTP command via the network interface and then generates an HTML file that defines the device web page in response to the HTTP command.

3. The web access mechanism ofclaim 2, wherein the HTTP command specifies a URL corresponding to the device.

4. The web access mechanism ofclaim 3, wherein the HTML file contains a set of information pertaining to the device.

5. The web access mechanism ofclaim 3, wherein the HTML file contains a set of URLs that control a set of predetermined functions for the device wherein each URL may point to a web page located internal to the device or a web page located external to the device.

6. The web access mechanism ofclaim 3, wherein the HTML file contains a hyperlink to an external web page that specifies additional information pertaining to the device.

7. A device, comprising:

processor that generates a device web page wherein the device web page provides a set of user interface functions for the device and includes a set of information pertaining to the device;

memory for storing the device web page;

input/output circuitry that enables communication via a communication path such that a web browser accesses the device web page via the communication path.

8. The device ofclaim 7, wherein the processor receives an HTTP command via the input/output circuitry and then generates an HTML file that defines the device web page in response to the HTTP command.

9. The device ofclaim 8, wherein the HTTP command specifies a URL corresponding to the device.

10. The device ofclaim 8, wherein the HTML file contains a set of URLs that control a set of predetermined functions for the device wherein each URL may point to a web page located internal to the device or a web page located external to the device.

11. The device ofclaim 8, wherein the HTML file defines a set of graphical mechanisms for controlling a set of predetermined functions for the device.

12. The device ofclaim 8, wherein the HTML file contains a hyperlink to an external web page that specifies additional information pertaining to the device.

13. A user interface method for a device, comprising the steps of:

generating a device web page within the device wherein the device web page provides a set of user interface functions for the device;

providing access to the device web page from a web browser external to the device such that a user of the web browser accesses the user interface functions for the device through the device web page.

14. The method ofclaim 13, wherein the step of generating a device web page includes the step of generating an HTML file that defines the device web page in response to an HTTP command received from the web browser.

15. The method ofclaim 14, wherein the HTTP command specifies a URL corresponding to the device.

16. The method ofclaim 14, wherein the HTML file contains a set of information pertaining to the device.

17. The method ofclaim 14, wherein the HTML file contains a set of URLs that control a set of predetermined functions for the device wherein each URL may point to a web page located internal to the device or a web page located external to the device.

18. The method ofclaim 14, wherein the HTML file contains a hyperlink to an external web page that specifies additional information pertaining to the device.

19. A user interface apparatus embedded in a device, comprising:

means for generating a device web page within the device wherein the device web page provides a set of user interface functions for the device;

means for providing access to the device web page from a web browser external to the device such that a user of the web browser accesses the user interface functions for the device through the device web page.

20. The apparatus ofclaim 19, wherein the means for generating a device web page includes means for generating an HTML file that defines the device web page in response to an HTTP command generated by the web browser.

21. The apparatus ofclaim 20, wherein the HTTP command specifies a URL corresponding to the device.

22. The apparatus ofclaim 20, wherein the HTML file contains a set of information pertaining to the device.

23. The apparatus ofclaim 20, wherein the HTML file contains a set of URLs that control a set of predetermined functions for the device wherein each URL may point to a web page located internal to the device or a web page located external to the device.

24. The apparatus ofclaim 20, wherein the HTML file contains a hyperlink to an external web page that specifies additional information pertaining to the device.

25. A system, comprising:

device having an embedded web server that generates a device web page wherein the device web page provides a set of user interface functions for the device and includes a set of information pertaining to the device, the device also having a network interface that enables access to the device web page via a communication network;

web browser coupled to the communication network wherein a user of the web browser accesses the user interface functions for the device through the device web page.

26. The system ofclaim 25, wherein the web server in the device receives an HTTP command via the communication network and the network interface and then generates an HTML file that defines the device web page in response to the HTTP command.

27. The system ofclaim 26, wherein the HTTP command specifies a URL corresponding to the device.

28. The system ofclaim 26, wherein the HTML file contains a set of URLs that control a set of predetermined functions for the device such that the user of the web browser selects the URLs to control the predetermined functions of the device wherein each URL may point to a web page located internal to the device or a web page located external to the device.

29. The system ofclaim 26, wherein the HTML file contains a hyperlink to an external web page located elsewhere on the communication network that specifies additional information pertaining to the device.

30. The system ofclaim 25, wherein the communication network comprises a home-based communication network.

31. The system ofclaim 25, wherein the communication network comprises a large-organization communication network.

32. The system ofclaim 25, wherein the communication network comprises the world wide web of the Internet.

Images