Patent Grant
10950091
Embodiments of the present invention are generally related to communications within data processing systems. More particularly, the present invention relates to the communication and processing of wagering data.
The gaming industry has traditionally developed electronic gaming machines (EGMs) that implement simple wagers. However, more complicated wagering processes need communication and processing systems that are better suited for implementing these more complicated wagering processes. Various aspects of embodiments of the present invention meet such a need.
Systems and methods in accordance with embodiments of the invention provide a communication and data processing system constructed for a billiard combined proposition wagering system.
In an embodiment of the invention, a combined wagering proposition includes one or more skill propositions and one or more chance propositions. In some embodiments, one or more skill outcomes of the one or more skill propositions are used to allocate one or more chance outcomes of the one or more chance propositions to determine a combined wagering outcome for the combined wagering proposition. In other such embodiments, one or more chance outcomes of the one or more chance propositions are used to allocate one or more skill outcomes of the one or more skill propositions to determine a combined wagering outcome for the combined wagering proposition.
In an embodiment of the invention, a process controller operates as an interface between an interactive controller that determines skill outcomes and a chance-based controller that determines chance outcomes. By virtue of this feature, the chance-based controller is isolated from the interactive controller allowing the interactive controller to operate in an unregulated environment will allowing the chance-based controller to operate in a regulated environment, thus providing for more efficient management of the operations of such a system.
In another embodiment of the invention, a single chance-based controller may provide services to two or more interactive controllers and/or two or more process controllers, thus allowing a billiard combined proposition wagering system to operate more efficiently over a large range of scaling.
In another embodiment of the invention, multiple types of interactive controllers using different operating systems may be interfaced to a single type of process controller and/or chance-based controller without requiring customization of the process controller and/or the chance-based controller, thus improving the efficiency of the process controller and or the chance-based controller by reducing complexity associated with maintaining separate process controllers and/or chance-based controllers for each type of interactive controller.
In another embodiment of the invention, an interactive controller may be provided as a user device under control of a user while maintaining the chance-based controller in an environment under the control of a regulated operator of wagering equipment, thus providing for a more economical system as the regulated operator need not expend capital to purchase interactive controllers.
In another embodiment of the invention, data communicated between the controllers may be encrypted to increase security of the billiard combined proposition wagering system.
In another embodiment of the invention, a process controller isolates chance proposition logic and skill proposition logic as unregulated logic from a regulated chance-based controller, thus allowing errors in the skill proposition logic and/or chance proposition logic to be corrected, new skill proposition logic and/or chance proposition logic to be used, or modifications to be made to the skill proposition logic and/or chance proposition logic without a need for time-consuming regulatory approval.
In another embodiment of the invention, an interactive application may require extensive processing resources from an interactive controller leaving few processing resources for the functions performed by a process controller and/or a chance-based controller. By virtue of an architecture of some embodiments of the invention, processing loads may be distributed across multiple devices such that operations of the interactive controller may be dedicated to the interactive application and the processes of the process controller and/or chance-based controller are not burdened by the requirements of the interactive application.
In another embodiment of the invention, a billiard combined proposition wagering system operates with its components being distributed across multiple devices. These devices can be connected by communication channels including, but not limited to, local area networks, wide area networks, local communication buses, and/or the like. The devices may communicate using various types of protocols, including but not limited to, networking protocols, device-to-device communications protocols, and the like. In many such embodiments, one or more components of a billiard combined proposition wagering system are distributed in close proximity to each other and communicate using a local area network and/or a communication bus. In several embodiments, an interactive controller and a process controller of a billiard combined proposition wagering system are in a common location and communicate with an external chance-based controller. In some embodiments, a process controller and a chance-based controller of a billiard combined proposition wagering system are in a common location and communicate with an external interactive controller. In many embodiments, an interactive controller, a process controller, and a chance-based controller of a billiard combined proposition wagering system are located in a common location. In some embodiments, a session/management controller is located in a common location with a process controller and/or a chance-based controller. In various embodiments, these multiple devices can be constructed from or configured using a single device or a plurality of devices such that a billiard combined proposition wagering system is executed as a system in a virtualized space such as, but not limited to, where a chance-based controller and a process controller are large scale centralized servers in the cloud operatively connected to widely distributed interactive controllers via a wide area network such as the Internet or a local area network. In such embodiments, the components of a billiard combined proposition wagering system may communicate using a networking protocol or other type of device-to-device communications protocol.
In another embodiment of the invention, a centralized chance-based controller is operatively connected to, and communicates with, one or more process controllers using a communication link. The centralized chance-based controller can generate chance outcomes for wagers in accordance with one or more chance-based propositions. The centralized chance-based controller can determine a number of simultaneous or pseudo-simultaneous chance outcomes in accordance with a variety of chance-based propositions that one or more distributed billiard combined proposition wagering systems can use.
In another embodiment of the invention, a centralized process controller is operatively connected to one or more interactive controllers and one or more chance-based controllers using a communication link. The centralized process controller can perform the functionality of a process controller across various billiard combined proposition wagering systems.
In another embodiment of the invention, an interactive application server provides a host for managing head-to-head play operating over a network of interactive controllers connected to the interactive application server using a communication link. The interactive application server provides an environment where users can compete directly with one another and interact with other users.
An embodiment includes an interactive controller constructed to: provide an interactive application display associated with an interactive application provided by the interactive controller; communicate, to a process controller, initialization data; communicate, to the process controller, skill outcome data; receive, from the process controller, wagering telemetry data; and update a wagering user interface based on the wagering telemetry data; a chance-based controller constructed to: receive, from a credit processing system, incoming credit data; receive, from the process controller, chance outcome request data; determine a chance outcome for a chance-based proposition based on the chance outcome request data; communicate, to the process controller, chance outcome data; receive, from the process controller, combined outcome data; update one or more credit meters based on the combined outcome data; and communicate, to the process controller, updated credit meter data; and the process controller operatively connecting the interactive controller and the chance-based controller, the process controller constructed to: receive, from the interactive controller, the initialization data; responsive to receiving the initialization data, communicate, to the chance-based controller, the chance outcome request data; receive, from the chance-based controller, the chance outcome data, wherein the chance outcome data comprises one or more outcomes; determine object values by assigning each outcome to one or more objects associated with the interactive application; receive, from the interactive controller, the skill outcome data; update the object values based on the skill outcome data; determine a billiard combined outcome based on the skill outcome data and the chance outcome data; communicate, to the chance-based controller, combined outcome data; receive, from the chance-based controller, the updated credit meter data; generate wagering telemetry data based on the combined outcome data and the updated credit meter data; and communicate, to the interactive controller, the wagering telemetry data.
In a further embodiment, the interactive controller and the process controller are constructed from the same device, and the process controller is operatively connected to the chance-based controller using a communication link.
In a further embodiment, the chance-based controller and the process controller are constructed from the same device, and the process controller is operatively connected to the interactive controller using a communication link.
In a further embodiment, the system comprises: an enclosure constructed to mount: a user input device operatively connected to the interactive controller; a user output device operatively connected to the interactive controller; a credit input device operatively connected to the chance-based controller; and a credit output device operatively connected to the chance-based controller.
In a further embodiment, the chance-based controller is further constructed to: communicate with the credit input device to receive a credit input; credit a credit meter with credits based on the incoming credit data; resolve a chance-based proposition based on a communication received from the process controller; update the credit meter based on a chance outcome of the wager; and communicate with the credit output device to generate a credit output based on credits transferred off of the credit meter.
In a further embodiment, the interactive application is a billiards interactive application and the one or more objects are billiard balls.
In a further embodiment, the skill outcome data reflects a user putting a billiard ball in a pocket, and wherein the object value associated with the pocketed ball is credited to the user.
In a further embodiment, the skill outcome reflects a scratch, and wherein the object value associated with the scratched ball is reassigned to one or more other billiard balls.
An embodiment includes an interactive controller constructed to: provide an interactive application display associated with an interactive application provided by the interactive controller; communicate, to a process controller, initialization data; communicate, to the process controller, skill outcome data; receive, from the process controller, wagering telemetry data; and update a wagering user interface based on the wagering telemetry data; and the process controller operatively connecting the interactive controller and a chance-based controller, the process controller constructed to: receive, from the interactive controller, the initialization data; responsive to receiving the initialization data, communicate, to the chance-based controller, chance outcome request data; receive, from the chance-based controller, chance outcome data, wherein the chance outcome data comprises one or more outcomes; determine object values by assigning each outcome to one or more objects associated with the interactive application; receive, from the interactive controller, the skill outcome data; update the object values based on the skill outcome data; determine a billiard combined outcome based on the skill outcome data and the chance outcome data; communicate, to the chance-based controller, combined outcome data; receive, from the chance-based controller, updated credit meter data; generate wagering telemetry data based on the combined outcome data and the updated credit meter data; and communicate, to the interactive controller, the wagering telemetry data.
An embodiment includes a chance-based controller constructed to: receive, from a credit processing system, incoming credit data; receive, from a process controller, chance outcome request data; determine a chance outcome for a chance-based proposition based on the chance outcome request data; communicate, to the process controller, chance outcome data; receive, from the process controller, combined outcome data; update one or more credit meters based on the combined outcome data; and communicate, to the process controller, updated credit meter data; and the process controller operatively connecting an interactive controller and the chance-based controller, the process controller constructed to: receive, from the interactive controller, initialization data; responsive to receiving the initialization data, communicate, to the chance-based controller, the chance outcome request data; receive, from the chance-based controller, the chance outcome data, wherein the chance outcome data comprises one or more outcomes; determine object values by assigning each outcome to one or more objects associated with an interactive application provided by the interactive controller; receive, from the interactive controller, skill outcome data; update the object values based on the skill outcome data; determine a billiard combined outcome based on the skill outcome data and the chance outcome data; communicate, to the chance-based controller, combined outcome data; receive, from the chance-based controller, the updated credit meter data; generate wagering telemetry data based on the combined outcome data and the updated credit meter data; and communicate, to the interactive controller, the wagering telemetry data.
A billiard combined proposition wagering system allows for the management of a combined wagering proposition having one or more skill propositions combined with one or more chance propositions. In some embodiments of a billiard combined proposition wagering system, an interactive application executed by an interactive controller provides skill proposition components of the billiard combined proposition wagering system. The interactive controller is operatively connected to a process controller that manages and configures the interactive controller and the interactive application, and determines how chance outcomes determined by a chance-based controller should be combined with skill outcomes determined by the interactive application. The process controller is further operatively connected to a chance-based controller that provides the chance outcomes for chance-based propositions.
In some embodiments, the interactive controller also provides a wagering user interface that is used to receive commands and display data for a combined wagering process and combined wagering outcome determined from a chance outcome and a skill outcome in accordance with a combined wagering proposition. The content of the wagering user interface is controlled by the process controller and includes content provided by the chance-based controller and the interactive controller.
In various embodiments, an interactive controller provides a management user interface used to manage a user profile.
Many different types of interactive applications may be utilized with the billiard combined proposition wagering system. In some embodiments, the interactive application reacts to the physical activity of a user. In these embodiments, the interactive application senses user interactions with the interactive application through one or more sensors that monitor the user's physical activities. Such sensors may include, but are not limited to, physiological sensors that monitor the physiology of the user, environmental sensors that monitor the physical environment of the interactive controller, accelerometers that monitor changes in motion of the interactive controller, and location sensors that monitor the location of the interactive controller such as global positioning sensors.
In some embodiments, the interactive application implements a skill-based game and interacts with the user by sensing skillful interactions with an interactive display generated by the interactive application.
In some embodiments, the interactive application is a tool used to achieve some useful goal.
In many embodiments, the interactive application generates various types of interactive elements in an interactive application environment. In some embodiments, these interactive elements are interactive application resources utilized within the interactive application environment to provide an interactive experience for a user. Chance outcomes of credits or interactive elements are determined in accordance with a chance-based proposition and initiation of automatic resolution of the chance-based proposition is achieved by interaction with one or more of the interactive elements of the interactive application. Chance outcomes of chance-based propositions of credits or interactive elements can cause consumption, loss or accrual of respective credits and/or interactive elements.
In accordance with some embodiments, chance outcomes of chance-based propositions events can influence interactive elements in the interactive application environment such as, but not limited to, automatically providing one or more new interactive elements, automatically restoring one or more consumed interactive elements, automatically causing the loss of one or more interactive elements, and automatic restoration or placement of one or more fixed interactive elements.
In various embodiments, the chance outcomes may be determined using one or more types of credits.
In some embodiments, credits can be one or more credits that are purchased using, and redeemed in, a real world currency having a real world value.
In many embodiments, credits can be one or more credits in a virtual currency. Virtual currency is an alternate currency that can be acquired, purchased or transferred by or to a user, but does not necessarily directly correlate to a real world currency. In many such embodiments, credits in a virtual currency are allowed to be purchased using a real world currency but are prevented from being redeemed in a real world currency having a real world value.
In several embodiments, interaction with the interactive elements of the interactive application, application credits can be optionally consumed and/or accrued within the interactive application as a result of interaction with the interactive elements. Application credits can be in the form of, but not limited to, application environment credits, experience points, and points generally.
In various embodiments, application credits are awarded on the basis of skillful interactions with the interactive elements of a skill-based interactive application. The skill-based interactive application can have one or more scoring criteria, embedded within a process controller and/or an interactive controller that provides the skill-based interactive application, that can be used to determine user performance against one or more goals of the skill-based interactive application in accordance with a skill proposition.
In many embodiments, application credits can be used to purchase in-application items, including but not limited to, application interactive elements that have particular properties, power ups for existing items, and other item enhancements.
In some embodiments, application credits may be used to earn entrance into a sweepstakes drawing, to earn entrance in a tournament with prizes, to score in the tournament, and/or to participate and/or score in any other game event.
In several embodiments, application credits can be stored on a user-tracking card or in a network-based user tracking system where the application credits are attributed to a specific user.
In many embodiments, a chance-based proposition includes utilization of application credits for a chance outcome of a randomly generated payout of interactive application credits, interactive elements, and/or interactive application objects in accordance with the chance-based proposition.
In a number of embodiments, a chance-based proposition utilizing an amount of credits results in a chance outcome of a payout of application credits, interactive elements, and/or interactive application objects that have a credit value if cashed out.
In some embodiments, such as when an interactive application is a skill-based interactive application, interactive application objects include in-application objects that may be utilized to enhance interactions with the skill-based interactive application. Such objects include, but are not limited to, power-ups, enhanced in-application items, and the like. In some embodiments, the interactive application objects include objects that are detrimental to interactions with the skill-based interactive application such as, but not limited to, obstructions in the skill-based interactive application space, a temporary handicap, an enhanced opponent, and the like.
In some embodiments, interactive elements in an interactive application include, but are not limited to, enabling interactive elements (EIE) that are interactive application environment resources utilized during interaction with an interactive application and whose utilization automatically initiates resolution of a chance-based proposition. In some embodiments, interactive elements in an interactive application include, but are not limited to, a reserve enabling interactive element (REIE), that is an interactive element that is automatically converted into one or more enabling interactive elements upon occurrence of a release event during an interactive session of an interactive application. In yet another embodiment, interactive elements in an interactive application include, but are not limited to, an actionable interactive element (AIE) that is an interactive element that is acted upon during a session of the interactive application to automatically initiate resolution of a chance-based proposition and may or may not be restorable during normal interaction with the interactive application. In yet another embodiment, interactive elements in an interactive application include a common enabling interactive element (CEIE) that is an interactive element that the interactive application shares between two or more users and causes a wagering event to be automatically determined in accordance with a combined proposition when interacted with by one or more of the two or more users during a session. In some embodiments, a user can utilize interactive elements during interactions with a controlled entity (CE) provided by an interactive application to a user.
In accordance with some embodiments of a billiard combined proposition wagering system, the initiation of resolution of a chance-based proposition can be dependent upon an interactive application environment variable such as, but not limited to, a required object (RO), a required environmental condition (REC), or a controlled entity characteristic (CEC). A RO is a specific interactive application object in an interactive application acted upon for an AE to be completed. A non-limiting example of an RO is a specific key needed to open a door. An REC is an interactive application state present within an interactive application for an AE to be completed. A non-limiting example of an REC is daylight whose presence enables a character to walk through woods. A CEC is a status of a controlled entity (CE) within an interactive application for an AE to be completed. A non-limiting example of a CEC is requirement that a CE have full health points before entering battle. Although various interactive application resources such as, but not limited to, the types of interactive application interactive elements as discussed herein may be used to automatically initiate resolution of a chance-based proposition in accordance with a chance-based proposition, one skilled in the art will recognize that any interactive application resource can be utilized in a billiard combined proposition wagering system to automatically initiate resolution of a chance-based proposition.
In several embodiments, a billiard combined proposition wagering system can utilize a process controller to continuously monitor use of the interactive application executed by an interactive controller in order to detect a wagering event and automatically initiate resolution of a combination proposition based on the wagering event.
In several embodiments, a wagering event occurrence can be determined by a process controller from one or more application environment variables within an interactive application environment that are used to initiate resolution of a combination proposition. Application environment variables can include, but are not limited to, passage of a period of time during billiard combined proposition wagering system interactive application use, a result from a billiard combined proposition wagering system interactive application session (such as, but not limited to, achieving a goal or a particular score), consumption of an interactive element, or an interaction that achieves a combination of interactive elements to be associated with a user profile.
In numerous embodiments, an interactive application instruction is an instruction by a process controller to an interactive controller and/or an interactive application of the interactive controller to modify a state of an interactive application or modify one or more interactive application resources or interactive elements. In some embodiments, the interactive application commands may be automatically generated by the process controller using one or more of a chance outcome and/or application environment variables. An interactive application instruction can be used by a process controller control many processes of an interactive application, such as, but not limited to, an causing an addition of a period of time available for a current interactive application session for the interactive application, an addition of a period of time available for a future billiard combined proposition wagering system interactive application session or any other modification to the interactive application interactive elements that can be utilized during an interactive application session. In some embodiments, an interactive application instruction can be used by the process controller to modify a type of an interactive element.
In several embodiments, a process controller of a billiard combined proposition wagering system may provide for a communications interface for asynchronous communications between a chance-based controller and an interactive application provided by an interactive controller, by operatively connecting the interactive controller, and thus the interactive controller's interactive application, with the chance-based controller.
In some embodiments, asynchronous communications provided for by a billiard combined proposition wagering system may reduce an amount of idle waiting time by an interactive controller of the billiard combined proposition wagering system, thus increasing an amount of processing resources that the interactive controller may provide to an interactive application or other processes of the interactive controller. In many embodiments, asynchronous communications provided for by a billiard combined proposition wagering system reduces an amount of idle waiting time by a chance-based controller, thus increasing an amount of processing resources that the chance-based controller may provide to determining chance outcomes, and other processes provided by the chance-based controller.
In some embodiments, a chance-based controller of a billiard combined proposition wagering system may be operatively connected to a plurality of interactive controllers through one or more process controllers and the asynchronous communications provided for by the one or more process controllers allows the chance-based controller to operate more efficiently by providing chance outcomes to a larger number of interactive controllers than would be achievable without the one or more process controllers of the billiard combined proposition wagering system.
In some embodiments, a billiard combined proposition wagering system including a process controller operatively connected to a chance-based controller and operatively connected to an interactive controller may provide for simplified communication protocols for communications of the interactive controller as the interactive controller may communicate interactions with an interactive application provided by the interactive controller to the process controller without regard to a nature of a chance-based proposition to be combined proposition with processes of the interactive application.
In various embodiments, a billiard combined proposition wagering system including a process controller operatively connected to a chance-based controller and operatively connected to an interactive controller may provide for simplified communication protocols for communications of the chance-based controller as the chance-based controller may receive requests and communicate chance outcomes without regard to a nature of an interactive application provided by the interactive controller.
In some embodiments, a billiard combined proposition wagering system including a process controller operatively connecting a chance-based controller to an interactive controller may provide for reduced processing requirement for the interactive controller by offloading the execution of a random number generator from the interactive controller to the chance-based controller. In various such embodiments, additional processing resources may be made available to graphics processing or other processing intensive operations by the interactive controller because of the offloaded random number processing.
In various embodiments, a billiard combined proposition wagering system including a process controller operatively connecting a chance-based controller to an interactive controller provides for operation of the interactive controller in an unsecure location or manner, while providing for operation of the chance-based controller in a secure location or manner.
In some embodiments, a billiard combined proposition wagering system including a process controller operatively connecting a chance-based controller to an interactive controller allows the combined proposition wagering system to have regulated components coupled to unregulated components in a heterogeneous regulated environment. For example, in several such embodiments, the interactive controller may be a device that is not regulated by a wagering regulatory agency whereas the chance-based controller is regulated by the wagering regulatory agency. A process controller of a billiard combined proposition wagering system may provide for isolation of the processing of the interactive controller from the processing of the chance-based controller. In such a heterogeneous regulatory environment, the process controller may or may not be itself a regulated by the wagering regulatory authority. In addition, components of an interactive application executed by the interactive controller may be either regulated or unregulated by the wagering regulatory agency.
Billiard Wagering Combined Proposition Systems
In some embodiments, a billiard combined proposition wagering system includes a session/management controller 150 operatively connected to one or more other components of the billiard combined proposition wagering system.
In many embodiments, a billiard combined proposition wagering system includes a credit processing system 198 operatively connected to one or more other components of the billiard combined proposition wagering system.
In various embodiments, the chance-based controller 102 includes one or more interfaces, such as interfaces 168, 169 and 190, that operatively connect the chance-based controller 102 to one or more session management servers, such as session/management controller 150, to one or more process controllers, such as process controller 112, and/or to a credit processing system 198, by their respective interfaces.
In some embodiments, one or more of the chance-based controller interfaces implement a chance-based controller interprocess communication protocol so that the chance-based controller 102 and one or more process controllers, one or more credit processing systems and/or one or more session/management controllers may be implemented on the same device. In operation, the chance-based controller interfaces provide application programming interfaces or the like that are used by the chance-based controller to communicate outgoing data and receive incoming data by passing parameter data to another process or application running on the same device.
In some embodiments, one or more of the chance-based controller interfaces implement a chance-based controller communication protocol employing an interdevice communication protocol so that the chance-based controller may be implemented on a device separate from one or more process controllers, one or more credit processing systems and/or one or more session/management controllers. The interdevice protocol may utilize a wired communication bus or wireless connection as a physical layer.
In various embodiments, one or more of the chance-based controller interfaces implement a chance-based controller communication protocol employing a networking protocol so that the chance-based controller may be operatively connected to one or more session/management controllers, one or more credit processing systems and/or one or more process controllers by a network. The networking protocol may utilize a wired communication bus or wireless connection as a physical layer. In many such embodiments, the networking protocol operates over a computer network and/or a telephone network or the like. During operation, the one or more chance-based controller interfaces communicate outgoing data to an external device or server by encoding the data into a signal and transmitting the signal to the external device or server. The one or more chance-based controller interfaces receive incoming data from an external device or server by receiving a signal transmitted by the external device or server and decoding the signal to obtain the incoming data.
In several embodiments, the chance-based controller 102 is a controller for providing one or more chance-based propositions provided by the billiard combined proposition wagering system 128 and automatically determines chance outcomes in accordance with the chance-based propositions as instructed by the process controller 112. Types of value utilized in a chance-based proposition can be one or more of several different types. Types of value of a chance-based proposition can include, but are not limited to, a chance-based proposition of an amount of credits corresponding to a real currency or a virtual currency, a chance-based proposition of an amount of application credits earned through interaction with an interactive application, a chance-based proposition of an amount of interactive elements of an interactive application, and a chance-based proposition of an amount of objects used in an interactive application. A chance outcome determined for a chance-based proposition can increase or decrease an amount of the type of value used in the chance-based proposition, such as, but not limited to, increasing or decreasing an amount of credits for a chance-based proposition of credits. In various embodiments, a chance outcome determined for a chance-based proposition can increase or decrease an amount of a type of value that is different than a type of value of the chance-based proposition, such as, but not limited to, increasing an amount of an object of an interactive application for a chance-based proposition of credits.
In many embodiments, the chance-based controller 102 includes one or more random number generators (RNGs) 106 for generating random results, one or more paytables 108 for determining a chance outcome from the random results, and one or more credit meters 110 for storing data about amounts of stored, wagered and won credits.
In several embodiments, the chance-based controller 102 is operatively connected to the credit processing system 198 via interface 190. The chance-based controller 102 communicates with the credit processing system 198 to receive incoming credit data 194 from the credit processing system 198. The chance-based controller 102 uses the incoming credit data 194 to transfer credits into the billiard combined proposition wagering system and onto the one or more credit meters 110. The chance-based controller 102 communicates outgoing credit data 192 to the credit processing system 198 to transfer credits off of the one or more credit meters 110 and out of the billiard combined proposition wagering system.
In many embodiments, the credit processing system 198 includes one or more credit input devices for generating incoming credit data 192 from a credit input. Credit inputs can include, but are not limited to, credit items used to transfer credits. The incoming credit data 194 are communicated to the chance-based controller 102. In various embodiments, the one or more credit input devices and their corresponding credit items include, but are not limited to: card readers for reading cards having magnetic stripes, RFID chips, smart chips, and the like; scanners for reading various types of printed indicia printed on to various types of media such as vouchers, coupons, ticket-in-ticket-out (TITO) tickets, rewritable cards, or the like; and bill validator and/or coin validators that receive and validate paper and/or coin currency or tokens.
In various embodiments, the credit processing system 198 includes one or more credit output devices for generating a credit output based on outgoing credit data 192 communicated from the chance-based controller. Credit outputs can include, but are not limited to, credit items used to transfer credits. Types of credit output devices and their corresponding credit items may include, but are not limited to: writing devices that are used to write to cards having magnetic stripes, smart chips or the like; printers for printing various types of printed indicia onto vouchers, coupons, TITO tickets, vouchers, rewritable cards or the like; and bill and/or coin dispensers that output paper and/or coin currency or tokens.
In some embodiments, the credit processing system 198 are operatively connected to, and communicate with, a TITO controller or the like to determine incoming credit data 194 representing amounts of credits to be transferred into the billiard combined proposition wagering system and to determine outgoing credit data 192 representing amounts of credits to be transferred out of the billiard combined proposition wagering system. In operation, the credit processing system 198 communicate with a connected credit input device, such as a bill validator/ticket scanner, used to scan a credit input in the form of a TITO ticket having indicia of credit account data of a credit account of the TITO controller. The credit processing system 198 communicates the credit account data to the TITO controller. The TITO controller uses the credit account data to determine an amount of credits to transfer to the credit processing system 198, and thus to the chance-based controller 102 of the billiard combined proposition wagering system 128. The TITO controller communicates the amount of credits to the credit processing system 198. The credit processing system 198 communicates the amount of credits as incoming credit data 194 to the chance-based controller 102 and the chance-based controller 102 credits one or more credit meters with the amount of credits so that the credits can be used when a user makes wagers using the billiard combined proposition wagering system 128.
In many embodiments, the credit processing system 198 includes a bill validator/ticket scanner as one of the one or more credit input devices. The credit processing system 198 communicates with the bill validator/ticket scanner to scan currency used as a credit input to determine an amount of credits as incoming credit data 194 to transfer credit to one or more credit meters 110 associated with one or more users. The chance-based controller 102 credits the one or more credit meters 110 with the amount of credits so that the credits can be used when a user makes wagers using the billiard combined proposition wagering system 128.
In some embodiments, the credit processing system 198 can use a TITO controller along with a ticket or voucher printer as one of the one or more credit output devices to generate a TITO ticket as a credit output for a user. In operation, the credit processing system 198 communicates, as outgoing credit data 192, data of an amount of credits to be credited to a credit account on the TITO controller. The TITO controller receives the amount of credits and creates the credit account and credits the credit account with the amount of credits. The TITO controller generates credit account data for the credit account and communicates the credit account data to the credit processing system 198. The credit processing system 198 uses the ticket or voucher printer to print indicia of the credit account data onto a TITO ticket as a credit output.
In various embodiments, the credit processing system 198 provides an interface to an electronic payment management system (not shown) such an electronic wallet or the like. The electronic payment system provides credit account data that is used for generating incoming credit data 194 as a credit input and outgoing credit data 192 as a credit output.
In several embodiments, during operation, the chance-based controller 102 communicates with the credit processing system 198 to receive incoming credit data 194 from the credit processing system 198 and adds credits onto the one or more credit meters 110 at least partially on the basis of the incoming credit data 194. The one or more RNGs 106 execute processes that generate random results. The chance-based controller uses the one or more paytables 108 to map the random results to a chance outcome. The chance-based controller 102 adds credits to, or deducts credits from, the one or more credit meters 110 based in part on the chance outcome. For example, in some embodiments, the chance-based controller 102 adds an amount of credits to the one or more credit meters 110 when the chance outcome indicates a win and deducts an amount of credits from the one or more credit meters 110 when the chance outcome indicates a loss or a partial win. At an end of a wagering session, the chance-based controller 102 transfers credits off of the one or more credit meters 110 and out of the billiard combined proposition wagering system by communicating outgoing credit data 192 to the credit processing system 198.
In various embodiments, the chance-based controller 102 includes one or more paytables 108. The one or more paytables 108 are used to implement one or more chance-based propositions in conjunction with one or more random outputs of the one or more RNGs 106.
In many embodiments, the chance-based controller 102 generates random numbers by continuously generating pseudo random numbers using a pseudo random number generator. A most current pseudo random number is stored in a buffer thus constantly refreshing the buffer. In many embodiments, the buffer is refreshed at a rate exceeding 100 times per second. When the chance-based controller receives a request for a chance outcome, the chance-based controller retrieves the stored most current pseudo random number from the buffer. As timing between requests for a chance outcome is not deterministic, the resulting output from the buffer is a random number. The random number is used along with a paytable that the chance-based controller selects from the one or more paytables 108. The selected paytable includes a mapping of values in a range of values of the random number to specified multipliers to be applied to an amount of credits to determine an amount of credits to be added to one or more credit meters associated with the chance-based proposition. A multiplier is selected from the paytable based on the random number and the selected multiplier is used along with an amount of credits to determine a chance outcome as an amount of credits.
In various embodiments, a chance outcome can include, but is not limited to, an amount of credits, application credits, and/or interactive elements or objects won as a function of the billiard combined proposition wagering system use and a type and amount of credits, application credits and/or interactive application objects wagered. A multiplier taken from the one or more paytables 108 is applied to the amount of credits, application credits and/or interactive application objects wagered and the resultant outcome is a chance outcome for a chance-based proposition.
In some embodiments, a range of the value of the random number is mapped to one or more symbols representing one or more random elements of a traditional chance-based proposition, and the mapped to one or more symbols are used in conjunction with a paytable selected from the one or more paytables 108. In one such embodiment, a random number is mapped to a virtual card of a deck of virtual cards. In another such embodiment, the random number is mapped to a virtual face of a virtual die. In yet another such embodiment, the random number is mapped to symbol of a virtual reel strip on a virtual reel slot machine. In yet another such embodiment, the random number is mapped to a pocket of a virtual roulette wheel. In some embodiments, two or more random numbers are mapped to appropriate symbols to represent a completed chance-based proposition. In one such embodiment, two or more random numbers are mapped to faces of two or more virtual dice to simulate a random outcome generated by throwing two or more dice. In another such embodiment, multiple random numbers are mapped to virtual cards from a virtual deck of cards without replacement. In yet another such embodiment, two or more random numbers are mapped to two or more virtual reel strips to create stop positions for a virtual multi-reel slot machine.
In some embodiments, a chance-based controller resolves a chance proposition by executing chance proposition determination commands that define processes of a chance-based proposition where the chance proposition determination commands are formatted in a scripting language. In operation, a decision engine of a process controller generates the chance proposition determination commands in the form of a script written in the scripting language. The script includes the chance proposition determination commands that describe how the chance-based controller is to resolve the chance-based proposition. The completed script is encoded as chance proposition determination command data and communicated to the chance-based controller by the process controller. The chance-based controller receives the chance proposition determination command data and parses the script encoded in the chance proposition determination command data and executes the commands included in the script to resolve the chance-based proposition to determine a chance outcome.
In some embodiments, a chance-based controller resolves a chance-based proposition by executing chance proposition determination commands that define processes of the wagering user interface. In operation, a decision engine of a process controller generates the chance proposition determination commands and encodes the chance proposition determination commands into chance proposition determination command data that are communicated to the chance-based controller by the process controller. The chance-based controller receives the chance proposition determination command data and executes the commands encoded in the chance proposition determination command data to resolve the chance-based proposition.
In various embodiments, the interactive controller 120 executes an interactive application 143 and provides one or more user interface input and output devices 103 so that a user can interact with the interactive application 143. In various embodiments, user interface input devices include, but are not limited to: buttons or keys; keyboards; keypads; game controllers; joysticks; computer mice; track balls; track buttons; touch pads; touch screens; accelerometers; motion sensors; video input devices; microphones; and the like. In various embodiments, user interface output devices include, but are not limited to: audio output devices such as speakers, headphones, earbuds, and the like; visual output devices such as lights, video displays and the like; and tactile devices such as rumble pads, hepatic touch screens, buttons, keys and the like. The interactive controller 120 provides for user interactions with the interactive application 143 by executing the interactive application 143 that generates an application interface 105 that utilizes the user interface input devices 103 to detect user interactions with the interactive controller and generates an interactive user interface that is presented to the user utilizing the user interface output devices.
In some embodiments, one or more components an interactive controller are housed in an enclosure such as a housing, cabinet, casing or the like. The enclosure further includes one or more user accessible openings or surfaces that constructed to mount the user interface input devices and/or the user interface output devices 103.
The interactive controller 120 is operatively connected to, and communicates with, the process controller 112. The interactive controller communicates application telemetry data 124 and skill outcome data 125 to the process controller 112 and receives skill proposition data, application instruction data and resource data 136 from the process controller 112. Via the communication of the skill proposition data, application instruction data, and/or resource data 136, the process controller 112 can control the operation of the interactive controller 120 by communicating control parameters to the interactive application 143 during the interactive application's execution by the interactive controller 120.
In some embodiments, during execution of the interactive application 143 by the interactive controller 120, the interactive controller 120 communicates, as application telemetry data 124, user interactions with the application user interface 105 of the interactive application to the process controller 112. The application telemetry data 124 includes, but is not limited to, utilization of the interactive elements in the interactive application 143.
In some embodiments, the interactive application 143 is a skill-based interactive application. In such embodiments, execution of the skill-based interactive application 143 by the interactive controller 120 is based on a user's skillful interaction with the skill-based interactive application, such as, but not limited to, the user's utilization of the interactive elements of the skill-based interactive application during the user's skillful interaction with the skill-based interactive application. In such an embodiment, the process controller 112 communicates with the interactive controller 120 in order to allow the coupling of the skill-based interactive application to chance outcomes determined in accordance with a chance-based proposition of the chance-based controller 102. In some embodiments, the skill-based interactive application determines skill outcomes 125 based on a skill proposition and a user's skillful interactions with the skill-based interactive application. The skill outcomes 125 are communicated to the process controller 112.
In some embodiments, the interactive controller 120 includes one or more sensors 138 that sense various aspects of the physical environment of the interactive controller 120. Examples of sensors include, but are not limited to: global positioning sensors (GPSs) for sensing communications from a GPS system to determine a position or location of the interactive controller; temperature sensors; accelerometers; pressure sensors; and the like. Sensor telemetry data 133 is communicated by the interactive controller to the process controller 112 as part of the application telemetry data 124. The process controller 112 receives the sensor telemetry data 133 and uses the sensor telemetry data to make chance-based proposition decisions.
In many embodiments, the interactive controller 120 includes a wagering user interface 148 used to display wagering data, via one or more of the user interface input and output devices 103, to one or more users.
In various embodiments, an application control interface 131 resident in the interactive controller 120 provides an interface between the interactive controller 120 and the process controller 112.
In some embodiments, the application control interface 131 implements an interactive controller to process controller communication protocol employing an interprocess communication protocol so that the interactive controller and the process controller may be implemented on the same device. In operation, the application control interface 131 provides application programming interfaces that are used by the interactive processing application 143 of the interactive controller 120 to communicate outgoing data and receive incoming data by passing parameter data to another process or application.
In some embodiments, the application control interface 131 implements an interactive controller to process controller communication protocol employing an interdevice communication protocol so that the interactive controller and the process controller may be implemented on different devices. The interdevice protocol may utilize a wired communication bus or wireless connection as a physical layer.
In various embodiments, the application control interface 131 implements an interactive controller to process controller communication protocol employing a networking protocol so that the interactive controller and the process controller may be implemented on different devices connected by a network. The networking protocol may utilize a wired communication bus or wireless connection as a physical layer. In many such embodiments, the network includes a cellular telephone network or the like and the interactive controller is a mobile device such as a smartphone or other device capable of using the telephone network. During operation, the application control interface 131 communicates outgoing data to an external device by encoding the data into a signal and transmitting the signal to an external device. The application control interface receives incoming data from an external device by receiving a signal transmitted by the external device and decoding the signal to obtain the incoming data.
In various embodiments, the process controller 112 includes one or more interfaces, 162, 163 and 164, that operatively connect the process controller 112 to one or more interactive controllers, such as interactive controller 120, to one or more session management servers, such as session/management controller 150, and/or to one or more chance-based controllers, such as chance-based controller 102, respectively.
In some embodiments, one or more of the process controller interfaces implement a process controller to device or server communication protocol employing an interprocess communication protocol so that the process controller and one or more of an interactive controller, a chance-based controller, and/or a session/management controller may be implemented on the same device. In operation, the process controller interfaces provide application programming interfaces or the like that are used by the process controller to communicate outgoing data and receive incoming data by passing parameter data to another process or application running on the same device.
In some embodiments, one or more of the process controller interfaces implement a process controller communication protocol employing an interdevice communication protocol so that the process controller may be implemented on a device separate from the one or more interactive controllers, the one or more session/management controllers and/or the one or more chance-based controllers. The interdevice protocol may utilize a wired communication bus or wireless connection as a physical layer. In various embodiments, one or more of the process controller interfaces implement a process controller communication protocol employing a networking protocol so that the process controller may be operatively connected to the one or more interactive controllers, the one or more session/management controllers, and/or the one or more chance-based controllers by a network. The networking protocol may utilize a wired communication bus or wireless connection as a physical layer. In many such embodiments, the network includes a cellular telephone network or the like and the one or more interactive controllers include a mobile device such as a smartphone or other device capable of using the telephone network. During operation, the one or more process controller interfaces communicate outgoing data to an external device or server by encoding the data into a signal and transmitting the signal to the external device or server. The one or more process controller interfaces receive incoming data from an external device or server by receiving a signal transmitted by the external device or server and decoding the signal to obtain the incoming data.
In many embodiments, process controller 112 provides an interface between the interactive application 143 provided by the interactive controller 120 and a chance-based proposition provided by the chance-based controller 102.
The process controller 112 includes a rule-based decision engine 122 that receives telemetry data, such as application telemetry data 124, skill outcome data 125, and sensor telemetry data 133, from the interactive controller 120. The rule-based decision engine 122 has combined wager logic 127 including skill proposition logic 132 and chance proposition logic 126. The decision engine 122 uses the telemetry data, along with chance proposition logic 126 to generate chance proposition determination commands 129 that are used by the process controller 112 to command the chance-based controller 102 to resolve a chance-based proposition. The chance proposition determination command data is communicated by the process controller 112 to the chance-based controller 102. The chance-based controller 102 receives the chance proposition determination command data 129 and automatically resolves a chance-based proposition to determine a chance outcome in accordance with the chance proposition determination command data 129.
In an embodiment, the application telemetry data 124 used by the decision engine 122 encodes data about the operation of the interactive application 143 executed by the interactive controller 120.
In some embodiments, the application telemetry data 124 encodes interactions of a user, such as a user's interaction with an interactive element of the interactive application 143.
In many embodiments, the application telemetry data 124 includes a state of the interactive application 143, such as values of variables that change as the interactive application 143 executes.
In several embodiments, the decision engine 122 includes one or more rules as part of chance proposition logic 126 used by the decision engine 122 to determine when a chance-based proposition should be automatically resolved. Each rule includes one or more variable values constituting a pattern that is to be matched by the process controller 112 using the decision engine 122 to one or more variable values encoded in the application telemetry data 124. Each rule also includes one or more actions that are to be taken if the pattern is matched. Actions can include automatically generating chance proposition determination command data 129 and communicating the chance proposition determination command data 129 to the chance-based controller 102, thus commanding the chance-based controller to automatically resolve a chance-based proposition as described herein. During operation, the decision engine 122 receives application telemetry data 124 from the interactive controller 124 via interface 160. The decision engine 122 performs a matching process of matching the variable values encoded in the application telemetry data 124 to one or more variable patterns of one or more rules. If a match between the variable values and a pattern of a rule is determined, then the process controller 112 performs the action of the matched rule.
In some embodiments, the application telemetry data 124 includes, but is not limited to, application environment variables that indicate a state of the interactive application 143, interactive controller data indicating a state of the interactive controller 120, and interactions with the interactive application 143 during execution of the interactive application 143 by the interactive controller 120. The chance proposition determination command data 129 may include, but are not limited to, an amount and type of the chance-based proposition, a request for resolution of the chance-based proposition, and a selection of a paytable to be used when resolving the chance-based proposition.
In some embodiments, the process controller 112 receives chance outcome data 130 from the chance-based controller 102. The decision engine 122 uses the chance outcome data 130, in conjunction with the telemetry data 124 and skill proposition logic 132, to automatically generate skill proposition data, interactive application instruction data, and/or resource data 136 that the process controller 112 communicates to the interactive controller 120 via interfaces 160 and 131.
In an embodiment, the chance outcome data 130 used by a decision engine encodes data about the resolution of a chance-based proposition resolved by the chance-based controller 102. In some embodiments, the chance outcome data 130 encodes values of variables including an amount of credits wagered, an amount of credits won and values of credits stored in the one or more meters 110 of the chance-based controller. In many embodiments, the chance outcome data includes a state of the chance-based controller 102, such as values of variables that change as the chance-based controller 102 resolves chance-based propositions. The decision engine 122 includes one or more rules as part of skill proposition logic 132 used by the decision engine 122 to automatically generate the skill proposition data, interactive application instruction data, and/or resource data 136 that is then communicated to the interactive controller 120. Each rule includes one or more variable values constituting a pattern that is to be matched to one or more variable values encoded in the chance outcome data 130. Each rule also includes one or more actions that are to be automatically taken by the process controller 112 if the pattern is matched. Actions can include automatically generating skill proposition data, interactive application instruction data, and/or resource data 136 and using the skill proposition data, interactive application instruction data, and/or resource data 136 to control the interactive controller 120 to affect execution of the interactive application 143 as described herein. During operation, the process controller 112 receives the chance outcome data 130 from the chance-based controller 102 via interface 162. The process controller 112 uses the decision engine 122 to match the variable values encoded in the chance outcome data to one or more patterns of one or more rules of the skill proposition logic 132. If a match between the variable values and a pattern of a rule is found, then the process controller automatically performs the action of the matched rule. In some embodiments, the process controller 112 uses the application telemetry data 124 received from the interactive controller 120 in conjunction with the chance outcome data 130 to generate the interactive application instruction and resource data 136.
The interactive controller receives the skill proposition data, interactive application command data, and resource data 136 and automatically uses the skill proposition data, interactive application instruction data, and/or resource data 136 to configure and command the processes of the interactive application 143.
In some embodiments, the interactive application 143 operates utilizing a scripting language. The interactive application 143 parses scripts written in the scripting language and executes commands encoded in the scripts and sets variable values as defined in the scripts. In operation of such embodiments, the process controller 112 automatically generates skill proposition data, interactive application instruction data, and/or resource data 136 in the form of scripts written in the scripting language that are communicated to the interactive controller 120 during execution of the interactive application 143. The interactive controller 120 receives the scripts and passes them to the interactive application 143. The interactive application 143 receives the scripts, parses the scripts and automatically executes the commands and sets the variable values as encoded in the scripts.
In many embodiments, the interactive application 143 automatically performs processes as instructed by commands communicated from the process controller 112. The commands command the interactive application 143 to perform specified operations such as executing specified commands and/or setting the values of variables utilized by the interactive application 143. In operation of such embodiments, the process controller 112 automatically generates commands that are encoded into the skill proposition data, interactive application instruction data, and/or resource data 136 that are communicated to the interactive controller 120. The interactive controller 120 passes the skill proposition data, interactive application instruction data, and/or resource data 136 to the interactive application 143. The interactive application parses the skill proposition data, interactive application instruction data, and/or resource data and automatically performs operations in accordance with the commands encoded in the skill proposition data, interactive application instruction data, and/or resource data 136.
In many embodiments, the process controller 112 includes a pseudo random or random result generator used to generate random results that are used by the decision engine 122 to generate portions of the skill proposition data, interactive application instruction data, and/or resource data 136.
The interactive application 143 uses the skill proposition data, interactive application instruction data, and/or resource data 136 to generate a skill proposition presented to the user as an application user interface 105 using one or more output devices of the user interface and output device(s) 103. The user skillfully interacts with the application user interface 105 using one or more of input devices of the user interface input and output devices 103. The interactive application 143 determines a skill outcome based on the skillful interactions of the player and communicates data of the determined skill outcome 125 to the process controller 112. In some embodiments, the interactive application 143 also communicates application telemetry data 124 encoding the user's interactions with the interactive application 143.
In various embodiments, the process controller 112 uses the rule-based decision engine 122 to automatically determine an amount of application credits to award based at least in part on the skill outcome data 125 and interactions with the interactive application 143 of the billiard combined proposition wagering system as determined by the process controller 112 from the application telemetry data 124. In some embodiments, the process controller 112 may also use the chance outcome data 130 to determine the amount of application credits that should be awarded. In numerous embodiments, the interactive application 143 is a skill-based interactive application and the application credits is awarded for skillful interaction with the interactive application.
In various embodiments, the process controller 112 uses the decision engine 122 along with combined proposition logic 127 to determine a combined wagering outcome 135 that is communicated to the wagering interface generator 144. The combined wagering outcome is determined on the basis of the skill outcome data 125 received from the interactive controller 120 and the chance outcome data 130 received from the chance-based controller 102.
The process controller 1112 uses the wagering user interface generator 144 to automatically generate wagering telemetry data 146 on the basis of the combined wagering outcome 135. The wagering telemetry data 146 is used by the process controller 112 to command the interactive controller 120 to automatically generate a wagering user interface 148 describing a state of wagered credit accumulation and loss for the billiard combined proposition wagering system.
In some embodiments, the wagering telemetry data 146 may include, but is not limited to, amounts of application credits and interactive elements earned, lost or accumulated through interaction with interactive application, and credits, application credits and interactive elements amounts won, lost or accumulated.
In some embodiments, the skill proposition data, interactive application instruction data, and/or resource data 136 are communicated to the wagering user interface generator 144 and used as a partial basis for generation of the wagering telemetry data 146 communicated to the interactive controller 120.
In various embodiments, the wagering user interface generator 144 also receives chance outcome data 130 that is used as a partial basis for generation of the wagering telemetry data 146 communicated to the interactive controller 120. In some embodiments, the chance outcome data 130 also includes data about one or more states of a chance-based proposition as resolved by the chance-based controller 102. In various such embodiments, the wagering user interface generator 144 generates a wagering process display and/or wagering state display using the one or more states of the chance-based proposition. The wagering process display and/or wagering state display is included in the wagering telemetry data 146 that is communicated to the interactive controller 120. The wagering process display and/or wagering state display is automatically displayed by the interactive controller 120 using the wagering user interface 148. In other such embodiments, the one or more states of the chance-based proposition are communicated to the interactive controller 120 and the interactive controller 120 is instructed to automatically generate the wagering process display and/or wagering state display of the wagering user interface 148 using the one or more states of the chance-based proposition for display.
In some embodiments, the chance outcome data 130 includes game state data about resolution of the chance-based proposition, including but not limited to a final state, intermediate state and/or beginning state of the chance-based proposition. For example, in a chance-based proposition that is based on slot machine math, the final state of the chance-based proposition may be reel positions, in a chance-based proposition that is based on roulette wheel math, the final state may be a pocket where a ball may have come to rest, in a chance-based proposition that is a based on card math, the beginning, intermediate and final states may represent a sequence of cards being drawn from a deck of cards, etc.
In some embodiments, the interactive controller 120 generates a wagering user interface by executing commands that define processes of the wagering user interface where the commands are formatted in a scripting language. In operation, a wagering user interface generator of a process controller generates commands in the form of a script written in the scripting language. The script includes commands that describe how the interactive controller is to display combined wagering outcome data. The completed script is encoded as wagering telemetry data and communicated to the interactive controller by the process controller. The interactive controller receives the wagering telemetry data and parses the script encoded in the wagering telemetry data and executes the commands included in the script to generate the wagering user interface.
In many embodiments, an interactive controller generates a wagering user interface based on a document written in a document markup language that includes commands that define processes of the wagering user interface. In operation, a wagering user interface generator of a process controller generates a document composed in the document markup language. The document includes commands that describe how the interactive controller is to display combined wagering outcome data. The completed document is encoded as wagering telemetry data and communicated to the interactive controller by the process controller. The interactive controller receives the wagering telemetry data and parses the document encoded in the wagering telemetry data and executes the commands encoded into the document to generate the wagering user interface.
In some embodiments, an interactive controller generates a wagering user interface by executing commands that define processes of the wagering user interface. In operation, a wagering user interface generator of a process controller generates the commands and encodes the commands into wagering telemetry data that is communicated to the interactive controller by the process controller. The interactive controller receives the wagering telemetry data and executes the commands encoded in the wagering telemetry data to generate the wagering user interface.
In various embodiments, an interactive controller includes a data store of graphic and audio display resources that the interactive controller uses to generate a wagering user interface as described herein.
In many embodiments, a process controller communicates graphic and audio display resources as part of wagering telemetry data to an interactive controller. The interactive controller uses the graphic and audio display resources to generate a wagering user interface as described herein.
When a user interacts with the wagering user interface 148, wagering user interface telemetry data is generated by the wagering user interface 148 and communicated by the interactive controller 120 to the process controller 112 using interfaces 131 and 160.
The process controller 112 can further operatively connect to the chance-based controller 102 to determine an amount of credit or interactive elements available and other wagering metrics of a chance-based proposition. Thus, the process controller 112 may affect an amount of credits in play for participation in the a chance-based proposition provided by the chance-based controller 102 in some embodiments. The process controller 112 may additionally include various audit logs and activity meters. In some embodiments, the process controller 112 can also couple to a centralized session and/or management controller 150 for exchanging various data related to the user and the activities of the user during game play of a billiard combined proposition wagering system.
In many embodiments, one or more users can be engaged in using the interactive application 143 executed by the interactive controller 120. In various embodiments, a billiard combined proposition wagering system can include an interactive application 143 that provides a skill-based interactive application that includes head-to-head play between a single user and a computing device, between two or more users against one another, or multiple users playing against a computer device and/or each other. In some embodiments, the interactive application 143 can be a skill-based interactive application where the user is not skillfully playing against the computer or any other user such as skill-based interactive applications where the user is effectively skillfully playing against himself or herself.
In some embodiments, the operation of the process controller 112 does not affect the provision of a chance-based proposition by the chance-based controller 102 except for user choice parameters that are allowable in accordance with the chance-based proposition.
In various embodiments, chance outcome data 130 communicated from the chance-based controller 102 can also be used to convey a status operation of the chance-based controller 102.
In a number of embodiments, communication of the chance proposition determination commands 129 between the chance-based controller 102 and the process controller 112 can further be used to communicate various wagering control factors that the chance-based controller 102 uses as input. Examples of wagering control factors include, but are not limited to, an amount of credits, application credits, interactive elements, or objects consumed per wagering event, and/or the user's election to enter a jackpot round.
In some embodiments, the process controller 112 utilizes the wagering user interface 148 to communicate certain interactive application data to the user, including but not limited to, club points, user status, control of the selection of choices, and messages which a user can find useful in order to adjust the interactive application experience or understand the wagering status of the user in accordance with the chance-based proposition in the chance-based controller 102.
In some embodiments, the process controller 112 utilizes the wagering user interface 148 to communicate aspects of a chance-based proposition to the user including, but not limited to, odds of certain chance outcomes, amount of credits, application credits, interactive elements, or objects in play, and amounts of credits, application credits, interactive elements, or objects available.
In a number of embodiments, the chance-based controller 102 can accept chance-based proposition factors from the process controller 112, including, but not limited to, modifications in the amount of credits, application credits, interactive elements, or objects wagered on each individual wagering event, a number of chance-based propositions per minute the chance-based controller 102 can resolve, entrance into a bonus round, and other factors. An example of a varying a wager amount that the user can choose can include, but is not limited to, using a more difficult interactive application level associated with an amount of a wager. These factors can increase or decrease an amount wagered per individual combination proposition in the same manner that a standard slot machine user can decide to wager more or less credits for each pull of the handle. In several embodiments, the chance-based controller 102 can communicate a number of factors back and forth to the process controller 112, via an interface, such that an increase/decrease in a wagered amount can be related to the change in user profile of the user in the interactive application. In this manner, a user can control a wager amount per wagering event in accordance with the combined proposition with the change mapping to a parameter or component that is applicable to the interactive application experience.
In some embodiments, a session/management controller 150 is used to regulate a billiard combined proposition wagering system session.
In various embodiments, the session/management controller 150 includes one or more interfaces, 165, 166 and 167 that operatively connect the session/management controller 150 to one or more interactive controllers, such as interactive controller 120, to one or more process controllers, such as process controller 112, and/or to one or more chance-based controllers, such as chance-based controller 102, through their respective interfaces.
In some embodiments, one or more of the session/management controller interfaces implement a session/management controller to device or server communication protocol employing an interprocess communication protocol so that the session/management controller and one or more of an interactive controller, a chance-based controller, and/or a process controller may be implemented on the same device. In operation, the session/management controller interfaces provide application programming interfaces or the like that are used by the session/management controller to communicate outgoing data and receive incoming data by passing parameter data to another process or application running on the same device.
In some embodiments, one or more of the session/management controller interfaces implement a session/management controller communication protocol employing an interdevice communication protocol so that the session/management controller may be implemented on a device separate from the one or more interactive controllers, the one or more process controllers and/or the one or more chance-based controllers. The interdevice protocol may utilize a wired communication bus or wireless connection as a physical layer. In various embodiments, one or more of the session/management controller interfaces implement a session/management controller communication protocol employing a networking protocol so that the process session/management controller may be operatively connected to the one or more interactive controllers, the one or more process controllers, and/or the one or more chance-based controllers by a network. The networking protocol may utilize a wired communication bus or wireless connection as a physical layer. In many such embodiments, the network includes a cellular telephone network or the like and the one or more interactive controllers include a mobile device such as a smartphone or other device capable of using the telephone network. During operation, the one or more session/management controller interfaces communicate outgoing data to an external device or server by encoding the data into a signal and transmitting the signal to the external device or server. The one or more session/management controller interfaces receive incoming data from an external device or server by receiving a signal transmitted by the external device or server and decoding the signal to obtain the incoming data.
In various embodiments, the process controller 112 communicates outgoing session data 152 to the session/management controller. The session data 152 may include, but is not limited to, user, interactive controller, process controller and chance-based controller data from the process controller 112. The session/management controller 150 uses the user, interactive controller, process controller and chance-based controller data to regulate a billiard combined proposition wagering system session.
In some embodiments, the session/management controller 150 may also assert control of a billiard combined proposition wagering system session by communicating session control data 154 to the process controller. Such control may include, but is not limited to, commanding the process controller 112 to end a billiard combined proposition wagering system session, initiating wagering in a billiard combined proposition wagering system session, ending wagering in a billiard combined proposition wagering system session but not ending a user's use of the interactive application portion of the billiard combined proposition wagering system, and changing from real credit wagering in a billiard combined proposition wagering system to virtual credit wagering, or vice versa.
In many embodiments, the session/management controller 150 manages user profiles for a plurality of users. The session/management controller 150 stores and manages data about users in order to provide authentication and authorization of users of the billiard combined proposition wagering system 128. In some embodiments, the session/management controller 150 also manages geolocation information to ensure that the billiard combined proposition wagering system 128 is only used by users in jurisdictions were wagering is approved. In various embodiments, the session/management controller 150 stores application credits that are associated with the user's use of the interactive application of the billiard combined proposition wagering system 128.
In some embodiments, the session/management controller 150 communicates user and session management data 155 to the user using a management user interface 157 of the interactive controller. The user 140 interacts with the management user interface 157 and the management user interface generates management telemetry data 159 that is communicated to the session/management controller 150.
In some embodiments, the chance-based controller 102 communicates wagering session data 153 to the session/management controller 150. In various embodiments, the session/management controller communicates wagering session control data 151 to the chance-based controller 102.
In some embodiments, a process controller operates as an interface between an interactive controller and a chance-based controller. By virtue of this construction, the chance-based controller is isolated from the interactive controller allowing the interactive controller to operate in an unregulated environment will allowing the chance-based controller to operate in a regulated environment.
In some embodiments, a single chance-based controller may provide services to two or more interactive controllers and/or two or more process controllers, thus allowing a billiard combined proposition wagering system to operate over a large range of scaling.
In various embodiments, multiple types of interactive controllers using different operating systems may be interfaced to a single type of process controller and/or chance-based controller without requiring customization of the process controller and/or the chance-based controller.
In many embodiments, an interactive controller may be provided as a user device under control of a user while maintaining the chance-based controller in an environment under the control of a regulated operator of wagering equipment.
In several embodiments, data communicated between the controllers may be encrypted to increase security of the billiard combined proposition wagering system.
In some embodiments, a process controller isolates chance proposition logic and skill proposition logic as unregulated logic from a regulated chance-based controller, thus allowing errors in the skill proposition logic and/or chance proposition logic to be corrected, new skill proposition logic and/or chance proposition logic to be used, or modifications to be made to the skill proposition logic and/or chance proposition logic without a need for regulatory approval.
In various embodiments, an interactive application may require extensive processing resources from an interactive controller leaving few processing resources for the functions performed by a process controller and/or a chance-based controller. By virtue of the architecture described herein, processing loads may be distributed across multiple devices such that operations of the interactive controller may be dedicated to the interactive application and the processes of the process controller and/or chance-based controller are not burdened by the requirements of the interactive application.
In many embodiments, a billiard combined proposition wagering system operates with its components being distributed across multiple devices. These devices can be connected by communication channels including, but not limited to, local area networks, wide area networks, local communication buses, and/or the like. The devices may communicate using various types of protocols, including but not limited to, networking protocols, device-to-device communications protocols, and the like.
In some embodiments, one or more components of a billiard combined proposition wagering system are distributed in close proximity to each other and communicate using a local area network and/or a communication bus. In several embodiments, an interactive controller and a process controller of a billiard combined proposition wagering system are in a common location and communicate with an external chance-based controller. In some embodiments, a process controller and a chance-based controller of a billiard combined proposition wagering system are in a common location and communicate with an external interactive controller. In many embodiments, an interactive controller, a process controller, and a chance-based controller of a billiard combined proposition wagering system are located in a common location. In some embodiments, a session/management controller is located in a common location with a process controller and/or a chance-based controller.
In various embodiments, these multiple devices can be constructed from or configured using a single device or a plurality of devices such that a billiard combined proposition wagering system is executed as a system in a virtualized space such as, but not limited to, where a chance-based controller and a process controller are large scale centralized servers in the cloud operatively connected to widely distributed interactive controllers via a wide area network such as the Internet or a local area network. In such embodiments, the components of a billiard combined proposition wagering system may communicate using a networking protocol or other type of device-to-device communications protocol.
In some embodiments, a billiard combined proposition wagering system is deployed over a local area network or a wide area network in an interactive configuration. An interactive configuration of a billiard combined proposition wagering system includes an interactive controller operatively connected by a network to a process controller and a chance-based controller.
In some embodiments, a billiard combined proposition wagering system is deployed over a local area network or a wide area network in a mobile configuration. A mobile configuration of a billiard combined proposition wagering system is useful for deployment over wireless communication network, such as a wireless local area network or a wireless telecommunications network. A mobile configuration of a billiard combined proposition wagering system 194 includes an interactive controller operatively connected by a wireless network to a process controller and a chance-based controller.
In many embodiments, a centralized chance-based controller is operatively connected to, and communicates with, one or more process controllers using a communication link. The centralized chance-based controller can generate chance outcomes for wagers in accordance with one or more chance-based propositions. The centralized chance-based controller can resolve a number of simultaneous or pseudo-simultaneous chance-based propositions in order to generate chance outcomes for a variety of chance-based propositions that one or more distributed billiard combined proposition wagering systems can use.
In several embodiments, a centralized process controller is operatively connected to one or more interactive controllers and one or more chance-based controllers using a communication link. The centralized process controller can perform the functionality of a process controller across various billiard combined proposition wagering systems.
In numerous embodiments, an interactive application server provides a host for managing head-to-head play operating over a network of interactive controllers connected to the interactive application server using a communication link. The interactive application server provides an environment where users can compete directly with one another and interact with other users.
In many embodiments, the process controller 172 is operatively connected to an external session/management controller (not shown). The session/management controller may provide session control for a wagering session or may provide services for management of a player account for the storage of player points, application credits and the like.
In various embodiments, the chance-based controller 173 is operatively connected to a credit processing system 175. In many embodiments, the credit processing system 175 includes one or more credit input devices 180 for generating incoming credit data from a credit input. Credit inputs can include, but are not limited to, credit items used to transfer credits. The incoming credit data are communicated to the chance-based controller 173. In various embodiments, the one or more credit input devices and their corresponding credit items include, but are not limited to: card readers for reading cards having magnetic stripes, RFID chips, smart chips, and the like; scanners for reading various types of printed indicia printed on to various types of media such as vouchers, coupons, TITO tickets, rewritable cards, or the like; and bill validators and/or coin validators that receive and validate paper and/or coin currency or tokens.
In various embodiments, the credit processing system 175 includes one or more credit output devices 182 for generating a credit output based on outgoing credit data communicated from the chance-based controller 173. Credit outputs can include, but are not limited to, credit items used to transfer credits. Types of credit output devices and their corresponding credit items may include, but are not limited to: writing devices that are used to write to cards having magnetic stripes, smart chips or the like; printers for printing various types of printed indicia onto vouchers, coupons, TITO tickets, vouchers, rewritable cards or the like; and bill and/or coin dispensers that output paper and/or coin currency or tokens.
In some embodiments, the chance-based controller 173 and/or the credit processing system 175 is operatively connected to, and communicates with, a TITO controller (not shown) or the like to determine incoming credit data representing amounts of credits to be transferred into the billiard combined proposition wagering system 170 and to determine outgoing credit data representing amounts of credits to be transferred out of the billiard combined proposition wagering system 170. In operation, the credit processing system 175 communicates with one of the one or more connected credit input devices 180, such as a bill validator/ticket scanner, used to scan a credit input in the form of a TITO ticket having indicia of credit account data of a credit account of the TITO controller. The credit processing system 175 communicates the credit account data to the TITO controller. The TITO controller uses the credit account data to determine an amount of credits to transfer to the credit processing system 175, and thus to the chance-based controller 173 of the billiard combined proposition wagering system 128. The TITO controller communicates the amount of credits to the credit processing system 175. The credit processing system 175 communicates the amount of credits as incoming credit data to the chance-based controller 173 and the chance-based controller 173 credits one or more credit meters with the amount of credits so that the credits can be used when a user makes wagers using the billiard combined proposition wagering system 170.
In many embodiments, the credit processing system 175 includes a bill validator/ticket scanner as one of the one or more credit input devices 180. The credit processing system 175 communicates with the bill validator/ticket scanner to scan currency used as a credit input to determine an amount of credits as incoming credit data to transfer credit to one or more credit meters associated with one or more users. The chance-based controller 173 credits the one or more credit meters with the amount of credits so that the credits can be used when a user makes wagers using the billiard combined proposition wagering system 170.
In some embodiments, the credit processing system 175 can use a TITO controller along with a ticket or voucher printer as one of the one or more credit output devices 182 to generate a TITO ticket as a credit output for a user. In operation, the credit processing system 175 communicates, as outgoing credit data, data of an amount of credits to be credited to a credit account on the TITO controller. The TITO controller receives the amount of credits and creates the credit account and credits the credit account with the amount of credits. The TITO controller generates credit account data for the credit account and communicates the credit account data to the credit processing system 175. The credit processing system 175 uses the ticket or voucher printer to print indicia of the credit account data onto a TITO ticket as a credit output.
In various embodiments, the credit processing system provides an interface to an electronic payment management system (not shown) such an electronic wallet or the like. The electronic payment system provides credit account data that is used for generating incoming credit data as a credit input and outgoing credit data as a credit output.
In some embodiments, the chance-based controller 173 is further operatively connected to a central determination controller (not shown). In operation, when the chance-based controller 173 needs to determine a chance outcome, the chance-based controller 173 communicates a request to the central determination controller for the chance outcome. The central determination controller receives the chance outcome request and generates a chance outcome in response to the chance outcome request. The central determination controller communicates data of the chance outcome to the chance-based controller 173. The chance-based controller 173 receives the data of the chance outcome and utilizes the chance outcome as described herein. In some embodiments, the chance outcome is drawn from a pool of pre-determined chance outcomes. In some embodiments, the chance outcome is a random result that is utilized by the chance-based controller along with paytables to determine a chance outcome as described herein.
In various embodiments, the chance-based controller 173 may be operatively connected to a progressive controller along (not shown) with one or more other chance-based controllers of one or more other billiard combined proposition wagering systems. The progressive controller provides services for the collection and provision of credits used by the chance-based controller 173 to provide chance outcomes that have a progressive or pooling component.
In some embodiments, an interactive controller may be constructed from or configured using an electronic gaming machine 200 as shown in
In many embodiments, an interactive controller may be constructed from or configured using a portable device 202 as shown in
In some embodiments, an interactive controller may be constructed from or configured using a gaming console 204 as shown in
In various embodiments, an interactive controller may be constructed from or configured using a personal computer 206 as shown in
In some embodiments, a device, such as the devices of
Some billiard combined proposition wagering systems in accordance with many embodiments of the invention can be distributed across a plurality of devices in various configurations.
In many embodiments, a distributed billiard combined proposition wagering system and may be operatively connected using a communication link to a session and/or management controller 307, that performs the processes of a session and/or management controller as described herein.
In several embodiments, a distributed billiard combined proposition wagering system and may be operatively connected using a communication link to credit processing system 306, that performs the processes of one or more credit processing systems as described herein.
A distributed billiard combined proposition wagering system in accordance with another embodiment of the invention is illustrated in
In many embodiments, a distributed billiard combined proposition wagering system and may be operatively connected using a communication link to a session and/or management controller 319, that performs the processes of a session and/or management controller as described herein.
In several embodiments, a distributed billiard combined proposition wagering system and may be operatively connected using a communication link to credit processing system 311, that performs the processes of one or more credit processing systems as described herein.
A distributed billiard combined proposition wagering systems in accordance with still another embodiment of the invention is illustrated in
In many embodiments, a distributed billiard combined proposition wagering system and may be operatively connected using a communication link to a session and/or management controller 353, that performs the processes of a session and/or management controller as described herein.
In several embodiments, a distributed billiard combined proposition wagering system and may be operatively connected using a communication link to credit processing system 355, that performs the processes of one or more credit processing systems as described herein.
In other embodiments, a number of other peripheral systems, such as a user management system, a gaming establishment management system, a regulatory system, and/or hosting servers are also operatively connected with the billiard combined proposition wagering systems using a communication link. Also, other servers can reside outside the bounds of a network within a firewall of the operator to provide additional services for network connected billiard combined proposition wagering systems.
Although various distributed billiard combined proposition wagering systems are described herein, billiard combined proposition wagering systems can be distributed in any configuration as appropriate to the specification of a specific application in accordance with embodiments of the invention. In some embodiments, components of a distributed billiard combined proposition wagering system, such as a process controller, chance-based controller, interactive controller, or other servers that perform services for a process controller, chance-based controller and/or interactive controller, can be distributed in different configurations for a specific distributed billiard combined proposition wagering system application.
Referring now to
In some embodiments, various components of the interactive application 402 can read data from an application state 414 in order to provide one or more features of the interactive application. In various embodiments, components of the interactive application 402 can include, but are not limited to: a physics engine; a rules engine; an audio engine; a graphics engine and the like. The physics engine is used to simulate physical interactions between virtual objects in the interactive application 402. The rules engine implements the rules of the interactive application and a random number generator that may be used for influencing or determining certain variables and/or outcomes to provide a randomizing influence on the operations of the interactive application. The graphics engine is used to generate a visual representation of the interactive application state to the user. The audio engine is used to generate an audio representation of the interactive application state to the user.
During operation, the interactive application reads and writes application resources 416 stored on a data store of the interactive controller host. The application resources 416 may include objects having graphics and/or control logic used to provide application environment objects of the interactive application. In various embodiments, the resources may also include, but are not limited to, video files that are used to generate a portion of the user presentation 406; audio files used to generate music, sound effects, etc. within the interactive application; configuration files used to configure the features of the interactive application; scripts or other types of control code used to provide various features of the interactive application; and graphics resources such as textures, objects, etc. that are used by a graphics engine to render objects displayed in an interactive application.
In operation, components of the interactive application 402 read portions of the application state 414 and generate the user presentation 406 for the user that is presented to the user using the user interface 404. The user perceives the user presentation and provides user interactions 408 using the user input devices. The corresponding user interactions are received as user actions or inputs by various components of the interactive application 402. The interactive application 402 translates the user actions into interactions with the virtual objects of the application environment stored in the application state 414. Components of the interactive application use the user interactions with the virtual objects of the interactive application and the interactive application state 414 to update the application state 414 and update the user presentation 406 presented to the user. The process loops continuously while the user interacts with the interactive application of the billiard combined proposition wagering system.
The interactive controller 400 provides one or more interfaces 418 between the interactive controller 400 and other components of a billiard combined proposition wagering system, such as, but not limited to, a process controller and a session/management controller. The interactive controller 400 and the other billiard combined proposition wagering system components communicate with each other using the interfaces. The interface may be used to pass various types of data, and to communicate and receive messages, status data, commands and the like. In certain embodiments, the interactive controller 400 and a process controller communicate application commands and environment resources 412 and application telemetry data 410. In some embodiments, the communications include requests by the process controller that the interactive controller 400 update the application state 414 using data provided by the process controller.
In many embodiments, a communications between a process controller and the interactive controller 400 includes a request that the interactive controller 400 update one or more resources 416 using data provided by the process controller. In a number of embodiments, the interactive controller 400 provides all or a portion of the application state to the process controller. In some embodiments, the interactive controller 400 may also provide data about one or more of the application resources 416 to the process controller. In some embodiments, the communication includes user interactions that the interactive controller 400 communicates to the process controller. The user interactions may be low level user interactions with the user interface 404, such as manipulation of a user input device, or may be high level interactions with game objects as determined by the interactive application. The user interactions may also include resultant actions such as modifications to the application state 414 or game resources 416 resulting from the user's interactions taken in the billiard combined proposition wagering system interactive application. In some embodiments, user interactions include, but are not limited to, actions taken by entities such as non-user characters (NPC) of the interactive application that act on behalf of or under the control of the user.
In various embodiments, the application commands and resources 412 include skill proposition application commands and/or resources used by the interactive application to generate a presentation of a skill proposition presented to a user and to determine a skill outcome based on the user's skillful interaction with the presentation of the skill proposition.
In some embodiments, the interactive controller 400 includes a wagering user interface 420 used to provide billiard combined proposition wagering system telemetry data 422 to and from the user. The billiard combined proposition wagering system telemetry data 422 from the billiard combined proposition wagering system include, but are not limited to, data used by the user to configure credit, application credit and interactive element wagers, and data about the chance-based proposition credits, application credits and interactive element wagers such as, but not limited to, credit, application credit and interactive element balances and credit, application credit and interactive element amounts wagered.
In some embodiments, the interactive controller 400 includes an administration interface 430 used to provide billiard combined proposition wagering system administration telemetry data 432 to and from the user.
In some embodiments, the interactive controller includes one or more sensors 424. Such sensors may include, but are not limited to, physiological sensors that monitor the physiology of the user, environmental sensors that monitor the physical environment of the interactive controller, accelerometers that monitor changes in motion of the interactive controller, and location sensors that monitor the location of the interactive controller such as global positioning sensors (GPSs). The interactive controller 400 communicates sensor telemetry data 426 to one or more components of the billiard combined proposition wagering system.
Referring now to
The one or more processors 504 may take many forms, such as, but not limited to: a central processing unit (CPU); a multi-processor unit (MPU); an ARM processor; a controller; a programmable logic device; or the like.
In the example embodiment, the one or more processors 504 and the random access memory (RAM) 506 form an interactive controller processing unit 599. In some embodiments, the interactive controller processing unit includes one or more processors operatively connected to one or more of a RAM, ROM, and machine-readable storage medium; the one or more processors of the interactive controller processing unit receive instructions stored by the one or more of a RAM, ROM, and machine-readable storage medium via a bus; and the one or more processors execute the received instructions. In some embodiments, the interactive controller processing unit is an ASIC (Application-Specific Integrated Circuit). In some embodiments, the interactive controller processing unit is a SoC (System-on-Chip).
Examples of output devices 512 include, but are not limited to, display screens; light panels; and/or lighted displays. In accordance with particular embodiments, the one or more processors 504 are operatively connected to audio output devices such as, but not limited to: speakers; and/or sound amplifiers. In accordance with many of these embodiments, the one or more processors 504 are operatively connected to tactile output devices like vibrators, and/or manipulators.
Examples of user input devices 514 include, but are not limited to: tactile devices including but not limited to, keyboards, keypads, foot pads, touch screens, and/or trackballs; non-contact devices such as audio input devices; motion sensors and motion capture devices that the interactive controller can use to receive inputs from a user when the user interacts with the interactive controller; physiological sensors that monitor the physiology of the user; environmental sensors that monitor the physical environment of the interactive controller; accelerometers that monitor changes in motion of the interactive controller; and location sensors that monitor the location of the interactive controller such as global positioning sensors.
The one or more communication interface devices 516 provide one or more wired or wireless interfaces for communicating data and commands between the interactive controller 400 and other devices that may be included in a billiard combined proposition wagering system. Such wired and wireless interfaces include, but are not limited to: a Universal Serial Bus (USB) interface; a Bluetooth interface; a Wi-Fi interface; an Ethernet interface; a Near Field Communication (NFC) interface; a plain old telephone system (POTS) interface, a cellular or satellite telephone network interface; and the like.
The machine-readable storage medium 510 stores machine-executable instructions for various components of the interactive controller, such as but not limited to: an operating system 518; one or more device drivers 522; one or more application programs 520 including but not limited to an interactive application; and billiard combined proposition wagering system interactive controller instructions and data 524 for use by the one or more processors 504 to provide the features of an interactive controller as described herein. In some embodiments, the machine-executable instructions further include application control interface/application control interface instructions and data 526 for use by the one or more processors 504 to provide the features of an application control interface/application control interface as described herein.
In various embodiments, the machine-readable storage medium 510 is one of a (or a combination of two or more of) a hard drive, a flash drive, a DVD, a CD, a flash storage, a solid state drive, a ROM, an EIEPROM, and the like.
In operation, the machine-executable instructions are loaded into memory 506 from the machine-readable storage medium 510, the ROM 508 or any other storage location. The respective machine-executable instructions are accessed by the one or more processors 504 via the bus 502, and then executed by the one or more processors 504. Data used by the one or more processors 504 are also stored in memory 506, and the one or more processors 504 access such data during execution of the machine-executable instructions. Execution of the machine-executable instructions causes the one or more processors 504 to control the interactive controller 400 to provide the features of a billiard combined proposition wagering system interactive controller as described herein
Although the interactive controller is described herein as being constructed from or configured using one or more processors and instructions stored and executed by hardware components, the interactive controller can be constructed from or configured using only hardware components in accordance with other embodiments. In addition, although the storage medium 510 is described as being operatively connected to the one or more processors through a bus, those skilled in the art of interactive controllers will understand that the storage medium can include removable media such as, but not limited to, a USB memory device, an optical CD ROM, magnetic media such as tape and disks. In some embodiments, the storage medium 510 can be accessed by the one or more processors 504 through one of the communication interface devices 516 or using a communication link. Furthermore, any of the user input devices or user output devices can be operatively connected to the one or more processors 504 vione of the communication interface devices 516 or using a communication link.
In some embodiments, the interactive controller 400 can be distributed across a plurality of different devices. In many such embodiments, an interactive controller of a billiard combined proposition wagering system includes an interactive application server operatively connected to an interactive client using a communication link. The interactive application server and interactive application client cooperate to provide the features of an interactive controller as described herein.
In various embodiments, the interactive controller 400 may be used to construct other components of a billiard combined proposition wagering system as described herein.
In some embodiments, components of an interactive controller and a process controller of a billiard combined proposition wagering system may be constructed from or configured using a single device using processes that communicate using an interprocess communication protocol. In other such embodiments, the components of an interactive controller and a process controller of a billiard combined proposition wagering system may communicate by passing messages, parameters or the like.
Referring now to
In some embodiments, an interface 628 allows the chance-based controller 604 to operatively connect to, and communicate with, an external device, such as one or more process controllers as described herein. The interface 628 provides for communication of chance proposition determination commands 629 from the external device that is used to specify chance-based proposition parameters and/or initiate resolution of a chance-based proposition by the chance-based controller 604 as described herein. The interface 628 may also provide for communicating chance outcome data 631 to an external device as described herein. In numerous embodiments, the interface 628 between the chance-based controller 604 and other systems/devices may be a wide area network (WAN) such as the Internet. However, other methods of communication may be used including, but not limited to, a local area network (LAN), a universal serial bus (USB) interface, and/or some other method by which two electronic devices could communicate with each other.
In various embodiments, an interface 630 allows the chance-based controller 604 to operatively connect to an external system or device, such as one or more credit processing systems, as described herein. The interface 630 provides for communication of incoming credit data 632 from the external system or device that is used to add credits to the one or more meters 626 as described herein. The interface 630 may also provide for communicating outgoing credit data 634 to an external system or device, such as a credit processing system, as described herein. In numerous embodiments, the interface 630 between the chance-based controller 604 and other systems/devices may be a wide area network (WAN) such as the Internet. However, other methods of communication may be used including, but not limited to, a local area network (LAN), a universal serial bus (USB) interface, and/or some other method by which two electronic devices or systems could communicate with each other.
In various embodiments, an interface 640 allows the chance-based controller 604 to operatively connect to an external system or device, such as one or more session/management controllers, as described herein. The interface 640 provides for communication of incoming session data 642 from the external system or device as described herein. The interface 640 may also provide for communicating outgoing session data 644 to an external system or device, such as a session/management controller, as described herein. In numerous embodiments, the interface 640 between the chance-based controller 604 and other systems/devices may be a wide area network (WAN) such as the Internet. However, other methods of communication may be used including, but not limited to, a local area network (LAN), a universal serial bus (USB) interface, and/or some other method by which two electronic devices or systems could communicate with each other.
In various embodiments, a chance-based controller 604 may use a random number generator provided by an external system. The external system may be connected to the chance-based controller 604 by a suitable communication network such as a local area network (LAN) or a wide area network (WAN). In some embodiments, the external random number generator is a central deterministic system that provides random results to one or more connected chance-based controllers.
During operation of the chance-based controller, the external system communicates chance proposition determination commands 629 to the chance-based controller 604. The chance-based controller 604 receives the chance proposition determination commands and uses the chance proposition determination commands to initiate resolution of a chance-based proposition in accordance with a chance-based proposition. The chance-based controller 604 executes the chance-based proposition and determines a chance outcome for the chance-based proposition. The chance-based controller communicates chance outcome data 631 of the chance outcome to the external system.
In some embodiments, the chance-based controller uses the chance proposition determination commands to select a paytable 628 to use and/or an amount of credits, application credits, interactive elements, or objects for a chance-based proposition.
In some embodiments, the chance outcome data may include, but is not limited to, an amount of credits, application credits, interactive elements, or objects.
In various embodiments, the chance outcome data may include, but is not limited to, an amount of credits, application credits, interactive elements, or objects in the one or more meters 626.
In some embodiments, the chance outcome data includes state data for the chance-based proposition of the resolved chance-based proposition. The state data may correspond to one or more game states of a chance-based proposition that is associated with the chance-based proposition. Examples of state data include, but are not limited to, reel strips in an operation state or a final state for a reel-based chance-based proposition, one or more dice positions for a dice-based chance-based proposition, positions of a roulette wheel and roulette ball, position of a wheel of fortune, or the like.
In various embodiments, the chance-based proposition control module 622 determines an amount of a chance-based proposition and a paytable to use from the one or more paytables 623. In such embodiments, in response to the chance proposition determination commands initiating resolution of the chance-based proposition, the chance-based proposition control module 622 resolves the chance-based proposition by requesting a random number generator result from the RNG 620; retrieving a paytable from the one or more paytables 623; adjusting the one or more credit meters 626 for an amount of the wager; applying the random number generator result to the retrieved paytable; multiplying the resultant factor from the paytable by an amount wagered to determine a chance outcome; updating the one or more meters 626 based on the chance outcome; and communicating the chance outcome to the external device.
In various embodiments, an external system communicates a request for a random number generator result from the chance-based controller 604. In response, the chance-based controller 604 returns a random number generator result as a function of an internal random number generator or a random number generator external to the external system to which the chance-based controller 604 is operatively connected.
In some embodiments, a communication exchange between the chance-based controller 604 and an external system relate to the external system support for coupling a random number generator result to a particular paytable contained in the chance-based controller 604. In such an exchange, the external system communicates to the chance-based controller 604 as to which of the one or more paytables 623 to use, and requests a result whereby the random number generator result would be associated with the requested paytable 623. The result of the coupling is returned to the external system. In such an exchange, no actual credit, application credit, interactive element, or object chance outcome is determined, but might be useful in coupling certain non-value wagering interactive application behaviors and propositions to the same final resultant chance outcome which is understood for the billiard combined proposition wagering system.
In some embodiments, the chance-based controller 604 may also include storage for statuses, wagers, chance outcomes, meters and other historical events in a storage device 616.
In some embodiments, an authorization access module provides a process to permit access and command exchange with the chance-based controller 604 and access to the one or more credit meters 626 for the amount of credits, application credits, interactive elements, or objects being wagered by the user in the billiard combined proposition wagering system.
In numerous embodiments, communication occurs between various types of a chance-based controller and an external system 630, such as process controller. In some of these embodiments, the purpose of the chance-based controller is to allocate wagers to pools, detect occurrences of one or more events upon which the wagers were made, and determine the chance outcomes for each individual random number generator based on the number of winning chance outcomes and the amount paid into the pool.
In some embodiments, the chance-based controller manages accounts for individual users wherein the users make deposits into the accounts, amounts are deducted from the accounts, and amounts are credited to the users' accounts based on the chance outcomes.
In some embodiments a chance-based controller is a pari-mutuel wagering system such as used for wagering on an events such as horse races, greyhound races, sporting events and the like. In a pari-mutuel wagering system, user's wagers on the outcome of an event are allocated to a pool. When the event occurs, chance outcomes are calculated by sharing the pool among all winning wagers.
In various embodiments, a chance-based controller is a central determination system, such as but not limited to a central determination system for a Class II wagering system or a wagering system in support of a “scratch off” style lottery. In such a wagering system, a user plays against other users and competes for a common prize. In a given set of chance outcomes, there are a certain number of wins and losses. Once a certain chance outcome has been determined, the same chance outcome cannot occur again until a new set of chance outcomes is generated.
In numerous embodiments, communication occurs between various components of a chance-based controller 604 and an external system, such as a process controller.
Referring now to
The one or more processors 734 may take many forms, such as, but not limited to, a central processing unit (CPU), a multi-processor unit (MPU), an ARM processor, a controller, a programmable logic device, or the like.
In the example embodiment, the one or more processors 734 and the random access memory (RAM) 736 form a chance-based controller processing unit 799. In some embodiments, the chance-based controller processing unit includes one or more processors operatively connected to one or more of a RAM, ROM, and machine-readable storage medium; the one or more processors of the chance-based controller processing unit receive instructions stored by the one or more of a RAM, ROM, and machine-readable storage medium via a bus; and the one or more processors execute the received instructions. In some embodiments, the chance-based controller processing unit is an ASIC (Application-Specific Integrated Circuit). In some embodiments, the chance-based controller processing unit is a SoC (System-on-Chip).
Examples of output devices 742 include, but are not limited to, display screens, light panels, and/or lighted displays. In accordance with particular embodiments, the one or more processors 734 are operatively connected to audio output devices such as, but not limited to speakers, and/or sound amplifiers. In accordance with many of these embodiments, the one or more processors 734 are operatively connected to tactile output devices like vibrators, and/or manipulators.
Examples of user input devices 734 include, but are not limited to, tactile devices including but not limited to, keyboards, keypads, touch screens, and/or trackballs; non-contact devices such as audio input devices; motion sensors and motion capture devices that the chance-based controller can use to receive inputs from a user when the user interacts with the chance-based controller 604.
The one or more communication interface and/or network interface devices 746 provide one or more wired or wireless interfaces for exchanging data and commands between the chance-based controller 604 and other devices that may be included in a billiard combined proposition wagering system. Such wired and wireless interfaces include, but are not limited to: a Universal Serial Bus (USB) interface; a Bluetooth interface; a Wi-Fi interface; an Ethernet interface; a Near Field Communication (NFC) interface; a plain old telephone system (POTS) interface; a cellular or satellite telephone network interface; and the like.
The machine-readable storage medium 740 stores machine-executable instructions for various components of a chance-based controller, such as but not limited to: an operating system 748; one or more application programs 750; one or more device drivers 752; and billiard combined proposition wagering system chance-based controller instructions and data 754 for use by the one or more processors 734 to provide the features of a billiard combined proposition wagering system chance-based controller as described herein.
In various embodiments, the machine-readable storage medium 740 is one of a (or a combination of two or more of) a hard drive, a flash drive, a DVD, a CD, a flash storage, a solid state drive, a ROM, an EIEPROM, and the like.
In operation, the machine-executable instructions are loaded into memory 736 from the machine-readable storage medium 740, the ROM 738 or any other storage location. The respective machine-executable instructions are accessed by the one or more processors 734 via the bus 732, and then executed by the one or more processors 734. Data used by the one or more processors 734 are also stored in memory 736, and the one or more processors 734 access such data during execution of the machine-executable instructions. Execution of the machine-executable instructions causes the one or more processors 734 to control the chance-based controller 604 to provide the features of a billiard combined proposition wagering system chance-based controller as described herein
Although the chance-based controller 604 is described herein as being constructed from or configured using one or more processors and machine-executable instructions stored and executed by hardware components, the chance-based controller can be composed of only hardware components in accordance with other embodiments. In addition, although the storage medium 740 is described as being operatively connected to the one or more processors through a bus, those skilled in the art of processing devices will understand that the storage medium can include removable media such as, but not limited to, a USB memory device, an optical CD ROM, magnetic media such as tape and disks. In some embodiments, the storage medium 740 can be accessed by the one or more processors 734 through one of the interfaces or using a communication link. Furthermore, any of the user input devices or user output devices can be operatively connected to the one or more processors 734 vione of the interfaces or using a communication link.
In various embodiments, the chance-based controller 604 may be used to construct other components of a billiard combined proposition wagering system as described herein.
In some embodiments, components of a chance-based controller and a process controller of a billiard combined proposition wagering system may be constructed from or configured using a single device using processes that communicate using an interprocess communication protocol. In other such embodiments, the components of a chance-based controller and a process controller of a billiard combined proposition wagering system may communicate by passing messages, parameters or the like.
It should be understood that there may be many embodiments of a chance-based controller 604 which could be possible, including forms where many modules and components of the chance-based controller are located in various servers and locations, so the foregoing is not meant to be exhaustive or all inclusive, but rather provide data on various embodiments of a chance-based controller 604.
Referring now to
In some embodiments, the process controller 860 includes an interactive controller interface 800 to an interactive controller. The interactive controller interface 800 provides for communication of data between an interactive controller and the process controller 860, including but not limited to wagering telemetry data 802, application instructions and resources 804, application telemetry data 806, and sensor telemetry data 810 as described herein.
In various embodiments, the process controller 860 includes a chance-based controller interface 812 to a chance-based controller. The chance-based controller interface 812 provides for communication of data between the process controller 860 and a chance-based controller, including but not limited to chance outcomes 814 and chance proposition determination commands 816 as described in.
In some embodiments, the process controller 860 includes a session/management controller interface 818 to a session/management controller. The session/management controller interface 818 provides for communication of data between the process controller 860 and a session/management controller, including but not limited to session control data 820 and session telemetry data 822 as described herein.
The process controller 860 includes a rule-based decision engine 824 that receives telemetry data, such as application telemetry data and sensor telemetry data, from an interactive controller. The rule-based decision engine 824 uses the telemetry data, along with chance proposition logic 826 to generate chance proposition data 816 used to command a chance-based controller to initiate resolution of a chance-based outcome. The chance proposition data may include, but are not limited to, an amount and type of the chance-based outcome, a request for resolution of the chance-based outcome, and a selection of a paytable to be used when resolving the chance-based proposition.
In some embodiments, the application telemetry data includes, but is not limited to, application environment variables that indicate the state of an interactive application being used by a user, interactive controller data indicating a state of an interactive controller, and user actions and interactions between a user and an interactive application provided by an interactive controller.
In some embodiments, the rule-based decision engine 824 also receives chance outcome data 814 from a chance-based controller. The decision engine 824 uses the chance outcome data, in conjunction with telemetry data and skill proposition logic 828 to generate application instructions and resources 804 for a skill proposition that is to be presented to a user by an interactive application of an interactive controller. The application instructions and resources 804 are communicated to the interactive application of the interactive controller.
In some embodiments, the application telemetry data 806 may further include a skill outcome determined by the interactive application in response to a user's skillful interactions with the skill proposition that was presented to the user.
In various embodiments, the rule-based decision engine 824 also determines an amount of application credit to award to a user based at least in part on the user's use of an interactive application of the billiard combined proposition wagering system as determined from application telemetry data. In some embodiments, chance outcome data may also be used to determine the amount of application credit that should be awarded to the user.
In numerous embodiments, an interactive application is a skill-based interactive application and the application credit is awarded to the user for the user's skillful play of the skill-based interactive application.
In some embodiments, the business rule decision engine 824 uses combined proposition logic 830 to generate a combined outcome using the skill outcome data included in the application telemetry 806 and the chance outcome data 814. Data of the combined outcome 832 are communicated to a wagering user interface generator 834. The wagering user interface generator 834 receives the combined outcome data 832 and generates wagering telemetry data 802 describing the state of wagering and credit accumulation and loss for the billiard combined proposition wagering system. In some embodiments, the wagering telemetry data 146 may include, but is not limited to, amounts of application credits and interactive elements earned, lost or accumulated by the user through use of the interactive application as determined from the application decisions, and credit amounts won, lost or accumulated as determined from the combined outcome data 832 and one or more credit meters.
The process controller 860 can further operatively connect to a chance-based controller to determine an amount of credit or interactive elements available and other wagering metrics of a chance-based proposition. Thus, the process controller 860 may potentially affect an amount of credits in play for participation in the wagering events of a chance-based proposition provided by the chance-based controller. The process controller 860 may additionally include various audit logs and activity meters. In some embodiments, the process controller 860 can also couple to a centralized server for exchanging various data related to the user and the activities of the user during game play of a billiard combined proposition wagering system.
In some embodiments, the operation of the process controller 860 does not affect the provision of a chance-based proposition by a chance-based controller except for user choice parameters that are allowable in accordance with the chance-based proposition.
In a number of embodiments, communication of chance proposition determination commands between a chance-based controller and the process controller 860 can further be used to communicate various wagering control factors that the chance-based controller uses as input. Examples of wagering control factors include, but are not limited to, an amount of credits, application credits, interactive elements, or objects consumed per wagering event, and/or the user's election to enter a jackpot round.
In some embodiments, the process controller 860 utilizes a wagering user interface to communicate certain interactive application data to the user, including but not limited to, club points, user status, control of the selection of user choices, and messages which a user can find useful in order to adjust the interactive application experience or understand the wagering status of the user in accordance with the chance-based proposition in the chance-based controller.
In some embodiments, the process controller 860 utilizes a wagering user interface to communicate aspects of a chance-based proposition to the user including, but not limited to, odds of certain chance outcomes, amount of credits, application credits, interactive elements, or objects in play, and amounts of credits, application credits, interactive elements, or objects available.
In a number of embodiments, a chance-based controller can accept chance-based proposition factors including, but not limited to, modifications in the amount of credits, application credits, interactive elements, or objects wagered on each individual wagering event, a number of wagering events per minute the chance-based controller can resolve, entrance into a bonus round, and other factors. In several embodiments, the process controller 860 can communicate a number of factors back and forth to the chance-based controller, such that an increase/decrease in a wagered amount can be related to the change in user profile of the user in the interactive application. In this manner, a user can control a chance-based proposition credit amount per wagering event in accordance with the chance-based proposition with the change mapping to a parameter or component that is applicable to the interactive application experience.
Referring now to
The one or more processors 863 may take many forms, such as, but not limited to: a central processing unit (CPU); a multi-processor unit (MPU); an ARM processor; a programmable logic device; or the like.
Examples of output devices 867 include, include, but are not limited to: display screens; light panels; and/or lighted displays. In accordance with particular embodiments, the one or more processors 863 are operatively connected to audio output devices such as, but not limited to: speakers; and/or sound amplifiers. In accordance with many of these embodiments, the one or more processors 863 are operatively connected to tactile output devices like vibrators, and/or manipulators.
In the example embodiment, the one or more processors 863 and the random access memory (RAM) 864 form a process controller processing unit 870. In some embodiments, the process controller processing unit includes one or more processors operatively connected to one or more of a RAM, ROM, and machine-readable storage medium; the one or more processors of the process controller processing unit receive instructions stored by the one or more of a RAM, ROM, and machine-readable storage medium via a bus; and the one or more processors execute the received instructions. In some embodiments, the process controller processing unit is an ASIC (Application-Specific Integrated Circuit). In some embodiments, the process controller processing unit is a SoC (System-on-Chip).
Examples of user input devices 868 include, but are not limited to: tactile devices including but not limited to, keyboards, keypads, foot pads, touch screens, and/or trackballs; non-contact devices such as audio input devices; motion sensors and motion capture devices that the process controller can use to receive inputs from a user when the user interacts with the process controller 860.
The one or more communication interface and/or network interface devices 869 provide one or more wired or wireless interfaces for exchanging data and commands between the process controller 860 and other devices that may be included in a billiard combined proposition wagering system. Such wired and wireless interfaces include, but are not limited to: a Universal Serial Bus (USB) interface; a Bluetooth interface; a Wi-Fi interface; an Ethernet interface; a Near Field Communication (NFC) interface; a plain old telephone system (POTS), cellular, or satellite telephone network interface; and the like.
The machine-readable storage medium 866 stores machine-executable instructions for various components of the process controller 860 such as, but not limited to: an operating system 871; one or more applications 872; one or more device drivers 873; and billiard combined proposition wagering system process controller instructions and data 874 for use by the one or more processors 863 to provide the features of a process controller as described herein.
In various embodiments, the machine-readable storage medium 870 is one of a (or a combination of two or more of) a hard drive, a flash drive, a DVD, a CD, a flash storage, a solid state drive, a ROM, an EIEPROM, and the like.
In operation, the machine-executable instructions are loaded into memory 864 from the machine-readable storage medium 866, the ROM 865 or any other storage location. The respective machine-executable instructions are accessed by the one or more processors 863 via the bus 861, and then executed by the one or more processors 863. Data used by the one or more processors 863 are also stored in memory 864, and the one or more processors 863 access such data during execution of the machine-executable instructions. Execution of the machine-executable instructions causes the one or more processors 863 to control the process controller 860 to provide the features of a billiard combined proposition wagering system process controller as described herein.
Although the process controller 860 is described herein as being constructed from or configured using one or more processors and instructions stored and executed by hardware components, the process controller can be composed of only hardware components in accordance with other embodiments. In addition, although the storage medium 866 is described as being operatively connected to the one or more processors through a bus, those skilled in the art of process controllers will understand that the storage medium can include removable media such as, but not limited to, a USB memory device, an optical CD ROM, magnetic media such as tape and disks. Also, in some embodiments, the storage medium 866 may be accessed by processor 863 through one of the interfaces or using a communication link. Furthermore, any of the user input devices or user output devices may be operatively connected to the one or more processors 863 vione of the interfaces or using a communication link.
In various embodiments, the process controller 860 may be used to construct other components of a billiard combined proposition wagering system as described herein.
In some embodiments, components of an interactive controller and a process controller of a billiard combined proposition wagering system may be constructed from or configured using a single device using processes that communicate using an interprocess communication protocol. In other such embodiments, the components of an interactive controller and a process controller of a billiard combined proposition wagering system may communicate by passing messages, parameters or the like.
Referring now to
The session/management controller 1104 may further include a datastore 1108 storing user data used to manage user registration and validation. The session/management controller 1104 may further include a datastore 1110 storing session data used to manage one or more sessions.
The various session/management controller components can interface with each other via an internal bus 1112 and/or other appropriate communication mechanism.
An interface 1114 allows the session/management controller 1104 to operatively connect to one or more external devices, such as one or more process controllers, chance-based controllers and/or interactive controllers as described herein. The interface provides for receiving session telemetry data 1116 from the one more external devices as described herein. The session telemetry data includes, but is not limited to, amounts of application credit earned by one or more users, requests for entering into a session as described herein, and telemetry data regarding the progress of one or more users during a session. The interface 1114 may also provide for communicating secession control data 1118 used to manage a session as described herein.
In numerous embodiments, the interface between the session/management controller and other systems/devices may be a wide area network (WAN) such as the Internet. However, other methods of communication may be used including, but not limited to, a local area network (LAN), a universal serial bus (USB) interface, and/or some other method by which two electronic devices could communicate with each other.
During operation of the session/management controller, the external system communicates session telemetry data to the session/management controller. The session/management controller receives the session telemetry data and uses the session telemetry data to generate session control data as described herein. The session/management controller communicates the session control data to the external system.
Referring now to
The one or more processors 1134 may take many forms, such as, but not limited to, a central processing unit (CPU), a multi-processor unit (MPU), an ARM processor, a controller, a programmable logic device, or the like.
In the example embodiment, the one or more processors 1134 and the random access memory (RAM) 1136 form a session/management controller processing unit 1199. In some embodiments, the session/management controller processing unit includes one or more processors operatively connected to one or more of a RAM, ROM, and machine-readable storage medium; the one or more processors of the session/management controller processing unit receive instructions stored by the one or more of a RAM, ROM, and machine-readable storage medium via a bus; and the one or more processors execute the received instructions. In some embodiments, the session/management controller processing unit is an ASIC (Application-Specific Integrated Circuit). In some embodiments, the session/management controller processing unit is a SoC (System-on-Chip).
Examples of output devices 1142 include, but are not limited to, display screens, light panels, and/or lighted displays. In accordance with particular embodiments, the one or more processors 1134 are operatively connected to audio output devices such as, but not limited to speakers, and/or sound amplifiers. In accordance with many of these embodiments, the one or more processors 1134 are operatively connected to tactile output devices like vibrators, and/or manipulators.
Examples of user input devices 1144 include, but are not limited to, tactile devices including but not limited to, keyboards, keypads, touch screens, and/or trackballs; non-contact devices such as audio input devices; motion sensors and motion capture devices that the session/management controller can use to receive inputs from a user when the user interacts with the session/management controller 1104.
The one or more communication interface and/or network interface devices 1146 provide one or more wired or wireless interfaces for exchanging data and commands between the session/management controller 1104 and other devices that may be included in a billiard combined proposition wagering system. Such wired and wireless interfaces include, but are not limited to: a Universal Serial Bus (USB) interface; a Bluetooth interface; a Wi-Fi interface; an Ethernet interface; a Near Field Communication (NFC) interface; a plain old telephone system (POTS) interface; a cellular or satellite telephone network interface; and the like.
The machine-readable storage medium 1140 stores machine-executable instructions for various components of a session/management controller, such as but not limited to: an operating system 1148; one or more application programs 1150; one or more device drivers 1152; and billiard combined proposition wagering system session/management controller instructions and data 1154 for use by the one or more processors 1134 to provide the features of a billiard combined proposition wagering system session/management controller as described herein.
In various embodiments, the machine-readable storage medium 1140 is one of a (or a combination of two or more of) a hard drive, a flash drive, a DVD, a CD, a flash storage, a solid state drive, a ROM, an EIEPROM, and the like.
In operation, the machine-executable instructions are loaded into memory 736 from the machine-readable storage medium 1140, the ROM 1138 or any other storage location. The respective machine-executable instructions are accessed by the one or more processors 1134 via the bus 1132, and then executed by the one or more processors 1134. Data used by the one or more processors 1134 are also stored in memory 1136, and the one or more processors 1134 access such data during execution of the machine-executable instructions. Execution of the machine-executable instructions causes the one or more processors 1134 to control the session/management controller 1104 to provide the features of a billiard combined proposition wagering system session/management controller as described herein
Although the session/management controller 1104 is described herein as being constructed from or configured using one or more processors and machine-executable instructions stored and executed by hardware components, the session/management controller can be composed of only hardware components in accordance with other embodiments. In addition, although the storage medium 1140 is described as being operatively connected to the one or more processors through a bus, those skilled in the art of processing devices will understand that the storage medium can include removable media such as, but not limited to, a USB memory device, an optical CD ROM, magnetic media such as tape and disks. In some embodiments, the storage medium 1140 can be accessed by the one or more processors 1134 through one of the interfaces or using a communication link. Furthermore, any of the user input devices or user output devices can be operatively connected to the one or more processors 1134 vione of the interfaces or using a communication link.
In various embodiments, the session/management controller 1104 may be used to construct other components of a billiard combined proposition wagering system as described herein.
In some embodiments, components of a session/management controller and a process controller of a billiard combined proposition wagering system may be constructed from or configured using a single device using processes that communicate using an interprocess communication protocol. In other such embodiments, the components of a session/management controller and a process controller of a billiard combined proposition wagering system may communicate by passing messages, parameters or the like.
In some embodiments, components of a session/management controller and a chance-based controller of a billiard combined proposition wagering system may be constructed from or configured using a single device using processes that communicate using an interprocess communication protocol. In other such embodiments, the components of a session/management controller and a process controller of a billiard combined proposition wagering system may communicate by passing messages, parameters or the like.
It should be understood that there may be many embodiments of a session/management controller 1104 which could be possible, including forms where many modules and components of the session/management controller are located in various servers and locations, so the foregoing is not meant to be exhaustive or all inclusive, but rather provide data on various embodiments of a session/management controller 1104.
In numerous embodiments, any of a chance-based controller, a process controller, an interactive controller, or a session/management controller as described herein can be constructed from or configured using multiple processing devices, whether dedicated, shared, or distributed in any combination thereof, or can be constructed from or configured using a single processing device. In addition, while certain aspects and features of billiard combined proposition wagering system processes described herein have been attributed to a chance-based controller, a process controller, an interactive controller, or a session/management controller, these aspects and features can be provided in a distributed form where any of the features or aspects can be provided by any of a session/management controller, a chance-based controller, a process controller, and/or an interactive controller within a billiard combined proposition wagering system without deviating from the spirit of the invention.
Although various components of billiard combined proposition wagering systems are discussed herein, billiard combined proposition wagering systems can be configured with any component as appropriate to the specification of a specific application in accordance with embodiments of the invention. In certain embodiments, components of a billiard combined proposition wagering system, such as a session/management controller, a process controller, a chance-based controller, and/or an interactive controller, can be configured in different ways for a specific billiard combined proposition wagering system.
In some embodiments, components of a session/management controller, an interactive controller, a process controller, and/or a chance-based controller of a billiard combined proposition wagering system may be constructed from or configured using a single device using processes that communicate using an interprocess communication protocol. In many embodiments, the components of a session/management controller, an interactive controller, a process controller and a chance-based controller of a billiard combined proposition wagering system may communicate by passing messages, parameters or the like.
In addition, while certain aspects and features of billiard combined proposition wagering system processes described herein have been attributed to a session/management controller, a chance-based controller, a process controller, or an interactive controller, these aspects and features can be provided in a distributed form where any of the features or aspects can be provided by any of a session/management controller, a chance-based controller, a process controller, and/or an interactive controller within a billiard combined proposition wagering system.
Operation of Billiard Combined Proposition Wagering Systems
In some embodiments, at a beginning of the wagering session, the process includes a credit input 909 to the billiard combined proposition wagering system with chance-based controller 902 communicating with the credit processing system 903 to receive incoming credit data 905. The chance-based controller 902 uses the incoming credit data to transfer credits onto one or more credit meters associated with one or more users of the billiard combined proposition wagering system, thus transferring credits into the billiard combined proposition wagering system and on to the one or more credit meters.
In many embodiments, the interactive controller 906 detects 907 a user performing a user interaction in an application interface of an interactive application provided by the interactive controller 906. The interactive controller 906 communicates application telemetry data 908 to the process controller 904. The application telemetry data 908 includes, but is not limited to, the user interaction detected by the interactive controller 906.
The process controller 904 receives the application telemetry data 908. Upon determination by the process controller 904 that the user interaction indicates a wagering event in the interactive application, the process controller 904 generates chance outcome request data 912 that the process controller 904 uses to command the chance-based controller 902 to resolve a chance-based proposition. The chance outcome request data 912 may include chance-based proposition terms associated with a chance-based proposition. The process controller 904 communicates the chance outcome request data 912 to the chance-based controller 902.
The chance-based controller 902 receives the chance outcome request data 912 and uses the chance outcome request data to determine 913 a chance outcome for a chance-based proposition. The chance-based controller 902 updates 919 the one or more credit meters associated with the one or more users based on an amount of credits used for the chance-based proposition and stores amounts of credits awarded from the resolved chance-based proposition in one or more intermediate data stores. The chance-based controller 902 communicates data of the chance outcome 914 of the resolved chance-based outcome to the process controller 904.
The process controller 904 receives the chance outcome data 914 and determines 915 a skill proposition based in part on the chance outcome data 914. The skill proposition includes interactive application instruction and resource data that the process controller 904 uses to command the interactive controller 906 to present a skill proposition to a user. The process controller 904 communicates data of the skill proposition 916 to the interactive controller 906.
The interactive controller 906 receives the skill proposition data 916. The interactive application executing on the interactive controller 906 uses the skill proposition data to generate and present 918 a skill proposition to the user. The interactive controller 906 detects 920 skillful user interactions with the skill proposition presentation of the interactive application and determines 922 a skill outcome based on the user's skillful interactions. The interactive controller 906 communicates data of the skill outcome 924 to the process controller 904. The process controller 904 receives the skill outcome data 924 and determines 926 a combined outcome based on the skill outcome data 924 and the chance outcome data 914.
The process controller 904 communicates data of the combined outcome 928 to the chance-based controller 902. The chance-based controller 902 receives the combined outcome data 928 and updates 930 the one or more credit meters based in part on the combined outcome data 928. In some embodiments, if the combined outcome indicates that a user has been awarded credits, the chance-based controller 902 decrements credits stored on the intermediate credit meter and adds credits to the credit meter associated with the user. The chance-based controller communicates data of the updated credit meters 932 to the process controller 904. The process controller 904 receives the updated credit meter data 932 and generates 934 wagering telemetry data 936 using the combined outcome data 928 and the updated credit meter data 932. The process controller 904 communicates the wagering telemetry data 936 to the interactive controller 906. The interactive controller 906 receives the wagering telemetry data 936. The interactive controller 906 updates 936 a wagering user interface on a partial basis of the wagering telemetry data 936.
In many embodiments, upon determining that the wagering session is completed, such as by receiving a cashout communication from one or more users of the billiard combined proposition wagering system, the chance-based controller 902 transfers credits off of the one or more credit meters, generates outgoing credit data 940 on the basis of the credits transferred off of the one or more credit meters, and communicates the outgoing credit data 940 to the credit processing system 903. The credit processing system receives the outgoing credit data 940 and generates 942 a credit output as described herein, thus transferring credits off of the one or more credit meters and out of the billiard combined proposition wagering system.
In some embodiments, at a beginning of the wagering session, the process includes an application credit input to the billiard combined proposition wagering system with the process controller 904 communicating with the credit processing system 903 to receive incoming application credit data. The process controller 902 uses the incoming application credit data to transfer application credits onto one or more application credit meters associated with one or more users of the billiard combined proposition wagering system, thus transferring application credits into the billiard combined proposition wagering system and on to the one or more application credit meters. The process controller 904 uses the skill outcome data 924 to determine an amount of application credit to award to a user based on the user's skillful interactions with an interactive application executed by the interactive controller 905. Upon determining that the wagering session is completed, such as by receiving a cashout communication from one or more users of the billiard combined proposition wagering system, the process controller 904 transfers application credits off of the one or more application credit meters, generates outgoing application credit data on the basis of the application credits transferred off of the one or more application credit meters, and communicates the outgoing application credit data to the credit processing system 903. The credit processing system receives the outgoing application credit data and generates an application credit output as described herein, thus transferring application credits off of the one or more application credit meters and out of the billiard combined proposition wagering system.
As shown in
After the balls are scattered with a break shot, the users are assigned either the group of solid balls or the stripes once a ball from a particular group is legally pocketed. The ultimate object of the game is to legally pocket the eight ball in a called pocket, which can only be done after all of the balls from a user's assigned group have been cleared from the table.
As shown in
One person is chosen to shoot first, using a cue stick to break the object-ball rack apart. In some embodiments, the process controller makes the determination of which user shoots first. In some embodiments, the interactive controller makes the determination.
A user will continue to shoot until committing a scratch, or failing to legally pocket an object ball. Thereupon it is the turn of the opposing user(s). Play alternates in this manner for the remainder of the application. Following a scratch, the incoming user has ball-in-hand anywhere on the table.
In some embodiments, a legal pocket occurs when a specific ball is sunk into a called pocket. In an example embodiment, a user may be assigned solids after the break. In order for a legal pocket to occur, they must select a specific ball, such as solid red, and a target pocket, such as the lower middle pocket, before using the cue stick. If the solid red ball is then sunk into the lower middle pocket, the user has succeeded in a legal pocket.
If the red ball is sunk into a pocket that is not called by the user, then the user has scratched, and it is the opponent's turn. If multiple balls are sunk during a turn, so long as the called ball is sunk in the called pocket, then the user has had a successful interaction. However, only balls into the called pocket count for distribution of the wagers. If only an opponent's object ball is sunk, then it is removed from the table, but the user also scratches and the turn passes to the opponent.
Once all of a user's group of object balls are pocketed, the user may attempt to sink the 8 ball. To win, the user must first designate which pocket they plan to sink the 8 ball into and then successfully pot the 8 ball in that called pocket. If the 8 ball falls into any pocket other than the one designated or is knocked off the table, or a scratch occurs and the 8 ball is pocketed, this results in loss of game.
In order for the process controller to start, the users must allocate sufficient funds to the chance-based controller. The sum of the entire wager from both users is divided by 14 rounded down to the closest whole number. That wager amount is assigned to each object ball in the interactive application. The remainder of the wager is assigned to the 8 ball.
If a user achieves a legal pocketing of a ball, then the user wins the wager assigned to that ball; if multiple balls are sunk in a single turn, then only balls that are sunk into the called pocket result in the distribution of the wager. If a ball is sunk illegally, then the wager associated with the ball is redistributed to the balls still on the table. If a user sinks a ball assigned to their opponent, then the ball has been sunk illegally, and the wager associated with the ball is redistributed to the balls still on the table.
In some embodiments, wagers associated with balls that are illegally sunk are redistributed to the 8 ball rather than to all the balls still in play.
Specifically, in some embodiments, each interaction with an interactive component by the user may trigger a wager event—either a win or a loss depending on how the balls move through the system. Whether a user has successfully interacted with the interactive component is determined by the process controller and then communicated to the chance-based controller which then determines what wager is associated with the interactive component and communicates the result to the process controller. Additionally, the process controller determines whether interactive application resources are to be provided to the user on the basis of the successful interactions. In some embodiments, these may include cosmetic or vanity items, such as visual effects (balls that leave trails of fire) or specialty cues. Alternatively, there may be special bonuses such as vector extensions, which makes targeting easier.
In some embodiments, such as a mobile environment where the operator has less control over the system, an RNG element may be introduced to combat cheating. In some embodiments, this would limit the extent to which outside cheats could be employed by a user.
In some embodiments, while objects are in motion, the interactive controller is inaccessible to users. The user may not interact with any portion of the system that is in motion, and may only observe the effects of the previous action(s).
The components of the billiards combined proposition wagering system include a chance-based controller 1306, such as chance-based controller 102 of
In various embodiments, communication of outgoing data between a controller and another controller is achieved by the controller encoding data to be communicated into a signal and transmitting the signal to the another controller. Communication of incoming data is achieved by the controller receiving from the another controller signals encoding the incoming data. The controller decodes the signals to obtain the incoming data.
In some such embodiments, two or more controllers implement a controller-to-controller communication protocol as an interdevice communication protocol so that the two or more controllers may be implemented on different processing devices. The interdevice communication protocol may utilize a wired communication bus or wireless connection as a physical layer. In yet other such embodiments, the controller-to-controller communication protocol is implemented as a networking protocol so that the two or more controllers may be implemented on different devices operatively connected by a network. The networking protocol may utilize a wired communication bus or wireless connection as a physical layer. In many such embodiments, the network includes a cellular telephone network or the like and one or more of the controllers is a mobile device such as a smartphone or other device capable of using the cellular telephone network.
In some embodiments, communication is achieved by two or more of the controllers implementing a controller-to-controller communication protocol as an interprocess communication protocol so that the two or more controllers may be implemented on the same device.
In some embodiments, the interactive controller 1302, the process controller 1304, and the chance-based controller 1306 are separated into different components in order to distribute computing responsibilities to provide improved latency results. In some embodiments, the interactive controller 1302 dedicates its resources toward providing the interactive application, and may be unable to perform the additional processing performed by the process controller 1304 without sacrificing latency.
During operation, in various embodiments, the interactive controller 1302 is constructed to provide an interactive application display associated with an interactive application provided by the interactive controller 1302.
In some embodiments, at a beginning of the wagering session, the process includes a credit input to the billiards combined proposition wagering system (1310). In some embodiments the credit input is an input of a ticket or cash to a credit input device, as described herein. The credit processing system 1308 communicates, to the chance-based controller 1306, credit data (1312). The chance-based controller 1306 communicates with the credit processing system 1308 to receive incoming credit data (1312). The chance-based controller 1306 uses the incoming credit data to transfer credits onto one or more credit meters associated with one or more users of the billiards combined proposition wagering system, thus transferring credits into the billiards combined proposition wagering system and on to the one or more credit meters.
In many embodiments, the interactive controller 1302 detects a user performing an initialization indication in an application interface of an interactive application provided by the interactive controller 1302. In some embodiments, the initialization indication is providing an input to a user interface. In some embodiments, the initialization indication is interacting with a button coupled with the interactive controller 1302. The interactive controller 1302 communicates initialization data to the process controller 1304 (1314). The initialization data includes, but is not limited to, the user interaction detected by the interactive controller 1302 and a user identification associated with the user.
The process controller 1304 receives, from the interactive controller 1302, the initialization data (1314). Upon determination by the process controller 1304 that the user interaction indicates initiating a session, the process controller 1304 generates chance outcome request data that the process controller 1304 uses to command the chance-based controller 1306 to resolve a chance-based proposition. The chance outcome request data may include chance-based proposition terms associated with a chance-based proposition. The process controller 1304 communicates the chance outcome request data to the chance-based controller 1306 (1316).
The chance-based controller 1306 receives the chance outcome request data (1316) and uses the chance outcome request data to determine a chance outcome for a chance-based proposition (1318). The chance-based controller 1306 communicates data of the chance outcome of the resolved chance-based outcome to the process controller 1304 (1320). In some embodiments, the resolved chance-based outcome is a single chance outcome divided by 14 and rounded down to the closest whole number, with each whole number associated with a billiard ball 1-7 and 9-15 and the remainder of the chance-based outcome associated with billiard ball 8, as described herein. In some embodiments, the wager amount is divided into 15 equal values, and 15 individual chance-based outcomes are determined and assigned to a billiard ball 1-15.
The process controller 1304 receives the chance outcome data (1320) and assigns each outcome to a corresponding object (1322). In some embodiments, the chance outcome data identifies the corresponding billiard ball associated with the value. In some embodiments, the chance outcome data is a series of values representing chance-based outcomes and the process controller 1304 is responsible for assigning the chance-based outcome to a billiard ball.
The interactive controller 1302 presents a skill proposition to a user. In some embodiments, the skill proposition is playing a game of eight-ball or pocket billiards against an opponent. In some embodiments, the process controller 1304 communicates data of the skill proposition to the interactive controller 1302.
The interactive controller 1302 detects skillful user interactions with the skill proposition presentation of the interactive application and determines a skill outcome based on the user's skillful interactions. The interactive controller 1302 communicates data of the skill outcome to the process controller 1304 (1326). In some embodiments, the skill outcome data reflects a user putting a billiard ball in a pocket. In an example embodiment, the skill outcome data indicates that the user has put the 2 ball in a corner pocket. The process controller 1304 receives the skill outcome data (1326).
In some embodiments, the skill outcome data follows a skill outcome data protocol. In some embodiments, the skill outcome data protocol comprises an account identification. In some embodiments, the skill outcome protocol includes an identification of the interactive application. In some embodiments, the skill outcome data protocol includes an action or event occurring in the interactive application. In some embodiments, the skill outcome data protocol includes skill outcome data encoded as a string. In some embodiments, the skill outcome data protocol includes skill outcome data encoded as an array of the elements making up the skill outcome data. In some embodiments, the skill outcome protocol includes skill outcome data formatted as a concatenation of data of elements making up the skill outcome data.
The process controller 1304 updates object values based on the skill outcome data (1328). In some embodiments, when a skill outcome of a scratch is achieved, the value associated with the scratched ball is reassigned to another billiard ball. In some embodiments, the value is reassigned to the 8 ball. In some embodiments, the value is assigned to the opponent of the user who committed the scratch. In some embodiments, when a ball is improperly pocketed, the value associated with the ball is distributed to the remaining balls.
The process controller 1304 determines a billiard combined outcome (1330). In some embodiments, the combined outcome is a combined outcome of the skill outcome and the chance-based outcome. In an example embodiment, the combined outcome includes an identification of a billiard ball successfully placed in a pocket and the chance-based outcome value associated with the billiard ball.
The process controller 1304 communicates data of the combined outcome to the chance-based controller 1306 (1332). The chance-based controller 1306 receives the combined outcome data (1332) and updates the one or more credit meters based in part on the combined outcome data (1334). In some embodiments, if the combined outcome indicates that a user has been awarded credits, the chance-based controller 1306 decrements credits stored on the intermediate credit meter and adds credits to the credit meter associated with the user.
The chance-based controller communicates data of the updated credit meters to the process controller 1304 (1336). The process controller 1304 receives the updated credit meter data (1336) and generates wagering telemetry data using the combined outcome data and the updated credit meter data (1338). The process controller 1304 communicates the wagering telemetry data to the interactive controller 1302 (1340). The interactive controller 1302 receives the wagering telemetry data (1340). The interactive controller 1302 updates a wagering user interface on a partial basis of the wagering telemetry data (1342).
In many embodiments, upon determining that the wagering session is completed, such as by receiving a cashout communication from one or more users of the billiards combined proposition wagering system, the chance-based controller 1306 transfers credits off of the one or more credit meters, generates outgoing credit data on the basis of the credits transferred off of the one or more credit meters, and communicates the outgoing credit data to the credit processing system 1308 (1344). The credit processing system receives the outgoing credit data (1344) and generates a credit output (1346) as described herein, thus transferring credits off of the one or more credit meters and out of the billiards combined proposition wagering system.
In some embodiments, at a beginning of the wagering session, the process includes an application credit input to the billiards combined proposition wagering system with the process controller 1304 communicating with the credit processing system 1308 to receive incoming application credit data. The process controller 1306 uses the incoming application credit data to transfer application credits onto one or more application credit meters associated with one or more users of the billiards combined proposition wagering system, thus transferring application credits into the billiards combined proposition wagering system and on to the one or more application credit meters. The process controller 1304 uses the skill outcome data to determine an amount of application credit to award to a user based on the user's skillful interactions with an interactive application executed by the interactive controller 1302. Upon determining that the wagering session is completed, such as by receiving a cashout communication from one or more users of the billiards combined proposition wagering system, the process controller 1304 transfers application credits off of the one or more application credit meters, generates outgoing application credit data on the basis of the application credits transferred off of the one or more application credit meters, and communicates the outgoing application credit data to the credit processing system 1308. The credit processing system receives the outgoing application credit data and generates an application credit output as described herein, thus transferring application credits off of the one or more application credit meters and out of the billiards combined proposition wagering system.
While the above description may include many specific embodiments of the invention, these should not be construed as limitations on the scope of the invention, but rather as examples of embodiments thereof. It is therefore to be understood that the present invention can be practiced otherwise than specifically described, without departing from the scope and spirit of the present invention. Thus, embodiments of the present invention described herein should be considered in all respects as illustrative and not restrictive.
This application is a continuation of U.S. patent application Ser. No. 14/984,965, filed Dec. 30, 2015, which claims the benefit of U.S. Provisional Patent Application No. 62/099,129, filed Dec. 31, 2014, the disclosure of which is incorporated by reference herein in its entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5413357 | Schulze et al. | May 1995 | A |
| 5718429 | Keller | Feb 1998 | A |
| 5785592 | Jacobsen | Jul 1998 | A |
| 5853324 | Kami et al. | Dec 1998 | A |
| 5963745 | Collins et al. | Oct 1999 | A |
| 6050895 | Luciano | Apr 2000 | A |
| 6165071 | Weiss | Dec 2000 | A |
| 6227974 | Eilat | May 2001 | B1 |
| 6267669 | Luciano | Jul 2001 | B1 |
| 6276689 | Brown | Aug 2001 | B1 |
| 6302791 | Frohm et al. | Oct 2001 | B1 |
| 6685563 | Meekins et al. | Feb 2004 | B1 |
| 6712693 | Hettinger | Mar 2004 | B1 |
| 6761632 | Bansemer et al. | Jul 2004 | B2 |
| 6761633 | Riendeau | Jul 2004 | B2 |
| 6764397 | Robb | Jul 2004 | B1 |
| 6811482 | Letovsky | Nov 2004 | B2 |
| 6942568 | Baerlocher | Sep 2005 | B2 |
| 7056210 | Bansemer | Jun 2006 | B2 |
| 7118105 | Benevento | Oct 2006 | B2 |
| 7294058 | Slomiany | Nov 2007 | B1 |
| 7326115 | Baerlocher | Feb 2008 | B2 |
| 7361091 | Letovsky | Apr 2008 | B2 |
| 7517282 | Pryor | Apr 2009 | B1 |
| 7575517 | Parham et al. | Aug 2009 | B2 |
| 7682239 | Friedman et al. | Mar 2010 | B2 |
| 7720733 | Jung | May 2010 | B2 |
| 7753770 | Walker et al. | Jul 2010 | B2 |
| 7753790 | Nguyen | Jul 2010 | B2 |
| 7766742 | Bennett et al. | Aug 2010 | B2 |
| 7775885 | Van Luchene | Aug 2010 | B2 |
| 7798896 | Katz | Sep 2010 | B2 |
| 7828657 | Booth | Nov 2010 | B2 |
| 7917371 | Jung et al. | Mar 2011 | B2 |
| 7931531 | Oberberger | Apr 2011 | B2 |
| 7938727 | Konkle | May 2011 | B1 |
| 7950993 | Oberberger | May 2011 | B2 |
| 7967674 | Baerlocher | Jun 2011 | B2 |
| 7980948 | Rowe | Jul 2011 | B2 |
| 7996264 | Kusumoto et al. | Aug 2011 | B2 |
| 8012023 | Gates | Sep 2011 | B2 |
| 8047908 | Walker | Nov 2011 | B2 |
| 8047915 | Lyle | Nov 2011 | B2 |
| 8060829 | Jung et al. | Nov 2011 | B2 |
| 8075383 | Friedman et al. | Dec 2011 | B2 |
| 8087999 | Oberberger | Jan 2012 | B2 |
| 8113938 | Friedman et al. | Feb 2012 | B2 |
| 8118654 | Nicolas | Feb 2012 | B1 |
| 8128487 | Hamilton et al. | Mar 2012 | B2 |
| 8135648 | Oram | Mar 2012 | B2 |
| 8137193 | Kelly et al. | Mar 2012 | B1 |
| 8142272 | Walker | Mar 2012 | B2 |
| 8157653 | Buhr | Apr 2012 | B2 |
| 8167695 | Rowe | May 2012 | B2 |
| 8167699 | Inamura | May 2012 | B2 |
| 8177628 | Manning | May 2012 | B2 |
| 8182338 | Thomas | May 2012 | B2 |
| 8182339 | Anderson | May 2012 | B2 |
| 8187068 | Slomiany | May 2012 | B2 |
| 8206210 | Walker | Jun 2012 | B2 |
| 8241136 | Bennett | Aug 2012 | B2 |
| 8308544 | Friedman | Nov 2012 | B2 |
| 8430735 | Oberberger | Apr 2013 | B2 |
| 8475266 | Amone | Jul 2013 | B2 |
| 8480470 | Napolitano et al. | Jul 2013 | B2 |
| 8485893 | Rowe | Jul 2013 | B2 |
| 8622809 | Arora et al. | Jan 2014 | B1 |
| 8864564 | Oberberger | Oct 2014 | B2 |
| 8998694 | Rowe | Apr 2015 | B2 |
| 9070257 | Scalise | Jun 2015 | B1 |
| 9092946 | Rowe | Jul 2015 | B2 |
| 9111412 | Rowe | Aug 2015 | B2 |
| 9454873 | Rowe | Sep 2016 | B2 |
| 20010004609 | Walker et al. | Jun 2001 | A1 |
| 20010019965 | Ochi | Sep 2001 | A1 |
| 20020022509 | Nicastro et al. | Feb 2002 | A1 |
| 20020090990 | Joshi et al. | Jul 2002 | A1 |
| 20020175471 | Faith | Nov 2002 | A1 |
| 20030060286 | Walker et al. | Mar 2003 | A1 |
| 20030119576 | McClintic et al. | Jun 2003 | A1 |
| 20030139214 | Wolf et al. | Jul 2003 | A1 |
| 20030171149 | Rothschild | Sep 2003 | A1 |
| 20030204565 | Guo et al. | Oct 2003 | A1 |
| 20030211879 | Englman | Nov 2003 | A1 |
| 20040092313 | Saito et al. | May 2004 | A1 |
| 20040102238 | Taylor | May 2004 | A1 |
| 20040121839 | Webb | Jun 2004 | A1 |
| 20040225387 | Smith | Nov 2004 | A1 |
| 20050003878 | Updike | Jan 2005 | A1 |
| 20050096124 | Stronach | May 2005 | A1 |
| 20050116411 | Herrmann et al. | Jun 2005 | A1 |
| 20050192087 | Friedman et al. | Sep 2005 | A1 |
| 20050233791 | Kane | Oct 2005 | A1 |
| 20050233806 | Kane et al. | Oct 2005 | A1 |
| 20050239538 | Dixon | Oct 2005 | A1 |
| 20050269778 | Samberg | Dec 2005 | A1 |
| 20050288101 | Lockton et al. | Dec 2005 | A1 |
| 20060003823 | Zhang | Jan 2006 | A1 |
| 20060003830 | Walker et al. | Jan 2006 | A1 |
| 20060035696 | Walker | Feb 2006 | A1 |
| 20060040735 | Baerlocher | Feb 2006 | A1 |
| 20060068913 | Walker et al. | Mar 2006 | A1 |
| 20060084499 | Moshal | Apr 2006 | A1 |
| 20060084505 | Yoseloff | Apr 2006 | A1 |
| 20060135250 | Rossides | Jun 2006 | A1 |
| 20060154710 | Serafat | Jul 2006 | A1 |
| 20060166729 | Saffari et al. | Jul 2006 | A1 |
| 20060189371 | Walker et al. | Aug 2006 | A1 |
| 20060223611 | Baerlocher | Oct 2006 | A1 |
| 20060234791 | Nguyen et al. | Oct 2006 | A1 |
| 20060240890 | Walker | Oct 2006 | A1 |
| 20060246403 | Monpouet et al. | Nov 2006 | A1 |
| 20060258433 | Finocchio et al. | Nov 2006 | A1 |
| 20070026924 | Taylor | Feb 2007 | A1 |
| 20070026956 | Pearson | Feb 2007 | A1 |
| 20070035548 | Jung et al. | Feb 2007 | A1 |
| 20070038559 | Jung et al. | Feb 2007 | A1 |
| 20070064074 | Silverbrook et al. | Mar 2007 | A1 |
| 20070087799 | Van Luchene | Apr 2007 | A1 |
| 20070090597 | Shallow | Apr 2007 | A1 |
| 20070093299 | Bergeron | Apr 2007 | A1 |
| 20070099696 | Nguyen et al. | May 2007 | A1 |
| 20070117641 | Walker et al. | May 2007 | A1 |
| 20070129149 | Walker | Jun 2007 | A1 |
| 20070142108 | Linard | Jun 2007 | A1 |
| 20070156509 | Jung et al. | Jul 2007 | A1 |
| 20070167212 | Nguyen | Jul 2007 | A1 |
| 20070167239 | O'Rourke | Jul 2007 | A1 |
| 20070173311 | Morrow et al. | Jul 2007 | A1 |
| 20070191104 | Van Luchene | Aug 2007 | A1 |
| 20070202941 | Miltenberger | Aug 2007 | A1 |
| 20070203828 | Jung et al. | Aug 2007 | A1 |
| 20070207847 | Thomas | Sep 2007 | A1 |
| 20070259717 | Mattice | Nov 2007 | A1 |
| 20070293306 | Nee et al. | Dec 2007 | A1 |
| 20080004107 | Nguyen et al. | Jan 2008 | A1 |
| 20080014835 | Weston et al. | Jan 2008 | A1 |
| 20080015004 | Gatto et al. | Jan 2008 | A1 |
| 20080064488 | Oh | Mar 2008 | A1 |
| 20080070659 | Naicker | Mar 2008 | A1 |
| 20080070690 | Van Luchene | Mar 2008 | A1 |
| 20080070702 | Kaminkow | Mar 2008 | A1 |
| 20080096665 | Cohen | Apr 2008 | A1 |
| 20080108406 | Oberberger | May 2008 | A1 |
| 20080108425 | Oberberger | May 2008 | A1 |
| 20080113704 | Jackson | May 2008 | A1 |
| 20080119283 | Baerlocher | May 2008 | A1 |
| 20080146308 | Okada | Jun 2008 | A1 |
| 20080161081 | Berman | Jul 2008 | A1 |
| 20080176619 | Kelly | Jul 2008 | A1 |
| 20080191418 | Lutnick et al. | Aug 2008 | A1 |
| 20080195481 | Lutnick | Aug 2008 | A1 |
| 20080248850 | Schugar | Oct 2008 | A1 |
| 20080254893 | Patel | Oct 2008 | A1 |
| 20080274796 | Lube | Nov 2008 | A1 |
| 20080274798 | Walker et al. | Nov 2008 | A1 |
| 20080311980 | Cannon | Dec 2008 | A1 |
| 20080318668 | Ching | Dec 2008 | A1 |
| 20090011827 | Englman | Jan 2009 | A1 |
| 20090023489 | Toneguzzo | Jan 2009 | A1 |
| 20090023492 | Erfanian | Jan 2009 | A1 |
| 20090061974 | Lutnick et al. | Mar 2009 | A1 |
| 20090061975 | Ditchev | Mar 2009 | A1 |
| 20090061991 | Popovich | Mar 2009 | A1 |
| 20090061997 | Popovich | Mar 2009 | A1 |
| 20090061998 | Popovich | Mar 2009 | A1 |
| 20090061999 | Popovich | Mar 2009 | A1 |
| 20090082093 | Okada | Mar 2009 | A1 |
| 20090088239 | Iddings | Apr 2009 | A1 |
| 20090098934 | Amour | Apr 2009 | A1 |
| 20090118006 | Kelly et al. | May 2009 | A1 |
| 20090124344 | Mitchell et al. | May 2009 | A1 |
| 20090131158 | Brunet De Courssou et al. | May 2009 | A1 |
| 20090131175 | Kelly et al. | May 2009 | A1 |
| 20090143141 | Wells | Jun 2009 | A1 |
| 20090149233 | Strause et al. | Jun 2009 | A1 |
| 20090156297 | Andersson et al. | Jun 2009 | A1 |
| 20090176560 | Herrmann et al. | Jul 2009 | A1 |
| 20090176566 | Kelly | Jul 2009 | A1 |
| 20090181777 | Christiani | Jul 2009 | A1 |
| 20090221355 | Dunaevsky et al. | Sep 2009 | A1 |
| 20090233697 | Bennett | Sep 2009 | A1 |
| 20090239610 | Olive | Sep 2009 | A1 |
| 20090247272 | Abe | Oct 2009 | A1 |
| 20090270164 | Seelig | Oct 2009 | A1 |
| 20090275393 | Kisenwether | Nov 2009 | A1 |
| 20090291755 | Walker et al. | Nov 2009 | A1 |
| 20090309305 | May | Dec 2009 | A1 |
| 20090312093 | Walker et al. | Dec 2009 | A1 |
| 20090325686 | Davis | Dec 2009 | A1 |
| 20100004058 | Acres | Jan 2010 | A1 |
| 20100016056 | Thomas et al. | Jan 2010 | A1 |
| 20100029373 | Graham et al. | Feb 2010 | A1 |
| 20100035674 | Slomiany | Feb 2010 | A1 |
| 20100056247 | Nicely | Mar 2010 | A1 |
| 20100056260 | Fujimoto | Mar 2010 | A1 |
| 20100062836 | Young | Mar 2010 | A1 |
| 20100093420 | Wright | Apr 2010 | A1 |
| 20100093444 | Biggar et al. | Apr 2010 | A1 |
| 20100105454 | Weber | Apr 2010 | A1 |
| 20100120525 | Baerlocher et al. | May 2010 | A1 |
| 20100124983 | Gowin et al. | May 2010 | A1 |
| 20100137047 | Englman et al. | Jun 2010 | A1 |
| 20100174593 | Cao | Jul 2010 | A1 |
| 20100184509 | Sylla et al. | Jul 2010 | A1 |
| 20100203940 | Alderucci et al. | Aug 2010 | A1 |
| 20100210344 | Edidin et al. | Aug 2010 | A1 |
| 20100227672 | Amour | Sep 2010 | A1 |
| 20100227688 | Lee | Sep 2010 | A1 |
| 20100240436 | Wilson et al. | Sep 2010 | A1 |
| 20100285869 | Walker | Nov 2010 | A1 |
| 20100304825 | Davis | Dec 2010 | A1 |
| 20100304839 | Johnson | Dec 2010 | A1 |
| 20100304842 | Friedman et al. | Dec 2010 | A1 |
| 20110009177 | Katz | Jan 2011 | A1 |
| 20110009178 | Gerson | Jan 2011 | A1 |
| 20110045896 | Sak et al. | Feb 2011 | A1 |
| 20110070945 | Walker | Mar 2011 | A1 |
| 20110077087 | Walker et al. | Mar 2011 | A1 |
| 20110082571 | Murdock et al. | Apr 2011 | A1 |
| 20110105206 | Rowe et al. | May 2011 | A1 |
| 20110107239 | Adoni | May 2011 | A1 |
| 20110109454 | McSheffrey | May 2011 | A1 |
| 20110111820 | Filipour | May 2011 | A1 |
| 20110111837 | Gagner | May 2011 | A1 |
| 20110111841 | Tessmer | May 2011 | A1 |
| 20110118011 | Filipour et al. | May 2011 | A1 |
| 20110201413 | Oberberger | Aug 2011 | A1 |
| 20110207523 | Filipour et al. | Aug 2011 | A1 |
| 20110212766 | Bowers | Sep 2011 | A1 |
| 20110212767 | Barclay | Sep 2011 | A1 |
| 20110218028 | Acres | Sep 2011 | A1 |
| 20110218035 | Thomas | Sep 2011 | A1 |
| 20110230258 | Van Luchene | Sep 2011 | A1 |
| 20110230260 | Morrow et al. | Sep 2011 | A1 |
| 20110230267 | Van Luchene | Sep 2011 | A1 |
| 20110244944 | Baerlocher | Oct 2011 | A1 |
| 20110263312 | De Waal | Oct 2011 | A1 |
| 20110269522 | Nicely et al. | Nov 2011 | A1 |
| 20110275440 | Faktor | Nov 2011 | A1 |
| 20110287828 | Anderson et al. | Nov 2011 | A1 |
| 20110287841 | Watanabe | Nov 2011 | A1 |
| 20110312408 | Okuaki | Dec 2011 | A1 |
| 20110319169 | Lam | Dec 2011 | A1 |
| 20120004747 | Kelly | Jan 2012 | A1 |
| 20120028718 | Barclay et al. | Feb 2012 | A1 |
| 20120058814 | Lutnick | Mar 2012 | A1 |
| 20120077569 | Watkins | Mar 2012 | A1 |
| 20120108323 | Kelly | May 2012 | A1 |
| 20120135793 | Antonopoulos | May 2012 | A1 |
| 20120202587 | Allen | Aug 2012 | A1 |
| 20120276985 | Bennett | Nov 2012 | A1 |
| 20120302311 | Luciano | Nov 2012 | A1 |
| 20120322545 | Arnone et al. | Dec 2012 | A1 |
| 20130029760 | Wickett | Jan 2013 | A1 |
| 20130131848 | Arnone et al. | May 2013 | A1 |
| 20130190074 | Arnone et al. | Jul 2013 | A1 |
| 20130260869 | Leandro et al. | Oct 2013 | A1 |
| 20130273986 | Amone | Oct 2013 | A1 |
| 20140087801 | Nicely et al. | Mar 2014 | A1 |
| 20140087808 | Leandro et al. | Mar 2014 | A1 |
| 20140087809 | Leupp et al. | Mar 2014 | A1 |
| 20140357350 | Weingardt et al. | Dec 2014 | A1 |
| 20160189487 | Arnone | Jun 2016 | A1 |
| 20160253867 | Arnone | Sep 2016 | A1 |
| 20170148271 | Graboyes Goldman et al. | May 2017 | A1 |
| Number | Date | Country |
|---|---|---|
| 20040097610 | May 2004 | JP |
| Entry |
|---|
| U.S. Appl. No. 14/815,764 Arnone, et al. filed Jul. 31, 2015. |
| U.S. Appl. No. 14/815,774 Arnone, et al. filed Jul. 31, 2015. |
| U.S. Appl. No. 14/817,032 Arnone, et al. filed Aug. 3, 2015. |
| U.S. Appl. No. 14/822,890 Arnone, et al. filed Aug. 10, 2015. |
| U.S. Appl. No. 14/823,951 Arnone, et al. filed Aug. 11, 2015. |
| U.S. Appl. No. 14/823,987 Arnone, et al. filed Aug. 11, 2015. |
| U.S. Appl. No. 14/825,056 Arnone, et al. filed Aug. 12, 2015. |
| U.S. Appl. No. 14/835,590 Arnone, et al. filed Aug. 25, 2015. |
| U.S. Appl. No. 14/836,902 Arnone, et al. filed Aug. 26, 2015. |
| U.S. Appl. No. 14/839,647 Arnone, et al. filed Aug. 28, 2015. |
| U.S. Appl. No. 14/842,684 Arnone, et al. filed Sep. 1, 2015. |
| U.S. Appl. No. 14/842,785 Arnone, et al. filed Sep. 1, 2015. |
| U.S. Appl. No. 14/854,021 Arnone, et al. filed Sep. 14, 2015. |
| U.S. Appl. No. 14/855,322 Arnone, et al. filed Sep. 15, 2015. |
| U.S. Appl. No. 14/859,065 Arnone, et al. filed Sep. 18, 2015. |
| U.S. Appl. No. 14/865,422 Arnone, et al. filed Sep. 25, 2015. |
| U.S. Appl. No. 14/867,809 Arnone, et al. filed Sep. 28, 2015. |
| U.S. Appl. No. 14/868,287 Arnone, et al. filed Sep. 28, 2015. |
| U.S. Appl. No. 14/868,364 Arnone, et al. filed Sep. 28, 2015. |
| U.S. Appl. No. 14/869,809 Arnone, et al. filed Sep. 29, 2015. |
| U.S. Appl. No. 14/869,819 Arnone, et al. filed Sep. 29, 2015. |
| U.S. Appl. No. 14/885,894 Arnone, et al. filed Oct. 16, 2015. |
| U.S. Appl. No. 14/919,665 Arnone, et al. filed Oct. 21, 2015. |
| U.S. Appl. No. 14/942,844 Arnone, et al. filed Nov. 16, 2015. |
| U.S. Appl. No. 14/942,883 Arnone, et al. filed Nov. 16, 2015. |
| U.S. Appl. No. 14/949,759 Arnone, et al. filed Nov. 23, 2015. |
| U.S. Appl. No. 14/952,758 Arnone, et al. filed Nov. 25, 2015. |
| U.S. Appl. No. 14/952,769 Arnone, et al. filed Nov. 25, 2015. |
| U.S. Appl. No. 14/954,922 Arnone, et al. filed Nov. 30, 2015. |
| U.S. Appl. No. 14/954,931 Arnone, et al. filed Nov. 30, 2015. |
| U.S. Appl. No. 14/955,000 Arnone, et al. filed Nov. 30, 2015. |
| U.S. Appl. No. 14/956,301 Arnone, et al. filed Dec. 1, 2015. |
| U.S. Appl. No. 14/965,231 Arnone, et al. filed Dec. 10, 2015. |
| U.S. Appl. No. 14/965,846 Arnone, et al. filed Dec. 10, 2015. |
| U.S. Appl. No. 14/981,640 Arnone, et al. filed Dec. 28, 2015. |
| U.S. Appl. No. 14/981,775 Arnone, et al. filed Dec. 28, 2015. |
| U.S. Appl. No. 14/984,943 Arnone, et al. filed Dec. 30, 2015. |
| U.S. Appl. No. 14/984,965 Arnone, et al. filed Dec. 30, 2015. |
| U.S. Appl. No. 14/984,978 Arnone, et al. filed Dec. 30, 2015. |
| U.S. Appl. No. 14/985,107 Arnone, et al. filed Dec. 30, 2015. |
| U.S. Appl. No. 14/995,151 Arnone, et al. filed Jan. 13, 2016. |
| U.S. Appl. No. 14/974,432 Arnone, et al. filed Dec. 18, 2015. |
| U.S. Appl. No. 14/997,413 Arnone, et al. filed Jan. 15, 2016. |
| U.S. Appl. No. 15/002,233 Arnone, et al. filed Jan. 20, 2016. |
| U.S. Appl. No. 15/005,944 Arnone, et al. filed Jan. 25, 2016. |
| U.S. Appl. No. 15/011,322 Arnone, et al. filed Jan. 29, 2016. |
| U.S. Appl. No. 15/051,535 Arnone, et al. filed Feb. 23, 2016. |
| U.S. Appl. No. 15/053,236 Arnone, et al. filed Feb. 25, 2016. |
| U.S. Appl. No. 15/057,095 Arnone, et al. filed Feb. 29, 2016. |
| U.S. Appl. No. 15/060,502 Arnone, et al. filed Mar. 3, 2016. |
| U.S. Appl. No. 14/205,303 Arnone, et al., filed Mar. 11, 2014. |
| U.S. Appl. No. 14/205,306 Arnone, et al., filed Mar. 11, 2014. |
| U.S. Appl. No. 14/209,485 Arnone, et al., filed Mar. 13, 2014. |
| U.S. Appl. No. 14/214,310 Arnone, et al., filed Mar. 14, 2014. |
| U.S. Appl. No. 14.222,520 Arnone, et al., filed Mar. 21, 2014. |
| U.S. Appl. No. 14/253,813 Arnone, et al., filed Apr. 15, 2014. |
| U.S. Appl. No. 14/255,253 Arnone, et al., filed Apr. 17, 2014. |
| U.S. Appl. No. 14/255,919 Arnone, et al. filed Apr. 17, 2014. |
| U.S. Appl. No. 14/263,988 Arnone, et al. filed Apr. 28, 2014. |
| U.S. Appl. No. 14/270,335 Arnone, et al. filed May 5, 2014. |
| U.S. Appl. No. 14/271,360 Arnone, et al. filed May 6, 2014. |
| U.S. Appl. No. 13/961,849 Arnone, et al. filed Aug. 7, 2013. |
| U.S. Appl. No. 13/746,850 Arnone, et al. filed Jan. 22, 2013. |
| U.S. Appl. No. 14/288,169 Arnone, et al. filed May 27, 2014. |
| U.S. Appl. No. 14/304,027 Arnone, et al. filed Jun. 13, 2014. |
| U.S. Appl. No. 14/306,187 Arnone, et al. filed Jun. 16, 2014. |
| U.S. Appl. No. 14/312,623 Arnone, et al. filed Jun. 23, 2014. |
| U.S. Appl. No. 14/330,249 Arnone, et al. filed Jul. 14, 2014. |
| U.S. Appl. No. 14/339,142 Arnone, et al. filed Jul. 23, 2014. |
| U.S. Appl. No. 14/458,206 Arnone, et al. filed Aug. 12, 2014. |
| U.S. Appl. No. 14/461,344 Arnone, et al. filed Aug. 15, 2014. |
| U.S. Appl. No. 14/462,516 Arnone, et al. filed Aug. 18, 2014. |
| U.S. Appl. No. 14/467,646 Meyerhofer, et al. filed Aug. 25, 2014. |
| U.S. Appl. No. 14/474,023 Arnone, et al. filed Aug. 29, 2014. |
| U.S. Appl. No. 14/486,895 Arnone, et al. filed Sep. 15, 2014. |
| U.S. Appl. No. 14/507,206 Arnone, et al. filed Oct. 6, 2014. |
| U.S. Appl. No. 14/521,338 Arnone, et al. filed Oct. 22, 2014. |
| U.S. Appl. No. 14/535,808 Arnone, et al. filed Nov. 7, 2014. |
| U.S. Appl. No. 14/535,816 Arnone, et al. filed Nov. 7, 2014. |
| U.S. Appl. No. 14/536,231 Arnone, et al. filed Nov. 7, 2014. |
| U.S. Appl. No. 14/536,280 Arnone, et al. filed Nov. 7, 2014. |
| U.S. Appl. No. 14/549,137 Arnone, et al. filed Nov. 20, 2014. |
| U.S. Appl. No. 14/550,802 Arnone, et al. filed Nov. 21, 2014. |
| U.S. Appl. No. 14/555,401 Arnone, et al. filed Nov. 26, 2014. |
| U.S. Appl. No. 14/559,840 Arnone, et al. filed Dec. 3, 2014. |
| U.S. Appl. No. 14/564,834 Arnone, et al. filed Dec. 9, 2014. |
| U.S. Appl. No. 14/570,746 Arnone, et al. filed Dec. 15, 2014. |
| U.S. Appl. No. 14/570,857 Arnone, et al. filed Dec. 15, 2014. |
| U.S. Appl. No. 14/586,626 Arnone, et al. filed Dec. 30, 2014. |
| U.S. Appl. No. 14/586,639 Arnone, et al. filed Dec. 30, 2014. |
| U.S. Appl. No. 15/063,365 Arnone, et al. filed Mar. 7, 2016. |
| U.S. Appl. No. 15/063,496 Arnone, et al. filed Mar. 7, 2016. |
| U.S. Appl. No. 15/073,602 Arnone, et al. filed Mar. 17, 2016. |
| U.S. Appl. No. 15/074,999 Arnone, et al. filed Mar. 18, 2016. |
| U.S. Appl. No. 15/077,574 Arnone, et al. filed Mar. 22, 2016. |
| U.S. Appl. No. 15/083,284 Arnone, et al. filed Mar. 28, 2016. |
| U.S. Appl. No. 15/091,395 Arnone, et al. filed Apr. 5, 2016. |
| U.S. Appl. No. 15/093,685 Arnone, et al. filed Apr. 7, 2016. |
| U.S. Appl. No. 15/098,287 Arnone, et al. filed Apr. 13, 2016. |
| U.S. Appl. No. 15/098,313 Arnone, et al. filed Apr. 13, 2016. |
| U.S. Appl. No. 15/130,101 Arnone, et al. filed Apr. 15, 2016. |
| U.S. Appl. No. 15/133,624 Arnone, et al. filed Apr. 20, 2016. |
| U.S. Appl. No. 15/134,852 Arnone, et al. filed Apr. 21, 2016. |
| U.S. Appl. No. 15/139,148 Arnone, et al. filed Apr. 26, 2016. |
| U.S. Appl. No. 15/141,784 Arnone, et al. filed Apr. 29, 2016. |
| U.S. Appl. No. 15/155,107 Arnone, et al. filed May 16, 2016. |
| U.S. Appl. No. 15/156,222 Arnone, et al. filed May 16, 2016. |
| U.S. Appl. No. 15/158,530 Arnone, et al. filed May 18, 2016. |
| U.S. Appl. No. 15/161,174 Arnone, et al. filed May 20, 2016. |
| U.S. Appl. No. 15/170,773 Arnone, et al. filed Jun. 1, 2016. |
| U.S. Appl. No. 15/174,995 Arnone, et al. filed Jun. 6, 2016. |
| U.S. Appl. No. 15/179,940 Arnone, et al. filed Jun. 10, 2016. |
| U.S. Appl. No. 15/189,797 Arnone, et al. filed Jun. 22, 2016. |
| U.S. Appl. No. 15/190,745 Arnone, et al. filed Jun. 23, 2016. |
| U.S. Appl. No. 15/191,050 Arnone, et al. filed Jun. 23, 2016. |
| U.S. Appl. No. 15/219,257 Arnone, et al. filed Jul. 25, 2016. |
| U.S. Appl. No. 15/227,881 Arnone, et al. filed Aug. 3, 2016. |
| U.S. Appl. No. 15/241,683 Arnone, et al. filed Aug. 19, 2016. |
| U.S. Appl. No. 15/245,040 Arnone, et al. filed Aug. 23, 2016. |
| U.S. Appl. No. 15/233,294 Arnone, et al. filed Aug. 24, 2016. |
| U.S. Appl. No. 15/252,190 Arnone, et al. filed Aug. 30, 2016. |
| U.S. Appl. No. 15/255,789 Arnone, et al. filed Sep. 2, 2016. |
| U.S. Appl. No. 15/261,858 Arnone, et al. filed Sep. 9, 2016. |
| U.S. Appl. No. 15/264,521 Arnone, et al. filed Sep. 13, 2016. |
| U.S. Appl. No. 15/264,557 Arnone, et al. filed Sep. 13, 2016. |
| U.S. Appl. No. 15/271,214 Arnone, et al. filed Sep. 20, 2016. |
| U.S. Appl. No. 15/272,318 Arnone, et al. filed Sep. 21, 2016. |
| U.S. Appl. No. 15/273,260 Arnone, et al. filed Sep. 22, 2016. |
| U.S. Appl. No. 15/276,469 Arnone, et al. filed Sep. 26, 2016. |
| U.S. Appl. No. 15/280,255 Arnone, et al. filed Sep. 29, 2016. |
| U.S. Appl. No. 15/286,922 Arnone, et al. filed Oct. 6, 2016. |
| U.S. Appl. No. 15/287,129 Arnone, et al. filed Oct. 6, 2016. |
| U.S. Appl. No. 15/289,648 Arnone, et al. filed Oct. 10, 2016. |
| U.S. Appl. No. 15/297,019 Arnone, et al. filed Oct. 18, 2016. |
| U.S. Appl. No. 15/298,533 Arnone, et al. filed Oct. 20, 2016. |
| U.S. Appl. No. 15/336,696 Arnone, et al. filed Oct. 27, 2016. |
| U.S. Appl. No. 15/339,898 Arnone, et al. filed Oct. 31, 2016. |
| U.S. Appl. No. 15/345,451 Arnone, et al. filed Nov. 7, 2016. |
| U.S. Appl. No. 14/799,481 Arnone, et al. filed Jul. 14, 2015. |
| U.S. Appl. No. 15/362,214 Arnone, et al. filed Nov. 28, 2016. |
| U.S. Appl. No. 15/920,390 Arnone, et al. filed Mar. 13, 2018. |
| U.S. Appl. No. 15/922,816 Arnone, et al. filed Mar. 15, 2018. |
| U.S. Appl. No. 15/922,905 Arnone, et al. filed Mar. 15, 2018. |
| U.S. Appl. No. 15/925,268 Arnone, et al. filed Mar. 19, 2018. |
| U.S. Appl. No. 15/925,751 Arnone, et al. filed Mar. 19, 2018. |
| U.S. Appl. No. 15/933,319 Arnone, et al. filed Mar. 22, 2018. |
| U.S. Appl. No. 15/935,956 Arnone, et al. filed Mar. 26, 2018. |
| U.S. Appl. No. 15/943,207 Arnone, et al. filed Apr. 2, 2018. |
| U.S. Appl. No. 15/948,607 Arnone, et al. filed Apr. 9, 2018. |
| U.S. Appl. No. 15/949,812 Arnone, et al. filed Apr. 10, 2018. |
| U.S. Appl. No. 15/951,155 Arnone, et al. filed Apr. 11, 2018. |
| U.S. Appl. No. 15/954,094 Arnone, et al. filed Apr. 16, 2018. |
| U.S. Appl. No. 15/954,136 Arnone, et al. filed Apr. 16, 2018. |
| U.S. Appl. No. 15/961,375 Arnone, et al. filed Apr. 24, 2018. |
| U.S. Appl. No. 15/961,382 Arnone, et al. filed Apr. 24, 2018. |
| U.S. Appl. No. 15/966,590 Arnone, et al. filed Apr. 30, 2018. |
| U.S. Appl. No. 15/968,723 Arnone, et al. filed May 1, 2018. |
| U.S. Appl. No. 15/971,288 Arnone, et al. filed May 4, 2018. |
| U.S. Appl. No. 15/978,087 Arnone, et al. filed May 11, 2018. |
| U.S. Appl. No. 15/979,391 Arnone, et al. filed May 14, 2018. |
| U.S. Appl. No. 15/984,168 Arnone, et al. filed May 18, 2018. |
| U.S. Appl. No. 15/991,576 Arnone, et al. filed May 29, 2018. |
| U.S. Appl. No. 15/991,594 Arnone, et al. filed May 29, 2018. |
| U.S. Appl. No. 15/996,906 Arnone, et al. filed Jun. 4, 2018. |
| U.S. Appl. No. 16/005,017 Arnone, et al. filed Jun. 11, 2018. |
| U.S. Appl. No. 16/005,108 Arnone, et al. filed Jun. 11, 2018. |
| U.S. Appl. No. 16/011,110 Arnone, et al. filed Jun. 18, 2018. |
| U.S. Appl. No. 16/011,116 Arnone, et al. filed Jun. 18, 2018. |
| U.S. Appl. No. 16/017,976 Arnone, et al. filed Jun. 25, 2018. |
| U.S. Appl. No. 14/185,847 Arnone, et al., filed Feb. 20, 2014. |
| U.S. Appl. No. 14/203,459 Arnone, et al., filed Mar. 10, 2014. |
| U.S. Appl. No. 14/205,272 Arnone, et al., filed Mar. 11, 2014. |
| U.S. Appl. No. 13/854,658, Arnone, et al., filed Apr. 1, 2013. |
| U.S. Appl. No. 13/855,676, Arnone, et al., filed Apr. 2, 2013. |
| U.S. Appl. No. 13/872,946, Arnone, et al., filed Apr. 29, 2013. |
| U.S. Appl. No. 13/886,245, Arnone, et al., filed May 2, 2013. |
| U.S. Appl. No. 13/888,326, Arnone, et al., filed May 6, 2013. |
| U.S. Appl. No. 13/890,207, Arnone, et al., filed May 8, 2013. |
| U.S. Appl. No. 13/896,783, Arnone, et al., filed May 17, 2013. |
| U.S. Appl. No. 13/898,222, Arnone, et al., filed May 20, 2013. |
| U.S. Appl. No. 13/900,363, Arnone, et al., filed May 22, 2013. |
| U.S. Appl. No. 13/903,895, Arnone, et al., filed May 28, 2013. |
| U.S. Appl. No. 13/917,513, Arnone, et al., filed Jun. 13, 2013. |
| U.S. Appl. No. 13/917,529, Arnone, et al., filed Jun. 13, 2013. |
| U.S. Appl. No. 13/920,031, Arnone, et al., filed Jun. 17, 2013. |
| U.S. Appl. No. 13/928,166, Arnone, et al., filed Jun. 26, 2013. |
| U.S. Appl. No. 13/935,410, Arnone, et al., filed Jul. 3, 2013. |
| U.S. Appl. No. 13/935,468, Arnone, et al., filed Jul. 3, 2013. |
| U.S. Appl. No. 13/686,876, Arnone, et al., filed Nov. 27, 2012. |
| U.S. Appl. No. 13/944,662, Arnone, et al., filed Jul. 17, 2013. |
| U.S. Appl. No. 13/962,815, Arnone, et al., filed Aug. 8, 2013. |
| U.S. Appl. No. 13/962,839, Meyerhofer, et al., filed Aug. 8, 2013. |
| U.S. Appl. No. 14/018,315, Arnone, et al., filed Sep. 4, 2013. |
| U.S. Appl. No. 14/019,384, Arnone, et al., filed Sep. 5, 2013. |
| U.S. Appl. No. 14/023,432, Arnone, et al., filed Sep. 10, 2013. |
| U.S. Appl. No. 13/600,671, Arnone, et al., filed Aug. 31, 2012. |
| U.S. Appl. No. 13/582,408, Arnone, et al., filed Sep. 26, 2012. |
| U.S. Appl. No. 13/849,458, Arnone, et al., filed Mar. 22, 2013. |
| U.S. Appl. No. 14/135,562, Arnone, et al., filed Dec. 19, 2013. |
| U.S. Appl. No. 14/080,767, Arnone, et al., filed Nov. 14, 2013. |
| U.S. Appl. No. 14/043,838, Arnone, et al., filed Oct. 1, 2013. |
| U.S. Appl. No. 14/162,735, Arnone, et al., filed Jan. 23, 2014. |
| U.S. Appl. No. 14/161,230, Arnone, et al., filed Jan. 22, 2014. |
| U.S. Appl. No. 14/083,331, Arnone, et al., filed Nov. 18, 2013. |
| U.S. Appl. No. 14/014,310, Arnone, et al., filed Aug. 29, 2013. |
| U.S. Appl. No. 14/152,953, Arnone, et al., filed Jan. 10, 2014. |
| U.S. Appl. No. 14/162,724, Arnone, et al., filed Jan. 23, 2014. |
| U.S. Appl. No. 14/104,897, Arnone, et al., filed Dec. 12, 2013. |
| U.S. Appl. No. 14/174,813 Arnone, et al., filed Feb. 6, 2014. |
| U.S. Appl. No. 14/175,986 Arnone, et al., filed Feb. 7, 2014. |
| U.S. Appl. No. 14/176,014 Arnone, et al., filed Feb. 7, 2014. |
| U.S. Appl. No. 14/179,487 Arnone, et al., filed Feb. 12, 2014. |
| U.S. Appl. No. 14/179,492 Arnone, et al., filed Feb. 12, 2014. |
| U.S. Appl. No. 14/181,190 Arnone, et al., filed Feb. 14, 2014. |
| U.S. Appl. No. 14/186,393 Arnone, et al., filed Feb. 21, 2014. |
| U.S. Appl. No. 14/188,587 Arnone, et al., filed Feb. 24, 2014. |
| U.S. Appl. No. 15/362,660 Arnone, et al. filed Nov. 28, 2016. |
| U.S. Appl. No. 15/365,628 Arnone, et al. filed Nov. 30, 2016. |
| U.S. Appl. No. 15/367,541 Arnone, et al. filed Dec. 2, 2016. |
| U.S. Appl. No. 15/369,394 Arnone, et al. filed Dec. 5, 2016. |
| U.S. Appl. No. 15/370,425 Arnone, et al. filed Dec. 6, 2016. |
| U.S. Appl. No. 15/375,711 Arnone, et al. filed Dec. 12, 2016. |
| U.S. Appl. No. 15/387,117 Arnone, et al. filed Dec. 21, 2016. |
| U.S. Appl. No. 15/392,887 Arnone, et al. filed Dec. 28, 2016. |
| U.S. Appl. No. 15/393,212 Arnone, et al. filed Dec. 28, 2016. |
| U.S. Appl. No. 15/394,257 Arnone, et al. filed Dec. 29, 2016. |
| U.S. Appl. No. 15/396,352 Arnone, et al. filed Dec. 30, 2016. |
| U.S. Appl. No. 15/396,354 Arnone, et al. filed Dec. 30, 2016. |
| U.S. Appl. No. 15/396,365 Arnone, et al. filed Dec. 30, 2016. |
| U.S. Appl. No. 15/406,474 Arnone, et al. filed Jan. 13, 2017. |
| U.S. Appl. No. 15/413,322 Arnone, et al. filed Jan. 23, 2017. |
| U.S. Appl. No. 15/415,833 Arnone, et al. filed Jan. 25, 2017. |
| U.S. Appl. No. 15/417,030 Arnone, et al. filed Jan. 26, 2017. |
| U.S. Appl. No. 15/422,453 Arnone, et al. filed Feb. 1, 2017. |
| U.S. Appl. No. 15/431,631 Arnone, et al. filed Feb. 13, 2017. |
| U.S. Appl. No. 15/434,843 Arnone, et al. filed Feb. 16, 2017. |
| U.S. Appl. No. 15/439,499 Arnone, et al. filed Feb. 22, 2017. |
| U.S. Appl. No. 15/449,249 Arnone, et al. filed Mar. 3, 2017. |
| U.S. Appl. No. 15/449,256 Arnone, et al. filed Mar. 3, 2017. |
| U.S. Appl. No. 15/450,287 Arnone, et al. filed Mar. 6, 2017. |
| U.S. Appl. No. 15/456,079 Arnone, et al. filed Mar. 10, 2017. |
| U.S. Appl. No. 15/457,827 Arnone, et al. filed Mar. 13, 2017. |
| U.S. Appl. No. 15/458,490 Arnone, et al. filed Mar. 14, 2017. |
| U.S. Appl. No. 15/460,195 Arnone, et al. filed Mar. 15, 2017. |
| U.S. Appl. No. 15/463,725 Arnone, et al. filed Mar. 20, 2017. |
| U.S. Appl. No. 15/464,282 Arnone, et al. filed Mar. 20, 2017. |
| U.S. Appl. No. 15/465,521 Arnone, et al. filed Mar. 21, 2017. |
| U.S. Appl. No. 15/470,869 Arnone, et al. filed Mar. 27, 2017. |
| U.S. Appl. No. 15/473,523 Arnone, et al. filed Mar. 29, 2017. |
| U.S. Appl. No. 15/483,773 Arnone, et al. filed Apr. 10, 2017. |
| U.S. Appl. No. 15/489,343 Arnone, et al. filed Apr. 17, 2017. |
| U.S. Appl. No. 15/491,617 Arnone, et al. filed Apr. 19, 2017. |
| U.S. Appl. No. 15/583,295 Arnone, et al. filed May 1, 2017, 2017. |
| U.S. Appl. No. 15/589,780 Arnone, et al. filed May 8, 2017. |
| U.S. Appl. No. 15/597,123 Arnone, et al. filed May 16, 2017. |
| U.S. Appl. No. 15/597,812 Arnone, et al. filed May 17, 2017. |
| U.S. Appl. No. 15/599,590 Arnone, et al. filed May 19, 2017. |
| U.S. Appl. No. 15/605,688 Arnone, et al. filed May 25, 2017. |
| U.S. Appl. No. 15/605,705 Arnone, et al. filed May 25, 2017. |
| U.S. Appl. No. 15/626,754 Arnone, et al. filed Jun. 19, 2017. |
| U.S. Appl. No. 15/631,762 Arnone, et al. filed Jun. 23, 2017. |
| U.S. Appl. No. 15/632,478 Arnone, et al. filed Jun. 26, 2017. |
| U.S. Appl. No. 15/632,479 Arnone, et al. filed Jun. 26, 2017. |
| U.S. Appl. No. 15/632,943 Arnone, et al. filed Jun. 26, 2017. |
| U.S. Appl. No. 15/632,950 Arnone, et al. filed Jun. 26, 2017. |
| U.S. Appl. No. 15/641,119 Arnone, et al. filed Jul. 3, 2017. |
| U.S. Appl. No. 14/586,645 Arnone, et al. filed Dec. 30, 2014. |
| U.S. Appl. No. 14/598,151 Arnone, et al. filed Jan. 15, 2015. |
| U.S. Appl. No. 14/601,063 Arnone, et al. filed Jan. 20, 2015. |
| U.S. Appl. No. 14/601,108 Arnone, et al. filed Jan. 20, 2015. |
| U.S. Appl. No. 14/608,000 Arnone, et al. filed Jan. 28, 2015. |
| U.S. Appl. No. 14/608,087 Arnone, et al. filed Jan. 28, 2015. |
| U.S. Appl. No. 14/608,093 Arnone, et al. filed Jan. 28, 2015. |
| U.S. Appl. No. 14/610,897 Arnone, et al. filed Jan. 30, 2015. |
| U.S. Appl. No. 14/611,077 Arnone, et al. filed Jan. 30, 2015. |
| U.S. Appl. No. 14/604,629 Arnone, et al. filed Jan. 23, 2015. |
| U.S. Appl. No. 14/625,475 Arnone, et al. filed Feb. 18, 2015. |
| U.S. Appl. No. 14/617,852 Arnone, et al. filed Feb. 9, 2015. |
| U.S. Appl. No. 14/627,428 Arnone, et al. filed Feb. 20, 2015. |
| U.S. Appl. No. 14/642,427 Arnone, et al. filed Mar. 9, 2015. |
| U.S. Appl. No. 14/665,991 Arnone, et al. filed Mar. 23, 2015. |
| U.S. Appl. No. 14/666,010 Arnone, et al. filed Mar. 23, 2015. |
| U.S. Appl. No. 14/666,022 Arnone, et al. filed Mar. 23, 2015. |
| U.S. Appl. No. 14/642,623 Arnone, et al. filed Mar. 9, 2015. |
| U.S. Appl. No. 14/663,337 Arnone, et al. filed Mar. 19, 2015. |
| U.S. Appl. No. 14/666,284 Arnone, et al. filed Mar. 23, 2015. |
| U.S. Appl. No. 14/679,885 Arnone, et al. filed Apr. 6, 2015. |
| U.S. Appl. No. 14/685,378 Arnone, et al. filed Apr. 13, 2015. |
| U.S. Appl. No. 14/686,675 Arnone, et al. filed Apr. 14, 2015. |
| U.S. Appl. No. 14/686,678 Arnone, et al. filed Apr. 14, 2015. |
| U.S. Appl. No. 14/701,430 Arnone, et al. filed Apr. 30, 2015. |
| U.S. Appl. No. 14/703,721 Arnone, et al. filed May 4, 2015. |
| U.S. Appl. No. 14/708,138 Arnone, et al. filed May 8, 2015. |
| U.S. Appl. No. 14/708,141 Arnone, et al. filed May 8, 2015. |
| U.S. Appl. No. 14/708,160 Arnone, et al. filed May 8, 2015. |
| U.S. Appl. No. 14/708,161 Arnone, et al. filed May 8, 2015. |
| U.S. Appl. No. 14/708,162 Arnone, et al. filed May 8, 2015. |
| U.S. Appl. No. 14/710,483 Arnone, et al. filed May 12, 2015. |
| U.S. Appl. No. 14/714,084 Arnone, et al. filed May 15, 2015. |
| U.S. Appl. No. 14/715,463 Arnone, et al. filed May 18, 2015. |
| U.S. Appl. No. 14/720,620 Arnone, et al. filed May 22, 2015. |
| U.S. Appl. No. 14/720,624 Arnone, et al. filed May 22, 2015. |
| U.S. Appl. No. 14/720,626 Arnone, et al. filed May 22, 2015. |
| U.S. Appl. No. 14/727,726 Arnone, et al. filed Jun. 1, 2015. |
| U.S. Appl. No. 14/730,183 Arnone, et al. filed Jun. 3, 2015. |
| U.S. Appl. No. 14/731,321 Arnone, et al. filed Jun. 4, 2015. |
| U.S. Appl. No. 14/740,078 Arnone, et al. filed Jun. 15, 2015. |
| U.S. Appl. No. 14/742,517 Arnone, et al. filed Jun. 17, 2015. |
| U.S. Appl. No. 14/743,708 Arnone, et al. filed Jun. 18, 2015. |
| U.S. Appl. No. 14/746,731 Arnone, et al. filed Jun. 22, 2015. |
| U.S. Appl. No. 14/748,122 Arnone, et al. filed Jun. 23, 2015. |
| U.S. Appl. No. 14/788,581 Arnone, et al. filed Jun. 30, 2015. |
| U.S. Appl. No. 14/793,685 Arnone, et al. filed Jul. 7, 2015. |
| U.S. Appl. No. 14/793,704 Arnone, et al. filed Jul. 7, 2015. |
| U.S. Appl. No. 14/797,016 Arnone, et al. filed Jul. 10, 2015. |
| U.S. Appl. No. 15/651,934 Arnone, et al. filed Jul. 17, 2017. |
| U.S. Appl. No. 15/657,826 Arnone, et al. filed Jul. 24, 2017. |
| U.S. Appl. No. 15/657,835 Arnone, et al. filed Jul. 24, 2017. |
| U.S. Appl. No. 15/664,535 Arnone, et al. filed Jul. 31, 2017. |
| U.S. Appl. No. 15/667,168 Arnone, et al. filed Aug. 2, 2017. |
| U.S. Appl. No. 15/267,511 Rowe, filed Sep. 16, 2016. |
| U.S. Appl. No. 15/681,966 Arnone, et al. filed Aug. 21, 2017. |
| U.S. Appl. No. 15/681,970 Arnone, et al. filed Aug. 21, 2017. |
| U.S. Appl. No. 15/681,978 Arnone, et al. filed Aug. 21, 2017. |
| U.S. Appl. No. 15/687,922 Arnone, et al. filed Aug. 28, 2017. |
| U.S. Appl. No. 15/687,927 Arnone, et al. filed Aug. 28, 2017. |
| U.S. Appl. No. 15/694,520 Arnone, et al. filed Sep. 1, 2017. |
| U.S. Appl. No. 15/694,738 Arnone, et al. filed Sep. 1, 2017. |
| U.S. Appl. No. 15/713,595 Arnone, et al. filed Sep. 22, 2017. |
| U.S. Appl. No. 15/715,144 Arnone, et al. filed Sep. 25, 2017. |
| U.S. Appl. No. 15/716,317 Arnone, et al. filed Sep. 26, 2017. |
| U.S. Appl. No. 15/716,318 Arnone, et al. filed Sep. 26, 2017. |
| U.S. Appl. No. 15/728,096 Arnone, et al. filed Oct. 9, 2017. |
| U.S. Appl. No. 15/784,961 Arnone, et al. filed Oct. 16, 2017. |
| U.S. Appl. No. 15/790,482 Arnone, et al. filed Oct. 23, 2017. |
| U.S. Appl. No. 15/794,712 Arnone, et al. filed Oct. 26, 2017. |
| U.S. Appl. No. 15/797,571 Arnone, et al. filed Oct. 30, 2017. |
| U.S. Appl. No. 15/804,413 Arnone, et al. filed Nov. 6, 2017. |
| U.S. Appl. No. 15/811,412 Arnone, et al. filed Nov. 13, 2017. |
| U.S. Appl. No. 15/811,419 Arnone, et al. filed Nov. 13, 2017. |
| U.S. Appl. No. 15/815,629 Arnone, et al. filed Nov. 16, 2017. |
| U.S. Appl. No. 15/822,908 Arnone, et al. filed Nov. 27, 2017. |
| U.S. Appl. No. 15/822,912 Arnone, et al. filed Nov. 27, 2017. |
| U.S. Appl. No. 15/830,614 Arnone, et al. filed Dec. 4, 2017. |
| U.S. Appl. No. 15/834,006 Arnone, et al. filed Dec. 6, 2017. |
| U.S. Appl. No. 15/837,795 Arnone, et al. filed Dec. 11, 2017. |
| U.S. Appl. No. 15/845,433 Arnone, et al. filed Dec. 18, 2017. |
| U.S. Appl. No. 15/858,817 Arnone, et al. filed Dec. 29, 2017. |
| U.S. Appl. No. 15/858,826 Arnone, et al. filed Dec. 29, 2017. |
| U.S. Appl. No. 15/862,329 Arnone, et al. filed Jan. 4, 2018. |
| U.S. Appl. No. 15/864,737 Arnone, et al. filed Jan. 8, 2018. |
| U.S. Appl. No. 15/882,328 Arnone, et al. filed Jan. 29, 2018. |
| U.S. Appl. No. 15/882,333 Arnone, et al. filed Jan. 29, 2018. |
| U.S. Appl. No. 15/882,428 Arnone, et al. filed Jan. 29, 2018. |
| U.S. Appl. No. 15/882,447 Arnone, et al. filed Jan. 29, 2018. |
| U.S. Appl. No. 15/882,850 Arnone, et al. filed Jan. 29, 2018. |
| U.S. Appl. No. 15/882,902 Arnone, et al. filed Jan. 29, 2018. |
| U.S. Appl. No. 15/888,512 Arnone, et al. filed Feb. 5, 2018. |
| U.S. Appl. No. 15/894,398 Arnone, et al. filed Feb. 12, 2018. |
| U.S. Appl. No. 15/912,019 Arnone, et al. filed Mar. 5, 2018. |
| U.S. Appl. No. 15/912,026 Arnone, et al. filed Mar. 5, 2018. |
| U.S. Appl. No. 15/912,529 Arnone, et al. filed Mar. 5, 2018. |
| U.S. Appl. No. 15/920,374 Arnone, et al. filed Mar. 13, 2018. |
| U.S. Appl. No. 15/920,380 Arnone, et al. filed Mar. 13, 2018. |
| U.S. Appl. No. 15/920,388 Arnone, et al. filed Mar. 13, 2018. |
| Number | Date | Country | |
|---|---|---|---|
| 20180336763 A1 | Nov 2018 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62099129 | Dec 2014 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 14984965 | Dec 2015 | US |
| Child | 16048893 | US |
