Graphical user interface engine for embedded systems
In an embedded system, for instance in a household appliance, in addition to the usual embedded microprocessor/microcontroller there is provided another processor which actually executes a user interface HTML document for accepting user input, for instance from a keypad and controlling the display device, for instance an LCD. The embedded microprocessor hosts the user interface document, responds to requests from the other processor, keeps track of changes in variables shared with the other processor, and executes the control device functionality. The other processor renders the graphical user interface to the display and interacts with the user by executing local functions to operate on the memory and i/o resources of the embedded processor as described by the user interface document served to it.
Latest Patents:
- METHODS AND THREAPEUTIC COMBINATIONS FOR TREATING IDIOPATHIC INTRACRANIAL HYPERTENSION AND CLUSTER HEADACHES
- OXIDATION RESISTANT POLYMERS FOR USE AS ANION EXCHANGE MEMBRANES AND IONOMERS
- ANALOG PROGRAMMABLE RESISTIVE MEMORY
- Echinacea Plant Named 'BullEchipur 115'
- RESISTIVE MEMORY CELL WITH SWITCHING LAYER COMPRISING ONE OR MORE DOPANTS
This application is a continuation of U.S. patent application Ser. No. 09/692,997, filed Oct. 20, 2000, which is a continuation of application Ser. No. 09/263,148, filed Mar. 5, 1999, now abandoned.
FIELD OF INVENTIONThis invention relates to computer systems and more specifically to embedded systems, i.e. other than general purpose programmable computers.
BACKGROUNDEmbedded systems are well known; this refers to microprocessors and microcontrollers (hereinafter generically referred to as microprocessors) used in devices other than general purpose computers. For instance many household appliances (such as microwave ovens) have embedded microprocessors which control operation of the appliance. The microprocessor typically accepts user input, for instance from the keypad of the microwave oven, and controls operation of the microwave oven, for instance the level of heating and duration of cooking. The embedded microprocessor also controls the device display which in a microwave oven is a small LCD (liquid crystal display). That is, the intelligence of such appliances resides in the embedded microprocessor, which interfaces to the human user. Typically this is done through firmware, i.e. computer software executed by the embedded microprocessor and stored in a memory associated with, or a part of, the microprocessor. In addition to executing the software to interact with the controlled device, the embedded microprocessor also accepts and decodes input from the human user, for instance via the keypad, as well as provides visual feedback on the display by providing text and/or graphic information to a display controller which in turn drives the LCD panel.
As shown in the block diagram of
As shown, the microprocessor 10 is coupled to a user input device 14, e.g. a keypad, an infrared remote controller such as used on television sets, or a touch screen input device. The associated controlled device (not shown) is, for instance, an appliance such as a microwave oven, washing machine, or automobile system, or a scientific instrument, or a machine tool, and is connected conventionally to microprocessor 10. It is to be appreciated that the lines connecting the blocks in
The
In accordance with this invention, a control system, for instance an embedded control system for controlling a device, operates such that the burden of accepting human user (or machine) input and providing information (output) to a human user or a machine via, e.g., a display is shifted from the embedded microprocessor to a second processor. The second processor, designated here a “hypertext” processor, is e.g. a microprocessor, microcontroller, or similar structure capable of processing a hypertext markup language document, as explained below. The embedded control system controls and/or monitors the controlled device and is application specific, unlike for instance a personal computer which can run any application program. The display controller of
The hypertext processor determines what operations to take upon receipt of, e.g., user input, for instance from a connected keypad. The hypertext processor performs actions described in the hypertext markup language document and commands the embedded microprocessor to act on the controlled device and to update its internal shared variables. The hypertext processor also updates the display as a function of the shared variables internal to the embedded microprocessor. The user interface software (code) is not resident in the hypertext processor, nor is it executed/interpreted by the embedded microprocessor. Instead, a (hypertext) document describing the user interface is external to the hypertext processor, and resident in the memory space of the embedded microcontroller or in a serial memory device (i.e. serial EEPROM, FLASH ROM, smart card, etc.). This hypertext document describing the user interface is provided (“served”) to the hypertext processor at the request of the hypertext processor. Thus the user interface is actually executed by the hypertext processor even though it does not permanently reside there.
In one embodiment, the user interface document is encoded in a particular hypertext markup language (HTML) called here μGHTML. The generic name “Hypertext Markup Language” refers to: Hypertext—A method for providing links within and between documents; popularized by multimedia authoring systems which used the hypertext concept to link the content of a text document to other documents encoded in certain multimedia formats. Markup Language—A method for embedding special control codes (TAGS) that describe the structure as well as the behavior of a document.
Like conventional HTML, PHTML files (“documents”) contain both control information (markup tags) and content (ASCII text), which together describe the appearance and content of a user interface. In addition, both markup languages provide capability to reference resources external to the document. Compared to conventional HTML, μHTML is smaller, easier to interpret, and defines a special library of GUI (graphical user interface) objects, data processing objects suitable for pipelining, and other system utilities common to embedded systems software. One key feature of μHTML is its ability to describe the interface to resources distributed among networked embedded subsystems and to link the data of these resources to the functions of a host processor.
In order to make μHTML easy to parse, it is headed by a directory of pointers to each tag. To make it compact, each tag is represented by a single byte (hereinafter referred to as an opcode). Following each opcode is a unique set of binary properties data, such as X-Y coordinate information, pointers to other resources, and other properties. There is a unique opcode for each object in the GUI object library. These objects are, e.g., push buttons, pop-up lists, and other sorts of visual (or aural) indicators. There are also opcodes for objects that contain methods to process or redirect data to and from other objects or external resources, e.g., an object referencing a variable from “external resource 0” may sample the variable data every 100 mS, and route the results to another object referencing a variable from “external resource 1”. Each library object opcode is followed immediately by a data structure unique to the object. The data contained in the data structure is specific to the instance of the library object. In this way, the memory allocated for each instance of all used objects is statically allocated in the memory buffering the μHTML document. When external resources are referenced, a data structure is provided to describe the format of the messages required to provide access to the external resource. For instance, to read a variable associated with an external device, the data structure describes a “Get” command and a “Return” response. Typically the Get command contains an identification to some external device and an index into a lookup table on the external device that provides references to variables, functions or files. In addition to the external device identification and lookup table index, the Return response also contains the data requested.
In one embodiment this user interface hypertext document is developed using conventional internet web page development tools of the type commercially available; this is not limiting. User interface objects are simulated in one embodiment with JAVA applets that correspond to objects in the GUI object library. The simulated GUI objects are referenced from within the conventional HTML document by using the same standard tags used to reference any conventional JAVA applet. Standard HTML tags are also used to format the display content and to point to resources resident to devices external to the hypertext processor.
The user interface document can then be viewed on a conventional web browser, for system development purposes. (Of course this has little to do with the actual user operation of the controlled device but is part of its user interface design and development.) This HTML/JAVA web page can then be converted (pre-compiled) to a more compact μHTML format by a compiler designed specifically to: (1) remove the conventional HTML tags and replace them with a corresponding μHTML opcode; (2) convert the attributes strings of the HTML tags to a binary structure appropriate for the μHTML opcode; (3) replace references to all JAVA applets and parameters with a corresponding opcode and object data; (4) reformat and add additional data to simplify parsing and execution by the hypertext processor, and (5) resolve references to resources external to the hypertext processor (i.e. executable code or variable data resident to an external embedded microprocessor, storage in an external serial memory device, I/O functions of an external serial I/O device, etc.). This is only illustrative of development of a system in accordance with this invention.
Moreover, the present invention is directed to more than a user interface processor. It is additionally directed to use of a hypertext markup language to provide program flow and structure while linking together resources distributed among embedded subsystems, even if the subsystems do not have user interfaces. That is, the invention more broadly contemplates a dedicated processor programmed with a hypertext markup language rather than with conventional application code.
BRIEF DESCRIPTION OF THE FIGURES
Although
Also, while the various blocks 30, 40, 20, 22, and 42a, 42b etc. of
The following describes each functional block of the hypertext processor 40 of
Network controller 58 formats and transmits all bytes of data queued by the μHTML processor 60 via the network 46. It also decodes any data received from the network 46 and places it in a queue to be processed by the μHTML processor 60.
User input decoder 62 detects and decodes input from user input device 14 which is, e.g., a keypad, touch screen, voice command decoder or IR (infrared) remote device. Decoder 62 places data describing a user input event into a queue to be processed by the μHTML processor 60.
μHTML processor 60 operates on data stored in μHTML buffer 64 to reflect events queued from the user input decoder 62 and network controller 58. Processor 60 is also responsible for generating and queuing events for the network controller 58 in response to system or user events that are linked to such events by the data in the μHTML buffer 64.
μHTML buffer 64 is RAM (random access memory) storage for a complete μHTML document describing all objects to be rendered to the display device 20. Each object contained in the μHTML document may also contain references to other network resources. Buffer 64 is only written to and modified by the μHTML processor 60 in response to user input events, system events or events generated in response to network messages. It is read by both the rendering engine 52 and the μHTML processor 60. μHTML buffer 64 is a section of RAM 72 accessible only by the microprocessor 68 (see
The rendering engine 52 only reads the graphic information for each UI object as required to properly draw the user interface to the frame buffer 30. The μHTML processor 60 reads the information required to generate system or network events in response to other events related to each UI object.
Rendering engine 52 draws all displayable user interface objects to the frame buffer 30 as described by the data stored in the μHTML buffer 64. It refreshes each UI object when marked as “dirty” in the μHTML buffer 64 by the μHTML processor 60. Rendering engine 52 is firmware executed by microprocessor 68 and stored in ROM 70 (see
Frame buffer 30 is RAM storage that contains the data for each pixel of the entire displayed page. It is written to by the rendering engine 52 as it draws the user interface on display 20. It is read from by the pixel serializer 36 as it converts the pixel information to signals appropriate to drive the physical display 20. Frame buffer 30 of
Pixel serializer 36 generates a continuous pixel stream in a format compatible with a specific commercially available physical display 20. As an example, when interfacing to an LCD panel (display 20), the pixel serializer collects and formats each line of pixel data from the frame buffer 30 and synchronizes it with the conventional display driver pixel clock, frame pulse and line pulse signals. The pixel clock signal clocks the pixel data into the display drivers' internal shift register. The line pulse signal indicates the end of a display line while the frame pulse signal marks the first line of the displayed page.
The
This eliminates the conventional programming, for example in assembler or C, required to implement graphical user interface objects that are linked to the variables and functions of the embedded microprocessor 10 such as is required in the prior art system of
The user input decoder 62 is shown in
μHTML Processor 60 of
The structures in
The block diagrams of
The embedded microprocessor resident resources accessed by program 92 are: two variables in this case containing the values 123 and 321, and two functions that in this case turn on an LED and turn off an LED attached to the embedded microprocessor. The variables are displayed via IntField objects and accessed by sending the commands in the <PARAM Name=“Send” . . . > tags. Upon receiving the command to GET a variable, the embedded processor executes the code in 92 to lookup the variable and send the value back via the ackClient routine. The IntField object of the markup language processors GUI Object library parses the response as per the <PARAM Name=“Return” . . . > tag to isolate, format and render the value to the LCD's frame buffer.
Likewise the functions referenced by the <PARAM Name=“Send” . . . > are invoked when the user activates the buttons rendered by the FunctBtn objects.
Associated with this document 86 is embedded request handler 92, shown in the right hand portion of
Alternatives to use of the μHTML disclosed here are other forms of text documents with control codes used to access resources located elsewhere. Examples of other markup languages are compact HTML, and HDML. Even the old UNIX “troff” is a markup language which was originally designed for page layout.
Memory devices (such as 42c) (
The embedded memory device 42c is thereby responsible for “hosting” the μHTML and other files. It responds to requests from the hypertext processor and keeps track of changes to variables in use by the hypertext processor and executes the controlled device functionality. The hypertext processor is responsible for rendering the graphical user interface to the display. The hypertext processor is also responsible for responding to user input from the user input device by updating display graphics and communicating with external devices to request changes to the values of external variables and to invoke external functions as described by the μHTML document. The hypertext processor is also responsible for responding to changes in the embedded microprocessor variables by updating the display device graphics. Typical requests to the embedded microprocessor by the hypertext processor are: open connection; get file (for instance a μHTML file, an image graphic file or a script); call up functions; get a value of the variable; send value of the variables and obtain status of the embedded microprocessor. “Script” refers here to files that contain code to be executed by the microprocessor portion of the hypertext processor.
This disclosure is illustrative and not limiting; further modifications will be apparent to one skilled in the art in light of this disclosure and are intended to fall within the scope of the appended claims.
Claims
1-17. (canceled)
18: A method for programming a graphic user interface (“GUI”) implemented by a first controller for a device independently from a second controller that monitors and controls the device, the method comprising:
- creating a HTML page defining an appearance of the GUI, said creating comprising: selecting an applet code of a GUI object and arranging the applet code on the HTML page; setting a source or a destination of a parameter of the GUI object;
- compiling the HTML page, comprising replacing the applet code with an operation code (“opcode”) identifying the GUI object; setting an operand identifying the source or the destination of the parameter of the GUI object;
- loading the compiled HTML page into at least one memory in the device, wherein in response to the opcode and the operand, the GUI controller executes executable codes in at least one memory to communicate the parameter with the source or the destination and to render the GUI object in response to the parameter.
19: The method of claim 18, wherein said communicating the parameter with the source comprises receiving a status of the device from the second controller.
20: The method of claim 18, wherein said communicating the parameter with the destination comprises sending a user command to the second controller.
21: The method of claim 20, further comprising executing the executable codes to receive the user command from an input device.
22: A first controller providing a graphical user interface (“GUI”) for a device independently from a second controller that monitors and controls the device, the first controller comprising:
- at least one memory comprising: a document buffer storing a document, the document comprising an operation code (“opcode”) identifying a GUI object in the GUI and an operand identifying a parameter of the GUI object, the GUI object being a graphical presentation of the parameter, the parameter being from the second controller; a frame buffer for storing at least one complete frame of the GUI including the GUI object; a GUI object library storing executable codes defining an appearance and a functionality of the GUI object, the executable codes comprising instructions for receiving non-graphical data of the parameter from the second controller and rendering the GUI object in response to any change to the parameter;
- a processor coupled to the second controller and the at least one memory, wherein the processor (1) reads the opcode and the operand, (2) reads the executable codes, (3) executes the executable codes to (a) receive the non-graphical data of the parameter from the second controller and (b) render the GUI object in response to any change to the parameter independently from the second controller, and (4) saves the rendered GUI object in the frame buffer.
23: The first controller of claim 22, further comprising an output device coupled to the frame buffer to receive the GUI, the output device displaying the GUI to the user.
24: The first controller of claim 23, wherein the output device is a liquid crystal display (“LCD”).
25: The first controller of claim 24, further comprising a pixel serializer coupled between the frame buffer and the LCD, the pixel serializer outputting each line of the GUI in the frame buffer to the LCD.
26: The first controller of claim 22, wherein the parameter is a status of the device from the second controller to the user.
27: The first controller of claim 26, wherein the GUI object is a text field.
28: The first controller of claim 22, further comprising another memory coupled to the processor, the another memory storing the document, the processor loading the document from the another memory to the at least one memory.
29: The first controller of claim 22, wherein the second controller further comprises another memory storing the document, the second controller reading the document from the another memory and sending the document to the first controller, the first controller loading the document in the at least one memory.
30: A method for a first controller to generate a graphic user interface (“GUI”) for a device independently from a second controller that monitors and controls the device, the method comprising:
- loading a document into a document buffer in at least one memory, the document defining an appearance of the GUI, the document comprising an operation code (“opcode”) identifying a GUI object and an operand identifying a parameter of the GUI object, the GUI object being a graphical presentation of the parameter, the parameter being from the second controller;
- in response to the opcode and the operand, retrieving executable codes of the GUI object from a GUI object library stored in the at least one memory, the executable codes defining an appearance and a functionality of the GUI object, the executive code comprising instructions for receiving non-graphical data of the parameter from the second controller and rendering the GUI object in response to any change to the parameter;
- independently from the second controller, executing the instructions to receive the non-graphical data of the parameter from the second controller and to render the GUI object in response to any change to the parameter;
- writing the rendered GUI object in a frame buffer in the at least one memory; and
- sending the rendered GUI object from the frame buffer to an output device, wherein the output device displays the GUI to a user.
31: The method of claim 30, wherein the output device is a liquid crystal display (“LCD”).
32: The method of claim 30, wherein the parameter is a status of the device from the second controller to the user.
33: The method of claim 32, wherein said rendering the GUI object comprises drawing a text field.
34: The method of claim 30, further comprising reading the document from another memory prior to said loading the document into the at least one memory.
35: The method of claim 30, further comprising receiving the document from the second controller prior to said loading the document into the at least one memory.
36: A first controller providing a graphical user interface (“GUI”) for a device independently from a second controller that monitors and controls the device, the first controller comprising:
- at least one memory comprising: a document buffer storing a document, the document comprising: an operation code (“opcode”) identifying a GUI object in the GUI, the GUI object being a graphical presentation of a user input, the user input being from an input device; and an operand identifying a destination of the user input, the destination being the second controller; a frame buffer for storing at least one complete frame of the GUI including the GUI object; a GUI object library storing executable codes defining an appearance and a functionality of the GUI object, the executable codes comprising instructions for (1) receiving the user input from the input device, (2) rendering the GUI object in response to any change to the user input, and (3) sending non-graphical data of the user input to the second controller;
- a processor coupled to the input device, the second controller, and the at least one memory, wherein the processor (1) reads the opcode and the operand, (2) reads the executable codes, (3) executes the executable codes to (a) receive the user input from the input device, (b) render the GUI object in response to any change to the user input independently from the second controller, and (c) send the non-graphical data of the user input to the second controller, and (4) saves the rendered GUI object in the frame buffer.
37: The first controller of claim 36, further comprising an output device coupled to the frame buffer to receive the GUI, the output device displaying the GUI to the user.
38: The first controller of claim 37, wherein the output device is a liquid crystal display (“LCD”).
39: The first controller of claim 38, further comprising a pixel serializer coupled between the frame buffer and the LCD, the pixel serializer outputting each line of the GUI in the frame buffer to the LCD.
40: The first controller of claim 36, wherein the input device is one of a touch screen, a key pad, an infrared remote, and a voice decoder.
41: The first controller of claim 40, wherein the GUI object is one of a button and a list.
42: The first controller of claim 36, further comprising another memory coupled to the processor, the another memory storing the document, the processor loading the document from the another memory to the at least one memory.
43: The first controller of claim 36, wherein the second controller further comprises another memory storing the document, the second controller reading the document from the another memory and sending the document to the first controller, the first controller loading the document in the at least one memory.
44: A method for a first controller to generate a graphic user interface (“GUI”) for a device independently from a second controller that monitors and controls the device, the method comprising:
- loading a document in a document buffer in at least one memory, the document defining an appearance of the GUI, the document comprising: an operation code (“opcode”) identifying a GUI object in the GUI, the GUI object being a graphical presentation of a user input, the user input being from an input device; and an operand identifying a destination of the user input, the destination being the second controller;
- in response to the opcode and the operand, retrieving executable codes of the GUI object from a GUI object library stored in the at least one memory, the executable codes defining an appearance and a functionality of the GUI object, the executable codes comprising instructions for (1) receiving the user input from the input device, (2) rendering the GUI object in response to any change to the user input, and (3) sending non-graphical data of the user input to the second controller;
- independently from the second controller, executing the instructions to (1) receive the user input from the input device, (2) render the GUI object in response to any change to the user input, and (3) send the non-graphical data of the user input to the second controller;
- writing the rendered GUI object in a frame buffer in the at least one memory; and
- sending the rendered GUI object from the frame buffer to an output device, wherein the output device displays the GUI to a user.
45: The method of claim 44, wherein the output device is a liquid crystal display (“LCD”).
46: The method of claim 44, wherein the input device is one of a touch screen, a key pad, an infrared remote, and a voice decoder.
47: The method of claim 46, wherein said rendering the GUI object comprises drawing one of a button and a list.
48: The method of claim 44, further comprising reading the document from another memory and loading the document in the at least one memory.
49: The method of claim 44, further comprising receiving the document from the second controller and loading the document in the at least one memory.
Type: Application
Filed: Aug 9, 2006
Publication Date: May 10, 2007
Applicant:
Inventor: Kenneth Klask (San Jose, CA)
Application Number: 11/502,071
International Classification: G06F 17/00 (20060101);