Application deployment method, apparatus, and vehicle

Abstract

An application deployment method, an apparatus, and a vehicle. The method comprises: in response to a first input for a first application displayed on a first display screen of a vehicle, acquiring a first instruction, wherein the first instruction indicates deployment of the first application on at least one display screen in the vehicle other than the first display screen; and deploying the first application on the at least one display screen on the basis of the first instruction. The present solution can be applied to the technical field of computers and / or the field of intelligent vehicles such as new energy vehicles and electric vehicles. For an application that has been deployed on one or more display screens in a vehicle cockpit, a deployment condition of the application can be flexibly adjusted, for example, the application can be deployed on another display screen on which the application has not been deployed, thereby satisfying different application usage requirements in the cockpit within different time periods, and thus improving user experience.

Description

Application Deployment Method, Device and Vehicle Technical Field

[0001] This application relates to the field of computer technology, and more specifically, to an application deployment method, device and vehicle. Background Art

[0002] With the improvement of the intelligent and connected level of vehicles, the vehicle cockpit is gradually developing towards an intelligent cockpit with human-computer interaction as the core and multi-screen linkage. At different time periods, the user's usage requirements for the applications deployed on the display screen in the cockpit may be different. In order to meet the different application usage requirements at different time periods in the cockpit, a convenient and fast application deployment solution is urgently needed to be developed.

[0003] Summary of the Invention

[0004] This application provides an application deployment method, device and vehicle, which can flexibly adjust the deployment of applications in one or more display screens in the cockpit, and helps to improve the user experience.

[0005] In a first aspect, an application deployment method is provided. This method can be executed by a vehicle. For example, it can be executed by the computing platform of the vehicle, or it can also be executed by a chip or circuit for the vehicle.

[0006] The method includes: in response to a first input for a first application displayed on a first display screen of the vehicle, obtaining a first instruction, where the first instruction indicates to deploy the first application on at least one display screen other than the first display screen in the vehicle; and according to the first instruction, deploying the first application on at least one display screen.

[0007] In some implementations, the first instruction is generated according to the first input.

[0008] In the above technical solution, for an application that has been deployed in one or more display screens in the vehicle cockpit, the deployment of the application can be flexibly adjusted. For example, the application can be deployed to other display screens where the application has not been deployed, which helps to meet different application usage requirements at different time periods in the cockpit, thereby improving the user experience.

[0009] In combination with the first aspect, in certain implementations of the first aspect, according to the first instruction, deploying the first application on at least one display screen includes: according to the first instruction, controlling a prompting device to prompt a first message, where the first message is used to prompt the user to select a display screen for deploying the first application; and in response to an operation where the user selects at least one display screen, deploying the first application on at least one display screen.

[0010] In the above technical solution, deploying the first application to the display screen selected by the user can realize personalized customization of application deployment, meet the user's personalized needs, and improve the user's interactive experience during vehicle use.

[0011] In conjunction with the first aspect, in some implementations of the first aspect, at least one display screen includes a second display screen associated with a first area of ​​the vehicle, and deploying a first application on the at least one display screen according to a first instruction includes: when a user is present in the first area, deploying the first application on the second display screen according to the first instruction.

[0012] The second display screen is the display screen in which the first application has not been deployed before the first instruction is received.

[0013] In the above technical solution, when a redeployment instruction (such as a first instruction) for the first application is detected, the first application can be automatically deployed to the display screen corresponding to the area of ​​the detected user. This eliminates the need for the user to manually select the display screen where the first application needs to be deployed, thus simplifying the user's operation steps and improving the vehicle's intelligence level.

[0014] In conjunction with the first aspect, in some implementations of the first aspect, the type of the first application is a first type or a second type, where the first type indicates that the application needs to be data isolated, and the second type indicates that the application does not need to be data isolated; deploying the first application on at least one display screen according to the first instruction includes: deploying the first application on at least one display screen according to the first instruction and the type of the first application.

[0015] In conjunction with the first aspect, in some implementations of the first aspect, deploying the first application on at least one display screen according to the first instruction and the type of the first application includes: when the type of the first application is a first type, adding a first icon of the first application to each of the at least one display screen and loading application data of the first application associated with each display screen; when the type of the first application is a second type, adding a second icon of the first application to each of the at least one display screen; wherein the first icon and the second icon are the entry points for the user to use the first application.

[0016] In the above technical solution, different deployment methods are adopted for different types of applications so that the applications can run normally when deployed to other displays.

[0017] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: in response to a second input to the first application, obtaining a second instruction indicating a change in the type of the first application; and changing the first application from its original type to a target type according to the second instruction; wherein the original type is a first type and the target type is a second type; or, the original type is a second type and the target type is a first type.

[0018] In the above technical solution, when the application supports a change in type, the application type can be changed in response to the user's operation, which helps to further improve the flexibility of application deployment.

[0019] In conjunction with the first aspect, in some implementations of the first aspect, changing the first application from its original type to the target type according to the second instruction includes: uninstalling the first application of the original type and deploying the first application of the target type according to the second instruction.

[0020] In conjunction with the first aspect, in some implementations of the first aspect, deploying the first application on at least one display screen according to the first instruction includes: when the first user account logs into the vehicle's infotainment system through the first display screen, deploying the first application on at least one display screen according to the first instruction; wherein the first user account is the vehicle owner's account, or the first user account is an account authorized by the vehicle owner.

[0021] In the above technical solution, when the account used to log in to the vehicle system is the vehicle owner's account or an account authorized by the vehicle owner, the deployment strategy of the installed applications can be adjusted, which helps to protect the privacy and security of the vehicle.

[0022] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: unloading the first application on the first display screen according to the first instruction.

[0023] In the above technical solution, while deploying the first application to at least one display screen other than the first display screen according to the first instruction, the first application on the first display screen can also be uninstalled. When the user does not want to keep the first application on the first display screen, no additional uninstallation operation is required, which helps to further improve the flexibility of application deployment.

[0024] In conjunction with the first aspect, in some implementations of the first aspect, the first application is an application other than a security-critical application.

[0025] In the above technical solution, no interface is provided to change or adjust the deployment location for safety-critical applications, which helps to ensure vehicle safety by preventing changes to the type and / or deployment location of safety-critical applications.

[0026] In a second aspect, an application deployment apparatus is provided, the apparatus including an acquisition unit and a processing unit, wherein the acquisition unit is configured to: acquire a first instruction in response to a first input to a first application displayed on a first display screen of a vehicle, the first instruction instructing the first application to be deployed on at least one display screen in the vehicle other than the first display screen; and the processing unit is configured to: deploy the first application on at least one display screen according to the first instruction.

[0027] In conjunction with the second aspect, in some implementations of the second aspect, the processing unit is further configured to: control the prompting device to prompt first information according to the first instruction, the first information being used to prompt the selection of a second display screen for deploying the first application, at least one display screen including the second display screen; the processing unit is configured to: deploy the first application on the second display screen according to the first instruction.

[0028] In conjunction with the second aspect, in some implementations of the second aspect, at least one display screen includes a second display screen associated with a first area of ​​the vehicle, and the processing unit is configured to: when a user is present in the first area, deploy a first application on the second display screen according to a first instruction.

[0029] In conjunction with the second aspect, in some implementations of the second aspect, the type of the first application is either a first type or a second type, where the first type indicates that the application needs to be isolated from data, and the second type indicates that the application does not need to be isolated from data; the processing unit is used to: deploy the first application on at least one display screen according to the first instruction and the type of the first application.

[0030] In conjunction with the second aspect, in some implementations of the second aspect, the processing unit is configured to: when the type of the first application is a first type, add a first icon of the first application to each of the at least one display screen, and load application data of the first application associated with each display screen; when the type of the first application is a second type, add a second icon of the first application to each of the at least one display screen; wherein the first icon and the second icon are the entry points for the user to use the first application.

[0031] In conjunction with the second aspect, in some implementations of the second aspect, the acquisition unit is further configured to: acquire a second instruction in response to a second input to the first application, the second instruction indicating a change in the type of the first application; the processing unit is further configured to: change the first application from its original type to a target type according to the second instruction; wherein the original type is a first type and the target type is a second type; or, the original type is a second type and the target type is a first type.

[0032] In conjunction with the second aspect, in some implementations of the second aspect, the processing unit is used to: uninstall the first application of the original type and deploy the first application of the target type according to the second instruction.

[0033] In conjunction with the second aspect, in some implementations of the second aspect, the processing unit is configured to: when a first user account logs into the vehicle's infotainment system via a first display screen, deploy a first application on at least one display screen according to a first instruction; wherein the first user account is the vehicle owner's account, or the first user account is an account authorized by the vehicle owner.

[0034] In conjunction with the second aspect, in some implementations of the second aspect, the processing unit is further configured to: unload the first application on the first display screen according to the first instruction.

[0035] In conjunction with the second aspect, in some implementations of the second aspect, the first application is an application other than a security-critical application.

[0036] Thirdly, a control device is provided, comprising: a processor for executing a computer program stored in the memory, such that the device performs the method in any possible implementation of the first aspect described above.

[0037] In conjunction with the third aspect, in some implementations of the third aspect, the control device also includes a memory.

[0038] Fourthly, a computer program product is provided, comprising: computer program code, which, when executed on a computer or processor, causes the computer or processor to perform the method in any possible implementation of the first aspect.

[0039] It should be noted that the above computer program code can be stored in whole or in part on a storage medium, which can be packaged together with the processor or packaged separately from the processor.

[0040] Fifthly, a computer-readable storage medium is provided, the computer-readable medium storing instructions that, when executed by a processor, cause the processor to implement the method in any possible implementation of the first aspect.

[0041] In a sixth aspect, a chip is provided that includes circuitry for performing the method in any of the possible implementations of the first aspect described above.

[0042] In a seventh aspect, a vehicle is provided that includes means as in any possible implementation of the second to third aspects, or the vehicle includes computer-readable storage as in any possible implementation of the fifth aspect, or the vehicle includes a chip as in any possible implementation of the sixth aspect, or the vehicle is loaded with computer program code as in any possible implementation of the fourth aspect.

[0043] In conjunction with the seventh aspect, in some implementations of the seventh aspect, the vehicle is a vehicle in a broad sense, such as a means of transportation (e.g., commercial vehicles, passenger cars, motorcycles, flying cars, trains, etc.), industrial vehicles (e.g., forklifts, trailers, tractors, etc.), engineering vehicles (e.g., excavators, bulldozers, cranes, etc.), agricultural equipment (e.g., lawnmowers, harvesters, etc.), amusement equipment, toy vehicles, etc. In practical implementation, the vehicle can also be a road vehicle, a water vehicle, an air vehicle, industrial equipment, agricultural equipment, or other intelligent driving equipment such as entertainment equipment.

[0044] For the beneficial effects not described in detail in aspects two through seven, please refer to the description in aspect one, which will not be repeated here. Attached Figure Description

[0045] Figure 1 is a functional block diagram of the vehicle provided in an embodiment of this application;

[0046] Figure 2 is a schematic diagram of a vehicle cabin scenario provided in an embodiment of this application;

[0047] Figure 3 is a schematic block diagram of the system architecture provided in an embodiment of this application;

[0048] Figure 4 is another schematic block diagram of the system architecture provided in the embodiments of this application;

[0049] Figure 5 is another schematic block diagram of the system architecture provided in the embodiments of this application;

[0050] Figure 6 is a schematic diagram of the data storage architecture provided in an embodiment of this application;

[0051] Figure 7 is a schematic flowchart of the control method provided in an embodiment of this application;

[0052] Figure 8 is a schematic diagram of the graphical user interface (GUI) provided in an embodiment of this application;

[0053] Figure 9 is another schematic diagram of the GUI provided in the embodiments of this application;

[0054] Figure 10 is another schematic diagram of the GUI provided in the embodiments of this application;

[0055] Figure 11 is another schematic diagram of the GUI provided in the embodiments of this application;

[0056] Figure 12 is another schematic diagram of the GUI provided in the embodiments of this application;

[0057] Figure 13 is another schematic diagram of the GUI provided in the embodiments of this application;

[0058] Figure 14 is another schematic diagram of the GUI provided in the embodiments of this application;

[0059] Figure 15 is another schematic diagram of the GUI provided in the embodiments of this application;

[0060] Figure 16 is another schematic diagram of the GUI provided in the embodiments of this application;

[0061] Figure 17 is another schematic flowchart of the application deployment method provided in the embodiments of this application;

[0062] Figure 18 is a schematic block diagram of the device provided in an embodiment of this application;

[0063] Figure 19 is another schematic block diagram of the device provided in the embodiments of this application. Detailed Implementation

[0064] The technical solutions in this application will now be described with reference to the accompanying drawings.

[0065] Figure 1 is a functional block diagram of a vehicle provided in an embodiment of this application. As shown in Figure 1, the vehicle 100 may include a display device 130 and a computing platform 150. The display device 130 in the cabin is mainly divided into two categories: the first is an in-vehicle display screen; the second is a projection display screen, such as a head-up display (HUD). An in-vehicle display screen is a physical display screen and an important component of the in-vehicle infotainment system. Multiple displays can be installed in the cabin, such as a digital instrument cluster display screen, a central control screen, a display screen in front of the front passenger (also known as the front row passenger), a display screen in front of the left rear passenger, and a display screen in front of the right rear passenger; even the car window can be used as a display screen. A head-up display, also known as a head-up display system, is mainly used to display driving information such as speed and navigation on a display device (e.g., the windshield) in front of the driver. This reduces the driver's eye movement time, avoids pupil changes caused by eye movement, and improves driving safety and comfort. HUDs include, for example, combiner-HUD (C-HUD) systems, windshield-HUD (W-HUD) systems, and augmented reality HUD (AR-HUD) systems.

[0066] Some or all of the functions of vehicle 100 can be controlled by computing platform 150. Computing platform 150 may include processors 151 to 15n. A processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction read and execute capabilities, such as a central processing unit (CPU), microprocessor, graphics processing unit (GPU) (which can be understood as a type of microprocessor), or digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationships of hardware circuits. These logical relationships are fixed or reconfigurable. For example, the processor may be a hardware circuit implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as a field-programmable gate array (FPGA). In reconfigurable hardware circuits, the process of the processor loading a configuration document and configuring the hardware circuit can be understood as the process of the processor loading instructions to implement related functions. Furthermore, the processor can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), tensor processing unit (TPU), deep learning processing unit (DPU), etc. In addition, the computing platform 150 may also include a memory for storing instructions. Some or all of the processors 151 to 15n can call the instructions in the memory to implement the corresponding functions.

[0067] Optionally, the structure of the vehicle 100 described above is merely illustrative. In actual applications, various components of the vehicle 100 may be added or removed as needed.

[0068] Figure 2 is a schematic diagram of a vehicle cockpit scenario provided in an embodiment of this application. The smart cockpit is equipped with one or more in-vehicle displays (or in-vehicle screens), including but not limited to display screen 201 (or central control screen), display screen 202 (or passenger entertainment screen), display screen 203 (or driver's headrest rear screen), display screen 204 (or passenger headrest rear screen), display screen 205 (or second-row entertainment screen) mounted on the cockpit ceiling, and an instrument panel. Further, displays 201 to 205 can display a graphical user interface (GUI), which may include icons of one or more applications and / or one or more cards. Exemplarily, the display device 130 shown in Figure 1 can be one or more of displays 201 to 205. In some possible implementations, display screen 201 can also be a long, continuous screen extending to the passenger area. Additionally, display screen 205 can also be a projection screen associated with a projector, which can be associated with a desktop launcher to manage applications projected onto the projection screen.

[0069] As shown in Figure 2, one or more cameras can also be installed in the cockpit to capture images inside or outside the cockpit. These could include cameras from a driver monitor system (DMS), a cabin monitor system (CMS), or a dashcam. The cameras used to capture images inside and outside the cockpit can be the same camera or different cameras. In addition, one or more pressure sensors and acoustic sensors are installed in the cockpit to monitor the presence and location of users.

[0070] In this application, based on the function of the display screen relative to the driver, cockpit displays can be divided into safety-critical screens and non-safety-critical screens. Safety-critical screens refer to screens or display devices that are likely to affect the driver and cause driver distraction, such as instrument panel screens and central control screens. Non-safety-critical screens indicate screens that are less likely to cause driver distraction, screens that are not easily observed by the driver, or screens located far from the driver, such as screens near rear passengers and rear entertainment screens.

[0071] It should be understood that the following embodiments are illustrated using a 5-seat vehicle as shown in Figure 2 as an example, and the embodiments of this application are not limited to this. For example, for a 7-seat sport / suburban utility vehicle (SUV), the cabin may include a central control screen, a passenger entertainment screen, a screen behind the driver's headrest, a screen behind the passenger's headrest, entertainment screens in the left-hand area of ​​the third row, and entertainment screens in the right-hand area of ​​the third row. As another example, for a bus, the cabin may include front and rear entertainment screens; or, the cabin may include a display screen in the driver's area and an entertainment screen in the passenger area. Furthermore, the following embodiments are illustrated using a left-hand drive vehicle (i.e., the driver is located on the left side of the vehicle), but in actual implementation, the vehicle may also be a right-hand drive vehicle (i.e., the driver is located on the right side of the vehicle).

[0072] As mentioned above, users' needs for applications deployed on the cockpit displays may vary at different times. For example, generally, rear-seat users do not need to use navigation applications, so navigation applications are not deployed on the second-row displays. However, in some scenarios, second-row users may need to use navigation applications, requiring rapid deployment of these applications to the second-row displays. In other words, a convenient and quick application deployment solution urgently needs to be developed to meet the different application usage needs within the cockpit at different times.

[0073] In view of this, embodiments of this application provide an application deployment method, apparatus, and vehicle, which help improve the convenience of application deployment and thus enhance the user experience.

[0074] To facilitate understanding of the technical solution of this application, the application deployment scheme provided by the embodiments of this application will be described in detail below with reference to Figures 3 to 19.

[0075] Figure 3 shows a schematic block diagram of the control system provided in an embodiment of this application. As shown in Figure 3, the control system includes multiple display devices, such as display device 1, display device 2, and display device n (n is a positive integer). These multiple display devices are associated with a single user space. That is, the multiple display devices share a single set of system services. Regardless of which display device the system account logs into the vehicle system through, the functions the user wants to achieve through this system account are supported by the same system service. For example, the system service may include basic services such as a desktop launcher, voice service, and data management. The desktop launcher has functions such as launching applications, managing applications (e.g., installing and / or uninstalling applications), and displaying desktop widgets; the voice service provides voice recognition capabilities; and the data management provides functions for managing multimedia data such as photos, videos, and music (e.g., reading and writing multimedia data in the storage area). It is understood that the storage load required by the system services for each user space, and the computational load (e.g., CPU load) required to start and stop the user space, are both high. If a user space is set up for each display device, the memory load and computational load required by the vehicle system will increase exponentially with the number of display devices. Furthermore, when switching system accounts on each display device, it is necessary to stop a system service (the user space corresponding to the logged-out system account) and start a new system service (the user space corresponding to the newly logged-in system account). Such large-scale starting and stopping of system services can cause system freezes, resulting in choppy displays or long waiting times for newly logged-in system accounts before they can use applications. Therefore, setting up a single user space for multiple display devices helps save on storage and computing costs. When the system account logged into the vehicle system changes, there is no need to stop and start system services, which helps reduce system lag, improves system smoothness, and ultimately enhances the user experience.

[0076] It should be noted that the user space involved in this application can be understood as the application's operating environment. The applications deployed on any two of display devices 1 to n can be the same or different. Furthermore, display devices 1, 2, and n in Figure 3 can be included in display device 130 shown in Figure 1. The placement of display devices 1, 2, and n in the cockpit can be referenced to the placement of displays 201 to 205 shown in Figure 2, and will not be elaborated further here.

[0077] It should also be noted that the applications or application programs mentioned below in this application refer to software running in the vehicle infotainment system. The icon corresponding to an application or application (or application icon, or application icon) refers to the entry point for using or accessing the application. Application login or logout refers to logging in or out of the application account within the application. Application exit refers to closing the application or ending the application-related process. Deploying an application on a specific screen refers to deploying the application's access point on a specific screen; for example, this could be deploying the application or application icon on a specific screen, or deploying the main application or a clone application of the application on a specific screen.

[0078] Figure 4 shows another schematic block diagram of the control system provided in an embodiment of this application. As shown in Figure 4, the system includes a user management unit 410, an application management unit 420, a user center service unit 430, and a public data service unit 440. The functional characteristics of each unit shown in Figure 4 can be implemented by one or more processors in the computing platform 150 shown in Figure 1. More specifically, the functions of each unit in the system are as described in items (i) to (iv) below:

[0079] (I) The user management unit 410 provides users with interfaces for logging into the vehicle infotainment system and setting system account permissions. More specifically, the user management unit 410 includes a login management unit 411 and a permission management unit 412. The login management unit 411 is used to obtain the system account requesting to log into or log out of the vehicle infotainment system. In some implementations, the system account may include at least three types: vehicle owner system account, authorized system account, and guest system account. The vehicle owner system account is the account of the legal owner of the vehicle; the authorized system account is the account authorized by the legal owner of the vehicle; and the guest system account is the account not authorized by the legal owner of the vehicle. The permission management unit 412 is used to obtain the permissions of the system account. The permissions of the system account may be user-set or default to the vehicle infotainment system. In some implementations, the permissions of the system account may include at least one of the following: whether it has permission to install applications, whether it has permission to uninstall applications, which applications are allowed to be uninstalled and / or installed, which applications are prohibited from being uninstalled and / or installed, whether it can access the data storage area, and which applications can access the data storage area. For example, system account 1 has the permission to install applications, including all applications in the app store, and all applications can access the data storage area; system account 2 cannot uninstall privacy-critical applications, and all applications cannot access the data storage area. For instance, the legitimate owner of the vehicle can set permissions for authorized system accounts and guest system accounts. For example, when the owner's system account logs into the vehicle's infotainment system, the user can set permissions for authorized system accounts and guest system accounts through the vehicle's human-machine interface (HMI). The permission management unit 412 can obtain the permissions of the system account entered by the user through the HMI.

[0080] (II) The application management unit 420 provides users with interfaces for logging into applications and accessing data storage areas. More specifically, the application management unit 420 includes an application login management unit 421, a user center management unit 422, and an access management unit 423. The application login management unit 421 manages and controls application logins. It can obtain the application account used to log into a specific application and control that account to log into that application. The user center management unit 422 obtains the system account currently logged into the vehicle system and sends this information to the application login management unit 421. The application login management unit 421 can then use the application account associated with the currently logged-in system account to log into one or more applications. The user center management unit 422 can also obtain the system account logged out of the vehicle system and send this information to the application login management unit 421. The application login management unit 421 can then control the application account associated with the logged-out system account to log out of one or more applications. The access management unit 423 manages the permissions for applications to read data from the data storage area and store data in the data storage area. Access management unit 423 can determine whether to send a data read request or data storage request from the application to public data service unit 440 based on the application's permissions. In one example, if an application has permission to access the data storage area, access management unit 423 sends a data read / storage request to public data service unit 440 to request to read the data required by the application or write the data requested by the application to the data storage area. In another example, if an application does not have permission to access the data storage area, access management unit 423 ignores the application's data read / storage request, that is, it does not send a data read / storage request to public data service unit 440.

[0081] (III) The user center service unit 430 is used for system account management and data access management. More specifically, the user center service unit 430 includes an account management unit 431 and a data management unit 432. The account management unit 431 controls a system account to log in to the vehicle infotainment system based on a request obtained from the user management unit 410; alternatively, it controls a system account to log out of the vehicle infotainment system based on a request obtained from the user management unit 410. Furthermore, after controlling a system account to log in or out of the vehicle infotainment system, the user center service unit 430 can send a login or logout notification to the application management unit 420. The data management unit 432 can obtain the system account's permission information from the user management unit 410, determine the applications that can access the data storage area under that system account based on the permission information, and then send the information about the applications that can access the data storage area under that system account to the public data service unit 440.

[0082] (iv) The public data service unit 440 is used to provide data storage and retrieval services for applications. More specifically, the public data service unit 440 includes a permission management module 441, a media library 442, and a file library 443. The permission management module 441 is used to create access path units for system accounts. Subsequently, one or more applications used under this system account need to read and write data in the data storage area through this access path unit. Specifically, the vehicle system can be associated with one or more system accounts. Access path units are set for system accounts that have permission to access the data storage area. At least one application running under the system account with the set access path unit needs to store data in or read data from the data storage area through the access path unit associated with that system account. A system account cannot read or write data in the data storage area through the access path unit of another system account. For example, if application 1 under system account 1 stores image 1 in the data storage area through access path unit 1 associated with system account 1, while application 1 under system account 2 does not store image 1 in the data storage area through access path unit 2 associated with system account 2, then system account 2 cannot read image 1 from the data storage area. Furthermore, for certain applications (such as those with low privacy or security requirements), data reading and writing can be performed without going through an access path unit. In this case, if such an application stores data A under one system account, data A can also be read under another system account.

[0083] Media library 442 and file library 443 are used to store data. When media library 442 or file library 443 receives a data read / write request (i.e., a data read or write request) from access management unit 423, request permission management module 441 authenticates the data read / write request to determine whether the request has permission to access the requested data. The data read / write request can be an application's access request to a data storage area. If the data read / write request authentication is successful, public data service unit 440 sends the requested data to application management unit 420; or, if the data read / write request authentication is successful, public data service unit 440 stores the requested data in the corresponding area of ​​media library 442 or file library 443; or, if the data read / write request authentication fails, public data service unit 440 sends a data access failure notification to application management unit 420.

[0084] It should be understood that the architecture shown in Figure 4 is merely illustrative. In actual implementation, the system shown in Figure 4 may include more or fewer units. For example, the system shown in Figure 4 may include multiple login management units 411, each corresponding to one of the multiple display devices in the vehicle; or, for another example, the system shown in Figure 4 may also include multiple application management units 420, each application management unit 420 being a login interface and / or data access interface corresponding to an application, and the multiple applications corresponding to the multiple application management units 420 may be deployed on one or more display devices in the vehicle. More specifically, when a user logs into the vehicle system using system account 1 through a display device (such as display device a), the login management unit 411 corresponding to display device a may send a login request to the user center service unit 430, which instructs system account 1 to request login into the vehicle system through display device a. Further, the user center service unit 430, based on the login request, controls system account 1 to log into the vehicle system through display device a. Furthermore, the user center service unit 430 sends a login notification for system account 1 to at least one application management unit. This notification indicates that system account 1 has logged into the vehicle infotainment system via display device a. The at least one application management unit controls the application account associated with system account 1 to log into one or more applications deployed on display device a that are associated with system account 1. The aforementioned at least one application management unit may include application management units 420 corresponding to all applications installed in the vehicle infotainment system, or it may include application management units 420 corresponding only to applications deployed on display device a.

[0085] It is understandable that Figure 4 shows a system architecture within a single user space. In actual implementation, multiple display devices in a vehicle can be associated with multiple user spaces. Specifically, as shown in Figure 5, display device 1, display device 2, and display device n (where n is a positive integer) can be associated with user spaces 1 through n', where n' is an integer greater than or equal to 2. In actual implementation, within the same time period, the runtime environment required by the applications deployed on display devices 1 through n is provided by a single user space. In different time periods, the runtime environment required by the applications deployed on display devices 1 through n can be provided by different user spaces. For example, in time period 1, the runtime environment required by the applications deployed on display devices 1 through n is provided by user space 1, while in time period 2, the runtime environment required by the applications deployed on display devices 1 through n is provided by user space n'. In this scenario, the end time of time period 1 is earlier than the start time of time period 2, or the end time of time period 1 coincides with the start time of time period 2; or the end time of time period 2 is earlier than the start time of time period 1, or the end time of time period 2 coincides with the start time of time period 1. In some implementations, within the same time period, the runtime environment required by applications deployed on display devices 1 to n can be provided by at least two user spaces. For example, the runtime environment required by applications deployed on display device 1 is provided by user space 1, and the runtime environment required by applications deployed on display devices 2 to n is provided by user space n'.

[0086] In actual implementation, in order to ensure the privacy and security of different users in the same user space, the data read and write architecture of this application embodiment is designed, which will be described in detail below with reference to Figure 6.

[0087] Figure 6 illustrates a schematic diagram of the data storage architecture provided in an embodiment of this application. As shown in Figure 6, the database includes an access path management unit and a data sandbox. The database may include the aforementioned media library, file library, etc. The data sandbox is used to store data. The access path management unit may include multiple access path units, each associated with a system account. For example, if system accounts a through N are all associated with the same user space (e.g., system accounts a through N are all registered in this user space, or have all logged into the vehicle system under this user space), the access path management unit may include access path units associated with system accounts a through N, such as system account a access path unit, system account N access path unit, etc. More specifically, system account a can log in to multiple applications, including applications 1 through m. Applications 1 through m need to read and write data through the access path management unit. For example, at least one of applications 1 through m stores image 11, image 21, image 31, and video 111 in the data sandbox through the system account a access path unit. More specifically, when at least one of applications 1 to m stores data, a reference associated with that data is created (e.g., reference to image 11, image 21, image 31, or video 111), and this reference is stored in the access path unit of system account a. This reference includes fields associated with system account a. When an application reads the aforementioned data, it needs to read it through the reference associated with that data. For example, when application m requests to read video 111 from the data sandbox, it needs to read video 111 through the video 111 reference stored in the access path unit of system account a.

[0088] In some implementations, applications 1 to m are privacy-critical applications. Among the multiple applications logged in under system account a, in addition to applications 1 to m, there may be at least one rights-sharing application. When at least one rights-sharing application reads or writes data, it can do so without going through the access path management unit.

[0089] For details on how applications 1' to m' under system account N read data from the data sandbox and store data in the data sandbox, please refer to the relevant descriptions of applications 1 to m reading and writing data. These details will not be repeated here.

[0090] It should be noted that applications under system account a, other than applications 1 to m, cannot read data stored through the access path management unit (such as images 11, 21, 31, and video 111). Furthermore, applications running under one system account cannot read data stored through the access path management unit by applications running under another system account. For example, an application running under system account a cannot read images 12, 22, 32, etc., stored through the access path management unit by an application running under system account N.

[0091] In actual implementation, the data reference stored in the aforementioned access path unit can be in the form of a field, which may include the system account name. For example, when application m' running under system account N stores data a in the data storage area, the "System Account N" field is added to the data storage path (or data reference). A more specific data storage path could be: "System Account N - Application m' - Data a". When application 1' running under system account N reads data a from the data storage area, the "System Account N" field is added to the data read path. A more specific data read path could be: "System Account N - Application 1' - Data a". It should be noted that the field representing the access path unit corresponding to a system account can be managed by the public data service unit 440. This field is not perceived by the application. When the public data service unit 440 receives a data access request from an application, it determines whether to respond to the application's data access request based on which system account the application is running under and whether the application needs to read or write data in the data storage area via the access path unit. Therefore, applications running under system account N that can read and write data to the data storage area without accessing the path unit, as well as applications running under other system accounts, cannot read the data stored by applications 1' to m' running under system account N.

[0092] In some implementations, for applications that can read and write data to the data storage area without going through an access path unit (such as rights-sharing applications), a public storage area can be set up. This public storage area is used for the aforementioned applications to read and write data. It should be noted that when a system account is authorized to access the public storage area, the data in that public storage area can be read by any application running under that system account. It should be understood that the aforementioned data storage area includes this public storage area.

[0093] It should also be noted that the privacy-critical applications and benefit-sharing applications involved in this application are categorized based on the application's data privacy requirements. Privacy-critical applications can also be referred to as clone applications, and benefit-sharing applications can also be referred to as instance applications. More specifically, privacy-critical applications refer to applications with data isolation requirements; for example, users do not want data associated with such applications to be accessed or obtained by other users. Privacy-critical applications can include social applications (such as instant messaging applications, social media platforms, etc.), or e-commerce applications, map navigation applications, etc. Benefit-sharing applications involved in this application refer to applications that do not require data isolation; for example, data associated with such applications can be accessed or obtained by other users, such as weather applications; or benefit-sharing applications can also be applications that require data sharing; for example, for one application, multiple system accounts can share the benefits of the same application account, such as audio and video applications. For example, the data associated with the aforementioned applications can include at least one of the following: data stored by the application, data read by the application, or the application's search history, browsing history, purchase history, etc. Furthermore, for privacy-critical applications, when the same application is deployed on multiple displays, the applications on different displays need to log in with different application accounts within the same time period. For benefit-sharing applications, when the same application is deployed on multiple displays, the applications deployed on multiple displays can log in with the same application account within the same time period. In other words, the benefits of an application account can be shared by applications on multiple displays within the same time period.

[0094] In practice, whether an application is classified as a privacy-critical application or a rights-sharing application can be set by the system default. For example, social applications can be set as privacy-critical applications by default, while audio and video applications can be set as rights-sharing applications by default. Alternatively, for a single application, users can be provided with both privacy-critical application installation packages and rights-sharing application installation packages, allowing users to choose which type of application to deploy in the vehicle's infotainment system.

[0095] The above, in conjunction with Figures 1 to 6, provides a detailed description of the system architecture provided in the embodiments of this application. The following describes in detail the control method provided in the embodiments of this application.

[0096] Figure 7 shows a schematic flowchart of a control method provided in an embodiment of this application. This method 700 can be executed by the system shown in Figure 4, wherein the user management unit, application management unit group, user center service unit, and public data service unit can be respectively a user management unit 410, at least one application management unit 420, a user center service unit 430, and a public data service unit 440 within a user space. The method may include the following steps:

[0097] S711, User Management Unit obtains user permission information 1.

[0098] In one example, when the main user is logged in, the user management unit retrieves user permission information 1 in response to the user's settings.

[0099] In another example, the user management unit obtains user permission information 1 from a vehicle owner application deployed on an electronic device associated with the vehicle. This vehicle owner application may be an application that provides vehicle control to the vehicle owner, and / or an application that provides services such as providing the vehicle owner with information about the vehicle's status. The association between the electronic device and the vehicle may include: the account used to log in to the electronic device and the vehicle being the same; or, although the accounts used to log in to the electronic device and the vehicle are different, both being accounts belonging to an authorized user of the vehicle; or, the electronic device being authorized by an authorized user of the vehicle, thereby establishing an association between the vehicle and the electronic device.

[0100] For example, the main user can be the aforementioned vehicle owner system account; user permission information 1 can include the permissions of each of the multiple system accounts. These multiple system accounts can include one or more authorized system accounts, and can also include one or more guest system accounts. The specific content of the permissions for each system account can be found in the descriptions in the preceding embodiments, and will not be repeated here.

[0101] In some implementations, applications running under a guest system account do not have permission to access the data storage area under that user space.

[0102] S712, the user management unit sends user permission information 1 to the user center service unit.

[0103] S713, the User Center Service Unit performs user permission processing.

[0104] For example, the user center service unit determines the applications that can access the data storage area under each system account based on user permission information 1, and then obtains user permission information 2. User permission information 2 includes information about at least one application and the association between each application and the system account. The at least one application may include one or more applications that can access the data storage area under one or more system accounts.

[0105] S714, The User Center Service Unit sends user permission information 2 to the Public Data Service Unit.

[0106] Furthermore, the public data service unit manages the data access permissions of applications running under each system account based on user permission information 2. For example, the public data service unit determines, based on user permission information 2, which applications can access the data storage area, and under which system accounts these applications can access the data storage area.

[0107] In some implementations, the public data service unit records the applications that can access the data storage area under each system account. When an application not recorded by the public data service unit requests access to the data storage area, the public data service unit rejects its request.

[0108] In some implementations, at least one application includes a privacy-critical application. In this case, the public data service unit establishes an access path unit for the system account associated with the privacy-critical application. The privacy-critical application running under this system account can subsequently read and write data in the data storage area through this access path unit. For a more detailed implementation of how privacy-critical applications read and write data in the data storage area, please refer to the description in the corresponding part of Figure 6 above, which will not be repeated here.

[0109] S721, the user management unit obtains login instruction 1, which is associated with system account A.

[0110] For example, system account A can be the vehicle owner's system account, or it can be an account authorized by the legal owner of the vehicle. System account A can be any of the aforementioned system accounts a to N, or it can be the aforementioned system account 1 or system account 2.

[0111] Login command 1 is associated with system account A, which can be understood as: Login command 1 requests to log in to the vehicle system using system account A, or Login command 1 requests to log in to the vehicle system using system account A through display device A. For example, display device A can be any one of the aforementioned display devices 1 to n.

[0112] S722, the user management unit sends a login request for system account A to the user center service unit.

[0113] S723, the user center service unit performs login processing for system account A.

[0114] For example, the user center service unit logs into the vehicle system using system account A on display device A.

[0115] S724, Application Management Snap-in Login Application 1.

[0116] For example, the application management unit group responds to the user's operation and controls application account 1 to log in to application 1.

[0117] S725, the Application Management Unit group sends a login notification for Application 1 to the User Center Service Unit.

[0118] For example, the login notification of application 1 instructs application account 1 to log in to application 1 under system account A.

[0119] S726, the User Center Service Unit performs the association processing between Application 1 and System Account A.

[0120] For example, the association process can be understood as binding application 1, system account A and application account 1 together, so that when system account A logs into the vehicle system next time, application account 1 can log into application 1 together.

[0121] In some implementations, if application 1 is a privacy-critical application, the user center service unit will perform the association processing between application 1 and system account A when it receives the login notification from application 1.

[0122] In some other implementations, when the user center service unit receives the login notification of application 1, the control prompt device prompts information 1, which prompts the user to determine whether application 1 needs to be associated with system account A. When it is determined that the user chooses to associate application 1 with system account A, S726 is executed.

[0123] It should be noted that S724 to S726 can be operations performed when logging into application 1 for the first time under system account A; or, S724 to S726 can also be operations performed when logging into application 1 for the first time under system account A using application account 1. For example, before executing S724, application 1 is already associated with system account A, but application 1 is associated with system account A while logging in with application account 2. After executing S724 to S726, the association between application 1 and system account A is updated to: when logging in with system account A, application 1 is logged in using application account 1.

[0124] In some implementations, S727 and S728 are executed after S723. For example, if the association between system account A and the application has already been processed, S727 and S728 are executed after S723.

[0125] S727, the User Center Service Unit sends a login notification for System Account A to the Application Management Unit Group.

[0126] For example, the login notification for system account A instructs system account A to log in to the vehicle system through display device A.

[0127] S728, Application management unit group login system account A associated with application group a.

[0128] In some implementations, application group a may include at least one application deployed on display device A and associated with system account A. For each application, the application is logged in using the application account associated with system account A; the application account used to log in to different applications may be different. It is understood that the association between the application, the application account, and the system account can be determined through steps S724 to S726.

[0129] For example, at least one application includes application 3, and application 3 is a rights-sharing application. That is, when application 3 is deployed on display device A, other display devices in the vehicle can deploy applications 3', 3" and so on. When logging into any one of application 3, application 3', or application 3" using an application account, the remaining two applications are also logged in. In other words, application group a can also include applications such as application 3' and application 3" that are associated with application 3 and deployed on other display devices.

[0130] It should be noted that the applications deployed on different display devices may be different. Therefore, when system account A logs into the vehicle system through different display devices, the applications that log in with system account A may be different.

[0131] In some implementations, S724 to S726 can also be executed after S727 and S728. For example, if application group a in S728 includes application 1, when S728 is executed, application account 2 is controlled to log in to application 1. Further, in response to a user action controlling application account 1 to log out of application 1, S724 to S726 are executed. Thus, the next time system account A is logged in, application account 1 is used to log in to application 1 associated with system account A.

[0132] S731, the user management unit obtains logout instruction 1, and logout instruction 1 requests system account A to log out.

[0133] S732, the user management unit sends a logout request for system account A to the user center service unit.

[0134] S733, the User Center Service Unit performs a logout process for system account A.

[0135] For example, the user center service unit logs out system account A on display device A.

[0136] S734, the User Center Service Unit sends a logout notification for System Account A to the Application Management Unit Group.

[0137] S735, the application management unit logs out at least one application in application group a.

[0138] In some implementations, all applications in application group a are logged out.

[0139] In some implementations, application group a includes at least one safety-critical application. Safety-critical applications refer to applications that affect driving safety, such as navigation applications or intelligent driving applications. Intelligent driving applications are those used to control intelligent driving functions, which may include, but are not limited to, the following functions affecting driving safety: automatic parking assist (APA), automatic valet parking (AVP), adaptive cruise control (ACC), lane cruise control (LCC), navigation cruise assist (NCA), forward collision warning, lane departure warning, lane keeping assist, and rear collision warning. Specifically, NCA refers to the function of controlling the vehicle to travel to its destination according to the navigation route and being able to control the vehicle to perform operations such as passing intersections, changing lanes, and shifting gears based on road information such as traffic lights.

[0140] In one example, when the vehicle is in drive or reverse, if the application management unit receives a logout notification for system account A, the application management unit will control the logout of all applications in application group a except for intelligent driving applications. Furthermore, when the vehicle is in park, the intelligent driving applications will be logged out.

[0141] In another example, when a smart driving application is running, if the application management unit receives a logout notification from system account A, the application management unit will control the logout of all applications in application group a except for the running smart driving application. Furthermore, when the smart driving application exits its running state, the application management unit will also be controlled to log out.

[0142] In some implementations, if application group a includes at least one benefit-sharing application, then when the application management unit receives a logout notification for system account A, it controls the logout of all applications in application group a except for the at least one benefit-sharing application. For example, if the at least one benefit-sharing application includes the aforementioned application 3, application 3', and application 3'", then the application management unit controls the logout of all applications in application group a except for application 3, application 3', and application 3'".

[0143] In some implementations, after controlling at least one application in application group a to log out, it is also possible to control at least one application in application group a to exit.

[0144] In practice, when the same system account logs into the vehicle system through different display devices, the system account can be logged out of the vehicle system before logging in again when the system account logs into the vehicle system through the next display device; or the system account can be kept logged into the vehicle system continuously during the aforementioned process.

[0145] S741, the application management unit group sends a data access request to the public data service unit for application 2 associated with system account B.

[0146] In this context, application 2 associated with system account B can be understood as an application running under system account B. For example, if system account 2 logs into the vehicle system through display device B, then application 2 can be an application deployed on display device B. Exemplarily, display device B can be any one of the aforementioned display devices 1 to n.

[0147] For example, a data access request may include a request to read data in a data storage area and / or a request to store data in a data storage area.

[0148] S742, the public data service unit performs authentication processing.

[0149] For example, the public data service unit determines whether application 2 associated with system account B has permission to access the data storage area. When it is determined that application 2 associated with system account B has permission to access the data storage area, the public data service unit also determines which data in the data storage area application 2 can access.

[0150] In some implementations, multiple system accounts can access application 2 when logging into the vehicle's infotainment system via display device B. However, the permissions of application 2 associated with different system accounts vary. For example, application 2 associated with system accounts B and C both have access to the data storage area, while application 2 associated with system account D does not. Furthermore, application 2 associated with system account B can access the public storage area, while application 2 associated with system account C does not have access to the public storage area.

[0151] S743, upon successful authentication, the public data service unit sends the data read / write results to the application management unit group.

[0152] In one example, if system account B is associated with application 2, which needs to access the data storage area through the access path unit, then the public data service unit stores the data requested by application 2 and / or reads the data requested by application 2 through the access path unit.

[0153] In another example, if application 2 associated with system account B can access the data storage area without going through the access path unit, then the public data service unit stores the data requested by application 2 in the public storage area and / or reads the data requested by application 2 from the public storage area.

[0154] S744, when authentication fails, the Public Data Service Unit sends a data access failure notification to the Application Management Unit Group.

[0155] For example, a data access failure notification is used to notify of a failure to store data in a data storage area, or to notify of a failure to read data from a data storage area.

[0156] It should be noted that when system account A and system account B are different and they log into the vehicle system through different display devices, S741 to S744 can be executed synchronously with any one of the following groups: S721 to S723, S724 to S726, S727 to S728, or S731 to S735, or they can be executed before any one of these groups. Furthermore, S741 to S744 can also be executed synchronously with S711 to S714, or S741 to S744 can be executed before S711 to S714.

[0157] It should also be noted that, in this application, "application login or logout" refers to logging into or logging out of an application using an application account; while "vehicle system login or logout" refers to logging into or logging out of a vehicle system using a system account. Furthermore, application logout and application exit are not the same. Application logout refers to the application account logging out of the application, while application exit refers to the termination or exit of all processes related to the application, such as stopping the application's background operation. In other words, after logging out of an application, the application may or may not exit. If the application does not exit, the display screen may show the application's running interface, or the display screen may not show the application's running interface; in this case, the application can run in the background.

[0158] To facilitate understanding of the application deployment scheme provided in the embodiments of this application, the application scenarios and GUI involved in this application will be described in detail below with reference to Figures 8 to 16. The processing actions (such as control, response, deployment, etc.) or steps involved in Figures 8 to 16 can be executed by the computing platform 150 shown in Figure 1, or they can also be executed by the aforementioned system. For example, processing actions related to application deployment can be executed by the desktop launcher.

[0159] Figure 8 illustrates an example of the GUI provided in this application embodiment. As shown in Figure 8, user A is located in the driver's seat area of ​​the vehicle cabin. At this time, the content displayed on the display screen 201 (i.e., the central control screen) can be as shown in Figure 8(a), including a content display area 1010 and a function bar 1010'. Exemplarily, the content display area 1010 includes: icons for various applications, each application icon being used to enable an application; a login control 1011 (not logged in state) for logging into the vehicle system; and Bluetooth function icons, Wi-Fi function icons, and cellular network signal icons, respectively used to indicate the vehicle's Bluetooth on and / or connection status, Wi-Fi on status, and cellular network signal strength. The function bar 1010' includes a homepage icon, seat controls, air conditioning controls, and volume controls, respectively used to control the content display area 1010 to display the homepage, control the on / off switch of seat ventilation and / or adjust the airflow of seat ventilation, control the on / off switch of air conditioning and / or adjust the air conditioning temperature and heating / cooling status, adjust the in-vehicle air circulation status, and adjust the volume of the sound device.

[0160] In some implementations, when a long press is detected on the video application icon, the display screen 201 can be controlled to display a control bar 1101 as shown in Figure 8(b). The control bar 1101 includes application details controls, application redeployment controls (i.e., "deploy to other screens"), and editing controls, which can be used to display application details, control the deployment of the application to other screens, and edit the application name, respectively.

[0161] For example, when the application redeployment control is detected to be clicked, the video application is deployed to other displays in the vehicle that do not have video applications deployed. For instance, if the vehicle includes displays 201 to 205, and displays 201, 202, and 203 all have video applications deployed, when the application redeployment control is detected to be clicked, the video application is deployed to displays 204 (i.e., the screen behind the passenger headrest) and displays 205.

[0162] Optionally, when the video application has been deployed on another display screen, the display screen 201 can be controlled to display the prompt bar 1102 shown in (c) of FIG8, which includes the prompt message "The video application has been deployed to another screen".

[0163] Figure 8(d) and (e) show the content displayed on display screen 204 before and after the video application is redeployed, respectively. It can be seen that after the video application in display screen 201 is deployed to display screen 204, a video application icon 1103 is added to display screen 204.

[0164] It should be noted that the icons shown in Figure 8 are for illustrative purposes only. In actual implementation, the content display area 1010 and the function bar 1010' may display more or fewer icons. For example, when sliding the interface switching component 1011' in the content display area 1010, the content display area 1010 may switch to other interfaces to display icons for other applications. As another example, the content display area 1010 may display some or all of the Bluetooth, Wi-Fi, and cellular network signal icons, or may not display them, depending on the user's settings. Furthermore, the function bar 1010' may display other styles of icons based on the user's settings for seat ventilation and air conditioning status.

[0165] In some implementations, when the application redeployment control is clicked, the user can be prompted to select a display screen to be deployed. For this scenario, Figure 9 shows another GUI provided in an embodiment of this application. As shown in Figure 9(a), the display screen 201 displays a control bar 1104 associated with the navigation application. When the application redeployment control in the control bar 1104 is clicked, the display screen 201 can be controlled to display a control bar 1105 as shown in Figure 9(b). This control bar includes various types of controls, such as a control 1106 corresponding to a non-selectable display screen, a control 1107 corresponding to a selectable display screen, a cancel control, a select all control, and a confirm control 1108. The non-selectable display screen can be a display screen where the navigation application has already been deployed, or it can be a display screen where the navigation application cannot be deployed; the cancel control is used to cancel the selection of the selected display screen; the select all control is used to select all selectable display screens; and the confirm control 1108 is used to confirm that the application will be deployed to the selected display screen. For example, if the control corresponding to the second row of right-side screens and the confirm control 1108 are clicked sequentially, the navigation application will be deployed to the display screen 204.

[0166] Optionally, when the navigation application has been deployed on the selected display screen, the display screen 201 can be controlled to display the prompt bar 1109 shown in (c) of Figure 9, which includes the prompt message "The navigation application has been deployed to the second row right screen".

[0167] Figure 9(d) and (e) show the content displayed on display screen 204 before and after the navigation application is redeployed. It can be seen that after the navigation application in display screen 201 is deployed to display screen 204, the navigation application icon 1110 is added to display screen 204.

[0168] It should be noted that Figures 8 and 9 are only used as examples of video and navigation applications. In actual implementation, video and navigation applications can also be other applications. Furthermore, Figure 8 shows application redeployment when the vehicle infotainment system is not logged in, while Figure 9 shows application redeployment when the vehicle infotainment system is logged in with user A's system account (the avatar 1013 displayed by the login control is the image associated with user A's system account). In actual implementation, application redeployment can be performed only when the vehicle owner's system account or authorized system account is logged into the vehicle infotainment system, or only certain applications can support application redeployment when the vehicle infotainment system is not logged in.

[0169] It should also be noted that Figures 8 and 9 illustrate the control of deploying applications already deployed on display screen 201 to other displays in response to user operations on the display screen. In actual implementation, applications deployed on one display screen can also be deployed to other displays in response to user voice commands. For example, when the voice command "Please deploy the video application to the second row right screen" is detected, the video application is deployed to display screen 204. As another example, when the voice command "Please deploy the navigation application to the second row left screen" is detected, the video application is deployed to display screen 203.

[0170] In some implementations, when the application redeployment control is clicked, the application can be deployed to a display screen in an area of ​​the cockpit where a user is present. For this scenario, Figure 10 illustrates another set of GUIs provided in this embodiment. As shown in Figure 10(a), when the application redeployment control in the control bar 1104 is clicked and a user (e.g., user B) is detected in the second row right-hand area, the navigation application is deployed to the display screen 204 in the second row right-hand area. After deploying the application to the display screen 204, the display screen 201 can be controlled to display the interface shown in Figure 10(b). Furthermore, the content displayed on the display screen 204 before and after the navigation application redeployment is shown in Figures 10(c) and (d), respectively.

[0171] Referring to Figure 10, in some implementations, when there is a user (such as user B) in the right-hand area of ​​the second row and a navigation application has been deployed on the display screen 204, when the user clicks the application redeployment control in the control bar 1104, a control bar for selecting the navigation application to be deployed on the display screen can be displayed. This control bar can be similar to the control bar 1105 shown in Figure 9(b), except that the screen controls in the right-hand area of ​​the second row in this implementation are unselectable.

[0172] For example, the presence of a user in different areas of a vehicle can be determined based on signals collected by sensors within the vehicle. For instance, pressure sensors are installed under each seat; when the pressure value measured by a sensor under a particular seat is greater than or equal to a preset pressure threshold, it can be determined that a user is present at that seat. Alternatively, one or more cameras are installed in the cabin, and the presence of a user in different areas of the vehicle is determined based on images captured by these cameras. In practical implementation, other methods can also be used to determine whether a user is present in one or more areas of the vehicle.

[0173] In some implementations, certain installed applications do not support redeployment to other displays; for example, safety-critical applications do not support redeployment to other displays. Exemplarily, safety-critical applications may include, but are not limited to, applications capable of implementing functions that affect driving safety, such as APA, AVP, ACC, LCC, NCA, forward collision warning, lane departure warning, lane keeping assist, and rear collision avoidance warning. For this scenario, Figure 11 illustrates another set of GUIs provided in an embodiment of this application. As shown in Figure 11(a), the intelligent driving application deployed on display 201 can be considered an example of a safety-critical application. In one example, when a long press is detected on an intelligent driving application, the display 201 is controlled to display a control bar 1111, which includes application detail controls and edit controls, but does not include application redeployment controls. In another example, when a long press is detected on the intelligent driving application, the control display screen 201 displays a control bar including application detail controls, edit controls, and application redeployment controls; further, when a click is detected on the application redeployment control, the control display screen 201 displays the control bar 1112 shown in Figure 11(b). As shown in Figure 11(b), the controls included in the control bar 1112 are all controls corresponding to non-selectable displays, meaning that the user cannot deploy the intelligent driving application to other displays through the control bar 1112.

[0174] In some implementations, when deploying an application already installed on one display to other displays, the deployment is based on the application's type. The application type can be either a data privacy application or a rights-sharing application.

[0175] When an application is a data privacy-preserving application, deploying the application to other displays can involve: deploying the application's icon to each of the other displays, and loading the application data for each display. It is understood that when deploying a data privacy-preserving application to other displays, the application data loaded for each display is not necessarily all of the application's data. For example, a virtual environment can be created for the application deployed on each display, allowing different application accounts to log in to the same application through different displays within the same time period. This virtual environment is an independent environment for application operation; applications running in different virtual environments do not interfere with each other, ensuring that the operation records and data of different applications do not interfere with each other. For example, if the video application in Figure 8 is a data privacy-preserving application, the use and operation of the video application deployed on each display do not interfere with each other; the video application on different displays can be logged into by different application accounts and run independently.

[0176] When an application is a shared benefits application, deploying the application to other displays can be done by deploying the application's icon to each of those displays. For example, if the video application in Figure 8 is a shared benefits application, then when an application account logs into the video application through one display, the video applications on other displays will also be logged into by that application account. Video applications deployed on different displays can play different videos independently, but all video applications on different displays share the same data and permissions.

[0177] In some implementations, when an application is already deployed on one or more displays, the user can change the application type via the application icon displayed on the display. For this scenario, Figure 12 illustrates another set of GUIs provided in an embodiment of this application. As shown in Figure 12(a), when the "Change Application Type" control in the control bar 1104' is clicked, the control display 201 displays a prompt bar 1113 as shown in Figure 12(b). The prompt bar 1113 includes the prompt message "Current application type is type 1, change to type 2?", and controls "Yes", "No", and an exit control 1114. When the "No" control or the exit control 1114 is clicked, the prompt bar 1113 is closed, and the application type change is terminated. When the "Yes" control is clicked, the navigation application is changed from type 1 to type 2. More specifically, changing the navigation application from type 1 to type 2 can be achieved by uninstalling the type 1 navigation application already deployed on each display and deploying the type 2 navigation application on the original display where the navigation application was deployed.

[0178] Optionally, after the application type is changed, the display screen 201 can be controlled to display the prompt bar 1115 shown in Figure 12(c), which includes the prompt message "Navigation application type has been changed to type 2". For example, the aforementioned type 1 can be data privacy type and type 2 can be benefit-sharing type, or type 1 can be benefit-sharing type and type 2 can be data privacy type.

[0179] The above, in conjunction with Figures 8 to 12, illustrates the specific implementation of application redeployment based on operations performed on the icons of deployed applications. It should be noted that, in actual implementation, the specific controls, content, and forms in the control bars 1101, 1104, 1105, and prompt bar 1113 shown in Figures 8 to 12 may differ from those shown in the figures, and the methods used to trigger the display of control bars 1101, 1104, 1105, and prompt bar 1113 may also differ from those described in the aforementioned embodiments.

[0180] After controlling the redeployment of an application or changing the type of an application through the desktop launcher, relevant information can be sent to the app store to update the application's deployment information and type. The app store is a platform for installing, updating, managing, and uninstalling applications. One or more displays in the vehicle can be deployed with the app store application for user access and / or use. In practice, the app store application may be deployed only on the central control screen.

[0181] In addition to redeploying applications based on operations performed on the icons of already deployed applications, application redeployment can also be controlled through the application store. For this scenario, Figure 13 illustrates another set of GUIs provided in this embodiment. As shown in Figure 13(a), the display screen 201 displays icons for the instant messaging application and the application store application. When a click is detected on the application store application icon, the display screen 201 is controlled to display the application store details page, specifically interface 1120 as shown in Figure 13(b). This interface 1120 currently displays the management interface for installed applications. Optionally, in response to clicks on the office control, category control, and settings control on the left side of interface 1120, different content can be displayed on the right side of interface 1120. More specifically, the right side of the current interface 1120 displays information about the installed applications, such as the application name (e.g., "Browser"), application type (e.g., "Type 1"), and deployment display (e.g., "Deployed on the main screen"). Furthermore, for each application, interface 1120 also provides a redeployment control 1121 and a change type control 1122.

[0182] In some implementations, when a click is detected on the redeployment control 1121 corresponding to an application, the application can be deployed to other displays using the deployment methods described in the corresponding parts of Figures 8 to 10. For example, taking a navigation application as an example, when a click is detected on the redeployment control of the navigation application, the navigation application can be deployed to all other displays where no navigation application is deployed; or, the navigation application can be deployed to other displays in areas where users are present; or, a control bar (such as control bar 1105) can be displayed for selecting the display to which the navigation application is to be deployed, and then the navigation application can be deployed to the selected display based on the display of the navigation application selected by the user.

[0183] In some implementations, when the redeployment control 1121 corresponding to a certain application (hereinafter, a video application is used as an example) is clicked, the display screen 201 can be controlled to display the interface shown in Figure 14. The right side of this interface includes a control bar 1123 for selecting the display screen to which the navigation application is to be deployed. The control bar 1123 includes multiple screen selection controls, a cancel control, a select all control, and a confirm control. Each of the multiple screen selection controls is used to control the deployment of the application to a display screen. The multiple screen selection controls can correspond to all the display screens in the vehicle that can deploy video applications. The functions of the cancel control, select all control, and confirm control can be referred to the description in the previous embodiments, and will not be repeated here. For example, regardless of which display screens the video application was previously deployed on, when the screen selection controls corresponding to the driver's screen, passenger's screen, and second-row right-side screen are clicked, and the confirm control is clicked, the video application is deployed to display screen 201 (i.e., the driver's screen), display screen 202 (i.e., the passenger's screen), and display screen 204 (i.e., the second-row right-side screen).

[0184] It should be noted that during the aforementioned process of redeploying the application based on the operation of the icon of the deployed application, when the application redeployment control is detected to be clicked, the control bar 1123 shown in Figure 14 can also be displayed, thereby responding to the user's operation of clicking one or more screen selection controls to redeploy the application to one or more displays.

[0185] In some implementations, when the type change control 1122 corresponding to a certain application (hereinafter, a video application will be used as an example) is clicked, the display screen 201 can be controlled to display the interface shown in Figure 15(a). This interface includes a prompt bar 1125, which includes the prompt message "Current application type is type 2, change to type 1?", and controls "Yes" and "No". When the control "No" is clicked, the prompt bar 1125 is closed, and the application type change is terminated. When the control "Yes" is clicked, the video application is changed from type to type 1. More specific change methods can be found in the description of the corresponding part of Figure 12, which will not be repeated here. In some implementations, when the control "Yes" is clicked, the display screen 201 can also be controlled to display the interface shown in Figure 15(b). This interface includes a prompt bar 1126, which includes the prompt message "Change the screen where the application is deployed?", and controls "Yes" and "No". When the "No" control is clicked, the application type is changed according to the corresponding part of Figure 12. When the "Yes" control is clicked, the display screen 201 can be controlled to display the interface shown in Figure 14, and then the application can be redeployed according to the method of changing the application deployment screen described in the corresponding part of Figure 14.

[0186] The above, in conjunction with Figures 13 to 15, illustrates the specific implementation of application redeployment through the app store. It should be noted that in actual implementation, the specific interface corresponding to the app store application, and the controls involved in Figures 13 to 15, may differ from those shown in the figures, and the method of triggering the display of each control may also differ from the method described in the aforementioned embodiments.

[0187] In actual implementation, which system accounts can redeploy applications and which system accounts can change application types can be set by the user through the vehicle owner's system account. For example, Figure 16 shows a set of GUIs for setting application deployment permissions. Taking user A's system account as the vehicle owner's system account as an example, when the vehicle owner's system account is logged in, the login control displays an avatar 1013. Further, as shown in Figure 16(a), when the login control is detected to be clicked, the control display screen 201 displays the details page of the vehicle system as shown in Figure 16(b). This details page includes the name 1131 of the vehicle owner's system account, the mobile phone number associated with the vehicle owner's system account 1132, and an expansion control 1133. This expansion control 1133 is used to open the settings page to set information such as name and avatar. In addition, this details page may also include a vehicle information card, which includes the vehicle name 1134, vehicle license plate number, and other related information 1135, as well as a vehicle authorization control 1136.

[0188] When the vehicle authorization control 1136 is clicked, the control display screen 201 displays the vehicle authorization details interface as shown in Figure 16(c). This interface includes cards 1137 and 1138. Card 1137 includes basic vehicle information (such as name, license plate number, etc.) and a new authorization control 1139, which is used to authorize unauthorized accounts. Card 1138 includes authorized account information. For example, authorized system accounts include account 1 and account 2, where account 1 has key and control permissions, application management permissions, and vehicle owner service permissions, and account 2 has key and control permissions and vehicle owner service permissions. Card 1138 also includes an expansion control (such as control 1140) for each account.

[0189] When a click is detected on control 1140, the display screen 201 can be controlled to display the authorization information editing interface corresponding to account 1, as shown in Figure 16(d). This interface includes a modify authorization control 1141, a delete authorization control 1142, and an authorization information card 1143 associated with application management. Specifically, the modify authorization control 1141 is used to modify the authorization content for account 1, the delete authorization control 1142 is used to revoke the authorization for account 1, and the authorization information card 1143 displays detailed information about the permissions related to application management granted to account 1. In addition, the authorization information editing interface also includes a slider control 1144. When the user slides the slider control 1144, other content of the authorization information editing interface can be accessed, such as the authorization information card associated with the key and control system, and the authorization information card associated with the vehicle owner service.

[0190] When the modification authorization control 1141 is clicked, the display screen 201 can be controlled to display the modification authorization details page corresponding to account 1 as shown in Figure 16(e). The modification authorization details page includes the application management associated settings card 1145, confirmation control 1147, and non-authorization control 1147. As shown in Figure 16(e), the controls corresponding to application installation include allow control, allow partial application control, and disallow control, which correspond to the permissions of being able to install any application in the application store, being able to install some applications, and disallowing the installation of any application, respectively. The controls corresponding to application uninstallation include allow control, allow partial application control, and disallow control, which correspond to the permissions of being able to uninstall any application other than system applications, being able to uninstall some applications other than system applications, and disallowing the uninstallation of any application, respectively. The controls corresponding to application redeployment include allow redeployment control, disallow redeployment control, allow change type control, and disallow change type control, which correspond to the permissions of being able to redeploy applications, disallowing application redeployment, being able to change application type, and disallowing change application type, respectively. It should be noted that for certain application controls that are allowed, when a click is detected, the display screen 201 can be controlled to show a custom interface. This custom interface allows setting which applications(s) can be installed and / or uninstalled under account 1. Furthermore, in the settings card 1145 shown in Figure 16(e), gray controls (such as allow controls) indicate that the corresponding permission is selected, and white controls (such as disallow controls) indicate that the corresponding permission is not selected. Further, when a click is detected on a white control, the permission corresponding to that item can be modified to the permission corresponding to the clicked white control. For example, if the disallow control and the confirmation control 1147 for application installation are clicked sequentially, the application installation permission for account 1 can be modified to disallow the installation of any applications. Additionally, if the disauthorization control 1147 and the confirmation control 1147 are clicked sequentially, the application management permissions granted to account 1 can be disabled.

[0191] When the newly created authorization control 1139 is clicked, a new authorization account can be created. Permissions for this newly created authorization account can be set through the authorization settings page shown in Figure 16(f).

[0192] It should be noted that the content and controls in the interfaces shown in Figure 16 are for illustrative purposes only. In actual implementation, when the vehicle owner's system account sets permissions for other system accounts, the interface displayed on the vehicle's screen may differ from that shown in Figure 16.

[0193] It should also be noted that Figures 8 to 16 illustrate the redeployment of applications already deployed on the central control screen. In actual implementation, applications already deployed on other screens besides the central control screen can also be redeployed.

[0194] Figure 17 shows a schematic flowchart of the application deployment method provided in an embodiment of this application. This method 30 can be applied to the vehicle shown in Figure 1, or the method can be executed by any of the systems shown in Figures 3 to 5. More specifically, the method includes:

[0195] S31, in response to a first input to a first application displayed on a first display screen of the vehicle, a first instruction is obtained, the first instruction instructing the first application to be deployed on at least one display screen in the vehicle other than the first display screen.

[0196] For example, the first display screen can be any display device in the vehicle cabin that can deploy the first application, such as any of the display devices shown in FIG2.

[0197] In some implementations, the first application can be any application other than a security-critical application.

[0198] For example, the first instruction can be generated based on a first input. The first input can be any of the following: clicking the redeployment control corresponding to the first application displayed on the first screen, or a voice command for the first application instructing it to be deployed to another screen. There are two ways to click the redeployment control corresponding to the first application: one is by long-pressing the icon of the first application on the first screen, causing a control bar including the application redeployment control to appear on the first screen, and then the user can click the application redeployment control in the control bar; the other is by displaying an application store interface on the screen, which includes a "redeploy" control corresponding to the first application, and then the user can click the "redeploy" control corresponding to the first application in the application store interface. For the former approach, the first input can be any of the following: clicking the application redeployment control shown in Figure 8(b), clicking the confirmation control 1108 shown in Figure 9(b), or clicking the application redeployment control shown in Figure 10(a).

[0199] It should be noted that for the second approach, the app store interface can be displayed on the first display screen, or it can be displayed on another display screen that has the app store application deployed. For example, the first display screen can be any one of display screens 202 to 205, and the display screen that has the app store application deployed can be display screen 201.

[0200] It should also be noted that, in actual implementation, before executing S31, the first application can be deployed on one or more other displays in the vehicle cabin, in addition to the first display.

[0201] S32, according to the first instruction, deploy the first application on at least one display screen.

[0202] In some implementations, at least one display screen includes all displays in the vehicle that can deploy the first application but do not deploy the first application, as described in the corresponding part of Figure 8 for specific implementation details.

[0203] In some other implementations, S32 can be further refined as follows: according to the first instruction, the control prompting device prompts the first information, the first information being used to prompt the user to select a display screen on which the first application is to be deployed; in response to the user's operation of selecting at least one display screen, the first application is deployed on at least one display screen.

[0204] For example, the prompting device includes the aforementioned display device, or it may also include a sound-emitting device, such as a speaker or audio device. In one example, the prompting device is a display device, and the first information may include the control bar 1105 as shown in Figure 9(b). Further, the user's operation of selecting at least one display screen may be: clicking at least one control in the control bar 1105. In yet another example, the prompting device is a sound-emitting device, and the first information may be voice information, such as "Please select the display screen where you want to deploy the first application," etc. Further, the user's operation of selecting at least one display screen may be: the user uttering the following voice: "Please deploy the first application on the xx display screen."

[0205] In some other implementations, at least one display screen includes a second display screen associated with the first area of ​​the vehicle. S32 can also be refined to: when a user is present in the first area, deploying the first application on the second display screen according to the first instruction.

[0206] The association of the second display screen with the first area of ​​the vehicle can be understood as: the second display screen belongs to the first area; or, the second display screen is for use by users in the first area to transmit information to users in the first area.

[0207] For example, taking the right-hand area of ​​the second row shown in Figure 10 as the first area, the second display screen can be display screen 204. When the first instruction is received and a user is detected in the first area, the first application can be deployed to the second display screen. For a more specific method to determine whether a user exists in the first area, and the specific implementation of deploying the application on the second display screen based on the detection result of the user in the first area, please refer to the description of the corresponding part of Figure 10, which will not be repeated here.

[0208] This implementation method can be applied to specific applications. For example, generally, rear-seat displays don't need navigation applications. The driver can input the location described by the rear passengers into the navigation application deployed on the central control screen for navigation. However, for locations that rear passengers cannot clearly describe, it's obviously more convenient to have them directly input navigation information. In this scenario, the navigation application is deployed directly to the display screen at the rear passenger's location based on the detection result, making it easier for them to use the application. The above only uses navigation applications as an example. Besides navigation applications, this implementation method can also be used to quickly redeploy some benefit-sharing applications, enabling users in the first area to quickly share the benefits of the first application.

[0209] In some implementations, the first application is of type 1 or type 2, where type 1 indicates that the application needs data isolation and type 2 indicates that the application does not need data isolation; deploying the first application on at least one display screen according to the first instruction includes: deploying the first application on at least one display screen according to the first instruction and the type of the first application.

[0210] For example, the first type can be the aforementioned data privacy application (or clone application), and the second type can be the aforementioned rights-sharing application (or instance application).

[0211] In some implementations, deploying the first application on at least one display screen according to the first instruction and the type of the first application includes: when the type of the first application is a first type, adding a first icon of the first application to each of the at least one display screen and loading application data of the first application associated with each display screen; when the type of the first application is a second type, adding a second icon of the first application to each of the at least one display screen; wherein the first icon and the second icon are the entry points for the user to use the first application.

[0212] For a more detailed description of how the first application is deployed according to the first instruction, please refer to the descriptions of the corresponding parts of Figures 8 to 10 and Figures 13 to 14, which will not be repeated here.

[0213] In some implementations, the method further includes: in response to a second input to the first application, obtaining a second instruction indicating a change in the type of the first application; and changing the first application from its original type to a target type according to the second instruction; wherein the original type is a first type and the target type is a second type; or, the original type is a second type and the target type is a first type.

[0214] For example, the second instruction can be generated based on a second input. The second input can be any of the following: a click on a control on the first display screen corresponding to the first application for changing the application type, or a voice command for the first application instructing a change of the application type. For example, the second input can be a click on the "Yes" control shown in Figure 12(b), or it can be a click on the "Yes" control shown in Figure 15(a).

[0215] In some implementations, the first application is changed from its original type to the target type according to the second instruction, including: uninstalling the first application of the original type and deploying the first application of the target type according to the second instruction.

[0216] For a more detailed explanation of how to change the application type according to the second instruction, please refer to the descriptions in the corresponding parts of Figures 12 and 15, which will not be repeated here.

[0217] In some implementations, S32 can be further refined as follows: when the first user account logs into the vehicle's infotainment system through the first display screen, the first application is deployed on at least one display screen according to the first instruction; wherein the first user account is the vehicle owner's account, or the first user account is an account authorized by the vehicle owner.

[0218] For example, the account authorized by the vehicle owner is a system account with application redeployment permissions authorized through the vehicle owner's system account, such as account 1 shown in Figure 16. The method for authorizing application redeployment permissions for a system account can be found in the description of the corresponding part of Figure 16, and will not be repeated here.

[0219] In some implementations, the method further includes: unloading a first application from a first display screen according to a first instruction.

[0220] For example, as shown in Figure 14 above, when the redeployment control is provided to the user in this way, the application on the first display screen is uninstalled if the user does not select the first display screen.

[0221] The application deployment method provided in this application embodiment can facilitate users to adjust the applications deployed on multiple displays in the cockpit at any time, which helps to improve the convenience of application deployment and thus improve the user experience.

[0222] In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions between the various embodiments are consistent and can be referenced by each other. Technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0223] The methods provided by the embodiments of this application have been described in detail above with reference to Figures 1 to 17. The apparatus provided by the embodiments of this application will now be described in detail below with reference to Figures 18 and 19. It should be understood that the descriptions of the apparatus embodiments correspond to the descriptions of the method embodiments; therefore, any content not described in detail can be referred to the method embodiments above, and for the sake of brevity, will not be repeated here.

[0224] Figure 18 shows a schematic block diagram of an apparatus 2000 provided in an embodiment of this application. The apparatus 2000 may include units for executing the methods described in the foregoing embodiments. Furthermore, each unit in the apparatus 2000 implements a corresponding process of the above method embodiments. The apparatus 2000 includes an acquisition unit 2010, which can be used to implement corresponding data acquisition or transmission / reception functions. The apparatus 2000 also includes a processing unit 2020, which can be used to implement corresponding processing functions.

[0225] Optionally, the device 2000 further includes a storage unit, which can be used to store instructions and / or data. The processing unit 2020 can read the instructions and / or data in the storage unit so that the device can perform the relevant actions in the aforementioned method embodiments.

[0226] It should be understood that the specific process of each unit performing the above-mentioned corresponding steps has been described in detail in the above method embodiments, and will not be repeated here for the sake of brevity.

[0227] It should also be understood that the device 2000 described herein is embodied in the form of a functional unit. The terms “module” or “unit” may refer to application-specific ASICs, electronic circuits, processors (e.g., shared processors, proprietary processors, or group processors) and memory for executing one or more software or firmware programs, integrated logic circuits, and / or other suitable components that support the described functions.

[0228] The apparatuses described above are capable of implementing the corresponding steps performed by the computing platform 150 in the methods described above. These functions can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the functions described above; for example, the acquisition unit 2010 can be replaced by a transceiver, and other units, such as processing units, can be replaced by a processor, used to execute the relevant processing operations in each method embodiment.

[0229] Exemplarily, the acquisition unit 2010 and processing unit 2020 can be disposed in the vehicle 100 shown in FIG1, or in any of the systems shown in FIG3 to FIG5. More specifically, the acquisition unit 2010 and processing unit 2020 can be disposed in a desktop launcher. Exemplarily, the operations performed by the acquisition unit 2010 and processing unit 2020 can be performed by a single processor, or by different processors. In specific implementation, the one or more processors can be processors disposed in the vehicle 100 shown in FIG1; or, the device 2000 can be a chip disposed in the vehicle 100.

[0230] In the specific implementation process, the units in the above device can be fully or partially integrated together, or they can be implemented independently. In one implementation, these units are integrated together and implemented in the form of a system-on-a-chip (SoC).

[0231] Figure 19 is another schematic block diagram of the apparatus provided in an embodiment of this application. The apparatus 2100 shown in Figure 19 may include a processor 2110, a transceiver 2120, and a memory 2130. The processor 2110, transceiver 2120, and memory 2130 are connected via internal interconnection paths. The memory 2130 is used to store instructions, and the processor 2110 is used to execute the instructions stored in the memory 2130 to implement the methods in the above embodiments. Optionally, the memory 2130 may be coupled to the processor 2110 via an interface or integrated with the processor 2110.

[0232] It should be noted that the transceiver 2120 mentioned above may include, but is not limited to, transceiver devices such as input / output interfaces, to realize communication between device 2100 and other devices or communication networks.

[0233] Memory 2130 can be volatile memory and / or non-volatile memory. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM). For example, RAM can be used as an external cache. By way of example and not limitation, RAM includes various forms such as: static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0234] Transceiver 2120 uses transceiver devices, such as but not limited to transceivers, to enable communication between device 2100 and other devices or communication networks to receive / send data / information for implementing the methods in the above embodiments.

[0235] This application also provides an intelligent driving device, which includes the device 2000 or device 2100 in the above embodiments.

[0236] This application also provides a computer program product, which includes computer program code. When the computer program code is run on a computer, it causes the computer to implement the methods described in the above embodiments of this application.

[0237] This application also provides a computer-readable storage medium storing computer instructions that, when executed on a computer, cause the computer to implement the methods described in the above embodiments of this application.

[0238] This application also provides a chip, including circuitry, for performing the methods described in the above embodiments of this application.

[0239] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0240] In the description of the embodiments of this application, unless otherwise stated, " / " means "or", for example, A / B can mean A or B; "and / or" in this document describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. In this application, "at least one" means one or more, and "more" means two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or multiple items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple.

[0241] The use of prefixes such as "first" and "second" in this application embodiment is solely for distinguishing different descriptive objects and does not limit the position, order, priority, quantity, or content of the described objects. The use of ordinal numbers and other prefixes to distinguish descriptive objects in this application embodiment does not constitute a limitation on the described objects. The description of the described objects is found in the claims or the context of the embodiments, and the use of such prefixes should not constitute unnecessary restrictions.

[0242] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0243] In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions between the various embodiments are consistent and can be referenced by each other. Technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

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

[0245] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0246] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. An application deployment method, characterized in that, include: In response to a first input to a first application displayed on a first display screen of a vehicle, a first instruction is obtained, the first instruction instructing the first application to be deployed on at least one display screen in the vehicle other than the first display screen; According to the first instruction, the first application is deployed on the at least one display screen.

2. The method according to claim 1, characterized in that, The step of deploying the first application on the at least one display screen according to the first instruction includes: According to the first instruction, the control prompting device prompts the first information, which is used to prompt the user to select the display screen where the first application is to be deployed; In response to a user's selection of the at least one display screen, the first application is deployed on the at least one display screen.

3. The method according to claim 1, characterized in that, The at least one display screen includes a second display screen associated with a first area of ​​the vehicle, and the step of deploying the first application on the at least one display screen according to the first instruction includes: When a user is present in the first area, the first application is deployed on the second display screen according to the first instruction.

4. The method according to any one of claims 1 to 3, characterized in that, The first application is of type one or type two, where type one indicates that the application needs data isolation and type two indicates that the application does not need data isolation; Deploying the first application on the at least one display screen according to the first instruction includes: Based on the first instruction and the type of the first application, the first application is deployed on the at least one display screen.

5. The method according to claim 4, characterized in that, Deploying the first application on the at least one display screen according to the first instruction and the type of the first application includes: When the type of the first application is the first type, a first icon of the first application is added to each of the at least one display screen, and application data of the first application associated with each display screen is loaded; When the type of the first application is the second type, a second icon of the first application is added to each of the at least one display screen; The first icon and the second icon serve as the entry points for users to access the first application.

6. The method according to claim 4 or 5, characterized in that, The method further includes: In response to a second input to the first application, a second instruction is obtained, the second instruction indicating a change in the type of the first application; According to the second instruction, the first application is changed from its original type to the target type; Wherein, the original type is the first type and the target type is the second type; or, the original type is the second type and the target type is the first type.

7. The method according to claim 6, characterized in that, The step of changing the first application from its original type to the target type according to the second instruction includes: According to the second instruction, uninstall the first application of the original type and deploy the first application of the target type.

8. The method according to any one of claims 1 to 7, characterized in that, Deploying the first application on the at least one display screen according to the first instruction includes: When a first user account logs into the vehicle's infotainment system via the first display screen, the first application is deployed on the at least one display screen according to the first instruction. Wherein, the first user account is the account of the vehicle owner, or the first user account is an account authorized by the vehicle owner.

9. The method according to any one of claims 1 to 8, characterized in that, The method further includes: According to the first instruction, uninstall the first application on the first display screen.

10. The method according to any one of claims 1 to 9, characterized in that, The first application is any application other than a security-critical application.

11. An application deployment device, characterized in that, include: The acquisition unit is configured to: in response to a first input to a first application displayed on a first display screen of a vehicle, acquire a first instruction, the first instruction instructing the first application to be deployed on at least one display screen in the vehicle other than the first display screen; The processing unit is configured to: deploy the first application on the at least one display screen according to the first instruction.

12. The apparatus according to claim 11, characterized in that, The processing unit is used for: According to the first instruction, the control prompting device prompts the first information, which is used to prompt the user to select the display screen where the first application is to be deployed; In response to a user's selection of the at least one display screen, the first application is deployed on the at least one display screen.

13. The apparatus according to claim 11, characterized in that, The at least one display screen includes a second display screen, the second display screen being associated with a first area of ​​the vehicle, and the processing unit is configured to: When a user is present in the first area, the first application is deployed on the second display screen according to the first instruction.

14. The apparatus according to any one of claims 11 to 13, characterized in that, The first application is of type one or type two, where type one indicates that the application needs data isolation and type two indicates that the application does not need data isolation; The processing unit is used for: Based on the first instruction and the type of the first application, the first application is deployed on the at least one display screen.

15. The apparatus according to claim 14, characterized in that, The processing unit is used for: When the type of the first application is the first type, a first icon of the first application is added to each of the at least one display screen, and application data of the first application associated with each display screen is loaded; When the type of the first application is the second type, a second icon of the first application is added to each of the at least one display screen; The first icon and the second icon serve as the entry points for users to access the first application.

16. The apparatus according to claim 14 or 15, characterized in that, The acquisition unit is also used for: In response to a second input to the first application, a second instruction is obtained, the second instruction indicating a change in the type of the first application; The processing unit is also used for: According to the second instruction, the first application is changed from its original type to the target type; Wherein, the original type is the first type and the target type is the second type; or, the original type is the second type and the target type is the first type.

17. The apparatus according to claim 16, characterized in that, The processing unit is used for: According to the second instruction, uninstall the first application of the original type and deploy the first application of the target type.

18. The apparatus according to any one of claims 11 to 17, characterized in that, The processing unit is used for: When a first user account logs into the vehicle's infotainment system via the first display screen, the first application is deployed on the at least one display screen according to the first instruction. Wherein, the first user account is the account of the vehicle owner, or the first user account is an account authorized by the vehicle owner.

19. The apparatus according to any one of claims 11 to 18, characterized in that, The processing unit is also used for: According to the first instruction, uninstall the first application on the first display screen.

20. The apparatus according to any one of claims 11 to 19, characterized in that, The first application is any application other than a security-critical application.

21. An application deployment device, characterized in that, include: A processor for executing a computer program stored in memory to cause the apparatus to perform the method as described in any one of claims 1 to 10.

22. The apparatus according to claim 21, characterized in that, The device also includes the memory.

23. A computer-readable storage medium, characterized in that, It stores instructions that, when executed by a processor, implement the method as described in any one of claims 1 to 10.

24. A chip, characterized in that, The chip includes circuitry for performing the method as described in any one of claims 1 to 10.

25. A computer program product, characterized in that, The computer program product includes: computer program code, which, when executed by a processor, implements the method as described in any one of claims 1 to 10.

26. A vehicle, characterized in that, Includes the apparatus as described in any one of claims 11 to 22, or the computer-readable storage medium as described in claim 23, or the chip as described in claim 24, or the vehicle is equipped with the computer program product as described in claim 25.

Images