JP4076152B2 - Content automatic linkage system and content linkage method - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a content cooperation technique. In particular, the present invention relates to a content automatic cooperation system, a content registration method, and a content cooperation method that realize cooperation between contents arbitrarily selected by a user on a user terminal.
[0002]
[Prior art]
In recent years, SMIL (Synchronized Multimedia Integration Language) has been widely used as a technology for linking multimedia contents such as video, audio, still images, text, and animation. By using SMIL, a plurality of multimedia contents can be reproduced in synchronization. Moreover, as a system that links video and audio with an application, for example, there is SVMV (Software Vision Multi-Vision) (see Patent Document 1).
By using SMIL and SVMV, a plurality of multimedia contents can be presented in cooperation with each other. In particular, it is possible to present a still image, text, animation, or the like related to the content of the video or audio content in synchronization with the reproduction of the video or audio content.
[0003]
[Patent Document 1]
Japanese Patent Laid-Open No. 2000-244889 (see paragraphs [0035] to [0045], FIG. 3 and FIG. 4)
[0004]
[Problems to be solved by the invention]
However, SMIL and SVMV specify the linkage between contents in advance by creating schedules (documents describing the relationship between time and events) and scenarios (documents describing system state transitions associated with events). There is a need to. At this time, the cooperation contents are fixed according to the schedule and the scenario. Therefore, in SMIL and SVMV, it is not possible to link contents that are not described in the schedule or scenario. Another problem is that the number of schedules and scenarios to be created increases in proportion to the number of content combinations.
[0005]
Therefore, in view of the above problems, the present invention provides a means for performing cooperation between contents arbitrarily selected by a user without requiring the creation of a schedule or scenario describing the cooperation between contents in advance. Objective.
[0006]
[Means for Solving the Problems]
  The present invention that solves the above problemsTomorrowIn response to a registration / cancellation operation of content to / from the automatic content linkage system by the user, the content registration / cancellation is performed according to the received operation, and when the content is newly registered, A content registration unit that outputs the file type to the linked component management unit, a linked component management unit that outputs the linked component corresponding to the file type input from the content registration unit to the browser unit, and a media viewer used to display the registered content In addition, a message communication path is provided between the linked components input from the linked component management unit, and the media viewer is used to cause the browser unit to display the registered content and to act on the displayed content. And an inter-component communication unit that transmits a cooperation message received from the cooperation component corresponding to the file type of the content to the cooperation component corresponding to the file type of the content registered in the content automatic cooperation system.An event receiving unit that acquires event information (for example, event name and data) generated in the content from the media viewer that displays the content, and a collaboration rule that links the content and metadata of the content Based on the event information that occurred An event / method conversion unit that converts information (for example, a linkage method and data), a linkage message that describes the linkage information, and a linkage message transmission unit that sends the created linkage message to the inter-component communication unit; The cooperative message received from the inter-component communication unit, and the cooperative message receiving unit that acquires the cooperative information described in the received cooperative message, and the cooperative information based on the cooperative rule and metadata (For example, control function name and data A method / function converter that converts the data to a media viewer, and a control information transmitter that transmits the control information to the media viewerIt is a content automatic cooperation system equipped with.
  In this configuration, the content registration unit has a content management table, and manages each registered content with an ID so that it can be uniquely identified. In addition, the linked component management unit has a linked component DB, and supports various file types by updating the contents of the DB or adding new linked components.
  It should be noted that in the embodiment of the invention described later, the content of “providing a message communication path between the media viewer used for content display and the linkage component” in the claims is simply “adding the linkage component to the content”. ”
[0007]
  Also,In this configuration, the cooperation component acquires event information generated in the content, transmits a cooperation message corresponding to the event information to the inter-component communication unit, and receives a cooperation message from the inter-component communication unit. Processing corresponding to the cooperation message is executed on the content. As described above, the cooperation messages are communicated between the cooperation components, and the contents are autonomously controlled based on the cooperation messages received by the cooperation components. As a result, the cooperation between the contents is realized. In other words, when a plurality of contents are registered in the content automatic cooperation system, an event that occurs in a certain content changes the state of its own content, and a cooperation message indicating the event information between the cooperation components of each content. The state of the content changes by controlling each content based on the cooperation message that is communicated with each other and received by each cooperation component. As a result, the contents can be linked.
  In addition, as a method for referring to metadata, in an embodiment of the invention described later, a metadata reference unit is provided in the cooperation component. This metadata reference unit refers to the metadata included in the content, converts the data acquired as event information into the corresponding metadata, sets the data to be described in the cooperation message to be transmitted, and the received cooperation message. The described data is converted into corresponding event data, and the data is described in the control information to be transmitted. At this time, it is assumed that event data and metadata are described in pairs in the metadata in the content.
[0008]
  Also bookThe invention provides an event output unit for outputting event information generated in the content displayed by the media viewer to the cooperation component, and a process described in the received control information. It is a content automatic cooperation system provided with the external control input part which performs this with respect to content.
  Here, as an event (action to the content) that occurs in the content, for example, input to the user's content (click operation or drag operation with a pointing device such as a mouse) or content state change (reproduction position of the video content) Change).
[0009]
  Also bookThe invention is an automatic content cooperation system in which a cooperation message is described by a cooperation method name and data independent of the content file type.
[0010]
  Also bookThe invention is an automatic content linkage in which linkage rules are described by at least two of an event name corresponding to a content action, a linkage method name independent of the content file type, and a control function name corresponding to content linkage processing. System.
  In this configuration, the event / method conversion unit and the method / function conversion unit of the cooperation component refer to the cooperation rule and perform conversion from the event name to the cooperation method name and from the cooperation method name to the control function name. At this time, by sharing the linkage method name between file types and changing the event name and control function name for each file type, the same linkage message is exchanged between each linkage component to link between the contents of different file types. It can correspond to. If there is only one content linkage content realized by the automatic content linkage system, describe only the “event name / control function name” in the linkage rule, and link from the linkage message corresponding to this description. It is also possible to remove the method and send only the data.
[0011]
  Also bookInvention is by the userReceives content registration / release operations to the content automatic linkage system, and registers / releases content according to the received operations, and outputs the file type of the registered content when newly registered And providing a message communication path between the media viewer used for displaying the registered content and the linkage component in the browser portion, and a step of outputting the linkage component corresponding to the file type to the browser portion described later. , A step of displaying the registered content by using the media viewer, and when an action to the displayed content occurs, a linkage message received from a linkage component corresponding to the file type of the content is And a step of transmitting to a linkage component corresponding to the file type of the content registered in the automatic linkage system, and executing the event information generated in the content by the linkage component, and a media viewer displaying the content. Create a linkage message that describes the linkage information, a step of converting the event information that occurred to linkage information, based on the linkage rule that links the content and the metadata of the content, A step of transmitting a cooperation message to the inter-component communication section; a step of receiving the cooperation message transmitted from the inter-component communication section; obtaining the cooperation information described in the received cooperation message; and a cooperation rule and metadata. On the basis of the And converting the coordination information to the control information, and transmitting the control information to the media viewerContent characterized by being executedCooperationIs the method.
[0013]
  Also bookThe inventionCoordination rulesIs a combination of at least two of the event name, the cooperation method name, and the control function name, and the combination of metadata that is data described with respect to predetermined data in the content and the data It is.
[0014]
DETAILED DESCRIPTION OF THE INVENTION
Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.
[0015]
≪Configuration and overview of automatic content linkage system≫
First, the configuration and outline of the content automatic cooperation system will be described. The content automatic linkage system registers content and links the registered content to each other. Specifically, the content automatic linkage system is realized by a computer such as a PC (Personal Computer).
FIG. 1 is a diagram showing a configuration of an automatic content cooperation system (hereinafter simply referred to as “system”) according to an embodiment of the present invention. This system receives a content registration / release operation to the system by a user, performs content registration / release according to the received operation, and when newly registering content, The content registration unit 1 that outputs the file type to the linkage component management unit 2, the linkage component management unit 2 that outputs the linkage component corresponding to the file type input from the content registration unit 1 to the browser unit 3, and used for displaying the registered content A message communication path is provided between the media viewer to be operated and the linked component input from the linked component management unit 2, and by using the media viewer, the browser unit 3 for displaying the registered content and the displayed content are displayed. The work of When configured cooperation message received from the cooperation component corresponding to the file type of the content, the inter-component communication unit 4 to be transmitted to the coordination components corresponding to the file type of the content that is registered in the system. The browser unit 3 includes an HTML (Hyper Text Markup Language) document linkage component 5, a PPT (POWERPOINT, registered trademark) document linkage component 6, a video content linkage component 7, an HTML document media viewer 8 such as a Web browser, a PPT application, and the like. A PPT document media viewer 9 and a video content media viewer 10 such as a video player.
[0016]
FIG. 2 is a diagram showing a configuration of the content registration unit according to the embodiment of the present invention. The content registration unit 1 includes a registration / release operation receiving unit 11 that receives user registration / release operations for content in the system, a content management table 13 that manages the registration status of content in the system, and the content management table 13. A content management unit 12 that registers and cancels content, and a file type notification unit 14 that determines a file type of the content and notifies the linked component management unit 2 when the content is newly registered.
FIG. 3 is a diagram showing a configuration of the cooperation component management unit according to the embodiment of the present invention. The linkage component management unit 2 receives the file type of the newly registered content from the linkage component DB 23 that manages the linkage component corresponding to each file type and the file type notification unit 14 of the content registration unit 1, and sets the file type as the file type. From the component search unit 21 that searches for a corresponding link component from the link component DB 23, the link component searched by the component search unit 21 is acquired from the link component DB 23, and the link component is transmitted from the component distribution unit 22 that transmits the link component to the browser unit 3. Composed.
[0017]
FIG. 4 is a diagram showing a configuration of an HTML document cooperation component and an HTML document media viewer according to the embodiment of the present invention. The HTML document cooperation component 5 refers to the event receiving unit 51 that acquires event information generated in the content from the HTML document media viewer 8 displaying the content, the event information and the cooperation rule 53, and also refers to the metadata. From the event / method conversion unit 52 that converts into cooperation information through interaction with the unit 54, the cooperation message transmission unit 55 that creates a cooperation message describing the cooperation information and transmits it to the inter-component communication unit 4, and the inter-component communication unit 4 The cooperative message receiving unit 56 that receives the transmitted cooperative message and acquires the cooperative information described in the cooperative message, refers to the cooperative rule of the cooperative information, and communicates with the metadata reference unit 54 to control information. Method to convert to The number conversion unit 57, a control information transmitting unit 58 for transmitting the control information in the HTML document media viewer 8.
The HTML document media viewer 8 receives the control information from the event output unit 81 and the HTML document cooperation component 5 that output event information generated by the action to the content to the HTML document cooperation component 5, and is described in the control information. It is assumed that an external control input unit 82 that executes processing for the content 83 is provided in advance. The content 83 displayed by the HTML document media viewer 8 includes data 84 that is the content itself, and metadata 85 that is data described with respect to the data 84. The HTML document cooperation component 5 and the HTML document media viewer 8 shown in FIG. 4 can be replaced with the PPT document cooperation component 6 and the PPT document media viewer 9, or the video content cooperation component 7 and the video content media viewer 10. Therefore, when describing the PPT document or video content, reference is made by replacing 5X (X = 1 to 8) and 8Y (Y = 1 to 5) in FIG. 4 with 6X and 9Y, or 7X or 10Y. It shall be.
[0018]
FIG. 6 is a diagram showing a configuration of the inter-component communication unit according to the embodiment of the present invention. The inter-component communication unit 4 refers to the message receiving unit 41 that receives a cooperation message transmitted from each cooperation component and the content management table 13 of the content registration unit 1 and acquires information about each content currently registered in the system. Content ID acquisition unit 42, and a message distribution unit 43 that transmits a cooperation message to the content indicated by each ID acquired by the content ID acquisition unit 42.
[0019]
≪Content registration process≫
Next, processing for registering an HTML document will be described with reference to the flowchart of FIG.
First, referring to FIG. 1 and FIG. 7, the user drops the HTML file icon on the system desktop into the window of the browser unit 3 (see step S101, FIG. 9A). An operation for registering an HTML file is performed. At this time, as a method for registering / releasing content to the system, registration is performed by dragging a file icon or hypertext on a Web browser and dropping it on the browser unit 3 to close the window displaying the content. In this case, there are a method of canceling the content and a method of registering / releasing the file name and URL (Uniform Resource Locator) of the content using a dialog.
[0020]
Next, registration processing of HTML document content to the system will be described with reference to FIGS. The registration operation of the HTML file from the user is received by the registration / release operation receiving unit 11 of the content registration unit 1, and then the content management unit 12 uniquely identifies the HTML file name and the HTML content. An ID corresponding to the HTML file name is described in the content management table 13 (step S102). Further, the file type notifying unit 14 determines the file type (“HTML”) of the HTML file and notifies the determined file type to the cooperative component management unit 2 (step S103). As a means for determining the file type, a method of referring to the extension of the file name, a method of referring to the attribute information described in the header of the file, and the like can be considered.
[0021]
Subsequently, in the cooperative component management unit 2 shown in FIGS. 3 and 7, the component search unit 21 queries the cooperative component DB 23 for a cooperative component corresponding to the file type (“HTML”) received from the file type notification unit 14. The component distribution unit 22 acquires the corresponding link component, in this case, the HTML document link component 5, and transmits it to the browser unit 3 (step S104).
[0022]
At this time, the browser unit 3 attaches the HTML document link component 5 received from the link component management unit 2 to the HTML document content, and displays the HTML file on the browser unit 3 using the HTML document media viewer 8 (steps). S106, see FIG. 9B). Here, as an actual process of “granting”, a logical path is provided between the HTML document media viewer 8 displaying the HTML file and the HTML document cooperation component 5, and messages and data between them are provided. Communication is enabled (step S105).
[0023]
Here, by dropping the PPT file icon and video content icon on the desktop onto the browser unit 3, the PPT file and video content are displayed on the browser unit 3 through the same processing as the HTML document content, The PPT document linkage component 6 is assigned to the PPT file, and the video content linkage component 7 is assigned to the video content.
[0024]
≪Content linkage processing≫
Further, processing for linking an HTML document, a PPT document, and video content will be described with reference to the flowchart of FIG.
With reference to FIG. 4, a description will be given of processing when a user acts on an HTML document content, for example, a drag operation of a character string (“Mt. Fuji”) in an HTML document occurs. When the character string ("Mt. Fuji") is dragged (step S201), the event output unit 81 of the HTML document media viewer 8 creates event information ("Drag, Mt. Fuji") corresponding to the action and creates the created event information. The event information is output to the event receiver 51 of the HTML document cooperation component 5 (step S202). The event reception unit 51 of the HTML document cooperation component 5 outputs the event information (“Drag, Mt. Fuji”) received from the event output unit 81 to the event / method conversion unit 52. Then, the event / method conversion unit 52 converts the event name (“Drag”) into the cooperation method name (“SearchText”) based on the cooperation rule 53 (step S203). Further, the metadata reference unit 54 refers to metadata (data described regarding data) 85 added to the content 83 which is an HTML document. However, since metadata is not added to the content 83, the event information data ("Mt. Fuji") is used as it is as the linkage information data (step S204, no conversion). In the cooperation rule shown in FIG. 5, a combination of an event name to be processed in the event element, a cooperation method name described in the cooperation message in the method element, and a control function name to be executed as a cooperation operation in the function element are described.
[0025]
Next, the cooperation message transmission unit 55 creates a cooperation message describing the cooperation information (“SearchText, Mt. Fuji”) acquired by the event / method conversion unit 52 and transmits it to the inter-component communication unit 4 (step S205). Here, it is assumed that the address of the inter-component communication unit 4 is registered in the cooperation message transmission unit 55 in advance.
[0026]
At this time, in the inter-component communication unit 4 illustrated in FIG. 6, the message reception unit 41 receives the cooperation message transmitted from the HTML document cooperation component 5, and then the content ID acquisition unit 42 performs the content management of the content registration unit 1. Referring to the table 13, the ID of each content (HTML document, PPT document, video content) currently registered in the system is acquired (step S206). Then, the message delivery unit 43 transmits a cooperation message to each cooperation component corresponding to the content indicated by the acquired ID (step S207).
[0027]
Next, processing in each cooperation component after receiving the cooperation message will be described with reference to FIG. 4 again. When describing the PPT document or the video content, reference is made by replacing 5X (X = 1 to 8) and 8Y (Y = 1 to 5) in FIG. 4 with 6X and 9Y, or 7X or 10Y. It shall be.
First, in the HTML document cooperation component 5, the cooperation message receiving unit 56 receives the cooperation message transmitted from the inter-component communication unit 4, and acquires the cooperation information (“SearchText, Mt. Fuji”) described in the cooperation message. And output to the method / function converter 57. Then, the method / function converter 57 converts the cooperation method name (“SearchText”) into the control function name (“SearchHtmlText”) based on the cooperation rule 53 (step S208). In addition, the metadata reference unit 54 refers to the metadata 85 added to the content 83 that is an HTML document. However, since no metadata is added to the HTML document, the data of the linkage information ("Mt. Fuji") is used as it is as the control information data (step S209, no conversion). Then, the control information transmission unit 58 transmits the control information (“SearchHtmlText, Mt. Fuji”) to the HTML document media viewer 8 (step S210). Thereafter, the external control input unit 82 of the HTML document media viewer 8 receives the control information and executes the process described in the control information (step S211). Here, the character string “Mt. Fuji” described in the content 83 is retrieved and highlighted (see FIG. 9C).
[0028]
Next, in the PPT document cooperation component 6, the cooperation message receiving unit 66 receives the cooperation message transmitted from the inter-component communication unit 4, and the cooperation information (“SearchText, Mt. Fuji”) described in the cooperation message is received. Acquired and output to the method / function converter 67. Then, the method / function converter 67 converts the cooperation method name (“SearchText”) into the control function name (“SearchSlide”) based on the cooperation rule 63 (step S208). The metadata reference unit 64 refers to the metadata 95 added to the content 93 that is a PPT document. Here, a combination of a slide number and slide title information is given to the content 93 as metadata 95. Therefore, the metadata reference unit 64 converts the linkage information data ("Mt. Fuji") into a slide number ("3") using the data as metadata (step S209). As a result, the method / function converter 67 converts the linkage information (“SearchText, Mt. Fuji”) into control information (“SearchSlide, 3”). Then, the control information transmission unit 68 transmits the control information (“SearchSlide, 3”) to the PPT document media viewer 9 (step S210). Thereafter, the external control input unit 92 of the PPT document media viewer 9 receives the control information and executes the process described in the control information (step S211). Here, the third slide of the content 93 is displayed. For example, a photo of Mt. Fuji is pasted on the third slide (see FIG. 9C).
[0029]
Further, in the video content cooperation component 7, the cooperation message receiving unit 76 receives the cooperation message transmitted from the inter-component communication unit 4, and acquires the cooperation information (“SearchText, Mt. Fuji”) described in the cooperation message. And output to the method / function converter 77. Then, the method / function converter 77 converts the cooperation method name (“SearchText”) into the control function name (“SearchTime”) based on the cooperation rule 73 (step S208). Also, the metadata reference unit 74 refers to the metadata 105 added to the content 103 that is video data. Here, a combination of time information and a telop character string (such as subtitles) is given to the content 103 as metadata 105. Therefore, the metadata reference unit 74 converts the cooperation information data ("Mt. Fuji") into time information ("12:30") that uses the data as metadata (displayed as a telop) (step S209). As a result, the method / function converter 77 converts the linkage information (“SearchText, Mt. Fuji”) into control information (“SearchTime, 12:30”). Then, the control information transmission unit 78 transmits the control information (“SearchTime, 12:30”) to the video content media viewer 10 (step S210). Thereafter, the external control input unit 102 of the video content media viewer 10 receives the control information and executes the process described in the control information (step S211). Here, the content 103 is reproduced from 12:30. For example, Mt. Fuji is reflected in the scene at 12:30 (see FIG. 9C).
[0030]
As described above, the user's action on the HTML document causes a display change in the HTML document and a corresponding display change in the PPT document and the video content, thereby causing a change between the HTML document, the PPT document, and the video content. Cooperation is realized.
[0031]
The content automatic cooperation system according to the embodiment of the present invention can be realized by a computer and a program, and the program can be provided by recording the program on a computer-readable recording medium. is there. It is also possible to provide the program through a network.
[0032]
<< Other embodiments >>
An example of the preferred embodiment of the present invention has been described above, but the present invention is not limited to the above-described embodiment, and can be appropriately changed without departing from the spirit of the present invention. For example, the following embodiments can be considered.
(1) Although the HTML document, the PPT document, and the video content are given as the linked contents in the embodiment, various other contents such as an EXCEL file, a PDF document, a TEXT document, an audio content, and an animation are considered. It is done. Further, as a method of cooperation, not only cooperation by a character string drag operation on an HTML document but also various cooperation can be considered. For example, when a user is browsing video content, a corresponding character string is searched for and highlighted in the HTML document in cooperation with the display of the telop character string on the video content. Thus, cooperation such as searching and displaying a corresponding slide in the PPT document is conceivable. Such a cooperative operation can be realized by the same flow as the processing described in the above embodiment.
(2) It is possible to link not only contents registered in the system but also search services on the Internet. In this case, when a search service linkage component is newly created and the linkage message receiver of the search service linkage component receives the linkage message, the search service is queried for a character string described in the linkage message data (processing request). ) And presenting the search result of the search service to the user. Thus, for example, by dragging the word “Mount Fuji” in the WORD document, a map image of a result of searching for “Mount Fuji” as a keyword in the search service, or a result of searching for “Mount Fuji” as a keyword in the map search service The search service linked to the operation on the WORD document can be used.
(3) In the above embodiment, when the content ID is acquired by the inter-component communication unit 4, it is described that all the content IDs registered in the system are acquired. It is also possible. For this purpose, for example, IDs when registering contents are grouped, and IDs acquired in the inter-component communication unit 4 are limited to the ID group of the content that has been worked on, thereby collaborating with predetermined contents. To be able to select other content.
[0033]
【The invention's effect】
  BookAccording to the present invention, when a new content is registered, a message communication path is provided between the media viewer corresponding to the content and the linked component, and the linked message between the linked components via the inter-component communication unit. Therefore, it is possible to change the display of other contents by using an action on one content as a trigger. That is, the registered contents can be linked.
[0034]
  Also bookAccording to the invention, in each cooperative component, conversion from event information to a cooperative message and conversion from a cooperative message to control information can be performed, and a cooperative message can be exchanged between each cooperative component. Content can be linked without creating a schedule or a scenario in advance.
[0035]
  Also bookAccording to the invention, the media viewer not only displays the content but also outputs event information generated in the content and executes processing on the received control information on the content. The contents can be linked in a visible manner.
[0036]
  Also bookAccording to the invention, since the linkage message is described by the linkage method name and data, the linkage method is shared between the contents, and the linkage message is communicated between the linkage components so that any plurality of contents can be linked. Can do.
[0037]
  Also bookAccording to the invention, since the linkage rule is described by at least two of the event name, the linkage method name, and the control function name, by arbitrarily describing the combination of the event name, the linkage method name, and the control function name, The linkage rules are updated and expanded, and as a result, various content linkages become possible.
[0038]
  Also bookAccording to the invention, since the registered content is displayed, it is possible to confirm the content registered by the user. In addition, since a path for message communication is provided between the media viewer corresponding to the registered content and the linkage component, it is possible to provide an environment in which the registered content can be linked with other content.
[0039]
  Also bookAccording to the invention, when an action occurs on one content, as a result, the processing is performed for each content file type registered in the content automatic cooperation system. Can be linked.
[0040]
  Also bookAccording to the invention, since the rules based on the conversion from event information to linkage information and the conversion from linkage information to control information are linkage rules and metadata, the linkage rules and metadata are arbitrarily described. By doing so, various content linkages are possible.
[0041]
As described above, according to the present invention, it is not necessary to create a schedule or a scenario describing the cooperation between contents in advance, and various cooperation between contents arbitrarily selected by the user can be realized. Further, in the present invention, there is no master-slave relationship in cooperation between contents, and a combination of contents can be set freely. Furthermore, even when content is newly added, it is possible to immediately link without adding a schedule or a scenario.
[Brief description of the drawings]
FIG. 1 is a block configuration diagram of an automatic content cooperation system according to an embodiment of the present invention.
FIG. 2 is a block configuration diagram of a content registration unit according to the embodiment of the present invention.
FIG. 3 is a block configuration diagram of a cooperation component management unit according to the embodiment of the present invention.
FIG. 4 is a block configuration diagram of a cooperation component and a media viewer according to the embodiment of the present invention.
FIG. 5 is a diagram illustrating an example of a cooperation rule according to an embodiment of the present invention.
FIG. 6 is a block configuration diagram of an inter-component communication unit according to the embodiment of the present invention.
FIG. 7 is a flowchart showing content registration processing according to the embodiment of the present invention.
FIG. 8 is a flowchart showing content linkage processing according to the embodiment of the present invention.
FIG. 9 is a diagram showing the display contents of the desktop of the content automatic cooperation system according to the embodiment of the present invention.
[Explanation of symbols]
1. Content registration section
2 ... Linked Component Management Department
3. Browser part
4 ... Inter-component communication section
5 ... HTML document integration component
6. PPT document linkage component
7 ... Video content linkage component
8 ... HTML document media viewer
9 ... PPT document media viewer
10. Video content media viewer

Claims (6)

A content automatic linkage system that registers a plurality of contents arbitrarily selected by a user and links the registered contents to each other,
When the content registration / release operation to the content automatic cooperation system by the user is received, the content is registered / released according to the received operation, and the newly registered content is registered. A content registration unit that outputs to the linked component management unit to be described later,
A linked component management unit that outputs a linked component corresponding to the file type input from the content registration unit to a browser unit to be described later;
A browser that provides a path for message communication between the media viewer used to display the registered content and the cooperative component input from the cooperative component management unit, and displays the registered content by using the media viewer And
When an action to the displayed content occurs, the cooperation message received from the cooperation component corresponding to the file type of the content is sent to the cooperation component corresponding to the file type of the content registered in the automatic content cooperation system. An inter-component communication section to send;
With
The linkage component is
An event receiver that acquires event information generated in the content from the media viewer displaying the content;
An event / method conversion unit that converts the generated event information into cooperation information based on a cooperation rule that links the contents and metadata of the content;
Creating a cooperation message describing the cooperation information, and sending the created cooperation message to the inter-component communication section; and
A cooperative message receiving unit that receives the cooperative message transmitted from the inter-component communication unit, and acquires the cooperative information described in the received cooperative message;
Based on the linkage rule and metadata, a method / function conversion unit that converts the linkage information into control information;
A control information transmission unit for transmitting the control information to the media viewer;
Features and to Turkey content automatic linkage system further comprising a. The media viewer
An event output unit that outputs event information generated in the content displayed by the media viewer to the cooperation component;
An external control input unit that receives control information from the cooperation component and executes processing described in the received control information on the content;
The content automatic cooperation system according to claim 1, further comprising: 2. The content automatic cooperation system according to claim 1, wherein the cooperation message is described by a cooperation method name and data independent of a content file type. The linkage rule is described by at least two of an event name corresponding to the action on the content, a linkage method name independent of the content file type, and a control function name corresponding to the content linkage processing. The content automatic cooperation system according to claim 1 . A content linkage method in a content automatic linkage system that registers a plurality of contents arbitrarily selected by a user and links the registered contents to each other,
When the content registration / release operation to the content automatic cooperation system by the user is received, the content is registered / released according to the received operation, and the newly registered content is registered. A step of outputting the file type of
Outputting a linkage component corresponding to the file type to a browser unit described later;
In the browser unit, providing a path for message communication between the media viewer used for displaying the registered content and the cooperation component, and displaying the registered content by using the media viewer;
When an action to the displayed content occurs, the cooperation message received from the cooperation component corresponding to the file type of the content is sent to the cooperation component corresponding to the file type of the content registered in the automatic content cooperation system. Sending, and
Including and running
The linkage component is
Obtaining event information generated in the content from the media viewer displaying the content;
Based on the linkage rules for linking the contents and the metadata of the contents,
Converting the generated event information into linkage information;
Creating a cooperation message describing the cooperation information, and transmitting the created cooperation message to the inter-component communication unit;
Receiving the cooperation message transmitted from the inter-component communication unit, obtaining the cooperation information described in the received cooperation message;
Converting the cooperation information into control information based on the cooperation rules and metadata;
Sending the control information to the media viewer;
The content cooperation method characterized by performing including this. The linkage rule is a linkage rule that is a combination of at least two of an event name, a linkage method name, and a control function name, and a combination of predetermined data in the content and metadata that is data described for the data. The content linkage method according to claim 5 , wherein:

Images