WO2011020402A1

WO2011020402A1 - Method and device for managing software using software component management object

Info

Publication number: WO2011020402A1
Application number: PCT/CN2010/075599
Authority: WO
Inventors: 常新苗; 刘海涛; 宋悦
Original assignee: 华为终端有限公司
Priority date: 2009-08-20
Filing date: 2010-07-30
Publication date: 2011-02-24
Also published as: CN101996074A; CN101996074B

Abstract

A method and device for managing software using the Software Component Management Object(SCOMO). The method includes: obtaining the software information on user equipments; obtaining the information of the software which is operated in the mode of non-Software Component Management Object (NSCOMO), on the user equipment, according to the software information; according to the information of the software which is operated in the mode of NSCOMO, creating and configuring corresponding nodes for the software which is operated in the mode of NSCOMO, on the corresponding nodes of SCOMO; reporting the information of the corresponding node to the SCOMO server. The solution solves the problem that the existing SCOMO mode can not manage software which is installed on the terminal equipment by users in the mode of NSCOMO.

Description

Method and device for managing object management software using software component The present application claims to be submitted to the Chinese Patent Office on August 20, 2009, and the application number is 200910168281. 0, the invention name is "method and device for managing object management software using software components" Priority of Chinese Patent Application, the entire contents of which is incorporated herein by reference. TECHNICAL FIELD The present invention relates to the field of wireless communication technologies, and in particular, to a method and apparatus for managing object management software using software components. BACKGROUND OF THE INVENTION Open Mobile Alliance Device Management Specification 1. 2 (OMA DM VI. 2) Open Mobile Alliance Device Management (0MA)

DM) system for third-party management and setting of environment and configuration information in wireless network terminal equipment, solving problems encountered in the use of these wireless network terminal equipment, and performing software through over-the-air (OTA) mode And firmware installation, upgrade and other operations, and provide more personalized and personalized services to enhance the user experience. The third party may be the information management department of the mobile operator, the service provider or the partner. The wireless network terminal device can be a functional object in the mobile terminal and the terminal.

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 delivered by the DM server. The management tree stored on the terminal device can be regarded as an interface for the DM server (DM Server) to manage the terminal device through the DM protocol. The management tree includes some basic management objects (Management Objects, MOs). The operation of the management objects by the DM server reaches the purpose of controlling the management objects of the terminal. The operation commands include Get, Replace (R), Exec, Copy, Delete, and so on. The software component management object (SC0M0) in the management object is used to manage the software that the device needs to install or has been installed, as shown in Figure 2. The software managed by the SC0M0 management object may include a program, an executable file, a software security certificate, a registration, and the like. The software management operations supported by the SC0M0 protocol are: download, distribution (del ivery)^ installation (instal lation), upgrade (update), removal (removal), activation/deactivation (activation/de-activation), and SC0M0 The management object also supports inventory counting of all software in the terminal device.

In the process of implementing the present invention, the inventors have found that the prior art has at least the following drawbacks: The existing SC0M0 mode cannot manage the software installed by the user to the terminal device through the non-SC0M0 mode, for example, the user downloads or copies himself. After installing the installation files to the terminal device for installation, the operator or the management of these terminal devices cannot query or manage the software by means of an effective management tree. Summary of the invention

The embodiment of the invention provides a method and a device for managing object management software by using a software component, so as to solve the problem that the existing SC0M0 mode cannot manage the software installed by the user on the terminal device through the non-SC0M0 mode.

An embodiment of the present invention provides a method for managing object management software by using a software component, including: acquiring software information on a user equipment;

Obtaining, according to the software information, information about software that is operated by the non-software component management object on the user equipment;

Creating, according to the information of the non-software component management object mode, the corresponding node of the software operated by the non-software component management object mode under the corresponding node of the software component management object;

The information of the node is reported to the software component management object server.

An embodiment of the present invention further provides a method for managing object management software by using a software component, including: receiving information of a node reported by a client component using a software component; and the node is a software component management object client on the software A node in the component management object that is created and configured for the software; the software is software that operates on the user device in a manner that is not a software component management object.

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

a first acquiring module, configured to acquire software information on the user equipment;

a second obtaining module, configured to obtain, according to the software information, information about software that is operated by the non-software component management object on the user equipment;

a creating module, configured to create and configure a corresponding node for the software operated by 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 according to the non-software component management object mode;

The reporting module is configured to report the information of the node to the software component management object server.

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

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

The above embodiment obtains the information of the software operated by the non-SC0M0 mode, and obtains the information according to the acquired information. The SCOMO-operated software creates a corresponding node in SCOMO, and reports the corresponding node information to the SC0M0 server, which solves the problem that the existing SC0M0 mode cannot manage the software installed by the user through the non-SC0M0 mode to the terminal device.

The technical solution of the present invention will be further described in detail below through the accompanying drawings and embodiments. BRIEF DESCRIPTION OF DRAWINGS FIG. 1 is a schematic overall structural diagram of an OMA DM system in the prior art;

2 is a schematic diagram of a SC0M0 management tree in the prior art;

3 is a flowchart of a method for managing object management software using a software component according to an embodiment of the present invention; FIG. 4 is a flowchart of another method for managing object management software using a software component according to an embodiment of the present invention;

5 is a flow chart of uninstall management in a method for managing object management software using a software component according to an embodiment of the present invention;

6 is a flow chart of still another method for managing object management software using a software component according to an embodiment of the present invention;

FIG. 7 is a schematic structural diagram of a software component management object client device according to an embodiment of the present invention; FIG. 8 is a schematic structural diagram of a software component management object server according to an embodiment of the present invention. 3 is a flowchart of a method for managing object management software using a software component according to an embodiment of the present invention. The method includes:

Step 31: Obtain software information on the user equipment.

This action can be performed by the SC0M0 client on the terminal device, ie the user device. The SC0M0 client can obtain software installation information, download information, distribution information, and the like from the user device. The SC0M0 client monitors the software to obtain software installation, download or distribution information, or collects software installation, download or distribution information after receiving the instructions sent by the SC0M0 server.

Step 32: Obtain information about the software that is operated by the non-SC0M0 mode on the user equipment according to the software information.

This action can be performed by the SC0M0 client on the terminal device, ie the user device. The SC0M0 client can determine, according to the information obtained in step 31, whether the software is installed, downloaded, or distributed in a non-SC0M0 manner. The soft The information of the piece is any one or combination of the following information: software name, software version, software description information. Step 33: Create and configure a corresponding node for the non-SC0M0 mode operating software under the corresponding node of the SC0M0 according to the information of the software operating in the non-SC0M0 mode.

This action can be performed by the SC0M0 client on the terminal device, ie the user device. The SC0M0 client creates and configures the corresponding node for the software under the corresponding node of SC0M0. When the software is installed in a non-SC0M0 mode, the corresponding node is created and configured for the software under the Deployed node of the SC0M0. When the software is downloaded in a non-SC0M0 mode, a corresponding node is created and configured for the software under the Download node of SC0M0. When the software is distributed in a non-SC0M0 manner, a corresponding node is created and configured for the software under the Delivered node of SC0M0.

When the corresponding node is created and configured for the software installed in the non-SC0M0 mode, the method includes: creating a package identifier reference node for the software under the deployment node of the SC0M0; configuring the reference identifier node for identifying the software The value to be installed with non-SC0M0. When it is used to identify that the software is installed in a non-SC0M0, a new node may also be created and configured under the deployment node of the SC0M0; the new node is a node for identifying that the software is installed with a non-SC0M0.

When the corresponding node is created and configured for the software that is downloaded in the non-SC0M0 mode, the method includes: creating a package identification node for the software under the deployment node of the SC0M0; configuring the package identification node to identify the software to be non- The value downloaded by SC0M0. When the software is used to download the non-SC0M0, a new node may be created and configured under the download node of the SC0M0; the new node is a node for identifying that the software is downloaded by the non-SC0M0.

When the corresponding node is created and configured for the software distributed in the non-SC0M0 manner, the method specifically includes: creating a package identification node for the software under the distribution node of the SC0M0; configuring the package identification node to identify the software to be non- The value assigned by SC0M0. When it is used to identify that the software is distributed by non-SC0M0, a new node may also be created and configured under the distribution node of SC0M0; the new node is a node for identifying that the software is distributed by non-SC0M0.

Step 34: Report the information of the node to the SC0M0 server.

This action can be performed by the SC0M0 client on the terminal device, ie the user device. The SC0M0 client may send the management subtree of the software to at least one or a combination of the location information of the SC0M0, the current state information of the software, or the information of the node used to identify the software to operate in a non-SC0M0 mode. Give the SC0M0 server. The action may also perform an operation of reporting information of the node according to the query instruction sent by the SC0M0 server.

In this embodiment, the SC0M0 client monitors the software operating in the non-SC0M0 mode, and creates and configures the corresponding node for the software in the SC0M0. The SC0M0 implements the management of the non-SC0M0 mode operating software, so that the operator or other management The party can implement all the software on the user equipment based on the already widely recognized SC0M0. Query and management.

The method for managing the object management software using the software component provided by the embodiment of the present invention may further include: when the software operating in the non-SC0M0 mode is uninstalled in the foregoing embodiment, the method for managing the object management software using the software component provided by the embodiment of the present invention may further include:

Obtaining the uninstallation information of the software operating in the non-SC0M0 mode. This action can be performed by the SC0M0 client on the terminal device, i.e., the user device. The SC0M0 client monitors the software to obtain the uninstallation information of the software, or collects the uninstallation information of the software after receiving the instruction sent by the SC0M0 server.

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

The software is reported to be unloaded to the SC0M0 server. This action can be performed by the SC0M0 client on the terminal device, ie the user device.

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

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

It is assumed that the SC0M0 client deletes the node information of a certain software according to the deletion instruction of the SC0M0 server. When the software has been installed, the method for managing the object management software using the software component provided in this embodiment may further include uninstalling the software. When the software is not installed, the method for managing object management software using the software component provided by this embodiment may further include deleting the physical file of the software operated by the non-SC0M0 mode on the user equipment.

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

Receiving information of a node reported by the SC0M0 client; the node is a node created and configured for the software in the SC0M0 on the SC0M0 client; the software is software running on the user equipment in a non-SC0M0 manner.

This action can be performed by the SC0M0 server on the DM server. After the SC0M0 client creates and configures the node for the software that is not in the SC0M0 mode, the SC0M0 client reports the corresponding information to the SC0M0 server. For details, see step 34 above.

After receiving the above information, the SC0M0 server can implement query and management of all software on the user equipment.

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

A query instruction containing an identifier for identifying a software operating in a non-SC0M0 mode, such as "UserPrivate", is used to query node information of the software operating in a non-SC0M0 mode based on the identifier. This action can be performed by the SC0M0 server on the DM server. SC0M0 server sends a query command All information on the software operated by the non-SC0M0 mode on the user equipment can be known.

Sending a delete command, which is used to delete software that is operated by the non-software component management object on the user equipment. This action can be performed by the SC0M0 server on the DM server. The SCOMO server can manage the software operated by the non-SC0M0 mode on the user equipment by sending a delete command.

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

Step 41: Obtain software installation information on the user equipment.

This action can be performed by the SC0M0 client. The SC0M0 client monitors the progress and process of software installation on the user equipment. The SC0M0 client can monitor the software installation information on the user equipment in real time. It can also use the periodic timing method to monitor the software installation information on the user equipment during the collection period. It can also start collecting the user equipment after receiving the instruction of the SC0M0 server. Software installation information on.

The SC0M0 client monitors and collects software installation information on the user equipment, and can be implemented by calling a calling function provided by the user equipment operating system. For example, the Windows Mobi le system can call the "msi" function to obtain a list of installed software on the mobile phone; It can also be implemented by analyzing the software files of the user equipment operating system installation and uninstallation. For example, the Symbian or Li dish x system can read the analysis system file "instal led-software, log" or "Appinist. ini". To get software installation information.

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

This action can be performed by the SC0M0 client. The SC0M0 client determines whether the software installed on the user equipment is SC0M0 mode or non-SC0M0 mode.

After the SC0M0 client knows the information about the software installed on the device, it determines whether the software is executing the SC0M0 command "Inventory/Delivered/<X>/0perations/Instal l".

Or " Inventory/Del ivered/ <X>/ Operat ions/Instal 1 Inactive "

Or "Download/ <X>/Operations/Downloadlnstal l "

Or "Download/ <X>/ Operat ions/Downloadlnstal 1 Inactive" to install, if no, it is determined that the software is installed in non-SC0M0 mode.

For the software installed in the SC0M0 mode, the SC0M0 client creates and configures the corresponding node under the deployed node according to the existing SC0M0 protocol.

Step 43: Create and configure a corresponding node for the software in SC0M0 according to the information of the software. This action can be performed by the SC0M0 client. For the software installed in the non-SC0M0 mode, the SC0M0 client knows the name, version, installation path, etc. of the installed software by running the monitoring program, creates a node for the software under the "Deployed" node, and configures the software information to the corresponding node. Go in.

After the SC0M0 client obtains the information of the software installed in the non-SC0M0 mode, create the corresponding node for the software under "Inventory/Deployed/": "<X>", "ID", "PkglDRef", "Name, , , "Version'^ "Status" and "State,,.

Among them, the name of the "<X>" node can be customized by the SCOMO client. The "ID" node is generated by the SC0M0 client. The value of this node is not repeatable and is the unique identifier of the software on SC0M0. The "PkglDRef" node value is a number generated by the SP number and the software name according to a certain algorithm in the SC0M0 protocol. In this embodiment, the value of the node is set to distinguish the special value of the number generated by the above algorithm, for example, "UserPrivate" is used to distinguish the software installed in the SC0M0 mode by the non-SC0M0 mode, and the SC0M0 server can pass the query value of "UserPrivate". The PkglDRef" node is used to obtain information about all software installed on SC0M0 in a non-SC0M0 manner. The "Name" node value can be the installation name of the software obtained in step 41. The "Version" node value can 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 started to delete. If the software is currently running, the "State" node value is 20; if the software is currently not running, the "State" node value is 10.

If the SC0M0 client obtains the description of the software from step 41, it can also create a "Description" node and write the description information to the node value.

The SC0M0 client can also create the executable node "Operations/Remove". For software that is not installed in SC0M0 mode, the SC0M0 server can also issue instructions to perform "Operations/Remove" to uninstall.

The SC0M0 server can issue the "Get" command to read the node under "Inventory/Dprinted" to get the node information under all "Dprinted", or just by reading the "PkglDRef" node with the value equal to "UserPrivate". , to get the node information of the software installed in non-SC0M0 mode.

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

This action can be performed by the SC0M0 client. The SC0M0 client reports information about the software installed in the SC0M0 mode to the SC0M0 server.

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

Correspondingly, the method for managing object management software using the software component provided by the embodiment of the present invention may include: Receiving information of a node reported by the SCOMO client; the node is a node created and configured for the software in the SC0M0 on the SC0M0 client; the software is software installed on the user equipment in a non-SC0M0 manner. This action can be performed by the SC0M0 server. For details of the received node, see the description of step 44 above.

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

The method for managing the object management software using the software component provided by the embodiment of the present invention may further include: sending a deletion instruction, and deleting the software installed by the user equipment in a non-SC0M0 manner. This action can be performed by the SC0M0 server. The SC0M0 server can delete all software installed on the user equipment that is not SC0M0 by deleting the instruction.

In this embodiment, the SC0M0 client monitors the software installed in the non-SC0M0 mode, and creates and configures the corresponding node for the software in the SC0M0. The SC0M0 implements the management of the non-SC0M0 mode installation software, so that the operator or other management The party can implement query management of all installed software on the user equipment on the basis of the already widely recognized SC0M0.

The method for managing object management software using the software component provided by the embodiment of the present invention may further include uninstalling and managing the software. As shown in FIG. 5, the specific may include:

Step 51: Obtain the uninstallation information of the software.

This action can be performed by the SC0M0 client. The SC0M0 client monitors whether the software is uninstalled on the user equipment through the monitoring program. In the case where the software is uninstalled, the SC0M0 client performs step 52.

The SC0M0 client can monitor the software uninstallation on the user equipment in real time. It can also use the periodic timing method to monitor the software uninstallation on the user equipment during the collection period. It can also start collecting the user equipment after receiving the instruction of the SC0M0 server. The software uninstallation situation.

The SC0M0 client monitors the software uninstallation on the user equipment. It can be implemented by calling the calling function provided by the operating system of the user equipment, or by analyzing the log files of the software uninstalled by the operating system of the user equipment, such as the Symbian or Li dish x system. The software uninstallation information can be obtained by reading the analysis system file "uninstal led-software, log" on the mobile phone.

Step 52: In the case that the software is uninstalled in a non-SC0M0 manner, the node created in the SC0M0 for the software is deleted according to the uninstall information.

This action can be performed by the SC0M0 client. The SC0M0 client determines whether the uninstalled software is uninstalled in SC0M0 mode. After the SC0M0 client knows the information of the software uninstalled on the user equipment through step 51, it can determine whether the software is uninstalled by executing the SC0M0 instruction "Inventory/Deployed/<X>/Operations/Remove". If yes, it indicates that the uninstalled software is uninstalled in the SC0M0 mode, and the corresponding node under the "D-printed" node is deleted according to the existing SC0M0 protocol; if not, the uninstalled software is uninstalled in the non-SC0M0 mode, and the obtained information is obtained from the monitoring information. Delete the name of the uninstalled software, delete the corresponding node under the "Deployed" node, and go to Step 53.

Step 53: Reporting to the SC0M0 server that the software is uninstalled.

This action can be performed by the SC0M0 client. The SC0M0 client reports to the SC0M0 server that the software is uninstalled in a non-SC0M0 mode.

The SC0M0 client reports the status of the software to the SC0M0 server as "Uninstall", and reports the URL of the software on the management tree: "Inventory/Deployed/<X>", and reports the value of "PkglDRef" to the SC0M0 server, letting the server know. Uninstalled is software that is installed or uninstalled in a non-SC0M0 mode.

Take a mobile phone with Windows Mobile operating system as an example. Assume that the phone has a SC0M0 client installed and supports the SC0M0 protocol. The SC0M0 client uses the "msi" function of the Windows Mobile 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 Fighter. 2 from the Internet to the computer, and uses the data cable to connect the mobile phone and the computer, copy the installation file to the mobile phone, and when installing, the SC0M0 client obtains the newly installed software. The name Fighter, version 1. 2, and the installation path " \Applications\Fighter,,.

The SC0M0 client checks the record of the installation instruction of the SC0M0 server, and after learning that the newly installed software is installed in the non-SC0M0 mode, starts to create a management node for the newly installed software under the "Inventory/DPrinted" node of SC0M0, and will obtain The software information obtained is configured into the corresponding node:

Create and configure the name of the node "Fighterl23", the name of the "<X>" node can be customized by the SC0M0 client;

Create and configure the value of the "ID" node to 000876 to uniquely identify the software on the entire SC0M0; create and configure the value of the "PkglDRef" node to be "UserPrivate" to indicate that the software is software that is not SC0M0 installed;

Create and configure the value of the "Name" node to be "Fighter";

Create and configure the value of the "Version" node to 1. 2;

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

Create and configure a "Status" with a node value of 10 to indicate that the software has not started uninstalling;

Create the executable node "Operations/Remove". When the SC0M0 server sends an instruction to execute the node to the SC0M0 client, the SC0M0 client looks for the uninstaller under the program installation directory "\Applications\Fighter" and uninstalls the software. After uninstalling, the SC0M0 client will delete all the sections starting from <Fighterl23> Point, that is, clear all information about the software in the management tree.

After the corresponding node is created and configured on the SC0M0 client, the information about the installation software is reported to the SC0M0 server. The reported information includes: The location information of the management subtree of the software on the entire SC0M0 "Inventory/Deployed/Fighterl23"; the status information of the software "Status = 10"; and "PkgIDRef=UserPrivate", telling the SC0M0 server that the software is The user installs the software, that is, the software installs the software in a non-SC0M0 mode.

Alternatively, the SC0M0 server may send a "Get" command to the SC0M0 client to obtain all the node information under the "D-printed" node to obtain all software installation information on the current device; or send a "Get" command with parameters. To obtain the information of all the <X> nodes of the "PkglDRef" node value under the "Deployed" node with the value of "UserPrivate", to obtain the software list of the non-SC0M0 mode installed on the current user equipment.

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

Suppose a user Bluetooth manner book reader software ERead _er 5. 5 sent to the phone, and install. The SC0M0 client query is known, or the SC0M0 server knows that the user equipment newly installed the software ERead _er 5. 5 through comparison analysis, and obtains the software name, version, description and installation path from the log file.

The SC0M0 client checks the record of the installation instruction of the SC0M0 server and determines that the software is not SC0M0. The SC0M0 client starts to create a management node for the software under the Inventory/DPrinted node of SC0M0:

Create and configure the name of the node as 456EReader, the name of the node can be customized by the SC0M0 client;

Create and configure the value of the "ID" node to 000888 to uniquely identify the software on the entire SC0M0; create and configure the value of the "PkglDRef" node to be empty to indicate that the software is installed in a non-SC0M0 mode;

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

The value of the "Version" node is 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 executable node "Operations/Active". When the SC0M0 server sends an instruction to execute the node to the SC0M0 client, the SC0M0 server looks for the startup file under the program installation directory "\Appl ications\EReader" and starts running the software. At the same time, the value of the "State" node is updated to 20, indicating that the software is running;

Create and configure the executable node "Operations/Remove". When the SC0M0 server sends an instruction to execute the node to the SC0M0 client, the SC0M0 server goes to the program installation directory "\Appl ications\Fighter" to find the uninstaller to uninstall the software. After the software is uninstalled, the SC0M0 client deletes all the nodes starting from <Fighterl23>, that is, clears all the information of the software in the management tree.

The SC0M0 server can send a "Get" command to the SC0M0 client to obtain all the node information under the "D-printed" node to obtain all software installation information on the current device; or send a "Get" command with parameters to obtain The information under the <X> node where the "PkglDRef" node value is empty under the "D-printed" node is used to obtain the list of software installed on the current device in the non-SC0M0 mode.

If the SC0M0 client obtains the latest system file "uninstal led-software. log", compare it with the system file "uninstal led-software. log" backed up 24 hours ago to analyze whether the software is uninstalled within 24 hours. When it is checked that the EReader is unloaded, the SC0M0 client checks the record of the installation instruction of the SC0M0 server, and judges that the software is unsold by the SC0M0 mode, and the SC0M0 client deletes all the nodes below the <EReader> node.

FIG. 6 is a flow chart of still another method for managing object management software using a software component according to an embodiment of the present invention. This embodiment mainly performs download management on software. As shown in FIG. 6, specifically, the method may include:

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

This action can be performed by the SC0M0 client. The SC0M0 client can implement the process of monitoring whether there is an over-the-air transmission on the current device. If it is detected, the information such as the name and version of the downloaded file can be obtained by obtaining the description file of the transmission file.

Step 62: In the case that the software is downloaded in a non-SC0M0 manner, the corresponding node is created and configured for the software according to the description file under the download node of the SC0M0.

This action can be performed by the SC0M0 client. The SC0M0 client creates and configures the corresponding node under the "Download" node according to the information such as the name and version of the downloaded file. After the software download is completed, the download management may further include:

Step 63: Create and configure a corresponding node for the software under the download node of the SC0M0.

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

For software that has been downloaded but not yet installed, or for software that is already installed on the user device and not installed, the SC0M0 client compares with the information already existing under the distribution node of SC0M0 according to the software information such as the file name or type. No, it indicates that the software is distributed in a non-SC0M0 manner, and the corresponding node is created and configured for the software under the distribution node of the SC0M0.

Take a mobile phone with an Andriod operating system as an example. Suppose the user receives a text message with a software download URL using the mobile phone, and the user clicks the URL to download the software. The SC0M0 client monitors the process of over-the-air downloading on the mobile phone, and then obtains a description file of the downloaded software, and obtains a download URL, a file name, a version number, a description information, and a file type of the software. The SC0M0 client monitors the execution of the instruction record of the SC0M0 server, and determines that the downloaded software is delivered by the non-SC0M0 server. Then, under the "Download" node, a node is created for the downloaded software, and the information obtained from the description file is configured. Go to the value of the "PkgURL", "Name", "Description '\ "PkgType" node, and set a special value for "PkgID" such as "UserPrivate" to identify the non-SC0M0 mode download. The SC0M0 server can pass the query value equal to "UserPrivate" The "Download/O /PkglD" node is used to obtain the software downloaded from the current mobile phone that is not downloaded by SC0M0.

After the software is successfully downloaded, the SC0M0 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. PkgID "sets a special value such as "UserPrivate" or null to identify that the software is downloaded in a non-SC0M0 mode and creates a "/Inventory/Delivered/<X>/Operations/Remove" node. The SC0M0 server can obtain the software downloaded by the non-SC0M0 mode downloaded from the mobile phone by querying the "/Inventory/Del ivered/<X>/PkgID" node whose value is equal to "UserPrivate". The SC0M0 server can also instruct the SC0M0 client to delete the software by issuing the command "/Inventory/Del ivered/<X>/Operations/Remove".

The SC0M0 client can also obtain software information on the user device by searching for all files on the user device. After obtaining the software information of a certain software, the SC0M0 client passes the file name and type in the software information of the software and the <name^P<PkgType> of the existing software information under the "Inventory/Delivered" node. Compare and determine if 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. The SC0M0 server can query or delete the software by querying or deleting the instruction of SC0M0.

Take a Windows Mobile phone as an example. The phone also has a SC0M0 client installed, which supports the SC0M0 protocol. In this embodiment, the SC0M0 client searches for the storage device of the mobile phone, and searches for files before the software installation in all CAB, INI, LIC, CERT and other formats to obtain an executable file, a license file or a certificate on the mobile phone. Specific information about the file. Among them, the registration file or certificate file can also be considered as software information.

After finding the files in the format listed above, the SC0M0 client judges that these files are not distributed in the SC0M0 mode. Create corresponding nodes for these files under the "Inventory/Delivered/" node on SC0M0, and configure the node name, such as "name". , , , " version , , , " PkgType ", etc., set a special value such as "UserPrivate" or empty for "Inventory/Delivered/<X>/PkgID" to identify these files for non-SC0M0 mode distribution. The SC0M0 server can obtain the software information distributed by all non-SC0M0 modes on the user equipment by querying the value of the "Inventory/Delivered/<X>/PkgID" node; the SC0M0 server can send the operation instruction "Inventory/Del ivered/<X>/ Operations/Remove" to delete the corresponding file.

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

The first obtaining module 71 may be specifically configured to acquire software installation information on the user equipment. The second obtaining module 72 may be specifically configured to obtain, according to the software installation information, the non-SC0M0 manner installed on the user equipment. The information of the software may be specifically configured to create and configure a corresponding node for the software under the deployment node of the SC0M0 according to the information of the software.

The first obtaining module 71 may be specifically configured to obtain software download information on the user equipment in the process of downloading the software. The second obtaining module 72 may be specifically configured to obtain the user equipment according to the software download information. The information of the software downloaded by the non-SC0M0 mode; the creating module 73 may be specifically configured to create and configure a corresponding node for the software under the download node of the SC0M0 according to the information of the software. The first obtaining module 71 may be specifically configured to obtain information of software that is already installed on the user equipment and that is not installed. The second obtaining module 72 may be specifically configured to obtain information according to the information of all the existing and not installed software. The information of the software distributed in the non-SC0M0 manner; the creating module 73 may be specifically configured to create and configure a corresponding node for the software under the distribution node of the SC0M0 according to the information of the software.

The reporting module 74 may be specifically configured to use location information of the management subtree of the software in the SC0M0, the current state information of the software, and information of a node used to identify the software to operate in a non-SC0M0 mode. At least one is sent to the SC0M0 server.

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

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 configured to receive the query instruction and the delete instruction sent by the SC0M0 server; the node deletion module is configured to delete the node created for the software according to the deletion instruction; the reporting module may be specifically used according to the SC0M0 server The sent query instruction reports the information of the node.

The software component management object client device provided by the embodiment of the present invention may further include at least one of the following modules: an uninstall module, a delete module. The uninstall module is used to uninstall the software; the delete module is used to delete the physical file of the software on the user device.

FIG. 8 is a schematic structural diagram of a software component management object server according to an embodiment of the present invention. The SC0M0 server includes: a receiving module 81. The receiving module 81 is configured to receive information about a node that is reported by the SC0M0 client; the node is a node that is created and configured for the software in the SC0M0 on the SC0M0 client; and the software is operated by the non-SC0M0 mode on the user equipment. software.

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

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 configured to send a delete instruction, where the delete command is used to delete software that is operated by the non-SC0M0 mode on the user equipment.

The foregoing method and apparatus embodiment obtains the information of the software that is operated in the non-SC0M0 mode, and creates a corresponding node in the SC0M0 according to the acquired information, and reports the corresponding node information as the software operating in the non-SC0M0 mode. The SC0M0 server solves the problem that the existing SC0M0 mode cannot manage the software installed by the user on the terminal device through the non-SC0M0 mode.

A person skilled in the art can understand that all or part of the steps of implementing the above method embodiments may be completed by using hardware related to program instructions, and the foregoing program may be stored in a computer readable storage medium, and the program is executed when executed. The steps of the foregoing method embodiments are included; and the foregoing storage medium includes: a medium that can store program codes, such as a ROM, a RAM, a magnetic disk, or an optical disk. It should be noted that the above embodiments are only for explaining the technical solutions of the present invention, and are not intended to be limiting; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those skilled in the art that: The technical solutions described in the foregoing embodiments are modified, or some of the technical features are equivalently replaced. The modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

Rights request

A method for managing object management software using a software component, comprising:

Obtaining software information on the user device;

2. The method for managing object management software using a software component according to claim 1, wherein the information of the software operated by the non-software component management object mode comprises at least one of the following:

Software name, software version, software description information.

The method for managing object management software by using a software component according to claim 1, wherein acquiring software information on the user equipment comprises: acquiring software installation information on the user equipment;

Obtaining information about the software that is operated by the non-software component management object on the user equipment according to the software information, including: obtaining, according to the software installation information, information about software installed on the user equipment by using a non-software component management object ;

Creating and configuring a corresponding node for the software operated by the non-software component management object mode under the corresponding node of the software component management object according to the information of the software, including: deploying the node of the software component management object according to the information of the software Creating and configuring a corresponding node for the software operated by the non-software component management object mode; creating and configuring a corresponding node for the software operated by the non-software component management object mode under the deployment node of the software component management object, including:

Creating a package identification reference node for the software operated by the non-software component management object mode under the deployment node of the software component management object;

Configuring, for the package identification reference node, software for identifying the non-software component management object mode operation to manage the value of the object installation by the non-software component; or managing the non-software component under the deployment node of the software component management object The object-oriented software creates and configures the corresponding nodes, including:

Creating and configuring a new node under the deployment node of the software component management object; the new node is a node for identifying the operation of the non-software component management object mode to be a node installed by the non-software component management object;

Or, obtaining software information on the user equipment includes:

Obtaining software download information on the user equipment during the process of downloading the software; Obtaining information about the software that is operated by the non-software component management object on the user equipment according to the software information, including: obtaining, according to the software download information, information about software downloaded by the non-software component management object on the user equipment ;

Creating and configuring a corresponding node for the software under the corresponding node 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- Software component management object mode operation software creates and configures corresponding nodes;

Creating and configuring a corresponding node for the non-software component management object mode operation software includes: creating a package identification node for the non-software component management object mode operation software;

Configuring, for the package identifier node, a value that is used to identify the software operation of the non-software component management object mode to be downloaded in a non-software component management object manner; or, creating and configuring a corresponding software for the non-software component management object mode operation Nodes, including:

Creating and configuring a new node, the new node being a node for identifying that the software is downloaded in a non-software component management object;

Or, obtaining software information on the user equipment includes:

Obtain information about software that is already on the user device and not installed;

Obtaining information about the software operated by the non-software component management object on the user equipment according to the software information, including: acquiring software distributed by using a non-software component management object according to the information of all the existing and not installed software Information;

Creating and configuring a corresponding node for the software under the corresponding node 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- Software component management object mode operation software creates and configures corresponding nodes;

Configuring, for the package identification node, a value for identifying a software operation of the non-software component management object mode to be distributed by a non-software component management object; or creating and configuring a corresponding software for the non-software component management object mode operation Nodes, including:

A new node is created and configured, and the new node is a node that distributes software that is used to identify the non-software component management object mode operation as a non-software component management object.

The method for managing the object management software using the software component according to any one of claims 1 to 3, wherein the reporting the information of the node to the software component management object server comprises: At least one of location information of the management subtree of the software in the software component management object, current state information of the software, or information identifying a node in which the software operates in a non-software component management object manner Sent to the software component management object server.

The method for managing the object management software by using the software component according to claim 4, wherein the reporting the information of the node to the software component management object server comprises:

And reporting the information of the node according to the query instruction sent by the software component management object server.

The method for managing object management software using a software component according to any one of claims 1 to 3, further comprising:

Obtaining the uninstallation information of the software operated by the non-software component management object mode;

And deleting, in the non-software component management object manner, the node created in the software component management object for the software according to the uninstallation information;

Reporting the software to the software component management object server is uninstalled.

Receiving a deletion instruction sent by the software component management object server;

Deleting a node created by the software operated by the non-software component management object mode according to the deletion instruction.

8. The method of managing object management software using a software component according to claim 7, further comprising: uninstalling software that is operated by the non-software component management object mode; or

Deleting the physical file of the software operated by the non-software component management object mode on the user device.

9. A method of managing object management software using a software component, comprising:

Receiving information of a 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 a non-user device The software component manages the software that operates in the object mode.

The method for managing object management software using a software component according to claim 9, further comprising:

A query instruction is provided that includes an identifier for identifying software operating in a non-software component management object, the query instruction for querying node information of the software operating in a non-software component management object manner based on the identifier.

The method for managing object management software using a software component according to claim 10, further comprising: Sending a delete command, which is used to delete software that is operated by the non-software component management object on the user equipment.

12. A software component management object client device, comprising:

The software component management object client device according to claim 12, wherein the first obtaining 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 a corresponding node for the software under the deployment node of the software component management object according to the information of the software;

Or the first acquiring module is specifically configured to acquire software download information on the user equipment in the process of downloading the software;

The second obtaining module is specifically configured to obtain, according to the software download information, information about software downloaded by the non-software component management object on the user equipment;

The creating module is specifically configured 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 installed on the user equipment, and the second acquiring module is configured to obtain information according to the information of all the existing and not installed software. Information about the software distributed by the software component management object;

The creating 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.

The software component management object client device according to claim 12 or 13, wherein the reporting module is specifically configured to use location information of the management subtree of the software in the software component management object, The software current state information, at least one of information for identifying a node in which the software operates in a non-software component management object manner is sent to the software component management object server.

The software component management object client device according to claim 12 or 13, further comprising:

a third obtaining module, configured to acquire uninstallation information of the software;

a node deletion module, configured to delete a node created in the software component management object for the software according to the uninstallation information, where the software is uninstalled in a non-software component management object manner;

The reporting module is specifically configured to report, to the software component management object server, that the software is uninstalled.

An instruction receiving module, configured to receive a query instruction and a delete instruction sent by the software component management object server; and a node deletion module, configured to delete a node created for the software according to the deletion instruction;

The reporting module is specifically configured to report information of the node according to the query instruction sent by the software component management object server.

17. The software component management object client device according to claim 16, further comprising at least one of the following modules:

An uninstalling module, configured to uninstall the software;

And deleting a module, configured to delete a physical file of the software on the user equipment.

18. A software component management object server, comprising:

19. The software component management object server according to claim 18, further comprising at least one of the following modules:

a first sending module, configured to send a query instruction that includes an identifier for identifying software operating in a non-software component management object, where the query instruction is configured to query the non-software component management object according to the identifier Node information of the operating software;

And a second sending module, configured to send a delete command, where the delete command is used to delete software that is operated by the non-software component management object on the user equipment.