JP2001324985A - Music distribution method and music storage method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a music distribution method by which redownloading of music data, which are distributed once, is easily conducted. SOLUTION: An ID, which specifies a user who desires a delivery, and a music code, which specifies the music to be distributed, are received and discrimination is made to determined whether the user has already received the distribution of the music or not based on the ID and the music code. When the music is already distributed, a redistribution is conducted employing a standard which differs from a normal distribution.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a music distribution method for distributing music song data using a communication line and a music storage method for storing music song data.

[0002]

2. Description of the Related Art There has been a service for distributing music data of music using a communication line such as the Internet. This is because a user who wishes to distribute music song data accesses a music distribution site from his / her personal computer (PC) or mobile terminal via the Internet, and downloads music data from the music distribution site. Downloaded and stored in the memory of PC or mobile terminal,
The stored music data is reproduced using specific reproduction software. In addition, the user paid a predetermined cost per music to a music distribution site when downloading music music data.

[0003]

In such a conventional music distribution service, a user can download and store music data of a new music when the memory of his or her PC or portable terminal becomes full. Will be gone. In this case, the user usually needs to delete the song data that is no longer heard, but if the user tries to listen to the song once deleted, or deletes the necessary song data by mistake. In this case, it becomes necessary to receive distribution of music song data again from a music distribution site. It is troublesome to download the music data again from the music distribution site, and there is a problem that a predetermined cost is generated again.

In the case of a PC or a portable terminal whose memory can be replaced, if the memory is replaced, the music data can be downloaded and stored again. However, the memory is expensive, and the replacement memory is used. There was also a problem that they had to carry them together. Furthermore, even if a failure occurs in the communication line during download and the line is disconnected in the middle, or if the download was not performed properly, distribution of music song data from the music distribution site again There was a problem that it was necessary to receive Further, downloading of various data such as image data and programs has the same problem.

An object of the present invention is to solve the above-mentioned problem, and an object of the present invention is to provide a music distribution method capable of easily re-downloading data such as music data once distributed. I do. Another object of the present invention is to solve the above-mentioned problem, and to provide a music storage method that can easily re-download data such as music data once distributed. .

[0006]

In order to solve the above-mentioned problems, a music distribution method according to the present invention receives an ID for specifying a user who desires distribution and a music code for specifying a music desired for distribution. , ID and song code to determine whether the user has already delivered the song,
When distribution has already been received, re-distribution is performed based on criteria different from normal distribution.

[0007] Even if the music data once distributed on the user side may be lost, the music data can be restored under conditions different from normal distribution (usually at a low price). Furthermore, if the distribution has already been received, it is further determined whether or not the condition for re-distribution is met, and only when the condition for re-distribution is met, re-delivery is performed according to a different standard from the normal condition. Is preferred.

Further, the re-distributable condition preferably limits the period during which re-distribution can be performed to a predetermined period, and preferably changes the criterion according to the length of the predetermined period. The capacity load of the music distribution company server is suppressed, and the effect of preventing unauthorized copying can be expected. Further, the redistributable condition is preferably one that limits the number of times redistribution can be performed, and it is preferable to change the reference in accordance with the number of redistributions. The effect of preventing unauthorized copying can be expected.

[0009] Further, it is preferable that the re-distributable condition is one that limits an interval at which re-delivery is performed. It is also expected that the effect of preventing repetition of redelivery at short intervals, which is considered to be an illegal copy, can be expected.
Further, it is preferable to detect the number of redistributions and change the reference in accordance with the detected number of redistributions. The redistribution fee for old songs, which had many redistributions, was designed to be cheaper.

[0010] Furthermore, it is preferable to change the re-distributable condition based on the release date of the music. This is to harden the guard for new music that is likely to be illegally copied. Further, the determination as to whether or not the distribution has already been performed is based on the song data stored in association with the ID,
Preferably, the search is performed by searching based on the received ID.

Further, it is preferable that the ID is set so as not to be rewritable for a download device of a user who desires distribution. Restrict the devices that can download,
An attempt was made to prevent unauthorized copying. Furthermore, it is preferable that the installation program of the download program for receiving the music data to the download device has an ID setting program for setting an ID. This makes it possible to easily set a dedicated ID and to prevent unauthorized modification of the ID.

Further, as an ID, a terminal I used by the provider to specify the download device of the user is used.
It is preferable to use D or telephone number display display data. Further, it is preferable that the user can set a plurality of IDs. This is for the sake of convenience when the same user has a plurality of download devices.

Further, it is preferable that the re-distribution is executed by converting the compression format of the music data into a specified format. This makes it possible to cope with a reproducing device employing a different data compression format. In order to solve the above problems, a music storage method according to the present invention provides an ID for specifying a user who wants to store, a music code for specifying a music to be stored, and a music to be stored. Song data is stored in association with each other, and an ID for specifying a user who wants to transmit and a music code for specifying a music to be transmitted are received from a user who wants to transmit, and the received transmission requesting user ID If the desired transmission music code matches the stored desired storage user ID and stored desired music code, the music data corresponding to the desired storage music code is transmitted to the desired transmission user.

There is no need for re-distribution from a music distribution company,
It is possible to delete the music data from the player itself and to receive the music data when necessary. Further, it is preferable to charge the storage requesting user according to the number of songs desired to be stored and the storage desired period. An appropriate fee structure is set according to the load of the storage service company server.

Further, it is preferable that the storage desired music code is stored for each storage desired user, and the storage desired music data is shared by a plurality of storage desired users. This prevents large-capacity music data from being redundantly stored, thereby saving storage capacity. Furthermore, it is preferable that the desired music can be searched and sorted by using the desired music code stored for each desired user.

Further, in order to solve the above-mentioned problem, a data distribution method according to the present invention receives an ID for specifying a user who wants distribution and a data code for specifying data to be distributed. Based on the data code, it is determined whether or not the user has already delivered data, and if it has already been delivered, re-delivery is performed according to a different standard from normal delivery. And

Further, in order to solve the above problems, a data storage method according to the present invention provides an ID for specifying a user who wants to store, a data code for specifying data to be stored, and a storage method. Desired data is stored in association with each other, and an ID for specifying a user who wants to transmit and a data code for specifying data to be transmitted are received from a user who wants to transmit. When the desired transmission data code matches the stored desired user ID and the desired stored data code, the data corresponding to the desired storage data code is transmitted to the desired transmission user.

[0018]

Embodiments of the present invention will be described below with reference to the drawings. FIG. 1 is a schematic diagram for explaining a system according to the music distribution method of the present invention. 10
Is a network such as the Internet, 20 is a music distribution company server connected to the network 10, 30 is a provider connected to the network 10, and 50 is a financial institution terminal connected to the network 10. Provider 3
Further, a plurality of user terminals 4 are connected to a telephone line or the like.
0 is connected to be accessible. User terminal 40
Is a PC, a mobile phone, or the like.

The music distribution company server 20 is composed of a CPU and the like, and has a processing section 21 having various communication functions and data processing functions, a keyboard and a mouse, etc., an input section 22 capable of inputting various data, and a display. And an output unit 23 configured to display or print out various data and a storage unit 24 configured to store various data. The storage unit 24 also stores a main program for executing various processes in the music distribution company server, a distribution user database 25 (to be described later, “distribution user D”).
B), a distribution music database 26 (hereinafter referred to as “distribution music DB”), and a distribution fee database 27 (hereinafter referred to as “distribution fee DB”).

FIG. 2 is a flowchart showing a procedure for installing a download program required for a user who desires distribution to receive distribution. At first,
The user terminal 40 sets and starts the download program (step 202). The download program may be supplied from a music distribution company on a recording medium such as a CD-ROM, or may be downloaded via the Internet or the like according to a predetermined procedure.

Next, the download program installs a “distribution program” to be started when receiving the distribution in a predetermined file in the memory of the user terminal 40 (step 203). The “distribution program” is a program for controlling an operation procedure on the user terminal 40 side when receiving distribution of music data. Next, the user terminal 4
No. 0 connects to the provider 30 using a telephone line, accesses the music distribution company server 20 via the Internet, and transmits data requesting a user ID (step 204). Note that the connection with the provider 30 will be omitted below.

Next, the music distribution company server 20, which has received the data requesting the user ID from the user terminal 40,
A user ID is determined according to a predetermined processing method, and the determined user ID is transmitted to the user terminal 40 (step 2).
06). Next, the user terminal 40 receives the user ID from the music distribution company server 20 (step 207), and automatically stores the received user ID in the memory (step 208). Instead of giving one user ID to one user, one user ID is assigned to one download device.
When two user IDs are assigned so that they cannot be rewritten, it is preferable that the assigned user IDs are not displayed on the user terminal 40. By setting in this manner, the user can use the user terminal 40 without being conscious of the user ID, and can automatically set the user ID to be transmitted to the music distribution company server 20. is there. Steps 204 to 208 can be said to be an ID setting program for setting a user ID.

Next, a password is input at the user terminal 10 (step 209), and the input password is transmitted to the music distribution company server 20 (step 210).
Note that this operation is preferably repeated a plurality of times in order to be careful in confirming the password. Next, the music distribution company server 20 receives the password 20 (step 211), stores it in the storage unit 24 with the user ID determined in step 206 (step 212), and sets the user ID and password. A confirmation signal is transmitted to the user terminal 10 (step 213).

The user terminal 10 receives the confirmation signal (step 215), and ends this program. By completing this processing, the user can access the music distribution company server 20 and receive music data distribution thereafter. It should be noted that although not specified here, confirmation of a settlement means for settlement of a fee when the distribution is received, for example, a credit card is also performed in parallel.

Further, the music distribution company server may provide the CPU number of the user terminal 40, the telephone number of the user (obtained by using a number display or the like) as needed, and the provider 30 to specify the user terminal independently. The adopted ID and the like can be stored in the storage unit 24 as a user ID or as an auxiliary ID and used. Furthermore, the same user assigns the second and subsequent terminals the same user ID.
If it is desired to use this, an additional user ID can be provided.

FIG. 3 is a flowchart for explaining a procedure for receiving distribution of music data between the user terminal 40 and the music distribution company server 20. Here, the user terminal 4
0 means that the music distribution company server 20 is actually accessed via the provider 30 and the network 10, but that point will be omitted below. Note that this procedure is executed by the “distribution program” described above on the user terminal 40 side, and the processing section is executed by the music distribution company server 20 according to the main program.

First, the user terminal 40 transmits the user ID, the password, and the music code of the music desired to be distributed determined by the procedure shown in FIG. 2 to the music distribution company server 20 (step 302). The song code is data determined in advance for one song. Next, the music distribution company server 20 receives the user ID, the password, and the music code (step 303), and uses the distribution user DB to convert the received user data corresponding to the user terminal 40 from the user ID and the password. Identify (Step 3
04). As shown in FIG. 4, the distribution user DB includes a user ID 401, a password 402, and a distributed music code 40.
3, and data items such as distribution date 404. For example, in the example of FIG.
11), all data having the user ID “00011”, in this case, No. 11 Data 1 and 2 are specified (step 304).

Next, it is determined from the user data specified in step 304 and the received music code whether or not the music corresponding to the received music code has already been distributed (step 305). Step 3 if already delivered
06, if not yet delivered, step 308
Proceed to. If it has already been distributed, it is determined whether or not it meets the redelivery condition (step 306). The re-distribution condition refers to a period, the number of distributions, an elapsed period from the previous distribution, an elapsed period from the release date of the song, and the like. The period is to determine whether the access is within a predetermined period. For example, if the redelivery period is 2000
January 1, 2000-October 10, 2000,
It is determined whether or not the access is for the predetermined period. The number of distributions refers to a predetermined number of re-distributable times, for example, two or three times in advance. Further, the elapsed period from the previous distribution is a period in which the distribution can be performed again from the date of the previous distribution, and is predetermined such as 10 days or 30 days. Things. In addition, the elapsed period from the release date of the song is a period in which the distribution of the song desired to be distributed is determined based on the release date of the song. For example, within 6 months from the release date,
It is predetermined in advance, such as two months after the release date. In step 306, the processing unit 21 of the music distribution company server 20 determines whether or not the re-distributable condition is met based on the distribution user DB and the date and time information. Step 3 if the conditions are met
If the condition is not satisfied, the process proceeds to step 308.

Next, if the conditions are met, distribution of music data (data that can be reproduced by using a predetermined reproduction program on the user terminal 40 or the like) is performed in response to the current distribution request. It is determined to be treated as redistribution (step 307). When the process proceeds to step 308, it is determined that the distribution of the music data is treated as a new distribution in response to the current distribution request.

Next, the processing unit 2 of the music distribution company server 20
4 transmits the form of distribution (re-distribution or new distribution) to the user terminal 40 (step 309). If the user terminal 40 (step 310) that has received the distribution form accepts the distribution in the distribution form, the user terminal 40 transmits data for distribution confirmation to the music distribution company server 20 (step 311), and The distribution company server receives the data (step 312). Although not explicitly shown in FIG. 3, if the user terminal 40 does not approve the distribution mode, the flow ends there.

Next, the processing unit 2 of the music distribution company server 20
4 searches for music data corresponding to the transmitted music code from the distribution music DB 25 (step 313), and transmits the music data to the user terminal 40 (step 314). FIG.
As shown in the figure, the distribution music DB 25 is composed of a music code 501, music data 502 and the like. Here, the music data is MP3 (MPEG1 Audio Layer).
The data is stored in a data format compressed in the format 3), but may be stored in another compression technology, for example, TwinVQ, Windows.
ws (R) Media Technology
It is also possible to adopt a data format compressed by es or ATRAC (registered trademark) 3 or the like. Further, in accordance with an instruction from the user terminal 40, the compression format can be changed and transmitted.

Finally, the user terminal 40 connects to the network 1
0, the desired music data is received (downloaded) via the provider 30 (step 315), and the program ends (step 316). The commission for new distribution or re-delivery is determined by the payment method determined in advance.
Settled. For example, in response to a request for payment of a fee from a music distribution company to a partner financial institution terminal 50 (credit card company or the like), a fee is paid from the financial institution to the music distribution company, and the user terminal 40 A method of making a request for payment can be adopted.

As described above, if distribution of the music data once distributed is desired again, and if the distribution conditions are met, the distribution is handled as re-distribution instead of new distribution. Redelivery fee is low (including free) for new distribution
It is set to make redelivery easier to use.
The commission for new distribution and redistribution is the distribution fee DB2
7 is stored in advance. Therefore, when re-distribution is required for some reason, the user can easily receive the distribution again at a lower cost than before.

Although the above example relates to the distribution of music data, various data such as image data or programs can be similarly realized.
The song code and song data in the above description may be replaced with data (program) code and (program) data. Next, a system according to the music storage method of the present invention will be described with reference to FIG. As in the case of FIG. 1, 10 is a network such as the Internet, 20 is a plurality of music distribution company servers connected to the network 10, 30 is a provider connected to the network 10,
40 is a user terminal accessible to the provider 30, and 50 is a financial institution terminal connected to the network 10.

Reference numeral 60 denotes a storage service company server,
As in the music distribution company server 20 of FIG.
It has an input unit 62, an output unit 63, and a storage unit 64. Further, the storage unit 64 includes a main program for executing various processes in the storage service company server, a storage user DB 65, a storage music DB 66, and a storage fee D described later.
B67 is stored.

The storage service company receives a request for storing music data from a user and stores the music data in association with the user. In response to the transmission request of the stored music data from the user, the storage service company makes a request. The received music data is transmitted to the user. When one user receives distribution of music data from a plurality of music distribution companies, or when the user terminal 40 is a mobile phone or the like and cannot always store a large number of music data, the music data is temporarily sent to the storage service company. This system stores data, and if necessary, receives music data not from a music distribution company but from a storage service company, and attempts to reproduce music of the music data. in this case,
There is an advantage that the user can receive the music data from the storage service company without considering distribution and redistribution.

FIG. 7 is a flowchart showing a procedure for a user who wishes to store music data to execute storage of music data. Here, the user terminal 40 actually accesses the storage service company server 60 via the provider 30 and the network 10, but that point is omitted below. First, the user terminal 40 transmits a predetermined user ID, a password, and a song code of a song desired to be stored to the storage company server 60 (step 702). The user ID and the password are determined in advance by the same software as in FIG.

Next, the storage service company server 60 receives the user ID, the password and the music code (step 703), and uses the storage user DB 65 to store the user ID.
Then, the received user terminal 40 is specified from the password and the password (step 704). The storage user DB 65 is shown in FIG.
As shown in the figure, user ID 1001, password 1
002, stored song code 1003 and storage date 100
4 data items.

Next, using the stored music DB 66, it is determined whether or not the music corresponding to the music code received in step 703 is already stored (step 705). If it has already been stored, the process proceeds to step 712. If it has not been stored, the process proceeds to step 706. In other words, if the same music data is stored even by a user other than the accessing user, it is not necessary to receive and store the music data again, and if it can be confirmed that the same music code is stored in the stored music DB 66 In this case, no music data is received from the user terminal 40. In any case, it is also possible to receive music data. The stored music DB 66 has the same data configuration as the distribution music DB shown in FIG.

If not already stored, request data requesting that the music data be transmitted is transmitted to the user terminal 40 (step 706). Next, the user terminal 40 that has received the song data transmission request (step 70)
7) The user ID and music data are transmitted to the storage service company server 60 (step 708). At this time, it is preferable to transmit a password and the like for confirmation.

Next, the processing section 64 of the storage service company server 60 receives the user ID and the music data (step 709), and stores the received music data in the storage music DB 66 together with the music code (step 710). . Next, the processing unit 64 of the storage service company server 60 changes the contents of the storage user DB 65 so as to add that the music data received by the user is stored (711). In addition,
Similarly, even if the music data already exists, the content of the storage user DB 65 is changed to add that the corresponding user has stored the music data (712).

Next, data indicating that the storage of the desired music data has been completed is transmitted to the user terminal 40 (step 7).
13), the user terminal 40 receives the storage completion data (step 714), and this flow ends (step 715). According to the above procedure, the music data desired by the user is stored in the storage service company server 60. Thereafter, by accessing from the user terminal 40, the user can receive the stored music data and play the music on the user terminal. Become like For example, the storage service company sets a fee for each case according to the storage period, and receives a fee from the user according to a predetermined settlement procedure. As the settlement method, the same method as that described for the music distribution service in the music distribution company can be adopted. It should be noted that the data on the fee is stored in the storage fee DB 67.

FIG. 8 is a flowchart showing a procedure for receiving music data once stored. Here, the user terminal 40 actually accesses the storage service company server 60 via the provider 30 and the network 10, but that point is omitted below. At first,
From the user terminal 40, the predetermined user ID, password, music code of the music desired to be transmitted, and transmission instruction data are transmitted to the storage company company server 60 (step 8).
02).

Next, the storage service company server 60 receives the user ID, the password, the music code, and the transmission instruction data (step 803), and uses the storage user DB 65 to extract the received user terminal from the user ID and the password. 40 is specified (step 804). Next, the processing unit 64 of the storage service company server 60 stores the storage music DB 6
6, the music data corresponding to the music code is searched (step 805), and the searched music data is transmitted (step 805).

The user terminal 40 receives the music data (step 807), and this flow ends (step 808). In this way, the user can perform simple operations,
By temporarily storing the music data once distributed in a storage service company, the music data can be received at any time. In addition, according to instruction data from the user terminal 40, a list of previous music data stored by the accessing user is transmitted to the user terminal 40, and the list is searched and sorted in a desired order. Is also possible.

FIG. 9 is a flowchart showing a procedure for a user who wishes to release the storage of the music data to execute the release of the storage of the music data. Here, the user terminal 4
0 actually accesses the storage service company server 60 via the provider 30 and the network 10, but that point is omitted below. First, the user terminal 40 transmits a predetermined user ID, a password, a song code of a song whose storage is desired to be released, and storage release instruction data to the storage company server 60 (step 90).
2).

Next, the storage service company server 60 receives the user ID, the password, the music code, and the storage release instruction data (step 903), and uses the storage user DB 65 to extract the received user ID and password from the received user ID and password. The terminal 40 is specified (Step 904). Next, by using the storage user DB 65, it is determined whether or not there is any user other than the user who has issued the release instruction for storing the song data for which the release instruction has been issued (step 905).
If the tune code for which the release instruction has not been stored except for the user who has issued the storage release instruction, the process proceeds to step 906, where the tune code for which the release instruction has been issued other than the user who has received the storage release instruction is stored. If there is any user, the process proceeds to step 908. That is, even if a plurality of users desire to store the same music data, only one music data is stored in the stored music DB 66 in principle (except for a backup or the like). This is because the song data cannot be deleted.

If the music code for which the release instruction has been issued is not stored except for the user who has issued the storage release instruction, the processing unit 64 of the storage service company server 60 executes the storage music DB
66, the corresponding song data is deleted (step 906), and the contents of the stored user DB 65 are changed so as to add that the deleted user does not store the deleted song data (step 907).

If there is a user who has stored the song code for which the release instruction has been issued other than the user who has issued the storage release instruction, the song data is not deleted from the stored music DB 66, and only the user concerned deletes the deleted music. The contents of the storage user DB 65 are changed so as to add that the data is not stored (step 908). Next, data indicating that the deletion of the music data for which the release instruction has been received is completed is transmitted (step 90).
9), the user terminal 40 receives the data to that effect (step 910), and this flow ends.

In this way, the storage of the music data that is no longer required to be stored can be released. This eliminates the need for the user to pay unnecessary storage fees. In addition,
The above example was about the distribution of song data,
Various data such as image data or programs can be similarly realized. In that case, the music code and music data in the above description may be replaced with data (program) code and (program) data.

[0051]

According to the present invention, in the case of re-distribution, since the distribution can be received on a different basis from the new distribution, the music data once distributed can be easily re-downloaded. Was. In addition, since the music data once distributed is stored in the storage service company, the stored music data can be received at any time regardless of new distribution or redistribution.

[Brief description of the drawings]

FIG. 1 is a diagram showing an outline of a system for implementing a music distribution method of the present invention.

FIG. 2 is a flowchart showing a method of installing a download program.

FIG. 3 is a flowchart showing a distribution procedure.

FIG. 4 is a diagram illustrating an example of a distribution user DB.

FIG. 5 is a diagram showing an example of a distribution music DB.

FIG. 6 is a diagram showing an outline of a system for implementing the music storage method of the present invention.

FIG. 7 is a flowchart showing a procedure for storing music data.

FIG. 8 is a flowchart showing a procedure for receiving music data.

FIG. 9 is a flowchart showing a procedure for canceling storage of stored music data.

FIG. 10 is a diagram illustrating an example of a storage user DB.

[Explanation of symbols]

 DESCRIPTION OF SYMBOLS 10 ... Network 20 ... Music distribution company server 30 ... Provider 40 ... User terminal 50 ... Financial term terminal 60 ... Storage service company server

 ──────────────────────────────────────────────────続 き Continuing on the front page (72) Hideaki Kawaji 1-2-28 Goshodori, Hyogo-ku, Kobe, Hyogo Prefecture Inside Fujitsu Ten Co., Ltd. (72) Daisuke Usui 1-chome, Goshodori, Hyogo-ku, Kobe-shi, Hyogo No. 28 No. 28 F-term in Fujitsu Ten Limited (reference) 5C064 BA07 BC01 BC10 BD02 BD03 BD08 5D045 DA20 9A001 CC02 HH34 JJ19 JZ25 KK62

Claims (22)

[Claims] 1. An ID for specifying a user who desires distribution and a music code specifying music desired to be distributed are received, and the user has already executed distribution of the music based on the ID and the music code. A music distribution method for determining whether or not the music has been distributed and, if the distribution has already been received, performing re-distribution based on a different standard from normal distribution. 2. If the distribution has already been received, it is further determined whether or not the condition for re-distribution is met. The music distribution method according to claim 1, wherein distribution is performed. 3. The music distribution method according to claim 2, wherein the redistributable conditions limit a period during which redistribution can be performed to a predetermined period. 4. The music distribution method according to claim 3, wherein the reference is changed according to a length of the predetermined period. 5. The music distribution method according to claim 2, wherein the redistributable conditions limit the number of times redistribution can be performed. 6. The music distribution method according to claim 5, wherein the criterion is changed according to the number of re-distributions. 7. The music distribution method according to claim 2, wherein the re-distributable condition limits an interval at which re-delivery is performed. 8. The music distribution method according to claim 2, further comprising detecting the number of redistributions and changing the criterion according to the detected number of redistributions. 9. The music distribution method according to claim 2, wherein the re-distributable condition is changed based on a release date of the music. 10. A determination as to whether or not distribution has already been performed, is performed by comparing song data stored in association with the ID with
The music distribution method according to claim 1, wherein the music distribution method is executed by performing a search based on the received ID. 11. The music distribution method according to claim 1, wherein the ID is set so as not to be rewritable for a download device of a user who desires distribution. 12. The music distribution method according to claim 12, wherein an installation program of a download program for receiving music data to the download device includes an ID setting program for setting the ID. 13. The music distribution method according to claim 11, wherein a terminal ID used by a provider to specify a download device of the user is used as the ID. 14. The music distribution method according to claim 1, wherein telephone number display display data is used as the ID. 15. The music distribution method according to claim 1, wherein the user can set a plurality of IDs. 16. The music distribution method according to claim 1, wherein the redistribution is performed by converting a compression format of the music data into a specified format. 17. An ID for specifying a user who wants to store, a music code for specifying a music to be stored,
And storing the song data of the song desired to be stored in association with each other, and receiving from the user desiring transmission an ID for identifying the user desiring transmission and a song code identifying the song desiring transmission. If the received desired transmission user ID and the desired transmission music code match the stored desired storage user ID and the desired storage music code, the music data corresponding to the desired storage music code is written. A music storage method, wherein the music is transmitted to the transmission requesting user. 18. The music storage method according to claim 17, wherein the storage requesting user is charged according to the number of songs desired to be stored and a storage desired period. 19. The music storage method according to claim 17, wherein the storage desired music code is stored for each storage desired user, and the storage desired music data is shared by a plurality of storage desired users. 20. The music storage according to claim 17, wherein the search and rearrangement of the music stored by the storage desired user are executed using the storage desired music code stored for each storage desired user. Method. 21. An ID for specifying a user who desires distribution and a data code for specifying data to be distributed are received, and the user has already executed distribution of the data based on the ID and the data code. A data distribution method characterized by determining whether or not the data has been distributed, and if distribution has already been performed, re-delivery is performed according to a different standard from normal distribution. 22. An ID for specifying a user who wants to store, a data code for specifying data to be stored, and a user who wants to store the data to be stored in association with each other and transmit the data. Receiving an ID for specifying a user who wants to transmit and a data code for specifying data to be transmitted, and storing the received user ID and the desired data code received in the storage request. A data storage method comprising: transmitting data corresponding to the storage desired data code to the transmission requesting user when the data matches the user ID and the storage desired data code.