WO2013003035A1

WO2013003035A1 - A method and communication device for determining a callback time

Info

Publication number: WO2013003035A1
Application number: PCT/US2012/042128
Authority: WO
Inventors: Gauri Shrikant DESHPANDE; Krishnan Raghavan
Original assignee: Motorola Mobility LLC
Current assignee: Motorola Mobility LLC
Priority date: 2011-06-29
Filing date: 2012-06-13
Publication date: 2013-01-03
Anticipated expiration: 2013-12-29

Abstract

A method for determining a callback time for a third mobile phone when the first mobile phone (102) is engaged in a first call with a second mobile phone (104). The method includes detecting a second call from the third mobile phone (106)while the first mobile phone is engaged in the first call with the second mobile phone (304). Next, the method generates the callback time for the third mobile phone based upon at least one of a first context information associated with the first mobile phone or a second context information associated with the second mobile phone (308) or the called party can reject the call manually and give a callback time (418, 524). This callback time is then transmitted to the third mobile phone while the first mobile phone remains engaged on the first call with the second mobile phone (310).

Description

A Method and Communication Device For Determining a Callback Time

FIELD OF THE DISCLOSURE

[0001] The present disclosure relates generally to a communication device and more particularly to a method and apparatus for determining a callback time at the communication device.

BACKGROUND

[0002] In the present systems, when a calling party calls a called party who is busy attending another conversation, there is no way for the calling party to know when the called party will become available. The calling party may attempt to call the called party at some random intervals without knowing how long the called party will be busy and, thus, the calling party keeps wasting his/her time. The calling party does not know when he/she can call the called party again. This might be annoying for the called party as well, who keeps getting repeated beeps of an incoming call.

[0003] Accordingly, there is a need for a method and apparatus for determining a callback time for a calling party.

BRIEF DESCRIPTION OF THE FIGURES

[0004] The accompanying figures, where like reference numerals refer to identical or functionally similar elements throughout the separate views, together with the detailed description below, are incorporated in and form part of the specification, and serve to further illustrate embodiments of concepts that include the claimed invention, and explain various principles and advantages of those embodiments.

[0005] FIG. 1 is a schematic of a wireless communication system in accordance with some embodiments of the present invention.

[0006] FIG. 2 is a block diagram of an electronic device or a server in accordance with some embodiments of the present invention. [0007] FIG. 3 is a flowchart of a method in accordance with some embodiments of the present invention.

[0008] FIG. 4 is a signal flow diagram in accordance with some embodiments of the present invention.

[0009] FIG. 5 is a signal flow diagram in accordance with some embodiments of the resent invention.

[0010] Skilled artisans will appreciate that elements in the figures are illustrated for simplicity and clarity and have not necessarily been drawn to scale. For example, the dimensions of some of the elements in the figures may be exaggerated relative to other elements to help to improve understanding of embodiments of the present invention.

[0011] The apparatus and method components have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments of the present invention so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.

Detailed Description

[0012] Before describing in detail the particular method and system for determining a callback time at a communication device, in accordance with an embodiment of the present disclosure, it should be observed that the present disclosure resides primarily in combinations of method steps and apparatus components related to the method and system for determining a callback time for a third device when a first device is engaged in a first call with a second device. Accordingly, the apparatus components and method steps have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to

understanding the present disclosure, so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art, having the benefit of the description herein.

[0013] A first device and method for determining a callback time for a third device when the first device is engaged in a first call with a second device are disclosed herewith. The method includes detecting a second call from the third device while the first device is engaged in the first call with the second device. Next, the method generates the callback time for the third device based upon at least one of a first context information associated with the first device or a second context information associated with the second device. The method further transmits the generated callback time to the third device while the first device remains engaged on the first call with the second device.

[0014] FIG. 1 illustrates a schematic of a wireless communication system 100 in accordance with some embodiments. The wireless communication system 100 includes one or more electronic devices 102, 104, 106 communicating with infrastructure 126. The infrastructure 126 may include one or more base stations 108 and an infrastructure entity 110 communicating with the base station 108 via wireless or wired link 124 (for example, landline connections such as fiber optic or copper wiring connections, microwave communications, radio channel communications, and/or wireless path communications) depending upon the embodiment or device that is involved. Herein, the infrastructure entity 108 is one part of the entire infrastructure 126 and may include a server 112, a transceiver 114, and a database 116.

[0015] In accordance with the embodiment, the base station 108 in the wireless communication system 100 is configured to operate according to any of a number of different communication technologies including, but not limited to, 2G, 3G and 4G wireless communication technologies. These include Global System for Mobile Communication (GSM), Code Division for Multiple Access (CDMA), Universal Mobile Telecommunication System (UMTS), Wideband Code Division for Multiple Access (W-CDMA), Orthogonal Frequency Division Multiplexing (OFDM),

Worldwide Interoperability for Microwave Access (WiMax), Long-Term Evolution (LTE) and other communication technologies. The base station 108 communicates with the electronic devices 102-106 via the wireless or wired links 118, 120, 122 (for example, landline connections such as fiber optic or copper wiring connections, microwave communications, radio channel communications, and/or wireless path communications) depending upon the embodiment or device that is involved.

[0016] Still referring to Fig. 1, an electronic device 102-106 is intended to be representative of any of a variety of wireless communication devices operated by persons (or users) or possibly by other entities (e.g., other computers) desiring or requiring communication capabilities. In some embodiments, for example, the electronic device 102-106 can be any of a call receiver, cellular telephone, a personal digital assistant (PDAs), a smart phone, another handheld or portable electronic device, a headset, a MP3 player, a battery-powered device, a wearable device, a radio, a navigation device, a laptop or notebook computer, a notebook, a pager, a PMP (personal media player), a DVR (digital video recorder), a gaming device, a camera, a notebook, an e-reader, an e-book, a tablet device, a navigation device with a video capable screen, a multimedia docking station, or another mobile. The electronic device 102-106 may be served by the base station 108.

[0017] The infrastructure entity 110 is a network element that is connected to the various other elements in the wireless communication system 100. For example, the infrastructure entity 110 is connected to the electronic devices 102-106 through the base station 108 serving the electronic devices 102-106. The infrastructure entity 110 routes the communications to electronic devices 102-106 via base station 108 or via a PSTN/Internet/other network elements. The infrastructure entity 110 includes the server 112, the transceiver 114, and the database 116. The server 112 is a network element that communicates either directly or via other network elements to the base station 108. The server may include a transceiver component and/or a database component, or the server may communicate with a transceiver 114 and/or database 116 of the infrastructure entity 110. The server 112 is also intended to be

representative of any computerized device or terminal (or several of these) with which the electronic devices 102-106 and the base station 108 are capable of communicating, for the purpose of receiving or transmitting information.

[0018] The transceiver unit 114 can be implemented as a transmitting and receiving component of the infrastructure entity 110. The transceiver 114 enables the

infrastructure entity 110 to transmit and receive the RF signals through an antenna (not shown). As mentioned before, the transceiver 114 may be a part of the server 112 and not necessarily a separate element in the infrastructure entity 110. The database 116 stores the information and data related to the electronic devices 102-106 connected to the infrastructure entity 110 and various other data required by the server 112. Also, the database 116 may be a part of server 112 and not necessarily a separate element in the infrastructure entity 110.

[0019] Further, it is to be understood that FIG. 1 is provided merely for the purpose of illustrating the principles of the present invention. FIG. 1 is not intended to be a comprehensive schematic diagram of all of the components of such a communication system. Therefore, wireless communication system 100 may comprise various other configurations and still be within the scope of the present disclosure.

[0020] Referring to FIG. 2, there is provided a block diagram 200 illustrating example internal hardware components of the electronic device 102-106 and/or a server 112 of the infrastructure entity 110 of FIG. 1. For the purposes of the explanation below, the block diagram 200 will be referred to as describing internal hardware components of a communication device 202. Herein, the communication device 202 refers to electronic device 102-106 and/or the server 112.

[0021] The block diagram 200 of the communication device 202 includes various components. The exemplary components include a transceiver 204, an output device 206 including a display 208 and a speaker 210, a processor 212, a user interface 214, a memory 216, and a power supply 218 each capable of communicating with one or more components of the communication device 202. For example, as shown in FIG. 2, all components are coupled to a bidirectional system bus 220.

[0022] In accordance with an embodiment, the transceiver unit 204 can be

implemented as a transmitting and receiving component of the communication device 202. The transceiver 204 enables the communication device 202 to transmit and receive the RF signals through an antenna (not shown). In accordance with the embodiment, the transceiver 204 converts the RF signals received from the antenna to digital data for use by the processor 212.

[0023] The output device 206 may generate visual indications of data generated during operation of the processor 212. The visual indications may include prompts for human operator input, calculated values, detected data, etc. Additionally, the output device 206 may include a video output component such as a display device 208 which includes cathode ray tube, liquid crystal display, plasma display, incandescent light, fluorescent light, front or rear projection display, and light emitting diode indicator. Other examples of output components 206 include an audio output component such as a speaker 210, alarm and/or buzzer, and/or a mechanical output component such as vibrating or motion-based.

[0024] In accordance with an embodiment, the user interface 214 may be connected to the processor 212 for entering data and commands in the form of text, touch input, gestures, etc. The user interface 214 is, in one embodiment, a touch screen device but may alternatively be an infrared proximity detector or any input/output device combination capable of sensing gestures and/or touch including a touch-sensitive surface. In addition, the user interface 214 may include one or more additional components, such as a video input component such as an optical sensor (for example, a camera), an audio input component such as a microphone, and a mechanical input component such as button or key selection sensors, touch pad sensor, another touch- sensitive sensor, capacitive sensor, motion sensor, and may include a pointing device such as a joystick and buttons used on laptop or notebook computers, a track ball, a touch pad, a rocker switch, a touch screen, a TTY input device for disable persons, a Braille key input, or a pad for handwriting pen, for example. The user interface 214 enables a user of the communication device 202 to provide an input for the communication device 202.

[0025] Still referring to FIG. 2, the memory 216 may be used to store data and instructions for the operation of the processor 212. In the various embodiments, the memory 216 may be one or more separate components and/or may be partitioned in various ways for various purposes such as but not limited to, optimizing memory allocations, etc. Thus it is to be understood that the exemplary memory 216 illustrated in FIG.1 are for illustrative purposes only, for the purpose of explaining and assisting one of ordinary skill in understanding the various embodiments described herein.

[0026] Further, the power supply 218, such as a battery, may be included in the internal components of the communication device 202 for providing power to the other internal components while enabling the communication device 202 to be portable.

[0027] Further, the processor 212 operates in conjunction with the data and instructions stored in the memory 216 to control the operation of the communication device 202. The processor 212 may be implemented as a microcontroller, a digital signal processor, hard-wired logic and analog circuitry, or any suitable combination of these.

[0028] It is to be understood that FIG. 2 is for illustrative purposes only and is primarily for, although not solely for, explaining the information stored in memory for the various embodiments of an electronic device in accordance with the present disclosure, and is not intended to be a complete schematic diagram of the various components and connections there between required for an electronic device.

Therefore, a communication device will comprise various other components not shown in FIG. 2, and/or have various other configurations internal and external, and still be within the scope of the present disclosure. Also, one or more of these components may be combined or integrated in a common component, or components features may be distributed among multiple components. Also, the components of the communication device 202 may be connected differently, without departing from the scope of the invention.

[0029] Finally, as mentioned above, FIG. 2 can also be considered to be equally or substantially equally representative of the internal components of one or more electronic devices 102-106 and/or server 112.

[0030] FIG. 3 is a flowchart for a method 300 for determining a callback time for a third device when a first device is engaged in a first call with a second device. For example, electronic device 106 may be provided a callback time, when electronic device 104 is engaged in a first call with electronic device 102. Referring to FIG. 3, the method 300 starts at step 302. In accordance with an embodiment, the first device 104 is engaged 302 in a first call with a second device 102. In one example, the first device 104 receives the first call from the second device 102. For another example, the second device 102 receives the first call from the first device 104. The method 300 then moves to a step of detecting 304 a second call from a third device 106 while the first device 104 is engaged in the first call with the second device 102. In other words, the first device 104 while being busy on an ongoing call with the second device 102, may receive another call from the third device 106. In accordance with an

embodiment, the processor 212 may detect the second call from the third device 106 while is first device 104 is busy on another call with the second device 102.

[0031] The method 300 then advances to a step of determining 306 a first context information associated with the first device 104 and a second context information associated with the second device 102. The first context information may include at least one of a time, location, activity, behavior, calendar event or historical log associated with the first device 104. For example, the time parameter of the first context information may include an indication of a weekday, weekend, or a holiday, time of the day, whether the user is on vacation, etc. Further, the location parameter of the first context information may include whether the use of the first device 104 takes longer calls with a particular person when the user is at home compared to when the user is at work, whether the user is in silence zone, etc. Additionally, the first context information may include user's current activity, for example, if the user is running or if the user will be sleeping after a predetermine time (such as, thirty minutes), lunch time, ambient noise, accessories used, device's behavior of accepting or rejecting calls, history of earlier calls, etc. Various other examples could be included herein.

[0032] Similarly, the second context information further includes receiving at least one of a time, location, activity, and behavior, calendar event or historical log associated with the second device 102. The second context information may include further examples as illustrated above for the first context information. In one embodiment, the transceiver 204 receives the first context information from the first device 104 and the second context information from the second device 102. In accordance with an embodiment, the second context information may include a call duration value which is indicative of the estimated call duration of the first call as estimated by a user of the second device 102. The second device 102 when initiating a first call with the first device 104 may transmit a message comprising the call duration value to the first device 104. In another example, the second device 102 may initiate the first call with the information about the call duration.

[0033] The method 300 may then generate 308 the callback time for the third device 106 based on the first context information or the second context information. The callback time may be indicative of an estimated time period within which the first call is expected to terminate. In one embodiment, the method 300 generates the callback time based upon the second context information received from the second device 102. Next, the transceiver 204 may transmit 310 the generated callback time to the third device 106 while the first device 104 remains engaged on the first call with the second device 102.

[0034] Further, the generated 308 callback time may be stored in a memory 216 of the communication device 202. In one example, the second call received from the third device 106 may be auto-answered by playing the generated callback time as audio by the speaker 210 of the communication device 202, to the third device 106. In another example, the generated callback time is transmitted in a call reject message comprising a user-user information element, such as those known in the 3 GPP standards.

[0035] In accordance with the embodiment, the generated 308 callback time may be overridden by a user input at a user interface 214 before transmitting 310 the generated callback time to the third device 106. In other words, the user of the first device 104 or the second device 102 may override the callback time if needed or required so that it is closer to being accurate. Either user, currently engaged in the call can influence this callback time value.

[0036] The method 300 then moves to a step 312 where the processor 212 may determine if the generated 308 callback time has been expired. If the callback time has been expired, the processor 212 may then determine 314 if the first call has been terminated. In case the first call has been terminated, the first device 104 may automatically 316 receive a third call from the third device 106. In another embodiment, the third device 106 may configure to just remember or not call at all.

[0037] On the other hand, if it is determined 314 that the first call has not been terminated after the callback time has been expired, a new estimated callback time may be manually 318 entered by a user input at the user interface 214. The new callback time is then transmitted by the transceiver 204 to the third device 106. The third device 106 may or may not call back after the new estimated callback time is elapsed.

[0038] Therefore, when a first device 104 is busy on a first call with the second device 102 and the first device 104 receives a second call from the third device 106, callback time which may be indicative of an approximate call duration in which the first call is expected to terminate can be transmitted to the third device 106 indicating when to callback. This helps a user of the third device 106 to know when the user of the first device 104 is expected to be available. By doing so, the user of the third device 106 may not have to keep trying calling the user of the first device 104 at random intervals and thus waste time. The user of the third device 106 may call based upon the received call duration value from the first device 104.

[0039] FIG. 4 is a signal flow diagram 400 in accordance with some embodiments of the present invention. The signal flow diagram 400 illustrates communication steps among three or more users, for example, User A 402, User B 404, and User C 406. The signal flow diagram 400 begins when the User B 404 initiates 408 a call to the User A 402. In the alternative, User A 402 may initiate a call with User B. While initiating the call with the other user, such as User B 404 initiating a call to the User A 402, the User B may transmit a message to the User A 402 indicating an approximate call duration value of the initiated call. The approximate call duration may be indicative of the estimated call duration of the call initiated by the User B 404 and as predicted by the User B 404. On receiving the approximate call duration value from the User B 404, the User A 402 may store 410 the received approximate call duration value in a memory of a communication device associated with the User A 402. Then, there is an ongoing call 412 between the User A 402 and the User B 404.

[0040] While the User A 402 is engaged in the ongoing 412 call with the User B 404, User A 402 may receive 414 a new call from the User C 406. Since the User A 402 is busy on the call received from the User B 404, the User A 402 may reject 416 the call received from the User C 406. The User A 402 may then transmit 418 a call reject message with a callback time to the User C 406. The callback time may be determined at the User A 402 after subtracting the elapsed duration of the ongoing call with the User B 404, when the new call from the User C 406 arrives, from the call duration value received from the User B 404. The callback time may be indicative of an estimated time period within which the ongoing call 412 is expected to terminate. The User C 406 may then automatically call back 420 after the callback time is elapsed. In another embodiment, the User C 406 may configure to just remember or not call at all.

[0041] FIG. 5 is a signal flow diagram 500 in accordance with some embodiments of the present invention. The signal flow diagram 500 illustrates communication steps between a server 502 and at least three users, for example, User A 504, User B 506, and User C 508. The signal flow diagram 500 begins when the User B 506 initiates 512 a call to the User A 504, or vice-versa, via the server 502. The server 502 upon receiving a request for initiating 510 a call with the User, such as User A 504, the server may initiate 512 the call between the User A 504 and the User B 506. While initiating the call to the User A 504, the User B 506, may transmit a message to the server 502 indicating an approximate call duration value of the initiated call. The approximate call duration may be indicative of the estimated call duration of the call initiated by the User B 506 and as predicted by the User B 506. On receiving the approximate call duration value from the User B 506, the server 502 may store 514 the received approximate call duration value in a memory associated with the server 502. Then, there is an ongoing call 516 between the User A 504 and the User B 506.

[0042] While the User A 504 is engaged in the ongoing 516 call with the User B 506, the server 502 may receive 518 a request for a new call with the User A 504 from the User C 508. On receiving 518 the call request from the User C 508, the server 502 determines 520 that the User A 504 is busy on the ongoing call 516 with the User B 506. Since the User A 504 is busy on the call received from the User B 506, the server 502 may reject 522 the call received from the User C 508. The server 502 may then transmit 524 a call reject message with a callback time to the User C 508. The callback time may be determined at the server 502 after subtracting the elapsed duration of the ongoing call between the User A 504 and the User B 506, when the new call from the User C 508 arrives, from the call duration value received from the User B 506. The callback time may be indicative of an estimated time period within which the ongoing call 516 is expected to terminate. In one embodiment, the callback time is transmitted in a user-user information element, such as those known in 3 GPP standards. In another embodiment, when the User C 508 is a Public Switch Telephone Network (PSTN) user, the request for call from the User C 508 is auto-answered by reading out the callback time value.

[0043] The User C 508 may then initiate call 528 after the callback time. In case the server 502 receives the request for initiating 526 call from the User C 508, the server 502 may initiate 528 the call with the User A 504. In another embodiment, the User C 406 may configure to just remember or not call at all. [0044] Therefore, using the embodiments of the present invention, a caller can know when the called user who is busy attending another call is expected to be available so that the caller need not keep checking and wasting time. The caller can then decide whether to call at suggested time, seek other ways to get information or reach the called user via alternate means in case of emergency.

[0045] In the foregoing specification, specific embodiments have been described. However, one of ordinary skill in the art appreciates that various modifications and changes can be made without departing from the scope of the invention as set forth in the claims below. Accordingly, the specification and figures are to be regarded in an illustrative rather than a restrictive sense, and all such modifications are intended to be included within the scope of present teachings.

[0046] The benefits, advantages, solutions to problems, and any element(s) that may cause any benefit, advantage, or solution to occur or become more pronounced are not to be construed as a critical, required, or essential features or elements of any or all the claims. The invention is defined solely by the appended claims including any amendments made during the pendency of this application and all equivalents of those claims as issued.

[0047] Moreover in this document, relational terms such as first and second, top and bottom, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. The terms "comprises," "comprising," "has", "having," "includes", "including," "contains", "containing" or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises, has, includes, contains a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. An element proceeded by "comprises ...a", "has ...a", "includes ...a", "contains ...a" does not, without more constraints, preclude the existence of additional identical elements in the process, method, article, or apparatus that comprises, has, includes, and/or contains the element. The terms "a" and "an" are defined as one or more unless explicitly stated otherwise herein. The terms "substantially", "essentially",

"approximately", "about" or any other version thereof, are defined as being close to as understood by one of ordinary skill in the art, and in one non-limiting embodiment the term is defined to be within 10%, in another embodiment within 5%, in another embodiment within 1% and in another embodiment within 0.5%. The term "coupled" as used herein is defined as connected, although not necessarily directly and not necessarily mechanically. A device or structure that is "configured" in a certain way is configured in at least that way, but may also be configured in ways that are not listed.

[0048] It will be appreciated that some embodiments may be comprised of one or more generic or specialized processors (or "processing devices") such as

microprocessors, digital signal processors, customized processors and field programmable gate arrays (FPGAs) and unique stored program instructions (including both software and firmware) that control the one or more processors to implement, in conjunction with certain non-processor circuits, some, most, or all of the functions of the method and/or apparatus described herein. Alternatively, some or all functions could be implemented by a state machine that has no stored program instructions, or in one or more application specific integrated circuits (ASICs), in which each function or some combinations of certain of the functions are implemented as custom logic. Of course, a combination of the two approaches could be used.

[0049] Moreover, an embodiment can be implemented as a computer-readable storage medium having computer readable code stored thereon for programming a computer (e.g., comprising a processor) to perform a method as described and claimed herein. Examples of such computer-readable storage mediums include, but are not limited to, a hard disk, a CD-ROM, an optical storage device, a magnetic storage device, a ROM (Read Only Memory), a PROM (Programmable Read Only Memory), an EPROM (Erasable Programmable Read Only Memory), an EEPROM (Electrically Erasable Programmable Read Only Memory) and a Flash memory. Further, it is expected that one of ordinary skill, notwithstanding possibly significant effort and many design choices motivated by, for example, available time, current technology, and economic considerations, when guided by the concepts and principles disclosed herein will be readily capable of generating such software instructions and programs and ICs with minimal experimentation.

[0050] The Abstract of the Disclosure is provided to allow the reader to quickly ascertain the nature of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the foregoing Detailed Description, it can be seen that various features are grouped together in various embodiments for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Thus the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separately claimed subject matter.

Claims

We Claim:

1. A method for determining a callback time for a third device when a first device is engaged in a first call with a second device, the method comprising:

detecting a second call from the third device while the first device is engaged in the first call with the second device;

generating the callback time for the third device based upon at least one of a first context information associated with the first device or a second context information associated with the second device; and

transmitting the generated callback time to the third device while the first device remains engaged on the first call with the second device.

2. The method of claim 1, wherein the callback time is indicative of an estimated time period within which the first call is expected to terminate.

3. The method of claim 1, further comprising:

receiving the first call from the second device; and

receiving the second context information including a call duration from the second device, wherein the call duration is indicative of the estimated call duration of the first call.

4. The method of claim 3, wherein the first device automatically receives a third call from the third device after the callback time is elapsed.

5. The method of claim 1, wherein the first context information includes at least one of a time, location, activity, behavior, calendar event or historical log associated with the first device.

6. The method of claim 3, wherein receiving the second context information further includes receiving at least one of a time, location, activity, and behavior, calendar event or historical log associated with the second device.

7. The method of claim 1, further comprising:

overriding the generated callback time by a user input at a user interface of the first device before transmitting the generated callback time to the third device.

8. The method of claim 1, further comprising:

storing the generated callback time at an infrastructure entity; and auto-answering the second call received from the third device by the infrastructure entity, wherein the auto-answering includes playing the generated callback time as audio to the third device.

9. The method of claim 1 , wherein transmitting the generated callback time to the third device further comprising:

transmitting the generated callback time to the third device in a call reject message comprising a user-user information element.

10. A method for determining a callback time for a third device when a first device is engaged in a first call with a second device, the method comprising:

receiving the first call from the second device;

receiving a context information including a call duration from the second device, wherein the call duration is indicative of the estimated call duration of the first call;

generating the callback time for the third device based on the context information received from the second device; and

transmitting the generated callback time to the third device while the first device remains engaged on the first call with the second device, wherein the callback time is indicative of an estimated time period within which the first call is expected to terminate.

11. The method of claim 10, wherein receiving the context information from the second device further includes receiving at least one of a time, location, activity, and behavior, calendar event or historical log associated with the second device.

12. A method for determining a callback time for a third device when a first device is engaged in a first call with a second device, the method comprising:

generating a callback time for the third device based upon at least one of first context information associated with the first device and a second context information associated with the second device;

overriding the generated callback time by a user input at a user interface of the first device; and

transmitting the overridden generated callback time to the third device while the first device remains engaged on the first call with the second device.

13. The method of claim 12, further comprising:

receiving the first call from the second device; and

receiving the second context information, including a call duration from the second device, wherein the call duration is indicative of the estimated call duration of the first call.

14. The method of claim 13, wherein:

generating a callback time for the third device includes generating the callback time based, at least in part, on the context information received from the second device.

15. A communication device for determining a callback time for a second device when the communication device is engaged in a first call with a first device, the communication device comprising:

a transceiver configured to receive the first call from the first device and detect a second call from the second device while the communication device is engaged on the first call with the first device;

a processor configured to generate a callback time for the second device based upon at least one of a first context information associated with the communication device or a second context information associated with the first device; and

the transceiver further configured to transmit the generated callback time to the second device while the communication device remains engaged on the first call with the first device.

16. The communication device of claim 15, wherein the callback time is indicative of an estimated time period within which the first call is expected to terminate.

17. The communication device of claim 15, wherein the transceiver is configured to transmit the generated callback time to an infrastructure entity.

18. The communication device of claim 15, further comprising:

a user interface configured to display a user prompt, wherein the user prompt provides for entry of a new callback time; and

a memory configured to store the new callback time.

19. The communication device of claim 18, wherein the transceiver is configured to transmit the new callback time to the second device.