KR100670775B1 - Method for embodying playlist for both index and context of portable media - Google Patents

Abstract

A method for implementing an index/context-combined playlist of a mobile device is provided to use a context type playlist in the mobile device having an index type playlist and offer support of a higher speed than the context type playlist in case of the index type playlist. A context type playlist file is searched from the mobile device and is registered to an index type playlist file database. The registered context type playlist file is parsed. It is checked whether the first signature code representing the context type playlist file is present(S230). If the first signature is present, it is checked whether the second signature code representing file information for the context type playlist file is present(S270). If the second signature is present, it is checked whether the same file name as the file name written in the context type playlist file is searched from the file database(S290). The passed context type playlist file is converted in the index type playlist file by additionally registering an index of the file having the searched same name to the index type playlist file(S300).

Description

{Method for embodying playlist for both index and context of portable media}

1 is a diagram illustrating an example of a M3U playlist according to the prior art.

2 is a diagram illustrating an example of a basic file database DB according to the prior art.

3 is a diagram illustrating an example of an indexed playlist according to the prior art.

4 is a flowchart illustrating a process of finding and registering a contextual playlist file according to an exemplary embodiment of the present invention.

5 is a flowchart illustrating a process of analyzing a contextual playlist file and converting an indexed playlist file according to an exemplary embodiment of the present invention.

The present invention relates to a method for implementing an index / context combined playlist of a mobile device, and more particularly, to a technology capable of supporting a contextual playlist for a mobile device having an indexed file database.

In general, WinAMP or Windows Media Player (WMP), which is an MP3 playback program of a computer, supports a function of constructing a list that allows a user to use contents in a desired order. It is called 'playlist', and this is a method of managing the location and playback order of each file by storing them as one file.

This method has the advantage that the user can configure the playback order in the desired format, the advantage is that it is easy to categorize a number of songs stored in a large capacity HDD (HDD), and the playback order between categories It is also widely used because it can adjust the playback order and the playback order within the category.

A typical example is a context-type playlist, such as M3U, which is supported by Winamp, and constitutes a playlist with a specific signature code and a file name in the form of a string.

1 is a diagram illustrating an example of an M3U playlist according to the prior art, FIG. 2 is a diagram illustrating an example of a basic file database according to the prior art, and FIG. 3 is an example of an indexed playlist according to the prior art. The figure which shows.

Referring to FIG. 1, an M3U playlist usually starts with a '# EXTM3U' signature code (hereinafter referred to as a "first signature code") indicating that it is an M3U file, and an 'EXTINF' signature code means a file before each file name. (Hereinafter referred to as 'second signature code'), length, display information, and the like.

In this case, in the case of the contextual playlist, the path should be stored as a string. Therefore, when the length of the path is long or composed of multiple steps, it becomes very complicated. In addition, if the file name is long, the calculation amount is increased drastically because the file name must be compared with each file and searched.

To overcome this shortcoming, different playlists have been proposed for removable media in Microsoft's Windows Media Player. It gives each file an index and builds a playlist with that index. However, in order to implement such an indexed playlist, it is assumed that an information database for each file is basically constructed.

That is, as shown in FIG. 2, information (file name, size, various metadata, starting cluster number on FAT, etc.) about each file is extracted, stored in a database in a predetermined form, and assigned a serial number.

Recently, it is not a big problem because mobile devices extract this information and configure and operate a database. Therefore, it is safe to assume that such a database is configured, and the information of the database is not limited to the above, but can be expanded as needed.

Referring to FIG. 3, the WMP playlist has a simple structure having the number of files belonging to the playlist and the index number of each belonging file among the files registered in the database. Playlists may be managed in a separate database from the file, or may be managed in the same database as the file. For convenience of explanation, it is assumed that a playlist in a file database is also managed as one file.

In other words, indexed playlists do not require complex parsing with separate signature code compared to contextual playlists, do not need to navigate the path each time to find the corresponding file, and the depth of the file name or folder Complexity is not affected.

However, most users are familiar with contextual playlists and have many contextual playlists. Therefore, manufacturers of mobile devices have been required to develop playlists in which their products can support both index and context types.

The present invention is to solve the above problems can be used as a context-based playlist in a mobile device having an indexed database, and to be able to support faster execution speed than the contextual playlist when the index is changed The purpose.

As a technical idea for achieving the above object of the present invention, the present invention includes the steps of determining whether the contextual playlist file in the stored folder of the mobile device; Registering in the database of indexed playlists when a contextual playlist file exists in the folder; Parsing the contextual playlist file registered in the indexed database; And determining whether there are other files in the folder, and repeating the above steps when there are other files in the folder.

According to the present invention, the analyzing and converting the contextual playlist file to the indexed playlist file may include reading the contextual playlist file in a storage device of the mobile device; Checking for the presence of a signature code representing a playlist file; Checking whether a signature code representing file information exists if the signature code exists; Searching for the name of the same file after checking a path of the file through a folder database if a signature code representing file information exists; Searching the file database for a file having the same name by comparing the file names with each other; If there exists a file of the same name, adding the index of the file to the last number of the playlist file and increasing the number of the entire file; is configured to include.

Hereinafter, with reference to the accompanying drawings, the configuration and operation of the embodiment of the present invention will be described in detail.

4 is a flowchart illustrating an embodiment of a process of finding and registering a contextual playlist file in a method of implementing an index / context playlist according to the present invention.

First, after reading the information of the folder contained in the mobile device (S110), it is determined whether the contextual playlist file exists (S120).

If the contextual playlist file exists, it is registered in the indexed playlist file database (S130).

In other words, in an indexed database that does not support contextual playlist files, the playlist is simply treated as a data file in an unidentified format. Therefore, a profiling process is used to find the indexed playlist file and search the indexed playlist. You must register as a file.

Here, the contextual playlist file that can be changed into the indexed playlist file is not limited to the M3U or the like. That is, any type of contextual playlist file having path information of a file belonging to the playlist and configured in a certain format is possible.

Thereafter, after parsing the contextual playlist file registered in the index type database (S140), it is determined whether another file exists in the corresponding folder (S150).

If there are other files in the folder, as in step S110, after reading the file, the same process of determining the existence of the contextual playlist file is performed.

If no other file exists in the corresponding folder, it is determined whether another auxiliary folder exists (S160).

At this time, if another auxiliary folder does not exist, the process of finding and registering the contextual playlist file is terminated.

As described above, referring to FIG. 4, a contextual playlist is searched and registered in an indexed playlist file database, and then an index of files belonging to the contextual playlist is found and configured as an indexed playlist file.

FIG. 5 is a flowchart illustrating an example of a process of analyzing a contextual playlist file and converting an indexed playlist file in a method of implementing an index / context combined playlist according to the present invention. will be.

First, the contextual playlist file is opened (S210) and read from the storage device of the mobile device (S220).

The presence of the signature code indicating the M3U playlist file, that is, the first signature code, such as EXTM3U of the Winamp M3U (S230).

In this process, it is not necessary to read the M3U playlist file into memory, and if the storage device of the mobile device is fast enough, it is also possible to read and use the necessary data from the storage device of the mobile device little by little.

On the other hand, if there is no separate signature code, it can be identified by the file extension. In other words, it can be used as long as it can indicate that the file is a playlist file.

If the signature code is present, the portable storage device reads the data of the signature code (S240).

Next, it is determined whether a signature code for the file information, that is, a second signature code 'EXTINF' exists (S250). In the present invention, the M3U file is described as an example, and the specific value of the second signature code may vary according to the playlist file.

At this time, the title size and title of the title to be displayed on the Winamp program are continuously provided. These information may be used if necessary, but it is assumed that the present invention does not use more than the description.

If there is a second signature code for the file information, the full or relative path of the file is checked.

That is, the folder path is searched through the folder database (S260), which is applicable only when the folder database for the folder path exists or when it is necessary to check the folder path.

Thereafter, after determining whether the folder path exists (S270), if the folder path exists, the name of the same file is searched through the file database (S280).

In this case, the actual name of the file may exist as a long filename, and the path of the file may or may not be used as necessary.

If the file name to search for a file stored in the index database in the form of a long file name is a short file name, a change is necessary. In this case, it is assumed that a long file name is also stored in the index database.

After searching for the same file name through the file database, it is determined whether the same file name exists (S290).

If a file of the same name exists, the index of the file is additionally registered to the last number of the playlist file (S300), and the number of all files is increased (S310).

At this time, when the user selects the play of the playlist converted into the index playlist file, there is no difference between the other index type playlist file and the basic operation. That is, a playlist may be constructed by reading an index from playlist files as many as the number of files on the playlist, and then played back sequentially or randomly according to a user's selection.

In addition, when a change occurs such as when the file index is changed or the file is deleted, the index type playlist file is automatically reconstructed by repeating the above process.

Thereafter, after determining whether there is other data to be read (S320), if there is no data to be read, the conversion process of the index type playlist file is terminated.

As described above, although preferred embodiments of the present invention have been described, the present invention is not limited to the specific preferred embodiments described above, and the technical field to which the present invention pertains without departing from the gist of the present invention claimed in the claims. Anyone of ordinary skill in the art can make various modifications, as well as such changes can be included within the technical scope of the claims.

As described above, according to the method of implementing the index / context combined playlist of the mobile device according to the present invention, the following effects are obtained.

First, the contextual playlist can be used in a mobile device having an indexed database to maximize user convenience.

Second, if the index type is changed, the execution speed can be faster than the context type playlist.

Third, the contextual playlist once changed to the indexed playlist does not need to be changed.

Claims (5)

Retrieving the contextual playlist file from the mobile device and registering it in the indexed playlist file database; Parsing the registered contextual playlist file; Confirming the existence of a first signature code indicating said contextual playlist file; If it is determined that the first signature code exists, determining whether a second signature code indicating file information on the contextual playlist file exists; If it is determined that the second signature code is present, searching for a file name identical to a file name described in the context playlist file from a file database; And Converting the parsed contextual playlist file into an indexed playlist file by further registering an index of the searched file having the same name in an indexed playlist file; The index / context combined playlist implementation method of the mobile device comprising a. The method of claim 1, And searching for an index of the files belonging to the contextual playlist and registering the index in the indexed playlist file. delete delete The method according to claim 1 or 2, If there is no separate signature code as the first signature code for displaying the playlist file, the method further comprises the step of verifying by using a file extension. .

Images