WO2017217785A1

WO2017217785A1 - Server and method for providing performer object-based collaboration service

Info

Publication number: WO2017217785A1
Application number: PCT/KR2017/006248
Authority: WO
Inventors: 최윤호; 천솔지
Original assignee: (주)잼투고
Priority date: 2016-06-17
Filing date: 2017-06-15
Publication date: 2017-12-21
Also published as: KR101827978B1; KR20170142523A

Abstract

A server for providing a performer object-based collaboration service according to the present invention is characterized by comprising: a communication module for performing communication with a terminal through a network; a moving image contents providing module for transmitting moving image contents and web page data to the terminal, thereby providing a moving image contents service; a collaborator database for associating performer data with the moving image contents and storing the performer data, the performer data comprising a performer object identifier for identifying at least one performer object of the moving image contents, which is expressed on a screen, and performer contact information; a collaboration request receiving module for receiving a collaboration request regarding the performer object expressed in the moving image contents from a collaboration requester who reproduces the moving image contents with the terminal; a performer object identifying module for identifying the performer object identifier of the performer object through the collaborator database according to the collaboration request received by the collaboration request receiving module; a collaboration group generating module for registering a performer corresponding to the performer object identifier, which has been identified as a target of the collaboration request by the performer object identifying module, in a performance collaboration group of the collaboration requester; and a notification module for notifying the performer of receipt of the collaboration request through the performer contact information of the performer registered in the performance collaboration group of the collaboration requester.

Description

Performer object based collaboration service provision server and provision method

The present invention relates to a server and method for providing a collaboration object-based collaboration service, comprising: a performance-based collaboration service providing server capable of creating a collaboration group by designating a performer that is a collaboration target output in the video content during viewing of the video content; It relates to a providing method.

With the development of communication technology and the development of multimedia technology, various multimedia contents are produced and provided, and users' demand for the distribution and sharing of multimedia contents is also increasing. As demand for multimedia contents increases, the usage of multimedia contents is diversified, and the generation of personalized contents (UGC), which allows users to directly capture images and edit images, is being activated.

In particular, among the UGC, music-related multimedia contents such as music videos and audio sources are gaining wide popularity, and music social network services that provide use, sharing and distribution of music sources are emerging. For example, services such as band-page, sound cloud, and pandora provide a storage service for registering a user-generated sound source and distributing it to other users.

However, since the sound source generated by the individual is generally inferior in quality, it is desirable to increase the quality of the sound source through collaboration with other collaborators. Here, collaboration is called a collaboration, and when a musician who is a performer collaborates, a performer sings or plays music provided by a composer, a performer sings or plays, a producer produces a video content, and the like. can do.

Collaboration can improve the quality of music-related video content, but it is difficult to find suitable collaborators and complicated preparation procedures for collaboration. First, a user who wants to collaborate should search for various video contents to search for a performer who appeared in a favorite video content or a producer of the corresponding video content. However, most video content has only a title or information of surrounding performers such as artists, and there is a problem in that it cannot identify the session or producer of the video content.

Second, even when the performer corresponding to the desired session is identified, there is a problem in that the contact information of the performer and the existence of the cooperative doctor cannot be confirmed.

Third, even if a variety of collaborators such as performers, composers, songwriters, or producers, there is a problem that it is difficult to determine a practice schedule or a collaboration schedule reflecting the intention of a large number of personnel.

U.S. Patent No. 8,213,689, "Method and System for automated annotation of persons in video content," discloses a method of recognizing a face of a person in a video content and automatically annotating the name of the person in the video content. . According to the conventional technology, a user can obtain musician information simply by referring to a tag of video content without a separate searching procedure. However, in the related art, first, since only the name of the performer is tagged in the video content, there is a problem that it is difficult to search for the video content of the performer corresponding to the session (for example, piano, guitar, or saxophone) specified by the user.

Second, the prior art simply displays the name of the performer in the video content, there is a problem that the collaboration request through the contact information of the performer is impossible.

Inha University Korean Patent No. 964198 “Social Network Analysis System” discloses a system for recognizing a face included in a photograph and checking a social connection relationship between people recognized through an SNS system. According to the related art, it is possible to increase the probability of obtaining contact information of a desired performer through a social connection relationship between performers of image content or video content.

However, since the present technology only identifies the personal information and the social relationship of the first performer, there is still a problem that the session information of the performer cannot be confirmed. Second, the prior art still has a problem that the collaboration request through the contact information of the performer is still impossible if the social connection between the collaboration requester and the performer is not established in advance.

US Patent Publication No. 2010-0319518, "Systems and Methods for Collaborative Music Generation," by Virendra Kumar Metha, is a method for creating music content by allowing multiple performers to connect to a single website, playing selected music, and then mixing them later. Initiate. According to this method, many performers provide the effect of creating music contents through collaboration regardless of time and place. However, the prior art considers the convenience of collaboration between performers who have already been determined as collaborators, and the problem that the collaborative requester does not provide a method of searching for other performers that meet their needs and a method of requesting collaboration to the collaborators is required. have.

[Preceding technical literature]

(Patent Document 1) US Patent No. 8,213,689

(Patent Document 2) Korean Registered Patent No. 964198

(Patent Document 3) US Patent Publication No. 2010-0319518

In order to solve the above problems, the server and the method for providing a collaboration object based collaboration service according to the present invention, upon receiving a collaboration request from the collaboration requester playing the video content through the collaboration object identifier associated with the video content request By registering registered performers with the collaboration requester's performance collaboration group, we can improve the user-friendliness of adding the collaboration collaborator group and improve the efficiency of collaboration and organization by directly grasping the performance and reliability of the performer by watching videos without further searching. The purpose.

In accordance with an embodiment of the present invention, a server and a method for providing a collaboration service based on a collaboration object may notify a performer of receiving a collaboration request through the contact information associated with the video content according to the reception of the collaboration request, and accept the performer for the collaboration request. Alternatively, the object of the present invention is to enable immediate collaborative decision making through two-way communication by receiving rejection through the communication network, and to adaptively negotiate the schedule of the collaborator and the schedule of performers.

In accordance with an embodiment of the present invention, the server and method for providing a collaboration object-based collaboration service provide a producer who does not appear in a video content by registering as a collaboration target through a producer identifier and producer contact information to a performance collaboration group of a collaboration requester. In addition, other purposes are to improve the quality of video content by allowing producers who are not performers as well as video content performers to easily register with the cooperative group.

In accordance with an embodiment of the present invention, the server and method for providing a collaboration service based on the object are overlaid with a selection area for selecting a producer on the video content, thereby sharing only the video content to other web pages beyond the video content providing web page. Even if it is possible to send a collaboration request to the producer who is not a video content for another purpose.

In accordance with an embodiment of the present invention, a server and method for providing a collaboration service based on an object are intuitive to select a video region of a desired performer by a collaboration requester by associating a collaboration request execution object with a display region of a performer object included in video content. In this case, it is possible to select a collaborative target and to send a collaboration request to a performer, a video content performer, even if only the video content is shared on another web page.

In accordance with an embodiment of the present invention, a server and a method for providing a collaboration service based on a performance object may be configured to form a performance collaboration group by a collaborative requester. The purpose.

In accordance with an embodiment of the present invention, a server and method for providing a collaboration object-based collaboration service provide a collaboration requester setting conforming to a collaboration requester specifying a category of a performer who appeared in the video content when the collaboration requester designates a collaboration requester. By automatically placing them in the category slots, it is another goal that collaborators can be quickly and accurately assigned according to the collaborator request setting performing categories.

In accordance with an embodiment of the present invention, the server and method for providing a collaboration object-based collaboration service further store a performer registration performing category when registering a performer, and automatically set up a cooperative requestor setting performing according to a performer registration performing category when the collaboration requester is requested. By automatically placing in slots, the other goal is to allow collaborators to be assigned more quickly and accurately according to collaborator set-up performing categories.

In accordance with an embodiment of the present invention, the server and method for providing a collaboration object-based collaboration service provide various performers by recommending a video content including a performer registered performing category conforming to a collaboration requester according to the collaboration requester setting performing category of the collaboration requester. Another aim is to provide a unified and unambiguous recommendation of the desired types of performers in their performance video content.

In accordance with an embodiment of the present invention, a server and a method for providing a collaboration service based on a performer object include a process of selecting a performer through video content playback by recommending a performer of a registered performing category corresponding to a collaboration requester setting performing category to a performer slot. Another object is to omit and immediately recommend the desired type of performers.

In accordance with an embodiment of the present invention, a server and method for providing a collaboration object based collaboration service may be configured to generate a collaboration collaborator group by receiving an entire collaboration request, which is a collaboration request for all the performance objects expressed in the video content, from the collaboration requester. The other aim is to improve the user convenience of the collaborator and to create an integrated and instant collaboration and configuration without the playback of additional video content.

In accordance with an embodiment of the present invention, a server and a method for providing a collaboration service based on a performer object are provided. The performance history information of the performer object is overlaid on the video content to enhance the accuracy and expertise of the production of the video content by utilizing the careers of the performers in collaboration. For other purposes.

In accordance with an aspect of the present invention, there is provided a server-based collaboration service providing server, including: a communication module configured to communicate with a terminal through a network; A video content providing module for transmitting a video content and web page data to the terminal to provide a video content service; A collaborator database for storing performer data including a performer object identifier and a contactor contact information identifying at least one performer object represented on a screen of the video content in association with the video content; A collaboration request receiving module configured to receive a collaboration request for the performer object represented in the video content from a collaboration requester playing the video content in the terminal; A performer object identification module for identifying the performer object identifier of the performer object through the collaborator database according to the collaboration request received by the collaboration request receiving module; A collaboration group generation module for registering a performer corresponding to the performer object identifier identified as the target of the collaboration request from the performer object identification module to the performance collaboration group of the collaboration requester; And a notification module for notifying the performer of the reception of the collaboration request through the performer contact information of the performer registered in the performance collaboration group of the collaboration requester.

In accordance with an embodiment of the present invention, a method for providing a collaboration service based on a collaboration object may include: a collaboration service providing server identifying a first performer object of first video content including at least one first performer object represented on a screen; A first step of storing first performer data including a performer object identifier and first performer contact information in a collaborator database in association with the first video content: the collaboration service providing server playing the first video content A second step of receiving a collaboration request for the first performer object represented in the first video content from a collaboration requester; A third step of the collaboration service providing server identifying the first performer object identifier of the first performer object through the collaborator database according to the collaboration request of the collaboration requester; A fourth step of the collaboration service providing server registering a first performer corresponding to the first performer object identifier identified as a target of the collaboration request to a performance collaboration group of the collaboration requester; And a fifth step of, by the collaboration service providing server, notifying the first performer of receipt of the collaboration request through the first performer contact information of the first performer registered in the performance collaboration group of the collaboration requester. Characterized in that it comprises a.

According to the above configuration, the server and method for providing a collaboration object-based collaboration service according to the present invention, when a collaboration request is received from a collaboration requester who plays video content, receives a collaboration requester through a performer object identifier associated with the video content. By registering in the collaboration requester's performance collaboration group, it improves the user convenience of adding the collaboration collaborator group and improves the efficiency of collaboration and organization by directly understanding the performance and reliability of the performer by watching videos without further searching. .

In accordance with an embodiment of the present invention, a server and a method for providing a collaboration service based on a collaboration object may notify a performer of receiving a collaboration request through the contact information associated with the video content according to the reception of the collaboration request, and accept the performer for the collaboration request. Or, by receiving rejection through the network, it enables immediate collaborative decision making through two-way communication, and provides the effect of adaptively negotiating the schedule of the collaborator and the schedule of performers.

In accordance with an embodiment of the present invention, the server and method for providing a collaboration object-based collaboration service provide a producer who does not appear in a video content by registering as a collaboration target through a producer identifier and producer contact information to a performance collaboration group of a collaboration requester. In addition, producers who are not performers as well as video content performers can be easily registered in the collaboration group, thereby improving the quality of video contents.

In accordance with an embodiment of the present invention, the server and method for providing a collaboration service based on the object are overlaid with a selection area for selecting a producer on the video content, thereby sharing only the video content to other web pages beyond the video content providing web page. Even if it provides the effect that it is possible to send a collaboration request to the producer who is not a video content performer.

In accordance with an embodiment of the present invention, a server and method for providing a collaboration service based on an object are intuitive to select a video region of a desired performer by a collaboration requester by associating a collaboration request execution object with a display region of a performer object included in video content. In this way, it is possible to select a collaborative target and to send a collaboration request to a performer, a video content performer, even if only the video content is shared on another web page.

In accordance with an embodiment of the present invention, a server and a method for providing a collaboration service based on a performer object have the effect of organizing desired types of performers systematically into a performance collaboration group by creating a performance collaboration group by setting a performing category slot. to provide.

In accordance with an embodiment of the present invention, a server and method for providing a collaboration object-based collaboration service provide a collaboration requester setting conforming to a collaboration requester specifying a category of a performer who appeared in the video content when the collaboration requester designates a collaboration requester. Automatic placement in category slots provides the ability to quickly and accurately assign collaborators based on collaborator set-up performing categories.

In accordance with an embodiment of the present invention, the server and method for providing a collaboration object-based collaboration service further store a performer registration performing category when registering a performer, and automatically set up a cooperative requestor setting performing according to a performer registration performing category when the collaboration requester is requested. By automatically placing in slots, collaborators can be assigned more quickly and accurately according to collaborator set-up performing categories.

In accordance with an embodiment of the present invention, the server and method for providing a collaboration object-based collaboration service provide various performers by recommending a video content including a performer registered performing category conforming to a collaboration requester according to the collaboration requester setting performing category of the collaboration requester. In their performance video content, it provides an integrated and clear recommendation of the desired types of performers.

In accordance with an embodiment of the present invention, a server and a method for providing a collaboration service based on a performer object include a process of selecting a performer through video content playback by recommending a performer of a registered performing category corresponding to a collaboration requester setting performing category to a performer slot. Omits and provides the effect of immediately recommending the desired type of performers.

In accordance with an embodiment of the present invention, a server and method for providing a collaboration object based collaboration service may be configured to generate a collaboration collaborator group by receiving an entire collaboration request, which is a collaboration request for all the performance objects expressed in the video content, from the collaboration requester. It improves the user convenience of collaborators and enables the creation of integrated and instant collaboration and composition without playing additional video contents.

In accordance with an embodiment of the present invention, a server and a method for providing a collaboration service based on a performer object are provided. The performance history information of the performer object is overlaid on the video content to enhance the accuracy and expertise of the production of the video content by utilizing the careers of the performers in collaboration. Provide effect.

1 is a block diagram showing an entire system according to the present invention.

Figure 2 is a detailed configuration diagram showing a collaboration service providing server according to the present invention.

3 is a diagram of a performer data structure stored in a collaborator database and a collaborator database according to an exemplary embodiment of the present invention.

Figure 4 is an illustration of registration of the performance collaboration group of the collaboration service providing server according to an embodiment of the present invention.

5 is a screen diagram showing a collaboration request execution object in the video content according to an embodiment of the present invention.

6 is a screen configuration diagram showing registration of a performance collaboration group in a plurality of video contents in a collaboration service providing server according to an embodiment of the present invention.

7 is an overall processing flow diagram illustrating a method of providing a collaboration object based collaboration service according to the present invention.

8 is a detailed flowchart illustrating a method for providing a collaboration object based collaboration service according to the present invention;

9 is a detailed flowchart illustrating a method of providing a collaboration object-based collaboration service according to the present invention.

(Explanation of the sign)

100: collaboration service providing server 200: terminal

110: communication module 120: video content providing module

130: collaboration target database 140: collaboration request receiving module

150: performer object identification module 160: collaboration group creation module

170: notification module 180: execution object insertion module

190: video content recommendation module 192: performer recommendation module

The terms or words used in this specification and claims are not to be construed as limiting in their usual or dictionary meanings, and the inventors shall refer to the principles on which terms and concepts may be defined in order to best explain their inventions. It should be interpreted as meanings and concepts corresponding to the technical spirit of the invention.

Therefore, the configuration shown in the embodiments and drawings described in this specification corresponds to a preferred embodiment of the present invention, and does not represent all of the technical spirit of the present invention, the configuration will be replaced at the time of filing of the present invention. There may be various equivalents and variations.

Throughout the specification, the description that a part “includes” an element means that the element may further include other elements, except for the absence of a special objection thereto. In addition, the terms “.. module”, “.. unit” and “.. system” described in the specification mean a unit that processes at least one function or operation, which is hardware or software or a combination of hardware and software. It may be implemented, and may be included in one device or each other device.

As used herein, “collaboration” refers to collaboration with performer objects that are performers of video content that can be directly selected from video content. In addition, "collaboration" refers to the collaboration with non- performers of video content, such as producers, lighting directors, cinematographers. This “collaboration request” includes both collaborative requests for co- performers or collaborative requests for non- performers. A “Performance Collaboration Group” can comprise both co- performers and non- performers who are “collaborated”.

Hereinafter, a cooperative service providing server 100 according to the present invention will be described with reference to the drawings.

First, Figure 1 shows the overall system configuration according to the present invention, the terminal 200 to perform the function of receiving and consuming the video content from the collaboration service providing server 100 and the collaboration service providing server 100 via a communication network. ).

The collaboration service providing server 100 stores a plurality of video contents (content_video), distributes video contents (content_video) to the terminal 200 on the web, and may be configured as a single server. The server system may be configured as a server, and the servers constituting the server system may be distributed in different locations.

In addition, all or some of the components of the collaboration service providing server 100 according to the present invention may be implemented as a program / application executed by a single information processing terminal such as, for example, a smartphone or a user computer, and some components. They may be implemented in a client terminal and some other components may be implemented in the form of a server-client service implemented in a server computer connected to the client terminal and a communication network, or components may be distributed and implemented in each server of a distributed server system. have. Alternatively, the cooperative service providing server 100 may implement the elements as a set of logic circuits constituting the semiconductor processor.

The terminal 200 is not particularly limited and includes a function of directly or indirectly accessing a communication network and a function of displaying video content (content_video) to a user through a display means. The terminal 200 may be a mobile communication terminal such as a personal computer, a laptop computer, a tablet computer, or a smartphone.

2 is a detailed configuration diagram illustrating a collaboration service providing server 100 according to the present invention. As shown in FIG. 2, the collaboration service providing server 100 according to the present invention includes a communication module 110, a video content providing module 120, a collaborative target database 130, a collaboration request receiving module 140, and a performer. It is configured to include an object identification module 150, the collaboration group generation module 160 and the notification module 170.

Each component is functionally divided to clearly explain the operation of the collaboration service providing server 100 according to the present invention. Therefore, each module is not necessarily divided into a single physically separated component, but may be implemented in the form of a set of computer instructions constituting a part of a program, for example. The function of the module can be expressed.

The communication module 110 communicates with the terminal 200 through a network. The communication module 110 may be configured as a general network connection device, and may be connected to the Internet or an intranet through a PSTN, a mobile communication network, etc. according to a communication protocol such as UDP or TCP.

The video content providing module 120 transmits video content (content_video) and web page data (data_web_page) to the terminal 200 to provide a video content (content_video) service.

More specifically, the video content providing module 120 may include a web page storage unit for storing web page data (data_web_page) and a video storage unit for storing video content (content_video).

The web page storage unit and the video storage unit may be local storage of a network-connected storage such as a network-connected storage such as a NAS connected to the collaboration service providing server 100 and a network or a P2P service, It may be composed of a plurality of storage modules distributed in geographic locations.

The video content providing module 120 may provide video content (content_video) in a streaming manner by including a URL for receiving each video content (content_video) in a web page, or provide video content (content_video). By including a downloadable URL in a web page, the video content (content_video) may be provided by a download method.

The collaborator database 130 includes: a performer data (data_performer) including a performer object identifier (id_performer_object) and performer contact information (info_contact_performer) that identify at least one performer object (object_performer) displayed on the screen of the video content (content_video). Performs the function of saving it.

For example, it may be stored in association with the corresponding video content (content_video) in the form of the performer data structure diagram 132 illustrated in FIG. 3. For example, the collaborator database 130 stores the performer object identifier id_performer_object and the performer contact information info_contact_performer, respectively. In this case, the performer object identifier id_performer_object may be a name of a performer, a service account, or the like, and the performer contact information (info_contact_performer) may include any one or more of an address, a phone number, an email, an SNS account, and a blog URL.

The collaboration request receiving module 140 receives a collaboration request (request_costarring) for a performer object (object_performer) expressed in the video content (content_video) from the collaboration requester (user_request_costarring) playing the video content (content_video) in the terminal 200. Perform the function.

For example, a collaborative requester (user_request_costarring) terminal runs an application in which the collaborative service providing server 100 according to the present invention is implemented, and a collaborative requester (user_request_costarring) calls a video content (content_video) from a network or a storage device through an application. Play it through Next, when the collaboration requester (user_request_costarring) selects the performer object (object_performer) on the video content (content_video), the application generates a collaboration request (request_costarring) for the selected performer object (object_performer). Accordingly, the collaboration request receiving module 140 may receive a collaboration request (request_costarring).

Alternatively, the collaboration requester (user_request_costarring) accesses a web page on which the collaboration service providing server 100 according to the present invention is implemented through a web browser to play video content (content_video) on a web page. When the collaborative requester (user_request costarring) selects a performer on the video content (content_video),

The collaboration service providing server 100 may be implemented by receiving a collaboration request (request_costarring). When the collaboration requester (user_request_costarring) selects a performer on the screen by a touch or click method using an input interface module such as a touch pad, a touch screen, or a mouse of the terminal 200, the terminal 200 selects a collaboration request (request_costarring). In addition, the collaboration request receiving module 140 receives a collaboration request (request_costarring).

The performer object identification module 150 identifies the performer object identifier (id_performer_object) of the performer object (object_performer) through the collaborator database 130 according to the collaboration request (request_costarring) reception of the collaboration request receiving module 140.

The performer object (object_performer) included in the video content (content_video) uploads a user's name of the performers of the video content (content_video) when uploading the video content (content_video), or the collaboration service providing server 100 recognizes a face image. Through the automatic tagging the names of the performers can be configured to distinguish each object (object_performer) on the screen of the video content (content_video).

The collaboration group creation module 160 transfers the performer corresponding to the performer object identifier id_performer_object identified as the target of the collaboration request (request_costarring) from the performer object identification module 150 to the performance collaboration group (group_collaborate_performance) of the collaboration requester user_request_costarring. Register.

For example, the collaborative requester (user_request_constarring) is a performer that performs guitar, drum and dance performing when the performer object (performer) represented on the screen of the first video content (content_video_first) performs drumming and dance performing. object_performer) to identify the performer object identifier (id_performer_object) and store the guitar, drum and boxer.

Meanwhile, it is not necessary to designate all the collaboration target performers in a single video content (content_video), but it is preferable to designate the collaboration target performers in the plurality of video contents (content_video). To this end, the collaborative group generation module 160 may perform performers corresponding to the performer object identifiers (id_performer_objects) identified by the collaboration requests (request_costarrings) received from each of the plurality of video contents (content_video), and perform the performance of the collaboration requester (user_request_costarring). It is desirable to register with the collaboration group (group_collaborate_performance).

According to this embodiment, as shown in FIG. 6, the collaborative requester (user_request_costarring) uses the guitar player 311 in the video content_A, the singer 312 in the video content_B, and the drummer 313 in the video content_C, respectively. You can choose. Accordingly, the collaboration group creation module 160 registers each of the performer object identifiers (id_performer_object, Kim Kita, Naga, and drum) to the performance collaboration group (group_collaborate_performance) 135 of the collaboration requester (user_request_costarring).

The notification module 170 notifies the performer of the reception of the collaboration request (request_costarring) through the performer contact information (info_contact_performer) registered in the performance collaboration group (group_collaborate_performance) of the collaboration requester (user_request_costarring). The notification module 170 may selectively use the notification interface according to various types of contact information of the performer, such as a phone number, an email, an SNS account, and the like.

On the other hand, the performer received the collaboration request (request_costarring) through the notification module 170, it is preferable to accept or reject the collaboration request (request_costarring) according to their schedule. To this end, the notification module 170 may receive through the network an acceptance or rejection of the collaboration request (request_costarring) from the performer or performers notifying the reception of the collaboration request (request_costarring). When the notification module 170 receives the rejection for the collaboration request request_costarring, the collaboration group generation module 160 excludes the performer from the performance collaboration group group_collaborate_performance.

When the collaboration service providing server 100 according to the present invention receives the acceptance through the notification module 170 from the performer or performers who have received the request for the collaboration request (request_costarring), the performer or performers capable of the collaboration request (request_costarring) are possible. In order to obtain information that can be collaborated from the collaboration schedule setting interface unit 162 is preferably further included.

To this end, the collaboration schedule setting interface unit 162 provides a collaboration schedule setting interface (interface_schedule) for setting a collaboration schedule (collaboration time) to performers or performers who have accepted the collaboration requester (user_request_costarring) and the collaboration request (request_costarring). Can be. More preferably, the collaboration schedule setting interface unit 162 may further set a collaboration place together with the collaboration schedule.

Hereinafter, operations of the collaboration request reception module 140, the performer object identification module 150, the collaboration group generation module 160, and the notification module 170 will be described in detail with reference to the exemplary diagram of FIG. 4.

As shown in FIG. 4, for example, a collaborative requester (user_request_costarring) performs a singer, a bass guitar, an electric guitar, an acoustic guitar, and a drum performer represented on a content_video screen 1 of a band session. When the acoustic guitar performer 310 is selected among the object_performers, the terminal of the collaboration requester user_request_costarring generates and transmits a collaboration request request_costarring, and the collaboration request receiving module 140 is configured for the acoustic guitar performer 310. Receive a collaboration request (request_costarring).

Next, the performer object identification module 150 identifies the performer object identifier (id_performer_object) "kim other" corresponding to the acoustic guitar performer 310 selected according to the collaboration request (request_costarring) through the collaborator database 130. Next, the collaboration group creation module 160 registers the identified performer object identifier id_performer_object "Kim Other" to the performance collaboration group (group_collaborate_performance). Finally, the notification module 170 transmits the reception of the collaboration request (request_costarring) to the "Kim Kita" through the http: //twiter.guitar kim / 010-123-4567, which is the information contactor (info_contact_performer) of "Kim Kita". Notify (3).

In an embodiment of further receiving / rejecting the performer, the notification module 170 may be configured to receive one of the intention to reject or accept the request_costarring from the performer “Kim Other”.

In an embodiment of further providing a collaboration schedule interface, the collaboration schedule setting interface unit 162 may provide a collaboration schedule setting interface (interface_schedule) 4 to obtain collaborative information of the performer Kim, who has received the acceptance. have. In this case, the collaboration schedule received from the performer Kim Kita may be configured to be registered in the collaboration schedule slot of the performer Kim Kita of the performance collaboration group (group_collaborate_performance) 133.

On the other hand, in the case of video content (content_video) where a performance session corresponding to a music performance is performed, a producer such as a composer who composes music and a songwriter who writes a song and a producer who plans a performance of the performance session appears. exist. In this case, it is desirable to enable the collaboration request (request_collaborate) for the producer in the same way as the collaboration request (request_costarring) for the performer object (object_performer) displayed on the screen.

To this end, the collaborator database 130 further associates the producer data (data_producer) including the producer identifier (id_producer) identifying the producer of the video content (content_video) and the producer contact information (info_contact_producer) with the video content (content_video). Save it.

The collaboration request receiving module 140 further receives a collaboration request (request_collaborate) for the producer of the video content (content_video) from the collaboration requester (user_request_costarring) playing the video content (content_video) in the terminal 200.

The performer object identification module 150 may further configure the producer identifier (id_producer) of the producer through the collaborator database 130 according to the collaboration request (request_collaborate) of the collaboration requester (user_request_costarring).

The collaboration group generation module 160 may be configured to further register a producer corresponding to the producer identifier (id_producer) identified as a target of the collaboration request (request_collaborate) to the performance collaboration group (group_collaborate_performance) of the collaboration requester (user_request_costarring).

The notification module 170 may be configured to notify the producer of the receipt of the collaboration request (request_collaborate) through the producer contact information (info_contact_producer) of the producer registered in the performance collaboration group (group_collaborate_performance) of the collaboration requester (user_request_costarring).

Based on this configuration, not only video content (content_video) performers but also producers who are not performers can easily register with the performance collaboration group (group_collaborate_performance) to improve the quality of the video content (content_video) for the performance designed by the collaborator (user_request_costarring). The collaboration service providing server 100 according to the present invention preferably further includes an execution object insertion module 180 for inserting the collaboration request execution object (object_request_collaborate) into the video content (content_video).

Accordingly, the collaboration request receiving module 140, as shown in Figure 5, the collaboration request execution object (object_request_collaborate) displayed in the outer region that does not overlap with the performer object (object_performer) displayed on the video content (content_video) screen ( The terminal further receives a collaboration request (request_collaborate) of a collaboration requester (user_request_costarring) generated according to the selection of 320).

The performer object identification module 150 further identifies the producer identifier (id_producer) of the producer through the collaborator database 130 according to the selection of the object_request_collaborate 320 displayed in the outer region of the video content (content_video). Can be configured to For example, as shown in the producer data (data_producer) structure diagram 134 of FIG. 5, a producer category including composition, writing, editing, and lighting, a producer identifier (id_producer) corresponding to each producer category, and a corresponding producer contact Information (info_contact_producer).

According to an embodiment of overlaying a selection area for selecting a producer on video content (content_video), the video content (content_video) may be shared even if only video content (content_video) is shared to another web page beyond the video content (video content) video providing web page. ) Provides the effect of sending a collaborative request (request_collaborate) to the non-producer.

On the other hand, recently, an increasing number of cases include additional execution objects in the video content (content_video). The execution object is implemented in such a manner as to be embedded or overlayed on the video content screen, and configured to perform additional operations when the user selects the execution object.

Accordingly, the collaboration service providing server 100 according to the present invention inserts an execution object insertion module for inserting the collaboration request execution object (object_request_costarring) into at least a portion of the display area of the object object (object_performer) included in the video content (content_video). It further includes (180), the collaboration request receiving module 140, the terminal 200 to further receive a collaboration request (request_costarring) generated in accordance with the collaboration request execution object (object_request_costarring) selection of the collaboration requester (user_request_costarring) desirable.

For example, if the video content (content_video) is about the music performance in which the session appears, post a JavaScript command or URL information that will take you to a web page where you can view the per-former data_performer included in the music-playing session. In this way, the function of the collaboration request execution object (object_request_costarring) can be implemented.

Through such a configuration, the execution object insertion module 180 associates the collaboration request execution object (object_request_costarring) with the display area of the performer object (object_performer) included in the video content (content_video), thereby allowing the collaboration requester (user_request_costarring) to desired image area. In order to select the collaborators in an intuitive way to select a video content, and even if only the video content (content_video) is shared on another web page beyond the video content (content_video) providing web page, request_costarring).

Meanwhile, the collaborative requester (user_request_costarring) may wish to create a performance collaboration group (group_collaborate_performance) including a plurality of performers and / or producers in various performing categories. In this case, when the performers are designated in the plurality of video contents (content_video), several performers belonging to the same performing category may be registered in duplicate, or a performer belonging to a certain performing category may be missing. In order to prevent such confusion, the collaborator requester (user_request_costarring) registers the performer slot (slot_performer) as a collaborative requester registration category (category_register) in advance to the performance collaboration group (group_collaborate_performance) that he or she wishes to set up. It is desirable to designate a producer.

More preferably, the collaborative requester (user_request_costarring) designates the performing category of the performer as a collaborative requester designated performing category (category_designate) when the performer is selected, and the collaborative group creation module 160 matches the collaborative requestor designated performing category (category_designate). Cooperative Requester Registration The performer may be registered in the performer slot (slot_performer) of the performing category (category_register).

To this end, before the collaboration group creation module 160 receives the collaboration request (request_costarring), the performance collaboration group configured to include a per-operator slot (slot_performer) for each collaboration requester setting category (category_reference) set by the collaboration requester (user_request_costarring). The group_collaborate_performance may be generated, and upon receipt of the collaboration request (request_costarring), the performer identified as the target of the collaboration request (request_costarring) may be configured to be registered in the performer slot (slot_performer) according to the collaboration requester setting performing category (category_reference).

In addition, the collaboration request receiving module 140 receives a collaboration request (request_costarring) further including a collaboration requester specification performing category (category_designate) of a performer according to the specification of the collaboration requester (user_request_costarring), and the collaboration group generation module 160. May be configured to register a performer in the performer slot slot_performer of the cooperative requestor setting performing category corresponding to the designated performing category (category_designate).

Alternatively, the performer registers its performing category as a performer registration performing category (category_register) when registering the performer data (data_performer), and if the collaboration requester (user_request_costarring) designates the performer, the collaboration group creation module 160 The performer registration corresponding to the performer registration conforming category (category_register) of the performer can register the performer in the performer slot (slot_performer) of the performing category (category_register).

According to this embodiment, since the performer slot (slot_performer) is created in the performance collaboration group (group_collaborate_performance) for each collaborator request setting category (category_reference), when the corresponding performer slot (slot_performer) is occupied, the addition of performers of the same performing category is no longer performed. Is blocked, and the unused performer slot (slot_performer) makes it easier to recognize performers in the performing category to add, thereby providing a more efficient way to manage performance collaboration groups (group_collaborate_performance).

To this end, the collaborator database 130 further includes a performer registration performing category (category_register) of the performer object (object_performer), and stores it as performer data (data_performer), and the collaboration group creation module 160 performs a performer registration performing category. The performer setting corresponding to (category_register) may be configured to register a performer in the performer slot (slot_performer) of the performing category (category_reference).

With this configuration, if a collaborator (user_request_costarring) categorizes the performer who appeared in the video content (content_video) as the designated performing category (category_designate) at the time of the request, the corresponding collaborator setting setting category (category_reference) slot By automatically deploying, collaborators can be quickly and accurately assigned according to the collaborator request setting category (category_reference).

On the other hand, the collaborative requester (user_request_costarring) meets the collaborator request setting category (category_reference), and in order to search for a favorite performer, a lot of video content (content_video) must be watched. In order to alleviate this inconvenience, it is preferable that the collaboration service providing server 100 preferentially recommend the video content (content_video) appearing by the performer corresponding to the collaboration requester setting performing category (category_reference).

To this end, the collaboration service providing server 100 recommends a video content (content_video) including a performer registration performing category (category_register) conforming to the collaboration requester setting performing category (category_reference) to the collaboration requester (user_request_costarring) It is preferable that the configuration further comprises a recommendation module 190.

Meanwhile, there may be a case in which it is more desirable for the collaborative requester (user_request_costarring) to immediately recommend the performer without having to watch the recommended video content. In this case, the collaboration service providing server 100 may automatically recommend, for example, a performer who has received a lot of recommendations, a performer included in the most viewed video content, and a performer who can join the collaboration time.

To this end, the collaboration service providing server 100 according to the present invention recommends a performer recommendation module 192 recommending a performer of a conforming category (category_register) corresponding to a collaboration requester setting performing category (category_register) to a performer slot (slot_performer). It is preferable that it further comprises.

The recommender recommendation module 192 recommends performers in the performing category (category_register) corresponding to the cooperative requestor setting performing category (category_register) to the performer slot (slot_performer) to immediately recommend the desired types of performers.

On the other hand, as described above, a collaborative requester (user_request_costarring) is a single video content (as opposed to designating a collaborative target performer in the plurality of video contents (content_video) by generating a collaboration request (request_costarring) for each video content (content_video). A performance collaboration group (group_collaborate_performance) can be created by generating a single collaboration request (request_costarring) by designating all performers appearing in content_video as a collaboration target.

To this end, the collaboration service providing server 100 according to the present invention executes the entire collaboration request for generating the entire collaboration request (request_costarring_all), which is a collaboration request (request_costarring) for all the performer objects (object_performer) expressed in the video content (content_video). It is preferable to further include an execution object insertion module 180 for inserting the object (object_request_costarring_all) to the video content (content_video).

Accordingly, the collaboration request receiving module 140 receives the entire collaboration request (request_costarring_all) according to the selection of the entire collaboration request execution object (object_request_costarring_all) of the collaboration requester (user_request_costarring).

The execution object insertion module 180 receives the entire collaboration request (request_costarring_all), which is a collaboration request (request_costarring) for all performer objects (object_performers) expressed in the video content (content_video), from the collaboration requester (user_request_costarring). ) Quickly organizes collaborators without having to search for multiple video content (content_video) so that an integrated and instantaneous performance collaboration group (group_collaborate_performance) is created.

On the other hand, in an environment in which various kinds of video content (content_video) are supplied, there is a problem of repeatedly watching various video content (content_video) until a performer corresponding to a performance planned by the collaborative requester (user_request_costarring) is satisfied. In order to solve this problem, it is desirable to display objective information on the performing ability of the performer who appears when viewing video content (content_video).

To this end, the collaboration service providing server 100 according to the present invention preferably further stores the performance history information (experience_performance), which is the history information of the performance object (object_performer) as shown in FIG. 3, in the performance data (data_performer). Do. In addition, the execution object insertion module 180 inserts a history request execution object (object_request_experience) requesting performance history information (experience_performance) in at least a portion of the display area of the performance object (object_performer) included in the video content (content_video). It is preferable to configure so that.

In this case, the execution object insertion module 180 may be configured to include an overlay processor 182 that receives the performance history information (experience_performance) through the collaborator database 130 and overlays the video content (content_video). Here, the history information may be a web page address or a calculated career year linked to the video content (content_video) in which the performer appears.

For example, as shown in FIG. 9, when the collaboration requester user_request_costarring selects the performer object area designated as the history information execution objects 330 and 332 on the video content content_video, the history information 340, near the corresponding object object_performer, is selected. 342 is overlaid. According to this configuration, the collaborative requester (user_request_costarring) can improve the quality of the collaborative video content (content_video) by confirming the careers of the performers before the collaborative request is decided.

Hereinafter, each step of the method for providing a cooperative service according to the present invention will be described with reference to FIGS. 7 and 8. The collaboration service providing method according to the present invention is implemented through the collaboration service providing server 100.

First, the overall processing flow of the collaboration service providing server 100 that performs the method for providing a collaboration object based on the present invention according to the present invention will be briefly described with reference to FIG. 7, and then each step will be described in detail with reference to FIG. do.

7 is a flowchart illustrating a method of providing a collaboration object based collaboration service according to the present invention.

First, as illustrated in FIG. 7, the collaboration service providing server 100 may identify a first performer object identifier (id_performer_object_first) and a first performer contact that identify a first performer object (object_performer_first) that is displayed on a video content (content_video) screen. Associating the first performer data (data_performer_first) including the information (info_contact_performer_first) in the collaborator database 130, and provides a video content (content_video) service to the terminal 200 through the video content providing module 120 The first steps s10 and s12 are performed.

Next, the collaboration request providing server 100 from the collaboration requester (user_request_costarring) playing the video content (content_video) in the terminal 200 for the collaboration request (object_performer) expressed on the video content (content_video) screen ( A second step s20 of receiving request_costarring is performed.

The second step (s20) receives a collaboration request (request_costarring) for the performer object (object_performer) expressed on the video content (video_video) screen from the collaboration requester (user_request_costarring) playing the video content (content_video) in the terminal 200 do.

Next, when the collaboration service providing server 100 receives the collaboration request (request_costarring), it performs a third step (s30) of identifying the performer object identifier (id_performer_object) of the performer object (object_performer) through the collaborator database 130. do.

Next, the collaboration service providing server 100 sets the first performer (first_former_first) corresponding to the first performer object identifier (id_performer_object_first) identified as the target of the collaboration request (request_costarring) to the performance collaboration group (group_collaborate_performance) of the collaboration requester (user_request_costarring). The fourth step (s40) of registering is performed.

For example, when the performer object (performer) represented on the screen of the first video content (content_video_first) performs guitar, drum and dance performing, the performer performing guitar, drum and dance performing is identified as a performer object (object_performer). It is divided into an object identifier (id_performer_object) and stores Kim Kita, Drum and Box Dancer.

According to this embodiment, as shown in FIG. 6, the collaborative requester (user_request_costarring) uses the guitar player 311 in the video content_A, the singer 312 in the video content_B, and the drummer 313 in the video content_C, respectively. You can choose. Accordingly, in the fourth step (s40), each of the performer object identifiers (id_performer_object, Kim Kita, Naga, and drums) is registered in the performance collaboration group (group_collaborate_performance) 135 of the collaboration requester (user_request_costarring).

Finally, the collaboration service providing server 100 receives the request for the collaboration request (request_costarring) through the first performer contact information (info_contact_performer_first) of the first performer (first_performer_first) registered in the performance collaboration group (group_collaborate_performance) of the collaboration requester (user_request_costarring). A fifth step s50 of notifying the first performer_first is performed.

Based on the foregoing description of FIG. 7, the first steps s10 to 5 s50 of FIG. 7 will be described in detail with reference to FIG. 8.

8 is a detailed flowchart illustrating a method of providing a collaboration object-based collaboration service according to the present invention.

First, the first performer object identifier (id_object_performer_first) identifying the first performer object (object_performer_first) of the first video content (content_video_first) including the first performer object (object_performer_first) displayed on the screen by the collaboration service providing server 100. ) And the first performer (first) data including the first performer contact information (info_contact_performer_first) in association with the first video content (content_video_first) in the collaborator database 130 (s10), the collaborator requester terminal (200) The first step (s10) is performed to provide a video content (content_video) service by transmitting video content data (data_content_video) and web page data (data_web_page) of the first video content (content_video_first) to the user (s12).

Next, the collaboration requester terminal 200 that receives the video content (content_video) service from the collaboration service providing server 100 plays the first video content (content_video_first) (s13) and performs a performer on the first video content (content_video_first). If selected, the collaboration service providing server 100 performs a second step (s20) of receiving the performer collaboration request (request_costarring) according to the collaboration request (request_costarring) for the selected performer.

For example, the collaboration request (request_costarring), the collaboration requester (user_request_costarring) drives the application in which the collaboration service providing server 100 according to the present invention is implemented in the collaboration requester terminal 200, the collaboration requester (user_request_costarring) is stored through the application When a video content (content_video) is loaded and played on a device, a performer selected from a collaboration requester (user_request_costarring) on the video content may be implemented in such a manner that an application generates a collaboration request (request_costarring).

Alternatively, the collaboration requester (user_request_costarring) accesses a web page on which the collaboration service providing server 100 according to the present invention is implemented through a web browser to play video content (content_video) on a web page. When the collaboration requester (user_request costarring) selects a performer on the video content (content_video), the collaboration service providing server 100 may be implemented by receiving the collaboration request (request_costarring). When the collaboration requester (user_request_costarring) selects a performer on the screen by a touch or clip method using an input interface module such as a touch pad, a touch screen, or a mouse of the collaboration requester terminal 200, the collaboration requester terminal 200 requests a collaboration request. (request_costarring) is generated and received from the collaboration service providing server 100 through a network.

Next, according to the collaboration request (request_costarring) received by the collaboration service providing server 100, a third step (s30) of identifying the performer object identifier (id_performer_object) of the performer object (object_performer) through the collaborator database 130 Perform.

Next, the collaboration service providing server 100 receives the collaboration request (request_costarring) through the first performer contact information (info_contact_performer_first) of the first performer (first performer_first) registered in the performance collaboration group (group_collaborate_performance) of the collaboration requester (user_request_costarring). The fifth step (s50) of notifying the first performer (firstformer_first) is performed. In the fifth step (s50), the notification interface may be selectively used according to various types of contact information of the performer, such as a telephone number, an email, an SNS account, and the like.

On the other hand, the performer receives the collaboration request (request_costarring) it is preferable to accept or reject the collaboration request (request_costarring) according to their schedule.

According to this embodiment, the collaboration service providing server 100 accepts the request for the collaboration request (request_costarring) from the first performer (first performer_first) or the first performers (first performer_first) that has notified the reception of the collaboration request (request_costarring) through the network. A sixth step of receiving a rejection (s60) is performed. When the collaboration service providing server 100 receives the rejection for the collaboration request request_costarring in step 6, the collaboration service providing server 100 excludes the performer from the performance collaboration group (group_collaborate_performance). In the sixth step, a notification interface may be selectively used according to various types of contact information of the first performer, for example, a telephone number, an email, an SNS account, and the like.

The performer who has received the request for collaboration (request_costarring) is recommended to accept or reject the request for collaboration (request_costarring) according to its schedule.

To this end, the collaboration service providing server 100 may receive an acceptance or rejection of the collaboration request (request_costarring) through the network from the first performer or the first performers that have notified the reception of the collaboration request (request_costarring). When receiving the rejection for the collaboration request (request_costarring), the collaboration service providing server 100 excludes the performer from the performance collaboration group (group_collaborate_performance).

According to an embodiment of the present invention, in the seventh step, when an acceptance of the request for request_costarring is received from the first performers_first or the first performers_first that notify the receipt of the request for request_costarring, the request for request_costarring is received. In operation S70, a collaboration scheduling interface (interface_schedule) is provided in order to obtain collaborative information from the first performer (first performer_first) or the first performers (first performer_first). The collaboration schedule setting interface (interface_schedule) sets a collaboration schedule (collaboration time) to the first performer (first_performer_first) or the first performers (first) _performers_first who have accepted the collaboration requester (user_request_costarring) and the collaboration request (request_costarring). (interface_schedule) can be provided. More preferably, in the collaboration schedule setting interface (interface_schedule), it is preferable to further set the collaboration place together with the collaboration schedule.

To this end, the collaboration service providing server 100 according to the present invention includes producer data including a producer identifier (id_producer) and a producer contact information (info_contact_producer) for identifying a producer of the first video content (content_video_first) in a first step (s10). It is preferable to store (data_producer) in the collaborator database 130 in association with the first video content (content_video_first).

Next, in a second step (s20), the collaboration service providing server 100 from the collaboration requester (user_request_costarring) playing the first video content (content_video_first) to the producer of the first video content (content_video_first) (request_collaborate) It is preferable to further receive (s22).

Next, in the third step (s30), the collaboration service providing server 100 identifies the producer identifier (id_producer) of the producer through the collaborator database 130 according to the collaboration request (request_collaborate) of the collaboration requester (user_request_costarring) ( s32) is preferred.

Next, in the fourth step (s40), the collaboration service providing server 100 selects the producer corresponding to the producer identifier (id_producer) identified as the target of the collaboration request (request_collaborate), and the performance collaboration group (group_collaborate_performance) of the collaboration requester (user_request_costarring). It is preferable to register at (s42).

Next, in the fifth step (s50), the collaboration service providing server 100 receives the collaboration request (request_collaborate) through the producer contact information (info_contant_producer) of the producer registered in the performance collaboration group (group_collaborate_performance) of the collaboration requester (user_request_costarring). It is desirable to notify the producer (s52).

Next, in the sixth step, it is preferable that the collaboration service providing server 100 receives the acceptance or rejection of the collaboration request (request_collaborate) from the producer who notified the reception of the collaboration request (request_costarring) through the network (S62).

Lastly, in the seventh step, when the collaboration service providing server 100 receives the acceptance from the producer notifying the receipt of the collaboration request (request_collaborate), the collaboration service is provided to obtain collaborative information from the producer who can request the collaborative request (collaborate). It is desirable to provide a schedule setting interface (interface_schedule) (s72).

Based on this embodiment, the collaboration service providing server 100 is not only a video content (content_video) performer, but also a non-producer producer is easily registered in the performance collaboration group (group_collaborate_performance), so that the video for the performance designed by the collaboration requester (user_request_costarring) In order to improve the quality of the content (content_video), the collaboration service providing server 100 according to the present invention preferably inserts the collaboration request execution object (object_request_collaborate) into the video content (content_video).

Accordingly, as shown in FIG. 5, the collaboration service providing server 100 according to the present invention may execute the collaboration request execution object displayed in the outer region that does not overlap with the performer object (object_performer) displayed on the video content (content_video) screen. object_request_collaborate) Further receiving a collaboration request (request_collaborate) of a collaboration requester (user_request_costarring) generated according to the selection.

The collaboration service providing server 100 according to the present invention stores the producer identifier (id_producer) of the producer according to the selection of the collaboration request execution object 320 displayed in the outer area of the video content (content_video). It is desirable to further identify through.

For example, as shown in the producer data (data_producer) structure diagram 134 of FIG. 5, a producer category including composition, writing, editing, and lighting, a producer identifier (id_producer) corresponding to each producer category, and a corresponding producer contact Information (info_contact_producer).

On the other hand, recently, an increasing number of cases include additional execution objects in the video content (content_video). The execution object is implemented by being embedded or overlayed on the video content (content_video) screen, and configured to perform additional operations when the user selects the execution object.

Accordingly, in operation S10, the collaboration service providing server 100 may select at least a portion of the display area of the first performer object object_performer_first included in the first video content content_video_first and the first performer. It is desirable to associate a collaboration request execution object (object_request_collaborate) that executes a collaboration request (request_costarring) for (performer_first).

In the second step (s20), receiving the collaboration request (request_costarring) for the first performer object (object_performer) generated by the collaboration request execution object (object_request_costarring) according to the selection of the performer selection of the collaboration requester (user_request_costarring) desirable.

According to this embodiment, the collaborative requester (user_request_costarring) is an intuitive method of selecting a desired performer's video area by associating the collaboration request execution object (object_request_costarring) with the display area of the performance object (object_performer) included in the video content (content_video). The user may select a collaborator, and even if only the video content (content_video) is shared to another web page beyond the video content (content_video) providing web page, the collaboration request (request_costarring) may be sent to the performer who is the video content (content_video) performer.

Meanwhile, it is not necessary to designate all the collaboration target performers in a single video content (content_video), but it is preferable to designate the collaboration target performers in the plurality of video contents (content_video). To this end, the collaboration service providing server 100 according to the present invention may perform performers corresponding to performer object identifiers (id_performer_objects) identified by collaboration requests (request_costarrings) received from a plurality of video contents (content_video), respectively. It is preferable to register with the performance collaboration group (group_collaborate_performance) of user_request_costarring.

In this embodiment, in the first step (s10) the collaboration service providing server 100 identifies the second performer object (id_performer_object_second) and the second performer object (object_performer_second) of the second video content (content_video_second) and the second The second performer data (data_performer_second) including the performer contact information (info_contact_performer_second) may be stored in the collaborator database 130 in association with the second video content (content_video_second).

Subsequently, after the fourth step s40 or after the fifth step s50, the collaboration service providing server 100 receives the second video content content_video_second from the collaboration requester user_request_costarring that plays the second video content content_video_second. An eighth step of receiving a collaboration request (request_costarring) for the second performer object (object_performer_second) to be represented is performed.

Next, the collaboration service providing server 100 identifies the second performer object identifier id_performer_second of the second performer object (object_performer_second) through the collaborator database 130 according to the collaboration request (request_costarring) of the collaboration requester user_request_costarring. Perform the ninth step.

Next, the collaboration service providing server 100 registers the second performer corresponding to the second performer object identifier (id_performer_second) identified as the target of the collaboration request (request_costarring) to the performance collaboration group (group_collaborate_performance) of the collaboration requester (user_request_costarring). The tenth step is performed.

Finally, the collaboration service providing server 100 receives the second request of the performer through the second performer contact information (info_contact_performer_second) of the second performer registered in the performance collaboration group (group_collaborate_performance) of the collaboration requester (user_request_costarring). The eleventh step of notifying the performer is performed.

According to this embodiment, as shown in FIG. 6, the collaborative requester user_request_costarring selects the guitar player 311 in the video content_A, the singer 312 in the video content_B, and the drummer 313 in the video content_C. Each can be selected. Accordingly, each of the performer object identifiers (id_performer_object, Kim Kita, Nagasu, and drums) is registered in the performance collaboration group (group_collaborate_performance) 135 of the collaboration requester (user_request_costarring).

According to this embodiment, the collaboration service providing server 100 before the first step (s10) or before the second step (s20), the collaboration requester (performer_user_request_costarring) set by the collaboration requester setting performing per category (category_reference) performer slot ( A twelfth step of generating a performance collaboration group (group_collaborate_performance) including slot_performer is performed. Next, the collaboration service providing server 100 registers the first performer identified as the target of the collaboration request (request_costarring) in the fourth step (s40) in the performer slot slot_performer according to the collaboration requester setting performing category (category_reference).

The collaboration service providing server 100 receives a collaboration request (request_costarring) further including a collaboration requester designation category (category_designate) of the first performer according to the designation of the collaboration requester (user_request_costarring). Next, the collaboration service providing server 100 registers the first performer in the perforator slot slot_performer of the collaboration requester setting performing category corresponding to the designated performing category in the fourth step (s40).

To this end, in order to register their own performing category as a performer registration performing category when registering their own performer data (data_performer), the first step (s10) may be performed by the collaboration service providing server 100 by the first performer object (object_performer_first). Performer registration further stores the first performer data (data_performer) further comprising the performing category (category_register) in the collaborator database 130, the fourth step (s40) is the collaboration service providing server 130, performing the perm registration registration It is preferable to register the first performer in the perforator slot slot_performer of the cooperative requestor setting performing category corresponding to the category (category_register).

To this end, the collaboration service providing server 100 registers the first video content (content_video_first) including the first performer of the performing category (category_register) corresponding to the collaboration requester setting performing category (category_register) before the second step (s20). It is preferable to perform the thirteenth step of recommending the to the collaboration requester (user_request_costarring).

Through such an embodiment, the performer registration corresponding to the collaborative requester setting performing category (category_register) of the cooperative requestor (user_request_costarring) recommends the video content (content_video) including the performer of the performing category (category_register) to the collaborative requester (user_request_costarring). Not only can the recommended types of performers be recommended and integrated in their video content (content_video), but they can also develop creative and cooperative performers by appealing their specialty.

To this end, the collaboration service providing server 100 recommends the video content (content_video) including the performer registration performing category (category_register) conforming to the collaboration requester setting performing category (category_reference) to the collaboration requester (user_request_costarring) Do.

To this end, the collaboration service providing server 100 recommends the 14th step of recommending the first performer of the performing category to the performer slot (slot_performer) corresponding to the collaboration requester setting performing category (category_register) before the second step (s20). It is preferable to carry out.

In this embodiment, the performer registration conforming to the collaborative requester setting performing category (category_register) performers of the category (category_register) to the performer slot (slot_performer) to immediately recommend the desired type of performers.

To this end, the collaboration service providing server 100 according to the present invention is the entire collaboration request (request_costarring_all), which is a collaboration request (request_costarring) for all performer objects (object_performer) expressed in the video content (content_video) in the second step (s20). It is preferable to insert the entire collaborative request execution object (object_request_costarring_all) that generates the data into the video content (content_video), and receive the entire collaborative request (request_costarring_all) according to the selection of the entire collaborative request execution object (object_request_costarring_all) of the collaborative requestor (user_request_costarring). Do.

According to this embodiment, the collaboration requester (user_request_costarring) is received by receiving the entire collaboration request (request_costarring_all), which is a request_costarring for all the performer objects (object_performers) expressed in the video content (content_video) from the collaboration requester (user_request_costarring). Quickly organize collaborators without having to search for video content (content_video) to create an integrated and immediate performance collaboration group (group_collaborate_performance).

To this end, the collaboration service providing server 100 further includes first performance history information (experience_performance_first), which is history information of the first performer object (object_performer_first), in the first performer data (data_performer_first) in the first step (s10). It is desirable to store in the database 130.

In a second step (s20), the collaboration service providing server 100 receives and receives a history request interaction for the first performer object expressed in the first video content (content_video_first) from the collaboration requester (user_request_costarring). s24).

Next, the second sub-step of the collaboration service providing server 100 to identify the first performer object (object_performer_first) through the first performer object identifier (id_performer_object_first) stored in the collaborator database 130 according to the history request interaction input ( s32).

The third sub-step s33 is performed to receive the first performance history information through the collaborator database 130 and overlay the first performance history information on the first video content content_video_first.

The description of the invention herein describes the preferred embodiment, and the invention is not limited to this embodiment. Those skilled in the art to which the present invention pertains can make various changes and modifications to the above embodiments without departing from the technical spirit of the present invention, the technical idea of the present invention is to make all such various changes and modifications Include.

Claims

A communication module for communicating with a terminal through a network;

A video content providing module for transmitting a video content and web page data to the terminal to provide a video content service;

A collaborator database for storing performer data including a performer object identifier and a contactor contact information identifying at least one performer object represented on a screen of the video content in association with the video content;

A collaboration request receiving module for receiving a collaboration request input to a terminal of a collaboration requester-a collaboration request for a performer object selected from the collaboration requester among the performer objects represented in the video content;

A performer object identification module for identifying a performer object identifier of the performer object selected according to the collaboration request received through the collaboration through the collaboration object database;

A collaboration group generation module that registers the performer object identifier identified as a target of the collaboration request to the performance collaboration group of the collaboration requester; And

And a notification module for notifying the terminal of the performer corresponding to the performer object identifier to receive the collaboration request through the performer contact information of the performer object identifier registered in the performance collaboration group. Server based collaboration service provider.
The method of claim 1, wherein the notification module,

Performer object-based collaboration service providing server, characterized in that for accepting or rejecting the collaboration request from the terminal of the performer or each terminal of the performers that received the collaboration request through the network.
The method of claim 2, wherein the collaboration group creation module,

And a collaboration schedule setting interface unit configured to provide a collaboration interface for setting a collaboration collaboration schedule to each terminal of the collaboration requester and the terminals of the performers or the terminals of performers who have accepted the collaboration request. Performer object-based collaboration service providing server.
The method of claim 1,

The collaborator database further stores producer data including a producer identifier identifying a producer of the video content and producer contact information in association with the video content,

The collaboration request receiving module is a collaboration request input to the terminal of the collaboration requester? Receiving a collaboration request for the producer of the video content played on the terminal of the collaboration requester-further receives the collaboration,

The performer object identification module further identifies the producer identifier of the producer through the collaborator database according to the collaboration request received through collaboration.

The collaboration group generation module further registers the producer identifier identified as a target of the collaboration request to the performance collaboration group of the collaboration requester,

The notification module, the collaboration object-based collaboration, characterized in that notifying the terminal of the producer corresponding to the producer identifier of the reception of the collaboration request through the producer contact information of the producer identifier registered in the performance collaboration group Service provision server.
The method of claim 1,

The collaboration service providing server further includes an execution object insertion module for inserting a collaboration request execution object into the video content.

The collaboration request receiving module further receives a collaboration request input to the terminal of the collaboration requester-the collaboration request generated according to the selection of the collaboration request execution object in the collaboration requester terminal. Server based collaboration service.
The method of claim 5,

The collaboration service providing server may further include an execution object insertion module for inserting a collaboration request execution object into at least a portion of a display area of the performer object included in the video content.

The collaboration request receiving module further receives a collaboration request input to the terminal of the collaboration requester-the collaboration request generated according to the selection of the collaboration request execution object in the collaboration requester terminal. Server based collaboration service.
The method of claim 1,

The collaboration group generation module, the performer object-based collaboration service providing server, characterized in that to register the performer object identifiers identified by the collaboration request received from a plurality of video content to the performance collaboration group of the collaboration requester.
The method of claim 1,

The collaboration group generation module generates a performance collaboration group configured to include a per-operator slot for each category of collaboration requester setting performing by the collaboration requester before receiving the collaboration request, and upon reception of the collaboration request, The performer object-based collaboration service providing server, characterized in that for registering the target object identifier identified as a target in the performer slot according to the collaboration requester setting performing category.
The method of claim 8,

The collaborative request receiving module receives the collaborative request from the collaborative requester terminal further including a collaborative requestor designated performing category of the performer according to the designation of the collaborative requester.

The collaboration group creation module, the performer object-based collaboration object providing server, characterized in that to register the performer object identifier in the performer slot of the collaboration requester setting performing category corresponding to the designated performing category.
The method of claim 8,

The collaborator database further includes a performer registration performing category of the performer object to store as the performer data,

The collaboration group generation module, the performer object-based collaboration service providing server, characterized in that to register the performer object identifier in the performer slot of the collaboration requester setting performing category corresponding to the performer registration performing category.
The method of claim 10, wherein the collaboration service providing server,

Performer object-based collaboration configured to further include; video content recommendation module for recommending to the collaboration requester video content including the performer registration performer object identifier of the performer registration performing category corresponding to the collaboration requester setting performing category; Service provision server.
The method of claim 10, wherein the collaboration service providing server,

Performer object-based collaboration service providing server, characterized in that the configuration further comprises a; performer registration module conforming to the collaboration requester setting performing category performer object identifier of the performing category to the performer slot.
The method of claim 1,

The collaboration service providing server may include: an execution object insertion module for inserting an entire collaboration request execution object for generating an entire collaboration request, which is the collaboration request for all or some of the performance objects expressed in the video content, into the video content. Including more,

The collaboration request receiving module, the collaboration object providing server, characterized in that for receiving the entire collaboration request according to the selection of the entire collaboration request execution object of the collaboration requester from the terminal of the collaboration requester.
The method of claim 1,

The collaborator database further stores performance history information, which is history information of the performer object, in the performer data,

The collaboration service providing server may further include an execution object insertion module for inserting a history request execution object for requesting the performance history information into at least a portion of a display area of the performer object included in the video content.

The execution object insertion module comprises a; overlay processing unit for receiving the performance history information through the collaborator database and overlay on the video content; Performer object-based collaboration service providing server, characterized in that it comprises a.
The collaboration service providing server may include first performer data including a first performer object identifier identifying the first performer object of the first video content including the first performer object represented on the screen and first performer contact information. A first step of storing in the collaborator database in association with the first video content:

A second step of receiving, by the collaboration service providing server, a collaboration request for the first performer object represented in the first video content from a terminal of a collaboration requester playing the first video content;

A third step of the collaboration service providing server identifying the first performer object identifier of the first performer object according to the collaboration request through the collaboration subject database;

A fourth step of the collaboration service providing server registering the first performer object identifier identified as a target of the collaboration request with the performance collaboration group of the collaboration requester; And

And a fifth step of, by the collaboration service providing server, notifying the terminal of the first performer of the reception of the collaboration request through the first performer contact information of the first performer object identifier registered in the collaboration group. Performer object-based collaboration service providing method characterized in that the configuration.
The method of claim 15, wherein the method for providing a collaboration object based on a performer object includes:

A sixth step of receiving, by the collaboration service providing server, an acceptance or rejection of the collaboration request from the terminal of the first performer or the respective terminals of the first performers which have notified the reception of the collaboration request through a network; Performer object-based collaboration service providing method comprising a.
The method of claim 16, wherein the method for providing a collaboration object based on a performer object includes:

Providing, by the collaboration service providing server, a collaboration schedule setting interface for setting a collaboration schedule between the collaboration requester and the terminal of the first performer or the respective terminals of the first performers that have accepted the collaboration request; Performer object-based collaboration service providing method characterized in that the configuration further comprises.
The method of claim 15,

In the first step, the collaboration service providing server further stores producer data including a producer identifier identifying a producer of the first video content and producer contact information, in association with the first video content, in the collaborator database. ,

In the second step, the collaboration service providing server further receives a collaboration request for the producer of the first video content from the terminal of the collaboration requester playing the first video content,

In the third step, the collaboration service providing server further identifies the producer identifier through the collaborator database according to the collaboration request for collaboration with the producer,

In the fourth step, the collaboration service providing server further registers the producer identifier identified as a target of the collaboration request to the performance collaboration group of the collaboration requester.

In the fifth step, the collaboration service providing server notifies the terminal of the producer of the receipt of the collaboration request through the producer contact information of the producer identifier registered in the performance collaboration group of the collaboration requester. Performer object-based collaboration service providing method.
The method of claim 18,

In the second step, the collaboration service providing server overlays and displays a selection area for selecting the producer on the first video content, and displays the collaboration request generated according to the selection area of the collaboration requester. Performer object-based collaboration service providing method, characterized in that receiving from the terminal of the collaboration requester.
The method of claim 15,

In the first step, the collaboration service providing server executes the collaboration request area and the collaboration request for the first performer, which is at least a portion of the display area of the first performer object included in the first video content. Associate the collaboration request execution object

In the second step, the collaboration service providing server, the collaboration requester terminal of the collaboration request for the first performer object generated by the collaboration request execution object according to the selection of the performer selection area of the collaboration requester terminal Method for providing a collaboration object-based collaboration service, characterized in that receiving from.
The method of claim 15,

In the first step, the collaboration service providing server associates the second performer data including the second performer object identifier identifying the second performer object of the second video content and the second performer contact information with the second video content. To further store in the collaborator database;

The method of providing a collaboration object based on the performer object,

After the fourth step or after the fifth step, the collaboration service providing server inputs a collaboration request input to the terminal of the collaboration requester-the collaboration request for the second performer object represented in the second video content. An eighth step of receiving;

A ninth step of the collaboration service providing server identifying the second performer object identifier of the second performer object through the collaborator database according to the collaboration request received through the collaboration;

A tenth step of the collaboration service providing server registering the second performer object identifier identified as a target of the collaboration request with the performance collaboration group of the collaboration requester; And

An eleventh step of the collaboration service providing server notifying the terminal of the second performer of the reception of the collaboration request through the second performer contact information of the second performer object identifier registered in the performance collaboration group of the collaboration requester; Performer object-based collaboration service providing method characterized in that the configuration, including.
The method of claim 15,

The method for providing a collaboration object based on the performer object may include configuring the collaboration requester setting per-performer slots by the collaboration service providing server before the first step or before the second step. And a twelfth step of creating a performance collaboration group.

In the fourth step, the collaboration service providing server registers the first performer object identifier identified as a target of the collaboration request to the performer slot according to the collaboration requester setting performing category. How to provide collaboration services.
The method of claim 22,

In the second step, the collaboration service providing server receives the collaboration request from the terminal of the collaboration requester, further including a collaboration requester-specific performing category of the first performer according to the designation of the collaboration requester.

In the fourth step, the collaboration service providing server provides a performer object-based collaboration service, wherein the first performer object identifier is registered in a performer slot of the collaboration requester setting performing category corresponding to the designated performing category. Way.
The method of claim 22,

In the first step, the collaboration service providing server further stores the first performer data in the collaborator database, wherein the first performer data further includes a performer registration performing category of the first performer object,

In the fourth step, the collaboration service providing server registers the first performer object identifier in a performer slot of the collaboration requester setting performing category corresponding to the performer registration performing category. How to Provide.
The method of claim 24, wherein the method for providing a collaboration object based on a performer object includes:

Before the second step, the collaboration service providing server recommends, to the terminal of the collaboration requester, first video content including the first performer object identifier of the performer registration performing category corresponding to the collaboration requester setting performing category. The thirteenth step; Performing method for providing a collaboration object based collaboration service further comprising.
The method of claim 24, wherein the method for providing a collaboration object based on a performer object includes:

Prior to the second step, the collaboration service providing server, step 14 for recommending the first performer object identifier of the performer registration performing category corresponding to the collaboration requester setting performing category to the performer slot; Method of providing a collaboration object based on the perfomator.
The method of claim 15, wherein the second step,

The collaboration service providing server may receive from the collaboration requester terminal an entire collaboration request which is the collaboration request for all the first performer objects expressed in the first video content from the collaboration requester. To provide collaborative services.
The method of claim 15,

In the first step, the collaboration service providing server further includes first performance history information, which is history information of the first performer object, in the first performer data, and stores the first performance data in the collaborator database. A first sub-step of the collaboration service providing server receiving a history request interaction with respect to the first performer object expressed in the first video content from the collaboration requester terminal; A second sub-step of the collaboration service providing server identifying the first performer object through the first performer object identifier stored in the collaborator database according to the history request interaction input; And a third sub-step of the collaboration service providing server receiving the first performance history information through the collaboration target database and overlaying the first video content on the first video content. How to Provide Services.