Dynamic location of a subordinate user

Information

  • Patent Grant
  • 9621376
  • Patent Number
    9,621,376
  • Date Filed
    Monday, January 30, 2012
    12 years ago
  • Date Issued
    Tuesday, April 11, 2017
    7 years ago
Abstract
Providing location information to a supervisory user includes providing a parental control, using a computer automatically to determine a location of a subordinate user, and storing location information indicative of the location of the subordinate user in a database. A request of the supervisory user to locate the subordinate user is received and a user interface informs the supervisory user of the location of the subordinate user based on the stored location information. At least one of the storing and/or the informing are based on the parental control.
Description
TECHNICAL FIELD

This invention relates to location of a subordinate user.


BACKGROUND

Communication technologies, such as mobile phones and the internet, have proliferated. As a result, children have ever greater freedom to move within the information world, and to do so from a variety of physical locations. Not all locations, however, are age appropriate, and the mobility and pervasiveness of communication technology may render impractical “eyes-on” supervision of the locations visited by a child or other user. “Eyes-on” supervision, moreover, generally reduces a child's sense of autonomy, and may require inordinate parental involvement.


SUMMARY

In one general aspect, providing location information to a supervisory user includes providing a parental control, using a computer automatically to determine a location of a subordinate user, and storing location information indicative of the location of the subordinate user in a database. A request of the supervisory user to locate the subordinate user is received and a user interface informs the supervisory user of the location of the subordinate user based on the stored location information. At least one of the storing and the informing are based on the parental control.


Implementations may include one or more of the following features. For example, providing the location information may include using the computer to determine a changed location of the subordinate user, using the database to update the stored location information based on the changed location, and using the user interface to inform the supervisory user of the changed location based on the updated stored location information. Informing the supervisory user of the changed location may include refreshing the information communicated by the user interface based on a predetermined interval.


Storing the location information may include storing an indication of the present location of the subordinate user. Location information indicative of past locations of the subordinate user also may be stored and the supervisory user may be informed of a past location of the subordinate user. The database may store the location information in relation to the subordinate user.


The supervisory user and the subordinate user may be associated through a familial relationship, and may hold related online accounts.


The parental control may include a white list indicative of an online location approved for visitation by the subordinate user and/or a black list indicative of an online location disapproved for visitation by the subordinate user. Providing location information may include informing the supervisory user of locations visited by the subordinate user that are included on the black list but not of locations that are included on the white list.


The parental control may indicate a range of location information of which the supervisory user desires to be informed. For example, the parental control may indicate that the supervisory user is to be informed of a predetermined number of the most recent locations visited by the subordinate user, of the locations most frequently visited by the subordinate user, and/or of the locations visited by the subordinate user within a defined period of time. The parental control also may include a textual analysis rule.


Determining the location of the subordinate user may include determining an online location and location information associated with the online location. The location information may include, for example, a universal resource locator (URL), an internet protocol (IP) address, and/or an identifier of an internet domain associated with the online location. The location information may include a television channel and/or an identification of a television program. The supervisory user may be enabled dynamically to access the online location of the subordinate user based on the location information.


Determining the location of the subordinate user also may include determining a physical location of the subordinate user, for example, based on information communicated by a global positioning system (GPS). Location information describing the physical location may include a physical address, a longitude and/or a latitude, and/or a name of a physical location.


The request of the supervisory user for information may include an identification (e.g., a screen name) of the subordinate user from a contact list of the supervisory user.


The supervisory user also may be enabled to communicate with the subordinate user in relation to a location visited by the subordinate user. The communication between the supervisory user and the subordinate may be enabled using an instant message, an email, a voice communication, and/or any other suitable electronic communication.


These general and specific aspects may be implemented using a method, a system, or a computer program, or any combination of systems, methods, and computer programs.


Other features will be apparent from the description, the drawings, and the claims.





DESCRIPTION OF DRAWINGS


FIGS. 1-3 illustrate graphical user interfaces (GUIs) that may be used by a supervisory user to dynamically locate a subordinate user.



FIG. 4 is a schematic diagram of a system for dynamically locating a subordinate user.



FIG. 5 is a flow diagram of a process implementable by the system of FIG. 5.



FIG. 6 is a schematic diagram of a user location system.



FIGS. 7A-7C are flow diagrams illustrating exemplary processes implementable by the user location system of FIG. 6.





Like reference symbols in the various drawings indicate like elements.


DETAILED DESCRIPTION

An online service provider may enable an online user to determine dynamically and in real time the location of another user, such as, for example, a child or other subordinate user. For instance, the user may perceive a web page or URL presently viewed by the other user, a physical location of the other user, and/or a log of the past online activity of the subordinate user.



FIG. 1 illustrates a graphical user interface 100 (buddy list interface) that a supervisory user (e.g., a parent or guardian) may use to locate another user (e.g., a subordinate user such as a child). The buddy list interface 100 lists contacts 105 (e.g., buddies) of the supervisory user. The listed contacts may be identified to the supervisory user using textual and or graphical identifiers, such as, for example, a name (e.g., a screen name) and/or an icon. A subordinate user 107 may be identified from among the other contacts based on an additional identifier. For example, buddy list interface 100 uses a star icon 109 to the right of HollingworthJT to identify HollingworthJT as a subordinate user. In addition or as an alternative, other forms of identification may be used. For example, the subordinate user may be listed in a separate group (e.g., a subordinate user group or a family group), and/or the identifier of the subordinate user may be highlighted visually.


The supervisory user may use a button 110 (the “Show” button) to select between various formats for listing the subordinate user 107 and other contacts of the supervisory user. The supervisory user may use a button 115 (the “Setup” button) to control the location information that is gathered with respect to the subordinate user 107 and/or how that information is presented.


Referring to FIG. 2, the buddy list interface 100 enables the supervisory user to obtain information related to the subordinate user 107, such as, for example, location information. For instance, the supervisory user may pause or “float” a cursor 205 over the name of the subordinate user 107 to obtain a snapshot 210 of the subordinate user's location and online activity. As illustrated, the snapshot 210 indicates that HollingworthJT presently is online and is visiting “Top Ten Games” at the Games Channel. The snapshot 210 also indicates that HollingworthJT is at home and has been online for 1 hour and 54 minutes. More complete location information may be accessed by opening (e.g., by double clicking) the name of the subordinate user 107 or by using a button 215 (the “Buddy Info” button) after selecting (e.g., by single clicking) the name of the subordinate user 107.


In addition, the supervisory user may communicate with the subordinate user 107 or with another contact using a button 220 (the “Send IM” button) to initiate an instant message or a button 225 (the “Buddy Chat” button) to initiate a chat session. The supervisory user also may use a button 230 (the “Address Book” button) to add or modify contact information for the subordinate user 107 or for other contacts.



FIG. 3 illustrates a buddy info interface 300 that may be invoked from the buddy list interface 100 of FIG. 1 or based on an alert trigger, for example, of a parental control. The buddy info interface 300 shows or provides access to more complete location information related to the subordinate user 107. The buddy info interface 300 also may be invoked to obtain information related to the other listed contacts 105; however, the information for a particular contact 105 may be less detailed and/or subject to consent of the selected contact 105. Referring to FIG. 1, the buddy info interface 300 may be invoked, for example, by opening the name of the subordinate user 107 or by using the “Buddy Info” button 215 after selecting the name of the subordinate user 107.


Referring again to FIG. 3, the buddy info interface 300 includes an ID bar 305 that identifies the subordinate user 107 for whom information is provided. The buddy info interface 300 also includes an information panel 310 that indicates the current online location of the subordinate user 107. For example, the information panel 310 indicates that HollingworthJT presently is visiting the Top Ten Games page at the Gaming Channel and has been online for 1 hour and 54 minutes. The location information presented in the information panel 310 may be updated at predetermined intervals or dynamically as HollingworthJT moves to a different location. The supervisory user may use a button 315 (the “Join Me” button) to access the present online location of the subordinate user 107, such as, for example, to visit the web page, URL, or chat room presently accessed by the subordinate user 107.


Additionally, or in the alternative, the information panel 310 may indicate a physical location of the subordinate user 107. The physical location may be determined, for example, based on a known physical location of a non-mobile device (e.g., a workstation or a desk-top personal computer) or based on location information provided by a GPS (global positioning system) associated with a mobile device (e.g., a notebook computer, a personal digital assistant, or a mobile telephone) of the subordinate user 107.


The supervisory user may use a button 320 (the “Show Full Log” button) to access a location log (e.g., the location log 330 of the supervisory user 107, HollingworthJT) of present and past location information related to the subordinate user 107. The location log 330 may display location information according to a predetermined window. The window may define a predetermined period of interest, such as, for example, the past twenty-four hours, the current day (e.g., Mar. 11, 2004, as shown), the current week, or any other desired period of time. Other types of windows also may be used (e.g., to define a number of most recently or frequently visited locations).


As shown, the location log 330 indicates present location information 335 related to HollingworthJT (i.e., that HollingworthJT presently is online visiting the Gaming Channel from home). The location log 330 also indicates location information 340 from prior in the day. Specifically, the location log 330 shows that HollingworthJT visited the Math site at the Education channel and also CoolMath.com from school; that HollingworthJT visited the site Casino.com from an unknown location; that, while at school, HollingworthJT was blocked from accessing (e.g., based on an over-inclusive black list) a site on Asexual Plants at the Botany Channel; and that HollingworthJT visited the Message Center from home.


The supervisory user may use the information of the location log 330 to judge, for example, the appropriateness of locations visited by the subordinate user 107, and may use the control panel 350 to respond accordingly. For example, the supervisory user may use the location log 330 to note that HollingworthJT visited the site Casino.com and may determine that Casino.com is inappropriate for the subordinate user 107 to visit. Consequently, the supervisory user may use a button 355 (the “Send IM” button) or a button 360 (the “Send Mail” button) to communicate with the subordinate user regarding the location visited. Specifically, the supervisory user may communicate with HollingworthJT regarding the visit to Casino.com; and may wish to know why HollingworthJT was not at school then, and from where access was made. The supervisory user also may use a button 365 (the “Block Site” button) to block Casino.com from future access by HollingworthJT. In the alternative, the supervisory user may use a button 370 (the “Clear Site” button) to clear a site (e.g., the Asexual Plate site of the Botany Channel) that the supervisory user deems unobjectionable but for which the subordinate user 107 was blocked access.


The supervisory user also may use a button 375 (the “Parental Controls” button) to provide or modify a parental control used to supervise locations visited by the subordinate user 107. The parental control may include age-appropriate default settings that apply to different age classes of users, such as, for example, subordinate users classified as “Kids,” “Young Teens,” or “Mature Teens.” The parental control may include one or more alert triggers that may cause the supervisory user to be quickly notified if the subordinate user visits a particular location or type of location.


The parental control also may include notification information to control delivery of the notification, for example, based on location information of the supervisory user. The location information, whether for a physical or an online location, may be determined similarly to the location of the subordinate user. In any event, the notification information and/or the location information may be used to select among several delivery mechanisms potentially available to the supervisory user. Delivery of the notification based on the location information enhances the likelihood that the notification is received by the supervisory user without significant delay.


In addition or in the alternative to the age-appropriate default settings, the parental control may include a white list defining approved locations (e.g., online educational sites, school, a friend's home) and/or a black list defining a domain of unacceptable locations (e.g., online gambling sites, a local pool hall, the home of a disapproved friend) for which visitation is disapproved. The white list and/or black list may be based on input of a rating authority or by a community of raters. The alert triggers may be used in conjunction with the white list and/or the black list. For example, an alert may indicate the arrival of the subordinate user to a white listed location (e.g., school or a friend's home). On the other hand, an alert also may be triggered when the subordinate user visits a black listed location. Although the white list or the black list may be provided initially as a default, the supervisory user may be enabled to modify or replace either the white list or the black list to better fit the supervisory user's preferences.


The parental control may include a time component used to supervise the times during which online access is permitted. For example, the supervisory user may restrict online access between the hours of 5:30 pm and 7:30 am during the school week, but may allow online access with less restriction in the afternoon after school, on the weekends while the subordinate user 107 is not at school, and during school with respect to school related activities. The time component of the parental control also may control the amount of time during a predetermined period (e.g., the present day, the present week, the preceding twenty-four hours) that the subordinate user 107 may access online sites. The alert triggers also may be used to generate a notification when the subordinate user disregards the time based parental controls.


The parental control may be used to control logging or reporting of the location of the subordinate user 107. The parental control may designate that all locations or only some locations visited by the subordinate user 107 are to be logged. The parental control may indicate that access to locations may be logged based, for example, on an approval status (e.g., based on a white list or a black list). Locations also may be logged based on a time constraint, such as, for example, whether the location is accessed at a non-approved time or is accessed for greater than an approved time. The parental control may indicate that logged locations are to be provided with an access time stamp and/or with an indication of the duration of access.



FIG. 4 shows a generalized system 400 used to identify dynamically to a supervisory user 405 locations visited by a subordinate user 407. The supervisory user 405 and the subordinate user 407 may be related through a familial relationship (e.g., a parent-child relationship) and may hold related online accounts. In any event, the system 400 identifies the locations visited by the subordinate user 407 using a dynamic user location system 420. The dynamic user location system 420 includes a determination service 425, an information management service 430, and an informing service 435.


The determination service 425 may be configured to determine the location 410 (e.g., an online location and/or a physical location) of the subordinate user 407, and to communicate information indicative of the location 410. The location 410 may include an online location of the subordinate user 407, such as, for example, a location of the subordinate user 407 at a particular URL (uniform resource locator), chat-room, message board, or newsgroup. The location 410 also may include a physical location determined, for example, from GPS information of a mobile device, identification information (e.g., an internet protocol address, a phone number) of a fixed device having a known physical location, or location information maintained within a fixed or mobile device. The determination service 425 may employ one or more protocols to transfer information internally or to communicate with other components of the dynamic user location system 420.


The information management service 430 maintains information (e.g., present location, log information of past locations, time stamp information, parental control information, identification information and/or contact information) related to the subordinate user 407. The information management service 430 may modify or recharacterize location information obtained from the determination service 425 (e.g., using a map of online or physical location to determine generalized location information), for example, to enable presentation of the location information in a more useful form. In any event, based on the parental control information and/or system default information, the information management service 430 may store some or all of the location information and may manage that information in relation to an identifier of the subordinate user 407. Similarly, the information management service 430 may remove from storage some or all of the location information as indicated by the parental controls and/or system default information. Storing only the information required may improve scalability of the system 400. For example, based on a parental control, the information management service 430 may retain only location information that satisfies a predetermined window (e.g., that falls within a predetermined time period such as a rolling twenty-four hour period or the present week).


The informing service 435 is configured to interface between the supervisory user 405 and the information management service 430. For example, the informing service 435 may be configured to receive a request from the supervisory user 405 for location information related to the subordinate user 407. Based on the request, the informing service 435 is configured to query the information management service 430 for location information related to the subordinate user 407 and to communicate that information to the supervisory user 405, using, for example, the online interface 415. The online interface 415 may correspond generally to the GUIs described above with respect to FIGS. 1-3. The informing service 435 also may be configured as a conduit by which the supervisory user 405 may access and configure parental controls, and/or other control information or parameters maintained, for example, by the information management service 430.


The informing service 435 may enable the supervisory user 405 to communicate with the subordinate user 407, for example, in relation to the location information.


The informing service 435 also may enable the supervisory user 405 to modify the presentation of the location information related to the subordinate user 407 (e.g., to select among different views or detail levels of the location information as shown in FIGS. 1-3), to obtain related follow-on information, and/or to select or filter information based on various criteria (e.g., based on a selected time period or a specified parental control).


In determining or providing location information, the dynamic user location system 420 may control (or allow the supervisory user 405 to control) the resolution at which the location of the subordinate user 407 is determined or reported. The resolution control function may be performed individually or in combination by one or more of the determination service 425, the information management service 430 and/or the informing service 435.


For example, the determination service 425 may determine a specific location (e.g., a specific web page viewed or an exact longitude and latitude) of the subordinate user 407, but may report a more generalized location (e.g., the web site that includes the viewed page or the school that includes the exact longitude and latitude) that may be more useful to the supervisory user 405. Similarly, the information management service 430 may receive exact location information from the determination service 425, but may maintain generalized location information based on stored or accessed location mapping information. This generalized information may be maintained in addition to or as an alternative to the exact location information. In like manner, the informing service 435 may inform the user 405 of a generalized location that the informing service 435 has determined based on exact location information and location mapping information obtained from the information management service 430. Other functional allocations are possible.


The elements of system 400 may include additional mechanisms for delivering or processing data. The mechanisms may include, for example, any applications, protocols, devices, or networks used to facilitate communication or processing of electronic data. The system elements also may include or be included in a general-purpose or a special-purpose computer, a database, a local area network (LAN), and/or a wide area network (WAN). The response to and execution of instructions received by the system elements may be controlled, for example, by a program, a piece of code, an instruction, a device, a computer system, or a combination thereof, for independently or collectively instructing the system elements to interact and operate as described.



FIG. 5 illustrates a flow diagram of a process 500 implementable by system 400 of FIG. 4 to identify dynamically to the supervisory user 405 a location of the subordinate user 407. The determination service 425 determines a location (e.g., an online location or a physical location) of the subordinate user 407 (step 505). The information management service 430 stores information indicative of the location of the subordinate user 407 using, for example, a database record associated with the subordinate user 407 (step 510). The informing service 435 receives a request from the supervisory user 405 to locate the subordinate user 407 (step 515). The informing service 435 then informs the supervisory user 405 of the location of the subordinate user 407 based on the stored location information. The informing service 435 may inform the supervisory user 405 using, for example, a pop-up window, a list, a graph, or any other appropriate mechanism. The informing service 435 may inform the supervisory user 405 of the location of the subordinate user 407 in a fashion suitable to enable the supervisory user 405 to communicate (e.g., in real time) with the subordinate user 407.


Referring to FIG. 6, a generalized system 600 identifies dynamically to a supervisory user 605 a location of a subordinate user 607. To this end, the system 600 uses a dynamic user location system 620 having a determination service 630, an information management service 630, and an interface service 635. Components of the location system 600 are described in greater detail below.


The subordinate user 607 may use a communication device 608 at a physical location 609 to visit an online location 610 included within a network 612. The communication device 608 may be configured to provide the subordinate user 607 with online access to the network 612. More generally, the communication device 608 may include any device, system, and/or piece of code that enables the subordinate user 607 to communicate with another device or service. For example, the communication device 608 may include a device such as a notebook computer, a telephone, a pen-enabled computer, a personal digital assistant (PDA), a mobile telephone, and/or a desktop computer. Components of the communication device 608 may include a global positioning system (GPS), a Web browser, an email client, a synchronization client (e.g., a calendar synchronization client or a task list synchronization client), an instant messaging (IM) client, a business productivity application (e.g., a word processing or spreadsheet program), and/or an operating system or operating system kernel residing on a device. The communication device 608 may be arranged to operate within or in concert with one or more other systems, such as, for example, one or more LANs and/or one or more WANs.


The network 612 (e.g., the internet) typically allows direct or indirect communication between the communication device 608 and the dynamic user location system 620, irrespective of physical or logical separation. The network 612 also may allow direct or indirect communication between the supervisory user 605 and the dynamic user location system 620, and between the supervisory user 605 and the subordinate user 607. The network 612 may access or include various sources of information, such as, for example, third party information or services, email, a discussion group, a chat room, a news service, a broker service, a banking service, a shopping service, a weather service, the World Wide Web, or other internet information sources.


The network 612 may employ one or more protocols (i.e., standards, formats, conventions, rules, and structures) to transfer information internally or deliver information to one or more users. The protocols may include, for example, the internet protocol (IP), the transmission control protocol (TCP), the hypertext transfer protocol (HTTP), the file transfer protocol (FTP), the user datagram protocol (UDP), the layer two tunneling protocol (L2TP) and/or the simple mail transfer protocol (SMTP). The network 612 may include, for example, the internet, the World Wide Web, a WAN, a LAN, analog or digital wired and wireless telephone networks (e.g., PSTN, ISDN, or xDSL), radio, television, cable, satellite, and/or any other delivery mechanism for carrying data. The network 612 may be secured or unsecured, public or private.


The dynamic user location system 620 may enable the supervisory user 605 to interact online with the subordinate user 607, and to do so, for example, by using instant messaging or email. The dynamic user location system 620 also may enable the supervisory user 605 to interact with the subordinate user 607 using a voice communication provided, for example, using a wireless mobile device. The dynamic user location system 620 allows the supervisory user 605 to view present and past locations of the subordinate user 607 so that the supervisory user 605 may determine the desirability of or need for communicating with the subordinate user 607.


In one implementation, the dynamic user location system 620 works to identify a television program viewed by the subordinate user 607. The dynamic user location system 620 may enable the supervisory user 605 to join the subordinate user 607 in viewing the television program and/or to interact during the television program with the subordinate user 607, using, for example, instant messaging and/or any other appropriate form of electronic messaging. The ability to interact dynamically and in real time with the subordinate user 607 (e.g., a child) may significantly enhance the real and perceived value of television programming by aiding parents, perhaps while away from their children, to participate in or monitor their children's viewing experience.


The dynamic user location system 620 includes a determination service 625 to determine dynamically the locations (e.g., online and/or physical) of the subordinate user 607. To make this determination with respect to online location 610, the determination service 625 may monitor dynamically the online activities of the subordinate user 607, such as, for example, the opening of a Web page of the network 612, focus upon an opened web page (e.g., by clicking on an open Web page or a portion thereof), and/or entry into a chat room or a news group. With respect to the physical location 609, the determination service 625 may obtain location information from a GPS of the communication device 608. The determination service 625 also may determine physical location 609 from location information stored by communication device 608 and/or based on location information accessed by the determination service 625 in relation to an identifier of the communication device (e.g., an internet protocol address, a phone number, an area code or a screenname). Having determined physical location information related to the subordinate user 607, the determination service 625 may communicate that information to the information management service 630.


The information management service 630 is similar generally to the information management service 430 of FIG. 4. To manage information related to the subordinate user, the information management service 630 may include and/or access a database service 631 and a parental control service 633. The database service 631 may include a database, such as, for example, a relational database, for storing or referencing information related to online and/or physical locations visited by the subordinate user 607. In general, the location information includes information, such as, for example, an identification of a physical location (e.g., a longitude and latitude, an address, a neighborhood or a town or city) and/or an online location (e.g., a URL, a web site, a chat room or a news group). The database service 631 also may store or reference notification information or information identifying a physical and/or online so location of the supervisory user to provide notifications to the supervisory user in response to alert triggers.


The location information may identify a location based on a hierarchical relationship. For example, the location information may identify as within the same location an online news site and web pages hierarchically associated with that site, or a television channel and programming associated with that channel.


In any event, the database service 631 may add or remove location information from the database in view of parental controls and/or system defaults. For example, the database service 631 may record only locations that have been visited but that have not been pre-approved (e.g., through the parental controls based on a white list). The database service 631 also may remove from the database (e.g., allow to be overwritten by the database) information that was stored previously but that relates to locations visited outside of a designated interest window (e.g., information relating to a location visited 48 hours ago when the window of interest is the preceding 24 hours).


The parental controls service 633 may enable parental controls similar to those accessed using the “Parental Controls” button 375 of FIG. 3. In general, the parental controls service 633 may be configured to allow a parent (e.g., the supervisory user 605) to control the monitoring of the locations visited by a child (e.g., the subordinate user 607). The parental controls service 633 also may enable a parent to establish or configure alert triggers in order to receive notifications based on compliance or non-compliance with the parental controls. The parental controls service 633 may employ a white list and/or a black list, as described relative to button 375 of FIG. 3, and the parent may be enabled to modify the white list or the black list. For example, the parent may decide to remove from a black list a Tom and Jerry® cartoon web site placed on the black list because of cartoon violence.


The parental controls service 633 may be configured to permit the supervisory user 605 to define a window of location information of which the supervisory user 605 wishes to be informed. For example, the supervisory user 605 may specify a time window that is either fixed (e.g., Mar. 13, 2004) or moving (e.g., the last 24 hours) for which the supervisory user 605 desires location information. The supervisory user 605 also may specify a numerical window that indicates a desire for location information regarding a specified number of the locations most recently visited and/or most frequently visited (e.g., the ten locations most recently or frequently visited) by the subordinate user 607.


The parental controls service 633 may screen a location based upon an analysis of text and/or a label associated with the location. For example, the parental controls service 633 may analyze the language of an online site to determine whether the online site includes inappropriate subject matter. Textual analysis may indicate, for instance, that visits to an online site should be reported because the online site relates to gambling (e.g., based on language that includes “gambling,” “sportbook,” “jackpot,” “casino,” “bonus,” “bingo,” “roulette,” “odds,” “house,” and/or “blackjack”). In another example, a physical location may be identified for reporting as a pool hall based on an associated label including the term “billiards.” In addition, or in the alternative, the location label may include an express identification of the age appropriateness of the location. The parental controls service 633 may enable a child's parent to select or modify the information or algorithms used to screen the locations based on the textual analysis.


The parental controls service 633 additionally may enable the parent to place a time based restriction on the child's visit to a location. For example, a visit to a friend's home may be restricted during school or homework hours, or visits to online locations may be restricted to no more than forty-five minutes a day. Other recognized control techniques also may be applied by the parental controls service 633.


The database service 631 and the parental controls service 633 may or may not be incorporated within the same hardware and/or software device, depending, for example, on an anticipated workload of the information management service 630. Structuring the information management service 630 to include a separable database service 631 and parental controls service 633 may improve the scalability of the information management service 630.


The dynamic user location system 620 also includes an interface service 635. The interface service 635 communicates between the supervisory user 605 and the information management service 630. The interface services 635 may include a print service, a file access service, an IM service, an operating system, an operating system kernel, an authentication service, an authorization service, and/or any combination of these or other services.


More specifically, the interface service 635 includes an informing service 636 and a control service 638 to communicate between the supervisory user 605 and the information management service 630. The control service 638 is configured to communicate requests, instructions, and/or configuration information from the supervisory user 605 to the information management service 630. For example, the control service 638 may be configured as a conduit by which the supervisory user 605 may access and configure parental controls and/or other control information or parameters maintained, for example, by the parental controls service 633 of the information management service 630. The supervisory user 605 also may use the control service 638 to query the database service 631 for location information related to the subordinate user 607.


The informing service 636 is configured to communicate information from the information management service 630 to the supervisory user 605. For example, in response to a query provided through the control service 638, the informing service 636 may communicate to the supervisory user 605 the current parental control configuration and/or system defaults maintained by the parental controls service 633. The informing service 636 also may communicate to the supervisory user 605 location information of the subordinate user 607 provided by the database service 631. The informing service may use the online interface 615 as a conduit to communicate information to the supervisory user 605.


The online interface 615 may correspond generally to the GUIs described with respect to FIGS. 1-3. For example, the online interface 615, alone or in conjunction with the interface service 635, may enable the supervisory user 605 easily to communicate with the subordinate user 607 in relation to the location information or otherwise. The supervisory user 605 may be enabled to modify the presentation of the location information related to the subordinate user 607 (e.g., to select among different views or detail levels of the location information as shown in FIGS. 1-3), to obtain related follow-on information, and/or to select or filter information based on various criteria (e.g., based on a selected time period or a specified parental control).


The online interface 615 may receive location information from the dynamic user location system 620 based on a query of the online interface 615. The online interface 615 also may receive location information from the dynamic user location system 620 automatically after a change in the subordinate user's location and/or at any time that the logged location information changes. For example, the online interface 615 may receive updated location information at short periodic intervals, such as, for example, every 30 or 60 seconds. In any event, the online interface 615, alone or in conjunction with the dynamic user location system 620, may perform sorting, prioritizing, or other types of organizational processing on the location information presented to the supervisory user 605 so that the location information is provided in a desired fashion. Typically, the online interface 615 and/or the dynamic user location system 620 will include a software program or a piece of code to cause the operation described above.


The online interface 615 may receive and present information to the supervisory user 605 using a standard protocol, such as, for example, the standard generalized markup language (SGML), the extensible markup language (XML), the hypertext markup language (HTML), the extensible hypertext markup language (XHTML), the compact hypertext markup language (cHTML), the virtual reality markup language (VRML), the wireless markup language (WML), the voice extensible markup language (VXML), the short message service (SMS), a document object model (DOM), the simple object access protocol (SOAP), or the dynamic hypertext markup language (DHTML). The online interface 615 may present the information to the supervisory user 605 in a manner that enables the supervisory user 605 to respond to, or to interact with, the presented information.


The dynamic user location system 620 may optionally be incorporated within the same hardware or software device, depending, for example, on an anticipated workload. The dynamic user location system 620 also may be implemented in a logically or physically distributed fashion to improve maintainability, cost, and/or scalability.


Each of the communication device 608, the online interface 615, the network 612, and the dynamic user location system 620 may include further mechanisms for communicating data, such as, for example, the short message service (SMS), the wireless application protocol (WAP), the transport connection protocol (TCP), the internet protocol (IP), the World Wide Web, one or more LANs, and/or one or more WANs. The communication device 608, the online interface 615, the network 612, and the dynamic user location system 620 also may include analog or digital wired and wireless communications networks, such as, for example, public switched telephone networks (PSTN), integrated services digital networks (ISDN), various types of digital subscriber lines (xDSL), advance mobile telephone service (AMPS), global system for mobile communications (GSM), general packet radio service (GPRS), code division multiple access (CDMA), radio, cable, satellite, and/or other delivery mechanisms for carrying data.


One or more other services may be included in the components of system 600 and/or these components (hereinafter the system services) may be included as part of one or more other services. For example, the system services may include or be included in a general-purpose or a special-purpose computer (e.g., a personal computer, a PDA, or a device specifically programmed to perform certain tasks), a local area network, and/or a wide area network. In either case, the response to and execution of instructions received by any or all of the system services may be controlled by, for example, a program, a piece of code, an instruction, a device, a computer system, or a combination thereof, for independently or collectively instructing the services to interact and operate as described herein.



FIGS. 7A-7C illustrate a method implementable by the dynamic user location system of FIG. 6. The method includes a logging procedure 700 (FIG. 7A) used to monitor the visitation activity of the subordinate user, a maintenance procedure 730 (FIG. 7B) used to maintain stored location information, and an interface procedure 750 (FIG. 7C) used to communicate with the supervisory user. The logging, maintenance, and interface procedures may be performed asynchronously and/or concurrently to each other.


Referring to the logging procedure 700 of FIG. 7A, visitation activity of the subordinate user 607 is monitored for entrance or exit events (step 702). Monitoring continues as long as neither an entrance event nor an exit event is detected (steps 704 and 706).


If an entrance event (e.g., entry into a physical location, opening of an online location, focusing on an online location) is detected (step 704), then a user identification and location information related to the visited location is communicated (step 708). If the parental controls and/or system defaults do not indicate that logging is required (step 710), then monitoring of the subordinate user's visitation activity resumes (step 702). Otherwise, if logging is required (step 710), then the location information is stored in a database record associated with the subordinate user to indicate that the subordinate user has visited the location (step 712). An indication also is stored that the location is the present location of the subordinate user (step 714). Thereafter, monitoring resumes (step 702).


In the event that an exit event is detected (step 706), the user identification and location information related to the location exited is communicated (step 716). If the subordinate's user's visit to the location was logged (step 718) then the indication that the subordinate user presently is at that location is cleared (step 720). Thereafter, or if the visit to the exited location was not logged (step 718), monitoring of the subordinate user's visitation activity resumes (step 702). Multiple steps may be performed concurrently.


Referring to FIG. 7B, the maintenance procedure 730 is performed upon a predetermined or automatically determined maintenance interval (step 732). In accordance with the maintenance interval, verification is made that stored location information still qualifies for storage based on the system defaults and/or parental controls (step 734). Verification may include, for example, ensuring that the stored location information continues to satisfy a moving window of interest indicated by the parental controls (e.g., that the location information relates to a visit made within 48 hours of the present time). In any event, stored information that fails presently to satisfy the system defaults and/or parental controls may be removed or purged (step 736). Multiple steps may be performed concurrently.


Referring to the interface procedure 750 of FIG. 7C, a communication of the supervisory user is received (step 752). If the communication is a request for location information (step 754), then stored location information associated with the subordinate user is accessed (step 756). The subordinate user's present location and/or other locations visited by the subordinate user are presented to the supervisory user based on the logged location information (step 758). In addition, the supervisory user may be enabled to act based on the presented location information (step 760). For example, the supervisory user may be enabled to communicate (e.g., via email, instant message, or mobile device) with the subordinate user based on or in relation to a location visited by the subordinate user. In the case of an online location, the supervisory user may be enabled further to join the subordinate user at a present online location or to access past locations visited by the subordinate user.


On the other hand, if the communication is for access to the parental controls (step 762), then the supervisory user may be enabled to view, add to, or otherwise modify the parental controls as desired (step 764). For example, the supervisory user may be enabled to modify or replace either a white list or a black list, to add or modify a time component, and/or to otherwise control or specify logging criteria to control storage or access to location information related to the subordinate user.


For messages of other types (i.e., not relating to a location request or to parental controls), other message handling routines may be employed as appropriate (step 766). In any event, irrespective of the message type received and handled, monitoring continues for other communications of the supervisory user (step 752). Multiple steps may be performed concurrently.


Other implementations are within the scope of the following claims.

Claims
  • 1. A method comprising: receiving, at a client computing device, from an account of a first user, a request to monitor online locations of a second user accessed using a mobile device of the second user while at a geographic location;receiving a black list indicative of one or more online locations disapproved for visitation by the second user while at the geographic location;monitoring, by the client computing device, online locations accessed by the mobile device of the second user while at the geographic location;providing, to the first user via a graphical user interface associated with the account of the first user, a listing of recent online locations accessed by the mobile device of the second user while at the geographic location; andproviding, via the graphical user interface and in conjunction with the listing of recent online locations, an option to add one or more of the recent online locations to the black list.
  • 2. The method of claim 1, wherein the one or more online locations on the black list are approved for visitation by the second user when at locations other than the geographic location.
  • 3. The method of claim 1, wherein the geographic location comprises at least one of a physical address, latitude and longitude, or a name associated with a physical location.
  • 4. The method of claim 1, wherein the online location comprises at least one of a domain name or a URL address.
  • 5. The method of claim 1, further comprising: providing an indication of the mobile device used by the second user to access the at least one disapproved online location.
  • 6. The method of claim 1, wherein the online location comprises at least one of a television channel or a television program identification.
  • 7. The method of claim 1, further comprising: enabling the first user to access the online location of the second user.
  • 8. The method of claim 1, further comprising: receiving a selection of the option to add one or more of the recent online locations to the black list; andpreventing the mobile device from accessing the one or more of the recent online locations while at the geographic location.
  • 9. A non-transitory computer-readable medium having stored thereon executable instructions that, when executed by at least one processor, cause the at least one processor to: receive, from an account of a first user, a request to monitor online locations of a second user accessed using a mobile device of the second user while at a geographic location;receive a black list indicative of one or more online locations disapproved for visitation by the second user while at the second location;monitor online locations accessed by the mobile device of the second user while at the geographic location;provide, to the first user via a graphical user interface associated with the account of the first user, a listing of recent online locations accessed by the mobile device of the second user while at the geographical location; andprovide, via the graphical user interface and in conjunction with the listing of recent online locations, an option to add one or more of the recent online locations to the black list.
  • 10. The computer-readable medium of claim 9, wherein the one or more online locations on the black list are approved for visitation by the second user when at locations other than the geographic location.
  • 11. The computer-readable medium of claim 9, wherein the geographic location comprises at least one of a physical address, latitude and longitude, or a name associated with a physical location.
  • 12. The computer-readable medium of claim 9, wherein the online location comprises at least one of a domain name or a URL address.
  • 13. The computer-readable medium of claim 9, wherein the instructions, when executed by the at least one processor, further cause the at least one processor to: provide an indication of the mobile device used by the second user to access the at least one disapproved online location.
  • 14. The computer-readable medium of claim 9, wherein the online location comprises at least one of a television channel or a television program identification.
  • 15. The computer-readable medium of claim 9, wherein the instructions, when executed by the at least one processor, further cause the at least one processor to: enable the first user to access the online location of the second user.
  • 16. The computer-readable medium of claim 9, wherein the instructions, when executed by the at least one processor, further cause the at least one processor to: receive a selection of the option to add one or more of the recent online locations to the black list; andprevent the mobile device from accessing the one or more of the recent online locations while at the geographic location.
  • 17. A system for monitoring and providing information comprising: a processor; anda memory, wherein the memory stores instructions that, when executed by the processor, cause the system to:receive, from an account of a first user, a request to monitor online locations of a second user accessed using a mobile device of the second user while at a geographic location;receive a black list indicative of one or more online locations disapproved for visitation by the second user while at the geographic location;monitor online locations accessed by the mobile device of the second user while at the geographic location;provide, to the first user via a graphical user interface associated with the account of the first user, a listing of recent online locations accessed by the mobile device of the second user while at the geographic location; andprovide, via the graphical user interface and in conjunction with the listing of recent online locations, an option to add one or more of the recent online locations to the black list.
  • 18. The system of claim 17, wherein the one or more online locations on the black list are approved for visitation by the second user when at location other than the geographic location.
  • 19. The system of claim 17, wherein the geographic location comprises at least one of a physical address, latitude and longitude, or a name associated with a physical location.
  • 20. The system of claim 17, wherein the online location comprises at least one of a domain name or a URL address.
  • 21. The system of claim 17, wherein the memory further stores instructions that, when executed by the processor, cause the system to: provide an indication of the mobile device used by the second user to access the at least one disapproved online location.
  • 22. The system of claim 17, wherein the online location comprises at least one of a television channel or a television program identification.
  • 23. The system of claim 17, wherein the memory further stores instructions that, when executed by the system, cause the processor to: enable the first user to access the online location of the second user.
  • 24. The system of claim 17, wherein the memory further stores instructions that, when executed by the system, cause the processor to: receive a selection of the option to add one or more of the recent online locations to the black list; andprevent the mobile device from accessing the one or more of the recent online locations while at the geographic location.
CROSS REFERENCE TO RELATED APPLICATION(S)

This is a continuation of U.S. application Ser. No. 11/574,831, filed Feb. 13, 2009 (now U.S. Pat. No. 8,122,137), which is a U.S. national stage application under 35 U.S.C. §371 of International Application No. PCT/US2004/029291, filed Sep. 8, 2004, all of which are expressly incorporated herein by reference in their entireties.

US Referenced Citations (942)
Number Name Date Kind
4650927 James Mar 1987 A
4817129 Riskin Mar 1989 A
4837798 Cohen et al. Jun 1989 A
5008853 Bly et al. Apr 1991 A
5021949 Morten et al. Jun 1991 A
5025252 DeLuca et al. Jun 1991 A
5086394 Shapira Feb 1992 A
5101424 Clayto et al. Mar 1992 A
5276905 Hurst et al. Jan 1994 A
5315636 Patel May 1994 A
5329619 Page et al. Jul 1994 A
5351235 Lahtinen Sep 1994 A
5425028 Britton et al. Jun 1995 A
5436960 Campana, Jr. et al. Jul 1995 A
5438611 Campana, Jr. et al. Aug 1995 A
5440551 Suzuki Aug 1995 A
5448566 Richter et al. Sep 1995 A
5448567 Dighe et al. Sep 1995 A
5459458 Richardson et al. Oct 1995 A
5479472 Campana, Jr. et al. Dec 1995 A
5487100 Kane Jan 1996 A
5491800 Goldsmith et al. Feb 1996 A
5497463 Stein et al. Mar 1996 A
5499343 Pettus Mar 1996 A
5548637 Heller Aug 1996 A
5557320 Krebs Sep 1996 A
5559949 Reimer et al. Sep 1996 A
5561703 Arledge et al. Oct 1996 A
5568536 Tiller et al. Oct 1996 A
5572643 Judson Nov 1996 A
5579472 Keyworth, II et al. Nov 1996 A
5590133 Billstrom et al. Dec 1996 A
5592538 Kosowsky et al. Jan 1997 A
5594947 Grube et al. Jan 1997 A
5604788 Tett Feb 1997 A
5608786 Gordon Mar 1997 A
5615336 Robson et al. Mar 1997 A
5619648 Canale et al. Apr 1997 A
5625670 Campana, Jr. et al. Apr 1997 A
5631946 Campana, Jr. et al. May 1997 A
5634129 Dickinson May 1997 A
5646982 Hogan et al. Jul 1997 A
5673308 Akhavan Sep 1997 A
5678179 Turcotte et al. Oct 1997 A
5684494 Nathrath et al. Nov 1997 A
5694616 Johnson Dec 1997 A
5697060 Akahane Dec 1997 A
5706211 Beletic et al. Jan 1998 A
5706501 Horikiri Jan 1998 A
5710884 Dedrick Jan 1998 A
5726984 Kubler et al. Mar 1998 A
5737726 Cameron et al. Apr 1998 A
5742668 Pepe et al. Apr 1998 A
5742905 Pepe et al. Apr 1998 A
5749081 Whiteis et al. May 1998 A
5760771 Blonder et al. Jun 1998 A
5761196 Ayerst et al. Jun 1998 A
5764916 Busey et al. Jun 1998 A
5771280 Johnson et al. Jun 1998 A
5774673 Beuk Jun 1998 A
5793365 Tang et al. Aug 1998 A
5793762 Penners et al. Aug 1998 A
5796394 Wicks et al. Aug 1998 A
5796948 Cohen Aug 1998 A
5799157 Escallon Aug 1998 A
5799284 Bourquin Aug 1998 A
5802466 Gallant et al. Sep 1998 A
5802470 Gaulke et al. Sep 1998 A
5812865 Theimer et al. Sep 1998 A
5819084 Shapiro et al. Oct 1998 A
5826025 Gramlich Oct 1998 A
5835089 Skarbo et al. Nov 1998 A
5835722 Bradshaw et al. Nov 1998 A
5835905 Pirolli et al. Nov 1998 A
5845073 Carlin et al. Dec 1998 A
5845300 Comer et al. Dec 1998 A
5864684 Nielsen Jan 1999 A
5864874 Shapiro Jan 1999 A
5867162 O'Leary Feb 1999 A
5870744 Sprague Feb 1999 A
5872521 Lopatukin et al. Feb 1999 A
5878219 Vance, Jr. et al. Mar 1999 A
5878233 Schloss Mar 1999 A
5878397 Stille et al. Mar 1999 A
5895454 Harrington Apr 1999 A
5896321 Miller et al. Apr 1999 A
5897635 Torres et al. Apr 1999 A
5903726 Donovan et al. May 1999 A
5913032 Schwartz et al. Jun 1999 A
5933477 Wu Aug 1999 A
5938725 Hara Aug 1999 A
5940379 Startup et al. Aug 1999 A
5940488 DeGrazia et al. Aug 1999 A
5944791 Scherpbier Aug 1999 A
5946616 Schornack Aug 1999 A
5946617 Portaro et al. Aug 1999 A
5946629 Sawyer et al. Aug 1999 A
5946630 Willars et al. Aug 1999 A
5950193 Kulkarni Sep 1999 A
5960074 Clark Sep 1999 A
5960173 Tang et al. Sep 1999 A
5960429 Peercy et al. Sep 1999 A
5961620 Trent et al. Oct 1999 A
5966663 Gleason Oct 1999 A
5970122 LaPorta et al. Oct 1999 A
5974446 Sonnenreich et al. Oct 1999 A
5978673 Alperovich et al. Nov 1999 A
5987113 James Nov 1999 A
5987376 Olson et al. Nov 1999 A
5999932 Paul Dec 1999 A
6006331 Chu et al. Dec 1999 A
6014429 LaPorta et al. Jan 2000 A
6020884 MacNaughton et al. Feb 2000 A
6026429 Jones et al. Feb 2000 A
6028866 Engel Feb 2000 A
6038451 Syed et al. Mar 2000 A
6041311 Chislenko et al. Mar 2000 A
6049533 Norman et al. Apr 2000 A
6064723 Cohn et al. May 2000 A
6065047 Carpenter et al. May 2000 A
6065056 Bradshaw et al. May 2000 A
6067529 Ray et al. May 2000 A
6067561 Dillon May 2000 A
6073109 Flores Jun 2000 A
6073138 de l'Etraz Jun 2000 A
6076100 Cottrille et al. Jun 2000 A
6081829 Sidana Jun 2000 A
6081830 Schindler Jun 2000 A
6088435 Barber Jul 2000 A
6091948 Carr et al. Jul 2000 A
6091958 Bergkvist et al. Jul 2000 A
6092049 Chislenko et al. Jul 2000 A
6108365 Rubin et al. Aug 2000 A
6112078 Sormunen et al. Aug 2000 A
6112181 Shear Aug 2000 A
6115455 Picard Sep 2000 A
6115605 Siccardo et al. Sep 2000 A
6119014 Alperovich et al. Sep 2000 A
6128739 Fleming, III Oct 2000 A
6134432 Holmes et al. Oct 2000 A
6134582 Kennedy Oct 2000 A
6138146 Moon et al. Oct 2000 A
6138158 Boyle et al. Oct 2000 A
6141545 Begeja et al. Oct 2000 A
6144959 Anderson et al. Nov 2000 A
6148328 Cuomo et al. Nov 2000 A
6148377 Carter Nov 2000 A
6157618 Boss et al. Dec 2000 A
6161129 Rochkind Dec 2000 A
6161130 Horvitz et al. Dec 2000 A
6167256 Yla-Outinen Dec 2000 A
6169911 Wagner et al. Jan 2001 B1
6175831 Weinreich et al. Jan 2001 B1
6175859 Mohler Jan 2001 B1
6178331 Holmes et al. Jan 2001 B1
6185603 Henderson et al. Feb 2001 B1
6189026 Birrell et al. Feb 2001 B1
6192396 Kohler Feb 2001 B1
6195354 Skalecki et al. Feb 2001 B1
6198738 Chang et al. Mar 2001 B1
6199099 Gershman Mar 2001 B1
6199103 Sakaguchi et al. Mar 2001 B1
6208996 Ben-Shachar et al. Mar 2001 B1
6212175 Harsch Apr 2001 B1
6212548 DeSimone et al. Apr 2001 B1
6212550 Segur Apr 2001 B1
6223177 Tatham Apr 2001 B1
6237027 Namekawa May 2001 B1
6237092 Hayes, Jr. May 2001 B1
6243039 Elliot Jun 2001 B1
6243714 Shapiro et al. Jun 2001 B1
6247043 Bates et al. Jun 2001 B1
6252952 Kung et al. Jun 2001 B1
6256516 Wagner et al. Jul 2001 B1
6259911 Bims et al. Jul 2001 B1
6260148 Aggarwal et al. Jul 2001 B1
6269369 Robertson Jul 2001 B1
6282435 Wagner et al. Aug 2001 B1
6292743 Pu et al. Sep 2001 B1
6301609 Aravamudan et al. Oct 2001 B1
6304864 Liddy et al. Oct 2001 B1
6311211 Shaw et al. Oct 2001 B1
6324541 de l'Etraz et al. Nov 2001 B1
6327590 Chidlovskii et al. Dec 2001 B1
6330590 Cotten Dec 2001 B1
6334111 Carrott Dec 2001 B1
6337712 Shiota et al. Jan 2002 B1
6343317 Glorikian Jan 2002 B1
6347332 Malet Feb 2002 B1
6349299 Spencer et al. Feb 2002 B1
6351777 Simonoff Feb 2002 B1
6360251 Fujita et al. Mar 2002 B1
6363248 Silverman Mar 2002 B1
6366907 Fanning Apr 2002 B1
6374246 Matsuo Apr 2002 B1
6374260 Hoffert et al. Apr 2002 B1
6374290 Scharber Apr 2002 B1
6389127 Vardi et al. May 2002 B1
6389372 Glance et al. May 2002 B1
6392669 Matoba et al. May 2002 B1
6393464 Dieterman May 2002 B1
6393465 Leeds May 2002 B2
6396512 Nickerson May 2002 B1
6404438 Hatlelid Jun 2002 B1
6405035 Singh Jun 2002 B1
6415318 Aggarwal et al. Jul 2002 B1
6421439 Liffick Jul 2002 B1
6421675 Ryan Jul 2002 B1
6421709 McCormick et al. Jul 2002 B1
6423012 Kato et al. Jul 2002 B1
6425012 Trovato et al. Jul 2002 B1
6430602 Kay et al. Aug 2002 B1
6430604 Ogle et al. Aug 2002 B1
6434599 Porter Aug 2002 B1
6442589 Takahashi et al. Aug 2002 B1
6442591 Haynes et al. Aug 2002 B1
6446119 Olah et al. Sep 2002 B1
6449344 Goldfinger et al. Sep 2002 B1
6449634 Capiel Sep 2002 B1
6457044 Iwazaki Sep 2002 B1
6457062 Pivowar Sep 2002 B1
6460073 Asakura Oct 2002 B1
6463464 Lazaridis et al. Oct 2002 B1
6463471 Dreke et al. Oct 2002 B1
6466918 Spiegel et al. Oct 2002 B1
6480885 Olivier Nov 2002 B1
6483913 Smith Nov 2002 B1
6484196 Maurille Nov 2002 B1
6487583 Harvey et al. Nov 2002 B1
6487584 Bunney Nov 2002 B1
6493703 Knight et al. Dec 2002 B1
6499053 Marquette Dec 2002 B1
6505167 Horvitz et al. Jan 2003 B1
6507866 Barchi Jan 2003 B1
6512570 Garfinkle et al. Jan 2003 B2
6512930 Sandegren Jan 2003 B2
6519629 Harvey et al. Feb 2003 B2
6519639 Glasser et al. Feb 2003 B1
6519648 Eyal Feb 2003 B1
6529903 Smith et al. Mar 2003 B2
6535228 Bandaru et al. Mar 2003 B1
6535586 Cloutier et al. Mar 2003 B1
6539421 Appelman et al. Mar 2003 B1
6542500 Gerszberg et al. Apr 2003 B1
6549933 Barrett et al. Apr 2003 B1
6549937 Auerbach et al. Apr 2003 B1
6557027 Cragun Apr 2003 B1
6564213 Ortega et al. May 2003 B1
6564261 Gudjonsson et al. May 2003 B1
6564264 Creswell et al. May 2003 B1
6567796 Yost et al. May 2003 B1
6567807 Robles May 2003 B1
6571234 Knight et al. May 2003 B1
6583799 Manolis et al. Jun 2003 B1
6584494 Manabe et al. Jun 2003 B1
6594673 Smith et al. Jul 2003 B1
6604133 Aggarwal et al. Aug 2003 B2
6606647 Shah et al. Aug 2003 B2
6606657 Zilberstein et al. Aug 2003 B1
6611822 Beams Aug 2003 B1
6615237 Kyne et al. Sep 2003 B1
6615241 Miller et al. Sep 2003 B1
6618747 Flynn et al. Sep 2003 B1
6625423 Wang Sep 2003 B1
6628194 Hellebust et al. Sep 2003 B1
6633630 Owens et al. Oct 2003 B1
6636733 Helferich Oct 2003 B1
6636850 Lepien Oct 2003 B2
6636888 Bookspan et al. Oct 2003 B1
6640218 Golding Oct 2003 B1
6640223 Jones et al. Oct 2003 B1
6643641 Snyder Nov 2003 B1
6643669 Novak et al. Nov 2003 B1
6647259 Boyle et al. Nov 2003 B1
6647383 August et al. Nov 2003 B1
6654800 Rieger, III Nov 2003 B1
6658095 Yoakum et al. Dec 2003 B1
6658260 Knotts Dec 2003 B2
6665676 Twig et al. Dec 2003 B2
6665715 Houri Dec 2003 B1
6677968 Appelman Jan 2004 B1
6678719 Stimmel Jan 2004 B1
6684240 Goddard Jan 2004 B1
6687362 Lindquist et al. Feb 2004 B1
6687739 Anupam Feb 2004 B2
6687745 Franco et al. Feb 2004 B1
6691162 Wick Feb 2004 B1
6694353 Sommerer Feb 2004 B2
6697807 McGeachie Feb 2004 B2
6697824 Bowman-Amuah Feb 2004 B1
6697840 Godefroid Feb 2004 B1
6699125 Kirmse et al. Mar 2004 B2
6701343 Kenyon Mar 2004 B1
6701348 Sommerer Mar 2004 B2
6701351 Gann Mar 2004 B1
6704727 Kravets Mar 2004 B1
6708205 Sheldon et al. Mar 2004 B2
6711565 Subramaniam et al. Mar 2004 B1
6714519 Luzzatti et al. Mar 2004 B2
6714791 Friedman Mar 2004 B2
6714793 Carey et al. Mar 2004 B1
6721784 Leonard et al. Apr 2004 B1
6728357 O'Neal et al. Apr 2004 B2
6731308 Tang et al. May 2004 B1
6732103 Strick et al. May 2004 B1
6732155 Meek May 2004 B2
6732185 Reistad May 2004 B1
6750881 Appelman Jun 2004 B1
6751603 Bauer et al. Jun 2004 B1
6754904 Cooper et al. Jun 2004 B1
6757365 Bogard Jun 2004 B1
6757531 Haaramo Jun 2004 B1
6760412 Loucks Jul 2004 B1
6760580 Robinson et al. Jul 2004 B2
6760753 Ohgushi et al. Jul 2004 B1
6760754 Isaacs et al. Jul 2004 B1
6772188 Cloutier Aug 2004 B1
6781608 Crawford Aug 2004 B1
6782414 Xue et al. Aug 2004 B1
6785554 Amerga Aug 2004 B1
6788769 Waites Sep 2004 B1
6799039 Wu et al. Sep 2004 B2
6800031 Di Cesare Oct 2004 B2
6801659 O'Dell Oct 2004 B1
6807562 Pennock et al. Oct 2004 B1
6816884 Summers Nov 2004 B1
6829607 Tafoya et al. Dec 2004 B1
6832245 Isaacs et al. Dec 2004 B1
6839554 McDowell Jan 2005 B2
6839735 Wong et al. Jan 2005 B2
6839737 Friskel Jan 2005 B1
6848008 Sevanto et al. Jan 2005 B1
6848542 Gailey et al. Feb 2005 B2
6853982 Smith et al. Feb 2005 B2
6854007 Hammond Feb 2005 B1
6856999 Flanagin et al. Feb 2005 B2
6868498 Katsikas Mar 2005 B1
6895426 Cortright et al. May 2005 B1
6898626 Ohashi May 2005 B2
6901398 Horvitz et al. May 2005 B1
6901559 Blum May 2005 B1
6904026 Tarnanen et al. Jun 2005 B1
6907243 Patel Jun 2005 B1
6912505 Linden et al. Jun 2005 B2
6912563 Parker et al. Jun 2005 B1
6912564 Appelman et al. Jun 2005 B1
6917813 Elizondo Jul 2005 B2
6917965 Gupta et al. Jul 2005 B2
6920478 Mendiola et al. Jul 2005 B2
6925469 Headings et al. Aug 2005 B2
6931419 Lindquist Aug 2005 B1
6934367 LaPierre et al. Aug 2005 B1
6952805 Tafoya et al. Oct 2005 B1
6957077 Dehlin Oct 2005 B2
6985943 Deryugin et al. Jan 2006 B2
6990628 Palmer et al. Jan 2006 B1
6993325 Waesterlid Jan 2006 B1
6999566 Eason et al. Feb 2006 B1
6999959 Lawrence et al. Feb 2006 B1
7003551 Malik Feb 2006 B2
7003794 Arye Feb 2006 B2
7007008 Goel et al. Feb 2006 B2
7007228 Carro Feb 2006 B1
7010312 Zechlin Mar 2006 B1
7016978 Malik et al. Mar 2006 B2
7020849 Chen Mar 2006 B1
7031961 Pitkow et al. Apr 2006 B2
7032007 Fellenstein et al. Apr 2006 B2
7035865 Doss et al. Apr 2006 B2
7035926 Cohen et al. Apr 2006 B1
7039639 Brezin et al. May 2006 B2
7054918 Polcyn May 2006 B2
7058036 Yu et al. Jun 2006 B1
7058690 Maehiro Jun 2006 B2
7058892 MacNaughton et al. Jun 2006 B1
7062533 Brown et al. Jun 2006 B2
7065186 Myers et al. Jun 2006 B1
7068769 Weaver et al. Jun 2006 B1
7076504 Handel Jul 2006 B1
7076546 Bates et al. Jul 2006 B1
7080139 Briggs et al. Jul 2006 B1
7082407 Bezos et al. Jul 2006 B1
7089237 Turnbull et al. Aug 2006 B2
7089287 Bellotti et al. Aug 2006 B2
7092952 Wilens Aug 2006 B1
7092998 Frietas Aug 2006 B2
7096009 Mousseau et al. Aug 2006 B2
7096030 Huomo Aug 2006 B2
7096214 Bharat et al. Aug 2006 B1
7113803 Dehlin Sep 2006 B2
7117254 Lunt et al. Oct 2006 B2
7124123 Roskind et al. Oct 2006 B1
7127232 O'Neil et al. Oct 2006 B2
7130956 Rao Oct 2006 B2
7133506 Smith Nov 2006 B1
7133898 Malik Nov 2006 B1
7136903 Phillips et al. Nov 2006 B1
7139806 Hayes et al. Nov 2006 B2
7142642 McClelland et al. Nov 2006 B2
7146404 Kay et al. Dec 2006 B2
7146416 Yoo et al. Dec 2006 B1
7162528 Simonoff Jan 2007 B1
7177880 Ruvolo Feb 2007 B2
7181498 Zhu et al. Feb 2007 B2
7185059 Daniell et al. Feb 2007 B2
7188143 Szeto Mar 2007 B2
7188153 Lunt et al. Mar 2007 B2
7190956 Dorenbosch et al. Mar 2007 B2
7194516 Giacobbe et al. Mar 2007 B2
7200634 Mendiola et al. Apr 2007 B2
7203507 Smith et al. Apr 2007 B2
7206814 Kirsch Apr 2007 B2
7212617 Owens et al. May 2007 B2
7218921 Mendiola et al. May 2007 B2
7222309 Chupin et al. May 2007 B2
7231428 Teague Jun 2007 B2
7231478 Leijten Jun 2007 B2
7237002 Estrada Jun 2007 B1
7237011 St. Pierre Jun 2007 B1
7240093 Danieli et al. Jul 2007 B1
7246371 Diacakis et al. Jul 2007 B2
7257639 Li et al. Aug 2007 B1
7269590 Hull et al. Sep 2007 B2
7269627 Knauerhase Sep 2007 B2
7275215 Werndorfer et al. Sep 2007 B2
7297110 Goyal et al. Nov 2007 B2
7299257 Boyer et al. Nov 2007 B2
7305624 Siegel Dec 2007 B1
7313760 Grossman Dec 2007 B2
7319882 Mendiola et al. Jan 2008 B2
7324826 Carey et al. Jan 2008 B2
7337219 Meenan et al. Feb 2008 B1
7366522 Thomas Apr 2008 B2
7370035 Gross et al. May 2008 B2
7380268 Challener et al. May 2008 B2
7383339 Meenan et al. Jun 2008 B1
7401098 Baker Jul 2008 B2
7403942 Bayliss Jul 2008 B1
7406715 Clapper Jul 2008 B2
7411939 Lamb et al. Aug 2008 B1
7424510 Gross et al. Sep 2008 B2
7428580 Hullfish et al. Sep 2008 B2
7428585 Owens et al. Sep 2008 B1
7475113 Stolze Jan 2009 B2
7478414 Glusker et al. Jan 2009 B1
7499973 Couts et al. Mar 2009 B2
7512407 Wu et al. Mar 2009 B2
7543243 Schwartz et al. Jun 2009 B2
7552460 Goldman Jun 2009 B2
7590696 Odell Sep 2009 B1
7603417 Ben-Yoseph Oct 2009 B2
7603683 Reto Oct 2009 B2
7613776 Ben-Yoseph Nov 2009 B1
7640306 Appelman et al. Dec 2009 B2
7653693 Heikes Jan 2010 B2
7675903 Ozugur et al. Mar 2010 B2
7680796 Yeh et al. Mar 2010 B2
7685311 Friedman Mar 2010 B2
7686693 Danieli et al. Mar 2010 B2
7716287 Appelman et al. May 2010 B2
7725541 Daniell et al. May 2010 B2
7725542 Daniell et al. May 2010 B2
7752273 Ito et al. Jul 2010 B2
7774410 Gang Aug 2010 B2
7774711 Valeski Aug 2010 B2
7792297 Piccionelli et al. Sep 2010 B1
7899862 Appelman et al. Mar 2011 B2
7908327 Kucharewski Mar 2011 B2
7921368 Moody et al. Apr 2011 B2
8001199 Appelman Aug 2011 B2
8005919 Mehanna Aug 2011 B2
8046476 Trossen Oct 2011 B2
8055675 Higgins et al. Nov 2011 B2
8117265 Ben-Yoseph Feb 2012 B2
8122137 Appelman et al. Feb 2012 B2
8150922 Griffin et al. Apr 2012 B2
8156193 Odell Apr 2012 B1
8167712 Sarkar et al. May 2012 B2
8224916 Kucharewski Jul 2012 B2
8452849 Mehanna May 2013 B2
8577972 Heikes Nov 2013 B1
9203647 Appelman Dec 2015 B2
9313046 Appelman Apr 2016 B2
20010002469 Bates et al. May 2001 A1
20010003202 Mache et al. Jun 2001 A1
20010003203 Mache Jun 2001 A1
20010005861 Mousseau et al. Jun 2001 A1
20010013050 Shah Aug 2001 A1
20010013069 Shah Aug 2001 A1
20010016823 Richards et al. Aug 2001 A1
20010018858 Dwek Sep 2001 A1
20010025280 Mandato et al. Sep 2001 A1
20010034224 McDowell et al. Oct 2001 A1
20010037211 McNutt et al. Nov 2001 A1
20010048735 O'Neal Dec 2001 A1
20010056363 Gantz et al. Dec 2001 A1
20020002586 Rafal et al. Jan 2002 A1
20020006803 Mendiola et al. Jan 2002 A1
20020007398 Mendiola et al. Jan 2002 A1
20020016818 Kirani et al. Feb 2002 A1
20020021307 Glenn et al. Feb 2002 A1
20020023132 Tornabene et al. Feb 2002 A1
20020023147 Kovacs et al. Feb 2002 A1
20020029224 Carlsson Mar 2002 A1
20020032729 Erickson et al. Mar 2002 A1
20020032742 Anderson Mar 2002 A1
20020035605 McDowell et al. Mar 2002 A1
20020042830 Bose et al. Apr 2002 A1
20020046243 Morris Apr 2002 A1
20020049610 Gropper Apr 2002 A1
20020049704 Vanderveldt et al. Apr 2002 A1
20020049751 Chen et al. Apr 2002 A1
20020049806 Gatz et al. Apr 2002 A1
20020049847 McArdle et al. Apr 2002 A1
20020049852 Lee et al. Apr 2002 A1
20020052921 Morkel May 2002 A1
20020054092 Hedloy May 2002 A1
20020059379 Harvey et al. May 2002 A1
20020059401 Austin May 2002 A1
20020059425 Belfiore et al. May 2002 A1
20020059526 Dillon et al. May 2002 A1
20020065828 Goodspeed May 2002 A1
20020065856 Kisiel May 2002 A1
20020065894 Dalal et al. May 2002 A1
20020066036 Makineni et al. May 2002 A1
20020071539 Diament et al. Jun 2002 A1
20020078077 Baumann et al. Jun 2002 A1
20020083127 Agrawal Jun 2002 A1
20020083136 Whitten, II Jun 2002 A1
20020084888 Jin Jul 2002 A1
20020087630 Wu Jul 2002 A1
20020087649 Horvitz Jul 2002 A1
20020087704 Chesnais et al. Jul 2002 A1
20020091667 Jaipuria et al. Jul 2002 A1
20020091936 Tema Jul 2002 A1
20020095464 Meek Jul 2002 A1
20020095663 Joory Jul 2002 A1
20020097856 Wullert Jul 2002 A1
20020103801 Lyons Aug 2002 A1
20020112181 Smith Aug 2002 A1
20020112239 Goldman Aug 2002 A1
20020116461 Diacakis et al. Aug 2002 A1
20020116463 Hart Aug 2002 A1
20020116528 Vale Aug 2002 A1
20020116641 Mastrianni Aug 2002 A1
20020118809 Eisenberg Aug 2002 A1
20020119789 Friedman Aug 2002 A1
20020120687 Diacakis et al. Aug 2002 A1
20020120697 Generous et al. Aug 2002 A1
20020120779 Teeple et al. Aug 2002 A1
20020123328 Snip et al. Sep 2002 A1
20020123988 Dean et al. Sep 2002 A1
20020128047 Gates Sep 2002 A1
20020130904 Becker et al. Sep 2002 A1
20020133369 Johnson Sep 2002 A1
20020136390 Lang et al. Sep 2002 A1
20020137530 Karve Sep 2002 A1
20020138632 Bade et al. Sep 2002 A1
20020138650 Yamamoto et al. Sep 2002 A1
20020143565 Headings et al. Oct 2002 A1
20020144283 Headings et al. Oct 2002 A1
20020151294 Kirby et al. Oct 2002 A1
20020154178 Barnett Oct 2002 A1
20020155826 Robinson et al. Oct 2002 A1
20020160757 Shavit et al. Oct 2002 A1
20020160805 Laitinen et al. Oct 2002 A1
20020165000 Fok Nov 2002 A1
20020165729 Kuebert et al. Nov 2002 A1
20020169748 Macholda Nov 2002 A1
20020174050 Eynard Nov 2002 A1
20020174260 Huang Nov 2002 A1
20020175953 Lin Nov 2002 A1
20020178072 Gusler et al. Nov 2002 A1
20020178161 Brezin et al. Nov 2002 A1
20020181703 Logan et al. Dec 2002 A1
20020184089 Tsou et al. Dec 2002 A1
20020184128 Holtsinger Dec 2002 A1
20020184309 Danker et al. Dec 2002 A1
20020184620 Davies et al. Dec 2002 A1
20020187794 Fostick et al. Dec 2002 A1
20020188620 Doss et al. Dec 2002 A1
20020194378 Foti Dec 2002 A1
20020199095 Bandini et al. Dec 2002 A1
20030004855 Dutta Jan 2003 A1
20030004872 Gardi et al. Jan 2003 A1
20030006912 Brescia Jan 2003 A1
20030009385 Tucciarone et al. Jan 2003 A1
20030009698 Lindeman et al. Jan 2003 A1
20030014485 Banatwala Jan 2003 A1
20030018704 Polychronidis et al. Jan 2003 A1
20030018726 Low et al. Jan 2003 A1
20030018747 Herland et al. Jan 2003 A1
20030023681 Brown et al. Jan 2003 A1
20030023684 Brown et al. Jan 2003 A1
20030023692 Moroo Jan 2003 A1
20030023875 Hursey Jan 2003 A1
20030025824 Ishikawa Feb 2003 A1
20030028524 Keskar Feb 2003 A1
20030028595 Vogt et al. Feb 2003 A1
20030028597 Salmi Feb 2003 A1
20030028884 Swart et al. Feb 2003 A1
20030030561 Yafuso et al. Feb 2003 A1
20030037110 Yamamoto Feb 2003 A1
20030037112 Fitzpatrick et al. Feb 2003 A1
20030037114 Nishio et al. Feb 2003 A1
20030042306 Irwin Mar 2003 A1
20030045272 Burr Mar 2003 A1
20030046097 LaSalle et al. Mar 2003 A1
20030050916 Ortega Mar 2003 A1
20030050976 Block Mar 2003 A1
20030051131 Reinold et al. Mar 2003 A1
20030051161 Smith et al. Mar 2003 A1
20030052915 Brown et al. Mar 2003 A1
20030054830 Williams et al. Mar 2003 A1
20030055831 Ryan Mar 2003 A1
20030055897 Brown et al. Mar 2003 A1
20030058478 Aoki Mar 2003 A1
20030060211 Chern Mar 2003 A1
20030060212 Thomas Mar 2003 A1
20030064422 McDevitt Apr 2003 A1
20030065721 Roskind Apr 2003 A1
20030078981 Harms et al. Apr 2003 A1
20030078987 Serebrennikov Apr 2003 A1
20030079024 Hough et al. Apr 2003 A1
20030081001 Munro May 2003 A1
20030083046 Mathis May 2003 A1
20030087632 Sagi et al. May 2003 A1
20030088554 Ryan May 2003 A1
20030101226 Quine May 2003 A1
20030101343 Eaton et al. May 2003 A1
20030105682 Dicker et al. Jun 2003 A1
20030105820 Haims et al. Jun 2003 A1
20030105822 Gusler et al. Jun 2003 A1
20030106054 Billmaier et al. Jun 2003 A1
20030110056 Berghofer Jun 2003 A1
20030110212 Lewis Jun 2003 A1
20030110293 Friedman Jun 2003 A1
20030112945 Brown et al. Jun 2003 A1
20030115585 Barsness et al. Jun 2003 A1
20030119532 Hatch Jun 2003 A1
20030119561 Hatch et al. Jun 2003 A1
20030120732 Couts et al. Jun 2003 A1
20030126267 Gutta et al. Jul 2003 A1
20030129969 Rucinski Jul 2003 A1
20030130014 Rucinski Jul 2003 A1
20030131061 Newton Jul 2003 A1
20030131143 Myers Jul 2003 A1
20030135659 Bellotti et al. Jul 2003 A1
20030154254 Awasthi Aug 2003 A1
20030154257 Hantsch et al. Aug 2003 A1
20030154373 Shimada et al. Aug 2003 A1
20030154398 Eaton et al. Aug 2003 A1
20030156138 Vronay et al. Aug 2003 A1
20030156707 Brown et al. Aug 2003 A1
20030158855 Farnham et al. Aug 2003 A1
20030158860 Caughey Aug 2003 A1
20030158864 Samn Aug 2003 A1
20030158902 Volach Aug 2003 A1
20030161335 Fransdonk Aug 2003 A1
20030167308 Schran Sep 2003 A1
20030167310 Moody et al. Sep 2003 A1
20030167324 Farnham et al. Sep 2003 A1
20030172349 Katayama Sep 2003 A1
20030174164 Capps Sep 2003 A1
20030177175 Worley et al. Sep 2003 A1
20030177190 Moody et al. Sep 2003 A1
20030179930 O'Dell et al. Sep 2003 A1
20030185232 Moore et al. Oct 2003 A1
20030185360 Moore et al. Oct 2003 A1
20030187813 Goldman Oct 2003 A1
20030188199 Tadano et al. Oct 2003 A1
20030188263 Bates et al. Oct 2003 A1
20030191673 Cohen Oct 2003 A1
20030191753 Hoch Oct 2003 A1
20030191969 Katsikas Oct 2003 A1
20030196967 Robinson et al. Oct 2003 A1
20030197729 Denoue et al. Oct 2003 A1
20030200272 Campise et al. Oct 2003 A1
20030204568 Bhargava et al. Oct 2003 A1
20030204741 Schoen et al. Oct 2003 A1
20030206195 Matsa et al. Nov 2003 A1
20030206619 Curbow et al. Nov 2003 A1
20030208545 Eaton et al. Nov 2003 A1
20030208547 Branimir Nov 2003 A1
20030210265 Haimberg Nov 2003 A1
20030212745 Caughey Nov 2003 A1
20030217109 Ordille et al. Nov 2003 A1
20030220835 Barnes, Jr. Nov 2003 A1
20030220946 Malik Nov 2003 A1
20030220976 Malik Nov 2003 A1
20030222902 Chupin et al. Dec 2003 A1
20030225834 Lee et al. Dec 2003 A1
20030225836 Lee et al. Dec 2003 A1
20030225850 Teague Dec 2003 A1
20030227487 Hugh Dec 2003 A1
20030227894 Wang et al. Dec 2003 A1
20030228908 Caiafa et al. Dec 2003 A1
20030229668 Malik Dec 2003 A1
20030229717 Teague Dec 2003 A1
20030229722 Beyda Dec 2003 A1
20030233265 Lee et al. Dec 2003 A1
20030233413 Becker Dec 2003 A1
20030233416 Beyda Dec 2003 A1
20030233417 Beyda et al. Dec 2003 A1
20030233418 Goldman Dec 2003 A1
20030233650 Zaner et al. Dec 2003 A1
20030236120 Reece et al. Dec 2003 A1
20040001480 Tanigawa et al. Jan 2004 A1
20040003041 Moore et al. Jan 2004 A1
20040003046 Grabelsky et al. Jan 2004 A1
20040003071 Mathew et al. Jan 2004 A1
20040005881 Ala-Luukko Jan 2004 A1
20040006621 Bellinson et al. Jan 2004 A1
20040010808 deCarmo Jan 2004 A1
20040017396 Werndorfer et al. Jan 2004 A1
20040019637 Goodman et al. Jan 2004 A1
20040019645 Goodman et al. Jan 2004 A1
20040019650 Auvenshine Jan 2004 A1
20040019671 Metz Jan 2004 A1
20040019695 Fellenstein et al. Jan 2004 A1
20040024478 Hans et al. Feb 2004 A1
20040024822 Werndorfer et al. Feb 2004 A1
20040024892 Creswell et al. Feb 2004 A1
20040029567 Timmins et al. Feb 2004 A1
20040029572 Nerot Feb 2004 A1
20040030741 Wolton et al. Feb 2004 A1
20040030750 Moore et al. Feb 2004 A1
20040030787 Jandel Feb 2004 A1
20040031058 Reisman Feb 2004 A1
20040044536 Fitzpatrick et al. Mar 2004 A1
20040044723 Bell et al. Mar 2004 A1
20040044736 Austin-Lane et al. Mar 2004 A1
20040052356 McKinzie et al. Mar 2004 A1
20040054646 Daniell et al. Mar 2004 A1
20040054729 Fukuizumi et al. Mar 2004 A1
20040054733 Weeks Mar 2004 A1
20040054735 Daniell et al. Mar 2004 A1
20040054736 Daniell et al. Mar 2004 A1
20040056901 March et al. Mar 2004 A1
20040059708 Dean et al. Mar 2004 A1
20040059781 Yoakum et al. Mar 2004 A1
20040059942 Xie Mar 2004 A1
20040064586 Weigand Apr 2004 A1
20040073643 Hayes et al. Apr 2004 A1
20040078440 Potter et al. Apr 2004 A1
20040078445 Malik Apr 2004 A1
20040092250 Valloppillil May 2004 A1
20040092272 Valloppillil May 2004 A1
20040092273 Valloppillil May 2004 A1
20040098491 Costa-Requena et al. May 2004 A1
20040103156 Quillen et al. May 2004 A1
20040107119 Ohishi Jun 2004 A1
20040111261 Chaudhari et al. Jun 2004 A1
20040117443 Barsness Jun 2004 A1
20040117451 Chung Jun 2004 A1
20040117831 Ellis et al. Jun 2004 A1
20040122681 Ruvolo Jun 2004 A1
20040122730 Tucciarone et al. Jun 2004 A1
20040122810 Mayer Jun 2004 A1
20040122855 Ruvolo Jun 2004 A1
20040122901 Sylvain Jun 2004 A1
20040133564 Gross et al. Jul 2004 A1
20040137882 Forsyth Jul 2004 A1
20040141599 Tang et al. Jul 2004 A1
20040143564 Gross et al. Jul 2004 A1
20040148347 Appelman et al. Jul 2004 A1
20040152477 Wu et al. Aug 2004 A1
20040152517 Hardisty et al. Aug 2004 A1
20040153506 Ito et al. Aug 2004 A1
20040153518 Seligmann et al. Aug 2004 A1
20040153552 Trossen Aug 2004 A1
20040154022 Boss et al. Aug 2004 A1
20040157586 Robinson et al. Aug 2004 A1
20040158631 Chang et al. Aug 2004 A1
20040162830 Shirwadkar et al. Aug 2004 A1
20040171396 Carey et al. Sep 2004 A1
20040172396 Vanska et al. Sep 2004 A1
20040172481 Engstrom Sep 2004 A1
20040176076 Uppuluri Sep 2004 A1
20040176081 Bryham et al. Sep 2004 A1
20040177119 Mason et al. Sep 2004 A1
20040179039 Blattner et al. Sep 2004 A1
20040183829 Kontny et al. Sep 2004 A1
20040186738 Reisman Sep 2004 A1
20040186887 Galli et al. Sep 2004 A1
20040186989 Clapper Sep 2004 A1
20040193684 Ben-Yoseph Sep 2004 A1
20040193722 Donovan Sep 2004 A1
20040196315 Swearingen et al. Oct 2004 A1
20040198351 Knotts Oct 2004 A1
20040199581 Kucharewski et al. Oct 2004 A1
20040199582 Kucharewski et al. Oct 2004 A1
20040201624 Crawford Oct 2004 A1
20040203766 Jenniges et al. Oct 2004 A1
20040204068 Komaki Oct 2004 A1
20040204140 Nagata Oct 2004 A1
20040205126 Ben-Yoseph Oct 2004 A1
20040205127 Ben-Yoseph Oct 2004 A1
20040210639 Ben-Yoseph et al. Oct 2004 A1
20040210844 Pettinati Oct 2004 A1
20040215648 Marshall Oct 2004 A1
20040215721 Szeto et al. Oct 2004 A1
20040215793 Ryan et al. Oct 2004 A1
20040219936 Kontiainen Nov 2004 A1
20040220897 Bernhart et al. Nov 2004 A1
20040221309 Zaner Nov 2004 A1
20040231003 Cooper et al. Nov 2004 A1
20040243844 Adkins Dec 2004 A1
20040255122 Ingerman et al. Dec 2004 A1
20040267604 Gross et al. Dec 2004 A1
20050004978 Reed et al. Jan 2005 A1
20050004984 Simpson Jan 2005 A1
20050004995 Stochosky Jan 2005 A1
20050009541 Ye et al. Jan 2005 A1
20050015432 Cohen Jan 2005 A1
20050021750 Abrams Jan 2005 A1
20050021854 Bjorkner Jan 2005 A1
20050027382 Kirmse et al. Feb 2005 A1
20050038856 Krishnasamy Feb 2005 A1
20050050143 Gusler et al. Mar 2005 A1
20050055306 Miller et al. Mar 2005 A1
20050055340 Dresden Mar 2005 A1
20050055416 Heikes Mar 2005 A1
20050066362 Rambo Mar 2005 A1
20050071251 Linden et al. Mar 2005 A1
20050076240 Appleman Apr 2005 A1
20050076241 Appelman Apr 2005 A1
20050086305 Koch et al. Apr 2005 A1
20050091314 Blagsvedt et al. Apr 2005 A1
20050976241 Appelman Apr 2005
20050096084 Pohja et al. May 2005 A1
20050102202 Linden et al. May 2005 A1
20050108091 Sotak May 2005 A1
20050108329 Weaver et al. May 2005 A1
20050108341 Mathew et al. May 2005 A1
20050114229 Ackley May 2005 A1
20050114783 Szeto May 2005 A1
20050125559 Mutha Jun 2005 A1
20050130633 Hill et al. Jun 2005 A1
20050149606 Lyle et al. Jul 2005 A1
20050160144 Bhatia Jul 2005 A1
20050171955 Hull et al. Aug 2005 A1
20050172001 Zaner et al. Aug 2005 A1
20050177486 Yeager Aug 2005 A1
20050181878 Danieli et al. Aug 2005 A1
20050187020 Amaitis et al. Aug 2005 A1
20050188044 Fleming, III Aug 2005 A1
20050195802 Klein et al. Sep 2005 A1
20050197846 Pezaris Sep 2005 A1
20050198131 Appelman et al. Sep 2005 A1
20050198164 Moore et al. Sep 2005 A1
20050198172 Appelman et al. Sep 2005 A1
20050198173 Evans Sep 2005 A1
20050198268 Chandra Sep 2005 A1
20050204063 O'Brien Sep 2005 A1
20050208957 Knotts Sep 2005 A1
20050216300 Appelman et al. Sep 2005 A1
20050223075 Swearingen et al. Oct 2005 A1
20050239550 Hardisty et al. Oct 2005 A1
20050246420 Little Nov 2005 A1
20050251515 Reed Nov 2005 A1
20050289469 Chandler et al. Dec 2005 A1
20060009243 Dahan et al. Jan 2006 A1
20060026237 Wang et al. Feb 2006 A1
20060031080 Mallya et al. Feb 2006 A1
20060031772 Valeski Feb 2006 A1
20060036701 Bulfer et al. Feb 2006 A1
20060047187 Goyal et al. Mar 2006 A1
20060047747 Erickson et al. Mar 2006 A1
20060116139 Appelman Jun 2006 A1
20060117380 Tachizawa et al. Jun 2006 A1
20060129678 Morita Jun 2006 A1
20060136584 Decker et al. Jun 2006 A1
20060149644 Sulmar et al. Jul 2006 A1
20060154650 Sherman et al. Jul 2006 A1
20060168204 Appelman et al. Jul 2006 A1
20060221173 Duncan Oct 2006 A1
20060242583 MacNaughton et al. Oct 2006 A1
20060259344 Patel et al. Nov 2006 A1
20060259476 Kadayam et al. Nov 2006 A1
20060271687 Alston et al. Nov 2006 A1
20060288077 Chen et al. Dec 2006 A1
20070092072 Jacobs Apr 2007 A1
20070112966 Eftis et al. May 2007 A1
20070157098 Chupin et al. Jul 2007 A1
20070185957 Mandalia et al. Aug 2007 A1
20070250566 Appelman Oct 2007 A1
20080008106 Boberg et al. Jan 2008 A1
20080133417 Robinson Jun 2008 A1
20080255989 Altberg et al. Oct 2008 A1
20080288604 Major et al. Nov 2008 A1
20090016499 Hullfish Jan 2009 A1
20090043844 Zimmet et al. Feb 2009 A1
20090070306 Stroe Mar 2009 A1
20090070433 Karstens Mar 2009 A1
20090299934 Horvitz et al. Dec 2009 A1
20110047487 DeWeese et al. Feb 2011 A1
20110167116 Kucharewski Jul 2011 A1
20110179117 Appelman Jul 2011 A1
20110282955 Appelman Nov 2011 A1
20120011110 Mehanna Jan 2012 A1
20120198012 Odell Aug 2012 A1
20120233269 Ben-Yoseph Sep 2012 A1
20130013686 Kucharewski Jan 2013 A1
20130066990 Ben-Yoseph Mar 2013 A1
20130066991 Ben-Yoseph Mar 2013 A1
20130066992 Ben-Yoseph Mar 2013 A1
20130067002 Heikes Mar 2013 A1
20130067003 Heikes Mar 2013 A1
20130072239 Hullfish Mar 2013 A1
20130073580 Mehanna Mar 2013 A1
20130073627 Mehanna Mar 2013 A1
20130073653 Heikes Mar 2013 A1
20130073656 Hullfish Mar 2013 A1
20130073657 Hullfish Mar 2013 A1
20130073966 Appelman Mar 2013 A1
20130073967 Appelman Mar 2013 A1
20130073968 Appelman Mar 2013 A1
20130080528 Mehanna Mar 2013 A1
20130097254 Appelman Apr 2013 A1
20130097255 Appelman Apr 2013 A1
20130097256 Appleman Apr 2013 A1
20130117399 Appelman May 2013 A1
20130124506 Mehanna May 2013 A1
20130124629 Appelman May 2013 A1
20130125138 Appelman May 2013 A1
20130132376 Mehanna May 2013 A1
20130138634 Mehanna May 2013 A1
20130138680 Mehanna May 2013 A1
20130144876 Mehanna Jun 2013 A1
20130144898 Mehanna Jun 2013 A1
20130145040 Mehanna Jun 2013 A1
20130151546 Mehanna Jun 2013 A1
20130159290 Mehanna Jun 2013 A1
20130159420 Appelman Jun 2013 A1
20130159439 Appelman Jun 2013 A1
20130159440 Appelman Jun 2013 A1
20130159441 Appelman Jun 2013 A1
20130159442 Appelman Jun 2013 A1
20130173722 Kucharewski Jul 2013 A1
20130174060 Odell Jul 2013 A1
20130332957 Deweese et al. Dec 2013 A1
Foreign Referenced Citations (84)
Number Date Country
2547240 Dec 2009 CA
2506417 Jun 2011 CA
1348296 May 2002 CN
100476805 Apr 2009 CN
10048653 Apr 2002 DE
0889660 Jan 1999 EP
1011243 Jun 2000 EP
1054329 Nov 2000 EP
1071295 Jan 2001 EP
1091532 Apr 2001 EP
1102443 May 2001 EP
1104961 Jun 2001 EP
1104964 Jun 2001 EP
1104965 Jun 2001 EP
1113619 Jul 2001 EP
1113620 Jul 2001 EP
1113631 Jul 2001 EP
1113640 Jul 2001 EP
1113659 Jul 2001 EP
1113677 Jul 2001 EP
1207655 May 2002 EP
1213874 Jun 2002 EP
1237384 Sep 2002 EP
1248484 Oct 2002 EP
1248486 Oct 2002 EP
1255414 Nov 2002 EP
1274222 Jan 2003 EP
1565845 Aug 2008 EP
2328835 Mar 1999 GB
2357932 Jul 2001 GB
2368747 May 2002 GB
04-86950 Mar 1992 JP
08-123821 May 1996 JP
09-247334 Sep 1997 JP
11-161682 Jun 1999 JP
11-328194 Nov 1999 JP
2000-148795 May 2000 JP
2000-222424 Aug 2000 JP
2002-7479 Jan 2002 JP
2001-109752 Apr 2002 JP
2002-132832 May 2002 JP
2002-175301 Jun 2002 JP
20011048800 Jun 2001 KR
1020010012984 Sep 2002 KR
WO 9734244 Sep 1997 WO
WO 9737303 Oct 1997 WO
WO 9820410 May 1998 WO
WO 9847270 Oct 1998 WO
WO 9934628 Jul 1999 WO
WO 0010099 Feb 2000 WO
WO 0042791 Jul 2000 WO
WO 0043892 Jul 2000 WO
WO 0047270 Aug 2000 WO
WO 0079396 Dec 2000 WO
WO 0106748 Jan 2001 WO
WO 0140957 Jun 2001 WO
WO 0141477 Jun 2001 WO
WO 0163423 Aug 2001 WO
WO 0167622 Sep 2001 WO
WO 0167787 Sep 2001 WO
WO 0169406 Sep 2001 WO
WO 0180079 Oct 2001 WO
WO 0203216 Jan 2002 WO
WO 0219643 Mar 2002 WO
WO 0228046 Apr 2002 WO
WO 02073886 Sep 2002 WO
WO 02077840 Oct 2002 WO
WO 02093400 Nov 2002 WO
WO 02093875 Nov 2002 WO
WO 03021929 Mar 2003 WO
WO 2006026908 Mar 2003 WO
WO 2004046875 Jun 2004 WO
WO 2004046949 Jun 2004 WO
WO 2004046970 Jun 2004 WO
WO 2004088943 Oct 2004 WO
WO 2004111812 Dec 2004 WO
WO 2004111871 Dec 2004 WO
WO 2005010709 Feb 2005 WO
WO 2005054991 Jun 2005 WO
WO 2005057329 Jun 2005 WO
WO 2005086723 Sep 2005 WO
WO 2005089286 Sep 2005 WO
WO 2006066092 Jun 2006 WO
WO 2006068955 Jun 2006 WO
Non-Patent Literature Citations (451)
Entry
U.S. Appl. No. 10/974,969, filed Oct. 28, 2004, 56 pages.
International Application No. PCT/US2004/029291, filed Sep. 8, 2004, 47 pages.
International Search Report mailed Dec. 27, 2005 for International Application No. PCT/US04/29291, filed Sep. 8, 2004, 5 pages.
International Search Report for International Application No. PCT/US05/45630, dated Oct. 23, 2006, 5 pages.
Office Action mailed Jan. 8, 2008 for U.S. Appl. No. 10/415,211, filed Nov. 18, 2003, 20 pages.
Written Opinion mailed Dec. 27, 2005 for International Application No. PCT/US04/29291, filed Sep. 8, 2004.
Written Opinion for International Application No. PCT/US05/45630, dated Oct. 23, 2006, 6 pages.
Haim Schneider, Lotus Developer Domain, “Adding a popup menu to your Sametime links,” Jul. 1, 2003, 8 pages.
IBM Lotus Software, Sametime Everyplace FAQ Overview Information, (visited Jul. 28, 2003), 3 pages.
IBM Lotus Software, Sametime Everyplace Wireless Collaboration that's Fit for e-Business, (Jul. 2, 2003), 2 pages.
Kirk Scott, “Ubique's Virtual Places: Communication and interaction on the World Wide Web,” (visited Jul. 28, 2003), 2 pages.
Tara Hall, Lotus Developer Domain, Place, Sametime with Chris Price, (visited Jul. 28, 2003), 8 pages.
Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority for International Application No. PCT/US2004/029291; Dec. 27, 2005; 9 pages.
U.S. Appl. No. 11/023,652, Apr. 29, 2014, Office Action.
U.S. Appl. No. 13/189,972, Apr. 21, 2014, Office Action.
U.S. Appl. No. 13/442,226, Apr. 14, 2014, Office Action.
U.S. Appl. No. 13/614,640, Jun. 11, 2014, Notice of Allowance.
U.S. Appl. No. 13/614,781, Apr. 2, 2014, Office Action.
U.S. Appl. No. 13/617,270, Apr. 10, 2014, Office Action.
U.S. Appl. No. 13/617,330, Apr. 8, 2014, Office Action.
U.S. Appl. No. 13/619,009, Apr. 11, 2014, Notice of Allowance.
U.S. Appl. No. 13/619,054, Apr. 7, 2014, Office Action.
U.S. Appl. No. 13/620,851, Apr. 8, 2014, Office Action.
U.S. Appl. No. 13/755,990, May 16, 2014, Notice of Allowance.
U.S. Appl. No. 13/766,781, May 6, 2014, Office Action.
U.S. Appl. No. 13/766,785, May 14, 2014, Office Action.
U.S. Appl. No. 13/766,776, May 8, 2014, Office Action.
U.S. Appl. No. 13/766,779, Apr. 11, 2014, Office Action.
U.S. Appl. No. 13/620,862, Aug. 3, 2015, Notice of Allowance.
U.S. Appl. No. 13/620,863, Jun. 19, 2015, Office Action.
U.S. Appl. No. 13/620,865, Jun. 16, 2016, Office Action.
U.S. Appl. No. 10/715,213, filed Nov. 18, 2003, Schlegel.
U.S. Appl. No. 10/974,969, filed Oct. 28, 2004, Wick.
U.S. Appl. No. 11/023,652, filed Dec. 29, 2004, Odell.
U.S. Appl. No. 13/361,141, filed Jan. 30, 2012, Appelman et al.
Automated feature of Internet Explorer, www.geocities.com/technofundo/tech/web/ie—autocomplete.html, pp. 1-6, Feb. 18, 2004.
“Approved Database for KnockKnock,” http://www.knockmail.com/support/appdatabase.html, pp. 1, as accessed on Dec. 4, 2003.
A. Dornan, “Instant Gratification [instant messaging]”, Network Magazine, Aug. 2000, INSPEC p. 9.
A.C.M. Fong et al., “Towards an Open Protocol for Secure Online Presence Notification”, Computer Standards & Interfaces, Sep. 2001, INSPEC p. 2.
AE. Milewski et al., “Providing Presence Cues to Telephone Users”, Proceedings of CSCW 2000, ACM Conference on Computer Supported Cooperative Work, Jan. 2000, INSPEC p. 3.
America Online Growing Pains, Newsbytes, Mar. 7, 1995.
Armstrong, R., et al., “Web Watcher: a learning apprentice for the world wide web,” Feb. 1, 1995,7 pages.
ATMobile Develops Networking-Sensing Instant Messaging, Dec. 8, 1999, Newsbytes, pp. 1-2.
“A Countermeasure to Duplicate-detecting Anti-spam Techniques,” Robert J. Hall, AT&T Labs Technical Report 99.9.1, May 1999, Abst. and pp. 1-26.
Adeptra Services Overview; Nov. 7, 2002; adeptra.com ; pp. 1-7.
Adeptra, Features; Nov. 27, 2002; adeptra.com ; pp. 1-2.
America Online Inc., “AOL Instant Messenger”, Aug. 29, 2000, Internet: www.aol.com/aim/ (18 pages).
America Online Inc., New AIM 4.7, Sep. 27, 2001, Internet: http://aim.aol.com (7 pages).
“Announce: Implementation of E-mail Spam Proposal,” Maurice L. Marvin, news.admin.net-abuse.misc, Aug. 3, 1996, 2 pages.
“A Reputation System for Peer-to-Peer Networks,” Gupta et al., Jun. 1-3, 2003, NOSSDAV'03, Monterey, California, pp. 144-152.
“BestCalls.com Announces the BestCalls Technology Index,” Business Wire, Jun. 30, 1999, Business Wire, (2 pages).
“Business at Cyberspeed; Brainstorm Becomes Quick Internet Hit,” Walker, Jan. 24, 1999, The Washington Post, p. A.01 (4 total pages).
“Better Bayesian Filtering,” Paul Graham, Jan. 2003, pp. 1-11, http:// www.paulgraham.com/better.html.
B. Raman et al., “Universal Inbox-Providing Extensible Personal Mobility and Service Mobility in an Integrated Communication Network”, Proceedings Third IEEE Workshop on Mobile Computing Systems and Applications, Oct. 2000, INSPEC p. 7.
Brown et al., “WWW Plug-Ins Companion,” Que Corporation, Oct. 1996, pp. 351-362.
Business Information Corporation, Sep. 1, 1999, Atmobile.com Enters ‘IM’ World.
Business Wire Atmobile Corporation, AtMobile awarded U.S. Patent Covering Key Elements of its Wireless Instant Messaging System, Sep. 13, 1999.
Boyce, Jim, “Microsoft Office Outlook 2003 Inside Out,” Microsoft Press (published Nov. 12, 2003), pp. 252.
Brugali, David, “Mediating the Internet,” Annals of Software Engineering, vol. 13, pp. 285-308, Jun. 2002, Kluwer Academic Publishers, The Netherlands.
Bryan Pfaffenberger, Netscape Navigator Gold, AP Professional, Jan. 1997, 4 pages.
Cerulean Studios, “Trillian Pro: No Boundaries,” (Overview, New Features, Tech Specs, Corporate, Product Tour—16 pages) 1999-2004; first release Jul. 2000.
Cerulean Studios, “Trillian Pro: Your Freedom to Chat,” (Overview, Features, Screenshots, Tech Specs—8 total pages) 1999-2004; first release Jul. 2000.
Chen, Hao et al. “Bringing Order to the Web: Automatically Categorizing Search Results.” Proceedings of the SIGCHI conference on human factors in computing systems. ACM Press. pp. 145-152, New York, Jan. 2000.
Chung-Hwa Herman Rao et al.; iMobile: A Proxy-Based Platform for Mobile Services; Network Services Research Center AT&T Labs—Rsearch, Aug. 2001.
Chung-Hwa-Rao, H. Di-Fa Chang, Yi-Bing Lin, “iSMS: an integration platform for short meassage service and IP networks,” Network, IEEE, vol. 15, No. 2, pp. 48-55, Mar./Apr. 2001.
“Creating a Single List of Contacts—Google Scholar” available at http://scholar.google.com/scholar?h1=en&1r=&q=creating+a+single+1ist+1ist+of+contacts&as . . . (Mar. 27, 2007), 10 pages.
CommWorks 8250 Personal Communications Management System; Dec. 11, 2002; commworks.com; pp. 1-2.
CommWorks IP Messaging; Dec. 11, 2002; commworks.com; pp. 1-2.
ConNexus to awareness: extending awareness to mobile users, Tang, J.C. and Yankelovich, N. and Begole, J. and Van Kleek M. and Li, F. and Bhalodia J., Proceedings of the SIGCHI conference on Human factors in computing systems, pp. 221-228, Dec. 2001, ACM Press, New York, NY, USA.
“CrushParty.com: Help,” retrieved Jun. 12, 2002 from the World Wide Web: http://www.crushparty.com/help.jsp, 3 pages.
CNET Networks Inc., “PopUp Killer”, Sep. 13, 2001, Internet: download. cnet.com/downloads/O-10059-100-6932612 shtml, (3 pages).
Convergys Interactive Alerts Reduce Customer Care Costs and Improve Customer Satisfaction; convergys.com ; pp. 1-2, Jan. 22, 2002.
“Digital Artifacts for Remembering and Storytelling: Post History and Social Network Fragments,” Viegas et al., retrieved from the World Wide Web: http://we.media.mit.edu/-fviegas/papers/posthistory.snfpdf, (10 pages), Jan. 2004.
Danny Sullivan, “What People Search for,” Search Engine Watch, pp. 1-4, http://searchenginewatch.com/facts/searches.html (visited Feb. 13, 2003).
“Degrees of Separation Email Spam Protection”, Halfbakery: Degrees of Separation Email Spam Protection, reprinted from http://halfbakery.com/idea/Degrees-20 of -20Separation-20Email-20Spam-20Protecti . . . printed on Mar. 1, 2004 (3 pages).
“Denied Database for KnockKnock,” http://www.knockmail coml support/denydatabase.html, pp. 1, as accessed on Dec. 4, 2003.
“Email Server Control for KnockKnock,” http://www.knockmail.com/supporUemailservcont,html, pp. 1-2, as accessed on Dec. 4, 2003.
Ed Bott and Ron Person, UsingWindows 95 with Internet Explorer 4.0, Feb. 17, 1998, Que, Special Edition, (21 pages).
“Finding Others Online: Reputation Systems for Social Online Spaces,” Jensen et al., Apr. 20-25, 2002, CHI, Minneapolis, Minnesota, vol. 4, Issue 1, pp. 447-454.
Global Solutions Directory; Nov. 7, 2002; softwaresibm.com ; pp. 1-5.
Google Zeitgeist—Search patterns, trends, and surprises according to Google, Jan. 2003, pp. 1-2, http://www.google.com/press/zeitgeist.html (visited Feb. 13, 2003).
G. Held, “Instant Messaging Finds its Voice”, Network Magazine, May 2001, INSPEC p. 5.
G. Reif et al.; A Web-based Peer-to-Peer Architecture for Collaborative Nomadic Working; Technical Univesrity of Vienna, Distributed Systems Group, Jun. 20, 2000.
Gross et al., “Computer-Supported Cooperative Work and the Internet,” IEEE, Sep. 1996, 00. pp. 425-430.
H. Schulzrinne et al., “The IETF Internet Telephony Architecture and Protocols”, IEEE Network, May-Jun. 1999, INSPEC p. 11.
Hubbub: a sound enhanced mobile instant messenger that supports awareness and opportunistic interactions, Issacs, E. and Walendowski A.m and Ranganathan, D., Proceedings of the SIGCHI conference on Human Factors in computing systems: Changing our world, changing ourselves, pp. 179-186, Apr. 2002, ACM Press New York, NY, USA.
Hottie or Nottie? Web Site Voters Let You Know WhetherYou Sizzle or Fizzle, Marino, Jul. 11, 2001, Florida Times Union, p. C.1. (2 total pages).
Home-tribe.net, http://washingtondc stribe meUmessage/24434d1b-817b-4580 -aa42 -3bffal5 f26a?page=1 , (4 pages), printed from Internet Dec. 13, 2004, message dated Oct. 19, 2003.
http://www.friendstercom , (17 pages), Dec. 2004.
http://www.knockrnail.com/support/newsettings.jpg, as accessed on Dec. 4. 2003.
“Icq.anywhere, Email Features-Email Center-Icq.com,” retrieved Apr. 29, 2004 from the World Wide Web: http://www.icq.com/email/popular-features.html, pp. 1-5.
Ion Adroutsopoulos et al., “Learning to Filter Spam E-Mail: A Comparison of a Naive Bayesian and a Memory-Based Approach”, University of Athens, Jun. 2000, pp. 1-12.
Ipipi Frequently Asked Questions; Nov. 6, 2002; ipipi.com ; pp. 1-2.
Ignite Software: Parent Tools Feature Set, “Parent Tools Features,” http://www.parent.tools.com/features.htm, Ignite Software, pp. 1-3, as accessed on Dec. 10, 2003.
ICQ 99a, “Welcome to ICQ version 99a”, XP-002163918, ICQ Inc., Nov. 1998.
“Instant Messaging is Everyone's Business,” Yahoo Business Messenger, Yahoo!, Mar. 2003.
IBM Lotus Software, Sametime Everyplace FAQ Overview Information, pp. 1-3, http://www.lotus.com/products/wireless.nsf/allpublic . . . , (visted Jul. 28, 2003).
IBM Lotus Software, Sametime Everyplace Wireless Collaboration that's Fit for e-Business, pp. 1-6, http://www.lotus.com/products.wireless.nsf/allpublic . . . , (visited Jul. 28, 2003).
IM Means Business IEEE Spectrum, Nov. 2002.
imForwards.com—FAQ's; Oct. 21, 2003.
Index of /tarvizo/oldfiles/elips/tnt-2.4, Jul. 2nd, 2001, TNT, http://web.mit.edu/tarvizo/oldfiles/elips/tnt-2.4/.
Instant messaging in teen life, Grinter, R.E. and Palen, L., Proceedings of the 2002 ACM conference on Computer supported cooperative work, pp. 21-30, Nov. 2002, ACM Press, New York, NY, USA.
Instant Messaging with Mobile Phones to Support Awareness, Mitsuoka, M. and Watanabe, S. and Kakuta, J. and Okuyama, S., pp. 223-230, Jan. 2001, IEEE.
“Idea for Online Networking Brings Two Entrepreneurs Together,” Patents: Idea for Online Networking Brings Two Entrepreneurs Together, reprinted from http://www.nytimes.com/2003/12/01/technology/technology-media-patents-idea-for-online-networking-brings-two-entrepreneurs.htmIOIpatt.html?acbmn1+0&adxnnlx=107029 . . . , printed on Nov. 5, 2004 (2 pages).
“Instant Messaging for Gamers,” PC Gamer, May 2004, vol. 11, No. 5, (2 pages).
J. Felix Hampe et al., Mobile Electronic Commerce: Reintermediation in the Payment System, Electronic Commerce: The End of the Beginning 13th International Bled Electronic Commerce Conference Bled, Slovenia, Jun. 19-21, 2000.
J. Dudley, “Telstra targets Net spammers”, news.com.au , Dec. 02, 2003.
Jabber, Inc., Jabber Wireless Gateway Overview, May 2001.
“Jabber” http://www.jabber.com/index.cgi?CONTENTID=9, as accessed on Dec. 4, 2003.
Jennifer B. Lee, “From 100 countries, a Google snapshot of what's going on,” International Herald Tribune, Nov. 29, 2002, pp. 1-3, http://www.iht.com.
Joanna Glasner, “Social Nets Find Friends in VCs”, Nov. 17, 2003, available at http://www.wired.com/culture/lifestyle/news/2003/11/61227?currentPage=al.
Jonathan B Postel, “Simple Mail Transfer Protocol”, RFC788, Information Science Institute, Nov. 1981.
Julian Byrne, “My Spamblock was thrwarting UCE address culling programs”, news.admin.net-abuse.e-mail, Jan. 19, 1997.
“Knock Settings ServersTab,” http://www.knockmail.com/support/advserverset.html, pp. 1-2, as accessed on Dec. 4, 2003.
Komatsu et al., “Text Input with Dynamic Abbreviation Expansion,” IPSJ SIG Notes, vol. 2001, No. 87, Sep. 14, 2008, pp. 133-138, in Japanese with a partial English Translation.
Kirk Scott, Ubique's Virtual Places: Communication and interaction on the World Wide Web, 1 page, http://www.w3.org/collabroation/workshop/proceedings/p2.html, (visted Jul. 28, 2003).
Kyungkoo Jun, et al., “Agent-Based Resource Discovery”, IEEE (Feb. 2000), 10 page.
Laliberte et al., “A Protocol for Scalable Group and Public Annotations,” Elsevier, Apr. 1995, pp. 911-918.
Leander Kahney, “Will You Buy a Car From This Man?”, Oct. 6, 2003, pp. 1-3, available at http://www.wired.com/techbizlmedia/news/2003/10/60703.
“Learning Spam: Simple Techniques for Freely-Available Software,” Bart Massey et ai, Computer Science Dept., Portland, or USA, Apr. 2003, pp. 1-14.
“Lotus Instant Messaging Everyplace FAQ” retrieved Apr. 29, 2004 from the World Wide Web: http://www.lotus.com/products/product4nsf/wdocs/249c6f083166cd3e85256d7300714407, (3 pages).
Lieberman, H., “Letizia: An Agent that Assists Web Browsing”, Aug. 20, 1995, pp. 924-929.
“Listsery Control for KnockKnock,” http://www.knockmail com/supporUlistservcont.html, pp. 1, as accessed on Dec. 4, 2003.
Luis Felipe Cabrera et al., “Herald: Achieving a Global Event NotificationService”, Microsoft Research, May 2001.
M. Castelluccio, “E-mail in Real Time”, Strategic Finance, Sep. 1999, INSPEC p. 10.
M. Day, S Aggarwal, G Mohr, J. Vincent, RFC 2279 Instant Messaging/Presence Protocol Requirements, Feb. 2000.
M. Meola et al., “Real-Time Reference Service for the Remote User: From the Telephone and Electronic Mail to Internet Chat, Instant Messaging and Collaborative Software”, Reference Librarian, Dec. 1999, INSPEC p. 8.
M. Smith et al.; Conversation Trees and Threaded Chats; Collaboration & Multimedia Group, Microsoft Research, Redmond, WA, Feb. 2000.
“Managing your Addresses in Knockmail,” http://www.knockmail.com/supporUmanaddresses.html, pp. 1-2, as accessed on Dec. 4, 2003.
McMurray, Susan, “Shield your children from unsuitable Internet content,” http://www.microsoft.com/canada/home/internet&security/2.4.8protectwithparentalcontrolshowtosafeguardyourcomputer.asp#, Microsoft Home Magazine, pp. 1-3, as accessed on Dec. 10, 2003.
Mark Handel et al., “TeamPortal: Providing Team Awareness on the Web”, Dec. 2000.
McKendrick, Joseph; “Internet Call Centers: New Era in Customer Service”, Feb. 2002; VIO, n2, (4 pages).
Microservices: CommWorks Find Me-Follow Me Application; Dec. 11, 2002; commworks.com; pp. 1-2.
Microservices: CommWorks Message Alert System; Dec. 11, 2002; commworks.com; pp. 1-3.
Microservices: CommWorks Message Delivery System; Dec. 11, 2002; commworks.com; pp. 1-2.
Microsoft PressPass; Nov. 7, 2002; microsoft.com ; pp. 1-9.
Mobile instant messaging through Hubbub, Issacs, E. and Walendowski, A. and Ranganathan, D., Communications of the ACM, vol. 45, No. 9, pp. 68-72, Sep. 2002, ACM Press New York, NY USA.
Midorikawa, et al., “Part 2 Build up a Comfortable Search Environment via Customization by Rules,” PC Japan, vol. 7, No. 10, pp. 172-176, in Japanese with a partial English Translation of p. 172, Nov. 2002.
Mozilla, www.mozilla.org/projects/ml/autocomplete, Mar. 13, 2003.
Moore, J. “AOL's Grand Goal; America Online seeks to transform itself into a major Internet player,”Information Week, Jul. 31, 1995, lines 7-23, pp. 38-42.
N. Liew Kwek Sing; AOL ICQ vs. MSN Messenger; Department of Electronic and Computer Science, University of Southampton, Mar. 2003.
Nardi, BA, Whittaker, S. and Bradner, E., Feb. 2000. Interaction and Outeraction: instant messaging in Action. In Proceedings of the 2000 ACM Conference on Computer Supported Cooperative Work (Philadelphia, Pennslyvannia, USA.) CSCW '00. ACM New York, NY, 79-88.
Nextel Announces On-Line Paging Service Provided by Wireless Services—First Wireless Telephone Messaging Service to Offer Delivery Confirmation, Aug. 12, 1998, NY.
Net Alerts Overview; Nov. 7, 2002; microsoft.com ; pp. 1-3.
Neo Mai, Ken Neo. “Buying and selling on the internet; [Computimes, 2* Edition].” New Straits Times. Kuala Lumpur: Jun. 28, 2001. p. 53.
Online! Feb. 1,2003, pp. 1-2, XP002297111, Webpage of Slipstick Systems: To add addresses automatically to Microsoft Outlook Contacts, http://web.archive.org/web/20030201082058/http://www.slipstick.com/contacts/addauto.htm>, retrieved on Sep. 17, 2004 the whole document.
Olsen, Stefanie, “Will instant messaging become instant spamming?,”. http://news.com.com/2100-1023-252765.html?legacy=cnet, Feb. 16, 2001, pp. 1-4.
Ozmosys Enterprise; Nov. 7, 2002; ozmosys.com ; pp. 1-3.
“Pending Database for KnockKnock,” http://www.knockmail coml support/penddatabase.html, pp. 1, as accessed on Dec. 4, 2003.
“Preview Pending Emails in KnockMail,” http://www.knockmail.com/supporUpreviewemail.html, pp. 1-2, as accessed on Dec. 4, 2003.
“Protect Your Privacy,” MSN Features, http://messenger.msn.com/Feature/Privacy.aspx, as accessed on Dec. 2, 2003.
Parviainen et al., “Mobile Instant Messaging”, Jul. 3, 2003 IEEE.
Patrice Godefroid et al., “Ensuring Privacy in Presence Awareness Systems: An Automated Verification Approach”. Feb. 2000.
Paul Mutton, “PieSpy Social Network Bot-Inferring and Visualizing Social Networks on IRC”, jibble.org, http://lister.linux-srv.anlx.net/piespy, © 2001-2004, pp. 1-18, Mar. 18, 2004.
Per E. Pedersen et al.; Using the Theory of Planned Behavior to Explain Teenager's Adoption of Text Messaging Services; Agder University College, Jun. 2002.
Per E. Pedersen; The Adoption of Text Messaging services among Norwegian Teens: Development and Test of an Extended Adoption Model; SNF-Report No. 23/02; Samfunns-Og Naeringslivsforskning As Bergen, Jun. 2002.
Phillips Business Information corporation—Aug. 23, 1999—Instant messaging has emerged as one of the most popular communication mediums in the world.
Prodigy Launches 100 Interest Groups on the World Wide Web; All Sites Have Deep Links to Chat and Newsgroups; Topics Range from “Adventure Travel” and “Astrology” to “Virtual Reality” and “Wrestling”, Business Wire, Sep. 27, 1995, 4 Pages.
“Plaxo—Update Your Address Book,” Plaxo Contact Networks, reprinted from http://web.archive.org/web/20030218233638/http://www.plaxo.com printed on Nov. 5, 2004 (available on Feb. 18,2003), (1 page).
“Plaxo”, Plaxo, reprinted from http://web.archive.org/web/20041105072256/http://www.plaxo.com/ printed on Nov. 5, 2004 (available on Feb. 14, 2004) (2 pages).
Parent Tools TheUltimate in Monitoring and Controlling AIM “Parent Tools for AIM,” http://www.parent-tools.com/screenshots.htm, pp. 1-4, as accessed on Dec. 10, 2003.
“Reputation Systems,” Resnick et al., Dec. 2000, Communications of the ACM, vol. 43, No. 12, pp. 45-48.
“RIM Road: Software: Internet & Network: Webmessenger RIM J2ME/Instant Messaging,” retrieved Apr. 29, 2004 from the World Wide Web: http://www.rimrod.com/software/rim//Webmessenger-RIM-J2ME-Instant-Messaging-20 . . . , pp. 1-4.
“Reflections on Friendster, Trust and Intimacy,” Danah Boyd, Ubicomp 2003, Workshop Application for The Intimate Ubiquitous Computing Workshop. Seattle, WA, Oct. 12-15, 2003, (4 pages).
R. Movva & W. Lai, “MSN Messenger Service 1.0 Protocol”, Aug. 1999, Internet Draft, http://toolsietf.org/id/draft-movva-msn-messenger-protocol-oo.bct, 28 pages.
Reichard, K., “AOL, ICO to Interoperate—But in a Limited Fashion,” Oct. 30, 2002, InstantMessagingPlanet, available at www.instantmessagingplanet.com/public/articie.php/1490771.
Ryze home page, www.ryze.com , Dec. 21, 2003, available at http://web.archivesorg/web/20031221010006/http://ryze .com, printed Mar. 16, 2005, 13 pages.
R. Droms, “Dynamic Host Configuration Protocol”, Network Working Group, Oct. 1993.
Richard S. Hall, “The Event Desktop: Supporting Event-Enabled Clients on the Web”, Freie University, Berlin. Retrieved on May 21, 2013.
Roscheisen et al., “Beyond Browsing: Shared Comments, SOAPs, Trails, and On-line Communities,” Elsevier, Apr. 1995, pp. 739-749.
S. Okuyana et al., “New Mobile Service Based on Instant Messaging Technology”, Fujitsu, Apr. 2001, INSPEC p. 1.
S. Ortiz, Jr., “Instant Messaging: No Longer Just Chat”, Computer, Mar. 2001, INSPEC p. 6.
Schulzrinne, H.; Rosenberg J., “The Session Initiation Protocol: Internet-centric signaling,” Communications Magazine, IEEE, vol. 38, No. 10, pp. 134-141, Oct. 2000.
SproWuest Wireless Instant messaging (Nov. 22, 1999) InfoSpace.com, pp. 1-2.
“Six Degrees—New Programs Help Companies ‘Mine Workers’ Relationships for Key Business Prospects,” William M. Bulkeley et al., Marketplace, The Wall Street Journal, Aug. 4, 2003, (3 pages).
Sm Cherry “Talk is Cheap, Text is Cheaper” (IEEE Spectrum May 2003).
“Social Network Fragments: An Interactive Tool for Exploring Digital Social Connections.” Danah Boyd, Jeff Potter. Sketch at SIGGRAPH 2003. San Diego, California: ACM, Jul. 27-31,2003, (1 page).
“Social Networking for Business: Release 0.5,” Esther Dyson, Esther Dyson's Monthly Report, vol. 21, No. 10, Nov. 25, 2003, www.edventure.com , (36 pages).
“Support Vector Machines for Spam, Categorization,” Harris Drucker et al., IEEE Transactions on Neural Networks, vol. 10, No. 5, Sep. 1999, pp. 1048-1054, (7 pages).
“Support Vector Machines,” Marti Hearst, IEEE Intelligent Systems, Jul./Aug. 1998, pp. 18-28.
“Social Sites Clicking With Investors,” Washingtonpost.com: Social Sites Clicking With Investors, reprinted from http://www.washingtonpost.com/ac2/wp-dyn/A32066-2003Nov12?language=printer printed on Nov. 5, 2004, (2 pages).
“Social Social Networks: Deodorant for the Soul?,” Esther Dyson, Esther Dyson's Monthly Report, vol. 21, No. 11, Dec. 12, 2003, www.edventure.com, (36 pages).
“Socialware: Multiagent Systems for Supporting Network Communities,” Hattori et al., Mar. 1999, Association for Computing Machinery, Communications of the ACM, vol. 42, Issue 3, (6 pages).
“Spoke Builds on Social Networking Patent Portfolio,” Spoke Builds on Social Networking Patent Portfolio, reprinted from http://www.internetnews.com/ent-news/print.php/3073621 printed on Nov. 5, 2004(3 pages).
Solutions Smartdelivery; Nov. 6, 2002; centerpost.com ; pp. 1-2.
“SurfControl Instant Message Filter,” Instant Message Filter, SurfControl pic. Apr. 2003.
“Spammers Target Instant Message Users,” http://www.bizreport.com/article.php?art id=5507 Nov. 13, 2003, pp. 1-4.
“SWF Seeks Attractive Head Shot; To Stand Out, Online Daters Pay for Professional Photos; Cropping out the Ex-Wife,” Leiber, Nov. 19, 2003, The Wall Street Journal, p. D.1.
“SVM-based Filtering of E-mail Spam with Content-specific Misclassification Costs,” Aleksander Kolcz et al., TextDm '2001 (IEEE ICDM—2001 Workshop on Text Mining); San Jose, CA, 2001, pp. 1-14, Nov. 2001.
The Wall Street Journal article “Esniff Ferrets Out Misbehavior by ‘Reading’ E-Mail, Web Visits,” Katherine Lange, interactive.wsj.com, Apr. 27, 2001, Tech Q&A.
The Early Report—The Early Show segment, “Big Brother in the Corner Office,” Julie Chen, cbsnews.com/earlyshow/caught/techage/20001228esniff.shtml, Dec. 28, 2000: Tech Age.
“The first Social Software . . . a true Social Adventure,” Huminity-Social Networking, Chat Software, Create Personal Free Blogs and My Group . . . , reprinted from http://www.huminity.com/ printed on Nov. 5, 2004 (2 pages).
“The eSniff Product Overview,” eSniff: Define Your e-Boundaries, www.esniff.com/product overview.html, May 15, 2001.
“Text Categorization with Support Vector Machines: Learning with Many Relevant Features,” Thorsten Joachims, University of Dortmund, Computer Science Dept., Ls-8 Report 23, 1998, (18 paqes), Nov. 27, 1997, revised Apr. 19, 1998.
“Technology Journal—Are You Satisfied? EBay's Battle Against Fraud Rests Primarily on a Simple Concept: Customer Feedback,” Wingfield, Sep. 23, 2002, Asian Wall Street Journal, p. T.8, (4 total pages).
“Technology Journal: Changing Chat-Instant Messaging is Taking Off, and for Some Users Its Nuzzling Out the Phone,” Nick Wingfield, Asian WSJ, Sep. 2000, (5 pages).
“Trillian Discussion Forums—HOWTO: Import ICQ 2003a Contact List,” retrieved Apr. 29, 2004 from the World Wide Web: http://trillian.cc/forums/showthread.php?s+&threadid=36475, pp. 1-2.
“Technical Solutions for Controlling Spam,” Shane Hird, Proceedings of Aug. 2002, Melbourne, Sep. 4-6, 2002, (17 pages).
Tara Hall, Lotus Developer Domain, “Same Place, Sametime with Chris Price”, pp. 1-8, http://www.10.lotus.com/Idd/today.nsf/DisplayForm/ . . . , (Visited Jul. 28, 2003), Sep. 2002.
Teraitech; Nov. 7, 2002; teraitech.com ; 1 page.
Uhara7, “Re. being invisible to all but one person on your list”, alt.chat-programs.icq, Feb. 29, 2000.
Upoc Quick Tour; Nov. 6, 2002; upoc.com; pp. 1-9.
Upoc General Help; Nov. 6, 2002; upoc.com; pp. 1-2.
Upoc NYSaIe; Nov. 6, 2002; upoc.com; pp. 1-2.
Upoc Entertainment Picks; Nov. 6, 2002; upoc.com; pp. 1-3.
Upoc Frequently Asked Questions; Nov. 6, 2002; upoc.com; pp. 1-6.
Upside, About Our Product; upsideweb.com ; pp. 1-5, Nov. 2002.
V, Vittore, “The Next Dial Tone? [instant messaging]”, Telephony, Oct. 16, 2000, INSPEC p. 8.
VisiblePath webpages, www.visiblepath.org , Dec. 3, 2003, available at http://web. archive. org/web/20031203132211/http://www.visiblepath.com, printed Mar. 16, 2005, 5 pages.
Walther, M., “Supporting Development of Synchronous Collaboration Tools on the Web with GroCo,” Feb. 2-9, 1996, pp. 1-6.
Way-bac machine, handspring treo 270, Jun. 1, 2002.
“Wireless Instant Messaging Solution . . . ” Newswire, NY Dec. 8, 1999 Atmobile corp, pp. 1-2.
WebleySystems; CommuniKate Unified Communications Features List; Dec. 11, 2002; webley.com; pp. 1-3.
“Welcome to Huminity World of Connections,” Huminity—Home, reprinted from http://web.archive.org/web/20030228131435/www.huminity.com/default.php?intemationa . . . printed on Nov. 5, 2004 (available on Feb. 2, 2003) (1 page).
WebmasterWorld.com Inc., “HTML and Browsers”, Mar. 5, 2001, Internet: www.webmaster.com/forum21/637.htm, (2 pages).
www.yahoo.com, Yahoo! Messenger for Text Messaging, Jul. 2002.
Yiva Hard of Segerstad et al.; Awareness of Presence, Instant Messaging and WebWho; Department of Linguistics, Goteborg University; Sweden, Dec. 2000.
Yahoo! Buzz Index, Feb. 13, 2003, 1 page, http://buzz.yahoo.com/overall/.
Yahoo! Buzz Index, Nov. 10, 2002, 1 page.
Yahoo! Messenger, “Messenger Help,” (4 total pages) Nov. 2002.
ZeroDegrees home page, www.zerodegrees.com , Jan. 24, 2004, available at http://web.archive.org/web/20040204153037/www.zerodegrees.com/home.htm, printed Mar. 16, 2005, 2 pages.
Zephyr on Athena (AC-34), http://web.mit.edu/olh//Zephyr/Revision.html, 11 pages, Retrieved on May 17, 2013.
European Search Report, European Application No. 03781972.8-2201, dated Feb. 8, 2008, 5 pages.
English translation of an Office Action issued in corresponding Japanese Application No. 2004-570418 on Aug. 7, 2008.
English translation of an Office Action issued in corresponding Japanese Application No. 2004-570418 on Feb. 5, 2009.
International Search Report and Written Opinion dated Feb. 15, 2006 for International Application No. PCT/US05/07204, (10 pages).
International Search Report and Written Opinion issued in International Application No. PCT/US05/45663, dated Apr. 11, 2008.
International Search Report issued in Application Serial No. PCT/US05/08476, dated Oct. 16, 2006, (3 pages).
International Search Report issued in International Application No. EP03731244, dated Aug. 30, 2005, (4 pages).
Supplementary European Search Report issued in European Application No. EP05728303, dated Jan. 9, 2009, (4 pages).
Supplementary European Search Report issued in European Application No. 05857099.5-1238/1836596, PCT/US2005045663, dated Nov. 7, 2008, (5 pages).
International Search Report, PCT/US03/36656, dated Apr. 22, 2004.
Supplementary European Search Report dated Jun. 7, 2006 for Application No. EP 03811631, 3 pages).
Notification of Transmittal of the International Search Report or the Declaration dated Jun. 23, 2004 for International Application Serial No. PCT/US03/36795.
Office Action issued in Chinese Application No. 200480013443.9, mailed Mar. 6, 2009, 20 pages, including English translation.
Office Action mailed Apr. 21, 2005 for European Application No. 97946924.4-1238, 6 pages.
Office Action mailed May 21, 2008 for European Application No. 97946924.4-1238, 10 pages.
International Search Report dated Jan. 27, 2005 for International Application No. PCT US2004/009422, International Filing Date Mar. 26, 2004.
International Search Report issued in International Application No. PCT/US03/36795 mailed Jun. 23, 2004, 9 pages.
International Search Report, Application Serial No. PCT/US04/23382, dated Feb. 1, 2007, 12 pages.
International Search Report of PCT/US03/36654 dated Aug. 17, 2004.
International Standard, Information technology—telecommunications and information exchange between systems—private integrated services network—specifications, functional model and information flows—Short message service, ISO/IEC21989, Jul. 1, 2002.
European Office Communication issued in Application No. EP 97946924.4-1238 mailed Apr. 5, 2007, 7 pages.
European Oral Proceedings issued in Application No. EP 97946924.4-1238 mailed Feb. 6, 2007, 9 pages.
European Oral Proceedings issued in Application No. EP 97946924.4-1238 mailed Oct. 7, 2007, 8 pages.
European Office Action, Application Serial No. 03 811 631.5-2201, dated Oct. 4, 2006, 4 pages.
European Search Report, Application No. EP 03811631, dated Jun. 23, 2006, 5 pages.
Office Action from the Canadian Intellectual Property Office in corresponding Canadian Application No. 2,506,417, dated Aug. 14, 2007, 3 pages.
Written Opinion dated Jan. 27, 2005 for International Application No. PCT/US2004/009422, International Filing Date Mar. 26, 2004.
Written Opinion mailed Dec. 27, 2005 for International Application No. PCT/US2004/29291, filed Sep. 8, 2004.
U.S. Appl. No. 10/146,814, Dec. 11, 2006, Office Action.
U.S. Appl. No. 10/146,814, Jul. 2, 2007, Office Action.
U.S. Appl. No. 10/184,002, Jan. 9, 2007, Office Action.
U.S. Appl. No. 10/334,056, Nov. 29, 2004, Office Action.
U.S. Appl. No. 10/334,056, Jul. 6, 2005, Office Action.
U.S. Appl. No. 10/334,056, Oct. 31, 2005, Office Action.
U.S. Appl. No. 10/334,056, May 10, 2006, Office Action.
U.S. Appl. No. 10/334,056, May 21, 2007, Office Action.
U.S. Appl. No. 10/334,056, Nov. 5, 2007, Office Action.
U.S. Appl. No. 10/334,056, May 12, 2008, Office Action.
U.S. Appl. No. 10/334,056, Oct. 30, 2008, Office Action.
U.S. Appl. No. 10/633,636, Oct. 11, 2006, Office Action.
U.S. Appl. No. 10/651,303, Feb. 9, 2007, Office Action.
U.S. Appl. No. 10/651,303, Apr. 28, 2008, Office Action.
U.S. Appl. No. 10/651,303, Oct. 8, 2008, Office Action.
U.S. Appl. No. 10/651,303, May 1, 2009, Office Action.
U.S. Appl. No. 10/651,303, Nov. 27, 2009, Office Action.
U.S. Appl. No. 10/651,303, Mar. 11, 2011, Notice of Allowance.
U.S. Appl. No. 10/715,206, Sep. 27, 2007, Office Action.
U.S. Appl. No. 10/715,206, Jul. 25, 2008, Notice of Allowance.
U.S. Appl. No. 10/715,206, Jan. 27, 2009, Office Action.
U.S. Appl. No. 10/715,206, Aug. 13, 2009, Notice of Allowance.
U.S. Appl. No. 10/715,210, Sep. 27, 2007, Office Action.
U.S. Appl. No. 10/715,210, Apr. 14, 2008, Office Action.
U.S. Appl. No. 10/715,210, May 13, 2009, Office Action.
U.S. Appl. No. 10/715,210, Mar. 29, 2010, Notice of Allowance.
U.S. Appl. No. 10/715,211, Jul. 11, 2008, Office Action.
U.S. Appl. No. 10/715,211, Nov. 28, 2008, Office Action.
U.S. Appl. No. 10/715,211, Jun. 24, 2009, Office Action.
U.S. Appl. No. 10/715,211, Oct. 2, 2009, Notice of Allowance.
U.S. Appl. No. 10/715,211, Feb. 3, 2010, Office Action.
U.S. Appl. No. 10/715,211, Jul. 14, 2010, Office Action.
U.S. Appl. No. 10/715,211, Oct. 25, 2010, Notice of Allowance.
U.S. Appl. No. 10/715,213, Apr. 26, 2007, Office Action.
U.S. Appl. No. 10/715,213, Oct. 22, 2007, Office Action.
U.S. Appl. No. 10/715,213, Aug. 7, 2008, Office Action.
U.S. Appl. No. 10/715,213, Feb. 5, 2009, Office Action.
U.S. Appl. No. 10/715,213, Aug. 6, 2009, Office Action.
U.S. Appl. No. 10/715,213, Jul. 18, 2013, Office Action.
U.S. Appl. No. 10/715,213, Dec. 6, 2013, Notice of Allowance.
U.S. Appl. No. 10/715,214, Apr. 20, 2007, Office Action.
U.S. Appl. No. 10/715,214, Oct. 9, 2007, Office Action.
U.S. Appl. No. 10/715,215, Mar. 23, 2007, Office Action.
U.S. Appl. No. 10/715,215, Aug. 20, 2007, Office Action.
U.S. Appl. No. 10/715,215, Nov. 20, 2010, Notice of Allowance.
U.S. Appl. No. 10/715,216, Feb. 12, 2007, Office Action.
U.S. Appl. No. 10/715,216, Jan. 11, 2008, Office Action.
U.S. Appl. No. 10/715,216, Aug. 18, 2009, Office Action.
U.S. Appl. No. 10/723,040, Mar. 14, 2006, Office Action.
U.S. Appl. No. 10/723,040, Jun. 26, 2006, Office Action.
U.S. Appl. No. 10/723,040, Jan. 4, 2007, Office Action.
U.S. Appl. No. 10/723,040, Jun. 4, 2007, Office Action.
U.S. Appl. No. 10/723,040, Oct. 25, 2007, Office Action.
U.S. Appl. No. 10/723,040, May 21, 2008, Notice of Allowance.
U.S. Appl. No. 10/746,230, Mar. 17, 2009, Office Action.
U.S. Appl. No. 10/746,232, Mar. 18, 2009, Office Action.
U.S. Appl. No. 10/747,263, Mar. 5, 2008, Office Action.
U.S. Appl. No. 10/747,263, Sep. 5, 2008, Office Action.
U.S. Appl. No. 10/747,263, Feb. 11, 2009, Notice of Allowance.
U.S. Appl. No. 10/747,263, Jun. 2, 2009, Notice of Allowance.
U.S. Appl. No. 10/747,651, Mar. 5, 2008, Office Action.
U.S. Appl. No. 10/747,651, Feb. 20, 2009, Office Action.
U.S. Appl. No. 10/747,676, Sep. 21, 2007, Office Action.
U.S. Appl. No. 10/747,676, Mar. 31, 2008, Office Action.
U.S. Appl. No. 10/747,678, Sep. 14, 2007, Office Action.
U.S. Appl. No. 10/747,678, Mar. 27, 2008, Office Action.
U.S. Appl. No. 10/747,678, Jun. 12, 2008, Office Action.
U.S. Appl. No. 10/747,678, Dec. 15, 2008, Office Action.
U.S. Appl. No. 10/747,678, Jun. 5, 2009, Notice of Allowance.
U.S. Appl. No. 10/747,678, Jun. 19, 2009, Notice of Allowance.
U.S. Appl. No. 10/747,682, Oct. 11, 2007, Office Action.
U.S. Appl. No. 10/747,682, Apr. 7, 2008, Office Action.
U.S. Appl. No. 10/747,682, Aug. 19, 2008, Office Action.
U.S. Appl. No. 10/747,682, Mar. 18, 2009, Office Action.
U.S. Appl. No. 10/747,682, Nov. 2, 2009, Office Action.
U.S. Appl. No. 10/747,682, Jun. 11, 2010, Office Action.
U.S. Appl. No. 10/747,682, Dec. 2, 2010, Office Action.
U.S. Appl. No. 10/747,682, Oct. 5, 2011, Notice of Allowance.
U.S. Appl. No. 10/825,617, Jun. 24, 2008, Office Action.
U.S. Appl. No. 10/825,617, Mar. 9, 2009, Notice of Allowance.
U.S. Appl. No. 10/825,617, Sep. 10, 2009, Notice of Allowance.
U.S. Appl. No. 10/895,421, Jan. 9, 2007, Office Action.
U.S. Appl. No. 10/895,421, Jun. 27, 2007, Office Action.
U.S. Appl. No. 10/895,421, Apr. 16, 2008, Office Action.
U.S. Appl. No. 10/895,421, Nov. 19, 2008, Notice of Allowance.
U.S. Appl. No. 10/895,421, Apr. 17, 2009, Notice of Allowance.
U.S. Appl. No. 10/974,969, Mar. 17, 2008, Office Action.
U.S. Appl. No. 10/974,969, Mar. 6, 2009, Office Action.
U.S. Appl. No. 10/974,969, Sep. 8, 2009, Notice of Allowance.
U.S. Appl. No. 10/981,460, Aug. 20, 2008, Office Action.
U.S. Appl. No. 11/015,423, Mar. 2, 2009, Office Action.
U.S. Appl. No. 11/015,424, Mar. 19, 2008, Office Action.
U.S. Appl. No. 11/015,424, May 1, 2009, Office Action.
U.S. Appl. No. 11/015,476, Mar. 2, 2009, Office Action.
U.S. Appl. No. 11/017,204, Dec. 12, 2007, Office Action.
U.S. Appl. No. 11/017,204, Jun. 23, 2008, Office Action.
U.S. Appl. No. 11/023,652, Aug. 30, 2010, Office Action.
U.S. Appl. No. 11/023,652, May 12, 2011, Office Action.
U.S. Appl. No. 11/023,652, Dec. 8, 2011, Office Action.
U.S. Appl. No. 11/023,652, Sep. 24, 2012, Office Action.
U.S. Appl. No. 11/023,652, Oct. 25, 2013, Office Action.
U.S. Appl. No. 11/079,522, Oct. 16, 2008, Office Action.
U.S. Appl. No. 11/079,522, Apr. 3, 2009, Office Action.
U.S. Appl. No. 11/237,718, Apr. 2, 2009, Office Action.
U.S. Appl. No. 11/408,166, Mar. 18, 2009, Office Action.
U.S. Appl. No. 11/408,166, Oct. 7, 2009, Office Action.
U.S. Appl. No. 11/408,166, Sep. 2, 2010, Office Action.
U.S. Appl. No. 11/408,166, Apr. 13, 2011, Office Action.
U.S. Appl. No. 11/408,166, Oct. 17, 2011, Office Action.
U.S. Appl. No. 11/464,816, Apr. 21, 2009, Office Action.
U.S. Appl. No. 11/574,831, Sep. 18, 2009, Office Action.
U.S. Appl. No. 11/574,831, May 16, 2010, Office Action.
U.S. Appl. No. 11/574,831, Sep. 9, 2010, Office Action.
U.S. Appl. No. 11/574,831, Apr. 15, 2011, Office Action.
U.S. Appl. No. 11/574,831, Oct. 13, 2011, Notice of Allowance.
U.S. Appl. No. 12/236,255, Apr. 2, 2010, Office Action.
U.S. Appl. No. 12/236,255, Sep. 17, 2010, Office Action.
U.S. Appl. No. 12/236,255, Feb. 3, 2011, Office Action.
U.S. Appl. No. 12/548,338, Nov. 9, 2010, Office Action.
U.S. Appl. No. 12/548,338, May 19, 2011, Office Action.
U.S. Appl. No. 12/548,338, Dec. 9, 2011, Notice of Allowance.
U.S. Appl. No. 12/626,099, Sep. 17, 2010, Office Action.
U.S. Appl. No. 12/626,099, Mar. 30, 2011, Notice of Allowance.
U.S. Appl. No. 12/689,699, Feb. 28, 2011, Office Action.
U.S. Appl. No. 12/689,699, Apr. 23, 2012, Office Action.
U.S. Appl. No. 12/689,699, Oct. 9, 2012, Notice of Allowance.
U.S. Appl. No. 12/689,699, Mar. 11, 2013, Office Action.
U.S. Appl. No. 12/689,699, Jun. 18, 2013, Notice of Allowance.
U.S. Appl. No. 13/023,256, Jun. 21, 2011, Office Action.
U.S. Appl. No. 13/023,256, Nov. 28, 2011, Office Action.
U.S. Appl. No. 13/023,256, Apr. 16, 2012, Office Action.
U.S. Appl. No. 13/023,256, Sep. 28, 2012, Office Action.
U.S. Appl. No. 13/023,256, Jun. 21, 2013, Office Action.
U.S. Appl. No. 13/023,256, Nov. 7, 2013, Office Action.
U.S. Appl. No. 13/048,312, Nov. 22, 2011, Office Action.
U.S. Appl. No. 13/048,312, Mar. 13, 2012, Notice of Allowance.
U.S. Appl. No. 13/184,414, Aug. 17, 2012, Notice of Allowance.
U.S. Appl. No. 13/184,414, Nov. 28, 2012, Notice of Allowance.
U.S. Appl. No. 13/184,414, Jan. 29, 2013, Notice of Allowance.
U.S. Appl. No. 13/189,972, Oct. 29, 2013, Office Action.
U.S. Appl. No. 13/189,972, Jul. 24, 2013, Office Action.
U.S. Appl. No. 13/189,972, Dec. 21, 2012, Office Action.
U.S. Appl. No. 13/189,972, Aug. 22, 2012, Notice of Allowance.
U.S. Appl. No. 13/189,972, May 7, 2012, Office Action.
U.S. Appl. No. 13/189,972, Jan. 5, 2012, Office Action.
U.S. Appl. No. 13/189,972, Sep. 2, 2011, Office Action.
U.S. Appl. No. 13/372,371, May 9, 2013, Office Action.
U.S. Appl. No. 13/372,371, Nov. 29, 2013, Office Action.
U.S. Appl. No. 13/507,429, Oct. 25, 2013, Office Action.
U.S. Appl. No. 13/614,640, Oct. 2, 2013, Office Action.
U.S. Appl. No. 13/614,640, Jan. 31, 2014, Office Action.
U.S. Appl. No. 13/614,781, Jun. 4, 2013, Office Action.
U.S. Appl. No. 13/614,781, Sep. 12, 2013, Office Action.
U.S. Appl. No. 13/614,781, Dec. 26, 2013, Office Action.
U.S. Appl. No. 13/617,270, Sep. 12, 2013, Office Action.
U.S. Appl. No. 13/617,330, Sep. 12, 2013, Office Action.
U.S. Appl. No. 13/619,009, Mar. 7, 2013, Office Action.
U.S. Appl. No. 13/619,009, Sep. 19, 2013, Office Action.
U.S. Appl. No. 13/619,036, Mar. 26, 2013, Office Action.
U.S. Appl. No. 13/619,036, Sep. 16, 2013, Office Action.
U.S. Appl. No. 13/619,054, Mar. 26, 2013, Office Action.
U.S. Appl. No. 13/619,054, Oct. 10, 2013, Office Action.
U.S. Appl. No. 13/620,851, Feb. 8, 2013, Office Action.
U.S. Appl. No. 13/620,851, Nov. 29, 2013, Office Action.
U.S. Appl. No. 13/620,853, Feb. 13, 2013, Office Action.
U.S. Appl. No. 13/620,853, Jan. 9, 2014, Office Action.
U.S. Appl. No. 13/620,856, Feb. 13, 2013, Office Action.
U.S. Appl. No. 13/620,856, Jan. 9, 2014, Office Action.
U.S. Appl. No. 13/361,141, Jan. 17, 2014, Office Action.
U.S. Appl. No. 13/729,318, Sep. 18, 2013, Office Action.
U.S. Appl. No. 13/729,318, Feb. 5, 2014, Office Action.
U.S. Appl. No. 13/731,124, Dec. 6, 2013, Office Action.
U.S. Appl. No. 13/755,990, Oct. 2, 2013, Office Action.
U.S. Appl. No. 13/755,990, Jan. 29, 2014, Office Action.
U.S. Appl. No. 13/766,775, Sep. 19, 2013, Office Action.
U.S. Appl. No. 13/766,781, Nov. 27, 2013, Office Action.
U.S. Appl. No. 13/766,785, Nov. 29, 2013, Office Action.
U.S. Appl. No. 13/766,786, Nov. 27, 2013, Office Action.
U.S. Appl. No. 13/766,779, Oct. 15, 2013, Office Action.
U.S. Appl. No. 13/614,781, Mar. 20, 2015, Office Action.
U.S. Appl. No. 13/620,862, Feb. 12, 2015, Office Action.
U.S. Appl. No. 13/620,863, Feb. 24, 2015, Office Action.
U.S. Appl. No. 13/620,865, Jan. 15, 2015, Office Action.
U.S. Appl. No. 13/372,371, Jul. 1, 2014, Notice of Allowance.
U.S. Appl. No. 13/614,781, Sep. 10, 2014, Office Action.
U.S. Appl. No. 13/620,862, Jul. 24, 2014, Office Action.
U.S. Appl. No. 13/620,863, Aug. 1, 2014, Office Action.
U.S. Appl. No. 13/620,865, Aug. 6, 2014, Office Action.
U.S. Appl. No. 13/731,124, Jun. 30, 2014, Office Action.
George Orwell, Nineteen Eighty-four (1st Mariner ed., 1949).
U.S. Appl. No. 13/620,863, Dec. 23, 2015, Notice of Allowance.
U.S. Appl. No. 13/620,865, Nov. 13, 2015, Office Action.
U.S. Appl. No. 13/372,371, Mar. 26, 2014, Office Action.
U.S. Appl. No. 13/507,429, Mar. 28, 2014, Office Action.
U.S. Appl. No. 13/617,650, Mar. 27, 2014, Office Action.
U.S. Appl. No. 13/619,009, Mar. 12, 2014, Notice of Allowance.
U.S. Appl. No. 13/619,036, Mar. 21, 2014, Office Action.
U.S. Appl. No. 13/766,775, Mar. 24, 2014, Office Action.
U.S. Appl. No. 13/023,256, Dec. 12, 2016, Notice of Allowance.
U.S. Appl. No. 13/023,256, Dec. 30, 2016, Notice of Allowance.
U.S. Appl. No. 13/620,865, Nov. 17, 2016, Office Action.
Related Publications (1)
Number Date Country
20130031638 A1 Jan 2013 US
Continuations (1)
Number Date Country
Parent 11574831 US
Child 13361141 US