Markport Limited

Klaas Wijbrans

Michel De Boer

Hugh Martin Carr

Jim Plimmer

Aram Krol

Wim Wedershoven

Igor Radovanović

Tanir Özçelebi

Ron Jesterhoudt

Louis Van Der Stam

Maurice Wollersheim

Tanir Özcelebi

Igor Radovanovic

Sander Brouwer

David Geen

Wollersheim Maurice

Johan Ruiter

Boudewijn Van De Moesdijk

Thijs Vermoolen

Petr Havel

Martin Bergink

A message flooding prevention system () has multiple interceptors (), each with an interceptor unit linked with an RCS server, and SMSC, or an MMSC. The interceptors () are connected to flood detect nodes () for receiving messages at a point in a communications network, extracting data from a message, generating at least one code from extracted data, and comparing the code or codes with one or more previous codes. The flood detect nodes () determine according to the comparison if the received message is suspected to be a flooding message and if so, performs code generation including hashing. The flood detect nodes () save the code to one of a set of database buckets (), each bucket being associated with a code, and select a bucket according to the generated code, and increment a fill parameter of the selected bucket.

Message flooding prevention in messaging networks

A messaging method is implemented by a system in a mobile network in which there are mobile devices including devices A, B, C, D, and E. An originating device sends a message addressed to multiple terminating devices. The system receives the messages and correlates them and routes them to the terminating devices. The system correlates the messages by grouping them according to originating device and sending time frame. The system allocates a global title record address from a pool for the session. The system forwards the messages with an MT-FSM, in which the originating device information is included in the message body, and the recipient address is that of the specific terminating device. The system transmits a confirmation message to the originating device.

Messaging system and method

The invention provides real time dynamic resource management to improve end-to-end QoS by mobile devices regularly updating a resource availability server (RAS) with resource update information. Examples of resource update information are device battery status, available memory, session bandwidth, delay, packet loss, and jitter, network element storage capacity, network element processing power. This information is made available by the RAS. In addition, the RAS generates and maintains predictive models and makes available predictive data from these models. Network elements and devices retrieve this information in the form of notifications from the RAS or by way of querying the RAS. The network elements and devices, based on these predictions, act to negotiate sessions to optimise QoS. In one embodiment the RAS is updated by only mobile devices subscribed to the operator which hosts the RAS. The update information is addressed to the RAS as a stand-alone entity. However, it is envisaged that the server may be hosted by multiple operators and may receive updates from devices subscribed to different operators. Also, it is envisaged that not only mobile devices but also network elements such as MMSCs may send update information.

Network resource management

When a device is switched off, all messages for that device are stored in different distributed service centers. For example, the message from user A may be stored in SMSC A and a message from user B in SMSC B where both subscribers and respective SMSCs can even belong to different networks. When the device is switched on again it notifies its presence to the network (performed by the MSC indicating this to the HLR). As a result of this alert, different service centers that have messages pending for that device will be notified that the device has come on-line again (performed by the HLR notifying SMSC A and SMSC B). Instead of directly sending out all messages, as in the prior art, each service center instead schedules the messages in an internal queue for delivery according to a local control scheme, which achieves synchronized delivery from multiple distributed SMSCs even though there is no centralised control. Each service center maps the 'age' of the message on its time axis as the time-to-deliver the message to the device. The deliveries are then sent out according to the derived schedule. As independent service centers all will base their decisions on the same length of the delivery schedule and same maximum retention time, the message deliveries of the different service centers will be interleaved with one another. This ensures that for significant time differences, messages from different service centers will still arrive in order at the device.

Message delivery in mobile networks

An application () in a mobile network, receives an EIR trigger (MAP CHECK_IMEI). The application generates a signature derived from a device identifier (IMEI) and a subscriber identifier (e.g. IMSI), the signature not having a semantic meaning as it is pseudo-randomly generated. The application () checks if the signature exists in a signature store (); and if not, determines that the device/subscriber combination has not been detected in the network within a certain preceding time window, and stores the signature in the store, with an associated timestamp. It also transmits a notification to an external system such as a device management system. If the signature is already in the database, the application determines that the device/subscriber combination already exists in the network and updates a time stamp associated with the signature in the store to indicate the last time the signature was processed.

Device detection in mobile networks

Growing community of inventors

Rijen, Netherlands

Klaas Wijbrans