GB2473763A

GB2473763A - Routing SMS messages to a destination mobile entity subscribed to value added services

Info

Publication number: GB2473763A
Application number: GB1019428A
Authority: GB
Inventors: Pedro Silva
Original assignee: ESERVGLOBAL UK Ltd
Current assignee: ESERVGLOBAL UK Ltd
Priority date: 2006-05-05
Filing date: 2006-05-05
Publication date: 2011-03-23
Anticipated expiration: 2026-05-05
Also published as: GB201019428D0; GB2473763B; GB0608940D0; GB0616881D0; GB2437776B; GB2437776A

Abstract

Providing routing information for routing a message to a destination mobile entity having an associated base network, the associated base network offering at least one value added service, comprising: receiving a request for routing information at a component in the base network; determining whether the destination mobile entity is subscribed to the at least one value added service; if the destination mobile entity is subscribed to the at least one value added service, providing routing information in response to the request for routing the message to a message handling component which provides said at least one value added service. The destination mobile entity may be roaming and the associated base network is the home network.

Description

Message Routing The present applicatibn relates the field of message routing and, in particular, to the routing of messages, such as Short Message Service (SMS) messages between components in a mobile telecommunications network.

As described in more detail below, in existing systems, if a user is roaming away from their own, home network when a message is sent to the user, the Home Location Register (HLR) of the home network supplies routing information to enable the message to be transmitted to the user device. On receipt of the routing information, the message is transmitted directly to the user device withkut passing through the home network of the user.

Hence the home network of a roaming user does not have any control over the delivery of messages to those users.

IS

According to one aspect, there is provided a method of providing routing information for routing a message to a destination mobile entity having an associated base network, wherein the destination mobile entity may roam to a foreign network, the method comprising: receiving a request for muting information at a component in the base network; determining whether the destination mobile entity is roaming to a foreign network; if the destination mobile entity is roaming to a foreign network, providing routing information in response to the request for routing the message to a component in the base network.

Hence the routing information supplied may depend on whether the user is roaming in a foreign network, or is located in the base network. If the user is roaming, the present method may enable the message to be sent to the user via the base network. This may allow the base network operator control over how and when the message is sent to the user and over the charging strategy adopted for the message.

In the event that the user is located within the base network, the routing information supplied may enable the message to be routed directly to the user. Such a message will pass through the base network so the base network operator may apply any routing or charging rules as required at this point. In one embodiment, a Value Added Services (VAS) component may intercept messages passing through the base network.

The base network may comprise the home network of the user of the destination mobile entity In some embodiments, the base network may not be the network to which the user is directly subscribed, but may be an underlying network for a Mobile Virtual Network Operator, as described in more detail below. In this situation, the user may consider the network of the MVNO to be their home network. However, the base network is the network having the infrastructure upon which the MVNO lies.

In some embodiments, the foreign network may be a separate network to the base network of the mobile operator used by the destination mobile entity. For example, a customer of i d Mobile Operator Network A may roam to the network of Mobile Operator B if there is no coverage of Network A available in a particular area (for example, if the customer is abroad).

In other embodiments, however, the foreign network may be a network of a Mobile Virtual Network Operator (MVNO). MVNOs implement mobile networks based on the physical infrastructure of another, underlying mobile operator. In such a situation, the base network of a mobile entity may be the network of the underlying mobile operator and the foreign network may be that of the MVNO. In this case, a user does not access the base network directly, but from a technical point of view, is always considered to be "roaming" in the "foreign" network of the MVNO.

Preferably, the method further comprises processing the message at the component in the base network. The processing may* comprise implementing a charging strategy for the message or implementing an intelligent routing strategy for the message, for example routing the message to the destination entity via a selected route based on network availability or forwarding the message to a destination other than that indicated in the message based on instructions received from the destination entity.

The method may include processing the message in accordance with a value added service.

Preferably, the meth5d further comprises forwarding the message to the destination mobile entity in the foreign ñètwork. Hence the message may be forwarded to the destination as detennined by the base network.

According to a further aspect, there is provided a method of providing routing information for roiting a message to a destination mobile entity having an associated base network, the associated base network offering at least one value added service; the method comprising: receiving a request for routing information at a component in the base network; determining whethef the destination mobile entity is subscribed to the at least one value added service; if the destination mobile entity is subscribed to the at least one value added service, providing routing information in response to the request for routing the message to a message handling component which provides said at least one value added service.

This aspect may enable the system to apply value added services to messages directed to destinations when the destination entity is subscribed to those services. The system may selectively intercept messages for which value added services are required without disturbing the distribution of other messages.

In one embodiment, the method further comprises determining whether the destination mobile entity is roaming to a foreign network and, if the destination mobile entity is roaming to a foreign network, providing routing information in response to the request for routing the message to a component in the base network.

In either of the aspects above, receiving a request for routing information at a component in the base network may comprise intercepting the request for routing information before it reaches a home location register of the base network.

Advantageously, this may reduce the load on the network HLR by offloading some of the routing request messages from the HLR. Further, this may enable the method to be implemented without requiring modifications to the network HLR or the way in which it handles routing requests.

In one embodiment, the at least one value added service comprises at least one of: selectively forwarding the message to a defined destination other than the destination message entity; selectively copying the message to one or more defined destinations; generating and sending an automated response message to the originator of the message; preventing the delivery of a predetermined type of message, a message from a predetermined originator or a message sent during a predetermined time period; retaining the message for delivery at a later time; forwarding the message to each of a group of message recipients on a message distribution list; parsing the message content; 1? applying s*cte4 vhrging strntegy for the message.

Further details of the value added services are set out below and it will be clear to one skilled in the art that the present methods may enable the implementation of a wide range of value added services, not limited to the list above.

Preferably, the message comprises a Short Message Service (SMS) message.

The method may further comprise terminating the message. For example, an acknowledgement of receipt of the mobile-originated message may be transmitted back to the originating mobile. The message may also be converted from a mobile-originated message to a mobile-terminated message.

The method may also further comprising forwarding the message to the destination mobile entity.

While the systems and methods described herein are particularly applicable to Short Message (SM) messages, it will be appreciated that the systems and methods may also be used in some embodiments for other message types. For example, the message may

S

comprise an MMS, Instant Messenger, email, facsimile or voicemail message. In one embodiment, a plurality of different message types may be sent within the network.

In one embodiment, the network may comprise an SS7 network. However, in other embodiments the network may comprise an MM7, GPRS, 3G network or an IP-based network or any other network type suitable for message transmission. Portions of the network may be implemented using different protocols.

According to a further aspect, there is provided a method of processing a message in a base network associated with a destination mobile entity, wherein the destination mobile entityis capable of roaming iri a foreign network, the method comprising: receiving a redirected message destined for the destination mobile entity; performing. at least one function for the message selected from a charging function and a value added service fiinctioii; forwarding the message to the destination mobile entity.

Hence redirected messages may be processed to perform charging or value added functions before the messages are forwarded to their destination, whether the destination is in the base network or roaming in a foreign network.

In one embodiment, the at least one value added service comprises at least one of: selectively forwarding the message to a defined destination other than the destination message entity; selectively copying the message to one or more defined destinations; generating and sending an automated response message to the originator of the message; preventing the delivery of a predetermined type of message, a message from a predetermined originator or a message sent during a predetermined time period; retaining the message for delivery at a later time; forwarding the message to each of a group of message recipients on a message distribution list; parsing the message content; applying a selected charging strategy for the message.

one embodiment, the message comprises a Short Message Service (SMS) message.

However, as set out above the present method may be applicable to other message types.

In a preferred embodithent, the method further comprises terminating the message.

Apparatus aspects corresponding to the method aspects set out above may also be provided and the apparatus may further incorporate one or more of the preferred features described above. Computer program, computer program product or computer readable medium aspects may further be provided corresponding to the method aspects set out above. Further a network may be configured and provided to implement the method aspects set out above.

Embodiments of the methods and apparatus described here will now be set out in more detail with reference to the figures in which: Fig. I illustrates a prior art message submission process; Fig. 2 illustrates a prior art message delivery process; Fig. 3 illustrates a prior art message delivery process when the destination entity is roaming; Fig. 4 illustrates a message delivery process according to one embodiment when the destination entity is roaming; Fig. S illustrates an architectural framework for SVAS provisioning according to one embodiment; Fig. 6 is a schematic diagram of a further architectural framework according to one embodiment; Fig. 7 illustrates a further embodiment of the intercept system; Fig. 8 is a schematic diagram of a further system according to one embodiment.

The process of delivering an SMS message from one subscriber to another according to a prior art system will now be described with reference to Figs. I and 2.

The process of getting an SM from the originating subscriber A to the destination subscriber 8 is carried out through two procedures: the MO-SM (Mobile Originated Short Message) transmission procedure, and the MT-SM (Mobile Terminated Short Message) transmission procedure.

Fig. 1 illustrates the MO-SM process. The SM 112 sent by subscriber A 110 is received by the Mobile Switching Centre (MSC) 114 to which A is attached. The MSC then forwards the SM to the Short Message Service Centre (SMSC) 118 A is assigned to. A MAP (Mobile Application Part) protocol Forward_SM message 116 is used to forward the message from theMSCll4totheSMSCllS.

The MT-SM transmission procedure now follows (see Fig. 2), as the SMSC 118 tries to deliver the SM directly to the receiving subscriber 220. To that effect, the SMSC starts by interrogating B's HLR 214 in order to obtain B's International Mobile Subscriber Identity (IMSI) and present location information (global title of the foreign MSC). The MAP SRI (Send Routing_Info) message 210 is sent, the reply 212 to which contains the requested location info. The SMSC 118 then forwards the SM 216 to the MSC 218 B is attached to (MAP Forward_SM message 216). The SM is finally pushed to the B subscriber 220.

15' Fig. 3 shows a normal MT-SM delivery procedure when the B-side subscriber is roaming in a separate network 314.

The message is sent by A from his home network 310. However, it is noted that the B-Side home network 312 provides the current location information for its subscriber, and then the actual Forward_SM message 316, carrying the user information, bypasses it completely. In other words, service providers have little or no control over how Short Messages are delivered to their subscribers when they roam.

One embodiment of the present system will now be described in more detail with. reference toFig.4.

As illustrated in Fig. 4, the B-Side Home Network 312 (the home network of the message destination entity) has an Mobile Delivery Platform (MDP) 410 installed, and the network has been configured to send all SRI requests 412 to the MEW 410.

When an SRI 412 reaches the MD? 410, the MD? 410 obtains the B-Side location information from the HLR, but then replies 414 to the original enquiry by providing its own

S

address as B-Side's foreign MSC. The Forward SM 416 will therefore be sent to the MDP 410.

The. MDP 410 can now apply intelligent processing arid routing rules to the' message received before forwarding it 418 to its final destination. In other words, B-Side's service provider can now control the delivery of short messages to the subscriber even as he roams.

Examples of intelligent routing scenarios and services that may be offered to the destination entity using the system described above will now be set out in more detail. It will be clear to the skilled person that the examples set out below represent only a small number of possible embodiments of services that may be offered and are not intended to be limiting in any way.

Possible Special Value Added Services (henceforth referred to as SVAS) that may be offered to a user using a system such as that described above may include SMS Copy, "Out of the office' auto-reply messages, and SMS Forwarding to multiple MSISDNs and/or e-mail. These services are described in more detail below.

SMS Copy In an SMS copy service, SMS can be copied to email in order to provide an archive) or to provide access on demand while the subscriber is travelling abroad. SMS can be copied to other devices (for example the twin SIM' in a earphone, or to the data card of a computer.

The Rules Engine of the Mobile Service Plaform (MSP) may be implemented to ensure, for example that SMS are only copied to the carphone if the device is active, thus reducing traffic and enhancing customer service perception.

In a further implementation, the operator can provide an intermediarisation service for business, by archiving SMS sent to a SMS recipient in order to provide non-repudiation services where financial transactions are triggered by SMS with offline payment (for example placing an order for a part against an existing account).

An SMS Copy service may also be used to distribute SMS to a group acting co-operative -for example a support team, or a group of taxi drivers -the first to respond to the SMS could be assigned the work.

SMS Forward While implementatkms of the Forward process may be similar to the SMS Copy service, different applications may become available. For example, forwarding SMS may enable applications like the following: -Sending SMS from certain recipients to a colleague and other SMS to email for later review.

-Providing, a termination of service forwarding service -should a subscriber move to another network, the subscriber's SMS could be diverted to another address for a period.

Auto-Answer (Out of Office Reply) An Auto-Answer capability can be used in conjunction with either Forward or Copy to provide additional subscriber services, or received messages can simply be rejected. For example, subscribers may wish to enable an auto-answer for periods when they are in meetings, travelling or simply don't wish to be disturbed.

The auto-reply message can be composed by the subscriber, or a default can be set up by the operator. In one implementation, the auto-answer facility may be integrated with Personal Information Manager (P114) services so that during busy or out-of-office periods responses will automatically be generated.

Since subscribers may activate the Auto-Answer service when they are roaming, in preferred implementations, it may be possible to allow, for example, 5145 from the country in which the subscriber is roaming to be delivered to the handset, thus providing the capability to communicate.

Barring In a barring service, subscribers can set-up times when they do not wish to receive SMS, with optional forwarding to a colleague, or to email.

In addition, in some embodiments, powerful barring can be operated by using White Lists or Black Lists to bar MSISDNs, applications, specific content types (for example Adult or Premium Rate content), content providers or phrases within content from being delivered.

Barring can be set by the user sending an SMS request message or by customer care operators through a web or provisioning interface.

Distribution Lists The system described herein can also operate on MO SMS. Thus services that are triggered by MO SMS can easily be provided.

Distribution lists may be implemented to enable subscribers to create numbered lists containing MSISDNs of friends or colleagues to which the message will automatically be delivered if an SMS is sent to that subscribers list number.

çgal Intercept Because the system described herein operates on both MO and MT messages related to a MSISDN it is may also be used for legal intercept in some embodiments. SMS can be non-intrusively copied to different agencies by email, and can be blocked and forwarded for review.

Virtual Private Network VPN short number dialling is often available. Offering short number SMS is a logical extension, and can be provided using the SVAS architecture, Call Data Records (CDRs) can be managed to vary the charge rate for SMS sent within the VPN, and for example, to apply VPN SMS to a special account.

In some embodiments, the VPN service can be configured to prevent SMS being sent outside the VPN, can apply different rates, or could effect a different billing mechanism for example SMS sent within the VPN would be billed to the corporate account, while SMS sent externally would be billed to the owner of the handset.

Further details of implementations of the system described herein will now be set out in more detail by way of example.

Fig. S illustrates an architectural framework for SVAS provisioning according to one embodiment. This architecture may enable a simple, fast triggering device 510 to manage SMS routing with minimal latency, while a sophisticated processing engine 512 (Rules Engine) may be used to manage and execute potentially complex business rules.

Both nodes may be connected to a subscriber database 514, where the SVAS status for each subscriber may be updated in real time.

Separating trigger evaluation from SVAS implementation may be provide one or more of the following advantages: Reducing the workload on the SVAS implementation node: the SVAS triggering 15' device acts as a filter, forwarding only relevant traffic to the SVAS implementation device, thus reducing its workload.

-Improved performance: the simple decision rule implemented at the triggering device (SVAS: Yes or No?) may allow for lower latency added onto messages for which no SVAS is provisioned.

20.. Independent scalability: this framework may allow a service provider to add capacity only if and where it is needed; for example: if the SMS traffic increases, but not the SVAS traffic, an upgrade to the triggering device will suffice; * likewise, an increase in the subscriber base that has no corresponding increase in traffic means an upgrade to the database will be enough.

-Inherent Flexibility: can design complex rules without regard to the latency of normal' messaging.

These requirements clearly apply to P2P SMS traffic. However these are not the only requirements. Advantageously, the present system may also deal with some or all of the following situations: -Out-Roamers should be catered for, particularly since one of the major anticipated reasons for service activation is holidays. This may be implemented using the system described herein that forces SMS messages from foreign networks to be handled by the home network. This ensures that rules can be app1id to all MS.

Applicatkin Originated Messages -in preferred embodiments, it is not assumed that Appikation Originated (AO) messages are exempt from treatment (a user may want subscribed alerts forwarded to email, or not). Hence, the solution described is preferably also capable of treating AO messages. Furthermore, in fUrther embodiments of the system, it may be possible to perform similar operations on MMS traffic.

Using the system described herein, each or some of the situations described above may be addressed. For examile, one embodiment of the system may manage MT Traffic from other networks (even to out-roan)ers), MO & MT traffic from the home network, and AO traffic from own network using the same rules.

A further example architecture for the system described herein is illustrated in Fig. 6. Such an architecture may enable the separation of different functions within the systtm.

The Mobile Delivery Platform (MDP) may be implemented to perform some or all of the following functions: -SMS Routing and First Delivery Attempt, with Retry through existing SMSCs or a proprietary Retry Component -AO-MT and MO-AT application by-pass, to protect the existing SMSCs from overload -SMS "Home Routing" as described herein to ensure SMS for out-roamers are

treatable for SVAS

-SMS Firewall to protect the home network against fraud and control Spam in addition to acting as the triggering node for SVAS, The Mobile Service Platform (MSP) may be implemented to provide, across a number of modules, the flexible logic engine for the SVAS. The MSP may further act as an application gateway for AO SMS (as explained above). In addition the MSP may provide one or more of the following functions: -Load Sharing for AO SMS (and MMS) delivery across the SMSC and Router infrastructure, protecting SMSCs and P2P traffic from being overloaded.

-Extensive set of API's and protocols to simplifS' external application integration and reduce lime to market S -Comprehensive filter engine for customisation of services (blocking, throttling, routing, validating, ete) -Provide subscriber protection against receipt of defined content types (such as Premium Rate or Adult) or specific application providers or services -Implemeht Aliasing to protect customer identity -Enhances reconciliation effectiveness by managing permanent records of all transactions -Single point for managing both SMS and MMS services, with a Role Based Web UI for simple provisioning and administration In one implementation of the system, the HLR may be implemented to act as a SVAS tricvoering node and point directly to the Rules Engine whenever a subscriber requests SVAS activation.

hi other words, upon reception of an SRI message, the HLR will check whether the subscriber concerned has an SVAS activated. If not, the HLR replies with the subscriber's current location. Otherwise, the SVAS replies with the address of the SVAS Rules Engine (i.e. the MSP).

This solution may be implemented by re-using a network element already owned by service.

providers, while permitting existing SMS routing components to continue in use without change.

However, this solution may require the HLR to be connected to a provisioning tool that updates the database whenever a subscriber activates or deactivates an SVAS.

Whilst it may be an appropriate implementation in some embodiments, this approach may provide an incomplete and perhaps unusable solution in other situations. In particular: -This architecture only works for MT procedures, meaning it provides a service provider with the ability to provide SVAS capabilities that are triggered on the basis of the destination (like "out of the office" auto-replies), For any SVAS capabilities triggered on the basis of the origin (like distribution lists), this approach would have to be complemented by a similar subscriber status query dependent routing function at the SMSC, S -. Routing loops may also cause a further problem with this solution: in the SMS copy service scenario, the SVAS implementer copies the original message to a group of MSISDN's, and optionally forwards the message to the original recipient -thus a new SRI for this recipient will be sent to the IILR, which will reply with the SVAS implementer's address again.

An alternative approach or solution may be termed the "SRI Intercept" approach. This approach is illustrated schematically in Fig. 7.

In this solution, access from the 557 network 712 to the HLR 714 passes through an SVAS 15' triering device, which may comprise an MDP message router 710.

In the embodiment illustrated, the SVAS MDP 710 will intercept all SRI requests sent to the HLR 714. These requests can be coming from the service provide? s SMSCs 716, or from other networks 718 (through the service provider's GMSC or Gateway STP).

The MDI> 710 preferably uses the data available in the SRI to query the subscriber database 720 to find out whether an SVAS is applicable: -If it is, the MDI> 710 may reply to the SRI with the SVAS Rules Engine's (MSP) address 722; alternatively, the MDI> 710 can reply with its own address -forwarding the SMS to the Rules Engine upon reception of the ForwardSM.

-If SVAS are not required, the MDI> triggering node 710 forwards the SRI to the HLR 714, and then forwards the HLR's reply to the querying node.

Embodiments of this solution may provide the advantage that it is not complicated, given that it is very close to the earlier from the network's point of view, and it does not interfere with the actual operation of the HLR (indeed, it reduces the load on the HLR). Furthermore, the triggering node could also provide a protection layer against Denial of Service attacks launched against the HLR -a throttling mechanism can be implemented for that.

The embodiment of the ystem described works on the basis of MT messages, and is applicable to destination-triggered SVAS (like auto-replies). Similar, complementary systems may also be iiiiplemented (at the SMSC, for instance) for services that are triggered on the basis of the origin (for example distribution lists, or archive).

The system disclosed in Fig. 7 may provide a solution the routing loop issue described above for the service scenario where an SVAS is enacted, but the SMS should nevertheless be forwarded to the briginal recipient: -The Rules Engine in the MSP can be programmed to loop back the message to the triggering node; this may be done in a specific message chanriel for which normal forwarding always applies -The database query at the triggering node level can yield 3 possible answers, instead of two: "NO SVAS APPLICABLE", "SVAS APPLICABLE", and "SVAS APPLICABLE + NORMAL FORWARD".

An architectural point relating to embodiments of the system is the handling of voice-MAP traffic, such as Mobile Terminated Calls. Assuming the SVAS node only gets S MS-MAP traffic, then the GMSC, and other MSCs, would still access the HLR directly for voice traffic. This means some STP in the service provider's network would be required to split voice-and SMS-MAP traffic. The corollary here is that the STP can theoretically be the HLR proxy itself, provided it has the capability to make routing decisions on the basis of a subscriber status database query.

A variation of the architecture described above, which may be termed the ForwardSM Sink Variant, is one where the MDP always replies with its own address to the SRI requests, and only does SVAS queries when the ForwardSM is received. Note that in this case, the MDP will get all SMS messages transiting through the network, The component may then attempt to directly deliver them without transmitting them through the network SMSC. This may free SMSC capacity to provide other services or enable the processing of a higher throughput of messages.

One advantage of this embodiment may Lie in the fact that the SVAS query can then be done on the basis of the inforthation available in the ForwardSM message. This may allow the implementation of ói'igin-triggered SVAS as well, given that the originator of the SM is included in the ForwatdSM request A further example embodiment of the system is illustrated schematically in Fig. 8. Such an embodiment may enable the intercept of both SRI and mobile originated messages.

In the embodiment Illustrated in Fig. 8, the MSP 812 is the SVAS implementation node, and the MDI? 810 is the SVAS triggering node.

In this case, the SVAS MDP 810 will intercept the SRI requests for all messages coming in from other networks, and all the MO-SM messages generated within the Home network, which will be sent via the network SMSC 814.

For the SRI intercept,, the triggering node 810 can make triggering decisions on the basis of the SRI itself, or always reply systematically with its own address and apply triggering rules upon reception of the ForwardSM. The latter may be preferable in some embodiments, as it will allow both origin-and destination-based triggering. Again, an SIP splitting voice-and SMS-MAP traffic may be used. For messages coming from foreign networks, there is no real difference between the present solution and the earlier system described above.

For the MO-SM intercept, the triggering rules may be applied upon reception of the MoForwardSM. Both origin-and destination-based rules can be implemented. The SMSC 814 may only receive SMS traffic for which no SVAS applies. This has the advantage of reducing traffic on the SMSC 814. Additionally, the SVAS triggering node can also implement first delivery attempt (FDA) routing, but that is optional.

A feature of implementations of the present system may be that MDI? can process MO and MT messages and apply rules based on any field of a message. In other words: the solution may provide for both origin and destination based SVAS triggering with minimal latency while avoiding the routing loop problem mentioned above.

A fUrther benefit of the system described may be the use of the flexible MSP Rules Engine to manage external interfaces, sophisticated logic and charging for the SVAS. The capability to manage A2P traffic, including MMS, together with direct P2P MMS delivery may enable an operator to deliver the same service levels for a number of different S messaging modes in the future.

It will be clear to one skilled in the art that variations and modifications may be provided to the systems and methods described above and that features of one aspect may be applied to other aspects.

Further embodiments of the invention are defined in the following numbered clauses: 1. A method of providing routing information for routing a message to a destination mobile entity having an associated base network, wherein the destination mobile entity may roam to a foreign network, the method comprising: receiving a request for routing information at a component in the base network; determining whether the destination mobile entity is roaming to a foreign network; if the destination mobile entity is roaming to a foreign network, providing routing information in response to the request for routing the message to a component in the base network.

2. A method according to Clause 1 further comprising processing the message at the component in the base network.

3. A method according to any preceding Clause further comprising determining whether the destination mobile entity is subscribed to the at least one value added service; if the destination mobile entity is subscribed to the at least one value added service, providing routing information in response to the request for routing the message to a message handling component which provides said at least one value added service.

4. A method of providing routing information for routing a message to a destination mobile entity having an associated base network, the associated base network offering at least one value added service, the method comprising: receiving a request for routing information at a component in the base network; determining whether the destination mobile entity is subscribed to the at least one value added service; if the destination mobile entity is subscribed to the at least one value added service, providing routing information in response to the request for routing the message to a message handling component which provides said at least one value added service.

5. A method according to Clause 4 further comprising determining whether the destination mobile entity is roaming to a foreign network and, if the destination mobile entity is roaming to a foreign network, providing routing information in response to the recfuest for routing the message to a component in the base network.

6. A method acc6rdinj to any preceding Clause wherein receiving a request for routing S information at a c?mponent in the base network comprises intercepting the request for routing information before the request reaches a home location register of the base network.

7. A method according to Clause 3 or 5 wherein the at least one value added service comprises at least one of: selectively fol-warding the message to a defined destination other than the destination message entity; selectively copying the message to one or more defined destinations; generating and sending an automated response message to the originator of the message; preventing the delivery of a predetermined type of message, a message from a predetermined originator or a message sent during a predetermined time period; retaining the message for delivery at a later time; forwarding the message to each of a group of message recipients on a message distribution list; parsing the message content; applying a selected charging strategy for the message.

8. A method according to any preceding Clause wherein the message comprises a Short Message Service (SMS) message.

9. A method according to any preceding Clause further comprising terminating the message.

10. A method according to any preceding Clause further comprising forwarding the message to the destination mobile entity.

11. Apparatus for providing routing infonnation for routing a message to a destination mobile entity having an associated base network, wherein the destination mobile entity may roam to a foreign network, the apparatus comprising: means for receiving a request for routing information at a component in the base network; means for determining whether the destination mobile entity is roaming to a foreign network; means for providing routing information in response to the request for routing the message to a component in the base network, if the destination mobile entity is roaming to a foreign network.

12. Apparatus according to Clause 11 further comprising means for processing the message at the component in the base network.

iS 13. Apparatus according to Clause Ii or 12 further comprising means for determining whether the destination mobile entity is subscribed to the at least one value added service; and means for providing routing information in response to the request for routing the message to a message handling component which provides said at least one value added service, if the destination mobile entity is subscribed to the at least one value added service.

14. Apparatus for providing routing information for routing a message to a destination mobile entity having an associated base network, the associated base network offering at least one value added service, the apparatus comprising: means for receiving a request for routing information at a component in the base network; means for determining whether the destination mobile entity is subscribed to the at least one value added service; means for providing routing information in response to the request for routing the message to a component in the base network, if the destination mobile entity is subscribed to the at least one value added service.

15. Apparatus according to Clause 14 further comprising means for determining whether the destinatidn mobile entity is roaming to a foreign network and, if the destination mobile entit? is roaming to a foreign network, means for providing routing information in iesponse to the request for routing the message to a component in the basenetwork. . I 16. Apparatus according to any of Clause; 11 to 15 wherein the means for receiving a request for routing information at a component in the base network comprises means for intercepting the request for routing information before the request reaches a base location register of the base network.

17. Apparatus according to Cause 13 or 14 wherein the at least one value added service comprises at least one of: selectively forwarding the message to a defined destination other than the destination message entity; selectively copying the message to one or more defined destinations; generating and sending an automated response message to the originator of the message; preventing the delivery of a predetermined type of message, a message from a predetermined originator or a message sent during a predetermined time period; retaining the message for delivery at a later time; forwarding the message to each of a group of message recipients on a message distribution list; parsing the message content; applying a selected chargingstrategy for the message.

18. Apjmratus according to any of Clause 11 to 17 wherein the message comprises a Short Message Service (SMS) message.

19. Apparatus according to any of Clause 11 to 18 further comprising means for terminating the message.

20. Apparatus according to any of Clause ii to 19 further comprising means for forwarding tEe mSsage to the destination mobile entity.

21. A method of jfroces sing a message in a base network associated with a destination S mobile entity, wherein the destination mobile entity is capable of roaming in a * foreign network, the method comprising: * receiving a redirected message destined for the destination mobileentity; performing at least one function for the message selected from a charging function and a value Added service function; to forwarding the message to the destination mobile entity.

22. A method according to Clause 21 wherein the at least one value added service comprises at least one of: selectively forwarding the message to a defined destination other than the destination message entity; selectively copying the message to one or more defined destinations; generating and sending an automated response message to the originator of the message; preventing the delivery of a predetermined type of message, a message from a predetermined originator or a message sent during a predetermined time period; retaining the message for delivery at a later time; forwarding the message to each of a group of message recipients on a message distribution list; parsing the message content; applying a selected charging strategy for the message.

23. A method according to Clause 21 or 22 wherein the message comprises a Short Message Service (SMS) message.

24. A method according to any of Clause 21 to 23 further comprising terminating the message.

25. Apparatus for processing a message in a base network associated with a destination mobile entity, wherein the destination mobile entity is capable of roaming in a foreign network, the apparatus comprising: means for receiving a redirected message destined for the destination mobile entity; means for performing at least one function for the message selected from a charging function and a value added service function; means for forwarding the message to the destination mobile entity.

26. Apparatus according to Clause 25 wherein the at least one value added service comprises at least one of: selectively forwarding the message to a defined destination other than the destination message entity; selectively copying the message to one or more defined destinations; generating and sending an automated response message to the originator of the message; preventing the delivery of a predetermined type of message, a message from a predetermined originator or a message sent during a predetermined time period; retaining the message for delivery at a later time; forwarding the message to each of a group of message recipients on a message distribution list; parsing the message content; applying a selected charging strategy for the message.

27. Apparatus according to Clause 25 or 26 wherein the message comprises a Short Message Service (SMS) message.

28. Apparatus according to any of Clause 25 to 27 fhrther comprising means for terminating the message.

29. A computer program or computer program product comprising instructions for carrying out a method according to any preceding method Clause, 30. A method substantially as any one described herein. * 24

31. Apparatus substantially as any one described herein with reference to any of Figures 4 toS.

Claims

Claims.1. A method of providing routing information for routing a message to a destination mobile entity having an associated base network, the associated base network offering at least one value added service, the method comprising: receiving a request for routing information at a component in the base network; determining whether the destination mobile entity is subscribed to the at least one value added service; if the destination mobile entity is subscribed to the at least one value added service, providing routing information in response to the request for routing the message to a message handling component which provides said at least one value added service.
2. A method according to Claim 1 wherein the at least one value added service comprises at least one of: selectively forwarding the message to a defined destination other than the destination message entity; selectively copying the message to one or more defined destinations; generating and sending an automated response message to the originator of the message; preventing the delivery of a predetermined type of message, a message from a predetermined originator or a message sent during a predetermined time period; retaining the message for delivery at a later time; forwarding the message to each of a group of message recipients on a message distribution list; parsing the message content; applying a selected charging strategy for the message.
3. A method according to any preceding claim wherein receiving a request for routing information at a component in the base network comprises intercepting the request for routing information before the request reaches a home location register of the base network.
4. A method according to any preceding claim wherein the message comprises a Short Message Service (SMS) message.
5. A method according to any preceding claim further comprising terminating the message.
6. A method according to any preceding claim further comprising forwarding the message to the destination mobile entity.
7. Apparatus for providing routing information for routing a message to a destination mobile entity having an associated base network, the associated base network offering at least one value added service, the apparatus comprising: means for receiving a request for routing information at a component in the base network; means for determining whether the destination mobile entity is subscribed to the at least one value added service; means for providing routing information in response to the request for routing the message to a component in the base network, if the destination mobile entity is subscribed to the at least one value added service.
8. Apparatus according to Claim 7 wherein the at least one value added service comprises at least one of: selectively forwarding the message to a defined destination other than the destination message entity; selectively copying the message to one or more defined destinations; generating and sending an automated response message to the originator of the message; preventing the delivery of a predetermined type of message, a message from a predetermined originator or a message sent during a predetermined time period; retaining the message for delivery at a later time; forwarding the message to each of a group of message recipients on a message distribution list; parsing the message content; applying a selected charging strategy for the message.
9. Apparatus according to Claim 7 or 8 wherein the means for receiving a request for routing information at a component in the base network comprises means for intercepting the request for routing information before the request reaches a base location register of the base network.
10. Apparatus according to any of Claims 7 to 9 wherein the message comprises a Short Message Service (SMS) message.
11. Apparatus according to any of Claims 7 to 10 ffirther comprising means for terminating the message.
12. Apparatus according to any of Claims 7 to 11 further comprising means for forwarding the message to the destination mobile entity.
13. A computer program or computer program product comprising instructions for carrying out a method according to any preceding method claim.