Patent US5603374A successfully refreshed from Google Patents.
Patent US7003571B1 successfully refreshed from Google Patents.
US7003571B1
Expired / Lapsed
US
⏱️ 0.0 years remaining
System and method for re-directing requests from browsers for communication over non-IP based networks
Assignee: TeleCommunication Systems Inc
•
Filing: 2000-10-30
•
Granted: 2006-02-21
•
Expires: 2020-10-30
Abstract
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.
Inventors
- 👤 James M. Zombek
- 👤 Donald J. Edwards
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-11-06 13:28
CPC Classifications
H; H04; H04L; H04L67/00; H04L67/01; H04L67/02; H04L1/00; H04L1/12; H04L1/16; H04L1/1607; H04L1/1635; H04L43/00; H04L43/06; H04L43/065; H04L43/08; H04L43/0805; H04L43/0817; H04L43/10; H04L51/00; H04L51/04; H04L63/00; H04L63/04; H04L63/0407; H04L67/025; H04L67/04; H04L67/10; H04L67/133; H04L67/50; H04L67/56; H04L67/563; H04L69/00; H04L69/08; H04L69/16; H04L69/164; H04L69/18; H04L69/30; H04L69/32; H04L69/322; H04L69/329; H04L9/00; H04L9/40; H04W; H04W80/00; H04L2001/0092; H04L41/00; H04L41/02; H04L41/0213; H04L41/06; H04L41/0681; H04L63/02; H04L63/0281; H04L63/0428; H04L63/08; H04L63/083; H04L67/565; H04L67/5651; H04L67/568; H04W80/04; H04W80/045
Claims Analysis
Total Claims: 52
Claim 1
Independent Claim
166 words
A method of deploying content to mobile client applications, comprising: accepting inbound messages from a mobile client application running on a mobile client device via a proxy IP/port; packaging said inbound messages into an internal message format with an HTTP redirector, wherein said HTTP redirector, provided at said mobile client device, accesses a library of mobile services in order to obtain information about a wireless protocol supported by said mobile client device; forwarding said packaged message from said mobile client device to a back-end server over a non-IP protocol network, said non-IP protocol being adapted to support at least one of message segmentation, message segmentation reassembly, message retries and message duplication with a maximum six byte header; receiving a response from a web server; packaging said response from said web server into said internal message format with said back-end server; forwarding said response to said HTTP redirector; and transferring said response to said mobile client application running on said mobile client device via the proxy IP/port.
Claim 2
Independent Claim
166 words
A method of deploying content to mobile client applications, comprising: accepting inbound messages from a mobile client application running on a mobile client device via a proxy IP/port; packaging said inbound messages into an internal message format with an HTTP redirector, wherein said HTTP redirector, provided at said mobile client device, accesses a library of mobile services in order to obtain information about a wireless protocol supported by said mobile client device; forwarding said packaged message from said mobile client device to a back-end server over a non-IP protocol network, said non-IP protocol being adapted to support at least one of message segmentation, message segmentation reassembly, message retries and message duplication with a maximum six byte header; receiving a response from a web server; packaging said response from said web server into said internal message format with said back-end server; forwarding said response to said HTTP redirector; and transferring said response to said mobile client application running on said mobile client device via the proxy IP/port.
Claim 3
Dependent Claim
20 words
The method according to claim 1 , wherein: said library of mobile services are stored at said mobile client device.
Claim 4
Dependent Claim
16 words
The method according to claim 1 wherein: said HTTP redirector acts as a client side proxy.
Claim 5
Dependent Claim
18 words
The method according to claim 1 , wherein: said HTTP redirector provides compression of said inbound packaged message.
Claim 6
Dependent Claim
16 words
The method according to claim 1 , wherein: said HTTP redirector provides decompression of said response.
Claim 7
Dependent Claim
15 words
The method according to claim 1 , wherein: said HTTP redirector unpacks said packaged response.
Claim 8
Independent Claim
136 words
A method of deploying content to mobile client applications, comprising: accepting inbound messages from a mobile client application running on a mobile client device via a proxy IP/port; accessing a HTTP redirector acting as a mobile client-side proxy; packaging said inbound messages into an internal message format with said HTTP redirector; forwarding said packaged message to a back-end server via a message router over a non-IP protocol network, said non-IP protocol being adapted to support at least one of message segmentation, message segmentation reassembly, message retries and message duplication with a maximum six byte header; receiving a response from a Web server over said non-IP protocol network; packaging said response into said internal message format by said back-end server; and forwarding said packaged response to said HTTP redirector via a message router and a protocol gateway.
Claim 9
Independent Claim
136 words
A method of deploying content to mobile client applications, comprising: accepting inbound messages from a mobile client application running on a mobile client device via a proxy IP/port; accessing a HTTP redirector acting as a mobile client-side proxy; packaging said inbound messages into an internal message format with said HTTP redirector; forwarding said packaged message to a back-end server via a message router over a non-IP protocol network, said non-IP protocol being adapted to support at least one of message segmentation, message segmentation reassembly, message retries and message duplication with a maximum six byte header; receiving a response from a Web server over said non-IP protocol network; packaging said response into said internal message format by said back-end server; and forwarding said packaged response to said HTTP redirector via a message router and a protocol gateway.
Claim 10
Dependent Claim
36 words
The method according to claim 7 , further comprising: unpacking said packaged response by said HTTP redirector; and transferring said unpacked response to said mobile client application running on said client device via said proxy IP/port.
Claim 11
Dependent Claim
39 words
The method according to claim 7 , wherein: said HTTP redirector, provided at said mobile client device, accesses a library of mobile services in order to obtain information about a non-IP wireless protocol supported by said mobile client device.
Claim 12
Dependent Claim
97 words
A wireless device for communicating with a server via a non-IP protocol wireless network, comprising: a browser generating a request; a proxy IP/port; and a redirector receiving said request via said proxy IP/port and packaging said request with a protocol used by said non-IP protocol wireless network, wherein said director accesses a library of mobile services in order to obtain information about said protocol used by said non-IP protocol wireless network, said protocol being adapted to support at least one of message segmentation, message segmentation reassembly, message retries and message duplication with a maximum six byte header.
Claim 13
Dependent Claim
97 words
A wireless device for communicating with a server via a non-IP protocol wireless network, comprising: a browser generating a request; a proxy IP/port; and a redirector receiving said request via said proxy IP/port and packaging said request with a protocol used by said non-IP protocol wireless network, wherein said director accesses a library of mobile services in order to obtain information about said protocol used by said non-IP protocol wireless network, said protocol being adapted to support at least one of message segmentation, message segmentation reassembly, message retries and message duplication with a maximum six byte header.
Claim 14
Dependent Claim
14 words
The device according to claim 1 , wherein: said request is an HTTP request.
Claim 15
Dependent Claim
16 words
The device according to claim 1 , wherein: said redirector acts as a client side proxy.
Claim 16
Independent Claim
130 words
A method of communicating HTTP requests over a non-IP protocol wireless network using a non-IP protocol, comprising: sending an HTTP request from a web browser on a wireless device; intercepting said HTTP request with a redirector; packaging said HTTP request into a message format used by said non-IP protocol wireless network with said redirector wherein said redirector, provided at said client device, accesses a library of mobile services in order to obtain information about a wireless protocol supported by said wireless device; sending said packaged request over the wireless network to a proxy server; and fulfilling said request from said proxy servers wherein said non-IP protocol being adapted to support at least one of message segmentation, message segmentation reassembly, message retries and message duplication with a maximum six byte header.
Claim 17
Independent Claim
130 words
A method of communicating HTTP requests over a non-IP protocol wireless network using a non-IP protocol, comprising: sending an HTTP request from a web browser on a wireless device; intercepting said HTTP request with a redirector; packaging said HTTP request into a message format used by said non-IP protocol wireless network with said redirector wherein said redirector, provided at said client device, accesses a library of mobile services in order to obtain information about a wireless protocol supported by said wireless device; sending said packaged request over the wireless network to a proxy server; and fulfilling said request from said proxy servers wherein said non-IP protocol being adapted to support at least one of message segmentation, message segmentation reassembly, message retries and message duplication with a maximum six byte header.
Claim 18
Dependent Claim
25 words
The method according to claim 13 , further comprising: unpacking said request and sending said request to an appropriate web server with said proxy server.
Claim 19
Dependent Claim
62 words
The method according to claim 13 , further comprising: sending an HTTP request from a proxy server to an appropriate web server; receiving a response to said request; packaging said response into a message format used by said wireless network; sending said packaged response to a redirector; unpacking said packaged response with said redirector; and providing said response to a web browser.
Claim 20
Dependent Claim
153 words
A computer useable information storage medium storing computer readable program code for causing a computer to perform the steps of: accepting inbound messages from a mobile client application running on a mobile client device; packaging said inbound messages into an internal message format with a redirector wherein said redirector, provided at said mobile client device, accesses a library of mobile services in order to obtain information about a non-IP wireless protocol supported by said mobile client device, said non-IP wireless protocol being adapted to support at least one of message segmentation, message segmentation reassembly, message retries and message duplication with a maximum six byte header; forwarding said packaged message to a back-end server; receiving a response from a web server; packaging said response into said internal message format with said back-end server; forwarding said response to said redirector; and transferring said response to said mobile client application running on said mobile client device.
Claim 21
Dependent Claim
153 words
A computer useable information storage medium storing computer readable program code for causing a computer to perform the steps of: accepting inbound messages from a mobile client application running on a mobile client device; packaging said inbound messages into an internal message format with a redirector wherein said redirector, provided at said mobile client device, accesses a library of mobile services in order to obtain information about a non-IP wireless protocol supported by said mobile client device, said non-IP wireless protocol being adapted to support at least one of message segmentation, message segmentation reassembly, message retries and message duplication with a maximum six byte header; forwarding said packaged message to a back-end server; receiving a response from a web server; packaging said response into said internal message format with said back-end server; forwarding said response to said redirector; and transferring said response to said mobile client application running on said mobile client device.
Claim 22
Dependent Claim
23 words
The computer useable information storage medium of claim 16 , wherein: said redirector communicates with said mobile client application via a proxy IP/port.
Claim 23
Dependent Claim
147 words
A messaging system, comprising: a mobile client device comprising a web browser and a redirector communicating with said web browser, said redirector packaging messages from said web browser into a fundamental non-IP network protocol, said non-IP network protocol being adapted to support at least one of message segmentation, message segmentation reassembly, message retries and message duplication with a maximum six byte header; a Web server; a plurality of wireless networks adapted to communicate messages between said mobile client device and said Web server, and support one or more non-IP wireless network protocols; a protocol gateway encapsulating said fundamental non-IP network protocol, said fundamental non-IP network protocol underlining each of said one or more wireless network protocols; and a communicator to communicate messages between said web browser and said Web server over said non-IP wireless network protocol through said protocol gateway independent of a selected wireless network protocol.
Claim 24
Dependent Claim
147 words
A messaging system, comprising: a mobile client device comprising a web browser and a redirector communicating with said web browser, said redirector packaging messages from said web browser into a fundamental non-IP network protocol, said non-IP network protocol being adapted to support at least one of message segmentation, message segmentation reassembly, message retries and message duplication with a maximum six byte header; a Web server; a plurality of wireless networks adapted to communicate messages between said mobile client device and said Web server, and support one or more non-IP wireless network protocols; a protocol gateway encapsulating said fundamental non-IP network protocol, said fundamental non-IP network protocol underlining each of said one or more wireless network protocols; and a communicator to communicate messages between said web browser and said Web server over said non-IP wireless network protocol through said protocol gateway independent of a selected wireless network protocol.
Claim 25
Dependent Claim
54 words
The messaging system according to claim 18 , wherein: said Web server is an HTTP proxy server adapted to receive a plurality of HTTP requests from said mobile client device, send each said request over said Internet to said server and transmit a response corresponding thereto from said server to said mobile client device.
Claim 26
Dependent Claim
31 words
The messaging system according to claim 19 , wherein: said HTTP proxy server comprises a creator to create a TCP/IP socket connection and a manager to manage said TCP/IP socket connection.
Claim 27
Dependent Claim
22 words
The messaging system according to claim 18 , wherein: said HTTP proxy server is adapted to support one or more HTTP protocols.
Claim 28
Dependent Claim
36 words
The system according to claim 18 , wherein: said redirector at said mobile client device accesses a library of mobile services in order to obtain information about said network protocol supported by said mobile client device.
Claim 29
Independent Claim
83 words
A method of receiving content at a mobile client application, comprising: receiving HTTP content at said mobile client application over a non-IP protocol network; redirecting said HTTP content in said non-IP protocol to a content packager, said non-IP protocol being adapted to support at least one of message segmentation, message segmentation reassembly, message retries and message duplication with a maximum six byte header; packing said HTTP content for presentation at said mobile client application; and presenting said HTTP content said mobile client application.
Claim 30
Independent Claim
83 words
A method of receiving content at a mobile client application, comprising: receiving HTTP content at said mobile client application over a non-IP protocol network; redirecting said HTTP content in said non-IP protocol to a content packager, said non-IP protocol being adapted to support at least one of message segmentation, message segmentation reassembly, message retries and message duplication with a maximum six byte header; packing said HTTP content for presentation at said mobile client application; and presenting said HTTP content said mobile client application.
Claim 31
Dependent Claim
20 words
The method according to claim 23 , wherein said step of redirecting further comprises: acting as a client side proxy.
Claim 32
Dependent Claim
19 words
The method according to claim 23 , wherein said step of redirecting further comprises: decompressing of said HTTP content.
Claim 33
Independent Claim
76 words
A method of deploying HTTP content to an Internet server, comprising: deploying HTTP content to said Internet server; redirecting said HTTP content to a non-IP protocol in a content packager, said non-IP protocol being adapted to support at least one of message segmentation, message segmentation reassembly, message retries and message duplication with a maximum six byte header; packing said HTTP content for presentation to a non-IP network; and presenting said HTTP content to said non-IP network.
Claim 34
Independent Claim
76 words
A method of deploying HTTP content to an Internet server, comprising: deploying HTTP content to said Internet server; redirecting said HTTP content to a non-IP protocol in a content packager, said non-IP protocol being adapted to support at least one of message segmentation, message segmentation reassembly, message retries and message duplication with a maximum six byte header; packing said HTTP content for presentation to a non-IP network; and presenting said HTTP content to said non-IP network.
Claim 35
Dependent Claim
20 words
The method according to claim 26 , wherein said step of redirecting further comprises: acting as a client side proxy.
Claim 36
Dependent Claim
19 words
The method according to claim 26 , wherein said step of redirecting further comprises: compressing of said HTTP content.
Claim 37
Dependent Claim
87 words
Apparatus for deploying HTTP content to an Internet server, comprising: a deployer to deploy HTTP content to said Internet server; a redirector to redirect said HTTP content to a non-IP protocol in a content packager, said non-IP protocol being adapted to support at least one of message segmentation, message segmentation reassembly, message retries and message duplication with a maximum six byte header; a packager to package said HTTP content for presentation to a non-IP network; and a presenter to present said HTTP content to said non-IP network.
Claim 38
Dependent Claim
87 words
Apparatus for deploying HTTP content to an Internet server, comprising: a deployer to deploy HTTP content to said Internet server; a redirector to redirect said HTTP content to a non-IP protocol in a content packager, said non-IP protocol being adapted to support at least one of message segmentation, message segmentation reassembly, message retries and message duplication with a maximum six byte header; a packager to package said HTTP content for presentation to a non-IP network; and a presenter to present said HTTP content to said non-IP network.
Claim 39
Dependent Claim
17 words
The apparatus according to claim 29 , wherein: said redirector further acts as a client side proxy.
Claim 40
Dependent Claim
14 words
The apparatus according to claim 29 , wherein: said redirector compresses said HTTP content.
Claim 41
Dependent Claim
83 words
Apparatus for deploying HTTP content to an Internet server, comprising: means for deploying HTTP content to said Internet server; means for redirecting said HTTP content to a non-IP protocol in a content packager, said non-IP protocol being adapted to support at least one of message segmentation, message segmentation reassembly, message retries and message duplication with a maximum six byte header; means for packing said HTTP content for presentation to a non-IP network; and means for presenting said HTTP content to said non-IP network.
Claim 42
Dependent Claim
83 words
Apparatus for deploying HTTP content to an Internet server, comprising: means for deploying HTTP content to said Internet server; means for redirecting said HTTP content to a non-IP protocol in a content packager, said non-IP protocol being adapted to support at least one of message segmentation, message segmentation reassembly, message retries and message duplication with a maximum six byte header; means for packing said HTTP content for presentation to a non-IP network; and means for presenting said HTTP content to said non-IP network.
Claim 43
Dependent Claim
22 words
The apparatus according to claim 32 , wherein said means for redirecting further comprises: means for acting as a client side proxy.
Claim 44
Dependent Claim
21 words
The method according to claim 32 , wherein said means for redirecting further comprises: means for compressing of said HTTP content.
Claim 45
Dependent Claim
94 words
Apparatus for receiving content at a mobile client application, comprising: a receiver to receive HTTP content at said mobile client application over a non-IP protocol network; a redirector to redirect said HTTP content in said non-IP protocol to a content packager, said non-IP protocol being adapted to support at least one of message segmentation, message segmentation reassembly, message retries and message duplication with a maximum six byte header; a packager to package said HTTP content for presentation at said mobile client application; and a presenter to present said HTTP content said mobile client application.
Claim 46
Dependent Claim
94 words
Apparatus for receiving content at a mobile client application, comprising: a receiver to receive HTTP content at said mobile client application over a non-IP protocol network; a redirector to redirect said HTTP content in said non-IP protocol to a content packager, said non-IP protocol being adapted to support at least one of message segmentation, message segmentation reassembly, message retries and message duplication with a maximum six byte header; a packager to package said HTTP content for presentation at said mobile client application; and a presenter to present said HTTP content said mobile client application.
Claim 47
Dependent Claim
17 words
The apparatus according to claim 35 , wherein: said redirector further acts as a client side proxy.
Claim 48
Dependent Claim
14 words
The apparatus according to claim 35 , wherein: said redirector decompresses said HTTP content.
Claim 49
Dependent Claim
90 words
Apparatus for receiving content at a mobile client application, comprising: means for receiving HTTP content at said mobile client application over a non-IP protocol network; means for redirecting said HTTP content in said non-IP protocol to a content packager, said non-IP protocol being adapted to support at least one of message segmentation, message segmentation reassembly, message retries and message duplication with a maximum six byte header; means for packing said HTTP content for presentation at said mobile client application; and means for presenting said HTTP content said mobile client application.
Claim 50
Dependent Claim
90 words
Apparatus for receiving content at a mobile client application, comprising: means for receiving HTTP content at said mobile client application over a non-IP protocol network; means for redirecting said HTTP content in said non-IP protocol to a content packager, said non-IP protocol being adapted to support at least one of message segmentation, message segmentation reassembly, message retries and message duplication with a maximum six byte header; means for packing said HTTP content for presentation at said mobile client application; and means for presenting said HTTP content said mobile client application.
Claim 51
Dependent Claim
17 words
The apparatus according to claim 38 , further comprising: means for acting as a client side proxy.
Claim 52
Dependent Claim
16 words
The apparatus according to claim 38 , further comprising: means for decompressing of said HTTP content.
References Cited (Backward Citations)
US5564070A
Cited
US5583859A
Cited
US5590122A
Cited
US5970059A
Cited
US5850517A
Cited
US5742592A
Cited
US5771353A
Cited
US6473609B1
Cited
US5689505A
Cited
US5862345A
Cited
US5754774A
Cited
US5781549A
Cited
US5862481A
Cited
US6185625B1
Cited
US5949799A
Cited
US6311215B1
Cited
US6421733B1
Cited
US6473411B1
Cited
US6393014B1
Cited
US6374305B1
Cited
US6167450A
Cited
US6512754B2
Cited
US6665718B1
Cited
US6675208B1
Cited
US6628965B1
Cited
US6246684B1
Cited
US6192029B1
Cited
US6233577B1
Cited
EP0959600A1
Cited
US6247048B1
Cited
US6539422B1
Cited
US6343318B1
Cited
US6397259B1
Cited
US6590588B2
Cited
US6445691B2
Cited
US6640248B1
Cited
US6862622B2
Cited
US6590885B1
Cited
US6160793A
Cited
US6477543B1
Cited
US6272129B1
Cited
US6857013B2
Cited
US6567857B1
Cited
US6701374B2
Cited
US6772195B1
Cited
US6510464B1
Cited
US6563919B1
Cited
US6452910B1
Cited
US6879582B1
Cited
US6681262B1
Cited
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 2009-02-20 | 2009-08-22 | 2010-02-21 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2013-02-20 | 2013-08-22 | 2014-02-21 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2017-02-20 | 2017-08-22 | 2018-02-21 | $7700.00 | Window Closed / Lapsed |