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

• US 20100268782A1
• Filed: 03/19/2010
• Published: 10/21/2010
• Est. Priority Date: 01/31/2000
• Status: Active Grant

• Current Assignee: TeleCommunication Systems Inc (Comtech Telecommunications Corporation)
• Original Assignee: TeleCommunication Systems Inc (Comtech Telecommunications Corporation)
• Inventors: Zombek, James M., Edwards, Donald J.
• Granted Patent: US 8,200,829 B2
• Time in Patent Office: Days
• US Class Current: 709/206
• 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-32. -32. (canceled)

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

intercepting a mobile client web browser Hypertext Transfer Protocol (HTTP) request from a mobile client device via a proxy IP/port;

accessing, with an HTTP redirector, a library of mobile services to obtain information about a wireless protocol supported by said mobile client device;

re-packaging, with said HTTP redirector, said mobile client web browser HTTP request into an internal message format;

transmitting said re-packaged mobile client web browser HTTP request from said mobile client device to a back-end server over a non-IP protocol network

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

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

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

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

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

said HTTP redirector acts as a client side proxy.

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

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

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

said HTTP redirector provides decompression of a response to said mobile client web browser HTTP request.

39. The method according to claim 33, wherein:

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

40. A mobile client, comprising:

a proxy IP/port to intercept a mobile client web browser Hypertext Transfer Protocol (HTTP) request from a mobile client device;

an HTTP redirector to access a library of mobile services to obtain information about a wireless protocol supported by said mobile client device, and to re-packaging said mobile client web browser HTTP request into an internal message format;

a transmitter to transmit said re-packaged mobile client web browser HTTP request from said mobile client device to a back-end server over a non-IP protocol network

41. The mobile client according to claim 40, wherein:

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

42. The mobile client according to claim 40, further comprising:

a library of mobile services accessed by said mobile client device to obtain information related to a wireless protocol supported by said mobile client device.

43. The mobile client according to claim 40, wherein:

said HTTP redirector acts as a client side proxy.

44. The mobile client according to claim 40, wherein:

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

45. The mobile client according to claim 40, wherein:

said HTTP redirector provides decompression of a response to said mobile client web browser HTTP request.

46. The mobile client according to claim 40, wherein:

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