Plug-in Architecture for Wagering Game Network Systems
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional wagering game systems rely on proprietary, monolithic software that limits flexibility and scalability, as they are typically built as a single unit on persistent storage devices, making it difficult to add new features or update components without rebuilding the entire system.
Innovation Solution
A plug-in architecture for wagering game networks that allows for dynamic loading of executable code, enabling third-party developers to create and integrate plug-ins for specific functions, such as user interface enhancements, RNG services, or protocol conversions, without modifying the core software, using a plug-in interface that registers functions and methods with the executable software unit.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If proprietary monolithic software is used, then system stability is improved, but adaptability deteriorates
Solution Approach 1:
The patent divides the monolithic software system into modular components: a core executable software unit and separate plug-in modules. The core unit provides stable foundational functions, while plug-ins provide adaptable specialized functions. This segmentation allows the core to remain stable while the system as a whole becomes adaptable through interchangeable plug-in modules.
Solution Approach 2:
The patent creates a universal plug-in architecture where a single core executable software unit can work with multiple different plug-in modules through standardized interfaces. This allows one core unit to serve multiple functions by loading different plug-ins, enhancing adaptability without compromising the stability of the core.
2Device complexity
If monolithic software structure is used, then system simplicity is improved, but device complexity deteriorates
Solution Approach 1:
The system is segmented into a simple core executable software unit and separate plug-in modules. The core remains simple and unchanged, while complexity is isolated to individual plug-ins that can be developed, tested, and deployed independently. This maintains overall system simplicity while enabling scalability.
Solution Approach 2:
The patent introduces a plug-in interface as an intermediary layer between the core executable software unit and the functional modules. This interface mediates interactions, allowing the core to remain simple while supporting complex plug-in functionalities through standardized communication protocols.
3Reliability
If entire system is rebuilt for new features, then reliability is improved, but productivity deteriorates
Solution Approach 1:
The patent segments the system into a stable core executable software unit and separate plug-in modules for new features. This allows new features to be developed, tested, and deployed as independent plug-ins without rebuilding the entire system, thereby maintaining reliability while significantly improving development productivity.
Solution Approach 2:
The patent establishes a predefined plug-in interface architecture in advance, with standardized methods and data structures. This preliminary action allows new plug-ins to be developed independently and integrated without requiring system-wide rebuilds, maintaining reliability while accelerating development through reusable interface patterns.
4Reliability
If proprietary software is used, then system stability is improved, but adaptability deteriorates
Solution Approach 1:
The patent segments the proprietary software into a stable core executable unit and separate plug-in modules. This allows the core proprietary functionality to remain stable and protected, while customization is achieved through interchangeable plug-ins that can be added, removed, or modified without affecting the core system stability.
Solution Approach 2:
The patent introduces a standardized plug-in interface as an intermediary between the proprietary core software and customization requirements. This interface layer allows proprietary software to maintain its stability while enabling adaptability through third-party and custom plug-ins that communicate through defined protocols.
Data Source
AI summary
A plug-in architecture for a wagering game network is described. Plug-in modules may provide various functions for services related to wagering games. Such functions may include random number generation, user interface functions, player tracking functions, central determinant functions etc. The plug-ins are dynamically loaded during the run-time of an application or service.