US 8,064,583 B1Grant
Multiple data store authentication
Issue Date:2011-11-22
•20 Claims
•5 Drawing Sheets
Abstract
System and methods for authenticating access to multiple data stores are disclosed. The system may include a server coupled to a network, a client device in communication with the server via the network and a plurality of data stores. The server may authenticate access to the data stores and forward information from those stores to the client device. An exemplary authentication method receives a request for access to data. Information concerning access to that data is stored and associated with an identifier assigned to a client device. If the identifier is found to correspond to the stored information during a future request for access to the store, access to that store is granted.
Metadata
Assignee
- Seven Networks, Inc.
Inventors
- Jay Sutaria
- Brian Daniel Gustafson
- Robert Paul van Gent
- Ruth Lin
- David Merriwether
- Parvinder Sawhney
Application Information
Application Number:US 11/525,294
Filing Date:2006-09-21
Priority Date:2005-04-21
Art Unit:2614
Classifications
IPC:
H04H3/42H04H11/00
Patent Drawings (5 sheets)
Description
Cross-Reference to Related Applications
[0001] This application is a continuation of U.S. patent application Ser. No. 11/112,690 filed Apr. 21, 2005 and entitled “Systems and Methods for Simplified Provisioning,” the disclosure of which is incorporated herein by reference.
Background of the Invention
[0002] 1. Field of the Invention
[0003] The present invention relates generally to service activation, and more particularly to systems and methods for simplified provisioning and multiple data store authentication.
[0004] 2. Description of Related Art
[0005] Conventionally, a user purchasing services associated with a device needs to register with a service provider to provide specific information about the user. The service provider often has a customer service center that assists the user with registration for various services associated with the wireless device. For instance, the customer service center can record personal information about the user in order to provide wireless Internet services. The service provider typically requires billing information from the user in order to identify the user and collect monies from the user for the services being provided.
[0006] When the user activates various services, the service provider may program various databases with the user's personal information, as well as information associated with the device the user is using to access the services. This process may be referred to as “provisioning.” Often, the user spends time on the phone with a representative of the service provider in order to provide the information the service provider requires in order to program the various databases. Alternatively, the user may spend time on a device associated with the user in order to provide the requisite information for the provisioning. In exchange for providing the information to the service provider, the user obtains access to certain resources made available by the service provider.
[0007] Collecting the user's personal information and storing the information in the databases is frequently done in order to maintain security and ensure that each user pays for the resources being requested. However, users often resent the time it takes to register for access to the resources. Further, users may register many times with the same service provider for different resources available via the service provider. Numerous minutes or hours spent entering information required by the service provider may deter users from subscribing to the various resources offered by the service provider. There is, therefore, a need for a system and method for simplified provisioning.
Summary of the Invention
[0008] An exemplary embodiment of the present invention provides a system for authenticating access to multiple data stores. The exemplary embodiment may include a server, which is coupled to a network. A client device may communicate with the server via the network. Various client devices may be used in this embodiment including cellular telephones, personal digital assistants, or a personal computer. The server may be configured to authenticate access to a plurality of data stores coupled to the server. As a result of authentication, the server may access and forward information at the data stores to the client. In one example, the data stores may be associated with an electronic mail server provider.
[0009] Authentication to the plurality of data stores may occur by utilizing data provided to the server by the client device. Authentication may also occur by comparing the data provided to the server by the client device with information at the plurality of data stores, which may have been provided by the client device during a previous authentication encounter.
[0010] In some embodiments, the server may be further configured to authenticate the client device prior to the server authenticating access to the plurality of data stores. Authentication of the client device may, for example, include the user of information identifying the client device or a token, which comprises a unique string of data. Alternatively, the server may be further configured to authenticate a user of the client prior to the server authenticating access to the plurality of data stores. Authentication may include use of a user name or a user name in further combination with a password.
[0011] In another exemplary embodiment of the present invention, a computing device for authenticating access to multiple data stores is provided. The computing device may include a communications interface for exchanging information over a network; an identification module for identifying a client device or user thereof based on information provided by the client device; and a registration module for accessing multiple data stores and authenticating access to the multiple data stores by the client device or user thereof. The communications interface may also receive information from the multiple data stores following authentication and may further forward received information to the client device.
[0012] The identification module of the computing device may identify the client device based on a client identifier. The client identifier may include a unique string of data (a token), which may have been previously assigned to the client device by the identification module. The client identifier, in another embodiment, may include a telephone number or, alternatively, a user name associated with a user of the device.
[0013] The identification module, in some embodiments of the present invention, may compare the aforementioned client identifier with information at one or more of the multiple data stores. The information at the multiple data stores may include information provided by the client device during a previous authentication operation. The registration module may also query the user of the client device for information required for accessing the multiple data stores if that information is not currently present.
[0014] An exemplary embodiment of the present invention provides a method for authenticating access to multiple data stores. In the exemplary method, a request is received from a client device to access a data store. Information associated with accessing the data store is stored and an identifier is assigned to the client device, that identifier being associated with the stored information. When a subsequent request for access to the data store is received, a query is made with respect to the identifier and if the identifier corresponds to the stored information for accessing the aforementioned data store, the data store is accessed.
[0015] In another embodiment of the aforementioned method, a client device may request access to a second data store. Information associated with accessing the second data store may be stored and further associated with the identifier initially associated with information concerning the access of the first data store. Upon receipt of a subsequent request for access to the second data store, if the assigned identifier corresponds to the information associated with accessing the second data store, access is granted to that data store. The information accessed at the first and second data store may be forwarded to the client device. That information may be electronic mail.
[0016] In yet another exemplary method for authenticating access to multiple data stores, a client device request for access to a data store is received. The client device may then be queried for an identifier associated with stored information for accessing the data store. If the assigned identifier corresponds to the information associated with accessing the data store, then the store may be accessed. The method may further include the steps of accessing a further data store if the assigned identifier corresponds to information associated with accessing the further data store. The information at the data stores may then be forwarded to the client device. The information may be electronic-mail.
[0017] An embodiment of the present invention provides for a computer-readable medium having embodied thereon a program executable by a processor to perform a method for authenticating access to multiple data stores. The method may include receiving a client device request for access to a data store; storing information associated with accessing the data store; assigning an identifier to the client device, wherein the identifier is associated with the stored information for accessing the data store; receiving a subsequent request for access to the data store; querying the client device for the assigned identifier; and accessing the data store if the assigned identifier corresponds to the information associated with accessing the data store.
[0018] The computer-readable medium may further include a program executable to receive a client device request for access to a second data store; store information associated with accessing the second data store; associate the stored information for accessing the second data store with the previously assigned identifier; receive a subsequent request for access to the second data store; and access the second data store if the assigned identifier corresponds to the information associated with accessing the second data store.
[0019] In yet another embodiment of the present invention, a computer-readable medium is provided for authenticating access to multiple data stores. The method may include receiving a client device request for access to a data store; querying the client device for an identifier associated with stored information for accessing the data store; accessing the data store if the assigned identifier corresponds to the information associated with accessing the data store; and accessing a second data store if the assigned identifier corresponds to information associated with accessing the second data store. The computer-readable medium may further include program instructions for forwarding information at the data stores to the client device, wherein the forwarded information is electronic mail.
Brief Description of the Drawings
[0020] FIG. 1 shows an exemplary environment for providing simplified provisioning in accordance with one embodiment;
[0021] FIG. 2 shows a schematic diagram of an exemplary provisioning module in accordance with one embodiment;
[0022] FIG. 3 shows a flow diagram of an exemplary process for providing simplified provisioning in accordance with one embodiment; and
[0023] FIG. 4 shows a detailed process for providing simplified provisioning in accordance with one embodiment.
Detailed Description
[0024] Referring to FIG. 1 , an exemplary environment for providing simplified provisioning in accordance with one embodiment is shown. A client 102 communicates with a server 106 via a network 104. The client 102 may include any type of device, such as a cellular telephone, a personal digital assistant (PDA), a personal computer, etc.
[0025] Any type of provisioning may be provided according to various embodiments. For instance, the provisioning may include an event registering a user in response to a user request for services, a communication to the user offering services, a communication to the user including activation data, a communication to the user with a uniform resource locator (URL) where the user can obtain additional information regarding services, and so on (“provisioning event”). Any type of provisioning event is within the scope of one embodiment.
[0026] Similarly, any type of services provided by a service provider managing the provisioning events is possible. For instance, the service provider may provide internet services, application services, wireless services, and so on.
[0027] A provisioning module 108 may be coupled to the server 106 for providing provisioning event related services. In one embodiment, the provisioning module 108 is included as a component of the server 106. In another embodiment, the provisioning module 108 provides provisioning event related processing for various servers.
[0028] The server 106 may include or otherwise have access to one or more storage mediums 110. Any type of storage medium 110 may be employed according to various embodiments. In FIG. 1 , the server 106 is coupled to the storage medium(s) 110 for storing and accessing information included in the storage medium(s) 110.
[0029] In an exemplary embodiment, the client 102 contacts the server 106 via the network 104 in order to request and/or access services provided by a service provider associated with the server 106. For example, a user at the client 102 may wish to subscribe to email services available by the service provider. The server 106 requests information about the user at the client 102 or about the client 102 itself before allowing the user to access services. In order to verify that the client 102 is genuine, the server 106 may access the storage medium(s) 110 to match data provided by the client 102 with information the server 106 stored in the storage medium(s) 110 as a result of prior encounters with the client 102.
[0030] Any manner of collecting information associated with the user and/or the device 102 associated with the user may be employed. The server 106 may collect the information from previous encounters with the device 102, from other service providers associated with the user and/or the device 102, and/or from any sources providing information about the user and/or the device 102.
[0031] The server 106 utilizes the provisioning module 108 to provide specified services and configurations for those services to the user at the client 102. The provisioning module 108 may verify information associated with the client 102 in one embodiment. The provisioning module 108 may have access to the storage medium(s) 110 via the server 106 or via a direct connection to the storage medium(s) 110.
[0032] Turning now to FIG. 2 , a schematic diagram of an exemplary provisioning module 108 in accordance with one embodiment is shown. The provisioning module 108 may provide users with accounts, the appropriate access to those accounts, all the rights associated with those accounts, all of the resources necessary to manage the accounts, and so forth. Provisioning may be utilized to refer to service activation and may also involve programming various databases, such as the storage medium(s) 110, with the user's information, as discussed herein. Although the server 106 may be identified as performing various functions, any of the functions may be performed by the provisioning module 108 and/or components thereof.
[0033] The provisioning module 108 may include an identification component 202. The identification component 202 may perform various tasks related to identifying the client 102 and/or the user associated with the client 102. The identification component 202 may assign an identifier to the client 102 and/or information associated with the user at the client 102 when the client 102 is connected to the server 106. The identification component 202 may store the information in the storage medium(s) 110 according to the identifier the identification component 202 associates with the information.
[0034] In one embodiment, the identification component 202 assigns a unique identifier, such as a number string, to the client 102 and stores the information associated with the client 102 according to the unique identifier. The identification component 202 may then forward the unique identifier to the client 102 as a communication, or part of a communication, so that the client 102 can provide the unique identifier when the client 102 connects to the server 106 on another occasion.
[0035] In another embodiment, a phone number associated with the client 102 is utilized by the identification component 202 to store information associated with the client 102. Accordingly, when the client 102 makes further contact with the server 106, the phone number may be used to access the information stored according to the phone number. The user may provide the phone number associated with the client 102 and/or the client 102 may provide the phone number to the server 106 when initial access to the server 106 is gained by the client 102.
[0036] The identification component 202 may also compare information provided by the user of the client 102 with information stored in the storage medium(s) 110 related to the client 102. The comparison may be performed in order to verify that the user of the client 102 is the same user of the client 102 about which the server 106 captured information during a previous encounter. The comparison may also be performed to ensure that the client 102 information in the storage medium(s) 110 is accurate.
[0037] For instance, if the phone number is utilized as the identifier and the phone number provided by the user at the client 102 in response to a query is different from the phone number in the storage medium(s) 110, the user may have entered the phone number incorrectly, the original information gathered at the server 106 may have been entered incorrectly, and so on. The information from the storage medium(s) 110 and the client 102 may be compared for any reason. As discussed herein, the server 106 may collect the information associated with the user and/or the client 102 during previous encounters with the client 102 and/or from any other sources.
[0038] A registration component 204 may also be included with the provisioning module 108. The registration component 204 can utilize information from the storage medium(s) 110 to “pre-fill” or to otherwise fill in information associated with, a registration for the user associated with the client 102. The server 106 captures information about the user when the client 102 accesses the server 106 initially and/or from any other source, as discussed herein.
[0039] For example, when the client 102 logs onto the server 106 to check email, the server 106 may capture the phone number of the client 102, the username of the user associated with the client 102, or any other information associated with the client 102. The information is stored in the storage medium(s) 110 according to a unique identifier assigned by the identification component 202, according to the phone number associated with the client 102, or according to any other method. When the client 102 logs onto the server 106 again in order to request instant messaging services, for example, the registration component 204 accesses the information in the storage medium(s) 110 in order to complete a registration for the user at the client 102 requesting the services.
[0040] The registration component 204 can then query the user for any information needed for registration that is not included in the information in the storage medium(s) 110. In one embodiment, information associated with the user and the client 102 is collected by the server 106 from other sources, rather than from a previous encounter the client 102 had with the server 106, as discussed herein. For instance, another service provider may forward information associated with the client 102, the server 106 may access information about the client 102 on available databases utilizing the phone number or other information about the client 102, and so forth. Any manner of gathering information about the client 102 to pre-fill the registration for services is within the scope of an embodiment.
[0041] The registration component 204 can register the user at the client 102 for any services offered by the service provider associated with the server 106, or otherwise. In one embodiment, the registration component 204 can pre-fill information related to services being requested by the user other than identification information. For instance, the server 106 may store information related to user preferences in the storage medium(s) 110. When the user requests services, the registration component 204 may utilize the user preferences information to pre-fill feature selections associated with the requested services. For example, the registration component 204 may pre-select calendar features for the user according to user preferences captured by the server 106 about user activity related to other services, whether those services are offered by the service provider or not.
[0042] A billing component 206 may be included with the provisioning module 108. The billing component 206 can track user activity of the services provided by the service provider. Accordingly, the billing component 206 can determine when to bill the user for the services being provided. The registration component 204 can provide user information to the billing component 206 that may be needed regarding where to bill the user, such as an email address, for instance.
[0043] An application generator 208 may be included with the provisioning module 108 for configuring the application and/or services requested by the user for the device 102 associated with the user. The application generator 208 can also create the application for the user including any features the user desires. Any type of application generator, 208 may be provided.
[0044] In one embodiment, the application generator 208 may utilize provisioning templates to create the profiles for configuring various devices, such as the client 102 (FIG. 1 ) associated with the user. For instance, the templates may provide the parameters for creating a particular application. The user can also specify customizations to the application, which can be used to modify the template for the application by the application generator 208. In other words, the provisioning templates can provide parameters for configuring various devices for the services as well as customizing the actual service features.
[0045] A communications interface 210 may also be provided with the provisioning module 108. The communications interface 210 receives communications from the user and/or the server 106 and processes the input utilizing the components discussed herein.
[0046] Although the provisioning module 108 is described as including various components, the provisioning module 108 may include more components or fewer components than those listed and still fall within the scope of an embodiment of the invention. For example, the provisioning module 108 may also include business rules for building the applications, a customer service component for managing applications and errors, a protocol configuration component for managing a variety of protocols associated with various devices, and so forth.
[0047] FIG. 3 shows a flow diagram of an exemplary process for providing simplified provisioning in accordance with one embodiment. At step 302, information associated with a user during a non-provisioning event is stored. As discussed herein, the information may be stored in the storage medium(s) 110. The server 106 collects information about the user and the client 102 associated with the user when contact is made with the server 106 at a time when provisioning is not occurring. In one embodiment, as discussed herein, the server may collect information related to the user and the client 102 from another source, rather than from the client 102, which also may constitute a non-provisioning event.
[0048] In one embodiment, the information related to the user and the client 102 may be collected during one or more previous provisioning events. For instance, the server 106 may store information associated with the user and the client 102 during previous provisioning events in order to avoid or limit querying the user for the same information during future provisioning events.
[0049] The information may be stored according to a phone number associated with the device 102 and/or according to a unique identifier assigned to the device 102. For example, the server 106 may assign a unique identifier to the information collected from the device 102 when the device 102 is connected to the server 106. In order to associate the unique identifier to the device 102 for recognition during future contact with the server 106, a text message, for example, can be sent to the device 102 with the unique identifier. The unique identifier may then be sent back to the server 106 to identify the device 102 if the phone number, for example, cannot be accessed by the server 106. As discussed herein, in one embodiment, the server 106 receives information about the user and/or the client 102 from a third party source and stores the information according to the phone number and/or a unique identifier.
[0050] At step 304, the information is utilized to pre-fill a registration related to a provisioning event. The information collected by the server 106 from the client 102 during a previous contact with the server 106 and/or from another source (e.g., phone network) is utilized to complete as much of a registration as possible without user input. Accordingly, the user at the client 102 is not required to provide information that the server 106 can access itself.
[0051] At step 306, one or more communications are forwarded to the user. The one or more communications are based on the information stored and request information to complete the registration for the provisioning event. In one embodiment, the information requested to complete the registration includes a user query to verify that the information used to complete the registration is correct. The information requested may include a user query to provide a password to complete the registration process, in another embodiment.
[0052] By using the information collected by the server 106 during a non-provisioning event that occurred prior to a current provisioning event to complete a registration, or a portion of the registration, the user at the client 102 can provide less information than required if no information about the user was accessible or utilized to pre-fill the registration. Accordingly, the user at the client 102 is provided with simplified provisioning.
[0053] Turning now to FIG. 4 , a detailed process for providing simplified provisioning in accordance with one embodiment is shown. At step 402, information associated with a user is stored. As discussed herein, the information may be stored by the server 106 to one or more storage mediums, such as the storage medium(s) 110 discussed in FIG. 1 .
[0054] An identifier is assigned to the information at step 404. The identifier may be assigned to the information in order to locate the information in the storage medium(s) 110, in order to compare the information with other information provided by the user during future contacts with the server 106, and so on. The identifier may be assigned to the information for any reason. As discussed herein, the identifier may be a phone number associated with a device of the user, such as the device 102 discussed in FIG. 1 , a unique identifier assigned by the identification component 202 of the provisioning module 108 associated with the server 106, and/or any other type of identifier.
[0055] At step 406, the user is queried for identification during a provisioning event. The identification sought from the user may be confirmation of the identifier used to store the information at step 404, such as the phone number and/or the unique identifier. The identification sought, however, may be any type of information from the user. For example, a “username” may be sought in order to match the username associated with the user with the username stored in the storage medium(s) 110.
[0056] At step 408, the information is accessed in order to match the identification from the user with the identifier associated with the information in response to receiving the identification from the user. The provisioning module 108 accesses the information in the storage medium(s) 110, directly or via the server 106, associated with the user and compares that information with the identification received from the user in response to the query.
[0057] By locating the information in the storage medium(s) 110 that was previously collected, the information can be utilized to register the user during the provisioning event at step 410. The information can complete the registration or a portion of the registration associated with the services for which the provisioning event is taking place. By completing the registration or a portion of the registration with information existing about the user and the user device, such as the device 102 discussed in FIG. 1 , the user is only required to provide data for the registration not included in the information from the storage medium(s) 110. Thus, the user experiences a streamlined provisioning process.
[0058] In one embodiment, as discussed herein, the information is utilized to complete the registration and the user is queried to verify that the information utilized is correct. In another embodiment, the user is queried to verify the accuracy of the information utilized according to a length of time between the provisioning event and when the information was collected. For instance, if the information was collected by the server 106 less than one month prior to the provisioning event, the server 106 may not seek verification from the user that the information is still accurate.
[0059] At step 412, the user is queried for a password in order to complete the provisioning event. The password may help to ensure that an intended user receives services. For instance, the server 106 may forward the communication regarding services to a user that did not request the services or requested the services using another user's information. Provisioning related information may erroneously reach users for a variety of reasons. The user is queried for the password in order to verify that the user matches the intended user. For instance, if the provisioning information is sent to a “user b” rather than the intended “user a,” “user b” will likely not know the “user a” password and resultantly will not be able to receive the services intended to go to the “user a.”
[0060] The provisioning event is completed in response to receiving the password at step 414. The password is compared with a password in the storage medium(s) 110. Provided the password matches the password known for the particular user, the provisioning event may be completed. In one embodiment, the server 106 accesses another database with user password information in order to confirm that the password provided is correct. Any method of verifying the password may be employed.
[0061] As discussed herein, the information from the storage medium(s) 110 may be sufficient for completing the registration for the service provider. However, the service provider may require additional information to complete the registration. For instance, the information about the user and/or the client 102 associated with the user the server 106 originally captured may not provide enough information about the user and/or the client 102 required for the registration for the services associated with the provisioning event. Accordingly, more information may be collected from the user. As part of the simplified provisioning process described in FIG. 4 , or any other exemplary provisioning process, the user may be queried for additional information to complete the registration.
[0062] In one embodiment, the server 106 stores information associated with the user during the client 102 connection with the server sometime prior to the provisioning event. Using the provisioning templates, discussed in FIG. 2 in connection with the application generator 208, the server 106 may collect other information about the user from third party databases in order to complete registration for provisioning for many of the service provider's services based on the provisioning templates. Any type of method for gathering information about the user and/or the device 102 associated with the user for simplifying provisioning is within the scope of various embodiments.
[0063] While various embodiments have been described above, it should be understood that they have been presented by way of example only, and not limitation. For example, any of the elements associated with the provisioning module may employ any of the desired functionality set forth hereinabove. Thus, the breadth and scope of a preferred embodiment should not be limited by any of the above-described exemplary embodiments. These embodiments include computer programs embodied on computer readable mediums for executing the methods disclosed herein.
Claims
What is claimed is:
1. A system for authenticating access to one or more data stores, comprising:
a server communicatively coupled to a network and the one or more data stores, wherein the server is configured to:
generate a unique identifier for a client device upon the client device initially communicating with the server;
send the unique identifier to the client device so that the client device can present the unique identifier in a subsequent communication with the server;
receive registration information from the client device;
store the registration information;
associate the stored registration information with the unique identifier of the client device;
receive via a subsequent communication with the client device a request to authenticate the client device to access the one or more data stores, wherein the request includes the unique identifier;
use the unique identifier to retrieve the stored registration information that is associated with the client device;
authenticate access to the one or more data stores on behalf of the client device using the stored registration information, and
forward information from the one or more data stores to the client device following authentication.
2. The system of claim 1, wherein the one or more data stores is associated with an electronic mail service provider.
3. The system of claim 1, wherein the client device is a cellular telephone.
4. The system of claim 1, wherein the client device is a personal digital assistant.
5. The system of claim 1, wherein the client device is a personal computer.
6. The system of claim 1, wherein the server authenticates the client device prior to the server authenticating access to the one or more data stores.
7. The system of claim 1, wherein the server authenticates a user of the client device prior to the server authenticating access to the one or more data stores.
8. The system of claim 6, wherein the authentication of the client device includes the use of the unique identifier.
9. The system of claim 6, wherein the unique identifier is a token, the token comprising a unique string of data.
10. The system of claim 7, wherein the authentication of the user of the client device includes the use of a user name.
11. The system of claim 10, wherein the authentication of the user of the client device includes the use of the user name in combination with a password.
12. A computing device for authenticating access to one or more data stores, comprising:
a communications interface that exchanges registration information and identification information over a network;
an identification module stored in memory and executable by a processor to:
create a unique identifier for a client device when the client device initially communicates with the computing device;
send to the unique identifier to the client device so that the client device can provide the unique identifier for verification purposes when the client device subsequently communicates with the computer device;
receive registration information from the client device;
store the registration information received from the client device; and
associate the unique identifier with the stored registration information so that the unique identifier can be used to retrieve the stored registration information when the client device subsequently communicates with the computing device; and
a registration module stored in memory and executable by a processor to:
receive via a subsequent communication with the client device a request to authenticate the client device to access the one or more data stores, wherein the request includes the unique identifier;
use the unique identifier to retrieve the stored registration information previously received from the client device;
query the client device for registration information required for accessing the one or more data stores that is not currently present in the stored registration information;
authenticate access to the one or more data stores by the client device using the stored registration information and/or the additional registration information, wherein the client device need not make contact with the one or more data stores for the purpose of authentication.
13. The computing device of claim 12, wherein the communications interface receives information from the one or more data stores following authentication of the client device or user thereof.
14. The computing device of claim 13, wherein the communication interface forwards the information received from the one or more data stores to the client device.
15. The computing device of claim 12, wherein the unique identifier is a token comprising a unique string of data.
16. The computing device of claim 12, wherein the unique identifier is a telephone number.
17. A method for authenticating access to one or more data stores, comprising:
receiving at a server registration information from a client device;
generating a unique identifier for a client device upon the client device initially communicating with the server;
sending the unique identifier to the client device so that the client device can present the unique identifier in a subsequent communication with the server;
storing the registration information associated with accessing the one or more data stores;
assigning the unique identifier to the stored registration information;
receiving a subsequent request from the client device to authenticate the client device to access the one or more data stores;
querying the client device to provide the unique identifier instead of the registration information upon determination that the registration information has been previously provided by the client device;
accessing the stored registration information assigned to the unique identifier;
using the stored registration information to authenticate the client device to access the one or more data stores.
18. The method of claim 17, further comprising querying the user to verify that the collected registration information associated with the unique identifier is correct.
19. The method of claim 18, wherein the user is queried to verify the accuracy of the collected registration information according to a length of time between registering the user for the requested service and when the collected information was collected.
20. The method of claim 18, further comprising querying the user for a password to complete the registration for the requested service.
Patent Citations (867)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US222458(A) | 1879-12-01 | Connolly et al. | Applicant |
| US447918(A) | 1891-03-01 | Strowger | Applicant |
| US4200770(A) | 1980-04-01 | Hellman et al. | Applicant |
| US4255796(A) | 1981-03-01 | Gabbe et al. | Applicant |
| US4276597(A) | 1981-06-01 | Dissly et al. | Applicant |
| US4531020(A) | 1985-07-01 | Wechselberger et al. | Applicant |
| US4807182(A) | 1989-02-01 | Queen | Applicant |
| US4831582(A) | 1989-05-01 | Miller et al. | Applicant |
| US4875159(A) | 1989-10-01 | Cary et al. | Applicant |
| US4897781(A) | 1990-01-01 | Chang et al. | Applicant |
| US4972457(A) | 1990-11-01 | O'Sullivan | Applicant |
| US5008853(A) | 1991-04-01 | Bly et al. | Applicant |
| US5220657(A) | 1993-06-01 | Bly et al. | Applicant |
| US5263157(A) | 1993-11-01 | Janis | Applicant |
| US5283856(A) | 1994-02-01 | Gross et al. | Applicant |
| US5357431(A) | 1994-10-01 | Nakada et al. | Applicant |
| US5384892(A) | 1995-01-01 | Strong | Applicant |
| US5386564(A) | 1995-01-01 | Shearer et al. | Applicant |
| US5392390(A) | 1995-02-01 | Crozier | Applicant |
| US5434994(A) | 1995-07-01 | Shaheen et al. | Applicant |
| US5436960(A) | 1995-07-01 | Campana, Jr. et al. | Applicant |
| US5438611(A) | 1995-08-01 | Campana, Jr. et al. | Applicant |
| US5479472(A) | 1995-12-01 | Campana, Jr. et al. | Applicant |
| US5487100(A) | 1996-01-01 | Kane | Applicant |
| US5493692(A) | 1996-02-01 | Theimer et al. | Applicant |
| US5519606(A) | 1996-05-01 | Frid-Nielsen et al. | Applicant |
| US5555376(A) | 1996-09-01 | Theimer et al. | Applicant |
| US5559800(A) | 1996-09-01 | Mousseau et al. | Applicant |
| US5572571(A) | 1996-11-01 | Shirai | Applicant |
| US5572643(A) | 1996-11-01 | Judson | Applicant |
| US5574859(A) | 1996-11-01 | Yeh | Applicant |
| US5581749(A) | 1996-12-01 | Hossain et al. | Applicant |
| US5600834(A) | 1997-02-01 | Howard | Applicant |
| US5603054(A) | 1997-02-01 | Theimer et al. | Applicant |
| US5604788(A) | 1997-02-01 | Tett | Applicant |
| US5613012(A) | 1997-03-01 | Hoffman et al. | Applicant |
| US5619507(A) | 1997-04-01 | Tsuda | Applicant |
| US5619648(A) | 1997-04-01 | Canale et al. | Applicant |
| US5623601(A) | 1997-04-01 | Vu | Applicant |
| US5625670(A) | 1997-04-01 | Campana, Jr. et al. | Applicant |
| US5625815(A) | 1997-04-01 | Maier et al. | Applicant |
| US5627658(A) | 1997-05-01 | Connors et al. | Applicant |
| US5630081(A) | 1997-05-01 | Rybicki et al. | Applicant |
| US5631946(A) | 1997-05-01 | Campana, Jr. et al. | Applicant |
| US5632018(A) | 1997-05-01 | Otorii | Applicant |
| US5634053(A) | 1997-05-01 | Noble et al. | Applicant |
| US5647002(A) | 1997-07-01 | Brunson | Applicant |
| US5652884(A) | 1997-07-01 | Palevich | Applicant |
| US5664207(A) | 1997-09-01 | Crumpler et al. | Applicant |
| US5666530(A) | 1997-09-01 | Clark et al. | Applicant |
| US5666553(A) | 1997-09-01 | Crozier | Applicant |
| US5680542(A) | 1997-10-01 | Mulchandani et al. | Applicant |
| US5682524(A) | 1997-10-01 | Freund et al. | Applicant |
| US5684990(A) | 1997-11-01 | Boothby | Applicant |
| US5689654(A) | 1997-11-01 | Kikinis et al. | Applicant |
| US5692039(A) | 1997-11-01 | Brankley et al. | Applicant |
| US5696903(A) | 1997-12-01 | Mahany | Applicant |
| US5701423(A) | 1997-12-01 | Crozier | Applicant |
| US5701469(A) | 1997-12-01 | Brandli et al. | Applicant |
| US5704029(A) | 1997-12-01 | Wright, Jr. | Applicant |
| US5706211(A) | 1998-01-01 | Beletic et al. | Applicant |
| US5706502(A) | 1998-01-01 | Foley et al. | Applicant |
| US5706507(A) | 1998-01-01 | Schloss | Applicant |
| US5710918(A) | 1998-01-01 | Lagarde et al. | Applicant |
| US5713019(A) | 1998-01-01 | Keaten | Applicant |
| US5715403(A) | 1998-02-01 | Stefik | Applicant |
| US5717925(A) | 1998-02-01 | Harper et al. | Applicant |
| US5721908(A) | 1998-02-01 | Lagarde et al. | Applicant |
| US5721914(A) | 1998-02-01 | DeVries | Applicant |
| US5727202(A) | 1998-03-01 | Kucala | Applicant |
| US5729549(A) | 1998-03-01 | Kostreski et al. | Applicant |
| US5729704(A) | 1998-03-01 | Stone et al. | Applicant |
| US5729735(A) | 1998-03-01 | Meyering | Applicant |
| US5742905(A) | 1998-04-01 | Pepe et al. | Applicant |
| US5745360(A) | 1998-04-01 | Leone et al. | Applicant |
| US5752186(A) | 1998-05-01 | Malackowski et al. | Applicant |
| US5752246(A) | 1998-05-01 | Rogers et al. | Applicant |
| US5754938(A) | 1998-05-01 | Herz et al. | Applicant |
| US5757916(A) | 1998-05-01 | MacDoran et al. | Applicant |
| US5758088(A) | 1998-05-01 | Bezaire et al. | Applicant |
| US5758150(A) | 1998-05-01 | Bell et al. | Applicant |
| US5758322(A) | 1998-05-01 | Rongley | Applicant |
| US5758354(A) | 1998-05-01 | Huang et al. | Applicant |
| US5758355(A) | 1998-05-01 | Buchanan | Applicant |
| US5765171(A) | 1998-06-01 | Gehani et al. | Applicant |
| US5778346(A) | 1998-07-01 | Frid-Nielsen et al. | Applicant |
| US5778361(A) | 1998-07-01 | Nanjo et al. | Applicant |
| US5781614(A) | 1998-07-01 | Brunson | Applicant |
| US5781901(A) | 1998-07-01 | Kuzma | Applicant |
| US5781906(A) | 1998-07-01 | Aggarwal et al. | Applicant |
| US5785355(A) | 1998-07-01 | Main | Applicant |
| US5787430(A) | 1998-07-01 | Doeringer et al. | Applicant |
| US5787441(A) | 1998-07-01 | Beckhardt | Applicant |
| US5790425(A) | 1998-08-01 | Wagle | Applicant |
| US5790790(A) | 1998-08-01 | Smith et al. | Applicant |
| US5790974(A) | 1998-08-01 | Tognazzini | Applicant |
| US5793413(A) | 1998-08-01 | Hylton et al. | Applicant |
| US5794210(A) | 1998-08-01 | Goldhaber et al. | Applicant |
| US5799318(A) | 1998-08-01 | Cardinal et al. | Applicant |
| US5802312(A) | 1998-09-01 | Lazaridis et al. | Applicant |
| US5802454(A) | 1998-09-01 | Goshay et al. | Applicant |
| US5802518(A) | 1998-09-01 | Karaev et al. | Applicant |
| US5802524(A) | 1998-09-01 | Flowers et al. | Applicant |
| US5806074(A) | 1998-09-01 | Souder et al. | Applicant |
| US5809242(A) | 1998-09-01 | Shaw et al. | Applicant |
| US5809415(A) | 1998-09-01 | Rossmann | Applicant |
| US5818437(A) | 1998-10-01 | Grover et al. | Applicant |
| US5819172(A) | 1998-10-01 | Campana, Jr. et al. | Applicant |
| US5819274(A) | 1998-10-01 | Jackson, Jr. | Applicant |
| US5819284(A) | 1998-10-01 | Farber et al. | Applicant |
| US5822324(A) | 1998-10-01 | Kostresti et al. | Applicant |
| US5822747(A) | 1998-10-01 | Graefe et al. | Applicant |
| US5826269(A) | 1998-10-01 | Hussey | Applicant |
| US5831664(A) | 1998-11-01 | Wharton et al. | Applicant |
| US5832483(A) | 1998-11-01 | Barker | Applicant |
| US5832489(A) | 1998-11-01 | Kucala | Applicant |
| US5832500(A) | 1998-11-01 | Burrows | Applicant |
| US5835722(A) | 1998-11-01 | Bradshaw et al. | Applicant |
| US5838252(A) | 1998-11-01 | Kikinis | Applicant |
| US5838768(A) | 1998-11-01 | Sumar et al. | Applicant |
| US5838973(A) | 1998-11-01 | Carpenter-Smith et al. | Applicant |
| US5845278(A) | 1998-12-01 | Kirsch et al. | Applicant |
| US5852775(A) | 1998-12-01 | Hidary | Applicant |
| US5852820(A) | 1998-12-01 | Burrows | Applicant |
| US5857201(A) | 1999-01-01 | Wright, Jr. et al. | Applicant |
| US5862223(A) | 1999-01-01 | Walker et al. | Examiner |
| US5867665(A) | 1999-02-01 | Butman et al. | Applicant |
| US5867817(A) | 1999-02-01 | Catallo et al. | Applicant |
| US5870759(A) | 1999-02-01 | Bauer et al. | Applicant |
| US5884323(A) | 1999-03-01 | Hawkins et al. | Applicant |
| US5889845(A) | 1999-03-01 | Staples et al. | Applicant |
| US5890147(A) | 1999-03-01 | Peltonen et al. | Applicant |
| US5892909(A) | 1999-04-01 | Grasso et al. | Applicant |
| US5898780(A) | 1999-04-01 | Liu et al. | Applicant |
| US5898917(A) | 1999-04-01 | Batni et al. | Applicant |
| US5903723(A) | 1999-05-01 | Beck et al. | Applicant |
| US5907618(A) | 1999-05-01 | Gennaro et al. | Applicant |
| US5909689(A) | 1999-06-01 | Van Ryzin | Applicant |
| US5913032(A) | 1999-06-01 | Schwartz et al. | Applicant |
| US5924096(A) | 1999-07-01 | Draper et al. | Applicant |
| US5928325(A) | 1999-07-01 | Shaughnessy et al. | Applicant |
| US5928329(A) | 1999-07-01 | Clark et al. | Applicant |
| US5937161(A) | 1999-08-01 | Mulligan et al. | Applicant |
| US5943676(A) | 1999-08-01 | Boothby | Applicant |
| US5948066(A) | 1999-09-01 | Whalen et al. | Applicant |
| US5951636(A) | 1999-09-01 | Zerber | Applicant |
| US5960394(A) | 1999-09-01 | Gould et al. | Applicant |
| US5960406(A) | 1999-09-01 | Rasansky et al. | Applicant |
| US5961590(A) | 1999-10-01 | Mendez et al. | Applicant |
| US5963642(A) | 1999-10-01 | Goldstein | Applicant |
| US5964833(A) | 1999-10-01 | Kikinis | Applicant |
| US5968131(A) | 1999-10-01 | Mendez et al. | Applicant |
| US5974238(A) | 1999-10-01 | Chase, Jr. | Applicant |
| US5974327(A) | 1999-10-01 | Agrawal et al. | Applicant |
| US5978837(A) | 1999-11-01 | Foladare et al. | Applicant |
| US5978933(A) | 1999-11-01 | Wyld et al. | Applicant |
| US5987440(A) | 1999-11-01 | O'Neil et al. | Applicant |
| US6000000(A) | 1999-12-01 | Hawkins et al. | Applicant |
| US6003070(A) | 1999-12-01 | Frantz | Applicant |
| US6006274(A) | 1999-12-01 | Hawkins et al. | Applicant |
| US6016478(A) | 2000-01-01 | Zhang et al. | Applicant |
| US6016520(A) | 2000-01-01 | Facq et al. | Applicant |
| US6018762(A) | 2000-01-01 | Brunson et al. | Applicant |
| US6023700(A) | 2000-02-01 | Owens et al. | Applicant |
| US6023708(A) | 2000-02-01 | Mendez et al. | Applicant |
| US6029238(A) | 2000-02-01 | Furukawa | Applicant |
| US6034621(A) | 2000-03-01 | Kaufman | Applicant |
| US6035104(A) | 2000-03-01 | Zahariev | Applicant |
| US6044372(A) | 2000-03-01 | Rothfus et al. | Applicant |
| US6044381(A) | 2000-03-01 | Boothby et al. | Applicant |
| US6047051(A) | 2000-04-01 | Ginzboorg et al. | Applicant |
| US6047327(A) | 2000-04-01 | Tso et al. | Applicant |
| US6052563(A) | 2000-04-01 | Macko | Applicant |
| US6052735(A) | 2000-04-01 | Ulrich et al. | Applicant |
| US6057855(A) | 2000-05-01 | Barkans | Applicant |
| US6065055(A) | 2000-05-01 | Hughes et al. | Applicant |
| US6073138(A) | 2000-06-01 | de l'Etraz et al. | Applicant |
| US6073142(A) | 2000-06-01 | Geiger et al. | Applicant |
| US6073165(A) | 2000-06-01 | Narasimhan et al. | Applicant |
| US6085166(A) | 2000-07-01 | Beckhardt et al. | Applicant |
| US6085192(A) | 2000-07-01 | Mendez et al. | Applicant |
| US6088677(A) | 2000-07-01 | Spurgeon | Applicant |
| US6101320(A) | 2000-08-01 | Schuetze et al. | Applicant |
| US6101480(A) | 2000-08-01 | Conmy et al. | Applicant |
| US6101531(A) | 2000-08-01 | Eggleston et al. | Applicant |
| US6112181(A) | 2000-08-01 | Shear et al. | Applicant |
| US6119014(A) | 2000-09-01 | Alperovich et al. | Applicant |
| US6119171(A) | 2000-09-01 | Alkhatib | Applicant |
| US6125369(A) | 2000-09-01 | Wu et al. | Applicant |
| US6125388(A) | 2000-09-01 | Reisman | Applicant |
| US6128627(A) | 2000-10-01 | Mattis et al. | Applicant |
| US6130898(A) | 2000-10-01 | Kostreski et al. | Applicant |
| US6131096(A) | 2000-10-01 | Ng et al. | Applicant |
| US6131116(A) | 2000-10-01 | Riggins et al. | Applicant |
| US6134432(A) | 2000-10-01 | Holmes et al. | Applicant |
| US6138013(A) | 2000-10-01 | Blanchard et al. | Applicant |
| US6138124(A) | 2000-10-01 | Beckhardt | Applicant |
| US6138128(A) | 2000-10-01 | Perkowitz et al. | Applicant |
| US6138146(A) | 2000-10-01 | Moon et al. | Applicant |
| US6141664(A) | 2000-10-01 | Boothby | Applicant |
| US6151606(A) | 2000-11-01 | Mendez | Applicant |
| US6157630(A) | 2000-12-01 | Adler et al. | Applicant |
| US6161140(A) | 2000-12-01 | Moriya | Applicant |
| US6167379(A) | 2000-12-01 | Dean et al. | Applicant |
| US6167435(A) | 2000-12-01 | Druckenmiller et al. | Applicant |
| US6170014(B1) | 2001-01-01 | Darago et al. | Examiner |
| US6173312(B1) | 2001-01-01 | Atarashi et al. | Applicant |
| US6173446(B1) | 2001-01-01 | Khan et al. | Applicant |
| US6175831(B1) | 2001-01-01 | Weinreich et al. | Applicant |
| US6178419(B1) | 2001-01-01 | Legh-Smith et al. | Applicant |
| US6181935(B1) | 2001-01-01 | Gossman et al. | Applicant |
| US6195533(B1) | 2001-02-01 | Tkatch et al. | Applicant |
| US6198696(B1) | 2001-03-01 | Korpi et al. | Applicant |
| US6198922(B1) | 2001-03-01 | Baynham | Applicant |
| US6201469(B1) | 2001-03-01 | Balch et al. | Applicant |
| US6202085(B1) | 2001-03-01 | Benson et al. | Applicant |
| US6205448(B1) | 2001-03-01 | Kruglikov et al. | Applicant |
| US6212529(B1) | 2001-04-01 | Boothby et al. | Applicant |
| US6219694(B1) | 2001-04-01 | Lazaridis et al. | Applicant |
| US6221877(B1) | 2001-04-01 | Aronov et al. | Applicant |
| US6223187(B1) | 2001-04-01 | Boothby et al. | Applicant |
| US6226686(B1) | 2001-05-01 | Rothschild et al. | Applicant |
| US6233341(B1) | 2001-05-01 | Riggins | Applicant |
| US6243705(B1) | 2001-06-01 | Kucala | Applicant |
| US6246875(B1) | 2001-06-01 | Seazholtz et al. | Applicant |
| US6247135(B1) | 2001-06-01 | Feague | Applicant |
| US6249808(B1) | 2001-06-01 | Seshadri | Applicant |
| US6256666(B1) | 2001-07-01 | Singhal | Applicant |
| US6263201(B1) | 2001-07-01 | Hashimoto et al. | Applicant |
| US6263340(B1) | 2001-07-01 | Green | Applicant |
| US6269369(B1) | 2001-07-01 | Robertson | Applicant |
| US6272545(B1) | 2001-08-01 | Flanagin et al. | Applicant |
| US6275850(B1) | 2001-08-01 | Beyda et al. | Applicant |
| US6289212(B1) | 2001-09-01 | Stein et al. | Applicant |
| US6292904(B1) | 2001-09-01 | Broomhall et al. | Applicant |
| US6295541(B1) | 2001-09-01 | Bodnar et al. | Applicant |
| US6300947(B1) | 2001-10-01 | Kanevsky | Applicant |
| US6304881(B1) | 2001-10-01 | Halim et al. | Applicant |
| US6308201(B1) | 2001-10-01 | Pivowar et al. | Applicant |
| US6317594(B1) | 2001-11-01 | Gossman et al. | Applicant |
| US6320943(B1) | 2001-11-01 | Borland | Applicant |
| US6324541(B1) | 2001-11-01 | de l'Etraz et al. | Applicant |
| US6324542(B1) | 2001-11-01 | Wright, Jr. et al. | Applicant |
| US6324544(B1) | 2001-11-01 | Alam et al. | Applicant |
| US6324587(B1) | 2001-11-01 | Trenbeath et al. | Applicant |
| US6327586(B1) | 2001-12-01 | Kisiel | Applicant |
| US6336117(B1) | 2002-01-01 | Massarani | Applicant |
| US6356937(B1) | 2002-03-01 | Montville et al. | Applicant |
| US6363352(B1) | 2002-03-01 | Dailey et al. | Applicant |
| US6370566(B2) | 2002-04-01 | Discolo et al. | Applicant |
| US6377810(B1) | 2002-04-01 | Geiger et al. | Applicant |
| US6380959(B1) | 2002-04-01 | Wang et al. | Applicant |
| US6389455(B1) | 2002-05-01 | Fuisz | Applicant |
| US6389457(B2) | 2002-05-01 | Lazaridis et al. | Applicant |
| US6397057(B1) | 2002-05-01 | Malackowski et al. | Applicant |
| US6397230(B1) | 2002-05-01 | Carmel et al. | Applicant |
| US6401104(B1) | 2002-06-01 | LaRue et al. | Applicant |
| US6401112(B1) | 2002-06-01 | Boyer et al. | Applicant |
| US6401113(B2) | 2002-06-01 | Lazaridis et al. | Applicant |
| US6405197(B2) | 2002-06-01 | Gilmour | Applicant |
| US6411696(B1) | 2002-06-01 | Iverson et al. | Applicant |
| US6415031(B1) | 2002-07-01 | Colligan et al. | Applicant |
| US6418308(B1) | 2002-07-01 | Heinonen et al. | Applicant |
| US6421669(B1) | 2002-07-01 | Gilmour et al. | Applicant |
| US6421781(B1) | 2002-07-01 | Fox et al. | Applicant |
| US6430602(B1) | 2002-08-01 | Kay et al. | Applicant |
| US6438585(B2) | 2002-08-01 | Mousseau et al. | Applicant |
| US6438612(B1) | 2002-08-01 | Ylonen et al. | Applicant |
| US6442589(B1) | 2002-08-01 | Takahashi et al. | Applicant |
| US6442637(B1) | 2002-08-01 | Hawkins et al. | Applicant |
| US6446118(B1) | 2002-09-01 | Gottlieb | Applicant |
| US6463463(B1) | 2002-10-01 | Godfrey et al. | Applicant |
| US6463464(B1) | 2002-10-01 | Lazaridis et al. | Applicant |
| US6487557(B1) | 2002-11-01 | Nagatomo | Applicant |
| US6487560(B1) | 2002-11-01 | LaRue et al. | Applicant |
| US6490353(B1) | 2002-12-01 | Tan | Applicant |
| US6496802(B1) | 2002-12-01 | van Zoest et al. | Applicant |
| US6499054(B1) | 2002-12-01 | Hesselink et al. | Applicant |
| US6505214(B1) | 2003-01-01 | Sherman et al. | Applicant |
| US6516327(B1) | 2003-02-01 | Zondervan et al. | Applicant |
| US6526506(B1) | 2003-02-01 | Lewis | Applicant |
| US6529908(B1) | 2003-03-01 | Piett et al. | Applicant |
| US6532446(B1) | 2003-03-01 | King | Applicant |
| US6535892(B1) | 2003-03-01 | LaRue et al. | Applicant |
| US6546005(B1) | 2003-04-01 | Berkley et al. | Applicant |
| US6549939(B1) | 2003-04-01 | Ford et al. | Applicant |
| US6556217(B1) | 2003-04-01 | Mäkipää et al. | Applicant |
| US6593944(B1) | 2003-07-01 | Nicolas et al. | Applicant |
| US6601026(B2) | 2003-07-01 | Appelt et al. | Applicant |
| US6615253(B1) | 2003-09-01 | Bowman-Amuah | Applicant |
| US6618710(B1) | 2003-09-01 | Zondervan et al. | Applicant |
| US6625621(B2) | 2003-09-01 | Tan et al. | Applicant |
| US6636482(B2) | 2003-10-01 | Cloonan et al. | Applicant |
| US6639693(B1) | 2003-10-01 | Ejiri et al. | Applicant |
| US6640097(B2) | 2003-10-01 | Corrigan et al. | Applicant |
| US6640244(B1) | 2003-10-01 | Bowman-Amuah | Applicant |
| US6640249(B1) | 2003-10-01 | Bowman-Amuah | Applicant |
| US6643650(B1) | 2003-11-01 | Slaughter et al. | Applicant |
| US6643688(B1) | 2003-11-01 | Fuisz | Applicant |
| US6647384(B2) | 2003-11-01 | Gilmour | Applicant |
| US6650890(B1) | 2003-11-01 | Irlam et al. | Applicant |
| US6662016(B1) | 2003-12-01 | Buckham et al. | Applicant |
| US6668046(B1) | 2003-12-01 | Albal | Applicant |
| US6671695(B2) | 2003-12-01 | McFadden | Applicant |
| US6671700(B1) | 2003-12-01 | Creemer et al. | Applicant |
| US6671702(B2) | 2003-12-01 | Kruglikov et al. | Applicant |
| US6671757(B1) | 2003-12-01 | Multer et al. | Applicant |
| US6694336(B1) | 2004-02-01 | Multer et al. | Applicant |
| US6697807(B2) | 2004-02-01 | McGeachie | Applicant |
| US6701378(B1) | 2004-03-01 | Gilhuly et al. | Applicant |
| US6707801(B2) | 2004-03-01 | Hsu | Applicant |
| US6708221(B1) | 2004-03-01 | Mendez et al. | Applicant |
| US6714965(B2) | 2004-03-01 | Kakuta et al. | Applicant |
| US6721787(B1) | 2004-04-01 | Hiscock | Applicant |
| US6727917(B1) | 2004-04-01 | Chew et al. | Applicant |
| US6728530(B1) | 2004-04-01 | Heinonen et al. | Applicant |
| US6728786(B2) | 2004-04-01 | Hawkins et al. | Applicant |
| US6732101(B1) | 2004-05-01 | Cook | Applicant |
| US6732158(B1) | 2004-05-01 | Hesselink et al. | Applicant |
| US6735591(B2) | 2004-05-01 | Khan | Applicant |
| US6741232(B1) | 2004-05-01 | Siedlikowski et al. | Applicant |
| US6741855(B1) | 2004-05-01 | Martin et al. | Applicant |
| US6742015(B1) | 2004-05-01 | Bowman-Amuah | Applicant |
| US6745024(B1) | 2004-06-01 | DeJaco et al. | Applicant |
| US6745326(B1) | 2004-06-01 | Wary | Applicant |
| US6756882(B2) | 2004-06-01 | Benes et al. | Applicant |
| US6757362(B1) | 2004-06-01 | Cooper et al. | Applicant |
| US6757696(B2) | 2004-06-01 | Multer et al. | Applicant |
| US6760916(B2) | 2004-07-01 | Holtz et al. | Applicant |
| US6771294(B1) | 2004-08-01 | Pulli et al. | Applicant |
| US6775362(B1) | 2004-08-01 | Ransom | Applicant |
| US6779019(B1) | 2004-08-01 | Mousseau et al. | Applicant |
| US6782409(B1) | 2004-08-01 | Yoshida | Applicant |
| US6785868(B1) | 2004-08-01 | Raff | Applicant |
| US6785906(B1) | 2004-08-01 | Gaughan et al. | Applicant |
| US6799190(B1) | 2004-09-01 | Boothby | Applicant |
| US6804707(B1) | 2004-10-01 | Ronning | Applicant |
| US6816849(B1) | 2004-11-01 | Halt, Jr. | Applicant |
| US6820088(B1) | 2004-11-01 | Hind et al. | Applicant |
| US6820204(B1) | 2004-11-01 | Desai et al. | Applicant |
| US6829487(B2) | 2004-12-01 | Eiden et al. | Applicant |
| US6834195(B2) | 2004-12-01 | Brandenberg et al. | Applicant |
| US6847974(B2) | 2005-01-01 | Wachtel | Applicant |
| US6850757(B2) | 2005-02-01 | Watanabe et al. | Applicant |
| US6859212(B2) | 2005-02-01 | Kumar et al. | Applicant |
| US6867774(B1) | 2005-03-01 | Halmshaw et al. | Applicant |
| US6868447(B1) | 2005-03-01 | Slaughter et al. | Applicant |
| US6871220(B1) | 2005-03-01 | Rajan et al. | Applicant |
| US6873688(B1) | 2005-03-01 | Aarnio | Applicant |
| US6879985(B2) | 2005-04-01 | Deguchi et al. | Applicant |
| US6886030(B1) | 2005-04-01 | Easterbrook | Applicant |
| US6892070(B2) | 2005-05-01 | Warrier et al. | Applicant |
| US6892196(B1) | 2005-05-01 | Hughes | Applicant |
| US6895394(B1) | 2005-05-01 | Kremer et al. | Applicant |
| US6895558(B1) | 2005-05-01 | Loveland | Applicant |
| US6898427(B1) | 2005-05-01 | Griffith et al. | Applicant |
| US6922547(B2) | 2005-07-01 | O'Neill et al. | Applicant |
| US6922721(B1) | 2005-07-01 | Minborg et al. | Applicant |
| US6925477(B1) | 2005-08-01 | Champagne et al. | Applicant |
| US6931529(B2) | 2005-08-01 | Kunzinger | Applicant |
| US6938079(B1) | 2005-08-01 | Anderson et al. | Applicant |
| US6944447(B2) | 2005-09-01 | Portman et al. | Applicant |
| US6944662(B2) | 2005-09-01 | Devine et al. | Applicant |
| US6947770(B2) | 2005-09-01 | Rydbeck | Applicant |
| US6957397(B1) | 2005-10-01 | Hawkins et al. | Applicant |
| US6965917(B1) | 2005-11-01 | Aloni | Applicant |
| US6966058(B2) | 2005-11-01 | Earl et al. | Applicant |
| US6968175(B2) | 2005-11-01 | Raivisto et al. | Applicant |
| US6970879(B1) | 2005-11-01 | Gilmour | Applicant |
| US6972682(B2) | 2005-12-01 | Lareau et al. | Applicant |
| US6973299(B2) | 2005-12-01 | Apfel | Applicant |
| US6981047(B2) | 2005-12-01 | Hanson et al. | Applicant |
| US6986061(B1) | 2006-01-01 | Kunzinger | Applicant |
| US6987734(B2) | 2006-01-01 | Hundemer | Applicant |
| US6990472(B2) | 2006-01-01 | Rosenhaft et al. | Applicant |
| US6993326(B2) | 2006-01-01 | Link, II et al. | Applicant |
| US6993327(B2) | 2006-01-01 | Mathis | Applicant |
| US6999753(B2) | 2006-02-01 | Beckmann et al. | Applicant |
| US7026984(B1) | 2006-04-01 | Thandu et al. | Applicant |
| US7032242(B1) | 2006-04-01 | Grabelsky et al. | Applicant |
| US7035630(B2) | 2006-04-01 | Knowles | Applicant |
| US7046993(B2) | 2006-05-01 | Haaramo et al. | Applicant |
| US7047202(B2) | 2006-05-01 | Jaipuria et al. | Applicant |
| US7062024(B2) | 2006-06-01 | Kreckel et al. | Applicant |
| US7069308(B2) | 2006-06-01 | Abrams | Applicant |
| US7072678(B2) | 2006-07-01 | Allison | Applicant |
| US7079499(B1) | 2006-07-01 | Akhtar et al. | Applicant |
| US7082316(B2) | 2006-07-01 | Eiden et al. | Applicant |
| US7085365(B2) | 2006-08-01 | Kauppinen | Applicant |
| US7096030(B2) | 2006-08-01 | Huomo | Applicant |
| US7100821(B2) | 2006-09-01 | Rasti | Applicant |
| US7103432(B2) | 2006-09-01 | Drader et al. | Applicant |
| US7120692(B2) | 2006-10-01 | Hesselink et al. | Applicant |
| US7120928(B2) | 2006-10-01 | Sheth et al. | Applicant |
| US7130839(B2) | 2006-10-01 | Boreham et al. | Applicant |
| US7136645(B2) | 2006-11-01 | Hanson et al. | Applicant |
| US7139555(B2) | 2006-11-01 | Apfel | Applicant |
| US7139565(B2) | 2006-11-01 | Fiatal et al. | Applicant |
| US7140549(B2) | 2006-11-01 | de Jong | Applicant |
| US7146645(B1) | 2006-12-01 | Hellsten et al. | Applicant |
| US7149780(B2) | 2006-12-01 | Quine et al. | Applicant |
| US7149789(B2) | 2006-12-01 | Slivka et al. | Applicant |
| US7149959(B1) | 2006-12-01 | Jones et al. | Applicant |
| US7162241(B2) | 2007-01-01 | Kim et al. | Applicant |
| US7165727(B2) | 2007-01-01 | de Jong | Applicant |
| US7172118(B2) | 2007-02-01 | Urken | Applicant |
| US7181228(B2) | 2007-02-01 | Boesch | Applicant |
| US7184790(B2) | 2007-02-01 | Dorenbosch et al. | Applicant |
| US7194273(B2) | 2007-03-01 | Vaudreuil | Applicant |
| US7200390(B1) | 2007-04-01 | Henager et al. | Applicant |
| US7206806(B2) | 2007-04-01 | Pineau | Applicant |
| US7209757(B2) | 2007-04-01 | Naghian et al. | Applicant |
| US7219222(B1) | 2007-05-01 | Durbin et al. | Applicant |
| US7224957(B2) | 2007-05-01 | Spector | Applicant |
| US7231206(B2) | 2007-06-01 | Cudak et al. | Applicant |
| US7233795(B1) | 2007-06-01 | Ryden | Applicant |
| US7234111(B2) | 2007-06-01 | Chu et al. | Applicant |
| US7239877(B2) | 2007-07-01 | Corneille et al. | Applicant |
| US7240095(B1) | 2007-07-01 | Lewis | Applicant |
| US7242680(B2) | 2007-07-01 | Gallant | Applicant |
| US7245926(B2) | 2007-07-01 | Liao et al. | Applicant |
| US7257391(B2) | 2007-08-01 | Burgess et al. | Applicant |
| US7259666(B1) | 2007-08-01 | Hermsmeyer et al. | Applicant |
| US7260552(B2) | 2007-08-01 | Riera Jorba et al. | Applicant |
| US7260590(B1) | 2007-08-01 | Williams | Applicant |
| US7272830(B2) | 2007-09-01 | de Jong | Applicant |
| US7277408(B2) | 2007-10-01 | Sorsa | Applicant |
| US7289792(B1) | 2007-10-01 | Turunen | Applicant |
| US7289964(B1) | 2007-10-01 | Bowman-Amuah | Applicant |
| US7289971(B1) | 2007-10-01 | O'Neil et al. | Applicant |
| US7293107(B1) | 2007-11-01 | Hanson et al. | Applicant |
| US7295853(B2) | 2007-11-01 | Jin et al. | Applicant |
| US7305700(B2) | 2007-12-01 | Boynton et al. | Applicant |
| US7310350(B1) | 2007-12-01 | Shao et al. | Applicant |
| US7310729(B2) | 2007-12-01 | Gordon et al. | Applicant |
| US7349871(B2) | 2008-03-01 | Labrou et al. | Applicant |
| US7359720(B2) | 2008-04-01 | Hartmaier et al. | Applicant |
| US7373386(B2) | 2008-05-01 | Gardner et al. | Applicant |
| US7374099(B2) | 2008-05-01 | de Jong | Applicant |
| US7376701(B2) | 2008-05-01 | Bhargava et al. | Applicant |
| US7382879(B1) | 2008-06-01 | Miller | Applicant |
| US7388950(B2) | 2008-06-01 | Elsey et al. | Applicant |
| US7389412(B2) | 2008-06-01 | Sharma et al. | Applicant |
| US7392483(B2) | 2008-06-01 | Wong et al. | Applicant |
| US7395329(B1) | 2008-07-01 | Holt et al. | Applicant |
| US7430609(B2) | 2008-09-01 | Brown et al. | Applicant |
| US7441271(B2) | 2008-10-01 | Fiatal et al. | Applicant |
| US7461071(B2) | 2008-12-01 | Fitzpatrick et al. | Applicant |
| US7465231(B2) | 2008-12-01 | Lewin et al. | Applicant |
| US7469125(B2) | 2008-12-01 | Nurmi | Applicant |
| US7483036(B2) | 2009-01-01 | Moore | Applicant |
| US7499573(B2) | 2009-03-01 | Tanabata et al. | Applicant |
| US7502615(B2) | 2009-03-01 | Wilhoite et al. | Applicant |
| US7519042(B2) | 2009-04-01 | Gorday et al. | Applicant |
| US7532571(B1) | 2009-05-01 | Price et al. | Applicant |
| US7539665(B2) | 2009-05-01 | Mendez | Applicant |
| US7567575(B2) | 2009-07-01 | Chen et al. | Applicant |
| US7574208(B2) | 2009-08-01 | Hanson et al. | Applicant |
| US7575171(B2) | 2009-08-01 | Lev | Applicant |
| US7587482(B2) | 2009-09-01 | Henderson et al. | Applicant |
| US7596608(B2) | 2009-09-01 | Alexander et al. | Applicant |
| US7643818(B2) | 2010-01-01 | Backholm et al. | Applicant |
| US7680281(B2) | 2010-03-01 | Fiatal et al. | Applicant |
| US7689664(B2) | 2010-03-01 | Karlberg | Applicant |
| US7706781(B2) | 2010-04-01 | Backholm et al. | Applicant |
| US7752633(B1) | 2010-07-01 | Fleming | Applicant |
| US7769395(B2) | 2010-08-01 | Fiatal et al. | Applicant |
| US7769400(B2) | 2010-08-01 | Backholm et al. | Applicant |
| US7796742(B1) | 2010-09-01 | Sutaria et al. | Applicant |
| US7797064(B2) | 2010-09-01 | Loomis et al. | Applicant |
| US7827597(B2) | 2010-11-01 | Boynton et al. | Applicant |
| US7853563(B2) | 2010-12-01 | Alvarado et al. | Applicant |
| US7877703(B1) | 2011-01-01 | Fleming | Applicant |
| US7917505(B2) | 2011-03-01 | Gent et al. | Applicant |
| US2001/0010046(A1) | 2001-07-01 | Muyres et al. | Applicant |
| US2001/0023414(A1) | 2001-09-01 | Kumar et al. | Applicant |
| US2001/0032254(A1) | 2001-10-01 | Hawkins | Applicant |
| US2001/0034225(A1) | 2001-10-01 | Gupte | Applicant |
| US2001/0034244(A1) | 2001-10-01 | Calder et al. | Applicant |
| US2001/0037453(A1) | 2001-11-01 | Mitty et al. | Applicant |
| US2001/0039191(A1) | 2001-11-01 | Maierhofer | Applicant |
| US2001/0041566(A1) | 2001-11-01 | Xanthos et al. | Applicant |
| US2001/0042009(A1) | 2001-11-01 | Montague | Applicant |
| US2001/0042099(A1) | 2001-11-01 | Peng | Applicant |
| US2001/0043148(A1) | 2001-11-01 | Stewart | Applicant |
| US2002/0002478(A1) | 2002-01-01 | Swart et al. | Applicant |
| US2002/0007303(A1) | 2002-01-01 | Brookler et al. | Applicant |
| US2002/0013727(A1) | 2002-01-01 | Lee | Applicant |
| US2002/0019225(A1) | 2002-02-01 | Miyashita | Applicant |
| US2002/0019812(A1) | 2002-02-01 | Board et al. | Applicant |
| US2002/0035556(A1) | 2002-03-01 | Shah et al. | Applicant |
| US2002/0035617(A1) | 2002-03-01 | Lynch et al. | Applicant |
| US2002/0038253(A1) | 2002-03-01 | Seaman et al. | Applicant |
| US2002/0042875(A1) | 2002-04-01 | Shukla | Applicant |
| US2002/0049828(A1) | 2002-04-01 | Pekarek-Kostka | Applicant |
| US2002/0053078(A1) | 2002-05-01 | Holtz et al. | Applicant |
| US2002/0055351(A1) | 2002-05-01 | Elsey et al. | Applicant |
| US2002/0059201(A1) | 2002-05-01 | Work | Applicant |
| US2002/0059457(A1) | 2002-05-01 | Ballard et al. | Applicant |
| US2002/0068559(A1) | 2002-06-01 | Sharma et al. | Applicant |
| US2002/0077077(A1) | 2002-06-01 | Rezvani et al. | Applicant |
| US2002/0077084(A1) | 2002-06-01 | Zellner et al. | Applicant |
| US2002/0078384(A1) | 2002-06-01 | Hippelainen | Applicant |
| US2002/0087679(A1) | 2002-07-01 | Pulley et al. | Applicant |
| US2002/0089542(A1) | 2002-07-01 | Imamura | Applicant |
| US2002/0091921(A1) | 2002-07-01 | Kunzinger | Applicant |
| US2002/0095319(A1) | 2002-07-01 | Swart et al. | Applicant |
| US2002/0095328(A1) | 2002-07-01 | Swart et al. | Applicant |
| US2002/0095391(A1) | 2002-07-01 | Swart et al. | Applicant |
| US2002/0095399(A1) | 2002-07-01 | Devine et al. | Applicant |
| US2002/0098855(A1) | 2002-07-01 | Hartmaier et al. | Applicant |
| US2002/0099613(A1) | 2002-07-01 | Swart et al. | Applicant |
| US2002/0101975(A1) | 2002-08-01 | Tiburtius et al. | Applicant |
| US2002/0116499(A1) | 2002-08-01 | Enns et al. | Applicant |
| US2002/0116501(A1) | 2002-08-01 | Ho et al. | Applicant |
| US2002/0120766(A1) | 2002-08-01 | Okajima et al. | Applicant |
| US2002/0120779(A1) | 2002-08-01 | Teeple et al. | Applicant |
| US2002/0126701(A1) | 2002-09-01 | Requena | Applicant |
| US2002/0133504(A1) | 2002-09-01 | Vlahos et al. | Applicant |
| US2002/0144109(A1) | 2002-10-01 | Benantar et al. | Applicant |
| US2002/0146129(A1) | 2002-10-01 | Kaplan | Applicant |
| US2002/0152379(A1) | 2002-10-01 | Gefwert et al. | Applicant |
| US2002/0155848(A1) | 2002-10-01 | Suryanarayana | Applicant |
| US2002/0158908(A1) | 2002-10-01 | Vaajala et al. | Applicant |
| US2002/0161587(A1) | 2002-10-01 | Pitts, III et al. | Applicant |
| US2002/0161925(A1) | 2002-10-01 | Munger et al. | Applicant |
| US2002/0161928(A1) | 2002-10-01 | Ndili | Applicant |
| US2002/0164977(A1) | 2002-11-01 | Link II et al. | Applicant |
| US2002/0186848(A1) | 2002-12-01 | Shaik | Applicant |
| US2002/0188940(A1) | 2002-12-01 | Breckner et al. | Applicant |
| US2002/0193094(A1) | 2002-12-01 | Lawless et al. | Applicant |
| US2002/0194209(A1) | 2002-12-01 | Bolosky et al. | Applicant |
| US2002/0198027(A1) | 2002-12-01 | Rydbeck | Applicant |
| US2003/0005151(A1) | 2003-01-01 | Ullman et al. | Applicant |
| US2003/0022662(A1) | 2003-01-01 | Mittal | Applicant |
| US2003/0023975(A1) | 2003-01-01 | Schrader et al. | Applicant |
| US2003/0028430(A1) | 2003-02-01 | Zimmerman | Applicant |
| US2003/0028441(A1) | 2003-02-01 | Barsness et al. | Applicant |
| US2003/0054810(A1) | 2003-03-01 | Chen et al. | Applicant |
| US2003/0056096(A1) | 2003-03-01 | Albert et al. | Applicant |
| US2003/0060188(A1) | 2003-03-01 | Gidron et al. | Applicant |
| US2003/0063120(A1) | 2003-04-01 | Wong et al. | Applicant |
| US2003/0065738(A1) | 2003-04-01 | Yang et al. | Applicant |
| US2003/0065802(A1) | 2003-04-01 | Vitikainen et al. | Applicant |
| US2003/0070061(A1) | 2003-04-01 | Wong et al. | Applicant |
| US2003/0072451(A1) | 2003-04-01 | Pimentel et al. | Applicant |
| US2003/0078880(A1) | 2003-04-01 | Alley et al. | Applicant |
| US2003/0084165(A1) | 2003-05-01 | Kjellberg | Applicant |
| US2003/0088629(A1) | 2003-05-01 | Berkowitz et al. | Applicant |
| US2003/0093691(A1) | 2003-05-01 | Simon et al. | Applicant |
| US2003/0097381(A1) | 2003-05-01 | Detweiler et al. | Applicant |
| US2003/0100321(A1) | 2003-05-01 | Rao et al. | Applicant |
| US2003/0100326(A1) | 2003-05-01 | Grube et al. | Applicant |
| US2003/0117432(A1) | 2003-06-01 | Kautto-Kiovula et al. | Applicant |
| US2003/0125023(A1) | 2003-07-01 | Fishler | Applicant |
| US2003/0126216(A1) | 2003-07-01 | Avila et al. | Applicant |
| US2003/0130984(A1) | 2003-07-01 | Quinlan et al. | Applicant |
| US2003/0146934(A1) | 2003-08-01 | Bailey et al. | Applicant |
| US2003/0153338(A1) | 2003-08-01 | Herz et al. | Applicant |
| US2003/0154212(A1) | 2003-08-01 | Schirmer et al. | Applicant |
| US2003/0156146(A1) | 2003-08-01 | Suomela et al. | Applicant |
| US2003/0157947(A1) | 2003-08-01 | Fiatal et al. | Applicant |
| US2003/0169262(A1) | 2003-09-01 | Lavelle et al. | Applicant |
| US2003/0177281(A1) | 2003-09-01 | McQuillan et al. | Applicant |
| US2003/0208529(A1) | 2003-11-01 | Pendyala et al. | Applicant |
| US2003/0208559(A1) | 2003-11-01 | Velline et al. | Applicant |
| US2003/0211845(A1) | 2003-11-01 | Lohtia et al. | Applicant |
| US2003/0217098(A1) | 2003-11-01 | Bobde et al. | Applicant |
| US2003/0217142(A1) | 2003-11-01 | Bobde et al. | Applicant |
| US2003/0223554(A1) | 2003-12-01 | Zhang | Applicant |
| US2003/0227745(A1) | 2003-12-01 | Khoo | Applicant |
| US2003/0235308(A1) | 2003-12-01 | Boynton et al. | Applicant |
| US2003/0236981(A1) | 2003-12-01 | Marmigere et al. | Applicant |
| US2004/0002324(A1) | 2004-01-01 | Juntunen et al. | Applicant |
| US2004/0006630(A1) | 2004-01-01 | Friend et al. | Applicant |
| US2004/0024795(A1) | 2004-02-01 | Hind et al. | Applicant |
| US2004/0024892(A1) | 2004-02-01 | Creswell et al. | Applicant |
| US2004/0027326(A1) | 2004-02-01 | Hays et al. | Applicant |
| US2004/0027375(A1) | 2004-02-01 | Ellis et al. | Applicant |
| US2004/0027378(A1) | 2004-02-01 | Hays et al. | Applicant |
| US2004/0043770(A1) | 2004-03-01 | Amit et al. | Applicant |
| US2004/0049599(A1) | 2004-03-01 | Friend et al. | Applicant |
| US2004/0051715(A1) | 2004-03-01 | Brokenshire et al. | Applicant |
| US2004/0054739(A1) | 2004-03-01 | Friend et al. | Applicant |
| US2004/0064445(A1) | 2004-04-01 | Pfleging et al. | Applicant |
| US2004/0064488(A1) | 2004-04-01 | Sinha | Applicant |
| US2004/0068698(A1) | 2004-04-01 | Wu et al. | Applicant |
| US2004/0075675(A1) | 2004-04-01 | Raivisto et al. | Applicant |
| US2004/0075695(A1) | 2004-04-01 | Chew et al. | Applicant |
| US2004/0078814(A1) | 2004-04-01 | Allen | Applicant |
| US2004/0080515(A1) | 2004-04-01 | Hagiwara | Applicant |
| US2004/0082346(A1) | 2004-04-01 | Skytt | Applicant |
| US2004/0098625(A1) | 2004-05-01 | Lagadec et al. | Applicant |
| US2004/0103147(A1) | 2004-05-01 | Flesher et al. | Applicant |
| US2004/0120323(A1) | 2004-06-01 | Viikari et al. | Applicant |
| US2004/0128375(A1) | 2004-07-01 | Rockwell | Applicant |
| US2004/0133626(A1) | 2004-07-01 | Herrero et al. | Applicant |
| US2004/0141011(A1) | 2004-07-01 | Smethers et al. | Applicant |
| US2004/0147262(A1) | 2004-07-01 | Lescuyer et al. | Applicant |
| US2004/0158611(A1) | 2004-08-01 | Daniell et al. | Applicant |
| US2004/0167966(A1) | 2004-08-01 | Lee et al. | Applicant |
| US2004/0170257(A1) | 2004-09-01 | Gross et al. | Applicant |
| US2004/0172481(A1) | 2004-09-01 | Engstrom | Applicant |
| US2004/0176128(A1) | 2004-09-01 | Grabelsky et al. | Applicant |
| US2004/0179513(A1) | 2004-09-01 | Smith et al. | Applicant |
| US2004/0181550(A1) | 2004-09-01 | Warsta et al. | Applicant |
| US2004/0186902(A1) | 2004-09-01 | Stewart | Applicant |
| US2004/0189610(A1) | 2004-09-01 | Friend | Applicant |
| US2004/0199497(A1) | 2004-10-01 | Timmons | Applicant |
| US2004/0199582(A1) | 2004-10-01 | Kucharewski et al. | Applicant |
| US2004/0205248(A1) | 2004-10-01 | Little et al. | Applicant |
| US2004/0205330(A1) | 2004-10-01 | Godfrey et al. | Applicant |
| US2004/0209602(A1) | 2004-10-01 | Joyce et al. | Applicant |
| US2004/0230619(A1) | 2004-11-01 | Blanco et al. | Applicant |
| US2004/0236792(A1) | 2004-11-01 | Celik | Applicant |
| US2004/0252816(A1) | 2004-12-01 | Nicolas | Applicant |
| US2004/0255126(A1) | 2004-12-01 | Reith | Applicant |
| US2004/0258231(A1) | 2004-12-01 | Elsey et al. | Applicant |
| US2004/0259535(A1) | 2004-12-01 | Elsey et al. | Applicant |
| US2004/0266364(A1) | 2004-12-01 | Nguyen et al. | Applicant |
| US2004/0268148(A1) | 2004-12-01 | Karjala et al. | Examiner |
| US2005/0002501(A1) | 2005-01-01 | Elsey et al. | Applicant |
| US2005/0002508(A1) | 2005-01-01 | Elsey et al. | Applicant |
| US2005/0002509(A1) | 2005-01-01 | Elsey et al. | Applicant |
| US2005/0002510(A1) | 2005-01-01 | Elsey et al. | Applicant |
| US2005/0010694(A1) | 2005-01-01 | Ma et al. | Examiner |
| US2005/0015432(A1) | 2005-01-01 | Cohen | Applicant |
| US2005/0021750(A1) | 2005-01-01 | Abrams | Applicant |
| US2005/0022182(A1) | 2005-01-01 | Mittal | Applicant |
| US2005/0027591(A9) | 2005-02-01 | Gailey et al. | Applicant |
| US2005/0027716(A1) | 2005-02-01 | Apfel | Applicant |
| US2005/0033812(A1) | 2005-02-01 | McCarthy et al. | Applicant |
| US2005/0038707(A1) | 2005-02-01 | Roever et al. | Applicant |
| US2005/0038724(A1) | 2005-02-01 | Roever et al. | Applicant |
| US2005/0038863(A1) | 2005-02-01 | Onyon et al. | Applicant |
| US2005/0041793(A1) | 2005-02-01 | Fulton et al. | Applicant |
| US2005/0044144(A1) | 2005-02-01 | Malik et al. | Applicant |
| US2005/0055578(A1) | 2005-03-01 | Wright et al. | Examiner |
| US2005/0063544(A1) | 2005-03-01 | Uusitalo et al. | Applicant |
| US2005/0071674(A1) | 2005-03-01 | Chou et al. | Applicant |
| US2005/0076136(A1) | 2005-04-01 | Cho et al. | Applicant |
| US2005/0086540(A1) | 2005-04-01 | Gunter et al. | Applicant |
| US2005/0094625(A1) | 2005-05-01 | Bouat | Applicant |
| US2005/0097225(A1) | 2005-05-01 | Glatt et al. | Applicant |
| US2005/0097570(A1) | 2005-05-01 | Bomers | Applicant |
| US2005/0101307(A1) | 2005-05-01 | Brugge et al. | Applicant |
| US2005/0102257(A1) | 2005-05-01 | Onyon et al. | Applicant |
| US2005/0102328(A1) | 2005-05-01 | Ring et al. | Applicant |
| US2005/0108427(A1) | 2005-05-01 | Datta | Applicant |
| US2005/0117606(A1) | 2005-06-01 | Kim | Applicant |
| US2005/0120082(A1) | 2005-06-01 | Hesselink et al. | Applicant |
| US2005/0120084(A1) | 2005-06-01 | Hu et al. | Applicant |
| US2005/0122333(A1) | 2005-06-01 | Sumanaweera et al. | Applicant |
| US2005/0124332(A1) | 2005-06-01 | Clark et al. | Applicant |
| US2005/0138111(A1) | 2005-06-01 | Aton et al. | Applicant |
| US2005/0144219(A1) | 2005-06-01 | Terada | Applicant |
| US2005/0154796(A1) | 2005-07-01 | Forsyth | Applicant |
| US2005/0155027(A1) | 2005-07-01 | Wei | Applicant |
| US2005/0164721(A1) | 2005-07-01 | Eric Yeh et al. | Applicant |
| US2005/0183143(A1) | 2005-08-01 | Anderholm et al. | Applicant |
| US2005/0188038(A1) | 2005-08-01 | Yabe | Applicant |
| US2005/0193036(A1) | 2005-09-01 | Phillips et al. | Applicant |
| US2005/0203966(A1) | 2005-09-01 | Labrou et al. | Applicant |
| US2005/0210104(A1) | 2005-09-01 | Torvinen | Applicant |
| US2005/0228812(A1) | 2005-10-01 | Hansmann et al. | Applicant |
| US2005/0232295(A1) | 2005-10-01 | Young | Applicant |
| US2005/0234860(A1) | 2005-10-01 | Roever et al. | Applicant |
| US2005/0235214(A1) | 2005-10-01 | Shimizu et al. | Applicant |
| US2005/0246139(A1) | 2005-11-01 | Rivenbark et al. | Applicant |
| US2005/0248526(A1) | 2005-11-01 | Twerdahl et al. | Applicant |
| US2005/0251555(A1) | 2005-11-01 | Little, II | Applicant |
| US2005/0262220(A1) | 2005-11-01 | Ecklund et al. | Applicant |
| US2005/0273804(A1) | 2005-12-01 | Preisman | Applicant |
| US2005/0278307(A1) | 2005-12-01 | Battagin et al. | Applicant |
| US2005/0278641(A1) | 2005-12-01 | Mansour et al. | Applicant |
| US2005/0278647(A1) | 2005-12-01 | Leavitt et al. | Applicant |
| US2005/0288006(A1) | 2005-12-01 | Apfel | Applicant |
| US2006/0020525(A1) | 2006-01-01 | Borelli et al. | Examiner |
| US2006/0020580(A1) | 2006-01-01 | Dettinger et al. | Applicant |
| US2006/0020804(A1) | 2006-01-01 | Schleifer et al. | Applicant |
| US2006/0020947(A1) | 2006-01-01 | Hallamaa et al. | Applicant |
| US2006/0021023(A1) | 2006-01-01 | Stewart et al. | Applicant |
| US2006/0022048(A1) | 2006-02-01 | Johnson | Applicant |
| US2006/0026580(A1) | 2006-02-01 | Cabillic et al. | Applicant |
| US2006/0029062(A1) | 2006-02-01 | Rao et al. | Applicant |
| US2006/0029063(A1) | 2006-02-01 | Rao et al. | Applicant |
| US2006/0029064(A1) | 2006-02-01 | Rao et al. | Applicant |
| US2006/0031114(A1) | 2006-02-01 | Zommers | Applicant |
| US2006/0031365(A1) | 2006-02-01 | Kay et al. | Applicant |
| US2006/0031428(A1) | 2006-02-01 | Wikman | Applicant |
| US2006/0031785(A1) | 2006-02-01 | Raciborski | Applicant |
| US2006/0037071(A1) | 2006-02-01 | Rao et al. | Applicant |
| US2006/0046686(A1) | 2006-03-01 | Hawkins et al. | Applicant |
| US2006/0047844(A1) | 2006-03-01 | Deng | Applicant |
| US2006/0048061(A1) | 2006-03-01 | Forlenza et al. | Applicant |
| US2006/0052091(A1) | 2006-03-01 | Onyon et al. | Applicant |
| US2006/0063544(A1) | 2006-03-01 | Zhao et al. | Applicant |
| US2006/0069686(A1) | 2006-03-01 | Beyda et al. | Applicant |
| US2006/0069687(A1) | 2006-03-01 | Cui | Applicant |
| US2006/0073810(A1) | 2006-04-01 | Pyhalammi et al. | Applicant |
| US2006/0074951(A1) | 2006-04-01 | Beier et al. | Applicant |
| US2006/0084410(A1) | 2006-04-01 | Sutaria et al. | Applicant |
| US2006/0085503(A1) | 2006-04-01 | Stoye et al. | Applicant |
| US2006/0093135(A1) | 2006-05-01 | Fiatal et al. | Applicant |
| US2006/0099969(A1) | 2006-05-01 | Staton et al. | Applicant |
| US2006/0132495(A1) | 2006-06-01 | Anderson | Applicant |
| US2006/0141962(A1) | 2006-06-01 | Forbes et al. | Applicant |
| US2006/0143464(A1) | 2006-06-01 | Ananthanarayanan et al. | Applicant |
| US2006/0149591(A1) | 2006-07-01 | Hanf et al. | Applicant |
| US2006/0149843(A1) | 2006-07-01 | Rhoads et al. | Applicant |
| US2006/0149970(A1) | 2006-07-01 | Imazu | Applicant |
| US2006/0165226(A1) | 2006-07-01 | Ernst et al. | Applicant |
| US2006/0168043(A1) | 2006-07-01 | Eisenberger et al. | Applicant |
| US2006/0168164(A1) | 2006-07-01 | Lemson et al. | Examiner |
| US2006/0179410(A1) | 2006-08-01 | Deeds | Applicant |
| US2006/0188864(A1) | 2006-08-01 | Shah | Applicant |
| US2006/0190428(A1) | 2006-08-01 | Jung et al. | Applicant |
| US2006/0190984(A1) | 2006-08-01 | Heard et al. | Examiner |
| US2006/0192014(A1) | 2006-08-01 | Hamilton et al. | Applicant |
| US2006/0195570(A1) | 2006-08-01 | Zellner et al. | Applicant |
| US2006/0212531(A1) | 2006-09-01 | Kikkawa et al. | Applicant |
| US2006/0224629(A1) | 2006-10-01 | Alexander et al. | Applicant |
| US2006/0230394(A1) | 2006-10-01 | Forth et al. | Applicant |
| US2006/0240804(A1) | 2006-10-01 | Backholm et al. | Applicant |
| US2006/0240805(A1) | 2006-10-01 | Backholm et al. | Applicant |
| US2006/0242210(A1) | 2006-10-01 | Ring et al. | Applicant |
| US2006/0242607(A1) | 2006-10-01 | Hudson | Applicant |
| US2006/0252435(A1) | 2006-11-01 | Henderson et al. | Applicant |
| US2006/0265595(A1) | 2006-11-01 | Scottodiluzio | Applicant |
| US2006/0277265(A1) | 2006-12-01 | Backholm et al. | Applicant |
| US2006/0294071(A1) | 2006-12-01 | Weare et al. | Applicant |
| US2007/0005738(A1) | 2007-01-01 | Alexion-Tiernan et al. | Applicant |
| US2007/0022118(A1) | 2007-01-01 | Layne | Applicant |
| US2007/0027775(A1) | 2007-02-01 | Hwang | Applicant |
| US2007/0027832(A1) | 2007-02-01 | Fiatal et al. | Applicant |
| US2007/0027886(A1) | 2007-02-01 | Gent et al. | Applicant |
| US2007/0027917(A1) | 2007-02-01 | Ariel et al. | Applicant |
| US2007/0027920(A1) | 2007-02-01 | Alvarado et al. | Applicant |
| US2007/0027921(A1) | 2007-02-01 | Alvarado et al. | Applicant |
| US2007/0027930(A1) | 2007-02-01 | Alvarado et al. | Applicant |
| US2007/0033531(A1) | 2007-02-01 | Marsh | Applicant |
| US2007/0038567(A1) | 2007-02-01 | Allaire et al. | Applicant |
| US2007/0038931(A1) | 2007-02-01 | Allaire et al. | Applicant |
| US2007/0044041(A1) | 2007-02-01 | Beynon et al. | Applicant |
| US2007/0049258(A1) | 2007-03-01 | Thibeault | Applicant |
| US2007/0060196(A1) | 2007-03-01 | Sharma | Applicant |
| US2007/0061393(A1) | 2007-03-01 | Moore | Applicant |
| US2007/0067381(A1) | 2007-03-01 | Grant et al. | Applicant |
| US2007/0067424(A1) | 2007-03-01 | Raciborski et al. | Applicant |
| US2007/0078857(A1) | 2007-04-01 | Punaganti et al. | Applicant |
| US2007/0105627(A1) | 2007-05-01 | Campbell | Applicant |
| US2007/0116223(A1) | 2007-05-01 | Burke et al. | Applicant |
| US2007/0118620(A1) | 2007-05-01 | Cartmell et al. | Applicant |
| US2007/0130108(A1) | 2007-06-01 | Simpson et al. | Applicant |
| US2007/0130217(A1) | 2007-06-01 | Linyard et al. | Applicant |
| US2007/0156824(A1) | 2007-07-01 | Thompson | Applicant |
| US2007/0174433(A1) | 2007-07-01 | Mendez et al. | Applicant |
| US2007/0175998(A1) | 2007-08-01 | Lev | Applicant |
| US2007/0198698(A1) | 2007-08-01 | Boyd et al. | Applicant |
| US2007/0220080(A1) | 2007-09-01 | Humphrey | Applicant |
| US2007/0249365(A1) | 2007-10-01 | Jendbro | Applicant |
| US2007/0250591(A1) | 2007-10-01 | Milic-Frayling et al. | Applicant |
| US2007/0264993(A1) | 2007-11-01 | Hughes | Applicant |
| US2007/0267492(A1) | 2007-11-01 | Maclaine Pont | Applicant |
| US2007/0276925(A1) | 2007-11-01 | La Joie et al. | Applicant |
| US2007/0276926(A1) | 2007-11-01 | LaJoie et al. | Applicant |
| US2007/0290787(A1) | 2007-12-01 | Fiatal et al. | Applicant |
| US2007/0293207(A1) | 2007-12-01 | Guedalia et al. | Applicant |
| US2007/0293238(A1) | 2007-12-01 | Fiatal et al. | Applicant |
| US2007/0294295(A1) | 2007-12-01 | Finkelstein et al. | Applicant |
| US2008/0001717(A1) | 2008-01-01 | Fiatal | Applicant |
| US2008/0009344(A1) | 2008-01-01 | Graham et al. | Applicant |
| US2008/0037787(A1) | 2008-02-01 | Boynton et al. | Applicant |
| US2008/0059308(A1) | 2008-03-01 | Gerken | Applicant |
| US2008/0059398(A1) | 2008-03-01 | Tsutsui | Applicant |
| US2008/0061142(A1) | 2008-03-01 | Howcroft et al. | Applicant |
| US2008/0077506(A1) | 2008-03-01 | Rampell et al. | Applicant |
| US2008/0077571(A1) | 2008-03-01 | Harris et al. | Applicant |
| US2008/0086379(A1) | 2008-04-01 | Dion et al. | Applicant |
| US2008/0103877(A1) | 2008-05-01 | Gerken | Applicant |
| US2008/0125225(A1) | 2008-05-01 | Lazaridis et al. | Applicant |
| US2008/0130663(A1) | 2008-06-01 | Fridman et al. | Applicant |
| US2008/0133326(A1) | 2008-06-01 | Goncalves et al. | Applicant |
| US2008/0133641(A1) | 2008-06-01 | Gent et al. | Applicant |
| US2008/0133708(A1) | 2008-06-01 | Alvarado et al. | Applicant |
| US2008/0134292(A1) | 2008-06-01 | Ariel et al. | Applicant |
| US2008/0140665(A1) | 2008-06-01 | Ariel et al. | Applicant |
| US2008/0151817(A1) | 2008-06-01 | Fitchett et al. | Applicant |
| US2008/0154870(A1) | 2008-06-01 | Evermann et al. | Applicant |
| US2008/0155613(A1) | 2008-06-01 | Benya et al. | Applicant |
| US2008/0192820(A1) | 2008-08-01 | Brooks et al. | Applicant |
| US2008/0201362(A1) | 2008-08-01 | Multer et al. | Applicant |
| US2008/0201751(A1) | 2008-08-01 | Ahmed et al. | Applicant |
| US2008/0207182(A1) | 2008-08-01 | Maharajh et al. | Applicant |
| US2008/0209491(A1) | 2008-08-01 | Hasek | Applicant |
| US2008/0270379(A1) | 2008-10-01 | Ramakrishna | Applicant |
| US2008/0298386(A1) | 2008-12-01 | Fiatal | Applicant |
| US2008/0313282(A1) | 2008-12-01 | Warila et al. | Applicant |
| US2009/0012841(A1) | 2009-01-01 | Saft et al. | Applicant |
| US2009/0016526(A1) | 2009-01-01 | Fiatal et al. | Applicant |
| US2009/0031006(A1) | 2009-01-01 | Johnson | Applicant |
| US2009/0054034(A1) | 2009-02-01 | Backholm et al. | Applicant |
| US2009/0063647(A1) | 2009-03-01 | Backholm et al. | Applicant |
| US2009/0075683(A1) | 2009-03-01 | Backholm et al. | Applicant |
| US2009/0110179(A1) | 2009-04-01 | Elsey et al. | Applicant |
| US2009/0119266(A1) | 2009-05-01 | Fitzpatrick et al. | Applicant |
| US2009/0125523(A1) | 2009-05-01 | Fitzpatrick et al. | Applicant |
| US2009/0144632(A1) | 2009-06-01 | Mendez | Applicant |
| US2009/0149203(A1) | 2009-06-01 | Backholm et al. | Applicant |
| US2009/0156178(A1) | 2009-06-01 | Elsey et al. | Applicant |
| US2009/0157792(A1) | 2009-06-01 | Fiatal | Applicant |
| US2009/0164560(A1) | 2009-06-01 | Fiatal | Applicant |
| US2009/0172565(A1) | 2009-07-01 | Jackson et al. | Applicant |
| US2009/0181641(A1) | 2009-07-01 | Fiatal | Applicant |
| US2009/0182500(A1) | 2009-07-01 | Dicke | Applicant |
| US2009/0191903(A1) | 2009-07-01 | Fiatal | Applicant |
| US2009/0193130(A1) | 2009-07-01 | Fiatal | Applicant |
| US2009/0193338(A1) | 2009-07-01 | Fiatal | Applicant |
| US2009/0221326(A1) | 2009-09-01 | Roussel et al. | Applicant |
| US2009/0241180(A1) | 2009-09-01 | Fiatal | Applicant |
| US2009/0248670(A1) | 2009-10-01 | Fiatal | Applicant |
| US2009/0248794(A1) | 2009-10-01 | Helms et al. | Applicant |
| US2009/0299817(A1) | 2009-12-01 | Fok et al. | Applicant |
| US2009/0307133(A1) | 2009-12-01 | Holloway et al. | Applicant |
| US2009/0318171(A1) | 2009-12-01 | Backholm et al. | Applicant |
| US2009/0323678(A1) | 2009-12-01 | Wang | Examiner |
| US2009/0325565(A1) | 2009-12-01 | Backholm | Applicant |
| US2010/0057924(A1) | 2010-03-01 | Rauber et al. | Applicant |
| US2010/0146107(A1) | 2010-06-01 | Fiatal | Applicant |
| US2010/0174735(A1) | 2010-07-01 | Fiatal | Applicant |
| EP772327(A2) | 1997-05-01 | Applicant | |
| EP1422899(A1) | 2004-05-01 | Applicant | |
| EP1466261(A1) | 2004-10-01 | Applicant | |
| EP1466435(A1) | 2004-10-01 | Applicant | |
| EP1815634(A1) | 2007-08-01 | Applicant | |
| EP1815652(A1) | 2007-08-01 | Applicant | |
| EP1817883(A1) | 2007-08-01 | Applicant | |
| FI117152(B) | 2006-06-01 | Applicant | |
| FI118288(B) | 2007-09-01 | Applicant | |
| FI119581(B) | 2008-12-01 | Applicant | |
| JP4154233(A) | 1992-05-01 | Applicant | |
| JP10-336372(A) | 1998-12-01 | Applicant | |
| JP2001-218185(A) | 2001-08-01 | Applicant | |
| JP2001-350718(A) | 2001-12-01 | Applicant | |
| JP2001-356973(A) | 2001-12-01 | Applicant | |
| JP2005-515664(T) | 2005-05-01 | Applicant | |
| JP4386732(B2) | 2009-10-01 | Applicant | |
| WO1997/041661(A2) | 1997-11-01 | Applicant | |
| WO9824257 | 1998-06-01 | Applicant | |
| WO1998/058322(A2) | 1998-12-01 | Applicant | |
| WO130130(A2) | 2001-05-01 | Applicant | |
| WO2003/007570(A1) | 2003-01-01 | Applicant | |
| WO2003/058483(A1) | 2003-07-01 | Applicant | |
| WO2003/058879(A1) | 2003-07-01 | Applicant | |
| WO3098890(A1) | 2003-11-01 | Applicant | |
| WO2004045171(A1) | 2004-05-01 | Applicant | |
| WO2005015925(A2) | 2005-02-01 | Applicant | |
| WO2005020108(A1) | 2005-03-01 | Applicant | |
| WO2006/045005(A1) | 2006-04-01 | Applicant | |
| WO2006/045102(A2) | 2006-04-01 | Applicant | |
| WO2006/053952(A1) | 2006-05-01 | Applicant | |
| WO2006/053954(A1) | 2006-05-01 | Applicant | |
| WO2006/058967(A1) | 2006-06-01 | Applicant | |
| WO2007/015725(A2) | 2007-02-01 | Applicant | |
| WO2007/015726(A1) | 2007-02-01 | Applicant | |
| WO2007/149526(A2) | 2007-12-01 | Applicant | |
| WO2007/149540(A2) | 2007-12-01 | Applicant |
Non-Patent Literature (222)
- Allchin, James E., “An Architecture for Reliable Decentralized Systems”, UMI Dissertation Services, Copyright 1983.Applicant
- Lotus Development Corporation, Lotus Notes Release 3.1. The Groupware Standard, Administrator's Guide-Server for NetWare, OS/2 and UNIX, 1989.Applicant
- Lotus Development Corporation, Lotus Notes Release 3.1. The Groupware Standard, Site and Systems Planning Guide, 1991.Applicant
- Wilcox, Adam A., PC Learning Labs Teaches Lotus Notes 3.0: The Quick and Easy Way to Learn Ziff-Davis Press, 1993.Applicant
- Lotus Development Corporation, Lotus Notes Release 3.3: Start Here, Workstation Install for Windows, OS/2 and Macintosh, 1993.Applicant
- Lotus Development Corporation, Lotus Notes Release 3.1: Administrator's Guid- Server for Windows, 1993.Applicant
- Lotus Development Corporation, Lotus Notes Release 3.1: The GroupWare Standard, Customer Services Application Guide, 1994.Applicant
- Lotus Development Corporation, Lotus Notes Release 3.1: The GroupWare Standard, Getting Started with Application Development, 1994.Applicant
- Lotus Development Corporation, Lotus Notes Release 3.1: The GroupWare Standard, Network Driver Documentation, 1994.Applicant
- Kornblith, Polly R., Lotus Notes Answers: Certified Tech Support, Covers Lotus Notes Release 3, Osborne McGraw-Hill, 1994.Applicant
- Freeland, Pat and Londergan, Stephen, Lotus Notes 3/3.1 for Dummies TM, IDG Books Worldwide, 1994.Applicant
- Gewirtz, David, Lotus Notes 3 Revealed! Your Guide to Managing Information and Improving Communication Throughout Your Organization, Prima Publishing, 1994.Applicant
- Shafran, Andrew B., Easy Lotus Notes for Windows™, QueÒ Corporation, 1994.Applicant
- Lotus Development Corporation, Lotus Notes Release 3.3: The Groupware Standard, Administration, 1994.Applicant
- McMullen, Melanie, Editor, Network Remote Access and Mobile Computing, Miller Freeman, Inc., 1994.Applicant
- Lotus Development Corporation, Lotus Notes: The Groupware Standard-Windows, 1994.Applicant
- IntelliLink Corporation, IntelliLink® For Windows User's Guide, Version 3.0, 1994.Applicant
- Lotus Development Corporation, Lotus Notes Release 4: InterNotes Web Navigator Administrator's Guide, 1995.Applicant
- Lotus Development Corporation, Lotus Notes Release 4 Install Guide for Servers, 1995.Applicant
- Lotus Development Corporation, Lotus Notes Release 4.1 Release Notes, 1995.Applicant
- Lotus Development Corporation, Lotus Notes Release 4 Migration Guide, 1995.Applicant
- Lotus Development Corporation, Lotus Notes Release 4 Database Manager's Guide, 1995.Applicant
- Lotus Development Corporation, Lotus Notes Release 4 Install Guide for Workstations, 1995.Applicant
- Lotus Development Corporation, Lotus Step by Step: A Beginner's Guide to Lotus Notes, 1995.Applicant
- Lotus Development Corporation, Lotus Notes Release 4 Programmer's Guide Part 1, 1995.Applicant
- Lotus Development Corporation, Lotus Notes Release 4 Programmer's Guide Part 2, 1995.Applicant
- Lotus Development Corporation, Lotus Notes Release 4 Administrator's Guide, 1995.Applicant
- Lotus Development Corporation, Lotus Notes Release 4 Deployment Guide, 1995.Applicant
- Lotus Development Corporation, Lotus Notes Release 4 Application Developer's Guide, 1995.Applicant
- Lotus Development Corporation, Lotus Notes Release 4 InterNotes Web Navigator User's Guide, 1995.Applicant
- Lotus Development Corporation, Lotus Notes Release 4 Release Notes, 1995.Applicant
- Lotus Development Corporation, Lotus Notes Release 4.5 Install Guide for Workstations, 1995.Applicant
- Lotus Development Corporation, Release Notes, Lotus Notes Release 3.30, Windows, OS/2, and Macintosh, 1995.Applicant
- Brown, Kevin, et al., Mastering LotusÒ NotesÒ, SYBEX Inc., 1995.Applicant
- Lotus Development Corporation, Lotus Notes Release 4.5, Network Configuration Guide, 1995.Applicant
- Netscape Communications Corporation, Installation Guide, Netscape Mail Server, Version 2.0 for Unix, 1995.Applicant
- Netscape Communications Corporation, Administrator's Guide, Netscape Mail Server, Version 2.0, 1995.Applicant
- Pyle, Hugh, “The Architecture of Lotus Notes”, Lotus Notes Advisor, Advisor Publications, Premiere Issue 1995, pp. 18-27.Applicant
- Lotus Notes Advisor, Advisor Publications, Jun. 1995, entire magazine.Applicant
- IBM, “The Architecture of Lotus Notes”, White Paper, No. 114654, Modified date: May 31, 1995.Applicant
- Lotus Development Corporation, Lotus Notes Knowledge Base, “What is the Notes Repilcator”, Jul. 5, 1995.Applicant
- Lotus Notes Advisor, Advisor Publications, Aug. 1995, entire magazine.Applicant
- Grous, Paul J., “Creating and Managing a Web Site with Lotus' InterNotes Web Publisher”, The View Technical Journal for Lotus NotesÒ Software, vol. 1, Issue 4, Sep./Oct. 1995, pp. 3-18.Applicant
- Lotus Notes Advisor, Advisor Publications, Oct. 1995, entire magazine.Applicant
- Cole, Barb, “Lotus airs Notes-to-database integration tool”, www.looksmart.com, Oct. 2, 1995.Applicant
- Lotus Development Corporation, Lotus Notes Knowledge Base, “Lotus Announces Lotus NotesPump 1.0”, Oct. 31, 1995.Applicant
- Lotus Development Corporation, Lotus Notes Knowledge Base, “Lotus NotesPump 1.0 Q & A”, Oct. 31, 1995.Applicant
- Lotus Development Corporation, Lotus Notes Knowledge Base, “Lotus NotesPump: Database Integration for Lotus Notes”, Oct. 31, 1995.Applicant
- Lotus Development Corporation, Lotus Notes Knowledge Base, “How to Set Up “Firewall” Protection for a Notes Domain”, Nov. 6, 1995.Applicant
- Balaban, Bob, “This is Not Your Father's Basic: LotusScript in Notes Release 4”, Lotus Notes Advisor, Advisor Publications, vol. 1, No. 5, Nov./Dec. 1995, pp. 31-58.Applicant
- Pyle, Lisa, “A Jump Start to the Top Ten R3-to-R4 Migration Considerations”, Lotus Notes Advisor, Advisor Publications, vol. 1, No. 5, Nov./Dec. 1995, pp. 3-20.Applicant
- Lotus Notes Advisor, Advisor Publications, Dec. 1995, entire magazine.Applicant
- Lotus Development Corporation, Lotus Notes Release 4 Install Guide for Workstations, First Revision, 1996.Applicant
- Freeland, Pat and Londergan, Stephen, Lotus Notes 4 for Dummies™, IDG Books Worldwide, 1996.Applicant
- Kreisle, Bill, Teach yourself . . . Lotus Notes 4, MIS: Press, 1996.Applicant
- Marmel, Elain, Easy LotusÒ Notes Release 4.0, Que Corporation, 1996.Applicant
- Lotus Development Corporation, Lotus Notes Server Up and Running!, Release 4, 1996.Applicant
- Falkner, Mike, “How to Plan, Develop, and Implement Lotus Notes in Your Organization”, Willy Computer Publishing, John Wiley and Sons, Inc., 1996.Applicant
- Lamb, John P., et al., “Lotus Notes Network Design”, McGraw-Hill, 1996.Applicant
- Tamura, Randall A., et al., Lotus Notes 4 Unleashed, Sams Publishing, 1996.Applicant
- Dahl, Andrew, Lotus Notes 4 Administrator's Survival Guide, Sams Publishing, 1996.Applicant
- Netscape Communications Corporation, Administrator's Guide, Netscape News Server, Version 2.0, 1996.Applicant
- Lotus Development Corporation, Lotus Notes Internet Cookbook for Notes Release 3, Jan. 16, 1996.Applicant
- Wong, Harry, “Casahl's Replic-Action: Delivering True Notes/DBMS Integration”, The View Technical Journal for Lotus Notes Software, vol. 2, Issue 1, Jan./Feb. 1996, pp. 33-50.Applicant
- Lotus Notes Advisor, Advisor Publications, Jan./Feb. 1996, entire magazine.Applicant
- IBM International Technical Support Organization, Lotus Notes Release 4 in a Multiplatform Environment, Feb. 1996.Applicant
- Lotus Development Corporation, Lotus Notes Internet Cookbook for Notes Release 4, Feb. 14, 1996.Applicant
- Blaney, Jeff, “You Can Take it with you: An Introduction to Mobile Computing with Notes R4”, The View Technical Journal for Lotus Notes Software, vol. 2, Issue 1, Jan./Feb. 1996, pp. 22-32.Applicant
- Lotus Notes Advisor, Advisor Publications, Apr. 1996, entire magazine.Applicant
- Frankel, Garry, “Pumping for Info: Notes and Database Integration”, Network Computing, May 1, 1996, pp. 76-84.Applicant
- Lotus Development Corporation, Lotus Notes Knowledge Base, “Firewall Security Overview and How Firewalls Relate to Lotus Notes”, May 22, 1996.Applicant
- Lotus Notes Advisor, Advisor Publications, Jun. 1996, entire magazine. .Applicant
- Augun, Audry, “Integrating Lotus Notes with Enterprise Data”, Lotus Notes Advisor Publications, Jul./Aug. 1996, pp. 22-25.Applicant
- Lotus Notes Advisor, Advisor Publications, Aug. 1996, entire magazine.Applicant
- IBM Corporation, Secrets to Running Lotus Notes: The Decisions No One Tells You How to Make, Oct. 1996.Applicant
- Lotus Notes Advisor, Advisor Publications, Oct. 1996, entire magazine.Applicant
- Opyt, Barbara, et al., “Use the Internet as Your Lotus Notes WAN”, Lotus Notes Advisor, Advisor Publications, Nov./Dec. 1996, pp. 17-20.Applicant
- Lotus Notes Advisor, Advisor Publications, Dec. 1996, entire magazine.Applicant
- Swedeen, Bret, et al., “Under the Microscope: Domino Replication”, LDD Today, Oct. 1, 1998.Applicant
- Lotus Development Corporation, Lotus Inside Notes: The Architecture of Notes and the Domino Server, 2000.Applicant
- “The History of Notes and Domino”, Lotus Developer Domain, Lotus, Sep. 29, 2003.Applicant
- Lotus Development Corporation, Lotus Quick Reference for SmartIcons for Lotus Notes Release 3.1, 1994; 4 pages.Applicant
- Lotus Development Corporation, Lotus Quick Reference for Windows and Presentation Manager for Lotus Notes Release 3; May, 1993; 6 pages.Applicant
- Lotus Development Corporation, Lotus Quick Reference for Macintosh for Lotus Notes Release 3; May, 1993; 6 pages.Applicant
- Lotus Development Corporation, Lotus Quick Reference for Application Developers for Lotus Notes Release 3; May 1993; 6 pages.Applicant
- Lotus Development Corporation, Lotus Customer Support Services, Lotus Notes Customer Support Guide;1995; 33 pages.Applicant
- Lotus Development Corporation, Lotus Software Agreement with Lotus Notes 4.0˜“Notes 4.0 NA DKTP CLIENT UPG”, Part No. 38985; Jan. 1996; 8 pages.Applicant
- Lotus Development Corporation, Lotus Customer Support˜North American Guide; 1996; 8 pages.Applicant
- Lotus Development Corporation, Lotus NotesPump 1.0 Release Notes; Oct. 1995; 8 pages.Applicant
- Overview, What is Lotus NotesPump?; 87 pages.Applicant
- Chapter: “About NotesPump”, Release 2.0; Jun. 1996; 480 pages.Applicant
- Lotus Development Corporation, Lotus Notes 4 Administration Help, screenshots; 1996, 17 pages.Applicant
- Lotus Development Corporation, LotusScript Classes for Notes Release 4, scans from Part No. JA0476; 1996, 6 pages.Applicant
- Chapter 13-1, publication unknown, “Anatomy of a Note ID”; Jun. 1996; 8 pages.Applicant
- Lotus Development Corporation, Lotus Notes 3.3, Lotus Customer Support, North American Guide; 1995; 33 pages.Applicant
- Lotus Development Corporation, Lotus Notes 4.0, Lotus Customer Support, North American Guide; 1996; 29 pages.Applicant
- Haas, Zygmunt J. et al., “Mobile-TCP: An Asymmetric Transport Protocol Design for Mobile Systems,” IEEE, pp. 1054-1058, 1997.Applicant
- Haas, Zygmunt J. et al., “The Design and Performance Of Mobile TCP for Wireless Networks,” Journal of High Speed Networks, vol. 10, pp. 187-207, 2001.Applicant
- Hajdu, Kalman et al., “Lotus Notes Release 4 In a Multiplatform Environment,” IBM Corporation, 173 pp., Feb. 1996.Applicant
- Hardy, Ed, “Microsoft Proposes Two New Thumb-Driven User Interfaces,” Brighthand Consulting, Inc., 2 pages, 2003.Applicant
- IBM Corporation, “The Architecture of Lotus Notes,” White Paper No. 114654, 26 pages, May 31, 1995.Applicant
- IBM Corporation, “The History of Notes and Domino,” Lotus Developer Domain, 11 pages, Sep. 29, 2003.Applicant
- ImTOO, “ImTOO iPod Movie Converter,” 3 pages, Nov. 9, 2005.Applicant
- IntelliLink Corporation, “IntelliLink® For Windows User's Guide,” Version 3.0, 167 pages, 1994.Applicant
- International Application No. PCT/US2003/000618, International Search Report, 1 page, Apr. 4, 2003.Applicant
- International Application No. PCT/US2003/000624, International Search Report, 2 pages, May 13, 2003.Applicant
- International Application No. PCT/US2005/037702, International Preliminary Examination Report, 6 pages, Nov. 20, 2007.Applicant
- International Application No. PCT/US2005/037702, International Search Report, 1 p., Nov. 5, 2007.Applicant
- International Application No. PCT/US2005/037702, Written Opinion, 6 pages, Nov. 5, 2007.Applicant
- International Application No. PCT/US2005/038135, International Search Report, 2 pages, Aug. 8, 2008.Applicant
- International Application No. PCT/US2005/038135, Written Opinion, 8 pages, Aug. 8, 2008.Applicant
- International Application No. PCT/FI2005/050424, International Search Report, 4 pages, Mar. 2, 2006.Applicant
- International Application No. PCT/FI2005/050426, International Search Report, 3 pages, Mar. 1, 2006.Applicant
- International Application No. PCT/FI2005/050441, International Search Report, 3 pages, Mar. 1, 2006.Applicant
- International Application No. PCT/US2006/023426, International Search Report, 1 page, Feb. 21, 2007.Applicant
- International Application No. PCT/US2006/023427, International Search Report, 1 page, Oct. 12, 2006.Applicant
- International Application No. PCT/US2007/014462, International Search Report, 1 page, Jul. 2, 2008.Applicant
- International Application No. PCT/US2007/014497, International Search Report, 1 page, Aug. 25, 2008.Applicant
- Japanese Patent Application No. 2003-558726, Office Action, 2 pages, Jun. 10, 2008.Applicant
- Karlson, Amy K. et al., “AppLens And LaunchTile: Two Designs for One-Handed Thumb Use on Small Devices,” Proceedings of CHI 2005, 10 pages, Apr. 2-7, 2005.Applicant
- Kent, S. et al., “Security Architecture for the Internet Protocol,” RFC 2401, The Internet Society, 62 pages, Nov. 1998.Applicant
- Kleinberg, Jon, “The Small-World Phenomenon: An Algorithmic Perspective,” Cornell Computer Science Technical Report 99/1776, 14 pages, Oct. 1999.Applicant
- Koeppel, Dan, “GUIs Just Want to Have Fun,” Wired Magazine, Issue 8.10, 12 pages, Oct. 2000.Applicant
- Kornblith, Polly Russell, “Lotus Notes Answers: Certified Tech Support,” Covers Release 3, McGraw-Hill, Inc., 326 pages, 1994.Applicant
- Kreisle, Bill, “Teach Yourself. . .Lotus Notes 4,” MIS Press, 464 pages, 1996.Applicant
- Lamb, John P. et al., “Lotus Notes Network Design,” McGraw-Hill, 278 pages, 1996.Applicant
- Londergan, Stephen et al., “Lotus Notes® Release 4 for Dummies®,” IDG Books Worldwide, 229 pages, 1996.Applicant
- Lotus Development Corporation, “Firewall Security Overview and How Firewalls Relate to Lotus Notes,” Lotus Notes Knowledge Base, 9 pages, May 22, 1996.Applicant
- Lotus Development Corporation, “How to Set Up ‘Firewall’ Protection For A Notes Domain,” Lotus Notes Knowledge Base, 2 pages, Nov. 6, 1995.Applicant
- Lotus Development Corporation, “Lotus Announces Lotus NotesPump 1.0,” Lotus Notes Knowledge Base, 6 pages, Oct. 31, 1995.Applicant
- Lotus Development Corporation, “Lotus Inside Notes—The Architecture of Notes and the Domino Server,” 207 pages, 2000.Applicant
- Lotus Development Corporation, “Lotus NotesPump 1.0 Q & A,” Lotus Notes Knowledge Base, 3 pages, Oct. 31, 1995.Applicant
- Lotus Development Corporation, “Lotus NotesPump: Database Integration For Lotus Notes,” Lotus Notes Knowledge Base, 5 pages, Oct. 31, 1995.Applicant
- Lotus Development Corporation, “Lotus Notes Administration,” Release 3.3, 20 pages, 1995.Applicant
- Lotus Development Corporation, “Lotus Notes Administrator's Guide,” Release 4, 499 pages, 1995.Applicant
- Lotus Development Corporation, “Lotus Notes Administrator's Guide—Server For NetWare, OS-2, And Unix,” Release 3.1, 509 pages, 1994.Applicant
- Lotus Development Corporation, “Lotus Notes Administrator's Guide—Server for Windows,” Release 3.1, 345 pages, 1994.Applicant
- Lotus Development Corporation, “Lotus Notes Application Developer's Guide,” Release 4, 475 pages, 1995.Applicant
- Lotus Development Corporation, “Lotus Notes Customer Service Application Guide,” Release 3.1, 46 pages, 1994.Applicant
- Lotus Development Corporation, “Lotus Notes Customer Support Guide,” 33 pages, Date Unknown—published prior to Jan. 8, 2003.Applicant
- Lotus Development Corporation, “Lotus Notes Customer Support Guide—North American Guide,” Release 4.1, 51 pages, Date Unknown—published prior to Jan. 8, 2003.Applicant
- Lotus Development Corporation, “Lotus Notes Database Manager's Guide,” Release 4, 115 pages, 1995.Applicant
- Lotus Development Corporation, “Lotus Notes Deployment Guide,” Release 4, 104 pages, 1995.Applicant
- Lotus Development Corporation, “Lotus Notes for Windows, OS-2, and Macintosh,” Release 3.3, 89 pages, 1995.Applicant
- Lotus Development Corporation, “Lotus Notes Getting Started With Application Development,” Release 3.1, 151 pages, 1994.Applicant
- Lotus Development Corporation, “Lotus Notes Install Guide for Servers,” Release 4, 68 pages, 1996.Applicant
- Lotus Development Cprporation, “Lotus Notes Install Guide for Workstations,” Release 4, 28 pages, 1995.Applicant
- Lotus Development Corporation, “Lotus Notes Install Guide for Workstations,” Release 4.1, 67 pages, 1996.Applicant
- Lotus Development Corporation, “Lotus Notes Install Guide for Workstations,” Release 4.5, 81 pages, 1996.Applicant
- Lotus Development Corporation, “Lotus Notes Internet Cookbook for Notes Release 3,” 21 pages, Jan. 16, 1996.Applicant
- Lotus Development Corporation, “Lotus Notes Internet Cookbook for Notes Release 4,” 35 pages, Feb. 14, 1996.Applicant
- Lotus Development Corporation, “Lotus Notes Internotes Web Navigator Administrator's Guide,” Release 4, 60 pages, 1995.Applicant
- Lotus Development Corporation, “Lotus Notes Internotes Web Navigator User's Guide,” Release 4, 56 pages, 1995.Applicant
- Lotus Development Corporation, “Lotus Notes Internotes Web Publisher Guide,” Release 4, 122 pages, 1996.Applicant
- Lotus Development Corporation, “Lotus Notes LotusScript Classes for Notes,” Release 4, 6 pages, Date Unknown—published prior to Jan. 8, 2003.Applicant
- Lotus Development Corporation, “Lotus Notes Migration Guide,” Release 4, 110 pages, 1996.Applicant
- Lotus Development Corporation, “Lotus Notes Network Configuration Guide,” Release 4.5, 121 pages, 1996.Applicant
- Lotus Development Corporation, “Lotus Notes Network Driver Documentation,” Release 3.1, 100 pages, 1994.Applicant
- Lotus Development Corporation, “Lotus Notes Programmer's Guide - Part 1,” Release 4, 614 pages, 1995.Applicant
- Lotus Development Corporation, “Lotus Notes Programmer's Guide—Part 2,” Release 4, 462 pages, 1995.Applicant
- Lotus Development Corporation, “Lotus Notes Quick Reference for Application Developers,” Release 3, 6 pages, Date Unknown—published prior to Jan. 8, 2003.Applicant
- Lotus Development Corporation, “Lotus Notes Quick Reference for Macintosh,” Release 3, 6 pages, Date Unknown—published prior to Jan. 8, 2003.Applicant
- Lotus Development Corporation, “Lotus Notes Quick Reference for SmartIcons,” Release 3.1, 4 pates, Date Unknown˜published prior to Jan. 8, 2003.Applicant
- Lotus Development Corporation, “Lotus Notes Quick Reference for Windows and Presentation Manager,” Release 3, 6 pages, Date Unknown˜published prior to Jan. 8, 2003.Applicant
- Lotus Development Corporation, “Lotus Notes Release Notes,” Release 4, 139 pages, 1995.Applicant
- Lotus Development Corporation, “Lotus Notes Release Notes,” Release 4.1, 197 pages, 1996.Applicant
- Lotus Development Corporation, “Lotus Notes Server for Windows,” Release 3.3, 7 pages, 1994.Applicant
- Lotus Development Corporation, “Lotus Notes Server Up and Running!,” Release 4, 13 pages, 1996.Applicant
- Lotus Development Corporation, “Lotus Notes Site And Systems Planning Guide,” Release 3.1, 169 pages, 1994.Applicant
- Lotus Development Corporation, “Lotus Notes Start Here—Workstation Install for Windows, OS-2 and Macintosh,” Release 3.3, 47 pages, 1995.Applicant
- Lotus Development Corporation, “Lotus Notes Step by Step—A Beginner's Guide to Lotus Notes,” Release 4, 179 pages, 1995.Applicant
- Lotus Development Corporation, “Lotus Notes Step by Step—A Beginner's Guide to Lotus Notes,” Release 4.1, 167 pages, 1996.Applicant
- Lotus Development Corporation, “Lotus Software Agreement,” 8 pages, Date Unknown˜published prior to Jan. 8, 2003.Applicant
- Lotus Development Corporation, “What Is The Notes Replicator?,” Lotus Notes Knowledge Base, 8 pages, Jul. 5, 1995.Applicant
- “Lotus Notes Advisor,” Advisor Publications Inc., 55 pages, Jun. 1995.Applicant
- “Lotus Notes Advisor,” Advisor Publications Inc., 55 pages, Aug. 1995.Applicant
- “Lotus Notes Advisor,” Advisor Publications Inc., 55 pages, Oct. 1995.Applicant
- “Lotus Notes Advisor,” Advisor Publications Inc., 55 pages, Dec. 1995.Applicant
- “Lotus Notes Advisor,” Advisor Publications Inc., 63 pages, Jan.-Feb. 1996.Applicant
- “Lotus Notes Advisor,” Advisor Publications Inc., 55 pages, Apr. 1996.Applicant
- “Lotus Notes Advisor,” Advisor Publications Inc., 55 pages, Jun. 1996.Applicant
- “Lotus Notes Advisor,” Advisor Publications Inc., 55 pages, Aug. 1996.Applicant
- “Lotus Notes Advisor,” Advisor Publications Inc., 55 pages, Oct. 1996.Applicant
- “Lotus Notes Advisor,” Advisor Publications Inc., 63 pages, Dec. 1996.Applicant
- “Lotus Notes - Notes Administration Help,” Screen Shots, 17 pages, Date Unknown˜published prior to Jan. 8, 2003.Applicant
- MacGregor, Rob et al., “The Domino Defense: Security In Lotus Notes And The Internet,” IBM Corporation, 183 pages, Dec. 1997.Applicant
- Maltz, David A. et al., “MSOCKS: An Architecture For Transport Layer Mobility,” IEEE, pp. 1037-1045, 1998.Applicant
- Marmel, Elaine, “Easy Lotus® Notes Release 4.0,” Que Corporation, 237 pages, 1996.Applicant
- Mason, Luke, “Windows XP: New GUI Design Shows Skin Is in,” TechRepublic, 4 pages, Apr. 4, 2001.Applicant
- McMullen, Melanie, “Network Remote Access And Mobile Computing,” Miller Freeman Inc., 226 pages, 1994.Applicant
- Microsoft, Definition of “Access,” Microsoft Computer Dictionary, Fifth Edition, 2 pages, May 1, 2002.Applicant
- Microsoft, Definition of “Synchronization,” Microsoft Computer Dictionary, Fifth Edition, 2 pages, May 1, 2002.Applicant
- Milgram, Stanley, “The Small-World Problem,” Psychology Today, vol. 2, pp. 60-67, 1967.Applicant
- Miller, Victor S., “Use of Elliptic Curves In Cryptography,” Advances In Cryptology—CRYPTO '85 Proceedings, vol. 218, pp. 417-426, 1985.Applicant
- Myers, Brad A. et al., “Extending the Windows Desktop Interface With Connected Handheld Computers,” WSS'00 Proceedings of the 4th Conference on USENIX Windows Systems Symposium, vol. 4, 10 pages, 2000.Applicant
- Myers, Brad a. et al., “User Interfaces That Span Hand-Held And Fixed Devices,” CHI'2001 Workshop on Distributed and Disappearing User Interfaces in Ubiquitous Computer, 4 pages, 2001.Applicant
- National Institute of Standards and Technology, “Advanced Encryption Standard (AES),” Federal Information Processing Standards Publication 197, 52 pages, Nov. 26, 2001.Applicant
- National Institute of Standards and Technology, “Secure Hash Standard,” Federal Information Processing Standards Publication 180-2, 83 pages, Aug. 1, 2002.Applicant
- Netscape Communications Corporation, “Netscape Mail Server Administrator's Guide,” Version 2.0, 172 pages, 1996.Applicant
- Netscape Communications Corporation, “Netscape Mail Server Installation Guide,” Version 2.0 for Unix, 62 pages, 1996.Applicant
- Netscape Communications Corporation, “Netscape Mail Server User's Guide,” Version 2.0, 35 pages, 1996.Applicant
- Netscape Communications Corporation, “Netscape News Server Administrator's Guide For Windows NT,” Version 2.0, 119 pages, 1996.Applicant
- Niederée, Claudia et al., “A Multi-Dimensional, Unified User Model for Cross-System Personalization,” Proceedings of the AVI 2004 Workshop on Environments for Personalized Information Access, 11 pages, 2004.Applicant
- Nokia, “Developer Platforms,” 3 pages, 2005.Applicant
- “NotesPump 1.0 Release Notes,” Publication Unknown, 8 pages, Date Unknown˜published prior to Jan. 8, 2003.Applicant
- Opyt, Barbara et al., “Use The Internet As Your Lotus Notes WAN,” Lotus Notes Advisor, pp. 17-20, Nov.-Dec. 1996.Applicant
- Ortiz, C. Enrique, “An Introduction To The Symbian Os™ Platform for Palm OS® Developers,” Metrowerks Corp., 21 pages, 2002.Applicant
- “Overview˜What Is Lotus NotesPump?,” Publication Unknown, 88 pages, Date Unknown˜published prior to Jan. 8, 2003.Applicant
- Phillips, Joshua et al., “Modeling The Intelligence Analysis Process For Intelligent User Agent Development,” Research and Practice in Human Resource Management, vol. 9, No. 1, pp. 5973, 2001.Applicant
- Pyle, Hugh, “The Architecture Of Lotus Notes,” Lotus Notes Advisor, Premiere Issue, pp. 18-27, 1995.Applicant
- Pyle, Lisa, “A Jump Start To The Top Ten R3-To-R4 Migration Considerations,” The View, vol. 1, Issue 5, 22 pages, Nov.-Dec. 1995.Applicant
- Ringel, Meredith et al., “iStuff: A Scalable Architecture For Lightweight, Wireless Devices for Ubicomp User Interfaces,” Proceedings of UbiComp 2002, 2 pages, 2002.Applicant
- Shafran, Andrew Bryce, “Easy Lotus Notes® for Windows™,” Que Corporation, 199 pages, 1994.Applicant
- Signorini, Eugene, “SEVEN's Service-Based Wireless Solutions Enable Enterprises To Untether E-Mail, ” Wireless/Mobile Enterprise & Commerce, 16 pages, Oct. 2004.Applicant
- Swedeen, Bret et al., “Under the Microscope˜Domino Replication,” LDD Today, 8 pages, Oct. 1, 1998.Applicant
- Tamura, Randall A., “Lotus® Notes™ 4 Unleashed,” Sams Publishing, 928 pages, 1996.Applicant
- U.S. Appl. No. 60/663,463, File History, 113 pages, Mar. 18, 2005.Applicant
- Vivacqua, Adriana et al., “Profiling and Matchmaking Strategies In Support of Opportunistic Collaboration,” CoopIS/DOA/ODBASE 2003, LNCS 2888, pp. 162-177, 2003.Applicant
- Wainwright, Andrew, “Secrets To Running Lotus Notes: The Decisions No One Tells You How to Make,” IBM Corporation, 193 pages, Oct. 1996.Applicant
- Wilcox, Adam A., “PC Learning Labs Teaches Lotus Notes 3.0,” Ziff-Davis Press, 381 pages, 1993.Applicant
- Wong, Harry, “Casahl's Replic-Action: Delivering True Notes-DBMS Integration,” The View, vol. 2, Issue 1, pp. 33-50, Jan.-Feb. 1996.Applicant
- Lotus Development Corporation, “Lotus Notes Customer Support Guide˜North American Guide,” Release 4.1, 51 pages, Date Unknown˜published prior to Jan. 8, 2003.Applicant