Application unloading method and device and vehicle

Abstract

The invention provides an application unloading method and device and a vehicle, and the method comprises the steps: obtaining a first unloading instruction of a user for a first application on a first screen, the first application being deployed on a plurality of screens in a cabin, the plurality of screens including the first screen; and in response to the first uninstalling instruction, executing an uninstalling operation according to the type of the first application, the type of the first application including a duplicate type or an instance type. The method can be applied to an intelligent automobile or an electric automobile, can support a user to flexibly unload the application, and facilitates the improvement of the driving experience of the user.

Description

Technical Field

[0001] The present application relates to the field of smart cockpits, and more specifically, to a method, device, and vehicle for offloading applications. Background Art

[0002] When a user uninstalls an app in the vehicle's cockpit, they typically uninstall apps on other screens at the same time. This inflexible uninstallation method forces the user to reinstall the app when they want to use it on another screen, resulting in a poor user experience. Summary of the Invention

[0003] The present application provides a method, device, and vehicle for uninstalling applications, which can support users to flexibly uninstall applications and help improve the user's driving experience.

[0004] In a first aspect, a method for uninstalling an application is provided, the method comprising: obtaining a first uninstall instruction from a user for a first application on a first screen, the first application being deployed on multiple screens in a cockpit, the multiple screens including the first screen; in response to the first uninstall instruction, performing an uninstall operation according to a type of the first application, the type of the first application including a clone type or an instance type.

[0005] Based on the above technical solution, applications can be uninstalled based on their types. This allows users to flexibly uninstall applications, which helps improve their driving experience.

[0006] In some possible implementations, the method further includes: determining a type of the first application based on an installation type of the first application.

[0007] Exemplarily, if the installation type of the first application is privacy-critical, then the type of the first application may be clone type.

[0008] For example, if the installation type of the first application is a benefit-sharing type, then the type of the first application may be an instance type.

[0009] The above clone applications can include a main application and clone applications, and the main application and clone applications can be deployed on different displays. When the main application is uninstalled, all clone applications are uninstalled together. Uninstalling the clone application does not affect the normal use of the main application. The main application can include the main application's user data and the main program segment. The main program segment includes programs associated with application startup. The clone application includes the clone application's user data and the clone application program. The clone application can include programs related to the ability to use the main application.

[0010] Unlike the aforementioned cloned apps, instanced apps do not distinguish between the main app and cloned apps. Regardless of which screen an instanced app is deployed on, there can only be one application entity (or main app) corresponding to that instanced app in the vehicle, and the icon for that instanced app will appear on all multiple screens. When the main app is uninstalled, the instanced app is completely uninstalled.

[0011] In combination with the first aspect, in certain implementations of the first aspect, an uninstall operation is performed based on the type of the first application, including: in response to the first uninstall instruction, when the type of the first application is an instance type, deleting the icon of the first application on the first screen and not performing the uninstall operation on the first application.

[0012] Based on the above technical solution, when uninstalling an instance-based application deployed on a certain display screen, if the instance-based application is deployed on multiple displays in the cabin, the vehicle may not uninstall the application entity (or main application) of the instance-based application, but instead delete the instance-based application icon displayed on the display screen. In this way, the user can still use the instance-based application on other displays that display the instance-based application icon.

[0013] In combination with the first aspect, in certain implementations of the first aspect, the method further includes: in response to obtaining a second uninstall instruction from the user for the first application on the second screen, performing an uninstall operation on the first application, and the second screen is the only screen among the multiple screens on which the first application is deployed.

[0014] Based on the above technical solution, when performing the uninstallation operation of the instance-type application, if the instance-type application is only deployed on the display screen in the current cabin, the vehicle can perform the uninstallation operation of the application entity (or main application) of the instance-type application.

[0015] In some possible implementations, the second screen is the only screen among the multiple screens on which the first application is deployed. It can also be understood that the second screen can be the only screen among the multiple screens on which the icon of the first application is displayed.

[0016] In combination with the first aspect, in certain implementations of the first aspect, in response to the first uninstall instruction, the icon of the first application on the first screen is deleted and the uninstall operation of the first application is not performed, including: when the type of the first application is a clone type, the first clone application corresponding to the first application is deployed on the first screen, and the main application corresponding to the first application is deployed on the third screen, in response to the first uninstall instruction, the icon of the first application on the first screen is deleted and the first clone application is uninstalled.

[0017] Based on the above technical solution, when the main application corresponding to the cloned application is deployed on the third screen and the cloned application corresponding to the cloned application is deployed on the first screen, if the user uninstalls the cloned application on the first screen, the cloned application can be uninstalled and the cloned application icon corresponding to the cloned application displayed on the first screen can be deleted. In this case, the vehicle does not need to uninstall the main application. In this way, even if the user uninstalls the cloned application corresponding to the cloned application on the first screen, the user can still use the main application of the cloned application on the third screen.

[0018] In combination with the first aspect, in certain implementations of the first aspect, in response to the first uninstall instruction, the icon of the first application on the first screen is deleted and the uninstall operation of the first application is not performed. The method also includes: when the first application is a clone application, the main application corresponding to the first application is deployed on the first screen and the second clone application corresponding to the first application is deployed on the fourth screen, in response to the first uninstall instruction, the icon of the first application on the first screen is deleted.

[0019] Based on the above technical solution, when the first application is a clone application, the main application corresponding to the first application is deployed on the first screen in the cockpit and the clone application corresponding to the first application is deployed on the fourth screen, if it is detected that the user uninstalls the first application deployed on the first screen, only the icon of the first application displayed on the first screen can be deleted.

[0020] In combination with the first aspect, in certain implementations of the first aspect, the method also includes: obtaining a third uninstall instruction from the user for the first application on the fifth screen; when the fifth screen is the only screen among the multiple screens on which the icon of the first application is deployed, uninstalling the main application in response to the third uninstall instruction.

[0021] Based on the above technical solution, when the first application is a clone application and the first application is deployed only on the fifth screen in the cockpit, if it is detected that the user uninstalls the first application deployed on the fifth screen, the main application can be uninstalled.

[0022] In combination with the first aspect, in certain implementations of the first aspect, in response to the first uninstall instruction, an uninstall operation is performed according to the type of the first application, including: in response to the first uninstall instruction, controlling the first screen to display a first interface, the first interface including prompt information, the prompt information being used to prompt the user to delete the icon of the first application deployed on the first screen or uninstall the first application; receiving the user's first instruction on the first interface; and performing the uninstall operation according to the first instruction.

[0023] Based on the above technical solution, the user can choose to delete the icon of the first application deployed on the first screen or uninstall the first application. In this way, the user can uninstall the first application by operating on one screen, which helps to improve the user's driving experience.

[0024] In combination with the first aspect, in certain implementations of the first aspect, in response to the first uninstall instruction, an uninstall operation is performed according to the type of the first application, including: in response to the first uninstall instruction, controlling the first screen to display a second interface, the second interface including information of the multiple screens; receiving a second instruction from the user on the first interface, the second instruction indicating at least one of the multiple screens; and performing the uninstall operation according to the second instruction.

[0025] Based on the above technical solution, the user can view information of all screens where the first application is deployed on the first screen. In this way, it is convenient for the user to select from them, and the user can operate on one screen to uninstall the first application deployed on other screens.

[0026] In some possible implementations, the information of the multiple screens displayed on the second interface is the multiple screens on which the first application is deployed.

[0027] In a second aspect, a device for uninstalling an application is provided, which includes: an acquisition unit for acquiring a first uninstall instruction from a user for a first application on a first screen, where the first application is deployed on multiple screens in a cockpit, and the multiple screens include the first screen; a processing unit for performing an uninstall operation in response to the first uninstall instruction and according to the type of the first application, where the type of the first application includes a clone type or an instance type.

[0028] In combination with the second aspect, in certain implementations of the second aspect, the processing unit is specifically used to: in response to the first uninstall instruction, when the type of the first application is an instance type, delete the icon of the first application on the first screen and do not perform an uninstall operation on the first application.

[0029] In combination with the second aspect, in certain implementations of the second aspect, the processing unit is also used to perform an uninstall operation on the first application in response to obtaining a second uninstall instruction from the user for the first application on the second screen, and the second screen is the only screen among the multiple screens on which the first application is deployed.

[0030] In combination with the second aspect, in certain implementations of the second aspect, the processing unit is specifically used to: when the type of the first application is a clone type, the first clone application corresponding to the first application is deployed on the first screen, and the main application corresponding to the first application is deployed on the third screen, in response to the first uninstall instruction, delete the icon of the first application on the first screen and uninstall the first clone application.

[0031] In combination with the second aspect, in certain implementations of the second aspect, the processing unit is specifically used to: when the first application is a clone application, the main application corresponding to the first application is deployed on the first screen, and the second clone application corresponding to the first application is deployed on the fourth screen, in response to the first uninstall instruction, delete the icon of the first application on the first screen.

[0032] In combination with the second aspect, in certain implementations of the second aspect, the acquisition unit is further used to obtain a third uninstall instruction from the user for the first application on the fifth screen; the processing unit is further used to uninstall the main application in response to the third uninstall instruction when the fifth screen is the only screen among the multiple screens on which the icon of the first application is deployed.

[0033] In combination with the second aspect, in certain implementations of the second aspect, the device also includes: a control unit, for controlling the first screen to display a first interface in response to the first uninstall instruction, the first interface including prompt information, the prompt information being used to prompt the user to delete the icon of the first application deployed on the first screen or uninstall the first application; a receiving unit, for receiving the first instruction from the user on the first interface; and the processing unit, for performing the uninstall operation according to the first instruction.

[0034] In combination with the second aspect, in certain implementations of the second aspect, the device also includes: a control unit, for controlling the first screen to display a second interface in response to the first uninstall instruction, wherein the second interface includes information of the multiple screens; a receiving unit, for receiving a second instruction from the user on the first interface, wherein the second instruction indicates at least one of the multiple screens; and the processing unit, for performing an uninstall operation according to the second instruction.

[0035] In a third aspect, the present application provides an application uninstallation device, which includes a processor and a memory, wherein the memory is used to store instructions, and the processor executes the instructions stored in the memory to enable the device to perform any possible method in the first aspect.

[0036] In a fourth aspect, the present application provides an application uninstallation system, which includes a computing platform and multiple display devices, wherein the computing platform includes any possible device in the second aspect or the third aspect.

[0037] In a fifth aspect, the present application provides a vehicle, which includes any possible device in the second aspect or the third aspect, or includes the system described in the fourth aspect.

[0038] In a sixth aspect, the present application provides a computer program product, comprising: a computer program code, which, when executed on a computer, enables the computer to execute any possible method in the first aspect.

[0039] It should be noted that the above-mentioned computer program code can be stored in whole or in part on the first storage medium, wherein the first storage medium can be packaged together with the processor or separately packaged with the processor, and the embodiments of the present application do not specifically limit this.

[0040] In a seventh aspect, the present application provides a computer-readable medium storing a program code, which enables the computer to execute any possible method in the first aspect when the computer program code is run on the computer.

[0041] In an eighth aspect, the present application provides a chip system comprising a processor for calling a computer program or computer instruction stored in a memory so that the processor executes any possible method in the above-mentioned first aspect.

[0042] In combination with the eighth aspect, in a possible implementation, the processor is coupled to the memory through an interface.

[0043] In combination with the eighth aspect, in one possible implementation, the chip system also includes a memory, in which a computer program or computer instructions are stored.

[0044] In a ninth aspect, the present application provides a chip system comprising a circuit for executing any possible method in the first aspect. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0046] Figure 2 is a schematic diagram of a vehicle cabin scene provided by an embodiment of the present application;

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

[0048] Figure 4 is another schematic block diagram of a control system provided in an embodiment of the present application;

[0049] Figure 5is another schematic block diagram of a control system provided in an embodiment of the present application;

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

[0051] Figure 7 is a schematic flow chart of the control method provided in an embodiment of the present application;

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

[0053] Figure 9 This is another schematic diagram of the GUI provided in an embodiment of the present application;

[0054] Figure 10 is another schematic diagram of the GUI provided in an embodiment of the present application;

[0055] Figure 11 is another schematic diagram of the GUI provided in an embodiment of the present application;

[0056] Figure 12 is another schematic diagram of the GUI provided in an embodiment of the present application;

[0057] Figure 13 is another schematic diagram of the GUI provided in an embodiment of the present application;

[0058] Figure 14 is another schematic diagram of the GUI provided in an embodiment of the present application;

[0059] Figure 15 This is a schematic flowchart of the application uninstallation method provided in an embodiment of the present application.

[0060] Figure 16 This is another schematic flowchart of the application uninstallation method provided in an embodiment of the present application.

[0061] Figure 17 This is a schematic block diagram of an application uninstallation device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0062] The technical solution in this application will be described below with reference to the accompanying drawings.

[0063] Figure 1 This is a functional block diagram of a vehicle provided in an embodiment of the present application. Figure 1As shown, the vehicle 100 may include a display device 130 and a computing platform 150, wherein the display device 130 in the cockpit is mainly divided into two categories, the first category is the vehicle-mounted display screen; the second category is a projection display screen, such as a head-up display (HUD). The vehicle-mounted display screen is a physical display screen and is an important part of the vehicle infotainment system. Multiple display screens can be set up in the cockpit, such as a digital instrument display screen, a central control screen, a display screen in front of the passenger on the front passenger seat (also called the front passenger), a display screen in front of the left rear passenger, and a display screen in front of the right rear passenger. Even the windows can be used as display screens for display. Head-up display, also known as head-up display system. It is mainly used to display driving information such as speed and navigation on a display device in front of the driver (such as a windshield). This can reduce the driver's line of sight diversion time, avoid pupil changes caused by the driver's line of sight diversion, and improve driving safety and comfort. For example, HUD includes a combiner-HUD (C-HUD) system, a windshield-HUD (W-HUD) system, and an augmented reality HUD (AR-HUD) system.

[0064] Some or all functions of the vehicle 100 may be controlled by a computing platform 150. The computing platform 150 may include processors 151 to 15n. A processor is a circuit capable of processing signals. In one implementation, the processor may be a circuit capable of reading and executing instructions, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor may implement certain functions through the logical relationships of a hardware circuit. The logical relationships of the hardware circuit may be fixed or reconfigurable. For example, the processor may be a hardware circuit implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as a field programmable gate array (FPGA). In a reconfigurable hardware circuit, the process of the processor loading a configuration file to implement the hardware circuit configuration can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units. In addition, the processor may also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), etc. In addition, the computing platform 150 may also include a memory for storing instructions, and some or all of the processors 151 to 15n may call the instructions in the memory to implement corresponding functions.

[0065] Optionally, the structure of the above vehicle 100 is merely illustrative, and in actual applications, various components in the above vehicle 100 may be added or deleted according to actual needs.

[0066] Figure 2A schematic diagram of a vehicle cockpit scene provided for an embodiment of the present application. One or more vehicle-mounted display screens (or vehicle-mounted screens) are arranged inside the smart cockpit, including but not limited to display screen 201 (or central control screen), display screen 202 (or co-pilot entertainment screen), display screen 203 (or screen behind the main driver's headrest), display screen 204 (or screen behind the co-pilot's headrest), display screen 205 (or second-row entertainment screen) arranged on the top of the cockpit, and instrument screen. Furthermore, display screens 201 to 205 can display a graphical user interface (GUI), which can include one or more application icons, and / or one or more cards. For example, Figure 1 The display device 130 shown may display one or more of the screens 201 to 205. In some possible implementations, the screen 201 may be a long screen extending to the passenger seat area. In addition, the screen 205 may be a projection screen associated with a projector. The projector may be associated with a desktop launcher, and the desktop launcher may be used to manage applications projected onto the projection screen.

[0067] Figure 2 The cockpit may also be equipped with one or more cameras to capture images inside or outside the cabin, such as a driver monitoring system (DMS) camera, a cabin monitoring system (CMS) camera, and a dashcam camera. The cameras used to capture images inside and outside the cabin can be the same or different. Furthermore, the cabin may also be equipped with one or more pressure sensors and acoustic wave sensors to monitor the presence and location of a user.

[0068] It should be understood that the method for controlling the display in the following embodiments is based on Figure 2 The five-seater vehicle shown is used as an example for illustration, and the embodiments of the present application are not limited thereto. For example, for a seven-seater sport / suburban utility vehicle (SUV), the cockpit may include a central control screen, a co-pilot entertainment screen, a screen behind the driver's headrest, a screen behind the co-pilot's headrest, entertainment screens in the three-row left area, and entertainment screens in the three-row right area. For another example, for a passenger car, the cockpit may include front-row entertainment screens and rear-row entertainment screens; or, the cockpit may include a display screen in the driving area and an entertainment screen in the passenger area. In addition, the following embodiments are described using a left-hand drive vehicle (i.e., the driver is on the left side of the vehicle) as an example. In actual implementation, the vehicle may also be a right-hand drive vehicle (i.e., the driver is on the right side of the vehicle).

[0069] In order to facilitate the understanding of the technical solution of this application, the following Figures 3 to 17 The solution provided in the embodiments of the present application is described in detail.

[0070] Figure 3 FIG. 1 shows a schematic block diagram of a control system provided by an embodiment of the present application. Figure 3 As shown, the control system includes multiple display devices, such as display device 1, display device 2, and display device n (n is a positive integer). Multiple display devices are associated with a single user space. In other words, multiple display devices share a set of system services. Regardless of which of the multiple display devices a system account uses to log into the vehicle system, the functions the user wishes to access through the system account are supported by the same system services. For example, system services may include basic services such as a desktop launcher, voice services, and data management. The desktop launcher provides 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 storage areas). It is understandable that the storage load occupied by the system services required for each user space, as well as 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. In addition, when switching system accounts on each display device, it is necessary to stop the 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 may cause the system to freeze, resulting in an unsmooth display on the display device, or causing the newly logged-in system account to wait for a long time before using applications. Therefore, setting up a single user space for multiple display devices helps save storage and computing overhead. If the system account logged in to the car system changes, there is no need to stop and start the system service, which helps reduce car system freezes and improves the smoothness of car system operation, thereby improving the user experience.

[0071] The above system account can also be called the car account.

[0072] It should be noted that the user space involved in this application can be understood as the operating environment of the application. The applications deployed in any two display devices from display device 1 to display device n can be the same or different. In addition, Figure 3 The display device 1, the display device 2 and the display device n may be included in Figure 1 In the display device 130 shown, the arrangement positions of the display device 1, the display device 2 and the display device n in the cockpit can refer to Figure 2The arrangement positions of the display screens 201 to 205 are shown and will not be described in detail here.

[0073] It should also be noted that the applications or applications referred to below in this application refer to software running in the vehicle system. The icon corresponding to the application refers to the entrance for using or accessing the application. Application login or logout refers to the login or logout of the application account in the application. Application exit refers to closing the application or ending the application-related process. Deploying an application on a certain screen means deploying the access entrance of the application on a certain screen, for example, the icon of the application (or, application), the main application of the application, or the clone application of the application can be deployed on a certain screen.

[0074] Figure 4 FIG. 1 shows another schematic block diagram of a control system provided by an embodiment of the present application. Figure 4 As shown, 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 . Figure 4 The functional characteristics of each unit shown can be determined by Figure 1 The system is implemented by one or more processors in the computing platform 150. More specifically, the functions of each unit in the system are as described in the following (1) to (4):

[0075] (1) The user management unit 410 is used to provide an interface for users to log into the vehicle-mounted system and set system account permissions. More specifically, the user management unit 410 includes a login management unit 411 and a permissions management unit 412. The login management unit 411 is used to obtain a system account for requesting to log into or log out of the vehicle-mounted system. In some implementations, system accounts can include at least three types: an owner system account, an authorized system account, and a guest system account. An owner system account is the account of the legal owner of the vehicle, an authorized system account is an account authorized by the legal owner of the vehicle, and a guest system account is an account not authorized by the legal owner of the vehicle. The permissions management unit 412 is used to obtain the permissions of the system account. The permissions of the system account can be set by the user or by the default of the vehicle-mounted system. In some implementations, the permissions of the system account can include at least one of the following: whether the user has the permission to install applications, whether the user has the 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 the user has access to the data storage area, and which applications are allowed to access the data storage area. For example, system account 1 has the permission to install applications and can install all applications in the application 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 example, the legal owner of the vehicle can set the permissions of the authorized system account and the guest system account. For example, when the vehicle owner's system account logs into the vehicle system, the user can set the permissions of the authorized system account and the guest system account through the vehicle's human machine interface (HMI), and the permission management unit 412 can obtain the permissions of the system account entered by the user through the HMI.

[0076] (2) The application management unit 420 is used to provide users with an interface for logging into applications and for applications to access the data storage area. 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 is used to manage and control application logins. The application login management unit 421 can obtain the application account used to log into a particular application, thereby controlling the application account's access to the application. The user center management unit 422 can obtain the system account currently logged into the vehicle system and send the information about the system account currently logged into the vehicle system to the application login management unit 421. The application login management unit 421 can then use the application account associated with the system account to log into one or more applications based on the system account currently logged into the vehicle system. The user center management unit 422 can also obtain the system account used to log out of the vehicle system and send the information about the system account logged out of the vehicle system to the application login management unit 421. The application login management unit 421 can then control the application account associated with the system account to log out of one or more applications based on the logged-out system account. The access management unit 423 is used to manage the application's permissions to read data from the data storage area and store data in the data storage area. Access management unit 423 can determine, based on the application's permissions, whether to send an application's data read or data storage request to public data service unit 440. In one example, if an application has permission to access the data storage area, access management unit 423 will send a data read / store request to public data service unit 440 to read the data required by the application or to 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 will ignore the application's data read / store request and will not send the data read / store request to public data service unit 440.

[0077] (3) The user-centered service unit 430 is used to perform system account management and data access management. More specifically, the user-centered service unit 430 includes an account management unit 431 and a data management unit 432. The account management unit 431 is used to control the system account to log into the vehicle system according to the request for the system account to log into the vehicle system obtained from the user management unit 410; or, it can also control the system account to log out of the vehicle system according to the request for the system account to log out of the vehicle system obtained from the user management unit 410. In addition, after controlling a system account to log in or log out of the vehicle system, the user-centered service unit 430 can send a notification of logging in or out with the system account to the application management unit 420. The data management unit 432 can obtain the permission information of the system account from the user management unit 410, determine the applications under the system account that can access the data storage area based on the permission information of the system account, and then send the information of the applications under the system account that can access the data storage area to the public data service unit 440.

[0078] (4) The public data service unit 440 is used to provide data storage and reading 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 an access path unit for a system account. 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. An access path unit is set for one or more system accounts that have permission to access the data storage area. At least one application running under the system account with the access path unit set needs to store data in or read data from the data storage area through the access path unit associated with this system account. One system account cannot read and 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 picture 1 in the data storage area through access path unit 1 associated with system account 1, but application 1 under system account 2 does not store picture 1 in the data storage area through access path unit 2 associated with system account 2, then system account 2 cannot read picture 1 from the data storage area. In addition, for some applications (such as those with low privacy or security requirements), data reading and writing can also be performed without going through the access path unit. In this case, if such an application stores data A under one system account, it can also read the data A under another system account.

[0079] The media library 442 and the file library 443 are used to store data. When the media library 442 or the file library 443 receives a data read or write request (i.e., a data read or write request) from the access management unit 423, the request authority management module 441 is requested to authenticate the data read or write request to determine whether the data read or write request has the authority to access the data it requests to access. The data read or write request can be an access request for a data storage area by an application. When the data read or write request is authenticated, the public data service unit 440 sends the data requested to be read by the data read or write request to the application management unit 420; or, when the data read or write request is authenticated, the public data service unit 440 stores the data requested to be stored by the data read or write request to the corresponding area of ​​the media library 442 or the file library 443; or, when the data read or write request is authenticated, a data access failure notification is sent to the public data service unit 440 to the application management unit 420.

[0080] It should be understood that Figure 4 The architecture shown is only an example. Figure 4 The illustrated system may include more or fewer units. For example, Figure 4 The system shown may include multiple login management units 411, each login management unit 411 corresponds to one of the multiple display devices of the vehicle; for example, Figure 4 The illustrated system may also include multiple application management units 420, each of which is a login interface and / or data access interface corresponding to an application. The multiple applications corresponding to the multiple application management units 420 can be deployed on one or more display devices in the vehicle. More specifically, when a user uses system account 1 to log in to the vehicle system through a display device (e.g., display device a), the login management unit 411 corresponding to display device a can send a login request to the user-centered service unit 430, indicating that system account 1 is requesting to log in to the vehicle system through display device a. Furthermore, the user-centered service unit 430 controls system account 1 to log in to the vehicle system through display device a based on the login request. Furthermore, the user-centered service unit 430 sends a system account 1 login notification to at least one application management unit, indicating that system account 1 has logged in to the vehicle system through display device a. At least one application management unit controls the application account associated with system account 1 to log in to one or more applications associated with system account 1 deployed on display device a. The at least one application management unit may include an application management unit 420 corresponding to all applications installed in the vehicle system, or the at least one application management unit may include an application management unit 420 corresponding only to applications deployed in the display device a.

[0081] It is understandable that Figure 4The system architecture in one user space is shown. In actual implementation, multiple display devices in a vehicle can also be associated with multiple user spaces. Figure 5 As shown, display device 1, display device 2 and display device n (n is a positive integer) can be associated with user space 1 to user space n' respectively, and n' is an integer greater than or equal to 2. In actual implementation, in the same time period, the operating environment required by the applications deployed in display devices 1 to display devices n is provided by one user space. In different time periods, the operating environment required by the applications deployed in display devices 1 to display devices n can be provided by different user spaces. For example, in time period 1, the operating environment required by the applications deployed in display devices 1 to display devices n is provided by user space 1, and in time period 2, the operating environment required by the applications deployed in display devices 1 to display devices n is provided by user space n'. 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 operating environment required by the applications deployed in display devices 1 to display devices n can be provided by at least two user spaces. For example, the operating environment required by the applications deployed in display device 1 is provided by user space 1, and the operating environment required by the applications deployed in display devices 2 to display devices n is provided by user space n'.

[0082] In actual implementation, in order to protect the privacy security of different users in the same user space, the embodiment of the present application designs a data reading and writing architecture. Figure 6 Provide a detailed introduction.

[0083] Figure 6 Schematic diagram of the data storage architecture provided by the embodiment of the present application is shown. Figure 6As shown, 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, and the access path management unit may include multiple access path units, each of which is associated with a system account. For example, when system accounts a to N are all associated with the same user space (for example, system accounts a to N are all registered in the user space, or have all logged into the vehicle system under the user space), the access path management unit may include access path units associated with system accounts a to N, for example, system account a access path unit, system account N access path unit, etc. More specifically, multiple applications can be logged in under system account a, and the multiple applications include applications 1 to m, and applications 1 to m need to read and write data through the access path management unit. For example, at least one application among applications 1 to m stores pictures 11, 21, 31, and video 111 in the data sandbox via the access path unit of system account a. More specifically, when at least one of applications 1 to m stores data, a reference associated with the data is created (e.g., a reference to picture 11, a reference to picture 21, a reference to picture 31, a reference to video 111), and the reference is stored in the access path unit of system account a. The 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 the data. For example, when application m requests to read video 111 in the data sandbox, it needs to read video 111 through the video 111 reference stored in the access path unit of system account a.

[0084] In some implementations, applications 1 to m are privacy-critical applications. In addition to applications 1 to m, multiple applications logged in under system account a may also include at least one equity-sharing application. When at least one equity-sharing application reads and writes data, it may not go through the access path management unit.

[0085] For the specific implementation of applications 1'-m' under system account N reading data from the data sandbox and storing data in the data sandbox, please refer to the relevant description of applications 1-m reading and writing data, which will not be repeated here.

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

[0087] In actual implementation, the data reference stored in the aforementioned access path unit can be in the form of a field, which can include a system account name. For example, when an application m' running under a system account N stores data a in a data storage area, a "system account N" field is added to the data storage path (or data reference), and a more specific data storage path can be: "system account N-application m'-data a". When an application 1' running under a system account N reads data a from the data storage area, a "system account N" field is added to the data reading path, and a more specific data reading path can 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, and this field is not perceived by the application. When obtaining a data access request from an application, the public data service unit 440 determines whether to respond to the data access request of the application based on which system account the application is running under and whether the application needs to read and 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 going through the access path unit, as well as applications running under other system accounts, cannot read data stored by applications 1'-m' running under system account N.

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

[0089] It should also be noted that the privacy-critical applications and rights-sharing applications involved in this application are divided according to the data privacy requirements of the application. Among them, privacy-critical applications can also be called avatar applications, and rights-sharing applications can also be called instance applications. More specifically, privacy-critical applications refer to applications with data isolation requirements. For example, users do not want the 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 privacy-critical applications can also include e-commerce applications, map navigation applications, etc. The rights-sharing applications involved in this application refer to applications that do not require data isolation. For example, the data associated with such applications can be accessed or obtained by other users, such as weather applications; or rights-sharing applications can also be applications that require data sharing. For example, for an application, multiple system accounts can share the rights of the same application account, such as audio and video applications. Exemplarily, 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. In addition, for privacy-critical applications, when the same application is deployed on multiple display screens, applications on different display screens need to be logged in through different application accounts during the same time period; for rights-sharing applications, when the same application is deployed on multiple display screens, applications deployed on multiple display screens can be logged in through the same application account during the same time period. In other words, the rights and interests of an application account can be shared by applications on multiple display screens during the same time period.

[0090] In actual implementation, the system can set the specific type of application as either a privacy-critical application or a rights-sharing application by default, such as setting social applications as privacy-critical applications and audio and video applications as rights-sharing applications by default. Alternatively, for each application, users can be provided with installation packages for privacy-critical applications and rights-sharing applications, allowing them to choose which type of application to deploy in the vehicle system.

[0091] Combination of the above Figures 1 to 6 A schematic diagram of the system architecture provided by the embodiment of the present application is introduced in detail, and the control method provided by the embodiment of the present application is introduced in detail below.

[0092] Figure 7 A schematic flow chart of the control method provided by the embodiment of the present application is shown. Figure 4 The system shown in FIG. 1 is executed, wherein the user management unit, the application management unit group, the user center service unit, and the public data service unit can be respectively a user management unit 410 under a user space, at least one application management unit 420, a user center service unit 430, and a public data service unit 440. The method may include the following steps:

[0093] S711, the user management unit obtains user authority information 1.

[0094] In one example, when a primary user logs in, the user management unit obtains user authority information 1 in response to user settings.

[0095] In another example, the user management unit obtains user permission information 1 from a vehicle owner application deployed in an electronic device associated with the vehicle. The vehicle owner application may be an application that provides vehicle control to the vehicle owner and / or an application that provides the vehicle owner with services such as obtaining information about the vehicle's status. The electronic device and the vehicle may be associated with each other, including: the electronic device and the vehicle are logged in using the same account; or the electronic device and the vehicle are logged in using different accounts but both are authorized users of the vehicle; or the electronic device is authorized by the vehicle's authorized user, thereby establishing an association between the vehicle and the electronic device.

[0096] For example, the primary user can be the aforementioned vehicle owner system account; user permission information 1 may include the permissions of each of the multiple system accounts. The multiple system accounts may include one or more authorized system accounts and one or more guest system accounts. The specific permissions of each system account can be found in the description of the previous embodiment and will not be repeated here.

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

[0098] S712, the user management unit sends user authority information 1 to the user center service unit.

[0099] S713: The user center service unit performs user authority processing.

[0100] Exemplarily, 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 in the at least one application and the system account. The at least one application may include one or more applications that can access the data storage area under the system account.

[0101] S714, the user center service unit sends the user authority information 2 to the public data service unit.

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

[0103] 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 in the public data service unit requests to access the data storage area, the public data service unit rejects its request to access the data storage area.

[0104] In some other implementations, at least one application includes a privacy-critical application. The public data service unit establishes an access path unit for the system account based on the system account associated with the privacy-critical application. The privacy-critical application running under the system account can subsequently read and write data in the data storage area through the access path unit. For a more specific implementation of the privacy-critical application reading and writing data in the data storage area, please refer to the aforementioned Figure 6 The description of the corresponding parts will not be repeated here.

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

[0106] For example, system account A can be the vehicle owner's system account, or 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 system account A can be the aforementioned system account 1 or system account 2.

[0107] Login instruction 1 is associated with system account A, which can be understood as: login instruction 1 requests to use system account A to log in to the vehicle system, or login instruction 1 requests to use system account A to log in to the vehicle system through display device A. Exemplarily, display device A can be any one of the aforementioned display devices 1 to display device n.

[0108] S722: The user management unit sends a login request for system account A to the user center service unit.

[0109] S723, the user center service unit executes the system account A login process.

[0110] For example, the user center service unit uses system account A at display device A to log in to the vehicle system.

[0111] S724, the application management unit group logs in to application 1.

[0112] Exemplarily, the application management unit group controls application account 1 to log in to application 1 in response to a user operation.

[0113] S725: The application management unit group sends a login notification of application 1 to the user center service unit.

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

[0115] S726 , the user center service unit performs association processing between application 1 and system account A.

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

[0117] In some implementations, if application 1 is a privacy-critical application, the user-centric service unit performs association processing between application 1 and system account A upon receiving a login notification of application 1.

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

[0119] It should be noted that S724 to S726 may be the operations performed when system account A logs into application 1 for the first time; alternatively, S724 to S726 may be the operations performed when application account 1 logs into application 1 for the first time under system account A. For example, before executing S724, application 1 was already associated with system account A, but application 1 was associated with system account A when application account 2 logged in. After executing S724 to S726, the association between application 1 and system account A is updated to: when system account A logs in, application account 1 logs in to application 1.

[0120] In some implementations, after executing S723 , S727 and S728 are executed. For example, if the association process between system account A and the application has been performed in the early stage, after executing S723 , S727 and S728 are executed.

[0121] S727, the user center service unit sends a system account A login notification to the application management unit group.

[0122] For example, the system account A login notification indicates that the system account A logs into the vehicle system through the display device A.

[0123] S728, the application management unit group logs into the application group a associated with the system account A.

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

[0125] For example, at least one application includes Application 3, and Application 3 is a rights-sharing application. That is, when display device A deploys Application 3, other display devices in the vehicle can deploy Application 3', Application 3", etc. When an application account is used to log in to any one of Application 3, Application 3', and Application 3", the remaining two applications are also logged in. In other words, Application Group A may also include Application 3', Application 3", and other applications associated with Application 3 deployed on other display devices.

[0126] It should be noted that the applications deployed in different display devices may be different. Therefore, when system account A logs in to the vehicle system through different display devices, the applications logged in with system account A may be different.

[0127] In some implementations, S724 through S726 may also be executed after S727 and S728. For example, if application group a in S728 includes application 1, then during S728, application account 2 is controlled to log into application 1. Furthermore, after application account 1 is controlled to log out of application 1 in response to a user operation, S724 through S726 are executed. Thus, the next time system account A logs in, application account 1 is used to log into application 1, which is associated with system account A.

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

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

[0130] S733, the user center service unit executes the system account A logout process.

[0131] Exemplarily, the user center service unit logs out of system account A in display device A.

[0132] S734, the user center service unit sends a logout notification of system account A to the application management unit group.

[0133] S735: The application management unit group logs out of at least one application in application group a.

[0134] In some implementations, all applications in application group a are controlled to log out.

[0135] In some other implementations, application group a includes at least one safety-critical application, which refers to an application that affects driving safety, such as a navigation application or an intelligent driving application. Among them, the intelligent driving application is an application used to control intelligent driving functions, wherein the intelligent driving functions may include but are not limited to the following functions that affect driving safety: automatic parking assist (APA), automatic valet parking (AVP), adaptive cruise control (ACC), lane cruise control (LCC), navigation cruise assist (NCA), front vehicle collision warning, lane departure warning, lane keeping assist, and rear vehicle collision avoidance warning. Among them, the NCA function refers to the function of controlling the vehicle to drive to the destination according to the navigation route, and being able to control the vehicle to pass through intersections, change lanes, and change speeds according to road information such as traffic lights.

[0136] In one example, if the application management unit receives a logout notification from system account A while the vehicle is in drive or reverse, the application management unit controls the logout of all applications in application group A except for the smart driving application. Furthermore, when the vehicle is in park, the smart driving application is also controlled to log out.

[0137] In another example, if an intelligent driving application is running and the application management unit group receives a logout notification from system account A, the application management unit group controls the logout of all applications in application group A except the running intelligent driving application. Furthermore, when the intelligent driving application exits the running state, the intelligent driving application is controlled to log out.

[0138] In some further implementations, if application group a includes at least one equity-sharing application, upon receiving a logout notification from system account A, the application management unit group controls the logout of all applications in application group a except for the at least one equity-sharing application. For example, if the at least one equity-sharing application includes the aforementioned application 3, application 3', and application 3", the application management unit group controls the logout of all applications in application group a except for application 3, application 3', and application 3".

[0139] In some implementations, after controlling at least one application in application group a to log out, at least one application in application group a may also be controlled to exit.

[0140] In actual implementation, when the same system account logs in to the vehicle system through different display devices respectively, you can first control the system account to log out of the vehicle system when the system account logs in to the vehicle system through the latter display device, and then control the system account to log in to the vehicle system; or in the above process, you can also keep the system account logged in to the vehicle system continuously.

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

[0142] Here, Application 2 associated with System Account B can be understood as: Application 2 is 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. For example, Display Device B can be any one of Display Devices 1 to n described above.

[0143] Exemplarily, the data access request includes a request to read data in the data storage area and / or a request to store data in the data storage area.

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

[0145] Exemplarily, the public data service unit determines whether application 2 associated with system account B has permission to access the data storage area. When determining 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.

[0146] In some implementations, when multiple system accounts log in to the vehicle system through display device B, they can all use application 2. However, the permissions of application 2 associated with different system accounts within the multiple system accounts vary. For example, application 2 associated with system account B and system account C both have permission to access 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.

[0147] S743: When the authentication is successful, the public data service unit sends the data reading and writing results to the application management unit group.

[0148] In one example, application 2 associated with system account B needs to access the data storage area through the access path unit, so the public data service unit stores data requested by application 2 to store and / or reads data requested by application 2 to read via the access path unit.

[0149] In another example, application 2 associated with system account B does not need to go through the access path unit to access the data storage area. The public data service unit then 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.

[0150] S744: When the authentication fails, the public data service unit sends a data access failure notification to the application management unit group.

[0151] Exemplarily, the data access failure notification is used to notify a failure in storing data in the data storage area, or to notify a failure in reading data from the data storage area.

[0152] 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 simultaneously with any group of S721 to S723, S724 to S726, S727 to S728, or S731 to S735, or can be executed before any group of S721 to S723, S724 to S726, S727 to S728, or S731 to S735. In addition, S741 to S744 can be executed simultaneously with S711 to S714, or S741 to S744 can be executed before S711 to S714.

[0153] It should also be noted that the application login or logout involved in this application refers to: the application account logging in or out of the application; the vehicle system login or logout involved in this application refers to: the system account logging in or out of the vehicle system. In addition, application logout and application exit are not the same. Application logout refers to the application account logging in to the application logout, and application exit refers to the end or exit of all application-related processes, such as stopping the background running of the application. In other words, after the application is logged out, the application can exit or not exit. When the application does not exit, the display screen can display the application's running interface, or the display screen can not display the application's running interface. At this time, the application can be in the background running state.

[0154] In order to facilitate understanding of the control method provided in the embodiment of the present application, the following Figures 8 to 14 The application scenarios and graphical user interface (GUI) involved in this application are introduced in detail. Figures 8 to 14 The processing actions (such as control, response, etc.) or steps involved can be Figure 1 The computing platform 150 shown may be executed, or it may be executed by the aforementioned control system, for example, it may be executed by the user center service unit 430.

[0155] Figure 8 and Figure 9An example of a GUI provided by an embodiment of the present application is shown.

[0156] like Figure 8 As shown in (a), user A is located in the main driving 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 follows: Figure 8 As shown in (a) in the figure, it includes a content display area 810 and a function bar 820. Exemplarily, the content display area 810 includes: icons of multiple applications, each application icon is used to enable an application; a login control 801 (indicating that it is in the logged-in state); and a Bluetooth function icon, a Wi-Fi function icon, and a cellular network signal icon, which are respectively used to indicate that the vehicle's Bluetooth is turned on and / or connected, the Wi-Fi is turned on, and the cellular network signal strength. The function bar 820 includes a homepage icon, seat controls, air conditioning controls, and volume controls, which are respectively used to control the content display area 810 to display the homepage, control the seat ventilation switch and / or adjust the seat ventilation air volume, control the air conditioning switch and / or adjust the air conditioning temperature and heating and cooling status, adjust the air circulation status in the vehicle, and adjust the volume of the sound device.

[0157] In such Figure 8 The tab shown in (a) includes icons for applications such as Settings, Navigation, Camera, Browser, Weather, HD Map, App Store, Social Apps, Stocks, and Videos.

[0158] like Figure 8 As shown in (b), user B is located in the right area of ​​the second row of the vehicle cabin. At this time, the content displayed on the display screen 204 (i.e., the right entertainment screen of the second row) can be as follows: Figure 8 As shown in (b) of FIG, the content display area 830 is included. Exemplarily, the content display area 830 includes: multiple application icons, each application icon is used to enable an application; a login control 801 (indicating a non-logged-in state); and a Bluetooth function icon, a Wi-Fi function icon, and a cellular network signal icon, which are used to indicate the vehicle's Bluetooth on and / or connection status, Wi-Fi on status, and cellular network signal strength, respectively.

[0159] In such Figure 8 The tab shown in (b) includes icons for applications such as Settings, Navigation, Camera, Browser, Weather, HD Map, App Store, Social Apps, Stocks, and Videos.

[0160] The social applications deployed on the above display screen 201 and the display screen 204 can be clone-type applications (or, the installation type of the social application is privacy-critical), the social application deployed on the display screen 201 can be the main application corresponding to the social application, and the social application deployed on the display screen 204 can be the clone application corresponding to the social application. When the main application is uninstalled, all clone applications are uninstalled together, and the uninstallation of the clone application does not affect the normal use of the main application. The main application may include the user data and the main program segment of the main application, and the main program segment includes the program associated with the application startup. The clone application includes the user data and clone application of the clone application, and the clone application may include programs related to the ability to use the main application. For the user, the experience when using the main application and the clone application is consistent.

[0161] When detecting that the user long presses the icon 801 of the social application, the vehicle can display the following information on the display screen 204: Figure 9 The GUI shown in (a) in FIG.

[0162] Figure 9 An example of a GUI provided by an embodiment of the present application is shown.

[0163] like Figure 9 As shown in (a) of FIG, in response to the user long pressing the icon 801, the vehicle can display a function bar 901 through the display screen 204. The function bar 901 includes multiple functions, such as uninstalling, changing the application type, sharing, and others. When the user clicks the uninstall function 902, the vehicle can display the following through the display screen 204: Figure 9 The GUI shown in (b) in FIG.

[0164] like Figure 9 As shown in (b) in the figure, in response to the user clicking the uninstall function 902, the vehicle can determine whether the social application deployed on the display screen 204 is the main application. When it is determined that the social application deployed on the display screen 204 is not the main application (or, the social application deployed on the display screen 204 is a clone application), the vehicle can determine whether the display screen 204 is the only screen in the cockpit where the social application is deployed. Since the display screen 204 is not the only screen in the cockpit where the social application is deployed, the vehicle can uninstall the clone application corresponding to the social application deployed on the display screen 204 and delete the icon 801. At the same time, the vehicle can also control the display screen 204 to display a prompt message "The clone application of the social application deployed on the second row right entertainment screen has been uninstalled. You can also experience the social application on the central control screen."

[0165] In this embodiment of the present application, when a main application corresponding to a social application is deployed on display screen 201 and a clone application corresponding to the social application is deployed on display screen 204, if the vehicle detects that the user wishes to uninstall the social application on display screen 204, the vehicle can execute the uninstallation operation on the clone application, delete the icon 801, and do not uninstall the main application. In this way, even if the user uninstalls the clone application corresponding to the social application on display screen 204, the user can still use the main application of the social application on the central control screen.

[0166] Figure 10 An example of a GUI provided by an embodiment of the present application is shown.

[0167] like Figure 10 As shown in (a) of FIG, in response to a user's long press operation on the icon of the social application deployed on the display screen 201, the vehicle can display a function bar 1001 on the display screen 201. The function bar 1001 includes multiple functions, such as uninstalling, changing the application type, sharing, and others. When the user clicks on the uninstall function 1002, the vehicle can display the following on the display screen 201: Figure 10 The GUI shown in (b) in FIG.

[0168] like Figure 10 As shown in (b), in response to the user clicking the uninstall function 1002, the vehicle can determine whether the social application deployed on the display screen 201 is the main application. When it is determined that the social application deployed on the display screen 201 is the main application, the vehicle can determine whether there are any clone applications on the display screens in the cockpit that have not been uninstalled (or, determine whether the display screen 201 is the only display screen in the cockpit where the social application is deployed). Since the clone applications on other display screens in the cockpit have all been uninstalled (or, the display screen 201 is the only screen in the cockpit where the social application is deployed), the vehicle can uninstall the main application corresponding to the social application deployed on the display screen 201 and delete the icon of the social application. At the same time, the vehicle can also control the display screen 201 to display the prompt message "The social application has been completely uninstalled."

[0169] In the embodiment of the present application, when only the display screen 201 in the cockpit is deployed with a social application, if the vehicle detects that the user has uninstalled the social application on the display screen 201, the vehicle can uninstall the main application.

[0170] Figure 11 An example of a GUI provided by an embodiment of the present application is shown.

[0171] like Figure 11 As shown in (a), the tab currently displayed on the display screen 201 includes icons of applications such as settings, navigation, camera, browser, weather, high-precision map, application market, social applications, stocks and videos.

[0172] like Figure 11 As shown in (b), the tab currently displayed on the display screen 204 includes icons of applications such as settings, navigation, camera, browser, weather, high-precision map, application market, social applications, stocks and videos.

[0173] The video applications deployed on the above display screen 201 and display screen 204 can be instance-type applications. Unlike the above-mentioned clone-type applications, instance-type applications do not distinguish between main applications and clone applications. Regardless of the screens on which the instance-type application is deployed, there can be only one application entity (or main application) in the vehicle, and the icons of the instance-type application are displayed on multiple display screens. When the main application is uninstalled, the instance-type application is completely uninstalled. After the vehicle installs the instance-type application, the icons of the instance-type application are displayed on display screen 201 and display screen 204. For users, the experience of using instance-type applications on different screens is consistent. For example, the instance-type application is a video application. After user A's car account is logged in on display screen 201, the account of the video application can be automatically logged in on display screen 201 and display screen 204.

[0174] When a long press operation of the user on the icon 1101 of the video application on the display screen 204 is detected, the display screen 204 may display the following Figure 11 The GUI shown in (c) in FIG.

[0175] like Figure 11 As shown in (c) of FIG, in response to the user's long press operation on the video application icon 1101 on the display screen 204, the vehicle can display a function bar 1102 on the display screen 204. The function bar 1102 includes multiple functions, such as uninstalling, changing the application type, sharing, and others. When the user clicks on the uninstall function 1103, the vehicle can display the following on the display screen 204: Figure 11 The GUI shown in (d) in FIG.

[0176] like Figure 11 As shown in (d) of FIG, in response to the user clicking on uninstall function 1103, the vehicle can determine whether display screen 204 is the only display in the cabin with the video application icon deployed. If it is determined that display screen 204 is not the only display in the cabin with the video application icon deployed, the vehicle can delete icon 1101 and not uninstall the video application. Simultaneously, the vehicle can control display screen 204 to display the prompt message "The video application icon on the second-row right entertainment screen has been deleted. You can still use the video application on the center console."

[0177] In an embodiment of the present application, when performing an uninstallation operation on an instance-type application, if the instance-type application icon currently displayed on the display screen is not the last instance-type application icon, the vehicle may not perform the uninstallation operation on the application entity (or main application) of the instance-type application, but may delete the instance-type application icon displayed on the display screen. In this way, the user can still use the instance-type application on other display screens that display the instance-type application icon.

[0178] Figure 12 An example of a GUI provided by an embodiment of the present application is shown.

[0179] like Figure 12 As shown in (a) of FIG, in response to a user's long press operation on the video application icon 1201 on the display screen 201, the vehicle can display a function bar 1202 on the display screen 201. The function bar 1202 includes multiple functions, such as uninstalling, changing the application type, sharing, and others. When the user clicks on the uninstall function 1203, the vehicle can display the following on the display screen 201: Figure 12 The GUI shown in (b) in FIG.

[0180] like Figure 12 As shown in (b) of FIG, in response to the user clicking on uninstall function 1203, the vehicle can determine whether display screen 201 is the only display screen in the cockpit with the video application icon deployed. If it is determined that display screen 201 is the only display screen in the cockpit with the video application icon deployed, the vehicle can delete icon 1201 and uninstall the video application. At the same time, the vehicle can also control display screen 201 to display the prompt message "Video application uninstalled".

[0181] In an embodiment of the present application, when performing an uninstall operation on an instance-type application, if the icon of the instance-type application currently displayed on the display screen is the icon of the last instance-type application, then the vehicle can perform an uninstall operation on the application entity (or main application) of the instance-type application.

[0182] Combination of the above Figures 8 to 12 This describes the process of uninstalling applications on each display. Figure 13 and Figure 14 Taking the GUI shown as an example, the process of quickly uninstalling an application is described.

[0183] Figure 13 An example of a GUI provided by an embodiment of the present application is shown.

[0184] like Figure 13As shown in (a) of FIG, in response to a user's long press operation on the icon of the video application on the display screen 204, the vehicle can display a function bar 1301 on the display screen 204. The function bar 1301 includes multiple functions, such as uninstalling, changing the application type, sharing, and others. When the user clicks on the uninstall function 1302, the vehicle can display the following on the display screen 204: Figure 13 The GUI shown in (b) in FIG.

[0185] like Figure 13 As shown in (b), in response to the user clicking the uninstall function 1302, the vehicle can display a prompt box 1303 through the display screen 204, and the prompt box 1303 includes the prompt information "Video applications are detected to be deployed on the central control screen and the second row right entertainment screen, please select", a control 1304 and a control 1305 for uninstalling the video application. The control 1304 is a control corresponding to the icon of the video application on the second row right entertainment screen.

[0186] For example, upon detecting a user clicking on the control 1304 , the vehicle may delete the icon of the video application displayed on the display screen 204 .

[0187] Exemplarily, when detecting the operation of the user clicking the control 1305, the vehicle can execute the uninstallation of the video application. After the uninstallation of the video application is completed, the icons on the display screen 201 and the display screen 204 are all deleted.

[0188] Figure 14 An example of a GUI provided by an embodiment of the present application is shown.

[0189] like Figure 14 As shown in (a) of FIG, in response to a user's long press operation on the icon of the video application on the display screen 204, the vehicle can display a function bar 1401 on the display screen 204. The function bar 1401 includes multiple functions, such as uninstalling, changing the application type, sharing, and others. When the user clicks on the uninstall function 1402, the vehicle can display the following on the display screen 204: Figure 14 The GUI shown in (b) in FIG.

[0190] above Figure 14 The number in the lower left corner of the application icon shown in (a) above can represent the number of displays in the cockpit where the application is deployed. For example, taking a social application as an example, since the social application is deployed on both display 201 and display 204, the number "2" is displayed in the lower left corner of the social application icon displayed on display 204. Similarly, the number "2" is displayed in the lower left corner of the social application icon displayed on display 201.

[0191] like Figure 14As shown in (b), in response to the user clicking the uninstall function 1402, the vehicle can display a prompt box 1403 through the display screen 204, and the prompt box 1403 includes the prompt information "Video applications are detected to be deployed on 2 screens in the cabin, please select the screen to be uninstalled" and highlights the controls corresponding to the central control screen and the second row right entertainment screen where the video application is deployed.

[0192] For example, when it is detected that the user clicks on the control corresponding to the central control screen and clicks to confirm the control, the vehicle can delete the icon of the video application displayed on the display screen 201 and does not perform an uninstall operation on the video application.

[0193] For example, when it is detected that the user clicks on the control corresponding to the second row right entertainment screen and clicks on the confirmation control, the vehicle can delete the icon of the video application displayed on the display screen 204 and does not perform the uninstallation operation on the video application.

[0194] For example, when the user clicks on the corresponding controls of the central control screen and the second row right entertainment screen and clicks on the confirmation control, the vehicle can perform an uninstall operation on the video application. After the video application is uninstalled, the icons on the display screen 201 and the display screen 204 will be deleted.

[0195] Figure 15 A schematic flow chart of an application uninstallation method 1500 provided in an embodiment of the present application is shown. The method 1500 may be executed by the vehicle 100; or, the method 1500 may be executed by the computing platform 150; or, the method 1500 may be executed by a processor, chip, or circuit in the computing platform 150. The method 1500 includes:

[0196] S1510 , obtaining a first uninstall instruction from a user for a first application on a first screen, where the first application is deployed on multiple screens in a cockpit, the multiple screens including the first screen.

[0197] For example, Figure 9 As shown in (a) in FIG, the first uninstall instruction may be an operation in which the user clicks on the control 902 .

[0198] For example, Figure 11 As shown in (c) in FIG, the first uninstall instruction may be an operation in which the user clicks on the control 1103 .

[0199] S1520. In response to the first uninstall instruction, perform an uninstall operation according to the type of the first application, where the type of the first application includes a clone type or an instance type.

[0200] The description of the above clone-type application or instance-type application can refer to the above embodiments, and for the sake of brevity, it will not be repeated here.

[0201] Optionally, the method 1500 further includes: determining the type of the first application based on the installation type of the first application.

[0202] Exemplarily, if the installation type of the first application is privacy-critical, then the type of the first application may be clone type.

[0203] For example, if the installation type of the first application is a benefit-sharing type, then the type of the first application may be an instance type.

[0204] Optionally, performing an uninstall operation based on the type of the first application includes: in response to the first uninstall instruction, when the type of the first application is an instance type, deleting the icon of the first application on the first screen and not performing an uninstall operation on the first application.

[0205] For example, the first screen may be as follows: Figure 11 In the display screen 204 shown in (c) and (d), in response to the user clicking the control 1103, the icon of the video application displayed on the display screen 204 can be deleted without performing the uninstallation operation of the video application.

[0206] Optionally, the method 1500 further includes: in response to obtaining a second uninstall instruction from the user for the first application on the second screen, performing an uninstall operation on the first application, where the second screen is the only screen among the multiple screens on which the first application is deployed.

[0207] For example, the second screen may be Figure 12 In the display screen 201 shown in (a) and (b) of FIG, the second uninstall instruction may be an operation in which the user clicks on the control 1203. In response to the operation in which the user clicks on the control 1203, an uninstall operation of the video application may be performed.

[0208] Optionally, in response to the first uninstall instruction, the icon of the first application on the first screen is deleted and the uninstall operation of the first application is not performed, including: when the type of the first application is a clone type, the first clone application corresponding to the first application is deployed on the first screen, and the main application corresponding to the first application is deployed on the third screen, in response to the first uninstall instruction, the icon of the first application on the first screen is deleted and the first clone application is uninstalled.

[0209] For example, the first screen may be as follows: Figure 9 The display screen 204 shown in (a) and (b) in FIG. 1 , the third screen may be as follows Figure 8 In the display screen 201 shown in (b), the first application may be a social application. In response to the user clicking the control 902, the icon of the social application displayed on the display screen 204 may be deleted and the clone application corresponding to the social application deployed on the display screen 204 may be uninstalled.

[0210] Optionally, in response to the first uninstall instruction, the icon of the first application on the first screen is deleted and the uninstall operation of the first application is not performed. The method also includes: when the first application is a clone application, the main application corresponding to the first application is deployed on the first screen and the second clone application corresponding to the first application is deployed on the fourth screen, in response to the first uninstall instruction, the icon of the first application on the first screen is deleted.

[0211] For example, the first screen may be as follows: Figure 8 The display screen 201 shown in (a) in FIG. 1 may be as follows: Figure 8 In the display screen 204 shown in (b) of FIG, the first application may be a social application. In response to a user's uninstall instruction for the social application displayed on the display screen 201, the icon of the social application displayed on the display screen 201 may be deleted without performing an uninstall operation on the main application and the clone application of the social application.

[0212] Optionally, the method 1500 further includes: obtaining a third uninstall instruction from the user for the first application on the fifth screen; and uninstalling the main application in response to the third uninstall instruction when the fifth screen is the only screen among the multiple screens on which the icon of the first application is deployed.

[0213] Exemplarily, the fifth screen may be as follows Figure 10 In the display screen 201 shown in (a) and (b), the first application may be a social application, and the third uninstall instruction may be an operation of the user clicking on the control 1002. In response to the user clicking on the control 1002, the vehicle may execute an uninstall operation on the main application of the social application.

[0214] Optionally, in response to the first uninstall instruction, an uninstall operation is performed according to the type of the first application, including: in response to the first uninstall instruction, controlling the first screen to display a first interface, the first interface including prompt information, the prompt information being used to prompt the user to delete the icon of the first application deployed on the first screen or uninstall the first application; receiving the first instruction from the user on the first interface; and performing the uninstall operation according to the first instruction.

[0215] For example, Figure 13 As shown, the first interface can be as follows Figure 13 The GUI shown in (b) includes a prompt message "Video applications have been detected deployed on the central control screen and the second row right entertainment screen, please select", control 1304 and control 1305.

[0216] Exemplarily, the first instruction may be an operation of the user clicking on the control 1304. In response to the operation of the user clicking on the control 1304, the vehicle may delete the icon of the video application displayed on the display screen 204.

[0217] For example, the second instruction may be a user clicking on control 1305. In response to the user clicking on control 1305, the vehicle may uninstall the video application. After the video application is uninstalled, the icons on display screen 201 and display screen 204 are deleted.

[0218] Optionally, in response to the first uninstall instruction, an uninstall operation is performed according to the type of the first application, including: in response to the first uninstall instruction, controlling the first screen to display a second interface, the second interface including information of the multiple screens; receiving a second instruction from the user on the first interface, the second instruction indicating at least one of the multiple screens; and performing the uninstall operation according to the second instruction.

[0219] For example, the second interface may be as follows: Figure 14 The GUI shown in (b) includes a prompt message "Video applications have been deployed on two screens in the cabin. Please select the screen you want to uninstall" and highlights the controls corresponding to the central control screen and the second-row right entertainment screen where the video application is deployed.

[0220] Exemplarily, the second instruction may be that the user clicks on a control corresponding to the central control screen and clicks to confirm the control. In response to the user clicking on the control corresponding to the central control screen and clicking to confirm the control, the vehicle may delete the icon of the video application displayed on the display screen 201 and does not perform an uninstall operation on the video application.

[0221] For example, the second instruction may be that the user clicks the control corresponding to the second row right entertainment screen and clicks the confirmation control. In response to the user clicking the control corresponding to the second row right entertainment screen and clicking the confirmation control, the vehicle may delete the icon of the video application displayed on the display screen 204 and does not perform the uninstallation operation on the video application.

[0222] For example, the second instruction may be a user clicking on the controls corresponding to the central control screen and the second-row right entertainment screen and then clicking to confirm the control. In response to the user clicking on the controls corresponding to the central control screen and the second-row right entertainment screen and clicking to confirm the control, the vehicle may execute an uninstallation operation on the video application. After the video application is uninstalled, the icons on display screens 201 and 204 are deleted.

[0223] Figure 16 A schematic flow chart of an application uninstallation method 1600 provided in an embodiment of the present application is shown. The method 1600 includes:

[0224] S1601: Detecting a user operation of uninstalling application 1 deployed on in-cabin display screen 1.

[0225] S1602, determine whether application 1 is a clone-type application.

[0226] Exemplarily, if application 1 is a clone-type application, S1603 may be executed; otherwise, S1609 may be executed.

[0227] S1603 , determining whether the application 1 deployed on the display screen 1 is the main application corresponding to the application 1 .

[0228] Exemplarily, if the application 1 deployed on the display screen 1 is the main application corresponding to the application 1, execute S1604; otherwise, execute S1605.

[0229] S1604: Determine whether there is any clone application corresponding to application 1 that has not been uninstalled.

[0230] Exemplarily, if there is a clone application corresponding to application 1 that has not been uninstalled, execute S1606; otherwise, execute S1607.

[0231] S1605 , determining whether the icon of application 1 deployed on display screen 1 is the last icon of application 1 .

[0232] Exemplarily, if the icon of application 1 deployed on display screen 1 is the last icon, execute S1607; otherwise, execute S1608.

[0233] S1606 , delete the icon of application 1 currently displayed on display screen 1 .

[0234] For example, the display screen 1 may be Figure 8 In the display screen 201 shown in (a) of FIG, the first application may be a social application. In response to a user's uninstall instruction for the social application displayed on display screen 201, when it is determined that the main application corresponding to the social application is deployed on display screen 1 and the clone application corresponding to the social application is deployed on display screen 204, the icon of the social application displayed on display screen 201 may be deleted.

[0235] S1607: Uninstall the main application corresponding to application 1.

[0236] For example, the display screen 1 may be Figure 10 In the display screen 201 shown in (a) and (b) of FIG, the first application may be a social application. In response to the user clicking control 1002, if it is determined that the main application corresponding to the social application is deployed on display screen 1 and the clone applications corresponding to the social application are not deployed on other displays in the cockpit (or the clone applications of the social application have all been uninstalled), the main application corresponding to the social application may be uninstalled.

[0237] S1608, uninstall the clone application corresponding to application 1.

[0238] For example, the display screen 1 may be Figure 9 In the display screen 204 shown in (a) and (b) of FIG, the first application may be a social application. In response to the user clicking control 902, if it is determined that a clone application corresponding to the social application is deployed on the display screen 204 and the icon of the social application deployed on the display screen 204 is not the last social application icon, the clone application corresponding to the social application deployed on the display screen 204 may be uninstalled.

[0239] S1609: Determine whether application 1 is an instance-type application.

[0240] Exemplarily, if application 1 is an instance-type application, S1610 may be executed; otherwise, S1611 may be executed.

[0241] S1610 , determining whether the icon of application 1 deployed on display screen 1 is the last icon of application 1 .

[0242] Exemplarily, if the icon of application 1 deployed on display screen 1 is the last icon, execute S1612; otherwise, execute S1613.

[0243] S1611, uninstall application 1.

[0244] For example, if application 1 is neither a clone-type application nor an instance-type application, then the uninstallation operation of application 1 can be performed.

[0245] S1612: Uninstall the main application corresponding to application 1.

[0246] Uninstalling the main application corresponding to application 1 in the above S1612 can also be understood as uninstalling the application entity corresponding to application 1.

[0247] For example, the display screen 1 may be Figure 12 In the display screen 201 shown in (a) and (b), the application 1 may be a video application. In response to the user clicking the control 1203, when it is determined that the icon of the video application deployed on the display screen 201 is the last video application icon, the video application may be uninstalled.

[0248] S1613: Delete the icon of application 1 currently displayed on display screen 1.

[0249] For example, the display screen 1 may be Figure 11In the display screen 204 shown in (c) and (d), the application 1 may be a video application. In response to the user clicking the control 1103, if it is determined that the icon of the video application deployed on the display screen 204 is not the last video application icon, the icon of the video application displayed on the display screen 204 may be deleted.

[0250] Figure 17 A schematic block diagram of an application uninstallation device 1700 provided in an embodiment of the present application is shown. Device 1700 includes: an acquisition unit 1710, configured to acquire a first uninstallation instruction from a user for a first application on a first screen, where the first application is deployed on multiple screens within a cockpit, including the first screen; and a processing unit 1720, configured to, in response to the first uninstallation instruction, perform an uninstallation operation based on the type of the first application, where the type of the first application includes either a clone type or an instance type.

[0251] Optionally, the processing unit 1720 is specifically configured to: in response to the first uninstall instruction, when the type of the first application is instance type, delete the icon of the first application on the first screen and do not perform an uninstall operation on the first application.

[0252] Optionally, the processing unit 1720 is further configured to perform an uninstall operation on the first application in response to obtaining a second uninstall instruction from the user for the first application on the second screen, where the second screen is the only screen among the multiple screens on which the first application is deployed.

[0253] Optionally, the processing unit 1720 is specifically used to: when the type of the first application is a clone type, a first clone application corresponding to the first application is deployed on the first screen, and a main application corresponding to the first application is deployed on the third screen, in response to the first uninstall instruction, delete the icon of the first application on the first screen and uninstall the first clone application.

[0254] Optionally, the processing unit 1720 is specifically used to: when the first application is a clone application, the main application corresponding to the first application is deployed on the first screen and the second clone application corresponding to the first application is deployed on the fourth screen, in response to the first uninstall instruction, delete the icon of the first application on the first screen.

[0255] Optionally, the acquisition unit 1710 is also used to obtain a third uninstall instruction from the user for the first application on the fifth screen; the processing unit 1720 is also used to uninstall the main application in response to the third uninstall instruction when the fifth screen is the only screen among the multiple screens on which the icon of the first application is deployed.

[0256] Optionally, the device 1700 also includes: a control unit, used to control the first screen to display a first interface in response to the first uninstall instruction, the first interface including prompt information, the prompt information being used to prompt the user to delete the icon of the first application deployed on the first screen or uninstall the first application; a receiving unit, used to receive the first instruction of the user on the first interface; the processing unit 1720, used to perform the uninstall operation according to the first instruction.

[0257] Optionally, the device 1700 also includes: a control unit, used to control the first screen to display a second interface in response to the first uninstall instruction, wherein the second interface includes information of the multiple screens; a receiving unit, used to receive a second instruction from the user on the first interface, wherein the second instruction indicates at least one of the multiple screens; and the processing unit 1720, used to perform an uninstall operation according to the second instruction.

[0258] It should be understood that the division of the various units in the above device is merely a division of logical functions. In actual implementation, they may be fully or partially integrated into a single physical entity, or they may be physically separated. Furthermore, the units in the device may be implemented in the form of a processor calling software; for example, the device includes a processor connected to a memory storing instructions, and the processor calls the instructions stored in the memory to implement any of the above methods or the functions of the various units in the device, where the processor is, for example, a general-purpose processor such as a CPU or a microprocessor, and the memory is a memory within the device or a memory external to the device. Alternatively, the units in the device may be implemented in the form of hardware circuits, and the functions of some or all of the units may be implemented through the design of the hardware circuits. The hardware circuits may be understood as one or more processors. For example, in one implementation, the hardware circuit is an ASIC, and the functions of some or all of the above units may be implemented through the design of the logical relationships between the components within the circuits. In another implementation, the hardware circuit may be implemented using a PLD, such as an FPGA, which may include a large number of logic gate circuits, and the connections between the logic gate circuits may be configured using a configuration file to implement the functions of some or all of the above units. All units of the above apparatus may be implemented entirely in the form of software called by a processor, or entirely in the form of hardware circuits, or partially in the form of software called by a processor and the rest in the form of hardware circuits.

[0259] In an embodiment of the present application, a processor is a circuit with the ability to process signals. In one implementation, the processor may be a circuit with the ability to read and execute instructions, such as a CPU, a microprocessor, a GPU, or a DSP. In another implementation, the processor may implement certain functions through the logical relationship of a hardware circuit, and the logical relationship of the hardware circuit may be fixed or reconfigurable, such as a hardware circuit implemented by an ASIC or PLD, such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document to implement the configuration of the hardware circuit can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units. In addition, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as an NPU, TPU, DPU, etc.

[0260] It can be seen that each unit in the above device can be one or more processors (or processing circuits) configured to implement the above method, such as: CPU, GPU, NPU, TPU, DPU, microprocessor, DSP, ASIC, FPGA, or a combination of at least two of these processor forms.

[0261] In addition, the various units in the above apparatus may be fully or partially integrated together, or may be implemented independently. In one implementation, these units are integrated together and implemented in the form of a system-on-chip (SoC). The SoC may include at least one processor for implementing any of the above methods or implementing the functions of the various units of the apparatus. The at least one processor may be of different types, for example, including a CPU and an FPGA, a CPU and an artificial intelligence processor, a CPU and a GPU, etc.

[0262] An embodiment of the present application also provides an application uninstallation device, which includes a processing unit and a storage unit, wherein the storage unit is used to store instructions, and the processing unit executes the instructions stored in the storage unit to enable the device to execute the method or steps executed in the above embodiment.

[0263] Alternatively, if the device is located in a vehicle, the processing unit may be Figure 1 Processors 151-15n are shown.

[0264] An embodiment of the present application also provides an application uninstallation system, which may include a computing platform and multiple screens, and the computing platform may include the above-mentioned application uninstallation device 1700.

[0265] An embodiment of the present application also provides a vehicle, which may include the above-mentioned application uninstallation device 1700 or application uninstallation system.

[0266] An embodiment of the present application further provides a computer program product, which includes: computer program code, which enables the computer to execute the method in the above embodiment when the computer program code is run on a computer.

[0267] An embodiment of the present application further provides a computer-readable medium, wherein the computer-readable medium stores a program code. When the computer program code runs on a computer, the computer executes the method in the above embodiment.

[0268] An embodiment of the present application further provides a chip, which includes a circuit, and the circuit is used to execute the noise reduction method in the above embodiment.

[0269] During implementation, each step of the above method can be completed by an integrated logic circuit of the hardware in the processor or by instructions in the form of software. The method disclosed in conjunction with the embodiments of the present application can be directly embodied as being executed by a hardware processor, or can be executed by a combination of hardware and software modules in the processor. The software module can be located in a storage medium mature in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, or a power-on erasable programmable memory, a register, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware. To avoid repetition, it will not be described in detail here.

[0270] It should be understood that in the embodiment of the present application, the memory may include a read-only memory and a random access memory, and provide instructions and data to the processor.

[0271] It should also be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0272] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0273] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0274] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0275] The units described as separate components may or may not be physically separate, and 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 these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0276] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0277] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0278] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present application should be covered and fall within the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. A method for uninstalling an application, characterized in that: include: Obtaining a first uninstall instruction from a user for a first application on a first screen, where the first application is deployed on multiple screens in a cockpit, the multiple screens including the first screen; In response to the first uninstall instruction, an uninstall operation is performed according to the type of the first application, where the type of the first application includes a clone type or an instance type.

2. The method according to claim 1, characterized in that The performing the uninstallation operation according to the type of the first application includes: In response to the first uninstall instruction, when the type of the first application is instance type, the icon of the first application on the first screen is deleted and the uninstall operation of the first application is not performed.

3. The method according to claim 2, characterized in that The method further comprises: In response to obtaining a second uninstall instruction from the user for the first application on a second screen, an uninstall operation is performed on the first application, where the second screen is the only screen among the multiple screens on which the first application is deployed.

4. The method according to claim 1, wherein The step of deleting the icon of the first application on the first screen and not performing an uninstall operation on the first application in response to the first uninstall instruction includes: When the type of the first application is a clone type, the first clone application corresponding to the first application is deployed on the first screen and the main application corresponding to the first application is deployed on the third screen, in response to the first uninstall instruction, the icon of the first application on the first screen is deleted and the first clone application is uninstalled.

5. The method according to claim 1, wherein In response to the first uninstall instruction, deleting the icon of the first application on the first screen and not performing an uninstall operation on the first application, the method further includes: When the first application is a clone application, a main application corresponding to the first application is deployed on the first screen, and a second clone application corresponding to the first application is deployed on the fourth screen, in response to the first uninstall instruction, the icon of the first application on the first screen is deleted.

6. The method according to claim 4 or 5, characterized in that The method further comprises: Obtaining a third uninstall instruction from the user for the first application on the fifth screen; When the fifth screen is the only screen among the multiple screens on which the icon of the first application is deployed, the main application is uninstalled in response to the third uninstall instruction.

7. The method according to any one of claims 1 to 6, characterized in that The step of performing an uninstall operation in response to the first uninstall instruction and according to the type of the first application includes: In response to the first uninstall instruction, controlling the first screen to display a first interface, where the first interface includes prompt information, where the prompt information is used to prompt a user to delete the icon of the first application deployed on the first screen or uninstall the first application; receiving a first instruction from a user on the first interface; According to the first instruction, an uninstall operation is performed.

8. The method according to any one of claims 1 to 6, characterized in that The step of performing an uninstall operation in response to the first uninstall instruction and according to the type of the first application includes: In response to the first uninstall instruction, controlling the first screen to display a second interface, where the second interface includes information about the multiple screens; receiving a second instruction from a user on the first interface, where the second instruction indicates at least one screen among the multiple screens; According to the second instruction, an uninstall operation is performed.

9. An application uninstallation device, characterized in that: include: an acquiring unit, configured to acquire a first uninstall instruction from a user for a first application on a first screen, where the first application is deployed on a plurality of screens in a cockpit, the plurality of screens including the first screen; The processing unit is configured to perform an uninstall operation in response to the first uninstall instruction and according to a type of the first application, where the type of the first application includes a clone type or an instance type.

10. The device according to claim 9, characterized in that The processing unit is specifically configured to: In response to the first uninstall instruction, when the type of the first application is instance type, the icon of the first application on the first screen is deleted and the uninstall operation of the first application is not performed.

11. The device according to claim 10, characterized in that The processing unit is further configured to, in response to obtaining a second uninstall instruction from the user for the first application on a second screen, perform an uninstall operation on the first application, where the second screen is the only screen among the multiple screens on which the first application is deployed.

12. The device according to claim 9, characterized in that The processing unit is specifically configured to: When the type of the first application is a clone type, the first clone application corresponding to the first application is deployed on the first screen, and the main application corresponding to the first application is deployed on the third screen, in response to the first uninstall instruction, the icon of the first application on the first screen is deleted and the first clone application is uninstalled.

13. The device according to claim 9, characterized in that The processing unit is specifically configured to: When the first application is a clone application, a main application corresponding to the first application is deployed on the first screen, and a second clone application corresponding to the first application is deployed on the fourth screen, in response to the first uninstall instruction, the icon of the first application on the first screen is deleted.

14. The device according to claim 12 or 13, characterized in that The acquiring unit is further configured to acquire a third uninstall instruction from the user for the first application on the fifth screen; The processing unit is further configured to uninstall the main application in response to the third uninstall instruction when the fifth screen is the only screen among the multiple screens on which the icon of the first application is deployed.

15. The device according to any one of claims 9 to 14, characterized in that The device further comprises: a control unit, configured to control the first screen to display a first interface in response to the first uninstall instruction, wherein the first interface includes prompt information, and the prompt information is used to prompt a user to delete the icon of the first application deployed on the first screen or uninstall the first application; A receiving unit, configured to receive a first instruction from a user on the first interface; The processing unit is configured to perform an uninstall operation according to the first instruction.

16. The device according to any one of claims 9 to 14, characterized in that The device further comprises: a control unit, configured to control the first screen to display a second interface in response to the first uninstall instruction, where the second interface includes information of the plurality of screens; a receiving unit, configured to receive a second instruction from a user on the first interface, where the second instruction indicates at least one screen among the multiple screens; The processing unit is configured to perform an uninstall operation according to the second instruction.

17. An application uninstallation device, characterized in that: include: memory for storing computer programs; A processor, configured to execute the computer program stored in the memory, so that the apparatus performs the method according to any one of claims 1 to 8.

18. An application uninstallation system, characterized in that: The device comprises a plurality of screens and a computing platform, wherein the computing platform comprises the apparatus according to any one of claims 9 to 17.

19. A vehicle, characterized in that: Comprising the apparatus according to any one of claims 9 to 17, or the system according to claim 18.

20. A computer-readable storage medium, characterized in that Instructions are stored thereon, and when the instructions are executed by a processor, the processor is caused to implement the method according to any one of claims 1 to 8.

21. A computer program product, characterized in that The computer program product comprises a computer program code, which, when run on a computer, causes the computer to implement the method according to any one of claims 1 to 8.

22. A chip, characterized in that: The chip comprises a circuit for executing the method according to any one of claims 1 to 8.

Images