Display method and device of vehicle-mounted application and vehicle
By creating a shadow user for the secondary screen and allocating user space, the high development cost problem of displaying the same in-vehicle application in a multi-screen configuration in the in-vehicle infotainment system is solved, and application display without code modification is achieved, which reduces development costs and improves compatibility.
Patent Information
- Application Number
- CN202510608410.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-05-13
- Publication Date
- 2025-09-19
AI Technical Summary
In the existing technology, in an in-vehicle infotainment system, the development cost of displaying the same in-vehicle application on multiple screens is high, especially when third-party applications need to modify their code and be re-signed.
By creating a shadow user for each secondary screen and allocating a user space for the shadow user, when the shadow user is detected to be started, the in-vehicle application of the main screen is installed in the user space corresponding to the shadow user. When the application icon is triggered on the desktop of the target secondary screen, the in-vehicle application is run and displayed in the user space of the target secondary screen.
It realizes the display of the same in-vehicle application or different in-vehicle applications on different screens without modifying the code or package name of the in-vehicle application, reducing development costs, being transparent to third-party applications, consuming less resources, and having good compatibility.
Smart Images
Figure CN120670069A_ABST
Abstract
Description
Technical Field
[0001] The present application belongs to the field of vehicle-mounted information display technology, and in particular relates to a display method, device and vehicle for vehicle-mounted applications. Background Art
[0002] With the prevalence of multi-screen configurations in existing in-vehicle infotainment (IVI) systems, users often need to use the same or different in-vehicle applications on different screens within the vehicle. For example, both the front driver and rear passenger may need to use in-vehicle applications such as navigation or multimedia on the corresponding screens.
[0003] Related technologies often use multiple package names to enable the use of the same in-car app on different screens. Specifically, multiple app instances are generated by modifying the in-car app's package name, and then running each instance on each screen. This method requires repackaging the app for each instance, which is a significant workload. This is especially true for third-party apps, as developers must collaborate on code modifications and re-signing, resulting in high development costs. Summary of the Invention
[0004] The embodiments of the present application provide a method, device, and vehicle for displaying an in-vehicle application, thereby reducing, at least to a certain extent, the development cost of displaying the same in-vehicle application or different in-vehicle applications on different screens in the vehicle.
[0005] Other features and advantages of the present application will become apparent from the following detailed description, or may be learned in part by practice of the present application.
[0006] According to a first aspect of an embodiment of the present application, a method for displaying in-vehicle applications is provided, which is applied to a vehicle, the vehicle including a main screen and at least one secondary screen. The method for displaying in-vehicle applications includes: creating a corresponding shadow user for each secondary screen, and allocating a user space for the shadow user; when the shadow user is monitored to be started, installing the in-vehicle application of the main screen into the user space corresponding to the shadow user; when the application icon in the desktop of the target secondary screen is triggered, running the in-vehicle application corresponding to the application icon in the user space corresponding to the target secondary screen, and outputting the in-vehicle application corresponding to the application icon to the target secondary screen for display.
[0007] In some embodiments, a corresponding shadow user is created for each secondary screen, including: creating multiple shadow users based on the Android user management framework; and binding the secondary screens and shadow users one-to-one.
[0008] In some embodiments, creating multiple shadow users based on the Android user management framework includes: calling the createProfileForUser interface of the Android user management framework to create multiple users; and setting the user type to a shadow user.
[0009] In some embodiments, when a shadow user is monitored to be started, the in-vehicle application on the main screen is installed into the user space corresponding to the shadow user, including: obtaining an application list based on the in-vehicle applications that support multiple openings in the in-vehicle applications on the main screen; when a shadow user is monitored to be started, the in-vehicle application in the application list is installed into the user space corresponding to the shadow user.
[0010] In some embodiments, the display method of the in-vehicle application further includes: calling the startUserInBackgroundWithListener interface of the Android user management framework to start each shadow user, and monitoring the startup status of each shadow user.
[0011] In some embodiments, installing the in-vehicle applications in the application list into the user space corresponding to the shadow user includes: calling the installExistingPackage interface of the Android user management framework to install the in-vehicle applications in the application list into the user space corresponding to the shadow user.
[0012] In some embodiments, the display method of the in-vehicle application further includes: storing user data of the target secondary screen in a corresponding user space.
[0013] According to a second aspect of an embodiment of the present application, a display device for an in-vehicle application is provided, which is applied to a vehicle, the vehicle including a main screen and at least one secondary screen, and the display device for the in-vehicle application includes: a shadow user creation module, which is used to create a corresponding shadow user for each secondary screen and allocate a user space for the shadow user; an in-vehicle application installation module, which is used to install the in-vehicle application of the main screen into the user space corresponding to the shadow user when monitoring the startup of the shadow user; and an in-vehicle application display module, which is used to run the in-vehicle application corresponding to the application icon in the user space corresponding to the target secondary screen when the application icon in the desktop of the target secondary screen is triggered, and output the in-vehicle application corresponding to the application icon to the target secondary screen for display.
[0014] According to a third aspect of an embodiment of the present application, a vehicle is provided, comprising a processor and a memory, wherein the memory stores computer program instructions that can be executed by the processor, and when the processor executes the computer program instructions, the steps of any method of the first aspect described above are implemented.
[0015] According to the fourth aspect of the embodiments of the present application, a computer-readable storage medium is provided, in which computer program instructions are stored. When the computer program instructions are executed by a processor, the processor is prompted to implement the steps of any method as described in the first aspect above.
[0016] In this application, a corresponding shadow user is created for each secondary screen, and a user space is allocated to the shadow user; when the shadow user is detected to be started, the in-vehicle application of the main screen is installed in the user space corresponding to the shadow user; when the application icon in the desktop of the target secondary screen is triggered, the in-vehicle application corresponding to the application icon is run in the user space corresponding to the target secondary screen, and the in-vehicle application corresponding to the application icon is output to the target secondary screen for display. The above solution does not require modifying the code or package name of the in-vehicle application, and is completely transparent to third-party in-vehicle applications. It does not require the cooperation of the developer of the in-vehicle application, and reduces the development cost when displaying the same in-vehicle application or different in-vehicle applications on different screens in the vehicle.
[0017] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS
[0018] The accompanying drawings are incorporated into and constitute a part of the specification, illustrating embodiments consistent with the present application and, together with the specification, explaining the principles of the present application. Obviously, the drawings described below are only some embodiments of the present application, and those skilled in the art can derive other drawings based on these drawings without inventive effort. In the drawings:
[0019] Figure 1 A schematic diagram showing a flow chart of a method for displaying an in-vehicle application according to some embodiments of the present application is shown;
[0020] Figure 2 A schematic diagram showing a flow chart of a method for displaying an in-vehicle application according to other embodiments of the present application is shown;
[0021] Figure 3 A block diagram of a display device for vehicle-mounted applications according to some embodiments of the present application is shown;
[0022] Figure 4 A schematic structural diagram of a vehicle according to some embodiments of the present application is shown. DETAILED DESCRIPTION
[0023] The following will be combined with the drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.
[0024] In addition, described feature, structure or characteristic can be combined in one or more embodiments in any suitable manner.In the following description, many specific details are provided so as to provide a full understanding of the embodiments of the present application. However, it will be appreciated by those skilled in the art that the technical scheme of the present application can be put into practice without one or more of the specific details, or other methods, components, devices, steps etc. can be adopted. In other cases, known methods, devices, implementations or operations are not shown or described in detail to avoid blurring the various aspects of the application.
[0025] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically separate entities. That is, these functional entities may be implemented in software, in one or more hardware modules or integrated circuits, or in different networks and / or processor devices and / or microcontroller devices.
[0026] The flowcharts shown in the accompanying drawings are for illustrative purposes only and do not necessarily include all contents and operations / steps, nor must they be executed in the order described. For example, some operations / steps may be decomposed, while others may be combined or partially combined. Therefore, the actual execution order may vary depending on the actual situation.
[0027] In order to enable those skilled in the art to better understand the present application, the background of the display method for vehicle-mounted applications involved in the present application is first briefly described.
[0028] For application scenarios where users in a vehicle need to use the same in-vehicle application on different screens, traditional implementation solutions include multi-package name technology, virtual machine / container technology, or native support for multiple instances of in-vehicle applications. Among them, multi-package name technology generates multiple application instances by modifying the package name of the in-vehicle application and runs the application instances on each screen. This method requires repackaging the application for each instance, which is a huge workload. Especially for third-party applications, developers need to cooperate in modifying the code and re-signing, which results in high development costs. Virtual machine / container technology runs in-vehicle applications by creating multiple virtual environments. This method consumes a lot of resources and performs poorly under the limited computing resources of the vehicle computer. There are very few in-vehicle applications that natively support multiple instances. Most in-vehicle applications do not have this function, and the scope of implementation is limited.
[0029] This application is based on shadow user technology. It creates a corresponding shadow user for each secondary screen and allocates a user space for the shadow user. When the shadow user is detected to be started, the in-car application on the main screen is installed in the user space corresponding to the shadow user. When the application icon on the desktop of the target secondary screen is triggered, the in-car application corresponding to the application icon is run in the user space corresponding to the target secondary screen, and the in-car application corresponding to the application icon is output to the target secondary screen for display. This solution can realize the display of the same in-car application or different in-car applications on different screens without modifying the code or package name of the in-car application. It is completely transparent to third-party applications and does not require the cooperation of developers. It can be implemented on the vehicle side without the need to synchronize data between the cloud and the vehicle side, which reduces development costs, consumes less resources, and has better compatibility.
[0030] It should be noted that the execution subject of the embodiments of the present application can be a computing service device in the vehicle that has data processing, network communication, and program execution functions, such as the controller of the main screen or the vehicle controller of the vehicle where the main screen and auxiliary screen are located. For ease of description, the following description of the embodiments of the present application and the following embodiments takes the execution subject as an example of a controller.
[0031] Figure 1 FIG2 shows a flow chart of a method for displaying an in-vehicle application according to some embodiments of the present application. Figure 1 As shown, a method for displaying an in-vehicle application is provided, which is applied to a vehicle including a main screen and at least one sub-screen. The method may include the following steps 101 to 103.
[0032] Step 101: Create a corresponding shadow user for each secondary screen and allocate a user space for the shadow user;
[0033] Step 102: When a shadow user is detected to be started, the in-car application on the main screen is installed into the user space corresponding to the shadow user;
[0034] Step 103, when the application icon in the desktop of the target secondary screen is triggered, the in-vehicle application corresponding to the application icon is run in the user space corresponding to the target secondary screen, and the in-vehicle application corresponding to the application icon is output to the target secondary screen for display.
[0035] Among them, the main screen can be the central control screen, and the sub-screen can be a display screen installed in the rear row, a head-up display system (HUD), etc. The embodiment of this application does not limit the specific setting positions of the main screen and the sub-screen.
[0036] Shadow user is a hidden, non-interactive user type in the Android system, designed for background tasks or data isolation, with characteristics such as invisibility and no interactive interface.
[0037] In-vehicle applications are software programs designed specifically for automotive environments and run on vehicle intelligent systems (such as car computers, in-vehicle infotainment systems, T-Box, etc.). They aim to provide driving assistance, infotainment, vehicle control, remote services and other functions to enhance driving experience, safety and intelligence.
[0038] App icons are graphical identifiers that users use to identify, access, and differentiate in-car apps. They are typically presented with a simple visual design (such as a logo, symbol, or text). The secondary screen's desktop can display the app icons of in-car apps installed in the user space of the corresponding shadow user.
[0039] In step 101, a corresponding shadow user can be created for each secondary screen based on the Android user management framework, and an independent user space can be allocated to the shadow user to isolate the shadow user from the main user and the data between the shadow users.
[0040] In step 102, the startup status of the shadow user can be monitored based on the Android user management framework, and the in-car applications on the main screen can be installed into the user space corresponding to the shadow user based on the Android user management framework, so that each shadow user can independently run the in-car applications in the corresponding user space. During the implementation process, when the shadow user startup is monitored, all or part of the in-car applications on the main screen can be installed into the user space corresponding to the shadow user. For example, the in-car applications that support multiple openings in the in-car applications on the main screen can be installed into the user space corresponding to the shadow user. In this way, the in-car applications on the main screen can be shared between the main user and the shadow user.
[0041] During implementation, it is also possible to determine which in-car apps on the main screen should be installed into the user space corresponding to the shadow user based on whether this is the first launch by the shadow user. For example, if it is detected that the shadow user is launching the app for the first time, all in-car apps on the main screen that support multiple openings can be installed into the user space corresponding to the shadow user. If it is detected that the shadow user is not launching the app for the first time, newly added in-car apps on the main screen that support multiple openings can be installed into the user space corresponding to the shadow user. This can reduce redundant loading, thereby reducing resource usage and saving memory.
[0042] In step 103, the desktops of all secondary screens can display the application icons of the in-vehicle applications installed in the user space of the corresponding shadow user. The passengers in the vehicle can trigger the application icons of the in-vehicle applications they want to display through various methods such as touch and voice. The target secondary screen is the secondary screen that currently needs to display the in-vehicle application. When the application icon on the desktop of the target secondary screen is triggered, it can send a trigger signal to the controller. When the controller receives the trigger signal, it can run the in-vehicle application corresponding to the application icon in the user space corresponding to the target secondary screen, and output the in-vehicle application corresponding to the application icon to the target secondary screen, and the target secondary screen will display the in-vehicle application corresponding to the application icon. In this way, the in-vehicle applications between each secondary screen and between the main screen and the secondary screen can be completely independent of each other without interfering with each other, thereby realizing personalized display of different screens. If the in-vehicle applications of the main screen include in-vehicle applications that support multiple openings, it can also be achieved that the same in-vehicle application is displayed on different screens.
[0043] The embodiment of the present application creates a corresponding shadow user for each secondary screen and allocates a user space for the shadow user; when the shadow user is detected to be started, the in-vehicle application on the main screen is installed in the user space corresponding to the shadow user; when the application icon on the desktop of the target secondary screen is triggered, the in-vehicle application corresponding to the application icon is run in the user space corresponding to the target secondary screen, and the in-vehicle application corresponding to the application icon is output to the target secondary screen for display. The above solution can realize the display of the same in-vehicle application or different in-vehicle applications on different screens without modifying the code or package name of the in-vehicle application. It is completely transparent to third-party applications and does not require the cooperation of developers. It can be implemented on the vehicle side without the need for data synchronization between the cloud and the vehicle side, reducing development costs, reducing resource consumption, and improving compatibility.
[0044] In some embodiments, creating a corresponding shadow user for each secondary screen may include: creating multiple shadow users based on the Android user management framework; and binding the secondary screens to the shadow users in a one-to-one correspondence.
[0045] The Android User Management Framework, part of the android.os package, is a core component of the Android system's APIs and services for managing multiple users on devices. It handles user account creation, switching, permission control, and lifecycle management, and is primarily used on devices that support multiple users.
[0046] It is understandable that the controller can first obtain the number of secondary screens, then create the same number of shadow users as the secondary screens, and then bind the secondary screens and shadow users one-to-one to reduce resource consumption.
[0047] During the implementation process, you can call the createProfileForUser interface of the Android user management framework to create multiple users, and then set the user type to a shadow user.
[0048] For example, you can call the createProfileForUser interface of the UserManager in the Android user management framework to create multiple users, passing in the flag that the types of the multiple users to be created are shadow users. After creating the shadow users, you can also call the setUserRestrictions interface of the UserManager to set the restriction attributes of each user to implement the attribute configuration of the shadow users.
[0049] The creation of shadow users is achieved through the Android native user management framework, which improves the stability and compatibility of the system.
[0050] In some embodiments, when a shadow user is monitored to be started, the in-vehicle application of the main screen is installed into the user space corresponding to the shadow user, which may include: obtaining an application list based on the in-vehicle applications that support multiple openings in the in-vehicle applications of the main screen; when a shadow user is monitored to be started, installing the in-vehicle application in the application list into the user space corresponding to the shadow user.
[0051] It can be understood that an in-vehicle application that supports multi-opening refers to an in-vehicle application that can run multiple identical instances at the same time.
[0052] During implementation, you can call the startUserInBackgroundWithListener interface of the Android user management framework to start each shadow user and monitor the startup status of each shadow user. You can also call the installExistingPackage interface of the Android user management framework to install the in-vehicle apps in the application list into the user space corresponding to the shadow user.
[0053] For example, the startUserInBackgroundWithListener interface of ActivityManager in the Android user management framework may be called to start each shadow user in the background and monitor the start status of each shadow user.
[0054] For example, the installExistingPackage interface of PackageInstaller in the Android user management framework may be called to install the in-vehicle applications in the application list into the user space corresponding to the shadow user.
[0055] By generating an application list of in-car applications that support multiple openings in the main screen's in-car applications and installing the in-car applications in the application list in the user space, it is possible to display the same in-car applications as the main screen on the secondary screen, or to display the same in-car applications between secondary screens.
[0056] In some embodiments, the user data of the target secondary screen may be stored in the corresponding user space.
[0057] It can be understood that there is a one-to-one correspondence between the secondary screen and the shadow user, and there is a one-to-one correspondence between the shadow user and the user space, so there is also a one-to-one correspondence between the secondary screen and the user space.
[0058] After the in-car app is displayed on the target secondary screen, the user can operate the in-car app, which will generate user data such as navigation history and playlists. By storing user data in the user space corresponding to the secondary screen, user data can be isolated and stored, improving the privacy and security of user data.
[0059] Figure 2 FIG2 shows a flow chart of a method for displaying an in-vehicle application according to other embodiments of the present application. Figure 2 As shown, the display method of the in-vehicle application may include the following steps:
[0060] Step 201: Call the createProfileForUser interface of the Android user management framework to create multiple users, set the user type to shadow user, bind the secondary screen to the shadow user one by one, and allocate user space for the shadow user;
[0061] Step 202: Call the startUserInBackgroundWithListener interface of the Android user management framework to start each shadow user and monitor the startup status of each shadow user;
[0062] Step 203: Obtain an application list based on the in-car applications that support multiple openings in the in-car applications on the main screen;
[0063] Step 204: When the shadow user is detected to be started, the installExistingPackage interface of the Android user management framework is called to install the in-vehicle application in the application list into the user space corresponding to the shadow user;
[0064] Step 205: When the application icon on the desktop of the target secondary screen is triggered, the in-vehicle application corresponding to the application icon is run in the user space corresponding to the target secondary screen, and the in-vehicle application corresponding to the application icon is output to the target secondary screen for display;
[0065] Step 206: Store the user data of the target secondary screen into the corresponding user space.
[0066] The embodiments of the present application have high stability and compatibility by creating shadow users, starting shadow users, monitoring the startup status of shadow users, and installing in-vehicle applications based on the Android user management framework; by installing in-vehicle applications that support multiple openings into the user space, it is possible to display the same in-vehicle applications as the main screen on the secondary screen and to display the same in-vehicle applications between the secondary screens; by storing user data in the user space, the privacy and security of user data are improved.
[0067] The following describes an embodiment of the device of the present application, which can be used to execute the display method of the vehicle-mounted application in the above embodiment of the present application. For details not disclosed in the embodiment of the device of the present application, please refer to the embodiment of the display method of the vehicle-mounted application in the above embodiment of the present application.
[0068] Figure 3 FIG. 1 shows a block diagram of a display device for vehicle-mounted applications according to some embodiments of the present application. Figure 3 As shown, the display device of the vehicle-mounted application in an embodiment of the present application is applied to a vehicle, and the vehicle includes a main screen and at least one secondary screen. The display device of the vehicle-mounted application includes: a shadow user creation module 301, an in-vehicle application installation module 302 and an in-vehicle application display module 303, wherein the shadow user creation module 301 can be used to create a corresponding shadow user for each secondary screen and allocate a user space for the shadow user; the in-vehicle application installation module 302 can be used to install the in-vehicle application of the main screen into the user space corresponding to the shadow user when monitoring the startup of the shadow user; the in-vehicle application display module 303 can be used to run the in-vehicle application corresponding to the application icon in the user space corresponding to the target secondary screen when the application icon in the desktop of the target secondary screen is triggered, and output the in-vehicle application corresponding to the application icon to the target secondary screen for display.
[0069] In some embodiments, based on the aforementioned solution, the shadow user creation module 301 can also be used to create multiple shadow users based on the Android user management framework; and bind the secondary screen to the shadow user one-to-one.
[0070] In some embodiments, based on the aforementioned solution, the shadow user creation module 301 can also be used to call the createProfileForUser interface of the Android user management framework to create multiple users; and set the user type to a shadow user.
[0071] In some embodiments, based on the aforementioned scheme, the in-vehicle application installation module 302 can also be used to obtain an application list based on the in-vehicle applications that support multiple openings in the in-vehicle applications on the main screen; when a shadow user is detected to be started, the in-vehicle applications in the application list are installed into the user space corresponding to the shadow user.
[0072] In some embodiments, based on the aforementioned solution, the in-vehicle application installation module 302 can also be used to call the startUserInBackgroundWithListener interface of the Android user management framework to start each shadow user and monitor the startup status of each shadow user.
[0073] In some embodiments, based on the aforementioned solution, the in-vehicle application installation module 302 can also be used to call the installExistingPackage interface of the Android user management framework to install the in-vehicle applications in the application list into the user space corresponding to the shadow user.
[0074] In some embodiments, based on the aforementioned solution, the in-vehicle application display module 303 may also be used to store user data of the target secondary screen into a corresponding user space.
[0075] The embodiments of the present application can display the same in-vehicle application or different in-vehicle applications on different screens without modifying the code or package name of the in-vehicle application. It is completely transparent to third-party applications and does not require developer cooperation. It can be implemented on the vehicle side without the need for data synchronization between the cloud and the vehicle side, thereby reducing development costs, consuming less resources, and improving compatibility.
[0076] Based on the same inventive concept, the embodiment of the present application further provides a vehicle, referring to Figure 4 , shows a schematic structural diagram of a vehicle in an embodiment of the present application, wherein the vehicle includes one or more memories 404, one or more processors 402, and at least one computer program (computer program instruction) stored in the memory 404 and executable on the processor 402, and the processor 402 implements the method described above when executing the computer program.
[0077] Among them, Figure 4In the embodiment of the present invention, a bus architecture (represented by bus 400) is shown. Bus 400 may include any number of interconnected buses and bridges, and bus 400 links together various circuits including one or more processors represented by processor 402 and memory represented by memory 404. Bus 400 may also link together various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. Bus interface 405 provides an interface between bus 400 and receiver 401 and transmitter 403. Receiver 401 and transmitter 403 may be the same component, namely a transceiver, which provides a unit for communicating with various other devices over a transmission medium. Processor 402 is responsible for managing bus 400 and general processing, while memory 404 may be used to store data used by processor 402 when performing operations.
[0078] Based on the same inventive concept, an embodiment of the present application provides a computer-readable storage medium, in which computer program instructions are stored. When the computer program instructions are executed by a processor, the processor is prompted to implement the steps of the method as described above.
[0079] Based on the same inventive concept, an embodiment of the present application provides a computer program product, including a computer program. When the computer program product is executed by a processor, it prompts the processor to implement the steps of the method described above.
[0080] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored as one or more instructions or codes on or transmitted via a computer-readable medium. Other examples and implementations are within the scope and spirit of this application and the appended claims. For example, due to the nature of software, the functions described above may be implemented using software executed by a processor, hardware, firmware, hardwiring, or a combination of any of these. Furthermore, the functional units may be integrated into a single processing unit, each unit may exist physically separately, or two or more units may be integrated into a single unit.
[0081] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only exemplary. For example, the division of the units can be a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.
[0082] The units described as separate components may or may not be physically separate, and the components of the control device may or may not be physical units, that is, they may be located in one place or distributed across multiple units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.
[0083] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, a server or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, magnetic disk or optical disk, etc. Various media that can store computer program instructions.
[0084] The foregoing is merely an embodiment of the present application and is not intended to limit the present application. Various modifications and variations are possible for those skilled in the art. Any modifications, equivalent substitutions, or improvements made within the spirit and principles of the present application shall be included within the scope of the claims of the present application.
Claims
1. A display method for an in-vehicle application, characterized in that: Applied to a vehicle, the vehicle includes a main screen and at least one secondary screen, and the method includes: Create a corresponding shadow user for each secondary screen and allocate a user space for the shadow user; When the shadow user is detected to be started, the in-vehicle application of the main screen is installed into the user space corresponding to the shadow user; When the application icon in the desktop of the target secondary screen is triggered, the in-vehicle application corresponding to the application icon is run in the user space corresponding to the target secondary screen, and the in-vehicle application corresponding to the application icon is output to the target secondary screen for display.
2. The display method for in-vehicle applications according to claim 1, characterized in that: The step of creating a corresponding shadow user for each secondary screen includes: Creating a plurality of shadow users based on the Android user management framework; Bind the secondary screen to the shadow user in a one-to-one correspondence.
3. The display method for in-vehicle applications according to claim 2, characterized in that: The step of creating multiple shadow users based on the Android user management framework includes: Call the createProfileForUser interface of the Android user management framework to create multiple users; Set the user type to a shadow user.
4. The display method for in-vehicle applications according to claim 1, characterized in that: The step of installing the in-vehicle application on the main screen into the user space corresponding to the shadow user upon detecting that the shadow user has started the application comprises: Obtain an application list based on the in-vehicle applications that support multiple openings in the in-vehicle applications on the main screen; When the shadow user is detected to be started, the in-vehicle application in the application list is installed into the user space corresponding to the shadow user.
5. The display method for in-vehicle applications according to claim 4, characterized in that: Also includes: Call the startUserInBackgroundWithListener interface of the Android user management framework to start each shadow user and monitor the startup status of each shadow user.
6. The display method for in-vehicle applications according to claim 4, characterized in that: The installing the in-vehicle application in the application list into the user space corresponding to the shadow user includes: Call the installExistingPackage interface of the Android user management framework to install the in-vehicle applications in the application list into the user space corresponding to the shadow user.
7. The display method for an in-vehicle application according to any one of claims 1 to 6, characterized in that: Also includes: The user data of the target secondary screen is stored in the corresponding user space.
8. A display device for vehicle-mounted applications, characterized in that: Applied to a vehicle, the vehicle includes a main screen and at least one secondary screen, and the device includes: A shadow user creation module, configured to create a corresponding shadow user for each secondary screen and allocate a user space for the shadow user; An in-vehicle application installation module, configured to install the in-vehicle application on the main screen into the user space corresponding to the shadow user when monitoring the shadow user's startup; The in-vehicle application display module is used to run the in-vehicle application corresponding to the application icon in the user space corresponding to the target secondary screen when the application icon in the desktop of the target secondary screen is triggered, and output the in-vehicle application corresponding to the application icon to the target secondary screen for display.
9. A vehicle comprising a processor and a memory, characterized in that: The memory stores computer program instructions that can be executed by the processor, and when the processor executes the computer program instructions, the steps of the method according to any one of claims 1 to 7 are implemented.
10. A computer-readable storage medium, characterized in that The computer-readable storage medium stores computer program instructions, which, when executed by a processor, prompt the processor to implement the steps of the method according to any one of claims 1 to 7.