System and method for operating intravendor and intervendor messaging systems

• US 20070066281A1
• Filed: 09/28/2006
• Published: 03/22/2007
• Est. Priority Date: 05/31/2002
• Status: Active Grant

• Current Assignee: Nokia Corporation
• Original Assignee: Nokia Corporation
• Inventors: Savinen, Teppo, Warsta, Ville
• Granted Patent: US 8,359,018 B2
• Time in Patent Office: Days
• US Class Current: 455/412.100
• CPC Class Codes: H04L 12/1854 with non-centralised forwarding system, e.g. chaincast
• CPC Class Codes: H04L 51/23 Reliability checks, e.g. acknowledgments or fault reporting
• CPC Class Codes: H04L 51/58 Message adaptation for wireless communication
• CPC Class Codes: H04L 67/04 specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/10015 Access to distributed or replicated servers, e.g. using brokers
• CPC Class Codes: H04L 67/1008 based on parameters of servers, e.g. available memory or workload monitoring of computer activity G06F11/30
• CPC Class Codes: H04L 67/1014 based on the content of a request
• CPC Class Codes: H04L 67/1019 Random or heuristic server selection
• CPC Class Codes: H04L 67/55 Push-based network services
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols
• CPC Class Codes: H04W 4/12 Messaging; Mailboxes; Announcements
• CPC Class Codes: H04W 88/182 Network node acting on behalf of an other network entity, e.g. proxy
• CPC Class Codes: H04W 88/184 Messaging devices, e.g. message centre

Abstract

A system and method for enabling the operation of intervendor and intravendor messaging service systems within an operator network includes correctly routing data messages and handshaking messages between the various system components. In one aspect, the present invention uses the uniform resource identifier of a particular messaging system to route one or more handshaking messages from a target terminal to the particular messaging system. In another aspect, the present invention uses a message transaction identification embedded in the handshaking message to direct the handshaking message to the correct messaging service system. In one embodiment, the transaction identification is analyzed by a load balancing switch to determine the location of the particular messaging service system. In another embodiment, one or more of the several messaging service systems in the operator network are used to analyze the transaction identification to determine the location of the particular messaging service system.

Claims

1. A messaging service system operating in an operator network including a plurality of messaging service systems;

comprising;

a receiver configured to receive a handshaking message directed to the messaging service system from a terminal; and

circuitry configured to route the handshaking messages to one or more other messaging service systems of the plurality of messaging service systems if the handshaking message is not directed to the messaging service system.

2. The messaging service system of claim 1, wherein the routing circuitry is configured to transmit the handshaking messages to a random messaging service system of the plurality of messaging service systems.

3. The messaging service system of claim 1, wherein the routing circuitry is configured to transmit the handshaking messages to a particular messaging service system of the plurality of messaging service systems.

4. The messaging service system of claim 1, wherein the routing circuitry is configured to analyze the handshaking messages and to transmit the handshaking messages to another messaging service system based on the analysis.

5. The messaging service system of claim 1, further comprising a transmitter configured to incorporate a transaction identification into a notification message transmitted to the terminal, wherein the handshaking messages include the transaction identification.

6. The messaging service system of claim 1, wherein the routing circuitry is configured to analyze a transaction identification and determine a particular messaging service system to which the handshaking message is directed.

7. The messaging service system of claim 1, wherein:

the receiver is configured to receive the handshaking message routed from a first messaging service system; and

the routing circuitry is configured to analyze the handshaking message to determine if the handshaking message is directed to the messaging service system.

8. The messaging service system of claim 7, wherein the routing circuitry is configured to route the message to a second messaging service system if the handshaking message is not directed to the messaging service system.

9. The messaging service system of claim 7, wherein the routing circuitry is configured to route the message to the plurality of messaging service systems in the operator network if the handshaking message is not directed to the messaging service system.

10. A method comprising:

receiving at least one handshaking message, indicating a status of at least one corresponding message transaction, at one of a plurality of messaging service systems available in an operator network;

determining whether the at least one handshaking message was directed to the receiving one of the messaging service systems; and

routing the at least one handshaking message to one or more other ones of the plurality of messaging service systems if the at least one handshaking message was not directed to the receiving one of the messaging service systems.

11. The method of claim 10, wherein determining whether the at least one handshaking message was directed to the receiving one of the messaging service systems comprises analyzing, by the receiving one of the messaging service systems, a transaction identifier affiliated with the messaging service system to which the at least one handshaking message was directed.

12. The method of claim 11, wherein routing the at least one handshaking message comprises routing the at least one handshaking message from the receiving one of the messaging service systems to the messaging service system to which the transaction identifier was affiliated.

13. The method of claim 10, further comprising providing an address of the messaging service system, to which the at least one handshaking message will be directed, to a network element that will subsequently provide the at least one handshaking message to the receiving one of the messaging service systems.

14. The method of claim 10, wherein routing the at least one handshaking message to one or more other ones of the plurality of messaging service systems comprises the receiving one of the plurality of messaging service systems broadcasting the at least one handshaking message to all of the other ones of the plurality of messaging service systems.

15. The method of claim 10, wherein routing the at least one handshaking message to one or more other ones of the plurality of messaging service systems comprises:

transferring the at least one handshaking message from the receiving one of the plurality of messaging service systems to second one of the plurality of messaging service systems; and

if the at least one handshaking message was not intended for the second messaging service system, repeatedly transferring the at least one handshaking message from messaging service system to messaging service system until the messaging service system to which the at least one handshaking message was directed is reached.