System and method for re-directing requests from browsers for communication over non-IP based networks

• US 8,578,032 B2
• Filed: 06/08/2012
• Issued: 11/05/2013
• 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: Zombek, James M., Edwards, Donald J.
• Primary Examiner(s): BAROT, BHARAT
• Application Number:
  US13/492,080
• Publication Number:
  US 20130144980A1
• Time in Patent Office: 515 Days
• Field of Search: 709201-203, 709217-219, 709227-230, 709237-238, 709/250, 370464-467
• US Class Current: 709/227
• 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 method and system for deploying content to client applications is provided. Inbound messages are accepted from a client application running on a client device via a proxy IP/port. The inbound messages are packaged into an internal message format with an HTTP redirector. The packaged message is forwarded to a back-end server via a message router. A response is received form from a web server. The response is packaged into the internal message format with the back-end server. The response is then forwarded to the HTTP redirector via a message router. The response can then be transferred to the client application running on the client device, via the proxy IP/port.

Claims

1. A method of accessing a back-end server, comprising:

intercepting, via a proxy port, a mobile client web browser request from a physical mobile client device;

accessing a transport library, independent of a peer wireless protocol, to obtain at least one of successful transmission information, message segmentation information, message retry information, and duplicate message information;

re-packaging, with said physical redirector, said mobile client web browser request;

transmitting, via a non-Internet Protocol (IP) protocol, said re-packaged mobile client web browser request to a physical back-end server; and

receiving a response message from said physical back-end server.

2. The method of method of accessing a back-end server according to claim 1, wherein:

said mobile client web browser request is a Hypertext Transfer Protocol (HTTP) request.

3. The method of method of accessing a back-end server according to claim 1, wherein:

said proxy port is an Internet Protocol (IP) proxy port.

4. The method of method of accessing a back-end server according to claim 1, wherein:

said non-IP protocol supports at least one of message segmentation, message segmentation reassembly, message retries and message duplication.

5. The method of accessing a back-end server according to claim 1, further comprising:

accessing, from said physical mobile client device, said transport library to obtain information related to a wireless protocol supported by said physical mobile client device.

6. The method of accessing a back-end server according to claim 1, wherein:

said physical redirector acts as a client side proxy.

7. The method of accessing a back-end server according to claim 1, wherein:

said physical redirector provides compression of said mobile client web browser request.

8. The method of accessing a back-end server according to claim 1, wherein:

said physical redirector provides decompression of said response message to said mobile client web browser request.

9. The method according to claim 1, wherein:

said physical redirector unpacks said response message to said re-packaged mobile client web browser request.

10. A mobile client, comprising:

a proxy port to intercept a mobile client web browser request from a mobile client device;

a transport library, independent of a peer wireless protocol, to obtain at least one of successful transmission information, message segmentation information, message retry information, and duplicate message information;

a physical redirector to re-package said mobile client web browser request;

a transmitter to transmit, via a non-Internet Protocol (IP) protocol, said re-packaged mobile client web browser request to a back-end server; and

a receiver to receive a response message from said physical back-end server.

11. The mobile client according to claim 10, wherein:

said mobile client web browser request is a Hypertext Transfer Protocol (HTTP) request.

12. The mobile client according to claim 10, wherein:

said proxy port is an Internet Protocol (IP) proxy port.

13. The mobile client according to claim 10, wherein:

said non-IP protocol supports at least one of message segmentation, message segmentation reassembly, message retries and message duplication.

14. The mobile client according to claim 10, wherein:

said transport library, accessible by said mobile client device, provides information related to a wireless protocol supported by said mobile client device.

15. The mobile client according to claim 10, wherein:

said physical redirector acts as a client side proxy.

16. The mobile client according to claim 10, wherein:

said physical redirector provides compression of said mobile client web browser request.

17. The mobile client according to claim 10, wherein:

said physical redirector provides decompression of said response message to said mobile client web browser request.

18. The mobile client according to claim 10, wherein:

said redirector unpacks said response message to said re-packaged mobile client web browser request.