A system includes an e-mail engine which uses a proper protocol to retrieve an e-mail from a first mail store and to store the e-mail in one or more folder structures. Upon request, the first mail store may send configuration data indicating the proper protocol to the e-mail engine, which can then properly configure itself. An e-mail synchronization module uses a predetermined criterion to determine whether the e-mail was previously sent and whether to synchronize the e-mail with a second mail store. The e-mail synchronization module may also synchronize the e-mail of specific folder structures. The second mail store may be located on a global server, which upon proper identification and authentication provides roaming users with access to its contents. A communications module establishes a communications channel through any firewalls with the second mail store. A web engine sends the e-mail via the communications channel to the second mail store.
|
34. A computer-readable storage medium storing program code for causing a client computer to perform the steps of:
obtaining e-mail from a mail server; using a predetermined criterion to determine whether to send e-mail to a central mail store; establishing a communications channel with the central mail store; and sending e-mail to the central mail store.
13. A client-based method comprising:
obtaining an e-mail from a mail server; using a predetermined criterion to determine whether to send the e-mail to a central mail store; establishing a communications channel with the central mail store, if the predetermined criterion indicates sending the e-mail; and sending the e-mail to the mail store, if the predetermined criterion indicates sending the e-mail.
32. A client system for automatically downloading e-mails for a particular client from a mail server which implements a particular protocol, comprising:
means for automatically initiating a communications channel with a mail server; means for identifying the particular protocol used by the mail server; and means for using the particular protocol to download e-mails addressed to a particular client from the mail server.
1. A client system comprising:
obtaining means for obtaining e-mail from a mail server; determining means for using a predetermined criterion to determine whether to send the e-mail to a central mail store; establishing means, coupled to the determining means, for establishing a communications channel with the central mail store; and sending means, coupled to the establishing means, for sending e-mail to the central mail store.
23. A client system comprising:
an e-mail engine for obtaining e-mail from a mail server; an e-mail synchronization module for using a predetermined criterion to determine whether to send e-mail to a central mail store; a communications module coupled to the e-mail synchronization module for establishing a communications channel with the central mail store; and a web engine, coupled to the communications module, for sending e-mail to the central mail store.
3. The system of
4. The system of
5. The system of
6. The system of
7. The system of
9. The system of
10. The system of
12. The system of
14. The method of
16. The method of
17. The method of
wherein the central mail store is protected by a firewall; and further comprising the step of communicating through the firewall.
18. The method of
19. The method of
21. The method of
22. The method of
25. The system of
27. The system of
28. The system of
29. The system of
30. The system of
31. The system of
33. The system of
|
|||||||||||||||||||||||||||
This application is a continuation-in-part application of patent application, Ser. No. 08/865,075, entitled "System and Method for Using a Global Translator to Synchronize Workspace Elements across a Network," filed on May 29, 1997, by inventors Daniel J. Mendez, Mark D. Riggins, Prasad Wagle and Christine C. Ying, which is herein incorporated by reference, which is a continuation-in-part of patent application Ser. No. 08/835,997, entitled "System and Method for Securely Synchronizing Multiple Copies of a Workspace Element in a Network," filed on Apr. 11, 1997, by inventors Daniel J. Mendez, Mark D. Riggins, Prasad Wagle and Christine C. Ying. These applications have also been assigned to RoamPage, Inc.
1. Field of the Invention
This invention relates generally to computer networks, and more particularly the present invention provides a system and method for synchronizing electronic mail across a computer network.
2. Description of the Background Art
Data consistency is a significant concern for computer users. For example, when maintaining multiple independently modifiable copies of a document, a user risks using an outdated version. By the time the user notices an inconsistency, interparty miscommunication or data loss may have already resulted. The user must then spend more time attempting to reconcile the inconsistent versions and addressing any miscommunications.
The problems of data inconsistency is exacerbated when copies of a document are inaccessible. For example, when multiple copies of a document are maintained at different network locations, network security systems such as conventional firewall technology compromise data accessibility. That is, a user may have access to only a particular one of these network locations. Without access to the other sites, the user cannot confirm that the version on an accessible site is the most recent draft.
The problems of data consistency and accessibility arise in the area of electronic mail (e-mail). For example, a user might maintain an e-mail database at work. Based on the security systems implemented by the work intranet, the user may not be afforded access to the database and thus cannot read or respond to the e-mails until returning to work. Further, a traveling user currently working at a remote terminal may not have the necessary dedicated application programs to pass the intranet security. Still further, when maintaining several sites, the traveling user is burdened to maintain a record of all procedures and passwords to overcome the security system at each site.
These problems are further exacerbated when using e-mail programs from different vendors and which implement different protocols. For example, the Netscape Navigator™ e-mail client and the Outlook Express™ e-mail client each manage e-mail across computer networks. However, each e-mail client uses different formats, stores e-mails in different files and implements different protocols. Thus, the e-mails are not readily interchangeable.
Therefore, a system and method are needed for providing users with e-mail consistency and accessibility across a computer network.
The present invention provides a system including an e-mail engine for using the proper protocol to retrieve an e-mail from a first mail store. That is, the e-mail engine and the first mail store implement the same protocol, e.g., the Post Office Protocol (POP3), to communicate therebetween. Upon request, the first mail store may send configuration data indicating the proper protocol to the e-mail engine, which can then properly configure itself.
The system further includes an e-mail synchronization module which uses a predetermined criterion to determine whether to send the e-mail to a second mail store. For example, the e-mail synchronization module need not send an e-mail to the second mail store if the e-mail was previously sent. The second mail store may be located on a global server, which upon proper identification and authentication provides roaming (traveling) users with HTML access to its contents.
The system further includes a communications module for establishing a communications channel with the second mail store. If the second store is protected by a firewall, the communications module is authorized to establish a secure communications link through the firewall with the second store. The system still further includes a web engine for using the HyperText Transfer Protocol (HTTP) to send the e-mail via the communications channel to the second mail store. The system may be stored on a computer-readable storage medium.
Another system which embodies the present invention can be broadly described to include means for retrieving an e-mail from a first mail store, means coupled to the retrieving means for using a predetermined criterion to determine whether to send the e-mail to a second mail store, means coupled to the using means for establishing a communications channel with the second mail store, and means coupled to the establishing means for sending the e-mail to the second mail store.
Similarly, a method which embodies the present invention includes the steps of retrieving an e-mail from a first mail store, using a predetermined criterion to determine whether to send the e-mail to a second mail store, establishing a communications channel with the second mail store, and sending the e-mail to the second mail store.
The system and method advantageously use a trusted third party to enable synchronization of electronic mail across a network. Accordingly, a user who maintains for example a work site, a home site and the global server site can synchronize e-mails among all three sites. The roaming user thus can access and reply to e-mails while away from the addressed site. Because the system and method operate over the Internet, synchronization can occur over any distance. Since the system and method include format translation, merging of e-mails between different application programs and different platforms is possible. Further, because synchronization is initiated from within the firewall and uses commonly enabled protocols such as HyperText Transfer Protocol (HTTP), the typical firewall which prevents in-bound communications in general and some outbound protocols does not act as an impediment to e-mail synchronization. Also. since the user's preferences may be previously set, the present system and method may operate unattended by the client user.
FIG. 1 is a block diagram illustrating a computer network in accordance with the present invention;
FIG. 2 is a block diagram illustrating details of a FIG. 1 service server;
FIG. 3 is a block diagram illustrating details of the FIG. 1 desktop computer;
FIG. 4 is a block diagram illustrating details of a FIG. 1 base system;
FIG. 5 is a block diagram illustrating details of the FIG. 1 synchronization agent;
FIG. 6 is a graphical representation of an example bookmark in the global format;
FIG. 7 is a flowchart illustrating a method for synchronizing multiple copies of a workspace element in a secure network;
FIG. 8 is a block diagram illustrating a computer network in accordance with the present invention;
FIG. 9 is a block diagram illustrating details of a FIG. 8 client;
FIG. 10 is a block diagram illustrating details of the FIG. 9 base system;
FIG. 11 is a block diagram illustrating details of a FIG. 8 global server;
FIG. 12 is a block diagram illustrating details of the FIG. 8 synchronization agent;
FIG. 13 is a block diagram illustrating details of the FIG. 8 remote terminal;
FIG. 14 is a flowchart illustrating a method for synchronizing electronic mail in a computer network; and
FIG. 15 is a flowchart illustrating a method for accessing electronic mail from the global server of FIG. 8.
FIG. 1 is a block diagram illustrating a computer network 100, comprising a first node such as a remote computer terminal 102 coupled via a communications channel 104 such as the Internet to a global server 106. The global server 106 is in turn coupled via a communications channel 108 such as the Internet to a second node such as a Local Area Network (LAN) 110. The global server 106 is protected by a global firewall 112, and the LAN 110 is protected by a LAN firewall 114.
The LAN 110 includes a system bus 126 coupling the LAN firewall 114 to an e-mail server 128 having an e-mail folder 138 containing e-mails, to a file server 132 having a file folder 142 containing files, to a calendar server 130 having a calendar folder 140 containing calendar data, and to a desktop computer 134 having a web browser 152 and a bookmark folder 144 containing bookmarks. It will be appreciated that the e-mail folder 138, file folder 142, calendar folder 140 and bookmark folder 144 or portions thereof may be stored at different locations such as on the desktop computer 134. The e-mail folder 138, file folder 142, calendar folder 140 and bookmark folder 144 are exemplary, grouped by like information and are collectively referred to herein as "workspace data" 136. Those skilled in the art will recognize that the workspace data 136 may include other types of data such as an application program such as Microsoft Word 6∅1 and the documents created using them. It will be further appreciated that the e-mail folder 138, file folder 142, calendar folder 140 and bookmark folder 144 may each be divided into workspace elements, wherein each workspace element folder or each workspace element individually is identified by particular version information 255 (described below with reference to FIG. 2). Accordingly, each e-mail or e-mail folder, file or file folder, calendar or calendar folder, bookmark or bookmark folder, document or document folder, etc. may be referred to as "a workspace element."
Each workspace element of workspace data 136 in LAN 110 is maintained in a predetermined format, referred to as Format A, which is based on the service engine 245 (FIG. 2) that created it. For example, the web browser 152 on the desktop computer 134 may be the Netscape Navigator™ web browser, and the bookmarks in the bookmark folder 144 created thereby are maintained in Format A. Although Format A is being described as a single format, one skilled in the art knows that Format A actually includes a format for each information type, e.g., there will be a Format A for bookmarks, a Format A for files, a Format A for calendar data, a Format A for e-mails, etc.
The remote terminal 102 stores service engines 154 for maintaining workspace data 116, which may include information common with information in the workspace data 136. The workspace data 116 is maintained in a format, referred to as Format B, which may be different from Format A. Format B is also based on the service engines 154 that create the workspace elements. For example, if one of the service engines 154 is the Internet Explorer™ web browser (not shown), then the bookmarks (not shown) created therewith are maintained in Format B. Although Format B is being described as a single format, one skilled in the art knows that Format B actually includes a format for each information type. Further, the workspace data 116 also includes version information 150 similar to version information 255 described below with reference to FIG. 2.
It will be appreciated that remote terminal 102 may include a smart telephone, a Personal Data Assistant (PDA) such as the PalmPilot system by the U.S. Robotics, Inc., a laptop computer, etc. As a smart telephone, the workspace data 116 may include telephone numbers and e-mails. As a PDA, the workspace data 116 may include addresses, calendar data and e-mails. As a laptop computer, the workspace data 116 may include the same types of information as workspace data 136.
The global server 106 acts as a third party administrator. The global server 106 stores independently modifiable copies of selected portions of the workspace data 136 and 116, collectively referred to herein as workspace data 120. Accordingly, the workspace data 120 includes an independently modifiable copy of each workspace element in the selected portions of the workspace data 136 and 116 and an independently modifiable copy of each corresponding version information 255 (FIG. 2) and 150. The version information copies are collectively referred to herein as version information 148, and are also described with reference to FIG. 2.
The global server 106 maintains the workspace data 120 in a format, referred to as a "global format," which is selected to be easily translatable by the global translator 122 to and from Format A and to and from Format B. Although the global format is being described as a single format, one skilled in the art knows that the global format actually includes a global format for each information type, e.g., there will be a global format for bookmarks, a global format for files, a global format for calendar data, a global format for e-mails, etc. An example bookmark workspace element in the global format is described in detail below with reference to FIG. 6.
Network 100 further comprises synchronization means, which includes a base system 146 stored within the LAN 110 and for example on the desktop computer 134. Network 100 further includes a synchronization agent 124 stored outside the LAN firewall 114 and preferably on the global server 106. The base system 146 and the synchronization agent 124 cooperate to synchronize selected portions of the workspace data 136 with selected portions of the workspace data 120. The synchronization means may synchronize workspace elements individually, e.g., specific word processor documents, or may synchronize workspace element folders, e.g., a bookmark folder. Generally, the base system 146 manages the selected portion of the workspace data 136 within the LAN 110 and the synchronization agent 124 manages the selected portions of the workspace data 120 within the global server 106. It will be appreciated that the global translator 122 cooperates with the synchronization means to translate data formats to and from the global format. As described in greater detail below with reference to FIG. 4, the base system 190 preferably initiates and controls data synchronization. Other components and functions of the global server 106 are described in the cross-referenced patent application which is herein incorporated by reference.
The synchronization means may also include, stored on the remote terminal 102, a base system 118 which operates in a similar manner to the base system 146. The base system 118 on the remote terminal 102 cooperates with the synchronization agent 124 to synchronize selected portions of the workspace data 116 with selected portions of the workspace data 120. As described in greater detail below with reference to FIG. 4, the base system 118 on the remote terminal 102 also preferably initiates and controls data synchronization with the global server 106. Also, note that the distribution of labor between the base system 118 in the remote terminal 102 and the synchronization agent 124 in the global server 106 may vary. Sometimes, primarily when the remote terminal 102 is a relatively less computationally powerful device (such as a smart phone or a PDA), most of the actual computationally intensive work will occur within the synchronization agent 124 in the global server 106. In other situations, for example, when the remote terminal 102 is a fully configured PC, most of the computationally-intensive work will occur locally on the base system 118 in the remote terminal 102.
Accordingly, the synchronization means independently synchronizes the selected portions of workspace data 116 and 136 with the selected portions of the workspace data 120. Thus, the synchronization means indirectly synchronizes workspace data 136 with workspace data 116.
FIG. 2 is a block diagram illustrating details of a service server 200, wherein each of the e-mail server 145, the file server 150, the calendar server 155 and the desktop computer 160 is an instance thereof. Service server 200 includes a Central Processing Unit (CPU) 205 such as an Intel Pentium® microprocessor or a Motorola Power PC® microprocessor. An input device 210 such as a keyboard and mouse and an output device 215 such as a Cathode Ray Tube (CRT) display are coupled via a signal bus 220 to CPU 205. A communications interface 225 (such as an Ethernet port), a data storage device 230 (such as a magnetic disk), and Random-Access Memory (RAM) 235 are further coupled via signal bus 220 to the CPU 205.
An operating system 240 includes a program for controlling processing by the CPU 205, and is typically stored in the data storage device 230 and loaded into the RAM 235 for execution. A service engine 245 includes a program for performing a particular service such as maintaining an e-mail database, a file database, a calendar database or a bookmarks database. The service engine 245 may also be stored in the data storage device 230 and loaded into the RAM 235 for execution.
To perform a service, the service engine 245 creates service data 250 (e.g., an e-mail or an e-mail folder 138 containing e-mails, a file or a file folder 142 containing files, calendar data or a calendar folder 140 containing calendar data, a bookmark or a bookmark folder 144 containing bookmarks, etc.) in Format A according to predetermined protocols. The service engine 245 stores the data 250 in the data storage device 250. The service data 250 includes version information 255 indicating the date and time of the last modification and the status as of the last interaction with the global server 106.
For example, if service data 250 is created and selected to be merged with global server workspace data 120, then the version information 255 for the service data 250 may include the date of last modification and a null set indicating the status as of the last interaction with the global server 106. From the version information 255, the base system 146 determines that the service data 250 in its entirety has not been merged with the global server workspace data 120. Similarly, if the service data 255 included elements 1, 2 and 3 as of the last modification, then the previous status as of the last interaction will indicate that the service data 255 included elements 1, 2 and 3. If the service data 255 currently includes elements 2, 3 and 4, then the base system 140 will determine that, since last synchronization, element 1 has been deleted and element 4 has been added.
It will be appreciated that the version information 148 on the global server 106 includes information similar to version information 255. That is, the version information 148 will include information indicating the date and time the version was last modified and the status as of the last interaction with each client. The service engine 245 operates to update the version information 255 after modifications are made and after synchronization occurs.
FIG. 3 is a block diagram illustrating details of the desktop computer 160, which includes a CPU 305, an input device 310, an output device 315, a communications interface 325, a data storage device 330 and RAM 335, each coupled to a signal bus 320.
An operating system 340 includes a program for controlling processing by the CPU 305, and is typically stored in the data storage device 330 and loaded into the RAM 335 for execution. A web browser 152 (i.e., a particular service engine 245, FIG. 2) includes a Format A service program for managing bookmark folder 144 (i.e., particular service data 250, FIG. 2) which includes version information 350 (i.e., particular version information 255, FIG. 2). The web browser 152 may be also stored in the data storage device 330 and loaded into the RAM 335 for execution. The bookmark folder 144 may be stored in the data storage device 330. As stated above with reference to FIG. 1, the base system 146 operates to synchronize the workspace data 136 (which includes the bookmark folder 144) with the workspace data 120. The base system 146 may be also stored in the data storage device 330 and loaded into the RAM 335 for execution.
FIG. 4 is a block diagram illustrating details of the base system 400, which exemplifies base systems 146 and 118. Base system 400 includes a communications module 405, a user interface module 410, locator modules 415, a synchronization-start ("synch-start") module 420, a general synchronization module 425 and a content-based synchronization module 430. For simplicity, each module is illustrated as communicating with one another via a signal bus 440.
The communications module 405 includes routines for compressing data and routines for communicating via the communications interface 325 (FIG. 3) with the synchronization agent 124 (FIG. 1). The communications module 405 may further include routines for applying Secure Socket Layer (SSL) technology and user identification and authentication techniques (i.e., digital certificates) to establish a secure communication channel through the global firewall 112. Examples of communications modules 405 may include TCP/IP stacks or the AppleTalk® protocol.
The user interface module 410 includes routines for communicating with a user, and may include a conventional Graphical User Interface (GUI). The user interface module 410 cooperates with the other system components as described herein.
The locator modules 415 include routines for identifying the memory locations of the workspace elements in the workspace data 136 or 116 and in the workspace data 120. Workspace element memory location identification may be implemented using intelligent software, i.e., preset memory addresses or the system's registry, or using dialogue boxes to query a user. More particularly, the locator modules 415 in the base system 146 determine the memory addresses of the e-mail folder 138, the file folder 142, the calendar folder 140 and the bookmark folder 144 and the memory addresses of the workspace elements therein. The locator modules 415 also determine the corresponding memory addresses of the corresponding folders in the workspace data 120 and the corresponding workspace elements therein. Similarly, the locator modules 415 in the base system 118 determine the memory locations of the workspace elements of workspace data 116 and the memory locations of the corresponding workspace elements in the workspace data 120.
It will be appreciated that the locator modules 415 may include locator modules 415 specifically dedicated to each folder or workspace data type. That is, the locator modules 415 may include a locator module 415 dedicated to locating bookmarks, a locator module 415 dedicated to locating e-mails, a locator module 415 dedicated to locating files, a locator module 415 dedicated to locating calendar appointments, etc. It will be further appreciated that the locator modules 415 may perform workspace element memory location identification upon system boot-up or after each communication with the global server 120 to maintain updated memory addresses of workspace elements.
The synchronization-start module 420 includes routines for determining when to initiate synchronization of workspace data 136 or 116 with workspace data 120. For example, the synchronization-start module 420 may initiate data synchronization upon user request, at a particular time of day, after a predetermined time period passes, after a predetermined number of changes, after a user action such as user log-off or upon like criteria. The synchronization-start module 420 initiates data synchronization by instructing the general synchronization module 425 (described below) to begin execution of its routines. It will be appreciated that communication with the synchronization agent 124 preferably initiates from within the LAN 110, because the typical firewall 114 prevents in-bound communications and allows out-bound communications.
The general synchronization module 425 includes routines for receiving version information 148 for modified versions from the synchronization agent 124 (FIG. 1), and routines for examining the version information 255 or 150 against a last synchronization signature 435 (such as a last synchronization date and time) to determine which versions have been modified. The general synchronization module 425 further includes routines for examining the version information 148 and the version information 255 or 150 to determine if one or both versions of a particular workspace element or workspace element folder have been modified.
Further, the general synchronization module 425 includes routines for performing an appropriate synchronizing responsive action. Appropriate synchronizing responsive actions may include, if only one version of a workspace element in workspace data 136 or 116 has been modified, then forwarding the modified version (as the preferred version) to the other store(s) or determining and forwarding only the changes made. Computing the changes made may be performed by examining the current status against the previous status as of the last synchronization or by comparing the two versions. It will be appreciated that no content-based review of the changes is needed. It will be appreciated that one store preferably forwards only the changes to the other store for optimizing use of processor power and minimizing the data communications across the communications channel 108 or 104.
Other appropriate synchronizing responsive actions may include, if two versions of a workspace element have been modified independently, then instructing the content-based synchronization module 430 (described below) to execute its routines. That is, if two versions of the same workspace element have been modified independently, then a content-based review of the changes is preferable. Upon completion of the data synchronization, the general synchronization module 425 updates the last synchronization signature 435.
The content-based synchronization module 430 includes routines for reconciling two or more modified versions of a workspace element. For example, if a user has independently modified the original and the copy of a workspace element since the last synchronization, then the content-based synchronization module 430 determines an appropriate responsive action. The content-based synchronization module 430 may request the user to select a preferred one of the modified versions or may respond based on preset preferences, i.e., by storing both versions in both stores or preferably by integrating the modified versions into a single preferred version which replaces each modified version at both stores.
The content-based synchronization module 430 examines the changes made to each version and determines if conflicts exist. When implementing version integration, a conflict may arise if inconsistent modifications such as deleting a paragraph in one version and modifying the same paragraph in the other version have been made. If a conflict exists, then the content-based synchronization module 430 attempts to reconcile the conflict, e.g., by requesting user selection or by storing both versions at both stores. Otherwise, if no conflict exists, then the content-based synchronization module 430 integrates the changes to each of the versions and updates the version information 148, 150 or 255 accordingly.
FIG. 5 is a block diagram illustrating details of the synchronization agent 124, which includes a communications module 505 (similar to the communications module 405 described above with reference to FIG. 4) and a general synchronization module 515 (similar to the general synchronization module 425 described above also with reference to FIG. 4).
The communications module 505 includes routines for compressing data, and routines for communicating via the communications channel 108 with the base system 146 or via the communications channel 104 with the base system 118. The communications module 505 may further include routines for establishing a secure communications channel through the global firewall 112 and through the LAN firewall 114 with the communications module 405.
Similar to the general synchronization module 425, the general synchronization module 515 includes routines for examining the version information 148 and the last synchronization signature 435 (FIG. 4) to determine which versions have been modified and the changes made. It will be appreciated that the general synchronization module 515 may maintain its own last synchronization signature 435 copy (not shown) or may request the last synchronization signature 435 from the base system 146 or 118. The general synchronization module 515 further includes routines for forwarding workspace data 120 determined to be modified to the general synchronization module 425, and routines for receiving preferred versions of workspace elements of workspace data 136 or 116 or just the changes from the general synchronization module 425.
FIG. 6 illustrates an example bookmark workspace element in the global format. The global translator 122 incorporates all the information needed by both formats (Format A and Format B) to create the Global Format. For example, if a bookmark in Format A needs elements X, Y and Z and a bookmark in Format B needs elements W, X and Y, the global translator 122 incorporates elements W, X, Y and Z to create a bookmark in the Global Format. Further, the global translator 122 incorporates the information which is needed by the synchronization means such as the last modified date. Accordingly, a bookmark in the Global Format includes a user identification (ID) 605, an entry ID 610, a parent ID 615, a folder ID flag 620, a name 625, a description 630, the Uniform Resource Locator (URL) 635, the position 640, a deleted ID flag 645, a last modified date 650, a created date 655 and a separation ID flag 660.
FIG. 7 is a flowchart illustrating a method 700 for using a global translator 122 to synchronize multiple copies of a workspace element in a secure network 100. Method 700 begins with the user interface module 410 in step 705 enabling a user to select workspace elements of workspace data 136 and 118 for the synchronization means to synchronize. The locator modules 415 in step 710 identify the memory locations of the workspace elements in workspace data 136 and 116 and the corresponding memory locations in workspace data 120. If a selected workspace element does not have a corresponding memory location, such as in the case of adding a new workspace element to the global server 106, then one is selected. The selected memory location may be a preexisting workspace element or a new workspace element. As stated above, workspace element memory location identification may be implemented using intelligent software or dialogue boxes. The general synchronization module 425 and general synchronization module 515 in step 715 set the previous status of the workspace elements equal to the null set. Setting the previous status to the null set indicates that all information of the workspace element has been added.
The synchronization-start module 420 in step 720 determines whether predetermined criteria have been met which indicate that synchronization of the workspace elements selected in step 705 should start. If not, then the synchronization-start module 420 in step 725 waits and loops back to step 720. Otherwise, the communications module 405 and communications module 505 in step 730 establish a secure communications channel therebetween.
The general synchronization module 425 and the general synchronization module 515 in step 735 determine whether any workspace elements have been modified. That is, the general synchronization module 425 in step 740 examines the version information 255 or 150 of each selected workspace element in the workspace data 136 or 116 against the last synchronization signature 435 to locate modified workspace elements. This comparison may include comparing the date of last modification with the date of last synchronization, or may include a comparison between the current status and the previous status as of the last interaction. Similarly, the general synchronization module 515 examines the version information 148 of each corresponding workspace element in workspace data 120 and the last synchronization signature 435 to locate modified workspace elements.
If in step 735 no modified workspace elements or folders are located, then the general synchronization modules 425 and 515 in step 760 update the last synchronization signature 435 and method 700 ends. Otherwise, the general synchronization module 425 in step 740 determines whether more than one version of a workspace element has been modified since the last synchronization.
If only one version has been modified, then the corresponding general synchronization module 425 or 515 in step 745 determines the changes made. As stated above, determining the changes made may be implemented by comparing the current status of the workspace element against the previous status of the workspace element as of the last interaction therebetween. If the changes were made only to the version in the workspace data 120, then the global translator 122 in step 750 translates the changes to the format used by the other store, and the general synchronization module 515 in step 755 forwards the translated changes to the general synchronization module 425 for updating the outdated workspace element in the workspace data 136 or 116. If the updated version is a workspace element in the workspace data 136 or 116, then the general synchronization module 425 sends the changes to the updated version to the global translator 122 for translation and then to the general synchronization module 515 for updating the outdated workspace element in the workspace data 120. The general synchronization module 425 and the general synchronization module 515 in step 757 update the previous state of to reflect the current state as of this interaction. Method 700 then returns to step 735.
If the general synchronization module 425 in step 740 determines that multiple versions have been modified, then the general synchronization module 425 in step 765 computes the changes to each version and in step 770 instructs the content-based synchronization module 430 to examine content to determine if any conflicts exist. For example, the content-based synchronization module 430 may determine that a conflict exists if a user deletes a paragraph in one version and modifies the same paragraph in another version. The content-based synchronization module 430 may determine that a conflict does not exist if a user deletes different paragraphs in each version. If no conflict is found, then method 700 jumps to step 750 for translating and forwarding the changes in each version to the other store. However, if a conflict is found, then the content-based synchronization module 430 in step 775 reconciles the modified versions. As stated above, reconciliation may include requesting instructions from the user or based on preselected preferences performing responsive actions such as storing both versions at both stores. Method 700 then proceeds to step 750.
It will be appreciated that in step 710 new workspace elements and preexisting workspace elements to which new workspace elements will be merged are set to "modified" and the previous status is set to the null set. Thus, the general synchronization module 425 in step 740 will determine that more that one version has been modified and the content-based synchronization module 430 in step 770 will determine that no conflict exists. The changes in each will be translated and forwarded to the other store. Accordingly, the two versions will be effectively merged and stored at each store.
For example, if a first bookmark folder was created by the web browser 152 on the desktop computer 134, a second folder was created by a web browser (not shown) on the remote terminal 102, no preexisting folder existed on the global server 106 and the user selected each of these folders for synchronization, then the synchronization means will effectively merge the first and second folders. That is, the general synchronization module 425 on the desktop computer 134 will determine that the first folder has been modified and the previous status is equal to the null set. The general synchronization module 425 will determine and send the changes, i.e., all the workspace elements in the first folder, to a new global folder on the global server 106. Similarly, the general synchronization module 425 on the remote terminal 102 will determine that, as of its last interaction, the previous status of each of the second and the global folders is the null set. The general synchronization module 425 will instruct the content-based synchronization module 430 to examine the changes made to each folder to determine whether a conflict exists. Since no conflicts will exist, the general synchronization module 425 will forward the changes to the global folder and the general synchronization module 515 will forward its changes to the second store, thereby merging the workspace elements of the first and second folders in the global and second folders. The general synchronization module 515 will inform the general synchronization module 425 that the global folder has been modified relative to the last interaction, and will forward the new changes to the first folder. Thus, the first and second folders will be merged and stored at each store.
For a second example, the user may select an exemplary document in the LAN 110 to be synchronized. The general synchronization module 425 will forward the document to the global server 106. Similarly, the user may select the same document for synchronization on the remote terminal 102. The general synchronization module 515 will forward the document to the remote terminal 102. If changes were made to the documents independently, then the content-based synchronization module 430 will examine the content of the documents to determine if a conflict exists. If no conflict exists, then as described above, the general synchronization modules 425 and 515 will merge the documents. Otherwise, if a conflict does exist, the content-based synchronization module 430 will reconcile the changes and then the general synchronization modules 425 and 515 will forward the reconciled changes to each other.
FIG. 8 is a block diagram illustrating a computer network 800, comprising a Local Area Network (LAN) 810 coupled via a communications channel 815 to a computer network 820 such as the Internet. The computer network 820 is in turn coupled via a communications channel 825 to a global server 830, via a communications channel 835 to a remote terminal 805, and via a communications channel 893 to an Internet Service Provider (ISP) mail server 894. The ISP mail server 894 is in turn coupled to another client 897. The global server 830 is protected by a global firewall 880, and the LAN 810 is protected by a LAN firewall 870.
The LAN 810 includes a network server 845 coupling the LAN firewall 870 via a system bus 855 to a client 840 and to a mail server 850. The mail server 850 receives and stores in one or more folder structures client electronic mail 875 (e-mails) from the computer network 820 and addressed to the client 840. The client 840 includes an e-mail synchronization system 860 for downloading client e-mails 875 from the mail server 850 and storing them locally in one or more folder structures as "downloaded e-mails 865." To communicate therebetween, the mail server 850 and the e-mail engine 965 must both use the same transmission protocol such as the third version of the Post Office Protocol (POP3), the Vendor-Independent Messaging (VIM) protocol developed by the Lotus Development Corporation, or the Messaging Application Program Interface (MAPI) protocol developed by the Microsoft Corporation. Each e-mail in the LAN 810 is stored in a predetermined format, referred to as Format A, which is determined by the e-mail engine 965 (FIG. 9) on the LAN 810 that downloaded it.
It will be appreciated that, after being downloaded, the client e-mails 875 corresponding to the downloaded e-mails 865 may be deleted from the mail server 850. The e-mail synchronization system 860 further synchronizes the downloaded e-mails 865, the client e-mails 875 or possibly only the e-mails of a specific folder structure (e.g., a user's unanswered mail folder or joke folder) with the global server 835. The e-mail synchronization system 860 is described in greater detail below with reference to FIG. 9.
The ISP mail server 894 and the client 897 operate in a similar manner to the mail server 850 and the client 840. Generally, the ISP mail server 894 receives e-mails from the computer network 820 which are addressed to the client 897, and stores them locally in one or more folder structures as "client e-mails 896." The e-mail synchronization system 898 of the client 897 uses an e-mail engine 965 (FIG. 9) to download client e-mails 896 and store them locally in one or more folder structures as "downloaded e-mails 899." The e-mail engine 965 of the client 897 stores the e-mails in Format B, which may be different than Format A. The e-mail synchronization system 898 then synchronizes the client e-mails 896, the downloaded e-mails 899 or possibly the e-mails of specific folder structures with the global server 830.
Each e-mail, whether stored on the mail server 850, on the client 840, on the mail server 894 (described below) or on the client 897 (described below), may include a source identifier (e.g., a source address), a creation date, a date received by the mail server 850 or 894, and a date when downloaded to the client 840 or 897. The date when downloaded to the client 840 or 897 may be the date when the e-mail synchronization system 860 or 898 downloads the client e-mails 875 or 896 for synchronization with the global server 835.
The global server 835 includes a synchronization agent 885 for cooperating with the e-mail synchronization system 860 or the e-mail synchronization system 898 to synchronize electronic mail therebetween. Based on its configuration, the e-mail synchronization system 860 or 898 translates and sends to the synchronization agent 885 either a copy or the original (i.e., not maintaining a copy) of a downloaded e-mail 865 or 899 or a client e-mail 875 or 896. The global server 835 stores the copies or originals of the downloaded e-mails 865 or 899 in one or more folder structures as "downloaded e-mails 832," and stores the copies or originals of the client e-mails 875 or 896 in one or more folder structures as "client e-mails 895." The global server 835 stores the e-mails in a global format, which may be the same as Format A or Format B or may include the combined elements of both formats. It will be appreciated that the e-mail synchronization system 860 or 898 may send and the global server 835 may store the client e-mails 875 or 896 and the downloaded e-mails 865 or 897 together without distinction. Further, the client e-mails 875 or 896 and the downloaded e-mails 865 of corresponding specific folders together without distinction. Still further, the global server 835 may be configured to store the e-mails of client 840 and client 897 together without distinction. The global server 835 further includes a web engine interface 890 enabling HTTP-based web engine access to the contents therein including access to the client e-mails 895, the downloaded e-mails 832 and the folder structures in which they are stored.
As described in greater detail above with reference to FIG. 4 and below with reference to FIG. 10, the e-mail synchronization system 860 preferably initiates and controls data synchronization. Other components and functions of the global server 835 are also described therein.
The remote terminal 1505 includes a web engine 833 for reading internet files including e-mails. The remote terminal 102 may include a smart telephone, a Personal Data Assistant (PDA) such as the PalmPilot system by the U.S. Robotics, Inc., a laptop computer, etc. Thus, so long as a user of the remote terminal 1505 can be identified and can access the global server 835, the user can access the e-mails 895 and 897. Further, so long as the client e-mails 895 and 832 are synchronized with the e-mails 865, 875, 896 and 899, the user can access all e-mails which are addressed to the client 840 and to the client 897.
FIG. 9 is a block diagram illustrating details of client 900, which exemplifies client 840 or client 897. Client 900 includes a Central Processing Unit (CPU) 905 such as an Intel Pentium® microprocessor or a Motorola Power PC® microprocessor. An input device 910 such as a keyboard and mouse and an output device 915 such as a Cathode Ray Tube (CRT) display are coupled via a signal bus 920 to CPU 905. A communications interface 925 (such as an Ethernet port), a data storage device 930 (such as a magnetic disk), and Random-Access Memory (RAM) 935 are further coupled via signal bus 920 to the CPU 905. The communications interface 925 is coupled to the signal bus 855 (FIG. 8).
An operating system 950 includes a program for controlling processing by the CPU 905, and is typically stored in the data storage device 930 and loaded into the RAM 935 (as illustrated) for execution. RAM 935 stores an e-mail synchronization system 953 (which exemplifies the e-mail synchronization system 860 or the e-mail synchronization system 898) having means for downloading client e-mails 875 or 896, means for reading downloaded e-mails 943 (which exemplifies downloaded e-mails 865 or 899), means for synchronizing e-mails 865, 875, 896 or 899 (which have been downloaded) with the global server 835 and means for synchronizing the e-mail of specific folder structures. For example, the e-mail synchronization system 953 includes a web engine 955 for communicating with web servers. The web engine 955 includes an e-mail module 960 for reading and writing electronic mail. The e-mail synchronization system 953 further includes an e-mail engine 965 for communicating with the mail server 850 or 894 to download, read and write e-mails. The e-mail engine 965 communicates using a conventional protocol such as POP3, VIM or MAPI. Downloaded e-mails 943 are stored in data storage device 930 (FIG. 9). The e-mail engine 965 also provides access to an address book 945 containing e-mail address entries, which is also stored in the data storage device 930.
The e-mail synchronization system 953 further includes a base system 970 for translating e-mails from Format A or Format B to the global format, and for initiating and controlling e-mail synchronization with the global server 835. Translation may include containing mail-server-formatted e-mail in HTTP packets. The base system 970 is described in greater detail with reference to FIG. 10 and in the cross-referenced patent application.
It will be appreciated that means for retrieving e-mails may be interpreted to include either the operating system 950 when retrieving downloaded e-mails 865 or 899, the e-mail engine 965 when retrieving client e-mails 875 or 896, the e-mail module 960 of the web engine 955 when retrieving e-mails from a site in the computer network 820, or combinations thereof.
FIG. 10 is a block diagram illustrating details of the base system 970. Base system 970 includes a communications module 1005, a user interface module 1010, locator modules 1015, a synchronization-start ("synch-start") module 1020 and an e-mail synchronization module 1030. For simplicity, each module is illustrated as communicating with one another via a signal bus 1030.
The communications module 1005 includes routines for compressing data and routines for establishing a communications link via the communications interface 925 (FIG. 9) with the synchronization agent 885 (FIG. 8). The communications module 1005 may further include routines for applying Secure Socket Layer (SSL) technology and user identification and authentication techniques (i.e., digital certificates) to establish a secure communication channel through the global firewall 880. Because synchronization is initiated from within the firewall and uses commonly enabled protocols such as HyperText Transfer Protocol (HTTP), the typical firewall which prevents in-bound communications in general and some outbound protocols does not act as an impediment to e-mail synchronization. Examples of communications modules 1005 may include TCP/IP stacks or the AppleTalk® protocol.
The user interface module 1010 includes routines for communicating with a user, and may include a conventional Graphical User Interface (GUI). The user interface module 1010 cooperates with the other system components as described herein.
The locator modules 1015 include routines for identifying the memory locations of e-mails in the FIG. 8 LAN 810 (e.g., e-mails 875 in the mail server 850 and e-mails 865 in the client 840), the memory locations of e-mails 896 in the ISP mail server 894, the memory locations of e-mails 899 in the client 897, the memory locations of e-mails in the global server 835 (e.g., client e-mails 895 and downloaded e-mails 832) and the memory locations of the folder structures in which the e-mails are stored. E-mail memory location identification may be implemented using intelligent software, i.e., preset memory addresses or the system's registry, or using dialogue boxes to query a user. It will be appreciated that the locator modules 1015 may perform e-mail location identification upon system boot-up or after each communication with the global server 835 to maintain updated memory addresses.
The synchronization-start module 1020 includes routines for determining when to initiate e-mail synchronization. For example, the synchronization-start module 1020 may initiate e-mail synchronization upon user request, at a particular time of day, after a predetermined time period passes, after receiving a predetermined number of e-mails, after a user action such as user log-off or upon like criteria. The synchronization-start module 1020 initiates e-mail synchronization by instructing the e-mail synchronization module 1025 (described below) to begin execution of its routines. It will be appreciated that communication with the synchronization agent 885 preferably initiates from within the LAN 810, because a security system such as the typical firewall 870 prevents inbound communications and allows out-bound communications. The synch-start module 1020 may instruct the communications module 1005 to establish the communications link with the synchronization agent 885 of the global server 835.
The e-mail synchronization module 1025 includes routines for instructing the e-mail engine 965 (FIG. 9) to retrieve the client e-mails 875 or 896 from the mail server 850 or 894 or from specific folders on the mail server 850 or 894. The e-mail synchronization module 1025 also includes routines for storing the retrieved e-mails in one or more folder structures as downloaded e-mails 865 or 899. The e-mail engine 965 may include means for identifying a transmission protocol also known by the mail server 850 or 894. For example, the e-mail engine 965 may request configuration information from the mail server 850 or 894 indicating the protocol, e.g., POP3, being used thereby. Accordingly, the e-mail engine 965 implements the identified protocol when downloading the e-mails.
The e-mail synchronization module 1025 further includes routines for comparing the receipt date of each downloaded e-mail 865 or 899 against a last synchronization signature 1035 (such as a last synchronization date and time) to determine which e-mails have not been sent to the global server 835. It will be appreciated that, in an embodiment which deletes client e-mails 875 or 896 after being downloaded from the mail server 850 or 894, the e-mail synchronization module 1025 need not perform a comparison test on the client e-mails 875 or 896 downloaded during synchronization. These client e-mails 875 or 896 in this embodiment have inherently not been sent.
The e-mail synchronization module 1025 still further includes routines for performing an appropriate synchronizing responsive action. Appropriate synchronizing responsive actions may include instructing the communications module 1005 to establish a communications link with the synchronization agent 885 of the global server 835, sending copies of each e-mail to the global server 835, redirecting (i.e., sending without maintaining a copy) only the client e-mails 875 or 896 to the global server 835, or redirecting the downloaded e-mails 865 or 899 and the client e-mails 875 or 896 to the global server 835. To send a copy or an original of an e-mail, the e-mail synchronization module 1025 includes a translator 1040 for translating the e-mail from Format A or Format B to the global format. The e-mail synchronization module 1025 then instructs the e-mail module 960 of the web engine 955 to send the translated e-mails to the global server 835.
E-mail synchronization may include synchronization of other information corresponding to electronic mail. For example, the e-mail synchronization module 1025 may include routines for examining and synchronizing the address book 945 with an address book 1130 (FIG. 11) on the global server 835. Examination and synchronization of address book entries are performed as described below with reference to FIGS. 1-7. Generally, the e-mail synchronization module 1025 may examine version information indicating the date and time of last modification of the address book 945 on the client 900 and version information indicating the date and time of last synchronization of the address book 1130 (FIG. 11) on the global server 835. Based on the examination, the e-mail synchronization module 1025 performs an appropriate responsive synchronizing action such as sending the updated e-mail address entries to the other store. The e-mail synchronization module 1025 may include a general synchronization module 425 (FIG. 4) and a content-based synchronization module 430 (FIG. 4).
FIG. 11 is a block diagram illustrating details of the global server 835, which includes a CPU 1105, a communications interface 1110, a data storage device 1120 and RAM 1125, each coupled to a signal bus 1115. The communications interface 1110 is coupled via the global firewall 880 (FIG. 8) to the communications channel 825.
An operating system 1135 includes a program for controlling processing by the CPU 1105, and is typically stored in the data storage device 1120 and loaded into the RAM 1125 (as illustrated) for execution. A web engine interface 890 is a program for communicating with web engine 833 or web engine 955 and to provide access to predetermined contents which may include client e-mails 895, downloaded e-mails 832 and address book 1130. The web engine interface 890 includes an e-mail module interface 1140 for communicating with e-mail module 960 or e-mail module 1355 (FIG. 13) and to provide e-mail reading and writing functions.
The synchronization agent 885 as best shown in FIG. 12 is also stored in the data storage device 1120 and loaded into the RAM 1125 for execution. The synchronization agent 885 communicates with the e-mail synchronization module 1025 to synchronize e-mails, the e-mail of specific folder structures and possibly to synchronize the address book 945. The synchronization agent 885 is described in greater detail below with reference to FIG. 12 and in the cross-referenced patent application.
FIG. 12 is a block diagram illustrating details of the synchronization agent 885, which includes a communications module 1205 (similar to the communications module 1005 described above with reference to FIG. 10) and an e-mail synchronization module 1210 (similar to the e-mail synchronization module 1025 also described above with reference to FIG. 10).
The communications module 1205 includes routines for compressing data, and routines for communicating via the computer network 820 (FIG. 8) with the communications module 1005 (FIG. 10). The communications module 1205 may further include routines for establishing a secure communications channel through the global firewall 880 and through the LAN firewall 870 with the communications module 1005.
Similar to the e-mail synchronization module 1025 (FIG. 10), the e-mail synchronization module 1210 includes routines for examining information to determine whether any have been added or modified and not synchronized with the client 840 (FIG. 8). Accordingly, the e-mail synchronization module 1210 may determine whether any addresses in the address book 1130 (FIG. 11) are to be copied and sent to a client 900. Further, if the system 1500 synchronizes e-mails at each of the client sites, then the e-mail synchronization module 1210 also determines whether any of the e-mails 895 or 832 have been added or modified and not synchronized with a client 900.
It will be appreciated that the e-mail synchronization module 1210 may maintain its own last synchronization signature 1035 copy (not shown) or may request the last synchronization signature 1035 from the base system 970. The e-mail synchronization module 1210 further includes routines for sending the information determined to be modified or just the changes to the e-mail synchronization module 1025.
FIG. 13 is a block diagram illustrating details of the remote terminal 1505. The remote terminal 1505 includes a Central Processing Unit (CPU) 1305 such as an Intel Pentium® microprocessor or a Motorola Power PC® microprocessor. An input device 1310 such as a keyboard and mouse and an output device 1315 such as a Cathode Ray Tube (CRT) display are coupled via a signal bus 1320 to CPU 1305. A communications interface 1325 (such as an Ethernet port), a data storage device 1330 (such as a magnetic disk), and Random-Access Memory (RAM) 1335 are further coupled via signal bus 1320 to the CPU 1305. The communications interface 1325 is coupled to the signal bus 835 (FIG. 8).
An operating system 1350 includes a program for controlling processing by the CPU 1305, and is typically stored in the data storage device 1330 and loaded into the RAM 1335 (as illustrated) for execution. The web engine 833 is also typically stored in the data storage device 1330 and loaded into the RAM 1335 (as illustrated) for execution. The web engine 833 includes an e-mail module 1355 for reading and writing electronic mail. After the remote terminal 1505 connects with the global server 835, the e-mail module 1355 communicates with the e-mail module interface 1140 to select and to download client e-mails 895 or downloaded e-mails 832. The e-mail module 1355 stores the e-mails downloaded from the global server 835 to the data storage device 1330 as "downloaded e-mails 1340." Alternatively, the e-mail module 1355 may store the e-mails 1340 only in RAM 1335 so that at the end of the session copies of the e-mails 1340 do not remain at the remote terminal 1505. The e-mail module 1355 enables the user to read, reply, forward, redirect, etc. the e-mails 1340. Similarly, the web engine 833 may enable access to the address book 945 so that the user can access his or her e-mail address entries otherwise stored only in the LAN 810.
FIG. 14 is a flowchart illustrating a method 1400 for synchronizing e-mails in a computer network 1500. Method 1400 begins with the mail server 850 or 894 in step 1405 receiving e-mails addressed to a client 840 or 897. The mail server 850 or 894 in step 1410 stores the received e-mails in one or more folder structures as client e-mails 875 or in one or more folder structures as client e-mails 896 (FIG. 8). The e-mail engine 965 in step 1415 enables a user to select client e-mails 875 or 894 to download from the mail server 850 or 896. If e-mails are selected, then the e-mail engine 965 in step 1420 downloads the selected client e-mails 875 or 894 and stores them in one or more folder structures as downloaded e-mails 865 or in one or more folder structures as downloaded e-mails 899 (FIG. 8). If in step 1415 e-mails are not selected, then method 1400 jumps to step 1425.
In step 1425, the synchronization-start module 1020 determines whether predetermined start criteria have been met indicating that it is time for e-mail synchronization. As stated above with reference to FIG. 4, the predetermined start criteria may be satisfied after a particular time period has passed, after receiving a particular number of e-mails, at a particular time of day, after a predetermined event, etc. If it is not time to synchronize, then the synchronization-start module 1020 in step 1430 waits. Otherwise, if it is time to synchronize, the e-mail synchronization module 1025 in step 1435 instructs the e-mail engine 965 to download client e-mails 875 or 896 or client e-mails 875 or 896 of specific folder structures.
The e-mail synchronization module 1025 in step 1440 determines whether any of the downloaded e-mails 865 or 899 (which include the client e-mails 875 or 896 recently downloaded) have not been sent to the global server 835. This comparison may be performed by examining the date and time the e-mail was received against a last synchronization signature 1035 which indicates the date and time of last synchronization. For example, if an e-mail was received after the date and time of last synchronization, the e-mail has not been sent. It will be appreciated that, in an embodiment which deletes client e-mails 875 and 896 from the mail server 850 or 894 after downloading them to the client 840 or 897, the e-mail engine 965 can automatically conclude that these e-mails have not been sent to the global server 835.
If all e-mails (intended for synchronization) have been sent to the global server 835, then method 1400 ends. Otherwise, if at least one e-mail has not been sent, then the e-mail synchronization module 1025 in step 1445 uses the translator 1040 to translate unsent e-mails 865 or 899 from Format A or Format B to the global format. The e-mail synchronization module 1025 in step 1450 instructs the web engine 955 to send the translated e-mail to the global server 835 for the web engine interface 890 to store. Method 1400 then ends.
FIG. 15 is a flowchart illustrating a method 1500 for accessing e-mails from the global server 835. Method 1500 begins with the e-mail synchronization module 1210 in step 1505 receiving e-mails from the client 840 or 897. The e-mail synchronization module 1210 in step 1510 stores the e-mails in the data storage device 1120 in one or more folder structures as client e-mails 895 and downloaded e-mails 832. The e-mail engine interface 890 in step 1515 uses HTML to enable e-mail module access to selected contents of the global server 835. Access to the selected contents is described in greater detail below with reference to the FIGS. 1-7.
The foregoing description of the preferred embodiments of the invention is by way of example only, and other variations of the above-described embodiments and methods are provided by the present invention. For example, although the global server 106 is illustrated as a single device, the global server 106 may include several computers networked together. Components of this invention may be implemented using a programmed general-purpose digital computer, using application specific integrated circuits, or using a network of interconnected conventional components and circuits. The embodiments described herein have been presented for purposes of illustration and are not intended to be exhaustive or limiting. Many variations and modifications are possible in light of the foregoing teaching. The system is limited only by the following claims.
Riggins, Mark D., Mendez, Daniel J., Wagle, Prasad, Ying, Christine C.
| Patent | Priority | Assignee | Title |
| 10033702, | Aug 05 2015 | INTRALINKS, INC | Systems and methods of secure data exchange |
| 10055090, | Mar 19 2002 | Meta Platforms, Inc | Constraining display motion in display navigation |
| 10089376, | Dec 29 2004 | Seven Networks, LLC | Database synchronization via a mobile network |
| 10116583, | Mar 14 2013 | OMNISSA, LLC | Controlling resources used by computing devices |
| 10116662, | Apr 12 2013 | OMNISSA, LLC | On-demand security policy activation |
| 10142316, | Apr 27 2012 | INTRALINKS, INC | Computerized method and system for managing an email input facility in a networked secure collaborative exchange environment |
| 10168921, | Oct 10 2007 | United Services Automobile Association (USAA); UNITED SERVICES AUTOMOBILE ASSOCIATION USAA | Systems and methods for storing time-series data |
| 10243932, | Dec 06 2012 | OMNISSA, LLC | Systems and methods for controlling email access |
| 10257180, | Sep 23 2013 | OMNISSA, LLC | Securely authorizing access to remote resources |
| 10257194, | Feb 14 2012 | OMNISSA, LLC | Distribution of variably secure resources in a networked environment |
| 10257233, | Apr 18 2005 | BlackBerry Limited | Method for providing wireless application privilege management |
| 10263899, | Apr 10 2012 | Seven Networks, LLC | 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 |
| 10303872, | May 02 2013 | OMNISSA, LLC | Location based configuration profile toggling |
| 10346937, | Nov 14 2013 | Intralinks, Inc. | Litigation support in cloud-hosted file sharing and collaboration |
| 10356095, | Apr 27 2012 | Intralinks, Inc. | Email effectivity facilty in a networked secure collaborative exchange environment |
| 10365785, | Mar 19 2002 | Meta Platforms, Inc | Constraining display motion in display navigation |
| 10404615, | Feb 14 2012 | OMNISSA, LLC | Controlling distribution of resources on a network |
| 10409829, | Feb 01 2002 | Microsoft Technology Licensing, LLC | Method and system for managing changes to a contact database |
| 10462189, | Apr 18 2005 | BlackBerry Limited | Method for providing wireless application privilege management |
| 10476865, | Oct 26 2001 | BlackBerry Limited | System and method for controlling configuration settings for mobile communication devices and services |
| 10521800, | Sep 30 2003 | WORKDAY, INC | Method for automatic creation and configuration of license models and policies |
| 10560459, | Apr 21 2005 | Seven Networks, LLC | Multiple data store authentication |
| 10666591, | Dec 06 2012 | OMNISSA, LLC | Systems and methods for controlling email access |
| 10681017, | Dec 06 2012 | OMNISSA, LLC | Systems and methods for controlling email access |
| 10686842, | Apr 18 2005 | BlackBerry Limited | Method for providing wireless application privilege management |
| 10785228, | Apr 12 2013 | OMNISSA, LLC | On-demand security policy activation |
| 10798076, | Sep 23 2013 | OMNISSA, LLC | Securely authorizing access to remote resources |
| 10824757, | Jun 06 2013 | OMNISSA, LLC | Social media and data sharing controls |
| 10838972, | Mar 13 2014 | Microsoft Technology Licensing, LLC | Storing service items in association with views |
| 10951541, | Feb 14 2012 | OMNISSA, LLC | Controlling distribution of resources on a network |
| 10965718, | Apr 18 2005 | BlackBerry Limited | Method for providing wireless application privilege management |
| 10979435, | Apr 21 2005 | Seven Networks, LLC | Multiple data store authentication |
| 11050719, | Dec 06 2012 | OMNISSA, LLC | Systems and methods for controlling email access |
| 11082355, | Feb 14 2012 | OMNISSA, LLC | Controllng distribution of resources in a network |
| 11157915, | Sep 30 2003 | WORKDAY, INC | Automatic creation and configuration of license models and policies |
| 11204993, | May 02 2013 | OMNISSA, LLC | Location-based configuration profile toggling |
| 11212290, | Apr 21 2005 | Seven Networks, LLC | Multiple data store authentication |
| 11226947, | Oct 10 2007 | United Services Automobile Association (USAA) | Systems and methods for storing time-series data |
| 11295360, | Apr 21 2005 | Seven Networks, LLC | Multiple data store authentication |
| 11310219, | Oct 26 2001 | BlackBerry Limited | System and method for controlling configuration settings for mobile communication devices and services |
| 11430029, | Apr 21 2005 | Seven Networks, LLC | Multiple data store authentication |
| 11483252, | Feb 14 2012 | OMNISSA, LLC | Controlling distribution of resources on a network |
| 11563707, | Mar 05 2015 | Microsoft Technology Licensing, LLC | Tracking electronic mail messages in a separate computing system |
| 11570160, | Sep 23 2013 | OMNISSA, LLC | Securely authorizing access to remote resources |
| 11651400, | Apr 21 2005 | Seven Networks, LLC | Multiple data store authentication |
| 11694241, | Apr 21 2005 | Seven Networks, LLC | Multiple data store authentication |
| 11734245, | Oct 10 2007 | United Services Automobile Association (USAA) | Systems and methods for storing time-series data |
| 11824644, | Mar 14 2013 | OMNISSA, LLC | Controlling electronically communicated resources |
| 11902281, | Apr 12 2013 | OMNISSA, LLC | On-demand security policy activation |
| 11915281, | Apr 21 2005 | Seven Networks, LLC | Multiple data store authentication |
| 11956280, | Apr 18 2005 | BlackBerry Limited | Method for providing wireless application privilege management |
| 11962510, | Jun 02 2013 | OMNISSA, LLC | Resource watermarking and management |
| 12081452, | Feb 14 2012 | OMNISSA, LLC | Controlling distribution of resources in a network |
| 6023708, | May 29 1997 | Malikie Innovations Limited | System and method for using a global translator to synchronize workspace elements across a network |
| 6125446, | Aug 29 1997 | Qualcomm Incorporated | Computer architecture with automatic disabling of hardware/software features using satellite positioning data |
| 6131096, | Oct 05 1998 | BlackBerry Limited | System and method for updating a remote database in a network |
| 6304896, | Sep 29 1997 | Murata Kikai Kabushiki Kaisha | System and method for denying connection to electronic mailbox if mailbox is empty |
| 6370566, | Apr 10 1998 | Microsoft Technology Licensing, LLC | Generating meeting requests and group scheduling from a mobile device |
| 6389457, | May 29 1998 | Malikie Innovations Limited | System and method for pushing information from a host system to a mobile data communication device |
| 6401112, | Jan 29 1997 | ACCESS CO , LTD | Method and apparatus for synchronizing an Email client on a portable computer system with an Email client on a desktop computer |
| 6401113, | May 29 1998 | Malikie Innovations Limited | System and method for pushing information from a host system to a mobile data communication device |
| 6438584, | Mar 07 2000 | Letter Services, Inc.; LETTER SERVICES, INC | Automatic generation of graphically-composed correspondence via a text email-interface |
| 6438585, | May 29 1998 | Malikie Innovations Limited | System and method for redirecting message attachments between a host system and a mobile data communication device |
| 6446115, | Mar 07 2000 | Letter Services, Inc.; LETTER SERVICES, INC | Automatic generation of graphically-composed correspondence via a text email interface |
| 6449634, | Jan 29 1999 | ZETA GLOBAL CORP | Method and system for remotely sensing the file formats processed by an E-mail client |
| 6459360, | Sep 19 1997 | HELFERICH PATENT LICENSING LLC | Networks, communication systems, transmitting and receiving devices and methods for transmitting, receiving, and erasing stored information |
| 6462646, | Sep 19 1997 | HELFERICH PATENT LICENSING LLC | Transmitting and receiving devices and methods for transmitting data to and receiving data from a communication system |
| 6463463, | May 29 1998 | Malikie Innovations Limited | System and method for pushing calendar event messages from a host system to a mobile data communication device |
| 6466951, | Feb 10 1999 | CLUSTER, LLC; Optis Wireless Technology, LLC | Data base synchronizing system with at least two host databases and a remote database |
| 6526413, | Sep 28 1999 | Microsoft Technology Licensing, LLC | Architecture for a hierarchical folder structure in hand-held computers |
| 6606649, | Sep 28 1999 | Microsoft Technology Licensing, LLC | Application programming interface functions for supporting an improved message store for hand-held computers |
| 6618710, | Jul 07 1999 | International Business Machines Corporation | Apparatus and method for intelligent routing of electronic messages to pagers and computers |
| 6636733, | Sep 19 1997 | HELFERICH PATENT LICENSING LLC | Wireless messaging method |
| 6636897, | Sep 28 1999 | Microsoft Technology Licensing, LLC | Selective information subset synchronization based on single user action |
| 6654779, | Apr 14 1999 | First Data Resources | System and method for electronic mail (e-mail) address management |
| 6671757, | Jan 26 2000 | Synchronoss Technologies, Inc | Data transfer and synchronization system |
| 6684239, | May 16 2000 | RPX Corporation | System and method for automatically publishing electronic mail messages on the internet |
| 6694336, | Jan 25 2000 | Synchronoss Technologies, Inc | Data transfer and synchronization system |
| 6696921, | Sep 19 1997 | HELFERICH PATENT LICENSING LLC | Transmitting and receiving devices and methods for transmitting data to and receiving data from a communications system |
| 6701378, | May 29 1998 | Malikie Innovations Limited | System and method for pushing information from a host system to a mobile data communication device |
| 6701522, | Apr 07 2000 | Microsoft Technology Licensing, LLC | Apparatus and method for portal device authentication |
| 6711609, | Jan 29 1997 | PALMSOURCE INC | Method and apparatus for synchronizing an email client on a portable computer system with an email client on a desktop computer |
| 6721804, | Apr 07 2000 | Microsoft Technology Licensing, LLC | Portal system for converting requested data into a bytecode format based on portal device's graphical capabilities |
| 6728714, | Nov 30 1999 | GOOGLE LLC | System and method for assigning unique identifier to deleted unopened original sender e-mail after delivery |
| 6735624, | Apr 07 2000 | Microsoft Technology Licensing, LLC | Method for configuring and authenticating newly delivered portal device |
| 6738789, | Jan 25 2000 | Synchronoss Technologies, Inc | Data package including synchronization data |
| 6742038, | Apr 07 2000 | Microsoft Technology Licensing, LLC | System and method of linking user identification to a subscriber identification module |
| 6757696, | Jan 25 2000 | Synchronoss Technologies, Inc | Management server for synchronization system |
| 6779019, | May 29 1998 | Malikie Innovations Limited | System and method for pushing information from a host system to a mobile data communication device |
| 6789108, | Apr 14 2000 | TMX Interactive | Method and apparatus for dissemination of rich media |
| 6826407, | Mar 29 1999 | HELFERICH PATENT LICENSING LLC | System and method for integrating audio and visual messaging |
| 6839738, | Dec 28 2000 | CUFER ASSET LTD L L C | System and method for cleansing addresses for electronic messages |
| 6865671, | Apr 07 2000 | Proofpoint, Inc | Electronic mail system with authentication methodology for supporting relaying in a message transfer agent |
| 6873841, | Dec 16 1999 | Mercury Kingdom Assets Limited | Shared address-data service for personal CE equipment |
| 6886017, | Apr 30 1999 | Qualcomm Incorporated | System and method for managing distribution of content to a device |
| 6895427, | Dec 28 2000 | CUFER ASSET LTD L L C | System and method for cleansing addresses for electronic messages |
| 6907450, | Jul 25 1997 | NOKIA SOLUTIONS AND NETWORKS OY; HMD Global Oy | Method and apparatus for the synchronized representation of network contents |
| 6925476, | Aug 17 2000 | Synchronoss Technologies, Inc | Updating application data including adding first change log to aggreagate change log comprising summary of changes |
| 6938045, | Jan 18 2002 | Seiko Epson Corporation | Image server synchronization |
| 6941374, | Aug 05 1999 | Amazon Technologies, Inc | Hidden agent transfer protocol |
| 6944651, | May 19 2000 | Synchronoss Technologies, Inc | Single click synchronization of data from a public information store to a private information store |
| 6957248, | Jul 31 2000 | CUFER ASSET LTD L L C | System and method for forwarding electronic messages |
| 6983138, | Dec 12 1997 | HELFERICH PATENT LICENSING LLC | User interface for message access |
| 6983308, | Nov 19 1998 | UNWIRED PLANET IP MANAGER, LLC; Unwired Planet, LLC | Mail synchronization of remote and local mail systems |
| 6988129, | Nov 26 2001 | CUFER ASSET LTD L L C | Method for providing address change notification in an electronic message forwarding system |
| 6993522, | Jun 27 2001 | Microsoft Technology Licensing, LLC | System and method for resolving conflicts detected during a synchronization session |
| 7003304, | Sep 19 1997 | HELFERICH PATENT LICENSING LLC | Paging transceivers and methods for selectively retrieving messages |
| 7007041, | Jan 25 2000 | Synchronoss Technologies, Inc | Synchronization system application object interface |
| 7010303, | Dec 22 2000 | Malikie Innovations Limited | Wireless router system and method |
| 7017125, | Oct 06 1999 | LENOVO INNOVATIONS LIMITED HONG KONG | Portable terminal system, portable terminal, method of controlling portable terminal, and storage medium storing program for controlling portable terminal |
| 7024457, | Feb 17 2000 | J2 CLOUD SERVICES, LLC | E-mail synchronization between heterogeneous mail servers |
| 7031964, | Jul 11 1997 | UNWIRED PLANET IP MANAGER, LLC; Unwired Planet, LLC | Providing a directory of frequently used hyperlinks on a remote server |
| 7035878, | Jan 25 2000 | Synchronoss Technologies, Inc | Base rolling engine for data transfer and synchronization system |
| 7035902, | Aug 11 2000 | International Business Machines Corporation | Method, article of manufacture and apparatus for processing an electronic mail document |
| 7039428, | Sep 19 1997 | HELFERICH PATENT LICENSING LLC | System and method for delivering information to a transmitting and receiving device |
| 7039679, | Dec 13 1996 | Malikie Innovations Limited | System and method for globally and securely accessing unified information in a computer network |
| 7047285, | Feb 16 2001 | Microsoft Technology Licensing, LLC | System and method for providing a unified messaging scheme in a mobile device |
| 7062512, | Sep 27 2002 | Microsoft Technology Licensing, LLC | System and method for processing identification codes |
| 7064688, | Jul 09 2001 | Malikie Innovations Limited | System and method for compressing data on a bandwidth-limited network |
| 7069326, | Sep 27 2002 | Microsoft Technology Licensing, LLC | System and method for efficiently managing data transports |
| 7072984, | Apr 26 2000 | RPX Corporation | System and method for accessing customized information over the internet using a browser for a plurality of electronic devices |
| 7089305, | Sep 25 2001 | International Business Machines Corporation | Conditional promotion of bookmarks |
| 7103656, | Feb 20 2001 | Malikie Innovations Limited | System and method for administrating a wireless communication network |
| 7107341, | Dec 07 2001 | Malikie Innovations Limited | System and method of managing information distribution to mobile stations |
| 7107349, | Sep 30 2002 | Microsoft Technology Licensing, LLC | System and method for disabling and providing a notification for a data processing device |
| 7117445, | Jun 30 2003 | Microsoft Technology Licensing, LLC | Multi-mode communication apparatus and interface for contacting a user |
| 7136982, | Nov 09 2001 | Microsoft Technology Licensing, LLC | Apparatus and method for allocating memory blocks |
| 7139565, | Jan 08 2003 | Seven Networks, Inc | Connection architecture for a mobile network |
| 7139803, | Jan 29 1999 | ZETA GLOBAL CORP | Method and system for remotely sensing the file formats processed by an e-mail client |
| 7146157, | Dec 12 1997 | HELFERICH PATENT LICENSING LLC | Systems and methods for downloading audio information to a mobile device |
| 7149780, | Dec 14 2001 | CUFER ASSET LTD L L C | Method for determining e-mail address format rules |
| 7155241, | Sep 19 1997 | HELFERICH PATENT LICENSING LLC | Systems and methods for enabling a user of a communication device to manage remote information |
| 7155483, | Aug 07 2001 | Google Technology Holdings LLC | Apparatus and method for conserving bandwidth by batch processing data transactions |
| 7155725, | Mar 27 2002 | Microsoft Technology Licensing, LLC | Apparatus and method for coordinating multiple e-mail accounts |
| 7162513, | Mar 27 2002 | Microsoft Technology Licensing, LLC | Apparatus and method for distributing electronic messages to a wireless data processing device using a multi-tiered queuing architecture |
| 7187937, | Sep 19 1997 | Richard J., Helferich; Thompson Investment Group LLC | Paging transceivers and methods for selectively retrieving messages |
| 7191218, | Feb 24 2000 | International Business Machines Corporation | Database synchronization for mobile computing devices |
| 7200668, | Mar 05 2002 | Oracle America, Inc | Document conversion with merging |
| 7206815, | Jan 29 1997 | PalmSource Inc. | Method and apparatus for synchronizing an email client on a portable computer system with an email client on a desktop computer |
| 7209946, | Oct 27 2000 | RPX Corporation | Negotiated wireless peripheral security systems |
| 7209949, | May 29 1998 | Malikie Innovations Limited | System and method for synchronizing information between a host system and a mobile data communication device |
| 7209955, | May 29 1998 | Malikie Innovations Limited | Notification system and method for a mobile data communication device |
| 7212811, | Nov 17 1998 | PUSH DATA LLC | Geographical web browser, methods, apparatus and systems |
| 7215947, | Nov 17 1998 | PUSH DATA LLC | Geographical web browser, methods, apparatus and systems |
| 7222154, | Oct 27 2000 | RPX Corporation | Negotiated wireless peripheral systems |
| 7225231, | Sep 20 2000 | Malikie Innovations Limited | System and method for transmitting workspace elements across a network |
| 7228355, | Oct 27 2000 | RPX Corporation | Federated multiprotocol communication |
| 7233992, | Apr 26 1999 | INTRALINKS, INC | Computerized method and system for managing the exchange and distribution of confidential documents |
| 7242951, | Sep 19 1997 | HELFERICH PATENT LICENSING LLC | Paging transceivers and methods for selectively retrieving messages |
| 7243163, | Aug 07 2001 | Google Technology Holdings LLC | System and method for full wireless synchronization of a data processing apparatus with a messaging system |
| 7246149, | Oct 27 2000 | RPX Corporation | Negotiated wireless peripheral systems |
| 7266365, | Apr 09 2001 | Malikie Innovations Limited | System and method for delayed transmission of bundled command messages |
| 7277424, | Jul 21 1998 | RPX Corporation | Method and apparatus for co-socket telephony |
| 7277716, | Sep 19 1997 | HELFERICH PATENT LICENSING LLC | Systems and methods for delivering information to a communication device |
| 7280838, | Sep 19 1997 | HELFERICH PATENT LICENSING LLC | Paging transceivers and methods for selectively retrieving messages |
| 7283808, | Jan 18 2001 | Malikie Innovations Limited | System, method and mobile device for remote control of a voice mail system |
| 7287097, | Aug 07 2001 | Google Technology Holdings LLC | System and method for full wireless synchronization of a data processing apparatus with a messaging system |
| 7287271, | Apr 08 1997 | Malikie Innovations Limited | System and method for enabling secure access to services in a computer network |
| 7292844, | Nov 17 1998 | PUSH DATA LLC | Geographical web browser, methods, apparatus and systems |
| 7293061, | Oct 27 2000 | RPX Corporation | Negotiated wireless peripheral security systems |
| 7293110, | Oct 27 2000 | RPX Corporation | Federated multiprotocol communication |
| 7295836, | Mar 09 2001 | Malikie Innovations Limited | Advanced voice and data operations in a mobile data communication device |
| 7296243, | Mar 19 2002 | Meta Platforms, Inc | Animating display motion |
| 7305700, | Jan 08 2003 | Seven Networks, Inc | Secure transport for mobile communication network |
| 7317699, | Oct 26 2001 | BlackBerry Limited | System and method for controlling configuration settings for mobile communication devices and services |
| 7340534, | Mar 05 2002 | Oracle America, Inc | Synchronization of documents between a server and small devices |
| 7343179, | Aug 13 2003 | Microsoft Technology Licensing, LLC | System and method for previewing and purchasing ring tones for a mobile device |
| 7356591, | Dec 07 2001 | Malikie Innovations Limited | System and method of managing information distribution to mobile stations |
| 7373144, | Sep 30 2002 | Microsoft Technology Licensing, LLC | System and method for automatically providing user status in a messaging service |
| 7376432, | Sep 19 1997 | HELFERICH PATENT LICENSING LLC | Paging transceivers and methods for selectively retrieving messages |
| 7383303, | Sep 30 2002 | Microsoft Technology Licensing, LLC | System and method for integrating personal information management and messaging applications |
| 7386588, | May 29 1998 | Malikie Innovations Limited | System and method for pushing information from a host system to a mobile data communication device |
| 7392297, | Nov 05 1999 | Kabushiki Kaisha Toshiba | Message processing scheme for realizing unified handling and management of messages using a portable message processing device |
| 7401104, | Aug 21 2003 | Microsoft Technology Licensing, LLC | Systems and methods for synchronizing computer systems through an intermediary file system share or device |
| 7403787, | Sep 19 1997 | HELFERICH PATENT LICENSING LLC | Paging transceivers and methods for selectively retrieving messages |
| 7415486, | Jan 26 2000 | Synchronoss Technologies, Inc | System using change log stored at a server to identify changes to user's application data for synchronizing data between systems |
| 7424511, | Oct 27 2000 | RPX Corporation | Negotiated wireless peripheral systems |
| 7424512, | Oct 27 2000 | RPX Corporation | Negotiated wireless peripheral systems |
| 7437405, | Oct 01 2002 | Microsoft Technology Licensing, LLC | System and method for managing data objects in a wireless device |
| 7441271, | Oct 20 2005 | Seven Networks, Inc | Method and apparatus for intercepting events in a communication system |
| 7447799, | Apr 24 2002 | Malikie Innovations Limited | System and method for automatically updating a wireless device |
| 7478170, | Mar 05 2002 | Oracle America, Inc | Generic infrastructure for converting documents between formats with merge capabilities |
| 7490172, | Oct 27 2000 | RPX Corporation | Federated multiprotocol communication |
| 7493367, | Feb 17 2000 | J2 CLOUD SERVICES, LLC | E-mail synchronization between heterogeneous mail servers |
| 7499716, | Sep 19 1997 | HELFERICH PATENT LICENSING LLC | System and method for delivering information to a transmitting and receiving device |
| 7500188, | Apr 26 2000 | RPX Corporation | System and method for adapting information content for an electronic device |
| 7508777, | Jul 21 1998 | RPX Corporation | Method and apparatus for co-socket telephony |
| 7509263, | Jan 20 2000 | EPOCRATES, LLC | Method and system for providing current industry specific data to physicians |
| 7509376, | May 29 1998 | Malikie Innovations Limited | System and method for redirecting message attachments between a host system and a mobile data communication device |
| 7529230, | Dec 22 2000 | Malikie Innovations Limited | Wireless router system and method |
| 7543026, | Dec 28 2000 | CUFER ASSET LTD L L C | System and method for address correction of electronic messages |
| 7574444, | Nov 15 2006 | Qualcomm Incorporated | Device-side data de-duping |
| 7580984, | Jun 25 2001 | AT&T Intellectual Property I, L.P. | System and method for sorting e-mail |
| 7581030, | Oct 27 2000 | RPX Corporation | Federated multiprotocol communication |
| 7584186, | Oct 14 2005 | Microsoft Technology Licensing, LLC | System and method for resolving conflicts detected during a synchronization |
| 7587446, | Nov 10 2000 | Synchronoss Technologies, Inc | Acquisition and synchronization of digital media to a personal information space |
| 7596565, | Aug 07 2001 | Google Technology Holdings LLC | System and method for maintaining wireless file folders at a wireless device |
| 7603435, | Nov 15 2006 | Qualcomm Incorporated | Over-the-air device kill pill and lock |
| 7606936, | May 29 1998 | Malikie Innovations Limited | System and method for redirecting data to a wireless device over a plurality of communication paths |
| 7613777, | Mar 11 2004 | Microsoft Technology Licensing, LLC | Rapidly obtaining a subset of message data from a server for filtering |
| 7613955, | Jan 06 2006 | Microsoft Technology Licensing, LLC | Collecting debug data from a wireless device |
| 7627305, | Mar 29 1999 | HELFERICH PATENT LICENSING LLC | Systems and methods for adding information to a directory stored in a mobile device |
| 7631105, | Oct 27 2000 | RPX Corporation | Federated multiprotocol communication |
| 7634509, | Nov 07 2003 | Synchronoss Technologies, Inc | Personal information space management system and method |
| 7643824, | Feb 27 2004 | Synchronoss Technologies, Inc | Wireless telephone data backup system |
| 7664067, | Dec 15 2005 | Microsoft Technology Licensing, LLC | Preserving socket connections over a wireless network |
| 7680281, | Oct 20 2004 | Seven Networks, Inc. | Method and apparatus for intercepting events in a communication system |
| 7689606, | May 02 2006 | MYPOINTS COM, LLC | System and method of efficiently generating and sending bulk emails |
| 7689721, | May 29 1998 | Malikie Innovations Limited | System and method for pushing information from a host system to a mobile data communication device |
| 7710912, | Jul 11 2005 | Microsoft Technology Licensing, LLC | Managing content synchronization between a data service and a data processing device |
| 7720920, | Jun 27 2007 | Microsoft Technology Licensing, LLC | Client side based data synchronization and storage |
| 7739334, | Mar 17 2000 | BlackBerry Limited | System and method for automatically forwarding email and email events via a computer network to a server computer |
| 7741954, | Sep 19 1997 | Wireless Science, LLC | Paging transceivers and methods for selectively retrieving messages |
| 7743119, | Aug 07 2001 | Google Technology Holdings LLC | System and method for mapping identification codes |
| 7747782, | Apr 26 2000 | RPX Corporation | System and method for providing and displaying information content |
| 7752166, | Nov 15 2001 | Malikie Innovations Limited | System and methods for asynchronous synchronization |
| 7769400, | Nov 22 2004 | Seven Networks, Inc | Connectivity function for forwarding e-mail |
| 7774007, | Jun 21 2005 | Seven Networks, Inc | Maintaining an IP connection in a mobile network |
| 7778237, | Jul 21 1998 | RPX Corporation | Method and apparatus for co-socket telephony |
| 7778962, | Apr 30 2004 | Microsoft Technology Licensing, LLC | Client store synchronization through intermediary store change packets |
| 7788224, | Oct 08 2003 | Alcatel | Fast database replication |
| 7796742, | Apr 21 2005 | Seven Networks, Inc | Systems and methods for simplified provisioning |
| 7813333, | Jul 21 1998 | RPX Corporation | Method and apparatus for co-socket telephony |
| 7813334, | Jul 21 1998 | RPX Corporation | Method and apparatus for co-socket telephony |
| 7818425, | Jun 25 2001 | AT&T Intellectual Property I, L P | System and method for regulating electronic messages |
| 7818435, | Dec 14 2000 | Synchronoss Technologies, Inc | Reverse proxy mechanism for retrieving electronic content associated with a local network |
| 7822865, | Oct 27 2000 | RPX Corporation | Federated multiprotocol communication |
| 7827597, | Jan 08 2002 | Seven Networks, Inc. | Secure transport for mobile communication network |
| 7835757, | Sep 19 1997 | HELFERICH PATENT LICENSING LLC | System and method for delivering information to a transmitting and receiving device |
| 7843314, | Sep 19 1997 | HELFERICH PATENT LICENSING LLC | Paging transceivers and methods for selectively retrieving messages |
| 7844906, | Jun 30 2003 | Microsoft Technology Licensing, LLC | Multi-mode communication apparatus and interface for contacting a user |
| 7849140, | Aug 29 2002 | Oracle America, Inc | Peer-to-peer email messaging |
| 7853563, | Aug 01 2005 | Seven Networks, Inc | Universal data aggregation |
| 7856365, | Dec 11 2008 | EPOCRATES, LLC | Method and system for providing current industry specific data to physicians |
| 7856508, | Oct 27 2000 | RPX Corporation | Accessing vended products or services using a wireless device |
| 7872640, | Mar 19 2002 | Meta Platforms, Inc | Constraining display motion in display navigation |
| 7895334, | Jul 19 2000 | Synchronoss Technologies, Inc | Remote access communication architecture apparatus and method |
| 7904101, | Jun 21 2005 | Seven Networks, Inc | Network-initiated data transfer in a mobile network |
| 7917468, | Aug 01 2005 | Seven Networks, Inc | Linking of personal information management data |
| 7917505, | Aug 01 2005 | Seven Networks, Inc. | Methods for publishing content |
| 7930352, | Jun 25 2001 | AT&T Intellectual Property II, L.P. | System and method for sorting electronic communications |
| 7937498, | Oct 27 2000 | RPX Corporation | Federated multiprotocol communication |
| 7953802, | May 29 1998 | Malikie Innovations Limited | System and method for pushing information from a host system to a mobile data communication device |
| 7957695, | Mar 29 1999 | HELFERICH PATENT LICENSING LLC | Method for integrating audio and visual messaging |
| 7962622, | Aug 07 2001 | Google Technology Holdings LLC | System and method for providing provisioning and upgrade services for a wireless device |
| 8001177, | Jun 18 2001 | Qualcomm Incorporated | Method and apparatus for automated personal information management data transfer for a wireless enabled handheld |
| 8010082, | Oct 19 2005 | Seven Networks, Inc. | Flexible billing architecture |
| 8015163, | Nov 15 2006 | Qualcomm Incorporated | Detecting duplicative user data on computing device |
| 8019808, | Aug 21 2003 | Microsoft Corporation | Systems and methods for the implementation of a synchronization schemas for units of information manageable by a hardware/software interface system |
| 8028033, | Feb 17 2000 | J2 CLOUD SERVICES, LLC | E-mail synchronization between heterogeneous mail servers |
| 8050684, | Dec 22 2000 | Malikie Innovations Limited | Wireless router system and method |
| 8060564, | May 29 1998 | Malikie Innovations Limited | System and method for pushing information from a host system to a mobile data communication device |
| 8064583, | Apr 21 2005 | Seven Networks, Inc. | Multiple data store authentication |
| 8069144, | Nov 15 2001 | Malikie Innovations Limited | System and methods for asynchronous synchronization |
| 8069166, | Aug 01 2005 | Seven Networks, Inc. | Managing user-to-user contact with inferred presence information |
| 8073954, | Jul 19 2000 | Synchronoss Technologies, Inc | Method and apparatus for a secure remote access system |
| 8078158, | Jun 26 2008 | Seven Networks, Inc | Provisioning applications for a mobile device |
| 8086695, | Nov 15 2006 | Qualcomm Incorporated | Over the air services for mobile devices |
| 8099046, | Mar 29 1999 | HELFERICH PATENT LICENSING LLC | Method for integrating audio and visual messaging |
| 8103745, | Mar 07 2007 | RPX Corporation | Negotiated wireless peripheral security systems |
| 8107601, | Sep 19 1997 | HELFERICH PATENT LICENSING LLC | Wireless messaging system |
| 8107921, | Jan 11 2008 | Seven Networks, Inc | Mobile virtual network operator |
| 8116214, | Dec 03 2004 | Seven Networks, Inc | Provisioning of e-mail settings for a mobile terminal |
| 8116741, | Sep 19 1997 | HELFERICH PATENT LICENSING LLC | System and method for delivering information to a transmitting and receiving device |
| 8116743, | Dec 12 1997 | HELFERICH PATENT LICENSING LLC | Systems and methods for downloading information to a mobile device |
| 8117344, | Dec 13 1996 | Malikie Innovations Limited | Global server for authenticating access to remote services |
| 8127342, | Jan 08 2002 | Seven Networks, Inc. | Secure end-to-end transport through intermediary nodes |
| 8134450, | Sep 19 1997 | HELFERICH PATENT LICENSING LLC | Content provision to subscribers via wireless transmission |
| 8134954, | Oct 26 2001 | BlackBerry Limited | System and method for controlling configuration settings for mobile communication devices and services |
| 8135609, | Jan 08 2002 | Microsoft Technology Licensing, LLC | Identifying and surveying subscribers |
| 8135675, | May 02 2006 | MYPOINTS COM, LLC | System and method of efficiently generating and sending bulk emails |
| 8135798, | Nov 15 2006 | Qualcomm Incorporated | Over-the-air device services and management |
| 8156074, | Jan 26 2000 | Synchronoss Technologies, Inc | Data transfer and synchronization system |
| 8165575, | Dec 22 2000 | Malikie Innovations Limited | Wireless router system and method |
| 8166101, | Aug 21 2003 | Microsoft Technology Licensing, LLC | Systems and methods for the implementation of a synchronization schemas for units of information manageable by a hardware/software interface system |
| 8166164, | Nov 01 2010 | Seven Networks, Inc. | Application and network-based long poll request detection and cacheability assessment therefor |
| 8176410, | Sep 13 2005 | Adobe Inc | System and/or method for content cropping |
| 8180900, | Dec 07 2001 | Malikie Innovations Limited | System and method of managing information distribution to mobile stations |
| 8181111, | Dec 31 2007 | Synchronoss Technologies, Inc | System and method for providing social context to digital activity |
| 8190170, | Nov 17 1998 | PUSH DATA LLC | Geographical web browser, methods, apparatus and systems |
| 8190701, | Nov 01 2010 | Seven Networks, Inc.; Seven Networks, Inc | Cache defeat detection and caching of content addressed by identifiers intended to defeat cache |
| 8200759, | Jan 29 1999 | ZETA GLOBAL CORP | Method and system for remotely sensing the file formats processed by an e-mail client |
| 8204953, | Nov 01 2010 | Seven Networks, Inc.; Seven Networks, Inc | Distributed system for cache defeat detection and caching of content addressed by identifiers intended to defeat cache |
| 8209709, | Mar 14 2005 | Seven Networks, Inc | Cross-platform event engine |
| 8224294, | Sep 19 1997 | HELFERICH PATENT LICENSING LLC | System and method for delivering information to a transmitting and receiving device |
| 8230026, | Jun 26 2002 | Malikie Innovations Limited | System and method for pushing information between a host system and a mobile data communication device |
| 8238696, | Aug 21 2003 | Microsoft Technology Licensing, LLC | Systems and methods for the implementation of a digital images schema for organizing units of information manageable by a hardware/software interface system |
| 8255006, | Nov 10 2009 | Synchronoss Technologies, Inc | Event dependent notification system and method |
| 8255359, | Nov 15 2001 | Malikie Innovations Limited | System and methods for asynchronous synchronization |
| 8259611, | Oct 26 2001 | BlackBerry Limited | System and method for controlling configuration settings for mobile communication devices and services |
| 8285200, | Jun 21 2005 | Seven Networks, Inc | Maintaining an IP connection in a mobile network |
| 8291076, | Nov 01 2010 | Seven Networks, Inc. | Application and network-based long poll request detection and cacheability assessment therefor |
| 8295450, | Sep 19 1997 | HELFERICH PATENT LICENSING LLC | Wireless messaging system |
| 8301587, | Jul 01 2004 | Hewlett Packard Enterprise Development LP | Internet enabled computer system management |
| 8315976, | Jan 26 2000 | Synchronoss Technologies, Inc | Data transfer and synchronization system |
| 8316098, | Apr 19 2011 | Seven Networks, Inc | Social caching for device resource sharing and management |
| 8321511, | Aug 07 2001 | Google Technology Holdings LLC | System and method for full wireless synchronization of a data processing apparatus with a messaging system |
| 8326985, | Nov 01 2010 | Seven Networks, Inc. | Distributed management of keep-alive message signaling for mobile network resource conservation and optimization |
| 8355702, | Sep 19 1997 | HELFERICH PATENT LICENSING LLC | System and method for delivering information to a transmitting and receiving device |
| 8356080, | Apr 19 2011 | Seven Networks, Inc | System and method for a mobile device to use physical storage of another device for caching |
| 8364181, | Dec 10 2007 | Seven Networks, Inc | Electronic-mail filtering for mobile devices |
| 8365240, | Apr 18 2005 | BlackBerry Limited | Method for providing wireless application privilege management |
| 8369263, | Nov 17 1998 | AIDO MOBILITY LLC | Geographical web browser, methods, apparatus and systems |
| 8374585, | Sep 19 1997 | HELFERICH PATENT LICENSING LLC | System and method for delivering information to a transmitting and receiving device |
| 8407305, | May 29 1998 | Malikie Innovations Limited | System and method for pushing information from a mobile computer to another device |
| 8412675, | Aug 01 2005 | Seven Networks, Inc. | Context aware data presentation |
| 8412805, | Jun 01 2001 | Malikie Innovations Limited | Adaptive synchronization of service data |
| 8417823, | Nov 22 2010 | Seven Network, Inc. | Aligning data transfer to optimize connections established for transmission over a wireless network |
| 8438633, | Apr 21 2005 | Seven Networks, Inc. | Flexible real-time inbox access |
| 8442943, | Jan 26 2000 | Synchronoss Technologies, Inc | Data transfer and synchronization between mobile systems using change log |
| 8447967, | Jun 29 2000 | DATAMOTION TEXAS LLC | Controlled message distribution |
| 8451822, | Jul 21 1998 | RPX Corporation | Method and apparatus for co-socket telephony |
| 8463862, | Aug 17 2000 | MXGO Technologies, Inc. | Methods and systems for dispatching messages to mobile devices |
| 8468126, | Aug 01 2005 | Seven Networks, Inc | Publishing data in an information community |
| 8483694, | Dec 22 2000 | Malikie Innovations Limited | Wireless router system and method |
| 8484303, | Feb 17 2000 | J2 CLOUD SERVICES, LLC | E-mail synchronization between heterogeneous mail servers |
| 8484314, | Nov 01 2010 | Seven Networks, Inc. | Distributed caching in a wireless network of content delivered for a mobile application over a long-held request |
| 8494510, | Jun 26 2008 | SEVEN NETWORKS INC | Provisioning applications for a mobile device |
| 8498289, | Jan 18 2001 | Malikie Innovations Limited | System, method and mobile device for remote control of a voice mail system |
| 8498387, | Sep 19 1997 | HELFERICH PATENT LICENSING LLC | Wireless messaging systems and methods |
| 8516034, | Jul 08 2002 | Malikie Innovations Limited | System and method for modifying application behavior based on network bandwidth |
| 8516055, | May 29 1998 | Malikie Innovations Limited | System and method for pushing information from a host system to a mobile data communication device in a wireless data network |
| 8527599, | Jun 25 2001 | AT&T Intellectual Property I, L.P. | System and method for regulating electronic messages |
| 8539040, | Nov 22 2010 | Seven Networks, Inc. | Mobile network background traffic data management with optimized polling intervals |
| 8549587, | Jan 08 2002 | Seven Networks, Inc. | Secure end-to-end transport through intermediary nodes |
| 8560006, | Sep 19 1997 | HELFERICH PATENT LICENSING LLC | System and method for delivering information to a transmitting and receiving device |
| 8561086, | Mar 14 2005 | Seven Networks, Inc | System and method for executing commands that are non-native to the native environment of a mobile device |
| 8566399, | Feb 27 2004 | HUAWEI TECHNOLOGIES CO , LTD | Method and system for synchronizing a drafts folder |
| 8611873, | May 12 2004 | Synchronoss Technologies, Inc | Advanced contact identification system |
| 8615566, | Mar 23 2001 | Synchronoss Technologies, Inc | Apparatus and method for operational support of remote network systems |
| 8620286, | Feb 27 2004 | Synchronoss Technologies, Inc | Method and system for promoting and transferring licensed content and applications |
| 8620858, | Dec 29 2004 | Seven Networks, Inc | Database synchronization via a mobile network |
| 8621025, | Jan 25 2000 | Synchronoss Technologis, Inc. | Mobile data transfer and synchronization system |
| 8621075, | Apr 27 2011 | Seven Metworks, Inc. | Detecting and preserving state for satisfying application requests in a distributed proxy and cache system |
| 8635339, | Apr 27 2011 | Seven Networks, Inc. | Cache state management on a mobile device to preserve user experience |
| 8645471, | Jul 21 2003 | Synchronoss Technologies, Inc | Device message management system |
| 8648801, | Mar 19 2002 | Meta Platforms, Inc | Aligned display navigation |
| 8676178, | Feb 01 2002 | Microsoft Technology Licensing, LLC | Method and system for managing changes to a contact database |
| 8693494, | Jun 01 2007 | Seven Networks, Inc | Polling |
| 8693996, | Dec 22 2000 | Malikie Innovations Limited | Wireless router system and method |
| 8694650, | Dec 07 2001 | Malikie Innovations Limited | System and method of managing information distribution to mobile stations |
| 8700728, | Nov 01 2010 | Seven Networks, Inc. | Cache defeat detection and caching of content addressed by identifiers intended to defeat cache |
| 8713646, | Dec 09 2011 | OMNISSA, LLC | Controlling access to resources on a network |
| 8731522, | Jan 22 2004 | Malikie Innovations Limited | Mailbox pooling pre-empting criteria |
| 8731542, | Aug 11 2005 | Seven Networks, Inc | Dynamic adjustment of keep-alive message intervals in a mobile network |
| 8738050, | Dec 10 2007 | Seven Networks, Inc. | Electronic-mail filtering for mobile devices |
| 8745167, | Dec 13 1996 | Malikie Innovations Limited | System and method for globally and securely accessing unified information in a computer network |
| 8750123, | Mar 11 2013 | Seven Networks, Inc. | Mobile device equipped with mobile network congestion recognition to make intelligent decisions regarding connecting to an operator network |
| 8756426, | Jul 03 2013 | OMNISSA, LLC | Functionality watermarking and management |
| 8761756, | Jun 21 2005 | SEVEN Networks International Oy | Maintaining an IP connection in a mobile network |
| 8762489, | Apr 27 2011 | Seven Networks, Inc. | System and method for making requests on behalf of a mobile device based on atomic processes for mobile network traffic relief |
| 8762577, | Jun 30 2003 | Apple Inc | Method and system for providing network synchronization with a unified messaging system |
| 8774844, | Jun 01 2007 | SEVEN NETWORKS INC | Integrated messaging |
| 8775631, | Jul 13 2012 | 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 |
| 8775815, | Jul 03 2013 | OMNISSA, LLC | Enterprise-specific functionality watermarking and management |
| 8782222, | Nov 01 2010 | Seven Networks | Timing of keep-alive messages used in a system for mobile network resource conservation and optimization |
| 8787947, | Jun 18 2008 | Seven Networks, Inc. | Application discovery on mobile devices |
| 8793305, | Dec 13 2007 | Seven Networks, Inc | Content delivery to a mobile device from a content service |
| 8799410, | Jan 28 2008 | SEVEN NETWORKS INC | System and method of a relay server for managing communications and notification between a mobile device and a web access server |
| 8805334, | Nov 22 2004 | Seven Networks, Inc | Maintaining mobile terminal information for secure communications |
| 8805425, | Jun 01 2007 | Seven Networks, Inc | Integrated messaging |
| 8806217, | Jul 03 2013 | OMNISSA, LLC | Functionality watermarking and management |
| 8811952, | Jan 08 2002 | Seven Networks, Inc. | Mobile device power management in data synchronization over a mobile network with or without a trigger notification |
| 8812695, | Apr 09 2012 | Seven Networks, Inc | Method and system for management of a virtual network connection without heartbeat messages |
| 8812702, | Dec 13 1996 | Malikie Innovations Limited | System and method for globally and securely accessing unified information in a computer network |
| 8826432, | Dec 06 2012 | OMNISSA, LLC | Systems and methods for controlling email access |
| 8831561, | Oct 20 2004 | Seven Networks, Inc | System and method for tracking billing events in a mobile wireless network for a network operator |
| 8832228, | Apr 27 2011 | Seven Networks, Inc. | System and method for making requests on behalf of a mobile device based on atomic processes for mobile network traffic relief |
| 8832785, | Dec 06 2012 | OMNISSA, LLC | Systems and methods for controlling email access |
| 8838744, | Jan 28 2008 | Seven Networks, Inc | Web-based access to data objects |
| 8838783, | Jul 26 2010 | Seven Networks, Inc | Distributed caching for resource and mobile network traffic management |
| 8839412, | Apr 21 2005 | Seven Networks, Inc. | Flexible real-time inbox access |
| 8843153, | Nov 01 2010 | Seven Networks, Inc. | Mobile traffic categorization and policy for network use optimization while preserving user experience |
| 8849902, | Jan 25 2008 | SEVEN NETWORKS INC | System for providing policy based content service in a mobile network |
| 8861354, | Dec 14 2011 | Seven Networks, Inc | Hierarchies and categories for management and deployment of policies for distributed wireless traffic optimization |
| 8862657, | Jan 25 2008 | Seven Networks, Inc | Policy based content service |
| 8862868, | Dec 06 2012 | OMNISSA, LLC | Systems and methods for controlling email access |
| 8868753, | Dec 06 2011 | Seven Networks, Inc. | System of redundantly clustered machines to provide failover mechanisms for mobile traffic management and network resource conservation |
| 8873411, | Dec 03 2004 | Seven Networks, Inc. | Provisioning of e-mail settings for a mobile terminal |
| 8874761, | Jan 25 2013 | Seven Networks, Inc.; Seven Networks, Inc | Signaling optimization in a wireless network for traffic utilizing proprietary and non-proprietary protocols |
| 8880618, | Feb 15 2007 | Malikie Innovations Limited | Email communications system with wireless device move reconciliation features and related methods |
| 8886176, | Jul 26 2010 | SEVEN NETWORKS INC | Mobile application traffic optimization |
| 8902253, | Mar 19 2002 | Meta Platforms, Inc | Constrained display navigation |
| 8903945, | Nov 15 2006 | Qualcomm Incorporated | Over the air services for mobile devices |
| 8903954, | Nov 22 2010 | Seven Networks, Inc. | Optimization of resource polling intervals to satisfy mobile device requests |
| 8909192, | Jan 11 2008 | SEVEN NETWORKS INC | Mobile virtual network operator |
| 8909202, | Jan 05 2012 | Seven Networks, Inc | Detection and management of user interactions with foreground applications on a mobile device in distributed caching |
| 8909759, | Oct 10 2008 | Seven Networks, Inc | Bandwidth measurement |
| 8914002, | Jan 11 2008 | SEVEN NETWORKS INC | System and method for providing a network service in a distributed fashion to a mobile device |
| 8914013, | Apr 25 2013 | OMNISSA, LLC | Device management macros |
| 8918503, | Dec 06 2011 | Seven Networks, Inc. | Optimization of mobile traffic directed to private networks and operator configurability thereof |
| 8943428, | Nov 01 2010 | Synchronoss Technologies, Inc | System for and method of field mapping |
| 8954512, | Aug 07 2001 | Google Technology Holdings LLC | System and method for full wireless synchronization of a data processing apparatus with a data service |
| 8966066, | Nov 01 2010 | Seven Networks, Inc. | Application and network-based long poll request detection and cacheability assessment therefor |
| 8972348, | Oct 04 1999 | Microsoft Technology Licensing, LLC | Method and system for supporting off-line mode of operation and synchronization |
| 8977755, | Dec 06 2011 | 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 |
| 8978110, | Dec 06 2012 | OMNISSA, LLC | Systems and methods for controlling email access |
| 8984581, | Jul 27 2011 | Seven Networks, Inc. | Monitoring mobile application activities for malicious traffic on a mobile device |
| 8989728, | Jan 08 2002 | Seven Networks, Inc. | Connection architecture for a mobile network |
| 8990695, | Oct 23 2003 | Microsoft Technology Licensing, LLC | Flexible architecture for notifying applications of state changes |
| 8997187, | Mar 15 2013 | OMNISSA, LLC | Delegating authorization to applications on a client device in a networked environment |
| 9001746, | Jun 21 2005 | Seven Networks, Inc | Network-initiated data transfer in a mobile network |
| 9002828, | Jan 02 2009 | Seven Networks, Inc | Predictive content delivery |
| 9009250, | Dec 07 2011 | Seven Networks, Inc | Flexible and dynamic integration schemas of a traffic management system with various network operators for network traffic alleviation |
| 9021021, | Dec 14 2011 | Seven Networks, Inc | Mobile network reporting and usage analytics system and method aggregated using a distributed traffic optimization system |
| 9021037, | Dec 06 2012 | OMNISSA, LLC | Systems and methods for controlling email access |
| 9037666, | Jun 25 2001 | AT&T Intellectual Property I, L.P. | System and method for regulating electronic messages |
| 9037685, | Nov 15 2006 | Qualcomm Incorporated | Intelligent migration between devices having different hardware or software configuration |
| 9041737, | Mar 19 2002 | Meta Platforms, Inc | Display navigation using navigation controls |
| 9041738, | Mar 19 2002 | Meta Platforms, Inc | Display navigation |
| 9043433, | Jul 26 2010 | SEVEN NETWORKS INC | Mobile network traffic coordination across multiple applications |
| 9043731, | Mar 30 2010 | Seven Networks, Inc | 3D mobile user interface with configurable workspace management |
| 9047142, | Mar 14 2005 | Seven Networks, Inc | Intelligent rendering of information in a limited display environment |
| 9049071, | Oct 26 2001 | BlackBerry Limited | System and method for controlling configuration settings for mobile communication devices and services |
| 9049179, | Jul 26 2010 | Seven Networks, Inc | Mobile network traffic coordination across multiple applications |
| 9055102, | Jun 20 2006 | Seven Networks, Inc. | Location-based operations and messaging |
| 9059891, | Apr 18 2005 | BlackBerry Limited | Method for providing wireless application privilege management |
| 9060032, | Nov 01 2010 | Seven Networks, Inc | Selective data compression by a distributed traffic management system to reduce mobile data traffic and signaling traffic |
| 9065765, | Jul 22 2013 | Seven Networks, Inc. | Proxy server associated with a mobile carrier for enhancing mobile traffic management in a mobile network |
| 9065902, | Feb 01 2002 | Microsoft Technology Licensing, LLC | Method and system for managing changes to a contact database |
| 9069436, | Apr 01 2005 | INTRALINKS, INC | System and method for information delivery based on at least one self-declared user attribute |
| 9071953, | Sep 19 1997 | HELFERICH PATENT LICENSING LLC | Systems and methods providing advertisements to a cell phone based on location and external temperature |
| 9077630, | Jul 26 2010 | Seven Networks, Inc | Distributed implementation of dynamic wireless traffic policy |
| 9084105, | Apr 19 2011 | Seven Networks, Inc. | Device resources sharing for network resource conservation |
| 9100873, | Nov 22 2010 | Seven Networks, Inc. | Mobile network background traffic data management |
| 9112749, | Jul 25 2013 | OMNISSA, LLC | Functionality management via application modification |
| 9131397, | Jan 05 2012 | Seven Networks, Inc. | Managing cache to prevent overloading of a wireless network due to user activity |
| 9148417, | Apr 27 2012 | INTRALINKS, INC | Computerized method and system for managing amendment voting in a networked secure collaborative exchange environment |
| 9161258, | Oct 24 2012 | Seven Networks, LLC | Optimized and selective management of policy deployment to mobile clients in a congested network to prevent further aggravation of network congestion |
| 9166941, | Apr 24 2007 | Microsoft Technology Licensing, LLC | Synchronizing email messages between external and local email servers and/or a wireless device |
| 9167401, | Sep 19 1997 | HELFERICH PATENT LICENSING LLC | Wireless messaging and content provision systems and methods |
| 9173128, | Dec 07 2011 | Seven Networks, LLC | Radio-awareness of mobile device for sending server-side control signals using a wireless network optimized transport protocol |
| 9185099, | Sep 23 2013 | OMNISSA, LLC | Securely authorizing access to remote resources |
| 9195811, | Jul 03 2013 | OMNISSA, LLC | Functionality watermarking and management |
| 9202025, | Jul 03 2013 | OMNISSA, LLC | Enterprise-specific functionality watermarking and management |
| 9203864, | Feb 02 2012 | Seven Networks, Inc | Dynamic categorization of applications for network access in a mobile network |
| 9208123, | Dec 07 2011 | Seven Networks, Inc | Mobile device having content caching mechanisms integrated with a network operator for traffic alleviation in a wireless network and methods therefor |
| 9219741, | May 02 2013 | OMNISSA, LLC | Time-based configuration policy toggling |
| 9226155, | Jul 25 2013 | OMNISSA, LLC | Data communications management |
| 9230243, | Oct 13 2011 | Dassault Systemes | Collaborative design using duplicated workspaces |
| 9239800, | Jul 27 2011 | Seven Networks, LLC | Automatic generation and distribution of policy information regarding malicious mobile traffic in a wireless network |
| 9241314, | Jan 23 2013 | Seven Networks, Inc | Mobile device with application or context aware fast dormancy |
| 9251193, | Aug 01 2005 | Seven Networks, LLC | Extending user relationships |
| 9251360, | Apr 27 2012 | INTRALINKS, INC | Computerized method and system for managing secure mobile device content viewing in a networked secure collaborative exchange environment |
| 9253176, | Apr 27 2012 | INTRALINKS, INC | Computerized method and system for managing secure content sharing in a networked secure collaborative exchange environment |
| 9258301, | Oct 29 2013 | OMNISSA, LLC | Advanced authentication techniques |
| 9258372, | May 09 2007 | Malikie Innovations Limited | Wireless router system and method |
| 9270777, | Jun 06 2013 | OMNISSA, LLC | Social media and data sharing controls for data security purposes |
| 9271238, | Jan 23 2013 | Seven Networks, Inc | Application or context aware fast dormancy |
| 9275163, | Nov 01 2010 | Seven Networks, LLC | Request and response characteristics based adaptation of distributed caching in a mobile network |
| 9277443, | Dec 07 2011 | Seven Networks, Inc | Radio-awareness of mobile device for sending server-side control signals using a wireless network optimized transport protocol |
| 9298792, | Dec 10 2004 | Seven Networks, Inc | Database synchronization |
| 9298793, | May 29 1998 | Malikie Innovations Limited | System and method for pushing information from a host system to a mobile data communication device |
| 9300719, | Apr 19 2011 | Seven Networks, Inc | System and method for a mobile device to use physical storage of another device for caching |
| 9306890, | Jun 25 2001 | AT&T Intellectual Property I, L.P. | System and method for regulating electronic messages |
| 9307493, | Dec 20 2012 | Seven Networks, LLC | Systems and methods for application management of mobile device radio state promotion and demotion |
| 9319243, | Oct 07 2004 | GOOGLE LLC | Message server that retains messages deleted by one client application for access by another client application |
| 9325662, | Jan 07 2011 | Seven Networks, Inc | System and method for reduction of mobile network traffic used for domain name system (DNS) queries |
| 9325713, | Dec 06 2012 | OMNISSA, LLC | Systems and methods for controlling email access |
| 9326189, | Feb 03 2012 | Seven Networks, Inc | User as an end point for profiling and optimizing the delivery of content and data in a wireless network |
| 9330196, | Nov 01 2010 | Seven Networks, Inc | Wireless traffic management system cache optimization using http headers |
| 9344839, | May 29 1998 | Malikie Innovations Limited | System and method for pushing information from a host system to a mobile communication device |
| 9360993, | Mar 19 2002 | Meta Platforms, Inc | Display navigation |
| 9361603, | Dec 31 1996 | Malikie Innovations Limited | System and method for globally and securely accessing unified information in a computer network |
| 9369454, | Apr 27 2012 | INTRALINKS, INC | Computerized method and system for managing a community facility in a networked secure collaborative exchange environment |
| 9369455, | Apr 27 2012 | INTRALINKS, INC | Computerized method and system for managing an email input facility in a networked secure collaborative exchange environment |
| 9369531, | Dec 07 2001 | Malikie Innovations Limited | System and method of managing information distribution to mobile stations |
| 9374435, | May 29 1998 | Malikie Innovations Limited | System and method for using trigger events and a redirector flag to redirect messages |
| 9391960, | Dec 06 2012 | OMNISSA, LLC | Systems and methods for controlling email access |
| 9397998, | Apr 27 2012 | INTRALINKS, INC | Computerized method and system for managing secure content sharing in a networked secure collaborative exchange environment with customer managed keys |
| 9407695, | Jun 01 2001 | Malikie Innovations Limited | Adaptive synchronization of service data |
| 9407713, | Jul 26 2010 | Seven Networks, Inc | Mobile application traffic optimization |
| 9426129, | Dec 06 2012 | OMNISSA, LLC | Systems and methods for controlling email access |
| 9426162, | May 02 2013 | OMNISSA, LLC | Location-based configuration policy toggling |
| 9444812, | Apr 21 2005 | Seven Networks, LLC | Systems and methods for authenticating a service |
| 9450921, | Dec 06 2012 | OMNISSA, LLC | Systems and methods for controlling email access |
| 9467475, | Mar 30 2012 | Synchronoss Technologies, Inc | Secure mobile framework |
| 9473417, | Mar 14 2013 | OMNISSA, LLC | Controlling resources used by computing devices |
| 9473533, | Mar 30 2012 | Synchronoss Technologies, Inc | Secure mobile framework |
| 9479638, | Aug 17 2000 | MXGO Technologies, Inc. | Methods and systems for dispatching messages to mobile devices |
| 9514327, | Nov 14 2013 | INTRALINKS, INC | Litigation support in cloud-hosted file sharing and collaboration |
| 9516005, | Aug 20 2013 | OMNISSA, LLC | Individual-specific content management |
| 9536083, | Jan 02 2015 | SV CAPITAL, LLC | Securing data on untrusted devices |
| 9537896, | Apr 18 2005 | BlackBerry Limited | Method for providing wireless application privilege management |
| 9542076, | May 12 2004 | Synchronoss Technologies, Inc. | System for and method of updating a personal profile |
| 9544306, | Oct 29 2013 | OMNISSA, LLC | Attempted security breach remediation |
| 9547770, | Mar 14 2012 | INTRALINKS, INC | System and method for managing collaboration in a networked secure exchange environment |
| 9552463, | Jul 03 2013 | OMNISSA, LLC | Functionality watermarking and management |
| 9553860, | Apr 27 2012 | INTRALINKS, INC | Email effectivity facility in a networked secure collaborative exchange environment |
| 9560502, | Sep 19 1997 | HELFERICH PATENT LICENSING LLC | Methods of performing actions in a cell phone based on message parameters |
| 9565212, | Mar 30 2012 | Synchronoss Technologies, Inc | Secure mobile framework |
| 9578027, | Apr 21 2005 | Seven Networks, LLC | Multiple data store authentication |
| 9584366, | Oct 26 2001 | BlackBerry Limited | System and method for controlling configuration settings for mobile communication devices and services |
| 9584437, | Jun 02 2013 | OMNISSA, LLC | Resource watermarking and management |
| 9585016, | Jul 25 2013 | OMNISSA, LLC | Data communications management |
| 9596227, | Apr 27 2012 | INTRALINKS, INC | Computerized method and system for managing an email input facility in a networked secure collaborative exchange environment |
| 9613190, | Apr 23 2014 | INTRALINKS, INC | Systems and methods of secure data exchange |
| 9615221, | Jul 21 2003 | Synchronoss Technologies, Inc. | Device message management system |
| 9626073, | Mar 19 2002 | Meta Platforms, Inc | Display navigation |
| 9654450, | Apr 27 2012 | INTRALINKS, INC | Computerized method and system for managing secure content sharing in a networked secure collaborative exchange environment with customer managed keys |
| 9659170, | Jan 02 2015 | SV CAPITAL, LLC | Securing data on untrusted devices |
| 9665723, | Aug 15 2013 | OMNISSA, LLC | Watermarking detection and management |
| 9678621, | Mar 19 2002 | Meta Platforms, Inc | Constraining display motion in display navigation |
| 9680763, | Feb 14 2012 | OMNISSA, LLC | Controlling distribution of resources in a network |
| 9686287, | Mar 15 2013 | OMNISSA, LLC | Delegating authorization to applications on a client device in a networked environment |
| 9699193, | Jul 03 2013 | OMNISSA, LLC | Enterprise-specific functionality watermarking and management |
| 9703949, | May 02 2013 | OMNISSA, LLC | Time-based configuration profile toggling |
| 9705813, | Feb 14 2012 | OMNISSA, LLC | Controlling distribution of resources on a network |
| 9712986, | Jan 11 2008 | SEVEN NETWORKS INC | Mobile device configured for communicating with another mobile device associated with an associated user |
| 9723460, | Jul 21 2003 | Synchronoss Technologies, Inc. | Device message management system |
| 9753606, | Mar 19 2002 | Meta Platforms, Inc | Animated display navigation |
| 9762553, | Apr 23 2014 | INTRALINKS, INC | Systems and methods of secure data exchange |
| 9769141, | Sep 23 2013 | OMNISSA, LLC | Securely authorizing access to remote resources |
| 9769176, | Apr 21 2005 | Seven Networks, LLC | Multiple data store authentication |
| 9787686, | Apr 12 2013 | OMNISSA, LLC | On-demand security policy activation |
| 9800454, | Jul 25 2013 | OMNISSA, LLC | Functionality management via application modification |
| 9807078, | Apr 27 2012 | INTRALINKS, INC | Computerized method and system for managing a community facility in a networked secure collaborative exchange environment |
| 9813368, | Jun 25 2001 | AT&T Intellectual Property I, LP | System and method for regulating electronic messages |
| 9813390, | Dec 06 2012 | OMNISSA, LLC | Systems and methods for controlling email access |
| 9813514, | Jun 12 2002 | Malikie Innovations Limited | Information repository system including a wireless device and related method |
| 9832095, | Dec 14 2011 | Seven Networks, Inc | Operation modes for mobile traffic optimization and concurrent management of optimized and non-optimized traffic |
| 9851864, | Mar 19 2002 | Meta Platforms, Inc | Constraining display in display navigation |
| 9882850, | Dec 06 2012 | OMNISSA, LLC | Systems and methods for controlling email access |
| 9886163, | Mar 19 2002 | Meta Platforms, Inc | Constrained display navigation |
| 9900261, | Jun 02 2013 | OMNISSA, LLC | Shared resource watermarking and management |
| 9912671, | Apr 21 2005 | Seven Networks, LLC | Multiple data store authentication |
| 9961065, | Apr 27 2012 | INTRALINKS, INC | Computerized method and system for managing an email input facility in a networked secure collaborative exchange environment |
| RE43070, | Jul 18 2000 | Qualcomm Incorporated | Identifying and locating lost or stolen personal digital assistant devices via a landline- or wireless-connected web server |
| RE43118, | Dec 14 2001 | CUFER ASSET LTD L L C | Method for determining e-mail address format rules |
| RE45348, | Oct 20 2004 | Seven Networks, Inc. | Method and apparatus for intercepting events in a communication system |
| RE46355, | Feb 27 2006 | Malikie Innovations Limited | Method and system for distributing and updating software in wireless devices |
| Patent | Priority | Assignee | Title |
| 4831582, | Nov 07 1986 | ALLEN-BRADLEY COMPANY, INC | Database access machine for factory automation network |
| 4875159, | Dec 22 1987 | Amdahl Corporation | Version management system using plural control fields for synchronizing two versions of files in a multiprocessor system |
| 4897781, | Feb 13 1987 | International Business Machines Corporation | System and method for using cached data at a local node after re-opening a file at a remote node in a distributed networking environment |
| 5263157, | Feb 15 1990 | International Business Machines Corporation | Method and system for providing user access control within a distributed data processing system by the exchange of access control profiles |
| 5386564, | Feb 24 1993 | HEWLETT-PACKARD DEVELOPMENT COMPANY, L P | Conversion of data and objects across classes in an object management system |
| 5392390, | Apr 10 1992 | Intellisync Corporation | Method for mapping, translating, and dynamically reconciling data between disparate computer platforms |
| 5572643, | Oct 19 1995 | INTERNETAD SYSTEMS LLC | Web browser with dynamic display of information objects during linking |
| 5581749, | Dec 21 1992 | TheDow Chemical Company | System and method for maintaining codes among distributed databases using a global database |
| 5600834, | May 14 1993 | Binary Services Limited Liability Company | Method and apparatus for reconciling different versions of a file |
| 5613012, | Nov 28 1994 | Open Invention Network, LLC | Tokenless identification system for authorization of electronic transactions and electronic transmissions |
| 5623601, | Nov 21 1994 | RPX Corporation | Apparatus and method for providing a secure gateway for communication and data exchanges between networks |
| 5627658, | Dec 14 1994 | Xerox Corporation | Automatic networked facsimile queuing system |
| 5634053, | Aug 29 1995 | HE HOLDINGS, INC , A DELAWARE CORP ; Raytheon Company | Federated information management (FIM) system and method for providing data site filtering and translation for heterogeneous databases |
| 5647002, | Sep 01 1995 | AVAYA Inc | Synchronization of mailboxes of different types |
| 5652884, | Nov 14 1994 | Apple Inc | Method and apparatus for dynamic update of an existing object in an object editor |
| 5666553, | Apr 10 1992 | Intellisync Corporation | Method for mapping, translating, and dynamically reconciling data between disparate computer platforms |
| 5678039, | Sep 30 1994 | Borland Software Corporation | System and methods for translating software into localized versions |
| 5680542, | Jun 07 1995 | Motorola, Inc.; Motorola, Inc | Method and apparatus for synchronizing data in a host memory with data in target MCU memory |
| 5682524, | May 26 1995 | Intellisync Corporation | Databank system with methods for efficiently storing non-uniform data records |
| 5684990, | Jan 11 1995 | Intellisync Corporation | Synchronization of disparate databases |
| 5701423, | Apr 10 1992 | Intellisync Corporation | Method for mapping, translating, and dynamically reconciling data between disparate computer platforms |
| 5706502, | Mar 26 1996 | Oracle America, Inc | Internet-enabled portfolio manager system and method |
| 5710918, | Jun 07 1995 | GOOGLE LLC | Method for distributed task fulfillment of web browser requests |
| 5713019, | Oct 26 1995 | Iconic access to remote electronic monochrome raster data format document repository | |
| 5715403, | Nov 23 1994 | CONTENTGUARD HOLDINGS, INC | System for controlling the distribution and use of digital works having attached usage rights where the usage rights are defined by a usage rights grammar |
| 5717925, | Oct 08 1993 | International Business Machines Corporation | Information catalog system with object-dependent functionality |
| 5721908, | Jun 07 1995 | GOOGLE LLC | Computer network for WWW server data access over internet |
| 5721914, | Sep 14 1995 | Verizon Patent and Licensing Inc | System and method for hierarchical data distribution |
| 5729735, | Feb 08 1995 | Remote database file synchronizer | |
| 5745360, | Aug 14 1995 | International Business Machines Corp.; IBM Corporation | Dynamic hypertext link converter system and process |
| 5757916, | Oct 06 1995 | Google Inc | Method and apparatus for authenticating the location of remote users of networked computing systems |
| 5758150, | Oct 06 1995 | Tele-Communications, Inc. | System and method for database synchronization |
| 5758354, | Apr 28 1995 | Intel Corporation | Application independent e-mail synchronization |
| 5758355, | Aug 07 1996 | WILMINGTON TRUST, NATIONAL ASSOCIATION, AS COLLATERAL AGENT | Synchronization of server database with client database using distribution tables |
| 5765171, | Dec 29 1995 | THE CHASE MANHATTAN BANK, AS COLLATERAL AGENT | Maintaining consistency of database replicas |
| 5778346, | Jan 21 1992 | Intellisync Corporation | System and methods for appointment reconcilation |
| 5790425, | Feb 19 1997 | Sun Microsystems, Inc. | Generic server benchmarking framework in a client-server environment |
| 5790790, | Oct 24 1996 | AXWAY INC | Electronic document delivery system in which notification of said electronic document is sent to a recipient thereof |
| 5799318, | Apr 13 1993 | Oracle International Corporation | Method and apparatus for collecting and displaying information from diverse computer resources |
| 5832483, | Dec 13 1996 | EMC IP HOLDING COMPANY LLC | Distributed control interface for managing the interoperability and concurrency of agents and resources in a real-time environment |
| 5870759, | Oct 09 1996 | Oracle International Corporation | System for synchronizing data between computers using a before-image of data |
| Executed on | Assignor | Assignee | Conveyance | Frame | Reel | Doc |
| Jul 22 1997 | Roampage, Inc. | (assignment on the face of the patent) | / | |||
| Jul 22 1997 | YING, CHRISTINE C | ROAMPAGE, INC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 008689 | /0576 | |
| Jul 22 1997 | WAGLE, PRASAD | ROAMPAGE, INC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 008689 | /0576 | |
| Jul 22 1997 | RIGGINS, MARK D | ROAMPAGE, INC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 008689 | /0576 | |
| Jul 22 1997 | MENDEZ, DANIEL J | ROAMPAGE, INC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 008689 | /0576 | |
| Aug 12 1997 | ROAMPAGE, INC | Visto Corporation | CHANGE OF NAME SEE DOCUMENT FOR DETAILS | 010685 | /0695 | |
| Mar 31 1998 | Visto Corporation | Silicon Valley Bank | SECURITY AGREEMENT | 009094 | /0488 | |
| Aug 03 2000 | Visto Corporation | Sand hill Capital II, LP | SECURITY INTEREST SEE DOCUMENT FOR DETAILS | 011052 | /0664 | |
| Dec 11 2000 | SAND HILL CAPITAL, LLC | FB COMMERCIAL FINANCE, INC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 011742 | /0974 | |
| Dec 11 2000 | SAND HILL CAPITAL II, L P | FB COMMERCIAL FINANCE, INC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 011742 | /0974 | |
| Dec 11 2000 | SAND HILL CAPITAL II Q, L P | FB COMMERCIAL FINANCE, INC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 011742 | /0974 | |
| Feb 13 2003 | Silicon Valley Bank | Visto Corporation | RELEASE | 013776 | /0491 | |
| Aug 12 2003 | Visto Corporation | Visto Corporation | CHANGE OF ADDRESS | 014384 | /0386 | |
| Sep 19 2012 | Visto Corporation | Good Technology Corporation | CHANGE OF NAME SEE DOCUMENT FOR DETAILS | 029347 | /0783 | |
| Jan 17 2014 | FB COMMERCIAL FINANCE, INC | Good Technology Corporation | RELEASE BY SECURED PARTY SEE DOCUMENT FOR DETAILS | 032384 | /0001 | |
| May 11 2023 | BlackBerry Limited | Malikie Innovations Limited | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 064104 | /0103 |
| Date | Maintenance Fee Events |
| Apr 15 2003 | M2551: Payment of Maintenance Fee, 4th Yr, Small Entity. |
| Apr 15 2003 | M2554: Surcharge for late Payment, Small Entity. |
| May 14 2003 | ASPN: Payor Number Assigned. |
| Aug 04 2003 | STOL: Pat Hldr no Longer Claims Small Ent Stat |
| Apr 25 2007 | REM: Maintenance Fee Reminder Mailed. |
| May 02 2007 | M1555: 7.5 yr surcharge - late pmt w/in 6 mo, Large Entity. |
| May 02 2007 | M1552: Payment of Maintenance Fee, 8th Year, Large Entity. |
| Dec 20 2010 | ASPN: Payor Number Assigned. |
| Dec 20 2010 | RMPN: Payer Number De-assigned. |
| Mar 30 2011 | M1553: Payment of Maintenance Fee, 12th Year, Large Entity. |
| Date | Maintenance Schedule |
| Oct 05 2002 | 4 years fee payment window open |
| Apr 05 2003 | 6 months grace period start (w surcharge) |
| Oct 05 2003 | patent expiry (for year 4) |
| Oct 05 2005 | 2 years to revive unintentionally abandoned end. (for year 4) |
| Oct 05 2006 | 8 years fee payment window open |
| Apr 05 2007 | 6 months grace period start (w surcharge) |
| Oct 05 2007 | patent expiry (for year 8) |
| Oct 05 2009 | 2 years to revive unintentionally abandoned end. (for year 8) |
| Oct 05 2010 | 12 years fee payment window open |
| Apr 05 2011 | 6 months grace period start (w surcharge) |
| Oct 05 2011 | patent expiry (for year 12) |
| Oct 05 2013 | 2 years to revive unintentionally abandoned end. (for year 12) |