Method and apparatus for intercepting events in a communication system
An intercept system provides more effective and more efficient compliance with legal intercept warrants. The intercept system can provide any combination of operations that include near-real-time intercept, capture of intercepted data in structured authenticated form, clear text intercept for communications where there is access to encryption keys, cipher text intercept for communications where there is no access to encryption keys, provision of transactional logs to the authorized agency, interception without altering the operation of the target services, and encryption of stored intercepted information.
Latest Seven Networks, Inc. Patents:
- System and method for a mobile device to use physical storage of another device for caching
- SECURE END-TO-END TRANSPORT THROUGH INTERMEDIARY NODES
- Managing cache to prevent overloading of a wireless network due to user activity
- Signaling optimization in a wireless network for traffic based on heart-beat messages
- Mobile traffic optimization and coordination and user experience enhancement
The present This patent application is a reissue application for commonly assigned U.S. Pat. No. 7,680,281, issued from U.S. patent application Ser. No. 12/211,790, filed on Sep. 16, 2008, which is a continuation of U.S. patent application Ser. No. 11/255,291, filed on Oct. 20, 2005, now U.S. Pat. No. 7,441,271, which claims priority to U.S. Provisional Patent Application No. 60/620,889, filed on Oct. 20, 2004, each of which are hereby incorporated by reference in their entirety.
BACKGROUNDWireless digital communication systems wirelessly transport electronic mail (email), text messages, text files, images, Voice Over Internet Protocol (VoIP) data, and any other types of digital data and communications to wireless devices. Wireless communication system providers are facing the prospects of having to comply with a variety of legal-intercept (wiretap) requirements. Authorization for a legal intercept may include warrants for “wiretap/interception”, “search and seizure”, or both. For example, the requirements outlined in CALEA (US Communications Assistance for Law Enforcement Act of 1994, http://www.askcalea.net/) may have to be met by any proposed solution. In another example, the requirements outlined by the Australian Communications Authority (http://www.aca.gov.au) in the Australia Telecommunications Act of 1997 may have to be met by any proposed solution.
There are several technical challenges complying with these legal intercept requirements that may not exist in conventional telephone systems. For example, the intercepted data may be encrypted. The wireless network provider must be able to intercept the encrypted data, and any other non-encrypted information, without tipping off the intercept target that the wiretap is taking place.
The wiretap warrant may require the communication system provider to provide any intercepted information in substantially real-time or may require the communication system provider to intercept and store communications in an automated manner for later retrieval and analysis by the law enforcement agency. Evidentiary problems exist with information intercepted outside the presence and control of the enforcement agency. For example, the intercepted communications could be either intentionally or inadvertently deleted. A system malfunction could also prevent some communications from being intercepted. There is also the evidentiary issue of whether or not someone has tampered with the intercepted information. It may also be necessary to prevent technicians operating the communication system from accessing or viewing the intercepted information.
The invention addresses these and other problems with the present technology.
SUMMARY OF THE INVENTIONAn intercept system provides more effective and more efficient compliance with legal intercept warrants. The intercept system can provide any combination of operations that include near-real-time intercept, capture of intercepted data in structured authenticated form, clear text intercept for communications where there is access to encryption keys, cipher text intercept for communications where there is no access to encryption keys, provision of transactional logs to the authorized agency, interception without altering the operation of the target services, and encryption of stored intercepted information.
The foregoing and other objects, features and advantages of the invention will become more readily apparent from the following detailed description of a preferred embodiment of the invention which proceeds with reference to the accompanying drawings.
In the description below, an intercept event refers to an event where an agency issues a warrant requesting data interception for a targeted user. A targeted user is identified by a unique label, such as a username or account number, that corresponds to a user who is under intercept. A communication event, transaction, or intercept data is any message either sent or received by the targeted user. The intercept data can include synchronization messages, email data, calendars, contacts, tasks, notes, electronic documents, files or any other type of data passing through the communication management system.
Communication Management System
The communication system 12 in one implementation is used for intercepting data pursuant to legal search warrants. For example, a law enforcement agency may require the operator of communication system 12 to intercept all messages sent to and from a mobile device 21. It should be understood that this is just one example of a communication system 12 and that the legal intercept system described in more detail below can operate with any communication network that is required to provide legal interception.
The communication system 12 includes a mobile network 14, an enterprise network 18, and a communication management system 16 that manages communications between the mobile network 14 and the enterprise network 18. The mobile network 14 includes mobile devices 21 that communicate with an IP infrastructure through a wireless or landline service provider. Since mobile networks 14 are well known, they are not described in further detail.
The enterprise network 18 can be any business network, individual user network, or local computer system that maintains local email or other data for one or more users. In the embodiment shown in
The PC 38 is connected to the server 34 over a Local Area Network (LAN) 35. The PC 38 includes memory (not shown) for storing local files that may include personal email data as well as any other types of electronic documents. Personal client software 40 is executed by a processor 37 in the PC 38. The personal client 40 enables the mobile device 21 to access email, calendars, and contact information as well as local files in enterprise network 18 associated with PC 38.
The communication management system 16 includes one or more management servers 28 that each include a processor 33. The processor 33 operates a transfer agent 31 that manages the transactions between the mobile device 21 and the enterprise network 18. A user database 42 includes configuration information for different users of the mobile communication service. For example, the user database 42 may include login data for mobile device 21.
While referred to as a communication management system 16 and management server 28, this can be any intermediary system that includes one or more intermediary servers that operate between the mobile network 14 and the enterprise or private network 18. For example, a separate Smart Device Server (SDS) 30 may be used in management system 16 for handling communications with mobile devices in mobile network 14. Correspondingly, a SEVEN Connection Server (SCS) 32 may be used for handling communications with personal clients in enterprise networks 18.
Legal Interception
A Legal Intercept (LI) software module 50 is operated by the processor 33 and communicates with the transfer agent 31 in order to capture intercept data 49 associated with targeted user 51B. An operator sets up a configuration file 51 that is then used by the legal intercept module to automatically intercept communications for a particular target user and then format the intercepted communications into self authenticating log files.
An operator runs a toolkit utility 54 from a computer terminal 52 to configure the management server 28 for capturing intercept data 49. The toolkit utility 54 is used for creating and loading the configuration file 51 into memory in management server 28 and can also display detected intercept data 49. To initiate an intercept, an entry is loaded into the configuration file 51. To stop capturing intercept data 49, the system administrator deletes the entry or configuration file 51 from memory. Changes to the configuration file 51 of management server 28 may be automatically replicated to other management servers that are part of the communication management system 16. The toolkit utility 54 may have tightly controlled access that only allows operation by a user with an authorized login and password.
The toolkit 54 allows the operator to view, add, modify, and delete a warrant sequence number 51A, user identifier (ID) 51B, and encryption key 57 in the configuration file 51. The warrant identifier may be the actual sequence number for a wiretap or search warrant issued by a court of law and presented to the operator of communication management system 16 by a federal, state, or municipal government agency. The user ID 51B for example may be an identifier used by communication management system 16 to uniquely identify different mobile clients 21.
The public encryption key 57 may be the public key component of a public/private key pair, such as a Pretty Good Privacy (PGP) or GNU Privacy Guard (GPG) public key, for encrypting the intercept data 49. In one embodiment, the legal intercept module 50 may not allow the management server 28 to start an interception process until a valid public key 57 is loaded into configuration file 51. This ensures that the intercepted data 49 can be immediately encrypted while being formatted into a log file 56. If this encryption fails for any reason, the legal intercept module 50 may shut down the intercept process ensuring that no intercept data 49 is stored in the clear.
The configuration file 51 may also include one or more entries defining a transport protocol, destination, and associated configuration values for the transmission of intercepted data via a network. In one embodiment, this could include a destination email address associated with a Simple Mail Transfer Protocol (SMTP) host and port number or other Internet Protocol (IP) destination address that is used by the legal intercept module 50 to automatically transmit the intercept data 49 to mail box 77 on a remote server 76 that is accessible by the agency issuing the warrant.
After the configuration file 51 is enabled, the legal intercept module 51 starts intercepting data 49 associated with the targeted user identified by user ID 51B. As mentioned above, this can include any emails, calendar information, contacts, tasks, notes, electronic documents, files or any other type of control or content data associated with user ID 51B. The intercepted data can include any type of communications such as email sent or received, calendar items sent or received, and other data sent/received by and from the targeted smart device 21. The captured intercept data 49 may then be encrypted using the encryption key 57 contained in the configuration file 51. The encrypted copy of the captured intercept data 49 may then be formatted and written to log file 56.
Data Delivery
The legal intercept module 50 running on each management server 28 may periodically poll the directory or location containing the encrypted intercept log files 56 for each user ID under intercept for the presence of new files or data. The poll period in one example is approximately every minute. Of course this is only one example and any user configurable time period can be used. New intercept data 49 which has been stored in one or more log files 56 and identified by the legal intercept module 50 during the polling process may be automatically reprocessed and/or transmitted according to the specification in configuration file 51. As an alternative to storing encrypted intercept data 49 in log file 56 on a file system, intercept data may be stored in database 42. Also, as shown in
In one implementation, an official from the agency physically sits at terminal 52 at the location of communication management system 16. The agency official then reads the log files 56 in semi-real-time as the intercept events 49 are being detected in the management server 49. The agency official then uses terminal 52 to store or copy the log files 56 onto a portable storage medium, such as a Compact Disc (CD), memory stick, etc. In this implementation, the legal intercept log files 56 may not reside in user database 42 at all, or may only reside in database 42 for some relatively brief period of time while being transferred onto the portable storage media.
A copy of the log files may be stored onto the portable storage medium while the same log files remain in the communication management system 16. The copy of the log files in the management system 16 could then be used, if necessary, for evidentiary purposes when admitting the copy under control of the agency official into evidence.
In an alternative implementation, the legal intercept module 50 may automatically send the log files 56 for the intercepted events to an email mailbox 77 operated in a remote server 76. The remote server 76 may be located in a wireless service provider network or may be located at the facilities of the enforcement agency issuing the warrant. In this implementation, a terminal 72 at the remote location 70 may include a toolkit utility 54 that has some of the same functionality as toolkit 54. The utility 54 only allows authorized users to decrypt and access the log files 56 received from communication management system 16.
For example, the toolkit utility 54 may include public and private PGP or GPG encryption keys 57 and 55, respectively, that are associated with the public encryption key 57 previously loaded into configuration file 51. Only personnel having authorized access to the toolkit 54 can decrypt and read the log files 56 previously generated and encrypted by legal intercept module 50. This provides additional privacy of the intercept data 49 from technical personnel of the communication management system 16 that may not be authorized to view the intercept data 49.
The intercept module 50 may transfer each captured log file 56 to a SMTP email server 76 via the Simple Mail Transfer Protocol (SMTP). The SMTP server 76 stores each log file 56 in an inbox of mailbox 77. The name of the mailbox 77 may be the same as the warrant sequence number @ the agency's domain name. For example, warrant123@LAPD.com. The warrant sequence number may correspond with the warrant identifier 51A in configuration file 51 and the domain name may correspond with the IP address 51D in configuration file 51. Once transmitted and accepted by the SMTP email server 76, the log file 56 may be automatically deleted from user database 42.
The agency issuing the warrant can retrieve the captured log files 56 in remote server 76 for a particular user ID under interception using for example the Post Office Protocol (POPv3). The agency is given the name of email server 76, POP and SMTP port numbers, the mailbox id (warrant sequence number 51) and a password to access the mailbox 77. The agency then retrieves log files 56 in mailbox 77 using POP. Once a file is downloaded from the mailbox 77 to an agency terminal 72, the log file 56 may be automatically deleted from the mailbox 77.
Log Files
Referring to
The log files 56 stored in directory 60 may indicate the number of events intercepted for the targeted device during each minute. For example, a first log file 56A is identified by the following log file name: fe0-2005/09/23-00:00.ASC, containing a single line that reads as follows: “0 events logged in the last minute”. This indicates that a management server fe0 on Sep. 23, 2005, at 12:00 midnight logged zero intercept events for a particular user ID during the specified time period. A second log file 56B is named to identify a next minute of the intercept period and indicates that between 12:00 A.M and 12:01 A.M, on the same day, no intercept events were logged.
The first detected intercept events for this particular user ID for this particular day were detected in log file 56C identified by the log file name: fe0-2005/09/23-00:02.ASC, the first and/or last line of which reads “3 events logged in the last minute”. Log file 56C indicates that 3 intercept events were detected on Sep. 23, 2005, between 12:01 A.M. and 12:02 A.M. The legal intercept 50 generates this contiguous set of log files 56 that cover each minute or other configured interval of the intercept period.
The legal intercept 50 may also load a first entry into the log file directory 60 that lists the warrant id 51A, PGP key 57, etc. The legal intercept 50 may also generate a log file 56 that indicates any management server status-change events. For example, if the management server 28 conducts a graceful shutdown, a log file 56 may be generated that indicates when the shut down occurred and possibly the cause of the shutdown.
This highly structured log file format provides the agency official a quick indicator of when intercept events are detected for a particular target user. Further, as shown above, the log files are created contiguously for predetermined time periods over a particular intercept period even when no intercept events are detected. This provides further verification that the legal intercept 50 was actually in operation and continuously monitoring for intercept events during the intercept period.
As described above, the log files 56 may be stored into a portable storage media that can be transported by an agency official. Alternatively, the log files 56 may be stored in the user database 42 in the communication management system 16 for later retrieval by the agency official via toolkit 54. In another implementation, the log files 56 may be sent to the mailbox 77 in a server 76 in a mobile operator infrastructure which is accessible by the agency official.
When intercept events are detected, all the intercepted data for that time period is formatted into a same log file 56 in operation 64. The log file is encrypted in operation 65 using the encryption key 57 (
When interception for a current interception period is completed, a Cyclic Redundancy Check (CRC) value, or some other type of digital certificate/signature, may be generated in operation 67. The CRC can be used to verify that the contents of intercept directory 60 have not been tampered with or deleted after their initial generation. The CRC may be encrypted in operation 68 and then separately emailed to the agency or separately stored for later validation. As discussed above, the encrypted log files may then either be emailed to a mailbox or stored locally for later retrieval by the enforcement agency.
Thus, the individual log file encryption in operation 65 ensures the authenticity of intercepted events for a particular time period and the CRC generated in operation 67 ensures that none of the individual log files have been removed or replaced.
Encrypted Intercept Data
Referring to
The mobile device 21 also negotiates a point-to-point security association, specifying a cryptographic ciphersuite and a unique encryption key 27, with the management server 28. In one example, the point-to-point encryption key 27 is also an AES encryption key. The negotiated security association that includes encryption key 27 enables secure point-to-point communication between the mobile device 21 and the management server 28 over connection 23. Each different mobile device 21 negotiates a different security association that includes a unique encryption key 27 with the management server 28.
The point-to-point encryption key 27 may be used for encrypting control data that needs to be transferred between the mobile device 21 and management server 28. The point-to-point encryption key 29 may be used for encrypting control data that needs to be transferred between the management server 28 and personal client 40. For example, the control data may include login information and transaction routing information.
An end-to-end security association, specifying a cryptographic ciphersuite and a unique encryption key 46, is negotiated between the mobile device 21 and the personal client 40. In one example, the end-to-end encryption key 46 is also an AES encryption key. The end-to-end encryption key 46 in one example is used for encrypting transaction payloads transferred between personal client 40 and mobile device 21. For example, the end-to-end encryption key 46 may be used for encrypting the content of emails, files, file path names, contacts, notes, calendars, electronic documents and any other type of data transferred between mobile device and the PC. The end-to-end encryption key 46 is only known by the mobile device 21 and the personal client 40. Data encrypted using the end-to-end key 46 cannot be decrypted by the management server 28.
Referring to
The communication management system 16 has access to the point-to-point encryption keys 27 and 29 used for encrypting the point-to-point encrypted information 49B. Therefore, the management system 16 can automatically decrypt the point-to-point encrypted information 49B before it is reformatted into log file 56.
The end-to-end encryption keys 46 are only shared between the endpoints 21 and 38 and are unknown to the communication management system 16. Therefore, the agency issuing the warrant may be required to extract the end-to-end encryption keys 46 either at the mobile device 21 or at the enterprise server 34 or personal computer 38. The end-to-end encrypted information 49C may then be decrypted at a later time separately from the point-to-point encrypted information 49B.
For example, after receiving and decrypting the log file 56, the enforcement agency may then independently conduct a seizure of the end-to-end encryption key 46 from either the enterprise network 18 or the mobile device 21. The enforcement agency could then separately decrypt information 56B in log file 56 with the seized end-to-end encryption key 46.
In operation 84, any point-to-point encrypted portion 49B of the intercepted data 49 (
Detecting Different Types of Intercept Data
A second portion 106 of intercept data 102 may include control information that only needs to be processed by one particular server. In this case, control data 106 may be encrypted using a first point-to-point encryption key. A third portion 104 of intercept data 102 may have other control information, for example, error checking data, that needs to be processed by a different server. Accordingly, the error checking data 104 is encrypted using a second point-to-point encryption key different than either of the other two encryption keys used for encrypting data 108 and 106.
It should be understood that this is only an example, and the devices shown in
The mobile device 21, management server 28, and the personal client 40 are all configured with an encryption schema 112 that identifies how specific items in the transaction 110 are to be encrypted. Each device is also configured with different security associations as described above in
The mobile device 21 forms the request transaction 110. One example of a request is as follows.
Mobile device 21 attaches an auth_token to transactions sent to the management server 28. For example, the mobile device 21 may be required to authenticate to the management server 28 by transmitting a username and password prior to being permitted to submit other transactions for processing. The management server 28 issues the mobile device 21 an auth_token after successfully validating the username and password against information in the user database 42. The mobile device 21 then attaches the auth_token to subsequent transactions sent to the management server 28. The management server 28 uses the auth_token to identify and authenticate the source of each transaction and to determine where to route the transaction.
The device_id identifies the particular mobile device 21 sending the request 110. The device_id may be necessary, for example, when a user has more than one mobile device. The personal client 40 can use different device_id values to track when synchronization information was last sent to each of multiple different mobile devices. The device_id can also be used by either the management server 28 or the personal client 40 to determine how to format data sent to particular types of mobile devices 21. For example, data may need to be formatted differently for a cell phone as opposed to a personal computer. The device_id can also be used to correlate a known security association with a particular mobile device.
The method_id item in the example identifies a particular function GetDocument associated with request 110. The method_id item also requires the inclusion of related argument items that identify the parameters for the GetDocument function. For example, the argument items might include the expression path=“/docs” identifying the pathname where the requested documents are located.
In order to prepare the request 110 for transmission, the mobile device 21 performs a pattern match of the request 110 using the encryption schema 112. This pattern match separates the items in request 110 into different channels. One example of the different channels is shown below. In this example, the items in each channel are associated with predefined security associations: clear, pp, and ee.
The channel contents are encoded (via a process commonly known as serialization) into arrays of bits or bytes referred to as data groups. These groupings of bits or bytes are referred to generally below as arrays, but can be any type of partition, group, etc.
The contents of the clear channel are encoded into an array of bits referred to as data_group—1, the contents of the pp channel are encoded into an array of bits referred to as data_group—2, and the contents of the ee channel are encoded into an array of bits referred to as data_group—3. The contents of each channel need to be encoded into bit arrays so that they can be encrypted. The contents of the channels after being encoded into bit arrays are represented as follows.
The bit arrays are then encrypted according to the security association parameters for each channel. According to the encryption schema 112, bits in the clear channel (data_group—1) are not encrypted. The bits in the pp channel data_group—2 are encrypted using the point-to-point security association between mobile device 21 and management server 28, using PP key 27, and are referred to after encryption as pp_data_group—2. The bits in the ee channel data_group—3 are encrypted using the end-to-end security association between mobile device 21 and personal client 40, using EE key 46, and are referred to after encryption as ee_data_group—3. The data groups are represented as follows after encryption:
The bits making up the encrypted and unencrypted channels are then encoded into one or more packets. For clarity, the description below will refer to a single packet, however, the data from the channels may be contained in multiple packets. Some of the contents of the packet are shown below.
Information in the packet header may include the packet length, a version number, and other flags. The packet payload includes a count identifying 3 pairs of items. The three items include the non-encrypted contents in the clear channel, the pp encrypted contents of the pp channel, and the ee encrypted contents of the ee channel. The packet is then transported by mobile device 21 to the management server 28.
The transfer agent operating in server 28 receives the packet. The bits in the packet are separated into the different channels clear=data_group—1, pp=pp_data_group—2, and ee=ee_data_group—3.
The data in the clear channel does not need to be decrypted. The transfer agent decrypts the only bits in channels for which it has a known security association. The transfer agent, as a member of the point-to-point security association between mobile device 21 and management server 28, possesses the PP key 27 and therefore decrypts the contents of the pp channel. The transfer agent is not a member of the end-to-end security association between mobile device 21 and personal client 40, does not have the EE key 46 and therefore does not decrypt the data in the ee channel. Decryption produces the following data groups: clear data_group—1, pp=data_group—2, and ee=ee_data_group—3.
The transfer agent decodes the contents of the clear and pp channels. The contents of the encrypted ee channel are not decoded, but instead are maintained in an unmodified state for eventual transport to the personal client 40. Decoding produces the following contents.
A partial request is formed by merging the items of the clear and pp channels. The partial request in this example could look similar to the following:
The transfer agent 31 in the management server 28 processes the partial request. In this example, the transfer agent may verify the request is authorized by matching the value of auth_token (“abc”) with contents in the user database 42 (
The transfer agent may identify a user_id=“joe” associated with the auth_token=“abc” and generate the following new request.
The legal intercept 50 in
The end-to-end encrypted data in group 3 remains encrypted and therefore may not provide all of the information desired for the enforcement agency. However, the decrypted information does provide enough information to adequately indicate that the intercepted data is associated with a particular user_id. The intercepted unencrypted data may also provide further evidence that the enforcement agency can then use to obtain another warrant to seize the ee encryption key from the targeted user.
As described above in
End-to-End Encrypted Data
As described above, the communication management system 16 may not have access to the end-to-end encryption keys 46 (
The intercept logs 56 can therefore contain data encrypted using encryption keys known only to the endpoints. For example, a mobile device 21 and a desktop connector running on personal computer 38 (
In order to make use of this functionality, the enforcement agency seeking the information may need to obtain both an intercept warrant, and either a search-and-seizure warrant authorizing the extraction of the configuration data from the smart device client in the mobile device 21 or a search-and-seizure warrant authorizing the extraction of the end-to-end encryption key from the desktop connector in the PC 38 (
After the authorized agency has executed the necessary warrants, the toolkit 54 is used by the agency to facilitate the recovery of the end-to-end key 46. The toolkit utility 54 then uses the end-to-end key 46 to decrypt the end-to-end encrypted information in the log files 56.
The system described above can use dedicated processor systems, micro controllers, programmable logic devices, or microprocessors that perform some or all of the operations. Some of the operations described above may be implemented in software and other operations may be implemented in hardware.
For the sake of convenience, the operations are described as various interconnected functional blocks or distinct software modules. This is not necessary, however, and there may be cases where these functional blocks or modules are equivalently aggregated into a single logic device, program or operation with unclear boundaries. In any event, the functional blocks and software modules or features of the flexible interface can be implemented by themselves, or in combination with other operations in either hardware or software.
Having described and illustrated the principles of the invention in a preferred embodiment thereof, it should be apparent that the invention may be modified in arrangement and detail without departing from such principles. Claim is made to all modifications and variation coming within the spirit and scope of the following claims.
Claims
1. A method for intercepting data, comprising:
- receiving, at a management server, a connection from a remote client, the connection being initiated by the remote client and established outbound from the remote client;
- negotiating a point-to-point encryption scheme with a remote mobile device, the point-to-point encryption scheme negotiated between the management server and the remote mobile device;
- receiving, at the management server, a value identifying an intercept target for a legal intercept and an indication that interception is authorized by a warrant, the intercept target corresponding to the remote mobile device;
- automatically intercepting, at the management server, data received and/or sent by the intercept target identified by the value, wherein data is intercepted without altering operation of email application services that operate on the remote mobile device;
- inspecting packets having the intercepted data to distinguish end-to-end encrypted information from other information that is encrypted according to the point-to-point encryption scheme negotiated with the remote mobile device;
- preserving encryption that is included on the end-to-end encrypted information when received while removing encryption that is included on at least a portion of the other information, said other information decrypted using a key obtained during the point-to-point encryption scheme negotiation; and
- transferring both the decrypted other information and the end-to-end information from the management server to a remote device.
2. The method of claim 1, wherein the packets are intercepted during a requested time period, and the method further comprises:
- formatting the data that is intercepted during the requested time period and associated with the target user into one or more first log files, each of the first log files corresponding to a different time segment occurring during the requested time period and indicating one or more intercept events for its corresponding time segment; and
- formatting one or more second different log files associated with the requested time period, the second log files indicating inactivity and corresponding to different remaining time segments that occur during the requested time period and that are unrepresented by the first log files that indicate the intercept events such that the first and second log files record monitoring for the entire requested time period independently of whether the data is intercepted intermittently during the requested time period.
3. The method of claim 2, wherein the data is intercepted according to an intercept configuration file that includes at least a unique intercept identifier and a user ID identifying the target user.
4. The method of claim 2, wherein the log files record an unbroken sequence of continuous monitoring over the requested time period independently of whether the data is intercepted intermittently.
5. The method of claim 2, further comprising transferring the log files to the remote device.
6. The method of claim 2, further comprising formatting the log files with different time values usable for verifying that communications from the remote mobile device were continuously monitored during the requested time period regardless of whether the data was intercepted intermittently.
7. The method according to claim 1, wherein the encryption that is included on the end-to-end encrypted information uses a security association that is kept secret from the management server such that the end-to-end encrypted information is kept private with respect to employees associated with the management server.
8. The method of claim 1, further comprising determining whether to encrypt at least one of the end-to-end information and the decrypted information prior to said transferring.
9. The method according to claim 1, further comprising:
- combining, at the management server, the end-to-end encrypted information of the intercepted data with the decrypted other information of the intercepted data in a same log file.
10. The method according to claim 1, further comprising:
- storing, at the management server, the intercepted data in a structure format that identifies when the data was intercepted and at the same time provides authentication that the stored intercepted data has not been altered or deleted.
11. The method according to claim 10, further comprising monitoring communications between the remote client and the remote mobile device for multiple contiguous time periods.
12. The method according to claim 11, further comprising:
- generating, using the management server, log files over an intercept period that encompasses the multiple contiguous time periods;
- storing the log files in a same intercept directory;
- inserting a warrant identifier received together with the value into the intercept directory; and
- generating a name for the intercept directory that identifies the intercept target and the intercept period over which the log files were generated.
13. The method according to claim 12, further comprising:
- encrypting the log files in the intercept directory with an encryption scheme known by an agency issuing the warrant, said encryption performed using the management server that intercepted the data; and
- sending the encrypted intercept directory to an electronic mailbox accessible by the agency.
14. The method according to claim 13, further comprising:
- generating a Cyclic Redundancy Check (CRC) or other digital signature value for all of the log files in the intercept directory;
- encrypting the resulting generated value; and
- providing the encrypted generated value to the enforcement agency, said encrypted generated value sent in a different communication than the encrypted intercept directory, said encrypted generated value verifying that the log files have not been altered.
15. The method according to claim 1, further comprising: reading an intercept configuration file that contains a warrant identifier, the value identifying the user, an enforcement agency known encryption key and an electronic mailbox address;
- upon reading the intercept configuration file automatically intercepting data received and/or sent by the remote mobile device;
- formatting any intercepted data into log files that identify when the data was intercepted; and
- encrypting the log files using the encryption key.
16. The method according to claim 1, wherein the end-to-end encrypted information is associated with content and is protected with an end-to-end encryption scheme that is kept secret from any midpoints located on a call path between transmitting and receiving endpoints, and the other information is associated with transaction routing information and is protected with the negotiated point-to-point encryption scheme.
17. A communication management system, comprising:
- a management server configured to receive a connection initiated by a remote client and established outbound from the remote client;
- the management server configured to negotiate a point-to-point encryption scheme with a remote mobile device, the point-to-point encryption scheme negotiated between the management server and the remote mobile device;
- the management server configured to receive a value identifying an intercept target for a legal intercept and an indication that interception is authorized by a warrant, the intercept target corresponding to the remote mobile device;
- the management server configured to automatically intercept data received and/or sent by the intercept target identified by the value, wherein the data is intercepted without altering operation of email application services that operate on the remote mobile device;
- the management server configured to inspect packets having the intercepted data to distinguish end-to-end encrypted information from other information that is encrypted according to the point-to-point encryption scheme negotiated with the remote mobile device;
- the management server configured to preserve encryption that is included on the end-to-end encrypted information when received while removing encryption that is included on at least a portion of the other information, said other information decrypted using a key obtained during the point-to-point encryption scheme negotiation; and
- the management server configured to transfer both the decrypted other information and the end-to-end information from the management server to a remote device.
18. The communication management system of claim 17, further comprising:
- the management server configured to automatically format the intercepted data into log files;
- the management server configured to generate multiple log files that identify any intercepted data for associated contiguous predetermined time periods extending over a continuous intercept period; and
- the management server configured to generate the log files for back-to-back time periods, the management server further configured to generate each log file by selecting between inserting the intercepted data and an inactivity indication therein such that each of the log files contains at least one selected from the group comprising the intercepted data for the associated time period and an indication that no data was intercepted during the associated time period.
19. The communication management system of claim 18, further comprising:
- the management server is configured to select a same duration for the time periods according to selectable time interval values included in an intercept configuration file.
20. The communication management system of claim 18, further comprising:
- the management server configured to encrypt the log files according to an encryption key known by an enforcement agency associated with the warrant before emailing the encrypted log files to a mailbox for the enforcement agency.
21. The communication management system of claim 18, further comprising:
- the management server configured to identify a first portion of the intercepted data encrypted using a first known security association for which the management server has knowledge of the encryption key and identify a second portion of the intercepted data encrypted using a second unknown security association, the management server configured to decrypt and store the first portion of the intercepted data into an associated one of the log files and combine the encrypted second portion of the intercepted data with the decrypted first portion of the intercepted data in the same associated log file.
22. The communication management system of claim 21, wherein the first portion of the intercepted data is encrypted with a known point-to-point encryption key and the second portion of the intercepted data is encrypted with an unknown end-to-end encryption key.
23. The communication management system of claim 21, further comprising:
- the management server is configured to encrypt both the decrypted first portion of the intercepted data and the second encrypted portion of the intercepted data.
24. The communication management system of claim 21, wherein the first portion of the intercepted data includes transaction authentication and routing information and the second portion of the intercepted data includes the contents of email messages, electronic files, or other electronic data.
25. The communication management system of claim 17, wherein the management server is configured to process communications exchanged between a local device operating in an enterprise or local network and a mobile wireless device that synchronizes with a portion of the data in the local device.
26. A method for intercepting data, comprising:
- in response to receiving a connection request, negotiating a point-to-point encryption scheme with a mobile device, the point-to-point encryption scheme negotiated between a management server and the mobile device;
- automatically intercepting, at the management server, data received and/or sent by an intercept target, wherein data is intercepted without altering operation of application services on the mobile device;
- inspecting packets having the intercepted data to distinguish end-to-end encrypted information from other information that is encrypted according to the point-to-point encryption scheme negotiated with the device;
- preserving encryption that is included on the end-to-end encrypted information when received while removing encryption that is included on at least a portion of the other information, said other information decrypted using a key obtained during the point-to-point encryption scheme negotiation; and
- transferring both the decrypted other information and the end-to-end information.
27. The method of claim 26, further comprising, receiving, at the management server, a value identifying the intercept target for a legal intercept and an indication that interception is authorized by a warrant, the intercept target corresponding to the mobile device.
28. The method of claim 26, wherein the packets are intercepted during a requested time period, and the method further comprises: formatting the data that is intercepted during the requested time period and associated with a target user into one or more first log files.
29. The method of claim 28, wherein: each of the first log files corresponding to a different time segment occurring during the requested time period and indicating one or more intercept events for its corresponding time segment.
30. The method of claim 29, further comprising:
- formatting one or more second different log files associated with the requested time period, the second log files indicating inactivity and corresponding to different remaining time segments that occur during the requested time period and that are unrepresented by the first log files that indicate the intercept events such that the first and second log files record monitoring for the entire requested time period independently of whether the data is intercepted intermittently during the requested time period.
31. The method of claim 28, wherein the log files record an unbroken sequence of continuous monitoring over the requested time period independently of whether the data is intercepted intermittently.
32. The method of claim 28, further comprising formatting the log files with different time values usable for verifying that communications from the mobile device were continuously monitored during the requested time period regardless of whether the data was intercepted intermittently.
33. The method of claim 26, wherein the data is intercepted according to an intercept configuration file that includes at least a intercept identifier and a user ID identifying a target user.
34. The method of claim 26, wherein the encryption that is included on the end-to-end encryption information uses a security association that is kept secret from the management.
35. The method of claim 26, further comprising determining whether to encrypt at least one of the end-to-end information and the decrypted information prior to said transferring.
36. The method according to claim 26, further comprising:
- combining the end-to-end encrypted information of the intercepted data with the decrypted other information of the intercepted data in a log file.
37. The method according to claim 26, further comprising:
- storing the intercepted data in a structure format that identifies when the data was intercepted and provides authentication that the stored intercepted data has not been altered or deleted.
38. The method according to claim 26, further comprising monitoring communications between a remote client and the device for multiple contiguous time periods.
39. The method according to claim 38, further comprising:
- generating log files over an intercept period that encompasses the multiple contiguous time periods;
- storing the log files in a same intercept directory.
40. The method according to claim 39, further comprising:
- inserting a warrant identifier received together with the value into the intercept directory; and
- generating a name for the intercept directory that identifies the intercept target and the intercept period over which the log files were generated.
41. The method according to claim 39, further comprising:
- encrypting the log files in the intercept directory with an encryption scheme known by an agency issuing the warrant, said encryption performed using the management server that intercepted the data; and
- sending the encrypted intercept directory to an electronic mailbox accessible by the agency.
42. The method according to claim 39, further comprising:
- generating a Cyclic Redundancy Check (CRC) or other digital signature value for all of the log files in the intercept directory;
- encrypting the resulting generated value; and
- providing the encrypted generated value to the enforcement agency, said encrypted generated value sent in a different communication than the encrypted intercept directory, said encrypted generated value verifying that the log files have not been altered.
43. The method according to claim 26, further comprising:
- reading an intercept configuration file that contains a warrant identifier, the value identifying the user, an enforcement agency known encryption key and an electronic mailbox address;
- upon reading the intercept configuration file automatically intercepting data received and/or sent by the remote mobile device;
- formatting any intercepted data into log files that identify when the data was intercepted; and
- encrypting the log files using the encryption key.
44. The method according to claim 26, wherein the end-to-end encrypted information is associated with content and is protected with an end-to-end encryption scheme that is kept secret from any midpoints located between transmitting and receiving endpoints, and the other information is associated with transaction routing information and is protected with the point-to-point encryption scheme.
45. A communication management system for intercepting data, comprising:
- a processor;
- a network interface configured to receive a connection request; and
- a memory unit having instructions stored thereon, wherein the instructions, when executed by the processor, causes the communication management system to: negotiate a point-to-point encryption scheme; inspect packets having the data to be intercepted to distinguish end-to-end encrypted information from other information that is encrypted according to the point-to-point encryption scheme; preserve encryption that is included on the encrypted information when received while removing encryption that is included on at least a portion of the other information, said other information decrypted using a key obtained in association with the point-to-point encryption scheme; transfer both the decrypted other information and the end-to-end encrypted information; automatically format the intercepted data into log files including: generating log files that identify intercepted data for associated contiguous predetermined time periods extending over a continuous intercept period; and generating the log files for back-to-back time periods, the management server generating each log file by selecting between inserting the intercepted data and an inactivity indication therein such that each of the log files contains at least one selected from the group including the intercepted data for the associated time period and an indication that no data was intercepted during the associated time period; negotiate the point-to-point encryption scheme with a mobile device in response to receiving the connection request, and intercept data received and/or sent by an intercept target, wherein data is intercepted without altering operation of application services on the mobile device.
222458 | December 1879 | Connolly et al. |
447918 | March 1891 | Strowger |
4200770 | April 29, 1980 | Hellman et al. |
4255796 | March 10, 1981 | Gabbe et al. |
4276597 | June 30, 1981 | Dissly et al. |
4531020 | July 23, 1985 | Wechselberger et al. |
4807182 | February 21, 1989 | Queen |
4831582 | May 16, 1989 | Miller et al. |
4875159 | October 17, 1989 | Cary et al. |
4897781 | January 30, 1990 | Chang et al. |
4972457 | November 20, 1990 | O'Sullivan |
5008853 | April 16, 1991 | Bly et al. |
5159624 | October 27, 1992 | Makita |
5220657 | June 15, 1993 | Bly et al. |
5263157 | November 16, 1993 | Janis |
5283856 | February 1, 1994 | Gross et al. |
5357431 | October 18, 1994 | Nakada et al. |
5384892 | January 24, 1995 | Strong |
5386564 | January 31, 1995 | Shearer et al. |
5392390 | February 21, 1995 | Crozier |
5434994 | July 18, 1995 | Shaheen et al. |
5436960 | July 25, 1995 | Campana, Jr. et al. |
5438611 | August 1, 1995 | Campana, Jr. et al. |
5479472 | December 26, 1995 | Campana, Jr. et al. |
5487100 | January 23, 1996 | Kane |
5491703 | February 13, 1996 | Barnaby et al. |
5493692 | February 20, 1996 | Theimer et al. |
5519606 | May 21, 1996 | Frid-Nielsen et al. |
5555376 | September 10, 1996 | Theimer et al. |
5559800 | September 24, 1996 | Mousseau et al. |
5572571 | November 5, 1996 | Shirai |
5572643 | November 5, 1996 | Judson |
5574859 | November 12, 1996 | Yeh |
5581749 | December 3, 1996 | Hossain et al. |
5600834 | February 4, 1997 | Howard |
5603054 | February 11, 1997 | Theimer et al. |
5604788 | February 18, 1997 | Tett |
5613012 | March 18, 1997 | Hoffman et al. |
5619507 | April 8, 1997 | Tsuda |
5619648 | April 8, 1997 | Canale et al. |
5623601 | April 22, 1997 | Vu |
5625670 | April 29, 1997 | Campana, Jr. et al. |
5625815 | April 29, 1997 | Maier et al. |
5627658 | May 6, 1997 | Connors et al. |
5630081 | May 13, 1997 | Rybicki et al. |
5631946 | May 20, 1997 | Campana, Jr. et al. |
5632018 | May 20, 1997 | Otorii |
5634053 | May 27, 1997 | Noble et al. |
5647002 | July 8, 1997 | Brunson |
5652884 | July 29, 1997 | Palevich |
5664207 | September 2, 1997 | Crumpler et al. |
5666530 | September 9, 1997 | Clark et al. |
5666553 | September 9, 1997 | Crozier |
5680542 | October 21, 1997 | Mulchandani et al. |
5682524 | October 28, 1997 | Freund et al. |
5684990 | November 4, 1997 | Boothby |
5689654 | November 18, 1997 | Kikinis et al. |
5692039 | November 25, 1997 | Brankley et al. |
5696903 | December 9, 1997 | Mahany |
5701423 | December 23, 1997 | Crozier |
5701469 | December 23, 1997 | Brandli et al. |
5704029 | December 30, 1997 | Wright, Jr. |
5706211 | January 6, 1998 | Beletic et al. |
5706502 | January 6, 1998 | Foley et al. |
5706507 | January 6, 1998 | Schloss |
5710918 | January 20, 1998 | Lagarde et al. |
5713019 | January 27, 1998 | Keaten |
5715403 | February 3, 1998 | Stefik |
5717925 | February 10, 1998 | Harper |
5721908 | February 24, 1998 | Lagarde et al. |
5721914 | February 24, 1998 | DeVries |
5727202 | March 10, 1998 | Kucala |
5729549 | March 17, 1998 | Kostreski et al. |
5729704 | March 17, 1998 | Stone et al. |
5729735 | March 17, 1998 | Meyering |
5742905 | April 21, 1998 | Pepe et al. |
5745360 | April 28, 1998 | Leone et al. |
5752186 | May 12, 1998 | Malackowski et al. |
5752246 | May 12, 1998 | Rogers et al. |
5754938 | May 19, 1998 | Herz et al. |
5757916 | May 26, 1998 | MacDoran et al. |
5758088 | May 26, 1998 | Bezaire et al. |
5758150 | May 26, 1998 | Bell et al. |
5758322 | May 26, 1998 | Rongley |
5758354 | May 26, 1998 | Huang et al. |
5758355 | May 26, 1998 | Buchanan |
5765171 | June 9, 1998 | Gehani et al. |
5778346 | July 7, 1998 | Frid-Neilsen et al. |
5778361 | July 7, 1998 | Nanjo et al. |
5781614 | July 14, 1998 | Brunson |
5781901 | July 14, 1998 | Kuzma |
5781906 | July 14, 1998 | Aggarwal et al. |
5787430 | July 28, 1998 | Doeringer et al. |
5787441 | July 28, 1998 | Beckhardt |
5790425 | August 4, 1998 | Wagle |
5790790 | August 4, 1998 | Smith et al. |
5790974 | August 4, 1998 | Tognazzini |
5793413 | August 11, 1998 | Hylton et al. |
5794210 | August 11, 1998 | Goldhaber et al. |
5799318 | August 25, 1998 | Cardinal et al. |
5802312 | September 1, 1998 | Lazaridis et al. |
5802454 | September 1, 1998 | Goshay et al. |
5802518 | September 1, 1998 | Karaev et al. |
5802524 | September 1, 1998 | Flowers et al. |
5806074 | September 8, 1998 | Souder et al. |
5809242 | September 15, 1998 | Shaw et al. |
5809415 | September 15, 1998 | Rossmann |
5818437 | October 6, 1998 | Grover et al. |
5819172 | October 6, 1998 | Campana, Jr. et al. |
5819274 | October 6, 1998 | Jackson, Jr. |
5819284 | October 6, 1998 | Farber et al. |
5822324 | October 13, 1998 | Kostresti et al. |
5822747 | October 13, 1998 | Graefe et al. |
5826269 | October 20, 1998 | Hussey |
5831664 | November 3, 1998 | Wharton et al. |
5832483 | November 3, 1998 | Barker |
5832489 | November 3, 1998 | Kucala |
5832500 | November 3, 1998 | Burrows |
5835087 | November 10, 1998 | Herz et al. |
5835722 | November 10, 1998 | Bradshaw et al. |
5838252 | November 17, 1998 | Kikinis |
5838768 | November 17, 1998 | Sumar et al. |
5838973 | November 17, 1998 | Carpenter-Smith et al. |
5845278 | December 1, 1998 | Kirsch et al. |
5852775 | December 22, 1998 | Hidary |
5852820 | December 22, 1998 | Burrows |
5857201 | January 5, 1999 | Wright, Jr. et al. |
5862223 | January 19, 1999 | Walker et al. |
5867665 | February 2, 1999 | Butman et al. |
5867817 | February 2, 1999 | Catallo et al. |
5870759 | February 9, 1999 | Bauer et al. |
5884323 | March 16, 1999 | Hawkins et al. |
5889845 | March 30, 1999 | Staples et al. |
5890147 | March 30, 1999 | Peltonen et al. |
5892909 | April 6, 1999 | Grasso et al. |
5898780 | April 27, 1999 | Liu et al. |
5898917 | April 27, 1999 | Batni et al. |
5903723 | May 11, 1999 | Beck et al. |
5907618 | May 25, 1999 | Gennaro et al. |
5909689 | June 1, 1999 | Van Ryzin |
5913032 | June 15, 1999 | Schwartz et al. |
5924096 | July 13, 1999 | Draper et al. |
5928325 | July 27, 1999 | Shaughnessy et al. |
5928329 | July 27, 1999 | Clark et al. |
5937161 | August 10, 1999 | Mulligan et al. |
5940813 | August 17, 1999 | Hutchings |
5943676 | August 24, 1999 | Boothby |
5948066 | September 7, 1999 | Whalen et al. |
5951636 | September 14, 1999 | Zerber |
5960394 | September 28, 1999 | Gould et al. |
5960406 | September 28, 1999 | Rasansky et al. |
5961590 | October 5, 1999 | Mendez et al. |
5963642 | October 5, 1999 | Goldstein |
5964833 | October 12, 1999 | Kikinis |
5968131 | October 19, 1999 | Mendez et al. |
5974238 | October 26, 1999 | Chase, Jr. |
5974327 | October 26, 1999 | Agrawal et al. |
5978837 | November 2, 1999 | Foladare et al. |
5978933 | November 2, 1999 | Wyld et al. |
5987440 | November 16, 1999 | O'Neil et al. |
6000000 | December 7, 1999 | Hawkins et al. |
6003070 | December 14, 1999 | Frantz |
6006274 | December 21, 1999 | Hawkins et al. |
6016478 | January 18, 2000 | Zhang et al. |
6016520 | January 18, 2000 | Facq et al. |
6018762 | January 25, 2000 | Brunson et al. |
6023700 | February 8, 2000 | Owens et al. |
6023708 | February 8, 2000 | Mendez et al. |
6029238 | February 22, 2000 | Furukawa |
6034621 | March 7, 2000 | Kaufman |
6035104 | March 7, 2000 | Zahariev |
6044372 | March 28, 2000 | Rothfus et al. |
6044381 | March 28, 2000 | Mendez et al. |
6047051 | April 4, 2000 | Ginzboorog et al. |
6047327 | April 4, 2000 | Tso et al. |
6052563 | April 18, 2000 | Macko |
6052735 | April 18, 2000 | Ulrich et al. |
6057855 | May 2, 2000 | Barkans |
6065055 | May 16, 2000 | Hughes et al. |
6073138 | June 6, 2000 | de l'Etraz et al. |
6073142 | June 6, 2000 | Geiger et al. |
6073165 | June 6, 2000 | Narasimhan et al. |
6085166 | July 4, 2000 | Beckhardt et al. |
6085192 | July 4, 2000 | Mendez et al. |
6088677 | July 11, 2000 | Spurgeon |
6101320 | August 8, 2000 | Schuetze et al. |
6101480 | August 8, 2000 | Conmy et al. |
6101531 | August 8, 2000 | Eggleston et al. |
6112181 | August 29, 2000 | Shear et al. |
6119014 | September 12, 2000 | Alperovich et al. |
6119171 | September 12, 2000 | Alkhatib |
6125369 | September 26, 2000 | Wu et al. |
6125388 | September 26, 2000 | Reisman |
6128627 | October 3, 2000 | Mattis et al. |
6130898 | October 10, 2000 | Kostreski et al. |
6131096 | October 10, 2000 | Ng et al. |
6131116 | October 10, 2000 | Riggins et al. |
6134432 | October 17, 2000 | Holmes et al. |
6138013 | October 24, 2000 | Blanchard et al. |
6138124 | October 24, 2000 | Beckhardt |
6138128 | October 24, 2000 | Perkowitz et al. |
6138146 | October 24, 2000 | Moon et al. |
6141664 | October 31, 2000 | Boothby |
6151606 | November 21, 2000 | Mendez |
6157630 | December 5, 2000 | Adler et al. |
6161140 | December 12, 2000 | Moriya |
6167379 | December 26, 2000 | Dean et al. |
6167435 | December 26, 2000 | Druckenmiller et al. |
6170014 | January 2, 2001 | Darago et al. |
6173312 | January 9, 2001 | Atarashi et al. |
6173446 | January 9, 2001 | Khan et al. |
6175831 | January 16, 2001 | Weinreich et al. |
6178419 | January 23, 2001 | Legh-Smith et al. |
6181935 | January 30, 2001 | Gossman et al. |
6185184 | February 6, 2001 | Mattaway et al. |
6195533 | February 27, 2001 | Tkatch et al. |
6198696 | March 6, 2001 | Korpi et al. |
6198922 | March 6, 2001 | Baynham |
6201469 | March 13, 2001 | Balch et al. |
6202085 | March 13, 2001 | Benson et al. |
6205448 | March 20, 2001 | Kruglikov et al. |
6212529 | April 3, 2001 | Boothby et al. |
6219694 | April 17, 2001 | Lazaridis et al. |
6221877 | April 24, 2001 | Aronov et al. |
6223187 | April 24, 2001 | Boothby et al. |
6226686 | May 1, 2001 | Rothschild et al. |
6233341 | May 15, 2001 | Riggins |
6243705 | June 5, 2001 | Kucala |
6246875 | June 12, 2001 | Seazholtz et al. |
6247135 | June 12, 2001 | Feague |
6249808 | June 19, 2001 | Seshadri |
6256666 | July 3, 2001 | Singhal |
6263201 | July 17, 2001 | Hashimoto et al. |
6263340 | July 17, 2001 | Green |
6269369 | July 31, 2001 | Robertson |
6272545 | August 7, 2001 | Flanagin et al. |
6275850 | August 14, 2001 | Beyda et al. |
6275858 | August 14, 2001 | Bates et al. |
6286099 | September 4, 2001 | Kramer |
6289212 | September 11, 2001 | Stein et al. |
6289214 | September 11, 2001 | Backstrom |
6292904 | September 18, 2001 | Broomhall et al. |
6295541 | September 25, 2001 | Bodnar et al. |
6300947 | October 9, 2001 | Kanevsky |
6304881 | October 16, 2001 | Halim et al. |
6308201 | October 23, 2001 | Pivowar et al. |
6317594 | November 13, 2001 | Grossman et al. |
6320943 | November 20, 2001 | Borland |
6324541 | November 27, 2001 | de l'Etraz et al. |
6324542 | November 27, 2001 | Wright, Jr. et al. |
6324544 | November 27, 2001 | Alam et al. |
6324587 | November 27, 2001 | Trenbeath et al. |
6327586 | December 4, 2001 | Kisiel |
6336117 | January 1, 2002 | Massarani |
6336138 | January 1, 2002 | Caswell et al. |
6351767 | February 26, 2002 | Batchelder et al. |
6356937 | March 12, 2002 | Montville et al. |
6363051 | March 26, 2002 | Eslambolchi et al. |
6363352 | March 26, 2002 | Dailey et al. |
6370566 | April 9, 2002 | Discolo et al. |
6377810 | April 23, 2002 | Geiger et al. |
6380959 | April 30, 2002 | Wang et al. |
6389422 | May 14, 2002 | Doi et al. |
6389455 | May 14, 2002 | Fuisz |
6389457 | May 14, 2002 | Lazaridis et al. |
6397057 | May 28, 2002 | Malackowski et al. |
6397230 | May 28, 2002 | Carmel et al. |
6401104 | June 4, 2002 | LaRue et al. |
6401112 | June 4, 2002 | Boyer et al. |
6401113 | June 4, 2002 | Lazaridis et al. |
6405197 | June 11, 2002 | Gilmour |
6411696 | June 25, 2002 | Iverson et al. |
6415031 | July 2, 2002 | Colligan et al. |
6418308 | July 9, 2002 | Heinonen et al. |
6421669 | July 16, 2002 | Gilmour et al. |
6421781 | July 16, 2002 | Fox et al. |
6430602 | August 6, 2002 | Kay et al. |
6438585 | August 20, 2002 | Mousseau et al. |
6438612 | August 20, 2002 | Ylonen et al. |
6442589 | August 27, 2002 | Takahashi et al. |
6442637 | August 27, 2002 | Hawkins et al. |
6446118 | September 3, 2002 | Gottlieb |
6463463 | October 8, 2002 | Godfrey et al. |
6463464 | October 8, 2002 | Lazaridis et al. |
6487557 | November 26, 2002 | Nagatomo |
6487560 | November 26, 2002 | LaRue et al. |
6490353 | December 3, 2002 | Tan |
6496802 | December 17, 2002 | van Zoest et al. |
6499054 | December 24, 2002 | Hesselink et al. |
6505214 | January 7, 2003 | Sherman et al. |
6516327 | February 4, 2003 | Zondervan et al. |
6526433 | February 25, 2003 | Chang et al. |
6526506 | February 25, 2003 | Lewis |
6529908 | March 4, 2003 | Piett et al. |
6532446 | March 11, 2003 | King |
6535892 | March 18, 2003 | LaRue et al. |
6546005 | April 8, 2003 | Berkley et al. |
6549939 | April 15, 2003 | Ford et al. |
6556217 | April 29, 2003 | Mäkipää et al. |
6593944 | July 15, 2003 | Nicolas et al. |
6601026 | July 29, 2003 | Appelt et al. |
6615253 | September 2, 2003 | Bowman-Amuah |
6618710 | September 9, 2003 | Zondervan et al. |
6621892 | September 16, 2003 | Banister et al. |
6625621 | September 23, 2003 | Tan et al. |
6636482 | October 21, 2003 | Cloonan et al. |
6639693 | October 28, 2003 | Ejiri et al. |
6640097 | October 28, 2003 | Corrigan et al. |
6640244 | October 28, 2003 | Bowman-Amuah |
6640249 | October 28, 2003 | Bowman-Amuah |
6643650 | November 4, 2003 | Slaughter et al. |
6643688 | November 4, 2003 | Fuisz |
6647384 | November 11, 2003 | Gilmour |
6650890 | November 18, 2003 | Irlam et al. |
6662016 | December 9, 2003 | Buckham et al. |
6668046 | December 23, 2003 | Albal |
6671695 | December 30, 2003 | McFadden |
6671700 | December 30, 2003 | Creemer et al. |
6671702 | December 30, 2003 | Kruglikov et al. |
6671757 | December 30, 2003 | Multer et al. |
6694336 | February 17, 2004 | Multer et al. |
6697807 | February 24, 2004 | McGeachie |
6701378 | March 2, 2004 | Gilhuly et al. |
6707801 | March 16, 2004 | Hsu |
6708221 | March 16, 2004 | Mendez et al. |
6714965 | March 30, 2004 | Kakuta et al. |
6721787 | April 13, 2004 | Hiscock |
6727917 | April 27, 2004 | Chew et al. |
6728530 | April 27, 2004 | Heinonen et al. |
6728786 | April 27, 2004 | Hawkins et al. |
6732101 | May 4, 2004 | Cook |
6732158 | May 4, 2004 | Hesselink et al. |
6735591 | May 11, 2004 | Khan |
6741232 | May 25, 2004 | Siedlikowski et al. |
6741855 | May 25, 2004 | Martin et al. |
6742015 | May 25, 2004 | Bowman-Amuah |
6742059 | May 25, 2004 | Todd et al. |
6745024 | June 1, 2004 | DeJaco et al. |
6745326 | June 1, 2004 | Wary |
6756882 | June 29, 2004 | Benes et al. |
6757362 | June 29, 2004 | Cooper et al. |
6757696 | June 29, 2004 | Multer et al. |
6757708 | June 29, 2004 | Craig et al. |
6760916 | July 6, 2004 | Holtz et al. |
6771294 | August 3, 2004 | Pulli et al. |
6775362 | August 10, 2004 | Ransom |
6779019 | August 17, 2004 | Mousseau et al. |
6782409 | August 24, 2004 | Yoshida |
6785868 | August 31, 2004 | Raff |
6785906 | August 31, 2004 | Gaughan et al. |
6799190 | September 28, 2004 | Boothby |
6804707 | October 12, 2004 | Ronning |
6816849 | November 9, 2004 | Halt, Jr. |
6820088 | November 16, 2004 | Hind et al. |
6820204 | November 16, 2004 | Desai et al. |
6829487 | December 7, 2004 | Eiden et al. |
6834195 | December 21, 2004 | Brandenberg et al. |
6847974 | January 25, 2005 | Wachtel |
6850757 | February 1, 2005 | Watanabe et al. |
6859212 | February 22, 2005 | Kumar et al. |
6859440 | February 22, 2005 | Sonti et al. |
6867774 | March 15, 2005 | Halmshaw et al. |
6868447 | March 15, 2005 | Slaughter et al. |
6871220 | March 22, 2005 | Rajan et al. |
6871236 | March 22, 2005 | Fishman et al. |
6873688 | March 29, 2005 | Aarnio |
6874017 | March 29, 2005 | Inoue et al. |
6879985 | April 12, 2005 | Deguchi et al. |
6886030 | April 26, 2005 | Easterbrook et al. |
6892070 | May 10, 2005 | Warrier et al. |
6892196 | May 10, 2005 | Hughes |
6895394 | May 17, 2005 | Kremer et al. |
6895558 | May 17, 2005 | Loveland |
6898427 | May 24, 2005 | Griffith et al. |
6922547 | July 26, 2005 | O'Neill et al. |
6922721 | July 26, 2005 | Minborg et al. |
6925477 | August 2, 2005 | Champagne et al. |
6931529 | August 16, 2005 | Kunzinger |
6938079 | August 30, 2005 | Anderson et al. |
6944447 | September 13, 2005 | Portman et al. |
6944662 | September 13, 2005 | Devine et al. |
6947770 | September 20, 2005 | Rydbeck |
6950862 | September 27, 2005 | Puthiyandyil et al. |
6957397 | October 18, 2005 | Hawkins et al. |
6965917 | November 15, 2005 | Aloni et al. |
6966058 | November 15, 2005 | Earl et al. |
6968175 | November 22, 2005 | Raivisto et al. |
6970879 | November 29, 2005 | Gilmour |
6972682 | December 6, 2005 | Lareau et al. |
6973299 | December 6, 2005 | Apfel |
6981041 | December 27, 2005 | Araujo et al. |
6981047 | December 27, 2005 | Hanson et al. |
6985933 | January 10, 2006 | Singhal et al. |
6985983 | January 10, 2006 | Pellegrino et al. |
6986061 | January 10, 2006 | Kunzinger |
6987734 | January 17, 2006 | Hundemer |
6990472 | January 24, 2006 | Rosenhaft et al. |
6993326 | January 31, 2006 | Link, II et al. |
6993327 | January 31, 2006 | Mathis |
6996627 | February 7, 2006 | Carden |
6999753 | February 14, 2006 | Beckmann et al. |
7020685 | March 28, 2006 | Chen et al. |
7024491 | April 4, 2006 | Hanmann et al. |
7026984 | April 11, 2006 | Thandu et al. |
7032242 | April 18, 2006 | Grabelsky et al. |
7035630 | April 25, 2006 | Knowles |
7046993 | May 16, 2006 | Haaramo et al. |
7047202 | May 16, 2006 | Jaipuria et al. |
7062024 | June 13, 2006 | Kreckel et al. |
7069308 | June 27, 2006 | Abrams |
7072678 | July 4, 2006 | Allison |
7079499 | July 18, 2006 | Akhtar et al. |
7080371 | July 18, 2006 | Arnaiz et al. |
7082316 | July 25, 2006 | Eiden et al. |
7085365 | August 1, 2006 | Kauppinen |
7096030 | August 22, 2006 | Huomo |
7100821 | September 5, 2006 | Rasti |
7103432 | September 5, 2006 | Drader et al. |
7120692 | October 10, 2006 | Hesselink et al. |
7120928 | October 10, 2006 | Sheth et al. |
7130839 | October 31, 2006 | Boreham et al. |
7136645 | November 14, 2006 | Hanson et al. |
7139555 | November 21, 2006 | Apfel |
7139565 | November 21, 2006 | Fiatal et al. |
7140549 | November 28, 2006 | de Jong |
7146645 | December 5, 2006 | Hellsten et al. |
7149780 | December 12, 2006 | Quine et al. |
7149789 | December 12, 2006 | Slivka et al. |
7149959 | December 12, 2006 | Jones et al. |
7162241 | January 9, 2007 | Kim et al. |
7165727 | January 23, 2007 | de Jong |
7172118 | February 6, 2007 | Urken |
7181228 | February 20, 2007 | Boesch |
7184790 | February 27, 2007 | Dorenbosch et al. |
7185362 | February 27, 2007 | Hawkes et al. |
7194273 | March 20, 2007 | Vaudreuil |
7200390 | April 3, 2007 | Henager et al. |
7203733 | April 10, 2007 | Bern |
7206806 | April 17, 2007 | Pineau |
7209757 | April 24, 2007 | Naghian et al. |
7210121 | April 24, 2007 | Xia et al. |
7219139 | May 15, 2007 | Martin et al. |
7219222 | May 15, 2007 | Durbin et al. |
7224957 | May 29, 2007 | Spector |
7231206 | June 12, 2007 | Cudak et al. |
7233795 | June 19, 2007 | Ryden |
7234111 | June 19, 2007 | Chu et al. |
7239877 | July 3, 2007 | Corneille et al. |
7240095 | July 3, 2007 | Lewis |
7242680 | July 10, 2007 | Gallant |
7245926 | July 17, 2007 | Liao et al. |
7257391 | August 14, 2007 | Burgess et al. |
7257639 | August 14, 2007 | Li et al. |
7259666 | August 21, 2007 | Hermsmeyer et al. |
7260552 | August 21, 2007 | Riera Jorba et al. |
7260590 | August 21, 2007 | Williams |
7260651 | August 21, 2007 | Parrella, Sr. et al. |
7272830 | September 18, 2007 | de Jong |
7277408 | October 2, 2007 | Sorsa |
7284664 | October 23, 2007 | Ivchenko et al. |
7289792 | October 30, 2007 | Turunen |
7289964 | October 30, 2007 | Bowman-Amuah |
7289971 | October 30, 2007 | O'Neil et al. |
7293107 | November 6, 2007 | Hanson et al. |
7295853 | November 13, 2007 | Jin et al. |
7296155 | November 13, 2007 | Trostle et al. |
7305252 | December 4, 2007 | Britt et al. |
7305700 | December 4, 2007 | Boynton et al. |
7310350 | December 18, 2007 | Shao et al. |
7310729 | December 18, 2007 | Gordon et al. |
7324473 | January 29, 2008 | Corneille et al. |
7349871 | March 25, 2008 | Labrou et al. |
7353274 | April 1, 2008 | Rouhi et al. |
7359720 | April 15, 2008 | Hartmaier et al. |
7373386 | May 13, 2008 | Gardner et al. |
7374099 | May 20, 2008 | de Jong |
7376701 | May 20, 2008 | Bhargava et al. |
7382879 | June 3, 2008 | Miller |
7388950 | June 17, 2008 | Elsey et al. |
7389412 | June 17, 2008 | Sharma et al. |
7392483 | June 24, 2008 | Wong et al. |
7395329 | July 1, 2008 | Holt et al. |
7398271 | July 8, 2008 | Borkovsky et al. |
7430609 | September 30, 2008 | Brown et al. |
7441271 | October 21, 2008 | Fiatal et al. |
7443847 | October 28, 2008 | Albert et al. |
7461071 | December 2, 2008 | Fitzpatrick et al. |
7465231 | December 16, 2008 | Lewin et al. |
7469125 | December 23, 2008 | Nurmi |
7483036 | January 27, 2009 | Moore |
7499537 | March 3, 2009 | Elsey et al. |
7502615 | March 10, 2009 | Wilhoite et al. |
7519042 | April 14, 2009 | Gorday et al. |
7532571 | May 12, 2009 | Price et al. |
7539665 | May 26, 2009 | Mendez |
7539728 | May 26, 2009 | Perepa et al. |
7548947 | June 16, 2009 | Karsriel et al. |
7548969 | June 16, 2009 | Tripp et al. |
7551900 | June 23, 2009 | Kang et al. |
7567575 | July 28, 2009 | Chen et al. |
7574208 | August 11, 2009 | Hanson et al. |
7575171 | August 18, 2009 | Lev |
7584294 | September 1, 2009 | Plamondon |
7587482 | September 8, 2009 | Henderson et al. |
7587608 | September 8, 2009 | Haller et al. |
7593714 | September 22, 2009 | Schultz et al. |
7596608 | September 29, 2009 | Alexander et al. |
7596791 | September 29, 2009 | Wei et al. |
7613792 | November 3, 2009 | Zervas et al. |
7630986 | December 8, 2009 | Herz et al. |
7634558 | December 15, 2009 | Mangal et al. |
7643818 | January 5, 2010 | Backholm et al. |
7644166 | January 5, 2010 | Appelman et al. |
7650416 | January 19, 2010 | Wu et al. |
7672291 | March 2, 2010 | Wang |
7672439 | March 2, 2010 | Appelman et al. |
7680281 | March 16, 2010 | Fiatal et al. |
7684346 | March 23, 2010 | Valli |
7689664 | March 30, 2010 | Karlberg |
7693555 | April 6, 2010 | Srinivasan et al. |
7693944 | April 6, 2010 | Appelman et al. |
7694008 | April 6, 2010 | Chang et al. |
7706781 | April 27, 2010 | Backholm et al. |
7707573 | April 27, 2010 | Marmaros et al. |
7752633 | July 6, 2010 | Fleming |
7757956 | July 20, 2010 | Koenck et al. |
7769395 | August 3, 2010 | Fiatal et al. |
7769400 | August 3, 2010 | Backholm et al. |
7769805 | August 3, 2010 | Barnes et al. |
7778792 | August 17, 2010 | Huang et al. |
7783757 | August 24, 2010 | Plamondon |
7796742 | September 14, 2010 | Sutaria et al. |
7797064 | September 14, 2010 | Loomis et al. |
7809818 | October 5, 2010 | Plamondon |
7827055 | November 2, 2010 | Snodgrass et al. |
7827597 | November 2, 2010 | Boynton et al. |
7853563 | December 14, 2010 | Alvarado et al. |
7877703 | January 25, 2011 | Fleming |
7881745 | February 1, 2011 | Rao et al. |
7899996 | March 1, 2011 | Levin-Michael |
7908656 | March 15, 2011 | Mu |
7917468 | March 29, 2011 | Ariel et al. |
7917505 | March 29, 2011 | van Gent et al. |
7921167 | April 5, 2011 | Shroff et al. |
7930416 | April 19, 2011 | Miller et al. |
7933929 | April 26, 2011 | McClendon et al. |
7937091 | May 3, 2011 | Roman et al. |
7970860 | June 28, 2011 | Kline et al. |
7996487 | August 9, 2011 | Snyder |
8005891 | August 23, 2011 | Knowles et al. |
8010082 | August 30, 2011 | Sutaria et al. |
8032409 | October 4, 2011 | Mikurak |
8064583 | November 22, 2011 | Sutaria et al. |
8069166 | November 29, 2011 | Alvarado et al. |
8078158 | December 13, 2011 | Backholm |
8107921 | January 31, 2012 | Fiatal |
8116214 | February 14, 2012 | Backholm et al. |
8127342 | February 28, 2012 | Boynton et al. |
8166164 | April 24, 2012 | Luna et al. |
8190701 | May 29, 2012 | Luna et al. |
8194680 | June 5, 2012 | Brandwine et al. |
8204953 | June 19, 2012 | Luna et al. |
8209709 | June 26, 2012 | Fleming |
8260852 | September 4, 2012 | Cselle |
8549587 | October 1, 2013 | Boynton et al. |
20010009025 | July 19, 2001 | Ahonen |
20010010046 | July 26, 2001 | Muyres et al. |
20010013069 | August 9, 2001 | Shah |
20010023414 | September 20, 2001 | Kumar et al. |
20010029524 | October 11, 2001 | Smith et al. |
20010032254 | October 18, 2001 | Hawkins et al. |
20010034225 | October 25, 2001 | Gupte et al. |
20010034244 | October 25, 2001 | Calder et al. |
20010037453 | November 1, 2001 | Mitty et al. |
20010039191 | November 8, 2001 | Maierhofer |
20010041566 | November 15, 2001 | Xanthos et al. |
20010042009 | November 15, 2001 | Montague |
20010042099 | November 15, 2001 | Peng |
20010043148 | November 22, 2001 | Stewart |
20010052052 | December 13, 2001 | Peng |
20010053687 | December 20, 2001 | Sivula |
20020002478 | January 3, 2002 | Swart et al. |
20020002591 | January 3, 2002 | Ketola |
20020007303 | January 17, 2002 | Brookler et al. |
20020013727 | January 31, 2002 | Lee |
20020019225 | February 14, 2002 | Miyashita |
20020019812 | February 14, 2002 | Board et al. |
20020035556 | March 21, 2002 | Shah et al. |
20020035617 | March 21, 2002 | Lynch et al. |
20020038253 | March 28, 2002 | Seaman et al. |
20020042875 | April 11, 2002 | Shukla |
20020049818 | April 25, 2002 | Gilhuly et al. |
20020049828 | April 25, 2002 | Pekarek-Kostka |
20020053078 | May 2, 2002 | Holtz et al. |
20020055351 | May 9, 2002 | Elsey et al. |
20020059201 | May 16, 2002 | Work |
20020059457 | May 16, 2002 | Ballard et al. |
20020068559 | June 6, 2002 | Sharma et al. |
20020073207 | June 13, 2002 | Widger et al. |
20020077077 | June 20, 2002 | Rezvani et al. |
20020077084 | June 20, 2002 | Zellner et al. |
20020078384 | June 20, 2002 | Hippelainen |
20020087549 | July 4, 2002 | Mostafa |
20020087679 | July 4, 2002 | Pulley et al. |
20020087883 | July 4, 2002 | Wohlgemuth et al. |
20020089542 | July 11, 2002 | Imamura |
20020091921 | July 11, 2002 | Kunzinger |
20020095319 | July 18, 2002 | Swart et al. |
20020095328 | July 18, 2002 | Swart et al. |
20020095391 | July 18, 2002 | Swart et al. |
20020095399 | July 18, 2002 | Devine et al. |
20020098855 | July 25, 2002 | Hartmaier et al. |
20020099613 | July 25, 2002 | Swart et al. |
20020099809 | July 25, 2002 | Lee |
20020101975 | August 1, 2002 | Tiburtius et al. |
20020103934 | August 1, 2002 | Fishman et al. |
20020107944 | August 8, 2002 | Bai et al. |
20020107985 | August 8, 2002 | Hwang et al. |
20020116499 | August 22, 2002 | Ennus et al. |
20020116501 | August 22, 2002 | Ho et al. |
20020120388 | August 29, 2002 | Bullock |
20020120766 | August 29, 2002 | Okajima et al. |
20020120779 | August 29, 2002 | Teeple et al. |
20020126701 | September 12, 2002 | Requena |
20020133504 | September 19, 2002 | Vlahos et al. |
20020144109 | October 3, 2002 | Benantar et al. |
20020146129 | October 10, 2002 | Kaplan |
20020152379 | October 17, 2002 | Gefwert et al. |
20020155848 | October 24, 2002 | Suryanarayana |
20020156839 | October 24, 2002 | Peterson et al. |
20020158908 | October 31, 2002 | Vaajala et al. |
20020161587 | October 31, 2002 | Pitts, III et al. |
20020161925 | October 31, 2002 | Munger et al. |
20020161928 | October 31, 2002 | Ndili |
20020164977 | November 7, 2002 | Link, II et al. |
20020167484 | November 14, 2002 | Hatanaka et al. |
20020174189 | November 21, 2002 | Peng |
20020186848 | December 12, 2002 | Shaik |
20020188940 | December 12, 2002 | Breckner et al. |
20020193094 | December 19, 2002 | Lawless et al. |
20020194209 | December 19, 2002 | Bolosky et al. |
20020198027 | December 26, 2002 | Rydbeck |
20030005151 | January 2, 2003 | Ullman et al. |
20030014491 | January 16, 2003 | Horvitz et al. |
20030022662 | January 30, 2003 | Mittal |
20030023692 | January 30, 2003 | Moroo |
20030023975 | January 30, 2003 | Schrader et al. |
20030028430 | February 6, 2003 | Zimmerman |
20030028441 | February 6, 2003 | Barsness et al. |
20030046433 | March 6, 2003 | Luzzatti et al. |
20030046586 | March 6, 2003 | Bheemarasetti et al. |
20030046587 | March 6, 2003 | Bheemarasetti et al. |
20030050041 | March 13, 2003 | Wu |
20030054810 | March 20, 2003 | Chen et al. |
20030056096 | March 20, 2003 | Albert et al. |
20030060188 | March 27, 2003 | Gidron et al. |
20030063120 | April 3, 2003 | Wong et al. |
20030065738 | April 3, 2003 | Yang et al. |
20030065739 | April 3, 2003 | Shnier |
20030065802 | April 3, 2003 | Vitikainen et al. |
20030070061 | April 10, 2003 | Wong et al. |
20030072451 | April 17, 2003 | Pimentel et al. |
20030078880 | April 24, 2003 | Alley et al. |
20030084165 | May 1, 2003 | Kjellberg et al. |
20030088629 | May 8, 2003 | Berkowitz et al. |
20030093691 | May 15, 2003 | Simon et al. |
20030097381 | May 22, 2003 | Detweiler et al. |
20030100321 | May 29, 2003 | Rao et al. |
20030100326 | May 29, 2003 | Grube et al. |
20030117432 | June 26, 2003 | Kautto-Kiovula et al. |
20030120685 | June 26, 2003 | Duncombe et al. |
20030125023 | July 3, 2003 | Fishler |
20030126216 | July 3, 2003 | Avila et al. |
20030130984 | July 10, 2003 | Quinlan et al. |
20030145038 | July 31, 2003 | Bin Tariq et al. |
20030146934 | August 7, 2003 | Bailey et al. |
20030153338 | August 14, 2003 | Herz et al. |
20030154212 | August 14, 2003 | Schirmer et al. |
20030156146 | August 21, 2003 | Suomela et al. |
20030157947 | August 21, 2003 | Fiatal et al. |
20030169262 | September 11, 2003 | Lavelle et al. |
20030177281 | September 18, 2003 | McQuillan et al. |
20030182431 | September 25, 2003 | Sturniolo et al. |
20030187984 | October 2, 2003 | Banavar et al. |
20030204605 | October 30, 2003 | Hudson et al. |
20030208529 | November 6, 2003 | Pendyala et al. |
20030208559 | November 6, 2003 | Velline et al. |
20030210666 | November 13, 2003 | Trossen et al. |
20030211845 | November 13, 2003 | Lohtia et al. |
20030217098 | November 20, 2003 | Bobde et al. |
20030217142 | November 20, 2003 | Bobde et al. |
20030223554 | December 4, 2003 | Zhang |
20030227487 | December 11, 2003 | Hugh |
20030227745 | December 11, 2003 | Khoo |
20030235308 | December 25, 2003 | Boynton et al. |
20030236857 | December 25, 2003 | Takase et al. |
20030236981 | December 25, 2003 | Marmigere et al. |
20040002324 | January 1, 2004 | Juntunen et al. |
20040006630 | January 8, 2004 | Friend et al. |
20040015504 | January 22, 2004 | Ahad et al. |
20040024795 | February 5, 2004 | Hind et al. |
20040024824 | February 5, 2004 | Ferguson et al. |
20040024892 | February 5, 2004 | Creswell et al. |
20040027326 | February 12, 2004 | Hays et al. |
20040027375 | February 12, 2004 | Ellis et al. |
20040027378 | February 12, 2004 | Hays et al. |
20040043770 | March 4, 2004 | Amit et al. |
20040049579 | March 11, 2004 | Ims et al. |
20040049599 | March 11, 2004 | Friend et al. |
20040051715 | March 18, 2004 | Brokenshire et al. |
20040054719 | March 18, 2004 | Daigle et al. |
20040054739 | March 18, 2004 | Friend et al. |
20040064445 | April 1, 2004 | Pfleging et al. |
20040064488 | April 1, 2004 | Sinha |
20040068579 | April 8, 2004 | Marmigere et al. |
20040068698 | April 8, 2004 | Wu et al. |
20040073476 | April 15, 2004 | Donahue et al. |
20040073651 | April 15, 2004 | Beaulieu et al. |
20040075675 | April 22, 2004 | Raivisto et al. |
20040075695 | April 22, 2004 | Chew et al. |
20040078814 | April 22, 2004 | Allen |
20040080515 | April 29, 2004 | Hagiwara |
20040082346 | April 29, 2004 | Skytt et al. |
20040098625 | May 20, 2004 | Lagadec et al. |
20040103147 | May 27, 2004 | Flesher et al. |
20040107319 | June 3, 2004 | D'Orto et al. |
20040110497 | June 10, 2004 | Little |
20040120323 | June 24, 2004 | Viikari et al. |
20040123095 | June 24, 2004 | Marshall |
20040123304 | June 24, 2004 | Black et al. |
20040127214 | July 1, 2004 | Reddy et al. |
20040128375 | July 1, 2004 | Rockwell |
20040133626 | July 8, 2004 | Herrero et al. |
20040141011 | July 22, 2004 | Smethers et al. |
20040147248 | July 29, 2004 | Will |
20040147262 | July 29, 2004 | Lescuyer et al. |
20040148375 | July 29, 2004 | Levett et al. |
20040158611 | August 12, 2004 | Daniell et al. |
20040167966 | August 26, 2004 | Lee et al. |
20040170257 | September 2, 2004 | Gross et al. |
20040172481 | September 2, 2004 | Engstrom |
20040176128 | September 9, 2004 | Grabelsky et al. |
20040177369 | September 9, 2004 | Akins, III |
20040179513 | September 16, 2004 | Smith et al. |
20040181550 | September 16, 2004 | Warsta et al. |
20040184475 | September 23, 2004 | Meier |
20040186902 | September 23, 2004 | Stewart |
20040189610 | September 30, 2004 | Friend |
20040199497 | October 7, 2004 | Timmons |
20040199582 | October 7, 2004 | Kucharewski et al. |
20040199663 | October 7, 2004 | Horvitz et al. |
20040205248 | October 14, 2004 | Little et al. |
20040205330 | October 14, 2004 | Godfrey et al. |
20040209602 | October 21, 2004 | Joyce et al. |
20040210639 | October 21, 2004 | Ben-Yoseph et al. |
20040219940 | November 4, 2004 | Kong et al. |
20040230619 | November 18, 2004 | Blanco et al. |
20040233930 | November 25, 2004 | Colby, Jr. |
20040236792 | November 25, 2004 | Celik |
20040242209 | December 2, 2004 | Kruis et al. |
20040252816 | December 16, 2004 | Nicolas |
20040255126 | December 16, 2004 | Reith |
20040258231 | December 23, 2004 | Elsey et al. |
20040259535 | December 23, 2004 | Elsey et al. |
20040259537 | December 23, 2004 | Ackley |
20040260948 | December 23, 2004 | Miyata et al. |
20040264396 | December 30, 2004 | Ginzburg et al. |
20040266364 | December 30, 2004 | Nguyen et al. |
20040268148 | December 30, 2004 | Karjala et al. |
20050002501 | January 6, 2005 | Elsey et al. |
20050002508 | January 6, 2005 | Elsey et al. |
20050002509 | January 6, 2005 | Elsey et al. |
20050002510 | January 6, 2005 | Elsey et al. |
20050010694 | January 13, 2005 | Ma et al. |
20050015432 | January 20, 2005 | Cohen |
20050021750 | January 27, 2005 | Abrams |
20050022000 | January 27, 2005 | Inomata et al. |
20050022182 | January 27, 2005 | Mittal |
20050027591 | February 3, 2005 | Gailey et al. |
20050027716 | February 3, 2005 | Apfel |
20050027869 | February 3, 2005 | Johnson |
20050033812 | February 10, 2005 | McCarthy et al. |
20050033926 | February 10, 2005 | Dumont |
20050037741 | February 17, 2005 | Gilbert |
20050038707 | February 17, 2005 | Roever et al. |
20050038724 | February 17, 2005 | Roever et al. |
20050038863 | February 17, 2005 | Onyon et al. |
20050041793 | February 24, 2005 | Fulton et al. |
20050044144 | February 24, 2005 | Malik et al. |
20050055578 | March 10, 2005 | Wright et al. |
20050063544 | March 24, 2005 | Uusitalo et al. |
20050071489 | March 31, 2005 | Parupudi et al. |
20050071674 | March 31, 2005 | Chou et al. |
20050073982 | April 7, 2005 | Corneille et al. |
20050076136 | April 7, 2005 | Cho et al. |
20050076241 | April 7, 2005 | Appelman |
20050086540 | April 21, 2005 | Gunter et al. |
20050094625 | May 5, 2005 | Bouat |
20050097225 | May 5, 2005 | Glatt et al. |
20050097570 | May 5, 2005 | Bomers |
20050101307 | May 12, 2005 | Brugge et al. |
20050102257 | May 12, 2005 | Onyon et al. |
20050102328 | May 12, 2005 | Ring et al. |
20050102351 | May 12, 2005 | Jiang et al. |
20050108427 | May 19, 2005 | Datta |
20050117606 | June 2, 2005 | Kim |
20050120082 | June 2, 2005 | Hesselink et al. |
20050120084 | June 2, 2005 | Hu et al. |
20050120181 | June 2, 2005 | Arunagirinathan et al. |
20050122333 | June 9, 2005 | Sumanaweera et al. |
20050124332 | June 9, 2005 | Clark et al. |
20050138111 | June 23, 2005 | Aton et al. |
20050138176 | June 23, 2005 | Singh et al. |
20050144219 | June 30, 2005 | Terada |
20050147130 | July 7, 2005 | Hurwitz et al. |
20050154698 | July 14, 2005 | Ikezawa et al. |
20050154796 | July 14, 2005 | Forsyth |
20050154836 | July 14, 2005 | Steeley et al. |
20050155027 | July 14, 2005 | Wei |
20050164703 | July 28, 2005 | Huynh |
20050164721 | July 28, 2005 | Eric Yeh et al. |
20050165909 | July 28, 2005 | Cromer et al. |
20050170776 | August 4, 2005 | Siorpaes |
20050183143 | August 18, 2005 | Anderholm et al. |
20050188038 | August 25, 2005 | Yabe |
20050193036 | September 1, 2005 | Phillips et al. |
20050193096 | September 1, 2005 | Yu et al. |
20050198170 | September 8, 2005 | LaMay et al. |
20050203966 | September 15, 2005 | Labrou et al. |
20050210104 | September 22, 2005 | Torvinen |
20050210125 | September 22, 2005 | Li |
20050222891 | October 6, 2005 | Chan et al. |
20050228812 | October 13, 2005 | Hansmann et al. |
20050232295 | October 20, 2005 | Young |
20050234860 | October 20, 2005 | Roever et al. |
20050235214 | October 20, 2005 | Shimizu et al. |
20050246139 | November 3, 2005 | Rivenbark et al. |
20050248526 | November 10, 2005 | Twerdahl et al. |
20050251555 | November 10, 2005 | Little, II |
20050254443 | November 17, 2005 | Campbell et al. |
20050262220 | November 24, 2005 | Ecklund et al. |
20050273804 | December 8, 2005 | Preisman |
20050278307 | December 15, 2005 | Battagin et al. |
20050278641 | December 15, 2005 | Mansour et al. |
20050278647 | December 15, 2005 | Leavitt et al. |
20050288006 | December 29, 2005 | Apfel |
20060012672 | January 19, 2006 | Schrader et al. |
20060020525 | January 26, 2006 | Borelli et al. |
20060020580 | January 26, 2006 | Dettinger et al. |
20060020804 | January 26, 2006 | Schleifer et al. |
20060020947 | January 26, 2006 | Hallamaa et al. |
20060021023 | January 26, 2006 | Stewart et al. |
20060022048 | February 2, 2006 | Johnson |
20060026580 | February 2, 2006 | Cabillic et al. |
20060029062 | February 9, 2006 | Rao et al. |
20060029063 | February 9, 2006 | Rao et al. |
20060029064 | February 9, 2006 | Rao et al. |
20060031114 | February 9, 2006 | Zommers |
20060031300 | February 9, 2006 | Kock et al. |
20060031365 | February 9, 2006 | Kay et al. |
20060031428 | February 9, 2006 | Wikman |
20060031785 | February 9, 2006 | Raciborski |
20060037071 | February 16, 2006 | Rao et al. |
20060046686 | March 2, 2006 | Hawkins et al. |
20060047844 | March 2, 2006 | Deng |
20060048061 | March 2, 2006 | Forlenza et al. |
20060052091 | March 9, 2006 | Onyon et al. |
20060052137 | March 9, 2006 | Randall et al. |
20060059495 | March 16, 2006 | Spector |
20060063544 | March 23, 2006 | Zhao et al. |
20060069686 | March 30, 2006 | Beyda et al. |
20060069687 | March 30, 2006 | Cui et al. |
20060069715 | March 30, 2006 | Vayssiere |
20060069742 | March 30, 2006 | Segre |
20060069746 | March 30, 2006 | Davis et al. |
20060073810 | April 6, 2006 | Pyhalammi et al. |
20060074951 | April 6, 2006 | Beier et al. |
20060075028 | April 6, 2006 | Zager et al. |
20060084410 | April 20, 2006 | Sutaria et al. |
20060085503 | April 20, 2006 | Stoye et al. |
20060093026 | May 4, 2006 | Montojo et al. |
20060093135 | May 4, 2006 | Fiatal et al. |
20060099969 | May 11, 2006 | Staton et al. |
20060099970 | May 11, 2006 | Morgan et al. |
20060112177 | May 25, 2006 | Barkley et al. |
20060123042 | June 8, 2006 | Xie et al. |
20060132495 | June 22, 2006 | Anderson |
20060141962 | June 29, 2006 | Forbes et al. |
20060143464 | June 29, 2006 | Ananthanarayanan et al. |
20060149591 | July 6, 2006 | Hauf et al. |
20060149843 | July 6, 2006 | Rhoads et al. |
20060149970 | July 6, 2006 | Imazu |
20060155822 | July 13, 2006 | Yang et al. |
20060161621 | July 20, 2006 | Rosenberg |
20060165226 | July 27, 2006 | Ernst et al. |
20060167969 | July 27, 2006 | Andreev et al. |
20060168043 | July 27, 2006 | Eisenberger et al. |
20060168164 | July 27, 2006 | Lemson |
20060179410 | August 10, 2006 | Deeds |
20060188864 | August 24, 2006 | Shah |
20060190428 | August 24, 2006 | Jung et al. |
20060190569 | August 24, 2006 | Neil et al. |
20060190984 | August 24, 2006 | Heard et al. |
20060192014 | August 31, 2006 | Hamilton et al. |
20060195570 | August 31, 2006 | Zellner et al. |
20060209842 | September 21, 2006 | Creamer et al. |
20060212531 | September 21, 2006 | Kikkawa et al. |
20060224629 | October 5, 2006 | Alexander et al. |
20060230394 | October 12, 2006 | Forth et al. |
20060240804 | October 26, 2006 | Backholm et al. |
20060240805 | October 26, 2006 | Backholm et al. |
20060242137 | October 26, 2006 | Shah et al. |
20060242210 | October 26, 2006 | Ring et al. |
20060242320 | October 26, 2006 | Nettle et al. |
20060242607 | October 26, 2006 | Hudson |
20060252435 | November 9, 2006 | Henderson et al. |
20060253456 | November 9, 2006 | Pacholec et al. |
20060253605 | November 9, 2006 | Sundarrajan et al. |
20060259923 | November 16, 2006 | Chiu |
20060265595 | November 23, 2006 | Scottodiluzio |
20060271884 | November 30, 2006 | Hurst |
20060277265 | December 7, 2006 | Backholm et al. |
20060277271 | December 7, 2006 | Morse et al. |
20060294071 | December 28, 2006 | Weare et al. |
20060294223 | December 28, 2006 | Glasgow et al. |
20070005738 | January 4, 2007 | Alexion-Tiernan et al. |
20070006317 | January 4, 2007 | Asami et al. |
20070011367 | January 11, 2007 | Scott et al. |
20070019610 | January 25, 2007 | Backholm et al. |
20070022118 | January 25, 2007 | Layne |
20070027775 | February 1, 2007 | Hwang |
20070027832 | February 1, 2007 | Fiatal et al. |
20070027886 | February 1, 2007 | Gent et al. |
20070027917 | February 1, 2007 | Ariel et al. |
20070027920 | February 1, 2007 | Alvarado et al. |
20070027921 | February 1, 2007 | Alvarado et al. |
20070027930 | February 1, 2007 | Alvarado et al. |
20070033531 | February 8, 2007 | Marsh |
20070038567 | February 15, 2007 | Allaire et al. |
20070038931 | February 15, 2007 | Allaire et al. |
20070044041 | February 22, 2007 | Beynon et al. |
20070049258 | March 1, 2007 | Thibeault |
20070060196 | March 15, 2007 | Sharma |
20070061393 | March 15, 2007 | Moore |
20070067147 | March 22, 2007 | Huang |
20070067381 | March 22, 2007 | Grant et al. |
20070067424 | March 22, 2007 | Raciborski et al. |
20070070931 | March 29, 2007 | Lewis et al. |
20070072617 | March 29, 2007 | Lewis et al. |
20070078857 | April 5, 2007 | Punaganti et al. |
20070078964 | April 5, 2007 | East et al. |
20070088852 | April 19, 2007 | Levkovitz |
20070105627 | May 10, 2007 | Campbell |
20070111764 | May 17, 2007 | Park et al. |
20070116223 | May 24, 2007 | Burke et al. |
20070118620 | May 24, 2007 | Cartmell et al. |
20070130108 | June 7, 2007 | Simpson et al. |
20070130217 | June 7, 2007 | Linyard et al. |
20070140193 | June 21, 2007 | Dosa et al. |
20070147317 | June 28, 2007 | Smith et al. |
20070147411 | June 28, 2007 | Bijwaard et al. |
20070150881 | June 28, 2007 | Khawand et al. |
20070156824 | July 5, 2007 | Thompson |
20070156842 | July 5, 2007 | Vermeulen et al. |
20070162514 | July 12, 2007 | Civetta et al. |
20070167178 | July 19, 2007 | Al-Harbi |
20070174433 | July 26, 2007 | Mendez et al. |
20070175998 | August 2, 2007 | Lev |
20070198698 | August 23, 2007 | Boyd et al. |
20070220080 | September 20, 2007 | Humphrey |
20070220099 | September 20, 2007 | Di Giorgio et al. |
20070233855 | October 4, 2007 | Brown et al. |
20070237318 | October 11, 2007 | McGary |
20070245010 | October 18, 2007 | Arn et al. |
20070249365 | October 25, 2007 | Jendbro |
20070250591 | October 25, 2007 | Milic-Frayling et al. |
20070254631 | November 1, 2007 | Spooner |
20070255848 | November 1, 2007 | Sewall et al. |
20070264993 | November 15, 2007 | Hughes |
20070267492 | November 22, 2007 | Maclaine Pont |
20070276925 | November 29, 2007 | LaJoie et al. |
20070276926 | November 29, 2007 | LaJoie et al. |
20070288469 | December 13, 2007 | Shenfield |
20070290787 | December 20, 2007 | Fiatal et al. |
20070293207 | December 20, 2007 | Guedalia et al. |
20070293238 | December 20, 2007 | Fiatal et al. |
20070293958 | December 20, 2007 | Stehle et al. |
20070294295 | December 20, 2007 | Finkelstein et al. |
20070294763 | December 20, 2007 | Udezue et al. |
20070296701 | December 27, 2007 | Pope et al. |
20070299918 | December 27, 2007 | Roberts |
20080001717 | January 3, 2008 | Fiatal |
20080008095 | January 10, 2008 | Gilfix |
20080009344 | January 10, 2008 | Graham et al. |
20080016236 | January 17, 2008 | Beverly et al. |
20080032718 | February 7, 2008 | Suresh |
20080034031 | February 7, 2008 | Weisbrot et al. |
20080037787 | February 14, 2008 | Boynton et al. |
20080059308 | March 6, 2008 | Gerken |
20080059398 | March 6, 2008 | Tsutsui |
20080061142 | March 13, 2008 | Howcroft et al. |
20080068519 | March 20, 2008 | Adler et al. |
20080077506 | March 27, 2008 | Rampell et al. |
20080077571 | March 27, 2008 | Harris et al. |
20080085719 | April 10, 2008 | Kuchibhotla et al. |
20080085724 | April 10, 2008 | Cormier et al. |
20080086379 | April 10, 2008 | Dion et al. |
20080091773 | April 17, 2008 | Hameen-Anttila |
20080103877 | May 1, 2008 | Gerken |
20080104666 | May 1, 2008 | Dillaway |
20080108298 | May 8, 2008 | Selen et al. |
20080114881 | May 15, 2008 | Lee et al. |
20080125225 | May 29, 2008 | Lazaridis et al. |
20080130663 | June 5, 2008 | Fridman et al. |
20080133326 | June 5, 2008 | Goncalves et al. |
20080133641 | June 5, 2008 | Gent et al. |
20080133708 | June 5, 2008 | Alvarado et al. |
20080134292 | June 5, 2008 | Ariel et al. |
20080140665 | June 12, 2008 | Ariel et al. |
20080151817 | June 26, 2008 | Fitchett et al. |
20080154870 | June 26, 2008 | Evermann et al. |
20080155613 | June 26, 2008 | Benya et al. |
20080166999 | July 10, 2008 | Guedalia et al. |
20080167019 | July 10, 2008 | Guedalia et al. |
20080168145 | July 10, 2008 | Wilson |
20080183800 | July 31, 2008 | Herzog et al. |
20080192820 | August 14, 2008 | Brooks et al. |
20080198995 | August 21, 2008 | McGary et al. |
20080201362 | August 21, 2008 | Multer et al. |
20080201751 | August 21, 2008 | Ahmed et al. |
20080207182 | August 28, 2008 | Maharajh et al. |
20080209491 | August 28, 2008 | Hasek |
20080214148 | September 4, 2008 | Ramer et al. |
20080216094 | September 4, 2008 | Anderson et al. |
20080220797 | September 11, 2008 | Meiby et al. |
20080232290 | September 25, 2008 | Elzur et al. |
20080233983 | September 25, 2008 | Park et al. |
20080242370 | October 2, 2008 | Lando et al. |
20080263170 | October 23, 2008 | Caron et al. |
20080270379 | October 30, 2008 | Ramakrishna |
20080273498 | November 6, 2008 | Jalil et al. |
20080281798 | November 13, 2008 | Chatterjee et al. |
20080288659 | November 20, 2008 | Hasha et al. |
20080298386 | December 4, 2008 | Fiatal |
20080299956 | December 4, 2008 | Bailey et al. |
20080301231 | December 4, 2008 | Mehta et al. |
20080301300 | December 4, 2008 | Toub |
20080313282 | December 18, 2008 | Warila et al. |
20090010204 | January 8, 2009 | Pratt, Jr. et al. |
20090010259 | January 8, 2009 | Sirotkin |
20090012841 | January 8, 2009 | Saft et al. |
20090016526 | January 15, 2009 | Fiatal et al. |
20090019485 | January 15, 2009 | Ellis et al. |
20090019532 | January 15, 2009 | Jacobsen et al. |
20090024794 | January 22, 2009 | Iyer et al. |
20090031006 | January 29, 2009 | Johnson |
20090052372 | February 26, 2009 | Durazzo et al. |
20090054034 | February 26, 2009 | Backholm et al. |
20090055353 | February 26, 2009 | Meema |
20090059950 | March 5, 2009 | Gao et al. |
20090063647 | March 5, 2009 | Backholm et al. |
20090075683 | March 19, 2009 | Backholm et al. |
20090077263 | March 19, 2009 | Koganti et al. |
20090077326 | March 19, 2009 | Motohashi |
20090094317 | April 9, 2009 | Venkitaraman |
20090100416 | April 16, 2009 | Brown et al. |
20090110179 | April 30, 2009 | Elsey et al. |
20090119266 | May 7, 2009 | Fitzpatrick et al. |
20090125523 | May 14, 2009 | Fitzpatrick et al. |
20090144632 | June 4, 2009 | Mendez |
20090147008 | June 11, 2009 | Do et al. |
20090149203 | June 11, 2009 | Backholm et al. |
20090156178 | June 18, 2009 | Elsey et al. |
20090157792 | June 18, 2009 | Fiatal |
20090164433 | June 25, 2009 | R et al. |
20090164560 | June 25, 2009 | Fiatal |
20090172565 | July 2, 2009 | Jackson et al. |
20090181641 | July 16, 2009 | Fiatal |
20090182500 | July 16, 2009 | Dicke |
20090187939 | July 23, 2009 | Lajoie |
20090191903 | July 30, 2009 | Fiatal |
20090193130 | July 30, 2009 | Fiatal |
20090193338 | July 30, 2009 | Fiatal |
20090215504 | August 27, 2009 | Lando |
20090221326 | September 3, 2009 | Roussel et al. |
20090228545 | September 10, 2009 | Mendez et al. |
20090241180 | September 24, 2009 | Fiatal |
20090248670 | October 1, 2009 | Fiatal |
20090248696 | October 1, 2009 | Rowles et al. |
20090248794 | October 1, 2009 | Helms et al. |
20090248878 | October 1, 2009 | Tran et al. |
20090252136 | October 8, 2009 | Mahany et al. |
20090254589 | October 8, 2009 | Nair et al. |
20090254971 | October 8, 2009 | Herz et al. |
20090264138 | October 22, 2009 | Kang et al. |
20090282125 | November 12, 2009 | Jeide et al. |
20090286531 | November 19, 2009 | Bhatt et al. |
20090287750 | November 19, 2009 | Banavar et al. |
20090299817 | December 3, 2009 | Fok et al. |
20090307133 | December 10, 2009 | Holloway et al. |
20090318171 | December 24, 2009 | Backholm et al. |
20090323678 | December 31, 2009 | Wang |
20090325565 | December 31, 2009 | Backholm |
20090327390 | December 31, 2009 | Tran et al. |
20100042691 | February 18, 2010 | Maguire |
20100049872 | February 25, 2010 | Roskind |
20100057924 | March 4, 2010 | Rauber et al. |
20100069127 | March 18, 2010 | Fiennes |
20100077035 | March 25, 2010 | Li et al. |
20100077083 | March 25, 2010 | Tran et al. |
20100083255 | April 1, 2010 | Bane et al. |
20100087167 | April 8, 2010 | Tsurutome et al. |
20100088722 | April 8, 2010 | Jiang |
20100093273 | April 15, 2010 | Hohl |
20100115050 | May 6, 2010 | Sultenfuss et al. |
20100118190 | May 13, 2010 | Salfati et al. |
20100131593 | May 27, 2010 | Kihara et al. |
20100131617 | May 27, 2010 | Osborne et al. |
20100146107 | June 10, 2010 | Fiatal |
20100149975 | June 17, 2010 | Tripathi et al. |
20100174735 | July 8, 2010 | Fiatal |
20100174939 | July 8, 2010 | Vexler |
20100186011 | July 22, 2010 | Magenheimer |
20100207870 | August 19, 2010 | Cho |
20100211651 | August 19, 2010 | Guedalia et al. |
20100214984 | August 26, 2010 | Cho et al. |
20100227594 | September 9, 2010 | DeVries |
20100228863 | September 9, 2010 | Kawauchi |
20100229096 | September 9, 2010 | Maiocco et al. |
20100238915 | September 23, 2010 | Cayla et al. |
20100250706 | September 30, 2010 | Burckart et al. |
20100250986 | September 30, 2010 | Black et al. |
20100268757 | October 21, 2010 | Fisher |
20100274983 | October 28, 2010 | Murphy et al. |
20100279662 | November 4, 2010 | Kuusinen et al. |
20100293335 | November 18, 2010 | Muthiah et al. |
20100299223 | November 25, 2010 | Crouch |
20100313018 | December 9, 2010 | Jorgensen |
20100319054 | December 16, 2010 | Mehta et al. |
20100322124 | December 23, 2010 | Luoma et al. |
20100325306 | December 23, 2010 | Vimpari et al. |
20110028129 | February 3, 2011 | Hutchison et al. |
20110040718 | February 17, 2011 | Tendjoukian et al. |
20110065424 | March 17, 2011 | Estevez et al. |
20110066646 | March 17, 2011 | Danado et al. |
20110099363 | April 28, 2011 | Boynton et al. |
20110113109 | May 12, 2011 | LeVasseur et al. |
20110119134 | May 19, 2011 | Zivkovic et al. |
20110126060 | May 26, 2011 | Grube et al. |
20110138102 | June 9, 2011 | Glikson et al. |
20110138402 | June 9, 2011 | Fleming |
20110153937 | June 23, 2011 | Annamalaisami et al. |
20110158239 | June 30, 2011 | Mohaban |
20110165889 | July 7, 2011 | Fiatal et al. |
20110179138 | July 21, 2011 | Van Geest et al. |
20110179377 | July 21, 2011 | Fleming |
20110182220 | July 28, 2011 | Black et al. |
20110184827 | July 28, 2011 | Hubert |
20110185355 | July 28, 2011 | Chawla et al. |
20110190014 | August 4, 2011 | Fiatal |
20110191474 | August 4, 2011 | Fiatal |
20110201304 | August 18, 2011 | Sutaria et al. |
20110207436 | August 25, 2011 | van Gent et al. |
20110208810 | August 25, 2011 | Li et al. |
20110213800 | September 1, 2011 | Saros et al. |
20110213898 | September 1, 2011 | Fiatal et al. |
20110214182 | September 1, 2011 | Adams et al. |
20110238772 | September 29, 2011 | Fiatal |
20110246950 | October 6, 2011 | Luna et al. |
20110252088 | October 13, 2011 | Fiatal |
20110264622 | October 27, 2011 | Vargas et al. |
20110264731 | October 27, 2011 | Knowles et al. |
20110294463 | December 1, 2011 | Fiatal |
20110294464 | December 1, 2011 | Fiatal |
20110296050 | December 1, 2011 | Cherukuri |
20110296120 | December 1, 2011 | Khan |
20110296415 | December 1, 2011 | Khan et al. |
20110302154 | December 8, 2011 | Snyder |
20120005276 | January 5, 2012 | Guo et al. |
20120008536 | January 12, 2012 | Tervahauta et al. |
20120022980 | January 26, 2012 | Angelone |
20120023190 | January 26, 2012 | Backholm et al. |
20120023226 | January 26, 2012 | Petersen et al. |
20120023236 | January 26, 2012 | Backholm et al. |
20120030280 | February 2, 2012 | Wang et al. |
20120054386 | March 1, 2012 | Hanes |
20120072910 | March 22, 2012 | Martin et al. |
20120077482 | March 29, 2012 | Backholm |
20120078996 | March 29, 2012 | Shah |
20120096092 | April 19, 2012 | Davidge et al. |
20120108225 | May 3, 2012 | Luna et al. |
20120110109 | May 3, 2012 | Luna et al. |
20120110110 | May 3, 2012 | Luna et al. |
20120110111 | May 3, 2012 | Luna et al. |
20120110112 | May 3, 2012 | Luna et al. |
20120110118 | May 3, 2012 | Luna et al. |
20120110171 | May 3, 2012 | Luna et al. |
20120110173 | May 3, 2012 | Luna et al. |
20120110174 | May 3, 2012 | Wootton et al. |
20120110275 | May 3, 2012 | Ganti et al. |
20120130973 | May 24, 2012 | Tamm et al. |
20120131095 | May 24, 2012 | Luna et al. |
20120131184 | May 24, 2012 | Luna et al. |
20120135726 | May 31, 2012 | Luna et al. |
20120140750 | June 7, 2012 | Yan et al. |
20120149352 | June 14, 2012 | Backholm et al. |
20120151044 | June 14, 2012 | Luna et al. |
20120157170 | June 21, 2012 | Backholm et al. |
20120158837 | June 21, 2012 | Kaul |
20120158908 | June 21, 2012 | Luna et al. |
20120170496 | July 5, 2012 | Yang et al. |
20120173616 | July 5, 2012 | Luna et al. |
20120174220 | July 5, 2012 | Rodriguez |
20120176968 | July 12, 2012 | Luna |
20120178414 | July 12, 2012 | Fiatal |
20120179801 | July 12, 2012 | Luna et al. |
20120185597 | July 19, 2012 | Luna |
20120185918 | July 19, 2012 | Backholm et al. |
20120210121 | August 16, 2012 | Boynton et al. |
20120226767 | September 6, 2012 | Luna et al. |
20120227059 | September 6, 2012 | Fleming |
0772327 | May 1997 | EP |
1278390 | January 2003 | EP |
1422899 | May 2004 | EP |
1462975 | September 2004 | EP |
1466261 | October 2004 | EP |
1466435 | October 2004 | EP |
1482702 | December 2004 | EP |
1815634 | August 2007 | EP |
1815652 | August 2007 | EP |
1817883 | August 2007 | EP |
117152 | June 2006 | FI |
118288 | September 2007 | FI |
119581 | December 2008 | FI |
4-154233 | May 1992 | JP |
4154233 | May 1992 | JP |
10-336372 | December 1998 | JP |
2001-218185 | August 2001 | JP |
2001-218185 | October 2001 | JP |
2001-350718 | December 2001 | JP |
2001-356973 | December 2001 | JP |
2005-515664 | May 2005 | JP |
2009-207177 | September 2009 | JP |
4386732 | October 2009 | JP |
2001-0018568 | March 2001 | KR |
2006-0068186 | June 2006 | KR |
2007-0071858 | July 2007 | KR |
10-0765238 | October 2007 | KR |
2007-0102091 | October 2007 | KR |
2007-0117874 | December 2007 | KR |
2009-0077515 | July 2009 | KR |
2010-0064605 | June 2010 | KR |
WO 97/41661 | November 1997 | WO |
WO 97/41661 | November 1997 | WO |
9824257 | June 1998 | WO |
WO 98/24257 | June 1998 | WO |
WO 98/58322 | December 1998 | WO |
WO 98/58322 | December 1998 | WO |
WO 01/30130 | May 2001 | WO |
WO 03/007570 | January 2003 | WO |
WO 03/058483 | July 2003 | WO |
WO 03/058879 | July 2003 | WO |
WO 03/065701 | August 2003 | WO |
03098890 | November 2003 | WO |
WO 03/098890 | November 2003 | WO |
WO 2004/017591 | February 2004 | WO |
2004045171 | May 2004 | WO |
WO 2004/045171 | May 2004 | WO |
WO 2005/015925 | February 2005 | WO |
WO 2005/020108 | March 2005 | WO |
WO 2006/045005 | April 2006 | WO |
WO 2006/045102 | April 2006 | WO |
WO 2006/053952 | May 2006 | WO |
WO 2006/053954 | May 2006 | WO |
WO 2006/058967 | June 2006 | WO |
WO 2007/015725 | February 2007 | WO |
WO 2007/015726 | February 2007 | WO |
WO 2007/149526 | December 2007 | WO |
WO 2007/149540 | December 2007 | WO |
WO 2008/061042 | May 2008 | WO |
WO 2011/126889 | October 2011 | WO |
WO 2012/018430 | February 2012 | WO |
WO 2012/018431 | February 2012 | WO |
WO 2012/018477 | February 2012 | WO |
WO 2012/018479 | February 2012 | WO |
WO 2012/018556 | February 2012 | WO |
WO 2012/024030 | February 2012 | WO |
WO 2012/060995 | May 2012 | WO |
WO 2012/060996 | May 2012 | WO |
WO 2012/060997 | May 2012 | WO |
WO 2012/061430 | May 2012 | WO |
WO 2012/061433 | May 2012 | WO |
WO 2012/061437 | May 2012 | WO |
WO 2012/071283 | May 2012 | WO |
WO 2012/071384 | May 2012 | WO |
WO 2012/094675 | July 2012 | WO |
- Allchin, James Edward, “An Architecture for Reliable Decentralized Systems,” Ph.D. Thesis, Georgia Institute of Technology, 185 pages, Sep. 1983.
- Android Developers, “Date,” 10 pages, Oct. 27, 2011.
- Augun, Audrey, “Integrating Lotus Notes With Enterprise Data,” Lotus Notes Advisory, pp. 22-25, Jul.-Aug. 1996.
- Balaban, Bob, “This Is Not Your Father's Basic: LotusScript in Notes Release 4,” The View, vol. 1, Issue 5, 32 pages, Nov.-Dec. 1995.
- Bedell, Doug, “Meeting Your New Best Friends Six Degrees Widens Your Contacts In Exchange for Sampling Web Sites,” The Dallas Morning News, 4 pages, Oct. 27, 1998.
- Bergman, Lawrence D. et al., “Programming-By-Demonstration for Behavior-Based User Interface Customization,” IBM Research Report, RC23116, 5 pages, Feb. 20, 2004.
- B'Far, Reza et al., “Designing Effective User Interfaces for Wireless Devices,” Publication Unknown, 14 pages, Published prior to Feb. 23, 2006.
- Blaney, Jeff, “You Can Take It With You—An Introduction to Mobile Computing With Notes R4,” The View, vol. 2, Issue 1, 14 pages, Jan.-Feb. 1996.
- Braden, R., “Requirements for Internet Hosts—Application and Support,” RFC 1123, 80 pages, Oct. 1989.
- Brown, Kevin et al., “Mastering Lotus Notes®,” Sybex Inc., 996 pages, 1995.
- “Chapter: About NotesPump,” Publication Unknown, 480 pages, Published prior to Jan. 8, 2003.
- “Chapter 13-1—Anatomy of a Note ID,” Publication Unknown, 8 pages, Published prior to Jan. 8, 2003.
- Cole, Barb et al., “Lotus Airs Notes-To-Database Integration Tool,” Network World, 2 pages, Oct. 2, 1995.
- “CR 3483 to Release 8 TS 25.331, Rev. 2,” 3GPP TSG-RAN2 Meeting #64, Prague, Czech Republic, 11 pages, Nov. 10-14, 2008.
- “CR 4100 to Release 8 TS 25.331, Rev. 1,” 3GPP TSG-RAN WG2 Meeting #69, San Francisco, U.S., 6 pages, Feb. 22-26, 2010.
- Dahl, Andrew, “Lotus Notes® 4 Administrator's Survival Guide,” Sams Publishing, 64 pages, 1996.
- Decker, Stefan et al., “The Social Semantic Desktop,” Digital Enterprise Research Institute, DERI Technical Report 2004-05-02, 7 pages, May 2004.
- Elz, R. et al., “Clarifications to the DNS Specification,” RFC 2181, 12 pages, Jul. 1997.
- European Patent Application No. EP 03705704.9, Supplementary European Search Report, 4 pages, Jun. 9, 2010.
- European Patent Application No. EP 03707338.4, Supplementary European Search Report, 2 pages, Apr. 18, 2011.
- European Patent Application No. EP 05815115.0, Supplementary European Search Report, 7 pages, Nov. 17, 2011.
- Falkner, Mike, “How to Plan, Develop, and Implement Lotus Notes® in Your Organization,” John Wiley & Sons, Inc., 539 pages, 1996.
- Freeland, Pat et al., “Lotus Notes 3-3.1 for Dummies™,” IDG Books Worldwide, 389 pages, 1994.
- Frenkel, Garry, “Pumping for Info: Notes and Database Integration,” Network Computing, 10 pages, May 1, 1996.
- Gameline, Advertisement, 1 page, 1982.
- Gewirtz, David, “Lotus Notes 3 Revealed!,” Prima Publishing, 261 pages, 1994.
- Grous, Paul J., “Creating and Managing a Web Site With Lotus Internotes Web Publisher,” The View, vol. 1, Issue 4, 20 pages, Sep.-Oct. 1995.
- GSM Association, “Network Efficiency Task Force Fast Dormancy Best Practices,” V1.0, 21 pages, May 26, 2010.
- Haas, Zygmunt J. et al., “Mobile-TCP: An Asymmetric Transport Protocol Design for Mobile Systems,” IEEE, pp. 1054-1058, 1997.
- 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.
- Hajdu, Kalman et al., “Lotus Notes Release 4 in A Multiplatform Environment,” IBM Corporation, 173 pages, Feb. 1996.
- Hardy, Ed, “Microsoft Proposes Two New Thumb-Driven User Interfaces,” Brighthand Consulting, Inc., 2 pages, 2003.
- IBM Corporation, “The Architecture of Lotus Notes,” White Paper No. 114654, 26 pages, May 31, 1995.
- IBM Corporation, “The History of Notes and Domino,” Lotus Developer Domain, 11 pages, Sep. 29, 2003.
- ImTOO, “ImTOO iPod Movie Converter,” 3 pages, Nov. 9, 2005.
- IntelliLink Corporation, “IntelliLink® for Windows User's Guide,” Version 3.0, 167 pages, 1994.
- International Application No. PCT/US2003/000618, International Search Report, 1 page, Apr. 4, 2003.
- International Application No. PCT/US2003/000624, International Search Report, 2 pages, May 13, 2003.
- International Application No. PCT/US2005/037702, International Preliminary Examination Report, 6 pages, Nov. 20, 2007.
- International Application No. PCT/US2005/037702, International Search Report, 1 page, Nov. 5, 2007.
- International Application No. PCT/US2005/037702, Written Opinion, 6 pages, Nov. 5, 2007.
- International Application No. PCT/US2005/038135, International Search Report, 2 pages, Aug. 8, 2008.
- International Application No. PCT/US2005/038135, Written Opinion, 8 pages, Aug. 8, 2008.
- International Application No. PCT/US2005/038135, International Preliminary Report on Patentability, 9 pages, Oct. 31, 2011.
- International Application No. PCT/FI2005/050424, International Search Report, 4 pages, Mar. 2, 2006.
- International Application No. PCT/FI2005/050426, International Search Report, 3 pages, Mar. 1, 2006.
- International Application No. PCT/FI2005/050441, International Search Report, 3 pages, Mar. 1, 2006.
- International Application No. PCT/US2006/023426, International Search Report, 1 page, Feb. 21, 2007.
- International Application No. PCT/US2006/023427, International Search Report, 1 page, Oct. 12, 2006.
- International Application No. PCT/US2007/014462, International Search Report, 1 page, Jul. 2, 2008.
- International Application No. PCT/US2007/014497, International Search Report, 1 page, Aug. 25, 2008.
- International Application No. PCT/US2011/030534, International Search Report, 10 pages, Dec. 29, 2011.
- International Application No. PCT/US2011/037932, International Search Report, 9 pages, Jan. 2, 2012.
- International Application No. PCT/US2011/037943, International Search Report, 11 pages, Jan. 2, 2012.
- International Application No. PCT/US2011/043322, International Search Report, 9 pages, Feb. 9, 2012.
- International Application No. PCT/US2011/043328, International Search Report, 12 pages, Feb. 27, 2012.
- International Application No. PCT/US2011/043409, International Search Report, 11 pages, Feb. 9, 2012.
- International Application No. PCT/US2011/058840, International Search Report, 10 pages, Apr. 26, 2012.
- International Application No. PCT/US2011/058843, International Search Report, 11 pages, May 16, 2012.
- International Application No. PCT/US2011/058848, International Search Report, 10 pages, Apr. 10, 2012.
- International Application No. PCT/US2011/061512, International Search Report, 10 pages, May 10, 2012.
- International Application No. PCT/US2012/022121, International Search Report, 11 pages, May 14, 2012.
- Japanese Patent Application No. 2003-558726, Office Action, 2 pages, Jun. 10, 2008.
- 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.
- Kent, S. et al., “Security Architecture for the Internet Protocol,” RFC 2401, The Internet Society, 62 pages, Nov. 1998.
- Kleinberg, Jon, “The Small-World Phenomenon: An Algorithmic Perspective,” Cornell Computer Science Technical Report 99/1776, 14 pages, Oct. 1999.
- Koeppel, Dan, “GUIs Just Want To Have Fun,” Wired Magazine, Issue 8.10, 12 pages, Oct. 2000.
- Kornblith, Polly Russell, “Lotus Notes Answers: Certified Tech Support,” Covers Release 3, McGraw-Hill, Inc., 326 pages, 1994.
- Kreisle, Bill, “Teach Yourself . . . Lotus Notes 4,” MIS Press, 464 pages, 1996.
- Lamb, John P. et al., “Lotus Notes Network Design,” McGraw-Hill, 278 pages, 1996.
- Londergan, Stephen et al., “Lotus Notes® Release 4 For Dummies®,” IDG Books Worldwide, 229 pages, 1996.
- Lotus Development Corporation, “Firewall Security Overview and How Firewalls Relate to Lotus Notes,” Lotus Notes Knowledge Base, 9 pages, May 22, 1996.
- Lotus Development Corporation, “How to Set Up ‘Firewall’ Protection for a Notes Domain,” Lotus Notes Knowledge Base, 2 pages, Nov. 6, 1995.
- Lotus Development Corporation, “Lotus Announces Lotus NotesPump 1.0,” Lotus Notes Knowledge Base, 6 pages, Oct. 31, 1995.
- Lotus Development Corporation, “Lotus Inside Notes—The Architecture of Notes and the Domino Server,” 207 pages, 2000.
- Lotus Development Corporation, “Lotus NotesPump 1.0 Q & A,” Lotus Notes Knowledge Base, 3 pages, Oct. 31, 1995.
- Lotus Development Corporation, “Lotus NotesPump: Database Integration for Lotus Notes,” Lotus Notes Knowledge Base, 5 pages, Oct. 31, 1995.
- Lotus Development Corporation, “Lotus Notes Administration,” Release 3.3, 20 pages, 1995.
- Lotus Development Corporation, “Lotus Notes Administrator's Guide,” Release 4, 499 pages, 1995.
- Lotus Development Corporation, “Lotus Notes Administrators Guide—Server for NetWare, OS-2, and Unix,” Release 3.1, 509 pages, 1994.
- Lotus Development Corporation, “Lotus Notes Administrators Guide—Server for Windows,” Release 3.1, 345 pages, 1994.
- Lotus Development Corporation, “Lotus Notes Application Developer's Guide,” Release 4, 475 pages, 1995.
- Lotus Development Corporation, “Lotus Notes Customer Service Application Guide,” Release 3.1, 46 pages, 1994.
- Lotus Development Corporation, “Lotus Notes Customer Support Guide,” 33 pages, Published prior to Jan. 8, 2003.
- Lotus Development Corporation, “Lotus Notes Customer Support Guide—North American Guide,” Release 4.1, 51 pages, Published prior to Jan. 8, 2003.
- Lotus Development Corporation, “Lotus Notes Database Manager's Guide,” Release 4, 115 pages, 1995.
- Lotus Development Corporation, “Lotus Notes Deployment Guide,” Release 4, 104 pages, 1995.
- Lotus Development Corporation, “Lotus Notes for Windows, OS-2, and Macintosh,” Release 3.3, 89 pages, 1995.
- Lotus Development Corporation, “Lotus Notes Getting Started With Application Development,” Release 3.1, 151 pages, 1994.
- Lotus Development Corporation, “Lotus Notes Install Guide for Servers,” Release 4, 68 pages, 1996.
- Lotus Development Corporation, “Lotus Notes Install Guide for Workstations,” Release 4, 28 pages, 1995.
- Lotus Development Corporation, “Lotus Notes Install Guide for Workstations,” Release 4.1, 67 pages, 1996.
- Lotus Development Corporation, “Lotus Notes Install Guide for Workstations,” Release 4.5, 81 pages, 1996.
- Lotus Development Corporation, “Lotus Notes Internet Cookbook for Notes Release 3,” 21 pages, Jan. 16, 1996.
- Lotus Development Corporation, “Lotus Notes Internet Cookbook for Notes Release 4,” 35 pages, Feb. 14, 1996.
- Lotus Development Corporation, “Lotus Notes Internotes Web Navigator Administrator's Guide,” Release 4, 60 pages, 1995.
- Lotus Development Corporation, “Lotus Notes Internotes Web Navigator User's Guide,” Release 4, 56 pages, 1995.
- Lotus Development Corporation, “Lotus Notes Internotes Web Publisher Guide,” Release 4, 122 pages, 1996.
- Lotus Development Corporation, “Lotus Notes LotusScript Classes for Notes,” Release 4, 6 pages, Published prior to Jan. 8, 2003.
- Lotus Development Corporation, “Lotus Notes Migration Guide,” Release 4, 110 pages, 1996.
- Lotus Development Corporation, “Lotus Notes Network Configuration Guide,” Release 4.5, 121 pages, 1996.
- Lotus Development Corporation, “Lotus Notes Network Driver Documentation,” Release 3.1, 100 pages, 1994.
- Lotus Development Corporation, “Lotus Notes Programmers Guide—Part 1,” Release 4, 614 pages, 1995.
- Lotus Development Corporation, “Lotus Notes Programmers Guide—Part 2,” Release 4, 462 pages, 1995.
- Lotus Development Corporation, “Lotus Notes Quick Reference for Application Developers,” Release 3, 6 pages, Published prior to Jan. 8, 2003.
- Lotus Development Corporation, “Lotus Notes Quick Reference for Macintosh,” Release 3, 6 pages, Published prior to Jan. 8, 2003.
- Lotus Development Corporation, “Lotus Notes Quick Reference for SmartIcons,” Release 3.1, 4 pages, Published prior to Jan. 8, 2003.
- Lotus Development Corporation, “Lotus Notes Quick Reference for Windows and Presentation Manager,” Release 3, 6 pages, Published prior to Jan. 8, 2003.
- Lotus Development Corporation, “Lotus Notes Release Notes,” Release 4, 139 pages, 1995.
- Lotus Development Corporation, “Lotus Notes Release Notes,” Release 4.1, 197 pages, 1996.
- Lotus Development Corporation, “Lotus Notes Server for Windows,” Release 3.3, 7 pages, 1994.
- Lotus Development Corporation, “Lotus Notes Server Up and Running!,” Release 4, 13 pages, 1996.
- Lotus Development Corporation, “Lotus Notes Site and Systems Planning Guide,” Release 3.1, 169 pages, 1994.
- Lotus Development Corporation, “Lotus Notes Start Here—Workstation Install for Windows, OS-2 and Macintosh,” Release 3.3, 47 pages, 1995.
- Lotus Development Corporation, “Lotus Notes Step by Step—A Beginner's Guide to Lotus Notes,” Release 4, 179 pages, 1995.
- Lotus Development Corporation, “Lotus Notes Step by Step—A Beginner's Guide to Lotus Notes,” Release 4.1, 167 pages, 1996.
- Lotus Development Corporation, “Lotus Software Agreement,” 8 pages, Published prior to Jan. 8, 2003.
- Lotus Development Corporation, “What Is the Notes Replicator?,” Lotus Notes Knowledge Base, 8 pages, Jul. 5, 1995.
- “Lotus Notes Advisor,” Advisor Publications Inc., 55 pages, Jun. 1995.
- “Lotus Notes Advisor,” Advisor Publications Inc., 55 pages, Aug. 1995.
- “Lotus Notes Advisor,” Advisor Publications Inc., 55 pages, Oct. 1995.
- “Lotus Notes Advisor,” Advisor Publications Inc., 55 pages, Dec. 1995.
- “Lotus Notes Advisor,” Advisor Publications Inc., 63 pages, Jan.-Feb. 1996.
- “Lotus Notes Advisor,” Advisor Publications Inc., 55 pages, Apr. 1996.
- “Lotus Notes Advisor,” Advisor Publications Inc., 55 pages, Jun. 1996.
- “Lotus Notes Advisor,” Advisor Publications Inc., 55 pages, Aug. 1996.
- “Lotus Notes Advisor,” Advisor Publications Inc., 55 pages, Oct. 1996.
- “Lotus Notes Advisor,” Advisor Publications Inc., 63 pages, Dec. 1996.
- “Lotus Notes—Notes Administration Help,” Screen Shots, 17 pages, Published prior to Jan. 8, 2003.
- MacGregor, Rob et al., “The Domino Defense: Security in Lotus Notes and the Internet,” IBM Corporation, 183 pages, Dec. 1997.
- Maltz, David A. et al., “MSOCKS: An Architecture for Transport Layer Mobility,” IEEE, pp. 1037-1045, 1998.
- Marmel, Elaine, “Easy Lotus® Notes Release 4.0,” Que Corporation, 237 pages, 1996.
- Mason, Luke, “Windows XP: New GUI Design Shows Skin Is In,” TechRepublic, 4 pages, Apr. 4, 2001.
- Microsoft, Definition of “Access,” Microsoft Computer Dictionary, Fifth Edition, 2 pages, May 1, 2002.
- Microsoft, Definition of “Synchronization,” Microsoft Computer Dictionary, Fifth Edition, 2 pages, May 1, 2002.
- Milgram, Stanley, “The Small-World Problem,” Psychology Today, vol. 2, pp. 60-67, 1967.
- Miller, Victor S., “Use of Elliptic Curves in Cryptography,” Advances in Cryptology—CRYPTO '85 Proceedings, vol. 218, pp. 417-426, 1985.
- Mockapetris, P., “Domain Names—Concepts and Facilities,” RFC 1034, 43 pages, Nov. 1987.
- Mockapetris, P., “Domain Names—Implementation and Specification,” RFC 1035, 43 pages, Nov. 1987.
- 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.
- 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.
- National Institute of Standards and Technology, “Advanced Encryption Standard (AES),” Federal Information Processing Standards Publication 197, 52 pages, Nov. 26, 2001.
- National Institute of Standards and Technology, “Secure Hash Standard,” Federal Information Processing Standards Publication 180-2, 83 pages, Aug. 1, 2002.
- Netscape Communications Corporation, “Netscape Mail Server Administrator's Guide,” Version 2.0, 172 pages, 1996.
- Netscape Communications Corporation, “Netscape Mail Server Installation Guide,” Version 2.0 for Unix, 62 pages, 1996.
- Netscape Communications Corporation, “Netscape Mail Server User's Guide,” Version 2.0, 35 pages, 1996.
- Netscape Communications Corporation, “Netscape News Server Administrator's Guide for Windows NT,” Version 2.0, 119 pages, 1996.
- 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.
- Nokia, “Developer Platforms,” 3 pages, 2005.
- “NotesPump 1.0 Release Notes,” Publication Unknown, 8 pages, Published prior to Jan. 8, 2003.
- Opyt, Barbara et al., “Use the Internet As Your Lotus Notes WAN,” Lotus Notes Advisor, pp. 17-20, Nov.-Dec. 1996.
- Ortiz, C. Enrique, “An Introduction to the Symbian OS™ Platform for Palm OS® Developers,” Metrowerks Corp., 21 pages, 2002.
- “Overview—What Is Lotus NotesPump?,” Publication Unknown, 88 pages, Published prior to Jan. 8, 2003.
- Perez, Sarah, “Onavo's Data-Compressing Mobile App Raises $10 Million Series B From Horizons, Motorola Ventures,” 2 pages, Jan. 24, 2012.
- Pyle, Hugh, “The Architecture of Lotus Notes,” Lotus Notes Advisor, Premiere Issue, pp. 18-27, 1995.
- 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.
- Qualcomm Incorporated, “Managing Background Data Traffic in Mobile Devices,” 16 pages, Jan. 2012.
- Qualcomm, “System Parameter Recommendations to Optimize PS Data User Experience and UE Battery Life,” 80-W1112-1, Revision B, 9 pages, Mar. 2007.
- Ringel, Meredith et al., “iStuff: A Scalable Architecture for Lightweight, Wireless Devices for Ubicomp User Interfaces,” Proceedings of UbiComp 2002, 2 pages, 2002.
- Signorini, Eugene, “Seven's Service-Based Wireless Solutions Enable Enterprises to Untether E-Mail,” Wireless/Mobile Enterprise & Commerce, 16 pages, Oct. 2004.
- Swedeen, Bret et al., “Under The Microscope—Domino Replication,” LDD Today, 8 pages, Oct. 1, 1998.
- Tamura, Randall A., “Lotus® Notes™ 4 Unleashed,” Sams Publishing, 928 pages, 1996.
- U.S. Appl. No. 60/663,463, File History, 113 pages, Mar. 18, 2005.
- Vivacqua, Adriana et al., “Profiling and Matchmaking Strategies In Support Of Opportunistic Collaboration,” CoopIS/DOA/ODBASE 2003, LNCS 2888, pp. 162-177, 2003.
- Wainwright, Andrew, “Secrets to Running Lotus Notes: The Decisions No One Tells You How to Make,” IBM Corporation, 193 pages, Oct. 1996.
- Wilcox, Adam A., “PC Learning Labs Teaches Lotus Notes 3.0,” Ziff-Davis Press, 381 pages, 1993.
- Wong, Harry, “Casahl's Replic-Action: Delivering True Notes-DBMS Integration,” The View, vol. 2, Issue 1, pp. 33-50, Jan.-Feb. 1996.
- Eronen, “TCP Wake-Up: Reducing Keep-Alive Traffic in Mobile IPv4 and Ipsec NAT Traversal,” NRC-TR-2008-002, Nokia, 10 pages, Jan. 31, 2008.
- European Patent Application No. EP 03707338.4, Examination Report, 4 pages, Sep. 9, 2011.
- European Patent Application No. EP 05813041.0, Supplementary European Search Report & Examination Report, 10 pages, Apr. 25, 2013.
- European Patent Application No. EP 05813045.1, Supplementary European Search Report & Examination Report, 6 pages, Apr. 9, 2013.
- International Application No. PCT/US2011/044974, International Search Report & Written Opinion, 15 pages, Jun. 1, 2012.
- International Application No. PCT/US2011/056474, International Search Report & Written Opinion, 9 pages, May 4, 2012.
- International Application No. PCT/US2011/056476, International Search Report & Written Opinion, 12 pages, May 24, 2012.
- International Application No. PCT/US2011/056478, International Search Report & Written Opinion, 11 pages, May 31, 2012.
- International Application No. PCT/US2011/061795, International Search Report & Written Opinion, 10 pages, Jul. 31, 2012.
- International Application No. PCT/US2012/020669, International Search Report & Written Opinion, 10 pages, Sep. 12, 2012.
- International Application No. PCT/US2012/021459, International Search Report & Written Opinion, 10 pages, Jun. 1, 2012.
- Newton, Harry, “Newton's Telecom Dictionary,” 20th Edition, pp. 67, 127, 542, Mar. 2004.
- 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. 59-73, 2001.
- Seven Networks, Inc., “Seven Optimizing the Mobile Ecosystem,” www.seven.com/products.traffic—optimization.php, 1 page, May 29, 2012.
- Wikipedia, Definition for “General Packet Radio Service,” 7 pages, downloaded on May 31, 2012.
- Lotus Development Coporation, Lotus Notes Release 3.1: The Groupware Standard, Site and Systems Planning Guide 1991.
- Lotus Development Corporation, Lotus Notes: The Groupware Standard—Windows, 1994.
- International Search Report for PCT/US03/00618, Date of completion Mar. 19, 2003; Date of Mailing Apr. 4, 2003; ISA/US.
- International Search Report for PCT/US03/00624, Date of completion Apr. 8, 2003; Date of Mailing May 13, 2003; ISA/US.
- International Search Report for PCT/US05/038135, Date of completion Jan. 30, 2007; Mailing Date Aug. 8, 2008; ISA/US.
- International Search Report for PCT/US05/37702, Date of completion Oct. 24, 2007; Date of Mailing Nov. 5, 2007; ISA/US.
- International Preliminary Examination Report for PCT/US05/37702, Date of completion Nov. 20, 2007; ISA/US.
- Written Opinion of the International Searching Authority for PCT/US05/37702; Date of completion Oct. 24, 2007; Date of mailing Nov. 5, 2007; ISA/US.
- Written Opinion of the International Searching Authority for PCT/US05/38135; Date of completion Jul. 14, 2008; Date of mailing Aug. 8, 2008; ISA/US.
- Stolowitz Ford Cowger, LLP, Listing of Related Cases, Jul. 13, 2009.
- Victor S. Miller, “Use of Elliptic Curves in Cryptography”, Lecture Notes in Computer Science, May 21, 1986, vol. 218, p. 417-426, Advances in Cryptology-Crypto' 85.
- Netscape Communications Corporation, Administrator's Guide, Netscape Mail Server, Version 2.0, 1995.
- IBM, “The Architecture of Lotus Notes,” White Paper No. 114654, modified date: May 31, 1995.
- Lotus Development Corporation, Lotus Notes Knowledge Base, “What is the Notes Replicator”, Jul. 5, 1995.
- 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.
- Cole, Barb et al., “Lotus airs Notes-to-database integration tool,” www.looksmart.com, Oct. 2, 1995.
- Lotus Development Corporation, Lotus Notes Knowledge Base, “Lotus Announces Lotus NotesPump 1.0”, Oct. 31, 1995.
- Lotus Development Corporation, Lotus Notes Knowledge Base, “Lotus NotesPump 1.0 Q & A”, Oct. 31, 1995.
- Lotus Development Corporation, Lotus Notes Knowledge Base, “Lotus NotesPump: Database Integration for Lotus Notes”, Oct. 31, 1995.
- Lotus Development Corporation, Lotus Notes Knowledge Base, “How to Set Up “Firewall” Protection for a Notes Domain”, Nov. 6, 1995.
- Lotus Development Corporation, Lotus Notes Release 4 Install Guide for Workstations, First Revision, 1996.
- Lotus Development Corporation, Lotus Step by Step: A Beginner's Guide to Lotus Notes, First Revision, 1996.
- Freeland, Pat and Londergan, Stephen, Lotus Notes Release 4 for Dummies™, IDG Books Worldwide, 1996.
- Kreisle, Bill, Teach Yourself . . . Lotus Notes 4, MIS:Press, 1996.
- Marmel, Elain, Easy Lotus® Notes Release 4.0, Que Corporation, 1996.
- Lotus Development Corporation, Lotus Notes Server Up and Running!, Release 4, 1996.
- Falkner, Mike, “How to Plan, Develop, and Implement Lotus Notes in Your Organization”, Wiley Computer Publishing, John Wiley and Sons, Inc., 1996.
- Lamp, John P., et al., “Lotus Notes Network Design”, McGraw-Hill, 1996.
- Tamura, Randall, A., et al., Lotus Notes 4 Unleashed, Sams Publishing, 1996.
- Lotus Development Corporation, Lotus Notes Internet Cookbook for Notes Release 3, Jan. 16, 1996.
- 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.
- IBM International Technical Support Organization, Lutos Notes Release 4 In a Multiplatform Environment, Feb. 1996.
- Lotus Development Corporation, Lotus Notes Internet Cookbook for Notes Release 4, Feb. 14, 1996.
- Frenkel, Garry, “Pumping for Info: Notes and Database Integration”, Network Computing, May 1, 1996, pp. 76-84.
- Lotus Development Corporation, Lotus Notes Knowledge Base, “Firewall Security Overview and How Firewalls Relate to Lotus Notes”, May 22, 1996.
- IBM Corporation, Secrets to Running Lotus Notes: The Decisions No One Tells You How to Make, Oct. 1996.
- Swedeen, Bret, et al., “Under the Microscope: Domino Replication”, LDD Today, Oct. 1, 1998.
- Lotus Development Corporation, Lotus Inside Notes: The Architecture of Notes and the Domino Server, 2000.
- Lotus Software Agreement for “Notes 4.0 NA DKTP Client UPG”, Part No. 38985, Date unknown.
- Lotus Development Corporation, Lotus Notes Release 3.1: Administrator's Guide—Server for Windows, 1993.
- Pyle, Hugh, “The Architecture of Lotus Notes”, Lotus Notes Advisor, Advisor Publication, Premier Issue 1995, pp. 18-27.
- Lotus Notes Advisor, Advisor Publications, Jun. 1995, entire magazine.
- Lotus Notes Advisor, Advisor Publications, Aug. 1995, entire magazine.
- Lotus Notes Advisor, Advisor Publications, Oct. 1995, entire magazine.
- Balaban, Bob, “This Is Not Your Fathers Basic: LotusScript in Notes Release 4”, Lotus Notes Advisor, Advisor Publications, vol. 1, No. 5, Nov.-Dec. 1995, pp. 31-58.
- 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., pp. 3-20.
- Lotus Notes Advisor, Advisor Publications, Dec. 1995, entire magazine.
- Dahl, Andrew, Lotus Notes 4 Administrator's Survical Guide, Sams Publishing, 1996.
- Netscape Communications Corporation, Administrator's Guide, Netscape News Server, Version 2.0, 1996.
- Lotus Notes Advisor, Advisor Publications, Jan./Feb. 1996, entire magazine.
- 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.
- Lotus Notes Advisor, Advisor Publications, Apr. 1996, entire magazine.
- Lotus Notes Advisor, Advisor Publications, Jun. 1996, entire magazine.
- Augun, Audry, “Integrating Lotus Notes With Enterprise Data,” Lotus Notes Advisor, Advisor Publications, Jul./Aug. 1996, pp. 22-25.
- Lotus Notes Advisor, Advisor Publications, Aug. 1996, entire magazine.
- Lotus Notes Advisor, Advisor Publications, Oct. 1996, entire magazine.
- Opyt, Barbara et al., “Use the Internet as Your Lotus Notes WAN”, Lotus Notes Advisor, Advisor Publications, Nov./Dec. 1996, pp. 17-20.
- Lotus Notes Advisor, Advisor Publications, Dec. 1996. entire magazine.
- “The History of Notes and Domino”, Lotus Developer Domain, Lotus, Sep. 29, 2003.
- Lotus NotesPump miscellaneous paper, date unkown.
- NotesPump 1.0 Release Notes, date unknown.
- Lotus Notes-Notes Administration Help screen shot, date unknown.
- Chapter 13-1, publication unknown, “Anantomy of a Note ID”, date unknown.
- Chapter: About NotesPump, publication unknown, date unknown.
- Lotus Development Corporation, Lotus Quick Reference for SmartIcons, Lotus Notes Release 3.1, Date unknown.
- Lotus Development Corporation, Lotus Quick Reference for Windows and Presentation Manager, Lotus Notes Release 3, Date unknown.
- Lotus Development Corporation, Lotus Quick Reference for Macintosh, Lotus Notes Release 3.0, Date unknown.
- Lotus Development Corporation, Lotus Quick Reference for Application Developer's, Lotus Notes Release 3, Date Unknown.
- Lotus Development Corporation, Lotus Customer Support Service, Lotus Notes Customer Support Guides, Date Unknown.
- Lotus Development Corporation, Lotus Notes 3.3, Lotus Customer Support, North American Guide, 29 pages, Date unknown.
- Lotus Development Corporation, Lotus Notes 4.0, Lotus Customer Support, North American Guide, 29 pages, Date unknown.
- Lotus Development Corporation, Lotus Notes 4.1 Starter Pack; Lotus Customer Support, North American Guide, 51 pages, Date unknown.
- Lotus Development Corporation, “LotusScript Clases for Notes Release 4”, 6 pages, date unknown.
- Allchin, James E., “An Architecture for Reliable Decentralized Systems”, UMI Dissertation Services, Copyright 1983.
- Lotus Development Corporation, Lotus Notes Release 3.1: The Groupware Standard, Administrator's Guide—Server for NetWare, OS/2, and UNIX, 1989.
- Lotus Development Corporation, Lotus Notes 3.0: The Quick and Easy Way to Learn, Ziff-Davis Press, 1993.
- Lotus Development Corporation, Lotus Notes Release 3.3: Start Here, Workstation Install for Windows, OS/2 and Macintosh, 1993.
- Lotus Development Corporation, Lotus Notes Release 3.1: The Groupware Standard, Customer Services Application Guide, 1994.
- Lotus Development Corporation, Lotus Notes Release 3.1: The Groupware Standard, Getting Started with Application Development, 1994.
- Lotus Development Corporation, Lotus Notes Release 3.1: The Groupware Standard, Network Driver Documentation, 1994.
- Kornblith, Polly R., Lotus Notes Answers: Certified Tech Support, Covers Lotus Notes Release 3, Osborne McGraw-Hill, 1994.
- Freeland, Pat and Londergan, Stephen, Lotus Notes 3/3.1 for Dummies™, IDG Books Worldwide, 1994.
- Gewirtz, David, Lotus Notes 3 Revealed! Your Guide to Managing Information and Improving Communication Throughhout Your Organization, Prima Publishing, 1994.
- Shafran, Andrew B., Easy Lotus notes for Windows™, Que® Corporation, 1994.
- Lotus Development Corporation, Lotus Notes Release 3.3: The Groupware Standard, Administration, 1994.
- McMullen, Melanie, Editor, Network Remote Access and Mobile Computing, Miller Freeman Inc., 1994.
- Lotus Development Corporation, Lotus Notes: The Groupware Standard—Windows, Version 3.3, 1994.
- IntelliLink Corporation, IntelliLink® For Windows User's Guide, Version 3.0, 1994.
- Lotus Development Corporation, Lotus Notes Release 4: InterNotes Web Navigator Administrator's Guide, 1995.
- Lotus Development Corporation, Lotus InterNotes Release 4 Web Publisher: InterNotes Web Publisher Guide, 1995.
- Lotus Development Corporation, Lotus Notes Release 4 Install Guide for Servers, 1995.
- Lotus Development Corporation, Lotus Notes Release 4.1 Release Note, 1995.
- Lotus Development Corporation, Lotus Notes Release 4 Migration Guide, 1995.
- Lotus Development Corporation, Lotus Notes Release 4 Database Manager's Guide, 1995.
- Lotus Development Corporation, Lotus Notes Release 4 Install Guide for Workstations, 1995.
- Lotus Development Corporation, Lotus Step by Step: A Beginner's Guide to Lotus Notes, 1995.
- Lotus Development Corporation, Lotus Notes Release 4 Programmer's Guide Part 1, 1995.
- Lotus Development Corporation, Lotus Notes Release 4 Programmer's Guide Part 2, 1995.
- Lotus Development Corporation, Lotus Notes Release 4 Administrator's guide, 1995.
- Lotus Development Corporation, Lotus Notes Release 4 Deployment Guide, 1995.
- Lotus Development Corporation, Lotus Notes Release 4 Application Developer's Guide, 1995.
- Lotus Development Corporation, Lotus Notes Release 4 InterNotes Web Navigator User's Guide, 1995.
- Lotus Development Corporation, Lotus Notes Release 4 Release Notes, 1995.
- Lotus Development Corporation, Lotus Notes Release 4.5 Install Guide for Workstaion, 1995.
- Lotus Development Corporation, Release Notes, Lotus Notes Release 3.30, Windows, OS/2, and Macintosh, 1995.
- Brown, Kevin, et al., Mastering Lotus® Notes®, SYBEX Inc., 1995.
- Lotus Development Corporation, Lotus Notes Release 4.5, Network Configuration Guide, 1995.
- Netscape Communications Corporation, Installation Guide, Netscape Mail Server, Version 2.0 for Unix, 1995.
- Netscape Communications Corporation, User's Guide, Netscape Mail Server, Version 2.0 for Unix, 1995.
Type: Grant
Filed: Mar 16, 2012
Date of Patent: Jan 20, 2015
Assignee: Seven Networks, Inc. (San Carlos, CA)
Inventors: Trevor A. Fiatal (Fremont, CA), Jay Sutaria (Los Altos Hills, CA), Sridhar Nanjundeswaran (Palo Alto, CA), Shailesh Bavadekar (Fremont, CA)
Primary Examiner: Ali Abyaneh
Application Number: 13/423,112
International Classification: H04L 29/06 (20060101);