IP Library › Granted Patent US 9,100,241

Granted Patent B2

US 9,100,241 · App. 14/071,337 · Granted Aug 4, 2015

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

View Patent ↗

Loading inventors, assignments & file history…

Monitor This Case

Get email alerts when status or documents change.

Order Certified Copies

Most orders are placed with the USPTO same day — all within 24 business hours.

Order via The Patent Place →

Pre-filled with this patent's details

Quick Facts

Patent No.: US 9,100,241
App. No.: 14/071,337
Granted: Aug 4, 2015
Kind: B2

External Links

USPTO Patent Center↗ Full Patent PDF↗

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 (50)

1. A method of deploying content to client applications, comprising:

accepting an inbound message from a client application running on a client device via a proxy IP/port;

packaging the inbound message into an internal message format with an HTTP redirector;

forwarding the packaged inbound message to a back-end server;

receiving a response from a web server;

packaging the response into the internal message format with the back end server;

forwarding the response to the HTTP redirector; and

transferring the response to the client application running on the client device via the proxy IP/port.

2. Apparatus for deploying content to client applications, comprising:

means for accepting an inbound message from a client application running on a client device via a proxy IP/port;

means for packaging the inbound message into an internal message format with an HTTP redirector;

means for forwarding the packaged inbound message to a back-end server;

means for receiving a response from a web server;

means for packaging the response into the internal message format with the back end server;

means for forwarding the response to the HTTP redirector; and

means for transferring the response to the client application running on the client device via the proxy IP/port.

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

intercepting, via a proxy port, a mobile client web browser HyperText Transfer Protocol (HTTP) request from a physical mobile client device;

packaging, with a physical HTTP re-director, said mobile client web browser HTTP request;

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

receiving a response message from said physical back-end server; and

accessing a transport library, independent of a peer wireless protocol, to obtain a message relating to said mobile client web browser request.

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

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

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

said non-IP protocol supports message segmentation.

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

said non-IP protocol supports message segmentation reassembly.

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

said non-IP protocol supports message retries.

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

said non-IP protocol supports message duplication.

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

said obtained message relates to successful transmission.

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

said obtained message relates to message segmentation.

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

said obtained message relates to message retry.

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

said obtained message relates to duplicate message.

13. The method of accessing a back-end server according to claim 3 , 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.

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

said physical HTTP re-director provides a client side proxy.

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

said physical HTTP re-director provides compression of said mobile client web browser HTTP request.

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

said physical HTTP re-director provides decompression of said response message to said mobile client web browser HTTP request.

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

said physical HTTP re-director unpacks said response message to said mobile client web browser HTTP request.

Assignments (5)

SECURITY AGREEMENT Recorded Mar 3, 2016

From: COMTECH EF DATA CORP.; COMTECH XICOM TECHNOLOGY, INC.; COMTECH MOBILE DATACOM CORPORATION; TELECOMMUNICATION SYSTEMS, INC.

To: CITIBANK N.A., AS ADMINISTRATIVE AGENT