JP2003345365A - Music usage report reception system and music usage report reception method - Google Patents

Abstract

(57) [Summary] [PROBLEMS] To provide a technology for supporting an operation of receiving a report on use of music in music distribution using a computer network. SOLUTION: A usage report receiving system 100 is a Web service.
A file in which a usage report is recorded is received from a user on a Web page provided by the front unit 110. The file in which the usage report is recorded is given a name according to a predetermined rule, and the usage report receiving system 100 registers the usage report in the licensor information database 210 according to the file name. Further, the usage report receiving system 100 specifies the usage fee calculation rule from the file name, calculates the usage fee pertaining to the usage report for each predetermined period, and charges the user.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a technique for receiving from a user a report on the use of music in music distribution using a computer network.

[0002]

2. Description of the Related Art In recent years, music distribution services using computer networks typified by the Internet have become popular regardless of individuals or companies.
Since the music that is the target of music distribution is a copyrighted work, the person who performs the music distribution service (distributor) receives a license from the copyright holder of the copyrighted work in principle and pays a usage fee according to the usage I have to pay.

[0003] Generally, the fee for music is charged by the composer
A copyright management organization that manages copyrights, rather than managing them by authors such as lyricists, music publishers, etc. Is being collected.

In order for the copyright management organization to calculate the usage fee charged to the user and to distribute the usage fee collected from the user to the right holder, the user uses which song how many times. You will need information on what you did.

For this reason, the copyright management organization regularly receives reports on the use of music pieces on the computer network from the users who have given permission for use.

[0006]

Conventionally, music usage reports have been made by paper or electronic mail. That is, the user sends a paper in which the track record of music is used to a copyright management organization, or sends an electronic mail in which the track record of music is used to make a usage report.

[0007] However, such a method may complicate the usage report received from the user for the copyright management organization, which may hinder the smooth execution of the work. In particular, when the number of managed songs is large or the number of licensees is large, the problem becomes more serious. For this reason,
It is desired to develop a technology for supporting the processing of receiving a usage report by a copyright management organization.

An object of the present invention is to provide a technique for supporting the work of receiving a report on the use of music in music distribution using a computer network.

[0009]

In order to solve the above problems, according to the first aspect of the present invention, the usage information of the music is provided for each license agreement from the terminal device of the licensee via the computer network. A music use report reception system for receiving a report file including the authentication screen for authenticating the licensee, and information on the license agreement to be reported to the authenticated licensee for reporting instructions. Web front means for displaying a list display screen displayed in association with the button and a file designation screen for accepting the designation of the report file on the terminal device of the licensee, and reception for receiving the report file for which the designation is accepted There is provided a music use report reception system characterized by comprising:

[0010] Here, when the Web front means accepts the selection of the button for the report instruction on the list display screen, it accepts the designation of the report file relating to the license contract associated with the selected button. The file designation screen can be displayed on the terminal device of the licensee.

Further, the system further comprises a usage information database for managing the usage information contained in the usage report file for each license agreement, and the receiving means specifies the license agreement based on the file name of the received report file. However, it can be recorded in the usage information database.

Further, the usage report file includes a music identifier and a title of the music, and the music identifier,
A music database that stores the titles of music in association with each other, and a music identifier that matches the music identifiers and music titles included in the received usage report file with the music identifiers and music titles stored in the music database. It is possible to further include a collating unit.

In this case, the usage report file includes information indicating whether or not matching is required, and the music identifier matching means requires matching of information indicating whether or not matching is required in the received usage report file. With respect to the music indicating that, the music identifier and the title of the music can be matched with the music identifier and the title of the music stored in the music database.

In order to solve the above problems, according to a second aspect of the present invention, there is provided a music usage report acceptance method for accepting music usage information for each license agreement from a music usage licensee. The step of displaying an authentication screen for authenticating the licensor on the terminal device of the licensor, and information on the license agreement to be reported for the authenticated licensor,
A step of displaying it on the terminal device of the licensee in association with a button for report instruction; a step of displaying a file designation screen for accepting the specification of the report file on the terminal device of the licensee; a report accepting the specification And a step of receiving a music file, the method for accepting a music usage report is provided.

[0015]

BEST MODE FOR CARRYING OUT THE INVENTION Embodiments of the present invention will be described with reference to the drawings.

First, an outline of the usage fee management work for music distribution using a computer network such as the Internet will be described with reference to the flowchart of FIG.

The usage fee management work for music distribution using a computer network can be roughly divided into the following processes, as shown in this flowchart. That is, a license process (S10) for licensing the person who wants to use the music on the computer network.
1), a usage report acceptance process (S102) for receiving a music usage report from the user, a usage fee calculation process (S103) for calculating a usage fee based on the usage report, and a usage fee collection process for collecting a usage fee from the user (S104) and usage fee distribution processing of distributing the collected usage fee to the right holder (S105)
Is.

Here, prior to the description of the usage report receiving system to which the present invention is applied, an outline of the usage permission processing (S101) which is a prerequisite for usage reporting processing will be described.

The use permission process (S101) is a process for accepting a use permission application for a music and giving a use permission to a person who is using the music such as music distribution on the Web page or who intends to use the music. Is.

The content of the license determined at the time of application for the license, for example, the specification method of the music to be used, the calculation method of the usage fee for the usage, and the like can take various forms.

In this embodiment, the method of designating the music to be used is not to specify the music and give the permission, but to give the permission comprehensively to all the repertoires of the copyright management organization. For this reason, it becomes necessary to report to the copyright management organization which music was actually used after the use.

The usage fee is calculated according to the number of times of use (for example, the number of times of downloading), which is a pay-as-you-go system, and the number of songs used, regardless of the number of times of usage. One of the flat rates shall apply. Whether the pay-as-you-go system or the flat-rate system is applied is determined depending on, for example, whether the usage form of the music is a download format, a stream format, or whether the music distribution is commercial or non-commercial. I shall.
The download format is a delivery format in which music data is downloaded as a file when a predetermined location on the Web page is clicked, and the streaming format is clicked on a predetermined location on the Web page or a predetermined Web page is displayed. Then, the distribution format is such that music is played or music data is displayed on the spot.

Usage in the case of the pay-as-you-go system The unit price per one time and the flat rate in the case of the flat-rate system are, for example, whether the music distribution is commercial or non-commercial It can be determined depending on whether information charges are collected, whether there is advertisement income, and the like. The information fee is a fee collected by the user from the recipient when the music is delivered.

In the present embodiment, whether the music distribution is commercial or non-commercial, whether the usage format is download format or stream format, and in the case of commercial, whether there is an advertisement income, It is assumed that the usage fee calculation categories are set according to combinations such as whether or not to collect information fees when using, and the usage fee calculation rules are set for each usage fee calculation category.

The usage fee calculation rule is set for each music distribution service type. Here, the service type is, for example, audio-only distribution (download /
Stream service, mobile phone incoming melody distribution service, lyrics score information distribution (download / stream) service, voice distribution (download / stream) service associated with other copyrighted material (video / e-book, etc.), etc. Regarding, the usage fee calculation rule is established. FIG. 2 is a diagram showing an example of a usage fee calculation rule for an audio-only delivery service (download / stream).

In the present embodiment, it is assumed that the user receives a license for each service type and makes a usage report for each service type. That is, when the music is used over a plurality of service types, the usage permission is received for each. Since the user specifies in what manner the music is to be used and applies for the license, the service type and the usage fee calculation category are determined at the time of license. That is, the method of calculating the usage fee is determined.

When the copyright management organization makes a license for each service type, it issues a license ID for identifying the license agreement and notifies the user. This license I
The D includes information for specifying the service type and the usage fee calculation category determined from the content of permission.
In the present embodiment, as an example, the license ID is a three-digit number for identifying the user and a two-digit number for identifying each license when the user has a plurality of licenses. Number and 1 to identify the service type
It shall consist of a character symbol and a one-digit number for specifying the usage fee calculation category.

Next, a usage report reception system to which the present invention is applied will be described. The usage report reception system uses the usage report reception process (S10) in the usage fee management work described above.
2), processing related to the usage fee calculation processing (S103) and usage fee distribution processing (S105). FIG. 3 is a block diagram for explaining the configuration of the usage report reception system 100 in this embodiment. Usage report reception system 10
0 is on the Web page managed by the copyright management organization,
A usage report of music is received from a user via a computer network.

As shown in the figure, the usage report reception system 100 includes a Web front unit 110 and a code verification unit 1.
20, a fee calculation unit 130, a distribution processing unit 140,
It is configured to include a licenser information database 210, a music information database 220, and a rights information database 230.

The Web front unit 110 performs a process for exchanging electronic information with a user's terminal via a computer network. For this reason, the Web front unit 110 has a display unit 111 that performs a process for displaying a Web page on the user's terminal, and a receiving unit 112 that performs a process for receiving usage report information sent from the user's terminal. It has and.

The chord verification unit 120 carries out a process for verifying whether or not the identifier (music code) of the music relating to the usage report of the user is correct.

The usage fee calculation unit 130 performs processing for calculating the usage fee to be collected from the user based on the usage report of the user. Therefore, the usage fee calculation unit 130
You can refer to the usage fee calculation rule.

The distribution processing unit 140 performs processing for distributing the usage fee collected from the user to the right holder.

The licenser information database 210 is a database for managing license information for each licenser (user).

FIG. 4 is a diagram for explaining the data structure of the licenser information database 210. As shown in this figure, the licensor information database 210 includes a licensor ID 211 for identifying the licensor, a password 212 used for certifying the licensor, and an email address 213 of the licensor.
And the usage permission information 214 that manages information for each usage permission, that is, for each service type. Licensor I
The D211, the password 212, and the e-mail address 213 are registered when the user first makes a contract with the copyright management team.

The use permission information 214 is provided for each use permission.
Permission ID 311, service type 312, usage fee calculation category 313, contract period 314, usage report information 315 that manages information for each usage report, usage fee billing information that manages usage fee billing information for each usage report 316 and The license ID 311, the service type 312, the usage fee calculation category 313, and the contract period 314 are registered at the stage when the user has received a license for a certain service type.

The usage report information 315 is, for each usage report,
Report target year 411, report date 412, and music information 41
3 and the status 414 are managed. Reportable year 4
11 is the year and month that is the target of the usage report. In addition, in the present embodiment, the usage report is performed on a monthly basis. The music information 413 manages information for each music used. The status 414 is information indicating the status regarding the usage report. The status regarding the usage report can be, for example, “usage report accepted”, “usage report is being checked”, “usage report accepted”, “usage fee charged”, “payment completed”, or the like. The report target year 411, the report date 412, and the music information 413 are registered when the usage report is received from the user. The status 414 is registered as "use report accepted" when the use report is received from the user. After that, according to the processing content of the usage report receiving system 100, the status changes to “during usage report checking”, “usage report accepted”, “usage fee charged”, and the like.

The music information 414 manages a collation code 511, a music code 512, a title 513, a composer 514, an information fee 515, and a usage count 516 for each music related to the usage report. The collation code 511 is a code used for the music code check processing described later, and is blank.
It is possible to have "correct" and "wrong" states. The music code 512 is an identifier for identifying a music. In copyright management organizations, music codes are attached to music to be managed in advance. The title 513 is the title of the music relating to the usage report. The composer 514 is the name of the composer of the music relating to the usage report. The information fee 515 is a fee collected from the recipient when the music is delivered. Number of uses 516
Is the number of times the music is used. The music information 414 is registered based on the content of the usage report when the usage report is received from the user.

Usage fee billing information 31 of the usage permission information 214
6 manages a billing target year 421, a billing date 422, a billing amount 423, a payment date 424, and detailed information 425 for each usage report. The billing target year 421 is the year and month for which the usage fee is billed. The charge amount 423 is the amount charged to the user. The billing amount 423 is registered as a result of the usage fee calculation process described later. The payment date 424 is the date on which the user paid the usage fee. The detailed information 425 manages the usage fee for each song in the usage report and the information used as the basis for calculating the usage fee.

The detailed information 425 includes a collation code 521, a music code 522, a title 523, a composer 524, an information fee 525, a usage count 526, and a usage fee 527 for each piece of music relating to the usage report. to manage. Of these,
Music code 522, title 523, composer 524,
As the information fee 525 and the number of times of use 526, the information of the music information in the usage report from the user is basically registered as it is. However, regarding the music code 522, if it is found as a result of the music code check described later that the user makes an error report, the music code 522 is corrected and registered. At this time, in order to show that the music code 522 was incorrect,
The collation code 521 is registered as "wrong" (details will be described later). The usage fee 527 is a usage fee for the music relating to the usage report in the case of the pay-as-you-go system.

Next, the music information database 220 will be described. The music information database 220 manages basic information about music managed by a copyright management organization.

FIG. 5 is a diagram for explaining the data structure of the music information database 220. As shown in the figure, the music information database 220 has a music code 221.
Manages the title 222 and the composer 223.

Next, the right information database 230 will be described. The rights information database 230 manages rights information about songs managed by a copyright management organization.

FIG. 6 is a diagram for explaining the data structure of the right information database 230. As shown in the figure, the right information database 230 has a music code 231.
The collection ratio 232 and the distribution information 233 are managed.
The collection ratio 232 is the ratio of the copyright management organization's share of the music usage fee. This is because, depending on the piece of music, the copyright management may be outsourced to a copyright management organization in which the composer, the lyricist, etc. are different. The distribution information 233 is information about how the copyright management organization distributes the usage fee collected from the user to the right holder for the music. For example, it is possible to set A% for the composer A, B% for the lyricist B, and C% for the music publisher Hei.

Next, the processing of the usage report acceptance system 100 in this embodiment will be described. FIG. 7 shows We
FIG. 6 is a diagram for explaining an example of screen transition of a web page provided to the user on the display unit 111 of the b front unit 110.

First, the usage report acceptance process (S102) will be described with reference to the flowchart of FIG.

As described above, the music user makes a music usage report every predetermined unit, for example, every month.

When the usage report receiving system 100 receives access for a usage report from the user via the computer network, the usage report receiving system 100 displays a music usage report page 700 as shown in FIG. Prompt input of ID and password (S201).

When the input of the license ID and the password is accepted, the licenser information database 210 is referred to, and the authentication by the password is performed.
A service menu selection screen 710 as shown in (1) is displayed (S202). At this time, referring to the license information 214 of the licenser information database, as shown in FIG. 7, the license ID 311 and the service type 31 relating to the user.
2. The contract period 314 is extracted and displayed as a list.

The user records the usage report of the music in a file in a predetermined format in advance, and attaches a file name according to a predetermined rule. This file should include information about all the songs used in the service type related to the report.

Here, the format of the usage report is such that line breaks are made for each song and the collation flag, song code, title, composer, information fee, and number of uses are separated by predetermined symbols (tabs, commas, etc.). And Note that the collation flag is blank when reporting the music for the first time.

The file name rule is a name obtained by adding the report target year to the license ID issued at the time of license.

The user selects the service menu selection screen 71.
By clicking a report button provided for each service type with 0, a file recording a music usage report can be transmitted to the usage report reception system 100.

That is, when the display section 111 of the Web front section 110 receives the click of the report button on the service menu selection screen 710, it displays the usage report file upload screen 720 as shown in FIG. 7 (S2).
03).

On the usage report file upload screen 720, the user can specify the file in which the music usage report is recorded and click the send button.

When the click of the send button is accepted, W
The reception unit 112 of the eb front unit 110 checks whether the file name complies with a predetermined rule (S204).

As a result, if the rule is not complied with, the file is not received and the fact is displayed to prompt the user to make a correction (S205).

On the other hand, when the rule is followed, the file is received and recorded in the usage report information 315 of the licensor information database 210 (S206). At this time,
Since the service type and the usage fee calculation category are specified from the file name, the reception unit 112 of the Web front unit 110
Can immediately specify which license information 214 is reported. Furthermore, since the reporting target year is also specified from the file name, it is possible to immediately specify which usage report information 315 to be reported.

In recording the usage report information 315, the report date 412 is the file reception date, and the status 414.
Is "reported". Further, the music information 413 records the content of the usage report as it is for each music.

When recording in the usage report information 315, if an error in the recording format or an error such as non-standard data is found, the fact is reported to the user by e-mail and the file is resent. Urge. Further, the status 414 of the usage report information 315 is set to “error”. Further, the service type selection screen 710 also displays that the corresponding service type has an error.

Next, a usage fee calculation process (S103) for calculating the usage fee for each music piece is performed. FIG. 9 is a flow chart for explaining the processing flow of the usage fee calculation processing (S103).

In the usage fee calculation process (S103), the usage fees for each music used are summed up for each service type.

The usage report receiving system 100 performs various processes by using the music code included in the user's report as a key. Therefore, the music code recorded in the licenser information database 210 needs to match the music code registered in the music information database 220.

Therefore, the music code included in the user's report is checked (S302). However, this checking process is performed by the music information 413.
The collation code 511 is blank or "wrong" (that is, other than "correct") music code 512 (S301).

That is, if the number of music pieces managed by the copyright management organization is large, the music code check processing (S30
The load of 2) becomes large. For this reason, it is desirable to omit the music code check process (S302) for the usage report once the music code is determined to be correct.

In this embodiment, when the user makes a usage report for a certain music for the first time, the collation code of the music is left blank. As a result, the music code check (S302) is performed. If the music code is correct, the user is notified of the information that the collation code for the music is "correct" (specifically,
It will be notified in the detailed information described later). When the user reports this music in the subsequent usage report, by registering “correct” in the collation code, it becomes possible to omit the music code check process (S302) relating to this music. . In order to promote the user to register the verification code, the copyright management organization can take an incentive measure, for example, reduce the usage fee for the user who registered the verification code.

In the music code check process (S302), the chord verification unit 120 sets the music code included in the user's report, the title, and the composer to the music code 2221 registered in the music information database. Title and 22
2 is compared with the composer 223. As a result, if all match, it is determined that the music code is correct (S303: Y). In this case, the collation code of the song is "correct" (S304).

On the other hand, if any of them is different (S303: N), the correction work is performed (S305). Although the content of the correction work is arbitrary, it is generally considered that the titles are often the same. Therefore, for example, the music information database 220 is searched based on the title included in the usage report, and the corresponding music code is searched. Extract. Then, the music code of the usage report is corrected. In this case, the collation code of the song is "wrong". In this case, the music code check process (S302) of this music will be performed again in the next usage report.

Next, the usage fee calculation unit 130 specifies the usage fee calculation rule to be applied from the service type 312 and the usage fee calculation category 313 (S306). Further, the collection ratio 322 of the music is extracted from the right information database 230 based on the music code 512.

Then, the usage fee calculation unit 130 uses the usage fee calculation rule, the information fee 515, the number of times of use 516, and the collection ratio 32.
The usage fee for the song is calculated from information such as 2 (S307). In the case of the service type to which the flat rate system is applied, the calculation of the usage fee can be omitted.

Next, the usage fee calculation unit 130 creates usage fee billing information 316 (S308). Usage fee billing information 3
16 is detailed information 425 in units of music for each service type
Is created and registered in the licensor information database. When the billing amount 423 is the pay-as-you-go system, the detailed information 42 for each song
The total of the usage charges 527 of 5 is charged to the user as a usage charge for the service type. In the case of the flat-rate system, a predetermined usage fee is the billing amount 423. Further, as the collation code 521, when the music code check process (S302) is performed, “correct” or “erroneous” is registered according to the result. If the music code check process (S302) is not performed,
The contents of the usage report from the user are registered as they are. In addition, the music code 522, the title 523 of the detailed information 425,
As for the composer 524, the information fee 525, and the number of times of use 52, the contents of the usage report from the user are basically registered as they are as described above.

The usage fee calculation unit 130 uses the usage fee billing information 3
When 16 is created, the user is notified by e-mail that the usage fee has been calculated (S309). And
The status of the usage report information 315 is changed to “usage billed”.

The user can browse the information on the corresponding service type by clicking the license ID column on the service type selection screen 710 shown in FIG.

That is, when the display unit 111 of the Web front unit 110 receives a click in the license ID column, it extracts information about the corresponding service type from the licenser information database 210, and an example is shown in FIG. The service type detailed information screen 730 is displayed.

As shown in the figure, the service type detailed information screen 730 displays information such as status and billing amount for each reporting year (billing target year).

On this screen, the user can confirm the status of the usage report, for example, the report is being accepted, billed, etc., on a year-by-month basis.

The user deposits the invoiced amount for the target year / month of the invoiced status. As a deposit method, for example, transfer or the like can be used.

When the copyright management organization confirms the payment, it determines that the usage fee has been collected (S104), and changes the status 414 of the usage report information 315 of the corresponding service type to "paid". This change is reflected on the service type detailed information screen 730.

The distribution processing unit 140 of the usage report acceptance system 100 refers to the rights information database 230 for the collected usage fee, acquires the distribution information 233 for each song, and calculates the share of each right holder ( S105). Then, the calculated share is distributed to each right holder.

[0080]

As described above, according to the present invention, there is provided a technique for supporting the work of accepting a report on the use of music in music distribution using a computer network.

[Brief description of drawings]

FIG. 1 is a flow chart for explaining an outline of a usage fee management work for music distribution using a computer network.

FIG. 2 is a diagram showing an example of a usage fee calculation rule for an audio-only delivery service (download / stream).

FIG. 3 is a block diagram for explaining the configuration of a usage report reception system 100.

FIG. 4 is a diagram for explaining a data structure of licensor information database 210.

FIG. 5 is a diagram for explaining the data structure of the music information database 220.

FIG. 6 is a diagram for explaining the data structure of the right information database 230.

FIG. 7 is a display unit 111 of the Web front unit 110.
FIG. 4 is a diagram for explaining an example of a screen transition of a web page provided to a user.

FIG. 8 is a flowchart for explaining the flow of processing of the usage report reception processing (S102).

FIG. 9 is a flowchart for explaining the processing flow of the usage fee calculation processing (S103).

[Explanation of symbols]

100 ... Usage report reception system 110 ... Web front section 111 ... Display unit 112 ... Receiver 120 ... Code verification unit 130 ... Fee calculation part 140 ... Distribution processing unit 210 ... Licensor Information Database 220 ... Music information database 230 ... Rights information database

Claims (11)

[Claims] 1. A music use report acceptance system for receiving a report file containing music use information for each license agreement from a terminal device of a music licensee via a computer network, wherein the licensee Screen for displaying the authentication screen for authenticating the license agreement, the information about the license agreement to be reported concerning the authenticated licensee in association with the button for the report instruction, and the file for accepting the specification of the report file A music use report acceptance system comprising: a web front means for displaying a designation screen on a terminal device of a licensee; and a reception means for receiving a report file for which the designation has been accepted. 2. The music use report receiving system according to claim 1, wherein the Web front unit receives a selection of a report instruction button on the list display screen, and a license associated with the selected button is received. A music use report acceptance system, characterized in that a file designation screen for accepting designation of a report file relating to a contract is displayed on a terminal device of a licensee. 3. The music usage report receiving system according to claim 1, further comprising a usage information database that manages usage information included in a usage report file for each license contract, and the receiving unit receives the received report. A music usage report receiving system, characterized in that a license agreement is specified based on the file name of the usage file and recorded in the usage information database. 4. The music usage report receiving system according to claim 1, wherein the usage report file includes a music identifier and a music title, and the music identifier and the music title are associated with each other. And a music identifier collating means for collating the stored music database and the music identifier and music title included in the received usage report file with the music identifier and music title stored in the music database. Characteristic music usage report acceptance system. 5. The music usage report receiving system according to claim 4, wherein the usage report file includes information indicating whether or not matching is required, and the music identifier matching means selects one of the received usage report files. , The information indicating whether the matching is required indicates that the matching is required, the identifier of the song and the title of the song are matched with the identifier of the song and the title of the song stored in the song database. A music usage report reception system. 6. The music usage report receiving system according to claim 3, wherein the usage report recorded in the usage information database is used for each license contract with reference to a rule for calculating a usage fee. A music usage report reception system, further comprising a usage fee calculation means for calculating a fee. 7. The music usage report receiving system according to claim 6, wherein the usage report file includes information indicating the number of times the music has been used, and the usage fee calculation unit uses the usage fee according to the usage frequency. A music usage report system characterized by calculating. 8. The music usage report acceptance system according to claim 6 or 7, wherein the Web front means further displays a license agreement detail screen for displaying the calculated usage fee in association with the corresponding license agreement. Music usage report reception system characterized by being displayed on the terminal device. 9. The music usage report receiving system according to claim 8, wherein the usage information database manages a status related to the status of the usage report for each usage permission, and the Web front means grants permission corresponding to the status. A music usage report reception system characterized by displaying on the license agreement details screen in association with a contract. 10. A music usage report acceptance method for accepting music usage information for each license agreement from a music licensee, wherein an authentication screen for authenticating the licensee is displayed on the terminal device of the licensee. And a step of displaying information on the license agreement to be reported concerning the authenticated licensee on the terminal device of the licensee in association with the button for reporting, and a file for accepting the designation of the report file. A music use report receiving method comprising: a step of displaying a designation screen on a terminal device of a licensee; and a step of receiving a report file for which the designation has been accepted. 11. The music usage report receiving method according to claim 10, further comprising the step of identifying a license agreement based on the file name of the received report file.