JPH0954732A - Mhs function highly advancing method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To flexibly customize an MHS(massage handling system) component function or to flexibly making an MHS user function highly advanced. SOLUTION: Desired processing is executed by an MHS component by notifying the component (MTA(message transfer agent), UA(user agent), MS(message store), etc.) of an MHS node 1 of a script 4 in which the processing procedure of a message 2 addressed to a principal is described to, or the desired processing is executed by the MHS user function by assuming the script in which a procedure processed by the MHS user function on a reception side is described in the message.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a message communication system for providing an electronic mail service in a public network,
So-called message handling system (Message Ha
ndling System: hereinafter referred to as MHS), which is a method for enhancing the function of MHS component and enhancing the function of MHS user by using a script language.

[0002]

2. Description of the Related Art In recent years, some of the e-mail systems originally have few functions and are not so advanced. Therefore, as seen in Enabled Mail, etc., functions are added using a script language. And a method for flexibly realizing customization is being studied.

Here, the script language is a high-level language for an interpreter, and a program described in the script language (hereinafter referred to as a script) can be executed sequentially while interpreting the statements one by one by the interpreter. Therefore, it is excellent in descriptiveness and extensibility compared to the compiler method.

On the other hand, the MHS individually supports various advanced message processing functions such as delivery notification, reception notification, content conversion, and recipient change in order to provide an electronic mail service in a public network. CCIT
The specifications are recommended by T (current ITU).

That is, as is well known in MHS, a message transfer agent (hereinafter referred to as MT) is used.
User Agent (hereinafter U)
(A), Message Store (hereinafter M)
MHS components such as S) are defined, and these MHS components cooperate to transfer and store MHS messages (hereinafter, also simply referred to as messages).

For example, the content conversion function of the MTA can convert a text-formatted message addressed to a recipient into a facsimile (hereinafter referred to as FAX) and output it.

[0007] Further, by the destination change (redirection) function of the MTA or the automatic forwarding (auto-forwarding) function of the UA,
It is possible to forward a message addressed to one recipient to another particular recipient.

[0008]

[Problems to be Solved by the Invention] However, the current MHS
Then, since processes such as route selection and dispatch in MTA and automatic transfer in UA are decisively performed according to the procedure defined in the standard for each MHS node, once a certain function of the MHS component is used, it is received. Functions corresponding to valid messages are unconditionally applied. It is difficult to dynamically change the processing procedure in the MHS node because it is executed by a program obtained by converting the source program by the compiler.

Condition setting for function application (for example, "only for a specific subject in a message addressed to a certain recipient" content conversion, "only from a specific sender" for a message addressed to a certain recipient) It is possible to add recipients, add functions, and combine existing functions, etc.,
If you try to customize or extend these functions later, it is necessary to change the processing procedure of the MHS node and reconfigure the system to realize the changed processing procedure, for example, to change and recompile the source program. We cannot deal flexibly.

Therefore, it is an object of the present invention to provide a method capable of flexibly customizing or expanding the function of MHS.

[0011]

In order to solve the above problems, an MHS function upgrading method of the present invention is to create a script that defines in a script language a procedure for processing a message addressed to a specific subscriber to be executed by an MHS component. Notifying the script to the MHS component from the subscriber terminal, the MHS component stores the notified script, and when a message addressed to a specific subscriber arrives, interprets the script with an interpreter including a library function prepared in advance. A method characterized by executing a processing procedure of the message addressed to the specific subscriber, or M
Describe in the message a script that specifies the processing procedure of the message to be executed by the receiving subscriber terminal of the HS in a script language, and send a message containing the script from the calling subscriber terminal to the receiving subscriber terminal. That is, the receiving subscriber terminal interprets the script in the received message by an interpreter including a library function prepared in advance and executes the processing procedure of the received message, or the script controls When using data, describe the structure of control data in abstract syntax notation, store the structure of script and control data in the first external definition body part of the message,
The method is characterized in that the value of the control data is stored in the second externally defined body part, and the receiving subscriber terminal executes the script based on the structure of the control data and the value of the control data.

[0012]

Embodiments of the present invention will be described below with reference to the drawings.

In the present invention, paying attention to a script language excellent in descriptiveness and extensibility, by introducing a control function of the script language into the MHS, the function of the MHS is enhanced. The sophistication of the MHS function is the customization of the MHS component function and the sophistication of the MHS user function.
There are two possible approaches.

Here, the MHS user function means a function of a subscriber terminal which performs local processing (eg, creation of a message to be sent, editing, display of a received message, etc.) with respect to the MHS.

(First Approach: Customization of MHS Component Function) The first approach is customization of the MHS component function.
This is realized by the idea of (5).

(1) As shown in FIG. 1, the MHS node 1
Has MHS components such as UA, MTA, and MS, and these MHS components support various message processing functions such as route selection, transfer, content conversion, and automatic reception response in advance. Therefore,
By flexibly executing these existing MHS component functions according to various conditions or by combining the functions, the processing for each message 2 for each subscriber can be customized.

(2) As means for customizing the MHS component function, as shown in FIG. 1, an instruction (script) 4 is written in a script language by the MHS user function of the subscriber terminal 3 and notified to the MHS component. Then, the MHS component is made to execute the script 4.

(3) The script (script) 4 has a message processing function in which each subscriber supports processing procedures such as route conversion and content conversion that each subscriber should process for a message addressed to itself by each MHS component. And the conditions that trigger the operation are specified in script language. For this reason, execution of the function to be supported and condition check are provided in advance from the MHS to each subscriber as a library function.

(4) As a method of notifying the script 4 to the MHS component, a Register (register;
Registration) such as extending the parameters of an existing MHS service primitive to notify script 4, a method of notifying script 4 by newly defining and adding a new service primitive, a special message such as a script body There is a method of transmitting the script 4 by a message held by the.

(5) An interpreter of a script language is prepared in advance in the MHS, and the MHS component stores the script 4 notified from each subscriber inside, and in addition to the standard processing procedure. , Every time the message 2 for the subscriber corresponding to the script 4 arrives,
By interpreting the script 4 from the subscriber by an interpreter including a library and checking the corresponding condition and executing the function, processing such as route selection and content conversion according to the subscriber's request is performed.

As described above, the subscriber can flexibly combine the existing message processing functions of the components defined by the MHS, or change the contents of each message processing function, for example, the subscriber can flexibly set detailed conditions. it can.

According to the MHS function enhancement method by customizing the MHS component functions described above, the MHS
The sophistication of the function can be realized by closing it in one MHS node 1, and it is not necessary to add special information to the existing message 2 to describe it. The message 2 is composed of an envelope 5 and a content 6 as shown in FIG. 1, and the content 6 is composed of a heading 7 and a body 8.

(Specific Example of Customization of MHS Component Function) Next, a specific example of the method for enhancing the MHS function according to the first approach will be described with reference to FIGS. However, as a script language, the tool command language (To
ol command langage: hereinafter referred to as Tcl).

In this example, customization is performed to add a copy recipient to a message from a specific sender, and a message received in a certain time zone and specified at the beginning of the subject. F for messages containing keywords (Important in this example)
Customization for conversion to AX will be described.

First, a script description library function 10 as shown in FIG. 2 is prepared. This library function 1
0 is composed of a command group 11 that defines the operation for message and execution of component functions, a function group 12 that obtains message parameters, and other support function group 13 that enables control according to the environment. The function group 12 for obtaining message parameters and the other support function group 13 are library functions for enabling condition setting.

Command group 11 of library function 10
The command "AddCopyRecip" is a command to add a copy recipient other than the principal as the recipient. The command "MsgRedirect" is a command to redirect the message to the specified recipient. The command "Msg2Fax" is a command for converting the text body of the message into a G3 FAX. The command “MsgDispatch” is a command requesting execution of the message dispatch (additional delivery) function.

Function group 12 for obtaining message parameters
, The function "GetOriginator" is the function that gets the sender name of the message, and "GetRecipients".
Is a function that gets the recipient name of the message.
"ct" is a function that gets the subject of the message, and "CompORAddr" is the sender / receiver (O / R: Orig).
This is a function to compare with the address of (inator / Recipient).

Explaining the other support function group 13, the support function "GetContSize" is a function for obtaining the size of the content in the message, and "GetCurrTim".
"e" is a function for obtaining the current time, and "ChkTimeRange" is a function for checking whether it is in a specific time zone.

The script 4A shown in FIG. 3 is for customizing to add a copy recipient to a message from a specific sender.
Instruct to get the caller name and set this as "org". In addition, the sender name set as "org" is specified by the "if statement" to a specific sender name (JP / K in this example).
DD / LAB / SUZUKI), and if there is a match, a specific recipient (JP / KDD / ABCD /
KATO) is added to the copy recipients to instruct delivery of the message to the copy recipients as well as the original recipients. Note that "set" and "if" are commands of Tcl itself.

When a subscriber notifies the MHS component of the script 4A, the MHS component stores the script 4A. When a message addressed to the subscriber arrives at the MHS node, the script 4A is generated based on the script 4A. The processing is performed as follows.

The script 4A is interpreted by an interpreter including the library function 10, and the sender name is first obtained from the message and set. Next, the set sender name is compared with the specified sender name, and if they match, the specified receiver is added to the copy receiver, and this copy receiver and the original receiver (script 4A is notified. Deliver the message to both subscribers).

The script 4B shown in FIG. 4 is for customizing a message received at a specific time zone and converting a message containing a specific keyword at the beginning of a subject into a FAX and transferring the FAX. Yes, "set statement"
To get the current time of the message arrival and call it "time
Now ". The first "if statement" checks whether the time set as "timeNow" is in a specific time zone (from 21:00 to 7:00 in this example). Instruct to get the subject of the message by "set statement" and set it as "subj". In addition, the following "if statement" causes "su
Check whether the subject set as “bj” includes a specific keyword (Important in this example) at the beginning, and if so, specify the specified recipient (JP / KDD / in this example).
COM / N = 0312345678), the destination of the message is changed, and the body in the text format of the message is converted into the FAX of the G3 system to be distributed. Here, "string match" is a Tcl command that checks for a string match. The asterisk "*" represents any character or character string.

When a subscriber notifies the MHS component of the script 4B, the MHS component stores the script 4B. When a message addressed to the subscriber arrives at the MHS node, the script 4B is based on the script 4B. The processing is performed as follows.

The script 4B is interpreted by an interpreter including the library function 10, and the time when the message arrives is first obtained and set. Next, it is checked whether or not the set time is in a specific time zone, and if it is in the specific time zone, the subject of the message is acquired and set. Next, it is checked whether or not a specific keyword is included at the beginning of the set subject matter, and if it is included, the message destination is changed to the specified recipient, and the text body of the message is changed to G3 FAX. Change and transfer.

As can be seen from the specific examples described above, by combining the library and the execution control functions such as the "set statement" and the "if statement" of the script language, it is possible to describe the detailed processing according to various conditions. It is possible.

(Second Approach: Sophistication of MHS User Function) Next, the second approach is sophistication of the MHS user function, which is realized by the following ideas (1) to (8).

(1) As shown in FIG. 5, a first external definition body part (hereinafter referred to as a script body part) in which a script is described in the body 8 of the MHS message 20.
21 is provided with an identifier, and a script 22 defining the processing procedure of the message 20 itself is described by the MHS user function of the calling subscriber terminal 3S.
0 is transmitted to the receiving side subscriber terminal 3R by MHS.

(2) The script 22 causes the receiving side subscriber terminal 3R to execute a processing procedure to be executed for the message 20, for example, to send a reply to the message, or change the output device to FAX for each subject. The procedure is specified by describing it using a script language by the MHS user function of the calling side subscriber terminal 3S.

(3) Further, in the case where the process of circulating the message to a plurality of designated destinations in order is performed, the script 22 uses the control data. In such a case, the control data structure is ASN.1 (Abstract Syntax Notation.
1: Abstract syntax notation. 1) The type is defined as shown in Fig. 5.
ASN.1 description 23 that defines the control data type as shown in
Should also be stored in the script body part 21.

(4) Therefore, the script body part 2
The structure of No. 1 may or may not have the ASN.1 description 23. Therefore, the structure of FIG. 6 is represented by ASN.1. The script body part 21 shall be encoded according to the ASN.1 encoding rules. Incidentally, [0] and [1] in FIG.
Is a tag.

(5) Further, the value itself of the control data, that is, the value of each element is the body 8 of the message 20 as shown in FIG.
A second external definition body part (hereinafter, control data body part) 24 is provided and stored therein, and the object identifier thereof may be specified in the script 22.

(6) Therefore, the library function used for the script 22 is predetermined between the calling side subscriber and the receiving side subscriber.

(7) In addition to the normal functions, the MHS user function of the receiving side subscriber terminal 3R has an interpreter in a script language and an AS for accessing ASN.1 type data.
It has an N.1 interpreter.

(8) When the message is received, the MHS user function of the receiving subscriber terminal 3R executes the script 2 to execute the script while accessing the control data.
The processing of the message 20 including 2 is performed as follows.

(8-1) Message 20 is sent by MHS UA
Read from (user agent) and display.

(8-2) If the message 20 includes the script body part 21, the bit string of the script body part 21 is decoded. The presence / absence of the script body part is determined by the presence / absence of a predetermined identifier.

(8-3) When the script body part 21 includes the ASN.1 description 23 of the control data,
The ASN.1 description 23 is passed to the ASN.1 interpreter to enable access to the control data. The presence or absence of the ASN.1 description 23 is determined by the tag.

(8-4) The script 22 is passed to the interpreter to control the message 20. That is, the script 22 in the message 20 is interpreted and executed by the interpreter to perform the process according to the instruction of the sender.

As described above, the function of changing the output device on the receiving side, the advanced message transfer function such as a roundabout mail that circulates the message to a plurality of designated destinations in order, the new electronic mail version such as electronic shopping that should be called teleshopping, etc. The mail application can be easily realized by the subscriber or the application provider without changing the MHS.

(Specific Example of Sophistication of MHS User Function) Next, referring to FIGS. 7 to 9, the MHS according to the second approach will be described.
A specific example of the function enhancement method will be described. However, Tcl is used as the script language in this example as well.

In this example, the approval letter mail for circulating the messages to a plurality of destinations in the designated order is realized.

Therefore, a library function 30 used in a script as shown in FIG. 7 is prepared. The script body part 21 of the message 20 includes the script 22 shown in FIG. 8 and the control data type ASN.1 shown in FIG.
Include description 23.

First, the meaning of the library function 10 is as described in FIG. 7, but the function "GetExternBody" is used.
Is a function for acquiring the bit string data of the second external definition body part, that is, the control data body part 24. The function "Decode" is a function that performs decoding according to the encoding rules of ASN.1. The function "WinGetYesNo" returns Yes to the screen to confirm whether to approve the approval request.
It is a function that displays the buttons No and No and returns the operation result (1/0). The function "ASN1Set" is a function that sets a value to a specified element of ASN.1 type. Function "ASN1Get"
Is a function that gets the value of a specified element of ASN.1 type. The function "Encode" is a function that performs encoding according to the ASN.1 encoding rules. Function "SetExternB
"ody" is a function for storing bit string data in the control data body part 24. The function "SendMessage" is a function that sends a message to a specified ORName (a code indicating the sender or receiver of the message).

Of the library functions, "Decode" and "En
"code", "ASN1Set", and "ASN1Get" are executed by the ASN.1 interpreter using the ASN.1 description 23 of the control data type.

Next, the ASN.1 description 23 shown in FIG. 8 will be described. In this ASN.1 description 23, the control data name is "DestAn
"dStatus", the element "current" indicating how far the structure of this control data was confirmed, and the element "destList" indicating the destination list. Furthermore, the destination list element "destList" is the same as "DestList". Represents that it consists of type elements. In addition, each element "DestLi
"st" is the destination element "dest" and the element "ap" that represents the approval result
prove ”. Furthermore, the control data is of SEQUENCE type, the element "current" is of INTEGER type, the element of "destList" is of SEQUENCE OF type, and the element of "DestList" is of order type. It is a column (SEQUENCE) type, element "dest" is a type that indicates the sender or recipient name ORName, and element "approve"
"Is a logical (BOOLEAN) type and takes 1 or 0. "OPTIONAL" is the element "approve"
Indicates that the value of may not exist.

Next, the script 22 shown in FIG. 9 is a script for approval request mail written in Tcl, and its meaning is as follows.

The "set statement" on the first line is the object identifier (0-3-XX in this example) specified from the received message.
XX-YZ) of the externally defined body part (that is, control data body part) is acquired, and this data is set to "bod
set as "y". This data is encoded into a bit string.

The "set statement" on the second line is the bit string data previously set as "body" (represented by $ body).
According to the control data type “DestAndStatus”,
Instructs to set this as "ds".

The "set statement" on the third line is "Do yon agree o
n message? (Do you agree with the message?) ”Is displayed, and Yes and No buttons are displayed to instruct to set the operation result (1/0) of the button as“ appr ”.

The "set statement" on the 4th line acquires the value of one element "current" in the control data (represented by $ ds) previously set as "ds", and acquires this value. "Curr"
To set as.

The "ASN1Set statement" on the fifth line is the value (represented by $ curr) previously set as "curr" of the element "destList" of the control data set as "ds". For the element "approve" to be in order, first add "app
Display that the value set as "r" (displayed as $ appr) is set.

The "ASN1Set statement" on the 6th line is "curr" in the element "current" of the control data set as "ds".
It is instructed to set the value obtained by adding 1 to the value set as.

The "set statement" on the 7th line is "curr" in the element "destList" of the control data set as "ds".
Indicates that the value (ORName) of the element "dest" whose order is the value obtained by adding 1 to the value set as is set as "next".

The "set statement" on the 8th line encodes the control data set as "ds" into a bit string to generate "newbody".
To set as.

The "SetExternBody statement" on the ninth line is the bit string data ($ newb) previously set as "newbody".
ody) is stored in the externally defined body part having the specified object identifier (0-3-XXXX-YZ in this example), that is, the control data body part.

The "Send Message statement" on the 10th line indicates to send a message to the value previously set as "next", that is, ORName (represented by $ next).

[Set] in the script 22 is Tcl
Command.

When the receiving subscriber terminal 3R receives the message 20 including the script 22 and the ASN.1 description 23 of the control data used by the script 22, the MHS
The user function executes the script 22 and performs the following processing.

First, the first line "set statement" and the second line "se"
By executing the "t statement", the value of the control data in the form of a bit string is extracted from the external definition body part (control data body part) 24 of the specified object identifier in the message 20, and the ASN that defines the type of the control data is extracted. .1 Decode control data using description 23.

Next, by executing the "set statement" on the third line, a confirmation button for the approval request is displayed and consent is obtained.

Next, "set statement" on the 4th line and "AS statement" on the 5th line
By executing "N1Set statement", the confirmation result of the approval request is displayed in the control data element "approv" corresponding to the current recipient.
e "as the value. That is, the control data sets how far the confirmation has been completed.

Next, the "ASN1Set statement" on the sixth line and the "set statement" on the seventh line are executed to obtain the next destination from the control data.

Next, the "set statement" on line 8 and the "Se statement" on line 9
By executing "tExternBody statement", the value of each element of the control data is encoded into a bit string and stored in the control data body part 24.

Finally, by executing the "SendMessage statement" on the 10th line, the message 2 having the script 22 and the ASN.1 description 23 is sent to the next destination acquired earlier.
Send 0.

As can be seen from the above-mentioned concrete example, by using the library function and the script language and the interpreter of ASN.1, the MHS user function is enhanced and the advanced message transfer function is easily or flexibly realized. can do.

[0076]

According to the present invention, by introducing the control function of the script language into the MHS, the MHS component function can be flexibly customized and the MHS user function can be flexibly enhanced. it can.

[Brief description of drawings]

FIG. 1 is an explanatory diagram of customization of MHS component functions as a first approach of the present invention.

FIG. 2 is a diagram showing an example of a library function.

FIG. 3 is a diagram showing an example of a script.

FIG. 4 is a diagram showing another example of a script.

FIG. 5 is an explanatory diagram of the sophistication of the MHS user function as the second approach of the present invention.

FIG. 6 is a diagram showing the structure of a first external definition body part in ASN.1.

FIG. 7 is a diagram showing an example of a library function.

FIG. 8 is a diagram showing an example of ASN.1 description defining a control data type.

FIG. 9 is a diagram showing an example of a script.

[Explanation of symbols]

1 MHS node 2, 20 message 3 subscriber terminal 3R receiving side subscriber terminal 3S calling side subscriber terminal 4, 4A, 4B, 22 script 5 envelope 6 content 7 heading 8 body 10, 30 library function 21 first external definition body Part (script body part) 23 Control data type ASN.1 description 24 Second external definition body part (control data body part)

Claims (3)

[Claims] 1. A script that defines a procedure for processing a message addressed to a specific subscriber to be executed by a component of a message handling system (hereinafter referred to as MHS) in a script language, and the script is transferred from the subscriber terminal to the MHS component. Notify me, MH
The S component stores the notified script and, when a message addressed to a specific subscriber arrives, interprets the script by an interpreter including a library function prepared in advance and executes the processing procedure of the message addressed to the specific subscriber. A method for enhancing the function of MHS, characterized by: 2. A script containing a script defining a processing procedure of a message to be executed by a receiving side subscriber terminal of a message handling system (hereinafter referred to as MHS) is written in the message, and a message including the script is transmitted. A call is sent from the subscriber terminal on the receiving side to the subscriber terminal on the receiving side, and the subscriber terminal on the receiving side interprets the script in the received message with an interpreter including a library function prepared in advance, and processes the received message. A method for enhancing MHS functions, which is characterized by executing. 3. The MHS advanced method according to claim 2, wherein the script uses control data,
The control data structure is described in abstract syntax notation, the script and control data structures are stored in the first external definition body part of the message, and the control data values are stored in the second external definition body part. The subscriber terminal executes a script based on a structure of control data and a value of the control data.