Abstract: A messaging server improves interworking of the Group-chat feature (such as defined in Rich Communications Services (RCS)) with short message services such as SMS. It matches chat invitations in an effective manner. When an RCS-User invites an SMS-User to an RCS Group-chat session, the identification of the RCS-User in the Group-chat to the SMS-User is via the MSISDN of the RCS-User. Using the MSISDN of the RCS-User in the RCS Group-chat invitation to the SMS-User will provide a direct match with the RCS-User MSISDN in the address-book of the SMS-User and therefore provide immediate clarity from who this Group-chat invitation was received. The SMS-User can accept or reject the Group-chat invitation by returning the proper response as requested in the invitation.

Abstract: The present disclosure provides a method of routing a short message to a user. According to the method, an SMSC sends a routing request to a HLR or HSS of the terminating user. The HLR or HSS has static provisioning settings for users and relays the request according to these settings. The HLR or HSS relays the request to the IP-SM-GW, which dynamically determines if the terminating user has attached to an IMS network and accordingly decides on onward routing of the message over circuit switched or IMS network elements. The present disclosure also provides a mobile network apparatus that is configured to perform the method.

Abstract: A signaling controller (DSC) performs dynamic management in networks such as Evolved Packet Core (EPC) networks that rely on Diameter signaling interfaces. The controller executes in real time a self-adjusting algorithm that achieves user-based service continuity during signaling storms or congestion situations. The algorithm is self-adjusting on the basis of comparing a signaling and peer group values which are dynamically determined. The dynamic determination of these values is based on items such as signaling message weight and a base value for a network user.

Abstract: A gateway (G) interfaces with a packet (IM) network (N) a mobile (GSM) network (N2), a HLR, an IM server (S1) and an SMSC (S2). The gateway (G) has a trajectory database (D) which is dynamically maintained and is accessed to determine in real time the optimum communication paths for messages.

Abstract: A communication network messaging server (1, 100) and user devices (2, 102) have control channels (10, 21, 110) to send and receive control data. The server sends to an originating device control data indicating recipient availability, status, and/or presence prior to the originating device sending a message. The server control channel (110) includes a multiplexer (104) for streaming between a user message channel and the control channel and maintains device registration data, status data, presence data, and user group management data. The server (100) enables end user initiated availability, status, and/or presence updates to be shared with the messaging network and with recipient devices via said control channel.

Abstract: A receiving network detects fraudulent messages received via a grey route. At a start of a session, a message delivery request is sent to a Short Message Service (SMS) node in the receiving network. This sends a request to a Home Location Register (HLR) of a supposedly originating network for routing information concerning an originator. Upon receiving a response from the HLR, it requests validation of retrieved information, to validate both the originator and the originating network. The SMS node also makes an HLR look-up for a recipient, before performing message delivery.

Abstract: A message flooding prevention system (1) has multiple interceptors (2, 3, 4), each with an interceptor unit linked with an RCS server, and SMSC, or an MMSC. The interceptors (2, 3, 4) are connected to flood detect nodes (10) 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 (10) 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 (10) save the code to one of a set of database buckets (21), 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.

Abstract: A home router network element assigns a correlation key including an LMS1 to an MSISDN in such a way that the risk of short message mis-delivery to a wrong mobile subscriber is very much reduced. This is achieved by projection of MSISDN ranges on correlation key ranges while the correlation key is still unpredictable. The level of correlation key unpredictability is determined by applicable numbering plans and for practical purposes avoids the chance that an MT message originated by a fraudulent party is successfully delivered via the home router.

Abstract: A message flooding prevention system (1) has multiple interceptors (2, 3, 4), each with an interceptor unit linked with an RCS server, and SMSC, or an MMSC. The interceptors (2, 3, 4) are connected to flood detect nodes (10) 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 (10) 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 (10) save the code to one of a set of database buckets (21), 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.

Abstract: An originating SMSC in Network A issues an SRI-SM towards the HLR of a recipient (User B in Network B). One of a number of N Platforms or Message Controllers (“MCOs”) intercepts the SRI-SM. Instead of passing on the SRI-SM, the MCO terminates it and performs a full decode of all fields, specifically extracting the recipient MSISDN from it. The MCO then constructs a new SRI-SM for the same MSISDN, but forcing the new request to ask for all available data, including, but not necessarily limited to visited-MSC address, SGSN address and IP-SM-GW address. When a response is received the MCO generates a fresh query response for the originating SMSC instead of merely routing on the response which it receives. If the MCO is programmed to provide a false address for smart services it incorporates the false address in the query response which it generates.

Abstract: 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.

Abstract: A gateway (G) interfaces with a packet (IM) network (N) a mobile (GSM) network (N2), a HLR, an IM server (S1) and an SMSC (S2). The gateway (G) has a trajectory database (D) which is dynamically maintained and is accessed to determine in real time the optimum communication paths for messages.

Abstract: An originating SMSC in Network A issues an SRI-SM towards the HLR of a recipient (User B in Network B). One of a number of N Platforms or Message Controllers (“MCOs”) intercepts the SRI-SM. Instead of passing on the SRI-SM, the MCO terminates it and performs a full decode of all fields, specifically extracting the recipient MSISDN from it. The MCO then constructs a new SRI-SM for the same MSISDN, but forcing the new request to ask for all available data, including, but not necessarily limited to visited-MSC address, SGSN address and IP-SM-GW address. When a response is received the MCO generates a fresh query response for the originating SMSC instead of merely routing on the response which it receives. If the MCO is programmed to provide a false address for smart services it incorporates the false address in the query response which it generates.

Abstract: A communication network messaging server (1, 100) and user devices (2, 102) have control channels (10, 21, 110) to send and receive control data. The server sends to an originating device control data indicating recipient availability, status, and/or presence prior to the originating device sending a message. The server control channel (110) includes a multiplexer (104) for streaming between a user message channel and the control channel and maintains device registration data, status data, presence data, and user group management data. The server (100) enables end user initiated availability, status, and/or presence updates to be shared with the messaging network and with recipient devices via said control channel.

Abstract: A home router network element assigns a correlation key including an LMS1 to an MSISDN in such a way that the risk of short message mis-delivery to a wrong mobile subscriber is very much reduced. This is achieved by projection of MSISDN ranges on correlation key ranges while the correlation key is still unpredictable. The level of correlation key unpredictability is determined by applicable numbering plans and for practical purposes avoids the chance that an MT message originated by a fraudulent party is successfully delivered via the home router.

Abstract: A message flooding prevention system (1) has multiple interceptors (2, 3, 4), each with an interceptor unit linked with an RCS server, and SMSC, or an MMSC. The interceptors (2, 3, 4) are connected to flood detect nodes (10) 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 (10) 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 (10) save the code to one of a set of database buckets (21), 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.

Abstract: A message router comprises a message controller with service logic functions, and a state database. It receives and processes message segments, maintains state of single and concatenated messages, and applies services to the messages. A routing and discrimination engine accesses a selected state database among an associated database and distributed state databases. The controller operates in a transparent-relay mode in which a message is relayed to a network element and the response from the network element is returned directly to an originator. The relaying may be performed using SCCP relaying. The controller can operate in a transparent-proxy mode in which it generates a fresh message and sends it to a network element and receives the response from the network element, and in turn returns a response to the originator.

Abstract: In a message routing method an application or device sends a message in a mobile network, the message having a status report request. The message is delivered via network elements including a router, and the router routs a status report to the originating device or application which cannot accept it. The router communicates with a message service centre having store-and-forward capability, and the message service centre performs a re-try of sending the status report to the originating device or application. The status report may be embedded in an otherwise conventional message to the service centre, which may for example be an SMSC. The status report may be embedded in a conventional SMC-MO PDU, without affecting the GSM or other network protocol.

Abstract: 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.

Abstract: A security system for a mobile network (1) has a gateway (3) for receiving messages from outside the network and a HLR (10) storing mobile terminal location information. The security system monitors in real time messages entering the network through the gateway (3), and decides according to said monitoring if messages are likely to be unsolicited. The system may block messages which are likely to be unsolicited. The system monitors a source address of a look-up request and a source address of a corresponding message, and decides that the message is likely to be unsolicited if its source address is different from that of the corresponding look-up request. The system further comprises a data store (5) and a timer (6), and stores look-up requests received from the gateway in the data store, and decides that a message is likely to be unsolicited if a corresponding look-up request has not been received within a pre-set time period.