U.S. patent application number 13/027825 was filed with the patent office on 2011-06-09 for music composition data transmission recording method and music composition reproduction device.
This patent application is currently assigned to Sony Corporation. Invention is credited to Hideko KIMURA, Kazushi SAKUMA.
Application Number | 20110138043 13/027825 |
Document ID | / |
Family ID | 33094986 |
Filed Date | 2011-06-09 |
United States Patent
Application |
20110138043 |
Kind Code |
A1 |
SAKUMA; Kazushi ; et
al. |
June 9, 2011 |
MUSIC COMPOSITION DATA TRANSMISSION RECORDING METHOD AND MUSIC
COMPOSITION REPRODUCTION DEVICE
Abstract
A song in a music player is replaced by another song in a server
in accordance with the user's estimated preferences without
requiring the user to become conscious of individual songs. A music
player in a server detects a size of a free space in a memory and a
playback history (a substantial playback count, which denotes the
number of times a song was continuously played for a duration not
shorter than a predetermined one, or a skip count, which denotes
the number of times a song was played for a duration shorter than a
predetermined one) of every song recording, and judges whether any
song should be deleted from the memory to permit a song to be
downloaded into the music player from the server. If any song
should be deleted, a CPU selects a song having a small evaluation
function as the song to be deleted.
Inventors: |
SAKUMA; Kazushi; (Chiba,
JP) ; KIMURA; Hideko; (Chiba, JP) |
Assignee: |
Sony Corporation
Tokyo
JP
|
Family ID: |
33094986 |
Appl. No.: |
13/027825 |
Filed: |
February 15, 2011 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
10550064 |
May 31, 2006 |
7917572 |
|
|
PCT/JP04/03770 |
Mar 19, 2004 |
|
|
|
13027825 |
|
|
|
|
Current U.S.
Class: |
709/224 |
Current CPC
Class: |
G11B 2220/61 20130101;
G06F 16/68 20190101; G11B 2220/65 20130101; G11B 27/034 20130101;
G06F 16/637 20190101; G11B 27/11 20130101 |
Class at
Publication: |
709/224 |
International
Class: |
G06F 15/173 20060101
G06F015/173 |
Foreign Application Data
Date |
Code |
Application Number |
Mar 26, 2003 |
JP |
2003-084245 |
Claims
1. A content data transfer method for transferring first content
data from a server to a player, the method comprising: playing back
second content data; storing a continuous playback count of each
second content data of the player, the continuous playback count
denoting the number of times second content data was continuously
played for a predetermined duration; selecting the first content
data to be transferred to the player based on the continuous
playback count; and transferring the first content data to the
player.
2. The content data transfer method according to claim 1 further
comprising: selecting third content data to be deleted from the
first content data based on the continuous playback count when the
player does not have a capability to store the second content data;
and deleting the third content data to be deleted from the
player.
3. The music data transfer method according to claim 1, the
continuous playback count of the third content data is low.
4. A content data transfer system for transferring first content
data from a server to a player, the system comprising: a playback
system configured to playback second content data; a storage system
configure to store a continuous playback count of each second
content data of the player, the continuous playback count denoting
the number of times second content data was continuously played for
a predetermined duration; a selection system configure to select
the first content data to be transferred to the player based on the
continuous playback count; and a transferring system configure to
transfer the first content data to the player.
5. In a content data transfer system for transferring first content
data from a server to a player, the player comprising: a playback
unit configured to playback second content; and a storage configure
to store a continuous playback count of each second content data of
the player, the continuous playback count denoting the number of
times other second content data was continuously played for a
predetermined duration, wherein the first content data to be
transferred to the player is selected based on the continuous
playback count; and wherein the first content data is transferred
to the player.
6. In a content data transfer system for transferring first content
data to a player, the player comprising: a playback unit configured
to playback second content data; and a storage configure to store a
continuous playback count of each second content data of the
player, the continuous playback count denoting the number of times
second content data was continuously played for a predetermined
duration, the first content data to be transferred to the player is
selected based on the continuous playback count, the first content
data is transferred to the player.
7. In a content data transfer system for transferring first content
data to a player, the first content data is selected based on
continuous playback count of each second content data stored in the
player, the continuous playback count denoting the number of times
second content data was continuously played for a predetermined
duration, the player comprising: a playback unit configured to
playback second content data; and a storage configure to store the
continuous playback count of each second content data stored in the
player.
8. A method of a player in a content data transfer system for
transferring first content data to the player, the method
comprising: playing back second content data; and at least one of
(i) storing a continuous playback count of each second content data
of the player, the continuous playback count denoting the number of
times second content data was continuously played for a
predetermined duration, (ii) selecting the first content data to be
transferred to the player based on the continuous playback count,
and (iii) selecting third content data to be deleted from the
player based on the continuous playback count when the player does
not have a capability to store the first content data.
9. A player in a content data transfer system for transferring
first content data to the player, the player comprising: playback
unit configured to playback second content data; and at least one
of (i) storage unit configured to store a continuous playback count
of each second content data of the player, the continuous playback
count denoting the number of times second content data was
continuously played for a predetermined duration, (ii) selection
unit configured to select the first content data to be transferred
to the player based on the continuous playback count, and (iii)
selection unit configured to select third content data to be
deleted from the player based on the continuous playback count when
the player does not have a capability to store the first content
data.
10. A method of a server in a content data transfer system for
transferring first content data to a player, the method comprising:
storing; and at least one of playing back second content data (i)
storing a continuous playback count of each second content data of
the player, the continuous playback count denoting the number of
times second content data was continuously played for a
predetermined duration, (ii) selecting the first content data to be
transferred to the player based on the continuous playback count,
and (iii) selecting third content data to be deleted from the
player based on the continuous playback count when the player does
not have a capability to store the first content data.
Description
CROSS-REFERENCE TO RELATED APPLICATIONS
[0001] This present application is a continuation application of
and claims the benefit of priority under 35 U.S.C. .sctn.120 from
U.S. application Ser. No. 10/550,064, filed on May 31, 2006, the
entire contents of which are incorporated herein by reference. U.S.
application Ser. No. 10/550,064 is a national stage application of
International Application No. PCT/JP04/03770, filed on Mar. 19,
2004, which is based upon and claims the benefit of priority under
35 U.S.C. .sctn.119 from the prior Japanese Patent Application No.
2003-084245, filed on Mar. 26, 2003.
TECHNICAL FIELD
[0002] The present invention relates to a music data
transfer/recording method for use in a music recording/playback
system that downloads song data from a PC (personal computer) or
other server for storing song data on a hard disk or other storage
device to a music player for playing song data stored in a flash
memory or other storage section. The present invention also relates
to a music player for such a system.
BACKGROUND ART
[0003] A small-size, portable music player that has a flash memory
or other relatively small-sized memory and plays song data stored
in the memory is now commercially available. The user of the music
player connects the music player to a PC and downloads song data
from the PC to the music player.
[0004] A music data download system disclosed by Patent Document 1
(Japanese Patent Laid-open No. 2002-108747) downloads song data, to
which playback control information is added, from a server to a
terminal. The terminal exercises song data playback control in
accordance with the playback control information.
[0005] Further, the invention disclosed by Patent Document 2
(Japanese Patent Laid-open No. Hei 10-208445) furnishes an
administration section, for instance, of a radio station with a
shelf for storing media on which music data is recorded, playback
means for playing back the music data from the media, and retention
means for retaining the music data in such a manner as to transfer
the music data at a high speed to a studio or other terminal
section via a network. The shelf is used to store media on which
infrequently used music data is recorded. The retention means is
used to retain frequently used music data. In accordance with the
frequency of music data use, this invention uses the shelf,
playback means, or retention means to store or retain the media or
music data.
[0006] However, the aforementioned small-size, portable music
player having a flash memory or other relatively small-sized memory
cannot retain hundreds or thousands of songs. Therefore, the user
of the small-size, portable music player has to marshal song data
as needed within the music player before downloading new song data
or the song data deleted from the music player from a PC to the
music player.
[0007] However, the user finds it troublesome to select the songs
to be deleted from the music player or may be at a loss what songs
to delete. The user also finds it troublesome to select the songs
to be transferred from the PC to the music player. The greater the
number of songs stored on the PC, the more often the user is at a
loss what songs to transfer.
[0008] The present invention has been made to provide a natural
method for replacing songs stored in the music player by the other
songs stored in the server in accordance with the user's estimated
preferences and wishes and without requiring the user to perform a
special procedure, exercise judgment, or become conscious of
individual songs.
DISCLOSURE OF INVENTION
[0009] According to a first aspect of the present invention, there
is provided a music data transfer/recording method for transferring
song data from a server, which retains song data in a storage
device, to a music player, which plays back song data retained in a
storage section, and writing the transferred song data in the
storage section, the method including:
[0010] a first step for causing the server to select the song data
to be transferred to the music player from among the song data that
are retained in the storage device and not retained in the storage
section;
[0011] a second step for causing the music player to judge whether
the free space in the storage section is exceeded by the amount of
song data to be transferred; and
[0012] a third step for causing the music player, when the free
space in the storage section is exceeded by the amount of song data
to be transferred, to select the song data to be deleted from the
storage section, delete the selected song data from the storage
section, and write the song data transferred from the server into
the storage section,
[0013] wherein the first step causes the server to preferentially
select song data that has not been transferred to the music player
and has been most recently registered in the server, as the song
data to be transferred to the music player; and
[0014] wherein the third step causes the music player to reference
a substantial playback count of each song data retained in the
storage section, the substantial playback count denoting the number
of times a song was continuously played for a duration not shorter
than a predetermined one, or a skip count of each song data
retained in the storage section, the skip count denoting the number
of times a song was played for a duration shorter than a
predetermined one, and preferentially select the song data having a
low substantial playback count or the song data having a high skip
count as the song data to be deleted from the storage section.
[0015] According to a second aspect of the present invention, there
is provided a music data transfer/recording method for transferring
song data from a server, which retains song data in a storage
device, to a music player, which plays back song data retained in a
storage section, and writing the transferred song data in the
storage section, the method including:
[0016] a first step for transmitting a substantial playback count,
which denotes the number of times a song was continuously played
for a duration not shorter than a predetermined one, or a skip
count, which denotes the number of times a song was played for a
duration shorter than a predetermined one, from the music player to
the server as a playback history of each song data retained in the
storage section;
[0017] a second step for causing the server to select the song data
to be transferred to the music player from among the song data that
are retained in the storage device and not retained in the storage
section, and to judge whether the free space in the storage section
is exceeded by the amount of song data to be transferred;
[0018] a third step for causing the server, when the free space in
the storage section is exceeded by the amount of song data to be
transferred, to select the song data to be deleted from the storage
section, specify the song data to be deleted, and transfer the song
data targeted for a transfer to the music player; and
[0019] a fourth step for causing the music player to delete the
specified song data from the storage section and write the
transferred song data into the storage section,
[0020] wherein the second step causes the server to preferentially
select song data that has not been transferred to the music player
and has been most recently registered in the server, as the song
data to be transferred to the music player; and
[0021] wherein the third step causes the server to reference the
playback history transmitted from the music player and
preferentially select the song data having a low substantial
playback count or the song data having a high skip count as the
song data to be deleted from the storage section.
[0022] When the user mounts the music player on a cradle that is
connected to the server or otherwise connects the music player to
the server in a situation where the music data transfer/recording
method according to the present invention, which has been described
above, is used, the server selects the song data to be transferred
from the server to the music player. If the free space of the
storage section in the music player is exceeded by the amount of
song data to be transferred, the music player or server selects the
song data to be deleted from the storage section of the music
player. Therefore, some songs in the music player are replaced by
the other songs in the server without requiring the user to perform
a special procedure, exercise judgment, or become conscious of
individual songs.
[0023] Further, the music player or server preferentially selects
songs having a low substantial playback count or a high skip count
as the song data to be deleted from the music player. Therefore,
songs that do not presumably match the user's preferences will be
deleted from the music player, whereas songs that presumably match
the user's preferences will be retained in the music player.
Furthermore, the server preferentially selects a song that has not
been transferred to the music player and has been most recently
registered in the server, as the song data to be transferred to the
music player. Consequently, a song that presumably matches the
user's preferences will be loaded into the music player.
BRIEF DESCRIPTION OF DRAWINGS
[0024] FIG. 1 illustrates one embodiment of a music
recording/playback system in which a music data transfer/recording
method according to the present invention is executed.
[0025] FIG. 2 shows an example of file-attached information in a
server.
[0026] FIG. 3 shows an example of file-attached information in a
music player.
[0027] FIG. 4 shows a part of a first example of a music player
side/server side processing program.
[0028] FIG. 5 shows the remaining part of the first example of the
music player side/server side processing program.
[0029] FIG. 6 shows a part of a second example of a music player
side/server side processing program.
[0030] FIG. 7 shows the remaining part of the second example of the
music player side/server side processing program.
BEST MODE FOR CARRYING OUT THE INVENTION
One Embodiment of a Music Recording/Playback System: FIGS. 1 to
3
[0031] FIG. 1 illustrates one embodiment of a music
recording/playback system in which a music data transfer/recording
method according to the present invention is executed.
[0032] The music recording/playback system according to the present
embodiment comprises a server 10, which is a PC; a cradle 20, which
is connected to the server 10; and a portable music player 30. When
the music player 30 is mounted on the cradle 20, the music player
30 is connected to the server 10 and a charger circuit 2 in the
cradle 20 charges a battery 3 in the music player 30.
(Typical Server)
[0033] In the currently used example, the server 10 includes a CPU
11. Its bus 12 is connected to a memory 13, which stores the
programs to be executed by the CPU 11 and various data; a HDD (hard
disk drive) 15, which contains a hard disk 14; a media drive 16,
which drives a music CD (Compact Disc) or other disk 1 that is
inserted into the server 10; a network interface (network I/F) 17
for connecting to an external network such as the Internet; and a
USB (Universal Serial Bus) interface (USB I/F) 19 for connecting to
the music player 30 via the cradle 20.
[0034] The bus 12 is also connected, for instance, to a display
such as an LCD (Liquid Crystal Display), an operating control
section containing a keyboard and a mouse, and an audio output
section including a DAC (Digital to Analog Converter) and an audio
amplifier circuit. However, these components are not shown in the
figure.
[0035] The hard disk 14 not only stores programs and data, but also
records music data (song data) that are acquired from a disk 1 or
external network and compressed/encoded by an audio encoding method
such as MP3 (MPEG-1 Audio Layer-3) or ATRAC3 (Adaptive Transform
Acoustic Coding-3, registered trademark).
(Typical Music Player)
[0036] In the currently used example, the music player 30 includes
a CPU 31. Its bus 32 is connected to a memory 33, which stores the
programs to be executed by the CPU 31 and various data; a flash
memory 34, which mainly stores compressed/encoded song data; a
decoder 35 for decompressing/decoding the song data; and a USB
interface (USB) 39 for connecting to the server 10 via the cradle
20. The output end of the decoder 35 is connected to an earphone 38
via an audio output section, which includes a DAC 36 and an audio
amplifier circuit 37.
[0037] The bus 32 is also connected, for instance, to an LCD for
displaying, for instance, the names of songs recorded in the flash
memory 34 and an operating control section for switching, for
instance, from one song name to another on the LCD and selecting
the song to be played. However, these components are not shown in
the figure.
(File Attached Information in the Server: FIG. 2)
[0038] As shown in FIG. 2, the hard disk 14 in the server 10
records the song name, artist name, length, size, server
registration date/time, music player registration date/time, and
transfer-to-music-player count of every file (compressed data file
for each song) that is recorded on the hard disk 14.
[0039] The server registration date/time denotes the date/time at
which a file was acquired from a disk 1 or external network,
entered into the server 10, and recorded on the hard disk 14.
[0040] The music player registration date/time denotes the
date/time at which a file was transferred from the server 10 to the
music player 30 and recorded in the flash memory 34. The
transfer-to-music-player count denotes the number of times a file
was transferred from the server 10 to the music player 30 and
recorded in the flash memory 34.
[0041] When a certain file (file G in FIG. 2) is transferred to the
music player 30, recorded in the flash memory 34, and deleted from
the flash memory 34 as described later, the
transfer-to-music-player count remains unerased, but the music
player registration date/time is erased. If the same file is later
transferred to the music player 30 and recorded in the flash memory
34, the transfer-to-music-player count is incremented by one and
the reregistration date/time is recorded as the music player
registration date/time. Therefore, the music player registration
date/time constantly represents the last registration date/time and
indicates that the associated file is currently retained in the
music player 30.
[0042] Files A to F are currently retained in the music player 30.
Files H, I, and J have not been transferred to the music player 30
or recorded in the flash memory 34.
[0043] As described later, the CPU 11 of the server 10 references
the server registration date/time, music player registration
date/time, and transfer-to-music-player count to select the files
(songs) to be downloaded into the music player 30.
(File Attached Information in the Music Player: FIG. 3)
[0044] As shown in FIG. 3, the flash memory 34 of the music player
30 records the song name, artist name, length, size, date/time of
registration from server (music player registration date/time),
substantial playback count Kp, and skip count Ks of every file that
is recorded in the flash memory 34.
[0045] The term "substantial playback" denotes a continuous
playback of a song for a duration not shorter than a predetermined
one (e.g., for a duration not shorter than 10 seconds). The term
"skip" denotes a playback of a song for a duration shorter than a
predetermined one (e.g., for a duration shorter than 10 seconds).
As described earlier, the term "skip" does not refer to a switch
from one song name to another on the LCD of the music player 30,
which is made to select the song to be played.
[0046] However, the predetermined duration for a substantial
playback may be longer than the predetermined duration for a skip.
For example, the substantial playback may represent a continuous
playback of a song for a duration not shorter than 30 seconds,
whereas the skip may represent a playback of a song for a duration
shorter than 10 seconds.
[0047] When a user-selected song is played, the CPU 31 of the music
player 30 judges whether the playback is a substantial playback or
skip (an intermediate playback, which is neither a substantial
playback nor a skip, may occur if, as described above, the
predetermined duration for a substantial playback is longer than
the predetermined duration for a skip), determines the substantial
playback count Kp and skip count Ks, and records the counts in the
flash memory 34 as a playback history.
[0048] The free space of the flash memory 34 is the size of an
unoccupied song data recording area excluding an area where the
information about songs is recorded as indicated in FIG. 3.
[0049] As described later, the CPU 31 of the music player 30 or the
CPU 11 of the server 10 selects the files to be deleted from the
flash memory 34 of the music player 30 in accordance with the
above-mentioned substantial playback count Kp and skip count Ks
when files selected by the server 10 are to be transferred.
One Embodiment of a Music Data Transfer/Recording Method: FIGS. 4
to 7
[0050] When the music player 30 of the music recording/playback
system described above is placed on the cradle 20 while the server
10 and music player 30 are running, the music player 30 is
connected to the server 10 so that the server 10 downloads files
(song data) to the music player 30 as described below.
(Selecting the Song to be Transferred)
[0051] The CPU 11 of the server 10 references the server
registration date/time, music player registration date/time, and
transfer-to-music-player count of every file that is recorded on
the hard disk 14, and preferentially selects a file that is
recorded on the hard disk 14, is not retained in the music player
30, has not been transferred to the music player 30, and has been
most recently registered in the server, as the file to be
transferred to the music player 30.
[0052] In the examples shown in FIGS. 2 and 3, files H, I, and J
are retained in the server 10. However, files H, I, and J are not
retained in the music player 30 and have not been transferred to
the music player 30. Among files H, I, and J, file J is most
recently registered in the server. File G is not retained in the
music player 30, but was previously transferred to the music player
30, recorded in the flash memory 34, and deleted from the flash
memory 34 by performing a process that is described later. Files A
to F are currently retained in the music player 30.
[0053] Consequently, when the timing is as indicated in the
currently used example, file J is selected as the file to be
transferred to the music player 30.
[0054] In the example shown in FIG. 2, however, the server
registration date/time of file I is close to that of file J. When
the difference between the server registration dates/times of a
plurality of files is not greater than the predetermined time, such
as one hour, the server side processing program may be configured
so that such plurality of files (files J and I in the example shown
in FIG. 2) are selected as the files to be transferred to the music
player 30.
(Selecting the Song to be Deleted)
[0055] When the size (download size) of the file to be transferred
from the server 10 to the music player 30 exceeds the free space of
the flash memory 34, the CPU 31 of the music player 30 or the CPU
11 of the server 10 selects the file to be deleted from the flash
memory 34 of the music player 30 in accordance with the substantial
playback count Kp and skip count Ks shown in FIG. 3.
[0056] More specifically, a substantial playback is regarded as a
plus evaluation factor for retaining the associated song, whereas a
skip is regarded as a minus evaluation factor for deleting the
associated song. When the values a and b are weighting
coefficients, the following equation is obtained:
K=a.times.Kp-b.times.Ks Equation (1)
The above is handled as an evaluation function. A song having a
small evaluation function (e.g., a minus evaluation function) will
be preferentially selected as the song to be deleted.
[0057] If, for instance, a=2 and b=1, the following equation is
obtained:
K=2Kp-Ks Equation (2)
[0058] Further, when a song was frequently transferred to the music
player, its substantial play count Kp is low or its skip count Ks
is high. It means that the song was frequently deleted from the
music player 30. It can therefore be estimated that the song does
not match the user's preferences. Therefore, when the server 10
selects the song to be deleted from the music player 30, the server
side processing program may be configured so as to handle the
transfer-to-music-player count Kt as a minus evaluation factor for
deleting the associated song as is the case with the skip count Ks,
handle the value c as a weighting coefficient, handle
K=a.times.Kp-b.times.Ks-c.times.Kt (Equation (3)) as an evaluation
function, and preferentially select a song having a small
evaluation function (e.g., a minus evaluation function) as the song
to be deleted.
[0059] If, in this instance, a=2, b=1, and C=4, the following
equation is obtained:
K=2Kp-Ks-4Kt Equation (4)
[0060] When Equation (2) is used to determine the evaluation
functions K for files A to F, which are retained in the music
player 30 as indicated in the examples shown in FIGS. 2 and 3, the
values outside the parentheses are obtained as indicated in FIG. 3.
Thus, file C is selected as the file to be deleted. When Equation
(4) is used to determine the evaluation functions K, the
parenthesized values shown in FIG. 3 are obtained. Thus, file C is
selected as the file to be deleted.
[0061] However, if the size of the free space of the flash memory
34 is added to the size of the file to be preferentially deleted as
described above and the resultant size is smaller than the download
size (the data size of the file to be transferred from the server
10), the music player side or server side processing program is
configured so that the sum of the data size of the file to be
deleted and the size of the free space of the flash memory 34 is
not smaller than the download size, and that lower-priority files
will be selected as the files to be deleted.
[0062] If two files are to be selected as the songs to be deleted
while the examples shown in FIGS. 2 and 3 are used, files C and D
are selected when Equation (2) is used to calculate the evaluation
function K, and files B and C are selected when Equation (4) is
used to calculate the evaluation function K.
(Process Performed when the Song to be Deleted is to be Selected on
the Music Player Side: FIGS. 4 and 5)
[0063] FIGS. 4 and 5 show examples of processing programs that the
CPU 31 of the music player 30 and the CPU 11 of the server 10
execute for allowing the music player 30 to select the song to be
deleted.
[0064] Referring to FIGS. 4 and 5, the processing program 40 for
the music player 30 first performs step 41 to judge whether the
music player 30 is placed on the cradle 20. If the obtained
judgment indicates that the music player 30 is placed on the cradle
20, the processing program 40 proceeds to step 42 and inquires of
the server 10 whether the server 10 retains a file (song data) that
is to be downloaded.
[0065] In response to the above inquiry, the processing program 50
for the server 10 performs step 51 in which the aforementioned
judgment standard is used to judge whether the file to be
downloaded into the music player 30 is retained in the server 10.
If the file to be downloaded is not found in the server 10, the
processing program 50 proceeds to step 52 and notifies the music
player 30 that the file to be downloaded is not found. If, on the
other hand, the file to be downloaded is found, the processing
program 50 proceeds to step 53 and notifies the music player 30 of
a download size.
[0066] After completion of step 42, the music player 30 proceeds to
step 43. In step 43, the music player 30 notes the notification
from the server 10 to judge whether the file to be recorded in the
flash memory 34 is available. If the file to be recorded is not
available, the music player 30 immediately terminates the process.
If, on the other hand, the file to be recorded is available, the
music player 30 proceeds to step 44 and detects the free space of
the flash memory 34. The music player 30 further proceeds to step
45 and judges whether the free space is not smaller than the
download size.
[0067] If the free space is smaller than the download size, the
music player 30 proceeds from step 45 to step 46, selects the file
to be deleted in a manner described earlier, and deletes the file
from the flash memory 34. The music player 30 then proceeds to step
47. If, on the other hand, the free space is not smaller than the
download size, the music player 30 jumps from step 45 to step 47
without deleting any file from the flash memory 34.
[0068] In step 47, the music player 30 sends a file transfer
request to the server 10. In response to the request, the server 10
performs step 54, which follows step 53, to transfer the file
selected in step 51 to the music player 30. The music player 30
then performs step 48, which follows step 47, to record the
transferred file in the flash memory 34.
[0069] The music player 30 further proceeds to step 49. If a file
was deleted in step 46, the music player 30 sends a notification
and the file identification information about the deleted file to
the server 10 to indicate that the file was deleted. If no file was
deleted in step 46, on the other hand, the music player 30 sends a
notification to the server 10 to indicate that no file was deleted.
The server 10 then proceeds to step 55, which follows step 54, and
performs a process in accordance with the notification from the
music player 30.
[0070] If a file is deleted by the music player 30, the server 10
deletes the music player registration date/time of the deleted
file. This causes the server 10 to recognize that the file is no
longer retained in the music player 30.
[0071] The above example indicates that a song in the music player
30 can be naturally replaced by another song in the server 10 in
accordance with the user's estimated preferences and wishes and
without requiring the user to perform a special procedure, exercise
judgment, or become conscious of individual songs.
[0072] The example shown in FIGS. 4 and 5 relates to a case where
the file to be downloaded is available and the server 10 transfers
the file to the music player 30 in compliance with a request from
the music player 30 after notifying the music player 30 of the
download size. The processing program may be configured so that the
server 10 transfers the file to the music player 30 at the time of
download size notification, and that the music player 30
temporarily stores the file in the memory 33, and further that, if
any file is to be deleted from the flash memory 34, the file
temporarily stored in the memory 33 is recorded in the flash memory
34 after deletion of the file to be deleted.
(Process Performed when the Song to be Deleted is to be Selected on
the Server Side: FIGS. 6 and 7)
[0073] FIGS. 6 and 7 show examples of processing programs that the
CPU 31 of the music player 30 and the CPU 11 of the server 10
execute for allowing the server 10 to select the song to be
deleted.
[0074] Referring to FIGS. 6 and 7, the processing program 60 for
the music player 30 first performs step 61 to judge whether the
music player 30 is placed on the cradle 20. If the obtained
judgment indicates that the music player 30 is placed on the cradle
20, the processing program 60 proceeds to step 62 and detects the
free space of the flash memory 34. Further, the processing program
60 proceeds to step 63, indicates the free space and the playback
history (substantial playback count Kp and skip count Ks) of every
file that is recorded in the flash memory 34, and inquires of the
server 10 whether the server 10 retains a file that is to be
downloaded.
[0075] In response to the above inquiry, the processing program 70
for the server 10 performs step 71 in which the aforementioned
judgment standard is used to judge whether the file to be
downloaded into the music player 30 is retained in the server 10.
If the file to be downloaded is not found in the server 10, the
processing program 70 proceeds to step 72 and notifies the music
player 30 that the file to be downloaded is not found. If, on the
other hand, the file to be downloaded is found, the processing
program 70 proceeds to step 73 and judges whether the free space
indicated by the music player 30 is not smaller than the download
size.
[0076] If the free space is not smaller than the download size, the
server 10 proceeds from step 73 to step 74 and transfers the file
to be recorded, which was selected in step 71, to the music player
30.
[0077] If, on the other hand, the free space is smaller than the
download size, the server 10 proceeds from step 73 to step 75, uses
Equation (2) or (4) to calculate the evaluation function K for
every file recording in the flash memory 34 of the music player 30
in accordance with the substantial playback count Kp and skip count
Ks indicated by the music player 30, and selects the file to be
deleted in a manner described earlier. Further, the server 10
proceeds to step 76, notifies the music player 30 of the file to be
deleted, and transfers the file to be recorded, which was selected
in step 71.
[0078] After completion of step 63, the music player 30 proceeds to
step 64 and judges whether any file is to be recorded in the flash
memory 34. If, in step 72, the music player 30 is notified that no
file is to be downloaded from the server 10, the process terminates
immediately.
[0079] If, in step 74 or 76, the file to be recorded is transferred
from the server 10, the music player 30 proceeds from step 64 to
step 65 and judges whether any file is to be deleted from the flash
memory 34.
[0080] If, in step 76, the file to be deleted is specified by the
server 10, the music player 30 proceeds from step 65 to step 66,
deletes the specified file from the flash memory 34, and then
proceeds to step 67. If, in step 74, the server 10 did not specify
the file to be deleted, the music player 30 jumps from step 65 to
step 67 without deleting a file from the flash memory 34.
[0081] In step 67, the music player 30 records in the flash memory
34 the file transferred from the server 10 in step 74 or 76.
Meanwhile, the server 10 proceeds to step 77 after completion of
step 76. In step 77, the server 10 deletes the music player
registration date/time of the file to be deleted from the music
player 30.
[0082] In the above example, too, a song in the music player 30 can
be replaced by another song in the server 10 in accordance with the
user's estimated preferences and wishes and without requiring the
user to perform a special procedure, exercise judgment, or become
conscious of individual songs.
[0083] The example shown in FIGS. 6 and 7 relates to a case where
the music player 30 indicates the free space of the flash memory 34
to the server 10. However, the server 10 can determine the total
data size of the song data recorded in the flash memory 34.
Therefore, if the total size of the song data recording area of the
flash memory 34 is known, the server 10 can calculate the free
space of the flash memory 34. Thus, the music player 30 does not
have to indicate the free space of the flash memory 34 to the
server 10.
[0084] The example shown in FIGS. 6 and 7 relates to a case where
the music player 30 initially indicates the playback history
(substantial playback count Kp and skip count Ks) of every file
recording in the flash memory 34 to the server 10. However, the
processing program may alternatively be configured so that the
playback history of every file recording in the flash memory 34 is
transmitted from the music player 30 to the server 10 in compliance
with a request from the server 10 when the server 10 judges that
the free space of the flash memory 34 is smaller than the download
size.
Other Embodiments
[0085] When selecting the song to be deleted, the foregoing
embodiment considers both the substantial playback count Kp and
skip count Ks. Alternatively, however, the song to be deleted may
be selected while considering either the substantial playback count
Kp or the skip count Ks.
[0086] The foregoing embodiment is configured so that a download is
performed when the music player 30 is placed on the cradle 20.
Alternatively, however, a download may be performed when, for
instance, the schedules of the music player 30 and server 10 are
synchronized with each other.
[0087] The storage section of the music player does not always have
to be a flash memory. The storage device of the server does not
always have to be a hard disk.
INDUSTRIAL APPLICABILITY
[0088] As described above, the present invention makes it possible
to replace a song in the music player 30 by another song in the
server 10 naturally in accordance with the user's estimated
preferences and wishes and without requiring the user to perform a
special procedure, exercise judgment, or become conscious of
individual songs.
* * * * *