CN114880140A

CN114880140A - Component management method, device, electronic apparatus, storage medium, and program product

Info

Publication number: CN114880140A
Application number: CN202210473033.2A
Authority: CN
Inventors: 韩天助; 陈烨; 丁冲; 陈默涵
Original assignee: Industrial and Commercial Bank of China Ltd ICBC
Current assignee: Industrial and Commercial Bank of China Ltd ICBC
Priority date: 2022-04-29
Filing date: 2022-04-29
Publication date: 2022-08-09

Abstract

The present disclosure provides a component management method, which is applied to a terminal component on an equipment terminal, relates to the technical field of front-end development, and can be used in the financial field or other fields. The component management method comprises the following steps: detecting the update time of a component import file in a server; when the updating time of the component import file is not matched with the local cache, acquiring the component import file; acquiring a newly added service component and a first resource dependent protocol from a server according to the component import file; respectively storing the newly added service component and the first resource dependent protocol to a service component layer and a protocol layer; and responding to the first operation instruction, and configuring a first resource dependence protocol in the protocol layer into the application program layer, wherein the first resource dependence protocol is used for enabling the application program layer to carry out self-adaptive loading operation on the corresponding newly-added service component in the service component layer according to the first resource dependence protocol. The present disclosure also provides a component management apparatus, an electronic device, a storage medium, and a program product.

Description

Component management method, device, electronic apparatus, storage medium, and program product

Technical Field

The present disclosure relates to the field of front-end development, and may be applied to the field of finance or other fields, and in particular, to a component management method, apparatus, electronic device, storage medium, and program product.

Background

For component providers, customization ability is one of the important indicators for measuring the quality of components. A terminal component is provided at present, configured in a device terminal and embedded in an Application (APP), for providing functional support to the APP.

The termination component generally includes a plurality of components, and in traditional termination component, the component directly docks with the APP, results in having strong coupling nature between component and the APP. When one terminal component is multiplexed by a plurality of APPs, the conventional multiplexing technology enables the components in the terminal component to have the customized contents of the plurality of APPs at the same time, and the complexity of the components is high. At this time, if a user wants to customize new content for an APP, for example, add a new component, the user will move the whole body by pulling, not only the terminal components in the current APP need to be modified, but also the corresponding terminal components in all APPs need to be modified, which results in a large workload, a high customization cost and a low efficiency.

Disclosure of Invention

In view of the above, the present disclosure provides a component management method, apparatus, electronic device, storage medium, and program product.

According to a first aspect of the present disclosure, there is provided a component management method applied in a terminal component on a device terminal, wherein the terminal component includes an application layer, a protocol layer and a service component layer, the component management method includes:

detecting the update time of a component import file in a server;

when the updating time of the component import file is not matched with the local cache, acquiring the component import file;

acquiring a newly added service component and a first resource dependent protocol corresponding to the newly added service component from the server side according to the component import file;

storing the newly added service component to the service component layer, and storing the first resource dependent protocol to the protocol layer;

and responding to a first operation instruction, configuring a first resource dependence protocol matched with the first operation instruction in the protocol layer into the application program layer, wherein the first resource dependence protocol is used for enabling the application program layer to carry out self-adaptive loading operation on a newly added service component corresponding to the service component layer according to the first resource dependence protocol.

According to an embodiment of the present disclosure, the storing the newly added service component to the service component layer and the storing the first resource dependent protocol to the protocol layer includes:

locally registering the first resource-dependent protocol to store the first resource-dependent protocol to the protocol layer;

when the first resource dependency protocol is successfully registered locally, storing the newly added service component corresponding to the first resource dependency protocol to the service component layer;

and determining a first operation page of the newly added service component in the service component layer, and configuring a corresponding menu entry for the newly added service component in the first operation page.

According to an embodiment of the present disclosure, the configuring, in response to the first operation instruction, a first resource-dependent protocol in the protocol layer, which matches the first operation instruction, into the application layer includes:

and responding to a jump operation instruction sent by a user through the menu entry, and injecting the first resource-dependent protocol matched with the jump operation into the application program layer.

According to an embodiment of the present disclosure, the component management method further includes:

determining a component to be unloaded from the service component layer according to the component import file;

setting a second resource-dependent protocol matched with the component to be unloaded in the protocol layer to be forbidden;

setting the menu entry in the first operation page matching the disabled second resource-dependent protocol to be invisible.

According to an embodiment of the present disclosure, the first resource dependency protocol includes an initialization method and a resource calling method of the newly added service component, and the adaptive loading operation includes:

according to the initialization method, a second operation page is created for the newly added service component;

according to the resource calling method, configuring resources for the second operation page and automatically adapting to obtain a third operation page;

and jumping to the third operation page.

According to the embodiment of the present disclosure, the resource includes a basic component configured in a public service component library and a UI service component library, and the configuring and automatically adapting the resource for the second operation page according to the resource calling method includes:

determining at least one part of basic components from the public service component library and the UI service component library according to the resource calling method;

accessing the determined basic component to the second operation page;

and adjusting the basic component accessed into the second operation page according to the resource calling method so as to perform the adaptation.

According to the embodiment of the present disclosure, the resource further includes a composite component configured in a composite service component library, the composite component calls a basic component pre-configured in a common service component library and a UI service component library, and the resource is configured and automatically adapted for the second operation page according to the resource calling method, further including:

determining at least one composite component from the composite service component library according to the resource calling method;

accessing the determined composite component to the second operation page;

and adjusting the composite component accessed into the second operation page according to the resource calling method so as to carry out the adaptation.

A second aspect of the present disclosure provides a component management apparatus, applied to a terminal component on a device terminal, where the terminal component includes an application layer, a protocol layer, and a service component layer, the component management apparatus including:

the detection module is used for detecting the update time of the component import file in the server;

the first acquisition module is used for acquiring the component import file when the update time of the component import file is not matched with a local cache;

the second acquisition module is used for acquiring a newly added service component and a first resource dependency protocol corresponding to the newly added service component from the server side according to the component import file;

the first processing module is used for storing the newly added service component to the service component layer and storing the first resource dependent protocol to the protocol layer;

and the second processing module is used for responding to a first operation instruction, configuring a first resource dependence protocol matched with the first operation instruction in the protocol layer into the application program layer, wherein the first resource dependence protocol is used for enabling the application program layer to carry out self-adaptive loading operation on a newly added service component corresponding to the service component layer according to the first resource dependence protocol.

According to an embodiment of the present disclosure, the component management apparatus further includes:

the third processing module is used for determining a component to be unloaded from the business component layer according to the component import file;

the fourth processing module is used for setting a second resource-dependent protocol matched with the component to be unloaded in the protocol layer to be forbidden;

and the fifth processing module is used for setting the menu entry matched with the disabled second resource dependency protocol in the first operation page to be invisible.

A third aspect of the present disclosure provides an electronic device, comprising: one or more processors; a memory for storing one or more programs, wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to perform the component management method described above.

The fourth aspect of the present disclosure also provides a computer-readable storage medium having stored thereon executable instructions that, when executed by a processor, cause the processor to perform the above-described component management method.

A fifth aspect of the present disclosure also provides a computer program product comprising a computer program which, when executed by a processor, implements the component management method described above.

One or more of the above-described embodiments may provide the following advantages or benefits:

through the layering idea, the terminal component is divided into a service component layer and a protocol layer, so that a matched resource dependent protocol (namely, a first resource dependent protocol) can be configured for a newly added service component (namely, a newly added service component). When a user needs to use a function provided by a newly added service component in an APP, the embodiment of the disclosure can find out a corresponding resource-dependent protocol from a protocol layer, and configure the resource-dependent protocol to an application program layer, and the application program layer can automatically implement adaptive loading of the newly added service component according to the configured resource-dependent protocol. In this way, the service component realizes the bridge connection with the APP through the resource dependence protocol, and is not directly butted with the APP, so that the decoupling of the service component and the APP is realized. When one terminal component is multiplexed by a plurality of APPs, the service components in the terminal component do not need to have the customized contents of the plurality of APPs at the same time, and the complexity of the service components is simplified. On this basis, when customizing new content (for example, adding a new service component) for an APP, the embodiment of the present disclosure can automatically implement adaptive loading of a newly added service component according to the first resource-dependent protocol, thereby implementing customized configuration for the APP, and other APPs are not affected, thereby greatly reducing the workload of customization, saving the customization cost, and simultaneously, greatly improving the work efficiency.

Drawings

The foregoing and other objects, features and advantages of the disclosure will be apparent from the following description of embodiments of the disclosure, which proceeds with reference to the accompanying drawings, in which:

FIG. 1 schematically illustrates an application scenario diagram of a component management method, apparatus, electronic device, storage medium and program product according to an embodiment of the disclosure;

FIG. 2 schematically shows one of the flow diagrams of a component management method according to an embodiment of the present disclosure;

FIG. 3 schematically illustrates a flow diagram for storing a newly added business component and a first resource dependent protocol to a business component layer and a protocol layer, respectively, in accordance with an embodiment of the disclosure;

FIG. 4 schematically illustrates a flow diagram for configuring a first resource dependent protocol into an application layer, in accordance with an embodiment of the present disclosure;

FIG. 5 schematically illustrates a second flow chart of a component management method according to an embodiment of the present disclosure;

FIG. 6 schematically illustrates a flow diagram of an adaptive load operation according to an embodiment of the present disclosure;

FIG. 7a schematically shows one of the flow diagrams of automatic adaptation according to an embodiment of the present disclosure;

FIG. 7b schematically illustrates a second flow chart of automatic adaptation according to an embodiment of the present disclosure;

fig. 8 schematically shows a block diagram of the structure of a component management apparatus according to an embodiment of the present disclosure;

fig. 9 schematically shows a block diagram of an electronic device adapted to implement a component management method according to an embodiment of the present disclosure.

Detailed Description

Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. It should be understood that these descriptions are illustrative only and are not intended to limit the scope of the present disclosure. In the following detailed description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the disclosure. It may be evident, however, that one or more embodiments may be practiced without these specific details. Moreover, in the following description, descriptions of well-known structures and techniques are omitted so as to not unnecessarily obscure the concepts of the present disclosure.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. The terms "comprises," "comprising," and the like, as used herein, specify the presence of stated features, steps, operations, and/or components, but do not preclude the presence or addition of one or more other features, steps, operations, or components.

All terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art unless otherwise defined. It is noted that the terms used herein should be interpreted as having a meaning that is consistent with the context of this specification and should not be interpreted in an idealized or overly formal sense.

Where a convention analogous to "at least one of A, B and C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B and C" would include but not be limited to systems that have a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.).

It should be noted that the component management method, apparatus, electronic device, storage medium, and program product provided by the present disclosure relate to the field of front-end development technology. The component management method, the device, the electronic device, the storage medium and the program product provided by the embodiment of the disclosure can be applied to the financial field or any field except the financial field, for example, the component management method, the device, the electronic device, the storage medium and the program product provided by the embodiment of the disclosure can be applied to front-end development business in the financial field. The present disclosure does not limit the application fields of the component management method, apparatus, electronic device, storage medium, and program product.

In the technical scheme of the disclosure, the collection, storage, use, processing, transmission, provision, disclosure, application and other processing of the personal information of the related user are all in accordance with the regulations of related laws and regulations, necessary confidentiality measures are taken, and the customs of the public order is not violated.

The embodiment of the disclosure provides a component management method, which is applied to a terminal component on an equipment terminal, wherein the terminal component comprises an application program layer, a protocol layer and a service component layer, and the component management method comprises the following steps: detecting the update time of a component import file in a server; when the updating time of the component import file is not matched with the local cache, acquiring the component import file; acquiring a newly added service component and a first resource dependence protocol corresponding to the newly added service component from a server according to first configuration information in a component import file; storing the newly added service component to a service component layer, and storing the first resource dependence protocol to a protocol layer; and responding to the first operation instruction, and configuring a first resource dependence protocol matched with the first operation instruction in the protocol layer into the application program layer, wherein the first resource dependence protocol is used for enabling the application program layer to carry out loading operation on a newly added service component corresponding to the service component layer according to the first resource dependence protocol.

In the embodiment of the present disclosure, through a layering idea, the terminal component is split into the service component layer and the protocol layer, so that a matched resource dependent protocol (i.e., a first resource dependent protocol) can be configured for a newly added service component (i.e., a newly added service component). When a user needs to use a function provided by a newly added service component in an APP, the embodiment of the disclosure may find a corresponding resource dependency protocol from a protocol layer, and configure the resource dependency protocol to an application layer, and the application layer may automatically implement adaptive loading of the newly added service component according to the configured resource dependency protocol. In this way, the service component realizes the bridge connection with the APP through the resource dependence protocol, and is not directly butted with the APP, so that the decoupling of the service component and the APP is realized. When one terminal component is multiplexed by a plurality of APPs, the service components in the terminal component do not need to have the customized contents of the plurality of APPs at the same time, and the complexity of the service components is simplified. On this basis, when customizing new content (for example, adding new business component) for an APP, the embodiment of the present disclosure can automatically implement adaptive loading of the newly added business component according to the first resource-dependent protocol, thereby implementing customized configuration for the APP, and other APPs are not affected, thereby greatly reducing the workload of customization, saving the customization cost, and simultaneously, greatly improving the work efficiency.

Fig. 1 schematically illustrates an application scenario diagram of a component management method, apparatus, electronic device, storage medium, and program product according to an embodiment of the present disclosure.

As shown in fig. 1, the application scenario 100 according to this embodiment may include

device terminals

101, 102, 103, a network 104 and a server 105. The network 104 serves to provide a medium for communication links between the

device terminals

101, 102, 103 and the server 105. Network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few.

The user may use the

device terminals

101, 102, 103 to interact with the server 105 over the network 104 to receive or send messages or the like. Various communication client applications, such as shopping applications, web browser applications, search applications, instant messaging tools, mailbox clients, social platform software, etc. (by way of example only) may be installed on the

device terminals

101, 102, 103.

The

device terminals

101, 102, 103 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, and the like.

The server 105 may be a server that provides various services, such as a background management server (for example only) that provides support for websites browsed by users using the

device terminals

101, 102, 103. The background management server may analyze and perform other processing on the received data such as the user request, and feed back a processing result (e.g., a webpage, information, or data obtained or generated according to the user request) to the device terminal.

It should be noted that the component management method provided by the embodiments of the present disclosure may be generally executed by the

device terminals

101, 102, and 103. Accordingly, the component management apparatus provided by the embodiments of the present disclosure may be generally disposed in the

device terminals

101, 102, 103.

It should be understood that the number of device terminals, networks and servers in fig. 1 is merely illustrative. There may be any number of device terminals, networks, and servers, as desired for implementation.

The component management method of the embodiment of the disclosure is applied to an equipment terminal, and particularly, the component management method is applied to a terminal component on the equipment terminal so as to manage components in the terminal component, and the terminal component can be embedded in an APP so as to provide functional support for the APP. For example, the terminal member may include a pass member, and the components in the pass member may include an account management component, an authentication component, and the like.

Optionally, the component management method in the embodiment of the present disclosure may be specifically used for managing addition and removal of components in a terminal component, so as to implement a terminal component capable of being quickly plugged (adding components) and unplugged (removing components) according to customization needs. The component management method of the disclosed embodiment will be described in detail below with reference to fig. 2 to 7b based on the scenario described in fig. 1.

Fig. 2 schematically shows one of flowcharts of a component management method according to an embodiment of the present disclosure, and as shown in fig. 2, the component management method of this embodiment includes steps S210 to S250, it should be noted that, although the steps in fig. 2 are shown in sequence as indicated by arrows, the steps are not necessarily executed in sequence as indicated by the arrows. The steps are not performed in the exact order shown and may be performed in other orders unless explicitly stated herein. Moreover, at least some of the steps in the figures may include multiple sub-steps or multiple stages that are not necessarily performed at the same time, but may be performed at different times, in different orders, and may be performed in turn or in alternation with other steps or at least some of the sub-steps or stages of other steps.

In the disclosed embodiment, the terminal component includes an application layer for interfacing with the APP, a protocol layer for configuring a resource-dependent protocol to be mentioned below, and a service component layer for configuring a service component to be mentioned below.

In step S210, the update time of the component import file in the server is detected.

In step S220, when the update time of the component import file does not match the local cache, the component import file is acquired.

In the embodiment of the present disclosure, the server is configured with a component library, and when new content needs to be customized for a terminal component in the device terminal, for example, a new component (for example, a new service component hereinafter) is added, the new component may be uploaded to the component library of the server, and a corresponding component import (podfile) file is modified, so as to increase the import of the new component and modify the update time of the component import file.

It should be noted that, when the update time of the component import file matches the local cache, the component import file is not changed, and the current state may be maintained at this time.

Optionally, when the APP in the device terminal is started, the update time of the component import file in the server may be detected, and when the update time of the component import file is not matched with the local cache in the device terminal, it may be determined that the component import file changes, and at this time, the component import file may be obtained through step S220.

In step S230, the newly added service component and the first resource-dependent protocol corresponding to the newly added service component are obtained from the server according to the component import file.

In the embodiment of the present disclosure, a newly added service component may refer to a newly added service component. Business components can include components that can implement a business function. For example, the terminal component may provide functional support for a class of services to the APP, while the service component may be used to implement one of the service functions. The component import file may include business components that are imported into the terminal member. When the update time of the component import file changes, the service components introduced into the component import file are changed, and the newly added service components can be determined by analyzing which service components are introduced into the component import file, that is, the newly added service components are determined. The first resource-dependent protocol may be a resource-dependent protocol matched with a newly added service component, and the resource-dependent protocol may implement bridging between the service component and the APP, thereby implementing decoupling between the service component and the APP. The first resource dependent protocol may include customized content for the APP by the business component, such as resource invocation methods and initialization methods, among others.

In step S240, the newly added service component is stored in the service component layer, and the first resource-dependent protocol is stored in the protocol layer.

In step S250, in response to the first operation instruction, a first resource-dependent protocol in the protocol layer, which is matched with the first operation instruction, is configured in the application layer, where the first resource-dependent protocol is used to enable the application layer to perform an adaptive loading operation on a newly added service component corresponding to the service component layer according to the first resource-dependent protocol.

In the embodiment of the present disclosure, the first resource dependency protocol may include an initialization method and a resource calling method of the service component. The first operation instruction may include a jump operation instruction issued by a user for using a function provided by the newly added service component, and the load operation may load the newly added service component to implement display of a corresponding operation page, and the like. For example, when the user wants to use the "life payment" function, the instruction sent by the user to jump to the "life payment" is the first operation instruction, and the loading of the "life payment" component to show that the "life payment" operation page is the loading operation. The adaptive loading operation may refer to a method for implementing a custom loading manner of the newly added service component, such as a resource calling logic, a page color, a page size, and the like, by using an initialization method and a resource calling method in the first resource dependency protocol, which will be specifically described in detail below and will not be described herein again.

In the embodiment of the present disclosure, through a layering idea, the terminal component is split into the service component layer and the protocol layer, so that a matched resource dependent protocol (i.e., a first resource dependent protocol) can be configured for a newly added service component (i.e., a newly added service component). As described above, the first resource-dependent protocol may include, for example, an initialization method and a resource calling method of a service component, and when a user needs to use a function provided by a newly added service component in an APP, an embodiment of the present disclosure may find a corresponding resource-dependent protocol from a protocol layer and configure the resource-dependent protocol to an application layer, where the application layer may automatically implement adaptive loading of the newly added service component according to the configured resource-dependent protocol.

Therefore, the service component realizes bridging with the APP through the resource dependence protocol instead of directly butting with the APP, so that the decoupling of the service component and the APP is realized. When one terminal component is multiplexed by a plurality of APPs, the service components in the terminal component do not need to have the customized contents of the plurality of APPs at the same time, and the complexity of the service components is simplified. On this basis, when customizing new content (for example, adding new business component) for an APP, the embodiment of the present disclosure can automatically implement adaptive loading of the newly added business component according to the first resource-dependent protocol, thereby implementing customized configuration for the APP, and other APPs are not affected, thereby greatly reducing the workload of customization, saving the customization cost, and simultaneously, greatly improving the work efficiency.

The component management method according to the embodiment of the present disclosure is further described below with reference to fig. 2 to 7 b.

Fig. 3 schematically illustrates a flowchart of storing a newly added service component and a first resource-dependent protocol to a service component layer and a protocol layer, respectively, according to an embodiment of the present disclosure, and as shown in fig. 3, in some specific embodiments, step S240 includes steps S241 to S243.

In step S241, the first resource-dependent protocol is locally registered to store the first resource-dependent protocol to the protocol layer.

In the embodiment of the present disclosure, the first resource dependent protocol may be locally registered in real time, or a plurality of first resource dependent protocols may be locally registered in batch according to a preset period.

In step S242, when the first resource-dependent protocol is successfully registered locally, the newly added service component corresponding to the first resource-dependent protocol is stored in the service component layer.

In the embodiment of the present disclosure, when the first resource-dependent protocol fails to register locally, at least one retry operation may be initiated, and when multiple retry operations still fail, the corresponding newly added service component may be removed, or the corresponding newly added service component may be stored in the standby component library, and generate corresponding prompt information to notify that the local registration fails.

Optionally, when the local registration fails, the failure reason may be analyzed, and a corresponding analysis report may be generated according to the failure reason.

Optionally, when the corresponding newly added service component is stored in the standby component library, the registration may be performed manually.

In step S243, a first operation page of the newly added service component in the service component layer is determined, and a corresponding menu entry is configured for the newly added service component in the first operation page.

In this embodiment of the present disclosure, the newly added service component may correspond to an operation page for visualizing functions that can be implemented by the newly added service component, for example, a second operation page that will be mentioned below, and the first operation page may be a top-level page of the second operation page. The first operation page may have a plurality of menu entries of the service components deployed therein, and different first operation pages may have different menu entries of the service components deployed therein. The menu entry may include an operation interface capable of performing a jump to an operation page corresponding to the newly added service component.

For example, the first operation page is configured with a menu entry B1, a menu entry B2, and a menu entry B3 corresponding to the service component a1, the service component a2, and the service component A3, respectively, where the service component A3 may be a newly added service component, and the menu entry B3 is a newly configured menu entry according to the service component A3. The user can jump to the operating page of service component a1 via menu entry B1, to the operating page of service component a2 via menu entry B2, and to the operating page of service component A3 via menu entry B3.

In some specific embodiments, the first operation instruction includes a jump operation instruction issued by the user through the menu entry, and fig. 4 schematically illustrates a flowchart of configuring the first resource-dependent protocol into the application layer according to an embodiment of the present disclosure, as shown in fig. 4, step S250 includes step S251.

In step S251, in response to a jump operation instruction issued by a user through a menu entry, a first resource-dependent protocol matching the jump operation is injected into the application layer.

In this embodiment of the present disclosure, after the newly added service component and the first resource dependent protocol are obtained, the newly added service component and the first resource dependent protocol may be stored in the service component layer and the resource dependent protocol layer, respectively, and a menu entry may be configured for the newly added service component. And then, when a user sends a jump operation instruction for jumping to the newly added service component through the menu entry, injecting a corresponding first resource dependence protocol into the application program layer in an injection mode, thereby realizing the rapid configuration of the first resource dependence protocol for the application program layer to execute subsequent self-adaptive loading operation and the like.

Fig. 5 schematically illustrates a second flowchart of a component management method according to an embodiment of the present disclosure, and as shown in fig. 5, in some specific embodiments, the component management method further includes step S310 to step S330.

In step S310, a component to be uninstalled is determined from the business component layer according to the component import file.

In the embodiment of the present disclosure, the component import file is configured with the service component imported into the terminal component, and when the update time of the component import file changes, it indicates that the service component imported into the component import file has changed, and besides the adding of the service component mentioned in the foregoing, the change of the service component also includes a case that the imported service component is reduced, that is, a case that it is desired to uninstall the corresponding service component in the terminal component. By analyzing which business components are introduced into the component introduction file, the component to be unloaded, namely the business component which is expected to be unloaded, can be determined.

In step S320, the second resource-dependent protocol in the protocol layer matching the component to be deleted is set to be disabled.

In step S330, the menu entry in the first operation page that matches the disabled second resource-dependent protocol is set to be invisible.

In the embodiment of the present disclosure, the second resource-dependent protocol may refer to a resource-dependent protocol corresponding to a service component to be offloaded, for example, for the service component a1, the first resource-dependent protocol and the second resource-dependent protocol may be the same protocol, and in the embodiment of the present disclosure, in order to distinguish between adding and offloading processes of the service component, the protocols are referred to as the first resource-dependent protocol and the second resource-dependent protocol, respectively.

In the embodiment of the present disclosure, when it is detected that the second resource-dependent protocol is disabled, the corresponding menu entry is set to be invisible, so that the user cannot access the menu entry, and when the service component is restarted to be enabled, the disabled second resource-dependent protocol may be set to be "enabled", and at this time, the menu entry may be set to be visible, so as to implement convenient uninstallation and re-addition.

In some specific embodiments, the first resource dependency protocol includes an initialization method and a resource calling method of a new service component, and fig. 6 schematically illustrates a flowchart of an adaptive loading operation according to an embodiment of the present disclosure, where, as shown in fig. 6, the adaptive loading operation includes steps S410 to S430.

In step S410, according to the initialization method, a second operation page is created for the newly added service component.

In this disclosure, the second operation page may refer to an operation page for implementing a function of a newly added service component. Alternatively, the terminal component may be implemented based on an object-oriented technology, and in step S410, based on an initialization method in the first resource-dependent protocol, operations such as initializing data in the newly added service component to a required format and allocating an address in a memory may be performed through the object-oriented technology to obtain the second operation page.

In step S420, according to the resource calling method, resources are configured for the second operation page and adaptation is automatically performed, so as to obtain a third operation page.

In the embodiment of the present disclosure, the resource calling method may include customized content for the APP, for example, a resource that needs to be called by the service component, a calling logic of the resource, a showing manner of the resource, and the like. Through automatic adaptation, automatic access of resources and adaptive adjustment according to customized content can be achieved, and therefore the final operation page of the newly added service component, namely the third operation page, is obtained.

In some specific embodiments, the resource is included in a basic component configured in a common service component library and a UI service component library, fig. 7a schematically shows one of the flow charts of automatic adaptation according to the embodiment of the present disclosure, as shown in fig. 7a, step S420 includes steps S421 to S423.

In step S421, at least a part of the basic components are determined from the common service component library and the UI service component library according to the resource calling method.

In the embodiment of the present disclosure, the basic component includes a component for providing basic functions to the business component, for example, the business component may include a "life payment" component, and the basic component on which the "life payment" component depends may include a "log record" component, a "picture processing" component, a "data parsing" component, and the like. Besides, the basic components in the public service component library can also comprise a buried point component, a network request component, an encryption and decryption component, a performance monitoring component and the like; the basic components in the UI service component library may also include rich text components, button components, dialog components, input box components, checkbox components, switch slider components, sliding components, and the like. The configuration of the basic components can be determined according to actual needs, and is not listed here.

In step S422, the determined basic component is accessed to the second operation page.

In step S423, the basic component accessed to the second operation page is adjusted according to the resource calling method to perform adaptation.

For example, the skin and size of the business component and the logical relationship between the basic components called by the business component can be adjusted according to the resource calling method, for example, the basic component X is called first and then the basic component Y is called; or, after the basic component X satisfies a certain condition, the basic component Y is called, and the like, which may be determined according to actual needs, and is not limited herein. By the resource calling method, low coupling connection between each component and the basic component can be realized, the dependence degree between the service component and the service component is reduced, and quick, simple and convenient addition and unloading are facilitated.

In some specific embodiments, the resource further includes a composite component configured in a composite service component library, the composite component calls a base component pre-configured in the common service component library and the UI service component library, fig. 7b schematically illustrates a second flow chart of automatic adaptation according to an embodiment of the disclosure, as shown in fig. 7b, and step S420 further includes step S424 to step S427.

At step S424, at least one composite component is determined from the composite service component library according to the resource calling method.

In embodiments of the present disclosure, the composite component may invoke at least two base components, for example, the composite component may include a face recognition component, a voiceprint recognition component, a handwritten signature component, and the like. The configuration of the composite component can be determined according to actual needs, and is not listed here.

And in step S425, accessing the determined composite component to a second operation page.

In step S426, the composite component accessed to the second operation page is adjusted according to the resource calling method to perform adaptation.

For example, the calling mode and the displaying mode of the composite component may be adjusted according to the resource calling method, and the like, which may be determined according to actual needs, and is not limited herein. Through the resource calling method, low coupling connection between each service component and the rechecking component can be realized, and quick, simple and convenient addition and unloading are facilitated.

In some embodiments, in a terminal component, lateral dependencies between business components are prohibited.

In step S430, jump to the third operation page to complete the corresponding display.

By adopting the module management method of the embodiment of the disclosure, for APP, the terminal component embedded therein realizes decoupling of the service module and the APP through the resource dependence protocol, so that the terminal component only contains the customized content for the APP and the basic module depending on the customized content, and further, the volume of the installation package is effectively reduced, the code coupling degree is reduced, the code execution efficiency is improved, and then, the system is more stable in operation, the service requirement fast iteration is satisfied, and the research and development efficiency is improved. Customization complexity is reduced for component providers, thereby enhancing reusability while also reducing subsequent maintenance costs. Moreover, the adding and the unloading of the service components are quick and convenient, so that a terminal component which can be quickly plugged (added with the service components) and pulled (unloaded with the service components) can be realized, and development of an APP which has good flexibility and is convenient to maintain is facilitated.

Based on the component management method, the disclosure also provides a component management device. The apparatus will be described in detail below with reference to fig. 8.

Fig. 8 schematically shows a block diagram of a component management apparatus according to an embodiment of the present disclosure, and as shown in fig. 8, a component management apparatus 800 of this embodiment is applied to a terminal component on a device terminal, where the terminal component includes an application layer, a protocol layer, and a service component layer, and the component management apparatus 800 of this embodiment includes a detection module 810, a first obtaining module 820, a second obtaining module 830, a first processing module 840, and a second processing module 850.

The detecting module 810 is used for detecting the update time of the component import file in the server. In an embodiment, the detecting module 810 may be configured to perform the step S210 described above, which is not described herein again.

The first obtaining module 820 is configured to obtain the component import file when the update time of the component import file does not match the local cache. In an embodiment, the first obtaining module 820 may be configured to perform the step S220 described above, which is not described herein again.

The second obtaining module 830 is configured to obtain, from the server, the newly added service component and the first resource dependency protocol corresponding to the newly added service component according to the component import file. In an embodiment, the second obtaining module 830 may be configured to perform the step S230 described above, and is not described herein again.

The first processing module 840 is configured to store the newly added service component to the service component layer, and store the first resource-dependent protocol to the protocol layer. In an embodiment, the first processing module 840 may be configured to perform the step S240 described above, which is not described herein again.

The second processing module 850 is configured to, in response to the first operation instruction, configure a first resource-dependent protocol, which is matched with the first operation instruction, in the protocol layer into the application program layer, where the first resource-dependent protocol is used to enable the application program layer to perform an adaptive loading operation on a newly added service component corresponding to the service component layer according to the first resource-dependent protocol. In an embodiment, the second processing module 850 may be configured to perform the step S250 described above, which is not described herein again.

Therefore, the service component realizes the bridging with the APP through the resource dependence protocol instead of directly butting with the APP, thereby realizing the decoupling of the service component and the APP. When one terminal component is multiplexed by a plurality of APPs, the service components in the terminal component do not need to have the customized contents of the plurality of APPs at the same time, and the complexity of the service components is simplified. On this basis, when customizing new content (for example, adding new business component) for an APP, the embodiment of the present disclosure can automatically implement adaptive loading of the newly added business component according to the first resource-dependent protocol, thereby implementing customized configuration for the APP, and other APPs are not affected, thereby greatly reducing the workload of customization, saving the customization cost, and simultaneously, greatly improving the work efficiency.

According to an embodiment of the present disclosure, any plurality of the detection module 810, the first obtaining module 820, the second obtaining module 830, the first processing module 840, and the second processing module 850 may be combined into one module to be implemented, or any one of them may be split into a plurality of modules. Alternatively, at least part of the functionality of one or more of these modules may be combined with at least part of the functionality of the other modules and implemented in one module. According to an embodiment of the present disclosure, at least one of the detection module 810, the first obtaining module 820, the second obtaining module 830, the first processing module 840 and the second processing module 850 may be implemented at least partially as a hardware circuit, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or may be implemented in hardware or firmware in any other reasonable manner of integrating or packaging a circuit, or in any one of three implementations of software, hardware and firmware, or in a suitable combination of any several of them. Alternatively, at least one of the detection module 810, the first acquisition module 820, the second acquisition module 830, the first processing module 840 and the second processing module 850 may be at least partially implemented as a computer program module, which when executed may perform the corresponding functions.

In some embodiments, the component management apparatus further includes: the device comprises a third processing module, a fourth processing module and a fifth processing module.

And the third processing module is used for determining the component to be unloaded from the business component layer according to the component import file.

And the fourth processing module is used for setting the second resource dependence protocol matched with the component to be unloaded in the protocol layer to be forbidden.

And the fifth processing module is used for setting the menu entry matched with the forbidden second resource dependency protocol in the first operation page to be invisible.

Adopt this assembly management device of this disclosed embodiment, to APP, the terminal component that is embedded wherein has realized the decoupling zero of business subassembly and APP through the resource dependence agreement to make only contain the basic subassembly to this APP's customization content and its dependence in the terminal component, and then, effectively reduced the volume of installation package, reduced the code coupling degree, improved code execution efficiency, then, make the system operation more firm, satisfy the quick iteration of business demand, promoted research and development efficiency. Customization complexity is reduced for component providers, thereby enhancing reusability while also reducing subsequent maintenance costs. Moreover, the adding and the unloading of the service components are quick and convenient, so that a terminal component which can be quickly plugged (added with the service components) and pulled (unloaded with the service components) can be realized, and development of an APP which has good flexibility and is convenient to maintain is facilitated.

Fig. 9 schematically shows a block diagram of an electronic device adapted to implement a component management method according to an embodiment of the present disclosure, and as shown in fig. 9, an electronic device 900 according to an embodiment of the present disclosure includes a processor 901 which can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM)902 or a program loaded from a storage portion 908 into a Random Access Memory (RAM) 903. Processor 901 may comprise, for example, a general purpose microprocessor (e.g., a CPU), an instruction set processor and/or associated chipset, and/or a special purpose microprocessor (e.g., an Application Specific Integrated Circuit (ASIC)), among others. The processor 901 may also include on-board memory for caching purposes. The processor 901 may comprise a single processing unit or a plurality of processing units for performing the different actions of the method flows according to embodiments of the present disclosure.

In the RAM 903, various programs and data necessary for the operation of the electronic apparatus 900 are stored. The processor 901, the ROM 902, and the RAM 903 are connected to each other through a bus 904. The processor 901 performs various operations of the method flows according to the embodiments of the present disclosure by executing programs in the ROM 902 and/or the RAM 903. Note that the programs may also be stored in one or more memories other than the ROM 902 and the RAM 903. The processor 901 may also perform various operations of the method flows according to embodiments of the present disclosure by executing programs stored in the one or more memories.

Electronic device 900 may also include input/output (I/O) interface 905, input/output (I/O) interface 905 also connected to bus 904, according to an embodiment of the present disclosure. The electronic device 900 may also include one or more of the following components connected to the I/O interface 905: an input portion 906 including a keyboard, a mouse, and the like; an output section 907 including components such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage portion 908 including a hard disk and the like; and a communication section 909 including a network interface card such as a LAN card, a modem, or the like. The communication section 909 performs communication processing via a network such as the internet. The drive 910 is also connected to the I/O interface 905 as necessary. A removable medium 911 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 910 as necessary, so that a computer program read out therefrom is mounted into the storage section 908 as necessary.

The present disclosure also provides a computer-readable storage medium, which may be contained in the apparatus/device/system described in the above embodiments; or may exist separately and not be assembled into the device/apparatus/system. The above-described computer-readable storage medium carries one or more programs which, when executed, implement a component management method according to an embodiment of the present disclosure.

According to embodiments of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, which may include, for example but is not limited to: a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. For example, according to embodiments of the present disclosure, a computer-readable storage medium may include the ROM 902 and/or the RAM 903 described above and/or one or more memories other than the ROM 902 and the RAM 903.

Embodiments of the present disclosure also include a computer program product comprising a computer program containing program code for performing the method illustrated in the flow chart. When the computer program product runs in a computer system, the program code is used for causing the computer system to realize the component management method provided by the embodiment of the disclosure.

The computer program performs the above-described functions defined in the system/apparatus of the embodiments of the present disclosure when executed by the processor 901. The systems, apparatuses, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the present disclosure.

In one embodiment, the computer program may be hosted on a tangible storage medium such as an optical storage device, a magnetic storage device, or the like. In another embodiment, the computer program may also be transmitted, distributed in the form of a signal on a network medium, and downloaded and installed through the communication section 909 and/or installed from the removable medium 911. The computer program containing program code may be transmitted using any suitable network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the foregoing.

In such an embodiment, the computer program may be downloaded and installed from a network through the communication section 909, and/or installed from the removable medium 911. The computer program, when executed by the processor 901, performs the above-described functions defined in the system of the embodiment of the present disclosure. The systems, devices, apparatuses, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the present disclosure.

In accordance with embodiments of the present disclosure, program code for executing computer programs provided by embodiments of the present disclosure may be written in any combination of one or more programming languages, and in particular, these computer programs may be implemented using high level procedural and/or object oriented programming languages, and/or assembly/machine languages. The programming language includes, but is not limited to, programming languages such as Java, C + +, python, the "C" language, or the like. The program code may execute entirely on the user's computing device, partly on the user's device, partly on a remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., through the internet using an internet service provider).

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

Those skilled in the art will appreciate that various combinations and/or combinations of features recited in the various embodiments and/or claims of the present disclosure can be made, even if such combinations or combinations are not expressly recited in the present disclosure. In particular, various combinations and/or combinations of the features recited in the various embodiments and/or claims of the present disclosure may be made without departing from the spirit or teaching of the present disclosure. All such combinations and/or associations are within the scope of the present disclosure.

The embodiments of the present disclosure have been described above. However, these examples are for illustrative purposes only and are not intended to limit the scope of the present disclosure. Although the embodiments are described separately above, this does not mean that the measures in the embodiments cannot be used in advantageous combination. The scope of the disclosure is defined by the appended claims and equivalents thereof. Various alternatives and modifications can be devised by those skilled in the art without departing from the scope of the present disclosure, and such alternatives and modifications are intended to be within the scope of the present disclosure.

Claims

1. A component management method is applied to a terminal component on a device terminal, and is characterized in that the terminal component comprises an application program layer, a protocol layer and a service component layer, and the component management method comprises the following steps:

detecting the update time of a component import file in a server;

2. The component management method according to claim 1, wherein the storing the newly added service component to the service component layer and the storing the first resource-dependent protocol to the protocol layer comprise:

3. The component management method according to claim 2, wherein the first operation instruction comprises a jump operation instruction issued by a user through the menu entry, and the configuring, in response to the first operation instruction, a first resource-dependent protocol in the protocol layer that matches the first operation instruction into the application layer comprises:

4. The component management method according to claim 2, wherein the component management method further comprises:

5. The component management method according to claim 1, wherein the first resource-dependent protocol includes an initialization method and a resource calling method of the newly added business component, and the adaptive loading operation includes:

and jumping to the third operation page.

6. The component management method according to claim 5, wherein the resource includes a basic component configured in a common service component library and a UI service component library, and the configuring and automatically adapting the resource for the second operation page according to the resource calling method includes:

accessing the determined basic component to the second operation page;

7. The component management method according to claim 5, wherein the resource further includes a composite component configured in a composite service component library, the composite component calls a base component pre-configured in a common service component library and a UI service component library, and the resource is configured and automatically adapted for the second operation page according to the resource calling method, further comprising:

accessing the determined composite component to the second operation page;

and adjusting the composite component accessed to the second operation page according to the resource calling method so as to perform the adaptation.

8. A component management apparatus applied to a terminal component on a device terminal, wherein the terminal component includes an application layer, a protocol layer, and a service component layer, the component management apparatus comprising:

9. The component management apparatus according to claim 8, wherein the component management apparatus further comprises:

10. An electronic device, comprising:

one or more processors;

a storage device for storing one or more programs,

wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to perform the component management method of any of claims 1-7.

11. A computer-readable storage medium having stored thereon executable instructions which, when executed by a processor, cause the processor to perform a component management method according to any one of claims 1 to 7.

12. A computer program product comprising a computer program which, when executed by a processor, implements a component management method according to any one of claims 1 to 7.