Electrical computers and digital processing systems: multicomput – Network computer configuring
Reexamination Certificate
2000-01-31
2002-01-22
Geckil, Mehmet B. (Department: 2152)
Electrical computers and digital processing systems: multicomput
Network computer configuring
C709S203000
Reexamination Certificate
active
06341307
ABSTRACT:
BACKGROUND OF THE INVENTION
1. Technical Field
The invention relates to the transfer of information across a plurality of dissimilar display devices. More particularly, the invention relates to a generic information interface architecture for transferring display information from a server to a plurality of dissimilar display devices, thereby allowing the server to ignore the attributes of each particular display device.
2. Description of the Prior Art
Computer system applications that require user interaction communicate information through devices such as Liquid Crystal Displays (LCDs), Light Emitting Diode (LED) displays, plasma displays, and cathode ray tubes (CRTs). Each display type requires a specialized driver to control any graphical representations on the display. The graphical representations may be very simple, one-line messages, e.g. “Self Test,” to very complicated graphical user interfaces (GUIs).
A software developer must create source code that is custom tailored for each display with which his application communicates. Typically, a library is created that represents all of the allowable graphic primitives on the screens that are displayed on the chosen display. The library contains information such as the screen creation primitives, button labels, user messages, blink characteristics, and headings. Built on top of the library is a module containing all of the screen descriptions. The library and screen description module are written in the programming language, e.g. “C,” that the software developer is using and customized for the type of display, e.g. a one, two, or five-line LCD display, or a GUI display. The differences between a two-line and a five-line LCD display is the amount of information that can be displayed. A two-line LCD display is limited in the amount of text that can be displayed to the user as compared to a five-line LCD display. A GUI display has much more display area than a line-limited LCD display. It can display on one screen, information that would require several screens on a line-limited LCD display. The source code is then compiled with the application source code and delivered as part of the final product.
This hard coding of display screens requires that new source code be created and compiled into the application software whenever a new display device is selected. The source code for each display type must be archived and maintained for the life of each display device. This is a cumbersome and expensive task, e.g. there are N different source codes for N different display devices used.
U.S. Pat. No. 4,787,035 issued to Bourne on Nov. 22, 1988, discloses a system which uses an interpreter that examines messages using grammar and lexical tables to produce a parse table. The parse table is compared to data needed in a semantics table to fire a rule which causes a function table to be evaluated and performs user desired functions. This is particularly suitable for manufacturing systems with multiple target languages.
If the product is one that is used by an Original Equipment Manufacturer (OEM), the OEM usually requires custom displays to differentiate their product from the other OEMs using the same base application. For an OEM engineer to create his custom displays, he must know the internal structure of the application's software. Revealing such information is many times a sensitive issue. The originating company would prefer to keep such internal software structures confidential in an attempt to retain their value as a product supplier to any OEM.
It would be advantageous to provide a display interface system that allows the developer to create a single set of screen descriptions that is used for all supported display types. It would further be advantageous to provide a display interface system that is independent of the display location, i.e. whether the display is embedded in the system or network accessible.
SUMMARY OF THE INVENTION
The invention provides a display interface system that has a generic architecture and is thereby independent of the supported display type. The invention uses a generic language approach that is independent of the type of display chosen and its location in relation to the generic code generator.
The invention uses a server-client approach. The server contains all of the necessary information regarding display information, while the client deals with the specific display type to which it is connected. The server allows a software developer to create generic descriptions of user interface screens. The generic screen descriptions allow the server to be independent of specific display types. This allows one version of software to support many types of displays, rather than several software versions for each display type. The software developer saves on time, maintenance, and labor costs.
A request-response communication system is used whereupon the client, acting as the user interface, requests previous or next user display screens, system parameter requests or updates from the server. Thus, the user interface function is offloaded from the server. The client requests screen information through a series of key-tag sequences. User display screen sequencing is controlled by the server. The concept of user display screens is known only to the server. The client is shielded from any knowledge of the contents of the screen and is only concerned with the fact that something is being displayed.
Communication between the server and client is through a unified protocol. The server-client approach, combined with the unified protocol, allows the client to be located either locally, in the same machine or remotely, across a network.
REFERENCES:
patent: 4558413 (1985-12-01), Schmidt et al.
patent: 4787035 (1988-11-01), Bourne
patent: 4860247 (1989-08-01), Uchida et al.
patent: 5045994 (1991-09-01), Belfer et al.
patent: 5289574 (1994-02-01), Sawyer
patent: 5315711 (1994-05-01), Barone et al.
patent: 5327529 (1994-07-01), Fults et al.
patent: 5388252 (1995-02-01), Dreste et al.
patent: 5539872 (1996-07-01), Mintz et al.
patent: 5715444 (1998-02-01), Danish et al.
patent: 5734852 (1998-03-01), Zias et al.
patent: 5748189 (1998-05-01), Trueblood
patent: 5768614 (1998-06-01), Takagi et al.
patent: 5815148 (1998-09-01), Tanaka
patent: 5854936 (1998-12-01), Pickett
patent: 5883613 (1999-03-01), Iwaki
patent: 5897635 (1999-04-01), Torres et al.
patent: 5950011 (1999-09-01), Albrecht et al.
patent: 6065041 (2000-05-01), Lum et al.
patent: 0333612 (1989-09-01), None
patent: 0684547 (1995-11-01), None
patent: WO95/15524 (1995-06-01), None
Guan Zhengo (Mark)
Lum Lambert Chun-Bob
Schwarz, Jr. James K.
Seidel Craig
Electronics for Imaging, Inc.
Geckil Mehmet B.
Glenn Michael A.
LandOfFree
Interface code architecture does not yet have a rating. At this time, there are no reviews or comments for this patent.
If you have personal experience with Interface code architecture, we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Interface code architecture will most certainly appreciate the feedback.
Profile ID: LFUS-PAI-O-2832089