Patent Grant
10412039
A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the U.S. Patent and Trademark Office patent files or records, but otherwise reserves all copyright rights whatsoever.
The present invention generally relates to the field of electronic messaging. In particular, the present invention is directed to an electronic message handling system and method between sending and recipient devices with separation of display of media component and header information.
Typically, an electronic message between two people is not private. It may travel along a public network, such as the Internet, and be susceptible to interception by unintended third parties. Messages are also logged and archived by the communication systems themselves. They may also be copied, cut, pasted, printed, forwarded, blind copied, or otherwise manipulated. This may give a message a “shelf-life” that is often uncontrollable by the sender or even the recipient. Surreptitious logging (e.g., by keystroke and message recording software) may occur by third parties that have gained unauthorized access to either the computer of the sender and/or the recipient. Electronic messages include the message content itself coupled to identifying information regarding the sender, the recipient, the location of the message, times and dates associated with the message, etc. This allows a third party that is logging messages, intercepting messages, or simply gaining access to the messaging system's logs or inbox archives to associate the potentially important identifying information (typically referred to as header information) with the message content. These are only some of the ways in which electronic messages can be misused. There is a demand for a system and method for reducing the traceability of electronic messages.
In one implementation, a system for reducing the traceability of electronic messaging between mobile devices is provided. The system includes a server computer configured to communicate with a first application program on a first mobile device and a second application program on a second mobile device, the server computer being an intermediate device configured to receive an electronic message with reduced traceability from the first mobile device without the use of industry standard email and to send the electronic message to the second mobile device without the use of industry standard email, the electronic message including a header information and a message content, the header information including an identifier of a recipient and the message content including an image and/or video, the first application program including instructions executable by a first processor of the first mobile device to provide a first set of reduced traceability displays via a display device of the first mobile device, the second application program including instructions executable by a second processor of the second mobile device to provide a second set of reduced traceability displays via a display device of the second mobile device, the first and second sets of reduced traceability displays being configured to reduce the traceability of the electronic message, the first set of reduced traceability displays including a first display configured to allow a user of the first mobile device to associate an image and/or video with the message content and a second display configured to allow the user of the first mobile device to associate the identifier of a recipient with the electronic message, the instructions executable by the first processor providing the first and second displays such that the identifier of the recipient is not displayed with the message content via the first display preventing a single screen capture of both the identifier of a recipient and the message content, the second set of reduced traceability displays including a third display configured to present an identifier of a sender of the electronic message and a fourth display configured to present the message content, the instructions executable by the second processor providing the third and fourth displays such that the identifier of a sending user is not displayed with the message content via the fourth display preventing a single screen capture of both the identifier of a sending user and the message content; a network connection allowing the server computer to communicate with the first mobile device to receive the electronic message and to communicate with the second mobile device to send the electronic message to the second mobile device; and a storage module associated with the server computer and configured to store the electronic message; wherein the first application program is configured to utilize a display-based keyboard to allow the user of the first mobile device to enter characters via a touchscreen screen of the first mobile device to include in the message content, and wherein the characters are included with the image and/or video of the message content if the user of the first mobile device enters the characters.
In another implementation, a system for reducing the traceability of electronic messaging between mobile devices is provided. The system includes a server computer configured to communicate with a first application program on a first mobile device and a second application program on a second mobile device, the server computer being an intermediate device configured to receive an electronic message with reduced traceability from the first mobile device without the use of industry standard email and to send the electronic message to the second mobile device without the use of industry standard email, the electronic message including a header information and a message content, the header information including an identifier of a recipient and the message content including an image and/or video, the first application program including instructions executable by a first processor of the first mobile device to provide a first set of reduced traceability displays via a display device of the first mobile device, the second application program including instructions executable by a second processor of the second mobile device to provide a second set of reduced traceability displays via a display device of the second mobile device, the first and second sets of reduced traceability displays being configured to reduce the traceability of the electronic message, the first set of reduced traceability displays including a first display configured to allow a user of the first mobile device to associate an image and/or video with the message content and a second display configured to allow the user of the first mobile device to associate the identifier of a recipient with the electronic message, the instructions executable by the first processor providing the first and second displays such that the identifier of the recipient is not displayed with the message content via the first display preventing a single screen capture of both the identifier of a recipient and the message content, the second set of reduced traceability displays including a third display configured to present an identifier of a sender of the electronic message and a fourth display configured to present the message content, the instructions executable by the second processor providing the third and fourth displays such that the identifier of a sending user is not displayed with the message content via the fourth display preventing a single screen capture of both the identifier of a sending user and the message content; a network connection allowing the server computer to communicate with the first mobile device to receive the electronic message and to communicate with the second mobile device to send the electronic message to the second mobile device; and a storage module associated with the server computer and configured to store the electronic message; wherein the first application program is configured to utilize a display-based keyboard to allow the user of the first mobile device to enter characters via a touchscreen screen of the first mobile device to include in the message content, wherein the characters are included with the image and/or video of the message content if the user of the first mobile device enters the characters, wherein if the message content is received at the server separately from the header information and/or if the message content is sent from the server separately from the header information and/or if the message content is stored separately from the header information, the server is configured to maintain a correspondence between the message content and the header information using a message ID, wherein the message ID is an alpha-numeric sequence that is unique for the electronic message for the system, the unique message ID being reusable by the system if the electronic message is deleted, wherein the message ID is separately associated with the message content and the header information, and wherein the system is configured to allow a notification message to be sent to a non-user of the system at a third-party address of a third-party messaging service.
In yet another implementation, a system for reducing the traceability of electronic messaging between mobile devices is provided. The system includes a server computer configured to communicate with a first application program on a first mobile device and a second application program on a second mobile device, the server computer being an intermediate device configured to receive an electronic message with reduced traceability from the first mobile device without the use of industry standard email and to send the electronic message to the second mobile device without the use of industry standard email, the electronic message including a header information and a message content, the header information including an identifier of a recipient and the message content including an image and/or video, the first application program including instructions executable by a first processor of the first mobile device to provide a first set of reduced traceability displays via a display device of the first mobile device, the second application program including instructions executable by a second processor of the second mobile device to provide a second set of reduced traceability displays via a display device of the second mobile device, the first and second sets of reduced traceability displays being configured to reduce the traceability of the electronic message, the first set of reduced traceability displays including a first display configured to allow a user of the first mobile device to associate an image and/or video with the message content and a second display configured to allow the user of the first mobile device to associate the identifier of a recipient with the electronic message, the instructions executable by the first processor providing the first and second displays such that the identifier of the recipient is not displayed with the message content via the first display preventing a single screen capture of both the identifier of a recipient and the message content, the second set of reduced traceability displays including a third display configured to present an identifier of a sender of the electronic message and a fourth display configured to present the message content, the instructions executable by the second processor providing the third and fourth displays such that the identifier of a sending user is not displayed with the message content via the fourth display preventing a single screen capture of both the identifier of a sending user and the message content; a network connection allowing the server computer to communicate with the first mobile device to receive the electronic message and to communicate with the second mobile device to send the electronic message to the second mobile device; and a storage module associated with the server computer and configured to store the electronic message; wherein the first application program is configured to utilize a display-based keyboard to allow the user of the first mobile device to enter characters via a touchscreen screen of the first mobile device to include in the message content, wherein the characters are included with the message content if the user of the first mobile device enters the characters, wherein if the message content is received at the server separately from the header information and/or if the message content is sent from the server separately from the header information and/or if the message content is stored separately from the header information, the server is configured to maintain a correspondence between the message content and the header information using a database, a lookup table, an entry in a file system, and/or a message ID, and wherein the first application program and/or the second application program is configured to allow a notification message that is different from the electronic message to be sent to a non-user of the system at a third-party address of a third-party messaging service.
For the purpose of illustrating the invention, the drawings show aspects of one or more embodiments of the invention. However, it should be understood that the present invention is not limited to the precise arrangements and instrumentalities shown in the drawings, wherein:
The present disclosure provides a system and method reducing traceability of an electronic message. In one embodiment, header information and message content of an electronic message are displayed by a system and method of the present disclosure so that header information and message content are not displayed at the same time. As will be clear to one skilled in the art from the disclosure below, separation of header information from message content reduces the traceability of the electronic message. To further reduce traceability of an electronic message, header information may be automatically deleted at a first predetermined time and message content may be automatically deleted at a second predetermined time (e.g., after message content is viewed). In one example, the first and second predetermined times may occur sequentially (e.g., deleting header information upon displaying message content and deleting message content upon closing a display of message content), simultaneously (e.g., deleting message content and associated header information upon closing a display of message content), or out of order such that the second predetermined time occurs before the first predetermined time (e.g., displaying message content first, deleting message content, displaying header information, then deleting header information). These and other aspects of the present disclosure will be described in greater detail below with respect to various exemplary embodiments illustrated in
Although computers 110 and 115 are illustrated as workstation computers, any well known computer may be utilized in creating and/or viewing electronic messages. Example computers include, but are not limited to, a personal computer, a workstation computer, a server computer, a laptop computer, a handheld device, a mobile telephone, a personal digital assistant (PDA), another computing device capable of communicating an electronic message via network 120, and any combinations thereof. System 100 may include one or more server computers. In one example, system 100 may reside substantially on a single server computer. In another example, system 100 may be distributed across two or more server computers. In yet another example, system 100 may be distributed across a plurality of user computers without a server computer, such as in a peer-to-peer environment. In one such example, components of a messaging system according to the present disclosure and/or their functionality (e.g., storage of header information and message content, display generation, reply generation, etc.) may occur at a recipient's user computer. In still another example, system 100 may be distributed across one or more server computers and one or more user computers. One or more relay servers or other systems may be utilized between server computers and/or user computers.
A basic input/output system 230 (BIOS), including basic routines that help to transfer information between elements within computer 200, such as during start-up, may be stored in ROM 220. Computer 200 may also include a storage/memory device 235 for reading and/or writing information. Example storage devices include, but are not limited to, a hard disk drive for reading from and/or writing to a hard disk, a magnetic disk drive for reading from and/or writing to a removable magnetic disk, an optical disk drive for reading from and/or writing to an optical media (e.g., a compact disc), and any combinations thereof. Storage/memory device 235 may be connected to bus 215 by an interface. In one example, storage/memory device 235 and associated computer-readable media provide nonvolatile storage of computer readable instructions, data structures, program modules, and/or other data for computer 200. It will be appreciated by those skilled in the art that other types of computer-readable media that can store data that is accessible by a computer in a volatile and/or non-volatile manner may also be used in an example operating environment. Examples of other types of computer-readable media include, but are not limited to, a magnetic cassette, a flash memory media (e.g., a card and a thumb-drive), a digital video disk, a Bernoulli cartridge, a random access memory (RAM), a read only memory (ROM), and any combinations thereof. A computer-readable medium, as used herein, is intended to include a single medium as well as a collection of physically separate media, such as, for example, a collection of compact disks or one or more hard disk drives in combination with a computer memory.
A number of program modules can be stored on storage/memory device 235, including, but not limited to, an operating system, one or more application programs, other program modules, program data, computer implemented instructions for carrying out the system and methodologies of the present disclosure, and any combinations thereof. A user may enter commands and information into computer 200 through one or more input devices, such as a keyboard 240 and/or a pointing device 245. Other examples of an input device include, but are not limited to a microphone, a joystick, a game pad, a satellite dish, a scanner, and any combinations thereof. These and other input devices may be connected to processing unit 205 through an interface 250 that is coupled to bus 215. Example interfaces for connecting an input device include, but are not limited to, a serial interface, a parallel interface, a game port, a universal serial bus (USB), an IEEE 1394 (Firewire) interface, a direct interface to system bus 215, and any combinations thereof.
A display device 255 may be connected to system bus 215 via an interface, such as a display generator/video adaptor 260. Example display devices include, but are not limited to, a cathode-ray tube (CRT) monitor, a plasma display, an LCD display, and any combinations thereof. In addition to a display device, a computer may include one or more other peripheral output devices, such as a speaker and a printer. A pen digitizer and an accompanying pen/stylus may be included in order to digitally capture freehand input. A pen digitizer may be separately configured or coextensive with a display area 265 of display device 255. Accordingly, a pen digitizer may be integrated with display device 255, or may exist as a separate device overlaying or otherwise appended to display device 255.
Computer 200 may include a network connection 270 for connecting to one or more of a variety of networks, such as network 120 of
Referring to
Electronic message 105 as communicated to system 100 in the example of
An electronic message may be any electronic file, data, and/or other information transmitted between one or more user computers. An electronic message may include (e.g., as part of a message content) any of a wide variety of information including, but not limited to, text, an image, video (e.g., single play video utilizing an application, such as MACROMEDIA FLASH), binary, tabular data (e.g., a spreadsheet), rich text including variable font color, tables, etc.), audio (e.g., single play audio utilizing an application, such as MACROMEDIA FLASH), other types of data, and any combinations thereof. In one example, a message content of an electronic message may include embedded information. In another example, a message content of an electronic message may include an attached and/or linked file. In such an example with an attached and/or linked file, the attached and/or linked file may be automatically deleted from the messaging system after being viewed by a recipient. Typically, a message content, such as message content 140 does not include information that in itself identifies the message sender, recipient, location of the electronic message, or time/date associated with the electronic message.
System 100 may optionally include a message ID generator 150. As described in further detail below, message ID generator 150 may generate a message ID for each electronic message received by system 100. The message ID is associated with the corresponding message. A message ID is used to associate a container (i.e., header) information with a corresponding separately-stored message content. In one example, a message ID may be created using a unique 128 bit, randomly generated number. System 100 may include a correlation between header information and message content in a variety of ways including, but not limited to, a database, a lookup table, an entry in a file system, and any combinations thereof. Utilizing a message ID associated with an electronic message, such as electronic message 105, system 100 may handle (e.g., store, deliver, display, etc.) a header information and a message content of a particular electronic message separately with the ability to correlate the two at a later time. Thus, a message content may be handled without any of the identifying header information. A message ID may contain unique and/or non-unique information. For example, a message ID may include a sequence number (e.g., 1, 2, 3, 4, etc.) identifying a number of a message amongst a group of messages. A sequence number may be re-used. For example, when an electronic message with a sequence number of “1” is viewed and subsequently deleted, sequence numbers for remaining electronic messages may be adjusted so that the electronic message having sequence number “2” is renumbered to number “1” and so forth. In another example, a message ID may include a sequence number and a unique user identifier (e.g., a user ID, a login ID, etc.).
System 100 may optionally include a reply ID generator 155. As described further below, reply ID generator 155 generates a reply ID for each electronic message received by system 100. The reply ID associates an electronic message, such as electronic message 105, with the sender of the electronic message. In one example, a reply ID may include no information that in itself would identify a sender of an electronic message to a third party that does not have access to the correlation maintained by the messaging system. System 100 may include a correlation between a reply ID and a corresponding message sender in a variety of ways, including, but not limited to, a database, a lookup table, an entry in a file system, and any combinations thereof. In one aspect, a reply ID associated with an electronic message allows the header information and/or the message content of the electronic message to include no information about the sender of the message that itself provides a traceable identity of the sender. As described in more detail below, a recipient may still send a reply electronic message to the original sender. Additionally, a third-party that may intercept, log, or otherwise come in possession of the header information and/or the message content will not be able to trace the electronic message to the sender without also gaining access to the correlation maintained by system 100. A reply ID may include a variety of different identifiers that allow a messaging system, such as system 100, to direct a reply electronic message back to a sender of the original electronic message. In one example, a reply ID may be created using a randomly generated number (e.g., a 128 bit, randomly generated number).
System 100 includes a display generator 160 in communication with electronic message storage module 130. Display generator 160 is configured to provide information representing a display image for display on a user computer, such as user computers 110, 115. Example display images include, but are not limited to, a user login display, a display listing information representing available electronic messages for viewing, a display for entering an electronic message, a display of a message content of an electronic message, a display for entering a reply electronic message, and any combinations thereof. In one example, display generator 160 may be configured to utilize a message ID in generating a first information 165 representing a first display image including at least some of the header information for electronic message 105. Display generator 160 may also be configured to generate a second information 170 representing a second display image including message content 140 of electronic message 105.
Display generator 160 may utilize any of a variety of well known display generation methodologies and/or protocols for creating information representing a displayable image. Example methodologies/protocols include, but are not limited to, hypertext markup language (HTML), extensible markup language (XML), direct graphic generation, and any combinations thereof. In one example, system 100 resides on one or more server computers and display generator 160 includes and/or utilizes a web server application to generate information representing web-browser-displayable images that may be viewed by a user computer including a web browser. In another example, display generator 160 may be configured to instruct a browser or other application of a user computer displaying a display image according to the present invention to not cache any of the information related to the display image.
System 100 may further include a deletion module 175 in communication with electronic message storage module 130. Deletion module 175 is configured to delete header information and/or message content from system 100 after a predetermined amount of time. In one example, deletion module 175 is configured to automatically delete header information and corresponding message content immediately after the message content is displayed. In another example, a deletion module (e.g., deletion module 175) is configured to automatically delete header information upon display of a corresponding message content. In yet another example, a deletion module (e.g., deletion module 175) is configured to automatically delete message content upon a display of the message content being closed. In still another example, a deletion module is configured to automatically delete header information and/or message content, whether or not they have been viewed, after a predetermined time (e.g., twenty-four hours after being received). In still yet another example, a deletion module is configured to automatically delete header information and/or message content a predetermined time (e.g., twenty-four hours) after first being displayed. In a further example, a predetermined amount of time may include a predetermined number of viewings (other than a single viewing) of a particular electronic message (e.g., an electronic message is deleted after 20 views). In still a further example, a deletion module (e.g., deletion module 175) is configured to automatically delete header information upon display of a corresponding message content and to automatically delete message content upon a display of the message content being closed. Combinations of deletion protocols, such as these examples, are also contemplated.
In an alternate embodiment, system 100 may include a display-based keyboard generator 180. Display-based keyboard generator 180 is configured to generate a display-based keyboard that may be included with a display image generated by display generator 160. A display-based keyboard can be utilized by a user (e.g., through mouse click or touch screen depression) to input information (e.g., username, password, recipient address, message content) without the use of the standard keyboard associated with the user computer. In this way interception by keyboard (keystroke) logging hardware and/or software resident on the user computer, such as computers 110, 115, can be avoided. In one example, a display-based keyboard generator may utilize FLASH technology commercially available from Macromedia Inc. In another example, a display-based keyboard generator may utilize Java technology commercially available from Sun Microsystems. In one aspect a FLASH-based keyboard may randomly place spaces between characters in the on-screen keyboard to further prevent interception of the message. Although this is a relatively slow data entry method, a user can be more assured that their information is not being logged and/or intercepted.
System 100 may also optionally include a reply message receiver 185. Reply message receiver 185 is configured to receive a reply message to one or more original electronic messages viewed by a recipient. In one aspect, a sender of an original electronic message may be determined from an identifying characteristic included, or associated, with the electronic message. Example identifying characteristics include, but are not limited to, a reply ID, an email address, a username, a display name, login ID, and any combination thereof. In one example, a reply ID of the original electronic message may be utilized in generating a reply message. In one example, a reply message as communicated by computer 115 to system 100 need only include a message content 190. System 100 may include a reply generator 195. Reply generator 195 may be configured to utilize the original reply ID to associate message content 190 and any corresponding header information with the original electronic message sending user. Message ID generator 150 may be configured to generate a message ID for the reply electronic message (i.e., message content 190 and corresponding header information). Reply ID generator 155 may be configured to generate a new reply ID for the reply message and electronic message storage module 130 may store message content 190 and corresponding header information separately for later display to the user (original sender).
Referring to
In one aspect, while a user is logged into system 300, a session may be established including the establishment of a session ID. A session and a corresponding memory may be utilized by system 300 to maintain certain information regarding the session and the user (e.g., user's identification information, a reply ID).
Upon proper login, the user may be presented with a session starting display image. One of skill in the art will appreciate that a variety of starting display images (i.e., pages) may be available for display to a user upon initial login to system 300. In one example, a display image for inputting an electronic message may be displayed.
Upon entering a recipient address (step 510 of
In an alternative embodiment, a display-based keyboard (as discussed above) may be included in an electronic message input displays, such as display images 700, 800, and 900. A user may use a mouse or other pointing device (e.g., a touchscreen display) to select characters being entered.
In an alternate embodiment, upon server 310 receiving electronic message 330, instructions associated with system 300 (e.g., instruction stored at server 310) generates a reply ID and associates the reply ID with electronic message 330 (step 525 of
In another alternate embodiment, at step 530, system 300 generates a message ID for associating the separated message content and header information of electronic message 330. Server 310 maintains a correspondence between the message content and header information.
At step 535, header information associated with electronic message 330 is identified for separation from message content 930. In one aspect, separation of information that identifies the sending user, recipient user, location of the electronic message, timing of electronic message from the message content may be implemented by associating such information with a container or header information component of the electronic message. In one example, utilization of a reply ID and a message ID can further facilitate the removal of information that itself identifies a sending user or recipient. A display name for the sending user may be generated and associated with the header information. The display name for the user need not be unique, thus maintaining the anonymity of the user when electronic message 330 is ultimately communicated to computer 320 or otherwise viewed by the recipient. In one example, system 300 replaces all information associated with electronic message 330 that could itself identify the sending user. In one embodiment, a predetermined display name for the sending user that does not provide unique identification of the sending user may be generated and associated with corresponding header information. In another example, system 300 may utilize a display name that includes information that uniquely identifies the sending user (e.g., login name, email address, etc.).
In one example, header information for a particular electronic message, such as header information, may include, but is not limited to, a reply ID, a message ID, a date/time associated with the electronic message (e.g., date/time of creation, date/time of delivery, etc.), a display name representing a sender of the electronic message, and any combinations thereof.
At step 540, an electronic message 330 is associated with a recipient represented by the recipient address. In one example, a location of the recipient is determined. As used herein, a location may include a message mailbox, a message server associated with the recipient, a computer associated with the recipient, an electronic address of the recipient, a display name for the recipient in system 300, or the like. For example, system 300 may identify a user by a variety of identities (e.g., display name, login ID, associated email address, text messaging address, instant messaging address, SMS address, mobile number, BLACKBERRY PIN, or the like) to determine a routing for electronic message 330. As discussed above, if the recipient is not a registered user of system 300, a notification may be sent to a third-party system of the existence of electronic message 330. For example, if the recipient is identified by a third-party email address, a notification may go to the email recipient over the third-party email network. Similarly, if the recipient is identified by a Blackberry PIN, a notification may go to the recipient over the Blackberry network.
At step 545, header information and message content are stored. In one example, header information and message content are stored separately from each other (e.g., in separate files, in separate databases, in separate tables, etc.). A message ID may be used to maintain a correspondence between the separated components of electronic message 330. Storage may occur in a variety of ways including, but not limited to, storage at a location of the recipient and storage at server 310. In one example, the header information and message content of electronic message 330 are stored in a storage medium of server 310 in separate tables.
In another example, each user of system 310 is assigned a storage directory (e.g., on a server, on a user computer such as in a peer-to-peer arrangement, etc.). Upon association of a user with the recipient address, the message content and header information for any electronic messages to that user may be stored in that user's storage directory. The following XML file definition illustrates an example of header information for two electronic messages stored in a user storage directory.
The above file definition includes a message ID (“streamsummary id”), a display name (“from”), date received, and reply ID for each message in the recipient's storage directory. Note that as an implementation variation, the sending user of the second message has associated therewith a display name, “user four”, which includes a reference to an email address, mike.smith@onlinemail.com. This email address may or may not be associated with an actual email account of a third-party system, and may or may not provide actual identifying information related to the sending user. The following message content XML file is stored separately in the storage directory from the above header information.
The following second message content XML file is stored separately in the storage directory from the header information.
Each of the message content XML files includes the corresponding message ID for correlation back to the corresponding header information. Each message content XML file also includes the message content. One skilled in the art would recognize other storage methodologies for separating header information from message content that are consistent with the present disclosure.
Referring again generally to
In an alternate embodiment, the header information communicated to computer 320 may include a sequence number (ex: 1, 2, 3, etc.) assigned to each electronic message associated with a particular user and/or sent to a particular computer. In such an embodiment, each sequence number may be associated in system 300 with the corresponding message ID. The message ID may be removed from the corresponding header information and/or message content. In this manner, system 300 may avoid sending a message ID to a user computer and instead may send the sequence number, which may be reused when a message is deleted and is, therefore, less traceable from the user computer.
At step 560, a user may select one of the electronic messages indicated by header information 1015, 1020, 1025 (e.g., by selecting a corresponding “read” indicator in message listing 1010). At the time of selection, the message content for each electronic message may not have been communicated to computer 320. In one example, message content may be communicated to computer 320 along with corresponding header information (but, not displayed). In another example, message content may be retained at server 310 until a second request from a user is sent to server 310 to view a message content of a particular electronic message. In such an example, computer 320 requests a message content for a selected electronic message (e.g., electronic message 330 via header information 1015) from server 310. In response to this action, server 310 may associate a message ID from the selected header information and communicate the message content having the corresponding message ID to computer 320. Alternatively, where a sequence number is utilized for each electronic message, server 310 associates the sequence number of the selected electronic message with a corresponding message content and communicates the message content to computer 320.
At step 565, a display image including the message content, but none of the header information, is provided at computer 320.
In one alternate embodiment, display image 1100 may employ FLASH technology to display the message content. For example, display image 1100 may require the user to “park” the on-screen cursor in an area in display image 1100 to see the message content, which may be displayed as a Flash movie. Should the cursor be moved, the displayed message content will be hidden from view on the screen to allow the user to quickly prevent the message content from being seen by onlookers. Also, this technology may also be utilized to prevent the message content from being printed using the web browser or application print because the message content will be hidden as soon as the user moves the mouse in attempt to print. In another example, the use of Cascading Style Sheets (CSS) may allow the portion of the display image including the message content to be not shown or hidden during printing.
Referring to
As discussed above, other examples of deletion times for deletion from a system, such as system 300, include, but are not limited to, automatic deletion of header information and corresponding message content immediately after the message content is displayed, automatic deletion of header information upon display of a corresponding message content, automatic deletion of message content upon a display of the message content being closed, automatic deletion of header information and/or message content (whether or not they have been viewed) after a predetermined time (e.g., twenty-four hours after being received), automatic deletion of header information and/or message content a predetermined time (e.g., twenty-four hours) after first being displayed, and any combinations thereof. In one example, system 300 is configured to require a given deletion scheme (e.g., automatic permanent deletion of an electronic message upon displaying the electronic message and/or one or more of its components) regardless of a desire of a sending and/or recipient user.
One example of a deletion algorithm appropriate for deletion of electronic messages from system 300 include, but is not limited to, US Department of Defense (DoD) clearing and sanitizing standard DoD 5220.22-M. In an alternative embodiment, server computer 310 may delete an electronic message, such as electronic message 330 and the corresponding reply ID from its own memory if the recipient fails to retrieve the electronic message within a predetermined amount of time.
In one example, after viewing the message content, the user may select a button 1130 on display image 1100 to return to the message listing (e.g., message listing 1010 of
In an alternative embodiment, electronic messages may be sent, stored, and/or retrieved using encryption technology. Various encryption technologies are known to those skilled in the art. For example, a combination of public and private encryption keys may be utilized by users and the system to further ensure security and reduce traceability of electronic messages until deletion.
Referring to
In one example, upon receipt of the reply message content, server 310 determines the reply ID for the original message (e.g., from the current session ID), and uses the reply ID to associate the electronic message with the user that sent the original message 330 (step 610 of
Next at step 620, the server 310 may generate another reply ID and associate the reply ID with reply message 340 in a similar fashion as discussed above for electronic message 330. Server 310 may also generate another message ID, which establishes a correlation between the message content of reply message 340 and header information for reply message 340. Header information and message content for reply message 340 are handled and stored similarly as described above with respect to electronic message 330. Reply message 340 may be viewed by its recipient in the same manner as original electronic message 330 was viewed.
Advantageously, the system 300 allows the users of the computers 315 and 320 to have a private conversation over network 325. After messages, such as electronic message 330 and reply message 340, are communicated the sender leaves no proof of the message on his or her computer. In one example, after the recipient views the message (or at another predetermined time), the message no longer exists on system 300, thus ensuring that the message cannot be forensically recreated and ensuring that there is no record of the message remaining on system 300. In another example, no copies of an electronic message are ever delivered to a user computer. In such an example, only non-caching display images of header information and message content are displayed separately. The header information and message content may be immediately, automatically, and permanently deleted from the system upon display. Once each display image is closed, the information is gone forever. Thus, in this example, there is never a copy on the user computer to be archived, forwarded, copied, pasted, etc. In another aspect, separate display of header information and message content prevents a single screen capture at a user computer from creating a complete record of the electronic message. In yet another aspect, a system and method according to the present disclosure may provide an end-to-end recordless electronic messaging system that upon the deletion of the electronic message leaves no trace of the message content, header information, or the fact that it was created, existed, delivered, viewed, etc.
As discussed above, separation of entry of header information from message content may occur via the use of a single display image screen in which the header information (such as the recipient address) and the message content are not displayed on the single display image screen at the same time. Such a single display image screen may be utilized in an electronic messaging system, such as the electronic messaging system discussed above with respect to
The display image screen and the two portions are configured so that the data representing the recipient address and the data representing the message content are not visibly displayed at the same time. Example ways to make data not visibly displayed on a display image screen include, but are not limited to, blurring the data, covering the data (e.g., with a graphical element), darkening the display of the display portion containing the data, removing the data from the display (e.g., while leaving the display image of the portion of the display on the screen), and any combinations thereof.
The timing of making the data of one portion of a display image screen not visibly displayed while data in another portion of the display image screen is visibly displayed can occur in a variety of ways. Example timings include, but are not limited to, making data of one portion not visibly displayed upon actuation of an interface control by a user (e.g., actuation of a control indicating that the entry of a recipient address is complete, indicating that the entry of a message content is complete, toggling between entry of a recipient address and a message content entry, indicating that the electronic message is ready for transmission from the computer, etc.), making data of one portion not visibly displayed upon commencing entry of data in the other portion, making data of one portion not visibly displayed upon the user stopping data entry in that portion for an amount of time (e.g., a predetermined and configured amount of time), and any combinations thereof.
In another exemplary aspect of separating the display of a recipient address from a message content on a single display image, a user can be restricted from entering data into one portion of the display image based on a variety of factors. Example factors for use in restricting entry of data into a portion (e.g., a recipient address entry portion, a message content entry portion) include, but are not limited to, restricting data entry into one portion of the display image until data is no longer visible to the user in the another portion of the display image (e.g., restricting entry of message content in the message content entry portion until the recipient address information is no longer visible in the recipient address entry portion), restricting data entry into one portion of the display image until data entered into another portion of the display image has been transmitted from the computer (e.g., restricting entry of data in a message content entry portion until a recipient address has been transmitted from the computer), and any combinations thereof. Example ways to restrict entry into a portion of a display image include, but are not limited to, blurring the entry portion (e.g., such that any information typed in the portion is not visible), covering the entry portion (e.g., with a graphical element), darkening the display of the display portion, disabling any data entry in the portion (e.g., not allowing keyboard text entry, not allowing pointing device to click into entry portion), removing the data from the display (e.g., while leaving the display image of the portion of the display on the screen), and any combinations thereof.
At step 1225, the message content is transmitted from the computer. In the example shown in
It is to be noted that the above described aspects and embodiments may be conveniently implemented using a computer programmed according to the teachings of the present specification, as will be apparent to those skilled in the computer art. Appropriate software coding can readily be prepared by skilled programmers based on the teachings of the present disclosure, as will be apparent to those skilled in the software art.
Such software can be a computer program product which employs a storage medium including stored computer code which is used to program a computer to perform the disclosed function and process of the present invention. The storage medium may include, but is not limited to, any type of conventional floppy disks, optical disks, CD-ROMs, magneto-optical disks, ROMs, RAMs, EPROMs, EEPROMs, magnetic or optical cards, or any other suitable media for storing electronic instructions. The term “computer readable medium” as used herein refers to a hardware medium and does not include a signal.
Exemplary embodiments have been disclosed above and illustrated in the accompanying drawings. It will be understood by those skilled in the art that various changes, omissions and additions may be made to that which is specifically disclosed herein without departing from the spirit and scope of the present invention.
This application is a continuation application of U.S. patent application Ser. No. 15/231,316, filed Aug. 8, 2016, and titled “Electronic Message Handling System and Method Between Sending and Recipient Devices with Display Separation,” which is a continuation application of U.S. patent application Ser. No. 15/061,351, filed Mar. 4, 2016, and titled “Electronic Message Handling System and Method Between Sending and Recipient Devices with Separation of Display of Media Component and Header Information,” which is a continuation application of U.S. patent application Ser. No. 13/447,932, filed Apr. 16, 2012, and titled “Reduced Traceability Electronic Message System and Method,” which is a continuation-in-part of U.S. patent application Ser. No. 12/605,885, filed Oct. 26, 2009, and titled “Reduced Traceability Electronic Message System and Method,” which is a continuation application of U.S. patent application Ser. No. 11/401,148, filed Apr. 10, 2006, and titled “Reduced Traceability Electronic System and Method,” each of which is incorporated by reference herein in its entirety. This application also claims the benefit of priority of U.S. Provisional Patent Application Ser. No. 60/703,367, filed Jul. 28, 2005, and titled “Method and System for Reducing Traceability of Electronic Messages,” which is incorporated by reference herein in its entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4803703 | DeLuca et al. | Feb 1989 | A |
| 5255356 | Michelman et al. | Oct 1993 | A |
| 5457454 | Sugano | Oct 1995 | A |
| 5560033 | Doherty et al. | Sep 1996 | A |
| 5598279 | Ishii et al. | Jan 1997 | A |
| 5608786 | Gordon | Mar 1997 | A |
| 5675507 | Bobo, II | Oct 1997 | A |
| 5680551 | Martino, II | Oct 1997 | A |
| 5742905 | Pepe | Apr 1998 | A |
| 5754778 | Shoujima | May 1998 | A |
| 5768503 | Olkin | Jun 1998 | A |
| 5781741 | Imamura et al. | Jul 1998 | A |
| 5801697 | Parikh et al. | Sep 1998 | A |
| 5812670 | Micali | Sep 1998 | A |
| 5848410 | Walls et al. | Dec 1998 | A |
| 5857201 | Wright, Jr. | Jan 1999 | A |
| 5870605 | Bracho | Feb 1999 | A |
| 5874960 | Mairs et al. | Feb 1999 | A |
| 5889942 | Orenshteyn | Mar 1999 | A |
| 5896301 | Barrientos | Apr 1999 | A |
| 5903472 | Barrientos | May 1999 | A |
| 5930479 | Hall | Jul 1999 | A |
| 5949348 | Kapp et al. | Sep 1999 | A |
| 5951636 | Zerber | Sep 1999 | A |
| 5956521 | Wang | Sep 1999 | A |
| 5958005 | Thorne et al. | Sep 1999 | A |
| 6006206 | Smith et al. | Dec 1999 | A |
| 6008807 | Bretschneider et al. | Dec 1999 | A |
| 6014689 | Budge et al. | Jan 2000 | A |
| 6018774 | Mayle et al. | Jan 2000 | A |
| 6018801 | Palage et al. | Jan 2000 | A |
| 6038601 | Lambert et al. | Mar 2000 | A |
| 6044395 | Costales et al. | Mar 2000 | A |
| 6071347 | Ogawa et al. | Jun 2000 | A |
| 6073174 | Montgomerie | Jun 2000 | A |
| 6076101 | Kamakura et al. | Jun 2000 | A |
| 6134432 | Holmes et al. | Oct 2000 | A |
| 6161129 | Rochkind | Dec 2000 | A |
| 6178331 | Holmes et al. | Jan 2001 | B1 |
| 6192407 | Smith et al. | Feb 2001 | B1 |
| 6209100 | Robertson et al. | Mar 2001 | B1 |
| 6223213 | Cleron et al. | Apr 2001 | B1 |
| 6233318 | Picard et al. | May 2001 | B1 |
| 6252588 | Dawson | Jun 2001 | B1 |
| 6268855 | Mairs et al. | Jul 2001 | B1 |
| 6271839 | Mairs et al. | Aug 2001 | B1 |
| 6285363 | Mairs et al. | Sep 2001 | B1 |
| 6289212 | Stein et al. | Sep 2001 | B1 |
| 6289450 | Pensak et al. | Sep 2001 | B1 |
| 6298446 | Schreiber et al. | Oct 2001 | B1 |
| 6288704 | Flack et al. | Nov 2001 | B1 |
| 6324569 | Ogilvie et al. | Nov 2001 | B1 |
| 6332164 | Jain | Dec 2001 | B1 |
| 6339825 | Pensak et al. | Jan 2002 | B2 |
| 6353892 | Schreiber et al. | Mar 2002 | B2 |
| 6357010 | Viets et al. | Mar 2002 | B1 |
| 6360252 | Rudy et al. | Mar 2002 | B1 |
| 6369908 | Frey et al. | Apr 2002 | B1 |
| 6370656 | Olarig et al. | Apr 2002 | B1 |
| 6411684 | Cohn | Jun 2002 | B1 |
| 6434702 | Maddalozzo, Jr. et al. | Aug 2002 | B1 |
| 6438594 | Bowman-Amuah | Aug 2002 | B1 |
| 6442592 | Alumbaugh | Aug 2002 | B1 |
| 6449721 | Pensak et al. | Sep 2002 | B1 |
| 6487586 | Ogilvie et al. | Nov 2002 | B2 |
| 6516416 | Gregg et al. | Feb 2003 | B2 |
| 6529500 | Pandharipande | Mar 2003 | B1 |
| 6549194 | McIntyre et al. | Apr 2003 | B1 |
| 6556586 | Sipila | Apr 2003 | B1 |
| 6563800 | Salo et al. | May 2003 | B1 |
| 6564248 | Budge et al. | May 2003 | B1 |
| 6591291 | Gabber et al. | Jul 2003 | B1 |
| 6591367 | Kobata et al. | Jul 2003 | B1 |
| 6601088 | Kelley et al. | Jul 2003 | B1 |
| 6606659 | Hegli et al. | Aug 2003 | B1 |
| 6609148 | Salo | Aug 2003 | B1 |
| 6629138 | Lambert et al. | Sep 2003 | B1 |
| 6631398 | Klein | Oct 2003 | B1 |
| 6651185 | Sauvage | Nov 2003 | B1 |
| 6671732 | Weiner | Dec 2003 | B1 |
| 6697806 | Cook | Feb 2004 | B1 |
| 6701346 | Klein | Mar 2004 | B1 |
| 6701347 | Ogilvie | Mar 2004 | B1 |
| 6711608 | Ogilvie | Mar 2004 | B1 |
| 6721784 | Leonard et al. | Apr 2004 | B1 |
| 6724370 | Dutta et al. | Apr 2004 | B2 |
| 6728714 | Doganata et al. | Apr 2004 | B1 |
| 6730863 | Gerpheide et al. | May 2004 | B1 |
| 6732150 | Thrane | May 2004 | B1 |
| 6732368 | Michael | May 2004 | B1 |
| 6741855 | Martin et al. | May 2004 | B1 |
| 6742032 | Castellani et al. | May 2004 | B1 |
| 6748422 | Morin et al. | Jun 2004 | B2 |
| 6757713 | Ogilvie et al. | Jun 2004 | B1 |
| 6779022 | Horstmann | Aug 2004 | B1 |
| 6804675 | Knight et al. | Oct 2004 | B1 |
| 6826688 | Westerman et al. | Nov 2004 | B1 |
| 6829599 | Chidlovskii | Dec 2004 | B2 |
| 6829631 | Forman et al. | Dec 2004 | B1 |
| 6832354 | Kawano et al. | Dec 2004 | B2 |
| 6834372 | Becker et al. | Dec 2004 | B1 |
| 6836846 | Kanevsky et al. | Dec 2004 | B1 |
| 6851049 | Price, III | Feb 2005 | B1 |
| 6922693 | Rubin et al. | Jul 2005 | B1 |
| 6965926 | Shapiro et al. | Nov 2005 | B1 |
| 6978376 | Giroux et al. | Dec 2005 | B2 |
| 6993662 | Rubin et al. | Jan 2006 | B2 |
| 6999565 | Delaney et al. | Feb 2006 | B1 |
| 7010566 | Jones et al. | Mar 2006 | B1 |
| 7020783 | Vange et al. | Mar 2006 | B2 |
| 7035912 | Arteaga | Apr 2006 | B2 |
| 7043563 | Vange et al. | May 2006 | B2 |
| 7054905 | Hanna et al. | May 2006 | B1 |
| 7062454 | Giannini et al. | Jun 2006 | B1 |
| 7062533 | Brown et al. | Jun 2006 | B2 |
| 7062563 | Lewis | Jun 2006 | B1 |
| 7072934 | Helgeson | Jul 2006 | B2 |
| 7076085 | Sah | Jul 2006 | B1 |
| 7076469 | Schreiber et al. | Jul 2006 | B2 |
| 7080077 | Ramamurthy | Jul 2006 | B2 |
| 7111006 | Vange et al. | Sep 2006 | B2 |
| 7113767 | Vaananen | Sep 2006 | B2 |
| 7120455 | Chen et al. | Oct 2006 | B1 |
| 7120615 | Sullivan et al. | Oct 2006 | B2 |
| 7120662 | Vange et al. | Oct 2006 | B2 |
| 7123609 | Glasser et al. | Oct 2006 | B2 |
| 7124189 | Summers | Oct 2006 | B2 |
| 7127518 | Vange et al. | Oct 2006 | B2 |
| 7130831 | Howard et al. | Oct 2006 | B2 |
| 7130885 | Chandra et al. | Oct 2006 | B2 |
| 7143195 | Vange et al. | Nov 2006 | B2 |
| 7149503 | Aarnio et al. | Dec 2006 | B2 |
| 7149893 | Leonard et al. | Dec 2006 | B1 |
| 7155539 | Vange et al. | Dec 2006 | B2 |
| 7155743 | Goodman et al. | Dec 2006 | B2 |
| 7155744 | Schreiber et al. | Dec 2006 | B2 |
| 7162014 | Skladman | Jan 2007 | B2 |
| 7162471 | Knight et al. | Jan 2007 | B1 |
| 7162508 | Messina | Jan 2007 | B2 |
| 7162649 | Ide | Jan 2007 | B1 |
| 7171620 | Castellani et al. | Jan 2007 | B2 |
| 7171693 | Tucker et al. | Jan 2007 | B2 |
| 7185359 | Schmidt et al. | Feb 2007 | B2 |
| 7185364 | Knouse et al. | Feb 2007 | B2 |
| 7191219 | Udell et al. | Mar 2007 | B2 |
| 7191252 | Redlich et al. | Mar 2007 | B2 |
| 7194547 | Moreh | Mar 2007 | B2 |
| 7194764 | Martherus et al. | Mar 2007 | B2 |
| 7200635 | Yashchin et al. | Apr 2007 | B2 |
| 7213249 | Tung Loo | May 2007 | B2 |
| 7219148 | Rounthwaite et al. | May 2007 | B2 |
| 7222157 | Sutton, Jr. et al. | May 2007 | B1 |
| 7174453 | Lu | Jun 2007 | B2 |
| 7266779 | Baek et al. | Sep 2007 | B2 |
| 7281272 | Rubin et al. | Oct 2007 | B1 |
| 7305069 | Day | Dec 2007 | B1 |
| 7305713 | Crance | Dec 2007 | B1 |
| 7334267 | Engstrom | Feb 2008 | B2 |
| 7340518 | Jenkins | Mar 2008 | B1 |
| 7356564 | Hartselle et al. | Apr 2008 | B2 |
| 7366760 | Warren et al. | Apr 2008 | B2 |
| 7386590 | Warren et al. | Jun 2008 | B2 |
| 7409425 | Naick et al. | Aug 2008 | B2 |
| 7433949 | Xu et al. | Oct 2008 | B2 |
| 7451359 | Coekaerts | Nov 2008 | B1 |
| 7496631 | Austin-Lane et al. | Feb 2009 | B2 |
| 7516183 | Shiigi | Apr 2009 | B2 |
| 7532913 | Doulton | May 2009 | B2 |
| 7539755 | Li et al. | May 2009 | B2 |
| 7562118 | Fellenstein et al. | Jul 2009 | B2 |
| 7590693 | Chan et al. | Sep 2009 | B1 |
| 7606918 | Holzman et al. | Oct 2009 | B2 |
| 7610345 | Collins et al. | Oct 2009 | B2 |
| 7620688 | Warren et al. | Nov 2009 | B2 |
| 7631336 | Diaz Perez | Dec 2009 | B2 |
| 7657759 | Rubin et al. | Feb 2010 | B2 |
| 7664956 | Goodman | Feb 2010 | B2 |
| 7669051 | Redlich et al. | Feb 2010 | B2 |
| 7676767 | Hofmeister et al. | Mar 2010 | B2 |
| 7707624 | Tomkow | Apr 2010 | B2 |
| 7730150 | Warren et al. | Jun 2010 | B2 |
| 7760662 | Maeda | Jul 2010 | B2 |
| 7765285 | Yoshida et al. | Jul 2010 | B2 |
| 7765483 | Schmieder et al. | Jul 2010 | B2 |
| 7774414 | Shah | Aug 2010 | B2 |
| 7783715 | Muller | Aug 2010 | B2 |
| 7802161 | Sohn et al. | Sep 2010 | B2 |
| 7814158 | Malik | Oct 2010 | B2 |
| 7836301 | Harris | Nov 2010 | B2 |
| 7860932 | Fried | Dec 2010 | B2 |
| 7865394 | Calloway et al. | Jan 2011 | B1 |
| 7899872 | Warren et al. | Mar 2011 | B2 |
| 7962654 | Vange et al. | Jun 2011 | B2 |
| 7966376 | Kelso et al. | Jun 2011 | B2 |
| 7975066 | Vange et al. | Jul 2011 | B2 |
| 8103724 | Dawson et al. | Jan 2012 | B2 |
| 8145715 | Henry et al. | Mar 2012 | B2 |
| 8171286 | Harris | May 2012 | B2 |
| 8200971 | Edwards | Jun 2012 | B2 |
| 8255465 | Edwards | Aug 2012 | B2 |
| 8291026 | Collins et al. | Oct 2012 | B2 |
| 8364764 | Hartselle et al. | Jan 2013 | B2 |
| 8386641 | Vange et al. | Feb 2013 | B2 |
| 8417770 | Vange et al. | Apr 2013 | B2 |
| 8463935 | Vange et al. | Jun 2013 | B2 |
| 8484706 | Tomkow | Jul 2013 | B2 |
| 8504080 | Jo et al. | Aug 2013 | B2 |
| 8650256 | Chakra et al. | Feb 2014 | B2 |
| 8725809 | Hartselle et al. | May 2014 | B2 |
| 8886739 | Collins et al. | Nov 2014 | B2 |
| 8935351 | Collins et al. | Jan 2015 | B2 |
| 9100355 | Tomkow | Aug 2015 | B2 |
| 9147050 | Park et al. | Sep 2015 | B2 |
| 9282081 | Collins et al. | Mar 2016 | B2 |
| 9304957 | Shimmoto | Apr 2016 | B2 |
| 9306885 | Collins et al. | Apr 2016 | B2 |
| 9306886 | Collins et al. | Apr 2016 | B2 |
| 9313155 | Collins et al. | Apr 2016 | B2 |
| 9313156 | Collins et al. | Apr 2016 | B2 |
| 9313157 | Collins et al. | Apr 2016 | B2 |
| 9338111 | Collins et al. | May 2016 | B2 |
| 9413711 | Collins et al. | Aug 2016 | B2 |
| 20010000265 | Schreiber et al. | Apr 2001 | A1 |
| 20010000359 | Schreiber et al. | Apr 2001 | A1 |
| 20010000541 | Schreiber et al. | Apr 2001 | A1 |
| 20010006551 | Masaki | Jul 2001 | A1 |
| 20010011262 | Hoyt et al. | Aug 2001 | A1 |
| 20010032246 | Fardella et al. | Oct 2001 | A1 |
| 20010034791 | Clubb et al. | Oct 2001 | A1 |
| 20010037316 | Shiloh | Nov 2001 | A1 |
| 20010044831 | Yamazaki | Nov 2001 | A1 |
| 20020002602 | Vange et al. | Jan 2002 | A1 |
| 20020002603 | Vange | Jan 2002 | A1 |
| 20020002611 | Vange | Jan 2002 | A1 |
| 20020002618 | Vange | Jan 2002 | A1 |
| 20020002622 | Vange et al. | Jan 2002 | A1 |
| 20020002625 | Vange et al. | Jan 2002 | A1 |
| 20020002636 | Vange et al. | Jan 2002 | A1 |
| 20020002686 | Vange et al. | Jan 2002 | A1 |
| 20020002688 | Gregg et al. | Jan 2002 | A1 |
| 20020004796 | Vange et al. | Jan 2002 | A1 |
| 20020004816 | Vange et al. | Jan 2002 | A1 |
| 20020016918 | Tucker et al. | Feb 2002 | A1 |
| 20020019853 | Vange et al. | Feb 2002 | A1 |
| 20020023159 | Vange et al. | Feb 2002 | A1 |
| 20020024506 | Flack et al. | Feb 2002 | A1 |
| 20020026487 | Ogilvie et al. | Feb 2002 | A1 |
| 20020026495 | Arteaga | Feb 2002 | A1 |
| 20020029248 | Cook et al. | Mar 2002 | A1 |
| 20020029249 | Campbell et al. | Mar 2002 | A1 |
| 20020032742 | Anderson | Mar 2002 | A1 |
| 20020049749 | Helgeson | Apr 2002 | A1 |
| 20020054120 | Kawano et al. | May 2002 | A1 |
| 20020056006 | Vange et al. | May 2002 | A1 |
| 20020059170 | Vange | May 2002 | A1 |
| 20020059381 | Cook et al. | May 2002 | A1 |
| 20020065892 | Malik | May 2002 | A1 |
| 20020069365 | Howard et al. | Jun 2002 | A1 |
| 20020078343 | Rubin et al. | Jun 2002 | A1 |
| 20020078361 | Giroux et al. | Jun 2002 | A1 |
| 20020083016 | Dittrich et al. | Jun 2002 | A1 |
| 20020087720 | Davis et al. | Jul 2002 | A1 |
| 20020091745 | Ramamurthy | Jul 2002 | A1 |
| 20020091775 | Morehead et al. | Jul 2002 | A1 |
| 20020095399 | Devine | Jul 2002 | A1 |
| 20020098831 | Castell et al. | Jul 2002 | A1 |
| 20020099826 | Summers | Jul 2002 | A1 |
| 20020107950 | Lu | Aug 2002 | A1 |
| 20020112005 | Namias | Aug 2002 | A1 |
| 20020112155 | Martherus et al. | Aug 2002 | A1 |
| 20020120646 | Dutta et al. | Aug 2002 | A1 |
| 20020120869 | Engstrom | Aug 2002 | A1 |
| 20020129140 | Peled et al. | Sep 2002 | A1 |
| 20020138582 | Chandra et al. | Sep 2002 | A1 |
| 20020143865 | Tung Loo | Oct 2002 | A1 |
| 20020149569 | Dutta et al. | Oct 2002 | A1 |
| 20020180788 | Wu | Dec 2002 | A1 |
| 20020184322 | Simpson et al. | Dec 2002 | A1 |
| 20020194470 | Grupe | Dec 2002 | A1 |
| 20030009672 | Goodman | Jan 2003 | A1 |
| 20030023580 | Braud et al. | Jan 2003 | A1 |
| 20030023695 | Kobata et al. | Jan 2003 | A1 |
| 20030028809 | Goodman et al. | Feb 2003 | A1 |
| 20030038835 | DeFelice | Feb 2003 | A1 |
| 20030050046 | Conneely et al. | Mar 2003 | A1 |
| 20030051054 | Redlich et al. | Mar 2003 | A1 |
| 20030054810 | Chen et al. | Mar 2003 | A1 |
| 20030055897 | Brown et al. | Mar 2003 | A1 |
| 20030061215 | Messina | Mar 2003 | A1 |
| 20030074248 | Braud | Apr 2003 | A1 |
| 20030074397 | Morin et al. | Apr 2003 | A1 |
| 20030074552 | Olkin et al. | Apr 2003 | A1 |
| 20030074580 | Knouse et al. | Apr 2003 | A1 |
| 20030078890 | Schmidt et al. | Apr 2003 | A1 |
| 20030100292 | Kynast et al. | May 2003 | A1 |
| 20030120948 | Schmidt et al. | Jun 2003 | A1 |
| 20030122922 | Saffer et al. | Jul 2003 | A1 |
| 20030126215 | Udell et al. | Jul 2003 | A1 |
| 20030126259 | Yoshida et al. | Jul 2003 | A1 |
| 20030131055 | Yashchin et al. | Jul 2003 | A1 |
| 20030131060 | Hartselle et al. | Jul 2003 | A1 |
| 20030147378 | Glasser et al. | Aug 2003 | A1 |
| 20030149737 | Lambert et al. | Aug 2003 | A1 |
| 20030152203 | Berger et al. | Aug 2003 | A1 |
| 20030154249 | Crockett et al. | Aug 2003 | A1 |
| 20030154292 | Spriestersbach et al. | Aug 2003 | A1 |
| 20030163538 | Yeh et al. | Aug 2003 | A1 |
| 20030167350 | Davis et al. | Sep 2003 | A1 |
| 20030224810 | Enzmann et al. | Dec 2003 | A1 |
| 20040002903 | Stolfo et al. | Jan 2004 | A1 |
| 20040014456 | Vaananen | Jan 2004 | A1 |
| 20040015729 | Elms et al. | Jan 2004 | A1 |
| 20040019644 | Fellenstein et al. | Jan 2004 | A1 |
| 20040019846 | Castellani et al. | Jan 2004 | A1 |
| 20040024788 | Hill et al. | Feb 2004 | A1 |
| 20040024890 | Baek et al. | Feb 2004 | A1 |
| 20040030918 | Karamchedu et al. | Feb 2004 | A1 |
| 20040049436 | Brand et al. | Mar 2004 | A1 |
| 20040051736 | Daniell | Mar 2004 | A1 |
| 20040051897 | Kakiuchi et al. | Mar 2004 | A1 |
| 20040059790 | Austin-Lane et al. | Mar 2004 | A1 |
| 20040068486 | Chidlovskii | Apr 2004 | A1 |
| 20040121762 | Chou | Jun 2004 | A1 |
| 20040133599 | Warren et al. | Jul 2004 | A1 |
| 20040133643 | Warren et al. | Jul 2004 | A1 |
| 20040133644 | Warren et al. | Jul 2004 | A1 |
| 20040177110 | Rounthwaite et al. | Sep 2004 | A1 |
| 20040188151 | Gerpheide et al. | Sep 2004 | A1 |
| 20040189616 | Gerpheide et al. | Sep 2004 | A1 |
| 20040189617 | Gerpheide et al. | Sep 2004 | A1 |
| 20040193591 | Winter | Sep 2004 | A1 |
| 20040193695 | Salo | Sep 2004 | A1 |
| 20040210632 | Carlson et al. | Oct 2004 | A1 |
| 20040210796 | Largman et al. | Oct 2004 | A1 |
| 20040218047 | Goodman et al. | Nov 2004 | A1 |
| 20040230657 | Tomkow | Nov 2004 | A1 |
| 20040234046 | Skladman | Nov 2004 | A1 |
| 20040243679 | Tyler | Dec 2004 | A1 |
| 20040249892 | Barriga et al. | Dec 2004 | A1 |
| 20040249899 | Shiigi | Dec 2004 | A1 |
| 20050010643 | Fellenstein et al. | Jan 2005 | A1 |
| 20050014493 | Ford | Jan 2005 | A1 |
| 20050021803 | Wren, III | Jan 2005 | A1 |
| 20050027846 | Wolfe et al. | Feb 2005 | A1 |
| 20050064883 | Heck | Mar 2005 | A1 |
| 20050071178 | Beckstrom et al. | Mar 2005 | A1 |
| 20050071282 | Lu et al. | Mar 2005 | A1 |
| 20050086186 | Sullivan et al. | Apr 2005 | A1 |
| 20050086527 | Jackson | Apr 2005 | A1 |
| 20050091501 | Osthoff et al. | Apr 2005 | A1 |
| 20050108335 | Naick et al. | May 2005 | A1 |
| 20050120230 | Waterson | Jun 2005 | A1 |
| 20050130631 | Maguire | Jun 2005 | A1 |
| 20050132010 | Muller | Jun 2005 | A1 |
| 20050132013 | Karstens | Jun 2005 | A1 |
| 20050132372 | Vargas et al. | Jun 2005 | A1 |
| 20050136886 | Aarnio et al. | Jun 2005 | A1 |
| 20050136953 | Jo et al. | Jun 2005 | A1 |
| 20050138110 | Redlich et al. | Jun 2005 | A1 |
| 20050144246 | Malik | Jun 2005 | A1 |
| 20050193068 | Brown et al. | Sep 2005 | A1 |
| 20050198365 | Wei | Sep 2005 | A1 |
| 20050204005 | Purcell et al. | Sep 2005 | A1 |
| 20050204008 | Shinbrood | Sep 2005 | A1 |
| 20050204130 | Harris | Sep 2005 | A1 |
| 20050209903 | Hunter et al. | Sep 2005 | A1 |
| 20050229258 | Pigin | Oct 2005 | A1 |
| 20050239447 | Holzman et al. | Oct 2005 | A1 |
| 20050240666 | Xu et al. | Oct 2005 | A1 |
| 20050240759 | Rubin et al. | Oct 2005 | A1 |
| 20050251399 | Agarwal et al. | Nov 2005 | A1 |
| 20050256929 | Bartol et al. | Nov 2005 | A1 |
| 20050266836 | Shan | Dec 2005 | A1 |
| 20050277431 | White | Dec 2005 | A1 |
| 20050283621 | Sato et al. | Dec 2005 | A1 |
| 20050289601 | Park et al. | Dec 2005 | A1 |
| 20060002315 | Theurer et al. | Jan 2006 | A1 |
| 20060010215 | Clegg et al. | Jan 2006 | A1 |
| 20060020714 | Girouard et al. | Jan 2006 | A1 |
| 20060031300 | Kock et al. | Feb 2006 | A1 |
| 20060031483 | Lund et al. | Feb 2006 | A1 |
| 20060041751 | Rogers et al. | Feb 2006 | A1 |
| 20060046758 | Emami-Nouri | Mar 2006 | A1 |
| 20060047748 | Kelso et al. | Mar 2006 | A1 |
| 20060075473 | Moreh | Apr 2006 | A1 |
| 20060095502 | Lewis et al. | May 2006 | A1 |
| 20060129697 | Vange et al. | Jun 2006 | A1 |
| 20060129823 | McCarthy et al. | Jun 2006 | A1 |
| 20060140347 | Kaji | Jun 2006 | A1 |
| 20060149822 | Henry et al. | Jul 2006 | A1 |
| 20060168058 | Midgley | Jul 2006 | A1 |
| 20060177007 | Vaghar | Aug 2006 | A1 |
| 20060208871 | Hansen | Sep 2006 | A1 |
| 20060212561 | Feng | Sep 2006 | A1 |
| 20060217126 | Sohm et al. | Sep 2006 | A1 |
| 20060223554 | Fried | Oct 2006 | A1 |
| 20060229899 | Hyder et al. | Oct 2006 | A1 |
| 20060234680 | Doulton | Oct 2006 | A1 |
| 20060235824 | Cheung et al. | Oct 2006 | A1 |
| 20060236095 | Smith | Oct 2006 | A1 |
| 20060248599 | Sack | Nov 2006 | A1 |
| 20060259492 | Jun et al. | Nov 2006 | A1 |
| 20060265453 | Kaminsky et al. | Nov 2006 | A1 |
| 20060282426 | Spears | Dec 2006 | A1 |
| 20060282738 | Sohn et al. | Dec 2006 | A1 |
| 20060284852 | Hofmeister et al. | Dec 2006 | A1 |
| 20070013662 | Fauth | Jan 2007 | A1 |
| 20070038715 | Collins et al. | Feb 2007 | A1 |
| 20070061399 | Schmieder et al. | Mar 2007 | A1 |
| 20070063999 | Park | Mar 2007 | A1 |
| 20070071222 | Flockhart et al. | Mar 2007 | A1 |
| 20070074018 | Edwards | Mar 2007 | A1 |
| 20070077921 | Hayashi et al. | Apr 2007 | A1 |
| 20070078675 | Kaplan | Apr 2007 | A1 |
| 20070083675 | Vemulapelli et al. | Apr 2007 | A1 |
| 20070083929 | Sprosts et al. | Apr 2007 | A1 |
| 20070101415 | Masui | May 2007 | A1 |
| 20070113287 | Blumenau | May 2007 | A1 |
| 20070113288 | Blumenau | May 2007 | A1 |
| 20070113289 | Blumenau | May 2007 | A1 |
| 20070113293 | Blumenau | May 2007 | A1 |
| 20070116001 | Kobayashi et al. | May 2007 | A1 |
| 20070130329 | Shah | Jun 2007 | A1 |
| 20070133034 | Jindal et al. | Jun 2007 | A1 |
| 20070136428 | Boutboul et al. | Jun 2007 | A1 |
| 20070143423 | Kieselbach et al. | Jun 2007 | A1 |
| 20070157252 | Diaz Perez | Jul 2007 | A1 |
| 20070177568 | Clontz et al. | Aug 2007 | A1 |
| 20070217393 | Lee et al. | Sep 2007 | A1 |
| 20070233790 | Agarwal et al. | Oct 2007 | A1 |
| 20070250619 | Li et al. | Oct 2007 | A1 |
| 20080010348 | Dawson et al. | Jan 2008 | A1 |
| 20080077704 | Shah et al. | Mar 2008 | A1 |
| 20080126496 | Warren et al. | May 2008 | A1 |
| 20080172468 | Almeida | Jul 2008 | A1 |
| 20080201440 | Shah et al. | Aug 2008 | A1 |
| 20080208998 | Warren et al. | Aug 2008 | A1 |
| 20080281930 | Hartselle et al. | Nov 2008 | A1 |
| 20080313296 | Muller | Dec 2008 | A1 |
| 20080320092 | Campbell et al. | Dec 2008 | A1 |
| 20090116492 | Maeda | May 2009 | A1 |
| 20090150758 | Gejdos et al. | Jun 2009 | A1 |
| 20090150771 | Buck et al. | Jun 2009 | A1 |
| 20090228557 | Ganz et al. | Sep 2009 | A1 |
| 20090254994 | Waterson | Oct 2009 | A1 |
| 20090311996 | Furuta | Dec 2009 | A1 |
| 20100058118 | Yamaoka | Mar 2010 | A1 |
| 20100064016 | Collins et al. | Mar 2010 | A1 |
| 20100077360 | Nason et al. | Mar 2010 | A1 |
| 20100082979 | Edwards | Apr 2010 | A1 |
| 20100131868 | Chawla et al. | May 2010 | A1 |
| 20100157998 | Vange et al. | Jun 2010 | A1 |
| 20100161743 | Krishnamurthi et al. | Jun 2010 | A1 |
| 20100161747 | Rayan et al. | Jun 2010 | A1 |
| 20100223338 | Hodes | Sep 2010 | A1 |
| 20100235892 | Tomkow | Sep 2010 | A1 |
| 20110030052 | Harris | Feb 2011 | A1 |
| 20110055334 | Tivyan | Mar 2011 | A1 |
| 20110061099 | Jiang et al. | Mar 2011 | A1 |
| 20110081923 | Forutanpour et al. | Apr 2011 | A1 |
| 20110083111 | Forutanpour et al. | Apr 2011 | A1 |
| 20110161448 | Warren et al. | Jun 2011 | A1 |
| 20110238860 | Vange et al. | Sep 2011 | A1 |
| 20110246665 | Vange et al. | Oct 2011 | A1 |
| 20110252161 | Ranney | Oct 2011 | A1 |
| 20110302321 | Vange et al. | Dec 2011 | A1 |
| 20120036147 | Borst et al. | Feb 2012 | A1 |
| 20120036452 | Coleman et al. | Feb 2012 | A1 |
| 20120054308 | Vange et al. | Mar 2012 | A1 |
| 20120059907 | Vange et al. | Mar 2012 | A1 |
| 20120114108 | Katis et al. | May 2012 | A1 |
| 20120203849 | Collins et al. | Aug 2012 | A1 |
| 20120226913 | Park et al. | Sep 2012 | A1 |
| 20120271619 | Abdel-Kader | Oct 2012 | A1 |
| 20130097248 | Chakra et al. | Apr 2013 | A1 |
| 20130159436 | Hartselle et al. | Jun 2013 | A1 |
| 20130166792 | Shimmoto | Jun 2013 | A1 |
| 20130290443 | Collins et al. | Oct 2013 | A1 |
| 20140074981 | Vange et al. | Mar 2014 | A1 |
| 20140115074 | Tomkow | Apr 2014 | A1 |
| 20140133656 | Wurster et al. | May 2014 | A1 |
| 20140181689 | Collins et al. | Jun 2014 | A1 |
| 20140201295 | Collins et al. | Jul 2014 | A1 |
| 20140201527 | Krivorot | Jul 2014 | A1 |
| 20140207887 | Hartselle et al. | Jul 2014 | A1 |
| 20150100657 | Collins et al. | Apr 2015 | A1 |
| 20150106459 | Collins et al. | Apr 2015 | A1 |
| 20150106460 | Collins et al. | Apr 2015 | A1 |
| 20150106461 | Collins et al. | Apr 2015 | A1 |
| 20150106743 | Collins et al. | Apr 2015 | A1 |
| 20150106744 | Collins et al. | Apr 2015 | A1 |
| 20150237021 | Sovio et al. | Aug 2015 | A1 |
| 20150248557 | Sallam | Sep 2015 | A1 |
| 20160191452 | Collins et al. | Jun 2016 | A1 |
| Number | Date | Country |
|---|---|---|
| 102004031677 | Jan 2006 | DE |
| 899918 | Mar 1999 | EP |
| 918420 | May 1999 | EP |
| 994608 | Apr 2000 | EP |
| 1113631 | Apr 2001 | EP |
| 1388986 | Feb 2004 | EP |
| 2430591 | Mar 2007 | GB |
| H11-163923 | Jun 1999 | JP |
| 200010879 | Jan 2000 | JP |
| 2003114852 | Apr 2003 | JP |
| 2004038407 | Feb 2004 | JP |
| 2004126973 | Apr 2004 | JP |
| 2004341813 | Dec 2004 | JP |
| 1998059456 | Dec 1998 | WO |
| 2000058850 | Oct 2000 | WO |
| 2001075651 | Oct 2001 | WO |
| 2003005636 | Jan 2003 | WO |
| 2004095814 | Nov 2004 | WO |
| 2006088915 | Aug 2006 | WO |
| 2006114135 | Nov 2006 | WO |
| 2007018636 | Feb 2007 | WO |
| 2008036971 | Mar 2008 | WO |
| 2008101165 | Aug 2008 | WO |
| 2010151873 | Dec 2010 | WO |
| 2013158603 | Oct 2013 | WO |
| 2013158764 | Oct 2013 | WO |
| 2014047489 | Mar 2014 | WO |
| Entry |
|---|
| U.S. Appl. No. 15/149,371, Jul. 6, 2018, Office Action. |
| U.S. Appl. No. 15/149,371, Jan. 7, 2019, Response to Office Action. |
| U.S. Appl. No. 15/149,371, Feb. 6, 2019, Notice of Allowance. |
| U.S. Appl. No. 15/231,316, Sep. 17, 2018, Office Action. |
| U.S. Pat. No. 8,935,351, Dec. 27, 2017, IPR2018-00404, Jul. 10, 2018. |
| U.S. Pat. No. 9,313,157, Jan. 10, 2018, IPR2018-00455, Aug. 31, 2018. |
| U.S. Pat. No. 9,306,886, Dec. 26, 2017, IPR2018-00397, Jul. 10, 2018. |
| U.S. Pat. No. 9,338,111, Dec. 29, 2017, IPR2018-00408, Jul. 10, 2018. |
| U.S. Pat. No. 8,886,739, Nov. 16, 2017, IPR2018-00200, Jun. 6, 2018. |
| U.S. Pat. No. 9,313,155, Dec. 21, 2017, IPR2018-00369, Jul. 10, 2018. |
| U.S. Pat. No. 9,313,156, Jan. 10, 2018, IPR2018-00458, Aug. 31, 2018. |
| U.S. Pat. No. 9,306,885, Dec. 14, 2017, IPR2018-00312, Jun. 18, 2018. |
| U.S. Pat. No. 9,413,711, Dec. 31, 2017, IPR2018-00416, Aug. 8, 2018. |
| U.S. Pat. No. 9,413,711, Jan. 9, 2018, IPR2018-00439, Aug. 2, 2018. |
| Claim Construction Order from Related Trial Court Case 2:17-cv-00220-MLH (KSx) Submitted as Exhibit to Patent Owner's Preliminary Response in Mulitple Inter Partes Review, Feb. 27, 2018, IPR2018-00404 IPR2018-00200 IPR2018-00369 IPR2018-00458 IPR2018-00312 IPR2018-00455 IPR2018-00397 IPR2018-00408 IPR2018-00416 IPR2018-00439, U.S. Pat. No. 8,935,351 U.S. Pat. No. 8,886,739 U.S. Pat. No. 9,313,155 U.S. Pat. No. 9,313,156 U.S. Pat. No. 9,306,885 U.S. Pat. No. 9,313,157 U.S. Pat. No. 9,306,886 U.S. Pat. No. 9,338,111 U.S. Pat. No. 9,413,711 U.S. Pat. No. 9,413,711. |
| Transcript of Deposition of Sandeep Chatterjee (Petitioner Expert) Taken on Sep. 26, 2018 and Submitted with Patent Owner's Response in Multiple Inter Partes Review Proceedings, Sep. 26, 2018, IPR2018-00404 IPR2018-00200 IPR2018-00369 IPR2018-00458 IPR2018-00312 IPR2018-00455 IPR2018-00397 IPR2018-00408 IPR2018-00416 IPR2018-00439, U.S. Pat. No. 8,935,351 U.S. Pat. No. 8,886,739 U.S. Pat. No. 9,313,155 U.S. Pat. No. 9,313,156 U.S. Pat. No. 9,306,885 U.S. Pat. No. 9,313,157 U.S. Pat. No. 9,306,886 U.S. Pat. No. 9,338,111 U.S. Pat. No. 9,413,711 U.S. Pat. No. 9,413,711. |
| Transcript of Deposition of Kevin C. Almeroth (Patent Owner Expert) Taken on Jan. 21, 2019 and Submitted with Petitioner's Reply in Multiple Inter Partes Review Proceeings (Part 1 of 2), Jan. 21, 2019, IPR2018-00404 IPR2018-00200 IPR2018-00369 IPR2018-00458 IPR2018-00312 IPR2018-00455 IPR2018-00397 IPR2018-00408 IPR2018-00416 IPR2018-00439, U.S. Pat. No. 8,935,351 U.S. Pat. No. 8,886,739 U.S. Pat. No. 9,313,155 U.S. Pat. No. 9,313,156 U.S. Pat. No. 9,306,885 U.S. Pat. No. 9,313,157 U.S. Pat. No. 9,306,886 U.S. Pat. No. 9,338,111 U.S. Pat. No. 9,413,711 U.S. Pat. No. 9,413,711. |
| Transcript of Deposition of Kevin C. Almeroth (Patent Owner Expert) Taken on Jan. 22, 2019 and Submitted with Petitioner's Reply in Multiple Inter Partes Review Proceedings (Part 2 of 2), Jan. 21, 2019, IPR2018-00404 IPR2018-00200 IPR2018-00369 IPR2018-00458 IPR2018-00312 IPR2018-00455 IPR2018-00397 IPR2018-00408 IPR2018-00416 IPR2018-00439, U.S. Pat. No. 8,935,351 U.S. Pat. No. 8,886,739 U.S. Pat. No. 9,313,155 U.S. Pat. No. 9,313,156 U.S. Pat. No. 9,306,885 U.S. Pat. No. 9,313,157 U.S. Pat. No. 9,306,886 U.S. Pat. No. 9,338,111 U.S. Pat. No. 9,413,711 U.S. Pat. No. 9,413,711. |
| Transcript of Deposition of Kevin C. Almeroth (Patent Owner Expert) Taken on Apr. 4, 2019 and Submitted with Petitioner's Sur-reply to, Apr. 4, 2019, IPR2018-00458 IPR2018-00455 IPR2018-00439, U.S. Pat. No. 9,313,156 U.S. Pat. No. 9,313,157 U.S. Pat. No. 9,413,711. |
| Patent Owner's Demonstrative Sides for Mar. 27, 2019 Oral Hearing in Inter Partes Review (Slides 1 to 61), Mar. 27, 2019, IPR2018-00404 IPR2018-00397 IPR2018-00408, U.S. Pat. No. 8,935,351 U.S. Pat. No. 9,306,886 U.S. Pat. No. 9,338,111. |
| Patent Owner's Demonstrative slides for Mar. 27, 2019 Oral Hearing in Inter Partes Review (slides 62 to 105), Mar. 27, 2019, IPR2018-00200 IPR2018-00369 IPR2018-00312, U.S. Pat. No. 8,886,739 U.S. Pat. No. 9,313,155 U.S. Pat. No. 9,306,885. |
| Patent Owner's Demonstrative Slides for Mar. 27, 2019 Oral Hearing in Inter Partes Review (Slides 106 to 149), Mar. 27, 2019, IPR2018-00200 IPR2018-00369 IPR2018-00312, U.S. Pat. No. 8,886,739 U.S. Pat. No. 9,313,155 U.S. Pat. No. 9,306,885. |
| Patent Owner's Demonstrative Slides for Mar. 27, 2019 Oral Hearing in Inter Partes Review (Slides 150 to 185), Mar. 27, 2019, IPR2018-00200 IPR2018-00369 IPR2018-00312, U.S. Pat. No. 8,886,739 U.S. Pat. No. 9,313,155 U.S. Pat. No. 9,306,885. |
| Petitioner's Demonstrative Slides for Mar. 27, 2019 Oral Hearing in Inter Partes Review, Mar. 27, 2019, IPR2018-00404 IPR2018-00200 IPR2018-00369 IPR2018-00312 IPR2018-00397 IPR2018-00408, U.S. Pat. No. 8,935,351 U.S. Pat. No. 8,886,739 U.S. Pat. No. 9,313,155 U.S. Pat. No. 9,306,885 U.S. Pat. No. 9,306,886 U.S. Pat. No. 9,338,111. |
| Petitioner's Demonstrative Slides for Apr. 17, 2019 Oral Hearing in Inter Partes Review, Apr. 17, 2019, IPR2018-00458 IPR2018-00455 IPR2018-00416 IPR2018-00439, U.S. Pat. No. 9,313,156 U.S. Pat. No. 9,313,157 U.S. Pat. No. 9,413,711 U.S. Pat. No. 9,413,711. |
| Patent Owner's Demonstrative Slides for Apr. 17, 2019 Oral Hearing in Inter Partes Review (Slides 1 to 50), Apr. 17, 2019, IPR2018-00458 IPR2018-00455 IPR2018-00416 IPR2018-00439, U.S. Pat. No. 9,313,156 U.S. Pat. No. 9,313,157 U.S. Pat. No. 9,413,711 U.S. Pat. No. 9,413,711. |
| Patent Owner's Demonstrative Slides for Apr. 17, 2019 Oral Hearing in Inter Partes Review (Slides 51 to 99), Apr. 17, 2019, IPR2018-00458 IPR2018-00455 IPR2018-00416 IPR2018-00439, U.S. Pat. No. 9,313,156 U.S. Pat. No. 9,313,157 U.S. Pat. No. 9,413,711 U.S. Pat. No. 9,413,711. |
| Petition for Inter Partes Review, Dec. 27, 2017, IPR2018-00404, U.S. Pat. No. 8,935,351. |
| Declaration of Sandeep Chatterjee Submitted with Petitioner's Petition for Inter Partes Review, Dec. 27, 2017, IPR2018-00404, U.S. Pat. No. 8,935,351. |
| Patent Owner's Preliminary Response in Inter Partes Review, Apr. 11, 2018, IPR2018-00404, U.S. Pat. No. 8,935,351. |
| Declaration of Michael Shamos in Opposition to Petition for Inter Partes Review, Apr. 11, 2018, IPR2018-00404, U.S. Pat. No. 8,935,351. |
| Decision Institution of Inter Partes Review, Jul. 10, 2018, IPR2018-00404, U.S. Pat. No. 8,935,351. |
| Patent Owner's Response in Inter Partes Review, Oct. 12, 2018, IPR2018-00404, U.S. Pat. No. 8,935,351. |
| Declaration of Kevin C. Almeroth (Patent Owner Expert) Submitted with Patent Owner's Response in Inter Partes Review, Oct. 12, 2018, IPR2018-00404, U.S. Pat. No. 8,935,351. |
| Petitioner's Reply in Inter Partes Review, Jan. 31, 2019, IPR2018-00404, U.S. Pat. No. 8,935,351. |
| Declaration of Sandeep Chatterjee Submitted with Petitioner's Reply in Inter Partes Review, Jan. 31, 2019, IPR2018-00404, U.S. Pat. No. 8,935,351. |
| Patent Owner's Sur-Reply in Inter Partes Review, Feb. 28, 2019, IPR2018-00404, U.S. Pat. No. 8,935,351. |
| Petition for Inter Partes Review, Jan. 10, 2018, IPR2018-00455, U.S. Pat. No. 9,313,157. |
| Declaration of Sandeep Chatterjee Submitted with Petitioner's Petition for Inter Partes Review, Jan. 10, 2018, IPR2018-00455, U.S. Pat. No. 9,313,157. |
| Patent Owner's Preliminary Response in Inter Partes Review, Jun. 8, 2018, IPR2018-00455, U.S. Pat. No. 9,313,157. |
| Declaration of Michael Shamos in Opposition to Petition for Inter Partes Review, Jun. 8, 2018, IPR2018-00455, U.S. Pat. No. 9,313,157. |
| Decision Institution of Inter Partes Review, Aug. 31, 2018, IPR2018-00455, U.S. Pat. No. 9,313,157. |
| Patent Owner's Response in Inter Partes Review, Nov. 13, 2018, IPR2018-00455, U.S. Pat. No. 9,313,157. |
| Patent Owner's Motion to Amend in Inter Partes Review, Nov. 13, 2018, IPR2018-00455, U.S. Pat. No. 9,313,157. |
| Declaration of Kevin C. Almeroth (Patent Owner Expert) Submitted with Patent Owner's Response in Inter Partes Review, Nov. 13, 2018, IPR2018-00455, U.S. Pat. No. 9,313,157. |
| Petitioner's Reply in Inter Partes Review, Feb. 19, 2019, IPR2018-00455, U.S. Pat. No. 9,313,157. |
| Petitioner's Opposition to Patent Owner's Motion to Amend in Inter Partes Review, Feb. 19, 2019, IPR2018-00455, U.S. Pat. No. 9,313,157. |
| Declaration of Sandeep Chatterjee Submitted with Petitioner's Reply in Inter Partes Review, Feb. 19, 2019, IPR2018-00455, U.S. Pat. No. 9,313,157. |
| Patent Owner's Sur-Reply in Inter Partes Review, Mar. 21, 2019, IPR2018-00455, U.S. Pat. No. 9,313,157. |
| Patent Owner's Reply in Support of Its Motion to Amend in Inter Partes Review, Mar. 21, 2019, IPR2018-00455, U.S. Pat. No. 9,313,157. |
| Declaration of Kevin C. Almeroth in Support of Patent Owner's Reply in Support of Its Motion to Amend in Inter Partes Review, Mar. 21, 2019, IPR2018-00455, U.S. Pat. No. 9,313,157. |
| Petitioner's Sur-Reply to Patent Owner's Motion to Amend in Inter Partes Review, Apr. 8, 2019, IPR2018-00455, U.S. Pat. No. 9,313,157. |
| Petition for Inter Partes Review, Dec. 26, 2017, IPR2018-00397, U.S. Pat. No. 9,306,886. |
| Declaration of Sandeep Chatterjee Submitted with Petitioner's Petition for Inter Partes Review, Dec. 26, 2017, IPR2018-00397, U.S. Pat. No. 9,306,886. |
| Patent Owner's Preliminary Response in Inter Partes Review, Apr. 11, 2018, IPR2018-00397, U.S. Pat. No. 9,306,886. |
| Declaration of Michael Shamos in Opposition to Petition for Inter Partes Review, Apr. 11, 2018, IPR2018-00397, U.S. Pat. No. 9,306,886. |
| Decision Institution of Inter Partes Review, Jul. 10, 2018, IPR2018-00397, U.S. Pat. No. 9,306,886. |
| Patent Owner's Response in Inter Partes Review, Oct. 12, 2018, IPR2018-00397, U.S. Pat. No. 9,306,886. |
| Declaration of Kevin C. Almeroth (Patent Owner Expert) Submitted with Patent Owner's Response in Inter Partes Review, Oct. 12, 2018, IPR2018-00397, U.S. Pat. No. 9,306,886. |
| Petitioner's Reply in Inter Partes Review, Jan. 31, 2019, IPR2018-00397, U.S. Pat. No. 9,306,886. |
| Declaration of Sandeep Chatterjee Submitted with Petitioner's Reply in Inter Partes Review, Jan. 31, 2019, IPR2018-00397, U.S. Pat. No. 9,306,886. |
| Patent Owner's Sur-Reply in Inter Partes Review, Feb. 28, 2019, IPR2018-00397, U.S. Pat. No. 9,306,886. |
| Petition for Inter Partes Review, Dec. 29, 2017, IPR2018-00408, U.S. Pat. No. 9,338,111. |
| Declaration of Sandeep Chatterjee Submitted with Petitioner's Petition for Inter Partes Review, Dec. 29, 2017, IPR2018-00408, U.S. Pat. No. 9,338,111. |
| Patent Owner's Preliminary Response in Inter Partes Review, May 9, 2018, IPR2018-00408, U.S. Pat. No. 9,338,111. |
| Declaration of Michael Shamos in Opposition to Petition for Inter Partes Review, May 9, 2018, IPR2018-00408, U.S. Pat. No. 9,338,111. |
| Decision Institution of Inter Partes Review, Jul. 10, 2018, IPR2018-00408, U.S. Pat. No. 9,338,111. |
| Patent Owner's Response in Inter Partes Review, Oct. 12, 2018, IPR2018-00408, U.S. Pat. No. 9,338,111. |
| Declaration of Kevin C. Almeroth (Patent Owner Expert) Submitted with Patent Owner's Response in Inter Partes Review, Oct. 12, 2018, IPR2018-00408, U.S. Pat. No. 9,338,111. |
| Petitioner's Reply in Inter Partes Review, Jan. 31, 2019, IPR2018-00408, U.S. Pat. No. 9,338,111. |
| Declaration of Sandeep Chatterjee Submitted with Petitioner's Reply in Inter Partes Review, Jan. 31, 2019, IPR2018-00408, U.S. Pat. No. 9,338,111. |
| Patent Owner's Sur-Reply in Inter Partes Review, Feb. 28, 2019, IPR2018-00408, U.S. Pat. No. 9,338,111. |
| Petition for Inter Partes Review, Nov. 16, 2017, IPR2018-00200, U.S. Pat. No. 8,886,739. |
| Declaration of Sandeep Chatterjee Submitted with Petitioner's Petition for Inter Partes Review, Nov. 16, 2017, IPR2018-00200, U.S. Pat. No. 8,886,739. |
| Patent Owner's Preliminary Response in Inter Partes Review, Mar. 7, 2018, IPR2018-00200, U.S. Pat. No. 8,886,739. |
| Declaration of Michael Shamos in Opposition to Petition for Inter Partes Review, Mar. 7, 2018, IPR2018-00200, U.S. Pat. No. 8,886,739. |
| Decision Institution of Inter Partes Review, Jun. 6, 2018, IPR2018-00200, U.S. Pat. No. 8,886,739. |
| Patent Owner's Response in Inter Partes Review, Oct. 12, 2018, IPR2018-00200, U.S. Pat. No. 8,886,739. |
| Declaration of Kevin C. Almeroth (Patent Owner Expert) Submitted with Patent Owner's Response in Inter Partes Review, Oct. 12, 2018, IPR2018-00200, U.S. Pat. No. 8,886,739. |
| Petitioner's Reply in Inter Partes Review, Jan. 31, 2019, IPR2018-00200, U.S. Pat. No. 8,886,739. |
| Declaration of Sandeep Chatterjee Submitted with Petitioner's Reply in Inter Partes Review, Jan. 31, 2019, IPR2018-00200, U.S. Pat. No. 8,886,739. |
| Patent Owner's Sur-Reply in Inter Partes Review, Feb. 28, 2019, IPR2018-00200, U.S. Pat. No. 8,886,739. |
| Petition for Inter Partes Review, Jan. 21, 2017, IPR2018-00369, U.S. Pat. No. 9,313,155. |
| Declaration of Sandeep Chatterjee Submitted with Petitioner's Petition for Inter Partes Review, Jan. 21, 2017, IPR2018-00369, U.S. Pat. No. 9,313,155. |
| Patent Owner's Preliminary Response in Inter Partes Review, Apr. 11, 2018, IPR2018-00369, U.S. Pat. No. 9,313,155. |
| Declaration of Michael Shamos in Opposition to Petition for Inter Partes Review, Apr. 11, 2018, IPR2018-00369, U.S. Pat. No. 9,313,155. |
| Decision Institution of Inter Partes Review, Jul. 10, 2018, IPR2018-00369, U.S. Pat. No. 9,313,155. |
| Patent Owner's Response in Inter Partes Review, Oct. 12, 2018, IPR2018-00369, U.S. Pat. No. 9,313,155. |
| Declaration of Kevin C. Almeroth (Patent Owner Expert) Submitted with Patent Owner's Response in Inter Partes Review, Oct. 12, 2018, IPR2018-00369, U.S. Pat. No. 9,313,155. |
| Petitioner's Reply in Inter Partes Review, Jan. 31, 2019, IPR2018-00369, U.S. Pat. No. 9,313,155. |
| Declaration of Sandeep Chatterjee Submitted with Petitioner's Reply in Inter Partes Review, Jan. 31, 2019, IPR2018-00369, U.S. Pat. No. 9,313,155. |
| Patent Owner's Sur-Reply in Inter Partes Review, Feb. 28, 2019, IPR2018-00369, U.S. Pat. No. 9,313,155. |
| Petition for Inter Partes Review, Jan. 10, 2018, IPR2018-00458, U.S. Pat. No. 9,313,156. |
| Declaration of Sandeep Chatterjee Submitted with Petitioner's Petition for Inter Partes Review, Jan. 10, 2018, IPR2018-00458, U.S. Pat. No. 9,313,156. |
| Patent Owner's Preliminary Response in Inter Partes Review, Jun. 8, 2019, IPR2018-00458, U.S. Pat. No. 9,313,156. |
| Declaration of Michael Shamos in Opposition to Petition for Inter Partes Review, Jun. 8, 2019, IPR2018-00458, U.S. Pat. No. 9,313,156. |
| Decision Institution of Inter Partes Review, Aug. 31, 2018, IPR2018-00458, U.S. Pat. No. 9,313,156. |
| Patent Owner's Response in Inter Partes Review, Nov. 13, 2018, IPR2018-00458, U.S. Pat. No. 9,313,156. |
| Declaration of Kevin C. Almeroth (Patent Owner Expert) Submitted with Patent Owner's Response in Inter Partes Review, Nov. 13, 2018, IPR2018-00458, U.S. Pat. No. 9,313,156. |
| Patent Owner's Motion to Amend in Inter Partes Review, Nov. 13, 2018, IPR2018-00458, U.S. Pat. No. 9,313,156. |
| Petitioner's Reply in Inter Partes Review, Feb. 19, 2019, IPR2018-00458, U.S. Pat. No. 9,313,156. |
| Petitioner's Opposition to Patent Owner's Motion to Amend in Inter Partes Review, Feb. 19, 2019, IPR2018-00458, U.S. Pat. No. 9,313,156. |
| Declaration of Sandeep Chatterjee Submitted with Petitioner's Reply in Inter Partes Review, Feb. 19, 2019, IPR2018-00458, U.S. Pat. No. 9,313,156. |
| Patent Owner's Sur-Reply in Inter Partes Review, Mar. 21, 2019, IPR2018-00458, U.S. Pat. No. 9,313,156. |
| Patent Owner's Reply in Support of Its Motion to Amend in Inter Partes Review, Mar. 21, 2019, IPR2018-00458, U.S. Pat. No. 9,313,156. |
| Declaration of Kevin C. Almeroth in Support of Patent Owner's Reply in Support of Its Motion to Amend in Inter Partes Review, Mar. 21, 2019, IPR2018-00458, U.S. Pat. No. 9,313,156. |
| Petitioner's Sur-Reply to Patent Owner's Motion to Amend in Inter Partes Review, Apr. 8, 2019, IPR2018-00458, U.S. Pat. No. 9,313,156. |
| Petition for Inter Partes Review, Dec. 14, 2017, IPR2018-00312, U.S. Pat. No. 9,306,885. |
| Declaration of Sandeep Chatterjee Submitted with Petitioner's Petition for Inter Partes Review, Dec. 14, 2017, IPR2018-00312, U.S. Pat. No. 9,306,885. |
| Patent Owner's Preliminary Response in Inter Partes Review, Mar. 19, 2018, IPR2018-00312, U.S. Pat. No. 9,306,885. |
| Declaration of Michael Shamos in Opposition to Petition for Inter Partes Review, Mar. 19, 2018, IPR2018-00312, U.S. Pat. No. 9,306,885. |
| Decision Institution of Inter Partes Review, Jun. 18, 2018, IPR2018-00312, U.S. Pat. No. 9,306,885. |
| Patent Owner's Response in Inter Partes Review, Oct. 12, 2018, IPR2018-00312, U.S. Pat. No. 9,306,885. |
| Declaration of Kevin C. Almeroth (Patent Owner Expert) Submitted with Patent Owner's Response in Inter Partes Review, Oct. 12, 2018, IPR2018-00312, U.S. Pat. No. 9,306,885. |
| Petitioner's Reply in Inter Partes Review, Jan. 31, 2019, IPR2018-00312, U.S. Pat. No. 9,306,885. |
| Declaration of Sandeep Chatterjee Submitted with Petitioner's Reply in Inter Partes Review, Jan. 31, 2019, IPR2018-00312, U.S. Pat. No. 9,306,885. |
| Patent Owner's Sur-Reply in Inter Partes Review, Feb. 28, 2019, IPR2018-00312, U.S. Pat. No. 9,306,885. |
| Petition for Inter Partes Review, Dec. 31, 2017, IPR2018-00416, U.S. Pat. No. 9,413,711. |
| Declaration of Sandeep Chatterjee Submitted with Petitioner's Petition for Inter Partes Review, Dec. 31, 2017, IPR2018-00416, U.S. Pat. No. 9,413,711. |
| Patent Owner's Preliminary Response in Inter Partes Review, May 9, 2018, IPR2018-00416, U.S. Pat. No. 9,413,711. |
| Declaration of Michael Shamos in Opposition to Petition for Inter Partes Review, May 9, 2018, IPR2018-00416, U.S. Pat. No. 9,413,711. |
| Decision Institution of Inter Partes Review, Aug. 8, 2018, IPR2018-00416, U.S. Pat. No. 9,413,711. |
| Patent Owner's Response in Inter Partes Review, Nov. 13, 2018, IPR2018-00416, U.S. Pat. No. 9,413,711. |
| Declaration of Kevin C. Almeroth (Patent Owner Expert) Submitted with Patent Owner's Response in Inter Partes Review, Nov. 13, 2018, IPR2018-00416, U.S. Pat. No. 9,413,711. |
| Petitioner's Reply in Inter Partes Review, Feb. 19, 2019, IPR2018-00416, U.S. Pat. No. 9,413,711. |
| Declaration of Sandeep Chatterjee Submitted with Petitioner's Reply in Inter Partes Review, Feb. 19, 2019, IPR2018-00416, U.S. Pat. No. 9,413,711. |
| Patent Owner's Sur-Reply in Inter Partes Review, Mar. 21, 2019, IPR2018-00416, U.S. Pat. No. 9,413,711. |
| Petition for Inter Partes Review, Jan. 9, 2018, IPR2018-00439, U.S. Pat. No. 9,413,711. |
| Declaration of Sandeep Chatterjee Submitted with Petitioner's Petition for Inter Partes Review, Jan. 9, 2018, IPR2018-00439, U.S. Pat. No. 9,413,711. |
| Patent Owner's Preliminary Response in Inter Partes Review, May 4, 2018, IPR2018-00439, U.S. Pat. No. 9,413,711. |
| Declaration of Michael Shamos in Opposition to Petition for Inter Partes Review, May 4, 2018, IPR2018-00439, U.S. Pat. No. 9,413,711. |
| Decision Institution of Inter Partes Review, Aug. 2, 2018, IPR2018-00439, U.S. Pat. No. 9,413,711. |
| Patent Owner's Response in Inter Partes Review, Nov. 13, 2018, IPR2018-00439, U.S. Pat. No. 9,413,711. |
| Declaration of Kevin C. Almeroth (Patent Owner Expert) Submitted with Patent Owner's Response in Inter Partes Review, Nov. 13, 2018, IPR2018-00439, U.S. Pat. No. 9,413,711. |
| Patent Owner's Motion to Amend in Inter Partes Review, Nov. 13, 2018, IPR2018-00439, U.S. Pat. No. 9,413,711. |
| Petitioner's Reply in Inter Partes R eview, Feb. 19, 2019, IPR2018-00439, U.S. Pat. No. 9,413,711. |
| Petitioner's Opposition to Patent Owner's Motion to Amend in Inter Partes R eview, Feb. 19, 2019, IPR2018-00439, U.S. Pat. No. 9,413,711. |
| Declaration of Sandeep Chatterjee Submitted with Petitioner's Reply in Inter Partes Review, Feb. 19, 2019, IPR2018-00439, U.S. Pat. No. 9,413,711. |
| Patent Owner's Sur-Reply in Inter Partes Review, Mar. 21, 2019, IPR2018-00439, U.S. Pat. No. 9,413,711. |
| Patent Owner's Reply in Support of Its Motion to Amend in Inter Partes Review, Mar. 21, 2019, IPR2018-00439, U.S. Pat. No. 9,413,711. |
| Declaration of Kevin C. Almeroth in Support of Patent Owner's Reply in Support of Its Motion to Amend in Inter Partes Review, Mar. 21, 2019, IPR2018-00439, U.S. Pat. No. 9,413,711. |
| Petitioner's Sur-Reply to Patent Owner's Motion to Amend in Inter Partes Review, Apr. 8, 2019, IPR2018-00439, U.S. Pat. No. 9,413,711. |
| Meyer, Eric A., Cascading Style Sheets: The Definitive Guide , O'Reilly Media, 2d ed. Mar. 2004, p. 75-91. |
| The American Heritage Dictionary of the English Language , Houghton Mifflin, 4th ed. 2000, p. 411, 1472, 1473. |
| Merriam Webster's Collegiate Dictionary , Merriam-Webster. 10th ed. 1993, p. 260. |
| Merriam Webster's Collegiate Dictionary , Merriam-Webster. 10th ed. 1993, p. 972. |
| Merriam Webster's Collegiate Dictionary , Merriam-Webster. 10th ed. 1993, p. 987. |
| Random House Webster's Unabridged Dictionary , Random House Reference, 2001, p. 455. |
| Flynn, Meredith and Rutkosky, Nita. Microsoft Access 2000: Core and Expert Certification . Paradigm Publishing. 2000. p. A130-A131. |
| Microsoft Computer Dictionary . Microsoft Press. 5th ed. 2002. p. 499. |
| Microsoft Computer Dictionary . Microsoft Press. 5th ed. 2002. p. 58, 59, 213, 228, 341, 349, 394, 399, 499, 545, and 574. |
| Doraswamy, Naganand and Harkins, Dan. IPSec: The New Security Standard for the Internet, Intranets, and Virtual Private Networks . Prentice Hall PTR. 2d ed. 2003. p. 8. |
| Pountain, Dick. The Penguin Concise Dictionary of Computing. Penguin Books . 2003. p. 21, 208, 272, 338, and 466-468. |
| Meloni, Julie C. PHP Essentials . Prima Publishing. 2000. p. 1-68. |
| Request for Comment (RFC) 2822: Internet Message Format . Network Working Group, Qualcomm Inc. Apr. 2001. |
| Request for Comment (RFC) 822: Standard for the Format of ARPA Internet Text Messages . Dept. of Elec. Eng'g, Univ. of Del. Aug. 13, 1982. |
| Request for Comment (RFC) 2109: HTTP State Management Mechanism . Bell Laboratories, Lucent Technologies and Netscape Communications. Feb. 1997. |
| Mehlman, Maxwell J. et al. “The Need for Anonymous Genetic Counseling and Testing,” Am. J. Hum. Genet. 58:393-397. 1996. |
| Request for Comment (RFC) 2821: Simple Mail Transfer Protocol . AT&T Laboratories. Apr. 2001. |
| Blum, Richard. “Chapter 15: Using the Maildir Mailbox Format.” Postfix . Sams Publishing. 2001. p. 336-358. |
| Hazel, Philip. Exim: The Mail Transfer Agent . O'Reilly Media. 2001. p. 1-100 and 173-237. |
| Boyce, Jim. Microsoft Outlook Version 2002: Inside Out . Microsoft Press. 2001. p. 121-144, 173-224, and 225-260. |
| Request for Comment (RFC) 2026: The Internet Standards Process—Revision 3 . Harvard University. Oct. 1996. |
| Request for Comment (RFC) 1543: Instructions to RFC Authors . Information Sciences Institute (ISI). Oct. 1993. |
| Tanenbaum, Andrew S. Modern Operating Systems . Prentice-Hall. 2d ed. 2001. p. 395-398. |
| Random House Concise Dictionary of Science & Computers . Helicon Publishing. 2004. p. 480, 575, and 700. |
| Inan, Hurol. Measuring the Success of Your Website: A Customer-Centric Approach to Website Management . Pearson Education Australia. 2002. p. 162-163. |
| Pallmann, David. Network Query Language (NQL) . Wiley Computer Publishing. 2002. p. 361-363. |
| Random House Webster's College Dictionary . Random House. 2d ed. 1999. p. 730. |
| Wilkinson, Neill. Next Generation Network Services: Technologies and Strategies . John Wiley & Sons. 2002. p. 63-64. |
| Mandel, Theo. The Elements of user Interface Design . Wiley Computer Publishing. 1997. p. ix-xvi, 47-79, 335-341. |
| Stevenson, Nancy. Tablet PCs for Dummies . Wiley Publishing. 2003. p. 1-26, 221-254, and 271-286. |
| User Manual: Nokia 9000i Communicator . Nokia Mobile Phones Ltd. 1997. |
| Nextel i1000plus User's Guide: Digital Multi-Service Data-Capable Phone . Nextel Communications. Mar. 22, 1999. |
| Sadun, Erica. Digital Video Essentials . Sybex, Inc. 2003. |
| Request for Comment (RFC) 772: Mail Transfer Protocol . Information Sciences Institute (ISI). Sep. 1980. |
| Rubenking, Neil J. “Disabling Print Screen.” P.C. Magazine, vol. 7, No. 14, p. 450-451, Aug. 1988. |
| Yuon, Michael Juntao. Enterprise J2ME: Developing Mobile Java Applications . Pearson Education. 2004. p. 1-13. |
| Yuon, Michael Juntao. Enterprise J2ME: Developing Mobile Java Applications . Pearson Education. 2004. p. 147-162. |
| Slides Presented at Claim Construction Hearing by Snap, Inc. on Feb. 26, 2018 in Vaporstream, Inc. v. Snap, Inc. , Case No. 2:17-cv-00220-MLH-KSx. |
| Slides Presented at Claim Construction Hearing by Vaporstream, Inc. on Feb. 26, 2018 in Vaporstream, Inc. v. Snap, Inc. , Case No. 2:17-cv-00220-MLH-KSx. |
| Claim Construction Opening Brief by Snap, Inc. with Exhibits, filed on Jan. 19, 2018 in Vaporstream, Inc. v. Snap, Inc. , Case No. 2:17-cv-00220-MLH-KSx. |
| Declaration of Saul Greenberg, Ph.D. (Expert for Snap, Inc.) Regarding Claim Construction, filed on Jan. 19, 2018 in Vaporstream, Inc. v. Snap, Inc. , Case No. 2:17-cv-00220-MLH-KSx. |
| Claim Construction Opening Brief by Vaporstream, Inc., filed on Jan. 19, 2018 in Vaporstream, Inc. v. Snap, Inc. , Case No. 2:17-cv-00220-MLH-KSx. |
| Exhibits 1 to 7 Submitted with Claim Construction Opening Brief by Vaporstream, Inc., filed on Jan. 19, 2018 in Vaporstream, Inc. v. Snap, Inc. , Case No. 2:17-cv-00220-MLH-KSx. |
| Exhibits 8 to 19 Submitted with Claim Construction Opening Brief by Vaporstream, Inc., filed on Jan. 19, 2018 in Vaporstream, Inc. v. Snap, Inc., Case No. 2:17-cv-00220-MLH-KSx. |
| Claim Construction Order, dated Feb. 27, 2018 in Vaporstream, Inc. v. Snap, Inc., Case No. 2:17-cv-00220-MLH-KSx. |
| Claim Construction Responsive Brief by Snap, Inc., filed on Feb. 2, 2018 in Vaporstream, Inc. v. Snap, Inc., Case No. 2:17-cv-00220-MLH-KSx. |
| Claim Construction Responsive Brief by Vaporstream, Inc., filed on Feb. 2, 2018 in Vaporstream, Inc. v. Snap, Inc., Case No. 2:17-cv-00220-MLH-KSx. |
| Transcript of Deposition of Saul Greenberg, Ph.D. (Expert for Snap, Inc.) for Deposition Taken on Sep. 15, 2017 in Vaporstream, Inc. v. Snap, Inc., Case No. 2:17-cv-00220-MLH-KSx. |
| Transcript of Deposition of Saul Greenberg, Ph.D. (Expert for Snap, Inc.) for Deposition Taken on Jan. 25, 2018 in Vaporstream, Inc. v. Snap, Inc., Case No. 2:17-cv-00220-MLH-KSx. |
| Transcript of Deposition of Saul Greenberg, Ph.D. (Expert for Snap, Inc.) for Deposition Taken on May 29, 2018 in Vaporstream, Inc. v. Snap, Inc., Case No. 2:17-cv-00220-MLH-KSx. |
| Expert Report of Saul Greenberg, Ph.D. Regarding Invalidity of Patents-in-Suit with Exhibit C Invalidity Tables, dated Apr. 25, 2018, in Vaporstream, Inc. v. Snap, Inc., Case No. 2:17-cv-00220-MLH-KSx. |
| Second Amended Invalidity Contentions of Snap, Inc. with Exhibits (Invalidity Tables), filed Jan. 12, 2018, in Vaporstream, Inc. v. Snap, Inc., Case No. 2:17-cv-00220-MLH-KSx. |
| Court Order Denying Snap, Inc.'s Motion to Dismiss for Lack of Patentable Subject Matter, dated Jun. 12, 2017 in Vaporstream, Inc. v. Snap, Inc., Case No. 2:17-cv-00220-MLH-KSx. |
| Snap, Inc.'s Reply in Support of Its Motion to Dismiss for Lack of Patentable Subject Matter, filed May 1, 2017 in Vaporstream, Inc. v. Snap, Inc., Case No. 2:17-cv-00220-MLH-KSx. |
| Snap, Inc.'s Notice of Motion, Motion, and Memorandum of Points and Authorities in Support of its Motion to Dismiss for Lack of Patentable Subject Matter, filed Feb. 22, 2017 in Vaporstream, Inc. v. Snap, Inc., Case No. 2:17-cv-00220-MLH-KSx. |
| Vaporstream, Inc.'s Memorandum of Points and Authorities in Opposition to Snap, Inc.'s Motion to Dismiss for Lack of Patentable Subject Matter with Exhibits, filed Apr. 19, 2017 in Vaporstream, Inc. v. Snap, Inc., Case No. 2:17-cv-00220-MLH-KSx. |
| Cour Order Denying Snap, Inc.'s Motion for Summary Judgement of Invalidity Under 35 U.S.C. §101, dated Feb. 27, 2018 in Vaporstream, Inc. v. Snap, Inc., Case No. 2:17-cv-00220-MLH-KSx. |
| Snap, Inc.'s Notice of Motion, Motion, and Memorandum of Points and Authorities in Support of its Motion for Summary Judgment of Invalidity Under 35 U.S.C. §101 with Exhibits (parts 1 to 3), filed Aug. 22, 2017 in Vaporstream, Inc. v. Snap, Inc., Case No. 2:17-cv-00220-MLH-KSx. |
| Snap, Inc.'s Reply in Support of its Motion for Summary Judgment of Invalidity Under 35 U.S.C. §101 with Exhibits, filed Oct. 16, 2017 in Vaporstream, Inc. v. Snap, Inc., Case No. 2:17-cv-00220-MLH-KSx. |
| User Guide for ArcSoft MMS Composer . ArcSoft, Inc. 2003. |
| “Arcsoft MMS Composer Website.” Mar. 10, 2005. Accessed at https://web.archive.org/web/20050310094354/http:/www.arcsoft.com:80/en/products/mmscomposer/. Last Accessed Apr. 24, 2018. |
| User Guide for Ericcson R320s Mobile Phone . Ericcson Mobile Communications. 2d ed. Dec. 1999. |
| User Guide for Ericcson I 888 World Mobile Phone . Ericcson Mobile Communications. 1st ed. Oct. 1998. |
| Nikkanen, Mikko. “One-Handed Use as a Design Driver: Enabling Efficient Multi-channel Delivery of Mobile Applications,” Mobile and Ubiquitous Information Access: Mobile HCI 2003 International Workshop Udine, Italy, Sep. 8, 2003. F.Crestini et al. (Eds.). Springer-Verlag Berlin Heidelberg. 2004. p. 28-41. |
| Lai, Jennifer. “Facilitating Mobile Communication with Multimodal Access to Email Messages on a Cell Phone,” CHI 2004: Late Breaking Results Paper. Vienna, Austria, Apr. 24-29, 2004. p. 1259-1262. |
| “ArcSoft MMS Composer Press Release: ArcSoft Delivers MMS Composer Imaging Softwware Solution to Handheld Device Manufacturers.” Dated Jun. 18, 2003. Accessed from WebArchive storage Date of Feb. 7, 2004 at https://web.archive.org/web/20040207012149/http:/www.arcsoft.com:80/en/press/releases/viewrelease.asp?releaseid=75. Last Accessed: Apr. 24, 2018. |
| Braginski, Leonid and Powell, Matthew. Running Microsoft Internet Information Server . Microsoft Press. 1998. p. 1-7, 621-689. |
| Honeycutt, Jerry. Introducing Microsoft Windows Server 2003 . Microsoft Press. 2003. p. 201-202. |
| Ivens, Kathy et al. Windows Server 2003: The Complete Reference . McGraw-Hill. 2003. p. 230-247. |
| Minasi, Mark et al. Mastering Windows Server 2003 . Sybex, Inc. 2003. p. 1303-1344. |
| Morimoto, Rand et al. Microsoft Windows Server 2003: Insider Solutions . Sams Publishing. 2004. p. 196-199. |
| Nokia 7610 User Guide . Nokia. 2004. |
| Ruest, Nelson and Ruest Danielle. Windows Server 2003 Pocket Administrator: Your On-the-Job Quick Reference . McGraw-Hill. 2003. p. 36-37. |
| Stanek, William R. Microsoft Windows Server 2003: Inside Out . Microsoft Press. 2004. p. 547-549. |
| Williams, Robert and Walla, Mark. The Ultimate Windows Server 2003 System Administrator's Guide . Addison_Wesley. 2003. p. 682-684. |
| User's Guide for Nokia 7610 . Nokia. 2004. |
| Microsoft Computer Dictionary . Microsoft Press. 3rd ed. 1997. p. 309. |
| Microsoft Computer Dictionary . Microsoft Press. 5th ed. 2002. p. 341. |
| Thomas, Stephen. HTTP Essentials: Protocols for Secure, Scaleable, Web Sites . Wiley Computer Publishing. 2001. p. 13-26. |
| “Nokia 7610 Press Release on Launch Date.” Jun. 1, 2004. Accessed at https://web.archive.org/web/20040612161055/http://press.nokia.com:80/PR/20040 6/947561_5.html. Last accessed Apr. 24, 2018. |
| Request for Comment (RFC) 2046: Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types . Innosoft and First Virtual. Nov. 1996. |
| Request for Comment (RFC) 2392: Content-ID and Message-ID Uniform Resource Locators . E. Levinson. Aug. 1998. |
| Paw, Howard and Gade, Lisa. “O2 XDA II Windows Mobile Phone Edition 2003.” MobileTechReview.com Article Posted Mar. 25, 2004, updated Jun. 2004. Accessed at https://web.archive.org/web/20050408095548/http://www.mobiletechreview.com/XDA_II.htm. Last Accessed: Apr. 25, 2018. |
| HP iPAQ Pocket PC h6300 Series User's Guide . Hewlett-Packard Development Company. Jun. 2004. |
| Henry, Paul and Luo, Hui. “Off the record Email System” (document and presentation). Presentation at IEEE Conference on Computer Communications (Infocom) Apr. 2001, Anchorage, Alaska, USA; last found at http://www.research.att.com:9000/˜macsbug/Other_Cool_Stuff/OTREM/otrem.html on Apr. 7, 2006. |
| Bass, Steve. “50 fixes for the biggest PC annoyances: Windows gone wacky? Hardware gone haywire? Software gone screwy? Take a deep breath—help is here.” [online] Oct. 1, 2003. [retrieved on Mar. 8, 2009] PC-World. [Retrieved from http://www.accessmylibrary.com/coms2/summary_0286-24479177_ITM] p. 3 Paragraph 5-7. |
| Gulco, Ceki and Tsudik, Gene. “Mixing E-mail with Babel.” Proceedings of the Symposium on Network and Distributed System Security, XP-002086536, Jan. 1, 1996, pp. 2-16. |
| Elkins, Michael. “The Mutt E-mail Client.” ftp://ftp.nluug.nl/pub/mail/mutt/historic/mutt-1.Opre2.tar.gz, XP-002245042, Sep. 1, 1999. |
| Eide, Kristian. “The Next Generation of Mail Clients.” LWN.net. Feb. 25, 2004. Retrieved from https://lwn.net/Articles/72937/, last visited Dec. 11, 2015. |
| Garrett, Jesse James. “Yahoo! Mail: Simplicity Holds Up Over Time.” BoxesandArrows.com. Mar. 11, 2002. Retrieved from http://boxesandarrows.com/yahoo-mail-simplicity-holds-up-over-time/, last visited Dec. 11, 2015. |
| Garrett, Jesse James. “Yahoo! Mail.” Dec. 28, 2001. From BoxesandArrows.com. |
| GSM Application Style Guide. Openwave Systems Inc. Feb. 2001. |
| Jarrett, Caroline. “Designing Usable Forms: The Three Layer Model of the Form.” Effortmark. Excerpt from St. Francis Leprosy Guild Forms. 2000. |
| Klensin, J. (ed.). Request for Comment 2821: “Simple Mail Transfer Protocol.” The Internet Society. Apr. 2001. Retrieved from https://www.ietf.org/rfc/rfc2821.txt, last visited Dec. 11, 2015. |
| Spolsky, Joel. “User Interface Design for Programmers.” Apress. 2001. |
| Starling, Andrew. “Usability and HTML Forms.” ecommerce-guide.com. Dec. 11, 2001. Retrieved from http://www.ecommerce-guide.com/solutions/building/article.php/938071/Usability-and-HTML-Forms.htm, last visited Dec. 11, 2015. |
| Wroblewski, Luke. “Web Application Form Design.” Jan. 22, 2005. Retrieved from http://www.lukew.com/ff/entry.asp?1502, last visited Dec. 11, 2015. |
| U.S. Appl. No. 11/401,148, filed Mar. 13, 2009, First Office Action, now U.S. Pat. No. 7,610,345. |
| U.S. Appl. No. 11/401,148, Jun. 10, 2009, Interview Summary, now U.S. Pat. No. 7,610,345. |
| U.S. Appl. No. 11/401,148, Jun. 15, 2009, Response to Office Action, now U.S. Pat. No. 7,610,345. |
| U.S. Appl. No. 11/401,148, Aug. 25, 2009, Notice of Allowance, now U.S. Pat. No. 7,610,345. |
| U.S. Appl. No. 11/401,148, Aug. 25, 2009, Rule 312 Amendment, now U.S. Pat. No. 7,610,345. |
| U.S. Appl. No. 11/401,148, Oct. 7, 2009, Issue Notification, now U.S. Pat. No. 7,610,345. |
| U.S. Appl. No. 11/859,777, Aug. 19, 2009, Office Action. |
| U.S. Appl. No. 12/031,845, Sep. 29, 2010, Office Action. |
| U.S. Appl. No. 12/605,885, Jan. 25, 2011, Office Action, now U.S. Pat. No. 8,291,026. |
| U.S. Appl. No. 12/605,885, May 25, 2011, Response to Office Action, now U.S. Pat. No. 8,291,026. |
| U.S. Appl. No. 12/605,885, Jun. 14, 2011, Examiner Interview Summary, now U.S. Pat. No. 8,291,026. |
| U.S. Appl. No. 12/605,885, Aug. 4, 2011, Final Office Action, now U.S. Pat. No. 8,291,026. |
| U.S. Appl. No. 12/605,885, Nov. 23, 2011, Examiner Interview Summary, now U.S. Pat. No. 8,291,026. |
| U.S. Appl. No. 12/605,885, Jan. 4, 2012, Response to Final Office Action and RCE, now U.S. Pat. No. 8,291,026. |
| U.S. Appl. No. 12/605,885, Jun. 11, 2012, Notice of Allowance, now U.S. Pat. No. 8,291,026. |
| U.S. Appl. No. 13/447,932, Jan. 9, 2014, Response to Office Action, now U.S. Pat. No. 9,282,081. |
| U.S. Appl. No. 13/447,932, Sep. 9, 2014, Office Action, now U.S. Pat. No. 9,282,081. |
| U.S. Appl. No. 13/447,932, Mar. 19, 2015, Notice of Allowance, now U.S. Pat. No. 9,282,081. |
| U.S. Appl. No. 13/447,932, May 21, 2015, Office Action, now U.S. Pat. No. 9,282,081. |
| U.S. Appl. No. 13/447,932, Jun. 24, 2015, Applicant Initiated Interview Summary, now U.S. Pat. No. 9,282,081. |
| U.S. Appl. No. 13/447,932, Jul. 16, 2015, Office Action (Supplemental), now U.S. Pat. No. 9,282,081. |
| U.S. Appl. No. 13/447,932, Dec. 11, 2015, Applicant Initiated Interview Summary, now U.S. Pat. No. 9,282,081. |
| U.S. Appl. No. 13/447,932, Dec. 11, 2015, Response to Office Action with eTerminal Disclaimers, now U.S. Pat. No. 9,282,081. |
| U.S. Appl. No. 13/447,932, Jan. 11, 2016, Examiner Interview Summary, now U.S. Pat. No. 9,282,081. |
| U.S. Appl. No. 13/447,932, Jan. 11, 2016, Examiner Initiated Interview Summary, now U.S. Pat. No. 9,282,081. |
| U.S. Appl. No. 13/447,932, Jan. 22, 2016, Notice of Allowance, now U.S. Pat. No. 9,282,081. |
| U.S. Appl. No. 13/447,932, Feb. 17, 2016, Issue Notification, now U.S. Pat. No. 9,282,081. |
| U.S. Appl. No. 13/651,909, Jun. 8, 2015, Office Action. |
| U.S. Appl. No. 13/651,909, Dec. 21, 2015, Notice of Abandonment. |
| U.S. Appl. No. 13/864,930, Nov. 6, 2015, Office Action. |
| U.S. Appl. No. 14/133,875, May 21, 2014, Office Action, now U.S. Pat. No. 8,935,351. |
| U.S. Appl. No. 14/133,875, May 28, 2014, Supplemental Office Action, now U.S. Pat. No. 8,935,351. |
| U.S. Appl. No. 14/133,875, Jun. 9, 2014, Examiner Interview Summary, now U.S. Pat. No. 8,935,351. |
| U.S. Appl. No. 14/133,875, Jun. 23, 2014, Examiner Interview Summary, now U.S. Pat. No. 8,935,351. |
| U.S. Appl. No. 14/133,875, Jul. 14, 2014, Response to Office Action, now U.S. Pat. No. 8,935,351. |
| U.S. Appl. No. 14/133,875, Jul. 23, 2014, Resubmission of Terminal Disclaimers, now U.S. Pat. No. 8,935,351. |
| U.S. Appl. No. 14/133,875, Aug. 15, 2014, Notice of Allowance, now U.S. Pat. No. 8,935,351. |
| U.S. Appl. No. 14/133,875, Dec. 23, 2014, Issue Notification, now U.S. Pat. No. 8,935,351. |
| U.S. Appl. No. 14/133,897, May 28, 2014, Office Action, now U.S. Pat. No. 8,886,739. |
| U.S. Appl. No. 14/133,897, Jun. 9, 2014, Examiner Interview Summary, now U.S. Pat. No. 8,886,739. |
| U.S. Appl. No. 14/133,897, Jun. 23, 2014, Examiner Interview Summary, now U.S. Pat. No. 8,886,739. |
| U.S. Appl. No. 14/133,897, Jul. 14, 2014, Response to Office Action, now U.S. Pat. No. 8,886,739. |
| U.S. Appl. No. 14/133,897, Jul. 23, 2014, Resubmission of Terminal Disclaimers, now U.S. Pat. No. 8,886,739. |
| U.S. Appl. No. 14/133,897, Aug. 5, 2014, Notice of Allowance, now U.S. Pat. No. 8,886,739. |
| U.S. Appl. No. 14/133,897, Oct. 22, 2014, Issue Notification, now U.S. Pat. No. 8,886,739. |
| U.S. Appl. No. 14/572,920, Dec. 11, 2015, Preliminary Amendment, now U.S. Pat. No. 9,313,155. |
| U.S. Appl. No. 14/572,920, Jan. 15, 2016, Response to Office Action with eTerminal Disclaimers, now U.S. Pat. No. 9,313,155. |
| U.S. Appl. No. 14/572,920, Feb. 18, 2016, Notice of Allowance, now U.S. Pat. No. 9,313,155. |
| U.S. Appl. No. 14/572,920, Feb. 18, 2016, 1.312 Amendment after Notice of Allowance, now U.S. Pat. No. 9,313,155. |
| U.S. Appl. No. 14/572,932, Dec. 9, 2015, Preliminary Amendment, now U.S. Pat. No. 9,313,156. |
| U.S. Appl. No. 14/572,932, Dec. 17, 2015, Office Action, now U.S. Pat. No. 9,313,156. |
| U.S. Appl. No. 14/572,932, Jan. 15, 2016, Response to Office Action with eTerminal Disclaimers, now U.S. Pat. No. 9,313,156. |
| U.S. Appl. No. 14/572,932, Feb. 17, 2016, Notice of Allowance, now U.S. Pat. No. 9,313,156. |
| U.S. Appl. No. 14/572,932, Feb. 18, 2016, 1.312 Amendment after Notice of Allowance, now U.S. Pat. No. 9,313,156. |
| U.S. Appl. No. 14/572,942, Dec. 17, 2015, Preliminary Amendment, now U.S. Pat. No. 9,306,885. |
| U.S. Appl. No. 14/572,942, Dec. 22, 2015, Office Action, now U.S. Pat. No. 9,306,885. |
| U.S. Appl. No. 14/572,942, Jan. 15, 2016, Response to Office Action with eTerminal Disclaimers, now U.S. Pat. No. 9,306,885. |
| U.S. Appl. No. 14/572,942, Feb. 17, 2016, Notice of Allowance, now U.S. Pat. No. 9,306,885. |
| U.S. Appl. No. 14/572,942, Feb. 18, 2016, 1.312 Amendment after Notice of Allowance, now U.S. Pat. No. 9,306,885. |
| U.S. Appl. No. 14/572,952, Dec. 17, 2015, Preliminary Amendment, now U.S. Pat. No. 9,313,157. |
| U.S. Appl. No. 14/572,952, Dec. 23, 2015, Office Action, now U.S. Pat. No. 9,313,157. |
| U.S. Appl. No. 14/572,952, Jan. 15, 2016, Response to Office Action with eTerminal Disclaimers, now U.S. Pat. No. 9,313,157. |
| U.S. Appl. No. 14/572,952, Feb. 18, 2016, Notice of Allowance, now U.S. Pat. No. 9,313,157. |
| U.S. Appl. No. 14/572,952, Feb. 18, 2016, 1.312 Amendment after Notice of Allowance, now U.S. Pat. No. 9,313,157. |
| U.S. Appl. No. 14/572,966, Dec. 3, 2015, Office Action, now U.S. Pat. No. 9,306,886. |
| U.S. Appl. No. 14/572,966, Dec. 23, 2015, Office Action, now U.S. Pat. No. 9,306,886. |
| U.S. Appl. No. 14/572,966, Jan. 15, 2016, Response to Office Action with eTerminal Disclaimers, now U.S. Pat. No. 9,306,886. |
| U.S. Appl. No. 14/572,966, Feb. 18, 2016, Notice of Allowance, now U.S. Pat. No. 9,306,886. |
| U.S. Appl. No. 14/572,966, Feb. 18, 2016, 1.312 Amendment after Notice of Allowance, now U.S. Pat. No. 9,306,886. |
| U.S. Appl. No. 14/572,976, Dec. 10, 2015, Preliminary Amendment, now U.S. Pat. No. 9,338,111. |
| U.S. Appl. No. 14/572,976, Dec. 16, 2015, Office Action, now U.S. Pat. No. 9,338,111. |
| U.S. Appl. No. 14/572,976, Jan. 15, 2016, Response to Office Action with eTerminal Disclaimers, now U.S. Pat. No. 9,338,111. |
| U.S. Appl. No. 14/572,976, Jan. 22, 2016, Applicant Initiated Interview Summary, now U.S. Pat. No. 9,338,111. |
| U.S. Appl. No. 14/572,976, Feb. 18, 2016, Notice of Allowance, now U.S. Pat. No. 9,338,111. |
| U.S. Appl. No. 14/572,976, Feb. 18, 2016, 1.312 Amendment after Notice of Allowance, now U.S. Pat. No. 9,338,111. |
| U.S. Appl. No. 14/572,920, Mar. 10, 2016, Corrected Notice of Allowability, now U.S. Pat. No. 9,313,155. |
| U.S. Appl. No. 14/572,920, Mar. 17, 2016, Corrected Notice of Allowability (2), now U.S. Pat. No. 9,313,155. |
| U.S. Appl. No. 14/572,920, Mar. 24, 2016, Issue Notification, now U.S. Pat. No. 9,313,155. |
| U.S. Appl. No. 14/572,932, Feb. 26, 2016, Office's Response to 312 Amendment, now U.S. Pat. No. 9,313,156. |
| U.S. Appl. No. 14/572,932, Mar. 17, 2016, Corrected Notice of Allowability, now U.S. Pat. No. 9,313,156. |
| U.S. Appl. No. 14/572,932, Mar. 24, 2016, Issue Notification, now U.S. Pat. No. 9,313,156. |
| U.S. Appl. No. 14/572,942, Feb. 26, 2016, Office's Response to 312 Amendment, now U.S. Pat. No. 9,306,885. |
| U.S. Appl. No. 14/572,942, Mar. 11, 2016, Corrected Notice of Allowability, now U.S. Pat. No. 9,306,885. |
| U.S. Appl. No. 14/572,942, Mar. 17, 2016, Issue Notification, now U.S. Pat. No. 9,306,885. |
| U.S. Appl. No. 14/572,952, Mar. 11, 2016, Corrected Notice of Allowability, now U.S. Pat. No. 9,313,157. |
| U.S. Appl. No. 14/572,952, Mar. 17, 2016, Office's Response to 312 Amendment, now U.S. Pat. No. 9,313,157. |
| U.S. Appl. No. 14/572,952, Mar. 24, 2016, Issue Notification, now U.S. Pat. No. 9,313,157. |
| U.S. Appl. No. 14/572,966, Mar. 8, 2016, Corrected Notice of Allowability, now U.S. Pat. No. 9,306,886. |
| U.S. Appl. No. 14/572,966, Mar. 17, 2016, Issue Notification, now U.S. Pat. No. 9,306,886. |
| U.S. Appl. No. 14/572,966, Apr. 14, 2016, Request for Certificate of Correction, now U.S. Pat. No. 9,306,886. |
| U.S. Appl. No. 14/572,976, Mar. 2, 2016, Notice to File Corrected Application Papers, now U.S. Pat. No. 9,338,111. |
| U.S. Appl. No. 14/572,976, Mar. 9, 2016, Response to Notice to File Corrected Application Papers, now U.S. Pat. No. 9,338,111. |
| U.S. Appl. No. 14/572,976, Mar. 14, 2016, Office's Response to 312 Amendment, now U.S. Pat. No. 9,338,111. |
| U.S. Appl. No. 14/572,976, Mar. 24, 2016, Office's Response to 312 Amendment #2, now U.S. Pat. No. 9,338,111. |
| U.S. Appl. No. 14/572,976, Apr. 21, 2016, Issue Notification, now U.S. Pat. No. 9,338,111. |
| U.S. Appl. No. 14/033,135, Apr. 8, 2016, Office Action. |
| U.S. Appl. No. 15/061,351, Jun. 9, 2016, Preliminary Amendment, now U.S. Pat. No. 9,413,711. |
| U.S. Appl. No. 15/061,351, Jun. 27, 2016, Notice of Allowance, now U.S. Pat. No. 9,413,711. |
| U.S. Appl. No. 15/061,351, Jun. 27, 2016, Examiner Initiated Interview Summary, now U.S. Pat. No. 9,413,711. |
| U.S. Appl. No. 15/061,351, Jul. 20, 2016, Issue Notification, now U.S. Pat. No. 9,413,711. |
| PCT/US2006/014254, WO, Oct. 19, 2007, International Search Report and Written Opinion. |
| PCT/US2007/079299, WO, Mar. 18, 2008, International Search Report and Written Opinion. |
| PCT/US2008/054093, WO, Jul. 25, 2008, International Search Report and Written Opinion. |
| PCT/US2013/036723, WO, Aug. 20, 2013, International Search Report and Written Opinion. |
| 2006276974, AU, Feb. 8, 2012, Examiner's Report (No. 2). |
| 2006276974, AU, Aug. 3, 2012, Response to Examiner's Report (No. 2). |
| 2616911, CA, Feb. 25, 2013, Office Action. |
| 2616911, CA, Aug. 23, 2013, Response to Office Action. |
| CN2006-80035550, CN, Jan. 22, 2010, Office Action (English Translation). |
| CN2006-80035550, CN, Dec. 21, 2011, Office Action (English Translation). |
| CN2006-80035550, CN, Jul. 13, 2012, Office Action (English Translation). |
| EU06750321.9, EU, Apr. 13, 2010, Supplementary Search Report. |
| EU06750321.9, EU, Jul. 6, 2010, Response to Search Report. |
| EU06750321.9, EU, Dec. 22, 2011, Examination Report. |
| EU06750321.9, EU, Jun. 22, 2012, Response to Examination Report. |
| 382/KOLNP/2008, IN, May 27, 2014, Examination Report. |
| 2008-523868, JP, Apr. 27, 2011, Office Action (English Letter Translating Objections). |
| 2008-523868, JP, Nov. 7, 2011, Response to Office Action (English Proposed Arguments and Claim Amendments). |
| 7004841/2008, KR, Nov. 2, 2012, Letter Reporting Notice of Preliminary Rejection. |
| TW095119990, TW, Oct. 18, 2012, Translation of Examination Report. |
| TW095119990, TW, May 8, 2013, English Summary of Arguments and Claims Responding to Examination Report. |
| U.S. Appl. No. 11/401,148, filed Apr. 10, 2006, U.S. Pat. No. 7,610,345. |
| U.S. Appl. No. 11/859,777, filed Sep. 23, 2007. |
| U.S. Appl. No. 12/031,845, filed Feb. 15, 2008. |
| U.S. Appl. No. 12/605,885, filed Oct. 26, 2009, U.S. Pat. No. 8,291,026. |
| U.S. Appl. No. 13/447,932, filed Apr. 16, 2012, U.S. Pat. No. 9,282,081. |
| U.S. Appl. No. 13/651,909, filed Oct. 15, 2012. |
| U.S. Appl. No. 13/864,930, filed Apr. 17, 2013. |
| U.S. Appl. No. 14/033,135, filed Sep. 20, 2013. |
| U.S. Appl. No. 14/133,875, filed Dec. 19, 2013, U.S. Pat. No. 8,935,351. |
| U.S. Appl. No. 14/133,897, filed Dec. 19, 2013, U.S. Pat. No. 8,886,739. |
| U.S. Appl. No. 14/572,920, filed Dec. 17, 2014, U.S. Pat. No. 9,313,155. |
| U.S. Appl. No. 14/572,932, filed Dec. 17, 2014, U.S. Pat. No. 9,313,156. |
| U.S. Appl. No. 14/572,942, filed Dec. 17, 2014, U.S. Pat. No. 9,306,885. |
| U.S. Appl. No. 14/572,952, filed Dec. 17, 2014, U.S. Pat. No. 9,313,157. |
| U.S. Appl. No. 14/572,966, filed Dec. 17, 2014, U.S. Pat. No. 9,306,886. |
| U.S. Appl. No. 14/572,976, filed Dec. 17, 2014, U.S. Pat. No. 9,338,111. |
| U.S. Appl. No. 15/149,371, filed May 9, 2016. |
| U.S. Appl. No. 15/061,351, filed Mar. 4, 2016, U.S. Pat. No. 9,413,711. |
| U.S. Appl. No. 15/231,316, filed Aug. 8, 2016. |
| Final Written Decision, Inter Partes Review No. IPR2018-00455 for U.S. Pat. No. 9,313,157, Jul. 31, 2019. |
| Final Written Decision, Inter Partes Review No. IPR2018-00416 and Inter Partes Review No. IPR2018-00439, both for U.S. Pat. No. 9,413,711, Aug. 1, 2019. |
| Final Written Decision, Inter Partes Review No. IPR2018-00404 for U.S. Pat. No. 8,935,351, dated Jun. 28, 2019. |
| Final Written Decision, Inter Partes Review No. IPR2018-00200 for U.S. Pat. No. 8,886,739, dated Jun. 4, 2019. |
| Final Written Decision, Inter Partes Review No. IPR2018-00369 for U.S. Pat. No. 9,313,155, dated Jun. 28, 2019. |
| Final Written Decision, Inter Partes Review No. IPR2018-00312 for U.S. Pat. No. 9,306,885, dated Jun. 14, 2019. |
| Final Written Decision, Inter Partes Review No. IPR2018-00397 for U.S. Pat. No. 9,306,886, dated Jun. 28, 2019. |
| Final Written Decision, Inter Partes Review No. IPR2018-00408 for U.S. Pat. No. 9,338,111, dated Jun. 28, 2019. |
| Number | Date | Country | |
|---|---|---|---|
| 20190215296 A1 | Jul 2019 | US |
| Number | Date | Country | |
|---|---|---|---|
| 60703367 | Jul 2005 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 15231316 | Aug 2016 | US |
| Child | 16356821 | US | |
| Parent | 15061351 | Mar 2016 | US |
| Child | 15231316 | US | |
| Parent | 13447932 | Apr 2012 | US |
| Child | 15061351 | US | |
| Parent | 11401148 | Apr 2006 | US |
| Child | 12605885 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 12605885 | Oct 2009 | US |
| Child | 13447932 | US |
