Open system interconnection (OSI) messaging

• US 7,895,256 B2
• Filed: 12/20/2000
• Issued: 02/22/2011
• Est. Priority Date: 01/31/2000
• Status: Expired due to Fees

• 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): Meky, Moustafa M
• Application Number:
  US09/740,040
• Publication Number:
  US 20010032232A1
• Time in Patent Office: 3,716 Days
• Field of Search: 709/200, 709/203, 709/219, 709/246, 709/206, 370/401, 370465-467
• US Class Current: 709/200
• CPC Class Codes: H04L 1/1635 Cumulative acknowledgement, i.e. the acknowledgement message applying to all previous messages
• CPC Class Codes: H04L 2001/0092 Error control systems characterised by the topology of the transmission link
• CPC Class Codes: H04L 41/0213 Standardised network management protocols, e.g. simple network management protocol [SNMP]
• CPC Class Codes: H04L 41/0681 Configuration of triggering conditions
• CPC Class Codes: H04L 43/065 related to network devices
• CPC Class Codes: H04L 43/0817 by checking functioning
• CPC Class Codes: H04L 43/10 Active monitoring, e.g. heartbeat, ping or trace-route
• CPC Class Codes: H04L 51/04 Real-time or near real-time messaging, e.g. instant messaging [IM]
• CPC Class Codes: H04L 63/0281 Proxies
• CPC Class Codes: H04L 63/0407 wherein the identity of one or more communicating identities is hidden cryptographic mechanisms or cryptographic arrangements for anonymous credentials or for identity based cryptographic systems H04L9/00
• 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/083 using passwords cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226
• CPC Class Codes: H04L 67/00 Network arrangements or protocols for supporting network services or applications user-to-user messaging H04L51/00; network arrangements, protocols or services for supporting real-time applications in data packet communications networks H04L65/00
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/025 for remote control or remote monitoring of applications
• 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/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/133 Protocols for remote procedure calls [RPC]
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04L 67/563 : Data redirection of data network streams
• CPC Class Codes: H04L 67/5651 : Reducing the amount or size of exchanged application data
• CPC Class Codes: H04L 67/568 : Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: H04L 69/08 : Protocols for interworking; Protocol conversion
• 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/164 : Adaptation or special uses of UDP protocol
• CPC Class Codes: H04L 69/18 : Multiprotocol handlers, e.g. single devices capable of handling multiple protocols
• 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 80/00 : Wireless network protocols or protocol adaptations to wireless operation
• CPC Class Codes: H04W 80/045 : involving different protocol versions, e.g. MIPv4 and MIPv6

Abstract

A messaging system, method, and computer program product includes a client device having stored therein a client application, which is adapted to be executed by the client device, a server having stored therein a server application, which is adapted to be executed by the server, a plurality of wireless networks, each of which is adapted to: communicate messages between the client device and the server; and support one or more wireless network protocols, and a protocol gateway encapsulating a fundamental network protocol. The fundamental network protocol underlies each of the one or more wireless network protocols and includes a protocol stack that corresponds substantially to an Open System Interconnection (OSI) model and incorporates a simple network transport layer (SNTL). In such a manner, the invention further includes means for communicating a message between the client application and the server application, over a selected wireless network protocol through the protocol gateway, independent of the selected wireless network protocol. Moreover, the present invention features methods of communicating such messages over wireless networks efficiently, without requiring significant bandwidth, a valuable resource in wireless networks.

Claims

1. A messaging system, comprising:

a client device;

a server; and

a protocol gateway adaptively arranged between at least two of a plurality of communication networks each communicating messages between said client device and said server with a plurality of differing wireless network protocols, said protocol gateway segmenting a message communicated with an underlying wireless network protocol into multiple segments, and said protocol gateway providing Transmission Control Protocol (TCP) functionality to said multiple segments communicated with a connectionless protocol through a layer of a peer protocol working in coordination with said connectionless protocol.

2. The messaging system according to claim 1, wherein said underlying wireless network protocol is comprised of a protocol stack that comprises:

an application layer mapped to layer 7 of said OSI model;

a network layer mapped to layer 3 of said OSI model;

a data link layer mapped to layer 2 of said OSI model; and

a physical layer mapped to layer 1 of said OSI model.

3. The messaging system according to claim 2, wherein:

said application layer comprises an interface between a client application and a simple network transport layer (SNTL); and

said client application is adapted to send and receive messages across said plurality of wireless networks without having any information of a communication implementation.

4. The messaging system according to claim 3, wherein:

said client application is selected from a group consisting of one or more e-mail applications, one or more file transfer applications, and a plurality of end user applications.

5. The messaging system according to claim 3, wherein:

said network layer comprises means for providing network protocol layer functionality and hiding details of said functionality from said SNTL.

6. The messaging system according to claim 5, wherein:

said network layer comprises an Internet Protocol (IP).

7. The messaging system according to claim 3, wherein:

said SNTL includes a connectionless UDP-like transport protocol having substantially all features and advantages of TCP.

8. The messaging system according to claim 7, wherein:

said features are selected from a group comprising message segmentation, message segment reassembly, message retries, and message duplication.

9. The messaging system according to claim 7, wherein:

said SNTL includes a transport header having a preselected width.

10. The messaging system according to claim 9, wherein:

said preselected width comprises between four to six bytes.

11. The messaging system according to claim 9, further comprising:

a single segment message header.

12. The messaging system according to claim 9, further comprising:

a multiple segment message header.

13. The messaging system according to claim 9, wherein said transport header further comprises:

a first field adapted to indicate a version number of a segment header;

a second field adapted to indicate a message identification value, adapted to discard segment/message duplications and to match acknowledgments with messages;

a third field adapted to indicate protocol information;

a fourth field adapted to indicate a total number of bytes contained in a message segment to be sent including said segment header; and

a fifth field adapted to indicate a number of each said message segment.

14. The messaging system according to claim 13, wherein:

said first field comprises two bits.

15. The messaging system according to claim 13, wherein:

said first field comprises bit 0 and bit 1 of a first word in said segment header.

16. The messaging system according to claim 13, wherein:

said first field comprises a value of from 0 to 3.

17. The messaging system according to claim 13, wherein:

said second field comprises thirteen bits.

18. The messaging system according to claim 13, wherein:

said second field comprises bits 2 through 14 of a first word in said segment header.

19. The messaging system according to claim 13, wherein:

said second field comprises a value of from 0 to 8,192.

20. The messaging system according to claim 13, wherein:

said third field comprises five bits.

21. The messaging system according to claim 13, wherein:

said third field comprises bits 15 through 19 of a first word in said segment header.

22. The messaging system according to claim 13, wherein:

bit 19 of said third field comprises a value indicative of message segmentation.

23. The messaging system according to claim 22, wherein:

bit 19 comprises a value of 0 when said message is not segmented.

24. The messaging system according to claim 22, wherein:

bit 19 comprises a value of 1 when said message is segmented.

25. The messaging system according to claim 13, wherein:

bit 16 of said third field comprises a value indicative of a message type.

26. The messaging system according to claim 25, wherein:

bit 16 comprises a value of 0 when said message includes a positive acknowledgment.

27. The messaging system according to claim 25, wherein:

bit 16 comprises a value of 1 when said message includes a negative acknowledgment.

28. The messaging system according to claim 13, wherein:

bit 15 of said third field comprises a message indicator.

29. The messaging system according to claim 28, wherein:

bit 15 comprises a value of 0 when said message is an application message.

30. The messaging system according to claim 28, wherein:

bit 15 comprises a value of 1 when said message is a system message.

31. The messaging system according to claim 13, wherein:

said fourth field comprises twelve bits.

32. The messaging system according to claim 31, wherein:

said fourth field comprises bits 20 through 31 of a second word in said segment header.

33. The messaging system according to claim 32, wherein:

said fourth field comprises a value of from 4 to 4,096.

34. The messaging system according to claim 13, wherein:

said fifth field comprises eight bits.

35. The messaging system according to claim 34, wherein:

said fifth field comprises bits 0 through 7 of a third word in said segment header.

36. The messaging system according to claim 34, wherein:

said fifth field comprises a value of from 2 to 255.

37. The messaging system according to claim 13, wherein:

said fifth field is adapted to re-order a plurality of message segments into a single complete message.

38. The messaging system according to claim 2, wherein:

said data link layer and said physical layer are together adapted to comply with a public switch telephone network protocol.

39. The messaging system according to claim 2, wherein:

said data link layer and said physical layer are together adapted to comply with a cellular digital packet data protocol.

40. The messaging system according to claim 2, wherein:

said data link layer and said physical layer are together adapted to comply with a Mobitex protocol.

41. The messaging system according to claim 2, wherein:

said data link layer and said physical layer are together adapted to comply with a RIM protocol.

42. The messaging system according to claim 2, wherein:

said data link layer and said physical layer are together adapted to comply with an ARDIS protocol.

43. The messaging system according to claim 2, wherein:

said data link layer and said physical layer are adapted to comply with a GPRS protocol.

44. The messaging system according to claim 2, wherein:

said data link layer and said physical layer are adapted to comply with a GSM protocol.

45. The messaging system according to claim 2, wherein:

said data link layer and said physical layer are adapted to comply with said selected wireless network protocol.

46. The messaging system according to claim 2, wherein:

said data link layer and said physical layer are adapted to comply with a wireless network protocol selected from a group comprising a public switch telephone network protocol, a cellular digital packet data protocol, a Mobitex protocol, an ARDIS protocol, a RIM protocol, a GPRS protocol, and a GSM protocol.

47. A messaging method, comprising:

communicating messages between a client application and a server application over a plurality of communication networks each communicating said messages between said client device and said server with a plurality of differing wireless network protocols;

segmenting with said protocol gateway a message communicated with an underlying wireless network protocol into multiple segments; and

adding with said protocol gateway Transmission Control Protocol (TCP) functionality to said multiple segments communicated with a connectionless protocol through a layer of a peer protocol working in coordination with said connectionless protocol.

48. The messaging method according to claim 47, further comprising:

a simple network transport layer (SNTL) that maps to layer 4 of said OSI model.

49. The messaging method according to claim 47, wherein said underlying wireless network protocol is comprised of a protocol stack that comprises:

an application layer mapped to layer 7 of said OSI model;

a network layer mapped to layer 3 of said OSI model;

a data link layer mapped to layer 2 of said OSI model; and

a physical layer mapped to layer 1 of said OSI model.

50. The messaging method according to claim 49, wherein:

said application layer comprises an interface between a client application and a simple network transport layer (SNTL); and

said client application is adapted to send and receive messages across said plurality of wireless networks without having any information of a communication implementation.

51. The messaging method according to claim 50, wherein:

said client application is selected from a group consisting of one or more e-mail applications, one or more file transfer applications, and a plurality of end user applications.

52. The messaging method according to claim 49, wherein:

said network layer comprises means for providing network protocol layer functionality and hiding details of said functionality from a simple network transport layer (SNTL).

53. The messaging method according to claim 52, wherein:

said network layer comprises an Internet Protocol (IP).