JPS58207131A - Mail address controlling system - Google Patents

Abstract

PURPOSE:To have the correspondence between an address designated by a user and a receiving user and at the same time to avoid an effect to the document communication processing of other users, by designating freely the address in a nickname by the user and through a conversation process. CONSTITUTION:A user of a terminal 2-1 actuates a conversation processing part 5-1 with application of an ON command. When the document communication is carried out, a transmission command is applied to actuate a transmission command processing part 7. The transmission command designates a mailbox file 15 which stores previously document data to be communicated and is registered to a file control information region 13-1 as a reserved file. At the same time, an address registered in a user address controlling table 16-1 with a nickname decided previously and freely. A transmission command processing part 7 actuates a sharing permission processing part 18 and sets the sharing permission infomration of the file 15 after setting a sharing information region 20. Then the information on the file name of the file 15 and the address of the table 16-1 is designated and a processing part 6 is entrusted for this information.

Description

DETAILED DESCRIPTION OF THE INVENTION (1) Technical field of the invention The present invention is a document communication processing method in a data processing system, in which the destination of document data can be registered and modified freely and interactively while maintaining confidentiality. The present invention relates to a mail destination management control method.

(2) Background and problems For example, data processing is logically connected to a data processing device by inputting a session start command from a terminal, and allows users to receive conversation processing services etc. through time sharing. In the system,
For example, when a user of a certain terminal sends a message to users of multiple other terminals via a data processing device,
Since the user of the terminal on the receiving side is not always ready to receive, conventionally, mail index files have been used for processing as described below.

FIG. 1 shows an example of a conventional document communication processing method.

In the figure, 1 is a data processing device, 2-1 to 2-3 are terminals, 3-1 to 3-3 are user spaces, 4 is system space, 5-1 to 5-3 are conversation processing units, and 6 is a multiplexer. Message processing unit, 7 is a sending command processing unit, 8 is a destination management table, 9 is a mail management table, 10-1, 10-2
1 is a receiving command processing section; 11 is a mailbox file creation processing section; 12 is a maildex file reading processing section; 13-1 to 13-4 are file management information areas;
4 represents a document file, and 15-1 to 15-3 represent mailbox files.

For example, when the user of the terminal 2-1 wants to receive a conversation processing service provided by the data processing device 1, he inputs a session start command (ON command). The ON command opens the user space 3-1 and activates the conversation processing section 5-1.

After that, you can input desired conversation processing commands one after another and receive services interactively.

In particular, when sending a document to a user of another terminal 2-2, 2-3, etc., the file name of the document file 14 in which the document to be sent is stored and the name of the sending destination Specify and submit the send command. The transmission command processing unit 7 is activated by inputting the transmission command.

The transmission command processing unit 7 transfers the document file 14 to a file management information area 13- in which file directories and the like are stored.
1, the read document data and destination name are specified, and the multiple message processing section 6 is requested to process the document communication. The multiple message processing unit 6 operates as a system resident task, and first starts the mailbox file creation processing unit 11 in response to a document transmission request. The mailbox file creation processing unit 11 creates a mailbox file 15-1 as a temporary file, stores the document data requested to be sent in the mailbox file 15-1, and also stores the file belonging to the multiplex message processing unit 6. Register the access information, etc. of the mailbox file 15-1 in the management information area 13-4. Also, refer to the destination management table 8 using the destination name as a key, determine the receiving terminal and user, and Transmission/reception management information, such as a list of recipients, is set in 9.

If the receiving terminal has an open session, a message indicating that the document data has been sent, that is, an email, is immediately output to that terminal, but if the receiving terminal does not have a session open, the ON command must be sent from the receiving terminal. When you put it in,
You will be notified that an email has been received.

For example, assume that the user of the receiving terminal 2-2 inputs an ON command to activate the conversation processing unit 5-2, and receives the above-mentioned message to the effect that the email request has been received. The user can input a receive command and receive the document data that is the contents of the mailbox file 15-1. In particular, in the received command, it is also possible to specify that the document data be cataloged as its own file. The reception command processing section 10-1 is activated by inputting the reception command, and the reception command processing section 10-1 requests the multiple message processing section 6 to process. and mailbox file 15-1 based on the access information in file management information area 13-4.
The contents are read out and transferred to the conversation processing section 5-2. Additionally, if a catalog is specified, a mailbox file 15-2 storing the contents is created as a storage file, and the file management information area 13 of the user is
-Register in 2.

The same applies to the other receiving terminal 2-3. The multiple message processing unit 6 deletes the information of the recipients whose reception has been completed from the recipient list of the mail management table 9, and when the reception is completed for all recipients, the mailbox file 15-1 is deleted.
Erase.

In the conventional method described above, the destination management table 8 is shared by all users in the system, and the destination name specified by the user in document communication is directly assigned to the internal user ID defined for processing within the system. It was made to correspond to a brush. Therefore, it was necessary to perform batch operations after the general service was completed. If a user can arbitrarily modify it through conversation processing, it would affect other users, and the user would have to be aware of the user identifier used for internal processing of the system. However, changes in internal processing may cause unfavorable compatibility problems. Furthermore, since the internal user identifier is general binary data, it is difficult to input it manually from a terminal as a normal character code, and even if conversion rules were established, there would be confusion.

(3) Purpose of the Invention The present invention aims to solve the above-mentioned problems by allowing a user to arbitrarily specify a destination name using a nickname through conversation processing, and to associate the destination name with the receiving user. The purpose is to ensure that the document communication processing of other users is not affected.

(4) Structure of the Invention In order to achieve the above object, the mail destination management control system of the present invention includes a conversation processing unit that is activated by a processing request from each terminal, and a multiple message processing unit that processes document communication between each terminal. In a document communication processing method in which document data is sent using a mail index file, a system destination management file is provided that associates an internal user identifier for identifying a receiving user with a destination number. , a user destination management file that associates an arbitrary destination name specified by the sending user as the destination of the document data with the one or more destination numbers, and the multiple message processing unit When transmitting data, the transmission destination is determined by matching the user destination management file with the system destination management file, and the user destination management file can be modified by the conversation processing section. It is characterized by

(5) Examples of the invention This will be explained below with reference to the drawings.

FIG. 2 shows the configuration of an embodiment of the present invention. In the figure, code 1.
2-1 to 2-3.3-1 to 3-3.4.5-1
or 5-3.6.7, 9.10-1°10'-2,
13-1 to 13-3 correspond to FIG. 1, 16-1 to 16-3 are user destination management tables, 17 is a system destination management table, and 18 is a shared permission (PERMIT) table.
) processing unit, 19-1 and 19-2 are shared declaration (5HA
RE) processing unit, addition is the shared information area, 21 is the destination correspondence processing unit, 22 is the reception confirmation processing unit, and the edict is the address correction processing unit 2. The user of the terminal 2-1 uses FIG. As in the case of the conventional method described above, the conversation processing unit 5-1 is activated by inputting the ON command. When attempting to perform document communication with the user 6 of another terminal, a send command is input to start the send command processing unit 7, but in the send command, the document data to be communicated is stored in advance. The mailbox file 15 registered as a save file is specified in the file management information area 13-1. Further, a destination name arbitrarily determined in advance and registered in the user destination management table 16-1 as a nickname is specified.

The sending command processing unit 7 starts the sharing permission processing unit 18 and sends the file name and builf held by the sending user.
In the file management information area 13-1 where IJ etc. are stored,
A shared information area group is established and shared permission information for the mail index file 15 to be transmitted is set. Of course, this sharing permission is granted only to the communication partner, and is not granted to other general users. Next, information regarding the file name of the mailbox file 15 and the destination name of the user destination management table 16-1 is specified, and processing is requested to the multiple message processing section 6.

The multiple message processing section 6 first calls the destination correspondence processing section 21, determines the receiving terminal, creates a recipient list, and registers it in the mail management table 9.

The user destination management table 16-1 and the system destination management table 17 related to the above processing are, for example, nicknames that can be arbitrarily determined by the user;
Several destination numbers are associated with each destination name. This user destination management table 16-1 is
The destination modification command allows the user to arbitrarily modify the destination by calling the destination modification processing section shown in FIG. On the other hand, the system destination management table 17 associates the destination number with a user identifier used for internal processing of the system. This system destination management table 17 is updated by patch processing when a new terminal is installed, a user joins, etc. Updates can only be performed by system administrators. The user destination management table 16-1 and the system destination management table 17 are associated with each other by a destination number.

Once the destination is determined, the multiple message processing section 6 outputs a message with mail to the terminal that is currently opening a session for that destination. Further, a terminal that has not opened a session is notified when an ON command is input from that terminal.

For example, when the user of the terminal 2-2 inputs an ON command to activate the conversation processing section 5-2 and receives the notification that the mail is available, the user inputs a receive command. The reception command processing section 10-1 is started by inputting the reception command.In order to receive the document data, the reception command processing section 10-1 first specifies the notified sender name and file name, and then executes the shared declaration processing section 19. -1 is called. The shared declaration processing unit 19-1 stores the other party's file management information area 13-
Referring to the shared information area No. 1, it is checked whether the user in question is permitted to share the mail index file 15. If sharing permission has been granted and you have confirmed that you are the user, you can import the information about the maildex file 15 in the file management information area 13-1 to your own file management information area 13-2, or □ File management. By setting a pointer to the information area 13-1, the conversation processing unit 5-2 can directly read the mail index file 15 owned by the sender. In this way, the email will be saved as a file 15.
When the document data is received, the reception confirmation processing section 4 of the multiple message processing section 6 is notified of the receipt. The reception confirmation processing section deletes information regarding the user of the terminal 2-2 from the recipient list of the mail management table 9. The same applies to the other receiving terminal 2-3. However, even if all recipients in the recipient list in the mail management table 9 have received the mail, the multiple message processing section 6 itself does not delete the mail file 15. This is because the mailbox file 15 is a saved file of the user of the terminal 2-1.

It is up to the user of the terminal 2-1, who is the owner, to decide whether to delete this mailbox file 15 or not.
When deleting, it is necessary to confirm that all recipients have received it. This confirmation requires communication with the multiple message processing section 6, and requires reference to the mail management table 9. Therefore, mailbox file 1
The erasure timing 5 is when the user of the terminal 2-1 inputs the next new transmission command or reception command. That is, since communication is performed between the conversation processing section 5-1 and the multiple message processing section 6 in processing the send command or the reception command r, the conversation processing section 5-1 obtains information about the reception status of the mail management table 9. and delete the mailbox file 15 as necessary. In other words, an opportunity is given to erase the previously created mailbox file 15 when a send command or a receive command is input.

As mentioned above, conventional destination management tables are separated into a user destination management table provided for each user and a system destination management table that exists only once in the system. Since only the information of a certain destination name and a destination number uniquely determined by the system administrator in advance is stored, each user can interactively use the destination correction processing section in his or her user destination management table at any time. You can modify it by starting it, and even if you modify it, it will not affect other users. Note that each user destination management table and system destination management table are registered as a user destination management file and a system destination management file, respectively, on, for example, a magnetic disk device, and are recalled from memory as necessary. (6) As described in detail, according to the present invention, each user can arbitrarily change and register the destination of document communication, improving operability and serviceability. It also increases compatibility and flexibility with respect to system changes.

[Brief explanation of drawings]

FIG. 1 shows an example of a conventional document communication processing system, FIG. 2 shows the configuration of an embodiment of the present invention, and FIG. 3 shows a related diagram of a user destination management table and a system destination management table. In the figure, 1 is a data processing device, 2-1 to 2-3 are terminals, 3-1 to 3-3 are user spaces, 4 is system space, 5-1 to 5-3 are conversation processing units, and 6 is a multiplexer. Message processing unit, 7 is a sending command processing unit, 8 is a destination management table, 9 is a mail management table, 10-1 and 10-
2 is a received command processing unit, 13-1 to 13-4 are file management information areas, 15 is a mailbox file, 1
6-1 to 16-3 are user destination management tables, 17
18 is a system destination management table, 18 is a shared permission processing unit,
19-1 and 19-2 represent a shared declaration processing unit, 19-1 and 19-2 represent a shared information area, and 19-2 represent a destination modification processing unit. Patent applicant: Fujitsu Limited (1 other person) Representative patent attorney: Mori 1) Hiroshi (1 other person): 1・□,,.

Claims (1)

[Claims] A document communication system that is equipped with a conversation processing section that is activated by a processing request from each terminal, and a multiple message processing section that processes document communication between each terminal, and that sends document data using a mailbox file. In the processing method,
In addition to providing a system destination management file that associates an internal user identifier that identifies a receiving user with a destination number, the system also provides a system destination management file that associates an internal user identifier that identifies a receiving user with a destination number, as well as an arbitrary destination name specified by the sending user as the destination of the document data mentioned above and the above 1. We still have a user destination management file that associates multiple destination numbers,
The multiple message processing unit is configured to determine the destination by matching the user destination management file and the system destination management file when transmitting the document data, and the user destination management file is configured to determine the destination by matching the user destination management file with the system destination management file. A mail destination management control method characterized in that it can be modified by a processing section.