JP2012018485A - Request reception device, request reception method and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a request reception device, a request reception method, and a program which can suppress occurrence of deviation in distribution contents.SOLUTION: A request reception device 1 comprises: a control unit 12 which discriminates whether a predetermined restriction condition is met or not; a storage unit 13 which stores a request from a user by classifying according to a category of the request when the control unit 12 determines that the restriction condition is met; and a distribution list generation unit 14 which extracts the request from the requests stored in the storage unit 13, and adds the request to a distribution list.

Description

  The present invention relates to a request reception device, a request reception method, and a program.

  Conventionally, a method of distributing content such as a moving image or sound in response to a request from a user has been proposed (for example, see Patent Document 1).

  Japanese Patent Application Laid-Open No. 2004-151561 discloses a technique for totaling requests from each user according to a predetermined rule and distributing content having a large number of requests, for example. According to this method, even if there is no operator that accepts a request from the user, the content according to the request from the user can be distributed.

JP 2001-358680 A

  However, in the technique disclosed in Patent Document 1, the content to be distributed is determined without considering the content of the request. For this reason, the distribution contents are biased, and the user may get bored.

  Therefore, the present invention has been made in view of the above-described problems, and an object of the present invention is to provide a request reception device, a request reception method, and a program that can prevent the distribution contents from being biased.

  The present invention proposes the following items in order to solve the above-described problems.

  (1) The present invention is determined by the control means (for example, corresponding to the control unit 12 in FIG. 2) to determine whether or not a predetermined restriction condition is satisfied, and that the restriction condition is satisfied by the control means. In this case, storage means (for example, equivalent to the storage unit 13 in FIG. 2) that stores the requests from the users classified according to the category of the request (for example, equivalent to a genre, artist name, and age described later); A request extraction unit (for example, corresponding to the distribution list generation unit 14 in FIG. 2) that extracts a request from the requests stored in the storage unit, and a request that is extracted by the request extraction unit (for example, A list generation means (e.g., corresponding to the distribution list generation unit 14 in FIG. 2) to be added to a distribution list (to be described later). The number of requests stored in the same category as the requests is less than a predetermined upper limit (for example, equivalent to “3” in the first embodiment). A device is proposed.

  According to the present invention, the request receiving apparatus is provided with a control means, a storage means, a request extraction means, and a list generation means. Then, the control means determines whether or not a predetermined restriction condition is satisfied. Then, when the storage means determines that the restriction condition is satisfied by the control means, the request from the user is classified and stored according to the category of the request. Then, the request extraction unit extracts the request from the requests stored in the storage unit, and the list generation unit adds the request extracted by the request extraction unit to the list. Furthermore, as a limiting condition, the number of requests having the same category as the request from the user stored in the storage means is adopted to be less than a predetermined upper limit value. For this reason, the number of requests received from the user can be limited for each category of requests, and as a result, the number of requests reflected in the list can be limited for each category of requests. Therefore, it can suppress that many requests of the same category are reflected in the list. Therefore, by determining the distribution contents based on the list, it is possible to reflect various categories of requests in the distribution contents, and to suppress the distribution contents from being biased.

  (2) The present invention relates to the request reception device of (1), wherein the request extraction unit receives a predetermined number of requests for each category from among the requests stored in the storage unit. The request reception apparatus is characterized in that it is extracted in order from the earliest (for example, corresponding to the first-come-first-served basis described later).

  According to the present invention, the request extraction means extracts a predetermined number of requests for each category from the requests stored in the storage means in order from the earliest received timing. For this reason, the number of requests reflected on the list can be limited for each category of request. Therefore, it is possible to prevent many requests of the same category from being reflected in the list. Therefore, by determining the distribution contents based on the list, it is possible to reflect various categories of requests in the distribution contents, and to prevent the distribution contents from being biased.

  Further, according to the present invention, as described above, the request extraction unit sequentially selects a predetermined number of requests for each category from the requests stored in the storage unit in order from the earliest received timing. It was decided to extract. For this reason, it is possible to preferentially add a request from a user who makes a request earlier to the list.

  (3) The present invention relates to the request reception device of (1), wherein the request extraction means is a predetermined number for each category from among the requests stored in the storage means (for example, the first embodiment The request accepting apparatus is characterized in that a request corresponding to “1” is extracted based on a predetermined priority (for example, a priority described later).

  According to the present invention, the request extraction unit extracts a predetermined number of requests for each category from the requests stored in the storage unit based on a predetermined priority. For this reason, the number of requests reflected on the list can be limited for each category of request. Therefore, it is possible to prevent many requests of the same category from being reflected in the list. Therefore, by determining the distribution contents based on the list, it is possible to reflect various categories of requests in the distribution contents, and to prevent the distribution contents from being biased.

  Further, according to the present invention, as described above, the request extraction unit determines a predetermined number of requests for each category from the requests stored in the storage unit based on a predetermined priority. To be extracted. For this reason, by setting the priority, it may be possible to preferentially determine the delivery content that the user is interested in.

  (4) In the request accepting device according to (2) or (3), the request extracting unit sets the predetermined number according to the number of requests stored in the storage unit. A request receiving apparatus characterized by this is proposed.

  According to the present invention, the request extraction unit sets the predetermined number according to the number of requests stored in the storage unit. For this reason, for example, as the number of requests stored in the storage unit increases, the aforementioned predetermined number is set to be small. Then, since the number of requests for each category reflected in the list decreases, the categories of requests reflected in the list vary. Therefore, by determining the distribution contents based on the list, requests of various categories can be reflected in the distribution contents, and it is possible to prevent the distribution contents from being biased.

  (5) The present invention relates to a content distribution unit (for example, the communication unit 11 in FIG. 2) that distributes content based on a request included in the list for any of the request reception devices of (1) to (4). And the limit condition is a predetermined upper limit value (for example, the second embodiment) in which the number of requests in the same category as the request from the user is stored in the storage means. The request accepting apparatus is characterized in that the request is different from the request for the content being distributed by the content distribution means.

  According to the present invention, the request receiving device is provided with the content distribution means for distributing the content based on the request included in the list. Then, as a restriction condition, the number of requests in the same category as the request from the user is stored in the storage unit is less than a predetermined upper limit value, and the content request being distributed by the content distribution unit Adopted different requests. For this reason, the number of requests received from the user can be limited for each category of request, and a request for content being distributed can be prevented from being received from the user. Therefore, it is possible to prevent a large number of requests of the same category from being reflected in the list, and it is possible to prevent a request for content being distributed from being reflected in the list. Therefore, by determining the delivery content based on the list, requests of various categories can be reflected in the delivery content, and it is possible to suppress the occurrence of bias in the delivery content and to repeatedly deliver the same content in a short time Can be suppressed.

  (6) The present invention provides a content distribution unit (for example, a content distribution unit) that distributes content to a plurality of user terminals based on the requests included in the list for any of the request reception devices of (1) to (5). The number of times the first signal (e.g., equivalent to the opposite command of the second embodiment) is received from the user terminal is equal to the first threshold (e.g., second implementation). Content distribution stopping means (for example, corresponding to the communication unit 11 and the control unit 12 in FIG. 2) for ending the distribution of the content being distributed by the content distribution unit, Has been proposed.

  According to this invention, the request distribution device is provided with the content distribution unit and the content distribution stop unit. Then, the content distribution means distributes the content to a plurality of user terminals based on the requests included in the list. In addition, if the number of times the first signal is received from the user terminal by the content distribution stopping unit is equal to or greater than the first threshold, the distribution of the content being distributed by the content distributing unit is terminated. For this reason, if the user does not want to view the content being distributed and the user receives the first signal from the user terminal, the number of users who do not want to view the content being distributed If is greater than or equal to the first threshold, distribution of this content is terminated. Therefore, content that matches the user's preference can be distributed.

  (7) According to the present invention, in the request reception device of (6), the number of times the second signal (for example, corresponding to the support command of the second embodiment) is received from the user terminal is the second threshold (for example, the second If it is equal to or greater than “50” in the embodiment, the content distribution continuation unit prohibits the end of content distribution by the content distribution stop unit (for example, corresponding to the control unit 12 in FIG. 2). We propose a request accepting device.

  According to the present invention, the request distribution device is provided with the content distribution continuation means for prohibiting the end of content distribution by the content distribution stop means if the number of times the second signal is received from the user terminal is equal to or greater than the second threshold. It was. For this reason, when the user wants to watch the content being distributed to the end, if the second signal is received from the user terminal of this user, the number of users who want to watch the content being distributed to the end If is greater than or equal to the second threshold, the end of distribution of this content is prohibited. Therefore, content that matches the user's preference can be distributed.

  (8) The present invention has determined that a first step (for example, corresponding to step S21 in FIG. 4) for determining whether or not a predetermined restriction condition is satisfied, and that the restriction condition is satisfied in the first step. In this case, a second step (for example, corresponding to step S22 in FIG. 4) for classifying and storing the request from the user according to the category of the request (for example, corresponding to a genre, artist name, and age described later); A third step (for example, corresponding to step S31 in FIG. 5) for extracting a request from the requests stored in the second step, and a request (for example, a distribution list described later) for the request extracted in the third step. 4) (e.g., corresponding to step S31 of FIG. 5), and the restriction condition is a user. The number of requests stored in the same category as the request in the second step is less than a predetermined upper limit (for example, equivalent to “3” in the first embodiment). Has proposed.

  According to the present invention, in the first step, it is determined whether or not a predetermined restriction condition is satisfied. In the second step, when it is determined that the restriction condition is satisfied in the first step, a request from the user is issued. Then, we decided to classify and store them according to the category of the request. In the third step, the request is extracted from the requests stored in the second step, and in the fourth step, the request extracted in the third step is added to the list. Furthermore, as a limiting condition, it is adopted that the number of requests having the same category as the request from the user stored in the second step is less than a predetermined upper limit value. For this reason, the number of requests received from the user can be limited for each category of request. Therefore, it can suppress that many requests of the same category are reflected in the list. Therefore, by determining the distribution contents based on the list, it is possible to reflect various categories of requests in the distribution contents, and to suppress the distribution contents from being biased.

  (9) The present invention has determined that a first step (for example, corresponding to step S21 in FIG. 4) for determining whether or not a predetermined restriction condition is satisfied, and that the restriction condition is satisfied in the first step. In this case, a second step (for example, corresponding to step S22 in FIG. 4) for classifying and storing the request from the user according to the category of the request (for example, corresponding to a genre, artist name, and age described later); A third step (for example, corresponding to step S31 in FIG. 5) for extracting a request from the requests stored in the second step, and a request (for example, a distribution list described later) for the request extracted in the third step. 4) (e.g., equivalent to step S31 in FIG. 5) to be added to The restriction condition refers to the number of requests having the same category as the request from the user stored in the second step being a predetermined upper limit value (for example, “3” in the first embodiment). Proposal of a program characterized by being less than

  According to the present invention, by causing the computer to execute the program, it is determined in the first step whether or not a predetermined restriction condition is satisfied, and in the second step, it is determined that the restriction condition is satisfied in the first step. In this case, the request from the user is classified and stored according to the request category. In the third step, the request is extracted from the requests stored in the second step, and in the fourth step, the request extracted in the third step is added to the list. Furthermore, as a limiting condition, it is adopted that the number of requests having the same category as the request from the user stored in the second step is less than a predetermined upper limit value. For this reason, the number of requests received from the user can be limited for each category of request. Therefore, it can suppress that many requests of the same category are reflected in the list. Therefore, by determining the distribution contents based on the list, it is possible to reflect various categories of requests in the distribution contents, and to suppress the distribution contents from being biased.

  By determining the distribution contents based on the list, it is possible to reflect various categories of requests in the distribution contents, and to suppress the distribution contents from being biased.

It is a block diagram which shows the structure of the content delivery system which concerns on 1st Embodiment of this invention. It is a block diagram which shows the structure of the request reception apparatus with which the said content delivery system is provided. It is a flowchart of the music distribution process which the said request reception apparatus performs. It is a flowchart of the request reception process which the said request reception apparatus performs. It is a flowchart of the distribution list production | generation process which the said request reception apparatus performs. It is a figure which shows the request reception screen displayed on the user terminal with which the said content delivery system is provided. It is a figure which shows the request reception screen displayed on the user terminal with which the content delivery system which concerns on 2nd Embodiment of this invention is provided. It is a flowchart of the music distribution process which the request reception apparatus with which the said content distribution system is provided performs. It is a flowchart of the support command reception process which the said request reception apparatus performs. It is a flowchart of the opposite command reception process which the said request reception apparatus performs. It is a flowchart of the request reception process which the said request reception apparatus performs.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. Note that the constituent elements in the following embodiments can be appropriately replaced with existing constituent elements, and various variations including combinations with other existing constituent elements are possible. Accordingly, the description of the following embodiments does not limit the contents of the invention described in the claims.

<First Embodiment>
[Configuration of Content Distribution System AA]
FIG. 1 is a block diagram showing a configuration of a content distribution system AA according to the first embodiment of the present invention. The content distribution system AA includes a request reception device 1 that distributes music by Internet radio service and user terminals T1 to Tn owned by users U1 to Un (n is an integer satisfying n ≧ 1). . Each of the user terminals T1 to Tn and the request reception device 1 are provided so as to be able to communicate with each other via, for example, an Internet line or a telephone line.

[Configuration of Request Accepting Device 1]
FIG. 2 is a block diagram illustrating a configuration of the request receiving apparatus 1. The request receiving apparatus 1 includes a communication unit 11, a control unit 12, a storage unit 13, a distribution list generation unit 14, and a content storage unit 15.

  The communication unit 11 receives a request transmitted from each of the user terminals T1 to Tn, or distributes music to each of the user terminals T1 to Tn.

  The content storage unit 15 stores a music database in which a large number of music is accumulated.

  The storage unit 13 includes category-specific storage areas 131 to 13m (m is an integer satisfying m ≧ 1). Each of these category-specific storage areas 131 to 13m is provided for each category of music, and stores the requests received from the user terminals T1 to Tn, classified according to the category. In each of the category-specific storage areas 131 to 13m, an upper limit value of the number of requests that can be stored is determined in advance. In this embodiment, “3” is uniformly set as the upper limit value. To do. In addition, the category-specific storage area 13X (X is an arbitrary integer satisfying 1 ≦ X ≦ m) stores requests for music pieces classified into the category X. Here, the category is, for example, a genre such as rock, classic, or pop, an artist name, an age, etc. One song may be classified into only one category, or one song may include a plurality of songs. It may be classified into categories.

  The distribution list generation unit 14 generates a distribution list, which is a list of songs to be distributed to the user terminals T1 to Tn, and requests stored in the category-specific storage areas 131 to 13m and predetermined extraction conditions. And generated in the storage unit 13. In the distribution list, names of music to be distributed to the user terminals T1 to Tn among the music stored in the content storage unit 15 are described according to the order of the music to be distributed to the user terminals T1 to Tn.

  As the above extraction condition, for example, majority decision or first-come-first-served basis can be adopted. When the majority vote is adopted, the requests stored in the category-specific storage areas 131 to 13m are totaled for each predetermined period. And the request of the music with the largest number of requests is extracted for each category, and the name of the music corresponding to the extracted request is added to the distribution list.

  On the other hand, when the first-come-first-served basis is adopted, the request with the earliest timing received by the communication unit 11 is extracted for each category for each predetermined period, and the name of the music corresponding to the extracted request is extracted. To the distribution list.

  In the present embodiment, it is assumed that the priority order is adopted as the extraction condition. When the priority order is adopted, the request for the highest priority music is extracted by “1” for each category for each predetermined period, and the name of the music corresponding to the extracted request is included in the distribution list. to add. As the priority, for example, the priority can be set higher as the published date of the music becomes new, or the priority can be set higher as the number of times the music is distributed.

  In addition, the distribution list generation unit 14 deletes the request for the music whose name is added to the distribution list from each of the category-specific storage areas 131 to 13m, and when the distribution of the music is started, the music whose distribution is started Remove all names from the distribution list.

  When the communication unit 11 receives a request for a music piece classified into the category X from the user terminal Tk (k is an arbitrary integer satisfying 1 ≦ k ≦ n), the control unit 12 is provided corresponding to the category X. The number of requests stored in the category-specific storage area 13X is confirmed. When the number of stored requests is less than “3”, the requests for music pieces classified into the category X received from the user terminal Tk are stored in the category-specific storage area 13X. On the other hand, when the number of stored requests is “3”, the request for the music classified into the category X received from the user terminal Tk is discarded.

  Further, the control unit 12 reads content from the content storage unit 15 based on the distribution list generated by the distribution list generation unit 14 and distributes the content to each of the user terminals T1 to Tn via the communication unit 11.

  Moreover, the control part 12 transmits the data for displaying the request reception screen mentioned later using FIG. 6 to each of user terminal T1-Tn via the communication part 11. FIG.

  The request receiving apparatus 1 having the above configuration performs music distribution processing, which will be described later with reference to FIG. 3, and distributes music based on the distribution list. Moreover, the request reception process mentioned later using FIG. 4 is performed, and the request transmitted from the user terminal is received. Also, a distribution list generation process, which will be described later with reference to FIG. 5, is executed to generate a distribution list.

[Music distribution processing]
FIG. 3 is a flowchart of the music distribution process. The music distribution process is always executed by the request receiving apparatus 1 during the period in which the request receiving apparatus 1 provides the Internet radio service.

  First, in step S <b> 11, the control unit 12 starts distributing the music having the name at the top of the distribution list. Specifically, the distribution list stored in the storage unit 13 is read, and the music having the name at the top of the distribution list is read from the content storage unit 15. Then, transmission of the read music data is started to all user terminals that are using the Internet radio service, and streaming distribution of the music is started. According to this, the same music is reproduced at substantially the same timing in all user terminals that are using the Internet radio service.

  Next, in step S12, the control unit 12 deletes all the names of music pieces that have been distributed in step S11 from the distribution list.

  Next, in step S13, the control unit 12 determines whether or not the music being distributed has ended, that is, whether or not the music that has been distributed in step S11 has been distributed to the end. If it has been distributed to the end, the process proceeds to step S11. If it has not been distributed to the end, the process of step S13 is repeated.

[Request reception process]
FIG. 4 is a flowchart of the request reception process. The request reception process is executed by the request reception apparatus 1 every time a request is received from the user terminal during the period in which the request reception apparatus 1 provides the Internet radio service. In FIG. 4, music pieces classified into the category P (P is an arbitrary integer satisfying 1 ≦ P ≦ m) transmitted from the user terminal Ta (a is an arbitrary integer satisfying 1 ≦ a ≦ n). The request will be described on the assumption that the communication unit 11 has received the request.

  First, in step S21, the control unit 12 determines whether or not there is a free space in the category-specific storage area 13P provided corresponding to the category P. Specifically, it is determined whether or not the number of requests stored in the category-specific storage area 13P is less than “3”. If it is less than “3”, the process proceeds to step S22. If it is “3”, the request reception process ends. According to this, in the case where three requests are stored in the category-specific storage area 13P, the request for the music classified into the category P received from the user terminal Ta is discarded without being reflected in the distribution list. The Rukoto.

  Next, in step S <b> 22, the control unit 12 stores the request for the music classified into the category P received from the user terminal Ta in the category storage area 13 </ b> P.

[Delivery list generation processing]
FIG. 5 is a flowchart of distribution list generation processing. The distribution list generation process is executed by the request reception apparatus 1 every predetermined period during the period in which the request reception apparatus 1 provides the Internet radio service.

  First, in step S31, the distribution list generation unit 14 generates a distribution list based on the requests stored in the category-specific storage areas 131 to 13m and the above-described predetermined extraction conditions, and stores them. Store in the unit 13.

  Next, in step S32, the distribution list generation unit 14 deletes the request for the music whose name is added to the distribution list in step S31 from each of the category-specific storage areas 131 to 13m.

  FIG. 6 is a diagram showing a request reception screen displayed on all user terminals that are using the Internet radio service.

  The image IMG1 shows the artist name and song name of the song being streamed. The image IMG2 shows an icon operated by the user when he wants to listen to the Internet radio. When the user operates the icon of the image IMG2, streaming distribution of music to the user terminal of the user is started, and reproduction of the Internet radio on the user terminal is started.

  The image IMG3 is an icon operated by the user when quitting listening to the Internet radio. When the user operates the icon of the image IMG3, streaming distribution of music to the user terminal of the user is stopped, and reproduction of the Internet radio on the user terminal is stopped.

  The image IMG4 is an icon operated by the user when adjusting the volume when listening to Internet radio. When the user operates the icon of the image IMG4, the volume of the Internet radio being played changes in accordance with the operation at the user terminal of the user.

  The image IMG5 indicates the song name and artist name of the music described in the distribution list.

  Images IMG6 and IMG7 are images operated by the user when making a request. When making a request, the user first operates the image IMG 6 to select an artist name to be requested. Then, the song name of the song of the selected artist is displayed on the image IMG7. Next, the user operates the image IMG7 to select the song name of the song to be requested. According to this, the music to be requested is determined, and the request for this music is transmitted to the request receiving apparatus 1.

  According to the request receiving apparatus 1 described above, when the user Ua tries to request a music piece classified into the category P, if three requests are stored in the category-specific storage area 13P, the user Ua requests Can not do. In other words, the number of requests received from the user can be limited for each category of the requested music, and as a result, the number of requests reflected in the distribution list can be limited for each category. it can. For this reason, it can suppress that the request | requirement of the music classified into the same category, for example, the request | requirement of the music of the same artist, and the request | requirement of the music of the same genre, are reflected in a delivery list many. Since the request reception apparatus 1 determines the music to be distributed based on the distribution list, it can reflect the request for the music classified into various categories in the distribution contents, and can suppress the occurrence of bias in the distribution contents.

  Further, according to the request receiving apparatus 1, when generating a distribution list, a request for a song with the highest priority is extracted one by one for each category. For this reason, a request with a high priority can be reflected with respect to a delivery list.

<Second Embodiment>
[Configuration of Request Accepting Device 1A]
The request receiving apparatus 1A according to the second embodiment of the present invention will be described below. The request receiving apparatus 1A is different from the request receiving apparatus 1 according to the first embodiment of the present invention illustrated in FIG. 2 in that a control unit 12A is provided instead of the control unit 12. In the request receiving apparatus 1A, the same components as those in the request receiving apparatus 1 are denoted by the same reference numerals and description thereof is omitted.

  The control unit 12A differs from the control unit 12 in the operation when the communication unit 11 receives a request from the user terminal Tk and the operation during music distribution.

  More specifically, the operation when the communication unit 11 receives a request from the user terminal Tk is different. Specifically, when the control unit 12 receives a request for music pieces classified into the category X from the user terminal Tk, the control unit 12 changes to the category X. It confirms how many requests are stored in the corresponding category-specific storage area 13X. On the other hand, when the control unit 12A receives a request for music pieces classified into the category X from the user terminal Tk, how many requests are stored in the category-specific storage area 13k provided corresponding to the category X. And whether the received requested music is different from the music being distributed.

  When the number of stored requests is less than “3” and a request for a music different from the music being distributed is received, a request for the music classified into the category X received from the user terminal Tk is received. Are stored in the category-specific storage area 13X.

  On the other hand, if the number of stored requests is “3” or if a request for a song being distributed is received, the three requests stored in the category-specific storage area 13X and the user terminal Tk Among the requests for music pieces classified into category X received from, three high priority items are stored in the category-specific storage area 13X. As the priority, for example, the priority is set higher as the published date of the music becomes new, or the priority is set higher as the number of times the music is distributed, as in the above-described extraction condition. be able to.

  On the other hand, when the operation during distribution of the music is different, specifically, the control unit 12A receives the support command and the opposite command from the user terminal during the distribution of the music, and the number of times each command is received. The music being distributed is changed accordingly.

  The support command is a command transmitted from the user terminal when the user wants to listen to the music being distributed to the end by performing a first operation described later on the user terminal. On the other hand, the opposite command is a command transmitted from the user terminal when the user does not want to listen to the music being distributed, and the user performs a second operation described later on the user terminal.

  When the opposite command is received “50” times during the distribution of the music M1, the distribution of the music M1 is forcibly terminated, and the distribution of the music having the name at the top of the distribution list, that is, the next music is started. On the other hand, if the approval command is received “50” times during distribution of the music M1, the number of times the opposite command is received is invalidated, and the music M1 is distributed to the end of the music M1.

  FIG. 7 is a diagram showing a request reception screen displayed on all user terminals that are using the Internet radio service. The request reception screen shown in FIG. 7 is different from the request reception screen shown in FIG. 6 in that images IMG8, IMG9, IMG10, and IMG11 are shown.

  The image IMG8 shows an icon operated by the user when it is not desired to listen to the music being distributed. When the user operates the icon of the image IMG8, the above-described second operation is performed. The image IMG9 indicates the number of users who have operated the icon of the image IMG8.

  The image IMG10 shows an icon operated by the user when it is desired to listen to the music being distributed to the end. When the user operates the icon of the image IMG10, the first operation described above is performed. The image IMG11 indicates the number of users who have operated the icon of the image IMG10.

  1 A of request reception apparatuses provided with the above structure perform the music distribution process mentioned later using FIG. 8, and distribute a music based on a distribution list. Further, the support command receiving process described later using FIG. 9 is executed to count the number of times the support command is received, and the opposite command receiving process described later using FIG. 10 is executed to receive the opposite command. Count the number of times. Moreover, the request reception process mentioned later using FIG. 11 is performed, and the request transmitted from the user terminal is received. Further, the distribution list generation process described above with reference to FIG. 5 is executed to generate a distribution list.

[Music distribution processing]
FIG. 8 is a flowchart of the music distribution process. The music distribution process is always executed by the request receiving apparatus 1A during the period in which the request receiving apparatus 1A provides the Internet radio service.

  First, in step S41, as in step S11 of FIG. 3, the control unit 12A starts distributing the music having the name at the top of the distribution list.

  Next, in step S42, as in step S12 of FIG. 3, the control unit 12A deletes all names of the music that has been distributed in step S41 from the distribution list.

  Next, in step S43, the control unit 12A determines whether or not the value of the support counter (see FIG. 9 described later) is “50” or more. If it is “50” or more, the process proceeds to step S45, and if it is less than “50”, the process proceeds to step S44. According to this, when the value of the support counter is “50” or more, the process of step S44 for confirming the value of the counter counter (see FIG. 10 described later) is not performed, and the counter counter value is invalidated. Will be.

  Next, in step S44, the control unit 12A determines whether or not the value of the counter counter is “50” or more. If it is “50” or more, the process proceeds to step S46, and if it is less than “50”, the process proceeds to step S45. According to this, when the value of the counter counter is “50” or more, the process of step S46 for clearing the support counter and counter counter is performed regardless of whether or not the music is being distributed. Then, the process of step S41 for starting distribution of the next music is performed.

  Next, in step S45, as in step S13 of FIG. 3, the control unit 12A determines whether or not the music being distributed has ended, that is, whether or not the music that has been distributed in step S41 has been distributed to the end. To do. If it has been distributed to the end, the process proceeds to step S46, and if it has not been distributed to the end, the process proceeds to step S43.

  Next, in step S46, the control unit 12A clears the support counter and the counter counter. According to this, the value of the support counter and the value of the counter counter are “0”.

[Supporting command reception process]
FIG. 9 is a flowchart of the support command reception process. The support command reception process is executed by the request reception device 1A every time a support command is received from the user terminal during the period in which the request reception device 1A provides the Internet radio service.

  In step S51, the control unit 12A adds “1” to the support counter. The support counter is provided in the storage unit 13 in order to count the number of times the support command is received from the user terminal.

[Reverse command reception processing]
FIG. 10 is a flowchart of the opposite command reception process. The counter command receiving process is executed by the request receiving apparatus 1A every time a counter command is received from the user terminal during the period in which the request receiving apparatus 1A provides the Internet radio service.

  In step S61, the control unit 12A adds “1” to the counter counter. The counter counter is provided in the storage unit 13 in order to count the number of times the counter command is received from the user terminal.

[Request reception process]
FIG. 11 is a flowchart of the request reception process. The request reception process is executed by the request reception apparatus 1A every time a request is received from the user terminal during the period in which the request reception apparatus 1A provides the Internet radio service. In FIG. 11, music pieces classified into the category Q (Q is an arbitrary integer satisfying 1 ≦ Q ≦ m) transmitted from the user terminal Tb (b is an arbitrary integer satisfying 1 ≦ b ≦ n). The request will be described on the assumption that the communication unit 11 has received the request.

  First, in step S71, as in step S21 of FIG. 4, the control unit 12A determines whether or not there is an empty space in the category-specific storage area 13Q provided corresponding to the category Q. If there is a vacancy, the process proceeds to step S72. If there is no vacancy, the process proceeds to step S74.

  Next, in step S72, the control unit 12A determines whether or not the requested music received from the user terminal Tb is different from the music being distributed. If they are different, the process proceeds to step S73. If they are the same, the request reception process ends. According to this, when the request for the music being distributed is received, the request for the music classified into the category Q received from the user terminal Tb is discarded without being reflected in the distribution list.

  Next, in step S73, similarly to step S22 of FIG. 4, the control unit 12A stores the request for the music classified into the category Q received from the user terminal Tb in the category-specific storage area 13Q.

  In step S74, the control unit 12A selects three high priority requests from among the three requests stored in the category-specific storage area 13Q and the requests for music pieces classified into the category Q received from the user terminal Tb. And stored in the category-specific storage area 13Q. As the priority, for example, the priority is set higher as the published date of the music becomes new, or the priority is set higher as the number of times the music is distributed, as in the above-described extraction condition. be able to.

  According to the request receiving apparatus 1A described above, when the user Ub tries to request a music piece classified into the category Q, when three requests are stored in the category-specific storage area 13Q, these three requests are stored. Then, three of the requests that the user Ub tries to request are stored in the category-specific storage area 13Q. That is, the number of requests reflected on the distribution list can be limited for each category. For this reason, it can suppress that the request | requirement of the music classified into the same category, for example, the request | requirement of the music of the same artist, and the request | requirement of the music of the same genre, are reflected in a delivery list many. Since the request accepting apparatus 1A determines the music to be distributed based on the distribution list, the request for the music classified into various categories can be reflected in the distribution content, and the distribution content can be prevented from being biased.

  Further, according to the request receiving apparatus 1A, as described above, when the user Ub tries to request a music piece classified into the category Q, when three requests are stored in the category-specific storage area 13Q, Of these three requests and the request that the user Ub attempted to request, the three priority items are stored in the category-specific storage area 13Q. For this reason, the request | requirement of a high priority music can be reflected for every category with respect to a delivery list.

  Further, according to the request accepting apparatus 1A, when a request for a music being distributed is received, the request is discarded and not accepted. For this reason, it can suppress that the same music is repeatedly delivered in a short time.

  Further, according to the request accepting apparatus 1A, when the number of times the opposite command is received from the user terminal during the distribution of the music reaches 50 times, the distribution of the music is performed regardless of whether the music is being distributed. End and start distributing the next song. The opposite command is a command transmitted from the user terminal when the user performs a predetermined operation on the user terminal when the user does not want to listen to the music being distributed. For this reason, when there are 50 or more users who do not want to listen to the music being distributed, the distribution of this music is terminated and the distribution of the next music is started. it can.

  Also, according to the request accepting apparatus 1A, when the number of times the support command is received from the user terminal during distribution of the music reaches 50 times, regardless of whether the number of times the opposite command is received reaches 50 times, This music is distributed to the end of this music. The support command is a command transmitted from the user terminal when the user performs a predetermined operation on the user terminal when the user wants to listen to the music being distributed to the end. For this reason, when there are 50 or more users who want to listen to the music being delivered to the end, the music is delivered to the end, so that the music that matches the user's preference can be delivered.

  The processing of the request reception device 1, 1A of the present invention is stored in a computer-readable recording medium, and is read by the request reception device 1, 1A recorded on the recording medium and executed, thereby realizing the present invention. it can.

  Further, the above-described program may be transmitted from the request receiving device 1, 1A storing the program in a storage device or the like to another computer system via a transmission medium or by a transmission wave in the transmission medium. Here, the “transmission medium” for transmitting the program refers to a medium having a function of transmitting information, such as a network (communication network) such as the Internet or a communication line (communication line) such as a telephone line.

  Further, the above-described program may be for realizing a part of the above-described function. Furthermore, what can implement | achieve the above-mentioned function in combination with the program already recorded on the request reception apparatuses 1 and 1A, what is called a difference file (difference program) may be sufficient.

  As described above, the embodiments of the present invention have been described in detail with reference to the drawings. However, the specific configuration is not limited to the above-described embodiments, and includes a design within a scope not departing from the gist of the present invention. It is.

  For example, in each of the above-described embodiments, music is used as the content to be distributed. However, the present invention is not limited to this.

  Further, for example, in each of the above-described embodiments, the music database is stored in the content storage unit 15 provided in the request reception device, but is not limited thereto, and is provided separately from the request reception device. It may be stored in the storage unit.

  Further, for example, in each of the above-described embodiments, the request for the music whose name is added to the distribution list is deleted from each of the category-specific storage areas 131 to 13m. However, the present invention is not limited to this. For example, every time a predetermined time elapses, all requests stored in each of the category-specific storage areas 131 to 13m may be deleted. Further, for example, after generating a distribution list based on the requests stored in each of the category-specific storage areas 131 to 13m and a predetermined extraction condition, the distribution list is stored in each of the category-specific storage areas 131 to 13m. All requests that have been made may be deleted.

  Further, for example, in each of the above-described embodiments, in the request reception device, the distribution list is generated and the music is distributed. However, the present invention is not limited thereto, and the distribution list is generated and the music is distributed. It is good also as performing by a separate apparatus.

  Further, for example, in the above-described first embodiment, the upper limit value of the number of requests that can be stored in each of the category-specific storage areas 131 to 13m is uniformly set to “3”. It may be set individually for each of the storage areas 131 to 13m. Alternatively, the number may be set according to the total number of user terminals that are using the Internet radio service provided by the request reception apparatus 1 or the total number of user terminals that have transmitted requests to the request reception apparatus 1.

  Further, for example, in the second embodiment described above, when the number of times the opposite command is received from the user terminal during distribution of the music reaches 50 times, the distribution of the music is performed regardless of whether the music is being distributed. Although the distribution is ended and the distribution of the next music is started, the present invention is not limited to this. For example, when the ratio of the number of times the opposite command is received with respect to the total number of user terminals using the Internet radio service provided by the request receiving apparatus 1A reaches a predetermined ratio (for example, 50%), the distribution is performed. It is also possible to end the distribution of the current music and start the distribution of the next music.

  In addition, for example, in the above-described second embodiment, when the number of times that the support command is received from the user terminal during distribution of the music reaches 50 times, whether or not the number of times the opposite command has been received has reached 50 times. However, the distribution of this music is performed until the end of this music, but this is not restrictive. For example, when the ratio of the number of times the support command is received to the total number of user terminals that are using the Internet radio service provided by the request receiving apparatus 1A reaches a predetermined ratio (for example, 10%), it is contrary to Regardless of whether or not the number of commands received has reached 50 times, the music may be distributed to the end of the music.

1, 1A; request accepting device 11; communication unit 12, 12A; control unit 13; storage unit 131 to 13m; storage area by category 14; distribution list generation unit 15; content storage unit AA; content distribution system T1 to Tn; Terminal

Claims (9)

Control means for determining whether or not a predetermined restriction condition is satisfied;
Storage means for classifying and storing requests from users according to the category of the request when the control means determines that the restriction condition is satisfied;
Request extracting means for extracting a request from requests stored in the storage means;
A list generation means for adding the request extracted by the request extraction means to a list,
The restriction condition is that the number of requests having the same category as the request from the user stored in the storage means is less than a predetermined upper limit value.   The request extracting unit extracts a predetermined number of requests for each category from the requests stored in the storage unit in order from the earlier received timing. The request receiving device described.   2. The request extraction unit extracts a predetermined number of requests for each category from the requests stored in the storage unit based on a predetermined priority. The request receiving device described in 1.   4. The request reception apparatus according to claim 2, wherein the request extraction unit sets the predetermined number according to the number of requests stored in the storage unit. Content distribution means for distributing content based on requests included in the list;
The restriction condition is
The number of requests in the same category as the request from the user is stored in the storage means is less than a predetermined upper limit value,
And,
5. The request reception apparatus according to claim 1, wherein the request reception apparatus is a request different from the request for the contents being distributed by the content distribution means. Content distribution means for distributing content to a plurality of user terminals based on requests included in the list;
Content distribution stopping means for ending distribution of content being distributed by the content distribution means if the number of times the first signal is received from the user terminal is equal to or greater than a first threshold value. Item 6. The request reception device according to any one of Items 1 to 5.   7. The content distribution continuation unit for prohibiting the end of content distribution by the content distribution stop unit when the number of times the second signal is received from the user terminal is equal to or greater than a second threshold. The request receiving device described. A first step of determining whether or not a predetermined restriction condition is satisfied;
A second step of classifying and storing a request from a user according to the category of the request when it is determined that the restriction condition is satisfied in the first step;
A third step of extracting a request from the requests stored in the second step;
A fourth step of adding the request extracted in the third step to a list,
The restriction condition is a request reception method characterized in that the number of requests in the same category as the request from the user is stored in the second step is less than a predetermined upper limit value. A first step of determining whether or not a predetermined restriction condition is satisfied;
A second step of classifying and storing a request from a user according to the category of the request when it is determined that the restriction condition is satisfied in the first step;
A third step of extracting a request from the requests stored in the second step;
A program for causing a computer to execute a fourth step of adding the request extracted in the third step to a list,
The restriction condition is a program characterized in that the number of requests of the same category as the request from the user is stored in the second step is less than a predetermined upper limit value.