JP2013235380A - Schedule management device, schedule management method and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a schedule management device that allows participants to share data related to an event with simple operation.SOLUTION: A schedule management device includes: an event information reception unit for receiving an event, a type of related data and a location where the related data is stored; an icon extraction unit 103 for extracting an icon of the type received by the event information reception unit from an icon storage unit 121 for storing the type of related data and an icon in association with each other; a link icon generation unit 104 for generating a link icon in which the icon and the storage location are associated with each other; an event notification information transmission unit for transmitting event notification information including the link icon to a user terminal; a provision request reception unit for receiving a request to provide the related data in the storage location associated with the link icon from the user terminal; a related data extraction unit 108 for extracting the related data from the storage location; and a related data transmission unit for transmitting the related data to the user terminal.

Description

  The present invention relates to a schedule management device, a schedule management method, and a program.

  Conventionally, software for managing schedules of individuals and groups is known. In such schedule management software, by registering event participants when registering an event, the participants can be managed together with the event, and event information can be shared among registered participants. . Furthermore, in the schedule management software, when an event is registered, information about the event is notified to the event participants by e-mail (see, for example, Patent Document 1).

  However, in the conventional schedule management software, the contents registered in the schedule management software can be shared among the participants, but the data file of the conference material, the DB (database) referenced for the conference, etc. The data to be shared by participants had to be sent separately to the participants.

  The present invention has been made in view of the above, and an object of the present invention is to provide a schedule management device, a schedule management method, and a program capable of sharing related data related to an event among participants by a simple operation. And

  In order to solve the above-described problems and achieve the object, the present invention is a schedule management device, which is an event, a type of related data related to the event, and a storage location where the related data is stored. An event information receiving unit that receives the related data, a related data storage unit that stores the related data in the storage location, an icon storage unit that stores the type of the related data and an icon indicating the related data in association with each other, In the icon storage unit, an icon extraction unit that extracts the icon associated with the type received by the event information reception unit, the icon extracted by the icon extraction unit, and the storage location of the related data A link icon creation unit for creating a link icon associated with the link icon, the link icon, and the event. An event notification information transmitting unit that transmits event notification information to a user terminal, and when the link icon is selected on the user terminal, the event notification information is stored in the storage location associated with the link icon from the user terminal. A provision request receiving unit that receives the provision request of the related data; a related data extraction unit that extracts the related data from the storage location of the related data storage unit indicated in the provision request; and the related data extraction unit And a related data transmitting unit that transmits the extracted related data to the user terminal.

  The present invention is also a schedule management method executed by a schedule management device, wherein the schedule management device stores related data related to an event, a type of the related data, and the related data An icon storage unit for storing an icon indicating data in association with each other, the event, a type of related data related to the event, and a storage location of the related data storage unit in which the related data is stored An event information receiving step for receiving, an icon extracting step for extracting the icon associated with the type received in the event information receiving step in the icon storage unit, and the icon extracted in the icon extracting step Linked to the storage location of the related data Link icon creating step for creating an icon, event notification information sending step for sending event notice information including the link icon and the event to a user terminal, and when the link icon is selected in the user terminal, A provision request receiving step of receiving the provision request of the related data stored in the storage location associated with the link icon from the user terminal; and the storage indicated in the provision request in the related data storage unit The method includes a related data extracting step of extracting the related data from a place, and a related data transmitting step of transmitting the related data extracted in the related data extracting step to the user terminal.

  Further, the present invention provides a computer including a related data storage unit that stores related data of an event, and an icon storage unit that stores a type of the related data and an icon indicating the related data in association with each other. An event information receiving unit that receives an event, a type of related data related to the event, and a storage location of the related data storage unit in which the related data is stored, and the icon storage unit receives the event information An icon extracting unit that extracts the icon associated with the type received by the unit, and a link that creates a link icon that associates the icon extracted by the icon extracting unit with the storage location of the related data Event notification information including an icon creation unit, the link icon, and the event When the link icon is selected in the user terminal and the event notification information transmitting unit that transmits to the user terminal, the related data provision request stored in the storage location associated with the link icon from the user terminal In the related data storage unit, the related data extraction unit that extracts the related data from the storage location indicated in the provision request, and the related data extracted by the related data extraction unit Is a program for causing the user terminal to function as a related data transmission unit.

  According to the present invention, there is an effect that related data related to an event can be shared among participants by a simple operation.

FIG. 1 is a diagram illustrating an overall configuration of a schedule management system according to an embodiment. FIG. 2 is a diagram illustrating a data configuration of the schedule management apparatus. FIG. 3 is a diagram schematically illustrating a data configuration of the event information storage unit. FIG. 4 is a diagram schematically illustrating a data configuration of the icon storage unit. FIG. 5 is a flowchart showing the schedule registration process. FIG. 6 is a diagram illustrating an example of a schedule registration screen. FIG. 7 is a diagram for explaining a process of creating a link icon. FIG. 8A is a diagram illustrating an example of attachment of a DB link icon. FIG. 8B is a diagram illustrating an example of attaching the link icon of the list screen data. FIG. 8C is a diagram illustrating an example of attaching a link icon of a document. FIG. 9 is a diagram illustrating an example of the notification mail. FIG. 10 is a flowchart showing a schedule providing process in the schedule management system.

  Exemplary embodiments of a schedule management device, a schedule management method, and a program will be described below in detail with reference to the accompanying drawings.

  FIG. 1 is a diagram illustrating an overall configuration of a schedule management system 1 according to the embodiment. The schedule management system 1 includes a schedule management device 10 and a plurality of user terminals 20 used by each user. The schedule management device 10 and the plurality of user terminals 20 are connected via the network 2.

  As the network 2, the Internet, a LAN (Local Area Network), or a WAN (Wide Area Network) can be used. Note that the network 2 may be wireless or wired.

  The user terminal 20 displays a schedule registration screen on the display unit 21 included in the user terminal 20. Then, in response to an operation from the user, an input of event information related to a predetermined event is accepted, and the event information is transmitted to the schedule management apparatus 10. The event information includes information about the event such as an event name. The event information will be described in detail later. When receiving the event information, the schedule management device 10 registers the event information and manages the schedule of each user based on each event information. For example, the schedule management device 10 notifies the user terminal 20 used by the event participant that the event information has been registered by e-mail. The schedule management device 10 also provides event information and the like to the event participant's user terminal 20 in response to a request from the event participant via the user terminal 20.

  FIG. 2 is a diagram illustrating a data configuration of the schedule management apparatus 10. The schedule management device 10 includes a schedule processing unit 100, an event information storage unit 120, an icon storage unit 121, and a related data storage unit 122.

  The schedule processing unit 100 includes a communication unit 101, an event information registration unit 102, an icon extraction unit 103, a link icon creation unit 104, an event notification information creation unit 105, a notification mail creation unit 106, and a related data registration unit. 107, a related data extracting unit 108, and a related data editing unit 109.

  The communication unit 101 transmits / receives various information to / from the user terminal 20. For example, the communication unit 101 receives event information from the user terminal 20. That is, the communication unit 101 functions as an event information receiving unit.

  The event information registration unit 102 stores the event information received by the communication unit 101 in the event information storage unit 120. FIG. 3 is a diagram schematically illustrating a data configuration of the event information storage unit 120. The event information storage unit 120 includes a registrant, an event scheduled date and time, an event subject, an event category, a place where the event is held, a comment, a storage location and type of related data, a user who views and edits related data, an event Participants (hereinafter referred to as “subjects” as appropriate) and messages are stored in association with each other.

  Here, the related data is data related to the event, and is data that should be shared among the target persons of the event. As related data, for example, when an event is a meeting, there is a file of a meeting material referred to in the meeting. The related data is transmitted from the user terminal 20 to the schedule management device 10 by the operation of the user terminal 20 by the user, and stored in the related data storage unit 122 of the schedule management device 10. The storage location of the related data is a storage location in the related data storage unit 122, and is specified by a URL (Uniform Resource Locator). The type of related data is the type of data. In the present embodiment, there are three types of data: a database (DB), data for displaying a list display screen, and a document.

  The related data browsing user is a user who is permitted to browse related data, that is, a user who has browsing authority. The related data editing user is a user who is permitted to edit related data, that is, a user who has editing authority. For example, in the example of the related data of the subject “Patent Application Case Study Group” shown in FIG. 3, the viewing authority is given to all target persons (user A, user B, user C, and user D) of the event. On the other hand, only the user A has the authority for editing.

  FIG. 3 shows an example of the event “subject meeting for patent application case”, but a plurality of events are registered in the event information storage unit 120 in response to the reception of the event information.

  FIG. 4 is a diagram schematically illustrating a data configuration of the icon storage unit 121. The icon storage unit 121 stores a type of related data and an icon in association with each other.

  Returning to FIG. 2, the icon extraction unit 103 identifies the type of related data from the information received by the communication unit 101 or the event information stored in the event information storage unit 120. The icon extraction unit 103 further refers to the icon storage unit 121 and extracts an icon associated with the specified type from the icon storage unit 121.

  The link icon creation unit 104 identifies the storage location of the related data from the event information. The link icon creation unit 104 further creates a link icon that associates the identified storage location with the icon extracted by the icon extraction unit 103.

  When the communication unit 101 receives a request for providing event notification information related to a predetermined event from the user terminal 20, the event notification information generation unit 105 generates event notification information related to the provision request. Specifically, the event notification information creation unit 105 includes an event name in the provision request, and extracts event information corresponding to the provision request from the event information storage unit 120 using the event name as a search key. The event notification information creation unit 105 further creates event information including the link icon created by the link icon creation unit 104 and the extracted event information for the related data included in the extracted event information. The event notification information creating unit 105 according to the present embodiment has a web server function and creates event notification information as a web page. The event notification information is transmitted to the user terminal 20 by the communication unit 101. That is, the communication unit 101 functions as an event notification information transmission unit.

  When a new event is registered by the event information registration unit 102, the notification mail creating unit 106 creates a notification mail that notifies the user terminal 20 of the registered event target person that the event has been registered. . Specifically, the notification mail creation unit 106 is a notification mail including the link icon created by the link icon creation unit 104 for the storage location of the related data included in the registered event information and the registered event information. Create

  When the communication unit 101 receives related data from the user terminal 20, the related data registration unit 107 writes the received related data in the related data storage unit 122. That is, related data is registered. The related data storage unit 122 stores related data related to the event stored in the event information storage unit 120.

  When the communication unit 101 receives a related data provision request from the user terminal 20, the related data extraction unit 108 extracts the related data indicated in the provision request from the related data storage unit 122. The provision request includes the storage location of the related data, and the related data extraction unit 108 extracts the related data related to the provision request from the related data storage unit 122 using the storage location as a search key. The extracted related data is transmitted to the user terminal 20 by the communication unit 101. The communication unit 101 functions as a provision request receiving unit that receives a related data provision request and functions as a related data transmission unit that transmits related data.

  When the communication unit 101 receives an instruction to edit related data from the user terminal 20, the related data editing unit 109 edits the related data according to the editing instruction in accordance with the received editing instruction. The communication unit 101 functions as an editing instruction receiving unit that receives an instruction to edit related data.

  FIG. 5 is a flowchart showing a schedule registration process in the schedule management system 1. For convenience of explanation, schedule registration processing will be described together with user operations. When registering the schedule, the user confirms the schedule of the target person of the event to be registered, and adjusts the schedule in which each target person can participate (step U100). Specifically, the user operates the user terminal 20 to receive information such as a web page indicating the schedule of each target person from the schedule management apparatus 10 and causes the display unit 21 to display the information. Then, the user adjusts the schedule with reference to the displayed schedule. Then, the user operates the user terminal 20 to display a schedule registration screen on the display unit 21 and inputs event information on the schedule registration screen (step U101).

  FIG. 6 is a diagram illustrating an example of the schedule registration screen 200. The schedule registration screen 200 includes a scheduled date / time registration field 201, a subject name registration field 202, a comment registration field 203, a link icon creation button 204, a target person registration field 205, an execution button 206, and the like. The user can input information in each column.

  In the scheduled date and time registration field 201, the scheduled date and time of event holding is input. In the subject registration column 202, the subject of the event is input. In the comment registration field 203, comments regarding the event are input. In the comment registration field 203, the storage location of the related data is also input. Specifically, a URL link as a storage location is input. The link icon creation button 204 is a button for accepting a link icon creation instruction indicating the URL link input in the comment registration field 203. In the target person registration field 205, the target person of the event is input. The execution button 206 is a button for accepting an event registration instruction for the content registered in the schedule registration screen 200.

  Returning to FIG. 5, the user uploads the related data to the schedule management device 10 by operating the user terminal 20 when the user wants to attach the related data (step U102, Yes). Then, the URL link indicating the storage location of the related data storage unit 122 in which the related data is stored is copied (step U103). Subsequently, the user pastes the copied URL link in the comment registration field 203 of the schedule registration screen 200, and selects the link icon creation button 204 (step U104). When the above operation is performed by the user, the communication unit 101 of the schedule management apparatus 10 receives a link icon creation instruction from the user terminal 20 (step S100). Here, the link icon creation instruction includes a URL link that is the target of the link icon.

  The icon extraction unit 103 of the schedule management apparatus 10 identifies the type of URL link, that is, the type of related data, based on the URL link format included in the link icon creation instruction. The icon extraction unit 103 further refers to the icon storage unit 121 and extracts an icon associated with the specified type (step S101). Next, the link icon creation unit 104 creates a link icon by associating the extracted icon with the URL (step S102). The created link icon is transmitted to the user terminal 20 via the communication unit 101.

  FIG. 7 is a diagram for explaining a process of creating a link icon. As shown in the upper part of FIG. 7, when a URL link is input by the user in the comment registration field 203 of the schedule registration screen 200 and the link icon creation button 204 is selected, a link icon is created by the above processing. As shown in the lower part of FIG. 7, link icons 210, 211, and 212 indicating URL links are displayed in the comment registration field 203 instead of URL links. Thereby, the user can confirm that the link icon has been created. Moreover, the link icon displayed as a schedule can be confirmed.

  FIG. 8A is a diagram illustrating an example of attaching the DB link icon 213 to the comment registration field 203. FIG. 8B is a diagram illustrating an example of attachment of the link icon 214 of the list screen data. FIG. 8C is a diagram illustrating an example of attachment of the document link icon 215. As described above, when the link icon creation button 204 is selected, a link icon corresponding to the type of related data is created in the schedule management apparatus 10, and the created link icon is transmitted to the user terminal 20. Then, a link icon is displayed in the comment registration field 203 of the schedule registration screen 200 in place of the URL link.

  Returning to FIG. 5, after the link icon is created, when the user selects the execution button 206 on the schedule registration screen 200, the communication unit 101 of the schedule management apparatus 10 is registered in the schedule registration screen 200 from the user terminal 20. The received event information is received (step S103). Then, the event information registration unit 102 registers the received event information in the event information storage unit 120 (step S104).

  Subsequently, the notification mail creating unit 106 checks whether or not a link icon exists in the registered event information. When the link icon exists (step S105, Yes), the notification mail creating unit 106 attaches the link icon to the comment field of the notification mail including the event information (step S106), and creates the notification mail (step S107). ).

  On the other hand, when the link icon does not exist in step S105 (No in step S105), the notification mail creating unit 106 creates a notification mail that does not include the link icon (step S107). Next, the communication unit 101 transmits a notification mail with the target person included in the event information as a transmission destination (step S108). Thus, the schedule registration process in the schedule management system 1 is completed.

  FIG. 9 is a diagram illustrating an example of the notification mail. Thus, the notification mail 300 includes event information registered by the user. When related data exists, link icons 301, 302, and 303 associated with the URL link of the related data are attached.

  As described above, in the schedule management system 1 according to the present embodiment, when there is related data related to the schedule, by uploading the related data to the related data storage unit 122 of the schedule management device 10, The schedule management apparatus 10 can collectively manage related data. Further, by accessing the related data storage unit 122, the related data can be shared among the target persons.

  Further, in the notification mail, the storage location of the related data is changed to the character string of the URL link and displayed as an icon. Thereby, the viewer of notification mail can grasp | ascertain the presence and kind of related data easily.

  Furthermore, in the schedule management system 1, event notification information (schedule) can be appropriately transmitted to the user terminal 20 in response to a request from the user terminal 20. FIG. 10 is a flowchart showing a schedule providing process in the schedule management system 1. For example, the user operates the user terminal 20, receives schedule display information including its own event from the schedule management device 10, and causes the display unit 21 to display the schedule display information. When the user selects a desired event from the schedule display information, the communication unit 101 of the schedule management device 10 receives a request for providing event notification information related to the selected event from the user terminal 20 (step S200). Next, the event notification information creation unit 105 extracts the event information indicated in the provision request from the event information storage unit 120, and creates event notification information attached with a corresponding link icon when related data exists. (Step S201). Next, the communication unit 101 transmits event notification information (step S202).

  At this time, the event notification information transmitted from the schedule management device 10 is displayed on the display unit 21 of the user terminal 20. When the link icon included in the event notification information is selected by the user, a related data provision request is transmitted from the user terminal 20 to the schedule management apparatus 10.

  Further, when the user terminal 20 selects a link icon in the event notification information displayed on the display unit 21 by the user, a request for providing related data including a URL link of the related data is scheduled from the user terminal 20. Transmitted to the device 10.

  When the communication unit 101 of the schedule management apparatus 10 receives the related data provision request (Yes in step S203), the related data extraction unit 108 refers to the event information storage unit 120, and includes the user identification information included in the provision request. Based on the above, it is confirmed whether or not the user of the user terminal 20 is a browsing user of related data related to the provision request. If the user is a browsing user (step S204, Yes), the related data extraction unit 108 extracts related data (step S205), and transmits the related data to the user terminal 20 via the communication unit 101 (step S206). .

  At this time, related data is displayed on the display unit 21 of the user terminal 20. When the user of the user terminal 2 wishes to edit the related data, a request for editing the related data is transmitted to the schedule management apparatus 10 according to the operation of the user terminal 20 by the user. Note that the edit request transmitted at this time includes user identification information of the user of the user terminal 20.

  When the communication unit 101 of the schedule management apparatus 10 receives a request for editing related data (step S207, Yes), the related data editing unit 109 refers to the event information storage unit 120, and includes user identification information included in the edit request. Based on the above, it is confirmed whether or not the user of the user terminal 20 is an editing user of related data. If the user is an editing user (step S208, Yes), the related data editing unit 109 edits the related data in accordance with the related data editing request, and transmits the editing result to the user terminal 20 (step S209). This completes the schedule providing process.

  In step S203, if a related data provision request is not received (step S203, No), in step S204, if the transmission source is not a viewing user (step S204, No), a request for editing related data is issued in step S207. If not received (No at Step S207), if the transmission source is not the editing user at Step S208 (No at Step S208), the process ends.

  Note that FIG. 10 illustrates the case where the link icon included in the event notification information is selected, but step S203 in FIG. 10 is also performed when the link icon included in the notification mail described in FIG. 5 is selected. The process of step S209 is executed.

  As described above, in the schedule management system 1 according to the present embodiment, the storage location of the related data is associated with the icon indicating the type of the related data, and the link icon is created. And since the link icon is created in the user terminal 20 instead of the character string of the storage location, the user can easily determine the character string input as a comment and the storage location. Furthermore, when a link icon displayed on the display unit 21 of the user terminal 20 is selected, a URL link corresponding to the link icon is accessed. Then, the related data corresponding to the link icon is transmitted from the schedule management device 10 to the user terminal 20 and displayed on the display unit 21. As described above, when the user wants to view the related data, the user can display the related data on the display unit 21 only by performing a simple operation of selecting the link icon. As described above, in the schedule management system 1 according to the present embodiment, related data can be shared among the target persons with a simple operation.

  Furthermore, when editing the related data, it is only necessary to edit the related data uploaded to the related data storage unit 122, so that the related data after the editing can be shared among the target persons immediately after the editing. In addition, since the authority for browsing and editing related data is limited for each user, the safety of the related data can be ensured.

  The schedule management apparatus 10 according to the present embodiment includes a control device such as a CPU, a storage device such as a ROM (Read Only Memory) and a RAM, an external storage device such as an HDD and a CD drive device, and a display device such as a display device. And an input device such as a keyboard and a mouse, and has a hardware configuration using a normal computer.

  The program executed by the schedule management apparatus 10 of the present embodiment is a file in an installable format or an executable format, such as a CD-ROM, a flexible disk (FD), a CD-R, a DVD (Digital Versatile Disk), or the like. The program is provided by being recorded on a computer-readable recording medium.

  The program executed by the schedule management apparatus 10 according to the present embodiment may be configured to be stored by being stored on a computer connected to a network such as the Internet and downloaded via the network. Further, the program executed by the schedule management apparatus 10 of the present embodiment may be configured to be provided or distributed via a network such as the Internet. Further, the program of the present embodiment may be configured to be provided by being incorporated in advance in a ROM or the like.

  The program executed by the schedule management apparatus 10 according to the present embodiment includes the above-described units (communication unit, event information registration unit, icon extraction unit, link icon creation unit, event notification information creation unit, notification mail creation unit, and related data). The module configuration includes a registration unit, a related data extraction unit, and a related data editing unit). As actual hardware, the CPU (processor) reads out and executes a program from the storage medium, and the respective units are main memory. It is loaded on the device, and each unit is generated on the main storage device.

DESCRIPTION OF SYMBOLS 1 Schedule management system 10 Schedule management apparatus 20 User terminal 21 Display part 100 Schedule processing part 101 Communication part 102 Event information registration part 103 Icon extraction part 104 Link icon creation part 105 Event notification information creation part 106 Notification mail creation part 107 Related data registration Unit 108 related data extraction unit 109 related data editing unit 120 event information storage unit 121 icon storage unit 122 related data storage unit

Japanese Patent No. 4166101

Claims (6)

An event information receiving unit for receiving an event, a type of related data related to the event, and a storage location where the related data is stored;
A related data storage unit for storing the related data in the storage location;
An icon storage unit that stores a type of the related data and an icon indicating the related data in association with each other;
In the icon storage unit, an icon extraction unit that extracts the icon associated with the type received by the event information reception unit;
A link icon creation unit that creates a link icon that associates the icon extracted by the icon extraction unit with the storage location of the related data;
An event notification information transmitting unit for transmitting event notification information including the link icon and the event to a user terminal;
A provision request receiving unit configured to receive a provision request for the related data stored in the storage location associated with the link icon from the user terminal when the link icon is selected in the user terminal;
A related data extraction unit that extracts the related data from the storage location of the related data storage unit indicated in the provision request;
A schedule management apparatus comprising: a related data transmission unit that transmits the related data extracted by the related data extraction unit to the user terminal. The event information receiving unit receives participating user information indicating participating users participating in the event together with the event,
The schedule according to claim 1, wherein the event notification information transmitting unit transmits the event notification information as an email to the user terminal of the participating user indicated by the participating user information received together with the event. Management device. The event information receiving unit receives browsing user information indicating a browsing user who can browse the related data together with the event,
The provision request receiving unit receives user identification information for identifying a user who uses the user terminal together with the provision request,
The related data transmitting unit determines, based on the user identification information, whether or not a user of the user terminal that is the transmission source of the provision request is the browsing user indicated in the browsing user information, and the user terminal The schedule management apparatus according to claim 1, wherein when the user is the browsing user, the related data is transmitted to the user terminal. An editing instruction receiving unit for receiving an instruction to edit the related data from the user terminal;
The schedule management according to claim 1, further comprising a related data editing unit that edits the related data stored in the related data storage unit in accordance with the editing instruction. apparatus. A schedule management method executed by a schedule management device,
The schedule management device includes:
A related data storage unit for storing related data related to the event;
An icon storage unit that associates and stores the type of the related data and an icon indicating the related data;
An event information receiving step for receiving the event, a type of related data related to the event, and a storage location of the related data storage unit in which the related data is stored;
In the icon storage unit, an icon extraction step of extracting the icon associated with the type received in the event information reception step;
A link icon creating step for creating a link icon that associates the icon extracted in the icon extracting step with the storage location of the related data;
Event notification information transmitting step for transmitting event notification information including the link icon and the event to a user terminal;
A provision request receiving step of receiving a request for provision of the related data stored in the storage location associated with the link icon from the user terminal when the link icon is selected in the user terminal;
In the related data storage unit, a related data extraction step of extracting the related data from the storage location indicated in the provision request;
And a related data transmitting step of transmitting the related data extracted in the related data extracting step to the user terminal. A related data storage unit for storing event related data;
A computer comprising an icon storage unit that associates and stores a type of the related data and an icon indicating the related data.
An event information receiving unit that receives the event, a type of related data related to the event, and a storage location of the related data storage unit in which the related data is stored;
In the icon storage unit, an icon extraction unit that extracts the icon associated with the type received by the event information reception unit;
A link icon creation unit that creates a link icon that associates the icon extracted by the icon extraction unit with the storage location of the related data;
An event notification information transmitting unit for transmitting event notification information including the link icon and the event to a user terminal;
A provision request receiving unit configured to receive a provision request for the related data stored in the storage location associated with the link icon from the user terminal when the link icon is selected in the user terminal;
In the related data storage unit, a related data extraction unit that extracts the related data from the storage location indicated in the provision request;
The program for functioning as a related data transmission part which transmits the said related data extracted by the said related data extraction part to the said user terminal.

Images