JP2022066113A - Company tie-up moving image sharing request acquisition support system - Google Patents

Abstract

To provide a system by which a moving image contributor who is not an extremely-popular moving image contributor but can expect a certain degree of moving image viewing frequencies can have a chance to acquire requests of company tie-up moving images.SOLUTION: The invention is configured so that an application page is sent and displayed on each contributor terminal 3 from a support server 1 about creation of a company tie-up moving image and a request of contribution of the moving image from a company, each moving image contributor sends application information from each contributor terminal 3, then the application information is recorded in an item management file 23. A lower limit value of a potential viewing frequency index is recorded in a request information file 22, and the potential viewing frequency index is recorded in a contributor information file 21 for every moving image submitter. If a summary value of the potential viewing frequency indexes of all moving image contributors who have applied exceeds the lower limit value of the potential viewing frequency index about the request, application information which is sent thereafter is not recorded in the item management file 23.SELECTED DRAWING: Figure 1

Description

The invention of this application relates to a system that supports a business that earns advertising revenue by producing a corporate tie-up video and posting it on a video sharing site.

The spread of video sharing services on the Internet in recent years is eye-opening. It is said that the number of viewers of famous video distribution sites worldwide is 2 billion, and the number of views of the videos that attracted attention has reached billions, and some of them have exceeded 10 billion. A proud video is also posted.
It goes without saying that the background to the spread of video sharing services is linked to corporate advertising activities. In-stream advertisements and overlay advertisements are known for linked advertisements in video sharing services, but many people post videos because the advertisement fee is paid to the video poster according to the number of times the video is viewed. From that, a video with an amazing number of views will be born.

JP-A-2015-090509

Focusing on the high exposure capacity of such video sharing sites, new movements are emerging on the corporate side as well. One of them is the distribution of corporate tie-up videos. Corporate tie-up video distribution is a video distribution in which a popular video contributor asks a company to produce a video and posts it. When making a request, ask them to produce a video in relation to the product or service to be advertised, such as having them produce a video using the product to be advertised. Then, by posting such a video and viewing it by many people, a large advertising effect can be expected for the product or service.
In the case of corporate tie-up videos, the video contributor is paid at the time of request (or at the time of posting the video), and is also paid according to the number of times the video is viewed, making it a very attractive activity. There is.

However, the current situation is that requests for corporate tie-up video sharing are limited to a handful of super popular video contributors who have a large number of subscribers or followers. For this reason, no matter how attractive corporate tie-up videos are, video contributors who do not have such a large number of subscribers or followers will not be able to win requests for corporate tie-up videos and will be rewarded. I'm not blessed with a chance to get it.
The invention of the present application was made to solve the above-mentioned problems in corporate tie-up video sharing as video sharing linked to corporate advertisements, and a video that can be expected to be viewed to some extent even if it is not a very popular video contributor. The aim is to provide a technical means for posters to have the opportunity to win requests for corporate tie-up videos.

In order to solve the above problems, a corporate tie-up video sharing request acquisition support system is disclosed in this specification. This support system is a system used when a plurality of video contributors acquire a corporate tie-up video sharing request. This support system is equipped with a support server that accepts access from the poster terminal, which is a terminal operated by each video poster who continuously posts videos to video sharing sites on the Internet, and a storage unit. ..
In the storage unit, a poster information file that records the potential viewing frequency index, which is an index related to the number of times that a video can be viewed when posted, is recorded for each video contributor, and the production and posting of corporate tie-up videos. A request information file that records information about the request and a project management file that records information about the application from the video contributor regarding the production and posting request of the company tie-up video are stored.
The support server sends an application page to the poster terminal that can send application information that is information that each video poster applies for the request for the production and posting of corporate tie-up videos. It is a server that can be viewed, and the application information includes information that can identify the video poster.
In the request information file, the lower limit of the potential viewing frequency index required by the company for one request for the production and posting of the company tie-up video is recorded, and the plurality of applications for the request are recorded. The index aggregate value, which is the total of the potential viewing frequency indexes of the video contributors, is recorded.
The support server is equipped with an application registration program that records the application information in the project management file when the application information is sent from the application page. The application registration program obtains the potential viewing frequency index of the video contributor related to the sent application information from the poster information file, and obtains the index aggregate value for the request related to the application information from the request information file. It is a program that updates the index total value by adding It is a program that does not.
In addition, in this corporate tie-up video sharing request acquisition support system, the application registration program will send application information after the updated index aggregate value exceeds the index upper limit value that is increased by adding the index lower limit value. It may be a program that does not record in the matter management file.
In addition, in this corporate tie-up video sharing request acquisition support system, the email address of each video contributor is recorded in the poster information file, and the support server receives a request to create and post a corporate tie-up video. At that time, a request notification e-mail sending program is implemented to send an e-mail containing the request and the access information to the application page for the request to each e-mail address recorded in the poster information file. Can have the configuration of being.
In addition, in this corporate tie-up video sharing request acquisition support system, the potential viewing frequency index is the number of views of videos produced and posted in the past by each video contributor in a predetermined period, or each video contributor It can be the number of viewers who have set the video produced and posted to be viewed preferentially.
In addition, in this company tie-up video sharing request acquisition system, the actual number of views of each video after each video poster who applied creates a video and posts it on the video sharing site is recorded in the matter management file. For the support server or the management terminal that can access the support server, the total advertising fee paid or paid by the company is apportioned to each video contributor according to the number of views recorded in the matter management file. It is possible to have a configuration in which a reward calculation program for calculating each reward amount is implemented.

As explained below, according to the company tie-up video sharing request acquisition support system related to the disclosed invention, multiple video contributors are notified of the tie-up video sharing request from the company side, and multiple videos. Even if you're not a particularly popular video contributor, you don't have to be a corporate tie because you're allowing contributors to win the request and the total potential views index of those video contributors to meet the demands of the company. You can get a request to share up videos and participate in it, and you can receive rewards for it.
For companies as well, since multiple video contributors create and post tie-up videos for the same advertising target, the risk that the number of views will be less than expected is reduced by dispersion. In addition, as for the trouble of requesting, it is only necessary to request the operator, and it is not necessary to directly request each video contributor, so that the convenience is not lacking.
In the configuration where an e-mail containing the request and the access information to the application page is sent to each poster terminal when there is a request for production and posting of a corporate tie-up video, each video poster applies. It is suitable because it is less likely to forget to do it and it will be easier to access the application page.
In addition, in a configuration in which a reward calculation program is implemented that calculates the reward paid to each video poster proportionally according to the number of views of each video, it is possible to pay each video poster fairly and easily. Will be.

It is a schematic diagram of the enterprise tie-up video sharing request acquisition support system of an embodiment. It is a schematic diagram which showed an example of the structure of a poster information file. It is a schematic diagram which showed an example of the structure of a request information file. It is a schematic diagram which showed an example of the structure of the matter management file. It is a schematic diagram which showed an example of the request notification mail sent to each poster terminal by the request notification mail sending program. It is a flowchart which showed the outline of the request notification mail sending program. It is a schematic diagram which showed an example of the application page accessed from the request notification mail as shown in FIG. It is a flowchart which showed the outline of the application registration program. It is a schematic diagram which showed an example of the application acceptance confirmation email sent by the application acceptance confirmation email transmission program. It is a flowchart which showed the outline of the viewing count monitor program. It is a schematic diagram which showed an example of the report produced by a reporting program.

Next, an embodiment (embodiment) for carrying out the invention of this application will be described.
FIG. 1 is a schematic diagram of a corporate tie-up video sharing request acquisition support system according to an embodiment. The corporate tie-up video sharing request acquisition support system shown in FIG. 1 is a system used when a plurality of video contributors acquire a corporate tie-up video sharing request. A corporate tie-up video is a video produced by a company for advertising purposes, and the content of the video is usually associated with the product or service to be advertised. A corporate tie-up video sharing request is a request to create such a video and post it on a video posting site. In this specification, "sharing" of a video means posting the video to the video sharing site and distributing it from the video sharing site (delivering to the server of the video sharing site).

The corporate tie-up video sharing request acquisition support system (hereinafter, abbreviated as a support system) of the embodiment includes a support server 1 and a storage unit 2 as shown in FIG.
The support server 1 is a server on the Internet 9 and is a server (web server) that hosts various web pages. The support server 1 is scheduled to be accessed from a terminal (hereinafter referred to as a poster terminal) 3 operated by each video poster who continuously posts videos to a video sharing site on the Internet 9. Has been done. "Video contributor who continuously posts a video" means a video contributor who has a considerable number of people who continuously watch the video, such as followers and subscribers.

The storage unit 2 is a storage device such as a hard disk provided in the support server 1. However, the storage unit 2 may be a storage device on a computer provided separately from the support server 1, or may be a storage device on a server provided separately from the support server 1 such as a storage server. Is also good.
The support system of the embodiment is operated by a business operator whose business is to mediate between each video contributor and a company requesting corporate tie-up video sharing. Hereinafter, this business operator is referred to as an operating business operator. As shown in FIG. 1, the operator is provided with a management terminal 4 operated by a person in charge. It is assumed that the management terminal 4 accesses the support server 1 with a special access authority.
In FIG. 1, the support server 1 is drawn like an in-house server of an operator, but this is an example, and the support server 1 is outside the company as in the case of using an external hosting service. It may be placed in. Further, the management terminal 4 may also be connected to the support server 1 via the Internet 9 in addition to the case where the management terminal 4 is connected to the support server 1 via the operator's in-house LAN.

The poster information file 21 is stored in the storage unit 2. The contributor information file 21 is a database file in which persons who are permitted to use the support system of the embodiment when acquiring a corporate tie-up video sharing request are registered. FIG. 2 is a schematic diagram showing an example of the structure of the poster information file 21.
The main purpose of the poster information file 21 is to evaluate and record the ability of each video poster who applies for a corporate tie-up video sharing request in advance. The ability of a video contributor is simply how many views the video contributor has after posting the video, and is an index of the potential number of views of the video (potential view count index). Is.

As a potential viewing frequency index, the first thing that can be considered is the past performance of the video contributor, that is, the viewing frequency of the video posted in the past. In this case, since the latest number of views more accurately reflects the ability of the video contributor, the number of views in the most recent predetermined period such as the past week or the past month (hereinafter referred to as the latest number of views) is potential. It is preferable as a frequency index.
From another point of view, the potential view count index is a name index such as the number of subscribers or the number of followers. These indicators are the number of users who are automatically notified when the video contributor posts a new video, and are the number of users who are paying attention to the video contributor (hereinafter referred to as the number of attention). ..

In this embodiment, each of these potential viewing frequency indexes is recorded in the poster information file 21. Specifically, as shown in FIG. 2, the poster information file 21 has a "poster ID", a "password", a "handle name", a "responsible person's name", a "responsible person's address", and a "person in charge". It is a database file in which records including fields such as "phone number", "poster email address", "latent index 1", and "latent index 2" are recorded.
The "poster ID" is an ID for uniquely identifying the video poster in the support system.
The "handle name" is a handle name when posting to a video sharing site, and a channel subscriber or a follower registers a channel or a follower for this post handle name.

The "name of the person in charge" is a field in which the name of the person in charge of the person who obtains the corporate tie-up video sharing request is recorded by this support system. If the contributor is an individual, the real name of the person posting with the post handle name is the name of the person in charge here. When a video is produced and posted in a certain group or organization, it is the name (real name) of the person in charge (leader) in that group or the like. The "responsible address" is a field in which the address of such a responsible person is recorded. The "poster email address" is a field in which an email address for contacting the poster is recorded.

The "latent index 1" is a field in which the most recent viewing count is recorded, for example, a field in which the viewing count in the past month is recorded. The "latent index 2" is a field in which the number of attention is recorded, and is a field in which the number of users notified when a new post is made, such as the number of subscribers and the number of followers, is recorded.
In addition, the poster information file 21 also records information on a bank account for receiving a reward for sharing a corporate tie-up video.

When there is an application from each video contributor, such a contributor information file 21 is recorded in the contributor information file 21 and registered after being examined by the operator. The person in charge accesses the support server 1 using the management terminal 4, adds a new record to the poster information file 21 on the storage unit 2, and records each of the above information. The potential viewing frequency index will be recorded after confirming the declaration from the applicant (poster who wants to register) on the video sharing site. That is, the registration is performed after collating with the official data (number of views, number of registered channels, etc.) published by the video sharing site. If it is incorrect, correct it with the official data of the video sharing site before registering.

The operator solicits registration from many video contributors, asks them to apply, and after screening, registers as described above. The application may be made on the website using the support server 1, or it may be filled out in writing and made by mail. In either case, if you are an individual, you will be asked to send a resident's card, etc., if you are a corporation, you will be asked to send a copy of the registry, etc., and you will be registered while properly verifying your identity.

Further, the storage unit 2 records a request information file 22 which is a database file for managing solicitations for projects requested by each company (company tie-up video sharing request). FIG. 3 is a schematic diagram showing an example of the structure of the request information file 22.
As shown in FIG. 3, the request information file 22 includes a "request ID", a "company name", an "advertisement target name", a "posting deadline", an "index lower limit", an "index upper limit", and a "recruitment start date". , "Application deadline", "Number of applicants", "Index tabulation", "Recruitment cutoff date" and other fields.
The "request ID" is an ID given once for each tie-up video sharing request from each company, and is an ID that uniquely identifies each record of the request information file 22.
The "company name" is a field in which the name of the company that made each request is recorded, and the "advertisement target name" is a field in which the name of the product or service to be advertised is recorded.
The "posting deadline" is a field for recording the deadline for posting a corporate tie-up video to a video sharing site, and each video contributor who applied and received a request is obliged to post the video by this date.

The "index lower limit value" is a field in which the lower limit value of the potential viewing frequency index within a predetermined period is input for the request. This value is usually a request from the requesting company. For example, when an index that the minimum number of views in one month is 300,000 is required, the numerical value of "300000" is recorded in the "index lower limit". In this case, the period in the "latent index 1" in the poster information file 21 is the same as the period in the "index lower limit". In other words, in the poster information file 21, when the potential viewing frequency index is set on a monthly basis, the lower limit is set based on how many views are desired on a monthly basis even for requests from companies. Ask them to present it and record it in the "lower limit of index".

The "index upper limit value" is the value of the index when the recruitment is terminated. As will be described later, in the support system of the embodiment, a configuration is adopted in which the recruitment is terminated when the total of the potential viewing frequency indexes of all the video contributors who participated in the recruitment reaches a certain value. The value at the time of this censoring is the "index upper limit value". As for the index upper limit value, the period within the predetermined period in the potential viewing frequency index is the same as the period in the “potential index 1” of the poster information file 21.

In the "recruitment start date", the date when the recruitment is started, that is, the date when the request notification email is sent is recorded. The "application deadline" records the deadline for application. The tie-up video sharing request from the company includes the video distribution start deadline (posting deadline) as the request content, and the application deadline is decided and recorded in consideration of the number of days of video production etc. by calculating back from this. To.
"Number of applicants" is a field in which the total number of applicants at that time is recorded, and "Index tabulation" is a potential viewing count index of all applicants at that time (in this example, the most recent viewing count). The field in which the total is recorded. The "recruitment discontinuation date" is a field in which the date on which the recruitment discontinuation was performed is recorded.

When such a request information file 22 is requested to share a corporate tie-up video, a person in charge of the operator operates the management terminal 4 to input the request information file 22 and records the value of each field. The support server 1 (may be the management terminal 4) is equipped with a request registration program 19 for adding a new record to the request information file 22. The request registration program 19 includes a code for automatically generating a request ID, and records the generated request ID in the "request ID". That is, every time there is a new request, a new request ID is generated and recorded in a new record of the application status file.

Further, the storage unit 2 stores a management file (hereinafter referred to as a matter management file) 23 created for each company tie-up video sharing request. FIG. 4 is a schematic diagram showing an example of the structure of the matter management file 23.
The matter management file 23 is created in a state of being associated with the request ID by, for example, using a file name using the request ID. The request information file 22 may be provided with a field in which the file name of the matter management file 23 is recorded.

As shown in FIG. 4, the matter management file 23 includes "participating poster ID", "participating poster handle name", "latent index 1", "application acceptance date", "confirmation contact date", and "video URL". , "Current number of views", "Compliance confirmation date", "Last number of views" and the like.
The "participating contributor ID" is a field in which the contributor ID of the contributor who applied for and registered the request among the video contributors is recorded. In the matter management file 23, one record is recorded for one participating contributor, and each record is identified by the contributor ID.
The "participating contributor handle name" is the handle name of the contributor related to the contributor ID, and the "latent index 1" is the most recent viewing count related to the contributor, and the value in the contributor information file 21 is posted.

The "application acceptance date" is recorded as the date when the poster applied for the request. The "confirmation contact date" is the date when the operator contacts the poster to confirm the acceptance of the application for the video sharing request.
The "video URL" is a field in which the URL of the posted video is recorded, and the "current number of views" is a field in which the number of views of the video is recorded, and is updated regularly. The "Compliance Confirmation Date" is a field where the date when the operator confirms the compliance etc. of the posted video is entered, and the "Final View Count" is the final when the aggregation is discontinued at a certain time. This is a field in which the number of times a video is viewed is recorded.

On the other hand, the support server 1 is a server that provides an application page capable of transmitting application information, which is information to the effect that a video poster applies for a corporate tie-up video sharing request. The application page is a page that can be viewed only by the poster registered in the poster information file 21. In this embodiment, when there is a request for sharing a corporate tie-up video, each video contributor is notified by e-mail, and the support server 1 has this electronic device for each contributor terminal 3. A request notification mail sending program 191 for sending a mail (hereinafter referred to as a request notification mail) is implemented.

FIG. 5 is a schematic diagram showing an example of a request notification email sent to each poster terminal 3 by the request notification email transmission program 191.
As shown in FIG. 5, the request notification mail includes the name of the company that requested the company tie-up video sharing, the name of the product or service to be advertised, the application deadline, the video posting deadline, and the like. At the same time, the request notification email incorporates a code (application page display code) for displaying the application page provided by the support server 1. In this example, the application page display code is an execution code of the application page display program 18 implemented in the support server 1, and is a hyperlink 51 in which a request ID and a poster ID are incorporated.

FIG. 6 is a flowchart showing an outline of the request notification mail transmission program 191. The request notification mail transmission program 191 is executed as a subroutine of the request registration program 19 that records the above-mentioned new request in the request information file 22. At this time, the generated request ID is passed as an argument to the request notification mail transmission program 191.
As shown in FIG. 6, the request notification mail transmission program 191 acquires the poster ID and the email address from each record of the poster information file 21. Then, the request information file 22 is searched by the request ID to acquire the "company name", the "advertisement target name", etc., and these are incorporated into the mail template to generate the request notification mail. At this time, the request notification mail transmission program 191 incorporates the request ID and the poster ID to generate an application page display code. In this example, the code for executing the application page display program 18 with the request ID and the poster ID as arguments is generated as the hyperlink 51. Then, as shown in FIG. 5, it is incorporated in the request notification email and sent to the acquired email address. When the above processing is performed for all the records of the poster information file 21, the request notification mail transmission program 191 is terminated.

FIG. 7 is a schematic diagram showing an example of an application page accessed from a request notification email as shown in FIG. When the hyperlink 51 shown in FIG. 5 is pressed, a page for entering the password is displayed (the poster ID is displayed by default as the one passed as an argument), where the password is correctly entered and the send button is pressed. Then, the user is logged in, and the application page as shown in FIG. 7 is displayed on the poster terminal 3. At this time, the poster ID and the request ID are held in the environment variables.

The application page display program 18 searches for the request information file 22 by the request ID, acquires each information, and incorporates it into the application page. Therefore, as shown in FIG. 5, on the application page, the content notified by the request notification email (company name, advertisement target name, application deadline, video posting deadline, etc.) is displayed confirmively. In addition, there may be comments from the company when making a request, which may also be displayed. The comment is, for example, the purpose and purpose of the advertisement, and an example of preferable content as a tie-up video.

Further, as shown in FIG. 7, the handle name, the name of the person in charge, and the like of the poster are displayed on the application page for confirmation. The application page display program 18 searches for the poster information file 21 by the poster ID, acquires and displays this information.
As shown in FIG. 7, the application page is provided with an application button 52. On the other hand, the application registration program 11 is implemented in the support server 1. The application button 52 is linked to a page that displays a confirmation message such as "I am applying for this company tie-up video sharing request. Are you sure?", And the OK button provided on this page is supportive. It is an execution button of the application registration program 11 on the server 1.

FIG. 8 is a flowchart showing an outline of the application registration program 11.
As described above, the application registration program 11 is executed when the application button 52 is pressed on the application page and the OK button is pressed on the confirmation page. The application registration program 11 first acquires the request ID held at the time of login and searches the request information file 22. Then, it is determined whether or not the "recruitment cutoff date" of the corresponding record is the Null value. If it is not the Null value, the recruitment has been terminated, so an error message to that effect is sent to the poster terminal 3 and the program is terminated.

If the "recruitment cutoff date" is a Null value, the application registration program 11 acquires the poster ID held at the time of login and searches the poster information file 21 by the poster ID. Then, the value (most recent viewing count) of the field of the "latent index 1" of the corresponding record is acquired, and the value of the "index aggregation" of the relevant record of the request information file 22 is acquired. Add these two values and determine if they exceed the "index upper limit". If it exceeds, the execution date of the program is recorded in the "recruitment cutoff date" of the request information file 22. In both cases where the value is not exceeded and the value is exceeded, the application registration program 11 records the added value in the field of "index aggregation". In addition, a new record is added to the matter information file, and the poster ID, handle name, latest viewing count, application acceptance date, etc. are recorded. Then, the application acceptance confirmation mail sending program 12 is executed with the request ID and the poster ID as arguments.

FIG. 9 is a schematic diagram showing an example of an application acceptance confirmation email sent by the application acceptance confirmation email transmission program.
As shown in FIG. 9, the application acceptance confirmation email states that the application has been accepted and that the request for sharing the corporate tie-up video has been made as one of the request destinations (the request has been obtained). At the same time, the deadline for posting videos, compliance and other conditions to be observed as corporate advertisements are described.
The support server 1 is equipped with a video URL registration program 13 for registering the URL of the posted video. As shown in FIG. 9, the execution code (hyperlink in this example) 53 of the video URL registration program 13 is embedded in the application acceptance confirmation email.

The video URL registration program 13 is a program that displays a page for inputting a video URL after logging in on the poster terminal 3 and records the URL input there in the matter management file 23. That is, the execution code includes the request ID, the matter management file 23 of the corresponding request is searched by the poster ID by the request ID, and the URL input to the "video URL" of the corresponding record is recorded. It is programmed.

The support server 1 is equipped with a censored mail transmission program 14. In the application registration program 11, when the execution date of the program is recorded in the "recruitment cutoff date" because the value of the "index total" added to the number of recent views exceeds the "index upper limit", a cutoff notification email is sent as a subroutine. The censored mail transmission program 14 to be transmitted to each poster terminal 3 is executed. The discontinuation notification email is an email stating that the application will be discontinued because the expected number of views by the video contributor who applied has exceeded the schedule.

In such a support system, the support server 1 has a viewing count monitoring program 15 that sequentially grasps the viewing counts of videos produced and posted based on requests and records them in the matter management file 23 and the request information file 22. It has been implemented.
FIG. 10 is a flowchart showing an outline of the viewing frequency monitoring program 15. The viewing count monitoring program 15 is a file that is automatically executed periodically, for example, once a day. For example, it is automatically executed at midnight every day.

The viewing count monitoring program 15 is executed for each matter management file 23. As shown in FIG. 10, the viewing count monitoring program 15 opens the request information file 22 and acquires the value of the "request ID" of the first record. Then, the matter management file 23 corresponding to it is opened, and the value of the "video URL" of the first record is acquired. If this value is not a Null value, a subroutine (view count acquisition module) for acquiring the number of views is executed at the URL.
In this embodiment, the video sharing site on which the corporate tie-up video is posted is limited to one specific site. Many video sharing sites publish a code to get the number of views (the number of views at that time) of the posted video. Therefore, the viewing count acquisition module is coded to acquire the viewing count using a publicly available code.

When the return value (view count) is returned from the viewing count acquisition module, the viewing count monitoring program 15 overwrites the return value with the "current viewing count" of the record in the matter management file 23 and records it. Then, the process is repeated in the same manner for the next record of the matter management file 23. After finishing the processing for the last record of the matter management file 23, the viewing count monitoring program 15 updates the value of the "final viewing count" of the request information file 22 for the matter. That is, the value of the "current number of views" of each record in the matter information file is added one after another to obtain the total number of views, and the total number of views is overwritten with the "final number of views" of the request information file 22 and recorded. do.

Next, the viewing count acquisition module repeats the process in the same manner for the next record of the request information file 22. That is, the "request ID" of the next record is read, and the corresponding matter management file 23 is opened. Then, similarly, the "video URL" is acquired in each record, and if it is not the Null value, the viewing count acquisition module is executed and the return value is recorded in the "current viewing count". When the processing up to the last record is completed, the "current number of views" of each record is totaled for the matter information file, and the "last number of views" of the corresponding record of the request information file 22 is updated. When the processing for all the records in the request information file 22 is completed, the viewing count monitoring program 15 is finished.

The support server 1 is equipped with a reporting program 16 for collectively reporting the results of the company tie-up video sharing request executed by each contributor to the requesting company. FIG. 11 is a schematic diagram showing an example of a report created by the reporting program (hereinafter referred to as a video sharing project report).
As shown in FIG. 11, in the video sharing project report, the name of the company that made the request and the name of the advertisement target are described for confirmation, and the release period of the tie-up video is described. The release period is the period from the video release date specified by the company to the execution date of the reporting program 16. Alternatively, if the publication period is specified by the company, the report will be created by dividing it by that period, so that period will be described.
Then, as shown in FIG. 11, in the video sharing project report, the handle name of each video poster who obtained the request and posted the video, the URL of the posted video, and the final number of views are described in a list state. Has been done. On top of that, the final total number of views is described. It goes without saying that this number is the overall advertising performance.

The reporting program 16 is executed by access from the management terminal 4 at an appropriate time. The management terminal 4 is equipped with a request search program that searches the request information file 22 by inputting a company name or an advertisement target name and acquires a request ID. Then, by executing the report program 16 with the request ID as an argument, a video sharing project report as shown in FIG. 11 is created. The reporting program 16 searches for the request information file 22 by the request ID, acquires the company name, the advertisement target name, etc. from the corresponding record, opens the corresponding matter management file 23, and opens the "handle name" and "handle name" of each record. Acquire each value of "video URL" and "current number of views". Then, the list is displayed as shown in FIG. Then, the total value of the "current number of views" is calculated and described as the final total number of views. The reporting program 16 creates and terminates such a video sharing project report in a PDF-like file format.

A program (hereinafter referred to as a reward calculation program) 17 for calculating a payment reward for each video poster who applied for one company tie-up video sharing request is implemented in the support server 1 or the management terminal 4. ing. This point will be described below.
The reward for each video contributor depends on how the company pays the reward to the operator. That is, there may be a fixed type and a success fee type in how the remuneration is paid from the company to the operator. The former is a case where a fixed amount is paid regardless of the actual number of views. Even in this case, it is often a condition that the lower limit of the number of viewings is cleared. The latter is the case where the reward is paid according to the number of views. The number of views in this case is the final number of views (final total number of views) of all posted videos.

First, the remuneration calculation program 17 in the fixed type will be described. The remuneration calculation program 17 first deducts the amount of the fee obtained by the operator for the remuneration paid by the company, and the remaining amount is according to the final number of views. It is programmed to be distributed to each video contributor. That is, the ratio of the final viewing times of each video to the final total viewing times is calculated, and the reward after deducting the commission is multiplied by this ratio to calculate the reward of each video contributor.
In the case of the success fee type, when submitting the above video sharing project report to the company side, the operator issues an invoice to the company side based on the final total number of views, and the company side pays based on this. Will be paid. In this case as well, the reward calculation program 17 calculates the ratio of the final number of views of each video to the final total number of views after deducting the fee of the operator, and multiplies this ratio by the amount after deducting the fee. It is programmed to calculate the rewards for video contributors.

The overall operation of the support system of the embodiment according to the above configuration will be described below.
The operator invites video contributors who regularly post videos on video sharing sites to register for the support system. The video contributor who responds to this will send the application form to the operator, and after examination, it will be registered. That is, the poster information is recorded in the poster information file 21. Many video contributors seeking rewards for posting corporate tie-up videos apply and are registered after review.

On the other hand, the operator explains to each company about corporate tie-up video sharing and invites them to use it. A company that responds to this request the operator to advertise its products or services by sharing company tie-up videos. At this time, the product or service to be advertised and what kind of video is desirable will be explained. In addition, inform the operator about the required lower limit of the number of views, the period of time, and the rewards that are ready to be paid. The person in charge of the operator operates the management terminal 4 based on the request and executes the request registration program. As a result, a new record is added to the request information file 22, each information is recorded, and the request notification mail transmission program 191 is executed as a subroutine. As a result, the request notification mail as shown in FIG. 5 is transmitted to the poster terminal 3 of each video poster (registered video poster). Further, the matter management file 23 is newly generated in a form corresponding to the request ID and stored in the storage unit 2.

Each video contributor looks at the request notification email and considers whether to apply. This review includes considering whether your audience is suitable for the product or service being advertised. For example, if the viewers of the video you are posting are mainly housewives, it is difficult to increase the number of views for the male cosmetics company tie-up video sharing request, and it is judged that it is not suitable. Is. If it is judged that the number of views can be increased to some extent, the video poster decides to accept the recruitment, executes the application page display code in the request notification email, and displays the application page on the poster terminal 3. do.

After reconfirming the recruitment contents on the application page, the video contributor presses the application button 52 and presses the OK button on the confirmation page to cause the support server 1 to execute the application registration program 11. The application registration program 11 adds a new record to the matter management file 23, and records the poster ID, the number of recent views, the number of attention, and the like. In addition, the latest viewing count of the poster is added to the value of the "index total" of the record in the request information file 22 and updated.

In this way, a plurality of video contributors apply, their information is recorded in the matter management file 23, and the value of the "index tabulation" of the request information file 22 is added. Then, when the value of the "index total" exceeds the "index lower limit value", the application registration program 11 records the program execution date in the "application cutoff date" of the request information file 22. Then, as a subroutine, the cutoff mail sending program 14 is executed.

An application acceptance confirmation email will be sent to each video contributor who applied. Each video contributor confirms each necessary condition such as video posting deadline and compliance, and starts video production. Then, when the video is complete, post it on the video sharing site. Then, the poster terminal 3 accesses the support server 1, executes the video URL registration program 13, and records the URL of the posted video in the corresponding record of the matter management file 23.

On the other hand, the operator actually watches and confirms the posted video, and checks whether there is a problem from the viewpoint of compliance and the like. Then, if there is a problem, it will notify the video poster who posted the video and request that the video be deleted from the video sharing site.
Further, the viewing count monitoring program 15 on the support server 1 is automatically executed periodically, and the viewing count of each moving image is acquired and recorded in each record of the matter management file 23. Then, the total of them is overwritten with the "final viewing count" of the corresponding record of the request information file 22.

In this way, each company's tie-up video is shared on the video sharing site during a predetermined release period, and each viewer watches it. When the publication period has passed, the person in charge of the operator operates the management terminal 4 and executes the reporting program 16. As a result, a video sharing project report as shown in FIG. 11 is created. The release period is a period for tabulation, and each video after the release period is posted on the video sharing site and can be viewed.
The operator sends the video sharing project report to the company and charges the reward. When the reward is paid from the company side, the reward calculation program 17 calculates the reward proportionally according to the number of final views, and pays the reward to each video contributor.

According to the support system of such an embodiment, a request for sharing a tie-up video from the company side is notified to a plurality of video contributors so that the multiple video contributors can acquire the request. Since the total of the potential viewing frequency indicators of those video contributors meets the demands of companies, it is possible to win and participate in corporate tie-up video sharing requests even if you are not a particularly popular video contributor. You can and you will be rewarded for it.

It's easier and more reliable for companies to ask a particularly popular video contributor (or a group), but that video contributor may not always get a lot of views. , There is no guarantee that the requirements will be met. On the other hand, when the support system of the embodiment is used, since a plurality of video contributors each produce and post a tie-up video for the same advertisement target, the risk that the number of views will be less than expected is reduced by dispersion. In addition, as for the trouble of requesting, it is only necessary to request the operator, and it is not necessary to directly request each video contributor, so that the convenience is not lacking.

Further, in the above embodiment, a value exceeding the index upper limit value required by the company is set as the index upper limit value, and recruitment is continued until the index upper limit value is exceeded, so that there is a risk that the number of views will be less than the expected total number of views. Can be reduced. As for how much the index upper limit value should be larger than the index lower limit value, it can be increased by, for example, 30%. For example, if the request from the company side is 300,000 views in one month, the total number of recent views (in this example, the number of views in the last month) of the video contributor who applied will be 390,000 views. The recruitment will be continued until 390,000 views, and the recruitment will be terminated. Of course, it may be increased by 10% or 20%.

Further, in this embodiment, a request notification email including the request to share the corporate tie-up video and the hyperlink 51 to the application page is sent to each poster terminal 3. It is suitable because it is less likely that each video contributor forgets to apply and access to the application page becomes easier. As the access information other than the hyperlink 51, the URL of the application page may be simply described. In addition, the URL of the login page may be described or the hyperlink of the login page may be embedded.
Furthermore, since the reward calculation program 17 that calculates the reward paid to each video poster by proportionally dividing it according to the number of views of each video is implemented, it is possible to pay each video poster fairly and easily. ..

It should be noted that although there may be a configuration in which recruitment is continued indefinitely, there is a problem that management becomes complicated. That is, if the recruitment is unlimited, the number of potential views increases, and a larger number of views can be expected, but the number of video contributors increases accordingly. This means that the number of videos to be monitored at the same time increases, and it means that more labor such as compliance check is required. Therefore, it is preferable to discontinue the recruitment at some point.
Further, in the above-described embodiment, if the number of recent viewings is below the index upper limit value when the recruitment period has elapsed, the recruitment may be extended. In this case, a program for sending a notification mail to the effect that the recruitment has been extended to each poster terminal 3 is implemented in the support server 1. However, when the recruitment period has elapsed, if the number of recent views exceeds the lower limit of the index, the recruitment may not be extended.

In the above embodiment, among the potential viewing frequency indexes recorded in the poster information file 21, the latest viewing frequency is totaled and it is determined whether or not the index lower limit value is exceeded. This is because the company has issued a request for a lower limit value from the viewpoint of the number of views. As a request from the company side, the total of the attention of each video contributor (for example, the number of registered channels) may be given as the request value. In this case, the number of attention of the video contributor who applied (posting). The value of the "latent index 2" of the person information file 21) is totaled, and the recruitment is terminated when the required value is sufficiently exceeded (for example, 30% increase).

Furthermore, recruitment may continue until both the number of recent views and the number of attention are exceeded the upper limit of the index. If the company makes a request based on the number of views, the operator estimates the total number of attention required in addition to the total number of recent views, sets this separately as the upper limit of viewing, and recruits until it exceeds this. You may try to continue. This is preferable because it increases the possibility of actually satisfying the demands of the company.

The number of recent views and the number of attention recorded in the poster information file 21 are updated periodically. Regarding the number of recent views, the number of recent views of videos freely produced and posted by the video contributors other than corporate tie-up videos is regularly monitored and updated. However, you may record the number of views of the company tie-up video and use it when applying for the next time or later. In addition, the number of attention is also monitored regularly and the value is updated. For these update work, the operator checks the report from each video contributor, or implements a program to access the video sharing site and automatically acquire it on the support server 1.

In the above embodiment, only video contributors whose potential viewing frequency index is equal to or higher than a certain value may be registered in the contributor information file 21. If you register even video contributors who have too few recent views or too few channel registrations, the number of registered video contributors will be enormous, and management will become complicated. Therefore, only video contributors who have a certain number of potential views may be registered.
It should be noted that a configuration may be adopted in which a video contributor who has a problem in terms of compliance or other viewpoints is deleted from the contributor information file 21 so that the next and subsequent requests are not notified.

Further, in the above embodiment, the technical configuration for discontinuing the recruitment is such that the recruitment termination date is recorded in the request information file 22 and the application registration program refers to it, but there are other configurations as well. obtain. For example, the application page display program 18 may refer to the value in the field of "recruitment cutoff date", and if it is not a Null value, the application page may not be displayed on the poster terminal 3.

The above description is based on the assumption that a plurality of video contributors post corporate tie-up videos only on one specific video sharing site, but the present invention relates to a plurality of different video sharing sites. It is possible to post a corporate tie-up video. In this case, one (or one group) video contributor may post to two or more different video sharing sites, a video contributor A posts to a video sharing site X, and a video contributor B. May post to a video sharing site called Y. Even in these cases, the viewing count monitoring program 15 monitors and totals the number of viewings of moving images on each site. If the same video is posted on different video sharing sites, their views are totaled.

1 Support server 11 Application registration program 14 View count monitoring program 2 Storage unit 21 Poster information file 22 Request information file 23 Matter management file 3 Poster terminal 4 Management terminal 51 Hyperlink 52 Application button 9 Internet

Claims (5)

Corporate tie-up video sharing request acquisition support used when multiple video contributors acquire one request for corporate tie-up video sharing, which is a request for a company to produce a video for advertising purposes and post it on a video sharing site. It ’s a system,
A support server that accepts access from each poster terminal, which is a terminal operated by each video poster who continuously posts videos to video sharing sites on the Internet.
Equipped with a storage unit,
In the storage unit, a poster information file that records the potential viewing frequency index, which is an index related to the number of times that a video can be viewed when posted, is recorded for each video contributor, and the production and posting of corporate tie-up videos. A request information file that records information about the request and a project management file that records information about the application from the video contributor regarding the production and posting request of the company tie-up video are stored.
The support server sends an application page to each poster terminal that can send application information that is information that the video poster applies for the request for the production and posting of corporate tie-up videos. It is a server that can be viewed, and the application information contains information that can identify the video poster.
In the request information file, the lower limit of the potential viewing frequency index required by the company for one request for the production and posting of the company tie-up video is recorded, and the plurality of applications for the request are recorded. The index aggregate value, which is the total of the potential views index of the video contributor of
The support server is equipped with an application registration program that records the application information in the project management file when the application information is sent from the application page.
The application registration program obtains the potential viewing frequency index of the video contributor related to the sent application information from the poster information file, and obtains the index aggregate value for the request related to the application information from the request information file. It is a program that updates the index total value by adding A corporate tie-up video sharing request acquisition support system characterized by being a program that does not work. The application registration program does not record the application information in the project management file for the transmission of application information after the updated index aggregate value exceeds the index upper limit value obtained by adding the index lower limit value. The company tie-up video sharing request acquisition support system according to claim 1, which is characterized by being a program. The e-mail address of each video contributor is recorded in the contributor information file.
When a request for production and posting of a corporate tie-up video is made to the support server, the poster information file contains an e-mail containing the request and access information to the application page for the request. The company tie-up video sharing request acquisition support system according to claim 1 or 2, wherein a request notification e-mail sending program to be sent to each e-mail address recorded in is implemented. The potential viewing frequency index is the number of views of videos produced and posted by each video contributor in the past in a predetermined period, or videos produced and posted by each video contributor are preferentially viewed. The corporate tie-up video sharing request acquisition support system according to any one of claims 1 to 3, wherein the number of viewers is set to be the same. The actual number of views of each video after each video poster who applied has created the video and posted it on the video sharing site is recorded in the matter management file.
For the support server or the management terminal that can access the support server, the total advertising reward paid or paid by the company is apportioned to each video contributor according to the number of views recorded in the project management file. The company tie-up video sharing request acquisition support system according to any one of claims 1 to 4, wherein a reward calculation program for calculating each reward amount is implemented.

Images