Events Agent Framework Decouples Wagering Game Content
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Online wagering games often present players with inconsistent interfaces and lack the ability for operators to provide out-of-game responses based on in-game events, as third-party-supplied games do not allow visibility into game content events.
Innovation Solution
An events agent framework is introduced that decouples game content and external components, enabling in-game event notifications to trigger out-of-game responses through a standardized messaging protocol, allowing operators to provide real-time updates and promotions based on game events.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If third-party game content software is used to provide wagering game play, then game content diversity and supplier independence are improved, but operator visibility into in-game events is lost and consistent interface implementation becomes difficult
Solution Approach 1:
An events agent framework is introduced as an intermediary component that sits between the third-party game content software and the operator's external components. This framework includes event sources within the game content that publish in-game events, and event subscribers (both front-end and back-end) that consume these events through a standardized protocol. This allows operators to receive and respond to in-game events without requiring direct access to or modification of the third-party game content software, thus maintaining game diversity while restoring event visibility.
2Adaptability or versatility
If third-party game content software is used, then game supply flexibility is improved, but interface consistency and out-of-game response capability deteriorate
Solution Approach 1:
The events agent framework implements a universal standardized messaging protocol that works across all third-party game content software. Event sources in different games publish events using common event types and data structures, allowing the same front-end and back-end event subscribers to handle events from multiple different game providers. This universal interface layer ensures consistent out-of-game responses regardless of which third-party game content is being used, while maintaining the flexibility to support diverse game supplies.
3Loss of information
If direct integration with game content software is implemented, then event visibility is improved, but system complexity and coupling between components increase
Solution Approach 1:
The system is segmented into distinct functional components: event sources within game content, an events agent framework, front-end event subscribers, and back-end event subscribers. Each component has a specific responsibility and communicates through well-defined interfaces. The event sources publish events without needing to know about subscribers, and subscribers consume events without needing to know about sources. This segmentation reduces coupling between components while maintaining full event visibility throughout the system.
Data Source
AI summary
An events agent core library of software functions, when executed by at least one processor of a client device, receives notifications of in-game events from game content software downloaded to the client device from a game supplier server and executing on the client device providing wagering game play to a user of the client device. Based on the notifications, the events agent core may report at least some of the in-game events to a front-end set of processor-executable instructions downloaded to the client device from a gaming operator server different from the game supplier server, the front-end set of processor-executable instructions being configured to cause the at least one processor of the client device to implement an out-of-game response based on at least one of the reported in-game events.