U.S. patent application number 13/280285 was filed with the patent office on 2012-05-03 for mobility call management.
This patent application is currently assigned to Aegis Mobility, Inc.. Invention is credited to Mandy Chan, John Joseph Geyer, David John Kiddie.
Application Number | 20120108219 13/280285 |
Document ID | / |
Family ID | 41608880 |
Filed Date | 2012-05-03 |
United States Patent
Application |
20120108219 |
Kind Code |
A1 |
Kiddie; David John ; et
al. |
May 3, 2012 |
MOBILITY CALL MANAGEMENT
Abstract
A mobility call management service is disclosed that provides
enhanced call management functionality for a wireless mobile
terminal (MT). Incoming and/or outgoing calls are managed based on
an assessment of the degree of motion of the MT, or other available
data pertinent to the MT's physical situation, such as but not
limited to it's location, movement, or rate of movement. The degree
of motion or other assessment may be used to determine whether a
communication can safely terminate on, originate from, or continue
safely on the MT, so as to reduce or remove driver distraction.
Inventors: |
Kiddie; David John;
(Coquitlam, CA) ; Geyer; John Joseph; (Vancouver,
CA) ; Chan; Mandy; (Vancouver, CA) |
Assignee: |
Aegis Mobility, Inc.
Vancouver
CA
|
Family ID: |
41608880 |
Appl. No.: |
13/280285 |
Filed: |
October 24, 2011 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
11696568 |
Apr 4, 2007 |
8045976 |
|
|
13280285 |
|
|
|
|
60744263 |
Apr 4, 2006 |
|
|
|
Current U.S.
Class: |
455/414.1 |
Current CPC
Class: |
H04M 2203/651 20130101;
H04M 3/436 20130101; H04W 4/02 20130101; H04M 3/4285 20130101; H04W
4/029 20180201; H04W 4/16 20130101; H04M 3/42348 20130101; H04M
2242/30 20130101; H04M 3/38 20130101; H04M 2203/2011 20130101 |
Class at
Publication: |
455/414.1 |
International
Class: |
H04W 4/04 20090101
H04W004/04 |
Claims
1. A method of processing communications between a remote terminal
and a mobile terminal, comprising: determining a risk assessment
state of a mobile terminal based at least in part on a degree of
motion of the mobile terminal, wherein the risk assessment state is
characterized as: a low risk assessment state associated with a
degree of motion below a first threshold, or a high risk assessment
state associated with a degree of motion above the first threshold;
and processing an information exchange between a remote terminal
and the mobile terminal based at least in part on the determined
risk assessment state of the mobile terminal, wherein: if the
determined risk assessment state corresponds to the low risk
assessment state, the information exchange between the remote
terminal and the mobile terminal is allowed, and if the determined
risk assessment state corresponds to the high risk assessment
state, the communication between the remote terminal and the mobile
terminal is not allowed.
2. The method of claim 1, wherein the information exchange between
the remote terminal and the mobile terminal corresponds to an
incoming request for communication to the mobile terminal, an
outgoing request for communication from the mobile terminal, or
ongoing communication between the remote terminal and the mobile
terminal.
3. The method of claim 1, wherein the information exchange between
the remote terminal and the mobile terminal corresponds to an
incoming request for communication to the mobile terminal, the
method further comprising, if the determined risk assessment state
corresponds to a high risk assessment state, placing the remote
terminal on hold until the risk assessment state of the mobile
terminal is reduced to a low risk assessment state.
4. The method of claim 3, further comprising subsequently causing a
connection of the information exchange between the remote terminal
and the mobile terminal in response to detecting that the risk
assessment state of the mobile terminal has reached a low risk
assessment state.
5. The method of claim 1, wherein the information exchange between
the remote terminal and the mobile terminal corresponds to an
incoming call from the remote terminal, the method further
comprising, if the determined risk assessment state corresponds to
a high risk assessment state, causing an output of an audible
message to the remote terminal that the mobile terminal is in
motion.
6. The method of claim 1, wherein the low risk assessment state
indicates that the mobile terminal is available to exchange
information with the remote terminal only after acknowledging an
audible warning, and wherein the audible warning to the user of the
mobile terminal is an audible signal other than a ring signal.
7. The method of claim 1, further comprising receiving an
acknowledgement by the user of the mobile terminal of the audible
warning; and allowing the information exchange between the remote
terminal and the mobile terminal.
8. The method of claim 1, wherein the information exchange between
the remote terminal and the mobile terminal corresponds to an
incoming call from the remote terminal, the method further
comprising, if the determined risk assessment state corresponds to
a high risk assessment state, recording a voice message from the
remote terminal, and subsequently causing the mobile terminal to
automatically play the voice message.
9. A system for processing communications between a remote terminal
and a mobile terminal, the system comprising: one or more computing
devices operable to: determine a risk assessment state of a mobile
terminal based at least in part on a degree of motion of the mobile
terminal, wherein the risk assessment state is associated with a
predefined risk assessment state corresponding to: a first risk
assessment state indicating that the mobile terminal is available
to exchange information with a remote terminal, or a second risk
assessment state indicating that the mobile terminal is unavailable
to exchange information with a remote terminal; and process an
information exchange between the remote terminal and the mobile
terminal based at least in part on the determined risk assessment
state of the mobile terminal, wherein: if the determined risk
assessment state corresponds to the first risk assessment state,
the information exchange between the remote terminal and the mobile
terminal is allowed, and if the determined risk assessment state
corresponds to the second risk assessment state, the information
exchange between the remote terminal and the mobile terminal is not
allowed.
10. The system of claim 9, wherein the information exchange between
the remote terminal and the mobile terminal corresponds to an
incoming request for communication to the mobile terminal, an
outgoing request for communication from the mobile terminal, or an
ongoing communication between the remote terminal and the mobile
terminal.
11. The system of claim 9, wherein the first risk assessment state
further corresponds to a risk assessment state indicating that the
mobile terminal is available to exchange information with the
remote terminal only after acknowledging an audible warning, and
wherein the one or more computing devices are further operable to,
if the determined risk assessment state corresponds to the first
risk assessment state, receive an acknowledgement by the user of
the mobile terminal of the audible warning; and allow the
information exchange between the remote terminal and the mobile
terminal.
12. The system of claim 9, wherein the first risk assessment state
further corresponds to a risk assessment state indicating that the
mobile terminal is available to exchange information with the
remote terminal only after acknowledging an audible warning, and
wherein the one or more computing devices are further operable to,
if acknowledgement by the user of the mobile terminal of the
audible warning is not received, disallow the information exchange
between the remote terminal and the mobile terminal.
13. The system of claim 9, wherein the one or more computing
devices are further operable to, if the determined risk assessment
state corresponds to the second risk assessment state, place the
information exchange on hold until the risk assessment state of the
mobile terminal is reduced to the first risk assessment state.
14. The system of claim 10, further comprising subsequently causing
the initiation of information exchange between the remote terminal
and the mobile terminal in response to detecting that the risk
assessment state of the mobile terminal has reached the first risk
assessment state.
15. The system of claim 9, wherein the risk assessment state of the
mobile terminal is further based on a geographic location of a
mobile terminal.
16. The system of claim 15, wherein the risk assessment state of
the mobile terminal is further based on a determination of whether
the mobile terminal is moving along a road or road segment, and
wherein the determination of whether the mobile terminal is moving
along a road or road segment is based at least in part on the
geographic location of a mobile terminal.
17. A computer-readable, non-transitory storage medium having
computer-executable modules for processing communications between a
remote terminal and a mobile terminal, the system comprising: a
risk management module operable to: determine a risk assessment
state of a mobile terminal based at least in part on a degree of
motion of the mobile terminal, the risk assessment state
corresponding to: a first risk assessment state indicating that the
mobile terminal is available to exchange information with a remote
terminal, or a second risk assessment state indicating that the
mobile terminal is unavailable to exchange information with a
remote terminal; and process an information exchange between the
mobile terminal and the remote terminal based at least in part on
the determined risk assessment state of the mobile terminal,
wherein: if the determined risk assessment state corresponds to the
first risk assessment state, the information exchange between the
remote terminal and the mobile terminal is allowed, and if the
determined risk assessment state corresponds to the second risk
assessment state, the information exchange between the remote
terminal and the mobile terminal is not allowed.
18. The computer-readable, non-transitory storage medium of claim
17, wherein the first risk assessment state further indicates that
the mobile terminal is available to exchange information with the
remote terminal only after acknowledging an audible warning, and
wherein the audible warning provides to the user of the mobile
terminal a plurality of call processing options.
19. The computer-readable, non-transitory storage medium of claim
18, wherein the plurality of call processing options include
allowing the information exchange, preventing the information
exchange, or placing the information exchange on hold until a
selected risk assessment state has been reached.
20. The computer-readable, non-transitory storage medium of claim
18, the risk management module is further operable to: if a call
processing option is not received from the user of the mobile
terminal, prevent the information exchange between the mobile
terminal and the remote terminal.
21. The computer-readable, non-transitory storage medium of claim
18, wherein the risk assessment state of the mobile terminal is
further based on a geographic location of a mobile terminal.
22. The computer-readable, non-transitory storage medium of claim
21, wherein the risk assessment state of the mobile terminal is
further based on a determination of whether the mobile terminal is
moving along a road or road segment, wherein the determination of
whether the mobile terminal is moving along a road or road segment
is based at least in part on the geographic location of a mobile
terminal.
Description
CROSS-REFERENCE TO RELATED APPLICATIONS
[0001] This application claims the benefit of U.S. Provisional
Appl. No. 60/744,263, filed Apr. 4, 2006, the disclosure of which
is hereby incorporated by reference.
FIELD OF THE INVENTION
[0002] The present invention relates to wireless communications and
call management, and more particularly, to the management of calls
placed to or from a mobile terminal.
BACKGROUND OF THE INVENTION
[0003] Each year more than 42,000 people are killed and more than 3
million are injured in more than 6 million motor vehicle accidents
on the nation's roads according to the National Highway
Transportation Safety Association (NHTSA). In its most recent 2005
report, the NHTSA estimates that driver distraction is contributing
to 20-30 percent of all motor vehicle crashes or 1.2 million
accidents each year. A 2002 Harvard Center for Risk Analysis
suggested that the rise in deaths and serious injuries and damages
is attributable to the fast growing pool of cell phone users with
85 percent of users admitting to cell phone use while driving.
Another study found that the risk of vehicle accidents is four
times greater when motorists are using cell phones and produce the
equivalent effect of reduced physical control and mental
inattentiveness as individuals having reached 0.08 percent blood
alcohol level, the legal limit in most states for driving under the
influence. Virginia Tech Transportation Institute's 2005 study
reported that hand-held wireless devices were among the highest
distraction-related factors in crashes and were the leading
distraction-related factor in near crashes.
[0004] Early researchers believed that hands-free phones were safer
to use than hand-held phones. Recent studies have shown that this
is assumption is untrue and that earlier assumptions may have
offered motorists a false sense of safety. The mechanism by which
cell phone conversations interfere with driving performance is not
based on whether the motorist is using a hands-free or a hand-held
device but rather by attentional interference, the diversion of
attention from the driving task to the cell phone conversation
itself. In neurophysiology, this competition between visual and
auditory stimuli is known as dual-task competition. Dual-task
competition occurs when auditory tasks unrelated to the visual task
are introduced. As a result, the degree of attentional distraction
depends on the complexity of the driving task and how engaged the
driver is to the cell phone conversation.
[0005] Recognizing the severity of this problem to public safety,
17 of the 50 states in America have introduced legislation that
restricts or bans cell phone use while driving. The NHTSA is
lobbying to have all 50 states adopt restrictions on cell phone use
while driving. Similar restrictions and bans have been adopted by
both developed and underdeveloped countries around the world,
including UK, France, Germany, Finland, Japan, Singapore, Hong
Kong, India and many others. Fines are commonly the method of
encouraging those who violate the cell phone use restrictions. In
New Delhi, India, motorists who are found talking on their cell
phone while driving have been imprisoned.
[0006] With the emergence of more and more wireless services and
applications, the likelihood of using the cell phone and other
wireless communication devices in a moving vehicle will continue to
rise. It is necessary to put in place guidelines in which users are
able to take advantage of their increasingly sophisticated services
but at the same time ensure that public safety is not compromised.
The reliance on public education may not be adequate because of the
convenience of cell phone communications. Furthermore, infringement
on restrictions and bans is difficult to monitor, making it
difficult for such legislation to be enforced.
SUMMARY
[0007] A mobility call management service is disclosed that
provides enhanced call management functionality for a wireless
mobile terminal (MT). Incoming and/or outgoing calls are managed
based on an assessment of the degree of motion of the MT, or other
available data pertinent to the MT's physical situation, such as
but not limited to it's location, movement, or rate of movement.
The degree of motion or other assessment may be used to determine
whether a communication can safely terminate on, originate from, or
continue safely on the MT, so as to reduce or remove driver
distraction.
BRIEF DESCRIPTION OF THE DRAWINGS
[0008] These and other features will now be described with
reference to the drawings summarized below. These drawings and the
associated description are provided to illustrate specific
embodiments of the invention, and do not to limit the scope of the
invention.
[0009] FIG. 1 illustrates a system architecture according to one
embodiment of the invention.
[0010] FIG. 2, which consists of FIGS. 2a-2e, is a flow diagram
illustrating how an incoming call to a mobile terminal (MT) is
managed according to one embodiment of the invention.
[0011] FIG. 3, which consists of FIGS. 3a-3d, is a flow diagram
illustrating how an outgoing call from a mobile terminal (MT) is
managed according to one embodiment of the invention.
[0012] FIG. 4, which consists of FIGS. 4a and 4b, illustrates
examples of degree of motion calculations.
[0013] FIG. 5 illustrates one example of an algorithm that may be
used to assess the MT's degree of motion.
[0014] FIG. 6 illustrates an example PSTN scenario.
[0015] FIG. 7 illustrates an example VoIP scenario.
[0016] FIG. 8 illustrates a hybrid PSTN/VoIP scenario.
DETAILED DESCRIPTION OF SPECIFIC EMBODIMENTS
[0017] Specific embodiments of a system for managing calls to and
from mobile terminals (MTs) will now be described with reference to
the drawings. This description is intended to illustrate, and not
limit the invention. The following terms are used throughout the
description:
[0018] Mobile terminal (MT)--a portable or stationary device that
operates on public and/or private wireless networks capable of
providing duplex voice and/or data communications.
[0019] Degree of motion--a calculated quantity, based on data
regarding the motion and/or other considerations of an MT, that
represents an MT's actual or predicted state of motion. The degree
of motion assessment is used in the preferred embodiment by a call
management application to intelligently manage calls originating
from and/or terminating on the subscriber's MT. The degree of
motion may, but need not, include a velocity calculation.
[0020] Mobility call management--the process of managing an MT call
(origination, termination and/or in process) in consideration of
the MT, potentially being in motion, as a telecommunications
feature involving methods such as but not limited to call routing,
for the purpose of improving driving safety and to enhance the
subscriber's experience, and the user experience of any other party
involved in the call.
System Architecture
[0021] As shown in FIG. 1, the system preferably involves the
cooperative interaction of four (4) software/hardware entities to
perform its functions: (1) a Service Switch (SS) that provides call
control capability, (2) a Feature Server (FS) that executes the
principle methods of the feature, (3) a Location Server (LS) that
provides data including but not limited to location, velocity,
and/or other pertinent information regarding the MT and/or the
subscriber, and (4) the Mobile Terminal (MT), which runs a client
that provides the user interface to the subscriber. As illustrated
in FIG. 1, the system also includes the following interfaces: (1)
an SS Interface, which is the logical and physical interface
between the Feature Server and the Service Switch, (2) an LD
Interface, which is the logical and physical interface between the
Feature Server and the Location Server, and (3) and MT Interface,
which is the logical and physical interface between the Feature
Server and the Mobile Terminal; this interface typically operates
over a communications network. Each of these components is further
described below:
[0022] The Remote Terminal (RT) is the communications device
through which the remote party participates in the cal, and is the
principle element through which the system feature logic interacts
with the remote party, the originator or intended terminator of the
communication for/by the end user of the MT. There ordinarily is no
system specific logic or modules in this element. The remote user
interacts with the system feature logic in a manner similar to that
used with IVR equipment.
[0023] This Service Switch (SS) represents the public or private
network element responsible for call control regarding the
subscriber communications service, and houses the call control and
service interface logic that is part of the MT's standard service.
As well, it contains the SS Service Logic Module that is the main
point of interaction between the system and the standard service.
The system assumes a "two half call" service model that allows for
feature insertion and call management as is typically found in a
carrier grade telecommunication switch. Note: in situations
involving emergency services the system is typically NOT permitted
to participate in the communication process.
[0024] The Feature Server (FS) is a standalone network service
component in which the principle feature software executes. It is
the logical hub of the system with interaction modules and
interfaces into the SS, the LS, and the MT. The feature server
executes feature software that processes MT location data to assess
the MT's "degree of motion." In other embodiments of the invention,
the feature software may run on a telecommunications switch, the
mobile terminals of subscribers, and/or other types of devices.
[0025] The Location Server (LS) supplies the feature server with
the realtime location data, and/or other data, regarding the MT, as
is typical for other Location Based Services (LBS). This data is
accessed with the expressed permission of the owner of the MT. The
Location Server may physically reside in a third party service
provider platform, in the MT itself, in the vehicle, or at some
other location. The location server may also provide realtime
velocity information if available to the Feature Server.
[0026] The Mobile Terminal (MT) is a portable communications
enabled device such as, but not limited, to a cellular telephone,
and is the mobile element that originates and terminates
communications with the end user. The mobile terminal includes a
User Interface (UI) for the feature to interact with the end user.
This capability is provided by the MT User Interface Module that
resides on the MT.
[0027] The SS Interface (SSI) allows for command and control
signaling interaction between modules on the FS and the SS Service
Logic Module. As well, it allows for audio interaction between
modules on the FS and the remote user on the RT.
[0028] The LD Interface (LDI) is the primary signaling channel
through which the feature logic in the FS acquires the location
data regarding the MT. This is typically a messaging channel to a
third party Location Data Provider server.
[0029] The MT Interface (MTI) is the main channel of communication
between the feature logic and the end user via the MT. Command and
control signaling typically occurs between modules on the FS and
the MT User Interface Module. Interaction with the end user occurs
via the MT User Interface.
[0030] Various alternatives to the architecture shown in FIG. 1 are
possible. For example, in a second embodiment of the system
architecture, some or all of the cooperating software entities may
execute in Service Switch, or Service Switch environment. In a
third embodiment of the system architecture, some or all of the
cooperating software entities may execute in the Mobile Terminal,
or Mobile Terminal environment. Additionally, the system may use
additional location based data, including but not limited to map
data, to perform the degree of motion assessment. For example, the
physical location of the device and/or the vehicle may or may not
necessitate that the rules used to assess the degree of motion be
augmented.
[0031] Additionally, the system may be provided with velocity
information pertinent to the MT's physical situation that may or
may not necessitate that the rules used to assess the degree of
motion be augmented. Additionally, the system may employ locally or
remotely available methods and apparatus to ascertain the proximity
of the MT to one or more specific vehicles, that may or may not
necessitate that the rules used to assess the degree of motion be
augmented.
[0032] The additional cooperating software entities described above
may reside in one of the specified physical elements of the system,
or in one or more additional physical elements.
[0033] In some embodiments, a subscriber can "bypass" the service
when, for example, the subscriber/MT is determined to be in motion
but is not actually operating a vehicle (e.g., when the subscriber
is riding on a bus or as a passenger in a car. By by-passing the
service, the subscriber may contractually accept responsibility for
any resulting harm, e.g., via agreement with their insurance
carrier, employer, wireless service provider, or another entity.
The actions of the subscriber may be appropriately logged for
purposes of implementing this feature.
Processing of Incoming Call to an MT
[0034] The following discussion illustrate how the system would
typically process an incoming communication destined for a typical
MT user. In this embodiment, the communication is a generic voice
call terminating on a generic MT user of a packet data enabled
mobile device. The generic voice call can be realized over a
typical mobility voice network or as a VoIP call over a typical
mobility packet data network. The incoming call presented here
represents only one possible scenario, and is not intended to
represent all possible usage scenarios. The following text explains
the events presented in the incoming call scenario (FIG. 2):
[0035] FIG. 2a:
[0036] The remote party (RT) initiates a voice call to a mobile
subscriber (MT) that has a network feature active on his mobile
voice service. The feature embodies aspects of the invention
[0037] The system's service logic module (service) that is running
in the service provider switch (SS), upon processing the call
request, checks and discovers that the subscriber has the feature
activated on the line--this triggers the system to execute the
mobility call management functions.
[0038] The service then queries the feature provider server (FS)
for instructions on how to route the call.
[0039] At this time the subscriber is driving a motor vehicle, and
at this instance is moving.
[0040] The system's feature logic modules (feature), running in the
feature provider server (FS), initiates periodic "degree of motion"
monitoring.
[0041] The feature then sequentially queries the location provider
server (LS) for several location data points, and executes a
"degree of motion" algorithm to obtain an assessment--at this time
the assessment result indicates that the "degree of motion" is HIGH
as the MT is physically moving quickly and is in an unsafe state.
The assessment of whether the MT is in a sufficiently safe state
may additionally take into consideration the MT's location, such as
whether MT is moving along an unsafe road or road segment as
revealed by map data associated with the MT's location.
[0042] The feature then responds to the service's query--in this
case the feature instructs the service to connect the remote party
to the feature server.
[0043] FIG. 2b:
[0044] The service then establishes a voice path between the remote
party and the feature's audio interface.
[0045] The feature then plays a recorded voice message to the
remote party to: (1) inform him of the subscriber's situation (in
motion and therefore may be driving a motor vehicle), and (2)
providing an opportunity for the remote party to select alternative
call options.
[0046] The remote party indicates that they are willing to hold for
a reasonable time so as to allow the subscriber to "pull over" and
receive the call.
[0047] The feature sends a message to the user interface running on
the MT requesting it to alert the subscriber that he has an
incoming call and that the remote party is waiting for him to
possibly "pull over" to receive the call.
[0048] The feature then provides treatment, in this case "music on
hold", to the remote party while they wait for the call to be
connected.
[0049] The UI then prompts the user in an appropriate manner--in
this case it might play a short midi file once.
[0050] At this time the subscriber has "pulled over" and safely
stopped, and at this instance is not moving.
[0051] The feature, having just performed another assessment as per
the monitoring function, determines that it is now appropriate for
the call to go through.
[0052] The feature instructs the service to transfer the call to
the MT.
[0053] The service tears down the voice path to the feature and
creates a voice path to the MT.
[0054] FIG. 2c
[0055] At this time the subscriber has started driving again, and
at this instance is moving.
[0056] The feature, having just performed another assessment as per
the monitoring function, determines that the MT is now in
motion.
[0057] The feature sends a message to the user interface running on
the MT requesting it to alert the subscriber that he, having been
assessed as now moving, must acknowledge that he is moving, and
therefore accept the liability.
[0058] The UI then prompts the user in an appropriate manner--in
this case it might play a short midi file once.
[0059] The user does not respond immediately.
[0060] The feature performs another assessment and determines that
the MT is still in motion.
[0061] FIG. 2d:
[0062] The feature sends a final warning message to the user
interface running on the MT requesting it to alert the subscriber
that he, having been assessed as still moving, must acknowledge
that he is moving, and therefore accept the liability.
[0063] The UI then prompts the user in an appropriate manner--in
this case it might play a short midi file once at a higher
volume.
[0064] The feature then logs the in-motion call event.
[0065] At this time the subscriber has stopped driving again, and
at this instance is not moving.
[0066] The feature, having just performed another assessment as per
the monitoring function, determines that the MT is now NOT in
motion.
[0067] The feature sends a polite message to the user interface
running on the MT requesting it to give the subscriber, having been
assessed as not moving, acknowledgment that he is no longer
considered to be moving.
[0068] The feature then logs the motion reduced call event.
[0069] The UI then prompts the user in an appropriate manner--in
this case it might play a short midi file once.
[0070] FIG. 2e
[0071] The MT then notifies the service that the subscriber has
"hung up".
[0072] The service notifies the feature that the call has
terminated.
[0073] The feature then logs the "on hook" event and terminates
monitoring the MT for motion.
[0074] The service tears down the voice path between the RT and the
MT, and the call is officially over.
[0075] The feature sends a polite message to the user interface
running on the MT requesting it to give the subscriber
acknowledgment that the monitoring process has terminated
successfully.
[0076] The UI then prompts the user in an appropriate manner--in
this case it might flash a quick message on the MT screen.
Processing of an Outgoing Call from an MT
[0077] The following discussion illustrates how the system would
typically process an outgoing communication from a typical MT/user.
In this embodiment, the communication is a generic voice call
originating from a generic MT user of a packet data enabled mobile
device. The generic voice call can be realized over a typical
mobility voice network or as a VoIP call over a typical mobility
packet data network. The outgoing call presented here represents
only one possible scenario, and is not intended to represent all
possible usage scenarios. The following text explains the events
presented in the outgoing call scenario (FIG. 3):
[0078] FIG. 3a:
[0079] The mobile subscriber (MT) initiates a voice call to a
remote party (RT). The subscriber has a network feature active on
his mobile voice service which embodies certain aspects of the
invention.
[0080] The system's service logic module (service) that is running
in the service provider switch (SS), upon processing the call
request, checks and discovers that the subscriber has the feature
activated on the line--this triggers the system to execute the
mobility call management functions.
[0081] The service then queries the feature provider server (FS)
for instructions on how to route the call.
[0082] At this time the subscriber is driving a motor vehicle, and
at this instance is moving.
[0083] The system's feature logic modules (feature), running in the
feature provider server (FS), initiates periodic "degree of motion"
monitoring.
[0084] The feature then sequentially queries the location provider
server (LS) for several location data points, and executes the
"degree of motion" algorithm to obtain an assessment--at this time
the assessment result indicates that the "degree of motion" is HIGH
as the MT is physically moving quickly.
[0085] The feature then responds to the service's query--in this
case the feature instructs the service to connect the subscriber to
the feature server.
[0086] FIG. 3b:
[0087] The service then establishes a voice path between the
subscriber and the feature's audio interface.
[0088] The feature then plays a recorded voice message to the
subscriber to: (1) inform him of the assessed motion situation (in
motion and therefore may be driving a motor vehicle), (2) provide
an opportunity for the subscriber to successfully address the
motion situation to enable the call to be placed, or (3) allow the
subscriber to authorize the call despite the warning.
[0089] The subscriber indicates that they wish to proceed with the
call by pressing the "1" key on the MT, or alternatively, by
uttering a voice command.
[0090] At this time the subscriber continues driving the motor
vehicle, and at this instance is moving.
[0091] The feature sends a message to the user interface running on
the MT requesting it to alert the subscriber that an active
acknowledgment is required to bypass the safety feature.
[0092] The subscriber indicates that they wish to proceed with the
call by pressing the key indicated on the MT's display screen.
[0093] The user interface replies to the feature's prompt message
thereby delivering the subscriber's active authorization to
complete the call setup.
[0094] The feature, having just performed another assessment as per
the monitoring function, determines that the MT is still in
motion.
[0095] FIG. 3c:
[0096] The feature then plays a recorded voice message to the
subscriber informing him that he has bypassed the safety feature
and that his call will be completed as per his authorization.
[0097] The feature then logs this event as it is a potential
violation of the safe usage of an MT in a moving vehicle--these
event logs can later serve if needed as evidence that the call was
place by an MT that was in a moving vehicle at a known time and
place.
[0098] The feature then instructs the service to establish a voice
path between the MT and the RT.
[0099] At this time the subscriber, having considered and taken
heed of the warning the feature provided" has stopped driving and
"pulled over", and at this instance is no longer moving.
[0100] The feature, having just performed another assessment as per
the monitoring function, determines that the MT is no longer in
motion.
[0101] FIG. 3d:
[0102] The feature sends a polite message to the user interface
(UI) running on the MT requesting it to give the subscriber, having
been assessed as not moving, acknowledgment that he is no longer
considered to be moving.
[0103] The feature then logs the motion reduced call event.
[0104] The UI then prompts the user in an appropriate manner--in
this case it might flash a brief message on the MT's screen.
[0105] The feature, having just performed another assessment as per
the monitoring function, determines that the MT is still NOT in
motion.
[0106] The RT then notifies the service that the remote party has
"hung up".
[0107] The service notifies the feature that the call has
terminated.
[0108] The feature then logs the "on hook" event and terminates
monitoring the MT for motion.
[0109] The service tears down the voice path between the RT and the
MT, and the call is officially over.
Degree of Motion Calculation
[0110] The "degree of motion" assessment provides a mobility call
management application with data, the "assessment", that allows the
intelligent management of calls if and when the subscriber's MT is
in motion. Any of a variety of known methods assessing the MT's
degree of motion may be used. The assessment preferably provides a
value that places the MT in one of a series of possible ranges. The
ranges, or zones, are strong indicators of the potential range of
velocities that an MT is experiencing at the time of the
assessment.
[0111] In one embodiment, the method provides an assessment that
places the MT in one of three zones. For example (FIG. 4), the
assessment could be: (1) a high "degree of motion" (H zone), (2) a
medium "degree of motion" (M zone), or (3) a low degree of motion L
zone). In this example, a high assessment might indicate that no
active communications may take place. A medium assessment might
indicate that no active communications may take place however the
subscriber can be alerted. A low assessment might indicate that the
subscriber is either not in motion or moving very slowly and can
safely participate in a communication. A greater number of zones,
such as four, five or six, may alternatively be used.
[0112] In one embodiment, the method uses as input two or more data
points. A data point contains two parameters, a global position
(latitude, longitude) and a time (the time the position data was
taken). The initial data point (p0) is considered to be the origin
point for the calculation. The subsequent data points are
statistically mapped to each of the possible ranges. Specifically,
the relative or weighted contribution of each data point is
statistically calculated for each zone and added to the zones sum.
The method will return the value of the zone with the highest sum.
That is, the method returns an indication to the zone that the MT's
motion is statistically most probably associated with.
[0113] In the first example (FIG. 4a) one additional data point
(p1) is provided as input to the method. At the time the data is
acquired the MT is in a motor vehicle that is moving very quickly.
The method maps the data to the zones placing the second point in
zone H relative to the origin point. This assessment results in a
significantly high probability that the MT is in a fast moving
vehicle. Only one assessment is typically sufficient in such
cases.
[0114] In the second example (FIG. 4b) three additional data points
(p1, p2, p3) are provided as input to the method. In this example,
at the time the data is acquired, the MT is not in a moving
vehicle, however the subscriber is in motion (for example,
jogging). The method maps the data to the zones as indicated. The
assessments results in a significantly high probability that the MT
is either not in a fast moving vehicle or not in a vehicle at
all.
[0115] If velocity data is available for the vehicle in which the
MT is situated, it can be used in the "degree of motion" assessment
in place of location data.
[0116] As can be seen from the input data examples (FIG. 4), the
zones preferably overlap. That is, there is a probability gradient
associated with each zone that determines the "weight" each data
point contributes to each zone sum. For example, data point p2
(FIG. 4b) contributes a slight value to both M zone and L zone,
while data point p1 contributes to only the L zone.
[0117] As can be seen from the example algorithm (FIG. 5), the
assessment calculation may execute one or more times before
returning the final value to the feature.
[0118] A typical deployment of the system in a PSTN scenario is
illustrated in FIG. 6. A typical deployment of the system in a VoIP
scenario is provided in FIG. 7. A typical deployment of the system
in a PSTN-VoIP hybrid scenario is provided in FIG. 8.
[0119] As illustrated by the forgoing, the system provides mobility
call management of an MT to reduce or eliminate the unsafe
generation of attentional interference on subscribers caused by
engaging in the use of an MT while operating a motor vehicle. The
system has the ability to calculate and provide an assessment of
the "degree of motion" that an MT is experiencing based on two or
more time stamped location data points obtained in realtime from a
location data source. Alternatively, the assessment can be made
with realtime velocity data in place of or in addition to location
data.
[0120] The system has the ability to enhance call management by
assessing the "degree of motion" that an MT is experiencing and
providing appropriate feature logic to assist in the call
management process, thereby improving and encouraging the safe use
of the MT: (a) when an incoming call is being considered for
delivery to an MT; (b) when an outgoing call is being considered
for delivery to a remote party, and/or (c) when a ongoing call
between an MT and one or more remote parties continues.
[0121] The system has the ability to enhance call management,
should the MT be assessed as having a considerable "degree motion"
indicating that the subscriber may be driving a motor vehicle at
that time, when an incoming call is being considered for delivery
to an MT, by doing any one or more of the following: (a) informing
the remote party of the subscriber's situation, and possibly
permitting the remote party to chose alternative call processing
options such as but not limited to having the call transferred to
the subscriber's voice mail; (b) informing the subscriber, and
possibly permitting the subscriber to chose alternative call
processing options such as but not limited to having the call
transferred to voice mail; (c) informing the subscriber, and
possibly permitting the subscriber to safely stop and accept the
call; (d) informing the subscriber, and permitting the subscriber
to override the service, such as when the subscriber is a passenger
in a moving vehicle and can safely engage in a call.
[0122] The system also has the ability to enhance call management
when an outgoing call is being considered for delivery from an MT
and the MT is assessed as having a considerable "degree motion"
indicating that the subscriber may be driving a motor vehicle at
that time. For example, in this scenario, the system may (a) inform
the subscriber, and possibly permit the subscriber to safely stop
and make the call; and/or (b) inform the subscriber, and permit the
subscriber to override the service, such as when the subscriber is
a passenger in a moving vehicle and can safely engage in a
call.
[0123] The system also has the ability to enhance call management
when an ongoing call between an MT and one or more remote parties
is in progress and the MT is assessed as having a considerable
"degree motion." In this scenario, the system may enhance call
management by doing one or more of the following: (a) informing the
remote party of the subscriber's situation, and possibly permitting
the remote party to chose alternative call processing options such
as but not limited to having the call transferred to the
subscriber's voice mail; (b) informing the subscriber, and possibly
permitting the subscriber to choose alternative call processing
options such as but not limited to having the call transferred to
voice mail; (c) informing the subscriber, and possibly permitting
the subscriber to safely stop and continue the call; (d) informing
the subscriber, and permitting the subscriber to override the
service, such as when the subscriber is a passenger in a moving
vehicle and can safely be engaged in a call.
[0124] The system may be configured to monitor and log an MT's call
events that occur when the "degree of motion" is assessed as
exceeding the permitted value or returning to the permitted value,
or when the "degree of motion" is assessed as exceeding the
permitted value and the subscriber has been informed and actively
authorizes the call to proceed.
[0125] The system may also be capable of using other sources of MT
location data, including, but not limited to, any one or more of
the following: 1) a third party MT location provider, 2) an
application running on the MT, 3) an application running in the
motor vehicle that the MT is located in, or 4) a third party
vehicle location provider of the motor vehicle that the MT is
located in.
[0126] The system preferably has the ability to provide mobile call
management features to enhance the subscriber's, and/or any other
party's involved in the call, mobile call experience, such as but
not limited to: (a) playing a distinctive audio indication
including, but not limited to, a musical sequence of tones as
indication to a remote party attempting to place a call to an MT
subscriber that the feature is active on their service, (b)
recording a short voice message from the remote party/caller for
the MT subscriber/callee, and delivering this message to the
subscriber in a safe and appropriate manner that does not require
the subscriber to dial or log-in to a voicemail system (e.g., the
recorded message may be played automatically in response to a
single key depression by the subscriber, in response to the MT's
degree of motion falling to an acceptable level, or automatically
once the message has been left), (c) providing a list of incoming
call attempts that were withheld and/or diverted by the feature via
the MT, a web interface, or in any other manner, (d) providing the
subscriber with the means and opportunity to reply to one or more
of the calls attempts that were withheld and/or diverted by the
feature via the MT, a web interface, or in any other manner. (e)
diverting call attempts that were withheld and/or diverted by the
feature to one or more of: a voice mail service, an attendant, a
designated person, a call management facility, or any other
specified location.
[0127] The system may use commercially available or manufacturer
supplied in-vehicle technology, such as but not limited to vehicle
telemetry via Bluetooth or Wi-Fi connectivity, to perform or
enhance the capabilities of the system.
[0128] The system may include the ability to provide feature
activation by multiple means, such as, but not limited to, (a) the
subscriber via any local means enabled to do so such as but not
limited to a soft key on the MT, (b) an in-vehicle device such as
but not limited to a Bluetooth unit or an EDR enabled to do so, (c)
by the feature itself given specific data warranting the activation
such as but not limited to GPS data and/or location data
[0129] The system may use commercially available location specific
data, such as but not limited to road or terrain information and
weather conditions, to perform or enhance the capabilities of the
system.
[0130] The system may have the ability to employ use data
pertaining to the subscriber such as, but not limited to, age,
driving record, and appropriate demographics, to perform or enhance
the capabilities of the system.
[0131] The system preferably has the following characteristics: (a)
system does not disable the use of the MT; (b) the system does not
require any "in vehicle" devices or systems, however, it may make
use of select available data that the in-vehicle device provides in
it regular operation; (c) the system does not interfere with the
proper functioning of the MT radio with the base station; this is
in contrast to some prior art systems that jam or interfering with
the MTs transmission and/or reception capability to restrict usage;
(d) the system preferably does not monitor the driver of the
vehicle for purposes of determining whether an MT call can safely
take place; (e) the system functions without requiring specific
knowledge of the involvement of a motor vehicle; (f) system will
function when the MT is in any moving vehicle, such as but not
limited to cars, trucks, busses, trains, boats and airplanes; (g)
system allows the user to responsibly use the MT in situations that
warrant it, such as in the event of an emergency, and in
appropriate situations that are not possible to foresee.
[0132] The various features and functions described above may be
embodied in software modules executed by general purpose and/or
special purpose computers. The software modules may be stored on
any type of computer readable medium or computer storage
device.
[0133] The various features described herein may be used in
combination with any one or more of the features described in U.S.
Provisional Appl. No. 60/892,628, filed Mar. 22, 2007, titled
ENHANCED CELLULAR MOBILITY CALL AND SESSION MANAGEMENT, the entire
disclosure of which is hereby incorporated by reference. For
instance, the system described herein can be augmented to include
some or all of the system components, and to implement some or all
of the methods, described in Appl. 60/892,628.
[0134] Although the invention has been described in terms of
certain embodiments and applications, other embodiments and
applications that are apparent to those of ordinary skill in the
art, including embodiments which do not provide all of the features
and advantages set forth herein, are also within the scope of this
invention. Accordingly, the scope of the present invention is
intended to be defined only by reference to the claims.
* * * * *