WO 03/023781
`
`PCT/US02/28485
`
`11
`
`typical M3U format and mayprovide absolute or relative path locations of the audio datafile
`
`associated with playlist record 92. In the exemplary embodiment, a relative path location is
`
`providedso that playlist 90 is transportable between devices. Information segment 93
`
`containing content information fields 93A and indexing information fields 93B that include an
`
`M3U commentformat, specifically the first character of the line being a "#" character.
`
`Additionally, data header 91 also includes an M3U commentformat.
`
`Music managementsoftware that encodes and transmits the audio data files may also
`
`create and transmitplaylist files 90 into data storage 32 via USB port 42 from a PC orother
`
`similar device. Such playlists generally use an M3U formatthat is similar to the data structure
`
`10
`
`disclosed above and in Fig. 6; however, the data structure likely consists of records 92
`
`containing only file pointer segments 94, and thus lack information segment 93 as disclosed
`
`above.
`
`The present invention includes a method of adding information segment 93 toa
`
`standard M3Uorotherplaylist file. While the inventive method may be executed in audio
`
`15
`
`data player 10, a PC, or another data device, the exemplary embodiment includes softwarefor
`
`adding information segment 93, including content information fields 93A descriptive of the
`
`content of each audio data file and indexing information fields 93B providing the relative
`
`location of related playlist records, to audio playlist files 90 in audio data player 10.
`
`Fig. 7 shows a flowchart illustrating the steps for adding content and indexing
`
`20
`
`information to a playlist in an audio data player 10 accordingto the present invention. The
`
`steps maybeinitiated manually by user selection via user input 26, or may be automatically
`
`initiated by the receipt of a new playlist into data storage 32 via USB port 42, or some other
`
`change in the files stored in data storage 32. In the exemplary embodiment, a software
`
`- module is provided for executing the steps of Fig. 7 in audio data player 10.
`
`25
`
`In step 102, an audio datafile playlist 90 located in data storage 32 is opened. For
`
`each record 92 ofplaylist 90, step 104 locates content information for the associated audio
`
`data file that record 92 refers to. For example, using a relative location stored in record 92 for
`
`the audio data file, audio data file located in data storage 32 may be opened and the content
`
`information read. Content information includesattributes or other descriptive information of
`
`30
`
`the audio stored by the audio data file. In the exemplary embodiment, the content information
`
`includes ID3 tag information from MP3 audio data files. Alternatively, content information
`
`for an associated audio data file may be downloaded from a connected PC,the Internet, user
`
`input 26, or another source of data information.
`
`IPR2022-01227
`IPR2022-01227
`EXHIBIT 1003 - PAGE 02231
`EXHIBIT 1003 - PAGE 02231
`
`

`

`WO 03/023781
`
`PCT/US02/28485
`
`12
`
`In step 106, a content information field 93A for sorting playlist records 92 is selected.
`
`The selection of which content field on which to sort playlist 90 may bespecified by the user
`
`via user input 26 or by software selection based on playlists generated to support display and
`
`browsing of audio data files on audio data player 10. For example,referring to Fig. SA, each
`
`of the main sort-by menu categories are supported by a playlist sorted by the content category
`
`or field listed. For example, a playlist sorted by each ofartist, album,title, genre, and file
`names.
`
`After the content information field 93A for sorting playlist file 90 is selected, in step
`
`108 playlist 90 is sorted and stored. Sorting may comprise more than onesorting level to
`
`10
`
`support grouping and quick andefficient browsing of related audio data file records within the
`
`sorted content information field 93A. For example, a playlist file that is sorted by artist may
`
`include a second sorting level sorted by albums within each particular artist and a third sorting
`
`level sorted by track numberortitle for each particular album. The additional sorting levels
`
`and the supporting indexing information fields 93B support browsing ofplaylist 90 and audio
`
`15
`
`data file content information without the need to access individual audio data files. In step
`
`110, the selected audio data file playlist 90 is rewritten using the formatted content
`
`information 93A and indexing information 93B andsorting order specified by the user or the
`
`software.
`
`Indexing information comprises the fields 93B disclosed in Table 2 above and
`
`20
`
`provides quick and memory-efficient browsing of related playlist records 92. The indexing
`
`information fields 93B support display groupings for browsing and navigation of various
`
`sorting levels, for example, those shown in Figs. 5A through 5D. Referring to Fig. SB, a
`
`playlist sorted by artist may include a second sorting level and associated indexing
`
`information 93B for each album ofeachartist, for example, the albums shownin Fig. 5C
`
`25
`
`associated with artist Anna Belle. Additionally, playlist 90 indexing information 93B may
`
`includea third sorting level of tracks or songs for each album as shown in Fig. 5B for the
`
`album Another Record byartist Anna Belle.
`
`Indexing information 93B defines the numberof records included at a given sorting
`
`level and therelative location of next and previous records in the samesorting level and the
`
`30
`
`relative location of the first record in the current grouping of the current sorting level. The
`
`indexing information fields 93B shown in Table 2 are exemplary, and mayinclude otherfields
`
`that provide browsing and navigation of the sorted playlist 90 with minimal memory and
`record 92 search time.
`
`IPR2022-01227
`IPR2022-01227
`EXHIBIT 1003 - PAGE 02232
`EXHIBIT 1003 - PAGE 02232
`
`

`

`WO 03/023781
`
`PCT/US02/28485
`
`13
`
`In the exemplary embodiment, information segment 93 including content information
`
`fields 93A and indexing information fields 93B is stored in M3U commentfield format.
`
`Using the commentfield format advantageously allows playlist 90 to remain compatible with
`
`other devices and software that utilize M3U playlist files.
`
`Fig. 8 illustrates in flowchart form the steps of creating a playlist file in audio data
`
`player 10 in accordance with the present invention. In step 202, a set of audio data files to be
`
`includedin playlist 90 is selected. In the exemplary embodiment, the audio data files are
`
`stored in data storage 32 and are selected by the user via user input 26 or by a software
`
`module directing generation of one or more playlist files to support browsing and navigation
`
`10
`
`of the available audio datafiles in data storage 32. For example, playlist files may be
`
`generated for each of the content information fields 93A represented on the main sort-by
`
`menu shownin Fig. 5A, or a user playlist may be generated byuserselection of particular
`
`—
`
`audio datafiles stored in data storage 32.
`In step 204, for each selected audio data file, a file pointer locating the associated
`audio data file relative to the location of playlist 90 is determined. For example, data storage
`
`15
`
`32 may includea folder structure for storing the audio files, thus the file pointer would include
`
`the necessary folder names and subfolder names as well as the file name for the associated
`
`data file. Alternatively, an absolute file pointer may be used that specifies device name and
`
`supports remote location of audio data files, for example, on a connected PC orthe Internet.
`
`20
`
`In step 206, content information is located and read for each selected audiodatafile.
`
`In the exemplary embodiment, content information for MP3 files is included in ID3 tags. In
`
`step 208, one of the content informationfields is selected for sorting playlist 90. For example,
`
`and as discussed above, a separate playlist file may be generated and sorted for each of the
`
`content information fields 93A displayed by the main sort-by menu shownin Fig. 5A.
`
`25
`
`Additionally, further sorting levels may be used to further group andsort associated playlist
`
`records 92 within each previous sorting level. The content information fields 93A used for
`
`sorting maybeselected by the user via user input 26 or by a software module for generating
`
`audio playlists 90. In step 210, DSP 12 sorts records 92 including file pointers 94 and content
`
`information fields 93, by the selected content information sorting field 93A.
`
`30
`
`In step 212, indexing information fields 93B are generated and content and indexing
`
`information 93 andfile pointers 94 are formatted and stored in a playlist file. As discussed
`
`above for the method disclosed in Fig. 7, indexing information 93B providesfor efficient and
`
`IPR2022-01227
`IPR2022-01227
`EXHIBIT 1003 - PAGE 02233
`EXHIBIT 1003 - PAGE 02233
`
`

`

`WO 03/023781
`
`PCT/US02/28485
`
`14
`
`quick browsing and navigation of content information stored in playlist 90. In step 214,
`
`playlist file 90 is written to data storage 32.
`In the exemplary embodiment,playlist files 90 having content and indexing
`information 93 stored in M3U commentfields are generated by a software application. The
`
`application, referred to as a profiler, may be implemented in a PC connected to audio data
`player 10, or as part of the software in non-PC-based audio data player 10. The profiler
`
`software locates each available audio data file stored in data stores 32 and readsits content
`
`information, for example, [D3 tag fields in MP3 files. The software profiler may then create
`several M3U playlists 90 including content and indexing information 93. Eachplaylist 90
`maybesorted by one or more ofthe content information fields 93A, for example,title, artist,
`genre, album,and file name. Using one playlist 90 for each content information sorting field
`reduces the memory and processing power requirements of audio data player 10 required to
`
`display the available audio data files in specific orders and groupings.
`Figs. 2-4 illustrate an exemplary embodimentofthe displays, buttons, switches,
`indicators, and ports which may be disposed on housing 13 of audio data player 10. Referring
`to Fig. 2, user input 26 comprisesa plurality of buttons 44 (Fig. 3), 46 (Fig. 4), and 60-77
`disposed on housing 13 of audio data player 10 for allowing a userto sort and select particular
`audio data files for playback, and to control playback settings. User input 26 mayalso
`comprise other input devices knownin the art, for example, keyboard, voice activated touch
`pad, and touch screen input devices. Two multi-way switches comprise buttons 62-66 and 68-
`72. Soft keys 74-77 are multi-function buttons whose function change for various user
`interface menu displays. Audio data player 10 also includes display 21 disposed on housing
`13. Display 21 displays the audio data files and playlists stored in data storage 32, the
`function of soft keys 74-77, and various status information associated with audio data player
`10, such as the playback status shownin Fig. 2 and the top-level menu shownin Fig. 5.
`
`Referring again to Fig. 2, STOP/POWERbutton 60 allows the user to stop playback
`
`and to turn audio data player 10 on and off. PLAY/PAUSEbutton 62 allowsthe userto start
`
`playback and to pause playback. Left arrow button 63 allowsa user to movea highlightleft
`whenusing the menu, andto skip back to the previous audio data file or scan backward in the
`present audio data file when playing music. The right arrow button 65 allowsthe user to
`move a highlight right when using the menu, skip forward to the next audio data file, and scan
`
`forward in the current audio data file when playing music. Up arrow button 64 allows the
`
`10.
`
`15
`
`20
`
`25
`
`30
`
`IPR2022-01227
`IPR2022-01227
`EXHIBIT 1003 - PAGE 02234
`EXHIBIT 1003 - PAGE 02234
`
`

`

`WO 03/023781
`
`PCT/US02/28485
`
`15
`
`user to movethe highlight up when using the menu. Downarrow button 66 allowsthe user to
`
`movethe highlight down whenusing the menu.
`
`Referringstill to Fig. 2, SELECT button 68 allowsthe user to select a highlighted
`
`item. Volumeup button 69 increases the playback volume level for headphones 18 and
`
`volume down button 71 decreases the volume level. MODEbutton 70 allowsthe user to
`
`select a particular playback mode, including NORMAL, REPEAT, REPEAT ONE, REPEAT
`
`ALL, SHUFFLE, and REPEAT ALL SHUFFLE. SAVEbutton 72 allows a user to create a
`new playlist or add audio datafiles to an existing playlist. Soft keys 74-77 select the menu
`item that appears just above each button at the bottom of display 21.
`Referring to Fig. 3, POWERindicator 78 lights when audio data player 10 is on.
`CHARGEindicator 79 lights when the power source 47 is charging. In the exemplary
`
`10
`
`embodiment, power source 47 is a rechargeable battery pack. DC IN jack 48 provides 5 volt
`
`DC from an AC adapter to poweraudio data player 10 and recharge power source 47. RESET
`
`button 44 allowsthe userto reset all of the audio data player settings to the factory defaults.
`
`15
`
`Referring now to Fig. 4, OFF/LOCKswitch 46 allowsthe user to make buttons 60-77
`
`inactive when switch 46 is slid to the locked position. LINE OUTjack 41 allowsa user to
`
`connect the audio data player to a separate audio system. Headphonesjack 17 allows the user
`
`to play the decoded audio on headphones 18. USB port 42 provides connection of audio data
`
`player 10 to a PC or other similar device using a USBcable.
`Whentheuserselects a particular audio data file for playback via user input, DSP 12
`
`20
`
`loads the appropriate decoderfile associated with the selected audio data file from data
`
`storage 32 into DSP memory 11. Referring again to Fig. 1, DSP 12 then streamsthe selected
`
`audio data file along buses 33 and 29 into buffer memory 25 as a skip-protection buffer.
`
`After streaming of the selected audio data file begins, DSP 12 decodes the audio data
`
`25
`
`file using an associated decoderfile. Various decoderfiles may be stored in data storage 32 to
`
`allow audio player 10 to be adapted to process the various encoding formats associated with
`
`the audio datafiles stored in data storage 32. In effect, portable audio player 10 can be
`
`software upgraded, as necessary, by the decoderfiles stored in data storage 32 when the user
`
`selects a particular audio data file stored in data storage 32.
`
`30
`
`After powering up, DSP 12 of audio data player 10 loads the system configuration file
`
`from data storage 32. DSP 12 identifies the various file formats that need to be supported for
`
`the data files stored in data storage 32. The configuration file also includes information that
`
`equates the file extension of the audio data files with particular decoderfiles stored in data
`
`IPR2022-01227
`IPR2022-01227
`EXHIBIT 1003 - PAGE 02235
`EXHIBIT 1003 - PAGE 02235
`
`

`

`WO 03/023781
`
`PCT/US02/28485
`
`16
`
`storage 32. If the configuration file is valid, DSP 12 readsthefile attribute table stored in
`
`data storage 32 and causes display 21 to display a menu-drivenlisting of the file/folders stored
`
`in data storage 32.
`Referring to Fig. 5A, the main menu displayed on display 21 allows the user to
`navigate and display audio data files according to groupings or identifying characteristics,
`such as, for example,artist, album,title, genre, playlist, and all audio data files. From the
`
`main menu,the user may operate user input 26, as described above,to navigate sortedlists
`
`and select a desired one of the displayed audio data files or playlists for playback.
`
`Whenanaudio datafile or playlist is selected for playback, DSP 12 perform a number
`
`10
`
`of steps, including several concurrent steps, to provide audio playback. First, DSP 12
`
`identifies and transfers the corresponding decoderfile from data storage 32 to DSP memory
`
`11. For example,if the user selects an MP3 file, microcontroller 22 transfers the MP3
`
`decoderfile from data storage 32 to DSP memory 11. The MP3 decoderfile is used to control
`
`the decoding operation of DSP 12.
`
`15
`
`DSP 12 begins streaming the selected audio datafile from data storage 32 to buffer
`
`memory 25. DSP 12 uses the decoderfile to decode and decrypt, if applicable, the audio data
`
`file in buffer memory 12 in accordance with the appropriate encoding format. The decoded
`
`audio data is provided to D/A converter 14 and headphone amp 16 andline out pre amp 40 for
`
`reproduction.
`
`20
`
`In the present embodiment, the necessary decoderfiles are stored in data storage 32
`
`along with the audio data files. As such, audio player 10 may be updatedto play different
`
`encoding formats by software updating of the DSP via decoderfiles stored along with the
`
`audio data files in data storage 32. Thus, audio data player 10 is capable of playing back data
`
`files encoded using a variety of encoding formats, including encoding formats that become
`
`25
`
`available in the future.
`
`During playback display, shown in Fig. 2, displays various information aboutthe
`
`audio data file and the audio data player settings. For example, display 21 in Fig. 2 showsthe
`
`file name,artist name, album title, genre, current track being played outoftotal files being
`
`played, volumelevel indication, elapsed play time of audio datafile, playback mode
`
`30
`
`indication, bit rate, and selected DSP modeselection.
`
`In the exemplary embodiment, suitable DSP 12 include, but are notlimitedto,
`
`TMS320DA250 manufactured by Texas Instruments Inc., of Dallas, Texas. Associated with
`
`DSP 12 is memory 23, in this case, 48 KB of ROM,and buffer memory 25 comprising 8 MB
`
`IPR2022-01227
`IPR2022-01227
`EXHIBIT 1003 - PAGE 02236
`EXHIBIT 1003 - PAGE 02236
`
`

`

`WO 03/023781
`
`PCT/US02/28485
`
`17
`
`of RAM,providing 7 minutes of buffered play time at 128 kbps and 14 minutes of buffered
`
`play time at 64 kbps. DSP 12 also includes associated memory 11, in this case 64 KB of
`
`RAM.Suitable hard drives for data storage 32 include, but are not limited to, Microdrive™
`
`manufactured by IBM Corporation of Armonk, New York. A 10 GB hard drive, for example,
`
`provides approximately 150 hours of audio at MP3 bit-rate of 128 kbps, or 300 hoursatabit-
`
`rate of 64 kbps.
`
`It will be apparent to those skilled in the art that although the present invention has
`
`been described in terms of an exemplary embodiment, modifications and changes may be
`
`madeto the disclosed embodiment without departing from the essence of the invention. For
`
`10
`
`example, although the present invention has been described with reference to data storage 32
`
`that is fixedly disposed within audio player 10, the present invention may be implemented
`
`using flash memory, anotherfixed storage device, optical device, or a memory cardthat is
`
`adapted to be removably coupled to audio player 10, wherein the decoder program and audio
`
`data files are loaded onto the memory card by the music management software. Also,it is.
`
`15
`
`herein recognized that the present feature of loading the appropriate decoder programsand the
`
`audio data files may be implemented in the music managementsoftware using any one of a
`
`number of conventionally known programming methods, or combination of programming
`
`methods. Also, although the above is described in reference to an audio data player, the
`present invention maybe extended to any portable data processing device, for example, video
`display devices, wherein the data may be encodedusing oneofa plurality of data encoding
`
`20
`
`formats. Therefore, it is to be understood that the present invention is intended to coverall
`
`modifications as defined in the appended claims
`
`IPR2022-01227
`IPR2022-01227
`EXHIBIT 1003 - PAGE 02237
`EXHIBIT 1003 - PAGE 02237
`
`

`

`WO 03/023781
`
`PCT/US02/28485
`
`18
`
`CLAIMS
`
`1.
`
`A computer-readable medium (32) having stored thereon a data structure (90)
`
`including a playlist record (92) for each audio data file, each playlist record (92) including a
`
`file pointer segment (94), characterized by each playlist record (92) including an information
`
`segment (93) having a content information field (93A) descriptive of the content of the audio
`
`data file and including at least one indexing informationfield (93B)indicating the location of
`related playlist records, and the playlist file including a data headerindicating a first content
`
`information field (93A) upon whichtheplaylist records are sorted.
`
`10
`
`2.
`
`The data structure of Claim 1, characterized in that the playlist records include
`
`an M3U format.
`
`3.
`
`The data structure of Claim 2, characterized in that said information segment
`
`includes an M3U commentformat and said content information field includes an ID3tag.
`
`4.
`
`The data structure of Claim 1, characterized in that the playlist records are
`
`15
`
`sorted accordingto at least a second content informationfield.
`
`5.
`
`The data structure of Claim 1, characterized in that the location of said related
`
`playlist recordsis a relative location.
`
`6.
`A method of addingto an audio datafile playlist (90) content and indexing
`information foreach playlist record (92), characterized by:
`locating content information
`(93A) descriptive of the content of each audio data file; determining for each playlist record
`
`20
`
`indexing information (93B) providing the location of related playlist records; and formatting
`
`the content and indexing information (93) for storage in the playlist (90).
`
`7.
`
`The method of Claim 6, characterized by sorting the playlist according to the
`
`content information.
`
`25
`
`8.
`
`The method of Claim 6, characterized in that the content information includes
`
`an ID3 tag, the playlist records include an M3U format, and the content and indexing
`
`information is stored in M3U commentfield format.
`
`9.
`
`In an audio data player having a user interface including an output device (17,
`
`21, 41) and a user input (26), a method of browsing audio data file content information by
`
`30
`
`providingat least one playlist (90) includingat least a first and second record (92) relating to
`
`audio data files available for playback, each record (92) stored in a predetermined sequence
`
`and including a content and indexing information segment (93), characterized by said content
`
`information including a field (93A) descriptive of the content of the related audio datafile,
`
`IPR2022-01227
`IPR2022-01227
`EXHIBIT 1003 - PAGE 02238
`EXHIBIT 1003 - PAGE 02238
`
`

`

`WO 03/023781
`
`PCT/US02/28485
`
`19
`
`and said indexing information having fields (93B) providing the location of related playlist
`
`records (92); outputting via the output device (17, 21, 41) said content information field (93.A)
`
`for at least a first record; receiving a playlist navigation signal from the user input (26); and in
`
`responseto said playlist navigation signal, using at least one of said indexing information
`
`fields (93B) to locate and output said content information field (93A)of at least a second
`
`record, said second recordrelated to said first record by said predetermined sequenceand said
`
`navigation signal.
`
`10.
`
`The method of Claim 9, characterized in that said playlist records include an
`
`M3U format, said content and index information segmentincludes an M3U commentfield
`
`10
`
`format, and said content information field includes an ID3tag.
`
`11,
`
`The method of Claim 9, characterized in that said predetermined sequence
`
`includes said playlist records sorted by at least one of said content informationfields.
`
`12.
`
`The method of Claim 9, characterized in that the location of said related
`
`playlist recordsis a relative location.
`
`15
`
`13.
`
`An audio data player (10) comprising a DSP (12) coupled with data storage
`
`(32) capable of storing audio data files and playlist files (90), the audio data files each having
`
`attributes descriptive of the audio content of each said audio data file; characterized by the
`
`playlist files (90) including records (92) for each of at least a portion of the audiodatafiles,
`
`said records (92) in a predetermined order based onat least one said attribute; said records
`including a content information field (93A) storing said attributes of each said audio data file,
`
`20
`
`and indexing information fields (93B) indicating the relative location of related playlist
`
`records (92); and the microcontroller (22) having software capable of reading said playlist
`records (92)and outputting a navigable list of at least a portion of said content information
`field (93A) according to said predetermined order.
`
`25
`
`14.
`
`The audio data player according to Claim 13, characterized by the DSP (12)
`
`having software capable of generating playlistfiles.
`
`15.
`
`The audio data player of Claim 14, characterized in that said playlistfile
`
`generating software is capable of sorting each playlist file according to said content
`
`informationfields.
`
`30
`
`16.
`
`The audio data player of Claim 15, characterized in that said playlist file
`
`generating software is capable of locating audio data files stored on the data storage device.
`
`17.
`
`The audio data player of Claim 16, characterized in that said playlist file
`
`generating softwareis capable of generating at least one additional audio datafile playlist,
`
`IPR2022-01227
`IPR2022-01227
`EXHIBIT 1003 - PAGE 02239
`EXHIBIT 1003 - PAGE 02239
`
`

`

`WO 03/023781
`
`PCT/US02/28485
`
`20
`
`said additional audio data file playlist sorted according to at least a second content
`
`information field.
`
`18.
`
`The audio data player according to Claim 13, characterized in that said
`
`attributes include an ID3 tag, and said playlist file records include an M3U format.
`
`19.
`
`The audio data player according to Claim 14, characterized in that said playlist
`
`file generating software is capable of determiningfile pointers locating each audio datafile in
`
`the data storage; reading said attributes for each audiodata file; formatting said attributes and
`
`said file pointers for storage in the audio datafile playlist.
`
`IPR2022-01227
`IPR2022-01227
`EXHIBIT 1003 - PAGE 02240
`EXHIBIT 1003 - PAGE 02240
`
`

`

`WO 03/023781
`
`PCT/US02/28485
`
`1/7
`
`AINOHdOVAH
`
`a
`
`SOTVNY
`
`OLWLSIG
`
`YS.LYAANOD
`
`9a/00|
`
`Gz3
`
`OVIOL
`INO-ANIT|}SNOHdQVSH
`LNO-ANIVU
`‘dINVAud‘dWV
`LV8Zh
`-ep
`spr)©
`NIOGAS|OA
`
`YSLYSANOOD“_SOYNOSYSMOd
`AV1dSIG091
`{—___———————)LyOdasn
`ree:od,FOVHOLS||ggiviva3
`Ly3
`
`WOdds3
`
`AINGOW
`
`Zp
`
`SUBSTITUTE SHEET (RULE 26)
`
`IPR2022-01227
`IPR2022-01227
`EXHIBIT 1003 - PAGE 02241
`EXHIBIT 1003 - PAGE 02241
`
`
`
`

`

`WO 03/023781
`
`PCT/US02/28485
`
`2/7
`
`ALIMOAVAAW
`
`wa[__
`
`
`7:00:00HDOYDISSV19
`
`M87L00/1000CO=MYL
`ANNOYVDGNVNOWIS
`OANI==dSd
`SONOS
`SN4OOMLAHL
`
`SUBSTITUTE SHEET (RULE 26)
`
`IPR2022-01227
`IPR2022-01227
`EXHIBIT 1003 - PAGE 02242
`EXHIBIT 1003 - PAGE 02242
`
`

`

`WO 03/023781
`
`PCT/US02/28485
`
`—o
`Fd
`
`6x
`
`t
`
`wT
`s
`
`©
`
`=
`Li
`
` 3/7
`
`>?
`
`3
`
`-
`8
`
`C9
`
`©
`
`Y
`LL
`
`SUBSTITUTE SHEET(RULE 26)
`
`IPR2022-01227
`IPR2022-01227
`EXHIBIT 1003 - PAGE 02243
`EXHIBIT 1003 - PAGE 02243
`
`

`

`WO 03/023781
`
`PCT/US02/28485
`
`SORT BY
`
`ALBUM
`
`TITLE
`
`GENRE
`USER PLAYLISTS
`
`AUDIO FILES
`
`HELP
`
`MORE
`
`MAIN
`
`ARTIST
`
`AEROSMITH
`
`AMERICA
`
`ANIMALS
`
`ANNA BELLE
`
`ANOTHER GROUP
`
`ASSUME THE WORST
`
`SUBSTITUTE SHEET(RULE 26)
`
`IPR2022-01227
`IPR2022-01227
`EXHIBIT 1003 - PAGE 02244
`EXHIBIT 1003 - PAGE 02244
`
`

`

`WO 03/023781
`
`PCT/US02/28485
`
`5/7
`
`ANNA BELLE
`
`ABSOLUTELY
`
`ANOTHER RECORD
`
`CAN'T MAKE IT
`
`HAPPY MUSIC II
`
`HELLO MONEY
`
`HONEY
`
`MAIN
`
`ANOTHER RECORD
`
`01 A SONG FOR YOU
`
`02 BE YOURSELF
`
`08 ASSUME THE WORST
`
`09 DO YOUR BEST
`
`10 ANOTHER SONG
`
`
`
`BACK
`
`PGI
`
`PGt
`
`- FIG. 5D
`
`SUBSTITUTE SHEET (RULE 26)
`
`IPR2022-01227
`IPR2022-01227
`EXHIBIT 1003 - PAGE 02245
`EXHIBIT 1003 - PAGE 02245
`
`

`

`WO 03/023781
`
`PCT/US02/28485
`
`6/7
`
`92
`
`92
`
`92
`
`Data Header
`
`Information
`Segment
`
`Content
`Information
`93A
`
`Indexing
`Information
`93B
`
`Record 1
`
`File Pointer
`
`Record 2
`
`.
`Information
`Segment
`
`Content
`.
`Information
`934
`
`Indexing
`Information
`93B
`
`Record 2
`
`File Pointer
`
`
`
`Record X
`
`Information
`Segment
`
`Content
`Information
`93A
`
`Indexing
`Information
`93B
`
`Record X
`
`File Pointer
`
`FIG. 6
`
`SUBSTITUTE SHEET (RULE 26)
`
`IPR2022-01227
`IPR2022-01227
`EXHIBIT 1003 - PAGE 02246
`EXHIBIT 1003 - PAGE 02246
`
`

`

`WO 03/023781
`
`PCT/US02/28485
`
`~ — ~
`
`Open Audio Data File Playlist
`
`102
`
`Lacate Content Information for Audio Data Files in Playlist
`
`104
`
`Select Content Field For Sorting
`
`Store Audio Data File Playlist by Indexing Field
`
`Format and Store Content and Indexing Information in
`Audio Data File Playlist
`
`FIG. 7
`
`Format and Store Content and Indexing Information and File Pointer Records for Each DataFile in a Playlist File
`
`Write the Playlist File to Data Storage
`
`106
`
`108
`
`110
`
`204
`
`208
`
`212
`
`214
`
`SUBSTITUTE SHEET(RULE 26)
`
`IPR2022-01227
`IPR2022-01227
`EXHIBIT 1003 - PAGE 02247
`EXHIBIT 1003 - PAGE 02247
`
`

`

`INTERNATIONAL SEARCH REPORT
`
` int
`
`ral Application No
`
` ._ CLASSIFICATION OF SUBJECT MATTER
`Tee7 G1IB27/10.
`G11B27/32
`
`Documentation searched other than minimum documentation to the extent that such documentsare included in the fields searched
`
`
`PCT/US 02/28485
`
`
` Accordingto International Patent Classification (IPC) or to both national classification and IPC
`B. FIELDS SEARCHED
`Minimum documentation searched (classification system followed by classification symbols)
`IPC 7
`G11B
`G11C
`GOQO6F
`
`
`
`
`
`Electronic data base consulted during the international search (name of data base and, where practical, search terms used)
`PAJd
`
`
`EPO-Internal, WPI Data,
`INSPEC,
`
`C. DOCUMENTS CONSIDERED TO BE RELEVANT
`
`Category *|Citation of document, with indication, where appropriate, of the relevant passages Relevant to claim No.
`
`line 17
`
`
`
`
`
`
`
`WO O01 28222 A (TANG JIMMY TAI KWAN ;LAI
`SAI KIT (CN); NG KIN PING (CN); TSUI CHI)
`
`
`19 April 2001 (2001-04-19)
`page 27,
`line 15 -page 30,
`
` EP 1 056 093 A (MATSUSHITA ELECTRIC IND CO
`
`
`LTD) 29 November 2000 (2000-11-29)
`
`sections ‘0237! - “0269!
`
`
`WO O1 33569 A (IOMEGACORP)
`1,6,9,13
`10 May 2001 (2001-05-10)
`
`
`page 10,
`line 5-11
`
`
` [x] Patent family members are listed in annex.
`
`"T'
`
`° Special categories ot cited documents:
`
`
`later documentpublishedafter the internationalfiling date
`pec
`99
`or priority date and notin conflict with the application but
`"A" document defining the general stale of the art which is not
`cited to understand the principle or theory underlying the
`
`
`invention
`consideredto be of particular relevance
`
`
`*X* documentof particular relevance:the claimed invention
`‘E* earlier document but published on orafterthe international
`
`
`cannot be considered novelor cannot be considered to
`filing date
`involve an inventive step whenthe documentis taken alone
`"L® document which may throw doubts on priority claim(s) or
`
`
`"¥* documentof particular relevance; the claimed invention
`whichis cited to establish the publication date of another
`
`
`cannot be considered to involve an inventive step when the
`citation or other special reason (as specified)
`
`
`document is combined with one or more other such docu—
`"O" documentreferring to an oral disclosure, use, exhibition or
`
`
`ments, such combination being obvious to a person skilled
`other means
`
`
`in the art.
`*P* document publishedpriorto the internationalfiling date but
`
`*&° document memberof the same patent family
`later than the priority date claimed
`
`
`Date of the actual completion of the international search Date of mailing of the international search report
`6 January 2003
`13/01/2003
`
`Authorized officer
`
`
`Name and mailing address of the ISA
`European Patent Office, P.B. 5818 Patentlaan 2
`NL - 2280 HV Rijswijk
`
`
`Tel. (431-70) 346-2040, Tx. 31 651 epo ni,
` Mourik, J
`
`
`
`Fax: (431-70) 340-3016
`
`Form PCT/ISA/210 (second sheet) (July 1992)
`
`IPR2022-01227
`IPR2022-01227
`EXHIBIT 1003 - PAGE 02248
`EXHIBIT 1003 - PAGE 02248
`
`

`

`INTERNATIONAL SEARCH REPORT
`
`Information on patent family members
`
`
`Inte
`
` al Application No
`
`
`PCT/US 02/28485
`
`Patent document
`cited in search report
`
`Publication
`date
`
`Patent family
`member(s)
`
`Publication
`date
`
`23-04-2001
`2018201
`19-04-2001
`WO 0128222
`19-04-2001
`0128222
`
`
`
`
`EP 1056093
`29-11-2000
`BR
`0006168 A
`17-04-2001
`BR
`0006882 A
`07-08-2001
`CA
`2338634 Al
`07-12-2000
`CA
`2338695 Al
`07-12-2000
`CA
`2338725 Al
`07-12-2000
`CN
`1321319 T
`07-11-2001
`CN
`1318196 T
`17-10-2001
`CN
`1318197 7
`17-10-2001
`CN
`1353853 T
`12-06-2002
`EP
`1056096 Al
`29-11-2000
`EP
`1056092 Al
`29-11-2000
`EP
`1056093 Al
`29-11-2000
`EP
`1056094 Al
`29-11-2000
`WO
`0074059 Al
`07-12-2000
`WO
`0074060 Al
`07-12-2000
`WO
`0074054 A2
`07-12-2000
`WO
`0074061 Al
`07-12-2000
`JP
`3327897 B2
`24-09-2002
`JP
`2001249693 A
`14-09-2001
`JP
`2001249694 A
`14-09-2001
`UP
`3327898 B2
`24-09-2002
`JP
`2001249669 A
`14-09-2001
`
`14-09-2001 2001249695
`
`
`
`
`14-05-2001
`1335401
`0133569
`
`
`
`
`A
`
`10-05-2001
`
`Form PCT/ISA/210 (patent family annex) (July 1992)
`
`IPR2022-01227
`IPR2022-01227
`EXHIBIT 1003 - PAGE 02249
`EXHIBIT 1003 - PAGE 02249
`
`

`

`(12) INTERNATIONAL APPLICATION PUBLISHED UNDER THE PATENT COOPERATION TREATY (PCT)
`
`(19) World Intellectual Property
`Organization
`
`International Bureau
`
`(43) International Publication Date
`6 May 2004 (06.05.2004)
`
`PCT
`
`(10) International Publication Number
`WO 2004/039034 Al
`
`