Game achievements system

Information

  • Patent Grant
  • 9355097
  • Patent Number
    9,355,097
  • Date Filed
    Wednesday, May 1, 2013
    11 years ago
  • Date Issued
    Tuesday, May 31, 2016
    8 years ago
Abstract
Systems and method for providing a game achievements system where players are rewarded with game achievements based on mastering certain in-game facets of the games they play. Each game achievement may be conveyed in a profile as a badge or trophy, title, description, date, etc. Players may also accumulate points based on game achievements. A display interface may be made available such that a player may see his achievements and total points, as well as those of others.
Description
COPYRIGHT NOTICE/PERMISSION

A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all copyright rights whatsoever. The following notice applies to the software and data as described below and in the drawings hereto: Copyright© 2004, Microsoft Corporation, All Rights Reserved.


FIELD OF THE INVENTION

This invention generally relates to the field of gaming and multimedia devices. In particular, the present invention is directed to a system and method of defining and creating game achievements that may be used to convey a player's skill.


BACKGROUND OF THE INVENTION

Conventional gaming systems include a concept of unique identity, which was intended to increase player satisfaction and create a sense of community. However, while the conventional unique identity does minimize the effort required to play online, the unique identity failed to accomplish these goals. One reason for this problem is that multiple players often share an identity because there is no easy way for multiple players to identify themselves on a shared gaming device. This creates confusion as a player using a particular identity during an online gaming session, may not be the same player in the next session or from the previous session.


Further, conventional identities have failed to provide a method for conveying information about players other than a limited set of game achievements and fail to convey information about offline achievements. Thus, it is difficult to learn more about a player through the conventional unique identity. Therefore, there is a need for a unique identity that is rich and includes game achievements from both offline and online contexts to convey a player's skill. Further, the achievements should be weighted such that excelling in more difficult games results in a higher achievement level. The present invention provides such a solution.


SUMMARY OF THE INVENTION

The present invention is directed to a system and methods for providing a game achievements system. In accordance with the present invention, players are rewarded with game achievements based on mastering certain in-game facets of the games they play. Each game achievement may be conveyed in a profile as a badge or trophy, title, description, date, etc. Players may also accumulate points based on game achievements. A display interface may be made available such that a player may see his achievements and total points, as well as those of others.


In accordance with an aspect of the invention, there is provided a method of providing a game achievements system in an online gaming environment. The method includes defining system achievements; receiving definitions of predetermined in-game achievements; tracking player activity to capture occurrences of the system achievements and the predetermined in-game achievements; and aggregating occurrences of the system achievements and the predetermined in-game achievements during game play into a profile associated with a user.


In accordance with features of the invention, the method may include assigning a predetermined number of points to each system achievement, aggregating the predetermined number of system achievement points into the profile, and maintaining an aggregate number of points for the profile. Also, the method may include assigning a predetermined number of points to each in-game achievement, and aggregating the predetermined number of in-game achievement points into the profile.


In accordance with the invention, the predetermined number of points may be a weighted valued based on a total number of points available. Further, the total number of points assigned to in-game achievements for a specified game may be determined in accordance with a difficulty of the specified game. However, it may be desirable to fix the total number of points assigned to the system achievements for all games.


A display user interface may be provided where the profile is published for viewing. The display may show the aggregate number of points within a profile.


In accordance with another aspect of the invention, there is provided a system for providing game achievements in an online gaming environment. The system includes an offline player achievement tracking mechanism that tracks offline player activity during periods when a player is not communicatively connected to the online gaming environment, an online player achievement tracking mechanism that tracks online player activity during online sessions with the online gaming environment, and an aggregation mechanism that receives data regarding offline player activity and the online player activity and aggregates the offline player activity and the online player activity into a player profile.


Additional features and advantages of the invention will be made apparent from the following detailed description of illustrative embodiments that proceeds with reference to the accompanying drawings.





BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing summary, as well as the following detailed description of preferred embodiments, is better understood when read in conjunction with the appended drawings. For the purpose of illustrating the invention, there is shown in the drawings exemplary constructions of the invention; however, the invention is not limited to the specific methods and instrumentalities disclosed. In the drawings:



FIG. 1 is a block diagram showing a gaming console in which aspects of the present invention may be implemented;



FIG. 2 illustrates an exemplary architecture in which the present invention may be implemented;



FIG. 3 illustrates sources of information that provide input to a Gamer Profile;



FIG. 4 illustrates an exemplary game achievements display user interface configuration;



FIG. 5 illustrates the aggregation of game achievements; and



FIG. 6 illustrates a developer user interface to specify in-game achievements.





DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS


FIG. 1 illustrates the functional components of a multimedia/gaming console 100 in which certain aspects of the present invention may be implemented. The multimedia console 100 has a central processing unit (CPU) 101 having a level 1 cache 102, a level 2 cache 104, and a flash ROM (Read Only Memory) 106. The level 1 cache 102 and a level 2 cache 104 temporarily store data and hence reduce the number of memory access cycles, thereby improving processing speed and throughput. The CPU 101 may be provided having more than one core, and thus, additional level 1 and level 2 caches 102 and 104. The flash ROM 106 may store executable code that is loaded during an initial phase of a boot process when the multimedia console 100 is powered ON.


A graphics processing unit (GPU) 108 and a video encoder/video codec (coder/decoder) 114 form a video processing pipeline for high speed and high resolution graphics processing. Data is carried from the graphics processing unit 108 to the video encoder/video codec 114 via a bus. The video processing pipeline outputs data to an A/V (audio/video) port 140 for transmission to a television or other display. A memory controller 110 is connected to the GPU 108 to facilitate processor access to various types of memory 112, such as, but not limited to, a RAM (Random Access Memory).


The multimedia console 100 includes an I/O controller 120, a system management controller 122, an audio processing unit 123, a network interface controller 124, a first USB host controller 126, a second USB controller 128 and a front panel I/O subassembly 130 that are preferably implemented on a module 118. The USB controllers 126 and 128 serve as hosts for peripheral controllers 142(1)-142(2), a wireless adapter 148, and an external memory device 146 (e.g., flash memory, external CD/DVD ROM drive, removable media, etc.). The network interface 124 and/or wireless adapter 148 provide access to a network (e.g., the Internet, home network, etc.) and may be any of a wide variety of various wired or wireless adapter components including an Ethernet card, a modem, a Bluetooth module, a cable modem, and the like.


System memory 143 is provided to store application data that is loaded during the boot process. A media drive 144 is provided and may comprise a DVD/CD drive, hard drive, or other removable media drive, etc. The media drive 144 may be internal or external to the multimedia console 100. Application data may be accessed via the media drive 144 for execution, playback, etc. by the multimedia console 100. The media drive 144 is connected to the I/O controller 120 via a bus, such as a Serial ATA bus or other high speed connection (e.g., IEEE 1394).


The system management controller 122 provides a variety of service functions related to assuring availability of the multimedia console 100. The audio processing unit 123 and an audio codec 132 form a corresponding audio processing pipeline with high fidelity and stereo processing. Audio data is carried between the audio processing unit 123 and the audio codec 132 via a communication link. The audio processing pipeline outputs data to the A/V port 140 for reproduction by an external audio player or device having audio capabilities.


The front panel I/O subassembly 130 supports the functionality of the power button 150 and the eject button 152, as well as any LEDs (light emitting diodes) or other indicators exposed on the outer surface of the multimedia console 100. A system power supply module 136 provides power to the components of the multimedia console 100. A fan 138 cools the circuitry within the multimedia console 100.


The CPU 101, GPU 108, memory controller 110, and various other components within the multimedia console 100 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 a Peripheral Component Interconnects (PCI) bus, PCI-Express bus, etc.


When the multimedia console 100 is powered ON, application data may be loaded from the system memory 143 into memory 112 and/or caches 102, 104 and executed on the CPU 101. The application may present a graphical user interface that provides a consistent user experience when navigating to different media types available on the multimedia console 100. In operation, applications and/or other media contained within the media drive 144 may be launched or played from the media drive 144 to provide additional functionalities to the multimedia console 100.


The multimedia console 100 may be operated as a standalone system by simply connecting the system to a television or other display. In this standalone mode, the multimedia console 100 allows one or more users to interact with the system, watch movies, or listen to music. However, with the integration of broadband connectivity made available through the network interface 124 or the wireless adapter 148, the multimedia console 100 may further be operated as a participant in a larger network community.


When the multimedia console 100 is powered ON, a set amount of hardware resources are reserved for system use by the multimedia console operating system. These resources may include a reservation of memory (e.g., 16 MB), CPU and GPU cycles (e.g., 5%), networking bandwidth (e.g., 8 kbs), etc. Because these resources are reserved at system boot time, the reserved resources do not exist from the application's view.


In particular, the memory reservation preferably is large enough to contain the launch kernel, concurrent system applications and drivers. The CPU reservation is preferably constant such that if the reserved CPU usage is not used by the system applications, an idle thread will consume any unused cycles.


With regard to the GPU reservation, lightweight messages generated by the system applications (e.g., popups) are displayed by using a GPU interrupt to schedule code to render popup into an overlay. The amount of memory required for an overlay depends on the overlay area size and the overlay preferably scales with screen resolution. Where a full user interface is used by the concurrent system application, it is preferable to use a resolution independent of application resolution. A scaler may be used to set this resolution such that the need to change frequency and cause a TV resynch is eliminated.


After the multimedia console 100 boots and system resources are reserved, concurrent system applications execute to provide system functionalities. The system functionalities are encapsulated in a set of system applications that execute within the reserved system resources described above. The operating system kernel identifies threads that are system application threads versus gaming application threads. The system applications are preferably scheduled to run on the CPU 101 at predetermined times and intervals in order to provide a consistent system resource view to the application. The scheduling is to minimize cache disruption for the gaming application running on the console.


When a concurrent system application requires audio, audio processing is scheduled asynchronously to the gaming application due to time sensitivity. A multimedia console application manager (described below) controls the gaming application audio level (e.g., mute, attenuate) when system applications are active.


Input devices (e.g., controllers 142(1) and 142(2)) are shared by gaming applications and system applications. The input devices are not reserved resources, but are to be switched between system applications and the gaming application such that each will have a focus of the device. The application manager preferably controls the switching of input stream, without knowledge the gaming application's knowledge and a driver maintains state information regarding focus switches.


The present invention is directed to a “Gamer Profile,” which serves as a building block for services and applications that aim to create a social community of gamers and grow relationships among players. In accordance with the present invention, the Gamer Profile is the entirety of information (e.g., metadata) related to a specific user (i.e., the gamer's digital identity). The Gamer Profile is developed from a set of services that collect and expose this information in a meaningful way to the community. The Gamer Profile also provides for personalization such that users can customize and enhance their gaming experience. As will be discussed in greater detail below, the Gamer Profile consists of various components, including, but not limited to, a Gamercard, game achievements, and gamer preferences.


Referring to FIG. 2, there is illustrated an overview of an exemplary architecture that may be used to implement the Gamer Profile. The console 100 interacts with a remote service 158 that provides services 160 such as voice/chat, a friends list, matchmaking, content download, roaming, feedback, tournaments, voice messaging, and updates to games. The service 158 also maintains the Gamer Profiles in a profile database 162 and configuration data 164 used by the services 160 and games 154. The service 158 collects Gamer Profiles, aggregates, processes information supplied by other services 160, and fulfills real-time client requests for retrieving Gamer Profile-related services. The Gamer Profiles in the database 162 are also used by the games 154 to enable, among other things, personalization and customization, etc.


Using the console 100, the user may interact with a guide 156. The guide 156 provides an interface where the user may navigate to, and enter, various online areas and options provided by the service 158. The configuration data 164 stored by the service 158 may be used to determine features and options provided by the guide 156. When the game 154 is running, a defined set of APIs are used to call and interact with the services 160. When requesting Gamer Profile information via the APIs, the game 154 may pass a unique identifier of a user. The service 158 may return a Gamercard (discussed below), game stats, game achievements, affiliations, game settings. etc. Additional details of the various aspects of the exemplary architecture are provided below.


The console 100 includes an offline tracking mechanism 157 that tracks offline player activity during periods when a player is not communicatively connected to the service 158. The tracker/aggregator 157 tracks offline player activity during offline sessions and aggregates that data with the online player activity into the Gamer Profile 166.


Referring to FIG. 3, the Gamer Profile 166 is created when a user creates a profile (selected from the guide 156) and chooses his/her unique Gamertag (a user's unique name), tile (picture/avatar associated with the user) other options during an account sign-up phase. From there, a base Gamer Profile 166 is created. The Gamer Profile 166 may then be populated from several sources. For example, the Gamer Profile 166 may include self-described data 168 from the Gamer Profile owner. Other gamers 170 can provide feedback regarding the Gamer Profile owner. The service 158 may track the gamer's online and offline activity. In addition, the games 154 may report the gamer's statistics and game achievements.


The owner of Gamer Profile can edit his/her Gamer Profile 166 directly and control who can view each section of the Gamer Profile. The Gamer Profile 166 may be edited via general fields (e.g., tile, country, language, gender, greeting, etc.) and/or system settings (e.g., voice output, controller vibration, character name, game format, game mode, etc.). Privacy/Opt-out Settings can be tuned for the Gamer Profile to, e.g., restrict presence information only to friends, allow game achievements to be visible to all, etc.


The Gamer Profile 166 may include feedback provided by other players 170. Feedback helps others learn about a particular gamer. For example, if the gamer uses foul language or aggressive play in game sessions, other gamers may submit feedback to the service 158. The feedback mechanism improves the user experience by building reputations. Players are therefore anonymous, but not unknown because of the accumulated feedback.


As noted above the Gamer Profile 166 may be used for customization and preference setting on a global level, as well as a per game level. Gamer preferences aid games 154 in choosing defaults for common settings such as game profile name, controller inversion and controller vibration, etc. For example, if a gamer likes using an inverted controller, this preference will be used for new titles as they are played. Games 154 have access to Gamer Profiles via the database 162 and services 160. In addition, game usage data can be mined to tune the game 154 to the user's particular preferences and game features updated after the initial game launch.


As noted above, the Gamer Profile 166 conveys, among other things, game achievements. Players will be rewarded with game achievements based mastering certain in-game facets of the games they play. Each game achievement may be conveyed in the Gamer Profile 166 as, e.g., a badge or trophy, title, description, date, etc., as shown in FIG. 4. Games may supply a screen snapshot or some other rich media captured at the moment the player earned a given achievement. This too may be displayed as part of the Gamer Profile 166. Players will accumulate gamer Cred (a points-based reward system) based on game achievements. As shown in FIG. 4, the player has a gamer Cred of 290. The display interface of FIG. 4 may be made available within the console 100 or via, e.g., a web browser, etc.


Referring to FIG. 5, there is illustrated the overall relationship of the game achievements and gamer Cred in accordance with the present invention. The player's total gamer Cred is an aggregation of gamer Cred awarded through the play of one or more games (e.g., Title A and Title B). Each game may award up to a certain amount of game Cred (e.g., 200) that is divided into game-defined achievements and standard system achievements.


For example, referring to the user interface FIG. 6, Title A may be a relatively easy game to master and may award a total of 100 game-defined gamer Cred points. Within Title A, there may be several achievements (e.g., Campaign completed on hardest, multiplayer level 10, etc.) The relative weight of each of the achievements is set based on the total weight (e.g., Campaign completed on hardest is 10/36 or 27.8%). If a player completes this achievement, then the player may be awarded 27.8% of the 100 total gamer Cred points, or 28, rounded to the nearest integer value. A player is preferably credited with an achievement only once.


The standard system achievements make up the remaining 100 points in the exemplary embodiment. The standard system achievements may be applied to all games. They may include achievements such as a first sign-in to a title, completing a first session with a game, completing a first hour of a game, completing 100 sessions with a game, completing 10 hours with a game, completing a game, etc. Other system achievements may be defined as necessary. The system achievements may be weighted such that a first sign-in is awarded a relative few points, whereas completing 100 sessions is awarded a higher number points.


Developers may use a tool that include user interface of FIG. 6 to describe their game. The tool may create a configuration file that a system application on the console 100 reads when the game is loaded, a C++ header file that game code can compile against, and an XML file that is used for configuration, creation of tables, creation stored procedures, and creation of leader boards.


Although Title A and Title B can award 200 gamer Cred points, more difficult games may award 500 or 1000 (or some other number) of gamer Cred points. The total amount to be awarded on a per game basis is preferably set by the online service 158 and is not editable by the developers. This will maintain fairness and avoid the situation where Game X wants to increase sales by making the total number of gamer Cred points available a significantly higher number than other games.


Thus, the present invention provides a balanced game achievements system by weighting the difficulty of the achievements and the games. In addition, because the aggregation of game Cred is abstracted from the game to the console 100, the likelihood that a hacker or developer can over-value achievements to inflate a player's gamer Cred is reduced.


While the present invention has been described in connection with the preferred embodiments of the various Figs., it is to be understood that other similar embodiments may be used or modifications and additions may be made to the described embodiment for performing the same function of the present invention without deviating therefrom.

Claims
  • 1. A system comprising: a first computing device; andan intermediary computing device;wherein the first computing device is configured to: receive configuration preferences from a first user having a first user profile; andsend the configuration preferences to the intermediary computing device;wherein the intermediary computing device is configured to: maintain the first user profile in a database remotely from the first computing device; andreceive the configuration preferences from the first computing device and update the first user profile to reflect the configuration preferences received from the first computing device;wherein the first computing device is further configured to: execute first game code of one or more first games; andsend a user identifier of the first user to the intermediary computing device;wherein the intermediary computing device is further configured to: receive the user identifier of the first user from the first computing device; andsend the configuration preferences to the first computing device responsive to receiving the user identifier; andwherein the first computing device is further configured to adapt an individual first game to execute on the first computing device according to the configuration preferences received from the intermediary computing device,wherein the configuration preferences relate to controller inversion or vibration settings.
  • 2. The system of claim 1, further comprising: a second computing device configured to execute second game code of one or more second games, wherein the one or more second games are played on the second computing device by a second user having a second profile.
  • 3. The system of claim 2, wherein the intermediary computing device is further configured to: receive, from the first gaming system, an indication that the first user achieved a system achievement by playing the individual first game on the first computing device;receive, from the first computing device, indications that the first user achieved occurrences of first in-game achievements while playing the individual first game on the first computing device;receive, from the second computing device, an indication that the second user also achieved the system achievement by playing, on the second computing device, an individual second game that is different than the individual first game;receive, from the second computing device, indications that the second user achieved occurrences of second in-game achievements while playing the individual second game on the second computing device;update the first profile to include first system achievement points for the system achievement by the first user and first in-game achievement points for the first occurrences of the first in-game achievements; andupdate the second profile to include second system achievement points for the system achievement by the second user and second in-game achievement points for the second occurrences of the second in-game achievements,wherein the first system achievement points and the second system achievement points are identical and the first in-game achievement points are different than the second in-game achievement points.
  • 4. The system of claim 1, wherein the configuration preferences relate to controller inversion.
  • 5. The system of claim 1, wherein the configuration preferences relate to vibration settings.
  • 6. The system of claim 1, wherein the first computing device is embodied as a gaming console.
  • 7. A computing system comprising: a processing unit; anda memory device storing computer executable instructions which, when executed by the processing unit, cause the computing system to: receive configuration preferences from a user having a user profile, the configuration preferences identifying user-preferred inversion settings or user-preferred vibration settings for game play by the user;send the user-preferred inversion settings or the user-preferred vibration settings to a remote service that maintains a user profile of the user in a database remotely from the computing system and updates the user profile to reflect the user-preferred inversion settings or the user-preferred vibration settings received from the computing system;send a user identifier of the user to the remote service, wherein the remote service sends the user-preferred inversion settings or the user-preferred vibration settings to the computing system responsive to receiving the user identifier; andconfigure a game to execute on the computing system according to the user-preferred inversion settings or the user-preferred vibration settings received from the remote service.
  • 8. The computing system of claim 7, wherein the user-preferred inversion settings are identified by the configuration preferences and specify that the user prefers to use an inverted game controller.
  • 9. The computing system of claim 8, wherein the computer executable instructions, when executed by the processing unit, cause the computing system to: adapt the game to use the inverted game controller.
  • 10. The computing system of claim 7, wherein the user-preferred vibration settings are identified by the configuration preferences and relate to vibration of a game controller.
  • 11. The computing system of claim 10, wherein the computer executable instructions, when executed by the processing unit, cause the computing system to: adapt the game to control vibration of the game controller according to the user-preferred vibration settings.
  • 12. The computing system of claim 7, embodied as a gaming console.
  • 13. The computing system of claim 7, wherein the computer executable instructions, when executed by the processing unit, cause the computing system to: as new games are played on the computing system, configure the new games to execute on the computing system according to the user-preferred inversion settings or the user-preferred vibration settings.
  • 14. A method performed by a processing unit of a computing system, the method comprising: receiving configuration preferences from a user having a user profile, the configuration preferences identifying user-preferred inversion settings or user-preferred vibration settings for game play by the user;sending the user-preferred inversion settings or the user-preferred vibration settings to a remote service that maintains a user profile of the user in a database remotely from the computing system and updates the user profile to reflect user-preferred inversion settings or the user-preferred vibration settings received from the computing system;sending a request to the remote service, wherein the remote service sends the user-preferred inversion settings or the user-preferred vibration settings to the computing system responsive to receiving the request; andconfiguring a game to execute on the computing system according to the user-preferred inversion settings or the user-preferred vibration settings received from the remote service.
  • 15. The method of claim 14, wherein sending the request comprises calling an application programming interface provided by the remote service.
  • 16. The method of claim 15, wherein calling the application programming interface comprises sending a unique identifier of the user to the remote service.
  • 17. The method of claim 14, wherein the user-preferred inversion settings specify that the user prefers to use an inverted game controller.
  • 18. The method of claim 17, further comprising: configuring the game and one or more other games to use the inverted game controller when the user plays the game and the one or more other games on the computing system.
  • 19. The method of claim 14, wherein the user-preferred vibration settings relate to vibration of a game controller.
  • 20. The method of claim 19, further comprising: configuring the game and one or more other games to control vibration of the game controller according to the user-preferred vibration settings when the user plays the game and the one or more other games on the computing system.
CROSS-REFERENCE TO RELATED APPLICATIONS

This patent application is a continuation of, and claims priority from, U.S. patent application Ser. No. 13/165,211 filed on Jun. 21, 2011. U.S. patent application Ser. No. 13/165,211 is a continuation of, and claims priority from, U.S. patent application Ser. No. 13/019,951 filed on Feb. 2, 2011, now U.S. Pat. No. 8,323,112 issued Dec. 4, 2012. U.S. patent application Ser. No. 13/165,211 is also a continuation of, and claims priority from, U.S. patent application Ser. No. 12/987,871 filed on Jan. 10, 2011, now U.S. Pat. No. 8,277,325 issued Oct. 2, 2012. U.S. patent application Ser. No. 13/019,951 is a continuation of U.S. patent application Ser. No. 12/987,871, which is a continuation of, and claims priority from, U.S. patent application Ser. No. 11/005,768 filed on Dec. 7, 2004, now U.S. Pat. No. 7,887,419 issued Feb. 15, 2011, all of which are incorporated herein by reference in their entirety.

US Referenced Citations (214)
Number Name Date Kind
5083271 Thacher et al. Jan 1992 A
5551701 Bouton et al. Sep 1996 A
5563805 Arbuckle et al. Oct 1996 A
5633484 Zancho et al. May 1997 A
5674127 Horstmann et al. Oct 1997 A
5697844 Von Kohom Dec 1997 A
5708709 Rose Jan 1998 A
5754176 Crawford May 1998 A
5768382 Schneier et al. Jun 1998 A
5779549 Walker et al. Jul 1998 A
5791992 Crump et al. Aug 1998 A
5846132 Junkin Dec 1998 A
5883955 Ronning Mar 1999 A
5918010 Appleman et al. Jun 1999 A
5945988 Williams et al. Aug 1999 A
5970143 Schneier et al. Oct 1999 A
6003013 Boushy et al. Dec 1999 A
6020884 MacNaughton et al. Feb 2000 A
6024643 Begis Feb 2000 A
6024943 Ness et al. Feb 2000 A
6071194 Sanderson et al. Jun 2000 A
6081830 Schindler Jun 2000 A
6106395 Begis Aug 2000 A
6149519 Osaki et al. Nov 2000 A
6174236 Tsuda et al. Jan 2001 B1
6174237 Stephenson Jan 2001 B1
6200216 Peppel Mar 2001 B1
6203432 Roberts et al. Mar 2001 B1
6206782 Walker et al. Mar 2001 B1
6219047 Bell Apr 2001 B1
6226618 Downs et al. May 2001 B1
6256620 Jawahar et al. Jul 2001 B1
6280328 Holch et al. Aug 2001 B1
6287201 Hightower Sep 2001 B1
6293865 Kelly et al. Sep 2001 B1
6302793 Fertitta et al. Oct 2001 B1
6312336 Handelman et al. Nov 2001 B1
6322451 Miura Nov 2001 B1
6334214 Horstmann Dec 2001 B1
6343990 Rasmussen et al. Feb 2002 B1
6352479 Sparks, II Mar 2002 B1
6359572 Vale Mar 2002 B1
6371852 Acres Apr 2002 B1
6425828 Walker et al. Jul 2002 B2
6508710 Paravia Jan 2003 B1
6511377 Weiss Jan 2003 B1
6519629 Harvey et al. Feb 2003 B2
6544126 Sawano et al. Apr 2003 B2
6572477 Hightower Jun 2003 B2
6645068 Kelly et al. Nov 2003 B1
6648760 Nicastro Nov 2003 B1
6688978 Herman Feb 2004 B1
6699124 Suchocki Mar 2004 B2
6708172 Wong et al. Mar 2004 B1
6732197 Overy May 2004 B1
6742032 Castellani et al. May 2004 B1
6746332 Ing et al. Jun 2004 B1
6755743 Yamashita et al. Jun 2004 B1
6804675 Knight et al. Oct 2004 B1
6805634 Wells et al. Oct 2004 B1
6821205 Takahashi et al. Nov 2004 B2
6829569 Drucker et al. Dec 2004 B1
6839435 Iijima et al. Jan 2005 B1
6939233 Emmerson Sep 2005 B2
6941353 Lane Sep 2005 B1
6979267 Leen et al. Dec 2005 B2
6996444 Ach, III Feb 2006 B2
7033276 Walker et al. Apr 2006 B2
7035653 Simon et al. Apr 2006 B2
7037198 Hameen-Anttila May 2006 B2
7056217 Pelkey et al. Jun 2006 B1
7069308 Abrams Jun 2006 B2
7086946 Yoshida Aug 2006 B2
7115033 Timperley Oct 2006 B1
7192352 Walker et al. Mar 2007 B2
7207011 Mulvey et al. Apr 2007 B2
7237189 Altenhofen et al. Jun 2007 B2
7240093 Danieli et al. Jul 2007 B1
7275105 Bloch et al. Sep 2007 B2
7311601 Anderson Dec 2007 B2
7311608 Daniell et al. Dec 2007 B1
7346658 Simpson Mar 2008 B2
7422521 Peterson Sep 2008 B2
7424617 Boyd et al. Sep 2008 B2
7490286 Commarford et al. Feb 2009 B2
7614955 Farnham et al. Nov 2009 B2
7621813 Bortnik et al. Nov 2009 B2
7698178 Chu Apr 2010 B2
7711847 Dhupelia et al. May 2010 B2
7730010 Kishore et al. Jun 2010 B2
7756926 Tseng et al. Jul 2010 B2
7806760 Baerlocher Oct 2010 B2
7837561 Bortnik et al. Nov 2010 B2
7857701 Murphy et al. Dec 2010 B2
7883413 Paulsen Feb 2011 B2
7887419 Bortnik Feb 2011 B2
7914381 Blythe et al. Mar 2011 B2
7918738 Paulsen Apr 2011 B2
8025571 Cisneros et al. Sep 2011 B2
8109828 Kane et al. Feb 2012 B2
8231472 Bortnik et al. Jul 2012 B2
8235818 Bortnik et al. Aug 2012 B2
8277325 Bortnik et al. Oct 2012 B2
8425331 Bortnik et al. Apr 2013 B2
8454443 Bortnik et al. Jun 2013 B2
8485905 Bortnik et al. Jul 2013 B2
8500560 Bortnik et al. Aug 2013 B2
8672751 Leen et al. Mar 2014 B2
20010010046 Muyres et al. Jul 2001 A1
20010044339 Cordero et al. Nov 2001 A1
20020002510 Sharp et al. Jan 2002 A1
20020023230 Bolnick et al. Feb 2002 A1
20020035568 Benthin et al. Mar 2002 A1
20020049507 Hameen-Anttila Apr 2002 A1
20020062316 Maehiro May 2002 A1
20020062350 Maehiro May 2002 A1
20020082077 Johnson et al. Jun 2002 A1
20020082086 Scallie Jun 2002 A1
20020082939 Clark et al. Jun 2002 A1
20020083145 Perinpanathan Jun 2002 A1
20020090996 Maehiro Jul 2002 A1
20020094851 Rheey Jul 2002 A1
20020103019 Emmerson Aug 2002 A1
20020115488 Berry et al. Aug 2002 A1
20020119824 Allen Aug 2002 A1
20020142815 Candelore Oct 2002 A1
20020142842 Easley et al. Oct 2002 A1
20020151366 Walker et al. Oct 2002 A1
20020160838 Kim Oct 2002 A1
20020173349 Ach, III Nov 2002 A1
20020173358 Yoshida Nov 2002 A1
20020183117 Takahashi et al. Dec 2002 A1
20020198949 Maehiro Dec 2002 A1
20030009549 Maehiro Jan 2003 A1
20030032474 Kaminkow Feb 2003 A1
20030043179 Gusler et al. Mar 2003 A1
20030045358 Leen et al. Mar 2003 A1
20030050115 Leen et al. Mar 2003 A1
20030070176 Parker et al. Apr 2003 A1
20030093168 Nagaoka May 2003 A1
20030100363 Ali May 2003 A1
20030104868 Okita et al. Jun 2003 A1
20030109301 Chudley Jun 2003 A1
20030109305 Gavin et al. Jun 2003 A1
20030114227 Rubin Jun 2003 A1
20030181242 Lee et al. Sep 2003 A1
20030190960 Jokipii et al. Oct 2003 A1
20030204566 Dhupelia et al. Oct 2003 A1
20030216962 Heller et al. Nov 2003 A1
20030228908 Caifa et al. Dec 2003 A1
20040077422 Bryant et al. Apr 2004 A1
20040087373 Choi May 2004 A1
20040088325 Elder et al. May 2004 A1
20040097287 Postrel May 2004 A1
20040107283 Paddon Jun 2004 A1
20040121835 Willis et al. Jun 2004 A1
20040172533 Demello et al. Sep 2004 A1
20040192440 Evans et al. Sep 2004 A1
20040198497 Yamashita et al. Oct 2004 A1
20040225386 Thompson et al. Nov 2004 A1
20040229698 Lind et al. Nov 2004 A1
20040242327 Shahar Dec 2004 A1
20040259641 Ho Dec 2004 A1
20050049037 Anderson Mar 2005 A1
20050054431 Walker et al. Mar 2005 A1
20050054447 Hiroyama et al. Mar 2005 A1
20050070359 Rodriquez et al. Mar 2005 A1
20050071786 Mariani et al. Mar 2005 A1
20050107157 Wachtfogel et al. May 2005 A1
20050130742 Feldman et al. Jun 2005 A1
20050137014 Vetelainen Jun 2005 A1
20050137015 Rogers et al. Jun 2005 A1
20050143174 Goldman et al. Jun 2005 A1
20050154557 Ebert Jul 2005 A1
20050170873 Fishbach et al. Aug 2005 A1
20050192097 Farnham et al. Sep 2005 A1
20050209002 Blythe et al. Sep 2005 A1
20050223080 Gray Oct 2005 A1
20050240603 Bodin et al. Oct 2005 A1
20050245314 Pirich et al. Nov 2005 A1
20050246638 Whitten Nov 2005 A1
20050261062 Lewin et al. Nov 2005 A1
20050282636 O'Brien Dec 2005 A1
20060048132 Chen et al. Mar 2006 A1
20060052168 Shacham Mar 2006 A1
20060064761 Multerer et al. Mar 2006 A1
20060075019 Donovan et al. Apr 2006 A1
20060085261 Chu Apr 2006 A1
20060085642 Multerer et al. Apr 2006 A1
20060121987 Bortnik et al. Jun 2006 A1
20060121991 Borinik et al. Jun 2006 A1
20060122716 Bortnik et al. Jun 2006 A1
20060136964 Diez et al. Jun 2006 A1
20060172799 Kane et al. Aug 2006 A1
20060183542 Ng et al. Aug 2006 A1
20060191016 Ostergren et al. Aug 2006 A1
20060196686 Gatto et al. Sep 2006 A1
20060258463 Cugno et al. Nov 2006 A1
20070077993 Midgley et al. Apr 2007 A1
20070099703 Terebilo May 2007 A1
20070111794 Hogan et al. May 2007 A1
20070117629 Fowler et al. May 2007 A1
20070173321 Shen et al. Jul 2007 A1
20070173327 Kilgore et al. Jul 2007 A1
20070191097 Johnson Aug 2007 A1
20080113789 Canessa et al. May 2008 A1
20090231515 Keam et al. Sep 2009 A1
20110045912 Bortnik et al. Feb 2011 A1
20110118035 Bortnik et al. May 2011 A1
20110136575 Bortnik et al. Jun 2011 A1
20110250959 Bortnik Oct 2011 A1
20120009999 Bortnik et al. Jan 2012 A1
20130252738 Bortnik et al. Sep 2013 A1
20140162773 Bortnik et al. Jun 2014 A1
Foreign Referenced Citations (26)
Number Date Country
1538339 Oct 2004 CN
1520608 Apr 2005 EP
1669117 Jun 2006 EP
09-152999 Jun 1997 JP
2001-109714 Apr 2001 JP
2001-212366 Aug 2001 JP
2002-085852 Mar 2002 JP
2002-210246 Jul 2002 JP
2002-239251 Aug 2002 JP
2003-047778 Feb 2003 JP
2003-111980 Apr 2003 JP
2003-154172 May 2003 JP
2003-205175 Jul 2003 JP
2003-271780 Sep 2003 JP
2003-281142 Oct 2003 JP
2003-337874 Nov 2003 JP
2003-340161 Dec 2003 JP
2004-097610 Apr 2004 JP
2004-329914 Nov 2004 JP
20000030338 Jun 2000 KR
20010082566 Aug 2001 KR
20030043348 Jun 2003 KR
20050003224 Jan 2005 KR
20050105396 Nov 2005 KR
WO0004458 Jan 2000 WO
WO2005092458 Oct 2005 WO
Non-Patent Literature Citations (104)
Entry
EP Communication for Application No. 05110418.0-2218, Reference EP36621RK900kap, Apr. 26, 2006.
EP Communication for Application No. 05110418.0-2218, Reference EP36621RK900kap, Jun. 14, 2006.
EP Rejection of request for extension of time limit issued for Application No. 05110418.0-1241, Reference EP36621RK900kap, Sep. 20, 2007.
EP Noting of loss of rights for Application No. 05110418.0-1241, Reference EP36621RK900kap, Oct. 12, 2007.
CN Notice on Reexamination for Application No. 200510119213.7, Sep. 29, 2012.
Abrash, M.; “Inside Xbox Graphics—A Powerful Game Platform Waiting in the Wings”; drdobbs.com; retrieved at http://www.drdobbs.com/184404199; Aug. 1, 2000; 9 pages.
Akkawi, A. et al.; “A Mobile Gaming Platform for the IMS”; Network and System Support for Games; Proceedings of 3rd ACM SIGCOMM Workshop on System Support for Games; 2004; 8 pages.
Henshaw, J.; “Inside Xbox 360: An Interview with Jeff Henshaw”; Interview by Paul Thurrott; Paul Thurrott's Supersite for Windows; retrieved at http://www.winsupersite.com/showcase/xbox360—inside.asp; Jun. 21-Jul. 7, 2005; 12 pages.
Huang, A.; “Keeping Secrets in Hardware: the Microsoft XBox™ Case Study”; Al Memo 2002-008; Massachusetts Institute of Technology-Artificial Intelligence Laboratory; Cambridge, MA; May 26, 2002; 15 pages.
Larocque, D.; “State Pattern in C++ Applications”; Codeguru.com; retrieved at http://www.codeguru.com/cpp/misc/misc/article.php/c3893; Sep. 17, 2001; 2 pages.
Suwalski, P; “Automotive Computing with Game Console Hardware”; Department of Systems and Computer Engineering at Carleton University; Ottawa, Ontario, Canada; Apr. 2005; 58 pages.
“Tiger Woods PGA Tour 2004”; copyright 2003.
EP Application 05110463.6; Search Report dated Feb. 28, 2006; 8 pages.
EP Application 05110463.6; Examination Report dated Jan. 10, 2007; 6 pages.
Japanese Patent Appln. 2005-311712; Second Office Action dated Aug. 31, 2012; 4 pages.
JP Application 2005-319924; Notice of Rejection dated Jun. 3, 2011; 5 pages.
Japanese Patent Appln. 2005-319924; Second Office Action dated Aug. 10, 2012; 3 pages.
KR Application 10-2005-97991; Notice of Preliminary Rejection dated Mar. 29, 2012; 6 pages.
EP Patent Application 05110418.0; Office Action dated Feb. 19, 2007.
CN Patent Application 200510119213.7; Office Actions dated Feb. 6, 2009; Oct. 9, 2009; Feb. 12, 2010; Jul. 29, 2010 and May 25, 2011.
EP Patent Application 2005-311712; Office Action dated Jun. 3, 2011.
Requirement for Restriction/Election mailed Apr. 6, 2015, from U.S. Appl. No. 13/874,945, 6 pages.
Response filed May 28, 2015 to Restriction Requirement mailed Apr. 6, 2015, from U.S. Appl. No. 13/874,945, 8 pages.
Examination Report mailed May 18, 2015 from European Patent Application No. 05110418.0-1905, 6 pages.
Response filed Oct. 22, 2007 to the Notification mailed Oct. 12, 2007, from European Patent Application No. 05110418.0-1905, 19 pages.
Response filed Aug. 8, 2008 to the Non-Final Office Action mailed Apr. 16, 2008, from U.S. Appl. No. 11/005,768, 9 pages.
Amendment filed Apr. 10, 2009 in response to the Non-Final Office Action mailed Dec. 10, 2008, from U.S. Appl. No. 11/005,768, 15 pages.
Response filed Jan. 8, 2010 to the Final Office Action mailed Aug. 10, 2009, from U.S. Appl. No. 11/005,768, 15 pages.
Response filed Jul. 22, 2010 to the Non-Final Office Action mailed Mar. 25, 2010, from U.S. Appl. No. 11/005,768, 18 pages.
Response filed Sep. 5, 2011 to the Notice of Rejection mailed Jun. 3, 2011, from Japan Patent Application No. 2005-311712, 21 pages.
Response filed Nov. 30, 2012 to the Final Notice of Rejection mailed Aug. 31, 2012, from Japan Patent Application No. 2005-311712, 24 pages.
Response filed Jun. 10, 2009 to the First Office Action mailed Feb. 6, 2009, from China Patent Application No. 200510119213.7, 10 pages.
Response filed Dec. 15, 2009 to the Second Office Action mailed Oct. 9, 2009, from China Patent Application No. 200510119213.7, 12 pages.
Response filed Oct. 11, 2010 to the fourth Office Action mailed Jul. 29, 2010, from China Patent Application No. 200510119213.7, 9 pages.
Request for Reexamination filed Sep. 6, 2011, from China Patent Application No. 200510119213.7, 11 pages.
Notice on Reexamination mailed Sep. 29, 2012, from China Patent Application No. 200510119213.7, 8 pages.
Preliminary Amendment filed Jan. 27, 2011 from U.S. Appl. No. 12/987,871, 9 Pages.
Preliminary Amendment filed Feb. 2, 2011 from U.S. Appl. No. 13/019,951, 7 Pages.
Response filed Aug. 14, 2012 to Non-Final Office Action mailed Jul. 17, 2012, from U.S. Appl. No. 13/019,951, 10 Pages.
Preliminary Amendment filed Jun. 21, 2011 from U.S. Appl. No. 13/165,211, 7 Pages.
Response filed Sep. 4, 2012 to Non-Final Office Action mailed Jul. 24, 2012, from U.S. Appl. No. 13/165,211, 13 Pages.
Non-Final Office Action mailed Jun. 23, 2008, from U.S. Appl. No. 11/005,674, 12 Pages.
Reply/Response filed Nov. 18, 2008 to Non-Final Office Action mailed Jun. 23, 2008, from U.S. Appl. No. 11/005,674, 11 Pages.
Preliminary Amendment filed May 1, 2013 from U.S. Appl. No. 13/874,945, 9 Pages.
Final Office Action mailed Jan. 29, 2009 from U.S. Appl. No. 11/005,674, 20 Pages.
Amendment/Response filed Apr. 29, 2009 to Final Office Action mailed Jan. 29, 2009 from U.S. Appl. No. 11/005,674, 15 Pages.
Non-Final Office Action mailed Dec. 4, 2009 from U.S. Appl. No. 11/005,674, 19 Pages.
Response filed Apr. 29, 2010 to Non-Final Office Action mailed Dec. 4, 2009 from U.S. Appl. No. 11/005,674, 17 Pages.
Final Office Action mailed Sep. 15, 2010 from U.S. Appl. No. 11/005,674, 22 Pages.
Response filed Nov. 2, 2010 to Final Office Action mailed Sep. 15, 2010 from U.S. Appl. No. 11/005,674, 21 Pages.
Non-Final Office Action mailed May 1, 2013 from U.S. Appl. No. 11/005,674, 20 Pages.
Response filed Aug. 1, 2013 to Non-Final Office Action mailed May 1, 2013 from U.S. Appl. No. 11/005,674, 12 Pages.
Notice of Allowance mailed Aug. 13, 2013 from U.S. Appl. No. 11/005,674, 6 Pages.
Notice of Allowance mailed Feb. 28, 2014 from U.S. Appl. No. 11/005,674, 5 Pages.
Notice of Allowance mailed Jun. 23, 2014 from U.S. Appl. No. 11/005,674, 5 Pages.
Adams et al., “Selecting Tools for Online Communities: Suggestions for Learning Technologists”, The Technology Source Archives at the University of North Carolina, <<http://technologysource.org/article/selecting—tools—for—online—communities/>>, Jul. 2003, 6 pages.
Bortnik et al., “Application Interface for Tracking Player Identity”, U.S. Patent Application filed May 12, 2015, 20 pages.
Braingle, “Braingle's Online Multiplayer Checkers Ladder”, <<http://www.braingle.in/games/checkers/index.php>>, Accessed May 13, 2014, 2 pages.
Braingle, “Gizzer”, <<https://web.archive.org/web/20031004154555/http://www.braingle.com/view.php?user=Gizzer>>, Accessed May 13, 2014, 3 pages.
Braingle, “Online Now—Braingle's Multiplayer Checkers Ladder”, <<http://www.braingle.in/games/checkers/index.php>>, Oct. 2, 2003, 3 pages.
“Phantasy Star Online IGN Guide”, IGN Guides, <<http://tails.kicks-ass.net/content/sorting/clean/gaming/sega—scene—releases/sega—dreamcast—manuals/PHANTASYSTAR ONLINE IGN-GUIDE.PDF>>, Accessed May 17, 2001, 64 pages.
“The Older Gamers Forums—FAQ: User Profile Features”, The Older Gamers Forum, <<http://www.theoldergamers.com/forum/faq.php?faq=vb3—user—profile>>, Accessed May 13, 2014, 6 pages.
Aslund, Jonas, “Authentication in Peer-to-Peer Systems”, Doctoral Dissertation, May 16, 2002, 134 pages.
Wang et al., “An Architecture of Game Grid Based on Resource Router”, Grid and Cooperative Computing, Lecture Notes in Computer Science, vol. 3032, Dec. 7, 2003, 8 pages.
Boga et al., “Mobile Casino”, A Master Thesis, Technical University of Denmark, Aug. 2004, 153 pages.
Chang et al., “Web Browsing in a Wireless Environment: Disconnected and Asynchronous Operation in ARTour Web Express”, Proceedings of the 3rd Annual ACM/IEEE International Conference on Mobile Computing and Networking, Sep. 26, 1997, 10 pages.
Non-Final Office Action mailed Jun. 23, 2008 from U.S. Appl. No. 11/005,674, 13 pages.
Reply/Response filed Nov. 18, 2008 to Non-Final Office Action mailed Jun. 23, 2008 from U.S. Appl. No. 11/005,674, 8 pages.
Amendment/Response to Final Office Action mailed Jan. 29, 2009 from U.S. Appl. No. 11/005,674, 15 pages.
Non-Final Office Action mailed Dec. 4, 2009, from U.S. Appl. No. 11/005,674, 19 pages.
Amendment/response filed Apr. 29, 2010 to Non-Final Office Action mailed Dec. 4, 2009, from U.S. Appl. No. 11/005,674, 17 pages.
Final Office Action mailed Sep. 15, 2010, from U.S. Appl. No. 11/005,674, 22 pages.
Response filed Nov. 2, 2010 to Final Office Action mailed Sep. 15, 2010, from U.S. Appl. No. 11/005,674, 21 pages.
Non-Final Office Action mailed May 1, 2013, from U.S. Appl. No. 11/005,674, 20 pages.
Response filed Aug. 1, 2013 to Non-Final Office Action mailed May 1, 2013, from U.S. Appl. No. 11/005,674, 12 pages.
Notice of Allowance mailed Feb. 28, 2014, from U.S. Appl. No. 11/005,674, 5 pages.
Notice of Rejection mailed on Aug. 10, 2012, from Japanese Patent Application No. 2005-319924, 5 pages.
Response filed Nov. 12, 2012 to Notice of Rejection mailed on Aug. 10, 2012, from Japanese Patent Application No. 2005-319924, 10 pages.
Response filed May 29, 2012 to Office Action, from Korean Patent Application No. 2005-0097991, 45 pages.
Notice of Final Rejection mailed Oct. 29, 2012, from Korean Patent Application No. 2005-0097991, 15 pages.
Non-Final Office Action mailed May 19, 2008, from U.S. Appl. No. 11/006,275, 10 pages.
Response/Reply filed Aug. 19, 2008 to Non-Final Office Action mailed May 19, 2008, from U.S. Appl. No. 11/006,275, 9 pages.
Final Office Action mailed Nov. 7, 2008, from U.S. Appl. No. 11/006,275, 9 pages.
Amendment/Response filed May 7, 2009 to Final Office Action mailed Nov. 7, 2008, from U.S. Appl. No. 11/006,275, 10 pages.
Notice of Allowance mailed Jul. 13, 2009, from U.S. Appl. No. 11/006,275, 7 pages.
Non-Final Office Action mailed Mar. 1, 2010 from U.S. Appl. No. 12/578,605, 6 pages.
Response filed May 19, 2010 to Non-Final Office Action mailed Mar. 1, 2010 from U.S. Appl. No. 12/578,605, 10 pages.
Notice of Allowance mailed Jul. 21, 2010 from U.S. Appl. No. 12/578,605, 7 pages.
Notice of Allowance mailed Mar. 28, 2012 from U.S. Appl. No. 12/916,246, 13 pages.
Notice of Allowance mailed Mar. 26, 2012 from U.S. Appl. No. 13/240,454, 15 pages.
Examiner-Initiated Interview Summary and Notice of Allowance mailed Apr. 3, 2013 from U.S. Appl. No. 13/535,151 16 pages.
Examiner-Initiated Interview Summary and Notice of Allowance mailed Apr. 3, 2013 from U.S. Appl. No. 13/535,161 16 pages.
Preliminary Amendment filed May 8, 2015 from U.S. Appl. No. 13/956,250, 5 pages.
Notice of Allowance mailed Jun. 1, 2015 from U.S. Appl. No. 13/956,250, 8 pages.
Non-Final Office Action mailed Sep. 8, 2015 from U.S. Appl. No. 13/874,945, 55 pages.
Applicant-Initiated Interview Summary mailed Nov. 19, 2015 from U.S. Appl. No. 13/874,945, 3 pages.
Response filed Nov. 23, 2015 to Non-Final Office Action mailed Sep. 8, 2015 from U.S. Appl. No. 13/874,945, 17 pages.
Notice of Allowance mailed Dec. 9, 2015 from from U.S. Appl. No. 13/874,945, 21 pages.
Communication under Rule 71(3) EPC, Notice of Intention to Grant mailed Oct. 6, 2015 from European Patent Application No. 05110463.6-1870, 38 pages.
Comments on Statement of Reasons of Allowance filed Aug. 25, 2015 from U.S. Appl. No. 13/956,250, 2 pages.
Response filed Jul. 17, 2007 to Official Communication dated Jan. 10, 2007 from European Patent Application No. 35110463.6-2413, 19 pages.
Notice of Intention to Grant mailed Oct. 6, 2015 from European Patent Application No. 05110463.6-2413, 38 pages.
Comments on Statement of Reasons for Allowance filed Aug. 25, 2015 from U.S. Appl. No. 13/956,250, 2 pages.
Preliminary Amendment filed Jan. 18, 2016 from U.S. Appl. No. 14/709,851, 7 pages.
Related Publications (1)
Number Date Country
20130244793 A1 Sep 2013 US
Continuations (4)
Number Date Country
Parent 13165211 Jun 2011 US
Child 13875104 US
Parent 13091951 Feb 2011 US
Child 13165211 US
Parent 12987871 Jan 2011 US
Child 13091951 US
Parent 11005768 Dec 2004 US
Child 12987871 US