CN102348004A - Configuration method of service assembly, system and equipment thereof - Google Patents

Abstract

The invention discloses a configuration method of a service assembly, a system and equipment thereof. The method is characterized in that: a configuration server sends service assembly identifications which matches with a terminal type of a mobile terminal to the mobile terminal; the mobile terminal selects at least one service assembly identification from the service assembly identifications according to accrual service demand and downloads the service assembly corresponding to the selected identification on the configuration server so that the service assembly does not need to be configured in advance in the mobile terminal. Therefore, mobile terminal resource waste caused by installing the unused service assembly in the mobile terminal can be avoided.

Description

Method, system and device for configuring business components

technical field

The invention relates to the communication field, in particular to a service component preparation method, system and equipment.

Background technique

With the continuous development of communication technologies, more and more users wish to manage and configure services provided by mobile terminals they use. At present, a common way to manage services provided by mobile terminals is to dynamically configure service menus in the mobile terminal, and increase menu items available to users under limited resource consumption.

In the dynamic management of the above-mentioned service menu in the mobile terminal, the user still has limited control rights to the service components running inside the mobile terminal. Therefore, the prior art proposes a dynamic management solution for the service components inside the mobile terminal.

As shown in Figure 1, it is a schematic diagram of the internal structure of the current mobile terminal. It can be seen from Figure 1 that in the internal modules of the current mobile terminal, the operating system is located at the upper layer of the hardware device, and the upper layer of the operating system is the application layer. According to different configurations of mobile terminals, there are multiple sets of service components, such as service components for telephone services, service components for Fetion services, and so on.

When using the mobile terminal shown in Figure 1 to implement the dynamic management solution of the above service components, the service components in the running state can be stopped according to the actual needs of users or the resource occupation of the mobile terminal, or some running service components can be stopped. The business components of the mobile terminal make reasonable use of the software and hardware resources in the mobile terminal while satisfying the personalized needs of the users for the services provided by the business components.

In the above-mentioned dynamic management scheme of business components, the business components actually frequently used by users are only a small part of all business components of the mobile terminal, and unused business components installed inside the mobile terminal will occupy the storage space of the mobile terminal, and need to be These unused service components set call interfaces, wasting limited software and hardware resources in the mobile terminal.

Contents of the invention

Embodiments of the present invention provide a service component configuration method, system and equipment to solve the problem in the prior art that unused service components waste limited software and hardware resources in a mobile terminal.

A method for configuring a business component, the method comprising:

The configuration server receives the service component configuration request carrying the terminal type of the mobile terminal reported by the mobile terminal;

The configuration server selects a service component whose encapsulation type matches the terminal type from pre-saved service components, and sends the identifier of the selected service component to the mobile terminal;

After receiving the identification selected and reported by the mobile terminal from the identifications of the service components, the configuration server sends the service component corresponding to the received identification to the mobile terminal, instructing the mobile terminal to install the received service component.

A configuration server, the configuration server comprising:

A request receiving module, configured to receive a service component configuration request carrying the terminal type of the mobile terminal reported by the mobile terminal;

A selection module, configured to select a service component whose encapsulation type matches the terminal type from pre-saved service components;

An identification sending module, configured to send the identification of the selected service component to the mobile terminal;

The component sending module is configured to, after receiving the identifier selected and reported by the mobile terminal from the identifiers of the service components, send the service component corresponding to the received identifier to the mobile terminal, and instruct the mobile terminal to install the received service component components.

A mobile terminal, the mobile terminal comprising:

A request reporting module, configured to report a service component configuration request carrying the terminal type of the mobile terminal;

An identification receiving module, configured to receive an identification of a business component, where the encapsulation type of the business component corresponding to the identification of the business component matches the terminal type;

The component receiving module is used to select and report the identification from the received identification of the business component, and then receive the business component corresponding to the reported identification;

The installation module is used to install the received business components.

A system for configuring business components, the system comprising:

The mobile terminal is configured to report a service component configuration request carrying the terminal type of the mobile terminal, and receive an identifier of the service component, where the encapsulation type of the service component corresponding to the identifier of the service component matches the terminal type, and, from After selecting and reporting the identifiers from the received identifiers of the business components, receiving and installing the business components corresponding to the reported identifiers;

The configuration server is configured to receive the service component configuration request, select a service component whose encapsulation type matches the terminal type from pre-saved service components, and send the identifier of the selected service component to the mobile terminal, and After receiving the identifier selected and reported by the mobile terminal from the identifiers of the service components, sending the service component corresponding to the received identifier to the mobile terminal.

In the solution of the embodiment of the present invention, the configuration server sends the identifier of the service component matching the terminal type of the mobile terminal to the mobile terminal, and the mobile terminal selects at least one identifier of the service component according to actual service requirements, and downloads the identifier from the configuration server. The service component corresponding to the selected identification makes it unnecessary to pre-configure the service component inside the mobile terminal, avoiding the waste of mobile terminal resources caused by installing unused service components in the mobile terminal.

Description of drawings

FIG. 1 is a schematic diagram of the internal structure of a mobile terminal in the background technology;

Fig. 2 is a schematic diagram of the internal structure of the mobile terminal in the present invention;

FIG. 3 is a schematic flowchart of a method for configuring a service component in Embodiment 1 of the present invention;

FIG. 4 is a schematic diagram of the conversion relationship between the states of the service components in the mobile terminal in Embodiment 1 of the present invention;

FIG. 5 is a schematic structural diagram of a configuration server in Embodiment 2 of the present invention;

FIG. 6 is a schematic structural diagram of a mobile terminal in Embodiment 3 of the present invention.

Detailed ways

In order to save the software and hardware resources in the mobile terminal to the greatest extent, and meet the user's personalized needs for the services provided by the service components of the mobile terminal, the embodiment of the present invention improves the internal architecture of the mobile terminal, as shown in FIG. 2 , which is The improved internal structure diagram of the mobile terminal in the embodiment of the present invention can be seen from Figure 2. After the internal structure of the mobile terminal is improved, the operating system is no longer an application layer structure, but is designed as a service framework. state, there is no business component inside the mobile terminal, and the business component is encapsulated and stored in the configuration server on the network side. When the mobile terminal needs to run a certain business A series of operations such as , update, etc. download the business component from the configuration server, install it in the service container component, and use the software and hardware environment provided by the service container component to run the business component. Through the solution of the present invention, only the service components corresponding to the services required by the user need to be installed and run in the mobile terminal, and the service components that are not commonly used by the user may not be installed in the mobile terminal, which saves the limited resources of the mobile terminal. At the same time, the user The service components can be downloaded from the configuration server according to the actual needs, which meets the personalized needs of the users for the mobile terminal to provide services.

Embodiments of the present invention will be described in detail below in conjunction with the accompanying drawings.

The business components involved in the embodiment of the present invention include at least resource files, program files, signature files, and configuration description files, wherein: resource files include predefined pictures, text, etc., and program files include program elements required by the business component when it runs ; The configuration description file contains the function description and keywords of the business component; the signature file is the integrity signature of the resource file, program file, and configuration description file of the business component based on the integrity tool.

As shown in FIG. 3 , it is a schematic flowchart of a configuration method of a service component in Embodiment 1 of the present invention, and the method includes the following steps:

Step 101: The mobile terminal reports a service component configuration request to the configuration server, and the service component configuration request carries the terminal type of the mobile terminal.

Preferably, in order to enable the service components configured by the subsequent mobile terminal to run correctly in the mobile terminal, the service component configuration request further carries the capability information of the mobile terminal, which is used to represent the software and hardware capabilities of the mobile terminal, such as the CPU of the mobile terminal size, memory size, etc.

Before this step is executed, many sets of business components have been saved in the configuration server. Considering the various types of mobile terminals used by users, if the encapsulation type of each set of business components in the configuration server is the same, it may cause subsequent mobile terminal operations The system cannot correctly decapsulate the downloaded business components. Therefore, the configuration server first determines the various service contents, and then encapsulates each service content according to various encapsulation types. Each encapsulation type is related to a terminal type matches. The terminal type may be the operating system type of the mobile terminal.

For example: the service content determined by the configuration server is call service and Fetion service, and the preset mobile terminal operating system types are Symbian and Windows mobile, then the configuration server encapsulates the call service component and the Fetion service component that match Symbian respectively, and Encapsulate call service components and Fetion service components that match Windowsmobile.

Step 102: The configuration server selects a service component whose encapsulation type matches the terminal type from the pre-stored service components.

In this step, the business components encapsulated for different encapsulation types are stored in the configuration server, and are stored in the configuration server in the manner shown in Table 1.

Table 1

In the configuration server, the background space corresponding to a business component identifier of a certain encapsulation type stores various contents of the business component and environment requirements for running the business component.

After receiving the service component configuration request reported by the mobile terminal, the configuration server queries the encapsulation type that matches the terminal type according to the terminal type carried in it. If the encapsulation type 1 is found to be the matching encapsulation type, select encapsulation type 1 to proceed. The identification of each packaged business component.

Step 103: The configuration server selects a service component matching the capability information of the mobile terminal according to the capability information of the mobile terminal.

This step is a preferred step for realizing the purpose of the present invention. After selecting a suitable service component of the encapsulation type in step 102, further select a service component that the capability of the mobile terminal can support from the service components of the suitable encapsulation type, so that the mobile terminal Excellent software and hardware capabilities can support the correct operation of downloaded business components inside the mobile terminal.

Step 104: The configuration server sends the identifier of the selected service component to the mobile terminal.

In this step, the configuration server can display the identifiers of the service components sent to the mobile terminal to the mobile terminal in the form of a list, so that the user can clearly know the information of the service components currently available for the mobile terminal through the display screen of the mobile terminal. list.

In the solution of this embodiment, although the configuration server can encapsulate the service components according to different encapsulation types, the configuration server can issue the identifier of the service component to the outside through the same service component management interface.

Step 105: The mobile terminal selects at least one identifier from the received service component identifiers, and sends the selected identifier to the configuration server.

In this step, select the ID of the business component according to the actual business needs of the user.

Step 106: The configuration server sends the service component corresponding to the received identifier to the mobile terminal.

Step 107: The mobile terminal installs and runs the received service component.

In this step, the state set of the service component in the mobile terminal may at least include the following states: ready, running, paused, exited, and uninstalled. The transition relationship among the states is shown in FIG. 4 . Each state corresponds to two callback mechanisms to realize the initialization operation and destruction operation of the state. For example: the two callback functions of the ready state can be the onReady function and the leaveReady function, the onReady function is used to request the initialization of system resources for the ready state, and the leaveReady function is used to release the system resources when the ready state ends.

Step 108: The mobile terminal uninstalls the installed service components.

This step is an optimal step for realizing the purpose of the present invention, and can be executed at any time point in this embodiment. Its purpose is to unload service components not used by users in the mobile terminal, so as to release software and hardware resources in the mobile terminal.

In particular, because the business components saved in the configuration server may be updated (such as new business components are packaged and saved, or the contents of the original packaged business components change), therefore, the encapsulation type and the described When the service component matching the terminal type is updated, the configuration server sends the identifier of the updated service component to the mobile terminal, and after receiving the identifier selected and reported by the mobile terminal from the identifiers of the updated service component , sending the updated service component corresponding to the received identifier to the mobile terminal, instructing the mobile terminal to install the received updated service component.

Through the scheme of steps 101 to 108 above, only the service components corresponding to the services required by the user need to be installed and run in the mobile terminal, and the service components that are not frequently used by the user may not be installed in the mobile terminal, which saves the limited cost of the mobile terminal. At the same time, users can download business components from the configuration server according to actual needs, which meets the user's personalized needs for mobile terminals to provide services; and, according to the capability information of mobile terminals, select the service components that mobile terminals can run, so that mobile terminals The configured service components can run correctly in the mobile terminal; in addition, if the service components installed in the mobile terminal are no longer used in the short term, the service components can be uninstalled in the mobile terminal so that the mobile terminal is no longer used. Allocate any system resources for service components that are not used in a short period, and the service components in the configuration server can be updated in real time, ensuring that the mobile terminal can request service components that provide various services.

Embodiment two:

Embodiment 2 of the present invention also provides a configuration server under the same inventive concept as Embodiment 1. As shown in FIG. 5 , the configuration server includes a request receiving module 11, a selection module 12, an identification sending module 13 and a component sending module 14, wherein: the request receiving module 11 is used to receive the service component configuration request carrying the terminal type of the mobile terminal reported by the mobile terminal; the selection module 12 is used to select the encapsulation type from the pre-saved service components to match the terminal type the service component of the service component; the identification sending module 13 is used to send the identification of the selected service component to the mobile terminal; the component sending module 14 is used to receive the identification selected and reported by the mobile terminal from the identification of the service component Afterwards, the service component corresponding to the received identifier is sent to the mobile terminal, and the mobile terminal is instructed to install the received service component.

Further, the selection module 12 is further configured to further select the mobile terminal from the service components whose encapsulation type matches the terminal type according to the capability information of the mobile terminal when the service component configuration request carries the capability information of the mobile terminal. The service component that matches the capability information of the terminal.

In addition, the configuration server further includes an encapsulation module 15, configured to encapsulate each service component according to an encapsulation type matching the terminal type according to at least one preset terminal type.

When the service component whose encapsulation type matches the terminal type is updated, the identification sending module 13 is also used for sending the identification of the updated service component to the mobile terminal; the component sending module 14 is also used for receiving After the mobile terminal selects and reports the identifier from the identifiers of the updated service components, send the updated service component corresponding to the received identifier to the mobile terminal, instructing the mobile terminal to install the received updated service component components.

Embodiment three:

Embodiment 3 of the present invention also provides a mobile terminal under the same inventive concept as Embodiment 1. As shown in FIG. 6, the mobile terminal includes a request reporting module 21, an identification receiving module 22, a component receiving module 23 and an installation module 24, wherein: the request reporting module 21 is used to report the configuration request of the service component carrying the terminal type of the mobile terminal; the identification receiving module 22 is used to receive the identification of the service component, the encapsulation type of the service component corresponding to the identification of the service component Matching with the terminal type; the component receiving module 23 is used to select and report the identification from the received identification of the service component, and then receive the service component corresponding to the reported identification; the installation module 24 is used to install the received service component .

The mobile terminal also includes an uninstall module 25 for uninstalling installed service components.

In Fig. 2, the mobile terminal architecture involved in the embodiment of the present invention is preliminarily described. In this embodiment, each module of the mobile terminal is also a refinement of the mobile terminal architecture shown in Fig. 2, wherein: request reporting module 21, identification receiving module 22 1. The component receiving module 23 may be the content in the service agent component in FIG. 2 , and the installation module 24 and the uninstallation module 25 may be the content in the service container component in FIG. 2 .

Embodiment four:

Embodiment 4 of the present invention also provides a service component configuration system, including a mobile terminal and a configuration server, wherein: the mobile terminal is used to report a service component configuration request carrying the terminal type of the mobile terminal, and receive an identifier of the service component, The encapsulation type of the service component corresponding to the service component identifier matches the terminal type, and after selecting and reporting the identifier from the received identifiers of the service component, receiving and installing the service component corresponding to the reported identifier; The configuration server is configured to receive the service component configuration request, select a service component whose encapsulation type matches the terminal type from pre-saved service components, and send the identifier of the selected service component to the mobile terminal, and, After receiving the identifier selected and reported by the mobile terminal from the identifiers of the service components, the service component corresponding to the received identifier is sent to the mobile terminal.

The structure of the configuration server in this embodiment may be the structure of the configuration server involved in the second embodiment, and the structure of the mobile terminal in this embodiment may be the structure of the mobile terminal involved in the second embodiment.

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

1. A method for configuring a business component, characterized in that the method comprises: The configuration server receives the service component configuration request carrying the terminal type of the mobile terminal reported by the mobile terminal; The configuration server selects a service component whose encapsulation type matches the terminal type from pre-saved service components, and sends the identifier of the selected service component to the mobile terminal; After receiving the identification selected and reported by the mobile terminal from the identifications of the service components, the configuration server sends the service component corresponding to the received identification to the mobile terminal, instructing the mobile terminal to install the received service component. 2. The method according to claim 1, wherein the service component configuration request also carries capability information of the mobile terminal; After the configuration server selects the service component whose encapsulation type matches the terminal type, and before sending the identifier of the selected service component to the mobile terminal, the method further includes: According to the capability information of the mobile terminal, the configuration server further selects the service component matching the capability information of the mobile terminal from the service components whose encapsulation type matches the terminal type. 3. The method according to claim 1, wherein before the configuration server receives the service component configuration request, the method further comprises: According to at least one preset terminal type, the configuration server encapsulates each service component according to the encapsulation type matching the terminal type. 4. The method according to claim 1, wherein the business component includes at least the following: Resource files containing predefined images and text; A program file containing program elements required for the business component to run; Contains the functional description of the business component and the configuration specification file of keywords; A signature file for signing the resource file, the program file and the configuration specification file. 5. The method according to claim 1, wherein after the configuration server sends the service component to the mobile terminal, the method further comprises: When the service component whose encapsulation type matches the terminal type is updated, the configuration server sends the identifier of the updated service component to the mobile terminal; After receiving the identifier selected and reported by the mobile terminal from the identifiers of the updated service components, the configuration server sends the updated service component corresponding to the received identifier to the mobile terminal, instructing the mobile terminal to install the received Updated business components. 6. A configuration server, characterized in that, the configuration server includes: A request receiving module, configured to receive a service component configuration request carrying the terminal type of the mobile terminal reported by the mobile terminal; A selection module, configured to select a service component whose encapsulation type matches the terminal type from pre-saved service components; An identification sending module, configured to send the identification of the selected service component to the mobile terminal; The component sending module is configured to, after receiving the identifier selected and reported by the mobile terminal from the identifiers of the service components, send the service component corresponding to the received identifier to the mobile terminal, and instruct the mobile terminal to install the received service component components. 7. The configuration server according to claim 6, wherein: The selection module is further configured to further select the capability of the mobile terminal from the service components whose encapsulation type matches the terminal type according to the capability information of the mobile terminal when the service component configuration request carries the capability information of the mobile terminal Information matching business components. 8. The configuration server according to claim 6, wherein the configuration server further comprises: The encapsulation module is used for encapsulating each service component according to an encapsulation type matching the terminal type according to at least one preset terminal type. 9. The configuration server of claim 6, wherein: The identifier sending module is further configured to send the identifier of the updated service component to the mobile terminal when the service component whose encapsulation type matches the terminal type is updated; The component sending module is further configured to, after receiving the identifier selected and reported by the mobile terminal from the identifiers of the updated service components, send the updated service component corresponding to the received identifier to the mobile terminal, instructing the mobile terminal to The terminal installs the received updated service component. 10. A mobile terminal, characterized in that the mobile terminal comprises: A request reporting module, configured to report a service component configuration request carrying the terminal type of the mobile terminal; An identification receiving module, configured to receive an identification of a business component, where the encapsulation type of the business component corresponding to the identification of the business component matches the terminal type; The component receiving module is used to select and report the identification from the received identification of the business component, and then receive the business component corresponding to the reported identification; The installation module is used to install the received business components. 11. A configuration system for business components, characterized in that the system comprises: The mobile terminal is configured to report a service component configuration request carrying the terminal type of the mobile terminal, and receive an identifier of the service component, where the encapsulation type of the service component corresponding to the identifier of the service component matches the terminal type, and, from After selecting and reporting the identifiers from the received identifiers of the business components, receiving and installing the business components corresponding to the reported identifiers; The configuration server is configured to receive the service component configuration request, select a service component whose encapsulation type matches the terminal type from pre-saved service components, and send the identifier of the selected service component to the mobile terminal, and After receiving the identifier selected and reported by the mobile terminal from the identifiers of the service components, sending the service component corresponding to the received identifier to the mobile terminal.

Images