JP4543761B2 - Content sharing system and content container creation method - Google Patents

Description

  The present invention relates to a content sharing system for sharing multimedia data among a plurality of users, and a method for creating a content container including a collection of specific contents shared between the plurality of users.

  2. Description of the Related Art Conventionally, a content sharing system for sharing content uploaded to a server such as the Internet among a plurality of users has been provided. When sharing content with a plurality of users on this content sharing system, a method is generally adopted in which a plurality of contents are collected and an access-permitted user is set for them (for example, patents). See references 1 and 2.)

  In this type of system, the user can classify his uploaded photos as albums or arbitrary categories and publish them on the server as athletic meet albums or travel albums, for example.

  However, in such a system, image / video data can be stored and shared for each group, but all procedures for creating a group such as an album must be manually performed by the user. Further, it is complicated because the user needs to manually associate contents with events.

  In order to be used by a general user, a method of creating a new content container such as a new group or album more easily is desired.

  For example, there is a method of creating a new group from an existing group. For example, in an electronic bulletin board system, a method has been proposed in which a new group is created in a group in such a manner that a specific message is disclosed only to a specific member (see, for example, Patent Document 3).

In addition, as a method for automatically classifying content, a method for classifying content based on the content has been proposed. For example, classification is performed by scene cutout of a moving image included in content (see, for example, Patent Document 4).
JP 2003-30195 A JP 2003-16002 A JP 2002-108766 A JP-A-6-121272

  However, the one described in Patent Document 3 can easily classify a message into keywords, but there is still a problem that the user must select and manually perform access permission user setting.

  Moreover, the thing of patent document 4 had the problem that it was difficult to classify | categorize the series of the photography which the user image | photographed. This is because, even in the case of photos that are actually taken, it may be recognized that they are not the same event because the shooting interval is long or different subjects are shot. Because. Moreover, in patent document 4, it does not show about the method of sharing the classified photograph between specific users.

  In view of such a point, the present invention allows a user to easily create a new container and a content container shared between users in the group without manually specifying each member individually, The purpose is to make it possible to easily classify content by event.

  In order to solve the above-described problems and achieve the object, the present invention newly adds a content including media data and metadata and a server in which access definition data in which an access-permitted user for the content is registered is recorded. When creating a content container consisting of a collection of specific content that can be shared among multiple users and receiving a content container creation command from a client operated by the user, a server is created according to the contents of the content container creation command. Users who interpret existing data stored internally or externally, extract access-permitted users based on the interpretation results of the existing data, create new access definition data, and are registered in the new access definition data Create new content containers that are shared between them.

  According to the present invention, without allowing the user to manually designate each individual member, the user can determine the access-permitted user by using the data accumulated by the communication of the content sharing system and other tools, etc. New content containers that can be shared among users can be created easily.

Above server, at least the event name and event ID, consisting of, event information for classifying the contents holds the event data table that will be registered, any client of the clients multiple users to operate New event information is registered in the event data table and new content is created from any of the clients operated by multiple users. Even when an event list request command is transmitted from time to time, all event information registered in the event data table is returned as candidates for event information associated with new content .

This makes it possible to easily classify content for each event. Furthermore, by sharing the event information among a plurality of users, it is possible to effectively save and use the event information performed in the group.

  According to the present invention, by using data accumulated by communication of a content sharing system and other tools, a user can easily specify an access-permitted user without specifying each member manually. Create new content containers that can be shared among other users. Therefore, there is an effect that the user can easily bundle the contents shared by a plurality of users on the content sharing system and perform a specific dialogue.

  Also, from the viewpoint of managing a large amount of content, instead of the conventional flow of content creation (shooting) → storage → classification → sharing, shared place creation → content creation (shooting) → storage + classification → a new shared place It becomes the flow of making. This not only simplifies the organization of content on a certain theme, but also supports the support of new content organization in a chained manner, and also provides a natural opportunity for users to organize content. There is an effect that it can be increased.

Also, holding the event data table event information for classifying the contents Ru is registered, information for generating a new event information from any client of the clients multiple users to operate is transmitted Therefore, even if event information is newly registered in the event data table and an event list request command is sent from any of the clients operated by a plurality of users when a new content is created, the event data all event information registered in the table, by sending back a candidate event information associating the new content may be categorized by easily events content. Furthermore, by sharing the event information among a plurality of users, there is an effect that the event information performed in the group can be effectively stored and utilized.

  Hereinafter, an example of an embodiment of the present invention will be described with reference to FIGS.

  First, an outline of the content sharing system will be described with reference to FIGS. A content sharing system is a system in which a plurality of users can record and read multimedia data such as still images, moving images, sounds, and texts via a communication network such as the Internet. The basic configuration of this system includes a server on a communication network such as the Internet and a plurality of clients operated by each user.

  FIG. 1 is a diagram showing a schematic configuration of a content sharing system. In FIG. 1, a content management unit 200 is a module for managing content (see FIG. 4) composed of media data and metadata, which will be described later, and controls storage, correction, comment addition, browsing, and the like of content. Moreover, only an authorized client can execute various operations by an appropriate authentication means.

  The clients 100 and 400 are application programs that are directly operated by the user, such as media capture, user interface such as text input, acquisition of metadata such as position information, registration of content in the content management unit 200, content registration, and the like. It provides functions such as display. The user can perform operations such as browsing, registration, acquisition, deletion, and change of the contents published on the system via the client.

  The display composition unit 300 acquires content data from the content management unit 200 and lays out the data in an appropriate form, and may be stored on either the server or the client terminal. As the layout method, various methods such as displaying the contents of a plurality of users in the latest order or displaying only the contents of a specific user can be applied.

  An example of a specific configuration method of the content sharing system shown in FIG. 1 is that the content management unit is a Java (registered trademark) Servlet and the display configuration unit and the client are Java application programs that operate on a mobile phone. is there.

  Also, an example of a different configuration method of the content sharing system is, for example, that the content management unit and the display configuration unit are Java Servlets, and the client is a web browser on a PC (personal computer) or the like.

  All blocks other than the clients 100 and 400 such as the content management unit 200 described in the present embodiment operate on the server, but each block is distributed on the network, information depending on the user who operates the client, Some functions may be included in the client. Each block may be a service on a network operating on a different server, a different program operating on the same server, or a library in the same program.

  Both the client and the server operate as a program on the computer, and data is recorded on a non-illustrated nonvolatile recording medium.

  Hereinafter, the content sharing system will be described using a more specific example. FIG. 2 is an example of a content container display screen, which is a user use screen of an electronic bulletin board system using a content sharing system, for example. Here, six users (Yamada, Sato, Kato, Sasaki, Kimura, Iijima) share content with each other. In this system, a set of specific contents is called a content container (also simply referred to as a container).

  A plurality of users can write and read a plurality of contents in the content container. Furthermore, access rights for each user can be set in the content container. In this example, two methods for writing content are defined to simplify the description. One is image posting, and image data and its title are used as a unit of writing. The other is comment posting, which uses text data as a writing unit.

  FIG. 2 shows an example in which a user posts an image or a comment in a content container having a container name 11 of “1990 year 3 year group B room”. For example, the image data display 13 is an image posted by a user named Yamada, and the poster name and the title set by the poster are displayed in the poster / title display 14. The contributor / comment display 16 is a display of the result of another user posting a comment to Yamada's post. In the figure, one comment is displayed on one line, but this is not the case.

  In FIG. 2, 12 is an image posting button to be pressed when posting an image to this content container, 15 is a comment button used when posting a comment, and 17 is a container creation used when creating a content container. Button.

  Next, how posting, commenting, and browsing are realized in this system will be described. First, the operation at the time of image posting will be described with reference to FIGS.

  FIG. 3 shows the internal configuration of the content management unit 200. The content management unit 200 includes a control unit 201, a content data unit 202, an action data unit 203, and an authentication data unit 204.

  In FIG. 3, the control unit 201 in the content management unit 200 receives various commands from the outside, manages internal data, and gives a display instruction to the display configuration unit 300. The content data unit 202 stores content and content container data. The action data section 203 stores a code for performing some processing. Further, the authentication data unit 204 stores data necessary for authentication such as user data and passwords. This authentication data may be stored outside.

  FIG. 4 illustrates the data configuration of the content data unit 202, where A indicates the configuration of the content container unit 202, B indicates the configuration of the content container, and C indicates the configuration of the content. The content data unit 202 stores and manages a plurality of content containers 211, 212,. Further, one content container 211 includes an access definition data 221 and a content list 222 including a plurality of contents 231, 232. Note that the content container may not include content when newly created.

  The content 231 includes media data 241 and metadata 251. The media data 241 stores multimedia data, and the metadata 251 stores information about the media data. In the case of this embodiment, both images and comments are stored here as one content.

  FIG. 5 shows a specific data storage structure of the content container with respect to FIG. 2, and stores container metadata 210, access definition data 221 and content list 222 representing the title of the container.

  As shown in FIG. 5, posting and viewing permission information (access right) for each user is registered in the access definition data 221. In this embodiment, the ID is Yamada for U001, Sato for U002, Kato for U003, Sasaki for U004, Kimura for U005, and Iijima for U006. In addition, regarding the setting of the access right, posting permission and browsing permission can also be set individually.

  Further, for example, in the image content 231 in the content list 222, image data is stored in the media data 241, and a contributor ID (Identification), a title, and child content IDs (0 or more) are stored in the metadata 251. Is done. On the other hand, in the comment content 232 that is a post comment of the image content 231, a comment text is stored in the media data 242, and a contributor ID and a parent content ID are stored in the metadata 252. Note that 211a is a content container ID for identifying the content container, and 231a is a content ID for identifying the content.

  As a specific posting work, the flow when posting the image data 13 shown in FIG. 2 will be described as an example. When a user (Yamada) posts, first, the image posting button 12 in FIG. 2 is selected, and an image and a title are designated. As a result, in FIG. 3, the client 100 transmits an image posting command to the control unit 201 of the content management unit 200. The content of the image posting command is composed of a posting target content container ID, a poster ID, a title, and image data.

  Upon receiving the image posting command, the control unit 201 executes posting command processing according to the flowchart shown in FIG. First, the control unit 201 searches the content data unit 202 for a content container as a posting destination (step S1). It is determined whether or not there is a designated content container (step S2). If the designated container is found, the access definition data 221 inside the container is confirmed and access permission judgment is performed (step S3). The control unit 201 refers to the access definition data 221, confirms that the contributor Yamada (ID U001) is permitted to post (access right) (step S4), creates posted content, and creates data. And a content ID (C001) is generated and stored in the content list 222 (step S5). When the storage process to the content list 222 is completed, a message indicating that the posting command process has ended is displayed on the screen (step S6), and the posting command process is ended.

  In the above-described determination steps S2 and S4, when there is no posting destination container or when the user does not have access right, a message indicating an error is displayed (step S7), and the posting command processing is terminated.

  In FIG. 5, two child contents are stored in the metadata 251 of the content 231, but at this stage, there is no child content in the content 231, so this item does not exist.

  Next, processing when the user browses the contents of the content container will be described with reference to FIGS. 2, 3, and 7. When the user performs an input operation on the client 100 (see FIG. 3) and instructs to browse the content container 211, the client 100 transmits a browsing command to the control unit 201. The contents of the browsing command at this time are the browsing target content container ID and the user ID of the requester.

  When receiving the browsing command, the control unit 201 executes browsing command processing according to the flowchart shown in FIG. First, the control unit 201 searches for a content container to be browsed (step S11), and determines whether there is a content container to be browsed (step S12). When the browsing target content container is found, the access definition data 221 inside the container is checked as in the posting, and access permission determination is performed (step S13). The control unit 201 refers to the access definition data 221 to confirm that the requester is permitted to browse (access right) (step S14), and if the requester is permitted to browse (viewing OK), The screen composition content data is transmitted to the display composition unit 300 (step S15), and the browsing command process is terminated.

  In the above-described determination step S12 and step S14, if there is no browsing destination container or the user does not have the access right, a message indicating an error is displayed (step S16), and the browsing command processing is terminated.

  The display composition unit 300 analyzes the content data and creates screen composition data. The display composition unit 300 extracts the title, the posted content, and the comment content from the content data, and arranges them as shown in FIG. Also, one image posting button and a comment button 15 for each posting (image data) are laid out. The screen configuration data is configured using, for example, HTML.

  Next, a case where a comment is made on content browsed by the user will be described with reference to FIGS. 2, 3, and 8. In FIG. 2, a case where a user (Sato) makes a comment on the image data display 13 will be described. When the user (Sato) selects the comment button 15, a comment posting command is issued from the client 100 (see FIG. 3) to the control unit 201. The contents of the comment posting command are a requester ID, a content container ID, a content ID, and a comment text.

  When receiving the comment posting command, the control unit 201 executes comment posting processing according to the flowchart shown in FIG. First, similarly to the time of posting, the control unit 201 searches for a comment destination container (step S21) and determines whether there is a comment destination container (step S22). When the comment destination container is found, the access definition data 221 inside the container is confirmed as in the posting, and access permission determination is performed (step S23). The control unit 201 refers to the access definition data 221, confirms that the requester is permitted to browse (access right) (step S24), and if the requester is permitted to browse (view OK), Next, the image content that is the comment destination is searched (step S25), and the content is stored (step S26). Then, a message indicating that the command execution process has been completed is displayed (step S27), and the process is terminated.

  In step S26 for storing content, the comment is stored as content as shown in FIG. At this time, for example, the content ID (C001) of the image content is stored in the parent content item of the metadata 252 of the comment content 232, and the child content item of the metadata 251 of the content 231 that is the comment destination is stored. Stores the ID (C002) of the stored comment content. At the time of browsing, the display composition unit 300 analyzes the metadata of the image content, extracts the child content as a comment of the image, and creates screen composition data.

  In the above-described determination steps S22 and S24, if there is no comment destination container or the user does not have access rights, a message indicating an error is displayed (step S28), and the comment command processing is terminated.

  The above is the basic description of the content sharing system. Next, an example of an embodiment of the present invention for easily creating a content container that can be shared by some users will be described with reference to FIGS.

  FIG. 9 is a diagram showing a system configuration of an embodiment of the present invention. The content sharing system shown in FIG. 9 includes a content container creation auxiliary control unit 510, a container creation unit 520, a data interpretation unit 530, a creation determination unit 540, and an action issue unit 550 in addition to the system shown in FIG. The content container creation assisting unit 500 is used to interpret existing content data from communication history data 700 in which user access history, content container creation history, and the like are recorded, and a user list 710 that each user has personally. An accessible user can be determined and a new content container shared by the accessible user can be created.

  The content container creation auxiliary control unit 510 illustrated in FIG. 9 analyzes a command transmitted when a content creation request is issued from the client 100 or 400, and displays a display configuration unit 300, a container creation unit 520, a data interpretation unit 530, and an action issue unit. Predetermined control and instructions are given to 550.

  The container creation unit 520 creates a predetermined content container in accordance with an instruction from the content container creation auxiliary control unit 510 or the data interpretation unit 530.

  The data interpretation unit 530 performs processing such as interpreting existing data such as user settings, user usage history, and user list to determine accessible users, and transmits the information to the container creation unit 520. .

  For example, the content interpretation unit 531 of the data interpretation unit 530 acquires the specified content from the content management unit 200 according to an instruction from the content container creation auxiliary control unit 510, performs content analysis, and obtains access definition data based on the analysis result. create.

  The access history interpretation unit 532 extracts access users for the corresponding content from the user's communication history, and creates access definition data.

  The user list interpretation unit 533 extracts a predetermined user recorded in a user list 710 of a certain user, and creates access definition data.

  Further, the group creation history interpretation unit 534 reads out information related to content containers created by the user in the past from the communication history data 700, and uses the same access definition data or partially modifies it. Is.

  Also, the external data interpretation unit 535 creates access definition data using information related to e-mail, chat, telephone, and the like obtained through the external application cooperation unit 600, for example.

  The creation determination unit 540 of the content container creation assistance unit 500 periodically analyzes the communication history recorded in the communication history data 700 and issues a content container creation command to the content container creation assistance control unit 510. .

  The action issuing unit 550 is for changing the access right according to a user instruction, and transmits an action definition such as changing the access right by setting the date and time to the content management unit 200.

  Here, an embodiment will be described in which a certain user uses the content sharing system to, for example, recruit a member volunteer from planning a banquet to recording the event.

  First, the user (Iijima) selects an image posting button on a certain content container display screen, and posts a picture of a pub with the title 14a “I will drink”. Then, an image 13a is displayed as in the content container display screen 10 shown in FIG.

  Next, the other five users each select a comment button 15a and post a comment. When all five comments are posted, the user (Iijima) selects the container creation button 17a. At this time, in FIG. 9, a content container creation request is transmitted from the client 100 to the content container creation assistance control unit 510 of the content container creation assistance unit 500.

  Upon receiving this request, the content container creation assistance control unit 510 instructs the display configuration unit 300 to display a screen for inquiring the user of information necessary for content container creation assistance. The display configuration unit 300 transmits configuration data prepared in advance to the client 100, and the client 100 displays a content container creation auxiliary screen 20 as illustrated in FIG. 10 on the client 100.

  The user (Iijima) inputs each setting column of the content container creation auxiliary screen 20 shown in FIG. First, the name of a newly created container is entered in the container name input field 21. In the access permission member setting 22, a method for designating accessible members of a newly created container is selected. In the content diversion setting 23, whether or not to divert the original image content and the comment content group posted to it as the first content of the newly created content container is set. In the link display setting 24, the presence / absence of a button for easily switching the display from the original image content to a new content container and the display method to the user (how the user sees) are set.

  When the user (Iijima) presses the confirmation button 25 for confirming the setting, the client 100 transmits these entry data and setting data to the content container creation assistance control unit 510 as a content container creation assistance command. The content container creation auxiliary command also includes the requester, the ID of the original content container, and the content ID. The cancel button 26 is a button for canceling the setting.

  The content container creation auxiliary control unit 510 analyzes the received command and first checks whether container analysis is necessary. In the present embodiment, the access history is set in the case of the first setting 22a and the second setting 22b shown in FIG. 9, and the content analysis is set in advance in the case of the third setting 22c.

  In FIG. 10, since the user has selected the third setting 22c, the content container creation auxiliary control unit 510 instructs the content interpretation unit 531 to interpret the command. Next, the content interpretation unit 531 executes processing according to the flowcharts shown in FIGS.

  FIG. 11 is a flowchart showing content container creation auxiliary command processing. In FIG. 11, the content interpretation unit 531 first requests the content management unit 200 to access the original content container (the group B room in 1990) with the access authority of the requester (Iijima). The creation source content container is acquired (step S31). Next, the content interpretation unit 531 analyzes the acquired content container (step S32).

  FIG. 12 is a detailed flowchart of content container analysis processing (step S32 in FIG. 1). In FIG. 12, first, the content (C004 shown in FIG. 5) based on the content management unit 200 is retrieved and acquired (step S41). Next, the content analysis unit 531 creates empty access definition data, adds U006: Iijima who is a requester of the content container creation auxiliary command, and sets both “browsing” and “posting” to be OK (step). S42). The process proceeds to the next step, the metadata of the content (C004) is analyzed, and the ID of the child content is searched (step S43). Then, the child content C005 is first discovered. In this way, the presence / absence of child content is determined (step S44), and if the child content is found, the process proceeds, the media data is searched, and the content is analyzed (step S45).

  Then, as a result of the content analysis, it is determined whether or not the user is permitted (step S46). Here, in the setting shown in FIG. 9, the user includes the character “participation” in the matching condition input field 22c1 of the third setting 22c and does not include the character “non-participation” in the mismatching condition input field 22c2. Is set. The media data of the content C005 meets this condition. Therefore, the poster (U001: Yamada) of this content is added to the access definition data, and both “posting” and “browsing” are set to OK (step S47).

  After the process of step S47, the process returns to step S43 and the same analysis is executed for all the child contents of the content (C004). If it is determined in the determination step S46 that the member is not a member to be permitted, the process returns to step S43 to search for the next child content and perform the same analysis. For example, Kato (U003) who commented “unfortunately not participating” as a result of analysis of the content C006 extracted as the child content is not added to the access definition data.

  If it is determined in the above-described determination step S44 that there is no child content, the analysis process is terminated.

  FIG. 13 shows the final access definition data of this embodiment as a result of the analysis of the content container. Kato (U003) and Sato (U002) are excluded from the access definition data. In addition, when the same user has made a plurality of postings, the last posting is valid.

  Then, the content interpretation unit 531 sends the access definition data created as described above to the container creation unit 520 via the combination interpretation unit 536. As will be described later, this combination interpretation unit 536 transmits combination information obtained by combining information obtained from other interpretation units to the container creation unit 520, and is unnecessary when combination interpretation is not performed. You can also.

  The container creation unit 520 executes predetermined processing according to the flowchart shown in FIG. In FIG. 13, first, a new container is created (step S51). The content management unit 200 is requested to create a new container, and the ID of the content container created thereby is set to T002.

  Next, the metadata of the container such as the title is set, and the metadata is created (step S52). In the present embodiment, for example, “2004 New Year's party”.

  Then, the access definition data received from the content interpretation unit 531 is copied and the access definition data is set (step S53).

  Further, link setting is performed (step S54). For example, a bidirectional link between the original content (C004) and the content container (T002) is set according to the user setting. First, new content (C010) is added to the content container (T001). This content is not an image or a comment but a link.

  FIG. 15 is a diagram for explaining the link setting. As shown in FIG. 15, the added content 235 (C010) has the content type of the metadata 255 as “link”, and the container ID and parent content ID of the link destination are displayed. In addition, users who can view the content are displayed. In this case, only the authorized person is displayed.

  Next, the link content (C101) is added to the newly created content container (T002). This is a link destination to the original content (C004). Further, the content (C102) indicating citation is added to the content container (T002) (step S55).

  FIG. 16 is a diagram showing a data storage structure of a newly created content container 251 (T002). Link content 271 (C101) and content 272 (C102) are stored in the content list 261 of the content container 251. The metadata 291 of the content 271 indicates information indicating a link to the content (C004). The content 272 is not a content entity but a content indicating that other content is cited as it is, and “reference” is indicated in the content type column of the metadata 292.

  In this way, the content container (T002) has a data structure as shown in FIG. Then, the container creation unit 520 transmits the content container 251 (T002) to the content management unit 200 and publishes it on the server (step S56), thereby terminating the process.

  FIG. 17 is a content container display screen when the content container 251 (T002) shown in FIG. Since the link has been set, by pressing the container display switching button 31 on the content container display screen 30, the screen can be switched to a screen displaying the content (C004) (see FIG. 18) of the original content container (T001). it can.

  This switching operation is controlled by a set link display unit (switch display unit) 310 provided in the display configuration unit 300. The set link display unit 310 receives a switching signal from the client and is designated by the content management unit 200. Get linked content and provide it to clients.

  Since the original content is not copied and refers to the content (C004) of the content container (T001) shown in FIG. 15, if there is a change such as a new comment posted to the content (C004) This is also reflected in the screen shown in FIG.

  On the other hand, FIG. 18 shows a display screen of the original content container (T001). A content switching button 41 is newly displayed next to the content (C004) display on the content container display screen 40, and the user can switch to the display of the content container (T002) by selecting this. . This button can be displayed only on the screen of the user who has access to the content container (T002) by the user link display setting 24.

  FIG. 19 is an example of a content container display screen when four users who have access rights to the content container (T002) additionally post images and comments. In FIG. 19, an image 33 and an image 34 are newly posted.

  With the configuration as described above, a content container shared only by specific members in a certain group can be created by a simple operation. This saves unrelated people from seeing the topic. In addition, since the content added to the content container is classified as natural, it is not necessary to classify the user later.

  Next, the case where the user sets the access permitted member setting 22 on the content container display screen 20 shown in FIG. In this case, the content container creation auxiliary control unit 510 instructs the access history interpretation unit 532 to perform a viewer extraction process. Then, the access history interpretation unit 532 extracts a browsing user for the corresponding content from the communication history of the communication history data 700 stored in an arbitrary server, creates access definition data, and transmits it to the container creation unit 520. In this way, the content management unit 200 can create a content container that can be shared among users who satisfy the above settings, based on information from the content creation unit 520.

  Furthermore, the access history interpretation unit 532 extracts the user who has performed writing among the browsing users described above, so that it is possible to cope with the case where the user selects the second setting 22b in FIG.

  In addition, by statistically interpreting the communication history and extracting only users who have posted a certain number of times in a certain content container, it is easy to create a new content container that is shared by those users. Can also be provided.

  Next, for example, each user may have a user list separately from the system common user list placed on the server. Thus, the case where each user has a user list individually is demonstrated. In this case, the content container creation auxiliary control unit 510 instructs the user list interpretation unit 533 to extract a predetermined user. Then, the user list interpretation unit 533 extracts the users recorded in the user list 710 or extracts a specific group therein, and creates access definition data. As a result, the user can create a new content container that can be shared among the users based on the information of the user list managed by the user.

  In addition, a case will be described in which users are grouped using a content container created by the user himself in the past or a content container that has been joined. The name and the user ID recorded in the access definition data for the content container created by the user in the past or the content container that has participated in the past are held as the communication history data 700. When a content container interpretation instruction is given from the content container creation auxiliary control unit 510 to the group creation history interpretation unit 534, the group creation history interpretation unit 534 calls the stored information when creating the content container. The same access definition can be used or partly modified.

  Furthermore, a case where access definition data is created using data of an external application will be described. The external application cooperation unit 600 shown in FIG. 9 receives an e-mail or the like from the outside and triggers a content container creation process of the content sharing system.

  In this embodiment, for example, the party invitation mail already exchanged on the content sharing system is transferred from the mail application 610 to the external application cooperation unit 600. In this case, the external application cooperation unit 600 transmits the mail data to the external data interpretation unit 535. The external data interpretation unit 535 compares the mail address (To), broadcast mail address (CC), and sender (From) with the user list of this system, and extracts the members with the user IDs. Access definition data can be created.

  Alternatively, even for data other than the mail application, the external application cooperation unit 600 receives the data and sends it to the external data interpretation unit 535 by a specific interface such as an instant messenger (chat system) 620 or a telephone 630 address book. . The external data interpretation unit 535 can analyze the received data, find the user ID of the content sharing system from the user ID, and create access definition data.

  Further, the combination interpreting unit 536 combines the information of the content interpreting unit 531, the access history interpreting unit 532, the user list interpreting unit 533, the group creation history interpreting unit 534, and the external data interpreting unit 535 to assist in creating a more complicated content container. Control can be possible.

  For example, when the user instructs creation of a content container via the client 100 as in the embodiment described using the content interpretation unit 531, for example, when there is a similar member configuration in the past, the same name It is possible to present such as adding.

  Also, a case will be described in which the content container creation trigger is not issued by the user, but is automatically issued to create predetermined access definition data. Unlike the embodiment described using the content interpretation unit 531, this example does not issue a content container creation auxiliary command, but the creation determination unit 540 periodically analyzes the communication history to create a container. This command is automatically issued to the unit 520 via the content container creation auxiliary control unit 510.

  For example, when a keyword preset by the user is included before the image posting, a process of automatically creating a container is performed. For example, in the example shown in FIG. 2, if the title at the time of image submission includes the words “drinking party”, “banquet”, “year-end party”, the user was asked for confirmation and the consent was obtained. If so, it automatically creates a content container. This makes it easy to create unity in content management, such as making content containers related to drinking alcohol without the user's awareness, and making content containers in the same way in the community. There is an effect that.

  Further, as an example of the automatic issue of the content container creation auxiliary command described above, when a comment preset by the user, for example, 20 or more is posted for a specific image posting, the creation determination unit 540 creates a container. If the image contributor is allowed to display the screen, and the user approves it, the access right of the parent content is inherited and another content container is automatically created. This makes it possible to consolidate conversations that are likely to have longer discussions. Instead of continuing to comment on the same image, the user can interact with the same theme while posting another image.

  By the way, in the embodiment described using the content interpretation unit 531, it is assumed that an access right is added to a newly created content container, but the present invention is not limited to this. For example, once a content container is created, even if a “participation” comment is subsequently posted, it cannot become a member (see FIGS. 10 and 13), and the administrator must request access definition data registration. Even in such a case, a case will be described in which a user who has posted a comment later can obtain access rights.

  In the embodiment described using the content interpretation unit 531, when creating the content container (T002) (see FIG. 16), the content container (T001) is linked to the content (C004) as the parent (C010). (See FIG. 15). In this embodiment, the action issuing unit 550 adds action content (not shown) whose parent is the content (C004) according to an instruction from the content container creation auxiliary control unit 510.

  The action content is a control content like the link content, and an operation program is stored in the media data. When a certain content is posted, the content management unit 200 activates an action content stored in the parent content.

  In this embodiment, it is assumed that, for example, an action A001 that defines a certain behavior when a content container (T002) is created is defined. This action A001 operates according to the flowchart shown in FIG. FIG. 20 is a flowchart for automatically correcting the access definition data in accordance with action A001. First, the posted content is analyzed (step S61), and it is confirmed whether or not the poster is suitable for an access member, that is, whether the poster is an access permission target member (step S62). If the conditions match, it is added to the access definition data of the content container (T002) and amended (step S63). If they do not match, the process ends. As a result, even after a content container is created once, it is possible to automatically access a new content container simply by making an appropriate comment.

  In the present embodiment, the action content operation program is stored in the media data. However, the present invention is not limited to this. For example, it is possible to store a program code in the action data section 203 shown in FIG. 3 and store reference information for the program and necessary parameters in the action content. As a result, when setting the same program code to a plurality of contents, it is possible to save the storage capacity for storing the program code, and it is convenient that the program code can be corrected in one place.

  A case will be described in which another action is defined for the embodiment in which the action issuing unit 550 adds an action content whose parent is a designated content according to an instruction from the content container creation auxiliary control unit 510.

  The action issuing unit 550 sets an action “make access right the same as the parent content container at a specific date and time” for the newly created content container (T002) according to a user instruction. With this setting, for example, the next day after the banquet is over, the content container will be released to those who could not participate in the banquet, and the contents that were examined for one of the members secretly were born The behavior of opening to the day can be automatically activated.

  Furthermore, the content container creator can make the access right of the newly created content container the same as that of the original content container regardless of the specific date and time. In this case, it is possible for the user to use content grouping in a certain content container. More specifically, for example, by making the browsing permission user of the content container (T002) the same as the content container (T001), a person who could not go to the banquet can enjoy the content from the beginning, and the banquet Grouping content from the beginning.

  It is also possible to create a content container from a plurality of contents. For example, in the embodiment described using the content interpretation unit 531, a new content container is created based on one content and a comment additionally posted thereto. On the other hand, a method for creating a new content container based on a plurality of contents can be easily performed by applying the present embodiment.

  For example, it is assumed that a plurality of users post content of the same theme, for example, a picture of Santa Claus in a certain content container. When one of the posters notices it and tries to create a content container for content related to Santa Claus, the present invention performs an operation of extracting the existing content and creating a content container including the content. At this time, the content may straddle a plurality of content containers. The content interpretation unit 531 creates access definition data with the posters of these contents as access-permitted users of the new content container. Thereby, the user can easily create a content container for users who have the same interest.

  In the above-described examples of the embodiments, some limitations have been made to simplify the description. For example, the types of posted content are not limited to images and comments, but various types such as audio can be used. The container creation button and the container display switching button are not limited to buttons, and may be other means such as right-click and double-click of the mouse.

  According to these embodiments described above, without specifying each individual member, the access permission user is determined by using the data accumulated by communication of the content sharing system and other tools, and the specific user is identified. You can easily create new content containers that can be shared between users. Therefore, the user can easily bundle content shared by a plurality of users on the content sharing system and have a specific dialogue.

  Also, from the viewpoint of managing a large amount of content, instead of the conventional flow of content creation (shooting) → storage → classification → sharing, shared place creation → content creation (shooting) → storage + classification → a new shared place It becomes the flow of making. By doing so, not only the organization of content of a certain theme is simplified, but also the organization of new content can be supported (supported) in a chained manner. Moreover, the opportunity for a user to organize content can be increased naturally.

  Next, an example of another embodiment of the present invention will be described with reference to FIGS.

  FIG. 21 is a diagram showing a system configuration according to another embodiment of the present invention. In FIG. 21, an event information management unit 800 is added to FIG. 1, and a display configuration unit 300 that configures the content acquired from the content management unit 200 in a predetermined display format and transmits it to the client (see FIG. 1). ) Is omitted. In FIG. 21, parts corresponding to those in FIGS. 1 and 9 are denoted by the same reference numerals.

  The system shown in FIG. 21 includes one or more clients, here clients 101, 102, and 103, a content management unit 200, and an event information management unit 800. The event information management unit 800 includes an event database (event data storage unit) 820 that stores event data and an event data input / output unit 810 corresponding to the event database, and transmits / receives information to / from each client. Then, the content management unit 200 transmits content data to the client via the display configuration unit 300 (not shown) according to an instruction from the client.

  Here, the difference between the event of this example and the above-described content container will be described. The content container is a container for storing a plurality of content entities. For example, each user may have a different content container. it can. On the other hand, an event is a collection of reference information for classifying content. As will be described later, a user who can change the event information cannot always change the content container or the content itself.

  FIG. 22 shows the contents of the event data table held in the event database 820. In this embodiment, the event data table is composed of ID, title, priority, place, start time, end time, member, activity, and category of each event. This table may have all elements or only a part of it.

  FIG. 23 is a manual event sharing sequence diagram. With reference to FIG. 23, a method in which the client (A) 101 and the client (B) 102 set the same event information in their contents will be described.

  In FIG. 23, first, the client A generates a new event (E1). An example of the event creation screen at that time is shown in FIG. In the event registration screen, for example, fields for inputting an event name, place, start date / time, end date / time, and participants (members) are provided. The event information management unit 800 registers and stores information from the client A in the event database 820 (E2). Then, the event information management unit 800 returns information on the generated event (E3). If event registration fails at this time, an error code is returned.

  Next, the client A issues an event list acquisition request (E4) and acquires all event information (E5). Thereafter, the content registration screen is displayed on the client A, and a content is registered by taking a picture (E6). At this time, all event information acquired in the process E5 is presented to the user through the screen, and the user selects an event of the content from the information. The user registers the content generated by operating the client A in the content management unit 200 (E7).

  Thereafter, when the client B wants to register contents, the client B requests to obtain an event list in the same manner as the process E4 of the client A (E8). The event information management unit 800 returns information on all events (E9). Note that the event information returned to client B at this time includes the event information generated by client A in process E1. That is, when the client A and the client B participate in the same event, the client B can reuse the event information created by the client A. The processes E10 and E11 are the same as the processes E6 and E7, respectively.

  FIG. 25 is a diagram illustrating an example of a content registration screen. 25A shows the content registration screen 120 in the normal state, and FIG. 25B shows the content registration screen 120 when the cursor button 121 is pressed. When the user displays the content registration screen shown in FIG. 25A and further presses the cursor button 121 shown in FIG. 25B, an event list request command is transmitted to the event information management unit 800 (E4), and the event registered earlier (see FIG. 25). 24) is sent to the client A and appears as an event candidate (E5).

  At this time, when the user selects an event, the client A sets an event ID in the content metadata (E6). When the user presses the registration button 122, the client A transmits the content to the content management unit 200 (E7).

  Similarly for other clients, for example, the client B can perform the same processes as the processes (E4) to (E7) described above and share the event information created by the client A (E8) to (E11). .

  Also, a user with change authority can update the event additional information such as the location, start time, and member.

  Furthermore, a method for generating an event simultaneously with content registration will be described. By inputting an event name that does not exist in the event list on the content registration screen (see FIGS. 25A and 25B), the client registers a new event in the event information management unit 200, and the above event is included in the metadata of the content. An ID may be set and registered in the content management unit 200. In this case, the user does not need to be aware of event creation explicitly.

  Next, another example of the embodiment of the present invention will be described with reference to FIG. In this embodiment, the event additional information is automatically set from the contents.

  FIG. 26 is a diagram showing a system configuration of still another embodiment of the present invention. 26 is different from FIG. 21 in that an event additional information setting unit 830 is provided in the event information management unit 801. The event additional information setting unit 830 automatically sets event additional information from the content content supplied from the content management unit 200 and registers it in the event database 820. Note that the description of the display configuration unit 300 is omitted as in FIG.

  For example, event metadata can be set from content metadata. For example, the event start time can be set the same as the content registration time, or the event position information can be set the same as the content position information.

  For example, it is assumed that a user registers content in which a specific event ID is set in metadata. At this time, the event additional information setting unit 830 automatically adds the user to the member information of the event data if the user is not included.

  Further, for example, it is assumed that the user A, the user B, and the user C go to golf every Sunday. At this time, the event additional information setting unit 830 automatically sets the category as golf for an event whose members are user A, user B, and user C and the time is set to Sunday.

  Further, for example, the event additional information 830 may be set by recognizing the contents of the media. For example, it is conceivable that content with sound of a piano concert is registered, it is determined that the sound is a piano, and the category is automatically set to “piano”.

  Next, another example of the embodiment of the present invention will be described with reference to FIG. In this embodiment, the occurrence of an event is automatically determined, and event information of newly registered content is automatically set.

  FIG. 27 is a diagram showing a system configuration of still another embodiment of the present invention. 27 is different from FIG. 21 in that an event detection unit 840 is provided in the event information management unit 802. The event detection unit 840 newly generates event data from the content content supplied from the content management unit 200 and registers it in the event database 820. Note that the description of the display configuration unit 300 is omitted as in FIG.

  FIG. 28 is a flowchart showing event automatic determination processing by the event detection unit 840. In FIG. 28, first, the event detection unit 840 acquires content from the content management unit 200 (step S101). Next, it is determined whether or not information regarding the new event exists in the acquired content (step S102). If the presence of a new event is confirmed, it is added to the event database 820 (step S103). In the determination step S102, if the presence of a new event is not confirmed, the automatic determination process is terminated. Note that the content acquired for determination may exist in a different content container.

  As a method of detecting a new event by the event detection unit 840, there is a method of determining from the similarity of a plurality of contents, and specifically, the following may be mentioned.

  One is a method of judging from the similarity of registration times of contents stored as metadata. In this case, when a plurality of contents are registered together, it is determined that some event has started.

  FIG. 29 is a diagram for explaining the event detection based on the registration time, and represents the position where the content is registered on the time axis. In FIG. 29, for example, it is assumed that contents 131, 133, and 135 are registered by user A, and contents 132 and 134 are registered by user B. At this time, since the registration times of the contents 133, 134, and 135 are close, it is determined that the new event 140 has occurred together.

  FIG. 30 is a flowchart showing a new event occurrence determination process based on the registration time. First, the number of contents registered within a certain time (Tth) is counted and set to (N) (step S111). Next, it is determined whether the content number N is greater than a predetermined threshold value (Nth). If the registered content number N is greater than the threshold value Nth, it is determined that there is a new event (step S112), and the process is terminated. Here, these parameters, time Tth, and content number threshold Nth can be set by the user. If the time Tth is extremely reduced, the condition becomes severe. Therefore, it is desirable to set the time Tth such that an event is generated only when the registered time is adjusted by the users.

Moreover, after the event starts, there is a high possibility that content registration for all members will be frequent. Therefore, it is desirable to suppress event generation once an event has been generated. As a method for suppression,
Increase the threshold value Nth of the number of contents for a certain period.
-The content number threshold Nth is increased unless the user explicitly specifies it.
As long as content registration continues, the threshold value Nth of the number of contents is increased.
Apply the above restrictions only to the content of users who are members of the latest event.
Etc. Note that if the threshold value Nth is sufficiently large, no event is generated.

  Further, the threshold value Nth may be normalized by the previous user registration frequency. That is, when the content registration number of the user A per unit time is Na, the content number registered by the user A is divided by Na, and generation of a new event is suppressed using this calculation result. By doing in this way, the influence by the user who registers the content regularly can be prevented.

  As still another embodiment, a method for determining from the similarity of text data stored as metadata will be described. This allows users to automatically create event information simply by deciding and registering the content title as “welcome party” or the like.

  FIG. 31 shows an outline of the new event occurrence determination by the title character string. In the content management unit 200, content registration is performed with the title “welcome party” from the client A, and content registration is also performed with the title “welcome party” from the client B. Then, the event detection unit 840 analyzes each content supplied from the content management unit 200, detects the same title, and newly generates a “welcome party” event.

  At this time, the content used for determination may be that of a different user or the same user. For example, in the case of content of the same user, an event may be generated when a certain user registers content twice with the same title.

  FIG. 32 is a flowchart showing a new event occurrence determination process using a title character string. 32, first, the event detection unit 840 extracts similar titles from the content acquired from the acquired content management unit 200, and sets the number of extracted content at this time to N (step S121).

  The similar title detection performed here may detect a completely matching title as shown in FIG. 31, or may detect a title that is determined to be similar on some basis. For example, methods for detecting similar titles include those containing the same character string, hiragana and katakana, which allow uppercase and lowercase notation fluctuation, and similar character strings that match using a thesaurus dictionary, etc. .

  Subsequently, it is determined whether or not the extracted content number N is greater than a preset threshold value Nth (step S122). If the extracted content number N is larger than the threshold value Nth, it is determined whether the event has a similar title with the event that has recently occurred (step S123).

  The determination process performed in step S123 is to prevent a plurality of the same events from being generated when the user continues to register content with the same title. If a number of contents generated with the same title are generated within a certain period, it is not determined that a new event has occurred. Here, since the possibility that the same title is accidentally input is relatively low, the content acquired for the event occurrence has a longer period than the event occurrence determination based on the posting time described above (see FIGS. 29 and 30). Post content acquisition may be performed. For example, the determination may be made regarding the content posted within one hour.

  If the title is not similar in the determination step S123, the event additional information is set by diverting the content title (step S124). Then, the new event occurrence flag is turned on (step S125), and the process ends.

  If the extracted content number N is smaller than the threshold value Nth in the determination step S122, or if it is a similar title in the determination step S123, the new event occurrence flag is turned off (step S126), and the process ends.

  As still another embodiment, a method for determining from the similarity of position data stored as metadata will be described. This is because when there is a plurality of contents whose position information is set in metadata using a client capable of acquiring position information, when there are a plurality of contents registered from the same place, they are used as event detection. Is. The position information may be acquired using GPS (Global Positioning System), cell phone area information, or the like, or both of them.

  FIG. 33 is a flowchart showing a new event occurrence determination process based on position metadata. In FIG. 33, first, the event detection unit 840 extracts content having metadata in the same region from the content acquired from the content management unit 200, and sets the number of extracted content at this time to N (step S131).

  As a specific method for determining the same area performed here, for example, a distance between contents is measured from GPS latitude and longitude information, and it is determined that contents whose distance is equal to or less than a certain distance exist in the same area. Or you may determine with the same area information of a mobile telephone existing in the same area.

  Subsequently, it is determined whether or not the number N of extracted contents is larger than a preset threshold value Nth (step S132). If the extracted content number N is greater than the threshold value Nth, it is determined whether or not the area is the same as the event that has recently occurred (step S133).

  The determination process performed in step S133 is to prevent a plurality of events in the same region from being generated when the user continues to register content from the same region. If a number of contents generated in the same region are generated within a certain period, it is not determined that a new event has occurred. Here, if it is assumed that there is a relatively low possibility of input from the same area by chance, the content acquired for the event occurrence is used for the event occurrence determination based on the posting time (see FIGS. 29 and 30). It may also be possible to obtain posted content for a longer period. For example, the determination may be made regarding the content posted within one hour.

  If it is not the same area in the determination step S133, the event additional information is set by diverting the location of the event (step S134). Then, the new event occurrence flag is turned on (step S135), and the process ends.

  If the extracted content number N is smaller than the threshold value Nth in the determination step S132 described above, or if it is not the same region in the determination step S133, the new event occurrence flag is turned off (step S136), and the process is terminated.

  As still another embodiment, a method for determining from the similarity of audio data stored as metadata will be described. In this method, when content is acquired, audio data is acquired at the same time, and it is determined by the data that the user participates in the same event. For example, if multiple users take photos when saying "Cheers" and register them, even if it is a photo taken of different objects and it is difficult to determine similarity only from that photo, It is determined that the user is in the same place based on the similarity of the audio data. Here, the audio data may be acquired for a certain period before and after taking a picture. By doing so, the possibility that the audio data matches is increased.

  FIG. 34 shows an outline of new event occurrence determination based on audio data. In FIG. 34, client A and client B collect the same sound source 150 with their microphones (microphones) 151 and 152, and register the content with the audio data in the content management unit 200, respectively. Then, the event detection unit 840 analyzes each content supplied from the content management unit 200, detects similar audio data, and generates a new event.

  FIG. 35 is a flowchart showing a new event occurrence determination process using audio data according to the present embodiment. In FIG. 35, first, the event detection unit 840 extracts content with similar audio metadata from the content acquired from the content management unit 200, and sets the number of extracted content at this time to N (step S141).

  Next, if the number N of extracted contents is larger than a preset threshold value Nth, it is determined that there is a new event (step S142), and the process ends.

  As still another embodiment, a method for determining from the similarity of content media data will be described. For example, when there are a plurality of photographs in which the same scenery is reflected in a plurality of contents, the event is determined to be started.

  For the event start determination, for example, a combination of a plurality of methods described above may be used, for example, considering registration time data and position data at the same time.

  As still another embodiment, new content can be generated by adding new event information to the content metadata. The advantage of this method is that the client does not need to communicate directly with the event information management unit 200. For example, this method is desirable when the network bandwidth of the client is narrow and multiple transactions are a problem. In addition, when content is registered by e-mail, for example, without using a dedicated client for content registration, event information can be generated using existing network protocol by embedding event information as metadata. . The event metadata can include event additional information.

  Next, as another embodiment, a method for determining an event in which the content is acquired from the content will be described. This is to determine the event to which the content belongs for the content newly generated by the client after the event has occurred once.

  FIG. 36 shows the system configuration of still another embodiment of the present invention. In FIG. 36, a conforming event determination unit 850 is provided in the event management information unit 802 of the system shown in FIG. The conforming event determination unit 850 determines which event of the events in the event database 820 the content given to the event information management unit 200 by the contenton management unit 200 is most suitable. The processing of the adaptation event adaptation unit 850 may be directly invoked by the client or may be invoked by the content management unit 200. The conforming event determination unit 850 returns, for all events in the event database 820, the likelihood that the content belongs to the event (degree of conformance). Using this information, the client may present the event candidates to the user in order of suitability and allow the user to select.

  As one of the adaptation event determination methods, registration time data of content metadata can be used. The event that occurred when the content was acquired is selected from the start time and end time of the event additional information.

For example, when the registration time (Ft) of the registration time is (Tc), the event start time is (Ts), and the event end time is (Te).
The registration time fitness Ft
Ft = 1 (if; Ts ≦ Tc and Tc ≦ Te)
Ft = 0 (if; Tc ≦ Ts or Te ≦ Tc)
Ft = 0.75 (if; Ts ≦ Tc and Te does not exist)
Ft = 0.75 (if; Tc ≦ Te and Ts does not exist)
Ft = 0.5 (if; there is no Ts, Te)
And

  In addition, as one of the conforming event determination methods, position information of content metadata can be used. An event in the same region as the content is selected from the position information of the event additional information.

  In addition, as one of the conforming event determination methods, user information of content metadata can be used. This is to select an event including the content registrant in the member information of the event additional information.

  Further, as one of the conforming event determination methods, content media data can be used. A similar image is searched by image recognition, and an event in which most similar images are found is determined as a corresponding event.

  FIG. 37 is a flowchart showing a conforming event determination process in which the conforming event determining unit 850 combines the above-described determination methods. First, the fitness (Ft) of registration time is calculated (step S151). Next, the fitness (Fl) of the position information is calculated (step S152). Then, the fitness (Fu) of the user information is calculated (step S153). Further, the media data fitness (Fm) is calculated (step S154). Then, the weighted sum of the fitness levels for each event is calculated (step S155), and the fitness event determination process ends.

If the overall fitness is F,
F = W1 * Ft + W2 * Fl + W3 * Fu + W4 * Fm
It becomes.
Here, Wi (i = 1, 2, 3, 4) is the weight of each data,
ΣWi = 1
It is. When all have the same weight, Wi = 0.25.

  Hereinafter, as another embodiment, a method for using event information in a client when event information is added to content will be described.

  First, FIG. 38 shows a screen in which contents registered in a plurality of content containers are displayed in the latest order without event information as a conventional example. The problems of the conventional example shown in FIG. 38 are that the content of different events is displayed in a mixed manner, so that the glance is bad, and when a certain user registers a large amount of content at one time, other content cannot be seen. , Etc.

  Next, FIG. 39 shows an example of the latest content display screen in which contents are collected for each event. In FIG. 39, 161 and 162 are event titles, 163 is an activity level, 164 is content belonging to an event, 165 is a link button to an event page for obtaining more detailed information, and 166 is a link button to the next page. As can be seen from FIG. 39, since a plurality of contents are classified in units of events, the user can browse only the contents of necessary events. In addition, there is an advantage that the attribute information for each event can be easily understood.

  FIG. 40 is a flowchart showing a display process of content and event information in the client. In FIG. 40, first, the client acquires N latest contents from the content management unit 200 (step S161). Next, the acquired content is classified for each event (step S162). Then, the events classified according to the predetermined criteria are rearranged (sorted) (step S163).

Here, as the content sorting criteria,
・ The order of the event in which the latest posting was made in the event ・ The order of the activity level of the event ・ The number of posting of the event

  When the sorting process in step S163 is completed, additional information of each event is acquired from the event information management unit 200 (step S164). Then, content and event information are displayed (step 165), and the process is terminated.

  As still another embodiment, an event generation method based on cooperation with an external application will be described.

  FIG. 41 is a diagram showing a system configuration for performing event generation in cooperation with an external application according to still another embodiment of the present invention. The event management information unit 805 shown in FIG. 41 is obtained by providing an external application cooperation unit 860 in the event management information unit 800 shown in FIG.

  The external application cooperation unit 860 generates event information by cooperating with an external application 861 having event information, and the generated event information is stored in the event database 820. The external application cooperation unit 860 has a function of associating user information of the external application 861 with user information in the content sharing system.

  As an example of the external application 861, for example, a scheduler can be used. From the scheduler, event additional information such as an event name, start time, end time, and member list can be obtained. Further, groupware shared on the network may be used as the scheduler.

  Further, as another external application 861, electronic mail can be used. For example, an event can be generated by sending a mail having a subject (subject) as an event name, a From (sender), a To (destination), and a CC (broadcast destination) to a specific mail address. . Furthermore, by defining an appropriate format, other event additional information such as a start time, an end time, and a category may be input.

  As described above, according to the embodiment described with reference to FIG. 21 and the subsequent drawings, it is possible to easily classify contents for each event. Furthermore, by sharing the event information among a plurality of users, it is possible to effectively store and use information related to events held in the group.

  In the system of the above-described embodiment, the functions of the event information management units 800 to 805 may be provided in the content container creation auxiliary unit 500 shown in FIG. Moreover, it is good also as a system structure which provided each event information management part 800-805 and the content container creation assistance part 500, respectively.

  The present invention is not limited to the above-described embodiments, and various other configurations can be taken without departing from the gist of the present invention.

It is a figure for demonstrating the outline | summary of a content sharing system. It is a figure which shows an example of a content container display screen. It is a figure which shows the structure of the content management part of FIG. FIG. 2 is a diagram showing a data configuration of a content data part in FIG. It is a figure which shows an example of the data storage structure of a content container. It is a flowchart which shows a posting command process. It is a flowchart which shows a browsing command process. It is a flowchart which shows a comment command process. It is a figure which shows the system configuration | structure of one embodiment of this invention. It is a figure which shows the content container creation assistance screen of one embodiment of this invention. It is a flowchart which shows the content container creation assistance command process of one embodiment of this invention. It is a flowchart which shows the content container analysis process of one embodiment of this invention It is a figure which shows an example of the access definition data of one embodiment of this invention. It is a flowchart which shows the process by the container preparation part of one embodiment of this invention. It is a figure with which it uses for description of the link setting of one embodiment of this invention. It is a figure which shows an example of the data storage structure of the newly created content container of one embodiment of this invention. It is a figure which shows an example of the newly created content container display screen of one embodiment of this invention. It is a figure which shows an example of the content container display screen of the link origin of one embodiment of this invention. It is a figure which shows an example of the display screen when a contribution matches the newly created content container of one embodiment of this invention. It is a flowchart which shows the automatic correction process of the access definition data of one embodiment of this invention. It is a figure which shows the system configuration | structure of other embodiment of this invention. It is a figure which shows an example of the event data table of other embodiment of this invention. It is a manual event sharing sequence diagram of other embodiment of this invention. It is a figure which shows an example of the event creation screen of one embodiment of this invention. It is a figure which shows an example of the content registration screen of other embodiment of this invention. It is a figure which shows the system configuration | structure of further another embodiment of this invention. It is a figure which shows the system configuration | structure of further another embodiment of this invention. It is a flowchart which shows the automatic determination process of further another embodiment of this invention. It is a figure with which it uses for description of the event detection by registration time of further another embodiment of this invention. It is a flowchart which shows the determination process of new event generation | occurrence | production by registration time. It is a figure which shows the outline | summary of the new event occurrence determination by the title character string of further another embodiment of this invention. It is a flowchart which shows the determination process of new event generation | occurrence | production by the title character string of further another embodiment of this invention. It is a flowchart which shows the determination process of new event generation | occurrence | production by the position metadata of further another embodiment of this invention. It is a figure which shows the outline | summary of the new event generation | occurrence | production determination by the audio | speech data of other embodiment of this invention. It is a flowchart which shows the determination process of new event generation | occurrence | production by the audio | voice data of other embodiment of this invention. It is a figure which shows the system configuration | structure of further another embodiment of this invention. It is a flowchart which shows the conformity event determination process of further another embodiment of this invention. It is a figure which shows an example of the conventional latest content display screen. It is a figure which shows an example of the newest content display screen (event unit) of further another embodiment of this invention. It is a flowchart which shows the display process of the content and event information of other embodiment of this invention. It is a figure which shows the system configuration | structure of further another embodiment of this invention.

Explanation of symbols

  10, 30, 40 ... content container display screen, 20 ... content container creation auxiliary screen, 31, 41 ... container display switching button, 100, 101, 102, 103, 400 ... client, 200 ... content management unit, 201 ... content control , 202 ... content data part, 203 ... action data part, 204 ... authentication data part, 211,212 ... content container, 211a ... content container ID, 221 ... access definition data, 231,232 ... content, 231a ... content ID, 235, 271 ... Link content, 241,242 ... Media data, 251,252 ... Metadata, 252a ... Contributor ID, 252b ... Title, 252c ... Child content ID, 272 ... Link content, 300 ... Display component, DESCRIPTION OF SYMBOLS 10 ... Set link display part, 500 ... Content container creation assistance part, 510 ... Content container creation assistance control part, 520 ... Container creation part, 530 ... Data interpretation part, 531 ... Content interpretation part, 532 ... Access history interpretation part, 533 ... user list interpretation unit, 534 ... group creation history interpretation unit, 535 ... external data interpretation unit, 536 ... combination interpretation unit, 540 ... creation judgment unit, 550 ... action issue unit, 600 ... external application cooperation unit, 700 ... communication history Data, 710 ... User list, 800, 801, 802, 803, 804, 805 ... Event information management unit, 810 ... Event data input / output unit, 820 ... Event database, 830 ... Event additional information setting unit, 840 ... Event detection unit , 850 ... Conforming event The determination unit, 860 ... external application cooperation section

Claims (27)

A content sharing system for sharing content on a server among multiple users' clients,
A content management server that manages content composed of media data and metadata and records access definition data in which access authentication information of each user is registered;
Acquires the content from the content management server, and a display configuration server to be displayed on the client to configure the specified display format,
Content that is shared among users registered in the new access definition data while creating access definition data by determining access-permitted users based on the existing data stored in the content management server or outside A content container creation auxiliary server that creates a container and sends it to the content management server ;
An event data storage unit holding an event data table in which event information for classifying content is registered, which includes at least an event name and an event ID, and performs data communication between the event data storage unit and the client, It possesses an event information management server configured to the event data event information stored in the storage unit to the client from the event data output unit for transmitting,
The event information management server
A process of newly registering the event information in the event data table based on the fact that information for generating the event information is newly transmitted from any one of the clients of the plurality of users;
Even when an event list request command is transmitted from any one of the clients of the plurality of users when creating new content, all the event information registered in the event data table is used as the new content. A content sharing system that performs processing for returning event information as a candidate for association . The content container creation auxiliary server has a content container creation auxiliary control unit that performs predetermined control upon receipt of a content container creation command from the client;
Interpreting the existing data according to an instruction from the content container creation auxiliary control unit, extracting an access-permitted user, and newly creating access definition data;
Based on the new access definition data supplied from the data interpretation unit, data necessary for the configuration of the content container shared among the users registered in the new access definition data is created and stored in the content management server. claim 1 content sharing system according to Ru and a container creation unit to be transmitted. The data interpretation unit comprises a content interpreting unit which interprets the data recorded in the posted contents for a given content in said content container as existing data,
The container creation unit, based on said interpretation result on the content interpreting unit, according to claim 2, wherein the data needed to create a new content container for content container link that sends to the content management server including the predetermined content Content sharing system. The content interpreting unit, the content sharing system of claim 3, wherein the user who posted the content you with the access authorized user with specific content for a given content. The data interpretation unit interprets the data of access history for a given content of the user as the existing data, an access history interpretation unit for extracting an access-permitted user,
The container creation unit, based on said interpretation result in the access history interpreting unit, wherein the predetermined contents that sends the data necessary to create a new content container for content container and linked to the content management server including the claims 2 The content sharing system described. The data interpretation unit, the existing claim 2 content sharing system according to Ru with a user list interpretation unit that interprets user list data owned by the user recorded in the client as data. The data interpretation unit, the existing claim 2, wherein the content sharing system of Ru with a group creation history interpreting unit for interpreting an access definition data created in the past as data. The data interpretation unit, according to claim 2, wherein the content sharing system of Ru with external data interpretation unit for interpreting the data obtained from outside the application software as the existing data. The data interpretation unit, data of the data recorded in the posted contents for a given content in a content container as existing data access history for a given content of the user data of the user list owned by the user, in the past access definition data, content sharing system according to claim 2, wherein the Ru with a combination interpreting unit for interpreting a combination of two or more of the created. A creation determination unit that periodically interprets text data written in arbitrary content posted for content in an arbitrary content container and detects a specific character string,
The creation determination unit, the case of detecting a specific character string, the content container created auxiliary control unit to that automatically issues a content container creation command claim 2, wherein the content sharing system. The content container created auxiliary control unit, after the creation of the content container, and interpret the content of the user who has posted the content, a user who satisfies a predetermined condition, the access definition data recorded in the content management server content sharing system according to claim 2, wherein the Ru was added to the access-permitted user. The content container created auxiliary controller, said after the creation of the content container, according to claim 2, wherein to change depending access definition data of the created content container at a specific date and time set in advance on the set contents Content sharing system. The display configuration server includes a display switching unit that switches the display of content containers linked to each other according to an instruction from the client,
The mutually by operating the display switching button displayed in the link set content container display screen, according to claim 3, wherein the content sharing system that you switch the display between the mutually linked set content container. The event information management server
An event additional information setting unit for automatically setting information to be added to the event information from the content supplied from the content management server and registering it in the event data table,
From the similarity of a plurality of contents supplied from the content management server, an event detection unit that newly generates the event information and registers it in the event data table,
The content management server further comprises any one of the event information registered in the event data table, and a conforming event determination unit that determines which event information is most suitable for the event information registered in the event data table. The content sharing system according to 1. A content container consisting of a collection of specific content that can be shared among a plurality of users is newly recorded on a server in which content consisting of media data and metadata and access definition data in which authorized users for the content are registered are recorded. A content container creation method to create,
A step wherein the server when receiving a content container creation command from the client that the user is operating, depending on the content of the content container creation command, the server or to interpret the existing data stored in the external,
Extracting access-permitted users based on the interpretation result of the existing data and newly creating access definition data;
Creating a new content container shared among users registered in the new access definition data ;
Holding an event data table in which event information for classifying content, at least consisting of an event name and an event ID, is registered;
A step of newly registering the event information in the event data table based on the fact that information for generating the event information is newly transmitted from any one of the clients operated by the plurality of users; ,
Even when an event list request command is transmitted from any of the clients operated by the plurality of users when a new content is created, all the event information registered in the event data table is stored in the new event data table. step a content container created how having a returning as a candidate event information associating the content. A step of interpreting the data to which the as existing data, recorded in the content posted for a given content in the recorded content container to the server,
Extracting a user who has posted content including specific content with respect to the predetermined content as the access-permitted user, and newly creating access definition data;
Wherein the predetermined content and content containers and links including, content container creation method of claim 15 that have a and creating a new content container that is shared between the registered in the new access definition data users . Examples existing data, the steps of interpreting the data of access history for a given content in the recorded content container to the server,
A step of based on said interpretation result data of the access history, and extracts the access-permitted user, create a new access definition data,
Wherein the predetermined content and content containers and links including, claim 15 content container created method according that have a and creating a new content container that is shared between the registered in the new access definition data users. Examples existing data content container creation method according to claim 15, wherein you interpret user list data recorded in the client. Examples existing data content container creation method according to claim 15, wherein you interpret access definition data created in the past. Examples existing data, according to claim 15 content container created method according you interpret the data obtained from outside the application software. Examples existing data, data recorded in the posted contents for a given content in a content container, the data of access history for a given content of a user, the user list of user-owned data, access definition created in the past data, according to claim 15 content container created method according you interpret a combination of two or more of the. Periodically interpreting text data written to any content posted to content in any content container to detect a particular string;
Wherein if a particular character string is detected, automatically that it has a and issuing a content container creation command claim 15 content container created method according. After creating the content container , interpreting the user's content posted to the content;
The users who satisfy a predetermined condition, the content container creation method according to claim 15, wherein that having a a step of adding to the access-permitted user of the access definition data recorded previously hexa over server. Wherein after the creation of a content container, a preset content container created method of claim 15, wherein to change depending access definition data of a particular of the created content container to date on the set contents. Whether or not to display a display switching button for switching the display of content containers linked to each other on the content container display screen after creation when a new content container is created, depending on the client instruction content container created method according to claim 15, wherein to change. From the content of the content recorded in the server, the step of automatically setting information to be added to the event information and registering it in the event data table,
From the similarity of a plurality of contents recorded in the server, the step of newly generating the event information and registering it in the event data table,
16. The content according to claim 15 , further comprising a step of determining which event information of the event information registered in the event data table is most suitable for the content recorded in the server. Container creation method. The event information acquired from the external application software, claim 15 content container created method according to register in the event data table.

Images