Application control method and device

Abstract

The invention provides an application control method and device, and the method comprises the steps: displaying a first control developed based on a 3D engine on a native interface of a target application, sending a corresponding webpage parameter to the target application through the 3D engine when a first triggering operation is triggered, and creating and displaying a target webpage through the target application based on the webpage parameter. Each webpage in the webpage library is developed based on the native engine of the target application, and compared with a webpage developed based on a 3D engine in a traditional scheme, the development and maintenance difficulty and cost are lower. Moreover, the calling and creation of the target webpage are realized by the target application native engine without depending on a 3D engine, so that the webpage response speed and fluency are higher, and the user experience is improved. And furthermore, the native engine directly displays the target webpage in the native interface, so that coverage display of the target webpage on the native interface is realized, the webpage does not need to be skipped, and the page display efficiency and the interaction experience are improved.

Description

Application control method and device TECHNICAL FIELD

[0001] The present specification relates to the technical field of electronic devices, and in particular to an application control method and device. BACKGROUND

[0002] With the development of electronic devices, application programs (App) on electronic devices are emerging in endlessly, and the functions that can be implemented by the application programs are more and more. For example, a 3D engine is embedded in part of the application programs, and a more realistic and stereoscopic effect is rendered and displayed through the 3D engine.

[0003] In related technologies, the functions of the 3D engine control are generally encapsulated in a 3D engine package, and then the 3D engine package is encapsulated in the application program. The functions of the 3D engine control are relatively independent, which leads to a large development difficulty, a high cost, and a poor running effect of part of the functions, and is not conducive to later modification and maintenance.

[0004] SUMMARY

[0005] To improve the web page display effect in the 3D engine control and reduce the development difficulty and maintenance cost, the present specification provides an application control method, device, electronic device, storage medium, and computer program product.

[0006] In a first aspect, the embodiments of the present specification provide an application control method, comprising:

[0007] displaying a first control on a native interface of a target application, wherein the target application is embedded with a 3D engine, the first control is rendered based on the 3D engine, and the native interface is rendered based on a native engine of an operating system;

[0008] in response to detecting a first trigger operation on the first control, determining a target web page corresponding to the first trigger operation and a web page parameter of the target web page through the 3D engine, and sending the web page parameter to the target application;

[0009] the target application creates a page container on the native interface according to the web page parameter, and displays the target web page in the page container.

[0010] In some embodiments, the determining a target web page corresponding to the first trigger operation and a web page parameter of the target web page through the 3D engine, and sending the web page parameter to the target application, comprises:

[0011] The 3D engine determines a target webpage corresponding to the first trigger operation and a webpage parameter of the target webpage based on a pre-packaged mapping relationship, where the mapping relationship represents a corresponding relationship between the first trigger operation and the webpage parameter.

[0012] The 3D engine calls a communication method between a native layer of the target application to send the webpage parameter to the target application.

[0013] In some embodiments, the webpage parameter includes a page position and a page size; and the target application creates a page container on the native interface according to the webpage parameter, including:

[0014] determining a position parameter of the page container on the native interface according to the page position included in the webpage parameter;

[0015] determining a size parameter of the page container according to the page size included in the webpage parameter;

[0016] creating the page container on the native interface based on the position parameter and the size parameter.

[0017] In some embodiments, the webpage parameter includes a webpage link of the target webpage; and the displaying the target webpage in the page container includes:

[0018] calling the target webpage from a pre-configured webpage library according to the webpage link included in the webpage parameter;

[0019] configuring the target webpage in the page container.

[0020] In some embodiments, the first control includes a three-dimensional human body model, and the first trigger operation includes an operation of triggering each human body part of the three-dimensional human body model.

[0021] In some embodiments, the first control includes a three-dimensional human body model, and the first control includes a three-dimensional human body model and at least one button control, the button control is associated with a human body part of the three-dimensional human body model, and the first trigger operation includes an operation of triggering the button control.

[0022] In some embodiments, the application control method of the present specification further includes:

[0023] In response to detecting the first trigger operation, the 3D engine determines a target scene associated with a target human body part of the first trigger operation from a pre-configured display scene library according to the target human body part, and renders the target scene, where the target scene includes a three-dimensional model corresponding to the target human body part.

[0024] In some embodiments, in the case that the target human body part is an internal organ of the human body, the rendering displaying the target scene comprises:

[0025] translucifying the appearance of the three-dimensional human body model and highlighting the target human body part;

[0026] switching the first control from the three-dimensional human body model to the target human body part.

[0027] In some embodiments, the application control method of the present specification further comprises:

[0028] In the case that the target web page is displayed on the native interface, in response to detecting a second trigger operation, switching the target web page displayed on the native interface from a first web page to a second web page; wherein the human body part corresponding to the second trigger operation is different from the first trigger operation.

[0029] In some embodiments, the application control method of the present specification further comprises:

[0030] In the case that the target web page is displayed on the native interface, in response to detecting a third trigger operation, the 3D engine sending a deletion instruction to the target application;

[0031] The target application deleting part or all of the target web page displayed on the native interface according to the deletion instruction.

[0032] In some embodiments, the 3D engine comprises a Unity engine, and the web page comprises an H5 web page.

[0033] In a second aspect, the embodiments of the present specification provide an application control device, comprising:

[0034] a view display module configured to display a first control on a native interface of a target application, wherein the target application is embedded with a 3D engine, the first control is rendered based on the 3D engine, and the native interface is rendered based on a native engine of an operating system;

[0035] a parameter interaction module configured to, in response to detecting a first trigger operation on the first control, determine a target web page corresponding to the first trigger operation and a web page parameter of the target web page through the 3D engine, and send the web page parameter to the target application;

[0036] a web page generation module configured to create a page container on the native interface by the target application according to the web page parameter, and display the target web page in the page container.

[0037] In some embodiments, the parameter interaction module is configured to:

[0038] The 3D engine determines a target webpage corresponding to the first trigger operation and a webpage parameter of the target webpage based on a pre-encapsulated mapping relationship, wherein the mapping relationship represents a corresponding relationship between the first trigger operation and the webpage parameter;

[0039] The 3D engine calls a communication method between a native layer of the target application to send the webpage parameter to the target application.

[0040] In some embodiments, the webpage parameter includes a page position and a page size, and the webpage generation module is configured to:

[0041] determine a position parameter of the page container on the native interface according to the page position included in the webpage parameter;

[0042] determine a size parameter of the page container according to the page size included in the webpage parameter;

[0043] create the page container on the native interface based on the position parameter and the size parameter.

[0044] In some embodiments, the webpage parameter includes a webpage link of the target webpage, and the webpage generation module is configured to:

[0045] retrieve the target webpage from a pre-configured webpage library according to the webpage link included in the webpage parameter;

[0046] configure the target webpage in the page container.

[0047] In some embodiments, the first control includes a three-dimensional human body model, and the first trigger operation includes an operation of triggering each human body part of the three-dimensional human body model.

[0048] In some embodiments, the first control includes a three-dimensional human body model, and the first control includes a three-dimensional human body model and at least one button control, the button control is associated with a human body part of the three-dimensional human body model, and the first trigger operation includes an operation of triggering the button control.

[0049] In some embodiments, the webpage generation module is configured to:

[0050] In response to detecting the first trigger operation, the 3D engine determines a target scene associated with the target human body part from a pre-configured scene library according to the target human body part corresponding to the first trigger operation, and renders the target scene to display the target scene, wherein the target scene includes a three-dimensional model corresponding to the target human body part.

[0051] In some embodiments, when the target human body part is an internal organ of the human body, the webpage generation module is configured to:

[0052] When the target webpage is displayed on the native interface, in response to detecting a second trigger operation, the target webpage displayed on the native interface is switched from a first webpage to a second webpage, wherein the human body part corresponding to the second trigger operation is different from the first trigger operation.

[0053] In some embodiments, the webpage generation module is configured to:

[0054] When the target webpage is displayed on the native interface, in response to detecting a third trigger operation, the 3D engine sends a deletion instruction to the target application;

[0055] The target application deletes part or all of the target webpage displayed on the native interface according to the deletion instruction.

[0056] In some embodiments, the 3D engine includes a Unity engine, and the webpage includes an H5 webpage.

[0057] In a third aspect, an electronic device is provided, including:

[0058] a display screen configured to display an application interface;

[0059] a processor; and

[0060] a memory storing computer instructions configured to cause the processor to perform the method of any of the above embodiments.

[0061] In a fourth aspect, a storage medium is provided, storing computer instructions configured to cause a computer to perform the method of any of the above embodiments.

[0062] In a fifth aspect, a computer program product is provided, which, when executed, implements the method of any of the above embodiments.

[0063] The application control method of the embodiments of the present specification comprises displaying a first control developed based on a 3D engine on a native interface of a target application, and sending a corresponding web page parameter to the target application by the 3D engine when a first trigger operation is triggered, and the target application creates and displays a target web page based on the web page parameter. Each web page in the web page library is developed based on the native engine of the target application, which has lower development and maintenance difficulty and cost compared with the web page developed based on the 3D engine in the traditional scheme. Moreover, the calling and creation of the target web page are realized by the native engine of the target application, without the need of relying on the 3D engine, so that the response speed and fluency of the web page are higher, and the user experience is improved. In addition, the native engine directly displays the target web page in the native interface, realizing the overlay display of the target web page on the native interface, so that the web page does not need to be switched, and the page display efficiency and interactive experience are improved. BRIEF DESCRIPTION OF DRAWINGS

[0064] In order to more clearly illustrate the technical solutions in the embodiments of the present specification or the prior art, the drawings needed to be used in the specific embodiments or prior art description will be briefly introduced. Obviously, the drawings in the following description are some embodiments of the present specification, and those skilled in the art can also obtain other drawings according to these drawings without creative labor.

[0065] FIG. 1 is a structural diagram of an electronic device in an example embodiment of the present specification.

[0066] FIG. 2 is a system structure diagram of an electronic device in an example embodiment of the present specification.

[0067] FIG. 3 is a flowchart of an application control method in an example embodiment of the present specification.

[0068] FIG. 4 is a native interface in an example embodiment of the present specification.

[0069] FIG. 5 is a structural diagram of a target application in an example embodiment of the present specification.

[0070] FIG. 6 is a flowchart of an application control method in an example embodiment of the present specification.

[0071] FIG. 7 is a flowchart of an application control method in an example embodiment of the present specification.

[0072] FIG. 8 is a native interface in an example embodiment of the present specification.

[0073] FIG. 9 is a flowchart of an application control method in an example embodiment of the present specification.

[0074] FIG. 10 is a native interface in an example embodiment of the present specification.

[0075] FIG. 11 is a flowchart of an application control method according to an example embodiment of the present specification.

[0076] FIG. 12 is a structural diagram of an application control device according to an example embodiment of the present specification. DETAILED DESCRIPTION

[0077] The technical solutions of the present specification will be clearly and completely described below with reference to the drawings. Obviously, the described embodiments are part of the embodiments of the present specification, rather than all the embodiments. Based on the embodiments of the present specification, all other embodiments obtained by a person of ordinary skill in the art without creative work fall within the protection scope of the present specification. In addition, the technical features involved in the different embodiments of the present specification described below can be combined with each other as long as they do not conflict with each other.

[0078] With the development of electronic devices, application programs (Apps) on electronic devices are emerging in endlessly, and the functions that can be achieved by the application programs are more and more. In order to achieve more realistic and three-dimensional visual effects and interactive experiences, part of the application programs render and display three-dimensional interfaces by embedding 3D engines, and users can interact with the three-dimensional interfaces to achieve various scene displays.

[0079] For example, in one example, taking a shopping application as an example, a 3D engine can be embedded in the shopping App, and a three-dimensional product can be rendered and displayed by using the 3D engine. Users can rotate and flip the product by interacting with the 3D engine interface. Alternatively, a three-dimensional human body model can be rendered and displayed by using the 3D engine, and users can change clothes and pinch the face of the three-dimensional human body model by interacting with the 3D engine interface.

[0080] For example, in another example, taking an electronic pet application as an example, a 3D engine can be embedded in the App, and a three-dimensional virtual pet can be rendered by using the 3D engine. Users can interact with, talk to, and feed the virtual pet by using various controls provided by the 3D engine interface.

[0081] When developing an application program, a 3D engine developer generally encapsulates all functions of 3D engine controls in a 3D engine package, and then an application developer encapsulates the 3D engine package in an App. The functions of 3D engine controls are relatively independent, which leads to great difficulty in developing part of the functions, high maintenance cost, and poor running effect.

[0082] Taking a certain health application as an example, a 3D engine can be embedded in a health App, and a three-dimensional human body model can be rendered and displayed by using the 3D engine. Users can jump to a corresponding web page by clicking different parts of the three-dimensional human body model to view health information corresponding to the part.

[0083] In the related art, when developing the application, the web page of each human body part and the control such as the three-dimensional human body model are encapsulated in a 3D engine package by using a 3D engine, and then the 3D engine package is embedded in the App. When a user interacts with the 3D engine interface and clicks a human body part, the 3D engine calls the corresponding web page to realize page jump and display of health information on the page.

[0084] It can be seen that when developing the App, the web page needs to be developed on the 3D engine side, which has high development difficulty and high development cost. Moreover, when the web page needs to be modified or updated later, maintenance and modification still need to be performed on the 3D engine side, which undoubtedly increases the maintenance difficulty and cost. More importantly, compared with the native engine of the App side, the response speed and fluency of the web page are poor when the 3D engine calls the web page to realize page jump, which affects the user experience.

[0085] Based on the above, the embodiments of the present specification provide an application control method and device, electronic equipment, storage medium and computer program product. Through the interaction between the 3D engine and the App native layer, the calling and display of the web page of the App side are realized. The 3D engine only transmits parameters to the App, and the calling and display functions of the web page do not need to depend on the 3D engine, but are realized by the App, which reduces the development and maintenance difficulty and cost. At the same time, the display page is directly overlaid on the App native interface, without page jump and waiting, which improves the interaction experience.

[0086] For ease of explanation and understanding, first, some nouns or technical terms appearing in the following text of the present specification are explained and described.

[0087] 1. Control: Control refers to the encapsulation of data and methods. The control can have its own attributes and methods, where the attribute is a simple access to the control data, and the method is some simple and visible function of the control. The control creation process includes design, development, debugging work, and then the use of the control. The control can be developed based on different development engines, such as 3D engine, native engine, etc.

[0088] 2. System (OS, Operating System): It is a system software program that manages and controls the operation, use and running of hardware and software resources of a computer and provides public services. According to the running environment, the operating system can be divided into desktop operating system, mobile phone operating system, server operating system, etc. Taking the mobile phone operating system as an example, the mainstream operating systems include Android, IOS, etc.

[0089] 3. 3D Engine: This refers to pre-written, editable 3D development systems or the core components of interactive real-time graphics applications. 3D engines provide developers with the tools needed to create various games, virtual scenes, characters, etc., aiming to enable developers to easily and quickly develop 3D scenes without starting from scratch. A typical 3D engine includes a rendering engine, physics engine, collision detection, sound effects, and scripting engine. Currently, the main 3D engines used for application development include the Unity engine and the UE engine.

[0090] 4. Native Engine: This refers to the system or tools provided by the operating system for application development, typically offering various development tools and programming languages. For example, in the Android operating system, the native engine includes Android Studio. Android Studio is an integrated development environment provided by Android, including a code editor, debugging tools, performance analysis tools, and a build system for building applications. Using Android Studio, native Android applications can be created, including various user interfaces and controls.

[0091] 5. H5 Page: H5 refers to HTML5 (HyperText Markup Language 5), a web page design standard. H5 provides a series of semantic tags, APIs (Application Programming Interfaces), and multimedia support, enabling developers to create richer and more interactive web page content. An H5 page is a web page created using the HTML5 standard.

[0092] 6. Page Container: In web design, this refers to the element or area used to contain page content. It is a layout component used to organize and control how page content is displayed. As the foundation of web page layout, the page container defines the boundaries of content and how elements are aligned and distributed within it.

[0093] In some embodiments, this specification provides an application control method that can be applied to an electronic device, which can be any type of device suitable for implementation, and this specification does not limit this.

[0094] For example, in one instance, the electronic device could be an all-in-one machine running a target application. This application is pre-developed and deployed by application developers and runs within the all-in-one machine's operating system. Of course, those skilled in the art will understand that the type of electronic device is not limited to an all-in-one machine; it could also be, for example, a mobile phone, tablet computer, wearable device, etc., which will not be elaborated upon in this specification.

[0095] FIG. 1 shows a structural schematic diagram of an electronic device in some embodiments of the present specification. As shown in FIG. 1, in some embodiments, the electronic device 100 can 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, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, a headphone jack 170D, a sensor module 180, a key 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc.

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

[0097] Among them, the controller can be the nerve center and command center of the electronic device 100. The controller can generate operation control signals according to instruction operation codes and timing signals, and complete the control of fetching and executing instructions.

[0098] The memory in the processor 110 can also be provided for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory can save instructions or data that have just been used or are repeatedly used by the processor 110. If the processor 110 needs to use the instructions or data again, it can be directly called from the memory. Avoiding repeated access, reducing the waiting time of the processor 110, thus improving the efficiency of the system.

[0099] The electronic device 100 implements a display function through a GPU (Graphics Processing Unit), a display screen 194, and an application processor, etc. The GPU is a microprocessor for image processing, and is connected to the display screen 194 and the application processor. The processor 110 can include one or more GPUs that execute program instructions to generate or change display information.

[0100] The display screen 194 is configured to display images, videos, and the like. The display screen 194 includes a display panel. In some embodiments, the electronic device 100 can include one or N display screens 194, where N is a positive integer greater than one.

[0101] The electronic device 100 can implement a photographing function through an ISP, a camera 193, a video codec, a GPU, a display screen 194, and an application processor, etc.

[0102] In the embodiments of the present specification, the processor 110 causes the electronic device to perform the application control method described below in the present specification by running instructions stored in the internal memory 121.

[0103] It can be understood that the structure illustrated in the embodiments of the present specification does not constitute a specific limitation on the electronic device 100. In other embodiments of the present specification, the electronic device 100 can include more or fewer components than those illustrated, or combine certain components, or split certain components, or different arrangement of components. The illustrated components can be implemented in hardware, software, or a combination of software and hardware.

[0104] FIG. 2 illustrates a software system architecture diagram of the electronic device 100 in some embodiments of the present specification. The embodiments of the present specification exemplarily illustrate the software structure of the electronic device 100 by taking an Android system with a layered architecture as an example.

[0105] As shown in FIG. 2, the Android operating system software architecture can be divided into four layers, which are an Applications layer, an Application Framework layer, a Libraries layer, and a Linux Kernel layer, respectively.

[0106] 1. Applications layer

[0107] The application layer is the layer in the Android system that interacts with the user. The application layer includes various applications of the mobile phone, such as system applications of settings, contacts, messages, calls, gallery, calendar, browser, and the like, or third-party applications such as WeChat. The application layer can access the services provided by the application framework layer according to different applications. Generally, the application is developed using the Java language, and is completed by calling the application programming interface (API) provided by the application framework layer.

[0108] 2. Application framework layer

[0109] The application framework layer mainly provides developers with various APIs that can be accessed by the application. For different applications, the APIs provided by the application framework layer for the application layer are different, and the services are also different.

[0110] Specifically, the developer can interact with the underlying of the operating system (such as function library, Linux kernel, etc.) through the application framework to develop his own application. The application framework can be a series of services and management systems of the operating system. The application framework mainly includes the following basic services:

[0111] Window Manager module: used for managing the graphical user page resources used on the screen, and specifically can include: creation and destruction of page objects, display and hiding of page objects, page layout, management of focus, and input method and wallpaper management, and the like.

[0112] Activity Manager module: used for managing the life cycle of each application. The application usually runs in the operating system in the form of Activity. For each Activity, there is an application record (Activity Record) corresponding to the Activity in the activity manager, and the Activity Record records the state of the Activity of the application. The activity manager can use the Activity Record as an identifier to schedule the Activity process of the application.

[0113] View: has a rich and extensible view set that can be used to build an application, and specifically includes List, Grid, TextBox, Button, and an embeddable web browser.

[0114] Notification Manager module: used to control the application to display prompt information (e.g. Alerts, Notifications, etc.) to the user in the status bar, lock screen interface, etc.

[0115] 3. Function library layer

[0116] The function library layer is the support of the application framework and is an important link between the application framework layer and the Linux kernel layer. The function library layer includes some function libraries compiled by computer program C language or C++ language, which can be used by different components in the operating system, and they provide services for developers through the application framework layer. Specifically, the function library can include the libc function library, which is specially customized for embedded Linux-based devices; the function library can also include the multimedia library (Media Framework), which supports the playback and recording of audio or video in multiple encoding formats, as well as static image files and common audio or video encoding formats. The function library also includes the interface management library (Surface Manager), which is mainly responsible for managing access to the display system and is specifically used to manage the interaction between display and access operations when multiple applications are executed, and is also responsible for 2D drawing and 3D drawing display synthesis.

[0117] The function library layer can also include other function libraries for implementing various functions of the mobile phone, such as: scalable graphics library (SGL): a 2D graphics image processing engine based on extensible markup language (XML) files; secure sockets layer (SSL): located between TVP / IP protocol and various application layer protocols, providing support for data communication; three-dimensional graphics processing library (OpenGL / ES): support for 3D effects; lightweight database (SQLite): a relational database engine; Webkit: Web browser engine; FreeType: bitmap and vector font support; etc.

[0118] Android Runtime is a running environment on the operating system and is a new virtual machine used by the operating system. In the Android Runtime, the AOT (Ahead-Of-Time) technology is adopted, and the bytecode of the application is pre-compiled into machine code when the application is installed for the first time, so that the application becomes a real native application, and after that, the compilation step is omitted, and the startup and execution will become faster.

[0119] In some other embodiments of the present specification, the Android Runtime can also be replaced by Core Libraries and Dalvik Virtual Machine. The Core Libraries provide most of the functionality in the Java language API, mainly through the Java Native Interface (JNI) to the Application Framework layer to provide interfaces to call underlying libraries. It also contains some core APIs of the operating system, such as android.os, android.net, android.media, etc. The Dalvik Virtual Machine uses a JIT (Just-in-Time) runtime compilation mechanism, and each time a process is started, the virtual machine needs to recompile the bytecode in the background, which will have a certain impact on the startup speed. Each application runs in an instance of a Dalvik virtual machine, and each Dalvik virtual machine instance is a separate process space. The Dalvik virtual machine is designed to efficiently run multiple virtual machines on a device. The Dalvik virtual machine executable file format is.dex, and the dex format is a compression format designed for Dalvik, suitable for systems with limited memory and processor speed. It needs to be pointed out that the Dalvik virtual machine relies on the Linux kernel to provide basic functions (threads, underlying memory management). It can be understood that the Android Runtime and Dalvik belong to different types of virtual machines, and those skilled in the art can choose different forms of virtual machines under different circumstances.

[0120] 4. Linux kernel layer

[0121] The Linux kernel layer provides the core system services of the operating system, such as security, memory management, process management, network protocol stack, and driver model, which are all based on the Linux kernel. The Linux kernel also serves as an abstraction layer between hardware and software stacks. This layer has many device-related drivers, including display drivers, Linux-based frame buffer drivers, keyboard drivers as input devices, Flash drivers based on memory technology devices, camera drivers, audio drivers, Bluetooth drivers, Wi-Fi drivers, and the like.

[0122] Based on the above understanding, the application control method of the embodiments of the present specification will be described below.

[0123] As shown in FIG. 3, in some embodiments, the application control method of the present specification includes:

[0124] S310, displaying a first control on a native interface of a target application.

[0125] In the embodiments of the present specification, the target application refers to an application program running on the electronic device, and the target application can be any suitable type of application for implementation, such as a shopping application, a health application, a game application, etc., which is not limited in the present specification.

[0126] It can be understood that the native interface refers to the application interface displayed on the display screen of the electronic device when the electronic device runs the target application, and the native interface refers to the App native interface developed based on the native engine. In the embodiments of the present specification, the native interface includes a first control, which refers to a control rendered based on the 3D engine.

[0127] In the embodiments of the present specification, the 3D engine is embedded in the target application, that is, the 3D engine package developed based on the 3D engine is encapsulated in the target application, so that related functions developed based on the 3D engine can be embedded in the target application. When the 3D engine package is running, the first control can be rendered and displayed on the native interface of the target application.

[0128] In the embodiments of the present specification, the 3D engine can be any suitable engine tool for developing a three-dimensional scene or model, such as Unity engine, UE engine, etc., which is not limited in the present specification.

[0129] The first control can be understood as a component developed based on the 3D engine and displayed on the native interface, and capable of interacting with the user. For example, in one example, the first control can include a three-dimensional human model, and the user can interact with the three-dimensional human model to realize functions such as model rotation, scaling, and dressing. For example, in another example, the first control can include a virtual scene, and the user can interact with the virtual scene to realize functions such as scene switching and animation effects. For example, in another example, the first control can include a virtual pet, and the user can interact with the virtual pet to realize functions such as dialogue and nurturing. For example, in another example, the first control can include a virtual button, and the user can interact with the virtual button to realize functions such as selection of corresponding functions.

[0130] In summary, it can be understood that the first control of the embodiments of the present specification refers to a control developed by using the 3D engine and embedded in the target application, which can be implemented in different forms according to different application types, which cannot be exhausted in the present specification.

[0131] As can be understood from the foregoing, since it is necessary to embed the 3D engine in the target application, when developing the target application, the 3D engine package implementing the first control function can be developed by using the 3D engine first, and then the 3D engine package is encapsulated in the target application. When the target application is running, the system can call the 3D engine package to render and display the 3D engine interface of the first control on the native interface.

[0132] For example, in one example, the target application is a health application, as shown in FIG. 4, the native interface 601 of the target application includes a first control, and the first control includes a three-dimensional human model 602 and a button control 603. In the example of FIG. 4, the three-dimensional human model 602 and the button control 603 are first controls developed based on a 3D engine and displayed on the native interface 601 of the target application.

[0133] In the example of FIG. 4, the three-dimensional human model 602 is a three-dimensional model of a human body. It can be understood that in the field of computer graphics, a mesh model is usually used to represent the geometry of a three-dimensional object, and the mesh model is composed of a large number of discrete vertices, edges connecting two vertex points, and mesh facets composed of multiple edges. For example, in some embodiments, the mesh facet can be a triangular facet, that is, a triangle formed by three vertices is a mesh facet, so that the mesh model is a continuous surface composed of a large number of triangular facets. For example, in some other embodiments, the mesh facet can be a quadrilateral, that is, a quadrilateral formed by four vertices is a mesh facet, so that the mesh model is a continuous surface composed of a large number of quadrilateral facets.

[0134] The button control 603 refers to a virtual button for interacting with the user. For example, in the example of FIG. 4, the first control includes a plurality of button controls 603, and each button control 603 is associated with a different body part of the three-dimensional human model, such as "brain", "skin", "heart", and the like. Thus, when the user clicks a certain button control 603, a corresponding trigger operation can be triggered, which will be described below.

[0135] It should be noted that in the example of FIG. 4, the control provided by the 3D engine interface for interacting with the user can be the button control 603 or the three-dimensional human model 602. That is, the three-dimensional human model 602 itself can interact with the user. For example, the three-dimensional human model 602 can be divided into different body parts, and the user can click a certain body part to trigger a corresponding trigger operation. For example, when the user clicks the head region A, a trigger operation for the "brain" can be triggered, which will be described below.

[0136] S320, in response to detecting the first trigger operation on the first control, determining, by the 3D engine, a target web page corresponding to the first trigger operation and a web page parameter of the target web page, and sending the web page parameter to the target application.

[0137] In the embodiments of the present application, when the user interacts with the first control of the native interface, a corresponding target web page can be created and displayed on the native interface. The target web page can include text, images, hyperlinks, and the like, thereby displaying relevant information to the user.

[0138] Still taking the application shown in FIG. 4 as an example, when the user clicks the "brain" button control 603, it indicates that the user wants to know the health status of the current brain, so the application can call the target webpage related to the brain health according to the user's click operation, and display the target webpage on the native interface.

[0139] To achieve the above functions, in the embodiments of the present specification, the system needs to detect the first trigger operation of the user on the first control. The first trigger operation refers to the operation of the user on the first control on the native interface. The specific operation type of the first trigger operation can be clicking, long pressing, gestures, voice, etc., which is not limited in the present specification.

[0140] For example, in one example, the first control includes a three-dimensional human model. As described earlier, the three-dimensional human model can be pre-divided into multiple body parts. When the user clicks on a certain body part of the three-dimensional human model, it can be determined that the first trigger operation on the body part is detected.

[0141] For example, in another example, referring to FIG. 4, the first control includes a three-dimensional human model 602 and at least one button control 603. Each button control 603 can be pre-associated with a body part. When the user clicks on a certain button control 603, it can be determined that the first trigger operation on the associated body part is detected.

[0142] In the example scenario of the present specification, when the first trigger operation is detected, the corresponding target webpage needs to be displayed on the electronic device. In the embodiments of the present specification, unlike the traditional scheme, the calling and display of the target webpage are not performed in the 3D engine. The 3D engine is only used to pass the webpage parameters of the target webpage to the native layer of the target application, and the calling and display of the target webpage are performed by the native engine of the target application.

[0143] FIG. 5 shows a software structure diagram of the target application in some embodiments of the present specification. Referring to FIG. 5, the 3D engine is embedded in the target application, and the first control function developed based on the 3D engine is encapsulated in the 3D engine package. The 3D engine can interact with the target application through the native layer of the target application.

[0144] In the embodiments of the present specification, the webpage library containing the target webpage is not encapsulated in the 3D engine, in other words, the webpages in the webpage library do not need to be developed and encapsulated by using the 3D engine, but are developed by using the native engine of the target application and encapsulated in the native application file. Only the webpage parameters of each webpage in the webpage library need to be encapsulated in the 3D engine, so that when the first trigger operation is detected, the webpage parameters of the corresponding target webpage are determined according to the first trigger operation, and then the webpage parameters are passed to the native layer of the target application. After the target application receives the webpage parameters passed by the 3D engine, the corresponding webpage page is called and created by using the native engine, and page display is realized.

[0145] The native layer refers to an interface layer in the target application for communication with the 3D engine. In some embodiments, the method of data communication between the native layer and the 3D engine can be defined in advance, so that the 3D engine can call the method to pass the webpage parameters to the native layer.

[0146] For example, taking the Android system as an example, the 3D engine can call the Unity Send Message method to send webpage parameters to the native layer of the Android application. Unity Send Message is a method provided by the Unity engine for sending messages in C# scripts to Game Objects mounted with specific scripts, which can be used to send messages from the Unity 3D engine to the Android native layer.

[0147] In combination with the example of FIG. 4, the first trigger operation can be a trigger operation for different human body parts, and therefore the corresponding webpages are different. In the embodiments of the present specification, the corresponding webpage library can be configured in advance for different first trigger operations. The webpage library includes multiple webpages. As known from the foregoing, the webpages in the webpage library can be developed based on the native engine of the target application. Only the webpage parameters of each webpage in the webpage library need to be encapsulated in the 3D engine.

[0148] The webpage parameters refer to the parameters required by the native engine to create a webpage. In the embodiments of the present specification, the webpage parameters include but are not limited to page position, page size, webpage link, etc.

[0149] In the embodiments of the present specification, when the system detects the first trigger operation, the 3D engine needs to determine the webpage parameters of the target webpage corresponding to the first trigger operation from the stored webpage parameters of the webpage library, and then call the native layer communication method to send the webpage parameters to the target application. The following will be described in combination with FIG. 6.

[0150] As shown in FIG. 6, in some embodiments, the process of determining the webpage parameters of the target webpage by the 3D engine and sending the webpage parameters to the target application in the application control method of the present specification includes:

[0151] S321, the 3D engine determines the target webpage corresponding to the first trigger operation and the webpage parameter of the target webpage based on the pre-packaged mapping relationship.

[0152] S322, the 3D engine calls a communication method between the native layer of the target application to send the webpage parameter to the target application.

[0153] In the embodiments of the present specification, the webpage library can be pre-developed by using the native engine of the target application, and the corresponding mapping relationship is configured in the 3D engine, which represents the corresponding relationship between different first trigger operations and different webpages and webpage parameters.

[0154] For example, in one example, the mapping relationship at the 3D engine end can be as shown in Table 1:

[0155] Table 1

[0156] In combination with the example of Table 1, the mapping relationship at the 3D engine end includes the corresponding relationship between each webpage (and webpage parameter) and each human body part in the three-dimensional human body model, and each human body part is associated with a corresponding first trigger operation, so that in the case of detecting the first trigger operation, the corresponding target webpage can be determined according to the human body part associated with the first trigger operation through the mapping relationship shown in Table 1, for example, and the webpage parameter corresponding to the target webpage.

[0157] In the example of Table 1, in combination with FIG. 4, when the first trigger operation is "operation A", it means that the user triggers the trigger operation for the human body part "brain", and the webpage corresponding to this operation is "webpage 1". The webpage parameter thereof is (url_1, size_1, loc_1).

[0158] In the examples of the present specification, the webpage parameter is represented by a url, size, and loc triple, wherein the url represents the webpage link, the size represents the page size of the webpage, and the loc represents the page position of the webpage on the native interface. Of course, those skilled in the art can understand that the webpage parameter can also include more or less types of parameters, which are not limited in the present specification.

[0159] It is worth noting that the target webpage corresponding to the first trigger operation can include only one webpage or multiple webpages, which are not limited in the present specification.

[0160] After constructing the above mapping relationship, the mapping relationship can be packaged in the 3D engine, and when the first trigger operation is detected during the running of the target application, the webpage parameter of the target webpage corresponding to the first trigger operation can be determined based on the mapping relationship.

[0161] After determining the webpage parameters of the target webpage, the 3D engine can call a communication method between the native layer according to the foregoing, and send the webpage parameters to the target application. In combination with FIG. 5, the communication method can be a Unity Send Message method, and the 3D engine calls the Unity Send Message method to send the webpage parameters of the target webpage to the native layer of the target application.

[0162] In S330, the target application creates a page container on the native interface according to the page parameters, and displays the target webpage in the page container.

[0163] In combination with FIG. 5, after the target application receives the webpage parameters of the target webpage sent by the 3D engine, the target application can call the corresponding target webpage according to the webpage link included in the webpage parameters, and then create and display the target webpage on the native interface based on the page position, size and other parameters included in the webpage parameters by using the native engine. The following will be described in combination with FIG. 7.

[0164] As shown in FIG. 7, in some embodiments, the application control method exemplified by the present specification, the process of displaying the target application on the native interface according to the webpage parameters includes:

[0165] In S331, the position parameters of the page container on the native interface are determined according to the page position included in the webpage parameters, and the size parameters of the page container are determined according to the page size included in the webpage parameters.

[0166] In S332, the page container is created on the native interface based on the position parameters and the size parameters.

[0167] In S333, the target webpage is called from the pre-configured webpage library according to the webpage link included in the webpage parameters.

[0168] In S334, the target webpage is configured in the page container.

[0169] In the embodiments of the present specification, when the target application displays the target webpage on the native interface, the page container needs to be created first. The page container refers to a layout component used to carry the target webpage. The position and size of the page container define the position and size of the target webpage. Therefore, when the page container is created, the position and size of the page container need to be determined according to the webpage parameters passed by the 3D engine.

[0170] For example, in some embodiments, the target application receives the webpage parameter sent by the 3D engine, determines the position parameter of the page container based on the page position in the webpage parameter, and determines the size parameter of the page container based on the page size in the webpage parameter. After determining the position parameter and the size parameter of the page container, the native engine of the target application can create the page container on the native interface. For example, as shown in FIG. 8, the position and size of the page container 605 are shown in the figure, and the page container 605 defines the display position and size of the target webpage.

[0171] After the native engine creates the page container 605 on the native interface 601, the target webpage can be displayed in the page container 605, and the rendering and display of the webpage are realized. In the embodiments of the present specification, a plurality of webpages are created based on the native engine in advance, and a webpage library is constructed. To realize the display of the target webpage, the target webpage needs to be called from the webpage library.

[0172] In some embodiments, the webpage library constructed by the target application in advance can be as shown in Table 2 below:

[0173] Table 2

[0174] Therefore, after receiving the webpage parameter sent by the 3D engine, the target application can find the corresponding webpage from the webpage library according to the webpage link in the webpage parameter, that is, the target webpage in the present specification.

[0175] After determining the target webpage, the target application can call the target webpage and configure the target webpage in the page container shown in FIG. 8, for example, to realize the rendering and display of the target webpage on the native interface.

[0176] In some embodiments, the target application takes a health App as an example. For each webpage in the webpage library, the recorded content can include user historical physical examination records, health suggestions recommended to the user, abnormal physiological parameters, and the like. For example, in one example, as shown in FIG. 10, the webpage 606 and the webpage 607 are abnormal indicators and health suggestions displayed for the user according to the health condition of the user.

[0177] It is worth noting that in the embodiments of the present specification, each webpage in the webpage library is developed based on the native engine of the target application. Compared with the webpage developed based on the 3D engine in the traditional scheme, the development difficulty and cost are lower, and when the webpage is modified or updated later, the webpage maintenance and update can also be realized by using the native engine on the application side, which greatly reduces the maintenance difficulty and cost.

[0178] Moreover, in the embodiments of the present specification, the calling and creation of the target webpage are implemented by the target application native engine, and the 3D engine only delivers parameters to the target application, and the calling and display function of the webpage does not need to rely on the 3D engine, so the webpage response speed and fluency are higher, and the user experience is improved.

[0179] In addition, in the embodiments of the present specification, the native engine directly displays the target webpage in the native interface, realizes the overlay display of the target webpage on the native interface, and thus does not need to jump to the webpage, and the webpage display efficiency and interactive experience are improved.

[0180] In some embodiments, in order to further improve the interactive effect, the corresponding scene switching can be performed in the 3D engine interface while the target webpage is displayed, and the scene switching process can be used as a transition effect, so that the interactive effect is more rich, which will be described below in combination with FIG. 9.

[0181] As shown in FIG. 9, in some embodiments, the application control method of the present specification also includes:

[0182] S910, in response to detecting the first trigger operation, the 3D engine determines a target scene associated with a target body part corresponding to the first trigger operation from a pre-configured display scene library.

[0183] S920, rendering and displaying the target scene.

[0184] In one example, as shown in FIG. 4, when the user clicks the “brain” button control 603, the 3D engine interface can switch from the full-body model shown in FIG. 4 to the three-dimensional model of the brain part shown in FIG. 10.

[0185] In implementing the above functions, first, a plurality of display effects can be developed based on the 3D engine during the development of the first control, so as to construct a display scene library, and the display scene library includes a plurality of scenes, and each scene is associated with a corresponding body part. For example, in one example, the display scene library created by the 3D engine can be as shown in Table Three:

[0186] Table Three

[0187] In the display scene library shown in Table Three, the display scene corresponding to each body part is included, and each body part is associated with a first trigger operation. When the first trigger operation is detected, the 3D engine can determine the body part associated with the first trigger operation, and the associated body part is the target body part. Then, the scene corresponding to the target body part can be determined through the display scene library shown in Table Three.

[0188] In the example of Table 3, when the first trigger operation is detected as "operation A", the corresponding target human body part is "brain", and the display scene corresponding to the target human body part "brain" is "scene 1". Then, the 3D engine renders the display according to scene 1 on the interface. Specifically, as shown in FIG. 4 and FIG. 10, first, the appearance of the three-dimensional human body model can be transparently processed, so that the user can view the internal organs of the human body, then the target human body part is highlighted, for example, in the example of FIG. 10, the "brain" part is highlighted by other colors, and finally, the three-dimensional human body model originally displayed in full body can be switched to the target human body part displayed in part, for example, in the example of FIG. 10, only the upper body of the human body is displayed, so as to highlight the brain part.

[0189] It should be noted that when switching from the three-dimensional human body model displayed in full body to the target human body part displayed in part, a certain transition animation effect can be designed to achieve, so as to improve the user interaction experience. In the embodiments of the present specification, the process of developing animation effects based on the 3D engine can be referred to by those skilled in the art in the related art, and the present specification will not be repeated here.

[0190] In the embodiments of the present specification, when the first trigger operation for the first control is detected, on the one hand, the 3D engine determines the web page parameters of the target web page based on the foregoing method process, and delivers the web page parameters to the native layer of the target application, so that the native engine displays the target web page on the native interface. On the other hand, the 3D engine determines the corresponding target scene from the display scene library according to the first trigger operation, and then switches the target scene on the 3D engine interface to achieve the switching effect of the three-dimensional model scene.

[0191] For example, in the example of FIG. 10, on the native interface 601, two target web pages are displayed, which are target web page 606 and target web page 607. At the same time, the three-dimensional model is switched from the human body model shown in FIG. 4 to the three-dimensional model of the brain part shown in FIG. 10 through the target animation transition.

[0192] From the above, it can be seen that in the embodiments of the present specification, the animation transition effect is realized by the 3D engine, and the human-computer interaction experience is improved.

[0193] In some embodiments, when the target web page is displayed on the native interface, in response to detecting a second trigger operation, the target web page displayed on the native interface is switched from a first web page to a second web page, wherein the human body part corresponding to the second trigger operation is different from the first trigger operation.

[0194] For example, in the example of FIG. 10, the user can view the target webpage corresponding to the "brain" through the interface. When the user wants to view other human body parts, the user can perform a second triggering operation in the manner described above, for example, the user can click the "heart" button on the interface. At this time, the new target webpage corresponding to the "heart" can be determined according to the method described above. In the example of the present specification, the target webpage corresponding to the "brain" is the first webpage, and the target webpage corresponding to the "heart" is the second webpage. In this case, the native engine can switch the first webpage originally displayed to the second webpage according to the method described above. In addition, during the switching of the target webpage, the switching of the display scene can also be implemented according to the ninth embodiment described above. Those skilled in the art can understand this, and the present specification will not be repeated.

[0195] As shown in FIG. 11, in some embodiments, the application control method of the present specification further includes:

[0196] S1110, in the case where the target webpage is displayed on the native interface, in response to detecting a third triggering operation, the 3D engine sends a deletion instruction to the target application.

[0197] S1120, the target application deletes part or all of the target webpage displayed on the native interface according to the deletion instruction.

[0198] It can be understood that in the case where the target webpage is displayed on the native interface, the user may need to close the target webpage after viewing the webpage information, so that the application needs to delete the displayed target webpage.

[0199] In the embodiments of the present specification, the third triggering operation refers to an operation for deleting the displayed target webpage. In some embodiments, the third triggering operation can be an operation on the first control of the 3D engine interface, for example, the user clicks other button controls, and then the currently displayed target webpage needs to be deleted. In some other embodiments, the third triggering operation can be an operation on the second control on the native interface, for example, in the example of FIG. 10, the "back" button 608 can be a second control developed based on the native engine, and the user triggers the third triggering operation by clicking the button 608.

[0200] Of course, those skilled in the art can understand that the third triggering operation is not limited to the above examples, but can also be, for example, an operation on the target webpage, such as clicking the close button at the upper right corner of the target webpage, and the present specification does not limit this.

[0201] It can be understood that, since the target webpage is created by the native engine of the target application, it needs to be deleted by the native engine of the target application. In the embodiments of the present specification, after detecting the third trigger operation, the 3D engine can send a deletion instruction to the native layer of the target application. It should be noted that the deletion instruction can be to delete all currently displayed target webpages, or to delete only part of the displayed target webpages.

[0202] For example, in one example, as shown in FIG. 10, in this example, there are 2 target webpages displayed on the native interface, which are target webpage 606 and target webpage 607. The user can click to close one of the target webpages, at this time, the 3D engine sends a deletion instruction to delete part of the target webpages to the native layer of the target application according to the third trigger operation triggered by the user. Alternatively, the user can click the back button 608, at this time, the 3D engine sends a deletion instruction to delete all target webpages to the native layer of the target application according to the third trigger operation triggered by the user.

[0203] After receiving the deletion instruction, the target application can delete the displayed target webpages on the native interface according to the deletion instruction.

[0204] In addition, in some embodiments, during the process of deleting the target webpages, the 3D engine can also switch the scene based on the aforementioned display scene library to switch the three-dimensional model of the brain part shown in FIG. 10 to the three-dimensional model of the human body shown in FIG. 4, which can be understood and fully implemented by those skilled in the art in combination with the foregoing, and the present specification will not repeat it.

[0205] In some embodiments, the above-mentioned webpages can be H5 webpages, and the 3D engine can use Unity engine.

[0206] As can be seen from the above, in the embodiments of the present specification, each webpage in the webpage library is developed based on the native engine of the target application, which has lower development and maintenance difficulty and cost compared with the webpages developed based on the 3D engine in the traditional scheme. Moreover, the calling and creation of the target webpages are realized by the native engine of the target application, without the need to rely on the 3D engine, so that the webpage response speed and fluency are higher, and the user experience is improved. In addition, the native engine directly displays the target webpages in the native interface, realizing the overlay display of the target webpages on the native interface, so that the page display efficiency and interactive experience are improved without jumping the webpages.

[0207] In some embodiments, the present specification provides an application control device, as shown in FIG. 12, the device comprises:

[0208] In a second aspect, the embodiments of the present specification provide an application control device, comprising:

[0209] The view display module 10 is configured to display a first control on a native interface of a target application, wherein the target application is embedded with a 3D engine, the first control is rendered based on the 3D engine, and the native interface is rendered based on a native engine of an operating system.

[0210] The parameter interaction module 20 is configured to, in response to detecting a first trigger operation on the first control, determine, by the 3D engine, a target webpage corresponding to the first trigger operation and a webpage parameter of the target webpage, and send the webpage parameter to the target application.

[0211] The webpage generation module 30 is configured to create, by the target application, a page container on the native interface according to the webpage parameter, and display the target webpage in the page container.

[0212] In some embodiments, the parameter interaction module 20 is configured to:

[0213] The 3D engine determines, based on a pre-encapsulated mapping relationship, a target webpage corresponding to the first trigger operation and a webpage parameter of the target webpage, wherein the mapping relationship represents a corresponding relationship between the first trigger operation and the webpage parameter.

[0214] The 3D engine calls a communication method between a native layer of the target application to send the webpage parameter to the target application.

[0215] In some embodiments, the webpage parameter includes a page position and a page size, and the webpage generation module 30 is configured to:

[0216] determine a position parameter of the page container on the native interface according to the page position included in the webpage parameter;

[0217] determine a size parameter of the page container according to the page size included in the webpage parameter;

[0218] create the page container on the native interface based on the position parameter and the size parameter.

[0219] In some embodiments, the webpage parameter includes a webpage link of the target webpage, and the webpage generation module 30 is configured to:

[0220] retrieve the target webpage from a pre-configured webpage library according to the webpage link included in the webpage parameter;

[0221] configure the target webpage in the page container.

[0222] In some embodiments, the first control includes a three-dimensional human body model, and the first trigger operation includes triggering an operation of each human body part of the three-dimensional human body model.

[0223] In some embodiments, the first control includes a three-dimensional human body model, and the first control includes a three-dimensional human body model and at least one button control, the button control being associated with a human body part of the three-dimensional human body model, and the first trigger operation includes triggering an operation of the button control.

[0224] In some embodiments, the webpage generation module 30 is configured to:

[0225] In response to detecting the first trigger operation, the 3D engine determines a target scene associated with the target human body part from a pre-configured scene library according to the target human body part corresponding to the first trigger operation, and renders a display of the target scene, wherein the target scene includes a three-dimensional model corresponding to the target human body part.

[0226] In some embodiments, in the case that the target human body part is an internal organ of the human body, the webpage generation module 30 is configured to:

[0227] In the case that the target webpage is displayed on the native interface, in response to detecting a second trigger operation, the target webpage displayed on the native interface is switched from a first webpage to a second webpage; wherein the human body part corresponding to the second trigger operation is different from the first trigger operation.

[0228] In some embodiments, the webpage generation module 30 is configured to:

[0229] In the case that the target webpage is displayed on the native interface, in response to detecting a third trigger operation, the 3D engine sends a deletion instruction to the target application;

[0230] The target application deletes part or all of the target webpage displayed on the native interface according to the deletion instruction.

[0231] In some embodiments, the 3D engine includes a Unity engine, and the webpage includes an H5 webpage.

[0232] In some embodiments, the present specification provides an electronic device, comprising:

[0233] a display screen for displaying an application interface;

[0234] a processor; and

[0235] a memory storing computer instructions for causing the processor to execute the method described in any of the above embodiments.

[0236] In some embodiments, the present specification provides a storage medium storing computer instructions for causing a computer to perform the method of any of the above embodiments.

[0237] In some embodiments, the present specification provides a computer program product, which, when executed, implements the method of any of the above embodiments.

[0238] Obviously, the above embodiments are only examples for clearly illustrating the present specification, but not limitation on the embodiments. Based on the above specification, other different forms of changes or variations can be made by those skilled in the art. Here, all the embodiments need not and can not be enumerated. The changes or variations derived therefrom are still within the protection scope of the present specification.

Claims

1. An application control method characterized by comprising: The method comprises: displaying a first control on a native interface of a target application, wherein the target application is embedded with a 3D engine, the first control is rendered based on the 3D engine, and the native interface is rendered based on a native engine of an operating system; in response to detecting a first trigger operation on the first control, determining, by the 3D engine, a target webpage corresponding to the first trigger operation and a webpage parameter of the target webpage, and sending the webpage parameter to the target application; the target application creates a page container on the native interface according to the webpage parameter, and displays the target webpage in the page container.

2. The method of claim 1, wherein, The method comprises: the 3D engine determines, based on a pre-encapsulated mapping relationship, a target webpage corresponding to the first trigger operation and a webpage parameter of the target webpage, wherein the mapping relationship represents a correspondence between the first trigger operation and the webpage parameter; the 3D engine calls a communication method between a native layer of the target application to send the webpage parameter to the target application.

3. The method of claim 1, wherein, The webpage parameter comprises a page position and a page size. The method comprises: determining a position parameter of the page container on the native interface according to the page position included in the webpage parameter; determining a size parameter of the page container according to the page size included in the webpage parameter; creating the page container on the native interface based on the position parameter and the size parameter.

4. The method of claim 1, wherein, The webpage parameter comprises a webpage link of the target webpage; and the method comprises: calling the target webpage from a pre-configured webpage library according to the webpage link included in the webpage parameter; configuring the target webpage in the page container.

5. The method of any one of claims 1 to 4, wherein: the first control comprises a three-dimensional human body model, and the first trigger operation comprises an operation of triggering each human body part of the three-dimensional human body model; and / or the first control comprises a three-dimensional human body model and at least one button control, the button control is associated with a human body part of the three-dimensional human body model, and the first trigger operation comprises an operation of triggering the button control. The method further comprises:

6. The method of claim 5, wherein, in response to detecting the first trigger operation, the 3D engine determines, from a pre-configured display scene library, a target scene associated with a target human body part corresponding to the first trigger operation, and renders and displays the target scene, wherein the target scene comprises a three-dimensional model corresponding to the target human body part. In a case where the target human body part is an internal organ of the human body, the rendering and displaying the target scene comprises:

7. The method of claim 6, wherein, translucifying an appearance of the three-dimensional human body model and highlighting the target human body part; and switching the first control from the three-dimensional human body model to the target human body part. The method further comprises:

8. The method of claim 6, wherein, ​ In a case where the target webpage is displayed on the native interface, in response to detecting a second trigger operation, the target webpage displayed on the native interface is switched from the first webpage to a second webpage; wherein a human body part corresponding to the second trigger operation is different from the first trigger operation.

9. The method of claim 8, wherein, Also comprising: In a case where the target webpage is displayed on the native interface, in response to detecting a third trigger operation, the 3D engine sends a deletion instruction to the target application; The target application deletes part or all of the target webpage displayed on the native interface according to the deletion instruction.

10. The method of claim 1, wherein, The 3D engine comprises a Unity engine, and the webpage comprises an H5 webpage.

11. An application control device characterized by comprising: Comprising: a view display module configured to display a first control on a native interface of a target application, wherein the target application is embedded with a 3D engine, the first control is rendered based on the 3D engine, and the native interface is rendered based on a native engine of an operating system; a parameter interaction module configured to, in response to detecting a first trigger operation on the first control, determine, by the 3D engine, a target webpage corresponding to the first trigger operation and a webpage parameter of the target webpage, and send the webpage parameter to the target application; a webpage generation module configured to create, by the target application, a page container on the native interface according to the webpage parameter, and display the target webpage on the page container.

12. An electronic device, comprising: Comprising: a display screen for displaying an application interface; a processor; and a memory storing computer instructions for causing the processor to execute the method according to any one of claims 1 to 10.

13. A storage medium, characterized by The computer instructions are for causing a computer to execute the method according to any one of claims 1 to 10.

14. A computer program product, characterised in that, The computer program product, when executed, implements the method according to any one of claims 1 to 10.

Images