JP4808368B2 - Multicast content distribution system and distribution control method - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present inventionMulticast content distribution system and multicast content distribution control methodAbout.
[0002]
The “distribution session condition” in this case is a session condition at the time of content distribution, and corresponds to, for example, information items such as a session expiration date, a distribution interval, and the number of distributions. The “reception client condition” is an information item related to the user condition of the client terminal to receive, for example, an information item such as gender, age, hobby, occupation. The “content information” is information relating to the content to be distributed, and includes information items such as designation of various data files constituting the content, creation date, content type, content name, and content outline.
The “multicast distribution condition” is a condition for multicast distribution of content, and corresponds to, for example, a combination of a distribution session condition, a reception client condition, and content information. “Session information” is information related to a session at the time of distribution required for a client terminal to receive content distribution, and corresponds to information such as a multicast address and a port number.
[0003]
[Prior art]
The multicast communication protocol is a protocol for simultaneously distributing data packets to a large number of users, and can reduce the network bandwidth and the load on the distribution server. In broadcast-type content distribution services, for which demand is expected to increase in the future, efficient use of communication bandwidth and reduction of server load are important because distribution to a large number of users at the same time is important. A multicast communication protocol is suitable (see Non-Patent Documents 1 to 3 below).
[0004]
In multicast distribution on the Internet, a content provider registers content and content distribution information (session information) in a distribution server, and a multicast receiving client obtains session information from the distribution server and selects a desired multicast group. You can receive the content you want. In addition to the content name, the session information includes information necessary for communication such as a multicast address, a port number, a session expiration date, and a delivery interval (refer to Non-Patent Documents 4 and 5 below regarding session notification). ). As a format for expressing session information of multicast communication, for example, there is Session Description Protocol (Session Description Protocol) standardized by IETF (Internet Engineering Task Force), and Session Announcement Protocol (Session Announcement Protocol) ) Can be used to notify the client. The Internet Assigned Number Authority (IAN) assigns a multicast address to deliver the session announcement protocol, and clients are notified using the session announcement protocol by joining this multicast group. , Information described using the session description protocol can be received. In addition, the client can receive information described using the session description protocol notified by the WWW server or net news using the session announcement protocol.
[0005]
FIG. 1 is a diagram illustrating a configuration example of a content distribution system 90 when content distribution is performed to a client terminal such as a personal computer or a mobile phone terminal. The content distribution system 90 includes a content provider 91 that is a content provider, a distribution server 92 that performs content distribution, and a client terminal 93 that receives the content. The distribution server 92 and the client terminal 93 are multicast communication such as the Internet. Connected via a network that supports. In the figure, when content is distributed to the client terminal 93 by multicast, first, the content provider 91 registers the content to be distributed to the distribution server 92, and the session information as the content distribution information is, for example, a session description. Describe in the protocol and register with the distribution server 92. The client terminal 93 acquires the session information from the distribution server 92 and the like, and selects and participates in the multicast group that is the distribution destination of the content desired to be received based on the acquired session information. Receive delivery.
[Non-Patent Document 1]
"Introduction to IP Multicast" (first edition, Kyoritsu Publishing Co., Ltd.), written by Thomas Maufer, translated by Hiroyuki Enomoto, November 2001
[Non-Patent Document 2]
“Mastering TCP / IP Multicast Edition” (1st edition, 2nd edition), Dave Kosiur, translated by Yukio Hamada, November 2000
[Non-Patent Document 3]
"IP Multicast Network Development Guide Vol.1" (first edition), by Beau Williamson, translated by Comsus, directed by Cisco Systems, July 2001
[Non-Patent Document 4]
IETF RFC2543 "Session Initiation Protocol" M.Handley, et al., 1999
[Non-Patent Document 5]
IETF RFC2327 "Session Description Protocol" M.Handley, et al., 1998
[0006]
[Problems to be solved by the invention]
As described above, in order to perform multicast distribution, a content provider registers content and content distribution information (session information) in a distribution server. This session information is for notifying the client of information necessary for receiving the content distribution, and accordingly, the distribution conditions for the content provider to which content is distributed to which client and at what timing. It cannot be set.
[0007]
On the other hand, in an existing television broadcast, there are a broadcasting station in charge of broadcasting and determining a broadcasting schedule and a target audience, and a production company that produces a broadcast program. Therefore, in a broadcast-type content distribution system that assumes an unspecified number of distribution destinations, there are a part for performing distribution, a part for determining a distribution schedule, a part for determining a distribution target user, and a part for holding information about content and content. The form which exists individually can be considered. However, even in this content distribution system, a mechanism for setting a distribution condition for a content provider to distribute content to which viewer and at what timing has not been established.
[0008]
Further, in the content distribution system 90 of FIG. 1 described above, when a change occurs in the content distribution schedule and the content to be distributed, a series of processes such as generation and reconstruction of session information related to the change is provided. There was an inconvenience that a person etc. had to do each time. For this reason, it has been awaited to provide an apparatus for centrally managing session information in a content distribution system.
[0009]
The present invention has been made in order to solve the above-described problems, and enables the content provider to specify distribution conditions such as when, to whom, and what content to be distributed, and the content based on the distribution conditions can be specified. Dynamic switching can be realized without increasing the processing burden on the content provider.Multicast content distribution system and distribution control methodThe purpose is to provide.
[0010]
To achieve the above object, according to the present invention.Multicast content distribution systemIsA multicast content distribution system in which a server and a content distribution apparatus are connected by a network. The serverIn accordance with a condition setting request input from an external content provider, a distribution session condition regarding a session condition at the time of content distribution, a receiving client condition regarding a user condition of a client terminal that receives the content, and content information regarding the content to be distributedContent information including any information items such as designation of various data files constituting the content, creation date, content type, content name, and content overviewA multicast distribution condition generating means for generating a multicast distribution condition relating to a condition for multicast distribution of the content based on the content, and a distribution time required for the client terminal to receive the content distribution based on the generated multicast distribution condition Session information generating means for generating session information related to the session, the generated session information, multicast distribution conditions, and content specified by the multicast distribution conditionsentityOutput means for outputting data to the content distribution device;. The content distribution apparatus manages a content management unit that manages content entity data output by the output unit of the server, manages session information and multicast distribution conditions output by the output unit of the server, and stores presence information of the user of the client terminal. When received from the client terminal, the received presence information is matched with the multicast distribution condition, and when the multicast distribution condition is met, the session information regarding the content specified in the multicast distribution condition is notified to the client terminal. A distribution condition processing unit that performs the multicast distribution of the content entity data managed by the content management unit based on the multicast distribution condition.
[0011]
Further, according to the present inventionDelivery control methodThe serverContent distribution system in which the content distribution apparatus and the content distribution apparatus are connected by a networkExecuted inMulticast content delivery control methodBecauseServerThe multicast distribution condition generation means is distributed according to the condition setting request input from the external content provider, the distribution session condition regarding the session condition at the time of content distribution, the receiving client condition regarding the user condition of the client terminal that receives the content, and the distribution Content information about contentContent information including any information items such as designation of various data files constituting the content, creation date, content type, content name, and content overviewA multicast distribution condition generating step for generating a multicast distribution condition related to a condition for multicast distribution of content,ServerA session information generating step for generating session information related to a session at the time of distribution required for the client terminal to receive content distribution based on the generated multicast distribution condition;ServerOutput means generates generated session information, multicast distribution conditions, and content specified by the multicast distribution conditionsentityAn output process for outputting data to a content distribution device;A content management process in which the content management unit of the content distribution device manages the content entity data output by the output unit of the server, and the distribution condition processing unit of the content distribution device outputs the session information output by the output unit of the server, and When multicast distribution conditions are managed and presence information of the user of the client terminal is received from the client terminal, the received presence information is matched with the multicast distribution conditions, and if the multicast distribution conditions are met, the multicast distribution conditions The distribution condition processing step of notifying the client terminal of session information related to the content specified in the item, and the distribution processing unit of the content distribution apparatus uses the content entity data managed by the content management unit as the multicast distribution condition And a delivery processing step of performing multicast delivery Zui.
[0013]
  According to the above invention, the multicast distribution condition generating means isContent providerIn accordance with the condition setting request input from, multicast distribution conditions are generated based on the distribution session conditions, the reception client conditions, and the content information. Therefore,Provided contentOrBy inputting a condition setting request to the server from the distribution session condition, the receiving client condition and the content information according to the request, the multicast distribution condition (that is,Content provider(Multicast distribution condition according to the condition setting request from) is generated. Then, the session information generation unit generates session information based on the generated multicast distribution condition, and the output unit generates the generated session information, the multicast distribution condition, and the content data specified by the multicast distribution condition. Output to the content distribution device.
[0014]
  Thus, according to the present invention,Provided contentOrBy inputting a condition setting request to the server from the distribution session condition, the receiving client condition and the content information according to the request, the multicast distribution condition (that is,Content providerMulticast distribution conditions according to the condition setting request fromContent providerAccordingly, it is possible to make a condition setting request for distribution conditions such as when, to whom, and what content is distributed. In addition, since a multicast distribution condition and session information is generated and output to the content distribution apparatus by a “server” separate from the content distribution apparatus and the content provider, the dynamic content can be changed even when the multicast distribution condition is added or changed. Can be realized without increasing the processing burden on the content provider or the like.
[0015]
By the way, according to the present inventionMulticast content distribution systemThe following configuration is desirable.
[0016]
  That is,Content providerIt is preferable that the “condition setting request” input from is a selection request for selecting a condition for each of the distribution session condition, the receiving client condition, and the content information, or a setting request for directly setting the generated multicast distribution condition. . That is,Provided contentWhoA selection request for selecting a condition for each of the distribution session condition, the receiving client condition, and the content information can be input to the server, or a setting request for directly setting the generated multicast distribution condition can be input to the server. In addition, it is possible to realize generation of multicast distribution conditions according to these selection requests or setting requests.
[0017]
  In addition, the server according to the present invention stores and manages distribution session conditions,Content providerAdd a delivery session condition entered from, orContent providerIt is desirable to further include a distribution session condition management means for extracting a distribution session condition from the multicast distribution condition input from and adding the distribution session condition. It also stores and manages receiving client conditions,Content providerAdd the incoming client condition entered from, orContent providerIt is desirable to further include a reception client condition management means for extracting the reception client condition from the multicast distribution condition input from and adding the reception client condition. In addition, content information is stored and managed,Content providerIt is desirable to further include content information management means for adding the content information input from. In this way, the distribution session condition, the receiving client condition, and the content information areContent providerIt becomes possible to appropriately store and manage the data based on the input conditions or input information.
[0019]
DETAILED DESCRIPTION OF THE INVENTION
Hereinafter, embodiments of the present invention will be described with reference to the drawings.
[0020]
[System configuration of this embodiment]
FIG. 2 shows a configuration example of a multicast content distribution system 1 to which the present invention is applied. A multicast content distribution system 1 shown in FIG. 1 includes a content provider 10 as a content provider, a registration server 20 as a content and various condition information management device, a distribution server 30 as a content distribution device, and a content receiver. The client terminal 40 is configured. These content provider 10, registration server 20, distribution server 30, and client terminal 40 are connected by a communication network such as the Internet.
[0021]
FIG. 4 shows a configuration diagram of the registration server 20 described above. As shown in the figure, the registration server 20 includes a transmission / reception unit 21 that transmits / receives information to / from the outside, a distribution session condition management unit 22 that stores and manages distribution session conditions, and a reception client condition that stores and manages reception client conditions. Management unit 23, content information management unit 24 that stores and manages content information, multicast distribution condition management unit 25 that stores and manages multicast distribution conditions, and multicast distribution conditions, session information, and the substance of the content to be distributed are distribution servers. 30 and a distribution server registration unit 26 that uploads to 30.
[0022]
Among these, the delivery session condition management unit 22 stores information on the delivery session conditions (for example, session expiration date (start time and end time), transmission interval, delivery count) by the delivery session condition table 22A as shown in FIG. to manage. The reception client condition management unit 23 stores and manages information on reception client conditions (for example, gender, age, etc.) using a reception client condition table 23A as shown in FIG. The content information management unit 24 uses the content information table 24A as shown in FIG. 12 to obtain information on the content information (for example, the types of data files constituting the content, creation dates, keywords representing the content, and descriptions of the content). Manage memory.
[0023]
FIG. 5 shows a configuration diagram of the distribution server 30 described above. As shown in the figure, the distribution server 30 manages a multicast distribution condition and session information, a transmission / reception unit 31 that transmits / receives information to / from the outside, a content management unit 32 that manages content to be distributed, and a client terminal. When the presence information of 40 users is received, the distribution condition processing unit 33 that selects the contents to be distributed to the client terminal by matching the presence information with the distribution conditions, and executes multicast distribution based on the distribution conditions And a distribution processing unit 34.
[0024]
[Processing content of this embodiment]
Next, as a process according to the present embodiment, a series of processes from when the content provider 10 registers distribution conditions until the client terminal 40 receives content will be described. FIG. 8 shows the flow of the above series of processing.
[0025]
[P01, P02, P03 in FIG. 8]
In FIG. 8, the content provider 10 registers the distribution session condition, the reception client condition, and the content information individually in the registration server 20 at arbitrary timing as follows (arrows P01, P02, and P03).
[0026]
First, registration of distribution session conditions will be described. FIG. 13 shows an example of the flow of registration processing for distribution session conditions in the registration server 20. When the distribution session condition is registered, the registration server 20 receives a distribution session condition registration request, or multicast distribution condition information is received from the multicast distribution condition management unit 25 in the registration server 20 to the distribution session condition management unit 22. By being delivered, the distribution session condition management unit 22 starts executing the process of FIG. 13 and accepts a registration request for the distribution session condition (S01). In the case of manual registration of a user (in this case, the content provider 10), the registration server 20 prompts the user to input condition items such as an expiration date, a distribution interval, and the number of times necessary as distribution session conditions, and the user completes the input. Submit a registration request. In response to this, the registration server 20 accepts the input of the condition item (S03), and new information is added to the distribution session condition table 22A as shown in FIG. 10 held by the distribution session condition management unit 22 (S05). ). On the other hand, in the case of automatic registration by receiving multicast distribution condition information from the multicast distribution condition management unit 25, various information items are extracted from the received multicast distribution condition information (S04), and the distribution session condition table 22A ( New information is added to FIG. 10) (S05).
[0027]
Next, registration of receiving client conditions will be described. FIG. 14 shows an example of the flow of registration processing for receiving client conditions in the registration server 20. When registering the reception client condition, the registration server 20 accepts a registration request for the reception client condition, or multicast distribution condition information is received from the multicast distribution condition management unit 25 in the registration server 20 to the reception client condition management unit 23. By being passed, the processing of FIG. 14 is started by the receiving client condition management unit 23, and a request for registering the receiving client condition is accepted (S11). In the case of manual registration of the user (in this case, the content provider 10), the registration server 20 prompts the user to input the contents and values of each item of the condition that the user wants to register as the receiving client condition. Enter a registration request. In response to this, the registration server 20 accepts the input of the condition item (S13), and new information is added to the reception client condition table 23A as shown in FIG. 11 held by the reception client condition management unit 23 (S15). ). On the other hand, in the case of automatic registration by receiving multicast distribution condition information from the multicast distribution condition management unit 25, various information items are extracted from the received multicast distribution condition information (S14), and the receiving client condition table 23A ( New information is added to FIG. 11) (S15).
[0028]
Next, registration of content information will be described. FIG. 15 shows an example of the flow of content information registration processing in the registration server 20. When registering content information, the user (in this case, the content provider 10) issues a content information registration request to the registration server 20, and the content information management unit 24 of the registration server 20 starts executing the processing of FIG. 15. A content information registration request is accepted (S21). The registration server 20 prompts the user to input content information items such as designation of various data files constituting one content, creation date, content type, content name, and content outline, and the user completes the input and issues a registration request. In response to this, the registration server 20 accepts input of information items (S22), and the substance data of various data files are uploaded to the registration server 20 and are held by the content information management unit 24 as shown in FIG. New information is added to the content information table 24A (S23). Further, when the user designates and registers the multicast distribution condition information related to the distribution time and the target user as one of the content information, the multicast distribution condition information is then stored in the multicast distribution condition management unit 25 in the registration server 20. (S25).
[0029]
[P04, P05 in FIG. 8]
After registering the conditions and information in the registration server 20 as described above, the content provider 10 requests the registration server 20 to register the multicast distribution conditions (arrow P04 in FIG. 8), and the registration server 20 As described later, registration of multicast distribution conditions and generation of session information, which is content distribution information in accordance with the contents of the multicast distribution conditions, are performed (P05).
[0030]
FIG. 16 shows an example of the flow of registration processing of multicast distribution conditions in the registration server 20. When registering multicast distribution conditions, a user (in this case, the content provider 10) issues a multicast distribution condition registration request to the registration server 20, or a multicast distribution condition management unit from the content information management unit 24 in the registration server 20. When the multicast distribution condition information is delivered to 25, the multicast distribution condition management unit 25 starts executing the process of FIG. 16 and accepts a request for registration of the multicast distribution condition (S31).
[0031]
In the case of manual registration of the user, the registration server 20 prompts the user to select an appropriate one from the registered delivery session conditions, reception client conditions, and content information. Complete the selection and submit a registration request. At this time, the user may directly set the multicast distribution conditions to be generated and issue a registration request. In S33, the registration server 20 generates a multicast distribution condition that is a set of the distribution session condition, the reception client condition, and the content information, and the session information including the multicast address and the port number is generated according to the multicast distribution condition. It is generated dynamically (S42). Then, the generated multicast distribution condition and session information are transferred to the distribution server registration unit 26 in the registration server 20.
[0032]
On the other hand, in the case of automatic registration by delivery of multicast distribution condition information, the registration server 20 determines, from the received multicast distribution condition information, a part corresponding to the distribution session condition, a part corresponding to the reception client condition, and content information The part corresponding to is extracted (S34). First, it is confirmed whether or not a portion corresponding to the designated distribution session condition has already been registered (S35). If not registered, information corresponding to the distribution session condition is transferred to the distribution session condition management unit 22 for distribution. New registration of session conditions is performed (S36). Thereafter, the distribution session condition specified in the multicast distribution condition information is selected from the registered distribution session conditions (S37). Next, it is confirmed whether or not a portion corresponding to the designated reception client condition has already been registered (S38). If it is not registered, information corresponding to the reception client condition is transferred to the reception client condition management unit 23 to receive the reception client. A new condition is registered (S39). Thereafter, the receiving client condition specified in the multicast distribution condition information is selected from the registered receiving client conditions (S40). Subsequently, the content information specified in the multicast distribution condition information is selected from the registered content information (S41). As a result, a multicast distribution condition that is a set of the distribution session condition, the reception client condition, and the content information is newly created. The subsequent processes in S42 and S43 are the same as in the case of manual registration by the user described above.
[0033]
[P06 in FIG. 8]
Thereafter, the distribution server registration unit 26 of the registration server 20 sends the content substance specified in the multicast distribution condition passed from the multicast distribution condition management unit 25, the multicast distribution condition, and the generated session information to the distribution server. 30 (arrow P06 in FIG. 8).
[0034]
[Processes after P07 in FIG. 8]
FIG. 17 shows an example of processing in the distribution condition processing unit 33 of the distribution server 30 that executes multicast distribution based on the distribution conditions. The distribution condition processing unit 33 manages multicast distribution conditions and session information. When the presence information of the user of the client terminal 40 is received from the client terminal 40 (arrow P07 in FIG. 8, S51 in FIG. 17), the received presence information The information is matched with the registered multicast distribution conditions (P08 in FIG. 8 and S52 in FIG. 17). If the distribution conditions are met, the session information regarding the content specified in the multicast distribution conditions is displayed on the client terminal. 40, the client terminal 40 is instructed to switch the received content (arrow P09 in FIG. 8, S53 in FIG. 17).
[0035]
Based on the received session information, the client terminal 40 performs various processes necessary for content reception, such as making a request to join a multicast group (P10). As a result, the distribution processing unit 34 of the distribution server 30 distributes the registered content data by multicast communication according to the specified temporal condition (arrow P11).
[0036]
Through the series of processes described above, the content provider 10 can make a registration request for a distribution session condition, a reception client condition, a content information and a registration request for a multicast distribution condition to the registration server 20. In order to register the distribution conditions and generate session information according to the contents of the multicast distribution conditions, and to transmit the session information, the multicast distribution conditions, and the content entity data to the distribution server 30, the content provider 10 determines when It is possible to make a condition setting request for multicast distribution conditions such as what kind of content is distributed.
[0037]
In addition, the “registration server 20” separate from the distribution server 30 and the content provider 10 generates the multicast distribution conditions and session information and transmits them to the distribution server 30. Therefore, even when adding or changing the multicast distribution conditions, Dynamic switching can be realized without increasing the processing load on the content provider 10.
[0038]
[Other Embodiments]
The configuration of the multicast content distribution system is not limited to the configuration of FIG. 2, and the distribution server 30 has a function of a “registration server” that is a registration device for content and various condition information as shown in FIG. It may be allowed. In this case, as shown in FIG. 6, the distribution server 30 includes a distribution condition registration unit 35 in addition to the processing units 31 to 34 described with reference to FIG. 5, and inside the distribution condition registration unit 35, FIG. As shown, the distribution session condition management unit 35A, the reception client condition management unit 35B, the content information management unit 35C, and the multicast distribution condition management unit 35D similar to those in FIG. 4 can be realized.
[0039]
A processing example different from the processing of FIG. 8 will be described with reference to FIG. In FIG. 9, at the time of content information registration (arrow P01A) from the content provider 10, multicast distribution conditions such as content distribution time and target client terminal user are also specified. In this case, the registration server 20 registers the content information, and automatically extracts, generates, and registers the distribution session condition and the receiving client condition from the designated multicast distribution condition (P02A), and then multicasts. Generate delivery conditions. The processing after P05 is the same as that described in FIG. The process of P02A corresponds to the processes of S04 and S05 in FIG. 13 and the processes of S14 and S15 in FIG.
[0040]
[Description of distribution condition generation control program]
Finally, a distribution condition generation control program for causing the registration server 20 to execute the series of processes described above will be described. As shown in FIG. 18, the distribution condition generation control program 28 is stored in a program storage area 27a formed in the recording medium 27.
[0041]
The distribution condition generation control program 28 performs multicast distribution on the basis of the distribution session condition, the reception client condition, and the content information in accordance with the main module 28a that comprehensively controls the processing in the registration server 20 and the condition setting request input from the outside. A multicast distribution condition generation module 28b that generates conditions, a session information generation module 28c that generates session information based on the generated multicast distribution conditions, the generated session information, the multicast distribution conditions, and the multicast distribution conditions specified And an output module 28d for outputting the content data to the distribution server 30.
[0042]
A part or all of the distribution condition generation control program 28 may be transmitted via a transmission medium such as a communication line, received by another device, and recorded (including installation).
[0043]
【The invention's effect】
As described above, according to the present invention, by inputting a condition setting request from the outside (for example, a content provider) to the server, according to the request, the multicast distribution condition is determined from the distribution session condition, the receiving client condition, and the content information. (That is, a multicast distribution condition corresponding to a condition setting request from the outside) is generated, and a condition setting request for distribution conditions such as when, to whom, and what content is distributed can be made externally. In addition, since a multicast distribution condition and session information is generated and output to the content distribution apparatus by a “server” separate from the content distribution apparatus and the content provider, the dynamic content can be changed even when the multicast distribution condition is added or changed. Can be realized without increasing the processing burden on the content provider or the like.
[Brief description of the drawings]
FIG. 1 is a diagram illustrating a configuration example of a content distribution system using conventional multicast communication.
FIG. 2 is a diagram showing an example of a content distribution system configuration according to the embodiment of the present invention.
FIG. 3 is a diagram showing another example of the content distribution system configuration according to the embodiment of the present invention.
4 is a diagram showing a configuration example of a registration server in the content distribution system of FIG. 2. FIG.
FIG. 5 is a diagram showing a configuration example of a distribution server in the content distribution system of FIG. 2;
6 is a diagram showing a configuration example of a distribution server in the content distribution system of FIG. 3. FIG.
7 is a diagram illustrating a configuration example of a distribution condition registration unit in the distribution server of FIG. 6;
FIG. 8 is a diagram showing an example of a series of content distribution processing procedures.
FIG. 9 is a diagram showing another example of a series of content distribution processing procedures.
FIG. 10 is a diagram illustrating an example of a table for managing distribution session conditions.
FIG. 11 is a diagram illustrating an example of a table for managing reception client conditions.
FIG. 12 is a diagram illustrating an example of a table for managing content information.
FIG. 13 is a flowchart illustrating an example of a process for registering a distribution session condition.
FIG. 14 is a flowchart illustrating an example of a process for registering a reception client condition.
FIG. 15 is a flowchart illustrating an example of a process for registering content information.
FIG. 16 is a flowchart illustrating an example of a process for registering multicast distribution conditions.
FIG. 17 is a flowchart illustrating an example of processing for performing content distribution based on multicast distribution conditions.
FIG. 18 is a diagram showing a configuration of a distribution condition generation control program according to the present invention.
[Explanation of symbols]
DESCRIPTION OF SYMBOLS 1 ... Multicast content delivery system, 10 ... Content provider, 20 ... Registration server, 21 ... Transmission / reception part, 22 ... Delivery session condition management part, 22A ... Delivery session condition table, 23 ... Reception client condition management part, 23A ... Reception client condition Table 24. Content information management unit 24 A Content information table 25 Multicast distribution condition management unit 26 Distribution server registration unit 27 Recording medium 27 a Program storage area 28 Distribution condition generation control program 28 a ... main module, 28b ... multicast distribution condition generation module, 28c ... session information generation module, 28d ... output module, 30 ... distribution server, 31 ... transmission / reception unit, 32 ... content management unit, 33 ... distribution condition processing unit, 34 ... distribution Management unit 35 ... Distribution condition registration unit 35A ... Distribution session condition management unit 35B ... Reception client condition management unit 35C ... Content information management unit 35D ... Multicast distribution condition management unit 40 ... Client terminal 90 ... Content distribution System 91... Content provider 92. Distribution server 93 93 Client terminal.

Claims (6)

A multicast content distribution system in which a server and a content distribution device are connected by a network,
The server
According external condition setting request input from the content provider, distributing the session condition related session conditions during content distribution, the receiving client criteria regarding user condition of the client terminal receiving the content, and a content information about the distributed content is Multicast distribution conditions relating to conditions for multicast distribution of content based on content information including any of the information items of designation of various data files constituting content, creation date, content type, content name, and content overview A multicast distribution condition generating means for generating;
Session information generating means for generating session information related to a session at the time of distribution required for the client terminal to receive content distribution based on the generated multicast distribution conditions;
Output means for outputting the generated session information, multicast distribution conditions, and content entity data designated by the multicast distribution conditions to the content distribution apparatus;
With
The content distribution device
A content management unit for managing content entity data output by the output means of the server;
Manages session information and multicast distribution conditions output by the output means of the server. When the presence information of the user of the client terminal is received from the client terminal, the received presence information is matched with the multicast distribution conditions, and multicast distribution is performed. A distribution condition processing unit that notifies the client terminal of session information related to the content specified in the multicast distribution condition when the condition is met;
A distribution processing unit that performs multicast distribution of content entity data managed by the content management unit based on multicast distribution conditions;
Multicast content delivery system comprising, characterized in that the. The condition setting request input from the content provider is
2. The multicast content distribution according to claim 1, wherein the distribution request is a selection request for selecting a condition for each of a distribution session condition, a reception client condition, and content information, or a setting request for directly setting a generated multicast distribution condition. System . The server
The distribution session condition is stored and managed, and the distribution session condition input from the content provider is added, or the distribution session condition is extracted from the multicast distribution condition input from the content provider and the distribution session condition is set. multicast content delivery system according to claim 1 or 2, further comprising said Rukoto the delivery session condition management means for adding. The server
The reception client condition is stored and managed, and the reception client condition input from the content provider is added, or the reception client condition is extracted from the multicast distribution condition input from the content provider and the reception client condition is set. multicast content delivery system according to any one of claims 1 to 3, further comprising wherein Rukoto incoming client condition management means for adding. The server
Content information stored and managed, the multicast content delivery system according to any one of claims 1-4, wherein further comprising a Rukoto content information managing means for adding content information input from the content provider . A multicast content delivery control method executed in a multicast content delivery system in which a server and a content delivery apparatus are connected by a network ,
In accordance with a condition setting request input from an external content provider, the multicast distribution condition generating means of the server, the distribution session condition regarding the session condition at the time of content distribution, the receiving client condition regarding the user condition of the client terminal that receives the content, and the distribution Distribution of content based on content information that includes information items such as specification of various data files that make up the content, creation date, content type, content name, and content overview A multicast distribution condition generation step for generating a multicast distribution condition related to a condition for
A session information generating step in which the session information generating means of the server generates session information related to a session at the time of distribution required for the client terminal to receive content distribution based on the generated multicast distribution condition;
An output step in which the output means of the server outputs the generated session information, multicast distribution conditions, and content entity data specified by the multicast distribution conditions to the content distribution apparatus;
A content management step in which the content management unit of the content distribution device manages the content entity data output by the output means of the server;
The distribution condition processing unit of the content distribution apparatus manages the session information and multicast distribution conditions output by the output means of the server, and when the presence information of the user of the client terminal is received from the client terminal, the received presence information and multicast A distribution condition processing step of performing matching with the distribution condition and notifying the client terminal of session information regarding the content specified in the multicast distribution condition when the multicast distribution condition is satisfied;
A distribution processing step in which the distribution processing unit of the content distribution device performs multicast distribution of the content entity data managed by the content management unit based on multicast distribution conditions;
The a distribution control method of multicast content, characterized in that.

Images