Jurisdictional control in a wagering game system plugin architecture
View Patent ↗A wagering game system and operations for a wagering game system include a plugin architecture and framework in which wagering game system applications utilize plugins to provide functionality for an application or service. The plugins may be independently tested and verified by a jurisdictional testing agent to confirm that the operation of the plugin complies with the rules and regulations for a jurisdiction. If plugins are added or updated, a system vendor may submit only those plugins that require jurisdictional approval to a testing agent. An application or service may download plugins that are approved for use in the jurisdiction in which the application or service is operating.
1. A method comprising:
determining a set of plugins associated with a host application;
receiving from a data repository metadata for each plugin in the set of plugins, the metadata including an indicator that jurisdictional approval is required for the plugin and data indicating whether jurisdictional approval has been obtained;
determining by one or more processors a first subset plugins of the set of plugins that have received jurisdictional approval;
determining by the one or more processors, based at least in part on the metadata for each plugin, a second subset of the set of plugins that have not received jurisdictional approval; and
submitting the second subset of plugins to a jurisdictional testing agent, wherein the first subset of plugins is not submitted to the jurisdictional testing agent.
2. The method of claim 1 , wherein determining a set of plugins that are associated with a host application comprises reading the set of plugins from a catalog associated with the application.
3. The method of claim 1 , and further comprising determining that jurisdictional approval is required for the host application in response to detecting an update to a plugin associated with the host application.
4. The method of claim 1 , wherein submitting the second subset of plugins to a jurisdictional testing agent includes submitting a change log identifying changes to the second subset of plugins.
5. A method comprising:
initiating by one or more processors execution of a host application of a wagering game system;
receiving by the one or more processors a catalog identifying one or more plugins for the host application;
receiving from a data repository metadata for each plugin in the one or more plugins, the metadata including an indicator that jurisdictional approval is required for the plugin and data indicating whether jurisdictional approval has been obtained;
selecting by the one or more processors a plugin of the one or more plugins;
determining by the one or more processors, based at least in part on the metadata for the plugin, whether the plugin is authorized for a current jurisdiction; and
in response to determining that the plugin is authorized for the current jurisdiction, obtaining the plugin and registering the plugin with the application.
6. The method of claim 5 , and further comprising:
determining a role associated with a user of the host application; and
determining whether the plugin is authorized for the role.
7. The method of claim 5 , and further comprising:
upon determining the occurrence of a replacement event during the execution of the host application, replacing a first plugin with a second plugin.
8. The method of claim 7 , wherein the replacement event is a debug event and wherein the second plugin comprises a debug version of the first plugin.
9. The method of claim 7 , wherein the replacement event is a new version event and wherein the second plugin comprises a newer version of the first plugin.
10. A wagering game system comprising:
a repository maintaining a plurality of plugins; and
a jurisdictional approval module executable by one or more processors communicably coupled to the repository and configured to:
determine a set of plugins of the plurality of plugins that are associated with a host application;
receive from the repository metadata for each plugin in the set of plugins, the metadata including an indicator that jurisdictional approval is required for the plugin and data indicating whether jurisdictional approval has been obtained;
determine a first subset plugins of the set of plugins that have received jurisdictional approval;
determine, based at least in part on the metadata for each plugin, a second subset of the set of plugins that have not received jurisdictional approval;
submit the second subset of plugins to a jurisdictional testing agent, wherein the first subset of plugins is not submitted to the jurisdictional testing agent.
11. The wagering game system of claim 10 , wherein the jurisdictional approval module is further configured to read the set of plugins from a catalog associated with the application.
12. The wagering game system of claim 10 , wherein the jurisdictional approval module is further configured to determine that jurisdictional approval is required for the host application in response to detecting an update to a plugin associated with the host application.
13. The wagering game system of claim 10 , wherein the jurisdictional approval module is further configured to submit a change log identifying changes to the second subset of plugins.
14. One or more non-transitory computer-readable media having stored thereon computer executable instructions for causing one or more processors to perform operations comprising:
determining a set of plugins that are associated with a host application;
receiving from a data repository metadata for each plugin in the set of plugins, the metadata including an indicator that jurisdictional approval is required for the plugin and data indicating whether jurisdictional approval has been obtained;
determining a first subset plugins of the set of plugins that have received jurisdictional approval;
determining, based at least in part on the metadata, a second subset of the set of plugins that have not received jurisdictional approval; and
submitting the second subset of plugins to a jurisdictional testing agent, wherein the first subset of plugins is not submitted to the jurisdictional testing agent.
15. The one or more non-transitory computer-readable media of claim 14 , wherein determining a set of plugins that are associated with a host application comprises reading the set of plugins from a catalog associated with the application.
16. The one or more non-transitory computer-readable media of claim 14 , wherein the operations further comprise determining that jurisdictional approval is required for the host application in response to detecting an update to a plugin associated with the host application.
17. The one or more non-transitory computer-readable media of claim 14 , wherein submitting the second subset of plugins to a jurisdictional testing agent includes submitting a change log identifying changes to the second subset of plugins.
18. One or more non-transitory computer-readable media having stored thereon computer executable instructions for causing one or more processors to perform operations comprising:
initiating execution of a host application of a wagering game system;
receiving a catalog identifying one or more plugins for the host application;
receiving from a data repository metadata for each plugin in the one or more plugins, the metadata including an indicator that jurisdictional approval is required for the plugin and data indicating whether jurisdictional approval has been obtained;
selecting a plugin of the one or more plugins;
determining, based at least in part on the metadata for the plugin, whether the plugin is authorized for a current jurisdiction; and
in response to determining that the plugin is authorized for the current jurisdiction, obtaining the plugin and registering the plugin with the application.
19. The one or more non-transitory computer-readable media of claim 18 , wherein the operations further comprise:
determining a role associated with a user of the host application; and
determining whether the plugin is authorized for the role.
20. The one or more non-transitory computer-readable media of claim 18 , wherein the operations further comprise:
upon determining the occurrence of a replacement event during the execution of the host application, replacing a first plugin with a second plugin.
21. The one or more non-transitory computer-readable media of claim 20 , wherein the replacement event is a debug event and wherein the second plugin comprises a debug version of the first plugin.
22. The one or more non-transitory computer-readable media of claim 20 , wherein the replacement event is a new version event and wherein the second plugin comprises a newer version of the first plugin.
23. A system comprising
means for determining a set of plugins that are associated with a host application;
means for receiving metadata for each plugin in the set of plugins, the metadata including an indicator that jurisdictional approval is required for the plugin and data indicating whether jurisdictional approval has been obtained;
means for determining a first subset plugins of the set of plugins that have received jurisdictional approval;
means for determining, based at least in part on the metadata for each plugin, a second subset of the set of plugins that have not received jurisdictional approval; and
means for submitting the second subset of plugins to a jurisdictional testing agent, wherein the first subset of plugins is not submitted to the jurisdictional testing agent.
24. The system of claim 23 , wherein determining a set of plugins that are associated with a host application comprises reading the set of plugins from a catalog associated with the application.
25. The system of claim 23 , and further comprising means for determining that jurisdictional approval is required for the host application in response to detecting an update to a plugin associated with the host application.