Architecture for manufacturing authenticatable gaming systems

<u style="single">TECHNICAL FIELD</u>

This invention relates to console-based gaming systems, and more particularly, to systems and methods for manufacturing game consoles that can be authenticated for participation in online services such as online gaming.

<u style="single">BACKGROUND</u>

Traditionally, gaming systems with a dedicated console were standalone machines that accommodated a limited number of players (e.g., 4). PC-based gaming grew in popularity in part due to the ability to play games online with many remote players over a network (e.g., the Internet). Thus, one trend for dedicated gaming systems is to provide broadband capabilities to facilitate online gaming.

Creating an online gaming architecture for dedicated consoles poses several unique and difficult problems. One problem is that there are a number of hackers that constantly attempt to cheat during online games to gain various gaming advantages. To defeat this cheating, various security schemes are deployed to protect the data being transmitted over the network from hacker observation and/or modification. Such schemes, however, require the game console to authenticate itself with a remote entity (e.g., online gaming server, registration server, other player system, etc.). Valid credentials are used during authentication to guarantee authenticity of network traffic during gaming. If these credentials could be easily obtained during registration, a hacker could easily manipulate the credentials and forge all network packets from the video game console using another computer. From the game server's perspective, the gaming packets appear to be authentic since it came from a network source that was capable of providing the required credentials.

Accordingly, to secure online gaming and other services, there is a need to prevent hackers from easily obtaining valid credentials for purposes of cheating or other improper uses.

<u style="single">SUMMARY</u>

An architecture for manufacturing console-based gaming systems involves placing pre-established secrets on a game console during manufacturing and subsequently using the secrets to guarantee the authenticity of the game console during registration time.

Two representative implementations are described: a symmetric key architecture and a public key architecture. The former architecture involves writing a randomly generated symmetric key, along with a console ID, into programmatically accessible non volatile memory of the game console during manufacturing. The symmetric key is encrypted using a public key during transport. The corresponding private key, and the encrypted symmetric key, are securely maintained at an authentication entity.

During registration, the game console submits the key (or proof of key knowledge) and the console ID pair to the authentication entity. The pair functions as a password/name pair to locate the corresponding symmetric key maintained at the authentication entity. The private key is then used to decrypt the symmetric key. The key submitted by the game console is evaluated against the recovered symmetric key as a way to determine whether the console is authentic.

The public key architecture involves writing a private key and a digital certificate into each game console during manufacturing. The certificate contains the public key corresponding to the private key. The certificate is part of a certificate chain that includes a certification authority certificate associated with a certification authority at each manufacturing site and a root certificate from which the certification authority certificate is derived. Whenever a game console goes online for registration, a certificate chain verification process along with proof of knowledge of the private key stored on the game console are used to authenticate the console as genuine.

<u style="single">BRIEF DESCRIPTION OF THE DRAWINGS</u>

<ul id="ul0001" list-style="none" compact="compact"><li>Fig. 1 illustrates a gaming system with a game console and one or more controllers.</li><li>Fig. 2 is a block diagram of the gaming system.</li><li>Fig. 3 illustrates a network gaming system in which the Fig. 1 gaming system is connected via a network to other consoles, services, and a ticket issuing entity.</li><li>Fig. 4 illustrates a manufacturing process in which a symmetric key and a console ID are placed on the game console during manufacturing.</li><li>Fig. 5 illustrates a registration process in which an authentication server authenticates the game console using the symmetric key and console ID.</li><li>Fig. 6 illustrates a pre-manufacturing process in which public key pairs and chained certificates are initially generated.</li><li>Fig. 7 illustrates a manufacturing process in which a private key and one or more certificates are placed on the game console during manufacturing.</li><li>Fig. 8 illustrates a registration process in which the authentication server authenticates the game console using the private key and a certificate verification process.</li></ul>

<u style="single">DETAILED DESCRIPTION</u>

The following discussion is directed to console-based gaming systems with online connectivity and techniques for manufacturing such gaming systems in a manner that they can be authenticated by a remote authentication entity over an open network, such as the Internet. The techniques address the problem of how the authentication entity can be assured that the entity on the other side of the network is an authorized gaming system.

The discussion assumes that the reader is familiar with basic cryptography principles, such as encryption, decryption, authentication, hashing, digital signatures, and digital certificates. For a basic introduction to cryptography, the reader is directed to a text written by <nplcit id="ncit0001" npl-type="s"><text>Bruce Schneier and entitled, "Applied Cryptography: Protocols, Algorithms, and Source Code in C," published by John Wiley &amp; Sons, copyright 1994</text></nplcit> (second edition 1996), which is hereby incorporated by reference.

<u style="single">Gaming System</u>

Fig. 1 shows an exemplary gaming system 100. It includes a game console 102 and up to four controllers, as represented by controllers 104(1) and 104(2). The game console 102 is equipped with an internal hard disk drive and a portable media drive 106 that supports various forms of portable storage media as represented by optical storage disc 108. Examples of suitable portable storage media include DVD, CD-ROM, game discs, game cartridges, and so forth.

The game console 102 has four slots 110 on its front face to support up to four controllers, although the number and arrangement of slots may be modified. A power button 112 and an eject button 114 are also positioned on the front face of the game console 102. The power button 112 switches power to the game console and the eject button 114 alternately opens and closes a tray of the portable media drive 106 to allow insertion and extraction of the storage disc 108.

The game console 102 connects to a television or other display (not shown) via AN interfacing cables 120. A power cable 122 provides power to the game console. The game console 102 may further be configured with broadband capabilities, as represented by the cable or modem connector 124 to facilitate access to a network, such as the Internet.

Each controller 104 is coupled to the game console 102 via a wire or wireless interface. In the illustrated implementation, the controllers are USB (Universal Serial Bus) compatible and are connected to the console 102 via serial cables 130. The controller 102 may be equipped with any of a wide variety of user interaction mechanisms. As illustrated in Fig. 1, each controller 104 is equipped with two thumbsticks 132(1) and 132(2), a D-pad 134, buttons 136, and two triggers 138. These mechanisms are merely representative, and other known gaming mechanisms may be substituted for or added to those shown in Fig. 1.

A memory unit (MU) 140 may be inserted into the controller 104 to provide additional and portable storage. Portable memory units enable users to store game parameters and port them for play on other consoles. In the described implementation, each controller is configured to accommodate two memory units 140, although more or less than two units may be employed in other implementations.

The gaming system 100 is capable of playing, for example, games, music, and videos. With the different storage offerings, titles can be played from the hard disk drive or the portable medium 108 in drive 106, from an online source, or from a memory unit 140. A sample of what the gaming system 100 is capable of playing back include: <ol id="ol0001" compact="compact" ol-style=""><li>1. Game titles played from CD and DVD discs, from the hard disk drive, or from an online source.</li><li>2. Digital music played from a CD in the portable media drive 106, from a file on the hard disk drive (e.g., Windows Media Audio (WMA) format), or from online streaming sources.</li><li>3. Digital audio/video played from a DVD disc in the portable media drive 106, from a file on the hard disk drive (e.g., Active Streaming Format), or from online streaming sources.</li></ol>

Fig. 2 shows functional components of the gaming system 100 in more detail. The game console 102 has a central processing unit (CPU) 200 and a memory controller 202 that facilitates processor access to various types of memory, including a flash ROM (Read Only Memory) 204, a RAM (Random Access Memory) 206, a hard disk drive 208, and the portable media drive 106. The CPU 200 is equipped with a level 1 cache 210 and a level 2 cache 212 to temporarily store data and hence reduce the number of memory access cycles, thereby improving processing speed and throughput.

The CPU 200, memory controller 202, and various memory devices are interconnected via one or more buses, including serial and parallel buses, a memory bus, a peripheral bus, and a processor or local bus using any of a variety of bus architectures. By way of example, such architectures can include an Industry Standard Architecture (ISA) bus, a Micro Channel Architecture (MCA) bus, an Enhanced ISA (EISA) bus, a Video Electronics Standards Association (VESA) local bus, and a Peripheral Component Interconnects (PCI) bus.

As one suitable implementation, the CPU 200, memory controller 202, ROM 204, and RAM 206 are integrated onto a common module 214. In this implementation, ROM 204 is configured as a flash ROM that is connected to the memory controller 202 via a PCI (Peripheral Component Interconnect) bus and a ROM bus (neither of which are shown). RAM 206 is configured as multiple DDR SDRAM (Double Data Rate Synchronous Dynamic RAM) that are independently controlled by the memory controller 202 via separate buses (not shown). The hard disk drive 208 and portable media drive 106 are connected to the memory controller via the PCI bus and an ATA (AT Attachment) bus 216.

A 3D graphics processing unit 220 and a video encoder 222 form a video processing pipeline for high speed and high resolution graphics processing. Data is carried from the graphics processing unit 220 to the video encoder 222 via a digital video bus (not shown). An audio processing unit 224 and an audio codec (coder/decoder) 226 form a corresponding audio processing pipeline with high fidelity and stereo processing. Audio data is carried between the audio processing unit 224 and the audio codec 226 via a communication link (not shown). The video and audio processing pipelines output data to an A/V (audio/video) port 228 for transmission to the television or other display. In the illustrated implementation, the video and audio processing components 220-228 are mounted on the module 214.

Also implemented on the module 214 are a USB host controller 230 and a network interface 232. The USB host controller 230 is coupled to the CPU 200 and the memory controller 202 via a bus (e.g., PCI bus) and serves as host for the peripheral controllers 104(1)-104(4). The network interface 232 provides access to a network (e.g., Internet, home network, etc.) and may be any of a wide variety of various wire or wireless interface components including an Ethernet card, a modem, a Bluetooth module, a cable modem, and the like.

The game console 102 has two dual controller support subassemblies 240(1) and 240(2), with each subassembly supporting two game controllers 104(1)-104(4). A front panel I/O subassembly 242 supports the functionality of the power button 112 and the eject button 114, as well as any LEDs (light emitting diodes) or other indicators exposed on the outer surface of the game console. The subassemblies 240(1), 240(2), and 242 are coupled to the module 214 via one or more cable assemblies 244.

Eight memory units 140(1)-140(8) are illustrated as being connectable to the four controllers 104(1)-104(4), i.e., two memory units for each controller. Each memory unit 140 offers additional storage on which games, game parameters, and other data may be stored. When inserted into a controller, the memory unit 140 can be accessed by the memory controller 202.

A system power supply module 250 provides power to the components of the gaming system 100. A fan 252 cools the circuitry within the game console 102.

A console user interface (UI) application 260 is stored on the hard disk drive 208. When the game console is powered on, various portions of the console application 260 are loaded into RAM 206 and/or caches 210, 212 and executed on the CPU 200. The console application 260 presents a graphical user interface that provides a consistent user experience when navigating to different media types available on the game console.

The game console 102 implements a cryptography engine to perform common cryptographic functions, such as encryption, decryption, authentication, digital signing, hashing, and the like. The cryptography engine may be implemented as part of the CPU 200, or in software stored on the hard disk drive 208 that executes on the CPU, so that the CPU is configured to perform the cryptographic functions.

The gaming system 100 may be operated as a standalone system by simply connecting the system to a television or other display. In this standalone mode, the gaming system 100 allows one or more players to play games, watch movies, or listen to music. However, with the integration of broadband connectivity made available through the network interface 232, the gaming system 100 may further be operated as a participant in a larger network gaming community. This network gaming environment is described next.

<u style="single">Network Gaming</u>

Fig. 3 shows an exemplary network gaming environment 300 that interconnects multiple gaming systems 100(1), ..., 100(g) via a network 302. The network 302 represents any of a wide variety of data communications networks. It may include public portions (e.g., the Internet) as well as private portions (e.g., a residential Local Area Network (LAN)), as well as combinations of public and private portions. Network 302 may be implemented using any one or more of a wide variety of conventional communications media including both wired and wireless media. Any of a wide variety of communications protocols can be used to communicate data via network 302, including both public and proprietary protocols. Examples of such protocols include TCP/IP, IPX/SPX, NetBEUI, etc.

In addition to gaming systems 100, one or more data centers may be accessible via the network 302 to provide various services for participants. An exemplary data center 304 is illustrated as comprising an authentication server 306 that registers individual gaming systems 100 and one or more online servers 308(1), ..., 308(s) to provide various services, such as hosting online games, serving downloadable music or video files, hosting gaming competitions, serving streaming audio/video files, and the like. The authentication server 306 has access to a database 310 that stores manufacturing secrets placed on individual gaming systems during manufacturing. These secrets are used for registering or authenticating the gaming systems prior to allowing the gaming systems to participate in online gaming or other services.

While the authentication server 306, online servers 308, and database 310 are logically grouped as forming the data center 304, it is noted that the various computer systems may or may not be physically located together or as part of the same facility. Additionally, while the authentication server 306 is illustrated separately from the online servers 308, the authentication functionality may be integrated as part of the services.

The network gaming environment 300 may further involve a key distribution center 312 that plays a role in authenticating individual players and/or gaming systems 100 to one another as well as online services 304. The distribution center 312 distributes keys and service tickets to valid participants that may then be used to form games amongst multiple players or to purchase services from the online services 308. The distribution center 312 may be integrated into the data center 304 or reside independently, as shown.

To participate in online gaming (or other network services), the gaming systems 100 first seek to be authenticated by the authentication server 306. To grant permission to participate in online services, the authentication server 306 needs to trust that each gaming system is genuine and not an imposter computing device. Authentic gaming systems 100 are manufactured with secrets that are stored in the database 310. The authentication server 306 uses these secrets to discern whether the gaming system 100 is genuine. The techniques for manufacturing gaming systems that can be authenticated for online gaming over an open network, such as the Internet, are described in the next section.

Once authenticated, the gaming systems can participate in online gaming or other services, or proceed to authenticate individual users with the key distribution center. A multi-user authentication architecture is described in more detail in <patcit id="pcit0001" dnum="US802795A"><text>U.S. Patent Application Serial No. 09/802,795</text></patcit>, entitled "Multiple User Authentication for Online Console-Based Gaming", which was filed March 9, 2001. This application is assigned to Microsoft Corporation and is hereby incorporated by reference.

<u style="single">Manufacturing Authenticatable Gaming Systems</u>

An architecture for manufacturing gaming systems is provided to address the console authentication problem. Simply stated, the problem is how an authentication entity can be assured that the entity on the other side of the network is an authentic game console. The architecture generally involves storing secret, authenticatable data on the game console during manufacturing and maintaining corresponding verifying data at the authentication entity. During registration, the authentication entity uses the verifying data to verify the authenticatable data submitted by the game console to determine the authenticity of the game console. Two representative architectures are described: (1) a symmetric key architecture and (2) a public key architecture.

Symmetric Key Architecture

The symmetric key architecture involves writing a randomly generated symmetric key, along with a console ID, on the game console during manufacturing. This key/ID pair subsequently functions as a password/name pair during registration to prove to the authentication server that the game console is authentic. The architecture is described with reference to Figs. 4 and 5, where Fig. 4 illustrates the manufacturing process and Fig. 5 illustrates the registration process.

Fig. 4 shows an exemplary manufacturing process 400 in which a symmetric key and a console ID are placed on the game console during manufacturing. For discussion purposes, the manufacturer operates one or more manufacturing facilities, each of which includes one or more manufacturing computing systems 450 and databases 452. The manufacturing databases are sometimes referred to as "genealogy databases". The manufacturing computing systems 450 are used to program, configure, or otherwise enable the software/firmware being placed in the game consoles.

At operation 402, a unique identifier Ni is assigned for each manufactured console 102(i). The console ID could be, for example, a sequential number or the serial number of the manufactured console. At operation 404, a symmetric key Ki is randomly generated for console 102(i). At operation 406, the symmetric key Ki and the console identifier Ni are stored in a programmatically accessible non volatile memory of the console 102(i). The location of storage is preferably secure and/or secret from access by the game console owner, but is otherwise programmatically accessible by authorized game code. The possible locations include, but are not limited to, an EEPROM, the hard drive, or flash ROM. The Ki/Ni pair may also be cryptographically protected to further prevent access by the game console owner.

The Ki/Ni pair will be used during the registration process to prove to the authenticity of the game console. Accordingly, the Ki/Ni pair is collected during manufacturing for transport to the data center 304 that is responsible for registering the game console. However, the transportation and storage of the key/ID pair introduce potential risks of discovery. To secure the symmetric keys for storage and transportation, the symmetric key is encrypted with a transportation public key Kt_pub right after the symmetric key Ki is generated and stored in the game console (operation 408). The corresponding transportation private key Kt_prv, which is used to decrypt and access the symmetric key Ki, is securely maintained at the data center 304 and is only accessed when used during registration of a game console.

It is noted that one or more of the operations 404-408 may be performed by the manufacturing computing systems 450, or alternatively by the game consoles themselves. Regardless of where the key Ki is generated and encrypted, the goal is to have the key exist in its raw state for as short of time as possible. Minimizing this time will further enhance security.

It is further noted that the symmetric key Ki may be encrypted using cryptographic ciphers other than public key ciphers. For instance, the symmetric key Ki may be encrypted using a symmetric key cipher, where the symmetric key is securely maintained at the manufacturer and the data center.

At operation 410, the encrypted symmetric key (denoted as E(Kt_pub, Ki)) is stored in the manufacturer database 452 along with the console identifier Ni. At operation 412, the console identifier Ni and the encrypted symmetric key E(Kt_pub, Ki) for all manufactured consoles are transferred, individually or in batch, from the manufacturer database 452 to the data center 304. The information may be transferred according to any number of different techniques, including electronic transmission over a network, secure portage on a portable storage media, or by other means.

At this point, the game consoles are finished being manufactured and are packaged for distribution and sale. After the game consoles are purchased, the owners may wish to participate in an online service, such as gaming or downloading audio/video files. When the game consoles initially encounter an online service, the game consoles perform a registration process to prove its authenticity to the online service. For discussion purposes, suppose the game console registers with the authentication server 306 of the data center 304 to enable participation in an online gaming event being hosted by one or more online servers 308.

Fig. 5 shows an exemplary registration process 500 in which the authentication server 306 at the data center 304 authenticates the game console 102(i). At operation 502, the console 102(i) submits the symmetric key (or proof of key knowledge) and the console ID pair (e.g., Ki, Ni) to the authentication server 306 at the data center 304 as part of an authentication protocol. The symmetric key Ki is usually protected in some manner during the authentication protocol, while the console identifier Ni need not be. Many different authentication protocols can be used during this operation, including (but not limited to) Kerberos, Digest, and HTTP Basic. The communication over the network can all be optionally secured within a secure channel (e.g., SSL channel).

At operation 504, the authentication server 306 uses the console identifier Ni to lookup the associated symmetric key in the manufacturer's secrets database 310. The result of the lookup produces a data record 520 for console 102(i). The data record 520 includes the encrypted symmetric key E(Kt_pub, Ki) originally created by and transferred from the manufacturer in the manufacturing process 400 of Fig. 4. At operation 506, the authentication server 306 decrypts the symmetric key using the transportation private key Kt_prv stored at the authentication server 306 to recover the symmetric key Ki.

At operation 508, the authentication server 306 verifies the credentials submitted by the game console 102(i) by, in part, comparing the submitted key Ki (or proof of its knowledge) with the manufacturer-assigned symmetric key Ki recovered from the record 520 in the manufacturer's secrets database 310. The authentication server either accepts or rejects the game console based on whether the authentication succeeds or fails, which is based at least in part on whether the two keys match.

At this point, the results of the authentication could be used to directly allow/disallow participation in online services. In this case, the symmetric keys are used each time the game console requests authentication for purposes of participating in online services. Alternatively, the results of the authentication could be used to bootstrap a new credential process in which a new set of credentials are generated and transported back to the game console for use later during online service authentication. In this second case, the Ki/Ni pair is used only once for authentication during registration of the game console and the registration process will return a new set of credentials to the console that can be used from then on.

The advantage of the symmetric key architecture is that no secrets are maintained at the manufacturer. The secret transportation private key is kept at the data center. Thus, the opportunity for a cheater to steal the secret is greatly diminished.

Public Key Architecture

The public key architecture involves writing a private key and a digital certificate into each game console during manufacturing. The certificate contains the public key that matches the private key. The certificate is signed by a certification authority placed at each manufacturing site. Each certification authority certificate is further signed by another certificate that eventually leads up a certificate chain to a root certificate. Whenever a game console goes online to register itself, a certificate chain verification process along with proof of knowledge of the private key are used to authenticate the console as genuine. The public key architecture is described with reference to Figs. 6-8, where Fig. 6 illustrates a pre-manufacturing process, Fig. 7 illustrates the manufacturing process, and Fig. 8 illustrates the registration process.

Fig. 6 shows an exemplary pre-manufacturing process 600 in which public key pairs and chained certificates are generated. The process 600 may be performed any time before the manufacturing of the game consoles 102. It may be performed at the manufacturing facility or elsewhere. At operation 602, a root public key pair consisting of a root public key Kroot_pub and a root private key Kroot_prv is generated. The root key pair is trusted and securely stored.

At operation 604, the root key pair is used to generate a root certificate CERT(Kroot_prv, Kroot_pub). The notation "CERT(Kroot_prv, Kroot_pub)" means that the root private key Kroot_prv is used to digitally sign a composite of the root public key Kroot_pub and a purpose statement vouching for the authenticity of the root public key for anyone knowing the corresponding root private key. Thus, anybody with access to the root public key Kroot_pub should be able to verify the authenticity of the certificate. One example type of certificate is an X.509 format certificate. However, other types of data structures that carry a public key signed by another private key can be considered a certificate.

At operation 606, a second public key pair is generated for use by a certification authority (CA) at the manufacturing site. This second key pair is referred to as the certification authority key pair (or CA key pair) and consists of a CA public key Kca_pub and a CA private key Kca_prv. If there is more than one certification authority at each manufacturing site, a different CA key pair is generated for each certification authority. Accordingly, each manufacturing site is associated with one or more CA key pairs.

At operation 608, a CA certificate for the certification authority is generated and signed by the root private key Kroot_prv. The CA certificate is designated as CERT(Kroot_prv, Kca_pub), meaning the root private key Kroot_prv is used to digitally sign a composite of the CA public key Kca_pub and a purpose statement vouching for the authenticity of the CA public key for anyone knowing the CA private key.

At operation 610, the CA certificate CERT(Kroot_prv, Kca_pub) and the CA private key are stored at the certification authority 650 at the manufacturing site. The CA certificate and the CA private key Kca_prv are securely maintained to prevent compromise. At operation 612, the root public key Kroot_pub and/or the root certificate CERT(Kroot_prv, Kroot_pub) is transported (if generated remotely) and securely stored to the data center 304.

Fig. 7 shows an exemplary manufacturing process 700 in which a private key and one or more certificates are placed on the game console during manufacturing. For purposes of manufacturing, the manufacturer maintains the CA public key pair (Kca_pub, Kca_prv) and the CA certificate CERT(Kroot_prv, Kca_pub).

At operation 702, a game console public key pair for each manufactured console 102(i) is generated. The console public key pair consists of a console public key Ki_pub and a console private key Ki_prv. At operation 704, a console certificate CERT(Kca_prv, Ki_pub) is generated and signed by the CA private key Kca_prv of the certification authority at the factory. The console certificate contains the console public key Ki_pub and vouches for its authenticity for anyone knowing the console private key Ki_prv.

At operation 706, the manufacturer records the console private key Ki_prv, the console certificate CERT(Kca_prv, Ki_pub), and CA certificate CERT(Kroot_prv, Kca_pub) into the game console. The location in storage is such that the key and certificates are programmatically accessible by authorized game code, but secure from being accessed by the game console owner. The possible locations include, but are not limited to, an EEPROM, hard drive, or flashable ROM. While the CA private key Kca_prv is secured at the manufacturing site, all other information including public keys and certificates can be freely distributed without security measures.

Fig. 8 shows an exemplary registration process 800 in which the game console is authenticated by the authentication server 306 at the data center 304. Many different public key authentication protocols can be employed to implement the registration process. At the time of registration, the authentication server 306 has access to the root certificate (and thus root public key).

At operation 802, as part of one suitable protocol, the console 102(i) sends the console certificate CERT(Kca_prv, Ki_pub) to the authentication server 306 at the data center 304. The console may optionally send the CA certificate CERT(Kroot_prv, Kca_pub) if the authentication server does not already possess the CA certificate CERT(Kroot_prv, Kca_pub). The console also submits some proof that it knows the console private key Ki_prv. This proof can be achieved in many ways. One approach for providing such proof is to encrypt some data using the console private key Ki_prv. This data may be, for example, the current time, a random number, a message, etc. For purposes of continuing discussion, assume the console encrypts the current time with the console private key; or E(Ki_prv, CurrentTime). Using the current time can help thwart replay attacks.

Next, the authentication server 306 performs a certificate chain authentication process to traverse the certificate chain out to the console certificate. More specifically, at operation 804, the authentication server 306 authenticates the CA certificate CERT(Kroot_prv, Kca_pub) by verifying the signature of the CA certificate using root public key Kroot_pub. The root public key may be stored at the authentication server or extracted from the root certificate CERT(Kroot_prv, Kroot_pub). At operation 806, the authentication server 306 obtains the CA public key Kca_pub from the CA certificate and uses it to verify the signature of the console certificate CERT(Kca_prv, Ki_pub), thereby authenticating the console certificate.

At operation 808, the authentication server 306 uses the console public key Ki_pub retrieved from the console certificate to evaluate the proof of knowledge of the console private key Ki_prv. If the authentication server 306 can verify via the submitted proof that the console has knowledge of the correct console private key, the game console 102(i) is trusted to be genuine. In our example of using current time, the authentication server employs the console public key to decrypt the encrypted current time submitted by the console. The recovered current time is verified to be within an acceptable time skew. The game server either accepts or rejects the game console based on whether the authentication succeeds or fails, which is based at least in part on whether the recovered time is within the time skew.

At this point, the results of the authentication could be used to directly allow/disallow participation in online services. In this case, the same registration process is used each time the game console requests authentication for purposes of participating in online services. Alternatively, the results of the authentication could be used to bootstrap a new credential process in which a new set of credentials are generated and transported back to the game console for use later during online service authentication. In this second case, the console private key Ki_prv, the console certificate CERT(Kca_prv, Ki_pub), and the CA certificate CERT(Kroot_prv, Kca_pub) credentials are used only once for authentication during registration and the registration process will return a new set of credentials to the console that can be used from then on.

It is noted that the public key architecture described herein employs two levels of certificate chaining from the root certificate to the console certificate. More or fewer levels of certificate chaining may be used to deploy the architecture.

The advantage of the public key architecture is that no transfer of keys takes place between the console manufacturing sites and the authentication server at the data center. However, with the public key architecture, secrets are maintained at the manufacturer.

<u style="single">Conclusion</u>

Although the invention has been described in language specific to structural features and/or methodological acts, it is to be understood that the invention defined in the appended claims is not necessarily limited to the specific features or acts described. Rather, the specific features and acts are disclosed as exemplary forms of implementing the claimed invention.

The following is a list of further preferred embodiments of the invention:

<ul id="ul0002" list-style="none"><li>Embodiment 1: A method comprising: <ul id="ul0003" list-style="none" compact="compact"><li>manufacturing a console-based gaming system with authenticatable data stored in programmatically accessible memory, the authenticatable data having corresponding verification data; and</li><li>authenticating the console-based gaming system for online participation by receiving the authenticatable data from the console-based gaming system and utilizing the verification data to verify the authenticatable data.</li></ul></li><li>Embodiment 2: A method as recited in embodiment 1, wherein the authenticatable data comprises a symmetric key used in a symmetric cryptographic cipher.</li><li>Embodiment 3: A method as recited in embodiment 1, wherein the authenticatable data comprises a private key used in a public key cryptographic cipher.</li><li>Embodiment 4: A method as recited in embodiment 1, wherein the manufacturing comprises: <ul id="ul0004" list-style="none" compact="compact"><li>storing a symmetric key and a console ID in the console-based gaming system;</li><li>encrypting the symmetric key to produce an encrypted symmetric key; and</li><li>storing the encrypted symmetric key and the console ID at an authentication entity employed to authenticate the console-based gaming system.</li></ul></li><li>Embodiment 5: A method as recited in embodiment 4, wherein the encrypting comprises encrypting the symmetric key using a public key cipher and a public key from a public key pair.</li><li>Embodiment 6: A method as recited in embodiment 4, wherein the encrypting comprises encrypting the symmetric key using a symmetric key cipher.</li><li>Embodiment 7: A method as recited in embodiment 4, wherein the authenticating comprises: <ul id="ul0005" list-style="none" compact="compact"><li>receiving the symmetric key and the console ID from the console-based gaming system;</li><li>using the console ID to locate the encrypted symmetric key at the authentication entity;</li><li>decrypting the encrypted symmetric key using the public key cipher and a corresponding private key from the public key pair to recover the symmetric key; and</li><li>evaluating the symmetric key recovered from the encrypted symmetric key with the symmetric key received from the console-based gaming system as a basis for authenticating the console-based gaming system.</li></ul></li><li>Embodiment 8: A method as recited in embodiment 1, wherein the manufacturing comprises: <ul id="ul0006" list-style="none" compact="compact"><li>storing, on the console-based gaming system, a console private key unique to the console-based gaming system and at least one console certificate that is part of a certificate chain chaining from a root certificate signed by a root private key, to the console certificate containing a console public key that corresponds to the console private key; and</li><li>storing the root public key at an authentication entity employed to authenticate the console-based gaming system.</li></ul></li><li>Embodiment 9: A method as recited in embodiment 8, wherein the authenticating comprises: <ul id="ul0007" list-style="none" compact="compact"><li>receiving the console certificate and proof of knowledge of the console private key from the console-based gaming system;</li><li>traversing the certificate chain to verify the console certificate and recover the console public key; and</li><li>using the console public key to evaluate the proof of knowledge of the console private key.</li></ul></li><li>Embodiment 10: One or more computer-readable media comprising computer-executable instructions that, when executed, perform the method as recited in embodiment 1.</li><li>Embodiment 11: A method comprising: <ul id="ul0008" list-style="none" compact="compact"><li>manufacturing a game console that includes a symmetric key stored in programmatically accessible memory; and</li><li>using symmetric key cryptography to verify the symmetric key on the game console as a basis for authenticating the game console for online participation.</li></ul></li><li>Embodiment 12: A method as recited in embodiment 11, wherein the manufacturing comprises: <ul id="ul0009" list-style="none" compact="compact"><li>encrypting the symmetric key to produce an encrypted symmetric key; and</li><li>maintaining the encrypted symmetric key at an authentication entity employed to authenticate the game console.</li></ul></li><li>Embodiment 13: A method as recited in embodiment 12, wherein the using comprises: <ul id="ul0010" list-style="none" compact="compact"><li>receiving a proffered symmetric key from the game console;</li><li>decrypting the encrypted symmetric key maintained at the authentication entity; and</li><li>evaluating the symmetric key recovered from the encrypted symmetric key with the proffered symmetric key received from the game console.</li></ul></li><li>Embodiment 14: A method as recited in embodiment 11, wherein the manufacturing comprises: <ul id="ul0011" list-style="none" compact="compact"><li>encrypting the symmetric key using a public key cipher and a public key from a public key pair to produce an encrypted symmetric key; and</li><li>maintaining the encrypted symmetric key at an authentication entity employed to authenticate the game console.</li></ul></li><li>Embodiment 15: A method as recited in embodiment 14, wherein the using comprises: <ul id="ul0012" list-style="none" compact="compact"><li>receiving a proffered symmetric key from the game console;</li><li>decrypting the encrypted symmetric key maintained at the authentication entity using the public key cipher and a private key from the public key pair to recover the symmetric key; and</li><li>evaluating the symmetric key recovered from the encrypted symmetric key with the proffered symmetric key received from the game console.</li></ul></li><li>Embodiment 16: A method comprising: <ul id="ul0013" list-style="none" compact="compact"><li>manufacturing a game console that stores a verifiable certificate and a private key from a public key pair in programmatically accessible memory; and</li><li>using public key cryptography to verify the verifiable certificate and the private key of the game console as a basis for authenticating the game console for online participation.</li></ul></li><li>Embodiment 17: A method as recited in embodiment 16, wherein the manufacturing comprises: <ul id="ul0014" list-style="none" compact="compact"><li>generating a root public key pair having a root public key and a corresponding root private key;</li><li>generating a certificate chain from a root certificate signed by the root private key to the verifiable certificate, the verifiable certificate containing a corresponding public key from the public key pair; and</li><li>writing the verifiable certificate and the private key into the programmatically accessible memory.</li></ul></li><li>Embodiment 18: A method as recited in embodiment 17, wherein the using comprises: <ul id="ul0015" list-style="none" compact="compact"><li>receiving the verifiable certificate and proof of knowledge of the private key from the game console;</li><li>traversing the certificate chain to verify the verifiable certificate and recover the public key; and</li><li>using the public key to evaluate the proof of knowledge of the private key.</li></ul></li><li>Embodiment 19: A method for manufacturing a game console, comprising: <ul id="ul0016" list-style="none" compact="compact"><li>writing a symmetric key in programmatically accessible memory in the game console;</li><li>encrypting the symmetric key to produce an encrypted symmetric key; and</li><li>maintaining the encrypted symmetric key in a database separate from the game console.</li></ul></li><li>Embodiment 20: A method as recited in embodiment 19, wherein the encrypting comprises encrypting the symmetric key using a public key cipher and a public key of a public key pair.</li><li>Embodiment 21: A method as recited in embodiment 19, wherein the encrypting comprises encrypting the symmetric key using a symmetric key cipher.</li><li>Embodiment 22: A method as recited in embodiment 19, further comprising randomly generating the symmetric key.</li><li>Embodiment 23: A method as recited in embodiment 19, further comprising: <ul id="ul0017" list-style="none" compact="compact"><li>assigning a console ID to each game console;</li><li>writing the console ID in the programmatically accessible memory; and</li><li>maintaining the console ID in the database in association with the encrypted symmetric key.</li></ul></li><li>Embodiment 24: A method as recited in embodiment 19, further comprising transferring the encrypted symmetric key to a data center that is used to authenticate the game console.</li><li>Embodiment 25: One or more computer-readable media comprising computer-executable instructions that, when executed, perform the method as recited in embodiment 19.</li><li>Embodiment 26: A method for registering a game console, comprising: <ul id="ul0018" list-style="none" compact="compact"><li>receiving a symmetric key and a console ID from the game console;</li><li>locating a record using the console ID, the record containing an encrypted symmetric key in which an original symmetric key assigned to the game console during manufacturing is encrypted;</li><li>decrypting the encrypted symmetric key found in the record; and</li><li>evaluating the original symmetric key recovered from the encrypted symmetric key with the symmetric key received from the game console as a basis for authenticating the game console.</li></ul></li><li>Embodiment 27: A method as recited in embodiment 26, wherein the original symmetric key is encrypted using a public key cipher and a public key of a public key pair and the decrypting comprises decrypting the symmetric key using the public key cipher and a private key of the public key pair.</li><li>Embodiment 28: A method as recited in embodiment 26, wherein the original symmetric key is encrypted using a symmetric key cipher and the decrypting comprises decrypting the symmetric key using the symmetric key cipher.</li><li>Embodiment 29: One or more computer-readable media comprising computer-executable instructions that, when executed, perform the method as recited in embodiment 26.</li><li>Embodiment 30: A method comprising: <ul id="ul0019" list-style="none" compact="compact"><li>during manufacturing: assigning a console ID to each game console; randomly generating a symmetric key; storing the symmetric key and the console ID in programmatically accessible memory in the game console; encrypting the symmetric key using a public key of a public key pair to produce an encrypted symmetric key; maintaining the encrypted symmetric key and the console ID in a database; transferring the encrypted symmetric key and the console ID to a data center;</li><li>during registration of the game console at the data center: receiving a proffered symmetric key and the console ID from the game console; locating a record using the console ID received from the game console, the record containing the encrypted symmetric key; decrypting the encrypted symmetric key using the public key cipher and a private key from the public key pair to recover the symmetric key; and evaluating the symmetric key recovered from the encrypted symmetric key with the proffered symmetric key received from the game console as a basis for authenticating the game console.</li></ul></li><li>Embodiment 31: A method for manufacturing a game console, comprising: <ul id="ul0020" list-style="none" compact="compact"><li>generating a console public key pair associated with a game console, the console public key pair having a console public key and a corresponding console private key;</li><li>creating a certificate chain of digital certificates starting from a root certificate signed by a root private key and ending at a console certificate, the console certificate containing the console public key; and</li><li>storing the console certificate and the console private key in programmatically accessible memory in the game console.</li></ul></li><li>Embodiment 32: A method as recited in embodiment 31, wherein the certificate chain further includes a certification authority (CA) certificate intermediate of the root certificate and the console certificate, the CA certificate being signed by the root private key and containing a CA public key from a CA public key pair, the CA public key pair having a corresponding CA private key that is used to sign the console certificate.</li><li>Embodiment 33: One or more computer-readable media comprising computer-executable instructions that, when executed, perform the method as recited in embodiment 31.</li><li>Embodiment 34: A method for registering a game console, comprising: <ul id="ul0021" list-style="none" compact="compact"><li>receiving a console certificate and proof of knowledge of a console private key from the game console, the console certificate being part of a certificate chain starting from a root certificate digitally signed by a root private key of a public key pair, and ending at a console certificate containing a console public key that corresponds to the console private key in a console public key pair;</li><li>traversing the certificate chain to verify the console certificate and recover the console public key; and</li><li>using the console public key to evaluate the proof of knowledge of the console private key received from the game console.</li></ul></li><li>Embodiment 35: One or more computer-readable media comprising computer-executable instructions that, when executed, perform the method as recited in embodiment 34.</li><li>Embodiment 36: A method comprising: <ul id="ul0022" list-style="none" compact="compact"><li>prior to registration: generating a root public key pair having a root public key and a corresponding root private key; generating a root certificate that contains the root public key and is signed by the root private key; generating a certification authority (CA) public key pair having a CA public key and a corresponding CA private key; generating a CA certificate that contains the CA public key and is signed by the root private key; generating a console public key pair having a console public key and a corresponding console private key; generating a console certificate that contains the console public key and is signed by the CA private key; storing the console certificate and the console private key in programmatically accessible memory of a game console;</li><li>during registration: receiving the console certificate and proof of knowledge of the console private key from the game console; using the root public key to verify the CA certificate and recover the CA public key; using the CA public key to verify the console certificate and recover the console public key; and using the console public key to evaluate the proof of knowledge of the console private key received from the game console.</li></ul></li><li>Embodiment 37: A computer-readable medium comprising computer-executable instructions that, when executed, direct a computing system to: <ul id="ul0023" list-style="none" compact="compact"><li>write a randomly generated symmetric key and a console ID into a programmatically accessible memory in the game console;</li><li>encrypt the symmetric key to produce an encrypted symmetric key; and</li><li>store the encrypted symmetric key and the console ID in a database separate from the game console.</li></ul></li><li>Embodiment 38: A computer-readable medium as recited in embodiment 37, further comprising computer-executable instructions that, when executed, direct the computing system to encrypt the symmetric key using a public key of a public key pair.</li><li>Embodiment 39: A computer-readable medium as recited in embodiment 37, further comprising computer-executable instructions that, when executed, direct the computing system to transmit the symmetric key and /or proof of knowledge of the symmetric key and the console ID to a data center used to authenticate the game console.</li><li>Embodiment 40: A computer-readable medium comprising computer-executable instructions that, when executed, direct a computing system to: <ul id="ul0024" list-style="none" compact="compact"><li>receive a proffered symmetric key and a console ID from the game console;</li><li>retrieve, using the console ID, an original symmetric key recorded into the game console during manufacturing; and</li><li>compare the proffered symmetric key received from the game console with the original symmetric key to determine whether the game console is authentic.</li></ul></li><li>Embodiment 41: A computer-readable medium as recited in embodiment 40, wherein the copy of the symmetric key is encrypted and further comprising computer-executable instructions that, when executed, direct the computing system to decrypt the copy of the original symmetric key.</li><li>Embodiment 42: A computer-readable medium comprising computer-executable instructions that, when executed, direct a computing system to: <ul id="ul0025" list-style="none" compact="compact"><li>generate a root public key pair having a root public key and a corresponding root private key;</li><li>generate a certificate chain from a root certificate signed by the root private key to a console certificate associated with the game console, the console certificate containing a console public key from a console public key pair; and</li><li>write the console certificate and a console private key corresponding to the console public key in programmatically accessible memory of a game console.</li></ul></li><li>Embodiment 43: A computer-readable medium comprising computer-executable instructions that, when executed, direct a computing system to: <ul id="ul0026" list-style="none" compact="compact"><li>receive a console certificate and proof of knowledge of a console private key from the game console, the console certificate being part of a certificate chain starting from a root certificate digitally signed by a root private key of a public key pair, and ending at the console certificate containing a console public key that corresponds to the console private key;</li><li>traverse the certificate chain to verify the console certificate and recover the console public key; and</li><li>evaluate the proof of knowledge of the console private key received from the game console using the console public key recovered from the console certificate.</li></ul></li><li>Embodiment 44: A game console, comprising: <ul id="ul0027" list-style="none" compact="compact"><li>a network port for connection to a communication network;</li><li>a memory;</li><li>a symmetric key stored in the memory; and</li><li>a processor coupled to the memory and configured to retrieve the symmetric key from the memory and transmit the symmetric key and/or proof of knowledge of the symmetric key via the network port to an authentication entity that uses the symmetric key to authenticate the game console.</li></ul></li><li>Embodiment 45: A game console, comprising: <ul id="ul0028" list-style="none" compact="compact"><li>a network port for connection to a communications network;</li><li>a memory;</li><li>a private key and a verifiable certificate stored in the memory, the verifiable certificate containing a public key that corresponds to the private key; and</li><li>a processor coupled to the memory and configured to transmit the verifiable certificate and proof of knowledge of the private key via the network port to an authentication entity that uses the verifiable certificate and the proof to authenticate the game console.</li></ul></li><li>Embodiment 46: A system, comprising: <ul id="ul0029" list-style="none" compact="compact"><li>a manufacturing-based computing system configured to write authenticatable data into programmatically accessible memory of a game console, the authenticatable data having corresponding verification data maintained separately from the game console; and</li><li>an authentication computing system configured to authenticate the game console by receiving the authenticatable data from the game console and utilizing the verification data to verify the authenticatable data.</li></ul></li><li>Embodiment 47: A system, comprising: <ul id="ul0030" list-style="none" compact="compact"><li>a manufacturing-based computing system configured to write a randomly generated symmetric key and a console ID into a programmatically accessible memory in the game console, the manufacturing-based computing system further storing the symmetric key in encrypted form; and</li><li>an authentication computing system configured to authenticate the game console by receiving a proffered symmetric key and the console ID from the game console, the authentication computing system using the console ID to locate the symmetric key in encrypted form and then decrypting the symmetric key, the authentication computing system using the symmetric key to evaluate the proffered symmetric key received from the game console as a basis for authenticating the game console.</li></ul></li><li>Embodiment 48: A system, comprising: <ul id="ul0031" list-style="none" compact="compact"><li>a manufacturing-based computing system configured to write a console certificate and a console private key into programmatically accessible memory of the game console, the console certificate being part of a certificate chain starting from a root certificate signed by a root private key, leading to the console certificate containing a console public key associated with the console private key; and</li><li>an authentication computing system configured to authenticate the game console by verifying a proffered console certificate submitted by the game console using the certificate chain, the authentication computing system using the console public key from the console certificate to evaluate proof of knowledge of the console private key submitted by the game console.</li></ul></li><li>Embodiment 49: A system, comprising: <ul id="ul0032" list-style="none" compact="compact"><li>writing means for writing an original symmetric key and a console ID into programmatically accessible memory of a game console;</li><li>encryption means for encrypting the original symmetric key using a public key of a public key pair to produce an encrypted symmetric key;</li><li>storage means for maintaining the encrypted symmetric key separately from the game console; and</li><li>authentication means for authenticating the game console by comparing a proffered symmetric key submitted by the game console with the original symmetric key decrypted from the encrypted symmetric key to determine if the proposed symmetric key matches the original symmetric key.</li></ul></li><li>Embodiment 50: A system, comprising: <ul id="ul0033" list-style="none" compact="compact"><li>certificate generation means for generating a certificate chain from a root certificate signed by a root private key to a console certificate associated with a game console, the console certificate containing a console public key from a console public key pair;</li><li>writing means for writing the console certificate and a console private key from the console public key pair in programmatically accessible memory of the game console; and</li><li>authentication means for authenticating the game console by verifying a proffered console certificate submitted by the game console using the certificate chain and if valid, extracting the console public key from the console certificate to evaluate proof of knowledge of the console private key submitted by the game console.</li></ul></li></ul>

Important Note:

While the attached claims relate to a preferred aspect of the present invention, the applicant wishes to reserve the right to file one or several further divisional applications at a later point in time for other aspects disclosed in the application. Those further applications will be divided out from the present divisional application. By this statement, the public is herewith informed that more divisional applications relating to different subject matter may follow.