Application uninstallation method and apparatus, and vehicle

Abstract

Provided in the present application are an application uninstallation method and apparatus, and a vehicle. The method comprises: acquiring a first uninstallation instruction of a user for a first application on a first screen, wherein the first application is deployed on a plurality of screens in a cockpit, and the plurality of screens comprises the first screen; and in response to the first uninstallation instruction, executing an uninstallation operation on the basis of the type of the first application, wherein the type of the first application comprises a clone type or an instance type. The present application can be applied to intelligent vehicles or electric vehicles, can support users in flexibly uninstalling applications, and is conducive to improving the driving and riding experience of the users.

Description

Application uninstallation methods, devices, and vehicles

[0001] This application claims priority to Chinese Patent Application No. 202411219285.8, filed with the China National Intellectual Property Administration on August 30, 2024, entitled "Method, Apparatus and Vehicle for Application Unloading", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of smart cockpits, and more specifically, to a method, apparatus, and vehicle for application unloading. Background Technology

[0003] Currently, when a user needs to uninstall an app while in the vehicle's cabin, other apps on other screens are usually uninstalled simultaneously. This uninstallation method is inflexible, requiring users to reinstall the app if they want to use it on other screens, resulting in a poor user experience. Summary of the Invention

[0004] This application provides a method, apparatus, and vehicle for uninstalling applications, which can support users in flexibly uninstalling applications and help improve the user's driving experience.

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

[0006] Based on the above technical solution, applications can be uninstalled according to their type. This allows users to flexibly uninstall applications, helping to improve their driving experience.

[0007] In some possible implementations, the method also includes: determining the type of the first application based on its installation type.

[0008] For example, if the installation type of the first application is privacy-critical, then the type of the first application can be clone.

[0009] For example, if the installation type of the first application is shared benefits, then the type of the first application can be instance-based.

[0010] The aforementioned cloned applications can include a main application and cloned applications, which can be deployed on different displays. When the main application is uninstalled, all cloned applications are uninstalled together; uninstalling cloned applications does not affect the normal use of the main application. The main application can include the main application's user data and main program segment, which includes programs associated with application launch. The cloned application includes the cloned application's user data and cloned application, which can include programs related to using the main application's capabilities.

[0011] Unlike cloned applications, instanced applications do not distinguish between the main application and cloned applications. Regardless of which screens an instanced application is deployed on, only one application entity (or the main application) corresponding to that instanced application can exist in the vehicle, and the icons of that instanced application will be displayed on multiple screens. When the main application is uninstalled, the instanced application is completely uninstalled.

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

[0013] Based on the above technical solution, when uninstalling an instance of an application deployed on a certain display screen, if the same instance of the application is deployed on multiple display screens in the cockpit, the vehicle can avoid uninstalling the application entity (or main application) of the instance of the application; instead, it can delete the icon of the instance of the application displayed on that display screen. In this way, the user can still use the instance of the application on other display screens that display its icon.

[0014] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: in response to receiving a second uninstallation instruction from a user for a first application on a second screen, performing an uninstallation operation on the first application, wherein the second screen is the only screen among the plurality of screens where the first application is deployed.

[0015] Based on the above technical solution, when performing the uninstallation operation of an instanced application, if the instanced application is only deployed on the display screen in the current cockpit, then the vehicle can perform the uninstallation operation of the application entity (or main application) of the instanced application.

[0016] In some possible implementations, the second screen is the only screen among the multiple screens where the first application is deployed, or it can be understood as the screen among the multiple screens where the icon of the first application is displayed.

[0017] In conjunction with the first aspect, in some implementations of the first aspect, the response to the first uninstallation command to delete the icon of the first application on the first screen without performing the uninstallation operation on the first application includes: when the type of the first application is a clone, 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, the response to the first uninstallation command to delete the icon of the first application on the first screen and uninstall the first clone application.

[0018] Based on the above technical solution, when the main application corresponding to the cloned app is deployed on the third screen and the cloned app corresponding to the cloned app is deployed on the first screen, if the user's operation of uninstalling the cloned app on the first screen is detected, the uninstallation operation of the cloned app can be performed, and the icon of the cloned app corresponding to the cloned app displayed on the first screen can be deleted. At this time, the vehicle does not need to uninstall the main application. In this way, even if the user uninstalls the cloned app corresponding to the cloned app on the first screen, the user can still use the main application of the cloned app on the third screen.

[0019] In conjunction with the first aspect, in some implementations of the first aspect, in response to the first uninstallation command, the icon of the first application on the first screen is deleted and the uninstallation operation of the first application is not performed. The method further includes: when the first application is a clone application, the first screen has a corresponding main application and the fourth screen has a corresponding second clone application, in response to the first uninstallation command, the icon of the first application on the first screen is deleted.

[0020] Based on the above technical solution, when the first application is a clone application, and 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 the user's operation of uninstalling the first application deployed on the first screen is detected, only the icon of the first application displayed on the first screen can be deleted.

[0021] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: obtaining a third uninstallation command from the user for the first application on the fifth screen; and uninstalling the main application in response to the third uninstallation command when the fifth screen is the only screen among the plurality of screens where the icon of the first application is deployed.

[0022] Based on the above technical solution, when the first application is a clone application and the first application is only deployed on the fifth screen in the cockpit, if the user's operation of uninstalling the first application deployed on the fifth screen is detected, the main application can be uninstalled.

[0023] In conjunction with the first aspect, in some implementations of the first aspect, the response to the first uninstallation instruction, performing an uninstallation operation according to the type of the first application, includes: responding to the first uninstallation 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 a first instruction from the user on the first interface; and performing the uninstallation operation according to the first instruction.

[0024] Based on the above technical solution, users can choose to delete the icon of the first application deployed on the first screen or uninstall the first application. This allows users to uninstall the first application from a single screen, improving the user's driving experience.

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

[0026] Based on the above technical solution, users can view information about all screens where the first application is deployed on the first screen. This allows users to easily select from these screens and uninstall the first application deployed on other screens by operating on a single screen.

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

[0028] Secondly, an application uninstallation apparatus is provided, the apparatus comprising: an acquisition unit for acquiring a first uninstallation command from a user for a first application on a first screen, the first application being deployed on multiple screens within a cockpit, the multiple screens including the first screen; and a processing unit for responding to the first uninstallation command and performing an uninstallation operation according to the type of the first application, the type of the first application including a clone or an instance.

[0029] In conjunction with the second aspect, in some implementations of the second aspect, the processing unit is specifically used to: in response to the first uninstallation instruction, when the type of the first application is instance type, delete the icon of the first application on the first screen and not perform the uninstallation operation on the first application.

[0030] In conjunction with the second aspect, in some implementations of the second aspect, the processing unit is further configured to perform an uninstallation operation on the first application in response to receiving a second uninstallation command from the user for the first application on the second screen, wherein the second screen is the only screen among the plurality of screens on which the first application is deployed.

[0031] In conjunction with the second aspect, in some implementations of the second aspect, the processing unit is specifically used to: when the type of the first application is a clone, the first screen has a first clone application corresponding to the first application deployed on the first screen and the third screen has a main application corresponding to the first application deployed on the third screen, in response to the first uninstallation command, delete the icon of the first application on the first screen and uninstall the first clone application.

[0032] In conjunction with the second aspect, in some implementations of the second aspect, the processing unit is specifically used to: in response to the first uninstallation command, delete the icon of the first application on the first screen when the first application is a clone application, the first screen has a corresponding main application of the first application deployed on the first screen and the fourth screen has a corresponding second clone application of the first application deployed on the fourth screen.

[0033] In conjunction with the second aspect, in some implementations of the second aspect, the acquiring unit is further configured to acquire a third uninstallation 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 uninstallation instruction when the fifth screen is the only screen among the plurality of screens where the icon of the first application is deployed.

[0034] In conjunction with the second aspect, in some implementations of the second aspect, the apparatus further includes: a control unit, configured to control the first screen to display a first interface in response to the first uninstallation command, the first interface including prompt information for prompting the 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 command from the user on the first interface; and a processing unit, configured to perform an uninstallation operation according to the first command.

[0035] In conjunction with the second aspect, in some implementations of the second aspect, the device further includes: a control unit, configured to control the first screen to display a second interface in response to the first unloading command, the second interface including information from the plurality of screens; a receiving unit, configured to receive a second command from a user on the first interface, the second command instructing at least one of the plurality of screens; and a processing unit, configured to perform an unloading operation according to the second command.

[0036] Thirdly, this application provides an application unloading apparatus, 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 cause the apparatus to perform any of the possible methods in the first aspect.

[0037] Fourthly, this application provides an application uninstallation system, which includes a computing platform and multiple display devices, wherein the computing platform includes any of the possible devices in the second or third aspect.

[0038] Fifthly, this application provides a vehicle that includes any of the possible devices of the second or third aspect, or includes the system described in the fourth aspect.

[0039] Sixthly, this application provides a computer program product comprising: computer program code, which, when run on a computer, causes the computer to perform any of the possible methods described in the first aspect above.

[0040] 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 packaged separately from the processor. This application embodiment does not specifically limit this.

[0041] In a seventh aspect, this application provides a computer-readable medium storing program code that, when run on a computer, causes the computer to perform any of the possible methods described in the first aspect above.

[0042] Eighthly, this application provides a chip system including a processor for calling a computer program or computer instructions stored in a memory to cause the processor to perform any of the possible methods in the first aspect above.

[0043] In conjunction with the eighth aspect, in one possible implementation, the processor is coupled to the memory via an interface.

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

[0045] Ninthly, this application provides a chip system including circuitry for performing any of the possible methods described in the first aspect above. Attached Figure Description

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

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

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

[0049] Figure 4 is another schematic block diagram of the control system provided in an embodiment of this application;

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

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

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

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

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

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

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

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

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

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

[0060] Figure 15 is a schematic flowchart of the application uninstallation method provided in the embodiments of this application;

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

[0062] Figure 17 is a schematic block diagram of the application uninstallation device provided in an embodiment of this application. Detailed Implementation

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

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

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

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

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

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

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

[0070] To facilitate understanding of the technical solution of this application, the following detailed description of the solution provided by the embodiments of this application is based on Figures 3 to 17.

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

[0072] The above system accounts can also be referred to as vehicle system accounts.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0155] To facilitate understanding of the control method provided in the embodiments of this application, the application scenarios and graphical user interface (GUI) involved in this application will be described in detail below with reference to Figures 8 to 14. The processing actions (such as control, response, etc.) or steps involved in Figures 8 to 14 can be executed by the computing platform 150 shown in Figure 1, or they can also be executed by the aforementioned control system, for example, by the user center service unit 430.

[0156] Figures 8 and 9 illustrate an example of a GUI provided in an embodiment of this application.

[0157] As shown in Figure 8(a), user A is located in the driver's seat area of ​​the vehicle cabin. The content displayed on the display screen 201 (i.e., the central control screen) can be as shown in Figure 8(a), including a content display area 810 and a function bar 820. For example, the content display area 810 includes: icons for multiple applications, each icon used to activate one application; a login control 801 (indicating login status); and Bluetooth, Wi-Fi, and cellular network signal icons, used to indicate the vehicle's Bluetooth on and / or connection status, Wi-Fi on status, and cellular network signal strength, respectively. The function bar 820 includes a homepage icon, seat controls, air conditioning controls, and volume controls, used to control the display of the homepage in the content display area 810, control the on / off switch of seat ventilation and / or adjust the airflow of seat ventilation, control the on / off switch of air conditioning and / or adjust the air conditioning temperature and heating / cooling status, adjust the in-vehicle air circulation status, and adjust the volume of the sound device, respectively.

[0158] The tab shown in Figure 8(a) includes icons for applications such as Settings, Navigation, Camera, Browser, Weather, High-resolution Maps, App Store, Social Apps, Stocks, and Video.

[0159] As shown in Figure 8(b), user B is located in the second-row right-side area of ​​the vehicle cabin. The content displayed on display screen 204 (i.e., the second-row right-side entertainment screen) can be as shown in Figure 8(b), including a content display area 830. For example, the content display area 830 includes: icons for multiple applications, each icon used to activate one application; a login control 801 (indicating an unlogged-in state); and Bluetooth, Wi-Fi, and cellular signal icons, respectively indicating the vehicle's Bluetooth on and / or connection status, Wi-Fi on status, and cellular signal strength.

[0160] The tab shown in Figure 8(b) includes icons for applications such as Settings, Navigation, Camera, Browser, Weather, High-resolution Maps, App Store, Social Apps, Stocks, and Video.

[0161] The social applications deployed on displays 201 and 204 can be cloned applications (or, the installation type of the social applications can be privacy-critical). The social application deployed on display 201 can be the main application corresponding to the social application, and the social application deployed on display 204 can be a cloned application corresponding to the social application. When the main application is uninstalled, all cloned applications are uninstalled together. Uninstalling cloned applications does not affect the normal use of the main application. The main application can include the user data and main program segment of the main application, which includes programs associated with the application's launch. The cloned application includes the user data and cloned application, which can include programs related to the capabilities of using the main application. For the user, the experience when using the main application and cloned applications is consistent.

[0162] When the system detects that the user has long-pressed the icon 801 of the social application, the vehicle can display the GUI shown in Figure 9(a) on the display screen 204.

[0163] Figure 9 shows an example of a GUI provided in an embodiment of this application.

[0164] As shown in Figure 9(a), in response to a user's long press of icon 801, the vehicle can display a function bar 901 on display screen 204. This function bar 901 includes multiple functions, such as uninstall, change application type, share, and others. When the user clicks the uninstall function 902, the vehicle can display the GUI shown in Figure 9(b) on display screen 204.

[0165] As shown in Figure 9(b), in response to the user clicking the uninstall function 902, the vehicle can determine whether the social application deployed on display screen 204 is the main application. If it is determined that the social application deployed on display screen 204 is not the main application (or, the social application deployed on display screen 204 is a clone application), the vehicle can determine whether display screen 204 is the only screen among the multiple screens in the cabin where the social application is deployed. Since display screen 204 is not the only screen among the multiple screens in the cabin where the social application is deployed, the vehicle can uninstall the clone application corresponding to the social application deployed on display screen 204 and delete its icon 801. Simultaneously, the vehicle can also control display screen 204 to display the message "The clone application of the social application deployed on the second-row right-side entertainment screen has been uninstalled. You can also experience the social application on the central control screen."

[0166] In this embodiment, when the main application corresponding to the 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 system detects that the user wants to uninstall the social application on display screen 204, the vehicle can perform the uninstallation operation on the clone application, delete the icon 801, and not uninstall the main application. Thus, 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.

[0167] Figure 10 shows an example of a GUI provided in an embodiment of this application.

[0168] As shown in Figure 10(a), in response to a user's long-press operation on the icon of a social application deployed on display screen 201, the vehicle can display a function bar 1001 on display screen 201, which includes multiple functions such as uninstall, change application type, share, and others. When the user's click on the uninstall function 1002 is detected, the vehicle can display the GUI shown in Figure 10(b) on display screen 201.

[0169] As shown in Figure 10(b), in response to the user clicking the uninstall function 1002, the vehicle can determine whether the social application deployed on display screen 201 is the main application. When it is determined that the social application deployed on display screen 201 is the main application, the vehicle can determine whether there are any clone applications on the displays in the cabin that have not been uninstalled (or, whether display screen 201 is the only display screen in the cabin with a social application deployed). Since all clone applications on other displays in the cabin have been uninstalled (or, display screen 201 is the only screen among multiple screens in the cabin with a social application deployed), the vehicle can uninstall the main application corresponding to the social application deployed on display screen 201 and delete the icon of that social application. Simultaneously, the vehicle can also control display screen 201 to display the message "Social application completely uninstalled".

[0170] In this embodiment of the application, when only the display screen 201 in the cockpit is equipped with a social application, if the user's operation of uninstalling the social application on the display screen 201 is detected, the vehicle can uninstall the main application.

[0171] Figure 11 shows an example of a GUI provided in an embodiment of this application.

[0172] As shown in Figure 11(a), the tab currently displayed on the screen 201 includes icons for applications such as Settings, Navigation, Camera, Browser, Weather, High-Precision Maps, App Store, Social Apps, Stocks, and Videos.

[0173] As shown in Figure 11(b), the tab currently displayed on display screen 204 includes icons for applications such as Settings, Navigation, Camera, Browser, Weather, High-Precision Maps, App Store, Social Apps, Stocks, and Videos.

[0174] The video applications deployed on displays 201 and 204 can be instance-based applications. Unlike clone applications, instance-based applications do not distinguish between a main application and clone applications. Regardless of which screens the instance-based application is deployed on, only one application entity (or main application) can exist in the vehicle, and the icons of the instance-based application will be displayed on multiple displays. When the main application is uninstalled, the instance-based application is completely uninstalled. After the instance-based application is installed in the vehicle, the icons of the instance-based application will be displayed on displays 201 and 204. For users, the experience of using the instance-based application on different screens is consistent. For example, if the instance-based application is a video application, after user A's vehicle system account logs in on display 201, the account of the video application can be automatically logged in on displays 201 and 204.

[0175] When a long press operation by the user on the icon 1101 of the video application on the display screen 204 is detected, the GUI shown in Figure 11(c) can be displayed on the display screen 204.

[0176] As shown in Figure 11(c), in response to a user's long-press operation on the video application icon 1101 on display screen 204, the vehicle can display a function bar 1102 on display screen 204. This function bar 1102 includes multiple functions, such as uninstall, change application type, share, and others. When the user's click on the uninstall function 1103 is detected, the vehicle can display the GUI shown in Figure 11(d) on display screen 204.

[0177] As shown in Figure 11(d), in response to the user clicking the uninstall function 1103, the vehicle can determine whether the display screen 204 is the only display screen in the cabin with the video application icon deployed. If it is determined that the display screen 204 is not the only display screen in the cabin with the video application icon deployed, the vehicle can delete the icon 1101 without performing the uninstall operation on the video application. At the same time, the vehicle can also control the display screen 204 to display the prompt message "The video application icon on the second-row right-side entertainment screen has been deleted. You can also use the video application on the central control screen."

[0178] In this embodiment, when performing an uninstallation operation on an instanced application, if the icon of the instanced application currently displayed on the screen is not the icon of the last instanced application, the vehicle may not perform an uninstallation operation on the application entity (or main application) of the instanced application, but instead delete the icon of the instanced application displayed on the screen. In this way, the user can still use the instanced application on other screens displaying the icon of the instanced application.

[0179] Figure 12 shows an example of a GUI provided in an embodiment of this application.

[0180] As shown in Figure 12(a), 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. This function bar 1202 includes multiple functions, such as uninstall, change application type, share, and others. When the user's click on the uninstall function 1203 is detected, the vehicle can display the GUI shown in Figure 12(b) on the display screen 201.

[0181] As shown in Figure 12(b), in response to the user clicking the uninstallation function 1203, the vehicle can determine whether the display screen 201 is the only display screen in the cabin with the video application icon deployed. If the display screen 201 is determined to be the only display screen in the cabin with the video application icon deployed, the vehicle can delete the icon 1201 and perform the uninstallation operation for the video application. Simultaneously, the vehicle can also control the display screen 201 to display the message "Video application uninstalled".

[0182] In this embodiment of the application, when performing an uninstallation operation on an instanced application, if the icon of the instanced application currently displayed on the screen is the icon of the last instanced application, then the vehicle can perform an uninstallation operation on the application entity (or main application) of the instanced application.

[0183] The above, together with Figures 8 to 12, describes the process of a user performing an uninstallation operation on an application on each display screen. The following uses the GUI shown in Figures 13 and 14 as an example to describe the process of quickly uninstalling an application.

[0184] Figure 13 shows an example of a GUI provided in an embodiment of this application.

[0185] As shown in Figure 13(a), in response to a user's long-press operation on the video application icon on display screen 204, the vehicle can display a function bar 1301 on display screen 204, which includes multiple functions, such as uninstall, change application type, share, and others. When the user's click on the uninstall function 1302 is detected, the vehicle can display the GUI shown in Figure 13(b) on display screen 204.

[0186] As shown in Figure 13(b), in response to the user clicking the uninstall function 1302, the vehicle can display a prompt box 1303 on the display screen 204. The prompt box 1303 includes the prompt message "A video application has been detected on the central control screen and the entertainment screen on the right side of the second row. Please select it", control 1304, and control 1305 to uninstall the video application. Control 1304 is the control corresponding to the icon of the video application on the entertainment screen on the right side of the second row.

[0187] For example, when a user clicks on control 1304 is detected, the vehicle can delete the icon of the video application displayed on display screen 204.

[0188] For example, when a user clicks on control 1305 is detected, the vehicle can uninstall the video application. After uninstalling the video application, the icons on displays 201 and 204 are deleted.

[0189] Figure 14 shows an example of a GUI provided in an embodiment of this application.

[0190] As shown in Figure 14(a), in response to a user's long-press operation on the video application icon on display screen 204, the vehicle can display a function bar 1401 on display screen 204, which includes multiple functions such as uninstall, change application type, share, and others. When the user's click on the uninstall function 1402 is detected, the vehicle can display the GUI shown in Figure 14(b) on display screen 204.

[0191] The number in the lower left corner of the application icon shown in Figure 14(a) above represents 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 displays 201 and 204, the lower left corner of the social application icon displayed on display 204 will show the number "2". Similarly, the lower left corner of the social application icon displayed on display 201 will show the number "2".

[0192] As shown in Figure 14(b), in response to the user clicking the uninstallation function 1402, the vehicle can display a prompt box 1403 on the display screen 204. The prompt box 1403 includes the prompt message "Video applications have been detected 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 entertainment screen on the right side of the second row where the video applications are deployed.

[0193] For example, when the system detects that a user clicks on the corresponding control on the central control screen and clicks the OK control, the vehicle can delete the icon of the video application displayed on the display screen 201 without performing an uninstallation operation on the video application.

[0194] For example, when the system detects that a user clicks the control corresponding to the entertainment screen on the right side of the second row and clicks the OK control, the vehicle can delete the icon of the video application displayed on the display screen 204 without performing an uninstallation operation on the video application.

[0195] For example, when the vehicle detects that a user clicks on the corresponding control on the central control screen and the second-row right-side entertainment screen and clicks the "OK" control, the vehicle can uninstall the video application. After uninstalling the video application, the icons on displays 201 and 204 will be deleted.

[0196] Figure 15 shows a schematic flowchart of the application uninstallation method 1500 provided in an embodiment of this application. The method 1500 can be executed by the vehicle 100; or, the method 1500 can be executed by the computing platform 150; or, the method 1500 can be executed by a processor, chip, or circuit in the computing platform 150. The method 1500 includes:

[0197] S1510, Obtain a first uninstall command from the user for a first application on a first screen, the first application being deployed on multiple screens within the cockpit, the multiple screens including the first screen.

[0198] For example, as shown in Figure 9(a), the first unload instruction can be an operation performed by the user clicking control 902.

[0199] For example, as shown in Figure 11(c), the first unload instruction can be an operation of the user clicking control 1103.

[0200] S1520, in response to the first uninstallation command, an uninstallation operation is performed according to the type of the first application, the type of the first application including clone type or instance type.

[0201] The above descriptions of clone-type or instance-type applications can be found in the above embodiments, and will not be repeated here for the sake of brevity.

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

[0203] For example, if the installation type of the first application is privacy-critical, then the type of the first application can be clone.

[0204] For example, if the installation type of the first application is shared benefits, then the type of the first application can be instance-based.

[0205] Optionally, depending on the type of the first application, an uninstallation operation is performed, including: in response to the first uninstallation instruction, if the type of the first application is instance type, deleting the icon of the first application on the first screen and not performing an uninstallation operation on the first application.

[0206] For example, the first screen can be a display screen 204 as shown in (c) and (d) of FIG11. In response to the user's click on the control 1103, the icon of the video application displayed on the display screen 204 can be deleted without performing an uninstallation operation on the video application.

[0207] Optionally, the method 1500 further includes: in response to receiving a second uninstallation command from the user for a first application on a second screen, performing an uninstallation operation on the first application, wherein the second screen is the only screen among the plurality of screens where the first application is deployed.

[0208] For example, the second screen can be display screen 201 as shown in Figures 12(a) and (b), and the second uninstallation instruction can be an operation of the user clicking control 1203. In response to the user clicking control 1203, an uninstallation operation of the video application can be performed.

[0209] Optionally, in response to the first uninstallation command, deleting the icon of the first application on the first screen and not performing the uninstallation operation on the first application includes: when the type of the first application is a clone, 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 uninstallation command, deleting the icon of the first application on the first screen and uninstalling the first clone application.

[0210] For example, the first screen can be display screen 204 as shown in Figures 9(a) and (b), the third screen can be display screen 201 as shown in Figure 8(b), and the first application can 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 can be deleted and the corresponding clone application deployed on the display screen 204 can be uninstalled.

[0211] Optionally, in response to the first uninstallation command, the icon of the first application on the first screen is deleted and the uninstallation operation of the first application is not performed. The method further includes: when the first application is a clone application, the first screen has a corresponding main application and the fourth screen has a corresponding second clone application, in response to the first uninstallation command, the icon of the first application on the first screen is deleted.

[0212] For example, the first screen can be display screen 201 as shown in FIG8(a), the fourth screen can be display screen 204 as shown in FIG8(b), and the first application can be a social application. In response to the user's uninstallation command for the social application displayed on display screen 201, the icon of the social application displayed on display screen 201 can be deleted without performing the uninstallation operation of the main application and clone application of the social application.

[0213] Optionally, the method 1500 further includes: obtaining a third uninstallation command from the user for the first application on the fifth screen; and uninstalling the main application in response to the third uninstallation command when the fifth screen is the only screen among the plurality of screens where the icon of the first application is deployed.

[0214] For example, the fifth screen may be display screen 201 as shown in Figures 10(a) and (b), the first application may be a social application, and the third uninstallation instruction may be an operation performed by the user clicking control 1002. In response to the user clicking control 1002, the vehicle may perform an uninstallation operation on the main application of the social application.

[0215] Optionally, in response to the first uninstallation command, an uninstallation operation is performed according to the type of the first application, including: in response to the first uninstallation command, 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 a first command from the user on the first interface; and performing the uninstallation operation according to the first command.

[0216] For example, as shown in Figure 13, the first interface can be a GUI as shown in Figure 13(b), which includes the prompt message "A video application has been detected on the central control screen and the entertainment screen on the right side of the second row. Please select it", control 1304 and control 1305.

[0217] For example, the first instruction could be an operation where the user clicks on control 1304. In response to the user clicking on control 1304, the vehicle can delete the icon of the video application displayed on display screen 204.

[0218] For example, the second instruction could be a user clicking control 1305. In response to the user clicking control 1305, the vehicle can uninstall the video application. After uninstalling the video application, the icons on both display screens 201 and 204 will be deleted.

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

[0220] For example, the second interface can be a GUI as shown in Figure 14(b), which includes the prompt message "Video applications have been detected on two screens in the cockpit. Please select the screen you want to uninstall" and controls that highlight the central control screen and the entertainment screen on the right side of the second row where the video applications are deployed.

[0221] For example, the second instruction could be that the user clicks the corresponding control on the central control screen and then clicks the "OK" control. In response to the user clicking the corresponding control on the central control screen and then clicking the "OK" control, the vehicle can delete the video application icon displayed on the display screen 201 without performing an uninstallation operation on the video application.

[0222] For example, the second instruction could be that the user clicks the control corresponding to the entertainment screen on the right side of the second row and clicks the "OK" control. In response to the user clicking the control corresponding to the entertainment screen on the right side of the second row and clicking the "OK" control, the vehicle can delete the icon of the video application displayed on the display screen 204 without performing an uninstallation operation on the video application.

[0223] For example, the second instruction could be a user clicking the corresponding control on the central control screen and the second-row right-side entertainment screen and clicking the "OK" control. In response to the user clicking the corresponding control on the central control screen and the second-row right-side entertainment screen and clicking the "OK" control, the vehicle can perform an uninstallation operation on the video application. After the video application is uninstalled, the icons on both display screens 201 and 204 will be deleted.

[0224] Figure 16 shows a schematic flowchart of an application uninstallation method 1600 provided in an embodiment of this application. The method 1600 includes:

[0225] S1601, An operation by the user to uninstall application 1 deployed on the cockpit display screen 1 has been detected.

[0226] S1602, Determine whether application 1 is a cloned application.

[0227] For example, if application 1 is a cloned application, S1603 can be executed; otherwise, S1609 can be executed.

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

[0229] For example, if the application 1 deployed on display 1 is the main application corresponding to application 1, execute S1604; otherwise, execute S1605.

[0230] S1604, determine if there are any cloned applications corresponding to application 1 that have not been uninstalled.

[0231] For example, if there is still a clone application corresponding to application 1 that has not been uninstalled, execute S1606; otherwise, execute S1607.

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

[0233] For example, if the icon of application 1 deployed on display 1 is the last icon, execute S1607; otherwise, execute S1608.

[0234] S1606, Delete the icon of application 1 currently displayed on display screen 1.

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

[0236] S1607, Uninstall the main application corresponding to application 1.

[0237] For example, the display screen 1 can be the display screen 201 shown in Figures 10(a) and (b), and the first application can be a social application. In response to the user clicking the control 1002, when it is determined that the main application corresponding to the social application is deployed on the display screen 1 and no clone application corresponding to the social application is deployed on other displays in the cockpit (or, all clone applications of the social application have been uninstalled), the uninstallation operation of the main application corresponding to the social application can be performed.

[0238] S1608, Uninstall the clone application corresponding to application 1.

[0239] For example, the display screen 1 can be the display screen 204 shown in Figures 9(a) and (b), and the first application can be a social application. In response to the user clicking the 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 icon of the last social application, the clone application corresponding to the social application deployed on the display screen 204 can be uninstalled.

[0240] S1609, Determine whether Application 1 is an instance application.

[0241] For example, if application 1 is an instance application, S1610 can be executed; otherwise, S1611 is executed.

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

[0243] For example, if the icon of application 1 deployed on display 1 is the last icon, execute S1612; otherwise, execute S1613.

[0244] S1611, Uninstall application 1.

[0245] For example, if application 1 is neither a cloned application nor an instanced application, then the uninstallation operation of application 1 can be performed.

[0246] S1612, Uninstall the main application corresponding to application 1.

[0247] In S1612 above, the main application corresponding to uninstalling application 1 can also be understood as the application entity corresponding to uninstalling application 1.

[0248] For example, the display screen 1 can be the display screen 201 shown in Figures 12(a) and (b), and the application 1 can 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 icon of the last video application, an uninstallation operation of the video application can be performed.

[0249] S1613, Delete the icon of application 1 currently displayed on display screen 1.

[0250] For example, the display screen 1 can be the display screen 204 shown in Figures 11(c) and (d), and the application 1 can be a video application. In response to a 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 icon of the last video application, the icon of the video application displayed on the display screen 204 can be deleted.

[0251] Figure 17 shows a schematic block diagram of an application uninstallation device 1700 provided in an embodiment of this application. The device 1700 includes: an acquisition unit 1710, configured to acquire a first uninstallation command from a user for a first application on a first screen, the first application being deployed on multiple screens within the cockpit, the multiple screens including the first screen; and a processing unit 1720, configured to, in response to the first uninstallation command, perform an uninstallation operation according to the type of the first application, the type of the first application including a clone type or an instance type.

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

[0253] Optionally, the processing unit 1720 is further configured to perform an uninstallation operation on the first application in response to receiving a second uninstallation command from the user for the first application on the second screen, wherein the second screen is the only screen among the plurality of screens on which the first application is deployed.

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

[0255] Optionally, the processing unit 1720 is specifically configured to: in response to the first uninstallation command, delete the icon of the first application on the first screen when the first application is a cloned application, the first screen has a corresponding main application and the fourth screen has a corresponding second cloned application, delete the icon of the first application on the first screen.

[0256] Optionally, the acquisition unit 1710 is further configured to acquire a third uninstallation command from the user for the first application on the fifth screen; the processing unit 1720 is further configured to uninstall the main application in response to the third uninstallation command when the fifth screen is the only screen among the plurality of screens where the icon of the first application is deployed.

[0257] Optionally, the device 1700 further includes: a control unit, configured to control the first screen to display a first interface in response to the first uninstallation command, the first interface including prompt information for prompting the 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 command from the user on the first interface; and a processing unit 1720, configured to perform the uninstallation operation according to the first command.

[0258] Optionally, the device 1700 further includes: a control unit, configured to control the first screen to display a second interface in response to the first unloading command, the second interface including information from the plurality of screens; a receiving unit, configured to receive a second command from a user on the first interface, the second command instructing at least one of the plurality of screens; and a processing unit 1720, configured to perform an unloading operation according to the second command.

[0259] It should be understood that the division of units in the above device is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, the units in the device can be implemented by a processor calling software; for example, the device includes a processor connected to memory, which stores instructions. The processor calls the instructions stored in memory to implement any of the above methods or to implement the functions of each unit in the device. The processor can be, for example, a general-purpose processor, such as a CPU or microprocessor, and the memory can be internal or external to the device. Alternatively, the units in the device can be implemented as hardware circuits. The functions of some or all units can be implemented through the design of the hardware circuits, which can 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 units are implemented through the design of the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using a PLD, such as an FPGA, which can include a large number of logic gates. The connection relationships between the logic gates are configured through configuration files, thereby implementing the functions of some or all units. All units of the above device can be implemented entirely through processor calling software, or entirely through hardware circuits, or partially through processor calling software and the remaining parts through hardware circuits.

[0260] In this application embodiment, a processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction reading and execution capabilities, such as a CPU, microprocessor, GPU, or DSP. In another implementation, the processor can implement certain functions through the logical relationships of hardware circuits. These logical relationships are fixed or reconfigurable. For example, the processor may be a hardware circuit implemented as an ASIC or PLD, such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and configuring the hardware circuit can be understood as the processor loading instructions to implement the functions of some or all of the above units. Furthermore, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as an NPU, TPU, or DPU.

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

[0262] Furthermore, the units in the above devices can be integrated in whole or in part, or they can be implemented independently. In one implementation, these units are integrated together as a System-on-a-Chip (SoC). The SoC may include at least one processor for implementing any of the above methods or implementing the functions of the units in the device. The at least one processor may be of different types, such as CPU and FPGA, CPU and AI processor, CPU and GPU, etc.

[0263] This application also provides an application uninstallation device, which includes a processing unit and a storage unit. The storage unit is used to store instructions, and the processing unit executes the instructions stored in the storage unit to cause the device to perform the methods or steps described in the above embodiments.

[0264] Alternatively, if the device is located in a vehicle, the aforementioned processing unit may be the processor 151-15n shown in FIG1.

[0265] This application embodiment also provides an application uninstallation system, which may include a computing platform and multiple screens, and the computing platform may include the application uninstallation device 1700 described above.

[0266] This application also provides a vehicle that may include the application uninstallation device 1700 or the application uninstallation system described above.

[0267] This application also provides a computer program product, which includes computer program code that, when run on a computer, causes the computer to perform the methods described in the above embodiments.

[0268] This application also provides a computer-readable medium storing program code that, when run on a computer, causes the computer to perform the methods described in the above embodiments.

[0269] This application also provides a chip, which includes a circuit for performing the noise reduction method described in the above embodiments.

[0270] In implementation, each step of the above method can be completed by integrated logic circuits in the processor's hardware or by instructions in software. The method disclosed in the embodiments of this application can be directly implemented by a hardware processor, or by a combination of hardware and software modules within the processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, power-on erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method. To avoid repetition, detailed descriptions are omitted here.

[0271] It should be understood that in the embodiments of this application, the memory may include read-only memory and random access memory, and provides instructions and data to the processor.

[0272] It should also be understood that, in the various embodiments of this application, the order of the above-mentioned processes does not imply 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 this application.

[0273] Those skilled in the art will recognize that the units and algorithm steps of the various examples 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 implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art 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.

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

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

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

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

[0278] If the aforementioned functions are implemented as 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 this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

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

Claims

1. An application uninstallation method, characterized in that, include: Obtain a user's first uninstall command for a first application on a first screen, wherein the first application is deployed on multiple screens in the cockpit, and the multiple screens include the first screen; In response to the first uninstallation command, an uninstallation operation is performed according to the type of the first application, which includes clones or instances.

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

3. The method according to claim 2, characterized in that, The method further includes: In response to receiving a second uninstall command from the user for a first application on the second screen, an uninstall operation is performed on the first application, wherein the second screen is the only screen among the plurality of screens where the first application is deployed.

4. The method according to claim 1, characterized in that, The step of responding to the first uninstallation command by deleting the icon of the first application on the first screen without performing an uninstallation operation on the first application includes: When 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 uninstallation command, 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, characterized in that, The method of responding to the first uninstallation command by deleting the icon of the first application on the first screen without performing an uninstallation operation on the first application further includes: When the first application is a cloned application, the main application corresponding to the first application is deployed on the first screen, and the second cloned application corresponding to the first application is deployed on the fourth screen, in response to the first uninstallation command, 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 includes: Obtain the user's third uninstall command for the first application on the fifth screen; When the fifth screen is the only screen among the plurality of screens where the icon of the first application is deployed, the main application is uninstalled in response to the third uninstall command.

7. The method according to any one of claims 1 to 6, characterized in that, The step of responding to the first uninstallation command and performing an uninstallation operation according to the type of the first application includes: In response to the first uninstallation command, the first screen is controlled 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; Receive the user's first instruction on the first interface; According to the first instruction, the uninstallation operation is performed.

8. The method according to any one of claims 1 to 6, characterized in that, The step of responding to the first uninstallation command and performing an uninstallation operation according to the type of the first application includes: In response to the first uninstallation command, the first screen is controlled to display a second interface, the second interface including information from the plurality of screens; Receive a second instruction from the user on a first interface, the second instruction instructing at least one of the plurality of screens; According to the second instruction, perform the uninstallation operation.

9. An application unloading device, characterized in that, include: The acquisition unit is used to acquire a user's first uninstallation instruction for a first application on a first screen, wherein the first application is deployed on multiple screens in the cockpit, and the multiple screens include the first screen. The processing unit is configured to respond to the first uninstallation command and perform an uninstallation operation according to the type of the first application, wherein the type of the first application includes a clone or an instance.

10. The apparatus according to claim 9, characterized in that, The processing unit is specifically used for: In response to the first uninstallation command, when the first application is of type instance, the icon of the first application on the first screen is deleted and the uninstallation operation of the first application is not performed.

11. The apparatus according to claim 10, characterized in that, The processing unit is further configured to perform an uninstallation operation on the first application in response to receiving a second uninstallation command from the user for the first application on the second screen, wherein the second screen is the only screen among the plurality of screens in which the first application is deployed.

12. The apparatus according to claim 9, characterized in that, The processing unit is specifically used for: When 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 uninstallation command, the icon of the first application on the first screen is deleted and the first clone application is uninstalled.

13. The apparatus according to claim 9, characterized in that, The processing unit is specifically used for: When the first application is a cloned application, the main application corresponding to the first application is deployed on the first screen, and the second cloned application corresponding to the first application is deployed on the fourth screen, in response to the first uninstallation command, the icon of the first application on the first screen is deleted.

14. The apparatus according to claim 12 or 13, characterized in that, The acquisition unit is further configured to acquire a third uninstallation command 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 uninstallation command when the fifth screen is the only screen among the plurality of screens where the icon of the first application is deployed.

15. The apparatus according to any one of claims 9 to 14, characterized in that, The device further includes: A control unit is configured to, in response to the first uninstallation command, control 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; A receiving unit is configured to receive a first instruction from the user on the first interface; The processing unit is configured to perform an unloading operation according to the first instruction.

16. The apparatus according to any one of claims 9 to 14, characterized in that, The device further includes: A control unit is configured to, in response to the first unloading command, control the first screen to display a second interface, the second interface including information from the plurality of screens; A receiving unit is configured to receive a second instruction from a user on the first interface, wherein the second instruction instructs at least one of the plurality of screens. The processing unit is configured to perform an unloading operation according to the second instruction.

17. An application unloading device, characterized in that, include: Memory, used to store computer programs; A processor for executing a computer program stored in the memory to cause the apparatus to perform the method as described in any one of claims 1 to 8.

18. An application uninstallation system, characterized in that, It includes multiple screens and a computing platform, the computing platform including the means as described in any one of claims 9 to 17.

19. A vehicle, characterized in that, Includes the apparatus as described in any one of claims 9 to 17, or the system as described in claim 18.

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

21. A computer program product, characterized in that, The computer program product includes computer program code that, when run on a computer, causes the computer to perform the method as described in any one of claims 1 to 8.

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

Images