WO2011038265A2

WO2011038265A2 - Systems and methods for altering control criteria for mobile device operation

Info

Publication number: WO2011038265A2
Application number: PCT/US2010/050255
Authority: WO
Inventors: Jose M. Fernandez; Oren Kagan; Stephen Vowell; Gerry White; Chris Grobicki; Paul Nikolich
Original assignee: Illume Software Inc
Current assignee: Illume Software Inc
Priority date: 2009-09-24
Filing date: 2010-09-24
Publication date: 2011-03-31
Anticipated expiration: 2012-03-24
Also published as: WO2011038265A3; WO2011038269A1

Abstract

Systems and methods are provided for selectively permitting use of a mobile device while the device is in motion. In one aspect, a method is provided for altering control criteria used for selectively permitting use of a mobile device. A processor determines a variation of a speed of the mobile device, then compares the variation to a variation threshold. Upon determining that the variation is greater than the variation threshold, the processor alters control criteria for the mobile device, which changes the conditions under which use of the mobile device is permitted.

Description

SYSTEMS AND METHODS FOR ALTERING CONTROL CRITERIA FOR

MOBILE DEVICE OPERATION

Cross-Reference to Related Applications

[0001] This application claims the benefit of U.S. Provisional Patent Application No.

61/245,556, filed September 24, 2009; U.S. Provisional Patent Application No. 61/245,799, filed September 25, 2009; U.S. Provisional Patent Application No. 61/246,737, filed

September 29, 2009; U.S. Provisional Patent Application No. 61/245,815, filed September 25, 2009; U.S. Provisional Patent Application No. 61/245,820, filed September 25, 2009; U.S. Provisional Patent Application No. 61/245,891, filed September 25, 2009; U.S.

Provisional Patent Application No. 61/245,839, filed September 25, 2009; U.S. Provisional Patent Application No. 61/245,900, filed September 25, 2009; and U.S. Provisional Patent Application No. 61/246,587, filed September 29, 2009. The contents of all of the foregoing are hereby incorporated by reference herein in their entireties.

Background of the Invention

[0002] The problem of mobile devices being used by people while operating vehicles or participating in other potentially dangerous activities is well-known. Drivers become distracted by these devices, and are at a higher risk of being involved in a driving-related incident, such as a collision or unintended departure from the roadway. Some reports indicate that "driving while talking" and "driving while texting" are as dangerous as driving while under the influence of alcohol or other intoxicants.

[0003] As discussed in co-pending U.S. Patent Application No. 11/956,067, filed December 13, 2007, one useful approach involves monitoring the speed at which a mobile device is traveling. When the mobile device is in transit (typically determined by comparing the speed of the mobile device to a predetermined threshold), access control messages are transmitted either by the mobile communications device itself or a vehicle associated with the mobile device. The access control messages indicate to the mobile device communications network that communication with the mobile communications device should be prevented or deflected until the mobile device is no longer in transit. Another useful approach is described in copending U.S. Patent Application No. 12/040,581, filed February 29, 2008, which includes a mobile phone -based system for disabling a cellular phone when the phone is known to be moving at a predetermined speed. These co-pending applications are incorporated by reference herein in their entireties. Summary of the Invention

[0004] Applicants have identified a number of shortcomings of existing mobile device control technologies, which are addressed by the systems and methods disclosed herein. In particular, drivers often experience heavy stop-and-go traffic in urban environments or on congested highways. Stop-and-go traffic is characterized by oscillations in speed between zero, slow and high speeds, at irregular intervals. In existing technologies, when an access control message is sent in response to mobile device motion above a fixed threshold speed, a device in stop-and-go traffic will undesirably move in and out of a restricted use state. In addition, the need for restricting device usage in stop-and-go traffic is more limited due to the lower speeds usually involved in such travel. In the network-centric systems described above, stop-and-go traffic results in an inordinate amount of access control messages being transmitted to a mobile switching center (MSC). In some systems, another problem arises when use of a mobile device is inadvisedly permitted in heavy traffic conditions, due to the average low speed of travel. Thus, in some instances, it is advantageous to prevent usage even at lower speeds if such speeds are determined to result from travel in heavy traffic.

[0005] To address these and other shortcomings of existing mobile device control technologies, systems and methods are provided herein for selectively permitting use of a mobile device while the device is in motion. These systems and techniques can be configured to selectively allow or prevent different uses of a mobile device in heavy traffic situations. In one aspect, a method is provided for altering control criteria used for selectively permitting use of a mobile device. A processor determines a variation of a speed of the mobile device, then compares the variation to a variation threshold. Upon determining that the variation is greater than the variation threshold, the processor alters control criteria for the mobile device, which changes the conditions under which use of the mobile device is permitted.

[0006] In some implementations, the control criteria for the mobile device include a first speed threshold against which a speed of the device is compared. When the speed of the mobile device exceeds the first speed threshold, the processor disables or enables one or more functions of the mobile device.

[0007] In some implementations, a processor determines a variation of a speed of the mobile device by counting the number of times in a first time interval that the speed of the mobile device has increased above or decreased below a second speed threshold. When the counted number of times exceeds a count threshold, the processor responds by increasing the first speed threshold (against which the speed of the mobile device is compared). In another approach, a processor may determine a variation of a speed of the mobile device by determining a measure of the consistency of the speed of the mobile device. For example, in some implementations, the processor determines an amount of time during which the speed of the mobile device exceeds a second speed threshold. When the amount of time exceeds a time threshold, the processor responds to this determination of consistency by decreasing a first speed threshold against which the speed of the mobile device is compared. In some imp lementations ,

[0008] In some implementations, a processor receives traffic information from a source external to the mobile device, and then alters the mobile device control criteria based at least in part on the received traffic information. For example, in some implementations, the mobile device control criteria may be altered based on an average speed of traffic in the vicinity of the mobile device, the average speed of traffic at a particular time of day, or a notification of hazardous during conditions in the vicinity of the mobile device. In some implementations, the processor determines whether the mobile device is located on a street. If yes, the mobile device control criteria are altered; if no, the mobile device control criteria are not altered.

[0009] In some implementations, the processor determines a variation of the speed of the mobile device by determining a first representative speed of the mobile device over a first interval of time and determining a second representative speed of the mobile device over a second interval of time. The processor compares the first and second representative speeds to determine the variability of motion of the device between the first and second intervals of time. In certain implementations, this comparison includes calculating a ratio of the first and second representative speeds. In certain implementations, the first and second representative speeds are only compared when at least one of the first and second representative speeds is greater than a threshold representative speed. This threshold representative speed may be a speed indicative of a walking pace.

[0010] The use of the mobile device that may be selectively permitted include any one or more of voice communication functions, text message communication functions, camera functions, data service functions, media player functions, gaming functions, display functions, audio functions, or any other general or device-specific functions.

[0011] In another aspect, a method is provided for generating a heavy traffic condition signal from electronic device speed signals. A processor receives at least one electronic signal indicative of a speed of a device and monitors the at least one electronic signal over a time interval. Based on the monitoring, the processor determines the number of times in the time interval that the device speed has increased above or decreased below a speed threshold, and when the determined number of times exceeds a count threshold, the processor generates a heavy traffic condition signal.

Brief Description of the Drawings

[0012] The above and other objects and advantages of the systems and methods of the present disclosure will be apparent upon consideration of the following detailed description, taken in conjunction with the accompanying drawings, in which like reference characters refer to like parts throughout, and in which:

[0013] FIG. 1 is a block diagram of a mobile device configured to selectively permit its use;

[0014] FIG. 2 is a block diagram of a network-centric system for controlling permitted use of a mobile device;

[0015] FIG. 3 is a block diagram of a vehicle-centric system for controlling permitted use of a mobile device;

[0016] FIG. 4 is a block diagram of an alternative vehicle-centric system for controlling permitted use of a mobile device for use in the system of FIG. 3;

[0017] FIG. 5 is a flow chart of a method of restricting use of a mobile device;

[0018] FIG. 6 is a flow chart of a method of generating or updating a mobility access profile; and

[0019] FIG. 7 is a flow chart of a method of selectively permitting use of a mobile device. Detailed Description

[0020] Described herein are systems and methods for selectively permitting use of a mobile device while the device is in motion. As used herein, "motion" of the mobile device may refer to any information regarding the context and movement of the mobile device, an associated vehicle and/or its user such as physical displacement, a geographic location, bearing, speed or acceleration. These systems and methods can be implemented in a number of different configurations. Several exemplary configurations are discussed below with reference to FIGS. 1-4. These configurations are not mutually exclusive, and it is anticipated that elements from each may be combined and still fall within the scope of the invention. After discussing the exemplary configurations of FIGS. 1-4, techniques that may be implemented in accordance with different embodiments are discussed with reference to FIGS. 5-6. Finally, techniques for selectively permitting use of a mobile device when a user is experiencing stop-and-go traffic are discussed and illustrated with reference to FIG 7.

[0021] FIG. 1 depicts a "mobile-centric" configuration in which control of a mobile device is at least partially exerted by a controller included in the mobile device itself. The mobile device could be a cellular telephone, personal digital assistant, two-way pager, portable media player, laptop or notebook computer, or any other mobile communication or information device.

[0022] In particular, FIG. 1 is a block diagram of an illustrative mobile device 102, which includes a controller 104 for controlling operation of the mobile device 102. A radio frequency transceiver 106 provides radio access between the mobile device 102 and a communication system 204 (discussed below with reference to FIG. 2). The mobile device 102 also includes a user interface 108 so that the user of the mobile device 102 can interact and control the operation of the device 102.

[0023] The controller 104 is described herein as a general purpose processor included in the mobile device 102 that has been programmed with software (i.e., one or more modules of computer executable instructions) configured to perform the monitoring and control techniques described herein. The software may be a downloadable application (e.g., one that can be purchased from an online source and transmitted to the mobile device 102).

Alternatively, the controller 104 may be implemented via any combination of hardware, firmware, and software executing on a general purpose processor.

[0024] The user interface 106 includes interface elements such as an audio element 110, an input element 112, and a visual display element 114. The audio element 110 may include a microphone and speaker, and other audio transducers for generating alerts, music, audible messages and ringing sounds. The input element 112 may include, for example, a keypad, a software-based graphical user interface, a mechanical or optical mouse or trackball, a touch screen, voice recognition components, or other button/entry elements. The visual display element 114 may include, for example, a graphical display such as a liquid crystal display.

[0025] The mobile device 102 may use any of a number of techniques to determine that it is moving at a sufficient speed to indicate that is in a vehicle, or is in some other condition under which use of the mobile device 102 should be selectively permitted or restricted. For example, in a cellular communication application, the controller 104 may track the received signal strength indicator (RSSI) 118 of nearby serving cells (such as the serving cell 209 and the neighbor cell 211 of the mobile device support system 200 of FIG. 2). If the signal strength changes at a sufficiently rapid rate, it may be used as an indication that the mobile device 102 is in transit. In another example, the detection by the controller 104 of a handover between serving cells may be used as an indication that the mobile device 102 is in transit. Another method that may be employed leverages the presence of a satellite-positioning information receiver 116 (such as a GPS receiver) in the mobile device 102 to determine. The controller 104 may also detect motion using an embedded accelerometer, an

anemometer, a ground-based positioning system, or by monitoring changes in the mobile device's environment (such as changes in atmospheric pressure, acoustic changes such as the Doppler effect, or changes in local scenery detected using known computer vision

algorithms). By tracking location and time, for example, the controller 104 can make a number of determinations about its motion, as described in detail below.

[0026] Upon determining that the mobile device 102 is in transit, the controller 104 processes data indicative of the device's movement to determine whether usage of the device should be restricted. In one embodiment, such processing includes comparing the motion information to data stored in a mobility access profile ("MAP") 123 stored therein. The MAP 123 is a file or record including information for setting the permitted uses of the mobile device 102. The MAP 123 may be stored or recorded in any suitable format or data structure. The MAP 123 includes two types of information about the mobile device 102: control criteria and permitted use parameters. Control criteria are criteria against which the motion of the mobile device 102 is compared to determine what operations and functions of the mobile device 102 should be enabled, disabled, or restricted. Each set of control criteria may be associated with a set of permitted use parameters. During use, controller 104 compares the motion of the mobile device 102 against the control criteria of the MAP 123 and applies the permitted use parameters associated with any control criteria that are met.

[0027] As a result, certain functions of the mobile device 102 may be modified or restricted; for example, the controller 104 may deny call setup requests; prohibit peer-to-peer and text messaging, Internet access, camera functionality, gaming applications, or the like; route incoming calls to a voice mail account associated with the mobile device 102 or provide a busy signal; divert an incoming communication to an e-mail, voicemail or other

communications medium, or otherwise modify any other mobile device function or feature, or any combination thereof. In some implementations, calling and/or receiving one or more specific phone numbers, such as an emergency number, a home number or a parent's cellular phone number, or a dispatcher or supervisor's number, may be allowed while all other call setup requests are blocked. In some implementations, enforcing the permitted use parameters includes the controller 104 shutting off, blocking, or inhibiting certain interface elements, such as the elements 110, 112 and 114 (FIG. 1). Disabling interface elements advantageously reduces user interaction with the mobile device 102; by doing so, a user is prevented from, for example, composing a text message on the mobile device 102, only to discover that the messaging service has been restricted upon trying to send the message. By disabling the text messaging interface elements, the user is not allowed to compose a message in the first place, thus preventing use of the mobile device 102 while in transit. The same methodology can be used to block voice messaging, web browsing, or any other mobile device function.

[0028] FIG. 2 depicts a "network-centric" configuration in which control of a mobile device is at least partially exerted by a remote communication system in contact with the mobile device. In particular, FIG. 2 depicts a mobile device support system 200, which includes the mobile device 102, and a communication system 204 that enables

communication to and from the mobile device 102. A user of the mobile device 102 may use a vehicle 206 to drive to various destinations. The communication system 204 includes a base station 208, which provides a radio-air interface to subscribing mobile devices (such as the mobile device 102) in the vicinity of the base station 208. The region over which the mobile device 102 exchanges information with the base station 208 is the serving cell 209. The mobile device 102 may travel to other cells, and the communication system 204 will hand over communication service to each new serving cell as the device changes cell affiliation, as is well known in the art. A nearby base station 210 and its associated cell 211 are referred to as a neighbor cell. Quite often, even though the mobile device 102 is affiliated with the serving cell 209, the mobile device 102 can receive and measure signals from the neighbor cell 211 to determine, for example, when to make a handover or for reporting to the communication system 204, which may determine when a handover is needed.

[0029] In some mobile communications applications, the base stations 208 and 210 serve as intermediaries between the mobile device 102 and a mobile switching center (MSC) 212.

The MSC 212 controls calling and other communication activity, and is connected to a public switched telephone network (PSTN) 214. The MSC 212 sets up communication circuits for various modes of communication, in accordance with request and authorization protocols as known in the art. The MSC 212 controls communication access for subscribing and authorized roaming mobile devices (such as the mobile device 102) in accordance with a home location register and visit location register (HLR/VLR) 214. The HLR/VLR 214 maintains subscriber information and other parameters relating to mobility management, access control, and so on, which governs the manner in which the mobile device 102 operates within the communication system 204. [0030] In certain implementations, the communication system 204 is informed of the apparent travel of the mobile device 102. The communication system 204 may be informed from any one of at least two sources. First, the mobile device 102, itself, may report to the communication system 204 that the mobile device 102 appears to be traveling. Second, a vehicle module 218 disposed in vehicle 206 may report to the communication system 204 when the vehicle 206 is being operated or is traveling. The monitoring of the mobile device 102 or the vehicle 206 is performed continuously, periodically, or aperiodically.

[0031] When the mobile device 102 is in transit, the communication system 204 receives an access control message (ACM). An ACM is an information signal which includes information regarding the mobile device 102, such as its position, velocity, relative position with respect to a communications cell, relative position with respect to a beacon or marker, geographical coordinates, bearing, acceleration, altitude, or information derived from one or more thereof (such as rates of change, higher-order derivatives, and statistical measures like averages, standard deviations, and medians). The ACM is created by the mobile device 102, the vehicle module 218, the base station 208 or 210, or by another component of the mobile device support system 200 used to determine movement of the mobile device 102 or the vehicle 206 (as discussed in other implementations below). In some implementations, the ACM also includes identifying information about the user, the mobile device 102 or the vehicle 206, such as a communication address for the mobile device 102 or the vehicle 206 (i.e., a telephone number, an IP address, an e-mail address). Utilizing this information, the ACM enables the MSC 212 to determine whether or not the communication circuit needs to be reconfigured to selectively permit use of the mobile device 102 while the device is in motion.

[0032] The MSC 212 recognizes the ACM and routes it to an access control processor (ACP) 220 as a function of the information contained in the ACM. The ACP 220 then accesses an access database 222 to retrieve a MAP 123, (e.g., a cellular system mobility access profile (MAP)) stored therein. As described above, the MAP 123 includes control criteria and permitted use parameters for a given user. The ACP 220 provides the information in the MAP 123 to the MSC 212, which then applies the permitted use parameters associated with the mobile device 102. More particularly, access to

communication resources of the communication system 204 by the mobile device 102 is selectively permitted by comparing the motion of the mobile device 102 or the vehicle 206 to the control criteria stored in the MAP 123. The communication system 204 may, for example, deny call setup requests, peer-to-peer and text messaging usage, Internet access; route incoming calls to a voice mail account associated with the mobile device 102; provide a busy signal upon receipt of an incoming call; divert an incoming communication to an e-mail, voicemail or other communications address, and so on as a function of the permitted use parameters stored in the MAP 123 and processed by the MSC 212 and the ACP 220. The communication system 204 may further allow exceptions to any restrictions imposed. For example, calling or receiving calls from one or more specific phone numbers, such as an emergency number, a home number or a parent's cellular phone number, a dispatcher, or supervisor, may be allowed while all other call setup requests are blocked. In some implementations, generic instructions to allow all emergency calls (91 1 , for example), may be executed by default at the MSC 212 or the ACP 220. This methodology applies whether the mobile device functions are triggered by actions originating at the mobile device 102 (e.g., outgoing calls) or are aimed at the mobile device 102 (e.g., incoming calls). Note that if a profile for the mobile device 102 associated with the generated ACM does not exist in the access database 222, then the user or another authorized party (such as the user's parent) may be notified by e-mail or an Internet site and a MAP may be created for a particular mobile device.

[0033] Once the information in the MAP 123 is provided to the MSC 212, the MSC 212 then updates the present permitted use parameters associated with the mobile device 102. The present permitted use parameters may be stored, for example, in the VLR 214, and may be accessed by the MSC 212 when the mobile device 102 requests communication resources, or when incoming communications are received which are bound for the mobile device 102.

[0034] FIG. 3 depicts a "vehicle-centric" configuration in which control of a mobile device is at least partially exerted by a vehicle-mounted control system in communication with the mobile device. In particular, FIG. 3 is a block diagram of a vehicle-mounted control system 300. The vehicle-mounted control system 300 includes a vehicle module 218 for use in selectively permitting use of the mobile device 102. The vehicle module 218 is mounted in the vehicle 206. The vehicle module 218 determines that the vehicle 206 is in motion and/or is being operated. In some implementations, the vehicle module 218 has a modem 302, which includes a radio frequency transceiver capable of accessing the communication system 204 of FIG. 2 via an antenna 304. In these implementations, the vehicle module 218 may transmit an access control message (ACM) to the communication system 204 (and

specifically to the ACP 220 or its functional equivalent as discussed above). The modem 302 may act as another subscribing device in the communications system 204 and use the same wireless interface to the communications system 204 as the mobile device 102. Alternatively, the modem 302 may use an alternative wireless interface to the communications system 204. The modem 302 operates under control of a vehicle controller 306, which is programmed to carry out operations such as creating an ACM.

[0035] In other implementations, the vehicle module 218 may use the modem 302 (or other communication device) to transmit an ACM or other communication including motion data directly to the mobile device 102, instead of transmitting such information to the

communications system 204. In such implementations, the mobile device 102 is configured to receive messages regarding the motion of the vehicle 206 and use its own internal hardware and software (e.g., a controller similar to controller 104 of FIG. 1) to compare the motion of the vehicle 206 to one or more sets of control criteria (e.g., a MAP similar to MAP 123), and adjust the permitted uses of the mobile device 102 accordingly.

[0036] In some implementations, the vehicle controller 306 is interfaced though a vehicle interface 308 (e.g., via a cable connected to an OBD-compliant data port) to the vehicle control system 310. The vehicle control system 310 is the system in the vehicle 206 that controls, for example, instrumentation, engine operation, diagnostics, and other vehicle operation and monitoring functions. The vehicle control system 310 may be configured to provide information to the vehicle controller 306 as, for example, vehicle speed, vehicle access, the identity of a specific key or other access device used to operate the vehicle, and so on. The vehicle module 218 may use this information to determine when to transmit an ACM or motion information message, and what the contents of the ACM are to be. For example, when the vehicle speed reaches a preselected threshold, or if a key associated with a restricted user is used to access and operate the vehicle 206, the vehicle module 218 may transmit an ACM or other motion information message to the mobile device.

[0037] In some implementations, the vehicle module 218 may operate independently of the vehicle control system 310 and determine use of the vehicle by other means, such as, for example, a satellite positioning system receiver 312, which receives positioning signals from positioning satellites via an antenna 314. By using position information, the vehicle controller 306 can determine when the vehicle is moving, at what speed and subsequently transmit the ACM or other motion information message. Other means of triggering the transmission of an ACM may be used, such as pairing the vehicle module 218 with the mobile device 102 via a personal area network link. The vehicle module 218 may be installed such that pairing the mobile device 102 with the vehicle module 218 is required before the vehicle module 218 allows the vehicle 206 to start, for example, by using the personal area network media access information of the mobile device 102 as a sort of key. [0038] The vehicle module 218 may, upon installation in the vehicle 206 , be programmed with information to identify the mobile device 102 to the ACP 220 of the communications system 204 (discussed above with reference to FIG. 2). For example, an international mobile subscriber identifier (IMSI) or simply the phone number assigned to the mobile device 102 may be used. An identifier of the vehicle module 218 may be associated with the mobile device 102 at the ACP 220 and, when the ACP 220 receives the access control message, the ACP 220 cross references the vehicle module identifier with the identity of the mobile device 102 to locate the appropriate MAP 123 corresponding to the mobile device 102.

[0039] FIG. 4 depicts a second "vehicle-centric" configuration in which control of a mobile device is at least partially exerted by a vehicle-mounted control system in contact with the mobile device. In particular, FIG. 4 is a block diagram of a vehicle system 400 based on the vehicle system 300 for selectively permitting use of the mobile device 102 in accordance with another embodiment of the invention. In the vehicle system 400, the vehicle module 218 is interfaced with the vehicle control system 310. The vehicle control system 310 may detect the use of a key 402 to access and operate the vehicle 206. Automobile manufacturers routinely design a standard key and a valet key, for example. Manufacturers may likewise provide a "teen" key 402 to be used by a young family member to access and operate the vehicle 206. The key 402 is used by the person who also uses the mobile device 102, which is to be restricted upon operation of the vehicle 206. In addition to, or instead of the key 402 having a unique mechanical configuration, the key 402 may be provided with a memory element 304, which contains a unique identifier recognized by the vehicle control system 310 as one that is authorized to operate the vehicle.

[0040] In some implementations, a wireless key 406 may be used to access the vehicle 206 (instead of or in addition to the key 402). The wireless key 406 may transmit a code to the vehicle control system 310 over a short-range wireless link. This causes the vehicle control system 310 to cause the vehicle module 218 to transmit an ACM as discussed above (e.g., to the communications network 104 or the mobile device 102). In certain implementations, the mobile device 102 is itself configured as a wireless key (such as the wireless key 406), using a personal area network interface such as that known in the industry by the trade name Bluetooth™, for example.

[0041] FIG. 5 is a flow chart of a method for selectively permitting the use of a mobile device. Some of the steps of the flow chart in FIG. 5 are described as being performed by a "processor," which may be any suitable electronic processor included in the mobile device 102, the vehicle systems 300 or 400, or the mobile device support system 200 (FIG. 2) described above, or any combination thereof. For example, the steps depicted in FIG. 5 may be performed by the controller 104 included in mobile device 102, or by an MSC 212.

Additionally, the steps included in the flow chart of FIG. 5 may be distributed between two or more processors, which may perform their operations in parallel or in series.

[0042] FIG. 5 is a flow chart 500 of a method of restricting use of a mobile device. At Step 502, a processor commences monitoring the motion state of a mobile device, such as mobile device 102. The processor may begin the monitoring upon a user powering up the mobile device 102, upon the mobile device 102 exiting a sleep state, upon launch of a separate software application stored in memory on mobile device 102, or upon detection by the mobile device 102 of a signal indicative of the device being within a vehicle (for example, receiving a message from a vehicle module 218 indicating the proximity of a key 402 or 306). Monitoring includes, without limitation, determining by any suitable means whether control criteria stored in a mobility access profile (MAP) (either stored on the device or stored remotely) have been met. For example, the processor monitors whether the device is moving at a rate above a threshold speed. Additional or alternative control criteria may include, without limitation, location within a given governmental jurisdiction having restrictions on mobile device usage, and time of day. These determinations can be made in any suitable fashion, including by making various analyses described above in relation to FIG. 1. In implementations of the method involving remote enforcement of permitted use parameters, the mobile device regularly, or on an event-driven basis, forwards data it collects from monitoring to the MSC 212 in an ACM.

[0043] At decision block 504, the processor determines whether any of the control criteria has been met. As indicated above, this determination can be made by the mobile device controller 104 or by the MSC 212, or a combination of the two. The determination could also be made by the vehicle module 218. Upon determining that sufficient control criteria have been met to justify limiting mobile device functionality, the mobile device 102 and/or the MSC 212 begin enforcing the permitted use parameters described above (Step 506).

[0044] The processor continues to monitor the motion of the mobile device (Step 508). Upon a determination that sufficient control criteria sufficient to restrict device usage are no longer met, the mobile device 102 and/or MSC 212 restores full device operation (Step 510).

[0045] FIG. 6 is a flow chart 600 of a method for generating or updating a mobility access profile (MAP) (such as MAP 123 of FIGS. 1, 2 and 3). At Step 602, a processor provides Internet access to a web server 224 (FIG. 1) to allow users and owners of mobile devices (such as the mobile device 102) to enter and edit information in mobility access profiles (such as MAP 123). At Step 604, a user, owner, or otherwise authorized party logs onto the web server 224 via an Internet connection 126 (FIG. 1). Examples of authorized parties include parents, managers, guardians, supervisors, law enforcement officials, insurance agents and other appropriate individuals or organizations. At Step 606, the web server 224 provides a web page or web pages requesting user input to establish settings and control criteria to be used as the parameters in adjusting the permitted uses of the mobile device 102. At Step 608, the user or other party enters the information, and by way of non-limiting example, may include the identity of the mobile device 102, a phone number assigned to the mobile device 102, the identity of the vehicle module 218, and one or more allowed phone numbers which will not be restricted. Emergency service numbers may be allowed by default, and may be updated by the user. At Step 610, the web server 224 uses the information to generate or update the MAP 123 (e.g., in the memory embedded in the mobile device 102, or the access database 222 of the communication system 204 of FIG. 1). At Step 612, the user may log off or otherwise terminate their session.

[0046] As discussed above, existing technologies fail to adequately address the challenges of mobile device control when a user is experiencing stop-and-go traffic. Stop-and-go traffic is characterized by oscillations in speed between zero, slow and high speeds, at irregular intervals. In existing technologies, when an access control message is sent in response to mobile device motion above a fixed threshold speed, a device in stop-and-go traffic will undesirably move in and out of a restricted use state. In addition, the need for restricting device usage in stop-and-go traffic is more limited due to the lower speeds usually involved in such travel. In network-centric systems described above, stop-and-go traffic results in an inordinate amount of access control messages being transmitted to an MSC. Described below are methods for selectively permitting use of a mobile device in stop-and-go traffic that address these and other challenges using the systems described above in relation to FIGS. 1- 4.

[0047] FIG. 7 is a flow chart describing techniques for selectively permitting use of a mobile device when the mobile device is travelling in heavy traffic. The techniques illustrated by FIG. 7 improve upon existing technologies in many ways; in particular, by altering control criteria in response to the variation of the speed of the mobile device. Several implementations of this technique are described in the discussion of FIG. 7 below.

[0048] At Step 702, the mobile device 102 is turned on, powered up or "awoken" from a sleep or hibernation mode. At Step 704, settings regarding operation of the mobile device 102 are initialized or retrieved from the MAP 123 (which may be stored in the communications system 204, the vehicle module 218, and/or the mobile device 102). These settings may be initialized to a default value (e.g., at the time of manufacture or sale), customized according to user preferences or local laws, or entered as part of HLR/NLR 214 or MAP 123 by the user (see e.g., the discussion of FIG. 6, above).

[0049] At Step 706, a processor activates a tracking system. The tracking system may be located in the mobile device 102, the vehicle module 218, the communications system 204, or distributed between two or more of these components. In certain implementations, the tracking system is a position tracking system included in the mobile device 102. In preferred implementations, the tracking system is a global positioning system (GPS) that is configured to determine the position of the mobile device 102. In some implementations, the tracking system is a position tracking system included in the vehicle module 218 (e.g., a GPS system). In certain implementations, the tracking system is a speed monitoring system that does not necessarily rely on position measurements (e.g., an accelerometer-based or signal strength tracking system). In the following discussion, GPS is used as the tracking system by way of non- limiting example to facilitate discussion, but non-GPS and non-position-based tracking systems may be used to implement the heavy traffic detection and response techniques described here. In implementations that do not include position-based tracking systems, the steps of the flow diagrams of FIG. 7 that include a position-based activity may be omitted and remain within the scope of the invention.

[0050] At Step 708, the processor receives a GPS reading indicative of the position of the mobile device 102. At decision block 710, the processor compares the GPS reading to a map stored in a memory accessible to the processor. Such maps are provided by Internet-based technologies including MAPQUEST and Google Maps, and can be downloaded to the memory in advance of decision block 710 or in conjunction with decision block 710 based on the GPS reading. This memory may be local or remote. Comparing the GPS reading to the stored map allows the processor to determine whether the mobile device 102 is positioned at a valid street location. If the position of the mobile device 102 is not a valid street location, then it is likely that the user of the mobile device 102 is not driving a vehicle (e.g., the user is on a train, or walking at an off-street location) and thus restricted use of the mobile device 102 is not required. In this case, the processor executes a "clear" Step 71 1 and sends an unlock software control signal to the mobile device 102 to reset any software locks that were set previously (discussed below), then executes Step 708 again to take further GPS readings until it is determined that the mobile device 102 is located at a valid street location. [0051] At decision block 710, if the processor determines that the mobile device 102 is in a valid street location, a second GPS reading is received at Step 712. This second GPS reading is taken at a predetermined time interval from the first GPS reading (received at Step 708), and can be used in to determine the speed of motion of the mobile device 102 by dividing the distance traveled between the first and second GPS readings by the duration of the time interval. As discussed above with reference to FIGS. 5 and 6, information about the motion of the mobile device 102, including its speed, is compared against the control criteria stored in MAP 123. In preferred implementations, the MAP 123 is stored at the mobile device 102. At decision block 714, the processor determines whether the motion of the mobile device 102 satisfies a set of control criteria which will require a change in the permitted uses of the mobile device 102. For example, the control criteria may include a safe speed threshold for the mobile device. This safe speed threshold may be a predetermined speed above which safe operation of the mobile device 102 is impaired. When the mobile device 102 is moving at a speed below the safe speed threshold of the control criteria, the processor executes a "clear" Step 71 1 , then returns to Step 708 and continues to take GPS readings to monitor the motion of the mobile device 102.

[0052] If the processor determines at decision block 714 that the speed of the mobile device 102 exceeds the safe speed threshold, the processor performs a heavy traffic detection technique at decision block 716. If the processor determines that the mobile device 102 is not in heavy traffic at decision block 716, then the control criteria are set to (or maintained at) their "normal traffic" values at Step 718, and the processor proceeds to decision block 722 (discussed below). However, if the processor determines that the mobile device 102 is in heavy traffic, the processor assesses whether the current control criteria are set to their heavy traffic values at decision block 720. If not, the control criteria are altered to their heavy traffic values at Step 721. Heavy traffic detection techniques are discussed in detail below, as are the techniques performed at Step 721 when a heavy traffic condition is detected. After the heavy traffic condition is detected and responded to (if necessary), the processor determines at decision block 722 whether the permitted uses of the mobile device 102 are to be changed as a result of the excessive speed detected at decision block 714. If the use of the mobile device 102 is already appropriately restricted (e.g., because the mobile device 102 has previously exceeded the safe speed threshold), the processor returns to execute Step 708 and receive another GPS reading.

[0053] If the use of the mobile device 102 is not appropriately restricted, the processor determines at decision block 724 whether the mobile device 102 is currently in use. For example, the user may be making use of the mobile device 102 to watch a video or send/receive a text message. If the mobile device 102 is not in use, the permitted use parameters are applied at Step 726 to the operation of the mobile device 102 to restrict or block operation. In some implementations, the permitted use parameters prevent access to the communication functions of the mobile device 102, and incoming calls are either rerouted, met with a busy signal, a voicemail message or the like as discussed above. The permitted use parameters may also cause the output of a software control signal to the mobile device 102 to "lock down" the keyboard and, in particular, a "send" button of the mobile device 102. At Step 728, the processor causes any camera capability of the mobile device 102 to be disabled. The permitted use parameters may also cause a software control signal to be transmitted to lock down access to the camera activation controls on the mobile device 102 and/or lock the display screen. The processor returned to Step 708 to take another GPS reading.

[0054] Returning to decision block 724, if the mobile device 102 is currently engaged in a voice communication, then the processor determines at decision block 730 whether or not the other party is on an exception list as stored in the MAP 123. The exception list includes phone numbers such as 911, for which the risk of using the mobile device 102 in transit is outweighed by the necessity to have such communications maintained. If the other party is on the exception list, then the communication session is allowed to continue at Step 732, and the processor returns to execute Step 708. If processor determines at decision block 730 that the other party is not on the exception list, then the restricted operation imposed by the permitted use parameters begins in order to ensure the safety of the user. Accordingly, at Step 734, the processor executes an "End Call" technique in which an "End Call" software signal generated by the mobile device 102 or the MSC 212 to activate the "hang-up" function of the mobile device 102. In this way, a communication session is ended without dropping the connection (i.e., the antenna is not turned off) and the stoppage of communication is handled as a normal "End Call," not as a dropped call. In some implementations, the antenna may be turned off at Step 734, forcing an end to wireless communication with the mobile device 102.

[0055] In some implementations, rather than terminating an in-progress call or other audio communication, the processor may cause a disruptive noise (e.g. , white noise, loud repeated beeps, automobile accident sounds, etc.) or an audible message (e.g., "PLEASE HANG UP. IT IS UNSAFE TO CONTINUE SPEAKING") to be generated so that the user and/or the remote party can hear it. This noise or message may be repeated at a sufficient frequency, at a high enough volume, or otherwise be disruptive enough that it is very difficult for the user or remote party to continue the conversation, forcing one of the parties to manually end the call. The disruptive noise or message may persist for the duration of the audio

communication, and may end when the audio communication ends, the mobile device 102 is no longer in transit, or both. The disruptive noise may be provided directly to

communications circuitry within the mobile device 102, such as microphone circuitry and/or speaker circuitry. In some implementations, a web interface (e.g. , the web interface for generating a mobility access profile described with reference to FIG. 6) is provided that allows mobile device users or other interested parties to select the disruptive signal from multiple possible disruptive signals, and/or record a custom sound or special message. For example, a user's child or spouse may record him or herself saying "Please think of our family, dear, and don't use the phone while you drive." In some implementations, an interface for selecting and customizing the disruptive signal is provided on the mobile device 102 itself.

[0056] Once the communication session has ended, the remaining permitted use parameters are used to adjust the operation of the mobile device support system 200 at Step 726 (as described above). Adjusting the mobile device 102 in accordance with the permitted use parameters may include configuring the mobile device 102 to prevent communication with the communication system 204 by turning off the transmit side of the antenna circuitry of the mobile device 102, by locking the keyboard of the mobile device 102, or any of the other permitted use adjustments described herein. Adjusting the communications system in accordance with the permitted use parameters may include causing the communication system 204 to re-route calls to an on- or off-device voicemail repository, a forwarding phone number, an e-mail or alternate device, or providing a busy signal. In this way, incoming and outgoing communication functions may not be used by the user of the mobile device 102. After Step 728, at which the processor disables a camera included in the mobile device 102, the processor returns to Step 708 to take another GPS reading.

[0057] An important part of the techniques illustrated by the flow diagram of FIG. 7 is the heavy traffic detection and response techniques, executed at steps 916 and 920. Indeed, heavy traffic detection and response is one of the ways in which the techniques disclosed herein improve upon existing technologies. Exemplary heavy traffic detection and response techniques are now discussed. [0058] In one implementation, the heavy traffic detection technique performed at Step 816 includes determining a variation of the speed of the mobile device 102. The speed variation may be determined by any one or more of the following exemplary techniques:

• Counting a number of times in a first time interval that the speed of the mobile device 102 has increased above or decreased below a particular speed threshold (which may be the same as, or different than, the safe speed threshold). By way of example, if the threshold speed (e.g., 10 miles per hour) is crossed, either up or down, a

predetermined number of times (e.g., 3) within a minute (or other predetermined time interval) then this would be an indicator that the vehicle 206 in which mobile device 102 is traveling is in heavy stop-and-go traffic. In certain implementations, the number of times that the mobile device 102 crosses the threshold speed is recorded at MSC 212, ACP 220, HLR/NLR 214 (FIG. 1), the vehicle module 218, or at the mobile device 102 itself. At substantially the same time, a running clock is maintained within any suitable component to determine how often the threshold speed is crossed by the mobile device 102.

• Determining an amount of time during which the speed of the mobile device 102 exceeds a particular speed threshold (which may be the same as, or different than, the safe speed threshold). This technique measures the consistency or "non- variation" of the speed, and is particularly useful for determining when a heavy traffic condition has abated, and the permitted uses of the device can be returned to their nominal settings. For example, if the speed is greater than 30 miles per hour for longer than one minute, the processor concludes that no heavy traffic condition exists.

• Determining a distance traveled over a particular time interval by comparing a starting position and an ending position. This comparison allows the processor to distinguish a continuous travel situation that included intermediate accelerations (long distance traveled) from a stop-and-go travel situation (short distance traveled).

• Receiving speed variation information regarding traffic local to the mobile device 102 from a source external to the mobile device 102 (e.g., a traffic website, news feed or Twitter feed). An online traffic monitoring sites may be queried by utilizing the web server 224 and Internet 226 (FIG. 1). If the tracking system activated at Step 806 is a position-based tracking system (e.g., GPS, satellite, tower determination, etc.), the processor can use the location of the mobile device 102 to interrogate a traffic monitoring website to determine the existence of heavy traffic to be utilized as an input at decision block 716. In some implementations, the mobile device control criteria may be altered based on an average speed of traffic in the vicinity of the mobile device, the average speed of traffic at a particular time of day, or a notification of hazardous during conditions in the vicinity of the mobile device.

• Monitoring accelerometer readings to identify frequent accelerations and

decelerations. This technique may be performed by counting the peaks and valleys of the accelerometer signal or a velocity signal derived from the accelerometer signal, or applying a frequency-domain or wavelet-domain analysis technique to detect high frequency components in the acceleration signal, for example.

[0059] Another exemplary technique for determining a variation of the speed of the mobile device 102 includes determining a first representative speed of the mobile device 102 over a first interval of time, and determining a second representative speed of the mobile device 102 over a second interval of time. The first and second intervals of time may be contiguous or separate. A representative speed over an interval may be an average speed over the interval, a maximum speed over the interval, a minimum speed over the interval, or any other speed that represents the motion of the mobile device 102 over the interval. Once the first and second representative speeds have been determined, the variation of the speed of the mobile device 102 is measured by comparing the first and second representative speeds. In some implementations, this comparison is the ratio of the first and second representative speeds. In other implementations, this comparison is the absolute difference of the first and second representative speeds. In some implementations of this technique, the first and second representative speeds are only compared when at least one of them is greater than a predetermined threshold speed. In some implementations, both the first and second representative speeds when must be greater than a predetermined threshold speed before they are compared. The threshold speed may correspond to a walking speed, for example. By "discarding" representative speeds that are too slow to indicate travel in a vehicle, this implementation advantageously reduces the erroneous detection of a heavy traffic condition when a user is simply walking and occasionally stopping.

[0060] Any one or all of the above techniques may be utilized to determine a variation of the speed of the mobile device 102. In each technique, the determined variation is then compared to a threshold to determine whether the recorded speed pattern is indicative of heavy traffic. For example, when the number of times that a speed threshold is crossed exceeds a threshold number, a heavy traffic condition is identified. In another example, when the distance traveled in a particular time interval exceeds a threshold, a heavy traffic condition is not identified.

[0061] If the processor determines that the mobile device 102 is not in heavy traffic at decision block 716, then the control criteria are set to (or maintained at) their "normal traffic" values at Step 718, and the processor proceeds to decision block 722 (discussed below). However, if the processor determines that the mobile device 102 is in heavy traffic, the processor assesses whether the current control criteria are set to their heavy traffic values at decision block 720. If not, the control criteria are altered to their heavy traffic values at Step 721. In preferred implementations, altering the control criteria at Step 721 includes increasing the safe speed threshold against which the speed of the mobile device 102 is compared to determine whether the permitted uses should be changed. Increasing the safe speed threshold advantageously allows the control criteria to adapt to periodic small accelerations without triggering the transmission of an ACM or the potential disruption caused by frequent changes of the permitted uses of the mobile device 102. For example, to accommodate for periodic quick bursts of acceleration, the safe speed threshold may be altered from 10 miles per hour to 20 miles per hour. The processor may make use of web- or feed-based traffic control information about the location at which the mobile device 102 is traveling, to adjust the safe speed threshold to an appropriate heavy traffic level of 20 miles per hour.

[0062] In some implementations, altering the control criteria at Step 721 comprises extending a time interval over which the speed must exceed a speed threshold in order for the use of the mobile device 102 to be selectively permitted. For example, in normal traffic, the processor may be configured to transmit an ACM when it determines that the speed of the mobile device 102 exceeds ten miles per hour for five seconds. In heavy, stop-and-go traffic, the control criteria may be altered so that the mobile device 102 must exceed ten miles per hour (or a higher threshold speed) for ten seconds before the control criteria are met and use of the mobile device 102 is selectively permitted.

[0063] In some implementations, altering the control criteria at Step 721 comprises applying additional signal processing steps to a motion signal (such as a location, speed, acceleration or bearing signal), then applying one or more criteria to the processed motion signal. For example, when heavy traffic is detected, the control criteria may be altered to require that a filtered version of a motion signal exceeds or falls below a threshold. In some such implementations, once a heavy traffic condition has been identified, the motion signal is low-pass filtered (e.g., by a moving average) and the low-pass filtered signal compared to a second speed threshold that is lower than the safe speed threshold. When the low-pass filtered signal exceeds the second speed threshold, the use of the mobile device 102 is selectively permitted. In such an implementation, the speed threshold at which mobile device use restriction occurs is lowered due to the presence of heavy traffic. Additional or different signal processing techniques may also extract other frequency information from the motion signal that can be used to alter the control criteria to adapt appropriately to heavy traffic situations.

[0064] Once the control criteria are altered at Step 721, the processor returns to execute Step 708 by taking another GPS reading. As long as the heavy traffic condition is maintained, the altered control criteria will be used to determine how and when the permitted uses of the mobile device 102 will change. Once the traffic condition clears (e.g., as indicated by the traffic control information or some of the speed variation measures described above), the processor will revert the control criteria to their nominal settings (i.e., the safe speed threshold will be decreased to its previous value of 10 miles per hour). Failure to receive an ACM for a predetermined period of time may also indicate a maintained high speed or low traffic condition, and thus cause the control criteria to revert to their nominal "normal traffic" values.

[0065] In some implementations, information about the motion patterns of the mobile device 102 are stored in a database (e.g., the access database 222) and are used to "learn" habitual traveled conditions of the mobile device 102. Using known pattern recognition techniques, such implementations account for rush hour traffic experienced on a repeated basis, such as a commute to work or to school. For example, if the user of the mobile device 102 travels in New York City on 5th Avenue, Monday through Friday at 7:00 A.M., the processor stores identified heavy traffic conditions as discussed above in the database and utilizes that information to alter the control criteria to include a heavy traffic safe speed threshold in the MAP 123 during that time period. In this way, one of the criteria now stored as part of the MAP 123 would include an automatic alteration of the control criteria to the heavy traffic settings at a predetermined time period during predetermined days of the week, when the processor identifies that the mobile device 102 is within a radius of a predetermined location.

[0066] In some applications, the user of the mobile device 102 is not the only party responsible for the mobile device 102 or the user. Other responsible or interested parties include administrators, parents and employers. In some implementations, when the mobile device 102 exceeds a threshold speed, a notification is sent to one or more of these interested parties (or friends or business associates of the user of the mobile device 102). Such a message notifies the receiving party that the user is traveling, and should not be contacted. It may be in these parties' interests to confirm that any control hardware or software (as described herein) has not been tampered with or removed. In some implementations, the controller 104 of the mobile device 102 is configured to detect whether any settings or functions of the mobile device 102 have been tampered with. In particular, the controller 104 may be configured to process identifying information about a mobile device control application (such as the name, size of the file, associated properties and identification of an associated mobile device such as the mobile device 102). On a periodic or triggered basis, the controller 104 may receive a "check application" query from a network server or other device to determine whether the control application is still active on the device. This check may include verifying whether the application has the appropriate identifying information; if not, notification may be provided to at least one of the mobile device 102 or a device or electronic communications account associated with an interested party. The device or electronic communications account information (such as an e-mail address) may be stored in the MAP 123. In some implementations, the controller 104 detects that a control application has been tampered with when the control application fails to operate during a predetermined time period. For example, if the control application is a tracking application, and a position of the mobile device 102 has not been reported to the communications network 404 within the previous 24-hour period, a "check application" query would be transmitted by the communications network 404. Tamper detection and notification techniques may be performed by any suitable processor or system involved in the configuring, monitoring or control of the mobile device 102.

[0067] It is to be understood that while various illustrative embodiments have been described, the forgoing description is merely illustrative and does not limit the scope of the invention. While several examples have been provided in the present disclosure, it should be understood that the disclosed systems, components, and methods may be embodied in many other specific forms without departing from the scope of the present disclosure.

Claims

What is claimed is:

1. A method for altering control criteria used for selectively permitting use of a mobile device, the method comprising:

determining a variation of a speed of the mobile device;

comparing the variation to a variation threshold; and

upon determining that the variation is greater than the variation threshold, altering mobile device control criteria to change the conditions under which use of the mobile device is permitted.

2. The method of claim 1, wherein the control criteria comprise a first speed threshold against which a speed of the device is compared.

3. The method of any of claims 1 and 2, wherein the altering step comprises increasing the first speed threshold.

4. The method of any of claims 1-3, further comprising:

comparing a speed of the mobile device to the altered control criteria; and

adjusting a permitted use of the mobile device based at least in part on the comparison.

5. The method of claim 4, wherein:

the control criteria comprise a first speed threshold,

the comparing step comprises comparing a speed of the mobile device to the first speed threshold, and

the adjusting step comprises, when the speed of the mobile device exceeds the first speed threshold, disabling one or more functions of the mobile device.

6. The method of any of claims 4 and 5, wherein:

the control criteria comprise a first speed threshold,

the adjusting step comprises, when the speed of the mobile device exceeds the first speed threshold, enabling one or more functions of the mobile device.

7. The method of any of claims 1-6, wherein determining a variation of a speed of the mobile device comprises counting a number of times in a first time interval that a speed of the mobile device has increased above or decreased below a second speed threshold.

8. The method of claim 7, wherein the altering step comprises, when the counted number of times exceeds a count threshold, increasing a first speed threshold against which the speed of the mobile device is compared.

9. The method of any of claims 1-8, wherein determining a variation of a speed of the mobile device comprises determining an amount of time during which the speed of the mobile device exceeds a second speed threshold.

10. The method of claim 9, wherein the altering step comprises, when the amount of time exceeds a time threshold, decreasing a first speed threshold against which the speed of the mobile device is compared.

11. The method of any of claims 1-10, further comprising receiving traffic information from a source external to the mobile device.

12. The method of claim 11, wherein altering the mobile device control criteria is based at least in part on the received traffic information.

13. The method of any of claims 1-11, further comprising determining whether the mobile device is located on a street.

14. The method of claim 13, wherein control criteria are altered when the device is determined to be located on a street and are not altered when the device is not determined to be located on a street.

15. The method of any of claims 1-14, wherein determining a variation of a speed of the mobile device comprises:

determining a first representative speed of a device over a first interval of time;

determining a second representative speed of a device over a second interval of time; comparing the first and second representative speeds to determine the variability of motion of the device between the first and second intervals of time.

16. The method of claim 15, wherein comparing the first and second representative speeds comprises calculating a ratio of the first and second representative speeds.

17. The method of claim 15, wherein the threshold representative speed is a speed indicative of a walking pace.

18. The method of claim 15, wherein the first and second representative speeds are compared when at least one of the first and second representative speeds is greater than a threshold representative speed.

19. The method of any of claims 1-18, wherein the use of the mobile device includes a voice communication function.

20. The method of claim 19, further comprising:

receiving a list of allowed telephone numbers; and

allowing use of the voice communication function for voice communication with a communication device associated with any one of the allowed telephone numbers.

21. The method of any of claims 1-20, wherein the use of the mobile device includes a text message communication function.

22. The method of any of claims 1-21, wherein the use of the mobile device includes a camera function.

23. The method of any of claims 1-22, further comprising:

detecting that a mobile device function or setting has been tampered with; and in response to detecting that the mobile device function or setting has been tampered with, sending a notification to a responsible party.

24. The method of any of claims 1-22, further comprising:

comparing a speed of the mobile device to a speed threshold, and when the speed of the mobile device exceeds the speed threshold, sending a notification to one or more parties.

25. The method of any of claims 1-24, further comprising:

providing a web interface configured for receiving default values for one or more of the control criteria.

26. A method for generating a heavy traffic condition signal from electronic device speed signals, the method comprising:

receiving at least one electronic signal indicative of a speed of a device;

monitoring the at least one electronic signal over a time interval;

determining the number of times in the time interval that the device speed has increased above or decreased below a speed threshold; and

generating a heavy traffic condition signal when the determined number of times exceeds a count threshold.

27. A system for altering control criteria used for selectively permitting use of a mobile device, the system comprising:

a control unit configured to:

determine a variation of a speed of the mobile device;

compare the variation to a variation threshold; and

upon determining that the variation is greater than the variation threshold, alter mobile device control criteria to change the conditions under which use of the mobile device is permitted.

28. The system of claim 27, wherein the control criteria comprise a first speed threshold against which a speed of the device is compared.

29. The system of any of claims 27 and 28, wherein the altering step comprises increasing the first speed threshold.

30. The system of any of claims 27-29, wherein the control unit is further configured to: compare a speed of the mobile device to the altered control criteria; and

adjust a permitted use of the mobile device based at least in part on the comparison.

31. The system of claim 30, wherein:

the control criteria comprise a first speed threshold,

32. The system of any of claims 30 and 31, wherein:

the control criteria comprise a first speed threshold,

33. The system of any of claims 27-32, wherein determining a variation of a speed of the mobile device comprises counting a number of times in a first time interval that a speed of the mobile device has increased above or decreased below a second speed threshold.

34. The system of claim 33, wherein the altering step comprises, when the counted number of times exceeds a count threshold, increasing a first speed threshold against which the speed of the mobile device is compared.

35. The system of any of claims 27-34, wherein determining a variation of a speed of the mobile device comprises determining an amount of time during which the speed of the mobile device exceeds a second speed threshold.

36. The system of claim 35, wherein the altering step comprises, when the amount of time exceeds a time threshold, decreasing a first speed threshold against which the speed of the mobile device is compared.

37. The system of any of claims 27-36, wherein the control unit is further configured to: receive traffic information from a source external to the mobile device.

38. The system of claim 37, wherein altering the mobile device control criteria is based at least in part on the received traffic information.

39. The system of any of claims 27-38, wherein the control unit is further configured to: determine whether the mobile device is located on a street.

40. The system of claim 39, wherein control criteria are altered when the device is determined to be located on a street and are not altered when the device is not determined to be located on a street.

41. The system of any of claims 27-40, wherein determining a variation of a speed of the mobile device comprises:

42. The system of claim 41, wherein comparing the first and second representative speeds comprises calculating a ratio of the first and second representative speeds.

43. The system of claim 41, wherein the threshold representative speed is a speed indicative of a walking pace.

44. The system of claim 41, wherein the first and second representative speeds are compared when at least one of the first and second representative speeds is greater than a threshold representative speed.

45. The system of any of claims 27-44, wherein the use of the mobile device includes a voice communication function.

46. The system of claim 45, wherein the control unit is further configured to:

receive a list of allowed telephone numbers; and

allow use of the voice communication function for voice communication with a communication device associated with any one of the allowed telephone numbers.

47. The system of any of claims 27-46, wherein the use of the mobile device includes a text message communication function.

48. The system of any of claims 27-47, wherein the use of the mobile device includes a camera function.

49. The system of any of claims 27-48, wherein the control unit is further configured to: detect that a mobile device function or setting has been tampered with; and in response to detecting that the mobile device function or setting has been tampered with, send a notification to a responsible party.

50. The system of any of claims 27-49, wherein the control unit is further configured to:: compare a speed of the mobile device to a speed threshold, and

when the speed of the mobile device exceeds the speed threshold, send a notification to one or more parties.

51. The system of any of claims 27-50, further comprising:

a web interface in communication with the control unit and configured for receiving default values for one or more of the control criteria.

52. A system for generating a heavy traffic condition signal from electronic device speed signals, the system comprising:

a control unit configured to:

receive at least one electronic signal indicative of a speed of a device;

monitor the at least one electronic signal over a time interval; determine the number of times in the time interval that the device speed has increased above or decreased below a speed threshold; and

generate a heavy traffic condition signal when the determined number of times exceeds a count threshold.