WO2012044449A1

WO2012044449A1 - System and method for third party monitoring of events created or taken by a cellular phone

Info

Publication number: WO2012044449A1
Application number: PCT/US2011/050866
Authority: WO
Inventors: Jr. Joseph William Witkins; Jeremy John Witkins
Original assignee: WYD EYE SOFTWARE LLC
Current assignee: WYD EYE SOFTWARE LLC
Priority date: 2010-09-08
Filing date: 2011-09-08
Publication date: 2012-04-05
Anticipated expiration: 2013-03-08

Abstract

A system and method for monitoring cellular phone events by a third party, the system and method including a server for creating an account through a website linked to the server, wherein the account is accessible by a user and verifying an email address for the user, configuring account parameters for the account for receiving and reporting events from a cellular phone, assigning an access code to link the phone with the account, installing an application on the cellular phone capable of capturing and transmitting events created or taken by the phone, activating the application on the phone and linking the phone to the account by entering the access code when starting the application for the first time, capturing any events created or taken by the phone, transmitting the events to the server from the phone periodically, and providing a periodic report from the server to the verified email address.

Description

TITLE: SYSTEM AND METHOD FOR THIRD PARTY MONITORING OF EVENTS CREATED OR TAKEN BY A CELLULAR PHONE

RELATED APPLICATIONS

[0001] This application claims priority to U.S. Provisional Application No. 61/380,950 entitled System For Mitigating Transmissions Of Certain Undersirable Or Illegal Content Over Wireless Data Systems In Particular Mobile Telephone Systems/Networks filed September 8, 2010, the contents of which is expressly incorporated herein by reference.

TECHNICAL FIELD

[0002] The present invention generally relates to monitoring content transmitted by telephone networks and in particular a system and method for providing a third party the ability to monitor events created or taken by identified cellular or smart phones.

BACKGROUND OF THE INVENTION

[0003] The Internet and cellular phones provide many new problems for controlling the dissemination of harmful, distasteful, or illegal information. Additionally, the difficulty controlling the use of resources and the ability to control the dissemination of valuable information is ever increasing as business is increasingly conducted utilizing cellular and smart phones.

[0004] In the area of cellular data transmission, for example, a behavior commonly referred to as "sexting" has become an epidemic problem involving both adults and minors transmitting nude or other inappropriate pictures or data regarding themselves, friends, or others, over the text network or other cellular transmission channels. The State of Illinois,

USA, for example, has made such transmission illegal as of 2010. Numerous states in the

USA alone have either adopted or are contemplating adopting similar legislation.

[0005] Others have proposed systems for individuals or business to monitor mobile phone use have provided some utility, but are for the most part, too cumbersome - including being prohibitively expensive - and require a prohibitive time requirement by the monitoring individual to be effective in any way, because of the in-depth and profuse amount of data required to make decisions or to take action to prevent and/or mitigate "sexting" or other harmful, unauthorized, or illegal transmissions in a timely, comprehensive fashion.

Additionally, many of these systems require parents, corporate employees, or other monitoring individuals to log into an account, creating the feeling that the monitoring individual is spying or acting in an otherwise improper way while monitoring the phones. 100061 The present invention is intended to provide to parents or other supervisors of an Internet or cellular transmission accounts and devices the ability to monitor the content of any events created or taken by the monitored phone.

[0007] It would be advantageous to improve on existing systems by providing, among other things - a simple, easy to use, system that is inexpensive, as well as requiring significantly reduced time and effort to manage events created or taken by a cellular device and/or account transmission. Importantly, a focus on pre-emption of activity as one aspect to reduce or eliminate a phone user's desire and ability to transmit or receive valuable, proprietary, illegal, unauthorized, and inappropriate events with their mobile phones.

[0008] It is through these systems, their economic advantages and ease of operating of same, versus the prior art, that the present inventor believes the goal of preventing individuals of using Internet and/or the mobile data system to disseminate undesirable, unauthorized, or illegal data will be best served.

SUMMARY OF THE INVENTION

[0009] According to one broad aspect of the invention, a system for monitoring and mitigating the transmission of undesired content on the Internet, and more preferably on the mobile phone network, is provided by, for example, providing a user account administrated, at least in part, by a service provider having a server for collecting, storing, and reporting events created or taken by cell phones the user seeks to monitor.

[0010] According to one embodiment one or more mobile device(s) having one or more account(s) administrated in a public cellular network for cellular transmission and reception, are linked to the user account, to provide the account owner certain control and monitoring ability over and/or information regarding, selected types of transmissions and receptions from and/or to, the account(s) and/or mobile device(s), through the operation, at least in part, by the one or more computing devices (irrespective of the provider).

[0011] According to another aspect of the invention, a system is provided wherein the mobile devices are cellular phones.

[0012] According to one aspect of the invention, a method of monitoring events created or taken by at least one cellular phone is provided. In order to monitor the events, an individual or user seeking to monitor the cell phone activity must first create an account and register with a service provider providing a server used to gather, store, and report cell phone events.

In order to create an account and register with the server, the user must verify an email address and receive an assigned access code for linking each monitored phone to the user's account. Once the user has verified the email address and received the access code, each phone the user seeks to monitor must download and install an application ("the App") that is linked to the server and capable of capturing and transmitting phone events. After the App is installed on each phone, the assigned access code must be entered to activate the App on the phone and to start the monitoring of phone content and insure that call captured and transmitted events are provided to the proper user account and provided in a report to the proper verified email address.

[0013] Once the App is activated each phone, the App may capture each event created or taken by the phone - like for example SMS and MMS messages transmitted from or received by the phone, each picture taken by or downloaded to the phone, emails sent from or received by the phone - and periodically transmit the captured events to the server. Once the server receives the captured and transmitted events, the server will buffer the events to the proper user accounts, format the events for delivery in a report to the proper user email address, create the report, and provide the report periodically to the verified email address of the user monitoring the phone events.

[0014] According to another aspect of the invention, the App may be configured to restart if it is disable for any reason, including but not limited to: becoming disabled because the phone is moved to an out of service area; the phone is powered down intentionally or because the battery dies; or because the App is turned off by the individual holding the phone or by the phone itself. If however, the App is removed from the phone, the App is configured to require the access code be re-entered before the App will restart.

[0015] According to another aspect of the invention, the App may be configured to provide a periodic heart beat signal to the server to indicate that the App is enabled, functioning properly, and that the phone is turned on and in a service area or in compunction with the server. If the heart beat signal is not provided to the server, the server may be configured to provide a notification or report to the user monitoring the phone, or provide notification in the periodic report, indicating that the heart beat signal was not received by the server for a particular reporting period(s).

[0016] According to another aspect of the invention, the App may be configured to capture and store events created or taken by the phone locally on the phone and periodically transmit the same to the server for inclusion in the periodic report. Storing the captured events on the phone locally allows for the transmission of events that are created or taken by the phone and deleted from the phone before a periodic transmission the events, or new events that are created or taken by the phone and not transmitted before the phone, for example, enters a no service area or is turned off.

[0017] According to another aspect of the invention, the service provider may be a cellular network service through whom the user has a primary account already linked to or responsible for multiple subsidiary accounts the primary account holder seeks to monitor.

[0018] Other advantages and aspects of the present invention will become apparent upon reading the following description of the drawings and detailed description of the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

[0019] FIG. I shows an embodiment of the system as contemplated by the invention;

[0020] FIG. 2 shows an embodiment of the server and application and server communication as contemplated by the invention;

1 0211 FIG. 3 shows a flow chart depicting an overview of the method contemplated by the invention;

100221 FIG. 4 shows a flow chart of the creation and login in method for user account's as contemplated by the invention;

[0023] FIG. 5 shows a flow chart of the monitoring method contemplated by the present invention;

100241 FIG. 6 shows a flow chart of the capturing method contemplated by the present invention;

[0025] FIG. 7 shows a flow chart of the capturing method contemplated by the present invention;

100261 FIG. 8 shows a flow chart of a method as contemplated by the present invention.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

1 0271 While this invention is susceptible to embodiments in many different forms, there is described in detail herein, preferred embodiments of the invention with the understanding that the present disclosures are to be considered as exemplifications of the principles of the invention and are not intended to limit the broad aspects of the invention to the embodiments illustrated.

[0028] FIG. 1 shows a system for monitoring events created or taken by a cellular phone by a remote user or individual. System 100 includes a server 102 operated by a service provider, the server being used for: registering and storing user account information and setting the user parameters; receiving transmitted events created or taken by on one or more phones monitored by the user; generating a periodic report for all events created or taken by the one or more phones monitored by the user; and, emailing the periodic report to the user. In order to register with the server, the system includes website 104, the website being accessible by users to: register with the server; review the events received by the server from one or more monitored phones; re-configure stored user information and user parameters; and, download and save any events received by the server. In order to capture events on the at least one monitored phone, transmit the events to the server, and ultimately report the events to an user, system 100 further includes software application 106 which is downloaded onto the one or more monitored phones 108. Software application 106 is capable of capturing all events created or taken by the one or more phones and puts the one or more monitored phones 108 in communication with the server 102 so the captured events are periodically transmitting the same to the server 102.

[0029] It is contemplated by the invention that server 100 may be maintained and operated by a service provider through whom the user currently has a cellular phone account, or alternatively through a third party service provider capable of providing the service. In embodiments where the service provider is the service provider through whom the user currently has a cellular phone account, it is contemplated by the invention that any subsidiary accounts linked to the primary account, and for which the primary account holder is responsible for, may be monitored by the primary account holder. In such embodiments, any fee charged by the service provider for utilizing the monitoring system may be incorporated into the monthly or periodic bill provided from the service provider to the primary account holder responsible for the primary and subsidiary accounts. Additionally, a primary account holder may configure a setting with the service provider to install and activate application 106 on all phones 108 purchased for any subsidiary account linked to the primary account. It is also contemplated by the invention that the user may monitor additional phones not linked to the primary account in any manner through their service provider, or by utilizing the service as provided by a third party service provider for monitoring at least one phone. Installation, activation, and monitoring, whether done by the primary and/or subsidiary account holders themselves or by the service provider at the time of the purchase of the phone may be accomplished using the methods described herein.

[0030] FIG. 2 shows an embodiment of server 102 and application 106 as used by phone 108.

Application 106 on phone 108 contains an event listener module 200 which captures and transmits the events to server 102. The events captured by event listener module 200 transmits the data to event data base 202 on server 102 where the events are stored until system administrator 204 buffers the captured events and provides the captured events to the proper user account in account database 206. The events stored in account database 206 may be accessed and reviewed by a user through the user's account page 208. In addition to being used to access events stored in the user's account in account database 206, account page 208 may be utilized to sign up and join the service and system, to set up and configure or reconfigure any parameters for event listener 200 to capture and transmit events to event database 202, like for example the types of events that are capture and transmitted and the period selected events are captured and transmitted. A user may also set and configure or reconfigure parameters related to a periodic report of events emailed to the user through event emailer 210 at client administration module 212. Any parameters and accounts are controlled by account administration module 214 which processes the reported events and controls the emailed report information and the time each report is sent to a user's verified email address.

[0031] FIG. 3 shows a method by which system 100 may be used to monitor cellular phone events by a remote, private third party. While the method in its broadest form may be utilized with any mobile phone capable of communicating over a wireless network, the present invention is particularly capable of monitoring smart phones, and more particularly smart phones operating with an "Android" or "Droid" operating system ("OS").

[0032] As seen in FIG. 3, in order to implement the method and remotely monitor at least one cell phone, a third party individual or user must first create a user account with a server hosted by a service provider providing monitoring of events created or taken by at least one cell phone 300. When creating the account, the individual remotely monitoring the at least one cell phone must create a username and password and verify an email address 302 to be linked to the account. Once the email address is verified, the individual may configure parameters for receiving and reporting events from the at least one cell phone to the verified email address 304 and assign an access code to the user account for linking the at least one cell phone to the user account 306. At the same time as creating an account, or any time before or after, in order to monitor the at least one phone, an application ("App") must be downloaded and installed on any phones the user seeks to monitor 308. Once the App is downloaded and installed on the at least one phone, the App may be activated and begin monitoring events created or taken by the at least one phone by entering the access code 310 to "start" the App and monitoring process. Entering the access code also links the at least one phone and events created or taken thereon to the proper user account in the server, insuring the vents of that phone are report to the correct user. After activation, the App will capture all events created or taken by the at least one phone 312, and transmit the same to the server periodically 314. The server is configured to receive these transmitted events, and transmit the same to the verified email address in the form of a periodic report 316 detecting each monitored event.

[0033] FIG. 4 shows the process through which an individual may create an account or log into a previously created account to begin, or continue, to remotely monitor a linked cellular phone. In order to create an account utilizing the website provided by the service provider for users to access the server, an individual may access the website 400 through any device capable of accessing the Internet and World Wide Web, like for example a mobile smart phone or a desktop, laptop, or tablet computer. When creating the account 402 with the server through the website, the individual will be required to provide a user name, a password, and an email address for receiving the periodic reports detailing the at least one phone's events, and alternatively may provide information such as, their name, mailing address, alternative methods of receiving reports or events like for example an alternative or additional email addresses or a mobile phone number, the names and phone numbers of the phones that are to be monitored, and payment information for utilizing the monitoring service.

[0034] When creating the account, the access code for activating the App and linking the at least one cell phone to the account will be assigned. The access code may be assigned by the individual or user creating the account selecting and inputting an access code created by them, or alternatively may be a randomly assigned code generated by the server and provided to the individual or user. Regardless of how the access code is assigned, it is contemplated by the invention that multiple access codes may be used in accounts where more than one cell phone is monitored by a single user account. In embodiments where the individual selects and inputs the access codes, the individual may input any number of additional access codes, assigning a different access code to certain groups of monitored phones, or a different access code to each individual phone that is monitored. In embodiments where the a random access code is generated by the server and provided to the individual, it is contemplated that the individual may request additional access codes linked the account for using on different groups of monitored phones, or so the individual can have a different access code for each monitored phone.

[0035] Once the individual has completed the registration or account creation process and entered any required account information and provided any voluntary or additional information the individual wishes to provide, an email will be sent from the server to the email address provided by the individual to verify the user account and begin the monitoring and reporting process. In order to verify the user's email address the verification or confirmation email may contain a code which must be entered in order for the account registration to be completed and a link back to the user account page on the website through which the individual may will verify their email address 404 and access and activate their account the code. In embodiments where the individual seeks to provide additional email addresses for accessing the account and receiving a periodic report, verification of the additional email address(es) may be accomplished in virtually the same manner. For embodiments where an individual wishes to use an alternative means for accessing the account and receiving the periodic report, like for example on a cellular phone, the individual may be required to verify the alternative means. For example, if a user wants to verify and receive reports on a cellular phone, the individual may receive a text message with a PIN number or access code which must be entered through the individual's phone to gain access to the account. Similar to entering the access code on monitored phones, it is contemplated that the App may be downloaded onto the individual monitoring the at least one phone and the access code may be entered, allowing the individual to receive or access the report from their own cellular phone. In embodiments where the App is installed on the user's phone for monitoring purposes, it may be possible for the user to view a log of reported event in real time directly on the user's verified phone through the App. As should be appreciated by those having ordinary skill in the art, in order to differentiate the user's phone from monitored phones, a different access code may be entered. The viewing privileges of account information associated with each access code may be set by the user in the step described below.

[0036] Once registration is completed, the individual may log into their account 406 through the internet or as otherwise described herein, and obtain an overview 408, for example, of any events transmitted from any monitored phones, any current activity or previously provided periodic reports currently stored on the server, and a summary of their current account settings and configured parameters for monitoring the events from the one or more linked phones and for receiving reports on the same.

[0037] From the account overview, the user may access and set or change the parameters or account settings configured for monitoring and reporting events from the at least one monitored phone 410. Access to set or change the parameters may be found directly on the overview page, or alternatively may be provided by clicking on a link or tab on the overview webpage containing the account overview. Examples of parameters which may be set on the website by the user include, but are not limited to: setting the events to be captured by the application on each monitored phone, transmitted to the server and reported in the periodic report; setting a period for the application to capture events on the at least one phone; setting a period for the application to transmit captured events to the server; requiring a periodic heart beat signal from the phone to the server and setting the period in which the heart beat signal must be received; setting the information and content reported for each event in the periodic report; setting parameters for sub-reports or highlighting specific events within each periodic report; configuring the period the report is provided by the server to the verified email address; and, authorizing or enabling the server to provide the periodic report to an alternative verified account, like for example a secondary email address or a cellular phone. It should be appreciated by those having ordinary skill in the art that any of these parameters may be set or adjusted by the user at any time by logging into their account and accessing the settings or parameters webpage. it should be further appreciated by those having ordinary skill in the art that the user may reset, change, or request additional access codes for activating and linking monitored phones to the user account from this page as well. Each of these settings and parameters will now be discussed with more detail.

|0038] Examples of events which may be monitored by the user and captured by the application, transmitted to the server, and included in the periodic report, include but are not limited to: standard text messages (SMS messages) transmitted from and/or received by the at least one phone; multimedia messages (MMS messages) transmitted from and/or received by the at least one phone; pictures (for example .jpeg files) taken by or downloaded to the phone from, for example, the internet or an external memory car; and, email messages and any associated attachments transmitted to, or received by, an email address linked to the at least one phone. It is contemplated by the invention users monitoring more than one phone may set different capture, transmit and report parameters for each phone or different groups of phones. For example, when used in a business setting, phones operated by sales people may capture, transmit and report all SMS, MMS, picture, and email events, while phones operated by engineers may capture only MMS, picture, and email events.

[0039] Monitoring any or all of these events will allow the user ultimately responsible and/or liable for activity related to the at least one cellular phone to monitor and attempt to prevent or mitigate illegal, wasteful, unnecessary, unauthorized, and inappropriate activity by individuals utilizing the monitored phones. For example, parents may utilize the method to prevent "sexting" by their children, or employers may use the method to prevent the dissemination of proprietary or confidential information, to prevent sexual harassment in the work place, or to prevent any or excessive personal usage of corporate provided phones.

Essentially, the method may be used by any user who seeks to monitor the events which are transmitted to or from, or taken by or downloaded to, a particular cellular phone.

100401 The frequency with which each of these events are captured by the App and transmitted to the server may also be set by the user on the account settings webpage. While events may be captured during any period, in a preferred embodiment, events may be captured in real-time as they occur, i.e. every time a SMS or MMS message is transmitted from the phone, the message is captured by the App. Likewise, the period captured events may be transmitted to the server from the at least one phone may be configured and set by the user as well. For example, captured events may be transferred from the at least one phone to the server once a minute, once every thirty minutes, or once every hour. While these periods are given as examples, it should be appreciated by a person having ordinary skill in the art that any period may be set by the user for capturing and transmitting monitored events, and such period may be identical or different as the user selects.

[0041] An example of the process for capturing events on the at least one phone and transmitting them to the server can be found in FIGs. 5-7. Though FIGs. 5-7 show the process for capturing and transmitting SMS and MMS messages sent from the phone, it should be appreciated by those having ordinary skill in the art that a similar method and flow chart is applicable to any of the aforementioned events which may be monitored, as well as any other data processes which may be created, taken, or received by the monitored cellular phone.

[0042] As seen in FIG. 5, when the App is activated on the at least one phone 500, the App will view the phone 502 and the state of the App 504 will be determined. If the App is being activated for the first time, the App will require that the access code be entered to initialize the App 506 and allow monitoring and reporting process to begin. When initialized for the first time, the App will observe events currently existing on the phone, shown in FIG. 5 as observe SMS 508 and observe MMS 510. If the App is installed, the App will close 512 until the OS alarm manager wakes the App 514 to capture and/or transmit all events created or taken by the phone 516. Once the App is awakened, it will observe events created or taken by the phone, once again shown as observe SMS 508 and observe MMS 510.

[0043] As should be appreciated by those having ordinary skill in the art, the App may periodically shut itself off, or be shut off by the OS, in order to save battery life on the phone.

As described herein, the App will automatically be woken or restarted based on the parameters configured by the user to capture events, transmit events, or provide a periodic heart beat signal to indicate that the App is functional and in communication with the server.

[0044] The process by which SMS messages, and other events containing a single data type, like for example pictures, may be observed and captured may be found in FIG. 6. While FIG. 6 shows only the process for observing, capturing, and transmitting sent SMS messages, the process for observing, capturing, and transmitting received SMS messages or other single data events will be substantially similar. In order to observe, capture and report any transmitted SMS messages 508, the App will first query the content of the SMS sent data contained on the at least one phone 600 and read the next SMS message 602. After reading the SMS message, the App will determine if the message is new. If the message is new, the App will timestamp and capture the message 604. If the App determines that the message captured 604 is not the last SMS message saved in the sent folder 606, the App will continue to read all saved messages. Once the App determines a time stamped and captured SMS message to be the last saved SMS 608, the App will determine the SMS address 610, add the event 612, increase the count 614. If there are no additional SMS messages 616, the App will return a new SMS count.

100451 The process by which multimedia messages or other events containing multiple data types, like for example emails, may be found in FIG. 7. As with the SMS message process, described above the App will query the MMS module in the phone 700, as shown in FIG. 7 as the sent MMS module, read the next message 702, determine if the next message is new, time stamp and capture the message 704 if it is new, and determine if the read MMS message is the last saved MMS message. If the read MMS message is not the last saved MMS message 706, the App will read the next message 702. If the time stamped and captured

MMS message is the last saved MMS message 708, the App will obtain the MMS address

710, add an event 712, and increase the count of the MMS messages 714. Where the MMS and other events containing multiple data types differ from SMS messages or other single data types is when no more MMS messages are found 716. Once the App has determine that all MMS messages have been read, time stamped, and captured, the App will query the MMS part: module 718 to determine additional parts or non-text portions of the MMS message 720, like for example a picture or jpeg file. If the App determines that there is no additional part to the MMS message 722, the App will continue querying the MMS part module. If the App determines that there is an additional part in the MMS message 724, the App will save the image attachment 726, and continue querying the MMS part module. Once the App has determined that there are no additional parts 728, the App will return a new MMS count.

[004 1 FIG. 8 shows another embodiment of how events on the phone are captured, stored, and transmitted to the server. As seen in FIG. 8, once the application is downloaded and installed on the phone 800, the App will process 802 all events based on the parameters configured in the user account by the user monitoring the at least one phone. The App will receive the set parameters from the user account when activated and periodically thereafter, and base on those parameters will: set the events that are extracted, captured, and stored on the phone; set the interval the stored events are extracted, captured, and stored on the phone; set the interval the stored events are transmitted to the server; and, transmit the events to the server. When extracting and capturing the events, the App will capture and record any monitored events in a separate internal file on the at least one phone, and periodically transmit the events stored in the separate file to the server based on the periodic interval set by the user at the server 804. The server will then incorporate the events into the periodic report and provide the report to the verified email address 806. The separate file may be configured to only be accessed by the App, and may be used to store any events not previously transmitted to the App, including events which are not transmitted because the phone is shut down or turned off before a periodic transmission containing the event occurs, because the phone is moved to a non-service area where a periodic transmission containing the event cannot occur, or because the event is created or taken by the phone and deleted before the next periodic transmission occurs. Since events can be captured and stored in the separate folder in real time, each event may be captured, no matter how fast the person utilizing the monitored phone removes the event from the phone, and eventually transmitted to the server for inclusion in the periodic report. In order to save memory on the phone, once each captured and stored event has been transmitted to the server in a periodic transmission, the event will be deleted from the separate file and removed from the at least one phone entirely.

[00471 In addition to capturing and transmitting events from the phone, a parameter may be set by the user to require that a heart beat signal be transmitted from the App to server periodically, regardless of whether any, or only when no, new events have been captured by the at least one phone. In embodiments where the heart beat signal is set by the individual, the server may be configured to report the non -receipt of the periodic heart beat signal to the individual for any reason. Reporting of the non-receipt may be configured to occur in real time, as soon as the signal is not received, or alternatively or additionally, in the periodic report detailing the events of the phone provided to the verified email address of the monitoring individual. Utilization of the heart beat signal allows the user to determine if the

App becomes disabled and/or loses communication with the server for any reason, allowing the user to follow up with the person utilizing the phone to discovery whether the person utilizing the phone has tampered with the App. Non-receipt of the heart beat signal may also provide a warning or notification to the user that the person utilizing the phone is in danger or has been kidnapped or the like.

[0048] In order to insure that the App periodically transmits captured events and any required heart beat signal in a timely fashion, the App may be configured to automatically restart if it becomes disabled for any reason. The App may be restarted by the OS through an alarm check waking the App to transmit data, or may be restarted by the OS if the App is turned off by the OS to preserve resources. If using, for example, an "Android" or "Droid" platform, the App may be restarted at a higher priority in the OS to insure the App is fully functional and able to capture all events created or taken by the phone. Once the App is restarted, it should be appreciated by those having ordinary skill in the art that any events stored on the phone not previously transmitted to the server will either be transmitted to the server immediately, or transmitted to the server during the next scheduled periodic transfer. Automatic restarting of the App helps curtail tampering by the person utilizing the phone and helps insure that the phone is monitored as frequently and efficiently as possible, and that as many monitored events are captured and transmitted to the server as is possible.

[0049] However, a "lock-out" feature will prevent restarting of the App if the App becomes disabled through being uninstalled from the at least one phone. Once the "lock-out" feature is activated, the access code will have to be re-entered when the App is reinstalled and restarted for events to be monitored and transmitted by the App. Utilization of the "lock-out" feature forces individuals who purposefully uninstall the App from a monitored phone to confess to intentionally disabling the App, and notifies the monitoring user that an event or multiple events that the user intended to prevent or mitigate may have occurred, alerting the user that additional investigation into the situation may be necessary.

[0050] As each captured event is transmitted to the server, the server saves each event to a common memory for all users, buffers the events, links the events to the proper account, formats each event for inclusion in the periodic report based on the users set parameters, and builds the periodic report, and transmits the report to the verified email address. The report may be transmitted in any period set by the individual at the server, like for example, the report may be transmitted to the verified email address every six, twelve, or twenty-four hours. In embodiments where the individual verifies at least one additional email address or a cell phone for receiving the periodic reports, the reports may be provided to each verified location at different intervals and may be configured to contain different information. For example, the periodic report to the first verified email address may be provided every twenty- four hours and contain every event configured to be captured by the App on the phone, while a secondary delivery for a verified cell phone may be configured to provide events from the at least one phone transmitted to a specifically identified phone number and any picture or image events, both being transmitted to the verified phone periodically or in real time.

[0051] The content included the report may be set or altered by the individual at any time after creating the account and may include, for example: the type of event; the full text associated with any events, like for example the full text of any SMS, MMS, or email messages transmitted from or received by the at least one phone; any additional media transmitted with any MMS or email messages transmitted from or received by the at least one phone; the sender or recipient of any SMS, MMS, or email messages; the date and time any SMS, MMS, or email messages are transmitted; any pictures taken by or downloaded to the phone; any web addresses visited by the phone; a list of the number of SMS and MMS messages transmitted to specifically identified numbers from the phone with the option of highlighting or creating a sub-report containing SMS and MMS messages transmitted to specifically identified numbers; and, a list of the number of SMS and MMS messages transmitted from the phone containing a specific word or words with the option of highlighting or creating a sub-report containing SMS and MMS messages containing specific words.

[0052] The user may further configure the parameters for the periodic report to set the delivery method of the report. For example, the user may set the report so that every event the App is configured to capture and transmit is provided in the report emailed to the verified email account, either directly in the email or as an attachment. Alternatively, the user may set the report to only provide a count of each event the App is configured to capture and transmit, like for example, the number of SMS messages, the number of MMS messages, and the number of pictures taken by the phone. As a further alternative, the user may configure the periodic report to email any sub-reports containing, for example, only SMS and MMS messages transmitted to one or more specifically identified phone numbers, SMS and MMS messages containing one or more specifically identified words, and any MMS messages containing pictures. Sub-reports may be emailed with a complete report detailing all monitored events, with a report containing a count of all monitored events, or in a report containing only the sub-reports. Regardless of what information is included in the periodic report provided to the verified email address, a link may be provided in the periodic report for the user to login into their account at the server and view, review, or download and save to an external memory device, any events the individual wants to save for their own records or as evidence of the event occurring. [0053] In order to format image events for the periodic report, like for example .jpeg pictures, the server may create a thumbnail image for each image event. Upon receipt of any image events from a monitored phone, the server may store the full size image while creating a scaled thumbnail of the image for inclusion in the periodic report to allow the individual to quickly view a smaller version of the image event, minimizing the size of the report emailed to the verified email address. If the individual wants to look at larger copy of the thumbnail image, the individual may log into their account on the server and view the image, or alternatively, click on the thumbnail image contained in the emailed report and be linked directly to the larger image at the server. As should be appreciated by those having ordinary skill in the art, if the individual has not logged into their account at the time of clicking a thumbnail image to view the enlarge image event, the server may require the individual to provide their username and password to view the full sized image.

[0054] In addition to saving full sized image events, the server is also configured to store each event reported by all monitored phones in a shared or common memory for a period of time, like for example seven days. After an event has been stored on the server for the set period of time after being reported in a periodic report, the event will be automatically deleted from the server. As long as the event is stored on the server, however, the user may log in and view or review all reported images linked to their account to view or review the event. When logging into the server and viewing any events or reports, the individual may be provided with a tab or other option to archive the event or report and/or download the event or report to an external memory device, like for example a USB memory stick or a PC hard drive.

[0055] As briefly discussed herein, returning to FIG. 2, it is also contemplated by the invention that individuals may log into their accounts 206 to view or review any provided periodic reports, or to merely view or review the stats or events of any or all stored reports 212. When doing so, either by accessing a report webpage from the login or overview screen, or directly from the overview screen, or alternatively by clicking the link to the server account provided in the emailed periodic report 214, the individual may access all stored details, events, and reports that have not yet been deleted from the server. The individual may also form a list of events to create a specific report of related events utilizing the webpage 21 8.

[0056] While in the foregoing there has been set forth a preferred embodiment of the invention, it is to be understood that the present invention may be embodied in other specific forms without departing from the spirit or central characteristics thereof. The present embodiments, therefore, are to be considered in all respects as illustrative and not restrictive, and the invention is not to be limited to the details given herein. While specific embodiments have been illustrated and described, numerous modifications come to mind without significantly departing from the characteristics of the invention and the scope of protection is only limited by the scope of the accompanying Claims.

Claims

CLAIMS What is claimed is:

1. A method of monitoring cellular phone events by a third party, the method comprising the steps of:

creating an account with a server through a website linked to the server, wherein the account is accessible by at least one user who wants to monitor outgoing messages from at least one cellular phone;

verifying at least one email address for the at least one user creating the account;

configuring account parameters for the account for receiving and reporting events from at least one cellular phone;

assigning an access code to link the at least phone with the created account at the server; installing an application on the at least one cellular phone, the application being capable of capturing and transmitting events created or taken by the at least one phone;

activating the application on the phone and linking the at least one phone to the account by entering the access code when starting the application for the first time;

capturing any events created or taken by the at least one phone;

transmitting the events to the server from the at least one phone periodically; and, providing a periodic report from the server to the at least one verified email address detailing any events created or taken by the at least one phone.

2. A method of monitoring events created or taken by a cellular phone, the method comprising the steps of:

assigning an access code with the server to link the at least one cellular phone with the created account;

installing an application on the at least one cellular phone, the application being capable of capturing and sending any events created or taken by the at least one phone;

activating the application on the phone and linking the phone to the account by entering the access code when starting the application for the first time; and,

restarting the application automatically if the application becomes disabled at any time.

3. A method of monitoring events created or taken by a cellular phone, the method comprising the steps of:

assigning an access code with the server to link the at least one phone with the created account;

installing an application on the at least one smart phone, the application being capable of capturing and sending any events created or taken by the at least one phone;

activating the application on the at least one phone and linking the phone to the account by entering the lCCCSS code when starting the application for the first time;

transmitting a periodic heart-beat signal from the phone to the server once the application is activated on the phone; and,

reporting to the at least one verified email address if the periodic heart-beat signal is not received by the server from the at least one phone.

4. A method of monitoring outgoing events created or taken by a cellular phone, the method comprising the steps of:

configuring parameters for the account for receiving and reporting activity from the at least one phone;

creating an access code with the server to link the at least one smart phone with the created account;

installing an application on the at least one smart phone, the application being capable of capturing any events created or taken by the at least one phone;

activating the application on the at least one phone and linking the phone to the account by entering the access code when starting the application for the first time; and, saving any events created or taken by the at least one phone, wherein the application will periodically transmit any events, including any events which are deleted or otherwise removed from the phone between reporting periods, while the application is disabled, or while the phone is in a non-service area, during the next periodic reporting period the application is enabled and the phone is in a service area.

5. The method of any one of claims 1 -4 further comprising the steps of:

capturing any SMS and MMS messages created by and transmitted from the at least one phone;

transmitting the captured SMS and MMS messages to the server; and,

including the transmitted, captured SMS and MMS messages in the periodic report.

6. The method of any one of claims 1 -4 further comprising the steps of:

capturing any pictures taken by, or downloaded and stored to, the at least one phone; transmitting the captured pictures to the server; and,

including the transmitted, captured pictures in the periodic report.

7. The method of any one of claims 1 -4 further comprising the steps of:

capturing any SMS and MMS messages received by the at least one phone;

transmitting the captured SMS and MMS messages received by the at least one phone to the server; and,

including the transmitted, captured received SMS and MMS messages received by the at least one phone in the periodic report.

8. The method of any one of claims 1 -4 further comprising the steps of:

capturing any email messages and attachments transmitted from, or received by, an email account linked to the at least one phone;

transmitting the captured email messages and attachments; and,

including the transmitted, captured email messages and attachments in the periodic report.

9. The method of any one of claims 2-4 further comprising the steps of:

capturing any events created or taken by the at least one phone;

10. The method of claims 1 or 9 further comprising the step of configuring at least one parameter to set the period in which events created or taken by the at least one phone are captured by the application and transmitted to the server.

1 1. The method of claim 10 further comprising the step of capturing events created or taken by the at least one phone in real time.

12. The method of claim 10 further comprising the step of transmitting the captured events created or taken by the at least one phone every minute.

13. The method of claim 10 further comprising the step of transmitting the captured events created or taken by the at least one phone every thirty minutes.

14. The method of claim 10 further comprising the step of transmitting the captured events created or taken by the at least one phone every hour.

15. The method of any one of claims 1 , 2, or 4 further comprising the step of providing a periodic heart beat signal from the application to the server indicating that the application is active and in communication with the server.

16. The method of claim 15 further comprising the step of configuring at least one parameter to set the period which the heart beat signal must be provided by the application to the server.

17. The method of claim 16 further comprising the step of providing a report from the server to the at least one verified email account indicating the non-receipt of any periodic heart beat signal from the application.

18. The method of claim 17 further comprising the step of reporting the non-receipt of any periodic heart beat signal in the period report.

19. The method of claim 15 further comprising the step of requiring the periodic heart beat signal only when no new events are detected by the application.

20. The method of any one of claims 1 -4 further comprising the step of assigning the access code by the user selecting and inputting the access code when creating the account with the server.

21 . The method of claim 20 further comprising the step of assigning at least one additional access code by the user selecting and inputting the at least one additional access code when creating the account for the server, each additional access code being assigned to an additional phone monitored by the user creating the account.

22. The method of any one of claims 1 -4 further comprising the step of assigning the access code by the server generating a random access code and providing it to the at least one user when the at least one user creates the account.

23. The method of any one of claims 1 , 3, or 4 further comprising the step of restarting the application automatically if the application is disabled on the at least one phone.

24. The method of claim 23 further comprising the step of requiring reactivation using the access code if the application is disabled because it has been uninstalled.

25. The method of claim 23 further comprising the step of transmitting any events created or taken by the at least one phone while the application is disabled or out of communication once the application is restarted and in communication with the server.

26. The method of any one of claims 1 -3 further comprising the step of copying and storing all captured events in a separate file on the at least one phone, the separate file only being accessible to the application.

27. The method of claim 26 further comprising the step of transmitting any events stored on the phone in the separate file but not previously transmitted to the server.

28. The method of claim 27 further comprising the step of transmitting any events stored on the phone but not previously transmitted to the server because the phone was turned off.

29. The method of claim 27 further comprising the step of transmitting any events stored on the phone but not previously transmitted to the server because the phone was in a non- service area.

30. The method of claim 26 further comprising the step of deleting any events stored in the separate file only accessible to the application once the events are transmitted to the server from the separate file.

31. The method of any one of claims 1 -4 further comprising the step of buffering any events transmitted from the at least one phone to the server.

32. The method of claims 1 or 9 further comprising the step of formatting any events transmitted from the at least one phone to the server for providing the periodic report to the at least one verified email address.

33. The method of claim 32 further comprising the step of creating a thumbnail image of any picture events transmitted by the at least one phone to the server.

34. The method of claim 33 further comprising the step of storing a full sized image of any picture events transmitted by the at least on phone to the server, on the server for review by the user monitoring the at least one phone.

35. The method of claim 33 further comprising the step of providing a thumbnail of any picture events transmitted by the at least one phone to the server, in the periodic report.

36. The method of claim 32 further comprising the step of providing a text component of any events transmitted from the phone in the periodic report.

37. The method of claim 36 further comprising the step of providing the text of any SMS or MMS messages transmitted from, or received by, the at least one phone in the periodic report.

38. The method of claim 36 further comprising the step of providing the text of any email messages transmitted from, or received by, the at least one phone in the periodic report.

39. The method of claim 32 further comprising the step of providing the phone number or email address of each recipient of each event transmitted from the at least one phone, in the periodic report.

40. The method of claim 32 further comprising the step of providing the phone number or email address of each provider of each event transmitted to the at least one phone, in the periodic report.

41. The method of claim 32 further comprising the step of providing the date and time each event was created or taken by the phone.

42. The method of claims 1 or 9 further comprising the step of saving the each event included in the periodic report on the server for a period of time for the user creating the account to log onto the server and review the event.

43. The method of claim 42 further comprising the step of downloading any events provided in the report and saving the events locally on a computer or other memory device owned by the at least one user.

44. The method of claim 42 further comprising the step of deleting each event previously included in the periodic report, periodically.

45. The method of claim 44 further comprising the step of deleting each event seven days after it has been included in the periodic report.

46. The method of claims 1 or 9 further comprising the step of providing a link the periodic report for the user to access their account on the server to further view or save any events provided in the periodic report.

47. The method of claims 1 or 9 further comprising the step of configuring a parameter setting the events to be captured by the application and transmitted to the server for inclusion in the periodic report.

48. The method of claim 47 further comprising the step of capturing and transmitting events related to one or more from the group consisting of: SMS and MMS messages transmitted from the at least one phone; SMS and MMS messages received by the at least one phone; email messages and attachments transmitted from the at least one phone; email messages and attachments received by the at least one phone; pictures taken by the at least one phone; and, pictures downloaded to the at least one phone.

49. The method of claim 32 further comprising the step of configuring a parameter to include a count of the number of events transmitted from the at least one phone to one or more specifically identified phone numbers or email address set by the user monitoring the account.

50. The method of claim 32 further comprising the step of configuring a parameter to identify the events transmitted from the at least one to the one or more specifically identified phone numbers.

5 1 . The method of claim 47 further comprising the step of configuring a parameter to include a count of the number of events transmitted from the at least one phone including a word or words specifically identified by the user monitoring the account.

52. The method of claim 51 further comprising the step of configuring a parameter to identify the events transmitted from the at least one phone containing any of the specifically identified word or words.

53. The method of claims 1 or 9 further comprising the step of configuring at least one parameter related to the report provided by the server to the at least one verified email address.

54. The method of claim 53 further comprising the step of configuring at least one parameter setting the period the report is provided by the server to the at least one verified email address.

55. The method of claim 54 further comprising the step of configuring at least one parameter so the periodic report is provided from the server to the verified email address every six hours.

56. The method of claim 54 further comprising the step of configuring at least one parameter so the periodic report is provided from the server to the verified email address every twelve hours.

57. The method of claim 54 further comprising the step of configuring at least one parameter so the periodic report is provided from the server to the verified email address every twenty-four hours.

58. The method of any one of claims 1 -4 further comprising the step of verifying at least one cellular phone number for the at least one user creating the account with the server.

59. The method of claim 57 further comprising the step of providing a periodic report from the server to the at least one verified phone number, detailing any events created or taken by the at least one phone.

60. The method of claim 58 further comprising the step of providing events transmitted to at least one specific phone number set by the at least one user monitoring the at least one account when configuring account parameters.

61. The method of claim 58 further comprising the step of providing events transmitted to the at least one specific phone number in real time.

62. The method of claim 58 further comprising the step of providing events created or taken by the at least one phone containing a picture to the verified phone number.

63. The method of claims 1 or 9 further comprising the step of logging into the server to view the periodic report.

64. The method of claim 2 further comprising the step of requiring the access code to be reentered to restart the application if the application is removed or deleted from the at least one phone.

65. The method of claim 2 further comprising the step of restarting the application automatically if the application is disabled for a period of thirty minutes.

66. The method of claim 3 further comprising the step of disabling the heart beat monitoring of the at least one phone when creating the account.

67. A system for monitoring events created or taken by a cellular phone, the system comprising:

a server for:

registering and storing user account information and setting the user parameters; receiving transmitted events created or taken by on one or more phones monitored by the user;

generating a periodic report for all events created or taken by the one or more phones monitored by the user; and,

emailing the periodic report to the user;

a website linked to the server allowing users to:

register with the server;

review the events received by the server;

re-con figure stored user information and user parameters; and,

download and save any events received by the server;

a software application for downloading onto the one or more phones, the software application being capable of capturing all events created or taken by the one or more phones and periodically transmitting the same to the server.

68. A method for monitoring cell phones including any and all embodiments discussed herein.

69. A system for monitoring cell phones including any and all embodiments discussed herein.