CN1953394A - A method for parameter configuration of functional assembly and its system and terminal equipment - Google Patents

Abstract

The invention discloses a function component parameter configuration method related to the field of OMA DM, which is used to realize the configuration management of the function component parameters in the equipment management specification, including setting corresponding parameters for each function component in the terminal equipment Node group: the device management server implements parameter configuration of the functional component by configuring relevant parameters in each node of the parameter node group corresponding to the functional component. Correspondingly, the invention also discloses a function component parameter configuration system and a terminal device thereof.

Description

Functional component parameter configuration method, system thereof, and terminal equipment

technical field

The present invention relates to Open Mobile Alliance (OMA, Open Mobile Alliance) device management (DM, Device Management) technology, in particular to a function component parameter configuration method and its system, and terminal equipment.

Background technique

Mobile terminal equipment is an important part of the entire mobile network operation service system. Device Management (DM, Device Management) refers to downloading data packets from the network side to terminal equipment through OTA (Over The Air), and The terminal equipment automatically runs, and then completes the subsequent corresponding software installation and configuration processing; at the same time, it can also automatically transfer the service information required by the operator and the function information of the terminal equipment from the terminal equipment to the DM server side. It can be seen that the device management system (DMS, Device Management System) provides a low-cost solution to maintain and manage the software and data of the terminal device, including setting the initial configuration information of the terminal device, and installing and updating it on the terminal device Permanent information, extract management information from terminal equipment, and process various events and alarm information generated by terminal equipment.

In the existing Open Mobile Alliance Device Management (OMA DM, Open Mobile Alliance DM) specification, the configuration processing of terminal devices such as network parameters and some general service parameters has been realized, such as network access points ( NAP, Network Access Point) parameters, proxy (Proxy) parameters, wireless application protocol proxy (WAP Proxy, Wireless Application Protocol Proxy) parameters, etc. are all network parameters. However, the existing OMA DM specification does not provide a corresponding mechanism for configuring functional component parameters on the terminal device, such as device capability parameters and application software parameters. The application software includes a network chat client, a photo album (Photo) client, an online game, etc., and the software parameters may be, for example, a server address, a user account, and the like. That is, in the OMA DM mode, the DM protocol does not set the relevant parameters of the functional components as the corresponding connection management objects, which is not convenient for the DM server to manage the relevant parameters of the functional components.

Contents of the invention

The technical problem to be solved by the present invention is to propose a function component parameter configuration method and its system, so as to realize the configuration management of the function component parameters in the equipment management specification.

Correspondingly, the present invention also provides a terminal device.

In order to solve the above problems, the technical scheme proposed by the present invention is as follows:

A method for configuring parameters of functional components, comprising the steps of:

In the terminal device, set a corresponding parameter node group for each functional component;

The device management server implements parameter configuration of the functional component by configuring relevant parameters in each node of the parameter node group corresponding to the functional component.

Preferably, the method further includes the step of updating the configured parameters in the node by the device management server.

Preferably, the process of updating the configured parameters specifically includes:

The device management server requests the configured relevant parameters from the terminal device;

The terminal device responds to the request, and feeds back the configured parameters in the relevant nodes in the corresponding parameter node group to the device management server;

When the parameter fed back by the terminal device is inconsistent with the pre-delivered new parameter, the device management server configures the new parameter into the corresponding node of the parameter node group in the terminal device.

Preferably, the parameter node group includes nodes for representing parameter names and nodes for representing parameter values.

Preferably, the parameter node group further includes a node representing a parameter type and a node representing a parameter format.

Preferably, the parameter node group exists in the form of a management object.

Preferably, each parameter node group existing in the form of a management object is set to the management subtree of the corresponding functional component in the device management tree.

Preferably, the parameter node group existing in the form of a management object is independently set in the terminal device; and an association between the parameter node group and the corresponding functional component identifier is established.

Preferably, the parameter node group based on the management object form is independently set in the terminal device; and a reference node is configured on the management subtree of the corresponding functional component to refer to the parameter node group based on the management object form .

Preferably, the corresponding parameter node group configured for each functional component is a common parameter node group.

A functional component parameter configuration system, comprising:

In the terminal device, respectively setting a node group setting unit corresponding to a parameter node group for each functional component; and

In the device management server, the parameter configuration unit for parameter configuration of the functional components is implemented by configuring relevant parameters in each node of the corresponding parameter node group set by the node group setting unit for the functional components.

Preferably, the system further includes a parameter update unit for updating the parameters configured by the parameter configuration unit in the relevant nodes in the device management server.

A terminal device includes a node group setting unit for setting a corresponding parameter node group for each functional component.

A method for configuring parameters of functional components, comprising the steps of:

Set a reference node on the management subtree of the corresponding functional component, which is used to refer to the corresponding existing parameter node group on the device management tree;

The device management server implements parameter configuration for corresponding functional components by configuring related parameters in each node of the referenced parameter node group.

Preferably, referring to the existing parameter node group is implemented by configuring an identifier corresponding to the existing parameter node group in the reference node.

Preferably, the parameter node group exists in the form of a management object.

Preferably, the parameter node group is a connection management object; or a specific management object corresponding to related functional components; or a common management object corresponding to multiple functional components at the same time.

A functional component parameter configuration system, comprising:

Configure a reference node on the management subtree corresponding to the functional component, which is used to refer to the reference node setting unit corresponding to the existing parameter node group on the device management tree; and

In the device management server, the parameter configuration unit for parameter configuration of the corresponding functional components is implemented by configuring relevant parameters in each node of the parameter node group referenced by the reference node set by the reference node setting unit.

A terminal device, comprising a reference node setting unit for setting a reference node on a management subtree corresponding to a functional component to refer to a corresponding existing parameter node group on the device management tree.

The beneficial effect that the present invention can reach is as follows:

In the present invention, the corresponding parameter node group is respectively set for each functional component in the terminal device, and the DM server realizes the parameter configuration of the functional component by configuring relevant parameters in each node of the parameter node group corresponding to the functional component, thereby being able to It solves the problem that the DM server cannot configure and manage the parameters of the functional components in the terminal device in the existing OMA DM specification, and it can facilitate the configuration and management of the functional component parameters and other parameters in the terminal device by the DM server.

The technical scheme of the present invention also sets a reference node on the management subtree of the corresponding functional component to use the set reference node to refer to the corresponding existing parameter node group on the device management tree, so that the DM server passes through the referenced parameter node Relevant parameters are configured in each node of the group to realize the parameter configuration of the corresponding functional components, which can also solve the problem that the DM server cannot perform parameter configuration and management of the functional components in the terminal device in the existing OMA DM specification.

Description of drawings

Fig. 1 is the main realization principle flow chart of the first kind of function module parameter configuration method proposed by the present invention;

2 is a schematic diagram of the interaction between the DM server and the parameter node group set in the terminal device, and the interaction process between the application software and the parameter node group in the terminal device;

Fig. 3 is the schematic diagram of the processing procedure of the server identification of the E-mail client software configured in the DM server updating terminal equipment in the method of the present invention;

Fig. 4 is a schematic diagram of the structure of the parameter node group when the MO form-based parameter node group is hung in the corresponding position in the corresponding software component management subtree in the DM management tree;

FIG. 5 is a schematic structural diagram of a parameter node group when the MO-based parameter node group is independently configured in a terminal device;

Fig. 6 is a schematic structural diagram of a parameter node group configured with parameters in the form of parameter name and parameter value matching;

7 is a block diagram of the main components of the first functional component parameter configuration system proposed by the present invention;

FIG. 8 is a structural block diagram of the main components of the first type of terminal equipment proposed by the present invention;

FIG. 9 is a schematic diagram of the management tree structure of reference nodes set on the corresponding SCOMO according to the principle of the second method proposed by the present invention.

Detailed ways

The design concept of the present invention is to set a corresponding parameter node group corresponding to each functional component on the DM tree of the terminal device, wherein each parameter node group can be set in the form of a management object, so that the DM server can pass through each functional component. Add, modify and delete parameters in each node of the parameter node group to realize the parameter configuration of the corresponding functional components.

The functional components mentioned here in the present invention include Software Component, Device Capability Component, Look and Feel Customization, etc. Specifically, software components can be, but are not limited to, executable applications (such as exe), libraries (such as lib, dll), configurations (such as ini), resources (such as jpg, png, ico) and the like. Among them, many configurable items on the terminal device exist in the form of functional components, such as user interface (skin, menu, desktop theme, wallpaper, etc.), functions (ringtone, video, camera, etc.), application software (chat software, album software, etc.) , E-mail software, online games, etc.), so these functional components all need configuration parameters.

The main realization principle of the present invention and its specific implementation will be described in detail below in conjunction with each accompanying drawing.

Please refer to Fig. 1, this figure is the main realization principle flowchart of the first kind of function component parameter configuration method proposed by the present invention, and its main realization process is as follows:

Step 10, in the terminal device, set corresponding parameter node groups for each functional component respectively; wherein the parameter node groups respectively set corresponding to each functional component can form a subtree structure, that is, in order to comply with the OMA DM specification, the parameter Each node in the node group exists based on a management object (MO); of course, each node in the parameter node group can also exist based on a decentralized state.

In step 20, the DM server implements parameter configuration processing for a certain functional component by configuring relevant parameters in each node of the parameter node group corresponding to the functional component. The subsequent DM server may also update the configured parameters in the corresponding nodes of the parameter node group, for example, update and delete the configured parameters.

According to the above-mentioned implementation principle of the method of the present invention, the DM server can remotely operate the parameter node group set on the terminal device through the DM protocol, and the application software installed in the terminal device can access the parameters configured in the corresponding nodes in the parameter node group through the correspondingly designed interface ; Wherein the corresponding interface mentioned above can be specifically designed and determined by a specific terminal equipment manufacturer. For example, the application software in the terminal device can call the configuration parameters in the corresponding node in the corresponding parameter node group through the underlying operating system. How the application software in the terminal device calls the configuration parameters in the corresponding node is not the concern of the present invention. Problem, the focus of the solution of the present invention is to solve the problem that the DM server realizes the parameter configuration of the functional components by configuring related parameters in the corresponding nodes of the corresponding parameter node group set on the terminal device. Specifically, please refer to FIG. 2 for a schematic diagram of the interaction between the DM server and the parameter node group set in the terminal device, and the interaction process between the application software and the parameter node group in the terminal device.

In the technical solution of the present invention, if the parameter node groups set corresponding to each functional component exist based on the MO form, and each parameter node group based on the MO form is set in the terminal device in the form of a management subtree, then the DM server will The process of configuring the parameters of the application software in the terminal device and the subsequent process of maintaining and managing the parameters of the configured functional components can be completed through the standard DM protocol. The process for the DM server to update the configured parameters in the corresponding nodes of the parameter node group in the terminal device is as follows:

The DM server requests the configured relevant parameters from the terminal device;

The terminal device responds to the received request, and feeds back the parameters configured in the relevant nodes in the corresponding parameter node group to the DM server;

When the parameter fed back by the terminal device is inconsistent with the pre-delivered new parameter, the DM server configures the new parameter into the corresponding node of the parameter node group in the terminal device.

Since the implementation process of parameter configuration for different functional components is similar, the following only takes the implementation method of parameter configuration for software components as an example to illustrate, and the parameter configuration for other functional components such as device capability components and appearance customization components The implementation method is similar to this.

Please refer to Fig. 3, this figure is the processing schematic diagram of the server identification of the E-mail client software configured in the DM server updating terminal equipment in the method of the present invention, and its concrete processing process is as follows:

1. The software provider provides the software component parameter configuration package to the DM server through the Web Service Interface (WSI, Web Service Interface);

2. The DM server establishes a session connection with the terminal device, and the session connection establishment process follows the standard OMA session connection mechanism;

3. The DM server sends a request for obtaining the server identification of the E-mail client software to the terminal device:

<Get>

<Item>

<Target>

<LocURI>./Setting/Server/Server ID</LocURI>

</Target>

</Item>

</Get>

4. The terminal device responds to the received request, extracts the server identification of the original E-mail client software configured in the corresponding node in the corresponding parameter node group, and returns it to the DM server;

<Results>

<Item>

<Source>

<LocURI>./Setting/Server/Server ID</LocURI>

</Source>

<Data>pop.huawei.com</Data>

</Item>

</Results>

5. The DM server compares whether the server ID of the original E-mail client software fed back by the terminal device is consistent with the server ID of the new E-mail client software;

6. If the comparison results in the above 5 are inconsistent, the DM server sends a new server ID to the terminal device, and the terminal device stores the new server ID in the corresponding node in the above parameter node group;

<Replace>

<Item>

<Source>

<LocURI>./Setting/Server/Server ID</LocURI>

</Source>

<Data>pop3.huawei.com</Data>

</Item>

</Replace>

7. The terminal device feeds back a parameter update success message to the DM server.

Preferably, in the terminal device, if the parameter node group set corresponding to the functional component exists based on the MO form, each parameter node group based on the MO form can be set to the management subtree of the corresponding functional component in the device management tree, The parameter node group that exists in the form of MO is to be hung on the corresponding position of the management subtree of the corresponding functional component in the DM tree. It is also possible to independently configure the MO-based parameter node group corresponding to each functional component in the terminal device, and establish an association between the parameter node group and the corresponding functional component identifier. For the above two situations of the existence of the parameter node group in the terminal device, the following will give explanations respectively:

1. Hanging each parameter node group based on the MO form on the corresponding position of the corresponding functional component management subtree in the DM management tree:

As shown in Figure 4, this figure is a schematic diagram of the structure of the parameter node group when the parameter node group based on the MO form is hung in the corresponding position in the corresponding software component management subtree in the DM management tree; on the DM management tree in the terminal device , the DM server configures the parameters of the installed application software by configuring relevant parameters in each node of the parameter node group. The meaning of each node in the parameter node group based on the MO form is specifically explained as follows:

<X>/<Setting>

Tree Occurrence (number of occurrences) Format (format) Min.Access Types (minimum access type) ZeroOrOne(0 or 1) Node (node) Get (get)

This node is the parent node of the parameter node group based on the MO form, and the relevant software component parameter configuration information is stored under this node.

When describing the node path below, <X>/ will be omitted, and ./ will be used to represent this path.

./<Setting>/<Server>

Tree Occurrence (number of occurrences) Format (format) Min.Access Types (minimum access type) ZeroOrMore(0 or more) Node (node) Get (get)

This node is the server parameter of the application software, and the relevant parameter information of the server is stored under the node. For example, some client software on the network needs to set up a server. There may be multiple servers to choose from, or multiple servers may be used at the same time. server.

./<Setting>/<Server>/<Server ID>

Tree Occurrence (number of occurrences) Format (format) Min.Access Types (minimum access type) One(1) Chr (character) Get (get)

This node is used to describe the server ID. This node has a <Name> attribute, which can be used to indicate the name of the server, such as receiving server, sending server, etc.

./<Setting>/<Server>/<IP Address>

Tree Occurrence (number of occurrences) Format (format) Min.Access Types (minimum access type) ZeroOrOne(0 or 1) Chr (character) Get (get)

This node is used to describe the IP address of the server.

./<Setting>/<Server>/<AAuthName>

Tree Occurrence (number of occurrences) Format (format) Min.Access Types (minimum access type) ZeroOrMore (0 or more) Chr (character) Get (get)

This node is used to describe the user's authentication name on the server.

./<Setting>/<Server>/<AAuthSecret>

Tree Occurrence (number of occurrences) Format (format) Min.Access Types (minimum access type) ZeroOrMore(0 or more) Chr (character) Get (get)

This node is used to describe the user's authentication password on the server, which is calculated by the user's authentication name and password through the Hash algorithm.

./<Setting>/<Parameter list>

Tree Occurrence (number of occurrences) Format (format) Min.Access Types (minimum access type) ZeroOrOne(0 or 1) Node (node) Get (get)

This node is the parent node of other parameter information of the software component. Other parameters of the software are stored under the node, such as network connection information (such as port number parameters, proxy parameters, etc.) Parameters are different. This storage structure only uniformly arranges server and user accounts commonly used in network software components. Other software component parameters that need to be configured are placed under this node.

./<Setting>/<Parameter>/<X>

Tree Occurrence (number of occurrences) Format (format) Min.Access Types (minimum access type) ZeroOrMore(0 or more) Node (node) Get (get)

This node is a placeholder under which additional parameters of the software component are stored.

./<Setting>/<Parameter list>/<X>/<Parameter>

Tree Occurrence (number of occurrences) Format (format) Min.Access Types (minimum access type) One(1) Chr (character) Get (get)

This node is used to describe the specific parameter value, and the <Name> attribute of the node can be used to indicate the specific name of the software component parameter.

./<Setting>/<Ext>

Tree Occurrence (number of occurrences) Format (format) Min.Access Types (minimum access type) ZeroOrOne(0 or 1) Node (node) Get (get)

This node is a standby node, which is used to store other relevant information about the parameter configuration of software components, or to reserve for future expansion.

2. The case where each parameter node group based on the MO form is independently configured in the terminal device:

That is, the MO-based parameter node group set in the terminal device exists independently and is not linked to any first-level node of the corresponding functional component management subtree. This independent setting method can ensure the flexibility of the parameter node group.

As shown in Figure 5, it is a schematic diagram of the structure of the parameter node group when the MO-based parameter node group is independently configured in the terminal device. The parameter node group shown in this figure is relative to the parameter node group shown in Figure 4 above. , there is only one more software identification <Soft ID> node, which is used to associate the parameter node group with the corresponding software component; the meanings of other nodes are the same as explained above.

./<Setting>

Tree Occurrence (number of occurrences) Format (format) Min.Access Types (minimum access type) One(1) Node (node) Get (get)

This node is the starting node of the parameter node group based on the MO form, that is, the root node of each software component parameter configuration; this node can be placed anywhere under the root node of the device management tree (DM management tree), and it is a permanent Nodes (permanent nodes refer to nodes that cannot be deleted by the DM server), can be generated by the device manufacturer, or by other management parties according to needs; the device description framework (DDF, Device Description Framework) document will indicate that it is in the DM management tree specific location on the .

./<Setting>/<X>

Tree Occurrence (number of occurrences) Format (format) Min.Access Types (minimum access type) ZeroOrMore(0 or more) Node (node) Get (get)

This node is a placeholder, and the parameter configuration information related to a certain software component is stored under the node.

./<Setting>/<X>/<Soft ID>

Tree Occurrence (number of occurrences) Format (format) Min.Access Types (minimum access type) One(1) Chr (character) Get (get)

The node is used to store the identifier of the software component, so that the MO-based parameter node group can be associated with the corresponding software component.

The above method is an embodiment of standardizing each parameter. In fact, many functional components have their special application parameters, which cannot be defined as public parameters. In the case that the parameters cannot be standardized, they can be sent to the terminal in the form of pairing the parameter name and parameter value. The terminal device configures various parameters to the corresponding functional components according to this pairing form, which requires corresponding to each functional component. The parameter node group includes a node for representing a parameter name and a node for representing a parameter value, and may further include a node for representing a parameter type and a node for representing a parameter format.

As shown in FIG. 6 , it is a schematic diagram of a parameter node group when parameter configuration is performed in the form of parameter name and parameter value pairing. This parameter node group can be stored in the management tree of the corresponding functional component as its child node. The specific meaning of each node in the parameter node group is explained as follows:

/<Parameter>

Tree Occurrence (number of occurrences) Format (format) Min.Access Types (minimum access type) ZeroOrOne(0 or 1) Node (node) Get (get)

The internal node is the parent node of the parameter node group, and one or more parameter nodes are stored under the node.

./<Parameter>/<X>

Tree Occurrence (number of occurrences) Format (format) Min.Access Types (minimum access type) OneOrMore(1 or more) Node (node) Get (get)

This node is a placeholder node, and there can be one or more nodes, and each node is used to store a parameter node group.

./<Parameter>/<X>/<Para Name>

Tree Occurrence (number of occurrences) Format (format) Min.Access Types (minimum access type) One(1) Chr (character) Get (get)

This node is used to represent the name of the parameter.

./<Parameter>/<X>/<Para Value>

Tree Occurrence (number of occurrences) Format (format) Min.Access Types (minimum access type) One(1) Chr (character) Get (get)

This node is used to represent the value of the parameter.

./<Parameter>/<X>/<Para Format>

Tree Occurrence (number of occurrences) Format (format) Min.Access Types (minimum access type) One(1) Chr (character) Get (get)

This node is used to indicate the format of the parameter, and the possible formats are 'b64', 'bin', 'int', 'float', 'chr', 'bool', 'xml, 'date', 'time', etc.

./<Parameter>/<X>/<Para Type>

TreeOccurrence (number of occurrences) Format (format) Min.Access Types (minimum access type) One(1) Chr (character) Get (get)

This node is used to indicate the access type of the parameter, for example, whether the parameter can be obtained by the server, whether it can be modified by the server, etc.

./<Parameter>/<X>/<Ext>

Tree Occurrence (number of occurrences) Format (format) Min.Access Types (minimum access type) ZeroOrOne(0 or 1) Node (node) Get (get)

This node is reserved for expansion.

For example, if a certain software needs to configure the port number, the device management server can send the parameters to the terminal in the form of the above parameter pair for parameter configuration, for example, set <Para Name> in the delivered parameter pair to Port, <Para Value> Set to 8080, <Para Format> to int, and <Para Type> to Replace.

In addition, when the parameter node group set corresponding to each functional component in the terminal device exists based on the form of MO, and when the parameter node group is independently set in the terminal device, the corresponding reference can also be configured on the management subtree of the corresponding functional component Node, the reference node of the configuration is used to refer to the parameter node group that exists independently based on the management object form, so that the terminal device can also call the corresponding parameters configured in the corresponding parameter node group based on the corresponding functional components. Especially when the corresponding parameter node group configured for each functional component is a common parameter node group, when the parameter node group is independently set in the terminal device based on this method, the memory resources of the terminal device can be saved very effectively. The specific implementation details of this method will be described in detail in the second function component parameter configuration method proposed by the present invention below.

Corresponding to the implementation principle of the first method proposed above in the present invention, a function component parameter configuration system is also proposed here correspondingly, please refer to FIG. Composition structure block diagram, which mainly includes a node group setting unit 100 and a parameter configuration unit 110, wherein the specific functions of each component unit are as follows:

A node group setting unit 100, configured to set a corresponding parameter node group for each functional component in the terminal device;

The parameter configuration unit 110 is used to configure the parameters of the functional components in the DM server by configuring relevant parameters in each node of the corresponding parameter node group set by the node group setting unit 100 for the functional components;

In addition, the functional component parameter configuration system of the present invention also includes a parameter update unit 120 for updating the parameters configured in the relevant nodes by the above parameter configuration unit 110 in the DM server.

Correspondingly, the present invention also proposes a terminal device, as shown in FIG. 8 , which is a structural block diagram of main components of the first terminal device proposed by the present invention, which mainly includes a node group setting unit 100 for each Each functional component sets the corresponding parameter node group respectively.

Wherein the node group setting unit 100 can respectively set each parameter node group corresponding to each functional component as an MO form, and hang on the corresponding position of the corresponding functional component management subtree in the DM tree; Each parameter node group is independently configured in the terminal device. In this case, the terminal device also includes an identification association establishing unit 102 for establishing each parameter node group set by the node group setting unit 100 and corresponding functions in the DM tree. Association between component IDs.

In addition to the implementation principle of the functional component parameter configuration method proposed above in the present invention, when some connection management objects already exist on the terminal device or a certain functional component has a specific management object, then the corresponding functional component management sub- Add reference nodes in the tree to refer to these existing management objects, so that the DM server can realize the reference of the corresponding functional components in the terminal device through the reference nodes by configuring relevant parameters in these existing MO nodes. The role is to refer to the corresponding stored MO configured with related parameters, so as to achieve the purpose of configuring parameters for related functional components.

In view of the above principles, the main implementation process of the second function component parameter configuration method proposed by the present invention is as follows:

In the terminal device, set a relevant reference node on the management subtree of the corresponding functional component, and the set reference node is used to refer to the corresponding existing parameter node group on the DM tree;

The DM server implements parameter configuration for the corresponding functional components by configuring relevant parameters in each node of the referenced parameter node group; preferably by configuring the identification (ID) of the corresponding existing parameter node group in the reference node to reference the existing parameter node group.

The following will take a functional component as a software component as an example. A better implementation is that the existing parameter node group can exist in the form of MO, so that the existing parameter node group includes the following three situations:

The first embodiment: the existing parameter node group is the existing connection management object in the terminal device, because in the DM protocol, some public connection information has been defined to be stored according to the standardized MO structure, such as Proxy, NAP, Porr and other information are stored in the standard MO, so if the connection parameters of a software component can be stored using the existing standard connection MO, you can directly set the reference node on the management subtree corresponding to the software component to Refer to these standard connection MOs that store relevant parameters, so that the DM server can configure and manage the connection parameters of the terminal equipment.

Second embodiment: the existing parameter node group is the specific management object of the corresponding relevant software components in the terminal device, if the DM server downloads the data synchronization (DS, Data Sync) client software to the terminal device by DM mode, this The software information will be stored on SCOMO, and at the same time, the data synchronization client has its own defined DSMO, which stores the relevant configuration parameters and connection information of the DS client. The download and installation information of the data synchronization client is stored on the SCOMO management tree like this, and the corresponding related parameter configuration information is stored on the DSMO at the same time. Based on the thought of the method of the present invention, a reference node can be defined on the management subtree of the SCOMO, with Refer to the existing DSMO, so that the DM server can configure the corresponding parameter information configured for the SCOMO to the relevant nodes in the corresponding DSMO, thus linking the download and installation information of the software components with the relevant parameter information , which is convenient for the DM server to manage the software components.

The third embodiment: the existing parameter node group is a public management object corresponding to multiple software components in the terminal device. If the parameters corresponding to multiple software components can be shared, a public node can be defined separately for these software groups. MO, so that a reference node can be defined on the management subtree corresponding to each software component to refer to this separately defined MO, so that the DM server can configure the corresponding parameters to each of the separately defined MO In the node, the purpose of configuring related parameters for multiple software components at the same time is realized.

As shown in Figure 9, according to the principle of the second method proposed by the present invention, a schematic diagram of the management tree structure of the reference node is set on the corresponding SCOMO, and the specific meaning of each node in the tree is explained as follows:

./Deployed/<X>/ConRefs

Tree Occurrence (number of occurrences) Format (format) Min.Access Types (minimum access type) ZeroOrOne(0 or 1) Node (node) Get (get)

The internal node is the parent node of each reference node, under which one or more reference nodes are stored, which are used to refer to connection management objects or some specific management objects related to the corresponding software components;

./Deployed/<X>/ConRefs/<X>

Tree Occurrence (number of occurrences) Format (format) Min.Access Types (minimum access type) OneOrMore(1 or more) Node (node) Get (get)

This node is a placeholder node, and each node corresponds to a reference node;

./Deployed/<X>/ConRefs/<X>/ConRef

Tree Occurrence (number of occurrences) Format (format) Min.Access Types (minimum access class one(1) Chr (character) Get (get)

The leaf node is used to store specific reference information, such as the ID information of the referenced connection management object or some specific management objects, etc., and refer to the connection management object or some specific management objects related to software components through the stored reference information. object.

Corresponding to the method proposed here in the present invention, the present invention further proposes a corresponding functional component parameter configuration system and terminal equipment, wherein the proposed functional component parameter configuration system mainly includes:

The reference node setting unit is used to configure the reference node on the management subtree of the corresponding functional component in the terminal device to refer to the corresponding existing parameter node group on the DM tree;

The parameter configuration unit is used in the DM server to implement parameter configuration for the corresponding functional components by configuring relevant parameters in each node of the parameter node group referenced by the reference node set by the reference node setting unit.

The terminal device proposed here further includes a reference node setting unit on the basis of the existing composition structure, which is used to set a reference node on the management subtree of the corresponding functional component to reference the corresponding existing parameters on the device management tree node group.

Obviously, those skilled in the art can make various changes and modifications to the present invention without departing from the spirit and scope of the present invention. Thus, if these modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalent technologies, the present invention also intends to include these modifications and variations.

Claims (19)

1. A method for configuring parameters of functional components, comprising the steps of: In the terminal device, set a corresponding parameter node group for each functional component; The device management server implements parameter configuration of the functional component by configuring relevant parameters in each node of the parameter node group corresponding to the functional component. 2. The method according to claim 1, further comprising the step of updating the configured parameters in the node by the device management server. 3. The method according to claim 2, wherein the process of updating the configured parameters specifically includes: The device management server requests the configured relevant parameters from the terminal device; The terminal device responds to the request, and feeds back the configured parameters in the relevant nodes in the corresponding parameter node group to the device management server; When the parameter fed back by the terminal device is inconsistent with the pre-delivered new parameter, the device management server configures the new parameter into the corresponding node of the parameter node group in the terminal device. 4. The method according to claim 1, 2 or 3, wherein the parameter node group includes a node for representing a parameter name and a node for representing a parameter value. 5. The method according to claim 4, wherein the parameter node group further includes a node representing a parameter type and a node representing a parameter format. 6. The method according to claim 1, 2 or 3, characterized in that the parameter node group exists based on the management object form. 7. The method according to claim 6, characterized in that each parameter node group existing in the form of a management object is set on the management subtree of the corresponding functional component in the device management tree. 8. The method according to claim 6, characterized in that the parameter node group existing in the form of management objects is independently set in the terminal device; and An association between the parameter node group and the corresponding functional component identifier is established. 9. The method according to claim 6, characterized in that the parameter node group existing in the form of management objects is independently set in the terminal device; and A reference node is configured on the management subtree of the corresponding functional component to refer to the parameter node group existing in the form of the management object. 10. The method according to claim 9, wherein the corresponding parameter node group configured for each functional component is a common parameter node group. 11. A function component parameter configuration system, characterized in that it comprises: In the terminal device, respectively setting a node group setting unit corresponding to a parameter node group for each functional component; and In the device management server, the parameter configuration unit for parameter configuration of the functional components is implemented by configuring relevant parameters in each node of the corresponding parameter node group set by the node group setting unit for the functional components. 12. The system according to claim 11, further comprising a parameter update unit for updating the parameters configured in the relevant nodes by the parameter configuration unit in the device management server. 13. A terminal device, characterized by comprising a node group setting unit for setting a corresponding parameter node group for each functional component. 14. A method for configuring parameters of functional components, comprising the steps of: Set a reference node on the management subtree of the corresponding functional component, which is used to refer to the corresponding existing parameter node group on the device management tree; The device management server implements parameter configuration for corresponding functional components by configuring related parameters in each node of the referenced parameter node group. 15. The method according to claim 14, wherein the reference to the existing parameter node group is implemented by configuring an identifier corresponding to the existing parameter node group in the reference node. 16. The method according to claim 14 or 15, wherein the parameter node group exists in the form of a management object. 17. The method according to claim 16, wherein the parameter node group is: a connection management object; or A specific managed object corresponding to the relevant functional component; or A common management object corresponding to multiple functional components at the same time. 18. A function component parameter configuration system, characterized in that it comprises: Configure a reference node on the management subtree corresponding to the functional component, which is used to refer to the reference node setting unit corresponding to the existing parameter node group on the device management tree; and In the device management server, the parameter configuration unit for parameter configuration of the corresponding functional components is implemented by configuring relevant parameters in each node of the parameter node group referenced by the reference node set by the reference node setting unit. 19. A terminal device, characterized in that it includes a reference node setting unit for setting a reference node on the management subtree corresponding to the functional component to refer to the corresponding existing parameter node group on the device management tree.

Images