JPS58207130A - Shared processing system of mailbox file - Google Patents

Abstract

PURPOSE:To save a mailbox file while securing the protection of secrecy among users, by producing the mailbox file as a file for users at the transmitter side and at the same time giving permission to the users at the receiver side to share the mailbox file. 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 with the user of another terminal, 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 registers the data to a file control information region 13-1 as a reserved file. The part 7 actuates a sharing permission processing part 18 and sets a sharing information region 20 at the region 13-1 to set the sharing permission information of the file 15 to be transmitted. Then the information on the file name of the file 15 and the address of a user address controlling table 16-1, and a processing request is given to a multiplex message processing part 6.

Description

DETAILED DESCRIPTION OF THE INVENTION (1) Technical Field of the Invention The present invention is directed to a data processing system in which a mailbox file used for document communication is shared between a sending side and a receiving party. By doing so, it is possible to create a mail-dex file sharing processing method that makes effective use of the file area.

(2) Background and problems An example is that by inputting a session start command from a terminal, it is logically connected to a data processing device, allowing users to receive time sharing, conversation processing services, etc. In data processing systems,
For example, a gift that sends a message from a user of one terminal to users of multiple other terminals via a data processing device,
Since users of terminals with RX@11I+'* are not always able to receive RX@JUNKA, conventionally, mailbox files have been used to perform the following disconnection process.

Figure 1 shows an example of the conventional Bunno communication processing system.
is Chitatami B Risousui, 2-1 or 2-3t, i or 1
floor, 3-1 to 3-3 are user spaces, 4 is system space, 5-1 to 5-3 are conversation processing units, 6 is a multiple 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 mailbox file reading processing section, 1.3-1 to 13-4 are file management information areas,
Reference numeral 14 indicates a document file, and 15-1 to 15-3 indicate mail index files.A user of the terminal 2-1 may, for example, issue a gift, a session start command ( ON command) Fully input. The ON command causes the user space 3-1 to be added and the conversation processing unit 5-1 to be activated.

After that, you can input the desired conversation processing commands one after another and send some kind of text to the user at 7 terminals 2-2.2-3.
f To send, specify the file name of the document file 14 that stores the document to be sent and the name of the destination to send, and enter a send command. By inputting the transmission command, the transmission command processing section 7 can be activated.

Transmission command processing unit 7i-I document file 14 is stored in file examination information area 1 in which file directories, etc. are stored.
3-1, and requests the multiple message processing section 6 to process the document communication by specifying the transmitted document data and the destination name. Multiple message processing @ 6 u
It operates as a system-resident task, and first starts the mailbox file creation processing section 11 in response to a request from the public. The mailbox file creation processing unit 11 creates a maildex file 15-1 as a temporary file, stores the text data requested to be sent in the mailbox file 15-1, and sends it to the multiple message processing unit 6. File management information &13-4
Then, the access information of the mailbox file 15-1 is retrieved. Still, refer to the destination inquiry table 8 using the destination name as a key, determine the destination and user, and set sending/receiving management information, for example, a list of recipients, in the mail management table 9 - the receiving terminal establishes a session. If it's open,
A message indicating that the document data was sent, that is, a 7I-rule, is immediately output to that terminal, but if the receiving terminal does not have a session open, when the ON command is input from that receiving terminal, a message is output to that terminal. A notification will be sent to that effect.

For example, assume that the user of the receiving terminal 2-2 inputs an ON command to activate the conversation processing section 5-2, and receives the message indicating that there is a mail. 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 receive command, it is also possible to specify that the data is to be cataloged as its own file.
1 Received command processing unit 10-I Lj: Depends on the multiple message processing unit 6, L! i! The unit 6 starts the mailbox file read processing unit 12 and reads the file management information area 1.
Based on the access information 3-4, the content of the mailbox file 15-1 is extracted and the content is sent to the conversation processing unit 5.
Transfer to -2. 1, if a catalog is specified,
A mailbox file 15-2 storing the contents is created as a save file and registered in the file management/information area 13-2 of the user.

The same applies to the other receiving terminal 2-3. The multiple message processing unit 6 removes the information of the recipients whose reception has been completed from the recipient list of the email management table 9, and when the reception has been completed for all recipients, the mail dex file 15 is saved.
According to the above conventional method of erasing the mailbox file 15-1';
Because it is created as a temporary file, as the number of email users increases, the file capacity of the entire system may become insufficient.
Furthermore, since the grand prize document data is exchanged between the conversation processing section and the multiple message processing section, processing efficiency is poor, and synchronization between the conversation processing section and the multiple message processing section cannot be achieved when a failure occurs. There were problems such as not being able to guarantee transmission and reception. However, in order to solve the above problems, it is necessary to completely maintain #reservation between users, and the conversation processing section of the receiving terminal must always be able to communicate with the system at the time of transmission. It is necessary to take into account that there is no guarantee that the

(3) Purpose of the Invention The present invention aims to solve the above-mentioned problems and to reduce the number of files and improve processing efficiency while guaranteeing confidentiality between users.

(4) Structure of the Invention In order to achieve the above object, the mailbox file sharing processing method of the present invention includes a conversation processing unit that is activated by a processing request from each terminal, and processes text communication between each terminal. In the Bunryo communication processing method, which is equipped with a multiple message processing section and is configured to send document data using a mailbox file, the above mailbox file is created as a file for one user on the sending side, and also on the receiving side. The configuration is configured to allow the user to share the mailbox file, and the conversation processing unit of the receiving user makes a sharing declaration for the mailbox file, refers to the mailbox file, and processes the document data. (5) Embodiments of the Invention A description will be given below with reference to the drawings.

Figure 2 shows the configuration of an embodiment of the present invention.
, 2-1 to 2-3.3-1 to 3-3.4.5-
1 to 5-3.6.7.9.10-1.10-2.1
3-1 to 13-3 correspond to FIG. 1, 16-1 to 16-3 are user destination transaction tables, 17 is a system destination table, and 18 is a shared permission (PERMIT) table.
) processing section, 19-1 and 19-2 are shared declaration (5H
20 is a shared information area, 21 is a destination correspondence processing section, 22 is a reception confirmation processing section, and 23 is a destination modification processing section.

The primary user of the terminal 2-1 activates the conversation processing section 5-1 by inputting an ON command, as in the case of the conventional method explained using FIG. When attempting to perform document communication with a user of another terminal, a send command is input to start the send command processing section 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 activates the sharing permission processing unit 18, and creates a shared information area 20 in the file management information area 13-1 in which file names, directories, etc. held by the sending user are stored. Set sharing permission information for the mailbox file 15 to be sent. 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 designated, and processing is left 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 related to the above processing. 1 and the system destination management table 17 have a relationship as shown in FIG. 3, for example. In FIG. 3, destination names X, Y, and Z in the user management table 16-1.

... are nicknames that can be arbitrarily determined by the user, and several destination numbers are associated with each destination name. This user destination management table 1
6-1 can be arbitrarily modified by the user by calling the destination modification processing section 23 shown in FIG. 2 using a destination modification command. On the other hand, system destination management table 17
The system destination management table 17 associates the above destination number with a user identifier used for internal processing of the system. Updated by processing. Recommendations can only be executed by the system administrator.Z7 The user advantage/loss management table 16-1 and the system destination management table 17 are associated with each other by destination number.

Once the destination is determined, the multiple message processing section 6 outputs a message containing mail to the terminal that is currently opening a session for that destination. Also, 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 terminal 2-2 inputs an ON command and starts the conversation processing section 5-2. , when receiving the notification that there is a mail, inputs a receive command. The received command processing unit 1O-1 is activated by inputting the received command. In order to receive document data, the reception command processing unit 1O-1 first specifies the notified sender name and file name and calls the shared declaration processing unit 19-1. The shared declaration processing unit 19-1 stores the other party's file management information area 13-
1 and checks whether the user is permitted to share the mailbox file 15. If it is confirmed that sharing permission has been granted, the information regarding the maildex file 15 in the file management information area 13-1 can be imported into the own file management information area 13-2, or the information about the maildex file 15 in the file management information area 13-1 can be imported By setting a pointer to 1, the conversation processing unit 5-2 can directly read the mailbox file 15 owned by the sender. When the document data in the mail index file 15 is received in this way, the reception confirmation processing section 22 of the multiple message processing section 6
Notify of receipt. Received! The first recognition processing unit 22 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 email management table 9 have received the email,
The multiple message processing section 6 itself does not delete the mailbox 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 or not to delete this mail index file 15.
When deleting a message, 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 a send command or a reception command, the conversation processing section 5-1 can obtain information about the reception status of the mail management table 9. , delete the mail index file 15 as required. In other words, when a send command or a receive command is input, an opportunity is given to delete the previously created mailbox file 15 - As described above, the mailbox file 15 owned by the sender is shared by the recipients. Document communication is done by this.

(6) As described in detail, according to the present invention, by sharing a mailbox file, it is possible to utilize the file area M-efficiently, and the one-time limitations on the entire system can be alleviated. In addition, processing vehicles will also rise. In particular, since the mailbox file is created as a save file for the sender, even in the event of a failure, it can be resent as is after recovery.

[Brief explanation of the drawing]

FIG. 1 shows an example of a conventional document transfer 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 the data processing unit k, 2-1 to 2-3 +a
3-1 to 3-3 are user space, 4 is system space, 5-1 to 5-3 are conversation processing units, 6 is multiple message processing unit, 7 is sending command processing unit, 8 is destination management table , 9 is a mail management table, 10-1 and 1
O-2 is a receiver command processing unit, 13-1 to 13-4
is a file management information area, 15 is a mailbox file, 16-1 to 16-3 are Rikaro address management tables,
17 is a system destination V management table, 18 is a shared permission processing section, 19-1 and 19-2 are common room 1 processing sections, 20 is a shared information area, and 18 is a destination 4-main processing section. Patent applicant: Fujitsu Co., Ltd. (14 patent attorneys: Mori 1) Hiroshi (1 other person)

Claims (1)

[Claims] A document 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 allows document data to be sent by email using a tx file. In the communication processing method,
The above-mentioned mailbox file is created as a file of the sending user, and the receiving-side user is configured to be allowed to share the above-mentioned mailbox file, and the conversation processing unit of the above-mentioned receiving user is configured to create the above-mentioned mailbox file as a file of the sending user. A maildex file sharing processing method in which a percentage is determined by making a file sharing declaration and referring to the above mailbox file to receive document data.