throbber
as) United States
`a2) Patent Application Publication co) Pub. No.: US 2002/0194074 Al
`(43) Pub. Date: Dec. 19, 2002
`
`Jacobs
`
`US 20020194074A1
`
`(54) SELF-CHECKOUT METHOD AND
`APPARATUS
`
`Publication Classification
`
`(76)
`
`Inventor: Erie L.L. Jacobs, Pointe Claire (CA)
`
`(SLY TRAC ccc tcnnanancsmnennnncennaccanneey GO6F 17/60
`(5B) OS CNE
`ceccctcicccseciscusrtstteetsieersnssesemneimeresreseer 705/16
`
`Correspondence Address:
`Clifford Chance Rogers & Wells LLP
`200 Park Avenue
`New York, NY 10166-0153 (US)
`
`(57)
`
`ABSTRACT
`
`A point-of-sale self-checkout
`terminal
`includes a code
`reader device for automated entry of a product identification
`(21) Appl. No.—10/150,146
`code present on items for purchase and a customer input
`device for receipt of data from a customer. A customer can
`initiate a purchase of a non-scannable item and, in response,
`a database is queriedto identify items basedon a prediction
`of purchase of the items, and the identified items are
`displayed for selection by the customer to purchasethe item.
`Inage processing and voice processing, can also be imple-
`mented to assist customers with the purchase of non-scan-
`nable items.
`
`(22)
`
`Filed:
`
`May17, 2002
`
`Related U.S. Application Data
`
`(63) Continuation-in-part of application No. 09/710,137,
`filed on Nov. 10, 2000.
`
`(60)
`
`Provisional application No. 60/244,234,filed on Oct.
`30, 2000.
`
`100
`
`PLEASE CHOOSE A PRODUCEITEM OR ENTER THE LABEL CODE ON
` THE KEYPAD PRESS DONE TO CONFIRM OR "NOLABELTOCONTINUE
`
`coca pou.|CASHIER
`
`[1[2Is|
`
`Geo
`=
` CrJILbore
`
`NAVELORANGE
`
`APPLES
`
`CLOVER NETWORK 1019
`CLOVER NETWORK1019
`
`

`

`Patent Application Publication Dec. 19,2002 Sheet 1 of 21
`
`US 2002/0194074 Al
`
`7}fegalfecd
`a
`|
`IRIWIFRUIT|
`
`Pewee
`casterfee
`DCcance|CALL
`
`IG. 1
`
` |
`I F
`
`*= ORGANIC
`
`PLEASE SELECTYOUR PRODUCETYPE
`Qa||SRY
`
`(Ay
`
`RAEBURN
`
`NO
`LABEL
`
`CALL
`
`ee
`
`Lact
`
`FIG. 2
`
`

`

`Patent Application Publication Dec. 19,2002 Sheet 2 of 21
`
`US 2002/0194074 Al
`
`TEST
`
`MAINTENANCE ee
`
`
`[FSvsens |vouneve|OMEa|
`|vo.uneoom|VOLUMEDOWN
`7te00Svotume 2d &
`| EXITMAINTENANCE |
`STOPROBOT 7
`
`
`
`CUSTOM
`SETUP
`
`TEST
`
`FIG. 3
`
`

`

`Patent Application Publication Dec. 19,2002 Sheet 3 of 21
`
`US 2002/0194074 Al
`
`|
`
`ca
`
`FIG. 4
`
`PLEASE ENTERYOURPASSWORD
`
`|canoes|
`foCLC
`
`|
`
`|
`
`PLEASETRYAGAIN
`
`|
`
`NY
`
`1|
`
`INVALIDPASSWORD
`
`FIG. 5
`
`

`

`Patent Application Publication Dec. 19,2002 Sheet 4 of 21
`
`US 2002/0194074 Al
`
`SocGO BACK
`MODIFICATION
`
`BEST-SELLER DATABASE
`MANAGEMENT
`
`FIG. 6
`
`LAYOUT
`
`FIG. 7
`
`

`

`Patent Application Publication Dec. 19,2002 Sheet 5 of 21
`
`US 2002/0194074 Al
`
`HOW OFTEN DO YOU WANT TO
`RESET THE DATABASE?
`
`a] er
`| GO BACK |
`
`TuEsoAY | emneson| aura
`MONDAY |
`[Frowy| [ssruRoay|
`SUNDAY
`
`FIG. 8
`
`ON WHICH WEEKDAY DO YOU WANT THE
`RESET TO TAKE PLACE?
`
`FIG. 9
`
`

`

`Patent Application Publication Dec. 19,2002 Sheet 6 of 21
`
`US 2002/0194074 Al
`
`SELECT LAYOUT TYPE FOR PRODUCE MAIN MENU
`
`
`
`J LUN
`
`8CONS*PINPAD(RIGHT) 8 ICONS*PINPAD(LEFT
`
`SELECT THE BUTTON THAT YOU WANT TO DEFINE/EDIT
`OR PRESS "EXIT" TO RETURN TO MAINTENANCE MODE
`
`|REMOVETHISBUTTON|
`
`WHAT DO YOU WANT TO ASSIGN
`TO THIS BUTTON POSITION?
`
`A'TOP 12"
`
`ASPECIFIC
`
`Sr
`
`| PRODUCECATEGORY |
`
`FIG. 12
`
`

`

`Patent Application Publication Dec. 19,2002 Sheet 7 of 21
`
`US 2002/0194074 Al
`
`SELECT THE BUTTON THAT YOU WANTTO DEFINE/EDIT
`OR PRESS "EXIT" TO RETURN TO MAINTENANCE MODE
`
`BANANA a)
`
`ENTER THE PLU CODE OF THE PRODUCE ITEM AND PRESS THE ITEM
`TO CONFIRM OR PRESS CLEAR TO ENTER A DIFFERENT PLU
`
`FIG. 14
`
`

`

`Patent Application Publication Dec. 19,2002 Sheet 8 of 21
`
`US 2002/0194074 Al
`
`ENTER THE PLU CODE OF THE PRODUCEITEM AND PRESS THEITEM
`TO CONFIRM OR PRESS CLEAR TO ENTERADIFFERENT PLU
`
`ay
`
`
`
`
`BANANA
`
`ORGANIC
`
`FIG. 15
`
`ENTER THE PLU CODE OF THE PRODUCEITEM AND PRESSTHEITEM
`TO CONFIRM OR PRESS CLEAR TO ENTERADIFFERENT PLU
`
`ae
`
`FIG. 16
`
`

`

`Patent Application Publication Dec. 19,2002 Sheet 9 of 21
`
`US 2002/0194074 Al
`
`BEST
`ELLER #1
`
`BEST
`SELLER #2
`
`SELECT THE BUTTON THAT YOU WANT TO DEFINE/EDIT
`OR PRESS “EXIT” TO RETURN TO MAINTENANCE MODE
`
`
`| GOBACK |
`
`[__exT_|
`
`FIG. 17
`
`DO YOU WANTTO:
`
`ASSIGN A GENERIC PRODUCE
`CATEGORY TO THIS BUTTON
`
`CREATE A SUBMENU FORTHIS
`GENERIC PRODUCE CATEGORY
`
`FIG. 18
`
`

`

`Patent Application Publication Dec. 19,2002 Sheet 10 of 21
`
`US 2002/0194074 Al
`
`CHOOSE A GENERIC PRODUCT CATEGORY
`
`FROM THE FOLLOWING:
`
`
`FIG. 19
`
`SELECT THE BUTTON THAT YOU WANTTO DEFINE/EDIT
`
`ORPRESS"EXIT"TORETURNTOMAINTE=)(S=]
`aes ara4 Jend
`Z) e2
`|_|
`
`[ExT_|
`
`FIG. 20
`
`

`

`Patent Application Publication Dec. 19,2002 Sheet 11 of 21
`
`US 2002/0194074 Al
`
`OR PRESS"EXIT" TO RETURN TO THE MAIN MEN
`
`SELECTTHE BUTTON THAT YOU WANT TO DEFINE/Ea
`Poo
`LI LJ LI
`Lj LILd
`
`
`
`FIG. 21
`
`ENTER THE PLU CODE OF THE PRODUCEITEM AND PRESSTHE ITEM
`TO CONFIRM OR PRESS CLEAR TO ENTER A DIFFERENT PLU
`
`
`
`
`
`BRAEBURN
`
`=
`
`FIGs 22
`
`

`

`Patent Application Publication Dec. 19,2002 Sheet 12 of 21
`
`US 2002/0194074 Al
`
`a]
`
`FIG, 23
`
`ENTER THE PLU CODE OF THE PRODUCEITEM AND PRESS THE ITEM
`TO CONFIRM OR PRESS CLEAR TO ENTER A DIFFERENT PLU
`
`
`I
`
`SELECT THE BUTTON THAT YOU WANTTO DEFINE/EDIT
`OR PRESS"EXIT" TO RETURN TO THE MAIN MENU
`
`oR,
`
`.L
`
`FIG. 24
`
`

`

`
`
`
`
`
`
`
`
`
`
`
`
`Patent Application Publication Dec. 19,2002 Sheet 13 of 21
`
`US 2002/0194074 Al
`
`
`
`THE BUTTON YOU HAVE SELECTED
`IS A GENERIC CATEGORY
`WITH A SUBMENU THAT HAS
`
`ALREADY BEEN DEFINED
`
`
`DO YOU WISH TO CHANGE
`THIS BUTTON ANYWAYS?
`
`
`
`FIG. 25
`
`ARE YOU SURE YOU WISH
`REMOVE THIS BUTTON?
`
`
`
`FIG. 26
`
`

`

`Patent Application Publication Dec. 19,2002 Sheet 14 of 21
`
`US 2002/0194074 Al
`
`)|=IEEESR||| PLEASECHOOSEAPRODUCEITEMOR ENTERTHELABELCODEON
`THEKEYPADPRESSDONETOCONFIRMOR"NOLABEL’TOore |
`
`
`ae=
`
`
`*= ORGANIC a!
`
`CEN *= ORGANIC
`
`poo
`EF
`
`FIG. 27
`
`PLEASE SELECT YOUR PRODUCE TYPE
`
`|GCY
`
`CRAB
`
`BRAEBURN
`
`)acaLl|
`|&CASHIER]
`
`——FTF
`
`FIG. 28
`
`

`

`Patent Application Publication Dec. 19,2002 Sheet 15 of 21
`
`US 2002/0194074 Al
`
`102
`
`SELECT CUSTOM SETUP
`IN MAINTENANCE MODE
`
`
`
`FIG. 29A
`
`

`

`Patent Application Publication Dec. 19,2002 Sheet 16 of 21
`
`US 2002/0194074 Al
`
`assaee eee ieee eae"
`
`
`
`PRODUCE
`TOP 12 MOST
`
`
`CATEGORY
`SOLD ITEMS
`
`
`
`GENERIC
`SEN)
`
`NO
`
`-/CONFIRM
`OVERWRITE
`
`YES
`
`SET BUTTON
`
`
` ATEGOR
`(NO<_
`penny
`
`SELECT]
`CLEAR
`NO
`
`SELECT CATEGORY
`
`are
`
`YES
`
`
`
`
`we
`YS
`ENTER PLU
`bp SELECT IMAGE}|[SELECT CLEAR a
`
`1% ea
`CORRECT?
`137
`
`
`
`15
`
`EXIT
`
`FIG. 29B
`
`

`

`ICOM
`
`LAdNIO3CIA
`
`ASVavLVvd
`
`90€
`
`eC
`
`Patent Application Publication Dec. 19, 2002
`
`Sheet 17 of 21
`
`US 2002/0194074 Al
`
`0€Old
`
`3009uve
`
`YANNVOS
`
`G0€
`
`
`
`AMLNA3TdketINI
`
`
`
`
`
`connecLINNSNISSS00UdLNdNIO|aNY
`
`Is10€
`
`
`
`
`
`
`

`

`Patent Application Publication Dec. 19,2002 Sheet 18 of 21
`
`US 2002/0194074 Al
`
`- Welcome*YouSieve" Valued:Stopper!
`~ CattipbellsSoup > »
`$0.89
`
`at | Fe
`Quakeroaiscersal 2" 93.49
`“Gi DetMontecup$249
`|." Manufactuier’sCotpon | 90.75.
`$4.29
`
`No Label!
`
`3102
`
`3103
`
`FIG. 31
`
`3201
` @eaunuue
`
`Seeseenaetenees
`seeeee
`
`FIG. 32
`
`

`

`Patent Application Publication Dec. 19,2002 Sheet 19 of 21
`
`US 2002/0194074 Al
`
`= 3301
`
`3305
`3301
`
`

`

`Patent Application Publication Dec. 19,2002 Sheet 20 of 21
`
`US 2002/0194074 Al
`
`WelcomeYourStore?Maluedved Shopoait”
`Campbells Soup
`wert
`
`;
`
`BH
`
`-Quaeercalscéteai *
`
`' Manufacturers,Coupon«
`
`Retum-to scanning
` tene oi - o «
`
`Enter more PLUs
`
`FIG. 35
`
`ws ee te a ns wo! .
`
`3601 J3602—3603 J U3604 Cscos L 3606
`
`FIG. 36
`
`

`

`Patent Application Publication Dec. 19,2002 Sheet 21 of 21
`
`US 2002/0194074 Al
`
`*“’ Non-Barcoded items Custom Setup
`He
`
`Bution Preview
`
`

`

`US 2002/0194074 Al
`
`Dec. 19, 2002
`
`SELF-CHECKOUT METHOD AND APPARATUS
`
`[0001] This application is a continuation-in-part of appli-
`cation Ser. No, 09/710,137 filed Nov. 10, 2000, entitled
`“Self-Checkout Method And Apparatus Including Graphic
`Interface For Non-Bar Coded Items” and claims benefit to
`provisional application serial No. 60/244,234 filed Oct. 30,
`2000.
`
`FIELD OF THE INVENTION
`
`invention relates to a method and
`[0002] The present
`apparatus for self-checkout.
`In particular,
`the invention
`relates to a method of and apparatus for self-checkout of
`non-bar coded items which includes using a graphic user
`interface (GUI) on a touch screen display.
`
`BACKGROUND OF THE INVENTION
`
`retail environment, a customer
`In a traditional
`[0003]
`selects various items for purchase and brings these items to
`a store clerk for checkout. Over the past few decades, retail
`point of sale systems have been greatly automated to expe-
`dite the checkout process. Computer-based point-of-sale
`systems are now the norm in the retail environment.
`
`(0004] Such point-of-sale systems include one or more
`terminals, and a database of prices,
`inventory and other
`information related to the items for purchase. Each terminal
`typically has an optical scanner which scans the items to be
`purchased for a machine readable bar codethat identifies the
`item on its packaging. When an item is scanned, the optical
`scanner sends a signal corresponding to the product number
`of the item to a data processing componentof the point-of-
`sale system, which then obtains from the database the price
`and the description of the scanned item.
`
`(0005] More recently, self-checkout point-of-sale systems
`have been popularized. These systems typically comprise
`self-checkout terminals each of which typically is provided
`with a bar code scanner with an integrated scale that allows
`the customer to scan the bar codes on the items to be
`purchased. The terminal typically also has other input and
`output devices such as a printer, electronic fund transfer
`terminal (EFT), a video camera unit and a display.
`
`(0006] Automated self-checkout systems, such as the
`U-Scan Express® available from Optimal Robotics Corp.,
`have become popular amongretailers throughout North
`America. Some self-checkout systems are described in U.S.
`Pat. Nos, 5,083,638, 5,115,888, 5,123,494, 5,125,465 and
`5,168,961.
`
`In the typical retail market, most produce items, as
`[0007]
`well as other items such as items priced according to weight
`bul usually not having a standardized weight, do not have a
`Universal Product Code (UPC), in the form of a bar code,
`associated with them. A Product Look Up (PLU) code is
`assigned instead to such items. The PLU code corresponds
`to a numeric identification of the item and, in most cases, is
`attached to the item with a sticker.
`
`[0008] The non-bar coded item typically is checked out by
`the item being placed on the scale at the checkout station, if
`the item is priced according to weight, and then the PLU
`code of the item being entered by the customer at
`the
`self-checkout station, or by the cashier at a manned checkout
`station, using the numeric keypad. The processing unit then
`
`assigns a price to the item based on the PLU code and, if
`applicable,
`the weight of the item detected by the scale.
`Many customers at such self-checkout stations do not know,
`however, that they need to enter manually the PLU code for
`such items, and therefore such customers experience delay
`in the checkout process.
`
`[0009] At a self-checkout terminal, the customer is pro-
`vided means to call
`for assistance from a supervisory
`employee when a non-bar coded item is to be processed. In
`some implementations, a video camera unit at
`the self-
`checkout terminal captures a video image of the uncoded
`item placed on the terminal’s scale by the customer. The
`video image of the uncodeditem is displayed at a supervisor
`station display which allows the supervisory employee to
`view the non-bar coded item and thereafter enter the appro-
`priate PLU code for the item. This employee typically
`supervises, however, several self-checkout terminals, and
`therefore the customer might encounter delay waiting for a
`non-bar coded item to be processed.
`
`SUMMARY OF THE INVENTION
`
`[0010] The present invention provides an apparatus and
`method for self-checkout of non-bar coded items. The
`apparatus includes a PLU entry device, a PLU database and
`a processing unit. The PLU entry device includes a display
`and a GUI. The GUI provides on the display a predetermined
`image corresponding to a non-bar codeditem, and meansfor
`the user to select the predetermined image of the non-bar
`coded item. The PLU entry device supplies a PLU corre-
`sponding to the non-bar coded item selected by the user. The
`processing unit uses the PLU supplied by the PLU entry
`device to retrieve the price per pound or per unit of the
`selected non-bar coded item from the PLU database. This
`data can be used to calculate price in relation to the weight
`or quantity of the item.
`
`[0011] The apparatus may include a GUI editor. The GUI
`editor may be used to configure the GUI for non-bar coded
`items.
`
`[0012] The processing unit may maintain for each item a
`count of the number of units of the item sold within a
`predetermined periodof time. The processing unit also may
`maintain a list of most frequently sold items, and the image
`ofat least one item onthe list may be provided on a selected
`display screen. The processing unit may update the display
`screen when the list of most frequently sold items changes.
`
`[0013] An image of a generic category of items may be
`provided on the display. The displayed image of the generic
`category may be selected by the user to view images of
`respective items in the generic category.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`[0014] The present invention can be more readily under-
`stood from the following detailed description by referring to
`the accompanying drawings wherein:
`
`1 shows an exemplary image of a non-bar
`[0015] FIG.
`coded item selection GUI that can appear on a touch screen
`monitor for selecting a generic category of items;
`
`[0016] FIG. 2 shows an exemplary GUI screen [orselect-
`ing one of specific types of apples;
`
`

`

`US 2002/0194074 Al
`
`Dec. 19, 2002
`
`[0017] FIG. 3 shows an exemplary GUI screen presenting
`maintenance mode options;
`
`[0018] FIG. 4 shows an exemplary GUI screen for enter-
`ing a password;
`
`(0019] FIG. 5 shows an exemplary GUI screen for enter-
`ing an alternate password;
`
`[0020] FIG. 6 shows an exemplary GUI screen presenting
`custom setup options;
`
`[0021] FIG. 7 shows an exemplary GUI editor screen
`presenting edit options;
`
`[0022] FIG. 8 shows an exemplary GUI editor screen for
`selecting a reset frequency for the database of most fre-
`quently sold items;
`
`[0023] FIG. 9 shows an exemplary GUI editor screen for
`selecting a day of the week upon which the database is to be
`reset;
`
`[0024] FIG. 10 shows an exemplary GUI editor screen for
`selecting visual layout of the GUI for non-bar coded items;
`
`(0025] FIG. 11 shows an exemplary GUI editor screen for
`selecting a button to which an item or generic category may
`be assigned;
`
`[0026] FIG. 12 shows an exemplary GUI editor screen for
`selecting a type of an item to be assigned to the selected
`button;
`
`{0027] FIG. 13 shows an exemplary GUI editor screen for
`selecting a third button to be defined;
`
`[0028] FIG. 14 shows an exemplary GUI editor screen for
`selecting a specific item to assign to a button;
`
`(0029] FIG. 15 shows an exemplary GUI editor screen
`indicating selection of an organic fruit/vegetable;
`
`[0030] FIG. 16 shows an exemplary GUI editor screen
`informing that an incorrect PLU code was entered;
`
`[0031] FIG. 17 shows an exemplary GUI editor screen for
`selecting a fourth button to be defined;
`
`[0032] FIG. 18 shows an exemplary GUI editor screen for
`selecting a generic category to be assigned to a selected
`button;
`
`{0033] FIG. 19 shows an exemplary GUI editor screen for
`selecting a generic category;
`
`[0034] FIG. 20 shows an exemplary GUI editor screen for
`selecting a fifth button to be defined;
`
`[0035] FIG. 21 shows an exemplary GUI editor sereen for
`selecting a button to be assigned in the submenu;
`
`[0036] FIG. 22 shows an exemplary GUI editor screen for
`selecting an item to assign to the selected button in the
`submenu;
`
`
`
`[0037] FIG. 23 shows an exemplary GUI editor screen for
`selecting an item to assign to a second button in the
`submenu;
`
`(0038] FIG. 24 shows an exemplary GUI editor screen for
`selecting a third button to be assigned in the submenu;
`
`[0039] FIG. 25 shows an exemplary GUI editor screen for
`presenting a warning if a selected button has been assigned
`to a generic category with a pre-defined submenu;
`[0040] FIG, 26 shows an exemplary GUI editor screen for
`confirming removal of a selected button;
`
`(0041] FIG. 27 shows an exemplary screen in the GUI for
`non-bar coded items;
`
`[0042] FIG. 28 shows an exemplary screen in the GUI for
`non-bar coded items when a generic category button is
`selected;
`
`for a
`[0043] FIGS. 29A and 29B show a flow chart
`process, in accordance with an embodiment of the present
`invention, of setting up a non-bar coded items GUI.
`
`[0044] FIG. 30 shows a block diagram of a self-checkout
`system.
`
`FIGS, 31-35 show exemplary screens of the GUI
`[0045]
`for non-bar coded items with alphanumeric lookup.
`[0046] FIG. 36 showsdata stored in exemplary database
`records.
`
`DETAILED DESCRIPTION OF THE
`INVENTION
`
`Improvements in the operation and usability of
`[0047]
`point-of-sale self-checkout systems can be provided by a
`self-checkout system that includes a scanning device for
`automated scanning of bar-coded items as well as a cus-
`tomer-operated interface for checkout of items that are not
`coded for scanning. The customer-operated interface can be
`a graphical user interface (GUI) (a “non-scannable item
`GUI”) that may include features such as a touch-screen
`display and input device, iconic representations of items for
`purchase, and search facilities to help identify items being
`purchasedand to enter appropriate checkout data. An editor
`for provisioning data and setting up various features ofthe
`non-scannable item interface can also be provided. The
`checkout system, and in particular, the non-scannable item
`GUI, can be used for checkout of items such as produce and
`bakery items in a grocery sales environment and for non-
`scannable items in other retail environments. To do so, a
`flexible method of provisioning data and icon images asso-
`ciated with the non-scannable items is provided.
`
`[0048] FIG. 30 shows a block diagram of an implemen-
`tation of a point-of-sale self-checkout station that includes a
`non-scannable item GUI. The self-checkout station 300
`includes a processing unit 301 which may be configured
`similar to known microprocessor-based computers andhas a
`central processing unit (CPU), a plurality of storage devices,
`an input/output (I/O) interface and a network interface. The
`storage devices may include program memory,
`random
`access memory (RAM), non-volatile memory, read-only
`memory (ROM), electrically erasable programmable ROM
`(EEPROM), ete., and any or a combination of the mass
`storage devices known conventionally in the art, such as
`floppy disk, optical disk, hard disk and/or tape cartridge
`drives, plus appropriate device drivers. The CPU commu-
`nicates via the I/O interface with a PLU database 303, one
`or more scales 304, a touch-screen display 302 (or other
`entry device, such as a touchpad), and a bar code scanner.
`Items may include other types of machine-detectible iden-
`tification encodings instead of, or in addition to, scannable
`
`

`

`US 2002/0194074 Al
`
`Dec. 19, 2002
`
`bar codes (e.g., magnetic encodings, magnetic transducers,
`and other machine-readable printed codes). Consequently,
`implementations may be equipped with other types of reader
`devices to detect encoded product identifications (IDs), e.g.,
`magnetic sensors to read magnetic encodings, and other
`types of scanning sensors for other printed code types.
`
`[0049] The self-checkoutstation (i-c., processing unit 301)
`alsocan include a networkinterface used for communication
`over a network(¢.g., a local area network, wide area network
`(WAN), wireless and other networks) with other devices.
`These other devices may include a host computer, such as a
`store’s central controller, and may also include other check-
`out stations and supervisory stations. The network interface
`includes the appropriate units for interfacing with the net-
`work, including, for example, Ethernet card, modem, radio
`frequency (RF) transceiver, etc. For example, processing
`unit 301 may download product and other information from
`a central point-of-sale database on the network, on power-up
`as well as periodically during operation, via the network
`interface. Thus, the PLU database 303 stored in the storage
`devices may be updated.
`
`{0050] Self-checkout orders commonly include a combi-
`nation of scannable (i.e., bar-coded) and non-scannable
`items. To purchase a scannable item, the customer moves the
`item past an automated scanning device which reads the
`scannable product
`identifier and thereby determines the
`item’s identification. If the customer wants to purchase a
`non-scannable item, the customer may do so by entering of
`a product identifier using the non-scannable item interface.
`This product identifier can be received through the entry of
`an alpha-numeric identifier, an icon selection, or by a
`combination of these methods (the chosen mechanisms may
`differ in different
`implementations). In some implementa-
`tions, speech and visual inputs may be processed by the
`self-checkout system to assist in identifying a produce.
`
`interface
`[0051] FIGS, 1-2 and 31-35 show customer
`screens displayed in two example implementations (imple-
`mentation #1 and #2) of non-scannable item GUIs. Each of
`the example implementations uses an interactive touch-
`screen display 302 combining a touch-sensor screen 302b
`and a cathode ray tube (CRT), liquid crystal display (LCD),
`or other graphical display element 302a@ for customer inter-
`action. Implementation #1 (FIGS. 1-2) includes a on-screen
`numeric keypad 192 for the entry of product lookup (PLU)
`codes, and displays interactive icons 191 that can be used to
`select an item from system-determined initial grouping of
`products. The system-determined grouping is a grouping
`that is determined separate from an explicit search request
`by a customer for a desired item. Examples of system-
`determined groupings include predetermined grouping and
`predictively determined grouping (e.g., a grouping of fre-
`quently-purchased non-scannable items).
`Implementation
`#2 (FIGS. 31-35) also includes a on-screen numeric keypad
`3102, as well as a system-determined initial group of inter-
`active icons 3201. Implementation #2 also includes a alpha-
`betic keyboard interface 3204 used to enter search terms so
`that the customer can locate and select products in addition
`to those shownin the initial group 3201. The self-checkout
`system’s non-scannable item GUI
`is accessed when the
`customer wishes to purchase a non-bar-coded item. Access
`to the interface may be triggered when the customer places
`an unscanned item on a scannerscale, or by explicit selec-
`
`tion of a on-screen control from the display 302 (e.g., a
`button labeled “Purchase Item Without A Bar Code).
`
`[0052] When the non-scannable item GUI is activated, a
`PLUentry screen 100, 3100 may be displayed. As shown in
`screen 100 of implementation #1, the customer can identify
`an item by PLU code entry using a graphical touch-screen
`keypad 192. If the item is displayed in the grouping 191, the
`customer can also select the appropriate item to enter the
`purchase.
`In some implementations,
`icons 191 display
`images representing a generic category and selection of the
`generic category’s icon will provide a more detailed sub-
`menu. If the item is not labeled with a PLU code, and an
`appropriate icon 191 is not displayed, the user mayselect the
`“No Label” button 103 to obtain assistance from store
`personnel. Interface screen 3100 of implementation #2 also
`permits entry of a PLU code using a graphical touch-screen
`interface. If the item is not labeled with a PLU code, the user
`can select the “No Label” button 3103 to access a second
`interface screen 3200 (FIG. 32).
`Interface screen 3200
`initially displays the system-determined icon grouping 3201
`as well as an on-screen keyboard 3202.
`Icons initially
`displayed in 3201 can be bestseller or most frequently sold
`items, and this information can be displayed as soon as the
`screen is displayed. If the purchase item is shownbyan icon
`3201, the user may select that icon to purchase the item,
`otherwise keyboard 3204 may be used to enter terms used to
`search a product database 303 and locate the desired item.
`
`[0053] To locate a desired item, keyboard 3204 is usedto
`provide alphabetic character input (or, in some implemen-
`lations, expanded input sets such as alpha-numeric) to the
`checkout system. The checkout system receives the input
`characters, parses the input
`into search terms, queries a
`product database, and display results as user-selectable
`icons. Referring to FIG. 33, as letters are entered on the
`keyboard 3204, they are displayed in a display area 3305 and
`matching products are determined based on the entered
`characters and displayed as icons 3301 displayed on the
`interface 3300. As additional letters are entered, the display
`area 3301 is again updated to reflect the additional input
`(compare the icons of FIG. 33 which are displayedafter the
`entry of the letter “P” with the icons of FIG. 34 which are
`displayed after the further entry of the letter “E”).
`
`[0054] To identify the matching products, the checkout
`syslem parses input characters to form search terms and uses
`those terms to query the database 303 and thereby locate
`matching items. The search terms included in the query can
`include words(i.¢c., a group of contiguous letters delimited
`by a space character) as well as a word fragment (1.e., a
`group of contiguous letters not yet delimited by a space
`character). Querying database 303 includes comparing each
`of the search terms to keywords associated with each
`product. The item-keyword database may be storedin a local
`database 303 or a central database (e.g., a store controller
`database). FIG. 36 shows example item-keyword records
`for a number of products. As shown in FIG, 36, for each
`product, the database stores an icon 3601, a PLU number
`3602, a descriptors 3603 that may be used by other store
`systems (e.g., by a store’s master controller), and keywords
`in one or more languages(e.g., English 3604, Spanish 3605,
`and French 3606).
`
`Preferably, the product query algorithm will match
`[0055]
`search termsto an item’s keywords regardless of the relative
`
`

`

`US 2002/0194074 Al
`
`Dec. 19, 2002
`
`ordering of the search terms and keywords. Further, a search
`term will match a keyword if the term is presentas an initial
`substring of the keyword. Thus, the term “Pear Bos” will
`match “Bose Pears.” Additionally,
`implementations may
`provide for automatic conversion between plural and singu-
`lar terms such that a term entered by the user in the plural
`(¢.g., “pears”) will match a keyword expressed in the
`singular (e.g., “pear’). Conversion between singular and
`plural tenses may be done, ¢.g., by using a lookuptable. In
`some implementations, a lookup table may also be used to
`convert a term entered by a user into an alternative term or
`to expand an entered term into multiple terms. This conver-
`sion and expansion feature may be used, for example, to
`convert a regional product name to a standard term, or where
`a product may be known by multiple terms (e.g.,
`in a
`hardware store implementation, the search term “fastener”
`may be expanded to the Boolean search expression “bolt or
`screw or rivet”). Where term substitution and/or expansion
`is employed, the display of results may be in accordance
`with an ordering that favors results matching the specific
`terms entered, rather than the expanded or substitute terms.
`[0056]
`In some implementations, the icon display 3301 is
`automatically updated as each letter is entered.
`In other
`implementations, the icon display may be updated when
`there is a pause in data entry (e.g., after a 500 millisecond
`pause), or upon explicit request by the user(e.g., selecting
`an “Enter” button). Implementations can also include scroll
`buttons (e.g., buttons 3302) used to scroll the displayed
`icons when the number of items exceedsthe available screen
`space. After the desired item icon is displayed and selected,
`another screen (FIG. 35) may be displayed for the entry of
`quantity information using keypad 3501.
`
`In the example implementations (#1 and #2), the
`(0057]
`system-determined icons (191 and 3201, respectively) are
`displayed when the non-scannable item GUI is accessed.
`These initial icons sets 191, 3201 may be selected based on
`an expectation or probability that a particular items is to be
`purchased, This expectation can be determined based on the
`frequency of purchaseof particular items during a preceding
`period (e.g., during the past month) in all customer orders,
`In other implementations,the initial icons 191, 3201 may be
`customer specific and can be determined based on a cus-
`tomer’s specific sales history. The initial icon set can also be
`determined based on other statistical/probabilistic factors.
`For example, the icons 191, 3201 may be determined based
`on a statistical correlation that a particular item will be
`purchased when another item has already been entered as
`part of an order. For example, in a hardware store imple-
`mentation, if copper piping has already been entered in an
`order, the icons 191, 3201 may correspond to non-bar-coded
`joints and fasteners used to connect copper piping.
`
`In some implementations, the system-determined
`[0058]
`icons 191, 3201 can be determined on a user-specific basis.
`To enable this feature, the database 303 includes customer
`purchase history information. Following receipt of a cus-
`tomer identification by the self-checkout system (e.g., by the
`swiping of a bar-coded frequent-shopper card in front of a
`scanner, swiping ofa credit or debit card entry, or using data
`entered directly by the customer),
`the database 303 is
`queried to determine the user’s purchase history. The icons
`191, 3201 are then determined based on the user’s purchase
`history or other user-specific information. Correspondingly,
`at the end of order processing, customer purchase data may
`
`be stored in the database 303 reflecting the newly purchased
`items. In other implementations, the sales history database
`may be implemented by data stored on the frequent-shopper
`card (¢.g., using a magnetic strip or
`in “smart card”
`memory).
`[0059]
`Implementations can include further refinements,
`such as the ability to determine the frequently sold items on
`a seasonal basis. In such implementations, the database 303
`can store customer purchase information along with pur-
`chase dates so that seasonal buying patterns can be deter-
`mined. Thus, for example, during the week before Hallow-
`een, icons for purchase of pumpkins may be displayed based
`on a customers’ purchases of pumpkins during that week of
`the previous year. This information may be stored without
`differentiating based on the particular customers, or may be
`stored on a customer-specific basis.
`
`[0060] The icon grouping 191, 3201 may change continu-
`ously as a result of ongoing sales at
`the self-checkout
`terminals. For example, in a frequently-sold item implemen-
`tation, the system automatically updates the images on the
`touch screen monitor for those buttons pre-defined as but-
`tons for most frequently sold items. The updating of the
`buttons may be dynamic and may occur in between the
`processing of two orders at the self-checkout terminal, or
`may be at greater intervals (e.g., monthly or quarterly). The
`processing unit of each self-checkout terminal, or a central
`database, may maintain an item count of every produce (or
`non-bar coded item) sold. Checkout terminals may commu-
`nicate to find the highest count of produce (or non-bar
`coded) items in their database.
`[0061] As anexample, the following may be a snapshot(in
`time) of information stored in the databases corresponding
`to counts of produce (or non-bar coded) items sold at four
`respective self-checkout terminals in a grocery store:
`
`Terminal 1
`Database
`
`Terminal 2
`Database
`
`Terminal 193
`Database
`
`Terminal 4
`Database
`
`carrots = 156
`peaches = 48
`
`lemons = 200
`tomatoes = 156
`
`bananas = 750
`carrots = 155
`
`cucumbers = 6
`bananas = 46
`
`{0062] After the terminals have communicated amongst
`themselves, (or the purchase information has been aggre-
`gated in a central data system) the following results may be
`displayed on the touch screen monitor of cach of the
`self-checkout terminals:
`
`Top 1 = bananas
`Top 2 = carrots
`Top 3 = lemons
`
`Top 4 = tomatoes
`Top 5 = peaches
`Top 6 = cucumbers
`
`[0063] Each database record mayalso contain other infor-
`mation such as an expected weight range, density range, and
`size information, This additional data may be employedin
`enhanced versions of a self-checkout system. Two such
`enhancements include the use of image processing and voice
`recognition.
`
`In an implementation that includes image process-
`{0064]
`ing, the system-selected items 191, 3201 may be selected
`
`

`

`US 2002/0194074 A

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket