US20150045092A1 - Systems and methods for handling incoming calls on a media device - Google Patents
Systems and methods for handling incoming calls on a media device Download PDFInfo
- Publication number
- US20150045092A1 US20150045092A1 US14/524,963 US201414524963A US2015045092A1 US 20150045092 A1 US20150045092 A1 US 20150045092A1 US 201414524963 A US201414524963 A US 201414524963A US 2015045092 A1 US2015045092 A1 US 2015045092A1
- Authority
- US
- United States
- Prior art keywords
- computing device
- handheld computing
- communication device
- items
- media playback
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- H04M1/72558—
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
- G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
- G06F3/0481—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
- G06F3/0482—Interaction with lists of selectable items, e.g. menus
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
- G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
- G06F3/0484—Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
- G06F3/04842—Selection of displayed objects or displayed text elements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M1/00—Substation equipment, e.g. for use by subscribers
- H04M1/60—Substation equipment, e.g. for use by subscribers including speech amplifiers
- H04M1/6033—Substation equipment, e.g. for use by subscribers including speech amplifiers for providing handsfree use or a loudspeaker mode in telephone sets
- H04M1/6041—Portable telephones adapted for handsfree use
- H04M1/6058—Portable telephones adapted for handsfree use involving the use of a headset accessory device connected to the portable telephone
- H04M1/6066—Portable telephones adapted for handsfree use involving the use of a headset accessory device connected to the portable telephone including a wireless connection
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M1/00—Substation equipment, e.g. for use by subscribers
- H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
- H04M1/724—User interfaces specially adapted for cordless or mobile telephones
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M1/00—Substation equipment, e.g. for use by subscribers
- H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
- H04M1/724—User interfaces specially adapted for cordless or mobile telephones
- H04M1/72403—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
- H04M1/72409—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality by interfacing with external accessories
- H04M1/72412—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality by interfacing with external accessories using two-way short-range wireless interfaces
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M1/00—Substation equipment, e.g. for use by subscribers
- H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
- H04M1/724—User interfaces specially adapted for cordless or mobile telephones
- H04M1/72403—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
- H04M1/72442—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality for playing music files
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M1/00—Substation equipment, e.g. for use by subscribers
- H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
- H04M1/724—User interfaces specially adapted for cordless or mobile telephones
- H04M1/72469—User interfaces specially adapted for cordless or mobile telephones for operating the device by selecting functions from two or more displayed items, e.g. menus or icons
-
- H04M1/72583—
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2201/00—Electronic components, circuits, software, systems or apparatus used in telephone systems
- H04M2201/42—Graphical user interfaces
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2250/00—Details of telephonic subscriber devices
- H04M2250/02—Details of telephonic subscriber devices including a Bluetooth interface
Abstract
A handheld computing device includes a plurality of controls for controlling operation of the handheld computing device, a processor, and an application executable in the processor. The application comprises logic that receives an indication of a notification sent from a communication device and logic that provides a user interface on a display of the handheld computing device responsive to receiving the indication, wherein the user interface comprises a plurality of items each corresponding to a respective action for handling the notification, wherein each of the plurality of items is assigned to a respective control of the handheld computing device for invoking the respective action. The application further comprises logic that receives a selection of one of the items.
Description
- This is a continuation application of U.S. application Ser. No. 13/328,484 entitled “Systems and Methods for Handling Incoming Calls on a Media Device,” filed on Dec. 16, 2011, the disclosure of which is incorporated herein by reference in its entirety.
- With the rapid development in communications technology, mobile devices have become an integral part of many people's lives given the portability and the growing number of applications available on mobile devices. Today, individuals can perform a wide range of functions such as playing music, viewing photos, etc. via mobile devices. There is an ever-increasing desire to increase the functionality and efficiency of mobile devices.
- Briefly described, one embodiment, among others, is a handheld computing device that comprises a plurality of controls for controlling operation of the handheld computing device, a processor, and an application executable in the processor. The application comprises logic that receives an indication of a notification sent from a communication device and logic that provides a user interface on a display of the handheld computing device responsive to receiving the indication, wherein the user interface comprises a plurality of items each corresponding to a respective action for handling the notification, wherein each of the plurality of items is assigned to a respective control of the handheld computing device for invoking the respective action. The application further comprises logic that receives a selection of one of the items.
- Another embodiment is a method implemented in a handheld computing device for handling a notification from a communication device. The method comprises receiving, by the handheld computing device, an indication of a notification sent from a communication device and providing, by the handheld computing device responsive to receiving the indication, a user interface on a display of the handheld computing device, wherein the user interface comprises a plurality of items each corresponding to a respective action for handling the notification, wherein each of the plurality of items is assigned to a respective control of the handheld computing device for invoking the respective action. The method further comprises receiving, by the handheld computing device, a selection of one of the items.
- Another embodiment is a handheld computing device that comprises a plurality of controls for controlling operation of the handheld computing device, a processor, and an application executable in the processor. The application comprises logic that receives an indication of a notification sent from a communication device and logic that provides a user interface on a display of the handheld computing device responsive to receiving the indication, wherein the user interface comprises a plurality of items each corresponding to a respective action for controlling operation of the communication device, wherein each of the plurality of items is assigned to a respective control of the handheld computing device for invoking the respective action on the communication device. The application further comprises logic that receives a selection of one of the items.
- Other systems, methods, features, and advantages of the present disclosure will be or become apparent to one with skill in the art upon examination of the following drawings and detailed description. It is intended that all such additional systems, methods, features, and advantages be included within this description, be within the scope of the present disclosure, and be protected by the accompanying claims.
- Many aspects of the disclosure can be better understood with reference to the following drawings. The components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Moreover, in the drawings, like reference numerals designate corresponding parts throughout the several views.
-
FIG. 1 is a block diagram of an environment in which embodiments of a media playback device may be implemented. -
FIG. 2A illustrates an example user interface generated by the call processing interface in the media playback device ofFIG. 1 . -
FIG. 2B illustrates another example user interface generated by the call processing interface in the media playback device ofFIG. 1 . -
FIG. 3 is a flowchart illustrating examples of functionality implemented as portions of the call processing interface in the media playback device ofFIG. 1 according to various embodiments of the present disclosure. -
FIG. 4 is a flowchart illustrating examples of functionality implemented as portions of the security module in the media playback device ofFIG. 1 according to various embodiments of the present disclosure. -
FIG. 5 is a flowchart illustrating examples of functionality implemented as portions of the security module in the media playback device ofFIG. 1 according to alternative embodiments of the present disclosure. -
FIG. 6 is a top-level flowchart illustrating examples of functionality implemented as portions of the media playback device ofFIG. 1 for handling incoming calls according to various embodiments of the present disclosure. -
FIG. 7 illustrates the high-level data flow between the media playback device, the communication device, and the output device ofFIG. 1 . -
FIG. 8 illustrates the data flow between the media playback device, the communication device, and the output device where the devices are coupled via Bluetooth® connections. -
FIG. 9 illustrates the media playback device and a computing device wirelessly coupled via an access point. -
FIG. 10 is a schematic block diagram of the media playback device according to an embodiment of the present disclosure. -
FIG. 11 is a schematic block diagram of the communication device according to an embodiment of the present disclosure. - Having summarized various aspects of the present disclosure, reference will now be made in detail to the description of the disclosure as illustrated in the drawings. While the disclosure will be described in connection with these drawings, there is no intent to limit it to the embodiment or embodiments disclosed herein. On the contrary, the intent is to cover all alternatives, modifications and equivalents included within the spirit and scope of the disclosure as defined by the appended claims.
- With the rapid development in communications technology, mobile devices have become an integral part of many people's lives given the portability and the growing number of applications available on mobile devices. Today, individuals can perform a wide range of functions such as playing music, viewing photos, etc. via mobile devices. Consider a scenario whereby a user is listening to music on a wireless headset coupled to a media playback device while the user is working out or performing some other activity. An incoming call is received by the user's phone but the user's phone is in not immediate reach (e.g., the phone is in a gym bag). In this scenario, the user misses the call and later discovers that a missed call occurred. Various embodiments are disclosed for allowing users to handle incoming calls using a media player device. In the following discussion, a general description of the system and its components is provided, followed by a discussion of the operation of the same.
-
FIG. 1 is a block diagram of amedia playback device 102 in which embodiments for handling incoming calls disclosed herein may be implemented. Themedia playback device 102 may be embodied, for example, as a handheld computing device or other computing platform and includes adisplay 104 and an interface for receiving input from a user. - Applications and/or other functionality may be executed in the
media playback device 102 according to various embodiments. The components executed on themedia playback device 102 include, for example, amedia file manager 112, acall processing interface 115, aperipheral interface 119, asecurity module 121, and other applications, services, processes, systems, engines, or functionality not discussed in detail herein. - The
media file manager 112 is executed to facilitate playback/consumption of media files through theperipheral interface 119. Themedia file manager 112 may provide controls for performing such functions as starting, stopping, pausing, moving to the next media file in a playlist, moving to the previous media file in a sequence, and/or performing other functions relating to media content. Themedia file manager 112 is further configured to render a user interface on thedisplay 104 of themedia playback device 102 that presents such items as a content listing in relation to the current media consumption. - The
call processing interface 115 is executed to facilitate communication with acommunication device 103. For example, thecall processing interface 115 receives an indication from thecommunication device 103 when thecommunication device 103 receives an incoming call. The indication may comprise, for example, caller identification (ID) information that thecall processing interface 115 uses to display caller identification information on themedia playback device 102. In accordance with various embodiments, the caller ID information and other items are displayed in the form of a user interface on thedisplay 104 of themedia playback device 102. - Reference is made to
FIG. 2A , which illustrates anexample user interface 202 generated by the call processing interface 115 (FIG. 1 ) in the media playback device 102 (FIG. 1 ). As shown, theuser interface 202 includes various items, including an alert that informs the user that an incoming call has been received by the communication device 103 (FIG. 1 ). In accordance with various embodiments, theuser interface 202 further comprises caller ID information that includes the name and or number or other information which identifies the calling party. - For some implementations, the
communication device 103 may also transmit a graphic associated with the calling party, which themedia playback device 102 displays on theuser interface 202. However, for other implementations, graphics corresponding to a contacts list may be stored locally on themedia playback device 102 and retrieved when themedia playback device 102 receives an indication from thecommunication device 103 that an incoming call has been received. Additional details relating to the retrieval of limited access data are described below. - As shown, the
user interface 202 further comprises items whereby the user can select to accept or reject the incoming call received by thecommunication device 103. For some embodiments, thecall processing interface 115 allows the user to accept or reject the incoming call by manipulatingcontrols 204 on themedia playback device 102. - Note, however, that this is just one example implementation and that other means for receiving user input may be utilized as well.
FIG. 2B illustrates anotherexample user interface 202 generated by the call processing interface 115 (FIG. 1 ) in the media playback device 102 (FIG. 1 ). As with the example user interface ofFIG. 2A , theuser interface 202 includes various items, including an alert that informs the user that an incoming call has been received by the communication device 103 (FIG. 1 ). For this implementation, however, the user specifies how to handle a call by pressing items on a touchscreen interface on themedia playback device 102. Note that while the embodiments described above involve the use of a visual alert comprising a user interface for notifying the user of an incoming call, themedia playback device 102 may also be configured to vibrate upon an incoming call being received by thecommunication device 103. - Referring back to
FIG. 1 , thecall processing interface 115 receives the user's selection regarding how to handle the incoming call (e.g., to accept or reject the incoming call) and generates a response to thecommunication device 103 communicating the user's response. Theperipheral interface 119 in themedia playback device 102 is executed to facilitate communications with other devices such as thecommunication device 103. As shown, theperipheral interface 119 may also be executed to establish a connection between themedia playback device 102 and anoutput device 130 such as a wireless headset, which may be, for example, Bluetooth® compatible and capable of supporting multiple simultaneous connections. - The
communication interface 125 on thecommunication device 103 then accepts or rejects the incoming call according to the response received from themedia playback device 102. In the event that the user accepts the call, theperipheral interface 129 in thecommunication device 103 establishes an audio path with theoutput device 130. At approximately the same time, themedia file manager 112 suspends the streaming of media content to theoutput device 130 in order to allow the user to conduct the call via an audio path between thecommunication device 103 and theoutput device 130. Once the call is terminated, themedia file manager 112 resumes streaming of the audio content to theoutput device 130. - Various data is stored in
data storage 117 implemented in themedia playback device 102 that is accessible to a user of themedia playback device 102. Thedata storage 117 may store such data as contact lists, photos, media files, user profile data, and other personal files. For some embodiments, the data stored in thedata storage 117 may be partitioned according to open access data 142 andlimited access data 145, where any user of themedia playback device 102 can access the open access data 142 while thelimited access data 145 is restricted to authorized users. Thesecurity module 121 is executed to implement privacy settings and provides restricted access to thelimited access data 145 in thedata storage 117. Thesecurity module 121 functions as a gateway through which authorized users access thelimited access data 145. - Having described the various components for handling incoming calls, a detailed description of the functionality associated with the various components described in connection with
FIG. 1 is now provided. Reference is made toFIG. 3 , which is aflowchart 300 in accordance with one embodiment for handling incoming calls via a media playback device 102 (FIG. 1 ). It is understood that theflowchart 300 ofFIG. 3 provides merely an example of the many different types of functional arrangements that may be employed to implement the operation of the call processing interface 115 (FIG. 1 ) in themedia playback device 102. As an alternative, the flowchart ofFIG. 3 may be viewed as depicting an example of steps of a method implemented in themedia playback device 102 according to one or more embodiments. - An incoming call is received by the communication interface 125 (
FIG. 1 ) in the communication device 103 (FIG. 1 ). Through the peripheral interface 129 (FIG. 1 ) in thecommunication device 103 and the peripheral interface 119 (FIG. 1 ) in themedia playback device 102, thecommunication device 103 establishes a connection with themedia playback device 102. Beginning withblock 310, themedia playback device 102 receives an indication from thecommunication device 103 that an incoming call has been received. - In
block 320, themedia playback device 102 retrieves data corresponding to the incoming call from the data storage 117 (FIG. 1 ). For some embodiments, thecall processing interface 115 receives as part of the indication fromcommunication device 103, caller identification (ID) information relating to the call. Such caller ID information may comprise, for example, the telephone number of the caller originating the incoming call. Based on this information, thecall processing interface 115 accesses thedata storage 117 to determine whether any data associated with the caller is currently stored in thedata storage 117. - Such data may comprise, for example, photos associated with callers. Other data may comprise other contact information relating to the caller and a call history corresponding to the caller. Based on the data retrieved from the
data storage 117, thecall processing interface 115 generates a user interface 202 (FIG. 2A ) rendered on the display 104 (FIG. 1 ) of themedia playback device 102 for providing the user of themedia playback device 102 options for handling the incoming call. - In
block 330, thecall processing interface 115 receives a selection from the user via theuser interface 202. Examples of selections by the user may include accepting the incoming call and rejecting the incoming call. As described earlier in connection withFIGS. 2A and 2B , theuser interface 202 may include selectable items whereby the user can accept or reject the incoming call received by thecommunication device 103. - For some embodiments, the
call processing interface 115 allows the user to accept or reject the incoming call by manipulating controls 204 (FIG. 2A ) on themedia playback device 102. In theexample user interface 202 shown inFIG. 2A , theuser interface 202 includes a graphic depicting the caller (John Smith). For some embodiments, the graphic is stored locally on themedia playback device 102 as limited access data 145 (FIG. 1 ) in thedata storage 117 and retrieved by thesecurity module 121, as described in more detail below. - In
block 340, thecall processing interface 115 generates a response based on the selection received from the user and transmits the response back to thecommunication device 103. Thecommunication interface 125 then handles the call according to the response sent by thecall processing interface 115 in themedia playback device 102. Thereafter, the portion of thecall processing interface 115 ends. - Reference is made to
FIG. 4 , which is aflowchart 400 in accordance with one embodiment for handling incoming calls via a media playback device 102 (FIG. 1 ). It is understood that theflowchart 400 ofFIG. 4 provides merely an example of the many different types of functional arrangements that may be employed to implement the operation of the security module 121 (FIG. 1 ) in themedia playback device 102. As an alternative, the flowchart ofFIG. 4 may be viewed as depicting an example of steps of a method implemented in themedia playback device 102 according to one or more embodiments. - Upon receiving an indication from the communication device 103 (
FIG. 1 ) that an incoming call has been received, the call processing interface 115 (FIG. 1 ) accesses the data storage 117 (FIG. 1 ) via thesecurity module 121 to retrieve data associated with the caller originating the incoming call for purposes of generating a user interface. - Beginning with
block 410, thesecurity module 121 grants access to thelimited access data 145 in thedata storage 117 based on thecommunication device 103 currently coupled with themedia playback device 102 through the respectiveperipheral interfaces media playback device 102 and thecommunication device 103. Based on thecommunication device 103 currently paired with themedia playback device 102, thesecurity module 121 determines whether an authorized user is using themedia playback device 102 and grants access to the limited access data 145 (FIG. 1 ) accordingly. For some embodiments, thelimited access data 145 may be partitioned according to users such that each user is only able to access certain data within thedata storage 117. - In
block 420, thesecurity module 121 performs a look-up in thedata storage 117 to retrieve data associated with the incoming call. For example, thesecurity module 121 may perform a look-up among contacts of the current user and retrieve a photo, if available, associated with the caller originating the incoming call. - In
block 430, the data retrieved by thesecurity module 121 is forwarded to thecall processing interface 115, which then generates a user interface 202 (FIG. 2A ) using the retrieved data, as described above. Thereafter, the portion of thesecurity module 121 ends. - Turning now to
FIG. 5 , shown is aflowchart 500 in accordance with other embodiments for providing restricted access to the data storage 117 (FIG. 1 ) via the security module 121 (FIG. 1 ) in themedia playback device 102. It is understood that theflowchart 500 ofFIG. 5 provides merely an example of the many different types of functional arrangements that may be employed to implement the operation of thesecurity module 121 in the media playback device 102 (FIG. 1 ). As an alternative, the flowchart ofFIG. 5 may be viewed as depicting an example of steps of a method implemented in themedia playback device 102 according to one or more embodiments. - In
block 510, themedia playback device 102 receives a request to access thedata storage 117 in themedia playback device 102. A user may be attempting to access, for example, contact lists, photos, media files, user profile data, and/or other personal files stored in thedata storage 117. For some embodiments, such data may be stored as limited access data 145 (FIG. 1 ) where only authorized users are allowed to access such data. - In
block 520, thesecurity module 121 determines whether the user attempting to access thedata storage 117 is an authorized user. Thesecurity module 121 may determine whether a user is authorized according to various means. For some embodiments, thesecurity module 121 determines the identity of the user according to the communication device 103 (FIG. 1 ) currently paired to themedia playback device 102. Thesecurity module 121 may also be configured to grant access to thelimited access data 145 upon successful pairing of thecommunication device 103 and themedia playback device 102 via a Bluetooth® connection. For some embodiments, thesecurity module 121 may determine the identity of the user according to a point-to-point connection with another device via a Wi-Fi Direct connection. - For other embodiments, the
security module 121 may determine the identity of the user according to connection via an access point. To illustrate, reference is made toFIG. 9 . As shown, a media playback device 102 (FIG. 1 ) and acomputing device 904 may be part of an IEEE 802.11 network whereby thedevices access point 902, which provides access to anetwork 908 such as the Internet. Based on an identifier (e.g., an IP address), themedia playback device 102 may determine the identity of the user of thecomputing device 904 in determining whether to grant access to the limited access data 145 (FIG. 1 ) in the data storage 117 (FIG. 1 ). For other embodiments, thesecurity module 121 may be configured to provide access to thelimited access data 145 via a web portal upon validation of user credentials. - Referring back to block 520 in
FIG. 5 , if thesecurity module 121 determines that the user attempting to access thedata storage 117 is an authorized user, thesecurity module 121 proceeds to block 530, where thesecurity module 121 grants access to thelimited access data 145 according to the identity of the user. Inblock 540, if the user is not an authorized user, thesecurity module 121 may be configured to grant access to only the open access data 142 (FIG. 1 ) in thedata storage 117. Note that thelimited access data 145 may be partitioned according to users such that different users access different portions of thelimited access data 145. Thesecurity module 121 thus provides limited access to such personal information as contact lists, call logs, and so on. Thereafter, the portion of thesecurity module 121 ends. - Reference is made to
FIG. 6 , which is aflowchart 600 in accordance with one embodiment for handling incoming calls via execution of the various components of the media playback device 102 (FIG. 1 ). It is understood that theflowchart 600 ofFIG. 6 provides merely an example of the many different types of functional arrangements that may be employed to implement the operation of themedia playback device 102. As an alternative, the flowchart ofFIG. 6 may be viewed as depicting an example of steps of a method implemented in themedia playback device 102 according to one or more embodiments. - In accordance with one method implemented in a
media playback device 102 for handling incoming calls to a communication device 103 (FIG. 1 ), themedia playback device 102 begins withblock 610 and establishes a connection with anoutput device 130, which may comprise, for example, a Bluetooth® compatible headset. - In
block 620, themedia playback device 102 streams audio content to theoutput device 130. Inblock 630, themedia playback device 102 receives an indication from thecommunication device 103 of an incoming call received by thecommunication device 103. Based on the contents of the indication, themedia playback device 102 proceeds to block 640 and generates an alert corresponding to the incoming call. As described earlier in connection withFIG. 2A , the alert may be embodied as a user interface 202 (FIGS. 2A and 2B ) shown on the display 104 (FIG. 1 ) of themedia playback device 102. Alerts embodied asuser interfaces 202 may include various items, including the name and number of the calling party and a graphic of the caller originating the incoming call. - Reference is made to
FIG. 7 , which illustrates the high-level data flow between themedia playback device 102, thecommunication device 103, and theoutput device 130. Themedia playback device 102 establishes a connection with theoutput device 130 and streams audio content. Thecommunication device 103 receives an incoming call and sends a call indicator to themedia playback device 102, which generates an alert in the form of a user interface 202 (FIGS. 2A and 2B ). At the same time, thecommunication device 103 may also transmit an audio alert (e.g., a ring tone) directly to theoutput device 130. The user of theoutput device 130 may therefore receive both a visual alert and an audio alert relating to the incoming call. - The
media playback device 102 receives a selection from the user relating to the incoming call. For example, the user may accept or reject the incoming call and specify the desired action by manipulating one or more controls on themedia playback device 102. As described earlier in connection withFIG. 2A , the user may, for example, press the PLAY button on themedia playback device 102 to accept the incoming call. Alternatively, the user may also interface via a touchscreen on the media playback device 102 (FIG. 2B ). Based on the user's selection, themedia playback device 102 transmits a response back to thecommunication device 103. - In the event that the user elects to accept the call, the
media playback device 102 suspends streaming of the audio content to theoutput device 130, and thecommunication device 103 routes the audio from the incoming call to theoutput device 130 so that the user can conduct the call. Upon termination of the incoming call, thecommunication device 103 alerts themedia playback device 102, and themedia playback device 102 resumes streaming of the audio. -
FIG. 8 illustrates the data flow between themedia playback device 102, thecommunication device 103, and theoutput device 130, where the devices are coupled via Bluetooth® connections. The sequence of events is shown for one embodiment for handling an incoming call via themedia playback device 102. For some embodiments, an Advanced Audio Distribution Profile (A2DP)/Audio/Video Remote Control Profile (AVRCP) link is established between themedia playback device 102 and theoutput device 130, whereby theoutput device 130 is capable of executing basic remote control commands (play, pause, etc.) associated with audio content being streamed from themedia playback device 102. - A Hands-Free Profile (HFP)/Human Interface Device Profile (HID) may be established between the
media playback device 102 and thecommunication device 103. A Hands-Free Profile (HFP)/Headset Profile (HSP) link may be established between thecommunication device 103 and theoutput device 130. Upon establishing an A2DP/AVRCP connection, themedia playback device 102 streams audio content to theoutput device 130. - As shown, an incoming call is received by the
communication device 103, and a +CLIP (Calling Line Identification Presentation) unsolicited response is sent from thecommunication device 103 to themedia playback device 102. At approximately the same time, the communication device transmits an alert (e.g., a ring tone) to theoutput device 130. For some embodiments, a pause command is transmitted by theoutput device 130 to the media playback device to suspend streaming of the audio content. - Next, the user accepts the incoming call, and a synchronous connection-oriented (SCO) link is established between the
communication device 103 and theoutput device 130. Call information is retrieved by themedia playback device 102 from thecommunication device 103, and the call is conducted. - The user terminates the call via the
media playback device 102 or theoutput device 130, which then alerts thecommunication device 103 that the call has been terminated. Thecommunication device 103 closes the SCO link with theoutput device 130, and playback resumes between themedia playback device 102 and theoutput device 130. - With reference to
FIG. 10 , shown is a schematic block diagram of themedia playback device 102 according to an embodiment of the present disclosure. Themedia playback device 102 includes at least one processor circuit, for example, having aprocessor 1103 and amemory 1106, both of which are coupled to alocal interface 1109. Thelocal interface 1109 may comprise, for example, a data bus with an accompanying address/control bus or other bus structure as can be appreciated. - Stored in the
memory 1106 are both data and several components that are executable by theprocessor 1103. In particular, stored in thememory 1106 and executable by theprocessor 1103 are themedia file manager 112, thecall processing interface 115, theperipheral interface 119, thesecurity module 121, and potentially other applications. Also stored in thememory 1106 may be thedata storage 117 and other data. In addition, an operating system may be stored in thememory 1106 and executable by theprocessor 1103. - With reference to
FIG. 11 , shown is a schematic block diagram of thecommunication device 103 according to an embodiment of the present disclosure. Thecommunication device 103 includes at least one processor circuit, for example, having aprocessor 1203 and amemory 1206, both of which are coupled to alocal interface 1209. Thelocal interface 1209 may comprise, for example, a data bus with an accompanying address/control bus or other bus structure as can be appreciated. - Stored in the
memory 1206 are both data and several components that are executable by theprocessor 1203. In particular, stored in thememory 1206 and executable by theprocessor 1203 are thecommunication interface 125, theperipheral interface 129, and potentially other applications. In addition, an operating system may be stored in thememory 1206 and executable by theprocessor 1203. - It is understood that there may be other applications that are stored in each of the
memories 1106/1206 and are executable by therespective processors 1103/1203 as can be appreciated. Where any component discussed herein is implemented in the form of software, any one of a number of programming languages may be employed. - A number of software components are stored in the
respective memories 1106/1206 and are executable by theprocessors 1103/1203. In this respect, the term executable means a program file that is in a form that can ultimately be run by arespective processor 1103/1203. Examples of executable programs may be, for example, a compiled program that can be translated into machine code in a format that can be loaded into a random access portion of amemory 1106/1206 and run by aprocessor 1103/1203, source code that may be expressed in proper format such as object code that is capable of being loaded into a random access portion of amemory 1106/1206 and executed by aprocessor 1103/1203, or source code that may be interpreted by another executable program to generate instructions in a random access portion of one of thememories 1106/1206 to be executed by arespective processor 1103/1203, etc. - An executable program may be stored in any portion or component of a
respective memory 1106/1206 including, for example, random access memory (RAM), read-only memory (ROM), hard drive, solid-state drive, USB flash drive, memory card, optical disc such as compact disc (CD) or digital versatile disc (DVD), floppy disk, magnetic tape, or other memory components. - Each of the
memories 1106/1206 is defined herein as including both volatile and nonvolatile memory and data storage components. Volatile components are those that do not retain data values upon loss of power. Nonvolatile components are those that retain data upon a loss of power. Thus, eachmemory 1106/1206 may comprise, for example, random access memory (RAM), read-only memory (ROM), hard disk drives, solid-state drives, USB flash drives, memory cards accessed via a memory card reader, floppy disks accessed via an associated floppy disk drive, optical discs accessed via an optical disc drive, magnetic tapes accessed via an appropriate tape drive, and/or other memory components, or a combination of any two or more of these memory components. - In addition, the RAM may comprise, for example, static random access memory (SRAM), dynamic random access memory (DRAM), or magnetic random access memory (MRAM) and other such devices. The ROM may comprise, for example, a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or other like memory device.
- Also, each
processor 1103/1203 may represent multiple processors and eachmemory 1106/1206 may represent multiple memories that operate in parallel processing circuits, respectively. In such a case, eachlocal interface 1109/1209 may be an appropriate network that facilitates communication between any two of the multiple processors, between any processor and any of the multiple memories, or between any two memories, etc. Such alocal interface 1109/1209 may comprise additional systems designed to coordinate this communication, including, for example, performing load balancing. Eachprocessor 1103/1203 may be of electrical or of some other available construction. - Although the components and applications described herein may be embodied in software or code executed by general purpose hardware as discussed above, as an alternative the same may also be embodied in dedicated hardware or a combination of software/general purpose hardware and dedicated hardware.
- If embodied in dedicated hardware, each can be implemented as a circuit or state machine that employs any one of or a combination of a number of technologies. These technologies may include, but are not limited to, discrete logic circuits having logic gates for implementing various logic functions upon an application of one or more data signals, application specific integrated circuits having appropriate logic gates, or other components, etc. Such technologies are generally well known by those skilled in the art and, consequently, are not described in detail herein.
- The flowcharts of
FIGS. 3-6 show an example of functionality associated with implementation of the various components in the system ofFIG. 1 . If embodied in software, each block may represent a module, segment, or portion of code that comprises program instructions to implement the specified logical function(s). The program instructions may be embodied in the form of source code that comprises human-readable statements written in a programming language or machine code that comprises numerical instructions recognizable by a suitable execution system such as aprocessor 1103 in a computer system or other system. The machine code may be converted from the source code, etc. If embodied in hardware, each block may represent a circuit or a number of interconnected circuits to implement the specified logical function(s). - Although the flowcharts of
FIGS. 3-6 show a specific order of execution, it is understood that the order of execution may differ from that which is depicted. For example, the order of execution of two or more blocks may be scrambled relative to the order shown. Also, two or more blocks shown in succession inFIGS. 3-6 may be executed concurrently or with partial concurrence. Further, in some embodiments, one or more of the blocks shown inFIGS. 3-6 may be skipped or omitted. In addition, any number of counters, state variables, warning semaphores, or messages might be added to the logical flow described herein, for purposes of enhanced utility, accounting, performance measurement, or providing troubleshooting aids, etc. It is understood that all such variations are within the scope of the present disclosure. - Also, any logic or application described herein that comprises software or code can be embodied in any non-transitory computer-readable medium for use by or in connection with an instruction execution system such as, for example, a processor in a computer system or other system. Each may comprise, for example, statements including instructions and declarations that can be fetched from the computer-readable medium and executed by the instruction execution system.
- In the context of the present disclosure, a “computer-readable medium” can be any medium that can contain, store, or maintain the logic or application described herein for use by or in connection with the instruction execution system. The computer-readable medium can comprise any one of many physical media such as, for example, magnetic, optical, or semiconductor media. More specific examples of a suitable computer-readable medium would include, but are not limited to, magnetic tapes, magnetic floppy diskettes, magnetic hard drives, memory cards, solid-state drives, USB flash drives, or optical discs.
- Also, the computer-readable medium may be a random access memory (RAM) including, for example, static random access memory (SRAM) and dynamic random access memory (DRAM), or magnetic random access memory (MRAM). In addition, the computer-readable medium may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or other type of memory device.
- It should be emphasized that the above-described embodiments of the present disclosure are merely possible examples of implementations set forth for a clear understanding of the principles of the disclosure. Many variations and modifications may be made to the above-described embodiment(s) without departing substantially from the spirit and principles of the disclosure. All such modifications and variations are intended to be included herein within the scope of this disclosure and protected by the following claims.
Claims (20)
1. A handheld computing device, comprising:
a plurality of controls for controlling operation of the handheld computing device;
a processor; and
an application executable in the processor, the application comprising:
logic that receives an indication of a notification sent from a communication device;
logic that provides a user interface on a display of the handheld computing device responsive to receiving the indication, wherein the user interface comprises a plurality of items each corresponding to a respective action for handling the notification, wherein each of the plurality of items is assigned to a respective control of the handheld computing device for invoking the respective action; and
logic that receives a selection of one of the items.
2. The handheld computing device of claim 1 , wherein the plurality of controls comprise playback controls for controlling playback of media content on the handheld computing device.
3. The handheld computing device of claim 1 , further comprising logic for sending a response to the communication device based on the selection.
4. The handheld computing device of claim 1 , further comprising logic for suspending playback of media content responsive to receiving the selection of the one item.
5. The handheld computing device of claim 1 , wherein the notification is sent from the communication device responsive to the communication device receiving an incoming call.
6. The handheld computing device of claim 5 , wherein the selection of the one item invokes one of accepting an incoming call received by the communication device or rejecting the incoming call received by the communication device.
7. The handheld computing device of claim 1 , wherein the assignment of each of the plurality of items to a respective control of the handheld computing device for invoking the respective action is shown on the user interface on the display.
8. The handheld computing device of claim 1 , wherein the logic receives the selection of one of the items by sensing manipulation of a corresponding assigned control of the handheld computing device.
9. A method implemented in a handheld computing device for handling a notification from a communication device, comprising:
receiving, by the handheld computing device, an indication of a notification sent from a communication device;
responsive to receiving the indication, providing, by the handheld computing device, a user interface on a display of the handheld computing device, wherein the user interface comprises a plurality of items each corresponding to a respective action for handling the notification, wherein each of the plurality of items is assigned to a respective control of the handheld computing device for invoking the respective action; and
receiving, by the handheld computing device, a selection of one of the items.
10. The method of claim 9 , further comprising generating, by the handheld computing device, one or more of a visual alert and an audio alert responsive to receiving the indication.
11. The method of claim 9 , wherein the plurality of controls comprise playback controls for controlling playback of media content on the handheld computing device.
12. The method of claim 9 , further comprising suspending playback of media content responsive to receiving the selection of the one item.
13. The method of claim 12 , further comprising resuming, by the handheld computing device, playback of the media content responsive to the incoming call being terminated.
14. The method of claim 9 , wherein the notification is sent from the communication device responsive to the communication device receiving an incoming call.
15. The method of claim 14 , wherein the selection of the one item invokes one of accepting an incoming call received by the communication device or rejecting the incoming call received by the communication device.
16. The method of claim 9 , wherein the assignment of each of the plurality of items to a respective control of the handheld computing device for invoking the respective action is shown on the user interface on the display.
17. The method of claim 9 , wherein receiving the selection of one of the items comprises sensing manipulation of a corresponding assigned control of the handheld computing device.
18. A handheld computing device, comprising:
a plurality of controls for controlling operation of the handheld computing device;
a processor; and
an application executable in the processor, the application comprising:
logic that receives an indication of a notification sent from a communication device;
logic that provides a user interface on a display of the handheld computing device responsive to receiving the indication, wherein the user interface comprises a plurality of items each corresponding to a respective action for controlling operation of the communication device, wherein each of the plurality of items is assigned to a respective control of the handheld computing device for invoking the respective action on the communication device; and
logic that receives a selection of one of the items.
19. The handheld computing device of claim 1 , wherein the plurality of controls comprise playback controls for controlling playback of media content on the handheld computing device.
20. The handheld computing device of claim 1 , further comprising logic for sending a response to the communication device for controlling the communication device based on the selection.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/524,963 US20150045092A1 (en) | 2011-12-16 | 2014-10-27 | Systems and methods for handling incoming calls on a media device |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/328,484 US8892088B2 (en) | 2011-12-16 | 2011-12-16 | Systems and methods for handling incoming calls on a media device |
US14/524,963 US20150045092A1 (en) | 2011-12-16 | 2014-10-27 | Systems and methods for handling incoming calls on a media device |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/328,484 Continuation US8892088B2 (en) | 2011-12-16 | 2011-12-16 | Systems and methods for handling incoming calls on a media device |
Publications (1)
Publication Number | Publication Date |
---|---|
US20150045092A1 true US20150045092A1 (en) | 2015-02-12 |
Family
ID=48610607
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/328,484 Active 2032-01-24 US8892088B2 (en) | 2011-12-16 | 2011-12-16 | Systems and methods for handling incoming calls on a media device |
US14/524,963 Abandoned US20150045092A1 (en) | 2011-12-16 | 2014-10-27 | Systems and methods for handling incoming calls on a media device |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/328,484 Active 2032-01-24 US8892088B2 (en) | 2011-12-16 | 2011-12-16 | Systems and methods for handling incoming calls on a media device |
Country Status (3)
Country | Link |
---|---|
US (2) | US8892088B2 (en) |
CN (1) | CN103220404B (en) |
TW (1) | TWI532359B (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10057880B2 (en) * | 2016-12-11 | 2018-08-21 | Qualcomm Incorporated | Smart notifications between devices |
Families Citing this family (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DK2728893T3 (en) * | 2012-11-05 | 2020-06-29 | Accenture Global Services Ltd | Managing a data stream |
KR102195314B1 (en) * | 2013-08-28 | 2020-12-24 | 삼성전자주식회사 | An electronic device and operating metod thereof |
US9510083B2 (en) * | 2014-03-14 | 2016-11-29 | Apple Inc. | Managing connections of a user device |
KR102156862B1 (en) | 2014-09-15 | 2020-09-16 | 후아웨이 테크놀러지 컴퍼니 리미티드 | Communication method, communication system and relevant device of wearable device |
KR102296184B1 (en) * | 2014-10-01 | 2021-08-31 | 삼성전자주식회사 | SCHEME FOR Communication AND transmitting discovery signal in MOBILE COMMUNICATION SYSTEM |
GB2538853B (en) * | 2015-04-09 | 2018-09-19 | Dolby Laboratories Licensing Corp | Switching to a second audio interface between a computer apparatus and an audio apparatus |
US20160366263A1 (en) * | 2015-06-09 | 2016-12-15 | Lg Electronics Inc. | Method and device for transmitting or receiving data in wireless communication system |
US9716969B2 (en) * | 2015-07-01 | 2017-07-25 | Lg Electronics Inc. | Method and apparatus for controlling device in wireless communication system |
US10572107B1 (en) * | 2017-06-23 | 2020-02-25 | Amazon Technologies, Inc. | Voice communication targeting user interface |
US10638229B1 (en) * | 2019-03-29 | 2020-04-28 | Bose Corporation | Methods and systems for establishing user controls |
CN112596907B (en) * | 2019-12-31 | 2021-12-03 | 华为技术有限公司 | Method for occupying equipment and electronic equipment |
CN115297405A (en) * | 2020-01-22 | 2022-11-04 | 荣耀终端有限公司 | Audio output method and terminal equipment |
CN111641753B (en) * | 2020-05-27 | 2021-07-06 | 维沃移动通信有限公司 | Audio output control method and device, electronic equipment and readable storage medium |
Citations (31)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050027385A1 (en) * | 2003-08-01 | 2005-02-03 | Wen-Hsiang Yueh | MP3 player having a wireless earphone communication with a mobile |
US20050181826A1 (en) * | 2004-02-18 | 2005-08-18 | Partner Tech. Corporation | Handheld personal digital assistant for communicating with a mobile in music-playing operation |
US20060030322A1 (en) * | 2004-08-04 | 2006-02-09 | Samsung Electronics Co., Ltd. | Method and system for handoff between base stations supporting multi-profile operation in BWA system |
US20060040699A1 (en) * | 2004-08-17 | 2006-02-23 | Samsung Electronics Co., Ltd. | Method and system for forming and transmitting/receiving neighbor base station information in a BWA communication system |
US20060199537A1 (en) * | 2005-03-07 | 2006-09-07 | Broadcom Corporation | Automatic resource availability using Bluetooth |
US20060255963A1 (en) * | 2005-05-13 | 2006-11-16 | Microsoft Corporation | System and method for command and control of wireless devices using a wearable device |
US20070112552A1 (en) * | 2005-11-17 | 2007-05-17 | International Business Machines Corporation | Native function of portable electronic device surfaced as soft device in host computer |
US20070142025A1 (en) * | 2002-04-09 | 2007-06-21 | Skullcandy, Inc. | Personal Portable Integrator for Music Player and Mobile Phone |
US20070173232A1 (en) * | 2006-01-25 | 2007-07-26 | Inventec Corporation | Incoming call notification device |
US20070206829A1 (en) * | 2006-03-06 | 2007-09-06 | Sony Ericsson Mobile Communications Ab | Audio headset |
US20070238484A1 (en) * | 2006-03-28 | 2007-10-11 | Sony Ericsson Mobile Communications Ab | Wireless peripheral with a multi-function control |
US20080076390A1 (en) * | 2006-09-22 | 2008-03-27 | Hong Fu Jin Precision Industry (Shenzhen) Co.,Ltd. | Media player capable of backing up data from a mobile phone and preventing other people from accessing the backed upped data |
US20080242365A1 (en) * | 2007-03-28 | 2008-10-02 | Motorola, Inc. | Devices and methods for hands-free connectivity to plural devices |
US20080280652A1 (en) * | 2007-05-08 | 2008-11-13 | Firefly Mobile, Inc. | Reconfigurable keypad method in handset device operable with plural subsystems |
US20090053997A1 (en) * | 2007-08-24 | 2009-02-26 | Motorola, Inc. | Dynamic user interface for displaying connection status and method thereof |
US20090061769A1 (en) * | 2007-08-31 | 2009-03-05 | Zimbric Frederick J | Methods and devices for automatic multiple pairing of bluetooth devices |
US20090077467A1 (en) * | 2007-07-16 | 2009-03-19 | Abhishek Adappa | Mobile television and multimedia player key presentations |
US20090124281A1 (en) * | 2007-11-12 | 2009-05-14 | Kabushiki Kaisha Toshiba | Information processing apparatus capable of outgoing and incoming calls |
US20090186580A1 (en) * | 2008-01-23 | 2009-07-23 | Samsung Electronics Co., Ltd. | Wireless headset and multipoint pairing method for the same |
US20090197524A1 (en) * | 2008-02-04 | 2009-08-06 | Sony Ericsson Mobile Communications Ab | Intelligent interaction between devices in a local network |
US20100045928A1 (en) * | 2008-08-25 | 2010-02-25 | Tri-Specs, Inc. | Fashion eyewear frame that houses circuitry to effect wireless audio communication while providing extraneous background noise cancellation capability |
US20100067723A1 (en) * | 2007-04-10 | 2010-03-18 | Oticon A/S | User interface for a communications device |
US20100112964A1 (en) * | 2008-11-04 | 2010-05-06 | Kyung-Hack Yi | Wrist watch type mobile terminal |
US20100146463A1 (en) * | 2008-12-04 | 2010-06-10 | Samsung Electronics Co., Ltd. | Watch phone and method for handling an incoming call in the watch phone |
US20100227631A1 (en) * | 2009-03-06 | 2010-09-09 | Apple Inc. | Remote messaging for mobile communication device and accessory |
US20100304674A1 (en) * | 2009-06-01 | 2010-12-02 | Samsung Electronics Co. Ltd. | System and method for connecting bluetooth devices |
US20110081859A1 (en) * | 2009-10-06 | 2011-04-07 | Lg Electronics Inc. | Mobile terminal capable of being connected to audio output device using short-range communication and method of controlling the operation of the mobile terminal |
US20110117851A1 (en) * | 2009-11-18 | 2011-05-19 | Samsung Electronics Co. Ltd. | Method and apparatus for remote controlling bluetooth device |
US20120135686A1 (en) * | 2009-08-13 | 2012-05-31 | Zte Corporation | Method and system for orderly connection of a bluetooth headset controlled by terminal |
US20120238330A1 (en) * | 2011-03-14 | 2012-09-20 | Willie Wu | Apparatus that connects wirelessly to a cell phone via bluetooth technology and provides additional ringing sound and visual alert upon an incoming call |
US20120242510A1 (en) * | 2011-03-25 | 2012-09-27 | Choi Sungha | Communication connecting apparatus and method thereof |
Family Cites Families (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN2788458Y (en) | 2005-06-06 | 2006-06-14 | 金纯� | Blue Tooth MP3 player with the function of Blue Tooth USB adapter |
CN201270156Y (en) * | 2008-10-09 | 2009-07-08 | 捷顶微电子(上海)有限公司 | MP3 player |
-
2011
- 2011-12-16 US US13/328,484 patent/US8892088B2/en active Active
-
2012
- 2012-09-27 TW TW101135488A patent/TWI532359B/en active
- 2012-10-16 CN CN201210392612.0A patent/CN103220404B/en active Active
-
2014
- 2014-10-27 US US14/524,963 patent/US20150045092A1/en not_active Abandoned
Patent Citations (31)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20070142025A1 (en) * | 2002-04-09 | 2007-06-21 | Skullcandy, Inc. | Personal Portable Integrator for Music Player and Mobile Phone |
US20050027385A1 (en) * | 2003-08-01 | 2005-02-03 | Wen-Hsiang Yueh | MP3 player having a wireless earphone communication with a mobile |
US20050181826A1 (en) * | 2004-02-18 | 2005-08-18 | Partner Tech. Corporation | Handheld personal digital assistant for communicating with a mobile in music-playing operation |
US20060030322A1 (en) * | 2004-08-04 | 2006-02-09 | Samsung Electronics Co., Ltd. | Method and system for handoff between base stations supporting multi-profile operation in BWA system |
US20060040699A1 (en) * | 2004-08-17 | 2006-02-23 | Samsung Electronics Co., Ltd. | Method and system for forming and transmitting/receiving neighbor base station information in a BWA communication system |
US20060199537A1 (en) * | 2005-03-07 | 2006-09-07 | Broadcom Corporation | Automatic resource availability using Bluetooth |
US20060255963A1 (en) * | 2005-05-13 | 2006-11-16 | Microsoft Corporation | System and method for command and control of wireless devices using a wearable device |
US20070112552A1 (en) * | 2005-11-17 | 2007-05-17 | International Business Machines Corporation | Native function of portable electronic device surfaced as soft device in host computer |
US20070173232A1 (en) * | 2006-01-25 | 2007-07-26 | Inventec Corporation | Incoming call notification device |
US20070206829A1 (en) * | 2006-03-06 | 2007-09-06 | Sony Ericsson Mobile Communications Ab | Audio headset |
US20070238484A1 (en) * | 2006-03-28 | 2007-10-11 | Sony Ericsson Mobile Communications Ab | Wireless peripheral with a multi-function control |
US20080076390A1 (en) * | 2006-09-22 | 2008-03-27 | Hong Fu Jin Precision Industry (Shenzhen) Co.,Ltd. | Media player capable of backing up data from a mobile phone and preventing other people from accessing the backed upped data |
US20080242365A1 (en) * | 2007-03-28 | 2008-10-02 | Motorola, Inc. | Devices and methods for hands-free connectivity to plural devices |
US20100067723A1 (en) * | 2007-04-10 | 2010-03-18 | Oticon A/S | User interface for a communications device |
US20080280652A1 (en) * | 2007-05-08 | 2008-11-13 | Firefly Mobile, Inc. | Reconfigurable keypad method in handset device operable with plural subsystems |
US20090077467A1 (en) * | 2007-07-16 | 2009-03-19 | Abhishek Adappa | Mobile television and multimedia player key presentations |
US20090053997A1 (en) * | 2007-08-24 | 2009-02-26 | Motorola, Inc. | Dynamic user interface for displaying connection status and method thereof |
US20090061769A1 (en) * | 2007-08-31 | 2009-03-05 | Zimbric Frederick J | Methods and devices for automatic multiple pairing of bluetooth devices |
US20090124281A1 (en) * | 2007-11-12 | 2009-05-14 | Kabushiki Kaisha Toshiba | Information processing apparatus capable of outgoing and incoming calls |
US20090186580A1 (en) * | 2008-01-23 | 2009-07-23 | Samsung Electronics Co., Ltd. | Wireless headset and multipoint pairing method for the same |
US20090197524A1 (en) * | 2008-02-04 | 2009-08-06 | Sony Ericsson Mobile Communications Ab | Intelligent interaction between devices in a local network |
US20100045928A1 (en) * | 2008-08-25 | 2010-02-25 | Tri-Specs, Inc. | Fashion eyewear frame that houses circuitry to effect wireless audio communication while providing extraneous background noise cancellation capability |
US20100112964A1 (en) * | 2008-11-04 | 2010-05-06 | Kyung-Hack Yi | Wrist watch type mobile terminal |
US20100146463A1 (en) * | 2008-12-04 | 2010-06-10 | Samsung Electronics Co., Ltd. | Watch phone and method for handling an incoming call in the watch phone |
US20100227631A1 (en) * | 2009-03-06 | 2010-09-09 | Apple Inc. | Remote messaging for mobile communication device and accessory |
US20100304674A1 (en) * | 2009-06-01 | 2010-12-02 | Samsung Electronics Co. Ltd. | System and method for connecting bluetooth devices |
US20120135686A1 (en) * | 2009-08-13 | 2012-05-31 | Zte Corporation | Method and system for orderly connection of a bluetooth headset controlled by terminal |
US20110081859A1 (en) * | 2009-10-06 | 2011-04-07 | Lg Electronics Inc. | Mobile terminal capable of being connected to audio output device using short-range communication and method of controlling the operation of the mobile terminal |
US20110117851A1 (en) * | 2009-11-18 | 2011-05-19 | Samsung Electronics Co. Ltd. | Method and apparatus for remote controlling bluetooth device |
US20120238330A1 (en) * | 2011-03-14 | 2012-09-20 | Willie Wu | Apparatus that connects wirelessly to a cell phone via bluetooth technology and provides additional ringing sound and visual alert upon an incoming call |
US20120242510A1 (en) * | 2011-03-25 | 2012-09-27 | Choi Sungha | Communication connecting apparatus and method thereof |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10057880B2 (en) * | 2016-12-11 | 2018-08-21 | Qualcomm Incorporated | Smart notifications between devices |
CN110063077A (en) * | 2016-12-11 | 2019-07-26 | 高通股份有限公司 | Intelligent Notification between devices |
Also Published As
Publication number | Publication date |
---|---|
TWI532359B (en) | 2016-05-01 |
TW201328309A (en) | 2013-07-01 |
CN103220404A (en) | 2013-07-24 |
US8892088B2 (en) | 2014-11-18 |
US20130157631A1 (en) | 2013-06-20 |
CN103220404B (en) | 2017-05-03 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8892088B2 (en) | Systems and methods for handling incoming calls on a media device | |
CA2740581C (en) | System and method for resuming media | |
AU2013204054B2 (en) | Communication service management system and operation method for the same | |
US20220232466A1 (en) | Method for Accessing Wireless Local Area Network and Terminal | |
WO2019090726A1 (en) | Method for selecting bluetooth device, terminal, and system | |
AU2020423946B2 (en) | Audio output method and terminal device | |
CN108184164A (en) | Audio frequency playing method, smart television and computer readable storage medium | |
JP2016518744A (en) | Handling multiple voice calls on multiple SIM mobile phones | |
US20220159453A1 (en) | Method for Using Remote SIM Module and Electronic Device | |
US11968058B2 (en) | Method for adding smart home device to contacts and system | |
AU2012376879B2 (en) | Method for managing calls and mobile terminal using the same | |
US20150105056A1 (en) | Methods and devices for establishing call | |
CN104793991B (en) | A kind of audio output apparatus switching method and device | |
CN115190197B (en) | Bluetooth headset-based communication method and device and storage medium | |
CN110945467B (en) | Disturbance-free method and terminal | |
CN106101456A (en) | A kind of method and device of call contact | |
US20160365021A1 (en) | Mobile device with low-emission mode | |
US9674686B2 (en) | Apparatus and method for pairing mobile devices | |
CN106453032A (en) | Information pushing method, device and system | |
KR20120023264A (en) | Method and apparatus for operating call function of portable terminal | |
CN105357388A (en) | Information recommending method and electronic equipment | |
CN105630286B (en) | Icon arrangement method and device | |
US20090240842A1 (en) | Portable electronic apparatus | |
WO2019011270A1 (en) | Method and terminal for playing audio, and computer-readable storage medium | |
WO2023236646A1 (en) | Incoming call display method and electronic devices |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: HTC CORPORATION, TAIWAN Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:WANG, HUAIYUAN;WILLIAMS, RODNEY OWEN;REEL/FRAME:034048/0393 Effective date: 20111212 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |