Patent ID: 12207153

In the figures of the drawings, like item callouts refer to like features.

DETAILED DESCRIPTION

A detailed description of the embodiments for a system, device, and method for limiting mobile device functionality in an operating vehicle will now be presented with reference toFIGS.1through11. One of skill in the art will recognize that these embodiments are not intended to be limitations on the scope, and that modifications are possible without departing from the spirit thereof. In certain instances, well-known methods, procedures, components, and circuits have not been described in detail.

As used herein, “Device Owner Application” includes within its meaning a specific type of application that 1) must be loaded onto a mobile device at the time of manufacture of the mobile device, or is loaded onto a mobile device only after a hardware reset of the mobile device; and 2) cannot be disabled or turned off by a user of the mobile device unless a hardware reset of the device is performed. This is in contrast to an application that has been downloaded and installed on a mobile device from a web site such as an online application store (“downloaded applications”). Such downloaded applications may be deleted, disabled, or turned off by a user of the mobile device without the need for performing a hardware reset of the mobile device and are not within the definition of “Device Owner Application”. A Device Owner Application is an application that cannot be defeated, disabled or uninstalled by a user of the mobile device. A Device Owner Application is structurally different from a downloaded application in that it runs as a Device Administrator on the mobile device, and as such may take control of mobile device configuration and security functions, and may alter the configuration of the mobile device. Downloaded applications are not able to take control of configuration and security functions, and are not able to alter the configuration of a mobile device.

As used herein, “application” or “software” includes within its meaning a set of non-transitory computer executable instructions that may be executed by a processor or controller, or by a plurality of processors or controllers. The non-transitory computer executable instructions may reside in a physical computer readable media that is in communication with the processors or controllers.

In an embodiment, as shown inFIG.1, system100comprises disabling device101and mobile device102. Disabling device101can be mounted, installed or otherwise positioned in a vehicle, such as for example cars, trucks, buses, motorcycles, trains and other motor vehicles. Disabling device101may be encased in a compact enclosure, such as a polycase. Disabling device101may be compact for discrete mounting on a vehicle windshield. Disabling device may be positioned on the interior of the vehicle at or near the corner of the windshield, on the windshield near the rearview mirror or at another location within the vehicle. Disabling device101comprises motion detector103, processor or microcontroller unit (MCU)104in communication with motion detector103, cellular radio105in communication with MCU104, signal generator106in communication with MCU104, power source108in communication with motion detector103, MCU104, cellular radio105, and signal generator106. Disabling device101may optionally comprise backup power source112in communication with MCU104. Backup power source112may also be in communication with one or more of motion detector103, cellular radio105, and signal generator106. Disabling device may optionally comprise solar cell109in communication with power source108. Solar cell109may also be in communication with backup power source112. Mobile device102, further shown and described below and inFIG.6, has a software application, or app, (e.g. Device Owner Application (DOA), mobile device management system or other applicable software) residing thereon that is capable of receiving a disabling signal from disabling device101.

Motion detector103determines the motion status of a vehicle. Motion detector103may be, for example, an accelerometer, a gyroscope or both an accelerometer and a gyroscope. Motion detector103may detect, for example, acceleration, direction (up/down/forward/backward), speed or a combination thereof. Motion detector103transmits a signal comprising the motion status to MCU104. Upon arrival at MCU104, the signal is converted into a signal readable by MCU104. This can be accomplished, for example, through the use of peripheral interface technology such as UART/SPI (universal asynchronous receiver/transmitter/serial peripheral interface) or I2C (Inter-Integrated Circuit).

MCU104uses the motion status within the signal received from motion detector103to ascertain the motion status of the vehicle. If the motion status indicates that the vehicle is in motion, MCU104instructs signal generator106to broadcast a disabling signal. MCU104interfaces with signal generator106, which may be, for example, a 802.11 radio, a Bluetooth® beacon, a Bluetooth® low energy beacon or any device that can transmit a similar electronic signal or trigger (which may optionally comprise an identifier), via any known mechanism, for example, UART or SPI. Motion detector103may detect movement of the vehicle causing it to produce a motion status indicating that the vehicle is in motion. Alternatively, motion detector103may only produce a motion status indicating that the vehicle is in motion once the motion has surpassed a certain threshold, such as, for example a pre-determined speed, a predetermined acceleration or a combination thereof. If the vehicle is not moving or alternatively, has not exceeded a movement threshold, motion detector103may produce a motion status indicating that the vehicle is not in motion. Alternatively, motion detector may not produce a signal, which may be interpreted by MCU104to mean that the vehicle was not in motion and that the motion status should so indicate. MCU104may continuously or periodically monitor motion detector103for vehicle movement.

If a disabling signal has been broadcast and mobile device102is in range of the broadcasting signal, the software residing on mobile device102will alter the system configuration of mobile device102to restrict the user's ability to perform certain tasks including, for example, using the keyboard, using the touch screen or sending and/or receiving text messages, email messages, and/or phone calls. Use of some features, such as maps, dialing 911 and voice-activated calling can still be permitted. Broadcast of the disabling signal will continue or be performed at regular intervals (e.g. every 20 seconds) until the motion status indicates that that the vehicle is not in motion. The disabling signal can be, for example, a Bluetooth® low energy beacon signal (or transmission). The broadcasting range of the disabling signal can be limited to only encompass the driver area or vehicle (e.g. 3-10 feet). The broadcast of the disabling signal may continue after the motion status of the vehicle becomes non-moving for a predetermined amount of time (e.g. one to two minutes).

MCU104ensures disabling device101's operation by checking for connectivity to other disabling device components and for installation in and/or removal from a vehicle. This can be accomplished with internal programming and/or a physical or software switch. As an example of monitoring for installation and/or removal, if disabling device is attached to the vehicle (for example, on the windshield) using suction cups or adhesive or another similar mounting mechanism, a pressure switch can be used to detect installation and/or removal of the disabling device. In addition, MCU104monitors power source108for the status of the power supply.

System100can further include monitoring party's device111. Cellular radio105communicates wirelessly with monitoring party's device111. Monitoring party's device111may monitor the status of disabling device101and the app running on mobile device102. Cellular radio105may use GSM cellular modules (global system for mobile communications) or any other known transmission service. Cellular radio105may include a subscriber identity module (SIM) card and may be equipped with SMS text capabilities. Cellular radio105, at the direction of MCU104, can send messages/alerts, such as, for example a short message service (SMS) push notification comprising an identifier of the disabling device to monitoring party's device111, when certain events occur. For example, a message may be sent when disabling device101is activated, when disabling device101is removed from the vehicle, when the available power in power source108or back-up power source112is low or when cellular radio105has low cellular service as well as periodic alerts showing the device is working properly. The app running on mobile device102can also send notifications, such as ‘app installed’, ‘app disabled’, or ‘app functioning normally’, to monitoring party's device111. The notifications from the app may include mobile device102's phone number. A monitoring party may be an insurance company or a concerned parent. Monitoring party's device111enables the monitoring party to receive information verifying that disabling device101and the app running on mobile device102are operational.

Power source108may be, for example, a battery or a long life battery. Power source108may provide power to MCU104, motion detector103, cellular radio105, and/or signal generator106if the element itself is not self-powered or it may serve as a secondary power source for any self-powered element. Disabling system may be hard-wired to the vehicle it is installed in. In this case, MCU104, motion detector103, cellular radio105, and/or signal generator106may draw power from the vehicle's power source. Power source108may then be used in the event disabling device101is removed from the vehicle or the hard-wired connection is severed.

Backup power source, which may be for example a backup battery, may provide power to MCU104and cellular radio105to allow cellular radio105to send an alert to monitoring party111when MCU104detects that the power available in power source108is low. Backup power source112may also provide power to signal generator106and motion detector103when the power available from power source108is low to allow disabling device101to operate continuously.

MCU104may also store information related to the driver/user or to the vehicle disabling device101is attached to. Such information may include the account number and name of the user and the make, year, and/or model of the vehicle. Such information can also be transmitted, as needed, via cellular radio103to, for example, monitoring party's device111, or via signal generator106to, for example, mobile device102.

Solar cell109may be used to recharge power source108and/or backup power source112.

System100may further include remote server113having a database (whitelist) containing a list of media access control (MAC) addresses or other unique identifier assigned to the signal generator of each disabling device in operation. Remote server113may be in bi-directional, wireless communication with mobile device102. This list, or whitelist, can be queried by the software running on a mobile device to determine if a received disabling signal is coming from a valid source. This may prevent a bad actor from attempting to disable a phone by sending a disabling signal from an unauthorized device.

An embodiment of a method of the present invention from the perspective of disabling device101(method300) is illustrated in the flowchart inFIG.2with reference to disabling device101ofFIG.1. As shown in operation305, disabling device101receives the motion status of the vehicle from motion detector103. If, in operation315, the motion status indicates that the vehicle is not in motion, disabling device101continues receiving the motion status from motion detector103. Otherwise, disabling device101, in operation320, transmits a disabling signal using signal generator106. Disabling device101then repeats the process. Optionally, disabling device101can, in operation325, wait a predetermined amount of time before repeating this process.

Another embodiment of a method of the present invention from the perspective of disabling device101(method400) is illustrated in the flowchart ofFIG.3with reference to disabling device101ofFIG.1. As shown, method400begins initially with the disabling signal turned off In operation405, disabling device101receives the motion status of the vehicle from motion detector103. If, in operation415, the motion status indicates that the vehicle is in motion, disabling device101, in operation420, transmits a disabling signal using wireless signal generator106. Broadcast of the disabling signal continues while the vehicle is in motion. Disabling device101then repeats the process. Optionally, disabling device101can, in operation425, wait a predetermined amount of time before repeating this process. If, in operation415, the motion status indicates that the vehicle is not in motion, then disabling device101, in operation430, determines if the disabling signal is turned on. If the disabling signal is off, then the process repeats. If the disabling signal is on, then it is turned off in operation440and the process repeats. Optionally, disabling device101can, in operation440, wait a predetermined amount of time before turning off disabling signal and repeating the process. Waiting a predetermined amount of time (e.g. one to two minutes) before repeating the process, allows for the host vehicle to come to a temporary stop (e.g. at a stop light or stop sign) without allowing the mobile device to return to normal operations.

Optionally, MCU104can monitor signal generator106for endpoint connectivity (e.g. a connection to mobile device102) if such connectivity is possible with the technology used for the signal generator. Once a connection is established, disabling device101can send a wireless signal or notification to mobile device102.

As discussed previously, cellular radio105, at the direction of MCU104, can send alerts, such as, for example a short message service (SMS) push notification, to monitoring party's device111, when certain events occur. An embodiment of a portion of the method of the present invention that issues these alerts is shown inFIG.4. In operation505of method500, disabling device101determines whether a monitoring event has occurred. If, in operation510, a monitoring event has occurred, an alert will be transmitted to monitoring party's device111in operation515. If, in operation510, no monitoring event has occurred, then disabling device101continues checking for a monitoring event.

Monitoring events may include disabling device101being removed from a host vehicle, disabling device101being secured in a host vehicle, or disabling device101losing power for a predetermined amount of time. A method of monitoring these three exemplary events (method600) is illustrated inFIG.5with reference to disabling device101ofFIG.1. In operation605, disabling device101determines if it has been newly installed in a host vehicle. If disabling device has been newly installed, then, in operation610, cellular radio105sends an alert to monitoring party's device111indicating that the initial installation of disabling device101is complete. If the disabling device has not been newly installed, then, in operation615, disabling device101determines if it has been removed from the vehicle. If disabling device101has been removed from the vehicle, then, in operation620, cellular radio105sends an alert to monitoring party's device111indicating that disabling device101has been removed. If disabling device101is still installed, disabling device101determines if it has lost power from power source108for a predetermined amount of time (e.g. two minutes). This can be determined by monitoring MCU104's interface with power source108. If disabling device101has lost power from power source108for a predetermined amount of time, cellular radio105, which may be powered by backup power source112or its own power source, sends an alert to monitoring party's device111indicating that disabling device101has lost power from power source108. If disabling device101has not lost power from power source108, then the process continues monitoring for disabling device101's removal from the vehicle (operation615) and disabling device101losing power from power source108(operation625).

Disabling device101can also perform a self-test to ensure that its disabling signal is transmitting and power source108is operational. A monitoring alert can then be sent at pre-determined intervals (e.g. every 30 days) to monitoring party's device111indicating that disabling device101is functioning properly.

FIG.6is a block diagram of a mobile device102according to an exemplary embodiment, which may be, for example mobile device102as described above and shown inFIGS.1and10. The exemplary mobile device includes memory701in communication with processor702and user interface module703, which includes touch-screen display module704and tactile feedback module705, all of which is described in further detail below. Mobile device102may also comprise transceiver706for receiving or transmitting, or both, wireless signals707, which may be any radio frequency (RF) signals such as WiFi, Bluetooth®, Low Energy Bluetooth®; Near Field Communications (NFC) or any other RF signal of any type or nature; optical signals such as infrared optical signals; or any other wireless signals known in the art. Processor702may be in communication with transceiver707. In an embodiment, wireless signal707may be the wireless signal1202as depicted inFIG.10. It should be understood, that a mobile device as illustrated and hereinafter described is merely illustrative of a mobile device that could benefit from embodiments of the invention and, therefore, should not be taken to limit the scope of the invention. While one embodiment of the mobile device is illustrated for purposes of example, other types of mobile electronic devices, such as, but not limited to, mobile phones, smart phones, portable digital assistants (PDAs), tablets, mobile computing devices, gaming devices, laptop computers, media players, and other types of mobile electronic systems, may readily employ embodiments of the invention.

An embodiment of the method of the present invention from the perspective of mobile device102(method800) is illustrated in the flowchart ofFIG.7. As shown in operation805, software running on mobile device102polls for a disabling signal. Once a disabling signal is received (in operation810), the software determines if it is valid in operation815. If the disabling signal is not valid, the software continues polling for a disabling signal in operation805. If the disabling signal is valid, then the software alters the system configuration of mobile device102in operation820to restrict the user's ability to perform certain tasks. These tasks may include, for example, using the keyboard, or sending and/or receiving text messages and/or email messages, placing and/or receiving phone calls, or placing and/or receiving phone calls when not in hands-free mode. In operation825, the software continues to poll for a disabling signal. In operation830, the software determines if the same disabling signal has been received within a predetermined period of time. If it has, then the software continues to poll for a disabling signal (operation825). If the same disabling signal has not been received within a predetermined period of time, the software restores the system configuration of mobile device102in operation835.

Another embodiment of the method of the present invention from the perspective of mobile device102(method900) is illustrated in the flowchart ofFIG.8. As shown in operation905, software running on mobile device102polls for a disabling signal. The disabling signal, which may be, for example a Bluetooth® beacon signal (or transmission), includes identifiers, such as, for example, a universally unique identifiers (UUID) or a MAC address. Once a disabling signal is received (in operation910), the software queries, in operation920, a locally located list of known identifiers to determine, in operation940, if the identifier received in the disabling signal is contained in the local list. If the identifier is not in the local list, then, in operation945, a remotely located list of known identifiers is queried to determine, in operation950, if the identifier is contained in the remote list. If the identifier is not contained in the remote list, the identifier is not recognized and the software continues polling for a disabling signal in operation905. If the MAC address is contained in the remote list, the MAC address is added to the local list in operation955. Once a valid MAC address has been confirmed, the software alters the system configuration of mobile device102in operation920to restrict the user's ability to perform certain tasks including, for example, using the keyboard, or sending and/or receiving text messages, email messages, and/or phone calls. In operation925, the software continues to poll for a disabling signal. In operation930, the software determines if the same network identifier has been received within a predetermined period of time. If it has, then the software continues to poll for a disabling signal (operation925). If the same disabling signal has not been received within a predetermined period of time, the software restores the system configuration of mobile device102in operation935.

Like disabling device101, the software running on mobile device102can protect itself from tampering and verify its own operable status by transmitting alerts, such as, for example, a SMS push notification containing, for example, mobile device102's phone number, to monitoring party's device111. Monitoring events can include the software being installed on mobile device102or the software being disabled. The software running on mobile device102may comprise two separate apps—a primary system app and a secondary app. The primary app may be monitored by the secondary app. The purpose of the secondary app is to send an alert to monitoring party device111in the event of removal of the primary app. The primary app also monitors the secondary app and sends an alert to monitoring party device111in the event of removal of the secondary app. In this respect the primary and secondary app independently monitor each other for removal, making the app portion of the system self-protecting. Methods (methods1000,1015, and1030) that issue exemplary alerts originating from mobile device102are shown inFIGS.9A through9C.

As shown inFIG.9A, method1000determines, in operation1005, if the primary app and the secondary app have been newly installed on mobile device102. If the software has been newly installed, then, in operation1010, mobile device102sends an alert to monitoring party's device111indicating that the software installation has been completed.

As shown inFIG.9B, method1015determines, in operation1020, if the primary app or the secondary app has been removed. If either app has been removed, then, in operation1025, an alert is sent to monitoring party's device111indicating that the primary app or secondary app (as applicable) has been removed.

As shown inFIG.9C, method1030determines, in operation1035, if mobile device102has received a disabling signal. If no disabling signal has been received, then the software continues to wait for the disabling signal to arrive. If a disabling signal has been received, then, in operation1040, the software determines if it is the first time mobile device102is receiving the disabling signal. If this is not the first time mobile device102has received a disabling signal, then the system configuration of mobile device102is altered in operation1050. If this is the first time mobile device102has received a disabling signal, then, in operation1045, an alert is sent to monitoring party's device111indicating that the software installation and communication with disabling device102has completed. The system configuration of mobile device102is then altered in operation1050. After mobile device102's system configuration has been altered, the software, in operation1055, determines if a predetermined amount of time (e.g. two minutes) has lapsed since the mobile device102received a disabling signal. If not, then the software continues polling for a disabling signal in operation1035. If the predetermined amount of time has lapsed then the software restores the system configuration of mobile device102in operation1060.

The software running on mobile device102can also perform a self-test to ensure that it is receiving disabling signals at expected intervals (e.g. every 15 seconds or twice within any 30 second window) and it is altering mobile device102's system configuration upon receipt of a valid disabling signal. A monitoring alert can then be sent at pre-determined intervals (e.g. every 30 days) to monitoring party's device111indicating that the software running on mobile device102is functioning properly.

The following are exemplary scenarios demonstrating pre-operational functionality of embodiments of the present invention.

Disabling device set-up—the disabling device is intact but not in the vehicle:Motion detector: Inactive.Power source (battery): Inactive (charged).MCU: Inactive.Signal generator: Inactive.Cellular Radio: Inactive.

Disabling device installed—the vehicle is not moving:Motion detector: Power available from disabling device's battery.Power source (battery): Inactive (charging).MCU: Recognizes connectivity to the motion detector via internal programming, physical switch or software switch and initiates a monitoring alert (e.g. push notification); analyzes the signal from the motion detector for the motion status of the vehicle.Signal generator: Inactive.Cellular Radio: Transmits ‘Disabling device installed’ alert to the monitoring party's device.

Vehicle not moving; disabling device installed:Motion detector: Active.Power source (battery): Active.MCU: Active; monitoring the motion detector.Signal generator: Inactive.Cellular Radio: Inactive.

Disabling device is removed:Motion detector: Inactive.Power source (battery): Active (discharging); Powers the MCU and the cellular radio.MCU: Recognizes the lack of connectivity of the disabling device to the vehicle via internal programming, physical switch or software switch; engages the battery and initiates a monitoring alert indicating that the disabling device has been disconnected.Signal generator: Inactive.Cellular Radio Transmits monitoring alert (e.g. push notification) indicating that the disabling device has been disconnected to the monitoring party's device.

The following are exemplary scenarios demonstrating operational functionality of embodiments of the present invention.

Vehicle not moving; disabling device installed:Motion detector: Power available from disabling device battery.Power source (battery): Active (charging).MCU: Recognizes connectivity to the motion detector via internal programming, physical switch or software switch; analyzes the signal from the motion detector for the motion status of the vehicle.Signal generator: Inactive.Cellular Radio: Inactive.

Vehicle moving; disabling device installed:Interface: Power available from the disabling device's battery.Power source (battery): Active.MCU: Recognizes connectivity to the motion detector via internal programming, physical switch, or software switch; analyzes the signal from the motion detector for the motion status of the vehicle.Signal generator: Sends the disabling signal nominally every twenty (2) seconds.Cellular Radio: Inactive.

Vehicle in motion or not in motion; disabling device installed; power from (primary) battery is unavailable for a predetermined period of time (e.g. two minutes):Motion detector: Inactive.Power source (Primary battery): Inactive; not charging.Backup Power Source (Back-up battery): Active; Powers the MCU and the cellular radio.MCU: Recognizes connectivity to the motion detector via internal programming, physical switch or software switch; analyzes the signal from the motion detector for the motion status of the vehicle; recognizes (primary) battery power is unavailable for predetermined period of time (e.g. two minutes); initiates monitoring alert (e.g. push notification) indicating no (primary) battery power to the disabling device for a defined time period.Signal generator: Inactive.Cellular Radio: Transmits a monitoring alert to the monitoring party's device that the (primary) battery is not operational.

Exemplary Electronic Devices—Mobile Device and Disabling Device

FIGS.1and6are block diagrams illustrating exemplary embodiments of disabling device101and mobile device102, respectively. It should be understood these exemplary embodiments are merely illustrative of disabling device and a mobile device that could benefit from embodiments of the invention and, therefore, should not be taken to limit the scope of the invention. Moreover, the apparatus of an example embodiment need not be the entire device, but may be a component or group of components of the device in other example embodiments.

Regarding mobile devices, devices may readily employ embodiments of the invention regardless of their intent to provide mobility. In this regard, even though embodiments of the invention are described in conjunction with a mobile device, it should be understood that embodiments of the invention may be utilized in conjunction with a variety of other electronic devices.

The devices may each comprise a processor or other processing circuitry. As used in this application, the term ‘circuitry’ refers to at least all of the following: hardware-only implementations (such as implementations in only analog and/or digital circuitry) and to combinations of circuits and software and/or firmware such as to a combination of processors or portions of processors/software including digital signal processor(s), software, and memory(ies) that work together to cause an apparatus, such as a mobile phone or tablet, to perform various functions and to circuits, such as a microprocessor(s) or portion of a microprocessor(s), that require software or firmware for operation, even if the software or firmware is not physically present. This definition of ‘circuitry’ applies to all uses of this term in this application, including in any claims.

As a further example, as used in this application, the term “circuitry” would also cover an implementation of merely a processor, multiple processors, gate arrays, programmable logic arrays, field-programmable gate arrays, discrete logic or a portion of a processor and its (or their) accompanying software and/or firmware.

Further, the processor(s) may comprise functionality to operate one or more software programs, which may be stored in memory and which may, among other things, cause the processor to implement at least one embodiment including, for example, one or more of the functions described above. The mobile device may comprise a user interface for providing output and/or receiving input. The mobile device may comprise an output device such as a ringer, a conventional earphone and/or speaker, a microphone, a display, and/or a user input interface, which are coupled to the processor. The user input interface, which allows the electronic device to receive data, may comprise means, such as one or more devices that may allow the electronic device to receive data, such as a keypad, a touch display, for example if the display comprises touch capability, and/or the like.

The devices may comprise a physical memory device including, in one embodiment, volatile memory, such as volatile Random Access Memory (RAM) including a cache area for the temporary storage of data. The devices may also comprise other physical memory, for example, non-volatile memory, which may be embedded and/or may be removable. The non-volatile memory may comprise an EEPROM, flash memory or the like. The memories may store any of a number of pieces of information, executable instructions, and data. The information, executable instructions and data may be used by the devices to implement one or more functions of the devices.

A further embodiment of the system and method of the invention is depicted inFIG.10, which depicts an exemplary embodiment of the system andFIG.11, which depicts an exemplary flow diagram of the steps of the method. Referring now toFIGS.10and11, at least one disabling device101transmits a disabling signal1202within and to the extent of a geographic area1200, which has a boundary1201. A plurality of disabling devices, which need not be co-located, may be used in order to create any desired shape or size geographic area1200. Geographic area1200is depicted as circular in shape inFIG.10, but this shape is exemplary only. Geographic area1200may be any arbitrary shape in which disabling signal1202is able to be received by mobile device102. Geographic area1200is not limited to a plane, in other words confined to only two dimensions, but may be any three dimensional shape. As such, geographic area1200could be, by way of example and not limitation, a hemispherical shape. In such cases the boundary1201of geographic area1200would comprise a surface area. Whether two dimensional or three dimensional, geographic area1200may take any arbitrary shape by the appropriate placement of antennas through which disabling signal1202is transmitted or by shaping antenna radiation patterns using techniques known in the art, or alternatively, a plurality of disabling devices101mtransmit disabling signals, in order to achieve a predefined desired geographic area1200and boundary1201. Geographic area1200and disabling signal, or signals,1202may be utilized to provide mobile device functionality limitation as described herein for any area or volume in which mobile device limitation is desired, for example work areas designated by employers such as retail store sales floors, warehouses, factory and manufacturing facilities, and offices; areas related to vehicular traffic such as crosswalks and intersections; areas in which danger may be present requiring that a mobile device user stay alert and not be distracted by the use of a mobile device such as subway or train platforms; areas in which specified activities are expected to occur requiring a mobile device user to pay attention and not be distracted by the use of a mobile device such as classrooms or lecture halls; and any other geographic area in which it is desired that person's situational awareness not be diminished or subject to distraction. When mobile device102is positioned outside the boundary of geographic area1201such as in position A, the receiver of mobile device102does not receive disabling signal1202transmitted by disabling device101, because mobile device102is outside boundary1201and is therefore outside the coverage area of disabling signal1202. As mobile device102is moved to the boundary1201along direction A′ to position B, corresponding to step1100ofFIG.11, the receiver of mobile device102is able to receive disabling signal1202because it has moved across the boundary1201into geographic area1200and is therefore within the coverage area of disabling signal1202. When mobile device102crosses boundary1201into geographic area1200the Device Owner Application on mobile device102receives disabling signal1202, corresponding to step1101ofFIG.11, and responds to disabling signal1202by altering mobile device102configuration as described elsewhere herein, corresponding to step1102ofFIG.11, which may include, but is not limited to restricting the mobile device's ability to send and receive text messages and email messages; restricting the mobile device's ability to respond to user input; restricting the mobile device's ability to place and receive phone calls; restricting the mobile device's ability to place and receive phone calls requiring user interaction with a touch screen or a keyboard of the mobile device; restricting the mobile device's ability to utilize a web browser application; restricting the mobile device's web browser from accessing predetermined web sites; and any other predetermined restriction of mobile device functionality as may be desired. As mobile device102moves along direction B′ to position C, the mobile device receiver continues to receive disabling signal1202because mobile device102is still in geographic area1200, i.e., mobile device102remains within the geographic area boundary1201, and the Device Owner Application on mobile device102continues to limit the functionality of mobile device102as described, corresponding to the “YES” leg of the decision step1103ofFIG.11. As mobile device102moves along direction C′ to position D, the mobile device receiver continues to receive disabling signal1202, and the Device Owner Application on mobile device102continues to receive disabling signal1202and to limit the functionality of mobile device102in response to disabling signal1202as described, however as mobile device moves along direction D′ and exits geographic area1200by crossing geographic area boundary1202as it moves towards position E, mobile device102is no longer able to receive disabling signal1202, corresponding to the “NO” leg of step1103ofFIG.11. When mobile device102moves out of geographic area1200by crossing boundary1201moving in direction D′ towards position E and is no longer able to receive disabling signal1202, the Device Owner Application on mobile device102responds to loss of disabling signal1202by returning mobile device102to the unaltered configuration, corresponding to step1104ofFIG.11, allowing the mobile device to operate normally, meaning the Device Owner Application no longer restricts the functionality of mobile device102. In an embodiment, the disabling device101depicted inFIG.10may comprise only a signal generator; or a signal generator and an MCU, or any other subset of the functions depicted inFIG.1.

Although the figures of the drawings illustrate example embodiments of a disabling device and mobile device, respectively, which may perform the functions of the system and method of the embodiments of the invention, the disabling device and the mobile device as depicted in the figures are each merely an example of devices that may utilize embodiments of the invention.

Embodiments of the invention may be implemented in software, firmware, programmable logic such field programmable gate arrays, hardware, application logic or a combination of software, hardware, and application logic. The software application logic and/or hardware may reside on the apparatus, a separate device, or a plurality of separate devices. If desired, part of the software application logic and/or hardware may reside on the apparatus, part of the software, application logic and/or hardware may reside on a separate device, and part of the software, application logic and/or hardware may reside on a plurality of separate devices. In an example embodiment, the application logic, software or an instruction set is maintained on any one of various conventional computer-readable media. In the context of this document, a “computer-readable medium” may be any tangible media or means that can contain, or store the instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer, with two examples of a computer described and depicted inFIGS.1and6. A computer readable medium may comprise a computer-readable storage medium that may be any tangible media or means that can contain or store the instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer. Any software or application described herein may comprise computer executable instructions for carrying out the steps described herein, and such instructions shall be non-transitory in nature and reside in computer readable media.

The geographic area may be shaped such that functionality of mobile device102is restricted in virtually any desired area or volume. For example, the Device Owner Application of the invention could be installed on mobile devices of employees of a certain workplace or on the mobile devices of students of a school to avoid distracting features of the mobile device such as texting, internet, or photography. The disabling signal would be transmitted by an existing or previously installed signal generator as described above; however, the mechanism triggering the disabling signal would be, for example, an physical on/off switch or a software timer that turned the disabling signal on and off at certain times of the day, rather than motion status of the vehicle. The app would query a list, or whitelist, of media access control (MAC) addresses to determine if a received disabling signal is coming from a valid source as described previously. Alerts such as the removal of the primary app or secondary app would be communicated to a monitoring party (such as the workplace owner) device as described previously.

Having now described the invention, the construction, the operation and use of preferred embodiments thereof, and the advantageous new and useful results obtained thereby, the new and useful constructions, and reasonable mechanical equivalents thereof obvious to those skilled in the art, are set forth in the appended claims.