EP3516851B1 - Verfahren zum austausch von nachrichten und zur verwaltung von nachrichten, endgerät und nachrichtenserver - Google Patents

Verfahren zum austausch von nachrichten und zur verwaltung von nachrichten, endgerät und nachrichtenserver Download PDF

Info

Publication number
EP3516851B1
EP3516851B1 EP17784361.2A EP17784361A EP3516851B1 EP 3516851 B1 EP3516851 B1 EP 3516851B1 EP 17784361 A EP17784361 A EP 17784361A EP 3516851 B1 EP3516851 B1 EP 3516851B1
Authority
EP
European Patent Office
Prior art keywords
terminal
network
contact
user
message
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
EP17784361.2A
Other languages
English (en)
French (fr)
Other versions
EP3516851A1 (de
Inventor
Jean-Claude Le Rouzic
Marc Bailly
Yann Gestraud
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Orange SA
Original Assignee
Orange SA
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Orange SA filed Critical Orange SA
Publication of EP3516851A1 publication Critical patent/EP3516851A1/de
Application granted granted Critical
Publication of EP3516851B1 publication Critical patent/EP3516851B1/de
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12—Messaging; Mailboxes; Announcements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0022—Control or signalling for completing the hand-off for data sessions of end-to-end connection for transferring data sessions between adjacent core network technologies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/04—Real-time or near real-time messaging, e.g. instant messaging [IM]
    • H04L51/043—Real-time or near real-time messaging, e.g. instant messaging [IM] using or handling presence information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/07—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail characterised by the inclusion of specific contents
    • H04L51/10—Multimedia information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/58—Message adaptation for wireless communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/54—Presence management, e.g. monitoring or registration for receipt of user log-on information, or the connection status of the users
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H04W36/30—Reselection being triggered by specific parameters by measured or perceived connection quality data
    • H04W36/305—Handover due to radio link failure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12—Messaging; Mailboxes; Announcements
    • H04W4/14—Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • H04W68/005—Transmission of information for alerting of incoming communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/08—Upper layer protocols
    • H04W80/10—Upper layer protocols adapted for application session management, e.g. SIP [Session Initiation Protocol]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/18—Service support devices; Network management devices
    • H04W88/184—Messaging devices, e.g. message centre
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0022—Control or signalling for completing the hand-off for data sessions of end-to-end connection for transferring data sessions between adjacent core network technologies
    • H04W36/00224—Control or signalling for completing the hand-off for data sessions of end-to-end connection for transferring data sessions between adjacent core network technologies between packet switched [PS] and circuit switched [CS] network technologies, e.g. circuit switched fallback [CSFB]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/34—Reselection control
    • H04W36/36—Reselection control by user or terminal equipment

Definitions

  • the invention relates to communication by messages.
  • the invention relates to communication by messages as provided for by the RCS (Rich Communication Services) mobile telephone standard.
  • RCS mobile telephone standard One of the services offered by the RCS mobile telephone standard is rich messaging. This messaging service allows users to exchange text or multimedia messages.
  • the RCS standard like other instant messaging services, is based on the IP protocol requiring a connection to a data network or data connectivity.
  • the main disadvantage for mobile phone, smartphone, etc. users of this type of messaging is that the connection to the data network is often fluctuating due to the nomadic nature of the terminals used to access the IP messaging service. For example, when a terminal of user A sends an IP message to a terminal of user B, if the telephone of recipient B of the IP message is not connected to the data network, the terminal of recipient B will not will not receive the IP message intended for it. This is why the RCS standard provides a storage and transfer functionality, called “Store & Forward”, which allows the data network messaging server to keep the IP message until the recipient's telephone B regains data coverage, that is to say it reconnects to the data network. The mail server will then push the retained IP message to recipient B's phone.
  • Store & Forward storage and transfer functionality
  • the “Store & Forward” function therefore makes it possible to compensate for fluctuating network coverage but not the absence of access to the data network for a long period (deactivation of the use of the data network, particularly in “roaming”, this that is to say when the terminal of recipient B uses the network of an operator partner of the operator with whom it has subscribed, for example abroad). Indeed, even if the terminal of recipient B retrieves the IP message intended for it after this long period, the proposed messaging loses its interest since it loses its so-called “instantaneous” character.
  • the RCS standard has provided a fallback mode: the exchange of messages by SMS therefore using a fallback network, in this case the mobile telephone network or cellular network.
  • the terminal of user A when the IP message sent by the terminal of user A is not transmitted to the terminal of user B because the latter is not connected to the data network, the terminal of user A retransmits the message in SMS form to user B's terminal. User A's terminal then switched to SMS transmission mode for user B's terminal.
  • the RCS standard provides for verification of the connection of user B's terminal by polling.
  • the terminal of user A in SMS transmission mode for a terminal of user B checks the IP connectivity of the terminal of user B.
  • SIP OPTIONS To capacities between IP terminals by messages predefined by the RCS standard called “SIP OPTIONS” and an analysis of the responses.
  • the disadvantage of the polling method is that it consumes resources.
  • the document “RCS Common Core Service Description Document, version 1.0” dated September 16, 2014 from GSM Association Non-confidential Official Document RCC.61 describes several use cases for exchanging messages between two parties: a transmitter 1 and a receiver B.
  • the messaging service used to transmit the messages depends on the connectivity statuses of the transmitter A and the receiver B.
  • a transmitter A exchanges by means of RCS messaging then it loses its IP connection allowing the use of RCS messaging, messages will then be exchanged in xMS.
  • transmitter A recovers its IP connection if receiver B has started to exchange messages with 1 in xMS, then this document does not provide for a return of message exchanges between these two terminals in RCS. In this case, the exchange of messages is not optimized.
  • One of the aims of the present invention is to provide improvements compared to the state of the art.
  • An object of the invention is a method of exchanging messages implemented by a terminal of a user capable of transmitting a message via a network among: a first network and a second network, the method of exchanging messages comprises , when the user's terminal is in a second transmission mode, using the second network, for a terminal of a contact, triggering a switch of the user's terminal into a first transmission mode, using the first network, for the contact's terminal upon receipt of a notification, to the user's terminal, of connection to the first network of the contact's terminal coming from a messaging server on the first network, the connection notification being received from the messaging server by the user's terminal upon receipt by the messaging server of a message from the contact's terminal via the first network.
  • the return to use of the first network by the user's terminal depends on only one message: the connection notification.
  • THE exchanges to determine the capabilities of the contact's terminal are thus reduced since this notification is sent only when the connection of the contact's terminal to the first network is effective.
  • the invention therefore makes it possible to reduce the use of resources.
  • the switchover is carried out following detection, by the messaging server, of connection of the contact's terminal to the first network.
  • the return to use of the first network by the user's terminal does not depend on the periodic sending of requests on the capabilities of the contact's terminal and the analysis by the user's terminal of a response from the contact's terminal, particularly during a polling method, but connection detection by the messaging server.
  • the invention therefore makes it possible to reduce the use of terminal resources and the first network.
  • the first network is a data network and the second network is a circuit network.
  • message exchanges are faster thanks to the data network used as the default network and the fallback network is more secure in terms of connectivity for nomadic terminals.
  • An object of the invention is also a device for communicating messages from a user's terminal, the communication device capable of transmitting a message via a network among: a first network and a second network, the communication device comprising a controller capable of triggering, upon receipt of a notification to the user's terminal of connection to the first network of a terminal of a contact coming from a messaging server on the first network, a switching of the terminal of the user in a first transmission mode, using the first network, for the contact's terminal, when the user's terminal is in a second transmission mode, using the second network, for a contact's terminal, the notification of connection being received by the user's terminal of the messaging server upon receipt by the messaging server of a message from the contact's terminal via the first network
  • An object of the invention is also a user's terminal comprising a message communication device capable of transmitting a message via a network among: a first network and a second network, the user's terminal comprising a controller capable of trigger, upon receipt of a notification to the user's terminal of connection to the first network of a terminal of a contact coming from a messaging server on the first network, a switch of the user's terminal into a first transmission mode, using the first network, for the contact's terminal, when the user's terminal is in a second transmission mode, using the second network, for a contact's terminal, the connection notification being received by the terminal of the user of the mail server upon receipt by the mail server of a message from the contact's terminal via the first network
  • An object of the invention is also a message management method implemented by a messaging server on a first network, the message management method comprises, when a user's terminal is in a second transmission mode , using a second network, for a contact's terminal a transmission to the user's terminal of a notification of connection to the first network of the contact's terminal upon receipt of a message from the contact's terminal via the first network, the connection notification triggering a switch of the user's terminal into a first transmission mode, using the first network, for the contact's terminal.
  • the return to use of the first network by the user's terminal depends on only one message: the connection notification.
  • the exchanges to determine the capabilities of the contact's terminal are reduced since this notification is sent only when the connection of the contact's terminal to the first network is effective.
  • the invention therefore makes it possible to reduce the use of resources.
  • the message management method comprises, when a terminal of a user is in a second transmission mode for a terminal of a contact, detection of a connection to the first network of the contact's terminal, following which the connection notification is sent.
  • the return to use of the first network by the user's terminal does not depend on the periodic sending of requests on the capabilities of the contact's terminal and the analysis by the user's terminal of a response from the contact terminal, particularly during a polling method, but connection detection by the mail server.
  • the invention therefore makes it possible to reduce the use of terminal resources and the first network.
  • the detection of connection to the first network of the contact's terminal comprises detection of a message coming from the contact's terminal via the first network.
  • any message on the first network coming from the contact's terminal detected by the messaging server whatever the type of message and the recipient of the message, will trigger the switch to the first transmission mode of the user's terminal for the message exchange with the contact's terminal.
  • the detection of connection to the first network of the contact terminal comprises a detection of a reception by the messaging server of a command message for deletion of a message stored on the messaging server, the command message coming from the contact terminal.
  • the message management method comprises, when a terminal of a user is in a second transmission mode for a terminal of a contact, a generation of a notification of connection to the first network of a terminal of a contact of a terminal of a user, generating the connection notification providing the connection notification generated upon transmission to the user's terminal.
  • the connection notification sent may depend on the contact's terminal and/or the user's terminal.
  • connection notification In the first case, triggering the generation by connection detection, the transmission can be triggered indirectly by connection detection by receiving the connection notification generated on command of this connection detection. Thus, the generated notification will not have to be kept before its issuance.
  • the connection notification may be generated not concomitantly with its emission. This makes it possible to reduce the latency between the detection of the connection of the contact's terminal to the first network and the switching of the user's terminal into the first transmission mode for the contact's terminal.
  • an implementation of the transmission of the notification is a function of a connection state to the first network of the user's terminal.
  • the different steps of the methods according to the invention are implemented by software or computer program, this software comprising software instructions intended to be executed by a data processor of a device forming part of a user's terminal or a messaging server and being designed to control the execution of the different stages of these processes.
  • the invention therefore also targets a program comprising program code instructions for executing the steps of the message exchange method, and/or the message management method when said program is executed by a processor.
  • This program may use any programming language and be in the form of source code, object code or intermediate code between source code and object code such as in partially compiled form or in any other desirable form.
  • An object of the invention is also a messaging server of a first network comprising a transmitter making it possible to transmit, when a terminal of a user is in a second transmission mode, using a second network, for a terminal of 'a contact, to the user's terminal a notification of connection to the first network of the contact's terminal upon receipt of a message from the contact's terminal via the first network, the connection notification triggering a switch of the user's terminal in a first transmission mode, using the first network, for the contact terminal
  • the messaging server includes a connection detector to the first network of a terminal of a contact capable of triggering a transmission by the transmitter of the connection notification.
  • FIGS. 1a and 1b illustrate the prior art.
  • FIG. 1a illustrates a message exchange diagram implementing the RCS standard in the case where the user's terminal is connected to the first network when a contact's terminal reconnects to the first network, according to the prior art.
  • the RCS standard provides that reception by a user's terminal of a message from the contact's terminal via the first network triggers the return of the user's terminal to a transmission mode using this first network to the contact terminal.
  • FIG 1a shows a terminal of a TU user exchanging messages: mssg1, mssg2, mssg3, mssg4 with a terminal of a TC contact.
  • the RCS standard provides that a first network is used as the default network for message transmission: the IP network and that a second network is used as a fallback network: SMS network.
  • the terminal of the user TU sends to the terminal of a contact TC a first message mssg1 on the default network: the first network, snd1 (mssg1).
  • the terminal of the contact TC not being connected to the first network: TC ⁇ cnx 1
  • the messaging server of the terminal of the contact SM C receives the first message mssg1 and stores it in particular in a temporary memory or a message database BDD_MSSG with a view to transferring it to the contact's terminal when it is again connected to the first network.
  • the user's terminal TU then triggers a countdown of a predetermined period of time at the end of which, if the first message mssg1 has not been transmitted by the messaging server SM C to the terminal of the contact TC, the terminal of the user TU sends a revocation of the transfer of the first message to the mail server SM C: Revoke(mssg1).
  • the first message mssg1 is deleted from the BDD_MSSG memory of the SM C messaging server.
  • sending by terminal of the user TU of a fourth message to the terminal of the contact TC will be made using the first network: send1 (mssg4).
  • FIG 1b illustrates a message exchange diagram implementing the RCS standard in the case where the user's terminal is disconnected from the first network when a contact's terminal reconnects to the first network, according to the prior art.
  • the first phase Ph l not illustrated corresponds to that of the figure 1a .
  • the contact terminal reconnected to the first network TC cnx 1.
  • the terminal of the contact TC sends on the default network, namely the first network, a third message to the terminal of the user TU: snd1 (mssg3). If at that time, the terminal of the user TU is disconnected from the first network TU ⁇ cnx1, then the third message will not be delivered to the terminal of the user TU via the first network.
  • the terminal of the user TU not being connected to the first network: TU ⁇ cnx 1 the messaging server of the terminal of the user SM U receives the third message mssg3 and stores it in particular in a temporary memory or a database.
  • BDD_MSSG message data with a view to transferring it to the user's terminal TU when it is again connected to the first network.
  • the terminal of the contact TC then triggers a countdown of a predetermined period of time at the end of which, if the third message mssg3 has not been transmitted by the messaging server SM U to the terminal of the user TU, the terminal of the TC contact sends a revocation of the transfer of the third message to the SM U messaging server: Revoke(mssg3).
  • the third message mssg3 is deleted from the BDD_MSSG memory of the SM U messaging server.
  • send2(mssg4) the two terminals: the terminal of the user TU and the contact terminal TC are connected to the first network.
  • FIG. 2 illustrates a simplified diagram of a message exchange method implemented by a user's terminal according to the invention.
  • the method for exchanging PEM messages comprises, when the user's terminal is in a second transmission mode for a terminal of a contact, triggering a SWT_TRG switchover of the user's terminal into a first mode of transmission.
  • transmission for the terminal of the contact MT (tc) MT1 upon receipt of a notification to the terminal of the user of connection to the first network N1 of the terminal of the contact tc_cnx1_ntf coming from a messaging server on the first network SM U.
  • the SWT_TRG switchover is triggered following detection, by the messaging server SM U , of connection of the contact terminal TC to the first network N1.
  • the first network N1 is a data network, in particular an IP network and the second network N2 a circuit network, in particular a cellular network.
  • the switchover trigger SWT_TRG sends a command to modify the transmission mode for the terminal of the contact mt_mdf(tc), in particular to a contact database BDDC, in which the transmission mode for each terminal of a contact is stored at least when the transmission mode is the fallback transmission mode, namely the second transmission mode.
  • the exchange method comprises, when sending a message to a terminal of a contact, a consultation of the BDDC contact database making it possible to determine the mode of transmission of the message to the terminal of the contact. contact.
  • the message When transmitting a message to a contact's terminal, the message is provided by default for transmission according to a first transmission mode, that is to say using the first network N1.
  • the method of exchanging messages comprises this transmission of the message according to the first mode of transmission.
  • the contact terminal TC is not connected to the first network N1
  • the mssg message is provided for transmission according to a second transmission mode MT2_TR, that is to say using the second network N2.
  • the provision of the message on transmission according to the second transmission mode is carried out by a CMT switching of the supply of the message from transmission according to the first transmission mode MT1_TR to transmission according to the second transmission mode MT2_TR depending on 'a transmission mode associated with the terminal of the contact recipient of the MT(tc) message.
  • the switchover trigger SWT_TRG sends the transmission mode modification command mt_mdf(tc) to the message supply CMT switching which then switches from message supply to transmission according to the second transmission mode MT2_TR at transmission according to the first transmission mode MT1_TR for the transmission of a message to the contact terminal TC.
  • a particular embodiment of the message exchange method is a program comprising program code instructions for executing the steps of the message exchange method according to any one of the claims when said program is executed by a processor .
  • FIG. 3 illustrates a simplified diagram of a message management method implemented by a messaging server according to the invention.
  • the PGM message management method comprises, when a terminal of a user TU is in a second transmission mode MT2 for a terminal of a contact TC, a transmission SND to the terminal of the user TU of a notification of connection to the first network of the terminal of the contact tc_cnx1_ntf, the connection notification tc_cnx1_ntf triggering a SWT_TRG switchover of the terminal of the user TU in a first transmission mode MT1 for the terminal of the contact TC.
  • the PGM message management method comprises, when a terminal of a user is in a second transmission mode for a terminal of a contact, a detection of a connection to the first network of the terminal of the contact TC_CNX1_DTCT, following which the SND connection notification is issued.
  • the detection of connection to the first network of the terminal of the contact TC_CNX1_DTCT comprises an MSSG TC _DTCT detection of an mssg message coming from the terminal of the contact TC via the first network N1.
  • the detection of connection to the first network of the terminal of the contact TC_CNX1_DTCT includes a detection MSSG TC _DTCT of a reception by the messaging server SM of a command message for deletion of a message stored on the revoke_mssg messaging server , the revoke_mssg command message coming from the TC contact terminal.
  • the PGM message management method comprises, when a terminal of a user is in a second transmission mode for a terminal of a contact, an NTF TU _GN generation of a notification of connection to the first network of 'a terminal of a tc_cnx1_ntf contact of a terminal of a TU user, the generation of the NTF connection notification TU _GN providing the generated connection notification tc_cnx1_ntf to the SND transmission to the terminal of the TU user.
  • the SND transmission of the tc_cnx1_ntf notification is carried out when the terminal of the user TU is in a second transmission mode MT2 for the terminal of the contact TC.
  • the PGM message management method receives from the user's terminal information indicating the switch of the user's terminal TU into the second transmission mode MT2 for the terminal of the contact TC.
  • the message management method PGM determines whether the terminal of the user TU is in a second transmission mode MT2 for the terminal of the contact TC.
  • the PGM message management method includes detection of switching of the user's terminal into the second transmission mode TU_MT2_DTCT.
  • the detection of switching to the second transmission mode TU_MT2_DTCT includes a REVOKE_DTCT detection of the revocation or deletion messages of the stored messages coming from the terminal of the user TU.
  • the determination of the switchover into the second transmission mode MT2 of a terminal of a user TU for a terminal of a contact TC reception of switchover information, detection of the switchover TU_MT2_DTCT triggers trgTU(tc) monitoring of the first network N1_MNT triggering the SND transmission of a connection notification to the first network of the terminal of the contact tc_cnx1_ntf.
  • This monitoring of the first network N1_MNT includes at least one detection TC_CNX 1 _DTCT of connection of the contact terminal to the first network.
  • the determination of the switchover in the second transmission mode MT2 of a terminal of a user TU for a terminal of a contact TC reception of switchover information, detection of the switchover TU_MT2_DTCT triggers trgTU(tc) the generation of NTF TU _GN connection notification, which triggers dtct_trg, itself, the TC_CNX 1 _DTCT detection of connection of the contact terminal to the first network.
  • the delay between connection to the first network of the contact's terminal and switching of the user's terminal to the first connection mode for the contact's terminal is optimized since it reduces the generation time of the NTF connection notification YOU _GN.
  • TC_CNX 1 _DTCT detection of connection of the contact's terminal to the first network which triggers snd_trg directly or indirectly the transmission SND to the terminal of the user TU of the tc_cnx1_ntf notification provided by the generation of connection notification NTF TU _GN.
  • determining the switchover to the second transmission mode MT2 of a terminal of a user TU for a terminal of a contact TC reception of switchover information, detection of the switchover TU_MT2_DTCT triggers trgTU(tc) the TC_CNX 1 _DTCT detection of connection of the contact terminal to the first network, which triggers dtct_trg, itself, the generation of NTF TU _GN connection notification.
  • the storage resources of the SM messaging server are optimized since the tc_cnx 1 _ntf connection notification is only stored if the user's terminal TU is not connected to the first network N1 when generating the NTF TU _GN connection notification. In this case, it is the generation of NTF connection notification TU _GN which provides the tc_cnx1_ntf connection notification and triggers snd_trg directly or indirectly its transmission SND to the terminal of the TU user.
  • an indirect snd_trg triggering of the SND transmission it is a transmission to a terminal of a user SND_TU which is triggered snd_trg directly either by the connection detection TC_CNX1_DTCT, or by the generation of connection notification NTFTU_GN , or by monitoring the first network N1_MNT.
  • the transmission to the terminal of the user SND_TU includes the transmission SND of the connection notification tc_cnx1_ntf to the terminal of the user TU.
  • the transmission to the user's terminal SND_TU also includes a verification of the connection of the user's terminal to the first network TU_CNX1?.
  • connection of the user's terminal to the first network TU_CNX1? is verified [Y], that is to say if the terminal of the user TU is connected to the first network N1, then the verification TU_CNX1? triggers snd_trg the transmission SND to the terminal of the user TU of the connection notification tc_cnx1_ntf provided by the generation of NTF connection notification TU _GN. If the connection of the user's terminal to the first network TU_CNX1? is not verified [N], that is to say if the terminal of the user TU is not connected to the first network N1, then the verification TU_CNX1? triggers connection detection of the user's terminal to the first network TU_CNX1_DTCT.
  • the reception by the messaging server of an mssg message coming from the terminal of the user TU via the first network N1 makes it possible to detect such a connection to the first network.
  • the message is, for example, a registration message on the first network N1, such as SIP REGISTER.
  • the detection of connection of the user's terminal to the first network TU_CNX1_DTCT triggers snd_trg the transmission SND to the user's terminal TU of the connection notification tc_cnx1_ntf provided by the generation of NTF connection notification TU _GN, and possibly stored in a mail server memory.
  • the monitoring of the first network N1_MNT also includes the verification TU_CNX1? and, if the connection of the user's terminal to the first network TU_CNX1? is not checked [N], the detection of connection of the user's terminal to the first network TU_CNX1_DTCT.
  • connection notification transmission the provision, also called “push” function in English, of a storage and transfer process implemented by the messaging server, in particular the “store&forward” or “push enabler” function as provided in certain standards: e.g. the RCS, OMA, etc. standard.
  • the delivery or "push” function could send in addition to the messages stored by the messaging server, in particular while waiting for a reconnection of the recipient's terminal, a new type of content namely tc_cnx1_nft notifications of connection of contacts to the first network as provided by the invention.
  • the storage of the store and transfer process implemented by the messaging server in particular the “store&forward” or “push enabler” function as provided for in certain standards: e.g. the RCS, OMA, etc. standard. can be used to keep the connection notification generated by the message management method while waiting for the transmission of the connection notification to be triggered.
  • the messaging server of the terminal of the contact SM C can implement detection of connection of the contact to the first network TC_CNX 1 _DTCT triggering an SND transmission of a notification of connection of the terminal of contact TC to the first network N1.
  • the transmission by the messaging server of the contact SM C to the first network is carried out to the messaging server of the terminal of a user SM U having switched to a second transmission mode MT2 for the terminal of the contact TC.
  • a reception by the messaging server of the user's terminal SM U of the notification of connection of the contact's terminal to the first network tc_cnx1_ntf, tc_cnx1_ntf* constitutes, in particular, the detection of connection of the contact's terminal to the first network TC_CNX 1 _DTCT by the messaging server of the user's terminal SM U triggering the transmission SND, by the messaging server of the user's terminal SM U , of a notification of connection of the contact's terminal to the first network tc_cnx1_ntf.
  • connection notification tc_cnx1_ntf is sent by the messaging server of the terminal of the user SM U to the terminal of the user TU triggering the switch to the first transmission mode SWT_TRG of the terminal of the user TU for the terminal of the CT contact.
  • the mail server of the terminal of the user SM U relays the connection notification received tc_cnx1_ntf from the mail server of the terminal of the contact SM C
  • the mail server of the terminal of the user SM U generates NTF TU _GN a new connection notification tc_cnx1_ntf following receipt of the connection notification received tc_cnx1_ntf * from the mail server of the SM C contact terminal, also called inter-operator notification tc_cnx1_ntf*.
  • the PGM message management process can also be implemented by the messaging server of the SM C contact terminal (cf. figures 5, 6 ), and the method of exchanging PEM messages by the terminal of the contact TC which then becomes the terminal of the claimed user.
  • the description and the claims will be read by replacing the user's terminal with the contact's terminal and, conversely, the contact's terminal with the user's terminal.
  • a particular embodiment of the message management method is a program comprising program code instructions for executing the steps of the message management method according to any one of the claims when said program is executed by a processor.
  • FIG 4 illustrates a message communication architecture implementing a user's terminal and a messaging server according to the invention.
  • An object of the invention is a message communication device 11.
  • the message communication device 11 is implemented in a terminal 1 of a user U.
  • the communication device 11 transmits an mssg message via a network 3 1 , 3 2 among: a first network 3 1 and a second network 3 2 .
  • the communication device 11 comprises a controller 12 triggering cmd, upon receipt of a tc_cnx1_ntf notification to the terminal of the user 1 of connection to the first network of the terminal of the contact coming from a messaging server 4 on the first network 3 1 , a switch of the terminal of the user 1 in a first transmission mode MT1 for a terminal 2 of a contact C, when the terminal of the user 1 is in a second transmission mode MT2 for the contact terminal 2.
  • the message communication device 11 comprises a switch 111 making it possible to provide a message to a first transmitter 10 1 , that is to say a transmitter on a first network, or a second transmitter 10 2 , that is to say a transmitter on a second network, depending on the transmission mode of the switch 111, respectively the first transmission mode MT1 or the second transmission mode MT2 .
  • the controller 12 then commands cmd , upon receipt of a tc_cnx1_ntf notification of connection to the first network of the contact's terminal, the switching of the switch 111 into a first transmission mode MT1 when sending a message to the terminal of the contact. contact 2.
  • the message communication device 11 includes a contact database 12 (not shown). That is, at least the terminals of the contacts 2 are registered in this contact database 12 when they are not connected to the first network 3 1 .
  • the switch 111 is, by default in the first transmission mode, and consults, for the terminal of contact 2 to which the mssg message is intended, the contact database 12. If the terminal of contact 2 is registered in the base 12, the switch 12 switches to the second transmission mode MT2. Then, on receipt of a tc_cnx1_ntf notification of connection to the first network of the contact's terminal, the controller 12 commands cmd the deletion of the terminal of contact 2 from the database 12, switching the terminal of user 1 into the first mode transmission for the terminal of contact 2.
  • the switch 111 consulting, for the terminal of contact 2 for which an mssg message is intended, the contact database 12 and not finding the terminal of contact 2 there, remains, by default, in the first transmission mode MT1 for sending the message to the terminal of contact 2. That is, the terminals 2 of all the contacts of the terminal of the contact database 12 are registered in this contact database 12. user whatever their connections, and for each terminal of a contact 2, a transmission mode is associated with it: by default, the first transmission mode MT1 and, when the terminal of contact 2 is not connected to the first network 3 1 , the second mode of transmission MT2.
  • the controller 12 when the terminal of user 1 is in a second transmission mode for a terminal of a contact 2, that is to say when the transmission mode associated with the terminal of contact 2 is the second mode transmission MT2 in the contact database 12, on receipt of a tc_cnx1_ntf notification of connection to the first network of the contact terminal, the controller 12 commands cmd the modification of the transmission mode associated with the terminal of contact 2 in the contact database data 12, switching the terminal of user 1 into the first transmission mode for the terminal of contact 2.
  • the switch 111 consulting, for the terminal of contact 2 to which an mssg message is intended, the contact database 12 and reads there that the transmission mode associated with the terminal of contact 2 is the first mode of transmission, and remains in the default transmission mode: the first mode of transmission MT1 for the transmission of the message to the terminal of the contact 2.
  • the message communication device 11 comprises a message transmitter on a first network 10 1 and a message transmitter on a second network 10 2 .
  • controller 12 is either implemented directly in the terminal of the user 1 or in the message communication device 11 as described above.
  • the message communication device 11 comprises a switch 111 making it possible to provide a message to a first transmitter 10 1 , that is to say a transmitter on a first network, or a second transmitter 10 2 , that is that is to say a transmitter on a second network, depending on the transmission mode of the switch 111, respectively the first transmission mode MT1 or the second transmission mode MT2.
  • the controller 12 then commands cmd , upon receipt of a tc_cnx1_ntf notification of connection to the first network of the contact's terminal, the switching of the switch 111 into a first transmission mode MT1 when sending a message to the terminal of the contact. contact 2.
  • the terminal of user 1 or the message communication device 11 of the terminal of user 1 includes a contact database 12 (not illustrated) as described previously.
  • the terminal of user 1 comprises a message transmitter on a first network 10 1 and a message transmitter on a second network 10 2 either implemented directly in the terminal of user 1 or in the communication device 11 of user 1's terminal.
  • the messaging server 4 of a first network 3 1 comprises a transmitter 400 1 making it possible to transmit, when a terminal of a user 1 is in a second transmission mode MT2 for a terminal of a contact 2, to the terminal of user 1 a notification of connection to the first network of the contact terminal 8.tc_cnx1_ntf, the connection notification 8.tc_cnx1_ntf triggering 9.cmd a switch of the terminal of user 1 into a first mode of transmission MT1 for the terminal of contact 2.
  • the messaging server 4 includes a detector 430 of connection to the first network of a terminal of a contact triggering a transmission by the transmitter 400 1 of the connection notification 8. tc_cnx1_ntf.
  • the detector 430 for connection to the first network of the terminal of contact TC_CNX1_DTCT comprises a detector 4301 (not illustrated) of a message 4.mssg coming from the terminal of contact 2 via the first network 3 1 .
  • the detector 430 for connection to the first network of the contact terminal comprises a detector 4302 (not illustrated) of a reception by the messaging server 4 of a command message for deletion of a message stored on the messaging server. messaging 4'.revoke_mssg, the command message 4'.revoke_mssg coming from the TC contact terminal.
  • the messaging server 4 includes a generator 42 of a notification of connection to the first network of a terminal of a contact 5.tc_cnx1_ntf of a terminal of a user 1.
  • the generator 42 is implemented when 'a terminal of a user 1 is in a second transmission mode MT2 for a terminal of a contact 2.
  • the generator 42 of the connection notification provides the generated connection notification 5.tc_cnx1_ntf to the transmitter 400 1 to be transmitted to the user's terminal TU.
  • the messaging server 4 includes a provider 401 of the connection notification to the transmitter on the first network 400 1 activated according to a state of connection to the first network of the terminal of the user 1.
  • the transmitter at the user's terminal 40 includes the transmitter on the first network 400 1 and a provider 401 of the connection notification to the transmitter on the first network 400 1 activated according to a state of connection to the first network of the user's terminal 1.
  • the transmitter of the notification to the user's terminal 40 (not illustrated) is activated in function of a connection state to the first network of the terminal of user 1.
  • the transmitter on the first network 400 1 transmits the notification tc_cnx1_ntf when the terminal of user 1 is in a second transmission mode MT2 for the terminal of contact 2.
  • the messaging server 4 receives information from the terminal of user 1, such as a revocation message 1.revoke (mssg TC ), indicating the switch of the terminal of user TU into the second transmission mode MT2 for the contact terminal TC.
  • the messaging server 4 determines whether the terminal of user 1 is in a second transmission mode MT2 for the terminal of contact 2.
  • the messaging server 4 includes a detector 41 of the switching of the terminal of the user in the second transmission mode.
  • the detector 41 for switching to the second transmission mode includes a detector for revocation or deletion messages from the stored messages coming from the terminal of user 1.
  • the detector 41 determining a switch to the second transmission mode MT2 of a terminal of a user 1 for a terminal of a contact 2: reception of switchover information, detection of the switchover triggers 2.trg(MT2 TC ) a monitor of the first network 43 (not illustrated) triggering a transmission by the transmitter on the first network 400 1 of a notification of connection to the first network of the contact terminal 8.tc_cnx1_ntf.
  • This monitor of the first network 43 comprises at least one detector 430 for connection of the contact terminal to the first network.
  • the detector 41 of the switchover in the second transmission mode MT2 of a terminal of a user 1 for a terminal of a contact 2 reception of switchover information, detection of the switchover triggers 2.trg(MT2 TC ) the connection notification generator 42, which triggers 3b.dtdt_trg, itself, the connection detector 430 of the contact terminal to the first network.
  • the detector 430 connecting the contact terminal to the first network which triggers 7.snd_trg directly or indirectly the transmission by the transmitter on the first network 400, to the terminal of user 1 of the notification 8 .tc_cnx1_ntf provided by connection notification generator 42.
  • the detector 41 determining a switchover in the second transmission mode MT2 of a terminal of a user 1 for a terminal of a contact 2 reception of switchover information, detection of the switchover triggers 2.trg (MT2 TC ) the detector 430 for connecting the contact terminal to the first network, which triggers 3a. ntf_trg, itself, the connection notification generator 42.
  • the connection notification generator 42 which provides the connection notification 5.tc_cnx1_ntf and triggers 7.snd_trg directly or indirectly the transmission by the transmitter on the first network 400, to the terminal of user 1 of notification 8.tc_cnx1_ntf.
  • the transmitter at the user's terminal 40 includes the transmitter on the first network 400, of the tc_cnx1_ntf connection notification at the terminal of the user 1.
  • the transmitter at the user's terminal 40 also includes a connection analyzer 401 checking the connection of the user's terminal to the first network.
  • the analyzer 401 triggers the transmission by the transmitter on the first network 400 1 to the terminal of the user 1 of the connection notification tc_cnx1_ntf provided by the connection notification generator 42, in particular by providing the transmitter on the first network 400 1 with the connection notification 8.tc_cnx1_ntf. If the connection of the user's terminal to the first network is not verified, that is to say if the terminal of user 1 is not connected to the first network 3 1 , then the analyzer 401 triggers a connection detector of the user's terminal to the first network.
  • either the transmitter at the user's terminal 40, or the monitor of the first network 43 includes the detector 430 for connecting the user's terminal to the first network.
  • the detector 430 of connection of the user's terminal to the first network triggers 7.snd_trg the supply by the analyzer 401 to the transmitter on the first network 400 1 of the connection notification 8.tc_cnx1_ntf provided by the notification generator 42 connection, which then transmits it to the user's terminal 1.
  • the monitor 43 of the first network also includes the analyzer 401 and the detector 430 for connection of the user's terminal to the first network.
  • the same detector 430 is used by the messaging server to detect the connection to the first network 3 1 of the terminal of user 1 and the terminal of contact 2. This is particularly possible when the terminal of user 1 and the terminal of the contact 2 share the same messaging server 4.
  • the messaging server 4 may include separate connection detectors to the first network for the user's terminal and the contact's terminal (not illustrated).
  • the messaging server 4 can include two separate first network connection detectors.
  • connection detector of the user's terminal can include a simple monitor of the registration messages of the user's terminal received by the messaging server, while the connection detector of the contact's terminal will include a detector of all messages coming from the contact's terminal received by the messaging server 4 of the user's terminal: message useful to a terminal of an interlocutor (not illustrated) sharing the messaging server with the user's terminal 4, revocation message of a message stored on the mail server 4, etc.
  • FIG 5 illustrates a message exchange diagram in the case where the user's terminal is disconnected from the first network when a contact's terminal reconnects to the first network, according to the invention.
  • the terminal of the user TU sends to the terminal of a contact TC a first message mssg1 on a default network: the first network, snd1 (mssg1).
  • the terminal of the contact TC not being connected to the first network: TC ⁇ cnx 1
  • the messaging server of the terminal of the contact SM C receives the first message mssg1 and stores it in particular in a temporary memory or a BDD_MSSG message database with a view to transferring it to the contact's terminal when it is again connected to the first network.
  • the user's terminal TU then triggers a countdown of a predetermined period of time at the end of which, if the first message mssg1 has not been transmitted by the messaging server SM C to the terminal of the contact TC, the terminal of the user TU sends a revocation of the transfer of the first message to the mail server SM C: Revoke(mssg1).
  • the first message mssg1 is deleted from the BDD_MSSG memory of the SM C messaging server.
  • the terminal of the user TU not being connected to the first network: TU ⁇ cnx 1 the messaging server of the terminal of the user SM U receives the third message mssg3 and stores it in particular in a temporary memory or a database.
  • BDD_MSSG message data with a view to transferring it to the user's terminal TU when it is again connected to the first network.
  • the terminal of the contact TC then triggers a countdown of a predetermined period of time at the end of which, if the third message mssg3 has not been transmitted by the messaging server SM U to the terminal of the user TU, the terminal of the TC contact sends a revocation of the transfer of the third message to the SM U messaging server: Revoke(mssg3).
  • the third message mssg3 is deleted from the BDD_MSSG memory of the SM U messaging server.
  • send2(mssg3) the third message via the second network (this time): send2(mssg3) , in this case in SMS form.
  • the terminal of the user TU regains its coverage by the first network, that is to say if it is again connected to the first network, then the terminal TU sends, for example, a registration message on the first reg network to the SM U mail server.
  • the message management method according to the invention transmits SND to the user's terminal TU a tc_cnx1_nft notification indicating that the contact's terminal has regained its connection.
  • the message management method according to the invention illustrated by the figure 5 comprises detection of the connection of the contact terminal to the first network, in particular by detection either of a mssg3 message from the contact terminal TC to the user terminal TU via the first network N1, or of the revoke revocation message (mssg3) of this mssg3 message, and, following this detection, an SND transmission of a tc_cnx1_nft notification of connection to the first network of the contact's terminal conditioned by a detection of connection to the first network of the user's terminal, in this case by receiving a reg registration message.
  • the TU user's terminal will then activate a return to the first mode of transmission, in the case of the RCS standard a return to "Chat", that is to say instant messaging over IP, and will transmit a fourth message using the first network: send1(mssg4) since the two terminals: the user terminal TU and the contact terminal TC are connected to the first network. Then, the terminal of the contact TC (which had itself switched to a second transmission mode MT2 for the terminal of the user TU) receiving this fourth message mssg 4 from the terminal of the user TU on the first network will switch, as provided for by the RCS standard, in the first transmission mode to continue the conversation on the first network by transmitting a fifth message snd1 (mssg5).
  • the messaging server SM U of the user's terminal of the state of connectivity on the first network of the contact's terminal TC and the user's terminal TU which results in the delivery of the the tc_cnx1_ntf connection notification to the TU user's terminal.
  • it is respectively the detection of a message from the contact's terminal to the user's terminal or the reception of the revocation message, that is to say the reception of the deletion command.
  • FIG. 6 illustrates a message exchange diagram in the case where the messaging server of the user's terminal detects a message on the first network of a contact's terminal, according to the invention.
  • the terminal of the user TU sends to the terminal of a contact TC a first message mssg1 on a default network: the first network, snd1 (mssg1).
  • the terminal of the contact TC not being connected to the first network: TC ⁇ cnx 1
  • the messaging server of the terminal of the contact SM C receives the first message mssg1 and stores it in particular in a temporary memory or a message database BDD_MSSG with a view to transferring it to the contact's terminal when it is again connected to the first network.
  • the user's terminal TU then triggers a countdown of a predetermined period of time at the end of which, if the first message mssg1 has not been transmitted by the messaging server SM C to the terminal of the contact TC, the terminal of the user TU sends a revocation of the transfer of the first message to the mail server SM C: Revoke(mssg1).
  • the first message mssg1 is deleted from the BDD_MSSG memory of the SM C messaging server.
  • send2(mssg1) in this case in SMS form.
  • the terminal of the TC contact finds the connection to the first network: TC ⁇ cnx 1 , it can send snd1(mssg3) on the first network a third message to a terminal of a TCC interlocutor different from the terminal of the user TU. If the terminal of the interlocutor TCC and the terminal of the user TU share the same messaging server SM U , then the messaging server can detect the connection to the first network of the terminal of the contact TC from this third message mssg3 and not wait for the reception by the terminal of the user TU of a message from the terminal of the contact TC via the first network as illustrated by the figure1b .
  • the messaging server SM U detecting the connection to the first network of the terminal of the contact TC, sends SND a tc_cnx1_ntf notification to the terminal of the user TU.
  • the user's terminal TU then switches to the default transmission mode, that is to say transmission on the first network, and can, from now on, send snd1(mssg4) a fourth message to the contact's terminal on the first network.
  • the Figure 6 shows that the connection notification allows you to return to the default network as soon as possible for message exchanges.
  • the invention also relates to a support.
  • the information carrier can be any entity or device capable of storing the program.
  • the medium may comprise a storage means, such as a ROM, for example a CD ROM or a microelectronic circuit ROM or even a magnetic recording means, for example a floppy disk or a hard disk.
  • the information carrier may be a transmissible medium such as an electrical or optical signal which may be conveyed via an electrical or optical cable, by radio or by other means.
  • the program according to the invention can in particular be downloaded onto a network, particularly of the Internet type.
  • the information carrier may be an integrated circuit in which the program is incorporated, the circuit being adapted to execute or to be used in executing the method in question.
  • module can correspond to either a software component or a hardware component.
  • a software component corresponds to one or more computer programs, one or more subprograms of a program, or more generally to any element of a program or software capable of implementing a function or a function set as described below.
  • a hardware component corresponds to any element of a hardware assembly capable of implementing a function or a set of functions.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephonic Communication Services (AREA)
  • Information Transfer Between Computers (AREA)

Claims (15)

  1. Verfahren zum Austausch von Nachrichten, das durch ein Endgerät eines Benutzers (TU, 1) umgesetzt wird, das dazu fähig ist, eine Nachricht (mssg, mssg1, mssg2, mssg4) über ein Netz von: einem ersten Netz (N1, 31) und einem zweiten Netz (N2, 32) zu übertragen, wobei das Nachrichtenaustauschverfahren, wenn sich das Endgerät des Benutzers (TU, 1) in einem zweiten Übertragungsmodus (MT2), der das zweite Netz verwendet, für ein Endgerät eines Kontakts (TC, 2) befindet, ein Auslösen einer Umschaltung (SWT_TRG) des Endgeräts des Benutzers (TU, 1) in einen ersten Übertragungsmodus (MT1), der das erste Netz verwendet, für das Endgerät des Kontakts (TC, 2) umfasst, sobald an dem Endgerät des Benutzers (TU, 1) eine Benachrichtigung (tc_cnx1_ntf) über eine Verbindung des Endgeräts des Kontakts zu dem ersten Netz empfangen wird, die von einem Nachrichtenserver in dem ersten Netz (SMU, 4) kommt, wobei das Endgerät des Benutzers die Verbindungsnachricht von dem Nachrichtenserver empfängt, sobald der Nachrichtenserver eine Nachricht von dem Endgerät des Kontakts über das erste Netz empfangen hat.
  2. Nachrichtenaustauschverfahren (PEM) nach dem vorhergehenden Anspruch, dadurch gekennzeichnet, dass das Auslösen der Umschaltung (SWT_TRG) im Anschluss an eine Erkennung (TC_CNX1_DTCT), durch den Nachrichtenserver (SMU, 4), einer Verbindung des Endgeräts des Kontakts zu dem ersten Netz erfolgt.
  3. Nachrichtenaustauschverfahren nach einem beliebigen der vorhergehenden Ansprüche, dadurch gekennzeichnet, dass das erste Netz ein Datennetz ist und das zweite Netz ein verbindungsorientiertes Netz ist.
  4. Vorrichtung zur Kommunikation von Nachrichten (11) eines Endgeräts eines Benutzers (TU, 1), wobei die Kommunikationsvorrichtung (11) dazu fähig ist, eine Nachricht (mssg, mssg1, mssg2, mssg4) über ein Netz von: einem ersten Netz (N1, 31) und einem zweiten Netz (N2, 32) zu übertragen, wobei die Kommunikationsvorrichtung (11) eine Steuereinheit (12) umfasst, die dazu fähig ist, bei Empfang einer Benachrichtigung (tc_cnx1_ntf), an dem Endgerät des Benutzers (TU, 1), über eine Verbindung eines Endgeräts eines Kontakts zu dem ersten Netz, die von einem Nachrichtenserver in dem ersten Netz (SMU, 4) kommt, eine Umschaltung des Endgeräts des Benutzers (TU, 1) in einen ersten Übertragungsmodus (MT1), der das erste Netz verwendet, für das Endgerät des Kontakts (TC, 2) auszulösen (cmd), wenn sich das Endgerät des Benutzers (TU, 1) in einem zweiten Übertragungsmodus (MT2), der das zweite Netz verwendet, für das Endgerät des Kontakts (TC, 2) befindet, wobei das Endgerät des Benutzers die Verbindungsbenachrichtigung von dem Nachrichtenserver empfängt, sobald der Nachrichtenserver eine Nachricht von dem Endgerät des Kontakts über das erste Netz empfangen hat.
  5. Endgerät eines Benutzers (TU, 1), das eine Vorrichtung zur Kommunikation von Nachrichten (11) umfasst, die dazu fähig ist, eine Nachricht (mssg, mssg1, mssg2, mssg4) über ein Netz von: einem ersten Netz (N1, 31) und einem zweiten Netz (N2, 32) zu übertragen, wobei das Endgerät des Benutzers (TU, 1) eine Steuereinheit (12) umfasst, die dazu fähig ist, bei Empfang einer Benachrichtigung (tc_cnx1_ntf), an dem Endgerät des Benutzers (TU, 1), über eine Verbindung eines Endgeräts eines Kontakts zu dem ersten Netz, die von einem Nachrichtenserver in dem ersten Netz (SMU, 4) kommt, eine Umschaltung des Endgeräts des Benutzers (TU, 1) in einen ersten Übertragungsmodus (MT1), der das erste Netz verwendet, für das Endgerät des Kontakts (TC, 2) auszulösen (cmd), wenn sich das Endgerät des Benutzers (TU, 1) in einem zweiten Übertragungsmodus (MT2), der das zweite Netz verwendet, für das Endgerät des Kontakts (TC, 2) befindet, wobei das Endgerät des Benutzers die Verbindungsbenachrichtigung von dem Nachrichtenserver empfängt, sobald der Nachrichtenserver eine Nachricht von dem Endgerät des Kontakts über das erste Netz empfangen hat.
  6. Verfahren zur Verwaltung von Nachrichten, das durch einen Nachrichtenserver in einem ersten Netz (SMU, 4) umgesetzt wird, wobei das Nachrichtenverwaltungsverfahren (PGM), wenn sich ein Endgerät eines Benutzers (TU, 1) in einem zweiten Übertragungsmodus (MT2), der ein zweites Netz verwendet, für ein Endgerät eines Kontakts (TC, 2) befindet, ein Senden (SND), an das Endgerät des Benutzers (TU, 1), einer Benachrichtigung über eine Verbindung des Endgeräts des Kontakts zu dem ersten Netz (tc_cnx1_ntf) umfasst, sobald eine Nachricht von dem Endgerät des Kontakts über das erste Netz empfangen wurde, wobei die Verbindungsbenachrichtigung (tc_cnx1_ntf) eine Umschaltung (SWT_TRG) des Endgeräts des Benutzers (TU, 1) in einen ersten Übertragungsmodus (MT1), der das erste Netz verwendet, für das Endgerät des Kontakts (TC, 2) auslöst.
  7. Nachrichtenverwaltungsverfahren nach dem vorhergehenden Anspruch, dadurch gekennzeichnet, dass das Nachrichtenverwaltungsverfahren (PGM), wenn sich ein Endgerät eines Benutzers (TU, 1) in einem zweiten Übertragungsmodus (MT2) für das Endgerät des Kontakts (TC, 2) befindet, eine Erkennung einer Verbindung des Endgeräts des Kontakts zu dem ersten Netz (TC_CNX1_DTCT) umfasst, an deren Anschluss das Senden der Verbindungsbenachrichtigung (SND) erfolgt.
  8. Nachrichtenverwaltungsverfahren (PGM) nach dem vorhergehenden Anspruch, dadurch gekennzeichnet, dass die Erkennung einer Verbindung des Endgeräts des Kontakts zu dem ersten Netz (TC_CNX1_DTCT) eine Erkennung einer Nachricht (mssg), die über das erste Netz (N1, 31) von dem Endgerät des Kontakts (TC, 2) kommt, umfasst.
  9. Nachrichtenverwaltungsverfahren (PGM) nach einem beliebigen der Ansprüche 7 oder 8, dadurch gekennzeichnet, dass die Erkennung einer Verbindung des Endgeräts des Kontakts zu dem ersten Netz (TC_CNX1_DTCT) eine Erkennung eines Empfangs, durch den Nachrichtenserver, einer Befehlsnachricht zum Löschen einer auf dem Nachrichtenserver gespeicherten Nachricht (revoke_mssg) umfasst, wobei die Befehlsnachricht (revoke_mssg) von dem Endgerät des Kontakts (TC, 2) kommt.
  10. Nachrichtenverwaltungsverfahren (PGM) nach einem beliebigen der Ansprüche 6 bis 9, dadurch gekennzeichnet, dass das Nachrichtenverwaltungsverfahren (PGM), wenn sich das Endgerät des Benutzers (TU, 1) in einem zweiten Übertragungsmodus (MT2) für das Endgerät des Kontakts (TC, 2) befindet, eine Erzeugung einer Benachrichtigung über eine Verbindung des Endgeräts des Kontakts zu dem ersten Netz für das Endgerät des Benutzers (NTFTU_GN) umfasst, wobei die Erzeugung der Verbindungsbenachrichtigung (NTFTU_GN) die erzeugte Verbindungsbenachrichtigung (tc_cnx1_ntf) beim Senden (SND) an das Endgerät des Benutzers (TU, 1) bereitstellt.
  11. Nachrichtenverwaltungsverfahren (PGM) nach dem vorhergehenden Anspruch, dadurch gekennzeichnet, dass die Erzeugung einer Verbindungsbenachrichtigung (NTFTU_GN) durch eines von folgenden Ereignissen in Zusammenhang mit einer Verbindung des Endgeräts des Kontakts zu dem ersten Netz ausgelöst (gr_trg) wird:
    • der Erkennung einer Verbindung des Endgeräts des Kontakts zu dem ersten Netz (TC_CNX1_DTCT);
    • einer Umschaltung (TU_MT2_DTCT) des Endgeräts des Benutzers (TU, 1) in einen zweiten Übertragungsmodus (MT2) für das Endgerät des Kontakts (TC, 2).
  12. Nachrichtenverwaltungsverfahren (PGM) nach einem beliebigen der Ansprüche 10 oder 11, dadurch gekennzeichnet, dass eine Umsetzung des Sendens der Benachrichtigung (SND) von einem Verbindungszustand des Endgeräts des Benutzers zu dem ersten Netz (TU_CNX1 ?) abhängt.
  13. Programm, das Programmcodeanweisungen für die Ausführung der Schritte des Nachrichtenaustauschverfahrens nach einem beliebigen der Ansprüche 1 bis 3 und/oder des Nachrichtenverwaltungsverfahrens nach einem beliebigen der Ansprüche 6 bis 12 beinhaltet, wenn das Programm von einem Prozessor ausgeführt wird.
  14. Nachrichtenserver (4) eines ersten Netzes (31), der einen Sender (4001) umfasst, der, wenn sich ein Endgerät eines Benutzers (1) in einem zweiten Übertragungsmodus (MT2), der ein zweites Netz verwendet, für ein Endgerät eines Kontakts (2) befindet, das Senden, an das Endgerät des Benutzers (1), einer Benachrichtigung über eine Verbindung des Endgeräts des Kontakts zu dem ersten Netz (tc_cnx1_ntf) gestattet, sobald eine Nachricht von dem Endgerät des Kontakts über das erste Netz empfangen wurde, wobei die Verbindungsbenachrichtigung (tc_cnx1_ntf) eine Umschaltung des Endgeräts des Benutzers (1) in einen ersten Übertragungsmodus (MT1), der das erste Netz verwendet, für das Endgerät des Kontakts (2) auslöst (cmd).
  15. Nachrichtenserver (4) eines ersten Netzes (31) nach dem vorhergehenden Anspruch, dadurch gekennzeichnet, dass der Nachrichtenserver (4) eine Einheit zur Erkennung (430) einer Verbindung eines Endgeräts eines Kontakt zu dem ersten Netz umfasst, die dazu fähig ist, ein Senden der Verbindungsbenachrichtigung (tc_cnx1_ntf) durch den Sender (4001) auszulösen.
EP17784361.2A 2016-09-23 2017-09-21 Verfahren zum austausch von nachrichten und zur verwaltung von nachrichten, endgerät und nachrichtenserver Active EP3516851B1 (de)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
FR1658948A FR3056873A1 (fr) 2016-09-23 2016-09-23 Procedes d'echange de messages et de gestion de messages, terminal et serveur de messagerie
PCT/FR2017/052534 WO2018055293A1 (fr) 2016-09-23 2017-09-21 Procédés d'échange de messages et de gestion de messages, terminal et serveur de messagerie

Related Child Applications (1)

Application Number Title Priority Date Filing Date
EP24168651.8 Division-Into 2024-04-05

Publications (2)

Publication Number Publication Date
EP3516851A1 EP3516851A1 (de) 2019-07-31
EP3516851B1 true EP3516851B1 (de) 2024-05-29

Family

ID=58347444

Family Applications (1)

Application Number Title Priority Date Filing Date
EP17784361.2A Active EP3516851B1 (de) 2016-09-23 2017-09-21 Verfahren zum austausch von nachrichten und zur verwaltung von nachrichten, endgerät und nachrichtenserver

Country Status (4)

Country Link
US (1) US11770743B2 (de)
EP (1) EP3516851B1 (de)
FR (1) FR3056873A1 (de)
WO (1) WO2018055293A1 (de)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112187629B (zh) * 2020-10-20 2022-04-29 珠海市小源科技有限公司 5g通信的消息撤回方法、计算机装置及计算机可读存储介质

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100217809A1 (en) * 2009-02-26 2010-08-26 Research In Motion Limited System and method for switching between messaging clients
US9641609B2 (en) * 2012-02-28 2017-05-02 Google Inc. Integrated messaging
US20160275301A1 (en) * 2015-03-17 2016-09-22 Dots Communication, Inc. Information sharing control
US10432561B2 (en) * 2016-08-19 2019-10-01 International Business Machines Corporation Proximity-based communication

Also Published As

Publication number Publication date
EP3516851A1 (de) 2019-07-31
WO2018055293A1 (fr) 2018-03-29
US11770743B2 (en) 2023-09-26
FR3056873A1 (fr) 2018-03-30
US20190261228A1 (en) 2019-08-22

Similar Documents

Publication Publication Date Title
EP3437263B1 (de) Verfahren zur benachrichtigung der unverfügbarkeit eines endgeräts
EP1715642A2 (de) Verfahren und System zum automatischen Aktivieren oder Deaktivieren eines Services
CN100421431C (zh) 一种实现即时消息通信的方法
US10812421B2 (en) Conveying instant messages via HTTP
EP2939450B1 (de) Übertragung einer multimedia-nachricht in kombination mit der übertragung einer textnachricht
EP3119060A1 (de) Verfahren und vorrichtung zur erstellung von webrtc-kommunikationen
EP2210396B1 (de) System zur herstellung einer verbindung zwischen mindestens einer kommunikationsvorrichtung und mindestens einem ferninformationssystem sowie verbindungsverfahren
EP3516851B1 (de) Verfahren zum austausch von nachrichten und zur verwaltung von nachrichten, endgerät und nachrichtenserver
EP3053309B1 (de) Verbesserte verwaltung von netzwerkverbindungen
CA2804562A1 (fr) Procede d'etablissement d'une communication sur internet entre terminaux mobiles, programme d'ordinateur et support d'enregistrement
WO2016062947A1 (fr) Methode de filtrage de messages pour fournir une fonction de type"ne pas deranger"
FR3086478A1 (fr) Gestion du fonctionnement d'une telecommande lors de la reception d'un appel telephonique.
EP3840312B1 (de) Datenübertragung zu speichergeräten
EP2273774B1 (de) Verbindungswunschbenachrichtigungsverfahren
FR2964815A1 (fr) Gestion de l'acces au statut d'une ressource
WO2007077349A2 (fr) Procede, appareils et programme d'ordinateur de gestion de flux entre equipements fonctionnant selon le protocole sip sur un reseau de telecommunications
EP2856302A2 (de) Lokaler server für eine anzeigevorrichtung
FR3110800A1 (fr) Procédé de notification d’un terminal mobile
WO2011023904A1 (fr) Procede de diffusion d'un contenu dans un reseau de telecommunications de maniere geolocalisee
WO2021260328A1 (fr) Procede de mise a jour d'un etat de presence d'un utilisateur d'un terminal de communication pour un ensemble d'applications de communication
FR3006137A1 (fr) Mecanisme de gestion d'une session de communication
FR3020539A1 (fr) Procede et dispositif d'etablissement d'une communication
FR2953671A1 (fr) Procede de telechargement automatique de messages, et premier terminal le mettant en oeuvre
FR2988945A1 (fr) Procede et dispositif de transfert de fichier
WO2007099267A1 (fr) Procede de redirection d'un appel et terminal mobile adapte a mettre en oeuvre un tel procede

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: UNKNOWN

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20190423

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20200120

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: ORANGE

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

RAP3 Party data changed (applicant data changed or rights of an application transferred)

Owner name: ORANGE

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602017082300

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: H04L0029080000

Ipc: H04W0004120000

Ref country code: DE

Ref legal event code: R079

Free format text: PREVIOUS MAIN CLASS: H04L0029080000

Ipc: H04W0004120000

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

RIC1 Information provided on ipc code assigned before grant

Ipc: H04L 51/58 20220101ALI20231127BHEP

Ipc: H04L 51/043 20220101ALI20231127BHEP

Ipc: H04L 51/10 20220101ALI20231127BHEP

Ipc: H04L 67/54 20220101ALI20231127BHEP

Ipc: H04W 4/14 20090101ALI20231127BHEP

Ipc: H04W 4/12 20090101AFI20231127BHEP

INTG Intention to grant announced

Effective date: 20231222

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602017082300

Country of ref document: DE