JPH057906B2 - - Google Patents

Description

[Detailed Description of the Invention] [Technical Field of the Invention] The present invention relates to document communication, and relates to a document communication device that, when transmitting a document, specifies the destination, subject, etc. by setting an identifier in the document. It is.

[Technical background of the invention and its problems] When transmitting a document, it is necessary to specify transmission management information (hereinafter referred to as a message header) such as the destination, subject, and transmission mode (normal, urgent, etc.).
Conventionally, the message header has to be inputted and created separately from the document to be transmitted (hereinafter referred to as the message body), which is cumbersome.

Moreover, even though many of the items in the message header are actually described in the message body (see FIG. 5), they had to be re-entered when creating the message header.

When sending the same document (or with slightly different contents) frequently, it has conventionally been common practice to separately store corresponding message headers. According to this, there were problems such as occupying storage space for storage and implementing a function for associating stored message headers with documents.

[Object of the Invention] The present invention has been made in consideration of the above circumstances, and provides a document communication device that can specify transmission management information such as destination and subject by setting an identifier in the document to be transmitted. The purpose is to

[Summary of the Invention] The present invention is characterized in that, when transmitting a document, a message header is created from a portion surrounded by a start code and an end code (different depending on the details of the message header) of an identifier set in advance in the document.

[Effects of the Invention] According to the present invention, if the destination, title, etc. in a document are surrounded by the start and end codes of the corresponding identifier when the document is created, these can be rewritten when the document is sent. There is no need to re-enter these items, and the message header is automatically created by collecting these items. In this way, the operational effort of re-entering information for creating a message header is eliminated.

In addition, there are various problems that occur when storing the message header separately from the document to which you want to send.
For example, the problem of storage space and the problem of associating stored message headers with transmitted documents can be solved.

[Embodiments of the Invention] FIG. 1 shows a block diagram of a document communication device embodying the present invention. The document communication device 100 includes a control device 110, a storage device 120, a terminal control device 130,
It is composed of a communication control device 140.

The control device 110 includes a message transmitting/receiving section 111, a document creation/editing section 112, a message header creation section 113, a message body creation section 114, and a timer 115, and controls the entire document communication device 100.

The storage device 120 stores a message file 1 that temporarily stores messages to be sent or messages received.
21, a document file 122 that stores documents to be sent or documents that are received and stored; a communication management file 123 that stores management information for communication;
etc. are stored.

A plurality of terminals are connected to the terminal control device 130, and input/output of the terminals is controlled.

A communication line is connected to the communication control device 140, and controls communication with other devices such as document communication devices.

FIG. 2 shows a block diagram of the message header creation section 113. The message header creation section 113 includes a reading section 1131 that reads a document, and an extraction section 11 that extracts each item to be set in the header of a message from the read document.
32, a writing unit 1133 that sets the information to be set in the message header in the message header.

FIG. 3 shows the format of the message to be communicated. The message is composed of message headers 310 to 360 and a message body 370.

310 is the message number set on the sending side, 320
is the title which is the name given to the message, 330 is the transmission mode indicating the transmission format such as normal, urgent, confidential, etc., 340 is the number of destinations, 341, 342,
... is the destination, 350 is the sender's destination, 360 is the sending time set on the sending side, and these 310 to 3
A message header is composed of 60 items.

The document to be sent is set in the message body 370.

FIG. 4 shows a message header management table 400 that represents start and end codes for specifying items to be set in a message header in a document.

In the document to be sent, the character string surrounded by the symbol A[, symbol]A is the message subject. The same applies to other items. Here, each code corresponds to, for example, a 2-byte code such as X'OB81'.

The message header management table 400 is stored in the communication management file 123 in the storage device 120, as shown in FIG.

The specific operation of this embodiment will be explained below.

First, the sender creates a document to be sent via the terminal using the document creation and organization section 112, and stores it in the document file 122.

An example of a transmitted document is shown in FIG.

In this example, the recipients are ``Tanaka, General Affairs Department,'' ``Suzuki, Accounting Department,'' the subject is ``March Safety Targets,'' the transmission mode is ``Urgent,'' and the sender is ``Sato, Safety Department.'' In the document, start and end codes for specifying the items are entered before and after each of these items.

FIG. 6 shows a message created from the document 500 shown in FIG. The message header 501 is created by the message header creation time 113, and the message body 502 is created by the message body creation unit 114.

The message header creation unit 113 operates according to the message header creation procedure shown in FIG. At this time,
Using the start code and end code of each item in the message header management table 400 (see FIG. 4), the subject, transmission mode, etc. are extracted from the document to be transmitted.

To set the message number, the value set in the message number counter 1236 in the communication management file 123 in FIG. 8 is set in the message header 501. After this, 1 is added to the value of the message number counter 1236.

The message body is created by the message body creation unit 114 using normal means, combined with the message header, and stored in the message file 121. The message stored in the message file 121 is transmitted to the destination by the message transmitting/receiving section 111 via the communication control device 140.

As described above, each item of the message header is extracted from the part surrounded by the start and end codes of the identifier set in advance in the document (different depending on the title, destination, etc. of the message header), and the message header is created. It can be automatically created and sent to the destination.

To set the start code and end code in the document,
Various document creation and editing techniques that have been proposed in the past can be employed.

Note that the present invention is not limited to the above embodiments.

For example, the message header management table 400 shown in FIG. 4 is not limited to one type. Each user may have a message header management table with a different start code and end code.
Alternatively, a plurality of message header management tables may be provided in case the same user uses the same document for different transmissions (for example, to different destinations). In the latter case, the user will specify which message header management table to use when sending.

Further, the message header management table 400 is not limited to the format shown in FIG. Various items can be added depending on the form of transmission, such as the purpose of transmission (report, notification, response, etc.), reception deadline (deadline for the other party to see it), etc.

[Brief explanation of the drawing]

Figure 1 is a block diagram of a document communication device showing an embodiment of the present invention, Figure 2 is a block diagram of a message header creation section, Figure 3 is a diagram showing the format of a message, and Figure 4 is a message header management table. , Figure 5 is a diagram showing an example of a transmitted document, Figure 6 is a diagram showing the transmitted document shown in Figure 5 in the form of a message, and Figure 7 is a diagram showing the procedure for creating a message header. The flowchart, FIG. 8, is a diagram showing the communication management file. 100... Document communication device, 110... Control device, 120... Storage device, 130... Terminal control device, 140... Communication control device.

Claims (1)

[Claims] 1. A means for creating and editing a document as a message body;
means for assigning different control codes for identifying each of the destination, sender, subject, and transmission mode described in the document;
Means for storing a correspondence table in which correspondence between transmission modes and respective control codes is registered, and extracting the destination, sender, subject, and transmission mode corresponding to the control code from the document using the correspondence table. A document communication device comprising: means for creating a message header; and means for transmitting and receiving a message composed of the message header and the document.