A screen display method and system for a third-party application of a car machine

Abstract

The application discloses a kind of screen display method and system of car machine third party application, method includes: in the Framework layer of car machine system, Hook plug-in package and virtual screen service are built-in, and Display is created by virtual screen service;When monitoring that user starts third party application, the Hook plug-in corresponding to Hook plug-in package is started by white list mechanism;Based on Hook plug-in, the pixel density parameter of third party application is obtained and the permission operation responding third party application;After response is completed, the display interface of third party application is screened and displayed by Display based on the pixel density parameter of third party application.The application is cooperated by Hook plug-in and Display, and the running permission and behavior of application can be monitored, isolated and controlled, and then the effect that third party application is displayed on car machine screen is optimized.

Description

Technical Field

[0001] This invention relates to the field of virtual screen display technology, and in particular to a screen display method and system for third-party applications in in-vehicle systems. Background Technology

[0002] As the market share of new energy vehicles continues to rise and the hardware configuration of in-vehicle central control screens becomes increasingly advanced, the functions of in-vehicle infotainment systems (CIS) are becoming richer and richer, such as games, karaoke, and cinemas, which greatly improves the playability and entertainment value of applications in the in-vehicle environment.

[0003] However, while providing a wealth of extended applications, the security issues brought about by these applications have gradually attracted attention. These include the sheer number and complexity of the ecosystem of applications; inconsistent application quality leading to unsolicited pop-ups and excessive system resource consumption; and insufficient system disk space due to excessive application installations, resulting in system lag, black screens, or even restarts, seriously affecting driving safety. Furthermore, directly installing third-party applications on the in-vehicle system also presents issues such as resolution compatibility problems or layout errors. Therefore, ensuring the safe and stable operation of the in-vehicle system while optimizing the display of third-party applications on the in-vehicle screen has become an urgent problem to be solved.

[0004] The above content is only used to help understand the technical solution of the present invention and does not represent an admission that the above content is prior art. Summary of the Invention The main objective of this invention is to provide a method and system for displaying third-party applications on a vehicle infotainment system screen, aiming to solve the technical problem of how to optimize the display effect of third-party applications on the vehicle infotainment system screen while ensuring the safe and stable operation of the vehicle infotainment system.

[0005] To achieve the above objectives, this invention provides a third-party application screen display method based on Hook technology, the method comprising: A Hook plugin package and a virtual screen service are built into the Framework layer of the vehicle infotainment system, and a Display is created through the virtual screen service. When a user launches a third-party application, the Hook plugin corresponding to the Hook plugin package is activated through a whitelist mechanism. Based on the Hook plugin, the pixel density parameters of the third-party application are obtained and the permission operations of the third-party application are responded to. After the response is completed, the display interface of the third-party application is displayed on the screen through the Display based on the pixel density parameters of the third-party application.

[0006] Optionally, creating a Display through the virtual screen service includes: Obtain the pixel density parameters of the vehicle's infotainment screen; A Display is created using the virtual screen service based on the pixel density parameters of the vehicle's infotainment screen and the preset virtual display size. Optionally, the step of activating the Hook plugin corresponding to the Hook plugin package through a whitelist mechanism includes: The process of the third-party application is created by forking the system based on zygote; During the creation of the process, it is determined whether the application package name of the third-party application exists in the preset whitelist; If so, load the Hook plugin package and start the Hook plugin corresponding to the Hook plugin package.

[0007] Optionally, after determining whether the application package name of the third-party application exists in the preset whitelist, the method further includes: If the application package name of the third-party application does not exist in the preset whitelist, the Hook plugin package will not be loaded.

[0008] Optionally, responding to the execution permissions and behaviors of the third-party application based on the Hook plugin includes: The Hook plugin is used to call the vehicle system's API; The system monitors the permission operations of the third-party application through the vehicle's infotainment system's API. The Hook plugin responds to permission operations of the third-party application.

[0009] Optionally, the step of displaying the third-party application's display interface on the screen using the Display based on the pixel density parameters of the third-party application includes: The pixel density parameters of the in-vehicle infotainment screen are adjusted based on the pixel density parameters of the third-party application. The third-party application's interface is displayed on the screen using the adjusted Display.

[0010] Optionally, the step of displaying the third-party application's interface on the screen using the adjusted Display includes: A SurfaceView control is created by using the vehicle system's API and floating on the vehicle screen. The SurfaceView control has an embedded Surface. The adjusted Display transmits the display interface of the third-party application to the Surface, so that the SurfaceView control displays the display interface of the Surface.

[0011] Optionally, the Surface can be bound to the adjusted Display.

[0012] Optionally, after the response is completed, and the third-party application's display interface is displayed on the screen via the Display based on the third-party application's pixel density parameters, the method further includes: When the SurfaceView control receives a touch event initiated by the user, the touch event is transmitted to the Display through the API of the vehicle system, so that the third-party application can respond to the touch event.

[0013] Furthermore, to achieve the above objectives, the present invention also proposes a screen display system for third-party applications in in-vehicle infotainment systems, the system comprising: A module is created to embed Hook plugins and virtual screen services into the Framework layer of the vehicle infotainment system, and to create a Display through the virtual screen service. The startup module is used to launch the Hook plugin corresponding to the Hook plugin package through a whitelist mechanism when it detects that a user has launched a third-party application. The processing module is used to obtain the pixel density parameters of the third-party application and respond to the permission operations of the third-party application based on the Hook plugin. The display module is used to display the display interface of the third-party application on the screen based on the pixel density parameters of the third-party application after the response is completed.

[0014] This invention first integrates a Hook plugin package and a virtual screen service into the Framework layer of the vehicle infotainment system. A Display is created through the Virtual Screen service. Then, when a user launches a third-party application, the corresponding Hook plugin is activated via a whitelist mechanism. Based on the Hook plugin, the pixel density parameters of the third-party application are obtained, and permission operations are responded to. Finally, after the response is complete, the third-party application's interface is displayed on the screen based on its pixel density parameters. This invention, through the cooperation of the Hook plugin and Display, can monitor, isolate, and control the running permissions and behaviors of applications, achieving both a rich ecosystem of expanded applications and optimized display effects of third-party applications on the vehicle infotainment screen. Attached Figure Description

[0015] Figure 1 This is a flowchart illustrating the first embodiment of the screen display method for third-party applications in a vehicle infotainment system according to the present invention. Figure 2 This is a structural block diagram of the first embodiment of the screen display system for third-party applications in the vehicle infotainment system of the present invention.

[0016] The realization of the objective, functional features and advantages of the present invention will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0017] It should be understood that the specific embodiments described herein are for illustrative purposes only and are not intended to limit the scope of the invention.

[0018] This invention provides a method for displaying third-party applications on a vehicle infotainment system screen, referring to... Figure 1 , Figure 1 This is a flowchart illustrating the first embodiment of the screen display method for third-party applications in in-vehicle infotainment systems according to the present invention.

[0019] In this embodiment, the screen display method for a third-party application in a vehicle infotainment system includes the following steps: S1, a Hook plugin package and a virtual screen service are built into the Framework layer of the vehicle system, and a Display is created through the virtual screen service.

[0020] It is easy to understand that the executing entity of this embodiment can be a vehicle system with functions such as data processing, network communication and program execution, and this embodiment does not limit it.

[0021] In the specific implementation, it is necessary to modify the Android vehicle system Framework layer, and build in a Hook plugin package and a virtual screen service. The virtual screen service is used to create, manage and destroy virtual screens, and grant system permissions.

[0022] It should also be noted that the virtual screen service can create one or more virtual screens adapted to third-party applications. Third-party applications can be understood as mobile applications installed on the vehicle's infotainment system, and the display screen adapted to the application may be a portrait-oriented display screen.

[0023] Furthermore, the process of constructing a Display is as follows: obtain the pixel density parameters of the vehicle's infotainment screen; create a Display through the virtual screen service based on the pixel density parameters of the vehicle's infotainment screen and the preset virtual display screen size.

[0024] The preset virtual display screen size can be customized by the user, such as an aspect ratio of 4:3 or 16:9.

[0025] S2, when a user launches a third-party application, the Hook plugin corresponding to the Hook plugin package is launched through a whitelist mechanism.

[0026] It should also be noted that when a user launches a third-party application, the system zygote creates a new application process (i.e., the process of the third-party application) through fork. During the process creation, it checks whether the application package name of the third-party application exists in the preset whitelist. If it does, the Hook plugin package is loaded and the corresponding Hook plugin is launched; otherwise, the Hook plugin package is not loaded, and the third-party application runs natively.

[0027] It should be understood that since all applications are created through zygote, the whitelist mechanism can be used to add the names of pre-installed and adapted application packages to the whitelist.

[0028] In the actual implementation, after the Hook plugin package is started, the entry API of the plugin package will also be run. When the plugin is started, it will be attached to the application process.

[0029] S3, based on the Hook plugin, obtain the pixel density parameters of the third-party application and respond to the permission operations of the third-party application.

[0030] Furthermore, based on the Hook plugin, it responds to the running permissions and behaviors of third-party applications, including: calling the vehicle system's API based on the Hook plugin; listening to the permission operations of third-party applications through the vehicle system's API; and responding to the permission operations of third-party applications through the Hook plugin.

[0031] Permission operations can be understood as the running permissions and behaviors used by an application.

[0032] Runtime permissions: For example, if an application needs to request sensitive permissions, it will call the system permission request interface. When the plugin intercepts the permission request interface, it can actively return the permission request result according to the type of sensitive permission.

[0033] Behavior: For example, if application A needs to silently launch application B (background launch behavior), application A will call the system's interface for launching applications (carrying application B's information). When a plugin in application A intercepts this interface, it will find that the application being launched is not itself, and can directly intercept and return that it is not supported, thus avoiding the background launch behavior.

[0034] S4. After the response is completed, the display interface of the third-party application is displayed on the screen through the Display based on the pixel density parameters of the third-party application.

[0035] Furthermore, after the response is completed, the pixel density parameters of the in-vehicle infotainment screen are adjusted based on the pixel density parameters of the third-party application; the screen display of the third-party application's display interface is then displayed through the adjusted Display.

[0036] In a practical implementation, the pixel density parameters of the vehicle's infotainment screen can be replaced with those of the third-party application. In this case, the adjusted pixel density parameters of the display will be the same as those of the third-party application.

[0037] The method for displaying the third-party application's interface on the screen using the adjusted Display is as follows: a SurfaceView control is created that floats on the vehicle's infotainment screen via the vehicle system's API, with the SurfaceView control embedding a Surface; the Surface is bound to the adjusted Display; and the third-party application's interface is transmitted to the Surface via the adjusted Display, so that the SurfaceView control displays the Surface's interface.

[0038] Furthermore, when the SurfaceView control receives a touch event initiated by the user, the touch event is transmitted to the Display via the vehicle system's API, so that the third-party application can respond to the touch event.

[0039] It should be understood that touch events can be click, move, long press, and other events received on the SurfaceView control.

[0040] It should also be noted that when running mobile applications on the vehicle's infotainment system, the application may crash when calling the corresponding interface. The plugin can intercept unsupported interfaces through hooks and return an unsupported status to avoid this situation.

[0041] In this embodiment, a Hook plugin package and a virtual screen service are first built into the Framework layer of the vehicle infotainment system. A Display is then created through the virtual screen service. When a user launches a third-party application, the corresponding Hook plugin is activated through a whitelist mechanism. Based on the Hook plugin, the pixel density parameters of the third-party application are obtained, and the permission operations of the third-party application are responded to. Finally, after the response is completed, the display interface of the third-party application is shown on the screen based on its pixel density parameters. This embodiment, through the cooperation of the Hook plugin and the Display, can monitor, isolate, and control the running permissions and behaviors of applications, achieving both the enrichment of the ecosystem of extended applications and the optimization of the display effect of third-party applications on the vehicle infotainment screen.

[0042] Reference Figure 2 , Figure 2 This is a structural block diagram of a first embodiment of a screen display system for third-party applications in a vehicle infotainment system according to the present invention.

[0043] Create module 2001 to embed Hook plugins and virtual screen services in the Framework layer of the vehicle infotainment system, and create a Display through the virtual screen service; The startup module 2002 is used to start the Hook plugin corresponding to the Hook plugin package through a whitelist mechanism when it detects that a user has started a third-party application. The processing module 2003 is used to obtain the pixel density parameters of the third-party application and respond to the permission operations of the third-party application based on the Hook plugin. The display module 2004 is used to display the display interface of the third-party application on the screen based on the pixel density parameters of the third-party application after the response is completed.

[0044] Other embodiments or specific implementations of the screen display system for third-party applications in vehicles according to the present invention can be referred to the above-described method embodiments, and will not be repeated here.

[0045] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or system. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or system that includes that element.

[0046] The sequence numbers of the above embodiments of the present invention are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0047] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as read-only memory / random access memory, magnetic disk, optical disk) and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of the present invention.

[0048] The above are merely preferred embodiments of the present invention and do not limit the scope of the patent. Any equivalent structural or procedural transformations made based on the description and drawings of the present invention, or direct or indirect applications in other related technical fields, are similarly included within the scope of patent protection of the present invention.

Claims

1. A method for displaying third-party applications on a vehicle infotainment system screen, characterized in that, The method includes the following steps: A Hook plugin package and a virtual screen service are built into the Framework layer of the vehicle infotainment system, and a Display is created through the virtual screen service. When a user launches a third-party application, the process of the third-party application is created by forking the system based on zygote. During the process of creating the process, it is determined whether the application package name of the third-party application exists in the preset whitelist. If the application package name of the third-party application does not exist in the preset whitelist, the Hook plugin package is not loaded; otherwise, the Hook plugin package is loaded and the Hook plugin corresponding to the Hook plugin package is activated. The Hook plugin calls the vehicle system's API, listens for permission operations of the third-party application through the API, and responds to the permission operations through the Hook plugin. After the response is completed, the pixel density parameters of the in-vehicle screen in the Display are adjusted based on the pixel density parameters of the third-party application. The Surface is bound to the adjusted Display. A SurfaceView control is created and floated on the in-vehicle screen through the API. The SurfaceView control embeds the Surface. The display interface of the third-party application is transmitted to the Surface through the adjusted Display so that the display interface of the Surface is displayed on the SurfaceView control.

2. The method as described in claim 1, characterized in that, Creating a Display through the virtual screen service includes: Obtain the pixel density parameters of the vehicle's infotainment screen; A Display is created using the virtual screen service based on the pixel density parameters of the vehicle's infotainment screen and the preset virtual display size.

3. The method as described in claim 1, characterized in that, After transmitting the display interface of the third-party application to the Surface through the adjusted Display, so that the display interface of the Surface is displayed on the SurfaceView control, the method further includes: When the SurfaceView control receives a touch event initiated by the user, the touch event is transmitted to the Display via the API so that the third-party application can respond to the touch event.

4. A screen display system for a third-party application in a vehicle infotainment system, applied to the screen display method for a third-party application in a vehicle infotainment system as described in claim 1, characterized in that, The system includes: A module is created to embed Hook plugins and virtual screen services into the Framework layer of the vehicle infotainment system, and to create a Display through the virtual screen service. The startup module is used to launch the Hook plugin corresponding to the Hook plugin package through a whitelist mechanism when it detects that a user has launched a third-party application. The processing module is used to obtain the pixel density parameters of the third-party application and respond to the permission operations of the third-party application based on the Hook plugin. The display module is used to display the display interface of the third-party application on the screen based on the pixel density parameters of the third-party application after the response is completed.

Images