Intelligent messaging network server interconnection

• US 8,090,856 B1
• Filed: 11/03/2000
• Issued: 01/03/2012
• Est. Priority Date: 01/31/2000
• Status: Expired due to Term

• Current Assignee: TeleCommunication Systems Inc (Comtech Telecommunications Corporation)
• Original Assignee: TeleCommunication Systems Inc (Comtech Telecommunications Corporation)
• Inventors: Bonefas, Rudy G., Sobchak, Richard K., Zombek, James M.
• Primary Examiner(s): Bruckart, Benjamin R
• Application Number:
  US09/704,535
• Time in Patent Office: 4,078 Days
• Field of Search: 709/200, 709/203, 709/217, 709/219, 709/220, 709/222, 709223-226, 709230-238, 709227-229, 709/250
• US Class Current: 709/230
• CPC Class Codes: H04L 1/0001 Systems modifying transmission characteristics according to link quality, e.g. power backoff adaptive data allocation for multicarrier modulation H04L5/0044; controlling transmission power for radio systems H04W52/04
• CPC Class Codes: H04L 41/0803 Configuration setting
• CPC Class Codes: H04L 63/0428 wherein the data content is protected, e.g. by encrypting or encapsulating the payload
• CPC Class Codes: H04L 63/101 Access control lists [ACL]
• CPC Class Codes: H04L 63/1416 Event detection, e.g. attack signature detection
• CPC Class Codes: H04L 67/104 Peer-to-peer [P2P] networks
• CPC Class Codes: H04L 69/16 Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
• CPC Class Codes: H04L 69/18 Multiprotocol handlers, e.g. single devices capable of handling multiple protocols
• CPC Class Codes: H04L 69/22 Parsing or analysis of headers
• CPC Class Codes: H04W 12/084 using delegated authorisation, e.g. open authorisation [OAuth] protocol

Abstract

An intelligent messaging network provides multiple software development kits (SDKs) to assist, e.g., engineers in developing client and server applications. The SDKs can contain a consistent set of application program interfaces (APIs) and a set of platform specific libraries for all intelligent messaging network supported platforms and networks. In addition to the SDKs, the intelligent messaging network can provide developers a resource kit including a set of tools to assist the developers when designing, implementing, and testing their client and server applications. The intelligent messaging network can provide a mobile client and server SDK environment to assist engineers developing client applications and servers. The SDKs can provide an easy to use APIs and a set of platform specific libraries to perform, e.g., compression, network management services, server-to-server communication, server registration/de-registration, and reliable message transport services.

Claims

1. A method for supporting a communications network, comprising:

establishing communications between a physical messaging network server and a wireless device utilizing a hybrid User Datagram Protocol (UDP) connectionless transport protocol comprised of a transport layer corresponding to a transport layer of an Open Systems Interconnection (OSI) model, said UDP transport layer being modified to detect at least one of a duplicate message and a duplicate segmented message while requiring less overhead than is required by Transport Control Protocol (TCP) protocol;

detecting said at least one of duplicate message and duplicate segmented message using a peer wireless protocol layer; and

discarding said at least one of duplicate message and duplicate segmented message, in response to said detection of said at least one of duplicate message and duplicate segmented message with said transport layer of said hybrid UDP connectionless transport protocol;

wherein said at least one of duplicate message and duplicate segmented message received from said wireless device is acknowledged back to said wireless device to said peer wireless protocol layer, discarded, and conditionally logged.

2. The method of claim 1, further comprising:

specifying a server class for said physical messaging network server during a registration of said physical messaging network server.

3. The method of claim 2, further comprising:

specifying at least one of a packet header, an IP address and a listener port during said registration.

4. The method of claim 2, wherein:

said physical messaging network server class is associated with at least one of a network access protocol for a communications network connecting said client device and said physical messaging network server.

5. The method of claim 1, further comprising:

generating a standard packet for communication between said physical messaging network server and said wireless device during encapsulation.

6. The method of claim 5, wherein the standard packet includes at least one of:

a header length;

protocol flags;

packet length;

database ID;

link station ID;

message ID;

customer ID;

port number;

network header; and

message body.

7. The method of claim 5, further comprising:

a network header comprising at least one of;

a compression indicator;

a security indicator;

a service type indicator;

a message type indicator; and

a server ID.

8. The method of claim 1, further comprising:

encapsulating a transport header;

notifying a sending device of a success or failure of a transmission;

segmenting a message over a pre-determined length into segmented messages;

assembling said segmented messages into assembled messages;

resending messages that are not acknowledged within a pre-determined time;

pacing a transmission of messages larger than a pre-determined number of segments;

detecting duplicate message segments; and

detecting duplicate messages.

9. The method of claim 8, further comprising:

encapsulating a communication layer.

10. The method of claim 1, further comprising:

generating acknowledgement messages;

processing the acknowledgement messages;

compressing and decompressing messages; and

encrypting and decrypting messages.

11. The method of claim 10, further comprising:

processing application specific messages;

providing special compression services; and

providing special security services.

12. The method of claim 1, further comprising:

searching a database based on a server type to identify said physical messaging network server, said physical messaging network server being of an intelligent messaging network server type that another physical messaging network server desires to connect with.

13. The method of claim 12, further comprising:

facilitating a handshake procedure to determine a validity of a connection between said physical messaging network server and said client device.

14. The method of claim 1, wherein the physical messaging network server types comprise:

at least one of a protocol gateway server, message router server, and back-end server.

15. The method of claim 1, further comprising:

encapsulating a network access protocol used to transmit data between said client device to said physical messaging network server, said network access protocol being transparent to said physical messaging network server receiving said data from said client device.