WO2008100673A1

WO2008100673A1 - Method and system for communicating call intents

Info

Publication number: WO2008100673A1
Application number: PCT/US2008/051283
Authority: WO
Inventors: Subodh K. Sohi; Brett L. Lindsley
Original assignee: Motorola, Inc.
Priority date: 2007-02-14
Filing date: 2008-01-17
Publication date: 2008-08-21

Abstract

A method (200) and a communication device (400) for communicating call intents in a communication network are disclosed. The method includes selecting (204) an identifier of a second communication device from a phonebook on a first communication device. Further, the method includes selecting (206) one or more call intents from a list of call intents stored in an intent store on the first communication device. Furthermore, the method includes transferring (208) the one or more call intents from the first communication device to a received-intent store on second communication device over a first communication channel.

Description

METHOD AND SYSTEM FOR COMMUNICATING CALL INTENTS

FIELD OF THE INVENTION

[0001] The present invention relates in general to communication networks, and more specifically, to communicating call intents in a communication network.

BACKGROUND OF THE INVENTION

[0002] With increased use of communication devices such as, mobile phones, in a communication network, it is beneficial to provide services that enable automatic call handling in the communication devices. One of these services is transferring call intents from a calling communication device to a receiving communication device. Call intents enable a receiver of a call to be aware of the context of the call from a caller. Further, there can be multiple call intents associated with a single call. Typically, the caller can send the call intents best suited to his intention for calling the receiver, prior to placing the call. The call intents can be read by the receiver at the receiving communication device prior to answering the call. For example, Mike can send call intents such as, software products, hardware products, Personal Computer (PC) accessories and wireless mouse, before making a call to a computer support center. The call intents can be read by the computer support center prior to answering the call. Based on the intents sent by Mike, the computer support center can be prepared to answer Mike's call.

[0003] In a conventional call handling mechanism, a connection is established between the calling and receiving communication devices. Further, additional information such as, status message for transfer of call intents can be displayed at the i calling communication device during a call set-up. However, this additional information is limited to being displayed only at the calling device. Further, this additional information can not be used for further processing the call intents. Processing the call intents can include, for example, deleting the call intents and/or the corresponding caller identifier from the receiving communication device, after the call intents are read by the receiver. Further, processing can also include disconnecting the call in case of either invalid caller identifier and/or invalid call intents.

[0004] In another call handling mechanism, the receiver tries to predict a single call intent before answering the call. However, the receiver may predict the single call intent incorrectly. Hence, this mechanism has limitation in terms of prediction accuracy. Further, this limitation gets compounded when multiple call intents have to be transferred.

[0005] In light of the above, there is a need for a method and system for communicating call intents in a communication network which guarantees that the semantics used for the call intents will be understood by the receiving communication device. Further, the system should not require any new standards and should fit within the existing communication infrastructures.

BRIEF DESCRIPTION OF DRAWINGS

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

[0007] FIG. 1 illustrates an environment where various embodiments of the present invention can be practiced;

[0008] FIG. 2 is a flow diagram illustrating a method for communicating call intents in a communication network, in accordance with an embodiment of the present invention;

[0009] FIG. 3 illustrates a set-up for communicating call intents in a communication network, in accordance with an embodiment of the present invention; and

[0010] FIG. 4 illustrates an exemplary communication device, in accordance with an embodiment of the present invention.

[0011] 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 in improving an understanding of embodiments of the present invention.

DETAILED DESCRIPTION

[0012] For one embodiment, a method for communicating one or more call intents in a communication network is provided. The method includes selecting an identifier from a phonebook on a first communication device. The identifier is associated with a second communication device. Further, the method includes selecting the one or more call intents from a list of call intents in an intent store on the first communication device. Furthermore, the method includes transferring the one or more call intents from the first communication device to a received-intent store associated with the second communication device. The one or more call intents are transferred to the second communication device over a first communication channel.

[0013] For another embodiment, a communication device is provided. The communication device includes a phonebook for storing one or more identifiers of one or more communication devices. Further, the communication device includes a first transmitter for transmitting one or more call intents to a receiving communication device. The one or more call intents are transmitted to the receiving communication device over a first communication channel. Furthermore, the communication device includes a second transmitter for placing a call to the receiving communication device. The call is placed to the second communication device over a second communication channel.

[0014] Before describing in detail the particular method and system for communicating call intents in a communication network in accordance with various embodiments of the present invention, it should be observed that the present invention utilizes a combination of method steps and apparatus components related to the method and system for communicating call intents in a communication network. 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 for an understanding of the present invention so as not to obscure the disclosure with details that will be readily apparent to those with ordinary skill in the art having the benefit of the description herein.

[0015] In this document, the terms 'comprises,' 'comprising,' 'includes,' 'including,' or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, article, system or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, article, or apparatus. An element preceded by 'comprises ... a' does not, without more constraints, preclude the existence of additional identical elements in the process, article, system, or apparatus that comprises the element. The terms 'includes' and/or 'having', as used herein, are defined as comprising.

[0016] The term 'another,' as used in this document, is defined as at least a second or more. The term 'includes' as used herein, are defined as comprising.

[0017] FIG. 1 illustrates an environment 100 where various embodiments of the present invention can be practiced. The environment 100 can include a first communication device 102 and a second communication device 104. Examples of the first communication device 102 and the second communication device 104 can include, but are not limited to, mobile phones, Personal Digital Assistants (PDAs) and smart phones. Further, the environment 100 includes a communication channel 106. Examples of the communication channel 106 can include, but are not limited to, the Internet and a mobile communication network. Although only the communication devices 104 and 106 have been shown in FIG.l, it will be apparent to a person ordinarily skilled in the art that the environment 100 can include more communication devices. [0018] For one embodiment, the first communication device 102 in the environment 100 can communicate with the second communication device 104 using the communication channel 106. A user operating the first communication device 102 can place a call to the second communication device 104. Further, the first communication device 102 can transfer one or more call intents to the second communication device 104. The one or more call intents transferred to the second communication device 104 can be recognized by the second communication device 104. Further, the one or more call intents can be processed by the second communication device 104. In this embodiment, the first communication device 102 can be referred to as a calling device. Further, the second communication device 104 can be referred to as a receiving device. Each of the communication devices 102 and 104 can act as either a calling device or a receiving device. However, for the sake of clarity, the present invention has been explained in conjunction with the first communication device 102 as the calling device, and the second communication device 104 as the receiving device in the following description.

[0019] FIG. 2 is a flow diagram illustrating a method 200 for communicating call intents in a communication network, in accordance with an embodiment of the present invention. At step 202, the method 200 can be initiated. At step 204, an identifier of a communication device, for example, the second communication device 104 can be selected from a phonebook on another communication device, for example, the first communication device 102. For an embodiment, the identifier can be, for example, a phone number of a communication device. The phonebook includes a list of call intents specific to a user of the first communication device 102 created by a user of the second communication device 104. For one embodiment, the user of the second communication device can customize the list of call intents specific to a user of the first communication device. The list of call intents can be stored and published in a published-intent store of the second communication device 104. The list of call intents can be added from the published-intent store on the second communication device 104 to an intent store in the first communication device 102. For example, the list of call intents can be obtained by an obtain-intent module of the first communication device 102 and stored in the intent store of the first communication device 102. For one embodiment, the published-intent store can be a Uniform Resource Locator (URL). In this embodiment, the obtain-intent module can obtain the list of call intents from the URL by using Electronic Numbering (ENUM) standards. ENUM maps a phone number of a communication device to a Domain Name Server (DNS) record. The DNS record can include a URL, possibly included in a VersitCard (vCard). The vCard is a file format standard for personal data interchange, for example electronic business cards. Further, vCards can include information, such as name and address information, phone numbers and URLs.

[0020] For another embodiment, HyperText Markup Language (HTML) methods can be used to transfer the list of call intents from the URL to the first communication device 102. For example, the HTML method 'GET' on the URL can return the list of call intents and the HTML method 'POST' on the URL can transfer the list of call intents. Thereafter, the list of call intents can be displayed in the phonebook of the first communication device 102. In another embodiment, for a user to access the list of call intents, some form of username and password may be provided. For one embodiment, the username/password can be used, for example, in Hypertext Transfer Protocol (HTTP) Basic authentication over a secure channel (HTTPS). [0021] At step 206, one or more call intents can be selected from the list of call intents stored in the intent store on the first communication device 102. The one or more call intents are selected from the list of call intents such that they specify the reason for a call from a user of the first communication device 102. At step 208, the one or more call intents selected from the first communication device 102 are transferred to a received-intent store at the second communication device 104. For one embodiment, the one or more call intents can be authenticated before being stored in the received-intent store of the second communication device 104. For another embodiment, the one or more call intents can be transferred to the received-intent store and then authenticated. Authentication can include, for example, confirming the validity of an identifier associated with the first communication device 102. Further, for one embodiment, the one or more call intents can be transferred to the received- intent store prior to placing a call from the first communication device 102 to the second communication device 104. This enables the one or more call intents to be read by a user at the second communication device 104 prior to receiving a call from the first communication device 102. For another embodiment, the one or more call intents can be transferred to the received-intent store while a call is being placed from the first communication device 102 to the second communication device 104. For yet another embodiment, the one or more call intents are transferred to the received-intent store after the first communication device 102 calls the second communication device 104. Furthermore, the one or more call intents can be transferred over a first communication channel, for example, the Internet. At step 210, the method 200 is terminated. [0022] FIG. 3 illustrates a set-up 300 for communicating call intents in a communication network, in accordance with an embodiment of the present invention. For one embodiment, the set-up 300 can include a first communication device 302, a second communication device 304, a first communication channel 306, a second communication channel 308 and a third communication channel 310. Examples of the first communication device 302 and the second communication device 304 include, but are not limited to, mobile phones, Personal Digital Assistants (PDAs) and smart phones. For one embodiment, the first communication device 302 can include an intent store 312, a phonebook 314, a first transmitter 316, a second transmitter 318 and an obtain-intent module 320. Further, the second communication device 304 can include a published-intent store 322, an authenticating module 324, a received-intent store 326, an intent association module 328 and a processor 330.

[0023] Further, the intent store 312 can store a list of call intents from the second communication device 304 for initiating a service, for example, communicating one or more call intents to the second communication device 304. For one embodiment, the list of call intents received from the second communication device 304 are specific to the first communication device 302. The list of call intents can be displayed in the phonebook 314 on the first communication device 302. One or more call intents that specify the purpose of communication of a user of the first communication device 302 with the second communication device 304 can be selected from the list of call intents. For one embodiment, the selected one or more call intents can be transmitted to the authenticating module 324 in the second communication device 304 over the first communication channel 306. The first communication channel 306 can be, for example, the Internet. A status signal can be sent by the second communication device 304 to the first communication device 302 on successful or unsuccessful transfer of the one or more call intents. Further, the identifier of the first communication device 302 can be authenticated and the one or more call intents can be stored in the received-intent store 326 in the second communication device 304. For another embodiment, the one or more call intents can be first stored in the received-intent store 326 and then the identifier can be authenticated. Further, unauthorized calls can be deleted along with the associated one or more call intents and the call can be disconnected.

[0024] Further, the identifier of the second communication device 304 can be looked up in the phonebook 314 on the first communication device 302. Furthermore, the second transmitter 318 can place a call to the second communication device 304 over the second communication channel 308. The second communication channel 308 can be, for example, a mobile communication network. For one embodiment, the intent association module 328 in the second communication device 304 can determine and authenticate the one or more call intents stored in the received-intent store 326 when the call is placed to the second communication device 304. For another embodiment, the intent association module 328 in the second communication device 304 can determine and authenticate the one or more call intents stored in the received-intent store 326 before the call is placed for the second communication device 304. For yet another embodiment, the intent association module 328 in the second communication device 304 can determine and authenticate the one or more call intents stored in the received-intent store 326 after the call is placed to the second communication device 304. Further, the intent association module 328 can retrieve the one or more call intents associated with the identifier of the first communication device 302. The one or more call intents retrieved from the received-intent store 326 can be processed by the processor 330. After processing, the one or more call intents can be read by the user of the second communication device 304.

[0025] For one embodiment, a signal can be generated after the one or more call intents are read at the second communication device 304. Thereby, the call and the one or more call intents can be processed. One or more functions can be implemented corresponding to each of the one or more call intents. The one or more functions can be, for example, deleting the one or more call intents and the identifier of the first communication device 302 from the received-intent store 326 after the one or more call intents have been processed. For another embodiment, when the one or more call intents are received from the first communication device 302 at different times, the one or more call intents received at previous times can be overwritten by the latest received call intents.

[0026] Further, a list of call intents can be specified by the second communication device 304. For one embodiment, the list of call intents can be specific to the first communication device 302. For another embodiment, the list of call intents can be same for all communication devices. The list of call intents can be published and stored in the published-intent store 322 of the second communication device 304. The obtain-intent module 320 can obtain the list of call intents in the first communication device 302 from the published-intent store 322 in the second communication device 304. The list of call intents can be received over the third communication channel 310. The third communication channel 310 can be, for example, the Internet. [0027] FIG. 4 illustrates an exemplary communication device 400, in accordance with an embodiment of the present invention. For an embodiment, the communication device 400 includes an obtain-intent module 402, an intent store 404, a first transmitter 406, a phonebook 408, a second transmitter 410, an authenticating module 412, a received-intent store 414, an intent association module 416, a processor 418 and a published-intent store 420. The communication device 400 can act as either a calling communication device or a receiving communication device. The obtain-intent module 402 obtains a list of call intents from a receiving communication device. The list of call intents can be transferred over the third communication channel 310. Further, the list of call intents is stored in an intent store 404 in the communication device 400. The list of call intents in the intent store 404 can be updated when changes are made to it in the receiving communication device. The phonebook 408 includes one or more identifiers of one or more communication devices. For one embodiment, the phonebook 408 includes the list of call intents specific to the communication device 400. For another embodiment, the phonebook 408 can be URL enhanced including information regarding the identifier of a communication device, call intent information associated with the communication device and an intent store associated with the communication device. Further, the one or more call intents to be sent to the receiving communication device can be selected from the list of call intents.

[0028] The first transmitter 406 transmits the one or more call intents to the receiving communication device over the first communication channel 306. An identifier of the receiving communication device can be selected from the phonebook 408 and a call can be placed to the receiving communication device by the second transmitter 410 over the second communication channel 308. The authenticating module 412 authenticates the identifier of the calling communication device and/or the one or more call intents associated with the identifier of the calling communication device. In case of an invalid identifier, no connection is established between the communicating devices. The received-intent store 414 stores the one or more call intents received at the receiving communication device from the calling communication device. For one embodiment, the received-intent store 414 can be a URL. The intent association module 416 determines the one or more call intents from the received-intent store 414. Further, the intent association module 416 authenticates the one or more call intents retrieved from the received-intent store 414. The one or more call intents and/or the call can be processed by the processor 418 after authentication. For one embodiment, processing the one or more call intents can include deleting the one or more call intents and the identifier of the first communication device when either the one or more call intents, the identifier and/or both are invalid. The published-intent store 420 publishes and stores the list of call intents. Further, the list of call intents in the published intent store 420 corresponding to one or more identifiers can be customized specific to the receiving communication device. For one embodiment, the published-intent store 420 can be a URL.

[0029] Various embodiments, as described above, provide a method and system for communicating one or more call intents in a communication network. The present invention uses the existing communication standards and communication infrastructure for implementation. Further, the present invention guarantees that the one or more call intents will be recognized by a receiving communication device since the list of call intents is customized by the receiving communication device. Consequently, the present invention prevents communication failure due to unrecognized call intents. Moreover, the present invention uses separate channels for transferring the call intents and for placing a call. This enables efficient transfer of call intents from a calling communication device to a receiving communication device. Furthermore, the system enables multiple call intents to be transferred in real time. Moreover, the system enables authentication of the caller ID and/or the call intents associated with the caller ID.

[0030] It will be appreciated that embodiments of the invention described herein may be comprised of one or more conventional processors and unique stored program instructions 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 embodiments of the invention described herein. The non-processor circuits may include, but are not limited to, a radio receiver, a radio transmitter, signal drivers, clock circuits, power source circuits, and user input devices. As such, these functions may be interpreted as steps of a method for communicating call intents. 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 these approaches could be used. Thus, methods and means for these functions have been described herein. In those situations for which functions of the embodiments of the invention can be implemented using a processor and stored program instructions, it will be appreciated that one means for implementing such functions is the media that stores the stored program instructions, be it magnetic storage or a signal conveying a file. 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 stored program instructions and ICs with minimal experimentation.

[0031] In the foregoing specification, the invention and its benefits and advantages have been described with reference to specific embodiments. However, one with ordinary skill in the art would appreciate that various modifications and changes can be made without departing from the scope of the present 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 the present invention. 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 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.

[0032] The Abstract of the Disclosure is provided to comply with 37 C.F.R. § 1.72(b), requiring an abstract that will 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 a single embodiment 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

WHAT IS CLAIMED IS:

1. A method for communicating one or more call intents in a communication network, the method comprising: selecting an identifier from a phonebook on a first communication device, wherein the identifier is associated with a second communication device; selecting the one or more call intents from a list of call intents in an intent store on the first communication device; and transferring the one or more call intents from the first communication device to a received-intent store associated with the second communication device, wherein the one or more call intents are transferred over a first communication channel.

2. The method as recited in claim 1 further comprising adding a list of call intents from a published-intent store on the second communication device to the intent store on the first communication device.

3. The method as recited in claim 2, wherein adding the list of call intents comprises using Electronic Numbering (ENUM) standards.

4. The method as recited in claim 2 further comprising customizing the list of call intents stored in the published-intent store on the second communication device, wherein the list of call intents is customized specific to the first communication device.

5. The method as recited in claim 1 further comprising authenticating the one or more call intents at the second communication device.

6. A communication device comprising: a phonebook for storing one or more identifiers of one or more communication devices; a first transmitter for transmitting one or more call intents to a receiving communication device over a first communication channel; and a second transmitter for placing a call to the receiving communication device over a second communication channel.

7. The communication device as recited in claim 6 further comprising an obtain- intent module for retrieving a list of call intents at the communication device from the receiving communication device over a third communication channel, wherein the list of call intents is specific to the communication device.

8. The communication device as recited in claim 7 further comprising an intent store for storing the list of call intents retrieved from receiving communication device.

9. The communication device as recited in claim 6 further comprising an authenticating module for authenticating one or more call intents, wherein the one or more call intents are received from a calling communication device.

0. The communication device as recited in claim 6 further comprising a processor for processing at least one of a call from a calling communication device and one or more call intents associated with the calling communication device.