WO2009090360A1

WO2009090360A1 - Text message processing service for message originators

Info

Publication number: WO2009090360A1
Application number: PCT/GB2008/004159
Authority: WO
Inventors: Jeffrey Wilson
Original assignee: Intellprop Limited
Priority date: 2008-01-18
Filing date: 2008-12-17
Publication date: 2009-07-23
Also published as: GB0800978D0; GB2457430A

Abstract

A method of providing a text message processing service, e.g. automatic archiving of sent messages, for originators of text messages in a telecommunications network, e.g. a network conforming to the GSM standard, is described. The method comprises receiving a text message in a mobile originated (MO) format from an originator terminal at an SMSC or SMS Router in the network. The text message includes both an indication of the identity of the originator terminal and an indication of an identity of an intended recipient terminal. The message is converted by the SMSC / SMS Router from the MO format to a mobile terminated (MT) format suitable for onward delivery to the intended recipient terminal. Depending on the identity of the message originator, the MT format message is routed to a service apparatus to process the text message to provide the text message processing service. The MT format message may be delivered to the recipient terminal by the service apparatus.

Description

TITLE OF THE INVENTION

TEXT MESSAGE PROCESSING SERVICE FOR MESSAGE ORIGINATORS

BACKGROUND ART

The invention relates to telecommunications services apparatus and methods for use with a mobile telecommunications system such as a mobile telephone system, and more particularly to the provision of text messaging services. Embodiments of the invention are applicable to the GSM (Global System for Mobile Communications) mobile telephony system and other types of mobile telephone network.

A network architecture for the SMS (Short Messaging Service) has been defined by the GSM specifications, which are now managed by the 3GPP (3rd Generation Partnership Project) organisation (www.3GPP.org). The specifications define two Short Message teleservices known as MO (mobile originated) and MT (mobile terminated). MO messages are sent from a Short Message Entity (SME) such as a mobile telephone handset and delivered in the first instance via a Short Message Service Interworking Mobile Switching Centre (SMS-IWMSC) to a Short Message Service Centre (SC). The SC then attempts delivery, retrying as necessary until delivery is successful or the message expires, via a Short Message Service Gateway Mobile Switching Centre (SMS-GMSC). The SMS-GMSC looks up, in a Home Location Register (HLR) of the destination network, the current network node address (associated with a Visited Mobile Switching Centre (VMSC)) and the International Mobile Subscriber Identity (IMSI) of the destination MSISDN (Mobile Subscriber Integrated Services Digital Network) number. The message in MT format is then delivered to the identified network node address. The combination of SMS-IWMSC, SC and SMS-GMSC are generally implemented as an integrated entity, which is widely known in the industry simply as an SMSC. However, the conversion from MO to MT format is now commonly performed by dedicated SMS Routers, and the term MO to MT entity (or MO to MT converter entity) will be used here to refer generally to any device performing this function in a network (i.e. the term encompasses SMSCs and SMS routers). In accordance with conventional telecommunication standards, e.g. the GSM standard, MO and MT format messages are different: the MO leg identifies the intended final destination by MSISDN, whereas the MT leg identifies it by IMSI. The MO leg is delivered to the sender's home SMSC (or other MO to MT entity as appropriate) as specified in the MO SMS message from the sender's SME (sender / originator terminal), while the MT leg is delivered to a VMSC identified by the network node address looked up in the HLR. From the VMSC it is delivered to the destination SME (recipient / destination terminal), e.g. a recipient's mobile telephone handset. Important consequences of the type of architecture defined by the 3GPP

Specifications are that —

■ MO messages are delivered via an MO to MT entity in the sender's home network, even when the sender is roaming

■ MT messages are sent directly from the MO to MT entity to a network node (VMSC) where the destination subscriber is located, which may be on the same or on another network.

The effect of this routing model is that supplementary SMS services and other service enhancements, e.g. automatic copying / archiving of SMS messages, have been difficult to implement. For MO messages, some networks have implemented SMS load sharing amongst several SMSCs, while some networks have implemented SMS Grooming (i.e. segregation of SMS messages for separate routing according to message characteristics). This has been achieved by insertion of SMS Routers into the network architecture in front of SMSCs, and in some cases replacing SMSCs. However the implementation of such an SMS Router layer has often only been justifiable as part of a major architectural overhaul in a network, for example to improve delivery times or capacity. The introduction of supplementary services to enhance the service experience of a Short Message sender (i.e. services based on the MO leg of an SMS message) has often not been sufficient justification on its own. Consequently such SMS Router implemented originator services have only been possible in networks that have introduced an SMS Routing layer for other more fundamental reasons, e.g. for capacity management

Accordingly, there is a need for apparatus and methods which allow SMS services associated with MO messages to be introduced while requiring less modification to existing network architectures than current solutions.

SUMMARY OF THE INVENTION

According to a first aspect of the invention there is provided a method of providing a text message processing service for originators of text messages in a telecommunications network, the method comprising: receiving a text message in a mobile originated (MO) format from an originator terminal, wherein the text message includes an indication of the identity of the originator terminal and an indication of an identity of an intended recipient terminal for the text message; converting the text message from the MO format to a mobile terminated (MT) format suitable for onward delivery to the intended recipient terminal; and routing the MT format message to a service apparatus for processing in dependence on the identity of the originator terminal to provide the text message processing service for the originator of the text message.

Thus a scheme for intercepting and processing a text message to provide additional services for an originator of the message during the MT leg of a message transit through the network (which may be thought of as the delivery leg for the message), instead of during the MO leg (which may be thought of as the submission leg for the message), as is conventionally done, is provided. This allows services, such as automatic archiving of sent messages to a storage medium coupled to the network, or automatic forwarding of messages to an email account, to be applied without requiring an overhaul of those components of the network architecture responsible for receiving MO format messages and converting them to MT format (e.g. SMSCs and / or SMS Routers). This is beneficial because modifications to these parts of a network can be significantly more difficult to implement, and more costly, than modifications to the network architecture for dealing with MT format messages.

Both the nature of the processing performed on the MT format text message, and / or the decision to route the MT format text message to the service apparatus may be determined in dependence on the identity of the originator terminal. For example, in one case all MT text messages may be routed to the service apparatus regardless of the identity of the originator terminal, and the processing applied to each message may then be made in dependence on the identity of the originator terminal, e.g. archiving to a data store specific to the originator terminal. In other cases, only a subset of MT text messages traversing the network may be routed to the service apparatus depending on the identity of the originator terminal. For example, only MT text messages associated with originator terminals that are subscribed to additional / enhanced originator-based text message services may be routed to the service apparatus based on the identity of the originator terminal. The processing applied to each message at the service apparatus may then be the same for each MT message received, or may also be made in dependence on the identity of the originator terminal.

The MT format message may be sent for onward delivery to the intended message recipient once it has passed through the service apparatus. Onward delivery may, for example, by instigated by the service apparatus sending the message in MT format for onward routing.

The step of converting the text message from the MO format to the MT format may include generating a first routing information query which is intended to obtain routing information for the recipient terminal from a Home Location Register (HLR) of a telecommunications network of the recipient terminal, e.g. an SRI SM request / query in the GSM standard, where the routing information query includes an indication of the identity of the originator terminal, e.g. an SM RP SMEA field in the GSM standard, and wherein the method comprises determining the identity of the originator terminal from the indication in the routing information query, and providing routing information for the service apparatus instead of routing information for the intended recipient terminal in response to the routing information query in dependence on the determined identity of the originator terminal, thereby causing the MT format message to be routed to the service apparatus for the processing to provide the text message processing service for the originator of the text message.

This approach of providing what might be thought of as a "faked" response to an otherwise conventional routing information query for messages identified as targets for the text message processing service provided by the service apparatus based on the identity of the message originator provides one way of ensuring messages are routed through the service apparatus as required, but without needing the entity in the network responsible for MO to MT conversion to be modified. The method may further comprise the service apparatus sending a second routing information query, e.g. another SRI SM, to the HLR to obtain routing information for the recipient terminal, and receiving a response from the HLR containing the routing information for the recipient terminal which may be used for forwarding the MT format message for onward delivery to the intended message recipient after it has passed through the service apparatus. In the event the originator terminal and the recipient terminal are on the same telecommunications network, in some embodiments the first routing information query may be received at the HLR, the HLR may determine the identity of the originator terminal from the indication in the routing information query, and the HLR may then respond to the routing information query by providing the routing information for the service apparatus instead of routing information for the intended recipient terminal in dependence on the determined identity.

In other embodiments in which the originator terminal and the recipient terminal are on the same telecommunications network, the first routing information query may be received at the HLR, and the HLR may determine the identity of the originator terminal from the corresponding indication in the routing information query. If the HLR determines that the originator terminal is associated with a subscriber who receives a service provided by the service apparatus, the HLR may forward the routing information query to the service apparatus, and the service apparatus may then respond to the routing information query by providing routing information for the service apparatus, instead of routing information for the intended recipient terminal.

In the event the originator terminal and the recipient terminal are on different telecommunications networks, the first routing information query may be intercepted before it is received at the HLR of the recipient terminal's network, i.e. while the routing information query is still under the control of the originator terminal's network. The routing information query may then be diverted away from the HLR and delivered instead to the service apparatus, and the service apparatus may then respond to the routing information query by providing routing information for the service apparatus instead of routing information for the intended recipient terminal in dependence on the identity of the originator a determined from the indication in the first routing information query. The method may further comprise processing the text message in dependence on the identity of the recipient terminal to provide a text message processing service for the recipient of the text message. Thus services may be provided for both originators and recipients of text messages. Processing the text message in dependence on the identity of the recipient terminal to provide a text message processing service for the recipient of the text message may also be performed by the service apparatus.

The text message processing service may comprise at least one of: archiving of text messages sent from the originator terminal in a storage element coupled to the service apparatus, forwarding of text messages sent from the originator terminal to an email gateway for delivery to an email address associated with the originator terminal, modifying or withholding a CLI (calling line identification) associated with the originator terminal, forwarding the text message to a group of multiple recipient terminals, converting the message to the so-called "flash" format for direct display on a screen of the recipient terminal. Services corresponding to those described in EP 1 474 934 [1] for text message recipients may also be provided for text message originators in accordance with embodiments of the inventions.

According to another aspect of the invention there is provided a system for providing a text message processing service for originators of text messages in a telecommunications network, the system comprising an MO to MT converter and a service apparatus, wherein the system is configured such that the MO to MT converter entity is operable to receive a text message in a mobile originated (MO) format from an originator terminal, the text message including an indication of the identity of the originator terminal and an indication of an identity of an intended recipient terminal for the text message, to convert the text message from the MO format to a mobile terminated (MT) format suitable for onward delivery to the intended recipient terminal, and to route the MT format message to the service apparatus for processing in dependence on the identity of the originator terminal so as to provide the text message processing service for the originator of the text message. BREEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the invention and to show how the same may be carried into effect reference is now made by way of example to the accompanying drawings in which: Figure 1 schematically shows a network architecture for providing services to

SMS message recipients;

Figure 2 schematically shows a network architecture for providing services to SMS message originators according to an embodiment of the invention;

Figure 3 schematically shows a network architecture for providing services to SMS message originators and recipients according to an embodiment of the invention;

Figure 4 schematically shows a network architecture for providing services to SMS message originators according to an embodiment of the invention in which the recipient of the message is on a different network to the message originator;

Figure 5 schematically shows an overview of a network architecture for providing services to SMS message originators according to an embodiment of the invention;

Figure 6 is a ladder diagram schematically showing a signalling process for providing services to SMS message originators according to an embodiment of the invention; and Figure 7 is a ladder diagram schematically showing a signalling process for providing services to SMS message originators according to an embodiment of the invention in which the recipient of the message is on a different network to the sending party. DETAILED DESCRIPTION

To assist in understanding embodiments of the invention which provide for the introduction of SMS services associated with MO SMS messages (i.e. services which may be seen as applying to senders of SMS messages), an overview of how SMS services associated with MT SMS messages (i.e. services which may be seen as applying to recipients of SMS messages) can be provided is first described.

For MT messages (as opposed to MO messages) there is a different problem impeding the introduction of services that benefit the recipient of the message (as opposed to the sender / originator of the message). This is caused by the legacy architecture of SMS, as described above, which delivers the MT messages directly from an MO to MT entity (e.g., SMSC or SMS Router, for example) to a destination network node in any network. The problem is that the MT message passes directly to the VMSC where the destination subscriber is located without passing through any central point in the receiving subscriber's home network where supplementary services equipment might conveniently be implemented. Furthermore, if the destination subscriber is roaming, then the MT message may never even touch the subscriber's home network at all. In this case it is all but impossible for the home network provider to apply additional services to SMS messages received by their subscriber as the network provider might never even know that the message existed. To alleviate this problem and permit the recipient's home network to have control over the messages being delivered to its subscribers, e.g., for regulatory, supplementary service, spam prevention or other reasons, Intellprop Limited introduced what is now known in the industry as SMS Home Routing. The principles of SMS Home Routing are described in EP 1 474 934 [1], which is hereby incorporated in full by reference. The Home Routing architecture is based on modifying the network node address given by an HLR in response to a conventional HLR query (conventionally known as an SRI_SM query) from an MO to MT entity. Instead of giving the appropriate network node address for the recipient of the message (i.e. the VMSC to which the recipient is currently associated), the SRI_SM response (either from the HLR or from an add-on apparatus) is arranged to return instead the address of a service apparatus within the home network of the message recipient. The service apparatus may be referred to as an SMS Advanced Service Node for MT services (ASN MT ), and may comprise an SMS Router. This causes the MO to MT entity to deliver the MT message to the ASN MT in the home network of the destination subscriber. Thus, the MT message is forced to pass through an apparatus in the recipient's home network, at which stage the additional service(s) may be applied as appropriate (e.g. automated archiving, forwarding to another destination, etc.), before onward delivery of the message to recipient. The ASN MT may perform an HLR lookup itself to determine the VMSC of the recipient and route the MT message accordingly for delivery to the recipient. In situations where MT services are provided, services may be activated for selected subscribers only, for example those who pay a fee for the enhanced MT services. The HLR may readily determine in each case whether the intended recipient is a subscriber of additional services, e.g. though a database look-up, and if so to cause the address of the ASN MT to be supplied to the MO to MT entity in response to the SRI SM query, for example, either by forwarding the SRI SM message to an SMS Router, or by responding to the SRI SM message itself. (The SMS Routing Layer approach for MO messages requires that every MO message is examined, and therefore the SMS Routing layer must carry the entire network's MO message capacity.) Thus as described above, the existing MT services scheme using SMS Home

Routing as described in EP 1 474 934 [1] changes the network node address in the response to an HLR query (e.g., a Send Routing Information for Short Message (SRI_SM) query) relating to the destination MSISDN. This is normally achieved by using an HLR modification that forwards affected SRI_SM messages to the ASN, which will respond to the SRI_SM on behalf of the HLR by sending its own address back to the MO to MT entity that sent the SRI SM request to the HLR in the first instance. That is to say the process of replying to the SRI SM with a modified address pointing to the ASN MT is normally performed by the ASN MT itself after it has received the forwarded SRI SM from the modified HLR, as opposed to the HLR itself sending the modified response. This simply a matter of the detailed implementation and is not significant to the underlying principle. Other methods are possible as described in EP 1 474 934 [I].

Figure 1 schematically shows the routing of an SMS message in accordance with a preferred embodiment of the SMS Home Routing scheme described above for providing MT services. Referring to Figure 1, an MO message 20 from a sender's SME (e.g. a terminal such as a telephone handset) is received at the sender's SMSC 6 as normal. Here it is assumed that the sender and recipient are on the same network so the SMSC 6 is on the recipient's home network. The SMSC sends an SRI SM query 21 to the home network ("on net") HLR 7. The HLR 7 identifies the SRI_SM as being associated with a subscriber having additional MT services and accordingly forwards the SRI SM request to the ASN MT 18 to deal with, shown schematically in Figure 1 by arrow 22. The ASN MT 18 responds to the SRI_SM query by sending an SRI SM response 25. The SRI_SM response 25 is modified from what would conventionally be sent by the HLR. The SRI_SM response is modified to have a destination network node address that points to the ASN MT 18 in the recipient's home network that will implement the MT service(s), instead of pointing to the recipient's Visitor Location Register (VLR). This modified HLR behaviour, resulting in network node address substitution, is typically performed for a subset of subscribers to the network, typically those who are subscribed to MT services such as copy to email, or SMS forwarding, though it could be applied to all subscribers for example for the purposes of spam prevention, regulatory requirements or other reasons. The IMSI field in the SRI SM response 25 from the ASN MT is also populated differently from that in a standard HLR response. The IMSI field is used to carry either the destination subscriber's MSISDN, or a correlation value / indicator that can be used by the ASN MT to later retrieve stored data relating to the HLR query to allow the SMS message to be properly delivered to the intended recipient once the ASN MT has finished processing the message.

While the above has described the case of the SMS sender and recipient being on the same network, the sender may equally be on a different network (off-net). Here the originator's MO SMS message would be received at an off-net SMSC (e.g. SMSC 6B in Figure 1), with an SRI SM query 22 and an SRI SM response 25B going from / to this off-net SMSC 6B.

On receiving the SRI_SM response 25, the SMSC 6 (or SMSC 6B if the sender is "off-net") sends the message 27 (duly converted from MO to MT form) to the network node address specified in the SRI SM response 25, which here is the address of the ASN MT 18. The MT message 27 includes in its IMSI field either the destination subscriber's MSISDN, or the correlation value / indicator supplied by the ASN MT in the IMSI field of the initial SRI_SM response 25.

The MT message 27 is thus routed through the ASN MT 18 which may then perform any MT service(s) as required on the message. To subsequently deliver the message, the ASN MT 18 performs an HLR lookup to the destination subscriber's

HLR 7 using the original destination MSISDN (as extracted from the IMSI field of the

MT message 27, or through a look-up based on the correlation value / indicator inserted into the IMSI field of the SRI_SM response 25 by the ASN MT when it responded to the SRI SM query 21 on behalf of the HLR 7.

The HLR 7 is configured so that when receiving an SRI_SM query (HLR lookup query) from the ASN MT 18 (as opposed to from an SMSC), it does not forward the SRI_SM message to the ASN MT, but instead responds to it in the normal way, Le. by providing the network node address where the recipient is located. The ASN MT 18 then performs a standard MT message delivery 28.

The present inventor has realised that an MT SMS Home Routing solution of the kind schematically shown in Figure 1 may be modified in order to also support originator services applied to selected (or all) subscribers sending SMS messages, without the need to insert in-line SMS Routers or other equipment in the MO message path (i.e. between a Mobile Switching Centre (MSC) and an SMSC in a 3GPP traditional architecture). This provides significant benefits for networks that wish to implement originator services (i.e. services applied for senders of SMS messages, which may be referred to as MO services) without installing a complete SMS Routing layer. Embodiments of the invention may nonetheless also be applied to networks that do include an SMS Routing layer as an alternative means of providing for MO services. Originator services refer to those supplementary services that a network may provide for its own subscribers when they originate messages. In contrast to MT services provided for a message recipient, where messages are subjected to supplementary processing according to settings configured for the destination MSISDN, in accordance with embodiments of the invention, originator services process messages according to settings configured for the originator's MSISDN. Examples of originator services (MO services) include copying all sent messages to an archive and / or an email address associated with the sending SME, the provision of group lists in the network for sending to multiple destinations, modifying or withholding a CLI (calling line identification) associated with the originator terminal, and / or converting the message to the so-called "flash" format for direct display on a screen of the recipient terminal, for example. As described above, in accordance with conventional telecommunications standards, MO messages automatically pass through the MO infrastructure of a sending subscriber's home network, even if the subscriber is roaming. It is desired to capture / intercept these messages before they reach their destination so that the subscribed services may be implemented.

However, and importantly, the inventor has realised that it is not necessary to implement the originator services while the message is transiting the MO leg of its journey. The inventor has appreciated the surprising result that it is possible to apply MO services to an SMS message while the message is transiting the MT leg, i.e. after it has passed through a conventional MO to MT entity in the sender's network. Previously originator service processing has only been possible in the MO leg of the SMS routing through the use of an SMS Routing layer in the MO leg.

Figure 2 schematically shows a scheme for providing MO service in a telecommunications network in accordance with an embodiment of the invention. In particular, Figure 2 shows an embodiment in which the originator of a message and the recipient of the message are subscribers of the same network. Elements of Figure 2 which are similar to and will be understood from corresponding elements of Figure 1 are identified by the same reference numeral. Likewise, some features of embodiments of the invention find parallels in, and so their understanding will be assisted by, the above-described schemes for providing MT services. Referring to Figure 2, it is disclosed that originator services (MO services) may be implemented using equipment referred to here as an SMS Advanced Services Node for MO Services (ASN MO) 38. (In practice the ASN MO 38 may be a general purpose computer programmed to provide the functionality required of the ASN MO for the various embodiments described herein.) To some extent the ASN MO 38 for MO services in Figure 2 may be seen in some ways as being analogous to the ASN MT 18 for MT services shown in Figure 1. Embodiments of the invention allow for the ASN MO to be added to a mobile network to provide MO services without requiring any infrastructure changes to the MO to MT entities (e.g. SMSCs or SMS Routers) already present in the network. This allows for much simpler introduction into an existing network when compared to the currently used SMS Router approach for providing MO services.

Thus as shown in Figure 2, an MO message 20 from a sender's SME (e.g. a terminal such as a telephone handset) is received at the sender's SMSC 6 as normal. In this example the sender's home network will be referred to as network A. (As noted above, it is assumed in this example that the sender and the recipient are on the same network.) The SMSC 6 thus sends an SRI SM query 21 to the HLR 7 of network A (because the recipient is "on net").

Conventional telecommunication network standards, such as the GSM standard, provide for a field in an SRI SM query (or equivalent) in which an indication of the MSISDN of a sending SME may be included, and so passed to the

HLR. In the GSM standard this is an optional field known as the SM-RP-SMEA field.

In accordance with the embodiment of the invention shown in Figure 2, this field is populated with an indication of the sending subscriber's MSISDN. Although the SM- RP-SMEA field of the SRI_SM query is optional, it has been specified for many years and is intended to support HLR filtering of messages by originator number, for example for the purposes of barring. If a network's SMS-GMSCs do not presently populate this field, it would be straightforward to enable its use by a configuration change. Such configuration changes would only be required within network A (i.e. the network of the sender), because MO messages from network A's subscribers always pass through network A' s infrastructure. Subscribers of network A who have subscribed to a given MO service are listed in an MO services database to which the HLR has access. On receipt of the SRI SM request (with properly populated SM-RP-SMEA field) from the SMSC 6, in accordance with embodiments of the invention, the "on-net" HLR 7 is configured to check whether or not the sending subscriber has subscribed to one or more of the MO services offered by the network. This is done by extracting the sending subscriber's MSISDN (or indication of the MSISDN) from the SM-RP-SMEA field of the SRI_SM query, and comparing this with entries in the MO services database. If the sending subscriber is not associated with any additional services, the HLR responds to the SRI SM query as normal with the message then being delivered in MT format by the SMSC 6 in the usual way.

However, if the HLR 7 identifies the SRI SM query as being associated with a sending subscriber having additional MO services based on the indication of the sending subscriber's MSISDN in the SM-RP-SMEA field of the SRI_SM query, the HLR 7 is configured to forward the SRI_SM request to the ASN MO 38 to deal with. This is shown schematically in Figure 2 by arrow 32. The ASN MO 38 responds to the SRI SM query by sending an SRI SM response 35. The SRI_SM response 35 is modified from what would conventionally be sent by the HLR 7. The SRI SM response 35 from the ASN MO 38 is modified to have a destination network node address that points to the ASN MO 38, instead of pointing to the recipient's Visitor Location Register (VLR). The IMSI field in the SRI_SM response 35 from the ASN MO is also populated differently from that in a standard HLR response. The IMSI field is used to carry either a representation of the destination subscriber's MSISDN, or a correlation value / indicator that can be used by the ASN MO to later retrieve stored data relating to the HLR query to allow the SMS message to be properly delivered to the intended recipient once the ASN MO has finished processing the message.

On receiving the SRI SM response 35 from the ASN MO 38, the SMSC 6 sends the message 27 (duly converted from MO to MT form) to the network node address specified in the SRI_SM response 35, which here is the address of the ASN MO 38. The MT message 27 sent to the ASN MO 38 by the SMSC 6 includes in its

IMSI field either the destination subscriber's MSISDN, or the correlation value / indicator supplied by the ASN MO 38 in the IMSI field of the SRI SM response 35 sent to the SMSC 6.

The MT leg of the message from the sender is thus routed through the ASN MO 18. The ASN MO 18 may then perform any MO service(s) as required, e.g. archiving, sending to email, on the message. To subsequently deliver the message, the ASN MO 18 performs an HLR lookup to the HLR 7 using the destination MSISDN (as extracted from the IMSI field of the MT message 27, or through a look-up based on the correlation value / indicator inserted into the IMSI field of the SRI_SM response 35 by the ASN MO when it responded to the SRI_SM query 21 on behalf of the HLR 7. The HLR 7 is configured so that when receiving an SRI_SM query (HLR look-up query) from the ASN MO 18 (as opposed to from an SMSC), it does not forward the SRI SM message to the ASN MO 38, but instead responds to the SRI SM query in the normal way, i.e. by providing the network node address where the recipient is located. The ASN MO 18 may then perform a standard MT message delivery 28. Thus the approach of providing MO services in accordance with embodiments of the present invention is based on arranging for modified responses to certain SRI SM messages to be returned to the SMSCs 6, thereby causing the subsequent associated MT messages 27 to be delivered in the first instance to the ASN MO 38, permitting originator services to be carried out on these messages. In contrast to the above described case of providing MT services as shown in

Figure 1, different approaches may be employed for providing MO services in dependence on whether the recipient is in the same network as the subscriber. For example, two cases may be distinguished for originator services as follows:

Case 1: The originator (sender) and recipient (destination) are both subscribers of the same network, e.g. network A, as shown in Figure 2. Here the HLR query 21 shown goes to an HLR 7 in network A. This case would also apply in a

Virtual Private Networking (VPN) situation where a group of users, for example at a company, are all subscribers of network A.

Case 2: The originator (sender) is a subscriber of network A, but the recipient (destination) is a subscriber of a different network, say network B. This situation is different because now so that the HLR query from the sender's SMSC is addressed to an HLR in another network over which the network provider for A may have no control. Even if network B provided its own MO services and so had its own suitably modified HLR, although technically possible, it is unlikely there would be an agreement for network B to redirect messages back to an ASN MO in network A. Accordingly, an alternative approach may be preferred in handle the case that the recipient is "off net".

The recipient "on-net" case and the recipient "off-nef ' case differ in the ways that the conventional SRI SM query from the SMSC may be captured in order that a modified response may be sent. Case 1 for originator services, as shown in Figure 2, is in some ways similar to the MT services case, since the HLR 7 is on-net. Case 2 is different because the HLR is off-net, but the SRI SM query messages would still be generated on-net because the originator is a subscriber of network A and so the SRI SM is generated by the SMSC of his network.

The modified response to the SRI SM query in the case the recipient is on the same network (Case 1) may be implemented in various ways, for example:

■ the HLR being configured to forward the SRI SM query unprocessed to a suitably configured apparatus which sends the modified response (as schematically shown in Figure 2)

■ the SRI SM being intercepted by a suitably configured apparatus placed in the path of the SRI_SM query from the SMSC to the HLR which sends the modified response

■ the HLR itself being programmed to send a modified response.

A key difference between the preferred ASN MO operation for case 1, as shown in Figure 2, and ASN MT operation as shown in Figure 1, lies in the HLR modification. In the MO case, the HLR uses the originator address rather than the recipient address to determine whether to forward or process the SRI SM query message or to treat it normally. As a result of the modified SRI_SM response, messages sent by an originator subscribed to originator services will be directed to the ASN MO in network A. If both MO and MT services are implemented simultaneously in network A, as might preferably be the case, then messages for which either the originator or the recipient is subscribed to supplementary services may be directed to a combined ASN MT (MO + MT ) in network A. Figure 3 schematically represents an example of this implementation. Elements of Figure 3 which are similar to and will be understood from corresponding elements of Figures 1 and 2 are identified by the same reference numerals. However, in Figure 3 a combined Advanced Service Node (ASN) 50 provides the respective functionalities of the ASN MT 18 shown in Figure 1 and the ASN MO 38 shown in Figure 2. The combined ASN 50 may be configured to compare the MSISDN and the SM RP SMEA specified in the SRI_SM query with respective databases of subscribers for MT and MO services respectively to determined whether MT or MO services, or both, should be applied to the MT message 27 that will be received from the SMSC 6 in due course.

Thus embodiments of the present invention can provide MT services and also originator services but applied in the MT message path, so that the same SMS

Advanced Services Node can be used for achieving both originator and MT services.

Techniques for implementing the signalling for originator services can also be applied to MT services. For example, the routing of SRI_SM query messages to the ASN MT can be achieved in a number of ways that have been discussed above for the originator services case and the ASN MO. The techniques thus may also be applied to MT services and the ASN MT case; implementation for MT services is thus not restricted to those techniques disclosed in EP 1 474 934 [I].

Naturally it would be possible to implement the present invention solely for originator services, or to have separate ASN MO nodes 38 for originator services and ASN MT nodes 18 for MT services. However, simplification may be provided when the same SMS Advanced Services Node (or nodes) is used for both types of service.

In implementations of MT services according to EP 1 474 934 [1], the mandatory 'MSISDN' field of the SRI SM query message, containing the recipient's

MSISDN, may be used as the key for deciding whether MT services are required. For MO services according to the present invention, the optional 'SM-RP-SMEA' field of the SRI SM message containing the originator's MSISDN may be used as the key for deciding whether originator services are required. If either or both types of service are required, then the network node address and IMSI field substitutions are performed in the SRI_SM response as described in EP 1 474 934 [1], causing the subsequent MT message to be delivered to the ASN MO in network A. Thus embodiments of the invention for handling Case 1 identified above (both originator and recipient are on the same network) can be implemented by the addition of an apparatus configured to perform the above described function of the ASN MO 38 shown in Figure 2, and application of the HLR modification described above. Thus MO services may provided without change to SMSC (or other MO to MT entity) operation or configuration.

For case 2 identified above (originator on network A and subscriber on a different network B), there are several possible methods by which the initial SRI SM query from the SMSC of the sender's network to the HLR of the recipient's network may be either captured or intercepted or dispensed with altogether in order that the subsequent MT message from the SMSC may be caused to be sent to an originator services equipment in network A, such as the ASN MO shown in Figure 2. These methods include:

■ Intercepting the SRI SM query message generated by the SMSC within network A before it leaves the network, and redirecting it to an ASN MO similar to that described above with reference to Figure 2. The interception may be achieved either by a physical entity providing an intercept point through which SRI SM query messages are arranged to pass, or by manipulation of routing rules so that all SRI SM query messages are sent directly to an ASN MO for processing, rather than to the appropriate HLR. In this case, if the ASN MO identifies the SRI_SM query as being associated with a sender subscribed to one or more MO services (based on comparison of the SM RP SMEA of the SRI_SM query with an MO service subscriber database), it may send a response directly to the SMSC in line with that described above with reference to Figure 2, i.e., without involving the HLR. If, on the other hand, the ASN MO identifies the SRI_SM query as not being associated with a sender subscribed to any MO services, it may simply forward the SRI SM to the appropriate HLR for the recipient. Depending on whether the network is able to separate SRI_SM query messages from other HLR-addressed messages, this method may result in a significant amount of signalling traffic being routed through the intercept point and / or the ASN MO. It will also be important to avoid circular routing when the ASN MO subsequently generates a "normal" SRI SM for onward routing the MT message to the final destination SME (i.e. SRI SM queries from the ASN MO should not be intercepted and returned back to it.)

■ Modifying the configuration of the MO to MT entity in such a way that SRI SM messages that it generates are routed directly to the ASN MO in network A rather than the appropriate HLR for the recipient. The SMS services equipment may then be programmed to respond to the SRI SM messages with a modified response as described above with reference to Figure 2 so that the subsequent associated MT message sent by the SMSC when it has received a response to the SRI_SM query arrives at the ASN MO. Although this approach does require a configuration change to the MO to MT entity, it has the advantage that the configuration will in many cases be changeable by the network operator without recourse to the MO to MT entity vendor for software changes.

■ Modifying a signalling parameter, e.g. the translation type of the SRI SM query generated by the MO to MT entity in such a way that the signalling routing in network A can be configured to route these SRJ SM messages via the ASN MO in network A. The SMS services equipment may then be programmed to respond to the SRI_SM messages with a modified response as described above with reference to Figure 2 so that the subsequent associated MT message sent by the SMSC when it has received a response to the SRI_SM query arrives at the ASN MO.

■ Modifying the MO to MT entity in network A that would generate the SRI_SM for the destination number so that it does not automatically generate it.

Instead this node may be programmed to do an HLR lookup, preferably an SRI SM query, on the originator's number in network A's own HLR to determine if the subscriber has subscribed to originator services. MT messages that have originators who are subscribed to originator services may then be sent directly to a known address of the SMS services equipment (ASN MO) in network A that provides these services. For these messages, the MO to MT entity's SRI SM query on the destination number and its response are skipped, saving signalling network bandwidth. In order to pass the destination MSISDN to the MO services equipment (so that the MO services equipment can send an appropriately configured SRI SM query to determine the location of the recipient of the message), the IMSI field in these MT messages is preferably populated with a representation of the destination MSISDN, for example encoded in IMSI format. Messages that do not have originators with an advanced services subscription are delivered normally by the MO to MT entity, while for those messages delivered to the SMS MO services equipment, an SRI SM on the destination number is carried out by the SMS MO services equipment followed by a normal onward delivery.

■ Modifying the MO to MT entity in network A that would generate the SRI SM for the destination number so that it does not generate it. Instead this node is programmed to send all MT messages directly to a known address of the SMS services equipment (ASN MO) in network A that provides these services. The SMS services equipment then does a lookup in the originator's HLR in network A to determine if the subscriber has originator services. It then provides these services if required, and then onward delivers the message in the normal way.

The first of the above described alternatives for providing MO services where the sender and recipient are on different networks (i.e. the interception point / change of routing rules scheme) may be preferred in some cases because it involves no changes to the MO to MT entities (e.g. the SMSC infrastructure). Figure 4 schematically shows a network architecture for implementing this scheme for MO service provision. Elements of Figure 4 which are similar to and will be understood from Figures 1 to 3 are indicated by the same reference numerals. As shown in Figure 4, an MO message 20 from a sender's SME (e.g. a telephone handset) is received at the sender's SMSC 6 as normal. In this example the sender and the recipient are on different networks. The SMSC 6 thus generates an SRI_SM query 21 to the HLR 7B of the recipient's network (because the recipient is "off net").

The network in Figure 4 is configured so that the SRI_SM query from the SMSC 6 is routed through an intercept apparatus 19. This identifies from the SRI_SM query (in particular from the SM RP SMEA, e.g. as described above through a database lookup) whether or not the sender of the SMS is a subscriber of MO services for the network. If not, the SRI SM query is routed as normal to the HLR 7B and message routing continues as normal. If the message sender is a subscriber of MO services, however, the message is routed to an ASN MO 38 which may be similar to that shown in Figure 2. Message processing may then continue as in Figure 2. The network may be configured so that a subsequent SRI SM query from the ASN MO 38 is routed directly through, or bypasses, the intercept apparatus 19 to avoid circular signalling.

The functionality of the intercept apparatus may be provided by an appropriately programmed general purpose computer, for example.

Thus some of the above-described schemes for providing MO services operate by using a modified SRI_SM response to route the MT message from an MO to an MT entity to an SMS Advanced Services Node configured to provide a service, while some other methods avoid the SRI_SM query step from the SMSC and route MT message directly from the SMSC to a known address for the SMS Advanced Services Node. Other methods are possible.

Throughout this description, the term SMSC is used to indicate the MO to MT entity that converts MO messages to MT format and is responsible for normal MT message delivery unless the context demands otherwise. It will be understood that in some networks message format conversion and delivery are performed by SMS Routers in the MO path, either placed in front of or replacing the SMSCs and in these cases the SMS Routers generate SRI_SM routing queries, while in other networks format conversion and delivery may be performed by SMSCs.

By way of an overview, Figure 5 shows some of the network elements in a network configured to provide MO services in accordance with embodiments of the invention. Elements of Figure 5 which are similar to and will be understood from corresponding elements described above are identified by the same reference numerals. Thus Figure 5 shows a sending telephone handset 1 associated with a sending party on a first network A, and a recipient handset 10 associated with a recipient party on a second network B. Handsets 1 is connected to MSC 2 and handsets

10 is connected to MSC 9. Messages sent from handset 1 are routed to SMSC 6 in network A via MSC 2 in the normal way. Interactions between SMSC 6, HLR 7 (which may be "on-net" (networks A and B being the same network) or "off-net" (networks A and B being different networks), and an SMS service node 38 (e.g. ASN MO) proceed as described above to provide MO services for the sending party. For example, here the network includes an email gateway 11 and an MO service offered by the network is the automatic emailing of copies of all SMS messages sent by the sending party to an email address, e.g. for archiving. The message is delivered to recipient handset 10 in MT format from the SMS service node. The SMS service node 38 may comprise one or more SMS Routers, an SMS Service Control Point (SMS SCP) for providing centralised control and intelligence and for providing routing instructions to the SMS Routers, an SMS Service Data Point (SMS SDP) for storing service configuration data, and interfaces to other media such as email, and provide functionality associated with the additional service.

An important feature of some embodiments of the present invention is that an architecture that allows a network to process MT messages in order to provide MT services for its recipients, such as the architecture illustrated in Figure 1, may also be used to provide services for its own subscribers when they are sending messages.

These so-called originator services (or MO services) may be implemented according to embodiments of the invention in the MT message path, i.e. during the delivery stage between the network's SMSC, or other node in the network that is responsible for delivery of MT messages (i.e. MO to MT entity / converter), and the MSC / VLR where the recipient is located.

In the case of originator services, the SMSC 6 or equivalent other node is located in the home network, while the HLR 7 could be in the same network, or in another network.

Figures 6 and 7 schematically show ladder diagrams indicating the signalling associated with the provision of an MO service in the network schematically shown in Figure 5 for a recipient who is "on-net" and "off-net" respectively.

In the first example, shown in Figure 6, the signalling flows are described for a message sent between two subscribers of the same network. The sender is subscribed to an originator service that allows him to copy all his sent messages to an email archive.

The message flow in Figure 6 is in some ways similar to that seen in a network configured to provide MT services. The signalling shown in Figure 6 starts with an MO FSM 50 from MSC 2 to SMSC 6, which is followed by a corresponding return delivery report 51. The SMSC 6 generates an SRI_SM 52 for the HLR 7, as is conventional. A key difference compared to the case of providing MT services is that here the HLR 7 identifies a correspondence between information identifying subscribers of the network who have an originator services option configured and an originator address carried in the SM_RP_SMEA field of the received SRI_SM message 52 (rather than a recipient address carried in the MSISDN field). The HLR acts on recognition of the sending party (A-party) address being that of an originator service subscriber and forwards the SRI_SM message 53 to an SMS Router in the SMS Advanced Services Node 38, which responds to the SMSC 6 on behalf of the HLR. This response contains modified IMSI and network node address fields, which result in the subsequent MT _FSM message 57 being delivered to the SMS Advanced Services Node 38. The Message is then shown as being onward delivered normally, with the SRI SM lookup 54 and 55 and the MT FSM 58. The originator service is depicted as a copy to email operation 61 and 62. Broadly conventional MT_FSM_ACK 60, REPORT_SM_DELIVERY_STATUS 63 and corresponding REPORT_SM_DELΓVΕRY_STATUS_ACK 64 signals are also provided, as indicated in the Figure.

Referring to Figure 7, in the case where the recipient (B-party) is a subscriber of a different network, a different signalling flow is provided, because the SRI SM 72 does not go to an HLR that is under the control of the A-party' s network. Possible approaches include —

1. intercepting the SRI_SM 72 from the on-net SMSC 6 so that it can be processed by the SMS Advanced Services Node 38 in the same way as the forwarded SRI SM 53 in Figure 6. 2. dispensing with the SRI_SM 72 altogether for messages sent by subscribers with originator services, and arranging for the corresponding MT FSMs to be addressed directly to a known address of the SMS Advanced Services Node and preferably to also carry the B-party MSISDN in the IMSI field;

3. dispensing with the SRI SM 72 for all messages, and arranging for all MT _FSMs to be addressed to a known address of the SMS Advanced Services Node and preferably also carrying the B-party MSISDN in the IMSI field.

Figure 7 shows the preferred approach, where the SRI SM 72 is intercepted and routed to the SMS Advanced Services Node 38 or routed to the Advanced Service Node by means of a configuration change to the SMSC 6 (or other MO to MT converter entity). The interception is done for at least those SRI SMs relating to messages addressed to subscribers of other networks, though the method could be used for all SRI SMs generated by the SMSC 6 as an alternative to the special HLR behaviour described in Figure 6. Having received the SRI SM, the SMS Advanced Services Node and the remainder of the message handling process works as described for Figure 6. A further significant feature of the present invention is therefore the method of achieving delivery of an MT message to the SMS Advanced Services Node that would otherwise have been delivered off-net. This can either be achieved by SRI SM interception or by modification of the MT message routing at source in the SMSC.

While embodiments of the invention have been described in terms of physically distinct elements, e.g. an HLR which is separate from the service apparatus for providing the service, it will be appreciated that single elements may be used to provide the functionality of the various functional blocks shown in the figures and described above. For example, single suitably programmed general purpose computer may provide the both the HLR and the service apparatus functionality in some embodiments. Also it will be appreciated that multiple service apparatus providing different services (or a single apparatus operable to provide multiple services) may be deployed in a network. Various ones, or all, of the multiple service may be provided in dependence on the identity of the user in manners broadly similar to those described above in the context of providing a single service. E.g. SRI SM requests from a first service apparatus may be responded to with the address of a second service apparatus to force an MT message from the first service apparatus to be routed through the second service apparatus to provide a second service in dependence on the identity of the originator terminal.

In so far as the embodiments) of the invention described above may be implemented, at least in part, using software controlled processing apparatus, it will be appreciated that a computer program providing such software control and a storage medium by which such a computer program is stored are envisaged as aspects of the invention.

Thus a method of providing a text message processing service, e.g. automatic archiving of sent messages, for originators of text messages in a telecommunications network, e.g. a network conforming to the GSM standard, is described. The method comprises receiving a text message in a mobile originated (MO) format from an originator terminal at an SMSC or SMS Router in the network. The text message includes both an indication of the identity of the originator terminal and an indication of an identity of an intended recipient terminal. The message is converted by the SMSC / SMS Router from the MO format to a mobile terminated (MT) format suitable for onward delivery to the intended recipient terminal. Depending on the identity of the message originator, the MT format message is routed to a service apparatus to process the text message to provide the text message processing service. The MT format message may be delivered to the recipient terminal by the service apparatus.

REFERENCES

[1] EP 1 474 934 [1]

Claims

1. A method of providing a text message processing service for originators of text messages in a telecommunications network, the method comprising: receiving a text message in a mobile originated (MO) format from an originator terminal, wherein the text message includes an indication of the identity of the originator terminal and an indication of an identity of an intended recipient terminal for the text message; converting the text message from the MO format to a mobile terminated (MT) format suitable for onward delivery to the intended recipient terminal; and routing the MT format message to a service apparatus for processing in dependence on the identity of the originator terminal to provide the text message processing service for the originator of the text message.

2. The method of claim 1, further comprising forwarding the MT format message for onward delivery to the intended recipient terminal.

3. The method of claim 1 or 2, wherein the step of converting the text message from the MO format to the MT format includes generating a first routing information query intended to obtain routing information for the recipient terminal from a Home Location Register (HLR) of a telecommunications network of the recipient terminal, wherein the routing information query includes an indication of the identity of the originator terminal, and wherein the method comprises determining the identity of the originator terminal from the indication in the routing information query, and providing routing information for the service apparatus instead of routing information for the intended recipient terminal in response to the routing information query in dependence on the determined identity of the originator terminal, thereby causing the MT format message to be routed to the service apparatus for the processing to provide the text message processing service for the originator of the text message.

4. The method of claim 2 or 3, further comprising the service apparatus sending a second routing information query to the HLR to obtain routing information for the recipient terminal, and receiving a response from the HLR containing the routing information for the recipient terminal to be used in the step of forwarding the MT format message for onward delivery to the intended message recipient.

5. The method of claim 3 or 4, wherein the originator terminal and the recipient terminal are on the same telecommunications network, and the first routing information query is received at the HLR, the HLR determines the identity of the originator terminal from the indication in the routing information query, and the HLR responds to the routing information query by providing routing information for the service apparatus instead of routing information for the intended recipient terminal in dependence on the determined identity.

6. The method of claim 3 or 4, wherein the originator terminal and the recipient terminal are on the same telecommunications network, and wherein the first routing information query is received at the HLR, the HLR determines the identity of the originator terminal from the indication in the routing information query, and the HLR forwards the routing information query to the service apparatus in dependence on the determined identity, and the service apparatus responds to the routing information query by providing routing information for the service apparatus instead of routing information for the intended recipient terminal.

7. The method of claim 3 or 4, wherein the originator terminal and the recipient terminal are on different telecommunications networks, and wherein the first routing information query is intercepted before it is received at the HLR and is routed away from the HLR to the service apparatus, and the service apparatus responds to the routing information query by providing routing information for the service apparatus instead of routing information for the intended recipient terminal in dependence on the identity of the originator a determined from the indication in the first routing information query.

8. The method of any preceding claim, further comprising processing the text message in dependence on the identity of the recipient terminal to provide a text message processing service for the recipient of the text message.

9. The method of claim 8, wherein the processing the text message in dependence on the identity of the recipient terminal to provide a text message processing service for the recipient of the text message is performed by the service apparatus.

10. The method of any preceding claim, wherein the telecommunication network of the originator terminal is a Global System for Mobile Communications (GSM) network, and the step of converting the text message from the MO format to MT format is performed by an MO to MT converter entity conforming to the GSM standard.

11. The method of claim 10, wherein the MO to MT converter entity comprises a Short Message Service Centre (SMSC) or a Short Message Service (SMS) Router

12. The method of any preceding claim, wherein the text message processing service comprises at least one of i) archiving of text messages sent from the originator terminal in a storage element coupled to the service apparatus, and / or ii) forwarding of text messages sent from the originator terminal to an email gateway for delivery to an email address associated with the originator terminal, and / or iii) modifying or withholding a CLI (calling line identification) associated with the originator terminal, and / or iv) forwarding the text message to a group of multiple recipient terminals, and / or v) converting the message to flash format for direct display on a screen of the recipient terminal.

13. A system for providing a text message processing service for originators of text messages in a telecommunications network, the system comprising an MO to MT converter and a service apparatus, wherein the system is configured such that the MO to MT converter entity is operable to receive a text message in a mobile originated (MO) format from an originator terminal, the text message including an indication of the identity of the originator terminal and an indication of an identity of an intended recipient terminal for the text message, to convert the text message from the MO format to a mobile terminated (MT) format suitable for onward delivery to the intended recipient terminal, and to route the MT format message to the service apparatus for processing in dependence on the identity of the originator terminal so as to provide the text message processing service for the originator of the text message.