Browse Prior Art Database

Mobile Device Safety Software Application Disclosure Number: IPCOM000152466D
Original Publication Date: 2007-May-04
Included in the Prior Art Database: 2007-May-04
Document File: 5 page(s) / 359K

Publishing Venue


Related People

Vishal B Arora: INVENTOR


A software application that would allow parents to control and monitor a child’s mobile device is described herein. This software application enables parents to control and monitor who their children talk to and who can contact them via voice call or text message. There are three important elements for using and implementing this mobile software application: an architecture, a client, and a web portal. The architecture is based on a mobile device connecting to the Internet, with a database/server of the child’s safety profile. The client controls all the communications on the mobile device. And finally, the web portal will allow parents to login and manage their account where all the children’s mobile settings are stored.

This text was extracted from a Microsoft Word document.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 37% of the total text.

Mobile Device Safety Software Application

            The mobile telephone has grown in popularity among children, but its widespread use also raises safety concerns for parents.  Parents have an interest in protecting their children from mature content and unsolicited contact from strangers.  Currently, there are software applications for filtering the content of websites, but there is no content filtering nor parental control software for mobile devices. 

            This software application enables the parents to control and monitor who their children talk to, and who can contact them on their mobile device.  Also, it can be configured to control a child’s access to content over the web, playing rated games, and listening to rated music.  There are  three important elements for using and implementing this mobile-device software application.  They comprise an architecture, a client and a web portal.  Figure 1 illustrates a block diagram of the architecture, according to at least one of the implementations of the application.

            In order to use the application, the parents (or user who would want to control the content of a mobile device) would need to download the application on their child’s web-enabled mobile phone, Smartphone or Personal Data Assistant (PDA).  Once the application is downloaded, parents can configure the settings either using the password protected client or via the web portal.  All the application’s settings may be stored within the client as well as within a remote database/server.

Figure 1:  Mobile-device Safety Application Architecture

            The client controls all the communications on the mobile device.  In one implementation, the client can be installed on the mobile device from the web or from a CD, and it can be installed on several devices.  The installation will create an access point on the mobile device for management User Interface (UI), which a parent can use.  The installation on the child’s mobile device would also create the access point for the management UI, but it can only be accessed with a password set by the parent.  The management UI on the parent’s mobile device enables the parent to manage the multiple mobile devices of their children.  There could be other access points for the management of a mobile devices, such as a web portal.  This web portal could even be formatted such that it can be accessed and navigated via a mobile phone.

            The client comprises two modules, namely the driver, and the management UI.  Also, the client can operate in multiple modes, parent and child.  The modules can be enabled separately depending on which mode the mobile device is in.  For example, in parent mode, only the management UI would be operating, and in child mode...