G2S v1.1 Host Certification Requirements – Release 2
1 Overview
The G2S v1.1 Host Certification Requirements Checklist, on the following pages, is used to identify
the Functional Groups to be certified for host systems that implement the GSA G2S Message
Protocol v1.1, its errata, and its extensions.
The checklist identifies the Functional Groups in which a product may be certified. Operational and
jurisdictional requirements will determine which Functional Groups must be certified. Each
Functional Group corresponds to a specific set of commands and/or functionality defined within the
GSA G2S Message Protocol v1.1 specification or a GSA-approved extension. When a Functional
Group corresponds to a specific set of commands, the commands are listed with the Functional
Groups.
In some cases, an extension may affect commands within an existing Functional Group. For
example, an extension might add new attributes to a command in an existing Functional Group. In
such cases, the affected commands are only listed with the existing Functional Group – the affected
commands are not listed with the extension. When the extension is to be certified, any commands
in existing Functional Groups, which are also to be certified, are required to meet the requirements
of the existing Functional Groups as well as the extension.
1.1
Eligible Versions
The following versions of the GSA G2S Message Protocol v1.1 specification and GSA-approved
extensions are eligible for certification. From time-to-time, as new versions, extensions, and errata
are released, this list may be updated and a new version of these Certification Requirements may
be released.

GSA G2S Message Protocol v1.1

GSA G2S Message Protocol Extension 1a2

GSA G2S Message Protocol Extension 1c

GSA G2S Message Protocol Extension 1d

GSA G2S Message Protocol Extension 1e

GSA G2S Message Protocol Extension 1f

GSA G2S Message Protocol Extension 1g1

GSA G2S Message Protocol Extension 1h

GSA G2S Message Protocol Extension 1i
2012/03/19
©2012 Gaming Standards Association
Page 1 of 19
G2S v1.1 Host Certification Requirements – Release 2

GSA G2S Message Protocol Extension 1j

GSA G2S Message Protocol Extension 1k
1.2
Technical Bulletins
From time-to-time, Technical Bulletins regarding the G2S Message Protocol may be issued by the
Gaming Standards Association (GSA). The Technical Bulletins contain critical information regarding
corrections, clarifications, and certification requirements for the G2S Message Protocol. Information
contained in the Technical Bulletins may have a direct impact on the requirements of the G2S
Message Protocol v1.1, its errata, and its extensions. Information contained in the Technical
Bulletins may also have a direct impact on and the requirements for GSA certification of
implementations of the G2S Message Protocol v1.1, its errata, and its extensions. It is strongly
recommended that implementers of the G2S Message Protocol review the Technical Bulletins on a
regular basis for corrections and clarifications that may affect their implementations. The Technical
Bulletins are available in the download area of the GSA website www.gamingstandards.com.
1.3
Transport Requirements
The GSA G2S Message Protocol v1.1 specification does not specify the transport required to
communicate G2S messages. However, to be certified, implementations of the GSA G2S Message
Protocol v1.1 MUST use a GSA-approved transport. A list of those transports may be found on the
GSA website at www.gamingstandards.com.
1.4
Certification Requirements
To be certified, implementations of the GSA G2S Message Protocol v1.1, its extensions, and its
errata MUST meet the requirements of the version of the protocol under test and the requirements
identified in this document. Released versions of the GSA G2S Message Protocol v1.1, its
extensions, and its errata can be found on the GSA website at www.gamingstandards.com.
Implementations of the GSA G2S Message Protocol v1.1, its extensions, and its errata MUST
adhere to the following requirements to be GSA certified. From time-to-time, as new versions,
extensions, and errata are released, these requirements may be updated and a new version of
these Certification Requirements may be released.

The manufacturer of the implementation MUST comply with all requirements of the GSA
Certification Program Guide. This document can be found on the GSA website at
www.gamingstandards.com.

All messages generated by an implementation MUST comply with the message-handling
requirements of the GSA G2S Message Protocol under test. Within the GSA G2S Message
Protocol specification and its errata, requirements are identified by the terms MUST, MUST
NOT, and REQUIRED. Some requirements may not be specifically tested by the testing
agency.

All messages generated by the implementation MUST be well-formed, syntactically correct,
and semantically correct.
2012/03/19
©2012 Gaming Standards Association
Page 2 of 19
G2S v1.1 Host Certification Requirements – Release 2

All messages generated by the implementation MUST contain all required elements and
attributes.

All messages generated by the implementation MUST contain all optional elements and
attributes necessary to construct a semantically correct message. Optional elements and
attributes MAY be omitted provided that the default values associated with the elements
and attributes convey the proper semantic meaning to the recipient of the message.

The implementation MUST be certified for a minimum required set of Functional Groups. In
the G2S v1.1 Host Certification Requirements Checklist, the required Functional Groups are
pre-checked. The implementation MAY be certified for other Functional Groups.

To be certified for a Functional Group, the implementation MUST comply with all
requirements for the Functional Group. Within the GSA G2S Message Protocol specification,
its extensions, and its errata, requirements are identified by the terms MUST, MUST NOT,
and REQUIRED. Some requirements may not be specifically tested by the testing agency.

To be certified for a Functional Group, the implementation MUST generate all host-initiated
requests and notifications within the Functional Group. However, when a major Functional
Group is sub-divided into minor Functional Groups,
o
Within the major Functional Group that is to be certified, if the implementation
generates any host-initiated requests or notifications within a minor Functional
Group, the minor Functional Group MUST be certified.
o
Within the major Functional Group that is to be certified, if a minor Functional
Group is to be certified, all host-initiated requests and notifications within the minor
Functional Group MUST be generated.
o
Within the major Functional Group that is to be certified, if a minor Functional
Group is not to be certified, all host-initiated requests and notifications within the
minor Functional Group MUST NOT be generated.
o
Within the major Functional Group that is to be certified, at least one minor
Functional Group MUST be certified.

To be certified for a Functional Group, for each EGM-initiated request within the Functional
Group, the implementation MUST generate a semantically correct response to the request
or generate a response that contains a semantically correct error code.

To be certified for a Functional Group, the implementation MUST meet the requirements for
the Functional Group as well as the requirements for any GSA-approved extensions to the
Functional Group that are also to be certified.

To be certified, the implementation MUST NOT create excessive traffic because of an error
generated by an EGM. Instead, the implementation MUST be able to continue to
interoperate with the EGM, perhaps with reduced functionality.

To be certified, when the implementation supports an optional feature, the implementation
MUST NOT create excessive traffic because an EGM does not support the feature. The
implementation MUST be able to interoperate with the EGM, except for the unsupported
feature.
2012/03/19
©2012 Gaming Standards Association
Page 3 of 19
G2S v1.1 Host Certification Requirements – Release 2

To be certified, when the implementation does not support an optional feature, the
implementation MUST be able to interoperate with an EGM that does support the feature,
perhaps with reduced functionality.

To be certified, the implementation MUST accept all syntactically and semantically correct
eventReport requests and notifications, properly acknowledging all eventReport requests.
1.5
Certification Record Requirements
For an implementation to be certified, the testing laboratory MUST provide a written Certification
Record for the implementation to the Certification Authority. The Certification Record MUST include
the complete results of the conformance testing performed on the implementation.
1.6

The Certification Record MUST identify all Functional Groups supported by the
implementation regardless of whether a specific Functional Group was actually tested.

For each Functional Group identified on the Certification Record, the Certification Record
MUST indicate whether the Functional Group conformed to the requirements for the
Functional Group, whether the Functional Group did not conform to the requirements for
the Functional Group, or whether the Functional Group was not tested.

The implementation MAY contain functionality that is not part of any Functional Group. For
example, the implementation might contain a private extension. If any such functionality is
present in the implementation, the Certification Record, at a minimum, MUST indicate that
other functionality was present in the implementation. Further details of the functionality
MAY be withheld from the Certification Record. The Certification Record MUST NOT include
any indication of whether the functionality was tested or whether the functionality
conformed to a set of requirements.
Errors and Ambiguities
If an error or ambiguity is discovered during certification testing, the Certification Authority should
use the following guidelines to resolve the issue.

Errors and ambiguities should be resolved in a manner that is consistent with subsequent
released versions of the GSA G2S Message Protocol or, in the absence of a released version,
with clarifications or corrections that have been approved by the GSA G2S Technical
Committee for inclusion in a future version of the GSA G2S Message Protocol.

Errors and ambiguities should be resolved in a manner that will do the most to promote
interoperability.
2012/03/19
©2012 Gaming Standards Association
Page 4 of 19
G2S v1.1 Host Certification Requirements – Release 2
1.7
Deprecated Functionality
Functionality within released versions of the G2S Message Protocol specification, its extensions, and
its errata may be identified as deprecated. This indicates that the GSA no longer recommends that
the functionality be implemented. Implementations SHOULD NOT include deprecated functionality.
However, to maintain backwards compatibility, implementations MAY include deprecated
functionality.
Functionality may also be identified as deprecated in subsequent released versions of the G2S
Message Protocol specification, its extensions, and its errata. Implementations MAY omit any such
deprecated functionality. However, before doing so, manufacturers SHOULD verify that the
functionality is not needed for interoperability with other end-points.
2012/03/19
©2012 Gaming Standards Association
Page 5 of 19
G2S v1.1 Host Certification Requirements – Release 2
2 G2S v1.1 Host Certification Requirements Checklist
2.1
How to Use Checklist
The checklist is organized by class and major Functional Group. Major Functional Groups are
identified in bold and have large left-aligned checkboxes. Major Functional Groups may be subdivided into one or more minor Functional Groups. Minor Functional Groups are indented and have
small right-aligned checkboxes.
Classes may include a “Core” Functional Group as well as other major Functional Groups. “Core”
Functional Groups always appear as the first major Functional Group within a class. Other major
Functional Groups may follow the “Core” Functional Group.
When a “Core” Functional Group exists for a class, if another major Functional Group is to be
certified, the “Core” Functional Group MUST also be certified. Certification of the other major
Functional Group is dependent on certification of the “Core” Functional Group. The “Core”
Functional Group MUST be selected for certification when the other major Functional Group is
selected for certification. If the “Core” Functional Group is not selected for certification, the other
major Functional Group cannot be certified.
Many major Functional Groups are sub-divided into minor Functional Groups. For a minor
Functional Group to be certified, the major Functional Group MUST also be certified. Certification of
the minor Functional Group is dependent on certification of the major Functional Group. The major
Functional Group MUST be selected for certification when the minor Functional Group is selected for
certification. If the major Functional Group is not selected for certification, the minor Functional
Group cannot be certified.
In a few cases, certification of one Functional Group may be dependent on certification of another
Functional Group. Any such dependencies are noted in the checklist for the affected Functional
Groups. In such cases, for the affected Functional Group to be certified, the Functional Group on
which it is dependent MUST also be certified.
To indicate that an implementation is to be certified for a major Functional group:

Simply indicate whether the implementation acts as an owner or guest for the major
Functional Group by checking the appropriate large left-aligned box for the major Functional
Group. Guest certification may not be available for all major Functional Groups.
To indicate that an implementation is to be certified for a minor Functional Group:

First, indicate whether the implementation acts as an owner or guest of the major
Functional Group that contains the minor Functional Group by checking the appropriate
large left-aligned box for the major Functional Group.

Second, select the minor Functional Group by checking the appropriate small right-aligned
box for the minor Functional Group. If the implementation is to be certified as an owner for
the major Functional Group, the owner box MUST be checked. If the implementation is to
be certified as a guest for the major Functional Group, the guest box MUST be checked.
The role selected for the minor Functional Group MUST be the same as the role selected for
the major Functional Group. Guest certification may not be available for all minor
Functional Groups.
When a Functional Group is required for certification, the appropriate boxes associated with the
required Functional Group are pre-checked. However, not all pre-checked Functional Groups are
required for certification. In some cases, a minor Functional Group may only be required for
certification if its major Functional Group is to be certified. In such cases, the boxes associated with
the minor Functional Group are pre-checked, but the boxes associated with its major Functional
2012/03/19
©2012 Gaming Standards Association
Page 6 of 19
G2S v1.1 Host Certification Requirements – Release 2
Group are not pre-checked. The minor Functional Group is only required for certification if the
implementation is to be certified for the major Functional group – that is, the appropriate box for
the major Functional Group is checked by the manufacturer.
2.1.1
Checklist Examples
The examples below demonstrate how the certification checklist should be used.
2.1.1.1
Example 1 – Owner Certification
The implementation requests that owner support for Major Functional Group A and Minor Functional
Group 1 be certified. Note that all Functional Groups are available for Guest and Owner certification.
The implementation must not generate any requests or notifications from Minor Functional Group 2.
Guest
Owner
Class / Functional Group
Requests / Notifications
Responses
Minor Functional Group 1
requestA
responseA
Minor Functional Group 2
requestB
responseB
Major Functional Group A
2.1.1.2
Example 2 – Guest Certification
The implementation requests that guest support for the Major Functional Group B, Minor Functional
Group 3, and Minor Functional Group 4 be certified. Note that Minor Functional Group 5 is not
available for Guest certification.
Guest
Owner
Class / Functional Group
Requests / Notifications
Responses
Minor Functional Group 3
requestC
responseC
Minor Functional Group 4
requestD
responseD
Minor Functional Group 5
requestE
responseE
Major Functional Group B
2.1.1.3
Example 3 – Core Certification
The implementation requests that owner support for Core Functional Group C, Minor Functional
Group 6, and Major Functional Group D be certified. Note that Major Functional Group D is not
available for Guest certification. Major Functional Group C can only be selected for certification if
Core Functional Group C is also selected for certification. The implementation must not generate
any requests or notifications from Minor Functional Group 7.
Guest
Owner
Class / Functional Group
Requests / Notifications
Responses
Minor Functional Group 6
requestF
responseF
Minor Functional Group 7
requestG
responseG
Core Functional Group C
Major Functional Group D
2012/03/19
©2012 Gaming Standards Association
Page 7 of 19
G2S v1.1 Host Certification Requirements – Release 2
2.2
Certification Checklist
2.2.1
communications Class
Guest
Owner
Class / Functional Group
Requests / Notifications
Responses
setCommsState
setCommsState
commsStatus
getCommsStatus
getCommsStatus
commsStatus
getCommsProfile
getCommsProfile
commsProfile
getDescriptor
getDescriptor
descriptorList
setKeepAlive
setKeepAlive
setKeepAliveAck
keepAlive
keepAlive
keepAliveAck
commsOnLine
commsOnLineAck
commsDisabled
commsDisabledAck
commsClosing
commsClosingAck
keepAlive
keepAliveAck
joinMcast
joinMcast
joinMcastAck
leaveMcast
leaveMcast
leaveMcastAck
getMcastList
getMcastList
mcastList
mcastKeyUpdate
mcastKeyUpdate
mcastKeyAck
getMcastKeyUpdate
mcastKeyUpdate
Requests / Notifications
Responses
setCabinetState
setCabinetState
cabinetStatus
getCabinetStatus
getCabinetStatus
cabinetStatus
getCabinetProfile
getCabinetProfile
cabinetProfile
setCabinetLockOut
setCabinetLockOut
cabinetStatus
setDateTime
setDateTime
cabinetDateTime
getDateTime
getDateTime
cabinetDateTime
resetProcessor
resetStarted
setOperatingHours
setOperatingHours
operatingHoursList
getOperatingHours
getOperatingHours
operatingHoursList
Core Communications Functionality
EGM-Initiated Communications
Multicast Message Support
EGM-Initiated Multicast
2.2.2
Guest
cabinet Class
Owner
Class / Functional Group
Core Cabinet Functionality
Remote Restart Support
resetProcessor
Operating Hours Support
(Extension 1d)
Master Reset Support (Extension 1e)
2012/03/19
©2012 Gaming Standards Association
Page 8 of 19
G2S v1.1 Host Certification Requirements – Release 2
Guest
Owner
Class / Functional Group
Requests / Notifications
Responses
masterReset
masterReset
masterResetStatus
authorizeMasterReset
authorizeMasterReset
masterResetStatus
cancelMasterReset
cancelMasterReset
masterResetStatus
getMasterResetStatus
getMasterResetStatus
masterResetStatus
masterResetStatus
masterResetStatusAck
Requests / Notifications
Responses
setEventHandlerState
setEventHandlerState
eventHandlerStatus
getEventHandlerStatus
getEventHandlerStatus
eventHandlerStatus
getEventHandlerProfile
getEventHandlerProfile
eventHandlerProfile
getSupportedEvents
getSupportedEvents
supportedEvents
setEventSub
setEventSub
setEventSubAck
getEventSub
getEventSub
eventSubList
clearEventSub
clearEventSub
clearEventSubAck
getEventHandlerLogStatus
getEventHandlerLogStatus
eventHandlerLogStatus
getEventHandlerLog
getEventHandlerLog
eventHandlerLogList
eventReport
eventAck
Requests / Notifications
Responses
getMeterInfo
getMeterInfo
meterInfo
setMeterSub
setMeterSub
meterSubList
clearMeterSub
meterSubList
getMeterSub
meterSubList
meterInfo
meterInfoAck
EGM-Initiated Master Reset
2.2.3
Guest
eventHandler Class
Owner
Class / Functional Group
Core Event Reporting Functionality
EGM-Initiated Events
2.2.4
Guest
meters Class
Owner
Class / Functional Group
Core Meter Reporting Functionality
clearMeterSub
1
getMeterSub
EGM-Initiated Meters
1
This requirement can also be satisfied if the subscription is cleared using an empty setMeterSub command.
2.2.5
Guest
gamePlay Class
Owner
Class / Functional Group
Requests / Notifications
Responses
setGamePlayState
setGamePlayState
gamePlayStatus
getGamePlayStatus
getGamePlayStatus
gamePlayStatus
Core Game Play Functionality
2012/03/19
©2012 Gaming Standards Association
Page 9 of 19
G2S v1.1 Host Certification Requirements – Release 2
Guest
Owner
Class / Functional Group
Requests / Notifications
Responses
getGamePlayProfile
getGamePlayProfile
gamePlayProfile
setActiveDenoms
setActiveDenoms
gameDenomList
getGameDenoms
getGameDenoms
gameDenomList
getRecallLogStatus
getRecallLogStatus
recallLogStatus
getRecallLog
getRecallLog
recallLogList
getOutcomeLogStatus
getOutcomeLogStatus
outcomeLogStatus
getOutcomeLog
getOutcomeLog
outcomeLogList
Requests / Notifications
Responses
enterCommConfigMode
enterCommConfigMode
commConfigModeStatus
getCommConfigModeStatus
getCommConfigModeStatus
commConfigModeStatus
getCommConfigProfile
getCommConfigProfile
commConfigProfile
getCommHostList
getCommHostList
commHostList
setCommChange
setCommChange
commChangeStatus
authorizeCommChange
authorizeCommChange
commChangeStatus
cancelCommChange
cancelCommChange
commChangeStatus
getCommChangeLogStatus
getCommChangeLogStatus
commChangeLogStatus
getCommChangeLog
getCommChangeLog
commChangeLogList
commHostList
commHostListAck
commChangeStatus
commChangeStatusAck
Requests / Notifications
Responses
enterOptionConfigMode
enterOptionConfigMode
optionConfigModeStatus
getOptionConfigModeStatus
getOptionConfigModeStatus
optionConfigModeStatus
getOptionConfigProfile
getOptionConfigProfile
optionConfigProfile
getOptionList
getOptionList
optionList
setOptionChange
setOptionChange
optionChangeStatus
authorizeOptionChange
authorizeOptionChange
optionChangeStatus
cancelOptionChange
cancelOptionChange
optiobChangeStatus
Configure Accessible Games &
Denominations (Extension 1i)
Game Outcome Support (Extension
1k)
2.2.6
Guest
commConfig Class
Owner
Class / Functional Group
Core Communications Configuration
Functionality
EGM-Initiated Comms Configuration
2.2.7
Guest
optionConfig Class
Owner
Class / Functional Group
Core Option Configuration
Functionality
2012/03/19
©2012 Gaming Standards Association
Page 10 of 19
G2S v1.1 Host Certification Requirements – Release 2
Guest
Owner
Class / Functional Group
Requests / Notifications
Responses
getOptionChangeLogStatus
getOptionChangeLogStatus
optionChangeLogStatus
getOptionChangeLog
getOptionChangeLog
optionChangeLogList
optionList
optionListAck
optionChangeStatus
optionChangeStatusAck
Requests / Notifications
Responses
setDownloadState
setDownloadState
downloadStatus
getDownloadStatus
getDownloadStatus
downloadStatus
getDownloadProfile
getDownloadProfile
downloadProfile
deletePackage
deletePackage
packageStatus
addPackage
addPackage
packageStatus
getPackageStatus
getPackageStatus
packageStatus
readPackageContents
readPackageContents
packageContents
getPackageList
getPackageList
packageList
getPackageLogStatus
getPackageLogStatus
packageLogStatus
getPackageLog
getPackageLog
packageLogList
setScript
setScript
scriptStatus
getScriptStatus
getScriptStatus
scriptStatus
authorizeScript
authorizeScript
scriptStatus
cancelScript
cancelScript
scriptStatus
getScriptList
getScriptList
scriptList
getScriptLogStatus
getScriptLogStatus
scriptLogStatus
getScriptLog
getScriptLog
scriptLogList
getModuleList
getModuleList
moduleList
packageStatus
packageStatusAck
scriptStatus
scriptStatusAck
createPackage
createPackage
packageStatus
uploadPackage
uploadPackage
packageStatus
abortPackageTransfer
abortPackageTransfer
packageStatus
Pause / Resume Transfer
pausePackageTransfer
packageStatus
resumePackageTransfer
packageStatus
EGM-Initiated Option Configuration
2.2.8
Guest
download Class
Owner
Class / Functional Group
Core Software Download Functionality
EGM-Initiated Download
Software Upload Functionality
Pause / Resume / Abort Support
(Extension 1h)
2012/03/19
©2012 Gaming Standards Association
Page 11 of 19
G2S v1.1 Host Certification Requirements – Release 2
2.2.9
Guest
handpay Class
Owner
Class / Functional Group
Requests / Notifications
Responses
setHandpayState
setHandpayState
handpayStatus
getHandpayStatus
getHandpayStatus
handpayStatus
getHandpayProfile
getHandpayProfile
handpayProfile
getHandpayLogStatus
getHandpayLogStatus
handpayLogStatus
getHandpayLog
getHandpayLog
handpayLogList
setRemoteKeyOff
setRemoteKeyOff
remoteKeyOffAck
handpayRequest
handpayAck
keyedOff
keyedOffAck
Requests / Notifications
Responses
setCoinAcceptorState
setCoinAcceptorState
coinAcceptorStatus
getCoinAcceptorStatus
getCoinAcceptorStatus
coinAcceptorStatus
getCoinAcceptorProfile
getCoinAcceptorProfile
coinAcceptorProfile
Requests / Notifications
Responses
setNoteAcceptorState
setNoteAcceptorState
noteAcceptorStatus
getNoteAcceptorStatus
getNoteAcceptorStatus
noteAcceptorStatus
getNoteAcceptorProfile
getNoteAcceptorProfile
noteAcceptorProfile
getNotesAcceptedStatus
getNotesAcceptedStatus
notesAcceptedStatus
getNotesAccepted
getNotesAccepted
notesAcceptedList
Requests / Notifications
Responses
setHopperState
setHopperState
hopperStatus
getHopperStatus
getHopperStatus
hopperStatus
getHopperProfile
getHopperProfile
hopperProfile
Core Handpay Functionality
EGM-Initiated Handpay
2.2.10 coinAcceptor Class
Guest
Owner
Class / Functional Group
Core Coin Acceptor Functionality
2.2.11 noteAcceptor Class
Guest
Owner
Class / Functional Group
Core Note Acceptor Functionality
2.2.12 hopper Class
Guest
Owner
Class / Functional Group
Core Hopper Functionality
2012/03/19
©2012 Gaming Standards Association
Page 12 of 19
G2S v1.1 Host Certification Requirements – Release 2
2.2.13 noteDispenser Class
Guest
Owner
Class / Functional Group
Requests / Notifications
Responses
setNoteDispenserState
setNoteDispenserState
noteDispenserStatus
getNoteDispenserStatus
setNoteDispenserState
noteDispenserStatus
getNoteDispenserProfile
getNoteDispenserProfile
noteDispenserProfile
getNotesDispensedStatus
getNotesDispensedStatus
notesDispensedStatus
getNotesDispensed
getNotesDispensed
notesDispensedList
Requests / Notifications
Responses
setPrinterState
setPrinterState
printerStatus
getPrinterStatus
getPrinterStatus
printerStatus
getPrinterProfile
getPrinterProfile
printerProfile
getPrinterTemplates
getPrinterTemplates
printerTemplateList
getPrintLogStatus
getPrintLogStatus
printLogStatus
getPrintLog
getPrintLog
printLogList
printTicket
printComplete
Requests / Notifications
Responses
setProgressiveState
setProgressiveState
progressiveStatus
getProgressiveStatus
getProgressiveStatus
progressiveStatus
getProgressiveProfile
getProgressiveProfile
progressiveProfile
setProgressiveLockOut
setProgressiveLockOut
progressiveStatus
setProgressiveValue – Point-to-Point
setProgressiveValue
progressiveValueAck
setProgressiveValue – Multicast1
setProgressiveValue
getProgressiveLogStatus
getProgressiveLogStatus
progressiveLogStatus
getProgressiveLog
getProgressiveLog
progressiveLogList
progressiveHit
setProgressiveWin
progressiveCommit
progressiveCommitAck
getProgressiveHostInfo
progressiveHostInfo
Core Note Dispenser Functionality
2.2.14 printer Class
Guest
Owner
Class / Functional Group
Core Printer Functionality
Host-Initiated Printing Support
printTicket
Restrict Printing to Specific Players
(Extension 1a igtPrn)
2.2.15 progressive Class
Guest
Owner
Class / Functional Group
Core Progressive Functionality
EGM-Initiated Progressive
EGM Discovery of Host Progressive
Configuration
EGM-Initiated Host Progressive
Configuration
2012/03/19
©2012 Gaming Standards Association
Page 13 of 19
G2S v1.1 Host Certification Requirements – Release 2
1
The joinMcast, leaveMcast, and mcastKeyUpdate Functional Groups within the communications class are also required.
2.2.16 idReader Class
Guest
Owner
Class / Functional Group
Requests / Notifications
Responses
setIdReaderState
setIdReaderState
idReaderState
getIdReaderStatus
getIdReaderStatus
idReaderStatus
getIdReaderProfile
getIdReaderProfile
idReaderProfile
setIdValidation
idReaderStatus
getIdValidation
setIdValidation
Requests / Notifications
Responses
setBonusState
setBonusState
bonusStatus
getBonusStatus
getBonusStatus
bonusStatus
getBonusProfile
getBonusProfile
bonusProfile
setBonusLockOut
setBonusLockOut
bonusStatus
setGameDelay
setGameDelay
bonusStatus
bonusActivity – Point-to-Point
bonusActivity
bonusStatus
bonusActivity – Multicast1
bonusActivity
setBonusAward – Point-to-Point
setBonusAward
setBonusAward – Multicast1
setBonusAward
cancelBonusAward
cancelBonusAward
cancelBonusAwardAck
setBonusMessage – Point-to-Point
setBonusMessage
bonusMessageAck
setBonusMessage – Multicast1
setBonusMessage
getBonusLogStatus
getBonusLogStatus
bonusLogStatus
getBonusLog
getBonusLog
bonusLogList
commitBonus
commitBonusAck
Core ID Reader Functionality
Host-Controlled ID Reader
Host-Initiated ID Reader
EGM-Controlled ID Reader
EGM-Initiated ID Reader
2.2.17 bonus Class
Guest
Owner
Class / Functional Group
Core Bonus Functionality
bonusAwardAck
EGM-Initiated Bonus
Bonus Award Limits (Extension 1a
igtBonus)2
Wager Match Bonus Support
(Extension 1a igtWM)2
Multiple Jackpot Time Bonus Support
(Extension 1a igtMJT)2
1
The joinMcast, leaveMcast, and mcastKeyUpdate Functional Groups within the communications class are also required.
2012/03/19
©2012 Gaming Standards Association
Page 14 of 19
G2S v1.1 Host Certification Requirements – Release 2
2
Minimum Display Requirements Extension is also required.
2.2.18 player Class
Guest
Owner
Class / Functional Group
Requests / Notifications
Responses
setPlayerState
setPlayerState
playerStatus
getPlayerStatus
getPlayerStatus
playerStatus
getPlayerProfile
getPlayerProfile
playerProfile
setCountdownOverride – Point-toPoint
setCountdownOverride
playerStatus
setCountdownOverride – Multicast1
setCountdownOverride
setCarryOver
setCarryOver
carryOverAck
setPointBalance
setPointBalance
playerStatus
setPlayerOverride
setPlayerOverride
playerStatus
setHostPoints
setHostPoints
hostPointsAck
setPlayerMessage – Point-to-Point
setPlayerMessage
playerMessageAck
setPlayerMessage – Multicast1
setPlayerMessage
getPlayerLogStatus
getPlayerLogStatus
playerLogStatus
getPlayerLog
getPlayerLog
playerLogList
playerSessionStart
playerSessionStartAck
playerSessionEnd
playerSessionEndAck
getCountdownOverride
setCountdownOverride
Core Player Tracking Functionality
EGM-Initiated Player
Display Limit Support (Extension 1a
igtPlayer-limits)2
Wager Match Player Support
(Extension 1a igtWMP)2
1
The joinMcast, leaveMcast, and mcastKeyUpdate Functional Groups within the communications class are also required.
2
Minimum Display Requirements Extension is also required.
2.2.19 voucher Class
Guest
Owner
Class / Functional Group
Requests / Notifications
Responses
setVoucherState
setVoucherState
voucherStatus
getVoucherStatus
getVoucherStatus
voucherStatus
getVoucherProfile
getVoucherProfile
voucherProfile
setVoucherLockout
setVoucherLockOut
voucherStatus
getVoucherLogStatus
getVoucherLogStatus
voucherLogStatus
getVoucherLog
getVoucherLog
voucherLogList
Core Voucher Functionality
Issue Voucher Support
EGM-Initiated Issue Voucher
2012/03/19
©2012 Gaming Standards Association
Page 15 of 19
G2S v1.1 Host Certification Requirements – Release 2
Guest
Owner
Class / Functional Group
Requests / Notifications
Responses
getValidationData
validationData
issueVoucher
issueVoucherAck
redeemVoucher
authorizeVoucher
commitVoucher
commitVoucherAck
Requests / Notifications
Responses
setWatState
setWatState
watStatus
getWatStatus
getWatStatus
watStatus
getWatProfile
getWatProfile
watProfile
setWatLockOut
setWatLockOut
watStatus
setWatCashOut
setWatCashOut
watStatus
initiateRequest
initiateRequest
requestPending
cancelRequest
cancelRequest
cancelRequestAck
getWatLogStatus
getWatLogStatus
watLogStatus
getWatLog
getWatLog
watLogList
initiateTransfer
authorizeTransfer
commitTransfer
commitTransferAck
getWatAccounts
watAccountList
getWatBalance
watBalance
getKeyPair
keyPair
Requests / Notifications
Responses
getGatProfile
getGatProfile
gatProfile
getComponentList
getComponentList
componentList
doVerification
doVerification
verificationStatus
getVerificationStatus
getVerificationStatus
verificationStatus
getSpecialFunctions
getSpecialFunctions
specialFunctions
runSpecialFunction
runSpecialFunction
specialFunctionResult
getGatLogStatus
getGatLogStatus
gatLogStatus
Redeem Voucher Support
EGM-Initiated Redeem Voucher
2.2.20 wat Class
Guest
Owner
Class / Functional Group
Core Wagering Account Functionality
EGM-Initiated WAT
EGM-Controlled WAT User Interface
EGM-Initiated WAT User Interface
2.2.21 gat Class
Guest
Owner
Class / Functional Group
Core Game Authentication
Functionality
2012/03/19
©2012 Gaming Standards Association
Page 16 of 19
G2S v1.1 Host Certification Requirements – Release 2
Guest
Owner
Class / Functional Group
Requests / Notifications
Responses
getGatLog
gatLogList
verificationResult
verificationResultAck
Requests / Notifications
Responses
setCentralState
setCentralState
centralState
getCentralStatus
getCentralStatus
centralStatus
getCentralProfile
getCentralProfile
centralProfile
getCentralLogStatus
getCentralLogStatus
centralLogStatus
getCentralLog
getCentralLog
centralLogList
getCentralOutcome
centralOutcome
commitOutcome
commitOutcomeAck
Requests / Notifications
Responses
setMediaDisplayState
setMediaDisplayState
mediaDisplayStatus
getMediaDisplayStatus
getMediaDisplayStatus
mediaDisplayStatus
getMediaDisplayProfile
getMediaDisplayProfile
mediaDisplayProfile
setMediaDisplayLockOut
setMediaDisplayLockOut
mediaDisplayStatus
loadContent
loadContent
contentStatus
releaseContent
releaseContent
contentStatus
setActiveContent
setActiveContent
contentStatus
getContentStatus
getContentStatus
contentStatus
showMediaDisplay
showMediaDisplay
mediaDisplayAck
hideMediaDisplay
hideMediaDisplay
mediaDisplayAck
getContentLogStatus
getContentLogStatus
contentLogStatus
getContentLog
getContentLog
contentLogList
Requests / Notifications
Responses
getStorageInfo
storageInfoList
getGatLog
EGM-Initiated GAT
2.2.22 central Class
Guest
Owner
Class / Functional Group
Core Central Determination
Functionality
EGM-Initiated Central
2.2.23 mediaDisplay Class
Guest
Owner
Class / Functional Group
Core Media Display (PUI)
Functionality (Extension 1a
mediaDisplay)
2.2.24 storage Class
Guest
Owner
Class / Functional Group
Core Storage Requirements
Functionality (Extension 1c)
getStorageInfo
2012/03/19
©2012 Gaming Standards Association
Page 17 of 19
G2S v1.1 Host Certification Requirements – Release 2
2.2.25 cashout Class
Guest
Owner
Class / Functional Group
Requests / Notifications
Responses
setCashoutState
setCashoutState
cashoutStatus
getCashoutStatus
getCashoutStatus
cashoutStatus
getCashoutProfile
getCashoutProfile
cashoutProfile
initiateCashoutRequest
initiateCashoutRequest
cashoutRequestPending
cancelCashoutRequest
cancelCashoutRequest
cancelCashoutRequestAck
getHostCashoutLogStatus
getHostCashoutLogStatus
hostCashoutLogStatus
getHostCashoutLog
getHostCashoutLog
hostCashoutLogList
commitCashoutRequest
commitCashoutRequestAck
Core Remote Cash-Out Functionality
(Extension 1f)
EGM-Initiated Cash Out
2.2.26 informedPlayer Class (Extension 1g)
Guest
Owner
Class / Functional Group
Requests / Notifications
Responses
setIpState
setIpState
ipStatus
getIpStatus
getIpStatus
ipStatus
getIpProfile
getIpProfile
ipProfile
setIpMessage
setIpMessage
ipMessageAck
setIpGameDelay
setIpGameDelay
ipStatus
getIpPinInfo
ipPinInfo
validateIpPin
validateIpAck
ipStatus
ipStatusAck
getIpKeyPair
ipKeyPair
Requests / Notifications
Responses
Core Informed Player Functionality
(Extension 1g)
EGM-Initiated Informed Player
2.2.27 Minimum Display Requirements
Guest
Owner
Class / Functional Group
Core Minimum Display Requirements
Minimum Display Requirements
Extension (Extension 1a)
2012/03/19
©2012 Gaming Standards Association
Page 18 of 19
G2S v1.1 Host Certification Requirements – Release 2
2.2.28 smartCard Class (Extension 1j)
Guest
Owner
Class / Functional Group
Requests / Notifications
Responses
setSmartCardState
setSmartCardState
smartCardStatus
setSmartCardLockOut
setSmartCardLockOut
smartCardStatus
getSmartCardStatus
getSmartCardStatus
smartCardStatus
getSmartCardProfile
getSmartCardProfile
smartCardProfile
getSmartCardLogStatus
getSmartCardLogStatus
smartCardLogStatus
getSmartCardLog
getSmartCardLog
smartCardLogList
hostMsg
hostMsg
Core Smart Card Functionality
(Extension 1j)
EGM-Initiated Smart Card
smartCardMsg
transactionReport
2012/03/19
©2012 Gaming Standards Association
transactionReportAck
Page 19 of 19