System and method for robotic ticket scratch processing via a live remote mobile interface

Abstract

The controller is configured to obtain a first video stream from a first video camera proximate to the ticket vending machine, transmit the first video stream to an application server for distribution to a user device, receive a ticket issuance command for the ticket vending machine from the application server, cause the ticket vending machine to issue a ticket having a scratch area based on the ticket issuance command, receive user-provided scratch data from the application server, and cause the robotic scratch device to scratch the scratch area in accordance with the scratch data.

Description

[Technical field]

[0001]

[0001] This application is a continuation of, and claims priority to, U.S. Patent Application No. 17 / 662,291, filed May 6, 2022, which is a continuation of, U.S. Patent Application No. 17 / 650,215, filed February 7, 2022. This application is also a continuation of, and claims priority to, U.S. Patent Application No. 17 / 650,215, filed February 7, 2022, U.S. Patent Application No. 17 / 655,996, filed March 22, 2022, U.S. Patent Application No. 17 / 655,998, filed March 22, 2022, and U.S. Patent Application No. 17 / 655,999, filed March 22, 2022. Each of these applications is a continuation of U.S. patent application Ser. No. 17 / 478,907, filed September 18, 2021, which issued on March 22, 2022 as U.S. Patent No. 11,278,789, claiming priority to U.S. Provisional Patent Application No. 63 / 203,666, filed July 27, 2021. This application is also a continuation of and claims priority to U.S. patent application Ser. No. 17 / 448,046, filed September 18, 2021, which claims priority to U.S. Provisional Patent Application No. 63 / 203,666, filed July 27, 2021. This application also claims priority to U.S. Provisional Patent Application No. 63 / 206,666, filed July 27, 2021. Each of the foregoing applications is incorporated herein by reference in its entirety.

[0002]

[0002] This application relates to the field of networked robotic devices configured to interact with government-regulated lottery ticket dispensers. [Background technology]

[0003]

[0003] The sale of lottery tickets (also called scratch tickets or scratchers) is typically regulated by a state or other governmental agency, which requires that the tickets be sold at a physical location (e.g., a point of sale) within its jurisdiction. Thus, a person who wants to participate in a favorite lottery game but cannot be present at one of the physical locations (e.g., due to vacation, disability, or lack of a convenience store location) may be prevented or discouraged from purchasing a desired lottery ticket. Due to the nature of lotteries, many players prefer to purchase the same ticket and play the same numbers every lottery cycle, and therefore may be disappointed if they end up missing a particular lottery cycle.

[0004]

[0004] Additionally, lottery scratch tickets typically require a physical action as part of game play. In some cases, the ticket must be scratched to reveal the basic information (e.g., numbers, shapes, patterns, etc.) needed to determine whether the ticket is a winning ticket and, if so, what the prize on the ticket is. This can deter people who are physically unable to play (e.g., due to conditions that make it difficult to scratch the ticket) from playing.

[0005]

[0005] Finally, lottery scratch tickets may be distributed among a group of players (e.g., family members, coworkers, etc.) to share the cost of purchasing multiple tickets (a "lottery pool" or "office pool"), thereby increasing the odds of winning. In such cases, one person typically pools the money, purchases the tickets, plays the tickets, and reports the results to others. Thus, others in the group often do not share in the gameplay experience and are less likely to continue contributing to future group ticket purchases. Summary of the Invention

[0006]

[0006] This disclosure describes a system and method using robotic devices that allows for virtual play of lottery games while complying with government regulations. Players who are not physically present at the point of sale (e.g., in a remote location) or who are physically present at the point of sale but unable to physically play their tickets may participate in desired lottery games. The system and method allows such users to participate in lotteries in each of the aforementioned scenarios in a manner that provides a comparable level of engagement and complies with applicable state, local, federal, municipal, and / or international game play regulations (e.g., regarding location, signatures, audits, etc.).

[0007] In one aspect, a system, method, and apparatus for robotic ticket scratch processing via a live remote mobile interface is disclosed. The user interface runs on a mobile device, tablet, computer, or application on a web browser. The user can be physically present in a remote location (such as a remote location in a particular state, or an overseas location). In some implementations, the user is not remote but is physically present (such as at a bingo hall) and may use the service for convenience or due to physical limitations.

[0008] In some implementations, the ticket issuing machine is equipped with a roll of tickets or is individually equipped depending on the form factor of the ticket to be obtained. There are one or more ticket issuing machines in the setup. In some implementations, the machine is in a secure room. In some implementations, the machine is in a retail store or other public location.

[0009]

[0009] In some implementations, there is a live video feed of the ticket machine. The user uses a user interface to select the desired ticket (and the machine, if the same ticket is available at multiple machines). The ticket is dispensed from the machine.

[0010]

[0010] In some implementations, cameras are positioned at multiple live angles, including top and bottom. When a ticket is dispensed, the bottom camera images the ticket and a scanner scans the ticket's lot / serial number. The controller sends the information to an application server. The ticket is assigned to a specific user by the application server. In some implementations, a user can remotely control the pan, tilt, and zoom of one or more cameras.

[0011] In some implementations, a user can choose to sign a ticket using a mobile interface: The user enters their signature using a touch screen, computer mouse, stylus, digital pen, keyboard, or other input method that captures an XY signature (a digital facsimile of the signature).

[0012]

[0012] In some implementations, the signature file is sent from the mobile application to the application server, to the controller, and to the robotic arm, which physically signs the ticket. The user can see the signature depicted on the ticket in real time. In some implementations, the signature feedback is replicated on the user interface.

[0013] In some implementations, a user virtually scratches a ticket from a remote location using a touch screen, mouse, stylus, digital pen, or other user input. In some implementations, the ticket scratching process may be fully automated and require no user interaction (other than starting and / or stopping). In some implementations, the system may use random XY coordinates.

[0014]

[0014] In some implementations, as the user scratches and watches the live video feed, a robotic arm is physically scratching the ticket, rubbing the ticket, or remotely revealing information on the ticket by some other means. In some embodiments, a simulated ticket exists on the mobile device (with or without a video feed) and real-time feedback is provided to digitally simulate the ticket scratching process on the mobile device. In some implementations, two or more people may be watching the same feed and / or virtual scratching process. In some implementations, there may be guest viewers who have no knowledge of the user or interest in the ticket.

[0015]

[0015] In some implementations, upon completion of the scratching, a barcode scanner scans the revealed unique code. In some implementations, the unique code is on the back of the ticket. In some implementations, the unique code does not need to be revealed. In some implementations, the code is in a fixed location and no user interaction is required to scratch the code.

[0016]

[0016] In some implementations, the unique code is sent by a scanner to a ticket exchange terminal and to a validation server at the ticket agency, which validates the ticket. The status of the ticket is returned. If the ticket is a winning ticket, the application server sends information, including the amount, to the mobile application. The mobile application can then provide a visual, audible, and / or tactile alert to the user. Winning funds are credited into a user account. The user account can be linked to a bank account or card account. In some implementations, the funds may be transferred to a virtual currency account (such as Bitcoin).

[0017]

[0017] Referring again to the robotic machines, in some implementations there is a ticket cutter that cuts the latest ticket from the stream of tickets. In some implementations there is a ticket sorter that picks out winning tickets or distinguishes them from losing tickets. In some implementations there may also be a pile of error tickets if system errors, imperfect scans, or imperfect scratches occur.

[0018]

[0018] In some implementations, each transaction (ticket scanning, signing, and / or scratching) may be video recorded and stored for later recall and authentication verification based on audit and / or control requirements. [Brief description of the drawings]

[0019] [Figure 1] FIG. 1 is a system diagram of a networked lottery system 100 according to some implementations. [Diagram 2]

[0020] 2 is a schematic diagram of the networked lottery system 100 of FIG. 1, including data flow, according to some implementations. [Diagram 3]

[0021] 3 is a flow diagram of a method of operating the ticket processing system of the lottery system 100 of FIGS. 1 and 2 according to some implementations. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0020]

[0022] Like reference numbers refer to corresponding parts throughout the several views of the drawings.

[0021]

[0023] In the age of mobile devices and connectivity, virtual playing of lottery games can be accomplished using robotic devices present within a regulated jurisdiction and live remote mobile interfaces associated with players. Examples of such robotic devices, mobile interfaces, and methods of their use are described herein.

[0022]

[0024] FIG. 1 is a system diagram of a networked lottery system 100 according to some implementations, and FIG. 2 is a schematic diagram of the networked lottery system 100 of FIG. 1 including more detailed data flows according to some implementations.

[0023]

[0025] As shown in FIGS. 1 and 2, lottery system 100 includes a ticket processing system 102 that is physically located within the jurisdiction that governs the lottery administered by lottery system 100 .

[0024]

[0026] The ticket processing system 102 includes a ticket issuing machine 190, an exchange terminal 120, a controller 110, a scanning device (scanner) 118, one or more video cameras 112, and a number of robotic components including a robotic signature mechanism (signature machine) 114, a robotic scratch mechanism (scratch machine) 116, a cutting device (cutter) 132, and / or a sorting device (sorter) 134.

[0025]

[0027] The ticket processing system 102 may be located in a public location (e.g., a retail store or other public location) or in a dedicated location, such as a secure room designed to house the various components of the processing system 102.

[0026]

[0028] The ticket processing system 102 or components included in the ticket processing system 102 may be referred to as a robotic machine or robotic device. In some implementations, the components forming the robotic machine or robotic device include the controller 110, the signature machine 114, the scratch machine 116, the cutter 132, the sorter 134, and hardware for receiving, moving, orienting, or otherwise handling the tickets issued from the ticket issuing machine 190 to ensure proper imaging, scanning, signing, scratching, and processing of each ticket issued from the ticket issuing machine 190.

[0027]

[0029] The ticket dispenser 190 includes a plurality of lottery tickets 192 (e.g., loaded with a roll of tickets 192 or loaded individually depending on the ticket form factor). There may be one or more ticket dispensers 190 within a single processing system 102.

[0028]

[0030] The ticket dispenser 190 is configured to receive ticket issuing commands from the controller 110 and either output the ticket specified by the ticket issuing command (if there is more than one type of ticket in the ticket dispenser 190) or output the ticket due to receiving the ticket issuing command regardless of whether the ticket issuing command specifies a particular type of ticket (e.g., if there is only one type of ticket in the ticket dispenser 190). The ticket issuing command may include a quantity of tickets to be issued. In such a scenario, the ticket dispenser 190 is configured to issue the number of tickets specified by the ticket issuing command, one at a time, so that other components of the processing system 102 can process each ticket in the manner described below.

[0029]

[0031] In some implementations, other components of the processing system 102 (e.g., the signature machine 114, the scratch machine 116, the camera 112, and / or the scanner 118) may be located within the ticket machine 190. Alternatively, the ticket machine 190 may be a machine modified to accept ticket issuing commands from the controller 110 instead of or in addition to ticket issuing commands triggered by physical game play (e.g., inserting money, pressing a selection button, etc.) at the ticket machine 190 itself. In such a scenario, the other components of the processing system 102 may be located outside and in close proximity to the ticket machine 190 to process tickets output by the ticket machine 190.

[0030]

[0032] The tickets included in the ticket issuing machine 190 (e.g., arranged in a ticket roll 192 or in any other configuration) may also be referred to as scratch cards, scratch-offs, scratch tickets, scratchers, scratch-its, scratch games, scratch and win, instant games, or instant lottery tickets. The tickets may be made of a thin paper-based card stock or plastic. One or more areas may contain hidden information that may be revealed by scratching an opaque substance (e.g., a silk-screened latex panel that is adhered to the ticket body, etc.) or removing the adhesive. The opaque substance may also be referred to as a coating, panel, label, scratch coating, scratch panel, scratch label, scratch substance, or scratch area.

[0031]

[0033] In some implementations, the entire scratchable area (or at least a threshold amount of the scratchable area) must be scratched to see if a prize has been won. The ticket may be printed to reveal if a prize has been won or not, or a secret code. In some implementations, the outcome does not depend on which part is scratched. In other implementations, some areas but not all areas must be scratched. This is the case in quizzes where the area corresponding to the correct answer is scratched, or in some applications where the card wins or misses depending on which area is scratched. In these cases, scratching too many areas will invalidate the card. After a miss, all areas can be scratched to see how or what was won.

[0032]

[0034] The video cameras 112 may be positioned in multiple locations within the ticket processing system 102 to provide multiple live angles. For example, a first camera 112 may include the ticket dispenser 190 within its field of view, a second camera 112 may include the top of the issued ticket 196 within its field of view, and a third camera 112 may include the bottom of the issued ticket 196 within its field of view. Thus, a user of the lottery system 100 can remotely (i) view the ticket dispenser 190 to determine which machine and / or ticket to select, (ii) view the top of the issued ticket 196 to view the scratch area, and / or (iii) view the bottom of the issued ticket 196 to view the signature area.

[0033]

[0035] In some implementations, a user can remotely control the pan, tilt, and zoom of the camera 112. Optionally, two or more users can watch the same video feed provided by the camera 112 during a single ticket play session (e.g., to view the virtual scratch process described below). In some implementations, there may be guest viewers who have no knowledge of the users or interest in ticket issuing and scratching.

[0034]

[0036] The scanner 118 is positioned proximate to an area where an issued ticket 196 is presented and is configured to scan the identification information on the issued ticket 196. For example, the ticket's identification information may include a unique code, such as a lot number or serial number, that identifies the ticket. Such a code may or may not be hidden behind an opaque material. The scanner 118 is configured to transmit the identification information (either a scan of the identification information or the identification information itself) to the controller 110.

[0035]

[0037] In some implementations, the scanner 118 is further configured to scan information (e.g., numbers, letters, symbols, marks, etc.) hidden behind an opaque substance that appears when the ticket is scratched. The scanner 118 is configured to transmit such information (either a scan of the information or the information itself) to the redemption terminal 120.

[0036]

[0038] Ticket redemption terminal 120 includes or is coupled to scanner 118 and configured to receive data captured by scanner 118. Ticket redemption terminal 120 may transmit the scanned data (or information derived from the scanned data, such as a number) to controller 110 or to ticket validation server 122, depending on the nature of the scanned data.

[0037]

[0039] In a first example, the ticket redemption terminal 120 sends the scanned identification number (e.g., serial number) of the issued ticket 196 to the controller 110, which may then (e.g., via the user device 104 and application 105, the application server 108, and the controller 110) link the ticket associated with the scanned identification number to a user account associated with the user currently playing with that ticket.

[0038]

[0040] In a second example, the ticket exchange terminal 120 may send scanned data associated with the game play of the ticket (e.g., a code emerging from under the opaque material) to the ticket validation server 122 for validation by the ticket agency 124 (e.g., to validate whether the ticket is a winning or non-winning ticket). In some implementations, the data associated with the game play may be an identification number (e.g., a serial number). In other words, a single number may not only identify the ticket (and be linked to a user account by the application server 108), but also serve as the basis for validating whether the ticket is a winning or non-winning ticket. In such a scenario, the ticket may not even need to be played (e.g., it does not need to be scratched) and scanning a single number on the issued ticket 196 may be sufficient to (i) link the ticket to a user account and (ii) validate the status of the ticket (e.g., winning or non-winning).

[0039]

[0041] The ticket redemption terminal 120 is configured to receive ticket validation information (eg, win / lose information) from the ticket validation server 122 and to transmit the ticket validation information to the application server 108 for further processing.

[0040]

[0042] The controller 110 comprises at least one processor (also referred to as a processing unit, processor, computer, programmable device, or any electronic technology capable of executing instructions or operations). The controller 110 comprises or is communicatively coupled to a memory that stores one or more programs executed by the processing unit of the controller. The memory includes computer readable media, including but not limited to connected storage media (e.g., hard disk drives, network disk drives, servers), internal storage media (e.g., RAM, ROM, EPROM, FLASH-EPROM, or any other memory chip or cartridge), removable storage media (e.g., CDs, DVDs, flash drives, memory cards, floppy disks, flexible disks), firmware, and / or other known or yet to be discovered storage media. Depending on its purpose, the storage can be temporary and / or non-transitory.

[0041]

[0043] The controller 110 is configured to receive ticket issuing commands from the application server 108 and transmit the received ticket issuing commands to the ticket issuing machine 190. The controller 110 is also configured to receive video data from the one or more cameras 112 and transmit the video data to the application server 108. The controller 110 is also configured to receive signature data and scratch data (described in more detail below) from the application server 108 and transmit the signature data and scratch data to the signature machine 114 and scratch 116, respectively. The controller 110 is also configured to receive scan data (e.g., the serial number and / or game play data discussed above) from the scanner 118 and transmit the scan data to the application server 108 for binding to the user account 106.

[0042]

[0044] In some implementations, the controller 110 may be configured to receive the win / loss information from the redemption terminal 120 and transmit the win / loss information to the application server 108. Alternatively, the redemption terminal 120 (or the ticket validation server 122) may transmit the win / loss information to the application server 108 without going through the controller 110.

[0043]

[0045] The signing machine 114 is a mechanical device configured to manipulate a writing tool (e.g., a pen, marker, or other signing tool) to sign a signature area of ​​a ticket according to signature data received from the user device 104 via the application server 108 and the controller 110. The signing machine 114 may also be referred to as a signing or signing device, a signing or signing mechanism, a signing or signing machine, an automated signing machine, or an automated pen. For example, the signing machine 114 may be a robotic arm.

[0044]

[0046] The signature machine 114 may be controlled remotely by a user interface of the application 105 of the user device 104. A user may virtually (remotely) control the signature machine 114 to sign the issued ticket 196 by signing locally on a user interface element on the application 105 of the user device 104 that resembles the signature area of ​​the ticket. For example, the user may use a touch screen, computer mouse, stylus, digital pen, keyboard, or other input method on the user device 104, thereby causing the application 105 to capture XY signature data (X and Y axes represent horizontal and vertical directions on the surface of the ticket). In some implementations, the XY signature data corresponds to a two-dimensional user-provided gesture that corresponds to the signature input on the user device. In some implementations, the user can see the signature depicted on the ticket in real time, with signature feedback replicated (displayed) on the user interface of the application 105.

[0045]

[0047] The scratch machine 116 is a mechanical device configured to operate a scratch tool (e.g., a needle, scratch tool, or other hard object) to scratch opaque material from a scratch area of ​​the ticket according to scratch data received from the user device 104 via the application server 108 and the controller 110. The scratch machine 116 may also be referred to as a scratch device, scratch mechanism, scratch machine, or automatic scratch machine. For example, the scratch machine 116 may be a robotic arm that physically scratches the ticket.

[0046]

[0048] In some implementations, the scratch machine 116 and the signing machine 114 may share some components. For example, a single robotic arm may be used to (i) sign a signature area of ​​a ticket when set in a signature mode (e.g., with a signing tool inserted at the end of the arm's travel) and (ii) scratch a scratch area of ​​a ticket when set in a scratch mode (e.g., with a scratch tool inserted at the end of the arm's travel). While the robotic arm is set in one mode, the tool associated with the other mode may be retracted from the end of the arm's travel.

[0047]

[0049] In some implementations, the scratch machine 116 and the signature machine 114 may be constructed and operated independently, such as in situations where the scratch area is on one side of the ticket and the signature area is on the opposite side of the ticket. Alternatively, for such ticket configurations, a ticket turning mechanism may reorient the ticket so that a single robotic arm can sign and scratch the ticket, as described above.

[0048]

[0050] The scratch machine 116 may be controlled remotely by a user interface of the application 105 of the user device 104. A user may virtually (remotely) control the scratcher 116 to scratch (or remove opaque material from) the scratch area of ​​the issued ticket 196 by locally interacting with user interface elements on the application 105 of the user device 104 that resemble the scratch area of ​​the ticket. For example, the user may use a touch screen (e.g., by using a swipe gesture), a computer mouse, a stylus, a digital pen, a keyboard, or other input method of the user device 104, thereby causing the application 105 to capture the scratch data. In some implementations, the scratch data captured by the application 105 is XY scratch data (X and Y axes representing horizontal and vertical directions on the surface of the ticket) corresponding to a two-dimensional user-provided gesture corresponding to a scratch input on the user device. Alternatively, the scratch data captured by the application 105 may include or comprise a command instructing the scratch machine 116 to scratch the scratch area of ​​the issued ticket (or remove opaque material from the scratch area) using a scratch pattern independent of any user-provided gesture. For example, a user may select a "scratch ticket" affordance on a user interface of the application 105 to send a scratch command to the scratch machine 116. The scratch machine 116 may receive the scratch command and scratch the scratch area of ​​the issued ticket (or remove opaque material from the scratch area) using a preconfigured scratch pattern or a random scratch pattern.

[0049]

[0051] In some implementations, the user can view the scratching process in real time on the issued ticket 196 with scratching process feedback replicated (displayed) on the user interface of the application 105. The scratching process feedback can be a digital simulation of the ticket being scratched on the user interface and / or a live video feed of the issued ticket 196 being scratched by the scratch machine 116.

[0050]

[0052] In some implementations, rather than manually interacting with a scratch element in the user interface of the application 105, the scratching process of an issued ticket 196 may be fully automated and require no user interaction other than to start and / or stop the scratch (e.g., controlled by one or more affordances on the user interface).

[0051]

[0053] The ticket cutter 132 (also referred to as a cutting device or cutting mechanism) is a mechanical device that includes a cutting element configured to separate issued tickets 196 from tickets in the stream 194 that have not yet been issued or processed. The ticket cutter 132 receives a cut command from the controller 110 after the ticket 196 has been processed (e.g., after the ticket has been signed, scratched, or scanned).

[0052]

[0054] The ticket sorter 134 (also referred to as a sorting device or sorting mechanism) is a mechanical device that includes a sorting element configured to extract or distinguish winning tickets from losing tickets. The ticket sorter 134 receives a sorting command from the controller 110 after the ticket 196 is processed (e.g., after the ticket is signed, scratched, and scanned). The ticket sorter 134 places winning tickets in a winning ticket pile or container 138 and losing tickets in a losing ticket pile or container 136, making them available for testing of the system and, in some cases, physical proof of the winning ticket that may be sent (e.g., mailed or otherwise delivered) to the ticket agency 124 and / or the user who purchased and / or played the ticket. In some implementations, in the event of a system error, incomplete scanning, or incomplete scratching, the ticket sorter 134 may place tickets corresponding to such errors in an error ticket pile or container (not shown) and making them available for troubleshooting the system.

[0053]

[0055] The application server 108 comprises at least one processor (also referred to as a processing unit, processor, computer, programmable device, or any electronic technology capable of executing instructions or operations). The application server 108 comprises or is communicatively coupled to a memory that stores one or more programs executed by the processing unit of the controller. The memory includes computer-readable media, including but not limited to connected storage media (e.g., hard disk drives, network disk drives, servers), internal storage media (e.g., RAM, ROM, EPROM, FLASH-EPROM, or any other memory chip or cartridge), removable storage media (e.g., CDs, DVDs, flash drives, memory cards, floppy disks, flexible disks), firmware, and / or other known or yet to be discovered storage media. Depending on its purpose, the storage can be temporary and / or non-transitory.

[0054]

[0056] The application server 108 is configured to receive commands (e.g., system 102 selection commands, machine 190 selection commands, and / or ticket issuing commands) and data (e.g., signature data and scratch data) from a plurality of user devices 104 (one representative device is shown in FIGS. 1 and 2 ) and to transmit the commands and data to a plurality of ticket processing systems 102 (one representative system 102 is shown in FIG. 2 ). The application server 108 is also configured to receive commands and data (e.g., scan data and / or video data) from the plurality of user devices 104 and to transmit the commands and data to the plurality of user devices 104.

[0055]

[0057] In some implementations, the application server 108 is also configured to receive win / loss (ticket status) information from the redemption terminal 120 or from the controller 110 and send a notification to the user device 104 conveying the win / loss information.

[0056]

[0058] In some implementations, the application server 108 is also configured to assign or link the issued ticket 196 (based on or associated with the received scan data, such as the ticket serial number) to a user account 106 corresponding to the user who caused the ticket to be issued.

[0057]

[0059] The user device 104 is an electronic communication device such as a mobile device, tablet, computer, or web browser. The user device 104 uses one or more processors to execute a remote lottery application 105, which executes a user interface configured to provide output to a user (e.g., a video feed from the application server 108, menus offering options for selecting a ticket issuing machine and a ticket, user interface affordances for accepting ticket issuing commands, winning ticket notifications, etc.). The user interface also accepts user input configured to operate the signature machine 114 and scratch machine 116, as described above.

[0058]

[0060] A user may be physically present at a remote location using the application 105 while playing a lottery ticket provided by the ticket processing system 102. In some implementations, a user may not be at a remote location but may be physically present at the location of the ticket processing system 102 (such as a bingo hall) and may optionally use the application 105 for convenience or due to physical limitations.

[0059]

[0061] The application 105 displays the video feed data (from the camera 112) and receives selections for a desired ticket and / or ticket machine (if the same ticket is available at multiple ticket machines). The application 105 receives input via an input module on the user device 104. The input module may comprise a touch screen, a computer mouse, a stylus, a digital pen, a keyboard, or other input device that captures XY movements (e.g., for signing and / or scratching).

[0060]

[0062] The application 105 receives the win / loss information (including the win amount) from the application server 108. The application 105 may cause the user device 104 to alert the user about the win / loss information using visual, audible, and / or tactile alerts.

[0061]

[0063] The ticket agency 124 is associated with the tickets and / or ticket issuing machines 190 that provide the tickets. The ticket agency verifies the tickets and the winning / losing status of the tickets through the ticket validation server 122. Once the ticket is confirmed (by the ticket validation server 122) as a valid winning ticket, the ticket agency 124 deposits the winning funds into the user account 106 linked to the ticket by the scanned identification number (e.g., the serial number described above). The ticket agency 124 may deposit the funds to the user via the provider bank account 126 and a payment processing module or service 128. The user account 106 may be linked to a bank account or card account 130. In some implementations, the funds may be transferred to a virtual currency account (such as Bitcoin) associated with the user account.

[0062]

[0064] In some implementations, system 100 may include additional components or only a subset of the components described above. For example, some implementations of system 100 may not include ticket agency 124, ticket validation server 122, provider bank account 126, payment processing module 128, and / or user bank / card account 130. Instead, system 100 may be configured to communicate with one or more of these components.

[0063]

[0065] In some implementations, one or more of the components of system 100 may be combined (i.e., the operations of two or more components may be performed by a single server, device, controller, etc.). For example, the ticket validation server 122 may be combined with the redemption terminal 120, the redemption terminal 120 may be combined with the controller 110, etc.

[0064]

[0066] In some implementations, one or more of the components of the ticket processing system 102 may be implemented as robotic machines. For example, the machines may be controlled by the controller 110 and include a signature machine 114, a scratch machine 116, a scanner 118, a camera 112, a redemption terminal 120, a cutter 132, a sorter 134, and / or a ticket issuing machine 190.

[0065]

[0067] The ticket processing system 102 (specifically, the controller 110 and the redemption terminal 120) communicates with other components of the system 100 via one or more communication network connections (indicated by arrows in the figure). The communication network connections may be wired or wireless communication connections that are maintained (e.g., dedicated connections, dedicated online connections, and / or hardwired connections) or may be accessible on demand (e.g., supporting the ability of a machine to temporarily connect to a server or the ability of a user device to contact a server). Examples of such network connection technologies may include hardwired, telephone network technologies, cellular technologies (e.g., GSM, CDMA, etc.), Wi-Fi technologies, wide area networks (WANs), local area networks (LANs), or any known or yet to be discovered wired or wireless communication technologies over the Internet. In other words, each communication network connection may be implemented over a communication network using a wired or wireless communication protocol (e.g., any of WiFi, Bluetooth, ZigBee, Z-Wave, 6LoWPAN, Thread, 4G, 5G, etc.).

[0066]

[0068] Communications (indicated by arrows in the figure) within the ticket processing system 102 may occur using the communications technologies described above. Additionally or alternatively, such communications may occur using short-range communications technologies such as Bluetooth (Bluetooth 4.0, Bluetooth Smart, Bluetooth Low Energy (BLE), etc.), Near Field Communication (NFC), Ultra Wide Band (UWB), Radio Frequency Identification (RFID), Infrared Radio, Inductive Radio, or any wired or wireless technology that can be used for communication over known or undiscovered short distances (approximately 100 feet or less).

[0067]

[0069] 3 is a flow diagram of a method of operating the ticket processing system of the lottery system 100 of FIGS. 1 and 2 according to some implementations. The method 300 is optionally governed by instructions stored in a computer memory or non-transitory computer-readable storage medium of the processing system 102, the application server 108, the redemption terminal 120, and / or the validation server 122. Such instructions may be executed by one or more processors of the aforementioned devices. The computer-readable storage medium may include magnetic or optical disk storage devices, solid-state storage devices such as flash memory, or other non-volatile memory devices. The instructions stored in each computer-readable storage medium may include one or more of source code, assembly language code, object code, or other instruction formats interpreted by one or more processors. Some operations of the method 300 may be combined and / or the order of some operations may be changed.

[0068]

[0070] Method 300 may begin at operation 302 or operation 304. At operation 302, controller 110 acquires a first video stream (indicating a live feed of the ticket machine) from one or more video cameras 112 proximate to ticket machine 190 and transmits the first video stream to application server 108 for delivery to user device 104.

[0069]

[0071] The user uses a user interface of the application 105 executing on the user device 104 to select a desired ticket and / or ticket machine 190, optionally based on the first video stream (e.g., the user sees available tickets and / or ticket machines in the video feed and makes a selection in the user interface).

[0070]

[0072] Upon receiving the user's selection, the user device sends a ticket issuing command to the controller 110 via the application server 108, which is received in operation 304. Upon receiving the ticket issuing command, the controller 110 causes the selected ticket vending machine to issue the selected ticket. The issued ticket is a physical lottery ticket that has a scratch area, a signature area, and / or an identification code (e.g., a lot number or serial number) that must be visible or revealed by the scratch machine when issued.

[0071]

[0073] When the ticket is dispensed, the first camera 112 (e.g., the lower camera) images the ticket and the scanner 118 scans the ticket for an identification code (operation 306). The controller 110 transmits the scanned identification number (referred to as first ticket data) to the application server 108. In operation 308, the application server 108 maps (i.e., assigns, associates) the ticket's identification code to the user account 106 associated with the user device 104.

[0072]

[0074] Before, during, or after operation 306, the controller 110 receives user-provided signature data (operation 310) and / or user-provided scratch data (obtained by the user device 104) from the application server 108. The signature data causes the robotic signature device to sign a signature area of ​​the ticket (operation 312) and / or the scratch data causes the robotic scratch device to scratch a scratch area of ​​the ticket (operation 316).

[0073]

[0075] In other words, the user can choose to sign the ticket using the user interface of the application 105 (operation 310). The user enters the signature using a touch screen, computer mouse, stylus, digital pen, keyboard, or other input method that captures the XY signature. The signature file is sent from the mobile application to the application server, to the controller, and to the robotic arm, which physically signs the ticket (operation 312). The user can see the signature depicted on the ticket in real time. In some implementations, the signature feedback is replicated on the user interface.

[0074]

[0076] Before, during, or after the signing operation, the user may virtually scratch the ticket using a touch screen, mouse, stylus, digital pen, or other user input (operation 314). In some implementations, the ticket scratching process may be fully automated and require no user interaction (other than starting and / or stopping). In some implementations, the scratching device may use random XY coordinates. A robotic arm physically scratches the ticket as the user performs a scratch gesture on the user interface and / or watches a live video feed. In some implementations, a simulated ticket exists on the user device 104 (with or without a video feed) and real-time feedback is provided to digitally simulate the ticket scratching process on the user device 104.

[0075]

[0077] Once the scratch operation is complete, the scanner 118 scans the revealed information (referred to as second ticket data) in the scratch area (operation 318). The information may include a unique code, a game play number, or any other data that was initially hidden under an opaque substance prior to the scratch operation. In some implementations, the information does not need to be revealed. In some implementations, the information is in a fixed location and / or no scratch operation is required. The scanner 118 transmits the second ticket data (the revealed information) to the ticket redemption terminal 120 for processing by the ticket validation server 122 (or the second ticket data is sent directly to the ticket validation server 122).

[0076]

[0078] Upon receiving the second ticket data, the ticket agency determines (via validation server 122) ticket status data corresponding to a winning or losing status of the ticket based on the second ticket data in operation 320. If the ticket is a winning ticket (ticket status data corresponding to a winning status), validation server 122 sends a notification to application server 108 (for delivery to the user device) in operation 322 that includes an amount associated with the winning status of the ticket.

[0077]

[0079] The application server 108 updates the user account based on the win / loss status and notifies the user device accordingly (operation 324). Funds corresponding to the amount associated with the win status may be automatically transferred (e.g., by the ticket agency using payment processing service 128) to a bank account linked to the user account associated with the user device.

[0078]

[0080] In some implementations, after the ticket is processed (upon completion of operations 312, 316, and 318), the controller 110 may cause the cutting device 132 to cut or separate the processed ticket from the stream of tickets. The controller 110 may further cause the sorting device 134 to extract or distinguish winning tickets from losing tickets, thereby storing the processed tickets according to winning or losing status. In some embodiments, if there have been system errors, incomplete scans, or incomplete scratches, a pile of error tickets may exist.

[0079]

[0081] In some implementations, each ticket processing transaction (e.g., actions 302-318 in the processing system 102) may be video recorded and stored (e.g., in the controller 110 and / or application server 108) for later recall and authentication verification, thereby satisfying audit and / or control requirements.

[0080]

[0082] The following clauses describe alternative and / or additional combinations of implementations of the above features.

[0081]

[0083] Clause 1: A system including one or more controllers configured to acquire a first video stream from a first video camera proximate a ticket issuing machine, transmit the first video stream to an application server for delivery to a user device, receive a ticket issuing command for the ticket issuing machine from the application server, cause the ticket issuing machine to issue a ticket having a scratch area based on the ticket issuing command, receive user-provided scratch data from the application server, and cause a robotic scratch device to scratch the scratch area of ​​the ticket or remove opaque material from the scratch area in accordance with the user-provided scratch data.

[0082]

[0084] Clause 2: The system of clause 1, wherein the one or more controllers are further configured to receive user-provided signature data from the application server and cause the robotic signature device to sign a signature area of ​​the ticket in accordance with the user-provided signature data.

[0083]

[0085] Clause 3: A system described in any of clauses 1 or 2, wherein the one or more controllers are further configured to obtain an identification code of the ticket from a scanning device proximate to the ticket issuing machine and transmit the identification code to a ticket validation server.

[0084]

[0086] Clause 4: The system of any of clauses 1 to 3, further comprising a ticket validation server configured to determine ticket status data corresponding to a winning or losing status of the ticket based on the identification code of the ticket, send a notification to the user device including an amount associated with the winning status of the ticket according to the ticket status data corresponding to the winning status of the ticket, and cause funds corresponding to the amount associated with the winning status to be transferred to a bank account linked to a user account associated with the user device.

[0085]

[0087] Clause 5: A system described in any of clauses 1 to 4, wherein the one or more controllers are further configured to cause a cutting device to separate tickets from the stream of tickets and to cause a sorting device to store the tickets according to their winning or losing status.

[0086]

[0088] Clause 6: The system of any of clauses 1 to 5, further comprising an application server configured to obtain an identification code of the ticket from the scanning device and associate the identification code with a user account associated with the user device.

[0087]

[0089] Clause 7: A system described in any of clauses 1 to 6, wherein the first video stream includes image data of a ticket issuing machine and / or image data of an issued ticket.

[0088]

[0090] Clause 8: A system described in any of clauses 1 to 7, wherein the issued ticket comprises a physical ticket body having two surfaces, the scratch area comprises an opaque substance adhered to one of the two surfaces, and the signature area comprises a blank portion of one of the two surfaces.

[0089]

[0091] Clause 9: A system described in any of clauses 1 to 8, wherein the user-provided signature data includes XY data obtained from a user interface of a user device, the XY data corresponding to a two-dimensional user-provided gesture corresponding to signature input on the user interface.

[0090]

[0092] Clause 10: A system described in any of clauses 1 to 9, wherein the user-provided scratch data includes XY data obtained from a user interface of a user device, the XY data corresponding to a two-dimensional user-provided gesture corresponding to scratch input on the user interface.

[0091]

[0093] Clause 11: A system described in any of clauses 1 to 10, wherein the one or more controllers are further configured to acquire a second video stream including image data of the signature area of ​​the ticket from a second video camera proximate to the ticket issuing machine while the robotic signature device is signing the signature area.

[0092]

[0094] Clause 12: A system described in any of clauses 1 to 11, wherein the one or more controllers are further configured to acquire a second video stream including image data of the scratch area of ​​the ticket from a second video camera proximate to the ticket issuing machine while the robotic scratch device is scratching the scratch area.

[0093]

[0095] Clause 13: A method comprising the operations described in any of clauses 1 to 12.

[0094]

[0096] Clause 14: A non-transitory computer-readable storage medium storing one or more programs configured to be executed by a computer system, the one or more programs including instructions for performing the operations described in any of clauses 1 to 12.

[0095]

[0097] The following clauses describe alternative and / or additional combinations of implementations of the above features.

[0096]

[0098] Clause 1: A system including one or more controllers configured to acquire a first video stream from a first video camera proximate a ticket issuing machine, transmit the first video stream to an application server for delivery to a user device, receive a ticket issuing command for the ticket issuing machine from the application server, cause the ticket issuing machine to issue a ticket having a scratch area based on the ticket issuing command, receive a user-provided scratch command from the application server, and cause a robotic scratch device to scratch the scratch area of ​​the ticket or remove opaque material from the scratch area in accordance with the user-provided scratch command.

[0097]

[0099] Clause 2: The system of clause 1, wherein the one or more controllers are further configured to receive user-provided signature data from the application server and cause the robotic signature device to sign a signature area of ​​the ticket in accordance with the user-provided signature data.

[0098]

[0100] Clause 3: A system described in any of clauses 1 or 2, wherein the one or more controllers are further configured to obtain an identification code of the ticket from a scanning device proximate to the ticket issuing machine and transmit the identification code to a ticket validation server.

[0099]

[0101] Clause 4: The system of any of clauses 1 to 3, further comprising a ticket validation server configured to determine ticket status data corresponding to a winning or losing status of the ticket based on the identification code of the ticket, send a notification to the user device including an amount associated with the winning status of the ticket according to the ticket status data corresponding to the winning status of the ticket, and cause funds corresponding to the amount associated with the winning status to be transferred to a bank account linked to a user account associated with the user device.

[0100]

[0102] Clause 5: A system described in any of clauses 1 to 4, wherein the one or more controllers are further configured to cause a cutting device to separate tickets from the stream of tickets and to cause a sorting device to store the tickets according to their winning or losing status.

[0101]

[0103] Clause 6: The system of any of clauses 1 to 5, further comprising an application server configured to obtain an identification code of the ticket from the scanning device and associate the identification code with a user account associated with the user device.

[0102]

[0104] Clause 7: A system described in any of clauses 1 to 6, wherein the first video stream includes image data of a ticket issuing machine and / or image data of an issued ticket.

[0103]

[0105] Clause 8: A system described in any of clauses 1 to 7, wherein the issued ticket comprises a physical ticket body having two surfaces, the scratch area comprises an opaque substance adhered to one of the two surfaces, and the signature area comprises a blank portion of one of the two surfaces.

[0104]

[0106] Clause 9: A system described in any of clauses 1 to 8, wherein the user-provided signature data includes XY data obtained from a user interface of a user device, the XY data corresponding to a two-dimensional user-provided gesture corresponding to signature input on the user interface.

[0105]

[0107] Clause 10: A system described in any of clauses 1 to 9, wherein a user-provided scratch command causes the robotic scratch device to initiate scratching the scratch area of ​​the ticket or removing opaque material from the scratch area, and the robotic scratch device is configured to scratch the scratch area of ​​the ticket or remove opaque material from the scratch area using a preconfigured or random scratch pattern.

[0106]

[0108] Clause 11: A system described in any of clauses 1 to 10, wherein the one or more controllers are further configured to acquire a second video stream including image data of the signature area of ​​the ticket from a second video camera proximate to the ticket issuing machine while the robotic signature device is signing the signature area.

[0107]

[0109] Clause 12: A system described in any of clauses 1 to 11, wherein the one or more controllers are further configured to acquire a second video stream including image data of the scratch area of ​​the ticket from a second video camera proximate to the ticket issuing machine while the robotic scratch device is scratching the scratch area.

[0108]

[0110] Clause 13: A method comprising the operations described in any of clauses 1 to 12.

[0109]

[0111] Clause 14: A non-transitory computer-readable storage medium storing one or more programs configured to be executed by a computer system, the one or more programs including instructions for performing the operations described in any of clauses 1 to 12.

[0110]

[0112] The following clauses describe alternative and / or additional combinations of implementations of the above features.

[0111]

[0113] Clause 1: A system including one or more controllers configured to acquire first image data from a camera associated with a ticket machine, transmit the first image data to an application server, receive a ticket issuance command for the ticket machine from the application server, cause the ticket machine to issue a ticket having a scratch area based on the ticket issuance command, receive a user-provided scratch command from the application server, and cause a robotic scratch device to scratch the scratch area of ​​the ticket or remove opaque material from the scratch area in accordance with the user-provided scratch command.

[0112]

[0114] Clause 2: The system of clause 1, wherein the one or more controllers are further configured to receive user-provided signature data from the application server and cause the robotic signature device to sign a signature area of ​​the ticket in accordance with the user-provided signature data.

[0113]

[0115] Clause 3: A system described in any of clauses 1 or 2, wherein the one or more controllers are further configured to obtain an identification code of the ticket from a scanning device associated with the ticket machine and transmit the identification code to a ticket validation server.

[0114]

[0116] Clause 4: The system of any of clauses 1 to 3, further comprising a ticket validation server configured to determine ticket status data corresponding to a winning or losing status of the ticket based on the identification code of the ticket, send a notification to the user device including an amount associated with the winning status of the ticket according to the ticket status data corresponding to the winning status of the ticket, and cause funds corresponding to the amount associated with the winning status to be transferred to a bank account linked to a user account associated with the user device.

[0115]

[0117] Clause 5: A system described in any of clauses 1 to 4, wherein the one or more controllers are further configured to cause a cutting device to separate tickets from the stream of tickets and to cause a sorting device to store the tickets according to their winning or losing status.

[0116]

[0118] Clause 6: The system of any of clauses 1 to 5, further comprising an application server configured to obtain an identification code of the ticket from the scanning device and associate the identification code with a user account associated with the user device.

[0117]

[0119] Clause 7: A system described in any of clauses 1 to 6, wherein the first image data includes an image of a ticket machine and / or an image of a ticket.

[0118]

[0120] Clause 8: A system described in any of clauses 1 to 7, wherein the ticket comprises a physical ticket body having two surfaces, the scratch area comprises an opaque substance adhered to one of the two surfaces, and the signature area comprises a blank portion of one of the two surfaces.

[0119]

[0121] Clause 9: A system described in any of clauses 1 to 8, wherein the user-provided signature data includes XY data obtained from a user interface of a user device, the XY data corresponding to a two-dimensional user-provided gesture corresponding to signature input on the user interface.

[0120]

[0122] Clause 10: A system described in any of clauses 1 to 9, wherein a user-provided scratch command causes the robotic scratch device to initiate scratching the scratch area of ​​the ticket or removing opaque material from the scratch area, and the robotic scratch device is configured to scratch the scratch area of ​​the ticket or remove opaque material from the scratch area using a preconfigured or random scratch pattern.

[0121]

[0123] Clause 11: A system described in any of clauses 1 to 10, wherein the one or more controllers are further configured to acquire second image data including an image of the signature area of ​​the ticket from a second camera associated with the ticket machine while the robotic signature device is signing the signature area.

[0122]

[0124] Clause 12: A system described in any of clauses 1 to 11, wherein the one or more controllers are further configured to acquire second image data including an image of the scratch area of ​​the ticket from a second camera associated with the ticket machine while the robotic scratch device is scratching the scratch area.

[0123]

[0125] Clause 13: A method comprising the operations described in any of clauses 1 to 12.

[0124]

[0126] Clause 14: A non-transitory computer-readable storage medium storing one or more programs configured to be executed by a computer system, the one or more programs including instructions for performing the operations described in any of clauses 1 to 12.

[0125]

[0127] The following clauses describe alternative and / or additional combinations of implementations of the above features.

[0126]

[0128] Clause 1: A server system including one or more controllers configured to receive first image data from a camera associated with a ticket machine, transmit the first image data to a user device, receive a ticket issuance command for the ticket machine from the user device, transmit the ticket issuance command to the ticket machine to cause the ticket machine to issue a ticket having a scratch area based on the ticket issuance command, receive a user-provided scratch command from the user device, and transmit the user-provided scratch command to the ticket machine to cause a robotic scratch device to scratch the scratch area of ​​the ticket or remove opaque material from the scratch area in accordance with the user-provided scratch command.

[0127]

[0129] Clause 2: The server system of clause 1, wherein the one or more controllers are further configured to receive user-provided signature data from the user device, transmit the user-provided signature data to the ticket machine, and cause the robotic signature device to sign the signature area of ​​the ticket in accordance with the user-provided signature data.

[0128]

[0130] Clause 3: A server system as described in any of clauses 1 or 2, wherein the one or more controllers are further configured to receive an identification code of the ticket from a scanning device associated with the ticket machine and transmit the identification code to a ticket validation server.

[0129]

[0131] Clause 4: The server system of any of clauses 1 to 3, further comprising a ticket validation server configured to receive a ticket identification code from a scanning device associated with the ticket machine, determine ticket status data corresponding to a winning or losing status of the ticket based on the ticket identification code, send a notification to the user device including an amount associated with the winning status of the ticket according to the ticket status data corresponding to the winning status of the ticket, and cause funds corresponding to the amount associated with the winning status to be transferred to a bank account linked to a user account associated with the user device.

[0130]

[0132] Clause 5: A server system as described in any of clauses 1 to 4, wherein the one or more controllers are further configured to send a command to the ticket machine to cause the classification device to store the ticket according to ticket status data corresponding to the winning status of the ticket.

[0131]

[0133] Clause 6: A server system as described in any of clauses 1 to 5, wherein the one or more controllers are further configured to obtain an identification code of the ticket from the scanning device and associate the identification code with a user account associated with the user device.

[0132]

[0134] Clause 7: A server system according to any one of clauses 1 to 6, wherein the first image data includes an image of a ticket machine and / or an image of a ticket.

[0133]

[0135] Clause 8: A server system described in any of clauses 1 to 7, wherein the ticket comprises a physical ticket body having two surfaces, the scratch area comprises an opaque substance adhered to one of the two surfaces, and the signature area comprises a blank portion of one of the two surfaces.

[0134]

[0136] Clause 9: A server system described in any of clauses 1 to 8, wherein the user-provided signature data includes XY data obtained from a user interface of a user device, the XY data corresponding to a two-dimensional user-provided gesture corresponding to signature input on the user interface.

[0135]

[0137] Clause 10: A server system described in any of clauses 1 to 9, wherein a user-provided scratch command causes the robotic scratch device to scratch a scratch area of ​​the ticket using a pre-configured or random scratch pattern or remove opaque material from the scratch area.

[0136]

[0138] Clause 11: A server system as described in any of clauses 1 to 10, wherein the one or more controllers are further configured to receive second image data including an image of the signature area of ​​the ticket from a second camera associated with the ticket machine while the robotic signature device is signing the signature area, and to transmit the second image data to the user device.

[0137]

[0139] Clause 12: A server system described in any of clauses 1 to 11, wherein the one or more controllers are further configured to receive second image data including an image of the scratch area of ​​the ticket from a second camera associated with the ticket machine while the robotic scratch device is scratching the scratch area, and to transmit the second image data to the user device.

[0138]

[0140] Clause 13: A method comprising the operations described in any of clauses 1 to 12.

[0139]

[0141] Clause 14: A non-transitory computer-readable storage medium storing one or more programs configured to be executed by a computer system, the one or more programs including instructions for performing the operations described in any of clauses 1 to 12.

[0140]

[0142] The following clauses describe alternative and / or additional combinations of implementations of the above features.

[0141]

[0143] Clause 1: A user device comprising one or more controllers configured to receive first image data acquired from a camera associated with a ticket machine from an application server, display the first image data on a display of the user device, obtain a ticket issuance command for the ticket machine at a user interface of the user device, send the ticket issuance command to the ticket machine via the application server to cause the ticket machine to issue a ticket having a scratch area based on the ticket issuance command, obtain a user-provided scratch command at a user interface of the user device, and send the user-provided scratch command to the ticket machine via the application server to cause a robotic scratch device to scratch the scratch area of ​​the ticket or remove opaque material from the scratch area in accordance with the user-provided scratch command.

[0142]

[0144] Clause 2: A user device as described in clause 1, wherein the one or more controllers are further configured to obtain user-provided signature data at a user interface of the user device, transmit the user-provided signature data to the ticket machine via the application server, and cause the robotic signature device to sign the signature area of ​​the ticket in accordance with the user-provided signature data.

[0143]

[0145] Clause 3: A user device as described in any of clauses 1 or 2, wherein the one or more controllers are further configured to receive ticket status data for the ticket from the ticket validation server corresponding to a winning or losing status of the ticket based on an identification code of the ticket scanned by a scanning device associated with the ticket machine.

[0144]

[0146] Clause 4: A user device described in any of clauses 1 to 3, wherein the one or more controllers are further configured to receive a notification from the ticket validation server including an amount associated with the winning status of the ticket in accordance with ticket status data of the ticket corresponding to the winning status of the ticket.

[0145]

[0147] Clause 5: A user device described in any of clauses 1 to 4, wherein the one or more controllers are further configured to obtain an identification code of the ticket from the scanning device and associate the identification code with a user account associated with the user device.

[0146]

[0148] Clause 6: A user device according to any of clauses 1 to 5, wherein the first image data includes an image of a ticket machine and / or an image of a ticket.

[0147]

[0149] Clause 7: A user device described in any of clauses 1 to 6, wherein the ticket comprises a physical ticket body having two surfaces, the scratch area comprises an opaque substance adhered to one of the two surfaces, and the signature area comprises a blank portion of one of the two surfaces.

[0148]

[0150] Clause 8: A user device described in any of clauses 1 to 7, wherein the user-provided signature data includes XY data obtained from a user interface of the user device, the XY data corresponding to a two-dimensional user-provided gesture corresponding to signature input on the user interface.

[0149]

[0151] Clause 9: A user device described in any of clauses 1 to 8, wherein a user-provided scratch command causes the robotic scratch device to scratch a scratch area of ​​the ticket using a pre-configured or random scratch pattern or remove opaque material from the scratch area.

[0150]

[0152] Clause 10: A user device described in any of clauses 1 to 9, wherein the user-provided scratch command includes XY data obtained from a user interface of the user device, the XY data corresponding to a two-dimensional user-provided gesture corresponding to a scratch input on the user interface.

[0151]

[0153] Clause 11: A user device described in any of clauses 1 to 10, wherein the one or more controllers are further configured to receive second image data from the application server including an image of the signature area of ​​the ticket acquired from a second camera associated with the ticket machine while the robotic signature device is signing the signature area.

[0152]

[0154] Clause 12: A user device described in any of clauses 1 to 11, wherein the one or more controllers are further configured to receive second image data from the application server including an image of the scratch area of ​​the ticket obtained from a second camera associated with the ticket machine while the robotic scratch device is scratching the scratch area.

[0153]

[0155] Clause 13: A method comprising the operations described in any of clauses 1 to 12.

[0154]

[0156] Clause 14: A non-transitory computer-readable storage medium storing one or more programs configured to be executed by a computer system, the one or more programs including instructions for performing the operations described in any of clauses 1 to 12.

[0155]

[0157] The following clauses describe alternative and / or additional combinations of implementations of the above features.

[0156]

[0158] Clause 1: A system including one or more controllers configured to acquire first image data from a camera associated with a ticket machine, send the first image data to an application server, receive a first command for the ticket machine from the application server, cause the ticket machine to provide a ticket having a scratch area based on the first command, receive a user-provided scratch command from the application server, and cause a robotic scratch device to scratch the scratch area of ​​the ticket or remove opaque material from the scratch area in accordance with the user-provided scratch command.

[0157]

[0159] Clause 2: The system of clause 1, wherein the one or more controllers are further configured to receive user-provided signature data from the application server and cause the robotic signature device to sign a signature area of ​​the ticket in accordance with the user-provided signature data.

[0158]

[0160] Clause 3: A system described in any of clauses 1 or 2, wherein the one or more controllers are further configured to obtain an identification code of the ticket from a scanning device associated with the ticket machine and transmit the identification code to a ticket validation server.

[0159]

[0161] Clause 4: The system of any of clauses 1 to 3, further comprising a ticket validation server configured to determine ticket status data corresponding to a winning or losing status of the ticket based on the identification code of the ticket, send a notification to the user device including an amount associated with the winning status of the ticket according to the ticket status data corresponding to the winning status of the ticket, and cause funds corresponding to the amount associated with the winning status to be transferred to a bank account linked to a user account associated with the user device.

[0160]

[0162] Clause 5: A system described in any of clauses 1 to 4, wherein the one or more controllers are further configured to cause a cutting device to separate tickets from the stream of tickets and to cause a sorting device to store the tickets according to their winning or losing status.

[0161]

[0163] Clause 6: The system of any of clauses 1 to 5, further comprising an application server configured to obtain an identification code of the ticket from the scanning device and associate the identification code with a user account associated with the user device.

[0162]

[0164] Clause 7: A system described in any of clauses 1 to 6, wherein the first image data includes an image of a ticket machine and / or an image of a ticket.

[0163]

[0165] Clause 8: A system described in any of clauses 1 to 7, wherein the ticket comprises a physical ticket body having two surfaces, the scratch area comprises an opaque substance adhered to one of the two surfaces, and the signature area comprises a blank portion of one of the two surfaces.

[0164]

[0166] Clause 9: A system described in any of clauses 1 to 8, wherein the user-provided signature data includes XY data obtained from a user interface of a user device, the XY data corresponding to a two-dimensional user-provided gesture corresponding to signature input on the user interface.

[0165]

[0167] Clause 10: A system described in any of clauses 1 to 9, wherein a user-provided scratch command causes the robotic scratch device to initiate scratching the scratch area of ​​the ticket or removing opaque material from the scratch area, and the robotic scratch device is configured to scratch the scratch area of ​​the ticket or remove opaque material from the scratch area using a preconfigured or random scratch pattern.

[0166]

[0168] Clause 11: A system described in any of clauses 1 to 10, wherein the one or more controllers are further configured to acquire second image data including an image of the signature area of ​​the ticket from a second camera associated with the ticket machine while the robotic signature device is signing the signature area.

[0167]

[0169] Clause 12: A system described in any of clauses 1 to 11, wherein the one or more controllers are further configured to acquire second image data including an image of the scratch area of ​​the ticket from a second camera associated with the ticket machine while the robotic scratch device is scratching the scratch area.

[0168]

[0170] Clause 13: A method comprising the operations described in any of clauses 1 to 12.

[0169]

[0171] Clause 14: A non-transitory computer-readable storage medium storing one or more programs configured to be executed by a computer system, the one or more programs including instructions for performing the operations described in any of clauses 1 to 12.

[0170]

[0172] It will be appreciated by those skilled in the art that changes may be made to the exemplary embodiments shown and described above without departing from the broad inventive concept thereof. It is understood, therefore, that the invention is not limited to the exemplary embodiments shown and described, but is intended to cover such modifications within the spirit and scope of the invention as defined by the appended claims.

[0171]

[0173] For example, certain features of the exemplary embodiments may or may not be part of the claimed invention, at least some of the features described herein may be performed by different components other than the components specifically mentioned, and features of the disclosed embodiments may be combined.

[0172]

[0174] The terms "about" and "approximately" as used herein may refer to +10% or -10% of the referenced value. For example, "about 9" is understood to include 8.2 and 9.9.

[0173]

[0175] It is to be understood that at least some of the figures and descriptions of the invention have been simplified to focus on elements relevant for a clear understanding of the invention, and for the sake of clarity have excluded other elements that one of ordinary skill in the art would recognize as forming part of the invention, however, because such elements are well known in the art and do not necessarily facilitate a further understanding of the invention, descriptions of such elements are not provided herein.

[0174]

[0176] Although terms such as "first," "second," and the like are sometimes used herein to describe various elements, it will be understood that these elements are not to be limited by these terms, but rather are used only to distinguish one element from another.

[0175]

[0177] For example, a first element could be referred to as a second element, and similarly a second element could be referred to as the first element, without changing the meaning of the description, so long as all occurrences of the first element are consistently renamed and all occurrences of the second element are consistently renamed. A first element and a second element are both elements, but they are not the same element.

[0176]

[0178] The term "if," as used herein, may be optionally interpreted to mean "upon" or "in response to a determination that" or "in response to detecting" or "following a determination that," depending on the context. Similarly, the phrase "if it is determined that" or "if [described condition or event] is detected" is optionally interpreted to mean "upon determining that" or "in response to a determination that" or "upon detecting [described condition or event]" or "in response to detecting [described condition or event]" or "following a determination that [described condition or event] is detected," depending on the context.

[0177]

[0179] The terminology used herein is for the purpose of describing particular implementations only and is not intended to limit the scope of the claims.

[0178]

[0180] As used in the description of implementations and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.

[0179]

[0181] It will also be understood that the term "and / or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.

[0180]

[0182] Furthermore, it will be understood that the terms "comprises" and / or "comprising" as used herein indicate the presence of stated features, integers, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integers, operations, elements, components, and / or groups thereof.

[0181]

[0183] The term "if", as used herein, may be interpreted to mean "when" the aforementioned condition is true, or "when" the aforementioned condition is true, or "in response to a determination that" the aforementioned condition is true, or "following a determination that" the aforementioned condition is true, or "in response to detecting that" the aforementioned condition is true, depending on the context.

[0182]

[0184] Similarly, the phrases "if (the aforementioned condition is determined to be true)" or "if (the aforementioned condition is true)" or "when (the aforementioned condition is true)" may be interpreted to mean "upon determining that" the aforementioned condition is true, or "in response to determining that" the aforementioned condition is true, or "following a determination that" the aforementioned condition is true, or "upon detecting that" the aforementioned condition is true, or "in response to detecting that" the aforementioned condition is true, depending on the context.

[0183]

[0185] Furthermore, to the extent that the method does not rely on a particular order of steps described herein, a particular order of steps should not be construed as limiting the scope of the claims. Claims directed to the method of the present invention should not be limited to performing its steps in the order described, and one of ordinary skill in the art can readily appreciate that the steps may be varied and still be within the spirit and scope of the invention.

Claims

1. Receive a ticket issuing command for a ticket issuing machine; causing the ticket issuing machine to issue a ticket having a scratch area based on the ticket issuing command; Receives user-supplied scratch data from the application server A controller configured as follows: a robotic scratch mechanism configured to scratch the scratch area of ​​the ticket or remove opaque material from the scratch area in accordance with the user-provided scratch data; a video camera proximate to the ticket issuing machine and configured to capture a video stream including image data of the scratch area of ​​the ticket while the robotic scratch mechanism is scratching the scratch area; A robotic ticket scratch processing system, including:

2. the controller is further configured to receive user-provided signature data from the application server; the robotic ticket scratch processing system further comprising a robotic signature mechanism configured to sign a signature area of ​​the ticket in accordance with the user-provided signature data; The system of claim 1 .

3. a scanning device proximate the ticket issuing machine, Scanning the identification code of the ticket; Sending the identification code to a ticket validation server A scanning device configured to The system of claim 1 or 2, further comprising:

4. a mechanical cutting device configured to separate said ticket from a stream of tickets; a mechanical sorting device configured to sort the tickets according to a winning or losing status of the tickets; The system of claim 1 or 2, further comprising:

5. 3. The system of claim 2, wherein the issued ticket comprises a physical ticket body having two surfaces, the scratch area comprises an opaque substance adhered to one of the two surfaces, and the signature area comprises a blank portion of one of the two surfaces.

6. 3. The system of claim 1, wherein the user-provided signature data includes XY data obtained from a user interface of a user device, the XY data corresponding to a two-dimensional user-provided gesture corresponding to a signature input at the user interface.

7. 3. The system of claim 1, wherein the user-provided scratch data comprises XY data obtained from a user interface of a user device, the XY data corresponding to a two-dimensional user-provided gesture corresponding to a scratch input on the user interface.

8. The system of claim 2 , wherein the video stream further comprises image data of the signature area of ​​the ticket while the robotic signature mechanism is signing the signature area.

9. 3. A method comprising the acts of any of claims 1 or 2.

10. 3. A non-transitory computer-readable storage medium storing one or more programs configured to be executed by a computer system, the one or more programs including instructions for performing the operations recited in claim 1 or 2.

Images