CN1848760A - Software assembly parameter configuration method, and system and terminal equipment thereof - Google Patents

Abstract

A method for configuring software component parameter includes downsending software component parameter to terminal device by device management server, configuring received software component parameter on corresponding software component by said terminal device. The configuring system of software component parameter and its relevant terminal device is also disclosed.

Description

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

technical field

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

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 the application software parameters on the terminal device, wherein the application software includes a network chat client, an album (Photo) client, an online game, etc., software parameters such as It can be server address, user account number, etc. That is, in the OMA DM mode, the DM protocol does not set the relevant parameters of the application software as the corresponding connection management objects, which is inconvenient for the DM server to manage the relevant parameters of the application software.

Contents of the invention

The technical problem to be solved by the present invention is to propose a software component parameter configuration method and system to realize configuration management of software component parameters in equipment management specifications.

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

A software component parameter configuration method, comprising the steps of:

A. The device management server sends software component parameters to the terminal device;

B. The terminal device configures the received software component parameters to corresponding software components.

Preferably, in the step A, the device management server sends the software component parameters in the parameter configuration data packet to the terminal device;

The parameter configuration data packet includes the software component identifier to which the software component parameters are to be configured, and the relative path of each software component parameter.

Preferably, said step B specifically includes the steps of:

B1. The terminal device finds the corresponding software component installation path according to the software component identifier contained in the received parameter configuration data packet; and

B2. Obtain the absolute path of the software component parameter according to the relative path of the software component parameter contained in the received parameter configuration data packet; and

B3. Write the corresponding software component parameter value on the obtained absolute path of the software component parameter, so as to configure the software component parameter to the corresponding software component.

Preferably, in the step A, the device management server sends the software component parameters in the configuration file to the terminal device;

The configuration file includes software component identifiers to which software component parameters are to be configured.

Preferably, in the step B, the terminal device configures the software component parameters contained in the received configuration file to the corresponding software components according to the software component identifier contained in the received configuration file.

Preferably, the configuration file is:

Device Management Profile; or

Client profile.

Preferably, the method also includes the steps of:

C. The terminal device establishes corresponding parameter configuration management objects on its own device management tree for the software component identification and each software component parameter contained in the received device management configuration file;

D. The device management server then manages and controls each parameter configuration management object in the terminal device to maintain the parameters of the corresponding software components.

Preferably, the method also includes the steps of:

c. The terminal device maps the software component identification and each software component parameter contained in the received client configuration file to corresponding nodes on its own device management tree; and

d. Establish a corresponding parameter configuration management object on each node mapped to;

e. The device management server then manages and controls each parameter configuration management object in the terminal device to maintain the parameters of the corresponding software components.

A software component parameter configuration system, including a terminal device and a device management server, wherein the device management server includes a parameter sending unit for sending software component parameters to the terminal device;

The terminal device includes a parameter receiving unit configured to receive the software component parameters delivered by the parameter delivery unit; and

A parameter configuration unit configured to configure the software component parameters received by the parameter receiving unit to corresponding software components.

Preferably, the terminal device further includes a management object creation unit for creating corresponding parameter configuration management objects on its own device management tree for the software component parameters received by the parameter receiving unit.

Preferably, the device management server further includes a parameter maintenance unit for maintaining parameters of corresponding software components by managing and controlling each parameter configuration management object established by the management object establishment unit in the terminal device.

A terminal device comprising:

A parameter receiving unit for receiving software component parameters issued by the device management server;

A parameter configuration unit configured to configure the software component parameters received by the parameter receiving unit to corresponding software components.

Preferably, the terminal device further includes:

A management object creation unit for creating corresponding parameter configuration management objects on the terminal device management tree for the software component parameters received by the parameter receiving unit.

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

The present invention sends the software component parameters to the terminal device through the DM server, and the terminal device then configures the received software component parameters to the corresponding software components, wherein the software component parameters delivered by the DM server can be delivered in the form of parameter configuration data packets, or It can be issued in the form of a device management configuration file, or in the form of a client configuration file. After the terminal device configures the received software component parameters to the corresponding software component, it can further target the Each software component parameter establishes a corresponding parameter configuration management object, thereby realizing the purpose of configuring the software parameters of the application software in the terminal device by the DM server in the existing OMA DM specification, and facilitating the DM server to configure the software in the terminal device. Configuration and management of parameters and other parameters.

Description of drawings

Fig. 1 is the main realization principle flow chart of the software component parameter configuration method of the present invention;

2 is a schematic diagram of a software component parameter configuration process in which the software component parameters are maintained by the underlying firmware in the terminal device in the method of the present invention;

3 is a schematic diagram of the main components of the software component parameter configuration system of the present invention;

FIG. 4 is a schematic diagram of main components and structures of a terminal device according to the present invention.

Detailed ways

For some application software on terminal devices, such as E-mail client, MMS client, Photo client, online games, etc., they all need to be configured with corresponding server IDs and user accounts, and some software also need to be configured with other Relevant parameters, such as points information in online games, etc. These software may not be downloaded to the terminal device through the DM server, but obtained by the user through other channels such as web sites or Portal; in addition, these software may also be downloaded to the terminal device through the DM server, but they are not installed. Configure related software parameters. Therefore, in these cases, it is necessary for the DM server to configure and modify relevant software parameters for these software on the terminal device.

The solution of the present invention is proposed to solve the above-mentioned problems. The main realization principles and specific realization methods of the present invention 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 software component parameter configuration method of the present invention, and its main realization process is as follows:

Step S10, the DM server delivers software component parameters to the terminal device;

Step S20, the terminal device configures the software component parameters issued by the DM server to the corresponding software components.

The software components mentioned here in the present invention specifically include 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. Many configurable items on terminal devices exist in the form of software components, such as user interface (skin, menu, desktop theme, wallpaper, etc.), functions (ringtones, video, camera, etc.), application software (chat software, album software, E-mail software, online games, etc.); these software components all require configuration parameters.

Wherein in the above step S10, the DM server can carry the pre-delivered software component parameters in the parameter configuration data packet and deliver it to the terminal device; the delivered parameter configuration data packet includes the software component identifier to which the software component parameters are to be configured, and the relative path to each software component parameter.

Based on this, the concrete realization process of above-mentioned step S20 can be as follows:

The terminal device finds the corresponding software component installation path according to the software component identification contained in the received parameter configuration data package;

The terminal device then configures the relative path of the software component parameter contained in the data packet according to the received parameter, thereby obtaining the absolute path of the software component parameter;

Finally, the terminal device writes the corresponding software component parameter value in the obtained absolute path of the software component parameter, so that the software component parameter can be configured to the corresponding software component.

In the above implementation manner, the configuration process of the software component parameters in the terminal device is not maintained by the DM Agent in the terminal device, but is maintained by the underlying firmware of the terminal device. Among them, DMAgent is the agent software running on the terminal device, which is responsible for interacting with the DM server, parsing and executing DM protocol commands, and maintaining each MO on the terminal device management tree; the underlying firmware is running on the terminal device platform software, similar to an operating system.

Please refer to Figure 2, which is a schematic diagram of the software component parameter configuration process in which the underlying firmware in the terminal device maintains the software component parameters in the method of the present invention, and its main implementation process is as follows:

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

Among them, for the software installed on the terminal equipment, the parameters to be configured are placed according to the predetermined relative path of the software provider. When the software provider sends the parameter configuration data package, the software parameters are arranged according to the predetermined relative path. That is, the parameter configuration data package includes a description table, which is used to describe the parameter values of each software respectively. The parameter values of each software described in the description table can be as follows: parameter value ./Soft ID/Server ID www.OMA.com ./Soft ID/IP address 10.0.0.0 ./Soft ID/User account User1 ... ...

Step 2: The DM server sends the received parameter configuration data packet to the DMAgent in the terminal device for processing.

Step 3: DM Agent forwards the parameter configuration data packet to the underlying firmware in the terminal device. The underlying firmware searches for the installation path of the software through the software identification, and then obtains the absolute value of the software parameters according to the relative path of the parameters in the above description table. Path, and write the corresponding parameter value in the description table into the corresponding parameter.

For example, the relative path of the parameters in the parameter configuration data packet received by DM Agent is ./SoftID/Server ID, and the underlying firmware finds the installation path of the software Soft ID, such as: System/Software/Soft ID, and the underlying firmware finds the installation path of the software Soft ID, for example: System/Software/Soft ID, and the underlying firmware finds the The absolute path of the parameter is obtained from the installation path and the relative path: System/Software/Soft ID/Server ID, and the corresponding parameter value www.OMA.com is written into the absolute path, thus achieving the purpose of parameter configuration.

Step 4: The application software invokes the corresponding software parameters configured by the underlying firmware.

The configured software parameters are maintained by the underlying firmware. The configured software parameters are similar to the registry information in the Windows operating system. The application software can obtain and use these configured software parameters from the underlying firmware.

Because in the terminal equipment, the application software is installed in the underlying firmware, in this way, the parameters are also maintained by the underlying firmware, which makes it easy for the software to use these configuration parameters. However, in this way, it is inconvenient for the DM server to configure the parameters of the software components, and the software provider must be required to provide a clear description of the parameters, so it is not convenient for the DM server to uniformly manage the parameter configuration of the software components.

Among them, the DM server in the above-mentioned step S10 can also send the pre-delivered software component parameters to the terminal device in the equipment management configuration file (OMA DM Profile); the issued device management configuration file contains the software component parameters to be configured. to the software component ID.

Based on this, in the above step S20, the terminal device can configure the software component parameters contained in the received device management configuration file to the corresponding software components according to the software component identifier contained in the received device management configuration file.

After the terminal device configures the software component parameters issued by the DM server to the corresponding software components in itself, it can further target the software component identification and each software component parameter contained in the received device management configuration file in its own DM Establish corresponding parameter configuration management objects (MO, Management Object) on the tree, so that the DM server can subsequently manage and control each parameter configuration management object in the terminal device, and realize the maintenance of corresponding software component parameters.

The device management configuration file issued by the DM server here contains a standard DM message package, which must be encoded into a Wireless Binary Extensible Markup Language (WBXML) format. The terminal device must also support the parameter configuration management object of the embedded WBXML coded device management tree, and the terminal device must support the <inbox> node (the <Inbox> node is the management node specified in the DM protocol, which is equivalent to an input cache. When the DM server adds a management tree node for a terminal device, it does not need to know the specific management node path. It can send the added node to this node <Inbox>, and the terminal device matches the corresponding management tree node according to the ID of the added node. position up).

When the terminal device supports the <inbox> node, the DM server can send the software component parameters to the <inbox> node of the terminal device through the Add command. Add the corresponding management node on the management tree. A node can be added through the <inbox> node, and a subtree can also be added. For example, the DM server adds the software component parameter subtree structure <Setting>/<Soft ID>, <Setting>/<Server>/<Receive Server>/<ServerID> to the DM management tree of the terminal device, which can be realized by the following command :

<Add>

<Item>

<Target>

<LocURI>./inbox/Setting/Soft ID</LocURI>

</Target>

<Data>E-mail client</Data>

</Item>

</Add>

<Add>

<Item>

<Target>

<LocURI>./inbox/Setting/<Server>/<Receive Server>/<ServerID></LocURI>

</Target>

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

</Item>

</Add>

After the terminal device receives the device management configuration file, the DM Agent on the terminal device transfers the node in the <inbox> to the corresponding path of the DM management tree according to the node ID, and reports this path to the DM server, so that the DM server can Manage later.

When the application software on the terminal device accesses the parameter configuration management object on the DM management tree, it can directly access the parameter configuration management object through the interface between the application software and the DM Agent; Mapping is provided between the software and the DM Agent, allowing the application software to indirectly access the corresponding parameter configuration management objects on the DM management tree.

Among the above-mentioned step S10, the DM server can also send the pre-delivered software component parameters to the terminal device in the client configuration file (OMA Client Provisioning Profile); The software component ID to which to configure.

Based on this, in the above step S20, the terminal device can configure the software component parameters contained in the received client configuration file to corresponding software components according to the software component identifier contained in the received client configuration file.

After the terminal device configures the software component parameters issued by the DM server to the corresponding software components in itself, it can further map the software component identification and each software component parameter contained in the received client configuration file to its own software component one by one. In the corresponding node on the DM tree, and establish a corresponding parameter configuration management object (MO) on each node mapped to; so that the DM server can subsequently manage and control each parameter configuration management object in the terminal device to realize Maintenance of the corresponding software component parameters.

The client configuration file delivered by the DM server here includes the application feature information of software component parameter configuration, which requires the terminal device to be able to identify and interpret the configuration parameters of each software component, and map the application feature information to the DM management tree The corresponding parameters are configured on the management object. For the identification of configuration parameters by the terminal device, a unified description of each software component parameter can be made in the Document Type Definition (DTD) document, so that the terminal device knows the specific meaning of each software component parameter issued by the DM server.

For example, the description of the parameters of each software component in the DTD document can be found in the following format:

Characteristic/parameter: APPLICATION/SOFT ID.--parameter name

Status: MUST.--status, must or optional

Occurs: 1/1.--Number of occurrences, 0 or 1, * means multiple times

Default value: None.--Default value, None

Used values: N/A.-- used value, no, Not Applicable

Interpretation: Soft Identity.--Explanation of this parameter

For the convenience of description, the description of the parameters of each software component can be expressed in the following table: Characteristic/parameter (application characteristic/parameter) Status Occurs Defaultvalues (default value) UsedValues (used values) Interpretation SOFT ID (software identification) Must (must) 1/1 None N/A (none) Soft identity (software identification) SERVER/SERVERNAME (server/server name) Must (must) 1/1 None N/A (none) Server name SERVER/SERVER ID (server/server ID) Must (must) 1/1 None N/A (none) Server identity SERVER/IP ADDRESS (server/IP address) Optional (required) 0/1 None N/A (none) IP address (IP address) USER ACCOUNT (user account) Must (must) 1/1 None N/A (none) User account (user account) PARAMETER/PARAMETER NAME (parameter/parameter name) Optional (required) 0/* None N/A (none) Parameter name PARAMETER/PARAMETER VALUE (parameter/parameter value) Optional (required) 0/* None N/A (none) Parameter value

Based on the above-mentioned DTD document, the DM server can deliver the client configuration file to the terminal device to configure software component parameters. For example, to set parameters such as receiving server, sending server, sending server port number and user account for the E-mail client, the main content of the delivered client configuration file is as follows:

#######

<characteristic type="APPLICATION">

<parm name="SOFT ID" value="E-mail client"/>

<parm name="SERVER/SERVER NAME" value="receive server"/>

<parm name="SERVER/SERVER ID" value="pop.huawei.com"/>

<parm name="SERVER/IP ADDRESS" value="10.0.0.0"/>

<parm name="SERVER/SERVER NAME" value="send server"/>

<parm name="SERVER/SERVER ID" value="smtp.huawei.com"/>

<parm name="SERVER/IP ADDRESS" value="10.0.1.0"/>

<parm name="USER ACCOUNT" value="user1"/>

<parm name="PARAMETER/PARAMETER NAME" value="send serverport"/>

<parm name="PARAMETER/PARAMETER VALUE" value="25"/>

</characteristic>

###END###

The terminal device maps the application feature information contained in the file to its own DM management tree according to the received client configuration file, and establishes corresponding parameter configuration management objects on the corresponding mapping nodes of the DM management tree. The mapping relationship between the application feature information contained in the client configuration file and the parameter configuration management object structure template on the terminal device can be shown in the following table: Application Characteristic Information Structure Template For Management Object (management object structure template) SOFT ID (software identification) Soft ID (software identification) SERVER/SERVER NAME (server/server name) Server/<X>/Server Name (server name) SERVER/SERVER ID (server/server ID) Server/<X>/Server ID (Server ID) SERVER/IP ADDRESS (server/IP address) Server/<X>/IP Address (IP address) USER ACCOUNT (user account) User account (user account) PARAMETER/PARAMETER NAME (parameter/parameter name) Parameter/<X>/Parameter Name (parameter name) PARAMETER/PARAMETER VALUE (parameter/parameter value) Parameter/<X>/Parameter Value (parameter value)

To sum up, the implementation of the DM server to deliver the configuration file (including the way to deliver the device management configuration file and the way to deliver the client configuration file) is generally used in the DM management tree of the terminal device and no related software components have been established. Parameters configure the case of managed objects (MOs). For example, if the user obtains the software through other channels (such as Web site or Portal, etc.), and does not store related software component parameter configuration management objects in the terminal device management tree, the DM server can carry the software in the configuration file delivered The relevant parameter information of the component, the terminal device then establishes the corresponding parameter configuration management object (MO) in its own DM management tree according to the software component parameter information contained in the configuration file received, such as ID (identification) management object, Name ( Name) management object, Version (version) management object, StateValue (state value) management object, EnvType (environment type) management object, etc., so that the DM server can configure the management object through the corresponding parameters in the DM management tree in the control terminal device, It is very convenient to manage the parameter configuration of each software component.

Correspondingly, the present invention also proposes a software component parameter configuration system, as shown in FIG. Including:

A parameter sending unit 101, configured to send software component parameters to the terminal device 20;

Terminal equipment 20 includes:

A parameter receiving unit 201, configured to receive the software component parameters delivered by the parameter delivery unit 101;

The parameter configuration unit 202 is configured to configure the software component parameters received by the parameter receiving unit 201 to its corresponding software components.

In addition, the terminal device 20 also includes a management object establishment unit 203 for establishing corresponding parameter configuration management objects 204 on its own DM management tree for the software component parameters received by the parameter receiving unit 201 . Correspondingly, the DM server 10 also includes:

The parameter maintenance unit 102 is configured to manage and control each parameter configuration management object 204 established by the management object establishment unit 203 in the terminal device 20, so as to realize maintenance of corresponding software component parameters.

Correspondingly, the present invention also proposes a terminal device, as shown in FIG. 4 , which is a schematic structural diagram of the main components of the terminal device of the present invention, and the terminal device 20 mainly includes:

A parameter receiving unit 201, configured to receive software component parameters issued by the DM server;

The parameter configuration unit 202 is configured to configure the software component parameters received by the parameter receiving unit 201 to corresponding software components.

In addition, the terminal device 20 of the present invention further includes a management object establishment unit 203 for establishing corresponding parameter configuration management objects on the terminal device management tree for the software component parameters received by the parameter receiving unit 201 .

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 (13)

1. A software component parameter configuration method, characterized in that, comprising steps: A. The device management server sends software component parameters to the terminal device; B. The terminal device configures the received software component parameters to corresponding software components. 2. The method according to claim 1, wherein in the step A, the device management server sends the software component parameters in the parameter configuration data packet to the terminal device; The parameter configuration data packet includes the software component identifier to which the software component parameters are to be configured, and the relative path of each software component parameter. 3. The method according to claim 2, wherein said step B specifically comprises the steps of: B1. The terminal device finds the corresponding software component installation path according to the software component identifier contained in the received parameter configuration data packet; and B2. Obtain the absolute path of the software component parameter according to the relative path of the software component parameter contained in the received parameter configuration data packet; and B3. Write the corresponding software component parameter value on the obtained absolute path of the software component parameter, so as to configure the software component parameter to the corresponding software component. 4. The method according to claim 1, wherein in the step A, the device management server sends the software component parameters in the configuration file to the terminal device; The configuration file includes software component identifiers to which software component parameters are to be configured. 5. The method according to claim 4, wherein in the step B, the terminal device configures the software component parameters contained in the received configuration file to the corresponding software components. 6. The method according to claim 5, wherein the configuration file is: Device Management Profile; or Client profile. 7. The method of claim 6, further comprising the step of: C. The terminal device establishes corresponding parameter configuration management objects on its own device management tree for the software component identification and each software component parameter contained in the received device management configuration file; D. The device management server then manages and controls each parameter configuration management object in the terminal device to maintain the parameters of the corresponding software components. 8. The method of claim 6, further comprising the step of: c. The terminal device maps the software component identification and each software component parameter contained in the received client configuration file to corresponding nodes on its own device management tree; and d. Establish a corresponding parameter configuration management object on each node mapped to; e. The device management server then manages and controls each parameter configuration management object in the terminal device to maintain the parameters of the corresponding software components. 9. A software component parameter configuration system, including a terminal device and a device management server, characterized in that, The device management server includes a parameter sending unit for sending software component parameters to the terminal device; The terminal device includes a parameter receiving unit configured to receive the software component parameters delivered by the parameter delivery unit; and A parameter configuration unit configured to configure the software component parameters received by the parameter receiving unit to corresponding software components. 10. The system according to claim 9, characterized in that, the terminal device further includes a parameter used for establishing corresponding parameter configuration management on its own device management tree for the software component parameters received by the parameter receiving unit Object's management object creation unit. 11. The system according to claim 10, characterized in that, the device management server further includes a device for managing and controlling each parameter configuration management object established by the management object establishment unit in the terminal device, so as to implement corresponding A parameter maintenance unit for maintaining software component parameters. 12. A terminal device, characterized by comprising: A parameter receiving unit for receiving software component parameters issued by the device management server; A parameter configuration unit configured to configure the software component parameters received by the parameter receiving unit to corresponding software components. 13. The terminal device according to claim 12, further comprising: A management object creation unit for creating corresponding parameter configuration management objects on the terminal device management tree for the software component parameters received by the parameter receiving unit.

Images