Defining and exposing storage devices generically to end users and developers through abstracted storage

• US 20060095475A1
• Filed: 10/29/2004
• Published: 05/04/2006
• Est. Priority Date: 10/29/2004
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Asmi, Yasser B., Whitten, Jon Marcus Randall, Maston, Michael Cory, Schmidt, Brian Lloyd, Martinez, Gregory A., Simon, Jeffrey Edward, Irving, Richard Henry, Pirich, Christopher, Carper, Tyler Scott
• Application Number:
  US10/977,646
• Publication Number:
  US 20060095475A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: A63F 13/48 Starting a game, e.g. activating a game device or waiting for other players to join a multiplayer session
• CPC Class Codes: A63F 13/49 Saving the game status; Pausing or ending the game
• CPC Class Codes: A63F 13/533 for prompting the player, e.g. by displaying a game menu
• CPC Class Codes: A63F 13/95 Storage media specially adapted for storing game information, e.g. video game cartridges
• CPC Class Codes: A63F 2300/206 Game information storage, e.g. cartridges, CD ROM's, DVD's, smart cards
• CPC Class Codes: A63F 2300/554 by saving game or status data
• CPC Class Codes: A63F 2300/636 involving process of starting or resuming a game
• CPC Class Codes: G06F 2003/0697 device management, e.g. handlers, drivers, I/O schedulers
• CPC Class Codes: G06F 3/0601 Interfaces specially adapted for storage systems
• CPC Class Codes: G06F 9/4411 Configuring for operating with peripheral devices; Loading of device drivers
• CPC Class Codes: G07F 17/32 for games, toys, sports, or amusements

Abstract

A system and method for enabling users and developers to store data on a number of different types of local and remote devices connected to a gaming console, a multimedia console or a console that is both gaming and multimedia console. The range of available storage devices creates issues that are addressed to avoid apparent inconsistencies in storage performance (e.g. latency). A consistent method of reading and writing data is provided such that end users and developers do not have to be concerned with restrictions and limitations inherent to various devices.

Claims

1. A method for reading/writing data from one of multiple, diverse storage devices communicatively connected to gaming console, comprising:

detecting and enumerating storage devices;

detecting an event requesting to read/write data;

presenting a user interface displaying detected storage devices;

receiving an input selecting a particular storage device from which said data is to be read/written; and

reading/writing said data in accordance with a received input.

2. The method of claim 1, said detecting and enumerating said storage devices further comprising tracking insertions and removals of storage devices for each said event.

3. The method of claim 1, further comprising searching said storage devices for identification information related to an application requesting to read/write data to said storage devices.

4. The method of claim 1, further comprising exposing APIs to provide a common system save user interface or an application-specific save user interface.

5. The method of claim 4, wherein if a read operation is performed, said method further comprises:

calling a first API;

providing said common system save dialog;

passing data to said first API; and

passing control to said gaming console to perform said read operation.

6. The method of claim 4, wherein if a read operation is performed and said application knows a location of data to be read, said method further comprises:

passing a pointer a data file and name;

mounting a storage location associated with said data file;

reading said data file; and

passing data from said data file to said application.

7. The method of claim 4, wherein if a read operation is performed, said method further comprises:

calling a second API to perform said detecting and enumerating of said storage devices;

providing said application-specific save user interface;

calling a third API to mount a requested storage device and to read said data from said requested storage device; and

informing said gaming console that said read operation is complete.

8. The method of claim 4, wherein if a write operation is performed, said method further comprises:

calling a fourth API;

providing said common system save dialog;

passing data to said fourth API; and

passing control to said gaming console to perform said write operation.

9. The method of claim 4, wherein if a write operation is performed and said application knows a location of data to be written, said method further comprises:

passing a pointer a data file and name;

mounting a storage location associated with said data file;

writing said data file; and

passing data from said application to said data file.

10. The method of claim 4, wherein if a write operation is performed, said method further comprises:

calling a fifth API to perform said detecting and enumerating of said storage devices;

providing said application-specific save user interface;

calling a sixth API to mount a requested storage device and to write said data to said requested storage device; and

informing said gaming console that said write operation is complete.

11. A computer readable medium having stored thereon computer executable instructions for reading/writing data from one of multiple, diverse storage devices communicatively connected to a gaming console, said instructions performing the steps of:

detecting and enumerating storage devices;

detecting an event requesting to read/write data;

presenting a user interface displaying detected storage devices;

receiving an input selecting a particular storage device from which said data is to be read/written; and

reading/writing said data in accordance with a received input.

12. The computer readable medium of claim 11, said detecting and enumerating said storage devices further comprising instructions for tracking insertions and removals of storage devices for each said event.

13. The computer readable medium of claim 11, further comprising instructions for searching said storage devices for identification information related to an application requesting to read/write data to said storage devices.

14. The computer readable medium of claim 11, further comprising instructions for exposing APIs to provide a common system save user interface or an application-specific save user interface.

15. The computer readable medium of claim 14, wherein if a read operation is performed, said computer readable medium further comprises instructions for:

calling a first API;

providing said common system save dialog;

passing a data structure to said first API; and

passing control to said gaming console to perform said read operation.

16. The computer readable medium of claim 14, wherein if a read operation is performed and said application knows a location of data to be read, said computer readable medium further comprises instructions for:

passing a pointer a data file and name;

mounting a storage location associated with said data file;

reading said data file; and

passing data from said data file to said application.

17. The computer readable medium of claim 14, wherein if a read operation is performed, said computer readable medium further comprises instructions for:

calling a second API to perform said detecting and enumerating of said storage devices;

providing said application-specific save user interface;

calling a third API to mount a requested storage device and to read said data from said requested storage device; and

informing said gaming console that said read operation is complete.

18. The computer readable medium of claim 14, wherein if a write operation is performed, said computer readable medium further comprises instructions for:

calling a fourth API;

providing said common system save dialog;

passing data to said fourth API; and

passing control to said gaming console to perform said write operation.

19. The computer readable medium of claim 14, wherein if a write operation is performed and said application knows a location of data to be written, said computer readable medium further comprises instructions for:

passing a pointer a data file and name;

mounting a storage location associated with said data file;

writing said data file; and

passing data from said application to said data file.

20. The computer readable medium of claim 14, wherein if a write operation is performed, said computer readable medium further comprises instructions for:

calling a fifth API to perform said detecting and enumerating of said storage devices;

providing said application-specific save user interface;

calling a sixth API to mount a requested storage device and to write said data to said requested storage device; and

informing said gaming console that said write operation is complete.