Network gaming system with a distribution server

Abstract

A network gaming system includes a distribution server to provide gaming devices with communication with backend servers. The system includes at least one backend server, at least one gaming device, and at least one distribution server, wherein each gaming device is in communication with at least one backend server through at least one distribution server.

Description

BACKGROUND OF THE INVENTION

Traditionally, gaming networks have been custom designed for gaming purposes only. In this regard, gaming networks have been constructed only to include gaming functionality and have lagged behind the rapid growth of network and communications capability available in the computing, communications and Internet industries.

In many older, or “legacy,” slot systems, data lines are constructed for robust and reliable communications in the harsh environment of the casino, wherein in many cases, slot systems remain up 24 hours a day, 365 days year. Certain legacy slot systems, such as SDS® “Slotline” System by Bally Gaming & Systems, Inc. of Las Vegas, Nev., were developed in the early 1970's before internet protocol (IP) or packet-based networks, such as the Internet and Ethernet networks, were developed to the current level. The legacy systems were originally designed to provide security and accounting information from the gaming device to the backend server over a cable, which was a serial (narrow band) network. Security information included door opens, machine breakdowns, and tilt conditions. Accounting information was related to profit and loss of the operation and used to detect cheating, skimming, and misreporting for tax purposes. The data transmission needs were modest and sporadic in nature, and implemented with a network bridge performing a polling protocol to communicate with the gaming devices. A data rate of 7,200 bits-per-second (bps) was a more than adequate selection for transmission speed since that data rate provided reliable and robust communication, and was by its unusual data rate, a security measure through its obscurity.

Recently, however, casino owners have become aware that the use of additional features to gaming machines and the increasing need for operational efficiency, are driving the current proprietary gaming networks toward much greater capabilities, such as full-duplex (two-way) connectivity and higher speed (e.g., 10 Mbps or greater) plus improved analytic features. These improvements are expected to bring the player greater game choices, more rapid renewal of the slot floor entertainment options, and greater operational efficiency for the operator. These translate into increased revenue generation and improved profits.

However, it is costly to install complete new networks to handle the high-speed traffic necessary for the improved features. Especially in the casino environment, for example, it is costly to install new high-speed cable, due to slot floors typically employing “Walker Duct” in which the communications cables are buried inside the concrete floor. Casino owners are unwilling at best to close down their casino for the time it would take to tear up the casino floor to install the new cabling.

One solution is to keep the previous network infrastructure in place, and to have backend servers that provide the enhanced features convert high speed protocols, for example Ethernet, into narrowband protocols, for example Slotline, to send and receive data through the older network cabling and equipment to and from the gaming devices in the network. However, this conversion requires significant overhead for the server or servers performing the conversion, while still causing a bottleneck in network traffic at the point of conversion to the older protocol.

Thus, it would be desirable to be able to provide high-speed communications in a gaming network using older or legacy network cabling and equipment, without burdening the backend servers in the gaming network with the task of protocol conversion.

SUMMARY OF THE INVENTION

Briefly, and in general terms, the claimed invention resolves the above and other problems by providing a gaming system having a distribution server to provide gaming devices with communication with backend servers. The system includes at least one backend server, at least one gaming device, and at least one distribution server, wherein each gaming device is in communication with at least one backend server through at least one distribution server.

In one embodiment, a gaming system includes at least one backend server, at least one gaming device, and at least one data cache server. Each gaming device is in communication with at least one backend server through at least one data cache server.

In one embodiment, a gaming network includes at least one gaming device, a core layer, and a distribution layer, wherein each gaming device communicates with the core layer via the distribution layer.

In another embodiment, a method eliminates asymmetrical data flow in a gaming network. A backend server and one or more gaming devices are established. A distribution server is established. Data is transmitted between the gaming devices and the backend server through the distribution server.

In another embodiment, an improvement in a gaming network includes a distribution server means for caching data, whereby offload processing and network efficiency are enhanced.

In another embodiment, an improvement in a gaming network comprises a data cache means for caching data between a gaming device and a backend server, whereby offload processing and network efficiency are enhanced.

In another embodiment, an improvement in a gaming network includes a distribution server means for caching data, whereby asymmetrical data flow is minimized between a gaming device and a backend server.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram that illustrates components of a preferred embodiment of a gaming network according to one embodiment;

FIG. 2 is a block diagram that illustrates the components of another embodiment of a network;

FIG. 3 is a block diagram that illustrates an example of a four game device carousel according to one embodiment;

FIG. 4 is a block diagram that illustrates a manner in which game node switches in a carousel routed to one last carousel switch in one embodiment;

FIG. 5 is a block diagram that illustrates a plurality of interfaces used in the distribution server or bridge according to one embodiment;

FIG. 6 is a block diagram illustrating a system that uses a long range Ethernet network according to one embodiment;

FIG. 7 is a block diagram of an internal structure of a bridge device;

FIG. 8 is a hardware block diagram illustrating components of an FPGA that implements transmission protocol according to one embodiment;

FIG. 9 is a block diagram that illustrates repeater/hub hardware in according to one embodiment;

FIG. 10 is a hardware block diagram that illustrates components of a GMU interface according to one embodiment;

FIG. 11 is a bock diagram that illustrates a CAT-5 twisted pair cable used in one embodiment;

FIG. 12 is a graphical illustration of a call/response cycle implemented by an FPGA to communicate with GMUs of the gaming devices;

FIG. 13 is a block diagram that depicts the structure of a communication transaction wherein a bridge transmits data to a GMU; and

FIG. 14 is a block diagram that depicts the structure of a broadcast message for a network.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

A one embodiment of a network gaming system, referred to herein as the “Tahoe Network,” constructed in accordance with the claimed invention, is directed towards a gaming system having a distribution server to provide gaming devices with communication with backend servers.

The Tahoe Network is capable of rapidly transporting large data loads using, in one embodiment, mostly industry-standard technology and off-the-shelf hardware and software. For example, Ethernet network typology is used as a network interface in this embodiment due to the World-wide acceptance of Ethernet as a network standard and its relative ease of use. For example, Ethernet networks have the ability to scale from single point-to-point connections to large-sized installations encompassing thousands of network devices.

In one embodiment, an upgraded proprietary network is used to connect at least some components. A hybrid network of the two technologies (Ethernet and proprietary) in which the strengths of Ethernet are exploited while its weaknesses are eliminated with the proprietary network is preferred for some embodiments, but not necessarily all embodiments.

Referring now to the drawings, wherein like reference numerals denote like or corresponding parts throughout the drawings and, more particularly to FIGS. 1-14, there is shown an embodiment of a network gaming system. With reference specifically to FIG. 1, a block diagram illustrates components of an embodiment of a gaming network 10. Preferably, but not necessarily, the network 10 is a 3-tiered, or layered, network 10. A backend core layer 300 performs as a gateway between a game server 102 and the gaming devices 302. A distribution layer 200, in one embodiment, contains servers 202 that preferably reside on the periphery of a casino floor. In one embodiment, the distribution layer servers (“distribution servers”) 202 concentrate data traffic from game devices 302 into high-bandwidth trunks 210 connected to the core layer 100. The distribution servers 202 also cache data for the casino floor devices 302. In one embodiment, an access layer 300 is a physical interface between a game interface (such as an iView® game interface available from Bally Systems & Gaming, Inc. of Las Vegas, Nev.) on a gaming device 302 and the rest of the network 10.

In one embodiment, L2 or L3 switches 220 connect the layers 100, 200 and 300 together. 10 or 100 base-T Ethernet cable is used with the switches 200 to eventually connect to managed switches 322 on the gaming floor to connect to the gaming devices 302 through a backbone switch 320.

In one embodiment, the cabling for the network 10 includes, at least in part, legacy cable, for example, serial cable, which is used congruent with newly installed cable for the network 10 to maintain the operation and integrity of a casino's existing systems, such as a slot accounting system for example. Eventually, the whole network 10, including cabling and other older components, may be phased out and ported to the new cabling and servers 102 and 202. For example, the slot accounting system installed in the core layer server 102 as a software process that communicates over the network 10 instead of through legacy serial connections to the gaming devices 302.

With reference to FIG. 2, a block diagram illustrates another embodiment of the network 10. In this embodiment, the servers 102 and switches 220 of the core layer 100 are the same as in FIG. 1. However, in the distribution layer, the distribution and switching functions are combined in the distribution server 202, which provides an improved “rapid slotline” (RSL) network connection, which includes a high-speed gaming network described in more detail below. In this embodiment, the RSL connection connects the distribution server 202 to an RSL hub 350 in the access layer 300. In one embodiment, each RSL hub 350 connects a plurality of gaming devices 302 (for example, 8 gaming devices 302 in FIG. 2) to the network 10. A plurality of RSL hubs 350 are daisy-chained together, each connecting an additional plurality of gaming devices 302 to the network 10.

Referring back to FIG. 1, in one embodiment, the switch 322 is a 5-8 port managed switch that resides either inside a game device 302 or the slot stand. In another embodiment, the switch 322 is a rackmount switch that is used depending on space in a slot stand. In one embodiment, a managed switch 322 is used instead of an un-managed switch 322 to achieve both speed and reliability across the network 10. A managed switch 322 operates in an industrial environment and, hence, has a higher mean time between failure (MTBF), and a more favourable mean time to repair (MTTR) than a typical un-managed switch 322. This is due to the built-in management and troubleshooting functionality of a managed switch 322. The relatively low cost of a managed switch 322, low port count and small size also make field repairs simpler. Further, a managed switch enforces CSMA/CD protocol on an individual line-by-line basis, providing each connected device with a dedicated line. Thus it provides much more efficient bandwidth utilization and prevents the entire system from ‘locking up’ in collision detections as traffic becomes higher.

In one embodiment, the 3Com® NJ200 Network Jack is used as a managed switch. The NJ200 is designed to be installed in an office network data port opening or electrical wall outlet. It features 4-10/100 downlink ports and 1-10/100 uplink port, and is powered via an external power supply (wall transformer), or by power-over-Ethernet (PoE).

The NJ200 is designed to be installed in an office network data port or electrical wall outlet, neither of which are present inside a gaming machine or accompanying slot stand. The proposed solution is to mount the NJ200 inside an inexpensive plastic electrical box and then mount the assembly into the slot stand.

In one embodiment, multiple upstream ports are concentrated within a carousel 310 with another switch 322.

In another embodiment, the Etherwan 1808C is used as an industrial managed switch 322 that comes in a “desktop” form, and provides 7 downlink ports and 1 uplink port. The advantage of using the Etherwan 1808C over the 3Com NJ200 is the expanded number of ports. Etherwan further offers several models of the Etherwan 1808 equipped with fiber ports in the event that fiber cable is used on the casino floor.

The Moxa ED6008 is yet another access layer switch 322 that can be used in one embodiment. The ED6008 is a small form-factor industrial DIN-mounted device equipped for dual-redundant power to attain a high MTBF. Although the ED6008 is an 8-port industrial managed switch, it can also function as a dynamic host configuration protocol (DHCP) server.

In embodiment, instead of using cabling to carry Ethernet signals over the network, connections between various components are wireless. In another embodiment, long range Ethernet (LRE) is used for the connections in some of the components of the network 10.

Data traffic flow in a modern gaming network is typically asymmetrical. Data flow is typically heavy from the core layer server(s) 102 to the gaming devices 302 on the gaming floor in the access layer 300 due to data download requirements of modern gaming devices 302, and data traffic flow is light from the gaming devices 302 to the core layer server(s). This asymmetry, and an accompanying data bottleneck it creates, is alleviated by the distribution server(s) 202, also referred to as data cache servers 202. The distribution server 202 is located at a midpoint of the network, namely, the Distribution Layer. One or more distribution servers 202 operate to cache data for download to floor devices 302 (e.g., code updates, device content), thus presenting a lighter load on the backend servers 102, and speeding up data distribution.

The distribution servers 202 are not confined to the role of data caches. By way of example, and not by way of limitation, dynamic host configuration protocol (DHCP) relay, bus translation (e.g., Ethernet to RSL), and distributed computing are other functions the distribution server 102 performs in some embodiments.

Distribution servers 202, or data caches, can be stand-alone devices (e.g., servers, or built in network hardware such as RSL hubs described below. Distribution Servers 202 allow for parallel processing across the gaming floor. In one embodiment, distribution servers offload processing loads from the backend servers 102, cache or backup data from games played on gaming devices 302, and speed up network 10 transactions. Other embodiments include redundant cabling in the core and distribution layers 100 and 200 for failover contingencies, or an expanded core layer 100 combining distribution and core layers 100 to reduce device count.

Cabling

In one embodiment, link 210 is a fiber optic link connecting the core and distribution layers 100 and 200, which serves a dual purpose of providing long-distance hauls and high bandwidth. Fiber optic cable has an advantage over copper (CAT-5) cabling in that it can transmit data over longer distances and, depending on the fiber type, has a much higher bandwidth. Fiber cable is also immune to electromagnetic noise and interference.

Fiber optic cable may be, however, more expensive than copper cable (approximately $0.65/ft. for multi-mode 12-fiber indoor/outdoor fiber optic cable vs. $0.25/ft. for CAT-5 cable). In some embodiments, fiber-optic cable is used in instances wherein a copper cable is not adequate, for example, when the distance between the core layer 100 and distribution layer 200 exceeds a 300 foot CAT-5 Ethernet limit.

In one embodiment, gigabit Ethernet over copper cable is used when high bandwidth is needed, and cable distances allow for it. The cabling requirements for copper gigabit Ethernet are the same as that for fast Ethernet (100 Mb/s) because gigabit Ethernet operates at the same frequency as Fast Ethernet (100 MHz). Gigabit Ethernet attains its higher data bandwidth by using all 4 pairs (8 wires) of the CAT-5 cable, whereas fast Ethernet uses only 2 pairs (4 wires). The end result is that copper gigabit Ethernet will operate on any network that currently operates at fast Ethernet speeds provided that all 8 wires are properly terminated within the CAT-5 cable RJ45 plug.

In one embodiment, bandwidth is increased by using a method called trunking (or aggregation, as it is also known). Trunking is a method of combining multiple communications channels (cables) to form one large bandwidth channel. For example, and not by way of limitation, in one embodiment, four fast Ethernet channels that operate individually at 100 Mb/s are combined into one trunk to produce a single channel operating at 400 Mb/s. In this embodiment, the network switches 220, and other network hardware, have the trunking feature built-in in order to take advantage of trunking. Another benefit of trunking is redundancy. If one channel (cable) of a trunk fails for any reason, the entire link does not fail. The bandwidth of the link is reduced, but the link is still functional.

Distribution to Access Layer Ethernet Cabling

In one embodiment, the cabling running from the distribution layer 200 to the access layer 300 is CAT-5 copper cable to function with the game node switches 322 in the access layer 300 that in some embodiments have CAT-5 interfaces. In one embodiment, these game node switches 322 are located inside slot stands and are relatively small fast Ethernet units with 5 to 8 ports. In some embodiments, as is the case in many casinos today, the arrangement of the gaming devices 302 on the casino floor is a “carousel” (310 in FIG. 1), which typically has 10-20 gaming devices 302 sitting atop slot stands arranged back-to-back, or side-to-side to form a long double row of gaming devices 302. In one embodiment, cabling to each gaming device 302 is achieved by routing a single CAT-5 cable from the gaming device 302 through the slot stand, and under the slot stand (through 3″×1″ cutouts called “mouse holes”) to the switch or bridge 322, which in some embodiments, is a passive switch 322. Any number of these switches 322 are connected together through a backbone 312, which is routed to the backend systems in the distribution and core layers 200 and 100.

With reference to FIG. 3, a block diagram illustrates an example four gaming device 302 carousel 310 according to one embodiment. Each gaming device (302 in FIGS. 1 and 2) is on a slot stand 306, and has a single CAT-5 cable 304 running from the gaming device down through mouse holes 308 in the slot stand 306, into a game node switch 322 located in one of the slot stands 306. For four gamine machines 302, at least a 5 port switch 322 is used (4 downlinks, and 1 uplink), so that 4 game devices 302 can be tied to one switch 322, with the switch 322 located within one of the slot stands 306 to which switch 322 is cabled.

FIG. 4 illustrates a manner in which the game node switches 322 in a carousel are concentrated to one last carousel or backbone switch 320 in one embodiment. In this embodiment, similar to the game node switches 322, the carousel switch 320 is located in a slot stand 306, and all the cabling to it is routed through the mouse holes in the slot stand 306. The uplink to the distribution layer from this carousel switch 320 runs to the closest distribution layer switch (220 in FIG. 1), preferably through a floor cable in this embodiment.

In one embodiment, each gaming device 302 is equipped with a combination user interface and game monitoring unit device. The game monitoring unit (GMU) is a device that monitors game activity in the gaming device 320, and among other functions, provides data regarding game play and status to the aforementioned user interface device. In one embodiment, the user interface device uses the game play data for bonus games or progressives. For network games, the interface device forwards the data to the backend servers 102. In one embodiment, the user interface is an iView device available from Bally Gaming & Systems, Inc. of, Las Vegas Nev.

The combination user interface device and GMU is referred to as a TahoeEPI herein. With reference to FIG. 5, a diagram illustrates a plurality of TahoeEPIs 500 used in the network 10 according to one embodiment. In one embodiment, the TahoeEPI 500 includes 3-port Ethernet hub 502 that is daisy chained to one or more hubs 502 for other TahoeEPIs 500. At least one of the TahoeEPIs 500 is further has an Ethernet connection to the carousel switch 320, which connects to the distribution layer 200 as described above.

In some embodiments, 4 TahoeEPI devices 500 are daisy-chained together through their integrated Ethernet hubs 502 with the last Tahoe EPI device 500 connected to the carousel switch. This arrangement eliminates the external game node switch 322 and effectively distributes the function of the game node switch 322 into each of the TahoeEPI devices 500, providing cost saving. Further, gaming devices 302 in one embodiment integrate Ethernet ports into their systems. The embedded Ethernet hub 502 on the TahoeEPI device 500 concentrates the Ethernet connections within a game device 302 into a single Ethernet port. This eliminates the need for redundant cabling to a game device 302 and at least some upstream hardware to interface to the additional Ethernet ports.

Distribution to Access Layer RSL Cabling

In one embodiment, the aforementioned RSL network integrates an older or existing slot cabling system while using active hubs 350 instead of passive switches 220 or line concentrators (“harmonicas”). The use of the active hub 350 allows for point-to-point signalling and higher data speeds.

Typically, an older or current slot line switch is used in older networks that is a 6-port device (1 line in; 1 line out; 4 device ports) whereas, in one embodiment, the RSL active hub 350 has provisions for 8 devices, or twice the capacity of typical slot line Harmonica. In one embodiment, the RSL active hub 350 follows the slot line switch topology in that it can be daisy-chained, for example, with 8 hubs 350.

Long Range Ethernet

In one embodiment, a long-range, low-bandwidth Ethernet network is used. One system is available from Hatteras Networks of Durham, N.C., a company that specializes in Long range Ethernet (LRE) solutions. The HN400 by Hatteras converts a standard 10/100B-TX Ethernet interface into an IEEE standard 2BASE-TL interface, which allows for Ethernet over long cables. The HN400 can operate at 2.3 Mb/s over 11,000 ft (3,350 meters) per wire pair. The 2BASE-TL IEEE specification uses “bonded pairs”, which means that two or more wire pairs can be combined to create a higher bandwidth trunk (similar to trunking described above).

FIG. 6 is block diagram illustrating one embodiment of the network 10 that uses long range Ethernet. In this embodiment, the network uses the Hatteras Networks LRE system, which uses a network interface unit (NIU) 600 at either end of a long cable run. Using the Hatteras system, a casino environment equipped with older, legacy, “Slotline” cabling 610 uses a NIU 600 in the core layer 100 and on the casino floor in the access layer 300, either on the periphery of the floor or inside a slot stand.

The maximum bandwidth on a single LRE bonded cable 610 (4 pairs bonded, 2.3 Mb/s/bonded pair) is typically 9.2 Mb/s. Dividing this bandwidth between a 16-game carousel gives each game ˜575 Kb/s of bandwidth. That is the main limitation of LRE. The bandwidth is limited unless multiple cables are bundled to produce a higher bandwidth trunk. LRE also doesn't obviate the need for access layer switches 320, 322 at the carousel 310 since the Hatteras NIUs 600 have only a single Ethernet port.

Hatteras Networks also produces their HN4000 product that can be used in place of the HN400 for the NIU 600. The HN4000 is a multi-channel version of the HN400 for the core layer 100 NIU 600. The HN4000 provides an interface for up to 40 wire pairs; a 100B-TX/LX or 1000B-TX/LX Ethernet interface, and is stackable up to five units.

The HN400 and HN4000 NIUs each have redundant power inputs through external power supplies (power bricks) and support in-band and out-of-band network management, including SNMP

Wireless

Wireless networking is used in one embodiment because it frees the gaming device 302 from a physical network interface (the network cable), allowing the casino owner the freedom to easily re-position gaming devices 302 about the casino floor.

Wireless (or “802.11” or “Wi-Fi”) systems are broken down into three fundamental standards, IEEE 802.11a, b and g. 802.11g is the most current standard and is backward compatible with 802.11b. 802.11a is used in dense user areas where higher bandwidth and a greater number of channels are needed. The relatively small coverage area allows more wireless “access points” (analogous to a wired hub or switch) to be concentrated in a certain area.

The 2.4 GHz band that 802.11b and 802.11g operate in and the 5 GHz band that 802.11a operates in is called the ISM band. This band of frequencies are unlicensed and open to anyone to use with few restrictions. The 2.4 GHZ band, for instance, is the same band that Bluetooth equipment and cordless phones operate in, and the use of these devices in a wireless networking environment may cause a decrease in the wireless network bandwidth.

In one embodiment, wired equivalent privacy (WEP) is employed in wireless networks as a baseline of security by encrypting data as it is transmitted. However, WEP does not have any provision for user authentication. In another embodiment, Wi-Fi protected access (WPA), a subset of the IEEE 802.1X security standard, is used to enhance the WEP user authentication mechanism. In another embodiment, a virtual private network (VPN) is employed on Wi-Fi systems as an alternative to 802.1X.

Antennas in wireless networking systems typically radiate in an omni-directional pattern to maximize coverage. In one embodiment, this is changed to achieve more directional coverage. In this embodiment, patch or yagi antennas are deployed for directional coverage and parabolic antennas are used for building-to-building links.

Hardware Management

In one embodiment, the switches used in the network are similar to the off-the-shelf desktop switches with the exception that they have been upgraded for industrial use, and include hardware management protocol, such as SNMP, to aid in monitoring and troubleshooting the network 10. Preferably, the distribution and core layer switches 220 use a management package such that the entire network 10 is managed from a central location.

Power

In some embodiments, where power is not readily available for additional network devices, power over ethernet (PoE) is used. PoE enables devices (such as access layer switches 220) to be powered over CAT-5.

In another embodiment, redundant power is used for devices in the core and distribution layer 100 and 200. Those devices equipped for redundant power use auxiliary DC power inputs, not dual AC power inputs, and use external rackmount power supply units. Blade-style switch chassis' are equipped with redundant, hot-swappable internal AC-DC power supplies.

Hardware Redundancy

In one embodiment, redundancy is used at critical bottlenecks in the system, such as the core layer 100. In one embodiment, the core layer 100 represents a single network access point that can severely impact the performance and availability of the entire network should it or any piece of it fail. Thus in this embodiment, redundancy is preferably used in many components in the core layer 100, at least for those components that do not have a favourable mean-time to repair (MTTR) rating, or for which replacing a failed component is not very quick and easy. In one embodiment, spare components are pre-configured, stocked and mounted with the online hardware as a “hot spare.”

Distribution Layer

The distribution layer switches 220 concentrate the access layer switch uplinks into a high-bandwidth link to the core layer 100. The distribution layer hardware is optional and is eliminated in some embodiments with small installations. In one embodiment, the distribution layer hardware includes 24 and/or 48 port rackmount managed L2 switches 220. These switches are mounted on the periphery of the casino floor within 300 feet (copper Ethernet range) of the access layer switches 320, 322 they interface to. In one embodiment, the L2 switch used is the Nortel® BayStack® 470-24T available from Nortel Networks of Santa Clara, Calif. This L2 switch features 24 RJ45 10/100 downlink ports and 2 Gigabit fiber uplink ports. It is stackable (multiple units can be connected together to produce one large logical switch) and the uplink ports can be trunked together to produce a single high-bandwidth pipeline. Multiple uplink ports (trunking) also provide a level of redundancy in single points.

Core Layer

The core layer 100 is the interface between the main backend server(s) 120 (Tahoe servers) and the rest of the network 10. A backend server 120 interfaces with each individual gaming device 320, or iView device describe above. In one embodiment, the core layer 100 includes fast L3 switches 220, which come in many different configurations ranging from 1U rackmount devices up to hot-swappable, dual-redundant enterprise blade switches 220.

The Netgear GSM7324 managed L3 switch is one such switch that is used in one embodiment. It is a 1U rackmount chassis featuring 24 RJ45 10/100/1000 ports and 4 SFP ports that can be configurable as RJ45 (copper) or SC (fiber) connections. In another embodiment, the 3Com GSM7324 is used as an L3 switch 220.

In another embodiment, 3Com's 4050 L3 Switch is used, which features 12 10/100/1000 ports and 12 fiber ports. The 3Com 4060 and 4070 switches are similar to the 4050 with the exception of the port configuration, wherein the 4060 has 6 10/100/1000 ports and 18 fiber ports, and the 4070 has 24 fiber ports. In some embodiments, any of these L3 switches are used as the L3 switch 220 in the core layer 100.

In yet another embodiment, the Cisco® 4507R modular blade switch, available from Cisco Systems of San Jose, Calif. is used as the L3 switch 220 in the core layer 100.

RSL

In the past, prior art slot networks, such as the “Slotline” network by Bally Gamming & Systems, Inc. of Nevada, Las Vegas, operated at a relatively low data rate of 7200 bps, which has served the needs of slot data systems (SDS) over the last 20 years. However, the demands of new applications and desire of casino operators to deliver a more compelling player experience has pushed the existing architecture to its breaking point.

In one embodiment a “rapid slot line” (RapidSL) system includes a networking solution that is similar in concept and physical layout to the existing Slotline network, while providing a substantial increase in network throughput as well as retaining deterministic timing and throughput for network traffic that exists in the system. In one embodiment, a throughput of 30 Mb/sec is achieved. In another embodiment, the throughput is greater than 100 Mb/sec. In one embodiment, RapidSL is based on the TIA/EIA RS-485 signalling standard (RS-R85) used in a number of non-gaming industries. This RS-485 standard is commonly used in industrial networking, process control, and consumer applications. For example, it forms the core of the Profibus industrial networking system and is often used as the physical layer for the widely used controller area network (CAN) protocol.

RSL Hardware Functional Description

In one embodiment, the RapidSL system architecture includes three major functional blocks, a head end, repeater/hub, and node hardware. The architecture of a RapidSL based slot floor is similar to that of the original slotline concept. With reference back to FIG. 2, the older switches that are used to distribute signals to the game device 320 are replaced by an active repeater/hub 350 that allows the data rate from a game network bridge/distribution server (GNB) 202 to the GMU of the gaming device 320 to be increased at least 30 Mb. In one embodiment, Up to eight repeater/hubs 350 are connected in a daisy chain fashion to a single GNB device 202. In one embodiment, the repeater/hubs 350 have eight available ports for GMU attachment. This configuration allows up to 64 GMUs to be attached to a single GNB driven 202 slotline.

RSL Signaling

One benefit of the RapidSL system is that of a point-to-point link is provided for every gaming device. Every link has its own transceiver data rates that are correspondingly higher and more reliable. In this embodiment, every link adheres to the TIA/EIA RS-485 specification in order to improve bus integrity.

RSL Head End Hardware

FIG. 7 depicts a block diagram of an internal structure of a bridge device (202 in FIG. 2), which is also referred to as a “GameNet Bridge” device 202 herein. The bridge 202 contains a RapidSL interface card 762. Rather than a separate card that connects to a single board computer (SBC) 764 through a serial port, as in some currently used bridges, the RapidSL interface card 762 connects directly to a PC local bus of the SBC 762. This provides a much higher bandwidth connection to the SBC 762, which allows the 10 Mb/sec slotline signalling rate that is supported. Other components of the bridge device 202 are power conditioning circuitry a field programmable gate array (FPGA) 768 that contains core functionality of the RapidSL line protocol.

With reference to FIG. 8, a block illustrates a hardware design implemented in the FPGA to create the Slotline protocol. In one embodiment, the protocol is entirely hardware based, and requires no firmware intervention to successfully move a packet, that in can be as large as 256 bytes. This completely eliminates a performance bottleneck that has plagued the firmware packages in previous generations of GMU hardware. In addition, due to the fact the Slotline protocol implemented in the FPGA is now hardware based, multi millisecond timeout values that previously wasted bandwidth in the previous protocol now shrink to approximately two microseconds.

With reference to FIG. 9, a block diagram illustrates repeater/hub hardware in the RSL-hub 350 according to one embodiment. A single connection from the GNB 202, or from another hub 350 is delivered to eight game connection ports and to a downstream port, which may in turn be connected to another hub. Control and distribution of signals inside the hub is managed by a small programmable logic device (FPGA) 602. In one embodiment, as the hub is merely splitting and repeating the signals from an upstream port, or from the game ports, the logic contained in the FPGA 602 is limited in scope for efficiency, but not necessarily. The hub 350 includes an RS-485 transmitter receiver 604, conditioner 606 and interface connector 608.

With reference to FIG. 10, a hardware block diagram illustrates components of a GMU interface 1002 to connect the GMU to a RapidSL network according to one embodiment. Each connector 1004 connects the interface 1002 to a GMU. For each connector 1004, a RS-485 signal conditioner 1006 and transmitter receiver 1008 transmit and receive data to and from the GMU. Similarly, each connector 1018 connects the interface 1002 to a bridge or another interface in a hub. For each connector 1018, a RS-485 signal conditioner 1020 and transmitter receiver 1022 transmit and receive data to and from a bridge or hub. Power input is handled by a converter 1032 for the interface 1002.

With the hardware assistance provided by the FPGA, a streamlined Slotline protocol is implemented that is not saddled with the immense delays inherent in the current Slotline protocol, while still maintaining the deterministic and timely throughput that has made the existing protocol such a success over the last two decades. The transmission protocol retains the high level of determinism by keeping and enhancing (through hardware components as illustrated in FIG. 10) a time slicing mechanism, described below with respect to FIGS. 12-14, that allows fair access to the network for all GMUs of the gaming devices 320.

With reference to FIG. 11, a bock diagram illustrates a CAT-5 twisted pair cable 950 according to one embodiment. In this embodiment, the hardware cable drivers used for RapidSL are based on the TIA/EIA RS-485 signalling standard. Although RS-485 is designed for use within a multi-drop environment (multiple drivers on the bus), RapidSL uses point-to-point nodes, wherein only two hardware drivers are needed on any continuous bus, which are a transmitter 952 and a receiver 954. In one embodiment, hardware drivers used for RapidSL are Linear Technology's LTC1686 52 Mbps Precision Delay RS485 Fail-Safe transceivers. The point-to-point network configuration in this embodiment has many advantages over a multi-drop network, the main advantage being that higher data speeds can be achieved due to the lack of stubs, or branches, off the main network backbone.

FIG. 12 graphically illustrates a call/response cycle implemented by the FPGA to communicate with the GMUs of the gaming devices 320 according to one embodiment. The GMUs are allowed access to the communications channel, in turn, via a time slicing mechanism. Time slices with no attached message are issued from the GNB 202 as a single byte containing the address of the gaming device 320 that is to respond. When a poll is issued, the gaming device 320 at the address in the poll byte can respond with a data packet. This packet is prefaced with the address of the device and a single byte indicating the actual number of bytes in the packet. Once the packet transmission is complete a sequence of two bytes each containing 0xFFh is transmitted. In one embodiment, this final two byte transmission is used to implement a CRC-16 error detection code. In the event that the GMU of a gaming machine 320 does not have a packet to transmit it simply transmits nothing. Once an approximately two microsecond time period has elapsed without a response, the GNB, grants a time slice to the next sequential gaming device 320 address.

It should be noted that this protocol does not define the content of the data packet. Any data can be transmitted, which allows the flexibility to layer any desired protocol atop this transmission medium.

In the event the a GNB 202 has system data to transmit to a GMU, a time slice with attached data is sent instead of a single byte address. FIG. 13 depicts the structure of this transaction. An address byte with the address of the desired device is transmitted followed by a byte containing the length of the message to be transmitted. The message containing up to 256 bytes is then transmitted. No acknowledgement is transmitted by the receiving GMU. In the event that the GMU has a packet ready to transmit at the time that the GNB 202 has finished its transmission, it the GMU begins its transmission using the format depicted in FIG. 10. Otherwise the GMU transmits nothing, the timeout elapses and the GNB 202 grants a time slice to the next device.

With reference to FIG. 14, a broadcast message is formatted in the same way as a system message, the only exception is that the address byte will be a higher value than 3Fh.

In one embodiment, the RapidSL protocol is time delimited. The end of a transmission is marked with a >2 microsecond period of no transmission. Start-of-transmission timeout is the same value as that of the end of transmission marker. Transmission timeout values are based on the worst-case propagation times through eight repeater/hubs attached to a total length of 200 m of CAT5 cable. Transmission times from the hubs to the attached GMUs are negligible and are not considered in the delay model.

In one embodiment, the RapidSL hardware presents a register and FIFO based interface to the applications that need to access it. Since the hardware only notifies the application that it needs to be serviced when it has a complete message available, the application is liberated from the stringent real-time requirements currently imposed by the Slotline system. The interface includes a control register, a message size register, an address register, read and write FIFOs, and an interrupt.

In one embodiment, writing a message to the RapidSL communication channel includes of three operations. First, if interrupts are enabled the application receives a transmitter empty interrupt. If interrupts are not enabled the control register is checked to see that the transmitter is empty. Second, the bytes of the message are written to the transmit FIFO. Third, the address of the GMU that the message is bound for is written to the address register. The act of writing the address to the address register causes the RapidSL hardware to begin transmission as soon as it is that address's time slice.

If there is no message waiting to be transmitted in the FIFO then the hardware time division engine continues issuing time slices.

In one embodiment, a message is read using a three-step process. If interrupts are enabled, the application will receive a “message waiting” interrupt. If interrupts are not enabled a control register is checked to see if a message is waiting. Second, the message size register is read. Third the number of bytes encoded in the message size register is read from the FIFO.

In some embodiments, the 30 Mb/sec data rate is not the highest bandwidth level that the RapidSL system is capable of achieving. Performance levels up to 100 Mb/sec are possible with existing RS-485 cable with the right selection of components and management of cable lengths. The basic architecture is not specifically mated to any particular transceiver technology, so, in some embodiments, RocketIO, Infiniband, LVDS, and 1 Gb Ethernet networks are used. Further a reasonable base target bandwidth for a fiber based RapidSL system is 2.5 Gb/sec if the Slotline cable were to be replaced with high bandwidth cabling.

Although the invention has been described in language specific to computer structural features, methodological acts, and by computer readable media, it is to be understood that the invention defined in the appended claims is not necessarily limited to the specific structures, acts, or media described. Therefore, the specific structural features, acts and mediums are disclosed as exemplary embodiments implementing the claimed invention.

Furthermore, the various embodiments described above are provided by way of illustration only and should not be construed to limit the invention. Those skilled in the art will readily recognize various modifications and changes that may be made to the claimed invention without following the example embodiments and applications illustrated and described herein, and without departing from the true spirit and scope of the claimed invention, which is set forth in the following claims.

Claims

1. A gaming system, comprising:

at least one backend server;

at least one gaming device; and

at least one distribution server, wherein each gaming device is in communication with at least one backend server through at least one distribution server.

2. A gaming system, comprising:

at least one backend server;

at least one gaming device; and

at least one data cache server, wherein each gaming device is in communication with at least one backend server through at least one data cache server whereby effects of asymmetrical dataflow is reduced.

3. A gaming network, comprising:

at least one gaming device; and

a core layer and a distribution layer; wherein each gaming device communicates with the core layer via the distribution layer.

4. A method of eliminating asymmetrical data flow in a gaming network, comprising:

establishing a backend server;

establishing one or more gaming devices;

establishing a distribution server; and

transmitting data between the gaming devices and the backend server through the distribution server.

5. In a gaming network, the improvement comprising:

distribution server means for caching data, whereby offload processing and network efficiency are enhanced.

6. In a gaming network, an improvement comprising:

a data cache means for caching data between a gaming device and a backend server, whereby offload processing and network efficiency are enhanced.

7. In a gaming network, an improvement comprising:

distribution server means for caching data, whereby asymmetrical data flow is minimized between a gaming device and a backend server.