IMPROVED MESSAGE RECORD MANAGEMENT

Description

[0001] The present invention relates to the management of a database of messages transmitted via a communications network.

[0002] More particularly, the message base is managed by a messaging server. The management of this base is implemented in particular in an embodiment where a terminal sending a message transmits this message to the aforementioned messaging server and the latter retransmits this message to a recipient terminal according to predefined rules.

[0003] An application of the aforementioned basic message management relates in particular to the situation where the sending terminal has sent a given message by mistake, for example. Thus, the sending terminal can send a request for non-delivery of this message, or, more particularly, for deletion of this message before the messaging server directs it to a recipient terminal. However, between the time when the message is sent by mistake and the time when the sending terminal sends this request, the recipient terminal may have received the message and a user has already read it.

[0004] We know of existing achievements (notably the messaging application « Outlook » ©< ) which mention that such messages have been "recalled"by their sender without always erasing the content, which in reality only draws the attention of the user of the recipient terminal to these messages. US 2011 / 0131281 and US 8,073,122 describe such functionalities, for example.

[0005] The present invention improves the situation.

[0006] To this end, it proposes to assign to such messages a status which corresponds, more generally, to a status of a message in the process of expiring, taking into account however the possibility that the recipient terminal has had access or not to this message. Thus, the present invention proposes to detect whether or not the recipient terminal is connected to the messaging server.

[0007] The invention then relates to a method according to claim 1, a messaging server according to claim 11 and a computer program according to claim 12.

[0008] Thus, depending on the detection of connection or non-connection of the recipient terminal to the messaging server, specific rules can be implemented to manage a message to which an expiring message status has been assigned.

[0009] For example, in one possible embodiment, the message may be deleted as soon as the aforementioned status of message in the process of expiring is assigned. This deletion may be carried out at the messaging server itself, for example, in the case where the recipient terminal has not been detected as already being connected to the server. Such an embodiment means that the recipient terminal, not being connected, was unable to receive the message and that this message may be deleted directly at the messaging server. Thus, the terminal initially receiving the message ultimately does not receive the message, nor any particular information relating to this message.

[0010] Thus, more generally, in the case where the recipient terminal has been detected as not connected to the messaging server, the latter can manage the message in the process of expiring according to predefined rules (for example its deletion, or deletion after a timeout as will be seen later in an example of implementation, or others), without the recipient terminal receiving any particular information concerning this message.

[0011] Thus, in one implementation, if the terminal is not detected as connected, the messaging server assigns the message a general status of an expiring message.

[0012] On the other hand, if the terminal is detected as connected, the server, in a particular implementation, may not transmit any particular command to the recipient terminal and the message retains a current status with the recipient terminal. For example, if the message has a status of already read (or, on the contrary, unread) message with the recipient terminal, it retains a status of read (or respectively, unread) message.

[0013] Of course, other rules may be provided, particularly in the case where the message has been previously sent to the recipient terminal. In this case, upon receipt of an expiration command for the message previously sent to the recipient terminal, the messaging server may transmit to the terminal a command to assign said message a status of a message in the process of expiring with the recipient terminal. In this case, the recipient terminal may itself manage the expiration of the message according to its own rules (deletion, or deletion after timeout, or expiration after timeout, or simply expiration).

[0014] The expiration command received from the sending terminal is accompanied by a timeout parameter, and, for an expiring message: a timeout is applied based on this parameter, and the message is assigned an expired message status after said timeout.

[0015] For example, the parameter can be a predetermined duration, or a given date, or a condition on a given event (for example, to erase the message in the event of a sports team losing), or others.

[0016] Thus, in an application where a particular message is of interest in a predetermined period (meeting in progress on a given day and for a given duration, or a commercial offer for a given period), the messaging server can transmit to the recipient terminal the command to assign the status " expiring”. So, after the predetermined period, the message has a status of “ expired " near the terminal.

[0017] These steps of applying the time delay and assigning the status " expired "can be implemented at the recipient terminal, for example. Alternatively, they can be implemented by the server itself. Indeed, in one implementation, the server detects whether the recipient terminal is connected or not and, as long as the terminal is not detected as connected, applies the timeout until the message expires.

[0018] Generally speaking, we can provide for example that a message, after the timeout, has the status of an expired message, and that then, this message is deleted.

[0019] So in the example above where the server implements the timeout, the server can then delete the message if the recipient terminal has not been detected as connected during the timeout.

[0020] In the case in particular where the terminal has received the message which is expiring or has expired, it may be provided, in one embodiment, that a message with expired message status is kept at the recipient terminal, with an indication of the message's expiry. This embodiment allows a user of the recipient terminal to see, for example, that a meeting has taken place or that a commercial promotion has taken place, at a period which has now expired nonetheless.

[0021] In one embodiment, assigning message status "expiring" may follow an expiration request received from a terminal sending the message. For example, the deletion of a message (in a section of the type " being sent") to the sending terminal may cause the expiration request to be sent to the server (which may be interpreted by the messaging server as a deletion request if, for example, it is not accompanied by a timeout parameter, in which case the server may delete the message if the recipient terminal is not detected as being connected).

[0022] In one embodiment, detecting the terminal's connection to the messaging server may include detecting the terminal's connection to an intermediate server (a third-party server) that may be connected to the messaging server. For example, the intermediate server may correspond to a social network application server (e.g., Facebook).

[0023] Thus, the messaging server can repeatedly query the intermediate server to obtain information on whether the recipient terminal is connected or not to the intermediate server and, from there, interpret any possible connection as meaning that the recipient terminal is connected to the network and is therefore likely to also connect to the messaging server.

[0024] In a variant, the intermediate server may include means for connecting the recipient terminal to the messaging server (for example, a link to the messaging server, on a WEB page associated with the intermediate server). Use of these connection means by the recipient terminal may then cause the transmission to the messaging server of information on the connection of the recipient terminal to the messaging server.

[0025] In a more advanced variant, the intermediate server may include means for instant connection of the recipient terminal to the messaging server and a connection of the recipient terminal to the intermediate server causes a connection of the recipient terminal to the messaging server.

[0026] Such an embodiment can also be implemented at the sending terminal. Thus, for example, the message expiration command can be launched by the terminal sending the message, via the aforementioned intermediate server (for example, the recall of a sent message can be ordered on the sending terminal, via a WEB page associated with the intermediate server, then transmitted to the messaging server). Such an embodiment can be advantageous, for example, in a context where a recipient can become aware of the message when it is displayed in a WEB interface (such as a Facebook ®< page for example), via a specific messaging application within the meaning of the invention.

[0027] The present invention also relates to an intermediate server, of the aforementioned type, since such a server can help detect the connection or non-connection of the recipient terminal, or participate in the transmission of requests for recall, deletion, or expiration of a message sent by the recipient terminal. It thus contributes, as an essential means, to the implementation of certain embodiments of the present invention.

[0028] Other advantages and characteristics of the invention will appear on reading the description, detailed below, of exemplary embodiments and on examining the corresponding drawings, in which: there figure 1 illustrates a context of implementation of the present invention, involving a messaging server SM within the meaning of the invention, the figure 2illustrates a particular embodiment for detecting connection or non-connection of the recipient terminal TD, and involving an intermediate server SI, the figure 3 schematically illustrates the main steps which follow a detection of connection or non-connection of the recipient terminal TD, for the assignment of an “expired” status to a message based on this detection, the figure 4 illustrates a particular embodiment, in which a time delay is applied before the message definitively expires, and the Figure 5 schematically represents an example of a SM messaging server for implementing the invention.

[0029] We first refer to the figure 1on which a sending terminal TE of a message M, a messaging server SM and a receiving terminal of a message M, can communicate together via a communication network R (such as, for example, the Internet). More particularly, the messaging server SM centralizes the exchange of messages between the different terminals and manages a message base M, for this purpose. In a possible context of application of the present invention, the sending terminal TE requests from the messaging server SM that the message M, intended for the receiving terminal TD, has an expired message status.

[0030] For example, the sending terminal TE may wish that the message M is not read, ultimately, by the destination terminal TD (the message M having been sent in error, for example). In another embodiment, it may simply be provided that the message M has an expiring message status, or an expired message status, although it has been received by the destination terminal TD.

[0031] Within the meaning of the invention, the assignment of such a status (or even the deletion of the message M without it being transmitted to the terminal TD) depends on a connection or non-connection state of the recipient terminal TD to the messaging server SM.

[0032] For this purpose, it has been represented on the Figure 5a messaging server SM comprising for example an input E to receive a request for expiration of a given message, previously sent by a sending terminal TE. The server also has means, such as a processor PROC and a memory storing the data of a message base DB, to find the message and assign it an expiration status (depending on a detection of connection or non-connection of the recipient terminal). The aforementioned detection of connection or non-connection can be carried out with the messaging server, for example by recognition of an IP address of the recipient terminal, or a connection identifier, or others. In this respect, the processor PROC and / or the memory DB can still be used.

[0033] However, the concept of connection or non-connection of the recipient terminal to the messaging server must be interpreted in the broad sense. In particular, the aim is to detect a possibility of connection or non-connection of the terminal to the messaging server. For example, if it is possible to detect that the recipient terminal is connected to the communications network R, then the recipient terminal is simply likely to connect to the messaging server and it may be decided whether or not to implement the assignment of the message expiry status, simply on the basis of this information. Thus, if the messaging server does not have the means to detect the connection of the recipient terminal to the communications network R, other servers to which the terminal may be connected and which can transmit this terminal connection information to the messaging server are used.For example, we can rely on an intermediary server, for example a social network application server (hosting a Facebook account or page for example), capable of notifying the messaging server of a connection from the terminal to this intermediary server.

[0034] It has been represented on the figure 2a corresponding exemplary embodiment. Here, the terminal TD connects to the intermediate server SI (arrow D1) and this connection information is transmitted to the messaging server (arrow D2). In one embodiment, the connection of the terminal to the intermediate server can automatically trigger the connection of the terminal to the messaging server. For example, the number of messages received from the messaging server, for a given Facebook account, can be displayed on an individual Facebook page, associated with this given account. Similarly, the user of the sending terminal can have an account with the same intermediate server, in particular to initiate a request for expiration of the message already sent (or simply, connect directly to the messaging server to request expiration of the message).

[0035] We now refer to the Figures 3 and 4to describe an exemplary embodiment of a method within the meaning of the present invention. These figures illustrate flowcharts corresponding to general algorithms of a computer program within the meaning of the present invention, for assigning an expiration status to a message, depending on the detection of connection of the terminal receiving this message.

[0036] (Referring to the figure 3, following the detection step S1 and the connection or non-connection test T4 of this terminal, in an exemplary embodiment, if the terminal is already connected (OK arrow at the output of test T4), no action is taken with respect to the message probably already received by the recipient terminal; the method stops at the end step S2. Thus, the message can naturally retain its current status with the recipient terminal. On the other hand, if the terminal is not connected (KO arrow at the output of test T4), a message expiration status is assigned at step S3.)

[0037] In a variant, it may be decided to transmit to the recipient terminal, in step S2, an expiration command targeting a message already transmitted, so that the recipient terminal manages the expiration of this message on its side.

[0038] Furthermore, assigning the expiration status at step S3 may simply consist of deleting the message, without it being transmitted to the unconnected recipient terminal.

[0039] In a further variation, illustrated on the figure 4 , a time delay may be provided in step S31 before assigning any status to the message. Thus, a counter with a time value t may be decremented to zero, as long as this value of zero is not reached (KO arrow at the output of test T32). On the other hand, if the value of zero is reached (OK arrow at the output of test T32), the expired message status is assigned in step S33. This expired message status may simply correspond to a deletion of the message, without communication to the destination terminal. In a variant, the message may be transmitted to the destination terminal subsequently and may appear as expired, with an appropriate presentation (for example in italic characters, or others).

[0040] Of course, the present invention is not limited to the embodiment described above as an example; it extends to other variants.

[0041] Thus, an embodiment has been described above in which, if the recipient terminal is not connected, the expiration status can then be assigned to the message. In a variant, however, this status can, on the contrary, be assigned if the terminal is connected to indicate to its user, for example, that an event associated with this message is no longer in progress and, for example, simply delete this message from the messaging server if the recipient terminal is not connected.

[0042] Furthermore, the term "expiring message status" generally means that a message must: have an expired message status after a timeout, or have an expired message status directly, without a timeout, or be deleted after a timeout, or be deleted directly, without a timeout, and this, as presented in the various examples of realization above.

[0043] Furthermore, the expiration status subsequently assigned to a message may not necessarily be related to a timeout, but may depend on other conditions such as, for example, the connection or disconnection of the recipient terminal, in particular from a WEB page. For example, in one embodiment, a message received by a terminal while participating in a forum on a WEB site may become “expired” after the terminal disconnects from the forum.

Claims

1. A method for managing a message base, implemented by a messaging server (SM), the method including the steps of: upon receiving an expiration command of a message (M) to be received by a recipient terminal (TD) of said message, said command being accompanied by a timeout parameter, - detecting (S1) whether the terminal is connected to the messaging server or not (T4), - if the terminal is detected as not connected, the messaging server assigns the message a currently expiring message status (S3), - for a currently expiring message: - a delay (S31) as a function of said parameter is applied, and - the message is assigned an expired message status after said timeout and the message is deleted.

2. The method according to claim 1, wherein, if the terminal is detected as connected, the server does not transmit any command to the recipient terminal and the message retains a current status at the recipient terminal.

3. The method according to one of the preceding claims, wherein, having previously sent the message to the recipient terminal, the messaging server transmits to the terminal a command to assign said message a currently expiring message status at the recipient terminal.

4. The method of claim 1, wherein a message with an expired message status is retained at the recipient terminal, with an expiration indication for the message.

5. The method according to any one of the preceding claims, wherein the message is deleted as soon as the currently expiring message status is assigned.

6. The method according to one of the preceding claims, wherein assigning the currently expiring message status follows an expiration request received from a terminal emitting the message.

7. The method according to claim 6, wherein deleting a message at the emitting terminal causes the expiration request to be emitted to the server.

8. The method according to one of the preceding claims, wherein detecting connection of the terminal to the messaging server includes detecting connection of the terminal to an intermediate server (IS) connected to the messaging server.

9. The method of claim 8, wherein the messaging server regularly queries the intermediate server to obtain information of connection or non-connection of the recipient terminal to the intermediate server.

10. The method according to claim 8, wherein the intermediate server includes means for instantly connecting the recipient terminal to the messaging server, and connection of the recipient terminal to the intermediate server causes connection of the recipient terminal to the messaging server.

11. A messaging server for managing a message base, said server including means configured to execute the method according to claims 1 to 10.

12. A computer program, including instructions for implementing the method according to one of claims 1 to 10, when this program is executed by a processor.