US 8,595,649 B2Grant
Preferred contact group centric interface
Issue Date:2013-11-26
•31 Claims
•30 Drawing Sheets
Abstract
A preferred contact group centric interface for a communication device can be used to facilitate communications by a user. The user interface can be arranged to activate from a user's “home page” on the display, from an idle screen that is accessed after a timeout period expires, or any other appropriate mechanism that activates the preferred contact group centric experience. A user selects the preferred contact group from among an array of the user's contacts. Once the contact group is configured, a minimal number of navigation/selection features is necessary to activate any number of communication modes available to the contacts. The contact group is configured such that simple and quick navigation between the contact members is achieved. The contact group can be presented in 2D and 3D arrangements, in any number of list or geometric configurations. A pricing plan can optionally be tied to each member of the contact group.
Metadata
Assignee
- T-Mobile USA, Inc.
Inventors
- Andrew Sherrard
- Warren McNeel
- Jasdeep Singh Chugh
- Stephen John O'Connor
- Mikkel Crone Koser
- Richard Paul Turnnidge
- Michael Thomas Hendrick
- Gary Sentman
- Karl Warfel
- Wen-Hsing Chang
- Sally Abolrous
- Adrian Buzescu
Application Information
Application Number:US 12/492,267
Filing Date:2009-06-26
Priority Date:2005-06-10
Art Unit:2171
Classifications
IPC:
G06F3/00
Patent Drawings (30 sheets)
Description
Cross-Reference to Related Applications
[0001] This utility patent application is a continuation of U.S. Patent Publication No. 2007/0035513 A1 filed on Apr. 10, 2006 (and accorded U.S. application Ser. No. 11/400,925), which in turn claims the benefit under 35 U.S.C. §119(e) of U.S. Provisional Patent Application No. 60/689,581 filed on Jun. 10, 2005, which is hereby incorporated by reference in its entirety.
Background of the Invention
[0002] 1. Field of the Invention
[0003] This present invention relates generally to user interfaces that are centered about a user's preferred group of contacts on a communication device.
[0004] 2. Description of the Related Art
[0005] Cellular telephones have become common communication tools in modern society. A wide variety of handset styles are available such as the “clam shell” flip-style cellular telephones, the non-flip or “candy-bar” style cellular telephones, and other cellular telephones with pivoting displays. While the internal designs of the cellular telephones may be quite different, each is generally designed ergonomically for maximum convenience and comfort. A variety of button and selector key configurations are also available, some with ergonomic design in mind and others with enhanced specialized functionality. Each cellular telephone has its own style and functional features that provide a unique set of user experiences.
[0006] Many modern cellular telephone devices also incorporate organizational tools that have traditionally been found in personal information managers or PIMs. Examples of PIM functionalities that may be incorporated into cellular telephone devices include personal call lists, business contact call lists, phone book information, calendars, personal reminders and other information. Moreover, the popularity of certain tools and functionalities traditionally associated with non-telecommunications devices, such as digital still and video cameras, MP3 players, and computers (with applications including e-mail, instant text messaging and photo messaging), have increased the interest in providing cellular telephone devices incorporating a wide variety of non-telecommunications functions.
[0007] The present disclosure has evaluated and contemplated a variety of these and other functions to provide a user interface system with ease of use that is centered about a user's preferred group of contacts. The group centered user interface is very useful in mobile or portable electronic devices such as cellular communication devices, PDAs, PIMs, as well as other devices. Moreover, the present disclosure contemplates that special billing systems may be applied to the group of contacts.
Brief Description of the Drawings
[0008] FIG. 1 is an illustration of various configurations of the user interface idle screen.
[0009] FIG. 2 is a screenshot of an example communication options menu for the user interface.
[0010] FIG. 3 is a diagram illustrating a first time power-up initialization sequence.
[0011] FIG. 4 is an illustration of example idle screens and other features related thereto.
[0012] FIG. 5 is an illustration of a user interaction sequence for a user interface for adding preferred contacts.
[0013] FIG. 6 is an illustration of a user interaction sequence for another aspect of a preferred contact group interface for adding preferred contacts.
[0014] FIG. 7 is an illustration of an example user interaction sequence for selection of a picture for a preferred contact.
[0015] FIG. 8 is an illustration of an example interaction sequence for modification of preferred contacts.
[0016] FIG. 9 is an illustration of an example user interaction sequence to change the order of the user's preferred contacts.
[0017] FIG. 10 is an illustration of an example user interface interaction sequence for changing various settings associated with the preferred contact group centric interface.
[0018] FIG. 11 is an illustration of an example user interface interaction sequence that illustrates various communication modes associated with a preferred contact.
[0019] FIG. 12 is an illustration of an example user interface interaction sequence that illustrates additional communication modes associated with a contact.
[0020] FIG. 13 is an illustration of another example user interface interaction sequence that illustrates selection of various communication modes associated with a contact
[0021] FIG. 14 is an illustration of a user interface interaction sequence for creation of a graphical icon for a preferred contact from a downloaded picture.
[0022] FIG. 15 is an illustration of an example user interface interaction sequence for an incoming communication notification associated with a contact.
[0023] FIGS. 16A-16E are illustrations of an example Web-based user interface for configuration and management of a preferred contact group user interface.
[0024] FIGS. 17A-17C are illustrations of an example WAP-based user interface for configuration and management of a preferred contact group user interface.
Detailed Description of the Invention
[0025] The present description relates to a preferred contact group centric interface that can be used to facilitate communications by the user with any of his or her designated preferred contacts via a communication device. The user interface can be arranged to activate from a user's “home page” on the display of his or her communication device, from an idle screen that is accessed after a timeout period expires, or any other appropriate mechanism that activates the preferred contact group centric experience.
[0026] Briefly stated, a preferred contact group centric interface for a communication device can be used to facilitate communications by a user. A user selects the preferred contact group from among an array of the user's contacts. Once the contact group is configured, a minimal number of navigation/selection features is necessary to activate any number of communication modes available to the contacts. The contact group is configured such that simple and quick navigation between the contact members is achieved. The contact group can be presented in two dimensional and three dimensional arrangements, and in any number of list or geometric configurations. A pricing plan may optionally be tied to the provision of communications services between the user and his or her preferred contact group.
[0027] The preferred contact group centric experience is designed to facilitate quick and easy selection of a contact from among an array of the user's contacts (as designated by the user), followed by quick and easy application selection from a variety of communications modes, including single-click initiation of a communication mode of a default contact or a default communication mode. Although many of the descriptions contained herein illustrate a grouping of five (5) key contacts related to the interface, the exact number of contacts is not significant and any number of contacts (e.g., 10, 20, 100, etc) can be employed individually or as part of groups. Moreover, the term communication device is intended to cover a wide variety of devices such as, for example, cellular telephone type devices, PDA/PIM style devices, as well as other devices that include communication facilities.
[0028] In one example, a display of five preferred contacts is presented on the idle screen of the user's communication device. The user may initiate a communication mode for a pre-selected default contact with a single click, or may swiftly traverse through his or her contacts using navigation keys configured for such purpose (e.g., up/down/left/right keys) until the desired contact is highlighted, then may initiate a pre-selected default communication to the highlighted contact simply by pressing the designated default key on the communication device or may traverse through numerous other communications modes that are available to communicate with the selected contact (e.g. e-mail, instant messaging, or photo messaging) simply by using navigation keys configured for such purpose (e.g., up/down/left/right keys) and then pressing a designated selection button on the communication device. The interface is contact group centric in that the interface experience commences with the selection of the desired recipient (either manually or by default) from the user's preferred contact group, followed by selection of the desired mode of communication with a selected contact (either via single-click initiation of a default mode of communication or via a communication mode menu).
[0029] While some conventional address book menus on communication devices do provide a minimal amount of person centric communications, the contact group centric interface is unique in that it provides a user with a novel method to select both preferred contacts and preferred communication modes through a single, visually appealing interface. The user's preferred contacts, as well as communications options relating to those contacts, may be presented in a list-styled arrangement, a circular-styled arrangement, an elliptical-styled arrangement, or some other geometric-styled arrangement such as pentagonal, hexagonal, “X” shaped, “T” shaped, or “+” shaped arrangements. In addition, the presentation of all communication modes in one location, accessible through presentation of the contacts on an idle screen, is novel to the preferred contact group centric interface. Example screenshots for various views of the preferred contact group centric interface are presented below, along with communication mode screenshots. User contacts are chosen in advance by the user and remain in the order selected until the user replaces or rearranges his or her contacts, thereby providing predictability in user interface interaction. For example, if the user selects “MOM” as his or her first contact, then only a single click of a designated key is required to call “MOM”, until the user changes the order and moves “MOM” to another location among his or her preferred contacts. This is an important novel concept of the preferred contact group centric interface and an enhancement to current user interface experiences.
[0030] Current cellular telephone user interfaces are designed in a very feature centric manner. For example, to make voice calls on a conventional cellular telephone, users typically access the device's address book. In order to type and transmit a text message, the user must typically first access a “messages” menu and then select a “compose” function from the menu, followed by selecting the desired recipient of the message. While some cellular telephones do permit a user to send a text message, for example, from a phone book menu, this user experience is not optimal in terms of minimizing number of key clicks and overall ease of navigation. Requiring users to navigate to numerous menus and locations in the traditional user interface also negatively impacts of the user's ability to discover those features. In summary, the user experience for current cellular telephones is very feature driven rather than contact centric.
[0031] The preferred contact group centric interface brings the user's most-desired contacts “front and center” to the idle screen (or some other appropriate screen) of the device display. Through easy and intuitive selection of a desired contact among an array of contacts, the user is then able to quickly access a variety of communication modes available to communicate with the contact, such as initiating a voice call, sending a text, picture, voice or instant message (IM), or sending an email. The preferred contact group centric interface also enables a novel scalable user experience that provides a “front and center” presentation from which to add new communication services.
[0032] This concept may benefit both the end customer and the service provider (e.g., a wireless telecommunications carrier). The service provider supporting the communication device may offer special, desirable pricing plans in conjunction with the unique qualities of the preferred contact group centric interface. For instance, the service provider may offer a special price plan providing unlimited incoming and outgoing voice calls between the user and his or her designated preferred contacts. By way of further example, the service provider may expand its offering of unlimited services to include unlimited messaging as well as data use related to the user's designated preferred contacts. Further expansion of the price plan can include calling to international numbers.
[0033] The idle screen can be defined at the front/home screen of the communication device, and may include the name of the service provider, battery level, wireless signal strength, date, time, and may provide access to the menu functions of the phone.
[0034] The display of the user's contacts on the preferred contact group centric interface's idle screen can be integrated into the background wallpaper through transparency.
[0035] In another embodiment, the user's contacts can be a Web-enabled page that is downloaded from a network connection such as a Web page or a WAP page, possibly including active X, Java, Flash, or some other scripting or executable format that provides a uniform interaction on all similar communications devices. Contacts can be managed through the Web, or WAP, other over-The-air transport technology, a cable interface with the device or other connection to another device (e.g., personal computer).
[0036] FIG. 1 is an illustration of various configurations (100) of the preferred contact group centric interface idle screen. Screenshot 110 illustrates a circular style idle screen where each contact in the user's contact group is arranged about a center axis on the graphics display. The currently-selected contact is illustrated in the bottom center portion of the screen, but any designated location can be used for the selected contact. In example screenshot 110, the dimensions of the graphical icon (a photo in this case) are larger for the selected contact than the other non-selected contacts. In example screenshot 110, the dimensions of the graphical icon are determined by the physical screen location (e.g., bottom center is larger than right/left, which are larger than top right and top left) relative to an axis or rotation (to be discussed later). The dimensions associated with the graphical icons can be the same for every contact regardless of screen location, different for every contact based on screen location, or according to some other specified motif Text identifying the selected contact's name is included beneath the associated graphical icon. The selected contact's name may also be overlaid on the graphic in a visually appealing manner.
[0037] Screenshot 120 illustrates a list-style idle screen configuration where each contact in the user's contact group is arranged in a vertical list about a linear axis with graphical icons positioned on the left hand side of the screen and text identifying the corresponding contacts name on right hand side of the screen. A selected contact is illustrated in an inverse video format or some other graphical form highlighting. In one example, the selected contact always appears in a fixed location on the display (e.g., the top most position, the bottom most position, the center position, etc.) and the user interface is arranged to vertically scroll up and down through the list. In another example, the highlighting indicator can be moved up and down through the contact list. In still another example, the list has a wrap-around effect where scrolling from the top of the display continues at the bottom of the list, and vice-versa. The list-style idle screen may also be displayed horizontally.
[0038] Screenshot 130 illustrates another circular style configuration where each contact in the user's contact group is arranged about a center axis on the display, with the currently-selected contact being located in the center of the other non-selected contacts. In example screenshot 130, the dimensions of the graphical icon (a photo in this case) are larger for the selected contact than the other non-selected contacts. Text identifying the selected contact's name is included around the bottom line of the graphical display.
[0039] Screenshot 140 illustrates another circular style configuration where each contact in the user's contact group is arranged about a center axis on the graphics display in a three-dimensional space. The dimensions of the graphical icon (a photo in this case) are larger for the selected contact than the other non-selected contacts. Text identifying the selected contact's name is included above the graphical icon, below the graphical icon, or overlapping the top portion of the graphical icon as illustrated in the figure. The graphical icons are depicted with a three-dimensional appearance that is akin to a sphere with an image wrapped around the visible face. The user interface can be arranged such that the selected icon can be changed by rotation about a three-dimensional axis. Shadows can be added to reflect a three dimensional look.
[0040] Each of the above-described idle screens permits the user to change the currently-selected contact by traversing the group of contacts in the user's contact group via the various navigation buttons/interfaces on the communication device (e.g., a wireless communication device, a cellular telephone, a PDA or PIN style device, etc.). A variety of graphical effects can be applied to the display screen when the user traverses the group of contacts appearing in the interface, such as an animated rotation effect, a picture swap effect, a fade-in effect, a fade-out effect, a fly-in effect, a fly-out effect, a dissolve-in effect, a dissolve-out effect, a spiral-in effect, a spiral-out effect, a slide-in effect, and a slide-out effect.
[0041] The preferred contact group centric interface that is described herein is described in terms of navigation/selection buttons and keys on the communication device, as well as other specially designated selectors that are used for initiating and cancelling telephone calls. However, any appropriate navigation/selection means is contemplated within the scope of this discussion including, but not limited to a keypad, a directional key, a dynamically assigned soft key, a joypad-style interface, a joystick-style interface, a trackball-style interface, a touch screen type interface, and a stylus type interface. Other means of navigation/selection can include side key push and hold, speech recognition, and gesture recognition.
[0042] FIG. 2 is a screenshot of an example list-style communication options menu (200) for the preferred contact group centric interface. After selecting the options screen, a number of communication modes are accessible. For this example screen (200), a communication mode can be selected by traversing through the list of available communication modes and pressing the select key, or by pressing the corresponding number on the keypad. The illustrated communication modes include placing a telephone call (“1. Call”), sending a text message (“2. Send Message”), sending a picture (“3. Share Picture”), sending a voice message (“4. Send Voice Message”), sending an instant message (“5. Send IM”), and sending an email message (“6. Send E-mail”). Additionally, maintenance methods can be selected from the options screen such as, for example, viewing activity logs (“7. Activity Log”) and editing the contacts profile (“8. Edit Profile”).
[0043] FIG. 3 is a diagram illustrating a first time power-up initialization sequence (300) that can be employed by a communication device in order to complete registration/activation with a service provider.
[0044] After initial power up, a timeout occurs and the communication device displays pre-activation idle screen 310. After activation is completed by the user with the service provider (e.g., via a telephone call, in a company store, over the Internet, or by other means), an SMS message is sent to the communication device. The communication device receives the SMS message and displays a text message receipt screen such as SMS screen 320. The user can either select “View” or “Exit” from SMS screen 320. Selection of “View” causes the communication device to display a welcome message such as welcome screen 330. The user can exit from welcome screen 330 by selecting “Options” or “Back”, resulting in the communication device transferring to the preferred contact group centric interface's main or default screen, which is illustrated as post-activation idle screen 340. User selection of “Exit” from SMS screen 320 also results in the communication device changing to the post-activation idle screen 340.
[0045] Once the preferred contact group centric interface is available on the communication device, the default main screen or idle screen can be initialized for a selected group of contacts that are considered within the user's preferred contacts group. Special telecommunications pricing and/or services associated with the user's preferred contacts group may be associated with a special pricing plan. When the user's preferred contacts are keyed to a special pricing plan, a service provider may desire that the user's group membership be changed only at the beginning of a billing cycle or during some other revolving enrollment period. The user may designate the membership of his or her preferred contact group via the communication device, a customer service center representative, a computer connected through the Internet, or some other mechanism.
[0046] FIG. 4 is an illustration of example idle screens (400) and other features related thereto.
[0047] A partially-populated idle screen includes a mix of graphical identifiers associated with the user's preferred contacts, as illustrated in idle screen 410 of FIG. 4 . A default picture icon can be used to represent a preferred contact in the group if no other graphical identifier has been assigned by the user, as illustrated by default picture icon 412. A thumbnail size picture can be assigned to a preferred contact as illustrated by icon 414. An unpopulated or unassigned icon includes another graphical identifier to indicate that another contact can be assigned to the group as illustrated by default unpopulated contact icon in 416.
[0048] A fully populated idle screen includes a mix of graphical identifiers associated for the various preferred contacts as illustrated in screenshot 420 of FIG. 4 . Each contact in the user's preferred contact group is illustrated with thumbnail pictures in this example, but is not so limited. Optional status indicators can be dynamically assigned to the graphical indicators as illustrated by example indicators 422 and 424. Indicators 422 illustrate a graphical indicator and a text indicator for a missed telephone call from one identified contact (e.g., Nate). Indicator 424 illustrates that an email message is waiting from another identified contact. Other indicators can also be associated with a contact, such as graphical icons and/or text strings as may be desired for a variety of indications such as text message waiting, voice message waiting, picture message waiting, as well as others.
[0049] The optional status indicators can also be tied to a variety of other features, such as presence information, upcoming dates and appointments, and a mood level associated with the particular contact.
[0050] Presence information indicators can reveal the contact's current availability status (e.g., “available”, “unavailable”, “on-line”, “off-line”, “busy”, “out to lunch”, “in a meeting”, “be right back”, “away”), their location status (“at the corner of 5th Ave.”), as well as other user configurable presence indicators (e.g., “meet me for lunch at 2 PM”).
[0051] Upcoming dates and appointments indicators can reveal the contact's birthday, anniversary, and other important dates and appointments.
[0052] Mood level indicators can be utilized to project a likely mood upon a preferred contact, such as happy, sad, or ambivalent, wherein the mood level can be changed dynamically based on a number of criteria. For example, if a user has not contacted a preferred contact recently, or not as frequently as other contacts from the user's preferred contact group, the mood indicator may designate the contact as sad. In contrast, a frequently contacted contact can have a mood indicator of happy. The mood indicators can also be tied to other items, such as a daily horoscope, or updated in response to a presence data that is provided by the contact, such as through an instant messaging program.
[0053] Other information such as current physical location of the contact (e.g., near the user, in the same city as the user) using location based technology can also be displayed. In addition, relevant content related to the contact may also be displayed (e.g., if contact is interested in a specific musical act, then the musical act's upcoming concert date can be displayed, along with a hotlink to purchase tickets).
[0054] FIG. 5 is an illustration of a user interaction sequence (500) for adding preferred contacts. The process flow (500) of FIG. 5 begins at the depicted unpopulated idle screen.
[0055] The user can press the “Select” key (e.g., the center button on a joypad, an “OK” button, or some other button) from the idle screen to add a contact for the currently selected contact group member. The pressing of the “Select” key results in another screen that either replaces the current screen with an “Add Group Contact” dialog or overlays the current screen (e.g., a pop-up window). The dialog notifies the user that a new contact is being added to the currently selected group (which was unpopulated in this example). The preferred contact group centric interface also permits the user to select “Create new”, “Get from phonebook” or “Back.” Selection of “Back” cancels the “add contact” dialog box and returns to the idle screen.
[0056] Selection of “Create new” from the “Add Group Contact” dialog transitions the preferred contact group centric interface to a “Create new” template with one or more data entry fields such as name, number, picture, etc. The fields could also include a wide variety of additional information, including e-mail address, home address, birthday, favorite ice cream, place of birth, and other information. The user can return to the prior screen with selection of the “Back” key, or enter data into one or more of the various data entry fields.
[0057] Data can be entered into the data entry fields using various keys and/or input devices available for the communication device. Once the user has entered data, the user can either cancel the entered data or select the “Save” key. Pressing the “Cancel” key returns the preferred contact group centric interface to the prior screen, which is the “Add Group Contact” dialog, while pressing the “Save” key transfers the preferred contact group centric interface to a confirmation dialog.
[0058] The confirmation dialog requests the user to approve saving the information for the selected contact from the user's preferred contact group. Approval can be rejected by the user by depressing one key function (e.g., “No”), or accepted by depressing another key function (e.g., “Yes”). Rejection of approval returns the process to the prior screen. When approval is accepted, the entered data is transmitted by the communication device to the service provider for records updating, and a dialog screen is displayed to indicate that the server is being updated.
[0059] After a timeout period has expired, processing returns to the idle screen where a wait indicator (e.g., an hourglass) is displayed for the previously selected icon. After the service provider has updated records for the communication device on server, a message is transmitted to the communication device to indicate that the records have been successfully updated (or perhaps an error message if some other error occurs). The updated records dialog screen can be dismissed with a user interaction such as pressing an “OK” button, and the user interface resumes the idle screen with the populated contact now present.
[0060] FIG. 6 is an illustration of a user interaction sequence (600) for another aspect of a preferred contact group centric interface for adding preferred contacts. The process flow (600) of FIG. 6 begins at the depicted unpopulated idle screen.
[0061] The user can press the “Select” key (e.g., the center button on a joypad, an “OK” button, or some other button) from the idle screen to add a contact for the currently selected contact group member. Pressing the “Select” key results in another screen that either replaces the current screen with an “Add Group Contact” dialog or overlays the current screen such as a pop-up window style. The dialog notifies the user that a new contact is being added to the currently selected group member (which was previously unpopulated in this example). The user interface also permits the user to select “Create new”, “Get from phonebook” or “Back.” Selection of “Back” cancels the “Add Group Contact” dialog box and returns to the idle screen.
[0062] Selection of “Get from phonebook” from the “Add Group Contact” dialog transitions the user interface to a phonebook interface such as from a contact manager type application. A previously entered contact can then be selected from the phonebook using the various keys and/or input devices available in the contact manager. Once the user has selected the contact, the user can either cancel the selection (e.g., selecting “Back”), or select a telephone number (e.g., from a list of available numbers such as a home number, a cell phone number, etc.) for the contact. After the desired phone number is selected, the user can either save the selected contact information (e.g. “Save”) or cancel and return to the prior screen (e.g., “Cancel”). The confirmation dialogs, approval/rejection, and remaining steps in FIG. 6 are substantially the same as that described for FIG. 5 .
[0063] As previously stated, each contact in the user's preferred contact group can have an associated graphical icon for display on the idle screen. FIG. 7 is an illustration of an example user interaction sequence (700) for selection of a picture for a preferred contact. In one example, the interaction of FIG. 7 occurs when the contact is initially selected such as from a contact manager application as previously described. A default picture might already be assigned to the identified contact such as when a photograph is assigned to the contact in a contact manager application. For this example, a dialog screen is displayed requesting approval or rejection of the default picture after the telephone number is selected.
[0064] Approval of the default picture opens a photographic edit tool that includes a crop tool that operates similar to a graphical cursor. The crop tool can be positioned on a desired region of the picture by the user. Optionally, the crop tool can also be configured to zoom in and out of the picture region to provide a desired image size for cropping. Selection of “Crop” will transition the user interface to a “Save” dialog window that permits approval or rejection of the cropped photo. Selection of “Back” aborts the crop tool back to the prior screen, which is the “Use default” picture dialog screen previously described.
[0065] When the default picture is rejected, another dialog screen is displayed that includes various data fields for the user's preferred contact. The user can then press the “Select” key or “Center” key over the picture field to select the photo from a number of sources such as a digital camera interface (e.g., “Take Picture”) that is built into the communication device, a file folder such as “My Photos”, an icon such as “Group Contact Icons”, or some other source such as downloaded icons. Selection of “Take Picture” causes the communication device to activate its facility for taking pictures, followed by cropping the picture, and the various approval and rejection dialogs previously described. Selection of “My Photos” results in activation of a file manager type of tool that permits selection of a photograph from a file folder, activation of the crop tool, and the various approval and rejection dialogs previously described. Selection of “Group Contact Icons” results in activation of a file manager type of tool that permits selection of an icon from a file folder, followed by the various approval and rejection dialogs as previously described. Selection of “Get More Icons” results in the launch of an Internet based browser (e.g., WAP) allowing the user to download more icons.
[0066] It is anticipated that a user may desire to edit the information associated with a member of the user's preferred contact group, or replace the contact with another more desirable contact. FIG. 8 is an illustration of an example interaction sequence (800) for modification of preferred contacts. From the idle screen, the selection key is depressed to recall various options that are available for a previously configured contact in the user's preferred contact group. Selection of the “Options” key permits the user to select any one of “Edit Profile”, “Replace Contact” or “Change Order” for the selected contact. Selection of “Edit Profile” permits the user to change any one of the data fields that are associated with the selected group contact.
[0067] Section of “Replace Contact” causes another dialog series, such as warning messages that a contact cannot be changed until the next billing cycle, or some other dialog such as a screen warning that the contact can only be replaced once a month. This dialog screen can be the result of a check with the network to confirm inability for the user to make the change. An approval/rejection dialog can then be exercised to permit replacing the contact.
[0068] FIG. 9 is an illustration of an example user interaction sequence (900) to change the presentation order of the user's preferred contacts. User interaction associated with the “Change Order” selection from the options screen of FIG. 8 can also described with reference to FIG. 9 . Once the “Change Order” selection is made, the user can utilize the left/right keys or some other set of keys to rotate the currently selected group member though the various ordering positions. In this example, a circular arrangement is used for the group members about a center axis on the screen. Pressing the left key rotates the selected contact in a counter-clockwise manner, while pressing the right key rotates the selected contact in a clockwise manner. Once the desired order position is reached, “Done” can be selected. Alternatively, the user can cancel changing the ordering of the contacts.
[0069] FIG. 10 is an illustration of an example user interface interaction sequence (1000) for changing various settings associated with the preferred contact group centric interface. The interaction begins at the IDLE screen where the user selects “Menu”. A series of icons are presented that represent all of the various menu options, including a settings icon. The settings icon is illustrated by an S, but any graphical and/or text based icon can be utilized as the settings icon. The user navigates the selection cursor to the settings icon and presses “Select” to activate the settings menu, or alternatively presses “Back” to return to the prior screen (the idle screen in this case).
[0070] From the settings menu, a variety of setting parameters are accessible, such as “1. Time & Date”, “2. Display Settings”, “3. Sound Settings”, “4. Group Settings”, “5. Network Services”, and “6. Security”. Selection of the designated number key (4 in this example) or navigating the cursor to the “Group Settings” and pressing the selection button activates the “Group Contacts Settings” menu. A “Back” interaction can also be used to return to the prior screen.
[0071] From the “Group Contact Settings” menu a number of selections are available such as “1. Hide Group”, “2. Refresh Group”, and “3. About Group Contacts”. Selection of “Hide Group” disables the idle screen from showing the preferred group contacts and a dialog screen is displayed that indicates the assignment of various shortcuts and related settings. Once “OK” is selected, the dialog screen is dismissed and the group contacts settings menu toggles “1. Hide Group” to “1. Unhide Group”. Selection of “Refresh Group” sends a message to the server requesting that the preferred group contact settings be updated, resulting in a dialog screen (which can be dismissed with “OK”) that refreshing may take a few minutes. Selection of “About Group Contacts” launches an Internet based site such as a WAP site. From the WAP site, the wireless carrier can provide a number of additional menu selection items, additional information about the current settings, or any other desired interaction.
[0072] The settings menu can also include other settings such as Animation Settings that allow the user the option to choose different ways in which the group contacts are animated. In one example animation setting, the visible contacts on the device's display screen are animated by rotating about a rotational axis when the user changes the currently selected contact. In another example animation setting, the visible contacts on the device's display screen are animated by fade-in and fade-out effects. In still another example animation setting, the visible contacts on the device's display screen are animated by fly-in and fly-out effects. Other effects may also be selected with an animation setting, including disabling the animation effects.
[0073] FIG. 11 is an illustration of an example user interface interaction sequence (1100) that illustrates various calling/communication modes associated with a user's preferred contacts. The interaction begins at the preferred contact group centric interface's idle screen where the user can navigate to a preferred contact, and either press the “Send” key or press the “Select” key for the currently selected preferred contact.
[0074] Selection of the “Send” key (or some other previously assigned key) from the idle screen results in the communication device activating a pre-selected communication mode associated with the currently selected contact. The pre-selected communication mode can be pre-configured for a default communication mode, or user configured. In one example, the pre-selected communication mode for each contact in the group of contacts can be different from one another. In another example, the pre-selected communication mode for each contact in the group of contacts are the same. In one example, the pre-selected communication mode is simply to place a telephone call to a previously designated phone number for the contact, as shown by the “Calling . . . ” dialog screen.
[0075] As depicted in FIG. 11 , a telephone call to a currently selected contact is quickly and easily placed without requiring the user to traverse through additional menu screens. Instead, the currently selected contact (e.g., “Nate”) is selected with a single click user selection. The single click user selection can be effected by any means such as depressing a dedicated selection key (e.g., “talk”), depressing a user configured soft key, or any other user input device such as a touchscreen, touchpad, joypad, joystick, etc. Since the pre-selected communication mode (e.g., “place phone call”) is activated with a single-click on the device, the user interface is very simple and efficient.
[0076] Pressing the “Select” key from the idle screen results in the communication device activating a communication options menu for the currently selected contact. The list of contacts can revert to the original state, for example immediately after the call has ended or the message has been sent or after a brief timeout (e.g., 5 seconds).
[0077] The communication options menu includes a set of choices such as “1. Call”, “2. Send Message”, “3. Share Picture”, “4. Send Voice Note” and “5. Activity Log”, similar to that described for FIG. 2 . The communication options menu permits changing the selected contact with navigation buttons such as left and right without returning to the idle screen, or returning to the idle screen in response to “Back”. Selecting “Call” from this menu places a telephone call in the manner discussed above.
[0078] Selecting “Send Message” from the communication options menu activates a text message interface. The user can enter and send text messages from the messaging interface. The preferred contact group centric interface automatically retrieves address data associated with the currently selected preferred contact such that selection of “OK” or “Options→Send” sends the message without further user interaction.
[0079] Selecting “Share Picture” from the communication options menu activates a picture-sharing interface that includes selections such as “1. Take Picture”, “2. My Photos”, and “3. Group Contact Icons”. Selection of “Take Picture” activates a digital camera interface on the communication device, where digital pictures can be captured by activating the electronic shutter (e.g., “Capture”). Selection of “My Photos” activates a file manager interface on the communication device, where digital pictures can be selected. Once again, the user interface automatically retrieves address data associated with the currently selected preferred contact such that selection of “OK” or “Options→Send” sends the captured or selected photo without further user interaction.
[0080] FIG. 12 is an illustration of an example preferred contact group centric interface interaction sequence (1200) that illustrates additional communication modes associated with a preferred contact. The interaction begins at the communication options menu, which includes a set of choices such as “1. Call”, “2. Send Message”, “3. Share Picture”, “4. Send Voice Note” and “5. Activity Log”, similar to that described previously for FIG. 2 .
[0081] Selecting “Send Voice Note” from the communication options menu activates a voice note interface where a voice message can be recorded by selecting “Record”. The user dictates the voice message to the communication device and presses the “Stop” key to end the recording. As may be desired in any interface, the voice note interface is illustrated with a “Back” key feature that permits returning to a prior screen such as the communication options menu. Similar to that discussed previously, the preferred contact group centric interface automatically retrieves address data associated with the currently selected preferred contact such that selection of “Send” transmits the recorded voice note without further user interaction.
[0082] Selecting “Activity Log” from the communication options menu activates a communications activity log interface that is associated with the selected contact. Communication activities for the selected contact are then displayed on the screen. The activity log can include any number of activities such as, for example, time and date of phone calls, text messages, voice notes, pictures received, etc. The activity log interface is illustrated with a “Back” key feature that permits returning to a prior screen such as the communication options menu. Additional options can also be available from the activity log interface such as “clear history”, as well as others.
[0083] FIG. 13 is an illustration of another example user interface interaction sequence (1300) that illustrates selection of various communication modes associated with a preferred contact. As illustrated in the figure, a preferred contact is initially selected from the idle screen by activating the “Select” key for the currently selected contact. The interaction activates the communication options menu, which includes a set of choices such as “Call”, “Messaging”, “Instant Messaging”, “Email”, etc., similar to that described previously for FIG. 2 .
[0084] An arrangement of graphical icons is used to indicate each of the communication modes that is available for the currently selected contact. The graphical icons are arranged about a central axis relative to the display screen. The user interface in this example is arranged such that selection of the left and right navigation keys will result in rotationally changing the location of each of the graphical icons relative to the central axis. The currently selected communication mode in this example corresponds to the graphical icon that is located in the bottom center location of the display screen. The currently selected graphical icon also includes a text string that is displayed in the bottom center area of the display screen. A selection indicator in this example is illustrated by the box that surrounds the graphical icon and the associated text string.
[0085] As may be desired in any interface, the “Back” key feature can permit the user to dismiss the communication options menu and return to a prior screen such as the idle display screen. Similar to that discussed previously, the preferred contact group centric interface automatically retrieves addressing information for any of the selected communication modes such that activation of a communication mode only requires a single click.
[0086] Although the above-described example communication options menu is arranged in a circular or elliptical arrangement that rotates about a central axis on the screen, other arrangements are also available such as a linear list, a vertical list, a horizontal list, a diagonal list, a circular shape, a semi-circular shape, an elliptical shape, a triangular shape, a diamond shape, a U-shape, an L-shape, a square shape, a quadrilateral shape, a pentagonal shape, a hexagonal shape, another geometric patterned shape, a two-dimensional pattern, and a three-dimensional pattern.
[0087] While the above description of the communication options menu is described with a rotation about the central axis, graphical effects can also be used such as an animation effect, a highlight effect, a fade-in effect, a fade-out effect, a fly-in effect, a fly-out effect, a dissolve-in effect, a dissolve-out effect, a spiral-in effect, a spiral-out effect, a slide-in effect, and a slide-out effect.
[0088] The above-described example is illustrated where the bottom center location of the display screen corresponds to the currently selected communication mode. The present disclosure it not so limited, and any other screen location may also be utilized for the currently selected communication mode. Moreover, the graphical icons can remain stationary in another example, where a graphical indicator of the currently selected communication mode moves about the screen. The graphical indicator can be any desired effect such as a highlight effect, a selection box, an inverse video effect, etc.
[0089] FIG. 14 is an illustration of a preferred contact group centric interface interaction sequence (1400) for creation of a graphical icon for a preferred contact from a downloaded picture. Interaction begins when “download picture” is activated from another menu such as from FIG. 7 , or by some other interaction such as an Internet based download. After the picture is downloaded, a dialog screen is displayed indicating the download is complete. The dialog can be dismissed by selecting “OK” or the downloaded picture can be displayed by selecting “View”. Once the dialog is dismissed or the photo is dismissed similarly with “OK”, a “Set As” menu is displayed.
[0090] The “Set As” menu has a number of available selections such as “1. Wallpaper”, “2. Picture ID”, and “3. Group Contact Icon”. Selection of “Wallpaper” saves the downloaded image as background wallpaper for the communication device. Selection of “Picture ID” saves the downloaded image as a photographic identifier, such as might be used by a contact manager application or perhaps stored in a file folder for other uses.
[0091] Selection of “Group Contact Icon” saves the downloaded image as a preferred contact icon. In some instances, the downloaded picture is not already in appropriate format and the image is cropped with a cropping tool similar to that previously described for FIG. 7 . In other instances, the downloaded picture is already cropped and formatted as a preferred contact icon, and no further cropping and/or formatting is required. A menu is then displayed to assign the formatted icon to one of the contacts in the user's preferred contact group.
[0092] FIG. 15 is an illustration of an example user interface interaction sequence (1500) for an incoming communication notification associated with a contact. The interaction begins from any appropriate screen such as an IDLE screen. When the incoming call is detected, the display screen on the communication device displays indicators for the incoming call such as the telephone number identified by caller ID, the group contact name associated with the incoming call, and a graphical identifier associated with the contact. The user can the select “accept” or “reject” for the incoming call as illustrated.
[0093] FIGS. 16A-16E are illustrations of an example web-based user interface for configuration and management of a preferred contact group user interface. As illustrated in FIG. 16A , a user can navigate a web page to select a preferred contacts group plan from the service provider, learn more about the plan, or view a demonstration of the preferred contacts group user interface. Once the group contact plan has been selected, a user can select management of group contacts through a web page as illustrated by FIG. 16B .
[0094] Selection of “manage group contacts” can be handled by a web-interface such as illustrated in FIG. 16C . Each contact has a designated name and phone number that can be added to the group as illustrated. An attempt to change a contact at a non-permitted time can result in a notification message such as illustrated in FIG. 16C , where group contacts can only be changed once a month. Failure to enter a name, or a duplicate name can result in a notification message to “please enter a name” as illustrated in FIG. 16D . FIG. 16E illustrates another contact management screen for managing group contacts, where web-links are used to edit all contacts, add a new contact, or select an existing contact for further editing.
[0095] FIGS. 17A-17C are illustrations of an example WAP-based user interface for configuration and management of a preferred contact group user interface.
[0096] Initial configuration is illustrated in FIG. 17A , where a manage group contacts welcome screen is initially displayed prior to a user adding any contacts to the preferred contact group. A WAP link is displayed for adding each of the group contact members. A group contact member (e.g., contact slot #1) is selected using navigation keys. Once the desired group contact member is highlighted (e.g., see the dotted box), the user can choose “Select” to traverse to the WAP link for adding a group contact member. A new display screen is then presented where the user can enter a name and telephone number for the selected contact (e.g., contact slot #1), or select “Cancel” Once the user chooses “Done” a confirmation screen can be displayed to permit the user a last chance to confirm the changes to the selected group contact member (e.g. slot #1). The manage group contact screen displays an update notification for the selected contact member slot until the carrier network confirms the updated contact.
[0097] FIG. 17B illustrates an example of user management of icons for group contacts from a WAP-based interface. A user selects to download group contact icons from the WAP-based interface by selecting an appropriate navigation link that can be designated on a WAP page provided by the communications carrier. Alternatively, the user can select a WAP link to download an icon from a WAP based “Manage Group Contacts” web page. Icons can be provided for a service charge or for free as illustrated in the figures. Once downloaded, an icon is available for assignment to any of the preferred group contacts as previously described.
[0098] FIG. 17C illustrates an example of user based editing of group contact icons from a WAP-based interface. A user selects a group contact member from a WAP-link on the “Manage Group Contacts” WAP-based web page using a variety of navigation and selection methods previously described. By selecting the appropriate web-link, the user navigates to an “Edit Group Contact” WAP-based web page. The selected group contact slot may have already been changed once within the prescribed period (e.g., once per month), in which case the user will be able to change the name associated with the contact but not the associated phone number. When the user has not changed to phone number within the prescribed period, the user will be able to update both the phone number and the name associated with the selected contact. Once the user selects “Done” from the web page, the information is updated accordingly on the carrier network as previously described.
[0099] The above specification, examples and data provide a complete description of the manufacture and use of the composition of the embodiments. Although the subject matter has been described in language specific to structural features and/or methods, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features, or specific implementations described above. Many other configurations of computing devices, communications features, applications, and distributed software and/or hardware systems may be employed to implement the described dynamic user interface. The specific features and methods described above are thus disclosed as example forms of implementing the claims and embodiments.
Claims
What is claimed is:
1. A system comprising:
a data store for maintaining a subset of contacts selected at least in part by a user of a communications device, wherein the subset of user contacts includes a portion of a set of contacts accessible by the communications device and wherein the subset of contacts includes a plurality of contacts;
a user interface component, implemented by executing instructions on a processor, the user interface component operative to:
cause the generation of a first display on the communications device without initiating a user contact application for accessing the set of contacts accessible by the communications device, wherein the first display includes a graphical identifier associated with each contact of the subset of contacts;
identify a first message event associated with the user and a first contact from the subset of contacts;
identify a second message event associated with the user and a second contact from the subset of contacts, wherein the second message event corresponds to a different type of message event than the first message event; and
cause the generation of an updated display on the communications device without initiating a user contact application for accessing the set of contacts accessible by the communication device,
wherein the updated display includes the graphical identifiers associated with the subset of contacts presented in the first display; a first message event indicator positioned adjacent to the graphical identifier associated with the first contact from the subset of contacts; and a second message event indicator positioned adjacent to the graphical identifier associated with the second contact from the subset of contacts,
wherein the first message event indicator corresponds to the first message event and the second message event indicator corresponds to the second message event,
wherein the first message event indicator and the second message event indicator are different,
wherein the first display and the updated display are caused to be presented on the communications device in one of a home page screen and an idle screen;
wherein the first and second status events include mood information associated with the first and second contacts respectively; and
wherein the mood information is determined as a function of a frequency of communication between the user and the respective contact.
2. The system as recited in claim 1, wherein each contact in the subset of contacts is selected by the user of the communications device.
3. The system as recited in claim 1, wherein the first message event corresponds to one of a missed call, receipt of an email message, receipt of a text message, receipt of a voice mail message, and receipt of a picture message.
4. The system as recited in claim 3, wherein the second message event corresponds to one of a missed call, receipt of an email message, receipt of a text message, receipt of a voice mail message, and receipt of a picture message.
5. The system as recited in claim 1, wherein the first message event and the first message event indicator correspond to a missed call and wherein the second message event and the second message event indicator correspond to an awaiting email message.
6. A computer-implemented method comprising:
identifying a subset of contacts selected at least in part by a user of a communications device, wherein the subset of user contacts includes a portion of a set of contacts accessible by the communications device and wherein the subset of contacts includes a plurality of contacts;
identifying a graphical identifier corresponding to each user contact from the subset;
identifying a first status event associated with the user and a first contact from the subset of contacts;
identifying a second status event associated with the user and a second contact from the subset of contacts; and
causing the generation of a display on the communications device without requiring user input,
wherein the display includes an arrangement of at least a portion of the graphical identifiers,
wherein the portion of the graphical identifiers includes the graphical identifier corresponding to the first contact from the subset and the graphical identifier corresponding to the second contact from the subset,
wherein the display further includes a first status indicator positioned adjacent to the graphical identifier associated with the first contact and a second status indicator positioned adjacent to the graphical identifier associated with the second contact,
wherein the first status indicator corresponds to the first status event and the second status indicator corresponds to the second status event,
wherein the graphical identifiers associated with the subset of contacts are caused to be presented on the display in response to initiation of at least one of a home screen state and an idle screen state,
wherein the first and second status events correspond to mood information associated with the first and second contacts respectively;
wherein the mood information is determined as a function of a frequency of communication between the user and the respective contact; and
wherein the method is implemented in a computer system.
7. The method as recited in claim 6, wherein each contact in the subset of contacts is selected by the user of the communications device.
8. The method as recited in claim 6, wherein the display includes an arrangement of each of the graphical identifiers corresponding to a user contact from the subset.
9. The method as recited in claim 6, wherein the second status event corresponds to a different type of status event than the first status event.
10. The method as recited in claim 6, wherein the first status indicator and the second status indicator are different.
11. The method as recited in claim 6, wherein causing the generation of the display without user input further comprises causing the generation of the display without causing initiation of a user contact application for accessing the set of contacts accessible by the communications device.
12. The method as recited in claim 6 further comprising:
identifying a third status event associated with the user and a third contact from the subset of contacts.
13. The method as recited in claim 12, wherein the display further includes a third status indicator positioned adjacent to the graphical identifier associated with the third contact and wherein the third status indicator corresponds to the third status event.
14. The method as recited in claim 6, wherein the first status event corresponds to one of a missed call, receipt of an email message, receipt of a text message, receipt of a voice mail message, and receipt of a picture message.
15. The method as recited in claim 14, wherein the second status event corresponds to one of a missed call, receipt of an email message, receipt of a text message, receipt of a voice mail message, and receipt of a picture message.
16. The method as recited in claim 6, wherein the first status event and the first status event indicator correspond to a missed call and wherein the second status event and the second status event indicator correspond to an awaiting email message.
17. The method as recited in claim 6, wherein the first and second status events correspond to presence information associated with the first and second contacts respectively.
18. The method as recited in claim 6, wherein the first and second status events correspond to one of an upcoming date or an appointment associated with the first and second contacts respectively.
19. The method as recited in claim 18, wherein the first and second status event indicators identify one of an upcoming date or an appointment associated with the first and second contacts respectively.
20. The method as recited in claim 6, wherein the mood information is determined as a function of a relative frequency of communication between the user and the respective contact as compared to a frequency of communication between the user and each of the other contacts from the subset.
21. A computer-implemented method comprising:
identifying a subset of contacts, wherein the subset of user contacts includes a portion of a set of contacts accessible by a communications device and wherein the subset of contacts includes a plurality of contacts;
causing the generation of a first display on the communications device without requiring user input when the communications device is in a first state, wherein the first display includes a graphical identifier associated with each contact of the subset of contacts and wherein the graphical identifiers associated with the subset of contacts are caused to be presented on the display in response to initiation of at least one of a home screen state and an idle screen state; and
dynamically causing the generation of an updated display while the communications device is in the first state, wherein the updated display includes the graphical identifiers associated with the subset of contacts presented in the first display, a first status indicator positioned adjacent to the graphical identifier associated with a first contact from the subset of contacts, and a second status indicator positioned adjacent to the graphical identifier associated with a second contact from the subset of contacts, wherein the first status indicator corresponds to a status associated with the first contact and the second status indicator corresponds to a status associated with the second contact,
wherein the first and second status indicators include mood information associated with the first and second contacts respectively,
wherein the mood information is determined as a function of a frequency of communication between the user and the respective contact, and
wherein the method is implemented in a computer system.
22. The method as recited in claim 21, wherein each contact in the subset of contacts is selected by the user of the communications device.
23. The method as recited in claim 21, wherein the first status indicator and the second status indicator are different.
24. The method as recited in claim 23, wherein the first status event indicator corresponds to a missed call indicator and wherein the second status indicator corresponds to an awaiting email message indicator.
25. The method as recited in claim 21, wherein causing the generation of the first display without user input further comprises causing the generation of the first display without causing initiation of a user contact application for accessing the set of contacts accessible by the communications device.
26. The method as recited in claim 21, wherein the updated display further includes a third status indicator positioned adjacent to the graphical identifier associated with a third contact and wherein the third status indicator corresponds to a status associated with the third contact.
27. The method as recited in claim 21, wherein the first status indicator corresponds to one of a missed call indicator, receipt of an email message indicator, receipt of a text message indicator, receipt of a voice mail message indicator, and receipt of a picture message indicator.
28. The method as recited in claim 27, wherein the second status indicator corresponds to one of a missed call indicator, receipt of an email message indicator, receipt of a text message indicator, receipt of a voice mail message indicator, and receipt of a picture message indicator.
29. The method as recited in claim 21, wherein the first and second status indicators correspond to presence indicators associated with the first and second contacts respectively.
30. The method as recited in claim 21, wherein the first and second status indicators correspond to one of an upcoming date indicator or an appointment indicator associated with the first and second contacts respectively.
31. A computer-implemented method comprising:
identifying a subset of contacts selected at least in part by a user of a communications device, wherein the subset of user contacts includes a portion of a set of contacts accessible by the communications device and wherein the subset of contacts includes a plurality of contacts;
identifying a graphical identifier corresponding to each user contact from the subset;
identifying a first status event associated with the user and a first contact from the subset of contacts;
identifying a second status event associated with the user and a second contact from the subset of contacts;
causing the generation of a display on the communications device without requiring user input, wherein the display includes an arrangement of at least a portion of the graphical identifiers, wherein the portion of the graphical identifiers includes the graphical identifier corresponding to the first contact from the subset and the graphical identifier corresponding to the second contact from the subset, wherein the display further includes a first status indicator positioned adjacent to the graphical identifier associated with the first contact and a second status indicator positioned adjacent to the graphical identifier associated with the second contact, wherein the first status indicator corresponds to the first status event and the second status indicator corresponds to the second status event, and wherein the graphical identifiers associated with the subset of contacts are caused to be presented on the display in response to initiation of at least one of a home screen state and an idle screen state; and
causing the generation of a second display on the communications device, the second display comprising a communications option menu including an arrangement of available communication modes associated with a currently selected graphical identifier corresponding to a first contact, wherein the second arrangement of graphical identifiers comprises at least a portion of a set of graphical identifiers indicative of available communication modes, and wherein one of the graphical identifiers indicative of available communication modes corresponds to a currently selected communication mode.
Patent Citations (473)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US4723209(A) | 1988-02-01 | Hernandez et al. | Applicant |
| USD296218(S) | 1988-06-01 | Wells-Papanek et al. | Applicant |
| USD298144(S) | 1988-10-01 | Wells-Papanek et al. | Applicant |
| US5590256(A) | 1996-12-01 | Tchao et al. | Applicant |
| USD384052(S) | 1997-09-01 | Kodosky | Applicant |
| USD388424(S) | 1997-12-01 | DeMuro et al. | Applicant |
| USD391948(S) | 1998-03-01 | Eisenberg | Applicant |
| US5724531(A) | 1998-03-01 | Miyashita et al. | Applicant |
| US5751980(A) | 1998-05-01 | Musashi et al. | Applicant |
| USD395427(S) | 1998-06-01 | Arora et al. | Applicant |
| US5793365(A) | 1998-08-01 | Tang et al. | Applicant |
| US5796394(A) | 1998-08-01 | Wicks et al. | Examiner |
| USD397687(S) | 1998-09-01 | Arora et al. | Applicant |
| USD398595(S) | 1998-09-01 | Baer et al. | Applicant |
| US5822123(A) | 1998-10-01 | Davis et al. | Applicant |
| US5867226(A) | 1999-02-01 | Wehmeyer et al. | Applicant |
| US5880733(A) | 1999-03-01 | Horvitz et al. | Applicant |
| US5889517(A) | 1999-03-01 | Ueda et al. | Applicant |
| USD415483(S) | 1999-10-01 | Decker | Applicant |
| US5987107(A) | 1999-11-01 | Brown | Applicant |
| US5987469(A) | 1999-11-01 | Lewis et al. | Applicant |
| US6006200(A) | 1999-12-01 | Boies et al. | Applicant |
| US6023275(A) | 2000-02-01 | Horvitz et al. | Applicant |
| USD424036(S) | 2000-05-01 | Arora et al. | Applicant |
| USD424541(S) | 2000-05-01 | Mugura | Applicant |
| US6104398(A) | 2000-08-01 | Cox, Jr. et al. | Applicant |
| US6130726(A) | 2000-10-01 | Darbee et al. | Applicant |
| US6144863(A) | 2000-11-01 | Charron | Applicant |
| US6151059(A) | 2000-11-01 | Schein et al. | Applicant |
| USD437858(S) | 2001-02-01 | Yasui et al. | Applicant |
| US6188406(B1) | 2001-02-01 | Fong et al. | Applicant |
| USD438873(S) | 2001-03-01 | Wang et al. | Applicant |
| US6201957(B1) | 2001-03-01 | Son et al. | Applicant |
| USD440979(S) | 2001-04-01 | Wang et al. | Applicant |
| US6226367(B1) | 2001-05-01 | Smith et al. | Applicant |
| US6236398(B1) | 2001-05-01 | Kojima et al. | Applicant |
| US6249863(B1) | 2001-06-01 | Redford et al. | Applicant |
| USD445426(S) | 2001-07-01 | Wang et al. | Applicant |
| USD446790(S) | 2001-08-01 | Wang et al. | Applicant |
| US6313877(B1) | 2001-11-01 | Anderson | Applicant |
| US6332024(B1) | 2001-12-01 | Inoue et al. | Applicant |
| USD454138(S) | 2002-03-01 | Imamura et al. | Applicant |
| USD454139(S) | 2002-03-01 | Feldcamp | Applicant |
| US6359635(B1) | 2002-03-01 | Perttunen | Applicant |
| US6393430(B1) | 2002-05-01 | Van Ryzin | Applicant |
| USD459361(S) | 2002-06-01 | Inagaki | Applicant |
| USD463444(S) | 2002-09-01 | Istvan et al. | Applicant |
| US6460181(B1) | 2002-10-01 | Donnelly | Applicant |
| US6486870(B1) | 2002-11-01 | Kozu | Applicant |
| USD467252(S) | 2002-12-01 | Lee | Applicant |
| USD469442(S) | 2003-01-01 | Bohlen, Jr. et al. | Applicant |
| USD470857(S) | 2003-02-01 | Anderson et al. | Applicant |
| USD471226(S) | 2003-03-01 | Gray | Applicant |
| US6532459(B1) | 2003-03-01 | Berson | Applicant |
| US6538635(B1) | 2003-03-01 | Ringot | Applicant |
| USD472902(S) | 2003-04-01 | Nashida et al. | Applicant |
| USD473236(S) | 2003-04-01 | Robbin et al. | Applicant |
| USD474198(S) | 2003-05-01 | Barnes | Applicant |
| USD474778(S) | 2003-05-01 | Barnes | Applicant |
| USD475064(S) | 2003-05-01 | Nashida et al. | Applicant |
| US6563515(B1) | 2003-05-01 | Reynolds et al. | Applicant |
| US6577330(B1) | 2003-06-01 | Tsuda et al. | Applicant |
| US6600936(B1) | 2003-07-01 | Karkkainen et al. | Applicant |
| USD478912(S) | 2003-08-01 | Johnson | Applicant |
| USD485279(S) | 2004-01-01 | DeCombe | Applicant |
| US6678891(B1) | 2004-01-01 | Wilcox et al. | Applicant |
| USD486499(S) | 2004-02-01 | Hayashi et al. | Applicant |
| US6741268(B1) | 2004-05-01 | Hayakawa | Applicant |
| US6757365(B1) | 2004-06-01 | Bogard | Applicant |
| USD495339(S) | 2004-08-01 | Gildred | Applicant |
| US6775659(B2) | 2004-08-01 | Clifton-Bligh | Applicant |
| US6781575(B1) | 2004-08-01 | Hawkins et al. | Examiner |
| USD495715(S) | 2004-09-01 | Gildred | Applicant |
| US6788987(B2) | 2004-09-01 | Slechta et al. | Applicant |
| US6801849(B2) | 2004-10-01 | Szukala et al. | Applicant |
| US6845153(B2) | 2005-01-01 | Tiburtius et al. | Applicant |
| US6850255(B2) | 2005-02-01 | Muschetto | Applicant |
| US6865404(B1) | 2005-03-01 | Tikkala et al. | Applicant |
| USD506474(S) | 2005-06-01 | Gildred | Applicant |
| US6907575(B2) | 2005-06-01 | Duarte | Applicant |
| USD507577(S) | 2005-07-01 | Totten et al. | Applicant |
| US6925650(B1) | 2005-08-01 | Arsenault et al. | Applicant |
| USD510581(S) | 2005-10-01 | Robbin et al. | Applicant |
| US6959207(B2) | 2005-10-01 | Keinonen et al. | Applicant |
| US6975712(B1) | 2005-12-01 | Schnarel et al. | Applicant |
| US6978473(B1) | 2005-12-01 | Nsonwu et al. | Applicant |
| US7007239(B1) | 2006-02-01 | Hawkins et al. | Examiner |
| US7036091(B1) | 2006-04-01 | Nguyen et al. | Applicant |
| US7046993(B2) | 2006-05-01 | Haaramo et al. | Applicant |
| USD523439(S) | 2006-06-01 | Kuroda | Applicant |
| USD523440(S) | 2006-06-01 | Hernandez et al. | Applicant |
| USD523868(S) | 2006-06-01 | Kuroda | Applicant |
| US7083109(B2) | 2006-08-01 | Pouchak | Applicant |
| US7086008(B2) | 2006-08-01 | Capps et al. | Applicant |
| US7089287(B2) | 2006-08-01 | Bellotti et al. | Applicant |
| US7099862(B2) | 2006-08-01 | Fitzpatrick et al. | Applicant |
| USD528556(S) | 2006-09-01 | Decombe | Applicant |
| US7111788(B2) | 2006-09-01 | Reponen | Applicant |
| US7117445(B2) | 2006-10-01 | Berger | Applicant |
| US7137073(B2) | 2006-11-01 | Kim et al. | Applicant |
| US7174516(B2) | 2007-02-01 | Chipchase | Examiner |
| US7178109(B2) | 2007-02-01 | Hewson et al. | Applicant |
| US7187761(B2) | 2007-03-01 | Bookstaff | Applicant |
| USD540340(S) | 2007-04-01 | Cummins | Applicant |
| USD543986(S) | 2007-06-01 | Rimas-Ribikauskas et al. | Applicant |
| USD543987(S) | 2007-06-01 | Rimas-Ribikauskas et al. | Applicant |
| USD543992(S) | 2007-06-01 | Vigesaa | Applicant |
| USD544875(S) | 2007-06-01 | Wang et al. | Applicant |
| USD544877(S) | 2007-06-01 | Sasser | Applicant |
| USD545324(S) | 2007-06-01 | Decombe | Applicant |
| US7231229(B1) | 2007-06-01 | Hawkins et al. | Applicant |
| US7236576(B2) | 2007-06-01 | Schnarel et al. | Applicant |
| US7236780(B2) | 2007-06-01 | Benco et al. | Applicant |
| USD545827(S) | 2007-07-01 | Evans et al. | Applicant |
| USD545832(S) | 2007-07-01 | Armendariz | Applicant |
| USD546342(S) | 2007-07-01 | Armendariz | Applicant |
| USD547321(S) | 2007-07-01 | Viegers et al. | Applicant |
| US7248677(B2) | 2007-07-01 | Randall et al. | Applicant |
| US7248857(B1) | 2007-07-01 | Richardson et al. | Applicant |
| USD548239(S) | 2007-08-01 | Rimas-Ribikauskas et al. | Applicant |
| USD548743(S) | 2007-08-01 | Takahashi et al. | Applicant |
| USD550681(S) | 2007-09-01 | Totten et al. | Applicant |
| USD551252(S) | 2007-09-01 | Andre et al. | Applicant |
| USD552114(S) | 2007-10-01 | Tolle et al. | Applicant |
| USD554142(S) | 2007-10-01 | Cameron | Applicant |
| US7280652(B2) | 2007-10-01 | Bocking et al. | Applicant |
| USD554652(S) | 2007-11-01 | Shen et al. | Applicant |
| USD556765(S) | 2007-12-01 | Evans et al. | Applicant |
| USD557268(S) | 2007-12-01 | Fletcher | Applicant |
| USD558221(S) | 2007-12-01 | Nagata et al. | Applicant |
| USD562343(S) | 2008-02-01 | Fletcher | Applicant |
| US7330845(B2) | 2008-02-01 | Lee et al. | Applicant |
| USD563972(S) | 2008-03-01 | Sherry | Applicant |
| US7343565(B2) | 2008-03-01 | Ying et al. | Applicant |
| USD565586(S) | 2008-04-01 | Shin et al. | Applicant |
| USD565627(S) | 2008-04-01 | Kase | Applicant |
| USD567251(S) | 2008-04-01 | Sadler | Applicant |
| USD567817(S) | 2008-04-01 | Kwag et al. | Applicant |
| US7360174(B2) | 2008-04-01 | Grossman et al. | Applicant |
| USD568334(S) | 2008-05-01 | Okaro et al. | Applicant |
| USD568897(S) | 2008-05-01 | Byeon | Applicant |
| USD568898(S) | 2008-05-01 | Byeon | Applicant |
| USD568899(S) | 2008-05-01 | Byeon | Applicant |
| USD569387(S) | 2008-05-01 | Byeon | Applicant |
| US7369850(B2) | 2008-05-01 | Andrew et al. | Applicant |
| USD570369(S) | 2008-06-01 | Fletcher | Applicant |
| USD571819(S) | 2008-06-01 | Scott et al. | Applicant |
| USD573601(S) | 2008-07-01 | Gregov et al. | Applicant |
| USD574392(S) | 2008-08-01 | Kwag et al. | Applicant |
| USD575297(S) | 2008-08-01 | Glezer et al. | Applicant |
| USD575298(S) | 2008-08-01 | Chen et al. | Applicant |
| USD575792(S) | 2008-08-01 | Benson | Applicant |
| USD576174(S) | 2008-09-01 | Ording et al. | Applicant |
| USD577364(S) | 2008-09-01 | Flynt et al. | Applicant |
| USD578134(S) | 2008-10-01 | Jasinski | Applicant |
| USD578543(S) | 2008-10-01 | Ulm et al. | Applicant |
| US7437005(B2) | 2008-10-01 | Drucker et al. | Applicant |
| USD580450(S) | 2008-11-01 | Chen et al. | Applicant |
| USD580946(S) | 2008-11-01 | Chen et al. | Applicant |
| US7450927(B1) | 2008-11-01 | Creswell et al. | Applicant |
| USD582426(S) | 2008-12-01 | Chen et al. | Applicant |
| USD582928(S) | 2008-12-01 | Blankenship et al. | Applicant |
| USD583823(S) | 2008-12-01 | Chen et al. | Applicant |
| USD584737(S) | 2009-01-01 | Stone et al. | Applicant |
| USD585453(S) | 2009-01-01 | Chen et al. | Applicant |
| USD585454(S) | 2009-01-01 | Ismail | Applicant |
| USD586361(S) | 2009-02-01 | Horowitz et al. | Applicant |
| USD586362(S) | 2009-02-01 | Horowitz et al. | Applicant |
| US7490295(B2) | 2009-02-01 | Chaudhri et al. | Applicant |
| USD588148(S) | 2009-03-01 | Stone et al. | Applicant |
| USD588149(S) | 2009-03-01 | Brownell et al. | Applicant |
| USD588150(S) | 2009-03-01 | Stone et al. | Applicant |
| US7503014(B2) | 2009-03-01 | Tojo et al. | Applicant |
| USD589970(S) | 2009-04-01 | Bhat et al. | Applicant |
| USD590407(S) | 2009-04-01 | Watanabe et al. | Applicant |
| USD590412(S) | 2009-04-01 | Saft et al. | Applicant |
| US7519912(B2) | 2009-04-01 | Moody et al. | Applicant |
| US7526306(B2) | 2009-04-01 | Brems et al. | Applicant |
| USD592218(S) | 2009-05-01 | Blankenship et al. | Applicant |
| USD592674(S) | 2009-05-01 | Kwag | Applicant |
| USD593120(S) | 2009-05-01 | Bouchard et al. | Applicant |
| US7536654(B2) | 2009-05-01 | Anthony et al. | Applicant |
| USD593574(S) | 2009-06-01 | Guimaraes et al. | Applicant |
| USD593576(S) | 2009-06-01 | Ball et al. | Applicant |
| USD594015(S) | 2009-06-01 | Singh et al. | Applicant |
| USD594465(S) | 2009-06-01 | Hong et al. | Applicant |
| USD594872(S) | 2009-06-01 | Akimoto | Applicant |
| US7543245(B2) | 2009-06-01 | Irimajiri | Applicant |
| US7546543(B2) | 2009-06-01 | Louch et al. | Applicant |
| US7555727(B2) | 2009-06-01 | Hawkins et al. | Examiner |
| USD596192(S) | 2009-07-01 | Shotel | Applicant |
| US7562304(B2) | 2009-07-01 | Dixon et al. | Applicant |
| US7577700(B2) | 2009-08-01 | Tolson et al. | Applicant |
| USD599368(S) | 2009-09-01 | Kanga et al. | Applicant |
| USD599806(S) | 2009-09-01 | Brown et al. | Applicant |
| USD599807(S) | 2009-09-01 | Marashi | Applicant |
| USD599810(S) | 2009-09-01 | Scalisi et al. | Applicant |
| USD599811(S) | 2009-09-01 | Watanabe et al. | Applicant |
| USD599812(S) | 2009-09-01 | Hirsch | Applicant |
| USD599813(S) | 2009-09-01 | Hirsch | Applicant |
| USD599814(S) | 2009-09-01 | Ogura et al. | Applicant |
| USD601153(S) | 2009-09-01 | Setiawan et al. | Applicant |
| US7587215(B2) | 2009-09-01 | Chakraborty et al. | Applicant |
| US7587683(B2) | 2009-09-01 | Ito et al. | Applicant |
| USD602038(S) | 2009-10-01 | Channell et al. | Applicant |
| US7603628(B2) | 2009-10-01 | Park et al. | Applicant |
| USD603415(S) | 2009-11-01 | Lin et al. | Applicant |
| USD603416(S) | 2009-11-01 | Poling et al. | Applicant |
| USD603418(S) | 2009-11-01 | Magnani et al. | Applicant |
| USD603420(S) | 2009-11-01 | Channell | Applicant |
| USD603867(S) | 2009-11-01 | La et al. | Applicant |
| USD604310(S) | 2009-11-01 | Ahn | Applicant |
| USD604316(S) | 2009-11-01 | Hoefnagels et al. | Applicant |
| USD604317(S) | 2009-11-01 | Hoefnagels et al. | Applicant |
| USD604740(S) | 2009-11-01 | Matheny et al. | Applicant |
| US7620996(B2) | 2009-11-01 | Torres et al. | Applicant |
| USD605200(S) | 2009-12-01 | Sakai | Applicant |
| USD605652(S) | 2009-12-01 | Plaisted et al. | Applicant |
| USD605653(S) | 2009-12-01 | Danton | Applicant |
| USD606088(S) | 2009-12-01 | Yokouchi et al. | Applicant |
| USD606550(S) | 2009-12-01 | La et al. | Applicant |
| USD607002(S) | 2009-12-01 | Jonasson et al. | Applicant |
| US7636889(B2) | 2009-12-01 | Weber et al. | Applicant |
| USD608364(S) | 2010-01-01 | Walsh et al. | Applicant |
| USD608366(S) | 2010-01-01 | Matas | Applicant |
| USD608367(S) | 2010-01-01 | Scalisi et al. | Applicant |
| USD608368(S) | 2010-01-01 | Bamford | Applicant |
| US7646745(B2) | 2010-01-01 | Caldwell et al. | Applicant |
| US7650361(B1) | 2010-01-01 | Wong et al. | Applicant |
| USD609714(S) | 2010-02-01 | Oda et al. | Applicant |
| USD609715(S) | 2010-02-01 | Chaudhri | Applicant |
| USD610159(S) | 2010-02-01 | Matheny et al. | Applicant |
| USD610161(S) | 2010-02-01 | Matas | Applicant |
| US7665028(B2) | 2010-02-01 | Cummins et al. | Applicant |
| US7665033(B2) | 2010-02-01 | Byrne et al. | Applicant |
| USD611056(S) | 2010-03-01 | Langlois et al. | Applicant |
| USD611484(S) | 2010-03-01 | Mays et al. | Applicant |
| USD611485(S) | 2010-03-01 | Marashi | Applicant |
| USD611489(S) | 2010-03-01 | Bell et al. | Applicant |
| USD611490(S) | 2010-03-01 | Lee et al. | Applicant |
| USD612394(S) | 2010-03-01 | La et al. | Applicant |
| USD612860(S) | 2010-03-01 | Tarara et al. | Applicant |
| US7673017(B2) | 2010-03-01 | Kim et al. | Applicant |
| US7685520(B2) | 2010-03-01 | Rashkovskiy et al. | Applicant |
| US7685530(B2) | 2010-03-01 | Sherrard et al. | Applicant |
| USD613300(S) | 2010-04-01 | Chaudhri | Applicant |
| USD613747(S) | 2010-04-01 | Jonasson et al. | Applicant |
| USD614191(S) | 2010-04-01 | Takano et al. | Applicant |
| USD614192(S) | 2010-04-01 | Takano et al. | Applicant |
| USD614633(S) | 2010-04-01 | Watanabe et al. | Applicant |
| USD614643(S) | 2010-04-01 | Viegers et al. | Applicant |
| USD614646(S) | 2010-04-01 | Chen et al. | Applicant |
| US7702543(B2) | 2010-04-01 | MacKay et al. | Applicant |
| US7703031(B2) | 2010-04-01 | Nakagawa et al. | Applicant |
| US7705833(B2) | 2010-04-01 | Kim | Applicant |
| USD615090(S) | 2010-05-01 | Sogabe | Applicant |
| USD615546(S) | 2010-05-01 | Lundy et al. | Applicant |
| USD615549(S) | 2010-05-01 | Caine et al. | Applicant |
| US7720498(B2) | 2010-05-01 | Lee | Applicant |
| USD617804(S) | 2010-06-01 | Hirsch | Applicant |
| USD617805(S) | 2010-06-01 | Scalisi et al. | Applicant |
| USD618250(S) | 2010-06-01 | Stallings et al. | Applicant |
| US7735021(B2) | 2010-06-01 | Padawer et al. | Examiner |
| US7738912(B1) | 2010-06-01 | Hawkins et al. | Applicant |
| USD619593(S) | 2010-07-01 | Fujioka et al. | Applicant |
| USD619594(S) | 2010-07-01 | Jonasson et al. | Applicant |
| USD620948(S) | 2010-08-01 | Scalisi et al. | Applicant |
| USD621844(S) | 2010-08-01 | Van Os | Applicant |
| USD621845(S) | 2010-08-01 | Anzures et al. | Applicant |
| USD622280(S) | 2010-08-01 | Tarara | Applicant |
| US7779358(B1) | 2010-08-01 | Gupta et al. | Applicant |
| USD624556(S) | 2010-09-01 | Chaudhri | Applicant |
| US7797641(B2) | 2010-09-01 | Karukka et al. | Applicant |
| USD625325(S) | 2010-10-01 | Vu et al. | Applicant |
| USD626136(S) | 2010-10-01 | Fujimura | Applicant |
| USD627790(S) | 2010-11-01 | Chaudhri | Applicant |
| USD628206(S) | 2010-11-01 | Lemay | Applicant |
| US7898600(B2) | 2011-03-01 | Lee et al. | Applicant |
| USD638025(S) | 2011-05-01 | Saft et al. | Applicant |
| US7971222(B2) | 2011-06-01 | Ellis | Applicant |
| US8015187(B2) | 2011-09-01 | Choi et al. | Applicant |
| US8046801(B2) | 2011-10-01 | Ellis et al. | Applicant |
| USD652843(S) | 2012-01-01 | van Os | Applicant |
| US2001/0044743(A1) | 2001-11-01 | McKinley et al. | Applicant |
| US2001/0046886(A1) | 2001-11-01 | Ishigaki | Applicant |
| US2002/0045960(A1) | 2002-04-01 | Phillips et al. | Applicant |
| US2002/0052754(A1) | 2002-05-01 | Joyce et al. | Applicant |
| US2002/0054164(A1) | 2002-05-01 | Uemura | Applicant |
| US2002/0059201(A1) | 2002-05-01 | Work | Applicant |
| US2002/0145623(A1) | 2002-10-01 | Decombe | Applicant |
| US2003/0014179(A1) | 2003-01-01 | Szukala et al. | Applicant |
| US2003/0078033(A1) | 2003-04-01 | Sauer et al. | Applicant |
| US2003/0164818(A1) | 2003-09-01 | Miller-Smith et al. | Applicant |
| US2003/0210265(A1) | 2003-11-01 | Haimberg | Examiner |
| US2003/0224816(A1) | 2003-12-01 | Kundaje et al. | Applicant |
| US2003/0225879(A1) | 2003-12-01 | Chipchase | Applicant |
| US2004/0017376(A1) | 2004-01-01 | Tagliabue et al. | Applicant |
| US2004/0041836(A1) | 2004-03-01 | Zaner et al. | Examiner |
| US2004/0046796(A1) | 2004-03-01 | Fujita | Applicant |
| US2004/0067751(A1) | 2004-04-01 | Vandermeijden | Applicant |
| US2004/0075691(A1) | 2004-04-01 | Moon | Examiner |
| US2004/0077340(A1) | 2004-04-01 | Forsyth | Applicant |
| US2004/0091093(A1) | 2004-05-01 | Bookstaff | Applicant |
| US2004/0100479(A1) | 2004-05-01 | Nakano et al. | Applicant |
| US2004/0102225(A1) | 2004-05-01 | Furuta et al. | Applicant |
| US2004/0119758(A1) | 2004-06-01 | Grossman et al. | Examiner |
| US2004/0122684(A1) | 2004-06-01 | Kaikuranta | Applicant |
| US2004/0133638(A1) | 2004-07-01 | Doss et al. | Applicant |
| US2004/0155908(A1) | 2004-08-01 | Wagner | Examiner |
| US2004/0162812(A1) | 2004-08-01 | Lane | Applicant |
| US2004/0172455(A1) | 2004-09-01 | Green et al. | Examiner |
| US2004/0185890(A1) | 2004-09-01 | Drozt et al. | Applicant |
| US2004/0221239(A1) | 2004-11-01 | Hachigian et al. | Applicant |
| US2004/0235520(A1) | 2004-11-01 | Cadiz et al. | Applicant |
| US2004/0237048(A1) | 2004-11-01 | Tojo et al. | Applicant |
| US2004/0239982(A1) | 2004-12-01 | Gignac | Applicant |
| US2004/0250217(A1) | 2004-12-01 | Tojo et al. | Applicant |
| US2004/0268228(A1) | 2004-12-01 | Croney et al. | Applicant |
| US2004/0268265(A1) | 2004-12-01 | Berger | Examiner |
| US2005/0005235(A1) | 2005-01-01 | Satterfield et al. | Applicant |
| US2005/0010876(A1) | 2005-01-01 | Robertson et al. | Applicant |
| US2005/0020243(A1) | 2005-01-01 | Benco et al. | Applicant |
| US2005/0033603(A1) | 2005-02-01 | Suzuki et al. | Applicant |
| US2005/0033698(A1) | 2005-02-01 | Chapman | Applicant |
| US2005/0039140(A1) | 2005-02-01 | Chen | Applicant |
| US2005/0041011(A1) | 2005-02-01 | Silfverberg et al. | Applicant |
| US2005/0071780(A1) | 2005-03-01 | Muller et al. | Applicant |
| US2005/0079863(A1) | 2005-04-01 | Macaluso | Applicant |
| US2005/0086611(A1) | 2005-04-01 | Takabe et al. | Applicant |
| US2005/0091272(A1) | 2005-04-01 | Smith et al. | Applicant |
| US2005/0094205(A1) | 2005-05-01 | Lo et al. | Applicant |
| US2005/0114374(A1) | 2005-05-01 | Juszkiewicz et al. | Applicant |
| US2005/0118996(A1) | 2005-06-01 | Lee et al. | Applicant |
| US2005/0120306(A1) | 2005-06-01 | Klassen et al. | Examiner |
| US2005/0143135(A1) | 2005-06-01 | Brems et al. | Applicant |
| US2005/0143138(A1) | 2005-06-01 | Lee et al. | Applicant |
| US2005/0160376(A1) | 2005-07-01 | Sciammarella et al. | Applicant |
| US2005/0163290(A1) | 2005-07-01 | Gilles et al. | Applicant |
| US2005/0172001(A1) | 2005-08-01 | Zaner et al. | Applicant |
| US2005/0182837(A1) | 2005-08-01 | Harris et al. | Applicant |
| US2005/0209994(A1) | 2005-09-01 | Noro et al. | Applicant |
| US2005/0210104(A1) | 2005-09-01 | Torvinen | Applicant |
| US2005/0229110(A1) | 2005-10-01 | Gegner et al. | Applicant |
| US2005/0235225(A1) | 2005-10-01 | Pradhan et al. | Applicant |
| US2005/0235226(A1) | 2005-10-01 | Watanabe et al. | Applicant |
| US2005/0235251(A1) | 2005-10-01 | Arend et al. | Applicant |
| US2005/0243979(A1) | 2005-11-01 | Starbuck et al. | Applicant |
| US2005/0245236(A1) | 2005-11-01 | Servi et al. | Applicant |
| US2005/0246654(A1) | 2005-11-01 | Hally et al. | Applicant |
| US2005/0261011(A1) | 2005-11-01 | Scott | Applicant |
| US2005/0278652(A1) | 2005-12-01 | Scholz | Applicant |
| US2006/0009249(A1) | 2006-01-01 | Fu et al. | Applicant |
| US2006/0030347(A1) | 2006-02-01 | Biswaas | Applicant |
| US2006/0048076(A1) | 2006-03-01 | Vronay et al. | Applicant |
| US2006/0053379(A1) | 2006-03-01 | Henderson et al. | Applicant |
| US2006/0055700(A1) | 2006-03-01 | Niles et al. | Applicant |
| US2006/0084410(A1) | 2006-04-01 | Sutaria et al. | Applicant |
| US2006/0101350(A1) | 2006-05-01 | Scott | Examiner |
| US2006/0112354(A1) | 2006-05-01 | Park et al. | Applicant |
| US2006/0123360(A1) | 2006-06-01 | Anwar et al. | Applicant |
| US2006/0140015(A1) | 2006-06-01 | Kasamsetty | Applicant |
| US2006/0141996(A1) | 2006-06-01 | Huh | Applicant |
| US2006/0143574(A1) | 2006-06-01 | Ito et al. | Applicant |
| US2006/0146765(A1) | 2006-07-01 | Van De Sluis et al. | Applicant |
| US2006/0148499(A1) | 2006-07-01 | Chie | Applicant |
| US2006/0168539(A1) | 2006-07-01 | Hawkins et al. | Applicant |
| US2006/0174121(A1) | 2006-08-01 | Omae et al. | Applicant |
| US2006/0212829(A1) | 2006-09-01 | Yahiro et al. | Applicant |
| US2006/0242597(A1) | 2006-10-01 | Park | Applicant |
| US2006/0253787(A1) | 2006-11-01 | Fogg | Examiner |
| US2006/0277488(A1) | 2006-12-01 | Cok et al. | Applicant |
| US2006/0293057(A1) | 2006-12-01 | Mazerski et al. | Applicant |
| US2007/0011617(A1) | 2007-01-01 | Akagawa et al. | Applicant |
| US2007/0027920(A1) | 2007-02-01 | Alvarado et al. | Applicant |
| US2007/0032267(A1) | 2007-02-01 | Haitani et al. | Applicant |
| US2007/0033540(A1) | 2007-02-01 | Bridges et al. | Applicant |
| US2007/0043688(A1) | 2007-02-01 | Kountz et al. | Applicant |
| US2007/0060206(A1) | 2007-03-01 | Dam Nielsen et al. | Examiner |
| US2007/0067738(A1) | 2007-03-01 | Flynt et al. | Applicant |
| US2007/0073874(A1) | 2007-03-01 | Moghaddam et al. | Applicant |
| US2007/0079246(A1) | 2007-04-01 | Morillon et al. | Applicant |
| US2007/0118813(A1) | 2007-05-01 | Forstall et al. | Applicant |
| US2007/0129112(A1) | 2007-06-01 | Tarn | Applicant |
| US2007/0135103(A1) | 2007-06-01 | Middleton | Applicant |
| US2007/0136687(A1) | 2007-06-01 | Pak | Applicant |
| US2007/0162862(A1) | 2007-07-01 | Ogasawara et al. | Applicant |
| US2007/0168262(A1) | 2007-07-01 | Morotomi et al. | Applicant |
| US2007/0174389(A1) | 2007-07-01 | Armstrong et al. | Applicant |
| US2007/0198947(A1) | 2007-08-01 | Cox et al. | Applicant |
| US2007/0226645(A1) | 2007-09-01 | Kongqiao et al. | Applicant |
| US2007/0250936(A1) | 2007-10-01 | Nakamura et al. | Applicant |
| US2007/0268908(A1) | 2007-11-01 | Linkola et al. | Applicant |
| US2007/0271528(A1) | 2007-11-01 | Park et al. | Applicant |
| US2008/0022228(A1) | 2008-01-01 | Kwon et al. | Applicant |
| US2008/0034317(A1) | 2008-02-01 | Fard et al. | Applicant |
| US2008/0059570(A1) | 2008-03-01 | Bill | Applicant |
| US2008/0081653(A1) | 2008-04-01 | Mock et al. | Applicant |
| US2008/0086703(A1) | 2008-04-01 | Flynt et al. | Applicant |
| US2008/0098311(A1) | 2008-04-01 | Delarue et al. | Applicant |
| US2008/0111826(A1) | 2008-05-01 | Endrikhovski et al. | Applicant |
| US2008/0122870(A1) | 2008-05-01 | Brodersen et al. | Applicant |
| US2008/0158189(A1) | 2008-07-01 | Kim | Applicant |
| US2008/0172030(A1) | 2008-07-01 | Blomquist | Applicant |
| US2008/0189614(A1) | 2008-08-01 | Jeong et al. | Applicant |
| US2008/0189627(A1) | 2008-08-01 | Nikitin et al. | Applicant |
| US2008/0194934(A1) | 2008-08-01 | Ray et al. | Applicant |
| US2008/0215978(A1) | 2008-09-01 | Bamba | Applicant |
| US2008/0220751(A1) | 2008-09-01 | De Bast | Examiner |
| US2008/0220752(A1) | 2008-09-01 | Forstall et al. | Applicant |
| US2008/0235248(A1) | 2008-09-01 | Krantz et al. | Applicant |
| US2008/0256170(A1) | 2008-10-01 | Hayashi et al. | Applicant |
| US2008/0261569(A1) | 2008-10-01 | Britt et al. | Examiner |
| US2008/0263069(A1) | 2008-10-01 | Harris et al. | Applicant |
| US2008/0280600(A1) | 2008-11-01 | Zhou | Applicant |
| US2008/0282158(A1) | 2008-11-01 | Aaltonen et al. | Applicant |
| US2008/0288612(A1) | 2008-11-01 | Kwon | Applicant |
| US2008/0288880(A1) | 2008-11-01 | Reponen et al. | Applicant |
| US2009/0040875(A1) | 2009-02-01 | Buzescu et al. | Applicant |
| US2009/0043847(A1) | 2009-02-01 | Laurila | Applicant |
| US2009/0077496(A1) | 2009-03-01 | Aravamudan et al. | Applicant |
| US2009/0164923(A1) | 2009-06-01 | Ovi | Applicant |
| US2009/0199120(A1) | 2009-08-01 | Baxter et al. | Applicant |
| US2009/0228513(A1) | 2009-09-01 | Tian | Applicant |
| US2009/0300518(A1) | 2009-12-01 | Mock et al. | Applicant |
| US2009/0303188(A1) | 2009-12-01 | Triplett | Applicant |
| US2010/0004008(A1) | 2010-01-01 | Abolrous et al. | Applicant |
| US2010/0020953(A1) | 2010-01-01 | Lidstrom et al. | Applicant |
| US2010/0062753(A1) | 2010-03-01 | Wen et al. | Applicant |
| US2010/0094837(A1) | 2010-04-01 | O'Sullivan et al. | Applicant |
| US2010/0144331(A1) | 2010-06-01 | Koberg et al. | Applicant |
| US2010/0245262(A1) | 2010-09-01 | Vance et al. | Applicant |
| US2010/0287504(A1) | 2010-11-01 | Vance et al. | Applicant |
| US2010/0333029(A1) | 2010-12-01 | Smith et al. | Applicant |
| US2011/0258547(A1) | 2011-10-01 | Symons et al. | Applicant |
| DE10155431 | 2003-06-01 | Applicant | |
| EP767418(A1) | 1997-04-01 | Applicant | |
| EP1246434 | 2002-10-01 | Applicant | |
| EP1469374(A1) | 2004-10-01 | Applicant | |
| EP1482758(A1) | 2004-12-01 | Applicant | |
| EP1571808 | 2005-09-01 | Applicant | |
| EP1608190(A1) | 2005-12-01 | Applicant | |
| JP7-129363 | 1995-05-01 | Applicant | |
| JP8-123658 | 1996-05-01 | Applicant | |
| JP9-083630 | 1997-03-01 | Applicant | |
| JP9-311661 | 1997-12-01 | Applicant | |
| JPH11-088496 | 1999-03-01 | Applicant | |
| JPH11-327741 | 1999-11-01 | Applicant | |
| JP2000-259304 | 2000-09-01 | Applicant | |
| JP2000-348058 | 2000-12-01 | Applicant | |
| JP2002-009899(A) | 2002-01-01 | Applicant | |
| JP2003/198705 | 2003-07-01 | Applicant | |
| JP2004-208217 | 2004-07-01 | Applicant | |
| JP2004-348601 | 2004-12-01 | Applicant | |
| JP2005-072958 | 2005-03-01 | Applicant | |
| JP3834039(B2) | 2006-10-01 | Applicant | |
| KR10-2002-0069964(A) | 2002-09-01 | Applicant | |
| KR10-2004-0024967(A) | 2004-03-01 | Applicant | |
| KR10-2005-0043148(A) | 2005-05-01 | Applicant | |
| KR10-2006-0042808(A) | 2005-05-01 | Applicant | |
| KR10-2007-0029009(A) | 2007-03-01 | Applicant | |
| KR10-2008-0004127(A) | 2008-01-01 | Applicant | |
| KR10-2008-0019614(A) | 2008-03-01 | Applicant | |
| KR10-2008-0079716(A) | 2008-09-01 | Applicant | |
| WO/25501 | 2000-05-01 | Applicant | |
| WO3/044756(A1) | 2003-05-01 | Applicant | |
| WO3/062976(A1) | 2003-07-01 | Applicant | |
| WO2005/045799 | 2005-05-01 | Applicant | |
| WO2005/064441 | 2005-07-01 | Applicant | |
| WO2005/120112(A1) | 2005-12-01 | Applicant | |
| WO2006/016227 | 2006-02-01 | Applicant | |
| WO2006/067567(A1) | 2006-06-01 | Applicant | |
| WO2007/093997(A1) | 2007-08-01 | Applicant | |
| WO2008/030776(A2) | 2008-03-01 | Applicant |
Non-Patent Literature (29)
- International Preliminary Preport on Patentability in application No. PCT/US2010/028960 dated Sep. 27, 2011.Applicant
- International Preliminary Report on Patentability in application No. PCT/2010/028863 mailed Sep. 27, 2011.Applicant
- International Preliminary Report on Patentability in application No. PCT/US/2010/028904 mailed Sep. 27, 2011.Applicant
- International Preliminary Report on Patentability in application No. PCT/US2010/028857 mailed Sep. 27, 2011.Applicant
- International Preliminary Report on Patentability in application No. PCT/US2010/028894 mailed Sep. 27, 2011.Applicant
- International Preliminary Report on Patentability in application No. PCT/US2010/028905 mailed on Sep. 27, 2011.Applicant
- International Preliminary Report on Patentability in application No. PCT/US2010/028947 mailed Sep. 27, 2011.Applicant
- International Preliminary Report on Patentability in application No. PCT/US2010/028954 mailed Sep. 27, 2011.Applicant
- International Search Report (PCT/US2010/028894), Nov. 12, 2010.Applicant
- International Search Report (PCT/US2010/028904), Nov. 8, 2010.Applicant
- International Search Report (PCT/US2010/028905), Nov. 12, 2010.Applicant
- International Search Report (PCT/US2010/028947), Nov. 12, 2010.Applicant
- International Search Report (PCT/US2010/028857), Oct. 11, 2010.Applicant
- International Search Report (PCT/US2010/028863), Oct. 22, 2010.Applicant
- International Search Report (PCT/US2010/028954), Oct. 27, 2010.Applicant
- International Search Report (PCT/US2010/028960), Oct. 26, 2010.Applicant
- Office Action in R.O.C. Application No. 098304597 dated Dec. 15, 2011, in 4 pages.Applicant
- European Search Report (PCT/US2006022645), Sep. 6, 2011.Applicant
- 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.Applicant
- Alltel's ‘My Circle’ Plan Lets Subscribers Adds 10 Numbers for Unlimited Calls, Wireless News, Apr. 23, 2006, pp. 2, Coventry.Applicant
- Cuneo, Alice Z., Alltel Gets Aggressive in Telecom War, Advertising Age, Apr. 24, 2006, vol. 77, Issue 17, pp. 8, 1 pg., Chicago (Midwest region edition).Applicant
- Weisser, Cybele and Farnoosh Torabi. “What do you pay to stay connected?” Money Magazine, Nov. 24, 2003. http://money.cnn.com/2003/11/20/pf/portability—strategy—0312/index.htm.Applicant
- Internation Search Report PCT/US2007070475, Jun. 29, 2011.Applicant
- “Alltel Corp at Lehman Brothers Worldwide Wireless, Wirelein, and Media Conference”. Fair Disclosure Wire. May 22, 2006.Applicant
- “Alltel's free wireless calling plan paying off”, Virgil Larson, Knight Rider Tribune Business News, May 2005, 2 pages.Applicant
- “Alltel to Offer Free-Calling Plan, With Limits”. Ken Belson. New York Times. (Late Edition (East Coast)). New York, N.Y.: Apr. 21, 2006. p. C.9.Applicant
- First Office Action in European Application No. 07812026.8 dated Jul. 17, 2012.Applicant
- Second Office Action in Chinese Application No. 200680020479.9 mailed Mar. 22, 2012.Applicant
- “Alltel to Offer Free-Calling Plan, With Limits”. Ken Belson. New York Times. (Late Edition (East Coast)). New York, NY.: Apr 21, 2006. p. C.9.Applicant