WO2024061036A1 - Inter-engine communication method and related device - Google Patents

Abstract

Embodiments of the present application disclose an inter-engine communication method and a related device, which are characterized by being applied to an operating system. The operating system comprises a first engine, a second engine and a bridging layer, the first engine comprising multiple first objects, and the second engine comprising multiple second objects. The method comprises: receiving a first request sent by the first engine by means of the bridging layer, the first request being used to request execution of a number N of first objects among the multiple first objects, N being an integer greater than 0; by means of the bridging layer, and in response to the first request, determining whether there are N second objects which are the same as the N first objects among the multiple second objects; if so, sending a second request to the second engine by means of the bridging layer, the second request being used to request that the second engine execute the N second objects according to a corresponding function parameter. Using an embodiment of the present application, communication between different engines may be implemented.

Description

Inter-engine communication method and related equipment

This application claims priority to the Chinese patent application submitted to the China Patent Office on September 19, 2022, with application number 202211137787.7 and the application title "An inter-engine communication method and related equipment", the entire content of which is incorporated by reference. in this application.

Technical field

The present application relates to the field of computer technology, and in particular, to an inter-engine communication method and related equipment.

Background technique

Ets is an extensible TS (TypeScript) language and the main development language for Hongmeng applications. It has the advantages of ecological integration with JS (JavaScript), efficient type system, and concise and efficient declarative development paradigm. In order to further expand the Hongmeng ecosystem, it is necessary to introduce the Web ecosystem. The Web ecosystem is mainly developed in HTML5 (H5) language. H5 pages are loaded and displayed through the web components in Hongmeng's Ark development framework (ArkUI).

The Hongmeng Ets code runs in the JS runtime of the Ark engine, and the H5 JS code runs in the JS runtime of the V8 engine of the WebView. Since the two languages run in different JS engines, it can also be understood that the two languages run in two independent sandbox-isolated contexts, resulting in the inability to communicate directly between H5 and Ets. In H5, it is impossible to reuse the Application Programming Interface (API) customized by developers on the Ets side or the Hongmeng system, which seriously affects the promotion and expansion of the Hongmeng application ecosystem.

Therefore, how to provide an inter-engine communication method and related equipment to realize communication between different engines, such as realizing information exchange between the H5 side and the Ets side, is an issue that needs to be solved urgently.

Contents of the invention

The technical problem to be solved by the embodiments of this application is to provide an inter-engine communication method and related equipment to realize communication between different JS engines.

In the first aspect, the implementation example of this application provides a communication method between engines, which is characterized in that it is applied to an operating system. The operating system includes a first engine, a second engine and a bridging layer. The first engine includes multiple a first object, the second engine includes a plurality of second objects, and the method includes: receiving a first request sent by the first engine through the bridging layer, the first request being used to request execution of the plurality of second objects. N first objects among the first objects, N is an integer greater than 0; in response to the first request, the bridging layer determines whether there are any of the plurality of second objects that are the same as the N first objects. N second objects with the same object; if they exist, send a second request to the second engine through the bridging layer, where the second request is used to request the second engine to execute the N according to the corresponding function parameters. a second object.

In this embodiment of the present invention, a bridge layer can be added between the first engine and the second engine to realize communication between different engines through the bridge layer. Specifically, the first application can be run on the first engine, and the first application can include multiple first objects; the second application can be run on the second engine, and the second application can include multiple second objects, and The first application and the second application run in two different contexts. Further, during the operation of the two engines, the first engine can send a request to execute one or more first objects to the bridging layer, and then the bridging layer determines whether there are multiple second objects that match the one or more first objects mentioned above. If a second object with the same object exists, the bridging layer will send a request to the second engine to execute the corresponding one or more second objects, and the request may include function parameters that need to be used during the execution process, so that the second object The engine can execute the corresponding second object based on the function parameters, realizing cross-engine communication. In this application, it is avoided to directly register the objects of the second engine in the first engine, and the information interaction between two different engines is efficiently realized through the bridging layer. Therefore, on the premise of ensuring security, the two operations are solved. The problem is that environments are isolated from each other and cannot call each other's objects (or functions).

In a possible implementation, determining whether there are N second objects that are the same as the N first objects among the plurality of second objects includes: determining whether among the plurality of second objects There are N second objects that have the same object identifiers as the N first objects; wherein, if they exist, the N second objects are the same as the N first objects.

In the embodiment of the present invention, the bridging layer can obtain the object names (also called object identifiers) of multiple first objects from the first engine, and the bridging layer can also obtain the objects of multiple second objects from the second engine. name. Further, when the bridging layer receives the request sent by the first engine, it can determine whether there are N second objects with the same object names as the N first objects in the request among the multiple second objects. If they exist, the bridge layer The layer can send an execution request to the second engine, so that the first engine can call the second engine through the bridging layer during operation. object. In this application, it is avoided to directly register the objects of the second engine in the first engine, and the information interaction between two different engines is efficiently realized through the bridging layer. Therefore, on the premise of ensuring security, the two operations are solved. The problem is that environments are isolated from each other and cannot call each other's objects (or functions).

In a possible implementation, determining whether there are N second objects that are the same as the N first objects among the plurality of second objects includes: determining whether among the plurality of second objects There are N second objects that have the same object identifiers as the N first objects; if they exist, the first function included in each of the N first objects is determined through the first record table; so The first record table includes the first function included in each first object among the plurality of first objects; based on the second record table, determine all the first functions included in each first object among the N first objects. Whether the first function is consistent with the second function included in each second object in the N second objects; wherein, if they are consistent, there is a function in the plurality of second objects that is the same as the N first objects. The N second objects; the second record table includes a second function included in each of the second objects.

In the embodiment of the present invention, the bridging layer not only needs to determine whether the object names are the same, but also needs to determine whether the functions under the object names are the same by looking up the table. If they are the same, the bridging layer can send an execution request to the second engine, so as to achieve running During the process, the first engine can call objects in the second engine through the bridging layer. In this application, it is avoided to directly register the objects of the second engine in the first engine, and the information interaction between two different engines is efficiently realized through the bridging layer. Therefore, on the premise of ensuring security, the two operations are solved. The problem is that environments are isolated from each other and cannot call each other's objects (or functions).

In a possible implementation, the method further includes: obtaining an object identifier corresponding to each of the plurality of first objects through the bridging layer, and each of the first objects includes: The first function generates the first record table; the object identifier corresponding to each second object in the plurality of second objects is obtained through the bridging layer, and each second object includes The second function generates the second record table.

In the embodiment of the present invention, the bridging layer can obtain the object names (also called object identifiers) of multiple first objects and the function names under the object names from the first engine and generate the first record table. The bridging layer can also The object names of multiple second objects and the function names under the object names are obtained from the second engine and a second record table is generated. Then the bridging layer can determine the names under the object names in the request based on the first record table and the second record table. functions are the same. In this application, it is avoided to directly register the objects of the second engine in the first engine, and the information interaction between two different engines is efficiently realized through the bridging layer. Therefore, on the premise of ensuring security, the two operations are solved. The problem is that environments are isolated from each other and cannot call each other's objects (or functions).

In a possible implementation, the method further includes: in response to the second request, executing the N second objects according to the corresponding function parameters through the second engine, and generating the Nth The execution results corresponding to the two objects are forwarded to the first engine through the bridging layer, and the execution results corresponding to the N second objects sent by the second engine are forwarded.

In the embodiment of the present invention, the second engine can respond to the request of the bridge layer, execute the corresponding second object based on the function parameters, and generate the corresponding execution result, and then forward the execution result to the first engine through the bridge layer, thereby Implement cross-engine data interaction. In this application, it is avoided to directly register the objects of the second engine in the first engine, and the information interaction between two different engines is efficiently realized through the bridging layer. Therefore, on the premise of ensuring security, the two operations are solved. The environment is isolated from each other, unable to call each other's objects (or functions), and cannot transfer data.

In a possible implementation, the method further includes: if the N second objects that are the same as the N first objects do not exist among the plurality of second objects, through the bridging layer A first notification is sent to the first engine, where the first notification includes a message of execution errors of the N first objects.

In this embodiment of the present invention, if the same object does not exist, it means that the second engine cannot execute the object in the request, and the first engine can be notified through the bridging layer that the object in the request will not be executed. In this application, it is avoided to directly register the objects of the second engine in the first engine, and the information interaction between two different engines is efficiently realized through the bridging layer. Therefore, on the premise of ensuring security, the two operations are solved. The environment is isolated from each other, unable to call each other's objects (or functions), and cannot transfer data.

In a second aspect, the present application provides an electronic device, characterized in that the electronic device runs an operating system, the operating system includes a first engine, a second engine and a bridging layer, and the first engine includes a plurality of third engines. An object, the second engine includes a plurality of second objects, the device includes: a first receiving unit configured to receive a first request sent by the first engine through the bridging layer, the first request is Upon requesting execution of N first objects among the plurality of first objects, N is an integer greater than 0; a first processing unit configured to respond to the first request through the bridging layer to determine whether the plurality of first objects are Whether there are N second objects that are the same as the N first objects in the second object; the first sending unit is used to, if there is, send a second request to the second engine through the bridging layer, so The second request is used to request the second engine to execute the N second objects according to corresponding function parameters.

In a possible implementation, the first processing unit is specifically configured to: determine whether the plurality of second objects is the same as the The object identifiers of the N first objects are the same N second objects; wherein, if they exist, the N second objects are the same as the N first objects.

In a possible implementation, the first processing unit is specifically configured to: determine whether there are N second objects among the plurality of second objects that have the same object identifiers as the N first objects; If it exists, determine the first function included in each first object among the N first objects through the first record table; the first record table includes the first function included in each first object among the plurality of first objects. The first function; based on the second record table, determine the first function included in each of the N first objects and the first function included in each of the N second objects. Whether the second function is consistent; wherein, if consistent, there are N second objects that are the same as the N first objects among the plurality of second objects; the second record table includes the second object The second function included in each second object.

In a possible implementation, the device further includes: a second receiving unit configured to obtain, through the bridging layer, the object identifier corresponding to each first object in the plurality of first objects, and each The first function included in each of the first objects generates the first record table; a third receiving unit is used to obtain each of the plurality of second objects through the bridging layer The corresponding object identifier and the second function included in each second object generate the second record table.

In a possible implementation, the device further includes: a second processing unit, configured to respond to the second request, execute the N second objects according to the corresponding function parameters through the second engine, and generate execution results corresponding to the N second objects; a second sending unit configured to forward to the first engine through the bridging layer all the execution results corresponding to the N second objects sent by the second engine. Describe the execution results.

In a possible implementation, the device further includes: a third sending unit, configured to: if there are no N second objects that are the same as the N first objects among the plurality of second objects, , then a first notification is sent to the first engine through the bridge layer, where the first notification includes execution error messages for the N first objects.

In a third aspect, the present application provides a computer storage medium, characterized in that the computer storage medium stores a computer program, and when the computer program is executed by a processor, it implements the method described in any one of the first aspects above.

In a fourth aspect, embodiments of the present application provide an electronic device, which includes a processor. The processor is configured to support the electronic device in implementing corresponding functions in the inter-engine communication method provided in the first aspect. The electronic device may also include a memory coupled to the processor that stores necessary program instructions and data for the electronic device. The electronic device may also include a communication interface for the electronic device to communicate with other devices or communication networks.

In a fifth aspect, the present application provides a chip system that includes a processor to support the electronic device to implement the functions involved in the above-mentioned first aspect, for example, generating or processing those involved in the above-mentioned inter-engine communication method. Information. In a possible design, the chip system further includes a memory, and the memory is used to store necessary program instructions and data of the electronic device. The chip system may be composed of chips, or may include chips and other separate components.

In a sixth aspect, the present application provides a computer program, characterized in that the computer program includes instructions that, when the computer program is executed by a computer, cause the computer to perform any of the methods described in the first aspect. .

Description of drawings

FIG. 1 is a schematic structural diagram of an electronic device 100 provided by an embodiment of the present invention.

Figure 2 is a schematic diagram of a system architecture for cross-engine communication provided by an embodiment of the present invention.

Figure 3 is a schematic flowchart of an inter-engine communication method in an embodiment of the present application.

Figure 4 is a schematic diagram of the interaction between the H5 side and the Ets side provided by an embodiment of the present invention.

FIG. 5 is a schematic diagram of an interface of an electronic device provided by an embodiment of the present invention.

Figure 6 is a schematic flow chart of interaction between the H5 side and the Ets side provided by an embodiment of the present invention.

FIG. 7 is a schematic diagram of an electronic device provided by this application according to an embodiment of the present invention.

Detailed ways

The embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application.

The terms “first”, “second”, “third” and “fourth” in the description, claims and drawings of this application are used to distinguish different objects, rather than to describe a specific sequence. . Furthermore, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but optionally also includes steps or units that are not listed, or optionally also includes Other steps or units inherent to such processes, methods, products or devices.

Reference herein to "an embodiment" means that a particular feature, structure or characteristic described in connection with the embodiment can be included in at least one embodiment of the present application. The appearances of this phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. Those skilled in the art understand, both explicitly and implicitly, that the embodiments described herein may be combined with other embodiments.

FIG. 1 shows a schematic structural diagram of an electronic device 100 .

The following uses the electronic device 100 as an example to describe the embodiment in detail. It should be understood that electronic device 100 may have more or fewer components than shown in the figures, may combine two or more components, or may have a different component configuration. The various components shown in the figures may be implemented in hardware, software, or a combination of hardware and software including one or more signal processing and/or application specific integrated circuits.

The electronic device 100 may include: a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2. Mobile communication module 150, wireless communication module 160, audio module 170, speaker 170A, receiver 170B, microphone 170C, headphone interface 170D, sensor module 180, button 190, motor 191, indicator 192, camera 193, display screen 194, And subscriber identification module (subscriber identification module, SIM) card interface 195, etc. Among them, the sensor module 180 may include a pressure sensor 180A, a gyro sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, and an environment. Light sensor 180L, bone conduction sensor 180M, etc.

It can be understood that the structure illustrated in the embodiment of the present invention does not constitute a specific limitation on the electronic device 100 . In other embodiments of the present application, the electronic device 100 may include more or fewer components than shown in the figures, or some components may be combined, some components may be separated, or some components may be arranged differently. The components illustrated may be implemented in hardware, software, or a combination of software and hardware.

The processor 110 may include one or more processing units. For example, the processor 110 may include an application processor (application processor, AP), a modem processor, a graphics processing unit (GPU), and an image signal processor. (image signal processor, ISP), controller, memory, video codec, digital signal processor (digital signal processor, DSP), baseband processor, and/or neural-network processing unit (NPU) wait. Among them, different processing units can be independent devices or integrated in one or more processors.

The controller may be the nerve center and command center of the electronic device 100 . The controller can generate operation control signals based on the instruction operation code and timing signals to complete the control of fetching and executing instructions.

The processor 110 may also be provided with a memory for storing instructions and data. In some embodiments, the memory in processor 110 is cache memory. This memory may hold instructions or data that have been recently used or recycled by processor 110 . If the processor 110 needs to use the instructions or data again, it can be called directly from the memory. Repeated access is avoided and the waiting time of the processor 110 is reduced, thus improving the efficiency of the system.

In some embodiments, processor 110 may include one or more interfaces. Interfaces may include integrated circuit (inter-integrated circuit, I2C) interface, integrated circuit built-in audio (inter-integrated circuit sound, I2S) interface, pulse code modulation (pulse code modulation, PCM) interface, universal asynchronous receiver and transmitter (universal asynchronous receiver/transmitter (UART) interface, mobile industry processor interface (MIPI), general-purpose input/output (GPIO) interface, subscriber identity module (SIM) interface, and /or universal serial bus (USB) interface, etc.

It can be understood that the interface connection relationships between the modules illustrated in the embodiment of the present invention are only schematic illustrations and do not constitute a structural limitation of the electronic device 100 . In other embodiments of the present application, the electronic device 100 may also adopt different interface connection methods in the above embodiments, or a combination of multiple interface connection methods.

The charging management module 140 is used to receive charging input from the charger. Among them, the charger can be a wireless charger or a wired charger.

The power management module 141 is used to connect the battery 142, the charging management module 140 and the processor 110. The power management module 141 receives input from the battery 142 and/or the charging management module 140, and supplies power to the processor 110, internal memory 121, external memory, display screen 194, camera 193, wireless communication module 160, etc.

The wireless communication function of the electronic device 100 can be implemented through the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modem processor and the baseband processor.

The electronic device 100 implements display functions through a GPU, a display screen 194, an application processor, and the like. The GPU is an image processing microprocessor and is connected to the display screen 194 and the application processor. GPUs are used to perform mathematical and geometric calculations for graphics rendering. Processor 110 may include one or more GPUs that execute program instructions to generate or alter display information.

The display screen 194 is used to display images, videos, etc. Display 194 includes a display panel. The display panel can use a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active matrix organic light emitting diode or an active matrix organic light emitting diode (active-matrix organic light emitting diode). emitting diode (AMOLED), flexible light-emitting diode (FLED), Miniled, MicroLed, Micro-oLed, quantum dot light emitting diode (QLED), etc. In some embodiments, the electronic device 100 may include 1 or N display screens 194, where N is a positive integer greater than 1.

The electronic device 100 can implement the shooting function through an ISP, a camera 193, a video codec, a GPU, a display screen 194, an application processor, and the like.

ISP is used to process the data fed back by camera 193. For example, when taking a photo, the shutter is opened, and the light is transmitted to the camera photosensitive element through the lens. The light signal is converted into an electrical signal, and the camera photosensitive element transmits the electrical signal to ISP for processing and converts it into an image visible to the naked eye. ISP can also perform algorithm optimization on the noise, brightness, and skin color of the image. ISP can also optimize the exposure, color temperature and other parameters of the shooting scene. In some embodiments, ISP can be set in camera 193.

The camera 193 is used to capture still images or videos. The object generates an optical image through the lens and projects it onto the photosensitive element. The photosensitive element can be a charge coupled device (CCD) or a complementary metal oxide semiconductor (CMOS) phototransistor. The photosensitive element converts the optical signal into an electrical signal, and then transmits the electrical signal to the ISP to convert it into a digital image signal. The ISP outputs the digital image signal to the DSP for processing. The DSP converts the digital image signal into an image signal in a standard RGB, YUV or other format. In some embodiments, the electronic device 100 may include other cameras. The electronic device may also include a dot matrix transmitter (not shown in the figure) for emitting light. The camera collects light reflected from the face to obtain a face image, and the processor processes and analyzes the face image, and verifies it by comparing it with the stored face image information.

Digital signal processors are used to process digital signals. In addition to digital image signals, they can also process other digital signals. For example, when the electronic device 100 selects a frequency point, the digital signal processor is used to perform Fourier transform on the frequency point energy.

Video codecs are used to compress or decompress digital video. Electronic device 100 may support one or more video codecs. In this way, the electronic device 100 can play or record videos in multiple encoding formats, such as moving picture experts group (MPEG) 1, MPEG2, MPEG3, MPEG4, etc.

NPU is a neural network (NN) computing processor. By drawing on the structure of biological neural networks, for example, drawing on the transmission mode between neurons in the human brain, it can quickly process input information and can also continuously self-learn. Through NPU, applications such as intelligent cognition of electronic device 100 can be realized, such as image recognition, face recognition, voice recognition, text understanding, etc.

The external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device 100. The external memory card communicates with the processor 110 through the external memory interface 120 to implement the data storage function. Such as saving music, videos, etc. files in external memory card.

Internal memory 121 may be used to store computer executable program code, which includes instructions. The processor 110 executes instructions stored in the internal memory 121 to execute various functional applications and data processing of the electronic device 100 . The internal memory 121 may include a program storage area and a data storage area. Among them, the stored program area can store the operating system and at least one application required for the function (such as face recognition function, fingerprint recognition function, mobile payment function, etc.). The storage data area can store data created during the use of the electronic device 100 (such as face information template data, fingerprint information templates, etc.). In addition, the internal memory 121 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, universal flash storage (UFS), etc.

The electronic device 100 can implement audio functions through the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the headphone interface 170D, and the application processor. Such as music playback, recording, etc.

The audio module 170 is used to convert digital audio information into analog audio signal output, and is also used to convert analog audio input into digital audio signals.

Speaker 170A, also called "speaker", is used to convert audio electrical signals into sound signals.

Receiver 170B, also called "earpiece", is used to convert audio electrical signals into sound signals.

Microphone 170C, also called "microphone" or "microphone", is used to convert sound signals into electrical signals.

The headphone interface 170D is used to connect wired headphones. The headphone interface 170D may be a USB interface 130, or may be a 3.5mm open mobile terminal platform (OMTP) standard interface, or a Cellular Telecommunications Industry Association of the USA (CTIA) standard interface.

The pressure sensor 180A is used to sense the pressure signal and convert the pressure signal into an electrical signal. In some embodiments, the pressure sensor 180A can be disposed on the display screen 194. There are many types of pressure sensors 180A, such as resistive pressure sensors, inductive pressure sensors, Capacitive pressure sensor, etc.

The gyro sensor 180B may be used to determine the motion posture of the electronic device 100 . In some embodiments, the angular velocity of electronic device 100 about three axes (ie, x, y, and z axes) may be determined by gyro sensor 180B.

Proximity light sensor 180G may include, for example, a light emitting diode (LED) and a light detector, such as a photodiode. The light emitting diode may be an infrared light emitting diode.

The ambient light sensor 180L is used to sense ambient light brightness. The electronic device 100 can adaptively adjust the brightness of the display screen 194 according to the perceived ambient light brightness. The ambient light sensor 180L can also be used to automatically adjust the white balance when taking pictures.

Fingerprint sensor 180H is used to collect fingerprints. The electronic device 100 can use the collected fingerprint characteristics to achieve fingerprint unlocking, access to application locks, fingerprint photography, fingerprint answering of incoming calls, etc. The fingerprint sensor 180H can be disposed below the touch screen. The electronic device 100 can receive the user's touch operation on the area corresponding to the fingerprint sensor on the touch screen. The electronic device 100 can respond to the touch operation and collect the fingerprint of the user's finger. information.

Temperature sensor 180J is used to detect temperature. In some embodiments, the electronic device 100 utilizes the temperature detected by the temperature sensor 180J to execute the temperature processing strategy.

Touch sensor 180K, also called "touch panel". The touch sensor 180K can be disposed on the display screen 194. The touch sensor 180K and the display screen 194 form a touch screen, which is also called a "touch screen". The touch sensor 180K is used to detect a touch operation on or near the touch sensor 180K. The touch sensor can pass the detected touch operation to the application processor to determine the touch event type. Visual output related to the touch operation may be provided through display screen 194 . In other embodiments, the touch sensor 180K may also be disposed on the surface of the electronic device 100 at a location different from that of the display screen 194 .

The buttons 190 include a power button, a volume button, etc. Key 190 may be a mechanical key. It can also be a touch button. The electronic device 100 may receive key inputs and generate key signal inputs related to user settings and function control of the electronic device 100 .

The indicator 192 may be an indicator light, which may be used to indicate charging status, power changes, or may be used to indicate messages, missed calls, notifications, etc.

The SIM card interface 195 is used to connect a SIM card. The SIM card can be connected to or separated from the electronic device 100 by inserting it into the SIM card interface 195 or pulling it out from the SIM card interface 195 . In some embodiments, the electronic device 100 uses an eSIM, that is, an embedded SIM card. The eSIM card can be embedded in the electronic device 100 and cannot be separated from the electronic device 100 .

The embodiments of the present application are described below with reference to the accompanying drawings.

Based on the technical issues raised above and to facilitate understanding of the embodiments of the present invention, the system architecture on which the embodiments of the present invention are based is first described below. Please refer to Figure 2. Figure 2 is a schematic diagram of a cross-engine communication system architecture provided by an embodiment of the present invention. This system can be run in the software system of the above-mentioned electronic device 100 and can solve the problem that different JS engines cannot communicate with each other during operation. question. The system architecture can include Ark JS engine module (Ark JavaScript Engine), Ark development architecture module (ArkUI Framework), H5JS engine module, JS engine bridge module, JS method identification module, and fault tolerance module. Among them, the Ark JS engine module can be responsible for executing JS code, parsing and generating Abstract Syntax Tree (AST), converting it into bytecode, and generating machine code, etc., and executing the machine code and passing the execution results to the Framework of ArkUI Module; ArkUI Framework module can be responsible for interacting with the JS engine, page life cycle management, event distribution, loading UI components, routing jumps, data binding, etc.; the H5JS engine module can be responsible for parsing and executing H5 JS code, and executing the JS The object name, function name, and function parameters are passed to the JS engine bridge module; the JS engine bridge module can be responsible for monitoring the object name, method name (also called function name), and function parameters passed by the Ark engine and the H5 JS engine. Function execution results and other messages will be described in detail later on how to implement communication between different engines based on the JS engine bridge module. I will not go into details here; the JS method identification module can be responsible for obtaining the H5 side and Ets side method names from the JS engine bridge module. , determine whether the JS method on the H5 side is the same as the method on the Ets side; the fault tolerance module can be responsible for processing illegal input on the H5 side, and monitor the existence of the method in Ets in real time, completing fault tolerance protection on the application side to avoid abnormal situations.

The specific method architecture based on the embodiment of the present invention is described below.

Please refer to Figure 3, which is a flow diagram of a method for communicating between engines in an embodiment of the present application. The following will be combined with Figure 3 and based on the system architecture of cross-engine communication in Figure 2 above to describe the method for communicating between engines in an embodiment of the present application from the interaction side. The method is applied to an operating system, the operating system includes a first engine, a second engine and a bridging layer, the first engine includes a plurality of first objects, the second engine includes a plurality of second objects, the plurality of first objects are objects running in a first application, the plurality of second objects are objects running in a second application, the first application and the second application are two different applications, that is, the first application and the second application run in two different contexts. The method can be used to solve the problem that different engines cannot communicate with each other at run time. It should be noted that in order to describe the method for communicating between engines in an embodiment of the present application in more detail, the present application describes the corresponding execution subject in each process step, and the electronic device (which can be the electronic device 100 in Figure 1 above) is described, but it does not mean that the embodiment of the present application can only perform the corresponding method flow through the described execution subject.

Step S201: The electronic device receives the first request sent by the first engine through the bridge layer.

Specifically, the first request is used to request execution of N first objects among the plurality of first objects, where N is an integer greater than 0. The first engine can be the H5JS engine on the H5 side mentioned above, and the H5JS engine can be used to parse and execute H5 JS code.

Step S202: The electronic device responds to the first request through the bridge layer and determines whether there are N second objects that are the same as the N first objects among the plurality of second objects.

Specifically, when the bridging layer receives the first request sent by the first engine, it determines the target object requested to be executed in the first request, that is, N first objects, and then the bridging layer determines whether any of the multiple second objects of the second engine There is a second object that is identical to the target object. The second engine can be the Ark JS engine on the Ets side mentioned above. The Ark JS engine can be used to execute JS code, parse and generate abstract syntax trees, convert it into bytecode, and generate machine code, etc.

In a possible implementation, determining whether there are N second objects that are the same as the N first objects among the plurality of second objects includes: determining whether among the plurality of second objects There are N second objects that have the same object identifiers as the N first objects; wherein, if they exist, the N second objects are the same as the N first objects.

Specifically, the bridge layer can obtain the object names (also called object identifiers) of multiple first objects from the first engine, and the bridge layer can also obtain the object names of multiple second objects from the second engine. Furthermore, after the bridge layer receives the request sent by the first engine, it can determine whether there are N second objects with the same object names as the N first objects in the request among the multiple second objects. If so, the bridge layer can send an execution request to the second engine, so that the first engine can call the objects in the second engine through the bridge layer during operation. In the present application, it is avoided to register the objects of the second engine directly in the first engine, and the information interaction between the two different engines is efficiently realized through the bridge layer. Therefore, under the premise of ensuring safety, the problem that the two operating environments are isolated from each other and cannot call each other's objects (or functions) is solved.

In a possible implementation, determining whether there are N second objects that are the same as the N first objects among the plurality of second objects includes: determining whether among the plurality of second objects There are N second objects that have the same object identifiers as the N first objects; if they exist, the first function included in each of the N first objects is determined through the first record table; so The first record table includes the first function included in each first object among the plurality of first objects; based on the second record table, determine all the first functions included in each first object among the N first objects. Whether the first function is consistent with the second function included in each second object in the N second objects; wherein, if they are consistent, there is a function in the plurality of second objects that is the same as the N first objects. The N second objects; the second record table includes a second function included in each of the second objects.

Specifically, the bridging layer not only needs to determine whether the object names are the same, but also needs to check the table to determine whether the functions under the object names are the same. If they are the same, the bridging layer can send an execution request to the second engine, thereby realizing the first execution during operation. The engine can call objects in the second engine through the bridging layer. In this application, it is avoided to directly register the objects of the second engine in the first engine, and the information interaction between two different engines is efficiently realized through the bridging layer. Therefore, on the premise of ensuring security, the two operations are solved. The problem is that environments are isolated from each other and cannot call each other's objects (or functions).

In a possible implementation, the method further includes: obtaining, through the bridging layer, an object identifier corresponding to each of the first objects in the plurality of first objects, and an object identifier included in each first object. The first function generates the first record table; and obtains, through the bridging layer, the object identifier corresponding to each second object in the plurality of second objects, and the information included in each second object. The second function generates the second record table.

Specifically, the bridge layer can obtain the object names (also called object identifiers) of multiple first objects and the function names under the object names from the first engine and generate a first record table, and the bridge layer can also obtain the object names of multiple second objects and the function names under the object names from the second engine and generate a second record table, and then the bridge layer can determine whether the functions under the object names in the request are the same based on the first record table and the second record table. In this application, it is avoided to register the objects of the second engine directly in the first engine, and the information interaction between the two different engines is efficiently realized through the bridge layer. Therefore, under the premise of ensuring safety, the problem that the two operating environments are isolated from each other and cannot call each other's objects (or functions) is solved.

For example, as shown in Figure 4, Figure 4 is a schematic diagram of the interaction between the H5 side and the Ets side provided by an embodiment of the present invention. It can be used on the JS engine side (i.e. the second engine) of ArkUI (Hongmeng's application development framework). Run the code on the Ets side) and H5's JS engine (i.e. the first engine, which can be used to run the code on the H5 side) build two mapping tables, and a bridge layer can be built between the two JS running environments for message transmission. Pass the parameters in the H5 function to the Ark engine side through callbacks, execute the JS method (also called a function) of the Ets object on the Ark engine side, and pass the execution result of the Ark engine back to the JS function in H5 through the bridging layer. , to realize the transmission of messages between H5 and Ets.

Specifically, the JS engine bridge module (which can be understood as the above-mentioned bridge layer) parses the object name and method name (also known as function name) customized by the developer on the Ark engine (i.e., the second engine) and registers them to obtain the object name included in the Ark engine and the method list under each object name (also known as function list) and record them in the second record table; the JS engine of WebView is connected to the JS engine of WebView through the JS engine bridge module. (i.e. the first engine) registers the above method (i.e. function); the H5 page executes the H5 method through the JS engine of WebView; the JS engine of WebView sends a request to the JS engine bridge module to determine whether the method exists; if the JS engine bridge module determines that the method exists based on the above second record table, the JS engine of WebView can be notified that the method exists; the JS engine of WebView sends an execution request to the JS engine bridge module and can carry the function parameters required in the execution process; the JS engine bridge module sends a request to execute the method to the Ark engine; the Ark engine executes the method and returns the result to the WebView kernel, and forwards it to the JS engine of WebView through the JS engine bridge module; the JS engine of WebView then passes the execution result back to the H5 page.

Step S203: If present, the electronic device sends a second request to the second engine through the bridge layer.

Specifically, the second request is used to request the second engine to execute the N second objects according to corresponding function parameters. The second request may include function parameters that need to be used in executing the N second requests.

In a possible implementation, the method further includes: in response to the second request, executing the N second objects according to the corresponding function parameters through the second engine, and generating the Nth The execution results corresponding to the two objects are forwarded to the first engine through the bridging layer, and the execution results corresponding to the N second objects sent by the second engine are forwarded.

Specifically, the second engine can respond to the request of the bridge layer, execute the corresponding second object based on the function parameters, and generate the corresponding execution results, and then forward the execution results to the first engine through the bridge layer, thereby realizing cross-engine Data interaction. In this application, it is avoided to directly register the objects of the second engine in the first engine, and the information interaction between two different engines is efficiently realized through the bridging layer. Therefore, on the premise of ensuring security, the two operations are solved. The environment is isolated from each other, unable to call each other's objects (or functions), and cannot transfer data.

Optionally, in response to the second request of the bridge layer, the second engine can determine again whether the corresponding object (or function) exists. If it exists, execute the corresponding object (or function) based on the function parameters; if not exists, the second engine will not execute the corresponding object (or function), and will notify the first engine of execution failure and return exception log information, thus completing fault-tolerance protection on the application side.

For example, as shown in Figure 5, Figure 5 is a schematic diagram of an interface of an electronic device provided by an embodiment of the present invention. In (a) of Figure 5, a first interface is displayed on the electronic device. The first interface can be the one currently opened by the browser. Page, users can implement real-time calculations on this interface. For example, the user inputs data 1 and 2. At this time, the first engine will send a request to call the addition operation (can be understood as a function) to the bridge layer. Further, the bridging layer will determine whether the function exists in the second engine. If it exists, the bridging layer will send the function parameters (such as 1 and 2) to the second engine. The second engine will execute the corresponding function based on the function parameters and will The execution results are sent to the first engine through the bridge layer. Finally, the execution result can be directly displayed on the electronic device as shown in (b) of Figure 5 . The communication method between engines provided by this application can not only solve the problem that the two operating environments are isolated from each other and cannot call each other's objects (or functions), but also can reduce the response delay in the scenario of frequent interaction between H5 and Ets, and the response is instantaneous. .

In a possible implementation, the method further includes: if the N second objects that are the same as the N first objects do not exist among the plurality of second objects, through the bridging layer A first notification is sent to the first engine, where the first notification includes a message of execution errors of the N first objects.

Specifically, if the same object does not exist, it means that the second engine cannot execute the object in the request, and then the first engine can be notified through the bridge layer that the object in the request will not be executed. In this application, the object of the second engine is avoided from being directly registered in the first engine, and the information interaction between the two different engines is efficiently realized through the bridge layer. Therefore, under the premise of ensuring security, the problem of the two operating environments being isolated from each other and unable to call each other's objects (or functions) and unable to transfer data is solved.

Next, the first engine is the JS engine of H5, and the second engine is the Ark engine of the Ets side. As shown in Figure 6, Figure 6 shows an interaction between the H5 side and the Ets side provided by an embodiment of the present invention. A schematic flow chart of the process, which describes the inter-engine communication method in the embodiment of the present application from the interactive side in conjunction with the system architecture of cross-engine communication in Figure 2 above. It should be noted that a mapping table can be implemented in this application mechanism, the ArkUI side only executes the Ets side methods, the H5 side executes the JS methods in H5, and passes the H5 object to the ArkUI side through the bridging layer. The ArkUI framework converts the object into an Ark engine object (JsValue object). And execute the JS method under the object defined by the developer on the Ets side; in this application, a bridging mechanism for the interaction between the H5JS engine and the ArkUI JS engine is also designed, which is responsible for passing the objects and method names of the Ark engine to the H5 JS engine. , after recognizing that the method exists, the JS engine bridge module passes the function parameters to the Ark engine. After the Ark engine executes the JS method according to the function parameters, the execution result is returned to the H5 JS engine, completing the mutual isolation of two different JS engines. Communication in the JS running environment; this application also designs a fault-tolerant protection mechanism for communication between H5 and Ark engines. By judging whether the executed JS method exists on the two different JS engine sides, if it does not exist, Ark's JS engine This method will not be executed, and the application side will be notified that the method does not exist, and exception log information will be returned to complete the fault tolerance protection of the application side. The detailed steps are as follows:

Step 1: Start the application. The Ark JS engine module executes the JS code of the application developer and parses the object name and method name customized by the developer. At the same time, the JS object and method names are passed to the ArkUI Framework module through the JS to C++ cross-language interface call.

Step 2: The ArkUI Framework module creates a C++ object based on information such as object name and method name, and binds the corresponding C++ object to the object. method, register the C++ function with the JS engine bridge module, save the object name and the method list under the object name into a hash table, and send it to the JS method identification module.

Step 3: The JS method identification module intelligently identifies whether the JS method in the JS engine in ArkUI exists and notifies the fault tolerance module.

Step 4: When the ArkUI JS engine module parses the objects and methods on the Ets side, when the H5 JS module starts the application and executes the H5 JS code, the H5 JS engine module will also parse the JS objects and method names used on the H5 side. The JS engine bridge module is used to determine whether the method under the object exists to notify the fault tolerance module.

Step 5: The fault tolerance module sends a message to the Ark JS engine module. If it recognizes that the corresponding method exists, it executes the corresponding JS method. If the method does not exist, it calls back to the application side through JS, and the user can be notified through a pop-up box that the executed method is invalid.

Step 6: The ArkUI JS engine module executes the JS method and returns the JS execution result to the JS engine bridge module. The JS engine bridge module will then pass the JS function execution result to the H5 JS engine through the registered callback;

Step 7: The H5 JS engine module returns the execution results to the H5 page, triggers page updates through data binding, updates the execution results on the H5 interface, and finally notifies the user.

In summary, in an embodiment of the present invention, a bridge layer can be added between the first engine and the second engine to realize communication between different engines through the bridge layer. Specifically, the first application can be run on the first engine, and the first application can include multiple first objects; the second application can be run on the second engine, and the second application can include multiple second objects, and the first application and the second application run in two different contexts. Further, during the operation of the two engines, the first engine can send a request to the bridge layer to execute one or more first objects, and then the bridge layer determines whether there is a second object that is the same as the one or more first objects in the multiple second objects. If so, the bridge layer sends a request to the second engine to execute the corresponding one or more second objects, and the request can include the function parameters needed to be used during the execution process, so that the second engine can execute the corresponding second object based on the function parameters, thereby realizing cross-engine communication. Since in this application, it is avoided to register the object of the second engine directly in the first engine, and the information interaction between the two different engines is efficiently realized through the bridge layer, so that under the premise of ensuring safety, the problem that the two operating environments are isolated from each other and cannot call each other's objects (or functions) is solved.

The method of the embodiment of the present invention is described in detail above, and the relevant equipment of the embodiment of the present invention is provided below.

Please refer to Figure 7. Figure 7 is a schematic diagram of an electronic device provided by this application according to an embodiment of the present invention. The electronic device 30 runs an operating system. The operating system includes a first engine, a second engine and a bridge layer. The first engine includes a plurality of first objects, and the second engine includes a plurality of second objects. The electronic device 30 may include a first receiving unit 301, a first processing unit 302, a first sending unit 303, a second receiving unit 304, a third receiving unit 305, a second processing unit 306, a second sending unit 307, a third Sending unit 308, where the detailed descriptions of each module are as follows.

The first receiving unit 301 is configured to receive a first request sent by the first engine through the bridge layer, where the first request is used to request execution of N first objects among the plurality of first objects, N is an integer greater than 0;

The first processing unit 302 is configured to respond to the first request through the bridging layer and determine whether there are N second objects that are the same as the N first objects among the plurality of second objects;

The first sending unit 303 is configured to, if present, send a second request to the second engine through the bridge layer. The second request is used to request the second engine to execute the N according to the corresponding function parameters. a second object.

In a possible implementation, the first processing unit 302 is specifically configured to determine whether there are N second objects among the plurality of second objects that have the same object identifiers as the N first objects. ; Wherein, if they exist, the N second objects are the same as the N first objects.

In a possible implementation, the first processing unit 302 is specifically configured to determine whether there are N second objects among the plurality of second objects that have the same object identifiers as the N first objects. ; If it exists, determine the first function included in each of the N first objects through the first record table; the first record table includes each first object in the plurality of first objects. The first function included; based on the second record table, determine the first function included in each of the N first objects and the first function included in each of the N second objects. Whether the second function of The second function included in each second object in the object.

In a possible implementation, the device further includes: a second receiving unit 304, configured to obtain the object identifier corresponding to each of the plurality of first objects through the bridging layer, and The first function included in each first object generates the first record table; the third receiving unit 305 is used to obtain each of the plurality of second objects through the bridging layer. The object identifiers corresponding to the two objects and the second function included in each second object are used to generate the second record table.

In a possible implementation, the device further includes: a second processing unit 306, configured to respond to the second request, execute the N second objects according to the corresponding function parameters through the second engine , and generate execution results corresponding to the N second objects; the second sending unit 307 is configured to forward the N second objects corresponding to the N second objects sent by the second engine to the first engine through the bridging layer. of The execution result.

In a possible implementation, the device further includes: a third sending unit 308, configured to: if the N second objects that are the same as the N first objects do not exist in the plurality of second objects, object, a first notification is sent to the first engine through the bridge layer, where the first notification includes execution error messages for the N first objects.

It should be noted that for the functions of each functional unit in the electronic device 30 described in the embodiment of the present invention, please refer to the relevant description of steps S201 to S203 in the method embodiment described in FIG. 3, and will not be described again here. .

The present application provides a computer storage medium, characterized in that the computer storage medium stores a computer program, and when the computer program is executed by a processor, any one of the above-mentioned inter-engine communication methods is implemented.

An embodiment of the present application provides an electronic device. The electronic device includes a processor. The processor is configured to support the electronic device to implement corresponding functions in any of the above inter-engine communication methods. The electronic device may also include a memory coupled to the processor that stores necessary program instructions and data for the electronic device. The electronic device may also include a communication interface for the electronic device to communicate with other devices or communication networks.

The present application provides a chip system, which includes a processor for supporting an electronic device to implement the functions involved above, for example, generating or processing information involved in the above-mentioned inter-engine communication method. In one possible design, the chip system also includes a memory, which is used to store program instructions and data necessary for the electronic device. The chip system can be composed of a chip, or it can include a chip and other separate devices.

The present application provides a computer program, which is characterized in that the computer program includes instructions, which when the computer program is executed by a computer, causes the computer to execute the above-mentioned inter-engine communication method.

In the above embodiments, each embodiment is described with its own emphasis. For parts that are not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

It should be noted that for the sake of simple description, the foregoing method embodiments are expressed as a series of action combinations. However, those skilled in the art should know that the present application is not limited by the described action sequence. Because according to this application, certain steps may be performed in other orders or simultaneously. Secondly, those skilled in the art should also know that the embodiments described in the specification are preferred embodiments, and the actions and modules involved are not necessarily necessary for this application.

In the several embodiments provided in this application, it should be understood that the disclosed device can be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the above units is only a logical function division. In actual implementation, there may be other divisions. For example, multiple units or components may be combined or integrated. to another system, or some features can be ignored, or not implemented. On the other hand, the coupling or direct coupling or communication connection between each other shown or discussed may be through some interfaces, and the indirect coupling or communication connection of the devices or units may be in electrical or other forms.

The units described above as separate components may or may not be physically separated. The components shown as units may or may not be physical units, that is, they may be located in one place, or they may be distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application can be integrated into one processing unit, each unit can exist physically alone, or two or more units can be integrated into one unit. The above integrated units can be implemented in the form of hardware or software functional units.

If the above-mentioned 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 computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a storage medium, including several instructions to enable a computer device (which can be a personal computer, server or network device, etc., specifically a processor in a computer device) to perform all or part of the steps of the above-mentioned methods in each embodiment of the present application. Among them, the aforementioned storage medium may include: U disk, mobile hard disk, magnetic disk, optical disk, read-only memory (Read-Only Memory, abbreviated: ROM) or random access memory (Random Access Memory, abbreviated: RAM) and other media that can store program codes.

As mentioned above, the above embodiments are only used to illustrate the technical solution of the present application, but not to limit it. Although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that they can still make the foregoing technical solutions. The technical solutions described in each embodiment may be modified, or some of the technical features may be equivalently substituted; however, these modifications or substitutions shall not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of each embodiment of the present application.

Claims (14)

A communication method between engines, characterized in that it is applied to an operating system. The operating system includes a first engine, a second engine and a bridging layer. The first engine includes a plurality of first objects. The second engine Including a plurality of second objects, the method includes: Receive a first request sent by the first engine through the bridging layer, where the first request is used to request execution of N first objects among the plurality of first objects, where N is an integer greater than 0; In response to the first request, the bridging layer determines whether there are N second objects that are the same as the N first objects among the plurality of second objects; If it exists, send a second request to the second engine through the bridging layer, where the second request is used to request the second engine to execute the N second objects according to the corresponding function parameters. The method of claim 1, wherein determining whether there are N second objects that are the same as the N first objects among the plurality of second objects includes: Determine whether there are N second objects among the plurality of second objects that have the same object identifiers as the N first objects; wherein, if they exist, the N second objects are the same as the N first objects. same. The method of claim 1, wherein determining whether there are N second objects that are the same as the N first objects among the plurality of second objects includes: Determine whether there are N second objects among the plurality of second objects that have the same object identifiers as the N first objects; If it exists, determine the first function included in each first object among the N first objects through the first record table; the first record table includes the first function included in each first object among the plurality of first objects. The first function of; Based on the second record table, determine whether the first function included in each of the N first objects is consistent with the second function included in each of the N second objects; wherein , if consistent, there are N second objects that are the same as the N first objects among the plurality of second objects; the second record table includes each of the second objects in the second object. The second function included by the object. The method of claim 3, further comprising: Obtain the object identifier corresponding to each first object among the plurality of first objects and the first function included in each first object through the bridging layer, and generate the first record table; The object identifier corresponding to each second object among the plurality of second objects and the second function included in each second object are obtained through the bridging layer, and the second record table is generated. The method according to any one of claims 1 to 4, characterized in that the method further comprises: In response to the second request, execute the N second objects according to the corresponding function parameters through the second engine, and generate execution results corresponding to the N second objects; The execution results corresponding to the N second objects sent by the second engine are forwarded to the first engine through the bridging layer. The method according to any one of claims 1-5, characterized in that the method further includes: If the N second objects that are the same as the N first objects do not exist among the plurality of second objects, a first notification is sent to the first engine through the bridging layer, and the first The notification includes a message of execution errors for the N first objects. An electronic device, characterized in that the electronic device runs an operating system, the operating system includes a first engine, a second engine and a bridging layer, the first engine includes a plurality of first objects, the second engine Including a plurality of second objects, the device includes: A first receiving unit configured to receive a first request sent by the first engine through the bridging layer, where the first request is used to request execution of N first objects among the plurality of first objects, where N is an integer greater than 0; A first processing unit configured to respond to the first request through the bridging layer to determine whether there are N second objects that are the same as the N first objects among the plurality of second objects; The first sending unit is configured to, if present, send a second request to the second engine through the bridging layer. The second request is used to request the second engine to execute the N functions according to the corresponding function parameters. Second object. The device of claim 7, wherein the first processing unit is specifically used to: Determine whether there are N second objects among the plurality of second objects that have the same object identifiers as the N first objects; wherein, if they exist, the N second objects are the same as the N first objects. same. The device of claim 7, wherein the first processing unit is specifically used to: Determine whether there are N second objects among the plurality of second objects that have the same object identifiers as the N first objects; If it exists, determine the first function included in each first object among the N first objects through the first record table; the first record table includes the first function included in each first object among the plurality of first objects. The first function of; Based on the second record table, determine whether the first function included in each of the N first objects is consistent with the second function included in each of the N second objects; wherein , if consistent, there are N second objects that are the same as the N first objects among the plurality of second objects; the second record table includes each of the second objects in the second object. The second function included by the object. The device of claim 9, further comprising: The second receiving unit is configured to obtain, through the bridging layer, the object identifier corresponding to each of the first objects in the plurality of first objects and the first function included in each of the first objects, and generate The first record table; A third receiving unit configured to obtain, through the bridging layer, the object identifier corresponding to each second object in the plurality of second objects and the second function included in each second object, and generate The second record table. The device according to any one of claims 7-10, characterized in that the device further includes: A second processing unit, configured to respond to the second request, execute the N second objects according to the corresponding function parameters through the second engine, and generate execution results corresponding to the N second objects; The second sending unit is configured to forward the execution results corresponding to the N second objects sent by the second engine to the first engine through the bridging layer. The device according to any one of claims 7-11, characterized in that the device further includes: A third sending unit configured to, if the N second objects that are the same as the N first objects do not exist among the plurality of second objects, send the first engine to the first engine through the bridging layer. A notification, the first notification includes execution error messages of the N first objects. A computer storage medium, characterized in that the computer storage medium stores a computer program, and when the computer program is executed by a processor, the method described in any one of claims 1-6 is implemented. A computer program, characterized in that the computer program includes instructions that when the computer program is executed by a computer, cause the computer to execute the method according to any one of claims 1-6.