WO2016099116A1 - Apparatus and method for providing object-oriented personalized broadcasting and, medium in which metadata therefor is stored - Google Patents

Abstract

The present invention provides an apparatus and method for providing object-oriented personalized broadcasting, and a medium in which metadata therefor is stored. An apparatus for providing object-oriented personalized broadcasting according to an aspect of the present invention comprises a database including at least one piece of first metadata and at least one piece of second metadata which are TV-Anytime metadata for a content, wherein the first metadata includes information on the content, the second metadata includes information in units of segments for each object included in the content, and the segment is a unit including frames for each camera, from a start frame in which each object appears in the content to an end frame in which the corresponding object disappears from the content.

Description

Object-oriented customized broadcast providing device, method and media storing metadata therefor

The present invention relates to a user-tailored broadcasting technology, and more particularly, to an apparatus and method for providing an object-oriented tailored broadcasting capable of providing a broadcasting service of a TV-Anytime standard, and a medium storing metadata therefor.

In general, a customized broadcast service enables a user to search / view a desired program without time constraints by using metadata collected from program information.

To this end, metadata for a customized broadcasting service is searched based on data inputted by a user to obtain desired information, and a customized broadcasting service is provided based on the result.

SUMMARY OF THE INVENTION The present invention has been made in view of the above-described technical background, and an object-oriented customized broadcast providing apparatus capable of providing a broadcast service for an object of interest of a user, and a method for providing a medium storing metadata therefor. do.

The object of the present invention is not limited to the above-mentioned object, and other objects that are not mentioned will be clearly understood by those skilled in the art from the following description.

An apparatus for providing object-oriented customized broadcasting according to an aspect of the present invention includes a database including at least one first metadata and at least one second metadata, which are metadata of a TV-Anytime standard for content. Wherein the first metadata includes information of the content, and the second metadata includes information in a segment unit for each object included in the content, wherein the segment includes the content. Each object is characterized in that it is a unit from the start frame appearing for each camera to the end frame disappears.

According to another aspect of the present invention, there is provided a method for providing an object-oriented customized broadcasting, wherein the control means includes at least one first metadata and at least one first metadata which is metadata of a TV-Anytime standard for each content in a database. And storing metadata, wherein the first metadata includes information of the content, and the second metadata includes information on a segment basis for each object included in the content. And a segment is a unit from a start frame in which each object included in the content appears for each camera to a disappearing end frame.

According to the present invention, a broadcast service for an object of interest of a user may be provided.

1 is a block diagram showing an object-oriented customized broadcasting system according to the present invention.

2 is a block diagram showing an object-oriented customized broadcast providing apparatus according to a first embodiment of the present invention.

3A is a block diagram showing an object-oriented customized broadcast providing apparatus according to a second embodiment of the present invention.

3B is a diagram for explaining a description system of metadata according to the present invention;

4A is a structural diagram of metadata according to the present invention;

4B illustrates an example of metadata in accordance with the present invention.

5A is a ProgramInformation metadata structure diagram in accordance with the present invention.

5B illustrates an example of ProgramInformation metadata in accordance with the present invention.

6A is a structural diagram of SegmentInformation metadata according to the present invention.

6B is a structural diagram of SegmentInformation metadata according to the present invention.

6C illustrates an example of SegmentInformation metadata in accordance with the present invention.

6D is a structural diagram of SegmentGroupInformation metadata according to the present invention.

6E illustrates an example of SegmentGroupInformation metadata in accordance with the present invention.

BRIEF DESCRIPTION OF THE DRAWINGS The above and other objects, advantages and features of the present invention, and methods of achieving them will be apparent with reference to the embodiments described below in detail with the accompanying drawings. However, the present invention is not limited to the embodiments disclosed below, but may be implemented in various forms. It is provided to fully convey the scope of the invention to those skilled in the art, the invention being defined only by the scope of the claims. Meanwhile, the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. In this specification, the singular also includes the plural unless specifically stated otherwise in the phrase. As used herein, “comprises” and / or “comprising” refers to a component, step, operation and / or device that is present in one or more other components, steps, operations and / or elements. Or does not exclude additions.

Embodiments of the present invention will now be described in detail with reference to the accompanying drawings. 1 is a block diagram illustrating an object-oriented customized broadcasting system according to an embodiment of the present invention.

As shown in FIG. 1, an object-oriented customized broadcasting system according to an exemplary embodiment of the present invention includes an object-oriented customized broadcasting providing apparatus 20 or 30 and a user terminal 10.

The user terminal 10 is used by a user (viewer) and transmits the interest information input by the user to the object-oriented customized broadcast providing apparatus 20 through a communication network.

Here, the interest information may include at least one of a name of an object of interest (eg, an actor's name) and a scene name in which the object of interest appears in the content to be watched. Since an embodiment of the present invention aims to provide an object-oriented customized broadcasting service, the interest information may include information about at least one object of interest.

The object-oriented customized broadcast providing apparatus 20 receives and confirms the interest information from the user terminal 10 through a communication network. In addition, the object-oriented customized broadcast providing apparatus 20 may provide an object of interest to a desired camera viewpoint by combining camera images (contents) of the object of interest of the user through object identification / classification for each object of interest. A detailed configuration of the object-oriented customized broadcast providing apparatus 20 will be described later with reference to FIGS. 2 and 3A.

As described above, an embodiment of the present invention may provide a scene including an object of interest desired by a user in various forms at a desired time in a desired manner.

Hereinafter, an object-oriented customized broadcast providing apparatus according to a first embodiment of the present invention will be described with reference to FIG. 2. 2 is a block diagram showing an object-oriented customized broadcast providing apparatus according to a first embodiment of the present invention.

As shown in FIG. 2, the apparatus for providing object-oriented customized broadcasting according to the first embodiment of the present invention 20 includes a content generator 210, a metadata identifier 220, a metafile generator 230, and a storage 240. ) And service provider 250.

Hereinafter, the first embodiment of the present invention will be described with an example in which the object-oriented customized broadcast providing apparatus 20 includes the content generator 210. However, the object-oriented customized broadcasting providing apparatus 20 according to the present invention is provided with metadata about the pre-generated content and contents, and further includes metadata related to the object in the corresponding metadata, thereby providing meta-object for the object-oriented customized broadcasting. You can also create a file. In this case, the object-oriented customized broadcast providing apparatus 20 according to the present invention may not include the content generator 210.

The content generator 210 generates content and content metadata (or metafiles). This can be done by studios, entertainment companies, web designers, user-linked content producers and users.

Here, the content may be image content and may include a plurality of programs. In this case, the program refers to a field of content such as entertainment, drama, and movie.

In addition, the content may be produced as a result of photographing one photographing target (eg, a sporting event) with a plurality of cameras at various locations. That is, the content of the same photographing target may include content made of images photographed from a plurality of camera viewpoints. This type of content may be a photograph of a sporting event, a performance, or the like.

However, dramas and movies are produced by synthesizing at least one selected camera point of view, which may well express the director's intention, even if the photographs are produced by a plurality of cameras. Such content may be image content that cannot be selected with respect to a camera viewpoint.

Here, the content metadata may be information of the content itself, such as a content title, play time, and summary information. In this case, the content metadata may be metadata of the TV-Anytime standard.

The metadata identifier 220 collects information for object-oriented customized broadcasting service by performing object extraction and tracking on content, and generates at least one object metadata by using the collected information. In this case, the collected information may include at least one of information on an object, segment information on which each object appears, and information on a camera.

The metadata identifier 220 also indexes the generated at least one object metadata into each segment.

The structure of the above-described content metadata and object metadata will be described later with reference to FIGS. 4A to 6E.

The metafile generator 230 generates at least one content metadata and at least one object metadata generated for one content in a metafile, and stores the metafile in the storage 240. In this case, the metafile generator 230 generates one metafile for one content. Here, the metafile is a set of metafiles of the TV-Anytime standard and may be an XML document including a plurality of metadata in a tree structure.

The repository 240 stores metafiles and may further store content.

When the service provider 250 checks the interest information according to the user's request received from the user terminal 10, the service provider 250 searches for a content or a specific portion of the content corresponding to the interest information by using a metafile in the storage 240. It may be provided to the user terminal 10.

In this case, the service provider 250 may provide content including the object of interest, and among them, may provide content photographing the object of interest from a camera viewpoint according to a user's request. If a plurality of pieces of content of the object of interest are photographed by a camera viewpoint according to a user's request, and the time of capturing the objects of interest is different, the service provider 250 may display a plurality of pieces of content of the object of interest in order of time. By integrating, the viewer may integrate and provide contents of a desired camera viewpoint.

If the information of the interest object included in the interest information is plural, the service provider 250 may perform a multi-key based content search using the plurality of information as a key.

As described above, an embodiment of the present invention may provide an object-oriented customized broadcasting service in a desired form at a desired time by using a metafile of interest information and a modified TV-Anytime standard according to a user's request.

Hereinafter, an object-oriented customized broadcast providing apparatus according to a second embodiment of the present invention will be described with reference to FIG. 3A. 3A is a block diagram showing an object-oriented customized broadcast providing apparatus according to a second embodiment of the present invention.

As shown in FIG. 3A, the apparatus for providing object-oriented customized broadcasting according to the second embodiment of the present invention includes a metadata generating module 310 and a searching module 320.

The metadata generation module 310 generates information such as information about an object, segment information, and information about a camera, and stores the information in a predetermined field in a metafile of a pre-generated structure. In the present invention, TV-Anytime Part3. Metadata Part A can be extended to add information related to an object, and based on this, an object-oriented customized broadcasting service can be provided. Thus, the preset field is set to TV-Anytime Part3. It may be an extended part from the Metadata Part A part.

The metadata generation module 310 includes a data parser 311 and a metafile generator 312. Hereinafter, each component of the metadata generation module 310 will be described.

The data parser 311 performs object extraction and tracking from the content, resulting in obtaining, analyzing and collecting information about the object. As a result, the data parser 311 may collect information about the object, segment information, and information about the camera.

In this case, the data parser 311 may generate object metadata using the collected information and provide the metadata to the metafile generator 312.

The metafile generator 312 stores the collected information in a metadata structure of the object-centric image media according to the embodiment of the present invention. As a result, the metafile generator 312 may generate a metafile.

 Alternatively, the metafile generator 312 may receive the information collected from the data parser 311, generate the object metadata, and generate the object metadata, and then store the data in a preset field in the generated content metafile. have.

The search module 320 can include a data parser 321 and a searcher 322.

The data parser 321 recognizes an object of interest of the user by using the interest information received from the user terminal 10, and extracts a metafile including the object of interest from the metafiles in the database 330.

The searcher 322 searches for the content including the object of interest by using the extracted metafile and provides the searched content to the user terminal 10.

When the content including the object of interest includes the content of the plurality of cameras, the searcher 322 may provide the photographed content to better reveal the object of interest. Alternatively, the searcher 322 may allow the user to select a plurality of camera viewpoints, and as a result, provide content of the camera viewpoint selected by the user. If a plurality of pieces of content of the object of interest are captured by a camera viewpoint according to a user's request, and the time of capturing the objects of interest is different, the searcher 322 collects a plurality of pieces of content of the object of interest and collects them in chronological order. By integrating, the viewer may integrate and provide contents of a desired camera viewpoint.

The metadata generation module 310 and the search module 320 described above may be a control unit of a computing device or a computing program such as a computer.

Hereinafter, a description system of metadata according to an embodiment of the present invention will be described with reference to FIG. 3B. 3B is a diagram for explaining a description system of metadata according to an embodiment of the present invention.

As shown in the left figure of FIG. 3B, when a golf game over a total of 5 hours is captured by two cameras, image contents of two camera views may be produced.

In the game, Jason Kang appeared for 10 minutes to 1 hour, 2 hours 20 minutes to 3 hours 10 minutes, 3 hours 45 minutes to 4 hours 30 minutes after the start of the game.

Choi Kyung Joo appeared from 50 minutes to 1 hour 30 minutes and 4 hours 10 minutes to 5 hours.

Keegan Bradley also appeared from 1 hour 15 minutes to 2:10 and from 3:10 to 3:50.

As shown in the right figure of Fig. 3b, in the game (scene number (1)), looking at the metadata in the metafile for the video content of the two camera views, the metadata is the camera (Cam (1) and Cam (2) Regarding)), the object of interest 1-1 and the object of interest 1-2 can be defined in units of segments that disappear after appearance.

Hereinafter, a structure of a metafile for an object-oriented customized broadcast service according to an embodiment of the present invention will be described with reference to FIGS. 4A to 6E.

4A illustrates a structure of metadata in a metafile according to an embodiment of the present invention, and FIG. 4B illustrates an example of metadata in a metafile according to an embodiment of the present invention. FIG. 5A is a structure diagram of ProgramInformation metadata according to an embodiment of the present invention, and FIG. 5B is a diagram illustrating an example of ProgramInformation metadata according to an embodiment of the present invention. FIG. 6A is a structural diagram of SegmentInformation metadata according to an embodiment of the present invention, FIG. 6B is a structural diagram of SegmentInformation metadata according to an embodiment of the present invention, and FIG. 6C is an example of SegmentInformation metadata according to an embodiment of the present invention. 6D is a structural diagram of metadata of a SegmentGroupInformation standard according to an embodiment of the present invention, and FIG. 6E is a diagram illustrating an example of metadata of a SegmentGroupInformation standard according to an embodiment of the present invention.

The metafile for the object-oriented customized broadcast service may be stored in the storage 240 of FIG. 2 or the database 330 of FIG. 3A. Hereinafter, for convenience of description, a case where the metafile for the object-oriented customized broadcasting service is stored in the database 330 will be described as an example. Here, the metadata of the lower tree of each table is expressed as Type.

4A and 4B, the database 330 stores a ProgramInformation Table (first metadata) and a SegmentInformation Table (second metadata) that are metadata of a TV-Anytime standard for content. . In this case, the database 330 may further include content.

For reference, the TV-Anytime metadata standard includes ProgramInformation Table and SegmentInformation Table metadata. In this case, the TV-Anytime metadata may be metadata of the TV-Anytime standard starting with the TVAMain root element.

Here, as shown in Table 1, the subtree of the ProgramInformation Table may include metadata describing content, and the subtree of the SegmentInformation Table may include metadata describing a portion of the content.

Data field	Remarks / Example	Explanation
ProgramInformationTable	ProgramInformation	Metadata fields described about the program (content)
SegmentInformationTable	SegmentInformation	Metadata fields that describe a segment of the program

In detail, the SegmentInformation Table metadata may include information on a segment basis for each object included in the content. In this case, the segment may be a unit from the start frame where each object appears for each camera to the end frame disappearing in the content.

Hereinafter, the metadata of the ProgramInformation Table and the SegmentInformation Table subtree will be described.

As shown in Figs. 5A and 5B, the metadata of the ProgramInformation Table standard includes the scene number (Scene_num) of each scene of the content, the title of each scene (Title), the filename of the scene image (MediaTitle), and the description of each scene. (Synopsis), an information list (CreditsList) of objects appearing in each scene, storage path information (MediaTitle_URL) of representative images of each scene, a high resolution support mode (Resol_type), and a multi camera support mode (Multi_cam_type) of content. Contains information. Here, the information list of the object may include an object name, an object unique ID (PersonNameIDRef), an organization name, and the like.

As shown in FIG. 5A, each information may be stored as a separate field, and a function and an example thereof may be as shown in Table 2 below.

Data field	Remarks / Example	Explanation
Scene_num	One	Scene number field, which is an identification number for a scene of a program.
Title	2013 swimming championship	Name field for the scene.
MediaTitle	Media_Title.jpg	File name field for the scene representative image.
Synopsis	2013 World Swimming Championships Finals	This field is for the scene description.
CreditsList	CreditsItem	It is stored as a list according to the objects appearing as information of the objects appearing in the current scene.
MediaTitle_URL	/web_external/1/title/media_title.jpg	URL information about the scene representative image file. This field is stored as an absolute path in the management server.
Resol_type	One	This field defines whether to support high resolution. The field value has a bool type of 0 or 1.
Multi_cam_type	One	This field defines the multiple camera support mode. The field value is 0 or 1 as bool type.

As described above, the MediaTitle_URL field may include a storage path of the representative image in the form of a URL such as "/web_external/1/title/media_title.jpg". Here, the URL may be an absolute path in the object-oriented customized broadcast providing device 20 or 30.

Here, the bool type may be a data type represented by 0 or 1 value. As shown in Table 2, when the content supports high resolution, the resolution support mode (Resol_type) field may be set to 1 (true).

In addition, as shown in Table 2, when the content supports multiple cameras, the multi-camera support mode (Multi_cam_type) field may be set to 1 (true). Contents supporting multiple cameras may be contents obtained by photographing a subject from various angles, such as a sports event.

As shown in FIG. 6A, metadata of a SegmentInformationTable standard includes SegmentList and SegmentGrouplist.

SegmentList (first list) may be a field for storing segment information (SegmentInformation) for each scene in the content in the form of a list.

SegmentGroupList (second list) may be a field for storing segment group information (SegmentGroupInformation) for each scene in the content in the form of a list.

Here, the segment group may be a grouping of segments including the same object in each scene for each camera.

Hereinafter, segment information (SegmentInformation) and segment group information (SegmentGroupInformation) metadata included in each of the first and second lists will be described.

As shown in FIGS. 6B and 6C, the SegmentInformation metadata (Second-1 metadata) may include a unique number of a segment (SegmentID), a temporal position of the segment (SegmentLocator), a storage path of a representative image of each segment (KeyFrameLocator), and a segment. Includes at least one information of the unique number (PersonNameIDRef) of my appearance object. In this case, each information may be stored as a separate field, and the functions and examples thereof may be as shown in Table 3 below.

Data field	Remarks / Example		Explanation
SegmentID	One		Segment ID field that is an identification number for the segment. Defined as an element value of SegmentInformationType.
segmentLocator	Time	0	This field indicates the position of the segment in the image. This field contains two pieces of information about time and frame information. Information about time is stored in ms and frame information is stored as the number of each frame.
		696
	Frame	0
		200
keyFrameLocator	/web_external/1/segment/segment1.jpg		This field stores the location URL information about the segment representative image. This field is stored as an absolute path in the management server.
PersonNameIDRef	One		This field stores the ID information of the object appearing in the segment. The object ID is associated with the object unique ID of the object information in the program information.

As illustrated in FIG. 6C, the segment information metadata may further include a detailed description field including information such as a keyword and a name of each scene (Synopsis). However, this is not highly related to the object-oriented customized broadcast service, and the contents will be apparent to those skilled in the art from the conventional TV-Anytime broadcast service, so a detailed description thereof will be omitted.

As shown in Figs. 6D and 6E, the segment group information metadata (second-2 metadata) is captured by the unique number (GroupID) of the segment group, the storage path (MediaLocator) of the representative image of the segment group, and photographed by each camera. It may include at least one of the storage path (Src) of the content and the information (Segment) of the unique number of the segment included in the segment group.

As shown in FIG. 6E, each information in the segment group information metadata may be stored in separate fields, and the functions and examples thereof may be as shown in Table 4 below.

Data field	Remarks / Example	Explanation
groupId	One	Group ID field, which is an identification number for a segment group. Defined as an element value of SegmentGroupInformationType.
MediaLocator	/web_external/1/segment_group/1/segment_group1.jpg	This field stores the location URL information about the camera representative image. This field is stored as an absolute path in the management server.
src	/web_external/1/avi/yoga_fullshot_720p.mp4	This field is the path URL where the image from the camera is stored. This field is stored as an absolute path in the management server.
Segments	1 2 3	This field is used to store information about the ID of the segment belonging to the segment. Each segment is a segment from the current camera image.

An example of searching for a content including an object of interest and a portion of the object using the above-described structure will be described. When a user delivers interest information including a name of an object of interest, the search module 320 may execute meta in the database 330. Search for the metafile containing the name of the object of interest in the file, more specifically the name of the object of interest corresponding to the information of interest from the CreditsList field of the ProgramInformation metadata, and the content of the object and the uniqueness of the object of interest. Check the ID. The search module 320 checks the segment in which the object of interest actually appears from the SegmentInformation metadata, particularly, the PersonNaemIDRef field, and checks the temporal position of the segment. The content may be provided to the user, but the content may be played based on the identified temporal position.

At this time, when the search module 320 confirms that the content searched from the Multi_cam_type of the ProgramInformation metadata supports the multiple cameras, the search module 320 checks the segment for each camera from the SegmentInformation metadata, and receives a selection for the camera viewpoint of the user. Editing can be performed to collect the segments of the selected camera viewpoint while providing the edited content at about the same time.

As described above, the metadata in the database 330 according to the embodiment of the present invention may not only define each scene of the content in units of segments but also for each camera. Therefore, the exemplary embodiment of the present invention may select and view only the portion of the content including the object of interest by using the interest information requested by the user.

In addition, when an image of an object of interest is photographed at various camera angles exists, an embodiment of the present invention may provide image content obtained by photographing an object of interest at a desired camera angle. Therefore, the viewing choices of the user can be widened.

Furthermore, an embodiment of the present invention can support the viewing of video content that can be viewed by athletes, actors, acquaintances or family members who are interested in the video content of sports, performances, events, and the like.

In the above, the configuration of the present invention has been described in detail with reference to the accompanying drawings, which are merely examples, and those skilled in the art to which the present invention pertains various modifications and changes within the scope of the technical idea of the present invention. Of course this is possible. Therefore, the protection scope of the present invention should not be limited to the above-described embodiment but should be defined by the following claims.

Claims (10)

1. A database including at least one first metadata and at least one second metadata that is metadata of a TV-Anytime specification for the content,

   The first metadata includes information of the content,

   The second metadata includes information of a segment unit for each object included in the content.

   The segment is an object-oriented customized broadcast providing device which is a unit from a start frame where each object appears for each camera to the end frame disappears in the content.
2. The method of claim 1, wherein the at least one first metadata includes:

   The scene number of each scene of the content, the name of each scene, the file name of the representative image of each scene, the description of each scene, the information list of the objects appearing in each scene, the storage of the representative image of each scene And at least one of the path information and the multi-camera support mode of the content.
3. The method of claim 1, wherein the at least one second metadata is located in a subtree thereof.

   A first list containing segment information of each scene of the content; And

   A second list including information of a segment group for each camera of each scene;

   The object-oriented customized broadcast providing device comprising a.
4. The method of claim 3, wherein the 2-1 metadata which is each metadata in the first list is

   And at least one of a unique number of the segment, a temporal position of the segment in the content, a storage path of a representative image for each segment, and a unique number of an appearance object in the segment.
5. The metadata of claim 3, wherein the second-2 metadata, which is each metadata in the second list,

   Object-oriented tailored to include at least one of the unique number of the segment group, the storage path of the representative image of the segment group, the storage path of the content taken by each camera and the unique number of the segment number included in the segment group Broadcast providing device.
6. The control means storing in the database at least one first metadata and at least one second metadata which is metadata of TV-Anytime specification for each content,

   The first metadata includes information of the content,

   The second metadata includes information of a segment unit for each object included in the content.

   Segment is a unit of the object-oriented custom broadcast providing unit is a unit from the start frame to each object included in the content to the end frame disappears.
7. The method of claim 6, wherein the first metadata,

   The scene number of each scene of the content, the name of each scene, the file name of the representative image of each scene, the description of each scene, the information list of the objects appearing in each scene, the storage of the representative image of each scene And at least one of the path information and the multi-camera support mode of the content.
8. The method of claim 6, wherein the second metadata,

   A first list containing segment information of each scene of the content; And

   A second list including information of a segment group for each camera of each scene;

   The object-oriented customized broadcast providing method comprising a.
9. The method of claim 8, wherein the 2-1 metadata, which is each metadata in the first list,

   And at least one of a unique number of the segment, a temporal position of the segment in the content, a storage path of a representative image for each segment, and a unique number of an appearance object in the segment.
10. The method according to claim 8, wherein the second-2 metadata, which is each metadata in the second list,

    Object-oriented tailored to include at least one of the unique number of the segment group, the storage path of the representative image of the segment group, the storage path of the content taken by each camera and the unique number of the segment number included in the segment group How to provide a broadcast.

Images