Card recognition system, card handling device, and method for tuning a card handling device

Description

FIELD

The disclosure relates generally to card recognition in card handling devices. More specifically, disclosed embodiments relate to automatic generation of calibration files and other improvements to card recognition systems of card handling devices.

BACKGROUND

Card handling devices (e.g., card shufflers) are used in the gaming industry for increasing the efficiency, security, and game speed in live table games, such as blackjack, baccarat, and various forms of poker. Card handling devices may perform a variety of functions including randomly shuffling one or more decks of cards in an efficient and thorough manner. In a live table game, shuffling the cards in an efficient and thorough manner may assist in preventing players from having an advantage by knowing the position of specific cards or groups of cards in the final arrangement of cards delivered in the play of the game. Additionally, it may be desirable to shuffle the cards in a very short period of time in order to reduce delay in the play of the game.

Card shufflers may include a card recognition system, which may be used to verify the contents of the card set, such as one or more decks and ensure that the card set contains all the appropriate cards, and also to detect any cards which do not belong therein. The card recognition system may also enable a card shuffler to verify the contents of the deck throughout the game play. Some known card shufflers may comprise a card recognition system that employs sensors and a hardware component that may sense the rank (2-10, jack-ace) and suit (spade, club, heart, diamond) from the face of a card and thereafter convert signals from the sensed data into vector sets. The vector sets may be compared to known vector sets of a verified deck of cards. Other known card shufflers may comprise a camera that captures an unknown image of each card entered into the card shuffler and then extracts the card rank and suit from the unknown image. The unknown image may be compared to master images of a verified deck of cards to identify the cards.

There are several different card manufacturers (e.g., Angel, Gemaco, U.S. Playing Card Company, Cartamundi, Ace, Copag, etc.) each having different types of card designs. For example, the card images (e.g., graphics) printed on the card faces may vary from one deck to the next. In addition, the size and location of the rank and suit may also vary from one deck design to the next.

In order to support each of the various possible card images, the card recognition system of the card shuffler may be loaded with a set of master images containing the rank and suit symbols of a particular deck design. The master images may be stored in memory within the card shuffler in a particular sub-directory associated with that particular deck design. For example, a sub-directory may exist for each deck type supported by the card shuffler. The process of creating these master images conventionally requires a substantial amount of manual measurement and analysis by a technician to create and load the master images for each deck type. For example, the technician may manually enter parameters into a calibration file listing different measurements and locations related to the rank and suit symbols. This process involves trial and error, and is time consuming as the technician attempts to find the right combination of parameters to use in generating the master images.

Another obstacle associated with conventional card detection devices is that card manufacturers may create new deck designs or make changes to existing deck designs. The conventional method of manually creating deck libraries becomes burdensome to technicians who not only have to create the deck libraries, but also need to update the deck libraries of card shufflers in use in the field. In addition, each individual card shuffler may be configured differently, which may require the technician to create a new calibration file for a particular machine. As a result, when the same deck library is created for one card shuffler and then simply reproduced and stored on each additional card shuffler, there may be variations during card recognition from one card shuffler to the next, even within the same model of shuffler.

Once loaded onto a card shuffler, the dealer may select the specific deck design that will be used during game play. Selecting the deck in the card shuffler determines which deck library (e.g., master images and other related files) is used for comparison with the card images captured during use. The dealer may select the incorrect deck type, often for reasons such as a lack of training or simple input error. As a result, the deck library from one deck type may be used for comparison with images from another deck type. Using the wrong deck library may result in errors in card identification.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a perspective view of a card handling device according to an embodiment of the present disclosure.

FIG. 2 is a perspective view of a card handling device according to another embodiment of the present disclosure.

FIG. 3 is a partial perspective view of a card handling device according to another embodiment of the present disclosure.

FIG. 4 is a schematic block diagram of a card processing system for a card handling device according to an embodiment of the present disclosure.

FIG. 5 is an illustration of an image captured by an imaging device of a card handling device, according to an embodiment of the present disclosure.

FIG. 6 is a raw image of a card showing the entire field of view for the imaging device.

FIG. 7A is a processed image of a card resulting in a region of interest.

FIGS. 7B and 7C are images for a rank area and a suit area extracted from the region of interest.

FIGS. 8A, 8B, and 8C show a processed image of a card, in which the imaging device had experienced dust build up on the lens.

FIGS. 9A and 9B illustrate a problem of incorrectly splitting an image that may arise during card recognition mode.

FIGS. 10A, 10B illustrate an issue that may arise when capturing an image using uneven illumination.

FIGS. 11A, 11B, 11C are raw images from the imaging device of a card handling device showing fish eye distortion caused by the imaging device.

FIGS. 12A, 12B, 12C are images for which the fisheye distortion has been reduced through mathematical stretching of the distorted image.

FIG. 13 is a flowchart illustrating a method for automatically generating a calibration file for a card detection system according to an embodiment of the present disclosure.

FIG. 14 is a flowchart illustrating a method for generating master images according to an embodiment of the present disclosure.

FIG. 15 is a flowchart illustrating a method for identifying a card rank and suit according to an embodiment of the present disclosure.

DETAILED DESCRIPTION

In the following description, reference is made to the accompanying drawings in which is shown, by way of illustration, specific embodiments of the present disclosure. Other embodiments may be utilized and changes may be made without departing from the scope of the disclosure. The following detailed description is not to be taken in a limiting sense, and the scope of the claimed invention is defined only by the appended claims and their legal equivalents. Furthermore, specific implementations shown and described are only examples and should not be construed as the only way to implement or partition the present disclosure into functional elements unless specified otherwise herein. It will be readily apparent to one of ordinary skill in the art that the various embodiments of the present disclosure may be practiced by numerous other partitioning solutions.

In the following description, elements, circuits, and functions may be shown in block diagram form in order not to obscure the present disclosure in unnecessary detail. Additionally, block definitions and partitioning of logic between various blocks is exemplary of a specific implementation. It will be readily apparent to one of ordinary skill in the art that the present disclosure may be practiced by numerous other partitioning solutions. Those of ordinary skill in the art would understand that information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof. Some drawings may illustrate signals as a single signal for clarity of presentation and description. It will be understood by a person of ordinary skill in the art that the signal may represent a bus of signals, wherein the bus may have a variety of bit widths and the present disclosure may be implemented on any number of data signals including a single data signal.

The various illustrative logical blocks, modules, and circuits described in connection with the embodiments disclosed herein may be implemented or performed with a general-purpose processor, a special-purpose processor, a Digital Signal Processor (DSP), an Application-Specific Integrated Circuit (ASIC), a Field-Programmable Gate Array (FPGA) or other programmable logic device, a controller, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A general-purpose processor may be considered a special-purpose processor while the general-purpose processor executes instructions (e.g., software code) stored on a computer-readable medium. A processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

Also, it is noted that the embodiments may be described in terms of a process that may be depicted as a flowchart, a flow diagram, a structure diagram, or a block diagram. Although a process may describe operational acts as a sequential process, many of these acts can be performed in another sequence, in parallel, or substantially concurrently. In addition, the order of the acts may be re-arranged. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. Furthermore, the methods disclosed herein may be implemented in hardware, software, or both. If implemented in software, the functions may be stored or transmitted as one or more instructions or code on computer readable media. Computer-readable media includes both computer storage media and communication media, including any medium that facilitates transfer of a computer program from one place to another.

It should be understood that any reference to an element herein using a designation such as “first,” “second,” and so forth does not limit the quantity or order of those elements, unless such limitation is explicitly stated. Rather, these designations may be used herein as a convenient method of distinguishing between two or more elements or instances of an element. Thus, a reference to first and second elements does not mean that only two elements may be employed or that the first element must precede the second element in some manner. In addition, unless stated otherwise, a set of elements may comprise one or more elements.

As used herein, the term “master image” is an image generated by a card recognition system during calibration mode that may be stored for future comparison with unknown images to identify a card during card recognition mode. The master images may include separate master images for each rank and suit of a deck. There may also be master images for other symbols, such as joker and Wagner symbols. In some embodiments, a master image may include both the rank and the suit of an individual card, such that each individual card has its own master image. A “raw image” is an image generated by a card recognition system during calibration mode and may be used to generate the master image. An example of a “raw image” is an image generated by a two-dimensional (2D) CMOS image sensor. As discussed below, the master images may be generated according to parameters stored in an automatically generated calibration file. In the context of card recognition, a “raw image” may be generated and used to generate an unknown image. The term “unknown image” is an image that is generated by the card recognition system for comparison with a master image to identify a card rank and suit during card recognition mode.

Embodiments of the present disclosure include card handling devices, card recognition systems, and related methods. It is contemplated that there are various configurations of card handling devices that may include a card recognition system according to an embodiment of the present disclosure. FIGS. 1 through 3, described below, are non-limiting examples of such card handling devices that may employ card recognition systems and methods of the present disclosure. Of course, other configurations of card handling devices are also contemplated.

FIG. 1 is a perspective view of a card handling device 100 according to an embodiment of the present disclosure. The card handling device 100 may be configured to randomize sets of cards, such as decks and sets of multiple decks of cards. The card handling device 100 may include a top surface 112 that comprises a flip-up cover 114 that, when opened, may expose a card insertion area 116 and an elevator platform 118. The card insertion area 116 may be configured to receive an input set of cards to be shuffled, counted, and/or sorted. The card handling device 100 may be configured to receive, read rank and suit, sort, and/or shuffle one or more decks of cards (e.g., standard deck of 52 cards each, 52 cards plus one or two jokers, etc.). The card handling device 100 may be particularly well suited for providing randomized decks of cards for card games, such as blackjack, poker, etc. In some embodiments, the card handling device 100 may be located adjacent to, or flush mounted into, a gaming table surface in a casino where a live card game may be played. In some embodiments, the card handling device 100 may be located at a remote location off the casino floor, which may be inaccessible to the public.

The elevator platform 118 may be configured to raise a set of shuffled cards to a level where the cards may be removed by a device user after the shuffling, reading, and/or sorting processes are completed. A body 124 of the card handling device 100 may include a card recognition system 400 (FIG. 4) therein. The card recognition system 400 may be configured to recognize the identity of the cards as the cards pass through the card handling device 100. The elevator platform 118 may include a card present sensor 120 configured to detect the presence of a card located on the elevator platform 118. Other card present sensors 430 (FIG. 4) in the card recognition system 400 may trigger the card recognition system to capture the image of the card.

The card handling device 100 may also be configured to display operational data relating to the device to a display panel 122 located on the top surface 112. An operator using the card handling device 100 may monitor the display panel 122 and view the displayed information in order to know the status of operation of the card handling device 100. Such information displayed on display panel 122 may include the number of cards present in the card handling device 100, the status of any shuffling, reading, or sorting operations, security information relating to the card handling device 100, status relating to a card verification process, or any other information about errors, or the operation of card handling device 100 that would be useful to the operator. The display panel 122 may include a user interface for the user to interact with the card handling device 100. For example, buttons 113, 115 may control operations, such as power on/off, special functions (e.g., raise elevator to the card delivery position, reshuffle command, security check, card count command, etc.), and the like.

Additional details regarding such a card handling device are described in U.S. Pat. No. 7,764,836, issued Jul. 27, 2010, and entitled “Card Shuffler with Card Rank and Value Reading Capability Using CMOS Sensor,” and U.S. Patent Application Publication No. 2008/0113700, filed Nov. 10, 2006, now U.S. Pat. No. 8,616,552, issued Dec. 31, 2013, and entitled “Methods and Apparatuses for an Automatic Card Handling Device and Communication Networks Including Same,” the disclosure of each of which is incorporated herein in its entirety by this reference.

FIG. 2 is a perspective view of another card handling device 200 according to another embodiment of the present disclosure. The card handling device 200 may include a recessed card infeed tray 222, a recessed card output tray 224, and a plurality of card shuffling compartments (not shown) arranged into a carousel structure 223 that are configured to shuffle a deck of cards inserted into the infeed tray 222 and outputted in smaller groups, such as hands and/or partial hands to the card output tray 224 during use. The shuffling compartments of the carousel structure 223 may be enclosed within a cover. A card present sensor (not shown) in the output tray 224 may generate a signal that causes the processor to instruct mechanical elements to dispense another group of cards after the last group of cards is removed. The card handling device 200 may further include a dealer display 242 that may include touch screen controls for the dealer to input commands for the card handling device 200. The card handling device 200 may be flush-mounted on a gaming table. Additional details regarding such a card handling device are described in U.S. Patent Application Publication No. 2008/0006997, filed Jul. 5, 2006, now U.S. Pat. No. 8,342,525, issued Jan. 1, 2013, and entitled “Card Shuffler with Adjacent Card Infeed and Card Output Compartments,” the disclosure of which is incorporated herein in its entirety by this reference. The card handling device 200 may further include a card recognition system (FIG. 4) that may be housed within the cover 228, and which will be described in further detail below.

FIG. 3 is a partial perspective view of a card handling device 300 according to yet another embodiment of the present disclosure. The card handling device 300 includes a card receiving area 306 that may be provided with a stationary lower support surface that slopes downwardly from an outer side 309 of the card handling device 300. The outer side 309 may include a depression configured to facilitate an operator's ability to place or remove cards into the card receiving area 306. A top surface 304 of the card handling device 300 may include a user interface 302 that may include a visual display 312 (e.g., LED, liquid crystal, micro monitor, semiconductor display, etc.), and one or more user inputs 324, 326. The user inputs 324, 326 may include one or more buttons, touch screens, etc. The interface 302 may further include additional lights and/or displays 328, 330, which may be configured to indicate power availability (on/off), a shuffler state (e.g., active shuffling, completed shuffling cycle, insufficient numbers of cards, missing cards, sufficient numbers of cards, complete deck(s), damaged or marked cards, entry functions for the dealer to identify the number of players, the number of cards per hand, access to fixed programming for various games, the number of decks being shuffled, card calibration information, etc.), or other information useful to the operator.

The card handling device 300 may further include a shuffled card return area 332. The shuffled card return area 332 may include an elevator surface 314 and card-supporting sides 334 that surround at least a portion of the elevator surface 314. In some embodiments, the card supporting sides 334 remain fixed to the elevator surface 314 during operation. In other embodiments, the card supporting sides 334 may be fixed to the frame and does not move. In some embodiments, the card supporting sides 334 may be removable. Removal of the card-supporting sides 334 may enable the operator to lift shuffled groups of cards onto a gaming table surface for use in a card game. Additional details regarding such a card handling device are described in U.S. Patent Application Publication No. 2007/0069462, filed Jul. 18, 2006, and entitled “Card Shuffler with Card Rank and Value Reading Capability Using CMOS Sensor,” now U.S. Pat. No. 7,764,836, issued Jul. 27, 2010, the disclosure of which is incorporated herein in its entirety by this reference. The card handling device 300 may further include a card recognition system (not shown), which will be described in further detail below.

Depending on the configuration of the card handling device employed, the physical configuration of the card recognition system may also vary from one card handling device to the next. For example, the placement of the imaging device may be different (e.g., different angles) from one card handling device to the next, which may result in the need to generate and maintain different deck libraries for the various types of card handling devices. According to conventional methods for generating deck libraries and master images where each step is performed manually, the need to maintain deck libraries for various types of card handling devices is increased with the different shuffler structures, which may further add to the benefits and advantages of embodiments of the present disclosure.

FIG. 4 is a schematic block diagram of a card processing system 400 for a card handling device according to an embodiment of the present disclosure. The card processing system 400 may include a card recognition system 410 and a shuffle processor 420. The shuffle processor 420 may be configured to control the shuffling of the cards, as well as the motors, rollers, etc. that move the cards through the card handling device. The card processing system 400 may further include a card present sensor 430.

The card recognition system 410 includes a card recognition processor 412, control logic 414, an imaging device 416, a memory device 418, and a latch 419. The card recognition processor 412 may be coupled with each of the control logic 414, the imaging device 416, and the memory device 418. The latch 419 may be coupled between the control logic 414 and the memory device 418. The control logic 414 may be coupled with the imaging device 416 to receive captured images from the imaging device 416. The imaging device 416 may be positioned and oriented within the card handling device, such that at least a portion of the card may be placed within its field of view when capturing an image of the card (i.e., reading the card). In some embodiments, the portion of the card within the field of view may be the upper-left hand corner of the card. Cards may be read when stationary or in motion.

The card present sensor 430 may be coupled with the card recognition system 410 to signal when a card is present for the imaging device 416 to read. In some embodiments, the card present sensor 430 may be coupled to the card recognition system 410 through the shuffle processor 420. In other embodiments, the card present sensor 430 may be coupled directly to the card recognition processor 412 or the imaging device 416.

The card recognition processor 412 may be configured (e.g., programmed) to control the operation of the card recognition system 410 to operate in either a tuning mode (i.e., generating a calibration file) or a card recognition mode (i.e., comparing an unknown image with a master image). The tuning mode may also be referred to herein as the “calibration mode.” In the tuning mode, the card recognition processor 412 may be further configured to automatically generate the calibration file used by the control logic 414 when generating master images for the complete set of reference rank and suit symbols. The card recognition processor 412 may run an operating system (e.g., Linux) having a file system. The file system may be organized in sub-directories for each deck type to which the card recognition system 410 has been tuned. The sub-directories may have files stored therein, such as a calibration file, a deck name file, and a plurality of master images, as will be discussed in more detail below. The card recognition processor 412 may be configured to instruct the imaging device 416 to capture the image (e.g., responsive to a signal from the card present sensor 430). The card recognition processor 412 may also be configured to communicate information to input and output devices (not shown), such as a display, operator inputs, etc.

The control logic 414 may include an FPGA or comparable hardware component configured to identify cards by rank and suit. The control logic 414 may be configured to process a raw image data captured by the imaging device 416, the raw image data being processed according to one or more parameters stored in the calibration file to generate the rank images and the suit images used as master images during the tuning mode. The control logic 414 may be further configured to generate the unknown images used during the card recognition mode. In addition, during card recognition mode, the control logic 414 may be configured to compare the generated unknown rank and suit images with master rank and suit images to determine the identity (ID) of the card.

The imaging device 416 may include a camera (e.g., 2D CMOS imager) configured to take a two-dimensional image of its field of view. The imaging device 416 may include an analog camera or a digital camera with a decoder or receiver that converts received radiation into signals that can be analyzed with respect to image content. The signals may reflect either color or black-and-white information, or merely measure shifts in color density and pattern. The imaging device 416 may include one or more lenses to focus light, mirrors to direct light, and additional radiation emitters to assure sufficient radiation intensity for imaging by the imaging device 416. For example, the additional radiation emitters may include LED light sources (not shown) to illuminate areas of a card being imaged. Although a white light source may sometimes be adequate to capture gray scale data from red and black print on cards, a green light source may be an efficient source of illumination for capturing black and white data from both red and black print on cards.

The memory device 418 may be configured to store the captured raw images for each of the cards of the deck. The raw images may include rank and suit symbols of the corresponding card. The raw images may be read in by the imaging device 416 to be used by the card recognition processor 412 during tuning mode to generate the calibration file. The raw images may further be provided to the control logic 414 during tuning mode to generate a set of master images. The memory may have N locations available for storing the raw images for each card, wherein N is any positive integer. For most standard decks, N may be 52. In some embodiments, N locations may include additional locations for jokers, special cards, blank cards, or other symbols. Decks of cards having more or fewer than 52 cards (e.g., cards with certain cards added or removed) are also contemplated. In addition, the calibration file and master images may be generated using a sub-set of all cards of the deck. In other words, a raw image may not be captured for each and every card in the deck so long as at least one raw image is available for each rank and each suit in the deck. As a result, N may be fewer than the total number of cards in the deck.

The latch 419 may be configured to select which location in the memory device 418 that a particular raw image should be stored in. For example, as the raw image for a card is successfully stored, the latch 419 may increment so that the raw image for the next card may be stored in the next location in memory device 418. If the raw image for a card is not successfully stored, the latch 419 may not increment.

The tuning mode may be employed to tune a card recognition system 410 for use with a particular deck of cards. The deck of cards may be inserted into the card handling device and the rank and suit information may be read by the card recognition system 410. Information from each card of the deck may be read into the card recognition system 410. In other words, the imaging device 416 captures a raw image for at least a portion of some of the cards (e.g., rank and suit symbols) of the deck to be used for tuning the card recognition system 410. In other embodiments, a larger portion of the card face (e.g., the entire card face) may be captured by the imaging device 416. The raw images are stored in the memory device 418. At the close of reading all or a portion of each card in the deck, the memory device 418 may have a raw image stored in memory device 418 for each card of the deck. In some embodiments, the cards may be read in a predetermined order, while in other embodiments, the cards may be read in any order. At this point, the raw images stored in the memory device 418 may not be processed, but represent full images for the entire field of view of the imaging device 416, including each rank and suit symbol.

The card recognition processor 412 may be configured to perform an image processing analysis of the raw image identifying measurements (e.g., sizes of areas, coordinates, dimensions, etc.) related to at least one of a rank area around a rank of the card, and a suit area around a suit of the card, an area around both the rank and the suit, and automatically generate a calibration file based, at least in part, on the image processing analysis, as discussed in more detail below. The card recognition processor 412 may perform an image processing analysis to automatically identify a size and location of the rank and suit symbols of at least one card. As an example, the card recognition processor 412 may perform a “blob” analysis on one or more of the raw images stored in the memory device 418. An example of such an image processing program capable of being programmed to perform the analysis described herein includes OpenCV (Open Source Computer Vision Library) developed by Intel Corporation of Santa Clara, Calif. Other blob analysis software may also be employed, such as MATLAB® developed by Mathworks of Natick, Mass.

The blob analysis may be configured to locate “blobs” within a selected raw image. A blob may include a point and/or a region in the image that differs in some property. For example, the blob analysis may locate black regions of a black-white image or may analyze intensity of a grayscale image. Although the term “raw image” is used during the description of the blob analysis, the image that is analyzed may be processed. For example, the card recognition processor 412 may convert the raw image to black and white, may crop (or ignore) the raw image to a region of interest around the card that is of a smaller size than the field of view of the imaging device 416, etc. prior to performing the blob analysis. In this context, the term “raw image” is intended to mean that the image is not a master image, and not necessarily that no processing of the image has been performed.

The blob analysis may be used to locate a number of blobs from the selected raw image, which may be further analyzed to determine the locations and measurements (e.g., in pixels) for a rank area 508 (FIG. 5) and suit area 510 (FIG. 5) as well as other related parameters that are part of the calibration file. As an example, the blob analysis may determine an initial number of blobs within the raw image. The initial number of blobs may be relatively large (e.g., 3000 blobs) based on the artwork on the card that is present within the field of view of the imaging device 416. The blob analysis may also return a location (e.g., centroid) of each blob within the raw image, as well as the measurements (e.g., height, width, etc.) of each blob. Because the rank and suit of most cards may be expected to have at least a minimum size, relatively small blobs may be ignored by the card recognition processor 412 for purposes of finding the rank and suit. In addition, because the rank and suit of most cards may be expected to be located near the corners of the cards, blobs that are outside of that expected region may also be ignored. As a result, the remaining blobs left to be analyzed should include the rank and suit of the card.

In some embodiments, finding the “10” number rank (i.e., excluding other cards, such as jack, king, etc.) may be used as a basis for defining parameters for the rank area and suit area, because of one or more unique qualities about the 10 rank that may be helpful to identify the rank. For example, the 10 rank may be recognizable because the 10 rank has two relatively large blobs that are side by side. Each of the two blobs may have approximately the same location on the Y-axis for the centroid, along with approximately the same height. In addition, the blob analysis may verify that one blob is narrow (the “1”) whereas the other blob is wide (the “0”). The 10 rank may also be useful in defining the measurements of the rank area because the 10 rank may have the largest area of the various ranks.

The location and measurements defining the suit area may be determined by locating and defining an area of a relatively large blob near the 10 rank. The suit may also be expected to be the blob located below the rank (in the Y direction) for most decks. As a result, the card recognition processor 412 may use a blob located below the 10 rank for defining the measurements of the suit area in the calibration file. Thus, from the blob analysis the measurements for the rank area 508 and the suit area 510 may be obtained. The final values stored in the calibration file may include some padding, which may compensate for the potential of variations in card position or orientation. Thus, the card recognition processor 412 may automatically generate a calibration file having parameters associated with locating the rank and suit within an image or partial image. Examples of parameters that may be stored in the calibration file are discussed below with reference to FIG. 5. The calibration file may be stored in a file system in a memory (e.g., non-volatile memory) associated with the card recognition processor 412. The calibration file may also be stored in memory (e.g., volatile memory) associated with the control logic 414.

Using the calibration file, the control logic 414 may process the raw images stored in the memory device 418 to generate the master images to be used in the card recognition mode. In some embodiments, only a selected portion of the raw images may be fed back from the memory device 418 into the control logic 414 for generating the master images. In some embodiments, an image for each rank from one of the suits may be used to generate the master image for that rank. For example, the ace of diamonds may be used to obtain the master image associated with the ace rank, while the other ace cards (e.g., ace of spades, ace of hearts, ace of clubs) may be ignored. The master images for the other ranks may be generated in a similar manner. While generating the master images for the ranks, certain card images may be selected to generate a master image for each suit as well. In other embodiments, each raw image may be used to obtain a master image for each rank and suit. As a result, a plurality of master images may be generated for each rank and suit. For example, four separate master images may be created for the ace rank (i.e., one ace image from a card for each suit). The card recognition processor 412 may then analyze each of the master images for that rank to determine which of the master images is desired to be used as the ultimate master image during the card recognition mode. In other words, the card recognition processor 412 may choose what it considers “the best” image from among a plurality of images to select the master image for a particular rank or suit. The best image may be determined by comparing against each of the other master images to obtain a score that is most dissimilar to the others so that the separation between master images is the greatest. Other factors or determinations may be used for, or contribute to, the determination of which master image is to be used as the master image for a particular rank or suit.

In some embodiments, the card recognition processor 412 may create the master images at the same time that the calibration file is generated. As a result, the blob analysis may be used by the card recognition processor 412 to locate, measure, and crop the master images before the calibration file is generated.

After the master images are generated, the card recognition processor 412 may associate the master images with the appropriate rank and suit. The master images may also be stored in the file system of the memory associated with the card recognition processor 412. In some embodiments, the master images may be associated with the corresponding rank and suit by having the cards read in a predetermined order using a sorted deck. Thus, each master image is assigned its rank or suit according to the order the master image was saved in the memory device 418. Such an embodiment, however, may rely on the card manufacturer or technician (or dealer, pit boss, etc.) who inserts the deck into the card handling device to insert a sorted deck. Inserting an unsorted deck into such an embodiment may result in improper associations between the proper ranks and suits.

In some embodiments, the card recognition system 410 may be configured to make the proper associations even with an unsorted deck. For example, the proper associations for the ranks and suits may be determined from a secondary analysis of the master images. For example, the card recognition processor 412 may be configured to analyze the curvature of the rank and suit symbols in the master images to make the associations with the appropriate ranks and suits. In some embodiments, the master images may be compared with each other, such that a score may be determined between each master image. In other words, the master images may be associated with the appropriate ranks and suits indirectly from other master images rather than direct association based on the expected identity.

For example, a score may be determined for a comparison between the master images for the 1 rank and the 2 rank, the 1 rank and the 3 rank, the 1 rank and the 4 rank, etc. Similarly, a score may be determined between the master images for the 2 rank and the 3 rank, the 2 rank and the 4 rank, etc. Scores for the other ranks (3-10, J, Q, K, A) may be determined as well. Of course, at this point the master images are unassociated with any particular rank, and the actual identity of the master image may not yet be known to the card recognition processor 412. The method of comparison includes determining a number (or percentage) of matched pixels, determining a number (or percentage) of unmatched pixels, comparing a shape of an edge of a symbol, or other methods of comparison.

Of course, the scores for comparisons of different master images would be dissimilar and would not result in a match. However, the score for a comparison of the 1 rank and the 7 rank may be more similar to each other than the score between the 1 rank and the 2 rank. In fact, each card rank may have a different rank that may result in a closest secondary match. For example, for some decks, the following table may represent the next best match for various ranks. The score represented in Table 1 below is a percentage of pixel matching as described in further detail below.

TABLE 1

Next Best

Rank
Match Rank
Score (%)

A
J
20

2
4
20

3
5
15

4
J
17

5
6
9

6
5
12

7
4
19

8
6
17

9
J
20

10
Q
18

J
4
17

Q
4
17

K
J
19

The next best matches shown in Table 1 is to be understood as an example for one style of card deck. Similarly, the scores shown in Table 1 may be approximates. Of course, as decks may vary from one design to the next, the next best match and the score may also differ from one deck to the next. In addition, the analysis regarding the secondary comparisons of master images may also consider the expected matches beyond the next best match. In other words, the accuracy may be improved if the third best match, the fourth best match, etc., may be considered. In some embodiments, a specific master image may be used as a baseline master image to determine the associations for the other master image. For example, the blob analysis may be used to identify a 10 rank by searching for the unique characteristics of the 10 rank. The master image for the 10 rank may then be used to compare with the unassociated master images. In other words, the 10 rank is compared with an unassociated rank master image to obtain a first score, the 10 rank is compared with another unassociated rank master image to obtain a second score, and so on. Each rank may have a score that is different with respect to a comparison with the 10 rank. These different scores may be associated to a corresponding rank based on the expected relative match to the 10 rank. Other ranks may be used as the baseline master image. In some embodiments, the deck may be required to be only partially sorted, such as requiring the technician to have a specific card as the first card read from the deck. For example, the queen of hearts may be required to be the first card read from the deck. The master images for the queen rank and the hearts suit may then be used as the baseline master image similar to the process described above for using the 10 rank.

As a result, the master image for each rank may be compared with the other master images of the remaining ranks with the score for each comparison being saved. The scores from these secondary comparisons may be analyzed to determine the proper associations for the master images. The master images for the suits may be associated with the appropriate suits in a similar manner. For example, as the cards may be read in a predetermined order, the master images may be associated with the appropriate suit based on the known position of that suit. In other embodiments, secondary analysis may be used to determine the identity of the suit for the master image, such as analyzing the curvature of the suit shapes or from comparisons of the other master images to determine the identity from secondary relationships of non-matching master images. Such secondary analysis may be beneficial for situations when the deck may not be sorted in any particular order. Such secondary analysis may also be performed for other reasons, such as to verify the order of a sorted deck (e.g., the system may still require a sorted deck, but these secondary relationships may provide a way alert the operator that the deck was not sorted properly), verify a correct deck (e.g., 52 unique cards exist), and verify quality of the total scan (e.g., identify dirty cards).

Once the master images have been created and properly associated with the appropriate ranks and suits, the card recognition system 410 may be said to be “calibrated” as to the particular deck of cards. In a standard deck of cards, 18 master images may be stored: one master image for each rank (2-10, J, Q, K, A) and suit (diamond, heart, spade, club), as well as a master image for a joker. The master image for a joker may be stored as a rank. Other symbols may also be printed on the face of some of the cards. For example, a “Wagner” symbol is a special symbol printed on some of the cards for a deck that is used in certain card games in order to assist in game play. For example, a Wagner is typically useful during blackjack by being printed on the face of each card having a value of ten (i.e., each 10 rank, jack rank, queen rank, king rank) and eleven (i.e., each ace rank) to assist with the determination that the dealer has a “21.” The Wagner symbol is often a polygon shape that is located between the rank and the top of the card. A master image for a “Wagner” symbol may be created and stored, while in some embodiments the Wagner symbol may simply be ignored by the card recognition processor 412. Other special symbols may also be treated similarly.

The master images may be stored as image files (e.g., bitmap files) in the subdirectory of the file system of the card recognition processor 412. The master images may further be loaded into the memory associated with the control logic 414 for comparison with the unknown images during card recognition mode. The master images may be separate files stored in the same subdirectory of the file system as the calibration file (e.g., a text file). In some embodiments, the calibration file may be combined in a file with the master images such that a single file may include image data and the calibration parameters.

During the card recognition mode, each time a card is moved past the card present sensor 430, the imaging device 416 may capture an unknown image of the card. The control logic 414 may compare the unknown image against the set of master images to determine the identity of the card. For example, the control logic 414 may compare the unknown image for the rank against each of the thirteen master images for the ranks (2-10, J, Q, K, A). The control logic 414 may also compare the unknown image for the suit against each of the four master images for the suits (diamond, heart, spade, club). Based on the results of these comparisons, the control logic 414 may determine the identity of the card by selecting the symbols with the highest degree of correlation. The control logic 414 may perform a plurality of processes that at least partially overlap in time. As a result, the unknown image may be compared with a plurality of different master images at the same time.

In one embodiment, the comparison may include comparing like pixels by performing an inverted XOR operation of the corresponding pixels of the unknown image and the master image. The result of the inverted XOR operation may be summed to obtain a score (e.g., a numeric sum). For example, a black pixel (1) compared with a black pixel (1) may add to the score, a white pixel (0) compared with a white pixel (0) may add to the score, while a black pixel (1) compared with a white pixel (0) may not add to the score. A larger score may indicate a greater number of matching pixels. The score may be represented as a raw number of pixels or as a percentage of the total number of pixels of the images. For example, a score of 100% may be a perfect pixel to pixel match of the unknown image and a master image. Of course, a perfect match may not be reasonable to expect, and a match may still be found for a score having a percentage less than 100%. As a result, a minimum threshold may be set for what the card recognition system 410 may consider a match. In some embodiments, the inverted XOR operation may be implemented as another logic operation. In some embodiments, like pixels may be added and dissimilar pixels may be not counted, while in other embodiments, dissimilar pixels may be added and then subtracted from the total number of pixels to determine the score.

In another embodiment, the comparison may include comparing cross correlation values of matrices from the master image and the unknown image. Such a cross correlation function may, however, require a larger amount of computational resources than embodiments that include a more simple summation.

The card recognition system 410 may generate either a valid card ID (if a match is determined) or an indication of an error (if a match is not determined). For example, the control logic 414 may return a score associated with the comparison of the unknown image with each master image. To obtain a “match,” the score may be required to be above a minimum error threshold. In some situations, the scores for more than one master image may be above the minimum error threshold. The highest score, however, will be selected as the valid card ID. In other words, the master image used in the comparison that resulted the highest score may be selected as the card ID (assuming the score is above a minimum error threshold). A deck may also be flagged as being invalid if a pre-determined (e.g., 6) number of errors (e.g., misread cards) occur during card recognition. In some embodiments, the score may be based on the dissimilar pixels. Thus, a match would occur for the lowest score of dissimilarity (0% for a perfect match) above a maximum error threshold rather than being based on the score of similar pixels.

In some embodiments, the card handling device 400 may display on a display device an image of the card from the imaging device 416 to be viewed by the operator during imaging. Such image displayed on the display device may be for verification that the valid card ID is the correct determination, or as a way to see that the card that produced an error indication.

FIG. 5 is an illustration of an image 500 taken by an imaging device 416 (FIG. 4) of a card handling device, according to an embodiment of the present disclosure. The image 500 is taken from a field of view 502 for the imaging device. The field of view 502 of the imaging device defines what data is able to be captured by the imaging device 416 for the image 500. For example, the imaging device 416 may be located within the card handling device to capture at least a portion of a card 506 passing through the card handling device.

The image 500 may be a grayscale image having a resolution determined by the imaging device 416 (e.g., 320 pixel×240 pixel resolution). A grayscale pixel may have large number of different values, whereas a black and white pixel may have the value of either a 1 (black) or a 0 (white). When processing the image 500, the image 500 may be converted from a grayscale image to a black and white image. For example, the control logic 414 (FIG. 4) may employ a method to assign grayscale pixels below a certain threshold value to a 0 (white) and grayscale pixels above a certain value to a 1 (black). Of course, different resolutions and color schemes may be employed, as desired. For example, a full color image may be captured by the imaging device 416; however, it should be appreciated that lower resolution and black and white conversion may result in smaller file sizes and reduced processing time. It is contemplated, however, that the color (e.g., red or black) of the rank or suit may be one more distinguishing factor to assist in card recognition even though the color is treated as irrelevant in many of the examples described herein. Adding color analysis may increase the accuracy of identifying ranks and suits; however, it may come at the expense of additional complexity and/or processing time.

The field of view 502 further includes a region of interest 504. The region of interest 504 is the portion of the field of view 502 that includes the rank and suit of the card 506. In the example shown in FIG. 5, the rank is a queen (Q) and the suit is a spade located in the upper left-hand corner of the card 506. Of course, the rank and suit may be located in other positions on the face of the card 506.

Focusing the analysis of the card to the region of interest 504 may reduce the processing needed for finding a rank area 508 and a suit area 510. The rank area 508 and the suit area 510 may define an area around the rank and suit. The area may be a box, a rectangle, or other shape. The region of interest 504 should be large enough to completely contain each rank and suit symbol in the master set with some additional area added to account for variability in the acquired signal and variability in card position. Thus, the region of interest 504 may be located by measuring a size and location of each rank and suit box created by the system, and identifying an area in which every rank and suit symbol in the master set appears during the training and calibration phase. Because there may exist some variation in the location of the rank and suit symbols throughout the deck, the rank and suit boxes for the entire deck may be analyzed to determine a minimum number of pixels (in both X and Y directions) to consider to ensure that the rank and suit symbols fall within the region of interest 504. In some embodiments, the minimum number of pixels may be used, whereas in other embodiments some padding (i.e., extra pixels) may be added to allow for variations (e.g., card orientation) during actual use.

In some embodiments, the region of interest 504 may be determined by adding a fixed dimension in the X-direction from the right side of the image, while the dimension in the Y-direction may be determined by determining the furthest location from the top of the card 506 in the Y-direction to the bottom of the suit symbol. Because the rank and suit symbols may vary in location, the furthest location may be determined after analyzing the locations of all suits from the blob analysis. The final dimensions of the region of interest 504 may include some padding on these measurements in each direction to compensate for slight variations in card orientation during use. Other methods for defining the boundaries for the region of interest 504 are also contemplated such that the region of interest 504 has a suitable size and location to ensure that rank and suit symbols within the deck will be within the defined region of interest 504 even if the locations of the rank and suit symbols may vary somewhat.

When the measurements for the region of interest 504 are stored in the calibration file, the location and dimensions for the region of interest 504 may be fixed from one card image to the next when generating master images as well as for unknown images during card recognition.

A rank area 508 and a suit area 510 may be defined to surround the rank and suit, respectively. The rank area 508 has a rank width 516 and a rank depth 518, which may be measured in pixels. The suit area 510 has a suit width 520 and a suit depth 522, which may be measured in pixels. The rank area 508 and the suit area 510 may be separated at a split region 509. The split region 509 is a region (e.g., point, line, etc.) that is between the rank and the suit of the card 506, which may be used to be a starting point for measuring the rank area 508 and the suit area 510. In some embodiments, the split region 509 may be ignored by finding the rank and suit symbols, such as by blob analysis, and then applying the parameters from the calibration file if the calibration file exists. For tuning mode, the blob analysis may be used to automatically generate the calibration file.

As discussed above, during the tuning mode, the measurements of the rank area 508 and the suit area 510 may be automatically generated for each master symbol based on an image processing analysis of the image 500. In addition, the region of interest 504 measurements may be stored in the calibration file. As a result, the calibration file may also include the parameters that are used to generate master images for the rank and suit. During card recognition mode, the parameters stored in the calibration file for defining the measurements of the rank area 508 and the suit area 510 may be used to generate the unknown images. The unknown images may be compared with the master images for determining the identity of an unknown card passing through the card handling device. The rank area 508 and the suit area 510 may completely encompass the rank and the suit of the card 506. Having a good fit for the rank and suit may reduce the amount of white space in the rank area 508 and the suit area 510, which may provide a better separation and a more accurate match when comparing master images and unknown images.

As discussed above, various parameters may be stored in the calibration file in order to assist the generation of the master files during tuning mode and the generation of the unknown files during card recognition mode. These parameters may be determined by the card recognition processor 412 (FIG. 4) and stored in the calibration file. The calibration file may include the parameters for the specific card deck. Such parameters may include V_lines 512, H_lines 514, rank width 516, rank depth 518, suit width 520, suit depth 522, H_start 524, V_start 526, and V_offset 528. These parameters may be associated with various locations and measurements within the image 500.

V_start 526 is the shift in the X-axis for the finding the region of interest 504. V_start 526 may be based on the changes in the camera mount position relative to the calibration target. V_start 526 may be set internally by the control logic 414 or the card recognition processor 412. V_start 526 may be approximately the same for all shufflers of the same model, but may account for small changes in camera mount position between devices.

V_offset 528 is the pixel offset that is added along the X-axis to V_start 526 to find the edge of the region of interest 504. The region of interest 504 may be defined just beyond the edge of the card 506 (e.g., by a few pixels) into the dark background. The V_offset 528, which is a relative offset used to shift the card image further leftward into the region of interest 504. The V_offset 528 may be determined by checking across all card images that the region of interest 504 edge is just a few pixels away from the card next to each rank/suit image, as the card recognition processor 412 uses a black-to-white transition algorithm to find the edge of the card. In order to compensate for some rotation-caused shifting of the cards, the V_offset 528 may be reduced by a number (e.g., 4 pixels) from the minimal value found across all cards.

H_start 524 is a relative offset along the Y-axis that is used to shift the card image to define the upper portion of the region of interest 504. The higher the value of H_start 524, the greater the shift. H_start 524 corresponds to a shift of the region of interest 504 downward from the top of the card 506. H_start 524 may be determined by finding the distance to the black-to-white transition at the top edge of the card 506 and reducing by a number (e.g., 4 pixels) to compensate for some shifting in the cards.

V_lines 512 is the number of pixels in the region of interest 504 along the X-axis. In other words, the V_lines 512 is the width of the region of interest 504. V_lines 512 may be determined by taking the maximum of the center-most edge coordinate for the rank and suit across all cards, and then subtracting V_start 526 and V_offset 528.

H_lines 514 is the number of pixels in the region of interest 504 along the Y-axis. In other words, the H_lines is the depth of the region of interest 504. H_lines 514 may be calculated by determining the maximum coordinate across all card images for the edge closest to the bottom of the suit.

The point having the coordinates (V_start+V_offset, H_start) may be used to define the upper left-hand corner of the region of interest 504. The size of the region of interest 504 may be defined by the V_lines 512 and H_lines 514. As a result, a smaller window (i.e., the region of interest 504) may be output in order to look at a selected region within the field of view 502 during operation.

Additional parameters may be stored in the calibration file that relate to the operation of the imaging device. Such additional parameters may include exposure, camera gain, brightness, camera speed, camera resolution, etc., which may be read from registers of the imaging device 416.

Additional parameters may be stored in the calibration file that relate to the deck or the operation of the card recognition mode. Such additional parameters may include preload sets, split_algorithm_select, err_min_rank, err_min_suit, a deck number, and a library number.

Split_algorithm_select may be used to indicate the direction that the control logic 414 begins its scan for finding the split region 509 in the unknown image. For example, if there is a non-rank blob (e.g., Wagner symbol or artwork) between the rank and the top edge of the card 506, the split_algorithm_select may be set to 1 to instruct the control logic 414 to scan the region of interest 504 from bottom to top when finding the split region 509. The split_algorithm_select may be set to 0 to instruct the control logic 414 to scan the region of interest 504 from top to bottom when finding the split region 509.

Err_min_rank is a parameter used to identify unknown rank images. For example, if the score is less than the err_min_rank, the master rank image is reported as being a non-match to the unknown rank image. Err_min_suit is a parameter used to identify unknown suit images. For example, if the score is less than the err_min_suit, the suit image is reported as being a non-match. During a summing determination, a perfect match would have a 100% match rate between the unknown image and a master image. Because of some variations, this may not be the case. The err_min_rank and err_min_suit are may be set to have values equating to a desired error threshold (e.g., 75%) of the potential total matches in the summing determination. For example, if a rank area 508 or a suit area 510 has 32 pixels, the err_min_rank and the err_min_suit may be set to 24 (e.g., 24/32=0.75). As a result, if the percentage of pixel matches falls below this percentage (e.g., 75%), the rank and/or suit may be considered a non-match against the master image. If more than one master image provides a score that exceeds the match threshold (75%) when compared to the unknown image, then the master image having the highest score may be considered the matching symbol. If none of the master images provide a score that exceeds the match threshold (75%) when compared to the unknown image, then the unknown image may remain unknown and an error alert may be provided to the dealer. Situations in which the score may be below the match threshold may include an error in the tuning process, an error in the image capture of the unknown image, a card being turned over, a card being from another deck, a damaged or dirty card, the card handling device being dirty, etc.

The deck number may be a unique number associated with a particular calibration file in order for the dealer to select to be used in the future. The library number may represent the number of times that the calibration file has been updated. The preload sets parameter may represent a number of image shifts that are done during correlation for an image pair (e.g., an unknown image and a master image). In some embodiments, the deck number and library number may be stored in a separate deck name file that is different than the calibration file.

FIG. 6 is a raw image 600 of a card 606 (three of hearts) showing the entire field of view 602 for the imaging device 416 (FIG. 4). The raw image 600 shown in FIG. 6 may be a grayscale image.

FIG. 7A is a processed image 700 of a card 706 (seven of diamonds) resulting in a region of interest 704. The processed image 700 shown in FIG. 7A may have been processed from a raw image. For example, the processed image 700 may be cropped to the region of interest 704, whereas the original raw image may have been for the entire field of view of the imaging device 416 (FIG. 4). In addition, the processed image 700 may be a black and white image, whereas the original raw image may have been a grayscale image or a color image.

FIGS. 7B and 7C are the images for a rank area 708 and a suit area 710 extracted from the region of interest 704 (FIG. 7A). The measurements of the rank area 708 and the suit area 710 may be determined during tuning mode and stored in the calibration file as discussed above. Also during tuning mode, the rank area 708 and the suit area 710 may be stored as the master images. During card recognition mode, the raw image may be an unknown image, and the rank area 708 and the suit area 710 may be the unknown images used for comparison of the master images. Although FIGS. 7B and 7C show the rank and suit to be shifted to the left and upper edges of the rank area 708 and the suit area 710, there may be some padding (i.e., white space) on each edge. In order to maintain a consistent location of the rank and suit in the images, the rank and suit may be shifted toward one of the corners as shown.

FIGS. 8A, 8B, and 8C show a processed image 800A, 800B, 800C of a card 806A, 806B, 806C, in which the imaging device 416 (FIG. 4) had experienced dust build up on the lens. Dust may accumulate on the lens over the lifetime of use of the card handling device. For example, FIG. 8A is an example of dust build up after a first number cycles, FIG. 8B is an example of dust build up after a greater number cycles, and FIG. 8C is an example of dust build up after many additional cycles.

When the imaging device 416 accumulates dust, the raw image may become a different shade of gray in terms of the grayscale image. The white area may become a little more gray and the black area may become a little less black. As discussed above, each pixel in a grayscale image has a value between white and black. When converting a grayscale image to a black and white image, a threshold value may be used as the cutoff point between black and white. As a result, the white area of the processed black and white image may become smaller as the camera accumulates dust.

The control logic 414 (FIG. 4) may be configured to correct for dust build up. In one embodiment, rather than setting a fixed threshold used to convert a grayscale image to a black and white image, the threshold value may be dynamically changed over time to compensate for dust build up. As an example, the threshold may change to have different levels over time. The threshold may be used to convert the grayscale image to a black and white image during the tuning mode. The threshold may be set to a first level during tuning mode, and to a second level during card recognition mode. As an example, the dynamic changes (from the first level to the second level) may be performed to compensate for changes in lighting conditions. It is also contemplated that the dynamic changes may be based on other conditions. In some embodiments, the number of cycles may be counted and the threshold may dynamically change with the number of cycles. In some embodiments, one or more data filters may be employed to further improve the processed image during conversion from grayscale to a black and white image.

FIGS. 9A and 9B illustrate a problem of incorrectly splitting an image that may arise during card recognition mode. In particular, incorrectly splitting an image may often occur when the imaging device 416 (FIG. 4) is not clean or if the actual card itself has a mark. As a result, a blemish 901 may appear on image 900 that is used to obtain the rank area and the suit area for the card 906. The blemish 901 may be mistaken for either the rank or suit, often because the control logic 414 may first look for the split between the rank and suit as a starting point. As shown in FIG. 9, the control logic 414 may mistake a space 907 between the blemish 901 and the rank as the split point. As a result, the control logic 414 may generate a box 902 as either the rank area or the suit area, but which does not include the proper portion of the image 900. Correcting for dust build up may result in fewer errors in splitting the image.

In some embodiments, the control logic 414 may not create the unknown images based on finding a split between the rank and suit symbols. Rather, the control logic 414 may compare the master images to the unknown image generated from the entire field of view of the imaging device 416 during card recognition mode. In other words, the entire field of view (or a portion thereof) may be used as the unknown image, which may be larger than the master image. In such an embodiment, the control logic 414 may perform a plurality of comparisons of each master image and the unknown image by scanning the master image in the region of interest. For example, the master image may begin this comparison in the top left corner of the unknown image and scan across pixel by pixel to the top right corner. The master image may then be moved down a row of pixels moving along the pixels of that row, and so on. If at some point during this scanning, a score results in a match, the card may be identified.

FIGS. 10A, 10B illustrate an issue that may arise when capturing an image using uneven illumination and fisheye distortion. FIG. 10A is a raw image 1000A using a grid for illustration. FIG. 10B is a processed image 1000B showing the grid after conversion from grayscale to black and white. As shown in FIGS. 10A and 10B, uneven lighting may cause some portions of the raw image 1000A to appear dark when they are actually white. As a result, recognition may not be as accurate due to a lower score when comparing images, or for more serious problems such as incorrect splitting (FIGS. 9A, 9B).

Uneven illumination may be corrected in a similar manner to the correction for dust build up on the imaging device 416 (FIG. 4). For example, the control logic 414 may be configured to dynamically change the threshold value used in the conversion from the grayscale image to the black and white image. The dynamic change may be responsive to a number of cycles of the imaging device, a light sensor detecting illumination changes, or other changes in the environment. In some embodiments, one or more data filters may be employed to further improve the processed image during conversion from grayscale to a black and white image.

FIGS. 11A, 11B, 11C are raw images from the imaging device 416 (FIG. 4) of a card handling device showing fish eye distortion caused by the imaging device 416. In some embodiments, the small measurements within the card handling device and proximity of the imaging device to the card may require a fisheye lens to be used with the imaging device. The fisheye lens may provide a wide field of view for the imaging device that is sufficient to view the rank and suit for different types of cards. For example, some decks may have relatively large ranks and suits that take up a large area of the corner of the card. In addition, the location of the rank and suit may vary from one deck to another.

The fisheye lens may introduce fisheye distortion in the raw images taken by the imaging device. For example, FIG. 11A shows a raw image 1100A of a grid in which the squares of the grid are equal sizes. However, as shown in FIG. 11A, the fisheye distortion causes the squares of the grid to appear to be different sizes throughout the raw image 1100A. Near the center of the raw image 1100A, the fisheye distortion may not be as pronounced; however, near the edges and corners of the raw image 1100A, the fisheye distortion becomes more pronounced.

FIGS. 11B and 11C are raw images 1100B, 1100C taken with an imaging device with a lens having fisheye distortion. When comparing the diamond suits in FIGS. 11B and 11C, it can be seen that the shapes of the diamond vary because of the different placement of the diamond ranks within the field of view of the imaging device. For example, the diamond suit in FIG. 11B is smaller than the diamond suit in FIG. 11C because it is located further from the center of the field of view. In addition, the ace (A) rank in FIG. 11B is mostly centered within the field of view. The king (K) rank in FIG. 11C, however, is off-center and is smaller near the top of the rank compared with the bottom of the rank. As a result, the more distortion experienced by the ranks and suits in an image, the greater the effect the distortion may have for the score from the comparison with the master images for the ranks for determining the card ID. In some situations, fisheye distortion has caused a misidentification of the card ID (e.g., the suit is identified as a spade when the suit was really a diamond).

The card recognition system 410 (FIG. 4) may be configured to correct for such fisheye distortion. In other words, the fisheye distortion may be reduced, such as by stretching the distorted image. In some embodiments, the image pixels may be translated from the raw image to a corrected raw image according to a correction table (i.e., look-up table). In some embodiments, the image pixels may be mathematically translated from the raw image to a corrected raw image.

FIGS. 12A, 12B, 12C are images 1200A, 1200B, 1200C for which the fisheye distortion has been reduced through mathematical stretching of the distorted image. As shown in FIG. 12A, the grid (which was distorted in FIG. 11A) has squares that are now substantially the same size. In FIG. 12B, the diamond suit (which was distorted in FIG. 11B) is now substantially symmetrical even though the diamond suit is off-center and proximate the edge of the image. In FIG. 12C, each of the king rank (K) and the diamond suit (which were distorted in FIG. 11C) are no longer distorted.

FIG. 13 is a flowchart 1300 illustrating a method for automatically generating a calibration file for a card detection system according to an embodiment of the present disclosure. The calibration file may be generated for a deck of cards selected by an operator prior to the card handling device being set up on location. In some embodiments, an operator (e.g., technician, dealer, pit boss, etc.) may be permitted to initiate the generation of the calibration file on location on an as-needed basis. One benefit of generating the calibration file on location may be that the parameters for the calibration file may be determined for the actual deck that is used (rather than just the same type of deck), for the actual imaging device, and under the actual lighting conditions. The operator may also select a name for the deck of cards so that the deck of cards may be used later without the need to retrain the card recognition system for that particular deck. Rather, the operator may select the deck for which a calibration file and master images have already been generated. Conversely, the operator may select a calibration file that was automatically generated in a previous training event when planning to use the same card type.

At operation 1310, raw images for the cards in the deck may be captured. For example, the deck of cards may be inserted into a card handling device with each card being read into the card recognition system of the card handling device. An imaging device may capture a raw image for each card of the deck. As discussed above, the deck may be pre-sorted as desired; however, in some embodiments, the deck may be in any order for capturing the raw images of each card. As a result, the operator may not need to manually sort the cards in the deck prior to inserting the deck into the card handling device, which may reduce time and errors in calibrating the card recognition system. In some embodiments, a new set of cards may be read in original deck order to calibrate the card recognition system.

At operation 1320, the raw images may be analyzed to determine the parameters (e.g., measurements of rank and suit areas, etc.) to be stored in the calibrate file. For example, a card recognition processor may be configured to perform an image processing analysis that automatically identifies a location and/or measurements for the rank and suit of at least one card. As an example, the card recognition processor may perform a blob analysis on one or more of the raw images stored in the memory. As discussed above, the blob analysis may be employed to locate rank and suit symbols, and distinguish between ranks, suits, and other markings on the card. Once the blobs are identified for the rank and suit of the card in the raw images, the measurements may be determined to define an area around each of the rank and the suit. In some embodiments, the 10 rank may be used as the particular rank to first identify the location and measurements of the rank area for the reasons discussed above. In some embodiments, the suit may be the large blob located below the rank, which may make identifying the location and measurements of the suit area relatively easy after locating the 10 rank.

In some embodiments, the location and measurements of the suit may be identified prior to the rank. For example, the suit may be identified by comparing portions of the raw image against a generic xml file describing suit curvatures, being immune to scale or rotation, for portions of the raw image that are closest to the corner of the card. In some embodiments, the rank may be the large blob located above the suit, which may make identifying the location and measurements of the rank area relatively easy after locating the appropriate suit.

Each of the raw images may be analyzed and the maximum and minimum measurements for the ranks and suits across the entire deck may be determined. The final measurements for the rank area and the suit area that are stored in the calibration file may be determined by taking the maximum measurements and then expanding values slightly to allow for some white space around the ranks and suits. Expanding the maximum value of the ranks and suits in this manner may allow for slight variations in print size, as well as for rotation of cards that may exist when reading in the cards.

At operation 1330, a calibration file may be generated and the parameters may be stored therein. The parameters may include the rank height, rank width, suit height, suit width, a location of an area of interest, as well as other desired parameters, such as those discussed above with respect to FIG. 5. The calibration file may be stored in memory within a card recognition processor, the control logic that performs the comparison of the unknown images and the master images, or both. Storing the calibration file in memory of the card recognition processor may include storing the calibration file in a subdirectory associated with the particular deck or deck type that is being tuned. The calibration file may further include other parameters that may be used by the control logic in generating master images, cropping unknown images, or for other reasons as discussed above.

FIG. 14 is a flowchart 1400 illustrating a method for generating master images according to an embodiment of the present disclosure. For the flow chart 1400, it is presumed that a calibration file has already been created, such as by the method of FIG. 13, or other methods described herein. For example, the calibration file may be automatically created using image processing methods to locate rank and suit symbols in the raw images and determine parameters regarding measurements of the rank and suit symbols. These parameters, along with other parameters discussed above, may be included with the calibration file that may be stored in a sub-directory of a file system. In addition, it may also be presumed that the raw images for the deck may have been stored in the memory device 418 (FIG. 4), which raw images may have been used in the analysis for automatically generating the calibration file.

At operation 1410, each raw image stored in the memory device 418 may be transmitted to the control logic 414 (FIG. 4). The raw images may be of the complete field of view of the imaging device 416 (FIG. 4) when a card was in a position to be read.

At operation 1420, the control logic 414 may generate the master images. In particular, the control logic 414 may crop the raw images according to the parameters stored in the calibration file. For example, the control logic 414 may crop the raw images according to stored rank area and suit area measurements to generate separate master images for the rank and the suit of the card. In some embodiments, a single master image may be generated for each card that includes both the rank and the suit (essentially the region of interest). Doing so, however, may require 52 master images (one for each card) rather than having as few as 17 master images (one for each rank and one for each suit), which may change the processing time during the card recognition mode.

At operation 1430, the master images may be associated with the appropriate rank and suit. In some embodiments, the order of each card in the deck may be known when master images are generated because deck may be pre-sorted when raw images are captured. As a result, each master image may be assigned a rank or suit based on the expected order of the pre-sorted deck. In other embodiments, the deck may not be required to be in any particular order. The card recognition processor 412 may perform analysis as described above, such as comparing master images against each other to determine secondary relationships between master images. In some embodiments, where the raw images may be stored in memory device 418 in a pre-determined order according to a sorted deck, the rank and suits may simply be known as being assigned according to the expected order of the cards being read in. If, however, the cards were not actually in the expected order, errors may occur. As a result, additional verification of this association may be desired to reduce such errors.

At operation 1440, secondary verification may be performed to determine whether the tuning process was correct. One example may include comparing master images with each other to determine secondary relationships. This may be done regardless of whether the deck should have been pre-sorted or not. For example, such secondary relationships may identify associations that may be incorrect because of a card that was out of order. Another secondary verification may be to check to see if the 10 ranks are in the correct location if a pre-sorted deck is being used. Additional levels of relationships (e.g., tertiary) between master images may also be analyzed for verification that the tuning process was accurate. Another secondary verification may be to display the master image and what the card recognition system determined the association to be. The operator may be allowed to select whether the association is correct and to make any changes if incorrect.

FIG. 15 is a flowchart 1500 illustrating a method for identifying a card rank and suit according to an embodiment of the present disclosure. At operation 1505, a calibration file may be generated by one or more of the following. At operation 1510, raw images may be captured from a deck of cards that is inserted into a card handling device. In some embodiments, the deck of cards may be sorted according to a predetermined order, while in other embodiments, the deck of cards may be in an order that is not predetermined. At operation 1515, the raw images may be stored in memory. At operation 1520, the size and the rank and suit symbols may be identified in the raw images. For example, a card recognition processor may perform a blob analysis to identify the location of the rank and suit symbols from among a plurality of blobs detected by the blob analysis. The blob analysis may ignore other blobs based on size, shape, or location in order to arrive at the rank and suit symbols. The blob analysis may also measure the size (e.g., height and width) of each of the rank and suit symbols. At operation 1525, a region of interest may be identified. The region of interest may be identified based on a maximum height and width for all of the rank and suit symbols as well as their locations to arrive at an area that may fully encompass each of the ranks and suits symbols of each card, which themselves may vary from card to card. At operation 1530, the parameters may be stored in the automatically generated calibration file. Parameters may include measurements for the rank box and the suit box and the measurements and coordinates for the region of interest, as well as additional parameters previously discussed.

At operation 1535, master rank images and master suit images may be generated by one or more of the following. At operation 1540, the raw images may be converted into master rank files and master suit files. For example, the calibration file may be used to crop the raw file around the rank symbol and the suit symbol in the raw images. In some embodiments, the master images and the calibration file may be created during operations that may overlap in time. At operation 1545, the master rank files and the master suit files may be associated with the appropriate rank and suit. For a deck that is arranged in a known order, these associations may be based on the expected order of the deck. For a deck of an unknown order, these associations may be based on indirect association that may be inferred by secondary analysis between master images, such as checking scores of next best matches and other similar relationships. At operation 1550, the master rank files and master suit files may be stored in a file system of the card recognition processor, in control logic, or both.

At operation 1555, cards may be identified during run mode by one or more of the following. At operation 1560, unknown images may be captured. For example, unknown images may be captured during game play to verify hands, at the beginning of game play to verify a deck, etc. At operation 1565, the unknown images may be compared to the master images. The comparison may be based on comparing pixel to pixel of each file to generate a score. The score may be represented as a number of pixels, a percentage of pixels, or other suitable form. In another embodiment, each master image may be scanned across a larger unknown image to determine a plurality of scores that may be used to determine if a match exists. At operation 1570, a match may be determined based on the score. The match and score may be determined based on meeting a threshold for either an appropriate measure of similarities or dissimilarities.

CONCLUSION

In an embodiment, a card recognition system comprises an imaging device configured to capture a raw image of at least a portion of a card, and a processor operably coupled with the imaging device. The processor is configured to perform an image processing analysis of the raw image identifying measurements of at least one of a rank area around a rank of the card, and a suit area around a suit of the card, and automatically generate a calibration file based, at least in part, on the image processing analysis.

In another embodiment, a card handling device comprises a card infeed, a card output, and a card recognition system. The card recognition system includes an image sensor configured to capture an image of a card passing from the card infeed to the card output, and a card recognition processor. The card recognition processor is configured to automatically generate a calibration file using an image analysis process of the image. The calibration file includes measurements for at least one of a size of a rank and a suit of the card within the image.

In another embodiment a method for tuning a card handling device is disclosed. The method comprises capturing a plurality of images from a deck of cards, storing the images in memory, analyzing the plurality of images for card identification information, and generating a calibration file including parameters associated with the card identification information based on the analyzing.

In another embodiment, a method of automatically generating a calibration file for identifying a specific card type is disclosed. The method comprises capturing a plurality of raw images from a deck of cards, storing the plurality of raw images in memory, identifying a size of each rank and suit symbol of each stored raw image of the plurality, storing a region of interest and symbol size information in a calibration file for the plurality of raw images, converting a plurality of raw images into a plurality of master rank files and a plurality of master suit files, and storing the plurality of master rank files and the plurality of master suit files corresponding to a specific card type.

In another embodiment, a method of identifying a card rank and suit is disclosed. The method comprises automatically creating a calibration file by capturing a plurality of raw images from a deck of cards, storing the plurality of raw images in memory, identifying a size of each rank and suit symbol of each stored raw image of the plurality, and storing a region of interest and rank and suit symbol size information in the calibration file for the plurality of raw images. The method further comprises generating a plurality of master rank files and a plurality of master suit files by converting a plurality of raw images into a plurality of master rank files and a plurality of master suit files, and storing the plurality of master rank files and the plurality of master suit files corresponding to a specific card type.

While certain illustrative embodiments have been described in connection with the figures, those of ordinary skill in the art will recognize and appreciate that embodiments of the disclosure are not limited to those embodiments explicitly shown and described herein. Rather, many additions, deletions, and modifications to the embodiments described herein may be made without departing from the scope of embodiments of the invention as hereinafter claimed, including legal equivalents. In addition, features from one embodiment may be combined with features of another embodiment while still being encompassed within the scope of the invention as contemplated by the inventor.

Claims

1. A card recognition system, comprising: an imaging device configured to capture a raw image of at least a portion of a card; anda processor operably coupled with the imaging device, the processor configured to: perform an image processing analysis of the raw image to identify measurements related to at least one of a rank area around a rank of the card, and a suit area around a suit of the card; andautomatically generate a calibration file during a calibration mode based, at least in part, on the image processing analysis, the calibration file including the measurements from the image processing analysis for processing cards during a subsequent card recognition mode.
2. The card recognition system of claim 1, further comprising a memory operably coupled with the imaging device, the memory configured to store a plurality of raw images received from the imaging device.
3. The card recognition system of claim 2, further configured to organize the plurality of raw images within the memory in the order received by the imaging device.
4. The card recognition system of claim 2, further comprising control logic operably coupled with the imaging device and the processor, the control logic configured to process the plurality of raw images according to one or more parameters stored in the calibration file to generate a plurality of rank images and a plurality of suit images used as master images during the calibration mode.
5. The card recognition system of claim 2, wherein the memory is further configured to: provide the raw images to the processor during the calibration mode to generate the calibration file; andprovide the raw images to the control logic during the calibration mode to generate a plurality of master images.
6. The card recognition system of claim 4, wherein the control logic is further configured to generate unknown images during a card recognition mode and compare the unknown images with the master images to determine a rank and a suit for the unknown images.
7. The card recognition system of claim 6, wherein the processor is configured to run an operating system having a file system, and wherein the control logic includes a Field-Programmable Gate Array.
8. The card recognition system of claim 5, wherein the plurality of raw images are captured from a sub-set of all cards in a deck of cards corresponding to the respective calibration file and the plurality of master images generated using the plurality of raw images.
9. The card recognition system of claim 1, wherein the processor is further configured to store the calibration file in a subdirectory of a file system, the subdirectory corresponding to a particular deck type.
10. The card recognition system of claim 9, wherein the processor is further configured to store a deck name file and a plurality of master images in the subdirectory corresponding to the particular deck type during the calibration mode.
11. The card recognition system of claim 1, wherein the image processing analysis includes a blob analysis of the raw image to obtain the measurements to include with the calibration file during the calibration mode.
12. The card recognition system of claim 11, wherein the blob analysis first identifies a rank to obtain the measurements of the rank area and then identifies a suit to obtain the measurements of the suit area to include with the calibration file during the calibration mode.
13. The card recognition system of claim 11, wherein the measurements of the rank area and the measurements of the suit area stored in the calibration file include additional padding added to the measurements obtained from the blob analysis.
14. The card recognition system of claim 12, wherein the blob analysis specifically searches for a ten rank to obtain the measurements of the rank area to include with the calibration file during the calibration mode.
15. The card recognition system of claim 14, wherein the blob analysis specifically searches for a relatively large blob in proximity of the ten rank to obtain the measurements of the suit area.
16. The card recognition system of claim 1, wherein the processor is further configured to automatically generate master images for each rank and suit of a deck of cards read by the imaging device during the calibration mode.
17. The card recognition system of claim 16, wherein the processor is further configured to automatically associate the master images with their corresponding rank and suit during the calibration mode.
18. The card recognition system of claim 17, wherein the processor is further configured to automatically associate the master images with their corresponding rank and suit according to an order in which the cards from the deck are read in by the imaging device during the calibration mode.
19. The card recognition system of claim 17, wherein the processor is further configured to automatically associate the master images with their corresponding rank and suit for the deck of cards without requiring a predetermined order for the deck of cards during the calibration mode.
20. The card recognition system of claim 19, wherein the processor is further configured to automatically associate the master images with their corresponding rank and suit for the deck of cards during the calibration mode by comparing the master images with each other to obtain scores that are compared with scores for known secondary relationships between different master images.
21. A card handling device, comprising: a card infeed;a card output; anda card recognition system, including: an image sensor configured to capture an image of a card passing from the card infeed to the card output; anda card recognition processor configured to automatically generate a calibration file using an image analysis process of the image during a calibration mode prior to card recognition mode, the calibration file including measurements from the image analysis process of the image for at least one of a size of a rank and a suit symbol of the card within the image.
22. The card handling device of claim 21, wherein the card recognition system further includes control logic operably coupled with the image sensor and configured to receive the image from the image sensor.
23. The card handling device of claim 22, wherein the card recognition system further includes a memory operably coupled with the control logic and the card recognition processor, the memory configured to receive the image from the control logic.
24. The card handling device of claim 22, wherein the control logic is configured to automatically generate a master image for at least one of the rank and the suit of the card within the image during the calibration mode.
25. The card handling device of claim 22, wherein the control logic is configured to convert the image from a grayscale image to a black and white image.
26. The card handling device of claim 22, wherein the imaging device includes a fish-eye lens.
27. The card handling device of claim 24, wherein the card recognition processor is configured to store the master image and the calibration file in a file system during the calibration mode.
28. The card recognition system of claim 27, wherein the master image and the calibration file are separate files stored in a same subdirectory of the file system during the calibration mode.
29. The card handling device of claim 25, wherein conversion from the grayscale image to the black and white image is based on a threshold level that dynamically changes over time.
30. The card handling device of claim 29, wherein the threshold level dynamically changes over time based on a change in lighting conditions.
31. The card handling device of claim 29, wherein the threshold level dynamically changes over time based on a count of a number of card cycles that the card handling device has handled.
32. The card handling device of claim 25, wherein the threshold level is set at a first level during the calibration mode and set at a second level during a card recognition mode.
33. The card handling device of claim 26, wherein the control logic is configured to compensate for the fish-eye distortion by translating pixels in the image using a look-up table.
34. The card handling device of claim 26, wherein the control logic is configured to compensate for the fish-eye distortion by mathematically translating pixels in the image.
35. The card handling device of claim 21, wherein the calibration file includes parameters including one or more of a rank height, a rank width, a suit height, a suit width, and a location of an area of interest.
36. The card handling device of claim 21, wherein the image process analysis during the calibration mode is configured to: capture raw images for cards in a deck;analyze the raw images to determine the measurements for at least one of the size of the rank and the suit symbol of the card within the image; andstore the measurements in the calibration file.
37. The card handling device of claim 36, wherein the control logic is configured to automatically generate master images during the calibration mode by: receiving the raw images; andcropping the raw images according to the measurements stored in the calibration file.

US Referenced Citations (888)

Number	Name	Date	Kind
130281	Coughlik	Aug 1872	A
205030	Ash	Jun 1878	A
609730	Booth	Aug 1898	A
673154	Bellows	Apr 1901	A
793489	Williams	Jun 1905	A
892389	Bellows	Jul 1908	A
1014219	Hall	Jan 1912	A
1043109	Hurm	Nov 1912	A
1157898	Perret	Oct 1915	A
1556856	Lipps	Oct 1925	A
1850114	McCaddin	Mar 1932	A
1885276	McKay	Nov 1932	A
1955926	Matthaey	Apr 1934	A
1992085	McKay	Feb 1935	A
1998690	Shepherd et al.	Apr 1935	A
2001220	Smith	May 1935	A
2001918	Nevius	May 1935	A
2016030	Rose	Oct 1935	A
2043343	Warner	Jun 1936	A
2060096	McCoy	Nov 1936	A
2065824	Plass	Dec 1936	A
2159958	Sachs	May 1939	A
2185474	Nott	Jan 1940	A
2254484	Hutchins	Sep 1941	A
D132360	Gardner	May 1942	S
2328153	Laing	Aug 1943	A
2328879	Isaacson	Sep 1943	A
2364413	Wittel	Dec 1944	A
2525305	Lombard	Oct 1950	A
2543522	Cohen	Feb 1951	A
2588582	Sivertson	Mar 1952	A
2661215	Stevens	Dec 1953	A
2676020	Ogden	Apr 1954	A
2692777	Miller	Oct 1954	A
2701720	Ogden	Feb 1955	A
2705638	Newcomb	Apr 1955	A
2711319	Morgan et al.	Jun 1955	A
2714510	Oppenlander et al.	Aug 1955	A
2717782	Droll	Sep 1955	A
2727747	Charles, Jr.	Dec 1955	A
2731271	Brown	Jan 1956	A
2747877	Howard	May 1956	A
2755090	Aldrich	Jul 1956	A
2757005	Nothaft	Jul 1956	A
2760779	Ogden et al.	Aug 1956	A
2770459	Wilson et al.	Nov 1956	A
2778643	Williams	Jan 1957	A
2778644	Stephenson	Jan 1957	A
2782040	Matter	Feb 1957	A
2790641	Adams	Apr 1957	A
2793863	Liebelt	May 1957	A
2815214	Hall	Dec 1957	A
2821399	Heinoo	Jan 1958	A
2914215	Neidig	Nov 1959	A
2937739	Levy	May 1960	A
2950005	MacDonald	Aug 1960	A
RE24986	Stephenson	May 1961	E
3067885	Kohler	Dec 1962	A
3107096	Osborn	Oct 1963	A
3124674	Edwards et al.	Mar 1964	A
3131935	Gronneberg	May 1964	A
3147978	Sjostrand	Sep 1964	A
3222071	Lang	Dec 1965	A
3235741	Plaisance	Feb 1966	A
3288308	Gingher	Nov 1966	A
3305237	Granius	Feb 1967	A
3312473	Friedman et al.	Apr 1967	A
3452509	Hauer	Jul 1969	A
3530968	Palmer	Sep 1970	A
3588116	Miura	Jun 1971	A
3589730	Slay	Jun 1971	A
3595388	Castaldi	Jul 1971	A
3597076	Hubbard	Aug 1971	A
3618933	Roggenstein	Nov 1971	A
3627331	Erickson	Dec 1971	A
3666270	Mazur	May 1972	A
3680853	Houghton	Aug 1972	A
3690670	Cassady et al.	Sep 1972	A
3704938	Fanselow	Dec 1972	A
3716238	Porter	Feb 1973	A
3751041	Seifert	Aug 1973	A
3761079	Azure	Sep 1973	A
3810627	Levy	May 1974	A
3861261	Maxey	Jan 1975	A
3897954	Erickson et al.	Aug 1975	A
3909002	Levy	Sep 1975	A
3929339	Mattioli et al.	Dec 1975	A
3944077	Green	Mar 1976	A
3944230	Fineman	Mar 1976	A
3949219	Crouse	Apr 1976	A
3968364	Miller	Jul 1976	A
4023705	Reiner et al.	May 1977	A
4033590	Pic	Jul 1977	A
4072930	Lucero et al.	Feb 1978	A
4088265	Garczynski et al.	May 1978	A
4151410	McMillan et al.	Apr 1979	A
4159581	Lichtenberg	Jul 1979	A
4162649	Thornton	Jul 1979	A
4166615	Noguchi et al.	Sep 1979	A
4232861	Maul	Nov 1980	A
4280690	Hill	Jul 1981	A
4283709	Lucero et al.	Aug 1981	A
4310160	Willette	Jan 1982	A
4339134	Macheel	Jul 1982	A
4339798	Hedges et al.	Jul 1982	A
4361393	Noto	Nov 1982	A
4368972	Naramore	Jan 1983	A
4369972	Parker	Jan 1983	A
4374309	Walton	Feb 1983	A
4377285	Kadlic	Mar 1983	A
4385827	Naramore	May 1983	A
4388994	Suda et al.	Jun 1983	A
4397469	Carter	Aug 1983	A
4421312	Delgado et al.	Dec 1983	A
4421501	Scheffer	Dec 1983	A
D274069	Fromm	May 1984	S
4467424	Hedges et al.	Aug 1984	A
4494197	Troy et al.	Jan 1985	A
4497488	Plevyak et al.	Feb 1985	A
4512580	Matviak	Apr 1985	A
4513969	Samsel	Apr 1985	A
4515367	Howard	May 1985	A
4531187	Uhland et al.	Jul 1985	A
4534562	Cuff et al.	Aug 1985	A
4549738	Greitzer	Oct 1985	A
4566782	Britt et al.	Jan 1986	A
4575367	Karmel	Mar 1986	A
4586712	Lorber et al.	May 1986	A
4659082	Greenberg	Apr 1987	A
4662637	Pfeiffer	May 1987	A
4662816	Fabrig	May 1987	A
4667959	Pfeiffer et al.	May 1987	A
4741524	Bromage	May 1988	A
4750743	Nicoletti	Jun 1988	A
4755941	Bacchi	Jul 1988	A
4759448	Kawabata	Jul 1988	A
4770412	Wolfe	Sep 1988	A
4770421	Hoffman	Sep 1988	A
4807884	Breeding	Feb 1989	A
4822050	Normand et al.	Apr 1989	A
4832342	Plevyak	May 1989	A
4858000	Lu	Aug 1989	A
4861041	Jones et al.	Aug 1989	A
4876000	Mikhail	Oct 1989	A
4900009	Kitahara et al.	Feb 1990	A
4904830	Rizzuto	Feb 1990	A
4921109	Hasuo et al.	May 1990	A
4926327	Sidley	May 1990	A
4948134	Suttle et al.	Aug 1990	A
4951950	Normand et al.	Aug 1990	A
4969648	Hollinger et al.	Nov 1990	A
4993587	Abe	Feb 1991	A
4995615	Cheng	Feb 1991	A
5000453	Stevens et al.	Mar 1991	A
5039102	Miller et al.	Aug 1991	A
5067713	Soules et al.	Nov 1991	A
5078405	Jones et al.	Jan 1992	A
5081487	Hoyer et al.	Jan 1992	A
5096197	Embury	Mar 1992	A
5102293	Schneider	Apr 1992	A
5118114	Tucci et al.	Jun 1992	A
5121192	Kazui	Jun 1992	A
5121921	Friedman	Jun 1992	A
5146346	Knoll	Sep 1992	A
5154429	LeVasseur et al.	Oct 1992	A
5179517	Sarbin et al.	Jan 1993	A
5197094	Tillery et al.	Mar 1993	A
5199710	Lamle	Apr 1993	A
5209476	Eiba	May 1993	A
5224712	Laughlin et al.	Jul 1993	A
5240140	Huen	Aug 1993	A
5248142	Breeding et al.	Sep 1993	A
5257179	DeMar et al.	Oct 1993	A
5259907	Soules et al.	Nov 1993	A
5261667	Breeding	Nov 1993	A
5267248	Reyner	Nov 1993	A
5275411	Breeding	Jan 1994	A
5276312	McCarthy	Jan 1994	A
5283422	Storch et al.	Feb 1994	A
5288081	Breeding et al.	Feb 1994	A
5299089	Lwee et al.	Mar 1994	A
5303921	Breeding	Apr 1994	A
5344146	Lee	Sep 1994	A
5356145	Verschoor	Oct 1994	A
5362053	Miller et al.	Nov 1994	A
5374061	Albrecht et al.	Dec 1994	A
5377973	Jones et al.	Jan 1995	A
5382024	Blaha	Jan 1995	A
5382025	Sklansky et al.	Jan 1995	A
5390910	Mandel et al.	Feb 1995	A
5397128	Hesse et al.	Mar 1995	A
5397133	Penzias et al.	Mar 1995	A
5416308	Hood et al.	May 1995	A
5431399	Kelley et al.	Jul 1995	A
5431407	Hofberg et al.	Jul 1995	A
5437462	Breeding et al.	Aug 1995	A
5445377	Steinbach	Aug 1995	A
5470079	LeStrange et al.	Nov 1995	A
D365853	Zadro	Jan 1996	S
5489101	Moody et al.	Feb 1996	A
5515477	Sutherland	May 1996	A
5524888	Heidel	Jun 1996	A
5531448	Moody et al.	Jul 1996	A
5544892	Breeding et al.	Aug 1996	A
5575475	Steinbach	Nov 1996	A
5584483	Sines et al.	Dec 1996	A
5586766	Forte et al.	Dec 1996	A
5586936	Bennett et al.	Dec 1996	A
5605334	McCrea et al.	Feb 1997	A
5613912	Slater et al.	Mar 1997	A
5632483	Garczynski et al.	May 1997	A
5636843	Roberts et al.	Jun 1997	A
5651548	French et al.	Jul 1997	A
5655961	Acres et al.	Aug 1997	A
5669816	Garczynski et al.	Sep 1997	A
5676231	Legras et al.	Oct 1997	A
5676372	Sines et al.	Oct 1997	A
5681039	Miller et al.	Oct 1997	A
5683085	Johnson et al.	Nov 1997	A
5685543	Garner et al.	Nov 1997	A
5690324	Otomo et al.	Nov 1997	A
5692748	Frisco et al.	Dec 1997	A
5695189	Breeding et al.	Dec 1997	A
5701565	Morgan	Dec 1997	A
5707286	Carlson	Jan 1998	A
5707287	McCrea et al.	Jan 1998	A
5711525	Breeding et al.	Jan 1998	A
5718427	Cranford et al.	Feb 1998	A
5719288	Sens et al.	Feb 1998	A
5720484	Hsu et al.	Feb 1998	A
5722893	Hill et al.	Mar 1998	A
5735525	McCrea et al.	Apr 1998	A
5735724	Udagawa	Apr 1998	A
5735742	French et al.	Apr 1998	A
5743798	Adams et al.	Apr 1998	A
5768382	Schneier et al.	Jun 1998	A
5770533	Franchi et al.	Jun 1998	A
5770553	Kroner et al.	Jun 1998	A
5772505	Garczynski et al.	Jun 1998	A
5779546	Meissner et al.	Jul 1998	A
5781647	Fishbine et al.	Jul 1998	A
5785321	Van Putten et al.	Jul 1998	A
5788574	Ornstein et al.	Aug 1998	A
5791988	Nomi et al.	Aug 1998	A
5802560	Joseph et al.	Sep 1998	A
5803808	Strisower	Sep 1998	A
5810355	Trilli	Sep 1998	A
5813326	Salomon et al.	Sep 1998	A
5813912	Shultz et al.	Sep 1998	A
5814796	Benson et al.	Sep 1998	A
5836775	Hiyama et al.	Nov 1998	A
5839730	Pike	Nov 1998	A
5845906	Wirth et al.	Dec 1998	A
5851011	Lott et al.	Dec 1998	A
5867586	Liang	Feb 1999	A
5879233	Stupero	Mar 1999	A
5883804	Christensen	Mar 1999	A
5890717	Rosewarne et al.	Apr 1999	A
5892210	Levasseur	Apr 1999	A
5911626	McCrea et al.	Jun 1999	A
5919090	Mothwurf	Jul 1999	A
5936222	Korsunsky et al.	Aug 1999	A
5941769	Order	Aug 1999	A
5944310	Johnson et al.	Aug 1999	A
D414527	Tedham	Sep 1999	S
5957776	Hoehne et al.	Sep 1999	A
5974150	Kaish et al.	Oct 1999	A
5985305	Peery et al.	Nov 1999	A
5989122	Roblejo et al.	Nov 1999	A
5991308	Fuhrmann et al.	Nov 1999	A
6015311	Benjamin et al.	Jan 2000	A
6019368	Sines et al.	Feb 2000	A
6019374	Breeding et al.	Feb 2000	A
6039650	Hill et al.	Mar 2000	A
6050569	Taylor	Apr 2000	A
6053695	Longoria et al.	Apr 2000	A
6061449	Candelore et al.	May 2000	A
6068258	Breeding et al.	May 2000	A
6069564	Hatano et al.	May 2000	A
6071190	Weiss et al.	Jun 2000	A
6093103	McCrea et al.	Jul 2000	A
6113101	Wirth et al.	Sep 2000	A
6117012	McCrea et al.	Sep 2000	A
D432588	Tedham	Oct 2000	S
6126166	Lorson et al.	Oct 2000	A
6127447	Mitry et al.	Oct 2000	A
6131817	Miller	Oct 2000	A
6139014	Breeding et al.	Oct 2000	A
6149154	Grauzer et al.	Nov 2000	A
6154131	Jones et al.	Nov 2000	A
6165069	Sines et al.	Dec 2000	A
6165072	Davis et al.	Dec 2000	A
6183362	Boushy	Feb 2001	B1
6186895	Oliver	Feb 2001	B1
6200218	Lindsay	Mar 2001	B1
6210274	Carlson	Apr 2001	B1
6213310	Wennersten et al.	Apr 2001	B1
6217447	Lofink et al.	Apr 2001	B1
6234900	Cumbers	May 2001	B1
6236223	Brady et al.	May 2001	B1
6250632	Albrecht	Jun 2001	B1
6254002	Litman	Jul 2001	B1
6254096	Grauzer et al.	Jul 2001	B1
6254484	McCrea, Jr.	Jul 2001	B1
6257981	Acres et al.	Jul 2001	B1
6267248	Johnson et al.	Jul 2001	B1
6267648	Katayama et al.	Jul 2001	B1
6267671	Hogan	Jul 2001	B1
6270404	Sines et al.	Aug 2001	B2
6272223	Carlson	Aug 2001	B1
6293546	Hessing et al.	Sep 2001	B1
6293864	Romero	Sep 2001	B1
6299167	Sines et al.	Oct 2001	B1
6299534	Breeding et al.	Oct 2001	B1
6299536	Hill	Oct 2001	B1
6308886	Benson et al.	Oct 2001	B1
6313871	Schubert	Nov 2001	B1
6325373	Breeding et al.	Dec 2001	B1
6334614	Breeding	Jan 2002	B1
6341778	Lee	Jan 2002	B1
6342830	Want et al.	Jan 2002	B1
6346044	McCrea, Jr.	Feb 2002	B1
6361044	Block et al.	Mar 2002	B1
6386973	Yoseloff	May 2002	B1
6402142	Warren et al.	Jun 2002	B1
6403908	Stardust	Jun 2002	B2
6443839	Stockdale	Sep 2002	B2
6446864	Kim et al.	Sep 2002	B1
6454266	Breeding et al.	Sep 2002	B1
6460848	Soltys et al.	Oct 2002	B1
6464584	Oliver	Oct 2002	B2
6490277	Tzotzkov	Dec 2002	B1
6508709	Karmarkar	Jan 2003	B1
6514140	Storch	Feb 2003	B1
6517435	Soltys et al.	Feb 2003	B2
6517436	Soltys et al.	Feb 2003	B2
6520857	Soltys et al.	Feb 2003	B2
6527271	Soltys et al.	Mar 2003	B2
6530836	Soltys et al.	Mar 2003	B2
6530837	Soltys et al.	Mar 2003	B2
6532297	Lindquist	Mar 2003	B1
6533276	Soltys et al.	Mar 2003	B2
6533662	Soltys et al.	Mar 2003	B2
6561897	Bourbour et al.	May 2003	B1
6568678	Breeding et al.	May 2003	B2
6579180	Soltys et al.	Jun 2003	B2
6579181	Soltys et al.	Jun 2003	B2
6581747	Charlier et al.	Jun 2003	B1
6582301	Hill	Jun 2003	B2
6582302	Romero	Jun 2003	B2
6585586	Romero	Jul 2003	B1
6585588	Hartl	Jul 2003	B2
6585856	Zwick et al.	Jul 2003	B2
6588750	Grauzer et al.	Jul 2003	B1
6588751	Grauzer et al.	Jul 2003	B1
6595857	Soltys et al.	Jul 2003	B2
6609710	Order	Aug 2003	B1
6612928	Bradford et al.	Sep 2003	B1
6616535	Nishizaki et al.	Sep 2003	B1
6619662	Miller	Sep 2003	B2
6622185	Johnson	Sep 2003	B1
6626757	Oliveras	Sep 2003	B2
6629019	Legge et al.	Sep 2003	B2
6629591	Griswold et al.	Oct 2003	B1
6629889	Mothwurf	Oct 2003	B2
6629894	Purton	Oct 2003	B1
6637622	Robinson	Oct 2003	B1
6638161	Soltys et al.	Oct 2003	B2
6645068	Kelly et al.	Nov 2003	B1
6645077	Rowe	Nov 2003	B2
6651981	Grauzer et al.	Nov 2003	B2
6651982	Grauzer et al.	Nov 2003	B2
6651985	Sines et al.	Nov 2003	B2
6652379	Soltys et al.	Nov 2003	B2
6655684	Grauzer et al.	Dec 2003	B2
6655690	Oskwarek	Dec 2003	B1
6658135	Morito et al.	Dec 2003	B1
6659460	Blaha et al.	Dec 2003	B2
6659461	Yoseloff et al.	Dec 2003	B2
6659875	Purton	Dec 2003	B2
6663490	Soltys et al.	Dec 2003	B2
6666768	Akers	Dec 2003	B1
6671358	Sossaman et al.	Dec 2003	B1
6676127	Johnson et al.	Jan 2004	B2
6676517	Beavers	Jan 2004	B2
6680843	Farrow et al.	Jan 2004	B2
6685564	Oliver	Feb 2004	B2
6685567	Cockerille et al.	Feb 2004	B2
6685568	Soltys et al.	Feb 2004	B2
6688597	Jones	Feb 2004	B2
6688979	Soltys et al.	Feb 2004	B2
6690673	Jarvis	Feb 2004	B1
6698756	Baker et al.	Mar 2004	B1
6698759	Webb et al.	Mar 2004	B2
6702289	Feola	Mar 2004	B1
6702290	Buono-Correa et al.	Mar 2004	B2
6709333	Bradford et al.	Mar 2004	B1
6712696	Soltys et al.	Mar 2004	B2
6719288	Hessing et al.	Apr 2004	B2
6719634	Mishina et al.	Apr 2004	B2
6722974	Sines et al.	Apr 2004	B2
6726205	Purton	Apr 2004	B1
6732067	Powderly	May 2004	B1
6733012	Bui et al.	May 2004	B2
6733388	Mothwurf	May 2004	B2
6746333	Onda et al.	Jun 2004	B1
6747560	Stevens, III	Jun 2004	B2
6749510	Giobbi	Jun 2004	B2
6758751	Soltys et al.	Jul 2004	B2
6758757	Luciano, Jr. et al.	Jul 2004	B2
6769693	Huard et al.	Aug 2004	B2
6774782	Runyon et al.	Aug 2004	B2
6789801	Snow	Sep 2004	B2
6802510	Haber	Oct 2004	B1
6804763	Stockdale et al.	Oct 2004	B1
6808173	Snow	Oct 2004	B2
6827282	Silverbrook	Dec 2004	B2
6834251	Fletcher	Dec 2004	B1
6840517	Snow	Jan 2005	B2
6842263	Saeki	Jan 2005	B1
6843725	Nelson	Jan 2005	B2
6848616	Tsirline et al.	Feb 2005	B2
6848844	McCue, Jr. et al.	Feb 2005	B2
6848994	Knust et al.	Feb 2005	B1
6857961	Soltys et al.	Feb 2005	B2
6874784	Promutico	Apr 2005	B1
6874786	Bruno	Apr 2005	B2
6877657	Ranard et al.	Apr 2005	B2
6877748	Patroni	Apr 2005	B1
6886829	Hessing et al.	May 2005	B2
6889979	Blaha et al.	May 2005	B2
6893347	Zilliacus et al.	May 2005	B1
6899628	Leen et al.	May 2005	B2
6902167	Webb	Jun 2005	B2
6905121	Timpano	Jun 2005	B1
6923446	Snow	Aug 2005	B2
6938900	Snow	Sep 2005	B2
6941180	Fischer et al.	Sep 2005	B1
6950948	Neff	Sep 2005	B2
6955599	Bourbour et al.	Oct 2005	B2
6957746	Martin et al.	Oct 2005	B2
6959925	Baker et al.	Nov 2005	B1
6959935	Buhl et al.	Nov 2005	B2
6960134	Hartl et al.	Nov 2005	B2
6964612	Soltys et al.	Nov 2005	B2
6986514	Snow	Jan 2006	B2
6988516	Debaes et al.	Jan 2006	B2
7011309	Soltys et al.	Mar 2006	B2
7020307	Hinton et al.	Mar 2006	B2
7028598	Teshima	Apr 2006	B2
7029009	Grauzer et al.	Apr 2006	B2
7036818	Grauzer et al.	May 2006	B2
7046458	Nakayama	May 2006	B2
7046764	Kump	May 2006	B1
7048629	Sines et al.	May 2006	B2
7059602	Grauzer et al.	Jun 2006	B2
7066464	Blad et al.	Jun 2006	B2
7068822	Scott	Jun 2006	B2
7073791	Grauzer et al.	Jul 2006	B2
7084769	Bauer et al.	Aug 2006	B2
7089420	Durst et al.	Aug 2006	B1
7106201	Tuttle	Sep 2006	B2
7113094	Garber et al.	Sep 2006	B2
7114718	Grauzer et al.	Oct 2006	B2
7124947	Storch	Oct 2006	B2
7128652	Lavoie et al.	Oct 2006	B1
7137627	Grauzer et al.	Nov 2006	B2
7139108	Andersen et al.	Nov 2006	B2
7140614	Snow	Nov 2006	B2
7162035	Durst et al.	Jan 2007	B1
7165769	Crenshaw et al.	Jan 2007	B2
7165770	Snow	Jan 2007	B2
7175522	Hartl	Feb 2007	B2
7186181	Rowe	Mar 2007	B2
7201656	Darder	Apr 2007	B2
7202888	Tecu et al.	Apr 2007	B2
7203841	Jackson et al.	Apr 2007	B2
7213812	Schubert et al.	May 2007	B2
7222852	Soltys et al.	May 2007	B2
7222855	Sorge	May 2007	B2
7231812	Lagare	Jun 2007	B1
7234698	Grauzer et al.	Jun 2007	B2
7237969	Bartman	Jul 2007	B2
7243148	Keir et al.	Jul 2007	B2
7243698	Siegel	Jul 2007	B2
7246799	Snow	Jul 2007	B2
7255344	Grauzer et al.	Aug 2007	B2
7255351	Yoseloff et al.	Aug 2007	B2
7255642	Sines et al.	Aug 2007	B2
7257630	Cole et al.	Aug 2007	B2
7261294	Grauzer et al.	Aug 2007	B2
7264241	Schubert et al.	Sep 2007	B2
7264243	Yoseloff et al.	Sep 2007	B2
7277570	Armstrong	Oct 2007	B2
7278923	Grauzer et al.	Oct 2007	B2
7294056	Lowell et al.	Nov 2007	B2
7297062	Gatto et al.	Nov 2007	B2
7300056	Gioia et al.	Nov 2007	B2
7303473	Rowe	Dec 2007	B2
7309065	Yoseloff et al.	Dec 2007	B2
7316609	Dunn et al.	Jan 2008	B2
7316615	Soltys et al.	Jan 2008	B2
7322576	Grauzer et al.	Jan 2008	B2
7331579	Snow	Feb 2008	B2
7334794	Snow	Feb 2008	B2
7338044	Grauzer et al.	Mar 2008	B2
7338362	Gallagher	Mar 2008	B1
7341510	Bourbour et al.	Mar 2008	B2
7357321	Yoshida et al.	Apr 2008	B2
7360094	Neff	Apr 2008	B2
7367561	Blaha et al.	May 2008	B2
7367563	Yoseloff et al.	May 2008	B2
7367884	Breeding et al.	May 2008	B2
7374170	Grauzer et al.	May 2008	B2
7384044	Grauzer et al.	Jun 2008	B2
7387300	Snow	Jun 2008	B2
7389990	Mourad	Jun 2008	B2
7390256	Soltys et al.	Jun 2008	B2
7399226	Mishra	Jul 2008	B2
7407438	Schubert et al.	Aug 2008	B2
7413191	Grauzer et al.	Aug 2008	B2
7434805	Grauzer et al.	Oct 2008	B2
7436957	Fischer et al.	Oct 2008	B1
7448626	Fleckenstein	Nov 2008	B2
7458582	Snow et al.	Dec 2008	B2
7461843	Baker et al.	Dec 2008	B1
7464932	Darling	Dec 2008	B2
7464934	Schwartz	Dec 2008	B2
7472906	Shai	Jan 2009	B2
7500672	Ho	Mar 2009	B2
7506874	Hall	Mar 2009	B2
7510186	Fleckenstein	Mar 2009	B2
7510190	Snow et al.	Mar 2009	B2
7510194	Soltys et al.	Mar 2009	B2
7510478	Benbrahim et al.	Mar 2009	B2
7513437	Douglas	Apr 2009	B2
7515718	Nguyen et al.	Apr 2009	B2
7523935	Grauzer et al.	Apr 2009	B2
7523936	Grauzer et al.	Apr 2009	B2
7523937	Fleckenstein	Apr 2009	B2
7525510	Beland et al.	Apr 2009	B2
7537216	Soltys et al.	May 2009	B2
7540497	Tseng	Jun 2009	B2
7540498	Crenshaw et al.	Jun 2009	B2
7549643	Quach	Jun 2009	B2
7554753	Wakamiya	Jun 2009	B2
7556197	Yoshida et al.	Jul 2009	B2
7556266	Blaha et al.	Jul 2009	B2
7575237	Snow	Aug 2009	B2
7578506	Lambert	Aug 2009	B2
7584962	Breeding et al.	Sep 2009	B2
7584963	Krenn et al.	Sep 2009	B2
7584966	Snow	Sep 2009	B2
7591728	Gioia et al.	Sep 2009	B2
7593544	Downs, III et al.	Sep 2009	B2
7594660	Baker et al.	Sep 2009	B2
7597623	Grauzer et al.	Oct 2009	B2
7644923	Dickinson et al.	Jan 2010	B1
7661676	Smith et al.	Feb 2010	B2
7666090	Hettinger	Feb 2010	B2
7669852	Baker et al.	Mar 2010	B2
7669853	Jones	Mar 2010	B2
7677565	Grauzer et al.	Mar 2010	B2
7677566	Krenn et al.	Mar 2010	B2
7686681	Soltys et al.	Mar 2010	B2
7699694	Hill	Apr 2010	B2
7735657	Johnson	Jun 2010	B2
7740244	Ho	Jun 2010	B2
7744452	Cimring et al.	Jun 2010	B2
7753373	Grauzer et al.	Jul 2010	B2
7753374	Ho	Jul 2010	B2
7753798	Soltys et al.	Jul 2010	B2
7762554	Ho	Jul 2010	B2
7764836	Downs, III et al.	Jul 2010	B2
7766332	Grauzer et al.	Aug 2010	B2
7766333	Stardust et al.	Aug 2010	B1
7769232	Downs, III	Aug 2010	B2
7769853	Nezamzadeh	Aug 2010	B2
7773749	Durst et al.	Aug 2010	B1
7780529	Rowe et al.	Aug 2010	B2
7784790	Grauzer et al.	Aug 2010	B2
7804982	Howard et al.	Sep 2010	B2
7846020	Walker et al.	Dec 2010	B2
7867080	Nicely et al.	Jan 2011	B2
7890365	Hettinger	Feb 2011	B2
7900923	Toyama et al.	Mar 2011	B2
7901285	Tran et al.	Mar 2011	B2
7908169	Hettinger	Mar 2011	B2
7909689	Lardie	Mar 2011	B2
7931533	LeMay et al.	Apr 2011	B2
7933448	Downs, III	Apr 2011	B2
7946586	Krenn et al.	May 2011	B2
7967294	Blaha et al.	Jun 2011	B2
7976023	Hessing et al.	Jul 2011	B1
7988152	Sines	Aug 2011	B2
7988554	LeMay et al.	Aug 2011	B2
7995196	Fraser	Aug 2011	B1
8002638	Grauzer et al.	Aug 2011	B2
8011661	Stasson	Sep 2011	B2
8016663	Soltys et al.	Sep 2011	B2
8021231	Walker et al.	Sep 2011	B2
8025294	Grauzer et al.	Sep 2011	B2
8038521	Grauzer et al.	Oct 2011	B2
RE42944	Blaha et al.	Nov 2011	E
8057302	Wells et al.	Nov 2011	B2
8062134	Kelly et al.	Nov 2011	B2
8070574	Grauzer et al.	Dec 2011	B2
8092307	Kelly	Jan 2012	B2
8092309	Bickley	Jan 2012	B2
8141875	Grauzer et al.	Mar 2012	B2
8150158	Downs, III	Apr 2012	B2
8171567	Fraser et al.	May 2012	B1
8210536	Blaha et al.	Jul 2012	B2
8221244	French	Jul 2012	B2
8251293	Nagata et al.	Aug 2012	B2
8267404	Grauzer et al.	Sep 2012	B2
8270603	Durst et al.	Sep 2012	B1
8287347	Snow et al.	Oct 2012	B2
8287386	Miller et al.	Oct 2012	B2
8319666	Weinmann et al.	Nov 2012	B2
8337296	Grauzer et al.	Dec 2012	B2
8342525	Scheper et al.	Jan 2013	B2
8342526	Sampson et al.	Jan 2013	B1
8342529	Snow	Jan 2013	B2
8353513	Swanson	Jan 2013	B2
8381918	Johnson	Feb 2013	B2
8419521	Grauzer et al.	Apr 2013	B2
8444147	Grauzer et al.	May 2013	B2
8469360	Sines	Jun 2013	B2
8480088	Toyama et al.	Jul 2013	B2
8485527	Sampson et al.	Jul 2013	B2
8490973	Yoseloff et al.	Jul 2013	B2
8498444	Sharma	Jul 2013	B2
8505916	Grauzer et al.	Aug 2013	B2
8511684	Grauzer et al.	Aug 2013	B2
8556263	Grauzer et al.	Oct 2013	B2
8579289	Rynda et al.	Nov 2013	B2
8616552	Czyzewski et al.	Dec 2013	B2
8628086	Krenn et al.	Jan 2014	B2
8662500	Swanson	Mar 2014	B2
8695978	Ho	Apr 2014	B1
8702100	Snow et al.	Apr 2014	B2
8702101	Scheper et al.	Apr 2014	B2
8720891	Hessing et al.	May 2014	B2
8758111	Lutnick	Jun 2014	B2
8777710	Grauzer et al.	Jul 2014	B2
8820745	Grauzer et al.	Sep 2014	B2
8899587	Grauzer et al.	Dec 2014	B2
8919775	Wadds et al.	Dec 2014	B2
20010036231	Easwar et al.	Nov 2001	A1
20010036866	Stockdale et al.	Nov 2001	A1
20020017481	Johnson et al.	Feb 2002	A1
20020030425	Tiramani et al.	Mar 2002	A1
20020045478	Soltys et al.	Apr 2002	A1
20020045481	Soltys et al.	Apr 2002	A1
20020063389	Breeding et al.	May 2002	A1
20020068635	Hill	Jun 2002	A1
20020070499	Breeding et al.	Jun 2002	A1
20020094869	Harkham	Jul 2002	A1
20020107067	McGlone et al.	Aug 2002	A1
20020107072	Giobbi	Aug 2002	A1
20020113368	Hessing et al.	Aug 2002	A1
20020135692	Fujinawa	Sep 2002	A1
20020142820	Bartlett	Oct 2002	A1
20020155869	Soltys et al.	Oct 2002	A1
20020163125	Grauzer et al.	Nov 2002	A1
20020187821	Soltys et al.	Dec 2002	A1
20020187830	Stockdale et al.	Dec 2002	A1
20030003997	Vuong et al.	Jan 2003	A1
20030007143	McArthur et al.	Jan 2003	A1
20030047870	Blaha et al.	Mar 2003	A1
20030048476	Yamakawa	Mar 2003	A1
20030052449	Grauzer et al.	Mar 2003	A1
20030052450	Grauzer et al.	Mar 2003	A1
20030064798	Grauzer et al.	Apr 2003	A1
20030067112	Grauzer et al.	Apr 2003	A1
20030071413	Blaha et al.	Apr 2003	A1
20030073498	Grauzer et al.	Apr 2003	A1
20030075865	Grauzer et al.	Apr 2003	A1
20030075866	Blaha et al.	Apr 2003	A1
20030087694	Storch	May 2003	A1
20030090059	Grauzer et al.	May 2003	A1
20030094756	Grauzer et al.	May 2003	A1
20030151194	Hessing et al.	Aug 2003	A1
20030195025	Hill	Oct 2003	A1
20040015423	Walker et al.	Jan 2004	A1
20040036214	Baker et al.	Feb 2004	A1
20040067789	Grauzer et al.	Apr 2004	A1
20040100026	Haggard	May 2004	A1
20040108654	Grauzer et al.	Jun 2004	A1
20040116179	Nicely et al.	Jun 2004	A1
20040169332	Grauzer et al.	Sep 2004	A1
20040180722	Giobbi	Sep 2004	A1
20040224777	Smith et al.	Nov 2004	A1
20040245720	Grauzer et al.	Dec 2004	A1
20040259618	Soltys et al.	Dec 2004	A1
20050012671	Bisig	Jan 2005	A1
20050023752	Grauzer et al.	Feb 2005	A1
20050026680	Gururajan	Feb 2005	A1
20050035548	Yoseloff et al.	Feb 2005	A1
20050037843	Wells et al.	Feb 2005	A1
20050040594	Krenn et al.	Feb 2005	A1
20050051955	Schubert et al.	Mar 2005	A1
20050051956	Grauzer et al.	Mar 2005	A1
20050062227	Grauzer et al.	Mar 2005	A1
20050062228	Grauzer et al.	Mar 2005	A1
20050062229	Grauzer et al.	Mar 2005	A1
20050082750	Grauzer et al.	Apr 2005	A1
20050093231	Grauzer et al.	May 2005	A1
20050104289	Grauzer et al.	May 2005	A1
20050104290	Grauzer et al.	May 2005	A1
20050110210	Soltys et al.	May 2005	A1
20050113166	Grauzer et al.	May 2005	A1
20050113171	Hodgson	May 2005	A1
20050119048	Soltys et al.	Jun 2005	A1
20050137005	Soltys et al.	Jun 2005	A1
20050140090	Breeding et al.	Jun 2005	A1
20050146093	Grauzer et al.	Jul 2005	A1
20050148391	Tain	Jul 2005	A1
20050192092	Breckner et al.	Sep 2005	A1
20050206077	Grauzer et al.	Sep 2005	A1
20050242500	Downs	Nov 2005	A1
20050272501	Tran et al.	Dec 2005	A1
20050288083	Downs	Dec 2005	A1
20050288086	Schubert et al.	Dec 2005	A1
20060027970	Kyrychenko	Feb 2006	A1
20060033269	Grauzer et al.	Feb 2006	A1
20060033270	Grauzer et al.	Feb 2006	A1
20060046853	Black	Mar 2006	A1
20060063577	Downs et al.	Mar 2006	A1
20060066048	Krenn et al.	Mar 2006	A1
20060181022	Grauzer et al.	Aug 2006	A1
20060183540	Grauzer et al.	Aug 2006	A1
20060189381	Daniel et al.	Aug 2006	A1
20060199649	Soltys et al.	Sep 2006	A1
20060205508	Green	Sep 2006	A1
20060220312	Baker et al.	Oct 2006	A1
20060220313	Baker et al.	Oct 2006	A1
20060252521	Gururajan et al.	Nov 2006	A1
20060252554	Gururajan et al.	Nov 2006	A1
20060279040	Downs et al.	Dec 2006	A1
20060281534	Grauzer et al.	Dec 2006	A1
20070001395	Gioia et al.	Jan 2007	A1
20070006708	Laakso	Jan 2007	A1
20070015583	Tran	Jan 2007	A1
20070018389	Downs	Jan 2007	A1
20070045959	Soltys	Mar 2007	A1
20070049368	Kuhn et al.	Mar 2007	A1
20070057469	Grauzer et al.	Mar 2007	A1
20070066387	Matsuno et al.	Mar 2007	A1
20070069462	Downs et al.	Mar 2007	A1
20070072677	Lavoie et al.	Mar 2007	A1
20070102879	Stasson	May 2007	A1
20070111773	Gururajan et al.	May 2007	A1
20070184905	Gatto et al.	Aug 2007	A1
20070197294	Gong	Aug 2007	A1
20070197298	Rowe	Aug 2007	A1
20070202941	Miltenberger et al.	Aug 2007	A1
20070222147	Blaha et al.	Sep 2007	A1
20070225055	Weisman	Sep 2007	A1
20070233567	Daly	Oct 2007	A1
20070238506	Ruckle	Oct 2007	A1
20070259709	Kelly et al.	Nov 2007	A1
20070267812	Grauzer et al.	Nov 2007	A1
20070272600	Johnson	Nov 2007	A1
20070278739	Swanson	Dec 2007	A1
20070290438	Grauzer et al.	Dec 2007	A1
20080006997	Scheper et al.	Jan 2008	A1
20080006998	Grauzer et al.	Jan 2008	A1
20080022415	Kuo et al.	Jan 2008	A1
20080032763	Giobbi	Feb 2008	A1
20080039192	Laut	Feb 2008	A1
20080039208	Abrink et al.	Feb 2008	A1
20080096656	LeMay et al.	Apr 2008	A1
20080111300	Czyzewski et al.	May 2008	A1
20080113700	Czyzewski et al.	May 2008	A1
20080113783	Czyzewski et al.	May 2008	A1
20080136108	Polay	Jun 2008	A1
20080143048	Shigeta	Jun 2008	A1
20080176627	Lardie	Jul 2008	A1
20080217218	Johnson	Sep 2008	A1
20080234046	Kinsley	Sep 2008	A1
20080234047	Nguyen	Sep 2008	A1
20080248875	Beatty	Oct 2008	A1
20080284096	Toyama et al.	Nov 2008	A1
20080303210	Grauzer et al.	Dec 2008	A1
20080315517	Toyama	Dec 2008	A1
20090026700	Shigeta	Jan 2009	A2
20090048026	French	Feb 2009	A1
20090054161	Schubert et al.	Feb 2009	A1
20090072477	Tseng	Mar 2009	A1
20090091078	Grauzer et al.	Apr 2009	A1
20090100409	Toneguzzo	Apr 2009	A1
20090104963	Burman et al.	Apr 2009	A1
20090121429	Walsh	May 2009	A1
20090140492	Yoseloff et al.	Jun 2009	A1
20090166970	Rosh	Jul 2009	A1
20090176547	Katz	Jul 2009	A1
20090179378	Amaitis et al.	Jul 2009	A1
20090186676	Amaitis et al.	Jul 2009	A1
20090189346	Krenn et al.	Jul 2009	A1
20090191933	French	Jul 2009	A1
20090194988	Wright et al.	Aug 2009	A1
20090197662	Wright et al.	Aug 2009	A1
20090224476	Grauzer et al.	Sep 2009	A1
20090227318	Wright et al.	Sep 2009	A1
20090227360	Gioia et al.	Sep 2009	A1
20090250873	Jones	Oct 2009	A1
20090253478	Walker et al.	Oct 2009	A1
20090253503	Krise et al.	Oct 2009	A1
20090267296	Ho	Oct 2009	A1
20090267297	Blaha et al.	Oct 2009	A1
20090283969	Tseng	Nov 2009	A1
20090298577	Gagner et al.	Dec 2009	A1
20090302535	Ho	Dec 2009	A1
20090302537	Ho	Dec 2009	A1
20090312093	Walker et al.	Dec 2009	A1
20090314188	Toyama et al.	Dec 2009	A1
20100013152	Grauzer et al.	Jan 2010	A1
20100038849	Scheper et al.	Feb 2010	A1
20100048304	Boesen	Feb 2010	A1
20100069155	Schwartz et al.	Mar 2010	A1
20100178987	Pacey	Jul 2010	A1
20100197410	Leen et al.	Aug 2010	A1
20100234110	Clarkson	Sep 2010	A1
20100240440	Szrek et al.	Sep 2010	A1
20100244376	Johnson	Sep 2010	A1
20100244382	Snow	Sep 2010	A1
20100252992	Sines	Oct 2010	A1
20100255899	Paulsen	Oct 2010	A1
20100276880	Grauzer et al.	Nov 2010	A1
20100311493	Miller et al.	Dec 2010	A1
20100311494	Miller et al.	Dec 2010	A1
20100314830	Grauzer et al.	Dec 2010	A1
20100320685	Grauzer et al.	Dec 2010	A1
20110006480	Grauzer et al.	Jan 2011	A1
20110012303	Kourgiantakis et al.	Jan 2011	A1
20110024981	Tseng	Feb 2011	A1
20110052049	Rajaraman et al.	Mar 2011	A1
20110062662	Ohta et al.	Mar 2011	A1
20110078096	Bounds	Mar 2011	A1
20110105208	Bickley	May 2011	A1
20110109042	Rynda et al.	May 2011	A1
20110130185	Walker	Jun 2011	A1
20110130190	Hamman et al.	Jun 2011	A1
20110159952	Kerr	Jun 2011	A1
20110159953	Kerr	Jun 2011	A1
20110165936	Kerr	Jul 2011	A1
20110172008	Alderucci	Jul 2011	A1
20110183748	Wilson et al.	Jul 2011	A1
20110230268	Williams	Sep 2011	A1
20110269529	Baerlocher	Nov 2011	A1
20110272881	Sines	Nov 2011	A1
20110285081	Stasson	Nov 2011	A1
20110287829	Clarkson et al.	Nov 2011	A1
20120015724	Ocko et al.	Jan 2012	A1
20120015725	Ocko et al.	Jan 2012	A1
20120015743	Lam et al.	Jan 2012	A1
20120015747	Ocko et al.	Jan 2012	A1
20120021835	Keller et al.	Jan 2012	A1
20120034977	Kammler	Feb 2012	A1
20120062745	Han et al.	Mar 2012	A1
20120074646	Grauzer et al.	Mar 2012	A1
20120091656	Blaha et al.	Apr 2012	A1
20120095982	Lennington et al.	Apr 2012	A1
20120161393	Krenn et al.	Jun 2012	A1
20120175841	Grauzer et al.	Jul 2012	A1
20120181747	Grauzer et al.	Jul 2012	A1
20120187625	Downs, III et al.	Jul 2012	A1
20120242782	Huang	Sep 2012	A1
20120286471	Grauzer et al.	Nov 2012	A1
20120306152	Krishnamurty et al.	Dec 2012	A1
20130020761	Sines et al.	Jan 2013	A1
20130085638	Weinmann et al.	Apr 2013	A1
20130099448	Scheper et al.	Apr 2013	A1
20130109455	Grauzer et al.	May 2013	A1
20130132306	Kami et al.	May 2013	A1
20130228972	Grauzer et al.	Sep 2013	A1
20130300059	Sampson et al.	Nov 2013	A1
20130337922	Kuhn et al.	Dec 2013	A1
20140027979	Stasson et al.	Jan 2014	A1
20140094239	Grauzer et al.	Apr 2014	A1
20140103606	Grauzer et al.	Apr 2014	A1
20140138907	Rynda et al.	May 2014	A1
20140145399	Krenn et al.	May 2014	A1
20140171170	Krishnamurty et al.	Jun 2014	A1
20140175724	Huhtala et al.	Jun 2014	A1
20140183818	Czyzewski et al.	Jul 2014	A1

Foreign Referenced Citations (52)

Number	Date	Country
5025479	Mar 1980	AU
757636	Feb 2003	AU
2266555	Apr 1998	CA
2284017	Sep 1998	CA
2612138	Dec 2006	CA
101127131	Feb 2008	CN
201139926	Oct 2008	CN
24952	Feb 2013	CZ
672616	Mar 1939	DE
2757341	Jun 1978	DE
3807127	Sep 1989	DE
777514	Feb 2000	EP
1194888	Apr 2002	EP
1502631	Feb 2005	EP
1713026	Oct 2006	EP
1 575 261	Aug 2012	EP
2375918	Jul 1978	FR
337147	Oct 1930	GB
414014	Jul 1934	GB
10063933	Mar 1998	JP
11045321	Feb 1999	JP
2000251031	Sep 2000	JP
2001327647	Nov 2001	JP
2002165916	Jun 2002	JP
2003250950	Sep 2003	JP
2005198668	Jul 2005	JP
2008246061	Oct 2008	JP
8700764	Feb 1987	WO
9221413	Dec 1992	WO
9528210	Oct 1995	WO
9607153	Mar 1996	WO
9710577	Mar 1997	WO
9814249	Apr 1998	WO
9840136	Sep 1998	WO
9943404	Sep 1999	WO
9952610	Oct 1999	WO
9952611	Oct 1999	WO
0051076	Aug 2000	WO
0156670	Aug 2001	WO
0205914	Jan 2002	WO
2004067889	Aug 2004	WO
2004112923	Dec 2004	WO
2006031472	Mar 2006	WO
2006039308	Apr 2006	WO
2008006023	Jan 2008	WO
2008005286	Jan 2008	WO
2008091809	Jul 2008	WO
2009137541	Nov 2009	WO
2010001032	Jan 2010	WO
2010055328	May 2010	WO
2010117446	Oct 2010	WO
2013019677	Feb 2013	WO

Non-Patent Literature Citations (85)

Entry
PCT International Search Report and Written Opinion of the International Searching Authority for PCT/US13/59665, dated Apr. 25, 2014, 21 pages.
DVD Labeled “Luciano Decl. Ex. K”. This is the video taped live Declaration of Mr. Luciano taken during preparation of litigation (Oct. 23, 2003).
DVD labeled Morrill Decl. Ex. A:. This is the video taped live Declaration of Mr. Robert Morrill, a lead trial counsel for the defense, taken during preparation for litigation. He is describing the operation of the Roblejo Prototype device. (Jan. 15, 2004).
DVD Labeled “Solberg Decl. Ex. C”. Exhibit C to Declaration of Hal Solberg, a witness in litigation, signed Dec. 1, 2003.
DVD labeled “Exhibit 1”. This is a video taken by Shuffle Master personnel of the live operation of a CARD One2Six™ Shuffler (Oct. 7, 2003).
Documents submitted in the case of Shuffle Master, Inc. v. Card Austria, et al., Case No. CV-N-0508-HDM-(VPC) (Consolidated with Case No. CV-N-02-0244-ERC-(RAM)), May 6, 2003, Part 1 of 23 (Master Index and Binder 1, 1 of 2).
Documents submitted in the case of Shuffle Master, Inc. v. Card Austria, et al., Case No. CV-N-0508-HDM-(VPC) (Consolidated with Case No. CV-N-02-0244-ERC-(RAM)), May 6, 2003, Part 2 of 23 (Master Index and Binder 1, 2 of 2).
Documents submitted in the case of Shuffle Master, Inc. v. Card Austria, et al., Case No. CV-N-0508-HDM-(VPC) (Consolidated with Case No. CV-N-02-0244-ERC-(RAM)), May 6, 2003, Part 3 of 23 (Binder 2, 1 of 2).
Documents submitted in the case of Shuffle Master, Inc. v. Card Austria, et al., Case No. CV-N-0508-HDM-(VPC) (Consolidated with Case No. CV-N-02-0244-ERC-(RAM)), May 6, 2003, Part 4 of 23 (Binder 2, 2 of 2).
Documents submitted in the case of Shuffle Master, Inc. v. Card Austria, et al., Case No. CV-N-0508-HDM-(VPC) (Consolidated with Case No. CV-N-02-0244-ERC-(RAM)), May 6, 2003, Part 5 of 23 (Binder 3, 1 of 2).
Documents submitted in the case of Shuffle Master, Inc. v. Card Austria, et al., Case No. CV-N-0508-HDM-(VPC) (Consolidated with Case No. CV-N-02-0244-ERC-(RAM)), May 6, 2003, Part 6 of 23 (Binder 3, 2 of 2).
Documents submitted in the case of Shuffle Master, Inc. v. Card Austria, et al., Case No. CV-N-0508-HDM-(VPC) (Consolidated with Case No. CV-N-02-0244-ERC-(RAM)), May 6, 2003, Part 7 of 23 (Binder 4, 1 of 2).
Documents submitted in the case of Shuffle Master, Inc. v. Card Austria, et al., Case No. CV-N-0508-HDM-(VPC) (Consolidated with Case No. CV-N-02-0244-ERC-(RAM)), May 6, 2003, Part 8 of 23 (Binder 4, 2 of 2).
Documents submitted in the case of Shuffle Master, Inc. v. Card Austria, et al., Case No. CV-N-0508-HDM-(VPC) (Consolidated with Case No. CV-N-02-0244-ERC-(RAM)), May 6, 2003, Part 9 of 23 (Binder 5 having no contents; Binder 6, 1 of 2).
Documents submitted in the case of Shuffle Master, Inc. v. Card Austria, et al., Case No. CV-N-0508-HDM-(VPC) (Consolidated with Case No. CV-N-02-0244-ERC-(RAM)), May 6, 2003, Part 10 of 23 (Binder 6, 2 of 2).
Documents submitted in the case of Shuffle Master, Inc. v. Card Austria, et al., Case No. CV-N-0508-HDM-(VPC) (Consolidated with Case No. CV-N-02-0244-ERC-(RAM)), May 6, 2003, Part 11 of 23 (Binder 7, 1 of 2).
Documents submitted in the case of Shuffle Master, Inc. v. Card Austria, et al., Case No. CV-N-0508-HDM-(VPC) (Consolidated with Case No. CV-N-02-0244-ERC-(RAM)), May 6, 2003, Part 12 of 23 (Binder 7, 2 of 2).
Documents submitted in the case of Shuffle Master, Inc. v. Card Austria, et al., Case No. CV-N-0508-HDM-(VPC) (Consolidated with Case No. CV-N-02-0244-ERC-(RAM)), May 6, 2003, Part 13 of 23 (Binder 8, 1 of 5).
Documents submitted in the case of Shuffle Master, Inc. v. Card Austria, et al., Case No. CV-N-0508-HDM-(VPC) (Consolidated with Case No. CV-N-02-0244-ERC-(RAM)), May 6, 2003, Part 14 of 23 (Binder 8, 2 of 5).
Documents submitted in the case of Shuffle Master, Inc. v. Card Austria, et al., Case No. CV-N-0508-HDM-(VPC) (Consolidated with Case No. CV-N-02-0244-ERC-(RAM)), May 6, 2003, Part 15 of 23 (Binder 8, 3 of 5).
Documents submitted in the case of Shuffle Master, Inc. v. Card Austria, et al., Case No. CV-N-0508-HDM-(VPC) (Consolidated with Case No. CV-N-02-0244-ERC-(RAM)), May 6, 2003, Part 16 of 23 (Binder 8, 4 of 5).
Documents submitted in the case of Shuffle Master, Inc. v. Card Austria, et al., Case No. CV-N-0508-HDM-(VPC) (Consolidated with Case No. CV-N-02-0244-ERC-(RAM)), May 6, 2003, Part 17 of 23 (Binder 8, 5 of 5).
Documents submitted in case of Shuffle Master, Inc. v. Card Austria, et al., Case No. CV-N-0508-HDM-(VPC) Consolidated with Case No. CV-N-02-0244-ERC-(RAM)), May 6, 2003, scan of color pages, for clarity, Part 18 of 23 (color copies from Binder 1).
Documents submitted in case of Shuffle Master, Inc. v. Card Austria, et al., Case No. CV-N-0508-HDM-(VPC) Consolidated with Case No. CV-N-02-0244-ERC-(RAM)), May 6, 2003, scan of color pages, for clarity, Part 19 of 23 (color copies from Binder 3).
Documents submitted in case of Shuffle Master, Inc. v. Card Austria, et al., Case No. CV-N-0508-HDM-(VPC) Consolidated with Case No. CV-N-02-0244-ERC-(RAM)), May 6, 2003, scan of color pages, for clarity, Part 20 of 23 (color copies from Binder 4).
Documents submitted in case of Shuffle Master, Inc. v. Card Austria, et al., Case No. CV-N-0508-HDM-(VPC) Consolidated with Case No. CV-N-02-0244-ERC-(RAM)), May 6, 2003, scan of color pages, for clarity, Part 21 of 23 (color copies from Binder 6).
Documents submitted in case of Shuffle Master, Inc. v. Card Austria, et al., Case No. CV-N-0508-HDM-(VPC) Consolidated with Case No. CV-N-02-0244-ERC-(RAM)), May 6, 2003, scan of color pages, for clarity, Part 22 of 23 (color copies from Binder 8, part 1 of 2).
Documents submitted in case of Shuffle Master, Inc. v. Card Austria, et al., Case No. CV-N-0508-HDM-(VPC) Consolidated with Case No. CV-N-02-0244-ERC-(RAM)), May 6, 2003, scan of color pages, for clarity, Part 23 of 23 (color copies from Binder 8, part 2 of 2).
VendingData Corporation's Responses to Shuffle Master, Inc.'s First set of interrogatories for Shuffler Master, Inc. vs. VendingData Corporation, In the U.S. District Court, District of Nevada, No. CV-S-04-1373-JCM-LRL, Mar. 14, 2005.
“ACE, Single Deck Shuffler,” Shuffle Master, Inc., (2005), 2 pages.
“Automatic casino card shuffle,” Alibaba.com, (last visited Jul. 22, 2014), 2 pages.
“Error Back propagation,” http://willamette.edu˜gorr/classes/cs449/backprop.html (4 pages), Nov. 13, 2008.
“i-Deal,” Bally Technologies, Inc., (2014), 2 pages.
“Shufflers—SHFL entertainment,” Gaming Concepts Group, (2012), 6 pages.
“TAG Archives: Shuffle Machine,” Gee Wiz Online, (Mar. 25, 2013), 4 pages.
1/3″ B/W CCD Camera Module EB100 by EverFocus Electronics Corp., Jul. 31, 2001, 3 pgs.
Canadian Office Action for CA 2,580,309 dated Mar. 20, 2012 (6 pages).
Christos Stergiou and Dimitrios Siganos, “Neural Networks,” http://www.doc.ic.ac.uk/˜nd/surprise—96/journal/vol4/ cs11/report.html (13 pages), Dec. 15, 2011.
European Patent Application Search Report—European Patent Application No. 06772987.1, Dec. 21, 2009.
Genevieve Orr, CS-449: Neural Networks Willamette University, http://www.willamette.edu/˜gorr/classes/cs449/intro.html (4 pages), Fall 1999.
http://www.google.com/search?tbm=pts&q=Card+handling+devicve+with+input+and+outpu . . . Jun. 8, 2012.
http://www.google.com/search?tbm=pts&q=shuffling+zone+onOopposite+site+of+input+ . . . Jul. 18, 2012.
Litwiller, Dave, CCD vs. CMOS: Facts and Fiction reprinted from Jan. 2001 Issue of Photonics Spectra, Laurin Publishing Co. Inc. (4 pages).
Malaysian Patent Application Substantive Examination Adverse Report—Malaysian Patent Application Serial No. PI 20062710, Sep. 6, 2006.
PCT International Preliminary Examination Report for corresponding International Application No. PCT/US02/31105 filed Sep. 27, 2002.
PCT International Preliminary Report on Patentability of the International Searching Authority for PCT/US05/31400, dated Oct. 16, 2007, 7 pages.
PCT International Search Report and Written Opinion—International Patent Application No. PCT/US2006/22911, Dec. 28, 2006.
PCT International Search Report and Written Opinion for International Application No. PCT/US2007/023168, dated Sep. 12, 2008, 8 pages.
PCT International Search Report and Written Opinion for International Application No. PCT/US2007/022858, mailed Apr. 18, 2008, 7 pages.
PCT International Search Report and Written Opinion for PCT/US07/15036, dated Sep. 23, 2008, 3 pages.
PCT International Search Report and Written Opinion for PCT/US07/15035, dated Sep. 29, 2008, 3 pages.
PCT International Search Report and Written Opinion of the International Searching Authority for PCT/GB2011/051978, dated Jan. 17, 2012, 11 pages.
PCT International Search Report and Written Opinion of the International Searching Authority for PCT/IB2013/001756, dated Jan. 10, 2014, 7 pages.
PCT International Search Report and Written Opinion of the International Searching Authority for PCT/US11/59797, datedMar. 27, 2012, 14 pages.
PCT International Search Report and Written Opinion of the International Searching Authority for PCT/US2008/007069, dated Sep. 8, 2008, 10 pages.
PCT International Search Report and Written Opinion of the International Searching Authority for PCT/US2010/001032, dated Jun. 16, 2010, 11 pages.
PCT International Search Report and Written Opinion, PCT Application No. PCT/US2013/062391, Dec. 17, 2013, 13 pages.
PCT International Search Report and Written Opinion, PCT/US12/48706, Oct. 16, 2012, 12 pages.
PCT International Search Report for International Application No. PCT/US2003/015393, mailed Oct. 6, 2003.
PCT International Search Report for PCT/US2005/034737 dated Apr. 7, 2006 (WO06/039308).
PCT International Search Report for PCT/US2007/022894, dated Jun. 11, 2008, 2 pages.
PCT International Search Report and Written Opinion of the International Searching Authority for PCT/US05/31400, dated Sep. 25, 2007, 8 pages.
PCT International Search Report and Written Opinion, PCT Application No. PCT/US2015/022158, Jun. 17, 2015, 13 pages.
Philippines Patent Application Formality Examination Report—Philippines Patent Application No. 1-2006-000302, Jun. 13, 2006.
Press Release for Alliance Gaming Corp., Jul 26, 2004—Alliance Gaming Announces Control with Galaxy Macau for New Mind Play Baccarat Table Technology, http://biz.yahoo.com/prnews.
Scarne's Encyclopedia of Games by John Scarne, 1973, “Super Contract Bridge”, p. 153.
Service Manual/User Manual for Single Deck Shufflers: BG1, BG2 and BG3 by Shuffle Master © 1996.
Shuffle Master Gaming, Service Manual, ACETM Single Deck Card Shuffler, (1998), 63 pages.
Shuffle Master Gaming, Service Manual, Let It Ride Bonus® With Universal Keypad, 112 pages, © 2000 Shuffle Master, Inc.
Shuffle Master's Reply Memorandum in Support of Shuffle Master's Motion for Preliminary Injunction for Shuffle Master, Inc. vs. VendingData Corporation, in the U.S. District Court, District of Nevada, No. CV-S-04-1373-JCM-LRL, Nov. 29, 2004.
Singapore Patent Application Examination Report—Singapore Patent Application No. SE 2008 01914 A, Aug. 6, 2006.
Specification of Australian Patent Application No. 31577/95, filed Jan. 17, 1995, Applicants: Rodney G. Johnson et al., Title: Card Handling Apparatus.
Specification of Australian Patent Application No. Not Listed, filed Aug. 15, 1994, Applicants: Rodney G. Johnson et al., Title: Card Handling Apparatus.
Statement of Relevance of Cited References, Submitted as Part of a Third-Party Submission Under 37 CFR 1.290 on Dec. 7, 2012 (12 pages).
Tbm=pts&hl=en Google Search for card handling device with storage area, card removing system pivoting arm and processor . . . ; http://www.google.com/?tbrn=pts&hl=en; Jul. 28, 2012.
Tracking the Tables, by Jack Bularsky, Casino Journal, May 2004, vol. 17, No. 5, pp. 44-47.
United States Court of Appeals for the Federal Circuit Decision Decided Dec. 27, 2005 for Preliminary Injuction for Shuffle Master, Inc. vs. VendingData Corporation, in the U.S. District Court, District of Nevada, No. CV-S-04-1373-JCM-LRL.
VendingData Corporation's Answer and Counterclaim Jury Trial Demanded for Shuffle Master, Inc. vs. VendingData Corporation, in the U.S. District Court, District of Nevada, No. CV-S-04-1373-JCM-LRL, Oct. 25, 2004.
VendingData Corporation's Opposition to Shuffle Master Inc.'s Motion for Preliminary Injection for Shuffle Master, Inc. vs. VendingData Corporation, in the U.S. District Court, District of Nevada, No. CV-S-04-1373-JCM-LRL, Nov. 12, 2004.
Documents submitted in case of Shuffle Master, Inc. v. Card Austria, et al., Case No. CV-N-0508-HDM-(VPC) Consolidated with Case No. CV-N-02-0244-ERC-(RAM)), May 6, 2003, scan of color pages, for clarity, Part 18 of 23.
Documents submitted in case of Shuffle Master, Inc. v. Card Austria, et al., Case No. CV-N-0508-HDM-(VPC) Consolidated with Case No. CV-N-02-0244-ERC-(RAM)), May 6, 2003, scan of color pages, for clarity, Part 19 of 23.
Documents submitted in case of Shuffle Master, Inc. v. Card Austria, et al., Case No. CV-N-0508-HDM-(VPC) Consolidated with Case No. CV-N-02-0244-ERC-(RAM)), May 6, 2003, scan of color pages, for clarity, Part 20 of 23.
Documents submitted in case of Shuffle Master, Inc. v. Card Austria, et al., Case No. CV-N-0508-HDM-(VPC) Consolidated with Case No. CV-N-02-0244-ERC-(RAM)), May 6, 2003, scan of color pages, for clarity, Part 21 of 23.
Documents submitted in case of Shuffle Master, Inc. v. Card Austria, et al., Case No. CV-N-0508-HDM-(VPC) Consolidated with Case No. CV-N-02-0244-ERC-(RAM)), May 6, 2003, scan of color pages, for clarity, Part 22 of 23.
Documents submitted in case of Shuffle Master, Inc. v. Card Austria, et al., Case No. CV-N-0508-HDM-(VPC) Consolidated with Case No. CV-N-02-0244-ERC-(RAM)), May 6, 2003, scan of color pages, for clarity, Part 23 of 23.

Related Publications (1)

	Number	Date	Country
	20140091521 A1	Apr 2014	US

Card recognition system, card handling device, and method for tuning a card handling device

Information

Patent Number

Date Filed

Date Issued

Inventors

Original Assignees

Examiners

Agents

CPC

Field of Search

US

CPC

International Classifications