[go: up one dir, main page]

WO2019010210A1 - Système et procédé pour décourager l'utilisation inappropriée d'un dispositif mobile - Google Patents

Système et procédé pour décourager l'utilisation inappropriée d'un dispositif mobile Download PDF

Info

Publication number
WO2019010210A1
WO2019010210A1 PCT/US2018/040764 US2018040764W WO2019010210A1 WO 2019010210 A1 WO2019010210 A1 WO 2019010210A1 US 2018040764 W US2018040764 W US 2018040764W WO 2019010210 A1 WO2019010210 A1 WO 2019010210A1
Authority
WO
WIPO (PCT)
Prior art keywords
mobile device
user
status
mode
change
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.)
Ceased
Application number
PCT/US2018/040764
Other languages
English (en)
Inventor
Brian Way
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Individual
Original Assignee
Individual
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Individual filed Critical Individual
Priority to EP18750554.0A priority Critical patent/EP3649771A1/fr
Priority to CA3069011A priority patent/CA3069011A1/fr
Publication of WO2019010210A1 publication Critical patent/WO2019010210A1/fr
Priority to US16/253,078 priority patent/US11356549B2/en
Anticipated expiration legal-status Critical
Priority to US17/831,015 priority patent/US12200584B2/en
Priority to US19/016,616 priority patent/US20250150794A1/en
Ceased legal-status Critical Current

Links

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/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/72454—User interfaces specially adapted for cordless or mobile telephones with means for adapting the functionality of the device according to specific conditions according to context-related or environment-related conditions
    • 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
    • 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
    • H04M1/724634—With partially locked states, e.g. when some telephonic functional locked states or applications remain accessible in the locked states

Definitions

  • Patent No. 9,621 ,707 which is a Non-Provisional Application, and claims priority to and the benefit of the filing date of U.S. Provisional Patent
  • This present invention is related to a system and method for discouraging, preventing and reporting on the usage of mobile electronic devices, such as cell phones or tablets, when a user is engaged in another activity demanding their attention, and specifically to the prevention and discouragement of texting, communicating, or otherwise being distracted with mobile devices while driving, working, and doing other important activities.
  • Texting in a general sense, is the typing out of a text message on a cellular telephone or other mobile device (referred to as SMS or MMS). Often, it is done using a very small keyboard on the device. Sending an email using a cellular phone presents the same problems as texting, and so both texting and emailing will be referred herein to generally as "texting". The resulting text message can be immediately received by another cellular telephone or computer.
  • the driver generally has to look at the small keyboard provided with the mobile device, and look away from the road or their other activity temporarily.
  • speech recognition capabilities on current devices have reduced the need for some typing, a large majority of device users still type out a text message using a keyboard. Even if speech recognition is utilized, they still are reviewing, modifying, and/or sending the text message while looking at the device screen or keyboard, and away from their main task, such as driving. As such, it takes their visual attention away from the more important tasks at hand.
  • the overuse and abuse of such devices in routine daily life and in competition with other tasks is a problem for young and old alike.
  • a person when a person is supposed to be engaged in another task, such as sleeping or in social interactions, they may be awoken or distracted by their device, such as through constant audible and visual notifications of incoming texts, incoming emails, incoming calls, etc.
  • This is particularly a problem with children and young adults.
  • young adults may be in their bedroom for the purposes of sleeping or doing homework according to their parents' wishes, but may be actually engaging in communications, via text, email, or other applications.
  • Distracted living and texting, communicating and device use in school is also a significant distraction.
  • Use of mobile devices in the educational environment is often a detriment to the entire educational process.
  • FIG. 1 is a block diagram of a monitoring system, one or more mobile devices, and one or more client devices consistent with embodiments of the invention.
  • Figure 2 is a block diagram of an embodiment of a monitoring system of Figure 1 .
  • Figure 3 is a block diagram of an embodiment of a mobile device of Figure 1 .
  • Figure 4 is a block diagram of an embodiment of a client device of Figure 1 .
  • Figure 5 is a flow design illustrating a sequence of operations that may be performed by the systems and devices of Figure 1 consistent with embodiments of the invention to monitor an operational status of one or more mobile devices.
  • Figure 6 is a diagrammatic view of an example graphical user interface that may be output on a display of a client device of Figure 1 , in accordance with the invention.
  • Figures 7 A - 7E are diagrammatic views of example graphical user interfaces that may be output on a display of a client device of Figure 1 , in accordance with the invention.
  • Figure 8 is a diagrammatic view of an example graphical user interface that may be output on a display of a mobile device of Figure 1 , in accordance with the invention.
  • Figures 9A - 9H are diagrammatic views of other example graphical user interfaces that may be output on a display of a mobile device of Figure 1 , for engaging the mobile device in accordance with the invention.
  • Figure 10 is a diagrammatic view of an example graphical user interface that may be output on a display of a mobile device of Figure 1 for engaging the mobile device, in accordance with the invention.
  • Figure 1 1 is flow design illustrating a sequence of operations that may be performed by the systems and devices of Figure 1 consistent with embodiments of the invention to monitor an operational status of one or more mobile devices.
  • Figure 12 is a schematic view of an activation message, in accordance with the invention.
  • Figure 13 is an exemplary dashboard screen reporting a device transaction, in accordance with the invention.
  • Figure 14 is another exemplary dashboard screen reporting a device transaction, in accordance with the invention.
  • Figure 15 is another exemplary dashboard screen reporting a device transaction, in accordance with the invention.
  • Figure 16A is a diagrammatic view of an example graphical user interface that may be output on a display of a mobile device in accordance with the invention.
  • Figure 16B is a diagrammatic view of an example graphical user interface that may be output on a display of a mobile device in accordance with the invention.
  • Figure 17 is a block diagram of a portion of the system of the invention using beacon devices.
  • Figure 18 is a schematic view of a deactivate message, in accordance with the invention.
  • Figure 19 is a diagrammatic view of an example graphical user interface that may be output on a display of a mobile device, in accordance with the invention.
  • Figure 20 is an exemplary dashboard screen for a mobile device, in accordance with the invention.
  • Figure 21 is a diagrammatic view of another example graphical user interface that may be output on a display of a mobile device of Figure 1 , in accordance with the invention.
  • Figure 22 is a diagrammatic view of an example graphical user interface that may be output on a display of a mobile device, in accordance with the invention.
  • Figure 23 is a diagrammatic view of another example graphical user interface that may be output on a display of a mobile device, in accordance with the invention.
  • Figure 24 is a diagrammatic view of another example graphical user interfaces that may be output on a display of a mobile device, in accordance with the invention.
  • Figure 25 and 27 are diagrammatic views of example graphical user interfaces that may be output on a display of a mobile device for powering Off the device, in accordance with the invention.
  • Figures 26 and 29 are diagrammatic views of example graphical user interfaces that may be output on a display of a mobile device for a device placed in a disabled mode, in accordance with the invention.
  • Figure 28 is an exemplary dashboard screen for a mobile device, in accordance with the invention.
  • Figures 30-32 are diagrammatic views of other example graphical user interfaces that may be output on a display of a mobile device for a device placed in a disabled mode, in accordance with the invention.
  • Figures 33-36 are diagrammatic views of other example graphical user interfaces that may be output on a display of a mobile device for a device placed in a disabled mode through a control center of device, in accordance with the invention.
  • Figure 37 is an exemplary dashboard screen for a mobile device, in accordance with the invention.
  • Figures 38-41 are diagrammatic views of other example graphical user interfaces that may be output on a display of a mobile device for a device to be activated through a control center of device, in accordance with the invention.
  • Figures 42-47 are diagrammatic views of other example graphical user interfaces that may be output on a display of a mobile device for a device to be activated through a control center of device, in accordance with the invention.
  • Figures 48-51 are diagrammatic views of other example graphical user interfaces that may be output on a display of a mobile device for a device placed in a disabled mode through a screen, in accordance with the invention.
  • Figures 52-53 are diagrammatic views of other example graphical user interfaces that may be output on a display of a mobile device for a device to be activated through a screen, in accordance with the invention.
  • Figures 54-58 are diagrammatic views of other example graphical user interfaces that may be output on a display of a mobile device for a device placed in a disabled mode through a control center of device, in accordance with the invention.
  • Figures 59-62 are diagrammatic views of other example graphical user interfaces that may be output on a display of a mobile device for a device placed in a disabled mode through a screen, in accordance with the invention.
  • Figures 63-68 are diagrammatic views of other example graphical user interfaces that may be output on a display of a mobile device for a device to be activated through a control center of device, in accordance with the invention.
  • FIGS 69-72 are exemplary dashboard screens reporting device transactions, in accordance with the invention.
  • Figures 73-83 are diagrammatic views of other example graphical user interfaces that may be output on a display of a mobile device for selecting among various automatic features of the invention for deactivating a device upon various detected conditions, in accordance with the invention.
  • Figures 84A-84B are exemplary dashboard screens reporting device transactions, in accordance with the invention.
  • Figure 85 is another exemplary dashboard screen reporting a device transaction, in accordance with the invention.
  • Figures 86-87 are diagrammatic views of other example graphical user interfaces that may be output on a display of a mobile device for messages indicating various detected conditions, in accordance with the invention.
  • the appended drawings are not necessarily to scale, presenting a somewhat simplified representation of various features illustrative of the basic principles of the invention.
  • the specific design features of the sequence of operations as disclosed herein, including, for example, specific dimensions, orientations, locations, and shapes of various illustrated components, will be determined in part by the particular intended application and use environment. Certain features of the illustrated embodiments have been enlarged or distorted relative to others to facilitate visualization and clear understanding. In particular, thin features may be thickened, for example, for clarity or illustration.
  • system 10 includes monitoring system 102, in accordance with aspects of the invention, which may be implemented as one or more server devices or servers.
  • the monitoring system may be connected to a suitable communication network 103, where the communication network 103 may comprise the Internet, a local area network (LAN), a wide area network (WAN), a cellular voice/data network, one or more high speed bus
  • LAN local area network
  • WAN wide area network
  • cellular voice/data network one or more high speed bus
  • the system 10 includes one or more mobile devices 104 and/or client devices 106 that may be connected to the communication network 103 such that the mobile devices 104 and/or client devices 106 may communicate data to and from the monitoring system 102.
  • the mobile device 104 may typically be a cellular phone or smart phone, tablet computer, laptop computer and/or other such personal computing devices, but the invention is not limited to such devices.
  • the client device 106 may be a desktop computer, laptop computer, thin client terminal, smart phone, tablet computer, and/or other such computing device, but the invention is also not limited to such devices.
  • the problem of texting and/or distracted device usage is mostly an issue with mobile phones, but other devices may also distract a user as well, and therefore, the invention is not limited to just addressing the problems of texting or other communications using a phone.
  • the monitoring system 102 may be configured to monitor operational status of one or more mobile devices 104, and store and maintain and report operational status change information for one or more mobile devices 104 that are registered with the monitoring system 102.
  • system 12 is configured for monitoring mobile device interaction with other elements, such as beacon devices of system 10.
  • the monitoring system 102 may be configured to interface with a client device 106 such that a user of the client device 106 may review the monitored status information and operational status change information and other interactions for a particular mobile device 104 that is registered with, and maintained by, the monitoring system 102. The information might be displayed as various transactions associated with the device.
  • an interface may be generated by the monitoring system 102 such that a system user (e.g., a parent, a supervisor, etc.) may input information using a client device 106, such as a computer.
  • the input information may be utilized to set up a user record for the system user, and identify one or more particular mobile devices 104 for which the user wishes to view status information and operational status change information.
  • a client device 106 such as a personal computer, a portable electronic device (e.g., a smart phone, a tablet, a laptop, etc.), or a terminal configured to interface with a server providing such interface.
  • the interface generated by the monitoring system 102 may be a web-based user interface, and the user may access the web-based user interface with an Internet web browser.
  • the interface generated by the monitoring system 102 may be a dedicated interface, such as an interface that may be provided by a special purpose application configured to be executed on the client device 106.
  • a mobile device 104 may be registered with the monitoring system 102 such that the mobile device 104 is linked with a user record for a registered user of the system, such as a user that is interfaced at a client device.
  • the mobile device may be configured to execute a status monitoring application that is configured to cause a processor of the mobile device 104 to monitor the mobile device, capture, and generate status information and other interaction information, and particularly, to generate a status change report that is responsive to an operational status or mode change of the mobile device.
  • the status change report may include data that indicates a status to which the mobile device 104 was changed and a time and date associated with the status change (i.e., a time/date stamp), as discussed further herein.
  • various notification messages, or communications might be sent, at various junctures, to one or more devices or accounts associated with the mobile device that is being monitored, and/or might be logged and displayed with status change information.
  • a mobile device is preferably disabled in some way to prevent use of the device and distractions, and the invention monitors how long the device was disabled, and when it was again enabled.
  • FIG. 2 provides a block diagram that illustrates components of the one or more servers 107 of the monitoring system 102 consistent with some embodiments of the invention.
  • the monitoring system server 107 includes at least one processor or CPU 122 including at least one hardware- based microprocessor and a memory 124 coupled to the at least one processor 122.
  • the memory 124 may represent the random access memory (RAM) devices comprising the main storage of the monitoring system 102, as well as any supplemental levels of memory, e.g., cache memories, nonvolatile or backup memories (e.g., programmable or flash memories), readonly memories, etc.
  • RAM random access memory
  • memory 124 may be considered to include memory storage physically located elsewhere in the monitoring system 102, e.g., any cache memory in a microprocessor, as well as any storage capacity used as a virtual memory, e.g., as stored on a mass storage device or on another computer coupled to the monitoring system 102.
  • the monitoring system 102 may include a user interface 126 incorporating one or more user input/output devices, e.g., a keyboard, a mouse or other pointing device, a display, a printer, etc.
  • Data may be communicated by the system 102 to and from another device, computer or terminal (e.g., the mobile device 104, the client device 106, etc.) over a suitable network interface 128 that is coupled to the appropriate communication network 103.
  • the monitoring system 102 also may be in communication with one or more mass storage devices, which may be, for example, internal hard disk storage devices, external hard disk storage devices, external databases, storage area network devices, etc.
  • the monitoring system 102 typically operates under the control of an operating system 130 and executes or otherwise relies upon various computer software applications, components, programs, objects, modules, engines, data structures, etc., including for example, a monitoring application 132, and/or a monitor interface application 134.
  • the monitoring application 132 may be configured to receive status data or information, such as status change report information or device interaction information, from a particular mobile device 104 over the communication network 103, and store status change information and other information in a corresponding user record for that mobile device based on the received status change report.
  • the monitor interface application 134 is generally configured to interface with one or more client devices 106, and to retrieve and report stored status change information for a particular mobile device 104 based at least in part on one or more queries that is received from the client device 106 when the client device interfaces with system 102.
  • the memory 124 of the monitoring system 102 may generally include or store one or more databases including, for example, a status database 140 that may store one or more user records 142.
  • each user record 142 of the status database may be associated with a registered user that had registered with the monitoring system 102, and the user record may store status information and other information for one or more mobile devices that are linked to the registered user and/or were registered by the particular registered system user.
  • the databases 140 may comprise data and supporting data structures that store and organize the data used by the invention, including data from the mobile device, client devices, and monitoring systems. In particular, the databases 140 may be arranged with any database
  • a database management system in the form of a computer software application executing as instructions on a processing unit 122 of the monitoring system 102 may be used to access the information or data stored in records of the databases 140 in response to one or more queries, where a query may be dynamically determined and executed by the operating system 130 and/or other applications 132, 134.
  • Figure 3 provides a block diagram that illustrates the
  • the mobile device 104 includes at least one processor or CPU 160 including at least one hardware-based microprocessor and a memory 162 coupled to the at least one processor 160.
  • the memory 162 may represent the random access memory (RAM) devices comprising the main storage of the mobile device 104, as well as any supplemental levels of memory, e.g., cache memories, non-volatile or backup memories (e.g., programmable or flash memories), read-only memories, etc.
  • RAM random access memory
  • memory 162 may be considered to include memory storage physically located elsewhere in the mobile device 104, e.g., any cache memory in a
  • the mobile device 104 may include at least one appropriate user interface 164 for interfacing with a user and a network interface 166 for communication over the one or more appropriate
  • the user interface might include a keyboard, microphone, speaker, touch screen, etc. for communicating or interfacing with a user.
  • the network interface may include, for example, a cellular network interface, as well as a Wi-Fi interface or other suitable network interfaces for communication over network(s) 103.
  • the mobile device 104 typically operates under the control of an operating system 168 and/or application and executes or otherwise relies upon various computer software applications, components, programs, objects, modules, data structures, etc., including for example, a status monitoring application 170.
  • the status monitoring application 170 may be executed by the processor 160 of the mobile device 104 to monitor status and interactions of the mobile device 104 and generate status change report information, interaction information or other status data/information
  • the status change report information may be communicated to the monitoring system 102 over the communication network 103 and ultimately to a client device 106. The information may then be displayed for a system user to review.
  • the status monitoring application 170 may be implemented as a downloadable application, such as an application supported by Android and iOS operating systems available from Open
  • the status monitoring application 170 may be downloaded to a device 104 from an external source including for example, a network accessible location (e.g., a mobile application store, an accessible database), a computer readable storage media, and/or other such external sources.
  • an external source including for example, a network accessible location (e.g., a mobile application store, an accessible database), a computer readable storage media, and/or other such external sources.
  • Figure 4 provides a block diagram that illustrates the
  • the client device 106 includes at least one processor or CPU 180 including at least one hardware-based microprocessor and a memory 182 coupled to the at least one processor 180.
  • the memory 182 may represent the random access memory (RAM) devices comprising the main storage of the client device 106, as well as any supplemental levels of memory, e.g., cache memories, non-volatile or backup memories (e.g., programmable or flash memories), read-only memories, etc.
  • RAM random access memory
  • memory 182 may be considered to include memory storage physically located elsewhere in the client device 106, e.g., any cache memory in a microprocessor, as well as any storage capacity used as a virtual memory, e.g., as stored on a mass storage device or on another computer coupled to the client device 106.
  • the client device 106 may include a user interface 184 for interfacing with a user and a network interface 186 for communication over the communication network 103.
  • An exemplary client device might be a computer with a suitable keyboard and screen for a user interface and a suitable wired or wireless Ethernet or other network interface, or a mobile device, such as a phone or pad device.
  • the client device 106 typically operates under the control of an operating system 188 and/or application and executes or otherwise relies upon various computer software applications, components, programs, objects, modules, data structures, etc., including for example, a monitor interface application 190.
  • the monitor interface application 190 may be executed by the processor 180 of the client device 106 to interface with the monitoring system 102 and receive status information/data and review status change information for one or more mobile devices 104.
  • the monitor interface application 190 may comprise an Internet browser that may be directed to an Internet address associated with a web interface provided by the monitoring system 102 that is displayed to a user of the client device 106 in the browser.
  • the monitoring system 102 may generate a web-based interface (e.g., a graphical user interface) that may be accessible by the client device using the Internet browser for viewing the operational status
  • interaction information interaction information and status change information for one or more previously-registered mobile devices.
  • the monitor interface application 190 may be configured to generate an interface (e.g., a graphical user interface) on the client device 106 that is configured to communicate data between the monitoring system 102 and the client device 106. Therefore, in these embodiments, the interface may be generated at the client device 106 by executing the monitor interface application 190.
  • a user may, for example, register one or more devices, check device status, and/or provide data that may be communicated to/from the monitoring system 102.
  • Program code generally comprises one or more instructions that are resident at various times in various memory and storage devices in a computer, and that, when read and executed by one or more hardware-based processing units in a computer (e.g., processors, microprocessors, processing cores, or other hardware-based circuit logic), cause that computer to perform the steps embodying desired functionality.
  • hardware-based processing units e.g., processors, microprocessors, processing cores, or other hardware-based circuit logic
  • Such computer readable media may include computer readable storage media and communication media.
  • Computer readable storage media is non-transitory in nature, and may include volatile and non-volatile, and removable and non-removable media implemented in any method or technology for storage of information, such as computer-readable
  • Computer readable storage media may further include RAM, ROM, erasable programmable read-only memory (EPROM), electrically erasable
  • EEPROM programmable read-only memory
  • flash memory or other solid state memory technology
  • CD-ROM, DVD, or other optical storage CD-ROM, DVD, or other optical storage
  • magnetic cassettes magnetic tape
  • magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store the desired
  • Communication media may embody computer readable instructions, data structures or other program modules.
  • communication media may include wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. Combinations of any of the above may also be included within the scope of computer readable media.
  • FIG. 5 provides a flowchart 200 that illustrates a basic sequence of operations in accordance with an embodiment of the invention that may be performed by the monitoring system 102, the mobile device 104, and the client device 106 consistent with various features of the invention.
  • a system user may register with the monitoring service that is offered through the application 132 of the monitoring system (block 202).
  • a system user may interface with the monitoring system 102 and application 132 via a client device 106 and network 103 to register for the monitoring service, to become a registered system user, create a user record, and to register one or more devices for the system to monitor.
  • registering for the inventive monitoring service may include the steps of providing user registration information through a client device 106 to the monitoring application run on system 102.
  • the provided user information is then used to create a user record that is associated with the user, and ultimately, is associated with one or more mobile devices that are to be monitored.
  • Such registration information may comprise, for example, a username, a password, payment information, contact information, information associated with the mobile devices to be registered for the service (e.g., a mobile telephone number associated with a mobile device), email addresses, mobile phone information, etc.
  • individual beacons are part of the overall system, and are used to interface with mobile devices to ensure that a user changes the operational status of their device at certain localities, or in certain working environments or situations.
  • the user registration information might also include information for one or more beacons that the monitored devices of various users may encounter, as discussed below.
  • various notification messages in the form of email messages or text messages may be sent to designated email addresses or phone numbers, and such information may be obtained from the user and
  • the monitoring system 102 and application 132 may generate one or more codes, such as an enrollment code or some other code that may be associated with the registered system user.
  • the codes are displayed for the system user.
  • the enrollment code is then used by the system user or some other entity to be input into one or more mobile devices 104 running a status monitoring application 170 to thereby associate or link the
  • Figures 7 A - 7E illustrate such codes as they are displayed for a system user at a client device, for example.
  • the one or more mobile devices 104 may be linked to the registered user (e.g., associated with a particular user record) through the monitoring application and the system 102. More specifically, one or more mobile devices will be linked with the monitoring application, through the network (block 204). Therefore, those mobile devices will be able to communicate with system 102 and application 132, and will be associated with one or more user records 142. As discussed above, in some
  • an enrollment code associated with a registered user and the user record of that registered user may be generated by the monitoring application of the monitoring system 102, and may be displayed by the monitoring application, such as on a screen of client device 106 (See Figures 7 A - 7E) for linking devices 104 with system 102.
  • a user or other entity then provides or enters the enrollment code to the program interface of the mobile device that is used when executing the status monitoring application 170 on the mobile device 104.
  • the application 170 and mobile device 104 interfaces/communicates with system 102, and provides the necessary enrollment information to link the device with a user record in system 102.
  • This step or series of steps links the mobile device 104 (and the user of the mobile device) to the registered system user and to the associated user record of the monitoring application of system 102. For example, a user interface that is part of the status
  • monitoring application 170 might be used to get the code information.
  • the user may provide other identification information (e.g., a username and password) to link the mobile devices 104 to a registered system user and the monitoring application and system 102.
  • the terms "user” or "system user” will generally refer to the particular user, such as a parent or supervisor, who wishes to monitor the status of a mobile device that is being used by someone else, such as the device user (e.g. a teenager, a worker, a driver, etc.) Those entities (system user and device user) could be the same entity, but generally, will be different users.
  • the device 104 and device user may be linked with one or more email addresses or mobile phone numbers through the monitoring application 132, and user records 142 associated therewith.
  • the devices 104 might be linked with one or more beacons, as discussed herein.
  • the mobile device(s) 104 may execute the status monitoring application 170 on a particular device that communicates with system 102, such that the operational status of the mobile device(s) or interactions of the mobile device, such as with one or more beacons, may be monitored (block 206).
  • a mobile device may be configured to operate in one or more operational modes, states, or statuses, where each operational mode, state, or status may facilitate or define certain operating features and functions of the device. That is, based on the operational status, certain functional features are enabled and/or disabled for the device.
  • the device may have a normal or basic or enabled operational mode, state, or status where all or most of the functions of the device are operating or enabled.
  • the device may also have one or more additional operational modes, states, or statuses where certain features are disabled or nonfunctional. That is, various functions of the mobile device 104 are limited or are not operational. These are referred to as disabled modes.
  • disabled modes To prevent distractions, it is generally desirable to have the device in one of the disabled modes where communication features, like cellular network connectivity or Wi-Fi connectivity are disabled so that the device is not used for distracting communications, or for otherwise distracting purposes.
  • the mobile device 104 may be configured to facilitate voice and data communications, execute one or more applications, facilitate processor communication with one or more components, etc.
  • the mobile device may be completely OFF (e.g., Powered OFF state/mode), or may be configured to disable certain device features, to not allow voice and/or data
  • modes For example, in a particular mode (e.g., Airplane mode, Do Not Disturb mode, limited
  • the mobile device 104 may be configured to not allow certain voice communication and/or data
  • an Airplane mode might disable all general communications, while a Do Not Disturb mode might be tailored to stop some communications or notifications, but allow certain phone calls.
  • the term "disabled" mode or state will refer generally to some status wherein at least one or more of the communication or notification functions is disabled, as opposed to a normal, enabled mode.
  • the disabling of the communication connectivity of a mobile device may be desirable to prevent or reduce use of devices and the distractions associated therewith.
  • Airplane mode a disabled mode for mobile devices
  • different devices may have different function-limiting modes, and the ultimate name of the disabled mode is less important than what the mode disables or enables.
  • Other scenarios such as when a person is driving, a person is in a meeting, a person is sleeping, a person is studying in a library, etc, might also be appropriate scenarios for disabling one or more features or functions of the phone or mobile device in order to prevent the distraction of using the device, or even prevent the temptation to use the device. Therefore, while “Airplane mode” is noted in several examples herein for description purposes, other disabled modes could be equally applicable to the invention.
  • the mobile device 104 executing the status monitoring application 170 monitors the operational status of the mobile device 104 to detect status changes or to detect interactions, such as with a beacon (block 208). As may be
  • a user of the inventive system will have a vested interest to make sure that a disabled device remains disabled while the device user is otherwise engaged in another task, such as driving, operating on a patient, sleeping, working, studying, etc.
  • a device user might be alerted that they are in a location or scenario where they should put their device into a disabled mode.
  • a device user may know that they are to put their device into a disabled mode.
  • the device user may be instructed, through a graphical interface on the mobile device, to place the device into a particular desired disabled state or mode. For example, as discussed below for the illustrated embodiment, the device user might be instructed to place the device in "Airplane mode", or some other mode, as part of the execution of application 170.
  • Figures 9A and 9B illustrate various examples of a screen interface 370 of a device setting forth instructions for disabling communication features of a device and activating and engaging the status monitoring application 170. Depending on the devices, slightly different instructions might be used.
  • various icons or fields may be presented, such as in a touch screen of a device, for activating programs and features of the invention and it will be understood that such fields may be engaged with a touch by a user for activation. Accordingly, the presentation of touchscreen fields implies that the feature might be activated, opened, selected or otherwise made operable with a touch.
  • the device user might be asked if they want to send an activation message (e.g., email or text message) that they will be starting, activating, or opening the status monitoring application or app (e.g., See Figure 9C).
  • an appropriate screen interface might prompt the device user, asking if they wish to send an activation message. If they do, such a message would be sent to one or more system users that may have an interest or stake in monitoring a mobile device and respective users and their activities.
  • the email address or phone numbers that are used as destination information for the messaging might be set when the system user enters or provides login information regarding selecting and monitoring one or more user devices, and sets up a user record ( Figures 7 A - 7E).
  • the transaction associated with sending an activation message might be logged to be displayed, or reported with other operational status information.
  • the desirable selected disabled state/mode for a device running the application 170 will disable certain functions, such as the texting and phone voice functions, in accordance with what is often instructed or mandated during takeoff and landing of an airplane.
  • the invention is not limited to just a conventional "Airplane mode", and thus, the application may instruct a device user to enter some other suitable disabled mode or state for a device where
  • a powered OFF mode or a Do Not Disturb mode, might be selected.
  • the mobile device user might just be instructed to disable one or more functions, for example, a texting function or a phone function, and such disabling of a function may also represent a particular "state" or mode.
  • the invention is not limited to any specific disabled state where certain
  • the mobile device that is in the desired operational state/mode is then monitored, according to the invention, to determine and to detect any change in operational status, such as when a device user exits the disabled mode.
  • any change in operational status might be the device being moved by the user back to a basic enabled operational state/mode where the device user can again text, make a call, or be otherwise distracted by the device and by using the device.
  • the mode Airplane, Do Not Disturb, etc.
  • the mobile device 104 while the mobile device 104 remains in a respective desired disabled operational state ("N" branch of block 208), the mobile device 104 executing the status monitoring application 170 continues monitoring the mobile device 206 (block 206) until a change in the operational status occurs, such as the device moving out of the desired state/mode or to another functional state/mode. Responsive to detecting a change in the operational status of the mobile device 104 (e.g., leaving or getting out of Airplane mode), the mobile device executing the status monitoring application 170 captures data about the change in status, and generates a status change report or generates data that is then communicated or reported to the monitoring system 102.
  • a change in the operational status of the mobile device 104 e.g., leaving or getting out of Airplane mode
  • the status change report may include data or information about the state or mode that the device was in and status to which the mobile device 104 has changed and associated information, such as a time and date (e.g., a date/time stamp) at which the operational status change occurred.
  • a time and date e.g., a date/time stamp
  • the change in operational status is then reported to the monitoring application and system 102, and then information about the status change is displayed appropriately to a system user.
  • the status change might be displayed using an appropriate graphical interface, such as an interface screen or
  • dashboard screen at a client device 106 For example, if the client device is a computer, the change in status will be reported to the system user by being displayed on a screen of the client device.
  • Figure 6 provides an example illustration of a graphical user interface screen 300 that may be generated by the monitoring system 102 and accessible by a client device 106, through appropriate monitor interface applications 134, 190, for implementing an embodiment of the invention.
  • a user may register as a user of the monitoring service provided by the monitoring program and system 102 of the invention and/or log in to view status change information for various mobile devices that is stored in a user record associated with the registered user.
  • the registered user interfaces with the example graphical user interface 300, such as through a web browser at a client device 106.
  • Certain fields 321 , 323 may be selected for registering with the system 10 of the invention to be set up as system user (321 ), or for signing in or out of the system user's account (323). Once signed or logged in, a user may view a dashboard to register further devices (See figures 7 A - 7E), or review operational information that was logged and reported for certain devices (See Figures 13, 14). At a
  • the system user may log in, enter information, edit information, register one or more mobile devices with the monitoring system, enter email addresses or mobile phone numbers for messaging, and identify beacons to be tracked by one or more devices, for example.
  • the graphical user interface links a user with a monitoring program 132 running on the
  • the interface 300 might also provide additional information to a system user or other person, such as though various fields 303.
  • Figures 7A - 7E provide example illustrations of another graphical user interface 320 in the form of a dashboard that may be
  • the graphical user interface screen or dashboard 320 includes an information field 322 that displays information about all the mobile devices 104 that are currently registered and linked to a user record associated with a registered user through the application 132 of system 102, as well as devices to be linked.
  • the dashboard interface 320 might be displayed, and a registered user associated with the user record may add one or more additional or new mobile devices for monitoring by interfacing with one or more interactive fields 324 of the graphical user interface 320 to provide information about the additional mobile device.
  • a user can engage field 324a to add a device.
  • each device might be given a name to designate the device and its possible user, such as "John's phone" (field 324a).
  • other information designating the device such as a phone number for a cellular phone device, or a cellular-enabled pad device, may be entered (field 324b). If a non-cellular enabled device is used, some other identification information might be provided in field 324b, and used to link the mobile device with the application 132 and system 102.
  • the selected mobile device is then linked to the user record for the system user and with the monitoring program 132.
  • Current devices for a particular user and user record are illustrated via the dashboard interface 320 and fields 322. As shown, multiple devices might be added and selected for monitoring.
  • the fields 322 a, 322b, and 322c illustrate the name of the device, identification information (e.g., phone number) for the device and its enrollment status.
  • Field 322d might be used to delete one or more selected devices from the user record.
  • the various current devices that are linked to the monitoring program 132 may be monitored as appropriate for detecting when a change in the operational status occurs in a device.
  • the link between the selected or added mobile device and system 102 and program 132 requires steps at the mobile device as well, such as use of an enrollment code, or other linking code information for providing the link between the system 102, the system user record 142, and the actual mobile device 104 to be monitored.
  • Field 322c of the interface 320 illustrates the enrollment status or linked status of a device. If the mobile device has been properly linked or enrolled with the system 102, the field 322c might indicate "Enrolled", as shown in the Figures. Alternatively, if a device has been entered through interface 320, but has not yet been linked or enrolled, an enrollment code might be displayed, as shown in field 322c for the devices "Greg's phone” and "Mindee's phone”.
  • Figures 7A - 7E also illustrate an embodiment of the invention, wherein various message notification features might be enabled for one or more of the current devices that are linked/enrolled and being monitored.
  • interactive fields 326 are provided in the dashboard interface 320 for the purpose of selecting a messaging feature and
  • messaging notifications such as emails, or text messages
  • certain notifications or messages are sent for certain transactions that are detected, such as status changes or device interactions.
  • information is provided through the interactive fields 326 so that the user record will include, for example, one or more email addresses, one or more mobile phone numbers, or other identification information providing a destination for message notifications that are associated with one or more monitored mobile devices in accordance with the invention.
  • the information entered is utilized by the monitoring application 132 to notify one or more system users regarding different device transactions, such as the status of the registered and monitored devices and/or device interactions, such as with a beacon.
  • the notifications are provided to a system user, such as through an email or text.
  • certain messages and message information are also logged and reported as a transaction, and may be displayed in an interface, along with operational status information and other information for review by a system user.
  • Figures 7 A - 7E illustrate an exemplary embodiment, wherein email notifications are provided to notify and assist the system user.
  • email notifications are provided to notify and assist the system user.
  • other notifications such as text message notifications or other notifications, might also be provided in accordance with the invention, and the invention is not limited to a particular type of notification.
  • the "Add" field 326a might be engaged and then an email address might be added via field 326b of the graphical user interface 320, as a destination for a notification.
  • a drop-down menu 326c is provided with a field 326d displaying which of the current devices registered for the system user and their user record are selected for the messaging feature using the email address 326b for generating various notifications. Devices may be selected by a user, and the selected devices are thereby associated with the email address of field 326b (See Figures 7B - 7C).
  • field 326d will indicate that no devices are selected ( Figure 7B).
  • a drop-down menu 326e appears ( Figure 7C).
  • the user selects one or more of the displayed devices through menu 326e.
  • the one or more selected devices are indicated in field 326d (See Figure 7D).
  • the label or name of the device is shown in field 326d, as illustrated in Figure 7D.
  • the number of devices that are selected is indicated, as illustrated in Figure 7D.
  • Various fields and devices may be appropriately selected and checked, such as through the use of a mouse, touch screen, keyboard, or other input device of a client device 106.
  • the notification addresses will be shown in fields 326b, along with the number of devices associated with that email address in field 326d.
  • multiple notification addresses may be utilized, and each may be associated with certain selected mobile devices that have been entered and/or enrolled. For example, as shown in Figure 7D, one address has a single device associated therewith wherein the other address has two devices that have been selected and are associated therewith.
  • email addresses or other message notification information is provided through the interactive fields 326, the information is part of the system user record, and will be appropriately associated with and linked with each of the selected devices for notification purposes, as discussed herein. If there is a desire to drop an address, one or more fields 326f might be engaged. In that way, one or more notifications are provided for a device for one or more notification destinations.
  • one or more beacon devices or beacons may be registered and added to the system user record, and associated with one or more of the devices of that user record.
  • the beacons can be used to prompt a mobile device user to change the operational status of their device, in accordance with the invention.
  • appropriate interactive fields 340, 342 are provided for adding beacon information and registering one or more beacons, and linking a specifically-labeled beacon with proper identification data. Specifically, by engaging field 340 to add a beacon, the label or name of the beacon, such as "CAR 1 " may be entered through field 340.
  • the label might indicate the location of the beacon, for example, to note that the beacon is located in a vehicle referred to as "CAR 1 ".
  • Identification information for the beacon such as an identification number, serial number, or some other identification number, is also entered in field 342 or other related fields. While some figures illustrate one field 342 for ID information, alternative interfaces, such as that shown in Figure 7E might provide other fields 346, 347 for additional information. In one embodiment, information such as UUID (342), a major ID (346), and a minor ID (347) might be used to register a beacon and might be entered using one or more appropriate fields. As such, the invention is not limited to the type of beacon information used to register a beacon with system 10.
  • Such beacons are then as associated with and generally registered to all the various current mobile devices that are listed and enrolled and associated with the system user and the user record, as shown in fields 322. That captured beacon information in system 102 is conveyed to the one or more mobile device of the particular system user record, once those mobile devices are successfully linked with system 102 and with the monitoring application 132. Using that beacon information within the status monitoring application 170 of a mobile device 104, the mobile devices will be able to identify specific beacon signals received from the one or more added beacons that have been associated with a particular mobile device, and will process those beacon signals in accordance with the invention.
  • the beacon detection or interaction is reported to the monitoring application and/or to the mobile device. For example, a message is sent to the device regarding beacon detection. Furthermore, the information regarding the detection is reported to the monitoring application, and logged as a transaction and/or reported as a transaction on a monitoring dashboard or other screen associated with the device. The label that is given to the unique identification number is utilized so that both a system user, and a mobile device user, will know which beacon is referred to, and has been detected. As noted herein, the beacon might be reported to the mobile device when it is detected, and also may be reported to the system 102, and displayed in a dashboard associated with the mobile device so that a system user can see which beacon was detected by the mobile device.
  • the information entered in fields 340, 342, 346, 347 will define the various beacons that are to be associated with a particular device.
  • the noted beacons will be associated with each of those devices.
  • the various beacons which have been entered or set up, along with their labels and identification numbers, will be stored and can be provided to the various registered mobile devices by system 102, through the operation of the monitoring application 132.
  • the mobile devices running the status monitoring application 170 will scan for Bluetooth ® signals, or other wireless signals of the beacons, to detect any beacons close to the particular mobile device.
  • the mobile device displays a message that a particular beacon was detected.
  • the mobile device instructs the device user to put the phone in a disabled mode, which disables certain communication features.
  • the mobile device also logs the transaction, and provides the information regarding the detection of the beacon to system 102, which provides a transaction
  • a beacon detection indicates that the device user/device is in a location where the device user should not be distracted.
  • each of the family cars might be equipped with a beacon, and thus, a mobile device associated with drivers of the family will identify beacon signals that are received when the mobile device is brought in proximity to the beacon, such as a driver getting in the car to drive with their mobile device.
  • the beacon information is utilized to display information on the mobile device that a beacon signal has been received, and also to display appropriate information on the dashboard screen of a system user to indicate which of the mobile devices that is being monitored has received a beacon signal, or otherwise interacted with a beacon, and when they received that signal. Therefore, the information entered in the interface 320 is used by the invention to provide notification of a mobile device interaction with a specific labeled or named beacon.
  • a field 307 in interface 320 may be used.
  • Field 305 allows a user to return to their dashboard from other interface screens.
  • a registered system user When a mobile device is added for a registered system user and associated with a user record and the information therein, a registered system user will be provided by the monitoring application 132, in one example, with an enrollment code or other information that will be used to link one or more mobile devices with the monitoring system 102 and with the user record 142 associated with a registered user.
  • the mobile device 104 runs a status monitoring application that uses the enrollment code to link with and communication with the system 102 so the mobile device may be monitored.
  • the status monitoring application 170 might be downloaded to the device, such as through an appropriate interface, like an online application store. It might be downloaded in other ways as well. Upon downloading the status monitoring application 170 to the mobile device and opening the application, fields are provided on the screen of the mobile device for entering the enrollment code that was provided by monitoring application 132 and other information.
  • Figure 8 provides an example illustration of a graphical user interface screen 360 that may be generated by the mobile device 104 executing the status monitoring application 170 of the invention.
  • the status monitoring application might be loaded onto a device 104, such as from an application or "app" store online, or some other appropriate way.
  • the mobile device application may then be opened, such as by touching or engaging an appropriate icon 504 on a device home screen (See Figure 16A), to run and provide monitoring, as discussed herein.
  • a user links the mobile device 104 to the system 102 and with the monitoring application of system 102 and an associated user record by inputting an enrollment code that is provided by monitoring application 132 upon registering a device (See Figures 7 A - 7E).
  • the code or other linking data that is provided is then entered in an interactive field 362 included in the graphical user interface 360 of the mobile device application 170.
  • the system user may actually provide the enrollment code for enrolling another user's device, such as a child's telephone device, to ensure that the device may be properly monitored in accordance with the invention.
  • the enrollment code might be provided from the system user to the actual device user for the device user to use when linking their device to the monitoring application and monitoring system 102.
  • a phone number for the device or some other identifying information associated with the particular mobile device is also entered, such as in a field 364 of the interface 360, to provide a further link with the device and the system 102 and a user record.
  • the mobile device communicates with system 102 over an appropriate network, and is officially linked with a system user record and application 132 and system 102, and may be monitored by the system and a system user. Specifically, as discussed herein, the mobile device is monitored to determine the operational status of the mobile device and to detect if a change occurs in the operational status to determine if a person is using their device and may be distracted. As noted, as illustrated in Figures 7A - 7E, once a new device is added, program 132 graphically illustrates the devices that are currently selected, and may show an associated enrollment code for the system user through the user interface, or once enrolled, the devices are shown as "Enrolled".
  • the enrolled devices are monitored and specifically the operational status of an enrolled device is monitored for detecting if a change occurs in that operational status.
  • the change in status is reported to the monitoring application of the system 102 and the status change information may be displayed, such as in a suitable graphical interface from a client device.
  • Figures 13 - 15 illustrate exemplary graphical screen interfaces with various dashboard entries for a device entitled "Greg's Phone", or "Brian's Phone". Such interfaces might be displayed on a client device.
  • the client device used for displaying the information might be the same as the mobile device that is being monitored. That is, the graphical interface and status information might be displayed directly on the mobile device that is being monitored, as discussed below. A mobile device user could then actually check the status information of their mobile device right at the mobile device. As discussed below, the mobile device user might have different reasons to know how their status information is being reported.
  • a notification message may be sent (e.g., email or text message) to a system user that had selected a mobile device to be monitored (See Figures 7A - 7E, 18).
  • FIGS. 9A and 9B provide example illustrations of graphical user interface screens that may be generated by the mobile device 104 executing the status monitoring application 170 in response to a user opening the application 170. The screens might be automatically presented when a user provides a valid enrollment code, and a valid link process
  • an icon on a home screen such as icon 504, in interface touch screen 500 of Figure 16A, might be engaged.
  • the graphical user interface 380 provides printed instructions on the screen to the mobile device user regarding one or more desired operational modes or states that should be entered, in accordance with starting or activating the application 170 and the monitoring features of system 102.
  • desired operational modes or states For example, such an operational mode might be a disabled operational mode.
  • Figure 9B illustrates another exemplary embodiment of a graphical interface 390 for activating the application 170.
  • the interface 380, 390 may include written instructions 382, 392 for activating and deactivating the monitoring that is provided in accordance with the invention.
  • the appropriate disabled operational mode such as Airplane mode as illustrated, might be entered when a device user is driving or engaging in some other activity where their attention should not be distracted by texting or some other use of the mobile device.
  • the appropriate disabled operational mode such as Airplane mode as illustrated, might be entered when a device user is driving or engaging in some other activity where their attention should not be distracted by texting or some other use of the mobile device.
  • video instructions might be implemented.
  • an icon 404 or 406 might be selected.
  • the mobile device application 170 would then play or display a video (not shown) on the device screen giving a device user video instructions on how to disable the device or put it into a disabled operational mode, activate the application 170, and start the monitoring process of the invention.
  • Figure 1 1 illustrates a flow diagram of one exemplary process of the invention, wherein the process 600 is initiated by opening and/or activating the status monitoring application on a mobile device 602.
  • a device user may open the status monitoring application of the device voluntarily, or might be instructed to do so based upon the detection of a beacon 628, as noted below.
  • the device user is instructed, by text or video, on how to further activate the application and the status monitoring process by changing the operational mode of the mobile device.
  • a user will be instructed to enter a disabled operational mode 604, wherein one or more communication functions of the device are disabled. Again, for the example, that desired disabled operational mode might be the Airplane mode.
  • a message notification feature may be activated, and a notification message might be sent by a device user to indicate that the status monitoring application 170 has been opened, and is to be started or activated for a mobile device.
  • a system user may desire the option of receiving certain email or text messages for certain transactions during monitoring of a device. Therefore, they may enter contact information (e.g., an email address) for that purpose to activate the message notification feature.
  • contact information e.g., an email address
  • Such a notification message or activation message may be automatic from system 102 or device 104, or may be optional. If selected/activated, when the application 170 is opened and a determination is made regarding whether the message notification feature is active (606), the mobile device may give the user the option of sending a message that the status monitoring application is being activated 606.
  • FIG. 9C an alternative interface 390 is illustrated that provides a pop-up message field 394, asking a device user whether they wish to send an activation message or not. This will occur if message communication information (e.g., email address) had been entered for a user record ( Figures 7A - 7E).
  • message communication information e.g., email address
  • Figures 7A - 7E The device user can answer YES or NO. If they answered YES, the mobile device 104 communicates with system 102 to determine what messaging information is associated with the device, and the user record associated with the device. For example, system 102 and the user records 142 will indicate if the device had been selected for message notifications, and the specific destination information, such as an email address, or a mobile phone number, or other information that is associated with the device.
  • a particular device might be associated with one or more email addresses. If a device user selects that they wish to send an activation message and answers YES appropriately in field 394, an activation message or other notification message is sent to one or more destinations (e.g., one or more email addresses) 608.
  • Figure 12 illustrates one exemplary embodiment of an activation message with text 396 that that might be sent in the form of an email to one or more addresses and recipients. Such an activation message provides an indication to one or more system users that the device user of the mobile device has opened the monitoring application 170, and is in the process of activating the status monitoring application 170 on their device.
  • the message notes "activating Eyecan” as an example, but other messages, such as “activating Airplane mode” or “activating Do Not Disturb mode” might be used as well to note to a system user or other monitoring party that the mobile device user is going to activate the application.
  • Such messaging provides a visual and real-time indication to the system user that a device user has opened the application and should then be activating the status monitoring application 170.
  • a transaction associated with the notification might also be logged or captured by the device and system 102, and ultimately reported at an interface screen 450 as a transaction 610 (See Figure 14).
  • the status monitoring application can be activated by switching the device to a specific disabled operational mode, such as Airplane mode.
  • Figure 9D illustrates the engagement of a control center or control screen 396 in a mobile device.
  • the control screen has various icons which allow a device user to engage certain functionality, and to chose various disabled device modes. For example, icon 398 might be engaged to put the device into an Airplane mode. Alternatively, icon 400 might be engaged to put the device into a Do Not Disturb mode.
  • the control center screen 396 may be closed, and the status monitoring application 170 is considered activated.
  • changes in the operational status of the device will be reported to the monitoring application and system 102, and may be reviewed by one or more parties, such as through a client device 106. For example, if the device user leaves Airplane mode, and goes back to a normal operating mode, it will be reported.
  • Figure 9F illustrates a foreground screen 390 that indicates activation of the status monitoring application of the invention, and is displayed while the application is active. As noted herein, in certain
  • the activation screen 390 should remain in the foreground to indicate that the application is operating in the foreground of the device, and that certain features are disabled to prevent distraction.
  • Screen 390 includes a display field 402 in the form of a synchronization status or "sync status". Such a sync status field 402 may change colors to indicate activation of the status monitoring application and the disabling of one or more of the communication
  • the element 402 when the device is functional to communicate (e.g., not in Airplane mode), the element 402 might be one color, such as green. However, once the application has been activated and the device has been disabled in some way, element 402 may change to a different color, such as red, to indicate that the device is not able to
  • the device can then be put down and not used by the user, leaving the screen of Figure 9F in the foreground.
  • the mobile device is linked to the monitoring application 132 and monitoring system 102 and the status monitoring application 170 is running on the device, and the mobile device user has switched the device to the appropriate desired operational state or mode as instructed, the mobile device is monitored.
  • time stamp and date information is captured by the status monitoring application of the mobile device.
  • the operational status of the mobile device is monitored to detect if and when a change occurs in that operational status, such as moving from the disabled operational mode to an enabled or normal mode.
  • the device is put into a disabled mode, such as Airplane mode, as part of activating the status monitoring application. This allows a user to focus on driving or some other task without being distracted.
  • the status monitoring application 170 detects when the mobile device leaves or exits the disabled mode, Airplane mode, or other monitored disabled operational mode. Application 170 will then capture time stamp and date information, and report the detected change in the
  • the mobile device and application 170 captures and reports data regarding the device status that includes the particular disabled mode selected, time stamp and date stamp information of when the application was activated on the mobile device (e.g., device enters Airplane mode) and time/date information of when the application was deactivated (device exits Airplane mode). Then, through the appropriate monitor interface applications 134, 190, the system 102 receives the transaction information from the mobile device, and the reported status change may be illustrated or displayed as one or more reported transactions in an appropriate graphical interface at a client device 106, such as a computer.
  • a client device 106 such as a computer.
  • the overall system user such as a parent, supervisor or some other entity, may monitor the mobile device and its use by another party or user, such as a child, or a worker under the supervision of the supervisor.
  • the application 170 of the device captures transaction and mode data 612, and may report the initial data to system 102 before the device goes into a disabled mode.
  • the data might all be reported to the system 102, when the device is again enabled (e.g., exit Airplane mode).
  • the disabled operational mode may prevent the device from communicating with system 102.
  • the device user may directly change the mode of that device. For example, once they are done with a task (e.g., driving), a user may wish to use their device again.
  • the control center screen 396 might again be engaged to display various mode icons, such as the Airplane mode icon 398. Then, the device may be taken out of the disabled mode or Airplane mode, and the control screen 396 closed, with the device again displaying the foreground screen 390.
  • the status monitoring application of the mobile device captures additional mode and transaction data and information 616, such as the date/time stamp of when the mode change occurred, and the mode the device was in, and the mobile device then reports data to system 102, such as the time and date information regarding the change of the operational status associated with entering and exiting of Airplane mode 618. Additional messages might be sent as well indicating deactivation of the program 620, 622, and that a device user has again enabled the device to communicate. The transaction of leaving Airplane mode or the status change might be logged as well for reporting to a system user (624) See Figure 1 1 .
  • the data synchronization and communication between the mobile device and system 102 must be completed before the status monitoring application is closed, the device turned OFF, or functionality otherwise changed, which may affect the reporting of data by the mobile device to system 102.
  • a device user might be instructed to wait for a message from the device that the data synchronization has been completed.
  • a popup screen or other field 410 might be utilized to indicate that transaction and mode information or data have been sent to the system regarding the change in the operational status of the device, in accordance with the invention.
  • the user can then answer "OK", returning to screen 390, and the deactivated application 170 may be closed, such as by going to a home screen or to some other application of the device.
  • the mobile device can then be used to make calls, text, email, or otherwise communicate.
  • the change in the operational status of the mobile device might be detected in various different ways.
  • a device user controls the mobile device to enter a specific desired disabled operational mode, such as Airplane mode, to activate the monitoring application, that device user might also exit that state or mode, and thus, would change the operational status directly.
  • a specific desired disabled operational mode such as Airplane mode
  • Such a direct change of status would then be detected at the mobile device through the status monitoring application 170 and then the data reported to system 102.
  • other conditions may be monitored as well to detect a change in the operational status.
  • the status monitoring application 170 might make a determination that the operational status at the mobile device has changed regardless of whether it actually was directly changed, such as by a user. In such scenarios, the status monitoring application or the system 102 and application 132 would make a
  • the user of the mobile device is or may be seeking to bypass the purpose of the invention, and to enable certain disabled features, and thus, begin operating the device, such as to text or to make a phone call. That is, based on the other conditions at the mobile device, the user is essentially trying to change the operational status of the device, although indirectly.
  • the monitoring application 170 of the device can be accessed at a home screen of a device with an icon, and then opened to run on device 104, assuming the application 170 has been downloaded on the device.
  • interface screen 380 of Figure 9A might appear to instruct a user to enter one or more disabled modes.
  • the application 170 is activated by then entering the disabled mode and information/data is logged regarding entering the disabled mode.
  • the program 170 monitors the status of the disabled device, and can determine or detect directly whether the operational status has been changed. That is, data is logged regarding the mobile device exiting the disabled mode.
  • the application 170 will report the status change information to the system 102, as noted. For example, if a user is instructed to place the mobile device into an Airplane mode or some other desirable disabled mode (e.g. Power Off), to activate the invention, then once that desired mode has later exited or the device has been taken out of the particular desired operational mode (Airplane mode OFF, or Power ON), the mobile device is again enabled and the status monitoring application 170 can detect that operational status change, and will communicate or report a change in the operational status of the mobile device to the monitoring system 102.
  • the change in the operational status might be reported from the mobile device to system 102, and then accessed by a client device 106.
  • the change in operational status might also be reported and displayed through a graphical user interface provided by a client device 106, such as a computer or reported through a message (e.g., email or text message) (See Figures 13, 14, 15).
  • the determination of a change in the operational status of the mobile device might be made in a more indirect fashion.
  • the status monitoring application might be opened, such as through an icon on the device home screen.
  • An interface screen such as 390 shown in Figure 9B, for example, might provide instructions on how to activate the application and put the mobile device is a disabled mode (e.g., go into Airplane mode, Power OFF, etc.). Once the program is activated (device disabled), the application will monitor the mobile device for status changes.
  • the application will capture data and report the status change to system 102, as discussed herein.
  • a user might take other steps to make a device functional again, such as not simply exiting a disabled mode, without those steps being directly detected as a direct change in the operational status. Or they may try to use the device is some other distracted way while they should not.
  • the status monitoring application 170 of such a device in those various scenarios will evaluate one or more of the other activities and conditions of the device, and determine that the operational status was changed or disabled (614). These other conditions may be detected and logically processed as an operational status change, and can be reported as a change in the operational status to a system user.
  • the iOS Control Center is pulled up, and the airplane icon may be engaged. Once that is done and the disabled mode selected, the iOS Control Center may be closed, or the Control Center screen closed, and the status
  • monitoring application 170 is now activated. Generally, when activated, the status monitoring application will keep the mobile device awake at all times so that the status monitoring application remains active. Then, to directly change the operational status, the iOS Control Center screen might again be engaged, with the airplane icon tapped to disable the Airplane mode, and deactivate the status monitoring application before leaving the iOS Control Center screen (see Figures 9A - 9H). For such a direct change in operational status, the status monitoring application
  • the status monitoring application may detect the event as a status change and may report a change in the operational status.
  • powering the device OFF is not treated or detected as a status change.
  • the threshold may be set appropriately to allow a mobile device user to quickly switch the device away from the active status monitoring application for a short period of time, but then quickly switch back. Generally, such a threshold would be determined so as to be a length of time that is too short for the mobile device user to take any steps that would be a distraction, such as sending a text. For example, in accordance with one embodiment of the invention, the time threshold might be five seconds.
  • a mobile device user after activating the program and entering the desired disabled operational mode/state, a mobile device user might open some other application or screen, such as another application on the device. If the device user does not return to the status monitoring application and foreground screen within five seconds, the status monitoring application will detect the event as a change in the operational status of a mobile device and report it. Similarly, if the mobile device is in the desired operational state and the device user opens the Control Center for the operating system of the device, and does not return to the status monitoring application and foreground screen within five seconds, a change in the operational status will also be detected and reported.
  • the present invention contemplates not only detecting a direct change in the operational status or a de-activation of the status monitoring application, but also monitors other more indirect conditions and events for detecting that a change has occurred in the operational status.
  • the status monitoring application and its associated screen must remain in the foreground on the user device during activation of the application.
  • an icon 504 indicative of the status monitoring application on the device might be engaged to begin the activation process for the status monitoring application (See Figure 16A).
  • an application interface screen like that shown in Figures 9A and 9B, would then appear as the foreground screen of the device.
  • the opening or foreground screen directs a device user how to activate the status monitoring application of the invention, such as by placing the device in a disabled mode.
  • the user then engages another screen, such as a control screen of the device or a settings application of the device, to select and enter a particular disabled mode for that device to disable certain functions of the device. For example, a user might enter an Airplane mode, a Do Not Disturb mode, or may power OFF the phone to put it into the disabled operational mode.
  • the user then returns to the status monitoring application screen.
  • the status monitoring application then must operate in the foreground of the device, with the interface screen, as shown in Figures 9A and 9B displayed. If the device is turned OFF, it will have been turned OFF with the status monitoring application in the
  • the status monitoring application then monitors the state of the device, and will detect any change in the operational status, such as a change in the state or mode of the device.
  • the status monitoring application When the status monitoring application is deactivated by a mode change (e.g., back to a normal operating mode) or by powering the device back ON from an OFF mode, the status monitoring application of the device will indicate that there has been a change in the operational status, and will report that change and the operational status back to system 102. The time/date information of when the device was disabled and then enabled again will also be captured and reported to system 102. The information regarding the device transactions can then be accessed, such as with a client device, as discussed herein. When the device reports the operational status change back to the system, the type of mode selected by the device user for disabling certain features is also reported so that it might be displayed.
  • a mode change e.g., back to a normal operating mode
  • the status monitoring application of the device will indicate that there has been a change in the operational status, and will report that change and the operational status back to system 102.
  • the time/date information of when the device was disabled and then enabled again will also be captured and reported to system
  • the type of mode might be reported. If the device is powered OFF, for example, and then powered back ON as an operational status change, one transaction might indicate that the user device was powered OFF for some period of time on a particular date. Alternatively, if the device remains powered ON, and one or more particular disabled modes are entered and exited (e.g., Airplane mode, Do Not Disturb mode, etc.), the user device might report the selected mode to the system 102 as well as the time period information of the disabled mode. The information can be graphically displayed as a transaction, and the system 102 would report the time information for how long the device was in that disabled mode (See Figures 13, 14, 15). The type of mode selected and time information is displayed on a suitable interface screen.
  • the status monitoring application must remain in the operational foreground while the system is activated, and the device is in the disabled mode.
  • the user just puts the device down then and does not use it.
  • the status monitoring program might report the event as a change in the operational status of the device.
  • the status monitoring application will report the data to the system, including the additional information as to how the status monitoring application was deactivated. As illustrated in Figure 13, when such an event occurs, the dashboard interface will display that additional information 480, such as an error or other incorrect change in operational status or in deactivating the invention.
  • the transaction when an error occurs in that way (improper deactivation/disabling of the application), the transaction will be considered a complete transaction and change in operational status and will be reported to the system 102 as a complete transaction, along with the error messaging.
  • the transaction can be displayed with the additional error information 480 as illustrated in Figure 13. If the device user then again returns to the
  • new transaction data is logged with time/date information of when the user returned to the foreground screen, and the device is disabled. This starts a new transaction.
  • the device user then later properly deactivates the application 170 (exits the disabled mode), that information is again logged and the second or new transaction is now a completed transaction and is reported to the system to be displayed. Therefore, with one or more errors based upon the device user improperly going away from the application foreground screen, what might normally be logged and reported as a single transaction, might be turned into multiple transactions that are logged and reported to the system.
  • certain communication aspects might be usable. If the device is placed in the disabled mode and then used, the use might be considered a change in the operational status, and reported as such. For example, referring to Figure 23, if the disabled mode selected is a Do Not Disturb mode, the device user might be prompted with a message confirming that selection when the control center is closed. Interface 390 shows message 397 asking for user confirmation that Do Not Disturb mode is the selected disabled mode. In the Do Not Disturb mode, certain features are still available, such as the ability to make or receive phone calls.
  • the user When the user completes the call or some other communication and returns back to a home screen, they may still be in the Do Not Disturb mode. In such a case, monitoring might begin again, as part of a new transaction, to monitor for the next operational status change.
  • the device user might be prompted with a notification at the device to confirm that they are still to be monitored.
  • the interface 390 might provide message 399 for confirmation by the program. If the device user is still to be monitored and selects YES, the program of the invention will start a new transaction with capture of new time/date information, and will monitor for the next operational status change.
  • a message is displayed at the mobile device to warn the device user.
  • a message is displayed at the mobile device to warn the device user.
  • a warning message 540 may be immediately displayed that warns the device user that they are improperly leaving or exiting the application and should return to that application ( i.e., return to the foreground screen and application 170). If the device user returns back to the foreground screen and application before a certain amount of time would elapse, such as a 5 second delay, then the application will proceed as usual and would not be reported as an error as noted herein.
  • the mobile device might be put to SLEEP without affecting the operation of the status monitoring application 170.
  • the device can have the application 170 activated with the foreground screen displayed, the device placed in a disabled mode, and the device then put to SLEEP.
  • the application will continue to function when the device is awoken from the SLEEP mode, the application 170 will still be activated and monitoring for a change in operational status. Therefore, battery life might be preserved without affecting the invention.
  • the system 10 of the invention incorporates one or more beacons 220, 222, 224 positioned in different locations to remind a user not to be distracted, and also to allow the system to determine when a mobile device user is in a location or performing a task such that they should not be using a mobile device or otherwise distracted by such a device.
  • the beacons as shown in Figure 1 , communicate beacon signals to the mobile devices 104.
  • one or more mobile devices 104 are illustrated in the vicinity of one or more indicator beacons 220, 222, 224.
  • Such indicator beacons are installed at various locations so as to indicate to the mobile device 104 and to system 102 that the mobile device user is currently engaged, or is about to be engaged in, a task, that requires their attention, and from which they should not be distracted.
  • beacon 220 as indicated is located within a vehicle 230 that may be driven by the user of the mobile device 104. The device user should not be distracted while driving.
  • beacon 224 might be located in a building 232, such as a hospital, for example, where the user of the mobile device might be engaged in an important task, such as performing surgery, or otherwise providing healthcare to a patient.
  • beacon 222 might be located in some other location, or inside a mobile piece of equipment (e.g., construction equipment), where the user must be focused in their task, and not distracted.
  • beacons such as 220, 222, and 224 might be implemented in a variety of different buildings, vehicles, or other locations, as appropriate, to indicate to a user that they should disable their mobile device and indicate to the system that the user of a mobile device is within proximity to a building, vehicle, or location, wherein they should not be distracted by their mobile device.
  • beacons can be added to the user record to be associated with that mobile device and/or the user of the mobile device.
  • the mobile device encounters one or more of the registered beacons 220, 222, 224, the information is captured and processed by the device and/or provided to system 102.
  • the user can be directed by their mobile device to put their device into a mode or state which disables certain of the communication functions of the device (a disabled operational mode/state) to eliminate or reduce the distractions associated with the device when the user is in a location or situation proximate to one of the beacons.
  • the system is able to display and monitor the status of the device and its interaction with one or more of its registered beacons, as discussed below.
  • beacons 220, 222, 224 are small devices and easily installable, such as within a vehicle or at some site in a building (See Figure 17). They are battery-powered devices, which send out a Bluetooth ® or other wireless signal which includes unique identification information, such as an identification number associated with the particular beacon.
  • a beacon device available from Estimote, Inc of New York, N.Y.
  • the mobile device running application 170 of the invention scans for the beacon, and receives the beacon signals when in proximity to a beacon.
  • the Bluetooth ® signal, or other signal from the beacon is processed by the status monitoring application of the device. Beacon information may also be sent to system 102.
  • beacon is a registered beacon for the device and associated user record, it will be logged, and the beacon interaction displayed and reported, as discussed herein. If the beacon is not registered for the device, it will be ignored.
  • the mobile device having functional Bluetooth ® capabilities for example, will periodically scan for beacons
  • the present invention can control when the device user is directed to disable their device.
  • FIG. 13 - 15 provide example illustrations of a graphical user interface screens 450, 460, or dashboard screens that may be generated by the monitoring system 102 and accessible by the system user through a client device 106 to monitor and display the detected changes in the operational status of one or more registered devices.
  • the dashboard interface 450 includes an information field 470 that displays various different status change transactions and other related information for a mobile device (in this example "Greg's Phone") linked to a particular registered user.
  • a system user after registering one or more devices, might choose the Dashboard icon 321 to review status.
  • the status monitoring application 170 of the mobile device will detect if a change occurs in the operational status of the device, such as by changing from one operational mode or state to another operational mode/state.
  • date and time-stamp information might also be monitored and acquired for the date and time when the change in the operational status occurs 612, 616.
  • Such transaction information is provided to system 102, and available to one or more client devices communicating with system 102.
  • the dashboard interface 450 of Figure 13 might illustrate the date information 472, and the time information 474 (with time zone) in the form of a dashboard transaction entry.
  • the data and time-stamp information may be captured and stored by status monitoring application 170 for the device. Then, when an operational status change occurs, such as when the device exits or leaves the disabled Airplane mode or moves to some other second mode, such as a normal operating mode, similar date and time-stamp information might be captured and stored for that event. Therefore, effectively, a start time/date and stop time/date is captured and logged for the device when it enters and exits a disabled mode that disables certain communication features or prevents some distracted usage.
  • the time period in the desired disabled state or mode is calculated from the start and stop time endpoints.
  • the status monitoring application 170 may provide additional information to system 102 regarding the change in the operational status of the mobile device so that the additional information may be reported.
  • a change in the operational status of the mobile device may occur in a number of different ways, as discussed herein.
  • a user of the mobile device may go from being in Airplane mode or Do Not Disturb mode to then directly exiting the Airplane mode or Do Not Disturb mode.
  • Such a direct change in the operational status may be indicated appropriately as a direct mode change, as illustrated in field 479, as shown in Figure 13.
  • Figure 13 only provides an example illustration of some of the various different designations or transactions that might be reported and displayed indicating the type of change in the operational status that occurred at the mobile device for the purposes of displaying a status change in a graphical interface, as shown in Figure 13.
  • pop-up field 480 other information captured by the status monitoring application 170 might be provided, such as an error message or the fact that the status monitoring application was incorrectly deactivated, or that the desired operational state or mode was incorrectly disabled, and thus indicated as a change in the operational status. For example, if a particular mode was exited in some way other than as directly instructed by the mobile device and status monitoring application, the noted transaction might be indicated as a status change with additional information 480 that the application was improperly disabled or deactivated (See Figure 22). A greater or lesser amount of transaction information as that illustrated in the example of Figure 13 might also be captured by the mobile device system and be provided in the reporting interface 450, 460. Generally, it would be desirable to provide a display of the status change transaction along with associated time and date information.
  • additional information might be provided to a system user or other monitor in the form of a notification message, such as an email message or text message that the device user is activating the status monitoring application, or that a change in operational status has occurred, or that a transaction has been completed.
  • a mobile device user may have deactivated the application 170 because they are done driving or performing some particular task.
  • a system user may select or indicate that they wish to have a notification message sent for one or more of the particular monitored devices.
  • the system user can also select one or more email addresses, mobile phone numbers, or other destinations for such a notification message.
  • an email address is provided, and appropriately associated with one or more of the selected devices.
  • Multiple destinations e.g., multiple email addresses, multiple telephone numbers, etc.
  • multiple devices might be associated with a message destination, such as an email address. In that way, upon a mobile device user
  • a notification message may be sent to the selected message destination.
  • an email message is sent indicating that a mobile device user (Brian's Phone) or a particular mobile device has changed status.
  • the application 170 of the mobile device in addition to reporting information 618, might also determine 620 if message notification was enabled for the system user record and device. If message notification is enabled for a device, a notification of the status change is sent as a message 622.
  • a message transaction might also be logged 624 to then also be displayed in a dashboard interface 450, 460, when reporting information to a system user.
  • a notification might be indicated by text 370 in the email message of Figure 18 that the mobile device or the associated user of the device is back online, or has "checked in”, or, in other words, has deactivated the status monitoring application, and currently now has an enabled device after a certain period of non-use, or being "checked out”.
  • other messages might be implemented to indicate the change in status, such as "User's device now enabled”.
  • additional information might be provided in the email message of Figure 18, such as the length of time that the device user or device was in a particular state or mode. Referring to Figure 18, the additional information 372 indicates an amount of time in the disabled mode or state, similar to the information set forth in fields 474, 476 of Figure 13.
  • multiple email addresses or message destinations might have been indicated for the particular device, and thus, a notification message would be sent to those addresses. That can provide a system user, or other monitor, desired information, and/or peace of mind with respect to the user of the device. For example, a device user may have been traveling to a particular destination, and thus, entered into a disabled operational mode preventing distractions, such as texting and text messages, email messages, or other distractions. It would be desirable for a monitor, such as a parent or employer, to know that they arrived safely, have checked back in, and were not distracted while driving. Therefore, in addition to the information on interface dashboard 450, notification messages might be implemented for a system user, as desired for one or more devices to report the change in operational status for different devices and users.
  • notification messages are handled by the system 102, and may be directed out to various client devices 106, or mobile devices 104, depending upon the selected destination for the notification message.
  • a mobile device 104 which is being monitored, might also send such notifications directly.
  • the necessary user record information for one or more user records 142 might be provided to one or more mobile devices 104.
  • Such a mobile device such as a telephone, or a pad device that has the ability to provide email messages, text messages, or other messages, might send such messages directly to the destinations that had been selected by a system user or monitor, as illustrated in Figures 7 A - 7E, when
  • the device 104 in addition to reporting data on the status of the mobile device 104 to the system 102, the device 104 might use the status change information directly to send notification
  • the graphical user interface 450 of Figure 13 might provide a limited number of incidences or transactions associated with changes in the operational status of the mobile device
  • field 490 might provide the ability to see older information associated with a status change.
  • the graphical user interface 450 provided by the monitoring system 102 through one or more client devices 106 might have other pages, such as other dashboards or pages (not shown), wherein all of the devices to be monitored are displayed and might be selected for viewing the status change information, as illustrated in Figure 13. Accordingly, the present invention is not limited to only the specific graphical user interfaces shown in the figures for displaying status information.
  • the system implements components for notifying a mobile device user that they should activate the application, and thus, disable their mobile device from various communication aspects and functions.
  • the beacon components may let the device users know that they are in a particular location, wherein a specific task is likely to be performed, and thus, they should not be distracted. The user is then instructed by the status monitoring application to activate the application, and thus, disable some of the functionality of the mobile device that would allow such distractions, such as phone, texting, or email features.
  • one or more beacon devices 220, 222, 224 might be implemented in the system.
  • beacon devices are implemented in locations, such as a car, where driving should not be distracted, in a building, wherein a particular task, such as providing healthcare, is to be executed, or some other location where a mobile device user should not be distracted by their mobile device.
  • the present invention is not limited to the areas where a beacon might be implemented.
  • beacons when different devices are registered with system 102, such as through the dashboard interface 320, one or more beacons might be designated for the registered mobile devices.
  • System 102 then communicates the beacon information, including a label for the beacon as well as the identification information, to each of the mobile devices.
  • the status monitoring application 170 of the mobile device is operable for scanning for particular registered beacons that might be associated with the device using Bluetooth ® or other wireless technology. In that way, the mobile device reacts to only those registered beacons with which it has been associated through the system 102, and not to all beacons it may encounter.
  • a beacon device might be placed in each car of a family, and given a particular label.
  • a beacon device might be associated with a building, such as a hospital building, or a surgical center.
  • the present invention is not limited to the specific locations or installations of desirable beacons. The invention will recognize one or more associated beacons, and will utilize the captured information regarding the beacon identification and the label associated with that beacon identification to inform the mobile device user, as well as a system user, that a beacon has been detected by a specific mobile device.
  • the status monitoring application provides a message or alert, such as on the screen of the mobile device, that a particular beacon has been detected.
  • the name of the beacon is displayed.
  • the device user will also be directed to open and activate the status monitoring application.
  • a mobile device screen 500 will display a message 502, such as on a separate pop-up screen, that a beacon has been detected 630.
  • a beacon associated with a car such as a CAR 1
  • the message 502 further instructs the mobile device user to activate the status monitoring application 602 on the mobile device.
  • the activation might be done by engaging icon 504 on the screen to open the application, and then putting the device into the disabled Airplane mode.
  • the message might remain on the screen for some time to be seen by a device user, and then may time out and disappear.
  • a beacon that is part of the system, and is registered and associated with one or more mobile devices, is provided in a location that coincides with a task to be performed. As noted, if the location is within a car, generally, the task to be performed is driving. The present invention thus discourages
  • a beacon device is located in a hospital, the message 502 from the mobile device will instruct a mobile device user, such as a doctor or other caregiver, to activate the status monitoring application, and thus, disable certain functional features of their phone.
  • a mobile device user such as a doctor or other caregiver
  • the invention discourages the caregiver from being distracted by their mobile device while they are providing care to a patient.
  • Various other distraction scenarios might also be addressed by the implementation of a beacon device in accordance with the invention.
  • Figure 16B illustrates another message 506 associated with the detection of a beacon.
  • Message 506 is in the form of a pop-up screen that advises a beacon has been detected, and has selectable fields 508, 510. Rather than disappearing automatically like the message 502 in Figure 16A, the message 506 might remain on the screen until it is closed, such as by engaging field 508.
  • the application might actually be activated by engaging field 510, which would then open the application 602, and take a device user to the application screen, such as those shown in Figures 9A - 9C. Therefore, the user would not have to otherwise open the status monitoring application, such as through an icon 504, but it would be opened automatically from the message displayed.
  • the dashboard interface 460 might report to a system user other related transaction or device interaction information, such as that a notification is sent, or that an interaction with the beacon has occurred for a particular mobile device.
  • a notification is sent, or that an interaction with the beacon has occurred for a particular mobile device.
  • an engagement with the beacon by the mobile device is captured or logged as transaction data 632, and may be
  • the logged beacon information can be accessed, such as through a dashboard interface accessed through a client device 106.
  • the system 102 might display a transaction message for a particular beacon.
  • the dashboard interface 460 illustrates a number of different system transactions indicating that a mobile device was disabled in some way, in accordance with the invention.
  • other logged transactions might indicate other related information, such that the mobile device has detected a beacon.
  • Still another displayed logged transaction might be an activation message that the user has opened the application 170, and is getting ready to activate it (See Figure 1 1 , 610), as noted above.
  • Different combinations of captured or logged transactions or interactions are displayed, depending upon how the device user actually activated application 170 to monitor a device.
  • the transactions 510 when a beacon is detected, the logged transaction information is displayed as a transaction, including the date and time information associated with the beacon detection, as well as the label associated with a specific beacon that has been detected.
  • Figure 14 illustrates the detection of beacons associated with cars (e.g., CAR 1 , CAR 2, etc.).
  • the mobile device user is instructed to activate the status monitoring application ( Figures 16A, 16B). Once that application is activated, the mobile device will be disabled to some extent, and the device user will not be distracted.
  • an activation message as shown in Figure 1 1 , might be sent and might be reported and displayed as a transaction in the dashboard interface 460.
  • transaction messages 512 indicate that an activation message was sent, and that the device user has opened the application on the device.
  • a system user who is monitoring one or more devices can track the various transactions in the interface dashboard 460, and determine how the mobile device is being used and/or disabled. For example, referring to the "Saturday" entries of Figure 14, when a beacon has been detected, the device user is instructed to activate the status monitoring application for the mobile device (see Figures 16A, 16B). That beacon detection creates a message ( Figures 16A, 16B), and is also displayed as a logged transaction 510 (See Figure 14).
  • the system processes the information and provides a display of the transaction 479 at an appropriate dashboard interface 450, 460.
  • the transaction 479 in Figure 14 follows the beacon transaction 510 and activation transaction 512.
  • beacon detected 510 one sequence of displayed transactions will be indicated as beacon detected 510, activation message 512, and then completed Airplane mode transaction 479.
  • a beacon might be detected 510, but then no activation message sent prior to a device user activating the status monitoring program (e.g., NO in Figure 9C). Then, the next displayed transaction is the completed Airplane mode transaction 479.
  • the completed transactions (e.g., Airplane mode, Do Not Disturb) might be completed by a device user without being prompted by a beacon, and also without sending any sort of activation message.
  • the transactions of Thursday in Figure 14 a user might open the status
  • the information provided in the dashboard interfaces 450, 460 can be interpreted by a system user to determine how a mobile device is being used. For example, if a beacon has been detected, the system user would normally expect a completed transaction 479 to follow shortly thereafter if a device user did as instructed, and disabled their device. Similarly, if an activation message transaction 512 is displayed, the system user might also expect a completed transaction 479 to follow in a related time frame.
  • a system user can see that a beacon was detected, and that the user responded by going to activate the status monitoring program on the mobile device. Furthermore, following the activation message transaction 512, the system user can also see that the device was disabled according to some selected disabled mode for a period of time following the detection of the beacon. As may be appreciated, the status monitoring application on the mobile device does not have to be activated pursuant to detecting a beacon, but can be activated at any time the user decides.
  • dashboard interface 460 there may be certain transactions 479 on the dashboard interface 460 that are not preceded by a beacon detection transaction 510. Similarly, if the user opens the foreground screen of the application, as illustrated in Figures 9A, 9B, but chooses not to send an activation message, no activation message transaction 512 will precede the transaction 479. Accordingly, various different combinations of transactions may be reported on dashboard interface 460 depending upon how the mobile device is implemented and how the status monitoring application is activated and deactivated.
  • the application is configured to detect if wireless connectivity is turned off in accordance with another aspect of the invention. More specifically, for Bluetooth ® connectivity, in one example, the status monitoring application 170 can detect when the Bluetooth ® functionality of the mobile device 104 has been turned off. As may be appreciated, because the system 10 may rely upon one or more beacons 220 which are detected utilizing a wireless standard, such as Bluetooth ® , it is important to inform a system user, parent, or other supervisor that a user may have turned off the Bluetooth ®
  • the application 170 in the illustrated example, once it has been downloaded onto the mobile device and opened at least once, will periodically run a check on the mobile device for the Bluetooth ® functionality.
  • the application 170 logs the appropriate data associated with the Bluetooth ® settings of the mobile device. If the application 170 detects that the
  • Bluetooth ® functionality is turned OFF, the application will capture information associated with the date and time of that detection.
  • the application will log the date and time information as one end point of transaction data and will report the date/time information to monitoring system 102.
  • the logged Bluetooth ® data can then be reported as a transaction, such as in a
  • the application 170 might operate to periodically have a device interaction ( Figure 1 1 , 614) to determine if there is a Bluetooth ® transaction or some other transaction to report.
  • a dashboard interface 470 is shown having reported transactions or interactions associated with the Bluetooth ® detection features of the invention. Specifically, if the application 170 has a device interaction and detects that the Bluetooth ® functionality is turned OFF, it will report the logged data as illustrated in transaction 492 with a "Bluetooth Off" message, along with the date/time information that was logged by the application. In that way, a system user will see that the beacon feature of the invention may not be implemented because the mobile device user cannot detect one or more registered beacons. They might then inform the mobile device user to turn the Bluetooth ® functionality back on, such as with a message on the device (See Figures 16A, 16B, for example).
  • a message informs the mobile device user that the Bluetooth ® functionality is OFF and that it should be turned on, such as to use the beacon features of the invention.
  • a specific message (not shown) might be displayed on the device interface screen noting "You have turned OFF Bluetooth ® , please turn Bluetooth ® ON to enable full functionality of the application.
  • the message might be temporary or may be in the form that requires action by the user to respond and make it disappear from the screen.
  • the application 170 will continue to monitor the Bluetooth ® functionality for the purpose of verifying that the Bluetooth ® functionality has been restored. Once the Bluetooth ® functionality is restored or turned ON and once the application 170 logs information regarding the mobile device having that functionality turned back on, the application then reports the logged information as a completed transaction, as illustrated by reference numeral 494 in Figure 15. As noted, the reported transaction 494 notes "Bluetooth Off” and sets forth suitable time/date information regarding the transaction to illustrate that Bluetooth ® is back on, and how long the
  • Bluetooth ® functionality may have been turned off.
  • the status monitoring application of the invention detects if the Bluetooth functionality had been turned off and alerts a system user to such information 492.
  • the application 170 continues to scan or detect that feature for the mobile device, and also reports when the Bluetooth ® functionality is turned back on or otherwise restored so that the beacon devices of the invention may be detected. The length of time that the functionality was off is reported as well 494.
  • the application 170 if the application 170 detects that the Bluetooth ® functionality is off, it will record the time/date information and report the transaction, as illustrated 492 in Figure 15. While the application 170 continues to monitor or poll the mobile device to determine if Bluetooth ® functionality has been restored, until that
  • dashboard interface 470 as illustrated in Figure 15, is not
  • status monitoring application 170 on the mobile device 104 allows the mobile device user to record an incident that occurs during use of the invention, such as an emergency incident.
  • the incident is recorded so that it might be reported as a transaction to a system user.
  • One particular use might be to provide an indication that something out of the ordinary has occurred, such as an accident, and thus a mobile device user will be deactivating the status monitoring application 170 and again restoring communication connectivity to the mobile device.
  • the invention since the invention is particularly useful to prevent distracted driving, it may occur that a mobile device user is involved in an accident. As such, the user may want to use their phone to make one or more phone calls, such as an emergency 91 1 call or a call to a parent.
  • the mobile device interface screen 390 might provide an incident icon or field 398 on the touch screen (incident button). That incident button 398 may be engaged by the mobile device user when they are using the invention and have an activated application that is monitoring the device for an operational status change. Once the button 398 is engaged, the application 170 captures time/date information regarding the incident and the engagement of the button. Such information is logged as transaction data for the incident.
  • the "incident" transaction may also be reported, such as in the dashboard interface 470.
  • the incident transaction data When the incident transaction data is logged, it will be reported to system 102 once the communication connectivity is restored, such as upon deactivating the status monitoring application 170 and again enabling communication functions of the mobile device.
  • a completed transaction 479 will have been logged and reported (see Figures 13 - 15).
  • the incident transaction prior to reporting the completed transaction 479, the incident transaction is reported and is illustrated in Figure 15 at 496.
  • the incident transaction 496 might then be followed by the reporting of the completed transaction 479.
  • the transaction 496 reports the engagement of the incident button 398 and the time/date information associated therewith. This illustrates to a system user that the mobile device user experienced some incident and deactivated the application 170 and restored device connectivity pursuant to the occurrence of that incident, such as an accident or some other emergency wherein the use of the mobile device was required.
  • a message screen similar to those illustrated in Figures 9C, 16B and 18 might be provided on interface screen 390.
  • the message might state "Do you want to record an incident” and may give the mobile device user the option of answering “YES” or "NO”. If they choose “YES”, the application 170 will proceed as noted herein. If “NO”, the interface screen 390 may return to the foreground screen, as illustrated in Figure 9B. This prevents inadvertent engagement of the incident button 398.
  • screens/dashboards 450, 460 that might be provided on a client device for reporting the status change in one or more devices, the user device itself might also be utilized effectively as a client device.
  • the status monitoring application 170 of a user device is functional to access status information associated with that user device, and display the status
  • a field might be provided on the application screen 390 of the device for accessing a dashboard display.
  • the status monitoring application 170 of the user device provides a direct link to system 102, and the status information associated with that particular user device.
  • icon fields such as shown in 404 and 406 might be configured and functional when engaged to provide such a direct link to displayed status information associated with the user device.
  • a dashboard similar in some ways to 450, 460 shown in Figures 13 - 15 might be displayed on screen 390, as shown in Figure 20.
  • FIG. 20 illustrates a suitable dashboard screen 530 on a mobile device.
  • Screen 530 might display various transactions like a beacon detection transaction 532, a disabled mode transaction 534, and/or an activation message transaction 536.
  • the device can be unlocked to report the incident.
  • the incident button may then be engaged (and confirmed if necessary) and then the status monitoring application can be deactivated, such as by enabling the device again, so that the incident is reported appropriately to a monitoring system 102 as illustrated in Figure 15 at 496.
  • the status monitoring application 170 on the device is running even when not open and can track and report on the operational status of the device even if the application 170 is not opened on the foreground screen of the device. Therefore, various actions may be taken to disable the device and the operational status of the device may be reported with time information even when the status monitoring application 170 has not been specifically opened and brought to the foreground on the device, such as through a touch screen engagement with an icon/field.
  • This provides further flexibility in the use of the device.
  • such an embodiment might be implemented with a device running the application 170 with an Android operating system.
  • the device might be placed in a disabled operational mode by being turned Off, either with the status monitoring application open or not.
  • a selection might be made through an appropriate field 650 to power Off the device without opening the application 170 on the device.
  • the status monitoring application 170 might be opened as illustrated in Figure 26.
  • the application 170 of the device might provide a message field 652 as illustrated in accordance with a messaging feature of the invention for indicating the device will be placed in a disabled operational mode.
  • the device can then be powered Off through engagement with field 654 as illustrated in Figure 27.
  • Figure 28 illustrates a dashboard screen 656, such as on a device that is also running a monitor interface application, for providing status reporting for the device. As noted, status might be reported and accessed from another computer or is also available on the device itself, such as through an icon/field.
  • the entry 674 indicates the device had been in a Powered Off mode for some period of time on the noted date, such as when the monitoring application 170 was not opened but the device was powered Off.
  • the entries 672, 674 indicate the device being powered Off after the application 170 was opened as in Figure 26 and an activation message sent. In both cases, the operational status change, such as the device being powered back on, was reported.
  • the Airplane mode might be selected in the way previously described for initiating the status monitoring application. That is, the status monitoring application is opened or engaged and brought to the foreground screen and then the control center for the device might be opened for selecting an Airplane mode and then the control center is closed.
  • the monitoring application is active and in the foreground for the device, and the device is in the Airplane mode.
  • the monitoring application can be left in the foreground screen and visible or the phone might be locked.
  • the control center can be opened and the Airplane mode deactivated. Then the application can be closed. If the device screen is locked, in one embodiment, the user can go directly to the control center without bringing the status monitoring application to the foreground and then deselect airplane mode and close the control center to complete the reporting entry.
  • the application can be opened and an activation might be sent through engagement with field 680, such as when the application has been enabled to send email or other alerts/messages to others.
  • the control center can be opened as illustrated in Figure 30.
  • the airplane mode can be selected as indicated by the icon and field 682 in Figure 31 .
  • the control center can be closed as illustrated in Figure 32.
  • the status monitoring application screen as shown in Figure 32 can be left in the foreground as the device is put down or put aside to limit distractions. Alternatively, the phone might be locked as discussed herein. Then once the operational status changes, such as when a user goes to use the device for a distracting activity, the change in status is reported.
  • the device might be put into the Airplane mode directly through the control center without opening the status monitoring application 170 and bringing it to the foreground. If Airplane mode is selected in that way, the device is in what might be considered a non-restricted Airplane mode. Since the status monitoring application 170 is loaded on the device, in accordance with one feature, the selection of a particular disabled mode through the control center will activate the status monitoring application even though the application 170 is not opened directly and is not brought to the foreground screen. For example, referring the Figure 33 and as seen by the icon 684 on the phone screen, a monitoring application is loaded on the device, but is not directly opened or activated.
  • the user can directly engage the control screen as illustrated in Figure 34, and then activate or select the Airplane mode as indicated by the icon and field 688 in Figure 35. Then the control screen can be closed to reveal a screen 650 without the status monitoring application screen in the foreground as indicated by Figure 36.
  • the device is in the Airplane mode as shown by icon/field 690.
  • the application 170 is not directly open and displayed but is functioning and the device user might then be able to use the device in various ways allowed by the Airplane mode that do not require connectivity. Such use will not be considered by the application 170 as a change in operational status. For example, if a user is listening to music on the device, they might be in the disabled operational mode but still be able to manipulate the device for controlling their music.
  • the device is in what may be considered an unrestricted disabled mode, and may be used in some ways without such use being reported as a status change.
  • This use is only allowed in Airplane mode where the device has no connection to a network.
  • any change in the operational status such as being taken out of the airplane mode, will be reported in accordance with the invention.
  • the monitoring application 132 might provide additional information in a dashboard entry indicating that the device was in a particular mode, like the unrestricted Airplane mode, for the time noted. Referring to Figure 37 which shows a dashboard screen displayed on a device, if the Airplane mode was entered without opening the Application directly and bringing it to the foreground screen, as noted above, when the status change is reported to the
  • the entry might read as in entry 687 with a separate icon 689 showing the mode was an unrestricted mode and the user could have been doing other things with the phone.
  • the icon is an unlocked padlock.
  • Other icons could be used as well to indicate an unrestricted mode.
  • the application will be working in the background even though not directly opened and brought to the foreground screen.
  • the device might be taken out of that disabled operational mode or the mode may be deactivated or changed in certain ways.
  • the control center may just be opened, the Airplane mode turned Off and then the control center closed.
  • the device is in Airplane mode. From the screen shown in Figure 38, the control center may be accessed as shown in Figure 39.
  • the Airplane mode field/icon 693 is engaged to deactivate the mode and restore operational service as shown in Figure 40. Then the control center may be closed ( Figure 41 ). The device has thus had its operational status changed and is active and can be used in a distracting manner.
  • the status monitoring application 170 will evaluate changes in the operational mode associated with the device being originally in such a disabled operational mode and then being brought back into a usable or enabled mode, which is considered a change in the operational status.
  • the user can proceed or is instructed to proceed to the control center for the device in order to select a disabled operational mode and thus activate the monitoring application to begin monitoring the device.
  • the disabled operational mode might be selected in other ways.
  • the device might be put into a disabled operational mode directly from the screen associated with the opened status monitoring application 170 rather than proceeding to the control center.
  • the monitoring application then monitors the device for a change in the operational status. That is, a device may be operating under an operating system wherein the monitoring application is active in the background without being opened and brought to the foreground screen.
  • This provides additional ways for putting the device into and out of a disabled operational mode for monitoring purposes.
  • a monitoring application operating with an Android operating system might be used to implement such an embodiment.
  • the device might be placed in a disabled operational mode without having to engage the control center for the device. Rather, the device might be placed into such a mode directly from the status monitoring application 170 and an open or foreground screen associated therewith.
  • FIG 48 a screen is shown for a device where the monitoring application is available as shown by icon/field 700.
  • the icon 700 might be engaged to open the application 170 and thereby monitor the device in a disabled operational mode and report a change of status in accordance with features of the status monitoring application 170.
  • a user After the status monitoring application is opened as illustrated in Figure 49, a user might be given a message or prompt through field 702 to send an activation message as earlier noted, such as in Figure 9C, in accordance with one feature of the invention.
  • Figure 50 reflects a foreground screen for the open status monitoring application (such as after sending an activation message) and provides a selectable field 704 for enabling a disabled operational mode for the device.
  • the device may be placed in a disabled operational mode or disabled right from the status monitoring application screen.
  • the Do Not Disturb (DND) mode for the device is shown.
  • the device By engaging the field 704, the device is placed in the DND mode and the status monitoring application is activated to note the change in status and and a time and then subsequently to report any change in the operational status of the device. Confirmation of the disable step might be required and screen Figure 51 shows a message 705 for confirmation of selection of the disabled operational mode such as the DND mode.
  • DND Do Not Disturb
  • Figure 52 illustrates a screen that indicates that the application is activated and in DND mode and the sync status field 710 and a changed color thereof might reflect the activated status monitoring application and another disabled operational mode, since it is in DND mode rather than Airplane mode.
  • field 712 is provided and might be engaged to take the device out of the disabled mode (DND mode). Therefore, the device may be disabled and again enabled from the application 170. If field 712 is engaged, the device is taken out of DND mode. This will result in a change in operational status in the invention and is reported as such.
  • the user might be given a notification as shown in field 714 of Figure 53 to confirm that the device is to change operational status. In this case, the DND mode is being turned Off. If DND is turned Off, the screen returns to the screen of Figure 50. The change in status is reported appropriately in accordance with the invention.
  • the DND mode might be another disabled mode that might be selected directly from the control center.
  • the device screen is shown and has the status monitoring application 170 thereon as illustrated by icon/field 719.
  • the user might go directly to the control center as illustrated in Figure 55.
  • the DND mode might be activated by engaging field 720.
  • a particular submode might be selected as illustrated in Figure 56 to activate the DND mode.
  • the DND submodes might provide for different connectivity depending on the device. For example, “Total Silence” will block everything, whereas the submode “Alarms only” might block everything except for a phone call.
  • the submode "Priority Only” might block everything except a phone call from a programmed list of callers. Then the control center can be closed as illustrated in Figure 57.
  • a confirmation message with selectable field 724 might be displayed to confirm the enablement of a DND mode as shown in Figure 57. After confirmation, the screen similar to the screen of Figure 58 is displayed and indicates that the application is activated and in DND mode, with the DND mode having been selected through the control center.
  • the device In order to deactivate the DND mode, there are several ways that might be accomplished, either through the monitoring application screen interfaces or through the control center directly as disclosed herein for entering the DND mode.
  • the device Referring to Figures 59-62, the device might be locked as shown in Figure 59, and can be unlocked thereby showing the screen if Figure 60 with the opened or foreground status monitoring application screen illustrated. Then the user can select Disable DND mode as in field 740 of Figure 60.
  • a message with fields requiring confirmation of the mode change might be provided as in Figure 53. If the mode or status change is confirmed (select Yes in Figure 53) the screen of Figure 61 shows the status change on the monitoring application screen, (e.g.
  • the control center might be opened to deactivate the disabled DND mode directly and bring the device to an operational status, thus triggering the reporting of the status change, without opening the monitoring application.
  • the control center can be brought up ( Figure 64).
  • the device is in a DND mode as illustrated by icon/field 746.
  • the DND mode can then be disabled (such as by selecting a "Total silence" field 746 for example) as shown in Figure 65 where DND is disabled.
  • the control center might be closed ( Figure 66).
  • the device In order to close the monitoring application, the device might be unlocked, thus revealing the screen of the monitoring application 170 ( Figure 67).
  • the monitoring application might then be closed ( Figure 68).
  • the invention even when a device has been placed into a disabled operational mode, there may be some features of the device that are not disabled and are still active. In such scenarios, in addition to capturing information about a change in operational status to the monitoring application, the invention also captures data related to other activities that might be done with the device by a user. This data is collected even if a particular reportable change in operational status has not occurred and the device is still in a disabled operational mode. Then such additional data may be reported along with any change in operational status in a dashboard as discussed herein. That is the status monitoring application is operational to capture and report other information in addition to a change in the operational status of the application.
  • a telephone call may still be made or received without taking the device out of the DND disabled operational mode. Therefore, the invention captures data regarding a call and reports such activity in addition to reporting any change in operational status. In accordance with another feature, the activities that occur may be reported differently depending on the type of activity and the data captured.
  • the status monitoring application might be opened for a device in the various ways as noted herein, such as by engaging an application icon on the device screen. Then the user might be advised to put the device in a disabled operational mode and then the device may be put into a disabled mode, such as, for example, the DND mode on the device. An activation message might be sent to a selected recipient indicating that the status monitoring application is being activated or opened for monitoring of the device. That sent activation message might be reported as shown in entry 800. During the time the device is in a DND mode, the user may receive an incoming call, and the application 170 captures data about that incoming call.
  • an entry 802 shows the incoming call and essentially the duration of same.
  • the dashboard entry 802 for the incoming call like other entries as discussed herein, contains date and time information and other information as appropriate for the data that was captured for that event and dashboard entry.
  • the device is still in the disabled operational mode of DND for posting the entry 802, the device reports data to the monitoring application 132 and system 107 and using that data, the dashboard reports a stopped DND entry 804 when the incoming call was answered. That data entry and time thereof matches up with the start of the call.
  • the call duration is noted as well in the entry 802 from the data captured from the device.
  • a new DND entry 806 will reflect the end of the call as the beginning of that entry, once the entry is ultimately reported, such as when the device is taken out of DND mode.
  • Such an entry similar to 802 is made when the incoming call is either a handheld call or a handsfree incoming call, such as through a vehicle Bluetooth system.
  • the device remains in DND mode, as it was not taken out of that mode for the call. Rather, the entries 804, 806 on either end of the call entry 802 indicate the mode that the device is in, and remains in, during the incoming phone call.
  • the final entry 806 will be made when there is a change in operational status, such as the device is actually taken out the of the disabled operational mode or DND mode eventually for normal use of the device. That information about the user being on the phone while the device was in the DND mode may be of interest to one or more parties concerned with the distraction of the device user.
  • Figure 70 illustrates a recordation of an outgoing call that is made while the device is in a disabled operational mode such as a DND mode reflecting the additional data and information captured by the device and then reported in accordance with the invention.
  • a call might be made from a handheld phone, rather than handsfree (such as through a vehicle Bluetooth system).
  • the application 170 may be opened and the device placed in the disabled operational mode by the user, with an activation message sent for the device as shown in entry 810.
  • the user makes an outgoing call such as with a handheld phone and the application 170 captures data about that call.
  • the call data is reported and an entry 812 shows the outgoing call and essentially the duration of same.
  • the device is still in the disabled operational mode of DND, but for posting the entry 812, the dashboard reports a stopped DND entry 814 when the outgoing call was made that generally is close to the time of the start of the outgoing call.
  • the type of activity that might occur in a disabled operational mode of a device might be categorized differently than other activity.
  • an outgoing call might be considered more distracting than an incoming as the user has to dial or take some other action rather than just answering.
  • the call is made from a handheld phone, that might be particularly true as discussed in Figure 70.
  • additional information regarding the use of the phone and the call mode ie., hands free or handheld
  • application 170 on the device is captured by application 170 on the device and reported to the application 132. Then that additional information can be displayed.
  • entry 814 since the call was handheld, the entry for the DND reporting right before reporting the outgoing call has additional activity information reported.
  • an icon 818 indicates the handheld nature or mode of the outgoing call.
  • the icon is a red triangle with an exclamation point therein;
  • Figure 71 indicates further reporting of an outgoing call and reporting of data regarding the mode of the call.
  • the call was placed through a handfree system, such as a vehicle or other Bluetooth system and additional activity data is captured reflecting how the call was made.
  • the device might connect to the
  • Bluetooth system of a vehicle for example and such an event is reported in the dashboard by entry 820.
  • the application 170 on the device may then be opened.
  • an activation message might be sent indicating the opening of the application 170 and reported appropriately to program 132 for display as shown in entry 822.
  • the device may then placed in the disabled operational mode by the user.
  • the user can make an outgoing call.
  • the call is made through the connected Bluetooth system and therefore could be a handsfree and additional activity information associated with the way the call is made is captured.
  • an entry 824 shows the outgoing call and essentially the duration of same.
  • the dashboard reports a stopped DND entry 826 that stops when the outgoing call was made.
  • the device is still in DND mode.
  • a new DND entry 828 is started that reflects the end of the outgoing call.
  • the backend entry 828 again, is reported when the device ultimately is taken out of DND mode. Since the call was handsfree, albeit still outgoing, the application 132 can use the additional activity information that was recorded with the device and reported and make a determination to not add any additional information to the entry in this example. As such, the entry 826 before the outgoing call entry 824 does not have any icon or other information displayed since the call was handsfree.
  • the program 132 treats the reporting differently.
  • additional activity information such as an icon, might be provided in entry 826 or another entry if that is desired in another embodiment of the invention wherein every outgoing call scenario is reported and displayed with additional activity information for a person to review and monitor.
  • the additional activity information that is captured might be displayed in the form of an icon on the dashboard.
  • that additional information might be used or displayed with a dashboard reporting entry that is normally
  • a change in the operational status such as an entry noting that the device was in a DND mode for a certain period of time. That is, when the device operational mode is changed and reported, additional activity information that is captured by the device regarding calls made will be reported in the form of an icon and will be displayed along with the entry to denote call activity while the device was in a DND or other disabled mode. Also, the initiation and completion of a call might act as the beginning of a particular entry or the end of an entry when the device status change is reported at the dashboard screen as discussed below.
  • the data regarding the stopped entry will be captured by the device and then recorded and displayed as shown in the previous entry 854.
  • the new entry 850 that is triggered by an outgoing phone call will be started at the time of the start of the outgoing call.
  • the previous entry 854 for the time in DND mode is indicated as ending around 12:07:26 or around the start of the outgoing call.
  • the duration of the status entry 850 will last until the device is ultimately taken out of the disabled operational mode (DND mode) or until the user makes another outgoing call, for example. Then, when there is a change in the operational status of the device (e.g.
  • the entry 850 associated with the call is completed, the information about that status change and the outgoing call is recorded and reported to applicaton 132 and then displayed.
  • a person reviewing the dashboard screen of Figure 72 will know that an outgoing call was made and will have information about the time of that call.
  • the device having a change in operational status to end the entry and trigger the reporting of entry 850 if an incoming call occurs during the duration of the entry 850, that might also end the entry as discussed herein.
  • the incoming calls might also be recorded in a dashboard entry similar to the reporting of a change in operational status but with additional activity information reported, such as with a particular icon.
  • additional activity information reported, such as with a particular icon.
  • Such incoming calls occurring when the device is in a DND mode may reported with an icon such as 858 with soundwaves to indicate incoming calls.
  • the current entry duration is stopped when the incoming call is concluded and then the entry 856 is reported with the additional activity information like icon 858.
  • the entry 856 indicates that the device was in a DND mode and an incoming call was received some time during that duration.
  • entry 856 tells a person monitoring the device that an incoming call was received sometime during the duration of entry 856.
  • an outgoing call might be made which starts a new monitoring duration and entry, and then as that duration in DND mode continues, an incoming call might be received.
  • the completion of the incoming call will stop the duration of that entry and it will be reported to the application 132 for display. Since both an outgoing call (to start the duration/entry) was made and then an incoming call also occurred (ending the current duration entry), then when the status is reported as in entry 860, the additional activity information regarding the calls is reported and then both icons 862 are displayed with other information in the entry 860. A person monitoring the device would know that calls were made and received during that duration.
  • the start of the entry is indicative of the start of the outgoing call and the end of the entry indicates the end of the incoming call. Therefore, you generally would only get double icons in the scenario of entry 860. Two outgoing calls made back to back would be shown in separate entries since each outgoing call stops the current entry and results in the sending of data to program 132 and reporting of the current entry and then triggers the capture of data and reporting for a new
  • the status monitoring application 170 is automatically opened and activated based upon one or more trigger conditions or triggers that are detected by the device, and the device is automatically placed in a disabled operational mode. That is, the user does not have to open the status monitoring application on the device.
  • the application may be opened automatically and the device put into a disabled operational mode for the detection or satisfaction of some trigger conditions.
  • the application 170 may be opened automatically, and the user might be prompted to take further action to put the device into a disabled operational mode.
  • a device operating with an Android operating system might function with automatic features as noted herein.
  • a device may be configured for operating with the automatic features of the invention by selecting or activating one or more of the trigger conditions for the device to detect. Depending on the trigger condition or conditions that are selected, different automatic features are activated in the device as part of the status monitoring program 170.
  • a drop down menu 900 might present a selectable setting field 902 and once engaged, the various trigger conditions for automatic operation are displayed as illustrated in Figure 74. The conditions may be activated by being turned ON.
  • the various trigger conditions might include the detection of motion, such as in a vehicle, per a selectable field 904, the connection to a Bluetooth system, per selectable field 906, or the detection of a beacon device, per selectable field 908.
  • any one of those trigger conditions to ON will automatically activate the program 170 upon the detection of a satisfied trigger condition with the device, and will put the device automatically into a disabled operational mode. That is, the user will not have to open or activate the status monitoring program 170 and will not have to put the device into a disabled operational mode as with other embodiments of the invention.
  • the Motion Detection trigger field 904 is ON or activated and therefore the status monitoring application 170 will monitor the motion of the device, such as while traveling in a vehicle. When a certain speed of motion is detected based on a set threshold, several automatic actions happen through the application 170. The status monitoring application 170 is opened and brought to the foreground screen of the device. Also, the Motion Detection is automatically noted or reported in the reporting dashboard. An activation message is automatically sent if a message feature is active and recorded on a reporting dashboard, and the device is
  • the disabled operational mode is a DND mode.
  • the threshold might be set from 10-20 miles per hour or some other threshold to meet the trigger condition.
  • dashboard screens are shown with various entries showing activity with a device and recordations of the status of the device and additional information associated with use of the device and changes in the operational status of the device.
  • entry 950 upon a Motion Detection trigger condition being ON in the settings and upon detecting motion that meets the trigger condition (speed greater than a threshold), an entry for the detected motion is automatically recorded and displayed. Then the automatically sent activation message is recorded and displayed with entry 952.
  • the device is automatically placed in the DND mode and the status monitoring application is opened in the foreground on the device.
  • the device is monitored and when there is a change in the operational status, such as the device being taken out of the DND mode, the change in the operational status is reported as noted herein, such as at entry 954. Because the status monitoring application was automatically triggered, the entry 954 will also have additional information noting the automatic nature of the status monitoring. In the illustrated embodiment, an icon "A" 956 is shown with entry 954. The entries 950-954 have the same start time when in such an automatic scenario as illustrated.
  • reminders to a user might be used for certain trigger conditions to cause some reporting and action to occur automatically but to allow the user to control whether the device will be put into the disabled operational mode. That is, such a device will not be put into a disabled operational mode automatically.
  • a reminder regarding motion might be used as a trigger condition as noted by Motion Detection Reminder field 910.
  • Motion Detection Reminder trigger field 910 is ON in the settings and motion is detected that meets the trigger condition (speed greater than a threshold)
  • an entry for the Motion Detection Reminder is automatically recorded and displayed as shown in entry 966 of the dashboard screen of Figure 85.
  • the application 170 is automatically opened and brought to a foreground screen with a message screen that is provided to the device user to note the Reminder, such as is shown in Figure 87.
  • a message 960 notes the Motion Detection Reminder and gives the user the option to send an activation message through fields 962.
  • the user wants to put the device into a disabled operational status, such as a DND mode, the user can manually engage field 964 once the activation message is sent and the message screen disappears as discussed herein. (See Figure 73).
  • the Motion Detection Reminder trigger option gives the user the ability to have a trigger condition such as motion as a reminder and sends an automatic dashboard entry and message to the user and
  • the application will prevent additional triggering or notification of the Motion Detection trigger conditions until the vehicle motion is below the threshold for a set amount of time, such as 5 minutes for example. In that way, once the motion is triggered and the device either automatically put into the disabled operational mode or the user given a reminder, there will not be further triggering or reporting until the vehicle stops or stays below the threshold speed for some set amount of time.
  • Another trigger condition might be connection of the device to another device or system through a wireless network.
  • the Bluetooth Connection trigger field 906 is ON or activated and therefore the status monitoring application 170 will monitor the connection of the device to some other system or device through a Bluetooth or other connection.
  • connection to a device or system through some other wireless connection might also be monitored.
  • One such Bluetooth connection might be to the system of a vehicle that the user is driving in order to prevent distraction to the user/driver by the use of the device.
  • the status monitoring application 170 is opened and brought to the foreground screen of the device.
  • the Bluetooth Connection is automatically noted in the dashboard. An activation message is automatically sent if a message feature is active and recorded on a reporting dashboard, and the device is automatically placed in a disabled operational mode.
  • the disabled operational mode is a DND mode.
  • dashboard screens are shown with various entries showing activity with a device and recordations of the status of the device and additional information associated with use of the device and changes in the operational status of the device.
  • entry 970 upon a Bluetooth Connection trigger condition being ON in the settings and upon detecting connection to a device/system through a Bluetooth wireless connection that meets the trigger condition, an entry for the
  • Bluetooth connection is automatically recorded and displayed. Then the automatically sent activation message is recorded and displayed with entry 972.
  • the device is automatically placed in the DND mode and the status monitoring application is opened in the foreground on the device. The device is monitored and when there is a change in the operational status, such as the device being taken out of the DND mode, the change in the operational status is reported as noted herein, such as at entry 974. Because the status monitoring application was automatically triggered, the entry 974 will also have additional information noting the automatic nature of the status monitoring.
  • an icon "A" 956 is shown with entry 974.
  • the entries 970-974 have the same start time when in such an automatic scenario as illustrated.
  • the status monitoring application is configured to detect only Bluetooth connections to multimedia systems, such as a multimedia system of a vehicle. In that way, those types of connections that might indicate scenarios wherein a device user should not be distracted are detected. Other connections, such as to a Bluetooth headphone device or some other device that does not indicate a non- distraction scenario, would not trigger the automatic features of the multimedia systems.
  • a reminder regarding a wireless connection might be used as a trigger condition as noted by the Bluetooth Connection Reminder field 912.
  • a Bluetooth Connection Reminder trigger field 912 is ON in the settings and a Bluetooth connection is detected that meets the trigger condition (multimedia system of a vehicle), an entry for the trigger condition (multimedia system of a vehicle).
  • Bluetooth Connection Reminder is automatically recorded and displayed as shown in entry 990 of the dashboard screen of Figure 85. Then the application 170 is automatically opened and brought to a foreground screen with a message screen that is provided to the device user to note the
  • a message 1000 notes the Motion Detection Reminder and gives the user the option to send an activation message through fields 1002. Then if the user wants to put the device into a disabled operational status, such as a DND mode, the user can manually engage field 1004 once the activation message is sent and the message screen disappears as discussed herein. (See Figure 73).
  • the Bluetooth Connection Reminder trigger option gives the user the ability to have a trigger condition such as a Bluetooth connection as a reminder and sends an automatic dashboard entry and message to the user and automatically opens and brings the application 170 to the screen of the device. This allows a person monitoring the activity of the user and the device to know that the user was reminded that they are doing a task such as driving and should put the device in a disabled operational mode. The user still has the choice to do so or not do so, but they have been warned and the warning is documented.
  • Bluetooth Connection trigger conditions are triggered once and will not be triggered again unless the device is disconnected from the Bluetooth or other system and then reconnected. In that way, there are not multiple instances of triggering or reporting in the dashboard.
  • Still other trigger conditions such as the detection of an external signal by the device might be used to trigger the automatic features of the invention based on the settings of the device. (See Figure 74).
  • detecting a beacon signal might provide automatic operation in accordance with the features of the invention.
  • the Beacon Referring to Figure 79, the Beacon
  • Detection trigger field 908 is ON or activated and therefore the status monitoring application 170 will monitor the detection of a signal such as a beacon signal. In other embodiments, detection of some other external signal might also be monitored.
  • a beacon signal might be a beacon signal from a beacon in a vehicle that the user is driving in order to prevent distraction to the user/driver by the use of the device.
  • Another external signal might be a beacon signal from a beacon that is in a facility wherein the user is to not be distracted while working or doing another task.
  • the status monitoring application 170 is opened and brought to the foreground screen of the device.
  • the Beacon Detection is automatically noted or reported in the reporting dashboard.
  • An activation message is automatically sent if a message feature is active and recorded on a reporting dashboard, and the device is automatically placed in a disabled operational mode.
  • the disabled operational mode is a DND mode.
  • dashboard screens are shown with various entries showing activity with a device and recordations of the status of the device and additional information associated with use of the device and changes in the operational status of the device.
  • entry 980 upon a Beacon Detection trigger condition being ON in the settings and upon detecting a signal from a beacon that meets the trigger conditions (such as a registered beacon), an entry for the Beacon Detection is automatically recorded and displayed. Then the automatically sent activation message is recorded and displayed with entry 982.
  • the device is automatically placed in the DND mode and the status monitoring application is opened in the foreground on the device.
  • the device is monitored and when there is a change in the operational status, such as the device being taken out of the DND mode, the change in the operational status is reported as noted herein, such as at entry 984. Because the status monitoring application was automatically triggered, the entry 984 will also have additional information noting the automatic nature of the status monitoring. In the illustrated embodiment, an icon "A" 986 is shown with entry 984.
  • the entries 980-984 have the same start time when in such an automatic scenario as illustrated.
  • FIG. 80 shows each of the conditions of fields 904, 906, 908 being ON. Any combination of those trigger conditions may be ON. If more than one trigger condition is selected or ON for automatic operation, the first trigger condition detected will perform the appropriate reporting and automatically put the device into a disabled operational mode and open the status monitoring application and bring it to the foreground screen. Also, the entry will be noted as being automatic, such as with the "A" icon.
  • trigger condition e.g., Motion Detection or Bluetooth Connection or Beacon Detection
  • the application since the application is open and the device already in a disabled operational mode automatically, they process will not be repeated and only the trigger condition detection is recorded and displayed.
  • the status monitoring application will disable certain reminder trigger fields from being selected if the underlying trigger condition is selected and ON. For example, if the Motion Detection trigger condition 904 is active (ie., the setting field is ON), the Motion Detection Reminder trigger condition 910 cannot be activated. Referring to Figure 80, since all the underlying trigger conditions are active (904, 906) the reminder trigger conditions (910, 912) are disabled. Figure 81 shows the Motion Detection trigger condition as OFF or
  • the Motion Detection Reminder trigger condition 910 may be selected as shown along with Bluetooth Connection and Beacon detection trigger conditions. If either of the active automatic trigger conditions (906, 908) are detected first, the status monitoring application will operate as noted turning the application on and putting the device automatically in a disabled operational mode. If the Motion Detection Reminder is then subsequently triggered, it will be suppressed by the application 170 since the device is already in a disabled operational mode and the application is On and in the foreground. Any of the other automatic conditions 906, 908 that are triggered would only have a single entry in the dashboard as noted herein. However, if the Motion Detection Reminder is triggered first, the application will proceed as described herein with the message of Figure 87 and other automatic actions. If the user does not put the device in the disabled operational mode and/or closes the program 170, the automatic trigger conditions 906 and 908 are still active and could still be triggered
  • Figure 82 discloses a Motion Detection Reminder trigger condition 910 as activated or ON and the Bluetooth Connection trigger condition 906 as ON.
  • the reminder field may be selected to be ON since the automatic Motion Detection trigger condition 904 is OFF. If the Bluetooth Connection is triggered first, the device will automatically be in a DND mode and therefore features of the Motion Detection Reminder directed to placing the device is a disabled operational mode will be suppressed. There will only be a dashboard entry of the trigger condition.
  • Figure 83 illustrates both reminder trigger conditions 910, 912 as ON. If either one is triggered, the application 170 is brought to the foreground and a dashboard entry is made, such as entries 966 or 990 in Figure 85. Also, a reminder notification screen, such as in Figures 86, 87 is displayed on the device. The application can be activated and the device put into a disabled operational mode, or the user can close the application. If the application is not activated, the next reminder condition will repeat the process again. If the application is activated and the device put into a mode such as DND mode, then triggering of the other reminder trigger will result in a dashboard entry but no further action.
  • a dashboard entry such as entries 966 or 990 in Figure 85.
  • a reminder notification screen such as in Figures 86, 87 is displayed on the device.
  • the application can be activated and the device put into a disabled operational mode, or the user can close the application. If the application is not activated, the next reminder condition will repeat the process again. If the application is activated

Landscapes

  • Engineering & Computer Science (AREA)
  • Human Computer Interaction (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne un système et un procédé pour décourager l'utilisation inappropriée d'un dispositif mobile, consistant à enregistrer un dispositif mobile à l'aide d'une application de surveillance s'exécutant sur un système couplé à un réseau. Un dispositif mobile est relié à l'application de surveillance via le réseau. L'état opérationnel du dispositif mobile est surveillé pour détecter si un changement se produit dans l'état opérationnel. Un changement dans l'état opérationnel du dispositif mobile est signalé au programme de surveillance avec des informations temporelles, et le changement d'état est affiché dans une interface graphique, et un message de notification est envoyé à un utilisateur du système. Des balises pourraient également être mises en œuvre pour inviter un utilisateur du dispositif à désactiver un dispositif mobile à surveiller.
PCT/US2018/040764 2008-02-15 2018-07-03 Système et procédé pour décourager l'utilisation inappropriée d'un dispositif mobile Ceased WO2019010210A1 (fr)

Priority Applications (5)

Application Number Priority Date Filing Date Title
EP18750554.0A EP3649771A1 (fr) 2017-07-03 2018-07-03 Système et procédé pour décourager l'utilisation inappropriée d'un dispositif mobile
CA3069011A CA3069011A1 (fr) 2017-07-03 2018-07-03 Systeme et procede pour decourager l'utilisation inappropriee d'un dispositif mobile
US16/253,078 US11356549B2 (en) 2014-01-07 2019-01-21 System and method for discouraging inappropriate use of a mobile device
US17/831,015 US12200584B2 (en) 2014-01-07 2022-06-02 System and method for discouraging inappropriate use of a mobile device
US19/016,616 US20250150794A1 (en) 2008-02-15 2025-01-10 System And Method For Discouraging Inappropriate Use Of A Mobile Device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201762528308P 2017-07-03 2017-07-03
US62/528,308 2017-07-03

Related Parent Applications (2)

Application Number Title Priority Date Filing Date
US14/590,814 Continuation US9621707B2 (en) 2008-02-15 2015-01-06 System and method for discouraging inappropriate use of a mobile device
US15/481,953 Continuation-In-Part US10187513B2 (en) 2008-02-15 2017-04-07 System and method for discouraging inappropriate use of a mobile device

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/253,078 Continuation US11356549B2 (en) 2008-02-15 2019-01-21 System and method for discouraging inappropriate use of a mobile device

Publications (1)

Publication Number Publication Date
WO2019010210A1 true WO2019010210A1 (fr) 2019-01-10

Family

ID=63113626

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2018/040764 Ceased WO2019010210A1 (fr) 2008-02-15 2018-07-03 Système et procédé pour décourager l'utilisation inappropriée d'un dispositif mobile

Country Status (3)

Country Link
EP (1) EP3649771A1 (fr)
CA (1) CA3069011A1 (fr)
WO (1) WO2019010210A1 (fr)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150195399A1 (en) * 2014-01-07 2015-07-09 20/20 Cte, Llc System and method for discouraging inappropriate use of a mobile device

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8270933B2 (en) * 2005-09-26 2012-09-18 Zoomsafer, Inc. Safety features for portable electronic device
US20160345131A9 (en) * 2012-04-04 2016-11-24 Port Nexus Corporation Mobile device tracking monitoring system and device for enforcing organizational policies and no distracted driving protocols

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150195399A1 (en) * 2014-01-07 2015-07-09 20/20 Cte, Llc System and method for discouraging inappropriate use of a mobile device

Also Published As

Publication number Publication date
CA3069011A1 (fr) 2019-01-10
EP3649771A1 (fr) 2020-05-13

Similar Documents

Publication Publication Date Title
US12200584B2 (en) System and method for discouraging inappropriate use of a mobile device
US10187513B2 (en) System and method for discouraging inappropriate use of a mobile device
US11132849B1 (en) Vehicle telematics and account management
Chang et al. Investigating mobile users' ringer mode usage and attentiveness and responsiveness to communication
US11490239B2 (en) Emergency reporting application
US10027795B1 (en) Mobile device monitoring system
US20030091158A1 (en) Monitoring and communication system for stationary and mobile persons
US20090253454A1 (en) Automatic changing mode of a communication device
EP2481256B1 (fr) Environnements pour dispositifs de communication du service mobile sélectionnables par l'utilisateur
US20130328665A1 (en) Generating Context-Based Options for Responding to a Notification
US10326877B2 (en) Driving without distraction support system
US11206508B2 (en) Electronic device and method for managing operation thereof while operating vehicle
US20070123287A1 (en) Method and apparatus for providing the status of a wireless communication device in a group network to other members in the group network
WO2011119273A2 (fr) Système et appareil permettant de localiser et de surveiller des personnes et/ou des abords
US11146912B1 (en) System automatically updating database information based on a user's specified geographical location
CA2972892A1 (fr) Plateforme de securite mobile
US20130052945A1 (en) Mobile communicator and system
US9736867B2 (en) Emergency radio communications system incorporating integral public safety radio bridging capability
KR20140100396A (ko) 기기 알림 동기화 장치 및 방법
US9866677B1 (en) Mobile device monitoring system
US20250150794A1 (en) System And Method For Discouraging Inappropriate Use Of A Mobile Device
US20170193807A1 (en) Alarm system on a device connected to a network
US11405772B2 (en) Monitoring and direct communications between mobile devices system and method
WO2019010210A1 (fr) Système et procédé pour décourager l'utilisation inappropriée d'un dispositif mobile
Kadry Safe drive in smart city

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18750554

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 3069011

Country of ref document: CA

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2018750554

Country of ref document: EP

Effective date: 20200203