System and method of verifying graphically displayed relative information

[0002] The present invention is related to the following commonly assigned and co-pending U.S. applications:

[0003] “System and Method of Graphically Displaying Relative Information By An Electronic Price Label”, filed May 14, 1999, invented by Goodwin, and having a Ser. No. 09/312,458, now abandoned; and

[0004] “Electronic Price Label and Method of Graphically Displaying Relative Information By An Electronic Price Label”, filed, May 14, 1999, invented by Goodwin, and having a Ser. No. 09/312,457.

[0005] The present invention relates to electronic price label (EPL) systems, and more specifically to a system and method of graphically displaying relative information by an EPL.

[0006] EPL systems typically include a plurality of EPLs for merchandise items in a transaction establishment. EPLs typically display the price of corresponding merchandise items on store shelves and are typically attached to a rail along the leading edge of the shelves. A transaction establishment may contain thousands of EPLs to display the prices of the merchandise items. The EPLs are coupled to a central server from where information about the EPLs is typically maintained in an EPL data file. Price information displayed by the EPLs is obtained from a price look-up (PLU) data file and stored within an EPL price change record.

[0007] EPLs typically include liquid crystal displays (LCDs) for displaying information. A typical EPL may include an LCD capable of displaying a minimum of eight characters of alphanumeric text information. Each character includes a number of segments which are turned on or off to generate a character. EPLs may also include icons for displaying limited amounts of graphical information about a product.

[0008] In order to obtain a competitive advantage, retailers must effectively market their products and have access to information about their products. For example, inventory and sales figures are important in running a retail business. The type and frequency of information may vary based upon job description. A stock person typically needs “daily quantities sold” information. A person placing orders needs another type of information, “what is in stock” and “what is on order” information. A manager needs another type of information, “how does this item rank against others” information.

[0009] Access to employee-directed competitive information is typically available only through a centralized in-store computer. Thus, to determine business information about items, employees get the information directly from the computer or from reports generated by the computer.

[0010] Therefore, it would be desirable to display competitive, promotional, and other relative information anywhere in a transaction establishment through an electronic price label system.

[0011] In accordance with the teachings of the present invention, a system and method of graphically displaying relative information by an electronic price label (EPL) is provided.

[0012] An electronic price label relative information verification system which ensures that first business information for an item is equal to second business information assigned to the electronic price label for display. The system includes a computer system coupled to the electronic price label, including a terminal and a storage medium coupled to the terminal. The storage medium contains a data record for the item, which contains identification information and a verifier for the item. The computer terminal obtains the first relative information for the item from the business information source, calculates another verifier from the first relative information for the item, reads the data record to obtain the one verifier, compares the one and the other verifiers to determine whether they are equal, and changes displayed business information to the first relative information if the one and the other verifiers are different.

[0013] The method includes reading a data record for the electronic price label to obtain an identification information number for the item and a verifier, obtaining the first relative information from the business information source using the identification information obtained from the data record, calculating another verifier from the first business information, comparing the one and the other verifiers to determine whether they are equal, and changing displayed relative information to the second relative information if the one and the other verifiers are different.

[0014] It is accordingly an object of the present invention to provide a system and method of graphically displaying relative information about a product associated with an EPL by the EPL.

[0015] It is another object of the present invention to provide a system and method of verifying graphically displayed relative information.

[0016] It is another object of the present invention to provide a system and method of verifying graphically displayed employee-directed business information.

[0017] Additional benefits and advantages of the present invention will become apparent to those skilled in the art to which this invention relates from the subsequent description of the preferred embodiments and the appended claims, taken in conjunction with the accompanying drawings, in which:

[0018] FIG. 1 is a block diagram of a first embodiment of a transaction processing system;

[0019] FIG. 2 is a diagram showing data files used within the transaction establishment of FIG. 1;

[0020] FIG. 3 is a block diagram of a second embodiment of the transaction processing system;

[0021] FIG. 4 is a diagram showing data files used within the transaction establishment of FIG. 3;

[0022] FIG. 5 illustrates several display segments or icons used to display relative business information;

[0023] FIG. 6 is a block diagram of a system for producing a file reader program;

[0024] FIG. 7 is a flow diagram illustrating how the file reader is created;

[0025] FIG. 8 is a flow diagram illustrating the operation of the file reader program; and

[0026] FIG. 9 is a flow diagram illustrating the operation of a data verifier program.

[0027] Referring now to FIG. 1, a first embodiment of transaction system 10 primarily includes host computer system 12, point-of-sale (POS) system 14, EPL system 16, and business information system 18. Here, components 12, 14, 16, and 18 are shown as separate components that are networked together, but they may also be combined in different ways to form less components. Thus, host computer system 12 may be a POS terminal which doubles as a host computer for network of other POS terminals. Also, host computer system 12 and business information system 18 may be combined into a single system.

[0028] POS system 14 includes bar code reader 19 and terminal 20.

[0029] EPL system 16 primarily includes EPLs 22, host EPL terminal 24, and EPL storage medium 26.

[0030] EPLs 22 include control circuitry 52, data registers 54 and displays 56.

[0031] Control circuitry 52 receives and transmits messages from EPL terminal 24 and controls display of information by display 56. Control circuitry 52 stores data within the messages, such as price, promotional, and relative business information, in data registers 54.

[0032] Under the present invention, relative business information is displayed in portion 58 while price information is displayed in second portion 59, but both types of information may be combined into a single data message prior to transmission to EPL 22.

[0033] Host EPL terminal 24 executes EPL software 30. To assist with execution of certain tasks performed by EPL software 30, EPL terminal 24 includes a built-in time keeping device, commonly referred to as a system clock, which is synchronized with current time, in order to automatically execute the tasks at their scheduled times.

[0034] EPL software 30 is responsible for scheduling and transmitting data to EPLs 22. EPL software 30 obtains prices in price look-up (PLU) data file 46 as they are entered in input device 40 or after they have been stored within PLU data file 46. Similarly, EPL software 30 obtains business information in business information data file 66 as it is entered in input device 60 or after it has been stored within business information data file 66.

[0035] EPL terminal 24 also executes EPL data verifier software 34, which is responsible for verifying that prices displayed by EPLs 22 for items stored within EPL data file 32 are the same as prices for those items contained within PLU data file 46. EPL data verifier software 34 is also responsible for verifying that business information displayed by EPLs 22 is the same as data for the items contained within business information data file 66. EPL data verifier software 34 combines business information from business information data file 66 with price data from PLU data file 46 into a single checksum entry in EPL data file 32.

[0036] Host EPL terminal 24 executes application programming interface (API) 33, which has hooks to operating system 50 or transaction software 31. For example, a commercially-available API exists for the UNIX and OS/2 operating systems of Novell and IBM, and the UNITY POS software of NCR Corporation. Data verifier software 34, as well as other independent applications, have hooks to API 33.

[0037] Host EPL terminal 24 also executes file reader 38, which is compiled to run on operating system 50 or on transaction software 31, depending on the needs of the transaction establishment. File reader 38 directly accesses PLU information in PLU data file 46 and business information data file 66, as an alternative to maintaining local duplicates of PLU data file 46 and business information data file 66.

[0038] File reader 38 is linked to API 33 through interprocess communications and includes file reading routine 43 which works with API 33 to cause transaction software 31 or operating system 50 to read PLU data file 46 and business information data file 66 and transfer PLU information and business information to data verifier software 34.

[0039] EPL storage medium 26 stores EPL data file 32. EPL storage medium 26 and is preferably a fixed disk drive.

[0040] EPL data file 32 contains EPL identification and checksum information. Checksum information is calculated from price information in PLU data file 46 and business information in business information data file 66. EPL data file 32 contains current information displayed by EPLs 22.

[0041] Host computer system 12 includes PLU storage medium 44, transaction server 42, and input device 40.

[0042] Transaction server 42 handles price requests from POS terminal 20. POS terminal 20 sends item identification information to transaction server 42 and transaction server 42 returns the corresponding price from PLU data file 46.

[0043] PLU storage medium 44 stores PLU data file 46. PLU data file 46 is available for distribution to POS terminal 20. Provision may be made for direct access to PLU data file 46 by bar code reader 19.

[0044] Input device 40 is preferably a keyboard.

[0045] Business information system 18 includes business information storage medium 64, business information server 62, and input device 60.

[0046] Business information server 62 manages employee-directed business information.

[0047] Business information storage medium 64 stores business information data file 66. Business information data file 66 may be a database, data warehouse, plan-o-gram database, in-store data file, or other source of business information. Business information in business information data file 66 is available for distribution to EPL system 16.

[0048] Input device 60 is preferably a keyboard.

[0049] Turning now to FIG. 2, EPL data file 32, PLU data file 46, and business information data file 66 are shown in more detail.

[0050] EPL data file 32 includes a line entry for each EPL 22 in EPL system 16. Each line entry has an item identification entry (ITEM ID), an EPL identification entry (EPL ID), and an EPL checksum value entry (EPL CHECK).

[0051] Entry ITEM ID identifies a store item. Entry EPL ID identifies which EPL is assigned to the item. Entry EPL CHECK is a checksum value of the digits of the combined price and business information that is displayed by display 56.

[0052] PLU data file 46 includes a line entry for each item sold in the transaction establishment. Each line entry should have at least an item identification entry (ITEM ID) and a PLU price entry (PLU PRICE).

[0053] Entry ITEM ID identifies a store item. Entry PLU PRICE identifies the price read by POS system 14 to determine the price of each item during scanning by bar code reader 19.

[0054] Business information data file 66 includes a line entry for items sold in the transaction establishment. Each line entry has an item identification entry (ITEM ID) and may have a business information entry (RELBUS).

[0055] Entry ITEM ID identifies a store item. Entry RELBUS could be an entry which identifies the relative profitability of the item. Profit, sales dollars, sales quantity (daily, monthly, quarterly, or last year, etc.), quantity on order, quantity in stock, and quantity to stock are all examples of different types of business information. Entry RELBUS may be modified, or if additional entries are present, a primary entry for display may be designated in business information data file 66. Business information can come from one or more files, for example, sales data from one file, quantity on order from another, and history data from another, etc.

[0056] During normal operation, EPL data verifier software 34 executes file reader 38 to obtain price information from PLU data file 46 and business information from business information data file 66. EPL data verifier software 34 combines the price and business information into display data and causes EPL software 30 to send the display data to an EPL 22. EPL 22 receives the display data, stores the display data in data registers 54, and causes display 54 to display the display data. Display 56 displays the price information in portion 59 and the business information in portion 58.

[0057] During a mismatch situation, the price information from PLU data file 46 does not agree with the price displayed by EPL 22 and/or the business data from business information data file 66 does not agree with the business information displayed by EPL 22. EPL data verifier software 34 combines a price for the item from PLU data file 46 with business information for the item from business information data file 66, creates a checksum of the combined data, and compares the checksum with the previously created checksum stored within EPL data file 32. If the checksums do not match, then EPL data verifier software 34 sends the new price and business data to EPL 22 with a command to display the new price and business data.

[0058] Referring now to FIG. 3, a second embodiment of transaction system 10 is similar to the first embodiment, except that it does not include a separate business information system. Under the second embodiment, business information is stored within PLU data file 46.

[0059] EPL software 30 obtains prices and relative business information in PLU data file 46 as they are entered in input device 40 or after they have been stored within PLU data file 46.

[0060] As in the first embodiment, EPL data verifier software 34 uses file reader 38 to obtain price information and business information, except that file reader 38 obtains both price and business information from PLU data file 46.

[0061] Turning now to FIG. 4, EPL data file 32 and PLU data file 46 are shown in more detail.

[0062] EPL data file 32 includes the same line entries as in FIG. 2.

[0063] PLU data file 46 combines the PLU data file 46 of FIG. 2 with the business information data file 66 of FIG. 2. PLU data file 46 includes a line entries ITEM ID, PLU PRICE, and at least one business information entry RELBUS.

[0064] During normal operation, EPL data verifier software 34 executes file reader 38 to obtain price and business information from PLU data file 46. EPL data verifier software 34 combines the price and business information into display data and causes EPL software 30 to send the display data to an EPL 22. EPL 22 receives the display data, stores the display data in data registers 54, and causes display 54 to display the display data. Display 56 displays the price information in portion 59 and the business information in portion 58.

[0065] During a mismatch situation, EPL data verifier software 34 operates as in the first embodiment. EPL data verifier software 34 combines price and business information from PLU data file 46, creates a checksum of the combined data, and compares the checksum with the previously created checksum stored within EPL data file 32. If the checksums do not match, then EPL data verifier software 34 sends the new price and business data to EPL 22 with a command to display the new price and business data.

[0066] Turning now to FIGS. 5A-D, a plurality of different ways of graphically displaying relative business information are illustrated. In each embodiment, display portion 58 includes a plurality of display segments or icons which convey relative level or degree information. These display segments or icons are arranged linearly to form a scale or level indicator. As the level of a predetermined business measure increases, the number of activated display segments or icons increase.

[0067] The level information is obtained from business information data in either business information data file 66 or PLU data file 46 and transmitted to EPL 22 with price information. Entry RELBUS contains a list of segments to be activated in order to convey the relative business information for the business measure displayed. An operator modifies this list as the level information changes. The list can also be generated automatically as the level information changes. The display can change meaning by day of week and time of day.

[0068] As business information system 18 updates its level information, it can be passed to EPL system 16 to automatically update the displayed information. Data verifier 34 would be scheduled to run as often as business information system 18 updates its level data. Each change in level information requires that a new message be sent to EPL 22. Data verifier 34 detects the changes and initiates new messages.

[0069] In FIG. 5A-B, display portion 58 includes three segments 58A-C of increasing size which are activated as the predetermined business measure increases. Thus, none of segments 58A-C are activated when the business measure is at a minimum value, while all three segments 58A-C are activated when the business measure is at a maximum value.

[0070] In FIG. 5C, display portion 58 includes five icons 58A-E of equal size arranged in a line.

[0071] In FIG. 5D, display portion 58 includes nine display segments 58A-I of increasing size surrounded by rectangular markings on display 56 which divide the nine display segments into three equal size groups 58J-L arranged in a line.

[0072] In FIGS. 5A-D, portion 59 includes price information, including unit price and total price information, or a promotional message, such as “On Sale”.

[0073] Turning now to FIG. 6, the components that are used to construct file reader 38 include template PLU file reader 80, object code 82, example mappings and translations 84, target routines 86, and make files 88. Template PLU reader 80 is a super set of example mappings and translations 84 and target routines 86. Example mappings and translations 84 and target routines 86 are edited and customized by developers to produce customized mappings and translations 85 and customized target routines 87 (customized template 81). File reading routine 43 is an example of a customized target routine. Customized mappings and translations 85 and customized target routines 87 along with object code 82 are fed into make files 88 in order to produce executable code for a file reader 38.

[0074] Object code 82 consists of libraries 83 that provide an interface into API 33 and isolate all other EPL applications from API 33, thus allowing the existence of file reader 38. Included in libraries 83 are functions to perform module start up, open PLU data file 46, connect an application to PLU data file 46, close an application's connection to PLU data file 46, close PLU data file 46, open business information data file 66, connect an application to business information data file 66, close an application's connection to business information data file 66, close business information data file 66, and to terminate the application

[0075] Example mappings and translations 84 provide non-displayable information (in code and/or in documentation) and may be edited to customize file reader 38.

[0076] Target routines 86 are routines that may be edited and customized to suit the needs of the target transaction establishment.

[0077] Make files 88 are files that pass source code (template 80 and target 81) through compiler 92 and then pass object code 82 through linker 94 to produce the target executable.

[0078] Turning now to FIG. 7, the method of creating file reader 38 begins with START 100.

[0079] In step 102, data verifier software 34 is isolated from PLU data file 46 and business information data file 66 through a non-displayable mapping determination and translation process. Example mappings and translations 84 result. This original development effort is provided to customers for future customization.

[0080] In steps 104, template 80 is provided. Template 80 is packaged in an installable format that can then be distributed and installed on the target system.

[0081] In step 105, customized mappings and translations 85 and customized target routines 87 are determined so that all information for an EPL can be displayed. Connection methods that will be employed for the target system are also determined.

[0082] In steps 106-112, customized template 81 is produced by changing template 80 to reflect customized mappings and translations 85. This work is performed by developers who are responsible for the integration of EPL system 16 for a target customer. Integration and customization are directed by the customer. This gives the customer the opportunity to gain a competitive advantage by displaying the information required to better serve its customers.

[0083] In step 106, the “read first” section is changed. The “read first” section is a routine that must be completed/customized to read the first PLU number in PLU data file 46 and the corresponding business information in business information data file 66.

[0084] In step 108, the “read next” section is changed. The “read next” section is a routine that must be completed/customized to read the next PLU number in PLU data file 46 and the corresponding business information in business information data file 66 sequentially.

[0085] In step 110, the “read specific” section is changed. The “read specific” section is a routine that must be completed/customized to read a specific PLU data file record and a corresponding record in business information data file 66.

[0086] In step 112, customized mapping and translations 85 and customized target routines 87 derived from step 105 are applied to template 80.

[0087] In step 114, a new executable (file reader 38) is compiled and linked from object code 82 and template 81 using make files 88, compiler 92, and linker 94.

[0088] In step 116, the method ends.

[0089] Referring now to FIG. 8, the operation of file reader 38 is illustrated in detail, beginning with START 120.

[0090] In step 122, file reader 38 starts up and configures itself.

[0091] In step 124, file reader 38 waits for an interprocess communications message from API 33. Interprocess communication services (e.g., “queues” for UNIX, threads or pipes for OS/2) are provided by operating system 50. API 33 calls on operating system 50 to send a request from data verifier software 34 to file reader 38, such as a request for price and business information in PLU data file 46 and/or business information data file 66 prior to comparing such information with corresponding information displayed by EPL 22. Data verifier software 34 issues a call to API 33, instructing API 33 to perform a “read direct” routine provided by API 33. API 33 calls on operating system 50 to send the interprocess communications message to file reader 38. Preferably, API 33 passes the message to libraries 83 within file reader 38.

[0092] If such a message is received, file reader 38 determines whether the interprocess communications message contains an “exit” command in step 125. If it does, file reader 38 terminates in step 136.

[0093] If the interprocess communications message does not contain an “exit” command, libraries 83 call file reading routine 43 within libraries 83 in step 126. File reading routine 43 is customized to the needs of the transaction establishment.

[0094] In step 128, file reading routine 43 uses operating system 50 to obtain the price and business information from PLU data file 46 and business information data file 66.

[0095] In step 130, file reading routine 43 masks the PLU information from PLU data file 46 and the business information from business information data file 66. Masking would include converting the price and business information into information that is displayable by EPL 22.

[0096] In step 132, file reading routine 43 terminates.

[0097] In step 134, libraries 83 call on operating system 50 to return the price and business information via interprocess communications to data verifier software 34 via API 33. File reader 38 returns to a waiting state in step 124.

[0098] After file reader 38 sends the price and business information to API 33, API 33 passes the price and business information to data verifier software 34. Data verifier software 34 can then compare the price and business information with currently-displayed price and business information, or otherwise examine the information in accordance with the function of application program 35.

[0099] Turning now to FIG. 9, the data verification method of the present invention begins with START 140.

[0100] In step 142, data verifier software 34 reads EPL data file 32.

[0101] In step 144, data verifier software 34 examines entry ITEM ID.

[0102] In step 146, data verifier software 34 reads PLU data file 46 and/or business information data file 66 using file reader 38.

[0103] In step 148, data verifier software 34 reads the line entry in PLU data file 46 and/or business information data file 66 having the same ITEM ID entry as the one read from EPL data file 32.

[0104] In step 150, data verifier software 34 examines entry PLU PRICE in the line entry from PLU data file 46.

[0105] In step 154, data verifier software 34 examines entry RELBUS in the line entry from PLU data file 46 and/or business information data file 66.

[0106] In step 156, data verifier software 34 combines price information with business information to produce combined data for display.

[0107] In step 158, data verifier software 34 calculates a checksum value for the combined display data.

[0108] In step 160, data verifier software 34 compares the calculated checksum value for the combined display data with the entry EPL CHECK in EPL data file 32.

[0109] If the calculated checksum value is not the same as the EPL CHECK entry, either the price or the business information for the item having ITEM ID is not the same in both EPL data file 32 and PLU data file 46. Display data mismatch has occurred.

[0110] In step 162, data verifier software 34 generates a display change request for changing the displayed data to new display data created in step 156.

[0111] In step 164, data verifier software 34 replaces the entry EPL CHECK with the checksum calculated checksum from step 158.

[0112] In step 166, data verifier software 34 determines whether the last line entry of EPL data file 32 has been read. If so, the method ends at step 168. If not, the method returns to step 142 to read another line entry from EPL data file 32.

[0113] Returning to step 160, if the calculated checksum value is the same as the EPL CHECK entry, the price and business information for the item having ITEM ID in EPL data file 32 are correct. Operation proceeds to step 166.

[0114] The data verification method of the present invention may be performed at any time. It is preferable to perform data verification after a loss of either EPL data file 32, PLU data file 46, or business information data file 66.

[0115] Although the present invention has been described with particular reference to certain preferred embodiments thereof, variations and modifications of the present invention can be effected within the spirit and scope of the following claims.