PROFILING REMOTE MANAGEMENT

FIELD OF INVENTION

The present invention relates to a profiling remote management system and a method of profiling and remotely managing at least one client and a server for at least one platform. BACKGROUND OF INVENTION

During post production, some, if not most of software inside client computer systems need to be updated due to bug fixes, and existing software features enhancements. In addition, new software that provides new capabilities need to be installed into client systems as well. One way to do this is to manually copy and install updated files using USB (Universal Serial Bus) drive onto the device. This approach, however, requires manual effort. Hence, this approach is not desirable in the event of mass distribution and deployment of client systems.

U.S. 6199204 describes a method for automatically updating computer programs via an updater agent which is associated with a computer program to access relevant network locations and automatically downloads and installs available updates. However, traces of old version of the software may cause some conflicts within the system. This document does not disclose any method to solve this problem. U.S. 6874143 describes methods and systems for network based or Internet based software delivery, wherein software extensions are deliverable over the Internet. However, this document does not address the problem of interrupted downloading where the downloading and installation is stopped because of the network interruption or user initiated.

Therefore, there is a need for a method or system to automatically and selectively update software as required while taking into consideration that downloading and installation may be interrupted during the updating process.

SUMMARY OF INVENTION

Accordingly there is provided a profiling remote management system which includes at least one client and a server for at least one platform, the system further includes a plurality of executables with at least one user profile in the at least one client and at least one repository within the server, wherein the at least one client is networked to the server .

There is also provided a method of profiling and remotely managing at least one client and a server for at least one platform, the method includes the steps of registering a user by a plurality of executables, generating at least one server address based on demographics, establishing network connections to the server and executing the at least one platform.

There is also provided a method of profiling and remotely managing at least one client and a server for at least one platform, the method includes the steps of displaying existing platform, establishing network connection to the server, verifying availability of a new version of the existing platform, uninstalling and deleting the existing platform and executing the new version of the existing platform. The present invention consists of several novel features and a combination of parts hereinafter fully described and illustrated in the accompanying description and drawings, it being understood that various changes in the details may be made without departing from the scope of the invention or sacrificing any of the advantages of the present invention.

BRIEF DESCRIPTION OF THE DRAWINGS

The drawings constitute part of this specification and include an exemplary or preferred embodiment of the invention, which may be embodied in various forms. It should be understood, however, the disclosed preferred embodiments are merely exemplary of the invention. Therefore, the figures (not to scale) disclosed herein are not to be interpreted as limiting, but merely as the basis for the claims and for teaching one skilled in the art of the invention.

Figure 1 shows a block diagram of a preferred embodiment of a profiling remote management system;

Figure 2 shows a flowchart describing steps to download and install software application on client from server if a software has never been installed in accordance to preferred embodiment of the invention; Figure 3 shows a flow diagram describing the steps to download and install software applications on client from server if an older version of the software has been installed in accordance to preferred embodiment of the invention;

Figure 4 shows a flow diagram illustrating steps to generate list of software executables available for download and installation by client based on certain combined values of User Profile characteristics or demographics in accordance to preferred embodiment of the invention;

Figure 5 shows a flow diagram indicating steps to uninstall and delete software residing on client if the software is not part of demographics that the user belongs to in accordance to preferred embodiment of the invention;

Figure 6 depicts a sequence of steps to resume download and installation if previously cancelled during subsequent booting up of the client in accordance to preferred embodiment of the invention;

Figure 7 depicts a sequence of steps to generate server address based on demographics that match with current user values of profile characteristics in accordance to preferred embodiment of the invention; and

Figure 8 shows a flow diagram to establish network connection in accordance to preferred embodiment of the invention. PREFERRED EMBODIMENTS

The present invention relates to a profiling remote management system and a method of profiling and remotely managing at least one client and a server for at least one platform. Hereinafter, this specification will describe the present invention according to the preferred embodiments of the present invention. However, it is to be understood that limiting the description to the preferred embodiments of the invention is merely to facilitate discussion of the present invention and it is envisioned that those skilled in the art may devise various modifications and equivalents without departing from the scope of the appended claims.

The following detailed description of the preferred embodiments will now be described in accordance with the attached drawings, either individually or in combination. Figure 1 shows an embodiment of a profiling remote management system (100) which includes at least one client (102) and a server (104) for at least one platform. The system (100) further includes a plurality of executables (106, 107) with at least one user profile (110) in the at least one client (102) and at least one repository (1 11 , 1 12,1 13) within the server (104), wherein the at least one client (102) is networked to the server (104).

Examples of the plurality of executables (106, 107) are platform executables (107) and software executables (106). In this embodiment, the at least one repository (1 11 , 1 12, 113) is selected from software executables repository (1 1 1 ), software information repository (1 12) and profile information repository (113). The server (104) can be defined as a combination of hardware and software hosting a plurality of repositories (111 , 112, 113) containing software executables (106, 107) and information associated with the hardware and software. Additionally, the server (104) hosts a profile information repository (113) that keeps profile information.

Software is an example of a platform used in the system (100). The software executables repository (111) is a directory made up of software which is installable and executable on at least one client (102) to perform specific functions. The software information repository (112) stores details of software available as part of the software executables repository (11 ). Details of software include name, version and type of software. A list of software based on certain demographics values of group and religion is also included. This is to ensure that the at least one client (102) registered to a user profile (110) characteristics which is connected to the server (104) would be able to access a matched list wherein a customized group of software applications are to be downloaded and installed accordingly. A generic list is also made available by the at least one client (102) when there is no user profile registered (110). Software suggested as part of the generic list is useful for any type of profile. This is to avoid applications targeted to specific demographics to be installed for other devices that are meant for generic use. The at least one client (102) with a registered user profile (110) are able to access and view and install applications that are unavailable on demographic specific list.

The profile information repository (113) stores all users of the at least one client (102). Furthermore, the profile information repository (113) takes in all software information inside the software information repository (112) and filters said information based on demographics. The filtered list is stored in software information repository (112). The at least one client (102) and the server (104) are connected by networking means such as Internet. Downloaded and installed software executables are available for user from the at least one client. Server information (108) provides details on the server (104) that is connectable to and updated by the at least one client (102).

A method of profiling and remotely managing at least one client (102) and a server (104) for at least one platform is described as seen in Figure 2. The method includes the steps of registering a user by a plurality of executables (106,107) such as platform executables (107) and software executables (106), generating at least one server address based on demographics, establishing network connections to the server (104) and executing the at least one platform.

The method of executing the at least one platform further includes the steps of downloading, installing and loading the platform.

A user profile (110) is registered and sent to the server (104) to be stored. The user profile is used to identify the at least one client (102). Next, saved states (109) are stored on the at least one client (102). The saved states (109) information is still available after the at least one client (102) is shut down. In this embodiment, the saved states (109) include a list of software to be deleted if the list is not part of the demographics, a list of older version of software which is no longer used and has been uninstalled and to be deleted and previous points of download and paused installation when an operation is aborted. A second embodiment of the method as seen in Figure 3 includes method includes the steps of displaying existing platform, establishing network connection to the server (104), verifying availability of a new version of the existing platform, uninstalling and deleting the existing platform and executing the new version of the existing platform. Executing the at least one new version of the existing platform further includes the steps of downloading, installing and loading the platform. The existing platform is uninstalled and physically deleted from the at least one client (102) file system when booted up subsequently.

The method as described above further includes building and deploying a plurality of executables, updating details of the plurality of executables, retrieving demographic information, getting a list of software based on demographics, positioning the constructed list in a repository and publishing said list as seen in Figure 4. The method creates a list of software which is available for update and installation. Groupings are defined based on group and religion but it is to be understood that this definition may be extended to include other defining characteristics such as race. The list are positioned in the software information repository (1 12) to be connected by the at least one client (102). For example, a group with JENii value and a religion with Islam value generates a customized list of software named as JENii-lslam-site. The suggested software is located in the software executables repository (11 1 ), wherein details of the software is located in the software information repository (1 2).

As seen in Figure 5, a method of profiling and remotely managing at least one client (102) and a server (104) for at least one platform is described. The method includes the steps of uninstalling and deleting software residing on at least one client (102) if the software is not part of the demographics that a user belongs to. Therefore, if installed software has been removed from http://<server>/JENii-lslam-site, the software will be uninstalled and deleted from the system (100). Figure 6 depicts a flow of sequence to resume downloading and installation process after being previously cancelled. A current state of download and installation is saved. The saved states (109) are stored, wherein subsequent restarting of the system (100) would resume download and installation from point of previously saved states (109). Upon execution of the download and installation, previously saved states (109) are deleted. There are possible factors that cause interruption of downloading and installation such as loss of network connection between the at least one client (102) and the server (104) because of physical network cable being disconnected or server (104) is unreachable. The interruption may also be caused by explicit cancellation of current download and installation operation by the user.

Figure 7 shows generation of server address based on demographics that match current user values with that of the user profile (110). A plurality of user profile characteristics is retrieved. Corresponding current user profile (1 10) values are used to construct a server (104) address. Finally the server address is saved in the system (100). In this preferred embodiment, group and religion are obtained from profile information repository (1 13). Corresponding values of current users for these characteristics are obtained such as JENii and Islam respectively. During construction of software information repository (112) server address, the server (104) address and values of profile characteristics are combined which yielded http://<server>/JENii- Islam-site in this preferred embodiment. This address corresponds to a file inside software information repository (1 12) at the server (104), wherein content is a list of software that the at least one client (102) can download and install. The server address is stored in the server information (108) at the at least one client (102)

Furthermore, as seen in Figure 8, network connection is established by loading software information repository (112) server address based on demographics, and storing said data in server information (108). Finally the software information repository (1 12) content is accessed and the list is retrieved. The list is traversed, downloaded and installed into at least one client (102) through a network.

Furthermore, types of software that can be installed on client systems can be customized. Each client is registered to a user. A user has a user profile associated with him or her. Customization then depends on user profile characteristics. For instance, if the user is a Muslim, then software applications which are made available for him to download and install must be those related to Islam. An example of this is software which enables him or her to access prayer times at various locations. Additionally, more characteristics can be added. Consequently, defining this customization must be done on a remote, centralized server which is accessible by client located dispersedly throughout different geographic locations.

This invention is adapted for managing software to be installed on clients which can be either a mobile device, mobile internet device or personal computer based on demographics. The disclosed invention is suitable, but not restricted to, demographics as described as well as other types of characteristics such as race. The software is made available at a remote central server.