JPH022754A - Mail accumulation processing system - Google Patents

Abstract

PURPOSE:To reduce the capacity of a mail box file by storing each mail in the box of the mail box file after attaching a mail classification identifier, and reading out a mail in the box which coincides with a corresponding mail classification identifier. CONSTITUTION:A user ID and the mail classification identifier(mail classification ID) with respect to the user are set on a user managing information file 16 in a mail accumulation processor 100. The correspondence of the managing information file 16 with the mail box file 18 is obtained by a correspondence table file 17, and the mail box file 18 is provided with a mail box which corresponds to the mail classification ID in one to one. The mail is classified by mail classification, and is stored in the mail box after attaching the mail classification ID. The readout of the mail is performed by reading out the mail in the mail box which coincides with the corresponding mail classification ID. In such a way, it is possible to reduce the capacity of the mail box file by accumulating the mail efficiently.

Description

[Detailed Description of the Invention] [Field of Industrial Application] The present invention stores mail (information) in a mailbox,
A center-end mailbox that delivers the mail to multiple users or reads it out to multiple users [prior art] Mail (information) is stored in a mailbox, and the mail is delivered to multiple users or read by multiple users. The following two are typical mailbox communication systems read by users.
is proposed.

(i) A circular mailbox communication system that stores mail in mailboxes of multiple destinations specified when mail is issued, and delivers or reads the mail.

(11) Select the regulations for the information the user wants in advance.
Selective Dlsse-I (Selective Dlsse-I) stores emails in a mailbox and delivers them when information that meets the conditions of that information type occurs.
Illination of lnrormation
) type mailbox communication system.

In these conventional mailbox communication systems, mails are loaded into mailboxes using the method described below.

FIG. 9 shows a conventional mailbox file configuration example 1, and FIG. 10 shows another conventional mailbox file configuration example 2. In FIG. 9, 1 is a mailbox file, 2 is a mailbox, and 3 is a usage 810. and 4 represent the mail storage area.

As shown in FIG. 9, the mailbox file 1 has a plurality of mailboxes 2. Each mailbox 2 is
It consists of a user ID 3 and a plurality of mail storage areas 4. The plurality of email storage areas 4 can store emails related to the user ID set as the user ID 3. Also, in Figure 10, 5
is a mailbox file, 6 is an individual box area, 7 is a shared box area, 8 is an individual box, and 9 is a shared box.

10 represents the usage ff1ID, 11 represents the pointer, 12 represents the common box number, and 13 represents the mail storage area.

As shown in the figure, the mailbox file 5 is divided into an individual mailbox [6] and a shared box area 7. The individual box area 6 covers a plurality of individual boxes 8. Each individual box 8 consists of a user 61D10 and a plurality of pointers 11. Pointer 11 points to shared box area 7
The address of one of the shared bosses 9 in the office. Shared box 9 has shared box number 12 and mail storage area 1.
It consists of 3.

When performing the above-mentioned circular mailbox communication (i) using mailbox file configuration example 1 in FIG. 9, mailbox 2 of mailbox file 1 is
1 to 1, and the user ID of that user is the user ID.
Set it to 3 in advance. When receiving a broadcast email, the usage f510 and usage e31 of the user specified as the destination
One free mail storage area 4 of the mailbox 2 with the matching contents of D3 is secured, and the mail is stored there. If there are any remaining destinations, secure one free mail storage area 4 of the mailbox 2 whose contents match the user ID 3 and the usage '51D of the user specified as the remaining first destination, and send the mail there. Store. Thereafter, this process is repeated for each destination and then delivered or read.

On the other hand, when carrying out the above-mentioned (i) reminder mail communication using the mailbox file configuration example 2 shown in FIG. 10, the mailbox file 5 is composed of an individual box area 6 and a common box area 7. Furthermore, the individual box area 6 is made up of individual boxes 8 that are set in one-to-one correspondence with users, and the common box area 7 is made up of a common box 9 that stores mail.

A serial number is given to the common box 9, and that number is set in the common box number 12 in advance. Also, use the user ID associated with individual box 8
Set in advance.

If you receive a 4-report email, please use an empty public box 9.
Secure one, store the email itself in that email storage area 13, and set the shared box number 12 of the shared box 9 where it was stored.
The content of is set in one empty space in the pointer 11 of the individual box 8 where the user ID of the first destination matches the user ID 10. If there are any remaining destinations, one space is reserved for the pointer 11 of the individual box 8 whose contents match the remaining first user rD and the contents of the used fileD10, and the shared box number of the shared box 9 that previously stored the mail is set. Set the contents of 12. Thereafter, this process is repeated until there are no more destinations left for delivery or reading.

Furthermore, when using the mailbox file configuration example 1 shown in FIG. 9 to perform the SDI type seal box communication described in (ii) above, one mailbox 2 of the mailbox file 1 is secured for each user. Then, the usage flilliD of that user is set to user ID3. When information matching a certain information selection condition occurs and there is a user with the number of stages who wants that information, the mailbox 2 that matches the user ID of the first user and the contents of mailbox 2 usage gLD3 is stored. Secure one free space in area 4 and store the information itself there. If there are remaining users, secure one free space in the mail storage area 4 of mailbox 2 that matches the user IO of the remaining first user and the contents of user ID 3 of mailbox 2, and do the same there. Stores information about. From then on, this process was repeated until there were no more users left, and the deliveries were made.

On the other hand, when performing the SDI'F mailbox communication described in (ii) above using mailbox file configuration example 2 shown in FIG. Mail was delivered using the same procedure as type mailbox communication.

[Problem to be solved by the invention]

However, both of the conventional mailbox file configuration examples 1 and 2 have the following problems.

When using the above mailbox file configuration example 1 for circular mailbox communication and SDI type seal box communication, in order for the same mail to be delivered to multiple users or read by multiple users, the same Since it is necessary to store e-mails in mailbox 2 for each of multiple users, there is a problem that e-mails cannot be stored efficiently and mailbox file 1, which has a very large capacity, must be used. .

On the other hand, when using the above mailbox file configuration example 2 for circular mailbox communication and SDI type seal box communication, individual boxes are allocated to each user, so as the number of users increases, the capacity of mail increases. There was a problem in that the box file 5 had to be used.

Therefore, the present invention solves the above-mentioned conventional problems and efficiently stores emails when there is a 1:n relationship between emails and the number of users who want the emails (n is an integer of 1 or more). The purpose is to reduce the size ω of mailbox files.

[F stage for solving problems]

The present invention classifies mail into mail types, assigns a mail classification identifier to each mail, stores it in a box in a mailbox file that corresponds one-to-one with the mail classification identifier, and reads the mail in the evening and on the first day of the month. This is done by reading out the mail in the box that matches the mail classification identifier.

(Operation) The configuration that classifies emails into email types, assigns an email classification identifier to each email, and stores it in a box in a mailbox file in one-to-one correspondence with the email classification identifier is as follows:
Avoid storing the same email multiple times in the mailbox file, and store only different emails to efficiently accumulate emails and reduce the capacity of the mailbox file.
This is to avoid people.

For example, in order to deliver the same email to multiple users, specify the email classification identifier corresponding to this email, read the email from the corresponding box in the mailbox file, and send the read email to each user. Deliver to.

In addition, if a user requests to read multiple emails, the user specifies the email classification identifier corresponding to each of the multiple emails, reads the email from the corresponding box in the mailbox file, and then reads the email. Deliver the email to each user.

〔Example〕

Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

FIG. 1 is a block diagram showing a system configuration (mail TI product processing ZARPIS system configuration) using an embodiment of the present invention. As shown in the figure, the system is a mail M-loading station II!
′! Apparatus 100. It includes a plurality of information provider devices 14 and a plurality of user terminals 15.

The mail storage processing device 100 is configured according to an embodiment of the present invention. The mail storage processing device 100 has a user managed information file 16. Correspondence table file 17. Mailbox file 18. and a control to1 section 200. The control unit 200 is a user management information registration mechanism 191
Outgoing mail accumulation structure 20° Mail delivery 121. Mail reading gate 22. and a mail search/transmission mechanism 23.

The user management information file 16 has a field (t4) (user management information) corresponding to a user on a one-to-one basis. In this user management information, usage i1D and a mail classification identifier regarding this user are set. The mail classification identifier (hereinafter simply referred to as mail classification!D) is mail identification information that classifies mail according to a predetermined type and is given to each classified mail. The correspondence table file 17 associates the user management information file 16 with the mailbox file 18. Mailbox file 18
is region 11, which corresponds one-to-one with the mail classification ID! (a mailbox to be described later).

The user management information σ recorder side 19 performs control so that the user can register in advance in the user management information file 16 a mail classification ID corresponding to the mail type desired by the user. This control is performed by operation 70-- shown in FIG.
It is carried out according to ty-t-. This O record is performed using the mail classification ID registration format 24 shown in FIG. As shown in the figure, the mail classification ID registration format 24 consists of one user ID 25 and a mail classification ID 26 related thereto. At the time of registration, information in the mail classification ID registration format 24 is sent from the user terminal 15 to the mail storage processing device 100.

The sent mail storage V4 mechanism 20 performs control for storing mail sent by an information provider from the information provider device 14 into the mailbox file 18. This control is
This is carried out according to an operation flowchart not shown in FIG. 6(B), which will be described later. The e-mail sent from the information provider device 14 is formed according to the e-mail sending format 27 shown in FIG. As shown in the figure, the mail transmission format 27 consists of one mail classification 1028 and the mail 29 related to this.

The mail delivery mechanism 21 performs control for delivering mail from the mail storage processing device 100 to the user terminal 15. This il+ control is performed in accordance with the operation flowchart of FIG. 6(C), which will be described later.

In this case, the mail read request format 30 shown in FIG.
Search for emails to be created and delivered.

The mail reading mechanism 22 performs control so that the user can read the required mail from the mail accumulation processing apparatus 100 via the user terminal 15. This control is performed according to the operation flowchart shown in FIG. 6(D), which will be described later. This reading can be done in two ways: One case is when the user reads an email that matches the email classification IQ that has been recorded in the user management information file 16 in advance. Now 1
One is not the e-mail classification ID recorded in advance, but
This is a process of reading emails that match the email classification ID specified by the user when making a read request. In the case of a song title, the user sets only user [D31] in the mail read request format 30 shown in FIG. 4 from the user terminal 15, and sends it to the mail storage processing device 100.

In the latter case, the user ID 31 and the required mail classification TD32 are sent to the mail storage processing device 1100.

The mail search/transmission mechanism 23 is activated in accordance with requests from the mail delivery system 21 and the mail reading mechanism 22, and performs search for mail stored in the mailbox file 18 and controls when sending mail. . This control is performed according to the operation flowchart shown in FIG. 6(E).

Next, the file structure in the mail storage processing device 100, that is, the user information file 16. Correspondence table file 1
7 and mailbox file 18 and their relationship to phase n will be explained with reference to FIG. The user management information file 16 holds a plurality of pieces of user management information 33 for each user.

Usage management information fa33 is prepared for the maximum number of users.

Each user management information 33 includes a user 1034 and a mail classification ID 35 related thereto. Correspondence table file 17
holds mail classification IDs 36 and mailbox numbers 37 in one-to-one correspondence in a table format.

As many pairs of mail classification IDs 36 and mailbox numbers 37 as the maximum number of mail classification IDs are prepared. The mailbox file 18 has a plurality of mailboxes 38. Each mailbox 38 is identified by a mailbox number 39, which is a serial number. Each mailbox 38 has a one-to-one correspondence with the mail classification ID 36. Each mailbox 38 has a mailbox number 39 and a mail storage area 40.

Prepare a mailbox for the maximum number of mail classification IDs (38 mm).

Next, the operation of the mail storage processing device 100 in this embodiment will be explained.

First, the operation when the user records the mail classification rD will be explained with reference to FIG.
According to the D registration format 24, the mail classification 1026 corresponding to the user ID 25 and the mail scale to be recorded is sent to the mail storage processing device I! /100. The management information σ record fi19 for the usage received is that the user management information whose content matches the received user fD25 and user ID3/4 is
It is checked whether it exists in the user management information file 16 (step 101 in FIG. 6 (Δ)). If it does not exist, a vacant one of the user management information 33 is secured (step 102). And usage from users 11
User I of user management information 33 who secured the contents of 025
D34 (step 104). On the other hand, if matching user management information exists in step 101,
The contents of the mail classification ID 35 of the user management information 33 are cleared and set to an empty state (step 103). Following step 103 or 104, use f5tJ instant information 3
1, which secures one free space for the mail classification ID 35 of No. 3 (step 105). Then, the contents of the mail classification 1026 are set in the mail classification TD 35 (step 106).

Then, it is checked whether all the email classification IDs 26 sent from the user according to the email classification ID σ record format 24 have been set to the email classification 1035 (step 107).
). All mail classification ■When setting D26,
Finish the process. On the other hand, if not, step 10
Returning to step 5, the process described above is performed.

Next, the operation when an information provider sends an e-mail to the e-mail storage processing device 100 from the information provider device 14 will be explained with reference to FIG. 6(B). sets the mail 29 and mail classification ID 28 for the mail to be sent and all mail classification IDs corresponding to the mail according to the mail transmission format 27 in FIG. 3, and sends the mail to the mail storage processing device 100. Upon receiving this, the outgoing mail storage mechanism 20 stores the unprocessed mail mID2.
8 (step 11 in FIG. 6(B))
1). Next, it is checked whether there is a match between the received email classification ID 28 and the email classification ID 36 stored in the correspondence table file 17 (step 112).
). If there is no match, one free mail classification ID 36 is secured and the contents of the received mail classification 1028 are set (step 113). On the other hand, step 112
Email classification ID with content that matches email classification 1028
36, the corresponding mailbox number 37
is empty (step 115).

If it is empty, the process proceeds to step 114; otherwise, the process proceeds to step 117. In step 114, one vacant mailbox 38 is secured (step 114).

Then, the contents of the three mailbox numbers of this mailbox 38 are set to the newly secured mail classification 1036 and the mailbox number 37, which is colored dark blue (step 116). Then, set the free mail storage area 40 to 1
The content of the received mail 29 is set there (step 117).Finally, it is checked whether there is an unprocessed mail classification TD28 in the mail transmission format 27 shown in FIG. 3 (step 118). ). When all mail classification IDs 28 have been processed, the process ends; otherwise, the process returns to step 111 and the same process is performed.

In the above outgoing mail storage process, the information provider device 14 assigns the mail classification ID in advance, but instead of this, the following may be used. In other words, the information providing device 14 sets only the mail 29 in the mail sending format 27 shown in FIG. 3 and sends it to the mail storage processing device 100. Upon receiving this, the outgoing mail storage mechanism 20 extracts the first one of the unprocessed mail classification IDs (step 111), and at t5, the mail classification ID is determined based on the format, content, etc. of the mail 29.
is determined, and the mail classification 10 determined according to the received mail transmission format 27 is added to all mail classification IDs 28. The subsequent operation is as shown in FIG. 6 (8).

Next, the operation of delivering mail from the mail storage processing device 100 to the user terminal 15 will be explained with reference to FIG. 6(C). First, the mail delivery mechanism 21 generates a mail read request format 30 shown in FIG.
21). Next, the usage fllD of the delivery target user is set to usage of read request format 30 = 51031 (step 122). Next, the user management information 33 that matches the content of the user ID 34 in the user management information file 16 and the delivery target user 10 is read out (step 123). Then, all of the email classifications 1035 of the user management information 33 are sent to the email classification ID 3 of the email read request format 30.
2 (step 124). Then, the mail delivery mechanism 21 activates the mail search and transmission mechanism 23 (step 125). In step 141 of FIG. 6(E), the mail search/transmission mechanism 23 uses the unprocessed mail classification ID.
Take out the first one of 32. Next, extract the mailbox number 37 that matches the retrieved mail classification ID 32 and the content of the mail classification ID 36 in the correspondence table file 17 (
Step 142). Then, it is checked whether the value of the retrieved mailbox number 37 is empty. If empty, processing continues at step 150; otherwise, step 14
Proceed to step 4. In step 144, mailbox number 3
The mailbox 38 whose mailbox number 39 matches the contents of 7 is extracted from the mailbox file 18.

Subsequently, one email from the first unsent email storage area 40 in the mailbox 38 is retrieved. Then, it is checked whether the corresponding user terminal 15 is connected to the mail storage processing device 100 (step 146). If not connected, connect the mail storage processing device ff 100 and the applicable 8 terminals 15 (step 147).
, proceed to step 148. If it is connected in step 146, the process proceeds directly to step 148. In step 148, one mail in the mail storage 1440 retrieved in step 145 is sent to the user terminal 15. Then, it is checked whether there is any unsent mail in the mail storage area 40 in the mailbox 38 taken out in step 144 (step 149).

If there is any unsent mail, the process returns to step 145, and if there is no unsent mail, the process proceeds to step 150. Step 1
In step 50, it is checked whether there is any unprocessed mail classification ID 32. If there is an unprocessed mail classification [D32, the process returns to step 141; if not, the process returns to FIG. 6(C) and proceeds to step 126. In step 126, the connection between the mail storage processing device 100 and the user terminal 15 is disconnected, and the process ends.

Next, the operation when the user reads mail will be explained with reference to FIG. 6(D). First, the user connects the user terminal 15 and the mail storage processing device 100,
According to the mail read request format 30 shown in FIG. 4, the user first sets his/her own user ID in the usage fileD31. At this point, the mail reading does not use the mail classification ID 35 registered in advance.

If you want to specify the email classification ID you want at that time,
The mail classification 10 is overridden by the mail classification 1032 setting of the mail read request format 30. On the other hand, when reading out mail corresponding to the mail number m[) 35 registered in advance in the user management information file 16, the setting of the mail classification 32 is not necessary. In step 131 of FIG. 6(D),
The mail reading mechanism 22 checks whether a mail classification ID 32 is set in the received mail reading request format 30. If it has been set, the process proceeds to step 134, where the mail search/transmitter f123 is activated and the operation shown in FIG. 6(E) described above is executed. If the mail classification ID 32 is not set in the mail read request format 30 in step 131, the user 1 in the mail read request format 30
The user management information 33 whose contents match 031 and usage 61034 is read from the user management information file 16 (step 132). Next, all of the email classification IDs 35 of the read user management information 33 are sent to the email continuous request format 3.
Set the mail classification ID32 to 0. Then, step 134 is executed.

As described above, since the mail in the mailbox 38 for each category stored in the mailbox file 18 can be used in a shared manner by multiple users or users, the mail can be efficiently stored in the mailbox. E-mail storage processing device 1 that can be stored well and uses less memory than conventional configurations.
7 of 00? It is possible to create an ile structure.

Next, another embodiment of the present invention will be described.

The block system configuration of this embodiment is similar to that shown in FIG. However, the correspondence table file 17 and mailbox file 18 in the mail storage processing device 100
The structure and mutual relationship are slightly different from those of the previous embodiment, and are constructed as shown in FIG. In FIG. 7, the correspondence table file 17 holds mail classifications 1036 and individual box numbers 41 in one-to-one correspondence in a table format. , a maximum of 10 sets of mail classifications 1036 and individual box numbers 41 are prepared.

Mailbox file 18 is individual box I442
and a common box area 43.

The individual box area 42 has individual boxes 44 for the number of pitches. Each individual box 44 is identified by an individual box number 46 which is a serial number. The individual boxes 44 are prepared by the maximum number of mail classification IDs, and each box 44 has a mail classification ID of 3.
There is a one-to-one correspondence with 6. Each individual box 44 has an individual box number 46 and a pointer 47 at t4. The common box area 43 has a plurality of common boxes 45.

Each common box 45 has a common box number 48 and a mail storage area 49. The common box number 48 is represented by a serial number. The common box 45 has a pointer 47
You can give instructions with

Next, the operation of the embodiment using the file structure shown in FIG. 7 will be explained. The operation of this embodiment is as follows: Outgoing mail storage 8! Except for the I mechanism 20 and the mail search/sending gate mechanism 23, this embodiment is the same as the embodiment described above. Further, as the mail classification 10 registration format, mail transmission format, and mail read request format, those shown in FIGS. 2, 3, and 4 can be used, respectively.

First, the operation of the outgoing mail storage mechanism 20 will be explained with reference to FIG.

Subsequently, the contents of the mail 29 are set in the mail storage k149 in the secured common box 45, and the contents of the common box number 48 are recorded (step 152).
. Then, the beginning of the unprocessed mail classification ID 28 in the outgoing mail format 27 sent from the information provider device 14 is extracted (step 153). Next, this mail classification 102
8 and the mail classification ID 36 are checked (step 154). If there is no match, email classification ID 3 in correspondence table file 17
6 is secured and the contents of this mail classification ID 28 are set here (step 155).Next, one desired individual box 44 in the individual box area 42 is secured (step 157).

Therefore, individual box number 4 in this individual box 44
6 is set in the individual box number 41 paired with the mail classification ID 36 (step 158). On the other hand, if it is determined in step 154 that there is no mail classification 1036 that matches the mail classification 28 retrieved in step 153, the process proceeds to step 156, and the mail classification l[) 15G that is currently being processed is Separate box number 4
Check whether 1 is empty (step 156). If there is a free space, the process goes to step 151, and if there is no space, the process goes to step 159. In step 159, the individual box 44 that matches this individual box number 41 is extracted.

The process then proceeds to step 16G. Then, one empty space is secured for the pointer 47 in this individual box 44, and the contents of the shared box 48 previously recorded are set there. Then, it is checked whether there is any unprocessed mail category 1028 in the outgoing mail format 27. If there is an unprocessed mail classification 1028, the process returns to step 153. On the other hand, when all mail classifications 1028 have been processed, the process ends.

Next, Figure 8 (
This will be explained with reference to B). First, the first one of the unprocessed mail classification IDs 32 in the mail read request format 30 is extracted (step 171). Next, retrieved email classification I
D32 and the individual box number 41 of the set that matches the contents of the mail classification ID 36 of the correspondence table 7 file 17 are extracted (step 112). Then, it is checked whether the individual box number 41 is empty (step 173). If it is empty at this time, the process proceeds to step 182. On the other hand, if it is not empty,
Extract the individual box 44 whose contents match the individual box number 41 and the individual box number 46 (step 173)
. Next, one of the unread head pointers 47 of the individual box 44 that has been taken out is taken out. Then, it is checked whether the capacity of the pointer 47 is empty (step 116).

If there is space in the pointer 47, the process proceeds to step 181; if there is no space, the process proceeds to step 177. Step 1.11
Now, the mail in the mail storage Wi 49 in the common box 45 whose contents match the pointer 47 and the common box number 48 is retrieved. Then, it is checked whether the corresponding user terminal 15 is connected to the mail storage processing device 100 (step 178). If connected, step 1
The process proceeds to step 80, and if not connected, the mail NV4 processing device 100 and the corresponding user terminal are connected (step 179), and then the process proceeds to step 180. Step 18
0, the mail stored in step 111 is stored ii! 14
Send the email in 9 to the user terminal 15 (Step 1
80). Then, it is checked whether there is any unprocessed pointer 47 in the individual box 44 taken out in step 174 (step 181). If there are any unprocessed items, return to step 175; if not, send mail reading format 301$
1 is checked to see if there is an unprocessed mail classification ID 32 (step 182). If there are any unprocessed items, the process returns to step 171; if not, the process returns to step 171;
Return to

As described above, even if the file structure is configured as shown in FIG. 7, the same effect as the previous embodiment with the file structure shown in FIG. 5 can be obtained.

Note that the name management information file 16, the correspondence table file 17, and the mailbox file 18 shown in FIG. It may be configured by a device. In addition, the control unit 200 is a central processing bag! (CPU). In this case, each component of the control unit 200 is controlled by the central processing unit as shown in FIGS. 6(A) to 6(E) and FIG.
) and (B) can be realized by executing a program embodying the operation flowcharts.

In the above embodiment, in addition to the mailbox file 18, a user management information file 16 and a correspondence table file 17 are used, but compared to the conventional configuration in which the same mail is stored in a mailbox file for each user, E-mails can be stored efficiently and storage capacity can be significantly reduced.

〔Effect of the invention〕

As explained above, according to the present invention, emails are classified into email types, each email is assigned an email classification identifier, and is stored in a box in a mailbox file that corresponds one-to-one with the email classification identifier. Since we decided to read emails by reading the emails in the boxes that match the corresponding email classification identifier, it is possible to efficiently store emails when there is a 1:n relationship between emails and the number of users who want them. You can reduce the size of your mailbox file.

[Brief explanation of the drawing]

Fig. 1 is a block diagram of a system (email storage processing service system) using an embodiment of the present invention, Fig. 2 is a diagram showing an example of the mail classification IDG record format used in an embodiment of the present invention, and Fig. 3 4 is a diagram showing an example of a mail sending format used in an embodiment of the present invention. FIG. 4 is a diagram showing an example of a mail reading request format used in an embodiment of the present invention. FIG. 5 is a diagram showing an example of a mail sending format used in an embodiment of the present invention A diagram showing an example of a file structure of a processing device. FIG. 6(A) is an initial flowchart of a user management information registration mechanism in an embodiment of the present invention. FIG. 6(B) is an outgoing mail diagram in an embodiment of the present invention. 11. Operation flowchart of the e-mail mechanism in the embodiment of the present invention. FIG. 6(D) is an operation flowchart of the mail delivery mechanism in the embodiment of the present invention. 70-JA-1., FIG. 6(E) is an operation flowchart of the mail search/sending mechanism in the embodiment of the present invention, and FIG. 7 is another example of file structure of the mail storage processing device in the embodiment of the present invention. Figure 8 (A) is a flowchart of the operation of the outgoing mail storage mechanism when the file structure example in Figure 7 is used, and Figure 8 (B) is a flowchart showing the operation of the outgoing mail storage mechanism when the file structure example in Figure 7 is used. Figure 9 shows the conventional mailbox file structure example 1, and Figure 10 shows the conventional mailbox file structure example 2. 14... Information provider device, 15... User terminal, 1
6... Usage crystal management information? file, 17...correspondence table file, 18...mailbox file, 19...
・User management information 0 recording mechanism, 20...Outgoing mail storage mechanism, 21...Mail delivery" L22...Mail reading mechanism, 23...Mail search/transmission mechanism, 24...
Mail classification ID registration format, 25...Usage MID,
26゜28.32.35.36...Mail classification 10,
27... Email sending format, 29... Email, 30.
...Mail read request format, 31...Use 61D, 3
3... Usage management information, 34... User ID, 37
...Mailbox number, 38...Mailbox number, 39...Box, 42...Individual box area, 43.45...Common box, 44...Individual box, 46...Individual Box number, 47...Pointer, 48...Common box number, 49...Mail storage area, 100...Mail storage processing device, and 200
is the control section. A block diagram showing a system configuration using an embodiment of the present invention.A diagram showing an example of mail classification rD registration format.A figure showing an example of an e-mail transmission format.Fig. 3 A diagram showing an example of an e-mail read request format. Figure 5 shows an example of the structure. Figure 5: Operation flowchart of the user management information registration mechanism. Figure 6 (A) Operation flowchart of the chat mail delivery mechanism. Figure (C) Section (E) Another example of the file structure of the email storage processing device. National policy map (A) showing the

Claims (1)

[Scope of Claims] Emails are classified into email types, each email is assigned an email classification identifier, and stored in a box in a mailbox file that corresponds one-to-one with the email classification identifier, and the emails are read in a corresponding manner. A mail storage processing method characterized by reading out mail in a box that matches a mail classification identifier.