Application-centric user interface technique

The present invention relates to human-computer interaction techniques such as when a computer user interacts with a user interface presented by software.

Some of the disclosures in this patent document include material that is subject to copyright protection. The copyright holder has no objection to any person copying this patent document or disclosure when it is found in a patent file or record of the U.S. Patent and Trademark Office, but otherwise all. Reserve any copyright.

Since the advent of the computer era, various human-computer interaction methods have been developed and implemented to help make computers easier to use. For example, the now popular graphical user interface (GUI) paradigm makes it easier for users to select a program by simply pointing to the icon associated with the desired program without typing the program name.

<p> However, with the advent of more complex computing devices, seemingly more complex graphical user interfaces with many levels of choice have been proposed. The user may be presented with a large number of levels of choice within the user interface, in which case finding the desired choice can be a cumbersome task. As a result, the user may try to avoid the choice of options that may actually be needed. Therefore, too many options are an obstacle for the user.</p>

<p> The techniques described herein provide a variety of user interface configurations and related features. For example, various application-centric user interface technologies can be used.</p><p> In one embodiment, an application-centric user interface is presented to the user. In one embodiment, the user can add, update, or launch a program from the application-centric part.</p><p> In one embodiment, the application-centric user interface includes an activity center, which allows the user to perform various actions related to the application.</p><p> In the embodiments described herein, the application includes game-related software. For example, available games and related information can be presented to the user. In one embodiment, a multiplayer online game can be launched.</p><p> Additional features and advantages will become apparent from the following detailed description of the exemplary embodiments, made with reference to the accompanying drawings.</p>

<figref num="1A">An example application-centric user interface screenshot.</figref><figref num="1B">An example application-centric user interface screenshot.</figref><figref num="2A">FIG. 6 is a screenshot of an example application tile for use in an application-centric user interface, such as the user interfaces 1A and 1B.</figref><figref num="2B">FIG. 6 is a screenshot of an example application tile for use in an application-centric user interface, such as the user interfaces 1A and 1B.</figref><figref num="2C">FIG. 6 is a screenshot of an example application tile for use in an application-centric user interface, such as the user interfaces 1A and 1B.</figref><figref num="2D">FIG. 6 is a screenshot of an example application tile for use in an application-centric user interface, such as the user interfaces 1A and 1B.</figref><figref num="3A">An alternative example application-centric user interface screenshot.</figref><figref num="3B">An alternative example application-centric user interface screenshot.</figref><figref num="4">It is a block diagram which shows the relationship between pages in an application-centric user interface.</figref><figref num="5A">It is a screenshot of an example detail page that presents information about the application.</figref><figref num="5B">It is a screenshot of an example detail page that presents information about the application.</figref><figref num="6">Screenshots of an exemplary application-centric user interface presented as part of the user interface for the operating system shell.</figref><figref num="7">It is a block diagram which shows the relationship between folders presented as a part of the user interface for an operating system shell.</figref><figref num="8">It is a figure which shows the contents of the example application metadata file.</figref><figref num="9">It is a block diagram showing the relationship between an operating system shell, an application metadata file, and an application.</figref><figref num="10">It is a Venn diagram showing the relationship between the application metadata file and the special application metadata file.</figref><figref num="11">Here is a screenshot of an example review of an application from which the application metadata file can be obtained.</figref><figref num="12">FIG. 5 is a flow diagram illustrating an exemplary method for achieving application installation via an application metadata file.</figref><figref num="13">It is a flow chart which shows the example method of accommodating a legacy application in an application activity center.</figref><figref num="14">It is a screenshot which shows the example detail page about a game in a game activity center.</figref><figref num="15">It is a block diagram which shows the scenario of the example multiplayer online game.</figref><figref num="16">FIG. 6 is a block diagram illustrating exemplary relationships between instant messaging, operating system shells, and gaming applications.</figref><figref num="17">FIG. 15 is a screenshot of the user interface for achieving an exemplary multiplayer online game scenario as shown in FIG.</figref><figref num="18A">Illustrations of application tiles for use in a game-centric user interface, such as the game-centric implementation of the user interface in Figures 1A and 1B.</figref><figref num="18B">Illustrations of application tiles for use in a game-centric user interface, such as the game-centric implementation of the user interface in Figures 1A and 1B.</figref><figref num="19">It is a block diagram which shows the example computer system.</figref><figref num="20">An excerpt of a programming language that specifies an exemplary application programming interface for achieving application installation through the techniques described herein.</figref><figref num="21">An excerpt of a programming language that specifies an exemplary application programming interface for achieving application installation through the techniques described herein.</figref><figref num="22">An excerpt of a programming language that specifies an exemplary application programming interface for achieving application installation through the techniques described herein.</figref><figref num="23">An excerpt of a programming language that specifies an exemplary application programming interface for achieving application installation through the techniques described herein.</figref><figref num="24">An excerpt of a programming language that specifies an exemplary application programming interface for achieving application installation through the techniques described herein.</figref><figref num="25">An excerpt of a programming language that specifies an exemplary application programming interface for achieving application installation through the techniques described herein.</figref><figref num="26">An excerpt of a programming language that specifies an exemplary application programming interface for achieving application installation through the techniques described herein.</figref><figref num="27">It is a figure which specifies an example XML schema for use with application metadata.</figref><figref num="28">It is a figure which specifies an example XML schema for use with application metadata.</figref><figref num="29">It is a figure which specifies an example XML schema for use with application metadata.</figref><figref num="30">It is a figure which specifies an example XML schema for use with application metadata.</figref><figref num="31">It is a figure which specifies an example XML schema for use with application metadata.</figref><figref num="32">FIG. 5 specifies an exemplary XML Schema for use with application metadata that has special game-related metadata.</figref><figref num="33">FIG. 5 specifies an exemplary XML Schema for use with application metadata that has special game-related metadata.</figref><figref num="34">FIG. 5 specifies an exemplary XML Schema for use with application metadata that has special game-related metadata.</figref><figref num="35">FIG. 5 specifies an exemplary XML Schema for use with application metadata that has special game-related metadata.</figref><figref num="36">It is a figure which specifies the example metadata about a game application according to the schema of FIGS. 32 to 35.</figref><figref num="37">It is a figure which specifies the example metadata about a game application according to the schema of FIGS. 32 to 35.</figref><figref num="38">It is a figure which specifies the example metadata about a game application according to the schema of FIGS. 32 to 35.</figref><figref num="39">It is a figure which specifies an example XML schema for use with an application manifest.</figref><figref num="40">It is a figure which specifies an example XML schema for use with an application manifest.</figref><figref num="41">It is a figure which specifies an example XML schema for use with an application manifest.</figref>

(Example 1) (Outline of the illustrated system) Application-centric user interface techniques can be utilized in the various embodiments described herein. With the advent of increasingly complex user interfaces, application-centric user interface technologies can avoid the problems associated with not being able to easily find applications and perform tasks related to them. For example, application-centric user interface technologies can handle applications in a special way and include application-specific areas of the user interface (eg, other types of items such as files are not listed within the area). .. Such an approach is an improvement over a system that simply presents the application as part of a file system that contains a myriad of other items such as files.

In addition, applications can be presented richer, such as when presented by an operating system shell by the various techniques described herein. In this way, the application publisher can customize the shell presentation of the application. This technology can handle different applications by different application publishers.

(Example 2) (Example user interface display) Figure 1A shows a screenshot of an exemplary application-centric user interface 100. In this embodiment, there are two or more application tiles 122 in pane 120 that display the representation of each application. The items displayed in pane 120 are limited to the representation of the application (for example, the representation of other items or files does not appear).

Figure 1B shows a screenshot of another example application-centric user interface 100. In this example, in addition to two or more application tiles 122, there are recent application panes 130, task panes 140, and information panes 150. In one embodiment, one or more of the illustrated panes 130, 140, 150 may be used.

The most recently launched application pane 130 can show tiles for one or more (eg, three) of the most recently launched applications. Alternatively, you can use some other mechanism to indicate the most recently launched (s) application.

The task pane 140 represents one or more tasks that can be performed on the user interface, such as navigating various pages within the user interface. One task may be application-specific, while another may not work on a particular application. In this example, the "View Wish List" option is shown. When activated (eg by clicking), the Browse Wish List option takes you to a page showing a list of one or more applications that the user has specified in the Wish List. For example, the user may be considering purchasing such an application, or may have already determined that such an application is desirable and will be purchased at the time of release.

The information pane 150 can present one or more links 122, and when activated (eg by clicking), directs you to a detail page about the application indicated by the links. Links can be limited to those with up-to-date information, such as new information available in the last n days (eg, configurable by the user).

In any of the examples, the area of the user interface shown as a pane may or may not indicate the displayed boundary between the panes. Thus, as an alternative, the pane can be an area of the user interface that has no visible boundaries. You can add items, make them fewer items, or include other items. For example, you can have the menu bar present additional features or options.

(Example 3) (Example tile) To facilitate a richer representation of the application in the user interface, the exemplary tiles described herein can present a graphical representation of the application and other information about the application. FIG. 2A is a screenshot of an exemplary application tile 200 for use in an application-centric user interface, such as the user interfaces in FIGS. 1A and 1B. In this embodiment, the application name 210, the application graphical representation (eg, icon representation, photographic representation, or artistic representation) 220, and publisher name 230 are included in tile 200. Alternatively, you can have fewer items, add more items, or indicate different items.

FIG. 2B is a screenshot of an alternative example application tile 200 for use in application-centric user interfaces such as the user interfaces in FIGS. 1A and 1B. In this embodiment, the application name 210, the application graphical representation (eg, icon representation, photographic representation, or artistic representation) 220, and publisher name 230 are included in tile 200. Also included is a date display for the application (eg, when the application was last run or when the application was published) 240, and a link 250 to the application details (eg the detail page). Alternatively, you can have fewer items, add more items, or indicate different items.

FIG. 2C is a screenshot of an alternative example application tile 200 for use in application-centric user interfaces such as the user interfaces in Figures 1A and 1B. In this embodiment, the name of the application, the graphical representation of the application (eg, icon representation, photographic representation, or artistic representation) 220, and the publisher name 230 are included in tile 200. It also includes an information link 270 that points to new information available from the publisher of the application. When an information link is activated, the new information can be presented. Alternatively, you can have fewer items, add more items, or indicate different items.

FIG. 2D is a screenshot of an alternative example application tile 200 for use in application-centric user interfaces such as the user interfaces in Figures 1A and 1B. In this embodiment, the application name 210 and the application graphical representation (eg, icon representation, photographic representation, or artistic representation) 220 are included within the tile 200. It also includes a view of one or more tasks that can be performed on the application 280. Such a display initiates task execution when activated. The task display 280 can be included in any of the tiles described herein and can be used to initiate any of the tasks described herein. Alternatively, you can have fewer items, add more items, or indicate different items.

In any of the examples, activation (eg, clicking or double-clicking) of the graphical representation 220 allows each application to be launched (eg, executed).

(Example 4) (Alternative example user interface display) Figure 3A shows screenshot 300 of an alternative example application-centric user interface. In this example, task pane 322 shows one or more tasks 352A, 352B, 352N that can be performed on the application represented by representations 342A, 342B, 342N. For example, the user can select one of the applications 342A, 342B, 342N and then (eg, by clicking) tasks related to the application 352A, 352B, 352N. Alternatively, you can have fewer items, add more items, or indicate different items. If desired, the items displayed in pane 332 can be limited to the representation of the application (for example, the representation of other items or files does not appear).

Figure 3B shows screenshot 300 of another alternative example application-centric user interface. This example is similar to FIG. 3A, but also includes an activity center task pane 362 (e.g. similar to task pane 140 in FIG. 1) and information pane 372 (e.g. similar to information pane 150 in FIG. 1). ..

In any of the examples, the respective applications can be launched (eg, executed) by activating (eg, clicking or double-clicking) the graphical representations 342A, 342B, 342N. Information about an application (such as an application) can be attached to the application representations 342A, 342B, and 342N. Alternatively, you can have fewer items, add more items, or indicate different items.

(Example 5) (Alternative example user interface display) FIG. 4 is a block diagram showing the relationships between pages in an application-centric user interface. In this discussion, the user interface displays 402, 412, 414, 416 are referred to as "pages". When first entering the application-centric user interface, the user is presented with an introductory page 402. When activating an item (eg, detail item 250 in FIG. 2) to direct information about a particular application (eg, application detail page), the respective application pages 412, 414, 416 are presented. The user can then return to welcome page 402 from any of application pages 412, 414, 416 (by activating the item presented on pages 412, 414, 416). As shown, two or more application pages 412, 414, 416 can be included. Pages are sometimes collectively referred to as "application activity centers" because various activities related to the application can be performed through the pages.

An additional page, not shown, which is implemented in some cases, includes an application wish list. In addition, fewer pages or different pages can be implemented. Introductory page 402 can take any form of the application-centric user interface shown above (eg, interface 100 in FIG. 1).

(Example 6) (Example application detail page) FIG. 5A is a screenshot of an exemplary detail page 500 that presents information about the application. Such a detail page 500 can be displayed when a detail page for each application is requested by the user (by activating detail item 250 in Figure 2), with the introductory page 402 shown in Figure 4. Can be related. In this embodiment, application representations (eg, icon representations, photographic representations, or artistic representations) 512 are shown along with information 514 about the application (eg, application name). In addition, one or more task items 518 are shown. Activating a task item (by clicking on the task item) performs the associated task (eg, one of the tasks described herein).

Figure 5B shows a screenshot of an alternative example detail page 500 that presents information about the application. Such a detail page 500 can be displayed when a detail page for each application is requested by the user (eg, by activating detail item 250 in FIG. 2), and the introductory page 1902 shown in FIG. Can be related to. Pane 510 shows various items that function in the same way as described with respect to FIG. 5B. In addition, detail page 500 includes an up-to-date information pane 520 showing information link 524. Information link 524 directs to information that is indicated to be activated.

In addition, detail page 500 includes installation details pane 530. For example, you can view the file location of a program, installation size, installation date, copyright information, preferred operating system, patch history, or any combination thereof. Alternatively, you can have fewer items, add more items, or indicate different items. Application publishers can create additional custom categories. The additional custom category may or may not include an object code module created by the publisher, but this module provides additional information about the application for the convenience of the user.

Further, detail page 500 includes a saved document pane 540 with saved document representations 542A, 542B, and 542C for the application. The activation of the expression opens the document (for example, launches the application if appropriate).

Finally, in this embodiment, the Capability Rating System Details pane 550 shows the recommended capability rating for the application, the minimum capability rating for the application, and the capability rating for the user computer. A capability rating outlines the computing resources needed to run an application and gives an easily understandable rating. In this way, the user can be warned in advance that the application will not work or will not work well on the user computer.

In any of the examples, activation (eg, click or double-click) of the graphical representation 512 allows each application to be launched (eg, executed).

(Example 7) (Example application-centric user interface in the operating system shell) Any of the user interfaces shown in the examples can be presented as part of the user interface for the operating system shell. For example, if the operating system shell points to a computer's file system, the user interface can be presented as part of the file system.

FIG. 6 is a screenshot of an exemplary application-centric user interface 624 presented as part of the user interface 600 for the operating system shell. In this embodiment, the operating system shell presents the application-centric part 624 of the user interface within a window on the desktop 602, along with pane 642 and activable item 652.

Other windows 632, 634 can be presented by the operating system shell or application. The operating system shell can present other windows, such as windows for navigating within the file system and windows that make up the operating system.

(Example 8) (Example relationship of application-centric user interface in operating system shell) FIG. 7 is a block diagram 700 showing the relationships between folders 702, 712, 714, 716 presented by the operating system shell as part of the user interface. In this embodiment, the user is directed from the "My Computer" folder 702 to either the "My Applications" folder 712 or any other folder 714, 716. Folders can be customized for each user, so that the operating system presents a different set of applications for each user. If desired, the application can be installed across each user at the same time so that the application appears in multiple users' folders.

In practice, the folder can be represented as an icon or list representation of the items in the folder, and in the case of the application folder 712, it presents a richer display, as shown in any of the examples herein. can do.

(Example 9) (Example application metadata file) Figure 8 shows the contents of an exemplary application metadata file. Application metadata files can store information about an application and can be used to present information about the application in an application-centric user interface.

Therefore, File 800 contains the name of the application, the name of the publisher of the application, the location where the link data that presents the information link is found, the capability rating system information, the graphical representation of the application, and many other items, or any combination thereof. Can be included.

If desired, File 800 can comply with markup (eg XML) conventions. File 800 can be associated with the signature of the source and the integrity of File 800. In addition, file 800 can contain information (eg, hyperlinks) for previewing (eg, getting a demo version) or purchasing an application.

(Example 10) (Example relationships between operating system shells, application metadata files, and applications) FIG. 9 is a block diagram 900 showing an exemplary relationship between an operating system shell 910, a database of application metadata files 920, and multiple applications 960A, 960B, 960N. Thus, the operating system shell 910 can present any of the user interfaces described herein by reference to the application metadata file 920 for applications 960A, 960B, 960N. The shell can also configure and launch the applications 960A, 960B, 960N as desired through the selections received from the user at the user computer via the user interface.

(Example 11) (Example relationship between application metadata file and special metadata file) FIG. 10 is a Venn diagram 1000 showing the relationship between the application metadata file 1010 and the special application metadata file 1020. For example, a special application metadata file is suitable as an application metadata file (eg, it follows the same schema), but also contains additional information that is specific to a special application (eg, a game).

(Example 12) (Obtaining an example of an application metadata file) Application metadata files can be obtained in a variety of ways. For example, if the application is provided via a CD-ROM, the application metadata file can be stored on the CD-ROM and copied from there. If the application is downloaded over a network connection, the file can be downloaded as part of the installation package. Alternatively, as described herein, application metadata files can be acquired without installing the application, such as when adding an application to a wishlist or when the application is hosted on a remote website. .. In some cases, the application metadata file can be embedded in or referenced by the application manifest. Such a manifest can be provided to indicate an item in a software package.

FIG. 11 is a screenshot of an exemplary page 1100 (eg, a web page) with a review of an application for which an application metadata file can be obtained. In this example, hyperlink 1116 is presented as part of page 1100. Activation of hyperlink 1116 acquires an application metadata file (for example, the file is stored in database 920 and added to the wishlist).

Application metadata files can be identified by a special file extension (eg ADF, GDF), or other mechanism. HTML tags in hyperlinks can tell you that a file should be added to your wishlist. A digital signature can be attached to the file to authenticate the source and integrity of the file.

(Example 13) (Example usage of metadata file for installing software) The software can be installed using any of the application metadata files described herein. FIG. 12 shows an exemplary method 1200 for achieving application installation via an application metadata file.

In step S1210, the application metadata file is acquired. Files can be acquired in a variety of ways, as described herein.

The S1220 evaluates the application. Even before purchasing or installing an application, the operating system shell can facilitate user evaluation by providing information about the application or a link to the online community.

On the S1230, buy the application. Billing information regarding application software purchases can be collected electronically and the purchase can be accomplished by activating (eg, clicking) the item. Items can be manipulated by referring to the information in each application metadata file.

On the S1240, install the application. The installation can proceed according to a variety of methods, including the standard methods provided by the operating system.

Method 1200 can also be applied to upgrades. For example, upgrades can be evaluated prior to purchase. In some cases, upgrades may be of a nature that would be considered separate applications (eg, major upgrades).

Method 1200 can also be described as a method for marketing software. By presenting the user with an easy way to add a representation of the application to the operating system shell before purchasing the software, the user can more easily become part of the online community associated with the application. In this way, the user can collect relevant information about whether or not to purchase an application or upgrade, and when to purchase it. In addition, application publishers can maintain contact with users via information links. In this way, you can achieve your target online marketing without flooding your online community with a large number of email campaigns.

(Example 14) (Handling of example legacy applications) When installing an operating system shell that supports application-centric user interface technology (for example, when upgrading an operating system), one or more applications may already be present on your computer. Such applications may not exist in the interface unless the user manually adds them.

Such applications are sometimes referred to as "legacy" applications. Users may strongly desire such applications, and therefore users may be disappointed and may not take advantage of the features described herein if they do not appear within the appropriate user interface.

Various methods can be used to facilitate the handling of legacy applications. Figure 13 shows one such method 1300. Method 1300 can be run by the operating system in the background while other applications are running. Over time, Method 1300 can identify applications on the computer. For example, if the operating system includes routines that scan files in the file system, Method 1300 can operate as part of the operating system routines. Alternatively, method 1300 can be performed all at once.

The S1310 finds files during scanning. The files to consider can be limited to executable files. The S1320 then determines if the file matches the fingerprint stored as part of the operating system. Fingerprinting techniques can be used, resulting in verification that the application is a specific application rather than an exact copy. If indicated to match, details about the file (eg, location and associated application metadata filename) can be stored in the list. You can then consider the list (for example, when you launch or restart the application activity center) and database the application metadata files (for example, after that, if you have the proper configuration). It can be added to the database 920).

Fingerprints and associated application metadata files can be provided as part of an operating system, operating system upgrade, or on remote internet resources such as web servers. The latter provides flexibility in providing running updates to the database of information about legacy applications. For example, application metadata files can be generated for more popular application titles, so that they are ultimately clarified within the application activity center. Any number of other techniques can also be used.

(Example 15) (Example of application to games) Any of the techniques described herein are advantageous when applied to games. You can implement a game-specific activity center (eg, not showing other applications). The game can be handled via a special application metadata file. Such files can contain additional information about the game, such as how to achieve a multiplayer online game scenario.

In addition, the Game Activity Center can be implemented as part of the user interface for the operating system shell to provide a way for users to easily manage and launch games. For example, the operating system shell can present a "My Games" folder that presents the Game Activity Center. In addition, the instant messaging function can be incorporated into the game activity center. Also, if the operating system supports contact objects, multiplayer online games can be started via references to contact objects.

Various other game-specific features can be incorporated. For example, an application tile can contain a link to play a recently saved game. The detail page allows you to graphically draw n (eg 3) recently saved games (eg via mini-screenshots showing the game state when they were saved).

(Example 16) (Example game detail page) FIG. 14 is a screenshot showing an exemplary detail page 1400 for a game in a game activity center, which can be used as an application detail page in any of the techniques described herein. In this example, the game detail pane 1430 is a graphic representation of the game (eg icon representation, photographic representation, or artistic representation) 1412, game name, publisher comment, publisher name, publisher website. Includes, the date the game was installed, the size of the game, and the date the game was last played. Such information can be stored, stored or acquired within the game's metadata file (eg, a special application metadata file). For example, certain information that changes frequently (eg, the date the game was installed, the date the game was last played) can be stored outside the game's metadata file. The size of the game is determined when the game is run.

In addition, pane 1430 includes information link pane 1420, information link pane 1420 contains information link 1424, and information link 1424 directs to information indicated to be activated (eg, by clicking).

Task pane 1440 shows various tasks that can be accomplished with respect to an application (eg, by activating task items). For example, you can play the game by activating Button 1444. Other tasks include continuing the last saved game, playing in multiplayer, playing with peers, reviewing and installing updates (for example, upgrading or updating data files). Browse saved games, search for new games, find similar games, visit online forums about games, visit online communities about games, join online chat rooms about games, modify or uninstall games To, go to the (official) web page of the game, check compatibility information about the game, check security information about the game, view usage history (for example, when you played, how much you played, how much Frequently played), including viewing program files.

In practice, you can have fewer items, add items, or indicate different items. In any of the examples, each application can be launched (eg, executed) by activating (eg, clicking or double-clicking) the graphical representation 1412.

(Example 17) (Example multiplayer online game scenario) FIG. 15 shows a block diagram 1500 showing an exemplary multiplayer online game scenario. In this embodiment, the user computer 1510 and one or more fellow computers 1520A, 1520B, 1520N are in contact with the game server 1530 via the network 1540. Each human player can be at the user computer and fellow computers. In this way, players can participate in the same game and compete for or cooperate with the game. The number of users can be much higher than shown, and in some scenarios one of the user computers or fellow computers can serve as a game server.

Contact information about fellow computers 1520A, 1520B, 1520N can be stored on the fellow list. You can examine the list to determine if a companion is playing a particular game or any game. If you want, you can also get consent before adding the contact to your peers list.

Although multiplayer online games have become very common, there are still some cases where it is somewhat difficult to start a multiplayer online game. Various techniques described herein can simplify the operation of the user interface of a multiplayer online game.

(Example 18) (Example relationship to achieve a multiplayer online game scenario) FIG. 16 is a block diagram showing an exemplary relationship 1600 for achieving a multiplayer online game scenario. In this embodiment, the operating system shell 1610 interfaces with the instant messaging function 1630 and the gaming application 1620. In addition, if desired, the operating system shell 1610 can interface with one or more contact objects 1640 (eg, stored in a database accessible by the operating system shell 1610).

The operating system shell 1610 can be operated to interface with the user (eg, through the operating system shell, or the interface for the instant messaging feature 1630) to receive instructions regarding scenarios for multiplayer games. The shell 1610 can then provide the gaming application 1620 with the appropriate information to start or participate in a multiplayer online game.

In some cases, a multiplayer online game can be started or participated in via contact object 1640 (eg, a user interface that presents information about an individual such as a friend or companion).

(Example 19) (Example user interface for achieving multiplayer online game scenarios) FIG. 17 is a screenshot of the user interface 1700 to achieve an exemplary multiplayer online game scenario as shown in FIG. In this embodiment, the user interface 1700 includes a user pane 1710, which includes a computer user display 1712 (eg, a photo), a user name 1714, a user's online status display 1716, and a user's display. Includes a motto (eg, a concise message to identify a user's accuracy among peers or new entrants).

The embodiment also includes a chat pane 1720, which allows the user to continue an online chat session with other potential players (eg, via the messenger feature). You can enter text in box 1722 and activate button 1724 to send a message via a chat session.

The Invited Companion Pain 1730 includes a display (eg, a photo) of the companion (eg, a remote user) that the user has invited to play. It also includes the name of the mate and the quality rating of the mate's connection (for example, indicating whether a dial-up or broadband connection is available to the mate). Added companions can be invited via button 1732. In this example, the user is hosting the game (eg, managing who is invited to the game), but other scenarios are possible.

This embodiment further includes a game pane 1740 that displays function 1742 and a list of games 1744.

Finally, the user (or companion at each computer) activates the ready button 1752 to indicate that he is ready to start playing. When you press the start button 1756, your friends will be displayed in the friend pane 1730 and the game will start. You can refer to the information in the game metadata file to determine how to launch the game (eg, how to get your friends to play an online game).

The user interface 1700 can be reached in various ways. For example, a game detail page can present a link (eg, "play in multiplayer" or "play with peers"), and interface 1700 is presented when the link is activated. Alternatively, the user may be chatting with a peer via message exchange software and may be offered the option of being presented with user interface 1700. Finally, when showing a list of peers (eg, in a contact list represented by a contact object), you can offer an option to receive the presentation of user interface 1700. If desired, the list can automatically include related players in the Companion Pain 1730.

Before presenting the interface 1700, another user interface can be presented in which the user selects a companion (for example, "Who would you like to play this game with?"). Such a user interface can present a variety of contact-related options (eg, "My Contacts", "Friends' List", "Family Address Book", "Recent Contacts", "Mobile Contact". , Filters, or any combination thereof).

(Example 20) (Rich expression of examples through the content rating system) In any of the game embodiments described herein, games can be associated with each other through content ratings in the content rating system. For example, a game can be rated to be accepted by all viewers or only by adult (mature) viewers. The system can address different content rating conventions (eg, in different countries).

A user (for example, having an administrator password) can configure the system to be designated to play a game with a given content rating by a user. For example, parents can specify that their children can only play games rated as "all viewers."

(Example 21) (A rich representation of examples through the capability rating system) In any of the embodiments described herein, an application can be associated with a capability rating system (CRS). For example, a high rating can indicate that more computing resources are needed to run the game. You can specify the lowest capability rating as well as the recommended capability rating for your application. This rating can be compared to the rating of the user computer to see if the application works or works well on the user computer.

In addition, discrete system requirements can be specified for the application. For example, some applications may require special hardware (eg graphics tablets or game controllers).

Depending on the option, it may not be possible to present based on the specified requirements. In practice, the user can launch the application even if it meets only the minimum system requirements.

When an application is added to the wish list, a capability system rating can be presented for that application. In this way, the user can easily determine whether or how well the application will run on the user computer.

(Example 22) (Rich representation of examples about the application) In any of the embodiments described herein, one or more combinations of the following may be presented with respect to the application (eg, as part of a tile for the application, or on the application detail page, or a combination thereof. On both sides): System requirements (eg CRS), installation details (eg installation folder, size on disk, date of installation), patch history (eg filtered for the application), and a summary of saved documents.

(Example 23) (A rich expression of examples about the game) When presenting a game in any of the examples herein, the following additional items may be presented: an online game currently in progress, an overview of saved games, and preferred input device assignments.

(Example 24) (Rich representation of examples about the application) When creating a list of applications in any of the examples herein, the list can be ordered by any of a variety of criteria (eg, alphabetical order by name, genre order, issuer order, most recently executed). Order, size on disk).

When presenting application tiles, you can include: links to new publisher content available, links to online forums, links to fan sites. When presenting the game, you can present the following: content rating, whether or not your peers are online, a list of peers online, or any combination thereof. When presenting multiple games at once, it is possible to present an overview of the games for which updates are available.

(Example 25) (Example application tile) For any of the application tiles presented herein, the tile can contain a variety of information. The tile can contain any combination of the following information: installation date, release date (highlighted if present on the wishlist), last run, run time, publisher and logo, developer name And logos, installation routes, patch history, CRS data, update notifications, extended descriptions, screenshots, saved documents.

Tiles that perform tasks when activated can contain various items (for example, items behave as hyperlinks or commands). Possible tasks include: Find new applications, consider and install updates, browse system features, check for updates, browse my wishlist, return to introductory page, run, last Continue documents, view saved documents, modify / delete, find similar applications, visit forums, join chat rooms, register applications, view usage history, view installation folders, Check online for updates about this application, email friends about this application, buy this application, download demos.

In addition, or otherwise, in embodiments dealing with games, the following information can be included: saved game, last play, time played, number of peers playing. You can include the following tasks: configure pair rental control, play, continue the last saved game, play with friends, join an internet / LAN game session, join a new internet / LAN game Create, find new games, browse saved games, find similar games, register games online.

(Example 26) (Illustrated game-centric implementation of tiles) FIG. 18A is a screenshot of an exemplary application tile 1800 for use in a game-centric user interface, such as the game-centric version of the user interface in FIGS. 1A and 1B. In this embodiment, the application name 1810, the application graphical representation (eg, icon representation, photographic representation, or artistic representation) 1820, and publisher name 1830 are included in tile 1800. In addition, you will be presented with a date of last play 1840, a link to details (eg a detail page) 1850, and a task item 1860 to launch a multiplayer online game. Alternatively, you can have fewer items, add more items, or indicate different items.

FIG. 18B is a screenshot of an alternative example application tile 1800 for use in a scenario similar to FIG. 18A. This embodiment includes indication 1880 that a companion is online with respect to the game. Alternatively, you can have fewer items, add more items, or indicate different items. For example, task item 1860 can be included.

(Example 27) (Example software update) When a user chooses to update or upgrade software, that feature can be integrated with other updates on the computer. For example, if your computer's software (eg, operating system) includes a download manager, you can launch the download manager to get updates or upgrades.

(Example 28) (Example function) A wide range of functions can be achieved through the techniques described herein. In addition to those shown here, users can add applications, see patch history for applications, and see upgrades or other applications.

(Example 29) (Example implementation of application metadata file) The application metadata file can contain any information appropriate to achieve the user interface described herein. Table 1 shows the example fields in the application metadata file.

<tables num="1"><img file="JP2010277603A_D0001.tif" /></tables>

(Example 30) (Information link) User interface items that contain information links (eg, information link 150 in pane 150 in Figure 1, link 270 in Figure 2, information pane 372 in Figure 3, link 524 in pane 520 in Figure 5, and information link 1424 in pane 1420 in Figure 14). Can implement an information link by the inventor of the present application.

(Example 31) (Example computing environment) FIG. 19 and the following description are intended to provide a brief general description of a suitable computing environment for implementation. This technique is described in the general context of computer executable instructions for computer programs running on computers and / or network devices, but can also be implemented in combination with other program modules. In general, a program module includes routines, programs, components, data structures, etc. that perform a particular task or implement a particular abstract data type. Further, those skilled in the art will appreciate that the present invention can be performed in other computer system configurations including multiprocessor systems, microprocessor-based electronic devices, minicomputers, mainframe computers, network appliances, wireless devices and the like. This extension allows it to run in a network computing environment or on a stand-alone computer.

Referring to FIG. 19, the exemplary system for implementation includes a conventional computer 1920 (such as a personal computer, laptop, server, mainframe, and various other computers), where the conventional computer 1920 is a processor. It includes 1921, system memory 1922, and system bus 1923, which connects various system components, including system memory, to processing equipment 1921. Processing devices include Intel x86 by Intel and others, including Cyrix, AMD, Nexgen, Pentium® processors, and compatible microprocessors, Alpha, MIPS Technology by Digital, NEC, IDT, Siemens, and MIPS, IBM and others by others. It can be any of a variety of commercially available processors, including PowerPC by Motorola. Dual microprocessors and other multiprocessor architectures can also be used as processor 1921.

Some system buses include memory buses or memory controllers, peripheral buses, and local buses that use any of a variety of traditional bus architectures, such as PCI, VESA, AGP, microchannel, ISA, and EISA. It may be any of the bus structures of the type. System memory includes read-only memory (ROM) 1924 and random access memory (RAM) 1925. A basic input / output system (BIOS) containing basic routines that help transfer information between elements in the computer 1920, such as during startup, is stored in ROM 1924.

The computer 1920 further includes a hard disk drive 1927, for example a magnetic disk drive 1928 for reading and writing removable disks 1929, and an optical disk drive 1930 for reading, for example, a CD-ROM disk 1931 or reading and writing other optical media. The hard disk drive 1927, the magnetic disk drive 1928, and the optical disk drive 1930 are connected to the system bus 1923 by the hard disk drive interface 1932, the magnetic disk drive interface 1933, and the optical drive interface 1934, respectively. The drive and its associated computer-readable medium provide non-volatile storage of data, data structures, computer-executable instructions, etc. for computer 1920. The description of computer-readable media above refers to hard disks, removable magnetic disks, and CDs, but other types of computer-readable media such as magnetic cassettes, flash memory cards, digital video disks, and Bernoulli cartridges are also included. Those skilled in the art should understand that it can be used in the exemplary operating environment.

In addition to implementation 1956, several program modules can be stored in drives and RAM 1925, including operating system 1935, one or more application programs 1936, other program modules 1937, and program data 1938.

The user can enter commands and information into the computer 1920 via a keyboard 1940 and a pointing device such as a mouse 1942. The above and other input devices are often connected to the processor 1921 via a serial port interface 1946 coupled to the system bus, but by other interfaces such as a parallel port, game port, or universal serial bus (USB). You can also connect. The monitor 1947 or other type of display device is also connected to the system bus 1923 via an interface such as the video adapter 1948. In addition to monitors, computers typically include other peripheral output devices (not shown) such as speakers and printers.

Computer 1920 operates in a network environment that uses a logical connection to one or more remote computers, such as remote computer 1949. The remote computer 1949 may be a server, router, peer device, or other common network node, and generally includes many or all of the elements described for computer 1920, but only the memory storage device 1950 is illustrated. The logical connections illustrated include a local area network (LAN) 1951 and a wide area network (WAN) 1952. Such networking environments are common in offices, enterprise-wide computer networks, intranets, and the Internet.

When used in a LAN networking environment, the computer 1920 is connected to the local network 1951 via a network interface / adapter 1953. When used in a WAN networking environment, the computer 1920 typically includes a modem 1954, or other means of establishing communication over a wide area network 1952, such as the Internet (eg, via LAN1951 and a gateway or proxy server 1955). Modem 954 can be internal or external and is connected to system bus 1923 via the serial port interface 1946. In a network environment, the program module shown for computer 1920 or a portion thereof can be stored in a remote memory storage device. It will be appreciated that the network connection shown is an example and other means of establishing communication links between computers can also be used.

(Example 32) (Example application programming interface) Figures 20-26 are excerpts 2000 of programming languages that specify an exemplary application programming interface (API) for performing application installations through the techniques described herein. The described functions can be used, for example, when installing an application. Although this embodiment will be described by taking a computer game as an example, this technique can also be applied to general applications.

In addition, although the example code is in the C # language, any number of other programming languages can be used to implement the application programming interface. Further, in this embodiment, the application is embedded in the operating system shell via a folder named "My Games", but a method of incorporating the application in another folder name or another operating system shell can also be used.

Table 2 shows the family of example functions for the API, and Table 3 shows the example functions for the API. In this example, "supported" titles are non-web non-legacy titles supported by the System, but web and legacy titles are still supported by the System. You can add functions to make them fewer or implement different functions.

<tables num="2"><img file="JP2010277603A_D0002.tif" /></tables>

<tables num="3"><img file="JP2010277603A_D0003.tif" /></tables>

(Example 33) (Example schema for use with application metadata) Figures 27-32 specify an exemplary XML Schema 2700 for use with application metadata. In this embodiment, the metadata is stored in "ADF" (eg, a file with a .adf file extension).

In this example, according to this schema, the metadata contains an application identifier (eg, "applicationid") that identifies the application that can be installed within the Application Activity Center and what the application can do when installed in the Application Activity Center1. A visible description of one or more tasks (eg, "description" for "task data") and data that indicates how to launch one or more tasks that the application can perform when installed in the Application Activity Center (eg, "description"). It can contain "invoke data" for "task data") and arguments for one or more tasks that the application can perform when installed in the Application Activity Center (eg "arguments" for "task data"). Is specified. You can add elements to this schema to make it less or define different elements.

(Example 34) (Example schema for use with computer game metadata) Figures 32 to 35 specify an exemplary XML Schema 3200 for use with application metadata. In this example, the metadata is stored in "GDF" (eg, a file with a .gdf file extension), and the "ADF" schema in Figures 27-31 is extended. You can also add elements with respect to the schema to make them fewer or define different elements.

(Example 35) (Example schema for use with computer game metadata) Figures 36-38 specify exemplary metadata 3600 for a particular application called "Freecell". Metadata for other applications will vary accordingly.

(Example 36) (Example schema for use with application manifest) Figures 39-41 specify an example XML Schema excerpt for use with the application manifest. In this embodiment, the manifest may specify application metadata by referencing an "ADF" or "GDF" file, such as that described in Figures 36-38, or any other application metadata file. it can. By incorporating a reference to the metadata file in the manifest, the metadata file is considered part of the software package for the application and can be distributed as a software package. You can also add elements with respect to the schema to make them fewer or define different elements.

(Alternative) Since the principles of the inventions of the present inventors have been described and illustrated with reference to various embodiments, it will be understood that the arrangement and details of the embodiments can be modified without departing from such principles. It should be understood that, unless otherwise specified, the programs, processes, or methods described herein relate to, or are not limited to, any particular type of computer equipment.

In any of the examples showing user interfaces, such an interface can be implemented as a graphical user interface (GUI). Although the icon representation of the program is illustrated, box art for the application (eg, a physical box-like photo of the software) can be used instead in any of the examples.

Some examples have been shown as general purpose computers, but the technology can be applied to console game scenarios instead.

According to the teachings described herein, various types of general purpose / dedicated computer equipment can be used, or various types of general purpose / dedicated computer equipment can perform operations. The elements of the embodiment shown as software can also be implemented as hardware and vice versa.

The techniques of one or more embodiments may also be incorporated into any of the other embodiments.

In light of the many possible embodiments to which the principles of the invention of the present inventors can be applied, the embodiments described in detail are merely examples and should be regarded as limiting the scope of the invention of the present inventors. Please understand that it is not. Rather, the inventors claim that all embodiments within the scope and spirit of the claims are the inventions of the present inventor.