WO2002086709A2

WO2002086709A2 - Method and system for plug-in mapper

Info

Publication number: WO2002086709A2
Application number: PCT/US2002/012710
Authority: WO
Inventors: Dipto Chakravarty; Jack Tam; Maryam Norouzi; Jordan Xu; Khanh Nguyen; Edward Jenkins; Malick Fall; An Hoang
Original assignee: Artesia Technologies, Inc.
Priority date: 2001-04-23
Filing date: 2002-04-23
Publication date: 2002-10-31
Also published as: WO2002086709A3

Abstract

Systems, methods and mediums are provided for dynamically determining the file type, determining the media format and the player (103), validating the file type combination (107), and picking the correct player for the combination (109). Information is provided representative of a set of candidate video file types corresponding to video files, including candidate media formats and candidate players corresponding to each candidate video file type. Also provided is information representative of a specific video file to be played. In connection with the video file to be played, a selection is made of at least one corresponding media format from the candidate media formats, and of at least one corresponding media player from the candidate players. Information representative of the selected media format and the selected media player is output, preferably in a HTML file (113). Optionally, the invention includes launching the selected player for the file.

Description

METHOD AND SYSTEM FOR PLUG-IN MAPPER

CROSS-REFERENCES TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application Serial No. 60/285,269, filed April 23,2001, expressly incorporated herein by reference.

BACKGROUND OF THE INVENTION

Field of the Invention

The present invention concerns computer-related and/or assisted methods, systems and computer readable mediums for appropriately mapping video files. More specifically, it relates to providing video viewing support extensible to a variety of file types, for example while launching video players from a web browser. Related Art

With the various video players available to users, incompatibility issues may be noted. This would be the case, for example, with the introduction of SMIL and ASX files. For example, there is a problem of association with a SMIL to its proper player.

SMIL file formats are supported by three free video players, which are mentioned by way of example: Windows™ Media Player, Quicktime™ and Real Player™. Quicklime can only play SMIL files containing Quicktime files(.mov). The problem, however, is associating the correct mime- type to the SMILfile in order for the correct video player to be launched by the browser. In addition, if new players are introduced, the user must be able to create or alter the video player to support his/her new player.

Thus, there remains a need for dynamic methods to select and associate appropriate video players with given file formats. There also remains a need to adapt to additional video file types, and to be extensible to new players and mime-types. Futher, there remains aneed for the settings of the solution to be configurable or changed. Moreover, the there remains a need for such a system and method which is scalable for possibly large and/or small user bases.

SUMMARY OF THE INVENTION

The present invention alleviates the problems of the conventional techniques described above by dynamically determining the file type, determining the media format and the player, validating the file type combination, and picking the correct player for the combination.

In one or more embodiments of the present invention, there is provided a method, system, and/or a computer program product for determining, validating and/or launching one or more players for one or more video files. It includes providing information representative of a set of candidate video file types corresponding to video files, including candidate media formats and candidate players corresponding to each candidate video file type. It also includes providing information representative of a specific video file to be played. It further includes selecting, for the video file to be played, at least one corresponding media format from the candidate media formats. It further includes selecting, for the video file to be played, at least one corresponding media player from the candidate players.

Also, it includes outputting information representative of the selected media format and the selected media player.

Optionally, the invention includes launching the selected media player.

According to other options, the invention includes adding or removing at least one additional media format to the candidate media formats, and/or adding at least one additional player to the candidate players. According to one or more embodiments, the invention includes adding or removing at least one additional video file type, and at least one corresponding media format, and at least one corresponding player. According to one or more embodiments, the outputted representative information includes an HTML file, having at least one of an obfuscated and direct HTTP path representing the video file to be played, and an indication of a mime type corresponding to the selected media player.

Optionally, the invention provides that the set of candidate media formats and set of candidate players are stored in at least one table, and wherein the selection among candidates is performed using at least one tabular summation.

According to one or more embodiments of the present invention, the set of candidate media formats is at least one of: video/avi, video/mov, video/real, video/mpeg2, video/wma,and video/asf; and/or the set of candidate players is at least one of: RealPlayer, WindowsMediaPlayer, QuickTime, and Ligos.

According to one or more embodiments of the present invention, the selected media player is launched from at least one of: a browser, a call from an application, and the Internet.

BRIEF DESCRIPTION OF THE FIGURES

The above mentioned and other advantages and features of the present invention will become more readily apparent from the following detailed description in the accompanying drawings, in which: Figure 1 is a process flow diagram showing one example of the plug-in mapper for processing in the present invention.

Figure 2 is a logic flow diagram showing one example of generating an HTML for use with the present invention.

Figure 3 is a block diagram illustrating a high level class model for use in accordance with one or more embodiments of the present invention.

Figure 4 is a block diagram showing a logic flow for personalization, in accordance with one or more embodiments of the present invention. Figure 5 is an example of a user interface for indicating file properties, for use with one or more embodiments of the invention.

Figure 6 is a block diagram of a computerized plug-in mapper which may be used in connection with one or more embodiments of the present invention. Figure 7 is a player table illustrating a test case.

Figure 8 is a media format table for the test case of Figure 7.

Figure 9 is a OS table for the test case of Figure 7.

Figure 10 is a validation matrix for determining given mime types, for use in connection with one or more embodiments of the present invention. Figure 11 is an example of a view real media video format on a windows client, for video/real, for use in connection with one or more embodiments of the present invention.

Figure 12 is an example of a subset of the validation matrix with a column summation, for use in connection with one or more embodiments of the present invention.

Figure 13 is an example of PDL containing realmedia, avi, and Quicktime on Windows, according to one or more embodiments of the present invention.

Figure 14 is an example of a PDL containing two mpeg2 videos Windows, according to one or more embodiments of the present invention.

Figure 15 is an example illustrating an administrator adding a new media player (Ligos™).

Figure 16 is an example of a modified media format table, according to one or more embodiments of the present invention.

Figure 17 is an example of a modified player table, according to one or more embodiments of the present invention

Figure 18 is another example of a modified media format table, according to one or more embodiments of the present invention.

DETAILED DESCRIPTION

The following detailed description includes many specific details. The inclusion of such details is for the purpose of illustration only and should not be understood to limit the invention. Throughout this discussion, similar elements are referred to by similar numbers in the various figures for ease of reference. In addition, features in one -embodiment may be combined with features in other embodiments of the invention.

Figure 1 is a process flow diagram showing one example of the plug-in mapper for processing in the present invention. The user inputs a file for personalization 101, described in more detail below in connection with Figure 4. The media format player table 103 is determined, and the appropriate player table 105 is also determined, for the particular file. A plug-in mapper is provided and accepts one or more of the following inputs: (1) a URL, or other path such as an HTTP path to the object to embed into an HTML code to be output. The path could be an obfuscated path or an absolute path; (2) an indication representing the operating system (OS)of the requesting client machine; (3) an indication representing the media format of one or more objects represented in the URL; and/or (4) a time code, representing the time segments to play for the corresponding file.

At step 107, the mapper validates the file type combination. At step 109, the mapper picks the correct player for the combination . At step 111, the mapper generates the metafile. At step 113, the mapper generates and outputs the HTML. The HTML that is output preferably contains the URL to the generated metafile, as well as the Mime-type of the correct player to use.

The process of generating the HTML for use by a calling class undergoes a process, described in Figure 2, a logic flow diagram showing one example of generating an HTML for use with the present invention. The process validates the file type combination. A matrix is generated of media formats and video players, if optional personalization is provided. Otherwise, a generated matrix can be created at initialization for use as a default. The Matrix may be built from a media format table..

The matrix is looked up to determine if the combination is valid. A list of players is returned, which can play the combination (not all combinations are valid). The system picks the correct player for the combination. It looks up the player table for the requesting OS and picks the player with the highest priority from the list returned by validation. The system generates a metafile. For the selected player, it looks up the player table to determine what metafile format should e generated. The content of the metafile is generated. The

URL of the metafile is returned.. The system also generates the HTML for the player's plugin (<embed>tag), including the mime type of the plugin and the URL path to the obfuscated metafile

As illustrated in Figure 2, according to one or more embodiments, at step201,the system determines whether there are multiple mime types. If so, it determines at step 202 whether this particular combination is supported. If it is not supported, an error is indicated. On the other hand, if the combination is supported, or if there are not multiple mime types, the system picks the player at step 203. At step 205, the system picks the metafile format (optionally). At step 207, the system generates and outputs the HTML.

Figure 3 is a block diagram illustrating an example of a high level class model for use in accordance with one or more embodiments of the present invention. In this particular object model, "Asset" 301 is associated with "Model" 303. "Model" 303 is aggregated with "Field" 305. "Field"

305 generalizes "ScalarField" 307 and "TabularField" 309. "ScalarField" 307 is aggregated from

"TabularField" 309.

Figure 4 is a block diagram showing a logic flow for personalization, in accordance with one or more embodiments of the present invention. The user makes a selection 401, including string title, string name, name value items, int. selected index, and/or int size. At block 403, the user makes a single selection, including selection first item, and string selection of the title. At block 407, the user selections a box, including a string prompt, a string section,, and vector selections. At block 409, the user selects the ISP, including selection Boxes (previously discussed), string saver class name, and string instruction. At block405, the user performs a multi selection., including selection of second (or subsequent) name, and string hidden name.

Figure 5 is an example of a user interface for indicating file properties, for use with one or more embodiments of the invention. In this particular example, the user adds or removes one or more fields. Available fields are displayed, such as for example Bounding Box, Color Usage, etc. Also, the user can add or remove displayed fields, such as for example asset name, asset description, asset version, content type, imported by, date of import, latest version indication, reference source, source physical type, and/or source physical location, etc. These fields are provided by way of example, and others could be substituted and/or added depending on the implementor's and/or user's preference Figure 6 is a block diagram of a computerized plug-in mapper which may be used in connection with one or more embodiments of the present invention. The meta file content 601 is input into a standard generate metafile routine. The mime types is sent for validation to the PlayerMap615. The player map provides validated mime types to the playerlhfo617. The Playerlnfo checks whether the information is null at step607. If so, then at step 605, the system returns the

HTML object. On the other hand, if the result is not null, then the system creates a metafile according to the data, including a metafile 609, a SMIL file 611, and/or an ASX file 613. Also, the system generates a corresponding HTML file, utilizing a standard routine. This creates a handler object according to, preferably, a fully qualified handler name. Also generated are a player handler 619,agenericplayer handler 621, a real player handler 623, and a quicktime handler 625. The system creates a string containing an HTML block or player to function properly.

Figure 7, 8 and 9 are a player table, media format table, and OS table, respectively, illustrating a base test case. Many variations of the test case are possible. However, the test case is one possible basic example of the present invention in action. Figure 7 illustrates a player table including player name 701, corresponding mime 703, corresponding metafile type 705, and assigned preference 707. Figure 8 is a media format table for the test case of Figure 7. It includes a mime type 801, an OS identification 803, and the player name 805. Figure 9 is a OS table for the test case of Figure 7. It includes the OS identification 901 and OS name 903. Figure 10 is a validation matrix for determining given mime types, for use in connection with one or more embodiments of the present invention. It includes the video name 1001, windows mediaplayerl003, quicktime indication 1005, and realplayer indication 1007. The system determines which player will be used to play the given mime types by using the validation matrix. The row is located that contains the given mime type, and the sum of each column is computed. The system locates the column that has the highest sum. If this value is not greater than or equal to the number of the given mime types, then this combination is determined to be invalid. Otherwise, this column represents the player that will be used to play the mime types. Once the player is found the system uses the player table to determine the embed mime and meta type to generate the HTML and meta-file. Figure 11 is an example of a view real media video format on a windows client, for video/real, for use in connection with one or more embodiments of the present invention. It includes the video/real indication, and the sum 1101, the windows media player indication 1003, the quicktime indicationl005,and the realplayer indication 1007. At a first step, the sum of each column is determined, and the column is located that has the highest value, in this case the real player column

1007. Next, the system selects the row from the player table that has the value "Real Player" within the name column. This row has an embed mime entry of "application/x_pn_realaudio_plugin" and meta entry "SMIL".

Figure 12 is an example of a subset of the validation matrix with a column summation, for use in connection with one or more embodiments of the present invention. It includes an indication of windows media playerl203, quicktime indicationl205, and realplayer indication 1207. As a first step, the system calculates the sum of each column and locates the column with the highest value, in this case the RealPlayer column 1207. Next, the system selects the row from the player table that has the value "realplayer": within the Name column. This row has an embedmime entry of "application/x_pn_realaudio_plugin"and meta entry "SMI". The system now has the values to be able to generate the HTML and meta files.

Figure 13 is an example of PDL containing realmedia, avi, and Quicktime on Windows, according to one or more embodiments of the present invention. It includes a name indication 1301, windows media player indication 1303, quicktime indication 1305,and realplayer indication 1307. The system calculates the sum of each column and locates the column that has the highest value. The mime type combination is invalid because the highest value is not greater than or equal to the number of the given mime types.

Figure 14 is an example of a PDL containing two mpeg2 videos Windows, according to one or more embodiments of the present invention. It includes a name indication 1401, a windowsmedia player indicationl403, a quick time indication 1405, and a realplayer indicationl407. The system calculates the sum of each column and locates the column that has the highest value, in this case the windows media player column. The system then selects the row from the Player Table that has the value "Windows Media Player" within the Name column. This row has an embedmime entry of "application/x_mplayer2" and meta entry "ASX". The system now has the values to be able to generate the HTML and meta files.

Figure 15 is an example illustrating an administrator adding a new media player (Ligos™). The table includes a player name indicationl501, an embed mime indication 1503, a metafile type indication 1505,and a preference indication 1507. Figure 16 is an example of a modified media format table, according to one or more embodiments of the present invention. It includes the mime type 1601, OS identification 1603, and player name 1603. The administrator adds a new row to the player table, and to the media format table, for each media format that the player can play. Figure 17 is an example of a modified player table, according to one or more embodiments of the present invention It includes playername indication 1701, embed mime indication 1703, metafile type 1705, and preference indication 1707. Theuser changes the player preference values for the Ligos and Windows media player within the player table. If there are two players that can be used to play a mime type then the system will choose the player that has the highest preference.

Figure 18 is another example of a modified media format table, according to one or more embodiments of the present invention. This table includes a mime type indication 1801, an OS identifierl803, and a player name 1805. The administrator adds the mime type to the media format table. Preferably, the administrator adds a row for each player that can play the new mimetype, to allow for additional flexibility.

While this invention has been described in conjunction with the specific embodiments outlined above, many alternatives, modifications and variations will be apparent to those skilled in the art. Accordingly, the preferred embodiments of the invention as set forth are intended to be illustrative and not limiting. Various changes may be made without departing from the spirit and scope of the invention as defined in the following claims.

For example, the invention may also be implemented as a distributed computer system (e.g., the Internet or an intranet) rather than as a single computer; some of the distributed system might include embedded systems. Further, the programming may be distributed among processing devices and/or computers. Similarly, the processing could be controlled by a software program on one or more computer systems or processors, or could be partially or wholly implemented in hardware. Also, the invention could be launched from a browser, or could be launched from any other application calling for use in connection with video files.

Claims

WHAT IS CLAIMED IS:

1. A computer-implemented method of determining, validating and/or launching one or more players for one or more video files, comprising the steps of: (A) providing information representative of a set of candidate video file types corresponding to video files, including candidate media formats and candidate players corresponding to each candidate video file type;

(B) providing information representative of a specific video file to be played;

(C) selecting, for the video file to be played, at least one corresponding media format from the candidate media formats;

(D) selecting, for the video file to be played, at least one corresponding media player from the candidate players; and

(E) outputting information representative of the selected media format and the selected media player.

2. The method of claim 1, further comprising the step of launching the selected media player.

3. The method of claim 1, further comprising the step of adding or removing at least one additional media format to the candidate media formats, and/or adding at least one additional player to the candidate players.

4. The method of claim 1, further comprising the step of adding or removing at least one additional video file type, and at least one corresponding media format, and at least one corresponding player.

5. The method of claim 1, wherein the outputted representative information includes an HTML file, having at least one of an obfuscated and direct HTTP path representing the video file to be played, and an indication of a mime type corresponding to the selected media player.

6. The method of claim 1, wherein the set of candidate media formats and set of candidate players are stored in at least one table, and wherein the selection among candidates is performed using at least one tabular summation.

7. The method of claim 1, wherein the set of candidate media formats is at least one of: video/avi, video/mov, video/real, video/mpeg2, video/wma,and video/asf.

8. The method of claim 1, wherein the set of candidate players is at least one of: RealPlayer,

WindowsMediaPlayer, QuickTime, and Ligos.

9. The method of claim 2, wherein the selected media player is launched from at least one of: a browser, a call from an application, and the Internet.

10. A computer program product for use in determining, validating and/or launching one or more players for one or more video files, the computer program product comprising:

(A) at least one computer readable medium; (B) instructions, provided on the at least one computer readable medium, for providing information representative of a set of candidate video file types corresponding to video files, including candidate media formats and candidate players corresponding to each candidate video file type;

(C) instructions, provided on the at least one computer readable medium, for providing information representative of a specific video file to be played;

(D) instructions, provided on the at least one computer readable medium, for selecting, for the video file to be played, at least one corresponding media format from the candidate media formats;

(E) instructions, provided on the at least one computer readable medium, for selecting, for the video file to be played, at least one corresponding media player from the candidate players; and

(F) instructions, provided on the at least one computer readable medium, for) outputting information representative of the selected media format and the selected media player.

11. The product of claim 10, further comprising instructions for launching the selected media player.

12. The product of claim 10, further comprising instructions for adding or removing at least one additional media format to the candidate media formats, and/or adding at least one additional player to the candidate players.

13. The product of claim 10, further comprising instructions for adding or removing at least one additional video file type, and at least one corresponding media format, and at least one corresponding player.

14. The product of claim 10, wherein the outputted representative information includes an HTML file, having at least one of an obfuscated and direct HTTP path representing the video file to be played, and an indication of a mime type corresponding to the selected media player.

15. The product of claim 10, wherein the set of candidate media formats and set of candidate players are stored in at least one table, and wherein the selection among candidates is performed using at least one tabular summation.

16. The product of claim 10, wherein the set of candidate media formats is at least one of: video/avi, video/mov, video/real, video/mpeg2, video/wma,and video/asf.

17. The product of claim 10, wherein the set of candidate players is at least one of: RealPlayer,

WindowsMediaPlayer, QuickTime, and Ligos.

18. The product of claim 11, wherein the selected media player is launched from at least one of: a browser, a call from an application, and the Internet.