throbber
(19) United States
`(12) Patent Application Publication (10) Pub. No.: US 2007/0036286 A1
`
`
` Champlin et al. (43) Pub. Date: Feb. 15, 2007
`
`US 20070036286A1
`
`(54) METHOD AND DEVICE FOR ENABLING
`MESSAGE RESPONSES TO INCOMING
`
`Publication Classification
`
`PHONE CALLS
`
`(76)
`
`Inventors: David Champlin, Menlo Park, CA
`(US); Srikiran Prasad, Cupertino, CA
`(US); Lang Chen, Oakland, CA (US);
`Rajan Ranga, Palo Alto; CA (US);
`Robert Haitani, Menlo Park, CA (US)
`
`Correspondence Address:
`SHEMWELL MAHAMEDI LLP
`4880 STEVENS CREEK BOULEVARD
`SUITE 201
`SAN JOSE, CA 95129 (US)
`
`(21) Appl. No.:
`
`11/200,511
`
`(22)
`
`Filed;
`
`Aug. 8, 2005
`
`(51)
`
`Int. Cl.
`(2006.01)
`H04M 1/64
`(52) US. Cl.
`............................................................ 379/671
`
`(57)
`
`ABSTRACT
`
`.
`.
`.
`.
`.
`.
`A computing deVice is configured to receive an incoming
`communication from another computing deVice. The incom-
`ing communication may be for purpose of initiating a
`voice-exchange session. In response to receiving the incom-
`ing call, the computing device may identify or determine a
`message identifier of the other computing device. The mes-
`sage identifier is determined based at least in part on data
`provided with the incoming communication. The computing
`device may programmatically address a message to the other
`computing device using the message identifier determined
`from the incoming communication.
`
`CALL
`DATA
`212
`
`I
`
`RESPONSE
`MODULE
`
`PHONE
`APPLICATION
`210
`
`INCOMING
`CALL
`
`204 MESSAGE
`250 MESSAGING
`MESSAGE COMPONENT
`
`MESS
`CREATION DATA
`222
`
`'
`
`CONTACT
`DATABASE
`
`230
`
`
`
`220
`
`'
`
`RESPONSE
`254
`
`,
`
`MESSAGE
`CONTENT
`242
`
`PROGRAMMATIC
`SOURCE
`244
`
`~
`
`USER
`202
`
`Qualcomm Exhibit 2021
`Apple v. Qualcomm, |PR2018—01279
`Page 1
`
`Qualcomm Exhibit 2021
`Apple v. Qualcomm, IPR2018-01279
`Page 1
`
`

`

`Patent Application Publication Feb. 15, 2007 Sheet 1 0f 4
`
`US 2007/0036286 A1
`
`
`INCOMING
`
`CALL
`OUTGOING
`
`
`MESSAGE
`
`
`RESPONSE
`
`
`
`MOBILE COMPUTING
`DEVICE
`110
`
`FIG. 1
`
`MOBILE COMPUTING
`DEVICE
`12
`0
`
`
`
`
`PHONE
`INCOMING
`
`APPLICATION
`CALL
`
`
`
`
`210
`204
`
`MESSAGE
`RESPONSE
`MODULE
`
`
`
`
`
` MESSAGE
`MESSAGING
`
`
`RESPONSE
`COMPONENT
`
`
`
`254
`
`
`
`
`MESSAGE
`
`
`CONTACT _
`
`CONTENT
`
`DATABASE
`
`242
`
`230
`
`
`
`
`
`
`
`PROGRAMMATIC
`SOURCE
`244
`
`-
`
`
`
`
`
`USER
`202
`
`FIG. 2
`
`Qualcomm Exhibit 2021
`Apple v. Qualcomm, |PR2018—01279
`Page 2
`
`Qualcomm Exhibit 2021
`Apple v. Qualcomm, IPR2018-01279
`Page 2
`
`

`

` 354
`
`
`
`
`CONTACT INFO
`324
`
`PHONE!
`MESSAGE
`
`
`DATA
`
`
`
`DISPLAY
`
`332
`
`
`APPLICATION
`
`PROCESSOR(S)
`
`330
`31o
`INSTRUCT
`
`
`
`322
`
`MESSAGE
`
`INPUT
`
`Patent Application Publication Feb. 15, 2007 Sheet 2 0f 4
`
`US 2007/0036286 A1
`
`VOICE DATA
`362
`
`MESSAGE
`
` COMPUTING DEVICE
`
`
`COMMUNICATION
`300
`COMPONENTS
`
`
`318
`
`
`
`
`MEMORY
`320
`
`342
`
`INPUT MECHANISMS
`34o
`
`
`
`
`
`
`
`
`
`
`
`FIG. 3
`
`Qualcomm Exhibit 2021
`Apple v. Qualcomm, |PR2018—01279
`Page 3
`
`Qualcomm Exhibit 2021
`Apple v. Qualcomm, IPR2018-01279
`Page 3
`
`

`

`Patent Application Publication Feb. 15, 2007 Sheet 3 0f 4
`
`US 2007/0036286 A1
`
`RECEIVE INCOMING CALL
`
`410
`
`IDENTIFY CALLER INFORMATION
`
`420
`
`PRESENT REPLY OPTIONS TO USER
`
`430
`
`440
` OTHER (IGNORE/
`
`REPLY)
`
`MESSAGE RESPONSE?
`
`435
`
`LAUNCH MESSAGING APPLICATION
`
`450
`
`ADDRESS MESSAGE TOCALLER USING
`CALLER INFORMATION
`
` _ 460
`
`ADDRESS MESSAGE BODY
`
`470
`
`'
`
`SEND MESSAGE
`
`480
`
`FIG. 4
`
`Qualcomm Exhibit 2021
`Apple v. Qualcomm, |PR2018—01279
`Page 4
`
`Qualcomm Exhibit 2021
`Apple v. Qualcomm, IPR2018-01279
`Page 4
`
`

`

`Patent Application Publication Feb. 15, 2007 Sheet 4 0f 4
`
`US 2007/0036286 A1
`
`IDENTIFY CALLER PHONE NUMBER
`
`510
`
`ACCESS CONTACT DATABASE TO DETERMINE IF
`
`
`
`
`
`
`CALLER NUMBER IS MESSAGE-ENABLED
`
`520
`
`
`NO MESSAGE
` MESSAGE ENABLED
`
`“:55"?
`OPTION
`
`
`
`
`I
`
`PROVIDE MESSAGE RESPONSE OPTION
`,
`54o
`
`RESPONSE
`
`
`
`530
`
`
`
`‘
`
`FIG. 5
`
`FIG. 6A
`
`CALL
`NOTIFICATION
`606
`
`CALL
`TERMINATION
`
`.
`
`610
`
`INCOMING
`CALL
`602
`
`sms;
`“Call Back Please”
`608
`
`CALL
`
`NOTIFICATION
`
`616
`
`-
`
`
`
`CALL
`PICK-UP
`
`
`s 5,
`'"COM'NG
`“Han orI-will
`CALL
`angwer"
`612
`618
`
`FIG. 63
`
`Qualcomm Exhibit 2021
`Apple v. Qualcomm, |PR2018—01279
`Page 5
`
`Qualcomm Exhibit 2021
`Apple v. Qualcomm, IPR2018-01279
`Page 5
`
`

`

`US 2007/0036286 A1
`
`Feb. 15, 2007
`
`METHOD AND DEVICE FOR ENABLING
`MESSAGE RESPONSES TO INCOMING PHONE
`CALLS
`
`TECHNICAL FIELD
`
`[0001] The disclosed embodiments relate generally to the
`field of messaging, and more particularly, to a method and
`apparatus for enabling message responses to incoming calls.
`
`BACKGROUND
`
`[0002] Communication devices have evolved to include
`numerous types of communication capabilities and function-
`ality. For example, handheld devices exist that operate as
`cellular phones, messaging terminals,
`Internet devices,
`while including personal information management (PIM)
`software and photo-management applications. Additionally,
`Internet Protocol services exist that can transform Intemet-
`
`enabled machines into telephony devices. Even stand-alone
`telephones that connect to traditional Public Switched Tele-
`phone Networks (PSTN) now carry software to assist the
`user in making and managing phone calls.
`
`[0003] Mobile phone networks have traditionally been
`limited to voice communications, but new technologies such
`as GSM (Global System for Mobile Communications) have
`enabled mobile phone networks to also include data com-
`munications. For example, SMS (Short Message Service)
`messaging provides a software-independent protocol to send
`short text messages composed of either: 160-7 bit charac-
`ters; 70-16 bit characters; or 140 octets of binary data.
`Individual SMS messages thus require a relatively small
`network bandwidth and devices can receive messages, even
`when connected to a voice call. The number of SMS
`
`messages a user receives has continually increased because
`many new types of network devices have joined mobile
`phone networks. These devices include, for example, PDAs,
`hybrid PDA/mobile phone devices, and other text messaging
`devices using GSM networks. Additionally, PSTN devices
`also exist that support messaging applications such as SMS.
`
`DESCRIPTION OF THE DRAWINGS
`
`[0004] FIG. 1 is a diagram illustrating a computing device
`issuing a message response to an incoming caller, according
`to one or more embodiments of the invention.
`
`[0005] FIG. 2 illustrates components for use in a comput-
`ing device configured according to an embodiment of the
`invention.
`
`[0006] FIG. 3 is a hardware diagram for use with one or
`more embodiments of the invention.
`
`[0007] FIG. 4 illustrates a message for handling incoming
`calls with message replies, under an embodiment of the
`invention.
`
`[0008] FIG. 5 illustrates an optional process that may be
`performed in order to determine or verify that a caller using
`a message-enabled device, under an embodiment of the
`invention.
`
`[0009] FIG. 6A and FIG. 6B illustrate timelines for dif-
`ferent usage scenarios, under one or more embodiments of
`the invention.
`
`DETAILED DESCRIPTION
`
`[0010] Embodiments described herein enable message
`replies to be made to incoming callers. In an embodiment, a
`device that receives an incoming phone call, for example,
`may be used to transmit a message as a reply to the caller.
`For example, rather than pick up a phone call or forward the
`phone call to voicemail, the user may simply generate a text
`(or other form of) message to the caller.
`
`[0011] Embodiments of the invention recognize that in
`some cases, a user answering or not answering a phone call
`is inconvenient, either to the recipient of the phone call, or
`the caller, As such, embodiments described herein provide
`an alternative of messaging the caller of an incoming phone
`call, rather answering the phone call or forwarding the phone
`call to voicemail.
`
`[0012] Embodiments described herein have particular
`application to mobile computing devices that offer voice and
`data capabilities on cellular networks.
`In this context,
`embodiments described herein allow the user of the device
`
`handling the incoming call to communicate with the caller
`without actually accepting the call. This can save both the
`caller and the recipient time, and “minutes” on their respec-
`tive cellular plans. Furthermore,
`if the recipient of the
`incoming call cannot accept the incoming call, the recipient
`is saved the trouble of having to respond to a voicemail
`message or having to find the time to return a call.
`
`[0013] While one or more embodiments of the invention
`are described for use with mobile, cellular devices, other
`telephony and computing devices are contemplated for use
`with embodiments of the invention. For example, some
`phones that connect to traditional wireline phone networks
`have capability to transmit and receive messages.
`
`In one embodiment, a computing device is config-
`[0014]
`ured to receive an incoming communication from another
`computing device. The incoming communication may be for
`purpose of initiating a voice-exchange session. In response
`to receiving the incoming call, the computing device may
`identify or determine a message identifier of the other
`computing device. The message identifier is determined
`based at least in part on data provided with the incoming
`communication. The computing device may programmati-
`cally address a message to the other computing device using
`the message identifier determined from the incoming com-
`munication.
`
`[0015] According to an embodiment, a computing device
`is configured to provide a message reply to an incoming
`phone call. In one embodiment, the computing device iden-
`tifies a phone number of a caller of the incoming call. The
`computing device may prompt the user of the computing
`device to generate a message reply to the incoming phone
`call. The computing device may then initiate the message
`reply by opening a message and addressing the message to
`the phone number of the caller of the incoming phone call.
`
`any data transfer
`[0016] A voice-exchange includes
`method in which a user’s speech or utterance is transmitted
`across a network to the location of another device or user in
`
`real-time (e.g. instantaneous) or near real-time (e.g. less than
`three seconds). Examples of voice-exchange includes stan-
`dard telephony practice. Another example of voice-ex-
`change is when a voice transmission is recorded and trans-
`mitted as an instant message or file to be received and played
`Qualcomm Exhibit 2021
`Apple v. Qualcomm, |PR2018—01279
`Page 6
`
`Qualcomm Exhibit 2021
`Apple v. Qualcomm, IPR2018-01279
`Page 6
`
`

`

`US 2007/0036286 A1
`
`Feb. 15, 2007
`
`back at the recipient. In the latter case, the recipient may not
`be able to interrupt the speaker, due to time delay, while in
`the former case, the recipient can interact with the speaker
`as if they were standing next to each other.
`
`the term “instant message” or
`[0017] As used herein,
`“instant messaging” means messages that when transmitted
`to a recipient, or rendered on a device of the recipient
`immediately, nearly immediately, or alternatively without
`user-action.
`
`[0018] Numerous types of computer telephony devices
`exist. One type of computer telephony device for use with an
`embodiment is a wireless, mobile computing device, some-
`times called the “smart phone”. Such devices are generally
`small to fit in one hand, and provide cellular telephony
`features in combination with other applications, such as
`contact applications for managing contact records, calendar
`applications for managing and scheduling events, task appli-
`cations for keeping lists, and camera applications for cap-
`turing images. Another type of computer telephony device
`contemplated with an embodiment is a desktop computer
`that is configured to include real-time voice data exchange
`(e.g. through use of Internet Protocol telephony). Still fur-
`ther, other types of computer telephony devices exist,
`including standalone devices that connect directly to a
`telephone network (whether Internet Protocol or Public
`Switch Telephony System) and provide software interfaces
`and applications.
`
`techniques
`[0019] Embodiments provide that methods,
`and actions performed by the communication device are
`performed programmatically, or as a computer-implemented
`method. Programmatically means through the use of code,
`or computer-executable instructions. A programmatically
`performed step may or may not be automatic.
`
`[0020] One or more embodiments described herein may be
`implemented using modules. A module may include a pro-
`gram, a subroutine, a portion of a program, or a software
`component or a hardware component capable of performing
`one or more stated tasks or functions. As used herein, a
`module can exist on a hardware component independently of
`other modules, or a module can be a shared element or
`process of other modules, programs or machines. A module
`may reside on one machine, such as on a client or on a
`server, or a module may be distributed amongst multiple
`machines, such as on multiple clients or server machines.
`
`[0021] Furthermore, one or more embodiments described
`herein may be implemented through the use of instructions
`that are executable by one or more processors. These
`instructions may be carried on a computer-readable medium.
`Machines shown in figures below provide examples of
`processing resources and computer-readable mediums on
`which instructions for implementing embodiments of the
`invention can be carried and/or executed. In particular, the
`numerous machines shown with embodiments of the inven-
`
`tion include processor(s) and various forms of memory for
`holding data and instructions. Examples of computer-read-
`able mediums include permanent memory storage devices,
`such as hard drives on personal computers or servers. Other
`examples of computer storage mediums include portable
`storage units, such as CD or DVD units, flash memory (such
`as carried on many cell phones and personal digital assis-
`tants (PDAs)), and magnetic memory. Computers, terminals,
`network enabled devices (e.g. mobile devices such as cell
`
`phones) are all examples of machines and devices that
`utilize processors, memory, and instructions stored on com-
`puter-readable mediums.
`
`FIG. 1 is a diagram illustrating a computing device
`[0022]
`issuing a message response to an incoming caller, according
`to one or more embodiments of the invention. In FIG. 1, an
`initiating computing device 120 (“calling device”) places a
`call 112 to a recipient computing device 110. Rather than
`answer the call or perform some other action like forwarding
`the call to voicemail, one or more embodiments described
`herein provide that
`the recipient computing device 110
`issues a message response 122 to the calling device 120. In
`one embodiment, the message response 122 is an alternative
`to the user of the recipient device 110 having to decline or
`not answer the incoming call 112.
`
`In an embodiment, the message response 122 is an
`[0023]
`instant message, meaning that the contents of the message
`are rendered immediately when received on the calling
`device 110. One implementation provides that a content of
`the message response is text. For example, the user of the
`receiving device 110 may insert or compose a text message
`(e.g. “Call me later”). A text message response may be
`provided using a Short Message Service (SMS) format and
`application. Other embodiments provide for other types of
`content data to be included in the message, including MMS
`(Multimedia Messaging Service), EMS (Enhanced Messag-
`ing Service), or any data protocol capable of encapsulating
`messages for transport between networked devices. Thus,
`one alternative implementation provides that the user may
`send an image that communicates information. For example,
`the user may send an image of a clock showing a particular
`time,
`indicating that user’s desire to be called back at a
`particular time. Still further, the user may include audio in
`the message response 122. For example, the user may send
`a voice blurb or a chime to indicate a message to the user of
`the caller device 120.
`
`FIG. 1 illustrates implementation of embodiments
`[0024]
`of the invention with cellular telephony devices, since such
`devices normally handle both message transmissions and/or
`receptions over cellular networks. However, there are tele-
`phones VoIP (voice-over IP) phones and phones that connect
`to Public Switched Telephony Networks (PSTN) that can
`handle messaging. For example, some PSTN phones may
`support SMS message handling. Thus, embodiments of the
`invention may extend to devices and networks other than
`those that are used on cellular networks.
`
`[0025] Furthermore, telephone calls are just one example
`of a voice-exchange session. Embodiments of the invention
`may be implemented in the context of other types of
`voice-exchange sessions. For example, caller device 120
`may initially communicate a walkie-talkie communication
`to the recipient device 110, for which recipient device 110
`sends back, for example, a text message response.
`
`[0026] Component Overview
`
`FIG. 2 illustrates components for use in a comput-
`[0027]
`ing device configured according to an embodiment of the
`invention. In FIG. 2, a computing device 200 includes a
`phone application 210 and a messaging component 220. A
`message response module 250 may be incorporated to
`operate in connection with both the phone application 210
`and the messaging component 220. According to an embodi-
`Qualcomm Exhibit 2021
`Apple v. Qualcomm, |PR2018—01279
`Page 7
`
`Qualcomm Exhibit 2021
`Apple v. Qualcomm, IPR2018-01279
`Page 7
`
`

`

`US 2007/0036286 A1
`
`Feb. 15, 2007
`
`ment, the message response module 250 triggers initiation of
`a message response 254 to the incoming call 204. In one
`implementation, computing device 200 corresponds to a
`hybrid mobile device having telephonic and messaging
`capability over cellular networks (sometimes called a “smart
`phone”). The phone application 210 may correspond to a
`software element that manages voice data exchanged over
`one or more wireless communication components 318 (see
`FIG. 3). In one embodiment, messaging component 220 is
`an instant messaging application.
`[0028] One example of a messaging application that is
`suitable for use with an embodiment is an SMS application,
`for sending and receiving text instant messages. Alternative
`instant text messaging applications may also be used. As
`another example, the messaging application 220 may cor-
`respond to a media-based messaging application, such as a
`Multimedia Messaging Service (MMS) application,
`for
`sending and receiving image data.
`[0029] With reference to FIG. 2, computing device 200
`may receive an incoming call 204, which is handled by the
`phone application 210. At an initial time, the incoming call
`204 may include call data 212, which is identified by the
`phone application 210. In one embodiment, call data 212
`includes identification information of the caller (e.g. “Caller
`ID” information). As such, call data 212 may include (i) a
`name of the caller, and/or (ii) a phone number used by the
`caller. The phone application 210 may identify call data 212
`from the incoming call 204 while causing transmission of
`audio rings/chimes, rendering of image data containing the
`Caller ID information on a display of the device, and/or
`other incoming call notification (e.g. vibration).
`[0030] The act of sending message response 254 to incom-
`ing call 204 may involve the following operations:
`(i)
`opening a new message for message response 254,
`(ii)
`addressing the message, (iii) including a message content
`242 or body for the message, and (iv)
`instructing the
`messaging component 220 to send the message response.
`The message response module 230 may perform at least
`some of these operations by communicating message cre-
`ation data 222 to the messaging component 220. The mes-
`sage creation data 222 may be generated at one time, or
`submitted in spurts based on the occurrence of other events.
`As such, some or all of the steps of sending the message
`response 254 may be performed automatically.
`[0031] Alternatively, some or all of the steps of sending
`the message response 254 may be performed automatically,
`after input triggers are provided from the user 202. For
`example, in one case, the user may designate a setting on the
`computing device 200 to handle all incoming calls with a
`message response (e.g. “on vacation”).
`[0032] As another alternative, in one implementation, the
`message creation data 222 is generated in response to a
`trigger from a user 202. The phone application 210, message
`response module 230, or some other component may prompt
`the user to message respond to a caller in response to receipt
`of call data 202. The prompt may occur shortly after the
`incoming call 204 is received, such as with or before the first
`“ring” generated on the computing device 200 for the
`incoming call. For example, the user may be able to elect
`message response as one option along with other options of
`answering or declining the incoming call 204.
`[0033] The message creation data 222 may be based on
`call data 212. In one embodiment, the message creation data
`
`222 may include (i) control data to cause the messaging
`application 220 to open a new message, and (ii) an address
`along with other data/instructions for addressing the newly
`created message. The message content 242 may be provided
`by a programmatic source 244, and/or by the user 202. In
`one embodiment, user 202 provides all of the message
`content 244.
`In another embodiment,
`the programmatic
`source 244 generates the content, in response to a user-input
`or other trigger. For example, the programmatic source 244
`may generate a macro message in response to a user select-
`ing to have incoming call 202 handled by the message
`response 254. Alternatively, content 242 may be a combi-
`nation of content provided by the programmatic source 244
`and the user. For example, the programmatic source may
`provide a template content that the user fills in. To illustrate,
`a portion of the message content 244 may correspond to
`“please call me in
`minutes.” The portion of the
`message content 244 provided by user 202 may correspond
`to “5”.
`
`[0034] An embodiment provides that the address provided
`by the message creation data 222 is a phone number of the
`incoming caller. In one embodiment, no verification or
`check is performed to determine if the device used by the
`caller is message enabled. For example,
`the user may
`manually make this selection in response to seeing the
`number being used by the caller. If the user recognizes the
`number as belonging to a cell phone, for example, the user
`may be assured that the caller’s device is message-enabled.
`Otherwise, the message response 254 may be transmitted,
`but not received by the caller.
`
`In another embodiment, a programmatic verifica-
`[0035]
`tion step is performed to see if the caller’s device is enabled
`to receive the message response 254. In one embodiment,
`the message response module 250 (or other programmatic
`element) may match the number of the caller to a field of a
`given contact record stored with a contact database 230 on
`the computing device. If, for example, the contact record
`information identifies the number of the incoming call as
`belonging to a “mobile” number, the messaging response
`module 250 may do one or more of the following: (i) provide
`an indication that message response is available, (ii) enable
`the user to elect message response option, and/or (iii)
`programmatically initiate a new message addressed to the
`number of the caller.
`
`[0036] Conversely, if the number of the incoming call is
`not
`identifiable as being message-enabled, embodiments
`provide that (i) a message or other indication is provided to
`the user warning that the caller’s device is not message
`enabled, or (ii) the message response feature is disabled.
`One embodiment may distinguish between not knowing
`whether the device of the caller can receive messages, and
`knowing definitively that the caller’s device cannot receive
`incoming messages. For example, in the former case, no
`action may be taken so that the message response feature is
`enabled, or a warning may be provided to the user indicating
`that the caller’s device may not be message-enabled. In the
`latter case, message response may be disabled. Numerous
`other
`scenarios
`are possible and contemplated under
`embodiments of the invention.
`
`[0037] Hardware Diagram
`
`FIG. 3 is a hardware diagram for use with one or
`[0038]
`more embodiments of the invention. In FIG. 3, a computing
`Qualcomm Exhibit 2021
`Apple v. Qualcomm, |PR2018—01279
`Page 8
`
`Qualcomm Exhibit 2021
`Apple v. Qualcomm, IPR2018-01279
`Page 8
`
`

`

`US 2007/0036286 A1
`
`Feb. 15, 2007
`
`device 300 includes one or more processors 310, one or
`more memory components 320, and a display 330. One or
`more communication components 318 may enable receipt of
`call data 204 (FIG. 2), voice exchanges, and message
`responses 254 (FIG. 2). In one embodiment, the communi-
`cation components 318 are for wireless communications,
`and cellular network communications in particular.
`
`[0039] The communication components 318 may config-
`ure computing device 300 to transmit and receive commu-
`nications on Code Division Multiple Access (CDMA) net-
`works, Global System for Mobile Communications (GSM)
`networks, and/or other types of cellular networks. The
`communication components 318 may include a Subscriber
`Identity Module (SIM) card, an input/output controller, a
`radio frequency transceiver, and an input/output controller.
`Combined, communication components 318 may enable
`voice-exchange, as well as text and other kinds of message
`data exchanges.
`
`[0040] The processors 310 may retrieve from the memory
`components 320 instructions
`(“application instructions
`322”) for executing operations such as described in FIG. 2.
`With reference to FIG. 2. the application instructions 322
`may correspond to execution of phone application 210,
`messaging application 220 and message response module
`230. Phone and/or message data 332 generated from execu-
`tion of these applications may be signaled to the display 330
`so that they can be viewed by the user.
`[0041]
`Input mechanisms 340 may enable the user to enter
`message input 342. The message input 342 may correspond
`to input triggers, corresponding to, for example: (i) decisions
`of the user to message reply to an incoming call, (ii) to
`include a specific pre-formulated message content 242,
`and/or (iii) to send the message response 254. As an alter-
`native or additional functionality, message input 342 gen-
`erated by the input mechanisms may include one or more
`manual entry items,
`including for example:
`(i) address
`and/or phone number of the recipient, and (ii) some or all of
`the message content 242 (FIG. 2).
`[0042] When used to compose message content 242 (FIG.
`2), input mechanisms 340 may have any one of a variety of
`forms. For example, input mechanisms 340 may correspond
`to a set of hard or soft keys (soft keys may be iconic in form
`and displayed through use of a contact-sensitive display)
`arranged in the form of a QWERTY keyboard or other
`layout. The message input 342 may correspond to alphanu-
`meric content, including phrases, keywords, or images that
`can be generated through use of keyboards (e. g. happy face).
`As another example, input mechanism 340 may correspond
`to a microphone, so that the message input is a voice file.
`Still further, the input mechanism 340 may correspond to a
`camera or other image capturing device, which captures an
`image for the message response 354.
`[0043] According to one embodiment, components 318
`receive call data 352 when a phone call or other voice-
`exchange session is initiated. Subsequently, such as in
`response to a call pick-up, voice data 362 may be received
`and transmitted. In one embodiment, a message 354 is
`transmitted as an alternative to the voice data 362 being
`exchanged. In another implementation, the message 354 is
`provided prior to the voice data exchange 362. For example,
`as described below, transmission of message 354 may result
`in an understanding between the caller and the recipient that
`the call pick-up will be delayed.
`
`[0044] Methodology
`
`FIG. 4 illustrates a message for handling incoming
`[0045]
`calls with message replies, under an embodiment of the
`invention. An embodiment such as described in FIG. 4 may
`be performed using components and elements such as
`described in FIG. 2 and other figures. Accordingly, reference
`may be made to elements of other figures for purpose of
`illustrating a suitable element or component for performing
`a step or sub-step being described.
`
`In step 410, an incoming call is received. The call
`[0046]
`may be transmitted over a cellular network, from one mobile
`device to another.
`
`Step provides that caller information is identified
`[0047]
`on the recipient device. This information may correspond to
`“Caller ID” information, which may include a name of the
`caller, and a phone number of the device being used to make
`the call.
`
`[0048] According to one embodiment, reply options are
`provided to the user in step 430. For example, the user may
`be provided the options of answering the call, declining the
`call, or message responding to the call. Under one imple-
`mentation, a graphic-user interface may be generated to
`enable the user to make the decision on how the call should
`
`be answered. The user may signal his or her decision by
`actuating, for example, a soft key that indicates one of the
`actions.
`
`[0049] A decision is made in step 435 as to whether the
`user has elected the message response. If the message
`response was not elected, step 440 provides an elected or
`default reply action is performed. This may correspond to
`the phone call being answered, or forwarding the phone call
`to another phone number or voicemail.
`
`If the user makes a decision in step 435 to message
`[0050]
`reply to the incoming call, then step 450 provides that a
`corresponding one of the messaging applications is opened,
`or otherwise presented in a state of use for the user.
`
`In step 460, a message reply is addressed to the
`[0051]
`incoming caller. This step may include a new message being
`created and then addressed. Alternatively, an existing mes-
`sage (such as one stored in a draft folder) may be addressed.
`In an embodiment such as shown by FIG. 2, the message
`response module 250 may signal control data to the message
`application 210 to cause the message creation, and to cause
`the message application to use the phone number of the
`incoming caller in the address field of the newly created
`message.
`
`the message body is
`Step 470 provides that
`[0052]
`inserted. Depending on the implementation, the message
`body may be created by (i) user-input, (ii) programmatically,
`or (iii) through a combination of user-input and program-
`matic creation. Programmatic content in the message body
`may be, for example, in the form of a template (text or
`image) or in the form of a macro. The macro may be
`triggered by user-input.
`
`In step 480, the message is transmitted to the caller.
`[0053]
`The message may be transmitted automatically in response
`to an event, such upon completion of the message. Altema-
`tively, the message may be transmitted through manual input
`from the user.
`
`Qualcomm Exhibit 2021
`Apple v. Qualcomm, |PR2018—01279
`Page 9
`
`Qualcomm Exhibit 2021
`Apple v. Qualcomm, IPR2018-01279
`Page 9
`
`

`

`US 2007/0036286 A1
`
`Feb. 15, 2007
`
`[0054] FIG. 5 illustrates an optional process that may be
`performed in order to determine or verify that a caller using
`a message-enabled device, under an embodiment of the
`invention. In step 510, the caller’s phone number is identi-
`fied. As mentioned, an embodiment provides that the Caller
`ID information may be used to identify the phone number
`used by the caller of the incoming call.
`
`In step 520, a database of contact records may be
`[0055]
`accessed to determine (i) a contact record that contains the
`phone number of the incoming call, and (ii) information
`provided in the contact record that indicates whether the
`device is message-enabled. With reference to FIG. 1, contact
`records stored in, for example, contact database 130 may be
`scanned for a contact record that contains the phone number
`of the incoming caller. The field assigned to the identified
`phone number may be the indicator of whether the device of
`the caller is message-enabled.
`
`the determination is made as to
`In step 525,
`[0056]
`whether the device of the caller is message-enabled. For
`example,
`if the phone number of the incoming call
`is
`matched to a contact record, and the number is listed in the
`contact record as belonging to a mobile, cellular device, the
`determination in step 525 may be that the caller’s device is
`message-enabled. Step 540 provides
`that
`a message
`response feature is provided as an option to the user if the
`determination in step 535 is that
`the caller’s device is
`message-enabled.
`
`[0057] One embodiment provides that if the determination
`in step 525 is negative,
`then step 530 provides that no
`message-response options are

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket