CN117591106A - Calling method and device of native function component, electronic equipment and storage medium - Google Patents

Abstract

Embodiments of the present application disclose a method, device, electronic device, and storage medium for calling native functional components. A native functional component calling framework applied to electronic devices. The framework includes multiple functional modules. The functional modules include native functional components and Jsbridge components that match the native functional components. The method includes: obtaining a target calling request through a preset target front-end framework; Determine the target Jsbridge component corresponding to the target Jsbridge identifier from multiple Jsbridge components; send the target call information to the target native function component through the target Jsbridge component; generate the target response information of the target call information through the target native function component; use the target Jsbridge component Return the target response information to the target front-end framework. The Jsbridge component in the electronic device of the embodiment of the present application is a Jsbridge component split according to the calling capabilities, which decouples the Jsbridge components with different calling capabilities. When there is a Jsbridge fault, the faulty Jsbridge component can be found faster, which improves the Jsbridge component. Component maintenance efficiency.

Description

Calling methods, devices, electronic devices and storage media of native functional components

Technical field

The present application relates to the field of data processing technology, and in particular to a method, device, electronic device and storage medium for calling native functional components.

Background technique

In current medium and large applications (Application, APP), in addition to native pages, there are often two to three front-end frameworks at the same time, such as front-end frameworks corresponding to H5, Weex, ReactNative or Flutter.

The front-end framework needs to use native functional components by calling Jsbridge, such as calling native facial recognition components, optical character recognition (Optical Character Recognition, OCR) components, WeChat payment components and other functional components. In the existing technology, all native functional components need to be The Jsbridges corresponding to the functional components are put together as one Jsbridge component, and the Jsbridge component is deployed in the corresponding APP. However, if the Jsbridges corresponding to all functions are put together, the Jsbridges with different functions are seriously coupled. When there is a Jsbridge When a fault occurs, maintenance efficiency is low because the Jsbridge of each function is coupled together.

Contents of the invention

The embodiments of this application provide a calling method, device, electronic device and storage medium for native functional components, which can improve the maintenance efficiency of Jsbridge components.

In a first aspect, embodiments of the present application provide a method for calling native functional components. The method is applied to a native functional component calling framework of an electronic device. The native functional component calling framework includes a plurality of functional modules, each of which functions The modules all include native functional components and Jsbridge components that match the native functional components. The methods include:

Obtain the target call request through the preset target front-end framework, and the target call request includes the target Jsbridge identification and target call information;

Determine the target Jsbridge component corresponding to the target Jsbridge identifier from a plurality of the Jsbridge components;

Send the target calling information to the target native functional component through the target Jsbridge component, and the target native functional component and the target Jsbridge component are located in the same functional module;

Generate target response information of the target call information through the target native functional component;

The target response information is returned to the target front-end framework through the target Jsbridge component.

In the second aspect, embodiments of the present application also provide a native functional component calling framework, which is deployed in an electronic device. The native functional component calling framework includes a container layer, an intermediate calling layer, and an independent functional module layer. The container layer includes multiple business framework containers, and different business frame containers carry different types of front-end frameworks. The intermediate call layer includes call entrances and registration tables corresponding to each of the business frame containers. The independent functional modules The layer includes multiple functional modules, each of which includes native functional components and Jsbridge components that match the native functional components, where:

The container layer is used to obtain a target call request through a target front-end framework in multiple front-end frameworks, where the target call request includes a target Jsbridge identifier and target call information;

The intermediate calling layer is used to determine the target Jsbridge component corresponding to the target Jsbridge identifier from a plurality of the Jsbridge components according to the registration table;

The independent function module layer is used to send the target call information to the target native function component through the target Jsbridge component, and the target native function component and the target Jsbridge component are located in the same functional module; through the target The native functional component generates target response information of the target call information; and returns the target response information to the target front-end framework through the target Jsbridge component.

In a third aspect, embodiments of the present application further provide an electronic device. A native functional component calling framework is deployed in the electronic device. The native functional component calling framework includes a plurality of functional modules, and each of the functional modules includes a native functional component calling framework. Functional components and Jsbridge components matching the native functional components. The electronic device includes a memory and a processor. A computer program is stored on the memory. The native functional component calling framework is implemented when the processor executes the computer program. the above method.

In a fourth aspect, embodiments of the present application also provide a computer-readable storage medium, the storage medium stores a computer program, the computer program includes program instructions, and when executed by a processor, the program instructions can implement the above method. .

Embodiments of the present application provide a method, device, electronic device, and storage medium for calling native functional components. Wherein, the method is applied to a native functional component calling framework of an electronic device. The native functional component calling framework includes a plurality of functional modules, and each of the functional modules includes a native functional component and a Jsbridge that matches the native functional component. component, the method includes: obtaining a target call request through a preset target front-end framework, the target call request including a target Jsbridge identification and target call information; determining from a plurality of the Jsbridge components corresponding to the target Jsbridge identification Target Jsbridge component; send the target call information to the target native functional component through the target Jsbridge component, and the target native functional component and the target Jsbridge component are located in the same functional module; generate the target native functional component through the target native functional component The target response information of the target call information is returned to the target front-end framework through the target Jsbridge component. The Jsbridge component in the embodiment of this application is a Jsbridge component split according to calling capabilities, which decouples Jsbridge components with different calling capabilities. When there is a Jsbridge failure, the faulty Jsbridge component can be found faster, which improves the performance of the Jsbridge component. Maintenance efficiency.

Description of drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings needed to be used in the description of the embodiments will be briefly introduced below. Obviously, the drawings in the following description are some embodiments of the present application, which are of great significance to this field. Ordinary technicians can also obtain other drawings based on these drawings without exerting creative work.

Figure 1 is a schematic diagram of the application scenario of the calling method of the native functional component provided by the embodiment of the present application;

Figure 2 is a schematic flow chart of the calling method of the native functional component provided by the embodiment of the present application;

Figure 3 is a schematic block diagram of an electronic device provided by an embodiment of the present application.

Detailed ways

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by those of ordinary skill in the art without creative efforts fall within the scope of protection of this application.

It should be understood that, when used in this specification and the appended claims, the terms "comprises" and "comprises" indicate the presence of described features, integers, steps, operations, elements and/or components but do not exclude the presence of one or The presence or addition of multiple other features, integers, steps, operations, elements, components and/or collections thereof.

It should also be understood that the terminology used in the specification 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 this specification and the appended claims, the singular forms "a", "an" and "the" are intended to include the plural forms unless the context clearly dictates otherwise.

It will be further understood that the term "and/or" as used in this specification and the appended claims refers to and includes any and all possible combinations of one or more of the associated listed items. .

Embodiments of the present application provide a method, device, electronic device, and storage medium for calling native functional components.

The execution subject of the calling method of the native functional component may be the calling device of the native functional component provided in the embodiment of the present application, or an electronic device integrated with the calling device of the native functional component, wherein the calling device of the native functional component may be It is implemented in the form of hardware or software. The electronic device is a terminal device, and the terminal device can be a mobile phone. The system of the terminal device can be an Android system or an IOS system. That is, the native functional components in the electronic device of this application can be Android native functional components or IOS native functional components.

Among them, the native functional component calling framework provided by the embodiment of the application includes multiple functional modules, and different functional modules are composed of different native functional components and corresponding Jsbridge components. The Jsbridge component can call the native functional components located in the same functional module. , Native functional components can also send information to the front-end framework through the Jsbridge component located in the same functional module.

In some embodiments, please refer to Figure 1. Figure 1 is a schematic structural diagram of a native functional component calling framework provided by an embodiment of the present application. The native functional component calling framework is deployed in the electronic device provided by the present application. The native functional component calling framework includes the container layer, the intermediate calling layer and the independent function module layer, among which:

The container layer: includes multiple business framework containers, and different business framework containers carry different types of front-end frameworks. In some embodiments, the front-end framework includes webview business framework, weex business framework and flutter business framework, wherein, according to Depending on the needs of the APP, the front-end framework can also be other types of front-end frameworks. The specific front-end framework type is not limited in this embodiment.

The intermediate calling layer: is the Bridge layer, including the calling entrance and the registration table corresponding to each of the business framework containers, and the independent functional module layer includes a plurality of the functional modules. For example, as shown in Figure 1, the call entry corresponding to the webview container is webEvent, the call entry corresponding to the weex container is weexEvent, and the call entry corresponding to the flutter container is flutterEvent. Call requests from different front-end frameworks can call the Jsbridge component through the corresponding call entrance. The Jsbridge data in the registry is the APP during the compilation phase. The bytecode instrumentation library is inserted into the registry according to the configuration in the APP compilation script. Register the corresponding Jsbridge component in the registry. Specifically, the registry includes the mapping relationship between the Jsbridge identifier of each Jsbridge component and the calling code. When registering the Jsbridge component, the Jsbridge component of the Jsbridge component will be registered. The logo is written into the registry, and the calling code (i.e., implementation class) corresponding to the Jsbridge component is inserted into the location corresponding to the Jsbridge logo through bytecode instrumentation technology to complete the construction of the mapping relationship between the Jsbridge logo and the calling code.

The independent functional module layer: includes a plurality of the native functional components. Each functional module includes a native functional component and a Jsbridge component that matches the native functional component. It should be noted that not all native functional components may have them. Its matching Jsbridge component, some native functional components that cannot be called by the front-end framework do not need to set the corresponding Jsbridge component, as shown in Figure 1, the face brushing function module includes the face brushing Jsbridge component and the face brushing component, and the log function module includes Log Jsbridge component and log component, OCR function module include OCR Jsbridge component and OCR component.

Specifically, in this embodiment of the application, the container layer is used to obtain a target call request through a target front-end framework in multiple front-end frameworks, and the target call request includes a target Jsbridge identification and target call information; The intermediate calling layer is used to determine the target Jsbridge component corresponding to the target Jsbridge identifier from a plurality of the Jsbridge components according to the registration table; the independent function module layer is used to transfer the target Jsbridge component to the target Jsbridge component through the target Jsbridge component. The target call information is sent to the target native function component, and the target native function component and the target Jsbridge component are located in the same functional module; the target response information of the target call information is generated through the target native function component; through the target The Jsbridge component returns the target response information to the target front-end framework.

Figure 2 is a schematic flowchart of the calling method of the native functional component provided by the embodiment of the present application. As shown in Figure 2, the method includes the following steps S110-S150.

S110. Obtain the target call request through the preset target front-end framework, where the target call request includes the target Jsbridge identifier and target call information.

In this embodiment, the target front-end frame is a page frame corresponding to a target page in multiple front-end frames, the target page is a page currently displayed by the electronic device, and the target page includes at least one of the native The calling control of functional components; obtaining the target calling request through the preset target front-end framework includes:

Receive a user's calling operation for a target calling control in at least one of the calling controls, where the target calling control is a calling control used to call the target native functional component in at least one of the calling controls; obtain the call operation based on the calling operation The target call information is generated, and the target call request is generated according to the target Jsbridge identifier bound to the target call control and the target call information.

For example, the user opens the target APP through an electronic device and enters a certain page (target page) of the target APP. At this time, the electronic device displays the target page. The target page is displayed based on the target front-end framework (such as the webview business framework), and the target The page displays at least one call control of the native functional component, and different call controls are bound to the Jsbridge logo of the Jsbridge component with the corresponding function; then the user clicks the target call control in the target page, and the electronic device displays the call information acquisition interface. The call information acquisition interface is used to obtain the target call information, then obtain the target call information based on the call information acquisition interface, and finally generate a target call request based on the obtained target call information and the corresponding target Jsbridge identification.

Among them, the target call information is the information that needs to be sent to the target native functional component for processing. For example, the user inputs an image to be recognized that needs to be OCR recognized. At this time, the corresponding target native functional component is an OCR component, and the user needs to upload the image to be recognized. Picture to call the information acquisition interface. Specifically, the Jsbridge identifier may be the Jsbridge name corresponding to the Jsbridge component.

S120. Determine the target Jsbridge component corresponding to the target Jsbridge identifier from the plurality of Jsbridge components.

In some embodiments, the native functional component calling framework also includes a registry, which includes a mapping relationship between the Jsbridge identifier of each Jsbridge component and the calling code. Step S120 includes: Determine the target calling code corresponding to the target Jsbridge identifier; based on the calling code, reflectively call the target Jsbridge component from a plurality of the Jsbridge components.

For example, when the target call request is obtained through the webview container carrying the webview business framework in the container layer in Figure 1, the Bridge layer obtains the target call request through the webEvent connected to the webview container. The target call request is data in json format. By parsing the target call request, the target Jsbridge ID and target call information can be obtained, and then the target Jsbridge ID is used to match in the registry. If the corresponding Jsbridge ID is matched, the calling code corresponding to the matched Jsbridge ID is determined as the target. Call the code, and then call the target Jsbridge component through reflection based on the target call code, that is, call the entity class identified by the target Jsbridge.

It can be seen that this embodiment can realize the connection between the Bridge layer and the Jsbridge component by placing a registry in the Bridge layer, and then reflectively calling the Jsbridge component based on the Jsbridge identifier and the corresponding calling code in the registry without directly calling the Jsbridge component. of decoupling.

It should be noted that before executing step S120, it is first necessary to determine whether the target Jsbridge identifier exists in the registry; when it is determined that the target Jsbridge identifier exists in the registry, step S120 is executed. If the target Jsbridge identifier does not exist in the registry, If the target Jsbridge identifier exists, the call failure information needs to be returned to the target front-end framework.

S130. Send the target calling information to the target native functional component through the target Jsbridge component. The target native functional component and the target Jsbridge component are located in the same functional module.

In this embodiment, after the target Jsbridge component is determined, the target calling information is sent to the target native functional component located in the same functional module as the target Jsbridge component through the target Jsbridge component.

For example, by calling the OCR Jsbridge component, the image to be recognized is sent to the target native functional component.

S140. Generate target response information of the target call information through the target native functional component.

In this embodiment, after the target native function component receives the target call information, it will process the target call information and generate a processing result, which is the target response information.

For example, after the OCR component obtains the image to be recognized, it performs OCR recognition processing on the image to be recognized and generates a recognition result.

S150. Return the target response information to the target front-end framework through the target Jsbridge component.

In this embodiment, after the target native functional component generates the target response information of the target call information, the target response information is returned to the target front-end framework through the target Jsbridge component.

For example, the OCR component returns the recognition result to the target front-end framework through the OCR Jsbridge component. At this time, the electronic device displays the recognition result based on the target front-end framework, so that the user can obtain the recognition result.

It should be noted that the Jsbridge component in this embodiment is subdivided according to different functions during the development stage. The development stage of the target APP is described below:

Since different APPs need to call different native functional components, in order to allow different APPs to quickly access the required Jsbridge functions, before development, it is first necessary to subdivide the original coupled Jsbridge into multiple Jsbridge components according to the calling functions. , that is, separate Jsbridge with different functions and encapsulate them in one component.

In the development stage, corresponding to the Jsbridge component access, the introduction of the Jsbridge component can be completed in the gradle script through a line of introduction code similar to "implementation'com.xxx.component:face:1.0.2"; the removal of the Jsbridge component is Just remove the "implementation'com.xxx.component:face:1.0.2" line of code in the gradle script.

It can be seen that during the development stage of APP, the access and removal of Jsbridge components is very convenient, thus improving development efficiency.

In this way, when the corresponding APP is installed in an electronic device, during the coding phase of the APP, the Jsbridge code will implement a specified method of a specified interface, which is the registration method of the Jsbridge. This specified interface and method will be configured in the compilation script. During the APP compilation phase: During the compilation process, the bytecode instrumentation library will insert the calling code of these Jsbridge registration methods into the specified registration method according to the configuration in the compilation script, such as named "initEvent". APP startup phase: Calling "initEvent" during the APP startup process is equivalent to calling these Jsbridge registration methods.

Specifically, the APP will add Jsbridge information to the registry through the registration method, so that when the APP is running, it will know which Jsbridges the APP is connected to. The registry is a key-value pair data format, that is, the Jsbridge name corresponds to the implementation class (calling code). This completes the Jsbridge registration. The purpose of such registration is decoupling, that is, the accessing APP does not directly call the classes and methods in Jsbridge.

To sum up, in the first aspect, the Jsbridge component in the electronic device of the embodiment of the present application is a Jsbridge component split according to the calling capabilities, which decouples the Jsbridge components with different calling capabilities. When there is a Jsbridge failure, the Jsbridge component can be processed more quickly. Finding faulty Jsbridge components improves the maintenance efficiency of Jsbridge components; secondly, subdividing Jsbridge components according to their calling capabilities can facilitate developers to use Jsbridge components, thereby improving development efficiency; thirdly, subdividing Jsbridge components The final Jsbridge component is bound to the corresponding native functional component in the electronic device to avoid loading the Jsbridge component of the native functional component that is not found in the electronic device, that is, to avoid accessing unnecessary Jsbridge components, thereby reducing redundancy in the electronic device. code.

This application also provides a native functional component calling framework, which is deployed in an electronic device. The native functional component calling framework includes a container layer, an intermediate calling layer and an independent function module layer. The container layer includes Multiple business framework containers. Different business framework containers carry different types of front-end frameworks. The intermediate call layer includes call entrances and registration tables corresponding to each business frame container. The independent function module layer includes multiple functions. Modules, each of the functional modules includes native functional components and Jsbridge components matching the native functional components, where:

The container layer is used to obtain a target call request through a target front-end framework in multiple front-end frameworks, where the target call request includes a target Jsbridge identifier and target call information;

The intermediate calling layer is used to determine the target Jsbridge component corresponding to the target Jsbridge identifier from a plurality of the Jsbridge components according to the registration table;

The independent function module layer is used to send the target call information to the target native function component through the target Jsbridge component, and the target native function component and the target Jsbridge component are located in the same functional module; through the target The native functional component generates target response information of the target call information; and returns the target response information to the target front-end framework through the target Jsbridge component.

In some embodiments, the registration table includes a mapping relationship between the Jsbridge identifier of each Jsbridge component and the calling code, and the intermediate calling layer determines the relationship between the Jsbridge component and the Jsbridge component when executing the When the target Jsbridge identifies the corresponding target Jsbridge component step, it is specifically used for:

The target calling code corresponding to the target Jsbridge identifier is determined from the registry; based on the calling code, the target Jsbridge component is reflectively called from a plurality of the Jsbridge components.

In some embodiments, the target front-end frame is a page frame corresponding to a target page in multiple front-end frames, the target page is a page currently displayed by the electronic device, and the target page includes at least one of the The calling control of the native functional component; when the container layer executes the step of obtaining the target calling request through the preset target front-end framework, it is specifically used to:

Receive the user's calling operation for the target calling control, which is the calling control used to call the target native functional component in at least one of the calling controls; obtain the target calling information based on the calling operation, and according to The target Jsbridge identifier bound to the target call control and the target call information generate the target call request.

In some embodiments, the front-end framework in the business framework container includes a webview business framework, a weex business framework or a flutter business framework.

In some embodiments, before executing the step of determining the target calling code corresponding to the target Jsbridge identifier from the registry, the intermediate calling layer is also used to:

Determine whether the target Jsbridge identifier exists in the registry;

At this time, when the intermediate calling layer executes the step of determining the target calling code corresponding to the target Jsbridge identifier from the registry, it is specifically used to:

If the target Jsbridge identifier exists in the registry, the calling code corresponding to the target Jsbridge identifier in the registry is determined as the target calling code.

In some embodiments, after performing the step of determining whether the target Jsbridge identification exists in the registry, the intermediate calling layer is also used to:

If the target Jsbridge identifier does not exist in the preset registry, a call failure message is returned to the target front-end framework.

To sum up, in the first aspect, the Jsbridge component in the native functional component calling framework of the embodiment of the present application is a Jsbridge component split according to the calling capabilities, which decouples the Jsbridge components with different calling capabilities. When there is a Jsbridge failure, you can Finding faulty Jsbridge components faster improves the maintenance efficiency of Jsbridge components; secondly, subdividing Jsbridge components according to their calling capabilities can facilitate developers to use Jsbridge components, thereby improving development efficiency; thirdly, Bind the subdivided Jsbridge components to the corresponding native functional components in the electronic device to avoid loading Jsbridge components that do not have native functional components in the electronic device, that is, to avoid accessing unnecessary Jsbridge components, thus reducing the number of components in the electronic device. redundant code.

It should be noted that those skilled in the art can clearly understand that the calling device of the above-mentioned native functional components and the specific implementation process of each unit can refer to the corresponding descriptions in the foregoing method embodiments. For the convenience and simplicity of description, in This will not be described again.

The above-mentioned calling device of the native functional component can be implemented in the form of a computer program, and the computer program can be run on the electronic device as shown in Figure 3.

Please refer to FIG. 3 , which is a schematic block diagram of an electronic device provided by an embodiment of the present application. The electronic device 300 may be a terminal, where the terminal may be an electronic device with communication functions and native functional components, such as a smartphone, a tablet computer, a notebook computer, a desktop computer, a personal digital assistant, a wearable device, etc. Wherein, a native functional component calling framework is deployed in the electronic device. The native functional component calling framework includes a plurality of functional modules, and each of the functional modules includes a native functional component and a Jsbridge component matching the native functional component.

Referring to FIG. 3 , the electronic device 300 includes a processor 302 , a memory, and a network interface 305 connected through a system bus 301 , where the memory may include a nonvolatile storage medium 303 and an internal memory 304 .

The non-volatile storage medium 303 can store an operating system 3031 and a computer program 3032. The computer program 3032 includes program instructions that, when executed, can cause the processor 302 to execute a calling method of a native functional component.

The processor 302 is used to provide computing and control capabilities to support the operation of the entire electronic device 300 .

The internal memory 304 provides an environment for the execution of the computer program 3032 in the non-volatile storage medium 303. When the computer program 3032 is executed by the processor 302, it can cause the processor 302 to execute a calling method of native functional components.

The network interface 305 is used for network communication with other devices. Those skilled in the art can understand that the structure shown in Figure 3 is only a block diagram of a partial structure related to the solution of the present application, and does not constitute a limitation on the electronic device 300 to which the solution of the present application is applied. Specific electronic devices 300 may include more or fewer components than shown, some combinations of components, or a different arrangement of components.

Wherein, the processor 302 is used to run the computer program 3032 stored in the memory to implement the following steps:

Obtain the target call request through the preset target front-end framework, and the target call request includes the target Jsbridge identification and target call information;

Determine the target Jsbridge component corresponding to the target Jsbridge identifier from a plurality of the Jsbridge components;

Send the target calling information to the target native functional component through the target Jsbridge component, and the target native functional component and the target Jsbridge component are located in the same functional module;

Generate target response information of the target call information through the target native functional component;

The target response information is returned to the target front-end framework through the target Jsbridge component.

It should be understood that in this embodiment of the present application, the processor 302 may be a central processing unit (Central Processing Unit, CPU). The processor 302 may also be other general-purpose processors, digital signal processors (Digital Signal Processor, DSP), dedicated integrated processors, etc. Circuit (Application Specific Integrated Circuit, ASIC), off-the-shelf programmable gate array (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general processor may be a microprocessor or the processor may be any conventional processor.

Those of ordinary skill in the art can understand that all or part of the processes in the methods of implementing the above embodiments can be completed by instructing relevant hardware through a computer program. The computer program includes program instructions, and the computer program can be stored in a storage medium, and the storage medium is a computer-readable storage medium. The program instructions are executed by at least one processor in the computer system to implement the process steps of the embodiments of the above method.

Therefore, this application also provides a storage medium. The storage medium may be a computer-readable storage medium. The storage medium stores a computer program, where the computer program includes program instructions. When executed by the processor, the program instructions cause the processor to perform the following steps:

Obtain the target call request through the preset target front-end framework, and the target call request includes the target Jsbridge identification and target call information;

Determine the target Jsbridge component corresponding to the target Jsbridge identifier from a plurality of the Jsbridge components;

Send the target calling information to the target native functional component through the target Jsbridge component, and the target native functional component and the target Jsbridge component are located in the same functional module;

Generate target response information of the target call information through the target native functional component;

The target response information is returned to the target front-end framework through the target Jsbridge component.

The storage medium may be a U disk, a mobile hard disk, a read-only memory (Read-Only Memory, ROM), a magnetic disk or an optical disk, and other computer-readable storage media that can store program codes.

Those of ordinary skill in the art can appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented with electronic hardware, computer software, or a combination of both. In order to clearly illustrate the relationship between hardware and software Interchangeability, in the above description, the composition and steps of each example have been generally described according to functions. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each specific application, but such implementations should not be considered beyond the scope of this application.

In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of each unit is only a logical function division, and there may be other division methods during actual implementation. For example multiple units or components may be combined or integrated into another system, or some features may be omitted, or not implemented.

The steps in the methods of the embodiments of this application can be sequence adjusted, combined, and deleted according to actual needs. The units in the device of the embodiment of the present application can be merged, divided, and deleted according to actual needs. In addition, each functional unit in various embodiments of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.

If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a storage medium. Based on this understanding, the technical solution of the present application is essentially or contributes to the existing technology, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium , including several instructions to cause an electronic device (which may be a personal computer, terminal, or network device, etc.) to execute all or part of the steps of the methods described in various embodiments of this application.

The above are only specific embodiments of the present application, but the protection scope of the present application is not limited thereto. Any person familiar with the technical field can easily think of various equivalent methods within the technical scope disclosed in the present application. Modification or replacement, these modifications or replacements shall be covered by the protection scope of this application. Therefore, the protection scope of this application should be subject to the protection scope of the claims.

Claims (10)

1. A method of calling native functional components, characterized in that the method is applied to a native functional component calling framework of an electronic device, and the native functional component calling framework includes a plurality of functional modules, each of which includes a native functional component. Functional components and Jsbridge components matching the native functional components, the method includes: Obtain the target call request through the preset target front-end framework, and the target call request includes the target Jsbridge identification and target call information; Determine the target Jsbridge component corresponding to the target Jsbridge identifier from a plurality of the Jsbridge components; Send the target calling information to the target native functional component through the target Jsbridge component, and the target native functional component and the target Jsbridge component are located in the same functional module; Generate target response information of the target call information through the target native functional component; The target response information is returned to the target front-end framework through the target Jsbridge component. 2. The method according to claim 1, characterized in that the native function component calling framework further includes a registry, and the registry includes a mapping relationship between the Jsbridge identifier of each Jsbridge component and the calling code; Determining the target Jsbridge component corresponding to the target Jsbridge identifier from the plurality of Jsbridge components includes: Determine the target calling code corresponding to the target Jsbridge identifier from the registry; Based on the target calling code, the target Jsbridge component is reflectively called from a plurality of the Jsbridge components. 3. The method according to claim 2, characterized in that the native functional component calling framework includes a container layer, an intermediate calling layer and an independent function module layer, and the container layer includes multiple business framework containers, and different business frameworks Containers carry different types of front-end frameworks. The intermediate call layer includes call entrances and the registration table corresponding to each business framework container. The independent function module layer includes a plurality of the function modules. 4. The method according to claim 3, wherein the target front-end frame is a page frame corresponding to a target page in a plurality of the front-end frames, and the target page is a page currently displayed by the electronic device, so The target page includes at least one call control of the native functional component; the obtaining the target call request through the preset target front-end framework includes: Receive a user's calling operation for a target calling control, which is a calling control used to call the target native functional component in at least one of the calling controls; The target calling information is obtained based on the calling operation, and the target calling request is generated according to the target Jsbridge identifier bound to the target calling control and the target calling information. 5. The method according to claim 3, characterized in that the front-end framework in the business framework container includes a webview business framework, a weex business framework or a flutter business framework. 6. The method according to claim 2, characterized in that, before determining the target calling code corresponding to the target Jsbridge identifier from the registry, the method further includes: Determine whether the target Jsbridge identifier exists in the registry; Determining the target calling code corresponding to the target Jsbridge identifier from the registry includes: If the target Jsbridge identifier exists in the registry, the calling code corresponding to the target Jsbridge identifier in the registry is determined as the target calling code. 7. The method according to claim 6, wherein after determining whether the target Jsbridge identifier exists in the registry, the method further includes: If the target Jsbridge identifier does not exist in the preset registry, a call failure message is returned to the target front-end framework. 8. A native functional component calling framework, characterized in that the native functional component calling framework is deployed in an electronic device, and the native functional component calling framework includes a container layer, an intermediate calling layer and an independent functional module layer, and the container The layer includes multiple business framework containers, and different business frame containers carry different types of front-end frameworks. The intermediate call layer includes call entrances and registration tables corresponding to each of the business frame containers. The independent function module layer includes multiple Each functional module includes a native functional component and a Jsbridge component matching the native functional component, where: The container layer is used to obtain a target call request through a target front-end framework in multiple front-end frameworks, where the target call request includes a target Jsbridge identifier and target call information; The intermediate calling layer is used to determine the target Jsbridge component corresponding to the target Jsbridge identifier from a plurality of the Jsbridge components according to the registration table; The independent function module layer is used to send the target call information to the target native function component through the target Jsbridge component, and the target native function component and the target Jsbridge component are located in the same functional module; through the target The native functional component generates target response information of the target call information; and returns the target response information to the target front-end framework through the target Jsbridge component. 9. An electronic device. A native functional component calling framework is deployed in the electronic device. The native functional component calling framework includes a plurality of functional modules. Each of the functional modules includes a native functional component and a native functional component. Matching Jsbridge components, the electronic device includes a memory, a processor and a computer program stored on the memory and executable on the processor. The feature is that the native function component calling framework executes all operations through the processor. The computer program implements the calling method of the native functional component as described in any one of claims 1-7. 10. A storage medium, characterized in that the storage medium stores a computer program, the computer program includes program instructions, and when executed by a processor, the program instructions cause the processor to execute claims 1-7 The calling method of any of the native functional components described above.