IP Library Granted Patent US 8,009,619
Granted Patent B1
US 8,009,619 · App. 11/977,319 · Granted Aug 30, 2011

Server-side wireless communications link support for mobile handheld devices

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 8,009,619
App. No.
11/977,319
Granted
Aug 30, 2011
Kind
B1
Abstract

A server-based method for implementing a communications link. The method includes receiving via a communications network a request for a communications link from a client communications component executing on a handheld device and establishing a wireless communications link with the handheld device by using a server communications interface executing on the server. An optimized protocol is automatically implemented between the client communications component and the server based on the wireless communications link type and the handheld device type, wherein the optimized protocol is implemented while maintaining a standardized application programming interface for the server communications interface, and wherein the communications link is established via the communications component functioning with a device API component to configure hardware of the handheld device.

Claims (30)

1. A server-based method for, comprising:

receiving, at a server and via a communications network, a request for a communications link from a client communications component executing on a handheld device;

establishing the communications link with the handheld device using a server communications interface executing on the server;

automatically implementing, at a first time, a first protocol between the client communications component and the server based on a type of the communications link and a type of the handheld device, the first protocol being implemented while maintaining a standardized application programming interface (API) for the server communications interface, the communications link being established via the client communications component functioning with a device API component to configure hardware of the handheld device; and

automatically implementing, at a second time after the first time, a second protocol, different from the first protocol, between the client communications component and the server based on a quality of the communications link at the second time, the first protocol and the second protocol being different ones of a socket full-duplex connection protocol, a socket half duplex connection protocol, an HTTP tunneling protocol, and an HTTP polling protocol.

2. The server-based method of claim 1 , wherein the device API component is a J2ME component.

3. The server-based method of claim 1 , wherein the device API component is a BREW component.

4. The server-based method of claim 1 , wherein the device API component is a Symbian component.

5. The server-based method of claim 1 , wherein the first protocol is configured to maintain a communications latency of less than one second.

6. The server-based method of claim 1 , wherein the client communications component includes a hardware abstraction component for translating between the client communications component and device specific hardware functions of the handheld device.

7. The server-based method of claim 6 , wherein the hardware abstraction component is configured to enable the client communications component to implement a stable communications API on multiple different handheld device types.

8. The server-based method of claim 1 , wherein a plurality of application servers are configured to communicate with the handheld device via the server communications interface.

9. A server, comprising:

a processor; and

a memory coupled to the processor, the memory storing processor readable code that, when executed by the processor, is configured to cause the processor to:

receive, via a communications network, a request for a communications link from a client communications component executing on a handheld device;

establish a wireless communications link with the handheld device by using a server communications interface;

automatically select, as an optimized protocol, a socket full-duplex connection protocol if a quality of the wireless communications link is above or equal to a threshold, or one of a socket half duplex connection protocol, an HTTP tunneling protocol, and an HTTP polling protocol if the quality of the wireless communications link is below the threshold; and

automatically implement the optimized protocol between the client communications component and the server communications interface, the optimized protocol being implemented while maintaining a standardized application programming interface (API) for the server communications interface, the communications link being established via the client communications component functioning with a device API component to configure hardware of the handheld device.

10. The server of claim 9 , wherein the device API component is one of a J2ME component, a BREW component, and a Symbian component.

11. The server of claim 9 , wherein a plurality of application servers are configured to communicate with the handheld device via the server communications interface.

12. A non-transitory processor-readable medium storing code representing instructions to cause a processor to:

receive, via a communications network, a request for a communications link from a client communications component executing on a handheld device;

establish a wireless communications link with the handheld device using a server communications interface;

automatically select, as an optimized protocol, a socket full-duplex connection protocol if a quality of the wireless communications link is above or equal to a threshold, or one of a socket half duplex connection protocol, an HTTP tunneling protocol, and an HTTP polling protocol if the quality of the wireless communications link is below the threshold; and

automatically implement the optimized protocol between the client communications component and the server communications interface, the optimized protocol being implemented while maintaining a standardized application programming interface (API) for the server communications interface, the communications link being established via the client communications component functioning with a device API component to configure hardware of the handheld device.

13. The non-transitory processor-readable medium of claim 12 , wherein a plurality of application servers are configured to communicate with the handheld device via the server communications interface.

14. The server-based method of claim 1 , wherein the quality of the communications link at the second time is less than a quality of the communications link at the first time.

15. The non-transitory processor-readable medium of claim 12 , wherein the optimized protocol is a first optimized protocol, the code representing instructions to cause the processor to automatically implement the first optimized protocol being executed at a first time, the quality of the wireless communications link being the quality of the wireless communications link at the first time, the non-transitory processor-readable medium further comprising code to:

automatically implement, at a second time after the first time, a second optimized protocol between the client communications component and the server communications interface based on a quality of the wireless communications link at the second time.

Assignments (8)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 4, 2025
From: PHUNWARE, INC.
To: GOTV NETWORKS, LLC
Reel/Frame 071318/0619 →
MERGER Recorded Jul 22, 2021
From: GOTV NETWORKS, INC.
To: PHUNWARE, INC.
Reel/Frame 056946/0302 →
RELEASE OF SECURITY INTEREST Recorded Mar 31, 2021
From: WESTERN ALLIANCE BANK
To: PHUNWARE, INC.
Reel/Frame 055787/0035 →
RELEASE OF SECURITY INTEREST Recorded Mar 31, 2021
From: BRIDGE BANK, NATIONAL ASSOCIATION
To: PHUNWARE, INC.
Reel/Frame 055787/0418 →
SECURITY INTEREST Recorded Apr 5, 2016
From: PHUNWARE, INC.
To: WESTERN ALLIANCE BANK
Reel/Frame 038194/0001 →
SECURITY AGREEMENT Recorded Jan 14, 2013
From: PHUNWARE, INC.
To: BRIDGE BANK, NATIONAL ASSOCIATION
Reel/Frame 029621/0751 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 29, 2010
From: HANDS-ON MOBLILE, INC.
To: GOTV NETWORKS, INC.
Reel/Frame 024306/0841 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 22, 2008
From: CLAVEL, PHILIPPE; WATERS, BRYAN
To: HANDS-ON-MOBILE, INC.
Reel/Frame 020421/0563 →