WO2014009212A1

WO2014009212A1 - Barring in alert messaging

Info

Publication number: WO2014009212A1
Application number: PCT/EP2013/063991
Authority: WO
Inventors: Fredrik ERLANDSON; Lars Kari
Original assignee: Mobile Arts Ab
Priority date: 2012-07-11
Filing date: 2013-07-03
Publication date: 2014-01-16

Abstract

The present disclosure relates to managing traffic in a communication network during an emergency situation. An alert middleware node (106, 202, 302, 700), an alert messaging service node (108, 204, 304, 700) and an alert messaging system (120), as well as methods thereof are disclosed. The present disclosure also relates to computer program products thereto. Barring of non-prioritized network communication traffic when alert messaging of a plurality of User Equipments, UEs, located in a specific geographical area within circuit and packet switched mobile networks is provided. In addition, blocking of non-prioritized services for said UEs is also provided. The present disclosure further enhances the protection against overload and congestion in mobile communication networks and in the core network during alert messaging.

Description

BARRING IN ALERT MESSAGING

TECHNICAL FIELD

The present disclosure relates generally to the field of alert messaging and more particularly to barring of non-prioritized traffic in a mobile communication network when sending alert messages during an emergency condition.

BACKGROUND

Today's globalized world and modern society is more vulnerable than ever and the population is exposed to an ever increasing number of major threats and hazards.

For example, the increased travelling around the planet for business and leisure makes travellers more exposed to environmental disasters, conflicts, epidemics or other diseases. More transportation through, and industries located within or close to, dense populated areas also increases the risk of serious consequences in case of e.g. traffic accidents or industrial hazardous leaks or pollutions.

The unpredictable and extreme weather conditions and climate changes also make environmental disasters more common with extreme consequences for people, infrastructure and health care.

Also, actions of war and terrorism are global and can affect a great number of people all over the world.

Furthermore, the supply of water, electricity, fuel and heat is now more centralised than ever, which, in case of disruptions or downtime, has a major impact on the population.

In all the examples above, knowledge of people's current location and a possibility to urgently alert people at risk on the current situation and what appropriate measures to take are top priorities to prevent people from ending up in unfortunate situations or even being injured or killed. This applies not only for citizens in their home country, but for citizens staying abroad as well.

In order not to worry people unduly and create unnecessary anxiety or mass hysteria, it is also of highest priority to only alert people who are actually at risk, i.e. alert only not those close to or within the affected area at the time of an incident.

Several attempts have been made in the past to inform and warn citizens of war related scenarios, emergencies, etc.

Sirens and similar aural solutions have been used since long to locally warn citizens of e.g. war scenarios, like bombs and missile attacks, etc. Aural solutions have later on often been complemented with public broadcasting systems, i.e. radio and television, in order to also provide information about the situation.

One of several problems with sirens and similar aural solutions alone is that the citizens do not get any direct information about the incident or where it is at. It can also be hard to determine if the incident is ongoing or has already occurred. The public broadcasting systems also suffer from various drawbacks. For example, the broadcasting of alert information does rarely reach only the local area in which the event has occurred, but often a whole nation why it may worry citizens unduly. A prerequisite for accessing the information is also that people are close to a turned on radio and/or television.

Due to the enormous increase of mobile telephony in most parts of the world during the last couple of decades and due to that mobile phones or user equipments have become nearly everyone's possession, the idea of using the mobile equipment for receiving alert notifications has been considered highly advantageous.

Since the majority of mobile telephony standards used around the world provide message and data services as well as speech services, notifications can easily be supplied to the mobile subscribers in text format as well as in other formats, like image or video formats.

One attempt to use mobile equipment for receiving alert notifications is subscription- based alert services, in which the mobile subscriber gets alerts within his fields of interest.

A major drawback with subscription-based alert services is that subscribers must provide information about themselves and their interests in advance to receive any alerts and that the subscriber often has to pay a periodic subscription fee. In practice, subscribers seldom want to voluntarily use their own time and energy on providing personal information to get notifications of any kind. Furthermore, subscribers often fear that their personal information may be misused, sold or passed on to third parties without their approval. Most importantly, in order for an emergency alert service to be effective, it is required that the vast majority of all subscribers subscribe to the same service, for which reason subscription-based alert services in practice never is an alternative for effective emergency alerting.

Another attempt to use mobile networks to warn citizens is cell broadcasting with short message service (SMS) which is a global systems for mobile communications (GSM) standard that provides a network operator or service supplier the possibility to broadcast a message to GSM subscribers within a certain radio cell or group of cells. A SMS cell broadcast message is broadcasted cyclically by base transceiver stations (BTSs) in defined radio cells at a specified frequency and duration. One of the major disadvantages with cell broadcasting is that all mobile subscribers must initially and manually configure their mobile equipment in order to be able to receive such messages. This configuration often also includes settings of different subjects that the subscriber is interested in receiving messages in, besides alert messages.

As in the case with subscription-based alert services, it is necessary that all subscribers are aware of cell broadcasting services and have actively done all the required reconfigurations and subject settings in able for emergency alert services to operate. In fact, the knowledge of cell broadcasting is generally poor and, and even if it were not, both the effort and knowledge how to reconfigure and the risk of letting personal settings being misused makes cell broadcasting a deficient alternative for emergency alert services.

Furthermore, since cell broadcasting systems are quite expensive and most certainly will be used for other purposes, such as commercial advertising during non-emergency periods, it is not unlikely that subscribers will become tired of this technique and choose to turn off the cell broadcasting feature on their mobile equipment.

Another disadvantage with cell broadcasting is that the location accuracy is limited to cell accuracy. Moreover, cell broadcasting services send the same alert message content and setting to all subscribers within a cell or set of cells.

Apart from the above, there have also been proposed other attempts to handle alert message distribution in mobile networks as described in the following prior art:

WO 2009/070029 Al describes a location based alert system for sending alert messages to users of mobile phones. Probes located between a home location register (HLR) and visiting location register (VLR) and corresponding mobile switching centres (MSCs) are utilised to monitor the traffic related to location updates. Probed data contains international mobile subscriber identity (IMSI) or mobile subscriber integrated services digital network number (MSISDN), cell ID, location area code (LAC) ID, date and time. Sending of alert messages comprises: assessing received information and determine the relevant mobile phones with corresponding MSISDN to send alert messages to and sending the alert messages to relevant mobile phones located in the specific geographical area. The assessing of received information may comprise a randomizing of cell ids in order to reduce queued traffic load on the same cell before a paging procedure on relevant MSISDNs for receiving serving cells for each relevant MSISDN and a check whether the returned cell ids are within the range of the cells covering a relevant geographic area. The alert message sending may also comprise measuring the time elapsed from sending the message to receiving a confirmation and, if the time elapsed is above a certain limit; reduce the load of the current cell by sending the next message through another cell. WO 2009/104970 Al reveals a traveller's alert system for producing updated status of subscribers who are staying in a specific geographical area abroad A database is continuously updated with location information and MSISDN of subscribers who are staying abroad with the aid of a probe that identifies queries from foreign operators in the mobile network to the HLR, i.e. probing is done between the national gateway (G-) MSC and HLR. Location data relates to whole countries or specific regions in one or more countries. Data updated in the database are visited country, region, MSISDN, date and time for last update for each person associated with the MSISDN. Status for persons staying abroad may be presented on a graphical user interface connected to clients.

WO 2008/079092 Al describes a method and apparatus for mobile subscriber alert notification in which a location server receives requests for subscribers that are within an alert area to enable notifications/alerts to be sent to the subscribers from an alert application. The quality of passive location data, generated in a network element due to any of the events: sending an SMS, making a call, location area update or periodic location update and stored in a database, is dependent of the frequency with which a core network sends passive location data to the location server at network events when the mobile station is in contact with the network. The location server reconfigures the core network and radio access network to send the information when it is needed. The method for mobile subscriber alert notification comprises sending a request to network nodes serving cells belonging to the alert area to modify the configuration of subscriber location data updating in the network nodes. The modified configuration comprises a periodic location update parameter.

WO 2006/028381 Al presents a method and system for optimized control of traffic load on switches in a communication network for maximum exploitation of the capacity of the switches when alerting the population when an undesirable event occurs in a specific geographical area by means of messages transmitted via the switches. The method comprises a step for establishing information on whom is located within a geographical area, a step for assigning load status on switches by test transmitting simultaneous calls, the number of calls being increased or reduced as a result of the revealed load on the switch and based on a set of rules, a step for clarifying and implementing broadcasting, a step for monitoring the load on the switches and a step for changing the number of message exchanges as a result of revealed load status on the switch(es).

As for alerting subscribers staying abroad, WO 2009/104970 Al reveals a traveller's alert system for producing updated status of subscribers who are staying in a specific geographical area abroad by means of a probe that identifies queries from foreign operators in the mobile network to the HLR, i.e. probing between a foreign MSC and the home network HLR. As radio network data for foreign countries seldom is available and the foreign MSCs may serve large unknown geographical regions (probing between an on-net HLR and an off -net MSC provides subscriber info (MSISDN/IMSI/ local mobile station identity (LMSI)) and node info (MSC/ serving general packet radio service (GPRS) support node (SGSN), but not cell info), the only certain location information provided by this method is in which country the subscriber is located.

Further shortcomings of prior art will become more apparent in the following description. There is thus a need to overcome the drawbacks of prior art configurations.

SUMMARY

An object of the present disclosure is to address at least some of the issues outlined above, and provide network conditions for enabling efficient alert message provision and delivery to a plurality of User Equipments.

This is attained by restricting the usage of the network for non-prioritized traffic services and/or subscriber activities.

The embodiments as presented in the present disclosure address this object of the present disclosure.

According to one aspect of this disclosure, a method for managing traffic in a communication network during an emergency situation, i.e. in an emergency mode, in an alert messaging system, is disclosed. The method comprises receiving a request to enter into an emergency mode, said request comprising information about a specific geographical area of the communication network, and determining which UEs are located in said specific geographical area. The method also comprises monitoring the present traffic in the specific geographical area, said present traffic being of different types, and selecting at least one traffic type according to a priority list of said different traffic types, based on the received request and the monitored present traffic. In addition, the method comprises initiating emergency-related barring of said selected at least one traffic type for the UEs located in the specific geographical area.

The priority list within the method in an alert messaging system, may comprise said different traffic types in the following order of decreasing priority: mobile terminating voice, mobile originating voice, and mobile originating messaging. This brings the advantage of allowing barring of traffic types according to different priorities. The priority refers to the importance of traffic during an emergency, i.e. mobile terminating (MT) voice is not especially important during emergencies, whereas mobile originating (MO) voice is a somewhat more important, whereas MO messaging is even more important, especially when attempting to answer an alert message.

The UEs located in the specific geographical area in initiating emergency-related barring, may comprise UEs within said specific geographical area being either only those UEs having specific MSISDNs, and/or or international mobile subscriber identities (IMSIs) or all UEs except for emergency or rescue personal UEs.

This is an advantage since it is important to be able to exclude certain types of subscribers from barring, especially emergency and/or rescue personal. Barring should neither be used to bar any services for emergency personnel subscriptions, e.g. ambulance personnel, police, the fire brigade, etc, as applicable for the type of emergency event.

Determining which UEs are located in said specific geographical area within the method in an alert messaging system may comprise positioning of said UEs by using one of more of the following methods: passive location methods, active basic location methods and active enhanced location methods.

Passive location methods bring the advantage that the network traffic is not unnecessarily increased.

Active location methods on the other hand bring an increased location quality, a compared to passive location methods.

The present traffic in monitoring of the present traffic, may comprise radio traffic information of at least one of: cell radio status information, radio traffic load information of signalling load on a radio channel per cell, and cell radio traffic capacity information, in a base station controller (BSC), radio network controller (RNC) and traffic data from interface probes on A-bis and/or Iub interfaces.

Initiating emergency-related barring within the method in an alert messaging system may comprise sending an emergency related barring initiation message, enabling an HLR to send an emergency related traffic barring message to a MSC/SGSN that serves UEs located in the specific geographical area.

The emergency related barring initiation message may comprise an any time modification (ATM) message comprising emergency related barring settings of said selected at least one traffic type. This has the advantage that an output message format of an alert messaging service node (AMN) can be used.

Initiating emergency related barring within the method in an alert messaging node may comprise sending an operator determined barring (ODB) request command prior to sending the emergency related barring initiation message, wherein the ODB request command requests the present ODB settings for the home public land mobile network (HPLMN), for MSISDNs and/or IMSIs, located in said specific geographical area.

In order to be able to roll-back to initial settings after message sending, before any message blocking and/or traffic barring setting modifications are done, the current settings are hereby collected by the AMN and uploaded and stored in the AMW.

The ODB request within command may comprise an any time subscription information (ATSI) command requesting said present ODB settings.

The method in an alert messaging system may also comprise receiving an ATSI response comprising said present ODB settings, prior to sending the emergency-related barring initiation message.

The method in an alert messaging system may further comprise exiting the emergency mode, based on receipt of a debarring request or on detection that the UEs in the geographical area to which an alert message has been sent, have received said alert message, and sending an ATM message with said present ODB settings to regain non-emergency mode subscriber barring settings.

It is an advantage that an initial message sending strategy for the AMN is downloaded and initiated from the AMW node to the AMN to allow the AMN to resume the former sending activities.

Initiating emergency-related barring within the method in an alert messaging system may comprise sending an emergency-related traffic barring message to serving MSCs/SGSNs.

This has the advantage that the HLR is off-loaded, thereby minimizing the traffic load in the core network and HLR.

Barring of non-prioritised traffic while off-loading the HLR and preventing overload and congestion in the core network and HLR, may be achieved by using an incorporated HLR functionality in the AMN. The HLR functionality can send a mobile application protocol (MAP) insert subscriber data (ISD) with ODB set as appropriate directly to MSC/VLR and SGSN.

As an additional option for maximum HLR off-load, the AMW could also suppress BDR, so that the AMN does not send a setting request as an MAP ATSI to the HLR. Instead, the barring procedure may be started by the AMW sending an initiate barring request (IBR) to AMN which would relay it using MAP ATM with ODB set as appropriate to the AMW included MSC/VLR and SGSN. As an alternative, the AMN could use its HLR functionality to send a MAP ISD directly to the MSC VLR/SGSN instead.

The emergency-related traffic barring message may comprise an ISD message enabling the MSC/SGSN to set barring settings of said selected at least one traffic type for UEs that are located in said specific geographical area.

The method in an alert messaging system may further comprise exiting the emergency mode based on receipt of a debarring request or on detection that the UEs in the geographical area to which an alert message has been sent, have also received an alert message, and sending another ISD message with ODB settings for all provided services to the MSC/SGSN.

When the alert message sending is completed, the initial message sending strategy for the AMN can be downloaded and initiated from the AMW to the AMN to allow the AMN to resume the former sending activities, which is an advantage.

The method in an alert messaging system may further comprise selecting at least one messaging activity of the alert messaging system, from a list of non-alert messaging activities of said alert messaging; and blocking the selected at least one non-prioritized messaging activity of the alert messaging system.

This brings the advantage of an enhanced protection of the mobile network from overload and congestions caused by non-prioritised messaging during an emergency situations and/or while sending alert messages.

This further minimises internal message sending resources while sending alert messages.

The method in an alert messaging system may further comprise monitoring present traffic in the alert messaging system during the emergency situation, and wherein selecting at least one messaging activity is based on said monitoring of said present traffic in the alert messaging system.

By monitoring the present messaging traffic in AMN and determining blocking based on said monitored traffic, a well-based decision regarding blocking of specific or all message sending activities can be made.

According to another aspect of this disclosure, a method for managing of traffic in a communication network during an emergency situation, i.e. in an emergency mode, in an AMW node, is disclosed.

This method comprises receiving a request to enter an emergency mode, where said request comprises information about a specific geographical area of the communication network, and determining which UEs are located in said specific geographical area. The method also comprises monitoring the present traffic in the geographical area, the present traffic being of different types, and selecting at least one traffic type according to a priority list of said different traffic types, based on the received request and the monitored present traffic. In addition, the method comprises sending an emergency-related barring request to an AMN, enabling barring of non-prioritized traffic services and/or subscriber activities.

Providing an alert middleware node brings the advantage that formats and interfaces of said alert middleware node may be used.

The priority list within the method in an alert middleware node may comprise said different traffic types in the following order of decreasing priority: mobile terminating voice, mobile originating voice, and mobile originating messaging.

Determining which UEs are located in said specific geographical area, within the method in an alert middleware node, may comprise positioning of said UEs by using one of more of the following methods: passive location methods, active basic location methods and active enhanced location methods.

The present traffic in monitoring of the present traffic in the method in an AMW node, may comprise radio traffic information of at least one of: cell radio status information, radio traffic load information of signalling load on a radio channel per cell, and cell radio traffic capacity information in a BSC, a R C, and traffic data from interface probes on A-bis and/or Iub interfaces.

According to yet another aspect of this disclosure, a method for managing of communication network traffic during an emergency situation, i.e. in an emergency mode, in an AMN, is disclosed.

This method comprises receiving a traffic barring request from an alert middleware node, wherein the request requests barring of at least one selected traffic type in a specific geographical area of the communication area. The method also comprises initiating emergency- related barring of said selected at least one traffic type for the UEs located in the specific geographical area, based on the received the traffic barring request.

The AMN handles the message sending including barring based on instructions/initiations from the AMW node.

The UEs located in the specific geographical area in initiating emergency-related barring, within the method in an alert messaging service node may comprise UEs within said specific geographical area being either only those UEs having specific MSISDNs and/or or international mobile subscriber identities (EVISIs) or all UEs except for emergency or rescue personal UEs. Initiating emergency-related barring within the method in an alert messaging service node may comprise sending an emergency-related barring initiation message to a HLR enabling the HLR to send an emergency-related traffic barring message to a MSC/SGSN that serves UEs located in the specific geographical area.

The emergency-related barring initiation message within the method in an alert messaging service node may comprise an ATM message, comprising emergency related barring settings of said selected at least one traffic type.

Initiating emergency related barring within the method in an alert messaging service node may further comprise sending an ODB request command prior to sending the emergency related barring initiation message, wherein the ODB request command requests the present ODB settings for the HPLMN for MSISDNs and/or IMSIs, located in said specific geographical area.

The ODB request command within the method in an alert messaging service node may comprise an ATSI command requesting said present ODB settings.

The method in an alert messaging service node may further comprise receiving an ATSI response comprising said present ODB settings, prior to sending the emergency-related barring initiation message.

Initiating emergency related barring within the method in an alert messaging service node may comprise sending a traffic barring message to a MSC/SGSN that serves UEs located in the specific geographical area.

Barring of non-prioritised traffic while off-loading the HLR and preventing overloads and congestions in the core network and HLR may be achieved by using an incorporated HLR functionality in the AMN. The HLR functionality can send a MAP ISD with ODB set as appropriate directly to MSC/VLR and SGSN.

As an additional option for maximum HLR off-load, the AMW node could also suppress BDR, so that the AMN does not send a setting request as an MAP ATSI to the HLR. Instead, the barring procedure may be started by the AMW node sending the IBR to AMN which would relay it using MAP ATM with ODB set as appropriate to the AMW node included MSC/VLR and SGSN. As an alternative, the AMN could use its HLR functionality to send a MAP ISD directly to the MSC/VLR/SGSN instead.

The traffic barring message within the method in an alert messaging service node may comprise an ISD message. The ISD message within the method in an alert messaging service node may comprise a calling global title (CgGT) identity of said alert messaging service node if it is detected that policing is not performed in a VLR of a MSC/SGSN serving UEs located in the geographical area.

The method in an alert messaging service node may further comprise receiving ISD responses from the MSC/SGSN.

The ISD message within the method in an alert messaging service node may comprise a CgGT identity of a regular/valid HLR for UEs located in the geographical area, if it is detected that policing is being performed in a VLR of a MSC/SGSN serving UEs located in the geographical area, enabling obtaining information about an ISD response by probing the interface between the HLR for UEs located in the specific geographical area and the

MSC/SGSN serving UEs located in the specific geographical area.

It is an advantage that a global title (GT) of the regular/valid HLR can be obtained by for example passive probing between the MSC/SGSN and the HLR - such as the called GT (CdGT) in a location update (LU) between the MSC/SGSN and the HLR.

This is advantageous since it allows verification that the barring settings has been carried out.

The method in an alert messaging service node may further comprise selecting at least one messaging activity of the alert messaging system, from a list of non-alert messaging activities of said alert messaging; and blocking the selected at least one non-prioritized messaging activity of the alert messaging system.

The method in an alert messaging service node may further comprise monitoring present traffic in the alert messaging system during the emergency situation, and wherein selecting at least one messaging activity is based on said monitoring of said present traffic in the alert messaging system.

According to yet another aspect of this disclosure, an alert middleware node for managing of communication network traffic during an emergency situation, i.e. in an emergency mode, is disclosed.

The AMW node comprises a processor and a memory storing computer program comprising computer program code which, when run in the processor, as a response to a receiving a request to enter into an emergency mode, said request comprising information about a specific geographical area of the communication network, causes the alert middleware node to:

determine which UEs are located in said specific geographical area, monitor the present traffic in the specific geographical area, said present traffic being of different types,

select at least one traffic type according to a priority list of said different traffic types, based on the received request and the monitored present traffic, and send a barring request to an AMN, enabling barring of non-prioritized subscriber activities.

According to yet another aspect of this disclosure, an alert messaging service node for sending traffic managing messages in a communication network traffic during an emergency situation, i.e. in an emergency mode, is disclosed.

The alert messaging service node comprises a processor and a memory storing computer program comprising computer program code which, when run in the processor, as a response to a receiving a traffic barring request from an alert middleware node, wherein the request requests barring of at least one selected traffic type in a specific geographical area of the communication area, causes the processor to:

- initiate barring of said selected at least one traffic type for the UEs located in the specific geographical area, based on the received traffic barring request.

According to yet another aspect of this disclosure, an alert messaging system for managing of communication network traffic during an emergency situation, i.e. in an emergency mode, is disclosed.

The alert messaging system comprises an alert middleware node as above and an alert messaging service node as above.

This is advantages since the handle different kinds of interfaces and signalling/messaging. It is noted that an alert middleware node and an alert messaging service node may be co- located or incorporated in a single apparatus.

According to yet another aspect of this disclosure, a computer program product having thereon computer program code for managing of communication network traffic during an emergency situation, i.e. in an emergency mode, is disclosed.

The computer program product comprises computer program code which, when run in a processor of an alert middleware node, as a response to receiving a request to enter into an emergency mode, said request comprising information about a specific geographical area of the communication network, causes processor of the alert middleware node to:

According to yet another aspect of this disclosure, a computer program product having thereon computer program code for sending traffic managing messages in a communication network during an emergency situation, i.e. in an emergency mode, is disclosed.

The computer program product comprises computer program code which, when run in the processor of alert messaging service node, as a response to receiving a traffic barring request from an alert middleware node, wherein the request requests barring of at least one selected traffic type in a specific geographical area of the communication area, causes the processor to:

initiate barring of said selected at least one traffic type for the UEs located in the specific geographical area, based on the received traffic barring request.

Further objects and features, as well as advantages of the present disclosure will become apparent from consideration of the various embodiments of the present disclosure described in the following description and the appended claims when considered in connection with the accompanied drawings.

BRIEF DESCRIPTION OF DRAWINGS

These and other aspects, features and advantages of which this disclosure is capable of, will be apparent and elucidated from the following description of embodiments of this disclosure, reference being made to the accompanying drawings, in which

Fig. 1 illustrates an alert messaging system topology of a GSM/universal mobile telecommunications system (UMTS) network related to embodiments of the present disclosure;

Figs. 2 and 3 illustrate signalling-type diagrams according to embodiments of the present disclosure; Figs. 4-6 present flow-charts of methods in according to embodiments of the present disclosure;

Fig. 7 schematically presents a node according to embodiments of the present disclosure; and

Fig. 8 schematically illustrates a computer readable product according to embodiments of the present disclosure.

ABBREVIATIONS

3 GPP Third Generation Partnership Program

A-GPS Assisted GPS

AMN Alert Messaging service Node

AMW Alert Middleware

AOI Area of Interest

ATI Any Time Interrogation

ATM Any Time Modification

ATSI Any Time Subscription Information

BDR Barring Data Retrieval

BR Barring Request

BSC Base Station Controller

BTS Base Transceiver Station

CAMEL Customized Applications for Mobile Network Enhanced Logic

CDR Charging Data Record

CdGT Called GT

CgGT Calling GT

CGI Cell Global Identity

DMAOL Default MAOL

E-CGI Enhanced CGI

GMLC Gateway Mobile Location Centre

GPRS General Packet Radio Service

GPS Global Positioning System

GSM Global System for Mobile Communications

GT Global Title

HLR Home Location Register

HPLMN Home Public Land Mobile Network HSS Home Subscriber Server

IBR Initiate Barring Request

IMS IP Multimedia Subsystem

IMSI International Mobile Subscriber Identity

IP Internet Protocol

ISD Insert Subscriber Data

ISDN Integrated Services Digital Network

LA Location Area

LAI Location Area Identity

LCS LoCation Service

LMSI Local Mobile Station Identity

LU Location Update

MAOL Max Age of Location

MAP Mobile Application Protocol

MMS Multimedia Messaging Service

MO Mobile Originating

MS Mobile Station

MSC Mobile Switching Centre

MSISDN Mobile Subscriber ISDN Number

MT Mobile Terminating

ODB Operator Determined Barring

OMA Open Mobile Alliance

PSI Provide Subscriber Information

RDS Reference Data Server

RNC Radio Network Controller

SAF Store and Forward

SAI Service Area Identity

SGSN Serving GPRS Support Node

SMS Short Message Service

SOAP Simple Object Access Protocol

SUPL Secure User Plane Location

SRI-LCS Send Routing Information for Location Service

SRI-SM Send Routing Information for Short Message

UE User Equipment UMTS Universal Mobile Telecommunications System

USSD Unstructured Supplementary Services Data

VLR Visiting Location Register DETAILED DESCRIPTION

Herein are disclosed methods, nodes, a system and computer program products for enhanced protection of the mobile network from overload and congestions caused by non- prioritised traffic when sending alert messages in circuit and packet switched mobile networks.

Examples of by non-prioritised traffic when sending alert messages in mobile networks are incoming and outgoing calls and outgoing messages, during emergency situations and/or while sending alert messages.

A general demand for cost-effective alert message routing and implementation is to utilise existing mobile networks, which infrastructure is dimensioned according to anticipated population density and communication requirements. Normally, the mobile network infrastructure is not dimensioned to handle more than a few percent of simultaneous calls and messages in comparison with the anticipated population in an area. There is hence a demand to handle urgent mass sending of alert messages during emergencies through circuit or packet switched mobile networks of any generation without jeopardising infrastructure overloads and congestions and without doing any changes to or interfere with the existing mobile core and radio access infrastructure.

To avoid unnecessary load on the mobile network and not to worry unconcerned people unduly, one major demand for effective alert message sending is to rapidly acquire knowledge of where subscribers are located and only alert subscribers within affected defined geographic areas. This applies both packet and circuit switched mobile networks as well as in mobile networks of different generations.

Accordingly, one challenge for effective alert messaging sending is to obtain and update subscriber data including UE location with minimal impact on mobile network load and functionality. Another challenge for effective alert message sending is to continually obtain and store subscriber data with UE location via location methods with minimal impact on the network traffic and load and then, if necessary, update old or obsolete data by location methods affecting network traffic and load as little as possible.

The alert middleware node can enable alerting UEs located in specific geographical areas with a defined alert message. A method therefore comprises obtaining UE subscriber data of said UEs, using passive UE location methods, optionally in combination with active UE location methods, where said UE subscriber data comprises UE location and UE-related network node information, obtaining radio network data for national or international communication networks using integrated or stand-alone radio planning or cell prediction tools, and global cell databases, respectively, obtaining service request including service-specific data from a client node and/or a managing node, for sending an alert message to subscriber UEs within defined areas, processing cell-based geographical alert and roaming zones in which UEs to be alerted is located based on obtained service-specific and radio network data, obtaining radio traffic information for cells within alert and roaming zones in a base station controller, a radio network controller or from interface probes on A-bis and/or Iub interfaces, optionally providing to client nodes and/or managing node service -related and/or service-specific subscriber data with UE location and UE-related network node information for subscribers of certain priority, type or all, and/or service-specific geographical alert area, area of interest (AO I), alert zone or roaming zone data, providing zone and cell data to a alert messaging service node for alerting UEs located in defined areas with a defined alert message, and processing service requests for alerting UEs of a certain priority, type or all located in defined zones with a defined alert message and providing said service requests to said alert messaging service node.

The alert middleware node may generally also handle the collection and determination of service-related subscriber, network and traffic data for enabling alerting UEs located in defined areas with a defined alert message. The alert middleware node may also obtain service -related UE subscriber data including UE location, UE status and UE-related network node information from the mobile network via passive location methods, which monitors the data traffic on the network interfaces non-intrusively and extracts, sorts and saves relevant location, status and node data per UE and/or subscriber identity.

Service-related data for a particular area or all areas may be uploaded from the alert middleware node to the client and/or managing nodes and be presented at all times, i.e.

presented while message sending is passive as well as while message sending is active and without having to spend time on the obtaining and processing the data. Furthermore, while processed service-related data is either already at hand at the client nodes and/ or at the managing node or could be promptly uploaded from the alert middleware node, the preparation for message sending can be done very fast.

The passively obtained UE subscriber data may be complemented with active location methods including at least one of: provide subscriber information (PSI), ATI, send routing information for location services (SRI-LCS) or send routing information for short message (SRI-SM).

Location methods for positioning of UEs comprise the following:

passive location methods, such as passive probe location, event manager location or charging data record (CDR) location,

active basic location methods, such as 3generation partnership program (GPP) customized application for mobile network enhanced logic (CAMEL) provide subscriber identity (PSI) or ATI, and

active enhanced location methods, such as 3GPP location service (LCS) enhanced cell global identity (E-CGI), open mobile alliance (OMA) secure user plane location

(SUPL) assisted global positioning system (A-GPS) (gateway mobile location centre (GMLC)) or mobile station (MS)-based or MS-assisted) 3 GPP LCS A-GPS

(GMLC/serving mobile location centre (SMLC)). Collection of service -related data may temporarily be put on hold while the system is not in service or while the system is handling other kind of non location-based services, such as bulk message sending. The collection of service-related data must first be activated and time be spent on collecting and processing the data before any location-dependant message sending may occur.

As UE subscriber data is collected via passive location methods, it may have to be complemented with active location methods in case of missing, obsolete or too old data. This also applies when the UE location quality or accuracy is insufficient compared to defined settings.

In case of older location or cell data than a defined (default) max age of location ((D)MAOL) or in case UE subscriber MSISDN or MSC/SGSN address is missing or obsolete, the alert middleware node may update (and store) these by:

sending a CAMEL PSI towards the MSC/SGSN to get (updated) cell information (CGLSAI) in case of missing or obsolete cell info,

sending a CAMEL ATI towards the HLR to get (updated) cell information (CGI /SAI) in case of missing or obsolete cell information (this method increases load on the HLR, why the PSI method may be preferred),

sending a SRI-SM for MSISDN towards the HLR in case of missing or obsolete IMSI and/or MSC/SGSN address (obtained node information may hereby be used as destination node address when sending the message and the IMSI may be used as subscriber address when sending the message), or

sending a SRI-LCS for IMSI towards the HLR in case of missing or obsolete MSISDN and/or MSC/SGSN address (obtained node information may hereby be used as destination node address when sending the message and the MSISDN may be used as subscriber index key).

Alert message sending in accordance with the present disclosure sends alert messages to all UEs currently located within a cell-based geographical alert zone and optionally to UEs currently located within an alert zone -related roaming zone.

According to one embodiment of the present disclosure, messages are sent to all UEs currently located within the cell-based geographical alert zone cells and optionally to UEs currently located within the alert zone -related roaming zone cells or Location Area(s) (LAs/LA Identities (LAIs)) in a parallel and load-balanced manner per cell and LAI. According to one embodiment of the disclosure, the roaming zone may be defined as geographic areas and/or coordinates surrounding the alert zone instead of cells and LAI(s).

According to one embodiment of the present disclosure, the alert middleware node handles the process of deriving geographic zone data, i.e. the corresponding radio network cell and/or LAI data for an alert area or AOI, and the message sending lists, i.e. the lists of subscriber UEs used by the alert messaging service node for knowing to which zones and subscriber UEs messages shall be sent and for message queuing and sending optimising purposes, based on obtained UE subscriber data, obtained service -specific data from the managing node or optionally directly from the client nodes in service requests, internal settings, current national radio network data continuously obtained from integrated, collocated or stand- alone radio planning and/or cell prediction tools and/or cell and LAI data input from the network operator, international radio network cell data obtained from global cell databases and passively obtained cell radio traffic data including at least one of: current cell status, capability, capacity or load from BSCs, RNCs or from interface probes on A-bis and/or Iub interfaces.

To increase the throughput of alert messages sending while avoiding core and radio access network overloads and congestions, one demand for effective alert message sending is to offload the HLR and MSC/SGSN as much as possible, e.g. by storing or caching subscriber UE node and location info, so that no extra signalling is needed to retrieve this.

In order to only send messages to subscribers within the actual defined emergency area(s), a demand for effective alert message sending is to determine cell-based geographical alert zones based on CGI, within GSM, and SAI within UMTS and/or geographic coordinates from alert area definition information and radio network data for the communication network.

To ensure that all subscribers, also those who may enter into an emergency area during alert message sending, will receive an alert message, a challenge for effective alert message sending is to determine an alert zone -related roaming zone from alert zone definition information comprising cells or geographic areas surrounding the alert zone or Location Areas, having LAIs including cells of the alert zone and then send messages to not only the alert zone, but also to the roaming zone dependant on settings. Another challenge is that the roaming zone should be able to be defined statically, with a size that is set from message sending start, as well as dynamically, with a size that varies, for instance decreases, over time based on e.g. remaining message sending validity period, progressed sending time, on internal system settings, subscriber priority or on subscriber-specific settings.

To increase the alert message sending throughput while avoiding core and radio access network overloads and congestions, one demand for effective alert message sending is to handle message sending so that the message output and radio traffic load lies within an acceptable output and radio traffic load interval and so that the radio traffic load is uniformly distributed among all (instances of) cells wherein a UE to be alerted is located.

Accordingly, one challenge for effective alert message sending is to determine and monitor the radio traffic capacity and radio traffic load per cell.

To optimise message sending and minimise network traffic load, it is important to have knowledge of UE status before sending. For example, it is no good, but rather a waste of traffic resources, to try sending messages to a UE in a busy or non-attached mode. On the contrary, traffic resources are effectively used when sending messages to UE that has currently been in dedicated mode, due to that no initial paging is needed before the actual message sending. Accordingly, the UE status as obtained via passive and/or active location methods for these purposes, can thus be used.

All service-related data, i.e. UE subscriber data together with radio network and radio traffic data, may be passively collected continuously over time for each network operator's whole network, while the collection of complementing data via active location methods are case -driven, i.e. collected when a message sending service so requires.

To further increase the throughput of alert messages while avoiding core and radio access network overloads and congestions, other challenges for effective alert message sending are to use separated sending processes for messages needing and not needing initial paging and to send messages as packet switched data instead of circuit switched data if possible. To fully utilize different network's performance and subscriber UE's presentation functionality, there are demands for effective alert message handling to send alert messages as circuit switched SMS messages or unstructured supplementary services data (USSD) messages as well as packet switched multimedia messaging service (MMS) or SMS over general packet radio service (GPRS).

To enable efficient defining, refining and supervision of alert geographical areas as well as enabling efficient defining and refining of alert message sending services, one demand for effective alert message sending preparation is to render presentation data, e.g. status and statistical data for subscribers of a particular type or all subscribers and their whereabouts, for presenting alert service-specific data. The alert service- specific data may comprise data that has been defined for a specific alert message sending service, e.g. service-specific alert zone/AOI, service data, message content and type, alert/roaming zones, and/or service related subscriber data, cell data and traffic data obtained from (continuous) data collection through passive location methods, alternatively in combination with data collection through active location methods, from radio network and from traffic data. Both the service -specific and service-related data may, for presentation use, be related to geographic area.

To ensure correct location information for subscribers staying abroad, one demand for effective subscriber UE location and alert message sending is to utilise obtained node information from passive probing between the on-net HLR and the off -net MSC/SGSN for deriving subscriber UE location, together with information from global cell databases where obtained foreign cell information can be translated into geographic coordinates.

For alert messaging systems there are also demands for withholding subscriber privacy data towards third party and to enable use of the system while not conducting alert message sending for other duties, such as location-based services for e.g. advertising, territorial monitoring and triggering services and non location-based services for e.g. bulk message sending.

With reference to the drawings, it is stressed that the particulars disclosed are by way of example and for purposes of illustrative discussion of the exemplary embodiments of the present disclosure only, and are presented in the cause of providing what is believed to be the most useful and readily understood description of the principles and conceptual aspects of the present disclosure. In this regard, no attempt is made to show structural details of the present disclosure in more detail than is necessary for a fundamental understanding of the disclosure, the description taken with the drawings making apparent to those skilled in the art how the present disclosure may be embodied in practice. The present disclosure can provide enhanced protection of the communication network from overload and congestion caused by non-prioritized traffic during emergency situations and/or while sending alert messages.

Figure 1 schematically presents a system for alert message sending. The main components comprise an alert middleware (AMW) node 106 and an alert messaging service node (AMN) 108. An over-all system may also comprise a client node 102 and a managing node 104.

The system is connected to a communication network comprising a home location register 1 10, a MSC/SGSN 1 12, a BSC/RNC 1 14 and a BTS/Node B 1 16. A UE or mobile station (MS) communicating with the BTS NodeB 1 16 is denoted 1 18.

The HLR 1 10 in GSM or home subscriber server (HSS) for IP multimedia subsystems (IMS), hereinafter referred to as HLR, is a central database to which mobile subscribers (i.e. subscriptions), identified via e.g. MSISDN, are permanently assigned for the purpose of storing vital details about the subscriber/subscription, the UE in use, the service(s) required, the user's identification encryption code, and serving network node information. Node information stored in the HLR enables charging and routing of messages towards the MSC or SGSN to which the UE is currently attached.

The MSC (for circuit switched messages) and the SGSN (for packet switched messages) basically handles the switching and routing of messages and often incorporates a VLR (not shown), which is a database similar to the HLR storing information on the location of subscribers currently visiting the location area having a LAI served by the VLR.

In the mobile network shown in the Figure 1 , the VLR and the MSC or SGSN are collocated in the same physical node and hereinafter referred to as MSC/SGSN.

The BSC (for circuit switched messages), packet control unit (PCU) (for packet switched messages, often collocated with BSC) or RNC (UMTS networks) is basically used to control groups of BTSs (in GSM) or Node Bs (in UMTS) and provide the mobility management for subscribers and the connection to the MSC/SGSN.

BTSs and Node Bs are basically transceivers distributed at fixed locations for communication with the UEs over radio links.

The mobile radio network is divided into L which represents the area in which a UE can move freely without updating the location to the VLR. Each LA is assigned a unique LAI.

The mobile network is also divided into smaller areas or cells; each served by a BTS/NodeB and assigned with a unique identity known as CGI in GSM, or SAI in UMTS. In most emergency situations, it is important to provide fast and accurate information to all individuals within an area exposed to the emergency, whether they are individuals living or working within or close to the emergency area, individuals temporarily visiting the area or any rescue team sent out for handling the emergency.

It is also important to provide a fast and accurate status on subscribers and statistics on how many and who are currently within or close to an emergency area, domestic or foreign, to give authorities an indication of the magnitude of the emergency and help the authorities to e.g. scale evacuation and medical operations in accordance with the number and nationality of the individuals or inform relevant parties, such as hospitals, fire brigades, police forces, press, relatives, etc. of the situation in the area.

The same applies to network technical status too; fast and accurate information regarding the network status in an alert area could provide vital input when e.g. assigning technical support personnel to the area. Fast and accurate status information is also vital when defining what and how information should be sent to the individuals concerned.

Embodiments of the present disclosure provide enhanced protection of the

communication network from overload and congestion caused by non-prioritized traffic during emergency situations and/or while sending alert messages.

During emergencies and serious incidents, the traffic load in the mobile networks is normally dramatically increased, which could lead to overload and congestions in the mobile core and radio access network.

As the distribution of alert messages to subscribers within affected areas is of highest priority while it contributes to an effective rescue and emergency handling that may save life, methods for protecting the mobile network from unnecessary or non-prioritised load are crucial to enable unobstructed alert message sending.

By prohibiting non-prioritised subscriber traffic activities, i.e. barring, while sending alert messages the load in the mobile network and the core network is reduced.

In addition, by prohibiting non-prioritised message sending activities except alert message sending, i.e. blocking, further load reduction may be achieved.

The mobile network is hereby efficiently protected against network overload and congestion during an emergency situation and/or while sending alert messages.

Embodiments of the present disclosure also presents how to achieve such protection while offloading the HLR, thereby minimising traffic load in the Core Network and HLR, hence prohibiting infrastructure overloads and congestions. Operator determined barring of non-prioritized subscriber activities as set in the MSC/SGSN per MSISDN to bar e.g. MO/MT calls or MO messages, may either be used as a precaution for all subscribers within the affected area when alert messages are to be sent, or be decided on a per occasion bases, for instance if experiencing congestions/long response times primarily in the radio access network or the core network.

Barring is normally performed on a national level, i.e. barring data is defined for each national network operator employing an alert message system, why it incorporates all on-net national subscribers located within specific geographical areas.

Different priorities between subscribers UE, i.e. barring may exclude specific subscribers/UE that may for example be involved in rescue operations such as police and fire brigade personnel.

Barring of non-prioritised calls may be defined in the operator defined barring general 32- bit string "odbgeneral32bitstring" and maybe performed on outgoing calls, e.g. all, international, packet switched and roaming outgoing calls, etc, and incoming calls, e.g. all, roaming outside HPLMN incoming calls, etc.

Barring of non-prioritised outgoing messages maybe defined in the operator defined barring HPLMN 32-bit string "odbhplmn32bitstring".

Due to the fact that barring is relatively potent as it can remove services from the targeted subscribers and increase the HLR load, the decision to bar subscribers is often taken by or in accordance with the network operator.

Operator determined barring may normally be used only as a last resort option when the signalling load in the core network and on the radio interface generated by other service activities has (or is assumed to have) a very large adverse impact on the MT messaging service used by the AMN and it is necessary to decrease/limit this signalling load.

In addition, when message responses from the subscribers back to the alert service are sought, the MO message service for the targeted subscribers shall certainly not be barred.

Barring should neither be used to bar any services for emergency personnel subscriptions, e.g. ambulance personnel, police, the fire brigade, etc, as applicable for the type of emergency event. Thus, if barring is to be used, the alert service should manage lists per type of alarm service of such emergency personnel subscriptions that will not be subject for barring.

Barring of alert messaging is performed on an MSISDN basis. Barring may hence be made on only specific MSISDN within a specific geographical area. Barring may also be performed dependent on the kind of massaging service, a messaging priority and/or an emergency mode criticality. In case of dual or more parallel emergencies, barring of alert messaging maybe performed for a prioritized emergency mode, based on a criticality of the emergency mode.

To be able to roll-back to earlier or default barring settings, i.e. to restore this information in the HLR after alert message sending, prior to barring of non-prioritised subscriber activities a first step of sending a command ATSI towards the HLR for each subscriber MSISDN is performed. The response to this command includes both current general and current HPLMN ODB settings per MSISDN and is stored in the AMW node.

The actual barring setting that is tagged per MSISDN in the MSC/SGSN, is set by sending an ATM with ODB settings as a bitmap of yes/no or set/not set from the AMN towards the HLR. The HLR then forwards the ODB settings as an ISD command towards the MSC/SGSN.

After alert message sending, the alert middleware node may initiate roll-back to initial barring settings by sending an IBR to the AMN with initial settings to initiate the AMN to send an ATM command to the HLR for all subscribers.

The barring of non-prioritised subscribers activities according to embodiments of the present disclosure will now be presented while referring to figure 2, which discloses a signalling-type diagram related to said embodiments of the present disclosure.

Signals are communicated between an AMW node 202, an AMN 204, a HLR 206 and a MSC/SGSN 208.

In 210, the AMW node 202 receives a request to enter an emergency mode. This request may be received from a client node (102) or from a managing node (104).

According to some embodiments the signalling-type diagram also comprises signalling 212-218. These are optional. To be able to roll-back to earlier or default barring settings, i.e. to restore these earlier or default barring settings information in the HLR after alert message sending, prior to barring of non-prioritised subscriber activities a first step of sending a command ATSI towards the HLR for each subscriber MSISDN is sent. The response to this command, i.e. ATSI response, includes both current general and current HPLMN ODB settings per MSISDN and is stored in the AMW node.

In 212 the AMW node 202 sends a BDR message to the AMN 204. Based on receipt of the BDR, the AMN sends 214 an ATSI command to the HLR 206.

Either by default, in connection with alert message sending or after receipt of a barring request (BR) from a client node or a managing node, the AMW node 202 node may initiate retrieval of default barring settings from the HLR by sending 212 a BDR command to the AMN 204. The AMN 204 may then send 214 an ATSI command towards the HLR 206. In 216 the AMN 204 receives an ATSI response from the HLR 206 revealing the general and current HPLMN ODB settings per MSISDN. These settings may then be uploaded 218 via service data over simple object access protocol (SOAP) and stored in the AMW 202. Down below we shall see that this data is used when rolling back to the initial or non-alert messaging barring strategy after the alert message sending if the barring strategy was changed during alert message sending.

It is noted that barring may be requested or initiated by the AMW node or the AMN when detecting for instance probes, data received from BNCs/RNCs such as network congestions or delays.

In 220 the AMW 202 sends the IBR to the AMN 204. The IBR normally includes barring information such as information to bar all MO/MT calls for certain subscribers UEs/MSISDNs and unbar the rest of the traffic, node identity (id) information such as MSC_id /SGSN_id and optionally HLR_id, and the ODB bitmap.

In 221 the AMN can optionally block some services to further provide for an enhanced protection against congestion or overload in the network.

When receiving an IBR from the AMW node 202, the AMN 204 sends 222 an ATM command to the HLR for all or a defined group of subscribers within the affected area. The decision to bar subscribers is often done by, or in accordance with, the network operator due to the increased HLR load and the limitations of services in their network.

Barring decision can also be made in accordance with type of service, if traffic load gets too high,, i.e. high priority emergency situations; bar all services except for certain MSISDNs that correspond to emergency personnel, low priority emergency situations; bar a lesser amount of traffic services for certain MSISDNs and for all other low priority message services; bar just some traffic services. The limitation of traffic for low priority message services should instead be done by lowering the message output.

After receiving 222 the ATM command, the HLR 206 sends 224 a mobile application protocol (MAP) ISD command including the ODB bitmap towards the MSC/SGSN 208, which temporarily marks the subscribers with a barring tag, at MSC/SGSN level, that will prevent them from being authenticated when for example trying to originate and terminate calls provided the ODB is set to bar MO/MT calls. It is noted that subscribers with priority, e.g. emergency personnel, shall not be barred.

When the alert message sending is completed, the initial barring strategy for the subscribers are downloaded 226 from the AMW 202 and an ATM command with the initial ODB settings, i.e. same settings as before changing barring setting, are sent 228 from the alert messaging service node 204 to the HLR 206. This regains their former subscriber barring settings. The HLR 206 then sends an ISD 230 command including the initial ODB settings to the MSC/SGSN 208, implementing the former subscriber barring settings.

In order to off-load the HLR during barring when alert messaging, the alert messaging service node can use its incorporated HLR functionality to send MAP ISD with ODB set as appropriate directly to MSC/VLR and SGSN instead of sending a MAP ATM with ODB set as appropriate to HLR.

The MSC/VLR-address, SGSN-address and HLR-address may then need to be included in the IBR from the Middleware Node for both barring and unbarring. In this case the HLR- functionality in the Alert Messaging Node can send the barring/unbarring request directly to the MSC/VLR / SGSN as an ISD, i.e. not via the HLR.

In 231 AMN unblocks the message sending strategy, and reloads the initial or default message sending strategy.

Figure 3 discloses a signalling-type diagram related to embodiments of the present disclosure for which a HLR in the communication network is off-loaded during the barring procedure as compared to the signalling-type diagram as presented in figure 2. Signalling is performed between a AMW node 302, an AMN 304, and a MSC/SGSN 306.

After receiving an alert message sending request from a client node or managing node, the client node or managing node may either by default or when experiencing network congestions send a BR 308 to the alert middleware node 302.

The AMW node can then send 310 an IBR to the alert messaging service node. When the IBR is used for HLR off-load barring, in addition to comprising barring information, node information such as MSC_id /SGSN_id and optionally HLR_id, and the ODB bitmap (set/no set), the IBR now also comprises a called global title (Cd GT) that equals any one of MSC_id, VLR_id and SGSN_id, and a calling global title (Cg GT). The CgGT is either the HLR id, in order to pretend that a valid HLR has sent the ISD in case of MSC/SGSN screening or policing of Cg GT, or the AMN ID in case of no screening or policing.

In 311 blocking of non-prioritized traffic services is performed by the AMN. The AMN then uses 312 its HLR functionality to send 314 a MAP ISD directly to the MSC/VLR/SGSN 306 stated in the IBR for all or a defined group of subscribers within the affected area.

It is noted that the alert middleware node may also need to resend the IBR as soon as it discovers that subscribers have roamed into another MSC/VLR or SGSN. In the case the Cg GT is a valid HLR_id, the AMN never retrieves any ISD responses. Instead, any ISD responses would be sent to the valid HLR. By passive probing interfaces between the MSC/SGSN/VLR and the valid HLR, information on ISD responses can however be gained.

In the case the Cg GT is the AMN, the AMN may receive ISD responses to the sent ISD messages.

The global title (GT) of a regular/valid HLR can be obtained by passive probing between the MSC/SGSN and the HLR, such as on the CdGT in a location update (LU)

When the alert message sending is completed the AMW node then indicates unbarring of all services when AMW node sends 316 the unbarring request to the AMN, including the

MSC VLR- Address, SGSN-address and HLR-address. The AMN then sends 318 an unbarring ISD to the MSC/SGSN for all services. For this reason, during some time after the direct debarring from the AMN, the subscriber may get some more services than actually subscribed for in valid HLR. The ODB data would for example be restored when the MS/UE attaches the MSC/SGSN after being detached or if the subscriber roams into another MSC/SGSN.

In 319 an unblocking of an earlier blocking may be performed to reset the blocking settings in the AMN, again allowing non-prioritized message sending.

The optional blocking/unblocking will be further described down below.

It is noted that this type of maximum HLR off-load is only an option, as it would also be possible to start the barring procedure by the AMW node retrieving the current ODB data from the AMN which would retrieve it using MAP ATSI. In such case, the barring procedure would be continued by the AMW sending the barring request to AMN which would relay it using MAP ATM with ODB set as appropriate to the AMW node included MSC/VLR and SGSN. The barring procedure would then be ended by the AMW node sending 316 a de -barring request to the AMN with the ODB-data set as previously retrieved and including the current

MSC/VLR-address and SGSN-address. This regains the former subscriber barring settings.

It has been described that to further protect a mobile network from overload and congestions caused by traffic non alert message traffic during emergency situations, the AMN may start with blocking all message sending activities except for sending of alert messages, and then initialise non-prioritised traffic barring by requesting the AMN to send an ATSI towards the HLR for each subscriber MSISDN to retrieve current barring settings. If found necessary, traffic barring per MSISDN is set by sending an ATM with appropriate ODB bitmap settings from the AMN towards the HLR. As described above, to set barring while off-loading the HLR, instead of sending ATSI and/or ATM commands from the AMN, the incorporated HLR functionality in the AMN handles the sending of a MAP ISD with ODB set as appropriate directly to MSC/VLR and SGSN. This has the advantage that signalling and requests towards the HLR is reduced, for which reason the HLR is off-loaded. Congestion in the HLR may thereby be dramatically reduced.

Figure 4 presents a flow-chart of a method for managing of communication network traffic during an emergency situation, i.e. in an emergency mode, in an AMW node of an alert messaging system.

First, the method comprises receiving 400 a request to enter an emergency mode, where said request comprises information about a specific geographical area of the communication network. This corresponds to 210 in figure 2 or 308 in figure 3. In 402, the method comprises determining which UEs are located in the specific geographical area.

In 404, the method comprises monitoring the present traffic in the geographical area, the present traffic being of different types.

Information of the present traffic may be obtained by obtaining passively cell radio traffic data including at least one of: current cell status, capability, capacity or load from BSCs, RNCs or from interface probes on A-bis and/or Iub interfaces.

In 406, the method comprises selecting at least one traffic type according to a priority list of said different traffic types, based on the received request and the monitored present traffic. In 408, the method comprises sending an emergency-related barring request to an alert messaging service node, enabling barring of non-prioritized subscriber activities. This corresponds to signalling 220 in figure 2 or 310 in figure 3.

The priority list may comprise different traffic types in the following order of decreasing priority: mobile terminating (MT) voice, mobile originating (MO) voice, and MO messaging.

The method for managing of communication network traffic during an emergency situation, i.e. in an emergency mode, in an alert middle ware (AMW) node of an alert messaging system, may further comprise monitoring present traffic in an alert messaging system during the emergency situation, selecting at least one messaging activity of the alert messaging system, from a list of non-alert messaging activities of said alert messaging; and blocking the selected at least one messaging activity of the alert messaging system.

Figure 5 discloses a flow-chart of a method for sending traffic managing messages in a communication network during an emergency situation, i.e. in an emergency mode, in an AMN. This method comprises receiving 500 a traffic barring request from an alert middleware node, wherein the request requests barring of at least one selected traffic type in a specific

geographical area of the communication area for certain or all MSISDNs in the specific

geographical area. Receiving 500 corresponds to 220 in figure 2. The method also comprises

initiating 502 emergency-related barring of said selected at least one traffic type for the UEs

located in the specific geographical area, based on the received traffic barring request.

The initiating 502 emergency-related barring may further comprise sending an

emergency-related barring initiation message to a HLR, enabling the HLR to send an

emergency-related traffic barring message to a MSC/SGSN.

The emergency-related barring initiation message may further comprise an ATM message

comprising emergency related barring settings of said selected at least one traffic type for the

UEs located in the specific geographical area.

The initiating 502 emergency-related barring may further comprise sending an operator

determined barring, ODB, request command to the HLR prior to sending the emergency related

barring initiation message, wherein the ODB request command requests the present ODB

settings for HPLMN of each MSISDN located in said specific geographical area.

The ODB request command within the method in an AMN may further comprise an

ATSI command requesting said present ODB settings.

The method in an AMN may further comprise receiving an ATSI response comprising

said present ODB settings, prior to sending the emergency-related barring initiation message.

When off-loading the HLR, initiating 502 emergency-related barring may comprise

sending a traffic barring message to a MSC/SGSN. Said traffic barring message may further

comprise an ISD message.

Reference will now be made to figure 6 presenting a flow-chart of a method for managing

of communication network traffic during an emergency situation, i.e. in an emergency mode, in

an alert messaging system. This method in the alert messaging system comprises receiving 600

a request to enter into an emergency mode, said request comprising information about a specific

geographical area of the communication network. [This method further comprises determining

602 which UEs are located in said specific geographical area, and monitoring 604 the present

traffic in the specific geographical area, said present traffic being of different types. [The method Kommentar [Fl]: Se fiteklaringania till posifionering sans teafikovervakning sedan also comprises selecting 606 at least one traffic type according to a priority list of said different tidigare - kanske flytt hit istiUet? traffic types, based on the received request and the monitored present traffic. In addition this

method also comprises initiating 608 emergency-related barring of said selected at least one

traffic type of the UEs located in the specific geographical area. The priority list in the method in the alert messaging system may comprise different traffic types in the following order of decreasing priority: MT voice, MO voice, and MO messaging.

The initiating 608 emergency-related barring within the method in the alert messaging system may comprise sending an emergency related barring initiation message to a HLR, enabling the HLR to send an emergency-related traffic barring message to a MSC/SGSN. Said emergency related barring initiation message may comprise an ATM message comprising emergency related barring settings of said selected at least one traffic type for the UEs located in the specific geographical area.

The initiating 608 emergency-related barring may further comprise sending an ODB request command to the HLR prior to sending the emergency related barring initiation message, wherein the ODB request command requests the present ODB settings for HPLMN of all or specific MSISDNs, located in said specific geographical area.

The ODB request command may comprise an ATSI command requesting said present ODB settings.

The method in the alert messaging system may further comprise receiving an ATSI response comprising said present ODB settings, prior to sending the emergency-related barring initiation message.

The method in an alert messaging system may also comprise exiting the emergency mode, based on receipt of a debarring request or on detection that the UEs in the geographical area to which an alert message has been sent, have also received an said alert message, and sending an ATM message with said present ODB settings to the HLR to regain non-emergency mode subscriber barring settings.

When off-loading the HLR, the initiating 608 emergency-related barring in the alert messaging system may comprise sending a emergency-related traffic barring message to a MSC/SGSN.

The emergency-related traffic barring message with the method in the alert messaging system may comprise an ISD message enabling the MSC/SGSN to set barring settings of said selected at least one traffic type for the UEs that are located in said specific geographical area. This ISD message may comprise a CgGT identity of the sender of the traffic barring message, wherein the method further comprises receiving ISD responses from the MSC/SGSN.

The method in an alert messaging system may also comprise exiting the emergency mode based on receipt of a debarring request or on detection that the UEs in the geographical area to which an alert message has been sent, have also received an alert message, and sending another ISD message with ODB settings to the MSC/SGSN to regain non-emergency mode subscriber barring settings.

The method in the alert messaging system may also comprise monitoring present traffic in the alert messaging system during the emergency situation, selecting at least one messaging activity of the alert messaging system, from a list of non-alert messaging activities of said alert messaging, and blocking the selected at least one messaging activity of the alert messaging system.

Blocking of the selected at least one messaging activity, within the method in an alert messaging system, may comprise blocking at least one non-prioritized messaging activity of said alert messaging system.

To prohibit overload and minimize the risk of congestions in the core and radio network, embodiments of the present disclosure can optionally comprise modifying a message sending strategy, i.e. a blocking strategy, to block non-prioritized message sending activities, in addition to changing a barring strategy with which barring of non-prioritized subscriber activities is performed in the network.

Blocking is a temporary measure to protect the mobile network from overload and congestions caused by other, i.e. non-alert message, traffic during emergency situations and/or while sending alert messages, a pre-defined or new blocking strategy settings can be downloaded via SAF control data over e.g. SOAP to the AMN and used by said AMN. For instance only sending of alert messages or only alert message sending for certain alert services types or priorities, may be allowed.

To protect the mobile network from overload and congestions caused by non alert message traffic during emergency situations, the AMW node may start with initiating blocking of all message sending activities in AMN but sending of Alert messages, before and then initializing non-prioritized traffic barring in the AMN.

The AMW node then downloads via store and forward (SAF) control data over e.g. SOAP a pre-defined or new blocking strategy, e.g. allowing only sending of alert messages or allowing only alert message sending for certain alert services types or priorities.

Operator determined blocking of non-prioritized message sending activities may either be used as a precaution for all message sending activities except alert message sending, or be decided on a per occasion basis

Blocking of message sending activities is based upon service type and/or invoked application for the MSISDN in question. Message blocking settings, i.e. the message sending strategy, are defined and updated through SAF control protocol over e.g. a SOAP interface. Normally, when receiving a request for alert message sending from a managing node the AMW node initiates blocking of all message sending activities in the AMN, but sending of alert messages, i.e. AMW node initiates the AMN message sending strategy to service type: "send only alert messages". This means that all non-alert message sending service types, such as all normal, bulk message or location-based advertising message sending, is prohibited and only alert message sending is allowed.

If alert messages for several alert services and affected geographical areas is going to be sent, i.e. several alert services are invoked from the same or different managing nodes, then the AMW may determine which geographical area/application has the highest priority and either blocks the rest of the geographical areas/applications or shares its resources between more than one or all geographical areas/applications. If sending alert messages for several alert services with the same priority, the message sending strategy is normally set to "allow only sending of alert messages". This means that only alert messages are sent and the sending resources are shared between all alert services.

To be able to roll-back to earlier, default or initial blocking settings, i.e. restore this information in the AMN after alert message sending, a method of blocking of non-prioritized message sending activities may comprise uploading current blocking and barring message sending strategy via SAF control protocol and storing said message sending strategy from the AMN to the AMW node, prior to blocking any activities.

To change a pre-defined or occasional-specific message sending strategy comprising blocking for the AMN, e.g. when activating alert message sending, the AMW node downloads via SAF control data over e.g. SOAP new settings defining whether to:

allow all message sending, e.g. alert messages as well as bulk and advertising message sending;

- allow only sending of alert messages, i.e. allow sending of messages for all alert service and block all other message sending;

allow only alert message sending for certain alert services and block all other message sending activities; or

do not allow any message sending at all; e.g. during re-configurations or changes in the network.

When the alert message sending is completed, the initial message sending strategy for AMN is downloaded and initiated from the AMW node to the AMN to allow the AMN to resume previous sending activities. Figure 7 schematically illustrates an AMW node or an alert messaging service node

AMN.

The alert middleware node 700 for managing of traffic in a communication network during an emergency situation, i.e. in an emergency mode, comprises:

- a processor 702, and

a memory 704 storing computer program comprising computer program code which, when run in the processor, as a response to a receiving 400 a request to enter into an emergency mode, said request comprising information about a specific geographical area of the communication network, causes the alert middleware node 700 to: - determine 402 which UEs are located in said specific geographical area,

monitor 404 the present traffic in the specific geographical area, said present traffic being of different types,

select 406 at least one traffic type according to a priority list of said different traffic types, based on the received request and the monitored present traffic, and - send 408 a barring request to an AMN enabling barring of non-prioritized subscriber activities.

The alert messaging service node 700 for sending traffic managing messages in a communication network during an emergency situation, i.e. in an emergency mode, comprises:

- a processor 702, and

a memory 704 storing computer program comprising computer program code which, when run in the processor, as a response to a receiving a traffic barring request from an alert middleware node, wherein the request requests 500 barring of at least one selected traffic type in a specific geographical area of the communication area, causes the alert messaging service node to:

initiate 502 barring of said selected at least one traffic type for the UEs located in the specific geographical area, based on the received traffic barring request.

The present disclosure also comprises computer program products for the methods as discussed herein above.

For instance, according to some embodiments there is provided a computer program product for managing of communication network traffic in an alert middleware node.

Figure 8 schematically illustrates a computer program product 800 comprising a computer program for managing of communication network traffic in an AMW node. According to some embodiments of the present disclosure, there is provided a computer program product 800 comprising computer program code which, when run in a processor of an alert middleware node, as a response to receiving a request to enter into an emergency mode, said request comprising information about a specific geographical area of the communication network, causes the AMW node 702 to:

select at least one traffic type according to a priority list of said different traffic types, based on the received request and the monitored present traffic, and send a barring request to an AMN enabling barring of non-prioritized subscriber activities.

Figure 8 may also schematically illustrate a computer program product 800 comprising a computer program for managing of communication network traffic in an AMN.

According to some embodiments of the present disclosure, there is provided a computer program product 800 comprising a computer program code which, when run in the processor of the AMN, as a response to receiving a traffic barring request from an AMW node, wherein the request requests barring of at least one selected traffic type in a specific geographical area of the communication area, causes the processor to:

process the received traffic barring request; and

initiate barring of said selected at least one traffic type for the UEs located in the specific geographical area, based on the processed barring request.

One skilled in the art will also appreciate that the present disclosure is not limited to the embodiments or the combined embodiments disclosed in the enclosed drawings and the foregoing description, which are presented for purposes of illustration only, but it can be implemented in a number of different ways, as defined by the following claims.

It should be appreciated by those skilled in the art that the conception and specific embodiment disclosed might be readily utilised as a basis for modifying or designing other structures for carrying out the same purposes of the present disclosure. For instance, nodes may be combined or co-located but are preferably separated due to that nodes handle different interfaces and protocols. It should also be realised by those skilled in the art that such equivalent constructions do not depart from the spirit and scope of the disclosure as set forth in the appended claims.

Embodiments of this disclosure have the following advantages:

By locating which UEs are located in the specific geographical area, and alert messaging only people within the specific geographical area, people outside the specific geographical area are not worried. In addition, by alert messaging only those affected, i.e. those within the specific geographical area, message sending will not unnecessarily contribute to traffic increase.

It is a further advantage to monitor the present traffic in the specific geographical area, gaining information about the traffic situation in the affected area, on which barring decision can be based.

It must be emphasized that this disclosure may be varied in many ways.

The elements of an embodiment of this disclosure may be physically, functionally and logically implemented in any suitable way. Indeed, the functionality may be implemented in a plurality of units or as part of other functional units. As such, this disclosure may be implemented in a plurality of units, or maybe physically and functionally distributed between different units and processors.

It is made clear that presented embodiments may well be combined forming new embodiments not explicitly described herein. Explicit embodiments of methods in one or more nodes as presented herein may thus be combined with embodiments of the corresponding nodes, producing embodiments of nodes comprising features and/or functions of said embodiments of methods of the present disclosure.

In the claims, the term "comprises/comprising" does not exclude the presence of other elements or steps. Additionally, although individual features may be included in separate claims, these may be combined, and the inclusion in different claims does not imply that a combination of features is not feasible and/or advantageous. In addition, singular references do not exclude a plurality. The terms "a", "an", "first", "second" etc do not preclude a plurality.

Reference signs in the claims are provided merely as a clarifying example and shall not be construed as limiting the scope of the claims in any way.

Although this disclosure has been described above with reference to specific embodiments, it is not intended to be limited to the specific form set forth herein. Rather, this disclosure is limited only by the accompanying claims and, other embodiments than the specific above are equally possible within the scope of these appended claims.

Claims

1. A method in an alert messaging system (120) for managing traffic in a communication network during an emergency situation, i.e. in an emergency mode, the method comprising:

receiving (600) a request to enter into an emergency mode, said request comprising information about a specific geographical area of the communication network,

determining (602) which user equipments, UEs, are located in said specific geographical area,

monitoring (604) the present traffic in the specific geographical area, said present traffic being of different types,

selecting (606) at least one traffic type according to a priority list of said different traffic types, based on the received request and the monitored present traffic, and initiating (608) emergency-related barring of said selected at least one traffic type for UEs located in the specific geographical area.

2. The method in an alert messaging system (120) according to claim 1, wherein the priority list comprises said different traffic types in the following order of decreasing priority: mobile terminating voice, mobile originating voice, and mobile originating messaging.

3. The method in an alert messaging system (120) according to claim 1 or 2, wherein the UEs located in the specific geographical area in initiating emergency-related barring, comprises UEs within said specific geographical area being either only those UEs having specific mobile subscriber integrated services digital network numbers, MSBDNs, and/or or international mobile subscriber identities, EVISIs, or all UEs except for emergency or rescue personal UEs.

4. The method in an alert messaging system (120) according to any of claims 1-3, wherein determining (602) which UEs are located in said specific geographical area, comprises positioning of said UEs by using one of more of the following methods: passive location methods, active basic location methods and active enhanced location methods.

5. The method in an alert messaging system (120) according to any of claims 1-4, wherein the present traffic in monitoring (604) of the present traffic, comprises radio traffic information of at least one of: cell radio status information, radio traffic load information of signalling load on a radio channel per cell, and cell radio traffic capacity information, in a Base Station Controller, BSC, Radio Network Controller, RNC, and traffic data from interface probes on A-bis and/or Iub interfaces.

6. The method in an alert messaging system (120) according to any of claims 1 -5 , wherein initiating (608) emergency-related barring comprises sending an emergency related barring initiation message, enabling an HLR to send an emergency related traffic barring message to a MSC/SGSN that serves UEs located in the specific geographical area.

7. The method in an alert messaging system (120) according to claim 6, wherein the

emergency related barring initiation message comprises an any time modification, ATM, message comprising emergency related barring settings of said selected at least one traffic type.

8. The method in an alert messaging system (120) according to claim 6 or 7, wherein initiating (608) emergency related barring further comprises sending an operator determined barring, ODB, request command prior to sending the emergency related barring initiation message, wherein the ODB request command requests the present ODB settings for the home public land mobile network, PLMN, for MSISDNs and/or EVISIs, located in said specific geographical area.

9. The method in an alert messaging system (120) according to claim 8, wherein the ODB request command comprises an any time subscription information, ATSI, command requesting said present ODB settings.

10. The method in an alert messaging system (120) according to claim 9, further comprising receiving an ATSI response comprising said present ODB settings, prior to sending the emergency-related barring initiation message.

11. The method in an alert messaging system (120) according to claim 10, further comprising exiting the emergency mode, based on receipt of a debarring request or on detection that the UEs in the geographical area to which an alert message has been sent, have received said alert message, and sending an ATM message with said present ODB settings to regain non-emergency mode subscriber barring settings.

12. The method in an alert messaging system (120) according to any of claims 1 -5 , wherein initiating (608) emergency-related barring comprises sending a emergency-related traffic barring message to serving MSCs/SGSNs.

13. The method in an alert messaging system (120) according to claim 12, wherein the emergency-related traffic barring message comprises an insert subscriber data, ISD, message enabling the MSC/SGSN to set barring settings of said selected at least one traffic type for UEs that are located in said specific geographical area.

14. The method in an alert messaging system (120) according to claim 12 or 13, further comprising exiting the emergency mode based on receipt of a debarring request or on detection that the UEs in the geographical area to which an alert message has been sent, have also received an alert message, and sending another ISD message with ODB settings for all provided services to the MSC/SGSN.

15. The method in an alert messaging system (120) according to any of claims 1-14, further comprising:

selecting at least one messaging activity of the alert messaging system, from a list of non-alert messaging activities of said alert messaging; and

blocking the selected at least one non-prioritized messaging activity of the alert messaging system.

16. The method in an alert messaging system (120) according to claim 15, further comprising monitoring present traffic in the alert messaging system during the emergency situation, and wherein selecting at least one messaging activity is based on said monitoring of said present traffic in the alert messaging system.

17. A method in an alert middleware node (106, 202, 302) for managing of traffic in a

communication network during an emergency situation, i.e. in an emergency mode, the method comprising: receiving (400) a request to enter into an emergency mode, said request comprising information about a specific geographical area of the communication network,

determining (402) which user equipments, UEs, are located in said specific geographical area,

monitoring (404) the present traffic in the specific geographical area, said present traffic being of different types,

selecting (406) at least one traffic type according to a priority list of said different traffic types, based on the received request and the monitored present traffic, and sending (408) an emergency-related barring request to an alert messaging service node, AMN, enabling barring of non-prioritized subscriber activities.

The method in an alert middleware node (106, 202, 302) according to claim 17, wherein the priority list comprises said different traffic types in the following order of decreasing priority: mobile terminating voice, mobile originating voice, and mobile originating messaging.

The method in an alert middleware node (106, 202, 302) according to claim 17 or 18, wherein determining (402) which UEs are located in said specific geographical area, comprises positioning of said UEs by using one of more of the following methods: passive location methods, active basic location methods and active enhanced location methods.

The method in an alert middleware node (106, 202, 302) according to any of claims 17- 19, wherein the present traffic in monitoring (404) of the present traffic, comprises radio traffic information of at least one of: cell radio status information, radio traffic load information of signalling load on a radio channel per cell, and cell radio traffic capacity information, in a base station controller, BSC, radio network controller, RNC, and traffic data from interface probes on A-bis and/or Iub interfaces.

A method in an alert messaging service node (108, 204, 304) for sending traffic managing messages in a communication network during an emergency situation, i.e. in an emergency mode, the method comprising: receiving (500) a traffic barring request from an alert middleware node, wherein the request requests barring of at least one selected traffic type in a specific geographical area of the communication area, and

initiating (502) emergency-related barring of said selected at least one traffic type for the UEs located in the specific geographical area, based on the received traffic barring request.

22. The method in an alert messaging service node (108, 204, 304) according to claim 21, wherein the UEs located in the specific geographical area in initiating emergency-related barring, comprises UEs within said specific geographical area being either only those

UEs having specific mobile subscriber integrated services digital network numbers, MSISDNs, and/or or international mobile subscriber identities, EVISIs, or all UEs except for emergency or rescue personal UEs.

23. The method in an alert messaging service node (108, 204, 304) according to claim 21 or 22, wherein initiating (502) emergency-related barring comprises sending an emergency- related barring initiation message to a home location register, HLR, enabling the HLR to send an emergency-related traffic barring message to a MSC/SGSN that serves UEs located in the specific geographical area.

24. The method in an alert messaging service node (108, 204, 304) according to claim 23, wherein the emergency-related barring initiation message comprises an any time modification, ATM, message, comprising emergency related barring settings of said selected at least one traffic type.

25. The method in an alert messaging service node (108, 204, 304) according to claim 23 or 24, wherein initiating (502) emergency related barring further comprises sending an operator determined barring, ODB, request command prior to sending the emergency related barring initiation message, wherein the ODB request command requests the present ODB settings for home public land mobile network, PLMN, for MSISDNs and/or

IMS Is, located in said specific geographical area.

26. The method in an alert messaging service node (108, 204, 304) according to claim 25, wherein the ODB request command comprises an any time subscription information, ATSL command requesting said present ODB settings.

27. The method in an alert messaging service node (108, 204, 304) according to claim 26, further comprising receiving an ATSI response comprising said present ODB settings, prior to sending the emergency-related barring initiation message.

28. The method in an alert messaging service node (108, 204, 304) according to claim 21 or 22, wherein initiating (502) emergency related barring comprises sending a traffic barring message to a MSC/SGSN that serves UEs located in the specific geographical area.

29. The method in an alert messaging service node (108, 204, 304) according to claim 28, wherein the traffic barring message comprises an insert subscriber data, ISD, message.

30. The method in an alert messaging service node (108, 204, 304) according to claim 29, wherein the ISD message comprises a calling global title, CgGT, identity of said alert messaging service node if it is detected that policing is not performed in a VLR of a MSC/SGSN serving UEs located in the geographical area.

31. The method in an alert messaging service node ( 108, 204, 304) according to claim 30, wherein the method further comprises receiving ISD responses from the MSC/SGSN.

32. The method in an alert messaging service node (108, 204, 304) according to claim 29, wherein the ISD message comprises a calling global title, CgGT, identity of a HLR for UEs located in the geographical area, if it is detected that policing is being performed in a VLR of a MSC/SGSN serving UEs located in the geographical area, enabling obtaining information about an ISD response by probing the interface between the HLR for UEs located in the specific geographical area and the MSC/SGSN serving UEs located in the specific geographical area.

33. The method in an alert messaging service node (108, 204, 304) according to any of claims 21-32, further comprising: selecting at least one messaging activity of the alert messaging system, from a list of non-alert messaging activities of said alert messaging; and

34. The method in an alert messaging service node (108, 204, 304) according to claim 33, further comprising monitoring present traffic in the alert messaging system during the emergency situation, and wherein selecting at least one messaging activity is based on said monitoring of said present traffic in the alert messaging system.

35. An alert middleware node (106, 202, 302, 700) for managing of traffic in a

communication network during an emergency situation, i.e. in an emergency mode, the alert middleware node comprising:

a processor (702), and

a memory (704) storing computer program comprising computer program code which,

when run in the processor, as a response to a receiving (400) a request to enter into an emergency mode, said request comprising information about a specific geographical area of the communication network, causes the alert middleware node (106, 202, 302, 700) to:

determine (402) which user equipments, UEs, are located in said specific geographical area,

monitor (404) the present traffic in the specific geographical area, said present traffic being of different types,

select (406) at least one traffic type according to a priority list of said different traffic types, based on the received request and the monitored present traffic, and send (408) a barring request to an alert messaging service node, AMN, enabling barring of non-prioritized subscriber activities.

36. An alert messaging service node (108, 204, 304, 700) for sending traffic managing

messages in a communication network during an emergency situation, i.e. in an emergency mode, the alert middleware node comprising:

a processor (702), and a memory (704) storing computer program comprising computer program code which,

when run in the processor, as a response to a receiving a traffic barring request from an alert middleware node, wherein the request requests (500) barring of at least one selected traffic type in a specific geographical area of the communication area, causes the alert messaging service node to:

initiate (502) barring of said selected at least one traffic type for the UEs located in the specific geographical area, based on the received traffic barring request.

37. An alert messaging system (120) for managing of traffic in a communication network during an emergency situation, i.e. in an emergency mode, the system comprising: an alert middleware node (106, 202, 302, 700) according to claim 35; and an alert messaging service node (108, 204, 304, 700) according to claim 36.

38. A computer program product (800) comprising computer program code which, when run in a processor (702) of an alert middleware node (700), as a response to receiving (400) a request to enter into an emergency mode, said request comprising information about a specific geographical area of the communication network, causes the alert middleware node (700) to:

39. A computer program product (800) comprising computer program code which, when run in a processor (702) of alert messaging service node (700), as a response to receiving a traffic barring request from an alert middleware node, wherein the request requests (500) barring of at least one selected traffic type in a specific geographical area of the communication area, causes the alert messaging service node to: initiate (502) barring of said selected at least one traffic type for the UEs located in the specific geographical area, based on the received traffic barring request.