Patent Application
20080153599
1. Technical Field
This invention pertains generally to management systems and methods. More particularly, the present invention relates to a computerized method and system for downloading gaming software and configuring gaming machines.
2. Description of Related Art
Various networked gaming systems have been developed over the years beginning at least in the 1980's. With acceptance and utilization, users such as casino operators have found it desirable to increase the computer management of their facilities and expand features available on networked gaming systems. For instance, there are various areas in the management of casinos that is very labor intensive, such as reconfiguring gaming machines, changing games on the gaming machines, and performing cash transactions for customers.
In one aspect of the invention, a computerized download and configuration server-based system and method for use with game devices, systems, and methods is provided to enable users to monitor, control, and modify game devices and other related activities.
At least one embodiment may be summarized as a method of game related reporting in a casino gaming network system including receiving at least one user input at a front end gaming reporting and control application program, the at least one user input indicative of a request for a report including an indication of at least one of a report type and a parameter to populate at least one field of the report type to produce the requested report; sending a report path indicative of a network address of the report and a set of credential information to a database server reporting service; receiving the requested report via the database server reporting service; and displaying the requested report by the front end gaming reporting and control application program. Sending a report path indicative of a network address of the report and a set of credential information to a database server reporting service may include sending the report path to an SQL server reporting service.
The method of game related reporting in a casino gaming network system may further include receiving at least one of a user identifier and a user password at the front end gaming reporting and control application program; and verifying at least the user password. Verifying at least the user password may be performed before the receiving the at least one user input indicative of the request for the report, and wherein the displaying the requested report by the front end gaming reporting and control application program is performed without any further user inputs indicative of either the user identifier or the user password.
Verifying at least the user password may further include determining which of a plurality of report types the user identifier has authority to access, wherein the displaying the requested report by the front end gaming reporting and control application program is only performed with the requested report where the user identifier has authority to access the requested report.
Verifying at least the user password may further include determining which of a plurality of reports the user identifier has authority to access; and displaying a plurality of indicia by the front end gaming reporting and control application program indicative of the reports that the user identifier has authority to access, without indicating any of the reports that the user identifier does not have authority to access. Displaying a plurality of indicia at the front end gaming reporting and control application program indicative of the reports that the user identifier has authority to access may include displaying the plurality of indicia indicative of the reports that the user identifier has authority to access by category of the reports.
Verifying at least the user password may further include determining which of a plurality of categories of reports the user identifier has authority to access; and displaying a plurality of indicia by the front end gaming reporting and control application program indicative of the categories of reports that the user identifier has authority to access without indicating any categories of reports that the user identifier does not have authority to access. Determining which of a plurality of reports the user identifier has authority to access may include determining which of the plurality of reports the user identifier has authority to access based on a user role logically associated with the user identifier. Determining which of the plurality of reports the user identifier has authority to access based on a user role logically associated with the user identifier may include retrieving information indicative of the user role from a directory. Retrieving information indicative of the user role from a directory may include retrieving information indicative of the user role from an Active directory.
The method of game related reporting in a casino gaming network system may further include determining which of a plurality of reports the user identifier has authority to access; and displaying a plurality of indicia by the front end gaming reporting and control application program indicative of the reports that the user identifier has authority to access, without indicating any of the reports that the user identifier does not have authority to access. Determining which of a plurality of reports the user identifier has authority to access may include determining which of the plurality of reports the user identifier has authority to access based on a user role logically associated with the user identifier. Determining which of the plurality of reports the user identifier has authority to access based on a user role logically associated with the user identifier may include retrieving information from an active directory.
The method of game related reporting in a casino gaming network system may further include determining which of a plurality of categories of reports the user identifier has authority to access; and displaying a plurality of indicia by the front end gaming reporting and control application program indicative of the categories of reports that the user identifier has authority to access without indicating any of the categories of repots that the user identifier does not have authority to access. Determining which of a plurality of categories of reports the user identifier has authority to access may include determining which of the plurality of reports the user identifier has authority to access based on a user role logically associated with the user identifier. Determining which of the plurality of categories of reports the user identifier has authority to access based on a user role logically associated with the user identifier may include retrieving information from an Active directory.
The method of game related reporting in a casino gaming network system may further include retrieving a network address of a database server reporting service; retrieving information that identifies all report categories and all reports available via the database server reporting service; retrieving a user role from a networked directory; determining which of the report categories and the reports that a user has authority to access; and displaying the report categories and the reports that the user has authority to access without displaying any of the report categories and the reports that the user does not have authority to access, without requiring the user to provide login information more than one time per user session.
At least one embodiment may be summarized as a computer-readable medium that stores instructions that cause an end user computer to provide game related reporting in a casino gaming network system by receiving at least one user input at a front end gaming reporting and control application program, the at least one user input indicative of a request for a report including an indication of at least one of a report type and a parameter to populate at least one field of the report type to produce the requested report; sending a report path indicative of a network address of the report and a set of credential information to a database server reporting service; receiving the requested report via the database server reporting service; and displaying the requested report by the front end gaming reporting and control application program. Sending a report path indicative of a network address of the report and a set of credential information to a database server reporting service may include sending the report path to an SQL server reporting service
The instructions may cause the end user computer to provide game related reporting in the casino gaming network system further by receiving at least one of a user identifier and a user password at the front end gaming reporting and control application program; and verifying at least the user password.
The instructions may cause the end user computer to provide game related reporting in the casino gaming network system further by determining which of a plurality of reports the user identifier has authority to access; and displaying a plurality of indicia by the front end gaming reporting and control application program indicative of the reports that the user identifier has authority to access, without indicating any of the reports that the user identifier does not have authority to access. Displaying a plurality of indicia at the front end gaming reporting and control application program indicative of the reports that the user identifier has authority to access may include displaying the plurality of indicia indicative of the reports that the user identifier has authority to access by category of the reports.
The instructions may cause the end user computer to provide game related reporting in the casino gaming network system, further by determining which of a plurality of categories of reports the user identifier has authority to access; and displaying a plurality of indicia by the front end gaming reporting and control application program indicative of the categories of reports that the user identifier has authority to access without indicating any categories of reports that the user identifier does not have authority to access. Determining which of a plurality of reports the user identifier has authority to access may include determining which of the plurality of reports the user identifier has authority to access based on a user role logically associated with the user identifier. Determining which of the plurality of reports the user identifier has authority to access based on a user role logically associated with the user identifier may include retrieving information indicative of the user role from a directory. Retrieving information indicative of the user role from a directory may include retrieving the information indicative of the user role from an Active directory.
At least one embodiment may be summarized as a computer-readable medium that stores instructions that cause an end user computer to provide game related reporting in a casino gaming network system by retrieving a network address of a database server reporting service; retrieving information that identifies all report categories and all reports available via the database server reporting service; retrieving a user role from a networked directory; determining which of the report categories and the reports that a user has authority to access; and displaying the report categories and the reports that the user has authority to access without displaying any of the report categories and the reports that the user does not have authority to access, without requiring the user to provide login information more than one time per user session. Retrieving information that identifies all report categories and all reports available via the database server reporting service may include retrieving information that identifies all report categories and all reports available via an SQL database server reporting service.
At least one embodiment may be summarized as an end-user computing system to provide game related reporting in a casino gaming network system including at least one user interface configure to receive user input device and to provide user output; a processor communicatively coupled to the user interface and operable to execute a number of instructions; a computer-readable medium communicatively coupled to the processor, the computer-readable medium stores instructions that cause the processor to retrieve a network address of a database server reporting service; retrieve information that identifies all report categories and all reports available via the database server reporting service; retrieve a user role from a networked directory; determine which of the report categories and the reports that a user has authority to access; and display the report categories and the reports that the user has authority to access via the user interface without displaying any of the report categories and the reports that the user does not have authority to access, without requiring the user to provide login information more than one time per user session. The processor may receive at least one user input from the user interface, the at least one user input indicative of a request for a report including an indication of at least one of a report type and a parameter to populate at least one field of the report type to produce the requested report. The computer-readable medium may store instructions that cause the processor to send a report path indicative of a network address of the report and a set of credential information to a database server reporting service; receive the requested report via the database server reporting service; and display the requested report via the user interface. The processor may send the report path indicative of a network address of the report and a set of credential information to an SQL server reporting service. The processor may receive at least one user input from the user interface, the at least one user input indicative of at least one of a user identifier and a user password, and the computer-readable medium may store instructions that cause the processor to verify at least the user password. The processor may determine which of the report categories and the reports that a user has authority to access based on a user role logically associated with the user identifier. The processor may retrieve information indicative of the user role from a directory. The processor may retrieve information indicative of the user role from an Active directory.
At least one embodiment may be summarized as a casino gaming network system including at least one end-user computing system executing front end gaming reporting and control application program; at least one database report server communicatively coupled to the end-user computing system by at least one network, the database report server providing at least one database reporting service; at least one directory communicatively coupled to the end-user computing system by at least one network, wherein the front end gaming reporting and control application program is configured to cause the at least one end-user computing system to receive at least one user input indicative of a request for a report including an indication of at least one of a report type and a parameter to populate at least one field of the report type to produce the requested report, send a report path indicative of a network address of the report and a set of credential information to the database reporting service of the database server, receive the requested report via the database reporting service of the database server, and display the requested report. The at least one end-user computing system may send a report path indicative of a network address of the report and a set of credential information to an SQL server reporting service. The at least one end-user computing system may receive at least one of a user identifier and a user password from an end-user via the front end gaming reporting and control application program and verifies at least the user password. The at least one end-user computing system may verify at least the user password before the at least one end-user computing system receives the at least one user input indicative of the request for the report, and the at least one end-user computing system displays the requested report without any further user inputs indicative of either the user identifier or the user password. The front end gaming reporting and control application program may be configured to cause the at least one end-user computing system to determine which of a plurality of reports the user identifier has authority to access; and display a plurality of indicia by the front end gaming reporting and control application program indicative of the reports that the user identifier has authority to access, without indicating any of the reports that the user identifier does not have authority to access. The front end gaming reporting and control application program may be configured to cause the at least one end-user computing system to display the plurality of indicia indicative of the reports that the user identifier has authority to access by report category. The front end gaming reporting and control application program may be configured to cause the at least one end-user computing system to: determine which of a plurality of categories of reports the user identifier has authority to access; and display a plurality of indicia by the front end gaming reporting and control application program indicative of the categories of reports that the user identifier has authority to access without indicating any categories of reports that the user identifier does not have authority to access. The front end gaming reporting and control application program may be configured to cause the at least one end-user computing system to determine which of the plurality of reports the user identifier has authority to access based on a user role logically associated with the user identifier. The front end gaming reporting and control application program may be configured to cause the at least one end-user computing system to retrieve information indicative of the user role from a directory. The front end gaming reporting and control application program may be configured to cause the at least one end-user computing system to retrieve information indicative of the user role from an Active directory.
At least one embodiment may be summarized as a casino gaming network system including at least one end-user computing system executing front end gaming reporting and control application program; at least one database report server communicatively coupled to the end-user computing system by at least one network, the database report server providing at least one database reporting service; and at least one directory communicatively coupled to the end-user computing system by at least one network, wherein the front end gaming reporting and control application program is configured to cause the at least one end-user computing system to retrieve a network address of the database server reporting service; retrieve information that identifies all report categories and all reports available via the database server reporting service, retrieve a user role from the at least one directory, determine which of the report categories and the reports that a user has authority to access; and indicate all of the report categories and all of the reports that the user has authority to access without indicating any of the report categories and any of the reports that the user does not have authority to access, without requiring the user to provide login information more than one time per user session. The front end gaming reporting and control application program may be configured to cause the at least one end-user computing system to retrieve information that identifies all report categories and all reports available via the database server reporting service by retrieving information that identifies all report categories and all reports available via an SQL database server reporting service.
Further aspects, features and advantages of various embodiments of the invention will be apparent from the following detailed disclosure, taken in conjunction with the accompanying sheets of drawings.
In the drawings, identical reference numbers identify similar elements or acts. The sizes and relative positions of elements in the drawings are not necessarily drawn to scale. For example, the shapes of various elements and angles are not drawn to scale, and some of these elements are arbitrarily enlarged and positioned to improve drawing legibility. Further, the particular shapes of the elements as drawn, are not intended to convey any information regarding the actual shape of the particular elements, and have been solely selected for ease of recognition in the drawings.
FIGS. 2A(1)-2A(3) are a context diagram of operation of a download configuration server system according to one illustrated embodiment.
FIGS. 2B(1) and 2B(2) are tiered layer diagram of a download and configuration system architecture, according to one illustrated embodiment.
FIGS. 2C(1) and 2C(2) are a block diagram showing various components of a download and configuration system architecture, according to one illustrated embodiment.
In the following description, certain specific details are set forth in order to provide a thorough understanding of various disclosed embodiments.
However, one skilled in the relevant art will recognize that embodiments may be practiced without one or more of these specific details, or with other methods, components, materials, etc. In other instances, well-known structures associated with computing systems, networks including servers, routers, bridges, firewalls, etc., and gaming device including electronic gaming machines have not been shown or described in detail to avoid unnecessarily obscuring descriptions of the embodiments.
Unless the context requires otherwise, throughout the specification and claims which follow, the word “comprise” and variations thereof, such as, “comprises” and “comprising” are to be construed in an open, inclusive sense, that is as “including, but not limited to.”
Reference throughout this specification to “one embodiment” or “an embodiment” means that a particular feature, structure or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, the appearances of the phrases “in one embodiment” or “in an embodiment” in various places throughout this specification are not necessarily all referring to the same embodiment. Further more, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.
As used in this specification and the appended claims, the singular forms “a,” “an,” and “the” include plural referents unless the content clearly dictates otherwise. It should also be noted that the term “or” is generally employed in its sense including “and/or” unless the content clearly dictates otherwise.
The headings and Abstract of the Disclosure provided herein are for convenience only and do not interpret the scope or meaning of the embodiments.
One conventional gaming machine management system is the Bally One System, which is designed to provide essential functionality for gaming facilities. The present example embodiment provides for a unified gaming machine management system that offers the full feature sets which are desirable for a Class III casino floor with a rich gaming environment and providing the flexibility to mix Class II and Class III machines on the same gaming floor. To accommodate this unification, many features and functions are needed to provide a robust functional capability. In the example embodiment, an architectural framework is provided that enables the addition of modules and functionality. Slot management system 101 may use standards based communications protocols, such as HTTP, XML, SOAP, SSL. Slot management system 101 may be a scaleable system, which may advantageously employ off-the-shelf components, such as conventional servers and storage devices. Slot management system 101 may utilize standard user interfaces for all system front ends, such as a display, keyboard, mouse, and conventional windows software. An example front-end may be a management terminal (server) 103 from which an operator can utilize a user interface to communicate with player account system server 105 and review and/or modify player information contained in a player database managed by player account system server 105. Slot management system 101 may use standardized authentication, authorization and/or verification protocols, which may be implemented and/or controlled by a server-to-server (S2S) server 107 which enables the secure communication of data and information between the respective servers within the slot management system 101. Third party interface 109 may further provide for the incorporation of third party servers and storage devices, such as IGT/Rocket server 111 and Gaming Database 113, using the standardized authentication, authorization and verification protocols. Slot management system 101 may support a wide range of promotional tools to enable various promotional and marketing programs which may be used in conjunction with casino market place server 115, such as Bally Gaming's CMP, or another system gaming subsystem. Slot management system 101 includes transaction server 117, for example a Bally iView transaction server which communicates with Bally iView apparatuses which are incorporated with gaming machines connected to the network, where iView apparatuses include a secondary display connected to a motherboard including a microprocessor or controller, memory, and selected communication, player, and/or gaming software, such as a conventional video wagering game or multi-media presentations which may be enabled by a player, the gaming machine, or the slot management system. It may be appreciated that transaction server 117 can be designed to drive and communicate with other network connected apparatuses having a display and user interface. In the contemplated embodiments, the networked apparatuses, such as the iView apparatuses, are incorporated with slot management system 101 to multi-task as both a presentation engine and a game management unit (GMU). To provide flexibility, slot management system 101 utilizes open standard GSA (Gaming Standards Association) protocols for ease of integrating various manufacturers devices and a windows-based system for ease of operators (users) in programming and obtaining data from, and adding data to the system.
FIGS. 2A(1)-2A(3) show operation of a download and configuration server system 201, according to one illustrated embodiment.
The download and configuration server system 201 includes control station 203, which may include a display and a user interface. The download and configuration server system 201 may also include a download and configuration services block 205 (including for example a download server or Web accessible service, a download handler server or Web accessible service, a configuration server or Web accessible service, an option configuration server or Web accessible service, a scheduler server or Web accessible service and a scheduler server or Web accessible service). The download and configuration server system 201 may further include a download and configuration database block 207, which may include, for example, conventional storage depositories such as a download database 227, a schedule database 229, and a configuration database 228. The download and configuration server system 201 may additionally include a network components block 209, for example, conventional hardware and software to support IIS 260, MSMQ, and DNS, a SQL report server, an active directory 245, a certificate server, a download library 234, and an SDDP (Software Download Distribution Point) 252. The download and configuration server system 201 may further include a Game-to-Server (G2S) host block 211, that may, for example, include a download handler 233, an executive service 220, an option configuration handler 232, a G2S engine 280, a delivery agent, and a G2S Web accessible service. The download and configuration server system 201 may even further include an electronic game machine (EGM) block 213, that may, for example, include a facility floor of network connected gaming machines and tables which may each include an iView or similar product features and/or a gaming management processor unit which are individually identifiable and addressable over the network. The referenced Web services may utilize a secure HTTPs transmission protocol used to communicate with the slot management service and vice-versa. The system 201 may operate using Web protocol and Web services to serve information and process transactions, in contrast to serving Web pages in the traditional sense.
Download and configuration server system 201 enables the transmission of software files, packages or modules to one or more clients, such as gaming machines or gaming tables, via, for example, a casino network using the Gaming Standard Association's (GSA's) Game to System (G2S) message protocols. The configuration portion of server system 201 enables the selecting of specific settings and options on one or more clients using GSA's G2S message protocols, such as to modify the Alpha operating system on conventionally available gaming machines or third party gaming machine or table operating systems. The respective subsystems of server system 201 communicatively couple to control station 203. The control station 203 includes a common user interface application, such as a control panel (e.g., Bally Control Panel 216 or BCP 216) software application, so that a user can request data and issue commands for the processing of download and configuration operations throughout the network.
Download and configuration server system 201 provides for the following G2S download class features: 1) the G2S download class provides a standardized protocol to manage the downloaded content on all G2S compliant gaming machines or tables (i.e., EGMs 213) from all G2S compliant host systems; 2) the G2S download class enables installation of downloaded packages; 3) the G2S download class enables the removal of software (uninstall); 4) the G2S download class enables scheduling of installation and/or removal of software including enabling scheduling options that relate to a specific time, EGM state, or interaction with a host server or technician; 5) the G2S message class supports reading an inventory of downloaded packages and installed modules, which provides the capability to effectively manage the content on the EGM 213; and 6) the G2S message class enables recording transaction logs for packages and scripts on a transaction database accessible through control station 203. This feature provides an audit capability or transaction tracer for determining how content came to be on an EGM 213.
Download and configuration server system also provides the following G2S option configuration (optionConfig) class features which allows for the selection of various configuration options: a) the optionConfig class provides a convenient and efficient mechanism to remotely configure EGMs 213 and b) the G2S optionConfig class provides for downloading options available from within an EGM 213.
Download and Configuration server system 201 implemented G2S classes (optionConfig, download, and scheduler) are also integratable through secondary displays, such as the Bally iView, by incorporating, for example an iView transaction server. Thus, download, configuration, and configuration options may be implemented at selected EGMs 213 through their respective Main Processor Unit (MPU) or through iViews. In the case of using the iViews for network communications, a separate processor board is provided along with a display and user interfaces. Communication channels are connectable between the iViews and the MPU to enable the download, configuration, and configuration option processes. Some definitions of terms and components follow:
Databases—The databases return information based on the results of a stored procedure call. For example, the following databases, which are descriptively named, may be utilized: Core; Configuration; Download; Activity; and Schedule.
Bally Control panel 216 (BCP)—As an example, the control panel application, such as a BCP 216, can be a smart client implemented on control station 203 encapsulating all the functionality to support the command and control portions of the download and configuration features of a facility or facilities. Downloads and configuration options can be remotely scheduled or deployed immediately by a user through control station 203. Notifications, approvals, searches, and reports produced through server system 201 can be viewed by a user through a display or by hardcopy provided by a printer connected to control station 203.
Control station 203 can be utilized for remote downloading and configuration of games and game operating systems of connected EGMs 213. Also, control station 203 can be utilized to download content to or to configure the iView (or similar components) and second game displays or monitors (for instance, in cases in which an EGM 213 has two or more major displays) (which may also include an additional processor unit such as for example in the case of multiple games operable on a single EGM 213 on separate displays), as well as peripheral software for components in the games like bill validators and ticket printers.
Control station 203 can be utilized for the throttling of system resources based on the requested changes. For example if the user requests several high bandwidth consuming jobs be initiated concurrently, the control station 203 would advise the user that this would utilize more than allocated bandwidth and require changes to the proposed schedule. It is also contemplated that the control station 203 could recommend changes to the schedule to ease the work requirement for the user.
Control station 203 can be utilized for the broad based change to gaming floors to support special events. For example on Halloween a specialized background or theme could be downloaded or configured on all capable games and devices for the duration of the event. This concept can be further extended to enabling specialized bonus games on other player centric activities relating to the special event or holiday. This allows a user of control station 203 to fully customize the property without the manual effort required with current systems and technologies.
Control station 203 can be utilized to fully view in a graphical fashion gaming floor configurations that have occurred in the past or are proposed for the future. This allows the user of control station 203 to easily and quickly compare past gaming floor configurations to configurations proposed for the future in an easy to understand graphical manner. It is contemplated that these configurations be animated in a manner that realistically depicts the activity on the gaming floor over a period of time allowing the user of control station 203 to visually assess the impact of the proposed changes.
Control station 203 can be utilized to view machine utilization information over time to determine where certain groups of players spend their time while at a property. For example if certain demographic groups are inclined to utilize gaming machines configured at $0.25 per play and this control station 203 capability can illustrate the fact that during certain times of the day this gaming machine configuration is completely utilized and that a large group of this demographic is scheduled to visit the property, the casino manager could opt to enable more of this type of game so players are not waiting for an opportunity to play. It is contemplated that this feature is presented in an animated fashion such that the user of control station 203 may select a date range and analyze in real time game usage by time of day and by player demographic. This feature also requires control station 203 have access to, and the capability of processing, information from the player marketing system or have access to a data stream feeding the player marketing system.
Control station 203 has the capability to allow groups of gaming machines to be identified and operated upon via a number of query options. This aids the user in quickly and effectively finding the gaming machines to apply changes. It is contemplated that advanced selection criteria such as performance over the last 30 days be considered as a query parameter. The control station 203 can provide the capability to utilize a graphical representation of the gaming floor. This allows selected groups of games to be graphically represented on a floor map as well as in a list form.
Control station 203 can utilize historical slot game performance data to provide guidance for new floor configuration options. The historical data may be accessed in the download system data stores or from an external business intelligence system. It is contemplated that the control station 203 may be programmed to allow for automated floor configuration changes based on the historical performance data. This capability may be applied automatically or via an interface requiring only approval from the user prior to applying the changes.
Database Web Services—These are World-Wide Web (Web) services that are conventionally available to be re-used by other user interfaces and service applications connected to slot management system 101. In other words, this is a secure closed system network using Web services connected on demand with the slot management system 101 (
Handlers—These are the logic libraries that are responsible for executing the business logic of the system.
Network Components—The following list of network components, or portions thereof, may be implemented and/or required by the download and configuration server system 201: Certificate Server; DNS; DHCP, Application Firewalls, Hardware Firewalls, Network Load Balancers.
Third Party Software Applications—the following list of 3rd party applications my be utilized or required by the server system 201: IIS 260, MSMQ, SQL Server, SQL Server Reporting Services, Active Directory 245, Microsoft Windows 2003 Server.
G2S Engine 280—This service will receive G2S messages directly from EGMs 213 and dispatch them to the respective subsystem of server system 201 based on the message component type.
EGMs 213—Electronic Gaming Machines, which may include gaming tables with processor and/or display components.
iView—For example, a conventional apparatus providing a player or employee user interface and display at EGMs 213 connected to the network including the player tracking server and enabling a player or employee to request and receive information, to receive award notifications, to transfer credits, and to conduct such activities through the apparatus as is enabled on slot management system 101. One usage of an iView-type apparatus may be to display marketing and player tracking information and various shows on the occurrence of an award or win by a player. Such apparatuses may also allow gaming, such as with server-based games or even independent games stored on their respective processor boards. Thus, separate games may be implemented through the iView-type device, apart from the main game of EGM 213 controlled by the MPU. In turn, the content of the iView may be separately modified as through downloads or configurations or configuration options.
Control station 203 is able to retrieve from the database and view all login attempts to the server both successful and failed. A user may be locked out of access to the control panel application at control station 203 after too many failed login attempts. The recorded transaction log may include the login ID, data, time of login and duration.
The Web services may support functionality between control station 203 and database block 207. The Web services may also support unsolicited messages between the G2S handlers and control station 203.
Server system 201 may maintain a record or transaction log of login attempts to the server both successful and failed. The log may include the login ID, data, time of login and duration. Server system 201 may also maintain a transaction record or log of all events and activity occurring on server system 201. The log may include a record of which login session in which the event occurred.
Server system 201 may also maintain a log of communication events with any EGM 213. Server system 201 may also maintain the status of each EGM 213 including: game history data; download status (available, requested, downloading, applied, rejected); package information (available for install, requested, being downloaded, downloaded, installed); hardware information; software module information; and/or error conditions.
The configuration and download server system 201 may dynamically build packages to be downloaded based on EGM 213 inventory and available updates, fixes and new data for EGMs 213. The configuration and download server system 201 may verify requests from EGM 213 including whether or not the EGM 213 is valid and is in a functional or operational state to make the request. All requests may be logged and contain the requesting EGM 213 identifier, time and date, specific request, and EGM 213 operational status. The configuration and download server system 201 may communicate with Software Distribution Point servers (SDDP) 252 to maintain a list of packages that are available for supported EGMs 213. The configuration and download server system 201 may supply the location of the SDDP 252 when instructing an EGM 213 to add a package. The configuration and download server system 201 may verify that all required hardware and software for a package to be sent to an EGM 213 exists before instructing EGM 213 to retrieve the package. The configuration and download server system 201 may support multiple EGMs 213 in multiple sites and/or facilities and EGMs 213 produced by multiple manufacturers. The configuration and download server system 201 may verify that a software package can be installed on a selected EGM 213 before instructing EGM 213 to add a package. Such verification may, for example, use information in the package header and information stored about selected of EGM 213. The configuration and download server system 201 may be able to track which packages are installed on any given EGM 213 and verify the data by requesting a selected EGM 213 to send package install information. The configuration and download server system 201 may report bad images and errors and log them when failed package installation information is received from an EGM 213. The configuration and download server system 201 and SDDP 252 may be used to control all network pacing, bandwidth, error recovery, and monitoring. The configuration and download server system 201 may be used to maintain the location of all SDDP 252 and the packages available on each.
Software Download Distribution Point (SDDP 252) server may be utilized to maintain all downloaded software packages in a secure library with the required number of secure backups defined by a jurisdiction. The SDDP server 252 may be used to restrict access to the library that stores all software download packages to only authorized personnel. The access may limit access, such as to only allow write access to those authorized to add, delete, and update packages and read access for all others authorized to access the library. The SDDP server 252 may provide secure software level firewalls to restrict access to everything saved on the server. The SDDP server 252 may maintain a log of login attempts to the server both successful and failed. The log may include the login ID of a user, data, time of login and duration. The SDDP server 252 may maintain a log of all events and activity occurring on server system 201. The log may include which login session in which an event occurred.
Software packages added to the software library may be verified from the package data using an MD5 or SHA1 hashing algorithm to validate the data or some other verification tool. The verification string may be added to a package header and used to re-verify the package when it is downloaded to the EGM 213.
All verification failures and related errors may be logged and the log entry may contain the date and time, the ID of the person running the process at the time, and the specific type of error that occurred. They may also be displayed on the correct display area.
The SDDP server 252 may be utilized to provide selected EGMs 213 with the communications port location and IP address used for sending software package data to the EGM 213. All data within a download package may be compressed using conventional compression techniques and transmitted in compressed format. On receipt, EGM 213 may decompress the downloaded software package.
FIGS. 2B(1) and 2B(2) shows a tiered layer architecture of a download and configuration system according to one illustrated embodiment.
A presentation layer 214 may include the control panel application 216. The control panel application 216 is loaded on control station 203 (FIGS. 2A(1)-2A(3)) which provides a user interface and display through which the download and configuration portion of the slot management system 101 (
A business logic layer 218 may include G2S Host 219, which may include G2S engine 280 components. G2S Host 219 may be used to send and receive G2S protocol messages to and from EGMs 213 and other configurable devices. G2S Host 219 may also be used for the packaging and unpackaging of the internal system messages and G2S protocol messages. The business logic layer 218 may also comprise of Download and Configuration logic libraries, Executive Service 220, and the Scheduler Service 221 which are responsible for implementing the Business Logic of the system.
A data access layer 222 may be comprised of Web Services 223, which may be used to enable methods and/or processes for interacting with a data layer 224. A network services layer 225 provides network services 226.
The data layer 224 may comprise various databases, for example a download database 227, configuration database 228, schedule database 229, activity database 230, and core database 231, as may be useful for storing download and configuration system data.
EGM layer 212 may comprise the EGMs 213 and other configurable components like iViews and game controllers.
FIGS. 2C(1) and 2C(2) show a componentization of a download and configuration system, according to one illustrated embodiment.
The presentation layer includes the control panel application 216. The control panel application 216 may be loaded on control station 203 which may include a user interface and display for user to manage the download and configuration server system 201.
The business logic layer includes Download Service and Logging. The Logging library may be used to store job logs and may include storing error and debug logs.
The scheduler 221 may implement the shared base classes for assignments and jobs, maintain the job queues, and/or provide execution contexts for host-originated activities. The scheduler 221 may also include upkeep (e.g., flush) of outdated job and job log entries.
G2S Host core 219 may provide the mechanisms to separate protocol specifics from application logic. G2S Host core may receive information from the application libraries (e.g., Configuration), and may be utilized to implement the interfaces that application and protocol components require to fulfill their needs.
An option configuration handler 232 may be utilized to implement the G2S class's specific to the Option Configuration context.
A download handler 233 may be utilized to implement the G2S class's specific to the download context.
A download library 234 may be part of the library of software packages available for download to EGM's 213.
The SDDP 252 may be comprised of a Website responsible for downloading software packages to EGMs 213.
The data access layer 222 may connect Web-based structure and services with the download database 227. The data access logic required for the download and configuration system 201 to interact with the download database 227 may be contained within the download Web service 236 (FIGS. 2B(1) and 2B(2)). The download Web service 236 may also provide structure and services for communicating download commands, such as between the BCP 216 and a download handler 237 via the executive component 220 (e.g., via an executive Web service 240).
A configuration Web service 238 (FIGS. 2B(1) and 2B(2)) may provide Web-based structure and services allowing the interaction with the configuration database 228. The data access logic required for the download and configuration system 201 to interact with the configuration database 228 may be contained within the configuration Web service 238. The configuration Web service 238 may also provide Web-based structure and service for communicating configuration commands, such as between the BCP 216 and a configuration handler 239 via the executive component 220 (e.g., via the executive Web service 240).
A scheduler Web service 241 (FIGS. 2B(1) and 2B(2)) may provide Web-based structure and services to consuming components to allow the interaction with the schedule database 229. The data access logic required for the configuration and download system 201 to interact with the schedule database 229 may be contained within the scheduler Web service 241.
A core Web service 242 may provide Web-based structure and services to consuming components to allow the interaction with the core database 231. The data access logic required for the system to interact with the core database 231 may be contained within the core Web service 242.
An activity Web service 243 may provide Web-based structure and services to consuming components to allow the interaction with the activity database 230. The data access logic required for the system to interact with the activity database 230 may be contained within the activity Web service 243.
A security Web service 244 may provide Web-based structure and services to consuming components to allow the interaction with active directory 245 for security purposes (e.g., authentication, verification, encryption, etc.). The security Web service 244 may be used as a Web based interface for retrieving and storing security data in the active directory 245 or other directories, databases or other security repositories.
At the Data layer 224, the configuration schema may implement the configuration database 228; download schema may implement the download database 227; activity schema may implement the logging database 230; core schema may implement the translator or core 231 database; and schedule schema may implement the schedule database 229.
Download and configuration server network 201 is a portion of slot management system 101 which provides a suite of subsystems designed to provide customizable solutions by allowing users to select products within the suite to meet their needs for particular facilities, such as a casino manager seeking to manage a single or multiple properties. Download and Configuration (Download and Config) are two of the subsystems offered in the suite that provides a user, such as the Slot Operations staff, an efficient mechanism to remotely configure electronic gaming machine (EGM) 213.
The Download and Config Software utilized together with the apparatuses as shown in the figures may be used to enable a casino Slot Operations staff to schedule and change a game(s) on the casino floor from a keyboard.
Using the Control Panel (BCP) interface 203, the staff may be able to schedule, configure, download and activate changes to games on the floor, without touching an EGM 213 on the floor. Download and Config software application may be loaded on control station 203 to enable the sending of information over the casino network using G2S & HTTPS standardized message protocols that manage the downloaded content. From control station 203, a user, such as casino staff, can change cabinet or game options, or games in EGMs 213. There are numerous selections that the staff can schedule to configure or make a minor change. Some examples of the types of software that may be downloaded or options which may be re-configured are:
In order to implement the download and configuration features, one approach is to install slot management system 101 at a facility, such as, for example, the Bally_Live slot management system 101. The implementation of the download and configuration features further contemplates the implementation of server hardware and related equipment as shown in the figures, and particularly FIGS. 2A(1)-2E, including software to perform the needed functions for communicating relevant data and instructions, the implementation of download ready EGMs 213, such as EGMs 213 with an Alpha operating system with remote download and configuration capability. An example system for implementing the download and configuration network 201 may be a Bally One System together with the Bally Live Floor program. Another example implementation of the Download and Configuration server network 201 may be in conjunction with other slot management systems incorporating the Bally Live Core program.
An example process for using the download and configuration server network 201 is as follows: A casino operator decides to change game themes on the Alpha V20D-20 EGMs 247. The software game themes are located on the SDDP Server 252. The Download management tools are located on the Application/Database Server System 251. One or more servers separate from the SDDP Server 252 contain the game theme software, such as for security or redundancy purposes. The Alpha EGMs 247 are identified on the casino floor using the BCP 216. A Download management tool, such as the BCP scheduler may be used through a menu to identify: the date and time to download the game packages; the game packages to send to the specific EGMs 213; the date and time to automatically activate the games on the EGMs 213 after the download. At the selected date and time, the EGM 213 may open communication with the Download Database 227. The EGM 213 request software from the SDDP server 252. The SDDP server 252 downloads the specified game information to the EGM 213 using a secure transmission protocol such as HTTPS. The download to the EGM 213 may occur in the background operation of the Alpha OS, so that game play is not interfered with. The EGM 213 may de-activate game operation a pre-determined amount of time subsequent to the last play on the EGM 213, such as five minutes, and issue a message on one of its display panels that it is temporarily offline, at which point the EGM 213 can initiate installation of the downloaded software. A record of the transmissions and corresponding activity of the EGM 213 is relayed to a retrievable storage on the network, such that a privileged user may operate the BCP 216 to run the reports identifying the old and new games, date changed, and by whom. User privileges may be restricted as discussed previously to provide additional levels of security and flexibility within the system and for the casino operator or users of slot management system 101 and download and configuration server network 201.
Example download and configuration components that are shown in
An SDDP server 252, which includes a download software library. The SDDP server 252 executes game server software, and the download software library stores download game software.
An application/database server 227 includes core databases, and provides core services as well as download services. The core databases may include a core database, a meter database and an activity database. The core services may include: communications, initiation and validation, certificate, IIS, MSMQ, DNS, DHCP, and active directory services. The core services may also include: meter services, activity services, cabinet services, and game play services. The download services may include certificate, IIS, MSMQ, DNS, DHCP, and active directory services. The download services may further include: a Web service, a configuration Web service, a scheduler Web service, a download handler Web service, an option configuration handler Web service and a scheduler service.
A panel control (BPC) 203.
A G2S may include certificate, IIS, MSMQ, DNS, DHCP, and active directory services. The G2S may also include a SQL Report, Web Service, and delivery agent.
Download and configuration databases may include: a download database, a configuration database and a scheduler database.
An adaptive security appliance (ASA) may create a firewall between back-end and floor systems. Such may provide proactive threat defense that stops attacks before they spread through the network, controls network activity and application traffic, and delivers flexible VPN connectivity.
The following devices and systems may be included within the described slot management network system and may have the referenced capabilities:
Manage Collection—A collection may be used by more than one assignment. The user can modify the membership of the collection:
Set Collections—Choose which EGMs 213, directly or via other collections that this assignment will affect.
Add or Remove Package—The user can pick from available packages and add them to the assignment for download. The modules included within packages are also displayed for reference.
Edit Download Schedule—The user can edit scheduling options for download.
User can schedule a start date for download using the BCP 216. It may be noted that the start date indicates the date the download process begins. It may take indeterminate amount of time for the downloaded package to be ready to be installed on a given EGM 213. This is the case where download occurs in a facility that is operating. If the facility is shutdown at a selected point in time or if it is not yet operational, download may occur as rapidly as the throughput pipelines and bandwidth of the servers and routers will allow on the system. Also, according to one embodiment, to avoid download conflict when multiple download assignments exist for the same module type on an EGM 213, the assignment with the latest creation date may take precedence.
Edit Install Schedule—The user can edit scheduling options to install packages.
Edit Assignment Attributes—The user can edit the name and description of an assignment. According to one embodiment, one of the most important attributes is active. Assignments can be created, edited, scheduled, and saved without having them take effect. For an assignment to be scheduled and affect the collection, it must be made active. The user may also de-activate an assignment.
Cancel Jobs—Informs the host system via the BCP 216 to abort an existing job. Any new commands for the JOB are not run. An attempt may be made to send cancel commands to the EGM 213 if appropriate.
The BCP 216 is a smart client application that may depend on the Dot Net 2.0 or similar framework. It may be deployed via the Systems Web site. Any software dependencies may be automatically downloaded with the application. The BCP 216 may run on Windows 2000 or newer OS machines. In one embodiment, as illustrated in
The following are exemplary windows of the BCP 216 application that may be available.
In an example embodiment, the BCP 216 interacts directly with the following Web-based services: Activity, User Authentication, Download, and Configuration.
In addition to the Web Services 223, the BCP 216 may require file system access for local debug/trace logging. It may have no direct Database access. It may be capable of printing but does not require a printer to perform its functions. The BCP 216 uses the tradition net processing model.
In an example implementation, communication with EGM devices may be exclusively via G2S messages, and there may not be a connection with BCP or other clients which create work requests. The Download handler 233 may be a .Net assembly. The assembly may be loaded by the G2S Engine 280 and may run in the context of this process (service).
The Download handler 233 may interact with the Data Tier 224, G2S Core, Activity (EGM events), and Microsoft Enterprise Library Logging components. In an example embodiment, there is no direct interaction to/from the end users. Job requests may be output to the database (Data Access Layer 222) and polled by the Download component.
The Data access layer 222 may store configuration and state information for the objects being managed by the download handler. Configuration files may be used to store all persistent data that is not stored in the Data tier 224. The distinction between storing a value in the configuration files instead of adding the element to the Data access layer 222 database and interface(s) can be arbitrary. For example, if there is a requirement to limit the maximum size for a package this value could be added to the Data access layer 222, or stored in a configuration file.
The configuration files may include, but are not limited to, values for:
1) settings required for testing; 2) limits and constraints; 3) constants.
The hierarchy for a value stored in a configuration data store may be:
i) File; ii) Section; and iii) Key/Value pairs.
Programmatic access to the configuration files may, for example, be with the Microsoft. Practices. EnterpriseLibrary.Configuration namespace classes. These classes allow a single application to use multiple configuration files, and for multiple applications to share common configuration files. The details of the data store implementation are hidden from the Download component.
In an example embodiment, the Download handler 233 does not receive work requests directly from the Control panel 216 (BCP) client or the scheduling component. These components add/modify job records in the database via the Data Access Tier. The Download Service may have a subcomponent that will poll the job data via the Data Access Tier and update job status
The interface between the Download Service and the Data tier 224 is a Web service. The required methods for polling and updating the job data may include: 1) GetJobList—A collection of all job requests. The method includes filtering parameters; 2) GetJob—Get a single job request; and 3) UpdateJob—Change the status of a job request.
The G2S Core may provide communication between the Download Service and the EGM 213 devices. Host commands may be sent from the Download Service to an EGM via the G2S Core Interface, and the G2S Core Interface may provide the response from the EGM 213. The G2S Core component(s) may provide persistent storage.
From G2S Message Protocol Download Class Draft v0.8 (hereby incorporated by reference), the requirements implicitly mandate that this interface provide the capability to send the following G2S host commands to an EGM:
Each of the above G2S host commands may need a response and the server system 201 may utilize handler(s) to process the EGM 213 response.
The Download Service may “register” to receive the following Events: a) G2S_DLX (download exceptions). There are approximately 25 DLX events to be handled, and b) G2S_DLE (download events). There are approximately 30 DLE events to be handled.
The events indicate a change in the state of processing an SMP (Service Management Platform) command by an EGM 213. The processing of these events will update the database via the Data Access Layer interface. The processing actions are specified in the sequence diagrams for the download class commands.
The Data tier 224 provides an API (Application Program Interface) between the Download Service component and the database for storing the configuration/state information of the objects being managed by slot management system 101, and the “job” information that is the primary input source for the Download Service. Because these two sets of data objects (i.e., config/state and job) may be loosely coupled, they may be implemented as separate classes.
All download class command responses from the EGMs 213 may result in a database operation through the Data access layer 222, excluding event class commands, which may be processed through the Activity Interface independently of the Download Service. The methods required may correlate directly with the EGM 213 command responses except as noted. The required methods for processing command responses from the EGM 213 may include:
The implementation of the Data access layer 222 interfaces may be a “synchronous” transaction, meaning that the success/failure of the database operation is included in the response.
In an example embodiment, some Business Rules include: a) an event record may be created for every request/response process with an EGM, via the Activity Web Service 243; b) package sizes may be limited to a configurable maximum size; and c) the OptionConfig handler may replicate the required EGM data from the Core database 231 to the Configuration database 228 in order to support reporting.
The Download handler 233 may consist of a single .Net assembly file. This assembly may be deployed to the disk location required by the G2S Engine 280.
Example Constraints may include: a) communication with EGM devices may be exclusively via G2S messages; and b) there may be no connection with BCP or other clients which create work requests.
The OptionConfig Service component may interact with the Data tier 224, G2S Core and the Activity (EGM events) components. The Data access layer 222 may store configuration and state information for the objects being managed by slot management system 101.
Configuration files may be used to store all persistent data that is not stored in the Data tier 224. The distinction between storing a value in the configuration files instead of adding the element to the Data Access Layer database and interface(s) can be arbitrary. For example, if there is a requirement to limit the maximum size for a package this value could be added to the Data Access Layer, or stored in a configuration file. The configuration files may include, but are not limited to, values for: 1) settings required for testing; 2) limits and constraints; and constants
Programmatic access to the configuration files may be with the .Net Framework 2.0 System, incorporated by reference herein. Configuration namespace classes and the Microsoft Practices, Enterprise, Library, Common Configuration classes, are all incorporated by reference herein. These classes allow a single application to use multiple configuration files, and for multiple applications to share common configuration files.
In an example embodiment, the Option Config handler does not receive work requests directly from the Control panel 216 (BCP) client or the scheduling component. These components add/modify job records in the database via the Data Access Tier. The Download Service may have a subcomponent that will poll the job data via the Data Access Tier and update job status.
The interface between the Option Config Service and the Data tier 224 may be a Web service. Methods for polling and updating the job data may include: a) GetJobList—A collection of all job requests. The method includes filtering parameters; b) GetJob—Get a single job request; and c) UpdateJob—Change the status of a job request.
The G2S Core may provide the communication between the Option Config Service and the EGM 213 devices. In which case, Host commands may be sent from the Option Config Service to an EGM via the G2S Core.
According to some embodiments, the Option Config Service may “register” to receive the following Events: a) G2S_DLX (download exceptions). For example, there may be 25 DLX events to be handled; and b) G2S_DLE (download events). For example, there may be 30 DLE events to be handled.
The events may indicate a change in the state of processing an SMP (Service Management Platform) command by an EGM. The processing of these events will update the database via data access layer 222 interface. The processing actions may be specified in the sequence diagrams for the download class commands.
The Data tier 224 provides an API (Application Program Interface) between the OptionConfig Service component and the database for storing the configuration/state information of the objects being managed by slot management system 101, and the “job” information that may be the primary input source for the Download Service. Because these two sets of data objects (config/state vs job) may be loosely coupled, they may be implemented as separate classes.
All Option Config class command responses from the EGMs 213 may result in a database operation through data access layer 222. The methods may correlate directly with the EGM 213 command responses except as otherwise noted. According to one embodiment, the methods for processing command responses from the EGM 213 may include:
Configuration assignments may be run in order by schedule type: Permanent, Permanent with start date, Re-occurring Override, One Time Override. Within a schedule type, the assignment with the earlier start date may be initiated first. Within matching start dates, assignments having static collections may be initiated before dynamic; if still tied, those assignments with earlier create dates may be initiated first. Configuration assignments of permanent and permanent with start date may include static collections.
Download Scheduling gets the start date that download process begins. It may take an indeterminate amount of time for the downloaded package to be ready to be installed on a given EGM. Also, to avoid download conflict, if multiple download assignments exist for the same module type on an EGM, the assignment with the latest creation date takes precedence.
The Scheduler may be reliant upon the Schedule database 229.
Exemplary Interactions may include: 1) scheduler listens to Schedule database 229; 2) scheduler interacts with Schedule Web service; 3) the Web Service may, for example, include a Windows Server version 2000 or 2003 (hereby incorporated by reference) with the following Windows components running: a).net Framework version 2.0 and/or b) Internet Information Server (IIS 260)
Processing—The Scheduler service 221 may query the Schedule database 229 for jobs that are scheduled to be run. The Scheduler may initiate the processing of the jobs by notifying the GUI Download Web Service 262 or the GUI Configuration Web Service 264.
Interface/Exports—The Scheduler service 221 may consume the Activity Web Service 243 to log its processing events. The Scheduler service 221 may also interact with the Schedule SQL database with ActiveX Data Objects (ADO) commands.
Classification—Web Service
Definition—The Web Service may expose Web Methods to consuming components to allow the interaction with the Download database 227.
The data access logic for the BCP 216 to interact with the Download database 227 may be included within the Download Web service 236.
The GUI Download Web Service 262 may be responsible for interacting with the Data tier 224 for those components that are consuming its exposed methods.
The BCP 216 may consume this Web Service and utilize its Web Methods to create and read necessary Download data in the database.
The GUI Download Web Service 262 may be used by the BCP 216 as a communication layer with the Download database 227.
Example Constraints may include: 1) consuming components may need to communicate via the Simple Object Access Protocol (SOAP) in order to consume the Web Service; 2) the Web Service may publish a Web Service Description Language (WSDL) to describe the Web service, the message format and protocol details; and 3) the Web Service may return its requested results in the form of a Serialized DataSet.
Example Interactions may include:
Processing—The GUI Download Web Service 262 may process requests made by consuming components. The requests may be made by the consuming component calling the GUI Download Web Service 262 exposed Web Methods. A successful request may be dependent upon the consuming component calling a Web Method by supplying the appropriate query parameters as dictated by the Web Service Description Language (WSDL) file. The Web Service processes the request by executing its embedded Business Logic while logging exceptions and events. The resulting output is returned to the consuming component.
The GUI Download Web Service 262 may consume the Activity Web Service 243 to log its processing events. It may also interact with the Download SQL database with ActiveX Data Objects (ADO) commands. Its capabilities may be exposed as Web Methods which are accessed via the Simple Object Access Protocol (SOAP).
Definition—This Web Service may expose Web Methods to consuming components to allow the interaction with the Configuration database 228. The data access logic used for the BCP 216 to interact with the Configuration database 228 may be arranged within the Configuration Web service 238.
The Configuration Web service 238 may be responsible for interacting with the Data tier 224 for those components that are consuming its exposed methods.
The BCP 216 may consume the Configuration Web service 238 and utilize its Web Methods to create and read necessary Option Configuration data in the database.
The Configuration Web service 238 may be advantageously used by the BCP 216 as communication layer with the Configuration database 228.
Example Constraints may include: 1) consuming components may communicate via the Simple Object Access Protocol (SOAP) in order to consume the Web Service; b) the Web Service may publish a Web Service Description Language (WSDL) to describe the Web service, the message format and protocol details; and c) the Web Service may return its requested results in the form of a Serialized DataSet.
Example Interactions may include:
The GUI Configuration Web Service may process requests made by consuming components. The requests may be made by the consuming component calling the GUI Configuration Web Services exposed Web Methods. A successful request may be dependent upon the consuming component calling a Web Method by supplying the appropriate query parameters as dictated by the Web Service Description Language (WSDL) file. The Web Service processes the request by executing its embedded Business Logic while logging exceptions and events. The resulting output is returned to the consuming component.
Example Interface/Exports may include:
Definition—According to one embodiment, the scheduler Web service 241 exposes Web Methods to consuming components to allow the interaction with the Scheduler database. The data access logic used for the Scheduler to interact with the Scheduler database may be included within the Scheduler Web service 241.
Exemplary Constraints may include: 1) consuming components may communicate via the Simple Object Access Protocol (SOAP) in order to consume the Web Service; 2) the Web Service may publish a Web Service Description Language (WSDL) to describe the Web service, the message format and protocol details; and 3) the Web Service may return its requested results in the form of a Serialized DataSet.
Example Uses/interactions may include:
Example Processing may include:
Example Interface/Exports may include:
Example Constraints may include: a) there may be no direct connection with the Presentation Layer (BCP) or EGM devices and/or b) inter-server communications may be secure. For example, a Secure Sockets Label (SSL) Web service is one approach to provide secure communications.
An example Composition may include:
Example Uses/Interactions May Include:
Example Configuration Interface May Include:
Data access layer 222 may store configuration and state information for the objects being managed by slot management system 101. Configuration files will be used to store all persistent data that is not stored in the Data tier 224. The configuration files may include, but are not limited to, values for: a) settings required for testing; b) limits and constraints; and c) constants.
Configuration data values that may be shared across multiple applications include: 1) executive host; 2) G2S host(s); 3) executive job interface Uri (referenced by Scheduler); 4) outbound G2S Host job queue (referenced by G2SHost) and/or 5) inbound G2S Host job status queue (referenced by G2SHost).
Programmatic access to the configuration files may be with the Microsoft.Practices.EnterpriseLibrary.Configuration namespace classes. These classes allow a single application to use multiple configuration files, and for multiple applications to share common configuration files. The details of the data store implementation are hidden from the Executive component.
The configuration for the Job Reader Interface may be in the system.runtime.remoting section of the application configuration file. The Scheduler may require the client configuration, and the Executive may use the service and channels configuration. The host name (or some form of identification) may be used for the client remoting configuration. If the Scheduler and Executive are not collocated on the same server and failover is required then a virtual IP address or host name in the client configuration may be used.
An example Job Creator may be incorporated as follows:
An example Assignment Dispatcher may be incorporated as follows:
An example EGM Assignment Web Service may be incorporated as follows:
An example Job Status Reader may be incorporated as follows:
An example EGM Job Status Delivery may be incorporated as follows:
An example Activity Interface may be incorporated as follows:
An example Data Access Layer Interfaces may be incorporated as follows:
Example Deployment Requirements may include the Executive being deployed in four separate components: 1) executive Windows Service, 2) executive IIS 260 Web services (2), 3) G2S Executive IIS 260 Web service; and 4) G2S Host.
Definition—This Web Service may expose Web Methods to consuming components to allow the interaction with the Download database 227. The data access logic required for the Download Handler to interact with the Download database 227 is contained within the Download Handler Web Service.
Example Constraints may include: a) consuming components may need to communicate via the Simple Object Access Protocol (SOAP) in order to consume the Web Service; b) the Web Service may publish a Web Service Description Language (WSDL) to describe the Web service, the message format and protocol details and/or c) the Web Service may return its requested results in the form of a Serialized DataSet.
Example Uses/Interactions may include:
Example Resources may include:
Example Processing may include:
Example Interface/Exports may include:
Definition—This component may expose Web Methods to consuming components to allow the interaction with the Configuration database 228. The data access logic required for the Configuration Handler 232 to interact with the Configuration database 228 is contained within the Configuration Handler Web Service 239.
Example Constraints may include: a) consuming components may communicate via the Simple Object Access Protocol (SOAP) in order to consume the Web Service and/or b) the Web Service may publish a Web Service Description Language (WSDL) to describe the Web service, the message format and protocol details.
The Web Service may return its requested results in the form of a Serialized DataSet.
Example Uses/Interactions may include:
Example Resources may include:
Example Processing may include:
Example Interface/Exports may include:
The SaveAssignment sequence may be created as part of detailed design and implementation. The SaveAssignment sequence may serve as a bridge between the Ul and the database, both of which have been specified in detail herein.
Other sequences in this section document the message flow between the host and an EGM. These have been implemented for all major use cases as this is an external integration point. While the G2S protocol documents may specify how these should work, they are often open to multiple interpretations. These sequences allow the iView and Alpha teams to compare their expectations with ours and give the whole team a chance to resolve differences earlier in the development cycle when it is cheaper.
An example Verify Package (described in
Example Package Management Sequence may include:
In one embodiment, the read only drives may be in the same machine which runs the Package Management GUI 274. Also, SDDP server 252 disks paths may be hard coded in Package Management GUI 274 (Console Application). Connections to databases may be through Download GUI Web Service 262.
An example Data View—Download
The download database 227 may encapsulate all the storage needed to support the download component of the system. It may hold the current inventory of all EGMs 213 as discovered via the G2S protocol (which is hereby incorporated) via the communications and download classes. It may store the assignments used to change that inventory via download class commands. It may store job state information for the jobs those assignments use to carry out downloads and installations. And it may store the inventory of the SDDP 252.
Download may be coupled directly or indirectly to the Schedule and Core databases 231. It leverages schedule to store assignment schedules for download and install and to queue pending jobs. It references core to replicate basic EGM information and to manage EGM collections. As with at least some components, activity history may be posted to the activity database 230 through Web Services 223 and may be stored locally in a limited fashion.
G2S may use the concept of scripts to install downloads and specify the approvals and other conditions that must be met for an install to occur. In the Download Database 227 the Script table with it related command tables may be linked to an assignment. When a script is sent to an individual EGM to be used, the script data from these tables maybe used as a template to create the ScriptStatus and related Command Status tables. The ScriptStatusID may be used as the script ID in the setScript command. Status for this script may be tracked within these Script Status tables and the rows may be used for that instance of the script.
An example JobQueue
Hold jobs that are waiting to be run. Scheduler may poll this table and kick off jobs when the start time has passed. If the schedule a job is tied to is recurring, then once the current instance succeeds, the scheduler may create a new row in this table for the next occurrence of the job using the same parameter data as the current job.
An example Schedule
May Hold schedule records used by any parts of the system that stores a schedule. In one embodiment, simple schedule types with a start date may be supported. In another embodiment, recurring tasks may also be supported.
An example ScheduleType
May Hold schedule records used by any parts of the system that stores a schedule. In one embodiment, simple schedule types with a start date may be supported. In another embodiment, recurring tasks may also be supported.
An example Assignment
An example AssignmentJob
An example AssignmentPackage
An example CoreEGM
An example EGMJob
An example EgmPackage
An example Package
An example ScheduleSchedule
An example Configuration may include:
An example Schedule database 229 may include:
An example Schedule Database Dictionary may include:
An example Schedule that may Hold schedule records used by any parts of the system that stores a schedule. In one embodiment, simple schedule types with a start date may be supported. In another embodiment, recurring tasks may also be supported.
An example ScheduleType may Hold schedule records used by any parts of the system that stores a schedule. In one embodiment, simple schedule types with a start date may be supported. In another embodiment, recurring tasks may also be supported.
Example User Interfaces—Control panel 216
Control panel—login to control panel. A user can change the password through a login password menu.
A Download Assignment Wizard may be included to pop-up and provide users with helpful tips or ask if the user needs assistance and then direct a user to a menu of information, similar to the Microsoft Windows Wizard. This feature can be disabled by a user, either by closing the Wizard display or selecting disablement from an options menu.
Similar to the Download Assignment Wizard, a Configuration Assignment Wizard may be included to assist users.
At 5702, a front end gaming reporting and control application program executing on an end user computing system receives at least one of a user identifier and a user password. At 5704, the front end gaming reporting and control application program verifies at least the user password.
At 5706, the front end gaming reporting and control application program determines which of a plurality of reports the user identifier has authority to access. At 5708, the front end gaming reporting and control application program determines which of a plurality of categories of reports the user identifier has authority to access.
At 5710, the front end gaming reporting and control application program displays a plurality of indicia by the front end gaming reporting and control application program indicative of the reports that the user identifier has authority to access, without indicating any of the reports that the user identifier does not have authority to access. At 5712, the front end gaming reporting and control application program displays a plurality of indicia by the front end gaming reporting and control application program indicative of the categories of reports that the user identifier has authority to access without indicating any categories of reports that the user identifier does not have authority to access.
At 5714, the front end gaming reporting and control application program receives at least one user input indicative of a request for a report including an indication of at least one of a report type and a parameter to populate at least one field of the report type to produce the requested report
At 5716, the front end gaming reporting and control application program sends a report path indicative of a network address of the report and a set of credential information to a database server reporting service.
At 5718, the front end gaming reporting and control application program receives the requested report via the database server reporting service. At 5720, the front end gaming reporting and control application program displays the requested report by the front end gaming reporting and control application program. The front end gaming reporting and control application program my display to report via a display device of an end user computing system, which in some embodiments may take the from of a mobile computing system such as a laptop computer, personal digital assistance or other mobile communications device.
The method 5700 verifies the user password before the at least one user input indicative of the request for the report is received. The method 5700 may also advantageously display the requested report without any further user inputs indicative of either the user identifier or the user password.
At 5802, a front end gaming reporting and control application program sends the report path indicative of a network address of the report and the credential information to a SQL server reporting service.
In particular at 5902, in displaying the reports that the user identifier has access to, the front end gaming reporting and control application program may display the report by report category. Such may make it easier for an end user to find and select a desired report.
At 6002, the front end gaming reporting and control application program may determine which of the plurality of reports the user identifier has authority to access based on a user role logically associated with the user identifier.
At 6102, the front end gaming reporting and control application program may retrieve information indicative of the user role from a directory.
At 6202, the front end gaming reporting and control application program may retrieve information indicative of the user role from an Active directory.
At 6302, the front end gaming reporting and control application program executing on an end-user computing system retrieves a network address of a database server reporting service.
At 6304, the front end gaming reporting and control application program retrieves information that identifies all report categories and all reports available via the database server reporting service. The front end gaming reporting and control application program may employ a web service, for example a database reporting service of a database report server, for example as previously described.
At 6306, the front end gaming reporting and control application program retrieves a user role from a networked directory.
At 6308, the front end gaming reporting and control application program determines which of the report categories and the reports that a user has authority to access.
At 6310, the front end gaming reporting and control application program displays the report categories and the reports that the user has authority to access without displaying any of the report categories and the reports that the user does not have authority to access.
At 6312, the front end gaming reporting and control application program receives a user input indicative of a request for a particular report.
At 6314, the front end gaming reporting and control application program retrieves the requested report using database reporting services.
At 6316, the front end gaming reporting and control application program displays the requested report to the end user via one or more display devices or the end-user computing system. Such advantageously is performed without requiring the user to provide login information more than one time per user session.
Example Reports software configuration and download project reports, may provide real-time and historical data. An example embodiment provides for Download and Configuration reports to be run on an inter/intranet browser, such as on SSRS. Windows authentication may be used for security. In other embodiments, the reports may also or alternatively be run from the BCP. The download reports may include reports in the Reports Detail Section. In addition, reports from the Floor System may be imported into the Download and Configuration project in order for the Download and Configuration applications to run independently of the floor system. One or more of the databases from the Floor System may be included as well.
An example Detailed Reports Design may include reports which are generated through and/or based upon the Software Download FRD 2.8 (which is hereby incorporated by reference) and the G2S specifications.
Example User Reports may include:
An example Package Assignment by EGM—Summary may include:
An example Package Assignment by EGM—Detail may include:
Example Module Assignment by EGM—Summary may include:
Input Parameters: [Start Date] to [EndDate] range for Assignment Approved Date
Logo: Tech Logo
Title: Module Assignment by EGM—Summary
Columns
Detail: Module ID, Package ID, Assignment ID, Component ID, Created Date, Created By, Approved Date, Approved By, Total packages assigned, Total EGMs
Group By: Site, EGM Group (Collection)
Sort By: Module ID, Package ID
Sub-Total field: n/a
Sub:Total Columns: n/a
Group Total field: Site Name
Group Total Columns: Total packages assigned, Total EGMs
Grand Total? Yes
Grand Total Columns: Total packages assigned, Total EGMs
An example Module Assignment by EGM—Detail may include:
Input Parameters: [Start Date] to [EndDate] range for Assignment Approved Date
Sub-Total field: EGM Group
Sub:Total Columns: Total packages assigned, Total EGMs
Group Total field: Site Name
Group Total Columns: Total packages assigned, Total EGM Groups, Total EGMs
Grand Total Columns: Total packages assigned, Total EGM Groups, Total EGMs
Input Parameters Start Date to End Date range for Assignment Approved Date
Sub-Total field: EGM Group
Sub:Total Columns: Total modules assigned
Group Total field: Site Name
Group Total Columns: Total modules assigned
Grand Total Columns: Total modules assigned,
Input Parameters Start Date to End Date range for Assignment Approved Date
Sub-Total field: N/A
Group Total field: Site Name
Group Total Columns: Total modules assigned
Grand Total Columns: Total modules assigned,
Input Parameters Start Date to End Date range for Job Submit Date
Sub-Total field: n/a
Group Total field: Site Name
Group Total Columns: Total assignments
Grand Total Columns: Total packages assigned
Input Parameters: [Start Date] to [EndDate] range for Job Submit Date
Sub-Total field: n/a
Group Total field: Site Name
Group Total Columns: Total assignments
Grand Total Columns: Total packages assigned
Input Parameters: [Start Date] to [EndDate] range for Job Submit Date
Sort By: Job ID, Submit Date, event, event date
Sub-Total field: n/a
Group Total field: Site Name
7) Failed EGM Job and/or
EGM Device Inventory Report
This report may be written for the Floor System project and may be imported from that project.
EGM Event
This report may be written for the Floor System project and may be imported from that project.
EGM Meter
This report may be written for the Floor System project and may be imported from that project.
EGM Daily Financial (audited data)
This report may be written for the Floor System project and may be imported from that project.
EGM Listing
This report may be written for the Floor System project and may be imported from that project.
EGM Media
This report may be written for the Floor System project and may be imported from that project.
EGM Game Theme
This report may be written for the Floor System project and may be imported from that project.
Input Parameters: [Start Date] to [EndDate] range for Group Create Date
1st header line: EGM ID, Manufacturer ID, Install Date,—Game Combinations—
2nd header line Game Theme, PayTable, Denomination
Sub-Total field: n/a
Group Total field: n/a
The above description of illustrated embodiments, including what is described in the Abstract, is not intended to be exhaustive or to limit the embodiments to the precise forms disclosed. Although specific embodiments of and examples are described herein for illustrative purposes, various equivalent modifications can be made without departing from the spirit and scope of the disclosure, as will be recognized by those skilled in the relevant art. For instance, the foregoing detailed description has set forth various embodiments of the devices and/or processes via the use of block diagrams, schematics, and examples. Insofar as such block diagrams, schematics, and examples contain one or more functions and/or operations, it will be understood by those skilled in the art that each function and/or operation within such block diagrams, flowcharts, or examples can be implemented, individually and/or collectively, by a wide range of hardware, software, firmware, or virtually any combination thereof. In one embodiment, the present subject matter may be implemented via Application Specific Integrated Circuits (ASICs). However, those skilled in the art will recognize that the embodiments disclosed herein, in whole or in part, can be equivalently implemented in standard integrated circuits, as one or more computer programs running on one or more computers (e.g., as one or more programs running on one or more computer systems), as one or more programs running on one or more controllers (e.g., microcontrollers) as one or more programs running on one or more processors (e.g., microprocessors), as firmware, or as virtually any combination thereof, and that designing the circuitry and/or writing the code for the software and or firmware would be well within the skill of one of ordinary skill in the art in light of this disclosure. It will also be appreciated that many of the methods or processes may omit some acts, include additional acts, and/or may perform the acts in a different order than described herein, so long as the desired end result or functionality is achieved.
In addition, those skilled in the art will appreciate that the mechanisms of taught herein are capable of being distributed as a program product in a variety of forms, and that an illustrative embodiment applies equally regardless of the particular type of signal bearing media used to actually carry out the distribution. Examples of signal bearing media include, but are not limited to, the following: recordable type media such as floppy disks, hard disk drives, CD ROMs, digital tape, and computer memory; and transmission type media such as digital and analog communication links using TDM or IP based communication links (e.g., packet links).
The various embodiments described above can be combined to provide further embodiments. To the extent that they are not inconsistent with the specific teachings and definitions herein, all of the U.S. patents, U.S. patent application publications, U.S. patent applications, foreign patents, foreign patent applications and non-patent publications referred to in this specification and/or listed in the Application Data Sheet, including but not limited to U.S. patent publication No. 2007/0082737A1; U.S. patent publication No. 2007/0006329A1; U.S. patent publication No. 2007/0054740A1; U.S. patent publication No. 2007/01111791; U.S. provisional patent application Ser. No. 60/865,345, filed Nov. 10, 2006, entitled “COMPUTERIZED GAME MANAGEMENT SYSTEM AND METHOD”; U.S. provisional patent application Ser. No. 60/865,575, filed Nov. 13, 2006, entitled “COMPUTERIZED GAME MANAGEMENT SYSTEM AND METHOD”; U.S. provisional patent application Ser. No. 60/865,332, filed Nov. 10, 2006, entitled “DOWNLOAD AND CONFIGURATION SERVER-BASED SYSTEM AND METHOD”; U.S. provisional patent application Ser. No. 60/865,550, filed Nov. 13, 2006, entitled “DOWNLOAD AND CONFIGURATION SERVER-BASED SYSTEM AND METHOD”; U.S. nonprovisional patent application Ser. No. ______, filed Nov. 9, 2007, entitled “GAMING SYSTEM DOWNLOAD NETWORK ARCHITECTURE” (Atty. Docket. No. 110184.454); U.S. nonprovisional patent application Ser. No. ______, filed Nov. 9, 2007, entitled “GAMING SYSTEM CONFIGURATION CHANGE REPORTING” (Atty. Docket. No. 110184.45401); U.S. nonprovisional patent application Ser. No. ______, filed Nov. 9, 2007, entitled “SECURE COMMUNICATIONS IN GAMING SYSTEM” (Atty. Docket. No. 110184.45403); U.S. nonprovisional patent application Ser. No. ______, filed Nov. 9, 2007, entitled “METHODS AND SYSTEMS FOR CONTROLLING ACCESS TO RESOURCES IN A GAMING NETWORK” (Atty. Docket. No. 110184.45404); U.S. nonprovisional patent application Ser. No. ______, filed Nov. 9, 2007, entitled “NETWORKED GAMING ENVIRONMENT EMPLOYING DIFFERENT CLASSES OF GAMING MACHINES” (Atty. Docket. No. 110184.453); U.S. nonprovisional patent application Ser. No. ______, filed Nov. 9, 2007, entitled “DOWNLOAD AND CONFIGURATION SERVER-BASED SYSTEM AND METHOD WITH STRUCTURED DATA” (Atty. Docket. No. 110184.449); U.S. nonprovisional patent application Ser. No. ______, filed Nov. 9, 2007, entitled “PACKAGE MANAGER SERVCE IN GAMING SYSTEM” (Atty. Docket. No. 110184.455); U.S. patent application Ser. No. 11/278,937, filed Apr. 6, 2006, entitled “LOGIC INTERFACE ENGINE SYSTEM AND METHOD”; U.S. Provisional Patent Application Ser. No. 60/676,429, filed Apr. 28, 2005, entitled “LOGIC INTERFACE ENGINE SYSTEM AND METHOD”; U.S. patent application Ser. No. 11/470,606, filed Sep. 6, 2006 entitled “SYSTEM GAMING”; U.S. Provisional Patent Application Ser. No. 60/714,754, filed Sep. 7, 2005, entitled “SYSTEM GAMING APPARATUS AND METHOD”; U.S. patent application Ser. No. ______ (Atty. Docket No. ______), filed Nov. 9, 2007 entitled “DOWNLOAD AND CONFIGURATION SERVER-BASED SYSTEM AND METHOD”; U.S. Provisional Patent Application No. 60/865,332, filed Nov. 10, 2006, entitled “DOWNLOAD AND CONFIGURATION SERVER-BASED SYSTEM AND METHOD”; and U.S. Provisional Patent Application No. 60/865,396, filed Nov. 10, 2006, entitled “DOWNLOAD AND CONFIGURATION CAPABLE GAMING MACHINE OPERATING SYSTEM, GAMING MACHINE, AND METHOD” are incorporated herein by reference, in their entirety. Aspects of the embodiments can be modified, if necessary, to employ systems, circuits and concepts of the various patents, applications and publications to provide yet further embodiments.
These and other changes can be made to the embodiments in light of the above-detailed description. In general, in the following claims, the terms used should not be construed to limit the claims to the specific embodiments disclosed in the specification and the claims, but should be construed to include all possible embodiments along with the full scope of equivalents to which such claims are entitled. Accordingly, the claims are not limited by the disclosure.
This application claims benefit under 35 U.S.C. 119(e) to U.S. provisional patent application Ser. No. 60/865,332, filed Nov. 10, 2006; and U.S. provisional patent application Ser. No. 60/865,550, filed Nov. 13, 2006.
| Number | Date | Country | |
|---|---|---|---|
| 60865332 | Nov 2006 | US | |
| 60865550 | Nov 2006 | US |
