JP5767962B2 - Address information registration / updating apparatus, address information registration / updating method, and address information registration / updating program - Google Patents

Description

  The present invention relates to an apparatus, a method, and a program that enable address information to be appropriately shared within an organization such as a company.

  E-mail has become an indispensable business tool as an inexpensive and easy communication tool. An address book function that stores and holds address information such as the name of the other party and an e-mail address in a communication device such as a personal computer used for sending and receiving e-mail, in order to easily and reliably send the e-mail. Is provided. Normally, for a communication device address book, the user can input the address information directly, or register the address information added to the received e-mail. Accumulate information. For this reason, if a user neglects the maintenance with respect to the address book of a communication apparatus, a useful address book cannot be formed.

  For this reason, Patent Document 1 described later discloses an invention relating to an address book update support method and apparatus. The invention described in Patent Document 1 first selects an e-mail from which personal information is to be extracted upon receipt of an e-mail, performs signature analysis on the e-mail that has been extracted, and performs address analysis. Update information is extracted and stored. Then, at a certain opportunity, the accumulated update information is reflected in the actual address book while confirming the user or automatically. That's it. According to the invention described in Patent Document 1, it is possible to reduce the maintenance load on the address book (address book) of the user's communication device.

Japanese Patent Laid-Open No. 10-171827

  In recent years, it has become impossible to keep business cards on the desk from the viewpoint of protecting personal information, and it has become time consuming to search for the telephone number of the other party. In addition, from the current situation in which electronic mail is frequently transmitted and received, it is necessary to appropriately update the address book that can be used from the personal computer used by the user to make it more convenient to use. In this case, it is not preferable that the user must perform maintenance of the address book frequently because the load on the user increases. Therefore, it is conceivable to use the technique described in Patent Document 1 described above.

  However, in an organization such as a company, the address book of the communication equipment that has been prepared is often suddenly rendered useless under the influence of personnel changes or reassignment. For example, if all of the business partners you are in charge of have changed due to personnel changes or reassignment, you must take over the business card of the business partner in charge from the predecessor and re-register it in the address book of the communication device. Don't be. Your successor must do the same. In other words, the update of the address book of the communication device must be performed for each communication device, which is extremely inefficient when viewed from the whole organization such as a company. It is also possible to collect address information from personal computers in an organization such as a company to form a shared address book, but simply collecting address information results in too much address information, It cannot be formed.

  In view of the above, the present invention is an easy-to-use shared address database that easily and reliably manages address information for various destinations in an organization such as a company without bothering the user as much as possible. The purpose is to arrange.

In order to solve the above-described problem, an address information registration / updating device according to the first aspect of the present invention provides:
A shared address database that manages the address information of email recipients by department,
Affiliation information storage means for storing affiliation history information including identification information of all employees, affiliation period, and department,
E-mail extracting means for extracting e-mail whose transmission date / time is within the range of the input / predetermined transmission date / time among the stored received e-mails ;
The email extractor means analyzes the information contained in the e-mail received extracted by the address information extraction means for extracting the destination address information to be registered in the address book,
Referring to the affiliation history information of the membership information storage means based on the received the e-mail recipient's identification information and the transmission time of the electronic mail to be analyzed is its own user, the transmission date and time the recipient Identifying means for identifying the department to which the user belonged as the registration destination of the address information of the other party extracted by the address information extracting means ;
And characterized in that it comprises with respect to the shared address database, the address information the destination address information extracted by the extraction means, and registering means for registering as the address information of the department that is specified by the specifying means Address information registration / updating device.

As a result, address information about various destinations can be registered in a shared address database that manages address information by affiliation easily and reliably without the user's hand as much as possible, and this can be shared. Can do. Since the shared address database manages address information by affiliation, it is easier to use, unlike an address database that simply collects address information. Further, based on the transmission date and time of the e-mail, the affiliation destination of the user who has received the e-mail is specified with reference to the affiliation history information. In other words, even if the user's affiliation changes due to personnel changes, etc., the affiliation can be specified on the basis of the e-mail transmission date, so the address information of the other party extracted from the accumulated e-mail Can be registered as address information of an appropriate affiliation.

  It is possible to easily and surely manage address information about various destinations in an organization such as a company and to prepare a user-friendly shared address database without bothering the user as much as possible.

It is a figure for demonstrating the structural example of the LAN (Local Area Network) system formed in a predetermined organization, the mail server apparatus 1 connected to the said LAN system, and the local terminal device 5. FIG. It is a figure for demonstrating the structural example of the shared address database. It is a figure for demonstrating the structural example of the personnel information database. 4 is a flowchart for explaining registration update processing of a shared address database 2 executed in the mail server device 1 and the local terminal device 5. 5 is a flowchart for explaining details of a registration update process of the shared address database 2 performed in steps S103 and S104 shown in FIG. It is a flowchart following FIG. It is a figure for demonstrating the example of the display screen used in the process of the flowchart shown to FIG. 5, FIG. It is a figure for demonstrating the example of the display screen used in the process of the flowchart shown to FIG. 5, FIG. It is a flowchart for demonstrating the process in the case of registering and updating the address information of an other party in the shared address database 2 fully automatically.

  Hereinafter, embodiments of the apparatus, method, and program of the present invention will be described with reference to the drawings. In the embodiments described below, for example, a case where the present invention is applied to a LAN system mail server device or a local terminal device mainly a personal computer formed in a predetermined organization such as a company is taken as an example. I will explain.

[Configuration example of mail server device and local terminal device]
FIG. 1 is a diagram for explaining a configuration example of a LAN system formed in a predetermined organization such as a company, a mail server device connected to the LAN system, and a local terminal device. The LAN system of this embodiment includes a mail server device 1, a shared address database 2, a personnel information database 3, and a number of local terminal devices 5 (1), 5 (2), 5 (3),. , And connected through the LAN 4. In the following, for the sake of simplicity, the shared address database 2 is abbreviated as a shared address DB2, and the personnel information database 3 is abbreviated as a personnel database DB3.

  The LAN 4 is a network formed in a predetermined organization using one or both of wired and wireless. The mail server device 1 enables transmission / reception of electronic mail between the LAN 4 and the outside and within the LAN 4. That is, the mail server device 1 has both a function as an SMTP (Simple Mail Transfer Protocol) server and a function as a POP (Post Office Protocol) server.

  The shared address DB 2 is formed in a large-capacity recording medium such as a hard disk, manages address information for each department, and 5 (1), 5 (2) of the mail server device 1 connected to the LAN 4 and each local terminal device described later. ), 5 (3)... Can be used. FIG. 2 is a diagram for explaining a configuration example of the shared address DB2. As shown in FIG. 2, the shared address DB 2 includes “management department”, “registration No.”, “name”, “company”, “affiliated department”, “phone”, “address”, “e-mail”, “ URL ”and“ Remarks ”are accumulated. “Management department” is information indicating a department in the company that should manage the address information. Each of the management departments is assigned a department code as shown by numbers “001”, “002”, “003”,... In FIG.

In FIG. 2, “ registration No.” is identification information attached to each address information in each management department, and functions as index information for identifying each address information together with a department code attached to the management department. Is realized. That is, “department code + registration number” is index information for specifying each address information. In FIG. 2, information from “name” to “URL” constitutes address information (addressee information) of the addressee. Note that various information necessary for “remarks” is input. In addition to this, it is possible to include various kinds of information, for example, adding the person-in-charge information for each address information.

  In FIG. 2, “Name” is the name (name) of the contact person in charge, “Company” is the name of the company (organization) to which the contact person belongs, and “Department” is the contact person in charge. This is the department name of the department to which the person belongs. “Telephone” is the telephone number of the contact person in charge. In the “phone” field of the shared address DB2, the representative number of the company to which the contact person belongs, the telephone number of the department to which the contact person belongs, the direct communication number of the contact person, the mobile phone number of the contact person, Each facsimile number of the contact person can be managed. The “address” is address information used when mail or the like is mailed to the contact person in charge, and usually indicates the location of the company or office to which the contact person belongs. “E-mail” is the e-mail address of the contact person in charge, and “URL” is the URL of the website of the company or department to which the contact person belongs.

  Then, as shown in FIG. 2, the address information of the other party is managed for each management department in the shared address DB2. Therefore, it is not necessary to change the address information of the shared address DB2 even if the person in charge changes to another department or is changed.

  In FIG. 1, a personnel information DB 3 is formed in a large-capacity recording medium such as a hard disk, and manages employee information of all employees in the company. The personnel information DB 3 can refer to the mail server device 1 connected to the LAN 4 and the local terminal devices 5 (1), 5 (2), 5 (3),... Within the permitted range. FIG. 3 is a diagram for explaining a configuration example of the personnel information DB 3. As shown in FIG. 3, the personnel information DB 3 stores “employee ID”, “employee name”, “e-mail address”, “entry date”, and “affiliation history information”. In addition to this, the personnel information DB 3 also stores various types of information such as home addresses, home phone numbers, educational histories, and work histories of each employee. However, since it is not used in this embodiment, the description of such information is omitted in FIG.

  In FIG. 3, “Employee ID” is unique identification information assigned to each employee. “Employee name” is the name of each employee, “E-mail address” is the email address assigned to each employee, and “Date of entry” is information indicating when each employee joined the company. is there. “Affiliation history information” is equivalent to the affiliation history (transfer history) information of each employee, and the affiliation period specified by the start date and end date, It is associated.

  Therefore, in the case of the example shown in FIG. 3, the employee “Taro” identified by the employee ID “050001” has an e-mail address of “xxxx @ ...” and “April 1, 2005” The personnel information DB 3 is managed to join the company. The employee “Taro XX” belongs to “First Sales Department” from “April 1, 2005 to March 31, 2007”, and “April 1, 2007 to March 2010”. It is managed in the personnel information DB 3 that it belongs to the “second sales department” until “31st” and belongs to the general affairs department from “March 31, 2010 to the present”.

  In addition, the employee “△△ Hanako” identified by “Employee ID” “060052” has an e-mail address of “yyyy @…”, and that he / she joined the company on “July 20, 2006” Managed by DB3. It is managed in the personnel information DB 3 that the employee “ΔΔ Hanako” belongs to the design department from “July 20, 2006 to the present”. As described above, the personnel information DB 3 of this embodiment has affiliation history information of company employees, and accurately manages which employees belong to which department from when to when.

  In FIG. 1, each of the local terminal devices 5 (1), 5 (2), 5 (3),... Is mainly a personal computer used by an employee and includes various application programs. Perform information processing. Each of the local terminal devices 5 (1), 5 (2), 5 (3),... Has a so-called mailer for sending and receiving emails, and sends and receives emails through the mail server device 1. Can do.

  In this embodiment, the mail server device 1 stores the received electronic mail (received mail) addressed to the subordinate local terminal and the electronic mail (transmitted mail) transmitted from the subordinate local terminal device. Then, the mail server device 1 analyzes, for example, the received mail and the transmitted mail accumulated for one day or the set number of days, extracts the address information of the other party (the other party information), and uses this as the shared address It has a function to update registration in the DB.

  Similarly, each of the local terminal devices 5 (1), 5 (2), 5 (3),... Stores received electronic mail (received mail) and transmitted electronic mail (transmitted mail). Each of the local terminal devices 5 (1), 5 (2), 5 (3),... Analyzes the received received mail and the transmitted mail in the order of the received date or the transmitted date, It has a function of extracting information and registering and updating it in the shared address DB.

  As described with reference to FIG. 2, the shared address DB 2 manages the address information of the other party for each department. For this reason, the mail server device 1 and each of the local terminal devices 5 (1), 5 (2), 5 (3),... Identify the department to which the receiver or sender belongs. Each of the mail server device 1 and the local terminal devices 5 (1), 5 (2), 5 (3),... Is registered or updated in the shared address DB.

  Note that the recipients and the departments to which the sender belongs at the date and time of email transmission are specified for processing the stored emails, so even if personnel changes are made, This is to appropriately specify the department to which the transmission date / time belongs. Therefore, it is assumed that the user who has moved from the first sales department to the general affairs department has performed processing to extract the address information of the other party from the received or transmitted e-mail and update the registration in the shared address DB 2 after the change. In this case, it can be determined that the address information from the e-mail received or transmitted before the change, that is, when belonging to the first sales department, should be managed as the address information of the first sales department. Further, it is possible to determine that address information from an e-mail received or transmitted after moving, that is, after moving to the general affairs department, should be managed as address information of the general affairs department.

  For example, after the personnel change, the person in charge of the other party may change, for example, so that an e-mail from a new partner concerning the department to which the employee belongs before the change may be received. In such a case, an e-mail notifying that the person has been transferred to the other party and a new person in charge is returned, and the address information of the e-mail is excluded from the target of registration update of the shared address DB2. To deal with it. In this way, it is possible to avoid the inconvenience of registering address information that should not be registered in that department.

  Next, in each of the mail server device 1 of the LAN system of this embodiment configured as shown in FIG. 1 and the local terminal devices 5 (1), 5 (2), 5 (3),. The main part for performing the registration update process for the shared address DB2 will be described. As shown in the block diagram on the upper end side of FIG. 1, the mail server device 1 includes a main part for performing registration update processing of the shared address DB2. Further, the local terminal device 5 (1) includes a main part for performing registration update processing of the shared address DB2 as shown in the block diagram on the lower end side of FIG. Each of the local terminal devices 5 (2), 5 (3),... Has the same configuration as the local terminal device 5 (1). For this reason, unless otherwise indicated, the local terminal devices 5 (1), 5 (2), 5 (3),... Are collectively referred to as the local terminal device 5.

  As can be seen by comparing the block diagrams of the mail server device 1 and the local terminal device 5, the mail server device 1 includes the communication I / F 11, but the local terminal device 5 does not include the communication I / F. For example, the configuration is almost the same. For this reason, here, common parts other than the communication I / F 11 will be described in common to avoid redundant description.

  The communication I / F 11 of the mail server device 1 is for performing communication through a wide area network such as the Internet. Specifically, the communication I / F 11 receives a signal from the wide area network, converts it into data that can be processed by the own device, and supplies the data to the control unit 12. In addition, the communication I / F 11 converts various data for transmission supplied through the control unit 12 into signals conforming to the protocol and transmits the signals to the wide area network.

  Next, a common part between the mail server device 1 and the local terminal device 5 will be described. The control units 12 and 52 control the respective units of the devices 1 and 5, and although not shown, a CPU (Central Processing Unit), a ROM (Read Only Memory), and a RAM (Random Access Memory) are connected through a CPU bus. A computer device configured. The LAN I / Fs 13 and 53 are for transmitting and receiving information through the LAN 4. In this embodiment, the LAN I / Fs 13 and 53 access the shared address DB2 and the personnel information DB on the LAN 4 to refer to the information, and register or update the address information with respect to the shared address DB2. It is used in cases such as

  The received mail storage units 14 and 54 are for storing received mail, and the transmitted mail storage units 15 and 55 are for storing transmitted mail. These received mail storage units 14 and 54 and transmitted mail storage units 15 and 55 are formed in a large-capacity recording medium such as a hard disk. The operation units 16 and 56 include a keyboard, a mouse (pointing device), and the like. The operation units 16 and 56 receive operation input from the user and supply the received information to the control units 12 and 52. The display unit 17 is for displaying various display information. The HDDs 18 and 58 are provided with a hard disk, and write / hold / read / delete various application programs and data obtained by various processes to the hard disk.

  Then, the inquiry processing units 19a and 59a make an inquiry as to whether or not to extract the address information of the other party and register it in the shared address DB2 for each of the stored received mail and transmitted mail. The counterpart information extraction units 19b and 59b analyze the received mail and the outgoing mail and extract the address information of the counterpart registered in the shared address DB2. The other party information presentation processing units 19c and 59c present the address information of the other party extracted by the other party information extracting units 19b and 59b to the user by displaying them on the display units 17 and 57, etc. In cooperation with 52, input of confirmation or change is accepted.

  The registration destination specifying units 19d and 59d specify the registration destination (management department) of the shared address DB2 in which the destination address information extracted by the destination information extraction units 19b and 59b is registered. Specifically, the registration destination specifying units 19d and 59d perform the personnel information DB3 based on the transmission date and time of the received mail or the transmitted mail from which the address information of the other party is extracted, and the recipient or sender of the received mail or the transmitted mail. The address information registration destination is specified by referring to.

  When the check processing units 19e and 59e register the destination address information extracted by the destination information extraction units 19b and 59b in the shared address DB 2 as the registration destination address information specified by the registration destination specification units 19d and 59d. Check if it is a duplicate registration. When the check processing units 19e and 59e detect that the registration is duplicated, the check processing units 19e and 59e cooperate with the control units 12 and 52 to update the address information of the registered partner, A selection input for registering the address information with another name, or not updating or registering, is accepted through the operation units 16 and 56.

  Then, the address registration units 19f and 59f register the extracted address information of the other party as information of the registered destination (management department) specified in the shared address DB2, or the address information of the other party already registered. Or process to update.

  As described above, each of the mail server device 1 and the local terminal device 5 extracts the address information of the other party from the received mail and the transmitted mail stored in its own device at an appropriate timing. Then, for the shared address DB 2 that manages the address information for each department, the address information of the other party is registered or updated using the extracted address information of the other party. In this case, taking account of personnel changes, it is possible to appropriately identify the department that should manage the address information according to the affiliation of the e-mail recipient and sender in the e-mail transmission date and time.

  Thereby, the shared address DB2 that can be used through the local terminal devices 5 (1), 5 (2), 5 (3),... Can be updated easily and reliably. In addition, since the shared address DB 2 manages the address information of the other party for each department, a user-friendly shared address DB can be realized.

[Registration update processing of shared address DB2]
Next, the registration update process of the shared address DB 2 performed in the mail server device 1 and the local terminal device 5 will be described more specifically. FIG. 4 is a flowchart for explaining the registration update processing of the shared address DB 2 executed in the mail server device 1 and the local terminal device 5. It is assumed that the control units 12 and 52 of the devices 1 and 5 have received a predetermined operation input for performing the registration update process of the shared address DB 2 through the operation units 16 and 56. In this case, the control units 12 and 52 read out an application program for executing the processing of the flowchart shown in FIG. 4 from the HDDs 18 and 58, for example, and execute it. Thus, the control parts 12 and 52 have a function as an application execution part. Further, the predetermined operation input is, for example, for selecting an icon or menu item associated with the process.

  Then, the control units 12 and 52 of the devices 1 and 5 display display information for accepting the specification of the range of the transmission date and time of the e-mail on the display units 17 and 57 and specify the range of the transmission date and time through the operation units 16 and 56 Is received (step S101). Although the display information for accepting the transmission date / time range designation displayed on the display units 17 and 57 in step S101 is not shown, for example, input fields for the start transmission date / time and the end transmission date / time, and that the input operation has been completed. And an “OK” button for instructing.

  Next, the control units 12 and 52 determine whether or not the “OK” button indicating that the input operation has been completed is selected through the operation units 16 and 56 (step S102). If it is determined in the determination process in step S102 that the “OK” button is not selected, the control units 12 and 52 repeat the process from step S101 so that the transmission date / time range designation can be input.

  If it is determined in step S102 that the “OK” button has been selected, the control units 12 and 52 first execute registration update processing for the shared address DB2 based on the received mail (step S103). After the process of step S103, the control units 12 and 52 execute the registration update process of the shared address DB2 based on the transmitted mail (step S104), and the registration update process of the shared address DB2 shown in FIG.

  Thus, in each of the mail server device 1 and the local terminal device 5, first, the range of the transmission date and time of the electronic mail to be processed is specified. Thereafter, the shared address DB2 is prepared by performing registration update processing to the shared address DB2 for each of the received mail and the transmitted mail.

[Details of registration update processing of shared address DB2]
Next, details of the registration update process to the shared address DB 2 performed in steps S103 and S104 shown in FIG. 4 will be described. Note that the processing performed in step S103 and step S104 in the flowchart shown in FIG. 4 differs in whether the processing target is a received mail or a transmitted mail, and there is a method for extracting address information of the other party between the received mail and the transmitted mail. Except for differences, the process is almost the same. Therefore, in the following, the processing performed in step S103 and step S104 shown in FIG. 4 will be described in common using the flowcharts shown in FIG. 5 and FIG. To do.

  5 and 6 are flowcharts for explaining details of the shared address DB registration update processing performed in steps S103 and S104 shown in FIG. FIGS. 7 and 8 are diagrams for explaining examples of display screens used in the processing of the flowcharts shown in FIGS. 5 and 6. First, the control units 12 and 52 extract, from the stored e-mails, e-mails whose transmission date and time belong to the transmission date and time range accepted in step S101 in FIG. The data is converted into format data (step S201).

In this case, when the processing of FIGS. 5 and 6 is executed in step S103 shown in FIG. 4, the processing target electronic mail is the received mail stored in the received mail storage units 14 and 54. In addition, when the processing of FIGS. 5 and 6 is executed in step S104 shown in FIG. 4, the processing target e-mail becomes the transmission mail stored in the transmission mail storage units 15 and 55.

  Next, under the control of the control units 12 and 52, the inquiry processing units 19a and 59a display the e-mails extracted and formatted in the HDDs 18 and 58 on the display units 17 and 57 one by one, and the shared address An inquiry is made as to whether or not to perform registration update processing in DB2 (step S202). And the control parts 12 and 52 receive the confirmation input with respect to the said inquiry through the operation parts 16 and 56 (step S203). FIG. 7A is a diagram for explaining an example of an inquiry display screen displayed on the display units 17 and 57 in step S202.

  As shown in FIG. 7A, on the display screen for inquiry, the sender (From), the destination (To), the transmission date and time (Date), the so-called header information of the subject and the e-mail text are displayed. Further, a window Wd for requesting confirmation input as to whether or not the electronic mail is to be processed is displayed at the upper right end portion of the inquiry display screen. Then, the user confirms the displayed e-mail information, and when registering the address information of the other party in the shared address DB2, the “Yes” button of the window Wd is displayed. An operation of selecting the “No” button is performed on the operation units 16 and 56. The displayed mail text can be scroll-displayed by performing a predetermined operation through the operation units 16 and 56 of the devices 1 and 5, and the entire text can be viewed.

  Then, the control units 12 and 52 determine whether or not the “Yes” button has been selected (step S204). If it is determined in the determination process in step S204 that the “Yes” button has not been selected, it is determined whether or not the “No” button has been selected (step S205). In the determination process of step S205, when it is determined that the “No” button has not been selected, the control units 12 and 52 repeat the process from step S203 and accept a selection input from the user. If it is determined in the determination process in step S205 that the “No” button has been selected, the control units 12 and 52 position the processing target as the next e-mail (step S206), and repeat the process from step S202.

  Further, it is assumed that it is determined that the “Yes” button has been selected in the determination process of step S204. In this case, under the control of the control units 12 and 52, the counterpart information extraction units 19b and 59b analyze the electronic mail to be processed and extract the destination address information (step S207). In step S207, when the processing target is a received mail, a so-called signature part included in the e-mail is analyzed to extract the name, company name, department, telephone number, address, and homepage URL of the other party. Further, the e-mail address of the transmission source is specified as the e-mail address of the other party.

  The signature is a summary of information such as the sender's name, contact information, and URL, which is added to the end of the e-mail. In the case of electronic mail, the sender's name, company name, and department are often described at the beginning or end of the body of the email. Therefore, when the processing target is an incoming mail, a description including the specific information of some possible recipients such as “Thank you for your support” in the body of the email. You can also find out and extract the partner's company, department, and name from the description.

  In addition, if the subject of processing is outgoing mail, find a description that includes specific information about some of the possible recipients, such as “XX Company △△ Department □□”, etc. in the body of the email. The previous company, department, and name can be extracted. In addition, when the processing target is outgoing mail, the destination electronic mail address is specified as the destination electronic mail address. Note that, regardless of whether the processing target is a received mail or a transmitted mail, information on the other party that could not be extracted can be supplemented after registration in the shared address DB2. For example, when the telephone number or facsimile number of the other party cannot be extracted, the information on the other party that has been found can be added to the address information of the other party registered in the shared address DB2.

  Next, under the control of the control units 12 and 52, the partner information presentation processing units 19c and 59c display a confirmation screen for the partner address information extracted in step S207 on the display units 17 and 57 (step S208). . And the control parts 12 and 52 receive the correction input from a user, etc. through the operation parts 16 and 56 (step S209). FIG. 7B is a diagram for describing an example of the confirmation screen displayed on the display units 17 and 57 in step S209. As shown in FIG. 7B, on the confirmation screen for the address information of the other party, the address information of the other party extracted in step S207 can be displayed, and the cursor CS can be positioned on the displayed item to be corrected.

  Also, the confirmation screen shown in FIG. 7B includes an “end” button for ending the registration update processing of the address information of the other party shown in FIGS. 5 and 6 and a registration update process of the displayed address information of the other party. An “OK” button for instructing to perform the operation is provided. In step S209, correction input for each item shown in FIG. 7B and operation input for the “end” button or “OK” button are accepted.

  Then, the control units 12 and 52 determine whether or not the “OK” button has been selected (step S210). If it is determined that the “OK” button has not been selected, whether or not the “End” button has been selected. Is determined (step S211). If it is determined in step S211 that the “end” button has not been selected, the control units 12 and 52 repeat the processing from step S209 so that the address information confirmation screen for the other party can be input. To do. If it is determined in the determination process in step S211 that the “end” button has been selected, a predetermined end process such as closing a data file in use is performed (step S212), and FIG. 5 and FIG. The process shown is terminated.

  If it is determined in step S210 that the “OK” button has been selected, the registration destination specifying unit 19d refers to the personnel information DB 3 through the LAN I / Fs 13 and 53 under the control of the control units 12 and 52, and the other party A process of specifying the registration destination (management department) of the shared address DB 2 for registering the address information is performed (step S213). In step S213, if the email to be processed is a received email, the registration destination is specified by referring to the affiliation history information in the personnel information DB 3 based on the transmission date and time of the email and the email address of the recipient. . In step S213, if the processing target e-mail is a transmission e-mail, the registration destination is determined by referring to the affiliation history information in the personnel information DB 3 based on the e-mail transmission date and time and the e-mail address of the transmission source. Identify. Of course, the names of the receiver and the sender may be considered.

  Next, under the control of the control units 12 and 52, the check processing units 19e and 59e function to check whether or not the address information of the registration target partner is already registered in the shared address DB2 (step S214). ). In the check processing in step S214, if at least “name” and “e-mail address” match, it is determined that they overlap. Thereafter, the process proceeds to the process of step S215 in FIG. 6, and the control units 12 and 52 determine whether or not the registration is duplicated based on the check result of step S214 (step S215).

  Assume that in the determination process of step S215, it is determined that duplication registration occurs when the address information of the other party to be processed is registered in the shared address DB2. In this case, the control units 12 and 52 display a processing content confirmation screen on the display units 17 and 57 and accept a confirmation input in order to confirm the processing content of the address information of the other party with the user (step S216). . FIG. 8 is a diagram for explaining an example of a confirmation screen for confirming with the user the processing content of the address information of the processing target partner in step S216. In the confirmation screen (FIG. 8) of the processing content, a message notifying that the address information of the processing target partner is duplicated, the address information (new address information) of the partner extracted this time, Address information registered in the shared address DB2 is displayed. Further, an “update” button, an “alias registration” button, and a “skip” button are displayed at the lower end of the confirmation screen (FIG. 8).

  The user confirms the content of the address information through the processing content confirmation screen shown in FIG. 8 and decides how to process the address information of the other party extracted this time. When the address information already registered in the shared address DB 2 is updated using the address information of the other party, the user selects the “Update” button. Further, when registering the address information of the destination as new address information by changing the “name”, the user selects the “register alias” button. If neither updating nor registration using the address information of the destination is performed, the user selects a “skip” button.

  Therefore, the control units 12 and 52 first determine whether or not the “update” button has been selected (step S217). Assume that it is determined in the determination process in step S217 that the “update” button has been selected. In this case, under the control of the control units 12 and 52, the address registration unit 19f uses the address information of the other party to be processed through the LAN I / Fs 13 and 53, and uses the shared address DB2 as the address information of the management department identified in step S213. The existing address information (duplicate address information) registered in is updated (step S218). In this case, duplicate address information can be specified by “department code and registration number” as described above. For example, as shown in FIG. 8, when the “affiliation” is different, the “affiliation” is rewritten from the “planning department” to the new “sales department”. Also, as shown in FIG. 8, when “URL” is found, “yyy.co.jp” is added to “URL”.

  Also, assume that it is determined in the determination process in step S217 that the “update” button is not selected. In this case, the control units 12 and 52 determine whether or not the “alias registration” button has been selected (step S219). When it is determined in the determination process in step S219 that the “alias registration” button has been selected, the control units 12 and 52 accept change input of “name” through the operation units 16 and 56 (step S220). In the process of step S220, not only “name” but also other information change input may be accepted. Then, under the control of the control units 12 and 52, the address registration units 19f and 59f function, and the address information of the other party after the “name” change is transmitted to the management department identified in step S212 through the LAN I / Fs 13 and 53. A process of registering in the shared address DB2 as address information is executed (step S221). In this case, a new “registration No.” is given to the address information to be registered. As a result, the “department code and registration number” becomes index information of the address information, and the address information can be uniquely specified, and can be deleted or changed.

  Further, it is assumed that it is determined that the registration is not duplicated in the determination process in step S215. In this case, those controlled by the control units 12 and 52 and the address registration units 19f and 59f function, and the address information of the other party extracted in step S207 is directly used as the address information of the management department specified in step S213. A process of registering in the shared address DB2 through / F13, 53 is executed (step S221). In this case, a new “registration No.” is given to the address information to be registered.

  After step S218 or after step S221, or when it is determined in step S219 that the “alias registration” button has not been selected, the process proceeds to step S222. Then, it is determined whether or not the current e-mail (the e-mail from which the address information of the other party is extracted) is the last e-mail extracted in step S201 (step S222). In the determination process of step S222, in order to determine that the e-mail to be processed is the last e-mail, a predetermined end process such as closing the data file in use is performed (step S223). The processes shown in FIGS. 5 and 6 are terminated. Further, in the determination process of step S222, in order to determine that the email to be processed is not the last email, the control units 12 and 52 position the processing target as the next email (step S224), The processing from step S202 shown in FIG. 5 is repeated.

  In this way, in each of the mail server device 1 and the local terminal device 5, the received and transmitted e-mails are stored, and the address information of the other party is extracted from them in a batch, and is classified by department. Registration and updating can be performed in the shared address DB 2 that manages address information. In addition, by using the personnel information DB 3 and taking into account personnel changes, the department that should manage the address information should be appropriately identified according to the recipient of the email and the affiliation of the sender in the email transmission date and time. Can do. Therefore, even if the stored electronic mail is a processing target, the address information can be appropriately registered and updated in the shared address DB2.

  In this embodiment, in step S201, all e-mails to which the transmission date / time belongs during the period instructed by the user are processed, but the present invention is not limited to this. The e-mail address is composed of a local part determined by the user and a domain name for specifying a mail server device on the Internet. For this reason, only e-mails having a domain name designated in advance can be processed. Further, only e-mails whose domain names include “.com” or “.co.jp” can be processed. In this way, it is possible to process only e-mails that meet a predetermined condition.

[Another example of registration update processing of shared address DB2]
In the case of the registration update processing of the shared address DB 2 described with reference to FIGS. 5 and 6, an inquiry about an electronic mail to be processed, confirmation of the extracted address information of the other party, and address information duplication of the other party Inquiry of processing contents was made to the user. However, it is also possible to automatically update the registration of the shared address DB2 of the address information of the other party without requiring user confirmation input or the like.

  FIG. 9 is a flowchart for explaining processing when the address information of the other party is registered and updated in the shared address DB 2 fully automatically. The processing shown in FIG. 9 is first executed by the control units 12 and 52 with the received mail as a processing target, and then executed with the outgoing mail as a processing target.

  In the case of this example, first, the control units 12 and 52 extract e-mails belonging to a predetermined period from the stored e-mails to the HDDs 18 and 58, and data in a predetermined format suitable for analysis. (Step S301). Here, the predetermined period is predetermined such as one day for the processing date, the past one week including the processing date, or the like. Of course, as described with reference to FIG. 4, the user may set in advance. And the process of this step S301 is performed similarly to the process of step S201 shown in FIG. Therefore, first, after performing the registration update process for the received mail stored in the received mail storage units 14 and 54, the transmitted mail stored in the transmitted mail storage units 15 and 55 is registered as the processing target. Update processing will be performed.

  Next, under the control of the control units 12 and 52, the counterpart information extraction units 19b and 59b analyze the electronic mail to be processed, and extract the destination address information (step S302). The process of step S302 is a process performed in the same manner as step S207 shown in FIG. Thereafter, under the control of the control units 12 and 52, the registration destination specifying unit 19d performs a process of specifying the registration destination (management department) of the shared address DB2 in which the address information of the other party is registered (step S303). The processing in step S303 is performed in the same manner as the processing in step S213 illustrated in FIG.

  That is, if the processing target e-mail is a received mail in step S303, the registration destination is determined by referring to the affiliation history information in the personnel information DB 3 based on the transmission date and time and the e-mail address of the e-mail. Identify. In step S303, if the processing target e-mail is a transmission e-mail, the registration destination is determined by referring to the affiliation history information in the personnel information DB 3 based on the e-mail transmission date and time and the e-mail address of the transmission source. Identify.

  Next, under the control of the control units 12 and 52, the check processing units 19e and 59e function to check whether or not the address information of the other party to be registered has already been registered in the shared address DB2 (step S304). ). The processing in step S304 is performed in the same manner as step S214 shown in FIG. Accordingly, in step S304, if at least “name” and “e-mail address” match, it is determined that they overlap. Thereafter, the control units 12 and 52 determine whether or not the registration is duplicated based on the check result in step S304 (step S305). The determination process in step S305 is a process performed in the same manner as step S215 illustrated in FIG.

  If it is determined in step S305 that the registration is not duplicated, the address information of the other party extracted in step S302 is directly registered in the shared address DB 2 as the address information of the management department specified in step S303. Processing is executed (step S306). The process in step S306 is performed in the same manner as the process in step S221 shown in FIG.

  If it is determined in the determination process of step S305 that the registration is duplicated, the control units 12 and 52 record the address information of the other party extracted in step S302 in the duplicate data file of the HDDs 18 and 58 (step S302). S307). In this step S307, the address information of the other party recorded in the duplicate data file is later presented to the user for confirmation, and when registration, update, or alias registration is instructed, sharing is performed according to those instructions. It becomes the object of registration update to the address DB2.

  After the processes in steps S306 and S307, the control units 12 and 52 determine that the e-mail that has been processed this time (the e-mail in which the address information of the other party is extracted) is the e-mail extracted in step S301. It is determined whether or not it is the last e-mail (step S308). The process in step S308 is performed similarly to the process in step S222 shown in FIG.

  Then, in the determination process of step S308, in order to determine that the e-mail to be processed is the last e-mail, a predetermined end process such as closing the data file in use is performed (step S309). Thereafter, the processing shown in FIG. 9 is terminated. Further, in the determination process of step S308, in order to determine that the email to be processed is not the last email, the control units 12 and 52 position the processing target as the next email (step S310), The processing from step S302 in FIG. 9 is repeated. Note that the processing in step S309 and step S310 is the same processing as the processing in step S223 and step S224 shown in FIG.

  In this way, the address information of the other party is extracted from the stored e-mail for each of incoming and outgoing e-mails without asking the user for confirmation, etc., and the address information is managed for each management department. Can be registered in the shared address DB2. In this case as well, the personnel information DB 3 is used and the department in which the address information should be managed is appropriately determined according to the affiliation of the e-mail recipient and the sender in the e-mail transmission date and time in consideration of personnel changes. Can be identified. Accordingly, even in the example described with reference to FIG. 9, the stored electronic mail can be processed, and address information can be appropriately registered and updated in the shared address DB2.

  In the process described with reference to FIG. 9 as well, in step S301, only e-mails that meet a predetermined condition are processed, for example, only e-mails having a preset domain name are processed. You can also

[Effect of the embodiment]
As described above, the address information of the other party is extracted using the stored received mail and transmitted mail as a processing target without performing the process each time an e-mail is received or transmitted. Then, the extracted address information is registered in the shared address DB 2 that manages the address information for each department. In this case, the extracted address information is associated with the receiver and the department to which the sender belongs at the e-mail transmission date and time. Identify the department that should be registered. Therefore, the address information of the other party can be registered in the shared address DB 2 as address information of an appropriate management department without being affected by personnel changes or the like. Therefore, the shared address DB2 does not need to be recreated due to the influence of personnel changes.

  It is also possible to select an e-mail to be registered, or to check and correct the extracted address information of the other party. In addition, when the address information of the other party is duplicated, processing according to the instruction to the user, such as whether to update the address information already registered in the shared address DB 2 or register with another name, may be performed. it can. Accordingly, the user can also finely control the destination to register the address information, the contents of the address information to be registered, the processing when the address information is duplicated, and the like.

  Further, it is possible to automate processing from extraction of the address information of the other party to registration update to the shared address DB 2 without bothering the user. In this case, the process for the address information of the other party that is the duplicate registration can be performed later according to a user instruction.

  Further, the extraction of the address information and the registration update process to the shared address DB2 can be performed at various timings. For example, the e-mail for the previous day can be processed as a processing target in the morning, or the e-mail for the previous week can be processed as a processing target on Monday. Of course, it is also possible to extract the address information from the stored electronic mail and update the registration in the shared address DB 2 at a predetermined cycle such as every 10 days, every 15 days, or every month.

  Through these, it is possible to easily and surely manage address information about various destinations in an organization such as a company and to prepare an easy-to-use shared address database without bothering the user as much as possible.

[Modifications, etc.]
There are various address book file formats. For example, CSV (comma delimited), LDIF (LDAP server), vCard (VCF file), Windows (registered trademark) address book file (Outlook Express address book, .Wab file), XML, TEXT, and various mobile phone formats are supported To do. Thereby, even if the shared address DB2 is created in any format, the address information can be appropriately registered and updated.

  In the above-described embodiment, the shared address DB 2 has been described as managing address information for each department. However, the present invention is not limited to this. It may be classified and managed according to the company (company and department) of the sender and receiver of the e-mail. That is, the shared address DB may be configured to classify (group) address information by department within the company, or may classify (group) address information by department of the other party.

  In the above-described embodiment, the e-mail to be processed is specified based on the transmission date and time, or the e-mail having a predetermined domain name is set as the process target. Matching emails were processed. However, it is not limited to this. Of course, only e-mails whose transmission date / time falls within the range designated by the user and meets a predetermined condition can be processed.

  For received mail, if the source email address has a predetermined domain name, and if the destination email address has a predetermined domain name in the case of outgoing mail, then unconditionally The address information of the other party can be registered in the shared address DB2. Therefore, there is no need to make an inquiry as to whether or not the electronic mail is to be processed. However, for incoming mail, if the source email address does not have a predetermined domain name, or if the destination email address does not have a predetermined domain name, For the electronic mail, the user is asked whether or not the address information of the other party is to be registered in the shared address DB2.

  In this way, address information of a partner that is always necessary for business can be surely registered in the shared address DB2. On the other hand, for a partner whose business is unclear, it is determined whether or not the user registers the address information of the partner in the shared address DB 2 each time. Can not be registered in the shared address DB2.

  In the embodiment described above, the extraction of the address information of the other party from the e-mail and the registration update processing of the extracted address information to the shared address DB can be performed by both the mail server device and the local terminal device. I did it. However, it is not limited to this. You may make it carry out only with any one apparatus. However, by making it possible to perform both in the mail server device and the local terminal device, for example, for any e-mail that remains in the mail server device without receiving any local terminal device, the address information The shared address DB can be registered.

  In the above-described embodiment, the local terminal device 5 has been described mainly as a personal computer. However, the present invention is not limited to this. For example, various communication devices that can perform communication processing by connecting to a LAN, such as an information terminal called a tablet-type terminal or a pad-type terminal, can be used as the local terminal device.

  Further, the processing shown in FIG. 4, FIG. 5 and FIG. 6 or FIG. 9 corresponds to the address information registration / updating method of the present invention. Further, a program for executing processing according to the flowcharts of FIGS. 4, 5, 6, or 9 is an address information registration / update program executed by the mail server device 1 or the local terminal device 5.

  Therefore, a program for executing the processing shown in FIG. 4, FIG. 5 and FIG. 6 or FIG. 9 is formed and installed in a mail server device or a local terminal device so that it can be executed in the device. Thus, the address information registration / updating apparatus of the present invention can be easily realized.

  DESCRIPTION OF SYMBOLS 1 ... Mail server apparatus, 2 ... Shared address DB, 3 ... Personnel information DB, 4 ... LAN, 5 ... Local terminal device, 11 ... Communication I / F, 12, 52 ... Control part, 13, 53 ... LAN I / F, 14, 54 ... received mail storage unit, 15, 55 ... transmitted mail storage unit, 16, 56 ... operation unit, 17, 57 ... display unit, 18, 58 ... HDD, 19a, 59a ... inquiry processing unit, 19b, 59b ... Destination information extraction unit, 19c, 59c ... Destination information presentation processing unit, 19d, 59d ... Registration destination specifying unit, 19e, 59e ... Check processing unit, 19f, 59f ... Address registration unit

Claims (8)

A shared address database that manages the address information of email recipients by department,
Affiliation information storage means for storing affiliation history information including identification information of all employees, affiliation period, and department,
E-mail extracting means for extracting e-mail whose transmission date / time is within the range of the input / predetermined transmission date / time among the stored received e-mails ;
The email extractor means analyzes the information contained in the e-mail received extracted by the address information extraction means for extracting the destination address information to be registered in the address book,
Referring to the affiliation history information of the membership information storage means based on the received the e-mail recipient's identification information and the transmission time of the electronic mail to be analyzed is its own user, the transmission date and time the recipient Identifying means for identifying the department to which the user belonged as the registration destination of the address information of the other party extracted by the address information extracting means ;
And characterized in that it comprises with respect to the shared address database, the address information the destination address information extracted by the extraction means, and registering means for registering as the address information of the department that is specified by the specifying means Address information registration / updating device. The address information registration / updating device according to claim 1,
The e-mail extracting means extracts e-mails whose transmission date / time is input or belonging to a predetermined transmission date / time range from among the e-mails transmitted to the stored destination,
The address information extraction unit analyzes the information described in the transmitted e-mail extracted by the e-mail extraction unit, and extracts address information of a destination to be registered in the address book,
The specifying means refers to the affiliation history information of the affiliation information storage means based on the identification information of the sender of the transmitted e-mail that is the user and the transmission date and time of the e-mail to be analyzed. An address information registration / updating apparatus that identifies a department to which the sender belongs at the transmission date and time as a registration destination of the address information of the destination extracted by the address information extraction unit . The address information registration / updating device according to claim 1 or 2 ,
For all of the electronic mail extracted by the mail extraction device, or, for the e-mail that meets the preset condition, query inquiring whether to registered Previous SL shared address database processing unit When,
Accepting means for accepting confirmation input for the inquiry by the inquiry means;
When the confirmation input received through the receiving means is an instruction for registration in the shared address database , the previous address information extracting means, the specifying means, and the registering means are operated to extract the e-mail. An address information registration / updating apparatus comprising: control means for performing control so as to register address information of a destination extracted from the e-mail extracted by the means. An address information registration / updating device according to claim 1 , claim 2, or claim 3 ,
Presenting processing means for presenting to the user the address information of the other party extracted by the address information extracting means;
Correction accepting means for accepting correction input for the address information of the other party presented through the presentation processing means ,
The addressing information registration / updating apparatus, wherein the registering means registers address information of a destination reflecting the correction input in the shared address database. An address information registration / updating device according to any one of claims 1, 2 , 3, or 4 ,
Before registering the address information of the other party extracted by the address information extracting means in the shared address database, a duplicate registration is checked, and if it is detected that it is a duplicate registration, a duplicate registration is made. A check processing means for informing that and requesting confirmation of processing contents;
Instruction accepting means for accepting an instruction input for the processing content requested to be confirmed through the check processing means ;
An address information registration / updating apparatus comprising: an overlapping time control unit that controls each unit so as to perform processing according to the instruction input received through the instruction input receiving unit . An address information registration / updating device according to any one of claims 1, 2, 3 , 4, or 5 ,
The shared address database can be classified according to the affiliation of the other party. Addresses that can access the shared address database that manages the address information of email recipients by department, and the membership information storage means that stores and stores membership history information including identification information, membership period, and department of all employees An address information registration update method used in an information registration update device,
An e-mail extracting step in which the e-mail extracting means extracts e-mails whose transmission date / time is input or belonging to a predetermined transmission date / time range among the stored received e-mails ;
Address information extraction means, said electronic mail extraction process by analyzing the information described in the e-mail received extracted in the address information extraction step of extracting destination address information to be registered in the address book,
The specific means, referring to the affiliation history information of the membership information storage means based on the transmission date of the e-mail to be analyzed and the identity of the recipient of the e-mail is its own user, the recipient said transmission A specific step of identifying the department to which the date belongs as the registration destination of the address information of the destination extracted in the address information extraction step ;
Registration means, to said shared address database, to have a registration step of the address information extracted the destination address information in the extraction step, is registered as the address information of the department specified in the specifying step A method of updating and registering address information as a feature. Addresses that can access the shared address database that manages the address information of email recipients by department, and the membership information storage means that stores and stores membership history information including identification information, membership period, and department of all employees An address information registration / update program executed by a computer installed in the information registration / update device ,
An e-mail extracting step, wherein e-mail extracting means extracts e-mails whose transmission date / time is input or belonging to a predetermined transmission date / time range among the stored received e-mails ;
Address information extraction means, the electronic mail extracted by analyzing the information described in the e-mail received extracted in step, and the address information extraction step of extracting the destination address information to be registered in the address book,
The specifying means refers to the affiliation history information in the affiliation information storage means based on the identification information of the e-mail recipient who is the user and the transmission date and time of the e-mail to be analyzed, and the recipient sends the transmission A specific step of identifying the department to which the person belongs at the date and time as a registration destination of the address information of the destination extracted in the address information extraction step ;
A registration unit for registering, with respect to the shared address database, the address information of the other party extracted in the address information extraction step as the address information of the belonging department identified in the identifying step; An address information registration update program characterized by

Images