Messaging system and method

• US 9,160,569 B2
• Filed: 01/31/2011
• Issued: 10/13/2015
• Est. Priority Date: 02/01/2010
• Status: Active Grant

• Current Assignee: Markport Limited (Mavenir Group Holdings Ltd.)
• Original Assignee: Markport Limited (Mavenir Group Holdings Ltd.)
• Inventors: Wijbrans, Klaas, Krol, Aram
• Primary Examiner(s): PHUNKULH, BOB A
• Application Number:
  US13/575,101
• Publication Number:
  US 20120297004A1
• Time in Patent Office: 1,716 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: H04L 51/214 using selective forwarding
• CPC Class Codes: H04L 51/48 Message addressing, e.g. address format or anonymous messages, aliases
• CPC Class Codes: H04L 51/58 Message adaptation for wireless communication
• CPC Class Codes: H04W 4/14 Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]

Abstract

A messaging method is implemented by a system in a mobile network in which there are mobile devices including devices A, B, C, D, and E. An originating device sends a message addressed to multiple terminating devices. The system receives the messages and correlates them and routes them to the terminating devices. The system correlates the messages by grouping them according to originating device and sending time frame. The system allocates a global title record address from a pool for the session. The system forwards the messages with an MT-FSM, in which the originating device information is included in the message body, and the recipient address is that of the specific terminating device. The system transmits a confirmation message to the originating device.

Claims

1. A messaging method carried out by devices and a messaging system in a communication network, the method comprising the steps of:

an originating device sending messages with the same content and addressed to multiple terminating devices;

the system receiving the messages, automatically detecting that the messages are intended by the originating device user as being a single message to be addressed to a plurality of users which shall form a group, correlating said messages as being for group messaging, and routing the messages to the terminating devices with a reply path address of the system;

the reply path address being a global title address from a pool of global titles allocated to the system;

the system storing a group messaging record with data for the originating and terminating devices; and

the system subsequently receiving a reply from at least one terminating device, routing the reply to the originating device, and forwarding corresponding replies to the other terminating devices in the group.

2. The messaging method as claimed in claim 1, wherein the system correlates the messages by grouping them according to originating device and time of sending.

3. The messaging method as claimed in claim 1, wherein the system forwards the messages with an MT-FSM, in which the originating device information is included in the message body, and the recipient address is that of the specific terminating device.

4. The messaging method as claimed in claim 1, wherein the system transmits a confirmation message to the originating device when routing the messages to the terminating devices.

5. The messaging method as claimed in claim 1, wherein the messaging system assigns to each of a plurality of message service centres its own reply path address range for use in group messaging, and the service centre on which a multi-recipient group session originates assigns a reply path address from its own pool to the sessions, and, subsequently, replies are routed back to that specific service centre.

6. The messaging method as claimed in claim 5, wherein a session database is local to each service centre.

7. The messaging method as claimed in claim 1, wherein a plurality of message service centres of the system are assigned the same reply path address range for use in group messaging sessions, and when a new session originates, the service centre where the session is originating creates the new session in the session database and assigns a common reply path address to the session.

8. The messaging method as claimed in claim 1, wherein a plurality of message service centers of the system are assigned the same reply path address range for use in group messaging sessions, and when a new session originates, the service centre where the session is originating creates the new session in the session database and assigns a common reply path address to the session;

and wherein a session database replicates the change to other session databases, thus ensuring resilience in case of a site failure.

9. The messaging method as claimed in claim 1, wherein, to indicate that a subscriber is part of the group an additional message is inserted at an initial submission setting up the group.

10. The messaging method as claimed in claim 1, wherein after reception of the initial message from the originating device, an additional message is generated by the system to all recipients indicating that a group session is set up and containing the addresses of all the other recipients, and this message includes the addresses of each recipient in the body text and also uses the same system address in its reply-path field for each recipient as the subsequently forwarded message will use.

11. The messaging method as claimed in claim 1, wherein group messaging is automatically set up in response to an initial message from the originating device which includes a command code, and replies to this message do not need to contain the command code, as they use an embedded reply path system address.

12. The messaging method as claimed in claim 1, wherein the system operates in response to a control command to extend the group by inviting a party not addressed by the originating device to ongoing group communication by allocating a reply path address for the additional party, informing the other group member by sending a message indicating that the additional party is made part of the group.

13. The messaging method as claimed in claim 1, wherein the system operates in response to a control command to remove a party from the group.

14. The messaging method as claimed in claim 1, wherein the system operates in response to a control command to send a list of participants who are active in a group session.

15. The messaging method as claimed in claim 1, wherein the system operates in response to a control command to send a reply to only a specified party and not the whole group.

16. The messaging method as claimed in claim 1, wherein the system operates in response to a control command to delete a party from the group.

17. The messaging method as claimed in claim 1, wherein the system operates in response to a control command to indicate usage of pre-defined group n so that it is not necessary to send a multi-recipient message from the device.

18. The messaging method as claimed in claim 1, wherein the system performs automatic group messaging detection by:

when the message is received from the originating device, storing the message and a time stamp in a database,

if the originating device sends another message, comparing all relevant fields to the message stored in the database, and if these are the same, the recipient is added to a recipient list in the database for this message and the submission is acknowledged, and

if any field is different, or after a configurable time-out expires, the group submission is considered to be complete, and the system then starts handling the message as a group message.

19. The messaging method as claimed in claim 1, wherein the system performs automatic group messaging detection by the originating device sending all of the messages in a single TCAP session or by the originating device using a field for a flag indicating that additional messages are waiting for submission by the originating device.

20. The messaging method as claimed in claim 1, wherein the system performs automatic group messaging detection by recognizing a specific keyword in the message from the originating device as indicating that a new group is to be started.

21. The messaging method as claimed in claim 1, wherein the system manages, either remotely or locally, a group messaging database having the following data:

session data, containing records identifying a group messaging session, the session data having a start time and a modify time, in which the modify time is updated every time a message is exchanged in the group, and in which the session data has a flag indicating whether the session is considered active or expired,

recipient data linking the recipients in a session to the sessions,

data per individual subscriber with active or retired session records with the allocated reply path number for that session and a reference to the session, and

a flag indicating status of the reply path.

22. The messaging method as claimed in claim 1, wherein the system manages, either remotely or locally, a group messaging database having the following data:

session data, containing records identifying a group messaging session, the session data having a start time and a modify time, in which the modify time is updated every time a message is exchanged in the group, and in which the session data has a flag indicating whether the session is considered active or expired,

recipient data linking the recipients in a session to the sessions,

data per individual subscriber with active or retired session records with the allocated reply path number for that session and a reference to the session, and

a flag indicating status of the reply path; and

wherein the flag indicating status of the reply path indicates whether it is active, retired or available, and the system manages a time stamp indicating when it went from active to retired, in which if a new session is set up, one of a number of available reply path addresses is selected and allocated to the session, and if a session has been inactive for a set period of time, for each recipient the associated reply path address is set to retired status and the time-stamp is set to that time, and in which after a minimum purge period has passed, the reply path address is set to available so that it can be re-used for new sessions.

23. A messaging system comprising an interface to mobile network elements and a circuit including at least one digital data processor, in which the circuit is perform the steps of:

an originating device sending messages with the same content and addressed to multiple terminating devices;

the system receiving the messages, automatically detecting that the messages are intended by the originating device user as being a single message to be addressed to a plurality of users which shall form a group, correlating said messages as being for group messaging, and routing the messages to the terminating devices with a reply path address including the system;

the reply path address being a global title address from a pool of global titles allocated to the system;

the system storing a group messaging record with data for the originating and terminating devices;

the system subsequently receiving a reply from at least one terminating device, routing the reply to the originating device, and forwarding corresponding replies to the other terminating devices in the group.

24. A computer program product, comprising a non-transitory computer usable medium having a computer readable program code embodied therein, said computer readable program code being executed to implement a method comprising the steps of:

receiving messages with the same content and addressed to multiple terminating devices, automatically detecting that the messages are intended by an originating device user as being a single message to be addressed to a plurality of users which shall form a group, correlating said messages as being for group messaging, and routing the messages to the terminating devices with a reply path address including a system;

the reply path address being a global title address from a pool of global titles allocated to the system;

storing a group messaging record with data for the originating and terminating devices; and

subsequently receiving a reply from at least one terminating device, routing the reply to the originating device, and forwarding corresponding replies to the other terminating devices in the group.