In-call contact information display

IN-CALL CONTACT INFORMATION DISPLAY

Microsoft Corporation C.212426 WO 2010/141495 PCT/US2010/036939

IN-CALL CONTACT INFORMATION DISPLAY

Background [0001] Mobile communications devices, such as wireless phones, have become 5 increasingly commonplace. However, the form factor employed by conventional mobile communications devices is typically limited to promote mobility of the mobile communications device. For example, the mobile communications device may have a relatively limited amount of display urea when compared to a conventional desktop computer. Although mobile communications devices may store a large amount of 10 information, the limited amount of display area can make it difficult and cumbersome for users to access the data. This can lead to frustrating user experiences when using the mobile communications devices.

Summary (0002) This Summary is provided to introduce a selection of concepts in a simplified 15 form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.

[0003| In accordance with one or more aspects, call control information regarding a phone call that a user of a mobile communications device is currently engaged in with an 20 individual is displayed on a screen. A single user input requesting display of in-call contact information is received, and in response to the single user input this in-call contact information regarding the individual is displayed.

[0004] In accordance with one or more aspects, a request to display in-call contact information regarding an individual that is currently engaged in a phone call with a mobile 25 communications device is received. In response to the request, the in-call contact information is obtained. This in-call contact information is displayed by the mobile communications device, and includes information obtained by the mobile communications device from a social networking service.

Brief Description of the Drawings 30 [0005[ The same numbers are used throughout the drawings to reference like features.

[0006] Fig. 1 illustrates an example system implementing the in-call contact information display in accordance with one or more embodiments.

[0007] Fig. 2 illustrates an example call control panel in accordance with one or more embodiments. 1 WO 2010/141495 PCT/US2010/036939 [0008] Fig. 3 illustrates an example in-call contact information panel in accordance with one or more embodiments.

[0009J Fig. 4 illustrates another example in-call contact information panel in accordance with one or more embodiments. 5 [0010] Fig. 5 illustrates additional example panels in accordance with one or more embodiments.

[001L| Fig. 6 illustrates additional example panels in accordance with one or more embodiments.

[0012] Fig. 7 is a flowchart illustrating an example process for a device implementing 10 the in-call contact information display in accordance with one or more embodiments.

[00131 Fig. 8 is a flowchart illustrating an example process for a device implementing the ίη-call contact information display in accordance with one or more embodiments.

[00141 Fig. 9 illustrates an example computing device that can be configured to implement the in-call contact information display in accordance with one or more 15 embodiments.

Detailed Description [00151 In-call contact information display is discussed herein. A user of a mobile communications device can use the device to participate in phone calls with one or more other individuals using other devices. During such phone calls, a contact information 20 display panel can be displayed to the user. The contact information display panel can be easily accessed by the user, such as in response to a single user input or action. The contact information display panel displays various information regarding the other individual that is part of the phone call. This information can include various data obtained regarding the other individual from a social networking service. 25 [0016] Fig. 1 illustrates an example system 100 implementing the in-call contact information display in accordance with one or more embodiments. System 100 includes a mobile communications device 102 that can communicate with one or more (x) other devices 104(1), ..., 104(x), and with one or more (y) social networking services 106(1), ..., 106(y). A mobile communications device refers to a communications device capable 30 of sending and receiving communications, such as phone calls, text messages, messages including other content types, and so forth. Mobile communications device 102 can be a variety of different types of devices, such as a cellular phone, a satellite phone, other types of wireless phones, a handheld computer, a personal digital assistant (PDA), an audio and/or video playback device, a portable game device, a dedicated messaging device, a 2 WO 2010/141495 PCT/US2010/036939 netbook, and so forth. It is to be appreciated that mobile communications device 102 can include functionality in addition to being able to send and receive communications calls, such as calendar functionality, audio and/or video playback functionality, and so forth. [0017] In one or more embodiments, mobile communications device 102 is a wireless 5 phone. Such a wireless phone can be implemented using a variety of different form factors, such as a “brick” configuration, a “clamshell” configuration, a “slide” configuration, and so forth. 100181 Devices 104 can be, but need not be, mobile communications devices. Devices 104 can be the same type or alternatively different types of devices as mobile 10 communications device 102. 100191 Mobile communications device 102 includes a screen 112, a user interface (LJI) module 114, a local store 116, a user input module 118, and a communication module 120. Each of modules 114, 118, and 120 can be implemented in software, firmware, hardware, or combinations thereof. When implemented in software or firmware, a module includes 15 one or more instructions that are executed by one or more processors or controllers of mobile communications device 102.

[0020) Screen 112 is a display component of mobile communications device 102. Screen 112 can be implemented in a variety of different manners, such as using liquid crystal display (LCD) technology, plasma screen technology, image projection 20 technology, and so forth. Alternatively, rather than including screen 112, mobile communications device 102 can generate one or more signals that are output to other display devices which include screen 112.

[0021] Communication module 120 manages receiving of communications from and sending of communications to devices 104 and social networking services 106. Mobile 25 communications device 102 can communicate with devices 104 using a variety of different technologies and protocols, such as cellular, satellite, and/or other technologies or protocols. The technologies or protocols can include wireless and/or wired technologies and protocols.

[0022] Communication module 120 supports a variety of different types of 30 communications with devices 104. One type of communication supported by communication module 120 is a voice call. This can include voice calls that are initiated by mobile communications device 102 (e.g., outgoing calls), as well as voice calls that are initiated by another device 104 (e.g., incoming calls). Additionally, communication 3 WO 2010/141495 PCT/US2010/036939 module 120 can typically support multiple voice calls concurrently (e.g., three-way calling, multi-party conferencing, call waiting or placing a call on hold, and so forth). [0023] Another type of communication supported by communication module 120 is a message, which refers to text messages or messages with other types of media such as 5 images, video, audio, combinations of types of media, and so forth. In one or more embodiments, messages comply with the Short Message Service (SMS) communication protocol. In one or more other embodiments, messages comply with the Multimedia Messaging Service (MMS) communication protocol. It is to be appreciated that SMS and MMS are only example protocols, and that other communication protocols can 10 alternatively be used. Various other types of communications can also be supported by communication module 120, such as mobile instant messaging, email, and so forth.

[0024] Communication module 120 can communicate with social networking services 106 using a variety of different networks, including the Internet, a local area network (LAN), a public telephone network, an intranet, a cellular or other wireless phone network, 15 other public and/or proprietary networks, combinations thereof, and so forth. Communication module 120 obtains data (also referred to herein as information) regarding various individuals or other entities using social networking services 106, and makes that data available for display on screen 112. It is to be appreciated that an individual can be an agent of or otherwise represent an entity as well, such as an individual representing a 20 business, service, other group, and so forth. Accordingly, the data can be data regarding the particular individual and/or an entity that the particular individual represents. The particular individuals or entities for which data is obtained is based at least in part on individuals with which mobile communications device 102 communicates using voice calls as discussed in more detail below. 25 [0025] In the example system 100, communication module 120 obtains data from social networking services 106 via an intermediary data service 108. Communication module 120 provides an indication to intermediary data service 108 of one or more individuals or other entities for which data is desired. These individuals or other entities can be, for example, individuals in a local address book of device 102 (e.g., stored in local 30 store 116). A user can maintain information regarding individuals as well as other entities (e.g., businesses, services, and other groups) in his or her local address book. Intermediary data service 108 in turn obtains data for the one or more individuals or other entities from one or more social networking services 106 and returns the obtained data to communication module 120. In one or more embodiments, intermediary data service 108 4 WO 2010/141495 PCT/US2III (1/036939 maintains a cache of data obtained from social networking services 106, and in response to a request for data from communication module 120 can return the data from the cache rather than accessing social networking services 106 at the time of the request. Intermediary data service 108 can also optionally communicate with multiple different 5 social networking services 106.

[0026] Communication module 120 can obtain data from intermediary data service 108 in different manners, such as by using a polling technique or a notification technique. Using a polling technique, communication module 120 sends requests for data (e.g., any data that has changed) for the one or more individuals or entities to intermediary data 10 service 108 at regular or irregular intervals. Using a notification technique, communication module 120 registers with intermediary data service 108 to receive notifications of data changes, and service 108 sends such notifications to communication module 120 of such data changes. Similarly, intermediary data service 108 can obtain data from social networking services 106 in different manners, such as by using a polling 15 technique or a notification technique. (0027] Alternatively, communication module 120 can communicate with one or more of social networking services 106 independent of intermediary data service 108. Communication module 120 can obtain data from social networking services 106 in different manners, such as by using a polling technique or a notification technique, 20 analogous to the discussion above regarding obtaining data from intermediary data service 108. The discussions herein referring to obtaining data from social networking services 106 include embodiments in which the data is obtained from services 106 via intermediary data service 108, as well as embodiments in which the data is obtained from services 106 independently of intermediary data service 108. 25 [0028] Local store 116 is one or more computer storage media. Local store 116 can include volatile media (such as random access memory (RAM)) and/or nonvolatile media (such as read only memory (ROM), Flash memory, optical disks, magnetic disks, and so forth). Store 116 can include fixed media (e.g., RAM, ROM, a fixed hard drive, etc.) as well as removable media (e.g., a Flash memory drive, a removable hard drive, an optical 30 disk, and so forth).

[0029[ Various information can be maintained in local store 116. In one or more embodiments, a component or module of mobile communications device 102 (e.g., module 114 or 120) maintains an address book, also referred to as a contacts list. The address book includes various information regarding particular individuals and/or entities 5 WO 2010/141495 PCT/US2010/036939 as desired by a user of device 102. The address book can include, for example, information regarding friends, family, business acquaintances, service providers, businesses, and so forth. A variety of different information can be maintained, such as phone numbers, e-mail addresses, instant messaging addresses, and so forth. 5 [0030( In one or more embodiments, communication module 120 obtains data regarding the individuals or other entities identified in the address book of local store 116 from social networking services 106 as discussed above. This data that is obtained is also stored in local store 116, as part of the address book or alternatively separate from the address book. Accordingly, communication module 120 can maintain current data from 10 social networking services 106 in local store 116. When a change is made to the data on a social networking service 106, that change is obtained by communication module 120 and saved in local store 116. Accordingly, other components are modules of device 102 can access the data in local store 116 in order to obtain current data from social networking services 106. 15 [0031] Alternatively, rather than maintaining information from social networking services 106 in local store 116, such information can be obtained by communication module 120 when desired. For example, when information regarding a particular individual or entity is desired to be displayed on screen 112, that information can be obtained by communication module 120 from intermediary data service 108 or social 20 networking services 106.

[0032] The information regarding individuals or other entities that is stored in local store 116 can include information obtained from social networking services 106 and can optionally include information obtained from other sources. For example, a user of mobile communications device 102 can input information regarding an individual or other entity 25 that is maintained in local store 116. By way of another example, mobile communications device 102 can receive a contact card or electronic business card from another device and store information from that card in local store 116. Accordingly, when the information regarding an individual or other entity stored in local store 116 is subsequently accessed by another component or module of device 102, that information can be information 30 obtained from social networking services 106 and/or other sources.

[0033] A variety of different information regarding an individual or other entity can be maintained in local store 116. In one or more embodiments, individuals and other entities can publish a variety of different information using social networking services 106, and such published information can be obtained and stored in local store 116. Examples of 6 WO 2010/141495 PCT/US2010/036939 such published information include phone numbers (e.g., a mobile phone number, a home phone number, a work phone number, and so forth), c-mail addresses, instant messaging addresses, postal mailing addresses, images or videos, images or videos that both the user of device 102 and the individual or entity are tagged in, a social feed (e.g., indicating a 5 current location of, or activity engaged in by, the individual or other entity), profile details (e.g., an individual's relationship status, birthday, interests or hobbies, and so forth), upcoming meetings or events that both the user of device 102 and individual or entity are to be part of, friends of the individual or entity, and so forth. Additional information that is not published using social networking services 106 can also be obtained from other 10 sources as discussed above and stored in local store 116. Examples of such information include, recent messages that the individual or entity sent to and/or received from the user of device 102, phone numbers or addresses entered by the user of device 102 or obtained from electronic business cards, and so forth.

[0034) Input module 118 receives user inputs from a user of mobile communications 15 device 102. These user inputs indicate particular user requests, such as commands, actions to be carried out, data being input, and so forth. The user input can be provided in a variety of different manners, such as by pressing one or more keys of a keypad or keyboard of device 102, by pressing a particular portion of a touchpad or touchscreen of device 102, by placing a finger of the user’s hand on a surface of the touchscreen and 20 dragging the finger across the surface, and so forth. Touchscreen functionality can be provided using a variety of different technologies, such as through capacitive, surface acoustic wave, resistive, optical, strain gauge, dispersive signals, acoustic pulse, or other touchscreen technologies. The user input can also be provided in other manners, such as via other physical feedback input to the device (e.g., tapping any portion of device 102 or 25 another action that can be recognized by a motion detection component of device 102, such as shaking device 102, rotating device 102, etc.), and so forth.

[0035] Ul module 114 generates, manages, and/or outputs a user interface for display on screen 112. This user interface includes one or more panels that are displayed on screen 112. A panel refers to a collection of information that is displayed. Different 30 panels can display different information and/or can display information that is organized in different manners. A user can navigate through different panels via various user inputs. A variety of different panels can be displayed for a variety of different purposes, such as to allow a user to place and/or answer a phone call, to allow a user to view information regarding another user that is part of the phone call, to allow a user to enter information 7 WO 2010/141495 PCT/US2010/036939 regarding an individual or entity, and so forth. The particular information displayed by Ul module 114 as a particular panel can vary, such us based on the inputs of the user (e.g., as obtained from user input module 118), information regarding a current phone call that the user is participating in (e.g., as obtained from communication module 120), information 5 from local store 116, and so forth.

[0036] The particular panel displayed by Ul module 114 is based at least in part on a phone call that mobile communications device 102 is engaged in at the time of display of the panel. This phone call is between mobile communications device 102 and another device 104. As devices 102 and 104 are typically being used by particular individuals 10 during a phone call, the phone call can also be referred to as being between these individuals or between an individual and a device. When two devices arc engaged in a phone call, a connection between the two devices exists over a network (which can include wired and/or wireless portions). Either device can typically end the phone call, in which case the connection between the two devices ceases. 15 [0037J It should also be noted that a particular individual using a device 104 during a phone call can be an individual associated with that device 104 or alternatively an agent or other representative of an entity associated with that device 104 as discussed above. For example, an entity can be a business or other group. This business or other group can have various information, such as phone numbers and addresses, published on social 20 networking services 106 and obtained by communication module 120. However, when a user of mobile communications device 102 places a phone call to this entity, an individual representing the entity answers the call and engages in the phone call with the user of device 102.

[0038] In one or more embodiments, Ul module 114 can display a call control panel 25 and an in-call contact information panel. Generally, the call control panel displays various information regarding the phone call and optionaliy control requests for the phone call that can be input by the user of device 102. The in-call contact information panel, on the other hand, displays information regarding the individual (or entity that individual represents) with which mobile communications device 102 is currently engaged in the phone call and 30 optionally indications of requests for additional communications with the individual (or entity that individual represents) that can be input by the user. The call control panel and in-call contact information panel can be displayed in situations where device 102 initiates a phone call and/or another device initiates the phone call. 8 WO 2010/141495 PCT/US2010/036939 [0039] During a phone call, Ul module 114 can display one of the call control panel und the in-cull contuct information panel. Accordingly, if display of one of call control panel and the in-call contact information is requested while the other is displayed, the requested panel is displayed in place of the previously displayed panel. Alternatively, 5 both the call control panel and the in-call contact information panel can be displayed concurrently.

[00401 A call control panel displays various call control information regarding a phone call that the mobile communications device is engaged in at the time the call control panel is displayed. This information can include status information regarding the phone and/or 10 the phone call, as well as indications of various control requests that can be made by the user regarding the phone call. For example, the status information can include an identifier of the individual with which mobile communications device 102 is currently engaged in the phone call (or an identifier of an entity represented by the individual with which mobile communications device 102 is currently engaged in the phone call), an 15 indication of whether that individual has been placed on hold, an indication of whether the microphone of device 102 has been muted, a duration of the phone call, an indication of the remaining battery life of device 102, an indication of signal strength for the phone call, and so forth. By way of another example, indications of control requests can include an indication to activate a speaker of device 102, an indication to mute a microphone of 20 device 102, an indication to end the phone call, an indication to put the individual with which mobile communications device 102 is currently engaged in a phone call on hold, an indication to add another individual to the phone call (e.g., to initiate or expand a conference call), and so forth. These various control requests can be input by a user of device 102 using a variety of different user inputs as discussed above. 25 [0041] An in-call contact information panel displays various information regarding the individual (or entity that individual represents) with which mobile communications device 102 is currently engaged in the phone call. This contact information panel is displayed during the call, which is also referred to as displaying the contact information panel incall. A variety of different information can be displayed on the in-call contact information 30 panel, such as any information regarding the individual or entity that is available from local store 116 and/or that can be obtained by communication module 120 from social networking services 106. This information displayed in the in-call contact information panel can also include an indication of the source ofthe information (e.g., an identifier of a particular social networking service 106, an identifier of a user of device 102, etc.), as well 9 WO 2010/141495 PCT/US2010/036939 as a date and/or time when the information was obtained by device 102. Additionally, if mobile communications device 102 is engaged in a phone cull with multiple individuals (e.g., a multi-party conferencing call), then the in-call contact information panel displays information regarding those multiple individuals (or the entities that those multiple 5 individuals represent).

[0042] Mobile communications device 102 can optionally be engaged in multiple different phone calls concurrently, such as when using call waiting, when placing a call on hold, and so forth. When engaged in multiple phone calls concurrently, a separate in-call contact information panel is displayed for each phone call. Only one such in-call contact 10 information panel is displayed at a time, and the user can input requests to transition between the different in-calt contact information panels. Alternatively, two or more such in-call contact information panels can be displayed concurrently. Each such in-call contact information panel displays various information regarding the individual (or entity that that individual represents) or individuals (or entities that the individuals represent) 15 with which mobile communications device 102 is currently engaged in the phone calls. [0043] The call control panel and in-call contact information panel can be displayed by mobile communications device 102 for the duration of the phone call. When the phone call ends, the display of the call control panel and the in-call contact information panel also ceases. Alternatively, the call control panel and/or ίη-call contact information panel 20 can be displayed for an amount of time (e.g., five seconds, ten seconds, thirty seconds, etc.) after the call ends.

[0044] Figs. 2-6 illustrate example panels that can be displayed by a mobile communications device in accordance with one or more embodiments. These panels can be displayed on, for example, screen 112 of Fig. 1. 25 [0045] Fig. 2 illustrates an example call control panel 202 displayed by a mobile communications device in accordance with one or more embodiments. Call control panel 202 includes status information in the form of call connection information 204 identifying an individual (“Sarah”) with which the user of the mobile communications device is engaged in a phone call. Call connection information 204 also indicates a duration ofthc 30 call in a “minutes:seconds” format (“0:01”) or an "hours:minutesseconds" (or "hours:minutes") format if the call is an hour or longer, and an indication of the status of the phone call (“connected to mobile”, indicating that "Sarah" is using her mobile phone or other mobile communications device). 10 WO 2010/141495 PCT/US2010/036939 [0046] Call control panel 202 also includes status information in the form of phone status information 206. Phone status information 206 indicates a current signal strength of the device displaying control panel 202 (in the form of multiple vertical bars), and a current battery life of the device displaying control panel 202 (in the form of a symbol of a 5 battery).

[0047] Call control panel 202 also includes indications 208 of control requests that can be input by the user of the mobile communications device. These control requests include un indication to turn on a speaker (e.g., enable speakerphone functionality), place the phone call on mute, add another caller, placed a phone call on hold, and end the call. A 10 user request to perform one of these control requests can be input by the user in a variety of different manners as discussed above.

[0048] Fig. 3 illustrates an example in-call contact information panel 302 in accordance with one or more embodiments. In-call contact information panel 302 includes status information 304 and contact information 306. In the illustrated example, 15 status information 304 is the same as status information 204 of Fig. 2. Alternatively, status information 304 can include a subset of the information in status information 204, and/or can include other status information not included in status information 204. The panel 302 illustrated in Fig. 3 can be the entire in-call contact information panel, or alternatively a portion ofthe panel, as discussed in more detail below. 20 [0049J Contact information 306 is in-call contact information for the phone call that the mobile communications device is currently engaged in. In the illustrated example, this in-call contact information includes a current status or location of the other individual engaged in the phone call (e.g., that Sarah is currently working on digging a ditch outside in the rain). Optionally, an indication of the date and/or time that this current status or 25 location was obtained, as well as the social networking service from which this current status or location was obtained, can be displayed as part of contact information 306. Additionally, a phone number of the individual with which the mobile communications device is engaged in the phone call is also displayed as part of contact information 306. In the illustrated example, an indication of the type of phone number (e.g., mobile) is also 30 displayed as part of contact information 306. An image recently uploaded to a social networking service by the other individual engaged in the phone call can also be displayed. The image can be displayed as a separate portion of contact information 306, or alternatively can serve as a background image as illustrated in Fig. 3. 11 WO 2010/141495 PCT/US2010/036939 [0050) In one or more embodiments, the user can also input requests for additional communications with the individual via in-call contact information panel 302. The types of these additional communications can vary based on the type of information displayed. For example, a request to send a message to or initiate a phone call with an individual via 5 a particular phone number can be input if the type of information displayed is a phone number. By way of another example, a request to send a message to an individual via a particular address (e.g., e-mail address, instant messaging address, etc.) can be input if the type of infonnation displayed is an address.

[00511 A user can input such a request while in-call contact infonnation panel 302 is 10 displayed in a variety of different manners as discussed above. In response to such an input, the requested action is taken. For example, the device displaying panel 302 can initiate a phone call to a particular phone number, can open a data input screen to allow data to be input that is subsequently sent as a message to the particular phone number or address, and so forth. 15 [0052J In the example of Fig. 3, a text option 312 and a call option 314 are associated with the mobile phone number displayed. Accordingly, a user can input a request to send a text message to the displayed mobile phone number by selecting text option 312 or otherwise inputting a send text message request. Similarly, a user can input a request to initiate a phone call to the displayed mobile phone number by selecting call option 314 or 20 otherwise inputting an initiate call request. It is to be appreciated that, in certain situations certain options need not be made available to the user. For example, if the current phone call was initiated to or from the displayed mobile phone number, then call option 314 need not be displayed (or can be disabled if displayed).

[0053] In one or more embodiments, the mobile communications device displays only 25 one of panels 202 of Fig. 2 and 302 of Fig. 3 at a time. The device can transition between displaying panel 202 and panel 302 in response to a user request. Such a user request can be input in a variety of different manners as discussed above.

[0054] For example, a pan gesture can be used to indicate a request to transition between in-call contact information panel 302 and call control panel 202. The screen on 30 which panels 302 and 202 are displayed includes touchscreen functionality that can be leveraged to detect a gesture input via a user’s finger or other input device (such as a stylus). The pan gesture may involve placing a finger of the user’s hand on a surface of the touchscreen and dragging the finger across the surface. An indication of the correct direction that the user is to drag in order to transition to panel 302 from panel 202 (or to 12 WO 2010/141495 PCT/US2010/036939 transition from panel 202 to panel 302) can be displayed on panel 302 (or panel 202). The user input module 118 of Fig. 1 cun detect this gesture and indicate to Ul module 114 of Fig. 1 to change to displaying the new panel.

[0055] The indication of the correct direction that the user is to drag to transition to 5 panel 302 or to panel 202 can be displayed in a variety of different manners, such as a small portion (e.g., a sliver) of the display indicating what is available in another panel, an icon indicating what is available in another panel, and so forth. For example, a sliver of the display on the right side of call control panel 202 can indicate that the user can input a pan gesture to the right to transition to the in-call contact information panel 302. By way 10 of another example, a sliver of the display on the left side of in-call contact information panel 302 can indicate that the user can input a pan gesture to the left to transition to call control panel 202.

[0056] Alternatively, other techniques can be used for the user to indicate that the device is to transition between in-call contact information panel 302 and call control panel 15 202. For example, when displaying panel 202, an indication of the availability of in-call contact information panel 302 can be displayed, and the user can touch this indication with his or her finger, a stylus, or otherwise input a request to display panel 302. In response to such a request, panel 302 is displayed. Similarly, when displaying panel 302, an indication of the availability of call control panel 202 can be displayed, and the user can 20 touch this indication with his or her finger, a stylus, or otherwise input a request to display panel 202. In response to such a request, panel 202 is displayed.

[0057] A request to transition from call control panel 202 to in-call contact information panel 302 can be input in a variety of different manners as discussed above. In one or more embodiments, this request is a single user input. A single user input refers 25 to a single action by the user. This single action can be a single gesture (e.g., a pan gesture as discussed above) or sequence of gestures, pressing of a single key or key sequence, pressing of a single part of a touchscreen or sequence of parts of a touchscreen, and so forth. In response to this single user input, a transition from call control panel 202 to incall information panel 302 is made. The user need not navigate through multiple different 30 menu options, screen displays, and so forth, inputting a different request at each stage of the navigation. Rather, the in-call contact information panel 302 is available to the user from the call control panel 202 with a single gesture or other input.

[0058] Additionally, depending on the size of the screen of the mobile communications device, the mobile communications device can have additional 13 WO 2010/141495 PCT/US2010/036939 information available for display but insufficient screen space to display the additional information. Accordingly, the user can input requests to scroll up and/or down through incall contact information panel 302 to allow this additional information to be displayed. A request to scroll up and/or a request to scroll down can be input in a variety of different 5 manners as discussed above, such as using a pan gesture, pressing a physical key, pressing a portion of a touchscreen, and so forth. Multiple additional portions can be scrolled up and/or down through. For example, assume that additional information for the individual with which the mobile communications device is engaged in a phone call is available. The user can input a request to, for example, scroll down from the displayed portion of in-call 10 contact information panel 302 in Fig. 3, resulting in a different portion of panel 302 being displayed.

[0059] Fig. 4 illustrates an example portion of in-call contact information panel 302 in accordance with one or more embodiments. The portion of panel 302 illustrated in Fig. 4 is the portion displayed after the user requests to scroll down from the display in Fig. 3. 15 In-call contact information panel 302 includes status information 304 and contact information 320. Status information 304 is the same status information as discussed above with reference to Fig. 3.

[00601 Contact information 320 is additional in-call contact information for the phone call that the mobile communications device is currently engaged in. In the illustrated 20 example, this in-call contact information includes an indication of a home phone number for the individual, as well as an instant messaging (IM) address for the individual and an e-mail address for the individual. Although, a message or text option (analogous to options 312 and 314) arc not illustrated for the addresses in contact information 320, such a message or text option can still be available to the user. For example, the user could touch 25 the area of the screen that displays the e-mail address in order to have a data input screen opened to allow data to be input that is subsequently sent as a message to the address.

[00611 Fig. 5 illustrates additional example panels in accordance with one or more embodiments. A call control panel 502 and two in-call contact information panels 504 and 506 are illustrated. Although three panels are illustrated in Fig. 5, in one or more 30 embodiments only one of the three panels is displayed at any given time. The user can transition between these three panels 502, 504, and 506, using a pan gesture or other user inputs as discussed above.

[0062) Fig. 5 illustrates the situation where the user of the device displaying panels 502 - 506 is engaged in two phone calls concurrently. A user can be engaged in two 14 WO 2010/141495 PCT/US2010/036939 phone calls concurrently in a variety of situations, such as a conference call, using call waiting or otherwise putting one individual on hold, and so forth. A separate in-call contact panel 504 and 506 is displayed for each phone call. For the phone calls illustrated in Fig. 5, the phone call to the individual “Dane” is currently on hold while the phone call 5 to the individual “Sarah” is currently active. This status of the phone calls is illustrated in panels 502 - 506.

[00631 Fig. 6 illustrates additional example panels in accordance with one or more embodiments. A call control panel 602 und two in-call contact information panels 604 and 606 are illustrated. Although three panels are illustrated in Fig. 6, in one or more 10 embodiments only one of the three panels is displayed at any given time. The user can transition between these three panels 602, 604, and 606, using a pan gesture or other user inputs as discussed above.

[0064, Fig. 6 illustrates the situation where the user of the device displaying panels 602 - 606 is engaged in two phone calls concurrently, one of which is a conference call. A 15 separate in-call contact panel 604 and 606 is displayed for each phone call. For the phone calls illustrated in Fig. 6, the phone call to the individual “Sarah” is on hold while the conference call is currently active. This status of the phone calls is illustrated in panels 602 - 606.

[0065) In the illustrated example, in-call contact panel 604 includes information 20 regarding the multiple other individuals that arc part of the conference call. As multiple individuals are included in the conference call, the information regarding each individual that is included in panel 604 can be reduced in order to conserve space. For example, a name of the individual, an image recently uploaded to a social networking service by the individual, and a duration that that individual has been on the phone call to the device 25 displaying panel 604 can be displayed. Indications can also be displayed that the user can end the individual’s participation in the conference call, such as by disconnecting the individual (e.g., “end”), or returning the individual to a one-on-one call (e.g., “private”). [0066] Fig. 7 is a flowchart illustrating an example process 700 for a device implementing the in-call contact information display in accordance with one or more 30 embodiments. Process 700 is carried out by a mobile communications device, such as device 102 of Fig. 1, and can be implemented in software, firmware, hardware, or combinations thereof. Process 700 is an example process for implementing the in-call contact information display; additional discussions of implementing the in-call contact information display are included herein with reference to different figures. 15 WO 2010/141495 PCT/US2010/036939 [00671 In process 700, call control information for a phone call is displayed in a call control panel (act 702). A variety of different information including status information regarding the phone and/or phone call as well as indications of various control requests that can be made by the user regarding the phone call can be displayed as discussed above. 5 [00681 A single user input requesting display of in-call contact information in an in call contact information display panel is received (act 704). This in-call contact information display panel includes various information regarding the individual with which the device implementing process 700 is currently engaged in a phone call as discussed above. 10 [0069] In response to the request in act 704, the ίη-call contact information regarding the individual engaged in the phone call is displayed (act 706). This in-call contact information can be displayed in an in-call contact information display panel as discussed above, or alternatively can be displayed in different manners, [00701 Fig. 8 is a flowchart illustrating an example process 800 for a device 15 implementing the in-call contact information display in accordance with one or more embodiments. Process 800 is carried out by a mobile communications device, such as device 102 of Fig. 1, and can be implemented in software, Firmware, hardware, or combinations thereof. Process 800 is an example process for implementing the in-call contact information display; additional discussions of implementing the in-call contact 20 information display arc included herein with reference to different figures.

[0071J In process 800, a request to display in-call contact information regarding an individual engaged with in a phone call is received (act 802). This individual is the individual with which the device implementing process 800 is engaged in the phone call. [0072( In response to the request, the in-call contact information is obtained (act 804). 25 This in-call contact information includes information obtained from a social networking service as discussed above. This information can be obtained from the social networking service in response to the request in act 802, or alternatively can be obtained from the social networking service at other times and maintained in a local store of the device implementing process 800 as discussed above. 30 [0073] The obtained in-call contact information regarding the individual engaged in the phone call is displayed (act 806). This information is displayed in an in-call contact information display panel, as discussed above.

[0074] Fig. 9 illustrates an example computing device 900 that can be configured to implement the in-call contact information display in accordance with one or more 16 WO 2010/141495 PCT/US2010/036939 embodiments. Computing device 900 can be, for example, a mobile communications device 102 of Fig. 1.

[0075] Computing device 900 includes one or more processors or processing units 902, one or more computer readable media 904 which can include one or more memory 5 and/or storage components 906, one or more input/output (I/O) devices 908, and a bus 910 that allows the various components and devices to communicate with one another. Computer readable media 904 and/or one or more I/O devices 908 can be included as part of, or alternatively may be coupled to, computing device 900. Bus 910 represents one or more of several types of bus structures, including a memory bus or memory controller, a 10 peripheral bus, an accelerated graphics port, a processor or local bus, and so forth using a variety of different bus architectures. Bus 910 can include wired and/or wireless buses. [0076] Memory/storage component 906 represents one or more computer storage media. Component 906 can include volatile media (such as random access memory (RAM)) and/or nonvolatile media (such as read only memory (ROM), Flash memory, 15 optical disks, magnetic disks, and so forth). Component 906 can include fixed media (e.g., RAM, ROM, a fixed hard drive, etc.) as well as removable media (e.g., a Flash memory drive, a removable hard drive, an optical disk, and so forth).

[0077] The techniques discussed herein can be implemented in software, with instructions being executed by one or more processing units 902. It is to be appreciated 20 that different instructions can be stored in different components of computing device 900, such as in a processing unit 902, in various cache memories of a processing unit 902, in other cache memories of device 900 (not shown), on other computer readable media, and so forth. Additionally, it is to be appreciated that the location where instructions arc stored in computing device 900 can change over time. 25 [0078] One or more input/output devices 908 allow a user to enter commands and information to computing device 900, and also allows information to be presented to the user and/or other components or devices. Examples of input devices include a keyboard, a cursor control device (e.g., a mouse), a microphone, a scanner, and so forth. Examples of output devices include a display device (e.g., a monitor or projector), speakers, a printer, a 30 network card, and so forth.

[0079] Various techniques may be described herein in the general context of software or program modules. Generally, software includes routines, programs, objects, components, data structures, and so forth that perform particular tasks or implement particular abstract data types. An implementation of these modules and techniques may be 17 WO 2010/141495 PCT/US2010/036939 stored on or transmitted across some form of computer readable media. Computer readable media can be any available medium or media that can be accessed by a computing device. By way of example, and not limitation, computer readable media may comprise "computer storage media" and "communications media." 5 [00801 "Computer storage media" include volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules, or other data. Computer storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks 10 (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by a computer, [0081] Communication media" typically embody computer readable instructions, data structures, program modules, or other data in a modulated data signal, such as carrier wave 15 or other transport mechanism. Communication media also include any information delivery media. The term "modulated data signal" means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media include wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, 20 infrared, and other wireless media. Combinations of any of the above arc also included within the scope of computer readable media.

[0082] Generally, any of the functions or techniques described herein can be implemented using software, firmware, hardware (e.g., fixed logic circuitry), manual processing, or a combination of these implementations. The terms “module” and 25 “component” as used herein generally represent software, firmware, hardware, or combinations thereof. In the case of a software implementation, the module or component represents program code that performs specified tasks when executed on a processor (e.g., CPU or CPUs). The program code can be stored in one or more computer readable memory devices, further description of which may be found with reference to Fig. 9. The 30 features of the in-catl contact information display techniques described herein are platform-independent, meaning that the techniques can be implemented on a variety of commercial computing platforms having a variety of processors.

[0083] Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter 18 WO 20111/141495 PCT/US2010/036939 defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and ucts described above are disclosed us example forms of implementing the claims. 19 □’Ewan , crnxan rwzn ατα iniab^a ρηνη irn nr naoa ,ρνιη Tsan -|aoana ma™ nairmaa np’ioa .zrtwan rwaa mp^an ρ-ίΛ axnria ......r. Geodau«r □ιηπη pv

»*···»· · ·* SW J«w\ ♦ *·*' '♦·"* · ·· CD Ji 12)12 052135 40300 .(moia nannn) cras&'an nwa

<img img-format="tif" img-content="drawing" file="IL216025AD00021.tif" id="idf0001" />