WO2011132181A1

WO2011132181A1 - A method and system for messaging in event of congestion in mobile networks

Info

Publication number: WO2011132181A1
Application number: PCT/IE2011/000025
Authority: WO
Inventors: Simon Dumbleton; Jim Plimmer; Shawn Duffy
Original assignee: Markport Limited
Priority date: 2010-04-21
Filing date: 2011-04-21
Publication date: 2011-10-27

Abstract

This invention provides resource sharing across multiple mobile networks by routing incoming (submitted messages) towards an external SMSC for delivery when the local resource is unavailable or fully utilized. For example, incoming messages can be routed to an external SMS function for safe storage and later delivery attempt to maximize SMS service quality and revenue. Determination of available external resources is achieved by use of a routing table that may be static (in the simple case) or dynamic (in the case where only the "spare" remote capacity is offered) that is shared in a reciprocal manner with each opted-in entity. Local network SMS-MO routing can selectively divert messages to the external SMS delivery resources, most typically after any billing is performed. The delivery to the external resource can be via MO-SMS (SS7/MAP) or IP (SIGTRAN/SMPP) depending on preference and locale. By offloading the MO message to another SMSC, local bandwidth usage is improved given that the MO message is only 2 transactions (MO & MO-ACK) compared with the 4 transactions for delivery. This presents the local network with a reduced transaction loading per unit time, than if the delivery is made synchronously by the local network. Therefore, the local network becomes more efficient under the extreme load.

Description

"A Method and System for Messaging in Event of Congestion in Mobile Networks"

INTRODUCTION Field of the Invention

The invention relates to communication networks, particularly for messaging. More particularly, it relates to operation of mobile networks at times of congestion. Prior Art Discussion

At present mobile networks can suffer from time to time from excessive congestion. An example is after a football match in a large stadium, or at New Year's Eve. It is known to perform handover of signalling from one cell to another during congestion. For example, US6490452 (Motorola) describes a system in which there is handover from a base station operating in one type of network such as UMTS to a base station in a different type of network such as GSM. The handover may be of a group of calls. US2004/0008647 (Hunkeler) describes a method and system for determining thresholds for evaluating inter-system handovers. US2010/0075682 (del Rio-Romero) describes load balancing among neighbouring cells of a mobile network.

The invention is directed towards providing an improved method and system to allow mobile networks to cater for temporary excessive demand. Another objective is to achieve this with as little impact as possible on network infrastructure.

Summary of the Invention

According to the invention there is provided a messaging network comprising network elements for receiving, storing, and delivering messages, wherein the network elements are adapted to: receive messages for delivery to a destination,

hand over messages to an external network if an element determines that resources of the messaging network insufficient, and subsequently receive messages back from the external network and to then route the message on to the destination.

In one embodiment, a messaging network element is adapted to perform a hand-over according to dynamic conditions such as temporary congestion or network outage.

In one embodiment, the messaging network is a mobile network.

In one embodiment, the messages include short messages.

In one embodiment, at least one of said network elements is adapted to determine according to published information data concerning external network availability.

In one embodiment, the published information is available in a resource sharing network.

In one embodiment, a messaging network element which decides on hand-over to an external network is a message controller which is dedicated to performing resource sharing operations.

In another embodiment, the message controller is linked with a message service centre such as an SMSC or an MMSC.

In one embodiment, at least one of said network elements is adapted to perform retry upon receipt of a retry signal from the external network. According to another aspect, the invention provides a method of operation of a first messaging network and an external messaging network, the method comprising the steps of:

a first network element receiving a message over a path including an air interface, and said element relaying the message to a message service centre,

based on local network conditions and information available for remote resources, the message service centre forwarding the message to the external network,

the external network accepting the incoming message, and

the external network applying processing rules and initiating delivery of the message. In one embodiment, the external network initiates delivery by sending the message to the first network for delivery to a destination device.

In one embodiment, the external network initiates delivery by sending the message to a third network for delivery to a destination device.

In one embodiment, a link between the first network and the external network is via a resource sharing system. In one embodiment, the resource sharing system operates according to a resource abstract model, in which functionality is available in a cloud mechanism in which network operators offer resources to other networks that have an agreement to use the resources exposed.

In one embodiment, networks subscribe to the resource sharing model.

In one embodiment, subscribed sharing networks share information to enable optimization of traffic locally and when handed to the cloud.

In one embodiment, the shared information is dynamic, being updated in real time to cater for current traffic scenarios.

In one embodiment, the shared information includes some or all of:

bandwidth available, in terms of number of messages per time unit, and/or

bandwidth available in terms of bytes per time, and/or

handoff-handback routing type, and/or

white or blacklisted destinations, and/or

white or blacklisted originators, and/or

cost per message or per unit size, and/or

maximum storage time, and/or

storage capacity offered and used.

In another aspect, the invention provides a computer program product, comprising a computer usable medium having a computer readable program code embodied therein, said computer readable program code being adapted to be executed to implement a communication method as defined above in any embodiment when executed by a digital processor.

DETAILED DESCRIPTION OF THE INVENTION

Brief Description of the Drawings

The invention will be more clearly understood from the following description of some embodiments thereof, given by way of example only with reference to the accompanying drawings in which: -

Fig. 1 is a flow diagram illustrating a message flow for a message from one user to another user in the same network, but using network resources in an external network in a different time zone; and Fig. 2 shows an alternative flow without retry;

Fig. 3 shows a message flow where a message controller "MCO" is used in each network; and Fig. 4 shows an alternative flow with use of message controllers;

Fig. 5 is a block diagram of a general resource abstraction model of the invention for resource availability data sharing; and

Fig. 6 is a set of message transfer diagrams illustrating the flows of Figs. 1 to 4 in a different manner for improved clarity.

Description of the Embodiments

Glossary

SMS - Short Message Service

SMS-MO - Mobile originated SMS (sent by a user's handset)

SMS-MT - Mobile terminated SMS (sent to the users handset)

MNO - Mobile Network Operator

MAP - Mobile Application Part

SS7 - Signaling Scheme #7

IP - Internet Protocol

SMPP - Short Message Peer-to-peer Protocol MMS - Multimedia Messaging Service

This invention provides resource sharing across multiple mobile networks by routing incoming (submitted messages) towards an external network's SMSC for storage and possibly also delivery when the local resources are unavailable or are fully utilized. For example, incoming messages can be routed to an external SMS function for safe storage and later delivery attempt to maximize SMS service quality and revenue.

Determination of available external resources is achieved by use of a routing table that may be static (in the simple case) or dynamic (in the case where only the "spare" remote capacity is offered) that is shared in a reciprocal manner with each opted-in entity.

In the dynamic model, subscribed networks publish the resources offered in a common resource table. This enables networks to measure the current traffic levels and publish the amount of resources that are currently idle. Changes in usage of the resources in the local network are then updated quickly and the partner networks are prevented from impacting the local network quality of service. The dynamic publishing of resource availability may include a distributed database and where each contributing network is responsible for publishing its current state and pulling the latest data about remote entities. Alternatively, there may be a publish/subscribe model (e.g. using SIP or Diameter) in which each element is responsible for publishing its current state and subscribing for updates to remote systems. It is envisaged that an architecture such as is used by networks for least cost routing may be utilized for resource sharing information.

Local network SMS-MO routing can selectively divert messages to the external SMS delivery resources, most typically after any billing is performed. The delivery to the external resource can be via MO-SMS (SS7/MAP) or IP (SIGTRAN/SMPP) depending on preference and locale.

By offloading the MO message to another SMSC, local bandwidth usage is improved given that the MO message is only 2 transactions (MO & MO-ACK) compared with the 4 transactions for storage and delivery. This presents the local network with a reduced transaction loading per unit time, than if the delivery is made synchronously by the local network. Therefore, the local network becomes more efficient under the extreme load. Routing towards external networks that are not experiencing the same event or indeed the event at that point in time (for example New Year, school results day, or emergency situation), offers additional interconnect bandwidth for message deliveries also, and improves quality of service. This invention also provides for extracting the local storage resources into a global "cloud". Existing storage infrastructure would be pushed into the "cloud" and resource sharing service levels publicized to other connected parties in the same "cloud".

Referring to Figs. 1 and 2, the invention allows an A-Party network to adapt to local and remote conditions (e.g. bandwidth, storage capacity, local radio usage, offered remote resources, B-Party location, and/or time of day) to maximize delivery performance. The examples show how a New Years Eve event in the UK can exploit the available capacity in Australia for message delivery.

In Fig. 1 the message sequence (also illustrated in Fig. 6) is as follows:

1 : in a network ("N/W A") in the GMT time zone, the mobile station (MS) submits an SMS- MO over the air interface to the BSS/MSC,

2: the BSS/MSC relays the SMS-MO to the SMSC address (SCA) in the conventional way, 3: based on the local conditions and the information available for remote resources, the SMSC entity (could be a message controller, "MCO", for example) forwards the SMS- MO to an external network ("N/W B") in a time zone ten hours ahead (GMT + 10),

4: the external network N W B accepts the incoming SMS-MO,

5: the external network N/W B applies processing rules and periodically delivers the SMS- MO back to the original network, in accordance with policy and network status,

6: the original network N/M A accepts the SMS-MO, and

7: an HLR lookup (not shown) and SMS-MT delivery occur as normal.

In Fig. 2 the message sequence (again, also illustrated in Fig. 6) is as follows:

1 : a mobile station (MS) in the network N/W A submits an SMS-MO over the air interface to the BSS/MSC,

2: the BSS/MSC relays the SMS-MO to the SMSC address (SCA) in the conventional way, 3: based on the local conditions and the information available for remote resources, the

SMSC entity (could be an MCO for example) forwards the SMS-MO to the external network N/W B,

4: the external network accepts the incoming SMS-MO, 5: the external network applies processing rules and delivers the SMS-MO to the destination network (in this case also the originating network NAV A, but could alternatively be a third network) using a normal SRI-SM and SMS-MT process, and

6, 7: the destination network is able to deliver the message.

The original network may not be involved in the actual delivery of this message. This could be done by a third network, in which case the external network NAV B provides the benefit of storing the message before passing it to the third network, in a situation where the original network does not have sufficient storage resources.

The delivery methods are selected according to an agreement between the two (or more) networks and published information in real time. Figs. 1 and 2 do not show the standard local network deliveries that would be occurring at the optimal rate, as set by the local operator and the local resources.

Routing to the offered remote resources could be via a variety of algorithms and could include in some embodiments primary/secondary routing, round robin, or weighted round robin for example. The implementation is preferably realized by an SMSC or by a message controller in the networks.

Figs. 3 and 4 show implementation of inter-network handover using message controllers ("MCOs"). The operating information for the flow of Fig. 3 (and also illustrated in Fig. 6) is as follows:

The A-party subscriber of a UK network NAV A sends a message to the B-party, also a subscriber of the UK network NAV A. Under normal circumstances, the network would deliver the SMS directly to the B-Party. This is the most efficient delivery path and is as defined in the GSM MAP specifications.

However, the prevailing conditions (or the static routing) of the message controller MCO have determined that additional resources are required. An Australian network N/W B is not experiencing the same demand on its resources, and via a cloud communication path, has indicated to the UK network message controller that its local resources "are available for use". This could be to offer additional capacity during the messaging peak that coincides with a New Year's Eve event. Due to the timezone difference (+10 hours), the same peak has been and gone in Australia.

Therefore, the message controller MCO redirects the mcoming SMS-MO message to the AU network. The SMS is retained in the SMS-MO format and is delivered using either the SIGTRAN standard signaling for MAP SMS, or via a superset protocol such as per Acision^™ ADMI protocol (or similar). The latter enables the relaying of additional information, including delivery options. A benefit of a superset protocol like ADMI is that additional value and community preferences can be readily shared between the co-operating networks, offering seamless services to subscribers without impacting on the service levels offered. This approach also allows co-operating networks to publish the service capabilities, providing another selection criteria when additional resources are selected for use.

When the receiving entity in the AU network (either the SMSC or the message controller) accepts the message, it stores it and enables an appropriate retry profile for the message. In this flow, it is required that the SMSC support retry using the SMS-MO format (simply buffering and redelivering the message) or it can be converted using the message controller MCO back to the SMS-MO format.

A major advantage of keeping the messaging at the SMS-MO level is that billing and delivery source information is simplified.

When the SMS-MO Retry message arrives back at the UK network, the local demand on resources may or may not be available. However, at some point, the UK network will be available to deliver the message to the B-Party. By handing off the message to the "cloud" (in the form of the AU network in this example), the demand on the Radio Access Network is controlled, avoiding the waste of bandwidth due to failed delivery attempts and collision of SMS in the radio data channels. The implementation of a "cloud" entity in this context can be varied. Existing protocols like SMPP allow messages to be offloaded to external entities and is often used for connectivity to SMS HUB providers. The "cloud" service can be seen as a generalization and evolution of these SMS HUBs to provide extra capabilities, including the delivery of the SMS using another network's resources, storing the message on behalf of the local network, or possibly changing the SMS into a different media type completely.

To preserve delivery order or sequence, the message controller MCO can be configured to send all messages to a defined B-Party in the same external network.

The operating information for Fig. 4 is as follows:

The UK network has a lack of local resources and calls upon the services of the remote AU network.

The message is handed off to the AU network in the SMS-MO format. The AU network accepts the message, stores it and takes responsibility for the delivery of the message to the B-Party in the SMS-MT format. The AU SMSC and MCO combination enable the AU delivery function to emulate the identity of a UK SMSC and / or MCO, hiding any sign of the routing changes from the recipient. Fig. 5 shows a resource abstract model, in which functionality is available in a "cloud". In Fig. 5 the operators offer all/some of the local resources to other networks that have an agreement to use the resources exposed.

All networks that are subscribed to the same cloud (or pool) of resources share information to enable the optimization of traffic locally and when handed to the cloud. This information is dynamic and is updated in real-time to cater for all traffic scenarios. The following are examples of information which could be shared:

• Bandwidth available (in SMS/sec)

• Bandwidth available (in bytes/sec)

· Handoff-handback routing type

• White or blacklisted destinations

• White or blacklisted originators

• Cost per SMS / Cost per byte

• Maximum storage time Storage capacity offered and used

All of the above could be segmented and/or repeated according to the source (i.e. within a particular operator group or not) as well as others.

The expansion of the "input" (i.e. storage) resource using external resources (i.e. operator B) enables the host network to limit the rate of the message deliveries given that there is no shortage of storage capacity. This avoids the current issue where the deliveries themselves collide with the incoming messages causing a high contention ratio on the radio and signaling network. This contention causes further issues as incoming submissions fail as do outgoing deliveries.

The interactions for receiving the messages back may for example involve a proprietary Diameter protocol or in an evolved case SIP and/or extensions in IMS. It is envisaged that the invention allows trade amongst operators within a group, or new networks that offer storage and resubmission capacity only.

It is also foreseen that the invention could enable the deployment of new networks with a reduced capacity of network infrastructure, if the storage and retry functionality is leased or supplied from an external network.

The invention is not limited to the embodiments described but may be varied in construction and detail. For example the first element which hands over a message may be the same as the second element which receives it back from the external network. The invention is not limited to SMS messaging, and could be implemented with other messaging protocols such as SIP/IP messaging. IP messaging is not exactly the same, but similar, in that Store and Forward engines are hardware-intensive, which results in operators having to invest in platforms to cater for peaks of demand which can be measured in terms of an hour or two per year. This investment is therefore one which operators try to avoid. Messages are stored for retry in a storage system, which at that moment in time, has spare capacity and that storage system could be in Australia and not the UK, for example, even if the recipient is in the UK.

Claims

A messaging network comprising network elements for receiving, storing, and delivering messages, wherein the network elements are adapted to: receive messages for delivery to a destination, hand over messages to an external network if an element determines that resources of the messaging network insufficient, and subsequently receive messages back from the external network and to then route the message on to the destination.

A messaging network as claimed in claim 1, wherein a messaging network element is adapted to perform a hand-over according to dynamic conditions such as temporary congestion or network outage.

A messaging network as claimed in claims 1 or 2, wherein the messaging network is a mobile network.

A messaging network as claimed in claim 3, wherein the messages include short messages.

A messaging network as claimed in any preceding claim, wherein at least one of said network elements is adapted to determine according to published information data concerning external network availability.

A messaging network as claimed in claim 5, wherein the published information is available in a resource sharing network.

A messaging network as claimed in any preceding claim, wherein a messaging network element which decides on hand-over to an external network is a message controller which is dedicated to performing resource sharing operations.

8. A messaging network as claimed in claim 7, wherein the message controller is linked with a message service centre such as an SMSC or an MMSC.

9. A messaging network as claimed in any preceding claim, wherein at least one of said network elements is adapted to perform retry upon receipt of a retry signal from the external network.

10. A method of operation of a first messaging network and an external messaging network, the method comprising the steps of:

the external network accepting the incoming message,

the external network applying processing rules and initiating delivery of the message.

11. A method as claimed in claim 10, wherein the external network initiates delivery by sending the message to the first network for delivery to a destination device.

12. A method as claimed in claim 10, wherein the external network initiates delivery by sending the message to a third network for delivery to a destination device.

13. A method as claimed in any of claims 10 to 12, wherein a link between the first network and the external network is via a resource sharing system.

14. A method as claimed in claim 13, wherein the resource sharing system operates according to a resource abstract model, in which functionality is available in a cloud mechanism in which network operators offer resources to other networks that have an agreement to use the resources exposed.

15. A method as claimed in claim 14, wherein networks subscribe to the resource sharing model.

16. A method as claimed in claims 14 or 15, in which subscribed sharing networks share information to enable optimization of traffic locally and when handed to the cloud.

17. A method as claimed in claim 16, wherein the shared information is dynamic, being updated in real time to cater for current traffic scenarios.

18. A method as claimed in either of claims 16 or 17, wherein the shared information includes some or all of: