WO2008075324A1

WO2008075324A1 - A system for providing group messaging services in a telecommunications network

Info

Publication number: WO2008075324A1
Application number: PCT/IE2007/000122
Authority: WO
Inventors: Mark Peter Dargan; William John Redmond
Original assignee: Mark Peter Dargan; William John Redmond
Priority date: 2006-12-21
Filing date: 2007-12-12
Publication date: 2008-06-26
Also published as: IE20060948A1

Abstract

A system (10) for providing a group messaging service in a telecommunications network (11) has a message sending mobile terminal (12), a plurality of message receiving mobile terminals (13, 14, 15), winch together constitute the group (12, 13, 14, 15), and a server (16) in communication with the group (12, 13, 14, 15) through the telecommunications network (11). A group module (17) in communication with the server (16) compiles and maintains information on the group (12, 13, 14, 15), and a message confirmation module (18) in communication with the server (16) compiles a report, for transmission to the message sending mobile terminal (12), of the members of the group (12, 13, 14, 15,) who have not received a particular message therefrom. The group manager only needs to consult one receipt report for a particular message sent rather than a receipt report from each member of the group.

Description

A system for providing group messaging services in a telecommunications network

Technical Field

This invention relates to messaging services in a telecommunications network and, in particular, to a system for providing group messaging services in a mobile telephony network.

Background Art

In a mobile telephony network, a mobile terminal is used for making and receiving voice communications by way of a telephone service. However, increasingly, mobile terminals are also used for data services, including messaging.

By a mobile terminal in this context is meant a mobile phone, palmtop computer, laptop computer or other mobile communication device capable of sending and receiving text messages.

A mobile terminal can transmit/receive a short message to/from another mobile terminal as well as other information, such as traffic information, weather information, etc., using the Short Message Service (SMS). This non-speech service enables a short message to be delivered, through an intermediate network-based SMS server, to a terminating mobile terminal, even though the terminating mobile terminal line may be busy or temporarily out of reach. This is accomplished by what is termed a store and forward system.

The SMS is designed for operation in two modes. The first mode is similar to a pager system and is referred to as a point-to-point service. In this system a first mobile terminal user simply types the desired text message using the mobile terminal keyboard, selects the directory number associated with a destination mobile terminal user and transmits the SMS message.

In the second mode, which is referred to as a multipoint or cell broadcast system, a given message, e.g., traffic conditions, weather forecast etc., is transmitted to all active mobile terminals in a particular cell.

One difference between point-to-point and multipoint messaging is that whereas reception confirmation is generally obtained in point-to- point transmissions, multipoint SMS is a one-way transmission without confirmation.

At present only the above two modes of SMS messaging are properly supported by a telephone network. Current SMS systems and services are unable to deliver selectively an SMS message to a subset of the available users.

However, because of the need for more powerful messaging capability a number of add-on solutions have been developed, including the sending of an SMS message from one person to a selected list of people. A person who wishes to contact a group of people simultaneously, via SMS, can use a variety of mechanisms, such as, groups on their phonebook, a contacts tool with distribution lists on the operator's web site, e.g., Vodafone All@once (Vodafone and All@once are trademarks), or list messaging applications on service provider platforms, which allow individuals to receive certain information e.g. Lotto, sports results, or marketing campaigns, by subscription.

List or group texting services as currently constituted have many drawbacks.

With groups and contacts tools, located on a mobile terminal, one drawback is that the senders have to pay for all the text messages and have to manage the list themselves. Moreover the mobile terminal must actually send an individual copy of the text to each person on the group list. Furthermore, not all mobile phone operators provide groups and contacts tools on their mobile terminals.

Moreover, for list or group texting services there is no simple method for ascertaining who received and who did not receive a particular message.

With network server solutions the applications are tailored for specific information and so the information engine part is different for each application. The volume of traffic generated by the list has to be sufficient to cover the hosting costs, connection fees and development costs. Therefore, as a business model, such server solutions only work for costly premium rate services, bulk messaging or very high volume services. Simple, or low cost, traffic will not work as a business model as it is necessary to generate significant revenue to cover the sunk and ongoing costs.

Furthermore, all network server-based solutions currently require a web-based application to create user lists.

Also network server based solutions do not offer any kind of message delivery confirmation.

It is an object of the present invention to overcome the disadvantages of the messaging services hereinbefore described.

Disclosure of Invention

Accordingly, the invention provides a system for providing a group messaging service in a telecommunications network, the system comprising a message sending mobile terminal, a plurality of message receiving mobile terminals, which together constitute a group, a server in communication with the group through the telecommunications network, a group module in communication with the server for compiling and maintaining information on the group, and a message confirmation module in communication with the server, which compiles a report, for transmission to the message sending mobile terminal, listing the members of the group, who have not received a particular message therefrom. An advantage of the system according to the invention is that a sender of the message does not have to check reception confirmations from each member of the group but only one return message indicating those group members who have not received the original message. The return message can be repeated at programmed intervals, as required.

Preferably, the group module and the message confirmation module are programmable through the message sending mobile terminal.

An advantage of this feature is that the user of the message sending mobile terminal can set up a particular group using the terminal only.

Further, preferably, access to the group module and the message confirmation module is protected by use of a Personal Identity Number (PIN).

The use of a PIN protects any data held in the group module and the message confirmation module, the settings of which, for a particular group, can only be changed by someone who knows the PIN associated with that group.

Alternatively, access to the group module and the message confirmation module can be transferred, for a period of time, to a third party by the user of the message sending mobile terminal.

Thus, the user of the message sending mobile terminal can program the group module and the message confirmation module to accept instructions from a third party for example while the user is away on holidays. On his return he can cancel this temporary permission.

In one embodiment of the system according to the invention, the time interval between the sending of a message and the receipt of a message reception report may be set, for a particular message, through the message sending mobile terminal.

Thus, the message sender can decide when he wishes to receive the message reception report for a particular message at the time he is sending the message. This could be advantageous where the message is urgent and the sender needs to know quickly if any of the group has not received it.

Preferably, the time interval between the sending of a message and the receipt of a message reception report may be preset for all messages when the group is set up.

This feature would be of use where the messages being sent to the group members are similar in nature and can be treated in the same fashion. This reduces the requirement for checking the settings in the message confirmation module each time a message is to be sent.

In a further embodiment of the system according to the invention, the time interval between the sending of a message and the receipt of a message reception report may be determined within the message confirmation module. Where the messages to a group can be classified and tagged according to some parameter e.g. urgency, then the message confirmation module can be programmed to send out the message reception report at an appropriate time for a particular message.

Preferably, determination of the time interval is based on the percentage of successful message deliveries.

Thus, a preset percentage of delivery receipts received will trigger the generation and delivery of the message reception report.

Alternatively, determination of the time interval is based on message delivery success history over time.

Where messages of a particular type are being sent regularly the message confirmation module can determine the appropriate time to deliver the message confirmation report based on past patterns of delivery receipt returns.

Alternatively, determination of the time interval is based on a particular message content.

Thus, the message confirmation module could be programmed to parse the message to be sent for a key identifier, which would be matched to a preset time interval for the generation of the message confirmation report. Alternatively, determination of the time interval is based on the time of sending of the message.

Thus, for example, if the messages to a group relate to regular activities on a particular day of the week, then the nearer to that day that the message is sent the shorter will be the time interval before the message confirmation report is delivered.

In a further embodiment of the system according to the invention, the group is identified within the telecommunications network by a combination of a unique Mobile Subscriber International Subscriber Identity Number (MSISDN) for the system, the MSISDN of the message sending mobile terminal and the group name.

An MSISDN for the system can be a short five digit premium number, which is reserved on each mobile network through which messages are to be sent to the server. Each group within the group module is further identified by the MSISDN of the message sending mobile terminal through which the group has been set up. Finally, each group is identified by a group name.

Preferably, each member of the group is identified within the group module by their MSISDN.

The MSISDN linked to a particular group can also be associated in the group module with the MSISDNs of the group members such that a message sent to the group MSISDN will be forwarded to each of the group members in one operation. Further, preferably, each member of the group is further identified within the group module by a user friendly identifier.

An example of such a user friendly identifier would be the group member's Christian name. This user friendly identifier could be included in the report compiled by the message confirmation module.

In a still further embodiment of the system according to the invention, a WEB interface enables data for a particular group to be reviewed and edited.

A web interface is useful where a person is managing a number of groups. Thus, all the settings for a particular group and all the details of the group members could be reviewed on screen and edited as required.

Preferably, the WEB interface enables analysis of the message traffic for a particular message to be undertaken.

Further, preferably, analysis of the message traffic can be used to determine the optimal period for resending a failed message.

Thus, analysis of the message data can identify the reason for receipt failures and based on this information the group manager can make a decision on how to deliver successfully the message to a particular member of the group. Further, preferably, a log of all messages sent to a group is maintained by the group module and is accessible by the members of the group.

Access to the message records can be important where public bodies are using the system. Thus, records of the message contents and lists of to whom each message was sent can be retained by the public body, as required.

Brief Description of Drawing

The accompanying Figure is a schematic representation of the system in accordance with the invention.

Best Modes for Carrying Out the Invention

The invention will be further illustrated by the following description of an embodiment thereof, given by way of example only with reference to the accompanying Figure.

Referring to the Figure there is illustrated generally at 10, a system for providing a group messaging service in a mobile telecommunications network, shown generally at 11, the system 10 comprising a message sending mobile terminal in the form of a mobile telephone 12, a plurality of message receiving mobile terminals in the form of mobile telephones 13, 14, 15, which together constitute the group 12, 13, 14, 15, and a server 16 in communication with the group 12, 13, 14, 15 through the telecommunications network 11. A group module 17 in communication with the server 16 compiles and maintains information on the group 12, 13, 14, 15, and a message confirmation module 18 in communication with the server 16 compiles a report, for transmission to the message sending mobile terminal 12, of the members of the group 12, 13, 14, 15, who have not received a particular message therefrom.

A short message from the message sending mobile terminal 12 is routed through the communications network 11 via a Mobile services Switching Centre/Visitor Location Register (MSC/VLR) 20, which relays the short message out of the particular Public Land Mobile Network (PLMN) servicing the message sending mobile terminal 12 to a Short Messaging Service Mobile services Switching Centre (SMS-MSC) 21. The short message is then transferred to the server 16 using the Short Message Peer-to-peer Protocol (SMPP).

A message to the group 12, 13, 14, 15 is sent from the group module 18 through the network 11 to the plurality of message receiving mobile terminals 13, 14, 15.

Short messages can also be received by the server 16 through other networks represented by cloud 22. A short message sent from the server 16 through one of the alternative networks 22 routes through a Short Message Service/Gateway Mobile services Switching Centre (SMS- GMSC) 23, which identifies the recipients of the message by consulting the Home Location Register (HLR) 24 of the particular PLMN of the called message receiving mobile terminal (not shown) and forwards the message thereto. Typically the system 10 could be used by the user of the message sending mobile terminal 12, hereinafter referred to as the group list owner, to set up the particular group 12, 13, 14, 15 so that he can send messages to the members of the group 12, 13, 14, 15 from time to time. A software application on the server 16 manages the group messaging service and the group list owner, can manage the group 12, 13, 14, 15 by programming the group module 17 and the message confirmation module 18 through the mobile message sending mobile terminal 12. Access to the group module 17 and the message confirmation module 18 is protected by use of a Personal Identity Number (PIN) .

The following are examples of how the group list owner can manage the group 12, 13, 14, 15.

Example 1

Creating a Group List

The group list owner sends a COMMAND STRING to the server

16 from the mobile message sending mobile terminal 12 using short messaging with the CREATE message, which comprises the command CREATE with an optional alphanumeric string suggesting the group list name,

e.g. CREATE clubTeamUlO

The SMS message is routed through the SMS-MSC 21 using standard mechanisms to the server 16. The group list is created in the group module 17 using the suggested group name. The group module 17 associates the group name with the list owner's Mobile Subscriber International Subscriber Identity Number (MSISDN) and a PIN code is generated for the group list. The PIN is specific to the group list and thus the group list can be managed by a person other than the group list owner provided he knows the PIN.

Once created successfully the server 16 sends back the group list name and PIN code to the list owner.

Billing for set-up of the group is done via standard billing mechanisms.

Example 2

Subscribing or Unsubscribing to/from the group list.

The list owner distributes the group list name to the intended group members. A potential group member may then send a mobile message containing a command string including the list owner (LO) MSISDN and the group list name from his message receiving terminal 13, 14, 15 to the server 16 via the SMS-MSC 21 using the same routing mechanism. The MSISDN of the group member is then added to the group list maintained in the group module 17. An example of such a command string for subscribing to a group list is as follows:

START LO MSISDN clubTeamUlO joe In the above subscribe message, the potential group member has appended a user friendly name "joe" so that the list owner can more easily identify him in future.

The group member can unsubscribe in a similar way using the following command string

STOP LO MSISDN clubTeamUlO

Adding a member to the group or removing a member from the group can also be accomplished by the list owner.

Billing for subscription is done via standard billing mechanisms.

Example 3

Posting a message to the group

The list owner may post to the group list by sending an SMS message to the server 16 with a post command, followed by the group list name, followed by the message, as follows:

POST clubTeamUlO "game off folks"

The list owner MSISDN and group list name are used by the group module to manage the lists.

The SMS message is routed via the SMS-MSC to the group module 17 via the server 16 where the sender's MSISDN is checked to ensure that the message is from the list owner and if so parses the message for the group list name and forwards the remainder of the message i.e. to the group members.

Reverse billing is used to charge the group members for the messages.

Billing for message posting is done by standard billing mechanisms.

The message confirmation module 18 analyses and correlates the delivery reports from the networks. For each message sent a record is compiled of the group members to whom the message was sent and the delivery reports received.

If a delivery report has not been received from a particular group member by a preset time the message is sent again to that group member. This step is repeated for a programmed number of times or until a preset number of delivery reports have been received. The message confirmation module then generates a summary report and sends it to the list owner, who can then decide what action needs to be taken, where a group member has not received the original message. Thus, only one report has to be reviewed at this stage by the list owner, for a particular message sent to the group members.

The message confirmation module is programmed to send further summary reports at programmed intervals, depending on the rate of receipt of the individual delivery reports. Thus, the list owner can choose to wait for a further summary report before taking any action.

Example 4

Deleting a group list

A group list can be deleted from the server 16 by the list owner by sending the following command:

DEL clubTeamUlO

Claims

Claims: -

1. A system for providing a group messaging service in a telecommunications network, the system comprising a message sending mobile terminal, a plurality of message receiving mobile terminals, which together constitute a group, a server in communication with the group through the telecommunications network, a group module in coinmunication with the server for compiling and maintaining information on the group, and a message confirmation module in communication with the server, which compiles a report, for transmission to the message sending mobile terminal, listing the members of the group, who have not received a particular message therefrom.

2. A system according to Claim 1, wherein the group module and the message confirmation module are programmable through the message sending mobile terminal.

3. A system according to Claim 2, wherein access to the group module and the message confirmation module is protected by use of a Personal Identity Number (PIN).

4. A system according to Claim 2, wherein access to the group module and the message confirmation module can be transferred, for a period of time, to a third party by the user of the message sending mobile terminal. . ' ^;

5. A system according to any preceding claim, wherein the time interval between the sending of a message and the receipt of a message reception report may be set, for a particular message, through the message sending mobile terminal.

6. A system according to any preceding claim, wherein the time interval between the sending of a message and the receipt of a message reception report may be preset for all messages when the group is set up.

7. A system according any one of Claims 1 to 4, wherein the time interval between the sending of a message and the receipt of a message reception report may be determined within the message confirmation module.

8. A system according to Claim 7, wherein determination of the time interval is based on the percentage of successful message deliveries.

9. A system according to Claim 7, wherein determination of the time interval is based on message delivery success history over time.

10. A system according to Claim 7, wherein determination of the time interval is based on a particular message content.

11. A system according to Claim 7, wherein determination of the time interval is based on the time of sending of the message.

12. A system according to any preceding claim, wherein the group is identified within the telecommunications network by a combination of a unique Mobile Subscriber International Subscriber Identity Number (MSISDN) for the system, the MSISDN of the message sending mobile terminal and the group name.

13. A system according to any preceding claim, wherein each member of the group is identified within the group module by their MSISDN.

14. A system according to Claim 13, wherein each member of the group is further identified within the group module by a user friendly identifier.

15. A system according to any preceding claim, wherein a WEB interface enables data for a particular group to be reviewed and edited.

16. A system according to Claim 15, wherein the WEB interface enables analysis of the message traffic for a particular message to be undertaken.

17. A system according to Claim 16, wherein analysis of the message traffic can be used to determine the optimal period for resending a failed message.

18. A system according to any one of Claims 15-17, wherein a log of all messages sent to a group is maintained by the group module and is accessible by the members of the group.

19. A system according to Claim 1 for providing a group messaging service in a telecommunications network, substantially as hereinbefore described with particular reference to and as illustrated in the accompanying drawing.