US7769394B1 - System and method for location-based device control - Google Patents
System and method for location-based device control Download PDFInfo
- Publication number
- US7769394B1 US7769394B1 US11/539,546 US53954606A US7769394B1 US 7769394 B1 US7769394 B1 US 7769394B1 US 53954606 A US53954606 A US 53954606A US 7769394 B1 US7769394 B1 US 7769394B1
- Authority
- US
- United States
- Prior art keywords
- mobile device
- component
- hardware component
- location
- request
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active, expires
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M1/00—Substation equipment, e.g. for use by subscribers
- H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
- H04M1/724—User interfaces specially adapted for cordless or mobile telephones
- H04M1/72448—User interfaces specially adapted for cordless or mobile telephones with means for adapting the functionality of the device according to specific conditions
- H04M1/72457—User interfaces specially adapted for cordless or mobile telephones with means for adapting the functionality of the device according to specific conditions according to geographic location
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M1/00—Substation equipment, e.g. for use by subscribers
- H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
- H04M1/724—User interfaces specially adapted for cordless or mobile telephones
- H04M1/72448—User interfaces specially adapted for cordless or mobile telephones with means for adapting the functionality of the device according to specific conditions
- H04M1/72463—User interfaces specially adapted for cordless or mobile telephones with means for adapting the functionality of the device according to specific conditions to restrict the functionality of the device
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M1/00—Substation equipment, e.g. for use by subscribers
- H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
- H04M1/724—User interfaces specially adapted for cordless or mobile telephones
- H04M1/72448—User interfaces specially adapted for cordless or mobile telephones with means for adapting the functionality of the device according to specific conditions
- H04M1/72463—User interfaces specially adapted for cordless or mobile telephones with means for adapting the functionality of the device according to specific conditions to restrict the functionality of the device
- H04M1/724631—User interfaces specially adapted for cordless or mobile telephones with means for adapting the functionality of the device according to specific conditions to restrict the functionality of the device by limiting the access to the user interface, e.g. locking a touch-screen or a keypad
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2250/00—Details of telephonic subscriber devices
- H04M2250/52—Details of telephonic subscriber devices including functional features of a camera
Definitions
- mobile electronic devices such as a cellular telephone, a personal digital assistant (PDA), a pager, a mobile computer, a digital camera, a digital music player, a digital calculator, an electronic key fob, or a mobile device comprising some combination of these devices.
- PDA personal digital assistant
- Such devices are often capable of a multitude of functions some of which comprise recording audio, video, or taking still images, as well as providing an alert by way of a vibrator or speaker, or wireless communicating with other devices or networks, among others.
- systems comprise a locating subsystem, a server, and a mobile device comprising a component manager.
- the component manager allows modifications to the operation of components of the mobile device based on a location provided by the locating subsystem.
- the component manager also provides confirmation of the modified operation of the components of the mobile device to the server.
- inventions are computer-readable media storing a component manager software program that, when executed by the processor of a mobile device, causes the processor to receive requests to modify operation of components of the mobile device from a requestor, modify the operation of the components of the mobile device based on the requests by way of operating system drivers, and provide confirmation of the modified operation of the components of the mobile device to the requestor.
- Yet other embodiments are methods comprising defining a restricted geographic region and a rule set corresponding to the restricted geographic region defining mobile device components that may or may not be enabled within the restricted geographic region, transmitting requests to modify operation of the components of a mobile device in the restricted geographic region, and receiving confirmation of the modified operation of the components of the mobile device.
- FIG. 1 is a wireless communications system in accordance with embodiments of the invention.
- FIG. 2 is a block diagram of an illustrative mobile device.
- FIG. 3 is a block diagram of an illustrative software environment comprising component manager software.
- FIG. 4 is a first system in accordance with embodiments of the invention configured for location-based device control.
- FIG. 5 is a first method in accordance with embodiments of the invention configured for location-based device control.
- FIG. 6 is a second method in accordance with embodiments of the invention configured for location-based device control.
- a mobile device within or near a restricted geographic region, such as the locker room of an athletic club, receives requests transmitted by a location-based device control system.
- the requests may comprise requests to disable certain hardware components of the mobile device (e.g., the video camera component) while the device is in or near the restricted geographic region.
- the mobile device is configured to provide confirmation of completion of the requests.
- the confirmation may be provided via the mobile device itself, via a server, via an audible tone or indication, or by some alternative means, and the confirmation may be further verified by an individual enforcing device compliance. In situations wherein confirmation is not provided, the mobile device may be confiscated by the individual providing enforcement, or the mobile device may be completely locked while the device is within or near the restricted region.
- FIG. 1 shows a wireless communications system comprising an illustrative mobile device 100 .
- device 100 may take various forms such as a personal digital assistant (PDA), a mobile computer, a digital camera, a digital music player, a digital calculator, or an electronic key fob for keyless entry.
- PDA personal digital assistant
- the mobile device is not a general purpose computing device like a notebook or tablet computer, but rather is a special-purpose communications device such as a mobile phone, pager, or PDA.
- Mobile device 100 comprises a display 102 and a touch-sensitive surface or keys 104 with which to interact with a user.
- the mobile device 100 may present options for the user to select, controls for the user to actuate, and/or cursors or other indicators for the user to direct.
- the mobile device 100 may further accept data entry from the user, comprising numbers to dial or various other values for configuring the operation of the mobile device 100 .
- Mobile device 100 may further execute one or more software or firmware applications in response to user commands or in response to external commands, requests, or other stimuli. These applications may configure the mobile device 100 to perform various customized functions.
- a component manager software application configured to control specific components of the mobile device 100 based on a rule set defining whether components of the mobile device may be enabled within a restricted geographic region.
- the components comprise one or more selected from the group: a camera component; an audio recording component; a video recording component; a networking component; an audible or inaudible output component such as a speaker or a vibrator; a graphical user interface; an input component such as a keypad or a microphone; or a port such as an infrared (IR) or universal serial bus (USB) port, among others.
- IR infrared
- USB universal serial bus
- the restricted geographic region may comprise a business location comprising a retail or wholesale store, an athletic club, a non-profit operation, a government entity or alternative place of business or a portion of the business location such as a locker room of the athletic club.
- Shown on the display 102 is an illustrative screen 106 indicating that the mobile device 100 is within the restricted geographic region that defines a restricted area of operation and showing indicators 108 to confirm to the user that specific components of the mobile device 100 have been disabled.
- the indicators 108 may confirm that specific components have been enabled, suspended, or had their operation otherwise modified.
- the location of the mobile device 100 may be determined by any one or more of a number of available position determination methods, such as by a global positioning system (GPS) comprising a GPS satellite 120 and/or triangulation from multiple base stations or cell towers via wireless communications between the mobile device 100 and a cell tower 110 or a wireless network access node.
- GPS global positioning system
- the cell tower 110 (or wireless network access node) is coupled to a wired network 112 such as a telephone network, the Internet, or other high-speed network via a mobile switching center and/or an Ethernet connection.
- the mobile device 100 may be in communication with various servers such as a local server 114 or a backend server 116 .
- the servers may provide such information as parameters (e.g., coordinate values) that define the restricted geographic region.
- the restricted geographic region may be defined by local antennas (e.g., circumscribing the restricted geographic region), or by other available means.
- the backend server 116 may be a wireless carrier server and may store the rule set that defines which components of the mobile device 100 may or may not be enabled within the restricted geographic region.
- the local server 114 may be within or near to the restricted geographic region that defines the restricted area of operation, and the local server 114 may communicate with the backend server 116 through the wired network 112 to retrieve the rule set.
- the rule set may be stored on the local server 114 .
- the local server 114 may provide local control of a location-based device control system deployed at a certain geographic location. In other embodiments, the local server 114 may provide local confirmation of modified operation of a component of the mobile device 100 .
- functions performed by the backend server 116 may be performed by the local server 114 for example, to reduce system latency. In other exemplary embodiments, functions performed by the local server 114 may be performed by the backend server 116 for example, to reduce system costs associated with implementing a local server 114 . In yet other embodiments, certain functions may be spread between the local server 114 and the backend server 116 .
- the component manager software application may receive requests transmitted (or broadcast) by the local server 114 or the backend server 116 to disable components of the mobile device 100 as prescribed by the rule set.
- mobile devices 100 that are non-compatible with a location-based device control system are not able to comply with the requests.
- users may manually deny requests to disable. Whether due to non-compatible mobile devices 100 or users who manually deny requests to disable, devices that do not comply with the requests may be confiscated while the user is within the restricted geographic region.
- some contemplated location-based device control systems may completely lock a mobile device 100 while the device is within or near the restricted geographic region without regard to specific device location or specific hardware components. In this case the mobile device will be unlocked only upon leaving the restricted geographic region.
- the component manager software application is what is utilized to disable the appropriate components of the mobile device 100 via operating system drivers within a digital signal processor (as described below).
- the user of the mobile device 100 may manually disable the components via the keys 104 in response to the requests.
- the restricted geographic region may be circumscribed by a periphery region wherein the mobile device 100 may receive requests transmitted by the local server 114 or the backend server 116 to enable components that were previously disabled while within the restricted geographic region, such as when a user is leaving the restricted geographic region by way of the periphery region carrying a mobile device with a disabled component.
- the restricted geographic region may be defined to be the locker rooms of the club, while the periphery region may be the rest of the athletic club excluding the locker rooms. In an alternative embodiment, the restricted geographic region may be the entire athletic club, while the periphery region may comprise a parking lot of the club.
- Requests to enable components may be manually fulfilled by the user or may be fulfilled by the component manager software application via the operating system drivers. In some exemplary embodiments, the user may manually request the enabling of components of the mobile device 100 upon leaving a restricted geographic region. In such a case, before enabling the components via the operating system drivers, the component manager software application is configured to validate that the mobile device 100 is not within a restricted geographic region whose rule set prohibits the enabling of the components that the user is requesting to enable.
- the component manager software application is also configured to provide confirmation in response to requests to enable components of the mobile device 100 .
- the requestor is the user of the mobile device (e.g., wherein the user manually selects components to be disabled or enabled by way of the keys 104 ) the component manager software application may provide confirmation by way of the indicators 108 ( FIG. 1 ).
- the component manager software application may provide confirmation by way of a database entry within one or both of the local server 114 or the backend server 116 ; an audible tone, audible message, or other audible indication generated by the mobile device 100 , the local server 114 , or the backend server 116 ; a visual indication via a graphical user interface electrically coupled to the local server 114 or the backend server 116 ; or other alternative means.
- confirmation may still be provided by way of the indicators 108 ( FIG. 1 ). For embodiments comprising non-compatible devices, it may not be possible to provide confirmation as described herein, thus appropriate actions should be taken such as confiscating or completely locking the mobile device (as discussed above).
- confirmation of device compliance may be enforced by a security guard (or other individual) stationed at an entrance to a restricted geographic region.
- a security guard or other individual stationed at an entrance to a restricted geographic region.
- the intellectual property may comprise technical publications, information contained in laboratory notebooks, files and/or data contained within company computer networks, confidential information presented in meetings, or other sensitive information.
- Attempts to compromise the privacy of such information may comprise any of several unauthorized activities (using an enabled mobile device) such as audio recordings of meetings via the audio recording component of the mobile device, photographic or video recordings of documents such as laboratory notebooks or unpublished publications via the camera or video recording components, downloading of files/data from a computer or from a computer network via an input/output (I/O) interface such as the IR or USB ports, or other unauthorized activities utilizing the mobile device.
- I/O input/output
- a security guard may be stationed at the entrance to such a high-tech research installation in order to check identification badges, for example, to protect against unauthorized entry into the facility.
- the security guard may enforce compliance of mobile devices entering the facility.
- the user of a mobile device may show the device to the security guard so that the security guard may visually confirm device compliance.
- the security guard may interface with a graphical user interface (e.g., a computer monitor) electrically coupled to the local server 114 , wherein the graphical user interface provides a visual indication as to compliance of the mobile device.
- a mobile device may download a specific “ringer of the day” or other ringtone from the local server 114 or the backend server 116 that will be played by those devices that are in compliance.
- the security guard may take appropriate action (e.g., confiscate or completely lock the mobile device) if a ringtone is not heard or if an incorrect ringtone (for a given day) is heard.
- the security guard may request a user's cellular telephone number (or other mobile device identification such as a serial number, for example) which may then be entered into the local server 114 by the security guard.
- the local server 114 may then cross-reference the telephone number to a database (or other record) comprising a listing of devices that have been successfully disabled, and if there is a match, the device is thus found to be in compliance and the user may proceed to enter the facility.
- the database comprising the listing of successfully disabled devices may be stored within the local server 114 or the backend server 116 .
- the total number of individuals entering or leaving a facility make enforcement of device compliance a difficult task, or there may be situations where certain unscrupulous individuals attempt to circumvent detection by the security guard or other controls that are in place.
- a secure facility may be forced to hire additional security, confiscate all electronic devices, or completely lock or disable all devices within or near the restricted region without regard to specific device location or specific hardware components. In this case the mobile device will be unlocked only upon leaving the restricted region.
- FIG. 2 shows a block diagram of the illustrative mobile device 100 .
- Mobile device 100 comprises a digital signal processor (DSP) 202 and a memory 204 .
- illustrative mobile device 100 may further comprise an antenna and front end unit 206 , a radio frequency (RF) transceiver 208 , an analog baseband processing unit 210 , a microphone 212 , an earpiece speaker 214 , a headset port 216 , an input/output interface 218 , a memory card 220 , a universal serial bus (USB) port 222 , an infrared (IR) port 224 , a vibrator 226 , a keypad 228 , a liquid crystal display (LCD) with a touch sensitive surface 230 , a touch screen/LCD controller 232 , a charge-coupled device (CCD) camera 234 , a camera controller 236 , and a GPS sensor 238 .
- RF radio frequency
- the DSP 202 or some other form of controller or central processing unit operates to control the various components of the mobile device in accordance with embedded software or firmware stored in memory 204 .
- the component manager software operates cooperatively with operating system drivers within the DSP 202 (as described below) to enable or disable components of the mobile device 100 based on the location of the mobile device and on the rule set governing that location.
- the functionality of the component manager software may be implemented as a separate hardware component integrated into the mobile device 100 that electrically couples to the DSP 202 to ensure compliance with a location-based control system.
- the DSP 202 may also execute other applications stored in memory 204 or made available via information carrier media such as portable data storage media like memory card 220 or via wired or wireless network communications.
- the application software may comprise a compiled set of machine-readable instructions that configure the DSP to provide the desired functionality, or the application software may be high-level software instructions to be processed by an interpreter or compiler to indirectly configure the DSP.
- An antenna and front end unit 206 may be provided to convert between wireless signals and electrical signals, enabling mobile device 100 to send and receive information from a cellular network or some other available wireless communications network. Communications between the mobile device 100 via the front end unit 206 and multiple cell towers with directional detection and/or relative strength sensing may be used to triangulate the position of the mobile device 100 for use by the component manager software.
- the RF transceiver 208 provides frequency shifting, converting received RF signals to baseband and converting baseband transmit signals to RF.
- Analog baseband processing unit 210 may provide channel equalization and signal demodulation to extract information from received signals, may modulate information to create transmit signals, and may provide analog filtering for audio signals.
- the analog baseband processing unit 210 may have ports for connecting to a built-in microphone 212 and earpiece speaker 214 that enable the mobile device 100 to be used as a mobile phone.
- the analog baseband processing unit 210 may further include a port for connecting to a headset or other hands-free microphone and speaker configuration.
- DSP 202 may send and receive digital communications with a wireless network via analog baseband processing unit 210 .
- these digital communications may provide Internet connectivity, enabling a user to gain access to content on the Internet and to send and receive email or text messages.
- An input/output interface 218 interconnects the DSP 202 and various memories and interfaces.
- Memory 204 and removable memory card 220 may provide software and data to configure the operation of DSP 202 .
- the interfaces may be a USB interface 222 and an infrared (IR) port 224 .
- the USB interface may enable the mobile device 100 to function as a peripheral device to exchange information with a personal computer or other computer system.
- the IR port 224 and other optional ports such as a Bluetooth interface or an IEEE 802.11 compliant wireless interface may enable the mobile device 100 to communicate wirelessly with other nearby mobile devices and/or wireless base stations.
- the mobile device 100 may communicate with multiple local wireless base stations having antennas with directional detection and/or relative strength sensing to triangulate the position of the mobile device 100 for use by the component manager software.
- the component manager software may be provided with the position of the mobile device 100 as determined by GPS sensor 238 , which is coupled to DSP 202 to decode global positioning system signals.
- Input/output interface 218 may further connect the DSP 202 to a vibrator 226 that, when triggered, causes the mobile device 100 to vibrate.
- the vibrator 226 may serve as a mechanism for silently alerting the user to any of various events such as an incoming call, a new text message, an appointment reminder, or a component that has had its operation modified.
- a keypad 228 couples to the DSP 202 via interface 218 to provide one mechanism for the user to make selections, enter information, and otherwise provide input to the mobile device 100 .
- Another input mechanism may be a touch screen display 230 , which may also display text and/or graphics to the user.
- a display controller 232 couples the DSP 202 to the touch screen display 230 .
- the CCD camera 234 enables the mobile device 100 to take digital pictures.
- the DSP 202 communicates with the camera 234 via a camera controller 236 .
- the mobile device may also be able to capture video clips through the CCD camera 234 by employing a video application specific integrated circuit (ASIC).
- ASIC video application specific integrated circuit
- Various other peripherals may also be included to provide additional functions, e.g., radio and television reception.
- FIG. 3 illustrates a software environment 302 that may be implemented by the DSP 202 .
- the DSP 202 executes operating system software that provides a platform from which the rest of the software operates.
- the operating system software provides drivers 304 for the mobile device hardware that may be used to enable or disable individual hardware components (the components as shown in FIG. 2 , among others).
- the drivers 304 are provided with standardized interfaces that are accessible to application software and other software of the operating system.
- the drivers 304 may interface with component manager software 306 , wherein the component manager software 306 may have overriding control (over other application software or other software of the operating system) of the hardware components of the mobile device 100 (based on the location of the mobile device and on rule set governing that location).
- the component manager software 306 may operate as part of the operating system or as separate software operating within the DSP 202 .
- each hardware component of the mobile device 100 has an associated register that controls its operation, wherein the register comprises a bit for enabling or disabling the hardware component, and wherein the DSP 202 sets or resets the enabling/disabling bit accordingly.
- the DSP 202 may access (via the input/output interface 218 ) a hardware control unit that distributes a clock signal to each hardware component, and the DSP 202 may direct the hardware control unit to start or stop the clock signal to a particular component, thus enabling or disabling a particular hardware component.
- the DSP 202 may set a status word in memory 204 (or other memory) that indicates that a particular hardware component is enabled or disabled.
- the DSP 202 may check the status word in memory 204 whenever access requests are made to particular hardware components by application programs, and the DSP 202 can disregard any access requests made to hardware components that have been indicated as being disabled by the status word and return an error message to the application programs requesting access to that particular hardware component.
- Other methods of enabling or disabling the hardware components as known in the art may also be used.
- the component manager software 306 may interface with other software on the mobile device 100 such as location monitor software 312 and rules monitor software 314 to determine the location of the mobile device 100 and the particular rule set that applies to a given restricted geographic region, respectively.
- the location monitor software 312 may periodically update the location of the mobile device 100 and provide such information to the component manager software 306 based on a determination of location as made by the GPS sensor 238 , by triangulation, or otherwise (as described above).
- the rules monitor software 314 may periodically update the rule set via wireless communication with the local server 114 or the backend server 116 and provide such information to the component manager software 306 .
- the updating of the rule set may be synchronous (or nearly synchronous) with the updating of the location of the mobile device 100 so that the rule set remains applicable to the current location of the mobile device 100 .
- the component manager software 306 takes appropriate actions such as enabling or disabling particular hardware components via commands to the drivers 304 that directly control the mobile device hardware.
- the component manager software 306 further comprises a request handler 308 and a confirmation handler 310 .
- the request handler 308 processes requests to disable or enable a particular device component, wherein the request may be transmitted (or broadcast) by the local server 114 or the backend server 116 , or may be manually entered by the user of the mobile device 100 . In the case of multiple or simultaneous requests, the request handler 308 may queue the requests and process them in the order received. In alternative embodiments, the requests may each have an assigned priority, and the requests may thus be processed according to their priority.
- the confirmation handler 310 provides confirmation in response to a request (as described above with respect to the component manager software application). In some embodiments, the confirmation handler 310 may provide notification of a denied request such as when the user of the mobile device 100 requests to enable a hardware component that is not allowed by the rule set corresponding to the current location of the mobile device 100 .
- the location-based control of mobile devices may be a service offered to customers (e.g., businesses comprising a particular restricted geographic region in which they would like to restrict the use of certain components of mobile devices) by wireless carriers, and the confirmation handler 310 would serve to provide paying customers with confirmation that their location-based device control system is properly disabling or enabling specified components of mobile devices within the defined restricted geographic region of their business.
- mobile devices may be configured to only recognize requests from specific “trusted” sources, such as a specific paying customer (e.g., an athletic club) or a specific wireless carrier.
- requests to disable or enable components of mobile devices from unrecognized third parties will be disregarded.
- some mobile devices may not be compatible with a system implementing location-based control of mobile devices. Such non-compatible devices would not return the expected confirmation and in some embodiments may instead result in an error message being returned to the requestor, thus allowing businesses to take appropriate action such as confiscating the non-compatible mobile devices while the user is within the restricted geographic region.
- some contemplated systems may completely lock a mobile device while the device is within or near the restricted geographic region without regard to specific device location or specific hardware components. In this case the mobile device will be unlocked only upon leaving the restricted geographic region.
- FIG. 4 shows a first system embodiment for location-based device control of components of a mobile device 100 .
- FIG. 4 shows embodiments wherein the mobile device 100 is entering a restricted geographic region.
- a service requestor 402 e.g., a business location such as an athletic club
- a component manager 401 on the mobile device 100 retrieves a signal from a locating subsystem 405 (that indicates the location of the mobile device 100 ) as shown by arrow 403 , wherein the locating subsystem may comprise the GPS satellite 120 ( FIG. 1 ), the cell tower 110 ( FIG. 1 ) or base stations, or local antennas, among others.
- the component manager 401 may provide the location of the mobile device 100 to the service requestor 402 as shown by arrow 404 , and if the mobile device 100 is within the restricted geographic region as defined by the parameters, the service requestor 402 may request that certain components of the mobile device 100 be disabled as defined by the rule set stored on the local server of the service requestor 402 .
- the rule set may have been previously retrieved from the backend server 407 as shown by arrow 409 .
- the service requestor 402 may send a message to the backend server 407 asking the backend server 407 to directly make the request to disable components of the mobile device 100 as shown by dashed arrow 406 .
- the component manager 401 may provide the location of the mobile device 100 directly to the backend server 407 as shown by dashed arrow 406 . Again, if the mobile device is within the region as defined by the parameters, the backend server 407 may request that certain components of the mobile device 100 be disabled based upon the rule set stored on the backend server 407 .
- the backend server 407 may have previously retrieved the rule set from the local server of the service requestor 402 as shown by arrow 409 , for example, in embodiments where rules have been entered locally by an individual interfacing with the local server of the service requestor 402 and wherein those rules have been subsequently transferred to the backend server 407 .
- the service requestor 402 or the backend server 407 may request the disabling of the components of the mobile device 100 based on the rule set without knowing the location of the mobile device 100 .
- the component manager 401 may subsequently determine the location of the mobile device 100 (as described above) and process the request if the mobile device 100 is within the restricted geographic region as defined by the parameters (i.e., the request is valid). Otherwise, the request is invalid and is disregarded.
- the requests are processed by the component manager 401 .
- the component manager 401 by way of the drivers 304 ( FIG. 3 ) provided by the operating system running on the DSP 202 ( FIG. 2 ), proceeds to disable hardware components 416 of the mobile device 100 as shown by arrow 408 .
- the component manager 401 provides confirmation to the service requester 402 (as shown by arrow 404 ), to the backend server 407 (as shown by dashed arrow 406 ), or to the mobile device itself via the display 102 ( FIG. 1 ) by way of the indicators 108 ( FIG. 1 ).
- confirmation may be provided via other hardware components of the mobile device such as the vibrator 226 ( FIG.
- the local server of the service requestor 402 or the backend server 407 may store information regarding which components of which mobile devices within the restricted geographic region have been confirmedly disabled so that superfluous requests are not made. In some embodiments, information may be stored within the memory of the mobile device 100 regarding disabled components of the device so that superfluous requests are not processed.
- the service requestor may register with a wireless carrier providing the system for location-based device control of components of a mobile device. Also in block 502 , the service requestor sets up parameters that define the restricted geographic region that is to be monitored by the location-based device control system, and the service requestor defines the rule set that prescribes which components of the mobile device 100 may or may not be enabled within the restricted geographic region defined by the parameters.
- a mobile device 100 enters the restricted geographic region, wherein the mobile device may be powered on or powered off. If the mobile device is powered off, the service requestor may request the user of the mobile device 100 to power on the mobile device 100 in block 506 .
- Such a request may come from an individual, a posted sign, an electronic display, an audible recording, or other available method.
- the mobile device 100 may receive requests in block 508 to disable particular hardware components. If the mobile device 100 was powered on upon entering the restricted geographic region, the process proceeds directly from block 504 to receiving requests to disable components in block 508 .
- the requests to disable in block 508 may be manual requests made by the user of the mobile device 100 or they may be requests transmitted by the location-based device control system (e.g., by the service requestor/local server or by the backend server).
- the component manager in block 510 will retrieve the location of the mobile device 100 and determine which components should be disabled as prescribed by the rule set. If the mobile device 100 determines that it is not within the restricted geographic region, then the request will be disregarded. In some exemplary embodiments, the component manager may receive the request to disable after it has provided the service requestor or the backend server with the location of the mobile device 100 and it has been determined that the mobile device 100 is within the restricted geographic region. In block 512 , the component manager, by way of the drivers 304 provided by the operating system running on the DSP 202 , disables the components of the mobile device 100 as prescribed by the rule set.
- the user of the mobile device 100 may manually request the disabling of components of the mobile device 100 in block 508 .
- determination of the location of the mobile device 100 (block 510 ) may be skipped and the components may be directly disabled by the component manager in block 512 as indicated in FIG. 5 .
- the component manager confirms fulfillment of the request to disable to the user of the mobile device, to the service requestor, or to the backend server.
- the mobile device 100 may receive transmitted (or broadcast) requests to enable components that were previously disabled while within the restricted geographic region. Requests to enable components may be manually fulfilled by the user or may be fulfilled by the component manager via the operating system drivers.
- the component manager 401 on the mobile device 100 retrieves a signal from the locating subsystem 405 (that indicates the location of the mobile device 100 ) as shown by arrow 403 .
- the component manager 401 may provide the location of the mobile device 100 to the service requestor 402 as shown by arrow 404 , and if the mobile device 100 is within the periphery region, the service requestor 402 may request that previously disabled components of the mobile device 100 be enabled.
- the service requestor 402 may send a message to the backend server 407 asking the backend server 407 to directly make the request to enable components of the mobile device 100 as shown by dashed arrow 406 .
- the component manager 401 may provide the location of the mobile device 100 directly to the backend server 407 as shown by dashed arrow 406 . Again, if the mobile device is within the periphery region, the backend server 407 may request that previously disabled components of the mobile device 100 be enabled. In yet other embodiments, the service requestor 402 or the backend server 407 may request the enabling of the components of the mobile device 100 without knowing the location of the mobile device. Upon receiving such a request, the component manager 401 may subsequently determine the location of the mobile device 100 (as described above) and process the request if the mobile device is within the periphery region or if the mobile device is outside the restricted geographic region entirely (i.e., the request is valid).
- the user may manually make requests to the component manager 401 to enable components of the mobile device 100 via the keypad 228 ( FIG. 2 ) or the touch screen LCD 230 ( FIG. 2 ) as shown by arrow 410 .
- the component manager before enabling the components via the operating system drivers, the component manager is configured to validate that the mobile device is not within a restricted geographic region (via locating system 405 as shown by arrow 403 ) whose rule set prohibits the enabling of the components that the user is requesting to enable.
- Valid requests are processed by the component manager 401 .
- the component manager 401 by way of the drivers 304 ( FIG. 3 ) provided by the operating system running on the DSP 202 ( FIG. 2 ), proceeds to enable hardware components 416 of the mobile device 100 as shown by arrow 408 .
- the component manager 401 provides confirmation to the service requestor 402 (as shown by arrow 404 ), to the backend server 407 (as shown by dashed arrow 406 ), or to the mobile device itself via the display 102 ( FIG. 1 ) by way of the indicators 108 ( FIG. 1 ).
- confirmation made be provided via other hardware components of the mobile device such as the vibrator 226 ( FIG. 2 ), the speaker 214 ( FIG. 2 ), or others.
- the mobile device 100 may receive requests to enable previously disabled hardware components.
- the component manager in block 604 , by way of the location monitor and the rules monitor, will retrieve the location of the mobile device 100 and determine if the request is valid given the current location of the device and the prescribed rule set for that location. If the mobile device 100 is within a restricted geographic region (i.e., the request is invalid), then the request will be disregarded and the components will remain disabled in block 608 . If the request is valid, then the previously disabled components will be enabled in block 606 . The enabling is done by the component manager by way of the drivers 304 provided by the operating system running on the DSP 202 . After enabling of the components is complete, in block 610 , the component manager confirms fulfillment of the request to enable to the user of the mobile device, to the service requestor, or to the backend server.
- the computer-readable medium may be, for example, a volatile memory, a non-volatile memory, a compact disc read only memory (CDROM), an electrically erasable programmable read only memory (EEPROM), a hard disk, a floppy disk, an optical disk, network connectivity devices, other ROM or RAM devices, or the like.
Abstract
Description
Claims (20)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/539,546 US7769394B1 (en) | 2006-10-06 | 2006-10-06 | System and method for location-based device control |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/539,546 US7769394B1 (en) | 2006-10-06 | 2006-10-06 | System and method for location-based device control |
Publications (1)
Publication Number | Publication Date |
---|---|
US7769394B1 true US7769394B1 (en) | 2010-08-03 |
Family
ID=42358887
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/539,546 Active 2028-01-26 US7769394B1 (en) | 2006-10-06 | 2006-10-06 | System and method for location-based device control |
Country Status (1)
Country | Link |
---|---|
US (1) | US7769394B1 (en) |
Cited By (51)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090132093A1 (en) * | 2007-08-21 | 2009-05-21 | Motorola, Inc. | Tactile Conforming Apparatus and Method for a Device |
US20090128376A1 (en) * | 2007-11-20 | 2009-05-21 | Motorola, Inc. | Method and Apparatus for Controlling a Keypad of a Device |
US20090156265A1 (en) * | 2007-12-17 | 2009-06-18 | Embarq Holdings Company Llc | System and method for ringtone shuffle |
US20090181716A1 (en) * | 2008-01-11 | 2009-07-16 | Benco David S | Network disabling of mobile phone camera operation |
US20100017874A1 (en) * | 2008-07-16 | 2010-01-21 | International Business Machines Corporation | Method and system for location-aware authorization |
US20100201536A1 (en) * | 2009-02-10 | 2010-08-12 | William Benjamin Robertson | System and method for accessing a structure using a mobile device |
US20100201482A1 (en) * | 2009-02-10 | 2010-08-12 | William Benjamin Robertson | System and method for accessing a structure using a mobile device |
US20100330958A1 (en) * | 2007-08-01 | 2010-12-30 | Nxp B.V. | Mobile communication device and method for disabling applications |
US20110065417A1 (en) * | 2006-10-20 | 2011-03-17 | Research In Motion Limited | Method and apparatus to control the use of applications on handheld devices based on network service |
WO2013011512A1 (en) * | 2011-07-20 | 2013-01-24 | Israel Aerospace Industries Ltd. | System and method for location based control of elements of a mobile communication device |
US20130257780A1 (en) * | 2012-03-30 | 2013-10-03 | Charles Baron | Voice-Enabled Touchscreen User Interface |
US8589991B2 (en) | 2010-12-14 | 2013-11-19 | Microsoft Corporation | Direct connection with side channel control |
US20140082754A1 (en) * | 2012-09-14 | 2014-03-20 | Hon Hai Precision Industry Co., Ltd. | Electronic device and method for disabling application and hardware |
US20140087758A1 (en) * | 2011-05-23 | 2014-03-27 | Wise-Sec Ltd. | Positioning systems and methods and location based modification of computing device applications |
US8781500B1 (en) | 2012-09-12 | 2014-07-15 | Google Inc. | Proprietor-controlled location-based setting of notification policies |
US8792429B2 (en) | 2010-12-14 | 2014-07-29 | Microsoft Corporation | Direct connection with side channel control |
WO2014171970A1 (en) | 2013-04-15 | 2014-10-23 | Sky Socket, Llc | Location-based functionality restrictions |
WO2014179750A1 (en) * | 2013-05-02 | 2014-11-06 | Sky Socket, Llc | Location-based configuration profile toggling |
WO2014179743A1 (en) * | 2013-05-02 | 2014-11-06 | Sky Socket, Llc | Time-based configuration policy toggling |
US8923770B2 (en) | 2010-12-09 | 2014-12-30 | Microsoft Corporation | Cognitive use of multiple regulatory domains |
US8948382B2 (en) | 2010-12-16 | 2015-02-03 | Microsoft Corporation | Secure protocol for peer-to-peer network |
US20150050922A1 (en) * | 2013-08-19 | 2015-02-19 | American Megatrends, Inc. | Mobile device security system |
US8971841B2 (en) | 2010-12-17 | 2015-03-03 | Microsoft Corporation | Operating system supporting cost aware applications |
US9003480B2 (en) | 2013-03-13 | 2015-04-07 | International Business Machines Corporation | Classifying files on a mobile computer device |
US20150248565A1 (en) * | 2012-11-20 | 2015-09-03 | Hitachi, Ltd. | Information system, control program for management server, and control program for mobile device |
US9224096B2 (en) | 2012-01-08 | 2015-12-29 | Imagistar Llc | System and method for item self-assessment as being extant or displaced |
US9294545B2 (en) | 2010-12-16 | 2016-03-22 | Microsoft Technology Licensing, Llc | Fast join of peer to peer group with power saving mode |
US9336635B2 (en) | 2009-02-10 | 2016-05-10 | Yikes Llc | System and method for permitting secure access to a structure |
US9367975B2 (en) | 2009-02-10 | 2016-06-14 | Yikes Llc | System for permitting secure access to a restricted area |
US20160234218A1 (en) * | 2015-02-10 | 2016-08-11 | Fu Tai Hua Industry (Shenzhen) Co., Ltd. | Application permission management device and method therefor |
US9542203B2 (en) | 2010-12-06 | 2017-01-10 | Microsoft Technology Licensing, Llc | Universal dock for context sensitive computing device |
US9552491B1 (en) * | 2007-12-04 | 2017-01-24 | Crimson Corporation | Systems and methods for securing data |
US9558604B2 (en) | 2009-02-10 | 2017-01-31 | Yikes Llc | System for permitting secure access to a restricted area |
US9584964B2 (en) | 2014-12-22 | 2017-02-28 | Airwatch Llc | Enforcement of proximity based policies |
US20170148244A1 (en) * | 2012-08-16 | 2017-05-25 | Schlage Lock Company Llc | Usage of gps on door security |
US9681471B1 (en) | 2016-08-31 | 2017-06-13 | Bank Of America Corporation | Pairing of devices for activation/deactivation of a paired device |
EP3195180A4 (en) * | 2014-09-18 | 2018-04-18 | Booz, Allen & Hamilton | System and method for location-based security |
US20180176770A1 (en) * | 2007-10-26 | 2018-06-21 | At&T Intellectual Property I, L.P. | Standardized control of wireless devices |
US20180184361A1 (en) * | 2015-03-31 | 2018-06-28 | Hewlett-Packard Development Company, L.P. | Application access based on network |
US10061933B1 (en) | 2018-01-09 | 2018-08-28 | Booz Allen Hamilton Inc. | System and method for controlling the power states of a mobile computing device |
US10085135B2 (en) | 2009-02-10 | 2018-09-25 | Yikes Llc | Radio frequency patch antenna and system for permitting secure access to a restricted area |
US10366582B2 (en) | 2016-06-21 | 2019-07-30 | Bank Of America Corporation | Devices and systems for detecting unauthorized communication of data from a magnetic stripe device or embedded smart chip device |
US10602317B2 (en) * | 2018-05-01 | 2020-03-24 | Satellite Tracking Of People Llc | System and method of alternative tracking upon disabling of monitoring device |
CN111124524A (en) * | 2018-10-30 | 2020-05-08 | 中兴通讯股份有限公司 | Business service framework configuration method, system, terminal and storage medium |
US10818119B2 (en) | 2009-02-10 | 2020-10-27 | Yikes Llc | Radio frequency antenna and system for presence sensing and monitoring |
US10951541B2 (en) | 2012-02-14 | 2021-03-16 | Airwatch, Llc | Controlling distribution of resources on a network |
US11082355B2 (en) | 2012-02-14 | 2021-08-03 | Airwatch, Llc | Controllng distribution of resources in a network |
US11196752B2 (en) * | 2019-01-22 | 2021-12-07 | Lenovo Enterprise Solutions (Singapore) Pte. Ltd. | Multifactor authentication for secure management of data center assets from a mobile device |
US11658971B1 (en) * | 2010-08-23 | 2023-05-23 | Amazon Technologies, Inc. | Virtual firewalls for multi-tenant distributed services |
US11824644B2 (en) | 2013-03-14 | 2023-11-21 | Airwatch, Llc | Controlling electronically communicated resources |
US11843988B2 (en) | 2018-03-19 | 2023-12-12 | Simpello Llc | System and method for detecting presence within a strictly defined wireless zone |
Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040102197A1 (en) * | 1999-09-30 | 2004-05-27 | Dietz Timothy Alan | Dynamic web page construction based on determination of client device location |
US20040131014A1 (en) * | 2003-01-03 | 2004-07-08 | Microsoft Corporation | Frame protocol and scheduling system |
US20050192029A1 (en) * | 2004-02-26 | 2005-09-01 | Siemens Aktiengesellschaft | Method and device for determining the position of terminal in a cellular mobile radio network |
US20050202832A1 (en) * | 2004-03-15 | 2005-09-15 | Isaias Sudit | Privacy features for a cellular telephone location identification system |
US6950662B2 (en) * | 2002-03-28 | 2005-09-27 | Intel Corporation | Wireless communication device and method for automatic time updates in personal information management applications |
US7194278B1 (en) | 2000-11-20 | 2007-03-20 | Sprint Spectrum L.P. | Method and system for managing device functions based on location |
US20080043689A1 (en) * | 2004-07-13 | 2008-02-21 | Sbc Knowledge Ventures, Lp | System and method for location based policy management |
-
2006
- 2006-10-06 US US11/539,546 patent/US7769394B1/en active Active
Patent Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040102197A1 (en) * | 1999-09-30 | 2004-05-27 | Dietz Timothy Alan | Dynamic web page construction based on determination of client device location |
US7194278B1 (en) | 2000-11-20 | 2007-03-20 | Sprint Spectrum L.P. | Method and system for managing device functions based on location |
US6950662B2 (en) * | 2002-03-28 | 2005-09-27 | Intel Corporation | Wireless communication device and method for automatic time updates in personal information management applications |
US20040131014A1 (en) * | 2003-01-03 | 2004-07-08 | Microsoft Corporation | Frame protocol and scheduling system |
US20050192029A1 (en) * | 2004-02-26 | 2005-09-01 | Siemens Aktiengesellschaft | Method and device for determining the position of terminal in a cellular mobile radio network |
US20050202832A1 (en) * | 2004-03-15 | 2005-09-15 | Isaias Sudit | Privacy features for a cellular telephone location identification system |
US20080043689A1 (en) * | 2004-07-13 | 2008-02-21 | Sbc Knowledge Ventures, Lp | System and method for location based policy management |
Cited By (97)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20110065417A1 (en) * | 2006-10-20 | 2011-03-17 | Research In Motion Limited | Method and apparatus to control the use of applications on handheld devices based on network service |
US9537866B2 (en) * | 2006-10-20 | 2017-01-03 | Blackberry Limited | Method and apparatus to control the use of applications based on network service |
US20100330958A1 (en) * | 2007-08-01 | 2010-12-30 | Nxp B.V. | Mobile communication device and method for disabling applications |
US8811971B2 (en) * | 2007-08-01 | 2014-08-19 | Nxp B.V. | Mobile communication device and method for disabling applications |
US20090132093A1 (en) * | 2007-08-21 | 2009-05-21 | Motorola, Inc. | Tactile Conforming Apparatus and Method for a Device |
US20180176770A1 (en) * | 2007-10-26 | 2018-06-21 | At&T Intellectual Property I, L.P. | Standardized control of wireless devices |
US10743172B2 (en) * | 2007-10-26 | 2020-08-11 | At&T Intellectual Property I, L.P. | Standardized control of wireless devices |
US20090128376A1 (en) * | 2007-11-20 | 2009-05-21 | Motorola, Inc. | Method and Apparatus for Controlling a Keypad of a Device |
US8866641B2 (en) | 2007-11-20 | 2014-10-21 | Motorola Mobility Llc | Method and apparatus for controlling a keypad of a device |
US9552491B1 (en) * | 2007-12-04 | 2017-01-24 | Crimson Corporation | Systems and methods for securing data |
US8145278B2 (en) * | 2007-12-17 | 2012-03-27 | Embarq Holdings Company Llc | System and method for ringtone shuffle |
US20090156265A1 (en) * | 2007-12-17 | 2009-06-18 | Embarq Holdings Company Llc | System and method for ringtone shuffle |
US9014764B2 (en) | 2007-12-17 | 2015-04-21 | Centurylink Intellectual Property Llc | System and method for selecting ringtones |
US8219144B2 (en) * | 2008-01-11 | 2012-07-10 | Alcatel Lucent | Disabling of mobile phone camera operation by video-restricted location device |
US20090181716A1 (en) * | 2008-01-11 | 2009-07-16 | Benco David S | Network disabling of mobile phone camera operation |
US20100017874A1 (en) * | 2008-07-16 | 2010-01-21 | International Business Machines Corporation | Method and system for location-aware authorization |
US9367975B2 (en) | 2009-02-10 | 2016-06-14 | Yikes Llc | System for permitting secure access to a restricted area |
US10085135B2 (en) | 2009-02-10 | 2018-09-25 | Yikes Llc | Radio frequency patch antenna and system for permitting secure access to a restricted area |
US10818119B2 (en) | 2009-02-10 | 2020-10-27 | Yikes Llc | Radio frequency antenna and system for presence sensing and monitoring |
US9129450B2 (en) | 2009-02-10 | 2015-09-08 | Yikes Llc | System and method for accessing a structure using a mobile device |
US20100201482A1 (en) * | 2009-02-10 | 2010-08-12 | William Benjamin Robertson | System and method for accessing a structure using a mobile device |
US20100201536A1 (en) * | 2009-02-10 | 2010-08-12 | William Benjamin Robertson | System and method for accessing a structure using a mobile device |
US8791790B2 (en) | 2009-02-10 | 2014-07-29 | Yikes Llc | System and method for accessing a structure using a mobile device |
US9558604B2 (en) | 2009-02-10 | 2017-01-31 | Yikes Llc | System for permitting secure access to a restricted area |
US9336635B2 (en) | 2009-02-10 | 2016-05-10 | Yikes Llc | System and method for permitting secure access to a structure |
US9361741B2 (en) | 2009-02-10 | 2016-06-07 | Yikes Llc | System and method for accessing a structure using a mobile device |
US11704955B2 (en) | 2009-02-10 | 2023-07-18 | Simpello Llc | Radio frequency antenna and system for presence sensing and monitoring |
US11658971B1 (en) * | 2010-08-23 | 2023-05-23 | Amazon Technologies, Inc. | Virtual firewalls for multi-tenant distributed services |
US9870028B2 (en) | 2010-12-06 | 2018-01-16 | Microsoft Technology Licensing, Llc | Universal dock for context sensitive computing device |
US9542203B2 (en) | 2010-12-06 | 2017-01-10 | Microsoft Technology Licensing, Llc | Universal dock for context sensitive computing device |
US9178652B2 (en) | 2010-12-09 | 2015-11-03 | Microsoft Technology Licensing, Llc | Cognitive use of multiple regulatory domains |
US8923770B2 (en) | 2010-12-09 | 2014-12-30 | Microsoft Corporation | Cognitive use of multiple regulatory domains |
US9801074B2 (en) | 2010-12-09 | 2017-10-24 | Microsoft Technology Licensing, Llc | Cognitive use of multiple regulatory domains |
US9462479B2 (en) | 2010-12-09 | 2016-10-04 | Microsoft Technology Licensing, Llc | Cognitive use of multiple regulatory domains |
US9813466B2 (en) | 2010-12-14 | 2017-11-07 | Microsoft Technology Licensing, Llc | Direct connection with side channel control |
US8589991B2 (en) | 2010-12-14 | 2013-11-19 | Microsoft Corporation | Direct connection with side channel control |
US8792429B2 (en) | 2010-12-14 | 2014-07-29 | Microsoft Corporation | Direct connection with side channel control |
US9450995B2 (en) | 2010-12-14 | 2016-09-20 | Microsoft Technology Licensing, Llc | Direct connection with side channel control |
US10575174B2 (en) | 2010-12-16 | 2020-02-25 | Microsoft Technology Licensing, Llc | Secure protocol for peer-to-peer network |
US8948382B2 (en) | 2010-12-16 | 2015-02-03 | Microsoft Corporation | Secure protocol for peer-to-peer network |
US9294545B2 (en) | 2010-12-16 | 2016-03-22 | Microsoft Technology Licensing, Llc | Fast join of peer to peer group with power saving mode |
US9998522B2 (en) | 2010-12-16 | 2018-06-12 | Microsoft Technology Licensing, Llc | Fast join of peer to peer group with power saving mode |
US9596220B2 (en) | 2010-12-16 | 2017-03-14 | Microsoft Technology Licensing, Llc | Secure protocol for peer-to-peer network |
US10044515B2 (en) | 2010-12-17 | 2018-08-07 | Microsoft Technology Licensing, Llc | Operating system supporting cost aware applications |
US8971841B2 (en) | 2010-12-17 | 2015-03-03 | Microsoft Corporation | Operating system supporting cost aware applications |
US9338309B2 (en) | 2010-12-17 | 2016-05-10 | Microsoft Technology Licensing, Llc | Operating system supporting cost aware applications |
US9008610B2 (en) | 2010-12-17 | 2015-04-14 | Microsoft Corporation | Operating system supporting cost aware applications |
RU2597885C2 (en) * | 2011-05-23 | 2016-09-20 | Уайс-Сек Лтд. | Positioning systems and methods and location based modification of computing device applications |
US20140087758A1 (en) * | 2011-05-23 | 2014-03-27 | Wise-Sec Ltd. | Positioning systems and methods and location based modification of computing device applications |
WO2013011512A1 (en) * | 2011-07-20 | 2013-01-24 | Israel Aerospace Industries Ltd. | System and method for location based control of elements of a mobile communication device |
US11195396B2 (en) | 2012-01-08 | 2021-12-07 | Imagistar Llc | Anticipation and warning of potential loss/theft for portable personal items |
US9786145B2 (en) | 2012-01-08 | 2017-10-10 | Imagistar Llc | System and method for item self-assessment as being extant or displaced |
US10373462B2 (en) | 2012-01-08 | 2019-08-06 | Imagistar Llc | Intelligent personal item transport containers for owner-customized monitoring, of owner-selected portable items for packing and transport by the owner |
US10354505B2 (en) | 2012-01-08 | 2019-07-16 | Imagistar Llc | System and method for item self-assessment as being extant or displaced |
US9224096B2 (en) | 2012-01-08 | 2015-12-29 | Imagistar Llc | System and method for item self-assessment as being extant or displaced |
US10951541B2 (en) | 2012-02-14 | 2021-03-16 | Airwatch, Llc | Controlling distribution of resources on a network |
US11483252B2 (en) | 2012-02-14 | 2022-10-25 | Airwatch, Llc | Controlling distribution of resources on a network |
US11082355B2 (en) | 2012-02-14 | 2021-08-03 | Airwatch, Llc | Controllng distribution of resources in a network |
CN104205010A (en) * | 2012-03-30 | 2014-12-10 | 英特尔公司 | Voice-enabled touchscreen user interface |
US20130257780A1 (en) * | 2012-03-30 | 2013-10-03 | Charles Baron | Voice-Enabled Touchscreen User Interface |
US10186099B2 (en) * | 2012-08-16 | 2019-01-22 | Schlage Lock Company Llc | Usage of GPS on door security |
US20170148244A1 (en) * | 2012-08-16 | 2017-05-25 | Schlage Lock Company Llc | Usage of gps on door security |
US8781500B1 (en) | 2012-09-12 | 2014-07-15 | Google Inc. | Proprietor-controlled location-based setting of notification policies |
US20140082754A1 (en) * | 2012-09-14 | 2014-03-20 | Hon Hai Precision Industry Co., Ltd. | Electronic device and method for disabling application and hardware |
US20150248565A1 (en) * | 2012-11-20 | 2015-09-03 | Hitachi, Ltd. | Information system, control program for management server, and control program for mobile device |
US9003480B2 (en) | 2013-03-13 | 2015-04-07 | International Business Machines Corporation | Classifying files on a mobile computer device |
US11824644B2 (en) | 2013-03-14 | 2023-11-21 | Airwatch, Llc | Controlling electronically communicated resources |
WO2014171970A1 (en) | 2013-04-15 | 2014-10-23 | Sky Socket, Llc | Location-based functionality restrictions |
EP2974394A4 (en) * | 2013-04-15 | 2016-10-26 | Airwatch Llc | Location-based functionality restrictions |
US20140330945A1 (en) * | 2013-05-02 | 2014-11-06 | Sky Socket, Llc | Location-based Configuration Policy Toggling |
US9219741B2 (en) | 2013-05-02 | 2015-12-22 | Airwatch, Llc | Time-based configuration policy toggling |
US11204993B2 (en) | 2013-05-02 | 2021-12-21 | Airwatch, Llc | Location-based configuration profile toggling |
US9703949B2 (en) | 2013-05-02 | 2017-07-11 | Airwatch, Llc | Time-based configuration profile toggling |
US9426162B2 (en) * | 2013-05-02 | 2016-08-23 | Airwatch Llc | Location-based configuration policy toggling |
US10303872B2 (en) | 2013-05-02 | 2019-05-28 | Airwatch, Llc | Location based configuration profile toggling |
WO2014179743A1 (en) * | 2013-05-02 | 2014-11-06 | Sky Socket, Llc | Time-based configuration policy toggling |
WO2014179750A1 (en) * | 2013-05-02 | 2014-11-06 | Sky Socket, Llc | Location-based configuration profile toggling |
US9723487B2 (en) * | 2013-08-19 | 2017-08-01 | American Megatrends, Inc. | Mobile device security system |
US20150050922A1 (en) * | 2013-08-19 | 2015-02-19 | American Megatrends, Inc. | Mobile device security system |
EP3195180A4 (en) * | 2014-09-18 | 2018-04-18 | Booz, Allen & Hamilton | System and method for location-based security |
US10244347B2 (en) | 2014-09-18 | 2019-03-26 | Booz Allen Hamilton Inc. | System and method for location-based security |
US10194266B2 (en) | 2014-12-22 | 2019-01-29 | Airwatch Llc | Enforcement of proximity based policies |
US9584964B2 (en) | 2014-12-22 | 2017-02-28 | Airwatch Llc | Enforcement of proximity based policies |
US9832203B2 (en) * | 2015-02-10 | 2017-11-28 | Fu Tai Hua Industry (Shenzhen) Co., Ltd. | Application permission management device and method therefor |
US20160234218A1 (en) * | 2015-02-10 | 2016-08-11 | Fu Tai Hua Industry (Shenzhen) Co., Ltd. | Application permission management device and method therefor |
US10492121B2 (en) * | 2015-03-31 | 2019-11-26 | Hewlett-Packard Development Company, L.P. | Application access based on network |
US20180184361A1 (en) * | 2015-03-31 | 2018-06-28 | Hewlett-Packard Development Company, L.P. | Application access based on network |
US10939298B2 (en) | 2015-03-31 | 2021-03-02 | Hewlett-Packard Development Company, L.P. | Application access based on network |
US10366582B2 (en) | 2016-06-21 | 2019-07-30 | Bank Of America Corporation | Devices and systems for detecting unauthorized communication of data from a magnetic stripe device or embedded smart chip device |
US9681471B1 (en) | 2016-08-31 | 2017-06-13 | Bank Of America Corporation | Pairing of devices for activation/deactivation of a paired device |
US10372923B2 (en) | 2018-01-09 | 2019-08-06 | Booz Allen Hamilton Inc. | System and method for controlling the power states of a mobile computing device |
US10061933B1 (en) | 2018-01-09 | 2018-08-28 | Booz Allen Hamilton Inc. | System and method for controlling the power states of a mobile computing device |
US11843988B2 (en) | 2018-03-19 | 2023-12-12 | Simpello Llc | System and method for detecting presence within a strictly defined wireless zone |
US10972875B2 (en) | 2018-05-01 | 2021-04-06 | Satellite Tracking Of People Llc | System and method of alternative tracking upon disabling of monitoring device |
US10602317B2 (en) * | 2018-05-01 | 2020-03-24 | Satellite Tracking Of People Llc | System and method of alternative tracking upon disabling of monitoring device |
CN111124524A (en) * | 2018-10-30 | 2020-05-08 | 中兴通讯股份有限公司 | Business service framework configuration method, system, terminal and storage medium |
US11196752B2 (en) * | 2019-01-22 | 2021-12-07 | Lenovo Enterprise Solutions (Singapore) Pte. Ltd. | Multifactor authentication for secure management of data center assets from a mobile device |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7769394B1 (en) | System and method for location-based device control | |
US10574667B2 (en) | Electronic devices having adaptive security profiles and methods for selecting the same | |
US8839453B2 (en) | Authenticating a mobile device based on geolocation and user credential | |
US8463238B2 (en) | Mobile device base station | |
US7912451B2 (en) | Limiting use of electronic equipment features based on location | |
US8755840B2 (en) | Data execution control method and system therefor | |
US8484707B1 (en) | Secure changing auto-generated keys for wireless access | |
US7428411B2 (en) | Location-based security rules | |
US8208900B2 (en) | Secure device configuration profiles | |
US8787941B2 (en) | Prohibiting electronic device usage based on geographical location | |
US9400877B2 (en) | Server device and service provision method | |
US20150358822A1 (en) | Utilizations and Applications of Near Field Communications in Mobile Device Management and Security | |
US20120178476A1 (en) | Determining the last location of lost and stolen portable electronic devices when wireless communications access to the lost or stolen devices is lost or intermittent | |
EP2885909B1 (en) | Apparatus, method and computer program product for sharing data | |
US8804680B2 (en) | System and method for managing wireless connections and radio resources | |
WO2006071430A2 (en) | Dynamic management for interface access permissions | |
US8805421B2 (en) | Method and system for sending ring setting reminders to mobile devices within a predetermined area | |
US10027629B2 (en) | Short message service reading method and device | |
US20080010091A1 (en) | Method and System for Sharing a User-Medical-Record | |
GB2421147A (en) | Secure profiles for mobile devices | |
US20230393837A1 (en) | In-box software updates | |
KR100719142B1 (en) | Mobile Communication Terminal with Location-Based Variable Password and Control Method Thereof, Location-Based Variable Password Setting System Therefor | |
TW201440449A (en) | Utilizations and applications of near field communications in mobile device management and security |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: SPRINT COMMUNICATIONS COMPANY L.P., KANSAS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:ZHU, KEVIN K.;REEL/FRAME:018365/0439 Effective date: 20060928 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
FPAY | Fee payment |
Year of fee payment: 4 |
|
AS | Assignment |
Owner name: DEUTSCHE BANK TRUST COMPANY AMERICAS, NEW YORK Free format text: GRANT OF FIRST PRIORITY AND JUNIOR PRIORITY SECURITY INTEREST IN PATENT RIGHTS;ASSIGNOR:SPRINT COMMUNICATIONS COMPANY L.P.;REEL/FRAME:041895/0210 Effective date: 20170203 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552) Year of fee payment: 8 |
|
AS | Assignment |
Owner name: SPRINT COMMUNICATIONS COMPANY L.P., KANSAS Free format text: TERMINATION AND RELEASE OF FIRST PRIORITY AND JUNIOR PRIORITY SECURITY INTEREST IN PATENT RIGHTS;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS;REEL/FRAME:052969/0475 Effective date: 20200401 Owner name: DEUTSCHE BANK TRUST COMPANY AMERICAS, NEW YORK Free format text: SECURITY AGREEMENT;ASSIGNORS:T-MOBILE USA, INC.;ISBV LLC;T-MOBILE CENTRAL LLC;AND OTHERS;REEL/FRAME:053182/0001 Effective date: 20200401 |
|
AS | Assignment |
Owner name: T-MOBILE INNOVATIONS LLC, KANSAS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:SPRINT COMMUNICATIONS COMPANY L.P.;REEL/FRAME:055604/0001 Effective date: 20210303 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 12TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1553); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 12 |
|
AS | Assignment |
Owner name: SPRINT SPECTRUM LLC, KANSAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS;REEL/FRAME:062595/0001 Effective date: 20220822 Owner name: SPRINT INTERNATIONAL INCORPORATED, KANSAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS;REEL/FRAME:062595/0001 Effective date: 20220822 Owner name: SPRINT COMMUNICATIONS COMPANY L.P., KANSAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS;REEL/FRAME:062595/0001 Effective date: 20220822 Owner name: SPRINTCOM LLC, KANSAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS;REEL/FRAME:062595/0001 Effective date: 20220822 Owner name: CLEARWIRE IP HOLDINGS LLC, KANSAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS;REEL/FRAME:062595/0001 Effective date: 20220822 Owner name: CLEARWIRE COMMUNICATIONS LLC, KANSAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS;REEL/FRAME:062595/0001 Effective date: 20220822 Owner name: BOOST WORLDWIDE, LLC, KANSAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS;REEL/FRAME:062595/0001 Effective date: 20220822 Owner name: ASSURANCE WIRELESS USA, L.P., KANSAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS;REEL/FRAME:062595/0001 Effective date: 20220822 Owner name: T-MOBILE USA, INC., WASHINGTON Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS;REEL/FRAME:062595/0001 Effective date: 20220822 Owner name: T-MOBILE CENTRAL LLC, WASHINGTON Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS;REEL/FRAME:062595/0001 Effective date: 20220822 Owner name: PUSHSPRING, LLC, WASHINGTON Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS;REEL/FRAME:062595/0001 Effective date: 20220822 Owner name: LAYER3 TV, LLC, WASHINGTON Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS;REEL/FRAME:062595/0001 Effective date: 20220822 Owner name: IBSV LLC, WASHINGTON Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS;REEL/FRAME:062595/0001 Effective date: 20220822 |