U.S. patent application number 11/837030 was filed with the patent office on 2008-11-06 for method and system for communicating and displaying data with a voice call.
Invention is credited to Nicholas Alfano, Jan John-Luc Bakker, David Castell, Richard George, Douglas Gisby, David Heit, Ian McDonald.
Application Number | 20080273677 11/837030 |
Document ID | / |
Family ID | 38983500 |
Filed Date | 2008-11-06 |
United States Patent
Application |
20080273677 |
Kind Code |
A1 |
Alfano; Nicholas ; et
al. |
November 6, 2008 |
Method and System for Communicating and Displaying Data With a
Voice Call
Abstract
A method of communicating information describing a voice call
from a caller to a recipient comprises steps of obtaining call
subject information describing the call and communicating the call
subject information to the recipient to inform the recipient about
the call. The call subject information can be presented as a
subject line displayed to a recipient in which the caller provides
information about the nature of the call and/or its urgency, which
thus enables the recipient to better judge whether it should be
answered immediately. The call subject information can be input as
text by the caller or it can be extracted automatically from a
calendar application or a messaging application.
Inventors: |
Alfano; Nicholas;
(Stratford-Upon-Avon, GB) ; Castell; David;
(Waterloo, CA) ; Heit; David; (Waterloo, CA)
; Gisby; Douglas; (Atlanta, GA) ; Bakker; Jan
John-Luc; (Keller, TX) ; George; Richard;
(Waterloo, CA) ; McDonald; Ian; (Waterloo,
CA) |
Correspondence
Address: |
ECKERT SEAMANS CHERIN & MELLOTT
600 GRANT STREET, 44TH FLOOR
PITTSBURGH
PA
15219
US
|
Family ID: |
38983500 |
Appl. No.: |
11/837030 |
Filed: |
August 10, 2007 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
60915298 |
May 1, 2007 |
|
|
|
Current U.S.
Class: |
379/93.17 ;
455/414.1 |
Current CPC
Class: |
H04M 2201/38 20130101;
H04W 4/16 20130101; H04M 1/72436 20210101; H04M 2203/2038 20130101;
H04M 3/42059 20130101; H04M 2203/654 20130101; H04M 7/0054
20130101; H04M 2203/2011 20130101; H04M 1/575 20130101; H04M
1/27453 20200101; H04M 7/0042 20130101; H04M 3/436 20130101; H04M
3/42042 20130101; H04M 3/02 20130101; H04W 4/20 20130101 |
Class at
Publication: |
379/93.17 ;
455/414.1 |
International
Class: |
H04M 11/00 20060101
H04M011/00; H04M 3/42 20060101 H04M003/42 |
Claims
1. A method of communicating information describing a voice call
from a caller to a recipient, the method comprising steps of:
obtaining call subject information describing the call; and
communicating the call subject information to the recipient to
inform the recipient about the call.
2. The method as claimed in claim 1 wherein the step of obtaining
call subject information comprises a step of prompting the caller
to input text describing the call.
3. The method as claimed in claim 1 wherein the step of obtaining
call subject information comprises a step of automatically
extracting contextual call subject information from an application
executing on the device.
4. The method as claimed in claim 3 wherein the step of
automatically extracting contextual call subject information
comprises a step of extracting meeting information from a calendar
application.
5. The method as claimed in claim 3 wherein the step of
automatically extracting contextual call subject information
comprises a step of extracting subject information from a messaging
application.
6. The method as claimed in claim 1 further comprising a step of
specifying an urgency of the call.
7. A computer program product comprising code which, when loaded
into memory and executed on a processor of a wireless
communications device, is adapted to perform the steps of:
obtaining call subject information describing the call; and
communicating the call subject information to the recipient to
inform the recipient about the call.
8. A method of displaying call information about an incoming voice
call, the method comprising steps of: receiving call subject data
associated with the incoming voice call; processing the call
subject data to obtain call subject information describing the
incoming call; and displaying the call subject information to a
recipient of the incoming voice call to inform the recipient about
the nature of the incoming call.
9. The method as claimed in claim 8 wherein the step of the
processing the call subject data comprises extracting priority data
indicative of an urgency of the call to enable the displaying of
the urgency of the call to the recipient.
10. The method as claimed in claim 8 wherein the call subject
information comprises text input by the caller.
11. The method as claimed in claim 8 wherein the call subject
information comprises text automatically generated based on a
context in which the call is initiated.
12. The method as claimed in claim 11 wherein the text is
automatically generated by extracting information from a calendar
application.
13. The method as claimed in claim 11 wherein the text is
automatically generated by extracting information from a messaging
application.
14. A computer program product comprising code which, when loaded
into memory and executed on a processor of a wireless
communications device, is adapted to perform the steps of:
receiving call subject data associated with an incoming voice call;
processing the call subject data to obtain call subject information
describing the incoming call; and displaying the call subject
information to a recipient of the incoming voice call to inform the
recipient about the nature of the incoming call.
15. A wireless communications device comprising: an input device
for initiating a voice call; a processor coupled to memory to
generate call subject information describing the call; and a
radiofrequency transceiver for communicating the call subject
information to the recipient to inform the recipient about the
call.
16. The wireless communications device as claimed in claim 15
wherein the input device enables a user to input text describing
the call.
17. The wireless communications device as claimed in claim 15
wherein the processor and memory cooperate to automatically
generate the call subject information based on an application
context in which the call is initiated.
18. A wireless communications device for displaying call
information about an incoming voice call, the device comprising: a
radiofrequency transceiver for receiving call subject data
associated with the incoming voice call; a processor coupled to
memory for processing the call subject data to obtain call subject
information describing the incoming call; and a display for
displaying the call subject information to a recipient of the
incoming voice call to inform the recipient about the nature of the
incoming call.
19. The wireless communications device as claimed in claim 18
wherein the call subject information comprises text input by a
caller who has initiated the call.
20. The wireless communications device as claimed in claim 18
wherein the call subject information comprises text automatically
generated based on a context in which the call is initiated.
21. A server for dispatching call subject information to a
recipient describing a voice call initiated by a caller to the
recipient, the server comprising: a data port for receiving call
subject data to be dispatched to the recipient; and a processor for
determining a routing address for dispatching the call subject data
to the routing address of the recipient to inform the recipient
about the call.
Description
CROSS-REFERENCE TO RELATED APPLICATIONS
[0001] This application claims priority under 35 U.S.C.
.sctn.119(e) from U.S. Provisional Patent Application Ser. No.
60/915,298 filed May 1, 2007.
TECHNICAL FIELD
[0002] The present disclosure relates generally to wireless
communications devices and, in particular, to techniques for
communicating and/or displaying information regarding a voice call
that is transmitted or received by a wireless communications
device.
BACKGROUND
[0003] Wireless communications devices such as the BlackBerry.RTM.
by Research in Motion Limited enable users to communicate by
placing voice calls or by sending text-based messages (e.g. e-mail,
SMS, MMS, etc.).
[0004] When receiving a voice call, the device may display the
caller's name and number provided the device is enabled with
"Caller ID" or "Call Display" technology (and provided, of course,
that the caller hasn't squelched his identity using "Call Block" or
by using a private number which results in the display merely
showing "Private Number" or "Unknown Number"). When a recipient
receives an incoming call, therefore, the only form of caller
identification is the caller's phone number and either the person's
name or the company's name. If only the caller's number is
displayed, then additional information about the caller can
potentially be obtained by attempting to correlate the number of
the incoming call with known numbers stored in the device's address
book. In many cases, the amount of information available to call
recipient is quite limited.
BRIEF DESCRIPTION OF THE DRAWINGS
[0005] Further features and advantages of the present technology
will become apparent from the following detailed description, taken
in combination with the appended drawings, in which:
[0006] FIG. 1 is a block diagram of key components of a wireless
communications system on which the present technology can be
implemented;
[0007] FIG. 2 is a screenshot of an example of a call setup
screen;
[0008] FIG. 3 is a screenshot of an example of an incoming call
screen;
[0009] FIG. 4 is a screenshot of an example of a connected call
screen;
[0010] FIG. 5 is a screenshot of an example of a drop-down menu for
placing a call from within an e-mail message;
[0011] FIG. 6 is a screenshot of an example of an incoming call
originating from a messaging application;
[0012] FIG. 7 is a screenshot of an example of a meeting request
screen from which a call can be placed;
[0013] FIG. 8 is a screenshot of an example of a pull-down menu for
originating a call from within a meeting request;
[0014] FIG. 9 is a screenshot of an example of an incoming call
originating from a meeting request;
[0015] FIG. 10 is a flowchart showing steps of setting up a call
using the present technology;
[0016] FIG. 11 is a flowchart showing steps of displaying subject
line information for an incoming call;
[0017] FIG. 12 is a flowchart showing steps of setting up a call by
auto-populating a call subject field based on application
context;
[0018] FIG. 13 is a schematic depiction of a wireless
communications system for implementing the present technology;
and
[0019] FIG. 14 is a flowchart depicting main steps of routing a
call having subject line information.
[0020] It will be noted that throughout the appended drawings, like
features are identified by like reference numerals.
DETAILED DESCRIPTION
[0021] Given today's hectic work environment, certain calls (even
from known callers) might have to be ignored if the receiver is too
busy to answer, in a meeting, or otherwise occupied. However, it
would be very useful to enable the caller to provide further
information to the recipient about the call so that the recipient
could make a more informed decision about whether to answer the
call.
[0022] The present technology provides a solution to the problem
set forth above by enabling a user to enter textual information in
a call subject line that would be pushed to the recipient for
displaying in an incoming call screen so as to provide additional
information to the recipient regarding the context of the call
and/or to signify the importance/priority of the call.
[0023] Thus, an aspect of the present technology is a method of
communicating information describing a voice call from a caller to
a recipient. The method includes steps of obtaining call subject
information describing the call and communicating the call subject
information to the recipient to inform the recipient about the
call.
[0024] Another aspect of the present technology is a method of
displaying call information about an incoming voice call. The
method includes steps of receiving call subject data associated
with the incoming voice call, processing the call subject data to
obtain call subject information describing the incoming call, and
displaying the call subject information to a recipient of the
incoming voice call to inform the recipient about the nature of the
incoming call.
[0025] Yet another aspect of the present technology is a computer
program product that includes code adapted to perform the steps of
either or both of the two foregoing methods when the computer
program product is loaded into memory and executed on a processor
of a wireless communications device or other computing device.
[0026] Yet a further aspect of the present technology is a wireless
communications device having an input device for initiating a voice
call, a processor coupled to memory to generate call subject
information describing the call, and a radiofrequency transceiver
for communicating the call subject information to the recipient to
inform the recipient about the call.
[0027] Yet another aspect of the present technology is a wireless
communications device for displaying call information about an
incoming voice call. The device includes a radiofrequency
transceiver for receiving call subject data associated with the
incoming voice call, a processor coupled to memory for processing
the call subject data to obtain call subject information describing
the incoming call, and a display for displaying the call subject
information to a recipient of the incoming voice call to inform the
recipient about the nature of the incoming call.
[0028] Yet another aspect of the present technology is a server for
dispatching call subject information to a recipient describing a
voice call initiated by a caller to the recipient. The server
includes a data port for receiving call subject data to be
dispatched to the recipient, and a processor for determining a
routing address for the recipient for dispatching the call subject
data to the routing address of the recipient to inform the
recipient about the call.
[0029] The details and particulars of these aspects of the
technology will now be described below, by way of example, with
reference to the attached drawings.
[0030] FIG. 1 is a block diagram of key components of a wireless
communications system for implementing the present technology. It
should be expressly understood that this figure is intentionally
simplified to show only certain components; the system, map server
and wireless communication device of course each include other
components beyond those shown in FIG. 1.
[0031] As depicted in FIG. 1, the system includes a wireless
communications device 100 that has a microprocessor 102 (or simply
a "processor") which interacts with memory in the form of RAM 104
and flash memory 106, as is well known in the art. The device 100
includes an RF (radio-frequency) transceiver 108 for communicating
wirelessly with one or more base stations 200 connected via a
wireless network to the Internet 210 to enable e-mail and Web
browsing, for example. The device 100 may optionally include a GPS
(Global Positioning System) receiver chipset 110 for receiving GPS
radio signals transmitted from one or more orbiting GPS satellites
300. In terms of input/output devices or user interfaces (UI), the
device 100 typically includes a display 112 (e.g. a small LCD
screen), a thumbwheel and/or trackball 114, a keyboard or keypad
116, a USB 118 or serial port for connecting to peripheral
equipment, a speaker 120 and a microphone 122. The processor and
memory thus enable a variety of applications (messaging,
calendaring, etc.) to run on the wireless device. The speaker 120,
microphone 122 and RF transceiver circuitry 108 form part of a
voice communication subsystem that enables cellular communication
for placing or receiving voice calls.
[0032] FIG. 2 is a screenshot of an example of a call setup screen.
A "call subject" line feature in accordance with the present
technology enables a caller to enter "call subject information"
into an alphanumeric edit control in the call user interface (UI)
of the device while setting up a call, as shown in the call setup
example presented in FIG. 2.
[0033] In the example presented in FIG. 2, the "Call Subject:" text
input field prompts the caller to enter alphanumeric text to
describe the subject or topic of the call that will then be
transmitted to the call recipient when placing the call. The text
field can accept an entry of a system-configurable character
length.
[0034] When the recipient receives a call from the caller, an
"Incoming Call" screen may be displayed on the device as shown in
FIG. 3, which presents one example of an incoming call screen in
accordance with this technology. Displaying this incoming call
screen to the call recipient enables the latter to read the subject
or the topic of the call as shown in the example presented in FIG.
3. In this particular example, the call subject line reads "Call
Subject: Need to verify account number right away!". This call
subject information therefore provides the recipient with
additional information about the nature of the call to enable the
call recipient to judge or decide whether to accept the call or not
at that time. In this particular example, the incoming call screen
shows the name of the caller, her telephone number and an
Answer/Ignore pop-up box for enabling the user of the device (the
intended recipient of the caller's call) to either answer the call
or to ignore it. This call subject information is thus information
that is additional to the caller's name and telephone number. It
should be appreciated that the user can enter any text even if it
is, in fact, unrelated to the subject or topic of the call. It
should also be appreciated that the prefatory words "Call Subject:"
could be suppressed to provide more text space for slightly longer
messages. Again, the user could configure the device to either
display the prefatory words "Call Subject:" (or an equivalent
phrase) or to suppress these prefatory words altogether.
[0035] If the user chooses to answer the call, a "call connected"
screen may be displayed. An example of a "call connected" screen is
presented in FIG. 4. As shown in this particular example, the call
subject information ("Need to verify account number right away!")
may remain on the display or, alternatively, may be made to
disappear once the call is answered. Whether the call subject
information persists or is suppressed once the call is answered may
be a user-configurable option or setting.
[0036] From the foregoing, it should be understood that this novel
method of communicating information describing a voice call from a
caller to a recipient entails steps of obtaining call subject
information describing the call and then communicating the call
subject information to the recipient to inform the recipient about
the call. Obtaining the call subject information can be
accomplished by prompting the caller to input text describing the
call (as described and illustrated above). Alternatively, though,
the step of obtaining call subject information may be achieved by
automatically extracting contextual call subject information from
an application executing on the device. For example, automatically
extracting contextual call subject information can entail
extracting meeting information from a calendar application or
extracting subject information from a messaging application, such
as email or instant messenger, or from any other application from
which contextual call information can be extracted.
[0037] In one example, the present technology enables the caller to
auto-populate the "Call Subject" line based on the current device
application context. The "application context" means the
applications from within which the call is initiated. For example,
where the call is initiated from within a calendar application or a
messaging application, then the device extracts subject information
automatically to auto-populate the call subject line. Although
calendar and messaging applications are described by way of
examples, the auto-population of call subject line can also be done
with other applications that contain relevant call subject
information.
[0038] With reference now to FIG. 5, a caller can use information
contained within an open message in a messaging application to
auto-populate the call subject line. For example, from within a
messaging application, the caller can scroll through the message
body and any phone number entries found will be highlighted to
enable the user to place a call to the highlighted number through
the menu entry "Call xxx-xxx-xxxx". The present technology thus
enables a caller to place a call to the highlighted number with the
current message subject line as the "Call subject" through the
selection of the additional menu entry "Call xxx-xxx-xxxx (call
subject)" as shown in FIG. 5.
[0039] FIG. 6 is a screenshot of an example of an incoming call
originating from a messaging application. The call recipient will
see the "Incoming Call" screen displayed on their device as shown
in FIG. 6 with the "Call Subject" field populated by the e-mail
message subject (e.g. "Call Subject: Urgent call").
[0040] FIG. 7 is a screenshot of an example of a meeting request
screen from which a call can be placed. In other words, from the
"Calendar" application the user can open a meeting request and
scroll down to the "Invited" list, and select an invitee to call,
as shown in FIG. 7. Placing a call from within a meeting request
can be useful if trying to make last-minute arrangements with an
invitee who may be busy preparing for the meeting (and who might
only want to be disturbed if he knows it has something to do with
the upcoming meeting). As shown in FIG. 7, when the invitee name is
highlighted a menu can then be invoked with a menu item to "Call
(selected invitee)".
[0041] FIG. 8 is a screenshot of an example of a pull-down menu for
originating a call from within a meeting request or calendar entry
in a calendar application. As depicted in FIG. 8, the present
technology enables the caller to place a call where the meeting
entry "Subject" and "Location" and timestamp are included as the
"Call subject". The device can be configured to auto-populate all
or a subset of these data entries (such as subject and location
only or location and timestamp only or subject and timestamp only).
As shown in FIG. 8, the technology allows for a call to be placed
through an additional menu entry "Call (invitee) with meeting
subject/location/timestamp". The call recipient will see the
"Incoming Call" screen displayed as shown by way of example in FIG.
9. In the particular example presented in FIG. 9, the incoming call
is originating from a meeting request and the call subject line has
been auto-populated with the meeting time (e.g. "Meeting 1 pm-2pm")
and the meeting location (e.g. "Location Moonraker Room") which is
all data extracted from the meeting request.
[0042] FIG. 10 is a flowchart showing steps of setting up a call
using the present technology. First, a "Place Call" screen is
invoked at step 400 by the user on the device, and the user can
select whom to call by either entering a number or selecting a call
recipient from, for example, an entry in an address book, an email
in a messaging application, a meeting request or entry in a
calendar application, or any other means on the device. The "call
subject" field can now be populated by the device's user if this is
desired.
[0043] At step 402, the device determines whether the user wishes
to place the call ("Place Call"), or whether the user chooses to
exit the "Place Call" screen. If the user chooses to exit the
"Place Call" screen (step 404), the user is returned to a previous
screen (e.g. back to an application context from which the aborted
call was initiated).
[0044] If the user has chosen to place the call, then the device
will determine if the "call subject" entry field is populated (step
406) either by user data entry or by application-context-specific
auto-population of the call subject field. It should be noted that,
as an optional feature, the user may be allowed to edit the
auto-populated subject field (i.e. engage in "post-user editing")
to customize or edit the call subject information.
[0045] At step 408, transmission of the "call subject" data package
is initiated. At step 410, the device then determines whether the
"call subject" data transmission was successful within the
appropriate time frame. In other words, the device determines if no
response is received within the appropriate time frame or if an
error status is received.
[0046] If the call subject data transmission is not successful, the
device (at step 412) updates the "Call Subject" text field in the
"Calling/Call Connected" screen with the error status code
including transmission time-out response for the "call subject"
data package.
[0047] If the call subject data transmission is successful, the
call is set up and placed over the appropriate network, at step
414, and then the Place Call operation ends (step 416).
[0048] FIG. 11 is a flowchart showing steps of displaying subject
line information for an incoming call. As an initial step 500, the
device determines if it recognizes the incoming data as being call
subject data.
[0049] If the incoming data package (or received data package) is
marked or otherwise identifiable as a "call subject" data package,
then call subject data is stored (step 502) by committing the call
subject data to a device memory (designated by reference numeral
504, but which may simply be a memory portion of the device's RAM
104 or flash memory 106 which were introduced with reference to
FIG. 1). If not, at step 506, the device prepares an initial
display of the "Incoming Call" screen by, for example, presenting
only the telephone number of the incoming voice call and/or the
name or organization associated with the telephone number.
[0050] At step 508, the device determines whether call subject data
is available. If "call subject" data is available, then the device
retrieves (step 510) the "call subject" data from the device memory
504 and populates (step 512) all the fields of the incoming call
screen. If no call subject data is available, then the device
populates all "Incoming Call" data fields with whatever data is
available, e.g. just the telephone number and name.
[0051] As further shown in the flowchart of FIG. 11, the device
then displays the "Incoming Call" screen, at step 514, to present
the call subject information to the recipient of the call and then
(at step 516) ends the initial screen display operation.
[0052] FIG. 12 is a flowchart showing steps of setting up a call by
auto-populating a call subject field based on application
context.
[0053] As an initial step 600, a "Place Call" screen is invoked
from within a call-enabled device application, e.g. a messaging
application or a calendar application. In this particular
implementation of the technology, the device then determines (step
602) whether the invoking application is "Messaging" or if the
invoking application is "Calendar". If it is neither application,
in this particular implementation of the technology, the call
subject population operation is terminated (Step 604) and regular
call setup proceeds.
[0054] If the invoking application is "Messaging", the device
retrieves the message subject from a currently open message at step
606. Alternatively, if the invoking application is "Calendar", the
device retrieves the calendar entries for appointment timestamp,
subject and location (or optionally a subset thereof), at step
608.
[0055] Regardless whether the invoking application is "Messaging"
or "Calendar", the device then auto-populates (step 610) the
appropriate data fields in the "call subject" data package based on
the invoking application from within which the call has been
initiated. In the subsequent step (step 612), transmission of the
"call subject" data package is initiated.
[0056] At step 614, the device then determines if the "call
subject" data transmission is successful within the appropriate
time frame. If no response is received within the appropriate time
frame or an error status is received (step 616), then the device
updates the "call subject" text field for the "Calling/Call
Connected" screen with the error status code including transmission
time out response for the "call subject" data package.
[0057] On the other hand, at step 618, if the transmission of the
call subject data package was successful, the call is set up and
placed over the appropriate network (by displaying the "Place Call"
screen at step 620). At step 620, the initial "Place Call"
operation thus ends.
[0058] FIG. 13 is a schematic depiction of a wireless
communications system for implementing the present technology. FIG.
13 presents a high-level generic server and client interaction for
a wireless communications system having a BlackBerry.RTM.
Enterprise Server (BES) or similar implementation.
[0059] The BES will in this implementation act as a routing agent
for the "call subject" data package based on available and selected
data transmission channels. Alternatively, a scenario where data is
pushed directly between two "call subject"-capable devices can also
be envisioned.
[0060] For the server-side description, with reference also to the
flowchart of FIG. 14, what will follow here only describes a
generic routing process of the "call subject" data package where
the BES is deemed to be the appropriate routing agent based on
device capabilities and network availability and selection for data
channel transmission.
[0061] FIG. 14 is a flowchart depicting main steps of routing a
call having subject line information. In the initial step 700 shown
in this flowchart, a decision is made as to whether an incoming
data package is or is not a "call subject" data package. If the
incoming data is not call subject data, then BES operation
continues conventionally at step 718 (i.e. operations continue
without dispatching any call subject information). On the other
hand, if the incoming data is in fact call subject data, then the
next step (step 702) is to determine a package routing address and
then to determine (step 704) whether the package routing address is
valid and reachable. If the routing address is not valid and
reachable, then the next step (step 706) is to set an error status
code and to return the status code to the initiator (step 716). On
the other hand, if the routing address is valid and reachable, the
next step (step 708) is to commit the entry to a log (if logging is
enabled). Subsequently, in step 710, the "call subject" data
package is dispatched to the call recipient. At step 712, it is
determined whether the package dispatch was successful. If the
package dispatch was successful, then the success status code is
set (step 714). If the package dispatch was not successful, then
the error status code is not set (step 706). In subsequent step
716, the success status code (or alternatively the error status
code) is returned to the initiator address, and then normal BES
operation continues at step 718.
[0062] In the foregoing examples, the call subject data is
transmitted, received, and processed (into intelligible call
subject information) in a time frame such that the call subject
information is displayed on the display screen of the receiving
device approximately contemporaneously with the arrival of the call
(and the initial sounding of the ring tone). While this is the most
desirable result, it should be appreciated that the call subject
information may be displayed slightly before the ring tone begins
to sound or slightly after the ring tone has begun to sound.
[0063] In a further implementation, the call subject data may be
forwarded to a voicemail server in the event that the call is
unanswered or in the event that the called party is already on
another call. In other words, if the called party has voicemail
service, then the call subject data can be forwarded to the
voicemail server whereupon it may be accessed by the called party
or automatically pushed to the called party as part of a text-based
message indicating that the called party has new voice mail. By way
of example only, an e-mail may be sent to the called party's
wireless communications device with a subject line: "New Voice Mail
re: (call subject information)".
[0064] This new technology has been described in terms of specific
implementations and configurations which are intended to be
exemplary only. The scope of the exclusive right sought by the
Applicant is therefore intended to be limited solely by the
appended claims.
* * * * *