Content distribution server and content distribution system

Abstract

Provided is a content distribution server having enhanced flexibility in selecting a terminal to be asked for provision of live video or the like. This content distribution server comprises: a theme management unit that receives, from a client terminal, a theme information set including a theme name, position information, and a publication mode related to a theme for inviting provision of content data, and transmits the received theme information set to provider terminals to invite provision of the content data related to the theme; a content information management unit that receives content data transmitted from the provider terminals and records the content data in a content recording unit; and a content distribution unit that distributes the content data related to the theme among the content data stored in the content recording unit on the basis of the publication mode included in the theme information set.

Description

Content distribution server and content distribution system

[0001] The present invention relates to a content distribution server and a content distribution system, and more particularly to a content distribution server and a content distribution system that provide content data provided in response to a request from requesters to requesters and / or viewers.

[0002] With the widespread use of mobile devices such as smartphones equipped with high-performance cameras, an environment is being created in which many people can become live video broadcasters.

[0003] Patent Document 1 discloses a video storage device that automatically selects a camera terminal with location information closest to the location of a subject to be photographed and requests that camera terminal to photograph the subject, thereby enabling the subject to be photographed quickly. When a subject to be photographed appears, a videophone with location information closest to the location of the subject among pre-registered videophones is searched for, and a request is made to that videophone via a network. The owner of the selected videophone can quickly arrive at the location of the subject to be photographed and quickly photograph the subject.

[0004] Japanese Patent Application Laid-Open No. 2005-51546

[0005] The inventor realized that with such conventional technology, the shooting terminal is limited to a terminal that has been registered in advance, and is not necessarily the most suitable shooting terminal, and that the closest location is not necessarily the most suitable location for shooting live footage.

[0006] To provide a content distribution server that allows a photographer's terminal to respond to requests for the provision of videos, etc., taking into consideration information other than location, and that can use the provided content data in accordance with various disclosure modes.

[0007] The means for solving these problems will be described below, but other problems and novel features will become apparent from the description of this specification and the accompanying drawings.

[0008] According to one embodiment of the present invention, the following is true.

[0009] A content distribution server is connected to a network and records and distributes content data received from provider terminals including both or either member provider terminals and non-member provider terminals, and comprises the following components.

[0010] Theme management unit: Receives from the requester terminal a theme information set including the theme name, location information, and publication mode related to the theme for which content data is being solicited, and sends the received theme information set to the provider terminal to solicit content data related to the theme.

[0011] Content information management unit: Receives content data transmitted from the provider terminal and records the content data in the content recording unit.

[0012] Content distribution unit: distributes content data related to the theme among the content data stored in the content recording unit based on the disclosure mode included in the theme information set.

[0013] Here, the terms "member provider terminal" and "non-member provider terminal" refer to terminals that provide content, and are used to distinguish between those who film, create, and provide the content and those who are members under a contract with the content distribution server operator and those who are not yet members (non-members). Various contract types are possible, such as non-members becoming members through application.

[0014] The effects obtained by the embodiment are briefly described below.

[0015] The content distribution server of this embodiment invites requests for content data by indicating at least location information, time information, and information on the release mode related to the theme, thereby making it easier for the requester to provide the content data they desire. This makes it possible to efficiently gather provider terminals that acquire content data on the theme (such as by shooting video), and to distribute the content data in a release mode that suits the characteristics of the theme.

[0016] FIG. 1 is a diagram showing a schematic example of the configuration of a content distribution system according to the present invention. FIG. 2 is a diagram showing an example of the hardware configuration of a content distribution server according to the present invention. FIG. 3 is a diagram showing an example of the hardware configuration of a requester terminal according to the present invention. FIG. 4 is a flowchart showing an outline of a process for soliciting content data by a requester terminal, a content distribution server, and a provider terminal according to the present invention. FIG. 5 is a flowchart showing an outline of a process for providing content data by a requester terminal, a content distribution server, and a provider terminal according to the present invention. FIG. 6 is a flowchart showing an outline of a process for a provider terminal according to the present invention to check themes currently being solicited. FIG. 7 is a diagram showing an example of a screen of a requester terminal according to the present invention. FIG. 8 is a diagram showing an example of a screen showing an instruction to operate a content data mark displayed on the screen of a requester terminal according to the present invention. FIG. 9 is a diagram showing an example of the data structure of a content source recording unit and a content archive recording unit according to the present invention. FIG. 10 is a diagram showing an example of the data structure of a member information recording unit according to the present invention.

[0017] 1. Overview of the Embodiments First, an overview of the representative embodiments disclosed in the present application will be described. Reference numerals in parentheses in the drawings used in the overview of the representative embodiments merely illustrate components included in the concept of the components to which they are attached.

[0018] [1] A content distribution server that specifies the publication mode and solicits content data from provider terminals. A representative embodiment disclosed in this application is a content distribution server (100) that is connected to a network (50) and records and distributes content data received from provider terminals (30) including both or either a member provider terminal (30a) and a non-member provider terminal (30b), and has the following configuration (Figures 1 and 2).

[0019] A theme management unit (130) receives from a requester terminal (10) a theme information set including a theme name, location information, and publication mode relating to a theme for which content data is being solicited, and transmits the received theme information set to the provider terminal (10) to solicit content data relating to the theme.

[0020] A content information management unit (150) receives content data transmitted from the provider terminal and records the content data in a content recording unit (180).

[0021] a content distribution unit (170) that distributes content data related to the theme among the content data stored in the content recording unit (180) based on the disclosure mode included in the theme information set;

[0022] Here, the requester terminal (10) is a terminal operated by a requester who requests the provision of content data related to a theme. The requester terminal also includes a request terminal used by a television station or a video production company when requesting the provision of content data as part of a program to be produced.

[0023] A theme refers to the subject of the content, such as events occurring in a specific location, incidents, disaster prevention information, local crime prevention information, and information for monitoring. Content data refers to information related to a theme, including video, still images, audio, text, and combinations thereof. Providing content data means sending filmed video and still images, recorded audio, entered text data, etc. to a content distribution server, with the assumption that the data will be used for distribution, etc.

[0024] The release mode refers to the mode of distribution of content data recorded on the content distribution server (10). For example, there are modes such as releasing the data to the general public without any restrictions, allowing transmission only to the requester's terminal, or releasing the data only to terminals that meet specific requirements. The mode of allowing transmission only to the requester's terminal is, for example, when the requester is a television station or video production company, and the posted video (content data) is used exclusively by the company. Also, when the requester is a nursing home, this is the case when searching for wandering elderly people. The mode of releasing the data only to terminals that meet specific requirements is, for example, when content data is distributed only to terminals that have paid a membership fee. An example of releasing the data to the general public without any restrictions is when you want to liven up an event.

[0025] The "distribution" of content data from the content distribution server (100) includes not only distribution from the content distribution server (100) to a viewer terminal (40) connected via a network (50), but also distribution from a terminal under the control of the client, such as the client terminal (10), or distribution to the client terminal (10) for broadcasting from broadcasting equipment.

[0026] The provider terminal (30) is a terminal that acquires content data related to a theme and transmits it to the content distribution server (10). A terminal operated by a member of this system is called a member provider terminal (31a), and a terminal operated by a non-member is called a non-member provider terminal (30b). Here, a member refers to a person who registers personal information and the like under a contract with a business operator that operates the content distribution server, and who provides the location information of the member provider terminal to the content distribution server as needed.

[0027] Furthermore, the network (50) connects the client terminal (10), editing terminal (20), provider terminal (30), content distribution server (100), and viewer terminal (40) so that they can communicate with each other, and refers to, for example, the Internet or a mobile phone network, and the communication may be wired or wireless.

[0028] With the above configuration, the content distribution server (100) of this embodiment can request the provider terminals (30) to provide content data related to a theme, and can set the publication mode of the content data and distribute it. This makes it possible to efficiently gather provider terminals (30) that take photos of the theme, and to distribute the content data in a publication mode that suits the characteristics of the theme.

[0029] [2] Sending an instruction to send a push notification of theme solicitation to the provider terminal In the content distribution server of [1], when the content information management unit (150) sends the theme information set to the provider terminal (30), the content information management unit (150) also sends an instruction for the provider terminal (30) to send a push notification to inform the owner of the terminal of information about the theme if the member provider terminal (30a) is located in an area within a predetermined distance from the location information.

[0030] The push notification from the provider terminal (30) makes it easier for the owner of the provider terminal to notice the theme solicitation, and furthermore, since the provider terminal is located in an area within a predetermined distance from the location information associated with the theme, notification can be sent to providers who are likely to provide content data.

[0031] Here, push notification refers to a function of a mobile device (such as a smartphone) that notifies you of messages, news, the start of sales, etc., by displaying notifications on the mobile device's lock screen or by sound or vibration.

[0032] [3] Confirming the provided content data at the client terminal In the content distribution server of [1] or [2], the content distribution unit (170) transmits the requested content data to the client terminal (10) in response to a request from the client terminal (10).

[0033] This allows the requester to check the provided content data and use it in their own business.

[0034] [4] Using content data from non-member provider terminals In any one of the content distribution servers [1] to [3], the theme management unit (130) selects the non-member provider terminal (30b) based on a response possibility factor, which is a factor related to the possibility that the non-member provider terminal (30b) will respond to a request for content data related to the theme, and sends the theme information set along with information that content data related to the theme is being solicited.

[0035] This makes it possible to efficiently send content solicitations to non-member provider terminals (30b) as well, and to provide a content distribution server (100) with improved freedom in selecting a terminal to request the provision of content data.

[0036] [5] Recruiting providers based on location information (obtaining location information of non-members from other media) In the content distribution server of [4], the theme management unit (130) uses location information regarding the non-member provider terminal (30b) as the response possibility factor.

[0037] This location information can be used by recording information that the owner of the non-member provider terminal 30b has made public on other media.

[0038] This makes it possible to selectively send a request for content data to non-members who are likely to be in areas close to the subject of the theme.

[0039] [6] Seeking providers related to the content of the theme (obtaining factors for the likelihood of response of non-members from public information on SNS) In the content distribution server of [4], the theme management unit uses information that the owner of the non-member provider terminal has made public on the Internet as the factors for the likelihood of response.

[0040] This allows the request for content data to be sent to non-members who are likely to be closely related to the theme subject, with the search results narrowed down efficiently.

[0041] [7] Recruiting donors based on location information (obtained from the mobile phone base station to which the photography terminal is connected) In the content distribution server of [4], the theme management unit (130) uses information on the mobile phone base station to which the non-member donor terminal (30b) is connected as the response possibility factor.

[0042] This allows the request for content data to be sent to non-members who are likely to be in areas close to the theme target in an efficient manner.

[0043] [8] The client instructs the content distribution server on settings related to the content data. In any one of the content distribution servers [1] to [7], the content information management unit (150), upon request from the client terminal (10), transmits to the client terminal the content data provided by the provider terminal (30) and content data attribute information related to the content data, which information is composed of the provider terminal identification number, location information, time information, and data type, and performs settings related to the content data based on the response to the transmission.

[0044] Settings related to content data refer to the settings for the release mode of the content data and whether or not it can be released. These settings are made when changing the release mode of content data that has already been distributed, or when selecting and distributing several content data from multiple content data provided. The content distribution server can accept all content data that meets the application conditions, so the requester data can choose the content data to distribute.

[0045] This allows the client terminal to use content data that has already been distributed, or allows the client to select content data to be made public from among the provided content data.

[0046] [9] The client edits the content data of the content distribution server. Any one of the content distribution servers [1] to [8] further has a content editing unit (160) that edits the content data recorded in the content recording unit based on instructions from an editor terminal that instructs editing of the content in the content recording unit or from the client terminal.

[0047] This allows the theme requester or content editor to be provided with the ability to edit the content to be distributed.

[0048]

[10] Mutual communication between the requester and the provider who provided the content data. Any one of the content distribution servers [1] to [9] further has a direct communication unit (175) that enables two-way communication between the requester terminal and the provider terminal.

[0049] Here, direct communication refers to direct, two-way communication between the requester terminal (10) and the provider terminal (30). For example, it is possible to obtain comments on the content data being distributed from the owner of the provider terminal (30), or to issue specific requests regarding photography, such as taking a closer-up shot.

[0050]

[11] Recording of content data distribution log In any one of the content distribution servers [1] to

[10] , the content distribution unit records at least the distribution time of the distributed content data in the content recording unit.

[0051] This allows the record of the distribution time to be used as a basis for calculating the fee to be paid by the requester of the content data to the content provider.

[0052]

[12] Recording of archive of content data In the content distribution server of

[11] , the content recording unit (180) is composed of a content source recording unit (182) that records content of live broadcasts and ongoing events and plays it back at the time of distribution, and a content archive recording unit (184) that records content for which the target time for a theme has already passed and plays it back at the time of distribution, and the content information management unit (150) records the time when the content data of one or both of the content source recording unit (182) and the content archive recording unit (184) is distributed.

[0053] This allows the content distribution server (100) to distribute not only ongoing content data but also past content data, and the requester can also obtain data that serves as the basis for calculating the remuneration to be paid to past content providers.

[0054]

[13] Recording the provider's content provision performance In any one of the content distribution servers [1] to

[12] , the content information management unit (150) records provider performance information, which is information regarding the distribution of the content data, in the provider terminal information recording unit (140), which records information regarding the provider terminal (30).

[0055] Here, the provider performance information is information indicating the performance of content delivery provided by the provider terminal 30, and is composed of the provider terminal identification number, content data delivery information, etc. The content data delivery information is information related to the delivery of content data, and is composed of, for example, a theme identification number, a provider terminal identification number, and information related to each delivery log, etc. The delivery log is a log related to the delivery of content data, and is composed of information such as the delivery start time, delivery end time, delivery duration, and delivery destination terminal.

[0056] The content distribution server (100) records the provider's content data provision record, and by referring to this content data distribution information, the provider can use it as a reference when calculating the amount of remuneration or when soliciting submissions for the next theme.

[0057]

[14] Sending themes currently being solicited to the provider terminal In any one of the content distribution servers [1] to

[13] , the content information management unit (150) sends a list of themes currently being solicited to the provider terminal (30) in response to a request from the provider terminal (30).

[0058] This allows the owner of the non-member provider terminal (30b) to check themes currently being collected, and the owner of the member provider terminal (30a) to check themes currently being collected without having to search for notifications of theme collection received in the past.

[0059]

[15] Content distribution system A content distribution system comprising any one of the content distribution servers (100) from [1] to

[14] , the requester terminal (10), and the provider terminal (30).

[0060] The content distribution system of this embodiment can request provider terminals (30) to provide content data related to a theme, and can set the publication mode of the content data before distributing it. This makes it possible to efficiently gather provider terminals (30) that take photos of the theme, and to distribute the content data in a publication mode that suits the characteristics of the theme.

[0061]

[16] Member provider terminal with the function of sending push notifications for theme solicitation and the function of applying filters In the content distribution system of

[15] , the member provider terminal (30a) among the provider terminals (30) receives an instruction to send the push notification from the content distribution server (100), and then, when certain conditions are met, sends a push notification to the member provider terminal (30a) with information regarding the theme being solicited, and further, the member provider terminal (30a) can filter the push conditions.

[0062] Here, the information about the theme is, for example, the name of the theme. Applying a push condition filter means that the member provider terminal determines whether to receive or reject pushed notifications based on the conditions set, for example, limiting received notifications to recruitments with rewards, or limiting the provided content data to themes that are open to the general public.

[0063] This makes it easier for the owner of the provider terminal (30) to notice the theme solicitation through push notifications. Furthermore, since the provider terminal is located within a predetermined distance from the location information associated with the theme, notifications can be sent to providers who are likely to provide content data. Furthermore, if push notifications are sent frequently, the provider can apply a filter to the provider terminal (30) so that push notifications are sent only for themes that can be applied for.

[0064]

[17] Displaying location information of content data on a map displayed on the client terminal In the content distribution system of

[15] or

[16] , the client terminal (10) displays a content data mark (73) indicating the content data on a map (74) based on the location information of the content data received from the content distribution server (100), and the content data mark (73) is displayed so that the data type of the content data and the device that acquired the content data can be visually identified (Figure 7).

[0065] This allows the requester to know the location information of the provided content data, the data type, and information about the device that acquired the content data.

[0066]

[18] Touching a content data mark on a map to display an operation screen. In the content distribution system of

[17] , the client terminal (10) displays a screen on which an operation related to the content data mark can be input.

[0067] As a result, the requester can touch the display unit of the requester terminal to display an operation screen, and by operating the screen, input operations to the content distribution server (100). This allows viewing, editing, etc. of content data related to the content data mark to be performed with simple operations.

[0068]

[19] Displaying content data on the client terminal In the content distribution system of

[17] or

[18] , the client terminal (10) requests the content distribution server (100) to transmit the content data, receives the content data transmitted from the content distribution server (100), and displays it.

[0069] This allows the operator of the client terminal (10) to check the content data.

[0070]

[20] The client edits the content data of the content distribution server. In the content distribution system of

[19] , the client terminal (10) requests the content distribution server (100) to edit the content data and instructs the content distribution server (100) to edit the content data.

[0071] This allows the client to edit the content data on the content distribution server (100).

[0072]

[21] Displaying a content data mark for a specific time period on a map In any one of the content distribution systems

[17] to

[20] , the client terminal (10) displays the content data mark (73) for a specific time period, and by operating the display screen, the client terminal (10) can change the time period setting and display the content data mark (73) for the changed time period.

[0073] This allows the requester to check not only the current distribution status of content data, but also the provision status of content data for future and past events.

[0074]

[22] Mutual communication between the requester and the provider who provided the content data. In any one of the content distribution systems

[15] to

[21] , the requester terminal (15) performs two-way communication with the provider terminal (30) via the content distribution server (100).

[0075] This allows the requester to give instructions to the provider terminal and obtain comments from the provider via the requester terminal (10).

[0076] 2. Details of the embodiment The embodiment will be described in further detail.

[0077] A content distribution server and a content system according to the present embodiment will be described in detail below with reference to the accompanying drawings, showing preferred embodiments. The present invention is not limited to these embodiments and includes various modifications and improvements. In other words, the components described below include those that would be easily conceivable to a person skilled in the art or that are substantially identical, and the components described below can be combined as appropriate. Furthermore, various omissions, substitutions, or modifications of the components of this embodiment can be made without departing from the spirit of the present invention.

[0078] Specific configuration examples of the present invention will be described below with reference to the drawings.

[0079] <Configuration of Content Distribution System> Fig. 1 is a diagram showing a schematic example of the configuration of a content distribution system according to this embodiment. As shown in Fig. 1, a content distribution server 100 is connected via a network 50 to a requester terminal 10, an editing terminal 20, and multiple provider terminals 30, including multiple member provider terminals 30a and multiple non-member provider terminals 30b, and can distribute content data to multiple viewer terminals 40.

[0080] The requester terminal 10 requests the content distribution server 100 to collect content data related to a predetermined theme and to distribute the provided content data. Furthermore, the requester terminal 10 can receive the content data provided by the content distribution server 100, display it, or use it itself.

[0081] The editing terminal 20 instructs the content distribution server 100 to edit the content data stored in the content distribution server 100. The editing terminal 20 may be included as a function within the requester terminal 10. In this case, the requester terminal 10 edits the content data stored in the content distribution server 100. Here, editing refers to, for example, selecting one or several pieces of content data from multiple pieces of content data and inserting (fitting) them into a predetermined layout within a program to be distributed. Other types of editing include adding captions or annotations, applying image processing to blur portions, and overlaying audio. It is even more preferable if the editing terminal 20 (or the requester terminal 10) is configured to receive low-resolution content data, and the content distribution server then edits the high-resolution image to be distributed in accordance with the instructions based on the low-resolution content data.

[0082] The provider terminals 30 include a member provider terminal 30a and a non-member provider terminal 30b. The member provider terminal 30a is a member of the system to which the content distribution server 100 belongs, and member data is recorded in the terminal information recording unit 190. The provider terminal identification number, which is the identification number of the member provider terminal 30a, may be the same as the membership number, for example. The non-member provider terminal 30b is a terminal of a general provider who is not a member.

[0083] The content distribution server 100 requests content data from the provider terminal 30, records the provided content, and distributes it. Here, "distribution" includes not only distribution from the content distribution server 100 to the viewer terminal 40 connected via the network 50, but also distribution from a terminal under the control of the requester, such as the requester terminal 10, and distribution of content data to the requester terminal 10 for broadcasting from broadcasting equipment.

[0084] <Configuration of Content Distribution Server> Figure 2 is a diagram showing an example of the hardware configuration of the content distribution server of this embodiment. The content distribution server 100 is composed of a communication unit 110, a display unit 120, a theme management unit 130, a provider terminal information management unit 140, a content information management unit 150, a content editing unit 160, a content distribution unit 170, a direct communication unit 175, a content recording unit 180, and a terminal information recording unit 190. The content recording unit 180 is composed of a content source recording unit 182 and a content archive recording unit 184. The content distribution server 100 may be composed of a server connected to the Internet, or may be realized using a cloud server.

[0085] The communication unit 110 is connected to the network 50 and transmits and receives data. The display unit 120 displays the status of the content distribution server 100, data, and the like.

[0086] The theme management unit 130 assigns a theme identification number, which is a number that identifies the theme, to the theme requested from the requester terminal 10 and manages the theme. The theme management unit 130 receives and records a theme information set from the requester terminal 10, including information about the theme such as the theme name, location information of the theme, time information, publication mode, and additional information. The location information of the theme can be set according to the characteristics of the theme, such as a circle centered on latitude and longitude, an area, a venue such as a music festival, or a roadside of a relay race. The additional information can specify information about a contract, such as compensation for distribution of content data.

[0087] If the content distribution server has the function of distributing content data that is not related to the theme requested by the requester terminal 10, the owner of the requester terminal 10 can view content data already distributed by the content distribution server 100 and request content data related to that content data. In this case, the theme management unit 130 can determine that the theme of the already distributed content data is the same as the theme requested based on the location information and time information of the already distributed content data transmitted from the requester terminal 10, and process the content data accordingly. Specifically, the theme identification number of the content data set related to the already distributed content data can be matched with the identification number of the requested theme. Here, the content data set is composed of content data attribute information and the content data itself. The content data attribute information is information related to the content data, and is composed of the theme identification number, content data identification number, location information, time information, data type, content data acquisition device information, provider terminal identification information, publication mode, etc.

[0088] The theme management unit 130 transmits information requesting the provision of content data to the selected member provider terminal 30 and non-member provider terminal 30b regarding the requested theme.

[0089] The theme management unit 130 reads member information from the member information recording unit 192 and requests the member provider terminal 30a to provide content data for the theme for which content data has been solicited from the requester terminal 10. At this time, the theme management unit 130 preferentially selects the member provider terminal 30a of a member whose location information is close to the location information related to the theme, and transmits the theme information set along with information indicating that content data related to the theme is being solicited, thereby requesting the provision of content data. The member's location information may be, for example, real-time terminal latitude and longitude information acquired by a GPS (Global Positioning System) installed in the member provider terminal 30a, or the member's home or workplace address, etc.

[0090] Furthermore, the theme management unit 130 can instruct the member provider terminal 30a to use its own push notification function. This push notification function can instruct the member provider terminal device 30b to send a push notification under predetermined conditions. These predetermined conditions include, for example, when the provider terminal comes within a predetermined distance from the location information of the content data being collected, or when the provider terminal enters the venue of the target event.

[0091] Furthermore, the theme management unit 130 selects the non-member provider terminal 30b and transmits the theme information set to the non-member provider terminal 30b based on response possibility factors, which are factors related to the likelihood that the non-member provider terminal 30b will respond to a request to photograph the theme. These response possibility factors include the following: For example, information published on the Internet by a non-member may indicate that the non-member's usual activity area is close to the location where the theme is being held, or the location information of the non-member's mobile phone base station. These response possibility factors may be collected and recorded in advance by a non-member information recording unit 196, or may be collected during recruitment and recorded thereafter.

[0092] When transmitting a theme information set to the non-member provider terminal 30b, the theme management unit 130 can include information requesting the inclusion of location information of the non-member provider terminal (basically real-time terminal latitude and longitude information acquired by a GPS installed in the non-member provider terminal 30b) in the information to be transmitted as content data. This increases the likelihood that the requester terminal 10 will receive content data acquired at the desired location.

[0093] The theme management unit 130 can create a solicitation theme information list, which is a list of information related to themes. This solicitation theme creation list is composed of the theme name, theme identification number, location information, time information, release mode, and additional information. The additional information can also include information such as the price and conditions for providing content data. The location information can be set according to the characteristics of the theme, such as a circle centered on latitude and longitude, an area, a venue such as a music festival, or the roadside of a relay race course. In response to a request from the provider terminal 30, the theme management unit 130 can transmit the solicitation theme information list to the provider terminal 30 as a list of themes currently accepting submissions. This allows the provider terminal 40 to know the themes currently accepting submissions, obtain content data for those themes, and provide them to the content distribution server 100.

[0094] The theme management unit 130 can receive information such as the publication mode of content data that has already been distributed from the client terminal 10 and change the settings of the content data, for example, when the owner of the client terminal 10 wants to use content data that has already been published.

[0095] The provider terminal information management unit 140 manages information on the member provider terminal 30a and non-member provider terminals. The provider information consists of additional information. The additional information includes, for example, membership rank (regular member, cooperating member), distribution record information, etc. The member provider terminal information management unit 140 records information on the provider terminal 30 that provided content data in the provider terminal information management unit 194. At this time, the information that the provider terminal information management unit 140 records in the provider terminal information recording unit 192 includes, for example, the provider terminal identification number, whether content can be provided, location information, and the time the response was received.

[0096] The content information management unit 150 receives content data transmitted from the provider terminal 30 and records it in the content source recording unit 182. At this time, the content information management unit 150 assigns a content data identification number that identifies the content data to the received content data, and records it together with the content data in the content source recording unit 182. The content information management unit 150 records a content data set made up of this content data identification number, theme identification number, location information, time information, data type, content acquisition device, content data body, provider identification number, etc. in the content source recording unit 182.

[0097] In order to notify the requester terminal 10 that content data has been received, the content information management unit 150 can also transmit content data attribute information consisting of a theme identification number, content data identification number, data type, location information, time information, provider terminal identification number, etc. to the requester terminal 10 and the editing terminal 20. The content data attribute information may further include a thumbnail. If the requester terminal 10 also serves as the editing terminal 20, the content information management unit 150 can send content data attribute information only to the requester terminal.

[0098] The content editing unit 160 transmits the content data recorded in the content source recording unit 182 for viewing in response to a request from the editing terminal 20 or the client terminal 10. Furthermore, the content editing unit 160 edits the content data in response to an instruction from the editing terminal 20 or the client terminal 10.

[0099] The content distribution unit 170 starts distributing content data when it receives an instruction to start viewing from the editing terminal 20 or the client terminal 10. The content distribution unit 170 performs distribution based on the release mode in response to a request from the viewer terminal 40. For example, if the release mode of the target content data is a member-only release mode, the content distribution unit 170 can confirm whether the viewer terminal 40 is eligible to view the content, and can distribute the content data only if the viewer terminal 40 is eligible to view the content.

[0100] The content distribution unit 170 can record the content data in the content source recording unit 182 or a part of the content data in the content archive recording unit 184. The content archive recording unit 184 can be used when distributing content data even after the implementation of a theme has ended. The content distribution unit 170 also distributes the content data in the content archive recording unit 184.

[0101] The content distribution unit 170 can record content data distribution information, which is information on the distribution status of content data, in the content source recording unit 182 or the content archive recording unit 184. The content data distribution information is made up of a theme identification number, a provider identification number, and each distribution log. The distribution log is log information for one distribution, and is made up of information such as the distribution start time, distribution end time, distribution duration, and information on the distribution destination terminal.

[0102] The direct communication unit 175 has a function of performing two-way communication between the requester terminal 10 and the provider terminal 30. If the requester terminal 10 is a television station, the requester terminal 10 can request comments from the provider who provided the content data of the accident video. The form of two-way communication by the direct communication unit 175 is not limited to video, audio, text data, etc., as long as it allows the requester terminal 10 and the provider terminal 30 to communicate with each other.

[0103] <Configuration and Operation of Requester Terminal> Fig. 3 is a diagram showing an example of the hardware configuration of the requester terminal 10 of this embodiment. The requester terminal 10 is composed of a communication unit 11, an input unit 12, a display unit 13, and a control unit 14. The requester terminal 10 is a computer such as a smartphone, tablet, or laptop. The communication unit 11 is an interface that communicates with the content distribution server 100. The input unit 12 accepts operations by the requester, and the display unit 13 displays data.

[0104] The requester terminal 10 requests the content distribution server 100 to collect content data related to a theme. Even if the requester is from a variety of industries, the requester terminal 10 can accommodate various applications by setting the release mode and additional information of the theme information set transmitted to the content distribution server 100. For example, if the requester is a television station, the release mode can be set to exclusive use of the content data, and the additional information can be set to payment to the provider. If the requester is an event organizer, the release mode can be set to public access, and the additional information can be set to payment based on the number of distributions. In the event of a disaster, if a local government wants to request information about a specific area from people in that area, the local government can specify the specific area as location information and set the release mode so that the local government can check it. For local crime prevention purposes, the local government can specify a specific location (location information), such as a park, and collect content data that captures the scene at that location. For monitoring purposes, information about wandering elderly people who have gone missing can also be collected.

[0105] The requester terminal 10 can check the content data provided to the content distribution server 100. By checking the content data provided to the content distribution server 100 in response to a theme call, the requester can select the content data to use and decide which content data to publish. The requester terminal 10 can instruct the content distribution server 100 on the publication mode of the selected and published content data. This function also allows the requester terminal 10 to view videos already posted to the content distribution server 100 and solicit videos related to that theme.

[0106] The requester terminal 10 can perform two-way communication with the provider terminal 30. If the requester is a television station, the requester can obtain comments from the owner of the provider terminal 30 that provided the content data, or can give instructions such as the angle and magnification of the video to the owner of the provider terminal 30 that is distributing live video. This two-way communication can be performed via the content distribution server 100.

[0107] <Example of Screen Configuration and Operation of Client Terminal> Fig. 7 is a diagram showing an example of a screen displayed on the client terminal 10 of this embodiment. The control unit 14 of the client terminal 10 can display information about content data provided by the content server 100 on the display unit 13. In the screen of Fig. 7, a theme name 71 is displayed at the top of the screen. The theme name 71 helps the user understand which theme the currently displayed screen pertains to. Themes include, for example, live events, crime scoops, disaster prevention, local crime prevention, and monitoring. The theme description 72 provides an explanation of the theme. It can be used to indicate whether a live broadcast or information about local crime prevention is desired.

[0108] Near the center of the screen, information about the content data is shown as a content data mark 73 based on the location information of the content data on a map 74. In Fig. 7, one content data mark 73 is shown for each piece of content data, but multiple pieces of content data can also be grouped together as a content data mark 73.

[0109] The design of the content data mark 73 can indicate the properties of the content data mark 73. In the example of Fig. 7, the characters written on the content data mark 73 indicate the content, such as "DR" indicates content data captured by a drive recorder, "PC" indicates a still image, "MO" indicates a video, "LN" indicates a current live broadcast, and "LF" indicates a future live broadcast. It can also indicate whether the provider terminal 30 that provided the content data mark 73 is a member provider terminal 30a or a non-member provider terminal 30b.

[0110] In Figure 7, a time scale 75 is displayed below the map 74. The status of the content data marks 73 displayed on the map 74 indicates the status at a certain point in time. This makes it possible to grasp the status of content data distribution during the time periods in which the theme will be held, from the past to the present and in the future. By manipulating this time scale 75, the display of the content data marks 73 displayed on the map 74 can be changed to show the status for the corresponding time period. This makes it possible to predict the status of content data provision for an event to be held tomorrow, for example, and determine whether further recruitment is necessary.

[0111] The layout of the display screen of the client terminal 10 can be changed as appropriate.

[0112] FIG. 8 is a diagram of a screen showing an example of an instruction to operate the content data mark 73 displayed on the screen of the requester terminal 10 in this embodiment. The operation screen 81 is used when the requester terminal 10 sends an instruction to the content distribution server 100. The operation screen 81 pops up and is displayed, for example, when the content data mark 73 displayed on the requester terminal 10 is touched with a finger. The operation screen 81 displays operation items 82. When the "Get Content Data" item is touched, the requester terminal 10 transmits a request for content data to the content distribution server 100, and the requester terminal 10 can display the content data received from the content distribution server 10. Additionally, the operation screen 81 can be used, for example, to change the disclosure mode of content data distributed by the content distribution server 100 or to perform direct communication.

[0113] <Functions of Editing Terminal> The editing terminal 20 edits content data recorded in the content distribution server 100. The editing terminal 20 is a computer device such as a smartphone, tablet, or personal computer. Specifically, the editing terminal 20 receives content data information from the content distribution server 100 and displays it on the display unit of the editing terminal 20. Editing instructions input to the input unit can be sent to the content distribution server 100 to edit the content data. If the client terminal 10 also functions as the editing terminal 20, the client terminal 10 sends editing instructions to the content distribution server 100.

[0114] <Configuration of the Content Recording Unit> The content source recording unit 182 records content data received from a content provider. The data recorded in this content source recording unit 182 can be edited by the client terminal 10 and the editing terminal 20. The data recorded in the content source recording unit 182 is distributed to the viewer terminal 40. This distribution can also accommodate live broadcasts.

[0115] The content archive recording unit 184 records each piece of content data recorded in the content source recording unit or a part of it, so that it can be distributed even after the theme has ended.

[0116] 9 shows an example of the data structure of the content source recording unit and the content archive recording unit of this embodiment. The content source recording unit 182 and the content archive recording unit 184 record, for example, content data attribute information, content data itself, and a delivery log. Specifically, these include a theme identification number, a content data identification number, location information, time information, data type, content data acquisition device, provider terminal identification number, release mode, content data itself, and a delivery log.

[0117] Here, the content data identification number is a number that identifies the content data. The theme identification number is a number that identifies the theme that the content is directed to. The location information is the location information of the content data provider terminal. The content time information is the start and end time of provision and the recording time of the content if the content is video or audio, and is the acquisition time if the content is still images or text. The data type is the type of content data, such as video, still images, audio, text, etc. The content acquisition device is the device that acquired the content, and indicates the type of device, such as a smartphone or dashcam.

[0118] <Configuration of Terminal Information Recording Unit> The terminal information recording unit 190 is composed of a member information recording unit 192 and a provider information recording unit 194 (Fig. 2). Fig. 10 is a diagram showing an example of the data structure of the member information recording unit 192. The member information recording unit 192 records the provider terminal identification number, member rank, additional information, etc. The member rank is information that ranks members based on the distribution record of content provided by that member in the past, etc. The additional information is information such as the provision log of past content data.

[0119] The provider information recording unit 194 records information about the provider terminals 30 that have responded to the content data solicitation, such as a provider identification number for identifying the provider, a theme identification number, and location information.

[0120] The terminal information recording unit 190 may further include a non-member information recording unit 196. When requesting content data from non-members, if the request is not made to terminals that are somewhat likely to respond to the request, the target set will be too broad, resulting in inefficiency. Therefore, the theme management unit 130 selects the provider terminal 30b from which the request is made based on a response likelihood factor, which is a factor related to the likelihood that the non-member provider terminal 30b will respond to the request for content data related to the theme. The non-member information recording unit 196 records this response likelihood factor and may be temporarily provided. The non-member information recording unit 196 may include, for example, a non-member terminal identification number, non-member terminal location information, contact information, etc. The non-member terminal identification number is a number used to identify non-member terminals and may be temporarily assigned for each theme. The non-member location information includes location information obtained from information publicly available on the Internet by non-members, location information from mobile phone base stations, and location information obtained through communication with non-members.

[0121] <Charging Method for Content Distribution> A requester can request the system administrator of a content distribution system centered around the content distribution server 100 to provide content data via the provider terminal 30, for example, for a monthly fee. In this case, the system administrator can pay a fee to the provider based on the information recorded in the provider information recording unit 190 and the content recording unit 180. Examples of the requester include news media, marketing companies, and local governments.

[0122] The client can also request the provision of content data from the provider terminal 30, who is a participant in the themed event, in the form of profit sharing. In this case, the content can be viewed by the viewer terminal 40 that has previously concluded a billing contract with the administrator, and a fee corresponding to the viewing can be paid to the content provider and the client.

[0123] In either case, rewards can be distributed by utilizing the theme identification number, provider terminal identification number, content data identification number, and content data distribution information recorded in the content distribution server 100.

[0124] <Flow of Theme Solicitation> FIG. 4 is a flowchart showing an outline of processing related to the solicitation of content data by the requester terminal, the content distribution server, and the provider terminal of this embodiment.

[0125] The requester terminal 10 transmits information about the theme for which requests are being solicited to the content distribution server 100 (step S412). At this time, the requester terminal 10 transmits to the content distribution server 100 a theme information set, which is information about the theme such as the theme name, location information about the theme, and time information.

[0126] The content distribution server 100 receives the theme information set (step S4102) and assigns a theme identification number. The content distribution server 100 registers the received theme information set in a theme information collection list (step S4104) and transmits to the provider terminal 30 a message that a theme collection has been opened. At this time, the content distribution server 100 transmits the theme information set, collection period, rewards, and other conditions to the provider terminal 30 (step S4106).

[0127] The provider terminal 30 receives the information about the theme solicitation (step S432), and the owner of the provider terminal 30 is informed of the theme solicitation. The owner of the provider terminal 30 reviews the information, and if he or she wishes to provide content data related to that theme, makes preparations for providing the content (step S434). For example, he or she may go to the location on the date and time of the theme.

[0128] <Flow of Providing Content Data> FIG. 5 is a flowchart showing an outline of processing related to the provision of content data by the client terminal, the content distribution server, and the provider terminal of this embodiment.

[0129] After acquiring the content data, the provider terminal 30 transmits the acquired content data together with location information, information on the content data acquisition device, etc. to the content distribution server 100 (step S532). If the theme identification number and release mode are known from the theme solicited, the provider terminal 30 transmits a content data set consisting of the theme identification number, content data identification number, location, time, data type, content data acquisition device, content data body, provider terminal identification number, release mode, etc. to the content distribution server 102 (step S532).

[0130] The content distribution server 100 records the content data received from the provider terminal 30 (step S5102). In principle, the content distribution server accepts all provided content data. The content distribution server 100 distributes the content data provided from the provider terminal 30 based on the disclosure mode specified in the theme information set from the requester terminal (step S5104).

[0131] The client terminal 10 requests content data attribute information and the like from the content distribution server 100 (step S512). Specifically, for example, the content data location information of each piece of content data provided for the theme is requested. The content distribution server 100 transmits the requested information to the client terminal 10 (step S5108). The client terminal 10 receives this information (step S514) and can display the information on the display unit 13.

[0132] The requester terminal 10 requests content data selected from the provided content data attribute information from the content distribution server 100 (step S516). The content distribution server 100 receives this (step S5110) and transmits the corresponding content data to the requester terminal 10 (step S5112). The requester terminal 10 receives this content data (step S518), allowing the requester to review the content data. The requester can review the content data on the requester terminal 10 and select content data to be publicly distributed. The requester terminal 10 can then transmit instructions regarding the selected content data to the content distribution server. The requester terminal 10 can also request information on content data that has already been provided and even distributed, rather than on themes that are being solicited (step S516). This allows the requester terminal 10 to review content data that has already been distributed but is not yet solicited.

[0133] <Outline of Process Flow for Provider Terminal to Obtain Solicited Theme Information> FIG. 6 is a flowchart showing an outline of a process for a provider terminal of this embodiment to check themes currently being solicited.

[0134] The client terminal 10 transmits a theme information set, which is information on the theme being solicited, to the content distribution server 100 (step S612), and the content distribution server 100 receives it (step S6102) and registers it in the solicitation theme information list (step S6104).

[0135] The provider terminal 30 requests the content distribution server 100 to send a solicitation theme information list (step S632). The content distribution server 100 receives this request (step S6106) and transmits the solicitation theme information list to the provider terminal 30 (step S6108). The provider terminal 30 receives this request (step S634), checks the contents, and, if a theme is available, prepares to acquire content data related to that theme (step S636). This allows the owner of the provider terminal 30 to obtain information on the currently solicited theme without having to check multiple solicitation notifications sent to his or her provider terminal. When a theme is solicited from a requester terminal, the content distribution server 100 registers the theme in the solicitation theme information list as described above with reference to FIG. 4 and transmits a notification to the provider terminal 30 that a theme has been solicited. Thereafter, upon receiving a request from the provider terminal, the content distribution server 100 transmits a detailed theme information list to the provider terminal as described above. In addition, the content distribution server 100 may be modified so that when a theme is solicited from a requester terminal, it registers the theme in the solicited theme information list without waiting for a request from the provider terminal, and then sends a detailed theme information list directly to the provider terminal.

[0136] The invention made by the inventor has been specifically described above based on an embodiment, but it goes without saying that the invention is not limited thereto and can be modified in various ways without departing from the spirit of the invention.

[0137] The present invention relates to a content distribution server and a content distribution system, and in particular can be applied to a content distribution server and a content distribution system that provides content data provided in response to a request from a requester to a requester and / or a viewer.

[0138] 10 Requester terminal 20 Editing terminal 30 Provider terminal 30a Member provider terminal 30b Non-member provider terminal 40 Viewer terminal 50 Network 71 Theme name 72 Theme description 73 Content data mark 74 Map 75 Time scale 81 Operation screen 82 Operation items 100 Content distribution server 110 Communication unit 120 Display unit 130 Theme management unit 140 Provider terminal information management unit 150 Content information management unit 160 Content editing unit 170 Content distribution unit 175 Direct communication unit 180 Content recording unit 182 Content source recording unit 184 Content archive recording unit 190 Terminal information recording unit 192 Member information recording unit 194 Provider information recording unit 196 Non-member information recording unit

Claims

1. A content distribution server connected to a network, which records and distributes content data received from provider terminals including both or either of member provider terminals and non-member provider terminals, comprising: a theme management unit which receives from a requester terminal a theme information set including a theme name, location information, and disclosure mode relating to a theme for which content data is being solicited, and transmits the received theme information set to the provider terminal to solicit content data relating to the theme; a content information management unit which receives content data transmitted from the provider terminal and records the content data in a content recording unit; and a content distribution unit which distributes content data related to the theme from among the content data stored in the content recording unit, based on the disclosure mode included in the theme information set.

2. A content distribution server as claimed in claim 1, wherein when the content information management unit transmits the theme information set to the provider terminal, the content information management unit also transmits an instruction for the provider terminal to send a push notification to inform the owner of the terminal of the theme information when the member provider terminal is located within a specified distance from the location information.

3. A content distribution server according to claim 1 or 2, wherein the content distribution unit transmits requested content data to the client terminal in response to a request from the client terminal.

4. A content distribution server according to any one of claims 1 to 3, wherein the theme management unit selects the non-member provider terminal based on a response possibility factor which is a factor relating to the possibility that the non-member provider terminal will respond to the solicitation of content data related to the theme, and transmits to the non-member provider terminal the theme information set along with information that content data related to the theme is being solicited.

5. A content distribution server according to claim 4, wherein said theme management section uses location information relating to said non-member provider terminal as said response possibility factor.

6. A content distribution server according to claim 4, wherein said theme management section uses information that an owner of said non-member provider terminal makes public on the Internet as said response possibility factor.

7. A content distribution server according to claim 4, wherein said theme management section uses information on a mobile phone base station to which said non-member provider terminal is connected as said response possibility factor.

8. A content distribution server according to any one of claims 1 to 7, wherein the content information management unit, in response to a request from the client terminal, transmits to the client terminal content data provided by the provider terminal and content data attribute information relating to the content data, the content data being composed of a provider terminal identification number, location information, time information and data type, and performs settings relating to the content data based on a response to the transmission.

9. A content distribution server according to any one of claims 1 to 8, further comprising a content editing unit that edits the content data recorded in the content recording unit based on instructions from an editor terminal that instructs editing of the content in the content recording unit or from the client terminal.

10. A content distribution server according to any one of claims 1 to 9, further comprising a direct communication unit for performing two-way communication between the requester terminal and the provider terminal.

11. A content distribution server according to any one of claims 1 to 10, wherein the content distribution unit records at least the distribution time of the distributed content data in the content recording unit.

12. A content distribution server as claimed in claim 11, wherein the content recording unit is composed of a content source recording unit which records content of live broadcasts and ongoing events and plays it back at the time of distribution, and a content archive recording unit which records content for which the target time for a theme has already passed and plays it back at the time of distribution, and the content information management unit records the time when the content data of one or both of the content source recording unit and the content archive recording unit is distributed.

13. A content distribution server according to any one of claims 1 to 12, wherein the content information management unit records provider performance information, which is information relating to the distribution of the content data, in a provider information recording unit that records information relating to the provider terminal.

14. A content distribution server according to any one of claims 1 to 13, wherein the content information management unit transmits a list of themes currently being solicited to the provider terminal in response to a request from the provider terminal.

15. A content distribution system comprising the content distribution server according to any one of claims 1 to 14, the requester terminal, and the provider terminal.

16. A content distribution system as claimed in claim 15, wherein the member provider terminal among the provider terminals, after receiving an instruction to send the push notification from the content distribution server, sends a push notification of information relating to the theme currently soliciting entries to the member provider terminal when predetermined conditions are met, and further wherein the member provider terminal is capable of filtering the push conditions.

17. A content distribution system as claimed in claim 15 or 16, wherein the client terminal displays a content data mark indicating the content data on a map based on location information of the content data received from the content distribution server, and the content data mark indicates the data type of the content data and the device that acquired the content data so that it can be visually identified.

18. A content distribution system according to claim 17, wherein the client terminal displays a screen on which an operation related to the content data mark can be input.

19. A content distribution system according to claim 17 or 18, wherein the client terminal requests the content distribution server to transmit the content data, receives the content data transmitted from the content distribution server, and displays the content data.

20. A content distribution system according to claim 19, wherein the client terminal requests the content distribution server to edit the content data and instructs the content distribution server to edit the content data.

21. A content distribution system according to any one of claims 17 to 20, wherein the client terminal displays the content data mark for a specified time period, and by operating the display screen, can change the time period setting and display the content data mark for the changed time period.

22. A content distribution system according to any one of claims 15 to 21, wherein the requester terminal performs two-way communication with the provider terminal via the content distribution server.

Images