CN101996074B - Method and device for managing software by using software component management object - Google Patents

Abstract

The present invention relates to a method and device for managing software using software component management objects. The method includes: acquiring software information on user equipment; information; according to the information of the software operating in the non-software component management object mode, create and configure corresponding nodes for the software operating in the non-software component management object mode under the corresponding node of the software component management object; Report to the software component management object server. By obtaining the information of the software operating in a non-SCOMO mode, and according to the obtained information, create corresponding nodes under SCOMO for the software operating in a non-SCOMO mode, and report the corresponding node information to the SCOMO server, which solves the problem that the existing SCOMO mode cannot Issues with managing software installed by users on end devices through non-SCOMO means.

Description

Method and device for managing object management software using software components

technical field

The invention relates to the technical field of wireless communication, in particular to a method and device for managing object management software using software components. the

Background technique

The Open Mobile Alliance Device Management (OMA DM) system provided by the Open Mobile Alliance Device Management Specification 1.2 (OMA DM V1.2) is used for third-party management and setting of the environment and configuration information in wireless network terminal devices, and solves the problem of these wireless network terminal devices. For problems encountered during the use of the device, the software and firmware are installed and upgraded through the wireless network (Over The Air, OTA), and other operations are provided, and more humanized and personalized services are provided to improve user experience. Wherein, the third party may be a mobile operator, a service provider, or an information management department of a partner. The wireless network terminal device can be a mobile phone terminal and a functional object in the terminal. the

The OMA DM system is shown in Figure 1. The DM client (DM Client) on the terminal device is used to interpret and execute the management commands issued by the DM server. The management tree stored on the terminal device can be considered as an interface for a DM server (DM Server) to manage the terminal device through the DM protocol. The management tree includes some basic management objects (Management Object, MO), and the DM server achieves the purpose of controlling the terminal management objects through the operation of the management objects. Operation commands include acquisition (Get), replacement (Replace), execution (Exec), copy (Copy), deletion (Delete) and so on. the

The software component management object (SCOMO) in the management object is used to manage the software that needs to be installed or has been installed on the device, as shown in FIG. 2 . The software managed by SCOMO management objects may include programs, executable files, software security certificates, licenses, etc. The software management operations supported by the SCOMO protocol include: download, distribution (delivery), installation (installation), upgrade (update), removal (removal), activation/deactivation (activation/de-activation), and SCOMO management objects It also supports inventory counting of all software in the terminal device.

In the process of realizing the present invention, the inventor found that the existing technology has at least the following defects: the existing SCOMO method cannot manage the software installed on the terminal device by the user through a non-SCOMO method, such as the user downloads or copies the installation file to the terminal If the software is installed on the device, the operator or the management side of these terminal devices cannot query or manage these software in an effective management tree. the

Contents of the invention

Embodiments of the present invention propose a method and device for managing object management software using software components to solve the problem that existing SCOMO methods cannot manage software installed by users on terminal devices through non-SCOMO methods. the

The embodiment of the present invention provides a method of using software component management object management software, including:

Obtain software information on the user's device;

Obtain information about software that operates in a non-software component management object mode on the user equipment according to the software information;

Create and configure corresponding nodes for the software operated in the non-software component management object mode under the corresponding node of the software component management object according to the information of the software operated in the non-software component management object mode;

The information of creating and configuring the corresponding node for the software operating in the non-software component management object mode is reported to the software component management object server. the

The embodiment of the present invention also provides a method of using software component management object management software, including:

Receiving the information of the node reported by the software component management object client; the node is a node created and configured for software in the software component management object on the software component management object client; the software is a non- A software component manages software that operates in the form of objects. the

The embodiment of the present invention also provides a software component management object client device, including:

The first obtaining module is used to obtain the software information on the user equipment;

The second obtaining module is used to obtain the information of the software on the user equipment that operates in a non-software component management object mode according to the software information;

Create a module for creating and configuring corresponding nodes for the software operating in the non-software component management object mode under the corresponding node of the software component management object according to the information of the software operated in the non-software component management object mode;

The reporting module is configured to report the information of creating and configuring corresponding nodes for the software operating in the non-software component management object mode to the software component management object server. the

The embodiment of the present invention also provides a software component management object server, including:

The receiving module is used to receive the information of the node reported by the software component management object client; the node is a node created and configured for the software in the software component management object on the software component management object client; the software is Software that operates on a user device as a non-software component management object. the

The above-mentioned embodiment solves the existing problem by acquiring the information of software operating in a non-SCOMO mode, and creating corresponding nodes under SCOMO for the software operating in a non-SCOMO mode according to the acquired information, and reporting the corresponding node information to the SCOMO server. The SCOMO method cannot manage the software installed on the terminal device by the user through a non-SCOMO method. the

The technical solutions of the present invention will be described in further detail below with reference to the accompanying drawings and embodiments. the

Description of drawings

Fig. 1 is the overall structural representation of the OMA DM system in the prior art;

Fig. 2 is the schematic diagram of SCOMO management tree in the prior art;

Fig. 3 is a flow chart of a method for using software components to manage object management software provided by an embodiment of the present invention;

Fig. 4 is a flowchart of another method for using software components to manage object management software provided by an embodiment of the present invention;

Fig. 5 is the flow chart of unloading management in the method for using software component management object management software provided by the embodiment of the present invention;

Fig. 6 is a flow chart of another method for using software component management object management software provided by the embodiment of the present invention;

7 is a schematic structural diagram of a software component management object client device provided by an embodiment of the present invention;

FIG. 8 is a schematic structural diagram of a software component management object server provided by an embodiment of the present invention. the

Detailed ways

Fig. 3 is a flowchart of a method for managing object management software using software components provided by an embodiment of the present invention. The method includes:

Step 31, acquiring software information on the user equipment. the

This action can be performed by the SCOMO client on the terminal device, that is, the user device. SCOMO client can obtain software installation information, download information, distribution information, etc. from user equipment. The SCOMO client monitors the software to obtain software installation, download or distribution information, or collects and obtains software installation, download or distribution information after receiving instructions sent by the SCOMO server. the

Step 32. Obtain information about software operating in a non-SCOMO mode on the user equipment according to the software information. the

This action can be performed by the SCOMO client on the terminal device, that is, the user device. The SCOMO client can judge whether there is software to be installed, downloaded or distributed in a non-SCOMO manner according to the information obtained in step 31. The software information is any one or a combination of the following information: software name, software version, and software description information. the

Step 33: Create and configure a corresponding node for the software operating in a non-SCOMO mode under the corresponding node of SCOMO according to the information of the software operating in a non-SCOMO mode. the

This action can be performed by the SCOMO client on the terminal device, that is, the user device. The SCOMO client creates and configures corresponding nodes for the software under the corresponding nodes of SCOMO. When the software is installed in a non-SCOMO mode, create and configure corresponding nodes for the software under the deployment (Deployed) node of SCOMO. When the software is downloaded in a non-SCOMO manner, a corresponding node is created and configured for the software under the download (Download) node of SCOMO. When the software is distributed in a non-SCOMO manner, create and configure a corresponding node for the software under the Delivered node of SCOMO. the

When creating and configuring corresponding nodes for software installed in a non-SCOMO manner, specifically include: creating a package identification reference node for the software under the deployment node of SCOMO; configuring the package identification reference node for identifying the software Take the value of a non-SCOMO installation. When used to identify that the software is installed in non-SCOMO, a new node can also be created and configured under the deployment node of SCOMO; the new node is a node used to identify that the software is installed in non-SCOMO. the

When creating and configuring corresponding nodes for software downloaded in a non-SCOMO manner, specifically include: creating a package identification node for the software under the deployment node of SCOMO; configuring the package identification node for identifying the software with non-SCOMO The value downloaded by SCOMO. When it is used to identify that the software is downloaded by non-SCOMO, a new node can also be created and configured under the download node of SCOMO; the new node is a node for identifying that the software is downloaded by non-SCOMO. the

When creating and configuring corresponding nodes for software distributed in a non-SCOMO manner, specifically include: creating a package identification node for the software under the distribution node of SCOMO; The value distributed by SCOMO. When used to identify that the software is distributed by non-SCOMO, a new node can also be created and configured under the distribution node of SCOMO; the new node is a node used to identify that the software is distributed by non-SCOMO. the

Step 34, reporting the information of the node to the SCOMO server. the

This action can be performed by the SCOMO client on the terminal device, that is, the user device. The SCOMO client may send at least one or a combination of the location information of the management subtree of the software in the SCOMO, the current status information of the software, or the information used to identify the node where the software operates in a non-SCOMO manner to the SCOMO server. This action may also perform the operation of reporting the information of the node according to the query instruction sent by the SCOMO server. the

In this embodiment, the SCOMO client monitors the software operated in a non-SCOMO manner, and creates and configures corresponding nodes for the software in SCOMO. SCOMO realizes the management of the software operated in a non-SCOMO manner, so that operators or other management On the basis of SCOMO, which has been widely recognized, it can realize the query and management of all software on user equipment. the

When the software operated in a non-SCOMO mode in the above embodiment is uninstalled, the method for using software component management object management software provided by the embodiment of the present invention may also include:

Obtain the uninstallation information of the software operating in the non-SCOMO mode. This action can be performed by the SCOMO client on the terminal device, that is, the user device. The SCOMO client monitors the software to obtain the software uninstallation information, or collects and obtains the software uninstallation information after receiving the instruction sent by the SCOMO server. the

In the case that the software is uninstalled in a non-SCOMO manner, the node created for the software in the SCOMO is deleted according to the uninstallation information. This action can be performed by the SCOMO client on the terminal device, that is, the user device. the

Reporting to the SCOMO server that the software is uninstalled. This action can be performed by the SCOMO client on the terminal device, that is, the user device. the

The method for managing object management software using software components provided by the embodiment of the present invention may further include: receiving a deletion instruction sent by the SCOMO server; this action may be executed by a terminal device, that is, a SCOMO client on a user device. the

The node created for the software operating in the non-SCOMO mode is deleted according to the deletion instruction. This action can be performed by the SCOMO client on the terminal device, that is, the user device. The SCOMO client deletes the node created for the software operating in a non-SCOMO mode after receiving the delete command sent by the SCOMO server. the

Assuming that the SCOMO client deletes the node information of a certain software according to the deletion instruction of the SCOMO server, when the software has been installed, the method for managing object management software using software components provided by this embodiment may also include uninstalling the software. When the software is not installed, the method for managing object management software using software components provided in this embodiment may further include deleting the physical file of the software operating in a non-SCOMO mode on the user device. the

Corresponding to the embodiment shown in Figure 3, another method for using software component management object management software provided by the embodiment of the present invention may include:

Receive the node information reported by the SCOMO client; the node is the node created and configured for software in SCOMO on the SCOMO client; the software is the software operated in a non-SCOMO mode on the user equipment. the

This action can be performed by the SCOMO server on the DM server. After the SCOMO client creates and configures nodes for software that operates in a non-SCOMO mode, it reports the corresponding information to the SCOMO server. For details, see step 34 above. After the SCOMO server receives the above information, it can realize the query and management of all software on the user equipment. the

The method for using the software component management object management software provided by the embodiment of the present invention may also include:

Send a query instruction including an identifier for identifying the software operating in a non-SCOMO manner, such as "UserPrivate", and the query instruction is used to query node information of the software operating in a non-SCOMO manner according to the identifier. This action can be performed by the SCOMO server on the DM server. The SCOMO server can obtain all the information of the software on the user equipment that operates in a non-SCOMO mode by sending an inquiry command. the

The method for using the software component management object management software provided by the embodiment of the present invention may also include:

Sending a deletion instruction for deleting software that operates in a non-software component management object mode on the user equipment. This action can be performed by the SCOMO server on the DM server. The SCOMO server can manage the software that operates in a non-SCOMO mode on the user device by sending a delete command. the

FIG. 4 is a flow chart of another method for managing object management software using software components provided by an embodiment of the present invention. The method includes:

Step 41, acquiring software installation information on the user equipment. the

This action can be performed by a SCOMO client. The SCOMO client monitors the progress and information of software installation on the user's device. The SCOMO client can monitor the software installation information on the user's device in real time; it can also monitor and collect the software installation information on the user's device during this period of time in a regular and timing manner; it can also start collecting users after receiving instructions from the SCOMO server Software installation information on the device. the

The SCOMO client monitors and collects the software installation information on the user equipment, which can be realized by calling the calling function provided by the user equipment operating system. For example, the "msi" function can be called on the mobile phone of the Windows Mobile system to obtain the list of installed software on the mobile phone; It can be realized by analyzing the log files of the software installation and uninstallation of the operating system of the user device. For example, on a mobile phone with a Symbian or Linux system, the software installation can be obtained by reading and analyzing the system file "installed-software.log" or "Appinist.ini". information. the

Step 42. Obtain information about software installed in a non-SCOMO manner on the user equipment according to the software installation information. the

This action can be performed by a SCOMO client. The SCOMO client terminal judges whether the software installed on the user equipment is installed in SCOMO mode or non-SCOMO mode. the

After the SCOMO client gets the information about the software installed on the device, it judges whether the software is executed by executing the SCOMO command "Inventory/Delivered/<X>/Operations/Install" 

or "Inventory/Delivered/<X>/Operations/InstallInactive"

Or "Download/<X>/Operations/DownloadInstall"

Or "Download/<X>/Operations/DownloadInstallInactive" to install, if not, it is determined that the software is installed in a non-SCOMO way. the

For software installed in SCOMO mode, the SCOMO client creates and configures corresponding nodes under the deployed (Deployed) node according to the existing SCOMO protocol. the

Step 43: Create and configure corresponding nodes for the software in SCOMO according to the information of the software. the

This action can be performed by a SCOMO client. For software installed in a non-SCOMO way, the SCOMO client will know the name, version, installation path and other information of the installed software through running the monitoring program, create a node for the software under the "Deployed" node, and configure the software information to the corresponding node to go. the

After the SCOMO client obtains the information of the software installed in a non-SCOMO way, create corresponding nodes for the software under "Inventory/Deployed/": "<X>", "ID", "PkgIDRef", "Name" , "Version", "Status" and "State". the

Among them, the name of the "<X>" node can be custom-generated by the SCOMO client. The "ID" node is generated by the SCOMO client, the value of this node cannot be repeated, and it is the unique identifier of the software on SCOMO. The "PkgIDRef" node value is a number generated by the SP number and software name according to a certain algorithm in the SCOMO protocol. In this embodiment, the value of this node is set to a special value that distinguishes the numbers generated by the above-mentioned algorithm. For example, "UserPrivate" is used to distinguish software installed in a non-SCOMO mode in SCOMO, and the SCOMO server can query the value of "UserPrivate". PkgIDRef" node to obtain information about all non-SCOMO-installed software on SCOMO. The "Name" node value may be the installation name of the software obtained in step 41. The "Version" node value may be the version number of the software obtained in step 41, such as 1.2. The "Status" node value can be set to 10, indicating that the software has not yet started to be deleted. If the software is currently running, the value of the "State" node is 20; if the software is not currently running, the value of the "State" node is 10. the

If the SCOMO client also obtains the description information of the software from step 41, a "Description" node can also be created here, and the description information can be written into the node value. the

The SCOMO client can also create an executable node "Operations/Remove", so that for software installed in a non-SCOMO way, the SCOMO server can also issue instructions to execute "Operations/Remove" to uninstall. the

The SCOMO server can issue the "Get" command to read the nodes under "Inventory/Deployed" to get all the node information under "Deployed", or just read the "PkgIDRef" node whose value is equal to "UserPrivate" to get non- Node information of software installed in SCOMO mode. the

Step 44: Report the information of the node to the SCOMO server. the

This action can be performed by a SCOMO client. The SCOMO client reports the information of the software installed in non-SCOMO way to the SCOMO server. the

The SCOMO client reports to the SCOMO server that the status of the software is "installation", and reports the location information of the software on the management tree such as URL: "Inventory/Deployed/<X>", and reports the value of "PkgIDRef" to the SCOMO server, Let the server know that the installed software is non-SCOMO installed. the

Correspondingly, the method for using software component management object management software provided by the embodiment of the present invention may include:

Receive the information of the node reported by the SCOMO client; the node is the node created and configured for the software in SCOMO on the SCOMO client; the software is the software installed on the user equipment in a non-SCOMO manner. This action can be performed by the SCOMO server. For the received node information, refer to the description of step 44 above. the

The method for managing object management software using software components provided by the embodiments of the present invention may further include: sending a query instruction for querying node information of the software installed in a non-SCOMO manner. This action can be performed by the SCOMO server. The SCOMO server can query the information of all software installed in the non-SCOMO mode on the user equipment through the query command. the

The method for managing object management software using software components provided by the embodiments of the present invention may further include: sending a deletion instruction for deleting the software installed in the user equipment in a non-SCOMO manner. This action can be performed by the SCOMO server. The SCOMO server can delete all software installed in a non-SCOMO way on the user device through the delete command. the

In this embodiment, the SCOMO client monitors the software installed in a non-SCOMO way, and creates and configures corresponding nodes for the software in SCOMO. SCOMO realizes the management of the software installed in a non-SCOMO way, so that operators or other management On the basis of the widely recognized SCOMO, Fang can realize the query management of all installed software on the user equipment. the

The method for using software components to manage object management software provided in the embodiment of the present invention may also include uninstalling management of the software. As shown in Figure 5, the details may include:

Step 51, acquiring uninstallation information of the software. the

This action can be performed by a SCOMO client. The SCOMO client monitors whether any software on the user equipment is uninstalled through the monitoring program. In the case that software is uninstalled, the SCOMO client executes step 52. the

The SCOMO client can monitor the software uninstallation on the user equipment in real time; it can also monitor and collect the software uninstallation on the user equipment during this period of time in a regular and timing manner; it can also start collecting user equipment after receiving instructions from the SCOMO server software uninstallation on the the

The SCOMO client monitors and collects software uninstallation on user equipment, which can be realized by calling the calling function provided by the operating system of the user equipment, or by analyzing the log files of software uninstallation in the operating system of the user equipment, such as Symbian or Linux system mobile phones Software uninstallation information can be obtained by reading and analyzing the system file "uninstalled-software.log". the

Step 52. In the case that the software is uninstalled in a non-SCOMO manner, delete the node created for the software in the SCOMO according to the uninstallation information. the

This action can be performed by a SCOMO client. The SCOMO client judges whether the uninstalled software is uninstalled in SCOMO mode. After the SCOMO client obtains the information of the uninstalled software on the user equipment through step 51, it can determine whether the software is uninstalled by executing the SCOMO command "Inventory/Deployed/<X>/Operations/Remove". If yes, it means that the uninstalled software is uninstalled in SCOMO mode, delete the corresponding node under the "Deployed" node according to the existing SCOMO protocol; software name and other information, delete the corresponding node under the "Deployed" node, and go to step 53. the

Step 53: Report to the SCOMO server that the software is uninstalled. the

This action can be performed by a SCOMO client. The SCOMO client reports to the SCOMO server that software has been uninstalled in a non-SCOMO manner. the

The SCOMO client reports to the SCOMO server that the status of the software is "uninstalled", and reports the URL of the software on the management tree: "Inventory/Deployed/<X>", and reports the value of "PkgIDRef" to the SCOMO server to let the server know What is uninstalled is the software installed or uninstalled in a non-SCOMO way. the

Take a mobile phone with Windows Mobile operating system as an example. It is assumed that the mobile phone is installed with a SCOMO client and supports the SCOMO protocol. The SCOMO client uses the "msi" function opened by the WindowsMobile system on the mobile phone to obtain the software installation list on the current mobile phone in real time. When the user downloads the installation file of a mobile game software Fighter1.2 from the Internet to the computer, connects the mobile phone and the computer with a data cable, copies the installation file to the mobile phone, and installs it, the SCOMO client will obtain the new installation software The name Fighter, the version is 1.2, and the installation path is "\Applications\Fighter". the

The SCOMO client checks the record of executing the installation instructions of the SCOMO server. After learning that the newly installed software is installed in a non-SCOMO way, it starts to create a management node for the newly installed software under the "Inventory/Deployed" node of SCOMO, and sends the obtained Configure the software information to the corresponding node:

Create and configure the name of the "<X>" node as "Fighter123", and the name of the "<X>" node can be customized by the SCOMO client;

Create and configure the "ID" node with a value of 000876 to uniquely identify the software throughout SCOMO;

Create and configure the value of the "PkgIDRef" node as "UserPrivate" to indicate that the software is not installed by SCOMO;

Create and configure the value of the "Name" node as "Fighter";

Create and configure the "Version" node with a value of 1.2;

Create and configure a "State" node with a value of 10 to indicate that the software is not currently running;

Create and configure the node value of "Status" to be 10 to indicate that the software has not been uninstalled;

Create an executable node "Operations/Remove". When the SCOMO server sends an instruction to execute the node to the SCOMO client, the SCOMO client searches for the uninstaller in the program installation directory "\Applications\Fighter" and uninstalls the software. After uninstalling, the SCOMO client will delete all nodes starting from <Fighter123>, that is, clear all the information of the software on the management tree. the

After the SCOMO client creates and configures the corresponding nodes, it reports the information of the installed software to the SCOMO server. The reported information includes: the position information of the management subtree of the software on the entire SCOMO "Inventory/Deployed/Fighter123"; the status information of the software "Status=10"; and "PkgIDRef=UserPrivate", informing the SCOMO server that the software is The user installs the software by himself, that is, the software is installed in a non-SCOMO way. the

Alternatively, the SCOMO server can send a "Get" command to the SCOMO client to obtain all node information under the "Deployed" node to obtain all software installation information on the current device; it can also send a "Get" command with parameters to obtain Information under all <X> nodes whose "PkgIDRef" node value is "UserPrivate" under the "Deployed" node is used to obtain the list of software installed in non-SCOMO mode on the current user device. the

Take a Symbian operating system mobile phone as an example. The phone also has a SCOMO client installed and supports the SCOMO protocol. In this embodiment, the SCOMO client sets a timer to query software newly installed or uninstalled on the device in a non-SCOMO manner every 24 hours, and creates a maintenance node on the SCOMO. Alternatively, the SCOMO client receives an instruction from the SCOMO server after 24 hours to synchronize the SCOMO information with the software information installed on the device. The SCOMO client obtains the latest system file "installed-software.log", compares it with the installed-software.log file backed up 24 hours ago, and analyzes whether there is information about newly installed software within 24 hours. the

Assume that the user sends a book reader software EReader5.5 to the mobile phone via bluetooth and installs it. The SCOMO client inquires and learns, or the SCOMO server learns that the user device has newly installed the software EReader5.5 through comparative analysis, and obtains the name, version, description and installation path of the software from the log file. the

The SCOMO client checks the record of executing the installation command of the SCOMO server, and judges that the software is installed in a non-SCOMO way; the SCOMO client starts to create a management node for the software under the "Inventory/Deployed" node of SCOMO:

Create and configure the name of the "<X>" node as 456EReader, the name of this node can be customized by the SCOMO client;

Create and configure the "ID" node with a value of 000888 to uniquely identify the software throughout SCOMO;

Create and configure the value of the "PkgIDRef" node to be empty to indicate that the software is installed in a non-SCOMO way;

Create and configure the "Name" node as EReader;

Create and configure the "Version" node with a value of 5.5;

Create and configure the value of the "Description" node as "Reader"

Create and configure a "State" node with a value of 10 to indicate that the software is not currently running;

Create and configure the node value of "Status" to be 10 to indicate that the software has not been uninstalled;

Create and configure the executable node "Operations/Active". When the SCOMO server sends an instruction to execute the node to the SCOMO client, the SCOMO server searches for the startup file in the program installation directory "\Applications\EReader" and starts running the software. Update the value of the "State" node to 20, indicating that the software is running;

Create and configure the executable node "Operations/Remove". When the SCOMO server sends an instruction to execute the node to the SCOMO client, the SCOMO server searches for the uninstaller in the program installation directory "\Applications\Fighter" to uninstall the software. After the software is uninstalled, the SCOMO client deletes all nodes starting from <Fighter123>, that is, clears all information of the software on the management tree. the

The SCOMO server can send the "Get" command to the SCOMO client to get all the node information under the "Deployed" node to get all the software installation information on the current device; it can also send the "Get" command with parameters to get the "Deployed" node information. " node under the "PkgIDRef" node value is empty all the information under the <X> node, to obtain the list of software installed on the current device in non-SCOMO mode. the

If the SCOMO client obtains the latest system file "uninstalled-software.log", compare it with the system file "uninstalled-software.log" backed up 24 hours ago, and analyze whether any software has been uninstalled within the 24 hours. When it is detected that EReader has been uninstalled, the SCOMO client checks the record of executing the installation command of the SCOMO server, and judges that the software is uninstalled in a non-SCOMO way, then the SCOMO client deletes all nodes below the <EReader> node. the

FIG. 6 is a flowchart of another method for managing object management software using software components provided by an embodiment of the present invention. This embodiment mainly performs download management on software. As shown in Figure 6, the details may include:

Step 61. Obtain the description file of the software when the software is downloaded. the

This action can be performed by a SCOMO client. The SCOMO client can monitor whether there is an air transmission process on the current device. If it is monitored, it can obtain the name, version and other information of the downloaded file by obtaining the description file of the transmitted file.

Step 62. When the software is downloaded in a non-SCOMO manner, create and configure a corresponding node for the software under the SCOMO download node according to the description file. the

This action can be performed by a SCOMO client. The SCOMO client creates and configures corresponding nodes under the "Download" node according to the information such as the name and version of the downloaded file. the

After the software download is completed, the download management may also include:

Step 63, under the download node of the SCOMO, create and configure a corresponding node for the software. the

This action can be performed by a SCOMO client. The SCOMO client creates a package identification (PkgID) node for the software under the SCOMO distribution node, and configures a value for identifying that the software is downloaded in a non-SCOMO manner for the creation package identification node. After the corresponding nodes are created and configured for the software, the SCOMO client may also report the value of the software creation package identification node to the SCOMO server. the

For software that has been downloaded but not yet installed, or for software that has not been installed on the user's device, the SCOMO client compares the information of the software, such as file name or type, with the existing information under the distribution node of SCOMO, if No, it means that the software is distributed in a non-SCOMO way, and a corresponding node is created and configured for the software under the distribution node of SCOMO. the

Take a mobile phone with an Andriod operating system as an example. Suppose the user uses the mobile phone to receive a short message with a software download URL, and the user clicks on the URL to download the software. The SCOMO client detects that there is an over-the-air download process on the mobile phone, so it obtains the description file of the downloaded software, from which it obtains the download URL, file name, version number, description information, and file type of the software. The SCOMO client monitors and executes the command record of the SCOMO server and judges that the downloaded software is issued by a non-SCOMO server, then starts to create a node for the downloaded software under the "Download" node, and configures the information obtained from the description file Go to the values of "PkgURL", "Name", "Description", and "PkgType" nodes, and set special values such as "UserPrivate" for "PkgID" to identify non-SCOMO downloads. The SCOMO server can query the "Download/<X>/PkgID" node whose value is equal to "UserPrivate" to obtain the software that is currently being downloaded on the mobile phone in a non-SCOMO way. the

After the software is successfully downloaded, the SCOMO client creates and configures node information for the successfully downloaded software under the "Inventory/Delivered" node, and configures the values of the "Name", "Description", and "PkgType" nodes accordingly, as " PkgID" set a special value such as "UserPrivate" or empty to identify the software as a non-SCOMO download, and create a "/Inventory/Delivered/<X>/Operations/Remove" node. The SCOMO server can query the "/Inventory/Delivered/<X>/PkgID" node whose value is equal to "UserPrivate" to obtain the software being downloaded on the mobile phone in a non-SCOMO way. The SCOMO server can also instruct the SCOMO client to delete the software by issuing the command "/Inventory/Delivered/<X>/Operations/Remove". the

The SCOMO client can also obtain software information on the user's device by searching all files on the user's device. After the SCOMO client obtains the software information of a certain software, it judges by comparing the file name and type in the software information with the <name> and <PkgType> of the existing software information under the "Inventory/Delivered" node. Whether the software already exists on the management tree. If it does not exist, create and configure the corresponding node under "Inventory/Delivered/" to manage the software, and the SCOMO server can query or delete these software through the query command or delete command to SCOMO. the

Take a Windows Mobile phone as an example. The mobile phone also has a SCOMO client installed and supports the SCOMO protocol. In this embodiment, the SCOMO client obtains the executable file, registration (license) file or certificate on the mobile phone by searching the mobile phone storage device to find all CAB, INI, LIC, CERT and other files before the software is installed. file specific information. Among them, the registration file or certificate file can also be considered as software information. the

After the SCOMO client finds the files conforming to the format listed above, it judges that these files are not distributed by SCOMO, creates corresponding nodes for these files under the "Inventory/Delivered/" node on SCOMO, and configures the node name, such as "name ", "version", "PkgType", etc., set special values such as "UserPrivate" or empty for "Inventory/Delivered/<X>/PkgID", to identify these files as non-SCOMO distribution. The SCOMO server can query the value of the "Inventory/Delivered/<X>/PkgID" node to obtain all software information distributed by non-SCOMO on the user device; the SCOMO server can send the operation command "Inventory/Delivered/<X>/Operations /Remove" to delete the corresponding file. the

FIG. 7 is a schematic structural diagram of a software component management object client device provided by an embodiment of the present invention. The SCOMO client device includes: a first obtaining module 71 , a second obtaining module 72 , a creating module 73 and a reporting module 74 . The first acquiring module 71 is configured to acquire software information on the user equipment. The second obtaining module 72 is configured to obtain information of software operating in a non-SCOMO mode on the user equipment according to the software information. The creating module 73 is configured to create and configure corresponding nodes for the software operating in the non-SCOMO mode under the corresponding nodes of SCOMO according to the information of the software operating in the non-SCOMO mode. The reporting module 74 is used for reporting the information of the node to the SCOMO server. the

The first acquiring module 71 may be specifically configured to acquire software installation information on the user equipment; the second acquiring module 72 may be specifically configured to acquire software installed on the user equipment in a non-SCOMO manner according to the software installation information. Software information; the creating module 73 may be specifically configured to create and configure corresponding nodes for the software under the SCOMO deployment node according to the software information. the

The first obtaining module 71 can be specifically used to obtain software download information on the user equipment during the process of downloading software; the second obtaining module 72 can be specifically used to obtain software download information on the user equipment according to the software download information. Information about software downloaded in a non-SCOMO manner; the creating module 73 may be specifically configured to create and configure a corresponding node for the software under the SCOMO download node according to the information about the software. the

The first acquisition module 71 can be specifically used to acquire information on existing and uninstalled software on the user equipment; the second acquisition module 72 can be specifically used to acquire information based on all existing and uninstalled software Information about software distributed in a non-SCOMO manner; the creating module 73 may be specifically configured to create and configure a corresponding node for the software under the SCOMO distribution node according to the information about the software. the

The reporting module 74 can be specifically configured to include the position information of the management subtree of the software in the SCOMO, the current state information of the software, and the information used to identify the node that the software operates in a non-SCOMO manner At least one is sent to the SCOMO server. the

The software component management object client device provided by the embodiment of the present invention may further include: a third acquiring module and a node deleting module. The third obtaining module is used to obtain the uninstallation information of the software; the node deletion module is used to delete the node created for the software in the SCOMO according to the uninstallation information when the software is uninstalled in a non-SCOMO manner; The reporting module is specifically configured to report to the SCOMO server that the software is uninstalled. the

The software component management object client device provided by the embodiment of the present invention may further include: an instruction receiving module and a node deleting module. The instruction receiving module is used to receive the query instruction and the deletion instruction sent by the SCOMO server; the node deletion module is used to delete the node created for the software according to the deletion instruction; the reporting module can be specifically used according to the SCOMO server The sent query command reports the information of the node. the

The software component management object client device provided by the embodiment of the present invention may also include at least one of the following modules: an uninstall module and a delete module. The uninstallation module is used to uninstall the software; the deletion module is used to delete the physical files of the software on the user equipment. the

FIG. 8 is a schematic structural diagram of a software component management object server provided by an embodiment of the present invention. The SCOMO server includes: a receiving module 81 . Receiving module 81 is used for receiving the information of the node that uses SCOMO client to report; Described node is the node that is created and configured for software in SCOMO on described SCOMO client; Described software is the non-SCOMO mode operation on user equipment software. the

The software component management object server provided by the embodiment of the present invention may further include: a first sending module. The first sending module is configured to send a query instruction including an identifier used to identify the software operating in a non-SCOMO mode, and the query instruction is used to query node information of the software operating in a non-SCOMO mode according to the identifier. the

The software component management object server provided by the embodiment of the present invention may further include: a second sending module. The second sending module is used to send a deletion instruction, and the deletion instruction is used to delete the software operating in a non-SCOMO mode on the user equipment. the

The above-mentioned method and device embodiment obtains the information of the software operating in a non-SCOMO mode, and according to the obtained information, creates corresponding nodes under SCOMO for the software operating in a non-SCOMO mode, and reports the corresponding node information to the SCOMO server, which solves the problem of The existing SCOMO method cannot manage the software installed on the terminal device by the user through a non-SCOMO method. the

Those of ordinary skill in the art can understand that all or part of the steps for realizing the above-mentioned method embodiments can be completed by hardware related to program instructions, and the aforementioned program can be stored in a computer-readable storage medium. When the program is executed, the It includes the steps of the above method embodiments; and the aforementioned storage medium includes: ROM, RAM, magnetic disk or optical disk and other various media that can store program codes. the

Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: it can still be Modifications are made to the technical solutions described in the foregoing embodiments, or equivalent replacements are made to some of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the various embodiments of the present invention. the

Claims (17)

1. A method for managing object management software using software components, comprising: Acquire software information on the user equipment, where the software information includes any of the following: software installation information, software download information, and information about existing and uninstalled software; Obtaining information about software that operates in a non-software component management object mode on the user equipment according to the software information; Create and configure corresponding nodes for the software operating in the non-software component management object mode under the corresponding node of the software component management object according to the information of the software operated in the non-software component management object mode; Create and configure the corresponding node information for the software operating in the non-software component management object mode and report to the software component management object server; The information of creating and configuring corresponding nodes for the software operating in the non-software component management object mode and reporting to the software component management object server includes: At least one of the position information of the management subtree of the software in the software component management object, the current status information of the software, or the information used to identify the node that the software operates in a non-software component management object mode sent to the software component management object server. 2. The method for using software component management object management software according to claim 1, wherein the information of the software operated in a non-software component management object mode includes at least any of the following: Software name, software version, software description information. 3. The method for using software component management object management software according to claim 1, characterized in that, Obtaining software information on the user device includes: obtaining software installation information on the user device; Obtaining, according to the software information, information about software operated in a non-software component management object manner on the user equipment includes: obtaining information about software installed on the user equipment in a non-software component management object manner according to the software installation information. ; According to the information of the software, create and configure corresponding nodes under the corresponding nodes of the software component management object for the software that operates in the non-software component management object mode, including: according to the information of the software, deploying nodes of the software component management object Create and configure corresponding nodes for the software operating in the manner of the non-software component management object; Create and configure corresponding nodes under the deployment node of the software component management object for the software that operates in the non-software component management object mode, including: Under the deployment node of the software component management object, create a package identification reference node for the software operating in the non-software component management object mode; Configuring the package identification reference node for identifying the software operating in the mode of the non-software component management object as a value installed by the non-software component management object; or, under the deployment node of the software component management object, for the non-software component management object The software operated in object mode creates and configures corresponding nodes, including: Create and configure a new node under the deployment node of the software component management object; the new node is used to identify the software operated in the non-software component management object mode as a node installed with the non-software component management object; Alternatively, obtaining software information on the user device includes: Obtain software download information on the user's device during the process of downloading the software; Obtaining, according to the software information, information about software operated in a non-software component management object manner on the user equipment includes: obtaining information on software downloaded in a non-software component management object manner on the user equipment according to the software download information. ; Create and configure corresponding nodes for the software under the corresponding nodes of the software component management object according to the information of the software, including: according to the information of the software, under the download node of the software component management object, for the non- The software operated in the way of software component management object creates and configures the corresponding nodes; Creating and configuring corresponding nodes for the software operating in the non-software component management object mode includes: Create a package identification node for the software operated in the non-software component management object mode; Configuring the package identification node with a value for identifying that the software operating in the non-software component management object mode is downloaded in the non-software component management object mode; or, creating and configuring the corresponding software for the non-software component management object mode. nodes, including: Create and configure a new node, where the new node is a node for identifying that the software is downloaded as a non-software component management object; Alternatively, obtaining software information on the user device includes: Obtain information about software that is already on the user's device but not installed; Obtaining information about software operated in a non-software component management object manner on the user equipment according to the software information includes: obtaining software distributed in a non-software component management object manner according to information about all existing and uninstalled software Information; Create and configure corresponding nodes for the software under the corresponding nodes of the software component management object according to the information of the software, including: according to the information of the software, under the distribution node of the software component management object, for the non- The software operated in the way of software component management object creates and configures the corresponding nodes; Creating and configuring corresponding nodes for the software operating in the non-software component management object mode includes: Create a package identification node for the software operated in the non-software component management object mode; Configuring the package identification node with a value for identifying that the software operating in the non-software component management object mode is distributed in the non-software component management object mode; or, creating and configuring the corresponding software for the non-software component management object mode nodes, including: Create and configure a new node, where the new node is used to identify the node for distributing the software operating in the non-software component management object mode. 4. The method for using software component management object management software according to claim 1, characterized in that the information of creating and configuring corresponding nodes for the software operated in the non-software component management object mode is reported to the software component management object Servers include: Reporting the information of the node according to the query instruction sent by the software component management object server. 5. The method for using software component management object management software according to any one of claims 1-3, further comprising: Obtaining uninstallation information of the software operated in the non-software component management object mode; In the case that the software is uninstalled in a manner other than a software component management object, delete the node created for the software in the software component management object according to the uninstallation information; Reporting that the software is uninstalled to the software component management object server. 6. The method for using software component management object management software according to any one of claims 1-3, further comprising: receiving a deletion instruction sent by the software component management object server; The node created for the software operating in the non-software component management object mode is deleted according to the deletion instruction. 7. The method for using software component management object management software according to claim 6, further comprising: uninstalling the software that operates in a non-software component management object mode; or, Deleting the physical file on the user equipment of the software operated in the non-software component management object mode. 8. A method for managing object management software using software components, comprising: Receiving the information of the node reported by the software component management object client; the node is a node created and configured for software in the software component management object on the software component management object client; the software is a non- A software component manages software that operates in the form of objects. 9. The method for managing object management software using software components according to claim 8, further comprising: Sending a query instruction including an identifier for identifying the software operating in the non-software component management object mode, the query instruction is used to query node information of the software operating in the non-software component management object mode according to the identifier. 10. The method for managing object management software using software components according to claim 9, further comprising: Sending a deletion instruction for deleting software that operates in a non-software component management object mode on the user equipment. 11. A client device using software component management object management software, characterized in that it comprises: The first acquiring module is configured to acquire software information on the user equipment, where the software information includes any of the following: software installation information, software download information, and information about existing and uninstalled software; A second obtaining module, configured to obtain, according to the software information, information about software that operates in a non-software component management object manner on the user equipment; Create a module for creating and configuring corresponding nodes for the software operating in the non-software component management object mode under the corresponding node of the software component management object according to the information of the software operated in the non-software component management object mode; A reporting module, configured to report information about creating and configuring corresponding nodes for the software operating in the non-software component management object mode to the software component management object server; The reporting module is specifically configured to use the position information of the management subtree of the software in the software component management object, the current state information of the software, and the node used to identify the software that operates in a non-software component management object mode At least one of the information is sent to the software component management object server. 12. The client device using software component management object management software according to claim 11, wherein the first acquisition module is specifically configured to acquire software installation information on the user equipment; The second obtaining module is specifically configured to obtain, according to the software installation information, information about software installed on the user equipment in a non-software component management object manner; The creating module is specifically configured to create and configure corresponding nodes for the software under the deployment node of the software component management object according to the information of the software; Or, the first obtaining module is specifically configured to obtain software download information on the user equipment during the process of downloading software; The second obtaining module is specifically configured to obtain, according to the software download information, information about software downloaded on the user equipment in a non-software component management object manner; The creation module is specifically used to create and configure a corresponding node for the software under the download node of the software component management object according to the information of the software; Or, the first acquiring module is specifically configured to acquire information about software that is already present on the user equipment and has not been installed; The second acquiring module is specifically configured to acquire the information of the software distributed in the form of non-software component management objects according to the information of all the existing and uninstalled software; The creation module is specifically configured to create and configure a corresponding node for the software under the distribution node of the software component management object according to the information of the software. 13. The client device using software component management object management software according to claim 11 or 12, further comprising: A third obtaining module, configured to obtain uninstallation information of the software; A node deletion module, configured to delete the node created for the software in the software component management object according to the uninstallation information when the software is uninstalled in a non-software component management object manner; The reporting module is specifically configured to report that the software is uninstalled to the software component management object server. 14. The client device using software component management object management software according to claim 11 or 12, further comprising: An instruction receiving module, configured to receive query instructions and deletion instructions sent by the software component management object server; a node deletion module, configured to delete the node created for the software according to the deletion instruction; The reporting module is specifically configured to report the information of the node according to the query instruction sent by the software component management object server. 15. The client device using software component management object management software according to claim 14, further comprising at least one of the following modules: an uninstall module for uninstalling the software; A deletion module, configured to delete physical files of the software on the user equipment. 16. A server using software component management object management software, characterized in that it comprises: The receiving module is used to receive the information of the node reported by the software component management object client; the node is a node created and configured for the software in the software component management object on the software component management object client; the software is Software that operates on a user device as a non-software component management object. 17. The server using software component management object management software according to claim 16, further comprising at least any one of the following modules: A first sending module, configured to send a query instruction including an identifier for identifying software operating in a non-software component management object manner, the query instruction is used to query the non-software component management object method according to the identifier node information of the operating software; The second sending module is configured to send a deletion instruction, and the deletion instruction is used to delete software that operates in a non-software component management object mode on the user equipment.