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
  • 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
  • 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
  • H04W56/00—Synchronisation arrangements
  • H04W56/001—Synchronization between nodes

Definitions

• the present invention relates to the transmission of messages in a multi-terminal context, and in particular to the transmission of SMS type messages in such a context.
• the SMS messaging system (for "Short Message Service” in English) was developed years ago, to allow the sending of short text messages between mobile terminals, by means of signaling messages used in the networks of second generation mobile communications at the time. This system was standardized through the 3GPP TS 23.240 and TS 23.040 standards and has met with immense success to the point that it is still widely used today.
• SMS messaging system as standardized was designed from its outset for cases of message transmission from a single sending mobile terminal to a single receiving mobile terminal.
• This common identifier can be the phone number natively linked to one of the system's terminals.
• This common identifier can also be a number not natively linked to one of the terminals of the system, such a number then being able to be called an “extra-number”, or even a “virtual number” (“Virtual number”). number ”in English), which is typically a new number assigned by the operator, not linked to a SIM card or to a particular terminal.
• This common identifier can be used by a user, with any of the terminals of the system, to call or receive a telephone call either from one of these terminals by means of this identifier.
• each terminal of the multi-terminal system -terminaux behaves completely independently of the other terminals of this system, without taking into account the existence of other terminals which are nevertheless associated with it within the multi-terminal system.
• Patent application EP 1 613 102 A1 describes a system for controlling the delivery of short messages, in which it is possible to program so flexible, by means of instructions stored in a database of a network entity, the redirection, copy or distribution of short messages sent by a source terminal which would be received by this network entity.
• the distribution of short messages to a plurality of recipient terminals is based on the use of distinct MSISDN identifiers for each recipient terminal, in order to be able to address the short message to be distributed to each of these terminals.
• recipients using a conventional messaging network architecture proves to be incompatible with the sending of messages to a “multi-terminal” system as described above, since the terminals of such a “multi-terminal” system share the same common identifier while the control of this patent application EP 1 613 102 A1 requires separate identifiers for each terminal to which to distribute a short message.
• the patent application FR 3 053 560 A1 for its part describes a message redirection system resulting from the modification of a conventional SMS messaging system, in which a database is added making it possible to redirect a message intended for a first phone line to a separate second phone line and, if this redirection fails, then redirect this message to the first phone line.
• the present invention therefore overcomes these drawbacks.
• destination terminal comprising the following steps, following receipt of the message by a routing gateway: transmission from the routing gateway to a synchronization server, of the message by means of a first signaling and recovery protocol, by said at least one terminal Associated B, of the message intended for the recipient terminal with the synchronization server by means of a first synchronization message.
• the method further comprises the determination, by the routing gateway, of the membership of the destination terminal to a multi-terminal system comprising the destination terminal and said at least one associated terminal, the step recovery taking place only in the event of a positive result of said determination.
• the method further comprises transmitting, from the routing gateway to the destination terminal, the message by means of a second signaling protocol.
• the transmission, from the routing gateway to the destination terminal, of the message by means of a second signaling protocol is carried out only if it is determined, during the determination step, that the destination terminal does not belong to a multi-terminal system.
• the method further comprises the storage, by the synchronization server, of the message following its reception from the routing gateway.
• the message intended for the destination terminal is a message in SMS format.
• the first and / or the second synchronization message is a message conforming to a protocol among the IMAP, JMAP, OMA DS or OMA NMS protocols.
• the first and / or the second signaling protocol is a protocol among the SIP, MAP and NAS protocols.
• a routing gateway comprising a communication module capable of receiving a message intended for a first terminal, said recipient terminal, according to a first signaling protocol and a processing module, configured to insert the message in a signaling message to be transmitted to a synchronization server in order to allow at least one second terminal, said associated terminal, sharing an identifier with the destination terminal, to retrieve said message from said synchronization server.
• this processing module is further configured to instruct the communication module to transmit said message to the destination terminal by means of a signaling message according to a second signaling protocol.
• this processing module is further configured to inhibit the transmission of said message by the communication module to the destination terminal.
• a synchronization server comprising a communication module capable of receiving a signaling message according to a first signaling protocol, this signaling message containing a message intended for a first terminal, called the destination terminal, and a processing module configured for inserting the message received in at least a first synchronization message to be transmitted, by the communication module, to at least one second terminal, said associated terminal, sharing an identifier with said recipient terminal.
• the processing module is further configured to insert the message in a second synchronization message to be transmitted, by the communication module, to said destination terminal.
• a terminal capable of sharing the same identifier with another terminal, called a recipient terminal, comprising a processing module, a communication module configured to receive messages intended for said terminal, and a storage module configured to store said said terminal. messages intended for said terminal with a view to presenting it to a user.
• the communication module is further configured to receive, from a synchronization server, a synchronization message containing a message intended for the destination terminal, and the processing module is configured to extract, from the message synchronization received, the message intended for the destination terminal and to deliver said message to the storage module in order to store said message therein with a view to presenting it to a user with the messages intended for said terminal.
• a system is also proposed for the transmission of a message intended for a first terminal, said destination terminal, from a second terminal, said source terminal, to at least a third terminal, said associated terminal, sharing the same identifier with the terminal.
• recipient comprising a routing gateway and a synchronization server as presented above.
• this system further comprises at least one terminal as presented above.
• Figure 1 schematically shows the architecture provided for the transmission of SMS message, as currently standardized
• FIG. 2 shows an embodiment of the message transmission method according to the present invention
• FIG. 3 shows another embodiment of the message transmission method according to the present invention
• Figure 4 illustrates a routing gateway according to one embodiment of the present invention
• FIG. 5 illustrates a synchronization server according to an embodiment of the present invention.
• FIG. 6 illustrates a terminal according to an embodiment of the present invention.
• FIG. 1 schematically illustrates a currently conceivable architecture, based on existing 3GPP standards, to allow the transmission of SMS messages from a sending mobile terminal UE-A to a receiving mobile terminal UE- B.
• the mobile terminal UE-A transmits (step A1 10) this SMS message to a routing gateway belonging to the communication network B to which the destination terminal is attached, so that this gateway can address this message to this UE-B terminal as soon as the latter becomes reachable.
• a transmission typically breaks down into a first transmission of the SMS message according to a SIP (for “Session Initiation Protocol”) or NAS (“Non Access Stratum”) signaling protocol, from the UE-A terminal to a gateway.
• SIP Session Initiation Protocol
• NAS Non Access Stratum
• this gateway then retransmitting this SMS message according to a MAP signaling protocol (for "Mobile Application Part” in English) to a network node of the SMSC type, for "Short Message Service Center ”in English (substep A1 12), so that this SMSC network node memorizes (substep A1 13) this SMS message with a view to its subsequent retransmission to the network B to which the destination terminal is subscribed.
• a MAP signaling protocol for "Mobile Application Part” in English
• a network node of the SMSC type for "Short Message Service Center ”in English
• this SMSC network node transmits (substep A1 14) the SMS message to a B_SMS routing gateway of this network B, by means of the protocol MAP signaling (this B_SMS gateway being typically an IP-SM-GW gateway in the case of a 4G access network or an MSC node in the case of a 2G or 3G access network).
• this B_SMS gateway being typically an IP-SM-GW gateway in the case of a 4G access network or an MSC node in the case of a 2G or 3G access network).
• this routing gateway B_SMS of the network B has been configured beforehand to transmit any SMS message intended for the destination terminal UE-B to other terminals which are associated with it (here the two terminals UE-B 'and UE-B ”Purely by way of illustration), this routing gateway must then proceed with the duplication (step A120) of this SMS message in as many messages as there are associated terminals, in order to transmit (step A130) this SMS message to the destination terminal UE-B using a signaling protocol (here the SIP protocol by way of example), to transmit (step A130 ') this same SMS message to the first associated terminal UE-B' still using a signaling protocol and to transmit (step A130 ”) this same SMS message to the second associated terminal UE-B” still using a signaling protocol.
• a signaling protocol here the SIP protocol by way of example
• a first terminal 10 called source terminal hereafter, wishes to send a message to a second terminal 20, called destination terminal hereafter.
• the terminals 10 and 20 can in particular be mobile terminals, for example of the smartphone type.
• the message in question is illustrated here as being an SMS1 message, formatted according to the SMS format, without the invention being limited to this single message format, the latter being able to be applied to any type of message intended for use. transmitted, between terminals and, in particular between mobile terminals, only in the signaling plane.
• the destination terminal 20 is associated with at least one other terminal, called an associated terminal, in the context of a communication context called "multi-terminal context".
• an associated terminal in the context of a communication context called "multi-terminal context”.
• it may be a mobile terminal, for example of the smartphone type.
• the various associated terminals share the same identifier, also called a common identifier, which can in particular be the same telephone number (ie the same MSISDN identifier) serving as a unique identifier in a defined numbering plan, so that the other terminals called by (or recipients of a message coming from) one of the associated terminals see only one and the same identifier, independently of the associated terminal which is actually used.
• a common identifier can in particular be the same telephone number (ie the same MSISDN identifier) serving as a unique identifier in a defined numbering plan, so that the other terminals called by (or recipients of a message coming from) one of the associated terminals see only one and the same identifier, independently of the associated terminal which is actually used.
• FIG. 2 illustrates the case of a multi-terminal system with three associated terminals, in which two other “associated” terminals 20 'and 20 ”are associated with the destination terminal 20, and therefore share with it a same identifier “MSISDN 2 o” (in this case the identifier of the destination terminal 20), without the invention being limited to this single case, a number N (with N> 1) of terminals which can be associated with the terminal recipient 20 within such a system.
• MSISDN 2 o in this case the identifier of the destination terminal 20
• the associated terminals within a multi-terminal system can in particular be mobile terminals (smartphones, connected watches, tablets, among others), as well as other less mobile types of terminals, such as voice assistants, or connected refrigerators, that is to say any terminal connected to the network and capable of sending and receiving messages, possibly by displaying them or by vocalizing them.
• this embodiment involves a synchronization server 30, with which the associated terminals 20 ′ and 20 ′′ (or even also the destination terminal 20, as will be seen later) exchange synchronization messages, designated here by “SYNC”.
• client synchronization modules are installed, typically in software form, in the associated terminals 20 'and 20 ”(or also in the destination terminal 20 as will be seen below) while a synchronization server module, typically in software form, is installed in the synchronization server 30, these modules being synchronized so that the client modules are notified of changes in content of the server module of the synchronization server, or in real time as soon as such a change takes place, either in a deferred manner when one of the client modules interrogates the server module in order to know the changes which have taken place since the last connection of the client terminal to the server.
• Such SYNC synchronization messages conform to a synchronization protocol suitable for use between a client module and a server module, which can be the IMAP (for “Interactive Message Access Protocol”), JMAP (for the implementation) protocol. Java of the IMAP protocol) OMA DS (for “Data Synchronization” in English) or OMA NMS (for “Network Message Storage” in English), for example.
• the terminals 20 'and 20 ”(or also the terminal 20) synchronize with the synchronization server 30 by exchanging synchronization messages in accordance with a synchronization protocol such as one of the aforementioned protocols, mentioned above. as an example of a synchronization protocol.
• the terminals 20 ′ and 20 ′′ associated with the destination terminal 20 register with the synchronization server 30, in order to subsequently benefit from the synchronization service managed by this server.
• the synchronization server 30 has the information making it possible to establish the link between all the associated terminals, typically an identifier common to all these terminals such as an identifier MSISDN20 of the destination terminal 20, or even an additional number of the type “Extra-number”, ie a new number, supplied by the operator, not linked to a SIM card or to a particular terminal.
• step S1 1 When an SMS1 message (here a message in the SMS format) is to be transmitted from the source terminal 10 to the destination terminal 20, the terminal 10 transmits (step S1 1 1) this SMS1 message according to a signaling protocol (here illustrated as being the SIP protocol) to a first routing gateway 50 (here illustrated without limitation by a gateway of IP-SM-GW type) belonging to the network to which the terminal 10 is attached, which retransmits (step S1 12) this message SMS1 to the means of a signaling protocol (here illustrated by the MAP protocol) to a network node 40 (here illustrated by an SMSC node) which stores this message (step S1 13) before retransmitting it (step S1 14) to a second gateway routing 50 '(here illustrated without limitation by a gateway of the IP-SM-GW type) by means of a signaling protocol (illustrated here by the MAP protocol).
• a signaling protocol here illustrated as being the SIP protocol
• a first routing gateway 50 here illustrated without limitation
• Such a retransmission can be done immediately (upon receipt of the message) and, if it fails, can be retried periodically until it succeeds, or else be retried once the network node 40 has been alerted by the network B of the availability. of the destination terminal 20.
• the second routing gateway 50 transmits (step S1 15) this SMS message to the destination terminal 20, within the network B to which this terminal 20 is attached, according to a signaling protocol which can be the SIP protocol, or a combination of the MAP and NAS protocols (for “Non-Access Stratum”), for example.
• a signaling protocol which can be the SIP protocol, or a combination of the MAP and NAS protocols (for “Non-Access Stratum”), for example.
• the second routing gateway 50 ' can transmit (step S130) the SMS1 message to the synchronization server 30 according to a signaling protocol, for example the MAP protocol as illustrated without limitation in FIG. 2, or even the OMA NMS protocol, among other protocols suitable for transmission signaling messages between routing gateway and synchronization server.
• a signaling protocol for example the MAP protocol as illustrated without limitation in FIG. 2, or even the OMA NMS protocol, among other protocols suitable for transmission signaling messages between routing gateway and synchronization server.
• the second routing gateway 50 has been advantageously configured beforehand to know the network address of this synchronization server 30, in order to be able to send it a signaling message containing the message SMS1, as well as to determine s' it is necessary, or not, to trigger the transmission of the transmission of this message SMS1 to this synchronization server 30, typically as a function of an identifier retrieved in the signaling message received from the routing gateway 50 ′, in particular from the identifier of the destination terminal indicated in a field of the SMS1 message.
• the routing gateway 50 when it receives an SMS1 message from the network node 40, the routing gateway 50 'can then determine (step S120) whether this SMS1 message must also be transmitted to the synchronization server 30, in addition to being transmitted to the destination terminal 20.
• This determination step can be performed as a function of an identifier associated with the destination terminal of the SMS1 message received from the network node 40, typically the MSISDN of the destination terminal as indicated in this SMS1 message.
• the routing gateway 50 ' can check whether this identifier has been previously stored by the routing gateway 50' (or by querying a database, for example an HLR) as being the identifier of a terminal belonging to a multi-terminal system involving several terminals, that is to say to the identifier of a destination terminal for which messages should be transmitted to the synchronization server 30.
• the method stops at this stage and only the destination terminal 20 receives the message SMS1 (step S1 15) in the signaling plane, in the traditional manner.
• the routing gateway 50 'then proceeds to the transmission (step S130) of this message SMS1 to the synchronization server 30, by inserting this message SMS1 in a signaling message conforming to a signaling protocol suitable for exchanges of signaling between routing gateways and synchronization servers, here the MAP protocol (but could also be the OMA NMS protocol).
• a signaling protocol suitable for exchanges of signaling between routing gateways and synchronization servers
• this determination step S120 can take place either before or after the transmission step S1 15 to the destination terminal 120, insofar as this transmission S115, in the signaling plane, of the message SMS1 is systematically performed in this mode implementation, whether the destination terminal belongs to a multi-terminal system or not.
• the synchronization server 30 stores (step S140) this message SMS1, after having extracted it from the signaling message in which it was received, or even within a storage module of this server , or in a database associated with this server.
• the associated terminals 20 'and 20 ” can then retrieve the SMS1 message, intended for the destination terminal 20, from the synchronization server 30, by means of synchronization messages conforming to a synchronization protocol suitable for synchronization in mode.
• client-server such as IMAP, JMAP, OMA DS or OMA NMS, among others.
• the synchronization server 30 retrieves the message SMS1 intended for the destination terminal 20 and inserts it into a synchronization message SYNC ′ [SMS1] which 'it transmits to this terminal 20' (step S150 ').
• the server 30 does the same for all the other associated terminals, in this case for the terminal 20 "(step S150") to which it transmits a synchronization message SYNC "[SMS1] in which it has inserted the message SMS1.
• synchronization messages can be implemented in the form of a message containing an attribute in which the SMS1 message is inserted. It may in particular be a message of the “pager-messenger” type according to the REST NMS interface, containing an object of the so-called “inline” SMS type, in which the SMS1 message can be directly inserted in a “textContent” attribute , as shown in the example below:
• synchronization messages can also be implemented in the form of a message with a “payload” field containing an address allowing the subsequent downloading of the message SMS1 (by GET request for example).
• it may be a “pager-messenger” type message according to the NMS REST interface, as illustrated by the example below: ⁇ obj ect>
• synchronization messages can also be implemented in the form of a notification from the synchronization server, containing in its subject a URL making it possible to directly download an “SMS1 message” object, as illustrated by the example below, where the element "Oldl OOO" at the end of the URL represents a unique identifier for this message:
• the SYNC synchronization message '[SMS1] used to transmit the SMS1 message to the associated terminal 20' can be the same as the SYNC synchronization message ”[SMS1] used to transmit the SMS1 message to the associated terminal 20 ”, or even be a synchronization message of a different type but conforming to the same synchronization protocol, or else conforming to a different synchronization protocol. All these synchronization messages are transmitted in the data transport plane, and not in the signaling plane as would be the case if the message SMS1 were to be duplicated and transmitted to each associated terminal.
• Each associated terminal 20 'and 20 "can then, after having received respectively these synchronization messages SYNC' and SYNC", extract the message SMS1 intended for the destination terminal 20 and store it in their own respective memories, for subsequent consultation or reproduction by an user.
• all the terminals associated with the destination terminal 20 have the SMS1 message to be received by the destination terminal 20, as well as information associated with this message, such as the time of sending of the message, the where the message was sent, read status, reply indicator, etc.
• the user of a multi-terminal system therefore has access to the same message reception history, regardless of the terminal he is accessing.
• FIG. 3 illustrates a message transmission method according to another embodiment of the present invention.
• This other embodiment is relatively similar to that illustrated in FIG. 2, with the difference that after having received the message SMS1, the routing gateway 50 'of the network to which the destination terminal is subscribed does not necessarily transmit it directly. at the destination terminal, in the signaling plane, but can on the contrary leave it to the synchronization server to take care of it, in the data transport plane.
• the traditional step (illustrated by S1 15 in FIG. 2) of transmitting the message SMS1 to the destination terminal 20 according to a signaling protocol can be hereby inhibited, and therefore does not systematically take place.
• the routing gateway 50 determine (step S220) whether this message SMS1 must be transmitted to the synchronization server 30, this determination which can be carried out in a similar manner to step S120 described in relation to FIG. 2.
• a signaling protocol here illustrated by the SIP protocol, but which can also be the combination of MAP and NAS protocols for example
• step S225 is inhibited and does not take place
• this message SMS1 is inserted in a signaling message conforming to a signaling protocol suitable for signaling exchanges between routing gateways and synchronization server (here the MAP protocol by way of example) and transmitted (step S230) to the synchronization server 30.
• a signaling protocol suitable for signaling exchanges between routing gateways and synchronization server here the MAP protocol by way of example
• the routing gateway 50 ' can insert in this signaling message an indicator, interpretable by the server 30, indicating that the message SMS1 was not transmitted to the destination terminal 20 by the gateway 50 '.
• the synchronization server 30 extracts this message SMS1 and stores it (step S240), either within a storage module of this server, or in an associated database. to this server.
• the destination terminal 20 can then retrieve the message SMS1, intended for the destination terminal 20, from the synchronization server 30, by means of synchronization messages in accordance with a synchronization protocol adapted to client-server synchronization, such as IMAP, JMAP, OMA DS or OMA NMS, among others.
• a synchronization protocol adapted to client-server synchronization such as IMAP, JMAP, OMA DS or OMA NMS, among others.
• the synchronization server 30 retrieves the message SMS1 intended for the destination terminal 20 and inserts it in a second synchronization message SYNC' [SMS1 ] which it transmits to this terminal 20 '(step S250'). It does the same for all the other associated terminals, in this case for the terminal 20 "(step S250") to which it transmits a third synchronization message SYNC "[SMS1] in which it has inserted the message SMS1.
• the synchronization server 30 can be configured to systematically retrieve the message SMS1 intended for this destination terminal 20 and insert it in a first synchronization message SYNC [SMS1] which 'it transmits to this terminal 20 (step S250), without taking into account a possible direct transmission to the terminal 20 of this message SMS1 in the signaling plan.
• the method can comprise an optional step (step S245) of determination, by the synchronization server, in order to transmit a synchronization message SYNC [SMS1] to the destination terminal 20 only when it is not determined. has not already been transmitted, in the signaling plane, by the routing gateway 50 '.
• This determination can in particular be carried out by verifying the presence, in the signaling message received from the routing gateway 50 ′ during step S230, of an indicator indicating that the message SMS1 has not been transmitted (or on the contrary, it was transmitted) to the destination terminal 20 by the gateway 50 '.
• the synchronization messages SYNC [SMS1], SYNC '[SMS1] and SYNC ”[SMS1] used to transmit the message SMS1 respectively to terminals 20, 20' and 20” can be one and the same type of synchronization message, or even be synchronization messages of different types but conforming to the same synchronization protocol, or else respectively conforming to different synchronization protocols.
• Each terminal 20, 20 'and 20 can then, after having received respectively these synchronization messages SYNC, SYNC' and SYNC", extract the message SMS1 intended for the destination terminal 20 and store it in their own memories. respective ones, for consultation or subsequent restitution by a user.
• all the terminals associated with the destination terminal have the message SMS1 to be received by the destination terminal, as well as the information associated with this message, as described above.
• FIG. 4 illustrating a routing gateway according to one embodiment of the present invention.
• This routing gateway 50 comprises in particular a communication module 51 (typically implemented in the form of a transceiver) configured to receive, from a network node 40 responsible for storing and transmitting messages in the plane. signaling, a signaling message (illustrated by “MAP [SMS1]”) conforming to a signaling protocol suitable for signaling exchanges between network node and routing gateway (here the MAP protocol) in which an SMS1 message has been inserted to be transmitted to a destination terminal 20.
• MAP [SMS1] signaling message conforming to a signaling protocol suitable for signaling exchanges between network node and routing gateway (here the MAP protocol) in which an SMS1 message has been inserted to be transmitted to a destination terminal 20.
• This communication module 51 is also configured to transmit, to a synchronization server 30, a signaling message (illustrated by “MAP [SMS1]”) conforming to a signaling protocol suitable for signaling exchanges between routing gateway and server.
• a signaling message illustrated by “MAP [SMS1]”
• MAP [SMS1] a signaling protocol suitable for signaling exchanges between routing gateway and server.
• synchronization here also the MAP protocol
• this SMS1 message has been inserted, as well as possibly an indicator indicating the possible absence of transmission of this SMS1 message from this gateway directly to the destination terminal 20.
• this communication module 51 is also configured to transmit, to the destination terminal 20, a signaling message conforming to a signaling protocol suitable for signaling exchanges between routing gateway and terminals ( here the SIP protocol, but could also be the MAP or NAS protocol, for example) in which this SMS1 message was inserted.
• a signaling protocol suitable for signaling exchanges between routing gateway and terminals here the SIP protocol, but could also be the MAP or NAS protocol, for example
• This routing gateway 50 further comprises a processing module 53 (typically implemented in the form of one or more processor (s) executing computer program instructions stored by the routing gateway), configured first of all to process the signaling messages received from the network node 40, and in particular to extract therefrom an SMS1 message intended for a destination terminal 20 , for example an SMS message, when such a message has been inserted therein (this case being illustrated here in FIG. 4 by the message “MAP [SMS1]”).
• This SMS1 message once extracted from the “MAP [SMS1]” signaling message, can be analyzed in order to retrieve an identifier associated with the terminal 20 for which it is intended (here its identifier “MSISDN 2 o) ⁇
• the processing module 53 can determine whether the destination terminal 20 belongs to a multi-terminal system previously signaled to the gateway 50 ′, by means of this identifier.
• the processing module 53 interrogates a storage module 55 (typically a non-volatile memory, which is here illustrated as being included in the routing gateway 50 ', but being able to also be implemented in the form of a database separate from this gateway, to which this gateway has access) to check whether this identifier is stored there.
• a storage module 55 typically a non-volatile memory, which is here illustrated as being included in the routing gateway 50 ', but being able to also be implemented in the form of a database separate from this gateway, to which this gateway has access
• the processing module 53 can then insert the SMS1 message into a signaling message according to a signaling protocol suitable for the terminals (here the SIP protocol, but could be the MAP or NAS protocol , for example) and instruct the communication module 51 to transmit this signaling message to the destination terminal 20, without requesting the synchronization server 30.
• a signaling protocol suitable for the terminals here the SIP protocol, but could be the MAP or NAS protocol , for example
• the processing module 53 can then insert the message SMS1 in a signaling message suitable for exchanges with a synchronization server (here the MAP protocol) and instruct the communication module 51 to do so. transmit to the synchronization server 30.
• a synchronization server here the MAP protocol
• the processing module 53 can determine whether it is appropriate to insert this SMS1 message in a signaling message suitable for exchanges with terminals (eg the SIP, MAP or NAS protocol) and d '' instruct the communication module 51 to transmit this signaling message directly to the destination terminal 20, or on the contrary not to do (in which case it is then up to the destination terminal 20 to retrieve this message SMS1 directly from the synchronization server).
• a signaling message suitable for exchanges with terminals eg the SIP, MAP or NAS protocol
• a parameter indicative of a direct transmission to the destination terminal, in the signaling plane can be associated with the identifier indicating the membership of the destination terminal to a multi-terminal system, during the prior storage of this identifier by the routing gateway 50 ', in the storage module 55.
• the processing module 53 determines that the recovered identifier is stored in the storage module 55 (and therefore that the destination terminal belongs to a multi-terminal system)
• the processing module can also determine whether it is appropriate to transmit the SMS1 message directly to this destination terminal 20, checking for the presence of a parameter indicative of such direct transmission in the signaling plane.
• the identifier “MSISDN20” is associated with the parameter “+” indicating that a direct transmission in the signaling plane is to be carried out.
• the identifier “MSISDN 30” is associated with the parameter “-” indicating that a direct transmission in the signaling plane is to be inhibited, and therefore that the destination terminal 30 must recover itself, from the synchronization server. , the messages intended for it.
• the processing module 53 comprises what is stored in the storage module 55, not only that one or more synchronization messages should be prepared, including the message SMS1, to be transmitted to the terminals associated with the terminal 20, but also a signaling message should be prepared including this message SMS1 to be transmitted to the terminal 20.
• the processing module can insert, in the signaling message intended for the synchronization server 30, an indication that this synchronization server does not need to send a synchronization message to the destination terminal 20.
• the processing module 53 comprises what is stored in the storage module 55, which it is only necessary to prepare one or more synchronization messages, including this message, to be transmitted to the terminals associated with the terminal 30, without preparing a signaling message including this message to be transmitted directly to the terminal 30.
• the processing module can insert, in the signaling message intended for the synchronization server 30, an indication that this synchronization server must allow the destination terminal 20 to retrieve the message SMS1, for example by inserting this message SMS1 in a synchronization message that it transmits to it.
• the indication mentioned in the two preceding cases is then up to the destination terminal 20 to detect that it has already received the message SMS1 directly, and therefore that it does not need to retrieve it from of the synchronization server.
• the SMS messages sent to such a type of identifier are always transmitted in the signaling plane, and therefore without retrieval from the synchronization server.
• the synchronization server can then be configured, by means of a global parameter, to apply such a network policy.
• FIG. 5 illustrating a synchronization server according to an embodiment of the present invention.
• This synchronization server 30 comprises in particular a communication module 31 (typically implemented in the form of a transceiver) configured to receive, from a routing gateway 50 ', a signaling message comprising a message SMS1 intended for a destination terminal 20.
• This communication module is also configured to exchange synchronization messages with the terminal or terminals 20 ′, 20 ”associated with the destination terminal 20, or even also with the destination terminal 20 itself.
• the synchronization server 30 further comprises a processing module 33, configured first of all to process the signaling messages received from the routing gateway 50 ', and in particular to extract therefrom an SMS1 message intended for a destination terminal. 20, for example an SMS message, when such a message has been inserted therein (this case being illustrated here in FIG. 5 by the message MAP [SMS1]).
• a processing module is typically implemented in the form of one or more processors executing code instructions of a computer program, associated with a random access memory and / or a read only memory in which these code instructions are stored.
• This message SMS1 once extracted from the synchronization message MAP [SMS1], can then be stored in a storage module 35 (typically a non-volatile memory), which is here illustrated as being included in the synchronization server 30, but which can also be implemented in the form of a database separate from this server, to which this server has access to store these messages and then access them.
• a storage module 35 typically a non-volatile memory
• the storage of this message, in the storage module 35, can be done in association with an identifier of the destination terminal 20 (here, its identifier “MSISDN20”) in order to facilitate its subsequent retrieval.
• the processing module 33 can then check with the storage module 35 whether an SMS1 message associated with the unique identifier associated with it has been stored and, if this is the case, the module 33 can then retrieve this message in order to insert it into a synchronization message SYNC '[SMS1] that it provides to the communication module 31 so that the latter transmits the synchronization message SYNC' [SMS1] to the associated terminal 20 'in question.
• This operation is repeated for all the terminals associated with the destination terminal 20, to be synchronized by means of the server 30 (here also the terminal 20 ", to which the synchronization message SYNC" [SMS1] is transmitted). In one embodiment, this operation is also performed for the destination terminal 20 when it can be synchronized by means of a SYNC message [SMS1] sent by the server 30.
• the SYNC [SMS1], SYNC '[SMS1] and SYNC ”[SMS1] messages can be sent spontaneously (ie without a prior request having been received to trigger the sending of this message) by the synchronization server 30 respectively to the terminals 20, 20 'and 20 ”, for example at regular intervals, in a“ push ”mode.
• these synchronization messages can be messages sent in response to synchronization requests received by the synchronization server 30 respectively from the terminals 20, 20 'and 20 ”, in a so-called“ pull ”mode (such requests being illustrated by “REQ SYNC” in figure 5).
• FIG. 6 illustrating a so-called “associated” terminal, sharing the same identifier as another terminal, called “recipient”, recipient of a message transmitted by a source terminal, according to an embodiment of the present invention.
• This terminal 20 ′ (which may in particular be a mobile terminal of smartphone type) comprises in particular a communication module 21 ′ configured to receive, from a synchronization server 30 as described above, a synchronization message SYNC ′ [SMS1] in which the message SMS1 intended for a destination terminal 20 has been inserted.
• This communication module 21 ' can also be configured to send (for example, but not necessarily, at predefined intervals) the synchronization request “REQ SYNC” discussed previously to this synchronization server 30, with a view to triggering the sending of the synchronization message SYNC ′ [SMS1] in return.
• Such a communication module can be implemented in particular in the form of a radio transceiver, e.g. of one or more radio antenna (s) connected to a digital / analog converter.
• the terminal 20 'further comprises a processing module 23' configured first of all to process the synchronization messages received from the synchronization server 30, and in particular to extract therefrom from such a synchronization message a message intended for a another destination terminal 20, for example an SMS format message, when such a message has been inserted therein (this case being illustrated here in FIG. 5 by the message SYNC '[SMS1]).
• a processing module is typically implemented in the form of one or more processors executing code instructions of a computer program, associated with a random access memory and / or a ROM in which these code instructions are stored.
• SMS1 message once extracted from the SYNC synchronization message [SMS1], can then be stored in a storage module 25 ′ (typically a non-volatile memory) also included in the terminal 20 ’.
• a storage module 25 ′ typically a non-volatile memory
• this SMS1 message extracted from the synchronization message can be stored with other SMSA, SMSB messages (ie in the storage area associated with this same type of message in the terminal 20 '), so that this message SMS1 is accessible to the user in the same way as any other message of the same type which would be received in a more traditional manner (ie without resorting to a synchronization server).
• the terminal 20 ' also comprises a user interface module 27', typically in the form of a touch screen
• the user consults his messages received from the mobile network (for example the messages in the SMS format), he will not only see the SMSA and SMSB messages received conventionally from the mobile network (ie without resorting to the synchronization server 30), but also the SMS1 message received from the synchronization server 30.
• the module managing the user interface 27 ' can optionally distinguish (for example by means of different colors) these messages SMSA and SMSB, on the one hand, and SMS1 on the other hand, when they display them. in order to alert the user to the difference in origin of these messages.
• this module presents these messages identically, so that the implementation of the present invention is transparent for the user, who sees only a series of messages of the same type, regardless of whether they have been. received traditionally or through synchronization with a synchronization server.
• SMS type messages have been discussed previously as an example of short messages that can be advantageously transmitted by virtue of the embodiments of the present invention.
• any other type of message, more or less short can also be concerned, the invention being however particularly advantageous when the size of the message to be transmitted is less than the size of the field available for inserting it into a synchronization message between a terminal and a synchronization server, so that a single synchronization message is sufficient to transmit one (or even several) message (s), intended for a "recipient" terminal, to another terminal associated with this destination terminal.
• the synchronization server presented above can be specific equipment, dedicated only to the synchronization of messages with terminals associated with a terminal recipient of messages, but also any network equipment having other functionalities, in which a software module of “server” type is installed to exchange the SYNC synchronization messages presented above with a “client” type software module installed in terminals associated with the destination terminal.

Applications Claiming Priority (2)

Publications (1)

Family

ID=67810766

Family Applications (1)

Country Status (4)

Family Cites Families (4)

• 2019
  • 2019-04-05 FR FR1903652A patent/FR3094861A1/fr not_active Withdrawn
• 2020
  • 2020-04-01 EP EP20713921.3A patent/EP3949457A1/de active Pending
  • 2020-04-01 US US17/601,301 patent/US20220182800A1/en active Pending
  • 2020-04-01 WO PCT/EP2020/059199 patent/WO2020201320A1/fr unknown

Also Published As

Similar Documents

Legal Events