Patent Application
20220309862
Generally, there are two types of lotteries. A first type of lottery is a draw-based lottery or “online” lottery, where a player makes a wager with respect to a subsequently occurring event. For example, a player may wager based upon numbers that will be drawn in the subsequent event. The numbers, which may be selected by the player or randomly selected if the player does not have a preference for the numbers, are printed on a ticket and provided to the player. Once the event occurs, for example the numbers are drawn or generated by the lottery organization, the ticket may be a winner depending on if one or more of the selected numbers were drawn or generated.
A second type of lottery is an instant win lottery where a printed ticket provides all of the lottery information. These instant-win tickets typically have a play area covered by scratch off material. The tickets can be purchased from a retailer, and the scratch off material removed to reveal whether the ticket is a winner.
An ongoing need exists for methods and systems which will allow users to participate in available lottery-type games efficiently and effectively.
Generally disclosed herein are methods and systems for facilitating a user's ongoing participation in lottery-type games.
In some embodiments a computer-implemented method for facilitating user participation in a user configurable subscription lottery plan comprising a central processor unit executing executable instructions to cause the performance of the method steps comprising: receiving information related to a user's selection of a user configurable subscription lottery device; determining validity of the information; updating one or more records associated with the user configurable subscription lottery device; allowing a user to access to the user configurable subscription lottery plan; providing options to the user for user configurable lottery-play criteria; and entering the user in one or more lotteries.
In some embodiments is a user configurable subscription lottery plan processing system comprising: a processor comprising a computer-readable medium storing instructions configured to cause the processor to: receive information related to a user's selection of a user configurable subscription lottery device; determine validity of the information; update one or more records associated with the user configurable subscription lottery device; allow a user to access to the user configurable subscription lottery plan; provide options to the user for user configurable lottery-play criteria; and enter the user in one or more lotteries.
Disclosed herein are various embodiments of pre-printed lottery tickets that can be securely merchandised, that is, made available, throughout a retail store without risk of loss from fraudulent redemption or shrinkage. Generally, the pre-printed lottery tickets disclosed herein can be displayed openly, for example, throughout a retail establishment, in that the pre-printed lottery tickets are inactive. Additionally, the disclosed pre-printed lottery tickets closely resemble a traditional paper ticket so as to foster consumer recognition, trial, and confidence.
In some embodiments, pre-printed tickets may be manufactured and shipped to retail locations. Retailers may manage inventory and display the pre-printed tickets in, for example, checkout lanes, at counters and throughout the store where the product is most visible to customers. Customers can select a lottery product at any time with no additional interaction with a lottery retailer and drop the pre-printed lottery ticket(s) into their shopping cart. During the checkout process, the pre-printed ticket is scanned by the cashier in the retailer's point of sale (e.g., terminal) as they would scan any other product being purchased. The pre-printed ticket may require one, possibly two scans dependent on the bar code standard used and the technical abilities of the retailer's point of sale system. Upon scanning of the ticket the retailer's point of sale will be updated with the product description and cost. The retailer's point of sale will communicate the transaction type, such as purchase or cancel, and the pre-printed ticket details, such as product information and/or a unique identifier, to other components/parties of the lottery (e.g., a central gaming system, a lottery system, or combinations thereof) though a secure communications channel. Upon receiving information for activating a pre-printed ticket being purchased, the system may initiate a pre-printed ticket wager by validating the pre-printed ticket details, generating the appropriate lottery wager information, for example generating an appropriate number of random numbers for the draw. The generated wager information may then be associated with unique identifier of the pre-printed ticket in the system and the pre-printed ticket activated for the next available draw. Confirmation of the activation, as well as the lottery numbers and draw information, for example when the draw is being held, may be withheld from the retailer's point of sale until payment confirmation is received by the lottery system. The cashier continues to scan the customer's purchases until the cart is empty. The cashier may then process payment as the normal course of action. Prior to the retailer's point of sale closing the sale and printing the receipt, the retailers point of sale system may communicate the payment confirmation and details to the system (e.g., a lottery system or central gaming system). Once payment confirmation is received the system (e.g., via a central gaming system and/or the lottery system) may in turn communicate the lottery numbers and draw information to the retailers point of sale system. This information may be communicated in the form of an image, text or any other message format deemed appropriate. The lottery numbers and draw date assigned to the pre-printed lottery ticket may be printed on the customer's store receipt. The printed receipt with the lottery information is for informational purposes only, and the pre-printed ticket would be required to validate the lottery numbers or to redeem a winning prize.
Additionally, also disclosed herein are various embodiments of virtual lottery tickets having preselected attributes (e.g., lottery picks). As will be disclosed herein, the pre-printed lottery tickets or preselected virtual lottery tickets disclosed herein allow for technical improvements in the processing of lottery tickets, in comparison to the way in which conventional lottery tickets are processed using conventional lottery systems. Particularly, in comparison to conventional lottery systems, the systems utilized to process the disclosed physical pre-printed/virtual pre-selected lottery tickets can benefit from reduced computer processing requirements due to the fact that the pre-printed/pre-selected ticket accounts/files are already present in the system and only need to be marked as active/enrolled instead of the system having to create new account/files for every ticket entered in a particular lottery.
Additionally, also disclosed herein are various embodiments of gaming devices configured to allow for a game to be accessed, loaded, or funded. As will be disclosed herein, like the pre-printed lottery tickets, the gaming devices can be displayed openly, for example, throughout a retail establishment, in that the pre-printed lottery tickets are inactive. Additionally, disclosed herein are lottery gaming systems and methods for the sale and activation of pre-printed draw based lottery tickets through the retailers' point of sale systems without the need for adding additional lottery gaming hardware to the retailers' point of sale systems.
It will be appreciated that in some contexts, a purchaser of a ticket may not ultimately be the person who “plays” or “uses” the ticket; conversely, a purchaser of a ticket may be a player or user of a ticket (though not necessarily). Thus, references throughout this disclosure to one or more of a “purchaser,” “consumer,” “user,” or “player” are not intended to be limiting and should be interpreted as synonymous except where explicitly or contextually so-limited.
In some embodiments disclosed herein are draw-type pre-printed lottery tickets. In some embodiments, the draw-type pre-printed lottery tickets may be activated at a point of sale (POS), such as in a retail store or via a consumer's interaction with a website or smart device application which provides the consumer with the ability to purchase and activate a virtual version of a draw-type pre-printed lottery ticket, e.g., a virtual draw-type pre-selected lottery ticket 102. In some embodiments, a draw-type pre-printed lottery ticket may be activated by enrollment of that particular draw-type pre-printed lottery ticket in a lottery.
In an embodiment, until purchased and activated, pre-printed tickets have no value, nor do they have any wager or draw date assigned. They cannot be used for validation or redemption purposes prior to purchase. For example, prior to activation (for example, by enrollment in a lottery), as will be disclosed herein, even if a draw-type pre-printed lottery ticket bears winning indicia, no prize would be paid out by the lottery to a holder of the draw-type pre-printed lottery ticket. Only winning tickets that have been activated, for example, enrolled in a lottery game, will be redeemable. For example, once scanned by the retailer's POS and paid for by the customer, the lottery will generate wagers for the pre-printed ticket and assign the next available draw date. The generated numbers, the draw date and unique ticket identifier is printed on the customers shopping receipt. Although the draw information is printed on the customer's receipt, it is only information and the pre-printed lottery ticket is the legal instrument for validation and prize redemption. Draw information on the printed receipt also serves to confirm the activation of the pre-printed lottery ticket and the assignment of draw numbers and draw date.
In some embodiments, the draw-type pre-printed lottery tickets disclosed herein contain pre-printed play-selections (e.g., wagers) which will later be determined to be either winning or losing. In such a case, when the pre-printed ticket with pre-printed play-selections is purchased, the lottery (e.g., central gaming system) may simply assign the next draw date to the pre-printed ticket and activate the ticket within the system. In this variation, the central gaming system will have a database of pre-printed tickets and associated play-selections.
Similarly, in some embodiments, a consumer may purchase a virtual draw-type pre-selected lottery ticket which will also include, e.g., be associated with, data equivalent to the information imprinted on a draw-type pre-printed lottery ticket. In various embodiments, the virtual ticket may be processed/activated/enrolled/and determined to be winners or losers via the same methods as described for the physical ticket, with the exception that a virtual ticket may be directly entered into a consumer's e-wallet and its purchase/activation requires a confirmation that the consumer device which has requested the purchase/activation is located in a geographic location approved for the sale of the particular virtual lottery ticket and/or participation in the particular gaming authority's lottery game. For example, the pre-printed play-selection may be determined to be either winning or losing based upon a drawing or other event taking place at a time after purchase of the draw-type pre-printed lottery ticket. After a draw-type pre-printed lottery ticket is purchased and activated by enrollment in a lottery, the lottery “plays” printed on the draw-type pre-printed lottery ticket may be compared to subsequently drawn numbers to determine if one or more of the lottery plays constitute winning entries. The draw-type pre-printed lottery tickets disclosed herein are distinct from scratch-off lottery tickets in which game data, when unobscured, is instantly recognizable as either winning data or non-winning data.
Referring to
In the embodiment of
In various embodiments, as shown in
In an alternative embodiment, the draw-type pre-printed lottery ticket 100 may be configured for play in a Mega Millions® lottery game (Mega Millions® is a registered trademark of Illinois Department of the Lottery). In an embodiment where the draw-type pre-printed lottery ticket 100 configured for play in a Mega Millions® lottery game, each play-selection 120 may include six attributes 122, particularly, a first, second, third, fourth, fifth, and sixth attribute 122. Each of the first, second, third, fourth, and fifth attributes 122 may be a number selected from seventy (70) possibilities and the sixth attribute 122 may be a number independently selected from twenty-five (25) possibilities. In an embodiment where the lottery ticket is a virtual draw-type pre-selected lottery ticket 102, the virtual draw-type pre-selected lottery ticket 102 may be electronically delivered to a consumer's device 200 wherein the virtual draw-type pre-selected lottery ticket 102 may be displayed as having the same characteristics as described in this paragraph for the physical draw-type pre-printed lottery ticket 100.
In some embodiments, the draw-type pre-printed lottery ticket 100 may include a covering 340 configured to obscure the play-selections 120, an encrypted control number 130, a low-tier redemption code 140, and a high-tier redemption code 220, until removed. In various embodiments, the covering may be a continuous layer disposed over a given play-selection 120 or two or more play-selections or disposed over a given attribute 122 or two more attributes 122. In various embodiments, the covering may be a continuous layer disposed over the encrypted control number 130, the low-tier redemption code 140, and the high-tier redemption code 220. The covering may include a material that may be suitably removed by a purchaser, such as a scratch-off material, an example of which may include, but is not limited to a latex film. The scratch-of material may obscure various information (e.g., the play-selections) from observation by both the ticket distributor (e.g., a retailer) and the ticket purchaser until after the ticket has been sold.
As shown in
As shown in
For example, in the embodiment of
Also, in the embodiment of
As shown in
Also, in the embodiment of
Also, in the embodiment of
Also, in the embodiment of
Also, in the embodiment of
As shown in
Also in the embodiment of
As shown in
A variation of the above is to produce pre-printed tickets with pre-printed wagers on the ticket. In such a case, when the pre-printed ticket with pre-printed wagers is purchased, the central gaming system 540 may simply assign the next draw date to the pre-printed ticket and activate the ticket within the lottery system. The central gaming system 540 in this variation will have a database of pre-printed tickets and associated lottery wagers.
In some embodiments disclosed herein are instant-win-type pre-printed lottery tickets. In some embodiments, the instant-win-type pre-printed lottery tickets may be activated at a POS, such as in a retail store or a consumer's interaction with a website or smart device application which provides the consumer with the ability to purchase and activate a virtual version of a draw-type pre-printed lottery ticket, e.g., a virtual instant-win-type pre-selected lottery ticket 302. In some embodiments, an instant-win-type pre-printed lottery tickets contain hidden pre-printed winning and losing game data. As such, the instant-win-type pre-printed lottery tickets are distinct from lottery tickets in which winning numbers are drawn some time after the sale of the ticket.
Referring to
In various embodiments, the instant-win-type pre-printed lottery ticket 300 is imprinted with various indicia (such as information, such as certain numbers, symbols, words and the like). Similarly, a consumer may purchase a virtual instant-win-type pre-selected lottery ticket 302 which will also include, e.g., be associated with, data equivalent to the information imprinted on a physical instant-win-type pre-printed lottery ticket 300. In various embodiments, the virtual ticket may be processed/activated/enrolled/and determined to be a winner or a loser via the same methods as described for the physical ticket, with the exception that a virtual ticket may be directly entered into a consumer's e-wallet and its purchase/activation requires a confirmation that the consumer device which has requested the purchase/activation is located in a geographic location approved for the sale of the particular virtual lottery ticket and/or participation in the particular gaming authority's lottery game. In some embodiments, the indicia may provide an indication as to whether the bearer has won a prize. Particularly, in the embodiment of
As shown in
In some embodiments, the instant-win-type pre-printed lottery ticket 300 may include a covering 340. For example, as illustrated in
In some embodiments, as shown in
In some embodiments, as shown in
Also, in some embodiments, as shown in
Additionally, in some embodiments the instant-win-type pre-printed lottery ticket 300 may also contain other information such as marketing, pricing, and rules of play, as similarly disclosed with respect to the draw-type pre-printed lottery ticket 100. In an embodiment where the lottery ticket is a virtual instant-win-type pre-selected lottery ticket 302, the virtual instant-win-type pre-selected lottery ticket 302 may be electronically delivered to a consumer's device 200 wherein other types of information, for example, related to as marketing, pricing, rules of play, and the like may be displayed.
Also disclosed herein are embodiments related to a system for processing a pre-printed lottery ticket (and/or a virtual pre-selected lottery ticket), such as the draw-type pre-printed lottery ticket 100 of
In some embodiments, the POS terminals 502 disposed at the retailer 501 may include a processing unit 504, memory unit 506 and I/O interface(s) 508 for communicating with devices external to the POS terminal 502. Additionally or alternatively, while the embodiment of FIG. 5A illustrates POS terminals 502 disposed at the retailer 501, in some other embodiments, other types of terminals may be used in place or along with conventional POS terminals, for example, network terminals which may include PCs, laptops, handheld devices, mobile phones, or other devices. Network terminals may, for example, be made available in kiosks to provide retailers access to the lottery system 520 and the associated functionality.
In some embodiments, the processing unit 504 can comprise an electronic input device, a register or terminal, a computer processing unit (“CPU”), a personal computer, a personal digital assistant (e.g., smart phone), or other means of communicating with the I/O interface(s) 508. In some embodiments, the processing unit 504 may incorporate a “store-and-forward” functionality. Generally, the store-and-forward functionality may operate during activation of a stored-value card such that, if connectivity between the POS terminal 502 and a stored-value processing system is lost during activation of the stored-value card, the processing unit 504 will store the activation request for the stored-value card and communicate the activation request when connectivity is regained, thus allowing the activation to go forward. In some embodiments, the processing unit 504 may be configured to allow the store-and-forward functionality to be disabled or suppressed.
The I/O interface(s) 508 generally comprises one or more interpretation units such as a bar code scanner, magnetic strip reader, optical character recognition device, biometric recognition device, numerical keyboard (e.g., for entering an identification number), or other device configured to interrogate, interpret, capture, or input the data encoded in or on the authentication token. For example, the I/O interface(s) 508 may comprise a barcode scanner for scanning and/or retrieving machine-readable (e.g., barcode information, such as Universal Product Code information or other information) disposed on a ticket. In some embodiments, the POS terminal 502 may also be connected to a printer 512, for example, for printing a receipt 114 of the transaction. The POS terminal 502 includes instructions 514 stored in the memory unit 506, which when executed by the processor unit 504, cause the POS terminal 502 to provide certain functionality, as disclosed herein.
In an embodiment, the lottery system 520 generally includes a processing unit 522, one or more memory units 524, one or more I/O interface(s) 526 for communicating with components external to the lottery system 520, a communication module 550 which is integrated with other systems capable of storing information and transmitting information according to the desired communication method, and at least one API 525 to interface and/or interact with components/systems outside lottery system 520. The memory unit(s) 524 may store instructions 528 that, when executed by the processing unit 522, cause the lottery system 520 to provide certain functionality, as disclosed herein. For example, in an embodiment, certain functionality may be receiving and verifying pre-printed lottery ticket information from a plurality of different retailers. The verification of the pre-printed lottery ticket information may involve checking that the received information corresponds to an actual ticket, verifying one or more check-digits, and/or verifying that the pre-printed lottery ticket was distributed to the retailer. In an embodiment, certain functionality may be processing transactions and exchanging data from a plurality of different retailers to a single central gaming system or multiple central gaming systems. Instructions 528 may include any functionality necessary for the successful exchange of data and the activation, cancellation, enrollment, and/or purchase of a lottery ticket.
As illustrated, pre-printed lottery ticket processing system 2500 includes a retailer's point of sale terminal 2022 and a central gaming system 2202 connected to each other through one or more communication networks 2180. The communication between retail POS terminals and the central gaming system may be secured using various encryption techniques.
The retailer's POS terminal 2022 may include a central processing unit (CPU) 2040, memory unit 2060 and I/O interface(s) 2080 for communicating with devices external to the POS terminal. As illustrated, a barcode scanner 2107 may be connected for scanning in barcode information, such as Universal Product Code information, and pre-printed ticket information. The retailer POS terminal may also be connected to a printer 2102 for printing a receipt 114 of the transaction. The POS terminal 2022 includes instructions 2140 stored in the memory unit 2060, which when executed by the processor unit 2040 configure the POS terminal 2022 to provide pre-printed draw-based lottery ticketing functionality 2160. The functionality 2160 may provide the functionality for communicating scanned in barcode information of pre-printed lottery tickets with the central gaming system 2202, and receiving confirmation of the pre-printed ticket's activation, as described herein.
The central gaming system 2202 may include a central processing unit (CPU) 2220, memory unit 2260 and I/O interface(s) 2240 for communicating with devices external to the central gaming system 2202. Instructions 2280 stored in the memory unit 2260, when executed by the processing unit 2220 configure the central gaming system 2202 to provide pre-printed draw-based lottery ticket activation and cancellation functionality 2300. The functionality 2300 may receive and verify pre-printed lottery ticket information from a plurality of different retailers. The verification of the pre-printed lottery ticket information may involve checking that the received information corresponds to an actual ticket, verifying one or more check-digits, and/or verifying that the pre-printed lottery ticket was distributed to the retailer. The pre-printed ticket information used in verifying the received information may be stored in a pre-printed ticket information database 2320. The functionality 2300 may also generate draw and wager information and associate the pre-printed ticket information in a draw information database 2340. The draw information database 2340 may be used in verifying subsequent tickets, including the pre-printed lottery tickets, as winning tickets following the draw event.
As illustrated, pre-printed lottery ticket processing system 2500 includes a retailer's point of sale terminal 2022 for the sale of the pre-printed ticket 100, a central gaming system 2202 for the generation and activation of pre-printed ticket wagers and draw date and a lottery system 6300 to facilitate the exchange of data between the retailer's point of sale 2022 and the central gaming system 2202 each connected to one other through one or more communication networks 2180; 2190. The communication between retail POS terminals 2022, the lottery system 6300, and the central gaming system 2202 may be secured using various encryption techniques.
The retailer's POS terminal 2022 may include a central processing unit (CPU) 2040, memory unit 2060 and I/O interface(s) 2080 for communicating with devices external to the POS terminal. As depicted, a barcode scanner 2107 may be connected for scanning in barcode information, such as Universal Product Code information, and pre-printed ticket information. The retailer POS terminal may also be connected to a printer 2102 for printing a receipt 114 of the transaction. The POS terminal 2022 includes instructions 2140 stored in the memory unit 2060, which when executed by the processor unit 2040 configure the POS terminal 2022 to provide pre-printed draw-based lottery ticketing functionality 2160. The functionality 2160 may provide the functionality for communicating scanned in barcode information of pre-printed lottery tickets to the lottery system 6300, and receiving confirmation of the pre-printed ticket's activation, as described herein.
The central gaming system 2202 may include a central processing unit (CPU) 2220, memory unit 2260 and I/O interface(s) 2240 for communicating with devices external to the central gaming system 2202. Instructions 2280 stored in the memory unit 2260, when executed by the processing unit 2220 configure the central gaming system 2202 to provide pre-printed draw-based lottery ticket activation and cancellation functionality 2300. The functionality 2300 may receive and verify pre-printed lottery ticket information from a plurality of different retailers. The verification of the pre-printed lottery ticket information may involve checking that the received information corresponds to an actual ticket, verifying one or more check-digits, and/or verifying that the pre-printed lottery ticket was distributed to the retailer. The pre-printed ticket information used in verifying the received information may be stored in a pre-printed ticket information database 2320. The functionality 2300 may also generate draw and wager information and associate the pre-printed ticket information in a draw information database 2340. The draw information database 2340 may be used in verifying subsequent tickets, including the pre-printed lottery tickets, as winning tickets following the draw event.
The lottery system 6300 may include a central processing unit (CPU) 6040, memory unit 6160 and I/O interface(s) 6080 for communicating with devices external to the transaction processor system 6300. Instructions 6140 stored in the memory unit 6160, when executed by the processing unit 6040 provide transaction processing and data exchange functionality 6020. The functionality 6020 may process transactions and exchange data from a plurality of different retailers to a central gaming system 2202 (or in other embodiments to a plurality of different central gaming systems). Instructions 6140 may include any functionality necessary for the successful exchange of data and the activation or cancellation of the pre-printed ticket 100.
In general, the system network 600 in
The system network 600 in
The layers of access are implemented as virtual local area networks (VLANs) having no real access to one another except through routing done by routing modules on the network switches. Each VLAN may be configured appropriately to limit access according to the appropriate level of security. The levels of security correspond in general to four tiers of network entities: the presentation tier, the business logic tier, the data access tier, and the data tier.
At the top level of access (for the consumer front-end), the presentation tier is responsible for delivery of data to end clients. The end clients may be consumers or partners 620a, 620b, 620c. In the presentation tier, data is formatted for communication with the business logic tier of applications that processes requests and handles data delivery to the client applications. Data in the presentation tier may be in XML format along with XSLT stylesheets to allow rendering by client applications. The presentation tier operations, generally, in a layer of servers from the web server farm 602 that resides in a DMZ (DeMilitarized Zone) network. These servers in the DMZ network may be accessed using a web farm DMZ VLAN 630 and the Layer 7 switch farm 610. The DMZ network servers operate as proxy servers between consumers and the enterprise infrastructure.
The next layer of access includes servers in the web server farm 602 that form the business logic tier. The business logic tier includes application code (Beans) that will handle requests from client applications (such as web browsers) and make requests to the Data Access Tier for relevant data. It will then process the data and deliver it for presentation to the client applications. The business logic tier is kept separate from interaction with consumers to preserve integrity of the applications and access to the database 605. Added security may be provided by an outer web farm VLAN 632.
In the next layer, the data access tier may make requests directly to the Data Tier (or the database 605). The data access tier may be separate from the business logic tier of applications to differentiate how the data is stored and how it is retrieved from certain platforms. Security may be configured with an inner web farm VLAN 634.
The data tier is in the last layer of security, which includes the database 605, and which has the tightest security to protect the most critical data. Security may be configured with an internal access VLAN 636.
The system network 600 includes a general horizontal separation of EDI partnerships, which are logical VLANs that separate access by each partner 620a, 620b, 620c to the infrastructure of the example system for implementing the disclosed lottery system/systems using the system network 600. In general, a partner may access their own private VLAN at 616 and 618 into the system network 600 infrastructure through a VPN concentrator or routed through a routing module on the backbone switch. This structure may isolate potential security breaches from single partners 620a, 620b, 620c. It may also prevent any partner 620a, 620b, 620c from being able to access rival partner data from the system network 600.
The EDI partner access to the system network 600 may also be layered vertically according to level of security. An EDI farm DMZ VLAN 640 provides the lowest level of security at the consumer front-end for access to the EDI server farm 606. The outer EDI farm VLAN 642 provides a higher level of security at a business logic level similar to the business logic tier described above with reference to the web server farm 602. The highest level of security is provided at the inner EDI farm VLAN 644 for access to more critical data via the database server farm 604.
Connectivity to the system network 600 may be provided by co-location facilities hosting the remote infrastructure. Connectivity may be provided by Tier 1 Internet Backbone providers to ensure access to most networks without having to transcend networks in order to provide the shortest network path from Leverage Consumer to Leverage Infrastructure. Besides utilizing connectivity to Tier 1 providers and managing complex BGP routes to the Internet Backbone, a backup connection to InterNAP will also be established.
In the example system for implementing an embodiment of the disclosed system, the complex backbone connections force the infrastructure to appear “local” to the consumers accessing the system network 600 via their host ISPs. This prevents the consumer from transcending networks between peer networks and eventually experience degraded network performance.
The web server farm 602 includes two banks of servers for serving either static or dynamic content. Each bank may be designated as either the static web farm or the dynamic web farm. The static web farm may service client requests for static content that is neither database-generated nor does it use any type of server content processing and generation before being transmitted through the Internet to the client applications (e.g. web browser). Such examples of content would be images, video, or web templates. The dynamic web farm may be designed to serve dynamic content generated in multiple ways, whether that is done via XML/XLS transformation, server-side scripting, or through middle-tier applications that directly interfaces with the database 605.
The web server farm 602 may be implemented using any suitable hardware and software systems implementing server functions. In one example implementation, the web server farm 602 is implemented with Sun® multiprocessor blade servers (Sun® is a registered trademark of Oracle America, Inc.) running either the Solaris® (Solaris® is a registered trademark of Oracle America, Inc.) operating system or Red Hat® Enterprise Linux™ operating system (Red Hat® Enterprise Linux™ are trademarks of Red Hat, Inc.). The example implementation of the web server farm 602 also includes the Zeus® web server (ZWS) application (Zeus® is a registered trademark of Marden-Kane, Inc.). Like the Apache® web server Apache Micro Peripherals, Inc.), the ZWS is a robust, commercial-grade, full-featured and highly efficient web server software. However, ZWS is multi-threaded to leverage the symmetric multiprocessing nature of multi-cored hardware platforms, which increases the response times and load servicing for client requests. The web server farm 602 will also house the Java® application server software (Java® is a registered trademark of Oracle America, Inc.) that operates the applications to service consumer requests on the enterprise website. The Java® application server software may be a combination of Apache® Tomcat for simple Java® applications and JBoss Application Server software for J2EE applications.
It is to be understood that specific implementations of the web server farm 602 may use any suitable hardware and software systems. The hardware and software systems described above are merely examples of the types of hardware and software systems that may be used.
The database server farm 604 may store data specific to consumer front-end interactions and the EDI partner data collected from partners 620a, 620b, 620c. The database server farm 604 may be implemented using any suitable hardware and software systems configured to operate as database servers. In one example implementation, the database server farm 604 is implemented using Sun multiprocessor Enterprise servers banked with multi-core processors and full redundant power and mirrored drives for the operating system and database application. Depending upon the nature of the application and the database 605 that is needed to interface against such applications, the database server farm 604 may run either the Oracle Database Server product or the MySQL Database server product. Also, depending upon the nature of the data that is being stored, highly complex relational database tables may use Oracle while simplistic database schemas may use MySQL. The database server applications may be clustered to ensure high availability and fault tolerance. This will also provide application load balancing among the database server farm 604.
The database 605 for the database server farm 604 may reside in a SAN (Storage Area Network) solution that will offer both high availability and fault tolerance.
It is to be understood that specific implementations of the database server farm 604 may use any suitable hardware and software systems. The hardware and software systems described above are merely examples of the types of hardware and software systems that may be used.
The EDI (Electronic Data Interchange) farm 606 may be designated in the system network 600 to communicate with partners 620a, 620b, 620c. The EDI farm servers 606 may have different applications and permissions from the web server farm 602 to access and process, as well as store, data within the database farm 604. The nature of the applications operating on the EDI farm servers 606 may have more direct access to the database 605 to increase efficiency in data processing and storage. The EDI farm servers 606 may reside in a private VLANs (Virtual Local Area Networks) that can only be accessed via VPN (Virtual Private Network) Concentrators or through specific Point-to-Point access into the VLAN as shown at 616 and 618.
The EDI farm servers 606 may be implemented using any suitable hardware and software system configured to operate server functions. In an example implementation, the EDI server farm 606 is implemented using the same platform as that of the web server farm 602 or by running IBM Mainframes. The EDI farm servers 606 software in the example implementation may also be similar to that of the web server farm 602 software. If the EDI farm servers 606 include IBM Mainframes, then the hardware will run IBM AIX operating systems, and the EDI farm servers 606 will run IBM Websphere Application Server software.
It is to be understood that specific implementations of the EDI server farm 606 may use any suitable hardware and software systems. The hardware and software systems described above are merely examples of the types of hardware and software systems that may be used.
The internal access farm servers 608 may also resemble the web server farm 602 in platform, software, and resource architecture. However, like the EDI farm servers 606, the applications will be tailored for internal access from an enterprise Intranet. Such applications may include data mining and statistical information for marketing and sales.
Referring again to
Also, in some embodiments, the lottery system 520 may be configured for communication with at least one CGS 540 (e.g., at least one of 540a, 540b, and 540c). Generally, lottery jurisdictions (e.g., a states) use various CGSs to manage the drawings associated with a lottery. In various embodiments, the lottery system 520 is configured to utilize one or more application programming interfaces (APIs) that are each configured to allow the lottery system 520 to interface and/or interact with a particular CGS (e.g., 540a, 540b, 540c). For example, in the embodiment of
In some embodiments, the CGSs 540 may be configured for communication with one or more information datastores, e.g., datastore 545. Datastore 545 may contain separate sub-datastores 545a and 545b. I an embodiment, separate sub-datastores 545a and 545b may individually or collectively include an entry for each of the pre-printed lottery tickets offered for sale the retailer 301 or multiple retailers. In an embodiment ticket information used in verifying information may be stored in a ticket information database, e.g., datastore 545a. Draw and wager information may be stored in a lottery information database, e.g., datastore 545b. The lottery information database 545b may be used in verifying subsequent tickets, including the pre-printed lottery tickets, as winning tickets following the draw event.
Also disclosed herein are embodiments of methods related to processing a transaction with respect to a pre-printed lottery ticket (and/or a virtual pre-selected lottery ticket), for example, the draw-type pre-printed lottery ticket 100 of
Referring to
In the embodiment of
At block 701, the method 700 begins when a purchaser selects the draw-type pre-printed lottery ticket 100, which may be displayed at the retailer 501 and, at block 702, the purchaser proceeds to the POS terminal 502 and presents the draw-type pre-printed lottery ticket 100 to the cashier to be scanned and purchased. At block 703, at the POS terminal 502, the activation code 210 may be read, such as via the I/O interface(s) 508 or, alternatively, manually input at the POS terminal 502. At block 704, the POS terminal 502 displays the total due for the order. For example, the UPC associated with the pre-printed lottery ticket 100 may be read, for example, to determine price for the draw-type pre-printed lottery ticket 100. At block 705, the purchaser pays the amount due and at block 706, the cashier then accepts the tender and updates the payment into the POS terminal 502.
In an embodiment where the lottery ticket is a virtual draw-type pre-selected lottery ticket 102, the virtual draw-type pre-selected lottery ticket 102 may be purchased by a consumer (e.g., a purchaser), wherein a consumer's electronic device (serving as a point of sale), e.g., consumer's device 200, accesses an electronic marketplace for virtual draw-type pre-selected lottery tickets and wherein the electronic marketplace is accessible via a website, application, or the like. Upon completion of the virtual draw-type pre-selected lottery ticket 102 purchase, the virtual draw-type pre-selected lottery ticket 102 is electronically delivered to the consumer's device 200.
At block 707, the POS terminal 502 generates a transaction request, particularly, an activation request, and communicates the activation request to the lottery system 520. The activation request may also constitute an enrollment request, for example, a request that each the play-selections 120 associated with the draw-type pre-printed lottery ticket 100 being enrolled be entered for a drawing of a lottery. The activation request may comprise, in addition to information uniquely identifying the draw-type pre-printed lottery ticket 100 being purchased, the encrypted control number 130 for the draw-type pre-printed lottery ticket 100 being purchased, information identifying the retailer 501, information identifying the POS terminal 502, information identifying the jurisdiction (e.g., the state) in which the draw-type pre-printed lottery ticket 100 is being purchased, or combinations thereof.
In an embodiment where the lottery ticket is a virtual draw-type pre-selected lottery ticket 102, the consumer's device 200 (e.g., serving as POS terminal 502) generates a transaction request, particularly, an activation request, and communicates the activation request to the lottery system 520. The activation request may also constitute an enrollment request, for example, a request that each the play-selections 120 associated with the virtual draw-type pre-selected lottery ticket 102 being enrolled be entered for a drawing of a lottery. The activation request may comprise, in addition to information uniquely identifying the draw-type pre-selected lottery ticket being purchased, the encrypted control number 130 for the draw-type pre-selected lottery ticket being purchased, information identifying the retailer 501, information identifying the consumer's device 200, information identifying the jurisdiction (e.g., the state) in which the draw-type pre-selected lottery ticket is being purchased, information identifying the geographic location (e.g. GPS coordinates) of the consumer's device 200 which is purchasing the virtual draw-type pre-selected lottery ticket 102, or combinations thereof.
Upon receipt of the activation request, at block 708, the lottery system 520 may access one or more records associated with the draw-type pre-printed lottery ticket 100 referenced in the activation request and determine the validity of the activation request received from the POS terminal 502. In various embodiments, the lottery system 520 may determine the validity of the activation request based upon (i) whether or not the draw-type pre-printed lottery ticket 100 referenced in the activation request has been previously activated or enrolled in a lottery drawing; (ii) whether or not a retailer associated with the draw-type pre-printed lottery ticket 100 referenced in the activation request is consistent with the retailer referenced in the activation request; (iii) whether or not a POS terminal associated with the draw-type pre-printed lottery ticket 100 referenced in the activation request is consistent with the POS terminal 502 referenced in the activation request; (iv) whether or not a jurisdiction associated with the draw-type pre-printed lottery ticket 100 referenced in the activation request is consistent with the jurisdiction referenced in the activation request; (v) whether or not the geographic location of the POS terminal associated with the purchase of the draw-type pre-printed lottery ticket 100 corresponds to a geographic location approved for the sale of the draw-type pre-printed lottery ticket 100, or (vi) combinations thereof.
In an embodiment where the lottery ticket is a virtual draw-type pre-selected lottery ticket 102, upon receipt of the activation request, the lottery system 520 may access one or more records associated with the virtual draw-type pre-selected lottery ticket 102 referenced in the activation request and determine the validity of the activation request received from the consumer's device 200 (serving as the POS terminal 502). In various embodiments, the lottery system 520 may determine the validity of the activation request based upon (i) whether or not the virtual draw-type pre-selected lottery ticket 102 referenced in the activation request has been previously activated or enrolled in a lottery drawing; (ii) whether or not a retailer associated with the virtual draw-type pre-selected lottery ticket 102 referenced in the activation request is consistent with the retailer referenced in the activation request; (iii) whether or not the consumer's device 200 associated with the virtual draw-type pre-selected lottery ticket 102 referenced in the activation request is consistent with the consumer's device 200 referenced in the activation request; (iv) whether or not a jurisdiction associated with the virtual draw-type pre-selected lottery ticket 102 referenced in the activation request is consistent with the jurisdiction referenced in the activation request; (v) whether or not the geographic location of the consumer's device 200 associated with the purchase of the virtual draw-type pre-selected lottery ticket 102 corresponds to a geographic location approved for the sale of the virtual draw-type pre-selected lottery ticket 102, or (vi) combinations thereof.
Upon a determination that the activation request is valid, at block 709, the lottery system 520 may determine the play selections 120 associated with the draw-type pre-printed lottery ticket 100 referenced in the activation request, for example, which may be stored in the one or more records associated with the draw-type pre-printed lottery ticket 100. At block 710, the lottery system 520 may also determine the CGS responsible for administering the lottery for the jurisdiction associated with the draw-type pre-printed lottery ticket 100 (e.g., the first CGS 540a), for example, which may also be stored in the one or more records associated with the draw-type pre-printed lottery ticket 100. At block 711, the lottery system 520 may also interact with the first CGS 540a, via the first API 525a, to enroll the play selections 120 in the next available drawing for the lottery with which the draw-type pre-printed lottery ticket 100 is associated. For instance, the lottery system 520 may employ a “cut-off” time prior which the play selections 120 will be enrolled in a particular drawing and subsequent to which the play selections 120 will be enrolled in a drawing subsequent to that drawing (e.g., the next available drawing).
In an embodiment where the lottery ticket is a virtual draw-type pre-selected lottery ticket 102, upon a determination that the activation request is valid, the lottery system 520 may determine the play selections 120 associated with the virtual draw-type pre-selected lottery ticket 102 referenced in the activation request, for example, which may be stored in the one or more records associated with the virtual draw-type pre-selected lottery ticket 102. The lottery system 520 may also determine the CGS responsible for administering the lottery for the jurisdiction associated with the virtual draw-type pre-selected lottery ticket 102 (e.g., the first CGS 540a), for example, which may also be stored in the one or more records associated with the virtual draw-type pre-selected lottery ticket 102. The lottery system 520 may also interact with the first CGS 540a, via the first API 525a, to enroll the play selections 120 in the next available drawing for the lottery with which the virtual draw-type pre-selected lottery ticket 102 is associated. For instance, the lottery system 520 may employ a “cut-off” time prior which the play selections 120 will be enrolled in a particular drawing and subsequent to which the play selections 120 will be enrolled in a drawing subsequent to that drawing (e.g., the next available drawing).
If the enrollment in the drawing is successful, at block 712, the lottery system 520 may receive an enrollment confirmation from the first CGS 540a, which may include an indication of the drawing (e.g., the date and/or time of the drawing) in which the play selections 120 were enrolled. Alternatively, if the enrollment in the drawing is unsuccessful, the lottery system 520 may either receive an indication from the first CGS 540a that the enrollment was not successful or fail to receive an enrollment confirmation within a predetermined time-period, thus indicating that the enrollment was unsuccessful.
In an embodiment where the lottery ticket is a virtual draw-type pre-selected lottery ticket 102, if the enrollment in the drawing is successful, the lottery system 520 may receive an enrollment confirmation from the first CGS 540a, which may include an indication of the drawing (e.g., the date and/or time of the drawing) in which the play selections 120 were enrolled. Alternatively, if the enrollment in the drawing is unsuccessful, the lottery system 520 may either receive an indication from the first CGS 540a that the enrollment was not successful or fail to receive an enrollment confirmation within a predetermined time-period, thus indicating that the enrollment was unsuccessful.
At block 713, the lottery system 520 may store the enrollment confirmation received from the first CGS 540a in association with one or more of the records associated with the draw-type pre-printed lottery ticket 100, for example, the indication that the play selections 120 have been successfully enrolled and the date and/or time of the drawing.
In an embodiment where the lottery ticket is a virtual draw-type pre-selected lottery ticket 102, the lottery system 520 may store the enrollment confirmation received from the first CGS 540a in association with one or more of the records associated with the virtual draw-type pre-selected lottery ticket 102, for example, the indication that the play selections 120 have been successfully enrolled and the date and/or time of the drawing.
At block 714, if the enrollment in the drawing is successful, the lottery system 520 may communicate an enrollment confirmation to the POS terminal 502, which may include an indication of the drawing (e.g., the date and/or time of the drawing) in which the play selections 120 were enrolled. Alternatively, if the enrollment in the drawing is unsuccessful, the lottery system 520 may either communicate an indication to the POS terminal 502 that the enrollment was not successful or fail to communicate an enrollment confirmation within a predetermined time-period, thus indicating that the enrollment was unsuccessful. If the enrollment is unsuccessful, the funds may be returned to the purchaser and the transaction canceled. In some embodiments, in order to allow for the possibility that an enrollment may be unsuccessful, any store-and-forward functionality of the POS terminal may be disabled.
In an embodiment where the lottery ticket is a virtual draw-type pre-selected lottery ticket 102, if the enrollment in the drawing is successful, the lottery system 520 may communicate an enrollment confirmation to the consumer's device 200 (e.g. serving as the POS 502), which may include an indication of the drawing (e.g., the date and/or time of the drawing) in which the play selections 120 were enrolled. Alternatively, if the enrollment in the drawing is unsuccessful, the lottery system 520 may either communicate an indication to the consumer's device 200 (e.g. serving as the POS 502) that the enrollment was not successful or fail to communicate an enrollment confirmation within a predetermined time-period, thus indicating that the enrollment was unsuccessful. If the enrollment is unsuccessful, the funds may be returned to the consumer and the transaction canceled. In some embodiments, in order to allow for the possibility that an enrollment may be unsuccessful, any store-and-forward functionality of the POS terminal may be disabled.
As disclosed with respect to
As disclosed with respect to
In some embodiments, the purchaser can also verify the draw date information at the same time as enrolling in automatic prize notification. After scanning the quick-response response code (e.g., a QR Code®) and/or texting a unique code to the system (e.g., lottery system 520 and/or central gaming system 540), the system would return the draw date information in a format appropriate to the communication channel selected by the purchaser.
In an embodiment where the lottery ticket is a virtual draw-type pre-selected lottery ticket 102, the consumer can also verify the draw date information at the same time as enrolling in automatic prize notification. After scanning the quick-response response code (e.g., a QR Code®), texting a unique code to the system (e.g., lottery system 520 and/or central gaming system 540), activating a functionality on the consumer's device 200 (e.g., a button and/or a hyperlink) to automatically verify and/or enroll, the system would return the draw date information in a format appropriate for the consumer's device 200.
In some embodiments, the draw-type pre-printed lottery ticket 100 and the numbers associated with the ticket may be configured to be able to be entered into a plurality of draws, e.g., a plurality of subsequent draws with the same lottery authority, and/or a plurality of draws with different lottery authorities. In some embodiments, the ticket may comprise a plurality of quick-response response codes associated with each draw. In some embodiments, the ticket may comprise one quick-response response code (e.g., a QR Code®), wherein the quick-response response code (e.g., a QR Code®) directs the user to a webpage where the user may select the plurality of draws desired and/or may see a display with the plurality of draws indicated. In some embodiments, the plurality of draws may be chosen at the time of purchase of the ticket.
In an embodiment where the lottery ticket is a virtual draw-type pre-selected lottery ticket 102, the numbers associated with the virtual draw-type pre-selected lottery ticket 102 may be configured to be able to be entered into a plurality of draws, e.g., a plurality of subsequent draws with the same lottery authority, and/or a plurality of draws with different lottery authorities. In some embodiments, the virtual draw-type pre-selected lottery ticket 102 may comprise a plurality of quick-response response codes associated with each draw. In some embodiments, the virtual draw-type pre-selected lottery ticket 102 may comprise one quick-response response code (e.g., a QR Code®) or activatable button/hyperlink, wherein the quick-response response code (e.g., a QR Code®) or activatable button/hyperlink directs the user to a webpage where the user may select the plurality of draws desired and/or may see a display with the plurality of draws indicated. In some embodiments, the plurality of draws may be chosen at the time of purchase of the virtual draw-type pre-selected lottery ticket 102.
In some embodiments, lottery tickets may not have the draw date printed on the ticket or receipt, but rather, consumers are informed that they are entered into a “next possible draw date.” The consumers then have the ability to verify their ticket's particular draw date through a variety of methods. For example, a consumer could visit a website, enter a unique ticket identifier, and then the website would display the draw date information. In addition to websites, consumers could text a unique ticket identifier to a short code and receive back via text the draw information, or the consumers could phone an interactive voice response (IVR) system and speak the unique ticket identifier and have the IVR speak the draw date information. In some embodiments, the consumer could scan a quick-response response code (e.g., a QR Code®) on the lottery ticket to verify the draw date.
A consumer who purchases a lottery ticket and then uses one of these methods to validate a draw date may typically receive back the draw date information. If a user attempts to use one of the methods to validate draw date information, but hasn't purchased that particular lottery ticket, the system might return a message that indicates the lottery ticket hasn't been purchased or some other similar type of response. A bad actor could discern differences in responses between purchased and activated lottery tickets and lottery tickets that have never been purchased.
If a bad actor was interested in committing fraud, such as attempting to counterfeit a lottery ticket, the bad actor might be advantaged if they had knowledge of which lottery tickets have been purchased or not purchased. This is particularly true if the bad actor uses a computer system to automate the process of entering a unique ticket identifier to the system, and then receiving back the system's response confirming draw date and/or if the ticket has been purchased.
Embodiments of the disclosure may prevent or reduce the possibility of a bad actor gathering information about lottery tickets in this way. In some embodiments, a system may comprise a user interface that allows a consumer to enter a unique identifier, e.g. control number 130 or 360, into the system. This user interface is then connected to a database that references the Ticket Draw Date information. In some embodiments, the system may comprise a consumer response system and/or a fraud mitigation system.
In some embodiments, a fraud mitigation system may employ different tools and methods to prevent bad actors from obtaining lottery ticket information. In some embodiments, the fraud mitigation system may comprise one or more fields that are invisible to humans, but visible to automated systems such as bots. Additionally or alternatively, the system could then not return any response where one of these invisible fields is filled in. The fraud mitigation system may comprise captchas. Additionally or alternatively, the fraud mitigation system may comprise human friendly, bot un-friendly questions. The fraud mitigation system may comprise Use Session Tokens that are applied at the site level and required by the user interface in the case of web bases user interfaces.
In various embodiments, some or all of the information outlined above may be stored in a database of the lottery system 520, central gaming system 540, or combinations thereof, which could include a unique lottery ticket identifier, the desired communication channel (such as text, email, voice, or some other communication channel), along with the communication channel unique identifier (such as a mobile phone number, email, etc.).
After the drawing takes place, the lottery system 520 receives the winning attributes from the CGS 540, or from an internal table in the case where this embodiment is offered by CGS 540. The lottery system 520 may provide a notification comprising the winning attributes to the user, for example, via a desired communication channel.
In some embodiments, the lottery system 520 matches winning and losing ticket numbers and associates them with tickets that have been purchased. The unique identifier of the tickets may then be used to identify associated communication channel identifiers for users. The lottery system 520 may receive information about the draw outcome, including whether or not a specific ticket is a winner, and if a winner, the amount won, prize redemption instructions, and expiration date of the winning ticket. Additionally, the lottery system 520 may identify the desired communication channel and the communication identifier associated with the ticket.
Next, the lottery system 520 utilizes a communication module 550, which is integrated with other systems capable of storing information and transmitting information according to the desired communication method (in some embodiments the communication module may reside within lottery system 520 and in other embodiments the communication module 550 may be communicatively coupled to lottery system 520 but not necessarily residing within lottery system 520). The user then receives notification informing them that their ticket wasn't a winner, or it was a winner, the amount won and prize redemption instructions.
In some embodiments, the lottery system 520 may be configured to also provide the user with an option to be notified of a winning lottery ticket and/or to claim a prize associated with the ticket. For example, the user may be prompted as to whether or not the user wishes to be notified as to whether or not the ticket is a winning ticket. In some embodiments where the ticket is determined to have a redeemable value (e.g., by virtue of the ticket being a winning ticket), the lottery system 520 may provide the user with options to redeem the lottery ticket, which may depend upon the amount and nature of the redeemable value. For example, the lottery system 520 could generate a stored-value card containing the prize amount associated with the ticket and cause the stored-value card to be delivered to the user electronically or by mail; alternatively, the lottery system 520 could cause a stored-value account to be added to the user's electronic wallet; alternatively, the lottery system 520 could direct the user to an authorized physical location (e.g., a lottery office) to redeem the lottery ticket (for example, if the redemption value exceeds a winnings threshold). Additionally or alternatively, the lottery system 520 could present the user with the option to redeem the winnings in the form of additional lottery tickets (e.g., which may be presented virtually to the user) for play in a future lottery game.
Referring to
In the embodiment of
At block 1001, the purchaser picks up an embodiment of the disclosure (e.g. a ticket) in a retail location such as a grocery store. At block 1002, the purchaser proceeds to POS terminal 502 and presents the instant-win-type pre-printed lottery ticket 300 to the cashier to be scanned and purchased. At block 1003, at the POS terminal 502, may be read, such as via the I/O interface(s) 508 or, alternatively, manually input at the POS terminal 502. As similarly disclosed with respect to one or more previously-disclosed methods, at block 1004, the POS terminal 502 displays the total due for the order; at block 1005, the purchaser pays the amount due; and, at block 1006, the cashier then accepts the tender and updates the payment into the POS terminal 502.
In an embodiment where the lottery ticket is a virtual instant-win-type pre-selected lottery ticket 302, the virtual instant-win-type pre-selected lottery ticket 302 may be purchased by a consumer (e.g., a purchaser), wherein a consumer's device 200 (serving as a point of sale) accesses an electronic marketplace for virtual instant-win-type pre-selected lottery tickets and wherein the electronic marketplace is accessible via a website, application, or the like. Upon completion of the virtual instant-win-type pre-selected lottery ticket 302 purchase, the virtual instant-win-type pre-selected lottery ticket 302 is electronically delivered to the consumer's device 200.
At block 1007, the POS terminal 502 generates a transaction request, particularly, an activation request, and communicates the activation request to the lottery system 520. The activation request may also constitute a request to update the status of the unique ticket number to an active or purchased state. The activation request may comprise, in addition to information uniquely identifying the draw-type pre-printed lottery ticket 100 being purchased, information identifying the retailer 501, information identifying the POS terminal 502, information identifying the jurisdiction (e.g., the state) in which the instant-win-type pre-printed lottery ticket 300 is being purchased, or combinations thereof.
In an embodiment where the lottery ticket is a virtual instant-win-type pre-selected lottery ticket 302, the consumer's device 200 (e.g., serving as POS terminal 502) generates a transaction request, particularly, an activation request, and communicates the activation request to the lottery system 520. The activation request may also constitute a request to update the status of the unique ticket number to an active or purchased state. The activation request may comprise, in addition to information uniquely identifying the draw-type pre-printed lottery ticket 100 being purchased, information identifying the retailer 501, information identifying the consumer's device 200, information identifying the jurisdiction (e.g., the state) in which the instant-win-type pre-printed lottery ticket 300 is being purchased, information identifying the geographic location (e.g. GPS coordinates) of the consumer's device 200 which is purchasing the virtual instant-win-type pre-selected lottery ticket 302, or combinations thereof.
Upon receipt of the activation request, the lottery system 520 may access one or more records associated with the instant-win-type pre-printed lottery ticket 300 referenced in the activation request and determine the validity of the activation request received from the POS terminal 502. In various embodiments, the lottery system 520 may determine the validity of the activation request based upon (i) whether or not the instant-win-type pre-printed lottery ticket 300 referenced in the activation request has been previously activated or redeemed in a lottery drawing; (ii) whether or not a retailer associated with the instant-win-type pre-printed lottery ticket 300 referenced in the activation request is consistent with the retailer referenced in the activation request; (iii) whether or not a POS terminal associated with the instant-win-type pre-printed lottery ticket 300 referenced in the activation request is consistent with the POS terminal 502 referenced in the activation request; (iv) whether or not a jurisdiction associated with the instant-win-type pre-printed lottery ticket 300 referenced in the activation request is consistent with the jurisdiction referenced in the activation request; (v) whether or not the geographic location of the POS terminal 502 associated with the purchase of the instant-win-type pre-printed lottery ticket 300 corresponds to a geographic location approved for the sale of the instant-win-type pre-printed lottery ticket 300; or (v) combinations thereof.
In an embodiment where the lottery ticket is a virtual instant-win-type pre-selected lottery ticket 302, upon receipt of the activation request, the lottery system 520 may access one or more records associated with the virtual instant-win-type pre-selected lottery ticket 302 referenced in the activation request and determine the validity of the activation request received from the consumer's device 200. In various embodiments, the lottery system 520 may determine the validity of the activation request based upon (i) whether or not the virtual instant-win-type pre-selected lottery ticket 302 referenced in the activation request has been previously activated or redeemed in a lottery drawing; (ii) whether or not a retailer associated with the virtual instant-win-type pre-selected lottery ticket 302 referenced in the activation request is consistent with the retailer referenced in the activation request; (iii) whether or not the consumer's device 200 associated with the virtual instant-win-type pre-selected lottery ticket 302 referenced in the activation request is consistent with the consumer's device 200 referenced in the activation request; (iv) whether or not a jurisdiction associated with the virtual instant-win-type pre-selected lottery ticket 302 referenced in the activation request is consistent with the jurisdiction referenced in the activation request; (v) whether or not the geographic location of the consumer's device 200 associated with the purchase of the virtual instant-win-type pre-selected lottery ticket 302 corresponds to a geographic location approved for the sale of the virtual instant-win-type pre-selected lottery ticket 302, or (vi) combinations thereof.
Upon a determination that the activation request is valid, at block 1008, the lottery system 520 responds to the POS terminal 502 with a response to the request indicating success or failure. If successful the purchase transaction is complete. If unsuccessful, the POS terminal may indicate the failure and the funds tendered by the purchaser may be returned.
In an embodiment where the lottery ticket is a virtual instant-win-type pre-selected lottery ticket 302, upon a determination that the activation request is valid, at block 1008, the lottery system 520 responds to the consumer's device 200 with a response to the request indicating success or failure. If success the purchase transaction is complete. If unsuccessful, the consumer's device 200 may indicate the failure and the funds tendered by the purchaser may be returned.
At block 1009, the purchaser may wish to play the instant-win-type pre-printed lottery ticket 300. The purchaser may remove the covering obscuring the “Your Winning Data” section 320, revealing a message instructing purchaser to send the ticket play-code to a short code for SMS (alternatively, some other node identifier in the case of another communication scheme). The play-code, which may be unique and specific to the instant-win-type pre-printed lottery ticket 300, will be associated with the instant-win-type pre-printed lottery ticket 300 and the unique number by the lottery system 520. The purchaser may also remove the covering obscuring the “Your Data” section 330, revealing the game attributes 332 (e.g., a second set of attributes). At block 1010 communication module 550 receives the SMS or other communication protocol containing the play-code for the instant-win-type pre-printed lottery ticket 300 and, at block 1011, forwards the play-code to the lottery system 520.
In an embodiment where the lottery ticket is a virtual instant-win-type pre-selected lottery ticket 302, the consumer may wish to play the virtual instant-win-type pre-selected lottery ticket 302. The consumer's device 200 may display a “Your Winning Data” section 320, revealing a message instructing consumer to send the ticket play-code to a short code for SMS (alternatively, some other node identifier in the case of another communication scheme) or activate a functionality displayed on consumer's device 200 (e.g., a button and/or a hyperlink) to send the ticket play-code. The play-code, which may be unique and specific to the virtual instant-win-type pre-selected lottery ticket 302, will be associated with the virtual instant-win-type pre-selected lottery ticket 302 at the unique number by the lottery system 520. The consumer's device 200 may also display a “Your Data” section 330, revealing the game attributes 332. At block 1010 communication module 550 receives the SMS or other communication protocol containing the play-code for the virtual instant-win-type pre-selected lottery ticket 302 and, at block 1011, forwards the play-code to the lottery system 520.
At block 1012, the play-code is received by the lottery system 520. If the records for the instant-win-type pre-printed lottery card 300 indicate that the ticket has been purchased and is active, the lottery system 520 may determine the CGS responsible for administering the lottery for the jurisdiction associated with the instant-win-type pre-printed lottery ticket 300 (e.g., the second CGS 540b), and, at block 1013, will communicate an enrollment request to the CGS 540a. If the records for the instant-win-type pre-printed lottery card 300 do not indicate that the ticket has been purchased and is active (e.g., that the ticket has not been purchased and remains inactive), the lottery system 520 may return a message, via the communication module 550, to the player's device indicating that the ticket is not able to be played (e.g., “Sorry, this ticket can't be played.”).
In an embodiment where the lottery ticket is a virtual instant-win-type pre-selected lottery ticket 302, at block 1012, the play-code is received by the lottery system 520. If the records for the virtual instant-win-type pre-selected lottery ticket 302 indicate that the ticket has been purchased and is active, the lottery system 520 may determine the CGS responsible for administering the lottery for the jurisdiction associated with the virtual instant-win-type pre-selected lottery ticket 302 (e.g., the second CGS 540b), and, at block 1013, will communicate an enrollment request to the CGS 540a. If the records for the virtual instant-win-type pre-selected lottery ticket 302 do not indicate that the ticket has been purchased and is active (e.g., that the ticket has not been purchased and remains inactive), the lottery system 520 may return a message, via the communication module 550, to the consumer's device 200 indicating that the ticket is not able to be played (e.g., “Sorry, this ticket can't be played.”).
At block 1014, the second CGS 540b enrolls the ticket and returns the payload (e.g., attributes) for the “Your Winning Data” (e.g., a first set of attributes) to the lottery system 520. At block 1015, the lottery system 520 routes the “Your Winning Data” (e.g., a first set of attributes) to the communication module 550 and, at block 1016, the communication module 550 sends the “Your Winning Data” to purchaser's mobile phone or other device, e.g., consumer's device 200, as shown in
In an embodiment where the lottery ticket is a virtual instant-win-type pre-selected lottery ticket 302, at block 1014, the second CGS 540b enrolls the virtual instant-win-type pre-selected lottery ticket 302 and returns the payload (e.g., attributes) for the “Your Winning Data” (e.g., a first set of attributes) to the lottery system 520. At block 1015, the lottery system 520 routes the “Your Winning Data” to the communication module 550 and, at block 1016, the communication module 550 sends the “Your Winning Data” to the consumer's device 200. At block 1017, the consumer's device 200 displays the “Your Winning Data” (e.g., a first set of attributes) and compares the “Your Winning Data” (e.g., a first set of attributes) with the “Your Data” (e.g., a second set of attributes 332) associated with the virtual instant-win-type pre-selected lottery ticket 302 to determine if any matches occur and evaluate what prizes may be paid based on the results, as shown in
Referring to
Referring to
In some embodiments, the instant ticket (i.e., the instant scratch-off lottery ticket and/or the chit) may comprise a quick-response response code (e.g., a QR Code®) (for example, on the back side of the instant ticket), where the quick-response response code (e.g., a QR Code®) may be used to deliver the winning numbers to the user, for the user to identify a match. For example, a user may purchase the instant ticket with a quick-response response code (e.g., a QR Code®) on the back, the instant ticket may be activated by purchase (as described above), the user may scratch the front of the ticket to reveal their selection, and then the user may scan the quick-response response code (e.g., a QR Code®) (for example, with a mobile device, and/or a scanner within the store, possibly near the POS 502 or at the in-lane dispenser machine 1220) to reveal the winning numbers associated with that instant ticket. The user may match these winning number revealed by scanning the quick-response response code (e.g., a QR Code®) with the scratched numbers on the front of the ticket to determine a win.
A method of the disclosure may comprise triggering, by the POS 1210, the in-lane dispenser 1220 to dispense an instant ticket 100 or 300. The barcode (which may be a 128 barcode) provided on the chit 1100 handed to the clerk will signal to the transaction processor 1240 for notification. The transaction processor 1240 may then capture the store ID, lane ID, and UPC of the chit 1100 and may send the transaction details (API call) to the lottery ticket distributor system 1230. The lottery ticket distributor system 1230 locates the wi-fi server 1250 for the store ID provided by the transaction processor 1240, finds the in-lane dispenser machine 1220 located at the lane ID, and dispenses the requested instant lottery ticket 100 or 300 by UPC.
The disclosed systems and methods may drive incremental lottery spending by virtue of being in-lane, and in the sight of the customer when they are checking out at the retail store. The disclosed embodiments may address deficiencies of consumer lottery purchase experience in grocery channels.
In some embodiments disclosed herein are various devices, for example, a chit such as a stored-value lottery card, that may be configured to allow entry into one or more lotteries upon the fulfillment of one or more user-defined criteria. For example, in some embodiments a device configurable to allow entry into a lottery upon the fulfillment of one or more user-defined criteria is a User-Configurable Subscription Lottery (UCSL) device.
The various embodiments of the UCSL devices disclosed herein may be made available throughout a retail store without risk of loss from fraudulent redemption or shrinkage, such retail store could be a brick and mortar, physical establishment or an online and/or virtual location. Generally, the UCSL devices disclosed herein can be displayed openly, for example, throughout a retail establishment, in that the UCSL device are displayed in an inactive state. Additionally, the disclosed UCSL devices can be made to closely resemble a traditional paper lottery ticket so as to foster consumer recognition, trial, and confidence.
It will be appreciated that in some contexts, a purchaser of a UCSL device may not ultimately be the person who “plays” or “uses” the device; conversely, a purchaser of a device may be a player or user of a device (though not necessarily). Thus, references throughout this disclosure to one or more of a “purchaser,” “consumer,” “user,” or “player” are not intended to be limiting and should be interpreted as synonymous except where explicitly or contextually so limited.
In some embodiments, the UCSL device is configured similarly to a stored-value card. Referring to
In the embodiment of
For example, in the embodiment of
In the embodiment of
Also in the embodiment of
Also, in the embodiment of
In some embodiments, the stored-value lottery card 1300 may include a covering 1306 configured to obscure various of the information on the stored-value lottery card 1300, until removed. In various embodiments, the covering 1306 may be a continuous layer disposed over a given portion of the card or discontinuous and disposed over multiple portions of the card. The covering 1306 may include a material that may be suitably removed by a purchaser, such as a scratch-off material, an example of which may include, but is not limited to a latex film. The scratch-of material may obscure various information (e.g., the play-selections) from observation by both the UCSL stored-value lottery card 1300 distributor (e.g., a retailer) and the UCSL stored-value lottery card 1300 purchaser until after the UCSL stored-value lottery card 1300 has been sold. In some embodiments, the enrollment security code 1330 may be obscured by the covering 1306, prior to the covering 1306 being removed (e.g., prior to being “scratched-off”).
Also, in the embodiment of
Also, in some embodiments the stored-value lottery card 1300 may include redemption information. For example, in the embodiment of
Also in the embodiment of
In various embodiments, as shown in
In an embodiment, the UCSL stored-value lottery card 1300 may be embodied as an electronic stored-value card which may be purchased, activated, and loaded into a user's electronic wallet 1775 via the scanning and/or interpretation of purchase and activation indicia (e.g., 1403 and 1410) at a point of sale 1702 and identification of the UCSL stored-value lottery card 1300 by the user for placement of the UCSL stored-value lottery card 1300 into the user's electronic wallet 1775.
Also, in some embodiments the UCSL device is configured similarly to a pre-printed lottery ticket. Referring to
In the embodiment of
Also, in the embodiment of
In the embodiment of
Each of the play-selections 1520 includes a plurality of game attributes 1522 and each attribute 1522 may include, for example, a number, a letter, a symbol, or an illustration. The attributes 1522 may be randomly selected. The attributes 1522 for the play-selection may be generated using, for example, a Random Number Generator (RNG).
In various embodiments, as shown in
In an alternative embodiment, the pre-printed lottery ticket 1500 may be configured for play in a Mega Millions® lottery game. In an embodiment where the pre-printed lottery ticket 1500 configured for play in a Mega Millions® lottery game, each play-selection 1520 may include six attributes 1522, particularly, a first, second, third, fourth, fifth, and sixth attribute 1522. Each of the first, second, third, fourth, and fifth attributes 1522 may be a number selected from seventy (70) possibilities and the sixth attribute 1522 may be a number independently selected from twenty-five (25) possibilities.
In some embodiments, the play-selections may be obscured by a virtual covering, for example, which may also be disposed over a given play-selection 1520 or two or more play-selections or disposed over a given attribute 1522 or two more attributes 1522.
Also, in some embodiments the pre-printed lottery ticket 1500 may include redemption information. For example, in the embodiment of
Also, and as similarly disclosed with respect to
In an embodiment, the UCSL pre-printed lottery ticket 1500 may be embodied as an electronic/virtual lottery ticket which may be purchased, activated, and loaded into a user's electronic wallet 1775 via the scanning and/or interpretation of purchase and activation indicia (e.g., 1603 and 1610) at a point of sale 1702 and identification of the UCSL pre-printed lottery ticket 1500 by the user for placement of the UCSL pre-printed lottery ticket 1500 into the user's electronic wallet 1775.
Also disclosed herein are embodiments related to a system for processing a UCSL device, such as the stored-value lottery card 1300 of
In some embodiments, the POS terminals 1702 disposed at the retailer 1701 may include a processing unit 1704, memory unit 1706 and I/O interface(s) 1708 for communicating with devices external to the POS terminal 1702. Additionally or alternatively, while the embodiment of
In some embodiments, the processing unit 1704 can comprise an electronic input device, a register or terminal, a computer processing unit (“CPU”), a personal computer, a personal digital assistant (e.g., smart phone), or other means of communicating with the I/O interface(s) 1708. In some embodiments, the processing unit 1704 may incorporate a “store-and-forward” functionality. Generally, the store-and-forward functionality may operate during activation of a stored-value card such that, if connectivity between the POS terminal 1702 and a stored-value processing system is lost during activation of the stored-value card, the processing unit 1704 will store the activation request for the stored-value card and communicate the activation request when connectivity is regained, thus allowing the activation to go forward. In some embodiments, the processing unit 1704 may be configured to allow the store-and-forward functionality to be disabled or suppressed.
The I/O interface(s) 1708 generally comprises one or more interpretation units such as a bar code scanner, magnetic strip reader, optical character recognition device, biometric recognition device, numerical keyboard (e.g., for entering an identification number), or other device configured to interrogate, interpret, capture, or input the data encoded in or on the authentication token. For example, the I/O interface(s) 1708 may comprise a barcode scanner for scanning and/or retrieving machine-readable (e.g., barcode information, such as Universal Product Code information or other information) disposed on a ticket. In some embodiments, the POS terminal 1702 may also be connected to a printer 1712, for example, for printing a receipt 114 of the transaction. The POS terminal 1702 includes instructions 1714 stored in the memory unit 1706, which when executed by the processor unit 1704, cause the POS terminal 1702 to provide certain functionality, as disclosed herein.
In the embodiment, the lottery system 1720 generally includes a processing unit 1722, one or more memory units 1724, and one or more I/O interface(s) 1726 for communicating with components external to the lottery system 1720, a communications module 1750 capable of storing information and transmitting information according to the desired communication method (in some embodiments the communication module may reside within lottery system 1720 and in other embodiments the communication module 1750 may be communicatively coupled to lottery system 1720 but not necessarily residing within lottery system 1720), and one or more application programming interfaces (APIs) (e.g., 1725a, 1725b, and 1725c) that are each configured to allow the lottery system 1720 to interface and/or interact with a particular central gaming systems (e.g., 1740a, 1740b, 1740c). The memory unit(s) 1724 may store (i) instructions that when executed by the processing unit, cause the lottery system 1720 to provide certain functionality and/or (ii) user accounts 1770 and associated data, as disclosed herein.
In some embodiments, the lottery system 1720 may be configured for communication with one or more information datastores 1730, for example, which may individually or collectively include an entry for each of the UCSL devices offered for sale the retailer 1701 or multiple similar retailers.
Also, in some embodiments, the lottery system 1720 may be configured for communication with at least one CGS (e.g., at least one of 1740a, 1740b, and 1740c). Generally, lottery jurisdictions (e.g., a states) use various CGSs to manage the drawings associated with a lottery. In various embodiments, the lottery system 1720 is configured to utilize one or more application programming interfaces (APIs) that are each configured to allow the lottery system 1720 to interface and/or interact with a particular CGS (e.g., 1740a, 1740b, 1740c). For example, in the embodiment of
Also, in some embodiments, the lottery system 1720 may be configured to provide a user-portal 1760, for example, by which a user (e.g., a purchaser, a player, and a lottery-card/ticket holder) may access certain functionality (e.g., subscription plan attributes, designations, and selections), as will be discussed herein. In various embodiments, the user-portal 1760 may comprise a webpage, an application (such “app” residing on a user device such as a smart-phone), or an IVR, all of which provide access to the subscription plan 1705.
Also disclosed herein are embodiments of methods related to processing a transaction with respect to a UCSL device, for example, the stored-value lottery card 1300 of
Referring to
In the embodiment of
At block 1801, the method 1800 begins when a purchaser selects the UCSL device (e.g., a stored-value lottery card 1300 or a pre-printed lottery ticket 1500), which may be displayed at the retailer 1701 and, at block 1802, the purchaser proceeds to the POS terminal 1702 and presents the UCSL device to the cashier to be scanned and purchased. At block 1803, at the POS terminal 1702, the activation code (e.g., activation code 1410 or activation code 1610) may be read, such as via the I/O interface(s) 1708 or, alternatively, manually input at the POS terminal 1702. At block 1804, the POS terminal 1702 displays the total due for the order. For example, the UPC associated with the UCSL device may be read, for example, to determine price for the UCSL device. At block 1805, the purchaser pays the amount due and at block 1806, the cashier then accepts the tender and updates the payment into the POS terminal 1702.
At block 1807, the POS terminal 1702 generates a transaction request, particularly, an activation request, and communicates the activation request to the lottery system 1720. The activation request may comprise, in addition to information uniquely identifying the UCSL device being purchased (e.g., activation code 1410 or activation code 1610), information identifying the retailer 1701, information identifying the POS terminal 1702, information identifying the jurisdiction (e.g., the state) in which the UCSL device is being purchased, or combinations thereof.
Upon receipt of the activation request, at block 1808, the lottery system 1720 may access one or more records associated with the UCSL device referenced in the activation request and determine the validity of the activation request received from the POS terminal 1702. In various embodiments, the lottery system 1720 may determine the validity of the activation request based upon (i) whether or not the UCSL device referenced in the activation request has been previously activated; (ii) whether or not a retailer associated with the UCSL device referenced in the activation request is consistent with the retailer referenced in the activation request; (iii) whether or not a POS terminal associated with the UCSL device referenced in the activation request is consistent with the POS terminal 1702 referenced in the activation request; (iv) whether or not a jurisdiction associated with the UCSL device referenced in the activation request is consistent with the jurisdiction referenced in the activation request; (v) whether or not the geographic location of the POS terminal associated with the purchase of the UCSL device corresponds to a geographic location approved for the sale of the UCSL device, or (vi) combinations thereof.
Upon a determination that the activation request is valid, at block 1809, the lottery system 1720 updates one or more records associated with the UCSL device referenced in the activation request to indicate that the UCSL device has been validly purchased and is active and, at block 1810, responds to the POS terminal 1702 with a response to the request indicating success or failure of the activation. If successful, the purchase transaction is complete. If unsuccessful, the POS terminal may indicate the failure and the funds tendered by the purchaser may be returned.
Following a successful purchase transaction, the purchaser may use a UCSL device to enroll in a user-configurable lottery subscription.
At block 1811, the purchaser may utilize the enrollment indicia (e.g., enrollment indicia 1420 or 1625) to access the user-configurable lottery subscription plan 1705 via the user-portal 1760. For example, where the enrollment indicia utilized is a QR® code, when the QR® code is scanned by a user using a mobile device capable of scanning a QR® code, the user's device would be directed to the user-configurable lottery subscription via the user-portal 1760 (e.g., a particular web-site or other network endpoint). Alternatively, where the enrollment indicia utilized is a SMS number, URL address, or phone-number, the user would similarly utilize the enrollment indicia the access the user-configurable lottery subscription plan 1705 via the user-portal 1760, such as via a website, IVR, or SMS.
In some embodiments, at block 1812, security information associated with the UCSL device is provided to the user-configurable lottery subscription. For example, upon accessing the user-configurable lottery subscription plan 1705, the user-configurable lottery subscription plan 1705 may then prompt the user to remove the covering obscuring the enrollment security code (1330 or 1630) and to enter the enrollment security code (1330 or 1630), such as in embodiments where the user-configurable lottery subscription plan 1705 was accessed by scanning a QR® code, typing in a URL, dialing a phone-number, or transmitting an SMS message. In embodiments where the user-configurable lottery subscription plan 1705 was accessed by scanning a QR® code, security information may have been encoded in the QR® code and there may be no need to enter security code (1330 or 1630).
As shown in
At block 1814, for example, where the user may be required (e.g., in accordance with gaming laws) to configure the lottery subscription plan criteria (1901-1910) only in a certain state (for example the state in which the UCSL device was purchased), the lottery system 1720 may utilize a geolocation service to determine if the user is accessing the user portal 1760 from the correct state to allow the system to be configured, and if not, would display an error message explaining why the USCLE could not be configured at that time. The lottery system 1720 may also prompt the user to enter their full name and/or contact information, for purposes of complying with lottery rules.
At block 1815, the user-configurable lottery subscription plan 1705 presents the user with options allowing the user to configure one or more lottery-play criteria and stores the user configurations in a designated criteria database 1900, for example, in association with the UCSL device. Generally, the lottery-play criteria relate to the way in which a user participates a lottery. For example, the lottery-play criteria may be configured to cause a user to participate in a lottery based upon the satisfaction of various criteria. In some embodiments, the particular lottery-play criteria that may be configured may be dependent upon the configuration of the UCSL device.
Similarly, where the UCSL device comprises the pre-printed lottery ticket 1500, examples of lottery-play criteria may include:
At block 1816, the user-configurable lottery subscription plan 1705 may prompt the user to create an account 1770, for example, which would allow the user to access their settings in the future, which would allow the user to access the configuration screen following the initial set-up, if the user desires to modify a previous setting. For example, the account 1770 could allow a user to link its UCSL stored-value lottery card 1300 and/or UCSL pre-printed lottery ticket 1500 to another payment account, which in turn could be utilized to keep the user's UCSL stored-value lottery card 1300 and/or UCSL pre-printed lottery ticket 1500 funded, e.g., if the user's UCSL stored-value lottery card 1300 was initially purchased with $50.00 worth of game plays, the account 1770 could be configured to reload the UCSL stored-value lottery card 1300 to its original level whenever the value of the UCSL stored-value lottery card 1300 was reduced to a pre-selected amount, e.g., $5.00. Alternatively, if the user's UCSL pre-printed lottery ticket 1500 was initially purchased with $50.00 worth of game plays, the account 1770 could be configured to reauthorize the UCSL pre-printed lottery ticket 1500 for its original amount whenever the UCSL pre-printed lottery ticket 1500 is entered into a drawing by requesting that the account 1770 initiate the appropriate funds transfer to the appropriate funds recipient and notify the system 1720 that a funds transfer sufficient to increase the value of UCSL pre-printed lottery ticket 1500 back to its original amount has been initiated. The account 1770 could be created by entering an email address and password.
At block 1817, the user-configurable lottery subscription plan 1705 may prompt the user to confirm their desired subscription settings, the lottery system 1720 stores the subscription settings, and the lottery system 1720 may send a confirmation email to the user, indicating the configuration settings.
Following a successful enrollment in the user-configurable lottery subscription, the user may be entered in one or more lotteries.
At block 1818, at a specified time or interval prior to any drawing, the lottery system 1720 would receive information related to the upcoming drawings (e.g., jackpot size) for all relevant lottery draws via an API or such other service. At block 1819, the lottery system 1720 would determine which users should be entered into the upcoming drawing, based upon the received information. For example, the lottery system 1720 may compare the lottery-play criteria for each user-configurable lottery subscription plan 1705 with the information pertaining to the upcoming drawing. If the lottery system 1720 determines that all of the criteria set by a user are predicted to be fulfilled by the upcoming drawing, the lottery system 1720 will determine that the user should be entered in the upcoming drawing.
If the lottery system 1720 determines that the user should be entered in the upcoming drawing, the lottery system 1720 will cause the user to be entered into the drawing, at block 1820.
In one embodiment, the lottery system 1720 may interact with the relevant CGS, such as via an API or some other similar method, to cause the user's game selections to be entered into the next drawing, and the corresponding confirmation would be stored by the system. For example, the lottery system 1720 will determine the play selections associated with the user's enrollment, for example, which may be stored in the one or more records associated with the user enrollment and/or the UCSL device. In embodiments where the UCSL device is a stored-value lottery card 1300, the user may have selected their own play selections. Alternatively, where the UCSL device is a pre-printed lottery ticket 1500, the play selection will be one or more of the play selections 1520 included on the pre-printed lottery ticket 1500. The lottery system 1720 may also determine the CGS responsible for administering the lottery for the jurisdiction associated with the user's enrollment (e.g., the first CGS 1740a), for example, which may also be stored in the one or more records associated with the user's enrollment. The lottery system 1720 may also interact with the first CGS 1740a, via the first API 1725a, to enroll the play selections in the drawing for the lottery.
If the entry in the drawing is successful, the lottery system 1720 may receive an entry confirmation from the first CGS 1740a, which may include an indication of the drawing (e.g., the date and/or time of the drawing) in which the play selections were entered. Alternatively, if the entry in the drawing is unsuccessful, the lottery system 1720 may either receive an indication from the first CGS 1740a that the entry was not successful or fail to receive an entry confirmation within a predetermined time-period, thus indicating that the entry was unsuccessful. The lottery system 1720 may store the entry confirmation received from the first CGS 1740a.
If the entry in the drawing is successful, the lottery system 1720 may create a graphical representation of a lottery ticket—including the name of the game, the numbers and other ticket information including the date, the estimated jackpot size and any other relevant draw information—and communicate (e.g., by email other digital communication, such as SMS) the graphical representation of the ticket to the user, as a confirmation of the entry.
In another embodiment, the lottery system 1720 may interact with a lottery retailer, such as via an API or some other similar method, to obtain a lottery ticket meeting the user's game selections. For example, upon determining that certain play selections should be entered into an upcoming drawing, the lottery system 1720 may cause a ticket to be purchased from a lottery terminal within an authorized lottery retailer's premises. The resulting ticket that would be printed from the terminal, for example, on traditional lottery ticket stock, and would be identical in all respects, except for the particular draw information, to any other lottery ticket printed within that lottery jurisdiction, for that lottery game. The ticket would then be scanned or mimicked, and an image or other identifier of the ticket would be delivered to the user. The actual paper ticket would be kept in a secure (e.g., restricted, authorized-access, waterproof, and/or fireproof) location by the retailer or another party authorized to secure and retain the paper ticket (e.g., an authorized courier). In such an embodiment, shortly after the lottery drawing, the system 1720 would determine any winning tickets and would notify users of this invention of a win. Low-tier prizes (under $600) could be paid out electronically, such as a via closed loop gift card, an open loop gift card, transfer of funds to a PayPal® or Venmo® account, or a credit to any existing debit or credit previously identified by the owner of the winning ticket. In the event of a high-tier win (or if so desired by the user/owner of the ticket for a low-tier prize win), the user's/owner's actual ticket which had been retained by the retailer or authorized courier would be delivered to the user via secure messenger (or the user/owner could be notified so that the user/owner could retrieve the actual paper ticket at the location of the retailer or authorized courier). Upon receipt of the actual physical ticket by the user/owner, the user/owner could then present, in person, the actual physical ticket for redemption/prize collection at the appropriate redemption authority's location.
Following entry into one or more lotteries, the user can receive notifications and winnings as specified in the user-configurable lottery subscription.
For example, at block 1821, the lottery system 1720 may determine if the user's entry in the drawing constitutes a winning entry. For example, shortly after the drawing for that particular game, the lottery system 1720 would receive information from the relevant CGS indicating the winning entries, and the lottery system 1720 would make a determination if any of the users had winning entries. The lottery system 1720 may provide a notification comprising the winning attributes to the user, for example, via a desired communication channel, as specified by the user.
In some embodiments, the lottery system 1720 may be configured to also provide the user with an option to claim a prize associated with the ticket. For example, the user may be prompted as to whether or not the user wishes to be notified as to whether or not the ticket is a winning ticket. In some embodiments where the ticket is determined to have a redeemable value (e.g., by virtue of the ticket being a winning ticket), the lottery system 1720 may provide the user with options to redeem the lottery ticket, which may depend upon the amount and nature of the redeemable value.
In an embodiment, if the ticket was a low-tier winner, it would be paid out electronically according to the payout instructions the user had created in the configuration table. For example, the lottery system 1720 could generate a stored-value card containing the prize amount associated with the ticket, where the stored-value card could be delivered to the user electronically or by mail. Alternatively, the lottery system 1720 could add a stored-value account to the user's electronic wallet 1775; alternatively, the lottery system 1720 could direct the user to an authorized physical location (e.g., a lottery office) to redeem the lottery ticket (for example, if the redemption value exceeds a winnings threshold). Additionally or alternatively, the lottery system 1720 could present the user with the option to redeem the winnings in the form of additional lottery tickets (e.g., which may be presented virtually to the user) for play in a future lottery game. Additionally or alternatively, the lottery system 1720 could pay out the low-tier winning amount via a credit to an existing debit card, transfer of funds to a PayPal® or Venmo® account, or via some other electronic payment method.
Alternatively, if the ticket was a high-tier winner, the winning ticket holder would claim their prize by visiting a local lottery claim center and present the UCSL device for examination prior to claim.
In some embodiments, the user's enrollment may enable the user to participate in additional drawings, for example, where game selection that have been purchased remain unplayed after a drawing. For example, when the lottery system 1720 next determines that an entry for a particular drawing should be entered into that drawing, the lottery system 1720 repeat the process for any remaining game selections as previously disclosed.
In an embodiment where the user has chosen their own game selections via the user-configurable lottery subscription plan 1705, the lottery system 1720 may retrieve the stored game selections selected by the user and enter that game selection into the drawing. Alternatively, wherein the user has not chosen their own game selections (such as where the game selections are pre-printed, for example, where the UCSL device comprises a pre-printed lottery ticket 1500), the lottery system 1720 would retrieve the next, unused game selections (e.g., the second row) and enter that game selection into the drawing. This would continue, until all game selections for the UCSL device have been played or the entire value associated with the UCSL has been used.
In some embodiments disclosed herein are various devices, for example, a gaming device that may be configured to allow for a game to be accessed, loaded, or funded. In some embodiments, a gaming device may be configured to allow a user to access, for example, via a user device, one or more particular games; additionally or alternatively, in some embodiments a gaming device may be configured to allow a user to load one or more particular games onto a device, for example, a user device; additionally or alternatively, in some embodiments, a gaming device may be configured to allow a user to fund one or more games, for example, which may be played via a user device.
Referring to
As similarly disclosed with respect to various other embodiments herein, the gaming device 2000 may comprise an activation code 2010 which may be machine-readable (such as via a scanner or card reader), human-readable, or both. For example, in various embodiments, the activation code 2010 may comprise a magnetic stripe, a bar-code (e.g., a linear barcode such as a UCC 128 barcode or a matrix barcode, such as a quick-response (e.g., a QR Code®), a number, a combination of letters and number, or combinations thereof. As will be further explained, the activation code 2010 may be unique, for example, with respect to the particular gaming device 2000 with which it is associated.
Also, the gaming device 2000 may comprise a user device-interface 2020, which may generally be configured to allow various data or information, as will be explained herein, to be stored by the gaming device 2000 and conveyed between the gaming device 2000 and a user device, for example, a PC, laptop, handheld device, mobile phone, or other device. In various embodiments, the user device-interface 2020 may comprise a contactless communication protocol device, examples of which may include near-field communication (NFC) and radio-frequency identification (RFID). Additionally or alternatively, the user device-interface 2020 may comprise a code that is readable via the user device, for example, via an optical reader, optical scanner, or camera of the user device, examples of which include a bar-code (e.g., a linear barcode such as a UCC 128 barcode or a matrix barcode, such as a quick-response code (e.g., a QR Code® —QR Code® is a registered trademark of Denso Wave Incorporated). Additionally or alternatively, the user device-interface may comprise a code that is readable by a user and can be input into the user device via a user interface, for example, a number, a combination of letters and numbers. In the embodiment of
Also, referring to
In the embodiment of
Also in the embodiments of
In some embodiments, the gaming device 2100 comprises a covering 2130 configured to obscure the user device-interface 2120 such that the user device-interface 2120 cannot be viewed or accessed until the covering 2130 has been removed, such as until after the gaming device has been sold and activated. In various embodiments, the covering 2130 may include a material that may be suitably removed by a purchaser, such as a removable sticker or a scratch-off material such as a latex film. In the embodiment of
Referring to
In the embodiment of
At block 2201, the method 2200 begins when a purchaser selects the gaming device 2000 or, in the embodiment of
At block 2207, the POS terminal generates a transaction request, particularly, an activation request, and communicates the activation request to the lottery system (e.g., lottery system 520 or 1720). The activation request may comprise, in addition to information uniquely identifying the gaming device being purchased (e.g., activation code 2010 or activation code 2110), information identifying the retailer, information identifying the POS terminal, information identifying the jurisdiction (e.g., the state) in which the gaming device is being purchased, or combinations thereof.
Upon receipt of the activation request, at block 2208, the lottery system may access one or more records associated with the gaming device referenced in the activation request and determine the validity of the activation request received from the POS terminal. In various embodiments, the lottery system may determine the validity of the activation request based upon (i) whether or not the gaming device referenced in the activation request has been previously activated; (ii) whether or not a retailer associated with the gaming device referenced in the activation request is consistent with the retailer referenced in the activation request; (iii) whether or not a POS terminal associated with the gaming device referenced in the activation request is consistent with the POS terminal referenced in the activation request; (iv) whether or not a jurisdiction associated with the gaming device referenced in the activation request is consistent with the jurisdiction referenced in the activation request; (v) whether or not the geographic location of the POS terminal associated with the purchase of the gaming device corresponds to a geographic location approved for the sale of the gaming device, or (vi) combinations thereof.
Upon a determination that the activation request is valid, at block 2209, the lottery system updates one or more records associated with the gaming device referenced in the activation request to indicate that the gaming device has been validly purchased and is active and, at block 2210, responds to the POS terminal with a response to the request indicating success or failure of the activation. If successful, the purchase transaction is complete. If unsuccessful, the POS terminal may indicate the failure and the funds tendered by the purchaser may be returned.
In some embodiments, for example, where the user device-interface 2020 comprises a contactless communication protocol device, for example, NFC or RFID, upon receipt of the response indicating success or failure of the activation of the gaming device, the cashier may be instructed to take one or more additional actions to complete the activation. For example, in some embodiments, the cashier may be instructed to scan the NFC of RFID device of the gaming device, for example, via a NFC or RFID reader/scanner to communicate the activation to the NFC of RFID device of the gaming device, for example, so that the NFC of RFID device of the gaming device is made active and usable, as will be disclosed herein, by the purchaser.
Also, in embodiments where a covering (e.g., covering 2130) obscures any part of the gaming device, the covering may be removed upon completion of the purchase and activation.
Following a successful purchase transaction, the purchaser may use a gaming device to access, load, or fund a game. Referring to
At block 2251, the purchaser may utilize their user device to interact with the user device-interface (e.g., user device-interface 2020 or 2120). For example, in various embodiments, the user may utilize an application or program residing on their user device to scan or read information or data from the user device interface. Alternatively, in some embodiments the user may enter a code into the user device, for example, via an application or program residing on their user device or into a portal accessed via the user device.
At block 2252, in some embodiments, the user device-interface (e.g., user device-interface 2020 or 2120) may be validated by a lottery system to ensure that the gaming device is active, for example, by accessing one or more records associated with the gaming device. If the status indicated inactive, the lottery system 1720 may display a message informing the user that the gaming device was inactive. Until the user device is validated, the lottery system may not allow accessing, loading, and/or funding one or more games.
Upon validation, at block 2253, the purchaser may be allowed to access, load, or fund one or more games. For example, in some embodiments, the user device-interface may be configured to cause the user device to access one or more games referenced via the user device-interface. For example, the upon an interaction between the user device-interface and the user device, as disclosed herein, the user device may be caused to access a game. For example, the information or data obtained from the user device-interface may serve as an access key to a gaming portal.
Additionally or alternatively, in some embodiments, the user device-interface may be configured to cause the user device to load (e.g., download and install software for) one or more games stored via the user device-interface, such as where the user device interface comprises an NFC chip. Additionally or alternatively, in some embodiments, the user device-interface may be configured to cause the user device to load (e.g., download and install software for) one or more games stored remotely, such as via an internet connection.
Additionally or alternatively, in some embodiments, the user device-interface may be configured to cause the user device to apply a value (such as a number of plays or an amount that can be wagered) to a user's account such that the user may utilize the value to play one or more games.
In various embodiments, the game being accessed, loaded, or funded, can be any wagering-type game capable of being played virtually (e.g., via the user device), examples of which include the virtual lottery tickets disclosed herein. Other examples may include virtual manifestations of lotteries, blackjack, poker, craps, slot machines, roulette, bingo, and dice.
At block 2254, the purchaser may play one or more games via their user device and may obtain prize-winnings. At block 2255, the user device may be configured to also provide the user with an option to claim a prize resulting from play of the gaming device. For example, where the winnings have a low-tier value, the winnings would be paid out electronically, such as by a stored-value card containing the prize amount to be delivered to the user electronically or by mail or added a stored-value account to the user's electronic wallet; alternatively, the user device could direct the user to an authorized physical location (e.g., a lottery office) to redeem the lottery ticket (for example, if the redemption value exceeds a winnings threshold). Additionally or alternatively, the user could have the option to redeem the winnings in the form of additional lottery tickets (e.g., which may be presented virtually to the user) for play in a future game.
All of, or a portion of, the system described above may be implemented on any particular machine, or machines, with sufficient processing power, memory resources, and throughput capability to handle the necessary workload placed upon the computer, or computers.
It is understood that by programming and/or loading executable instructions onto the computer system 2380, at least one of the CPU 2382, the RAM 2388, and the ROM 2386 are changed, transforming the computer system 2380 in part into a particular machine or apparatus having the novel functionality taught by the present disclosure. It is fundamental to the electrical engineering and software engineering arts that functionality that can be implemented by loading executable software into a computer can be converted to a hardware implementation by well-known design rules. Decisions between implementing a concept in software versus hardware typically hinge on considerations of stability of the design and numbers of units to be produced rather than any issues involved in translating from the software domain to the hardware domain. Generally, a design that is still subject to frequent change may be preferred to be implemented in software, because re-spinning a hardware implementation is more expensive than re-spinning a software design. Generally, a design that is stable that will be produced in large volume may be preferred to be implemented in hardware, for example in an application specific integrated circuit (ASIC), because for large production runs the hardware implementation may be less expensive than the software implementation. Often a design may be developed and tested in a software form and later transformed, by well-known design rules, to an equivalent hardware implementation in an application specific integrated circuit that hardwires the instructions of the software. In the same manner as a machine controlled by a new ASIC is a particular machine or apparatus, likewise a computer that has been programmed and/or loaded with executable instructions may be viewed as a particular machine or apparatus.
The secondary storage 2384 is typically comprised of one or more disk drives or tape drives and is used for non-volatile storage of data and as an over-flow data storage device if RAM 2388 is not large enough to hold all working data. Secondary storage 2384 may be used to store programs which are loaded into RAM 2388 when such programs are selected for execution. The ROM 2386 is used to store instructions and perhaps data which are read during program execution. ROM 2386 is a non-volatile memory device which typically has a small memory capacity relative to the larger memory capacity of secondary storage 2384. The RAM 2388 is used to store volatile data and perhaps to store instructions. Access to both ROM 2386 and RAM 2388 is typically faster than to secondary storage 2384. The secondary storage 2384, the RAM 2388, and/or the ROM 2386 may be referred to in some contexts as computer readable storage media and/or non-transitory computer readable media.
I/O devices 2390 may include printers, video monitors, liquid crystal displays (LCDs), touch screen displays, keyboards, keypads, switches, dials, mice, track balls, voice recognizers, card readers, paper tape readers, or other well-known input devices.
The network connectivity devices 2392 may take the form of modems, modem banks, Ethernet cards, universal serial bus (USB) interface cards, serial interfaces, token ring cards, fiber distributed data interface (FDDI) cards, wireless local area network (WLAN) cards, radio transceiver cards such as code division multiple access (CDMA), global system for mobile communications (GSM), long-term evolution (LTE), worldwide interoperability for microwave access (WiMAX), and/or other air interface protocol radio transceiver cards, and other well-known network devices. These network connectivity devices 2392 may enable the processor 2382 to communicate with the Internet or one or more intranets. With such a network connection, it is contemplated that the processor 2382 might receive information from the network or might output information to the network in the course of performing the above-described method steps. Such information, which is often represented as a sequence of instructions to be executed using processor 2382, may be received from and outputted to the network, for example, in the form of a computer data signal embodied in a carrier wave.
Such information, which may include data or instructions to be executed using processor 2382 for example, may be received from and outputted to the network, for example, in the form of a computer data baseband signal or signal embodied in a carrier wave. The baseband signal or signal embedded in the carrier wave, or other types of signals currently used or hereafter developed, may be generated according to several methods well known to one skilled in the art. The baseband signal and/or signal embedded in the carrier wave may be referred to in some contexts as a transitory signal.
The processor 2382 executes instructions, codes, computer programs, scripts which it accesses from hard disk, floppy disk, optical disk (these various disk-based systems may all be considered secondary storage 2384), ROM 2386, RAM 2388, or the network connectivity devices 2392. While only one processor 2382 is shown, multiple processors may be present. Thus, while instructions may be discussed as executed by a processor, the instructions may be executed simultaneously, serially, or otherwise executed by one or multiple processors. Instructions, codes, computer programs, scripts, and/or data that may be accessed from the secondary storage 2384, for example, hard drives, floppy disks, optical disks, and/or other device, the ROM 2386, and/or the RAM 2388 may be referred to in some contexts as non-transitory instructions and/or non-transitory information.
In an embodiment, the computer system 2380 may comprise two or more computers in communication with each other that collaborate to perform a task. For example, but not by way of limitation, an application may be partitioned in such a way as to permit concurrent and/or parallel processing of the instructions of the application. Alternatively, the data processed by the application may be partitioned in such a way as to permit concurrent and/or parallel processing of different portions of a data set by the two or more computers. In an embodiment, virtualization software may be employed by the computer system 2380 to provide the functionality of a number of servers that is not directly bound to the number of computers in the computer system 2380. For example, virtualization software may provide twenty virtual servers on four physical computers. In an embodiment, the functionality disclosed above may be provided by executing the application and/or applications in a cloud computing environment. Cloud computing may comprise providing computing services via a network connection using dynamically scalable computing resources. Cloud computing may be supported, at least in part, by virtualization software. A cloud computing environment may be established by an enterprise and/or may be hired on an as-needed basis from a third-party provider. Some cloud computing environments may comprise cloud computing resources owned and operated by the enterprise as well as cloud computing resources hired and/or leased from a third-party provider.
In an embodiment, some or all of the functionality disclosed above may be provided as a computer program product. The computer program product may comprise one or more computer readable storage medium having computer usable program code embodied therein to implement the functionality disclosed above. The computer program product may comprise data structures, executable instructions, and other computer usable program code. The computer program product may be embodied in removable computer storage media and/or non-removable computer storage media. The removable computer readable storage medium may comprise, without limitation, a paper tape, a magnetic tape, magnetic disk, an optical disk, a solid state memory chip, for example analog magnetic tape, compact disk read only memory (CD-ROM) disks, floppy disks, jump drives, digital cards, multimedia cards, and others. The computer program product may be suitable for loading, by the computer system 2380, at least portions of the contents of the computer program product to the secondary storage 2384, to the ROM 2386, to the RAM 2388, and/or to other non-volatile memory and volatile memory of the computer system 2380. The processor 2382 may process the executable instructions and/or data structures in part by directly accessing the computer program product, for example by reading from a CD-ROM disk inserted into a disk drive peripheral of the computer system 2380. Alternatively, the processor 2382 may process the executable instructions and/or data structures by remotely accessing the computer program product, for example by downloading the executable instructions and/or data structures from a remote server through the network connectivity devices 2392. The computer program product may comprise instructions that promote the loading and/or copying of data, data structures, files, and/or executable instructions to the secondary storage 2384, to the ROM 2386, to the RAM 2388, and/or to other non-volatile memory and volatile memory of the computer system 2380.
In some contexts, the secondary storage 2384, the ROM 2386, and the RAM 2388 may be referred to as a non-transitory computer readable medium or a computer readable storage media. A dynamic RAM embodiment of the RAM 2388, likewise, may be referred to as a non-transitory computer readable medium in that while the dynamic RAM receives electrical power and is operated in accordance with its design, for example during a period of time during which the computer 2380 is turned on and operational, the dynamic RAM stores information that is written to it. Similarly, the processor 2382 may comprise an internal RAM, an internal ROM, a cache memory, and/or other internal non-transitory storage blocks, sections, or components that may be referred to in some contexts as non-transitory computer readable media or computer readable storage media.
The ordering of steps in the various processes, data flows, and flowcharts presented are for illustration purposes and do not necessarily reflect the order that various steps must be performed. The steps may be rearranged in different orders in different embodiments to reflect the needs, desires and preferences of the entity implementing the systems. Furthermore, many steps may be performed simultaneously with other steps in some embodiments.
Also, techniques, systems, subsystems and methods described and illustrated in the various embodiments as discrete or separate may be combined or integrated with other systems, modules, techniques, or methods without departing from the scope of the present disclosure. Other items shown or discussed as directly coupled or communicating with each other may be coupled through some interface or device, such that the items may no longer be considered directly coupled to each other but may still be indirectly coupled and in communication, whether electrically, mechanically, or otherwise with one another. Other examples of changes, substitutions, and alterations are ascertainable by one skilled in the art and could be made without departing from the spirit and scope disclosed. The following numbered entries represent a non-exhaustive collection of exemplary embodiments of the instantly disclosed subject matter.
Following are particular embodiments of the disclosure.
A first embodiment is a computer-implemented method for facilitating user participation in a user configurable subscription lottery plan comprising a central processor unit executing executable instructions to cause the performance of the method steps comprising: receiving information related to a user's selection of a user configurable subscription lottery device; determining validity of the information; updating one or more records associated with the user configurable subscription lottery device; allowing a user to access to the user configurable subscription lottery plan; providing options to the user for user configurable lottery-play criteria; and entering the user in one or more lotteries.
A second embodiment is the computer-implemented method of the first embodiment, wherein the information comprises an activation request for the user configurable subscription lottery device.
A third embodiment is the computer-implemented method of one of the first through the second embodiments, wherein the user configurable subscription lottery device comprises a unique account code which associates the user configurable subscription lottery device with a user-portal.
A fourth embodiment is the computer-implemented method of the third embodiment, wherein the user-portal allows the user to assign, modify, establish, or combinations thereof, various attributes of the user configurable subscription lottery device.
A fifth embodiment is the computer-implemented method of one of the first through the fourth embodiments, wherein the user configurable subscription lottery device comprises a security information which provides access to the user configurable subscription lottery plan.
A sixth embodiment is the computer-implemented method of one of the first through the fifth embodiments, further comprising activating the user configurable subscription lottery device.
A seventh embodiment is the computer-implemented method of one of the first through the sixth embodiments, wherein determining the validity of the information comprises determining: (i) whether the user configurable subscription lottery device has been previously activated; (ii) whether a retailer associated with the user configurable subscription lottery device referenced in an activation request is consistent with the retailer referenced in the activation request; (iii) whether a point of sale terminal associated with the user configurable subscription lottery device referenced in the activation request is consistent with the point of sale terminal referenced in the activation request; (iv) whether a jurisdiction associated with the user configurable subscription lottery device referenced in the activation request is consistent with the jurisdiction referenced in the activation request; (v) whether a geographic location of the point of sale terminal associated with a purchase of the user configurable subscription lottery device corresponds to an approved geographic location for the sale of the user configurable subscription lottery device; or (vi) combinations thereof.
An eighth embodiment is the computer-implemented method of one of the first through the seventh embodiments, further comprising enrolling the user in the user configurable subscription lottery plan.
A ninth embodiment is the computer-implemented method of one of the first through the eighth embodiments, further comprising receiving the user configurable lottery-play criteria from the user.
A tenth embodiment is the computer-implemented method of one of the first through the ninth embodiments, wherein the user configurable lottery-play criteria comprise: (i) which lottery games to enter; (ii) minimum jackpot size for entry; (iii) number of entries per lottery; (iv) number of entries per jackpot size; (v) which numbers the user chooses to play; (vi) how the user is to be notified of entry into games; (vii) how the user is to be notified of game results; (viii) how the user is to be notified of winnings; (ix) which game options foe participation; (x) how to redeem winnings; or (xi) combinations thereof.
An eleventh embodiment is the computer-implemented method of the ninth embodiment, wherein the numbers the user chooses to play are printed on a pre-printed user configurable subscription lottery device.
A twelfth embodiment is the computer-implemented method of the ninth embodiment, wherein the numbers the user chooses to play are the user's own numbers which the user selects and provides.
A thirteenth embodiment is the computer-implemented method of one of the first through the twelfth embodiments, wherein the user configurable subscription lottery device comprises denomination indicia.
A fourteenth embodiment is the computer-implemented method of the thirteenth embodiment, wherein denomination indicia indicates how many plays in which the user configurable subscription lottery device may participate.
A fifteenth embodiment is the computer-implemented method of one of the first through the fourteenth embodiments, further comprising prompting the user to create an account which links the user configurable subscription lottery device, a pre-printed lottery user configurable subscription lottery device, another payment account, or combinations thereof.
A sixteenth embodiment is the computer-implemented method of the fifteenth embodiments, wherein the account would keep the user configurable subscription lottery device, the pre-printed lottery user configurable subscription lottery device, or combinations thereof, funded for participation in the one or more lotteries.
A seventeenth embodiment is the computer-implemented method of one of the first through the sixteenth embodiments, wherein entering the user in one or more lotteries comprises interacting with one or more relevant central gaming systems.
An eighteenth embodiment is the computer-implemented method of the seventeenth embodiment, wherein interacting with one or more relevant central gaming systems comprises causing a ticket to be purchased from a lottery terminal within an authorized lottery retailer's premises.
A nineteenth embodiment is the computer-implemented method of the eighteenth embodiment, further comprising printing the ticket by the lottery terminal, scanning the ticket, and delivering an image or other identifier of the ticket to the user.
A twentieth embodiment is the computer-implemented method of one of the first through the nineteenth embodiments, wherein the user configurable subscription lottery device is virtual and loadable into an electronic wallet.
A twenty-first embodiment is a user configurable subscription lottery plan processing system comprising: a processor comprising a computer-readable medium storing instructions configured to cause the processor to: receive information related to a user's selection of a user configurable subscription lottery device; determine validity of the information; update one or more records associated with the user configurable subscription lottery device; allow a user to access to the user configurable subscription lottery plan; provide options to the user for user configurable lottery-play criteria; and enter the user in one or more lotteries.
A twenty-second embodiment is the user configurable subscription lottery plan processing system of the twenty-first embodiment, wherein the information comprises an activation request for the user configurable subscription lottery device.
A twenty-third embodiment is the user configurable subscription lottery plan processing system of one of the twenty-first through the twenty-second embodiments, wherein the user configurable subscription lottery device comprises a unique account code which associates the user configurable subscription lottery device with a user-portal.
A twenty-fourth embodiment is the user configurable subscription lottery plan processing system of the twenty-third embodiment, wherein the user-portal allows the user to assign, modify, establish, or combinations thereof, various attributes of the user configurable subscription lottery device.
A twenty-fifth embodiment is the user configurable subscription lottery plan processing system of one of the twenty-first through the twenty-fourth embodiments, wherein the user configurable subscription lottery device comprises a security information which provides access to the user configurable subscription lottery plan.
A twenty-sixth embodiment is the user configurable subscription lottery plan processing system of one of the twenty-first through the twenty-fifth embodiments, wherein the processor is further configured to activate the user configurable subscription lottery device.
A twenty-seventh embodiment is the user configurable subscription lottery plan processing system of one of the twenty-first through the twenty-sixth embodiments, wherein the processor is further configured to determine the validity of the information by determining: (i) whether the user configurable subscription lottery device has been previously activated; (ii) whether a retailer associated with the user configurable subscription lottery device referenced in an activation request is consistent with the retailer referenced in the activation request; (iii) whether a point of sale terminal associated with the user configurable subscription lottery device referenced in the activation request is consistent with the point of sale terminal referenced in the activation request; (iv) whether a jurisdiction associated with the user configurable subscription lottery device referenced in the activation request is consistent with the jurisdiction referenced in the activation request; (v) whether a geographic location of the point of sale terminal associated with a purchase of the user configurable subscription lottery device corresponds to an approved geographic location for the sale of the user configurable subscription lottery device; or (vi) combinations thereof.
A twenty-eighth embodiment is the user configurable subscription lottery plan processing system of one of the twenty-first through the twenty-seventh embodiments, wherein the processor is further configured to enroll the user in the user configurable subscription lottery plan.
A twenty-ninth embodiment is the user configurable subscription lottery plan processing system of one of the twenty-first through the twenty-eighth embodiments, wherein the processor is further configured to receive the user configurable lottery-play criteria from the user.
A thirtieth embodiment is the user configurable subscription lottery plan processing system of one of the twenty-first through the twenty-ninth embodiments, wherein the user configurable lottery-play criteria comprise: (i) which lottery games to enter; (ii) minimum jackpot size for entry; (iii) number of entries per lottery; (iv) number of entries per jackpot size; (v) which numbers the user chooses to play; (vi) how the user is to be notified of entry into games; (vii) how the user is to be notified of game results; (viii) how the user is to be notified of winnings; (ix) which game options foe participation; (x) how to redeem winnings; or (xi) combinations thereof.
A thirty-first embodiment is the user configurable subscription lottery plan processing system of the thirtieth embodiment, wherein the numbers the user chooses to play are printed on a pre-printed user configurable subscription lottery device.
A thirty-second embodiment is the user configurable subscription lottery plan processing system of the thirtieth embodiment, wherein the numbers the user chooses to play are the user's own numbers which the user selects and provides.
A thirty-third embodiment is the user configurable subscription lottery plan processing system of one of the twenty-first through the thirty-second embodiments, wherein the user configurable subscription lottery device comprises denomination indicia.
A thirty-fourth embodiment is the user configurable subscription lottery plan processing system of the thirty-third embodiment, wherein denomination indicia indicates how many plays in which the user configurable subscription lottery device may participate.
A thirty-fifth embodiment is the user configurable subscription lottery plan processing system of one of the twenty-first through the thirty-fourth embodiments, wherein the processor is further configured to prompt the user to create an account which links the user configurable subscription lottery device, a pre-printed lottery user configurable subscription lottery device, another payment account, or combinations thereof.
A thirty-sixth embodiment is the user configurable subscription lottery plan processing system of the thirty-fifth embodiment, wherein the account would keep the user configurable subscription lottery device, the pre-printed lottery user configurable subscription lottery device, or combinations thereof, funded for participation in the one or more lotteries.
A thirty-seventh embodiment is the user configurable subscription lottery plan processing system of one of the twenty-first through the thirty-sixth embodiments, wherein the processor is further configured to enter the user in one or more lotteries by interacting with one or more relevant central gaming systems.
A thirty-eighth embodiment is the user configurable subscription lottery plan processing system of the thirty-seventh embodiment, wherein interacting with one or more relevant central gaming systems comprises causing a ticket to be purchased from a lottery terminal within an authorized lottery retailer's premises.
A thirty-ninth embodiment is the user configurable subscription lottery plan processing system of the thirty-eighth embodiment, wherein the processor is further configured to cause the ticket to be printed by the lottery terminal, cause the ticket to be scanned, and cause an image or other identifier of the ticket to be delivered to the user.
A fortieth embodiment is the user configurable subscription lottery plan processing system of one of the twenty-first through the thirty-ninth embodiments, wherein the user configurable subscription lottery device is virtual and loadable into an electronic wallet.
This application claims priority to provisional application U.S. Ser. No. 62/858,227 filed Jun. 6, 2019 by Richard Alan Gotlieb and titled “Pre-Printed and Pre-Selected Lottery Tickets for Point of Sale Purchase” and is incorporated herein by reference in its entirety.
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/US2020/036500 | 6/5/2020 | WO |
| Number | Date | Country | |
|---|---|---|---|
| 62858227 | Jun 2019 | US |
