# US 9,521,185 B2 · System and method for re-directing requests from browsers for communications over non-IP based networks > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 9,521,185 B2 - Document ID: US9521185B2 - Status: Granted - Kind: B2 - Application number: 14/753,383 - Filed: 2015-06-29 - Published: 2016-06-23 - Granted: 2016-12-13 - Earliest claimed: 2000-01-31 - Assignees: Telecommuncation Systems, Inc. - Applicants: TeleCommunication Systems, Inc. - Inventors: James M. Zombek; Donald J. Edwards - Web page: https://patentgrep.com/patent/US9521185B2 ## CPC - H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP] - H04L 1/1635: {Cumulative acknowledgement, i.e. the acknowledgement message applying to all previous messages} - H04L 43/065: related to network devices - H04L 43/0817: by checking functioning - H04L 43/10: Active monitoring, e.g. heartbeat, ping or trace-route - H04L 51/04: Real-time or near real-time messaging, e.g. instant messaging [IM] - 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)} - 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) - H04L 67/025: for remote control or remote monitoring of applications - H04L 67/04: specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability - H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46) - H04L 67/133: Protocols for remote procedure calls [RPC] - H04L 67/56: Provisioning of proxy services (store-and-forward switching systems in data switching networks H04L12/54) - H04L 67/563: Data redirection of data network streams - H04L 69/16: Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP] - H04L 69/164: Adaptation or special uses of UDP protocol - H04L 69/18: Multiprotocol handlers, e.g. single devices capable of handling multiple protocols - H04L 69/329: in the application layer [OSI layer 7] - H04W 80/00: Wireless network protocols or protocol adaptations to wireless operation - H04L 41/0213: Standardised network management protocols, e.g. simple network management protocol [SNMP] - H04L 41/0681: Configuration of triggering conditions - H04L 63/0281: {Proxies} - H04L 63/0428: {wherein the data content is protected, e.g. by encrypting or encapsulating the payload} - H04L 63/083: {using passwords (cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226)} - H04L 67/5651: Reducing the amount or size of exchanged application data - H04L 67/568: Storing data temporarily at an intermediate stage, e.g. caching - H04L 2001/0092: {Error control systems characterised by the topology of the transmission link} - H04W 80/045: {involving different protocol versions, e.g. MIPv4 and MIPv6} - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) ## 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 ### Claim 1 A method to deploy content to a physical wireless device, comprising: receiving, on a physical proxy Internet Protocol (IP) port, a mobile client web browser HTTP request from a physical wireless device; packaging, with a physical HTTP redirector, said mobile client web browser HTTP request into an internal message; transmitting said packaged mobile client web browser HTTP request to a physical back-end server using a non-IP protocol; receiving a response message from a physical web server; packaging, with said physical back-end-server, said response message into a response internal message; forwarding said response internal message to said physical HTTP redirector; and transferring said response internal message to said physical wireless device via said physical proxy IP port. ### Claim 2 (depends on 1) The method of deploying content to a physical wireless device according to claim 1, wherein: said non-IP protocol includes message segmentation reassembly. ### Claim 3 (depends on 1) The method of deploying content to a physical wireless device according to claim 1, wherein: said non-IP protocol includes message retries. ### Claim 4 (depends on 1) The method of deploying content to a physical wireless device according to claim 1, wherein: said non-IP protocol includes message duplication. ### Claim 5 (depends on 1) The method of deploying content to a physical wireless device according to claim 1, wherein: said response message relates to successful transmission. ### Claim 6 (depends on 1) The method of deploying content to a physical wireless device according to claim 1, wherein: said response internal message relates to message segmentation. ### Claim 7 (depends on 1) The method of deploying content to a physical wireless device according to claim 1, wherein: said response internal message relates to message retry. ### Claim 8 (depends on 1) The method of deploying content to a physical wireless device according to claim 1, wherein: said response internal message relates to duplicate message. ### Claim 9 (depends on 1) The method of deploying content to a physical wireless device according to claim 1, further comprising: accessing, from said physical wireless device, a transport library to obtain information related to a wireless protocol supported by said physical wireless device. ### Claim 10 (depends on 1) The method of deploying content to a physical wireless device according to claim 1, wherein: said physical HTTP re-director provides a client side proxy. ### Claim 11 (depends on 1) The method of deploying content to a physical wireless device according to claim 1, wherein: said physical HTTP redirector compresses said mobile client web browser HTTP request. ### Claim 12 (depends on 1) The method of deploying content to a physical wireless device according to claim 1, wherein: said physical HTTP redirector decompresses said response internal message. ### Claim 13 (depends on 1) The method of deploying content to a physical wireless device according to claim 1, wherein: said physical HTTP redirector unpacks said response internal message. ### Claim 14 Apparatus to deploy content to a physical wireless device, comprising: means for receiving, on a physical proxy Internet Protocol (IP) port, a mobile client web browser HTTP request from a physical wireless device; means for packaging, with a physical HTTP redirector, said mobile client web browser HTTP request into an internal message; means for transmitting said packaged mobile client web browser HTTP request to a physical back-end server using a non-IP protocol; means for receiving a response message from a physical web server; means for packaging, with said physical back-end-server, said response message into a response internal message; means for forwarding said response internal message to said physical HTTP redirector; and means for transferring said response internal message to said physical wireless device via said physical proxy IP port. ### Claim 15 (depends on 14) The apparatus to deploy content to a physical wireless device according to claim 14, wherein: said non-IP protocol includes message segmentation reassembly. ### Claim 16 (depends on 14) The apparatus to deploy content to a physical wireless device according to claim 14, wherein: said non-IP protocol includes message retries. ### Claim 17 (depends on 14) The apparatus to deploy content to a physical wireless device according to claim 14, wherein: said non-IP protocol includes message duplication. ### Claim 18 (depends on 14) The apparatus to deploy content to a physical wireless device according to claim 14, wherein: said response message relates to successful transmission. ### Claim 19 (depends on 14) The apparatus to deploy content to a physical wireless device according to claim 14, wherein: said response internal message relates to message segmentation. ### Claim 20 (depends on 14) The apparatus to deploy content to a physical wireless device according to claim 14, wherein: said response internal message relates to message retry. ### Claim 21 (depends on 14) The apparatus to deploy content to a physical wireless device according to claim 14, wherein: said response internal message relates to duplicate message. ### Claim 22 (depends on 14) The apparatus to deploy content to a physical wireless device according to claim 14, further comprising: accessing, from said physical wireless device, a transport library to obtain information related to a wireless protocol supported by said physical wireless device. ### Claim 23 (depends on 14) The apparatus to deploy content to a physical wireless device according to claim 14, wherein: said physical HTTP re-director provides a client side proxy. ### Claim 24 (depends on 14) The apparatus to deploy content to a physical wireless device according to claim 14, wherein: said physical HTTP redirector compresses said mobile client web browser HTTP request. ### Claim 25 (depends on 14) The apparatus to deploy content to a physical wireless device according to claim 14, wherein: said physical HTTP redirector decompresses said response internal message. ### Claim 26 (depends on 14) The apparatus to deploy content to a physical wireless device according to claim 14, wherein: said physical HTTP redirector unpacks said response internal message. ### Claim 27 Apparatus to access a back-end server, comprising: means for intercepting, via a proxy port, a mobile client web browser HyperText Transfer Protocol (HTTP) request from a physical mobile client device; means for packaging, with a physical HTTP redirector, said mobile client web browser HTTP request; means for transmitting, via a non-Internet Protocol(IP) protocol, said packaged mobile client web browser HTTP request to a physical back-end server; means for receiving a response message from said physical back-end server; and means for accessing a transport library, independent of a peer wireless protocol, to obtain a message relating to said mobile client web browser request.