阅读说明：本技术 组件处理方法、装置及设备 (Component processing method, device and equipment ) 是由 韩晓明 高林峰 于 2021-07-30 设计创作，主要内容包括：本申请实施例提供一种组件处理方法、装置及设备,该方法包括：针对目标视图创建对应的引擎实例,目标视图为宿主应用中组件的视图,或者,寄生应用的第一页面中的第一原生组件的视图；在寄生应用需要显示包括第二原生组件的第二页面时,创建第二原生组件的原生视图,并通过原生视图将引擎实例共享给第二原生组件,第一原生组件和第二原生组件均是原生的目标组件,目标组件与目标视图的种类一致。本申请能够减少寄生应用的资源消耗,提高寄生应用的页面加载速度。(The embodiment of the application provides a component processing method, a device and equipment, wherein the method comprises the following steps: creating a corresponding engine instance for a target view, wherein the target view is a view of a component in the host application or a view of a first native component in a first page of the hosted application; when the parasitic application needs to display a second page comprising a second native component, a native view of the second native component is created, and the engine instance is shared to the second native component through the native view, wherein the first native component and the second native component are both native target components, and the target components are consistent with the category of the target view. The method and the device can reduce resource consumption of parasitic application and improve page loading speed of the parasitic application.)

1. A component handling method, wherein the method comprises:

creating a corresponding engine instance for the target view; the target view is a view of a component in the host application, or a view of a first native component in a first page of the parasitic application;

creating a native view of a second native component and sharing the engine instance to the second native component through the native view when the parasitic application needs to display a second page that includes the second native component; the first and second native components are each native target components, the target components being of a kind consistent with the target view.

2. The method of claim 1, wherein the sharing of the engine instance to the second native component through the native view comprises:

adapting the target view to the second native component through the native view to enable sharing of the engine instance to the second native component.

3. The method of claim 2, wherein said adapting the target view to the second native component through the native view comprises:

establishing, by the native view, a transitive relationship between the target view and the second native component to pass component parameters for the second native component to the target view to trigger the engine instance to provide engine services to the second native component in accordance with the component parameters.

4. The method of claim 3, wherein the component parameters include any one or more of: component parameters triggered by an event, component parameters triggered by a function call, or component parameters triggered by an initial display.

5. The method of claim 3, layers of the native view being located over layers of the target view, and a region of the native view at least partially overlapping with a region of the target view;

the method further comprises the following steps: setting the background of the native view to transparent.

6. The method of claim 5, wherein there are other views between the native view and the target view; the method further comprises the following steps: setting the background of the other views to be transparent.

7. The method of any of claims 1-6, wherein the method further comprises:

when jumping from the page including the component to which the target view belongs to the page displaying the second page, saving the current component parameters of the component to which the target view belongs;

and when the second page is displayed to jump back to display the page comprising the component to which the target view belongs, triggering the engine instance to provide engine service for the component to which the target view belongs according to the saved component parameter of the component to which the target view belongs.

8. The method of any of claims 1-6, wherein the target view is a map view, the target component is a map component, and the engine instance is a map engine instance for providing a map engine service.

9. A component handling apparatus, wherein the apparatus comprises:

the creating module is used for creating a corresponding engine instance aiming at the target view; the target view is a view of a component in the host application, or a view of a first native component in a first page of the parasitic application;

a sharing module for creating a native view of a second native component and sharing the engine instance to the second native component through the native view when the parasitic application needs to display a second page including the second native component; the first and second native components are each native target components, the target components being of a kind consistent with the target view.

10. A computer program product comprising computer instructions, wherein the computer instructions, when executed by a processor, implement the steps of the method of any one of claims 1-8.

Technical Field

The present application relates to the field of computer technologies, and in particular, to a method, an apparatus, and a device for processing a component.

Background

An applet is an application that runs on the host application without requiring download installation.

At present, a native component which needs to be participated in processing by a host application can be included in a page of an applet, taking the native component as a map component as an example, if the map component is included in a page of the applet, a map engine instance needs to be created when the page is displayed. Also, if a map component is also included in another page in the applet, another map engine instance needs to be created when the other page is displayed.

However, in the above manner, there are problems that the resource consumption of the applet is large and the page loading is slow.

Disclosure of Invention

The embodiment of the application provides a component processing method, device and equipment, which are used for solving the problems that in the prior art, a small program consumes a large amount of resources and a page is loaded slowly.

In a first aspect, an embodiment of the present application provides a component processing method, including:

creating a corresponding engine instance for the target view; the target view is a view of a component in the host application, or a view of a first native component in a first page of the parasitic application;

creating a native view of a second native component included in the parasitic application when the parasitic application needs to display a second page of the second native component, and sharing the engine instance to the second native component through the native view; the first and second native components are each native target components, the target components being of a kind consistent with the target view.

In a second aspect, an embodiment of the present application provides a component processing apparatus, including:

the creating module is used for creating a corresponding engine instance aiming at the target view; the target view is a view of a component in the host application, or a view of a first native component in a first page of the parasitic application;

a sharing module for creating a native view of a second native component and sharing the engine instance to the second native component through the native view when the parasitic application needs to display a second page including the second native component; the first and second native components are each native target components, the target components being of a kind consistent with the target view.

In a third aspect, an embodiment of the present application provides an electronic device, including: a memory, a processor; wherein the memory is configured to store one or more computer instructions, wherein the one or more computer instructions, when executed by the processor, implement the method of any of the first aspects.

In a fourth aspect, the present application provides a computer program product, which includes computer instructions that, when executed by a processor, implement the steps of the method according to any one of the first aspect.

Embodiments of the present application further provide a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and the computer program includes at least one piece of code, which is executable by a computer to control the computer to perform the method according to any one of the first aspect.

In the embodiment of the application, the native target component in one page of the parasitic application can share the engine instance created for the target view of the component in the host application or the target view of the native target component in another page of the parasitic application, and the target view is consistent with the type of the target component, for example, the native map component in one page of the parasitic application can share the map view of the component in the host application or the map view of the native map component in another page of the parasitic application, and the engine instance created for the target view of the other component is shared through the native target component in the parasitic application, so that the resource consumption of the native component in the parasitic application is reduced, and the page loading speed of the parasitic application is improved.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative efforts.

Fig. 1 is a schematic flow chart illustrating a component processing method according to an embodiment of the present disclosure;

fig. 2 is a schematic view of a home page of a charging station applet according to an embodiment of the present application;

FIG. 3 is a schematic diagram of layers of the front page shown in FIG. 2 according to an embodiment of the present application;

fig. 4 is a schematic structural diagram of a device for processing components according to an embodiment of the present disclosure;

fig. 5 is a schematic structural diagram of an electronic device according to an embodiment of the present application.

Detailed Description

In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

The terminology used in the embodiments of the present application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in the examples of this application and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise, and "a" and "an" typically include at least two, but do not exclude the presence of at least one.

It should be understood that the term "and/or" as used herein is merely one type of association that describes an associated object, meaning that three relationships may exist, e.g., a and/or B may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter related objects are in an "or" relationship.

The words "if", as used herein, may be interpreted as "at … …" or "at … …" or "in response to a determination" or "in response to a detection", depending on the context. Similarly, the phrases "if determined" or "if detected (a stated condition or event)" may be interpreted as "when determined" or "in response to a determination" or "when detected (a stated condition or event)" or "in response to a detection (a stated condition or event)", depending on the context.

It is also noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a good or system that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such good or system. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a commodity or system that includes the element.

In addition, the sequence of steps in each method embodiment described below is only an example and is not strictly limited.

For the convenience of those skilled in the art to understand the technical solutions provided in the embodiments of the present application, a technical environment for implementing the technical solutions is described below.

Taking a native component as an example of a map component, a processing method of a native component in an applet, which is commonly used in the related art, mainly includes that if a page of the applet includes a map component, a map engine instance needs to be created when the page is displayed. Also, if a map component is also included in another page in the applet, another map engine instance needs to be created when the other page is displayed. However, creating a map engine instance requires consuming more resources, which results in slower page loading of an applet, and therefore a component processing method capable of reducing the resource consumption of the applet and increasing the page loading speed of the applet is needed in the related art.

Based on the actual technical requirements similar to those described above, the component processing method provided by the application can reduce the resource consumption of the applet by using a technical means, and improve the page loading speed of the applet.

The component processing method provided by the embodiment of the Application can be applied to any type of electronic equipment capable of deploying Application programs (APPs). An application program that can be hosted by other application programs, i.e., a hosted application, may be deployed in the electronic device. An application program that is hosted in and run in dependence on the host application is a hosted application. The parasitic application comprises a native component which needs the host application to participate in the processing, and the parasitic application also comprises a non-native component which does not need the host application to participate in the processing. In one embodiment, the parasitic application may be specifically a small program.

It should be noted that a Component (Component) in the embodiment of the present application refers to a simple package of data and methods, and may also be referred to as a control, a Component, and the like in other specific application scenarios.

In order to reduce the resource consumption of the parasitic application and increase the page loading speed of the parasitic application, in the embodiment of the application, target components native to a page of the hosted application, capable of sharing a target view for components in the hosted application, or a target view of a target component native in another page of the hosted application, the target view being consistent with the category of the target component, for example, map components native in a page of the hosted application, can share a map view for components in the hosted application, or an engine instance created from a map view of a native map component in another page of the hosted application, by hosting the target component native to the application, sharing the engine instances created for the target views of other components, therefore, resource consumption of the native component in the parasitic application is reduced, and the page loading speed of the parasitic application is increased.

It should be noted that, in the embodiments of the present application, the parasitic application is mainly exemplified as a small program.

Some embodiments of the present application will be described in detail below with reference to the accompanying drawings. The embodiments described below and the features of the embodiments can be combined with each other without conflict.

Fig. 1 is a flowchart illustrating a component processing method according to an embodiment of the present application, where an execution main body of the embodiment may be the electronic device. As shown in fig. 1, the method of this embodiment may include:

step 11, creating a corresponding engine instance for the target view; the target view is a view of a component in the host application, or a view of a first native component in a first page of the parasitic application;

step 12, when the parasitic application needs to display a second page comprising a second native component, creating a native view of the second native component, and sharing the engine instance to the second native component through the native view; the first and second native components are each native target components, the target components being of a kind consistent with the target view.

In the embodiment of the application, the target components native in the second page of a parasitic application can share the engine instance created for the target view of the components in the host application of the parasitic application, or can share the engine instance created for the target view of the target components native in the first page of the parasitic application, and the target view is consistent with the type of the target components. The engine instance is used for providing the engine service, and it can be understood that after the engine instance correspondingly created for the target view is shared with the second native component, the engine instance correspondingly created for the target view can be used for providing the engine service for the second native component.

Wherein, the target component can be flexibly selected according to the requirement. In one embodiment, a native component in the parasitic application that consumes more resources corresponding to the engine instance may be selected as the target component. Illustratively, the target component may be a map component. Based on this, native map components in the second page of a hosted application can share engine instances created for map views (MapView) of components in the hosted application of the hosted application, or can share engine instances created for map views of native map components in the first page of the hosted application. In this case, the engine instance correspondingly created for the target view is a map engine instance for providing a map engine service. For convenience of description, the following description mainly takes the target component as an example of the map component.

When the target view is a view of a component in the host application, sharing the engine instance created for the target view of the component in the host application to the target component native in the second page of the parasitic application (i.e., the second native component) may be achieved.

For example 1, when a map application needs to display its home page, a map view of a component in the home page may be created, and a corresponding map engine instance may be created for the map view. Thereafter, when a charging station applet hosted in the map-like application needs to display a home page that includes a native map component, a native view of the map component can be created and the map engine instance created for the map view can be shared to the map component through the native view. The map application is a host application, the charging station applet is a parasitic application, the home page of the charging station applet is a second page, and native map components included in the home page of the charging station applet are second native components.

When the target view is a view of a first native component in a first page of the parasitic application, sharing an engine instance created for the target component native in the first page of the parasitic application (i.e., the first native component) to the target component native in a second page of the parasitic application (i.e., the second native component) may be implemented.

For example 2, when a map-related applet needs to display a page a including a native map component 1 in a host application, a native view of the map component 1 may be created, a map view may be further created under the native view, and a corresponding map engine instance may be created for the map view. Thereafter, when the map-related applet needs to display page b including the native map component 2, a native view of the map component 2 can be created and the map engine instance created for the map view of map component 1 can be shared to map component 2 through the native view of map component 2. The map-related small program is a parasitic application, a page a of the map-related small program is marked as a first page, a map component 1 in the page a is a first native component, a page b of the map-related small program is a second page, and a map component 2 in the page b is a second native component.

In an embodiment, sharing the engine instance created for the target view to the second native component through the native view of the second native component may specifically include: the engine instances correspondingly created for the target view are shared directly to the second native component through the native view of the second native component.

In another embodiment, sharing the engine instance created for the target view to the second native component through the native view of the second native component may specifically include: the target view is adapted to the second native component through the native view of the second native component to enable sharing of the engine instance correspondingly created for the target view to the second native component. It should be noted that, the relationship between the engine instance and the target view is that the target view is a package of the engine instance, the engine is further at the bottom layer, taking the map engine and the map instance as an example, the map view is a package of the map engine, and the target view is adapted to the second native component through the native view, so that the package of the engine instance does not need to be rewritten when the sharing of the engine instance is realized, which is beneficial to simplifying the implementation.

For example, the adapting the target view to the second native component through the native view of the second native component may specifically include: establishing a transitive relationship between the target view and the second native component through the native view of the second native component to pass component parameters for the second native component to the target view to trigger the engine instance to provide engine services to the second native component according to the component parameters of the second native component. Since the engine instance is created for the target view, and the target view and the engine instance have the capability of transferring parameters, by establishing a transfer relationship between the target view and the second native component, the component parameters for the second native component can be transferred to the target view, so as to be transferred to the engine instance created for the target view by the target view, and the engine instance is triggered to provide the engine service for the second native component according to the component parameters of the second native component, so that the engine instance created for the target view is shared with the second native component.

The component parameters of the second native component may specifically be any type of parameters that the second native component needs to transfer to the engine instance, and specifically, may be flexibly implemented according to requirements. Illustratively, the component parameters of the second native component may include any one or more of: component parameters triggered by an event, component parameters triggered by a function call, or component parameters triggered by an initial display.

For example, on the basis of example 1, assuming that a gesture event of the user for a map component native in the home page of the charging station applet is acquired in the case of displaying the home page of the charging station applet, the response procedure for the gesture event may be, for example: the native map component in the home page of the charging station applet can transmit gesture parameters corresponding to the acquired gesture events to a map view of a component in a page for map application through a native view of the map component, the map view can convert the gesture parameters into parameters recognizable by an engine instance and transmit the converted parameters recognizable by the engine instance to a map engine instance created for the map view, and the map engine instance can convert the received parameters recognizable by the engine instance into real longitude and latitude parameters and render and display a map according to the longitude and latitude parameters.

For another example, in example 2, if a route query operation from a location a to a location B input by a user is acquired when a page B of a map-related applet is displayed, a response procedure to the route query operation may be, for example: the map-related small program can calculate a series of longitude and latitude coordinates of a corresponding route according to the route query operation, and transmit the parameters such as the longitude and latitude coordinates and the line width to the native map component 2 in the page b in a function calling mode, the map component 2 transmits the native view of the map component 1 in the page a of the map-related small program to the map view of the native map component 1 in the page a of the map-related small program, the map view can transmit the parameters to the map engine instance created aiming at the map view, and the map engine instance can render and display a map according to the parameters.

Optionally, the transfer relationship between the target view established by the native view of the second native component and the second native component may also be used to transfer the parameter to the second native component when the target view acquires the parameter returned by the engine instance established for the target view. And the parameter transfer relation from the engine instance of the target view to the second target component is provided, so that the parasitic application can acquire the parameter returned by the engine instance of the target view.

It should be noted that, because the engine instance is created for the target view, the content that the engine instance needs to display may be presented on the component to which the target view belongs, after the engine instance created corresponding to the target view is shared with the second native component, the display content that should be presented by the second native component may be changed to be presented by the component to which the target view belongs.

Based on this, in a case that the layer of the native view of the second native component is located above the layer of the target view, and the region of the native view and the region of the target view at least partially overlap, the method provided in the embodiment of the present application may further include: the background of the native view of the second native component is set to transparent. Therefore, the problem that the content presented on the component to which the target view belongs cannot be seen clearly by a user due to the fact that the background of the native view of the second native component is non-transparent can be avoided, and the use experience of the user is improved.

Further optionally, in a case that there is another view between the native view and the target view of the second native component, the method provided in the embodiment of the present application may further include: setting the background of the other views to be transparent. Taking a parasitic application as an applet implemented based on web development technology, for example, the other views existing between the native view of the second native component and the target view may include, for example, a web page view (WebView). By setting other views between the native view of the second native component and the target view to be transparent, the problem that a user cannot clearly see contents presented on the component to which the target view belongs due to non-transparent backgrounds of the other views between the native view of the second native component and the target view can be avoided, and the use experience of the user can be improved.

Optionally, the method according to the embodiment of the present application may further include: when the page including the component to which the target view belongs is displayed and jumps to a second page, saving the current component parameters of the component to which the target view belongs; and when the second page is displayed and the page comprising the component to which the target view belongs is switched back to be displayed, triggering the engine instance correspondingly created aiming at the target view to provide the engine service for the component to which the target view belongs according to the component parameter of the component to which the target view belongs. So that the display content of the component to which the target view belongs can remain unchanged when jumping back to display the page including the component to which the target view belongs. The saved component parameters of the component to which the target view belongs can be regarded as the component parameters of the component to which the target view belongs triggered by the initial display. When the target view is a view of a component in the host application, the page of the component to which the target view belongs may specifically be a page of the host application including the component; when the target view is a view of a first native component in a first page of the parasitic application, the page of the component to which the target view belongs may specifically be the first page.

Similarly, the method provided by the embodiment of the present application may further include: saving the current component parameters of the second native component when the page comprising the component to which the target view belongs is displayed by the second page jump back display; and when the page including the component to which the target view belongs is displayed and the second page is displayed, triggering the engine instance correspondingly created aiming at the target view to provide the engine service for the second native component according to the saved component parameters of the second native component. Thereby enabling the display content of the second native component to remain unchanged when jumping back to display the second page. Wherein the saved component parameters of the second native component may be considered as the component parameters of the second native component triggered by the initial display.

Assuming that the host application is a map-class application, the parasitic application is a charging station applet parasitic in the map-class application, and the home page of the charging station applet includes native map components, if the user opens the charging station applet in the map-class application, the charging station applet page displayed to the user may be, for example, as shown in fig. 2, and the layer structure of fig. 2 may be as shown in fig. 3. Referring to fig. 2 and 3, a map view (referred to as a main map layer 31 for short) of a component in the map class application may be located at the bottom of a page stack, a webpage view layer 32 of a charging station applet home page may be located on the main map layer 31, a native view 33 of the map component of the charging station applet home page may be located on the webpage view layer 32, and views 34 of other components in the charging station applet home page may be located on the native view 33 of the map component in the charging station applet home page, it can be seen from fig. 2 and 3 that after sharing an engine instance of the main map to the map component of the charging station applet, display content that should be originally presented by the map component of the charging station applet is changed to be presented by a component to which the main map of the map class application belongs.

It should be noted that fig. 3 is an example of rendering native components in an applet by using a peer rendering technique.

According to the component processing method provided by the embodiment of the application, the native target component in one page of the parasitic application can share the target view aiming at the component in the host application or the engine instance created by the target view aiming at the native target component in the other page of the parasitic application, and the target view is consistent with the type of the target component, for example, the native map component in one page of the parasitic application can share the map view aiming at the component in the host application or the engine instance created by the map view aiming at the native map component in the other page of the parasitic application, and the engine instance created by the target view aiming at the other component is shared through the native target component in the parasitic application, so that the resource consumption of the native component in the parasitic application is reduced, and the page loading speed of the parasitic application is improved.

Fig. 4 is a schematic structural diagram of a device for processing components according to an embodiment of the present disclosure; referring to fig. 4, the present embodiment provides a component handling apparatus, which may perform the component handling method described above, and specifically, the component handling apparatus may include:

a creating module 41, configured to create a corresponding engine instance for the target view; the target view is a view of a component in the host application, or a view of a first native component in a first page of the parasitic application;

a sharing module 42, configured to create a native view of a second native component when the parasitic application needs to display a second page including the second native component, and share the engine instance to the second native component through the native view; the first and second native components are each native target components, the target components being of a kind consistent with the target view.

Optionally, the sharing module 42 is configured to share the engine instance to the second native component through the native view, and specifically includes: adapting the target view to the second native component through the native view to enable sharing of the engine instance to the second native component.

Optionally, the sharing module 42 is configured to adapt the target view to the second native component through the native view, and specifically includes: establishing, by the native view, a transitive relationship between the target view and the second native component to pass component parameters for the second native component to the target view to trigger the engine instance to provide engine services to the second native component in accordance with the component parameters.

Optionally, the component parameters may include any one or more of the following: component parameters triggered by an event, component parameters triggered by a function call, or component parameters triggered by an initial display.

Optionally, the layer of the native view is located above the layer of the target view, and a region of the native view and a region of the target view at least partially overlap; the sharing module 42 is further configured to: and setting the background of the native view to transparent.

Optionally, there are other views between the native view and the target view; the sharing module 42 is further configured to: setting the background of the other views to be transparent.

Optionally, the apparatus further includes a skip module, configured to:

when jumping from the page including the component to which the target view belongs to the page displaying the second page, saving the current component parameters of the component to which the target view belongs; and when the second page is displayed and the page comprising the component to which the target view belongs is jumped back to be displayed, triggering the engine instance to provide engine service for the component to which the target view belongs according to the saved component parameter of the component to which the target view belongs.

Optionally, the target view is a map view, the target component is a map component, and the engine instance is a map engine instance for providing a map engine service.

The apparatus shown in fig. 4 can perform the method of the embodiment shown in fig. 1, and reference may be made to the related description of the embodiment shown in fig. 1 for a part of this embodiment that is not described in detail. The implementation process and technical effect of the technical solution refer to the description in the embodiment shown in fig. 1, and are not described herein again.

In one possible implementation, the structure of the decision device shown in fig. 4 may be implemented as an electronic device. As shown in fig. 5, the electronic device may include: a processor 51 and a memory 52. Wherein the memory 52 is used for storing a program for supporting the electronic device to execute the component processing method provided in the embodiment shown in fig. 1, and the processor 51 is configured for executing the program stored in the memory 52.

The program comprises one or more computer instructions which, when executed by the processor 51, are capable of performing the steps of:

creating a corresponding engine instance for the target view; the target view is a view of a component in the host application, or a view of a first native component in a first page of the parasitic application;

creating a native view of a second native component and sharing the engine instance to the second native component through the native view when the parasitic application needs to display a second page that includes the second native component; the first and second native components are each native target components, the target components being of a kind consistent with the target view.

Optionally, the processor 51 is further configured to perform all or part of the steps in the foregoing embodiment shown in fig. 1.

The electronic device may further include a communication interface 53 for communicating with other devices or a communication network.

In addition, the present application provides a computer storage medium for storing computer software instructions for an electronic device, which includes a program for executing the component processing method in the method embodiment shown in fig. 1.

The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.

Through the above description of the embodiments, those skilled in the art will clearly understand that each embodiment can be implemented by adding a necessary general hardware platform, and of course, can also be implemented by a combination of hardware and software. With this understanding in mind, the above-described technical solutions and/or portions thereof that contribute to the prior art may be embodied in the form of a computer program product, which may be embodied on one or more computer-usable storage media having computer-usable program code embodied therein (including but not limited to disk storage, CD-ROM, optical storage, etc.).

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.

Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.

Finally, it should be noted that: the above embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present application.