JP2011197783A - Information processing device, information processing method, and information processing program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To associate a conference with a resource only by transmitting electronic mail as usual.SOLUTION: The information processing device includes: a mail event detection part for detecting an event relating to transmission/reception of electronic mail; a resource acquisition part for acquiring a resource relating to the electronic mail or resource information including information for accessing the resource; a relevant user acquisition part for acquiring the user information of a plurality of users relating to the electronic mail; a common schedule extraction part for extracting a common schedule of the plurality of users by referring to schedule information in which the users of the electronic mail are associated with the schedules of the users, based on the user information of a plurality of users acquired by the relevant user acquisition part; and a resource management part for storing the resource information acquired by the resource acquisition part and the common schedule extracted by the common schedule extraction part in association with each other in the resource storage part.

Description

  The present invention relates to information processing technology using electronic mail.

  In recent years, paper materials have not been distributed, and materials have been electronically distributed in advance using e-mail and file servers, and the style that participants can refer to on their laptops in conference rooms has become established. However, the user usually needs to attend various meetings, and it is difficult to immediately find documents related to each meeting in the meeting room.

  In particular, since portable terminals such as notebook computers have a small screen and are not highly operable, it is troublesome to find a necessary file. In addition, there is a possibility that the conference materials will be updated until just before, and it is difficult to organize and prepare the latest versions of all the materials distributed before the conference starts.

  As a technology for solving the above problems, when receiving an e-mail, the content of the e-mail is analyzed to determine whether it is a meeting opening notice. Is extracted, and access control including date and time and participants is set for a shared resource such as a file server corresponding to the location (see, for example, Patent Document 1).

JP 2006-53824 A

  However, the technique of Patent Literature 1 only sets access control to a shared resource related to a conference, and the problem is that the user accesses the shared resource in a conference room and searches for a file. Has not solved anything. Also, if the user himself / herself determines which conference the user is involved in and the material cannot be copied to the shared folder, it is impossible to associate the conference material with the conference. Troublesomeness occurs.

  Therefore, in the present invention, a common meeting is extracted from the schedule information of the user to whom the e-mail is sent and received, and resources related to the date and place of the meeting are managed in association with each other. It is an object to make it possible to associate a conference with a resource.

  In order to achieve the above object, an information processing apparatus disclosed below includes a mail event detection unit that detects an event related to transmission / reception of an e-mail and a resource related to e-mail or information for accessing a resource Based on the user information of the plurality of users acquired by the resource acquisition unit that acquires resource information, the user information acquisition unit that acquires user information of a plurality of users related to the email, and the user information acquisition unit, With reference to the schedule information that associates the user with the user's schedule, the common schedule extraction unit that extracts the common schedule of the plurality of users, the resource information acquired by the resource acquisition unit, and the common schedule extraction unit extracted Resources that are stored in the resource storage unit in association with a common schedule And a processing section.

  According to said structure, a meeting and a resource can be matched only by exchange of a normal electronic mail.

Schematic which shows the structure of the information processing system which concerns on embodiment of this invention The block diagram which shows an example of a structure of the information processing system which concerns on Embodiment 1 of this invention. The figure which shows an example of a user information table The figure which shows an example of a schedule information table The figure which shows an example of operation | movement of the information processing system which concerns on Embodiment 1 of this invention. The figure which shows an example of a resource management table The figure which shows an example of operation | movement of the information processing system which concerns on Embodiment 1 of this invention. The figure which shows an example of a place correlation table Figure showing an example of the related resource list screen The figure which shows an example of operation | movement of the information processing system which concerns on Embodiment 1 of this invention. A figure showing an example of mail header information The figure which shows an example of a resource management table The figure which shows an example of operation | movement of the information processing system which concerns on Embodiment 1 of this invention. Figure showing an example of the related resource list screen The block diagram which shows an example of a structure of the information processing system which concerns on Embodiment 2 of this invention. The figure which shows an example of a resource management table The figure which shows an example of operation | movement of the information processing system which concerns on Embodiment 2 of this invention. The figure which shows an example of a resource management table The figure which shows an example of operation | movement of the information processing system which concerns on Embodiment 2 of this invention. The block diagram which shows an example of a structure of the information processing system which concerns on Embodiment 3 of this invention. The flowchart which shows an example of operation | movement of the information processing system which concerns on Embodiment 3 of this invention. The figure which shows an example of a reevaluation event management table The block diagram which shows an example of a structure of the information processing system which concerns on Embodiment 4 of this invention. The flowchart which shows an example of operation | movement of the information processing system which concerns on Embodiment 4 of this invention. The figure which shows an example of a resource management table Figure showing an example of the related resource list screen The flowchart which shows an example of operation | movement of the information processing system which concerns on Embodiment 4 of this invention. The figure which shows an example of a meeting history table The figure which shows an example of a resource management table Figure showing an example of the related resource list screen The flowchart which shows an example of operation | movement of the information processing system which concerns on Embodiment 4 of this invention. The block diagram which shows an example of a structure of the information processing system which concerns on Embodiment 5 of this invention. The flowchart which shows an example of operation | movement of the information processing system which concerns on Embodiment 5 of this invention. The flowchart which shows an example of operation | movement of the information processing system which concerns on Embodiment 5 of this invention. The block diagram which shows an example of a structure of the information processing system which concerns on Embodiment 6 of this invention. Figure showing an example of the related resource list screen The block diagram which shows an example of a structure of the information processing system which concerns on Embodiment 7 of this invention. The flowchart which shows an example of operation | movement of the information processing system which concerns on Embodiment 7 of this invention.

[Embodiment 1]
Next, embodiments of the present invention will be described in detail with reference to the drawings.

  FIG. 1 is a schematic diagram showing the overall configuration of a system including an information processing apparatus according to an embodiment of the present invention. In FIG. 1, a notebook PC 110 owned by a user is connected to a mail server 130, a directory server 140, and a schedule server 150 via a network 120. In addition, the conference rooms A to X each show a system configuration in which wireless LAN access points A to X for a user to access each server and other Web servers via the network 120 are set. In the present embodiment, a case where the notebook PC 110 functions as an information processing apparatus will be described. Note that the information processing apparatus of the present invention is not limited to being configured by a single computer, and may be configured by a plurality of computers.

  The notebook PC 110 operates as a mail client by a mail program for implementing this embodiment. Detailed operations by the mail program will be described later. In the present embodiment, it is assumed that the user uses the notebook PC 110, but the terminal that operates as a mail client is not limited to this. For example, a small mobile terminal such as a mobile phone or a smartphone may be used.

  In the present embodiment, the network 120 is assumed to be an in-house network, but it may be a normal Internet or other networks. In this case, however, the mail client is allowed to access the mail server 130, the directory server 140, the schedule server 150, etc. via the network 120.

  The mail server 130 is operated by a mail delivery program. The mail server 130 accumulates e-mails when receiving e-mails, and returns information related to the user's e-mails in response to requests from the users. Further, the mail server 130 requests delivery of electronic mail to other mail delivery programs in response to a request from the user. In this embodiment, an existing program can be used as the mail delivery program.

  The directory server 140 is operated by a user information management program. As shown in FIG. 3, for example, the directory server 140 manages user information of a user ID, name, telephone number, affiliation, mail address, and scheduler ID in a user information table 300, and responds to a request from the user. In response, the user information is returned. In the present embodiment, an existing program can be used as the user information management program.

  The schedule server 150 is operated by a schedule management program. As shown in FIG. 4, for example, the schedule server 150 manages the schedule information of the user with the schedule ID, date, time, place, and content in the schedule table 400, and according to the request from the user, Return schedule information. Also, in response to a request from the user, a new schedule is registered or the contents of an existing schedule are updated. In the present embodiment, an existing program can be used as the schedule management program.

  In this embodiment, it is assumed that the mail server 130, the directory server 140, and the schedule server 150 are installed in the company, but may be installed outside the company as long as they can be accessed from the mail client.

The wireless LAN access points A to X are used to connect to the network 120 described above when the user moves with the notebook PC 110 to the conference room. In addition, a unique ID (BSSID) is assigned to each of the wireless LAN access points A to X, and the conference room information is associated with this value and managed, so which conference room the user is in. Can be determined. The above-mentioned mail program is implemented for the conference room determination function and the association information.
[Embodiment 1]
FIG. 2 is a block diagram illustrating an example of the configuration of the information processing apparatus according to the first embodiment of the present invention. In FIG. 2, the information processing apparatus realized by the notebook PC 110 includes a mail event detection unit 201, a resource acquisition unit 202, a related user acquisition unit 203, a common schedule extraction unit 204, a resource management unit 205, a location detection unit 206, and a presentation A unit 207 is provided. In the present embodiment, the notebook PC 110 is obtained by further adding these functions to a normal mail function. Note that the functions of these information processing apparatuses included in the notebook PC 110 may be distributed and provided in at least one external computer. Each function of the information processing apparatus is provided in the notebook PC 110 that operates as a mail client, but may be provided in the mail server 130 or another server.

  The mail event detection unit 201 detects at least an event related to an e-mail when an e-mail is transmitted, when an e-mail is received, or when a file attached to the e-mail is saved. The mail event detection unit 201 may detect mail transmission / reception and attached file saving processing in the mail client as events, or mail transmission / reception in the mail server 130 as events.

  The resource acquisition unit 202 acquires resource information related to electronic mail. A resource related to e-mail is, for example, a set of data that both the sender and receiver of an e-mail may need to access later. For example, data used by a user associated with an email in a later meeting can be identified as a resource. For example, the body of an e-mail, an attached file, a shared file recorded on a server accessible to both users, and the like can be resources. The resource information includes at least one of the resource itself and information for accessing the resource. The resource acquisition unit 202 acquires resource information from information included in an e-mail or an attached file. Details of the resource information acquisition method will be described later. The resource acquisition unit 202 can acquire at least one of e-mail, a file attached to the e-mail, and resource location information described in the e-mail text as resource information. The resource acquisition unit 202 can execute the resource information acquisition process only when it is determined that there is a resource related to the electronic mail.

  The related user acquisition unit 203 acquires user information of a sender / receiver of an email. For example, the related user acquisition unit 203 refers to the header information of the email, and performs the transmission source user (refer to the From header), the transmission destination user (refer to the To header), and the copy transmission destination user (refer to the Cc header). The user information of the sender / receiver can be acquired.

  The common schedule extraction unit 204 extracts a common schedule for each user based on the user information of the sender / receiver of the email acquired by the related user acquisition unit 203. Based on the acquired user information of the sender and receiver, the common schedule extraction unit 204 searches for schedule information that shares the time and place of the schedule of all users, and extracts a common event. The schedule information has been described with the configuration recorded in the schedule server 150. However, the schedule information may be provided in the information processing apparatus itself.

  The resource management unit 205 associates the resource information acquired by the resource acquisition unit 202 and the common event extracted by the common schedule extraction unit 204 and stores them in the resource storage unit.

  The location detection unit 206 detects a location where the user is present. For example, it is possible to detect the conference room in which the user is located, for example, based on information from a wireless LAN access point, and to detect the location of the user. In this embodiment, the position of the user is determined by the wireless LAN access points A to X. However, an entrance management system using an IC card or other position positioning systems may be used.

  The presentation unit 207 generates a list of resource information when the location detected by the location detection unit 206 matches the location where the common schedule extracted by the common schedule extraction unit 204 is executed, and the generated resource information Present the list to the user. The presentation unit 207 is not limited to presenting based on the location where the user is currently located. For example, a common schedule, time, place, sender / receiver instructions, etc. may be received from the user and presented based on the instructions.

  Hereinafter, the operation of the information processing system 100 according to the first embodiment of the present invention when an e-mail is received will be described with reference to the flowchart of FIG.

  The mail event detection unit 201 waits for an event when the mail program is activated. In the event waiting state, the mail event detection unit 201 accesses the mail server 120 at regular intervals, acquires the mail information when there is a new mail, and notifies the user that there is a new mail. (Steps S501 → S502).

  When a new mail is received, the mail event detection unit 201 confirms whether or not a file is attached to the email (step S503). This can be done by referring to the header information of the email.

  Alternatively, the mail event detection unit 201 can detect an event at the time of mail transmission on the mail client side. In order to attach a file to an e-mail in a mail client, the user needs to drag and drop the file to be attached to the e-mail or select a file to be attached from a dialog box. Therefore, the mail event detection unit 201 can easily check whether a file is attached to the e-mail.

  Next, the resource acquisition unit 202 refers to the text of the e-mail and confirms whether information on the resource such as directory information and URL of the shared server is described. Since the directory and URL have a specific pattern, this can be executed by simple pattern matching of character strings. At this point, if no file is attached to the e-mail and no information about the resource is described, it is determined that there is no resource, and the processing described later is not executed.

  The resource acquisition unit 202 determines that there is a resource when a file is attached to the e-mail or information about the resource is described, and the e-mail described in the header information of the e-mail is uniquely identified. A message ID for identification is acquired (step S504).

  Further, the related user acquisition unit 203 refers to the header information of the email, and sends the emails of the transmission source user (refer to the From header), the transmission destination user (refer to the To header), and the copy transmission destination user (refer to the Cc header). An address is acquired (step S505).

  The related user acquisition unit 203 acquires the user ID of the user who owns each mail address from the directory server 140 (step S506). The user ID is used to search the schedule server 150 for user schedule information. When the schedule server 150 manages the user's schedule by e-mail address (see, for example, FIG. 3), the user ID acquisition process using the “directory server” is not necessary.

  Next, the common schedule extraction unit 204 acquires the schedule information of the transmission source user, the transmission destination user, and the copy transmission destination user acquired by the above-described processing from the schedule server 150 (step S507).

  Next, the common schedule extraction unit 204 searches for schedule information having a common time and place from the acquired schedule information of all users (step S508). For example, if the time information of the schedule information and the location information are the same, the time information is the same, but if the location information is different, there is a time zone that is not common and the time information is common, If the information matches, it can be determined that the information is common. Other common determination methods will be described later.

  Next, the common schedule extraction unit 204 determines whether there is a common schedule (step S509). If common schedule information is found in step S509, the resource management unit 205 updates the resource management table 600 shown in FIG. 6, for example, with the schedule as a common conference (step S510). On the other hand, if no common schedule is found in step S509, the resource management unit 205 returns the process to step S501.

  The resource management table 600 in FIG. 6 will be described. The “date and time” field is a field for storing date and time information of the conference. The “location” field is a field for storing conference location information. The “resource” field is a field for storing resource information related to the e-mail in which the meeting is found. The prefix “m” indicates that the value after the “-” delimiter is the message ID of the e-mail, and “s”. Indicates a shared server directory, and “l” indicates a locally stored directory. The “sender”, “receiver”, and “copy recipient” fields are fields for storing sender information, recipient information, and copy recipient information of an e-mail, respectively. The “usage flag” is a flag indicating whether or not the associated resource is used in the conference. In the example illustrated in FIG. 6, nothing is described because it is before the conference time. In this way, the resource management table 600 of FIG. 6 can be created from the information obtained by the processing so far.

  In addition, the mail event detection unit 201 detects an operation of saving the file attached to the received mail on the local hard disk (step S511). When the storing operation is performed in step S511, the mail event detection unit 201 searches the “resource” field using the message ID of the mail as a key (step S512).

  Next, the resource management unit 205 adds the file storage location and file name to the found “resource” field (step S513). At this time, the message ID of the original electronic mail associated with the resource may be deleted from the “resource” field.

  Next, processing when the user moves to the conference room will be described with reference to the flowchart of FIG.

  When the user moves to the conference room, the user's notebook PC 110 is connected to the wireless LAN access point installed in the conference room, and the location detection unit 206 acquires the BSSID of the wireless LAN access point (steps S701 → S702).

When the BSSID is acquired, the location detection unit 206 acquires location information indicated by the BSSID using, for example, the location association table 800 illustrated in FIG. 8 (step S703). The location linking table 800 of FIG. 8 that can determine where the user is now will be described. The “BSSID” field is a field for storing the BSSID of the wireless LAN access point. The “location” field is a field for storing location information corresponding to the BSSID. In the present embodiment, it is assumed that the location association table 800 is held by the mail client. However, the location association table can be stored in the server and the BSSID can be used as a key to obtain location information. It may be configured.

  Next, when the location detection unit 206 determines the location by connecting to the wireless LAN access point of the conference room, the location detection unit 206 determines whether the location has moved from the previous location (step S704). In step S704, when it is not moving, the location detection unit 206 returns the process to step S701. On the other hand, when it is moving, the location detection unit 206 acquires the current time (step S705).

  Next, the presentation unit 207 searches for the corresponding conference from the resource management table 600 using the time information and the location information as keys (step S706).

  Next, the presentation unit 207 determines whether there is a corresponding meeting in the resource management table 600 (step S707). In step S707, when there is no corresponding meeting in the resource management table 600, the presentation unit 207 returns the process to step S701. On the other hand, if there is a corresponding meeting in step S707, the presenting unit 207 acquires the corresponding resource information from the resource management table 600, and lists related resources on the related resource list screen 900 shown in FIG. Is displayed (step S708). The time information used when searching the resource management table 600 may be searched after adding a predetermined margin (for example, 10 minutes) before and after.

  The related resource list screen 900 of FIG. 9 will be described. The resource list displays the resource information acquired from the resource management table 600 for each resource type. In this embodiment, only the message ID is displayed for the mail, but the sender and the mail title may be acquired using the message ID as a key, and these may be displayed in the list. The “Open” button can be clicked only when a resource in the “Resource” list is selected. When the button is clicked, the selected resource is opened. When the “Close” button is clicked, the related resource list screen 900 is closed.

  When the number of related resources associated with the conference is a predetermined number (for example, 1 or less), instead of displaying the related resource list screen 900, a file or a related mail may be opened directly.

(Threaded)
Hereinafter, the case where an email is threaded will be described with reference to the flowchart of FIG. Threading means grouping emails. Related emails can be grouped based on information indicating other related emails included in the email.

  For example, by grouping electronic mails, it is possible to group files attached to the mail and location information of the files attached to the mail. The resource management unit 205 can store resource information in the resource storage unit for each thread in which emails are grouped.

  The mail event detection unit 201 receives mail (steps S1001 to S1002). The mail event detection unit 201 determines whether a resource is included in the received mail (step S1003). If it is determined in step S1003 that it is not included, the mail event detection unit 201 returns the process to step S1001. On the other hand, when it is determined in step S1003 that it is included, the mail event detection unit 201 determines whether or not the References header is included in the header information of the received mail (step S1004).

  If it is determined in step S1004 that the resource is not included, the resource management unit 205 associates the conference with the resource as usual (steps S1004 → S1007). On the other hand, if it is determined that it is included, the mail event detection unit 201 searches for a thread including the References header of the received mail.

  Then, the mail event detection unit 201 determines that the received mail is related to the email with the message ID described in the References header of the received mail, and uses the header information to determine the email message. Thread. The header information of the mail includes, for example, a transmission source user (From header), a transmission destination user (To header), a copy transmission destination user (Cc header), and a message ID shown in FIG.

  Specifically, it is assumed that the user A first transmits a mail attached with the conference material, and the message ID in this case is “userA: 00000”. Next, the user B transmits an email with another conference material attached to the email of the user A. In this case, the message ID is different from the message ID of the user A, for example, “userB: 00000”, but the References header includes the message ID “userA: 00000” of the first mail of the user A.

  Further, when the user C sends an email with another conference material attached to the email of the user B, a unique “userC: 00000” is assigned to the message ID, but the user A and the user B are assigned to the References header. Message IDs “userA: 00000” and “userB: 00000” are included. Therefore, by storing the message ID of the first electronic mail that does not have the References header, it is possible to thread other reply mail and resources related to the mail.

  Next, the resource management unit 205 adds resource information to the “resource” field of the corresponding thread (step S1006).

  Further, the mail event detection unit 201 determines whether or not an operation for saving the file attached to the received mail to the local hard disk has been performed (steps S1001 to S1008). When the storing operation is performed in step S1008, the mail event detection unit 201 searches the “resource” field using the message ID of the mail as a key (step S1009).

  Next, the resource management unit 205 adds the file storage location and file name to the found “resource” field (step S1010).

  FIG. 12 shows an example of a resource management table 1200 for managing threaded resources. The “thread” field is a field for storing ID information for identifying a thread, and in this example, stores a message ID of an e-mail having no References header.

  The “resource” field is a field for storing resource information belonging to the thread identified by the “thread” field. The other fields are the same as those in the resource management table 600 of FIG.

  In the case of the resource management table 1200 shown in FIG. 12, an email having a message ID “userB: 123456” and a resource “\ shared \ material.doc” are allocated to the thread “userB: 123456”, and the thread “userA: An electronic mail having message IDs of “userA: 98765” and “userB: 11111” is assigned to 98765 ”.

  Next, processing when the user moves to the conference room will be described with reference to the flowchart of FIG.

  When the user moves to the conference room, the user's notebook PC 110 connects to the wireless LAN access point installed in the conference room, and the location detection unit 206 acquires the BSSID of the wireless LAN access point (steps S1301 → S1302).

  When the BSSID is acquired, the location detection unit 206 acquires location information indicated by the BSSID using, for example, the location association table 800 shown in FIG. 8 (step S1303). This makes it possible to determine where the user is currently.

  The place linking table 800 in FIG. 8 will be described. The “BSSID” field is a field for storing the BSSID of the wireless LAN access point. The “location” field is a field for storing location information corresponding to the BSSID. In this embodiment, it is assumed that the location association table 800 is held by the mail program. However, the location association table can be held in the server and the BSSID can be used as a key to obtain location information. It may be configured.

  Next, when the location detection unit 206 determines the location by connecting to the wireless LAN access point in the conference room, the location detection unit 206 determines whether the location has moved from the previous location (step S1304). In step S1304, when it is not moving, the location detection unit 206 returns the process to step S701. On the other hand, if it is moving in step S1304, the location detection unit 206 acquires the current time (step S1305).

  Next, the presentation unit 207 searches for the corresponding conference from the resource management table 600 using the time information and the location information as keys (step S1306).

  Next, the presentation unit 207 determines whether there is a corresponding meeting (step S1307). If there is no corresponding conference in step S1307, the presentation unit 207 returns the process to step S1301. On the other hand, if there is a corresponding meeting in step S1307, the presentation unit 207 acquires a resource for each corresponding thread, and displays a list of related resources, for example, on the related resource list screen 1400 shown in FIG. (Step S1308).

In FIG. 14, the message ID of the mail that is the origin of the thread is displayed as the thread name. The sender name and the mail title are acquired using the message ID as a key, and the thread name is generated from the information. , May be displayed in the “resource” list. By threading resources in this way, resources having a certain relationship can be listed together, so that the convenience of user resource reference can be improved.
[Embodiment 2]
FIG. 15 is a block diagram illustrating an example of the configuration of the information processing apparatus according to the second embodiment of the present invention. In FIG. 15, the information processing apparatus further includes a resource usage monitoring unit 208 with respect to the configuration of the first embodiment. In addition, the same code | symbol is attached | subjected about the structure similar to Embodiment 1. FIG.

  The information processing apparatus further includes a resource usage monitoring unit 208 that monitors the usage status of resources stored in the resource storage unit by the resource management unit 205. The resource management unit 205 can update the information of the corresponding resource when the resource usage monitoring unit 208 detects the use of the resource.

  For example, the resource usage monitoring unit 208 detects that the resource managed by the resource management unit 205 has been opened. The resource management unit 205 deletes the association between the resource and the conference other than the conference in which the resource is detected to be opened.

  The resource management unit 205 associates resources with all the extracted conferences (a plurality of conferences) when associating the conferences with the resources, and then, at the time and place corresponding to the conferences, the resource usage monitoring unit 208 Whether or not the resource is opened is monitored from the related resource list screen, and when opened, the resource management unit 205 deletes the association between the resource and another conference.

  As a result, the material once used in the conference is not treated as a related resource in the next and subsequent conferences where the same user participates, and the convenience of the user's resource selection can be improved.

  FIG. 16 shows an example of the resource management table 1600 after the resource is opened from the related resource list screen. In the resource management table 1600 of FIG. 16, the mail resource is used among the resources associated with the meeting of the date “9/30 10: 00-12: 00” and the place “5A meeting room”. Since “used” is set in the entry and the file resource “material.doc” on the shared server is also used, the “usage flag” entry “used” is set.

  Hereinafter, the processing when the user moves from the conference room in the above case will be described with reference to the flowchart of FIG.

  When the user moves to the conference room, the user's notebook PC 110 connects to the wireless LAN access point installed in the conference room, and the location detection unit 206 acquires the BSSID of the wireless LAN access point (steps S1701 → S1702).

  When the BSSID is acquired, the location detection unit 206 acquires location information indicated by the BSSID using, for example, the location association table 800 shown in FIG. 8 (step S1703). This makes it possible to determine where the user is currently.

  Next, when the location detection unit 206 determines the location by connecting to the wireless LAN access point of the conference room, the location detection unit 206 determines whether or not the location has moved from the previous location (step S1704). If it is determined in step S1704 that the user has not moved, the location detection unit 206 returns the process to step S1701. On the other hand, if the resource is moving, the resource usage monitoring unit 208 acquires resources that have been used in the previous meeting (step S1705).

  Next, the resource usage monitoring unit 208 determines whether or not the resource that has been used in the previous conference is associated with another conference (step S1706). In step S1706, if not associated, the resource usage monitoring unit 208 returns the process to step S1701. On the other hand, if it is associated in step S1706, the resource management unit 205 cancels the association (step S1707).

  For example, in the case of FIG. 16, “m-userB: 123456”, “s” among the resources associated with the meeting of the date “9/30 9: 30-12: 00” and the place “5A meeting room”. Since the resource of “− ¥ shared ¥ material.doc” has been used, the association is deleted (steps S1701 to S1707).

  FIG. 18 shows an example of the resource management table 1800 after using resources from the related resource list screen. All the resources “m-userB: 123456” and “s- ¥ shared ¥ material.doc” associated with the meeting of the date “9/30 9: 30-12: 00” and the place “5A meeting room” are used. Since it has already been completed, the data related to the meeting at the date “9/30 9: 30-12: 00” and the place “5A meeting room” has been deleted. In addition, the resources “m-userB: 123456” and “s- ¥ shared ¥ material.doc” associated with the meeting of the date and time “9/30 9: 30-12: 00” and the place “5A meeting room” are used. "Is also associated with the meeting of the date" 10/1 9: 30-110: 00 "and the place" 5B Meeting Room ", the date" 10/1 9: 30-11: 0 ", the place" It has been deleted from the conference resource “5B Conference Room”.

  In addition, when associating a resource with a meeting, the resource is associated with the first extracted meeting (one meeting), and then the resource is opened from the related resource list screen at the time and place corresponding to the meeting. If the conference is not opened, another conference of the resource may be re-extracted, and the found conference and the resource may be associated with each other and managed.

  As a result, it is possible to automatically manage materials that are not used in the conference while associating them with other conferences while suppressing the load of the conference search. Therefore, it is possible to improve the convenience of user resource selection. .

  Hereinafter, processing when the user moves from the conference room in the above case will be described with reference to the flowchart of FIG.

  When the user moves to the conference room, the user's notebook PC 110 connects to the wireless LAN access point installed in the conference room, and the location detection unit 206 acquires the BSSID of the wireless LAN access point (steps S1901 → S1902).

  When the BSSID is acquired, the location detection unit 206 acquires location information indicated by the BSSID using, for example, the location association table 800 illustrated in FIG. 8 (step S1903). This makes it possible to determine where the user is currently.

  Next, when the location detection unit 206 determines the location by connecting to the wireless LAN access point of the conference room, the location detection unit 206 determines whether the location has moved from the previous location (step S1904). In step S1904, if not moving, the location detection unit 206 returns the process to step S1901. On the other hand, when the resource is moving, the resource usage monitoring unit 208 acquires an unused resource in the previous meeting (step S1905).

  Next, the resource usage monitoring unit 208 determines whether an unused resource in the previous conference is associated with another conference (step S1906). In step S1906, if not associated, the resource usage monitoring unit 208 returns the process to step S1901. On the other hand, if it is associated in step S1906, the resource management unit 205 associates the resource with the newly extracted first conference (steps S1906 to S1907).

  For example, in the case of FIG. 18, the resource usage monitoring unit 208 uses the information in the “sender”, “receiver”, and “copy recipient” fields of the resource management table 1800 to determine the first meeting after the current time. If it is extracted and found, an entry for the conference is created, and “m-userA: 98765”, “lc: ¥ meeting 0930.ppt”, and “lc: ¥ material 0930a.txt” are created as resources. Corresponding management is performed (steps 1901 to S1907).

In the present embodiment, whether or not the resource is opened from the related resource list screen is monitored, but an event of the operating system or the like may be monitored to monitor whether or not the resource is opened by other means.
[Embodiment 3]
FIG. 20 is a block diagram illustrating an example of the configuration of the information processing apparatus according to the third embodiment of the present invention. In FIG. 20, the information processing apparatus further includes a schedule information update monitoring unit 209 with respect to the configuration of the first embodiment. In addition, the same code | symbol is attached | subjected about the structure similar to Embodiment 1. FIG. The schedule information update monitoring unit 209 monitors the update of the user's schedule information related to the event.

  In the first embodiment, the common meeting information of the sender, the receiver, and the copy recipient is extracted as a common meeting. However, for example, the following method may be used. Even when the schedule information of all the members is not included, an event in which the time and place of at least two people match is acquired as a common conference candidate, and a score indicating a common degree is calculated for each conference candidate.

  Specifically, every time a user is included, 10 points are added, and in the case of a sender, the weight is doubled, and in the case of a copy receiver, the weight is 0.5 times. The point that is calculated and divided by the total number of senders, recipients, and copy senders is the commonality score. When the commonality score exceeds a predetermined value (for example, 5), Perform resource mapping.

  For example, for a common conference candidate extracted when a mail of the sender userA, the receiver userB, userC, userD, and the duplicate receiver userE, userF is sent, the same time zone is set for the userA, userB, userC, userF If the location schedule is set, the commonality score is (2 × 10 + 10 + 10 + 0.5 × 10) /6=7.5, so it is determined as a common conference. When userB, userC, and userF have the same time zone and place schedule, the commonness score is (10 + 10 + 0.5 × 10) /6=4.2, and thus it is not determined as a common conference.

  Note that the above-described commonness score calculation method is merely an example, and of course, other methods may be used. For example, the score of the copy recipient may not be taken into account, or the commonness score may be calculated with a greater weight of the user with high credibility of the schedule information.

  When the commonness score is within a certain range (for example, between 4 and 5), the common schedule extraction unit 204 considers that there is a user who has not entered the schedule information, and the reevaluation shown in FIG. Information is temporarily saved in the event management table 2200. Each field of the reevaluation event management table 2200 stores information when the commonness score is calculated.

  The information processing apparatus further includes a schedule information update monitoring unit 209 that detects an update of the user's schedule information. When the schedule information update monitoring unit 209 detects the update of the schedule information, the common schedule extraction unit 204 can recalculate the commonness score and extract the common schedule again.

  For example, the schedule information update monitoring unit 209 monitors the update of the user's schedule information related to the event. When there is an update, the common schedule extraction unit 204 acquires the schedule of the corresponding user, recalculates the commonness score again, and extracts a common schedule obtained as a result of the recalculation.

  Hereinafter, a description will be given according to the flowchart of FIG.

  The mail event detection unit 201 accesses the mail server 120 at regular intervals when the mail program is activated, acquires mail information when there is a new mail, and receives a new mail to the user. It is notified (step S2101 → S2102).

  When a new mail is received (Yes in Step 2102), the mail event detection unit 201 confirms whether a file is attached to the electronic mail (Step S2103). This can be done by referring to the header information of the email.

  Next, the resource acquisition unit 202 refers to the text of the e-mail and confirms whether information on the resource such as directory information and URL of the shared server is described. Since the directory and URL have a specific pattern, this can be executed by simple pattern matching of character strings. At this point, if no file is attached to the e-mail and no information about the resource is described, the processing described later is not executed.

  The resource acquisition unit 202, when a file is attached to an e-mail or information about a resource is described, a message ID for uniquely identifying the e-mail described in the header information of the e-mail Is acquired (step S2104).

  Further, the related user acquisition unit 203 refers to the header information of the email, and sends the emails of the transmission source user (refer to the From header), the transmission destination user (refer to the To header), and the copy transmission destination user (refer to the Cc header). An address is acquired (step S2105).

  The related user acquisition unit 203 acquires a user ID for searching the schedule server 150 for the schedule information of the user who owns each mail address from the directory server 140 (step S2106). When the schedule server 150 manages the user's schedule by e-mail address, this user ID acquisition process using the “directory server” is unnecessary.

  Next, the common schedule extraction unit 204 acquires the schedule information of the transmission source user, transmission destination user, and copy transmission destination user acquired from the schedule server 150 by the above-described processing (step S2107).

  Next, the common schedule extraction unit 204 extracts common conference candidates, calculates their commonness score, and temporarily saves them in the reevaluation event management table 2200 (step S2108).

  Next, the common degree event extraction unit 204 determines whether or not the calculated common degree score has cleared a predetermined value (step S2109).

  If the default value is cleared in step S2109, the resource management unit 205 determines that the common conference candidate is a common conference, acquires necessary information from the field of the reevaluation event management table 2200, and manages the resource. The table is updated (step S2110). Thereafter, the resource management unit 207 deletes information regarding the common conference candidate registered in the resource management table from the reevaluation event management table 2200.

  On the other hand, if the predetermined value is not cleared in step S2109, the common schedule extraction unit 204 determines whether or not the calculated commonality score is within the predetermined range (step S2111). In step S2111, if it is not within the predetermined range, the common schedule extraction unit 204 returns the process to step S2101. On the other hand, when it is within the predetermined range, the schedule information update monitoring unit 209 acquires the schedule of the corresponding date and time of “sender”, “receiver”, and “copy recipient” in the reevaluation event management table 2200, When there is an update, the common schedule extraction unit 204 calculates the commonness score again, and updates information related to the common conference candidate in the reevaluation event management table 2200 (step 2112).

  Next, the schedule information update monitoring unit 209 monitors the update of the user schedule information related to the common conference candidate (step S2113).

If a new mail has not been received (No in Step 2102), the mail event detection unit 201 monitors whether or not an operation for saving a file attached to the received mail to the local hard disk is detected ( Step S2114). When the mail event detection unit 201 detects an operation of saving the file attached to the received mail in the local hard disk (Yes in step S2114), the mail event detection unit 201 searches the “resource” field using the mail message ID as a key (step S2114). S2115). The resource management unit 205 adds the file storage location and file name to the found “resource” field (step S2116).
[Embodiment 4]
FIG. 23 is a block diagram illustrating an example of the configuration of the information processing apparatus according to the fourth embodiment of the present invention. In FIG. 23, the information processing apparatus further includes a related resource change monitoring unit 210 with respect to the configuration of the first embodiment. In addition, the same code | symbol is attached | subjected about the structure similar to Embodiment 1. FIG. The related resource change monitoring unit 210 determines that the resource names similar to the same conference are different versions of the same resource.

  The information processing apparatus further includes a related resource change monitoring unit 210 that monitors the change status of the resource stored in the resource storage unit by the resource management unit 205. When the related resource change monitoring unit 210 detects a resource change, the resource management unit 205 can update the corresponding resource information.

  For example, the related resource change monitoring unit 210 detects that the resource has a different version. The resource management unit 205 adds and updates the detected resource with a different version.

  Hereinafter, a description will be given according to the flowchart of FIG.

  The mail event detection unit 201 accesses the mail server 120 at regular intervals when the mail program is activated, acquires mail information when there is a new mail, and receives a new mail to the user. A notification is made (steps S2401 → S2402).

  In step S2402, if there is no new mail (No in step S2402), the mail event detection unit 201 monitors whether or not an operation for saving the file attached to the received mail on the local hard disk is detected (step S2402). Step S2413). When the mail event detection unit 201 detects an operation of saving the file attached to the received mail on the local hard disk (Yes in step S2413), the mail event detection unit 201 searches the “resource” field using the message ID of the mail as a key (step S2413). S2414). The resource management unit 205 adds the file storage location and file name to the found “resource” field (step S2415).

  On the other hand, when a new mail is received in step S2402, the mail event detection unit 201 confirms whether a file is attached to the e-mail (step S2403). This can be done by referring to the header information of the email.

  Next, the resource acquisition unit 202 refers to the text of the e-mail and confirms whether information on the resource such as directory information and URL of the shared server is described. Since the directory and URL have a specific pattern, this can be executed by simple pattern matching of character strings. At this point, if no file is attached to the e-mail and no information about the resource is described, the processing described later is not executed.

  The resource acquisition unit 202, when a file is attached to an e-mail or information about a resource is described, a message ID for uniquely identifying the e-mail described in the header information of the e-mail Is acquired (step S2404).

  Further, the related user acquisition unit 203 refers to the header information of the email, and sends the emails of the transmission source user (refer to the From header), the transmission destination user (refer to the To header), and the copy transmission destination user (refer to the Cc header). An address is acquired (step S2405).

  The related user acquisition unit 203 acquires a user ID for searching the schedule server 150 for the schedule information of the user who owns each mail address from the directory server 140 (step S2406). When the schedule server 150 manages the user's schedule by e-mail address, this user ID acquisition process using the “directory server” is unnecessary.

  Next, the common schedule extraction unit 204 acquires the schedule information of the transmission source user, transmission destination user, and copy transmission destination user acquired by the above-described processing from the schedule server 150 (step S2407).

  Next, the common schedule extraction unit 204 searches for a meeting having a common time and place from the acquired schedule information of all users (step S2408). If there is no common conference in step S2408, the common schedule extraction unit 204 returns the process to step S2401. On the other hand, if there is a common conference in step S2408 (YES in step S2409), the related resource change monitoring unit 210 determines whether the resource name is similar to the same conference when associating the conference with the resource. Determination is made (step S2410).

  If they are not similar in step S2410, the resource management unit 205 adds the resource to the “resource” field of the resource management table (step S2411).

  On the other hand, if they are similar in step S2410, the related resource change monitoring unit 210 regards the version difference of the same resource, and the resource management unit 205 displays the information of the current “resource” field of the resource management table as the previous version. Is added to the head of the “resource” field (step S2412).

  For example, “document 200909030.doc” and “document 20099092-2.doc” have the same file name except for the part corresponding to the date, and are therefore regarded as the same resource and managed as resources of different versions in time order. Of course, the above determination method is merely an example, and similarity may be determined using a determination method other than this. The resource management table 2500 at this time is shown in FIG. 25, and the related resource list screen 2600 is shown in FIG.

  In FIG. 25, the “resource previous version” field is added to the normal resource management table, and if it is determined that the version is different when the resource is added, the resource management unit 207 displays the resource in the “resource” field. In this example, information is added to the head of the “resource previous version” field, and new resource information is set in the “resource” field.

  FIG. 26 shows an “other version” window displayed when a resource in the “resource” list on the related resource list screen 2600 is selected and the “previous version” button is clicked. The “Previous Version” button can be clicked only when a resource having a plurality of versions is selected. In the “other version” window, the resource information stored in the “prior resource version” field of the resource management table 2500 of FIG. 25 is displayed.

  Select a resource in the “Other Versions” window and click the “Open” button to open the corresponding resource. The “Open” button is clickable only when a resource in the “Other Version” window is selected. Clicking the “Close” button closes the “Other Versions” window.

  In addition, when associating resources with a conference, the previous conference related to the “sender”, “receiver”, and “copy recipient” that is the source of the conference may be associated and managed. 28 shows a conference history table 2800, a resource management table 2900 for managing conferences related to FIG. 29 in association with each other, and FIG. 30 shows a related resource list screen 3000.

  In the conference history table 2800 shown in FIG. 28, conference information whose conference date has passed is stored. Other than the “conference ID” field for identifying the conference, the values of the fields of the resource management table 2900 are stored. However, the “use flag” field is not stored. Since it is difficult to store and manage all common events whose date and time have passed on the mail program due to memory limitations, the conference history table 2800 may be stored on the database server. Further, only information during a predetermined period may be stored.

  FIG. 29 shows a resource management table 2900 in which the “related conference ID” field is added to the normal resource management table. This field is a field in which the conference history table 2800 is searched to store a conference ID in which “sender”, “receiver”, and “copy recipient” information matches the conference extracted this time. It should be noted that past conferences may be conducted by other methods such as searching only by “sender” and “recipient”.

  FIG. 30 shows a “related conference” window displayed when the “related conference” button on the related resource list screen 3000 is clicked. The “related conference” button is clickable only when the related resource list screen 3000 of the conference with the related conference is displayed. In the “related conference” window, information corresponding to the ID stored in the “related conference” field of FIG. 29 is displayed.

  Hereinafter, the above example will be described with reference to the flowchart of FIG.

  The mail event detection unit 201 accesses the mail server 120 at regular intervals when the mail program is activated, acquires mail information when there is a new mail, and receives a new mail to the user. It is notified (step S2701 → S2702).

  If there is no new mail (No in step S2702), the mail event detection unit 201 monitors whether or not an operation for saving the file attached to the received mail to the local hard disk is detected. When the mail event detection unit 201 detects an operation of saving the file attached to the received mail in the local hard disk (Yes in step S2712), the mail event detection unit 201 searches the “resource” field using the mail message ID as a key (step S2712). S2713). The resource management unit 205 adds the file storage location and file name to the found “resource” field (step S2714).

  On the other hand, when a new mail is received (Yes in step S2702), the mail event detection unit 201 checks whether a file is attached to the e-mail (step S2703). This can be done by referring to the header information of the email.

  Next, the resource acquisition unit 202 refers to the text of the e-mail and confirms whether information on the resource such as directory information and URL of the shared server is described. Since the directory and URL have a specific pattern, this can be executed by simple pattern matching of character strings. At this point, if no file is attached to the e-mail and no information about the resource is described, the processing described later is not executed.

  The resource acquisition unit 202, when a file is attached to an e-mail or information about a resource is described, a message ID for uniquely identifying the e-mail described in the header information of the e-mail Is acquired (step S2704).

  Further, the related user acquisition unit 203 refers to the header information of the email, and sends the emails of the transmission source user (refer to the From header), the transmission destination user (refer to the To header), and the copy transmission destination user (refer to the Cc header). An address is acquired (step S2705).

  The related user acquisition unit 203 acquires a user ID for searching the schedule server 150 for the schedule information of the user who owns each mail address from the directory server 140 (step S2706). When the schedule server 150 manages the user's schedule by e-mail address, this user ID acquisition process using the “directory server” is unnecessary.

  Next, the common schedule extraction unit 204 acquires the schedule information of the transmission source user, the transmission destination user, and the copy transmission destination user acquired by the above-described processing from the schedule server 150 (step S2707).

  Next, the common schedule extraction unit 204 searches for a meeting having a common time and place from the acquired schedule information of all users (step S2708). If there is no common conference in step S2708, the common schedule extraction unit 204 returns the process to step S2701. On the other hand, if there is a common conference in step S2708 (YES in step S2709), the related resource change monitoring unit 210 refers to the conference history table 2800, and “sender” and “recipient” that are the origin of the conference. A related meeting, which is a previous meeting related to the “copy recipient”, is acquired (step S2710).

  Next, the resource management unit 205 updates the resource corresponding to the acquired related conference in the resource management table (step S2711).

  At this time, information on “date and time”, “location”, and “resource” of the corresponding conference is acquired and displayed as a list by using the conference ID in the “related conference” field as a key. Select a resource in the “Related Meeting” window and click the “Open” button to open the corresponding resource. The “Open” button is clickable only when a resource in the “Related Meeting” window is selected. Clicking the “Close” button closes the “Related Meeting” window.

  The related resource change monitoring unit 210 monitors the change operation of the resource file name and storage location, and when there is a change, the resource information before the change is used as a key, and the entry to be changed in the resource management table is displayed. Identify and replace with resource information after change.

  Hereinafter, the above case will be described with reference to the flowchart of FIG.

  First, the mail event detection unit 201 determines whether or not a resource change event has been received (steps S3101 → S3102). In step S3102, if not received, the mail event detection unit 201 returns the process to step S3101. On the other hand, if received in step S3102, the resource change monitoring unit 210 acquires resource information before the change based on the information of the resource change event (step S3103).

  Next, the resource change monitoring unit 210 searches for a change target resource from the resource management table (step S3104). If there is a change target resource (YES in step S3105), the resource management unit 205 updates the resource management table.

The resource change operation can be monitored, for example, by monitoring an operating system event. Thereby, even when the user changes the file name or storage location of the resource, the correct resource can be opened from the related resource list screen.
[Embodiment 5]
FIG. 32 is a block diagram illustrating an example of the configuration of the information processing apparatus according to the fifth embodiment of the present invention. In FIG. 32, the information processing apparatus further includes a related user situation acquisition unit 211 with respect to the configuration of the first embodiment. In addition, the same code | symbol is attached | subjected about the structure similar to Embodiment 1. FIG. The related user status acquisition unit 211 acquires information on the current status and operation of the user related to the conference.

  The information processing apparatus further includes a related user status acquisition unit 211 that acquires a user's location status related to the common schedule extracted by the common schedule extraction unit 204. When the related user situation acquisition unit 211 acquires a change in the user's place situation, the presentation unit changes and presents the resource presentation priority so as to correspond to the place situation.

  For example, the related user status acquisition unit 211 acquires the location change status of the user. When the user who has changed the location is in the corresponding location, the presentation unit 207 presents the resource with a higher priority, and when the user is not in the corresponding location, the presentation unit 207 presents the resource with a lower priority.

  The related user status acquisition unit 211 transmits and receives the current status and operations of users related to the conference to each other, and uses the information to change the priority of the resource. For example, information can be transmitted and received in real time by using a presence system.

  Specifically, when the related user status acquisition unit 211 extracts the conference, the presence information of other users has changed since then by executing the process of subscribing to the presence information of other users other than itself. When you can receive information in real time.

  For example, when the user's location is changed, the user's location information is sent to other users, so that when the user is at the conference location, the priority of the resource from which the user is the source is raised and the user is not at the conference location In this case, the priority of the resource that is the source of the user is lowered. The priority can be raised or lowered by rearranging the order of the “resource” fields in the resource management table. As a result, documents sent by users who are not at the meeting location (not attending) are not displayed on the related resource list screen, or can be displayed at the bottom of the list, making it easier for users to access resources. Increases nature.

  Hereinafter, the above example will be described with reference to the flowchart of FIG.

  When the user moves to the conference room, the user's notebook PC 110 connects to the wireless LAN access point installed in the conference room, and the location detection unit 206 acquires the BSSID of the wireless LAN access point (steps S3301 → S3302).

  When the BSSID is acquired, the location detection unit 206 acquires location information indicated by the BSSID using, for example, the location association table 800 illustrated in FIG. 8 (step S3303). This makes it possible to determine where the user is currently.

  Next, when the location detection unit 206 determines the location by connecting to the wireless LAN access point of the conference room, the location detection unit 206 determines whether or not the location has moved from the previous location (step S3304). In step S3304, if the user has not moved, the location detection unit 206 returns the process to step S3301. On the other hand, when the user is moving, the related user situation acquisition unit 211 sets location information in the presence (step S3305).

  Next, the presentation unit 207 displays a related resource list corresponding to the place set in the presence (step S3306).

  If the BSSID cannot be acquired, the related user status acquisition unit 211 determines whether location information has been received (step S3307). In step S3307, if not received, the related user status acquisition unit 211 returns the process to step S3301. On the other hand, when the resource is received, the resource acquisition unit 202 acquires the resource for which the user is the location information transmission source (step S3308).

  If the resource does not exist (NO in step S3309), the resource acquisition unit 202 returns the process to step S3301. On the other hand, when the resource exists (YES in step S3309), the presentation unit 207 determines whether the related resource list is being displayed (step S3310).

  In step S3310, when not being displayed, the presenting unit 207 changes the order of the “resource” field of the resource management table (step S3311). On the other hand, when the display is being performed in step S3310, the presentation unit 207 changes the display position of the corresponding resource, and changes the order of the “resource” field of the resource management table (steps S3311 → S3312).

  In addition, when a user opens a related resource, if the source of the resource is himself, by setting the file open command and the opened resource name as presence information, the command and resource name are notified to other users. The display priority of the corresponding resource can be increased on the related resource list screen of other users.

  As a result, when the resource transmission source user opens the resource to explain the contents, other users can easily find the resource from the list. In addition to increasing the display priority, resources may be automatically opened. In this case, the resource may be automatically opened only when the user does not refer to another resource. In addition, when the resource is in the thread format, the resource may be opened by selecting the thread with the latest update time and opening the resource.

  The above example will be described with reference to the flowchart of FIG.

  First, the related user situation acquisition unit 211 determines whether or not a resource has been opened from the resource list (step 3401 → S3402).

  If it is opened in step S3402, the related user status acquisition unit 211 acquires information on the sender of the resource from the resource management table (step S3403).

  If the resource sender is not himself (NO in step S3304), the presenting unit 207 opens the file on his terminal (step S3404 → step S3406). On the other hand, if the sender of the resource is itself (YES in step S3404), the related user status acquisition unit 211 sets the file open and the file name in the presence, and opens the file on its own terminal ( Step S3404 → S3405 → S3405).

  If the file is not opened in step S3402, the related user status acquisition unit 211 determines whether a file open command has been received (step S3407).

  In step S3407, if it is not received, the related user situation acquisition unit 211 returns the process to step S3401. On the other hand, when it is received in step S3407, the presenting unit 207 determines whether or not the related resource list is being displayed (step S3408).

In step S3408, when the related resource list is being displayed, the presentation unit 207 displays the corresponding resource at the top, and the resource management unit 205 changes the order of the resource fields in the resource management table (steps S3409 → S3410). . On the other hand, if the related resource list is not being displayed in step S3408, the resource management unit 205 changes the order of the resource fields in the resource management table (steps S3408 → S3410).
[Embodiment 6]
FIG. 35 is a block diagram illustrating an example of the configuration of the information processing apparatus according to the sixth embodiment of the present invention. In FIG. 35, the information processing apparatus further includes a time input unit 212 with respect to the configuration of the first embodiment. In addition, the same code | symbol is attached | subjected about the structure similar to Embodiment 1. FIG. The time input unit 212 receives input of date and time from the user.

  The information processing apparatus further includes a time input unit 212 that receives input of time information from the user. The resource list generation unit 206 can present resource information related to a schedule corresponding to the time at which the time input unit 212 has accepted the input.

  For example, the time input unit 212 receives input of time information from the user. The resource list generation unit 206 presents the resources associated with the conference after the time when the input is accepted to the user.

  The time input unit 212 receives input of time information from the user, and displays related resources of the conference after the input time. Thereby, even before the conference starts, related resources associated with the conference can be easily referred to, and the convenience for the user is enhanced.

  FIG. 36 shows a “conference display window” displayed when the “specify date and time” button on the related resource list screen 3600 is clicked. When a date and time is entered in the “date and time designation” field of the “conference display” window and the “search” button is clicked, the common schedule extraction unit 204 refers to the resource management table and extracts the first meeting after the input time. The associated resource information is displayed.

  If the “search” button is clicked without entering the date and time in the “date and time designation” field, the first meeting after the current time is extracted and the associated resource information is displayed. When the “Previous” button and the “Next” button are clicked, the resources associated with the conference before or after the currently displayed conference are displayed.

  Select a resource in the “Conference View” window and click the “Open” button to open the corresponding resource. The “Open” button is clickable only when a resource in the “Conference Display” window is selected. Clicking the “Close” button closes the “Conference View” window.

In the present embodiment, only the date and time are specified, but it is also possible to search by matching the location or by searching only by location.
[Embodiment 7]
FIG. 37 is a block diagram illustrating an example of the configuration of the information processing apparatus according to the seventh embodiment of the present invention. In FIG. 37, the information processing apparatus further includes an other terminal information transmission / reception unit 213 with respect to the configuration of the first embodiment. In addition, the same code | symbol is attached | subjected about the structure similar to Embodiment 1. FIG. The other terminal information transmission / reception unit 213 transmits / receives detection information of other terminals existing on the network.

  The information processing apparatus includes a terminal that includes a resource storage unit. The information processing apparatus further includes an other terminal information transmission / reception unit 213 that detects the presence of a terminal of another user and transmits / receives information to / from the other user terminal. When the other terminal information transmitting / receiving unit 213 detects the presence of another user's terminal, the other terminal information transmitting / receiving unit 213 refers to the resource storage unit of its own terminal to determine whether the user owns the resource. The terminal can be requested to transmit resources.

  For example, the other terminal information transmission / reception unit 213 detects the presence of another user's terminal. When the other terminal information transmitting / receiving unit 213 detects the presence of a terminal of another user, the other terminal information transmitting / receiving unit 213 determines whether or not the own terminal has resources related to the current schedule. The other terminal information transmission / reception part 213 requests | requires the resource regarding the present schedule with respect to another terminal, when it determines with the resource regarding the present schedule not being own terminal.

  The above example will be described below with reference to the flowchart of FIG.

  First, the other terminal information transmission / reception unit 213 determines whether another terminal is detected (steps S3801 → S3802). If another terminal is detected in step S3802 (YES in step SS3802), the resource management table of its own terminal is searched using the current location information and time information as keys (step S3803) and associated with the current conference. It is determined whether the owned resource is owned (step S3804).

  In step S3804, if the own terminal does not own the resource, the other terminal information transmitting / receiving unit 213 requests the mail program operating on the other terminal to transmit the resource list and the resource (step S3804). S3805). On the other hand, if the own terminal owns the resource, the other terminal information transmitting / receiving unit 213 returns the process to step S3801.

  Also, the other terminal that has received the request command searches the resource management table based on the location and time information (YES in step S3806 → S3807).

  When there is no resource (NO in S3808), the presentation unit 207 generates an empty resource list (step S3811). On the other hand, when there is a resource (YES in S3808), the presentation unit 207 generates a resource list associated with the current conference (step S3809), and when the resource is an e-mail or a file stored locally Are transmitted including those entities (step S3810).

  If the request command has not been received (NO in step S3806), the other terminal information transmitting / receiving unit 213 determines whether a request response has been received (step S3812). If not received in step S3812, the other terminal information transmitting / receiving unit 213 returns the process to step S301. On the other hand, when receiving, the presentation unit 207 determines whether or not the resource list is empty (step S3813).

  In step S3813, when it is not empty, the presentation unit 207 returns the process to step S3801. On the other hand, when it is empty, the presentation unit 207 copies the resource to a predetermined folder (S3814). Then, the presentation unit 207 rewrites the contents of the “resource” field in the resource list to the actual storage location (step S3815). Then, the presentation unit 207 merges the resource list into its own resource management table (step S3816).

  Thereby, the user who participated in the emergency meeting can receive the necessary resources from the surrounding users. Note that detection of other terminals in the vicinity and actual data transmission / reception can be realized by using a proximity wireless technology such as Bluetooth. Of course, you may implement | achieve by communication technologies other than Bluetooth. Also, in the above, the resource list and the resource are requested when there is no related resource in the terminal of its own, but the resource list of the difference is transmitted on the side of receiving the request command by attaching the resource list to the request command and transmitting it. The list and resource entities may be returned in response.

  In the above embodiment, an example is shown in which the resource management table is held in the notebook PC. However, when the resource management table is installed in the server and a mail event detection unit is required, the resource management table is transmitted via the network. The configuration may be referred to. As a result, it is possible to easily access resources related to the conference even when using a different PC depending on the location, such as a desktop PC at the office desk or a notebook PC at the conference.

  As described above, according to the present invention, it is possible to improve the complexity of the procedure for referring to resources (conference materials etc.) related to a conference. Specifically, since the user does not need to perform a special operation, the event and the file can be easily associated with each other. Further, when the time and the detected location hit the event, the file list automatically associated is automatically displayed or the file is opened, so that the user does not need to search for the related file, which is highly convenient.

  The configuration described in the above embodiment merely shows a specific example, and does not limit the technical scope of the present invention. Any configuration can be employed within the scope of the effects of the present invention.

  In the embodiment of the present invention, a software program (in the embodiment, a program corresponding to the flowchart shown in the drawing) is supplied to an apparatus, and the computer of the apparatus supplies the program supplied to the apparatus. It is also possible to achieve this by reading and executing. Therefore, in order to realize the functional processing described in this embodiment by a computer, the program itself installed in the computer is also an embodiment of the present invention. That is, a program for realizing the functional processing of the present invention is also included in one aspect of the embodiment. A medium recording a program for realizing the functional processing of the present invention is also included in one aspect of the embodiment.

100 Information processing system 110 Notebook PC
120 Network 130 Mail Server 140 Directory Server 150 Schedule Server 201 Mail Event Detection Unit 202 Resource Acquisition Unit 203 Related User Acquisition Unit 204 Common Schedule Extraction Unit 205 Resource Management Unit 206 Location Detection Unit 207 Presentation Unit 208 Resource Usage Monitoring Unit 209 Schedule Information Change Monitoring unit 210 Related resource change monitoring unit 211 Related user status acquisition unit 212 Time input unit 213 Other terminal information transmission / reception unit

Claims (12)

A mail event detector that detects events related to sending and receiving e-mail;
A resource acquisition unit for acquiring resource information including information related to the e-mail or information for accessing the resource from the information included in the e-mail or an attached file;
A related user acquisition unit that acquires user information of a plurality of users related to the e-mail;
Based on user information of a plurality of users acquired by the related user acquisition unit, a common schedule for extracting a common schedule of the plurality of users with reference to schedule information in which an email user is associated with the schedule of the user A schedule extractor;
An information processing apparatus comprising: a resource management unit that stores resource information acquired by the resource acquisition unit in association with a common schedule extracted by the common schedule extraction unit in a resource storage unit. A location detector that detects where the user is currently located;
A presentation unit for presenting resource information associated with and stored by the resource storage unit when the location detected by the location detection unit matches the location where the common schedule extracted by the common schedule extraction unit is implemented; The information processing apparatus according to claim 1, further comprising:   The common schedule extraction unit refers to the schedule information, calculates a commonality score of a plurality of users' schedules, and extracts a schedule in which the calculated commonness score exceeds a predetermined value as a common schedule. The information processing apparatus according to 1 or 2.   The said resource acquisition part determines the presence or absence of the resource relevant to the said e-mail, and when it determines with a resource existing, the process of the said common schedule extraction part and the said resource management part is performed. 4. The information processing apparatus according to any one of 3.   The information processing apparatus according to claim 1, wherein the resource management unit stores resource information in a resource storage unit for each thread in which the electronic mail is grouped. The resource management unit further comprises a resource monitoring unit that monitors the usage status or change status of the resource information stored in the resource storage unit,
The information processing apparatus according to claim 1, wherein the resource management unit updates corresponding resource information when the resource monitoring unit detects use or change of resource information. A schedule information update monitoring unit for detecting an update of the user's schedule information;
The information processing apparatus according to claim 3, wherein the common schedule extraction unit recalculates a commonness score and extracts a common schedule again when the schedule information update monitoring unit detects an update of the schedule information. . A related user status acquisition unit that acquires a user's location status related to the common schedule extracted by the common schedule extraction unit;
The said presentation part changes the presentation priority of resource information so that it respond | corresponds to a user's place condition, when the said related user condition acquisition part acquires a user's place condition change, It presents. Information processing device. A time input unit for receiving time input from the user;
The information processing apparatus according to claim 2, wherein the presenting unit presents resource information related to a schedule corresponding to a time when the time input unit accepts an input. An information processing apparatus configured by a terminal including the resource storage unit,
It further includes an other terminal information transmission / reception unit for transmitting / receiving information to / from another user terminal,
When the other terminal information transmitting / receiving unit detects the presence of another user's terminal, the other terminal information transmitting / receiving unit determines whether the resource information is owned by referring to the resource storage unit of its own terminal. The information processing apparatus according to claim 1, wherein the information processing apparatus requests a user terminal to transmit resource information. Computer
A mail event detection step for detecting an event related to transmission / reception of an email;
A resource acquisition step of acquiring resource information including information related to the e-mail or information for accessing the resource from information included in the e-mail or an attached file;
A related user acquisition step of acquiring user information of a plurality of users related to the e-mail;
Based on user information of a plurality of users acquired in the related user acquisition step, a common schedule for extracting a common schedule of the plurality of users with reference to schedule information that associates an email user with the user's schedule A schedule extraction step;
An information processing method comprising: a resource management step of storing the resource information acquired in the resource acquisition step and the common schedule extracted in the common schedule extraction step in association with each other in a resource storage unit. On the computer,
A mail event detection step for detecting an event related to transmission / reception of an email;
A resource acquisition step of acquiring resource information including information related to the e-mail or information for accessing the resource from information included in the e-mail or an attached file;
A related user acquisition step of acquiring user information of a plurality of users related to the e-mail;
Based on user information of a plurality of users acquired in the related user acquisition step, a common schedule for extracting a common schedule of the plurality of users with reference to schedule information that associates an email user with the user's schedule A schedule extraction step;
An information processing program that executes a resource management step of associating resource information acquired in the resource acquisition step with a common schedule extracted in the common schedule extraction step and storing the same in a resource storage unit.

Images