Office of Liquor and Gaming
Regulation
QCOM 3 Information Session
Novotel Sydney on Darling Harbour
11 August 2015
Presenter:
Robert Larkin
Principal Technical Officer
OLGR
Download this presentation at:
publications.qld.gov.au/dataset/qcom-3-interface-specification
Why QCOM 3 was developed
• Age
• Technology
Main Features
•
•
•
•
•
Encompass all QCOM v1.6 functionality
Ethernet and IP based protocols
Support for encryption
Support for multiple service providers
A wide range of possible modes of
operation and configuration
• Significantly more extensible and versatile
than its predecessor
Multiple Service Providers
•
•
•
•
•
•
•
•
General Auditing
Monitoring
Game Performance and Analysis
Player Loyalty Systems
Card Based Gaming
Ticket-In / Ticket-Out
Attendant Paging Systems
Jackpot Systems
QCOM 3 Interface Specification
QCOM 3 is not a network protocol
specification
QCOM 3 is fundamentally an
Application Programming Interface (API)
Interface Location QCOM v1
Interface Location QCOM 3
Overview
QCOM Users
QCOM 1 vs QCOM 3
Protocol vs QCOM 3
QCOM Authorities
• QCOM Master Authority (QMA)
• Script Approval Authority (SAA)
• Software Upgrade Authority (SUA)
QCOM Master Authority
• Persistent
• Full access to the QCOM API
• Installs at least the first QCOM user
(typically all of them)
• Can operate via proxy
• Configures the mode of operation of the
gaming machines
Differences between the anon user, the QMA and QCOM Users
QCOM v3.0.0. draft 3-Aug-2015
anon user
QMA
QCOM users
Very limited
Full Access
Varies
Jailed environment for script
execution
Yes
Yes
Yes
Event Hooking
No
No
Yes
QCI only
Signed scripts
exec'd by other
users
Event handlers
Yes
No
Yes
Always
Always
Created on
demand
(no loops, no recursion, reduced
set of libraries)
Yes
No
No
Can be quarrantined
No
No
Yes
QCOM API Privileges
Script Execution via
QCOM Command Interface
(QCI) login
Persistence
Crippled jail/environment
Mode of Operation (MO)
• What is a Mode of Operation?
• QCOM 3 can accommodate a wide range
of gaming machine MO’s
• In QCOM 3 the MO is dynamic
Example MO’s are shown on the following slides
MO – Stand Alone
MO – Single Service Provider
MO – Mutli Service Providers
MO –
rd
3
Party Lockout
MO – WAN Example
MO – QLD Clubs and Hotels
MO – QLD Clubs and Hotels
MO – QLD Casinos
QCOM 3 EGM Summary
Concerning Regulators
• The role of the regulator
– Define the Mode of Operation
• QMA
– Privileges
• Any special requirements or roles?
Concerning Service Providers
•
•
•
•
•
•
•
QCOM Users
QCOM API
Operating Procedures MR document
Implementing QCOM 3
Scripts
QSIM
Technical support
Concerning EGM manufacturers
•
•
•
•
QCOM 3 Software Development Kit (SDK)
QSIM & Implementation Testing
Technical support
Implementing QCOM 3
Current Status
•
•
•
•
QCOM 3 Interface Specification document
QSIM & SDK
QCOM API
Scripting language
– Which version of Lua?
– Co-routine support
Questions