JP2013011928A - Event information collection method, event information collection device and event information collection program - Google Patents

Abstract

An object of the present invention is to classify content efficiently.
An event information collection device includes an event storage unit, a reception unit, and a storage unit. The event storage unit stores a plurality of combinations of the name of the event scheduled by the user and the scheduled time that is the range of the time when the event is performed or the planned location where the event is performed. The reception unit receives predetermined content from a user terminal used by a user who performs any of the events stored in the event storage unit. The storage unit stores the content in the event storage unit in association with the scheduled time including the generation time of the content received by the reception unit in the time range, or associates the content with the planned location that matches the generation location of the content The content is stored in the event storage unit.
[Selection] Figure 3

Description

  Embodiments described herein relate generally to an event information collection method, an event information collection device, and an event information collection program.

  In recent years, mobile terminals such as mobile phones having a photographing function have become widespread. Such a mobile terminal generates image data (still image data or moving image data) by performing a photographing process, and records the generated image data in its own device. There is also a mobile terminal having a recording function, and the mobile terminal generates voice data by performing a recording process, and records the generated voice data in its own device.

  Such a user of a mobile terminal often takes pictures or records using the mobile terminal when participating in events such as school excursions or weddings. Then, after the event ends, the user may save contents such as image data and audio data generated by the mobile terminal in a PC (Personal Computer) or the like. As a result, the user can browse photos and videos taken during school excursions, weddings, etc. on a PC, and can view audio recorded during excursions, weddings, etc.

  Here, there are cases where the above-described user organizes content (image data, audio data, etc.) stored in the PC. For example, the user may arrange the events corresponding to the content to be clear by changing the file name of the content. In the case of this example, the user can browse the content for each event.

JP 2001-344591 A

  However, the above prior art has a problem that it takes time and effort to classify content for the user. Specifically, since the user changes the file name of the content, it takes time to classify the content, and as a result, the content may not be classified.

  The present invention has been made in view of the above, and an object of the present invention is to provide an event information collection method, an event information collection device, and an event information collection program capable of efficiently classifying content.

  The event information collection method according to the embodiment is an event information collection method executed by an event information collection device, and includes a name of an event scheduled by a user and a scheduled time range where the event is performed. Or an accepting step of accepting predetermined content from a user terminal used by a user who performs one of each event stored in an event storage unit that stores a plurality of combinations with a planned place where the event is to be performed; If the content received by the receiving step includes the generation time of the content, the content is stored in the event storage unit in association with the scheduled time including the generation time within the time range, or When the content includes a generation location of the content, the content is associated with the planned location that matches the generation location. Characterized in that it includes a storage step of storing the contents in the event storage unit.

  The event information collection method, the event information collection device, and the event information collection program according to the embodiment have an effect of efficiently classifying content.

FIG. 1 is a diagram illustrating a configuration example of an event information collection system according to the first embodiment. FIG. 2 is a diagram illustrating an example of processing performed by the event information collection system according to the first embodiment. FIG. 3 is a diagram illustrating a configuration example of the event information collection device according to the first embodiment. FIG. 4 is a diagram illustrating an example of an event storage unit according to the first embodiment. FIG. 5 is a flowchart of a process procedure performed by the event information collection apparatus according to the first embodiment. FIG. 6 is a diagram illustrating an example of the event storage unit according to the first embodiment. FIG. 7 is a diagram illustrating an example of an event storage unit according to the first embodiment. FIG. 8 is a diagram illustrating an example of an event storage unit according to the first embodiment. FIG. 9 is a diagram illustrating a computer that executes an event information collection program.

  Embodiments of an event information collection method, an event information collection device, and an event information collection program according to the present invention will be described below in detail with reference to the drawings. In addition, this invention is not limited by this Example.

[Configuration of event information collection system]
First, the event information collection system according to the first embodiment will be described with reference to FIG. FIG. 1 is a diagram illustrating a configuration example of an event information collection system 1 according to the first embodiment. In the example shown in FIG. 1, the event information collection system 1 includes a mobile terminal 10 and an event information collection device 100. The mobile terminal 10 and the event information collection device 100 are connected to a communicable state via the network N.

  The mobile terminal 10 has a shooting function for taking pictures and moving images, and is a user terminal such as a mobile phone or a PDA (Personal Digital Assistant). The event information collection device 100 collects image data generated by the mobile terminal 10 and arranges the collected image data.

  Here, the user of the mobile terminal 10 according to the first embodiment registers in advance the event schedule (schedule) in the event information collecting apparatus 100 when an event such as a school trip or a wedding is performed. Specifically, events such as school trips and weddings are generally scheduled in advance. For example, when the event is a school excursion, events such as “meeting (calling)”, “sightseeing”, “meal”, etc. are determined in advance, and the start time and end of each event The time, place where each event is held, etc. are determined in advance. Also, for example, when the event is a wedding, events such as “formula start”, “greeting greeting”, “cake cut”, etc. are performed, and the start time and end time of each event are determined in advance. ing.

  In the following, the time when an event is scheduled to start is referred to as “scheduled start time”, the time when the event is scheduled to end is referred to as “scheduled end time”, and the event is scheduled to be held. In some cases, the designated place is referred to as “planned place”.

  In the first embodiment, the event information collection device 100 provides the mobile terminal 10 with a schedule input screen for inputting such a schedule. Then, the user of the mobile terminal 10 accesses the event information collection device 100 using the mobile terminal 10, and displays the event name, scheduled start time, and end on the schedule input screen provided from the event information collection device 100. The schedule is registered in the event information collection device 100 by inputting the scheduled time, the planned location, and the like.

  When the user of the mobile terminal 10 actually participates in an event such as a school trip or a wedding and takes a picture using the mobile terminal 10, the image data generated by the mobile terminal 10 is displayed. By transmitting from the mobile terminal 10 to the event information collection device 100, such image data can be classified for each event.

  Specifically, when the event information collection device 100 receives image data from the mobile terminal 10, the event information collection device 100 compares the shooting time, which is the time when the image data is generated, with the schedule registered in advance by the user. To do. Then, the event information collection device 100 identifies an event whose image data shooting time is included between the scheduled start time and the scheduled end time from each event included in the schedule, and associates the image data with the identified event. Remember. In this way, each time the event information collection device 100 receives image data from the mobile terminal 10, it stores the image data in association with the event. Thereby, the event information collection device 100 can classify and store the image data generated by the mobile terminal 10 for each event. As a result, the user of the mobile terminal 10 can browse the image data classified for each event by accessing the event information collection device 100.

  The user of the mobile terminal 10 can correct the schedule registered in the event information collection device 100 or add an event to such a schedule even while participating in school excursions or weddings. You can also do it. Specifically, the user moves the schedule registration screen provided from the event information collection device 100 by accessing the event information collection device 100 using the mobile terminal 10 even during participation in the event. It can be displayed on the body terminal 10. The user can change various information related to the event and add an event on the schedule registration screen. Thereby, the user of the mobile terminal 10 can change to a schedule that matches the actual action even if the schedule registered in advance in the event information collection device 100 is changed.

  In the above example, the event information collection device 100 classifies the image data received from the mobile terminal 10 for each event. However, the event information collection device 100 can receive content other than the image data from the mobile terminal 10. The received content may be classified for each event. For example, the event information collection device 100 receives audio data recorded by the mobile terminal 10 from the mobile terminal 10 and classifies the audio data for each event based on the recording time of the received audio data. Also good.

  Next, the flow of processing by the mobile terminal 10 and the event information collection device 100 shown in FIG. 1 will be described using FIG. FIG. 2 is a diagram illustrating an example of processing performed by the event information collection system 1 according to the first embodiment.

  As shown in FIG. 2, the mobile terminal 10 registers a schedule T10 including an action schedule, a visited place, and the like in the event information collection device 100 as advance preparation. When the mobile terminal 10 generates content such as image data or audio data, the mobile terminal 10 transmits the content to the event information collection device 100 in accordance with an operation by the user. Thereby, the event information collection device 100 classifies the content received from the mobile terminal 10 for each event. Moreover, the mobile terminal 10 corrects the schedule T10 as needed according to the user's operation. As described above, the mobile terminal 10 transmits the content to the event information collection device 100 as needed or modifies the schedule T10 as needed according to the operation by the user while the schedule T10 is being performed by the user. Or

  Thereby, the user can browse the image data classified for each event by accessing the event information collection device 100 after the event such as the school trip or the wedding is finished. That is, the content classified for each event by the event information collection apparatus 100 becomes an event album or a life log for the user.

[Configuration of event information collection device]
Next, the event information collection device 100 shown in FIG. 1 will be described with reference to FIG. FIG. 3 is a diagram illustrating a configuration example of the event information collection device 100 according to the first embodiment. Hereinafter, image data will be described as an example of content. However, examples of content are not limited to image data, and may be audio data or the like. As illustrated in FIG. 3, the event information collection apparatus 100 according to the first embodiment includes an IF (interface) unit 110, an event storage unit 120, and a control unit 130.

  The IF unit 110 transmits and receives various data to and from an external device other than the event information collection device 100. For example, the IF unit 110 provides a schedule input screen or the like to the mobile terminal 10. For example, the IF unit 110 receives image data from the mobile terminal 10.

  The event storage unit 120 is, for example, a semiconductor memory device such as a RAM (Random Access Memory) or a flash memory, or a storage device such as a hard disk or an optical disk, and stores various information related to the event.

  Specifically, the event storage unit 120 stores the name of the event scheduled by the user of the mobile terminal 10, the scheduled start time and scheduled end time of the event, the scheduled location where the event is to be performed, and the like. In addition, the event memory | storage part 120 in Example 1 shall memorize | store the event group performed in this event for every predetermined event. For example, the event storage unit 120 individually stores an event group performed in the event “school trip” and an event group performed in the event “wedding”.

  Here, FIG. 4 illustrates an example of the event storage unit 120 according to the first embodiment. Note that the event storage unit 120 illustrated in FIG. 4 stores various types of information related to event groups that are performed during school excursions. In the example illustrated in FIG. 4, the event storage unit 120 includes items such as “scheduled time”, “planned place”, “event name”, and “related information link”. Hereinafter, “scheduled time”, “scheduled place”, and “event name” stored in the event storage unit 120 may be collectively referred to as “scheduled information”.

  “Scheduled time” indicates a scheduled start time at which an event is scheduled to start and an scheduled end time at which an event is scheduled to end. The “scheduled time” illustrated in FIG. 4 stores the scheduled start time and the scheduled end time in the format of “YYYY / MM / DD scheduled start time (HH: MM) −scheduled end time (HH: MM)”. Shall be.

  “Scheduled place” indicates a place where an event is scheduled to be performed. The “planned place” may store a place name, a store name, a vehicle name, and the like, but may store location information (latitude and longitude) of the place name along with the place name.

  “Event name” indicates the name of the event. The “related information link” indicates a storage location (file path) of image data generated at a corresponding scheduled time. The “related information link” stores various types of information by the storage unit 133 described later.

  That is, the event storage unit 120 in FIG. 4 is scheduled to have the event name “Gathering” at the planned location “A Junior High School” at the scheduled time “June 19, 2011, 10:00 to 10:30”. It shows that there is. Further, the event storage unit 120 performs the event name “move” at the planned location “bus” at the scheduled time “10:30 to 12:00” and the scheduled time “12:00 to 13:00”. The event name “Lunch” will be held at the planned location “B Restaurant” at “Min”, and the event name “Kiyomizu Temple Visit” will be held at the planned location “Kyoto Kiyomizu-dera” at the scheduled time “13: 00-16: 00” The event name “Kinkakuji visit” will be held at the planned location “Kyoto Kinkakuji” at the scheduled time “16:00 to 19:00”, and the planned location at the scheduled time “19:00 to 21:00” An example is shown in which the event name “Dinner” is performed at “C Hotel”.

  4 stores the image data “AAA.gif” generated by the mobile terminal 10 at the scheduled time “10:00 to 10:30” under “/ home / gif”. Indicates that it is stored. The device in which the image data “AAA.gif” is stored may be the event information collection device 100 or a file server connected to the event information collection device 100.

  In the example illustrated in FIG. 4, an example in which both the scheduled start time and the scheduled end time are stored in the scheduled time of the event storage unit 120 is illustrated, but only the scheduled start time may be stored. In such a case, the scheduled end time of the predetermined event is assumed to be the scheduled start time of the next event after the predetermined event. For example, “hours and minutes” of the scheduled time of the event storage unit 120 illustrated in FIG. 4 are “10:00”, “10:30”, “12:00”, “13:00”, “16” in order from the top. 0:00 "," 19:00 ".

  Although not shown in FIG. 4, the event storage unit 120 may have an item such as “user identifier” for identifying the user of the mobile terminal 10, for example. In other words, the event storage unit 120 may store various types of information regarding each event described above for each user.

  Returning to the description of FIG. 3, the control unit 130 includes, for example, an electronic circuit such as a CPU (Central Processing Unit) and an MPU (Micro Processing Unit), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), and the like. It is an integrated circuit and controls various processes by the event information collection device 100. In the example illustrated in FIG. 3, the control unit 130 includes a schedule information update unit 131, a reception unit 132, and a storage unit 133.

  The schedule information update unit 131 updates the schedule information in the event storage unit 120. Specifically, the schedule information update unit 131 updates “schedule time”, “schedule location”, and “event name” in the event storage unit 120.

  When a schedule registration screen is requested from the mobile terminal 10 by HTTP (Hypertext Transfer Protocol) or the like, the schedule information update unit 131 according to the first embodiment uses the schedule information corresponding to the user of the mobile terminal 10 as an event. Obtained from the storage unit 120. Then, the event storage unit 120 transmits, to the mobile terminal 10, HTML (HyperText Markup Language) text or the like constituting the schedule registration screen in which the acquired schedule information is reflected. At this time, if the schedule information corresponding to the user of the mobile terminal 10 is not stored in the event storage unit 120, the event storage unit 120 newly registers a schedule registration screen that does not reflect the schedule information. Is transmitted to the mobile terminal 10 as a screen for performing the above.

  Thereby, a schedule registration screen is displayed on the mobile terminal 10. When the schedule information is input to the schedule registration screen by the user of the mobile terminal 10, the mobile terminal 10 transmits the input schedule information to the event information collection device 100. In such a case, the schedule information update unit 131 updates the schedule information received from the mobile terminal 10 in the event storage unit 120. The schedule information update unit 131 transmits a schedule registration screen for newly registering a schedule to the mobile terminal 10, and when schedule information is received from the mobile terminal 10, the schedule information update unit 131 adds a new schedule to the event storage unit 120. Stores schedule information.

  The accepting unit 132 accepts predetermined content from the mobile terminal 10. Specifically, the reception unit 132 according to the first embodiment receives image data as predetermined content from the mobile terminal 10 used by a user who performs any of the events stored in the event storage unit 120. Accept.

  Here, when the mobile terminal 10 generates image data after the shooting process, the mobile terminal 10 adds shooting time information indicating the time when the shooting process is performed to the image data. For example, the mobile terminal 10 gives image data generation time (time stamp) to the image data as shooting time information. Then, when the user performs an operation for uploading the image data to the event information collection device 100, the mobile terminal 10 transmits the image data to which the shooting time information is given to the event information collection device 100. . The reception unit 132 of the event information collection device 100 receives the image data transmitted from the mobile terminal 10 in this way.

  The storage unit 133 stores the content received by the receiving unit 132 in the event storage unit 120. Specifically, the storage unit 133 according to the first embodiment includes the shooting time indicated by the shooting time information given to the image data received by the receiving unit 132, and the scheduled time stored in the event storage unit 120. Compare Then, the storage unit 133 associates the shooting time with the scheduled time including the shooting time within the time range, and uses the file path indicating the storage location of the image data received by the reception unit 132 as the related information link of the event storage unit 120. Store.

  For example, it is assumed that various types of information stored in the schedule information (scheduled time, planned location, event name) in the event storage unit 120 are in the state shown in FIG. Further, it is assumed that the reception unit 132 has received image data “AAA.gif” to which shooting time information indicating the shooting time “June 19, 2011, 10:15” is added. Further, it is assumed that the event information collection apparatus 100 stores the image data “AAA.gif” in a directory (or “folder”) under “/ home / gif”.

  In such a case, the storage unit 133 includes the image data “AAA.gif” shooting time “June 19, 2011 10:15” within the time range of the scheduled time stored in the event storage unit 120. Specify the scheduled time included in the. Here, the storage unit 133 specifies the scheduled time “June 19, 2011 10:00 to 10:30” including the imaging time “June 19, 2011 10:15”. Then, the storage unit 133 uses the file path of the image data “AAA.gif” to the related information link of the event storage unit 120 corresponding to the scheduled time “June 19, 2011, 10:00 to 10:30”. A certain “/home/gif/AAA.gif” is stored.

  In this manner, the storage unit 133 compares the shooting time of the image data transmitted from the mobile terminal 10 with the scheduled time of the event storage unit 120, and associates it with an event whose shooting time is included in the scheduled time. The file path of the image data is stored in the event storage unit 120. As a result, the storage unit 133 can store image data that is assumed to be captured while a predetermined event registered in the event storage unit 120 is being performed, in association with the predetermined event.

  In the above example, the example in which the mobile terminal 10 gives the shooting time information to the image data is shown. However, when the mobile terminal 10 has a GPS (Global Positioning System) function, the mobile terminal 10 may add shooting position information indicating the position where the shooting process is performed to the image data. Specifically, when performing a photographing process, the mobile terminal 10 acquires position information (latitude and longitude) where the mobile terminal 10 is located by a GPS function. When the mobile terminal 10 generates image data after the shooting process, the mobile terminal 10 adds the position information to the image data as shooting position information.

  Here, when the image data with shooting position information as in the above example is received by the receiving unit 132, the storage unit 133 displays the shooting position indicated by the shooting position information given to the image data, The planned location stored in the event storage unit 120 is compared. At this time, the storage unit 133 determines whether or not the place name indicated by the shooting position matches the planned place when the map data in which the latitude and longitude are associated with the place name is held. Further, when the latitude and longitude are stored in the planned location of the event storage unit 120, the storage unit 133 determines that both positions match if the distance from the shooting position is equal to or less than a predetermined threshold. To do. Then, the storage unit 133 stores the file path indicating the storage location of the image data received by the reception unit 132 in the related information link of the event storage unit 120 in association with the planned location that matches the shooting position. Note that if the event storage unit 120 does not have a planned location that matches the shooting position, the storage unit 133 associates the file path of the image data with the planned location that indicates the position near the shooting position, and the event storage unit. It may be stored in 120 related information links.

  In addition, when both the shooting time information and the shooting position information are added to the image data, the storage unit 133 compares the shooting time information with the scheduled time of the event storage unit 120 or the shooting position information. And either one of the processes for comparing the event storage unit 120 and the planned location of the event storage unit 120 may be performed, or both comparison processes may be performed. That is, the storage unit 133 may store the image data in association with the scheduled time in which the shooting time is included in the time range, or store the image data in association with the planned location that matches the shooting position. Alternatively, the image data may be stored in association with a scheduled time in which the shooting time is included in the time range and a planned location that matches the shooting position.

[Processing procedure by event information collection device]
Next, a processing procedure performed by the event information collection apparatus 100 according to the first embodiment will be described with reference to FIG. FIG. 5 is a flowchart of a process procedure performed by the event information collection apparatus 100 according to the first embodiment. In FIG. 5, image data reception processing by the event information collection device 100 will be described.

  As shown in FIG. 5, the event information collection device 100 determines whether image data has been received from the mobile terminal 10 (step S101). If the event information collection device 100 has not received image data (No at step S101), the event information collection device 100 waits until image data is received.

  On the other hand, when the event information collection device 100 receives image data from the mobile terminal 10 (Yes at step S101), the event information collection device 100 stores the shooting time given to the received image data and the event storage unit 120. The scheduled time is compared (step S102).

  If the scheduled time including the image data shooting time exists in the time range (Yes in step S103), the event information collecting apparatus 100 associates the scheduled time with the file indicating the storage location of the image data. The path and the like are stored in the related information link of the event storage unit 120 (step S104).

  On the other hand, the event information collection device 100 returns to the processing procedure in step S101 when there is no scheduled time including the image data shooting time in the time range (No in step S103).

[Effect of Example 1]
As described above, the event information collection device 100 according to the first embodiment includes the name of the event scheduled by the user, the scheduled time that is the range of the time when the event is performed, and the scheduled event. An event storage unit 120 that stores a plurality of combinations with places is provided. Then, the reception unit 132 of the event information collection apparatus 100 receives predetermined data such as image data and audio data from the mobile terminal 10 used by a user who performs any of the events stored in the event storage unit 120. Accept content. Then, the storage unit 133 of the event information collection device 100 associates the generation time with the scheduled time including the generation time in the time range when the content generation time for the content received by the reception unit 132 is included. Is stored in the event storage unit 120, or the content is stored in the event storage unit 120 in association with a planned location that matches the generation location.

  Thereby, the event information collection device 100 according to the first embodiment can classify and store various contents generated by the mobile terminal 10 for each event. That is, the event information collection device 100 can efficiently organize various contents based on pre-registered schedule information. As a result, the user of the mobile terminal 10 can browse the contents classified for each event by accessing the event information collection device 100.

  In addition, the event information collection apparatus 100 according to the first embodiment classifies various contents transmitted from the mobile terminal 10 as needed based on the schedule information stored in the event storage unit 120, so that the event album In addition, the user can create an action history such as a user's life log dictionary with content indicating “when, where, and what”.

  For example, as a method for classifying image data of photos and videos taken at travel destinations, the file name of the image data can be changed manually by the user, or the image data can be stored in a folder (directory) created for each event. Classification is possible. However, since such a classification method is performed after an event such as a travel destination has been completed, image data that is strongly impressed by the user is classified into a folder created for each event. Image data with a weak impression that forgets the shooting position or the like may not be correctly classified. Even if the image data has a weak impression, the user's interest in the image data may increase later. However, since it is not correctly classified, it is difficult for the user to find this kind of image data.

  On the other hand, since the event information collection apparatus 100 according to the first embodiment can classify various contents efficiently and accurately for each event, it is image data that increases the interest level of the user later. Even if it exists, it can hold | maintain so that a user can discover easily.

  1 shows an example in which the event information collection system 1 includes one mobile terminal 10, the event information collection system 1 may include a plurality of mobile terminals. Further, the schedule information stored in the event storage unit 120 of the event information collection device 100 may be shared by a plurality of users. In other words, the related information link of the event storage unit 120 may store only information related to content transmitted from a specific user, or may store information related to content transmitted from a plurality of users. .

  In the first embodiment, as illustrated in FIG. 4, the case where the event storage unit 120 stores a group of events performed in a school excursion has been described as an example. Here, another example of the event group stored in the event storage unit 120 will be described with reference to FIG. FIG. 6 is a diagram illustrating an example of the event storage unit 120 according to the first embodiment. The event storage unit 120 illustrated in FIG. 6 stores various types of information related to an event group performed at a wedding.

  Specifically, the event storage unit 120 in FIG. 6 indicates that all events are scheduled to be performed at the planned place “D wedding hall”. The event storage unit 120 in FIG. 6 receives the event name “entrance” at the scheduled time “June 19, 2011 11:30 to 12:00” and the scheduled time “12:00 to 12:00”. “30 minutes” is the event name “Greeting Greeting”, the scheduled time is “12:30 to 13:00”, the event name “Event X” is scheduled, and the scheduled time is “13:00 to 13:30” Event name “Event Y” will be held, event time “Event Z” will be held at the scheduled time “14: 00-14: 30”, and scheduled time “14: 30-15: 00” An example in which the event name “Acknowledgment” is performed is shown.

  As described above, in the case of an event where various events are performed at a specific place such as a wedding, the same information may be stored in the planned place of the event storage unit 120. In the case of the example illustrated in FIG. 6, for example, a wedding presenter or the like accesses the event information collection device 100 to update the schedule information in the event storage unit 120 according to the actual progress. be able to.

  Here, the various event groups stored in the event storage unit 120 illustrated in FIG. 4 and FIG. 6 described above are “schedule type” in which various events include a scheduled time. Change. However, the event storage unit 120 according to the first embodiment may store a group of events other than the “schedule type”. Specifically, the event storage unit 120 may store, as a list, planned visit locations that the user plans to visit regardless of the time at which the event is performed.

  This point will be described with reference to FIGS. 7 and 8 are diagrams illustrating an example of the event storage unit 120 according to the first embodiment. The event storage unit 120 illustrated in FIG. 7 stores information related to a place name of a destination to be visited in such a trip, with “travel” performed by the user as an event. In the example illustrated in FIG. 7, the event storage unit 120 stores “South America”, “Peru”, and “Machu Picchu” in the planned location.

  Further, the event storage unit 120 illustrated in FIG. 8 stores information related to the name of a shop to be visited that is scheduled to be visited in such a meal with “meal (dining out)” performed by the user as an event. In the example illustrated in FIG. 8, the event storage unit 120 stores “E Western restaurant”, “F Chinese restaurant”, and “G Japanese restaurant” at the planned location.

  The various event groups stored in the event storage unit 120 illustrated in FIGS. 7 and 8 can be said to be “list type” in that various events can occur regardless of time. The user of the mobile terminal 10 has the mobile terminal 10 equipped with a GPS function when registering various “list type” event groups in the event storage unit 120. In such a case, the mobile terminal 10 acquires position information of the mobile terminal 10 by the GPS function at the time of shooting processing, and assigns the position information to the image data as shooting position information.

  For example, assume that various types of information stored in the event storage unit 120 are in the state illustrated in FIG. Further, it is assumed that the image data “CCC.gif” to which the photographing position information “Machu Picchu” is added is received by the receiving unit 132. Further, the event information collection apparatus 100 stores the image data “CCC.gif” in a directory under “/ home / gif”. In such a case, the storage unit 133 identifies a planned location that matches the shooting position information given to the image data “CCC.gif” among the planned locations stored in the event storage unit 120 illustrated in FIG. To do. Here, since the shooting position information of the image data “CCC.gif” indicates “Machu Picchu”, the storage unit 133 identifies the planned locations “South America” and “Machu Picchu” that coincide with the shooting position “Machu Picchu”. Then, the storage unit 133 stores “/home/gif/CCC.gif” which is the file path of the image data “CCC.gif” in the related information link of the event storage unit 120 corresponding to the planned location “South America”. At the same time, “/home/gif/CCC.gif” is stored in the related information link of the event storage unit 120 corresponding to the planned place “Machu Picchu”.

  By the way, the event information collection method, the event information collection device, and the event information collection program according to the present invention may be implemented in various different forms other than the above-described embodiments. Therefore, in the second embodiment, another embodiment of the event information collecting method, the event information collecting apparatus, and the event information collecting program according to the present invention will be described.

[Scheduled location of event storage unit]
In the above embodiment, an example is shown in which names such as place names and store names, latitudes and longitudes are stored in the planned locations of the event storage unit 120. However, information indicating a predetermined range on the map data may be stored in the planned location of the event storage unit 120. That is, the user may select a predetermined area for the map data held by the event information collection device 100 and register the selected area in the planned location of the event storage unit 120. In such a case, information indicating the area selected by the user (such as latitude and longitude ranges) is stored in the planned location of the event storage unit 120.

[Reception time]
In the above embodiment, the storage unit 133 stores the time when the content is received by the reception unit 132 and the event storage unit 120 when time information or position information is not added to the content received by the reception unit 132. The stored scheduled time may be compared.

  Further, in the above embodiment, when the mobile terminal 10 transmits image data to the event information collection device 100, the mobile terminal 10 acquires the location information where the mobile terminal 10 is located by the GPS function, and the image data is sent to the event together with the location information. You may transmit to the information collection apparatus 100. FIG. That is, the mobile terminal 10 may transmit a transmission location, which is a location where image data is transmitted, to the event information collection device 100. In such a case, when the time information and the position information are not given to the content accepted by the accepting unit 132, the storage unit 133 and the transmission location where the content is transmitted by the mobile terminal 10 and the event storage unit 120 You may compare with the scheduled time memorize | stored.

[content]
Further, in the above-described embodiment, the description has been given by taking the image data, which is still image data or moving image data, and audio data as examples. However, the content example is not limited to this. For example, the content may be text information (diary, impression, comment, etc.) written on an electronic bulletin board or blog. For example, it is assumed that the event information collection device 100 is operated by a travel agency, and the event information collection device 100 provides an electronic bulletin board or the like that can write impressions during travel. Then, the user writes an impression or the like on the electronic bulletin board via the mobile terminal 10. At this time, the event information collection apparatus 100 may manage character string data written on an electronic bulletin board or the like as content. For example, the storage unit 133 of the event information collection device 100 can, when an impression or the like is written on an electronic bulletin board or the like, an electronic bulletin board that can browse the impression on the related information link of the event storage unit 120 corresponding to the written time URL (Uniform Resource Locator) may be stored.

  Moreover, in the said Example, the mobile terminal 10 had an imaging | photography function and a recording function, and the image data and audio | voice data produced | generated by the mobile terminal 10 were shown to the event information collection apparatus 100 was shown. However, the content transmitted to the event information collection device 100 may not be generated by the mobile terminal 10. For example, when a user takes a picture with a digital camera or a digital video camera, the content (image data or the like) generated by the digital camera or the like is stored in a communicable device (for example, a notebook computer) and the user The content may be transmitted from the device to the event information collection device 100.

[Mobile terminal]
Moreover, in the said Example, the schedule was previously registered with respect to the event information collection apparatus 100 by the mobile terminal 10, and the example to which a content is transmitted with respect to the event information collection apparatus 100 by the mobile terminal 10 was shown. However, the device that registers the schedule in advance and the device that transmits the content may be different devices.

[Auto Send]
Moreover, in the said Example, the mobile terminal 10 showed the example which transmits a content to the event information collection apparatus 100 according to operation by a user. However, when the mobile terminal 10 generates content such as image data or audio data, the mobile terminal 10 may automatically transmit the generated content to the event information collection device 100.

[System configuration]
In addition, among the processes described in the above embodiment, all or a part of the processes described as being automatically performed can be manually performed, or the processes described as being performed manually can be performed. All or a part can be automatically performed by a known method. In addition, the processing procedures, specific names, and information including various data and parameters shown in the document and drawings can be arbitrarily changed unless otherwise specified. For example, the various information shown in FIGS. 4 and 6 to 8 is an example and can be arbitrarily changed.

  Further, each component of each illustrated apparatus is functionally conceptual, and does not necessarily need to be physically configured as illustrated. In other words, the specific form of distribution / integration of each device is not limited to that shown in the figure, and all or a part thereof may be functionally or physically distributed or arbitrarily distributed in arbitrary units according to various loads or usage conditions. Can be integrated and configured.

[program]
It is also possible to create a program in which the processing executed by the event information collection apparatus 100 described in the above embodiment is described in a language that can be executed by a computer. For example, it is also possible to create an event information collection program in which processing executed by the event information collection apparatus 100 according to the first embodiment is described in a language that can be executed by a computer. In this case, when the computer executes the event information collection program, the same effect as in the first embodiment can be obtained. Further, the event information collecting program is recorded on a computer-readable recording medium, and the event information collecting program recorded on the recording medium is read by the computer and executed, thereby realizing the same processing as in the first embodiment. May be. Hereinafter, an example of a computer that executes an event information collection program that realizes the same function as the event information collection apparatus 100 illustrated in FIG. 3 will be described.

  FIG. 9 is a diagram illustrating a computer 1000 that executes an event information collection program. As illustrated in FIG. 9, the computer 1000 includes, for example, a memory 1010, a CPU 1020, a hard disk drive interface 1030, a disk drive interface 1040, a serial port interface 1050, a video adapter 1060, and a network interface 1070. These units are connected by a bus 1080.

  The memory 1010 includes a ROM (Read Only Memory) 1011 and a RAM 1012 as illustrated in FIG. The ROM 1011 stores a boot program such as BIOS (Basic Input Output System). The hard disk drive interface 1030 is connected to the hard disk drive 1031 as illustrated in FIG. The disk drive interface 1040 is connected to the disk drive 1041 as illustrated in FIG. For example, a removable storage medium such as a magnetic disk or an optical disk is inserted into the disk drive. The serial port interface 1050 is connected to a mouse 1051 and a keyboard 1052, for example, as illustrated in FIG. The video adapter 1060 is connected to a display 1061, for example, as illustrated in FIG.

  Here, as illustrated in FIG. 9, the hard disk drive 1031 stores, for example, an OS 1091, an application program 1092, a program module 1093, and program data 1094. That is, the event information collection program is stored in, for example, the hard disk drive 1031 as a program module in which a command executed by the computer 1000 is described. For example, the schedule information update procedure for executing the same information processing as the schedule information update unit 131 illustrated in FIG. 3, the reception procedure for executing the same information processing as the reception unit 132, and the same information processing as the storage unit 133 are performed. A program module 1093 describing the storage procedure to be executed is stored in the hard disk drive 1031.

  Further, various data held by the event information collection device 100 described in the above embodiment is stored as program data in, for example, the memory 1010 or the hard disk drive 1031. Then, the CPU 1020 reads the program module 1093 and program data 1094 stored in the memory 1010 and the hard disk drive 1031 to the RAM 1012 as necessary, and executes the schedule information update procedure, the reception procedure, and the storage procedure.

  Note that the program module 1093 and the program data 1094 related to the event information collection program are not limited to being stored in the hard disk drive 1031, but are stored in, for example, a removable storage medium and read out by the CPU 1020 via the disk drive or the like. May be. Alternatively, the program module 1093 and the program data 1094 related to the event information collection program are stored in another computer connected via a network (LAN (Local Area Network), WAN (Wide Area Network), etc.), and the network interface 1070 is stored. It may be read by the CPU 1020 via

DESCRIPTION OF SYMBOLS 1 Event information collection system 10 Mobile terminal 100 Event information collection apparatus 110 IF part 120 Event memory | storage part 130 Control part 131 Schedule information update part 132 Reception part 133 Storage part

Claims (5)

An event information collection method executed by an event information collection device,
Each event stored in the event storage unit that stores a plurality of combinations of the name of the event scheduled by the user and the scheduled time that is the range of the time when the event is performed or the planned location where the event is performed A receiving step of receiving predetermined content from a user terminal used by a user who performs any of the following:
If the content received by the receiving step includes the generation time of the content, the content is stored in the event storage unit in association with the scheduled time including the generation time within the time range, or A storage step of storing the content in the event storage unit in association with the scheduled location that matches the generation location when the content includes the generation location of the content. Collection method. An event storage unit that stores a plurality of combinations of the name of an event scheduled by the user and a scheduled time that is a range of time at which the event is performed or a planned location at which the event is performed;
A receiving unit that receives predetermined content from a user terminal used by a user who performs any of the events stored in the event storage unit;
When the content received by the receiving unit includes the generation time of the content, the content is stored in the event storage unit in association with the scheduled time including the generation time within the time range, or And a storage unit that stores the content in the event storage unit in association with the scheduled location that matches the generation location when the content includes the generation location of the content. Collection device. The storage unit
When the content received by the reception unit does not include the generation time and generation location of the content, the reception time when the content is received by the reception unit is associated with the scheduled time including the time range. The event information collection device according to claim 2, wherein the content is stored in the event storage unit. The storage unit
When the content received by the reception unit does not include the generation time and the generation location of the content, the content is associated with the scheduled location that matches the transmission location where the content is transmitted by the user terminal. The event information collection device according to claim 2, wherein the event storage unit stores the event information in the event storage unit. Each event stored in the event storage unit that stores a plurality of combinations of the name of the event scheduled by the user and the scheduled time that is the range of the time when the event is performed or the planned location where the event is performed An acceptance procedure for accepting predetermined content from a user terminal used by a user who performs any of the following:
When the content generation time is included in the content received by the reception procedure, the content is stored in the event storage unit in association with the scheduled time including the generation time within the time range, or A storage procedure for storing the content in the event storage unit in association with the scheduled location that matches the generation location when the content includes the generation location of the content; Event information collection program.

Images