FR2886795A1 - METHOD AND SYSTEM FOR JOURNALIZING MESSAGES ACCORDING TO INSTANT MESSENGER PROTOCOL IN RELAY MODE - Google Patents

Abstract

The invention relates to a message logging method according to the relay-mode MSRP instant messaging protocol, in which an initiating terminal (TA) communicates with at least one participating terminal (TB) via relay servers (RS1). ) (RS2) selected from the terminals, consisting of selecting, from one of the terminals (TA), a log server (Slog) for logging messages.Application to the execution of discussions in messaging instant.

Description

METHOD AND SYSTEM FOR JOURNALIZING MESSAGES ACCORDING TO ONE

  The invention relates to a method and a system for message logging according to an instant messaging protocol in relay mode.

  The instant messaging protocols make it possible to establish messaging sessions between fixed or mobile terminals, either in peer-to-peer mode, peer to peer mode in English, or with intermediary relay servers.

  However, it is common for messaging systems to implement logging, English logging features, in order to save conversations between two or more users. In the case where the instant messaging server does not provide such a function, it is then necessary either to capture this information when it travels between the users, or to send it to an external server for storage, which inevitably duplicates the trades.

  At present, for the purpose of performing the aforementioned logging operations, two solutions are commonly proposed.

  According to a first solution, logs, or logs in English, can be managed and stored on the client terminal. It is therefore impossible for the user to access it from any other terminal.

  According to a second solution, the logs or logs can be managed by sending them to an external server.

  In this situation, it is the amount of network traffic requested by this solution that is problematic. Indeed, that we make updates in real time, periodically at a given frequency or on specific request of the user, the amount of data to be exchanged remains the same and ultimately doubles the traffic between the terminal and the server .

  The present invention aims to overcome the disadvantages and limitations of technical solutions of the prior art.

  In particular, an object of the present invention is the implementation of a method and a system for logging messages according to a relay mode instant messaging protocol allowing either the implementation of a discussion logging process. between terminals, simply by a user, or the lack of implementation of the aforementioned logging process.

  Another object of the present invention is also the implementation of the method and the aforementioned message logging system fully compatible with a relay mode instant messaging protocol, in the absence of introduction of modification of the latter.

  The method of message logging according to a relay mode instant messaging protocol, object of the invention, in which an initiating terminal communicates with at least one participating terminal via at least one relay server selected from of these terminals is remarkable in that it consists in selecting from one of these terminals a log server to ensure the logging of these messages.

  The message logging system according to a relay mode instant messaging protocol, object of the invention, in which an initiating terminal communicates with at least one participating terminal via at least one relay server selected from of one of the terminals is remarkable in that this logging system comprises at least one message logging server, specific address, and a selection module of the log server located in at least one terminal, per connection from this terminal this specific address. Selecting the log server allows logging of these messages.

  The invention furthermore covers a remarkable message logging server in that this server comprises a module for transferring messages to a relay server ensuring the communication between an initiating terminal and at least one participating terminal, according to a relay mode instant messaging protocol, and a message journaling module.

  The invention also covers a remarkable message logging server in that this server is an ambivalent server formed by a relay server connecting a initiating terminal and at least one participating terminal according to an instant messaging protocol. in relay mode and having a logging function.

  The invention finally covers a terminal operating according to an outstanding relay mode instant messaging protocol in that this terminal comprises a module for selecting a specific address log server, by inserting this specific address in a list of relay server addresses enabling the communication of this terminal with at least one other terminal according to a relay mode instant messaging protocol.

  The method, the system, the logging servers and the terminal enabling the selection of a log server, according to the subject of the present invention, will be better understood on reading the description and on observing the drawings. after which: in addition to FIG. 1 illustrating a timing diagram of the message exchange between an initiator terminal, a first and a second relay server and a participating terminal according to the relay mode MSRP instant messenger protocol, known as such ; FIG. 2a represents, by way of illustration, a flowchart of the essential steps of implementing the message logging method that is the subject of the present invention; FIG. 2b represents, by way of illustration, a timing diagram of the message exchange between an initiator terminal, a log server, a first and a second relay server and a participating terminal, in accordance with the method that is the subject of the invention, illustrated in FIG. Figure 2a; FIG. 2c represents, by way of illustration, a timing diagram of the exchange of response messages transmitted from the participating terminal to an initiator terminal via a log server chosen in accordance with the method that is the subject of the present invention, illustrated in FIG. Figures 2a and 2b; FIG. 2d represents a message exchange schedule between an initiating terminal and a participating terminal, given a so-called ambivalent server allowing both to act as a relay server and a log server, the logging process however, it is not executed and the ambivalent server is not used; FIG. 2e represents a timing diagram for the exchange of messages between an initiating terminal and a participating terminal, taking into account a so-called ambivalent server allowing both to act as a relay server and a log server, the ambivalent server being substituted. to a relay server and the logging process being executed; FIG. 3a represents, by way of illustration, in the form of a block diagram, a message journaling system, object of the invention, according to a first embodiment; FIG. 3b represents, by way of illustration, in the form of a block diagram a message journaling system, object of the invention, according to a second embodiment; FIG. 4 represents, by way of illustration, in the form of a functional diagram, a terminal enabling the selection of a message journaling server, in accordance with the object of the present invention.

  Prior to a description of the method and the message logging system according to a relay mode instant messaging protocol, object of the present invention, a review of the procedure will now be given in connection with FIG. 1. This procedure is described in FIG. As an example using the MSRP instant messaging protocol, for Message Session Relay Protocol in English The above operating mode is described in the presence of a user having an initiator terminal TA usera.orange address. com negotiating an instant chat session with a user having a TB participating terminal whose address is userb.wanadoo.com, the initiating terminal user negotiating a session with the participating terminal using the SDP / SIP / protocol SIMPLE (SDP for "Session Description Protocol" in English, SIP for "Session Initiation Protocol" in English, SIMPLE for "SIP for Instant Messaging and Presence Leveraging Extensions"). The user of the initiating terminal wishes to establish an MSRP session using, in particular, the relay server RS1 of address polrelayl.orange.com.

  It is indicated that the participating terminal TB and the initiating terminal TA have first authenticated to the relay server RS1 for the initiating terminal TA and to a relay server RS2 for the participating terminal TB. The authentication messages are the AUTH messages and Auth 401 response messages shown in FIG. 1. These messages are conventional type messages and will not be described in detail in the description.

  To communicate in relay mode, IM users use a list of relay servers that are traversed by each message. This process is described online at http: // www. ietf.org/internet-drafts/draft-ietfsimple-msrp-relays-03.txt. It is currently in draft document state and is subject to change.

  It is indicated that the session establishment messages check the relation: TA -4 TB c = IN IP4 usera.orange.com m = message 1234 TCP / * a = accept-types: message / cpim text / plain text / html a = path: s: // polrelayl. orange.com:9000/hjdhfha;tcp s: // will use. orange.com:7965/agic456;tcp TB + TA c = IN IP4 userb.wanadoo.com m = message 1234 TCP / TLS / * a = accept-types: message / cpim text / plain text / html a = path: s : //polrelay2.wanadoo. com: 8145 / hjdhfha; tcp s: //userb.wanadoo.com: 1234 / fuige; tcp The session for sending instant messages is therefore established between the users of the aforementioned terminals TA and TB.

  The successive messages are noted m1 to m9 in Figure 1 and then have the following message structure: 25 ml: 6aef SEND To-Path: s: //polrelayl.orange.com: 9000 / kjfjan; tcp s: / /polrelay2.wanadoo. com: 8145 / zerty; tcp s: //userb.wanadoo.com: 1234 / kjfjan; tcp From-Path: s: //usera.orange.com: 7965 / bar; tcp Success-Report: yes Byte-Range: 1 - * / * Message-ID: 87652 Content-Type: text / plain Hi UserB here is my mailing address: xxxx 6aef $ m2: 6aef 200 0K To-Path: s: //usera.orange. com: 7965 / bar; tcp From-Path: s: //polrelayl.orange.com: 9000 / kjfjan; tcp 6aef $ m3: xght6 SEND To-Path: s: //polrelay2.wanadoo.com: 8145 / zerty; tcp s: //userb.wanadoo.com: 8145 / foo; tcp From-Path: s: //polrelayl.orange. com: 9000 / kjfjan; tcp s: //usera.orange.com: 7965 / bar; tcp Success-Report: yes Message-ID: 87652 Byte-Range: 1 - * / * Content-Type: text / plain Hi UserB here is my mailing address: xxxx xght6 $ m4: Xght6 200 0K To-Path: s: //polrelayl.orange.com: 9000 / bar; tcp From-Path: s: //polrelay2.wanadoo. com: 8145 / zerty; tcp 6aef $ 10 30 35 m5: Az34q SEND To-Path: s: // polrelay2. wanadoo.com:8145/zerty;tcp s: //userb.wanadoo.com: 1234 / foo; tcp From-Path: s: //polrelayl.orange.com: 9000 / kjfjan; tcp s: //usera.orange .com: 7965 / bar; tcp Success-Report: yes Message-ID: 87652 Byte-Range: 1 - * / * Content-Type: text / plain Hi UserB here is my mailing address: xxxx xght6 $ m6: Az34q 200 OK To-Path: s: // polrelay2.wanadoo.com:8145/zerty;tcp From-Path: s: //userb.wanadoo.com: 1234 / kjfjan; tcp 6aef $ m7: yh67 REPORT To-Path: s: //polrelay2.wanadoo.com: 8145 / zerty; tcp s: //polrelayl.orange. com: 9000 / kjfjan; tcp s: //usera.orange.com: 7965 / bar; tcp From-Path: s: //userb.wanadoo.com:1234/foo; tcp Message-ID: 87652 Byte-Range: 1-39 / 39 Status: 000 200 0K yh67 $ Mg: yh67 REPORT To-Path: s: //polrelayl.orange. com: 9000 / kjfjan; tcp s: //usera.orange.com: 7965 / bar; tcp From-Path: s: //polrelay2.wanadoo.com: 8145 / zerty; tcp s: //polrelayl.orange. com: 9000 / kjfjan; tcp s: //userb.wanadoo.com: 1234 / foo; tcp From-Path: s: //userb.wanadoo.com:1234/foo; tcp Message-ID: 87652 Byte-Range: 1-39 / 39 Status: 000 200 OK yh67 m9: yh67 REPORT To-Path: s: //UserA.orange. com: 7965 / bar; tcp From-Path: s: //polrelayl.orange.com: 9000 / kjfjan; tcp s: //userb.wanadoo.com: 1234 / foo; tcp From-Path: s: // userb .wanadoo. com: 1234 / foo; tcp Message-ID: 87652 Byte-Range: 1-39 / 39 Status: 000 200 OK yh67 $ When the discussion is over, a user such as the TA user who wants to record the chat can then either save it locally or send it to a specific server, as previously described in the description relative to the prior art.

  The method which is the subject of the present invention will now be described with reference to FIG. 2a and the following figures.

  In general, it is recalled that the notion of logging covers not only the recording for saving messages, text messages, but also bibliographic data such as date of the discussion, billing data or other. 15 25 30 40

  Similar to the situation described in FIG. 1, the users of the TA and TB terminals wishing to communicate using the instant messaging system according to the MSRP protocol are considered similarly. The TA and TB terminals were of course designed to allow the storage of the addresses of the relay servers RS1 and RS2 as well as in the case of Figure 1.

  According to a remarkable aspect of the method of message logging, which is the subject of the invention, one and / or the other of the terminals TA and TB also has a log server, the aforementioned terminals being then parameterized, c ie provisioned, with the coordinates not only of all RS1 and RS2 relay servers but also an additional parameter giving the address of a registration relay server noted Slog.

  As shown in FIG. 2a, the method, which is the subject of the invention, furthermore consists in selecting in step A from a terminal, the terminal TA for example, the logging server Slog making it possible to ensure the logging messages. This choice is represented in step A of FIG. 2a. On positive answer to the test A of FIG. 2a, the step A of choice is followed by a step B of logging message messages and, of course, of transmission of these messages to the participating terminal TB and vice versa of the participating terminal. to the initiating terminal.

  In general, it is indicated that in this situation, the method that is the subject of the invention can consist in selecting a log server, the Slog server distinct from the aforementioned RS1 and RS2 relay servers.

  Slog logging server is then formed by an intermediate server ensuring, on the one hand, the transmission of messages to one of the relay servers, the RS1 server for example and, on the other hand, the logging of messages. These operations are executed between the relay server RS1 and the terminal TA which, in fact, proceeded to the selection of the logging server.

  A timing diagram of the message exchange between the terminal initiator terminal TA, the intermediate logging server Slog, the relay servers RS1, RS2 and the participating terminal TB will now be described in connection with FIG. 2b and FIG. 2c.

  With reference to FIG. 2b, it is indicated that the situation is set in which the user of the terminal TA decides to activate the system for recording the discussions and, of course, the parameterization of TA terminal with the recrelay.orange.com address of the Siog logging server.

  In addition to the exchange of authentication messages comparable to those shown in FIG. 1 between the initiator terminal TA and the logging server Slog, then between this log server and the relay server RS1, on the one hand, and between the participating terminal TB and the relay server RS2, on the other hand, these authentication messages being comparable to those previously described in connection with FIG. 1, the message exchange makes it possible in the first place to establish sessions under the following conditions: the user of the terminal TA transmits to the user of the terminal TB a request SDP including of course the log server Siog.

  The messages allowing the establishment of the aforementioned session can then have the following form: TA TB c = IN IP4 usera.orange. com m = message 1234 TCP / a = accept-types: message / cpim text / plain text / html a = path: s: //recrelay.orange.com: 3456 / aagrl; tcp s: //polrelayl.orange. com: 9000 / hjdhfha; tcp s: //usera.orange.com: 7965 / agic456; tcp TB -TA c = IN IP4 userb.wanadoo.com m = message 1234 TCP / TLS / * a = accept-types: message / cpim text / plain text / html a = path: s: //polrelay2.wanadoo. com: 9000 / hjdhfha; tcp s: //userb.wanadoo.com: 1234 / fuige; tcp In the message transmitted by the terminal TA to the terminal TB, the recording server Siog is introduced via its address recrelay.orange.com which is added first and therefore before the relay server RS1. It is of course understood that this location may vary and that the transaction can be executed differently. 15 20 30 40 50

  Since the MSRP session is open, the traffic between the different relay servers and the log server is much the same, except for the presence of the additional Slog relay server.

  The succession of messages transmitted and received by the TA initiating terminal, the Slog logging server, the RS1 and RS2 relay servers and the participating terminal is then the following: m'1: 6aef SEND To-Path: s: // recrelay .orange.com: 3456 / aagrl; tcp s: //polrelayl.orange. com: 9000 / kjfjan; tcp s: //polrelay2.wanadoo.com: 8145 / zerty; tcp s: // userb. wanadoo.com:1234/kjfjan;tcp From-Path: s: //usera.orange.com: 7965 / bar; tcp Success-Report: yes Byte-Range: 1 - * / * Message-ID: 87652 Content-Type : text / plain Hi UserB here is my mailing address. 6aef $ m'2: 6aef 200 0K To-Path: s: //usera.crange.com: 7965 / bar; tcp From-Path: s: // recrelay. orange.com:3456/aagrl;tcp 6aef $ m'3: xght6 SEND To-Path: s: // polrelayl. orange.com:9000/kjfjan;tcp s: //polrelay2.wanadoo.ccm: 8145 / zerty; tcp s: //userb.wanadoo.com: 1234 / foo; tcp From-Path: s: //recrelay.orange . com: 3456 / aagrl; tcp s: //usera.orange.com: 7965 / bar; tcp Success-Report: yes Message-ID: 87652 Byte-Range: 1 - * / * Content-Type: text / plain Hi UserB This is my mailing address.???? xght6 $ m'4: xght6 200 0K To-Path: s: //recrelay.orange.com: 3456 / aagrl; tcp From-Path: s: //polrelayl.orange. com: 9000 / kjfjan; tcp xght6 $ m'5: az34q SEND To-Path: s: //polrelay2.wanadoo. com: 8145 / zerty; tcp s: //userb.wanadoo.com: 1234 / foo; tcp From-Path: s: //polrelayl.orange.com: 9000 / kjfjan; tcp s: //recrelay.orange. com: 3456 / aagrl; tcp s: //usera.orange.com: 7965 / bar; tcp Success-Report: yes Message-ID: 87652 Byte-Range: 1 - * / * Content-Type: text / plain Hi UserB This is my mailing address.???? az34q $ me6: az34q 200 OK To-Path: s: //polrelay2.wanadoo.com: 8145 / zerty; tcp From-Path: s: //userb.wanadoo. com: 1234 / kjfjan; tcp az34q $ Mt ') phies9 SEND To-Path: s: //userb.wanadoo. com: 1234 / foo; tcp From-Path: s: //polrelay2.wanadoo.com: 8145 / zerty; tcp s: //polrelayl.orange.com: 9000 / kjfjan; tcp s: //recrelay.orange. com: 3456 / aagrl; tcp s: //usera.orange.com: 7965 / bar; tcp Success-Report: yes Message-ID: 87652 Byte-Range: 1 - * / * Content-Type: text / plain Hi UserB This is my mailing address.???? phies9 $ M'8: phies9 200 OK To-Path: s: //polrelay2.wanadoo.com: 8145 / zerty; tcp From-Path: s: //userb.wanadoo. com: 1234 / kjfjan; tcp phies9 $ yh67 REPORT To-Path: s: //polrelay2.wanadoo. com: 8145 / zerty; tcp s: //polrelayl.orange.com: 9000 / kjfjan; tcp s: // recrelay. orange.com:3456/aagrl;tcp s: //usera.orange.com: 7965 / bar; tcp From-Path: s: //userb.wanadoo.com:1234/foo; tcp Message-ID: 87652 Byte- Range: 1-39 / 39 Status: 000 200 OK yh67 $ - 12 - me10 yh67 REPORT To-Path: s: // polrelayl. orange.com:9000/kjfjan;tcp s: //recrelay.orange.com: 3456 / aagrl; tcp s: //usera.orange.com: 7965 / bar; tcp From-Path: s: //polrelay2.wanadoo . com: 8145 / zerty; tcp s: //userb.wanadoo.com: 1234 / foo; tcp From-Path: s: //userb.wanadoo.com:1234/foo; tcp Message-ID: 87652 Byte-Range: 1-39 / 39 Status: 000 200 0K yh67 $ me11: yh67 REPORT To-Path: s: //recrelay.orange. com: 3456 / aagrl; tcp s: //usera.orange.com: 7965 / bar; tcp From-Path: s: //polrelay2.wanadoo.com: 8145 / zerty; tcp s: //polrelayl.orange. com: 9000 / kjfjan; tcp s: //userb.wanadoo.com: 1234 / foo; tcp From-Path: s: //userb.wanadoo.com:1234/foo; tcp Message-ID: 87652 Byte-Range: 1-39 / 39 Status: 000 200 0K yh67 $ me12 yh67 REPORT To-Path: s: //UserA.orange. com: 7965 / bar; tcp From-Path: s: //recrelay.orange.com: 3456 / aagrl; tcp s: //polrelayl.orange.com: 9000 / kjfjan; tcp s: //polrelay2.wanadoo. com: 8145 / zerty; tcp s: //userb.wanadoo.com: 1234 / foo; tcp From-Path: s: //userb.wanadoo.com:1234/foo; tcp Message-ID: 87652 Byte-Range: 1-39 / 39 Status: 000 200 OK yh67 $ On the aforementioned messages, the parts in bold represent the changes introduced due to the selection of the S1og logging server.

  As regards the message m'1, it is indicated that the content of this message passes through the log server S1og and is then registered by the latter as a new discussion associated with the initiator terminal TA and in particular the usera address. orange.com. In this case, it is the first "SEND" message sent on this connection relating to this chat session.

  The message m'11 is a message of good reception of the message by the participating terminal TB this message of course of interest to the log server S1og and can be intercepted and used at the latter.

  The user of the participating terminal TB responds and continues the discussion as shown in connection with FIG. 2c. 10 20 35

  The response messages transmitted by the participating terminal TB take the same communication channel and therefore pass accordingly by the log server S1og. Each reply message with the same Uniform Resource Identifier (URI) URIs will be associated with the same discussion. The response messages transmitted by the participating terminal TB to the initiator terminal TA via the logging server Slog are represented in FIG. 2c and designated at 13 to 24.

  Finally, when the interlocutors have finished the discussion, the Slog logging server, like any conventional relay server, closes the associated connections after a specified delay. This closing event may mark the end of the discussion, the discussion then being considered as stopping at the last message before this connection closure.

  The aforementioned discussion recorded can then be accessed, accessed and / or manipulated by other protocols, such as the XCAP protocol for Xml Configuration Access Protocol in English.

  Of course, the method, which is the subject of the present invention, may be implemented according to a variant consisting in selecting instead of a relay server, such as the relay server RS1, an ambivalent server formed by a relay server comprising in besides a logging function.

  In this situation, the selected ambivalent server replaces the RS1 relay server, and thus makes it possible to make a real saving of traffic. This procedure can be executed by specifying not only the parameter indicating the relay server performing the recording, that is to say the replacement relay server, but also the relay server replaced, that is to say the server RS1 relay.

  Such a mode of operation is represented by the timing diagrams of FIGS. 2d and 2e for an ambivalent server designated RSllog of address polrecrelay. orange.com.

  In FIGS. 2d and 2e, the exchanged messages are denoted respectively m "1 for the message transmitted by the initiator terminal TA to the participating terminal TB and m" 2 for the response messages transmitted by the participating terminal TB to the - 14 - TA initiating terminal in the absence of logging, the ambivalent server RSllog being ignored for Figure 2d, respectively m "'1, respectively m"' 2 in log mode the ambivalent server RSliog then being substituted for the RS1 relay server as shown on Figure 2e. Of course the form of the messages is substantially the same as in the case of Figure 1 to the value of the addresses of the log server near ambivalent.

  A more detailed description of a message logging system according to the MSRP instant messenger protocol, in accordance with the subject of the present invention will now be given in connection with FIGS. 3a and 3b.

  FIG. 3a shows the journaling system that is the subject of the invention, involving the initiator terminal TA entering into communication with at least one participating terminal TB, via relay servers RS1 and RS2 selected from at least one of one of the terminal initiator terminals TA and / or participant TB, as described previously in the description. The system also comprises, as represented in FIG. 3a, the Slog logging server of address recrelay.orange.com, this address being an address specific to the aforementioned log server. It is understood, in particular, as represented in FIG. 3a, that the log server represented in the above-mentioned figure is a separate server operating in accordance with the message exchange protocol as represented in FIGS. 2b and 2c above.

  As shown specifically in FIG. 3a, the system, which is the subject of the invention, furthermore comprises a selection module for the log server installed in one of the terminals and in particular, as shown in the above-mentioned figure, on the initiator terminal TA.

  According to a remarkable feature of the system, object of the invention, the selection of the log server is performed by calling from the aforementioned terminal of the specific address recrelay. orange.com of the logging server to further ensure logging of the company discussion.

  For this purpose, as shown in Figure 3a, there is shown the address of the log server Siog, address recrelay. orange.com stored in a part or memory area of the TA initiating terminal this address can of course be called from the relay server addresses according to the message exchange protocol, as described in connection with Figures 2b and 2c above.

  With reference to FIG. 3a, it is understood in this case that the separate log server of the relay servers is then constituted by an intermediate server ensuring the transmission of messages to one of the relay servers, in particular the server RS1, between the terminal TA and the aforementioned relay server. It is understood, of course, that the transmission of messages can then be performed by redirection by address change at the aforementioned S1og log server. Of course, the log server also performs the logging function for which this server is provided.

  FIG. 3b shows a system according to the subject of the present invention according to a second embodiment, in which the logging server is an ambivalent server, that is to say the RSiiog server of address polrecrelay .orange.com, this relay server further comprising a logging function.

  In this situation, it is understood that while the separate log server S1og and the server RS1, which although physically present on the network, are then ignored and therefore represented in dotted lines, the transaction between the terminal initiator terminal TA and the participating terminal TB, that is to say the transfer of messages between them is performed only through the ambivalent server RSüog address polrecrelay.orange. com, and the relay server RS2 as shown in Figure 2e previously described.

  Regarding the mode of operation of the selection of the log server, regardless of the type of log server used and selected by the user, it is indicated with reference to FIGS. 3a and 3b that the module for selecting the server for logging logging implemented on the corresponding terminal TA as an example in the above figures, comprises at least one module for selecting the address of the corresponding log server is recrelay.orange. com respectively polrecrelay.orange.com, for the systems represented in the aforementioned figures, and inserting this address in the address list of the relay servers ensuring the communication between the terminal initiator terminal TA and at least one participating terminal TB according to the MSRP protocol in relay mode.

  The method and the message logging system, objects of the invention, thus have a very great flexibility of implementation and use.

  When, initially, neither the user of the terminal initiator terminal TA nor the user of the participating terminal TB wishes to record the discussion they are executing, the discussion messages go through the conventional relay servers RS1 and RS2 which materialize the course of the aforementioned messages. This use corresponds to a conventional use of the MSRP protocol in relay mode.

  When, on the other hand, one of the users such as the user of the terminal TA decides to record the discussion, he activates, for example, the function on his terminal TA via an option of his human interface. machine. The terminal TA then adds the address recrelay. orange.com Siog logging server for example in the list of servers to cross. This requires updating the SDP negotiation as provided in http: //www.ietf. org / internetdrafts / draft-ietf-simple-message-sessions-10.txt chapter 8.1. 3 "updated SDP offer".

  The discussion messages are then logged automatically and transit through the servers shown in Figure 3a according to the message exchange protocol as shown in Figures 2b and 2c.

  According to another embodiment, and by way of example, when the user of the initiator terminal TA decides ab initio to record the discussion, the selection of the log server may then correspond to an ambivalent log server. and the selection of the address polrecrelay.orange.com of the latter as shown in Figure 3b. In this situation, logging is automatic as soon as the ab initio log server is selected.

  A more detailed description of a terminal operating according to the MSRP instant messenger protocol in accordance with the subject of the present invention will now be given in connection with FIG. 4.

  Of course, the aforementioned terminal includes all the functions of a mobile communication terminal for example and in particular access to the instant messaging service normally available. In addition, it includes a human-machine interface consisting of an SC display screen and a conventional KB keyboard to ensure an interactive dialogue between the user and the terminal.

  According to a remarkable aspect of the terminal, object of the invention, it comprises a module M for selecting a specific address log server by the insertion of this specific address in a relay server address list allowing placing the aforementioned terminal in communication with at least one other terminal according to an instant messaging protocol in relay mode.

  For this purpose, in addition to a processing processor or processing CPU 1 o and RAM working memory 11 present in the terminal, the module M can advantageously be formed by a program module 2 and a programmable memory 31, 32 for storing the list of addresses of the relay servers allowing the communication of the terminal concerned with at least one other terminal according to the MSRP protocol in relay mode.

  It is understood in particular that the programmable memories 31 and 32 advantageously make it possible to store the address of the aforementioned relay servers or an identifier of the abovementioned addresses, identifier designated RS1 and RSilog, RS2 in FIG. 4, respectively the address of the ambivalent server Siog during parameterization, that is to say the provisioning of the terminal considered.

  When the user starts the terminal TA, the program module 2 allows the loading of the relay servers RS1, RS2 into working memory 11. The human-machine interface then offers the latter the choice of the journaling , that is to say the recording of the discussion ab initio or the possibility of declining this choice.

  On positive response for example, the storage choice having been made, the address of the ambivalent server RS1log can then be loaded into working memory 11, the program module 2 then replacing the address of the relay server RS1 by that The message exchange protocol is then carried out between the abovementioned addresses.

  On the contrary, on declination of the choice by the user to proceed to a logging, the communication is established from the addresses of the relay servers RS1 and RS2 present in working memory.

  When, during the discussion, the user of the terminal considered decides to proceed with the logging of the discussion messages, then the address of the separate log server S1og is loaded from the memory zone 32 into working memory 11 by the module of program 2 and the message exchange session is then modified in that the path to be used for the session is updated from the addresses of the relay servers RS1, RS2 which is of course added the address of the server of S1og separate logging, as previously described in connection with Figures 2b and 2c.

  The invention therefore also covers a computer program product stored on a storage medium for execution by a computer, characterized in that it comprises a module M for selecting a specific address log server by the computer. inserting this specific address into a list of relay server addresses allowing communication of a terminal with another terminal, according to a relay mode instant messaging protocol.

Claims (11)

  A method of logging messages according to a relay mode instant messaging protocol, in which an initiating terminal communicates with at least one participating terminal via at least one relay server selected from said terminals, characterized in that said method comprises selecting, from one of said terminals, a message logging server for logging said messages.   2. Method according to claim 1, characterized in that the selected message logging server is a server separate from said at least one relay server, said log server being provided by an intermediate server providing between said at least one relay server and said terminal for selecting said log server, on the one hand, the transmission of messages to said at least one relay server, and, on the other hand, the logging of said messages ,.   3. Method according to claim 1, characterized in that the logging server selected is an ambivalent server formed by a relay server having a logging function.   4. Message logging system according to a relay mode instant messaging protocol, in which an initiating terminal communicates with at least one participating terminal via at least one relay server selected from one of said terminals characterized in that said logging system comprises at least: a specific address message logging server; and means for selecting said log server located in at least one of said terminals, by connection from said terminal to said specific address, selecting said log server to ensure the logging of said messages.   5. System according to claim 4, characterized in that said log server is a separate server of said at least one relay server, said log server being constituted by an intermediate server providing between said one at least terminals and said at least one relay server, on the one hand, the transmission of messages to said at least one relay server, and, on the other hand, the logging of said messages.   6. System according to claim 4, characterized in that said log server is an ambivalent server formed by a relay server having a logging function.   7. System according to one of claims 4 to 6, characterized in that said means for selecting said log server include at least means for selecting the address of said server for logging and inserting said address in the list. relay server addresses ensuring the communication between said initiator terminal and at least one participating terminal.   8. Message logging server, characterized in that said server comprises: means for transferring messages to a relay server ensuring the communication of an initiator terminal and at least one participating terminal according to an instant messaging protocol in relay mode; and, means for logging messages.   9. Message logging server, characterized in that said server is an ambivalent server formed by a relay server ensuring the communication of an initiator terminal and at least one participating terminal according to an instant messaging protocol relay mode and having a logging function.   10. Terminal operating according to an instant messaging protocol in relay mode, characterized in that said terminal comprises means for selecting a specific address message logging server by inserting said specific address in a list of addresses. relay server enabling the communication of said terminal with at least one other terminal, according to said instant messaging protocol.   11. Computer program product stored on a storage medium for execution by a terminal, characterized in that it comprises a module for selecting a specific address log server by inserting said specific address in a list. relay server addresses enabling the communication of said terminal with another terminal, according to a relay mode instant messaging protocol.