KR20080022809A - Method and system for transmitting email assigned a plurality of recipients - Google Patents

Abstract

A method for sending mail where plural receivers are designated in a mobile communication system and a system therefor are provided to transmit template messages configured to personalize partial contents of one mail according to each receiver, and to configure personalized mail for each receiver to send the personalized mail, thereby inducing fast replies from each user. A mobile communication terminal(110) sets mail by personalizing partial contents of the mail so that the partial contents are provided to partial receivers only, by inserting index tags assigned for each receiver and predetermined template tags into contents of the mail, configures other contents except the partial contents as template messages set to be commonly provided to all receivers, and sends addresses of each receiver, and then transmits the template messages. A submit server(120) receives the addresses, assigns indexes to the addresses, configures mail corresponding to each receiver in reference to the assigned indexes, and then sends the configured mail to the corresponding receivers.

Description

METHOOD AND SYSTEM FOR TRANSMITTING EMAIL ASSIGNED A PLURALITY OF RECIPIENTS}

1 is a view showing a conventional mail transmission process;

2 is a diagram showing the configuration of a mobile communication system to which the present invention is applied;

3 is a diagram showing the configuration of a mobile communication terminal according to an embodiment of the present invention;

4 is a view showing an operation process of a mobile communication terminal according to an embodiment of the present invention;

5 is a diagram illustrating a mail transmission process according to an embodiment of the present invention.

The present invention relates to a messaging service of a mobile communication system, and more particularly, to a method and system for transmitting a mail to which a plurality of recipients are designated in a mobile communication system.

Mail has been a major messaging service for a long time and has evolved highly to accommodate a variety of needs. The recent trend is to provide a mail service using a mobile communication terminal, and much effort has been made to establish a common framework interoperable within a standard organization.

In general, at the current technology level, the architecture for mobile mail based on the IETF standard is based on the Mail User Agent (MUA), the submit server, the Internet Message Access Protocol (IMAP) storage, and mail delivery. Agent (Mail Transfer Agent: MTA) and notification mechanism (notification mechanism). MUA is a mail client that reads received mail and sends mail written for you. The submission server receives and accepts mail from the MUA and submits it to the MTA. As defined by the IETF, the protocol used between the MUA and the submission server is a submit protocol, which in fact is an extended Simple Mail Transfer Protocol of SMTP with added restrictions or permissions. The submission server may modify the mail received from the MUA prior to final submission to conform to some existing policy or to follow the sender's specific instructions through the MUA. An IMAP storage device is a mail server that stores all incoming messages, sends a corresponding notification to the user, and interacts with the MUA to perform retrieval using IMAP. The MTA delivers the message to the receiver. More than one MTA can be included for delivery, which allows certain MTAs to receive messages from other MTAs and relay them. When the MTA last relays an incoming message, it stacks the message on the IMAP storage device. When the MTA relays an outgoing message for the first time, it is common to receive the message submitted from the submission server 20 and deliver the message to the MTA relaying to the next. The notification mechanism sends a notification related to the receipt of mail by the IMAP storage device to the MUA. This is to inform the arrival of new mail. Such a notification mechanism can be realized by various techniques such as, for example, a short message server or SIP.

SMTP delivers a mail object consisting of two parts: the SMTP envelope and the SMTP content. The SMTP envelope consists of a series of protocol units that inform the submission server 20 and other network elements about the sender (MAIL FROM) and the receiver (RCPT TO) for routing and delivery purposes, and about possible protocol extensions. SMTP content is divided into two parts: the header part and the body part. The header contains a series of field names and values, for example field names such as From :, To: and Subject :, which are displayed to the receiving user and are not used for routing / forwarding purposes. The body contains the actual message.

The transaction flow between the MUA and the submission server of the general mobile communication mail architecture configured as described above will be described with reference to FIG. 1 is a view showing a conventional mail transmission process. The MUA 10 requests connection with the submission server 20 in step 11 if a transmission request is made after the mail configuration in which one or more recipients are set according to a user input is completed. The submission server 203 connects with the MUA according to the connection request of the MUA 10, and responds to the connection request to the MUA 10 using the 220 code in step 13. In this case, the 220 code may be configured, for example, "220 server.com Simple Mail Transfer Service Read". Thereafter, in step 15, the MUA 10 transmits an Extended Hello (EHLO) command, for example, "EHLO client.com" to the submission server 20. The EHLO command has two purposes, the first is to send the MUA 10's identification information to the submission server 20, the second is to confirm that the MUA 10 supports basic SMTP service extension requests, It is asking the submission server 20 to send a list of extensions it supports. If the MUA 10 cannot handle or want any service extension, it can send a HELO command. The submission server 20 receives the EHLO command in step 15 to approve the EHLO or HELO command, and in step 17 transmits the EHLO command response using the 250 code. In this case, the 250 code may be configured, for example, 250 server.com welcomes client.com. Subsequently, the submission server 20 retrieves the extended service list, and configures 250 codes corresponding to each of the extended services in step 19 to transmit them to the MUA 10. In this case, the 250 code may be, for example, 250 8BITMIME, 250 HELP, and the like. Receiving a list of all expanded services from the submission server 20, the MUA 10 transmits a MAIL FROM command identifying a sender's mailbox in step 21, to initiate a mail transaction. That is, the MAIL FROM command includes the sender's mail address and may be, for example, MAIL FROM: <sender@client.com>. The submission server 20 responds to the received MAIL FROM command by transmitting a 250 code, that is, 250 OK in step 23, and accepts the MAIL FROM command. Upon receiving the MAIL FROM command response, the MUA 10 transmits an RCPT TO command for identifying the recipient mailbox in step 25. That is, the RCPT TO command includes a recipient mail address and may be, for example, RCPT TO: <recipient@dest.com>. The submission server 20 receives the RCPT TO command, accepts it, and transmits a 250 OK using the 250 code to the MUA 10 in step 27 to transmit the RCPT TO command response. At this time, if multiple recipients are set for the same mail, steps 25 and 27 are repeated for each recipient. When the RCPT TO command transmission corresponding to the preset receiver is completed, the MUA 10 transmits a DATA command to the submission server 20 in step 29 to request transmission of mail data. The submission server 20 having received the DATA command allows mail data transmission, thereby authorizing the MUA 10 to send mail data by sending a DATA command response using the 354 code. When the MUA 10 receives the DATA command response, the MUA 10 transmits mail data including a header part and a body part in step 33. Mail data can span several lines, terminated by a line containing only "." This last line informs the submission server 20 that it has received the end of the mail data and can proceed with subsequent procedures. After receiving and successfully storing all the mail data, the submission server 20 transmits 250 OK to the MUA 10 in step 35 and responds that the mail data reception is normally performed. Subsequently, in step 37, the submission server 20 processes the received message. That is, it transmits to the appropriate MTA according to the location of the recipient mailbox. Meanwhile, the MUA 10 sends a QUIT command to the submission server 20 to terminate the SMTP connection at any time. The submission server 20 approves the received QUIT command, transmits the QUIT response using the 221 code in step 41, and then closes the transmission channel.

Mail is transmitted according to the above process, it is possible to send the same mail to multiple recipients. This is possible by separately transmitting the RCPT TO command for each set receiver as described above. However, a sender may want to send a personalized mail with a personal message corresponding to each recipient while keeping the same basic content for multiple recipients. As a typical example, you may want to send mail of the same contents to users A and B, with one mail starting with "dear A user" and the other starting with "dear B user." Mail written in this way is particularly useful when the sender wants to give the recipient the impression that the recipient is the only person who receives the mail, so that the intended recipient can reply quickly when requesting a reply compared to sending a message to a group of recipients. Can be induced. Another reason for the need for personalized mail is that the sender may need to deliver certain parts of the message to only some of the recipients and allow the rest of the message to be accessible to all recipients. In addition, the sender may want to display a different originating mail address for each recipient. That is, there may be a case in which the sender manages different types of mail address accounts in correspondence with the recipient classification. For example, you may manage your family, co-workers, American friends, and Canadian friends using different mail accounts. In this case, the sender may want to display only a mail address corresponding to the recipient's classification criteria in a part indicating the sender address while sending similar messages to various types of recipients, thereby receiving a reply from the corresponding mail account.

In the conventional mail, the above object can be achieved by creating and sending a separate mail for each recipient or classification criteria of each recipient. However, this is too cumbersome for the sender when there are many recipients. And in the case of mobile mail, since the interaction between the MUA 10 and the submission server 20 uses radio resources, sending a large number of personalized mails directly from the MUA 10 consumes a lot of bandwidth and time, This is especially true if the mail is large and has a large number of recipients.

Accordingly, the present invention provides a mail transmission method and system that can conveniently send a personalized mail corresponding to each recipient when a plurality of recipients are set.

The present invention provides a mail transmission method and system that can minimize the consumption of radio resources.

The present invention provides a mail transmission method and system that can improve the reply rate.

According to the present invention for achieving the above object, in a mail transmission method in which a plurality of recipients are designated in a mobile communication system, the mobile communication terminal corresponds to each recipient when setting the plurality of recipients according to a user input. The template message set by inserting an assigned index tag and a predetermined template tag into the contents of the mail, personalizing some contents to be provided to only a part of designated recipients, and setting contents to be provided to all recipients in common except for the partial contents. And transmitting, by the mobile communication terminal, the address of each recipient according to the assigned index order according to the template message transmission request, and receiving the recipient address by the submission server. Assigning an index to the recipient address in order; The communication terminal transmits the template message, and the template message received by the submission server refers to the index tag and the template tag inserted into the mail with reference to the assigned index. And constructing a mail corresponding to the recipient and transmitting the mail to the recipient.

The present invention provides a mail transmission system in which a plurality of recipients are designated in a mobile communication system, wherein the mail is assigned an index tag and a predetermined template tag which are assigned to each recipient when setting the plurality of recipients according to a user input. By inserting into the contents of the mail, some contents are set to be personalized to be provided only to the designated partial recipients, and the contents except the partial contents are composed of template messages set to be provided to all recipients in common, and according to the request for transmitting the template message Receiving a mobile communication terminal for transmitting the address of each recipient according to the assigned index order, and receiving the template message, and each of the recipient address, assigning an index to the recipient address in the receiving order, In the template message, the assigned index is true In accordance with the index tag and set by the template tag inserted in the message by constructing a message corresponding to each of the receivers it includes a submission server sending to the recipient.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings. Note that the same components in the drawings are represented by the same reference numerals and symbols as much as possible even though they are shown in different drawings. In addition, in describing the present invention, when it is determined that a detailed description of a related known function or configuration may unnecessarily obscure the subject matter of the present invention, the detailed description thereof will be omitted.

First, a mobile communication system to which the present invention is applied will be described with reference to FIG. 2 is a diagram illustrating a configuration of a mobile communication system to which the present invention is applied. Referring to Figure 2 the mobile communication system

Mobile communication terminal 110, submit server 120, IMAP (Internet Message Access Protocol) storage device 130, and first and second Mail Transfer Agents (MTAs) 150, 160 ), A notification server (140), and a mobile communication network (170). The objects may map to objects defined in the OMA standard organization. In other words, the submission server 120 and the IMAP storage server 130 correspond to a combination of a MEM server and an email server, and the notification mechanism may be provided by anyone other than the MEM service enabler. For simplicity, only IETF terminology will be used, but it is assumed that all the objects described below can also be applied to the corresponding objects defined in the OMA.

The mobile communication terminal 110 is a mail user agent, which is a mail client that transmits a mail created by a user and provides the received mail to the user. In particular, the mobile communication terminal 110 composes and transmits a template message according to an embodiment of the present invention when sending a mail according to a user selection. The template message refers to a message configured to personalize the contents of the arbitrary mail corresponding to each recipient when a plurality of recipients are set in any mail. Template message is composed of a message including a predetermined template tag according to an embodiment of the present invention, the message contained in the template tag is specified only to the recipients specified by the parameters included in the template tag, thereby creating a number of mails Depending on the recipient of the mail can be sent slightly different content. The mobile communication terminal 110 sets a template message composition mode when a user requests to create a template message. Thereafter, the index tag is allocated in correspondence with the setting order of the plurality of template message receivers selected by the user. Then, the template tag, the index tag and the message content are combined according to the user input to create a template message and transmit it to the submission server 120. When transmitting the template message, the mobile communication terminal 110 transmits the recipient address to the submission server 120 in the index tag assignment order.

The submission server 120 receives and accepts a mail from the mobile communication terminal 110 and submits it to the first MTA 150. At this time, the protocol used between the mobile communication terminal 110 and the submission server 120 is an extended version of the SMTP (Extended Simple Mail Transfer Protocol) to which restrictions or permissions are added. The submission server 120 may modify the mail received from the mobile communication terminal 110 prior to final submission to conform to some existing policy or to follow the sender's specific command through the mobile communication terminal 110. The submission server 120 transmits the received mail to the first MTA 150. In other words, when the submission server 120 receives a mail transmission request from the mobile communication terminal 110 according to the present invention, the submission server 120 confirms whether the transmitted mail is a template message. When the mail to be transmitted is a template message, the submission server 120 assigns an index to each recipient address in response to the received order when receiving the recipient address associated with the template message. That is, the submission server 120 assigns an index corresponding to the index tag assigned by the mobile communication terminal 110 to each recipient address to the received recipient address. Subsequently, upon receiving the arbitrary template message, the submission server 120 searches and combines the assigned index with the template tag included in the received template message or the caller's phone book, and configures mail to be transmitted for each recipient. When the submission mail configuration of each recipient is completed, the submission server 120 transmits the mail to the first MTA 150 to transmit the mail to the corresponding recipient.

The first MTA 150 and the second MTA 160 transmit the mail to the receiving side. More than one MTA can be included for the delivery of mail, which allows a given MTA to receive messages from other MTAs and relay them. IMAP storage server 130 is a mail server that stores all incoming mail, sends a corresponding notification to a user, and interacts with mobile communication terminal 110 to perform a search using IMAP. The notification server 140 transmits a notification related to the reception when the mail to be received by the mobile communication terminal 110 is stored in the IMAP storage server 130. This is to inform the arrival of new mail. Such notification server 140 may be realized by various techniques such as, for example, a short message server or a SIP.

A detailed operation process and a template message of the mobile communication terminal 110 according to an embodiment of the present invention in the mobile communication system configured as described above will be described with reference to FIG. 3. 3 is a diagram illustrating a configuration of a mobile communication terminal according to an embodiment of the present invention. Referring to FIG. 3, the mobile communication terminal 110 includes a control unit 111, a memory unit 113, a display device 115, a key input unit 117, a baseband processing unit 119, and an RF (Radio Frequency) module 121. ), And includes a voice processing unit 123. The controller 111 controls the overall operation of the mobile communication terminal.

The display device 115 displays various image information and images received from the mobile communication network 170 or stored in the memory 113 on the screen under the control of the controller 111. The key input unit 117 includes a plurality of function keys, such as a menu, a selection, a call, a clear, a power / end, a volume, and a photograph, corresponding to the *, # keys, and various functions of the mobile communication terminal. The control unit 111 provides key input data corresponding to a key pressed by the user. The RF module 121 transmits and receives a radio signal with the mobile communication network 170 through an antenna. The RF module 121 modulates a signal to be transmitted from the control unit 111 through the baseband processor 119 to convert the RF signal into an antenna. And demodulates an RF signal received through the antenna and provides the demodulated RF signal to the controller 111 through the baseband processor 119. The baseband processor 119 processes baseband signals transmitted and received between the RF module 121 and the controller 111. The voice processing unit 123 connected to the control unit 111 and the microphone MIC and the speaker SPK connected to the voice processing unit 123 are used for phone calls and voice recording.

The memory unit 113 stores a program for processing and controlling the control unit 111, reference data, various updatable storage data, a phone book, and the like, and is provided as a working memory of the control unit 111. . According to an embodiment of the present invention, the memory unit 113 stores program data necessary for constructing the template message and a template tag related to the template message format.

The template tag serves to personalize the contents included in the tag corresponding to a specific receiver. That is, the content contained in the template tag is valid only for the recipient specified by the parameter included in the tag. According to an embodiment of the present invention, when creating a template message, a user may directly input a recipient address to set a plurality of template message recipients or set up a plurality of template message recipients using a phone book. Accordingly, the template tag may be configured to include a basic template tag and parameters used when a user inputs a recipient address directly to set a template message recipient, and a phone book template tag and parameters used when using a phone book.

 The default template tag contains an individualization tag that personalizes the contents of the tag, and designation and separation parameters that specify the receiver. Basic template tags can be represented by <tdat> and </ tdat> tags, for example. Accordingly, all data included between the <tdat> and </ tdat> tags are considered personalized data. In addition, the default template tag <tdat> may include a specific parameter and a separate parameter. An assignment parameter that specifies the recipient associated with the personalized data can be represented by rcpt. The rcpt parameter indicates to which receiver the personalized data is applicable and accepts as value one or more numbers corresponding to the assigned index tag corresponding to the template receiver set by the user. For example, if a template message is addressed to the first and third recipients, and index tags of 1,2 and 3 are sequentially assigned to each receiver, the default template tag including the rcpt parameter is <tdat rcpt = 1, 2,3>. Or <tdat rcpt = 1-3>. Separation parameters can be represented by the / tdat / parameter. The / tdat / parameter can separate personal data between <tdat> and </ tdat> tags and can be used as an alternative to the rcpt parameter. The / tdat / parameter can simplify the notation when it is necessary to send personal data to multiple recipients each. For example, when specifying 10 recipients, the tag can be constructed as follows using the rcpt parameter.

<tdat rcpt = 1> ... </ tdat> <tdat rcpt = 2> ... </ tdat> (...) <tdta rcpt = 10> ... </ tdat>

In the above case, if the / tdat / parameter is used, the notation can be simplified in the following manner.

<tdat> ... / tdat /(...)/ tdat /...</ tdat>

That is, / tdat / is used 9 times to separate 10 personal data. The submission server 20 basically assumes that the first part is assigned to the first receiver and the second part is assigned to the second receiver. If the assignment starts for a different user, you can use the rcpt parameter in combination with the / tdat / parameter. That is, personal data of the users 7 to 10 may be represented as follows.

<tdat rcpt = 7> ... / tdat /.../ tdat /.../ tdat /...</ tdat>

Table 1 below shows an example of configuring a template message when Alice, Bob, and Claire are set as template recipients, and corresponding index tags of 1, 2, and 3 are assigned. .

-Start message-- From: Dave Brown << tdat rcpt = 1,2> dbrown@friends_account.com </ tdat> <tdat rcpt = 3> dbrown@colleagues_account.com </ tdat >> To: <tdat rcpt = 1> Alice Smith <alice_smith@accountA.com> </ tdat> <tdat rcpt = 2> Bob Johnson <bob_johnson@accountB.com> </ tdat> <tdat rcpt = 3> Claire Williams <Claire_williams@accountC.com> < / tdat> From Friday, May 19, 2006 Subject: Party Invite Dear <tdat rcpt = 1> Alice </ tdat> <tdat rcpt = 2> Bob </ tdat> <tdat rcpt = 3> Claire </ tdat >, Next Monday we would like to invite you to a party to our new home. (Party content) Will you come? Please let me know. Dave Dream <tdat rcpt = 1> PS: How about playing tennis this Sunday? </ Tdat> --End of message--

Looking at Table 1 above, the From: field line of the template message is configured so that the address of the friend's account, that is, friends_account.com is displayed to Alice and Bob, and Claire is displayed to colleagues_account.com. The To: field line indicates that only addresses corresponding to each recipient should be displayed. That is, because there are three recipients, three personalized mails are generated from the template message. Referring to Table 1, the first line of the text part names each of the recipients (dear Alice, dear Bob, dear Claire), and the main part of the message is common to all. However, the PS: section at the bottom is configured to be delivered only to Alice and not to Bob or Claire. Using the / tdat / separation parameter, the first line of the body of the example can be variously written as follows.

-Dear <tdat rcpt = 1> Alice </ tdat> <tdat rcpt = 2> Bob </ tdat> <tdat rcpt = 3> Claire </ tdat>,

-Dear <tdat> Alice / Tdat / Bob / tdat / Claire </ tdat>,

-Dear <tdat rcpt = 1> Alice </ tdat> <tdat rcpt = 2> Bob / tdat / Claire </ tdat>

As the number of recipients increases, the second notation becomes the simplest notation. The basic template tag and each parameter may be directly input by the user by using a character key, or may be input by calling a stored format corresponding to each tag and parameter through a menu or the like.

The mobile communication terminal 110 transmits the recipient address to the submission server 120 according to the index tag order assigned to the template recipient after completing the template message preparation as shown in Table 1 above. Send a template message of 1.

The submission server 120 allocates and stores an index corresponding to the reception order of the recipient address, and receives the template message shown in Table 1 from the template message in Table 1 using the index assigned to the recipient address. Compose a mail like 3,4 and send it to the recipient.

-Alice starts receiving messages-From: Dave Brown <dbrown@friends_account.com> To: Alice Smith <alice_smith@accountA.com> From Friday, May 19, 2006 Subject: Party Invitation Dear Alice, Next Monday We Would like to invite you to a party at your new home. (Party content) Will you come? Please let me know. Dave Dream PS: How about playing tennis this Sunday? --End Alice incoming message--

--Bob Start Message ---- From: Dave Brown <dbrown@friends_account.com> To: Bob Johnson <bob_johnson@accountB.com> From: May 19, 2006 Subject: Party Invitation Dear Alice, Next Monday We Would like to invite you to a party at your new home. (Party content) Will you come? Please let me know. Dave Dream-End of Bob's Received Message--

-Claire starts receiving messages-From: Dave Brown <dbrown@colleagues_account.com> To: Claire Williams <claire_williams@accountC.com> From Friday, May 19 Subject: Party Invitation Dear Alice, Next Monday We Would like to invite you to a party at your new home. (Party content) Will you come? Please let me know. Dave Dream-End of Claire's Inbox

Meanwhile, in another embodiment of the present invention, a template message may be configured using a phone book. If information about the recipient is stored in the sender's phone book, when attempting to refer to any personal data in the template message, the sender can simply refer to the data in the phone book without having to explicitly specify personal data for each recipient. There is convenience. The phone book template tag is used for this. The phone book template tag performs the same function as the basic template tag, and instructs the submission server 20 to withdraw specific data stored in the phone book. In this case, it is assumed that the mobile communication terminal 110 and the submission server 120 are shared with the submission server 20 of the phone book. The phone book template tag may be composed of <tdat_ab> ("ab" means address book). The phone book template tag <tdat_ab> may include a phone book address parameter, a designation parameter, and a field designation parameter. The address parameter may be represented by a url, which indicates the location of the phone book, and represents any URL (Uniform Resource Locator) syntax defined by the IEFT standard (RFC 1738) if the phone book is not located in the submission server 20. Accept as a value. The url parameter is automatically included in the template message when the phone book template tag is inserted into the template message. The designated parameter can be expressed as rcpt, and it is a parameter that designates a receiver related to personalized data included in the phone book template tag, that is, a parameter which designates receivers to be searched in the phone book. Accept as. The rcpt parameter is identical to the rcpt parameter in the <tdat> tag, which is the default template tag. The field designation parameter can be expressed as fields, and is a parameter for designating a field to be searched and displayed in the mail among various fields constituting the phone book. In other words, the fields parameter is used to substitute data to be included in various user data stored in the phone book, for example, data of the registered user's name, phone number, address, email address, nickname, etc. This parameter specifies the corresponding storage field to include the data in the mail. If the mail contains the recipient's name, instead of typing the name directly, the name field of the phonebook field is specified using the <tdat_ab> tag, the rcpt parameter, and the fields parameter at that location.

In the template message of Table 1, a template message is configured as follows to transmit three personalized messages corresponding to each recipient, such as "Dear Alice, Dear Bob, and Dear Claire".

-Dear <tdat rcpt = 1> Alice </ tdat> <tdat rcpt = 2> Bob </ tdat> <tdat rcpt = 3> Claire </ tdat>

In this case, the caller had to manually enter three names: Alice, Bob, and Claire. If the three recipients are registered in the phone book, the template message may be configured using the phone book. First, the sender sets the three users among the users registered in the phone book as recipients of the template message. At this time, the index tag is sequentially assigned by the control unit 111 according to the template message receiver setting order corresponding to each receiver, and at this time, the address of the phone book corresponding to each receiver is included in the template message together with the assigned index. It is done. After that, the name field in which Alice, Bob, and Claire are stored is designated as a field parameter value among a plurality of fields constituting the phone book by the user, thereby making "dear Alice, dear Bob, dear Claire" practical. The template message may be configured as follows.

Dear <tdat_ab rcpt = 1-3 fields = Name>

Other parts of the mail may be configured by combining the phone book template tag, the rcpt parameter, and the fields parameter in the same manner as described above, and the basic template tag and the phone book template tag may be mixed when configuring one template message. The same applies to the setting of the recipient of the template message, and the index tags are sequentially assigned according to the order of setting the recipient. When the recipient is set using the phone book, the address tag is included in the template message together with the assigned index tag. The phone book template tag and each parameter may be directly input by the user by using a text key, or may be input by calling a stored format corresponding to each tag and parameter through a menu or the like.

The mobile communication terminal 110 transmits the recipient address to the submission server 120 according to the index tag order assigned to the template recipient after the template message is completed and the mail transmission request is received from the user, and transmits the template message.

The submission server 120 allocates and stores an index corresponding to the reception order of the recipient address. When the template message is received, the mail corresponding to each recipient is composed and sent to the corresponding recipient using the template tag included in the template message and the index assigned to the recipient address. If the template message includes the phone book template tag, the submission server 20 accesses the sender's phone book and corresponds to the field specified by the fields parameter in the user data corresponding to the receiver specified by the rcpt parameter in the template message. Organize your email by extracting stored values.

The operation of the mobile communication terminal 110 is shown in FIG. 4 is a diagram illustrating an operation process of the mobile communication terminal 110 according to an embodiment of the present invention. When the template message creation mode is set, the mobile communication terminal 110 checks whether there is a phone book use request from the user in step 201, and proceeds to step 207 if there is a phone book use request, and proceeds to step 203 if there is no phone book use request. Proceed. In step 203, the mobile communication terminal 110 sets a template message receiver according to a user input, sequentially assigns an index tag to the template message receiver, and proceeds to step 205. In step 205, the mobile communication terminal 110 configures a template message as shown in Table 1 by using a basic template tag, an index tag, and body data according to a user input.

On the other hand, the mobile communication terminal 110 proceeds to step 207 to display the phone book list if the user has requested to use the phone book in step 201. Thereafter, in step 209, a template message receiver is set among the users registered in the phone book in response to the user input, the index tag corresponding to the storage address of each receiver is sequentially assigned and stored together with the corresponding address, and the procedure proceeds to step 211. . In step 211, the mobile communication terminal 110 configures a template message using the phone book template tag, the index tag and the body data according to a user input, and proceeds to step 213.

In step 213, when the template message is completed, the mobile communication terminal 110 proceeds to step 215, and detects a transmission request. If there is a transmission request, the mobile communication terminal 110 proceeds to step 217 and submits the template message configured in the step. To send.

5 illustrates a transaction between the mobile communication terminal 110 and the submission server 120 in order for the mobile communication terminal 110 to transmit the template message to the submission server 120. 5 is a diagram illustrating a mail transmission process according to an embodiment of the present invention.

 Referring to FIG. 5, if there is a request for transmission of a template message, the mobile communication terminal 110 requests access to the submission server 120 in step 301. The submission server 120 connects to the mobile communication terminal 110 according to the connection request of the mobile communication terminal 110, and responds to the mobile communication terminal 110 using the 220 code in step 220. In this case, the 220 code may be configured, for example, "220 server.com Simple Mail Transfer Service Ready". In step 307, the mobile communication terminal 110 transmits an extended hello (EHLO) command, for example, "EHLO client.com", to the submission server 120. The EHLO command has two purposes, the first of which sends identification information of the mobile terminal 110 to the submission server 120, and the second of which the mobile terminal 110 supports basic SMTP service extension requests. To request submission server 120 to send a list of extensions it supports. The submission server 120 receives the EHLO command in step 305 to approve the EHLO command, and in step 307 transmits the EHLO command response using the 250 code. In this case, the 250 code may be configured, for example, 250 server.com welcome client.com. Subsequently, the submission server 120 searches for the expanded service list, and configures 250 codes corresponding to each of the extended services in step 309 and transmits them to the mobile communication terminal 110. In this case, the 250 code may be, for example, 250 8BITMIME, 250 HELP, and transmits 250 TEMPL which means that the template message function is supported. The mobile communication terminal 110, which has received all the extended service list from the submission server 120, transmits a MAIL FROM command for identifying the sender's mailbox in step 311 to initiate a mail transaction. That is, the MAIL FROM command includes the sender mail address, and may be, for example, MAIL FROM: <sender@client.com>. The submission server 120 transmits a 250 code, that is, 250 OK to the received MAIL FROM command in step 313, and accepts the MAIL FROM command. In response to receiving the MAIL FROM command response, the mobile communication terminal 110 transmits an RCPT TO command for identifying a receiver mailbox. That is, the RCPT TO command includes a recipient mail address and may be, for example, RCPT TO: <recipient@dest.com>. Since the template message has a plurality of recipients set, the mobile communication terminal 110 transmits the recipient address in the RCPT TO command in the order corresponding to the index tags assigned to the plurality of recipients set in the template message. When the submission server 120 receives the RCPT TO command from the mobile communication terminal 110 in step 317, the submission server 120 receives the RCPT TO command, and assigns an index to the received recipient address according to the reception order. Subsequently, in step 319, the submission server 120 transmits the 250 OK using the 250 code to the mobile communication terminal 110 to transmit the RCPT TO command response. The mobile communication terminal 110 transmits a TDATA command to the submission server 120 in step 321 to request transmission of a template message. The TDATA command indicates that the mail to be transmitted is a template message, and includes some specific instructions on how to generate a personalized message from the template message. The submission server 120 receiving the TDATA command grants mail data transmission, and accordingly, in step 323, the TDATA command response is transmitted using the 354 code to authorize the mobile communication terminal 110 to transmit the mail data. . When the mobile communication terminal 110 receives the TDATA command response, the mobile communication terminal 110 transmits mail data consisting of a template message in step 325. After receiving and successfully storing all the template messages, the submission server 120 transmits 250 OK to the mobile communication terminal 110 in step 327 and responds that mail data has been received normally. Thereafter, in step 329, the submission server 120 processes the received template message. That is, the submission server 120 corresponds to each template recipient from the template message by using the index assigned to the recipient address and the basic template tag included in the template message, the phone book template tag, various parameters, and the phone book. Mails, for example, mails such as Tables 2, 3, and 4, are configured and sent to the corresponding recipients.

Meanwhile, in step 331, the mobile communication terminal 110 transmits a QUIT command to the submission server 120 to terminate the SMTP connection. The submission server 120 accepts the received QUIT command, transmits a QUIT response using the 221 code in step 333, and then closes the transmission channel.

In the above description of the present invention, specific embodiments have been described, but various modifications may be made without departing from the scope of the present invention. For example, although the index tag assignment of the mobile communication terminal 110 to the template message receiver is configured to be performed sequentially according to the setting order, another embodiment of the present invention may be configured to be assigned according to user selection. The scope of the invention should not be defined by the described embodiments, but should be determined by the equivalents of the claims and claims.

As described above, in the present invention, when a plurality of recipients are set for one mail, the mobile terminal transmits a template message configured to personalize a part of the contents of one mail for each recipient by using a specific tag, and receives the received message. A submission server constructs individualized mail for each recipient from a template message and sends it to that recipient, giving the sender the impression that the recipient is the only person who receives the mail, and can promptly respond to the message. A specific part can only be delivered to some of the many recipients. In addition, a plurality of recipients can conveniently send a personalized mail corresponding to each recipient when the set mail is transmitted, and minimize the consumption of radio resources.

Claims (10)

In the mobile communication system, a plurality of recipients specified mail transmission method, The mobile communication terminal inserts the mail according to the user input, the index tag assigned corresponding to each recipient when setting the plurality of recipients, and the predetermined template tag into the contents of the mail, so that some contents are provided to only some designated recipients. A process of configuring a template message set to be personalized to be set as possible, and the contents except for the partial contents are provided to all recipients in common; Transmitting, by the mobile communication terminal, an address of each receiver according to the allocated index order according to the template message transmission request; Receiving, by the submission server, each of the recipient addresses, and assigning an index to the recipient addresses in a receiving order; Transmitting, by the mobile communication terminal, the template message; In the template message received by the submission server, a mail corresponding to each recipient is configured and transmitted to the corresponding recipient according to the index tag and the template tag inserted in the mail with reference to the assigned index. Mail transmission method comprising a process. The method of claim 1, wherein the process of configuring the template message of the mobile communication terminal includes the selected user among the users registered in the phone book shared with the submission server, according to user selection. And configuring the template message by setting user data stored in the phone book to be used when setting personalized content in relation to the selected user. 3. The template tag of claim 2, wherein the template tag is a basic template tag for individualizing the partial content included between the tags to be provided only to any designated recipients, and the optional partial content to be provided using the index tag. A designation parameter for designating a receiver, a phone book template tag for instructing the partial contents contained between the tags to be provided only to any designated receiver, and instructing to detect data stored in the phone book, and a storage location of the phone book And an address parameter including a field parameter and a field parameter for specifying a field to be searched and displayed in the mail among various fields constituting the phone book. The method of claim 3, wherein in the process of configuring a template message of the mobile communication terminal, Setting a plurality of recipients as a plurality of recipients according to a user's selection, a user selected directly from a user and a user registered in a phone book shared with the submission server; Assigning the index tag to each of the plurality of recipients; Configuring the template message by inserting the index tag, the basic template tag, the designation parameter, the phone book template tag, the address parameter, and the field parameter into the mail content according to a user selection. Mail transmission method comprising the. The process of claim 4, wherein the submission server constructs and sends a mail corresponding to each of the recipients. Receiving the template message; Analyzing the template message to identify the template tag included; Including contents not included in the template tag and contents included in a basic template tag among the template tags in an e-mail related to a recipient designated by a designated parameter included in the basic template tag; The user data corresponding to the field specified by the field parameter included in the phone book template tag among the user data stored in the phone book in relation to the receiver specified by the designated parameter included in the phone book template tag among the template tags. Detecting and including the detected user data, contents not included in the template tag, and contents included in the phone book template tag in an e-mail related to the recipient designated by the designated parameter; And sending the mails to the corresponding recipients. In a mail transmission system in which a plurality of recipients are designated in a mobile communication system, According to a user input, an index tag assigned corresponding to each recipient when setting the plurality of recipients, and a predetermined template tag are inserted into the contents of the mail, and the contents are personalized to be provided only to the designated partial recipients. The content except for the partial content is configured as a template message set to be provided to all recipients in common, and according to the template message transmission request, the address of each recipient is transmitted in the assigned index order, and the template message is transmitted. A mobile communication terminal for transmitting a; Receiving each recipient address, assigning an index to the recipient address in the receiving order, and setting the index tag and the template tag inserted in the mail by referring to the assigned index in the received template message And a submission server configured to transmit the mail corresponding to each of the recipients to the corresponding recipients. The mobile communication terminal of claim 6, wherein the mobile communication terminal includes, according to a user selection, a selected user among users registered in a phone book shared with the submission server in the plurality of recipients, and sets personalized contents in relation to the selected user. And the user data stored in the phone book is used. 8. The template tag of claim 7, wherein the template tag is a basic template tag for individualizing the partial content included between the tags to be provided only to any designated recipient, and the optional partial content to be provided using the index tag. A designation parameter for designating a receiver, a phone book template tag for instructing the partial contents contained between the tags to be provided only to any designated receiver, and instructing to detect data stored in the phone book, and a storage location of the phone book And an address parameter including a field parameter and a field parameter for specifying a field to be searched and displayed in the mail among various fields constituting the phone book. The mobile communication terminal of claim 8, wherein the mobile communication terminal sets the selected user among the recipients directly input from the user and a user registered in the phone book shared with the submission server according to user selection, and the plurality of recipients. Assign the index tag to each of the recipients, and assign the index tag, the basic template tag, the designation parameter, the phone book template tag, the address parameter, and the field parameter to the mail according to a user selection. And inserting the contents into the template message to form the template message. The basic template of claim 9, wherein the submission server analyzes the received template message to identify the included template tag, and the content not included in the template tag and the content included in the basic template tag among the template tags. The phone book template of the user data stored in the phone book in association with the recipient specified by the designated parameter included in the tag and included in the mail related to the recipient specified by the designated parameter included in the tag. Detects user data corresponding to a field specified by the field parameter included in a tag, and detects the detected user data, contents not included in the template tag, and contents included in the phone book template tag. The receiver specified by the specified parameter in the template tag, Ryeondoen included in the mail and mail transmission system, characterized in that said mail sent to that recipient.

Images