Touchless and touch optimized processing of retail and other commerce transactions

BACKGROUND OF THE INVENTION

0001The present invention relates to processing data from an input device. In particular, the present invention relates to performing tasks in a commerce application based on input data.

0002There are a number of different input devices that communicate with a computer. For example, retail input devices can include a keyboard for manual input, a barcode scanner for scanning barcodes and a magnetic stripe reader for reading a magnetic stripe on a credit card. Additionally, pointer devices, touch screens and other devices can be used. A commerce based application such as a retail software application running on the computer uses input data from these devices for a number of different tasks, for example to process a transaction.

0003Typically, software applications require a prompt or other indication of a particular input that the software application can expect. This prompting requires additional tasks to be performed by a user. Typically, the prompting is provided by a form of “touch” input device, where a user has to physically touch the device, such as a mouse, keyboard or touch screen. These additional input operations lead to increased time in processing a transaction, mistakes and training costs. For example, in a simple one-item transaction, a user will need to prompt the application to expect input related to one or more items for purchase, expect input related to customer information and expect input related to a tender used for the transaction. Thus, there is a need to provide an efficient manner for performing tasks based on input from an input device.

SUMMARY OF THE INVENTION

0004A computer implemented method for reducing input performed in a commerce based application is provided. The method includes receiving a sequence of input values from an input device and associating the sequence of input values with an object in the application based on the sequence. A context of the application is determined. One or more tasks in the application are automatically performed based on the object, the context and the sequence of input values.

0005Another aspect of the present invention relates to a commerce based system having a computer with memory and at least one input port. A plurality of input devices are operably coupled to the at least one input port to send a sequence of input values to the input port. A commerce based application program is stored on the memory and operably coupled to the at least one input port to receive a particular sequence of input values from one of the plurality of input devices. The application program includes an application context module defining a context of the application program and a transaction processing module operably coupled to the application context module. The transaction processing module is adapted to receive the particular sequence, associate the particular sequence with an object based on the sequence and perform one or more tasks based on the object, the particular sequence and the context of the application program.

BRIEF DESCRIPTION OF THE DRAWINGS

0006<figref idref="DRAWINGS">FIG. 1</figref> is a block diagram of a general computing environment in which the present invention can be useful.

0007<figref idref="DRAWINGS">FIG. 2</figref> is a block diagram of a plurality of input devices providing input to a computer.

0008<figref idref="DRAWINGS">FIG. 3</figref> is a flow diagram of a method for processing input from an input device.

0009<figref idref="DRAWINGS">FIG. 4</figref> is a block diagram of a retail application that receives input from an external device.

0010<figref idref="DRAWINGS">FIGS. 5-9</figref> are screen shots of a retail application that illustrates tasks performed based on input from an input device.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

0011Prior to discussing the present invention in greater detail, one embodiment of an illustrative environment which the present invention can be used will be discussed. <figref idref="DRAWINGS">FIG. 1</figref> illustrates an example of a suitable computing system environment <b>100</b> on which the invention may be implemented. The computing system environment <b>100</b> is only one example of a suitable computing environment and is not intended to suggest any limitation as to the scope of use or functionality of the invention. Neither should the computing environment <b>100</b> be interpreted as having any dependency or requirement relating to any one or combination of components illustrated in the exemplary operating environment <b>100</b>.

0012The invention is operational with numerous other general purpose or special purpose computing system environments or configurations. Examples of well known computing systems, environments, and/or configurations that may be suitable for use with the invention include, but are not limited to, personal computers, server computers, hand-held or laptop devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the above systems or devices, and the like.

0013The invention may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The invention may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices. Tasks performed by the programs and modules are described below and with the aid of figures. Those skilled in the art can implement the description and figures as processor executable instructions, which can be written on any form of a computer readable medium.

0014With reference to <figref idref="DRAWINGS">FIG. 1</figref>, an exemplary system for implementing the invention includes a general purpose computing device in the form of a computer <b>110</b>. Components of computer <b>110</b> may include, but are not limited to, a processing unit <b>120</b>, a system memory <b>130</b>, and a system bus <b>121</b> that couples various system components including the system memory to the processing unit <b>120</b>. The system bus <b>121</b> may be any of several types of bus structures including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of bus architectures. By way of example, and not limitation, such architectures include Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus also known as Mezzanine bus.

0015Computer <b>110</b> typically includes a variety of computer readable media. Computer readable media can be any available medium or media that can be accessed by computer <b>110</b> and includes both volatile and nonvolatile media, removable and non-removable media. By way of example, and not limitation, computer readable media may comprise computer storage media and communication media. Computer storage media includes both volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by computer <b>110</b>. Communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. Combinations of any of the above should also be included within the scope of computer readable media.

0016The system memory <b>130</b> includes computer storage media in the form of volatile and/or nonvolatile memory such as read only memory (ROM) <b>131</b> and random access memory (RAM) <b>132</b>. A basic input/output system <b>133</b> (BIOS), containing the basic routines that help to transfer information between elements within computer <b>110</b>, such as during start-up, is typically stored in ROM <b>131</b>. RAM <b>132</b> typically contains data and/or program modules that are immediately accessible to and/or presently being operated on by processing unit <b>120</b>. By way of example, and not limitation, <figref idref="DRAWINGS">FIG. 1</figref> illustrates operating system <b>134</b>, application programs <b>135</b>, other program modules <b>136</b>, and program data <b>137</b>.

0017The computer <b>110</b> may also include other removable/non-removable volatile/nonvolatile computer storage media. By way of example only, <figref idref="DRAWINGS">FIG. 1</figref> illustrates a hard disk drive <b>141</b> that reads from or writes to non-removable, nonvolatile magnetic media, a magnetic disk drive <b>151</b> that reads from or writes to a removable, nonvolatile magnetic disk <b>152</b>, and an optical disk drive <b>155</b> that reads from or writes to a removable, nonvolatile optical disk <b>156</b> such as a CD ROM or other optical media. Other removable/non-removable, volatile/nonvolatile computer storage media that can be used in the exemplary operating environment include, but are not limited to, magnetic tape cassettes, flash memory cards, digital versatile disks, digital video tape, solid state RAM, solid state ROM, and the like. The hard disk drive <b>141</b> is typically connected to the system bus <b>121</b> through a non-removable memory interface such as interface <b>140</b>, and magnetic disk drive <b>151</b> and optical disk drive <b>155</b> are typically connected to the system bus <b>121</b> by a removable memory interface, such as interface <b>150</b>.

0018The drives and their associated computer storage media discussed above and illustrated in <figref idref="DRAWINGS">FIG. 1</figref>, provide storage of computer readable instructions, data structures, program modules and other data for the computer <b>110</b>. In <figref idref="DRAWINGS">FIG. 1</figref>, for example, hard disk drive <b>141</b> is illustrated as storing operating system <b>144</b>, application programs <b>145</b>, other program modules <b>146</b>, and program data <b>147</b>. Note that these components can either be the same as or different from operating system <b>134</b>, application programs <b>135</b>, other program modules <b>136</b>, and program data <b>137</b>. Operating system <b>144</b>, application programs <b>145</b>, other program modules <b>146</b>, and program data <b>147</b> are given different numbers here to illustrate that, at a minimum, they are different copies.

0019A user may enter commands and information into the computer <b>110</b> through input devices such as a keyboard <b>162</b>, a microphone <b>163</b>, and a pointing device <b>161</b>, such as a mouse, trackball or touch pad. Other input devices (not shown) may include a joystick, game pad, satellite dish, scanner, or the like. These and other input devices are often connected to the processing unit <b>120</b> through a user input interface <b>160</b> that is coupled to the system bus, but may be connected by other interface and bus structures, such as a parallel port, game port or a universal serial bus (USB). A monitor <b>191</b> or other type of display device is also connected to the system bus <b>121</b> via an interface, such as a video interface <b>190</b>. In addition to the monitor, computers may also include other peripheral output devices such as speakers <b>197</b> and printer <b>196</b>, which may be connected through an output peripheral interface <b>195</b>.

0020The computer <b>110</b> may operate in a networked environment using logical connections to one or more remote computers, such as a remote computer <b>180</b>. The remote computer <b>180</b> may be a personal computer, a hand-held device, a server, a router, a network PC, a peer device or other common network node, and typically includes many or all of the elements described above relative to the computer <b>110</b>. The logical connections depicted in <figref idref="DRAWINGS">FIG. 1</figref> include a local area network (LAN) <b>171</b> and a wide area network (WAN) <b>173</b>, but may also include other networks. Such networking environments are commonplace in offices, enterprise-wide computer networks, intranets and the Internet.

0021When used in a LAN networking environment, the computer <b>110</b> is connected to the LAN <b>171</b> through a network interface or adapter <b>170</b>. When used in a WAN networking environment, the computer <b>110</b> typically includes a modem <b>172</b> or other means for establishing communications over the WAN <b>173</b>, such as the Internet. The modem <b>172</b>, which may be internal or external, may be connected to the system bus <b>121</b> via the user-input interface <b>160</b>, or other appropriate mechanism. In a networked environment, program modules depicted relative to the computer <b>110</b>, or portions thereof, may be stored in the remote memory storage device. By way of example, and not limitation, <figref idref="DRAWINGS">FIG. 1</figref> illustrates remote application programs <b>185</b> as residing on remote computer <b>180</b>. It will be appreciated that the network connections shown are exemplary and other means of establishing a communications link between the computers may be used.

0022<figref idref="DRAWINGS">FIG. 2</figref> illustrates an environment wherein a plurality of input devices communicate with a computer <b>200</b>, an example of which is described above with respect to <figref idref="DRAWINGS">FIG. 1</figref>. Computer <b>200</b> includes at least one application <b>202</b> and an input device handler <b>204</b>. A plurality of input devices including a keyboard and/or a touch screen <b>212</b>, a barcode scanner <b>214</b>, a magnetic stripe reader <b>216</b> and a RF identification receiver <b>218</b> communicate through at least one port <b>220</b> to computer <b>200</b>. As appreciated by those skilled in the art, other input devices, such as a magnetic ink character recognition (MICR) reader, may also be used in accordance with the present invention and multiple input devices can share a common form factor and/or input conduit.

0023Keyboard/touch screen <b>212</b> receives manual input from a user, barcode scanner <b>214</b> scans a barcode, magnetic stripe reader <b>216</b> reads a magnetic stripe of a magnetic card and RF identification receiver <b>218</b> receives radio frequency signals that are sent to port <b>220</b>. In accordance with the present invention, multiple ports similar to port <b>220</b> that are operably coupled to separate input devices can also be used. Each of the multiple ports can provide information received from a respective input device to input device handler module <b>204</b>.

0024Input device handler <b>204</b> receives input from the plurality of devices through at least one port <b>220</b> and sends the input to application <b>202</b>. In an exemplary embodiment, the input includes a sequence of input values that relate to various information, such as a customer name, a product identification number and a credit card account number. Application <b>202</b> detects the input and automatically performs tasks based on the input. The tasks are also based on a particular context for the application. In accordance with an embodiment of the present invention, using application <b>200</b>, the need for use of keyboard/touch screen <b>212</b> can be reduced and in some cases eliminated during processing of a transaction. For example, a cashier need only use a scan, scan and swipe to completely process a transaction. Thus, operation of other input devices that use touching is minimized.

0025<figref idref="DRAWINGS">FIG. 3</figref> is an exemplary method for processing input from an input device in a commerce application. As discussed below, the input is processed based on program heuristics to predict a logical flow for the input. At step <b>252</b>, input from the input device is detected. For example, input device handler <b>204</b> can detect input from any of the input devices described above. At step <b>254</b> a source and content of the input is determined. In one embodiment, the source and content of the input can be determined in a manner described in U.S. application Ser. No. 10/740,936, filed Dec. 19, 2003, entitled AUTOMATED INPUT DETERMINATION, the contents of which are hereby incorporated by reference in its entirety. For example, if a sequence of sixteen input values is received, the sequence can indicate that a magnetic stripe reader provided the input. Other methods of determining the source and content can be used. The sequence is associated with an object in the application based on the content and/or the source of the sequence at step <b>255</b>. Exemplary objects for a commerce application include a retail item, a customer, a tender, an order a shipping notice, etc. The context of an associated application is determined at step <b>256</b>. The context can be related to one or more aspects of the application, for example a particular mode for the application, a location, a user, etc.

0026At step <b>258</b>, one or more tasks (or actions) are automatically performed based on the object, the context and the input. For example, these tasks can include a comparison of the input with an inventory list, a customer list and/or a receipt list. Further tasks can additionally be performed, such as calculation of sales tax, requesting approval for a credit card transaction and/or presenting multiple options to a user. In some instances, the context of the application is switched based on the input. For example, the context can be switched from an initial mode to a sales transaction made or a return void mode. The tasks that are performed are determined from heuristics based on a logical flow for the application based on the input.

0027<figref idref="DRAWINGS">FIG. 4</figref> is a block diagram of an exemplary commerce application <b>300</b> for use with the present invention. Commerce application <b>300</b> includes an application context <b>302</b> and a transaction processing module <b>304</b>. An external device <b>306</b>, which can be any of the input devices discussed above, provides input to application <b>300</b>, which is then sent to transaction processing module <b>304</b>.

0028Transaction module <b>304</b> is based on program heuristics designed to reduce, and in some cases eliminate, input from a user of devices such as a mouse and/or a keyboard. Based on the input of external device <b>306</b>, transaction processing module <b>304</b> associates the input with an object and utilizes a plurality of actions, herein shown as actions <b>1</b>-N, depending on application context <b>302</b>. The object can be an object as discussed above. Application context <b>302</b> includes a user context <b>308</b>, location context <b>310</b> and object context <b>312</b>. Other context associated with application context <b>302</b> can also be used.

0029User context <b>308</b> includes default behavior actions based on a particular user for application <b>300</b>. For example, the user may be an owner, a manager, a cashier, etc. Each of these user contexts can have varying attributes, roles and permissions. For example, retail application <b>300</b> can be designed such that only a manager or owner can void a transaction. Location context <b>310</b> is based on the location of retail application <b>300</b>. For example, the location could be at a point of sale, a back office setting, a warehouse, etc. Location context <b>310</b> thus includes default behavior actions based on the location. In a point of sale context, scanning an item can populate a retail transaction with the item's details. Object context <b>312</b> identifies various objects, such as items, customers, tenders, transactions, receipts, etc. Transaction module <b>304</b> associates the input with one or more of these objects. Object context <b>312</b> includes default behavior actions based on user context <b>308</b>, location context <b>310</b> and the one or more objects.

0030Given the application context <b>302</b>, which includes user context <b>308</b>, location context <b>310</b> and object context <b>312</b>, transaction processing module <b>304</b> selects one or more actions based on the context and the input from external device <b>306</b>. For example, one action can be related to adding a customer to a transaction based on a customer scan of a customer ID card. Another action can be related to adding an item to a transaction based on a bar code scan of an item's bar code. Yet another action can be based on tendering an amount to a credit card based on a card swipe from a magnetic stripe reader.

0031Thus, in a store or other environment having bar coded inventory with customer cards and electronic credit or debit processing, a sales cashier can complete a sales transaction without accessing input devices such as keyboards, pointer devices and/or touch panels. Instead, a transaction is completed with only a scan of an item, a scan of a customer card and a swipe of the credit card. The transaction processing module <b>204</b>, based on heuristics, compares the first scan to an inventory list and adds an item to the transaction, the second scan adds a customer to the transaction and the credit card swipe tenders the credit card to the transaction and prints out a receipt.

0032<figref idref="DRAWINGS">FIGS. 5-9</figref> are exemplary screen shots that illustrate tasks performed by a retail application based on input from an input device and a context of the retail application. The retail application is at a point of sale location. Heuristics can help to predict a logical flow for the retail application based on the input. For example, if a credit card is swiped after items are entered in a transaction, the credit card is most likely the tender for the transaction. It will be appreciated that the present invention can be implemented in other environments and/or locations, for example in back office settings and shipping warehouses.

0033<figref idref="DRAWINGS">FIGS. 5-7</figref> are screen shots for a single sales transaction. In <figref idref="DRAWINGS">FIG. 5</figref>, a user has scanned a bar code for an item. Input can also be provided from an RF identification receiver. The retail application determines the source and the content of the input as discussed above. Based on the source and content of the input, the input is associated with one or more objects. The input here is associated with an inventory item. A context of the retail application is also determined. In this case, the context is an initial mode. Based on the one or more objects, the context and the input, tasks are performed in the retail application. For the bar code scan, a comparison of the input is made with inventory data, a customer list and/or a receipt list. As shown in <figref idref="DRAWINGS">FIG. 5</figref>, the retail application has located and matched the input with item number 25000-010202. This item, along with any other information, is automatically added to a sales transaction and a subtotal and tax for the transaction are calculated. Furthermore the context of the retail application is updated to a sales transaction mode. In the sales transaction mode, further items that are scanned are automatically added to the transaction.

0034<figref idref="DRAWINGS">FIG. 6</figref> is a screen shot wherein a customer barcode has been scanned. The input is detected and associated with one or more objects. The context of the application, herein the sales transaction mode, is also determined. In this case, the input is compared to a database and matches a customer's information. This customer information is automatically added to the transaction. In <figref idref="DRAWINGS">FIG. 7</figref>, a user has swiped a credit card using a magnetic stripe reader. The credit card information is associated with a tender for the application. Since the retail application is still in the sales transaction mode, the tasks to be performed include posting the transaction, tendering a sale amount to the credit card, printing a sales receipt and opening a cash drawer. As a result, a full transaction can be processed in the application using only the bar code scanner and the magnetic stripe reader. A user has only needed to scan an item, scan a customer card and swipe a credit card. Thus, no manual input, for example, using a keyboard, pointer device and/or a touch panel is necessary from the user.

0035<figref idref="DRAWINGS">FIG. 8</figref> is a screen shot for processing input in a retail application. In this case, a user has scanned an item and the input has been detected as well as the context been determined. The input has matched multiple items from a data source associated with the retail application. The input has matched an item (Softball Book) and a customer (John, Smith). Both of these options are presented to the user in order for the user to quickly select either option and continue with the transaction. For example, if the user scanned the item (Softball Book), the user can easily select the softball book to be put into the transaction.

0036<figref idref="DRAWINGS">FIG. 9</figref> is a screen shot wherein a user has scanned in a sales receipt, for example by using a bar code scanner. Automatically, the sales receipt appears in a window of the retail application and various options are presented to the user. The retail application is also updated to a return void mode. Accordingly, if sale items are scanned and matched to an item in the sales receipt, a return void transaction will begin.

0037Using the present invention discussed above, input from an input device can be automatically processed in order to reduce input required by a user. The tasks that are automatically performed by an application can be based on heuristics that predict an intended action of the user. For example, given a retail point of sale context, scanning an item will automatically populate a retail transaction with the item's detail, such as a description, an item number and an amount. Further input can produce additional processing tasks for the retail application. As discussed above, the present invention can also be extended to other inputs, input devices and/or contexts. For example, in a warehouse setting, a scanned item provided from an RF device can automatically enter an application into a shipping mode and print and send a shipping notice.

0038Although the present invention has been described with reference to preferred embodiments, workers skilled in the art will recognize that changes may be made in form and detail without departing from the spirit and scope of the invention.