|Publication number||US20090241180 A1|
|Application number||US 12/361,538|
|Publication date||Sep 24, 2009|
|Filing date||Jan 28, 2009|
|Priority date||Jan 28, 2008|
|Also published as||US8799410, US8838744, US20090193130, US20090193338, US20110191474, US20110238772, US20120246333, US20140380437|
|Publication number||12361538, 361538, US 2009/0241180 A1, US 2009/241180 A1, US 20090241180 A1, US 20090241180A1, US 2009241180 A1, US 2009241180A1, US-A1-20090241180, US-A1-2009241180, US2009/0241180A1, US2009/241180A1, US20090241180 A1, US20090241180A1, US2009241180 A1, US2009241180A1|
|Original Assignee||Trevor Fiatal|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (6), Referenced by (80), Classifications (17), Legal Events (4)|
|External Links: USPTO, USPTO Assignment, Espacenet|
The present application claims the priority benefit of U.S. provisional patent application No. 61/062,797 filed Jan. 28, 2008 and entitled “Systems and Methods for Data Transport.”
This application is related to U.S. patent application Ser. No. 12/361,520, filed Jan. 28, 2009 and entitled “Integrated Messaging,” the disclosure of which is incorporated herein by reference.
1. Field of the Invention
The present invention is generally related to the transport of data in a network. More specifically, the present invention is related to the transport of data objects to a mobile device from a data store in a mobile network without relying upon a store-and-forward methodology.
2. Description of the Related Art
Prior art data transport systems rely upon a store-and-forward approach that requires enormous server farms. Due to the immense amount of data stored for eventual forwarding, these systems are prone to collapse. A collapse jeopardizes data that has already been processed from a native data source to the extent that a store-and-forward system does not utilize any backup or redundancy precautions.
There is a need in the art for a scalable data transport system that does not rely upon a store-and-forward methodology and, further, that maintains the integrity of an original data object at the initial data source.
In a first claimed embodiment, a system is recited. The system includes a mobile device, a facilitating server, and a data source, wherein a data object at the data source is transported to the mobile device by way of the facilitating server.
Mobile device 110 is inclusive of any variety of mobile devices that are capable of communicating over the Internet. Mobile device 110 is inclusive of cellular telephones, smart phones, personal digital assistants (PDAs), wireless e-mail devices, and handheld computing devices. A variety of mobile networks and communications channels for enabling Internet access are well known in the art.
Mobile device 110 may be configured for communications over a Global System for Mobile communications (GSM), the General Packet Radio Service (GPRS), Enhanced Data rates for GSM Evolution (EDGE), Code Division Multiple Access (CDMA), or networks using the 3G mobile network standard. Mobile device 110 may include any number of applications or provisioned services. Exemplary applications hosted at the mobile device 110 include the aforementioned SMS agent 120 and Transport Protocol Application 130.
The SMS agent 120 may allow for operation in a hybrid mode (i.e., not purely Internet Protocol based). Keeping an Internet Protocol address open at all times, for some network operators, may be difficult as there is finite number of addresses available for numerous handsets. Time limits may be set for a particular Internet Protocol connection. Internet Protocol connections may be allowed so long as there is an active transmission. Keeping an Internet Protocol connection (and related address) open when the connection is really down (e.g., the mobile device 110 is on an airplane example), however, may be detrimental by using up an address that is not otherwise occupied or being used.
To avoid allocation of an address when an address is not (or need not be) in use, an SMS message may be sent to a device 110 by the facilitating server 140 or an SMS Message Center (SMSC). The SMSC may be operating in conjunction with the facilitating server 140 in order to wake up the device 110. The SMSC may similarly be used by the facilitating server 140 to verify that the device 110 is awake during periods of low activity at a data store 150 or extended periods of time with no connectivity. Failed responses or wakeups to an SMS message may be logged as an unavailable connection and the address reassigned. Likewise, the device 110 may request a connection by sending its own SMS message.
The transport protocol application 130 may operate in conjunction with facilitating server 140 to allow for updating a status table or index and to otherwise allow for the commencing of data transactions with data stores 150. The transport protocol application 130 may inform the facilitating server 140 that the device 110 is available for interaction. This interaction availability may include exchange of credentials or other registration information.
Facilitating server 140 is a rendezvous point or transaction router for system 100. Various applications and connectors for phones, data services, data stores, and so forth may be implemented at facilitating server 140. Facilitating server 140 (or servers) is scalable.
Various data sources (collectively 150) are exemplified by a Google mail account 150 a, Yahoo! mail account 150 b, and Exchange server 150 c, and which may be accessed in quasi-real-time by facilitating server 140 and/or optional proxy server 160 as described below. Data sources 150 are not limited to electronic-mail and are inclusive of any variety of data objects such as e-mail, calendar data, to do lists, and document attachments such as word processing documents, spreadsheets, presentation slide decks, photos, sound files, and motion picture files. Data objects may reside at or are otherwise accessible by data store 150. Data source 150 may also be representative of certain services utilizing data objects such as picture sharing services like Flickr.
Mobile device 110 may connect and ‘register’ with facilitating server 140. The mobile device 110 may be registered as a particular end point. The mobile device 110 may be broken down further with respect to particular data end points, for example, electronic mail. Mobile device 110 may be registered as one end point (e.g., a service channel) and individual mail boxes or data stores (e.g., Gmail, Exchange, Yahoo! Mail, person domain mail, etc.) related to a user of that mobile device 110 may be characterized as sub- or individual end points (e.g., specific service channels within that service channel). Each end point may be considered its own service operating over the same data connection between mobile device 110 and facilitating server 140.
More specifically, the mobile device 110 may be considered a master end-point. The mobile device 110, in turn, hosts various provisioned services (e.g., electronic mail). At the other ‘end’ of the system 100, and through facilitating server 140, is a particular data store 150 (e.g., a Gmail account) to which the facilitating server 140 is communicatively coupled. The facilitating server 140 maintains a record indicating that the particular data store 150 is associated with and accessible by the master end-point (mobile device 110), which is inclusive of a service or application corresponding to that data store (the aforementioned Gmail account). A similar record is maintained at facilitating server 140 for any other active service at mobile device 110.
In the process of registering with the facilitating server 140, the mobile device 110 provides a set of credentials. These credentials may be manually entered at the mobile device 110 or automatically provided as a part of a registration process. In the latter instance, the log-in information may be provided to the mobile device 110 by the user during an initial registration process (e.g., upon purchase and initialization of the phone or an application associated with the facilitating server 140). Credentials may include a user name, password, domain, identifying token, and/or any combination of the foregoing.
A separate mobile device with the proper credential information (e.g., a user name and password) might likewise interact with the facilitating server 140 and, in turn, access the same data store. This allows for the same data store to be accessible on a series of mobile devices. The facilitating server 140, in this regard, allows for mapping of credentials to data store access rather than any particular device.
Facilitating server 140 may host and execute certain connection applications to recognize certain events or data changes at data sources 750. Alternatively, data sources 750 may host and execute certain connection applications to provide notifications as to certain events or data changes at data sources 750. Those notifications, in turn, are received and processed by facilitating server 140. As appropriate, the facilitating server will provide subsequent notifications to mobile device 110 with respect to responding to a change at data source 750. Alternatively, facilitating server 140 may automatically take responsive action following notification or having identified the existence of a certain event or data change at data source 150. Automatic responsive action may be reflected by certain credential information provided by mobile device 110, which is then stored and mapped at facilitating server 140.
An ‘always on’ data connection is maintained (or attempted to be maintained) between mobile device 110 and facilitating server 140. If facilitating server 140 is unable to forward data from data source 750 due to the fact that the data connection between the facilitating server 140 and mobile device 110 is down (e.g., the user is on an airplane and has turned off their phone), the facilitating server 140 does not operate as a store and forward mechanism. Any data from a data source 150 that was being processed by the facilitating server 140 (or, in certain embodiments, at the data store 150 as is described below) for transport to the mobile device 110 is ‘flushed’ and removed from the facilitating server 140. The original data object or other data transaction thus remains in a pending state at the data source 150 and awaiting transport from the facilitating server 140 to mobile device 110.
In the event that a connection is down, a processing index at the facilitating server 140 will indicate that a data change or event has taken place at data source 150. The processing index will further indicate that processing of data related to that change or event remains unprocessed. Once the mobile device 110 is again available, that processing should re-commence with respect to the unprocessed data at data source 150. This index is maintained with respect to the mapped user credentials at the facilitating server 140 and any particular data store 150 mapped to the same.
The facilitating server 140 may also inform the connector application that the transmission of the data object to the mobile device 110 has failed (e.g., no ACK) and not to attempt further data transactions. This stay on further data transactions may remain in place until the facilitating server 140 confirms a ‘live’ connection. This status of the connection with respect to a particular set of credentials, which may be associated with a particular mobile device, may likewise be maintained in a processing index at the facilitating server 140.
Once the mobile device 110 is back online, the facilitating server 140 will attempt to re-establish a connection with the mobile device 110, which will result in an update to the processing index or other related status table. Once back on-line, the connection application will inform the data stores 150 that the associated end point is now available to receive data object transactions. Processing of any outstanding transactions as reflected in the index table may then take place whereby the facilitating server 140 and/or data source 150 begins re-processing the data object subject to a transaction.
In the event that a connection is down or unavailable, the facilitating server 140 will first attempt to open a data connection with the mobile device 110. The facilitating server 140 will undertake such an attempt rather than automatically and immediately flushing the data. If a pool of facilitating servers is utilized, this task may be ‘passed around’ in an attempt to find a facilitating server 140 that may successfully open the data connection. Passing around this task may also involve finding a facilitating server 140 that is properly balanced (i.e., not overloaded) with respect to any number of other facilitating servers in the system 100.
It may be most efficient to begin processing a data object from the data source 150 prior to or concurrent with opening a communication channel with the mobile device 110. In this manner, the processed data object may immediately be sent to the mobile device as soon as the channel is opened (i.e., the data has been processed and merely awaits an open channel for transmission). If processing of the data from data source 150 were delayed until the data channel were opened, that data channel would remain open but un-utilized while processing of the data from the data source 150 is initially undertaken (e.g., pulling the data object from the data source 150 to the facilitating server 140).
Opening a channel between facilitating server 140 and mobile device 110 may involve attempting to re-open an otherwise dormant but previously used TCP/IP channel. Alternatively, the facilitating server 140 may trigger the delivery of an SMS message to the device to initiate a fresh connection. In an embodiment not utilizing SMS, the mobile device 110 may utilize a polling application (not shown) that periodically polls the facilitating server 140. Polling may be subject to a predetermined schedule (e.g., every 10-15 seconds). The facilitating server 140 may wait for the next scheduled poll within a predetermined margin of error or delay. If a channel cannot be opened (the device 110 is actually unavailable), then the data is flushed as previously described and the index updated and/or maintained as is appropriate in light of the unprocessed data from data source 150.
For example, data source 150 b (Yahoo! Mail) may be representative of an empty e-mail inbox. An e-mail message may then arrive at message inbox 150 b. The appropriate connector application (of which there may be many, each for an appropriate data store 150) indicates to the facilitating server 140 that an event or data change has taken place.
The message—or other data object—may be compressed, truncated, and otherwise processed for delivery to the mobile device 110. This processing may take place at the facilitating server 140 after the data has been pulled from the data source 150. This compression and so forth may likewise take place at the data source 150. The processed data object then may be pushed to the facilitating server 140 or await a command from the facilitating server 140 pulling that data object to the facilitating server 140. A push of the processed data object to the mobile device 110 then takes place. Where certain processing of a data object takes place may depend on a particular arrangement between the host of the data source 150 and the facilitating server 140.
In some embodiments, an optional proxy server 160 may be used. The proxy server 160 may be used to communicate through an optional firewall 170. Certain data sources 150 or a corresponding firewall 170 may not allow facilitating server 140 to directly communicate with the data source 150. Certain data sources 150 may require an enterprise type server to handle certain transactions (e.g., proxy server 160). Facilitating server 140 and proxy server 160 may execute a number of similar functions and operate utilizing a similar software code base.
In such an embodiment where a proxy server 160 is required, the facilitating server 140 will process incoming transactions from mobile device end points, which are in turn passed to the proxy server 160, which allows for communication through the firewall 170 and may, in fact, be behind the firewall 170. In this regard,
The terms “computer-readable storage medium” and “computer-readable storage media” as used herein refer to a medium or media that participates in providing instructions to a CPU for execution. Such media can take many forms including, but not limited to, non-volatile and volatile media. Non-volatile media include, for example, optical or magnetic disks, such as a fixed disk. Volatile media include dynamic memory, such as system RAM. Common forms of computer-readable storage media include, for example, a floppy disk, a flexible disk, a hard disk, magnetic tape, any other magnetic medium, a CD-ROM disk, digital video disk (DVD), any other optical medium, punch cards, paper tape, any other physical medium with patterns of marks or holes, a RAM, a PROM, an EPROM, a FLASHEPROM, any other memory chip or cartridge.
Transmission media may include coaxial cables, copper wire and fiber optics and various computer bus. Transmission media can also take the form of acoustic or light waves such as those generated during radio frequency (RF) and infrared (IR) data communications. Carrier wave or other media for transmission of information may be used.
The above description is illustrative and not restrictive. Many variations of the invention will become apparent to those of skill in the art upon review of this disclosure. The scope of the invention should, therefore, be determined not with reference to the above description, but instead should be determined with reference to the appended claims along with their full scope of equivalents.
While the present invention has been described in connection with a series of preferred embodiment, these descriptions are not intended to limit the scope of the invention to the particular forms set forth herein. To the contrary, the present descriptions are intended to cover such alternatives, modifications, and equivalents as may be included within the spirit and scope of the invention as defined by the appended claims and otherwise appreciated by one of ordinary skill in the art
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US7454457 *||Jun 8, 2000||Nov 18, 2008||Parallel Networks, Llc||Method and apparatus for dynamic data flow control using prioritization of data requests|
|US20020174208 *||May 16, 2001||Nov 21, 2002||International Business Machines Corporation||Network communications management system and method|
|US20040117439 *||Feb 12, 2002||Jun 17, 2004||Levett David Lawrence||Client software enabling a client to run a network based application|
|US20040121785 *||Dec 18, 2002||Jun 24, 2004||Vance Robert B.||Message transmission system in a GPRS environment|
|US20040185834 *||Mar 21, 2003||Sep 23, 2004||Daniel Sommers||Method for enabling IP push capability to wireless devices on a wireless network|
|US20040224674 *||Apr 7, 2004||Nov 11, 2004||O'farrell Robert||System and method for context sensitive mobile data and software update|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US8010082||Oct 19, 2005||Aug 30, 2011||Seven Networks, Inc.||Flexible billing architecture|
|US8064583||Sep 21, 2006||Nov 22, 2011||Seven Networks, Inc.||Multiple data store authentication|
|US8069166||Feb 27, 2006||Nov 29, 2011||Seven Networks, Inc.||Managing user-to-user contact with inferred presence information|
|US8078158||Jun 26, 2008||Dec 13, 2011||Seven Networks, Inc.||Provisioning applications for a mobile device|
|US8107921||Jan 11, 2008||Jan 31, 2012||Seven Networks, Inc.||Mobile virtual network operator|
|US8116214||Nov 30, 2005||Feb 14, 2012||Seven Networks, Inc.||Provisioning of e-mail settings for a mobile terminal|
|US8127342||Sep 23, 2010||Feb 28, 2012||Seven Networks, Inc.||Secure end-to-end transport through intermediary nodes|
|US8166164||Oct 14, 2011||Apr 24, 2012||Seven Networks, Inc.||Application and network-based long poll request detection and cacheability assessment therefor|
|US8190701||Nov 1, 2011||May 29, 2012||Seven Networks, Inc.||Cache defeat detection and caching of content addressed by identifiers intended to defeat cache|
|US8204953||Nov 1, 2011||Jun 19, 2012||Seven Networks, Inc.||Distributed system for cache defeat detection and caching of content addressed by identifiers intended to defeat cache|
|US8209709||Jul 5, 2010||Jun 26, 2012||Seven Networks, Inc.||Cross-platform event engine|
|US8291076||Mar 5, 2012||Oct 16, 2012||Seven Networks, Inc.||Application and network-based long poll request detection and cacheability assessment therefor|
|US8316098||Nov 20, 2012||Seven Networks Inc.||Social caching for device resource sharing and management|
|US8326985||Nov 1, 2011||Dec 4, 2012||Seven Networks, Inc.||Distributed management of keep-alive message signaling for mobile network resource conservation and optimization|
|US8356080||Jan 15, 2013||Seven Networks, Inc.||System and method for a mobile device to use physical storage of another device for caching|
|US8364181||Dec 10, 2007||Jan 29, 2013||Seven Networks, Inc.||Electronic-mail filtering for mobile devices|
|US8412675||Feb 24, 2006||Apr 2, 2013||Seven Networks, Inc.||Context aware data presentation|
|US8417823||Nov 18, 2011||Apr 9, 2013||Seven Network, Inc.||Aligning data transfer to optimize connections established for transmission over a wireless network|
|US8438633||Dec 18, 2006||May 7, 2013||Seven Networks, Inc.||Flexible real-time inbox access|
|US8468126||Dec 14, 2005||Jun 18, 2013||Seven Networks, Inc.||Publishing data in an information community|
|US8484314||Oct 14, 2011||Jul 9, 2013||Seven Networks, Inc.||Distributed caching in a wireless network of content delivered for a mobile application over a long-held request|
|US8494510||Dec 6, 2011||Jul 23, 2013||Seven Networks, Inc.||Provisioning applications for a mobile device|
|US8539040||Feb 28, 2012||Sep 17, 2013||Seven Networks, Inc.||Mobile network background traffic data management with optimized polling intervals|
|US8549587||Feb 14, 2012||Oct 1, 2013||Seven Networks, Inc.||Secure end-to-end transport through intermediary nodes|
|US8561086||May 17, 2012||Oct 15, 2013||Seven Networks, Inc.||System and method for executing commands that are non-native to the native environment of a mobile device|
|US8621075||Apr 27, 2012||Dec 31, 2013||Seven Metworks, Inc.||Detecting and preserving state for satisfying application requests in a distributed proxy and cache system|
|US8635339||Aug 22, 2012||Jan 21, 2014||Seven Networks, Inc.||Cache state management on a mobile device to preserve user experience|
|US8693494||Mar 31, 2008||Apr 8, 2014||Seven Networks, Inc.||Polling|
|US8700728||May 17, 2012||Apr 15, 2014||Seven Networks, Inc.||Cache defeat detection and caching of content addressed by identifiers intended to defeat cache|
|US8738050||Jan 7, 2013||May 27, 2014||Seven Networks, Inc.||Electronic-mail filtering for mobile devices|
|US8750123||Jul 31, 2013||Jun 10, 2014||Seven Networks, Inc.||Mobile device equipped with mobile network congestion recognition to make intelligent decisions regarding connecting to an operator network|
|US8761756||Sep 13, 2012||Jun 24, 2014||Seven Networks International Oy||Maintaining an IP connection in a mobile network|
|US8774844||Apr 8, 2011||Jul 8, 2014||Seven Networks, Inc.||Integrated messaging|
|US8775631||Feb 25, 2013||Jul 8, 2014||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|
|US8782222||Sep 5, 2012||Jul 15, 2014||Seven Networks||Timing of keep-alive messages used in a system for mobile network resource conservation and optimization|
|US8787947||Jun 18, 2008||Jul 22, 2014||Seven Networks, Inc.||Application discovery on mobile devices|
|US8793305||Dec 13, 2007||Jul 29, 2014||Seven Networks, Inc.||Content delivery to a mobile device from a content service|
|US8799410||Apr 13, 2011||Aug 5, 2014||Seven Networks, Inc.||System and method of a relay server for managing communications and notification between a mobile device and a web access server|
|US8805334||Sep 5, 2008||Aug 12, 2014||Seven Networks, Inc.||Maintaining mobile terminal information for secure communications|
|US8805425||Jan 28, 2009||Aug 12, 2014||Seven Networks, Inc.||Integrated messaging|
|US8811952||May 5, 2011||Aug 19, 2014||Seven Networks, Inc.||Mobile device power management in data synchronization over a mobile network with or without a trigger notification|
|US8812695||Apr 3, 2013||Aug 19, 2014||Seven Networks, Inc.||Method and system for management of a virtual network connection without heartbeat messages|
|US8831561||Apr 28, 2011||Sep 9, 2014||Seven Networks, Inc||System and method for tracking billing events in a mobile wireless network for a network operator|
|US8832228||Apr 26, 2012||Sep 9, 2014||Seven Networks, Inc.||System and method for making requests on behalf of a mobile device based on atomic processes for mobile network traffic relief|
|US8838744||Jan 28, 2009||Sep 16, 2014||Seven Networks, Inc.||Web-based access to data objects|
|US8838783||Jul 5, 2011||Sep 16, 2014||Seven Networks, Inc.||Distributed caching for resource and mobile network traffic management|
|US8839412||Sep 13, 2012||Sep 16, 2014||Seven Networks, Inc.||Flexible real-time inbox access|
|US8843153||Nov 1, 2011||Sep 23, 2014||Seven Networks, Inc.||Mobile traffic categorization and policy for network use optimization while preserving user experience|
|US8849902||Jun 24, 2011||Sep 30, 2014||Seven Networks, Inc.||System for providing policy based content service in a mobile network|
|US8861354||Dec 14, 2012||Oct 14, 2014||Seven Networks, Inc.||Hierarchies and categories for management and deployment of policies for distributed wireless traffic optimization|
|US8862657||Jan 25, 2008||Oct 14, 2014||Seven Networks, Inc.||Policy based content service|
|US8868753||Dec 6, 2012||Oct 21, 2014||Seven Networks, Inc.||System of redundantly clustered machines to provide failover mechanisms for mobile traffic management and network resource conservation|
|US8873411||Jan 12, 2012||Oct 28, 2014||Seven Networks, Inc.||Provisioning of e-mail settings for a mobile terminal|
|US8874761||Mar 15, 2013||Oct 28, 2014||Seven Networks, Inc.||Signaling optimization in a wireless network for traffic utilizing proprietary and non-proprietary protocols|
|US8886176||Jul 22, 2011||Nov 11, 2014||Seven Networks, Inc.||Mobile application traffic optimization|
|US8903954||Nov 22, 2011||Dec 2, 2014||Seven Networks, Inc.||Optimization of resource polling intervals to satisfy mobile device requests|
|US8909192||Aug 11, 2011||Dec 9, 2014||Seven Networks, Inc.||Mobile virtual network operator|
|US8909202||Jan 7, 2013||Dec 9, 2014||Seven Networks, Inc.||Detection and management of user interactions with foreground applications on a mobile device in distributed caching|
|US8909759||Oct 12, 2009||Dec 9, 2014||Seven Networks, Inc.||Bandwidth measurement|
|US8914002||Aug 11, 2011||Dec 16, 2014||Seven Networks, Inc.||System and method for providing a network service in a distributed fashion to a mobile device|
|US8918503||Aug 28, 2012||Dec 23, 2014||Seven Networks, Inc.||Optimization of mobile traffic directed to private networks and operator configurability thereof|
|US8966066||Oct 12, 2012||Feb 24, 2015||Seven Networks, Inc.||Application and network-based long poll request detection and cacheability assessment therefor|
|US8977755||Dec 6, 2012||Mar 10, 2015||Seven Networks, Inc.||Mobile device and method to utilize the failover mechanism for fault tolerance provided for mobile traffic management and network/device resource conservation|
|US8984581||Jul 11, 2012||Mar 17, 2015||Seven Networks, Inc.||Monitoring mobile application activities for malicious traffic on a mobile device|
|US8989728||Sep 7, 2006||Mar 24, 2015||Seven Networks, Inc.||Connection architecture for a mobile network|
|US9002828||Jan 2, 2009||Apr 7, 2015||Seven Networks, Inc.||Predictive content delivery|
|US9009250||Dec 7, 2012||Apr 14, 2015||Seven Networks, Inc.||Flexible and dynamic integration schemas of a traffic management system with various network operators for network traffic alleviation|
|US9021021||Dec 10, 2012||Apr 28, 2015||Seven Networks, Inc.||Mobile network reporting and usage analytics system and method aggregated using a distributed traffic optimization system|
|US9043433||May 25, 2011||May 26, 2015||Seven Networks, Inc.||Mobile network traffic coordination across multiple applications|
|US9043731||Mar 30, 2011||May 26, 2015||Seven Networks, Inc.||3D mobile user interface with configurable workspace management|
|US9047142||Dec 16, 2010||Jun 2, 2015||Seven Networks, Inc.||Intelligent rendering of information in a limited display environment|
|US9049179||Jan 20, 2012||Jun 2, 2015||Seven Networks, Inc.||Mobile network traffic coordination across multiple applications|
|US9055102||Aug 2, 2010||Jun 9, 2015||Seven Networks, Inc.||Location-based operations and messaging|
|US9060032||May 9, 2012||Jun 16, 2015||Seven Networks, Inc.||Selective data compression by a distributed traffic management system to reduce mobile data traffic and signaling traffic|
|US9065765||Oct 8, 2013||Jun 23, 2015||Seven Networks, Inc.||Proxy server associated with a mobile carrier for enhancing mobile traffic management in a mobile network|
|US9077630||Jul 8, 2011||Jul 7, 2015||Seven Networks, Inc.||Distributed implementation of dynamic wireless traffic policy|
|US9084105||Apr 19, 2012||Jul 14, 2015||Seven Networks, Inc.||Device resources sharing for network resource conservation|
|US9100873||Sep 14, 2012||Aug 4, 2015||Seven Networks, Inc.||Mobile network background traffic data management|
|US9131397||Jun 6, 2013||Sep 8, 2015||Seven Networks, Inc.||Managing cache to prevent overloading of a wireless network due to user activity|
|USRE45348||Mar 16, 2012||Jan 20, 2015||Seven Networks, Inc.||Method and apparatus for intercepting events in a communication system|
|U.S. Classification||726/12, 709/227, 709/203, 709/230, 455/466, 707/999.2, 726/5, 709/206|
|International Classification||G06F15/16, G06F21/20, H04W4/12|
|Cooperative Classification||H04W12/06, H04L63/10, H04L12/587, H04L63/08, H04L51/24|
|May 26, 2009||AS||Assignment|
Owner name: SEVEN NETWORKS, INC., CALIFORNIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:FIATAL, TREVOR;REEL/FRAME:022735/0393
Effective date: 20090202
|Aug 5, 2009||AS||Assignment|
Owner name: VELOCITY FINANCIAL GROUP, INC.,MASSACHUSETTS
Free format text: SECURITY AGREEMENT;ASSIGNOR:SEVEN NETWORKS, INC.;REEL/FRAME:023044/0834
Effective date: 20090720
|Jun 27, 2015||AS||Assignment|
Owner name: SEVEN NETWORKS INC., CALIFORNIA
Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:VELOCITY FINANCIAL GROUP, INC.;REEL/FRAME:035922/0345
Effective date: 20120228
|Aug 27, 2015||AS||Assignment|
Owner name: SEVEN NETWORKS, LLC, CALIFORNIA
Free format text: ENTITY CONVERSION;ASSIGNOR:SEVEN NETWORKS, INC.;REEL/FRAME:036485/0059
Effective date: 20150714