Generally described, telecommunications devices and communication networks facilitate the collection and exchange of information. Utilizing a communication network and relevant communication protocols, a telecommunications device can engage in audio and/or data communications with other telecommunications devices, such as voice calls, video calls, messaging (e.g., short message service (“SMS”) or multimedia messaging service (“MMS”), content streaming, instant messaging, resource browsing (e.g., Web browsing), and the like.
To facilitate communications, telecommunications devices can be associated with software and hardware components that allow the telecommunications device to maintain contact information, such as telephone numbers, email addresses, messaging addresses, etc., utilized to establish and engage in communications via available communication channels. Typically, such contact information is maintained as contact information in which all known contact information for an identified entity, such as user, can be presented to a telecommunications device user. For example, a telecommunications device may present a user interface in which the contact information associated with a selected individual is presented in a list-based format. In another example, a telecommunications device with voice calling capabilities may maintain a “last call list” that keeps track of telephone numbers of the most recent incoming calls to or outgoing calls from the telecommunications device.
Although contact management user interfaces and software can facilitate the input and management of contact information for a larger set of contacts, typical contact management approaches can become deficient as the set of entities associated with a user grows. In one example, typical call list approaches are limited in the number of contacts identified in the user interfaces (e.g., the last 4 numbers called). Accordingly, such approaches can become deficient as the number of incoming or outgoing communications (e.g., voice calls) increases because potentially desired contacts are removed from the display based on order of the most recent incoming or outgoing communications.
In another example, typical contact management approaches relate to the presentation of the entire set of contacts that are associated with a user, such as in alphabetical order. As the number of contacts maintained in the telecommunications device, or on behalf of the telecommunications device, grows, users may have increased difficulty in identifying the contact information of specific entities. Additionally, for each contact, the typical contact management approach identifies all known contact information (e.g., phone numbers, IM aliases, email addresses, etc.) without regard to a desired, or preferred, communication method. Additionally, typical contact management approaches are inefficient in the accessibility of select contact information and the establishment of options or actions that can be initiated by the telecommunications device user via a number of user interfaces.
The foregoing aspects and many of the attendant advantages of the present disclosure will become more readily appreciated as the same become better understood by reference to the following detailed description, when taken in conjunction with the accompanying drawings, wherein:
Generally described, the present disclosure is directed to managing a subset of user contacts on a telecommunications device. Specifically, in one embodiment, aspects of the disclosure will be described with regard to determining at least two contact groups from a subset of contacts accessible by a telecommunications device and generating a contact display including at least one contact group from the subset based on a current context of a user of the telecommunications device. The current context may, for example, be one or more of a location, time, date, and the like. In one embodiment, the user of the telecommunications device can initially select the members of each of the contact groups from the subset of contacts. In this case, the user of the telecommunications device may also select and associate a context with each of the user-selected groups. Alternatively, a context associated with each of the user-selected groups may be determined automatically based on communication events between the user and the members of each group. In another embodiment, rather than being user-selected, the members of the at least two contact groups may be determined automatically based on a context associated with the user of the telecommunications device and a plurality of user communication events associated with the context.
In another embodiment, aspects of the disclosure will be described with regard to determining at least two contact groups from a subset of contacts accessible by a telecommunications device and generating a contact display including a representation of at least a portion of the first and second contact groups and a divider display object. Illustratively, the at least two contact groups can be determined in response to an add divider input initiated by a user of the telecommunications device. The divider display object generated in the contact display partitions the first contact group from the second contact group. In other embodiments, the divider display object can be repositioned to modify members of the contact groups. In still further embodiments, a plurality of divider display objects can be generated for visually partitioning other additional contact groups from the subset of contacts.
Although aspects of the present disclosure will be described with regard to an illustrative telecommunications environment and component interactions, telecommunications protocols, flow diagrams, and user interfaces, one skilled in the relevant art will appreciate that the disclosed embodiments are illustrative in nature and should not be construed as limiting. Specifically, although the term telecommunications device is used in this document, the term represents any type of device having a component for communicating with one or more other devices via one or more communication paths. Such communication paths can include wireless communication paths (via infra-red, RF, optical, terrestrial, or satellite communication media) and wired communication paths.
With reference now to
For each telecommunications device user, the contact group information may correspond to information associated with the generation of contact groups from a subset of user contacts accessible by a telecommunications device. The contact group information may be generated, at least in part, from information corresponding to interaction with individual users of telecommunications devices and maintained in a data store 110. Additionally, the contact management service 102 may obtain additional information from external sources, such as network-based data sources 120. The additional information may become part of the contact group information. Even further, the additional information may be used by the contact management service 102 to generate or process the contact group information. Such network-based data sources may include web sites, location based services, social network services, telecommunications services, message publication services, etc. While the data store 110 is depicted in
While the contact management service 102 is depicted in
As illustrated in
One skilled in the relevant art will appreciate that the contact management service 102 may correspond to a number of computer devices, such as server computing devices. Additionally, the external data source interface component 104, device interface component 106, and contact management component 108 may be implemented in a single computing device or across multiple computing devices. Likewise, although the contact management data store 110 is illustrated as local to the contact management service 102, the data store 110 can correspond to a distributed data store and/or network-based data store. One skilled in the relevant art will also appreciate that the contact management service 102 may include any one of a number of additional hardware and software components that would be utilized in the illustrative computerized network environment to carry out the illustrative functions of the service 102 and/or any of the individually identified components.
With continued reference to
In an illustrative embodiment, the telecommunications environment 100 can include a number of additional components, systems, and/or subsystems for facilitating communications with the telecommunications devices 112 and/or the contact management service 102. The additional components can include one or more switches or switching centers 116 (in GSM embodiments, Mobile Switching Centers or MSCs) for establishing communications with the telecommunications devices 112 via the telecommunication network 114, such as a cellular radio access network, an IP-based telecommunications network based on the family of IEEE 802.11 technical standards (“WiFi”) or IEEE 802.16 standards (“WiMax”), a converged wireless telecommunications network such as Unlicensed Mobile Access (UMA) or General Access Network (GAN), and other wired and wireless networks. The operation of telecommunication networks, such as telecommunication network 114 are well known and will not be described in greater detail. As illustrated in
With reference now to
The telecommunications device 112 performs functions by using the processing unit(s) 202 to execute instructions provided by the system memory 204. The telecommunications device 112 may also include one or more input devices 212 (keyboard, mouse device, specialized selection keys, etc.) and one or more output devices 214 (displays, printers, audio output mechanisms, etc.). Illustrative user interfaces for a telecommunications device 112 will be described with regard to
With continued reference to
As previously described, in accordance with an aspect of the present disclosure, a telecommunications device 112 can generate one or more displays on a user interface via an output device 214. In an illustrative embodiment, the displays include various display objects that represent user contacts, identifiers of contact groups, contact dividers, or combinations thereof. In an illustrative embodiment, display objects may be selectable by a user via any one of a variety of input methods and devices. Additionally, the determination of the display objects that are included in the displays may be predetermined, automatically determined (in real time or semi-real time), or manually configured/managed according to user-specified criteria. Further, the display and formatting of the display objects and the illustrative displays may be specified according to specific telecommunication device capabilities, service provider specifications, or user configurations.
With reference now to
At block 302, the contact management service 102 identifies a subset of user contacts from a set of user contacts. As similarly set forth above, a user contact may correspond to an individual person, an identifier associated with a person such as a telephone number, a group of people, an identifier associated with a group of people, and the like. In some embodiments, the set of user contacts from which the subset is identified is not limited and, in others, it may be limited such that only those contacts that the device has access to without requiring further input by user are included in the set. In other embodiments, the set from which the subset is identified may be further limited to contacts known to the user, contacts identified in one or more electronic address books, contacts having user-specified characteristics, and the like.
Additionally, in one illustrative embodiment, the subset of contacts can be selected by the user and subsequently maintained, for example, in data store 110 for future identification and access by the contact management service 102.
In another embodiment, a portion of the subset of contacts can be selected by the user of the telecommunications device 112, while a remaining portion of the subset of contacts are selected automatically based on one or more other factors. In one example, the factor used to select the remaining portion of the subset of contacts can be a frequency of communication between the user and one or more user contacts accessible by the telecommunications device 112. In this example, the contact management service 102 monitors communications between the user and each of the user's contacts accessible by the telecommunications device 112 and maintains data associated with the monitored communications. Based on the monitored communications and corresponding maintained data, the contact management service 102 may determine a frequency of communication between the user and each of the user's contacts. This information can then be used to determine the remaining portion of the subset of contacts. In one illustrative embodiment, the remaining portion of the subset of contacts can be selected based on the user contacts that have been in communication with the user the most number of times. In other embodiments, the contact management service 102 may track the types of communications between the user and the user's contacts, such as SMS messages, MMS messages, emails, voice calls, and the like, and then select the remaining portion of the subset of contacts based on the frequency of one type of communication or an aggregation of some or all types of communications. In addition, if aggregated, one type of communication can be weighted over other types. Even further, in other embodiments, the contact management service 102 may track only those communications initiated by the user to select the remaining portion of the subset of contacts based on the user's frequency of initiating communication with each of the user's contacts. Yet further, the contact management service 102 may track the frequency of communication between the user and each of the user's contacts during any period of time.
Additionally or alternatively, in a further embodiment, the identified subset of user contacts can be associated with a special rate plan offered by a telecommunications carrier providing communication services to the telecommunications device 112. Specifically, the user may be provided a special rate associated with any communications made between the user and any of the contacts identified in the subset. In addition to a special rate, the rate plan may have a variety of other parameters that may affect selection of the contacts to be included in the subset. For example, in one embodiment, the subset of contacts may be limited in number to correspond to a number of contacts with whom communications will be provided at a special rate. As another example, the subset of contacts may be editable only after a specified period of time has elapsed from initial selection (whether by the user or partially by automated selection based on other factors such as frequency of communication information).
With continued reference to
If, at block 304, the contact management service 102 determines that context information should take into consideration in the creation of contact groups, the contact management service 102 determines at least two contact groups from the identified subset of user contacts based on context information at block 306. In one embodiment, the contact management service 102 uses a context of the user of the telecommunications device and a plurality of user communication events associated with the context to determine contact groups. For example, the contact management service 102 may determine that any user contacts from the identified subset and with whom the user communicates using the user's telecommunications device at a particular geographic location, such as the user's place of employment, should be associated to form a first contact group, such as a work contact group. In another example, the contact management service 102 may determine that any user contacts from the identified subset and with whom the user communicates during particular times and dates, such as from 8 a.m. to 9 a.m. and 5 p.m. to 6 p.m. on Mondays through Fridays, should be associated to form a second contact group, such as a commuting contact group. In addition or alternatively, in another embodiment, the contact management service 102 uses a context of the user's contacts from the identified subset to determine a contact group. For example, the contact management service 102 may determine that two or more of the user's contacts are located in a single geographic region from 1 p.m. to 5 p.m. on Saturdays and that these user contacts should thus be associated to form a third contact group, such as a basketball contact group. In yet another example, the context information can include user preference information indicating preferred contacts for the user such as based on overall frequency of communication. The contact management service 102 may determine that these contacts form a V.I.P. contact group.
In one illustrative embodiment, the contact management service 102 may determine at least two contact groups based on context information such that each user contact from the subset may only belong to a single contact group. Alternatively, a user contact may be allowed to belong to more than one contact group. For example, while a spouse may be a member of a family contact group based on context information, the user may regularly communicate with the spouse at work and thus the spouse may also be a member of a work contact group based on other context information.
In another illustrative embodiment, the contact management service 102 may also determine an identifier for each determined contact group. In one embodiment, the contact group identifier may be determined based on context information associated with the corresponding group. For example, the context information may include information published or otherwise made available about members of the contact group, such as a subject line of calendar information for each of the members indicating that from 1 p.m. to 5 p.m. on Saturdays the contacts are at a basketball game. Accordingly, this contact group may be associated with a basketball identifier. In some embodiments, a user may be able to edit identifiers which were previously automatically determined by the contact management service 102. Alternatively, a user may provide the identifiers. In this embodiment, the contact management service 102 is configured to associate an identifier with each determined contact group, but requires user input to provide the specific corresponding identifier. The contact management service 102 may accordingly request such user input upon generation of the contact groups. In yet another embodiment, the contact management service 102 can associate a priority to the determined contact group based on preferences identified in or associated with the context information.
In a still further illustrative embodiment, the contact groups may be predetermined based on context information and maintained in the data store 110 (
With continued reference to
In yet another embodiment, the contact management service 102 can determine at least two contact groups from the subset of user contacts based on other user-created groups of contacts. Such user-created groups may include contacts other than those included in the subset of user contacts currently being processed. For example, a user may have previously created groups of work contacts, school contacts, and family contacts. Additionally, the subset of user contacts currently being processed may correspond to a group of favorite contacts. In this example, there may be additional contacts in each of the work, school, and family contact groups that are not included in the user's favorites contact group. Nonetheless, the contact management service 102 may use these other user-created work, school, and family contacts to determine contact groups from the favorite contacts subset. For example, a portion of the contacts in the favorite contacts subset may also belong to the user-created work contact group. Accordingly, the contact management service 102 may determine a first contact group from the favorite contacts subset to be a “favorite work” contact group based on the intersection of members between the favorite contacts subset and the user-created work contact group.
Next, at block 310, the contact management service 102 optionally predetermines context information for association with each of the at least two contact groups select by a user of the telecommunications device 112. As similarly, set forth above, the context information can correspond to information that is published, or otherwise made available, about events associated with the telecommunications device user, any one or more of the user's contacts, the telecommunications environment 100, or any combination thereof. By way of example, context information as used in determining contact groups includes, but is not limited to, location, time of day, individual travel designations (e.g., stationary, moving, velocity, heading, etc.), manual designations (e.g., location, status, mood, etc.), cost information (e.g., rate plans, location), and the like. In an illustrative embodiment, the context information associated with the contact group may be a selected from the same context information that is available in the formation of contact groups. Alternatively, the contact management service 102 may limit, or otherwise specify, context information that can be associated with a determined contact group.
In one embodiment, the contact management service 102 uses context information associated with the telecommunications device user and/or the members of each user-selected contact group to determine a context associated with the respective contact group. For example, the contact management service 102 may determine that the telecommunications device user always communications with user contacts in a “work” contact group while the user is at a particular geographic location, such as the user's place of employment. The contact management service 102 may thus associate this geographic location with the “work” contact group. In another example, the contact management service 102 may determine that the telecommunications device user always communicates with user contacts in a “commuting” contact group during particular times and dates, such as from 8 a.m. to 9 a.m. and 5 p.m. to 6 p.m. on Mondays through Fridays. The contact management service 102 may thus associate this time and date information with the “commuting” contact group. As another example, the contact management service 102 may determine that user contacts in a “basketball” contact group are all located in a single geographic region from 1 p.m. to 5 p.m. on Saturdays. The contact management service 102 may thus associate this location, day of the week, and time information with the “basketball” contact group.
In another embodiment, the contact management service 102 may identify a context for association with each contact group based on manual determination of the context associated with the formed content group. A variety of methodologies may be utilized to present users of a telecommunications device 112 with context information for selection and association with a particular contact group. Additionally, the selection and association of a context with a particular contact group by a user of the telecommunications device 112 may be achieved utilizing a variety of input methods and hardware or software components in the telecommunications device 112. In one illustrative embodiment, the telecommunications device user may generate a user interface for allowing a user to input, or otherwise select, a context, to be associated with a particular contact group. Additionally, the communication management service 102 may provide a telecommunications device user with the ability to edit dynamically determined context information, to modify the context information, or otherwise add/remove context information.
In yet another embodiment, rather than the contact management service 102 automatically determining a context associated with each of the contact groups based on context information and rather than providing for user selection of the context, a context may be predefined as being associated with a particular contact group. For example, a work contact group may be predefined as being associated with a geographic location corresponding to the telecommunications device user's place of employment. As also further explained below, one skilled in the relevant art will appreciate that block 310 may be omitted altogether or partially implemented in accordance with user preferences for example.
With continued reference to
While the contact management service 102 may compare the user's current context with context information previously associated with each of the contact groups, the contact management service 102 may also dynamically determine context information associated with each of the contact groups for comparison with the user's current context. For example, the contact management service 102 may determine that the user is currently located at a park. The contact management service 102 may then dynamically determine that user contacts in a “family” contact group are also located in the park or are on their way to the park. This context information may not be previously associated with the “family” contact group as the picnic may be a recently planned event. The contact management service 102 may thus dynamically determine that the “family” contact group corresponds to the user's current context and generate a display in which the “family” contact group is presented to user based on the user's current context.
In some embodiments, more than one contact group may correspond to the user's current context. In this case, the contact management service 102 may prioritize the identified contact groups based on one or more additional criteria. Such criteria may be predetermined by the service 102 or provided by the user of the telecommunications device. In one example, location based context information may be prioritized over date and time based context information. In another example, user provided context information, such as an “at work” designation, may be prioritized over any real time context information.
After identifying a contact group based on a user's current context, the contact management service 102 generates a display in which the identified contact group is presented. Illustrative user interfaces for displaying a contact group from the subset of user contacts based on a user's current context are provided in
It will be appreciated by those skilled in the art and others that the determination at block 304 is optional in some embodiments. For example, the routine 300 may be implemented without determining members of each of the contact groups based on context information at block 306. Alternatively, the routine 300 may be implemented only where the contact groups are created based on context information and thus, in this case, blocks 308 and 310 may be omitted. It will also be appreciated by one skilled in the art and others that the functionality at block 310 may also be optional. For example, in some embodiments, the contact management service 102 alternatively dynamically determines context information associated with each contact groups.
With reference now to
With reference to
With reference now to
With reference now to
With reference to
With reference now to
With reference to
With reference to
In one embodiment, while the “Work” contact group is identified and displayed based on the user's current context, other contacts from different contact groups may be simultaneously presented on the display screen 652. Accordingly, the “Work” contact group may be presented to a user of the telecommunications device as the contact group of relevance (i.e., the contact group identified based on the user's current context) in accordance with a number of methodologies, such as by providing a contact group identifier for only the identified contact group, prominently displaying only contacts from the identified contact group, providing any other emphasis for only those contacts in the identified contact group, and the like. In the current example, while one of the contacts 614 from the “Commuting” contact group (
With reference now to
With reference now to
With further reference to
With reference now to
As further illustrated in
In another embodiment, the display objects 722, 724 which are associated with the user contacts may be individually selectable and moveable to reposition the selected display object in a different contact group. In this embodiment, movement of a display object from the portion 706 on the display screen 700 (on the right side of the divider display object 704), for example, to the portion 708 on the display screen 700 (on the left side of the divider display object) causes the moved display object to become a member of a different contact group.
In yet another embodiment, contact groups, at least a part of which are displayed in the display screen 700, may be modified based on deleting a divider display object 704. In one example, selection of the divider display object 704 illustrated in
In a still further embodiment, upon addition of a first divider display object between contacts in the subset, the contact management service 102 may automatically generate one or more additional dividers to further define the group, or groups, formed by the insertion of the first divider display object. Specifically, the contact management service 102 can automatically generate a start divider display object, an end divider display object, or both in addition to the requested divider display object. This embodiment may be particularly applicable to embodiments in which the subset of contacts emulate rotation about an axis external to the telecommunications device display. By way of example, assume the contact management service 102 displays a subset of contacts that emulate rotation about an axis. In one aspect, the user may want to be able to visually distinguish between the first and last contact in the subset (or a start and an end of the subset). Accordingly, the contact management service 102 can automatically add a display object (e.g., a start or end divider) adjacent to contacts in a first and/or last logical position, respectively, in the subset. Accordingly, in the embodiment in which the subset of contacts emulate rotation about the external axis, the start and/or end divider display object provides the user with an indication that the user has cycled through to the first and/or last contact in the subset.
In one embodiment, start and/or end divider display objects may be automatically generated and displayed in response to a user's request to add a first divider display object. In another embodiment, the contact management service 102 may always initially generate a start and/or end divider display object for display with the subset of contacts without requiring user input.
In yet another embodiment, the contact management service 102 may provide additional functionality so that a user can cause the display to scroll immediately to the next divider positioned between contacts. In particular, the contact management service 102 may be able to immediately cause a next divider display object (previously positioned between contacts) and at least one contact adjacent to the next divider display object to be presented on the telecommunications device display in response to a user input. In this way, rather than displaying each contact from the subset in sequence via emulated rotation of the contacts, the contact management service 102 can bypass display of select contacts in the sequence (and which are not currently of interest to the user) by immediately advancing the display to a next divider display object in response to a user input. Accordingly, the contact management service 102 can advance the contacts displayed in increments defined by the positioning of the divider display objects.
In any of the foregoing embodiments, rather than the display objects 722, 724 corresponding exclusively to contacts from a subset of contacts, the display objects 722, 724 can correspond to individual contacts, groups of contacts each represented by a single graphical identifier, applications, other executable components, or any combination thereof, determined from a larger set. For example, instead of creating contact groups within a user's favorite set of contacts (which is a subset of all of the user's contacts), a user may create a favorite set of applications or a favorite set of executable components from which groups may be created, modified, and displayed using the divider display object 704 as described above.
Additionally, rather than being exclusively applicable to user contacts, any of the other foregoing embodiments, such as those described in reference to
All of the processes described herein may be embodied in, and fully automated via, software code modules executed by one or more general purpose computers or processors. The code modules may be stored in any type of computer-readable medium or other computer storage device. Some or all the methods may alternatively be embodied in specialized computer hardware. In addition, the components referred to herein may be implemented in hardware, software, firmware or a combination thereof.
Conditional language, such as, among others, “can,” “could,” “might,” or “may,” unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements and/or steps. Thus, such conditional language is not generally intended to imply that features, elements and/or steps are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without user input or prompting, whether these features, elements and/or steps are included or are to be performed in any particular embodiment.
Any process descriptions, elements, or blocks in the flow diagrams described herein and/or depicted in the attached figures should be understood as potentially representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps in the process. Alternate implementations are included within the scope of the embodiments described herein in which elements or functions may be deleted, executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those skilled in the art.
It should be emphasized that many variations and modifications may be made to the above-described embodiments, the elements of which are to be understood as being among other acceptable examples. All such modifications and variations are intended to be included herein within the scope of this disclosure and protected by the following claims.
This application is a continuation of U.S. patent application Ser. No. 12/413,390, filed on Mar. 27, 2009, entitled MANAGING CONTACT GROUPS FROM SUBSET OF USER CONTACTS, the disclosure of which is incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
4723209 | Hernandez et al. | Feb 1988 | A |
D296218 | Wells-Papanek et al. | Jun 1988 | S |
5590256 | Tchao | Dec 1996 | A |
5617539 | Ludwig et al. | Apr 1997 | A |
D384052 | Kodosky | Sep 1997 | S |
D388424 | DeMuro et al. | Dec 1997 | S |
D391948 | Eisenberg | Mar 1998 | S |
5724531 | Miyashita et al. | Mar 1998 | A |
5751980 | Musashi et al. | May 1998 | A |
D395427 | Arora et al. | Jun 1998 | S |
5793365 | Tang et al. | Aug 1998 | A |
5796394 | Wicks et al. | Aug 1998 | A |
D397687 | Arora et al. | Sep 1998 | S |
D398595 | Baer et al. | Sep 1998 | S |
5822123 | Davis et al. | Oct 1998 | A |
5867226 | Wehmeyer et al. | Feb 1999 | A |
5880733 | Horvitz et al. | Mar 1999 | A |
5889517 | Ueda et al. | Mar 1999 | A |
D415483 | Decker | Oct 1999 | S |
5987107 | Brown | Nov 1999 | A |
5987469 | Lewis | Nov 1999 | A |
6006200 | Boies et al. | Dec 1999 | A |
6023275 | Horvitz et al. | Feb 2000 | A |
6047233 | Salvatore, Jr. | Apr 2000 | A |
D424036 | Arora et al. | May 2000 | S |
D424541 | Mugura | May 2000 | S |
6104398 | Cox, Jr. | Aug 2000 | A |
6130726 | Darbee et al. | Oct 2000 | A |
6144863 | Charron | Nov 2000 | A |
6151059 | Schein et al. | Nov 2000 | A |
D437858 | Yasui et al. | Feb 2001 | S |
6188406 | Fong et al. | Feb 2001 | B1 |
D438873 | Wang et al. | Mar 2001 | S |
6201957 | Son et al. | Mar 2001 | B1 |
D440979 | Wang et al. | Apr 2001 | S |
6222921 | Mugura et al. | Apr 2001 | B1 |
6226367 | Smith et al. | May 2001 | B1 |
6236398 | Kojima et al. | May 2001 | B1 |
6249863 | Redford et al. | Jun 2001 | B1 |
D445426 | Wang et al. | Jul 2001 | S |
D446790 | Wang et al. | Aug 2001 | S |
6313877 | Anderson | Nov 2001 | B1 |
6332024 | Inoue et al. | Dec 2001 | B1 |
D454138 | Imamura et al. | Mar 2002 | S |
D454139 | Feldcamp | Mar 2002 | S |
6359635 | Perttunen | Mar 2002 | B1 |
6393430 | Van Ryzin | May 2002 | B1 |
D459361 | Inagaki | Jun 2002 | S |
D463444 | Istvan et al. | Sep 2002 | S |
6460181 | Donnelly | Oct 2002 | B1 |
6486870 | Kozu | Nov 2002 | B1 |
D467252 | Lee | Dec 2002 | S |
D469442 | Bohlen, Jr. et al. | Jan 2003 | S |
D470857 | Anderson et al. | Feb 2003 | S |
D471226 | Gray | Mar 2003 | S |
6532459 | Berson | Mar 2003 | B1 |
6538635 | Ringot | Mar 2003 | B1 |
D472902 | Nashida et al. | Apr 2003 | S |
D473236 | Robbin et al. | Apr 2003 | S |
D474198 | Barnes | May 2003 | S |
D474778 | Barnes | May 2003 | S |
D475064 | Nashida et al. | May 2003 | S |
6563515 | Reynolds et al. | May 2003 | B1 |
6577330 | Tsuda et al. | Jun 2003 | B1 |
6600936 | Karkkainen et al. | Jul 2003 | B1 |
D478912 | Johnson | Aug 2003 | S |
D485279 | DeCombe | Jan 2004 | S |
6678891 | Wilcox et al. | Jan 2004 | B1 |
D486499 | Hayashi et al. | Feb 2004 | S |
6741268 | Hayakawa | May 2004 | B1 |
6757365 | Bogard | Jun 2004 | B1 |
D495339 | Gildred | Aug 2004 | S |
6775659 | Clifton-Bligh | Aug 2004 | B2 |
6781575 | Hawkins et al. | Aug 2004 | B1 |
D495715 | Gildred | Sep 2004 | S |
6788987 | Slechta et al. | Sep 2004 | B2 |
6801849 | Szukala et al. | Oct 2004 | B2 |
6845153 | Tiburtius et al. | Jan 2005 | B2 |
6850255 | Muschetto | Feb 2005 | B2 |
6865404 | Tikkala et al. | Mar 2005 | B1 |
D506474 | Gildred | Jun 2005 | S |
6907575 | Duarte | Jun 2005 | B2 |
D507577 | Totten et al. | Jul 2005 | S |
6925650 | Arsenault et al. | Aug 2005 | B1 |
D510581 | Robbin et al. | Oct 2005 | S |
6959207 | Keinonen et al. | Oct 2005 | B2 |
6968179 | De Vries | Nov 2005 | B1 |
6975712 | Schnarel et al. | Dec 2005 | B1 |
6978473 | Nsonwu et al. | Dec 2005 | B1 |
7007239 | Hawkins et al. | Feb 2006 | B1 |
7036091 | Nguyen et al. | Apr 2006 | B1 |
7046993 | Haaramo et al. | May 2006 | B2 |
D523439 | Kuroda | Jun 2006 | S |
D523440 | Hernandez et al. | Jun 2006 | S |
D523868 | Kuroda | Jun 2006 | S |
7076546 | Bates et al. | Jul 2006 | B1 |
7083109 | Pouchak | Aug 2006 | B2 |
7086008 | Capps et al. | Aug 2006 | B2 |
7089287 | Bellotti et al. | Aug 2006 | B2 |
7099862 | Fitzpatrick et al. | Aug 2006 | B2 |
D528556 | Decombre | Sep 2006 | S |
7111788 | Reponen | Sep 2006 | B2 |
7117445 | Berger | Oct 2006 | B2 |
7137073 | Kim et al. | Nov 2006 | B2 |
7174516 | Chipchase | Feb 2007 | B2 |
7178109 | Hewson et al. | Feb 2007 | B2 |
7187761 | Bookstaff | Mar 2007 | B2 |
D540340 | Cummins | Apr 2007 | S |
D543986 | Rimas-Ribikauskas et al. | Jun 2007 | S |
D543987 | Rimas-Ribikauskas et al. | Jun 2007 | S |
D543992 | Vigesaa | Jun 2007 | S |
D544875 | Wang et al. | Jun 2007 | S |
D544877 | Sasser | Jun 2007 | S |
D545324 | Decombe | Jun 2007 | S |
7231229 | Hawkins et al. | Jun 2007 | B1 |
7236576 | Schnarel et al. | Jun 2007 | B2 |
7236780 | Benco et al. | Jun 2007 | B2 |
D545827 | Evans et al. | Jul 2007 | S |
D545832 | Armendariz | Jul 2007 | S |
D546342 | Armendariz | Jul 2007 | S |
D547321 | Viegers et al. | Jul 2007 | S |
7248677 | Randall et al. | Jul 2007 | B2 |
7248857 | Richardson et al. | Jul 2007 | B1 |
D548239 | Rimas-Ribikauskas et al. | Aug 2007 | S |
D548743 | Takahashi et al. | Aug 2007 | S |
D550681 | Totten et al. | Sep 2007 | S |
D551252 | Andre et al. | Sep 2007 | S |
D552114 | Tolle et al. | Oct 2007 | S |
D554142 | Cameron | Oct 2007 | S |
7280652 | Bocking et al. | Oct 2007 | B2 |
D554652 | Shen et al. | Nov 2007 | S |
D556765 | Evans et al. | Dec 2007 | S |
D557268 | Fletcher | Dec 2007 | S |
D558221 | Nagata et al. | Dec 2007 | S |
D562343 | Fletcher | Feb 2008 | S |
7330845 | Lee et al. | Feb 2008 | B2 |
D563972 | Sherry | Mar 2008 | S |
7343365 | Farmham et al. | Mar 2008 | B2 |
7343565 | Ying et al. | Mar 2008 | B2 |
D565586 | Shin et al. | Apr 2008 | S |
D565627 | Kase | Apr 2008 | S |
D567251 | Sadler | Apr 2008 | S |
D567817 | Kwag et al. | Apr 2008 | S |
7353034 | Haney | Apr 2008 | B2 |
7360174 | Grossman et al. | Apr 2008 | B2 |
D568334 | Okaro et al. | May 2008 | S |
D568897 | Byeon | May 2008 | S |
D568898 | Byeon | May 2008 | S |
D568899 | Byeon | May 2008 | S |
D569387 | Byeon | May 2008 | S |
7369850 | Andrew et al. | May 2008 | B2 |
D570369 | Fletcher | Jun 2008 | S |
D571819 | Scott et al. | Jun 2008 | S |
D573601 | Gregov et al. | Jul 2008 | S |
D574392 | Kwag et al. | Aug 2008 | S |
D575297 | Glezer et al. | Aug 2008 | S |
D575298 | Chen et al. | Aug 2008 | S |
D575792 | Benson | Aug 2008 | S |
D576174 | Ording et al. | Sep 2008 | S |
D577364 | Flynt et al. | Sep 2008 | S |
D578134 | Jasinski | Oct 2008 | S |
D578543 | Ulm et al. | Oct 2008 | S |
7437005 | Drucker et al. | Oct 2008 | B2 |
7440910 | Ruvolo et al. | Oct 2008 | B1 |
7444342 | Hall et al. | Oct 2008 | B1 |
D580450 | Chen et al. | Nov 2008 | S |
D580946 | Chen et al. | Nov 2008 | S |
7450927 | Creswell et al. | Nov 2008 | B1 |
D582426 | Chen et al. | Dec 2008 | S |
D582928 | Blankenship et al. | Dec 2008 | S |
D583823 | Chen et al. | Dec 2008 | S |
D584737 | Stone et al. | Jan 2009 | S |
D585453 | Chen et al. | Jan 2009 | S |
D585454 | Ismail | Jan 2009 | S |
D586361 | Horowitz et al. | Feb 2009 | S |
D586362 | Horowitz et al. | Feb 2009 | S |
7490295 | Chaudhri et al. | Feb 2009 | B2 |
D588148 | Stone et al. | Mar 2009 | S |
D588149 | Brownell et al. | Mar 2009 | S |
D588150 | Stone et al. | Mar 2009 | S |
7503014 | Tojo et al. | Mar 2009 | B2 |
7506246 | Hollander | Mar 2009 | B2 |
7512652 | Appelman et al. | Mar 2009 | B1 |
D589970 | Bhat et al. | Apr 2009 | S |
D590407 | Watanabe et al. | Apr 2009 | S |
D590412 | Saft et al. | Apr 2009 | S |
7519912 | Moody et al. | Apr 2009 | B2 |
7526306 | Brems et al. | Apr 2009 | B2 |
D592218 | Blankenship et al. | May 2009 | S |
D592674 | Kwag | May 2009 | S |
D593120 | Bouchard et al. | May 2009 | S |
7536654 | Anthony et al. | May 2009 | B2 |
D593574 | Guimaraes et al. | Jun 2009 | S |
D593576 | Ball et al. | Jun 2009 | S |
D594015 | Singh et al. | Jun 2009 | S |
D594465 | Hong et al. | Jun 2009 | S |
D594872 | Akimoto | Jun 2009 | S |
7543245 | Irimajiri | Jun 2009 | B2 |
7546543 | Louch et al. | Jun 2009 | B2 |
7555727 | Hawkins et al. | Jun 2009 | B2 |
D596192 | Shotel | Jul 2009 | S |
7562304 | Dixon et al. | Jul 2009 | B2 |
7577700 | Tolson et al. | Aug 2009 | B2 |
7580363 | Sorvari et al. | Aug 2009 | B2 |
D599368 | Kanga et al. | Sep 2009 | S |
D599806 | Brown et al. | Sep 2009 | S |
D599807 | Marashi | Sep 2009 | S |
D599810 | Scalisi et al. | Sep 2009 | S |
D599811 | Watanabe et al. | Sep 2009 | S |
D599812 | Hirsch | Sep 2009 | S |
D599813 | Hirsch | Sep 2009 | S |
D599814 | Ogura et al. | Sep 2009 | S |
D601153 | Setiawan et al. | Sep 2009 | S |
7587215 | Chakraborty et al. | Sep 2009 | B2 |
7587683 | Ito et al. | Sep 2009 | B2 |
D602038 | Channell et al. | Oct 2009 | S |
7603628 | Park | Oct 2009 | B2 |
D603415 | Lin et al. | Nov 2009 | S |
D603416 | Poling et al. | Nov 2009 | S |
D603418 | Magnani et al. | Nov 2009 | S |
D603420 | Channell | Nov 2009 | S |
D603867 | La et al. | Nov 2009 | S |
D604310 | Ahn | Nov 2009 | S |
D604316 | Hoefnagels et al. | Nov 2009 | S |
D604317 | Hoefnagels et al. | Nov 2009 | S |
D604740 | Matheny et al. | Nov 2009 | S |
7620996 | Torres et al. | Nov 2009 | B2 |
D605200 | Sakai | Dec 2009 | S |
D605652 | Plaisted et al. | Dec 2009 | S |
D605653 | Danton | Dec 2009 | S |
D606088 | Yokouchi et al. | Dec 2009 | S |
D606550 | La et al. | Dec 2009 | S |
D607002 | Jonasson et al. | Dec 2009 | S |
7636889 | Weber et al. | Dec 2009 | B2 |
D608364 | Walsh et al. | Jan 2010 | S |
D608366 | Matas | Jan 2010 | S |
D608367 | Scalisi et al. | Jan 2010 | S |
D608368 | Bamford | Jan 2010 | S |
7646745 | Caldwell et al. | Jan 2010 | B2 |
7650361 | Wong et al. | Jan 2010 | B1 |
D609714 | Oda et al. | Feb 2010 | S |
D609715 | Chaudhri | Feb 2010 | S |
D610159 | Matheny et al. | Feb 2010 | S |
D610161 | Matas | Feb 2010 | S |
7665028 | Cummins et al. | Feb 2010 | B2 |
7665033 | Byrne et al. | Feb 2010 | B2 |
D611056 | Langlois et al. | Mar 2010 | S |
D611484 | Mays et al. | Mar 2010 | S |
D611485 | Marashi | Mar 2010 | S |
D611489 | Bell et al. | Mar 2010 | S |
D611490 | Lee et al. | Mar 2010 | S |
D612394 | La et al. | Mar 2010 | S |
D612860 | Tarara et al. | Mar 2010 | S |
7673017 | Kim et al. | Mar 2010 | B2 |
7685520 | Rashkovskiy et al. | Mar 2010 | B2 |
7685530 | Sherrard | Mar 2010 | B2 |
D613300 | Chaudhri | Apr 2010 | S |
D613747 | Jonasson et al. | Apr 2010 | S |
D614191 | Takano et al. | Apr 2010 | S |
D614192 | Takano et al. | Apr 2010 | S |
D614633 | Watanabe et al. | Apr 2010 | S |
D614643 | Viegers et al. | Apr 2010 | S |
D614646 | Chen et al. | Apr 2010 | S |
7702543 | MacKay et al. | Apr 2010 | B2 |
7703031 | Nakagawa et al. | Apr 2010 | B2 |
7705833 | Kim | Apr 2010 | B2 |
D615090 | Sogabe | May 2010 | S |
D615546 | Lundy et al. | May 2010 | S |
D615549 | Caine et al. | May 2010 | S |
7720498 | Lee | May 2010 | B2 |
D617804 | Hirsch | Jun 2010 | S |
D617805 | Scalisi et al. | Jun 2010 | S |
D618250 | Stallings et al. | Jun 2010 | S |
7735021 | Padawer et al. | Jun 2010 | B2 |
7738912 | Hawkins et al. | Jun 2010 | B1 |
D619593 | Fujioka et al. | Jul 2010 | S |
D619594 | Jonasson et al. | Jul 2010 | S |
D620948 | Scalisi et al. | Aug 2010 | S |
D621844 | Van Os | Aug 2010 | S |
D621845 | Anzures et al. | Aug 2010 | S |
D622280 | Tarara | Aug 2010 | S |
7779358 | Gupta | Aug 2010 | B1 |
D624556 | Chaudhri | Sep 2010 | S |
7797641 | Karukka et al. | Sep 2010 | B2 |
D625325 | Vu et al. | Oct 2010 | S |
D626136 | Fujimura | Oct 2010 | S |
D627790 | Chaudhri | Nov 2010 | S |
D628206 | Lemay | Nov 2010 | S |
7831675 | Narayanaswami et al. | Nov 2010 | B2 |
7898600 | Lee et al. | Mar 2011 | B2 |
7900139 | Hosotsubo | Mar 2011 | B2 |
D638025 | Saft et al. | May 2011 | S |
7971222 | Ellis | Jun 2011 | B2 |
8015187 | Choi et al. | Sep 2011 | B2 |
8032470 | Heidenreich et al. | Oct 2011 | B1 |
8046801 | Ellis et al. | Oct 2011 | B2 |
D652843 | van Os | Jan 2012 | S |
8631351 | Fong et al. | Jan 2014 | B2 |
8671355 | Pegg | Mar 2014 | B2 |
9160828 | Vance et al. | Oct 2015 | B2 |
9195966 | Vance et al. | Nov 2015 | B2 |
9210247 | Vance et al. | Dec 2015 | B2 |
9304659 | Sherrard et al. | Apr 2016 | B2 |
9355382 | Vance et al. | May 2016 | B2 |
9363378 | McDaniel | Jun 2016 | B1 |
9396542 | Vance et al. | Jun 2016 | B2 |
20010044743 | McKinley et al. | Nov 2001 | A1 |
20010046886 | Ishigaki | Nov 2001 | A1 |
20020045960 | Phillips et al. | Apr 2002 | A1 |
20020052754 | Joyce et al. | May 2002 | A1 |
20020054164 | Uemura | May 2002 | A1 |
20020059201 | Work | May 2002 | A1 |
20020145623 | DeCombe | Oct 2002 | A1 |
20030014179 | Szukala et al. | Jan 2003 | A1 |
20030030670 | Duarte et al. | Feb 2003 | A1 |
20030034878 | Hull et al. | Feb 2003 | A1 |
20030078033 | Sauer et al. | Apr 2003 | A1 |
20030164818 | Miller-Smith et al. | Sep 2003 | A1 |
20030210265 | Haimberg | Nov 2003 | A1 |
20030224816 | Kundaje et al. | Dec 2003 | A1 |
20040017376 | Tagliabue et al. | Jan 2004 | A1 |
20040041836 | Zaner et al. | Mar 2004 | A1 |
20040046796 | Fujita | Mar 2004 | A1 |
20040067751 | Vandermeijden | Apr 2004 | A1 |
20040075691 | Moon | Apr 2004 | A1 |
20040077340 | Forsyth | Apr 2004 | A1 |
20040091093 | Bookstaff | May 2004 | A1 |
20040100479 | Nakano et al. | May 2004 | A1 |
20040102225 | Furuta et al. | May 2004 | A1 |
20040113927 | Quinn et al. | Jun 2004 | A1 |
20040119755 | Guibourge | Jun 2004 | A1 |
20040119758 | Grossman et al. | Jun 2004 | A1 |
20040122683 | Grossman et al. | Jun 2004 | A1 |
20040122684 | Kaikuranta | Jun 2004 | A1 |
20040133638 | Doss et al. | Jul 2004 | A1 |
20040155908 | Wagner | Aug 2004 | A1 |
20040162812 | Lane | Aug 2004 | A1 |
20040172455 | Green et al. | Sep 2004 | A1 |
20040185890 | Drozt et al. | Sep 2004 | A1 |
20040221239 | Hachigian et al. | Nov 2004 | A1 |
20040235520 | Cadiz et al. | Nov 2004 | A1 |
20040236749 | Cortright et al. | Nov 2004 | A1 |
20040237048 | Tojo et al. | Nov 2004 | A1 |
20040239982 | Gignac | Dec 2004 | A1 |
20040250217 | Tojo et al. | Dec 2004 | A1 |
20040268228 | Croney et al. | Dec 2004 | A1 |
20040268265 | Berger | Dec 2004 | A1 |
20050005235 | Satterfield et al. | Jan 2005 | A1 |
20050010876 | Robertson et al. | Jan 2005 | A1 |
20050033603 | Suzuki et al. | Feb 2005 | A1 |
20050033698 | Chapman | Feb 2005 | A1 |
20050039140 | Chen | Feb 2005 | A1 |
20050041011 | Silfverberg et al. | Feb 2005 | A1 |
20050071780 | Muller et al. | Mar 2005 | A1 |
20050079863 | Macaluso | Apr 2005 | A1 |
20050086611 | Takabe et al. | Apr 2005 | A1 |
20050091272 | Smith et al. | Apr 2005 | A1 |
20050094205 | Lo et al. | May 2005 | A1 |
20050114374 | Juszkiewicz et al. | May 2005 | A1 |
20050118996 | Lee et al. | Jun 2005 | A1 |
20050120306 | Klassen et al. | Jun 2005 | A1 |
20050138574 | Lin | Jun 2005 | A1 |
20050143135 | Brems et al. | Jun 2005 | A1 |
20050143138 | Lee et al. | Jun 2005 | A1 |
20050160376 | Sciammarella et al. | Jul 2005 | A1 |
20050163290 | Gilles et al. | Jul 2005 | A1 |
20050172001 | Zaner et al. | Aug 2005 | A1 |
20050182837 | Harris et al. | Aug 2005 | A1 |
20050188312 | Bocking et al. | Aug 2005 | A1 |
20050209994 | Noro et al. | Sep 2005 | A1 |
20050210104 | Torvinen | Sep 2005 | A1 |
20050221807 | Karlsson et al. | Oct 2005 | A1 |
20050229110 | Gegner et al. | Oct 2005 | A1 |
20050235225 | Pradhan et al. | Oct 2005 | A1 |
20050235226 | Watanabe et al. | Oct 2005 | A1 |
20050235251 | Arend et al. | Oct 2005 | A1 |
20050243979 | Starbuck et al. | Nov 2005 | A1 |
20050245236 | Servi et al. | Nov 2005 | A1 |
20050246654 | Hally et al. | Nov 2005 | A1 |
20050261011 | Scott | Nov 2005 | A1 |
20050261032 | Seo et al. | Nov 2005 | A1 |
20050268237 | Crane et al. | Dec 2005 | A1 |
20050278652 | Scholz | Dec 2005 | A1 |
20060009249 | Fu et al. | Jan 2006 | A1 |
20060010395 | Aaltonen | Jan 2006 | A1 |
20060030347 | Biswaas | Feb 2006 | A1 |
20060048076 | Vronay et al. | Mar 2006 | A1 |
20060053379 | Henderson et al. | Mar 2006 | A1 |
20060055700 | Niles et al. | Mar 2006 | A1 |
20060084410 | Sutaria et al. | Apr 2006 | A1 |
20060101350 | Scott | May 2006 | A1 |
20060112354 | Park | May 2006 | A1 |
20060123360 | Anwar et al. | Jun 2006 | A1 |
20060140015 | Kasamsetty | Jun 2006 | A1 |
20060141996 | Huh | Jun 2006 | A1 |
20060143574 | Ito et al. | Jun 2006 | A1 |
20060146765 | Van De Sluis | Jul 2006 | A1 |
20060148499 | Chie | Jul 2006 | A1 |
20060148522 | Chipchase et al. | Jul 2006 | A1 |
20060168539 | Hawkins et al. | Jul 2006 | A1 |
20060174121 | Omae et al. | Aug 2006 | A1 |
20060212829 | Yahiro et al. | Sep 2006 | A1 |
20060223518 | Haney | Oct 2006 | A1 |
20060224675 | Fox et al. | Oct 2006 | A1 |
20060242581 | Manion et al. | Oct 2006 | A1 |
20060242597 | Park | Oct 2006 | A1 |
20060253787 | Fogg | Nov 2006 | A1 |
20060277488 | Cok | Dec 2006 | A1 |
20060293057 | Mazerski et al. | Dec 2006 | A1 |
20070011617 | Akagawa et al. | Jan 2007 | A1 |
20070026645 | Lieber et al. | Feb 2007 | A1 |
20070027920 | Alvarado | Feb 2007 | A1 |
20070032267 | Haitani et al. | Feb 2007 | A1 |
20070033540 | Bridges et al. | Feb 2007 | A1 |
20070043688 | Kountz et al. | Feb 2007 | A1 |
20070060206 | Dam Nielsen et al. | Mar 2007 | A1 |
20070067738 | Flynt et al. | Mar 2007 | A1 |
20070072586 | Morhenn et al. | Mar 2007 | A1 |
20070073874 | Moghaddam et al. | Mar 2007 | A1 |
20070079246 | Morillon et al. | Apr 2007 | A1 |
20070118813 | Forstall et al. | May 2007 | A1 |
20070129112 | Tarn | Jun 2007 | A1 |
20070135103 | Middleton | Jun 2007 | A1 |
20070136687 | Pak | Jun 2007 | A1 |
20070150830 | Ording et al. | Jun 2007 | A1 |
20070162862 | Ogasawara et al. | Jul 2007 | A1 |
20070168262 | Morotomi et al. | Jul 2007 | A1 |
20070174389 | Armstrong et al. | Jul 2007 | A1 |
20070198947 | Cox et al. | Aug 2007 | A1 |
20070226645 | Kongqiao et al. | Sep 2007 | A1 |
20070250936 | Nakamura et al. | Oct 2007 | A1 |
20070268908 | Linkola et al. | Nov 2007 | A1 |
20070271528 | Park et al. | Nov 2007 | A1 |
20080014982 | Foxenland | Jan 2008 | A1 |
20080022228 | Kwon et al. | Jan 2008 | A1 |
20080034317 | Fard | Feb 2008 | A1 |
20080059570 | Bill | Mar 2008 | A1 |
20080081653 | Mock et al. | Apr 2008 | A1 |
20080086703 | Flynt et al. | Apr 2008 | A1 |
20080098311 | Delarue | Apr 2008 | A1 |
20080111826 | Endrikhovski et al. | May 2008 | A1 |
20080122870 | Brodersen et al. | May 2008 | A1 |
20080158189 | Kim | Jul 2008 | A1 |
20080172030 | Blomquist | Jul 2008 | A1 |
20080189614 | Jeong | Aug 2008 | A1 |
20080189627 | Nikitin et al. | Aug 2008 | A1 |
20080194934 | Ray et al. | Aug 2008 | A1 |
20080215978 | Bamba | Sep 2008 | A1 |
20080220751 | De Bast | Sep 2008 | A1 |
20080220752 | Forstall et al. | Sep 2008 | A1 |
20080235248 | Krantz et al. | Sep 2008 | A1 |
20080256170 | Hayashi et al. | Oct 2008 | A1 |
20080261569 | Britt et al. | Oct 2008 | A1 |
20080263069 | Harris et al. | Oct 2008 | A1 |
20080280600 | Zhou | Nov 2008 | A1 |
20080282158 | Aaltonen | Nov 2008 | A1 |
20080288612 | Kwon | Nov 2008 | A1 |
20080288880 | Reponen et al. | Nov 2008 | A1 |
20090013048 | Partaker et al. | Jan 2009 | A1 |
20090040875 | Buzescu et al. | Feb 2009 | A1 |
20090043847 | Laurila | Feb 2009 | A1 |
20090055484 | Vuong et al. | Feb 2009 | A1 |
20090077496 | Aravamudan et al. | Mar 2009 | A1 |
20090100363 | Pegg | Apr 2009 | A1 |
20090164923 | Ovi | Jun 2009 | A1 |
20090187630 | Narayanaswami et al. | Jul 2009 | A1 |
20090193512 | Buckley et al. | Jul 2009 | A1 |
20090199120 | Baxter et al. | Aug 2009 | A1 |
20090228513 | Tian | Sep 2009 | A1 |
20090300518 | Mock | Dec 2009 | A1 |
20090303188 | Triplett | Dec 2009 | A1 |
20100004008 | Abolrous et al. | Jan 2010 | A1 |
20100020727 | Narayan et al. | Jan 2010 | A1 |
20100020953 | Lidstrom et al. | Jan 2010 | A1 |
20100050123 | Sherrard et al. | Feb 2010 | A1 |
20100062753 | Wen | Mar 2010 | A1 |
20100064231 | Gupta | Mar 2010 | A1 |
20100094837 | O'Sullivan et al. | Apr 2010 | A1 |
20100095009 | Matuszewski et al. | Apr 2010 | A1 |
20100144331 | Koberg et al. | Jun 2010 | A1 |
20100180001 | Hardt | Jul 2010 | A1 |
20100190467 | Scott et al. | Jul 2010 | A1 |
20100190468 | Scott et al. | Jul 2010 | A1 |
20100241544 | Benson et al. | Sep 2010 | A1 |
20100245262 | Vance | Sep 2010 | A1 |
20100248701 | Vance et al. | Sep 2010 | A1 |
20100250606 | Vance et al. | Sep 2010 | A1 |
20100287504 | Vance et al. | Nov 2010 | A1 |
20100333029 | Smith et al. | Dec 2010 | A1 |
20110029892 | Kurtz et al. | Feb 2011 | A1 |
20110258547 | Symons et al. | Oct 2011 | A1 |
20120071244 | Gillo et al. | Mar 2012 | A1 |
20130019173 | Kotler et al. | Jan 2013 | A1 |
20130019203 | Kotler et al. | Jan 2013 | A1 |
20130024780 | Sutedja et al. | Jan 2013 | A1 |
20130275897 | Vance et al. | Oct 2013 | A1 |
20130281161 | Vance et al. | Oct 2013 | A1 |
20130283180 | Vance et al. | Oct 2013 | A1 |
20140033071 | Gruber et al. | Jan 2014 | A1 |
20140220942 | Vance et al. | Aug 2014 | A1 |
20150072644 | Sherrard et al. | Mar 2015 | A1 |
20150220220 | Sherrard et al. | Aug 2015 | A1 |
20160078097 | Vance et al. | Mar 2016 | A1 |
20170116532 | Vance et al. | Apr 2017 | A1 |
20170124175 | Vance et al. | May 2017 | A1 |
Number | Date | Country |
---|---|---|
10155431 | Jun 2003 | DE |
0767418 | Apr 1997 | EP |
1246434 | Oct 2002 | EP |
1469374 | Oct 2004 | EP |
1482758 | Dec 2004 | EP |
1571808 | Sep 2005 | EP |
1608190 | Dec 2005 | EP |
07-129363 | May 1995 | JP |
08-123658 | May 1996 | JP |
09-083630 | Mar 1997 | JP |
09-311661 | Dec 1997 | JP |
H11-088496 | Mar 1999 | JP |
H11-327741 | Nov 1999 | JP |
2000-259304 | Sep 2000 | JP |
2000-348058 | Dec 2000 | JP |
2002-009899 | Jan 2002 | JP |
2003-198705 | Jul 2003 | JP |
2004-208217 | Jul 2004 | JP |
2004-348601 | Dec 2004 | JP |
2005-072958 | Mar 2005 | JP |
3834039 | Oct 2006 | JP |
10-2002-0069964 | Sep 2002 | KR |
10-2004-0024967 | Mar 2004 | KR |
10-2005-0043148 | May 2005 | KR |
10-2006-0042808 | May 2006 | KR |
10-2007-0029009 | Mar 2007 | KR |
10-2008-0004127 | Jan 2008 | KR |
10-2008-0019614 | Mar 2008 | KR |
10-2008-0079716 | Sep 2008 | KR |
WO 0025501 | May 2000 | WO |
WO 03044756 | May 2003 | WO |
WO 03062976 | Jul 2003 | WO |
WO 2005045799 | May 2005 | WO |
WO 2005064441 | Jul 2005 | WO |
WO 2005120112 | Dec 2005 | WO |
WO 2006016227 | Feb 2006 | WO |
WO 2006067567 | Jun 2006 | WO |
WO 2007093997 | Aug 2007 | WO |
WO 2007143678 | Dec 2007 | WO |
WO 2008030776 | Mar 2008 | WO |
WO 2010111610 | Sep 2010 | WO |
WO 2010111614 | Sep 2010 | WO |
WO 2010111637 | Sep 2010 | WO |
WO 2010111642 | Sep 2010 | WO |
WO 2010111643 | Sep 2010 | WO |
WO 2010111670 | Sep 2010 | WO |
WO 2010111675 | Sep 2010 | WO |
WO 2010111679 | Sep 2010 | WO |
Entry |
---|
Alltel Corp at Lehman Brothers Worldwide Wireless, Wirelein, and Media Conference, Fair Disclosure Wire, May 22, 2006. |
Alltel Launches ‘My Circle,’ a One-of-a-Kind Program That Gives Customers Free Calls to Any Network or Number They Choose, Business Wire, Apr. 20, 2006, pp. 1, New York. |
Alltel's ‘My Circle’ Plan Lets Subscribers Adds 10 Numbers for Unlimited Calls, Wireless News, Apr. 23, 2006, pp. 2, Coventry. |
Belson, K., Alltel to Offer Free-Calling Plan, With Limits, New York Times, Apr. 21, 2006, pp. C9, New York. |
Boy Genius, LG Xenon hitting AT&T Before Christmas?, http://www.boygeniusreport.com/2008/09/24/lg-xenon-hitting-att-before-christmas/, Sep. 24, 2008, pp. 1. |
Cuneo, A.Z., Alltel Gets Aggressive in Telecom War, Advertising Age, Chicago (Midwest region edition), Apr. 24, 2006, vol. 77, Issue 17, pp. 8. |
Larson, V., Alltel's free wireless calling plan paying off, Knight Rider Tribune Business News, May 2005, pp. 2. |
LG Xenon User Guide, AT&T, Apr. 8, 2009, pp. 146. |
MobileCom Provides All Residential Pay as You Go Subscribers the Ability to Talk for 1 Piaster Per Minute Day and Night, www.albawaba.com, Mar. 14, 2006. |
Sellers, P., MCI Communications Yes, Brands Can Still Work Magic, www.money.cnn.com, Feb. 7, 1994. |
Weisser, C., et al., What do you pay to stay connected?, Money Magazine, http://money.cnn.com/2003/11/20/pf/portability_strategy_0312/index.htm, Nov. 24, 2003. |
European Search Report issued in connection with PCT/US2006022645., dated Sep. 6, 2011. |
Second Office Action in Chinese Application No. 200680020479.9 dated Mar. 22, 2012. |
Office Action in Canadian Application No. 2588250 dated Aug. 23, 2013. |
International Search Report (PCT/US2010/028954)., dated Oct. 27, 2010. |
International Preliminary Report on Patentability in application No. PCT/US2010/028954 dated Sep. 27, 2011. |
International Search Report (PCT/US2010/028960)., dated Oct. 26, 2010. |
International Preliminary Report on Patentability in application No. PCT/US2010/028960 dated Sep. 27, 2011. |
International Search Report (PCT/US2010/028947)., dated Nov. 12, 2010. |
International Preliminary Report on Patentability in application No. PCT/US2010/028947 dated Sep. 27, 2011. |
Office Action in R.O.C. Application No. 098304597 dated Dec. 15, 2011, in 4 pages. |
International Search Report (PCT/US2010/028894)., dated Nov. 12, 2010. |
International Preliminary Report on Patentability in application No. PCT/US2010/028894 dated Sep. 27, 2011. |
International Search Report issued in connection with PCT/US2010/028857., dated Oct. 11, 2010. |
International Preliminary Report on Patentability in application No. PCT/US2010/028857 dated Sep. 27, 2011. |
International Search Report issued in connection with PCT/US2010/028863., dated Oct. 22, 2010. |
International Preliminary Report on Patentability in application No. PCT/2010/028863 dated Sep. 27, 2011. |
International Search Report (PCT/US2010/028905)., dated Nov. 12, 2010. |
International Preliminary Report on Patentability in application No. PCT/US2010/028905 dated Sep. 27, 2011. |
International Search Report issued in connection with PCT/US2010/028904., dated Nov. 8, 2010. |
International Preliminary Report on Patentability in application No. PCT/US/2010/028904 dated Sep. 27, 2011. |
First Office Action in European Application No. 07812026.8 dated Jul. 17, 2012. |
International Search Report (PCT/US2007070475)., dated Jun. 29, 2011. |
Office Action in Canadian Application No. 2657240 dated Sep. 3, 2013. |
Number | Date | Country | |
---|---|---|---|
20160088139 A1 | Mar 2016 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 12413390 | Mar 2009 | US |
Child | 14961798 | US |