JPH02311048A - Electronic mail system - Google Patents

Abstract

PURPOSE:To deliver an urgent text faster than a conventional system by detecting the communication state between a host computer and a opposite terminal equipment and controlling the delivery of the urgent text received by a prescribed sequence in response to the result of detection by a delivery control means. CONSTITUTION:When the designation of an urgent text exists, a CPU 9 generates a control document CD for text delivery from a transmission information table 14 to check whether or not a terminal equipment of delivery destination is busy. When the delivery destination terminal equipment is not busy, a text management table 12 is referenced. Then a relevant text ND is read from an ND memory area recorded on the table 12, the said text is set to a head of a transmission queue 5 and the resulting text is sent to the delivery destination terminal equipment. Whether or not the text is sent within a specified time or within specified retransmission number of times is checked. When the text cannot be sent within the specified value, the transmission of the relevant urgent text is stopped, a message of transmission disable notice is generated and the CD of the transmission disabled notice is sent to a sender terminal equipment.

Description

Detailed Description of the Invention [Field of Industrial Application] The present invention relates to an e-mail system, and more particularly to an e-mail system comprising a plurality of 04 terminals having MHS access procedures and a host computer that centrally processes information communication between the terminals. Regarding.

[Prior art] Conventionally, in this type of system, a host computer sets a message to be delivered with priority at the head of a transmission queue (if there is a message being sent, next to that message), and when the destination terminal /If a reception operation was in progress, the message was delivered after the operation was completed.

Furthermore, when it was delivered, it was configured to be handled in the same way as a general message designated for immediate delivery.

[Problems to be Solved by the Invention] However, since the message is distributed after the sending/receiving operation of the destination terminal is completed, it lacks promptness.

In addition, during delivery, the process is the same as for immediate delivery, so if the destination terminal is unable to receive the message, the message will be held at the center, and the host computer will be unable to send the message even though it is an urgent message. It remains stored inside for a long time.

[Problems to be Solved by the Invention] The present invention eliminates the above-mentioned drawbacks of the prior art, and its purpose is to provide an e-mail system in which emergency messages can be delivered more quickly. .

[Means for Solving the Problems] In order to achieve the above object, the e-mail system of the present invention is an electronic mail system comprising a plurality of 64 terminals having MHS access procedures and a host computer that centrally processes information communication between the terminals. In the mail system chimney, the sender terminal is equipped with a sending means for loading a control document with information indicating that it is an emergency message and sends it, and the host computer communicates with the host computer and the other party when distributing the emergency message received from the sender terminal. The outline of the system is to include a detection means for detecting the communication state with the destination terminal, and a distribution control means for controlling the distribution of the received emergency message in a predetermined sequence according to the detection result of the detection means.

Preferably, when the detection means detects that a message is being sent from the host computer to the destination terminal, the distribution control means interrupts the transmission of the message and preferentially distributes the received emergency message. , the outline is to retransmit the interrupted message after the distribution process is completed.

Preferably, the host computer further includes six
The distribution control means includes a storage means for storing reception capability information for the four terminals, and the distribution control means stores the information of the distribution destination terminal from the storage means when the detection means detects that a message is being sent from the distribution destination terminal to the host computer. The outline of the method is to read reception capability information and to immediately transmit the received emergency telegram by confirming that the destination terminal can receive the information even during transmission.

Preferably, the host computer further includes six
The distribution control means includes a storage means for storing reception capability information for the four terminals, and the distribution control means stores the information of the distribution destination terminal from the storage means when the detection means detects that a message is being sent from the distribution destination terminal to the host computer. Reading information on reception capability, since the information cannot be received by the destination terminal during transmission, after the destination terminal has finished transmitting,
The outline is to distribute the received emergency message with priority.

Preferably, the host computer further includes determining means for determining whether the received emergency message could be delivered by a specified time, and the distribution control means determines whether the received emergency message could be delivered by the specified time. The outline of the process is to delete the received emergency message, include information to that effect in a control document, and send it to the source terminal.

[Operation] In such a configuration, the transmission means of the transmission source terminal embeds information indicating an emergency message in the control document and transmits it. On the other hand, the detection means of the host computer detects the communication state between the host computer and the destination terminal when distributing the emergency message received from the transmission source terminal.

Then, the distribution control means controls the distribution of the received emergency message in a predetermined sequence according to the detection result of the detection means.

[Description of Embodiments] Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings.

FIG. 1 is a block diagram of an e-mail system according to an embodiment. In the figure, 1a to 1c are G4 terminals, and M
Has an HS access procedure. Note that each of the 64 terminals is also called a transmission source terminal or a distribution destination terminal depending on the purpose for which it is used.

2 is a digital line network. 3 is the host computer (
(hereinafter referred to as a host), and performs intensive processing of information communication between the G4 terminals 1a to lc. That is, each G4 terminal 1
Communication management information regarding the a-wlc is stored in the host 3, and all information communication between the terminals is performed via the host 3.

In the host 3, 4 is a CCP, which provides an interface between the host 3 and the digital line network 2. 5 is a transmission queue, which stores messages waiting to be transmitted in order of priority. A receiving buffer 6 temporarily stores the received message. 7
is a decoder, which expands the MMR data in the received message into image data. 8 is an encoder which compresses image data into MMR data. 9 is the CPU;
Performs main control and processing of the host computer 3. For example, the communication control programs shown in FIGS. 2A to 2H and FIG. 3 of the embodiment are executed. lO is the memory management unit (MMU)
It manages files for various types of memory. lla～l
lb is a memory that temporarily stores the distributed message. 1
Reference numeral 2 denotes a message management table, which stores management information of the message being handled. Reference numeral 13 denotes a recipient identification table, which stores terminal addresses (DA) used by the recipient in association with recipient identification information (for example, ID). Reference numeral 14 denotes a transmission information table, which stores information such as message distribution information and information necessary for creating a control document (CD). 1
Reference numeral 5 denotes a change information table, which stores information for changing predetermined communication management information (for example, information on temporary absence, change in terminal, etc.) in correspondence with recipient identification information.

Reference numeral 16 denotes a center-deposited message management table, which stores information for managing messages that have been kept by the center. Reference numeral 17 denotes an interruption message management table, which stores information for managing interrupted messages. 18 is a service discrimination table, G4
Stores information for determining various service requests loaded on the CD by the terminal. A mailbox 19 stores electronic messages treated as emails. Note that the mailbox 19 is assigned to each individual. 20 is a PBX interface unit (PBX-I/F), which connects host 3 and PB
Provides an interface with the X exchange 21. Furthermore, 2
1 is a general PBX exchange, 22a to 22c are telephone terminals connected to the PBX exchange 21, and 23 are telephone terminals 22a to 22c.
22c is a voice guidance device for notifying the incoming message via voice.

FIG. 4 is a diagram showing the format of the control document (CD) of the embodiment. In the figure, the first CD
/N The D identifier is CD, followed by the basic part. Furthermore, a plurality of service identifiers (1) to (n) and parameters (1) to (n) accompanying these can be installed. The service identifier represents the type of each service request. Examples include emergency delivery, immediate delivery, time-specified delivery, mailbox handling, information table changes, passwords, recipient identification information (ID), etc.

FIG. 5 is a diagram showing the storage structure of the recipient identification table 13 of the embodiment. In the figure, the recipient IDJ is identification information that can uniquely identify an individual, and may be an employee number within a company, for example. In addition, the recipient's "name" and the terminal address (DA) of the terminal used by the recipient.
, the telephone number (TelNo,
) J, "Mailbox No. J, etc. for each recipient are stored.

FIG. 6 is a diagram showing the storage structure of the transmission information table 14 of the embodiment. In the figure, "sender information" includes the name, ID, etc. of the sender of the message. The "recipient information" includes the name, ID, etc. of the recipient who is the addressee of the message. "Sending terminal information" contains the message sending terminal address (SA),
In addition, “Receiving terminal information” includes the message delivery destination terminal address (D
A) is included.

FIG. 7 is a diagram showing the storage structure of the message management table 12 of the embodiment. In the figure, "table NO0" stores information for establishing linkage with information in other tables. rND storage memory area" stores area information in which the relevant message (ND) in the memories lla to llb is stored.

The same applies to the interruption message management table 17.

FIG. 8 is a diagram showing the storage structure of the center deposited message management table 16 of the embodiment. In the figure, "elapsed time" stores the elapsed time since the message was held at the center.

The "telegram information storage area" is kept by the center and the contents of the transmission information table 14 and the like related to the telegram are saved. rN
"D storage area" is the memory 11 of the center storage and Natsu telegram.
Stores ND storage area information in a to llb.

FIG. 9 is a diagram showing the storage structure of the change information table 15 of the embodiment. In the figure, depending on the "change type", for example, if the recipient changes the receiving terminal, the "changed receiving terminal address" is stored, and if the recipient is absent, the "absence time" information is stored. . Additionally, "change cancellation conditions" for canceling such changes are also stored.

FIG. 3 is a flowchart of the registration/change processing procedure for the change information table 15 according to the embodiment.

When there is a change in the reception status due to the recipient's convenience, the contents of the change information table 15 are registered (i.e., the first change) or changed in advance through this process.

First, in step 5101, a person who wishes to make a change incorporates predetermined information into the CD of the G4 terminal. That is, for example, a password number is loaded in the service identifier (i) column, and change instruction contents are loaded in the service identifier (j) column. Please note that only one password can be entered per 10D. In step 5102, the CD is sent to host 3, and in step 5
At IO3, host 3 receives the CD. Step 510
In step 4, the host 3 checks the received CD and refers to the recipient identification table 13 for predetermined CD information. In step 5105, it is checked whether the password (for example, recipient ID) received with the CD is registered in the recipient identification table 13.

If a password has been registered, further step 5106
Then, it is checked whether there are any errors in the changed items of the request (for example, the receiving terminal address DA after the change cannot exist).

If the requested changes are correct, the change information table 15 is referred to based on the management number in step 5107. In step 8108, it is checked whether the person who desires the change has previously registered or made a change. If the registration or change has been made, the old registration is deleted in step 5109, and if the change has not been made, the change is newly written in the change information table 15 in step 5110. In step 5111, the host 3 creates a message to the effect of "OK" to the G4 terminal that issued the change request,
Send it out on CD. Then, in step 5112, the call is disconnected.

Also, in the determination in step 5105, the recipient identification table 13
If there is no password registered, the process proceeds to step 5113, where the host 3 forms a message saying "No password registered" and sends the request to the G4 terminal using a CD.

Further, if it is determined in step 5106 that there is an error in the changed item, the process proceeds to step Sl14, where the host 3 forms a message saying "there is an error in the changed item" and transmits it on a CD to the G4 terminal that issued the request.

In this way, each individual can change predetermined communication management information from any of the 64 terminals, provided the password is correct.

Note that, unless otherwise specified, the contents of the change information table 15 are deleted after a predetermined period of time has elapsed since they were registered or changed in the table 15 for the convenience of the user. This is because such changes are often temporary.

FIGS. 2A to 2H are flowcharts of the e-mail processing procedure of the embodiment.

The first half of this process uses the CD information received from the source terminal,
The objective is to create a transmission information table 14 for appropriate telegram distribution based on information on the recipient's reception status (contents of the change information table 15, etc.).

In FIG. 2A, in step S1, the source terminal 1a-
Receive the message from 1c. In step S2, the CCP 4 of the host 3 first separates a control document (CD) and a normal document (ND) upon reception from the source terminals 1a to 1c. Then, the ND is sent to the decoder 7, and the CD information is sent to the CPU 9. Furthermore, in detail about the CD information, the CCP4 extracts the source terminal address (SA) from the calling packet session information etc.
The CPU 9 records the SA in the transmission information table 14.

In addition, the address (DA) of the delivery destination terminal is included in the CD information.
If the DA is included, the corresponding DA is also stored. Furthermore, the CPU
9 stores other information (for example, sender's name, etc.) in the CD information in the transmission information table 14. In step S3, the table number in the transmission information table 14 is set to the message management table 1.
It is stored in table No. 2. With this, the relevant portions of the message management table 12 and the transmission information table 14 are linked. On the other hand, the decoder 7 that has received the ND decodes the ND into image data in step s4. In step S5, it is checked whether decoding is OK (decoding possible, etc.).

If the decoding is not OK, the decoder 7 reports an error to the CPU 9. As a result, the CPU 9 performs step S6.
A decode error notification message is created in step S7, and an error notification CD is sent to the transmission source terminal (SA) in the transmission information table 14. In step S8, the received message is deleted. In step S9, the recorded information in the message management table 12 and transmission information table 14 is cleared.

In this way, the host 3 checks the contents of the ND before distribution, and in the case of an error, deletes the error message without transmitting it to the destination terminal. Therefore, meaningless retransmission operations by the host 3 do not occur, and communication costs are saved. Also, the efficiency of using message memory increases.

On the other hand, if the determination in step S5 is that the decoding is OK, the process proceeds to step SIO, where the encoder 8 encodes the once decoded ND into MMR data again. and C
The PU 9 temporarily stores the encoded MMR data in one of the memories lla to llb via the memory management unit 10. In step Sll, the memory area storing the MMR data is recorded in the message management table 12. In step S12, the CPU 9 further checks the received CD information. Then, in step S13, the type of telegram service (handling of telegrams) in the CD information is referred to in the service discrimination table 18.

In step S14, it is determined whether the delivery is immediate delivery (including emergency designated delivery). If it is not immediate delivery, step S15
Perform the corresponding service processing.

Note that the flow beyond this process is omitted because it has little relation to the present invention. In the case of immediate distribution, the process proceeds to step S16 in FIG. 2B, and the CPU 9 refers to the transmission information table 14. Then, in step S17, the transmission information table 1
It is determined whether there is a designation (record) of DA in 4.

If there is no record of DA, the process advances to step S18 and the CP
U9 further checks the received CD information. Then, in step S19, the recipient identification ID is included in the received CD information.
Check whether there is.

If there is a recipient identification ID, proceed to step S20,
The CPU 9 refers to the recipient identification table 13. Then, in step S21, it is checked whether the recipient identification ID is registered in the recipient identification table 13. If registered, the contents of the recipient identification table 13 (for example, DA corresponding to the ID) are recorded in the transmission information table 14 in step S22.

As a result, even if the CD from the sender terminal does not have a DA installed, it is possible to deliver a message as long as the recipient identification ID is present.

On the other hand, if there is no recipient identification ID in the determination in step S19, or if there is a recipient identification ID but it is not registered in the recipient identification table 13 in the determination in step S21, the process advances to step S23, and the CPU 9 Create a message for an unknown recipient notification. In step S24, a CD of destination unknown notification is sent to the source terminal (SA) in the transmission information table 14. In step S25, the received message is deleted, and in step S26, the message management table 12
and clears the corresponding recorded information in the transmission information table 14.

Also, in the determination in step S17, D is added to the transmission information table 14.
If there is a record of A, the process advances to step S27 in FIG. 2C, and the CPU 9 further checks the received CD information.

Then, in step S28, it is checked whether there is a recipient identification ID.

If there is a recipient identification ID in the CD information, step S
The recipient identification table 13 is referred to in step 29. Then, in step S30, it is determined whether the recipient identification ID is registered in the recipient identification table 13. If registered, the contents of the recipient identification table 13 are recorded in the transmission information table 14 in step S32. This gives priority to the recipient identification ID and its registered contents.

On the other hand, if there is no recipient identification ID in the CD information as determined in step S28, or if there is a recipient identification ID but it is not registered in the table 13 as determined in step S30, the process advances to step S31, and the CPU 9 records the information present in the CD information in the transmission information table 14.

Now, returning to FIG. 2C, if there is a recipient identification ID in the CD information as determined in step S28 and this ID is registered in the recipient identification table 13 as determined in step S30, then It is necessary to check whether there is any change in the reception status. After executing step S32 in FIG. 2C, the CPU 9 refers to the change information table 15 in step 333 in FIG. 2D. And step S34
Then, it is checked whether change information regarding the recipient is registered in the change information table 15.

If the change information is registered, in step S35,
Furthermore, it is checked whether the type of change is designation of absence time.

If the change information specifies the absence time, the received CD from the source terminal is checked in step S39. Step S
In step 40, it is checked whether there is an emergency message designation.

If there is an emergency message designation, the recipient has already specified the recipient to be absent, so even if the message is delivered urgently, the recipient cannot actually receive the message. Therefore, the CPU 9 does not immediately distribute the message, and in step S41 creates a message of emergency transmission failure notification. In step S42, a CD of emergency transmission failure notification is sent to the source terminal. In step S43, the received message is deleted, and in step S44, the message management table 12 and transmission information table 1 for the message are deleted.
Clear the recorded information in step 4.

Further, if it is determined in step S40 that there is no emergency message specification, it is further checked in step S45 whether or not there is a time specification. If there is a time specification, in step S46, the content of the delivery time specification of this message to be delivered is rewritten with the content of the absence time recorded in the change information table 15, and the processing is performed for time specification delivery. If no time is specified, the message is placed in the mailbox 19 of the recipient at step S47.

If it is determined in step S35 that the absence time is not specified,
Furthermore, in step S36, it is determined whether the change information registered in the change information table 15 is a change designation of the receiving terminal. In the case of specifying a change in the receiving terminal, in step S37, the receiving terminal number (terminal address changed by the recipient) recorded in the change information table 15 is set in the sending information table 14 as the delivery destination DA of the message. Furthermore, Te
Check whether the change in No. is specified, and if the change is specified, check Te1No.

If the change is not specified, the Te1No area of the transmission information table 14 (part of the recipient information)
Clear. In addition, even when specifying a change in the receiving terminal, if there is a specification for the period for which the terminal change is to be maintained, the CPU
9 automatically changes information table 15 after this period ends.
Clear information related to device changes. Also step 83
If it is determined in step 6 that the receiving terminal is not specified to change, proceed to step S.
Other modification processing is performed in step 38.

This allows recipients to change their receiving terminals on an individual basis. Therefore, the sender can save the trouble of checking the location of each recipient. In addition, the recipient can temporarily receive messages addressed to him/her on a terminal in another location.

The transmission information table 14 has been created through the processing up to now.

Next, the distribution process to the destination terminal will be explained.

In FIG. 2E, step 848 checks the received CD. Then, in step S49, it is checked whether there is an emergency message designation.

If an emergency message is specified, proceed to step S50,
The CPU 9 selects a CD for message distribution from the transmission information table 14.
Create. In step S51, the destination terminal is connected to the bus
y Check whether it is (communicating) or not. G4 terminal 1a~
Since the IC's direct communication partner is always host 3, G4
The host 3 can easily determine whether the terminals 1a to 1c are busy or not.

If the destination terminal is not busy, step S52
The message management table 12 is referred to.

In step S53, the corresponding message (ND) is read from the ND memory area recorded in the message management table 12, and the message is set at the head of the transmission queue 5. In step S54, the message is transmitted to the destination terminal (DA). In step S55, it is checked whether the message has been transmitted within a specified time or within a specified number of retransmissions. If it cannot be sent within the regulations, the transmission of the emergency message will be canceled and a second message will be sent.
Proceeding to step S41 in Figure D, a message is created to notify that transmission is not possible, and in step S42, a CD of notification that transmission is not possible is sent to the sender terminal. In step S43, the emergency message is deleted, and in step S44, the recorded information of the message management table 12 and transmission information table 14 of the message is cleared.

Also, if the transmission was possible within the specifications, step S7 in Figure 2F
Proceed to step 2. The details will be described later.

In the determination in step S51 of FIG. 2E, the destination terminal is bu
In the case of sy, the process advances to step S56, and it is further checked whether the terminal is currently transmitting a message to the host 3.

If the destination terminal is transmitting to host 3, the 2nd G
Proceeding to step S77 in the figure, the CPU 9 refers to the transmission information table 14. Then, in step S78, it is checked whether there is information regarding a predetermined terminal. The information related to the terminal is, for example, information recording whether full-duplex operation (full-duplex communication (receiving a message while transmitting a message) is possible or not).

If there is information regarding the terminal, it is checked in step S79 whether the terminal is capable of full-duplex operation. If possible, the message management table 12 is referred to in step S81, and in step S82, the message (ND) is read from the ND storage area of the memories 11a to llb, and the message is sent with a CD for distribution attached to it. It is set at the head of queue 5 and transmitted to the destination terminal.

If there is no information about the terminal, or if there is information about the terminal but it is determined in step S79 that full-duplex operation is not possible, the process waits for the terminal to complete its transmission operation in step S80. After the transmission operation is completed, the process advances to step S81, and the message is urgently transmitted.

Note that the reason why the host 3 side does not forcibly interrupt reception when the destination terminal is sending a message is that this type of terminal automatically restarts sending a message after transmission is interrupted for the purpose of -1i11. This is because they do not have the means to do so. Therefore, for a terminal that automatically restarts message transmission, step S8
Processing of 0 is not necessary.

If it is determined in step S56 of FIG. 2E that the destination terminal is not transmitting to the host 3, it is receiving, and the process advances to step S57, where the host 3 interrupts the transmission of the message at the page break. In step S58, the message after the interruption page is temporarily stored in one of the memories lla to llb, and the ND storage area of the message is recorded in the interruption message management table 17. In step S59, the message management table 12 of the emergency message to be delivered is referred to, and in step S60, the memory l
The message (ND) is read from la to llb. Then, a CD for distribution is created from the transmission information table 14, an emergency message is set at the head of the transmission queue 5, and the message is transmitted to the destination terminal.

As a result, even if the destination terminal is receiving another message from the host 3 at the time of distributing the emergency designated message, there is no need to wait for the delivery until the end of the reception (the emergency message is immediately distributed).

In step S61, it is determined whether the transmission of the emergency message has been completed within a specified time or within a specified number of retransmissions.

If it is not completed within the specified time, the transmission of the emergency message is stopped and the process proceeds to step S83 in FIG. 2H, where a CD that cannot be sent in an emergency is created and sent to the source terminal.

In step S84, the emergency message is deleted, and in step S84, the emergency message is deleted.
In step 85, the records of the message management table 12 and transmission information table 14 of the message are cleared.

In this way, if the purpose cannot be accomplished within the regulations, the message is deleted, so that, for example, an emergency message is not stored (left unattended) in the host 3 for a long time, thereby increasing the operational efficiency of the system.

Further, in step S86, the contents of the interrupted message management table 17 are returned to the transmission information table 14, and in step S87, the continuation of the interrupted message is transmitted to the destination terminal.

In FIG. 2F, in step S67, it is checked whether the transmission has been completed normally.

If the transmission is not completed normally, a predetermined number of attempts are made in step S68. In step S69, it is checked again whether or not the transmission has been completed normally. If the transmission of the message, including the emergency designated message, etc., has not been completed normally, the message is kept in the center's custody in step S70, and the message is stored in the center's custody message management table 1.
6 records the storage area of the ND. Step S71
Now, copy the necessary information in the message management table 12 and transmission information table 14 to the center entrusted message management table,
Then clear the records in Table 12.14.

Note that the message held at the center may be resent later. Furthermore, the elapsed time may be managed according to the type of message (emergency, time specified, etc.), and if the message is not retransmitted within the time, the message may be deleted and the sender terminal may be notified of this fact.

If the transmission is completed normally in the determination in step S67, or if the transmission is completed successfully within the specified number of attempts, the
In step S72, the record of the message in the message management table 12 is cleared. In this case, the message (ND) on host 3
shall be automatically deleted upon successful completion of transmission to the destination terminal. Furthermore, in step S73, the CPU 9 refers to the transmission information table 14 corresponding to the transmission completion message, and in step S74, the CPU 9 selects Te1No.

Check whether there is any registration.

If there is a registration of Tel No., step S75
This Te1No is sent to the PBX 21, and the telephone terminal 2 of the Te1No is sent using the voice guidance device 23.
2a to 22c is notified by voice message that the telegram will be distributed.

This saves the recipient of the message the trouble of having to go to the location where the terminal is installed each time to check whether there is a message addressed to him or her. In addition, the recipient can quickly obtain the received message.

If Te1No is not registered, the process of step S75 is skipped, and the record in the transmission information table 14 is cleared in step S76.

In addition, if you send an emergency message while interrupting other messages,
After the emergency message is successfully transmitted, the voice message sending operation described above (processing from step S72 onwards) is performed on the emergency message, and then the interruption message is retransmitted.

[Effects of the Invention] As described above, according to the present invention, emergency messages are delivered to destination terminals more quickly than before.

Furthermore, even if the destination terminal is unable to receive the message, the emergency message will not be left unattended by the host computer for a long time, increasing the security of information communication.

[Brief explanation of drawings]

FIG. 1 is a block configuration diagram of the e-mail system of the embodiment, FIGS. 2A to 2H are flowcharts of the e-mail processing procedure of the embodiment, and FIG. 3 is the registration/change processing procedure of the change information table 15 of the embodiment. FIG. 4 is a diagram showing the format of the control document (CD) of the embodiment. FIG. 5 is a diagram showing the storage structure of the recipient identification table 13 of the embodiment. FIG. 6 is a transmission information table of the embodiment. 14. FIG. 7 is a diagram showing the storage structure of the message management table 12 of the embodiment. FIG. 8 is a diagram showing the storage structure of the center deposited message management table 16 of the embodiment. It is a figure showing the storage structure of change information table 15 of an example. In the figure, 1a to 1c...G4 terminal, 2...digital line network, 3...host computer, 4...CCP,
5... Send queue, 6... Receive buffer, 7...
・Decoder, 8...Encoder, 9...CPU, 1
0...Memory management unit (MMU), 11 a to l
lb...Memory, 12...Message management table, 13
... Recipient identification table, 14... Transmission information table, 15... Change information table, 16... Center deposit message management table, 17... Interruption message management table, 18... Service discrimination table , 19...Mailbox, 20...PBX interface section (PBX
-I/F), 2 L---P B X, 22 a ~
22 c-telephone terminal, 23... voice guidance device. Patent Applicant Canon Co., Ltd. Agent Patent Attorney Yasunori Otsuka (and others) Figure 2B Figure 2C Figure 2FIII Figure 2G Figure 2H Figure 5 Figure 6vA

Claims (5)

[Claims] (1) In an e-mail system equipped with multiple G4 terminals with MHS access procedures and a host computer that centrally processes information communication between the terminals, the sender terminal loads a control document with information indicating an emergency message and sends it. The host computer includes: a detection means for detecting the communication state between the host computer and the destination terminal when distributing the emergency message received from the transmission source terminal; An e-mail system characterized by comprising a distribution control means for controlling distribution of the received emergency message in a predetermined sequence. (2) The distribution control means interrupts the transmission of the message when the detection means detects that the message is being sent from the host computer to the destination terminal, and distributes the received emergency message with priority; 2. The e-mail system according to claim 1, wherein the interrupted message is retransmitted after the distribution process is completed. (3) The host computer further includes a storage means for storing information on receiving capability for each G4 terminal, and the distribution control means detects that the detection means is in the process of transmitting a message from the destination terminal to the host computer. According to claim 1, the information on the reception capability of the delivery destination terminal is read from the storage means, and the information indicates that the delivery destination terminal is capable of receiving even during transmission, so that the received emergency message is immediately transmitted. The e-mail system described in Section 1. (4) The host computer further includes a storage means for storing reception capability information for each G4 terminal, and the distribution control means detects that the detection means is in the process of transmitting a message from the destination terminal to the host computer. As a result, information on the reception capability of the delivery destination terminal is read from the storage means, and since the information cannot be received while the delivery destination terminal is transmitting, the received emergency telegram is transmitted after the transmission operation of the delivery destination terminal is completed. 2. The e-mail system according to claim 1, wherein the e-mail system distributes e-mails preferentially. (5) The host computer further includes a determination means for determining whether the received emergency message could be delivered by a specified time, and the distribution control means determines whether the received emergency message could not be delivered by the specified time. 2. The e-mail system according to claim 1, wherein upon determining that the received emergency message is correct, the received emergency message is deleted, information to that effect is included in a control document, and the control document is sent to the sender terminal.