WO2020057234A1

WO2020057234A1 - Engine isolation method, related device, and computer-readable storage medium

Info

Publication number: WO2020057234A1
Application number: PCT/CN2019/095120
Authority: WO
Inventors: 李森林
Original assignee: Oppo广东移动通信有限公司
Priority date: 2018-09-20
Filing date: 2019-07-08
Publication date: 2020-03-26
Also published as: CN109254793B; CN109254793A

Abstract

Disclosed are an engine isolation method, a related device, and a computer-readable storage medium. The engine isolation method is applied in a game platform. The game platform runs on a mobile terminal and comprises a system layer, a bridging layer, and a JS layer. The bridging layer connects the system layer to the JS layer, and encapsulates the system capability of the system layer. The method comprises: when a first game runs on a game platform, the bridging layer determines a JS engine corresponding to the system layer according to the system type thereof; the bridging layer invokes the JS engine corresponding to the system layer to process a game code of the first game running in the JS layer; the bridging layer exposes the encapsulated system capability for invoking by the JS layer. According to embodiments of the present application, the bridging layer is added to isolate the JS layer from the system layer and prevent the JS layer from directly interacting with the system layer, thereby reducing game development costs.

Description

Engine isolation method, related equipment and computer-readable storage medium

Technical field

The present invention relates to the technical field of mobile terminals, and in particular, to an engine isolation method, a mobile terminal, and a computer-readable storage medium.

Background technique

Small games developed based on the browser environment, such as H5 games (HTML5 games), are widely used on mobile terminals such as mobile phones because they have the advantage of not downloading and playing online directly.

At present, game developers develop game code based on the browser kernel. When the H5 game runs on a mobile terminal, it is limited by the browser development environment. It is necessary to use the browser kernel to parse and execute the JS file in the game. When the game is running on a mobile terminal, the JS layer and the system layer are generally used. The JS layer directly calls the system layer's capabilities to implement the game's functions. If the system layer is updated, the JS layer will also be updated accordingly, and the corresponding game code needs to be changed again, increasing the game development cost.

Summary of the Invention

The embodiments of the present application provide an engine isolation method, related equipment, and a computer-readable storage medium. Selecting different JS engines according to the system type can make full use of the built-in engine capabilities and reduce the cost of game development.

The first aspect of the embodiments of the present application provides an engine isolation method. The engine isolation method is applied to a game platform that runs on a mobile terminal. The game platform includes a system layer, a bridge layer, and a JS layer. A bridge layer connects the system layer and the JS layer, the bridge layer encapsulates the system capabilities of the system layer, and the method includes:

When the first game runs on the game platform, the bridge layer determines the JS engine corresponding to the system layer according to the system type of the system layer;

The bridge layer calls a JS engine corresponding to the system layer to process the game code of the first game running in the JS layer;

The bridging layer exposes the encapsulated system capability to the JS layer, and the encapsulated system capability is available for the JS layer to call.

The second aspect of the embodiments of the present application provides an engine isolation device. The engine isolation device is applied to a game platform. The game platform runs on a mobile terminal. The game platform includes a system layer, a bridge layer, and a JS layer. The bridge layer connects the system layer and the JS layer. The bridge layer encapsulates the system capabilities of the system layer. The engine isolation device includes a determination unit and a processing unit, where:

The determining unit is configured to determine a JS engine corresponding to the system layer according to a system type of the system layer when a first game runs on the game platform;

The processing unit is configured to call a JS engine corresponding to the system layer to process the game code of the first game running in the JS layer;

The processing unit is further configured to expose the encapsulated system capability to the JS layer, and the encapsulated system capability is for the JS layer to call.

A third aspect of the embodiments of the present application provides a mobile terminal, including a processor and a memory, where the memory is configured to store one or more programs, and the one or more programs are configured to be executed by the processor. The program includes steps for performing some or all of the steps as described in any method in the first aspect of the embodiments of the present application.

A fourth aspect of the embodiments of the present application provides a computer-readable storage medium, where the computer-readable storage medium is used to store a computer program for electronic data exchange, wherein the computer program causes a computer to execute the first aspect of the embodiment of the present application Some or all of the steps described in either method.

A fifth aspect of the embodiments of the present application provides a computer program product. The computer program product includes a non-transitory computer-readable storage medium storing a computer program, and the computer program is operable to cause a computer to execute the program as described in the first embodiment of the present application. Some or all of the steps described in any method in one aspect.

In the embodiment of the present application, when the first game runs on the game platform, the bridge layer determines the JS engine corresponding to the system layer according to the system type of the system layer; the bridge layer calls the JS engine corresponding to the system layer to run the The game code of a game is processed, the bridge layer exposes the encapsulated system capabilities to the JS layer, and the encapsulated system capabilities are called by the JS layer. The embodiment of the present application can add a bridge layer to isolate the JS layer from the system layer. The bridge layer can encapsulate the system capabilities of the system layer, and the encapsulated system capabilities can be used by the JS layer to avoid the JS layer directly interacting with the system layer. There is no need to adapt to the system layer, and the game code of the first game running in the JS layer does not need to adapt to a different type of system, which can reduce the game development cost.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to explain the technical solutions in the embodiments of the present application or the prior art more clearly, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings in the following description are merely These are some embodiments of the present invention. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without paying creative labor.

FIG. 1 is a schematic flowchart of an engine isolation method disclosed in an embodiment of the present application;

2 is a schematic diagram of distribution of a system layer, a bridge layer, and a JS layer disclosed in an embodiment of the present application;

3 is a schematic flowchart of another engine isolation method disclosed in an embodiment of the present application;

4 is a schematic flowchart of another engine isolation method disclosed in an embodiment of the present application;

5 is a schematic flowchart of another engine isolation method disclosed in an embodiment of the present application;

6 is a schematic flowchart of another engine isolation method disclosed in an embodiment of the present application;

7 is a schematic structural diagram of an engine isolation device disclosed in an embodiment of the present application;

8 is a schematic structural diagram of a mobile terminal disclosed in an embodiment of the present application;

FIG. 9 is a schematic structural diagram of still another mobile terminal disclosed in an embodiment of the present application.

detailed description

In order to enable those skilled in the art to better understand the solutions of the present invention, the technical solutions in the embodiments of the present application will be described clearly and completely in combination with the drawings in the embodiments of the present application. Obviously, the described embodiments are only It is a part of the embodiments of the present invention, but not all the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by a person of ordinary skill in the art without creative efforts shall fall within the protection scope of the present invention.

The terms "first", "second", and the like in the description and claims of the present invention and the above-mentioned drawings are used to distinguish different objects and are not used to describe a specific order. 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 containing 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 these processes, methods, products or equipment.

Reference to "an embodiment" herein means that a particular feature, structure, or characteristic described in connection with the embodiment may be included in at least one embodiment of the invention. The appearances of this phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are they independent or alternative embodiments that are mutually exclusive with other embodiments. It is explicitly and implicitly understood by those skilled in the art that the embodiments described herein may be combined with other embodiments.

The mobile terminals involved in the embodiments of the present application may include various handheld devices with wireless communication functions, vehicle-mounted devices, wearable devices, computing devices, or other processing devices connected to a wireless modem, and various forms of user equipment (User Equipment (UE), mobile station (MS), terminal device (terminal), and so on. For ease of description, the devices mentioned above are collectively referred to as mobile terminals.

The embodiments of the present application are described in detail below.

Please refer to FIG. 1. FIG. 1 is a schematic flowchart of an engine isolation method disclosed in an embodiment of the present application. As shown in FIG. 1, the engine isolation method includes the following steps.

101. When the first game runs on the game platform, the bridge layer determines the JS engine corresponding to the system layer according to the system type of the system layer.

In the embodiment of the present application, the game platform is a software module for running a game application, and can be run on a mobile terminal such as a mobile phone. The game platform includes a system layer, a bridge layer, and a JS (JavaScript) layer. As shown in FIG. 2, the system layer can be understood as the bottom layer and is responsible for providing system capabilities related to the bottom layer of the mobile terminal, such as the ability to access memory and the ability to make calls. The first game may be a small game developed based on a browser environment, such as an H5 game (HTML5 game). The JS layer can be understood as the upper layer, which is responsible for running the small game. The game code of the small game can be run in the JS layer. The JS layer can also be called the JavaScript layer. The bridge layer can be understood as an intermediate layer, which is used to connect the system layer and the JS layer. The bridge layer can encapsulate the capabilities of the system layer into a unified application programming interface (Application Programming Interface) that is directly called by the JS layer. The system layer, the bridge layer, and the JS layer in the embodiments of the present application can be understood as a piece of code. For example, the system layer can be a piece of program code written in assembly language; the bridge layer can be a piece of program code written in C ++; the bridge layer can also be called the C ++ layer; and the JS layer can be a piece of program code written in Java.

The engine isolation method of the present application can be applied to different game platforms, and the system types of different game platforms may be different. For example, the system of some game platforms is an Android system, and the system of some game platforms is an IOS system. The bridge layer determines the JS engine corresponding to the system layer according to the system type of the system layer. For example, when the system type of the system layer is Android system, the corresponding JS engine of the system layer is V8; when the system type of the system layer is IOS system, the corresponding JS engine of the system layer is JavaScriptCore. The JS engine can be understood as a program written by code. For example, V8 is written in C / C ++. The JS engine parses JS code, which can be understood as a piece of code to parse another piece of code. The execution process of the engine isolation method of the present application may correspond to a piece of program code. This piece of program code can be run on the Android system or the IOS system, and can be compatible with different types of systems. The engine isolation method of the present application can determine the JS engine that parses the game code according to the system type of the system layer that runs on the application platform. For game developers, they only need to write a set of game code, which can be used on different game platforms, reducing the workload of game developers, and then reducing the cost of game development.

Among them, when the system type of the system layer of the application platform is Android system, using V8 in Android system can make full use of the built-in engine capabilities of Android system to improve the performance of JS code running on V8. When the system type of the system layer of the application platform is an IOS system, the use of JavaScriptCore in the IOS system can make full use of the built-in engine capabilities of the IOS system to improve the performance of JS code running on the JavaScriptCore.

It should be noted that the JS engine in the embodiment of the present application is different from the JS engine developed by a general browser developer. Because the browser needs to do many other things besides analyzing the game code, such as parsing pages, rendering pages, cookie management, history, etc., the JS engine developed by browser developers is more complicated and needs more functions . The JS engine in the embodiment of the present application is a JS engine specially developed for parsing game code, and may also be called a JS game-specific engine. The JS game-specific engine is a specially designed engine for game code parsing. Compared with the JS engine developed by the browser developer, the JS game-specific engine strips out some functions (such as cookie management functions) in the browser that are not related to the game.

102. The bridge layer calls a JS engine corresponding to the system layer to process the game code of the first game running in the JS layer.

In the embodiment of the present application, the game code of the first game may be a JS code. For example, if the system type of the system layer is Android system, the bridge layer calls V8 to process the game code of the first game running in the JS layer. If the system type of the system layer is an IOS system, the bridge layer calls JavaScriptCore to process the game code of the first game running in the JS layer.

103. The bridging layer exposes the encapsulated system capability to the JS layer, and the encapsulated system capability is provided for the JS layer to call.

In the embodiment of the present application, the bridging layer may encapsulate system capabilities that can be used by games in the system layer, and provide the encapsulated capabilities for the JS layer to call. Specifically, the bridge layer can inject the system capabilities into the JS engine, and the JS engine can provide the JS layer with the system capabilities injected in the JS engine when executing the JS code in the game. In the embodiment of the present application, the system capabilities of the system layer may be all the capabilities that can be used by the mini-game. For example, system capabilities can be the ability to access memory. For system capabilities that are not used in mini-games, they will not be encapsulated or injected into the JS engine.

Among them, the encapsulated system capability may exist in the form of an Application Programming Interface (Application Programming Interface).

In the embodiment of the present application, the mini-game can directly utilize the underlying capabilities of the system through the bridge layer, thereby improving the running performance of the mini-game.

Optionally, the system capability includes at least one of a graphics drawing capability, a sensor calling capability, a file downloading capability, a file uploading capability, a payment capability, a short message reading capability, an address book access capability, and a camera calling capability.

For example, the encapsulated graphics drawing capability can be Open Graphics Library (Open Graphics Library, OpenGL). OpenGL is a professional graphics program interface with cross programming language and cross platform programming interface specifications. It is a low-level graphics library that is easy to call. The sensor calling capability may specifically include a calling capability of an infrared proximity sensor, a calling capability of a light sensor (also referred to as an ambient light sensor), a calling capability of a gravity sensor, a calling capability of a three-axis acceleration sensor, a calling capability of a three-axis gyroscope, and the like.

In the embodiment of the present application, the JS layer is isolated from the system layer by adding a bridge layer. The bridge layer can encapsulate the system capabilities of the system layer, and the encapsulated system capabilities can be called by the JS layer to avoid the JS layer directly interacting with the system layer. The JS layer does not need to adapt to the system layer. The game code of the first game running in the JS layer does not need to adapt to a different type of system. The game code of the first game only needs to be adapted to the bridge layer, which can reduce the Game development costs. At the same time, since the JS layer does not directly interact with the system layer, adding a bridge layer can ensure the security of the system layer.

Please refer to FIG. 3, which is a schematic flowchart of another engine isolation method disclosed in an embodiment of the present application. As shown in FIG. 3, the engine isolation method includes the following steps.

301. When the first game runs on the game platform, the bridge layer determines the JS engine corresponding to the system layer according to the system type of the system layer.

302. The bridge layer calls a JS engine corresponding to the system layer to process the game code of the first game running in the JS layer.

303. The bridging layer exposes the encapsulated system capability to the JS layer, and the encapsulated system capability is provided for the JS layer to call.

For steps 301 to 303 in this embodiment of the present application, reference may be made to steps 101 to 103 shown in FIG. 1, and details are not described herein again.

304. When the system layer detects the first system event, the bridge layer converts the first system event into a first JS event, and generates a first JS event processing function corresponding to the first JS event.

305. The JS layer calls the first JS event processing function to process the first JS event.

In the embodiment of the present application, the first system event may be an event triggered by a system layer. For example, during the first game running, when the user touches the display screen of the mobile terminal, a touch event is generated, and the system layer can detect the touch event. The following uses the first system event as a touch event for illustration. The system layer passes the detected touch event to the bridge layer for processing. The bridge layer converts the touch event into a JS touch event that the JS layer can recognize, and generates a JS touch event processing function corresponding to the JS touch event. The JS layer can directly call the JS touch. The event handler executes the JS touch event.

Specifically, the system layer, the bridge layer, and the JS layer can be understood as a piece of program code, and are program codes written in different programming languages. For example, the system layer can be a piece of program code written in assembly language; the bridge layer can be a piece of program code written in C ++ language; the JS layer can be a piece of program code written in Java language. When the system layer sends the detected touch event to the bridge layer for processing, since the system layer is written in assembly language, and the touch event corresponds to a piece of assembly language code, the JS layer obviously cannot directly handle the touch event. The layer converts the touch event into a JS touch event that can be recognized by the JS layer, and generates a corresponding JS event processing function. Each JS event is eventually converted into one or more JS functions, and the JS layer can directly call JS functions for processing.

Among them, the bridge layer serves as an intermediate layer, and can convert the assembly language code of the touch event into JS code that can be recognized by the JS layer. The steps of converting the first system event into the first JS event and generating the first JS event processing function corresponding to the first JS event are avoided at the system layer, which reduces the burden on the system layer and improves the response speed of the touch event. Improved gaming experience.

Among them, before calling the JS touch event processing function, the JS layer can initialize the game business, add event listeners, and register the touch event processing function, so as to call the JS touch event processing function of the bridge layer to execute the JS touch event. The bridge layer in the embodiment of the present application serves as a bridge between the JS layer and the system layer. The bridge layer can convert events detected by the system layer into JS touch event processing functions that can be directly called by the JS layer, which is convenient for the JS layer to process and reduce JS. Difficulty of developing game code to run at layers.

In the embodiment of the present application, the JS layer is isolated from the system layer by adding a bridge layer. The bridge layer can encapsulate the system capabilities of the system layer, and the encapsulated system capabilities can be called by the JS layer to avoid the JS layer directly interacting with the system layer. The JS layer does not need to adapt to the system layer. The game code of the first game running in the JS layer does not need to adapt to a different type of system. The game code of the first game only needs to be adapted to the bridge layer, which can reduce the Game development costs. At the same time, since the JS layer does not directly interact with the system layer, adding a bridge layer can ensure the security of the system layer. The bridging layer can convert the events detected by the system layer into S touch event processing functions that can be directly called by the JS layer, which is convenient for the JS layer to process and reduces the difficulty of developing game code for the JS layer.

Please refer to FIG. 4. FIG. 4 is a schematic flowchart of another engine isolation method disclosed in the embodiment of the present application. As shown in FIG. 4, the engine isolation method includes the following steps.

401. When the first game runs on the game platform, the bridge layer determines the JS engine corresponding to the system layer according to the system type of the system layer.

402. The bridge layer calls a JS engine corresponding to the system layer to process the game code of the first game running in the JS layer.

403. The bridging layer exposes the encapsulated system capability to the JS layer, and the encapsulated system capability is provided for the JS layer to call.

For steps 401 to 403 in this embodiment of the present application, reference may be made to steps 101 to 103 shown in FIG. 1, and details are not described herein again.

404. When the JS engine corresponding to the system layer is upgraded, the bridge layer adapts to the system layer to perform the corresponding upgrade.

In the embodiment of the present application, when the JS engine of the system layer is upgraded, the bridge layer needs to be adapted to the system layer for corresponding upgrade, so that the bridge layer can be adapted to the system layer. For the JS layer, there is no need to upgrade, the JS layer does not need to adapt to the system layer, and the game code of the first game running in the JS layer does not need to adapt to the underlying system layer, which can reduce game development costs.

Optionally, the embodiment of the present application may further include the following steps:

When the system layer is capable of updating, the bridging layer encapsulates the updated ability of the system layer to obtain the updated system ability after the package, and the updated system ability after the package is called by the JS layer.

In the embodiment of the present application, when the system layer is capable of updating, the bridging layer encapsulates the updated ability of the system layer to obtain the encapsulated updated system ability, and the encapsulated updated system ability is called by the JS layer. For the JS layer, there is no need to adapt to the system layer, and the game code of the first game running in the JS layer does not need to adapt to the underlying system layer, which can reduce game development costs.

In the embodiment of the present application, the JS layer is isolated from the system layer by adding a bridge layer. The bridge layer can encapsulate the system capabilities of the system layer, and the encapsulated system capabilities can be called by the JS layer to avoid the JS layer directly interacting with the system layer. The JS layer does not need to adapt to the system layer. The game code of the first game running in the JS layer does not need to adapt to a different type of system. The game code of the first game only needs to be adapted to the bridge layer, which can reduce the Game development costs. At the same time, the first game can take advantage of the underlying capabilities of the system, improving the performance of small games.

Please refer to FIG. 5, which is a schematic flowchart of another engine isolation method disclosed in an embodiment of the present application. As shown in FIG. 5, the engine isolation method includes the following steps.

501. When the first game runs on the game platform, the bridge layer determines the JS engine corresponding to the system layer according to the system type of the system layer.

502. The bridge layer calls a JS engine corresponding to the system layer to process the game code of the first game running in the JS layer.

503. The bridging layer exposes the encapsulated system capabilities to the JS layer, and the encapsulated system capabilities are provided for the JS layer to call.

For steps 501 to 503 in the embodiment of the present application, reference may be made to steps 501 to 503 shown in FIG. 1, and details are not described herein again.

504. The bridge layer obtains a system capability call permission set of the first game.

505. When the first game receives a call to a system capability beyond the system capability call permission set, the bridge layer performs a permission authentication operation for the system capability beyond the system capability call permission set.

506. After the authority authentication operation exceeding the system capability calling permission set passes, the system capability exceeding the system capability calling permission set is added to the system capability calling permission set of the first game.

In the embodiments of the present application, the system capability calling authority of different types of games is generally different. For example, gravity-sensing games have the ability to call gravity sensors; games with friends ranking have the ability to upload files and access contacts. Generally speaking, for some systems with strong privacy (such as address book access ability, SMS reading ability, camera calling ability, etc.), when the game is first run on the game platform, the user's opinion is generally consulted. The user You can choose whether to give the game these system capabilities. Therefore, the system capability call permissions of different types of games are generally different.

The bridging layer may obtain a system capability call permission set of the first game when the first game runs on the game platform for the first time.

When the user is running the first game, if the user's operation for the first game requires the ability to call the system capabilities of the first game other than the permission set to be realized, the user's opinion can be sought to determine whether to run the first game. A capability other than the system capability call permission set of the game is added to the system capability call permission set of the first game.

Specifically, the bridging layer performing a permission authentication operation for a system capability beyond the system capability call permission set may include the following steps:

Verify user identity information;

Output the advantages and disadvantages of calling the system capabilities beyond the system capability calling permission set;

A user touch operation is received to determine whether the authority authentication operation is passed.

In the embodiment of the present application, for a small game, real-time system capability permission authentication can be performed when the system capability used by the game exceeds its calling authority, and there is no need to re-set the system capability permission after exiting the game to avoid interrupting the game for a long time. This can improve the user gaming experience.

Please refer to FIG. 6. FIG. 6 is a schematic flowchart of another engine isolation method disclosed in the embodiment of the present application. As shown in FIG. 6, the engine isolation method includes the following steps.

601. When the first game runs on the game platform, the bridge layer determines the JS engine corresponding to the system layer according to the system type of the system layer.

602. The bridge layer calls a JS engine corresponding to the system layer to process the game code of the first game running in the JS layer.

603. The bridging layer exposes the encapsulated system capability to the JS layer, and the encapsulated system capability is provided for the JS layer to call.

For steps 601 to 603 in this embodiment of the present application, reference may be made to steps 601 to 603 shown in FIG. 1, and details are not described herein again.

604. When the first game and the second game run on the game platform at the same time, if the first game and the second game running on the JS layer call the first system capability encapsulated by the bridge layer at the same time, the bridge layer obtains the first game. And the priority of the second game, and confirm the highest priority game among the first and second games, and prioritize the packaged first system capability to the highest priority game among the first and second games.

In the embodiment of the present application, when two games are running on a game platform at the same time, if two games call the same system capability at the same time, a conflict will occur. At this time, the bridge layer may determine to prioritize the first system capability to the game with the highest priority among the first game and the second game according to the priorities of the two games.

Among them, the scenario where two games are running on the game platform at the same time may be a split-screen multi-tasking scenario. For example, when two games call the system payment capability at the same time, in order to ensure the security of payment, only one of the two games is allowed to call the system payment capability at the same time. The priorities of the first game and the second game may be determined based on the running information of the first game and the second game on the game platform, user evaluation information, the calling frequency of the first system capability, and the like.

Optionally, the bridge layer obtains the priorities of the first game and the second game, which may specifically include the following steps:

The bridge layer receives the running information of the first game on the game platform and the running information of the second game on the game platform sent by the JS layer, and determines the first based on the running information of the first game on the game platform and the running information of the second game on the game platform. The priority of the game and the priority of the second game.

The running information of the game on the game platform may include information such as the cumulative online duration of the game on the game platform, the activity of the game on the game platform, and the ranking of the game on the game platform. Generally speaking, the longer the cumulative online time, the higher the activity, and the higher the popularity of the game, the higher the priority.

For example, if the priority of the first game is higher than the priority of the second game, after the packaged first system capability is used for the first game, the first system capability may be used for the second game.

In the embodiment of the present application, when two games call conflicts on the same system capability at the same time, the priority of the two games is used to prioritize the system capability to the game with the highest priority among the two games. When the game calls the same system capability at the same time, a system error occurs when a conflict occurs.

The above mainly introduces the solution of the embodiment of the present application from the perspective of the method-side execution process. It can be understood that, in order to realize the above functions, the mobile terminal includes a hardware structure and / or a software module corresponding to each function. Those skilled in the art should easily realize that the present invention can be implemented in the form of hardware or a combination of hardware and computer software by combining the units and algorithm steps of each example described in the embodiments disclosed herein. Whether a certain function is performed by hardware or computer software-driven hardware depends on the specific application of the technical solution and design constraints. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation should not be considered outside the scope of the present invention.

The embodiments of the present application may divide the functional units of the mobile terminal according to the foregoing method examples. For example, each functional unit may be divided corresponding to each function, or two or more functions may be integrated into one processing unit. The above integrated unit may be implemented in the form of hardware or in the form of software functional unit. It should be noted that the division of the units in the embodiments of the present application is schematic, and is only a logical function division. There may be another division manner in actual implementation.

Please refer to FIG. 7, which is a schematic structural diagram of an engine isolation device disclosed in an embodiment of the present application. The engine isolation device 700 is applied to a game platform. The game platform runs on a mobile terminal. The game platform includes a system layer, a bridge layer, and a JS layer. The bridge layer encapsulates the system capabilities of the system layer. The bridge layer connects the system layer and the JS layer, such as As shown in FIG. 7, the engine isolation device 700 includes a determining unit 701 and a processing unit 702, where:

A determining unit 701, configured to determine a JS engine corresponding to the system layer according to the system type of the system layer when the first game runs on the game platform;

A processing unit 702, configured to call a JS engine corresponding to the system layer to process the game code of the first game running in the JS layer;

The processing unit 702 is further configured to expose the encapsulated system capability to the JS layer, and the encapsulated system capability is provided for the JS layer to call.

Optionally, the engine isolation device 700 further includes a conversion unit 703 and a generation unit 704, where:

A conversion unit 703, configured to convert the first system event into a first JS event when the system layer detects the first system event;

The generating unit 704 is configured to generate a first JS event processing function corresponding to the first JS event; the JS layer is configured to call the first JS event processing function to process the first JS event.

Optionally, the engine isolation device 700 further includes an adaptation unit 705, where:

The adapting unit 705 is configured to perform a corresponding upgrade when the JS engine corresponding to the system layer is upgraded.

Optionally, the processing unit 702 is further configured to encapsulate the updated capability of the system layer when the system layer is capable of updating, to obtain the encapsulated updated system capability, and the encapsulated updated system capability is available for the JS layer to call.

Optionally, the engine isolation device 700 further includes an obtaining unit 706;

An obtaining unit 706, configured to obtain a system capability call permission set of the first game;

The processing unit 702 is further configured to execute a permission authentication operation for a system capability beyond the system capability call permission set when the first game receives a call of the system capability beyond the system capability call permission set;

The processing unit 702 is further configured to add a system capability beyond the system capability call permission set to the system capability call permission set of the first game after a permission authentication operation that exceeds the system capability call permission set passes.

Optionally, the obtaining unit 706 is further configured to: when the first game and the second game run on the game platform at the same time, if the first game and the second game running on the JS layer simultaneously encapsulate the first system capability of the bridge layer Make a call to obtain the priority of the first game and the second game;

The processing unit 702 is further configured to confirm the game with the highest priority among the first game and the second game, and prioritize the packaged first system capability to the game with the highest priority among the first game and the second game.

Optionally, the obtaining unit 706 obtains the priorities of the first game and the second game, specifically:

The obtaining unit 706 receives the running information of the first game on the game platform and the running information of the second game on the game platform and sends the JS layer to determine the first game based on the running information of the first game on the game platform and the running information of the second game on the game platform. The priority of the first game and the priority of the second game.

Implement the engine isolation device shown in Figure 7 to isolate the JS layer from the system layer by adding a bridging layer. The bridging layer can encapsulate the system capabilities of the system layer. The encapsulated system capabilities can be called by the JS layer to avoid the JS layer directly from the system. The JS layer does not need to adapt to the system layer. The game code of the first game running in the JS layer does not need to adapt to a different type of system. The game code of the first game only needs to adapt to the bridge layer. , Which can reduce game development costs. At the same time, since the JS layer does not directly interact with the system layer, adding a bridge layer can ensure the security of the system layer.

Please refer to FIG. 8, which is a schematic structural diagram of a mobile terminal disclosed in an embodiment of the present application. As shown in FIG. 8, the mobile terminal 800 includes a processor 801 and a memory 802. The mobile terminal 800 may further include a bus 803. The processor 801 and the memory 802 may be connected to each other through a bus 803, and the bus 803 may be a peripheral component and Connected to a standard (Peripheral Component Interconnect (PCI) bus or extended industry standard architecture (EISA) bus, etc. The bus 803 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is used in FIG. 8, but it does not mean that there is only one bus or one type of bus. The mobile terminal 800 may further include an input-output device 804, and the input-output device 804 may include a display screen, such as a liquid crystal display screen. The memory 802 is configured to store one or more programs containing instructions; the processor 801 is configured to call the instructions stored in the memory 802 to execute some or all of the method steps in the foregoing FIG. 1 to FIG. 6.

Implement the mobile terminal shown in Figure 8 to isolate the JS layer from the system layer by adding a bridging layer. The bridging layer can encapsulate the system capabilities of the system layer. The encapsulated system capabilities can be called by the JS layer to avoid the JS layer directly from the system layer. For interaction, the JS layer does not need to adapt to the system layer. The game code of the first game running in the JS layer does not need to adapt to a different type of system. The game code of the first game only needs to adapt to the bridge layer. This can reduce game development costs. At the same time, since the JS layer does not directly interact with the system layer, adding a bridge layer can ensure the security of the system layer.

This embodiment of the present application also provides another mobile terminal. As shown in FIG. 9, for convenience of explanation, only relevant parts of the embodiment of the present application are shown. For specific technical details not disclosed, please refer to the method of the embodiment of the present application. section. The mobile terminal may be any terminal device including a mobile phone, a tablet computer, a PDA (Personal Digital Assistant), a POS (Point of Sales), and a vehicle-mounted computer. Taking the mobile terminal as a mobile phone as an example:

FIG. 9 is a block diagram showing a partial structure of a mobile phone related to a mobile terminal according to an embodiment of the present application. Referring to FIG. 9, the mobile phone includes: a radio frequency (RF) circuit 910, a memory 920, an input unit 930, a display unit 940, a sensor 950, an audio circuit 960, a wireless fidelity (WiFi) module 970, and a processor 980 , And power supply 990 and other components. Those skilled in the art can understand that the structure of the mobile phone shown in FIG. 9 does not constitute a limitation on the mobile phone, and may include more or fewer parts than those shown in the figure, or combine some parts, or arrange different parts.

The following describes each component of the mobile phone in detail with reference to FIG. 9:

The RF circuit 910 can be used for receiving and transmitting information. Generally, the RF circuit 910 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a Low Noise Amplifier (LNA), a duplexer, and the like. In addition, the RF circuit 910 can also communicate with a network and other devices through wireless communication. The above wireless communication can use any communication standard or protocol, including but not limited to Global System of Mobile (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (Code Division Multiple Access) Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Long Term Evolution (LTE), E-mail, Short Messaging Service (SMS), etc.

The memory 920 may be used to store software programs and modules. The processor 980 executes various functional applications and data processing of the mobile phone by running the software programs and modules stored in the memory 920. The memory 920 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function, and the like; the storage data area may store data created according to the use of the mobile phone, and the like. In addition, the memory 920 may include a high-speed random access memory, and may further include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, or other volatile solid-state storage device.

The input unit 930 may be used to receive inputted numeric or character information, and generate key signal inputs related to user settings and function control of the mobile phone. Specifically, the input unit 930 may include a fingerprint recognition module 931 and other input devices 932. The fingerprint identification module 931 can collect fingerprint data on the user. In addition to the fingerprint recognition module 931, the input unit 930 may also include other input devices 932. Specifically, the other input devices 932 may include, but are not limited to, one or more of a touch screen, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, and the like.

The display unit 940 may be used to display information input by the user or information provided to the user and various menus of the mobile phone. The display unit 940 may include a display screen 941. Optionally, the display screen 941 may be configured by using a liquid crystal display (Liquid Crystal Display, LCD), an organic or inorganic light emitting diode (Organic Light-Emitting Diode, OLED) and the like.

The mobile phone may further include at least one sensor 950, such as a light sensor, a motion sensor, a pressure sensor, a temperature sensor, and other sensors. Specifically, the light sensor may include an ambient light sensor (also referred to as a light sensor) and a proximity sensor. The ambient light sensor may adjust the brightness of the backlight of the mobile phone according to the brightness of the ambient light, and then adjust the brightness of the display screen 941. The proximity sensor may When the mobile phone is moved to the ear, the display 941 and / or the backlight are turned off. As a kind of motion sensor, the accelerometer sensor can detect the magnitude of acceleration in various directions (usually three axes), and can detect the magnitude and direction of gravity when it is stationary. It can be used to identify the attitude of mobile phones (such as horizontal and vertical screen switching, magnetic force) Calibration of the meter), vibration recognition related functions (such as pedometer, tap), etc. As for the mobile phone can also be equipped with gyroscope, barometer, hygrometer, thermometer, infrared sensor and other sensors, will not repeat them here.

The audio circuit 960, the speaker 961, and the microphone 962 can provide an audio interface between the user and the mobile phone. The audio circuit 960 may transmit the received electrical data converted electrical signals to a speaker 961, which is converted into a sound signal for playback; on the other hand, the microphone 962 converts the collected sound signal into an electrical signal, and the audio circuit 960 After receiving, it is converted into audio data, and then processed by the audio data playback processor 980, and then sent to, for example, another mobile phone via the RF circuit 910, or the audio data is played to the memory 920 for further processing.

WiFi is a short-range wireless transmission technology. The mobile phone can help users send and receive emails, browse web pages, and access streaming media through the WiFi module 970. It provides users with wireless broadband Internet access. Although FIG. 9 shows the WiFi module 970, it can be understood that it does not belong to the necessary configuration of the mobile phone, and can be omitted as needed without changing the essence of the invention.

The processor 980 is the control center of the mobile phone. It uses various interfaces and lines to connect various parts of the entire mobile phone. The processor 980 runs or executes software programs and / or modules stored in the memory 920 and calls data stored in the memory 920 to execute Various functions and processing data of the mobile phone, so as to monitor the mobile phone as a whole. Optionally, the processor 980 may include one or more processing units; preferably, the processor 980 may integrate an application processor and a modem processor, wherein the application processor mainly processes an operating system, a user interface, and an application program, etc. The modem processor mainly handles wireless communication. It can be understood that the foregoing modem processor may not be integrated into the processor 980.

The mobile phone also includes a power supply 990 (such as a battery) for supplying power to various components. Preferably, the power supply can be logically connected to the processor 980 through the power management system, so as to implement functions such as managing charging, discharging, and power consumption management through the power management system.

The mobile phone may further include a camera 9100, which is used to capture images and videos, and transmit the captured images and videos to the processor 980 for processing.

The mobile phone can also have a Bluetooth module, etc., which is not repeated here.

In the foregoing embodiments shown in FIG. 1 to FIG. 6, each step and method flow can be implemented based on the structure of the mobile phone.

An embodiment of the present application further provides a computer storage medium, wherein the computer storage medium stores a computer program for electronic data exchange, and the computer program causes a computer to execute a part of any one of the engine isolation methods described in the foregoing method embodiments. Or all steps.

An embodiment of the present application further provides a computer program product, the computer program product includes a non-transitory computer-readable storage medium storing a computer program, and the computer program is operable to cause a computer to perform the operations described in the foregoing method embodiments. Part or all of the steps for any one engine isolation method.

It should be noted that, for the foregoing method embodiments, for simplicity of description, they are all described as a series of action combinations, but those skilled in the art should know that the present invention is not limited by the described action order. Because according to the present invention, certain steps may be performed in another order or simultaneously. Secondly, those skilled in the art should also know that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the present invention.

In the above embodiments, the description of each embodiment has its own emphasis. For a part that is not described in detail in one embodiment, reference may be made to related descriptions in other embodiments.

In the several embodiments provided in this application, it should be understood that the disclosed device may be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the unit is only a logical function division. In actual implementation, there may be another division manner. For example, multiple units or components may be combined or may be combined. Integration into another system, or some features can be ignored or not implemented. In addition, the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be electrical or other forms.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, may be located in one place, or may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objective of the solution of this embodiment.

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

When the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it may be stored in a computer-readable memory. Based on this understanding, the technical solution of the present invention essentially or part that contributes to the existing technology or all or part of the technical solution can be embodied in the form of a software product, which is stored in a memory, Several instructions are included to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in various embodiments of the present invention. The foregoing memories include: U disks, Read-Only Memory (ROM), Random Access Memory (RAM), mobile hard disks, magnetic disks, or optical disks and other media that can store program codes.

A person of ordinary skill in the art may understand that all or part of the steps in the various methods of the foregoing embodiments may be completed by a program instructing related hardware. The program may be stored in a computer-readable memory, and the memory may include a flash disk. , Read-only memory (English: Read-Only Memory, referred to as ROM), random access device (English: Random Access Memory, referred to as RAM), magnetic disks or optical disks, etc.

The embodiments of the present application have been described in detail above. Specific examples have been used herein to explain the principles and implementation of the present invention. The descriptions of the above embodiments are only used to help understand the method of the present invention and its core ideas; meanwhile, for Those of ordinary skill in the art may change the specific implementation and application scope according to the idea of the present invention. In summary, the content of this specification should not be construed as a limitation on the present invention.

Claims

An engine isolation method, characterized in that the engine isolation method is applied to a game platform, the game platform runs on a mobile terminal, the game platform includes a system layer, a bridge layer, and a JS layer, and the bridge layer is connected to an office The system layer and the JS layer, the bridge layer encapsulates the system capabilities of the system layer, and the method includes:

When the first game runs on the game platform, the bridge layer determines the JS engine corresponding to the system layer according to the system type of the system layer;

The bridge layer calls a JS engine corresponding to the system layer to process the game code of the first game running in the JS layer;

The bridging layer exposes the encapsulated system capability to the JS layer, and the encapsulated system capability is available for the JS layer to call.
The method according to claim 1, wherein the method comprises:

When the system layer detects a first system event, the bridging layer converts the first system event into a first JS event, and generates a first JS event processing function corresponding to the first JS event; the The JS layer is configured to call the first JS event processing function to process the first JS event.
The method according to claim 1 or 2, wherein the method comprises:

When the JS engine corresponding to the system layer is upgraded, the bridging layer adapts to the system layer for corresponding upgrade.
The method according to any one of claims 1-3, wherein the method comprises:

When the system layer is capable of updating, the bridging layer encapsulates the updated ability of the system layer to obtain the updated system ability after the package, and the encapsulated updated system ability is for the JS layer to call.
The method according to any one of claims 1-4, wherein the method comprises:

Acquiring, by the bridge layer, a system capability call permission set of the first game;

When receiving the first game calling a system capability beyond the system capability call permission set, the bridging layer performs permission authentication for the system capability beyond the system capability call permission set operating;

After the permission verification operation of the system capabilities beyond the system capability calling permission set is passed, adding the system capabilities beyond the system capability calling permission set to the system capability calling permission of the first game set.
The method according to any one of claims 1-4, wherein the method comprises:

When the first game and the second game run on the game platform at the same time, if the first game and the second game running on the JS layer simultaneously perform the first system capabilities encapsulated by the bridge layer When called, the bridge layer obtains the priorities of the first game and the second game, and confirms the game with the highest priority among the first game and the second game, and copies the encapsulated first The system capability is given priority to the game with the highest priority among the first game and the second game.
The method according to claim 6, wherein the obtaining, by the bridge layer, the priorities of the first game and the second game comprises:

The bridge layer receives the running information of the first game on the game platform and the running information of the second game on the game platform sent by the JS layer, based on the first game on the game platform. And the running information of the second game on the game platform determine the priority of the first game and the priority of the second game.
The method according to claim 5, wherein the bridging layer executes a permission authentication operation for the system capabilities beyond the system capability call permission set, comprising:

Verify user identity information;

Output the calling advantages and calling disadvantages of the system capabilities beyond the system capability calling permission set;

A user touch operation is received to determine whether the authority authentication operation is passed.
The method according to claim 1, wherein the system capabilities include graphics drawing capabilities, sensor calling capabilities, file downloading capabilities, file uploading capabilities, payment capabilities, SMS reading capabilities, address book access capabilities, and camera calling capabilities At least one of.
An engine isolation device is characterized in that the engine isolation device is applied to a game platform, the game platform runs on a mobile terminal, the game platform includes a system layer, a bridge layer, and a JS layer, and the bridge layer is connected to an office The system layer and the JS layer, the bridge layer encapsulates the system capabilities of the system layer, and the engine isolation device includes a determination unit and a processing unit, wherein:

The determining unit is configured to determine a JS engine corresponding to the system layer according to a system type of the system layer when a first game runs on the game platform;

The processing unit is configured to call a JS engine corresponding to the system layer to process the game code of the first game running in the JS layer;

The processing unit is further configured to expose the encapsulated system capability to the JS layer, and the encapsulated system capability is for the JS layer to call.
The device according to claim 10, wherein the engine isolation device further comprises a conversion unit and a generation unit, wherein:

The conversion unit is configured to convert the first system event into a first JS event when the system layer detects a first system event;

The generating unit is configured to generate a first JS event processing function corresponding to the first JS event; the JS layer is configured to call the first JS event processing function to process the first JS event.
The device according to claim 10 or 11, wherein the engine isolation device further comprises an adaptation unit, wherein:

The adapting unit is adapted to adapt the system layer for a corresponding upgrade when the JS engine corresponding to the system layer is upgraded.
The device according to any one of claims 10-12, wherein:

The processing unit is further configured to encapsulate the updated capability of the system layer when the system layer has the capability to update, to obtain the encapsulated updated system capability, and the encapsulated updated system capability is provided for the JS layer call.
The device according to claim 13, wherein the engine isolation device further comprises an obtaining unit, wherein:

The obtaining unit is configured to obtain a system capability call permission set of the first game;

The processing unit is further configured to, when the first game receives a call to a system capability beyond the system capability call permission set, execute the system for the system beyond the system capability call permission set. Competence authorization operation;

The processing unit is further configured to add the system capability beyond the system capability call permission set to the system capability after the authority authentication operation of the system capability beyond the system capability call permission set passes. The system capabilities of the first game call permission sets.
The device according to claim 14, wherein:

The obtaining unit is further configured to, when the first game and the second game are running on the game platform at the same time, if the first game and the second game running on the JS layer are simultaneously connected to the bridge, The first system capability encapsulated in the layer is called to obtain the priorities of the first game and the second game;

The processing unit is further configured to confirm a game with the highest priority among the first game and the second game, and prioritize the packaged first system capability to the first game and the second game. The highest priority game to use.
The device according to claim 15, wherein the obtaining unit obtains the priorities of the first game and the second game, specifically:

The acquiring unit receives the running information of the first game on the game platform and the running information of the second game on the game platform sent by the JS layer, based on the first game on the game platform. And the running information of the second game on the game platform determine the priority of the first game and the priority of the second game.
The apparatus according to claim 14, wherein the processing unit executes a permission authentication operation for the system capability beyond the system capability call permission set, specifically:

The processing unit verifies user identity information, outputs the calling advantages and calling disadvantages of the system capabilities beyond the system capability calling permission set, and receives a user touch operation to determine whether to pass a permission authentication operation.
The device according to claim 10, wherein the system capabilities include graphics drawing capabilities, sensor calling capabilities, file downloading capabilities, file uploading capabilities, payment capabilities, SMS reading capabilities, address book access capabilities, and camera calling capabilities At least one of.
A mobile terminal includes a processor and a memory, where the memory is used to store one or more programs, the one or more programs are configured to be executed by the processor, and the programs include The method according to any one of claims 1-9 is performed.
A computer-readable storage medium, characterized in that the computer-readable storage medium is used to store a computer program for electronic data exchange, wherein the computer program causes a computer to execute the computer program according to any one of claims 1-9. method.