1461083635-5aaf5f87-f4d7-461b-8cb2-d9578ac36ff5

1. A method comprising:
a customer premise equipment (CPE) downloading a CPE configuration file over a machine communication network;
the CPE checking the configuration file for a software load name;
if the software load name is found in the configuration file, the CPE downloading an operating software image specified in the software load name, and the CPE resetting and entering an initialized state ready for service;
if the software load name is not found in the configuration file, the CPE determining if the configuration file includes a vendor table having records specific to a vendor of the CPE, the vendor table comprising Type Length Value data fields;
if the vendor table is not found in the configuration file, the CPE entering the initialized state ready for service;
if the vendor table is found in the configuration file, the CPE locating a record in the vendor table corresponding to a criteria unique to a subset of CPEs of the vendor of the CPE;
if the record in the vendor table corresponding to a criteria unique to a subset of CPEs of the vendor of the CPE is found, the CPE downloading an operating software image specified in the record; and
if the record in the vendor table corresponding to a criteria unique to a subset of CPEs of the vendor of the CPE is not found, the CPE entering the initialized state ready for service.
2. The method of claim 1, the vendor of the CPE identified from a media access control address of the CPE.
3. The method of claim 1, the criteria unique to a subset of CPEs of the vendor of the CPE comprising a hardware model number for the CPE.
4. The method of claim 1, the criteria unique to a subset of CPEs of the vendor of the CPE comprising a hardware revision number for the CPE.
5. The method of claim 1, the criteria unique to a subset of CPEs of the vendor of the CPE comprising a software revision number for the CPE.
6. The method of claim 1, the criteria unique to a subset of CPEs of the vendor of the CPE contained in a management information block (MIB) object for the CPE.
7. The method of claim 6, the MIB object for the CPE stored in a non-volatile memory of the CPE.
8. A device comprising:
a file retrieval module operable to download a configuration file over a machine communication network;
a boot module to place the device into an initialized and ready for service state;
a comparison module operable to check the configuration file for a software load name, and if the software load name is found in the configuration file, to operate the file retrieval module to download an operating software image specified in the software load name, and to operate the boot module to place the device into the initialized state ready for service;
a comparison module operable to

(i) check the configuration the for a software load name, and
(ii) if the software load name is not found in the configuration file, to determine if the configuration file includes a vendor table having records specific to a vendor of the device, the vendor table comprising Type Length Value data fields, and
(iii) if the vendor table is not found in the configuration file, to operate the boot module to place the device into the initialized state ready for service, and
(iv) if the vendor table is found in the configuration file, to locate a record in the vendor table corresponding to a criteria unique to a subset of devices of the vendor of the device, and
(v) if the record in the vendor table corresponding to a criteria unique to a subset of devices of the vendor of the device is found, to operate the file retrieval module to download an operating software image specified in the record, and
(vi) if the record in the vendor table corresponding to a criteria unique to a subset of devices of the vendor of the device is not found, to operate the boot module to place the device into the initialized state ready for service;
each of the comparison module, boot module, and file retrieval module stored in a non-transitory machine memory.
9. The device of claim 8, the vendor of the device identified from a media access control address of the device.
10. The device of claim 8, the criteria unique to a subset of devices of the vendor of the device comprising a hardware model number for the device.
11. The device of claim 8, the criteria unique to a subset of devices of the vendor of the device comprising a hardware revision number for the device.
12. The device of claim 8, the criteria unique to a subset of devices of the vendor of the device comprising a software revision number for the device.
13. The device of claim 8, the criteria unique to a subset of devices of the vendor of the device contained in a management information block (MIB) object for the device.
14. The device of claim 13, the MIB object for the device stored in a non-volatile memory of the device.

The claims below are in addition to those above.
All refrences to claim(s) which appear below refer to the numbering after this setence.

1. A gaming system comprising:
a housing;
at least one display device supported by the housing;
a plurality of input devices supported by the housing, said plurality of input devices including:
(i) an acceptor,
(ii) a validator, and
(iii) a cashout device;

at least one processor; and
at least one memory device which stores a plurality of instructions, which when executed by the at least one processor, cause the at least one processor to operate with the at least one display device and the plurality of input devices to:
(a) if a physical item is received via the acceptor:
(i) identify, via the validator, the received physical item, and
(ii) establish a credit balance based, at least in part, on a monetary value associated with the received and identified physical item,

(b) send to a service provider identification system a notification message including an enterprise player identifier, wherein the enterprise player identifier is a casino-specific identifier assigned by a casino to a player,
(c) receive a federated player identifier, wherein the federated player identifier is resolved from the enterprise player identifier and wherein the federated player identifier is associated with a plurality of different enterprise player identifiers,
(d) utilize the federated player identifier to retrieve game-specific status data, and
(e) if a cashout input is received via the cashout device, cause an initiation of any payout associated with the credit balance.
2. The gaming system of claim 1, wherein the enterprise player identifier is linked to the federated player identifier.
3. The gaming system of claim 1, wherein when executed by the at least one processor, the plurality of instructions cause the at least one processor to enable the player to participate in at least one gaming program at each of a plurality of enterprises, wherein gaming data associated with said player is shared among the plurality of enterprises.
4. The gaming system of claim 1, wherein the game-specific status data includes data selected from the group consisting of: goal progress data, unlocked levels data, player achievement data, and avatar data.
5. The gaming system of claim 1, wherein when executed by the at least one processor, the plurality of instructions cause the at least one processor to prompt the player to enter a service provider identification system username and password, wherein the enterprise player identifier is linked to the federated player identifier if the enterprise player identifier is unknown to the service provider identification system.
6. The gaming system of claim 1, wherein when executed by the at least one processor, the plurality of instructions cause the at least one processor to ensure that the player is an owner of an identification device used.
7. The gaming system server of claim 1, wherein when executed by the at least one processor, the plurality of instructions cause the at least one processor to receive an enterprise gaming machine identifier together with the enterprise player identifier.
8. The gaming system server of claim 1, wherein when executed by the at least one processor, the plurality of instructions cause the at least one processor to link the enterprise player identifier to the federated player identifier.
9. The gaming system server of claim 1, wherein the federated player identifier is used to publish game-specific status data on an Internet if a player approval is obtained.
10. The gaming system server of claim 1, wherein when executed by the at least one processor, the plurality of instructions cause the at least one processor to:
store at least one of: at least one wager, at least one win, and at least one preferred game of the player; and
utilize player data for at least one of: marketing and implementing at least one gaming guideline.
11. The gaming system server of claim 1, wherein the federated player identifier is used to monitor player game progress across multiple games at different enterprises.
12. The gaming system server of claim 1, wherein when executed by the at least one processor, the plurality of instructions cause the at least one processor to federate a plurality of enterprise identifiers to a single federated player identifier.
13. A gaming system server comprising:
at least one processor; and
at least one memory device which stores a plurality of instructions, which when executed by the at least one processor, cause the at least one processor to:
(a) receive a notification message including an enterprise player identifier from a gaming machine including at least one display device supported by a housing and a plurality of input devices supported by the housing, said plurality of input devices including: (i) an acceptor of a physical item associated with a monetary value, (ii) a validator configured to identify the physical item, and (iii) a cashout device configured to receive an input to cause an initiation of a payout associated with a credit balance, wherein the enterprise player identifier is a casino-specific identifier assigned by a casino to a player,
(b) resolve the enterprise player identifier to a federated player identifier, wherein the federated player identifier is associated with a plurality of different enterprise player identifiers, and
(c) send the federated player identifier to the gaming machine, wherein the gaming machine utilizes the federated player identifier to retrieve game-specific status data.
14. A gaming system comprising:
a housing;
at least one display device supported by the housing;
a plurality of input devices supported by the housing, said plurality of input devices including:
(i) an acceptor,
(ii) a validator, and
(iii) a cashout device;

at least one processor; and
at least one memory device which stores a plurality of instructions, which when executed by the at least one processor, cause the at least one processor to operate with the at least one display device and the plurality of input devices to:
(a) if a physical item is received via the acceptor:
(i) identify, via the validator, the received physical item, and
(ii) establish a credit balance based, at least in part, on a monetary value associated with the received and identified physical item,

(b) receive an enterprise player identifier from a player, the enterprise player identifier being a casino-specific identifier assigned by a casino to the player,
(c) transmit the enterprise player identifier to an external game provider identification system, wherein the enterprise player identifier is resolved to a federated player identifier and the federated player identifier is associated with a plurality of different enterprise player identifiers assigned to the player from different casinos,
(d) receive the federated player identifier,
(e) query an external database using the federated player identifier to obtain game status information,
(f) record game play data to the external database, said recording is performed using the federated player identifier, and
(g) if a cashout input is received via the cashout device, cause an initiation of any payout associated with the credit balance.
15. The gaming system of claim 14, wherein when executed by the at least one processor, the plurality of instructions cause the at least one processor to provide data for at least one gaming program.
16. The gaming system of claim 14, wherein when executed by the at least one processor, the plurality of instructions cause the at least one processor to provide data for direct marketing to the player.
17. The gaming system of claim 14, wherein when executed by the at least one processor, the plurality of instructions cause the at least one processor to:
prompt the player to enter an external game provider identification system password and username, and
receive an external game provider identification system password and username.
18. The gaming system of claim 14, wherein when executed by the at least one processor, the plurality of instructions cause the at least one processor to enable the player to create a new external game provider identification system account.