Application program centrol user interface technology

The first application-centric user interface technology technical field This technical field relates to human-computer interaction such as when a computer user is combined with a user interface given by software.

The part of the disclosure of the patent document contains copyrighted material. When it appears in patent and trademark patent documents or archives, the copyright owner does not object to any form of copying in patent documents or patent disclosures, but retains all copyright rights in other respects.

BACKGROUND Since entering the computer age, different human-computer interaction technologies have been developed and implemented to make computers easier to use. For example, the current generic graphical user interface ("GUI") paradigm makes it easier to select a program because the user can click on an icon associated with the desired program instead of typing in the program name.

However, with the advent of more complex computers, there have been seemingly more complex graphical user interfaces that can provide multiple levels of selection. Providing a user with so many levels of choices in the user interface makes finding the desired option an unwelcome piece of work. As a result, the user tries to avoid the choice that is actually desired. So a large number of choices become an obstacle for users.

SUMMARY The described technology can provide different user interface arrangements and related functions. For example, different application center user interface technologies can be used.

In some instances, an application center user interface is provided to the user. In some examples, users can add, update, and run programs from the central part of the application.

In some instances, the application center user interface includes an action center through which users can perform different actions related to the application.

In one described implementation, the application program includes game-related software. For example, to provide users with available games and related information. In some instances, Yu Hua runs multiplayer online games.

In one aspect of the present invention, a method for providing an application center graphical user interface is provided

200410039768.6 No. device, the device includes: a device used to define an interface area, the interface area contains a graphical description of multiple applications, wherein the area is limited to applications; used to select applications displayed in the area A device for displaying the selected application program in the area; a device for displaying multiple selectable task items executable by the application program; a device for activating one of the selectable task items in the area A device for performing the selected task on the selected application displayed in the display; and a device for providing the application center user interface as a part of the operating system shell user interface.

In yet another aspect of the present invention, there is provided a method for providing an application center graphical user interface. The method includes: defining an interface area that contains graphical descriptions of multiple applications, wherein the area is only limited to applications. Program; select the application program to be displayed in the area to display the selected application program in the area; display multiple optional task items executable by the application program; activate one of the optional task items to display the selected application program in the area; The selected task is executed on the selected application displayed in the area; and the application center user interface is provided as a part of the operating system shell user interface.

From the following detailed description of the illustrated embodiments in conjunction with the accompanying drawings, other features and advantages become more obvious.

BRIEF DESCRIPTION OF THE DRAWINGS Figures 1A and 1B are screen shots of a typical application center user interface.

Figures 2A, 2B, 2C, and 2D are tiles of typical applications used in application center user interfaces such as the user interface in Figures 1A and 1B.

Figures 3A and 3B are screen shots of the user interface of the optional typical application center.

Figure 4 is a structural diagram showing the relationship between pages in the application center user interface.

Figures 5A and 5B are screen shots of typical detail pages that provide information to the application.

Figure 6 is a screen shot of a typical application center user interface provided as part of the user interface of an operating system shell.

Figure 7 is a structural diagram of the relationship between folders provided as part of the user interface of an operating system shell.

Figure 8 shows the contents of a typical application metadata file.

Figure 9 is a structural diagram showing the relationship between an operating system shell, application metadata files, and application programs.

Figure 10 shows the relationship between application metadata files and special application metadata files

200410039768.6 Venn diagram.

Figure 11 is a screen shot of a typical review of an application, in which the metafile of an application can be obtained from the application.

Figure 12 is a flowchart showing a typical method for completing application installation via application metadata files.

FIG. 13 is a flowchart illustrating a typical method for adapting traditional applications in the application action center. Figure 14 is a screen shot showing a typical detail page for a game in a game action center.

Figure 15 is a structural diagram showing a typical multiplayer online game solution.

Fig. 16 is a structural diagram showing a typical relationship between instantaneous communication, operating system shell, and game application.

FIG. 17 is a screen shot of a user interface used to implement a typical multiplayer online game solution as shown in claim 15.

18A and 18B are shots of typical application tiles used in a game center user interface such as the game center implementation of the user interface in FIGS. 1A and 1B.

Fig. 19 is a diagram showing the structure of a typical computer system.

Figures 20-26 are programmable language excerpts that specify the user interface of a typical application program that implements application installation through the techniques described herein.

Figure 27-31 specifies a typical XML diagram that uses application metadata. Figure 32-35 specifies a typical XML diagram that uses application metadata with specific game-related metadata. Figures 36-38 are based on the diagrams in Figures 32-35. Specify typical metadata used for gaming applications. Figure 39-41 specifies a typical XML diagram used with the application manifest.

Specific implementation examples]-typical system overview The different embodiments described herein can all use application-centric user interface technology. With the advent of more complex user interfaces, the application center user interface can avoid the disappointing things that infertility can easily discover applications and perform application tasks. For example, application user interface technology treats applications in a special way and includes an area limited to the user interface of the application (for example, other object types such as files are not included in the area). The method is an improvement on a system that only provides applications as part of a file system, which includes files such as

200410039768.6 No. 1 and many other items.

In addition, the different techniques described herein can produce multiple representations of applications, such as those given by the operating system shell. In this case, the application publisher Yumai customizes the shell representation of their application. This technology expands to adapt to different applications from different application publishers.

Example 2-Representation of a typical user interface FIG. 1A shows a screen shot of a typical application center user interface 100. In this embodiment, there are two or more application tiles 122 that can display respective application images in the pane 120. The items displayed in the pane 120 are limited to images of the application program (for example, images of other objects or files are not displayed).

FIG. 1B shows a screen shot of another typical application center user interface 100. In the embodiment, in addition to two or more application tiles 122, there are also a recent application pane 130, a task pane 140, and an information pane 150. In one implementation, one or more of the illustrated panes 130, 140, 150 may be used.

The recently run applications pane 130 may display tiles for one or more (eg, three) recently run applications. Alternatively, some other mechanism can be used to indicate the most recently running application.

The task pane 140 presents one or more tasks suitable for the user interface to perform, such as locating different pages within the user interface. Some tasks may be specific applications, while other tasks may not run on specific applications. In this embodiment, a "view wish list" option is shown. When it is activated (for example, clicked), the "View wish list" option will navigate to a page indicating one or more application catalogs, which are specified by the user in the wish list. For example, a user may consider purchasing the application or has determined that the application is required and will be purchased at the time of publication.

The information pane 150 can give one or more magnets 122, when activated (for example, clicked), to locate a detail page for the application indicated by the link. The links are limited to links with recent information, such as new information generated in the past n days (for example, configured by the user).

In either embodiment, the area of the user interface shown as panes may or may not be the visual boundary between the panes. Therefore, the pane can be selected as an area of the user interface that does not have a visual boundary. In addition, fewer or other items may be included. For example, a Caiweilan can give additional features or options.

Example 3-Typical Tiles To facilitate the presentation of applications in the user interface, an application will be given in the described typical tiles

200410039768.6 Graphical representation of the program and other information related to the application. Figure 2A is a screen shot of a typical application tile 200 used in an application center user interface such as the user interface in Figures 1A and 1B. In this embodiment, the name 210 of the application, the graphical (for example, iconic, camera, and artistic) representation 220 of the application, and the publisher's name 230 are all included in the tile 200. Optionally, fewer, additional, or other items can be shown.

Figure 2B is a screen shot of another selectable typical application tile 200 used in an application center user interface such as the user interface in Figures 1A and 1B. In this embodiment, the name of the application, the graphic (for example, iconic, camera, artistic) representation 220 of the application, and the name of the publisher are all included in the tile 200. It also includes a date indicator 240 for the application (for example, when the application was last run or published) and a link 250 to the application details (details page). Optionally, fewer, additional, or different items can be shown.

Figure 2C is another screen shot of an optional typical application tile used in an application center user interface such as the user interface of Figures 1A and 1B. In this embodiment, the name of the application 210, the graphic (for example, iconic, camera, or artistic) representation 220 of the application, and the name of the publisher are all included in the tile 200. It also contains an information link 270 indicating new information from the publisher of the application. _ Once the information link is activated, new information will be given. Optionally, fewer, additional, or different items may be shown.

FIG. 2D is another screen shot of a typical application tile 200 used in an application center user interface such as the user interface of FIGS. 1A and 1B. In an embodiment, the name 210 of the application program and the graphical (for example, iconic, camera, or artistic) representation 220 of the application program are included in the tile 200. It also contains instructions 280 suitable for one or more tasks performed by the application program. When this indication is activated, the characteristics of the task will be initialized. A task indication 280 can be included in any_tile described herein and can be used to initialize any task described herein. Optionally, fewer, additional, or different items may be shown.

In either embodiment, activating (for example, clicking or double-clicking) the graphical representation 220 will run the corresponding application.

Example 4-Alternative Representative User Interface Representation FIG. 3A shows a screen shot 300 of an alternative typical application center user interface. In this embodiment, the task pane 322 shows one or more tasks 352A, 352B, 352N that can be performed on the application provided by the images 342A342B, 342N. For example, a user can select an application

200410039768.6 No.

One of 342A, 342B, 34N, and then select a task suitable for the application (for example, click) 352A, 352B, 352No optional, can show fewer, additional, or different items. If it is desired, the options displayed in the pane 332 will be limited to the image of the application (for example, no images of other items or files appear).

FIG. 3B shows a screen shot 300 of another optional typical application center user interface. This embodiment is similar to FIG. 3A, and further includes an action center task pane 362 (for example, similar to the task pane 140 of FIG. 1) and an information pane 372 (for example, similar to the information pane 150 of FIG. 1).

In either embodiment, activating (eg, clicking or double-clicking) the graphic images 342A, 342B, 342N will run (eg, execute) the respective application program. The application images 342A, 342B, 342N will be accompanied by information about the application (such as the name of the application, etc.). Optionally, fewer, additional, different items can be shown.

Example 5-Optional Representative User Interface Representation Figure 4 is a structural diagram showing the relationship between pages in the application center user interface. For the following discussion, the user interface representations 402, 412, 414, 416 are referred to as "pages." When entering the application center user interface for the first time, a welcome page 402 is provided to the user. Once activated a project that locates a special application word (for example, Reading Wuyi DETAIL M®) Ayanxi project (Zhuangkou, detailed column in Figure 2), the respective application pages 412, 414, 416 will be provided. The user can then return to the welcome page 402 from any of the application pages 412, 414, 416 (for example, by activating an item on the pages 412, 414, 416). As shown in the figure, two or more application pages 412, 414, 416 may be included. In general, the page is sometimes called the "application action center" because different actions related to the application can be completed through the page.

Additional pages that are not shown but may be implemented include an application wish list. In addition, a few or different pages can also be implemented. The welcome page may adopt any form of the application center user interface shown above (for example, the interface 100 in FIG. 1).

Example 6-Typical Application Program Details Page FIG. 5A is a screen shot of a typical details page 500 that provides information to the application program. When a user requests a detail page for the respective application (for example, activates the detail option 250 of FIG. 2), the detail page 500 may be displayed and the detail page is related to the welcome page 402 shown in FIG. In this embodiment, an image of the application 512 (for example, iconic, camera, or artistic) will be shown along with information about the application. In addition, one or more task items may be shown. By activating the task item (for example,

Click it on 200410039768.6) to perform related tasks (for example, any of the tasks described here).

Figure 5B shows a screen shot of an optional typical detail page 500 that provides information to the application. When a user requests a detail page for the respective application (for example, activating the detail option 250 of FIG. 2), the detail page 500 may be displayed and the detail page is related to the welcome page 1902 shown in FIG. 19. As shown in Figure 5B, pane 510 shows different item functions. In addition, the details page 500 includes a recent information pane 520 showing an information link 524, which is used to locate the indicated information when the information link is activated.

In addition, the details page 500 includes an installation details pane 530. For example, the location of the program file, installation size, data creation, copyright information, preferred operating system, repair history, or a combination of them can be displayed. Optionally, fewer, additional, or different items can be displayed. The application publisher establishes an additional user classification, which may or may not include the object code module established by the publisher, and the object code module established by the publisher is provided for the benefit of the user related to the application. The additional faithful.

Likewise, the detail page 500 includes a save file pane 540 with images 542A, 542B and 542C of the save file suitable for the application. Activating the above image will open the file (for example, run the application if appropriate).

Finally, in this embodiment, the performance level system details page 550 shows the recommended performance level suitable for the application, the minimum performance level suitable for the application, and the performance level of the user's computer. The performance level gives an easy-to-understand level to roughly indicate the computing resources required to execute the application. In this way, the user can be informed in advance that the application program will not run on the user's computer or will not run well.

In either embodiment, activating (eg, clicking or double-clicking) the graphic image 512 will run (eg, execute) the respective application.

Example 7-A typical application center user interface in the operating system shell Any user interface shown in the embodiment will be given as a part of the user interface for the operating system shell. For example, if the operating system shell describes the computer's file system, then the user interface is presented as part of the file system.

FIG. 6 is a screen shot of a typical application center user interface 624 given as part of the user interface 600 of the operating system shell. In this embodiment, the operating system shell provides the application center portion of the user interface 624, the pane 642, and the activatable items 652 in the window of the desktop 602.₀

200410039768.6 The other »632, 634 can be provided through the operating system shell or application program. The operating system shell may provide other windows, such as windows for locating entire files or configuring the operating system.

Example 8-Typical relationship of the application center user interface in the operating system shell Figure 7 is a structural diagram showing the relationship between the folders 702, 712, 714, and 716 proposed as part of the user interface through the operating system shell . In this embodiment, the user profile is located from the "My Compter" folder 702 to My Applications (My Applications folder 712 or any other folders 714, 716. The folder can be customized by each user Therefore, the operating system will provide each user with a different application program group. If it is desired, the application program can be installed on the entire user at the same time, so that the application program appears in the folder of more than one user.

In fact, the folder can be shown as an icon or list image of the items in the folder, or in the case of the application folder 712, the female mouth is shown here like a T-letter to provide a richer representation.

Example 9-Typical Application Metadata File Figure 8 shows the contents of a typical application metadata file. The application metadata file can store information about the application and when the application information is provided in the user interface of the application center, use the drunk metadata file as the address.

Therefore, the file 800 can include the name of the application, the name of the publisher of the application, a location for finding the link data that provides the information link, the performance level system information, the graphic image mark of the application, and many other items, Or some combination of them.

If it is desired, the file 800 may follow a mark-up (eg, XML) protocol. The file 800 can be associated with a signature to verify the data source and integrity of the file 800. In addition, the file 800 may include information about previewing (for example, obtaining a demo version) or purchasing an application.

Example 10-Operating System Shell, Application Metadata File, and Typical Relationship Between Applications Figure 9 is a database showing the operating system shell 910, application metadata file 920, and multiple applications 960A, 960B, 960N A structural diagram of the typical relationship between. In this way, the operating system shell 910 presents any of the user interfaces described herein by referring to the application metadata file 920 for the application programs 960A, 960B, 960N. As expected, via the user interface in the user computer, the shell can also configure and run the application programs 960A, 960B, 960N through selections received from the user.

Example 11-A typical relationship between application metadata files and special metadata files Figure 10 shows a typical relationship between application metadata files 1010 and special metadata files 1020

200410039768.6 Venn diagram of the first series. For example, a special application metadata file can be limited to an application metadata file (for example, according to the same diagram), but it also contains additional information specific to the special application (for example, a game).

Example 12-Typical acquisition of application metadata files Application metadata files can be obtained in different ways. For example, if an application is provided via a CD-ROM, the application metadata file can be stored on it and copied from it. If you download the application through a network connection, the downloaded file will be part of the installation component. Or, as described above, such as when an application is added to a desired list or used for an application managed by a remote site, the application metadata file can be obtained without installing the application. In some cases, application metadata files can be incorporated into the application manifest or referenced by the application manifest. This list is provided in the software package to indicate the project.

FIG. 11 is a screen shot of a typical page 1100 (for example, a web page) with an application program review, and the application program metadata file can be obtained from the above-mentioned application program. In this embodiment, a hyperlink is given as part of the page 1100. Activating the hyperlink will result in obtaining the application metadata file (eg, storing the file in the database 920 and adding it to the wish list).

Application metadata files can recognize SU through special file extensions (for example, ADF, GDF) or other mechanisms. The HTML tag in the hyperlink and the deleted file will be added to the wish list. The file is accompanied by a digital signature so that the data source and integrity of the file can be authenticated.

Example 13_ Use metadata files to install software Use any of the application metadata files described here to install software. FIG. 12 shows a typical method 1200 for completing instant program installation through an application metadata file. In step 1210, an application metadata file is obtained. As mentioned here, documents can be obtained in different ways.

In step 1220, the application is evaluated. By providing magnets to relevant applications or online communities, the operating system shell will make it easier for users to comment on it, even before purchasing or delivering Cheng Yun.

At step 1230, the application is purchased. The billing information for application software purchases can be collected electronically, and the purchase can be completed by activating (for example, clicking) items, which can be operated by referring to the information in the respective application metadata files.

In step 1240, the application is installed. The installation can be performed according to different methods, including the standard methods provided by the operating system.

200410039768.6 Method 1200 is also used for upgrading. For example, evaluate the upgrade before purchasing. In some cases, the upgrade may have the nature of being considered an independent application (for example, a main upgrade).

The method 1200 can also be described as a method of selling software. Before purchasing the software, by providing the user with an image of adding the application to the operating system shell in a simple way, the user will more easily become a part of the online community related to the application. In this way, users can collect relevant information when deciding whether or when to purchase an application or upgrade. In addition, application publishers keep in touch with users through information links. In this way, the target online sales can be completed without causing the online community to suffer from a large number of emails.

Example 14: A typical adaptation of a traditional application Once an operating system shell supporting the application center user interface technology is installed (for example, an operating system upgrade), then there will be one or more existing applications on the computer. The application does not appear in the interface until the user manually adds it.

This application is sometimes referred to as a "traditional" application. The user is very interested in this application, so if they fail to appear in the appropriate user interface, the user will be disappointed and not be able to take advantage of the features described here.

In order to promote the adaptation of traditional applications, different methods can be used. Figure 13 shows one such method 1300. When other applications are running, the method 1300 is executed by the operating system in the background. Over time, the method 1300 can identify applications on the computer. For example, if the operating system includes a routine that can scan files in the file system, then the method 1300 runs as part of the operating system routine. Optionally, the method 1300 can be run simultaneously.

In step 1300, a file is found during scanning. The files envisaged are limited to executable files. Then, in step 1320, it is necessary to determine whether the file matches the fingerprint stored as part of the operating system. Fingerprint technology can be used so that the application is identified as a special application rather than an exact copy. If the indications match, the details of the file (for example, the location and the name of the related application metadata file) are stored in the list. Next, consider the list (for example, when running or continuing to execute the application action center), and add the application metadata file (for example, if any, after appropriate configuration) to the database (for example, database 920 ).

The fingerprint and related application metadata files are provided as part of the operating system, operating system upgrades, or provided on remote network resources such as web servers. In the latter case, the information database of traditional applications can be flexibly provided with real-time updates. For example, to generate application meta

The 200410039768.6 data file is used for multiple common application titles, so that they appear in the application action center. Other techniques can also be used.

Example 15 _Typical game application Any of the techniques described here can be effectively applied to games. The execution is limited to one action center of the game (for example, other applications are not described). A special application metadata file can be used to adapt the game. Such files can include additional information about the game, such as how to implement a multiplayer online game solution.

In addition, when executed as part of the user interface of the operating system shell, the Game Action Center can provide users with an easy way to manage and run games. For example, the operating system shell Yukeng provides a "My Games" folder, through which the game action center can be provided. Further, the instant information function can be incorporated into the game action center. If the operating system supports a contact object, then refer to the contact object to start a multiplayer online game.

It can also incorporate other different game-specific functions. For example, the application tile includes a link to run a recently saved game. In a detail page, n (for example, 3) recently saved games can be graphically depicted (for example, when the game is saved, the game situation is described through the smallest screen shot).

Example 16-Typical Game Details Page FIG. 14 is a screen shot showing a typical details page 1400 of the game in the Game Action Center and the details page can be used as an application detail page in any of the techniques described herein. In this embodiment, the game details pane 1430 includes graphics (for example, iconic, camera, or artistic) images of the game, the name of the game, the description of the publisher, the name of the publisher, the URL of the publisher, and the installation of the game. The date of the game, the size of the game, and the date the game was last run. The information can be stored in the game's metadata file (for example, a special application program metadata file) or be stored or obtained separately. For example, certain information that changes frequently (for example, the date the game was installed and the date the game was last run) can be stored outside of the game's metadata file. When the game is executed, Itachi determines the size of the game.

In addition, the pane 1430 includes an information link pane 1420, the information link pane includes an information link 1424, when the information link is activated (for example, clicked), it will locate the information link task pane 1440 indicating the deactivation instruction. Different tasks that can be completed by the application (for example, by activating task options) are listed. For example, by activating the button 1444, the game is run. Other tasks include; continuing the last saved game, multiplayer games, playing with partners, checking and installing updates (for example, updates or update age files), viewing saved games, finding new games, finding similar games, accessing online games Forum, visit tour

200410039768.6 The online community of the first play, join the online chat room of the game, change or uninstall the game, go to the game's (official) webpage, check the compatibility information of the game, check the security information of the game, check the usage history (for example, when is it running, How long to run, how often to run), and show the program files.

In fact, additional, fewer, or different items can be displayed. In either embodiment, activating (eg, clicking or double-clicking) the graphical image 1412 will run (eg execute) the respective application program.

Example 17-Typical Multiplayer Online Game Scheme Figure 15 shows a structural diagram 1500 illustrating a typical multiplayer online game scheme. In this embodiment, the user computer 1510, and one or more partner computers 1520A, 1520B, 1520N are via the network 1540 is connected to the U game server 1560. The respective players can be on the user's and partner's computers. In this way, players can participate in the same game in order to compete or cooperate in the game. The number of users far exceeds those shown in the figure. In some solutions, one of the user's or partner computers can act as a game server.

The connection information for the partner computers 1520A, 1520B, and 1520N is automatically stored on a partner list. You can refer to this list when determining whether your partner is playing a specific game or some games. If it is desired, then consent can be obtained before adding the contact to the buddy list.

Although multiplayer online games have become very popular, they still have some difficulties to deal with. The various technologies described here can simplify the user interface operation of a multiplayer online game.

Example 18-Typical Relationship for Realizing Multiplayer Online Game Solution Figure 16 is a structural diagram showing a typical relationship 1600 for realizing a multiplayer online game solution. In this embodiment, the operating system shell 1610 connects the instant information function 1630 and the game application 1620. Similarly, if desired, the operating system shell 1610 can connect one or more connection objects] 640 (for example, through the operating system shell 1610 Stored in an accessible database).

The operating system shell 1610 can be operatively connected to a user (for example, via the operating system shell or an interface for instant information functions) in order to receive instructions about the multiplayer game plan. The shell 1610 then provides appropriate information to the game application 1620 in order to start or join the multiplayer online game.

In some It situations, a multiplayer online game can be started by connecting objects 1640 (for example, a user interface describing information about individuals, such as a friend or partner).

Example 19-A typical user interface for implementing a multiplayer online game solution FIG. 17 is a screen shot of a user interface 1700 for implementing a typical multiplayer online game solution such as shown in FIG. 15. In this embodiment, the user interface 1700 includes a user pane 1710 that includes a portrayal 1712 (for example, a photo) of a computer user, a user name 1714, and whether the user is in

200410039768.6 Line instructions 1716, and the users motto (for example, a short message to identify the users personality among partners or new users).

This embodiment also includes a chat pane 1720 through which the user can maintain an online chat session with other potential players (for example, through a messaging function). Text can be inserted into box 1722 and button 1724 is activated to send a message through the chat pliers.

The invitation f friend pane 1730 contains descriptions of those partners (for example, delete accounts) (for example, Zhaodou, where those partners are invited by the user. It also includes the name of the partner and the quality level of the partner connection (for example, indicating to the user) Whether dial-up or broadband connection is available). Other partners can also be invited through the button 1732. In this embodiment, the user can control the game (for example, control who will be invited to participate in the game). Other solutions are also possible.

This embodiment further includes a game pane 1740 for displaying a function 1742 and a game list 1744.

Finally, an eaday button 1752 can be activated by the user (or partner on their respective computer) to indicate that they are ready to start the game. Once the run button 1756 is pressed, the buddies displayed in the buddy pane 1730 will play the game. The information in the game metadata file can be consulted to determine how to run the game (for example, how to submit a partner to an online game).

The user interface 1700 can be obtained in different ways. For example, the game details page can provide a link (for example, "multiplayer game" or "game with buddies"), and when the link is activated, it will provide an interface 1700. Alternatively, the user can chat with buddies through information software and provide An option through which a user interface 1700 can be provided. Finally, when a partner list (for example, a connection list represented by a connection object) is shown, an option is provided, wherein the user interface 1700 is provided through the partner list. If it is desired, the relevant player can be automatically listed in the buddy pane 1730.

Before the sweet supply interface 1700, another user interface can be provided (for example, "This Lake"), through which the user can select a partner. This user interface can provide different connection-related options (for example, "My Connection", Company Directory", Home Address Book", "Recent Connections", "Cellular Phone Connection Filtering Program, or some combination of them).

Example 20-Typical multiple representations via a content rating system In any of the game examples described here, games are associated with a content rating in a content rating system. For example, a game can be rated as a game acceptable to all audiences or only mature audiences. The system automatically adapts to different content level agreements (for example, from different countries).

200410039768.6 The first user (for example, with the administrator password) configures the system so that certain users are designated to play a certain content level game. For example, parents stipulate that children can only play games rated as "all viewers".

Example 21-Typical multiple representations via a performance rating system In any of the embodiments described herein, the application can be associated with a performance rating system ("CRS"). For example, a higher level of self-slipping indicates that more computer resources are required to run the game. A minimum and recommended performance level can be assigned to the application. This level can be compared with the level of the user's computer in order to know whether the application can run on the computer or run well.

In addition, discrete system requirements can be specified for the application. For example, an application requires specialized hardware (for example, a graphics tablet or game controller).

Certain options may not be given based on specified requirements. In fact, users are allowed to run applications even if they only meet the minimum system requirements.

When it is added to the wish list, the performance system level can be provided to the application. In this way, the user can easily determine whether or how the application program runs well on the user's computer.

Example 22 - Typical multiple representations of the application In any of the embodiments described here, one or more are provided to the application (for example, as part of the application tile, on the application details page, or both) A combination of the following: system requirements (for example, CRS), installation details (for example, installation folder, disk size, date of installation), repair history (for example, application screening), and save document summary.

Example 23-Typical multiple representations of games. When a game is provided in any of the embodiments, self-certification gives the following additional items: online game currently in progress, save game deletions, and input device allocation.

Example 24-Typical multiple representations of applications. When enumerating applications in any of the embodiments, it follows multiple criteria (for example, by name/letter, by type, by publisher, by recent run, disk size) To arrange the list.

When the application tile is given, the following content can be included: content that can be used by the high-profile version; links to online forums; links to the location of fans. When a game is given, the following content can be given; content level, whether a partner is online, a list of partners online, or some combination of them. When more than one game is given at a time, a summary of the game will be given, for which updated information is available.

200410039768.6 Example 25-Typical Application Tiles For any application tile shown here, the tile includes different information. The tile includes any combination of the following information: installation date, factory date (if the desired list is emphasized), last run, run time, publisher's name and logo, developer's name and logo, installation path, patch history , CRS data, update notifications, extended descriptions, screen shots, saved documents.

Tiles can include different items. When the item is activated, a task is executed (the item is represented by _ hyperlinks or a command). Possible tasks include: finding a new application, checking and installing updates, viewing system performance, verifying updates, viewing my wish list, returning to the Ouying page, running, continuing the last document, viewing the saved document, changing/deleting , Find the same application, visit the forum, join the chat room, register the application, check the usage history, display the installation folder, check the online update of the application, send a friend about the application, buy the application , Download the demo.

Additionally or alternatively, in the implementation of the adaptation game, the following information may be included: save the game, the last run, the run time, and the number of game partners. Can include the following tasks: configure parental control, run, continue the last saved game, play with a partner, try to recognize the Internet or LAN game session, store a new Internet or LAN game, find a new game, view the save Games, find similar games, register for online games.

Example 26-Typical Game Center Implementation of Tiles Figure 18A is a screen shot of a typical application 1800 used in a game center user interface such as the Game Center version user interface of Figures 1A and 1B. In an embodiment, the name of the application 1810, the graphic (icon, photographic, or artistic) image 1820 of the application, and the name of the publisher 1830 are included in the tile 1800. In addition, the last running data 1840, the link 1850 to the Yo section (for example, the detail page), and the task option 1860 for running the multiplayer online game are given. Optionally, fewer, additional, or different items may be shown.

Figure 18B is a screen shot of an optional typical application tile 1800 used in a scheme similar to Figure 18A. This embodiment includes an indication 1880 for instructing a partner to play online. Optionally, a few, additional, or different options may be shown. For example, the task option 1860 is included. Example 27-A typical software update When the user chooses to update or upgrade the software, this function can be combined with other update functions on the computer. For example, if the computer software (e.g., operating system) includes a download manager, then

200410039768.6 Call the download manager to get updates or upgrades.

Example 28-Typical functions. Many different functions can be achieved by the techniques described here. In addition to those shown, users can add applications, see the patch history of the applications, and see upgrades or other applications.

Example 29-A typical implementation of an application metadata file An application metadata file can include any information suitable for obtaining the user interface described herein. Table 1 shows the typical fields of the application metadata file. Table 1-The text of Yuan Ka Wen Ji Duan

<td></td><td>description</td>

<td>Application ID</td><td>A unique identifier (for example, GUID) used for issuance. The next major version of the application will get a new ID</td>

<td>ProductFamily ID</td><td>An identifier used for the product family (for example, GUID). For example, MICROSOFT MONEY 2002 and MICROSOFT MONEY 2003 have the same family ID, even though they have different application Qs</td>

<td>ParentApplicationlD</td><td>For complete application systems and expansion packages</td>

<td>Information</td><td>Metadata block for users who have not yet installed the application. Use in the "will appear image</td>

<td>Common TaskData</td><td>Activate information for common application tasks for applications</td>

Example 30-Information Links .For those related to information links (for example, 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 window in Figure 14 The information link 1424) of the grid 1420 is the option of the user interface. The information link can be realized according to the technology described in the US Patent Application, that is, the US patent filed by Ivan et al. entitled "Providing Information Links via the Internet" The application and agent record abstract number 3382-64291, which is incorporated herein as a reference and is filed with this application.

Example 31 Typical Computing Environment Figure 19 and the following discussion are intended to provide a concise, general description for implementing a suitable computing environment. Although these technologies are described in the general case of computer executable instructions of computer programs running on computers and/or network devices, these technologies can also be executed in combination with other program modules.

200410039768.6 Generally, these program modules include routines, programs, components, data structures, etc., used to perform specific tasks or implement specific abstract data types. Moreover, these technologies can be implemented in other computer system configurations, and include multi-processor systems, microprocessor-based electronic technologies, small computers, large computers, network devices, wireless devices, and so on. Its expansion can be implemented in a networked computing environment or a stand-alone computer.

Referring to FIG. 19, an implemented typical system includes a traditional computer 1920 (such as a personal computer, a laptop computer, a server, a mainframe computer, and various other computers). The computer includes a processing unit 1921, a system memory 1922, and a system bus 1923 that can couple different system components. The system components include from the system memory to the processing unit 1921. The processing unit can be any commercially available processor, including Intel x86, Pentium and compatible microprocessors of Intel and other companies including Cyrix> AMD and Nexgen; Alpha of Digital; MIPS, NEC, IDT of MIPS technology, Siemens, and others; and IBM and Motorola's PowerPC dual processor and other multi-processor technologies can also be used as the processing unit 1921 ο The above system bus can be any of a variety of bus structures, including storage bus and storage control Device, peripheral bus, and local bus. The local bus uses any different traditional bus technology, for example, PCI, VESAAGR microchannel, ISA and EISA. The system memory includes Read Only Memory (ROM) 1924 and Random Access Memory (RAM) 1925. A basic input/output system (BIOS) includes some basic routines that facilitate the transfer of information between elements in the computer 1920, such as during startup, the system can be stored in the ROM 24.

The computer 1920 further includes a hard disk drive 1927, a magnetic disk drive 1928, for example, reading or writing from a removable disk, and an optical disk drive 1930, for example, reading a CD-ROM disk or reading or writing from other optical media. The hard disk drive 1927, the magnetic disk drive 1928, and the optical disk drive 1930 are respectively connected to the system bus via a hard disk drive interface 1932, a magnetic disk drive interface 933, and an optical drive interface 1934. These drives and their associated computer-readable media provide computer 1920 with non-volatile storage of data, data structures, computer-executable commands, etc. Although the above description of computer readable media mentions hard disks, removable disks and CDs, those skilled in the art should understand other types of computer readable media such as tape cartridges, flash memory cards, digital video disks, Bernoulli cassette tapes, etc. It can also be used in a typical operating environment.

A plurality of program modules may be stored in the drive and RAM 1925. The plurality of program modules include an operating system 1935, one or more application programs 1936, other program modules 1937, and a program data device 193 &amp; also include a device 1956.

200410039768.6 The user can input instructions and information to the computer 1920 through a keyboard and a pointing device such as a mouse 1947. These devices and other input devices are usually connected to the processing unit 1921 via a serial port interface 1946, which is coupled to the system bus, But it can also be connected through other interfaces, such as parallel port, game port and universal serial interface (USE). The monitor 1947 or its type display device may also be connected to the system bus 1923 through an interface such as a video adapter. In addition to the monitor, the computer usually includes other peripheral output devices (not shown), such as speakers and printers.

In a networked environment, the computer 1920 uses logical connections to one or more remote computers such as the remote computer 1949 to operate. The remote computer 1949 may be a server, router, equivalent device, or other public network node, and usually includes some or all of the elements related to the computer, although only one memory storage device 1950 is shown. The logical connection includes a local area network (LAN) 1951 and a wide area network (WAN) 1952. The networking environment is generally an office, an inter-enterprise computer network, an intra-enterprise network, and the Internet.

When used in a LAN networking environment, the computer 1920 is connected to the local network 1951 via a network interface or adapter 1953. When used in a WAN networking environment, the computer 1920 generally includes a modem 1954 or other device capable of establishing communication (for example, via a LAN 1951 and a gateway or proxy server 1955) on a wide area network such as the Internet. The internal or external modem 1954 is connected to the system bus 1923 via the serial port interface 1946. In a networked environment, the program module related to the computer 1920 or a part of it may be stored in a remote memory storage device. It should be understood that the network connection shown is just an example, you can use the example of establishing communication between computers 32-Typical Application Programming Interface Figure 20-26 is a programming language summary 2000, the detailed description is described here by using The technology implements a typical application programming interface ("API") for application installation. For example, when an application is installed, the functions described can be used. Although this embodiment is performed with reference to related computer games, these techniques can generally also be applied to other applications.

Similarly, although the code of this embodiment is in C# language, many other programming languages can also be used to implement the application programming interface. In addition, this embodiment shows that the application program can be incorporated into the operating system shell via a folder named "My Games", but it can also be incorporated into the operating system shell using other folder names or methods.

200410039768.6 Table 2 shows the typical series of functions used for the API, and Table 3 shows the typical functions used for the API. In this embodiment, a "supported" title is a non-web page, non-traditional title supported by the system; web pages and traditional titles are still supported by the system. Additional, fewer, or different functions can be implemented.

Table 2-Typical API function series

<td>Function series</td><td>description</td>

<td>AddXXX</td><td>Install an application into "My Games"</td>

<td>UninstallXXX</td><td>Uninstall an application from "My Games"</td>

<td>IsXXXInstalled</td><td>Check if there are special applications installed in "My Games"</td>

<td>GetXXX</td><td>Return to the list of applications in "My Games"</td>

Table 3-Typical API functions

<td>Features</td><td>description</td>

<td>AddLegacyTitle</td><td>Install traditional apps into the game action center</td>

<td>AddWebTitie</td><td>Install the web application 5 Burnt Play Action Center</td>

<td>AddSupportedTitle</td><td>I found a supportive clan Ci An Mi Chang Bo Zuo Center</td>

<td>GetMyGamesApps</td><td>Retrieve the application list in the game action center</td>

<td>GetMyGamesS^pportedApps</td><td>Retrieve the list of supported applications in the game action center</td>

<td>GetMyGamesLegacyApps</td><td>Retrieve a list of traditional applications in the game action center</td>

<td>GetMyGamesWebApps</td><td>Retrieve the list of installed web applications in the game action center</td>

<td>IsAppInstalled</td><td>Check whether the specified application is installed in the game action center as any type of application</td>

<td>IsLegacyTitlelnstalled</td><td>Check whether the specified application is installed in the game action center as a traditional application</td>

<td>IsWebTitlelnstalled</td><td>Check whether the specified application is installed in the game action center as a web application</td>

<td>UninstallWebTitle</td><td>Remove a page title from the game action center</td>

<td>UninstallSupportedTitle</td><td>Remove a supported title from the game action center</td>

<td>UninstallLegacyTitle</td><td>Remove a traditional title from the game action center</td>

Example 33-A typical scenario using application metadata Figures 27-31 detail a typical XML scenario 2700 using application metadata. In this embodiment, the metadata is stored in an "ADF" (for example, a file with the .adf file extension).

In this embodiment, the scheme stipulates that the metadata can include: the identification can be installed in the action of the application

200410039768.6 The application identifier of the application in the first mind (for example, "applicationid"); when the application is installed in the application action center, the displayable description of one or more tasks that the application can perform (for example, "task data "Description"); when the application is installed in the application action center, instruct how to call the application program to execute a Φ or pin any #stability data (for example, the "call data" of "Ren axis"), and When the application is installed in the application action center, the argument of one or more tasks that the application can execute (for example, the "argument" of the "task data"). The scheme can define additional, fewer, or different elements.

Example 34-Typical Scenario Using Computer Game Metadata Figures 32-35 detail a typical XML that uses application metadata. In this embodiment, metadata is stored in "GDF" (for example, a file with a gdf extension) and expands the "ADF" scheme in Figures 27-31. Additional, few, or different elements can be defined for this scheme.

Example 35-Typical Scheme of Using Computer Metadata Figures 36-38 detail a typical metadata 3600 used for a specific free-wheeling loss named "FreeceU". Thus the Yuan Qi used for its magnetic terminology will be different.

Example 36-Typical scenario using application manifests Figures 39-41 detail an excerpt of a typical XML scenario using application manifests. In this embodiment, the manifest specifies the application metadata by referring to an "ADF" or "GDF" file such as the file described in FIGS. 36-38 or its overuse instantaneous axis file. Chao merges the reference of the Yuannen file into the U list, and the metadata file can be regarded as a part of the software package of the application and can be distributed in it. Additional, fewer, or different elements can be defined for this scheme.

Optionality Although the principles of the present invention have been described and illustrated in conjunction with the various embodiments, it is still recognized that the above-mentioned embodiments can be modified in terms of arrangement and details without departing from the above-mentioned principles. It should be understood that the programs, processes, or methods described herein do not involve or are limited to some specific computer devices, unless otherwise specified.

In any example describing a user interface, the interface may be implemented as graphical user interfaces (GUIs). Although the image display of the program is shown, in any embodiment, a frame technology for the program (for example, an appearance photo of a software physical frame) may be used instead.

Although some embodiments have been shown in general-purpose computers, many techniques can be selectively applied to control game scenarios.

200410039768.6 Different types of general or special computer devices can be used or performed in accordance with the techniques described herein. The units of the embodiments shown in software can be executed in hardware, and vice versa.

One or more of the technologies in implementation can be incorporated into other embodiments.

Considering that the principle of the invention can be applied to many possible embodiments, it should be recognized that the detailed embodiments are only illustrative and should not be taken as a limitation of the scope of the present invention. On the contrary, we claim that all these embodiments as our invention are likely to be within and equivalent to the scope and concept of the appended claims.

200410039768.6