System and method for robotic ticket scratching via live remote mobile interface

Abstract

To provide a system and a method that use robotic apparatuses that enable virtual play of lottery games.SOLUTION: A controller is configured to obtain a first video stream from a first video camera proximate to a ticket issuing machine, transmit the first video stream to an application server for distribution to a user device, receive a ticket issuance 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 issuance command, receive user-provided scratch data from the application server, and cause a robotic scratch device to scratch the scratch area in accordance with the scratch data.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001]

[0001] This application is a continuation of 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 Feb. 7, 2022, and claims priority to these applications. This application also claims priority to and is a continuation of U.S. Patent Application No. 17 / 650,215, filed Feb. 7, 2022; U.S. Patent Application No. 17 / 655,996, filed Mar. 22, 2022; U.S. Patent Application No. 17 / 655,998, filed Mar. 22, 2022; and U.S. Patent Application No. 17 / 655,999, filed Mar. 22, 2022. Each of these applications is a continuation of U.S. Patent Application No. 17 / 478,907, filed Sep. 18, 2021, which was issued as U.S. Patent No. 11,278,789 on Mar. 22, 2022, claiming priority to U.S. Provisional Patent Application No. 63 / 203,666, filed Jul. 27, 2021. This application also claims priority to and is a continuation of U.S. Patent Application No. 17 / 478,907, filed Sep. 18, 2021, and U.S. Patent Application No. 17 / 448,046, filed Sep. 18, 2021, claiming priority to U.S. Provisional Patent Application No. 63 / 203,666, filed Jul. 27, 2021. This application also claims priority to U.S. Provisional Patent Application No. 63 / 206,666, filed Jul. 27, 2021. Each of the foregoing applications is hereby incorporated by reference in its entirety.

[0002]

[0002] This application relates to the field of network-connected robotic devices configured to interact with lottery ticket vending machines under administrative control.

Background Art

[0003]

[0003] The sale of lottery tickets (also referred to as scratch tickets or scratchers) is typically regulated by a state or other administrative agency, and it is required to sell tickets at a physical location (e.g., a sales counter) within its jurisdiction. Therefore, a person who wishes to participate in a favorite lottery game but is unable to be present at one of those physical locations (e.g., due to vacation, physical disability, or the lack of a convenience store nearby) may have their purchase of the desired lottery ticket blocked or may hesitate to make the purchase. Due to the nature of lottery tickets, many players prefer to purchase the same ticket and play with the same numbers for each lottery cycle, and thus may be disappointed if they miss a particular lottery cycle.

[0004]

[0004] In addition, lottery scratch tickets typically require a physical action as part of the 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 winner and, if so, what the prize for that ticket is. Therefore, a person who is in a situation where it is difficult to physically play (e.g., due to conditions that make it difficult to scratch the ticket) may hesitate to play.

[0005]

[0005] Finally, scratch lottery tickets may be distributed among a group of players (e.g., family members, co-workers, etc.) to share the cost of purchasing multiple tickets (a "lottery pool" or "office pool") and thereby increase the odds of winning. In such cases, typically one person collects the money, purchases the tickets, plays the tickets, and reports the results to the others. Therefore, other people in the group often cannot share the game play experience and are less likely to continue contributing to future group ticket purchases.

Summary of the Invention

[0006]

[0006] The present disclosure describes a system and method for using a robotic device that enables virtual play of a lottery game while complying with administrative regulations. Players who are not physically present at a sales location (e.g., located remotely) or who are physically present at a sales location but cannot physically play a ticket can participate in a desired lottery game. With this system and method, such users can provide an equivalent level of engagement in each of the scenarios described above and participate in the lottery in a manner that complies with applicable state, local, federal, municipal, and / or overseas game play rules (e.g., regarding location, signature, auditing, etc.).

[0007]

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

[0008]

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

[0009]

[0009] In some implementations, there is a live video feed of the ticket issuing machine. The user selects a desired ticket (or the ticket issuing machine if the same ticket is available at multiple ticket issuing machines) using the user interface. A ticket is dispensed from the ticket issuing machine.

[0010]

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

[0011]

[0011] In some implementations, the user can choose to sign the ticket using a mobile interface. The user inputs their signature using a touch screen, computer mouse, stylus, digital pen, keyboard, or other input method that captures an X-Y 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, the controller, and then the robotic arm, and the robotic arm physically signs the ticket. The user can view the signature being drawn on the ticket in real time. In some implementations, the signature feedback is replicated on the user interface.

[0013]

[0013] In some implementations, the user uses a touch screen, mouse, stylus, digital pen, or other user input to virtually scratch the ticket from a remote location. In some implementations, the scratching of the ticket is fully automated and may not require user interaction (other than start and / or stop). In some implementations, the system can use random X-Y coordinates.

[0014]

[0014] In some implementations, when the user is scratching and viewing the live video feed, the robotic arm physically scratches the ticket, rubs the ticket, or remotely causes the information on the ticket to appear by some other means. In some embodiments, there is a ticket simulated on the mobile device (regardless of the presence or absence of the video feed), and real-time feedback is provided to digitally simulate the scratching of the ticket on the mobile device. In some implementations, two or more people may be viewing the same feed and / or virtual scratching process. In some implementations, there may be guest viewers who have no knowledge of the user and no interest in the ticket.

[0015]

[0015] In some implementations, upon completion of the scratch, a barcode scanner scans the unique code that appears. In some embodiments, the unique code is on the back of the ticket. In some embodiments, there is no need to cause the unique code to appear. 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 the scanner to the ticket redemption terminal and then to the verification server of the ticket agency, and the verification server verifies the ticket. The status of the ticket is returned. If the ticket is a winner, the application server sends information including the amount to the mobile application. The mobile application can then provide visual, audible, and / or tactile warnings to the user. The winning funds are deposited into the user account. The user account can be linked to a bank account or a card account. In some implementations, the funds may be transferred to a virtual currency account (such as Bitcoin).

[0017] Referring again to the robotic machine, in some implementations, there is a ticket cutter that cuts the latest ticket from the ticket stream. In some implementations, there is a ticket sorter that extracts winning tickets or differentiates them from losing tickets. In some implementations, there may also be a stack of error tickets if a system error, incomplete scan, or incomplete scratch occurs.

[0018]

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

Brief Description of the Drawings

[0019]

Figure 1

[0019] FIG. 12 is a system diagram of a network-connected lottery system 100 according to some implementations.

Figure 2

[0020] FIG. 13 is a schematic diagram of the network-connected lottery system 100 of FIG. 1, including a data flow, according to some implementations.

Figure 3

[0021] FIG. 14 is a flowchart of a method for operating the ticket processing system of the lottery system 100 of FIGS. 1 and 2 according to some implementations.

Modes for Carrying Out the Invention

[0020]

[0022] Like reference numerals refer to corresponding parts throughout the multiple views of the drawings.

[0021]

[0023] In the era of mobile devices and connectivity, it is possible to virtually play a lottery game using a robotic device located within a controlled jurisdiction and a live remote mobile interface associated with a player. This document describes examples of such robotic devices, mobile interfaces, and methods of using them.

[0022]

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

[0023]

[0025] As shown in FIGS. 1 and 2, the lottery system 100 includes a ticket processing system 102 physically located within a jurisdiction that controls the lottery managed by the 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, 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, and a plurality of robotic components.

[0025]

[0027] The ticket processing system 102 may be located in a public place (e.g., a retail store or other public place), or a dedicated place 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 a robotic device. In some implementations, the components forming the robotic machine or the robotic device include a controller 110, a signature machine 114, a scratch machine 116, a cutting machine 132, a sorting machine 134, and hardware for receiving, moving, orienting, or otherwise processing tickets issued from a 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 issuing machine 190 includes a plurality of lottery tickets 192 (e.g., equipped with a roll of tickets 192 or individually equipped depending on the ticket form factor). One or more ticket issuing machines 190 may be present within a single processing system 102.

[0028]

[0030] The ticket issuing machine 190 is configured to receive a ticket issuing command from the controller 110 and output the ticket specified by the ticket issuing command (if there are multiple types of tickets within the ticket issuing machine 190), or output a ticket upon 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 within the ticket issuing machine 190). The ticket issuing command may include the quantity of tickets to be issued. In such a scenario, the ticket issuing machine 190 is configured to issue the number of tickets specified by the ticket issuing command one by one to enable other components of the processing system 102 to process each ticket in the manner described below.

[0029]

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

[0030]

[0032] Tickets included in ticket dispenser 190 (e.g., within ticket roll 192 or arranged in any other configuration) may also be referred to as scratch cards, scratch-offs, scratch tickets, scratchers, scratch-its, scratch games, scratch-and-wins, instant games, or instant lottery tickets. The tickets may be made of thin paper-based cardstock or plastic. One or more areas may include hidden information that can appear by scratching an opaque substance (e.g., a silk screen latex panel adhered to the ticket body) or removing an 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, to check whether a prize has been won, it may be necessary to scratch the entire scratchable area (or at least a threshold amount of the scratchable area). The ticket may be printed with whether a prize has been won or to reveal a secret code. In some implementations, the result does not depend on the portion that is scratched. In other implementations, it may be necessary to scratch only some areas and not all areas. This may be the case for a quiz where the area corresponding to the correct answer is scratched, or for some applications where the card wins or loses depending on which areas are scratched. In such cases, scratching too many areas may invalidate the card. After losing, all areas can be scratched to see how and what it was a win for.

[0032]

[0034] The video camera 112 may be disposed at multiple locations within the ticket processing system 102 to provide multiple live angles. For example, the first camera 112 may include the ticket dispenser 190 within its field of view, the second camera 112 may include the top of the issued ticket 196 within its field of view, and the 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 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, the user can remotely control the pan, tilt, and zoom of camera 112. Optionally, two or more users can view the same video feed provided by camera 112 (e.g., view the virtual scratch process described below) during a single ticket presentation session. In some implementations, there may be guest viewers who have no knowledge about the user and no interest in ticket issuance and scratching.

[0034]

[0036] Scanner 118 is disposed closest to the area where the ticketed ticket 196 is provided and is configured to scan the identification information on the issued ticket 196. For example, the identification information of the ticket 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 substance. Scanner 118 is configured to transmit the identification information (either the scanned identification information or the identification information itself) to controller 110.

[0035]

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

[0036]

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

[0037]

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

[0038]

[0040] In the second example, the ticket exchange terminal 120 may send the scanned data associated with the game play of the ticket (e.g., a code that appears from under an opaque substance) to the ticket verification server 122 for verification by the ticket agency 124 (e.g., to verify whether the ticket is a winning ticket or not). In some implementations, the data associated with the game play can be an identification number (e.g., serial number). In other words, a single number can not only identify the ticket (and be associated with the user account by the application server 108), but also function as a basis for verifying whether the ticket is a winning ticket or not. In such a scenario, the ticket may not even need to be played (e.g., scratched), and it may be sufficient to simply scan a single number on the issued ticket 196 to (i) associate the ticket with the user account and (ii) verify the status of the ticket (e.g., win or lose).

[0039]

[0041] The ticket exchange terminal 120 is configured to receive ticket verification information (e.g., win / lose information) from the ticket verification server 122 and send the ticket verification information to the application server 108 for further processing.

[0040]

[0042] The controller 110 includes 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 includes 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 drive, network disk drive, server), internal storage media (e.g., RAM, ROM, EPROM, FLASH-EPROM, or any other memory chip or cartridge), removable storage media (e.g., CD, DVD, flash drive, memory card, floppy disk, flexible disk), firmware, and / or other known or undiscovered storage media. Depending on the purpose, the storage can be temporary and / or non-temporary.

[0041]

[0043] The controller 110 is configured to receive a ticket-issuing command from the application server 108 and transmit the received ticket-issuing command to the ticket issuer 190. The controller 110 is also configured to receive video data from 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 the scratch data to the signature machine 114 and the scratch 116, respectively. The controller 110 is also configured to receive scan data (e.g., the serial number and / or game play data described above) from the scanner 118 and transmit the scan data to the application server 108 for association with the user account 106.

[0042]

[0044] In some embodiments, the controller 110 may be configured to receive the hit / miss information from the exchange terminal 120 and transmit the hit / miss information to the application server 108. Alternatively, the exchange terminal 120 (or the ticket verification server 122) may transmit the hit / miss information to the application server 108 without going through the controller 110.

[0043]

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

[0044]

[0046] The signature machine 114 may be remotely controlled by the user interface of the application 105 of the user device 104. The user may virtually (remotely) control the signature machine 114 to sign the issued ticket 196 by locally signing a user interface element on the application 105 of the user device 104 that is similar to the signature area of the ticket. For example, the user may use a touch screen, a computer mouse, a stylus, a digital pen, a keyboard, or other input methods of the user device 104, thereby causing the application 105 to capture X-Y signature data (the X-axis and Y-axis represent the horizontal and vertical directions of the surface of the ticket). In some embodiments, the X-Y signature data corresponds to a two-dimensional user-provided gesture corresponding to the signature input on the user device. In some embodiments, the user can view the signature depicted on the ticket in real time along with the 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, a scratch tool, or other hard object) according to scratch data received from the user device 104 via the application server 108 and the controller 110 to scratch an opaque substance from the scratch area of the ticket. The scratch machine 116 may also be referred to as a scratch device, a scratch mechanism, a scratch machine, or an automatic scratch machine. For example, the scratch machine 116 can be a robotic arm that physically scratches the ticket.

[0046]

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

[0047]

[0049] In some implementations, in cases such as when the scratch area is on one side of the ticket and the signature area is on the opposite side of the ticket, the scratch machine 116 and the signature machine 114 may be constructed and operated independently. 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 mechanism 116 may be remotely controlled by a user interface of an application 105 of the user device 104. The user may virtually (remotely) control the scratch 116 and locally interact with a user interface element on the application 105 of the user device 104 that is similar to the scratch area of a ticket to scratch (or remove an opaque substance from) the scratch area of the redeemed ticket 196. 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 methods of the user device 104, thereby causing the application 105 to capture scratch data. In some implementations, the scratch data captured by the application 105 is X-Y scratch data (where the X-axis and Y-axis represent the horizontal and vertical directions of the surface of the ticket) corresponding to a two-dimensional user-provided gesture corresponding to the scratch input on the user device. Alternatively, the scratch data captured by the application 105 may include or comprise a command to instruct the scratch mechanism 116 to scratch (or remove an opaque substance from) the scratch area of the redeemed ticket using a scratch pattern that is independent of any user-provided gesture. For example, the user may select an affordance such as "scratch ticket" on the user interface of the application 105 to send a scratch command to the scratch mechanism 116. The scratch mechanism 116 may receive the scratch command and scratch (or remove an opaque substance from) the scratch area of the redeemed ticket using a pre-configured scratch pattern or a random scratch pattern.

[0049]

[0051] In some implementations, the user can view in real time the scratching process on the issued ticket 196, along with the scratch processing feedback replicated (displayed) on the user interface of the application 105. The scratch processing 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 scratching machine 116.

[0050]

[0052] In some implementations, the scratching process of the issued ticket 196 may be fully automated rather than manually interacting with the scratch element of the user interface of the application 105, and requires no user interaction other than starting and / or stopping 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 the issued ticket 196 from the tickets in the stream 194 that have not yet been issued or processed. The ticket cutter 132 receives a cutting command from the controller 110 after the ticket 196 has been processed (e.g., after the ticket has been signed, scratched, scanned).

[0052]

[0054] The ticket sorter 134 (also referred to as a sorting device or sorting mechanism) is a mechanical device that includes sorting elements configured to extract winning tickets or distinguish them from losing tickets. After the ticket 196 has been processed (e.g., after the ticket has been signed, scratched, scanned), the ticket sorter 134 receives a sorting command from the controller 110. The ticket sorter 134 places winning tickets in a stack of winning tickets or in a container 138, and places losing tickets in a stack of losing tickets or in a container 136, making them available for inspection by the system and, in some cases, can serve as physical proof of winning tickets that can be sent (e.g., mailed or otherwise delivered) to the ticket agent 124 and / or the user who purchased and / or played the tickets. In some implementations, if a system error, incomplete scan, or incomplete scratch occurs, the ticket sorter 134 may place tickets corresponding to such errors in a stack of error tickets or in a container (not shown), making them available for system troubleshooting.

[0053]

[0055] The application server 108 includes 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 includes or is communicatively coupled to a memory that stores one or more programs executed by a processing unit of the controller. The memory includes computer-readable media including, but not limited to, connected storage media (e.g., hard disk drive, network disk drive, server), internal storage media (e.g., RAM, ROM, EPROM, FLASH-EPROM, or any other memory chip or cartridge), removable storage media (e.g., CD, DVD, flash drive, memory card, floppy disk, flexible disk), firmware, and / or other known or undiscovered storage media. Depending on the purpose, the storage can be temporary and / or non-temporary.

[0054]

[0056] The application server 108 is configured to receive commands (e.g., selection commands for system 102, selection commands for machine 190, and / or ticket issuance 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 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 a plurality of user devices 104 and 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 exchange terminal 120 or the controller 110 and transmit a notification conveying the win / loss information to the user device 104.

[0056]

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

[0057]

[0059] User device 104 is an electronic communication device such as a mobile device, tablet, computer, or web browser. User device 104 uses one or more processors to execute remote lottery application 105, and remote lottery application 105 executes a user interface configured to provide outputs to the user (such as a video feed from application server 108, a menu providing options for selecting a ticket issuing machine and tickets, user interface affordances for receiving a ticket issuing command, a winning ticket notification, etc.). The user interface also receives user input configured to operate signature machine 114 and scratch machine 116 as described above.

[0058]

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

[0059]

[0061] Application 105 displays video feed data (from camera 112) and receives selection results for a desired ticket and / or ticket dispenser when the same ticket is available at multiple ticket dispensers. Application 105 receives input via the input module of user device 104. The input module may comprise a touch screen, computer mouse, stylus, digital pen, keyboard, or other input device that captures X-Y movement (e.g., for signatures and / or scratches).

[0060]

[0062] Application 105 receives win / lose information (including winning amounts) from application server 108. Application 105 may alert the user regarding win / lose information using visual, audible, and / or tactile warnings on user device 104.

[0061]

[0063] Ticket agent 124 is associated with a ticket and / or ticket dispenser 190 that provides tickets. The ticket agent verifies the ticket and the win / lose status of the ticket through ticket verification server 122. When the ticket is confirmed to be a valid winning ticket (by ticket verification server 122), ticket agent 124 deposits winning funds into user account 106 associated with the ticket by the scanned identification number (e.g., the serial number described above). Ticket agent 124 may deposit funds to the user via provider bank account 126 and payment processing module or service 128. User account 106 may be associated with a bank account or card account 130. In some implementations, 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 only additional components or a subset of the components described above. For example, some implementations of system 100 may not include ticket agent 124, ticket verification 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, ticket verification server 122 and exchange terminal 120 may be combined, exchange terminal 120 and controller 110 may be combined, and so on.

[0064]

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

[0065]

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

[0066]

[0068] The communication (indicated by the arrows in the figure) within the ticket processing system 102 may be performed using the communication technologies described above. Additionally or alternatively, such communication may be performed using short-range communication technologies such as Bluetooth (Bluetooth 4.0, Bluetooth Smart, Bluetooth Low Energy (BLE), etc.), Near Field Communication (NFC), Ultra-Wideband (UWB), Radio Frequency Identification (RFID), infrared wireless, inductive wireless, or any known or undiscovered wired or wireless technology that can be used for short-range (up to about 100 feet) communication.

[0067]

[0069] FIG. 3 is a flow diagram of a method of operating a ticket processing system of the lottery system 100 of FIGS. 1 and 2 according to some implementations. Method 300 is optionally controlled by instructions stored in a computer memory or a non-transitory computer-readable storage medium of processing system 102, application server 108, redemption terminal 120, and / or verification 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 method 300 may be combined and / or the order of some operations may be changed.

[0068]

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

[0069]

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

[0070]

[0072] When the user device receives the user's selection result, it sends a ticket issuance command to the controller 110 via the application server 108, and the ticket issuance command is received in operation 304. When the controller 110 receives the ticket issuance command, it causes the selected ticket vending machine to issue the selected ticket. The ticket to be issued is a physical lottery ticket having a scratch area, a signature area, and / or an identification code (e.g., a lot number or a serial number) that becomes visible when issued or must be made to appear by a scratching machine.

[0071]

[0073] When the ticket is sent out, the first camera 112 (e.g., the lower camera) images the ticket, and the scanner 118 scans the identification code of the ticket (operation 306). The controller 110 sends the scanned identification number (referred to as the first ticket data) to the application server 108. In operation 308, the application server 108 associates (i.e., assigns, associates) the identification code of the ticket with 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 (operation 314) from the application server 108 (obtained by the user device 104). The signature data causes the robotic signature device to sign the signature area of the ticket (operation 312), and / or the scratch data causes the robotic scratch device to scratch the 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 application 105 (operation 310). The user inputs the signature using a touch screen, computer mouse, stylus, digital pen, keyboard, or other input method that captures an X-Y signature. The signature file is sent from the mobile application to the application server, the controller, and then the robotic arm, and the robotic arm physically signs the ticket (operation 312). The user can view 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 scratching of the ticket may be fully automated and may not require user interaction (other than to start and / or stop). In some implementations, the scratch device can use random X-Y coordinates. When the user performs a scratch gesture on the user interface and / or views a live video feed, the robotic arm physically scratches the ticket. In some implementations, there is a simulated ticket on the user device 104 (regardless of the presence of a video feed), and real-time feedback is provided to digitally simulate the scratching of the ticket on the user device 104.

[0075]

[0077] When the scratch operation is completed, the scanner 118 scans the information (referred to as the second ticket data) that appears within 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 before the scratch operation. In some implementations, it may not be necessary to make the information appear. In some implementations, the information is in a fixed location and / or the scratch operation is not required. The scanner 118 transmits the second ticket data (the information that appears) to the ticket exchange terminal 120 for processing by the ticket verification server 122 (or the second ticket data is sent directly to the ticket verification server 122).

[0076]

[0078] When the ticket agency receives the second ticket data, in operation 320, it determines the ticket status data corresponding to the winning or losing status of the ticket based on the second ticket data (via the verification server 122). If the ticket is a winning ticket (ticket status data corresponding to the winning status), the verification server 122 transmits, in operation 322, a notification including the amount associated with the winning status of the ticket to the application server 108 (for delivery to the user device).

[0077]

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

[0078]

[0080] In some implementations, after a ticket has been 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 ticket stream. The controller 110 may further cause the sorting device 134 to extract the winning tickets or distinguish them from the losing tickets, thereby storing the processed tickets according to their winning or losing status. In some embodiments, there may be a stack of error tickets in the event of a system error, an incomplete scan, or an incomplete scratch.

[0079]

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

[0080]

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

[0081]

[0083] Clause 1: A system including one or more controllers configured to obtain a first video stream from a first video camera proximate to a ticket issuing machine, transmit the first video stream to an application server for delivery to a user device, receive an 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 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 according to the user-provided scratch data or remove an opaque substance from the scratch area.

[0082]

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

[0083]

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

[0084]

[0086] Clause 4: The system according to any one of clauses 1 to 3, further comprising a ticket verification server configured to determine ticket status data corresponding to a winning or losing status of a ticket based on the identification code of the ticket, transmit a notification including an amount associated with the winning status of the ticket to a user device 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 associated with a user account associated with the user device.

[0085]

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

[0086]

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

[0087]

[0089] Clause 7: The system according to any one of Clauses 1 to 6, wherein the first video stream includes image data of the ticket vending machine and / or image data of the issued ticket.

[0088]

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

[0089]

[0091] Clause 9: The system according to any one of Clauses 1 to 8, wherein the user-provided signature data includes X-Y data obtained from the user interface of the user device, and the X-Y data corresponds to a two-dimensional user-provided gesture corresponding to a signature input at the user interface.

[0090]

[0092] Clause 10: The system according to any one of Clauses 1 to 9, wherein the user-provided scratch data includes X-Y data obtained from the user interface of the user device, and the X-Y data corresponds to a two-dimensional user-provided gesture corresponding to a scratch input at the user interface.

[0091]

[0093] Clause 11: The system according to any one of Clauses 1 to 10, wherein one or more controllers are further configured to obtain a second video stream including image data of the signature area of the ticket from a second video camera proximate to the ticket vending machine while the robotic signature device is signing the signature area.

[0092]

[0094] Clause 12: The system according to any one of Clauses 1 to 11, wherein one or more controllers are further configured to obtain a second video stream including image data of the scratch area of the ticket from a second video camera proximate to the ticket vending machine while the robotic scratch device is scratching the scratch area.

[0093]

[0095] Clause 13: A method including the operations described in any one 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 one 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: Obtain a first video stream from a first video camera proximate to a ticket vending machine, transmit the first video stream to an application server for delivery 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 a user-provided scratch command from the application server, and include one or more controllers configured to scratch the scratch area of the ticket or remove an opaque substance from the scratch area according to the user-provided scratch command.

[0097]

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

[0098]

[0100] Clause 3: The system according to any one of Clauses 1 or 2, wherein one or more controllers are further configured to obtain an identification code of the ticket from a scanning device proximate to the ticket vending machine and transmit the identification code to a ticket verification server.

[0099]

[0101] Clause 4: A ticket verification server further included in the system according to any one of Clauses 1 to 3, which is configured to determine ticket status data corresponding to the winning status or losing status of a ticket based on the identification code of the ticket, send a notification including the amount associated with the winning status of the ticket to the user device according to the ticket status data corresponding to the winning status of the ticket, and transfer funds corresponding to the amount associated with the winning status to the bank account linked to the user account associated with the user device.

[0100]

[0102] Clause 5: The system according to any one of Clauses 1 to 4, wherein one or more controllers are further configured to separate tickets from the ticket stream to the disconnection device and store the tickets according to the winning status or losing status of the tickets in the classification device.

[0101]

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

[0102]

[0104] Clause 7: The system according to any one of Clauses 1 to 6, wherein the first video stream includes image data of the ticket issuing machine and / or image data of the issued ticket.

[0103]

[0105] Clause 8: The system according to any one of Clauses 1 to 7, wherein the issued ticket includes a physical ticket body having two surfaces, the scratch area includes an opaque substance adhered to one of the two surfaces, and the signature area includes a blank portion of one of the two surfaces.

[0104]

[0106] Clause 9: The system according to any one of Clauses 1 to 8, wherein the user-provided signature data includes X-Y data obtained from the user interface of the user device, and the X-Y data corresponds to a two-dimensional user-provided gesture corresponding to a signature input at the user interface.

[0105]

[0107] Clause 10: The system according to any one of Clauses 1 to 9, wherein the user-provided scratch command causes the robot scratch device to start scratching the scratch area of the ticket or removing an opaque substance from the scratch area, and the robot scratch device is configured to scratch the scratch area of the ticket or remove an opaque substance from the scratch area using a pre-configured or random scratch pattern.

[0106]

[0108] Clause 11: The system according to any one of Clauses 1 to 10, wherein one or more controllers are further configured to obtain 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 robot signature device is signing the signature area.

[0107]

[0109] Clause 12: The system according to any one of Clauses 1 to 11, wherein one or more controllers are further configured to obtain 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 robot scratch device is scratching the scratch area.

[0108]

[0110] Clause 13: A method including the operations according to any one of Clauses 1 to 12.

[0109]

[0111] 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 obtain first image data from a camera associated with a ticket machine, transmit the first image data to an application server, receive an 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 issuance command, receive a user-provided scratch command from the application server, and cause a robot scratch device to scratch the scratch area of the ticket or remove an opaque substance from the scratch area according to the user-provided scratch command.

[0112]

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

[0113]

[0115] Clause 3: The system according to 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 verification server.

[0114]

[0116] Clause 4: A ticket verification server further included in the system according to any one of Clauses 1 to 3, which is configured to determine ticket status data corresponding to the winning status or non-winning status of a ticket based on the identification code of the ticket, send a notification including an amount associated with the winning status of the ticket to the user device according to the ticket status data corresponding to the winning status of the ticket, and transfer funds corresponding to the amount associated with the winning status to the bank account linked to the user account associated with the user device.

[0115]

[0117] Clause 5: The system according to any one of Clauses 1 to 4, further configured such that one or more controllers cause the disconnection device to separate the ticket from the ticket stream and cause the classification device to store the ticket according to the winning status or non-winning status of the ticket.

[0116]

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

[0117]

[0119] Clause 7: The system according to any one of Clauses 1 to 6, wherein the first image data includes an image of the ticket machine and / or an image of the ticket.

[0118]

[0120] Clause 8: The system according to any one of Clauses 1 to 7, wherein the ticket includes a physical ticket body having two surfaces, the scratch area includes an opaque substance adhered to one of the two surfaces, and the signature area includes a blank portion of one of the two surfaces.

[0119]

[0121] Clause 9: The system according to any one of Clauses 1 to 8, wherein the user-provided signature data includes X-Y data obtained from the user interface of the user device, and the X-Y data corresponds to a two-dimensional user-provided gesture corresponding to a signature input at the user interface.

[0120]

[0122] Clause 10: The system according to any one of Clauses 1 to 9, wherein the user-provided scratch command causes the robot scratch device to start scratching the scratch area of the ticket or removing an opaque substance from the scratch area, and the robot scratch device is configured to scratch the scratch area of the ticket or remove an opaque substance from the scratch area using a pre-configured or random scratch pattern.

[0121]

[0123] Clause 11: The system according to any one of Clauses 1 to 10, wherein one or more controllers are further configured to obtain second image data including an image of the signature area of the ticket from a second camera associated with the ticket machine while the robot signature device is signing the signature area.

[0122]

[0124] Clause 12: The system according to any one of Clauses 1 to 11, wherein one or more controllers are further configured to obtain second image data including an image of the scratch area of the ticket from a second camera associated with the ticket machine while the robot scratch device is scratching the scratch area.

[0123]

[0125] Clause 13: A method including the operations according to any one of Clauses 1 to 12.

[0124]

[0126] 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 according to any one of Clauses 1 to 12.

[0125]

[0127] The following clauses describe alternative and / or additional combinations of the implementation forms 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, transmit the user-provided scratch command to the ticket machine to cause a robot scratch device to scratch the scratch area of the ticket or remove an opaque substance from the scratch area according to the user-provided scratch command.

[0127]

[0129] Clause 2: The server system according to Clause 1, wherein 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 to cause a robot signature device to sign the signature area of the ticket according to the user-provided signature data.

[0128]

[0130] Clause 3: The server system according to any one of Clauses 1 or 2, wherein one or more controllers are further configured to receive an identification code of a ticket from a scanning device associated with the ticket machine and transmit the identification code to a ticket verification server.

[0129]

[0131] Clause 4: A ticket verification server further included in the server system according to any one of Clauses 1 to 3, which is configured to receive an identification code of a ticket from a scanning device associated with the ticket machine, determine ticket status data corresponding to a winning status or a losing status of the ticket based on the identification code of the ticket, send a notification including an amount associated with the winning status of the ticket to a user device 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 associated with a user account associated with the user device.

[0130]

[0132] Clause 5: The server system according to any one of Clauses 1 to 4, wherein 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 the ticket status data corresponding to the winning status of the ticket.

[0131]

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

[0132]

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

[0133]

[0135] Clause 8: The server system according to any one of Clauses 1 to 7, wherein the ticket includes a physical ticket body having two surfaces, the scratch area includes an opaque substance adhered to one of the two surfaces, and the signature area includes a blank portion of one of the two surfaces.

[0134]

[0136] Clause 9: A server system according to any one of Clauses 1 to 8, wherein user-provided signature data includes X-Y data obtained from a user interface of a user device, and the X-Y data corresponds to a two-dimensional user-provided gesture corresponding to a signature input at the user interface.

[0135]

[0137] Clause 10: A server system according to any one of Clauses 1 to 9, wherein a user-provided scratch command causes a robot scratch device to scratch a scratch area of a ticket or remove an opaque substance from the scratch area using a pre-configured or random scratch pattern.

[0136]

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

[0137]

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

[0138]

[0140] Clause 13: A method including the operations according to any one of Clauses 1 to 12.

[0139]

[0141] 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 according to any one of Clauses 1 to 12.

[0140]

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

[0141]

[0143] Clause 1: Receive first image data obtained from a camera associated with a ticket machine from an application server, display the first image data on a display of a user device, obtain a ticket issuance command for the ticket machine in a user interface of the user device, transmit the ticket issuance command to the ticket machine via the application server, cause the ticket machine to issue a ticket having a scratch area based on the ticket issuance command, obtain a scratch command provided by the user in the user interface of the user device, transmit the scratch command provided by the user to the ticket machine via the application server, and cause a robot scratch device to scratch the scratch area of the ticket according to the scratch command provided by the user, or a user device comprising one or more controllers configured to remove an opaque substance from the scratch area.

[0142]

[0144] Clause 2: The user device according to clause 1, wherein one or more controllers are further configured to obtain signature data provided by the user in a user interface of the user device, transmit the signature data provided by the user to the ticket machine via the application server, and cause a robot signature device to sign a signature area of the ticket according to the signature data provided by the user.

[0143]

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

[0144]

[0146] Clause 4: The user device according to any one of Clauses 1 to 3, wherein one or more controllers are further configured to receive, from a ticket verification server, a notification including an amount associated with the per-ticket status according to the ticket status data of the ticket corresponding to the per-ticket status.

[0145]

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

[0146]

[0148] Clause 6: The user device according to any one 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: The user device according to any one of Clauses 1 to 6, wherein the ticket comprises a physical ticket body having two surfaces, the scratch area includes an opaque substance adhered to one of the two surfaces, and the signature area includes a blank portion of one of the two surfaces.

[0148]

[0150] Clause 8: The user device according to any one of Clauses 1 to 7, wherein the user-provided signature data includes X-Y data obtained from a user interface of the user device, and the X-Y data corresponds to a two-dimensional user-provided gesture corresponding to a signature input at the user interface.

[0149]

[0151] Clause 9: The user device according to any one of Clauses 1 to 8, wherein the user-provided scratch command causes a robotic scratch device to scratch the scratch area of the ticket or remove the opaque substance from the scratch area using a pre-configured or random scratch pattern.

[0150]

[0152] Clause 10: The user device according to any one of Clauses 1 to 9, wherein the user-provided scratch command includes X-Y data obtained from the user interface of the user device, and the X-Y data corresponds to a two-dimensional user-provided gesture corresponding to a scratch input on the user interface.

[0151]

[0153] Clause 11: The user device according to any one of Clauses 1 to 10, wherein one or more controllers are further configured to receive from the application server second image data including an image of the signature area of the ticket obtained from a second camera associated with the ticket machine while the robot signature device is signing the signature area.

[0152]

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

[0153]

[0155] Clause 13: A method including the operations according to any one of Clauses 1 to 12.

[0154]

[0156] 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 according to any one 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 obtain first image data from a camera associated with a ticket machine, transmit 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 an opaque substance from the scratch area according to the user-provided scratch command.

[0157]

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

[0158]

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

[0159]

[0161] Clause 4: Further including a ticket verification server configured to determine ticket status data corresponding to a winning status or a losing status of the ticket based on the identification code of the ticket, transmit a notification including an amount associated with the winning status of the ticket to a user device according to the ticket status data corresponding to the winning status of the ticket, and transfer funds corresponding to the amount associated with the winning status to a bank account associated with a user account associated with the user device. The system according to any one of clauses 1 to 3.

[0160]

[0162] Clause 5: The system according to any one of Clauses 1 to 4, wherein one or more controllers are further configured to cause a cutting device to separate tickets from a ticket stream and cause a sorting device to store the tickets according to a hit status or a miss status of the tickets.

[0161]

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

[0162]

[0164] Clause 7: The 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.

[0163]

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

[0164]

[0166] Clause 9: The system according to any one of Clauses 1 to 8, wherein the user-provided signature data includes X-Y data obtained from a user interface of a user device, and the X-Y data corresponds to a two-dimensional user-provided gesture corresponding to a signature input at the user interface.

[0165]

[0167] Clause 10: The system according to any one of Clauses 1 to 9, wherein a user-provided scratch command causes a robot scratch device to start scratching a scratch area of a ticket or removing an opaque substance from the scratch area, and the robot scratch device is configured to scratch the scratch area of the ticket or remove the opaque substance from the scratch area using a pre-configured or random scratch pattern.

[0166]

[0168] Clause 11: The system according to any one of Clauses 1 to 10, wherein one or more controllers are further configured to obtain second image data including an image of the signature area of the ticket from a second camera associated with the ticket machine while the robot signature device is signing the signature area.

[0167]

[0169] Clause 12: The system according to any one of Clauses 1 to 11, wherein one or more controllers are further configured to obtain second image data including an image of the scratch area of the ticket from a second camera associated with the ticket machine while the robot scratch device is scratching the scratch area.

[0168]

[0170] Clause 13: A method including the operations according to any one of Clauses 1 to 12.

[0169]

[0171] 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 according to any one of Clauses 1 to 12.

[0170]

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

[0171]

[0173] For example, a particular feature of an exemplary embodiment may or may not be part of the claimed invention, and at least some of the features described herein may be performed by different components rather than the particularly recited components, and the 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 value being referenced. For example, "about 9" is understood to include 8.2 and 9.9.

[0173]

[0175] At least some of the figures and descriptions of the present invention have been simplified to focus on related elements so that the present invention can be clearly understood, and for clarity, it should be understood that other elements that a person skilled in the art would recognize as possibly constituting a part of the present invention have been excluded. However, since such elements are well known in the art and do not necessarily facilitate a further understanding of the present invention, no description of such elements is provided herein.

[0174]

[0176] In this specification, terms such as "first", "second", etc. are sometimes used to describe various elements, but it should be understood that these elements should not be limited by these terms. These terms are only used to distinguish one element from another.

[0175]

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

[0176]

[0178] As used herein, the term "when" may optionally be construed to mean "upon" or "in response to a determination that" or "in response to a detection of" or "in accordance with a determination that", depending on the context. Similarly, the phrases "when determined" or "when [stated state or event] is detected" may optionally be construed to mean "when determined that" or "in response to a determination that" or "when [stated state or event] is detected" or "in response to detecting [stated state or event]" or "in accordance with a determination that [stated state or event] is detected", depending on the context.

[0177]

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

[0178]

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

[0179]

[0181] Also, the term "and / or" as used herein is to be understood to refer to and encompass any and all possible combinations of one or more of the associated listed items.

[0180]

[0182] Further, the terms "comprises" and / or "comprising" as used herein are to be understood to indicate the presence of the stated features, integers, acts, elements, and / or components, but not to preclude the presence or addition of one or more other features, integers, acts, elements, components, and / or groups thereof.

[0181]

[0183] The term "when (if)" as used in this specification may, depending on the context, be interpreted to mean "when" the foregoing condition is true, or "upon" the foregoing condition being true, or "in response to a determination that" the foregoing condition is true, or "in accordance with a determination that" the foregoing condition is true, or "in response to a detection that" the foregoing condition is true.

[0182]

[0184] Similarly, the phrases "(when it is determined that) (the foregoing condition is true)", or "(when) (the foregoing condition is true)", or "(when) (the foregoing condition is true)" may, depending on the context, be interpreted to mean "when it is determined that" the foregoing condition is true, or "in response to a determination that" the foregoing condition is true, or "in accordance with a determination that" the foregoing condition is true, or "when it is detected that" the foregoing condition is true, or "in response to a detection that" the foregoing condition is true.

[0183]

[0185] Further, unless the method depends on a particular order of steps described herein, the particular order of steps should not be construed as limiting the claims. The claims directed to the method of the present invention should not be limited to performing the steps in the order described, and one of ordinary skill in the art can readily understand that the steps may be varied and still be within the spirit and scope of the present 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; Receive user-provided 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 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. The system of claim 1 , further comprising a robotic signature mechanism configured to sign the signature area of ​​the ticket in accordance with the user-provided signature data.

5. 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 , further comprising:

6. 6. The system of claim 1, 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.

7. 7. 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.

8. 8. 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.

9. 9. The system of claim 1, further comprising a video camera proximate to the ticket issuing machine and configured to capture a video stream including image data of the signature area of ​​the ticket while the robotic signature mechanism is signing the signature area.

10. 10. The system of claim 1, further comprising 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.

11. A method comprising the operations of any one of claims 1 to 10.

12. 11. 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 of any of claims 1 to 10.

Images