WO2009065251A1

WO2009065251A1 - Method, device and system for sending and transmitting message

Info

Publication number: WO2009065251A1
Application number: PCT/CN2007/003289
Authority: WO
Inventors: Xiaohui Wei
Original assignee: Lucent Technologies Inc.
Priority date: 2007-11-21
Filing date: 2007-11-21
Publication date: 2009-05-28
Also published as: CN101816152A

Abstract

A method for communicating between a sender and a transmitter is provided. The method includes the steps: establishing a sending message at the sender, wherein the message includes the third party identifier manage entries for storing the third party identifier, and the third party identifier expresses the third party which the transmitter subsequently transmits the message to; the sender sends the message to the transmitter; the transmitter receives the message; the transmitter takes out at least one of the third party identifiers in the third party identifier manage entries of the received message; the transmitter transmits the received message as another message to the third party which is expressed in the taken out the third party identifier. The efficiency of the e-mail sending and transmitting in the e-mail system are improved and the process is predigested by this method of this invention.

Description

Method, device and system for transmitting and forwarding messages

The present invention relates to the field of information technology and, more particularly, to a method, apparatus and system for transmitting and forwarding messages. Background technique

With the rapid development of Internet technology, the use of e-mail for communication has become widespread. In an email system, user A (for example, a company boss) sometimes needs to send the same email to a group of multiple recipients C (for example, multiple clients). In most cases, User A is very busy and has no time to write this email. Thus, User A can request User B (such as an assistant or secretary) to write the email for it. After completing the writing of the email, User B sends the email to User A. User A then makes the appropriate edits to receive the email as a new email to multiple recipients (:.

However, since the recipient C of the email is a plurality of people, the "to" field in the header of the email is sometimes very long. Therefore, in this case, User A takes a long time to enter the recipient's address in the header "To" field of the email.

In this regard, the existing solution mainly includes the following steps: First, User B sends a separate email to User A, the body of the separate email containing the detailed email addresses of multiple recipients C; After receiving the separate email from User B, User A copies the email address of recipient C contained in the body to the "To" field in the header of the new email, and finally sends it.

Fig. 1 is an exemplary illustration for describing a user interface of an electronic mail in the prior art. As shown in Figure 1, User A (company boss)'s email address is boss@nil.test, which wants to notify multiple recipients C, such as Jack and Jerry (the email addresses are respectively

Confirmation Jack (3⁄4machine. example and ierry(3⁄4machine.example ) about the meeting schedule. User A asks User B (Secretary) to draft an email for it. So, in addition to the message body that User A wants to send in the email ( For example, "We will have a meeting 1 :30 this afternoon in Room 123" ), User B also needs to indicate the email address of recipient C in the email ( 3⁄4ack(g)machine.example and ierry(3⁄4machine.example) When necessary, User B also needs to write in the e-mail the purpose of the P piece (iH: ί 口 "let them know the meeting schedule below"), so that the user A can know in the case of a large number of e-mails. The purpose of the email. After receiving the email from User B, User A will address the recipient C in the email - iack@machine.example and .ierrv (glmachine.example complex j ^'J email title In the "To (to)" field, and then send the message to Jack and Jerry

However, the existing solution of this kind has the following disadvantages. First, this involves additional email or other means of communication to send User A the email address required to "send" the domain. Sometimes this is very confusing and inefficient for User A. Second, different client email applications use different styles to separate recipient addresses in the "recipient" domain. For example, in some email applications, multiple recipients' email addresses are separated by semicolons, and some are separated by commas. Therefore, it is difficult for User B to know which style should be used. If you use a different style than User A, then for User A, you need to re-edit the email address, which is also a time-consuming and labor-intensive job.

Accordingly, there is a need to provide an advantageous solution to the problems of inefficiency and confusing existing in the prior art described above. Summary of the invention

The object of the present invention is to overcome the shortcomings of low efficiency and easy confusion of destination address management in the existing information system, and to provide a method and system for improving the efficiency of message transceiving in an information system and reducing the burden on users by using third party identity management. According to a first aspect of the present invention, a method for transmitting a message at a sender is provided. The method can include the steps of: creating a message to be sent, wherein the message includes a third party identity management entry for storing a third party identity, the third party identity indicating a third party to which the forwarder subsequently forwards the message; The message is sent to the forwarder.

According to a second aspect of the present invention, a method for forwarding a message at a forwarder is provided. The method can include the steps of: receiving a message including a third party identity management entry, wherein the third party identity management entry is for storing a third party identity, the third party identity indicating a third party to which the forwarder subsequently forwards the message; extracting the The third party identifies at least one third party identifier in the management entry; and forwards the received message as another message to the third party represented by the extracted third party identifier.

According to a third aspect of the present invention, a method for communicating between a sender and a forwarder is provided. The method can include the steps of: creating a message to be sent at the sender, wherein the message includes a third party identity management entry for storing a third party identity, the third party identity indicating a third party to which the forwarder then forwards the message Sending the message to the forwarder at the sender; receiving the message at the forwarder; extracting at least one of the third party identity management entries of the received message at the forwarder; and forwarding The party forwards the received message as another message to the third party represented by the extracted third party identifier.

According to a fourth aspect of the present invention, an apparatus for transmitting a message at a sender is provided. The device can include: a creating means for creating a message to be sent, wherein the message includes a third party identity management entry for storing a third party identity, the third party identity indicating a third party to which the forwarder then forwards the message And a transmitting device, configured to send the message to the forwarder.

According to a fifth aspect of the present invention, an apparatus for forwarding a message at a forwarder is provided. The device may include: a receiving device, receiving a message including a third-party identity management entry, where the third-party identity management entry is used to store a third-party identifier, the third-party identifier indicating a third party to which the forwarder forwards the message; Device, And a forwarding device, configured to forward the received message as another message to a third party represented by the extracted third-party identifier.

According to a sixth aspect of the present invention, a system for communicating between a sender and a forwarder is provided. The system can include a sender client and a forward client. The sender client can include: a creating device, configured to create a message to be sent, wherein the message includes a third party identity management entry for storing a third party identity, the third party identity indicating that the forwarder then forwards the message to a third party; and a transmitting device for transmitting the message to the forwarder. The forwarding client may include: receiving means for receiving the message; extracting means, extracting at least one third party identifier of the third party identification management entry of the received message; and forwarding means for The received message is forwarded as another message to a third party represented by the extracted third party identity. DRAWINGS

1 is an exemplary schematic diagram depicting a user interface of an email in the prior art;

2 is a flow chart of a message transmitting and receiving method according to the present invention;

4 is an exemplary diagram of a user interface when a forwarder receives an email from a sender in accordance with the present invention;

5 is an exemplary diagram of a user interface after a forwarder transfers a third party email address to a "recipient" domain in accordance with the present invention;

Figure 6 is a system block diagram depicting a messaging system in accordance with the present invention;

7 is a flow chart depicting a method of transmitting a message at a sender client in accordance with the present invention;

8 is a flow chart describing a method of forwarding a message at a forwarding client according to the present invention. Cheng Tu. detailed description

The main principle of the present invention is: By using the third party identity management in message transmission and reception, the efficiency of message transmission and reception in the information system can be improved, the burden on the user can be reduced, and work efficiency can be improved.

It is to be understood by those skilled in the art that the specific names are hereinafter applied, and are not intended to limit the invention, and those skilled in the art may modify or replace these names according to their own preferences or habits.

2 is a flow chart of a messaging method in an information system in accordance with an embodiment of the present invention, wherein the information system includes a first client and a second client.

As shown in FIG. 2, first, at step S100, a first message can be created at the first client. The first message can be, for example, an email.

In step S110, a third-party identity management entry may be created in the first message, where the third-party identity management entry may be used to store a third-party identity, where the third-party identity indicates that the forwarding party subsequently forwards the message to Three parties. The third-party identification management entry may be a storage space that can store content in the form of numbers, strings, and the like. The third party identification can be any information that identifies the identity of the third party, such as an email address, a phone number, a name, and the like.

For different applications, third-party identities can have different specific formats. For example, for email, the third party can be an email address with name@machine.example or similar format.

Additionally, the third party identity can also be content associated with a particular format address. For example, the name associated with an email address. To this end, step S1 10 may further comprise an associating step of associating content received by the third party identity management entry with a particular third party identity having a format supported by the information system. For example, if the user enters "name" in the third-party ID management entry, that is, the name of the user, the client will automatically consider the address corresponding to the name to be name@machine.example. It should be understood that the association step may not need to appear separately in actual operation, but may be set in advance in the information system used (for example, an email system), for example, the input recipient name, phone number. Etc.

The above implementation is easily implemented by those skilled in the art, and thus will not be described herein. The input of the third party identifier can be implemented by a keyboard, a tablet, a touch screen, etc., and the present invention does not impose any limitation on the input mode.

Furthermore, step S1 10 does not necessarily occur after step S100, and both may occur simultaneously, for example, a third party identity management entry may be automatically established in the first message while the first message is being established.

At step S120, a first message containing a third party identity management entry is sent to the second client. This transmission can be sent via wired or wireless media, or via the Internet, intranet, etc. It should also be noted that the first client and the second client are not necessarily physically separate entities, but may be modules that are logically separated but physically located on the same client. For example, the user can operate on the same client according to their own email address or login authority. This will be readily understood by those skilled in the art and will not be described again here.

In step S130, when the first message is received at the second client, if the third party identification management entry has a third party identifier, the third party identifier is extracted.

Optionally, the step S130 further includes a selecting step (not shown), in which the third party identifier to which the forwarding is desired may be selectively extracted from all the third party identifiers. For example, if the third-party identity management entry in the first message received at the second client has multiple third-party identifiers, and the user of the client only needs a few of the ideas, the Select the desired ID from the three-party logo without sending the message to all third parties.

At step S140, based on the third party identifier, the received first message is separately forwarded to the third party as a second message. It should be noted that the first message and the second message described herein may be the same or different. For example, the user may edit the received first message to form a second message different from the first message. For ease of understanding, the application of the present invention will be described in detail below in connection with the transmission, forwarding and reception of emails. However, those skilled in the art will appreciate that the present invention can also be used in other information systems.

First, as shown in Figure 3, User B (for example, Secretary, Secretary mary@machine.example) creates a new message that includes the domain "Pt", which is the email used to receive the third-party email address. Suggested recipients (proposed to ) " . User B can enter the domain that User A wants to send to the p by the p-part address in the field indicated by Pt, for example, "jack(3⁄4machine.example, ierrv@machine.example). Then, User B will use this electronic The mail is sent to the user A, for example, boss@nil.test. It should be noted that, according to the present invention, the mail address contained in the domain may be one or more. When the mail address is not included, it is sent with the traditional mail. the same.

One way to add a desired domain to an email message header is to utilize RFC 2822. RFC 2822 is a standard that can be downloaded from the Internet and is used to define Internet mail formats that contain several title fields. Now, in this standard, fields such as "From", "Subject", "Cc," are defined. The contents of these fields are filled in by the sender, and the receiver can obtain data from the corresponding domain according to this standard.

For example, adding a "Proposed to" field to the Internet message header section can be added in the following ways:

Proposed-To = "Proposed-To: ,, address-list CRLF where "address-list" represents the address list and CRLF is the carriage return line feed. Thus, when the "Proposed to" field is added, the receiver (here refers to For example, user A) can know the email address contained in the domain as a third party.

The method of adding a "Proposed to" field to the Internet mail header portion using RFC 2822 is well known to those skilled in the art and will not be described again here.

Next, after user A receives the email, the email can Presented to User A as shown in FIG. As shown in Figure 4, User A can see that the email address of the third party is included in the "Proposed to" field of the email, ie iack@machine. example, jerry@machine. example„

Next, in order to send the message to the third party, User A needs to extract the third-party addresses contained in the "Proposed to" field and place those addresses in the "To (to), domain. This can be done by adding a special extraction function to the toolbar options of User A. For example, as shown by the number 9 in Figure 4, for convenience, you can directly add the "To-Proposed" menu. When user A clicks on the "To-Proposed" menu, the third-party address contained in the "Proposed to" field is copied directly into the "To" field, so that the user shown in Figure 5 appears. Interface.

The user interface shown in Figure 5 is the usual form of sending an email. User A can simply press the "send" menu to receive the email content from User B (eg "We will have a meeting 1 : 30 this afternoon in Room 123" ) forwarded to third party Jack and Jerry.

Finally, third parties (such as Jack and Jerry) will be able to receive emails from user A (such as Boss).

Of course, for those skilled in the art, the names of the menus corresponding to the extraction function may be variously selected, and are not necessarily the above-mentioned "To-Proposed". The above names are merely examples, and do not constitute a limitation of the present invention. .

In addition, if User A changes his mind, for example, if you need to delete a third-party recipient or add a new third-party recipient, User A can also optionally copy the third-party address contained in the "Proposed to" field to "Receive". Edit in the "to" (to) field or directly in the "to" (to).

Of course, for deleting a few third-party recipients, it can be easily done by editing directly in the "to" list. However, when there are a large number of third-party recipients and only a few of them are needed, the above-mentioned direct editing method is somewhat time consuming. The method for solving the above problem can be as follows. You can set the next level of options in the option "To-Proposed" (for example, "Select (not shown), ). In the specific operation, when User A clicks the right mouse button on the "To-Proposed" menu, it pops up. The "Select" option, which includes a list of all third-party recipients under this option. Users can selectively extract those expected third-party addresses in the list. Selectively extracted third-party addresses are automatically added to User A. The "To (to)" field. The above method is very efficient and convenient for selecting only a few from a large number of third-party addresses.

According to another embodiment of the present invention, when the user sends a mail through the mobile phone, it can also be implemented by the above process. This implementation can be easily implemented by those skilled in the art and will not be described again here.

As shown in Figure 6, the present invention also provides a system for communicating between a sender client and a forward client. The system can include a first client 10 (i.e., a sender client) and a second client 20 (i.e., a forwarder client). As indicated above, the first client 10 and the second client 20 may be located at the same physical location or at different physical locations.

The first client 10 may include: a creating device 200, configured to create a message to be sent, wherein the message includes a third-party identity management entry for storing a third-party identifier, the third-party identifier indicating that the forwarder then forwards the message a third party to; and a transmitting device 210 for transmitting the message to the second client 20.

The second client 20 may include: a receiving device 220, configured to receive the message; an extracting device 230, configured to extract at least one third-party identifier of the third-party identity management entry of the received message; and a forwarding device 240, And for forwarding the received message as another message to a third party represented by the extracted third party identifier.

Taking the email as an example, the creating apparatus 200 can be implemented by "creating a new mail (new)" in the mail itself, and the creation of the third-party identification management item can be implemented by the well-known RFC 2822 standard, and the implementation method thereof has been implemented. In the above, I have read the detailed 4w. Preferably, the creating device 200 further comprises an associating device 201 for associating the content received by the third party identity management entry with a specific third party identity having a format supported by the information system. Taking an email as an example, the third party information includes a third party's name, a phone number, and the like, and the dedicated third party information format refers to an email address.

For e-mail, the functions of the extracting means 230 and the forwarding means 240 can be implemented, for example, by the "To-Proposed" menu and the "send" menu, respectively.

Preferably, the extraction device 230 includes a selection device 231 that can selectively extract the third party identification to which it is forwarded from among all third party identifications. For e-mail, the selection means 231 can be a sub-option under the "To-Proposed" menu above, which helps to provide a convenient and quick way for the user to operate.

Figure 7 is a flow diagram of a method for transmitting a message at a sender client in accordance with the present invention. The method may include the following steps: Step S300, creating a message at the sender client; Step S310, creating a third-party identity management entry in the message, the third-party identity management entry is used to receive the third-party identity; and step S320 Send a message containing a third-party identity management entry.

8 is a flowchart of a method for forwarding a message on a forwarding client according to the present invention. The method may include the following steps: Step S400: Receive a message at a forwarding client, where the message includes a third-party identity management entry, the third-party identifier The management entry is used to store the third-party identifier; Step S410, when the message is received at the forwarding client, if the third-party identity management entry has a third-party identity, the third-party identity is extracted; and step S420, based on the The extracted third party identifier forwards the received message to another party as another message.

The present invention can be implemented on clients such as desktop computers, notebook computers, mobile phones, etc., and these clients can run different operating systems such as Windows, Linux, etc., as well as different application software such as Outlook, Foxmail, and the like. The invention is not limited in any way. It is to be understood that the modifications and changes may be made in the embodiments of the present invention without departing from the scope of the invention. The description in the specification is for illustrative purposes only and should not be considered as limiting. The scope of the invention is to be limited only by the claims.

Claims

Claim

CLAIMS 1. A method for transmitting a message at a sender, the method comprising the steps of: creating a message to be sent, wherein the message comprises a third party identity management entry for storing a third party identity, the third party identity indicating forwarding The party then forwarded the message to the third party; and

The message is sent to the forwarder.

2. The method of claim 1 wherein the message is an email blank

3. The method of claim 2, wherein the third party identification management entry is a title field of an email system, and the third party identification is an email address of the third party.

4. The method of claim 2, wherein the third party identification management entry is a title field of an email system, and the third party identification is a name of the third party, the email with the third party The address is associated.

5. A method for forwarding a message at a forwarding party, the method comprising the steps of: receiving a message comprising a third party identity management entry, wherein the third party identity management entry is for storing a third party identity, the third party identity indicating forwarding The party then forwarded the message to the third party;

Extracting at least one third party identifier in the third party identity management entry; and

The received message is forwarded as another message to the third party represented by the extracted third party identifier.

6. The method of claim 5, wherein the message is an email message.

7. The method of claim 6, wherein at least one of the third party identification management entries is extracted via an offer recipient menu set on an email client.

8. The method of claim 6, wherein the third party identification is an email address of the third party.

9. The method of claim 6, wherein the third party identification is a name of the third party that is associated with an email address of the third party.

10. A method for communicating between a sender and a forwarder, the method comprising the steps of:

At the sender,

Creating a message to be sent, wherein the message includes a third party identity management entry for storing a third party identity, the third party identity indicating a third party to which the forwarder subsequently forwards the message;

Sending the message to the forwarder;

At the forwarding side,

Receiving the message;

Extracting at least one third party identifier in the third party identification management entry of the received message;

The received message is forwarded as another message to the third party represented by the extracted third party identity.

1. The method of claim 10, wherein the message is an email message.

12. The method of claim 11, the third party identification being an email address of the third party.

13. The method of claim 11, the third party identification being a name of the third party associated with an email address of the third party.

14. A device for transmitting a message at a sender, the device comprising: a creating device, configured to create a message to be sent, wherein the message includes a third party identity management entry for storing a third party identity, the The three-party identity indicates the third party to which the forwarder subsequently forwards the message;

And a sending device, configured to send the message to the forwarder.

15. The device of claim 14, wherein the message is an email message.

16. The device of claim 15, wherein the third party identification management entry is a title field of an email system, and the third party identification is an email address of the third party.

17. The device of claim 15, wherein the third party identification management entry is a title field of an email system, and the third party identification is a name of the third party, the email with the third party The address is associated.

18. An apparatus for forwarding a message at a forwarding party, the apparatus comprising: receiving means, receiving a message including a third party identity management entry, wherein the third party identity management entry is for storing a third party identity, the third party identity Represents the third party to which the forwarder forwards the message to;

An extracting device, configured to extract at least one third-party identifier of the third-party identity management entry;

And a forwarding device, configured to forward the received message as another message to a third party represented by the extracted third party identifier.

19. The device of claim 18, wherein the message is an email message.

20. The device of claim 19, wherein the third party identification is an email address of the third party.

21. The device of claim 19, wherein the third party identification is a name of the third party that is associated with an email address of the third party.

22. A system for communicating between a sender and a forwarder, the system comprising a sender client and a forward client, wherein:

The sender client includes:

Creating means for creating a message to be sent, wherein the message comprises a third party identity management entry for storing a third party identity, the third party identity indicating a third party to which the forwarder subsequently forwards the message; a sending device, configured to send the message to a forwarder; the forwarder client includes:

Receiving means, configured to receive the message;

An extracting device, configured to extract at least one third-party identifier in the third-party identity management entry of the received message;

23. The system of claim 22, wherein the message is an email message.

24. The system of claim 23, the third party identification being an email address of the third party.

25. The system of claim 23, the third party identification being a name of the third party associated with an email address of the third party.