Internet protocol loopback wireless data protocol converter

• US 20060227808A1
• Filed: 04/07/2005
• Published: 10/12/2006
• Est. Priority Date: 04/07/2005
• Status: Active Grant

• Current Assignee: Malikie Innovations Limited (Key Patent Innovations Limited)
• Original Assignee: Blackberry Limited
• Inventors: Estable, Luis
• Granted Patent: US 9,363,306 B2
• Time in Patent Office: Days
• US Class Current: 370/466
• 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/289 Intermediate processing functionally located close to the data consumer application, e.g. in same machine, in same home or in same sub-network
• 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/565 Conversion or adaptation of application format or content adding application control or application functional data H04L67/561
• CPC Class Codes: H04L 69/08 Protocols for interworking; Protocol conversion
• CPC Class Codes: H04L 69/085 specially adapted for interworking of IP-based networks with other networks
• CPC Class Codes: H04W 80/00 Wireless network protocols or protocol adaptations to wireless operation

Abstract

An internet protocol loopback wireless data protocol converter for a mobile device comprising: at least one loopback interface; at least one internet protocol server operating on one or more ports of any of the at least one loopback interface; a wireless optimized data communications module to connect to a wireless data infrastructure to send and receive wireless optimized data; and at least one protocol converter to convert communications in a wireless optimized data protocol to and from standard internet protocol, wherein an internet protocol application can communicate with the at least one server using the loopback interface and data to and from the application can be received and transmitted using the wireless optimized data communications module with conversion by the at least one protocol converter.

Claims

1. An internet protocol loopback wireless data protocol converter for a mobile device comprising:

a. at least one loopback interface;

b. at least one internet protocol server operating on one or more ports of any of said at least one loopback interface;

c. a wireless optimized data communications module to connect to a wireless data infrastructure to send and receive wireless optimized data; and

d. at least one protocol converter to convert communications in a wireless optimized data protocol to and from standard internet protocol,

wherein an internet protocol application can communicate with said at least one server using said loopback interface and data to and from said application can be received and transmitted using said wireless optimized data communications module with conversion by said at least one protocol converter.

2. The protocol converter of claim 1 further comprising a wireless optimized data module communicating with said at least one protocol converter, said wireless optimized data module storing wireless optimized data.

3. The protocol converter of claim 1, further comprising a client optimized data module storing client optimized data.

4. The protocol converter of claim 1, further comprising a notification module for notifying the internet protocol application when wireless optimized data is received and converted by said mobile device.

5. The protocol converter of claim 4, wherein said notification module includes notification means selected from the group consisting of:

a loopback port notification means, a vendor specific notification means using said server and a host-dependent notification means.

6. The protocol converter of claim 5, wherein said host-dependent notification means includes an application program interface (API) callback.

7. The protocol converter of claim 1, wherein the loopback interface has an address of the form 127.0.0.N, where N is between 1 and 254.

8. The protocol converter of claim 1, wherein the application is an email application and said at least one server is an email server selected from the group consisting of:

a Post Office Protocol 3 (POP3) server, an Internet Message Access Protocol (IMAP) server, and a Simple Mail Transfer Protocol (SMTP) server.

9. A method of utilizing an internet protocol application on a mobile device having a wireless optimized data communications module, a server on the mobile device and a protocol converter, the method comprising the steps of:

a. configuring the internet protocol application to communicate using a loopback interface with the server;

b. converting data coming from said server to said wireless optimized data communications module using said protocol converter to a wireless optimized data protocol; and

c. converting data from said wireless optimized data communications module to said server using said protocol converter to an internet protocol.

10. The method of claim 9, wherein the application is an email application and said at least one server is an email server selected from the group consisting of:

a Post Office Protocol 3 (POP3) server, an Internet Message Access Protocol (IMAP) server, and a Simple Mail Transfer Protocol (SMTP) server.

11. The method of claim 9, wherein said method further comprises the step of notifying the application from the server when the server receives data from said wireless optimized data communications module.

12. The method of claim 11, wherein the notify step utilizes a notification means selected from the group consisting of:

a loopback port notification means, a vendor specific notification means using said server, and a host-dependent notification means.

13. The method of claim 12, wherein said host-dependent notification means includes an application program interface (API) callback.

14. The method of claim 9 further comprising the step of optimizing data for a client application on said mobile device.

15. The method of claim 9, wherein the loopback interface has an address of the form 127.0.0.N, where N is between 1 and 254.