WO2007072055A1

WO2007072055A1 - Messaging systems for use in telecommunications networks

Info

Publication number: WO2007072055A1
Application number: PCT/GB2006/004916
Authority: WO
Inventors: Jeffrey Wilson
Original assignee: Intellprop Limited
Priority date: 2005-12-22
Filing date: 2006-12-22
Publication date: 2007-06-28
Also published as: GB0526223D0; GB2433674A

Abstract

A method and apparatus are provided for sending messages such as video or voice mail messages in a telecommunications system. A recipient message number is allocated to a subscriber to the system for each recipient to whom the subscriber wishes to send messages. This allocated recipient number is then stored with an associated recipient number. The subscriber makes a call to the recipient message number and a message is recorded in the call. A recipient pick-up number is then allocated to the recorded message and the recorded message is stored. A separate message including the recipient pick-up number is then sent to the recipient and he is able to dial the recipient pick-up number to retrieve the stored message.

Description

MESSAGING SYSTEMS FOR USE IN TELECOMMUNICATIONS NETWORKS

FIELD OF THE INVENTION

This invention relates to messaging systems for use in telecommunications networks and particularly to messaging systems of the type which may be used in mobile telecommunications networks.

BACKGROUND TO THE INVENTION

One of the frequently used features of mobile telecommunication networks is text messaging. This is implemented in GSM GPRS and 3G systems. It enables a sender of a message to type the message on his handset and then send it to a desired recipient. The message is sent via a data channel in the GSM GPRS and 3G systems. This data channel has a narrow bandwidth and is suitable to transmit the basic character data used for text messaging.

Text messaging is one way and is therefore well suited to situations where transfer of information is required but dialogue with the recipient is not required.

The narrow bandwidth data channels used for text messaging are not well suited to transmit broader bandwidth messages such as voice messages or video messages. Furthermore, such messages would require a recipient to have a handset which can store and playback voice or video message, when such a message is received.

It would therefore be desirable to provide a system which gave a user a one way mode of voice or video message without the bandwidth restrictions of text messaging and in the case of voice messages without requiring a user to have a handset with store and play back functions.

Many networks have voicemail services. However, these are only accessed after an unsuccessful attempt at a normal voice call. It is not possible to access directly a subscriber's voicemail. Furthermore, many subscribers disable their voicemail service for reasons of cost. SUMMARY OF THE INVENTION

Preferred embodiments of the present invention provide a system for sending voice or video messages to a recipient and which enables the recipient to listen to the voice or video message at a time convenient to him. This is achieved within a network by enabling a user to store a message in the network and to notify the recipient of the existence of the message. An access number is provided to the recipient and he uses this to retrieve the message at a time convenient to him.

Preferably the system enables a user to set up an association in the network between a recipient's number and a number the user has to dial to send a voice or video message to that recipient. The number the user has to dial can then be stored in the phone book on his handset.

In accordance with one aspect of the invention there is provided a method for sending messages in a telecommunication system comprising the steps of: allocating to a subscriber a recipient message number for each recipient to whom the subscriber wishes to send messages; storing the thus allocated recipient message number with an associated recipient number; receiving a call from the subscriber to a recipient message number; recording a message provided by the subscriber in the call; storing the recorded message; allocating a recipient pick-up number to the recorded message; sending a separate message to the recipient, the separate message including the recipient pick-up number.

Preferably the system is adapted to send voice or video messages.

Preferably the method includes the step of identifying the subscriber from CLI data included in the call to the recipient message number.

Preferably the method includes the step of retrieving the recipient number using the received CLI data.

Preferably the step of storing the recorded message includes the step of storing the recipient number with the recorded message. Preferably the method dynamically allocates the recipient pick-up number to the recorded message.

Preferably the step of storing the recipient number includes storing a file number for the recorded message and the recipient pick-up number for the recorded message.

Preferably the method includes the step of deleting the recorded message after a predetermined period of time.

Aspects of the invention also provide a method for retrieving messages so stored comprising the steps of: receiving a call to a recipient pick-up number allocated to a stored message, and retrieving and playing back the stored message to a person making the call.

Preferably this method includes the step of comparing CLI data received with the call with a recipient number stored with the message, and playing back the message in dependence on the result of the comparison.

BRIEF DESCRIPTION OF THE DRAWINGS

Preferred embodiments of the invention are now described in detail by way of example with reference to the accompanying drawings, in which:

Figure 1 is a flow diagram of the set up phase in an embodiment of the invention;

Figure 2 is a flow diagram of the message recordal phase in an embodiment of the invention; and

Figure 3 is a flow diagram of a message play back phase in an embodiment of the invention.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

An embodiment of the invention is now described in the context of voice messaging, but can be extended to video or other message formats. In order to use an embodiment of the invention, a subscriber to a voice messaging service must first go through a set up phase for each recipient to whom he wishes to send voice messages. Following the set up phase, he can send voice messages in a straightforward manner. The set up phase of the service will be described later but initially the operation of the service once it has been set up will be described.

In operation, subscriber A wishes to send a voice message to a friend called John Smith. In the phone book of his handset subscriber A has an entry named John Smith SVS, (where SVS stands for Short Voice Service). Subsriber A selects John Smith SVS from the phone book in the normal way and a call is made to the number associated with that entry. Once the call is connected an automatic response invites subscriber A to leave a message, for example, it could say "please leave your message after the tone". He then records the voice message he wishes to send to John Smith and ends the call. John Smith then receives a text message, for example over the SMS system, the sender of which appears to John Smith as subscriber A. The text message indicates that a voice message has been left for him and provides a number to retrieve the voice message. For example, the message could read "I have just left you a short voice service message on +447797835462".

John Smith then calls the number provided and hears the message left by subscriber A. The message is retained by the system for a set period of time, e.g. seven days. John Smith can call the number again if he wishes to relisten to the message.

Most mobile telephones which use the SMS service enable detail from a text message such as a number to be used by the recipient by entering a simple sequence of key presses. Thus, it is a straightforward matter for John Smith to select the number from the received text message and use it to make a call to receive the voice message.

The set up phase performed by subscriber A is now explained. The voice message or SVS service is provided by the network to which A is a subscriber. The network could make the service available to subscribers of other networks if it chose to do so, although this would involve additional charging difficulties. The set up service is available on network A preferably by dialling a short code (e.g. 787 which corresponds to the key pad letters SVS). A longer number could be used by subscribers to other networks.

In order to set up e.g. John Smith's mobile number to receive voice messages, subscriber A sends a text message to 787 containing John Smith's mobile number, e.g. 07700900123. Subscriber A receives back from the network a text message which includes a number to use to send voice messages to John Smith. For example, the message could read "save +447797835926 in your phone book, and call it to send a short voice service message to 07700900123". Thus, the network has associated a number which subscriber A must ring with the facility to send a voice message to John Smith's mobile number. Subscriber A saves the allocated number in his phone book with an indication that it is for sending voice messages and is then able to send voice messages to John Smith at any time in the future.

It will be appreciated from the above overview that a service embodying the present invention is straightforward for a user to set up and use. It can be implemented on existing handsets without modification and can therefore very easily be provided to a large number of people.

The processes which have to be performed in the network in order for this voice messaging service to operate are now described. Various terms are used in this description which require definition and these are as follows:

"Subscriber number" is the telephone number of a subscriber to the service.

"Recipient number" is the number of a person to whom a subscriber wishes to send a voice message.

"Recipient SVS number" (or recipient message number) is a number dynamically allocated by the system to a particular recipient number and is associated with a particular subscriber number. It is used by the subscriber to send a voice message to the associated recipient number.

"Recipient pick-up number" is a number used by a recipient to retrieve a stored voice message. It is dynamically allocated and associated with that message, and the recipient. Figure 1 illustrates the steps which take place in the network during the set up phase. At 2, a new recipient number is received from a subscriber. At step 4, a recipient SVS number is allocated in response to the new recipient number. At 6, this recipient SVS number is sent to the subscriber in a text message so that he may store it in his handset as the number he will use to send voice messages to that recipient. At 8, the recipient number received at step 2 is stored along with the recipient SVS number which has been allocated and the subscriber number. Thus, an association has been made between the subscriber number, the recipient SVS number, and the recipient number. This enables the recipient number to be retrieved and used when the subscriber records a voice message for a recipient, by dialling the recipient SVS number.

Figure 2 shows the steps which are performed when a subscriber wishes to record a voice message for a recipient.

At 10, a call is received from a subscriber to a recipient SVS number. This calll activates a prompt to the subscriber to record a voice message which he does at 12. The recipient SVS number which is dialled and the subscriber number which is included in received CLI data are used to retrieve from storage the recipient number at 14. A recipient pick-up number is dynamically allocated to the recorded message at 16. The recorded message is then stored at 18 in a dynamically allocated file. The recipient pick-up number and the recipient number are stored with the file address and are used to enable the recorded message to be subsequently retrieved. A text message is then sent at 20 to the recipient number which was retrieved at 14. This text message indicates that a voice message has been recorded for the recipient.

Figure 3 shows the steps which take place in the network when a recipient picks up a recorded voice message. At 20, a call is received from the recipient to the recipient pick-up number. The recipient pick-up number and recipient number received via CLI are used at 22 to retrieve the stored message. The message is then played back at 24 to the recipient over the connection which has been established.

The system is preferably implemented in a communications network using known programmable devices. A preferred embodiment comprises an SMS router that can route certain text messages to a query unit which can receive and respond to natural language in formatted text queries (such as the Telsis SMS Wizard (TM) and an interactive voice response (IVR) unit such as Telsis FastlP (RTM). These two units require a communication link and protocol between them.

The IVR unit is preferably connected to the query unit via an IP (Internet Protocol) link. The IVR is connected to the communication network via a service switching point (SSP) in the network.

Text messages which are sent to the SVS service number 787 by subscribers on a home network, or messages sent to an equivalent long number (if allocated) are routed by the SMS router to the query unit. This query unit is able to process received text message content according to syntax rules programmed into it. If the content is unrecognised or otherwise invalid the query unit may send suitable help messages or error messages.

Associations between the recipient SVS numbers and recipient numbers are dynamically allocated by the query unit when they are required during set up operation. Associations between these two numbers are also associated with a subscriber number and therefore only apply to calls made by that subscriber as identified by his calling line identification (CLI). The association is set up indefinitely unless the subscriber chooses to delete it. Thus, because the association is personal to the subscriber, the same access number may be reused by another user but will lead to a different association between subscriber and recipient being retrieved by the system. If a user withholds his CLI on a call, then the system will not operate for that call, and the call will be cleared after an error message has been transmitted.

A predefined number of recipient SVS numbers are allocated to each subscriber, e.g. 50 and because of the association with a subscriber, these may be the same numbers for each subscriber. The system provides the subscriber with the ability to ask queries in order to ascertain the number of the remaining free allocations or the content of any particular allocation. These are dealt with by the query unit. The examples of the type of queries which can be handled are shown below.

In response to any received query, the query unit constructs an appropriate reply text and delivers it to the subscriber's number.

The recipient pick-up number which is texted to the recipient is also dynamically allocated, preferably from a different number range to the recipient SVS numbers used by subscribers. The recipient pick-up number remains valid for a predefined period, such as seven days, after which its association with the recorded message and the recipient is deleted, along with deletion of the recorded message. The recipient can listen to the message as many times as he likes during this period. For additional security, the recipient's telephone number is also stored with the stored voice message and can be checked against a recipient's CLI when he dials in using the voice message number. This feature can be used to ensure that a recording is never played to any recipient other than the one intended.

In operation, when a subscriber calls a recipient SVS number a call arrives at the IVR which then queries the query unit over the IP link by sending a message containing the subscriber number and a recipient SVS number to determine whether or not there is a matching allocation stored. If no matching allocation is found then a suitable negative response is returned and the call is cleared with an appropriate error message. If a matching allocation is found then the query unit returns a response containing the corresponding recipient number and sufficient information to correlate the response with the original query.

The IVR will allocate a file number and will prompt the caller to leave the voice message to be recorded. The IVR will then allocate a recipient pick-up number to the recorded message. The recipient pick up number is allocated from the predefined range discussed above. The recipient pick-up number, and the file number are then stored in a data structure on the IVR. They may be hashed together so as to be easily searchable. As discussed above, the recorded file itself may be tagged with the recipient number, and this may be included in the file name for extra security.

The system may offer interactive menu choices to allow a subscriber to review, rerecord, or abandon his recorded message.

The creation of a message causes the query unit to construct and send an alert text to the recipient. This will contain the telephone number of the subscriber and the recipient pick-up number. The resultant text is sent to the recipient with the CLI of the subscriber.

When the recipient calls into the recipient pick-up number the call is passed to the IVR. This checks for a matching entry in its data structure for the recipient number and the recipient pick-up number and if it finds one is able to look up the recorded file. If the file has been tagged with the recipient number then this is also checked. The recorded file is then played to the recipient. The system may include various interactive options for replay, rewind, fast forward etc. The recipient may be prompted to delete or retain the message but these are not essential features. The system may also enable the user to enquire as to the remaining time for which the message will be stored and the date and time it was left along with the CLI of the sender. These are all optional features.

A housekeeping service provided on the IVR periodically checks the database of stored messages and deletes entries older than a predetermined age such as seven days along with the corresponding stored file. The associated recipient pick-up number is then returned to the free list of recipient pick-up numbers.

The system can deal with error conditions such as disk full, or no available recipient pick-up numbers using straightforward error logic and by generating suitable audio messages prior to clearing any calls.

The storage structure and data instructions used may vary according to the networks on which embodiments of the invention are implemented.

A similar system may be used with video messaging. The only difference here is that it is video rather than a voice data which is stored. Other forms of message may also be used.

The system may be modified to enable a user to define groups of recipients. These can be stored in the network. When a group is created, a subscriber number may be associated with a single recipient SVS number and a plurality of recipient numbers. When a message is recorded for a group, the system will associate the file number with a single recipient pick-up number and a plurality of recipient numbers, such that each of the recipients is able to pick up the same message.

The system has significant advantages over voice mail systems. It enables a subscriber to send a voice or video message to a recipient without making a direct call to the recipient for example if he does not immediately require a dialogue, or so as not to interrupt the recipient. He is able to do this for recipients who do not have a voice mail service or who has chosen to disable his voicemail service because the message service is associated with the subscriber.

Embodiments of the invention can be implemented in mobile networks, and also in other networks which enable text as well as voice calls to be made. The invention can be implemented in programmable units as described above with appropriate software, or may be implemented in dedicated hardware.

Claims

1. A method for sending messages in a telecommunications system comprising the steps of : allocating to a subscriber a recipient message number for each recipient to whom the subscriber wishes to send messages; storing the thus allocated recipient message number with an associated recipient number; receiving a call from the subscriber to a recipient message number; recording a message provided by the subscriber in the call; allocating a recipient pick-up number to the recorded message; storing the recorded message; sending a separate message to the recipient, the separate message including the recipient pick-up number.

2. A method according to claim 1 in which the message is a voice message.

3. A method according to claim 1 in which the message is a video message.

4. A method according to claims 1 , 2 or 3 including the step of identifying the subscriber from CLI data included in the call to the recipient message number,

5. A method according to claim 4 in which the step of sending a separate message includes the step of retrieving the recipient number using the received CLI data, and using the recipient number to send the separate message.

6. A method according to claim 5 in which the step of storing the recorded message includes the step of storing the recipient number with the recorded message.

7. A method according to any preceding claim in which the recipient pick-up number is dynamically allocated to the recorded message.

8. A method according to any of claims 1 to 7 in which the step of storing the recorded message includes storing a file number for the recorded message and the recipient pick-up number for the recorded message.

9. A method according to any preceding claim including the step of deleting the recorded message after a predetermined period of time.

10. A method for retrieving messages stored in accordance with the method of any preceding claim comprising the steps of receiving a call to a recipient pick- up number allocated to a stored message, retrieving and playing back the stored message to a person making the call.

11. A method according to claim 10 including the step of comparing CLI data received with the call with a recipient number stored with the message, and playing back the message in dependence on the result of the comparison.

12. A system for sending messages in a telecommunication system comprising: means for allocating to a subscriber a recipient message number for each recipient to whom the subscriber wishes to send messages; means for storing the thus allocated recipient message number with an associated recipient number; means for receiving a call from a subscriber to a recipient message number; means for recording a message provided by a subscriber in the call; means for allocating a recipient pick-up number to the recorded message; means for storing the recorded message; means for sending a separate message to the recipient, the separate message including the recipient pick-up number.

13. A system according to claim 12 in which the message is a voice message.

14. A system according to claim 12 in which the message is a video message.

15. A system according to claim 12, 13, or 14 including means to identify the subscriber from CLI data included in the call to the recipient message number.

16. A system according to claim 15 including means for retrieving the recipient number using the received CLI data.

17. A system according to claim 16 in which the means for storing the recorde 5dd mmeessssaaggee also stores the recipient number with the recorded message.

18. A system according to any of claims 12 to 17 in which the means for allocating a recipient pick-up number to the recorded message dynamically allocates the recipient pick-up number.

19. A system according to claim 17 in which the means for storing the recipient number also stores a file number for the recorded message and the recipient pick-up number for the recorded message.

20. A system according to any of claims 12 to 19 including means for deleting the recorded message after a predetermined period of time.

21. A system for retrieving messages stored by the system of any of claims 12 to 20 comprising means for receiving a call to a recipient pick-up number allocated to a stored message and means for retrieving and playing back the stored message to a person making the call.

22. A system according to claim 21 including means for comparing CLI data received with the call with a recipient number stored with the message, and wherein the means for playing back the message does so in dependence on the result of the comparison.

23. Method for sending messages in a telecommunication system comprising the steps of transmitting from a mobile communication device to a mobile communication network, a request for a recipient message number for a recipient, receiving a recipient message number from the communication network, and storing the recipient message number in the mobile communication device, and subsequently using the stored recipient message number to send messages to that recipient.

24. A mobile communication device comprising means to send a request for a message number for a recipient to a mobile communication network, means for receiving a recipient message number from the communication network, means for storing the recipient message number in the mobile communication device, wherein the recipient message number may subsequently be used to send messages for the recipient from the mobile communication device.

25. A method for allocating a recipient message number in a mobile communication network comprising the step of receiving a request from a mobile communication device for a recipient message number, allocating a recipient message number to a recipient identified in the request, transmitting the recipient message number to the mobile communication device that issued the request, storing the recipient message number with the recipient address, storing any messages addressed to the recipient message number, and using the recipient address to notify the recipient of any received messages.

26. Apparatus for allocating a recipient message number in a mobile communication network comprising means for receiving a request from a mobile communication device for a recipient message number, means for allocating a recipient message number to a recipient identified in the request, means for transmitting the recipient message number to the mobile communication device that issued the request, means for storing the recipient message number with a recipient address, means for storing any messages that are addressed to the recipient message number, and means for using the stored recipient address to notify the recipient of any received messages.