A METHOD AND SYSTEMS FOR ROUTING PACKETS FROM A GATEWAY TO AN ENDPOINT
First Claim
1. A method for routing packets from a gateway to an endpoint, the method comprising:
- (a) associating a private internet protocol (IP) address with an endpoint having a public IP address;
(b) capturing a packet addressed to the private IP address of the endpoint;
(c) applying a policy to the packet; and
(d) transmitting the packet to the public IP address of the endpoint, responsive to the application of the policy to the packet.
1 Assignment
0 Petitions

Accused Products

Abstract
A method for routing packets from a gateway to an endpoint includes the step of associating a private internet protocol (IP) address with an endpoint having a public IP address. A packet addressed to the private IP address of the endpoint is captured. A policy is applied to the packet. The packet is transmitted to the public IP address of the endpoint, responsive to the application of the policy to the packet.
295 Citations
Retrieving data from a server | ||
Patent #
US 7,937,370 B2
Filed 02/21/2007
|
Current Assignee
PTC Inc.
|
Original Assignee
Axeda
|
Establishing a virtual tunnel between two computer programs | ||
Patent #
US 7,966,418 B2
Filed 02/20/2004
|
Current Assignee
PTC Inc.
|
Original Assignee
Axeda
|
System and method for using multiple communication protocols in memory limited processors | ||
Patent #
US 7,957,401 B2
Filed 07/03/2003
|
Current Assignee
Upland Software Inc.
|
Original Assignee
Geos Communications Inc.
|
INTELLIGENT RENDERING OF INFORMATION IN A LIMITED DISPLAY ENVIRONMENT | ||
Patent #
US 20110179377A1
Filed 12/16/2010
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Flexible billing architecture | ||
Patent #
US 8,010,082 B2
Filed 10/19/2005
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
In-band quality-of-service signaling to endpoints that enforce traffic policies at traffic sources using policy messages piggybacked onto DiffServ bits | ||
Patent #
US 7,983,170 B2
Filed 12/19/2006
|
Current Assignee
Citrix Systems Inc.
|
Original Assignee
Citrix Systems Inc.
|
Managing user-to-user contact with inferred presence information | ||
Patent #
US 8,069,166 B2
Filed 02/27/2006
|
Current Assignee
Seven Networks LLC
|
Original Assignee
Seven Networks Inc
|
Multiple data store authentication | ||
Patent #
US 8,064,583 B1
Filed 09/21/2006
|
Current Assignee
Seven Networks LLC
|
Original Assignee
Seven Networks Inc
|
Reporting the state of an apparatus to a remote computer | ||
Patent #
US 8,055,758 B2
Filed 08/14/2006
|
Current Assignee
PTC Inc.
|
Original Assignee
Axeda
|
XML scripting of SOAP commands | ||
Patent #
US 8,060,886 B2
Filed 02/12/2007
|
Current Assignee
PTC Inc.
|
Original Assignee
Axeda
|
Managing configurations of distributed devices | ||
Patent #
US 8,065,397 B2
Filed 12/26/2006
|
Current Assignee
PTC Inc.
|
Original Assignee
Axeda Acquisition Corp.
|
System and method of binding a client to a server | ||
Patent #
US 7,676,599 B2
Filed 01/26/2005
|
Current Assignee
Upland Software Inc.
|
Original Assignee
I2 Telecom Ip Holdings Inc.
|
System and method for sharing an IP address | ||
Patent #
US 7,782,878 B2
Filed 08/11/2005
|
Current Assignee
Upland Software Inc.
|
Original Assignee
I2TELECOM IP HOLDINGS INC.
|
SYSTEM AND METHOD OF VOICE OVER INTERNET PROTOCOL COMMUNICATION | ||
Patent #
US 20100238834A9
Filed 10/31/2008
|
Current Assignee
Upland Software Inc.
|
Original Assignee
I2Telecom International Inc.
|
Virtual Desktop Integration with Terminal Services | ||
Patent #
US 20090006537A1
Filed 06/29/2007
|
Current Assignee
Microsoft Technology Licensing LLC
|
Original Assignee
Microsoft Corporation
|
SYSTEM AND METHOD OF VOICE OVER INTERNET PROTOCOL COMMUNICATION | ||
Patent #
US 20090067341A1
Filed 10/31/2008
|
Current Assignee
I2Telecom International Inc.
|
Original Assignee
I2Telecom International Inc.
|
METHOD AND SYSTEM FOR DETECTION OF NAT DEVICES IN A NETWORK | ||
Patent #
US 20090175197A1
Filed 05/24/2007
|
Current Assignee
ForeScout Technologies Incorporated
|
Original Assignee
ForeScout Technologies Incorporated
|
System and method for routing telephone calls over a voice and data network | ||
Patent #
US 7,606,217 B2
Filed 07/22/2003
|
Current Assignee
Upland Software Inc.
|
Original Assignee
I2 Telecom International Inc.
|
SYSTEM AND METHODS TO ROUTE CALLS OVER A VOICE AND DATA NETWORK | ||
Patent #
US 20090323920A1
Filed 09/02/2009
|
Current Assignee
Upland Software Inc.
|
Original Assignee
I2 Telecom International Inc.
|
Scalable address resolution in a communications environment | ||
Patent #
US 20090319683A1
Filed 06/19/2008
|
Current Assignee
Radius Networks inc.
|
Original Assignee
4DK Technologies Inc.
|
INTEGRATED CLIENT FOR ACCESS TO REMOTE RESOURCES | ||
Patent #
US 20090327905A1
Filed 06/27/2008
|
Current Assignee
Microsoft Technology Licensing LLC
|
Original Assignee
Microsoft Corporation
|
System and method for group management | ||
Patent #
US 20080001717A1
Filed 03/27/2007
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Portable VoIP Service Access Module | ||
Patent #
US 20080025291A1
Filed 08/03/2007
|
Current Assignee
magicJack VocalTec Limited
|
Original Assignee
I2 Telecom International Inc.
|
Portable VoIP service access module | ||
Patent #
US 7,336,654 B2
Filed 10/25/2004
|
Current Assignee
magicJack VocalTec Limited
|
Original Assignee
I2Telecom International Inc.
|
REMOTE ACCESS TO SECURE NETWORK DEVICES | ||
Patent #
US 20080075096A1
Filed 09/22/2006
|
Current Assignee
Enthenergy LLC
|
Original Assignee
Enthenergy LLC
|
A System and Method for Dynamically Grouping Devices Based on Present Device Conditions | ||
Patent #
US 20080082657A1
Filed 10/03/2006
|
Current Assignee
PTC Inc.
|
Original Assignee
Questra Corporation
|
In-Band Quality-of-Service Signaling to Endpoints that Enforce Traffic Policies at Traffic Sources Using Policy Messages Piggybacked onto DiffServ Bits | ||
Patent #
US 20080144502A1
Filed 12/19/2006
|
Current Assignee
Citrix Systems Inc.
|
Original Assignee
Deterministic Networks Inc.
|
Context Based Action | ||
Patent #
US 20080133708A1
Filed 10/28/2007
|
Current Assignee
Seven Networks LLC
|
Original Assignee
Seven Networks Inc
|
Providing A Generic Gateway For Accessing Protected Resources | ||
Patent #
US 20080178278A1
Filed 01/22/2007
|
Current Assignee
Bitkoo LLC
|
Original Assignee
Bitkoo LLC
|
Strategies for Securely Applying Connection Policies via a Gateway | ||
Patent #
US 20080209538A1
Filed 02/28/2007
|
Current Assignee
Microsoft Technology Licensing LLC
|
Original Assignee
Microsoft Corporation
|
Dynamically adapting the transmission rate of packets in real-time VoIP communications to the available bandwidth | ||
Patent #
US 7,460,480 B2
Filed 03/11/2005
|
Current Assignee
Upland Software Inc.
|
Original Assignee
I2Telecom International Inc.
|
XML Scripting of SOAP Commands | ||
Patent #
US 20070150903A1
Filed 02/12/2007
|
Current Assignee
PTC Inc.
|
Original Assignee
Axeda
|
Portable VoIP Service Access Module | ||
Patent #
US 20070248081A1
Filed 04/20/2007
|
Current Assignee
magicJack VocalTec Limited
|
Original Assignee
I2Telecom International Inc.
|
System and method of binding a client to a server | ||
Patent #
US 20060031393A1
Filed 01/26/2005
|
Current Assignee
Upland Software Inc.
|
Original Assignee
Geos Communications IP Holdings Incorporated
|
System and method for sharing an IP address | ||
Patent #
US 20060034296A1
Filed 08/11/2005
|
Current Assignee
Upland Software Inc.
|
Original Assignee
I2 Telecom International Inc.
|
Portable VoIP service access module | ||
Patent #
US 20060088025A1
Filed 10/25/2004
|
Current Assignee
magicJack VocalTec Limited
|
Original Assignee
Sinon Data LLC
|
Establishing a virtual tunnel between two computer programs | ||
Patent #
US 20050021772A1
Filed 02/20/2004
|
Current Assignee
PTC Inc.
|
Original Assignee
Axeda
|
System and method for routing telephone calls over a voice and data network | ||
Patent #
US 20050002506A1
Filed 07/22/2003
|
Current Assignee
Upland Software Inc.
|
Original Assignee
Geos Communications IP Holdings Incorporated
|
Retrieving data from a server | ||
Patent #
US 20020116550A1
Filed 04/17/2002
|
Current Assignee
PTC Inc.
|
Original Assignee
Axeda
|
Secure end-to-end transport through intermediary nodes | ||
Patent #
US 8,127,342 B2
Filed 09/23/2010
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Retrieving data from a server | ||
Patent #
US 8,108,543 B2
Filed 04/17/2002
|
Current Assignee
PTC Inc.
|
Original Assignee
Axeda
|
Provisioning applications for a mobile device | ||
Patent #
US 8,078,158 B2
Filed 06/26/2008
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Provisioning of e-mail settings for a mobile terminal | ||
Patent #
US 8,116,214 B2
Filed 11/30/2005
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Mobile virtual network operator | ||
Patent #
US 8,107,921 B2
Filed 01/11/2008
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Application and network-based long poll request detection and cacheability assessment therefor | ||
Patent #
US 8,166,164 B1
Filed 10/14/2011
|
Current Assignee
Seven Networks LLC
|
Original Assignee
Seven Networks Inc
|
Cache defeat detection and caching of content addressed by identifiers intended to defeat cache | ||
Patent #
US 8,190,701 B2
Filed 11/01/2011
|
Current Assignee
Seven Networks LLC
|
Original Assignee
Seven Networks Inc
|
Strategies for securely applying connection policies via a gateway | ||
Patent #
US 8,201,218 B2
Filed 02/28/2007
|
Current Assignee
Microsoft Technology Licensing LLC
|
Original Assignee
Microsoft Corporation
|
Method and system for detection of NAT devices in a network | ||
Patent #
US 8,254,286 B2
Filed 05/24/2007
|
Current Assignee
ForeScout Technologies Incorporated
|
Original Assignee
ForeScout Technologies Incorporated
|
Establishing a virtual tunnel between two computer programs | ||
Patent #
US 8,291,039 B2
Filed 05/11/2011
|
Current Assignee
PTC Inc.
|
Original Assignee
Axeda
|
Application and network-based long poll request detection and cacheability assessment therefor | ||
Patent #
US 8,291,076 B2
Filed 03/05/2012
|
Current Assignee
Seven Networks LLC
|
Original Assignee
Seven Networks Inc
|
Social caching for device resource sharing and management | ||
Patent #
US 8,316,098 B2
Filed 04/19/2012
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Distributed management of keep-alive message signaling for mobile network resource conservation and optimization | ||
Patent #
US 8,326,985 B2
Filed 11/01/2011
|
Current Assignee
Seven Networks LLC
|
Original Assignee
Seven Networks Inc
|
Method and system of renegotiating end-to-end voice over internet protocol CODECs | ||
Patent #
US 8,335,232 B2
Filed 10/31/2008
|
Current Assignee
Upland Software Inc.
|
Original Assignee
Geos Communications IP Holdings Inc. a wholly owned subsidiary of Augme Technologies Inc.
|
Remote Presentation Session Connectionless Oriented Channel Broker | ||
Patent #
US 20120331032A1
Filed 06/22/2011
|
Current Assignee
Microsoft Technology Licensing LLC
|
Original Assignee
Microsoft Corporation
|
Span Out Load Balancing Model | ||
Patent #
US 20120331300A1
Filed 06/22/2011
|
Current Assignee
Microsoft Technology Licensing LLC
|
Original Assignee
Microsoft Corporation
|
DISKLESS PC NETWORK COMMUNICATION AGENT SYSTEM | ||
Patent #
US 20130013755A1
Filed 07/05/2011
|
Current Assignee
Jade Quantum Technologies Incorporated
|
Original Assignee
Jade Quantum Technologies Incorporated
|
System and method for a mobile device to use physical storage of another device for caching | ||
Patent #
US 8,356,080 B2
Filed 07/20/2012
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Electronic-mail filtering for mobile devices | ||
Patent #
US 8,364,181 B2
Filed 12/10/2007
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
System and method for dynamically grouping devices based on present device conditions | ||
Patent #
US 8,370,479 B2
Filed 10/03/2006
|
Current Assignee
PTC Inc.
|
Original Assignee
Axeda Acquisition Corp.
|
System and methods to route calls over a voice and data network | ||
Patent #
US 8,379,634 B2
Filed 09/02/2009
|
Current Assignee
Upland Software Inc.
|
Original Assignee
Augme Technologies Incorporated
|
Adaptive device-initiated polling | ||
Patent #
US 8,406,119 B2
Filed 09/29/2006
|
Current Assignee
PTC Inc.
|
Original Assignee
Axeda Acquisition Corp.
|
Context aware data presentation | ||
Patent #
US 8,412,675 B2
Filed 02/24/2006
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Aligning data transfer to optimize connections established for transmission over a wireless network | ||
Patent #
US 8,417,823 B2
Filed 11/18/2011
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks LLC
|
Rule based extensible authentication | ||
Patent #
US 8,418,233 B1
Filed 10/24/2005
|
Current Assignee
F5 Networks Inc.
|
Original Assignee
F5 Networks Inc.
|
Flexible real-time inbox access | ||
Patent #
US 8,438,633 B1
Filed 12/18/2006
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Publishing data in an information community | ||
Patent #
US 8,468,126 B2
Filed 12/14/2005
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Distributed caching in a wireless network of content delivered for a mobile application over a long-held request | ||
Patent #
US 8,484,314 B2
Filed 10/14/2011
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Provisioning applications for a mobile device | ||
Patent #
US 8,494,510 B2
Filed 12/06/2011
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Systems and methods of making a call | ||
Patent #
US 8,504,048 B2
Filed 04/07/2008
|
Current Assignee
Upland Software Inc.
|
Original Assignee
Geos Communications IP Holdings Inc. a wholly owned subsidiary of Augme Technologies Inc.
|
Network traffic management through protocol-configurable transaction processing | ||
Patent #
US 8,533,308 B1
Filed 10/05/2005
|
Current Assignee
F5 Networks Inc.
|
Original Assignee
F5 Networks Inc.
|
Mobile network background traffic data management with optimized polling intervals | ||
Patent #
US 8,539,040 B2
Filed 02/28/2012
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Secure end-to-end transport through intermediary nodes | ||
Patent #
US 8,549,587 B2
Filed 02/14/2012
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Selectively enabling packet concatenation based on a transaction boundary | ||
Patent #
US 8,559,313 B1
Filed 09/09/2011
|
Current Assignee
F5 Networks Inc.
|
Original Assignee
F5 Networks Inc.
|
System and method for executing commands that are non-native to the native environment of a mobile device | ||
Patent #
US 8,561,086 B2
Filed 05/17/2012
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Selectively enabling packet concatenation based on a transaction boundary | ||
Patent #
US 8,565,088 B1
Filed 03/02/2006
|
Current Assignee
F5 Networks Inc.
|
Original Assignee
F5 Networks Inc.
|
System and method of binding a client to a server | ||
Patent #
US 8,606,874 B2
Filed 08/31/2009
|
Current Assignee
Upland Software Inc.
|
Original Assignee
Hipcricket Inc.
|
Selectively enabling packet concatenation based on a transaction boundary | ||
Patent #
US 8,611,222 B1
Filed 08/22/2012
|
Current Assignee
F5 Networks Inc.
|
Original Assignee
F5 Networks Inc.
|
Integrated client for access to remote resources | ||
Patent #
US 8,612,862 B2
Filed 06/27/2008
|
Current Assignee
Microsoft Technology Licensing LLC
|
Original Assignee
Microsoft Corporation
|
Detecting and preserving state for satisfying application requests in a distributed proxy and cache system | ||
Patent #
US 8,621,075 B2
Filed 04/27/2012
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks LLC
|
Cache state management on a mobile device to preserve user experience | ||
Patent #
US 8,635,339 B2
Filed 08/22/2012
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Diskless PC network communication agent system | ||
Patent #
US 8,655,978 B2
Filed 07/05/2011
|
Current Assignee
Jade Quantum Technologies Incorporated
|
Original Assignee
Jade Quantum Technologies Incorporated
|
Centralized publishing of network resources | ||
Patent #
US 8,683,062 B2
Filed 02/28/2008
|
Current Assignee
Microsoft Technology Licensing LLC
|
Original Assignee
Microsoft Corporation
|
Polling | ||
Patent #
US 8,693,494 B2
Filed 03/31/2008
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Cache defeat detection and caching of content addressed by identifiers intended to defeat cache | ||
Patent #
US 8,700,728 B2
Filed 05/17/2012
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Cross-platform event engine | ||
Patent #
US 8,209,709 B2
Filed 07/05/2010
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Distributed system for cache defeat detection and caching of content addressed by identifiers intended to defeat cache | ||
Patent #
US 8,204,953 B2
Filed 11/01/2011
|
Current Assignee
Seven Networks LLC
|
Original Assignee
Seven Networks Inc
|
Electronic-mail filtering for mobile devices | ||
Patent #
US 8,738,050 B2
Filed 01/07/2013
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Mobile device equipped with mobile network congestion recognition to make intelligent decisions regarding connecting to an operator network | ||
Patent #
US 8,750,123 B1
Filed 07/31/2013
|
Current Assignee
Seven Networks LLC
|
Original Assignee
Seven Networks Inc
|
Scripting of soap commands | ||
Patent #
US 8,752,074 B2
Filed 10/04/2011
|
Current Assignee
PTC Inc.
|
Original Assignee
Axeda
|
Maintaining an IP connection in a mobile network | ||
Patent #
US 8,761,756 B2
Filed 09/13/2012
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks International Oy
|
Retrieving data from a server | ||
Patent #
US 8,762,497 B2
Filed 12/19/2011
|
Current Assignee
PTC Inc.
|
Original Assignee
Axeda
|
System and method for dynamically grouping devices based on present device conditions | ||
Patent #
US 8,769,095 B2
Filed 12/26/2012
|
Current Assignee
PTC Inc.
|
Original Assignee
Axeda Acquisition Corp.
|
Integrated messaging | ||
Patent #
US 8,774,844 B2
Filed 04/08/2011
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Dynamic bandwidth adjustment for browsing or streaming activity in a wireless network based on prediction of user behavior when interacting with mobile applications | ||
Patent #
US 8,775,631 B2
Filed 02/25/2013
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Timing of keep-alive messages used in a system for mobile network resource conservation and optimization | ||
Patent #
US 8,782,222 B2
Filed 09/05/2012
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks LLC
|
Application discovery on mobile devices | ||
Patent #
US 8,787,947 B2
Filed 06/18/2008
|
Current Assignee
Seven Networks LLC
|
Original Assignee
Seven Networks Inc
|
Managing configurations of distributed devices | ||
Patent #
US 8,788,632 B2
Filed 10/04/2011
|
Current Assignee
PTC Inc.
|
Original Assignee
Axeda Acquisition Corp.
|
System and methods to route calls over a voice and data network | ||
Patent #
US 8,792,479 B2
Filed 11/27/2012
|
Current Assignee
Upland Software Inc.
|
Original Assignee
Hipcricket Inc.
|
Content delivery to a mobile device from a content service | ||
Patent #
US 8,793,305 B2
Filed 12/13/2007
|
Current Assignee
Seven Networks LLC
|
Original Assignee
Seven Networks Inc
|
System and method of a relay server for managing communications and notification between a mobile device and a web access server | ||
Patent #
US 8,799,410 B2
Filed 04/13/2011
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
System and method of media over an internet protocol communication | ||
Patent #
US 8,804,758 B2
Filed 02/06/2013
|
Current Assignee
Upland Software Inc.
|
Original Assignee
Hipcricket Inc.
|
Maintaining mobile terminal information for secure communications | ||
Patent #
US 8,805,334 B2
Filed 09/05/2008
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Integrated messaging | ||
Patent #
US 8,805,425 B2
Filed 01/28/2009
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Mobile device power management in data synchronization over a mobile network with or without a trigger notification | ||
Patent #
US 8,811,952 B2
Filed 05/05/2011
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Method and system for management of a virtual network connection without heartbeat messages | ||
Patent #
US 8,812,695 B2
Filed 04/03/2013
|
Current Assignee
Seven Networks LLC
|
Original Assignee
Seven Networks Inc
|
System and method for tracking billing events in a mobile wireless network for a network operator | ||
Patent #
US 8,831,561 B2
Filed 04/28/2011
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
System and method for making requests on behalf of a mobile device based on atomic processes for mobile network traffic relief | ||
Patent #
US 8,832,228 B2
Filed 04/26/2012
|
Current Assignee
Seven Networks LLC
|
Original Assignee
Seven Networks Inc
|
Distributed caching for resource and mobile network traffic management | ||
Patent #
US 8,838,783 B2
Filed 07/05/2011
|
Current Assignee
Seven Networks LLC
|
Original Assignee
Seven Networks Inc
|
Flexible real-time inbox access | ||
Patent #
US 8,839,412 B1
Filed 09/13/2012
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Web-based access to data objects | ||
Patent #
US 8,838,744 B2
Filed 01/28/2009
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Mobile traffic categorization and policy for network use optimization while preserving user experience | ||
Patent #
US 8,843,153 B2
Filed 11/01/2011
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Method and system of renegotiating end-to-end voice over internet protocol CODECs | ||
Patent #
US 8,842,568 B2
Filed 11/26/2012
|
Current Assignee
Upland Software Inc.
|
Original Assignee
Hipcricket Inc.
|
System for providing policy based content service in a mobile network | ||
Patent #
US 8,849,902 B2
Filed 06/24/2011
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Hierarchies and categories for management and deployment of policies for distributed wireless traffic optimization | ||
Patent #
US 8,861,354 B2
Filed 12/14/2012
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Policy based content service | ||
Patent #
US 8,862,657 B2
Filed 01/25/2008
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
System of redundantly clustered machines to provide failover mechanisms for mobile traffic management and network resource conservation | ||
Patent #
US 8,868,753 B2
Filed 12/06/2012
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Provisioning of e-mail settings for a mobile terminal | ||
Patent #
US 8,873,411 B2
Filed 01/12/2012
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Signaling optimization in a wireless network for traffic utilizing proprietary and non-proprietary protocols | ||
Patent #
US 8,874,761 B2
Filed 03/15/2013
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Mobile application traffic optimization | ||
Patent #
US 8,886,176 B2
Filed 07/22/2011
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Reporting the state of an apparatus to a remote computer | ||
Patent #
US 8,898,294 B2
Filed 10/03/2011
|
Current Assignee
PTC Inc.
|
Original Assignee
Axeda
|
Optimization of resource polling intervals to satisfy mobile device requests | ||
Patent #
US 8,903,954 B2
Filed 11/22/2011
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Mobile virtual network operator | ||
Patent #
US 8,909,192 B2
Filed 08/11/2011
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Bandwidth measurement | ||
Patent #
US 8,909,759 B2
Filed 10/12/2009
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Detection and management of user interactions with foreground applications on a mobile device in distributed caching | ||
Patent #
US 8,909,202 B2
Filed 01/07/2013
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
System and method for providing a network service in a distributed fashion to a mobile device | ||
Patent #
US 8,914,002 B2
Filed 08/11/2011
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Optimization of mobile traffic directed to private networks and operator configurability thereof | ||
Patent #
US 8,918,503 B2
Filed 08/28/2012
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Method and apparatus for intercepting events in a communication system | ||
Patent #
US RE45,348 E1
Filed 03/16/2012
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Application and network-based long poll request detection and cacheability assessment therefor | ||
Patent #
US 8,966,066 B2
Filed 10/12/2012
|
Current Assignee
Seven Networks LLC
|
Original Assignee
Seven Networks Inc
|
Network protocol proxy | ||
Patent #
US 8,966,112 B1
Filed 11/29/2010
|
Current Assignee
Dell Products LP
|
Original Assignee
Dell Software Inc.
|
Mobile device and method to utilize the failover mechanism for fault tolerance provided for mobile traffic management and network/device resource conservation | ||
Patent #
US 8,977,755 B2
Filed 12/06/2012
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Monitoring mobile application activities for malicious traffic on a mobile device | ||
Patent #
US 8,984,581 B2
Filed 07/11/2012
|
Current Assignee
Seven Networks LLC
|
Original Assignee
Seven Networks Inc
|
Connection architecture for a mobile network | ||
Patent #
US 8,989,728 B2
Filed 09/07/2006
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Predictive content delivery | ||
Patent #
US 9,002,828 B2
Filed 01/02/2009
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Establishing a virtual tunnel between two computer programs | ||
Patent #
US 9,002,980 B2
Filed 09/13/2012
|
Current Assignee
PTC Inc.
|
Original Assignee
Axeda
|
Flexible and dynamic integration schemas of a traffic management system with various network operators for network traffic alleviation | ||
Patent #
US 9,009,250 B2
Filed 12/07/2012
|
Current Assignee
Seven Networks LLC
|
Original Assignee
Seven Networks Inc
|
Mobile network reporting and usage analytics system and method aggregated using a distributed traffic optimization system | ||
Patent #
US 9,021,021 B2
Filed 12/10/2012
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
3D mobile user interface with configurable workspace management | ||
Patent #
US 9,043,731 B2
Filed 03/30/2011
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Mobile network traffic coordination across multiple applications | ||
Patent #
US 9,043,433 B2
Filed 05/25/2011
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Intelligent rendering of information in a limited display environment | ||
Patent #
US 9,047,142 B2
Filed 12/16/2010
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Mobile network traffic coordination across multiple applications | ||
Patent #
US 9,049,179 B2
Filed 01/20/2012
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Network protocol proxy | ||
Patent #
US 9,054,913 B1
Filed 11/29/2010
|
Current Assignee
Dell Products LP
|
Original Assignee
Dell Software Inc.
|
Location-based operations and messaging | ||
Patent #
US 9,055,102 B2
Filed 08/02/2010
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Selective data compression by a distributed traffic management system to reduce mobile data traffic and signaling traffic | ||
Patent #
US 9,060,032 B2
Filed 05/09/2012
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Proxy server associated with a mobile carrier for enhancing mobile traffic management in a mobile network | ||
Patent #
US 9,065,765 B2
Filed 10/08/2013
|
Current Assignee
Seven Networks LLC
|
Original Assignee
Seven Networks Inc
|
Distributed implementation of dynamic wireless traffic policy | ||
Patent #
US 9,077,630 B2
Filed 07/08/2011
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Device resources sharing for network resource conservation | ||
Patent #
US 9,084,105 B2
Filed 04/19/2012
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Mobile network background traffic data management | ||
Patent #
US 9,100,873 B2
Filed 09/14/2012
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Method, intermediate device and computer program code for maintaining persistency | ||
Patent #
US 9,106,606 B1
Filed 11/16/2008
|
Current Assignee
F5 Networks Inc.
|
Original Assignee
F5 Networks Inc.
|
Managing cache to prevent overloading of a wireless network due to user activity | ||
Patent #
US 9,131,397 B2
Filed 06/06/2013
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Exposed control components for customizable load balancing and persistence | ||
Patent #
US 9,130,846 B1
Filed 08/27/2008
|
Current Assignee
F5 Networks Inc.
|
Original Assignee
F5 Networks Inc.
|
Optimized and selective management of policy deployment to mobile clients in a congested network to prevent further aggravation of network congestion | ||
Patent #
US 9,161,258 B2
Filed 03/15/2013
|
Current Assignee
Seven Networks LLC
|
Original Assignee
Seven Networks LLC
|
Radio-awareness of mobile device for sending server-side control signals using a wireless network optimized transport protocol | ||
Patent #
US 9,173,128 B2
Filed 03/06/2013
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks LLC
|
Adaptive device-initiated polling | ||
Patent #
US 9,170,902 B2
Filed 02/20/2013
|
Current Assignee
PTC Inc.
|
Original Assignee
PTC Inc.
|
Dynamic categorization of applications for network access in a mobile network | ||
Patent #
US 9,203,864 B2
Filed 02/04/2013
|
Current Assignee
Seven Networks LLC
|
Original Assignee
Seven Networks LLC
|
Mobile device having content caching mechanisms integrated with a network operator for traffic alleviation in a wireless network and methods therefor | ||
Patent #
US 9,208,123 B2
Filed 12/07/2012
|
Current Assignee
Seven Networks LLC
|
Original Assignee
Seven Networks LLC
|
Rule based extensible authentication | ||
Patent #
US 9,210,177 B1
Filed 06/30/2011
|
Current Assignee
F5 Networks Inc.
|
Original Assignee
F5 Networks Inc.
|
Protocol-configurable transaction processing | ||
Patent #
US 9,225,479 B1
Filed 09/13/2012
|
Current Assignee
F5 Networks Inc.
|
Original Assignee
F5 Networks Inc.
|
Mobile device with application or context aware fast dormancy | ||
Patent #
US 9,241,314 B2
Filed 03/15/2013
|
Current Assignee
Seven Networks LLC
|
Original Assignee
Seven Networks LLC
|
Automatic generation and distribution of policy information regarding malicious mobile traffic in a wireless network | ||
Patent #
US 9,239,800 B2
Filed 07/11/2012
|
Current Assignee
Seven Networks LLC
|
Original Assignee
Seven Networks LLC
|
Extending user relationships | ||
Patent #
US 9,251,193 B2
Filed 10/28/2007
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks LLC
|
Application or context aware fast dormancy | ||
Patent #
US 9,271,238 B2
Filed 03/15/2013
|
Current Assignee
Seven Networks LLC
|
Original Assignee
Seven Networks LLC
|
Request and response characteristics based adaptation of distributed caching in a mobile network | ||
Patent #
US 9,275,163 B2
Filed 10/17/2011
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks LLC
|
Radio-awareness of mobile device for sending server-side control signals using a wireless network optimized transport protocol | ||
Patent #
US 9,277,443 B2
Filed 12/07/2012
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks LLC
|
Systems and methods of making a call | ||
Patent #
US 9,276,965 B2
Filed 08/06/2013
|
Current Assignee
Upland Software Inc.
|
Original Assignee
Hipcricket Inc.
|
Span out load balancing model | ||
Patent #
US 9,292,248 B2
Filed 06/22/2011
|
Current Assignee
Microsoft Technology Licensing LLC
|
Original Assignee
Microsoft Technology Licensing LLC
|
System and method for a mobile device to use physical storage of another device for caching | ||
Patent #
US 9,300,719 B2
Filed 01/14/2013
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Systems and methods for application management of mobile device radio state promotion and demotion | ||
Patent #
US 9,307,493 B2
Filed 03/15/2013
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks LLC
|
System and method for reduction of mobile network traffic used for domain name system (DNS) queries | ||
Patent #
US 9,325,662 B2
Filed 01/09/2012
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks LLC
|
User as an end point for profiling and optimizing the delivery of content and data in a wireless network | ||
Patent #
US 9,326,189 B2
Filed 02/04/2013
|
Current Assignee
Seven Networks LLC
|
Original Assignee
Seven Networks LLC
|
Wireless traffic management system cache optimization using http headers | ||
Patent #
US 9,330,196 B2
Filed 06/14/2012
|
Current Assignee
Seven Networks LLC
|
Original Assignee
Seven Networks LLC
|
System and method of binding a client to a server | ||
Patent #
US 9,401,974 B2
Filed 12/10/2013
|
Current Assignee
Upland Software Inc.
|
Original Assignee
Upland Software III LLC
|
Mobile application traffic optimization | ||
Patent #
US 9,407,713 B2
Filed 01/16/2012
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks LLC
|
Managing configurations of distributed devices | ||
Patent #
US 9,491,049 B2
Filed 07/18/2014
|
Current Assignee
PTC Inc.
|
Original Assignee
PTC Inc.
|
System and method for dynamically grouping devices based on present device conditions | ||
Patent #
US 9,491,071 B2
Filed 06/27/2014
|
Current Assignee
PTC Inc.
|
Original Assignee
PTC Inc.
|
Scripting of SOAP commands | ||
Patent #
US 9,591,065 B2
Filed 06/06/2014
|
Current Assignee
PTC Inc.
|
Original Assignee
PTC Inc.
|
System and method for directing network traffic in tunneling applications | ||
Patent #
US 9,614,772 B1
Filed 11/21/2003
|
Current Assignee
F5 Networks Inc.
|
Original Assignee
F5 Networks Inc.
|
DEVICE FOR PROVIDING SECURITY BARRIER FOR NETWORK | ||
Patent #
US 20170099258A1
Filed 10/05/2015
|
Current Assignee
Zyxel Communications Incorporated
|
Original Assignee
Zyxel Communications Incorporated
|
Adaptive device-initiated polling | ||
Patent #
US 9,674,067 B2
Filed 10/23/2015
|
Current Assignee
PTC Inc.
|
Original Assignee
PTC Inc.
|
Managing configurations of distributed devices | ||
Patent #
US 9,712,385 B2
Filed 04/06/2016
|
Current Assignee
PTC Inc.
|
Original Assignee
PTC Inc.
|
Mobile device configured for communicating with another mobile device associated with an associated user | ||
Patent #
US 9,712,986 B2
Filed 03/22/2012
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks LLC
|
Scalable address resolution in a communications environment | ||
Patent #
US 9,736,006 B2
Filed 06/19/2008
|
Current Assignee
Radius Networks inc.
|
Original Assignee
Radius Networks inc.
|
Span out load balancing model | ||
Patent #
US 9,742,876 B2
Filed 02/08/2016
|
Current Assignee
Microsoft Technology Licensing LLC
|
Original Assignee
Microsoft Technology Licensing LLC
|
Device for providing security barrier for network | ||
Patent #
US 9,769,118 B2
Filed 10/05/2015
|
Current Assignee
Zyxel Communications Incorporated
|
Original Assignee
Zyxel Communications Incorporated
|
Persistence based on server response in an IP multimedia subsystem (IMS) | ||
Patent #
US 9,832,069 B1
Filed 05/29/2009
|
Current Assignee
F5 Networks Inc.
|
Original Assignee
F5 Networks Inc.
|
Operation modes for mobile traffic optimization and concurrent management of optimized and non-optimized traffic | ||
Patent #
US 9,832,095 B2
Filed 12/14/2012
|
Current Assignee
Seven Networks LLC
|
Original Assignee
Seven Networks LLC
|
SPAN OUT LOAD BALANCING MODEL | ||
Patent #
US 20170374179A1
Filed 07/12/2017
|
Current Assignee
Microsoft Technology Licensing LLC
|
Original Assignee
Microsoft Technology Licensing LLC
|
Method, intermediate device and computer program code for maintaining persistency | ||
Patent #
US 9,967,331 B1
Filed 07/02/2015
|
Current Assignee
F5 Networks Inc.
|
Original Assignee
F5 Networks Inc.
|
Establishing a virtual tunnel between two computers | ||
Patent #
US 10,069,939 B2
Filed 04/03/2015
|
Current Assignee
PTC Inc.
|
Original Assignee
PTC Inc.
|
Retrieving data from a server | ||
Patent #
US 10,069,937 B2
Filed 06/20/2014
|
Current Assignee
PTC Inc.
|
Original Assignee
PTC Inc.
|
System and method for dynamically grouping devices based on present device conditions | ||
Patent #
US 10,212,055 B2
Filed 09/26/2016
|
Current Assignee
PTC Inc.
|
Original Assignee
PTC Inc.
|
Enhanced customer service for mobile carriers using real-time and historical mobile application and traffic or optimization data associated with mobile devices in a mobile network | ||
Patent #
US 10,263,899 B2
Filed 04/10/2013
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks LLC
|
SPAN OUT LOAD BALANCING MODEL | ||
Patent #
US 20160156745A1
Filed 02/08/2016
|
Current Assignee
Microsoft Technology Licensing LLC
|
Original Assignee
Microsoft Technology Licensing LLC
|
Systems and methods for protecting network devices by a firewall | ||
Patent #
US 10,541,971 B2
Filed 01/17/2017
|
Current Assignee
Cryptzone North America Inc.
|
Original Assignee
Cryptzone North America Inc.
|
Scripting of soap commands | ||
Patent #
US 10,708,346 B2
Filed 04/03/2018
|
Current Assignee
PTC Inc.
|
Original Assignee
PTC Inc.
|
System and method of providing multimedia service to a user equipment | ||
Patent #
US 10,721,597 B2
Filed 12/19/2015
|
Current Assignee
Reliance Jio Infocomm Limited
|
Original Assignee
Reliance Jio Infocomm Limited
|
System and method for establishing a virtual private network | ||
Patent #
US 20060005240A1
Filed 01/24/2005
|
Current Assignee
Citrix Systems Inc.
|
Original Assignee
Citrix Application Networking LLC
|
Distributing tasks in data communications | ||
Patent #
US 7,644,188 B2
Filed 02/25/2002
|
Current Assignee
Intel Corporation
|
Original Assignee
Intel Corporation
|
Network traffic accelerator system and method | ||
Patent #
US 7,480,312 B2
Filed 08/19/2003
|
Current Assignee
TEHUTI NETWORKS LTD.
|
Original Assignee
TEHUTI NETWORKS LTD.
|
Method and apparatus for monitoring the availability of network resources | ||
Patent #
US 7,496,659 B1
Filed 08/06/2003
|
Current Assignee
Cisco Technology Incorporated
|
Original Assignee
Cisco Technology Incorporated
|
Cooperative proxy auto-discovery and connection interception | ||
Patent #
US 7,318,100 B2
Filed 08/12/2003
|
Current Assignee
Riverbed Technology Incorporated
|
Original Assignee
Riverbed Technology Incorporated
|
TCP proxy connection management in a gigabit environment | ||
Patent #
US 7,328,267 B1
Filed 05/02/2002
|
Current Assignee
Cisco Technology Incorporated
|
Original Assignee
Cisco Technology Incorporated
|
Systems and Methods of Symmetric Transport Control Protocol Compression | ||
Patent #
US 20080046616A1
Filed 08/21/2006
|
Current Assignee
Citrix Systems Inc.
|
Original Assignee
Citrix Systems Inc.
|
METHODS AND SYSTEMS FOR ROUTING PACKETS IN A VPN-CLIENT-TO-VPN-CLIENT CONNECTION VIA AN SSL/VPN NETWORK APPLIANCE | ||
Patent #
US 20080034416A1
Filed 08/03/2006
|
Current Assignee
Citrix Systems Inc.
|
Original Assignee
Citrix Systems Inc.
|
Systems and Methods for Providing Dynamic Spillover of Virtual Servers Based on Bandwidth | ||
Patent #
US 20080049786A1
Filed 03/12/2007
|
Current Assignee
Citrix Systems Inc.
|
Original Assignee
Citrix Systems Inc.
|
Electronic menu document creator in a virtual financial environment | ||
Patent #
US 7,167,844 B1
Filed 12/22/1999
|
Current Assignee
Accenture Global Services Limited
|
Original Assignee
Accenture LLP
|
Transparent conveyor for check-out scanning | ||
Patent #
US 7,159,777 B2
Filed 04/02/2004
|
Current Assignee
Silverbrook Research Pty Limited
|
Original Assignee
Silverbrook Research Pty Limited
|
Scheme for supporting real-time packetization and retransmission in rate-based streaming applications | ||
Patent #
US 7,164,680 B2
Filed 06/04/2001
|
Current Assignee
Pendragon Wireless LLC
|
Original Assignee
Koninklijke Philips N.V.
|
Method and system for efficient and automated version management of embedded objects in web documents | ||
Patent #
US 7,159,014 B2
Filed 12/03/2001
|
Current Assignee
Cisco Technology Incorporated
|
Original Assignee
Fineground Networks LLC
|
Transport layer relay method, transport layer relay device, and program | ||
Patent #
US 20070008883A1
Filed 07/07/2004
|
Current Assignee
NEC Corporation
|
Original Assignee
NEC Corporation
|
Architecture and API for of transport and upper layer protocol processing acceleration | ||
Patent #
US 7,184,445 B2
Filed 02/11/2004
|
Current Assignee
Avago Technologies International Sales Pte Limited
|
Original Assignee
Silverback Systems Inc.
|
Face determination | ||
Patent #
US 7,175,089 B2
Filed 04/02/2004
|
Current Assignee
Silverbrook Research Pty Limited
|
Original Assignee
Silverbrook Research Pty Limited
|
Facilitating user interaction | ||
Patent #
US 7,178,719 B2
Filed 04/02/2004
|
Current Assignee
Silverbrook Research Pty Limited
|
Original Assignee
Silverbrook Research Pty Limited
|
Presentation of media content from multiple media sources | ||
Patent #
US 7,178,106 B2
Filed 08/21/2001
|
Current Assignee
Rovi Technologies Corporation
|
Original Assignee
Sonic Solutions
|
Client-side techniques for web server allocation | ||
Patent #
US 6,175,869 B1
Filed 04/08/1998
|
Current Assignee
WSOU Investments LLC
|
Original Assignee
Lucent Technologies Inc.
|
Method and product for enchancing performance of computer networks including shared storage objects | ||
Patent #
US 5,881,229 A
Filed 04/26/1996
|
Current Assignee
Intel Corporation
|
Original Assignee
Shiva Corp.
|
System for localizing and sensing objects and providing alerts | ||
Patent #
US 6,847,892 B2
Filed 10/29/2001
|
Current Assignee
Rateze Remote Mgmt. L.L.C.
|
Original Assignee
Digital Angel Corporation
|
Methods and apparatus for transmission of analog channels over digital packet networks | ||
Patent #
US 6,993,016 B1
Filed 11/16/2000
|
Current Assignee
Venture Lending Leasing III Incorporated As Agent
|
Original Assignee
Juniper Networks Incorporated
|
Automatic retrieval of changed files by a network software agent | ||
Patent #
US 6,029,175 A
Filed 06/07/1996
|
Current Assignee
Teknowledge Corporation
|
Original Assignee
Teknowledge Corporation
|
System and method for caching JavaServer Pages™ responses | ||
Patent #
US 6,697,849 B1
Filed 05/01/2000
|
Current Assignee
Oracle America Inc.
|
Original Assignee
Sun Microsystems Incorporated
|
Network file server sharing local caches of file access information in data processors assigned to respective file systems | ||
Patent #
US 6,192,408 B1
Filed 09/26/1997
|
Current Assignee
EMC Corporation
|
Original Assignee
EMC Corporation
|
Adaptive traffic bypassing in an intercepting network driver | ||
Patent #
US 6,687,732 B1
Filed 08/05/1999
|
Current Assignee
Excalibur IP LLC
|
Original Assignee
Inktomi Corporation
|
Location-independent packet routing and secure access in a short-range wireless networking environment | ||
Patent #
US 6,691,227 B1
Filed 09/08/2000
|
Current Assignee
Reefedge Networks LLC
|
Original Assignee
Reefedge Inc.
|
Method and apparatus for adjusting packet transmission volume from a source | ||
Patent #
US 6,990,070 B1
Filed 12/17/1999
|
Current Assignee
RPX Clearinghouse LLC
|
Original Assignee
Nortel Networks Limited
|
Decoding steganographic messages embedded in media signals | ||
Patent #
US 6,681,029 B1
Filed 07/06/2000
|
Current Assignee
Digimarc Corporation
|
Original Assignee
Digimarc Corporation
|
Method and device for performing integrated caching in a data communication network | ||
Patent #
US 20060015570A1
Filed 06/29/2005
|
Current Assignee
Citrix Systems Inc.
|
Original Assignee
NetScaler Inc.
|
System and method for increasing data throughout using a block acknowledgement | ||
Patent #
US 20060018332A1
Filed 07/21/2004
|
Current Assignee
Nokia Technologies Oy
|
Original Assignee
Nokia Corporation
|
Method and system for providing direct data placement support | ||
Patent #
US 20060034283A1
Filed 08/13/2004
|
Current Assignee
International Business Machines Corporation
|
Original Assignee
International Business Machines Corporation
|
System and method for integrated on-demand delivery of operating system and applications | ||
Patent #
US 20060031547A1
Filed 05/07/2004
|
Current Assignee
Wyse Technology Incorporated
|
Original Assignee
Wyse Technology Incorporated
|
Connection management system and method | ||
Patent #
US 7,007,092 B2
Filed 10/05/2001
|
Current Assignee
Juniper Networks Incorporated
|
Original Assignee
Juniper Networks Incorporated
|
Systems and methods for uniquely identifying networks by correlating each network name with the application programming interfaces of transport protocols supported by the network | ||
Patent #
US 7,000,012 B2
Filed 04/23/2001
|
Current Assignee
Microsoft Technology Licensing LLC
|
Original Assignee
Microsoft Corporation
|
Method to offload a network stack | ||
Patent #
US 7,007,103 B2
Filed 04/30/2002
|
Current Assignee
Microsoft Technology Licensing LLC
|
Original Assignee
Microsoft Corporation
|
Flexible teleport architecture | ||
Patent #
US 20060041635A1
Filed 05/28/2004
|
Current Assignee
Microsoft Technology Licensing LLC
|
Original Assignee
Microsoft Corporation
|
Application-layer monitoring of communication between one or more database clients and one or more database servers | ||
Patent #
US 20060053164A1
Filed 09/03/2004
|
Current Assignee
CF DB EZ LLC
|
Original Assignee
Teracruz Inc.
|
Client-side network access polices and management applications | ||
Patent #
US 20050022012A1
Filed 09/30/2002
|
Current Assignee
Ginegar LLC
|
Original Assignee
Fiberlink Communications Corporation
|
Method and system for mobility across heterogeneous address spaces | ||
Patent #
US 20050013280A1
Filed 07/14/2003
|
Current Assignee
Alcatel-Lucent SA
|
Original Assignee
Alcatel-Lucent USA Inc.
|
Multi-layer based method for implementing network firewalls | ||
Patent #
US 20050022011A1
Filed 06/06/2003
|
Current Assignee
Microsoft Technology Licensing LLC
|
Original Assignee
Microsoft Corporation
|
Transport system for instant messaging | ||
Patent #
US 20050005014A1
Filed 07/01/2003
|
Current Assignee
Microsoft Technology Licensing LLC
|
Original Assignee
Microsoft Corporation
|
Advanced URL and IP features | ||
Patent #
US 20050022031A1
Filed 05/28/2004
|
Current Assignee
Microsoft Technology Licensing LLC
|
Original Assignee
Microsoft Corporation
|
Method of operation of an intelligent transpartent gateway during an FTP session | ||
Patent #
US 20050021762A1
Filed 05/11/2004
|
Current Assignee
Microsoft Technology Licensing LLC
|
Original Assignee
Microsoft Corporation
|
Load balancing service | ||
Patent #
US 20050033858A1
Filed 08/31/2004
|
Current Assignee
Akamai Technologies Inc.
|
Original Assignee
Akamai Technologies Inc.
|
Method and apparatus for automatic gain control of a wireless receiver | ||
Patent #
US 20050031058A1
Filed 07/09/2004
|
Current Assignee
Telefonaktiebolaget LM Ericsson
|
Original Assignee
Telefonaktiebolaget LM Ericsson
|
Method, system and program product for validating remotely cached dynamic content web pages | ||
Patent #
US 20050033926A1
Filed 08/06/2003
|
Current Assignee
International Business Machines Corporation
|
Original Assignee
International Business Machines Corporation
|
Method and system for dynamic interleaving | ||
Patent #
US 20050027788A1
Filed 06/17/2004
|
Current Assignee
Citrix Systems Inc.
|
Original Assignee
Citrix Systems Inc.
|
Accelerating network performance by striping and parallelization of TCP connections | ||
Patent #
US 20050025150A1
Filed 08/01/2003
|
Current Assignee
F5 Networks Inc.
|
Original Assignee
Itworx Egypt
|
A SYSTEM AND METHOD OF EXPLOITING THE SECURITY OF A SECURE COMMUNICATION CHANNEL TO SECURE A NON-SECURE COMMUNICATION CHANNEL | ||
Patent #
US 20050050317A1
Filed 05/28/2004
|
Current Assignee
Citrix Systems Inc.
|
Original Assignee
William Harwood, Andre Kramer
|
System and method for communication between computers via an integrated hardware device | ||
Patent #
US 20050055690A1
Filed 09/10/2003
|
Current Assignee
Microsoft Technology Licensing LLC
|
Original Assignee
Microsoft Corporation
|
Information communicating system, information transmitting apparatus and information transmitting method | ||
Patent #
US 20040010604A1
Filed 07/15/2002
|
Current Assignee
CMIC Company Limited
|
Original Assignee
CMIC Company Limited
|
Caching control for streaming media | ||
Patent #
US 20040003101A1
Filed 06/26/2002
|
Current Assignee
Microsoft Technology Licensing LLC
|
Original Assignee
Microsoft Technology Licensing LLC
|
Process-mode independent driver model | ||
Patent #
US 20040003137A1
Filed 06/26/2002
|
Current Assignee
Microsoft Technology Licensing LLC
|
Original Assignee
Microsoft Corporation
|
Method and system for protecting web sites from public internet threats | ||
Patent #
US 20040010601A1
Filed 07/09/2002
|
Current Assignee
Akamai Technologies Inc.
|
Original Assignee
Akamai Technologies Inc.
|
System for fast recovery from losses for reliable data communication protocols | ||
Patent #
US 20040008693A1
Filed 03/25/2003
|
Current Assignee
Akamai Technologies Inc.
|
Original Assignee
Akamai Technologies Inc.
|
Method for intercepting network packets in a computing device | ||
Patent #
US 6,678,734 B1
Filed 11/13/1999
|
Current Assignee
Rambus Inc.
|
Original Assignee
SSH Communications Security Ltd.
|
Method for caching and delivery of compressed content in a content delivery network | ||
Patent #
US 20040010621A1
Filed 07/11/2002
|
Current Assignee
Akamai Technologies Inc.
|
Original Assignee
Akamai Technologies Inc.
|
Method and apparatus for browsing using alternative linkbases | ||
Patent #
US 20040031058A1
Filed 05/08/2003
|
Current Assignee
Convergent Media Solutions LLC
|
Original Assignee
Teleshuttle Tech2 LLC
|
Delay cache method and apparatus | ||
Patent #
US 20040034744A1
Filed 08/13/2002
|
Current Assignee
Hewlett-Packard Development Company L.P.
|
Original Assignee
Hewlett-Packard Development Company L.P.
|
Third party authentication of files in digital systems | ||
Patent #
US 20040049515A1
Filed 09/09/2003
|
Current Assignee
Intellectual Ventures I LLC
|
Original Assignee
HyperSpace Communications Inc.
|
System and method for optimizing internet applications | ||
Patent #
US 20040044731A1
Filed 03/24/2003
|
Current Assignee
Warp Solutions Inc.
|
Original Assignee
Warp Solutions Inc.
|
Providing a notification when a plurality of users are altering similar data in a health care solution environment | ||
Patent #
US 6,701,345 B1
Filed 04/13/2000
|
Current Assignee
Accenture Global Services Limited
|
Original Assignee
Accenture LLP
|
Network traffic accelerator system and method | ||
Patent #
US 20040042487A1
Filed 08/19/2003
|
Current Assignee
TEHUTI NETWORKS LTD.
|
Original Assignee
TEHUTI NETWORKS INC.
|
Method and apparatus for managing internal caches and external caches in a data processing system | ||
Patent #
US 6,507,891 B1
Filed 07/22/1999
|
Current Assignee
International Business Machines Corporation
|
Original Assignee
International Business Machines Corporation
|
Methods, systems and computer program products for kernel based transaction processing | ||
Patent #
US 20030023767A1
Filed 07/26/2001
|
Current Assignee
International Business Machines Corporation
|
Original Assignee
International Business Machines Corporation
|
Encrypted packet inspection | ||
Patent #
US 20030018891A1
Filed 06/07/2002
|
Current Assignee
Ncipher Security Limited
|
Original Assignee
nCipher Corporation Limited
|
Secure sockets layer proxy architecture | ||
Patent #
US 20030014628A1
Filed 07/06/2001
|
Current Assignee
Juniper Networks Incorporated
|
Original Assignee
Juniper Networks Incorporated
|
Network caching system for streamed applications | ||
Patent #
US 20030009538A1
Filed 11/06/2001
|
Current Assignee
Numecent Holdings Incorporated
|
Original Assignee
Credit Managers Association Of California Doing Business AS
|
Bufferless secure sockets layer architecture | ||
Patent #
US 20030014625A1
Filed 07/06/2001
|
Current Assignee
Juniper Networks Incorporated
|
Original Assignee
Juniper Networks Incorporated
|
Non-proxy internet communication | ||
Patent #
US 20030014624A1
Filed 02/26/2002
|
Current Assignee
Andes Networks Inc.
|
Original Assignee
Andes Networks Inc.
|
Secure sockets layer cut through architecture | ||
Patent #
US 20030014623A1
Filed 07/06/2001
|
Current Assignee
Juniper Networks Incorporated
|
Original Assignee
Juniper Networks Incorporated
|
FIFO architecture with in-place cryptographic service | ||
Patent #
US 20030039354A1
Filed 08/27/2001
|
Current Assignee
Texas Instruments Inc.
|
Original Assignee
Texas Instruments Inc.
|
System and method for maintaining statefulness during client-server interactions | ||
Patent #
US 20030037108A1
Filed 08/16/2002
|
Current Assignee
Juniper Networks Incorporated
|
Original Assignee
Juniper Networks Incorporated
|
HTTP multiplexor/demultiplexor system for use in secure transactions | ||
Patent #
US 20030033520A1
Filed 04/29/2002
|
Current Assignee
Juniper Networks Incorporated
|
Original Assignee
Juniper Networks Incorporated
|
Packet transfer method for hierarchical packet network, hierarchical packet communication system, and gate node, edge node and mobile terminal for use with hierarchical packet communication system, as well as handover method and routing node for packet network | ||
Patent #
US 20030026241A1
Filed 09/28/2001
|
Current Assignee
Fujitsu Limited
|
Original Assignee
Fujitsu Limited
|
Content caching with special handling of multiple identical requests for content | ||
Patent #
US 20030051100A1
Filed 09/12/2001
|
Current Assignee
International Business Machines Corporation
|
Original Assignee
International Business Machines Corporation
|
Systems and methods for implementing host-based security in a computer network | ||
Patent #
US 20030061505A1
Filed 08/30/2002
|
Current Assignee
Avago Technologies International Sales Pte Limited
|
Original Assignee
Adaptec Incorporated
|
System providing internet access management with router-based policy enforcement | ||
Patent #
US 20030055962A1
Filed 08/30/2001
|
Current Assignee
Check Point Software Technologies Incorporated
|
Original Assignee
Check Point Software Technologies Incorporated
|
Synthetic transaction monitor | ||
Patent #
US 20030055883A1
Filed 03/29/2002
|
Current Assignee
BMC Software Incorporated
|
Original Assignee
BMC Software Incorporated
|
System and method for flushing bean cache | ||
Patent #
US 20030051102A1
Filed 08/05/2002
|
Current Assignee
Oracle International Corporation
|
Original Assignee
BEA Systems Incorporated
|
Secure remote access using enterprise peer networks | ||
Patent #
US 20030046587A1
Filed 07/03/2002
|
Current Assignee
NetSilica Inc.
|
Original Assignee
NetSilica Inc.
|
Secure remote access to data between peers | ||
Patent #
US 20030046586A1
Filed 07/03/2002
|
Current Assignee
NetSilica Inc.
|
Original Assignee
NetSilica Inc.
|
Application gateway system, and method for maintaining security in a packet-switched information network | ||
Patent #
US 20030110379A1
Filed 12/07/2001
|
Current Assignee
AuthenTec Incorporated
|
Original Assignee
AuthenTec Incorporated
|
Secure and reliable document delivery | ||
Patent #
US 20020004902A1
Filed 06/21/2001
|
Current Assignee
BAE Systems Applied Intelligence US Corp.
|
Original Assignee
Message Secure Corp.
|
Capping a printhead against a transfer roller | ||
Patent #
US 6,334,664 B1
Filed 12/11/1999
|
Current Assignee
Memjet Technology Ltd.
|
Original Assignee
Silverbrook Research Pty Limited
|
System and method for network caching | ||
Patent #
US 20020007404A1
Filed 04/16/2001
|
Current Assignee
Circadence Corporation
|
Original Assignee
Circadence Corporation
|
Approach for managing and providing content to users | ||
Patent #
US 20020007402A1
Filed 01/17/2001
|
Current Assignee
R2 Solutions LLC
|
Original Assignee
Yahoo Inc.
|
Flexible remote data mirroring | ||
Patent #
US 20020016827A1
Filed 06/02/2001
|
Current Assignee
Intellectual Ventures Assets 78 LLC
|
Original Assignee
Miralink Corporation
|
Systems and methods for packet sequencing | ||
Patent #
US 20020032798A1
Filed 08/16/2001
|
Current Assignee
SPONTANEOUS NETWORKS INC.
|
Original Assignee
SPONTANEOUS NETWORKS INC.
|
Systems and methods for packet distribution | ||
Patent #
US 20020038339A1
Filed 08/16/2001
|
Current Assignee
SPONTANEOUS NETWORKS INC.
|
Original Assignee
SPONTANEOUS NETWORKS INC.
|
Security mechanisms in a web server | ||
Patent #
US 6,363,478 B1
Filed 09/17/1998
|
Current Assignee
International Business Machines Corporation
|
Original Assignee
International Business Machines Corporation
|
Client-side resource-based load-balancing with delayed-resource-binding using TCP state migration to WWW server farm | ||
Patent #
US 6,182,139 B1
Filed 06/23/1998
|
Current Assignee
Resonate
|
Original Assignee
Resonate
|
Method computer program product, and system for assessing the performance of a packet schedule | ||
Patent #
US 6,173,325 B1
Filed 07/31/1998
|
Current Assignee
Microsoft Technology Licensing LLC
|
Original Assignee
Microsoft Corporation
|
Method and system coordinating actions among a group of servers | ||
Patent #
US 6,170,017 B1
Filed 05/08/1997
|
Current Assignee
International Business Machines Corporation
|
Original Assignee
International Business Machines Corporation
|
Determining how changes to underlying data affect cached objects | ||
Patent #
US 6,026,413 A
Filed 08/01/1997
|
Current Assignee
International Business Machines Corporation
|
Original Assignee
International Business Machines Corporation
|
Method and apparatus for selective data caching implemented with noncacheable and cacheable data for improved cache performance in a computer networking system | ||
Patent #
US 6,021,470 A
Filed 03/17/1997
|
Current Assignee
Oracle International Corporation
|
Original Assignee
Oracle Corporation
|
Apparatus and methods for use therein for an ISDN LAN modem that displays fault information to local hosts through interception of host DNS request messages | ||
Patent #
US 6,023,724 A
Filed 09/26/1997
|
Current Assignee
Hewlett Packard Enterprise Development LP
|
Original Assignee
3Com Corporation
|
Methods and apparatus for efficient caching in a distributed environment | ||
Patent #
US 5,864,837 A
Filed 06/12/1996
|
Current Assignee
Unisys Corporation
|
Original Assignee
Unisys Corporation
|
Method and apparatus for packet data transmission | ||
Patent #
US 5,708,656 A
Filed 09/11/1996
|
Current Assignee
Nokia Technologies Oy
|
Original Assignee
Nokia Mobile Phones UK Limited
|
36 Claims
-
1. A method for routing packets from a gateway to an endpoint, the method comprising:
-
(a) associating a private internet protocol (IP) address with an endpoint having a public IP address;
(b) capturing a packet addressed to the private IP address of the endpoint;
(c) applying a policy to the packet; and
(d) transmitting the packet to the public IP address of the endpoint, responsive to the application of the policy to the packet. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8)
-
-
9. A device for routing packets from a gateway to an endpoint, the device comprising:
-
an addressing element associating a private IP address with an endpoint having a public IP address;
a receiver in communication with the addressing element intercepting a packet destined for the private IP address of the endpoint;
a policy engine in communication with the receiver receiving the packet and transmitting the packet to the endpoint responsive to a policy applied to the packet; and
a transmitter in communication with the receiver, the policy engine, and the addressing element performing a network address translation on the packet and transmitting the packet to an endpoint. - View Dependent Claims (10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22)
-
-
23. A system for routing packets from a gateway to an endpoint, the system comprising:
-
a gateway comprising a kernel and an application space; and
a device, in communication with the gateway, comprising;
an addressing element associating a private IP address with an endpoint having a public IP address;
a receiver in communication with the addressing element intercepting a packet addressed to the private IP address of the endpoint;
a policy engine in communication with the receiver receiving the packet and transmitting the packet responsive to a policy applied to the packet; and
a transmitter in communication with the receiver, the policy engine, and the addressing element performing a network address translation on the packet and transmitting the packet to the endpoint. - View Dependent Claims (24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36)
-
1 Specification
This present application claims priority to U.S. Provisional Patent Application No. 60/590,837, entitled “Ad Hoc Distributed Networks And Remote Access Architecture,” filed Jul. 23, 2004, and U.S. Provisional Patent Application No. 60/601,431, entitled “System And Method For Assuring Redundancy In Remote Access Solutions,” filed Aug. 13, 2004, and U.S. Provisional Patent Application No. 60/607,420, entitled “Virtual Network Bridging”, filed Sep. 3, 2004, and U.S. Provisional Patent Application No. 60/634,379, entitled “Securing Access to Private Networks from End Points Based on Encryption and Authentication Technology Built into the USB or Other Peripheral Devices Without the Need for Additional Software on the Host Operating System”, filed Dec. 7, 2004, all of which are incorporated herein by reference.
The present invention relates to a method and systems for securing routing packets and, in particular, to a method and systems for routing packets from a gateway to an endpoint.
Conventional methods of routing packets between a gateway and an endpoint implement architectures such as Internet Protocol Security (IPSec) and Point-to-Point Tunneling Protocol (PPTP) virtual private network (VPN) architectures. These types of architectures typically provide layer-2 network access by creating a point-to-point network layer tunnel between a remote endpoint and VPN gateway. Providing access at this layer provides support for routing network traffic originating either from the endpoint or from the gateway. The endpoint receives an internal network address representation and, once connected to the VPN gateway, the endpoint is treated as a virtual internal resource.
Typically, implementing these architectures provides a user of an endpoint with maximum functionality, at the cost of security to a private network and protected resources behind the gateway. One security risk resulting from implementation of conventional methods is a consequence of the typical requirement for modifying a routing table on the endpoint to reflect connectivity to the private network behind the VPN gateway. The modification of the routing table provides the endpoint with information about the private network that may be manipulated to propagate worm-virus hybrids, Trojan viruses, and malicious, unauthorized access to the protected resources.
Conventional implementations of a VPN gateway provide functionality at the low-level kernel layer. However, the kernel layer typically lacks the ability to increase security by accessing information regarding which applications generated network packets and applying security policies to packets based on the identified applications. Additionally, traditional VPN endpoints rely on unsecured kernel routing processes to identify packets that constitute security risks, and may rely upon secondary or tertiary packet inspection to identify malicious data, increasing network level latency.
Conventional VPN gateways create a Virtual Network Interface on the remote endpoint. This interface is a logical hardware interface and may be used to create a network routing table entry within the network kernel space on the endpoint to enable delivery of network traffic. In conventional implementations, the network routing table entry, and the information it provides to the endpoint about the private network, increases security risks to the private network. Furthermore, during the routing of the packets for inspection, the packet is susceptible to alteration and misuse by third-party software or malicious users. A method of providing a VPN solution that permits trusted two-way communication between a gateway and an endpoint, without modifying the endpoint routing table or creating a Virtual Network Interface would be desirable.
In one aspect, the present invention relates to a method of routing packets from a gateway to an endpoint, including the step of associating a private internet protocol (IP) address with an endpoint having a public IP address. A packet addressed to the private IP address of the endpoint is captured. A policy is applied to the packet. The packet is transmitted to the public IP address of the endpoint, responsive to the application of the policy to the packet.
In one embodiment, a driver on the gateway captures a packet addressed to the private IP address of the endpoint. In another embodiment, the driver complies with the Network Driver Interface Specification (NDIS). In still another embodiment, the policy is applied to the packet prior to routing the packet to the endpoint. In yet another embodiment, a network address translation is performed to transform the private IP address of the endpoint to the public IP address of the endpoint.
In another aspect, the present invention relates to a device for routing packets from a gateway to an endpoint. The device includes an addressing element, a receiver, a policy engine, and a transmitter. The addressing element associates a private IP address with an endpoint having a public IP address. The receiver, in communication with the addressing element, intercepts a packet destined for the private IP address of the endpoint. The policy engine, in communication with the receiver, receives the packet and transmitting the packet to the endpoint responsive to a policy applied to the packet. A transmitter, in communication with the receiver, the policy engine, and the addressing element, performs a network address translation on the packet and transmitting the packet to an endpoint.
In one embodiment, the receiver comprises a driver in compliance with NDIS. In another embodiment, the receiver is a process executing in kernel mode. In still another embodiment, the receiver forwards the intercepted packet to the policy engine. In one embodiment, the policy engine executes in user mode. In another embodiment, the policy engine applies an access control list to the packet. In one embodiment, the transmitter transforms a private IP address of the packet to the public IP address associated with the endpoint. In another embodiment, the transmitter is a process executing in kernel mode.
In another aspect, the present invention relates to a system for routing packets from a gateway to an endpoint, including a gateway and a device. The gateway includes a kernel and an application space. The device, in communication with the gateway, comprises an addressing element, a receiver, a policy engine, and a transmitter. The addressing element associates a private IP address with an endpoint having a public IP address. The receiver, in communication with the addressing element, intercepts a packet addressed to the private IP address of the endpoint. The policy engine, in communication with the receiver, receiving the packet and transmitting the packet responsive to a policy applied to the packet. The transmitter, in communication with the receiver, the policy engine, and the addressing element, performs a network address translation on the packet and transmits the packet to the endpoint.
In one embodiment, the receiver comprises a driver in compliance with NDIS. In another embodiment, the receiver is a process executing in kernel mode. In still another embodiment, the receiver forwards the intercepted packet to the policy engine. In one embodiment, the policy engine executes in user mode. In another embodiment, the policy engine applies an access control list to the packet. In one embodiment, the transmitter transforms a private IP address of the packet to the public IP address associated with the endpoint. In another embodiment, the transmitter is a process executing in kernel mode.
These and other aspects of this invention will be readily apparent from the detailed description below and the appended drawings, which are meant to illustrate and not to limit the invention, and in which:
Referring now to
As shown in
The central processing unit 202 is any logic circuitry that responds to and processes instructions fetched from the main memory unit 204. In many embodiments, the central processing unit is provided by a microprocessor unit, such as: the 8088, the 80286, the 80386, the 80486, the Pentium, Pentium Pro, the Pentium II, the Celeron, or the Xeon processor, all of which are manufactured by Intel Corporation of Mountain View, Calif.; the 68000, the 68010, the 68020, the 68030, the 68040, the PowerPC 601, the PowerPC604, the PowerPC604e, the MPC603e, the MPC603ei, the MPC603ev, the MPC603r, the MPC603p, the MPC740, the MPC745, the MPC750, the MPC755, the MPC7400, the MPC7410, the MPC7441, the MPC7445, the MPC7447, the MPC7450, the MPC7451, the MPC7455, the MPC7457 processor, all of which are manufactured by Motorola Corporation of Schaumburg, Ill.; the Crusoe TM5800, the Crusoe TM5600, the Crusoe TM5500, the Crusoe TM5400, the Efficeon TM8600, the Efficeon TM8300, or the Efficeon TM8620 processor, manufactured by Transmeta Corporation of Santa Clara, Calif.; the RS/6000 processor, the RS64, the RS 64 II, the P2SC, the POWER3, the RS64 III, the POWER3-II, the RS 64 IV, the POWER4, the POWER4+, the POWER5, or the POWER6 processor, all of which are manufactured by International Business Machines of White Plains, N.Y.; or the AMD Opteron, the AMD Athlon 64 FX, the AMD Athlon, or the AMD Duron processor, manufactured by Advanced Micro Devices of Sunnyvale, Calif.
Main memory unit 204 may be one or more memory chips capable of storing data and allowing any storage location to be directly accessed by the microprocessor 202, such as Static random access memory (SRAM), Burst SRAM or SynchBurst SRAM (BSRAM), Dynamic random access memory (DRAM), Fast Page Mode DRAM (FPM DRAM), Enhanced DRAM (EDRAM), Extended Data Output RAM (EDO RAM), Extended Data Output DRAM (EDO DRAM), Burst Extended Data Output DRAM (BEDO DRAM), Enhanced DRAM (EDRAM), synchronous DRAM (SDRAM), JEDEC SRAM, PC100 SDRAM, Double Data Rate SDRAM (DDR SDRAM), Enhanced SDRAM (ESDRAM), SyncLink DRAM (SLDRAM), Direct Rambus DRAM (DRDRAM), or Ferroelectric RAM (FRAM).
In the embodiment shown in
In the embodiment shown in
A wide variety of I/O devices 230 may be present in the computer 200. Input devices include keyboards, mice, trackpads, trackballs, microphones, and drawing tablets. Output devices include video displays, speakers, inkjet printers, laser printers, and dye-sublimation printers.
In further embodiments, an I/O device 230 may be a bridge between the system bus 120 and an external communication bus, such as a USB bus, an Apple Desktop Bus, an RS-232 serial connection, a SCSI bus, a FireWire bus, a FireWire 800 bus, an Ethernet bus, an AppleTalk bus, a Gigabit Ethernet bus, an Asynchronous Transfer Mode bus, a HIPPI bus, a Super HIPPI bus, a SerialPlus bus, a SCI/LAMP bus, a FibreChannel bus, or a Serial Attached small computer system interface bus.
General-purpose desktop computers of the sort depicted in
A computer 200 may also be any personal computer (e.g., 286-based, 386-based, 486-based, Pentium-based, Pentium II-based, Pentium III-based, Pentium 4-based, Pentium M-based, or Macintosh computer), Windows-based terminal, Network Computer, wireless device, information appliance, RISC Power PC, X-device, workstation, mini computer, main frame computer, personal digital assistant, or other computing device. Windows-oriented platforms supported by the computer 200 can include, without limitation, WINDOWS 3.x, WINDOWS 95, WINDOWS 98, WINDOWS NT 3.51, WINDOWS NT 4.0, WINDOWS 2000, WINDOWS CE, WINDOWS ME, WINDOWS XP, WINDOWS Longhorn, MAC/OS, Java, and UNIX. The computer 200 can include a visual display device (e.g., a computer monitor), a data entry device (e.g., a keyboard), persistent or volatile storage (e.g., computer memory) for storing downloaded application programs, a processor, and a mouse. Execution of a communication program allows the system 200 to participate in a distributed computer system model.
For embodiments in which the client computing device 110 is a mobile device, the device may be aJAVA-enabled cellular telephone, such as the i55sr, i58sr, i85s, or the i88s, all of which are manufactured by Motorola Corp. of Schaumburg, Ill.; the 6035 or the 7135, manufactured by Kyocera of Kyoto, Japan; or the i300 or i330, manufactured by Samsung Electronics Co., Ltd., of Seoul, Korea. A typical mobile device may comprise many of the elements described in
In other embodiments in which the client computing device 110 is mobile, it may be a personal digital assistant (PDA) operating under control of the PalmOS operating system, such as the Tungsten W, the VII, the VIIx, the i705, all of which are manufactured by palmOne, Inc. of Milpitas, Calif. In further embodiments, the computer 100 may be a personal digital assistant (PDA) operating under control of the PocketPC operating system, such as the iPAQ 4155, iPAQ 5555, iPAQ 1945, iPAQ 2215, and iPAQ 4255, all of which manufactured by Hewlett-Packard Corporation of Palo Alto, Calif.; the ViewSonic V36, manufactured by ViewSonic of Walnut, Calif.; or the Toshiba PocketPC e405, manufactured by Toshiba America, Inc. of New York, N.Y. In still other embodiments, the computer 100 is a combination PDA/telephone device such as the Treo 180, Treo 270, Treo 600, or the Treo 650, all of which are manufactured by palmOne, Inc. of Milpitas, Calif. In still further embodiments, the client computing device 110 is a cellular telephone that operates under control of the PocketPC operating system, such as the MPx200, manufactured by Motorola Corp. A typical combination PDA/telephone device may comprise many of the elements described in
Referring back to
Client computing devices 110 communicate with the gateway computing device 120 over a first network 150. In some embodiments, client computing devices 110 communicate over a network connection. The network can be a local area network (LAN), a metropolitan area network (MAN), or a wide area network (WAN) such as the Internet. The client computing devices 110 and the gateway computing device 120 may connect to a network through a variety of connections including standard telephone lines, LAN or WAN links (e.g., T1, T3, 56 kb, X.25), broadband connections (ISDN, Frame Relay, ATM), and wireless connections. Connections between the client computing devices 110 and the gateway computing device 120 may use a variety of data-link layer communication protocols (e.g., TCP/IP, IPX, SPX, NetBIOS, NetBEUI, SMB, Ethernet, ARCNET, Fiber Distributed Data Interface (FDDI), RS232, IEEE 802.11, IEEE 802.11 a, IEE 802.11 b, IEEE 802.11 g and direct asynchronous connections).
Still referring to
Referring now to
Still referring to
The gateway computing device 120 authenticates the user of the client computing device 110 (step 304). In some embodiments, the gateway computing device 120 prompts the user for authentication credentials using HTTP 401 Basic, Digest, or NTLM. Once credentials are received from the user, authentication may occur using LDAP, RADIUS, two-factor authentication techniques, authentication certificates, or biometric techniques. For example, the user may authenticate using token-based, two-factor authentication techniques such SecurID tokens, manufactured and sold by RSA Security Inc. of Bedford, Mass. or SafeWord tokens manufactured by Secure Computing of San Jose, Calif.
The gateway computing device 120 transmits a portal page to the client computing device 110 for display to the user (step 306). In some embodiments, the portal page requests additional information from the user, such as the user'"'"'s location, the capabilities of the client computing device 110, or whether the user owns the client computing device 110. In other embodiments, the portal page allows the user to specify particular network resources to which the user wants access. In still other embodiments, the portal page provides a button for the user to select to establish the connection.
The client computing device 110 transmits a request to connect to the gateway device 120 (step 308). In one embodiment, the client computing device 110 automatically transmits the request upon selection by a user of a network resource to access. In other embodiments, the client computing device 110 automatically transmits the request after the user submits information requested by the portal page.
The gateway computing device 120 transmits remote process to the client computing device 110 (step 310). In one embodiment, the remote process comprises a client application. The client application may comprise functionality for receiving a packet, applying a policy to the packet, and determining to transmit the packet to the gateway computing device 110.
In some embodiments, the remote process comprises a driver. The driver may comprise functionality for capturing a packet and determining to forward the packet to the client application, responsive to a filter table received from the client application. In one of these embodiments, the remote process comprises a driver constructed in compliance with the Network Driver Interface Specification (NDIS). In another of these embodiments, the driver comprises a mini-filter. In still another of these embodiments, the driver executes in kernel space on the client computing device 110. In yet another of these embodiments, the driver executes in application space on the client computing device 110. In still another of these embodiments, the driver is transmitted to the client computing device 120 separately from the remote process. In yet another of these embodiments, the gateway computing device 120 determines that the client computing device 110 already comprises an NDIS driver and that transmission of an NDIS driver to the client computing device 110 is not required.
The client computing device 110 launches the remote process (step 312). The client computing device 110 may launch the remote process automatically, at the time of installation. In other embodiments, the client computing device 110 may launch the remote process automatically, at a time when the user of the client computing device 110 requests access to a target computing device 140. In still other embodiments, a user of the client computing device 110 may launch the remote process automatically prior to requesting access to a target computing device 140.
Once launched, the remote process establishes a secure communication tunnel to the gateway computing device 120 (step 314). In embodiments where the remote process is a client application executing in application space, the client application establishes the secure communication tunnel to the gateway computing device 120. In one embodiment, the secure communication tunnel is established over an HTTPS port, such as port 442, or any other configured port on the gateway computing device 120, using TLS or SSL encryption. In another embodiment, the secure communications tunnel may be established using industry standard connection establishment techniques, such as HTTPS, Proxy HTTPS, and SOCKS. Use of these techniques may enable use of the present invention in embodiments where a firewall 130 is implemented. In some embodiments, a connection is made via an intermediate proxy. In one of these embodiments, the client computing device 110 obtains from the user of the client computing device 110 credentials requested by the intermediate proxy.
In some embodiments, the secure communication tunnel is encrypted using industry standard technology, such as SSL and TLS. Upon establishment of the secure communication tunnel, session payload is encrypted and captured IP packets may be securely transmitted to the gateway computing device 120. Packets and packet header information transmitted across the secure communication tunnel are encrypted. The secure communication tunnel may support 196-bit encryption as well as higher or lower bit values. In one embodiment, the secure communication tunnel supports all OpenSSL ciphers, including CAST, CAST5, DES, Triple-DES, IDEA, RC2, RC4, and RC5.
In some embodiments, the gateway computing device 120 transmits configuration information to the remote process. The configuration information may provide the remote process with descriptive information regarding a network being secured, such as the network 180. The configuration information may also include IP addresses required to enable visibility of the client computing device 110 on one or more networks. The configuration information may further include information needed to validate that the remote process successfully established the communication tunnel. This information may enable the remote process to test and validate client-side certificates, directly or by configuring the client computing device 110 to do so. The information may also comprise authentication information enabling the remote process to validate that the tunnel is established.
In some embodiments, upon the launch of the remote process, the remote process captures all network traffic destined for a private, secured network, such as the network 180. In one of these embodiments, the remote process redirects captured network traffic over the established secure communications tunnel to the gateway computing device 120. In an embodiment where all network traffic is captured and transmitted over a secure link, the present invention provides functionality equivalent to that provided by an IPSec solution.
In one of these embodiments, a TCP connection is initiated by an application executing on the client computing device 110, for transmission of IP packets to a target computing device 140. The remote process captures the IP packets generated by the application. The remote process may send a TCP acknowledgement packet to the application and terminate the TCP connection initiated by the application. The remote process then creates a second TCP connection to the gateway computing device 120 and transmits the captured IP packets to the gateway computing device 120 across the secure communications tunnel. In some embodiments, the remote process may store a captured IP packet in a buffer. In these embodiments, the remote process may transmit the stored IP packet to the gateway computing device 120. Storing the captured IP packets in a buffer enables preservation of the packets in the event of a disruption in the secure communications tunnel between the gateway computing device 120 and the client computing device 110.
In another of these embodiments, upon receipt of the captured IP packets, the gateway computing device 120 may create a third TCP connection between the gateway computing device 120 to the target computing device 140. The gateway computing device 120 may maintain a port-mapped Network Address Translation (NAT) table, enabling the gateway computing device 120 to transmit response packets from the target computing device 140 to the port monitored by the application that originally generated the IP packet on the client computing device 110.
Because the client computing device 110 communicates only with a public network address of the gateway computing device 120, the client computing device 110 is unaware of the network address of the target computing device 140, increasing security to the network on which the target computing device 140 resides. Similarly, since the gateway computing device 120 originates the TCP connection to the target computing device 140, the target computing device 140 does not receive the address information of the client computing device 110, protecting the client computing device and the network on which it resides. Additionally, since the gateway computing device 120 receives the IP packets, the gateway computing device 120 may make a determination responsive to a policy or security check as to whether or not to transmit the IP packets to the target computing device 140, further increasing protection to the network on which the target computing device 140 resides.
In some embodiments, functionality is required that enables the gateway computing device 120 to create a connection to the client computing device 110. The functionality may be required to enable the client computing device 110 to use protocols such as those required by real-time voice applications. In one of these embodiments, the remote process associates the client computing device 110 with a network address on the network 180. In another of these embodiments, a remote process execution on the gateway computing device 120 associates the client computing device 110 with the network address on the network 180. In other embodiments, a remote process execution on the gateway computing device 120 maintains a reverse NAT table.
In one embodiment, the present invention provides a method for securing a packet transmitted from a private, secured network 180 behind a gateway 120 to a client computing device 110 on an external network 150. The invention enables separation of the client computing device from the private network by providing network address translation (NAT) functionality on the gateway. A VPN gateway that uses NAT provides masquerading of IP addresses of a client computing device to shield the private network from direct layer-2 access by the client computing device.
Referring now to
A filtering table is received (step 402). In some embodiments, the filtering table includes information about a private network. In other embodiments, a filter on a client computing device receives the filtering table. In one of these embodiments, the filter receives the filtering table from a client application on the client computing device. In another of these embodiments, the filter receives configuration settings from the client application and stores the configuration settings in a filtering table.
An outbound packet is intercepted (step 404). In some embodiments, a filter on a client computing device intercepts the outbound packet. In one of these embodiments, the filter intercepts all outbound packets. In another of these embodiments, the filter inspects an intercepted outbound packet. In still another of these embodiments, the filter inspects an intercepted outbound packet prior to the outbound packet being routed. In another embodiment, the filter inspects an intercepted outbound packet prior to the outbound packet reaching the data link layer in which the outbound packet would be prepared for routing.
The outbound packet is transmitted to a client application responsive to the filtering table (step 406). In some embodiments, a filter transmits the outbound packet to the client application, responsive to the filtering table. In one of these embodiments, when the filter inspects an outbound packet, the filter compares data in the outbound packet to data in the filtering table. In one embodiment, the filtering table indicates that an outbound packet should be transmitted to the client application if the outbound packet is addressed to a particular destination, such as a private network behind a gateway computing device. In another embodiment, the filtering table indicates that an outbound packet should be transmitted to the client application if the outbound packet is a particular type of packet, for example, a packet containing real-time data, such as voice or video data. In still another embodiment, the filtering table indicates that a packet should be transmitted to the client application if transmission of the outbound packet requires a particular protocol type. In one embodiment, the filter transmits the outbound packet to the client application responsive to a routing table. In another embodiment, the filter transmits the outbound packet to a port monitored by the client application. In some embodiments, the filter rewrites a destination address and a destination port of the packet. In one of these embodiments, the filter transmits the rewritten packet back up the network stack of the operating system for delivery to the client application. In another of these embodiments, the filter transmits information about the outbound packet to the client application prior to rewriting the destination address and destination port. The transmitted information may include the original destination address and destination port.
The client application determines to transmit the outbound packet to a gateway computing device, responsive to an application of a policy to the outbound packet (step 408). In one embodiment, the filtering table indicates to the filter that the outbound packet should be transmitted to the client application. In some embodiments, upon receipt of the outbound packet from the filter, the client application applies a policy to the outbound packet. In one of these embodiments, the client application determines whether to transmit the outbound packet to the gateway computing device responsive to the application of the policy. In one embodiment, the determination to transmit the outbound packet to the gateway computing device is based upon the type of application that generated the outbound packet. In another embodiment, the determination to transmit the outbound packet to the gateway computing device is based upon the type of data within the outbound packet. In still another embodiment, the determination to transmit the outbound packet to the gateway computing device is based upon a characteristic of a destination network to which the outbound packet is addressed.
In one embodiment, the client application authenticates the client computing device to a gateway computing device prior to transmission of the outbound packet. In another embodiment, the client application encrypts the outbound packet prior to transmitting the outbound packet to the gateway computing device. In still another embodiment, the client application establishes a secure sockets layer (SSL) tunnel to the gateway computing device. In yet another embodiment, the client application transmits an encrypted outbound packet to the gateway computing device via an SSL tunnel to the gateway computing device.
Referring now to
The kernel 534 may include a filter 522 and an outbound packet 528. The filter 522 may include a packet capture module 565. The packet capture module 565 may comply with the Network Driver Interface Specification (NDIS). The packet capture module 565 may operate in kernel mode. The packet capture module 565 may intercept outbound packet traffic. The packet capture module 565 may forward the packets to a frame monitor in an application 526.
In some embodiments, the filter 522 communicates with the client application 526 via asynchronous I/O control messages. In one of these embodiments, the packet capture module 565 may forward packets addressed to a private network behind a gateway computing device 540 via asynchronous I/O control messages. In other embodiments, the filter 522 communicates with the client application 526 running in the application space 534 via UDP packets. In one embodiment, the filter 522 receives configuration settings from the client application 526 driver via asynchronous I/O control messages. The configuration settings may include information regarding which networks, protocols, or types of packets to filter. In one embodiment, the filter 522 stores the configuration settings in a filtering table. In another embodiment, the filter 522 receives a filtering table including the configuration settings.
In one embodiment, the filter 522 intercepts all outbound packets 528 for inspection. If the packet 528 satisfies a condition listed in the filtering table, the filter 522 may transmit the packet 528 to the client application 526 and not to the original destination of the packet 528. The filter 522 may use an asynchronous I/O control message to forward the packet 528 to the client application 526. The filter 522 may transmit the packet 528 to the client application 526 responsive to a routing table.
The kernel 534 in the client computing device 520 may include an NDIS interface. In some embodiments, the NDIS interface includes a plurality of intermediate filters. In one embodiment, a packet 528 passes through the NDIS interface and may be inspected by the plurality of intermediate filters. The filter 522 may be provided as an NDIS driver. The filter 522 may also be a process executing on the kernel 534.
The application space 532 includes a client application 526. In one embodiment, the application space 532 may include an application 538, which may generate the packet 528. In some embodiments, an application 538 executing in application space 532 generates a packet 528 for transmission by the client computing device 520. The application 538 can be any type and/or form of application such as any type and/or form of web browser, web-based client, client-server application, a thin-client computing client, an ActiveX control, or a Java applet, or any other type and/or form of executable instructions capable of executing on client computing device 110 or communicating via a network. The application 538 can use any type of protocol and it can be, for example, an HTTP client, an FTP client, an Oscar client, or a Telnet client. In some embodiments, the application 538 uses a remote display or presentation level protocol. In one embodiment, the application 538 is an ICA client, developed by Citrix Systems, Inc. of Fort Lauderdale, Fla. In other embodiments, the application 538 includes a Remote Desktop (RDP) client, developed by Microsoft Corporation of Redmond, Wash. In other embodiments, the application 538 comprises any type of software related to Voice over IP (VOIP) communications, such as a soft IP telephone. In further embodiments, the application 538 comprises any application related to real-time data communications, such as applications for streaming video and/or audio.
The client application 526 may reside in application space 532 on a client computing device 520. In some embodiments, the client application 526 provides functionality for receiving packets from the filter 522. In other embodiments, the client application 526 provides functionality for applying a policy to a received packet 528. In still other embodiments, the client application 526 provides functionality for managing an SSL tunnel to the gateway computing device 540. In yet other embodiments, the client application 526 provides functionality for encrypting and transmitting a packet 528 to the gateway computing device 540.
The client application 526 may include frame monitor 560. The frame monitor 560 may include policies and logic for applying a policy to a received packet. The frame monitor 560 may apply a policy to a received packet 528. The client application 526 may transmit a packet to a gateway computing device 540 responsive to a policy-based determination made by the frame monitor 560.
In some embodiments, the frame monitor 560 may apply a policy to determine a state of the client computing device 520 at the time of transmission of the packet. In some embodiments, the policy applied may require satisfaction of a condition. In one of these embodiments, the policy may require that the client computing device 520 execute a particular operating system to satisfy the condition. In some embodiments, a policy may require that the client computing device 520 execute a particular operating system patch to satisfy the condition. In still other embodiments, a policy may require that the client computing device 520 provide a MAC address for each installed network card to satisfy the condition. In some embodiments, a policy may require that the client computing device 520 indicate membership in a particular Active Directory to satisfy the condition. In another embodiment, a policy may require that the client computing device 520 execute a virus scanner to satisfy the condition. In other embodiments, a policy may require that the client computing device 520 execute a personal firewall to satisfy the condition. In some embodiments, a policy may require that the client computing device 520 comprise a particular device type to satisfy the condition. In other embodiments, a policy may require that the client computing device 520 establish a particular type of network connection to satisfy the condition.
In other embodiments, the frame monitor 560 may identify an application 538 that generated the packet 528. In one of these embodiments, the frame monitor 560 may make a policy-based determination to transmit the packet 528 to the gateway computing device 540 responsive to the identified application 538. In another of these embodiments, the frame monitor 560 may perform a checksum on the packet to verify that the identified application actually generated the packet 528.
In one embodiment, the gateway computing device 540 is a remote access server. The gateway computing device 540 may decrypt packets received from the client computing device 520. The gateway computing device 540 may protect a private network. In some embodiments, the gateway computing device 540 associates a client computing device 520 with a private IP address. In one of these embodiments, when the gateway computing device 540 receives a packet from the client computing device 520, the gateway computing device 540 transforms the IP address of the packet to the IP address associated with the client computing device 520. The gateway computing device 540 may apply access control policies to a received packet prior to routing the packet to a final destination. The gateway computing device 540 is described in further detail below, in
Once a frame enters the gateway computing device 540 via an SSL tunnel, the packet and its payload are dispatched via callbacks into a handlers executing in user mode, which provide functionality for SSL decryption. In one embodiment, OpenSSL is used. In another embodiment, a hardware accelerator is used. Once the packet is decrypted, it is injected into the HTTP stack where headers are assembled and passed on to the remote access blade.
In a remote access blade, a packet is classified by the type of data contained within the packet. In one embodiment, the packet contains an HTTP header requesting login and registration. In another embodiment, the packet seeks TCP/UDP/RAW/OTHER connection establishment. In still another embodiment, the packet contains connection-specific data. In yet another embodiment, the packet contains a special feature request such as collaboration with other users, fetching of user directory and presence or requesting telephony functionality such as conferencing and web cast. The remote access module dispatches the packet appropriately to the corresponding sub handler. For example, the client computing device may request that a connection be set up to a specific machine on the private network behind the gateway computing device. The remote access module may consult with the access control module and if a positive response is returned, the remote access module may grant the request. In some embodiments, the remote access module may grant the request by injecting subsequent frames on the private network using a frame forwarding module utilizing NAT/PAT to correlate incoming frames to corresponding SSL tunnels to the client computing device.
Referring now to
The client application 526 in application space 532 receives a packet. In one embodiment, the client application 526 receives the packet from the filter 522. In some embodiments, an interface 602 on the client application 526 receives the packet. In one of these embodiments, the interface 602 is a full-duplex direct I/O-based IRP-handling interface with an I/O Control Windows Management Interface (WMI).
The client application 526 inspects the packet. In one embodiment, a policy and host security engine API 620 on the client application 526 inspects the packet. In one embodiment, the policy and host security engine API 620 applies a policy to the packet. The policy may include requirements for hosts and processes accessing a corporate network.
In some embodiments, the policy and host security engine API 620 identifies an application 538 that generated the packet. An application 538 may be continuously check-summed to ensure that malicious applications with the same name did not generate the packet. If the policy and host security engine API 620 determines that the current condition and history of the machine satisfies the applied policies, the client application 526 may transmit the packet to the gateway computing device 540.
In some embodiments, a packet/frame forwarding and SSL tunnel management API 610 on the client application 326 transmits the packet to a gateway computing device 540. The API 610 may transmit the packet across an SSL tunnel to the gateway computing device 540.
In one embodiment, the client application 526 establishes an asynchronous maintenance tunnel to communicate with a policy module on the gateway computing device 540. The client application 526 may use the tunnel to communicate with the gateway computing device 540 regarding client events (such as status of firewalls and anti-virus programs). The client application 526 may also use the tunnel to receive new policies from the gateway computing device.
In some embodiments, the client application 526 includes an Application Hook and TDI analysis API 630. The API 530 may use Windows menu hooking and tray pop hooking to inject GUI messages to an end user of the client computing device 520. In one embodiment, the GUI messages alert the end user of various system events, system administrator announcements and gather user credentials.
In other embodiments, the client application 526 includes an audio/video and messaging integration API 640. The API 640 may use audio, video and IM messaging hooks to interconnect with existing user applications (such as MSN messenger or an installed softphone).
Referring now to
Packets entering the protocol edge driver 710 on the receive path are arriving from other client computing devices that are using the client computing device 520 as a gateway computing device.
Packets entering the miniport edge 720 are arriving from applications 538 running on the client computing device 520 that are transmitting outbound packets to a private network behind a gateway computing device 540. The I/O filter 712 applies filtering logic on each packet and compares it against its filter table. If the I/O filter 712 filters the packet, the I/O filter 712 passes the packet to the IOCTL dispatch engine 714 with a request to forward the packet to the client application 526. Otherwise, the I/O filter 712 sends the packet to its original direction, either up or down the network stack as appropriate.
In some embodiments, the client application 326 is not located on the client computing device 320. In one of these embodiments, a peripheral device contains the client application 326.
Referring now to
Referring now to
In one embodiment, the peripheral device stores a VPN application. Upon connection to a computer system, the peripheral device identifies itself to the client computing device as a mass storage device and executes the VPN application on the client computing device. In some embodiments, the VPN application authenticates the peripheral device to a VPN gateway computing device. In one of these embodiments, after authentication, the VPN application retrieves routing table changes from the VPN gateway computing device. In another of these embodiments, the VPN application creates a file on the peripheral device storing retrieved routing table changes. In still another of these embodiments, the VPN application retrieves data for use by the peripheral device. The data may include a destination address of the VPN gateway computing device, an IP address for the client computing device, and at least one port address for the VPN application to monitor.
In some embodiments, upon creation of a file on the peripheral device, the peripheral device identifies itself to the client computing device as a network device. In one of these embodiments, the peripheral device transfers to the client computing device a plurality of routing table changes stored in the created file. In another of these embodiments, the peripheral device instructs a computer through the transmitted routing table changes to transmit an outbound packet to the peripheral device. In still another of these embodiments, the change to the routing table indicates to the client computing device that all outbound packets not destined for the VPN application should be transmitted to the peripheral device. In some embodiments, an outbound packet is transmitted by the client computing device to the peripheral device, responsive to the change to the routing table.
The peripheral device receives an outbound packet (step 804). In one embodiment, the peripheral device receives the outbound packet responsive to the change made to the routing table. In one embodiment, the peripheral device receives the outbound packet by interacting with the peripheral side of R-NDIS, accepts the outbound packet, and indicates to R-NDIS that the packet has been delivered.
In one embodiment, when the peripheral device receives the outbound packet, the outbound packet includes an IP header storing a set of address information. In some embodiments, the peripheral device determines that the set of address information is unique. In one of these embodiments, when the peripheral device receives a unique set of address information, the peripheral device maps the unique set of address information to a unique source port. The peripheral device may generate a random number to create the unique source port. The peripheral device may store, in memory, the mapping from the unique set of address information to the unique source port.
In some embodiments, the peripheral device generates a second packet. In one of these embodiments, the peripheral device creates a data structure inside a control frame in a data section of the second packet. In another of these embodiments, the data structure includes the unique source port. In still another of these embodiments, the data structure stores an IP address of the client computing device. In yet another of these embodiments, the data structure stores one of a plurality of well-known destination ports monitored by the VPN application. In some embodiments, the data structure stores well-known destination ports and destination address retrieved from the VPN Gateway computing device.
The peripheral device transmits information about the outbound packet to a client application (step 806). In some embodiments, the peripheral device transmits the generated second packet to a VPN application. In one of these embodiments, the generated second packet includes the IP address of the client computing device and a destination port monitored by the VPN application. Including this information in the generated second packet enables the peripheral device to transmit the generated second packet and have the generated second packet delivered to the VPN application on a port monitored by the VPN application. In another of these embodiments, the generated second packet includes the unique source port generated by the peripheral device. In still another of these embodiments, the peripheral device indicates to the client computing device that the generated second packet is a new received packet and transmits the second packet to the client computing device. The client computing device receives the second packet and delivers it to the VPN application.
The peripheral device replaces address information on the outbound packet with a destination address and a destination port associated with the client application (step 808). Rewriting the address information enables the peripheral device to forward the outbound packet to a VPN application. In one embodiment, the peripheral device replaces the destination address on the outbound packet with the IP address of the client computing device on which the VPN application executes. In another embodiment, the peripheral device replaces the destination port on the outbound packet with a destination port monitored by the VPN application. In still another embodiment, the peripheral device replaces the source port on the outbound packet with the generated unique source port described above.
The peripheral device transmits the modified outbound packet to the VPN application (step 810). In some embodiments, the peripheral device indicates to the client computing device that the modified outbound packet is a newly received packet. In one of these embodiments, the client computing device receives the modified outbound packet, identifies the destination port as a port monitored by the VPN application, and transmits the modified outbound packet to the VPN application.
The peripheral device generates the second packet to provide the VPN application with the unique source port. Once the VPN application receives the unique source port, the VPN application may use the unique source port to identify an original destination address associated with other packets. In one embodiment, when the VPN application receives a new, modified outbound packet containing a source port, the VPN application uses the unique source port to retrieve the original destination address of the outbound packet from a mapping stored on the peripheral device.
In some embodiments, the VPN application transmits the outbound packet to the VPN gateway computing device. In one of these embodiments, the VPN application encrypts the modified outbound packet. In another of these embodiments, the VPN application transmits the outbound packet to the VPN gateway computing device, responsive to the information received about the outbound packet from the peripheral device. In still another of these embodiments, the VPN application employs a received unique source port to retrieve from the peripheral device a destination port and destination address associated with the unmodified outbound packet. The VPN application may then transmit the retrieved address information with the modified outbound packet to the VPN gateway computing device. In some embodiments, the VPN application makes a connection to the original destination address and then transmits the packet to the destination.
In one embodiment, the VPN application establishes an SSL tunnel to the VPN gateway computing device. The VPN application may transmit the outbound packet to the VPN gateway computing device across the SSL tunnel. In this embodiment, the VPN application may establish the SSL tunnel responsive to a destination address associated with the outbound packet received from the peripheral device.
In some embodiments, the firmware on the device enables several types of functionality. In one of these embodiments, the firmware reports the type of device as a composite USB mass storage and network device combination device. In another of these embodiments, the firmware stores and launches applications. These applications may include, without limitation, encryption and tunnel management logic, end user applications (such as email or soft phones), end user identity (such as certificates or tokens), autorun.inf files so applications are automatically launched, and end user application data (such as email pst files). In yet another of these embodiments, the firmware implements an R-NDIS loop back such that outbound IP packets that are sent to the peripheral device are identified to the client computing device as inbound IP packets and sent back to the host operating system to a different port. By marking an outbound packet as an inbound packet, the peripheral device can send the packet to the VPN application and prevent the packet from leaving the computer unencrypted. Forcing a packet to the VPN application, which sends the packet to a VPN gateway computing device for transmission to the original destination of the packet, also ensures that the packet is transmitted to the original destination in a secure manner.
In other embodiments, the firmware on the peripheral device implements token software such that unique tokens are generated on a timely basis in synchronization with the authenticating VPN gateway computing device. The peripheral device may establish an authentication tunnel with the VPN gateway computing device. The VPN gateway computing device can read tokens from a file stored in mass storage on the peripheral device. The host VPN tunnel logic may fetch the token and sent the token to the VPN gateway computing device as an authentication factor.
Referring now to
The client computing device 920 comprises a routing table 930, a packet 928, a physical NIC 936, and a remote-NDIS driver 938. In some embodiments, the client computing device 920 further comprises a device driver that enables communication between the client computing device 920 and the device 900. In one of these embodiments, the device driver may comprise a Remote-NDIS driver for Universal Serial Bus (USB) device.
In one embodiment, the device 900 connects to the physical NIC 936 on the client computing device 920. The physical NIC 936 may be a USB card. In other embodiments, the physical NIC 936 is an external bus supporting high data transfer rates and complying with the IEEE 1394 standard, such as a Firewire card. In other embodiments, the physical NIC 936 is a small computer system interface (SCSI) card.
Still referring to
In one embodiment of the present invention, the device 900, which may be a USB peripheral device, operates as a composite USB device declaring itself as a device capable of mass storage. A reporting element 916, shown in shadow in
In an embodiment where the device 900 has a composite nature, the device 900 may initially appear as a mass storage capable of removable media and use autostart.inf to launch a port forwarder application 912 on a VPN application 910. The port forwarder application 912 may show a login dialog to a user of the client computing device 920 and collect user credentials. In one embodiment, the port forward application 912 may establish an SSL tunnel with the VPN gateway computing device 940 and present the VPN gateway computing device 940 with authentication credentials, certificates, or tokens, each of which may be read from the mass storage section on the device 900.
For packets that are destined for a network on which the VPN gateway computing device 940 resides, the device 900 generates a unique source port number and maps the unique source port number to a destination address on the packet 928. The device 900 may then rewrite the packet 928, addressing the packet 928 to the destination address of the client computing device 920 and to a port on the client computing device 920 monitored by the port forwarder application 912, and including the unique source port number in the rewritten packet 928. The device 900 may transmit the rewritten packet 928 to the client computing device 920. The client computing device 920 transmits the rewritten packet 928 to the port monitored by the VPN application 910.
The device 900 may store applications, such as electronic mail applications, in the storage element 914, for execution on the client computing device 920. In some embodiments, the present invention enables sandboxing. In one of these embodiments, the device 900 hosts application data if the device 900 determines that mass storage on the client computing device 920 is not a safe asset for the storage of data generated and used during a VPN session. In another of these embodiments, the invention provides a mechanism enabling plugging a device 900 into any client computing device 920 and automatically having session data readily available. Additionally, storage of an application and execution data on a device 900 may prevent a user from leaving sensitive data on insecure client computing devices 920.
In other embodiments, if the device 900 determines that the client computing device 920 is insecure and should not receive access to the network on which the VPN gateway computing device 940 resides, the device 900 may serve as a platform for launching a remote frame buffer (or thin client) mode of operation to gain remote access. In one of these embodiments, the session state for the remote access can be saved on the device 900 and resumed from other locations. In still other embodiments, the device 900 may also serve as an audio device and provide soft phone functionality to the client computing device, where the telephony logic runs in the port forwarder application and the device simply serves as an I/O mechanism.
The routing element 902 implements a change to the routing table 930 on the client computing device 920. In one embodiment, the routing element 902 changes the routing table so that the client computing device 920 reroutes all outbound packets to the device 900. In another embodiment, the routing element 902 implements the change by transmitting a retrieved change to the client computing device after a reporting element 916, shown in shadow in
In some embodiments, the routing element 902 retrieves a plurality of changes to make to the routing table 930. In one of these embodiments, the routing element 902 may retrieve the changes from a VPN gateway computing device 940. In another of these embodiments, the VPN application 910 may retrieve the changes from the VPN gateway computing device 940. In still another of these embodiments, the VPN gateway computing device 940 may require authentication of the device 900 prior to the retrieval of routing table changes.
In some embodiments, the routing element 902 retrieves the change from the storage element 914. In one of these embodiments, the routing element 902 retrieves the change after the VPN application 910 has stored the change on the storage element 914.
In an embodiment where the device 900 includes a reporting element 916, the reporting element 916 may communicate with the client computing device 920 to identify the device 900 to the client computing device 920. In some embodiments, the reporting element 916 communicates with an R-NDIS driver 938. In one embodiment, the reporting element 916 identifies the device 900 as a mass storage device. The reporting element 916 may make this identification when the device 900 is initially connected to the client computing device.
In some embodiments, the reporting element 916 identifies the device 900 as a network device. In one of these embodiments, the reporting element 916 makes the identification after changes to the routing table 930 are retrieved and stored in the storage element 914. In another of these embodiments, the routing element 902 transfers to the client computing device 920 the retrieved routing table changes after the reporting element 916 identifies the device 900 to the client computing device 920 as a network device. In still another of these embodiments, the client computing device 920 implements the routing table changes as if the device 900 were a conventional network device.
The receiver 904 receives a packet from the client computing device 920. In one embodiment, the receiver 904 receives the outbound packet responsive to the change made to the routing table 930 by the routing element 902.
The transmitter 906, in communication with the receiver 904 and the packet rewriter 908, transmits information about the outbound packet to the VPN application 910. In one embodiment, the information comprises a unique source port generated by the packet rewriter 908 and associated with the outbound packet 920. In another embodiment, the information comprises a mapping between the unique source port of the outbound packet and the destination address of the outbound packet. In still another embodiment, the transmitter 906 transmits a rewritten outbound packet to the VPN application 910. In yet another embodiment, the transmitter 906 transmits a second packet generated by the peripheral device to the client computing device 920 for delivery to a port monitored by the VPN application 910.
The packet rewriter 908, in communication with the receiver 904 and the transmitter 906, rewrites address information on the outbound packet 928. In some embodiments, the packet rewriter 908 rewrites a destination address on the outbound packet 928 with a destination address and a destination port associated with the VPN application 910. In one embodiment, rewriting the destination address and the destination port enables transmission of the outbound packet to the VPN application 910. In some embodiments, the packet rewriter 908 generates a mapping table associating information in the outbound packet 928 with information in the modified outbound packet 928. In one embodiment, the mapping table associates a destination address and a destination port in the outbound packet 928 with the unique source port stored in the modified outbound packet 928. In another of these embodiments, the mapping table may contain information including an original source address, an original source port, an original destination address, an original destination port, and a unique mapping key used as the source port on rewritten packets.
In one embodiment, the packet rewriter 908, in communication with the receiver 904 and the transmitter 906, generates a second packet as described above in
The packet rewriter 908 replaces a destination address and a destination port on the outbound packet 920 with a destination address and destination port associated with the VPN application 910. In one embodiment, the packet rewriter 908 rewrites the destination address on the outbound packet 928 with an IP address of the client computing device 920 on which the VPN application 910 executes. In another embodiment, the packet rewriter 908 rewrites the destination port on the outbound packet 928 with a port monitored by the VPN application 910.
In some embodiments, the device 900 includes a VPN application 910, which may include a port forwarder application 912. In one of these embodiments, the VPN application 910 is stored in the storage element 914. In another of these embodiments, although the VPN application 410 is stored on the device 900, it executes on the client computing device 920. In this embodiment, the VPN application 910 provides secure transmission of a packet 928 without requiring a software installation on the client computing device 920.
In some embodiments, the VPN application 910 receives the rewritten outbound packet 928 from the client computing device 920. In one of these embodiments, the VPN application 910 uses a unique source address on the rewritten outbound packet 928 to obtain an original destination address. The VPN application 910 may consult a mapping table stored on the storage element 914 on the device 900 to correlate the unique source address on the outbound packet 928 with the original destination address. In another of these embodiments, the VPN application 910 transmits the outbound packet 928 and the original destination address to the VPN gateway computing device 940. In still another of these embodiments, the VPN gateway computing device 940 receives the outbound packet 928 and the original destination address from the VPN application 910 and forwards the outbound packet 920 to the original destination address.
In some embodiments, a port forwarder application 912 provides the functionality of the VPN application 910. In one of these embodiments, the port forwarder application 912 retrieves the changes to the routing table 930 from the VPN gateway computing device 940. In another of these embodiments, the port forwarder application 912 authenticates the device 900 to the VPN gateway computing device 940. In still another of these embodiments, the port forwarder application 912 stores the changes to the routing table 930 in the storage element 914. In yet another of these embodiments, the port forwarder application 912 uses a unique source port to determine the original destination address of the outbound packet 928 and forward the original destination address and the rewritten outbound packet 928 to the VPN gateway computing device 940.
In one embodiment, the port forwarder application 912 obtains routing rules after presenting the VPN gateway computing device 940 with authentication credentials. The device 900 obtains routing rules from the port forwarder application 912. In some embodiments, the port forwarder application 912 stores the routing rules on the storage element 914.
Once the VPN tunnel is established and routing information for the network on which the VPN gateway computing device 940 resides is retrieved from the VPN gateway computing device 940, the VPN application 910 may create a file on the storage element 914 of the mass media device. In one embodiment, the file contains the retrieved routing information. Creation of the file may indicate to the reporting element 916 that it should identify the device 900 to the client computing device 920 as an R-NDIS-capable USB device connected to the client computing device 920. At this point, the operating system on the client computing device 920 will negotiate (via R-NDIS) a DHCP IP address from the device 900 and adjust its routing tables based on information given to it from the device 900, which may be derived from the file created by the port forwarder application 912.
The device 900 may communicate with the port forwarder application 912 on the VPN application 910 using IP packets encapsulated in R-NDIS. The device 900 may also send status packets to the port forwarder application 912. These status packets may convey information regarding state and data structures stored by the device 900.
In some embodiments, to communicate with the port forwarder application 912, the device 900 transmits packets to a control port and unique IP address associated with the port forwarder application 912. In one of these embodiments, the device 900 transmits a packet including a unique source port, indicating to the port forwarder application 912 that the device 900 has received a packet with a unique destination address and that the device 900 generated the unique source port to map to the unique destination address. In another of these embodiments, the device 900 transmits a packet indicating to the port forwarder application 912 that the device 900 has removed a mapping between a unique source port and a unique destination address. In still another of these embodiments, the device 900 transmits a packet requesting from the port forward application 912 instructions for responding to a request, such as an Address Resolution Protocol request.
In other embodiments, the port forwarder application 912 transmits a communications packet to the device 900. In one of these embodiments, the port forwarder application 912 transmits to the device 900 a packet indicating that the port forwarder application 912 has successfully opened a connection to the VPN gateway computing device 940. In another of these embodiments, the port forwarder application 912 transmits to the device 900 a packet indicating that the port forwarder application 912 failed to open a connection to the VPN gateway computing device 940.
In some embodiments, the port forwarder application 912 listens for packets on a plurality of ports, including the following: UDP Traffic Port, TCP Traffic Port, ICMP Traffic Port, and the Control Port. When the port forwarder application 912 receives a packet from a traffic port, such as the UDP traffic port or the TCP traffic port, the port forwarder application 912 uses the unique source port number in the rewritten packet 928 to identify an original destination address. The port forwarder application 912 may then transmit the rewritten packet 928 with the original destination to the VPN gateway computing device 940. In one embodiment, the port forwarder application 912 transmits the rewritten packet 928 with the original destination to the VPN gateway computing device 940 across an SSL VPN tunnel. In another embodiment, the port forwarder application 912 encrypts the rewritten packet 928 prior to transmission.
In some embodiments, the port forwarder application 912 receives a packet from the VPN gateway computing device 940. In one of these embodiments, the port forwarder application transmits the packet to a port monitored by the device 900. The device 900 may transmit the received packet to the client computing device 920 for routing the packet to a user application.
In some embodiments, a gateway computing device protects a private network by securing a packet transmitted from the private network to a client computing device remotely accessing the private network. To minimize security threats to the private network, the gateway computing device may intercept, inspect, and secure packet traffic sent from a protected system on the private network to the client computing device. In one of these embodiments, the gateway computing device is a virtual VPN gateway computing device using NAT to masquerade the IP addresses of the protected system and of the private network. A NAT-enabled VPN gateway computing device may monitor and secure packet traffic permitting more secure transmission of traffic to dynamic ports on a client computing device from the private network. The VPN gateway computing device may monitor network traffic for packet traffic originating from secured resources and addressed to the client computing device. When this VPN gateway computing device identifies this traffic, the VPN gateway computing device may secure the packets for transmission to the client computing device.
Referring now to
A private IP address is associated with a client computing device having a public IP address (step 1002). In some embodiments, each connecting client computing device is assigned a private IP address. In one of these embodiments, the private IP address is not available to the client computing device, for security purposes. Since the client computing device does not have the private IP address, if the client computing device is compromised, the private network is still protected. In another of these embodiments, the private IP address is an address in a private network behind the gateway computing device. In some embodiments, associating a private IP address with a client computing device minimizes security risks to the private network behind the gateway computing device.
A packet addressed to the private IP address of the client computing device is captured (step 1004). In one embodiment, an application generates a packet for transmission to the client computing device. In some embodiments, the application executes on the gateway computing device. In other embodiments, the application executes on a machine residing on a private network behind the gateway computing device. In one embodiment, before the packet is routed to the client computing device, the packet is captured.
In some embodiments, a packet on a client computing device is captured by an application executing in kernel mode, such as an NDIS driver or filter. In one of these embodiments, the application executing in kernel mode forwards the packet to an application executing in user mode. Capturing a packet at kernel level, but transmitting the packet from user mode provides the ability to apply higher-level access control on the traffic to ensure that the application that created the packet satisfies security policies of the network to which the packet is transmitted.
In some embodiments, a filter on the gateway computing device captures a layer-2 Ethernet MAC frame transmitted to the gateway computing device from a client computing device. In one of these embodiments, a client computing device client application executing in user mode does not modify a routing table on the client computing device. Instead, a filter driver on the client computing device captures traffic below the network level, at the media access control (MAC) layer. The client computing device filter driver may capture and transmit a layer-2 Ethernet MAC frame intact to the gateway computing device, over a secure SSL VPN tunnel. In these embodiments, the filter on the gateway computing device provides functionality for capturing the Ethernet MAC frames in addition to capturing packets.
In some embodiments, the packet is inspected after it is captured. In one of these embodiments, the destination address of the packet is inspected. If the destination address is a private IP address associated with the client computing device, the packet may be redirected to a gateway computing device application executing in user mode on the gateway computing device.
A policy is applied to the packet (step 1006). In one embodiment, a management process applies the policy to the packet. In another embodiment, a policy engine applies the policy to the packet. The policy applied may require performance of a series of security checks, such as Access Control List matching and Deep Packet Inspection, on the received packet.
The packet is transmitted to the public IP address of the client computing device, responsive to the application of the policy to the packet (step 1008). After a packet has satisfied a policy, the gateway computing device may determine to transmit the packet to the client computing device. In one embodiment, the packet is re-associated with the original source address of the application generating the packet. The packet is forwarded to the client computing device. In some embodiments, the packets are transmitted over a secure SSL socket to the client computing device.
Referring now to
The gateway computing device 1140 includes a capture driver 1144 executing in the kernel 1142. In some embodiments, an operating system on the gateway computing device 1140 does not readily allow the interception of incoming RAW IP Layer packets. In one of these embodiments, the capture driver 1144, operating in kernel mode on the gateway computing device 1140, captures all Ethernet packets destined for remote client computing devices and forwards the packets back to the management process 1160 operating in user mode on the gateway computing device 1140.
In some embodiments, a protected server 1180, residing on the private network behind the gateway computing device 1140, generates a packet for transmission to the client computing device 1120. In one of these embodiments, the protected server 1180 transmits the packet to the gateway computing device for the gateway computing device for transmission to the client computing device. In another of these embodiments, the generated packet is transmitted as an Ethernet frame. In this embodiment, the capture driver 1144 may capture the Ethernet frame when the Ethernet frame arrives at the gateway computing device 1140. In an embodiment where the capture driver 1144 captures an Ethernet frame, the capture driver 1144 forwards the Ethernet frame to the gateway computing device application 1152 as a frame, not as a packet.
In some embodiments, the capture driver 1144 receives a request from the gateway computing device application 1152 for notification of any packet received with a destination address of the private IP address associated with the client computing device 1120. In one of these embodiments, the capture driver 1144 forwards any Ethernet frame that arrives to the gateway computing device application 1152 over an appropriate raw IP socket. Any reply packets arriving from the client computing device 1120 (even if for a port chosen dynamically by the client computing device 1120, which is typical of active protocols such as active FTP and SIP), are captured by the capture driver 1144 and forwarded to the management process 1160 in the gateway computing device application 1152, which manages the SSL tunnel between the gateway computing device 1140 and that particular client computing device 1120.
In some embodiments, the capture driver 1144 inspects all outbound network frames prior to routing. In one of these embodiments, an outbound network frame is a frame transmitted to the gateway computing device 1140 by a protected server 1180 for forwarding to the client computing device 1120. In another of these embodiments, an application 1158 on the gateway computing device 1140 generates an outbound network frame for transmission to the client computing device 1120. By inspecting all packets prior to routing, the capture driver 1144 increases security and performance, and minimizes the risk of conflicting entries in an operating system routing table. Inspecting packets prior to routing also increases the ability to control packet flow, without the intervention of the underlying network operating system. Since the capture driver 1144 inspects, and potentially filters, all packets prior to routing, a forwarding decision can be made without use of the routing table.
The gateway computing device 1140 includes application space 1150, on which applications execute, and a gateway computing device application 1152. In one embodiment, the gateway computing device application 1152 operates in user mode on the application space 1150. In some embodiments, the gateway computing device application 1152 includes a policy engine 1154, an addressing element 1156 and a management process 1160.
In one embodiment, the management process 1160 manages the capture driver 1144. In another embodiment, the management process 1160 receives a captured frame or a captured packet from the capture driver 1144. In some embodiments, the management process 1160 applies a policy to the packet. In other embodiments, the management process 1160 forwards the captured packet or frame to the policy engine 1154 for packet inspection and policy application.
In one embodiment, when a client computing device 1120 connects to the gateway computing device 1140 the gateway computing device 1140 creates a plurality of raw IP sockets for UDP, IP and other protocols such as ICMP. The management process 1160 may request notification from a capture driver 1144 when a packet arrives on the gateway computing device 1140 from a protected server 1180 addressed to a client computing device 1120. When the capture driver 1144 captures the packet, the capture driver 1144 may transmit the packet to one of the plurality of sockets.
In one embodiment, the policy engine 1154 inspects a captured packet or captured frame. In another embodiment, the policy engine 1154 applies a policy to the captured packet or captured frame. In some embodiments, the policy is an access control policy. In other embodiments, application of the policy determines whether the packet originated from a trusted source, such as a protected server 1180. In some embodiments, the policy engine 1154 transmits a configuration setting to the capture driver 1144.
In one embodiment, the gateway computing device application 1152 includes an addressing element 1156. The addressing element 1156 may associate a private IP address with a client computing device 1120. In one embodiment, the private IP address provides the client computing device 1120 with an address on a private network behind the gateway computing device 1140.
In some embodiments, the addressing element 1156 provides functionality for network address translation. In one of these embodiments, the addressing element 1156 transforms a private IP address to a public IP address. This type of transformation may occur on a packet prior to transmission of the packet from a protected server 1180 to a client computing device 1120, after the policy engine 1154 has approved the packet for transmission to the client computing device 1120.
In other embodiments, when a client computing device 1120 transmits a packet to the gateway computing device 1140, the addressing element 1156 enables transformation of the source address on the packet from the public IP address associated with the client computing device 1120 to the private IP address associated with the client computing device 1120. In one of these embodiments, the transformation occurs because the client computing device is not aware of its associated private IP address.
After the policy engine 1154 has applied a policy to a captured packet, the policy engine 1154 may determine that the packet may be transmitted to its original destination. In one embodiment, the policy engine 1154 forwards the packet to the transmitter 1148 for transmission to the client computing device 1120. In another embodiment, the transmitter 1148 first performs a network address translation on the packet. In some embodiments, the transmitter 1148 performs the network address translation. In one of these embodiments, the transmitter 1148 forwards the packet to the addressing element 1156 for transformation of the private IP address to the public IP address of the client computing device. In another of these embodiments, the transmitter 1148 completes the network address translation.
In one embodiment, the capture driver 1144 provides the functionality of the transmitter 1148. In another embodiment, the network address translation occurs in the gateway computing device application 1152 first and then the packet is forwarded to the capture driver 1144 for transmission to the client computing device 1120.
After the transmitter 1148 transmits the packet to the client computing device 1120, the client application 326 receives the packet from the gateway computing device 1140 and forwards the packet to the filter 322, using an I/O control message. The filter 322 then marks the packet as an incoming packet and forwards the packet to the destination application via the network stack.
The present invention may be provided as one or more computer-readable programs embodied on or in one or more articles of manufacture. The article of manufacture may be a floppy disk, a hard disk, a compact disc, a digital versatile disc, a flash memory card, a PROM, a RAM, a ROM, or a magnetic tape. In general, the computer-readable programs may be implemented in any programming language. Some examples of languages that can be used include C, C++, C#, or JAVA. The software programs may be stored on or in one or more articles of manufacture as object code.
While the invention has been shown and described with reference to specific preferred embodiments, it should be understood by those skilled in the art that various changes in form and detail may be made therein without departing from the spirit and scope of the invention as defined by the following claims.