Method, apparatus, and vehicle for application offloading

Abstract

The application provides a method, device and vehicle for application uninstalling, the method comprising: obtaining a first uninstalling instruction of a user for a first application on a first screen, the first application being deployed on a plurality of screens in a cabin, the plurality of screens comprising the first screen; and in response to the first uninstalling instruction, performing an uninstalling operation according to a type of the first application, the type of the first application comprising a clone type or an instance type. The application can be applied to a smart car or an electric car, can support flexible uninstalling of an application by a user, and helps to improve the driving experience of the user.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of intelligent cockpit, and more particularly, to a method and device for application uninstallation and a vehicle. BACKGROUND

[0002] When a user needs to uninstall an application in the cockpit of a vehicle, the user generally uninstalls other applications on other screens at the same time. Such uninstallation is not flexible enough, and the user needs to reinstall the application when the user wants to use the application on other screens, which leads to a poor user experience. SUMMARY

[0003] The present application provides a method and device for application uninstallation and a vehicle, which can support flexible application uninstallation and improve the user experience.

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

[0005] Based on the above technical solution, the application can be uninstalled based on the type of the application. In this way, the user can flexibly uninstall the application, and the user experience can be improved.

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

[0007] For example, if the installation type of the first application is a privacy key type, the type of the first application can be the clone type.

[0008] For example, if the installation type of the first application is a right sharing type, the type of the first application can be the instance type.

[0009] The clone type application can include a main application and a clone application. The main application and the clone application can be deployed on different display screens. When the main application is uninstalled, all the clone applications are uninstalled together, and the uninstallation of the clone applications does not affect the normal use of the main application. The main application can include user data of the main application and a main program segment, the main program segment including a program associated with application startup. The clone application can include user data of the clone application and a clone application program, the clone application program including a program related to the capability of using the main application.

[0010] Different from the above-mentioned clone type application, the instance type application does not distinguish the main application and the clone application. No matter on which screen the instance type application is deployed, there can be only one application entity (or main application) corresponding to the instance type application in the vehicle, and the icons of the instance type application are displayed on the multiple display screens. The instance type application is completely uninstalled after the main application is uninstalled.

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

[0012] Based on the above technical solution, when the uninstall operation on the instance type application deployed on a certain display screen is performed, if the instance type application is deployed on the multiple display screens in the cabin, the vehicle can not perform the uninstall operation on the application entity (or main application) of the instance type application, but delete the icon of the instance type application displayed on the display screen. In this way, the user can still use the instance type application on the display screen displaying the icon of the instance type application.

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

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

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

[0016] In combination with the first aspect, in some implementations of the first aspect, in response to the first uninstall instruction, deleting the icon of the first application on the first screen and not performing the uninstall operation on the first application includes: in response to the first uninstall instruction, when the type of the first application is the clone type, the first application corresponding first clone application is deployed on the first screen, and the main application corresponding to the first application is deployed on the third screen, deleting the icon of the first application on the first screen and uninstalling the first clone application.

[0017] Based on the technical solution, when the first screen is deployed with the main application corresponding to the first application and the fourth screen is deployed with the second split application corresponding to the first application, if it is detected that the user performs an operation of uninstalling the first application deployed on the first screen, only the icon of the first application displayed on the first screen can be deleted.

[0018] With reference to the first aspect, in some implementations of the first aspect, in response to the first uninstall instruction, the icon of the first application on the first screen is deleted and the uninstall operation of the first application is not performed, and the method further includes: when the first application is a split application, the first screen is deployed with a main application corresponding to the first application, and the fourth screen is deployed with a second split application corresponding to the first application, in response to the first uninstall instruction, the icon of the first application on the first screen is deleted.

[0019] Based on the technical solution, when the first application is a split application, the first screen in the cabin is deployed with a main application corresponding to the first application, and the fourth screen is deployed with a split application corresponding to the first application, if it is detected that the user performs an operation of uninstalling the first application deployed on the first screen, only the icon of the first application displayed on the first screen can be deleted.

[0020] With reference to the first aspect, in some implementations of the first aspect, the method further includes: obtaining a third uninstall instruction of the user for the first application on the fifth screen; when the fifth screen is the only screen in the plurality of screens on which the icon of the first application is deployed, in response to the third uninstall instruction, the main application is uninstalled.

[0021] Based on the technical solution, when the first application is a split application and only the fifth screen in the cabin is deployed with the first application, if it is detected that the user performs an operation of uninstalling the first application deployed on the fifth screen, the uninstall operation of the main application can be performed.

[0022] With reference to the first aspect, in some implementations of the first aspect, in response to the first uninstall instruction, the uninstall operation is performed according to the type of the first application, including: in response to the first uninstall instruction, the first screen is controlled to display a first interface, the first interface includes prompt information, the prompt information is used to prompt the user to delete the icon of the first application deployed on the first screen or uninstall the first application; a first instruction of the user on the first interface is received; and according to the first instruction, the uninstall operation is performed.

[0023] Based on the technical solution, the user can select to delete the icon of the first application deployed on the first screen or uninstall the first application on the first screen. In this way, the user can operate on one screen, and the uninstallation of the first application can be realized, which helps to improve the driving experience of the user.

[0024] With reference to the first aspect, in some implementations of the first aspect, in response to the first uninstall instruction, the uninstall operation is performed according to the type of the first application, including: in response to the first uninstall instruction, controlling the first screen to display a second interface, the second interface including information of the plurality of screens; receiving a second instruction of the user on the first interface, the second instruction indicating at least one screen of the plurality of screens; and performing the uninstall operation according to the second instruction.

[0025] Based on the technical solution, the user can view the information of all screens on which the first application is deployed on the first screen. In this way, the user can select from the information, and the user can operate on one screen, and the uninstallation of the first application deployed on other screens can be realized.

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

[0027] The second aspect provides an application uninstallation device, including: an acquisition unit configured to acquire a first uninstall instruction of a user for a first application on a first screen, the first application being deployed on a plurality of screens in a cockpit, the plurality of screens including the first screen; and a processing unit configured to, in response to the first uninstall instruction, perform an uninstall operation according to the type of the first application, the type of the first application including a clone type or an instance type.

[0028] With reference to the second aspect, in some implementations of the second aspect, the processing unit is specifically configured to: in response to the first uninstall instruction, when the type of the first application is the instance type, delete the icon of the first application on the first screen and not perform the uninstall operation on the first application.

[0029] With reference to the second aspect, in some implementations of the second aspect, the processing unit is further configured to, in response to acquiring a second uninstall instruction of the user for the first application on a second screen, perform the uninstall operation on the first application, the second screen being the only screen of the plurality of screens on which the first application is deployed.

[0030] In some implementations of the second aspect, in response to the first uninstall instruction, the processing unit is specifically configured to: in a case where the first application is a split application, the first screen is deployed with a main application corresponding to the first application, and a fourth screen is deployed with a second split application corresponding to the first application, delete an icon of the first application on the first screen.

[0031] In some implementations of the second aspect, in response to the first uninstall instruction, the processing unit is specifically configured to: in a case where the first application is a split application, the first screen is deployed with a main application corresponding to the first application, and a fourth screen is deployed with a second split application corresponding to the first application, delete an icon of the first application on the first screen.

[0032] In some implementations of the second aspect, the obtaining unit is further configured to obtain a third uninstall instruction of the first application on the fifth screen; and the processing unit is further configured to, in a case where the fifth screen is the only screen of the plurality of screens on which the icon of the first application is deployed, uninstall the main application in response to the third uninstall instruction.

[0033] In some implementations of the second aspect, the apparatus further includes: a control unit configured to, in response to the first uninstall instruction, control the first screen to display a first interface, 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; and a receiving unit configured to receive a first instruction of the user on the first interface; and the processing unit is configured to perform an uninstall operation according to the first instruction.

[0034] In some implementations of the second aspect, the apparatus further includes: a control unit configured to, in response to the first uninstall instruction, control the first screen to display a second interface, the second interface including information of the plurality of screens; and a receiving unit configured to receive a second instruction of the user on the first interface, the second instruction indicating at least one screen of the plurality of screens; and the processing unit is configured to perform an uninstall operation according to the second instruction.

[0035] In a third aspect, the present application provides an application uninstallation apparatus, which includes a processor and a memory, wherein the memory is configured to store instructions, and the processor is configured to execute the instructions stored in the memory, so that the apparatus performs any possible method in the first aspect.

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

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

[0038] In a sixth aspect, the present application provides a computer program product, which comprises computer program codes, and when the computer program codes are run on a computer, the computer is caused to execute any possible method in the first aspect.

[0039] It should be noted that the above computer program codes can be stored on the first storage medium in whole or in part, and the first storage medium can be packaged together with the processor or packaged separately from the processor, and the embodiments of the present application do not make a specific limitation in this regard.

[0040] In a seventh aspect, the present application provides a computer readable medium, which stores program codes, and when the computer program codes are run on a computer, the computer is caused to execute any possible method in the first aspect.

[0041] In an eighth aspect, the present application provides a chip system, which comprises a processor, and is configured to invoke computer programs or computer instructions stored in a memory, so as to cause the processor to execute any possible method in the first aspect.

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

[0043] With reference to the eighth aspect, in a possible implementation, the chip system further comprises the memory, and the memory stores the computer programs or the computer instructions.

[0044] In a ninth aspect, the present application provides a chip, which comprises a circuit, and the circuit is configured to execute any possible method in the first aspect. BRIEF DESCRIPTION OF DRAWINGS

[0045] Figure 1 is a functional block diagram of a vehicle provided by the embodiments of the present application;

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

[0047] Figure 3 is a schematic block diagram of a control system provided by the embodiments of the present application;

[0048] Figure 4 is still another schematic block diagram of a control system provided by the embodiments of the present application;

[0049] Figure 5is another schematic block diagram of a control system provided by embodiments of the present application.

[0050] Figure 6 is a schematic diagram of a data storage architecture provided by embodiments of the present application.

[0051] Figure 7 is a schematic flowchart of a control method provided by embodiments of the present application.

[0052] Figure 8 is a schematic diagram of a graphical user interface (GUI) provided by embodiments of the present application.

[0053] Figure 9 is another schematic diagram of a GUI provided by embodiments of the present application.

[0054] Figure 10 is another schematic diagram of a GUI provided by embodiments of the present application.

[0055] Figure 11 is another schematic diagram of a GUI provided by embodiments of the present application.

[0056] Figure 12 is another schematic diagram of a GUI provided by embodiments of the present application.

[0057] Figure 13 is another schematic diagram of a GUI provided by embodiments of the present application.

[0058] Figure 14 is another schematic diagram of a GUI provided by embodiments of the present application.

[0059] Figure 15 is a schematic flowchart of an application uninstallation method provided by embodiments of the present application.

[0060] Figure 16 is another schematic flowchart of an application uninstallation method provided by embodiments of the present application.

[0061] Figure 17 is a schematic block diagram of an application uninstallation apparatus provided by embodiments of the present application. DETAILED DESCRIPTION

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

[0063] Figure 1 is a functional block diagram of a vehicle provided by embodiments of the present application. As shown in Figure 1As shown, the vehicle 100 can include a display device 130 and a computing platform 150, wherein the display device 130 in the cabin is mainly divided into two categories, the first category is an on-board display screen; the second category is a projection display screen, for example, a head up display (HUD). The on-board display screen is a physical display screen, which is an important part of the in-vehicle infotainment system, and multiple display screens can be provided in the cabin, such as a digital instrument display screen, a central control screen, a display screen in front of a passenger (also referred to as a front passenger) at a co-driver position, a display screen in front of a left rear passenger, and a display screen in front of a right rear passenger, and even a vehicle window can be used as a display screen for display. The head up display, also known as a head-up display system. Mainly used for displaying driving information such as speed, navigation, etc. on a display device (such as a windshield) in front of the driver. In order to reduce the driver's line-of-sight shift time, avoid pupil changes caused by the driver's line-of-sight shift, and improve driving safety and comfort. The HUD, for example, includes a combiner-HUD (C-HUD) system, a windshield-HUD (W-HUD) system, and an augmented reality HUD (AR-HUD).

[0064] Part or all of the functions of the vehicle 100 can be controlled by the computing platform 150. The computing platform 150 can include processors 151-15n, which are circuits having a processing capability for signals. In one implementation, the processors can be circuits having an instruction reading and running capability, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a kind of microprocessor), a digital signal processor (DSP), and the like. In another implementation, the processors can be circuits having a certain function implemented by a logic relationship of hardware circuits, which is fixed or can be reconfigured, such as an application-specific integrated circuit (ASIC) or a programmable logic device (PLD) implemented hardware circuit, such as a field programmable gate array (FPGA). In the reconfigurable hardware circuit, the processor loads a configuration document to implement the hardware circuit configuration process, which can be understood as the process of the processor loading instructions to implement the functions of the above part or all units. In addition, the processor can also be a hardware circuit designed for artificial intelligence, which can be understood as a kind of ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), and the like. In addition, the computing platform 150 can also include a memory for storing instructions, and part or all of the processors 151-15n can call the instructions in the memory to implement corresponding functions.

[0065] Optionally, the above structure of the vehicle 100 is only schematic, and in actual application, each component in the vehicle 100 described above can be added or deleted according to actual needs.

[0066] Figure 2This is a schematic diagram of a vehicle cockpit scenario provided in an embodiment of this application. The smart cockpit includes 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. For example, Figure 1 The display device 130 shown may be one or more of displays 201 to 205. In some possible implementations, display 201 may also be a long screen extending into the passenger area. In addition, display 205 may also be a projection screen associated with a projector, which may be associated with a desktop launcher, through which applications projected by the projector onto the projection screen can be managed.

[0067] Figure 2 The cockpit can also be equipped with one or more cameras to capture images inside or outside the cockpit, such as cameras from a driver monitor system (DMS), a cabin monitor system (CMS), and a dashcam. These cameras can be the same 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.

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

[0069] To facilitate understanding of the technical solution of this application, the following is combined with... Figures 3 to 17 The solutions provided in the embodiments of this application are described in detail.

[0070] Figure 3 A schematic block diagram of a control system provided in an embodiment of this application is shown. Figure 3 As shown, this 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. This means that 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 services. For example, the system services may include basic services such as a desktop launcher, voice services, 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 understandable that the storage load required by the system services for each user space, as well as the computational load (e.g., CPU load) required to start and stop the user space, are relatively 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.

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

[0072] It should be noted that the user space involved in this application can be understood as the application's runtime environment. The applications deployed on any two of display devices 1 to n can be the same or different. Furthermore, Figure 3 Display device 1, display device 2, and display device n can be included in Figure 1 The positions of display device 1, display device 2, and display device n in the cockpit of the display device 130 shown can be referenced. Figure 2The setting positions of the display screens 201 to 205 are not described herein again.

[0073] It should be further noted that the application or application program referred to herein below refers to software running in the car machine system. The icon corresponding to the application program refers to the entry for using or accessing the application program. Application login or logout refers to the login or logout of an application account in the application program. Application exit refers to closing the application program or ending the process related to the application. The deployment of the application on a certain screen refers to deploying the access entry of the application on a certain screen, for example, the icon of the application program (or, the application), the main application of the application program or the split application of the application program can be deployed on a certain screen.

[0074] Figure 4 Another schematic block diagram of the control system provided by the embodiments of the present application is shown. As shown in the figure, the system includes a user management unit 410, an application management unit 420, a user center service unit 430 and a public data service unit 440. Figure 4 The functional characteristics of the units shown can be implemented by one or more processors in the computing platform 150. More specifically, the roles of the units in the system are as described in the following (I) to (IV) items: Figure 4 Figure 1

[0075] ​​The user management unit 410 is configured to provide an interface for a user to log in to the in-vehicle system and set the permissions of the system account. 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 configured to obtain a system account requesting to log in to the in-vehicle system or a system account requesting to log out of the in-vehicle system. In some embodiments, the system account can include at least three types: a vehicle owner account, an authorized account, and a visitor account. The vehicle owner account is an account of a legal owner of the vehicle, the authorized account is an account authorized by the legal owner of the vehicle, and the visitor account is an account not authorized by the legal owner of the vehicle. The permission management unit 412 is configured to obtain the permissions of the system account, which can be set by the user or can be default permissions of the in-vehicle system. In some embodiments, the permissions of the system account can include at least one of the following: whether to have the permission to install applications, whether to have the permission to uninstall applications, which applications are allowed to be uninstalled and / or installed, which applications are prohibited to be uninstalled and / or installed, whether to have access to the data storage area, and which applications can access the data storage area. For example, the system account 1 has the permission to install applications, can install all applications in the application store, and all applications can access the data storage area; the system account 2 cannot uninstall privacy-critical applications, and all applications cannot access the data storage area. For example, the legal owner of the vehicle can set the permissions of the authorized account and the visitor account, for example, when the vehicle owner account logs in to the in-vehicle system, the user can set the permissions of the authorized account and the visitor account through the human machine interface (HMI) of the vehicle, and the permission management unit 412 can obtain the permissions of the system account input by the user through the HMI.

[0076] The application management unit 420 is configured to provide an interface for the user to log in the application and access the data storage area. More specifically, the application management unit 420 includes an application login management unit 421, a user center management unit 422, and an access management unit 423. The application login management unit 421 is configured to manage and control the login of the application, and can obtain an application account for logging in an application, thereby controlling the application account to log in the application. The user center management unit 422 can obtain a system account currently logged in the vehicle machine system, and then send the information of the system account currently logged in the vehicle machine system to the application login management unit 421, which can log in one or more applications using the application account associated with the system account currently logged in the vehicle machine system. The user center management unit 422 can also obtain a system account logged out of the vehicle machine system, and then send the information of the system account logged out of the vehicle machine system to the application login management unit 421, which can control the application account associated with the system account to log out of one or more applications according to the logged-out system account. The access management unit 423 is configured to manage the permission of the application to read the data in the data storage area and store the data in the data storage area. The access management unit 423 can determine whether to send the data reading requirement or the data storage requirement of the application to the public data service unit 440 according to the permission of the application. In one example, an application has the permission to access the data storage area, and the access management unit 423 sends a data reading / storage request to the public data service unit 440 to request to read the data required by the application or write the data requested to be stored by the application in the data storage area. In another example, an application does not have the permission to access the data storage area, and the access management unit 423 ignores the data reading / storage request of the application, i.e., does not send the data reading / storage request to the public data service unit 440.

[0077] (Three) The user center service unit 430 is configured to manage system account and data access. More specifically, the user center service unit 430 comprises an account management unit 431 and a data management unit 432. The account management unit 431 is configured to control a system account to log in or log out of the vehicle system according to a request from the user management unit 410. In addition, after controlling the system account to log in or log out of the vehicle system, the user center service unit 430 can send a notification of login or logout to the application management unit 420. The data management unit 432 can obtain the permission information of the system account from the user management unit 410, determine the application that can access the data storage area under the system account according to the permission information of the system account, and send the information of the application that can access the data storage area under the system account to the public data service unit 440.

[0078] (Four) The public data service unit 440 is configured to provide data storage and reading services for applications. More specifically, the public data service unit 440 comprises a permission management module 441, a media library 442, and a file library 443. The permission management module 441 is configured to create an access path unit for a system account, and subsequently one or more applications used under the system account need to read and write data in the data storage area via the access path unit. Specifically, the vehicle system can be associated with one or more system accounts, and an access path unit is set for a system account that has the permission to access the data storage area among the one or more system accounts. At least one application running under the system account that sets the access path unit needs to store data in the data storage area or read data from the data storage area through the access path unit associated with the system account. A system account cannot read and write data in the data storage area through the access path unit of another system account. For example, application 1 under system account 1 stores picture 1 in the data storage area through access path unit 1 associated with system account 1, and application 1 under system account 2 does not store picture 1 in the data storage area through access path unit 2 associated with system account 2, so system account 2 cannot read picture 1 from the data storage area. In addition, for some applications (such as applications with low privacy or security requirements), data reading and writing can also be performed without going through the access path unit. Then, such an application stores data A under a system account, and the data A can also be read under another system account.

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

[0080] It should be understood that, Figure 4 The illustrated architecture is only exemplary. In the specific implementation process, Figure 4 The illustrated system can include more or fewer units. For example, Figure 4 The illustrated system can include multiple login management units 411, each of which corresponds to one of the multiple display devices of the vehicle; for another example, Figure 4 The illustrated system can also include multiple application management units 420, each of which is a login interface and / or a data access interface corresponding to an application. The multiple applications corresponding to the multiple application management units 420 can be deployed in one or more display devices of the vehicle. More specifically, when a user logs in to the vehicle system using system account 1 through a display device (such as display device a), the login management unit 411 corresponding to the display device a can send a login request to the user center service unit 430, the login request indicating that system account 1 requests to log in to the vehicle system through the display device a. Further, the user center service unit 430 controls system account 1 to log in to the vehicle system through the display device a according to the login request. And the user center service unit 430 sends a system account 1 login notification to at least one application management unit, the system account 1 login notification indicating that system account 1 has logged in to the vehicle system through the display device a, and the at least one application management unit controls the application accounts associated with system account 1 to log in to one or more applications associated with system account 1 deployed in the display device a. The at least one application management unit can include the application management units 420 corresponding to all applications installed in the vehicle system, or the at least one application management unit can also include the application management units 420 corresponding to only the applications deployed in the display device a.

[0081] It can be understood that, Figure 4The system architecture in one user space is shown. In actual implementation, multiple display devices in the vehicle can also be associated with multiple user spaces. Specifically, as shown in Figure 5 The display device 1, the display device 2, and the display device n (n is a positive integer) can be respectively associated with the user space 1 to the user space n', and n' is an integer greater than or equal to 2. In actual implementation, the running environment required by the application deployed in the display device 1 to the display device n in the same time period is provided by one user space. In different time periods, the running environment required by the application deployed in the display device 1 to the display device n can be provided by different user spaces, for example, in the time period 1, the running environment required by the application deployed in the display device 1 to the display device n is provided by the user space 1, and in the time period 2, the running environment required by the application deployed in the display device 1 to the display device n is provided by the user space n'. Wherein, the end time of the time period 1 is earlier than the start time of the time period 2, or the end time of the time period 1 coincides with the start time of the time period 2; or the end time of the time period 2 is earlier than the start time of the time period 1, or the end time of the time period 2 coincides with the start time of the time period 1. In some implementations, in the same time period, the running environment required by the application deployed in the display device 1 to the display device n can be provided by at least two user spaces, for example, the running environment required by the application deployed in the display device 1 is provided by the user space 1, and the running environment required by the application deployed in the display device 2 to the display device n is provided by the user space n'.

[0082] In actual implementation, in order to protect the privacy and security of different users under the same user space, the data read-write architecture is designed in the embodiments of the present application, which will be described in detail below. Figure 6

[0083] Figure 6 The schematic diagram of the data storage architecture provided by the embodiments of the present application is shown. As shown in Figure 6 ​As shown, the database includes an access path management unit and a data sandbox, which can include the aforementioned media library, file library, etc. The data sandbox is used to store data, and the access path management unit can include multiple access path units, each of which is associated with a system account. For example, in the case where system accounts a to system account N are all associated with the same user space (e.g., system accounts a to system account N are all registered in the user space, or have all logged into the in-vehicle system under the user space), the access path management unit can include access path units associated with system accounts a to system account N, such as system account a access path unit, system account N access path unit, etc. More specifically, system account a can log into multiple applications, including applications 1-m, which need to read and write data via the access path management unit. For example, at least one of applications 1-m stores pictures 11, 21, 31, and video 111 in the data sandbox via the system account a access path unit. More specifically, when at least one of applications 1-m stores data, a reference associated with the data (e.g., picture 11 reference, picture 21 reference, picture 31 reference, video 111 reference) is created and stored in the system account a access path unit, and the reference includes a field associated with system account a. When an application reads the aforementioned data, it needs to read the data via the reference associated with the data. For example, when application m requests to read video 111 in the data sandbox, it needs to read video 111 via the video 111 reference stored in the system account a access path unit.

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

[0085] The specific implementation of applications 1'-m' under system account N reading data in the data sandbox and storing data in the data sandbox can refer to the related description of applications 1-m reading and writing data, which will not be described here.

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

[0087] In actual implementation, the data reference stored in the aforementioned access path unit can be in the form of a field, which can include a system account name. For example, when application m' running under system account N stores data a in the data storage area, the field of "system account N" is added in the data storage path (or data reference), and a more specific data storage path can 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 field of "system account N" is added in the data reading path, and a more specific data reading path can be "system account N-application 1'-data a". It should be noted that the field representing the access path unit corresponding to one system account can be managed by the public data service unit 440, which is not perceived by the application. When the public data service unit 440 obtains a data access request of an application, it determines whether to respond to the data access request of the application according to whether the application is running under which system account and whether the application needs to read and write data in the data storage area through the access path unit. Therefore, the application running under system account N that does not need to read and write data in the data storage area through the access path unit, and the application running under other system accounts, cannot read the data stored by applications 1' to m' running under system account N.

[0088] In some implementations, for applications that do not need to read and write data in the data storage area through the access path unit (such as equity sharing type applications), a public storage area can be set for the aforementioned applications to read and write data. It should be noted that in the case where a system account is authorized to access the public storage area, the data in the public storage area can be read by any application running under the system account. It should be understood that the aforementioned data storage area includes the public storage area.

[0089] 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.

[0090] 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.

[0091] The above combination Figures 1 to 6 The schematic diagram of the system architecture provided in the embodiments of this application is described in detail. The control method provided in the embodiments of this application is described in detail below.

[0092] Figure 7 A schematic flowchart of a control method provided in an embodiment of this application is shown. This method can be... Figure 4 The system shown is executed, 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:

[0093] S711, the user management unit acquires user permission information 1.

[0094] In an example, the user management unit acquires the user permission information 1 in response to the user's setting in the case that the primary user logs in.

[0095] In another example, the user management unit acquires the user permission information 1 from an owner application deployed in an electronic device associated with the vehicle. The owner application can be an application that provides the owner of the vehicle with control of the vehicle, and / or an application that provides the owner of the vehicle with services such as information about the status of the vehicle. The electronic device being associated with the vehicle can include that the account for logging into the electronic device and the vehicle is the same, or that the accounts for logging into the electronic device and the vehicle are different but both are accounts of authorized users of the vehicle, or that the electronic device is authorized by an authorized user of the vehicle, and accordingly an association between the vehicle and the electronic device is established.

[0096] Illustratively, the primary user can be the account of the aforementioned owner system, and the user permission information 1 can include the permission of each system account in the plurality of system accounts. The plurality of 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 permission of each system account can refer to the description in the foregoing embodiments, and will not be described here.

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

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

[0099] S713, the user center service unit performs user permission processing.

[0100] Illustratively, the user center service unit determines the applications that can access the data storage area under each system account according to the user permission information 1, and further obtains user permission information 2. The user permission information 2 includes information of at least one application and an association between each application in the at least one application and a system account. The at least one application can include one or more applications that can access the data storage area under one or more system accounts.

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

[0102] Further, the public data service unit manages data access permissions of the applications running under each system account according to the user permission information 2. Illustratively, the public data service unit determines the applications that can access the data storage area according to the user permission information 2, and the data storage area can be accessed by these applications when running under which system account.

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

[0104] In yet some implementations, the at least one application includes a privacy-critical application, and 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 the system account can subsequently read and write data in the data storage area through the access path unit. More specific implementations of the privacy-critical application reading and writing data in the data storage area can refer to the foregoing Figure 6 Corresponding descriptions are not repeated here.

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

[0106] Illustratively, the system account A can be a vehicle owner system account, or can also be an account authorized by a legal owner of the vehicle. The system account A can be any one of the foregoing system accounts a to system account N, or the system account A can also be the foregoing system account 1 or system account 2.

[0107] The login instruction 1 is associated with the system account A, which can be understood as that the login instruction 1 requests to log in to the vehicle machine system using the system account A, or the login instruction 1 requests to log in to the vehicle machine system through the display device A using the system account A. Illustratively, the display device A can be any one of the foregoing display devices 1 to display device n.

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

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

[0110] Illustratively, the user center service unit logs in to the vehicle machine system using the system account A at the display device A.

[0111] S724, the application management unit groups the login application 1.

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

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

[0114] Exemplarily, the login notification of the application 1 indicates that the application account 1 logs in the application 1 under the system account A.

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

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

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

[0118] In yet some implementations, the user center service unit receives the login notification of the application 1, controls a prompt device to prompt information 1, the information 1 is used to prompt the user to determine whether the application 1 needs to be associated with the system account A, and performs S726 when it is determined that the user selects to associate the application 1 with the system account A.

[0119] It should be noted that S724 to S726 can be operations performed when the application 1 is logged in for the first time under the system account A; or, S724 to S726 can also be operations performed when the application account 1 is used to log in the application 1 for the first time under the system account A. For example, before S724 is performed, the application 1 has been associated with the system account A, but the application 1 is associated with the system account A in the case that the application account 2 is logged in, then after S724 to S726 are performed, the association relationship between the application 1 and the system account A is updated to: when the system account A is logged in, the application account 1 is used to log in the application 1.

[0120] In some implementations, after S723 is performed, S727 and S728 are performed. For example, in the case that the association processing of the system account A and the application has been performed in the early stage, after S723 is performed, S727 and S728 are performed.

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

[0122] Exemplarily, the system account A login notification indicates that the system account A logs in the vehicle machine system through the display device A.

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

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

[0125] Exemplarily, the at least one application includes application 3, and the application 3 is a benefit sharing type application, that is, in the case that the application 3 is deployed in the display device A, other display devices in the vehicle can deploy application 3', application 3'' and the like, and when any one of the applications 3, 3', 3'' is logged in using the application account, the remaining two applications are also logged in. That is, the application group a can also include the applications 3', 3'' and the like associated with the application 3 deployed in other display devices.

[0126] It should be noted that the applications deployed in different display devices can be different, and therefore, when the system account A logs in the vehicle system through different display devices, the applications logged in together with the system account A can be different.

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

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

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

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

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

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

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

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

[0135] In yet some implementations, the application group a includes at least one safety-critical application, which refers to an application that affects driving safety, such as a navigation application or an intelligent driving application. The intelligent driving application is an application for controlling intelligent driving functions, which can include, but are not limited to, the following functions that affect driving safety: auto parking assist (APA), auto valet parking (AVP), adaptive cruise control (ACC), lane cruise control (LCC), navigate cruise assist (NCA), front vehicle collision warning, lane departure warning, lane keeping assist, and rear vehicle collision warning. The NCA function refers to a function of controlling a vehicle to travel to a destination according to a navigation route, and enabling the vehicle to control passing through an intersection, lane changing, and gear shifting according to road information such as traffic lights.

[0136] In an example, when the vehicle is in a driving gear or a reverse gear, the application management unit group receives the log-out notification of the system account A, and then controls the applications in the application group a other than the intelligent driving application to log out. Further, when the vehicle is in a parking gear, the intelligent driving application is controlled to log out.

[0137] In another example, when the intelligent driving application is in a running state, the application management unit group receives the log-out notification of the system account A, and then controls the applications in the application group a other than the running intelligent driving application to log out. Further, when the intelligent driving application exits the running state, the intelligent driving application is controlled to log out.

[0138] In yet some implementations, the application group a includes at least one benefit sharing application, and when the application management unit group receives the log-out notification of the system account A, the application management unit group controls the applications in the application group a other than the at least one benefit sharing application to log out. For example, the at least one benefit sharing application includes the application 3, the application 3', and the application 3", and the application management unit group controls the applications in the application group a other than the application 3, the application 3', and the application 3" to log out.

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

[0140] In actual implementation, when the same system account logs in the vehicle machine system through different display devices in sequence, the system account can be controlled to log out the vehicle machine system and then log in the vehicle machine system when the system account logs in the vehicle machine system through the latter display device. Alternatively, the system account can be maintained in a state of continuously logging in the vehicle machine system in the foregoing process.

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

[0142] The application 2 associated with the system account B can be understood as: the application 2 is an application running under the system account B. For example, the system account 2 logs in the vehicle machine system through the display device B, and the application 2 can be an application deployed in the display device B. Exemplarily, the display device B can be any one of the display devices 1 to n.

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

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

[0145] Exemplarily, the public data service unit determines whether the application 2 associated with the system account B has the permission to access the data storage area, and when it is determined that the application 2 associated with the system account B has the permission to access the data storage area, the public data service unit further determines which data in the data storage area can be accessed by the application 2.

[0146] In some implementations, multiple system accounts log in the vehicle machine system through the display device B, and all of them can use the application 2. However, the permissions of the application 2 associated with different system accounts in the multiple system accounts are different. For example, the application 2 associated with the system account B and the system account C has the permission to access the data storage area, and the application associated with the system account D does not have the permission to access the data storage area. In addition, the application 2 associated with the system account B can access the public storage area, and the application 2 associated with the system account C does not have the permission to access the public storage area.

[0147] S743, when the authentication is passed, the public data service unit sends a data read-write result to the application management unit group.

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

[0149] In yet another example, the application 2 associated with the system account B does not need to access the data storage area through the access path unit, and the common data service unit stores the data requested to be stored by the application 2 in the common storage area and / or reads the data requested to be read by the application 2 from the common storage area.

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

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

[0152] It should be noted that when the system account A and the system account B are different, and the two log in the vehicle machine system through different display devices, S741 to S744 can be executed synchronously with any one of S721 to S723, S724 to S726, S727 to S728 or S731 to S735, or can be executed before any one of S721 to S723, S724 to S726, S727 to S728 or S731 to S735. In addition, S741 to S744 can also be executed synchronously with S711 to S714, or S741 to S744 can also be executed before S711 to S714.

[0153] It should be further noted that the application login or logout referred to in the present application refers to the application account logging in or logging out of the application, and the vehicle machine system login or logout referred to in the present application refers to the system account logging in or logging out of the vehicle machine system. In addition, the application logout is not the same as the application exit, the application logout refers to the application account logging in the application, and the application exit refers to the application related processes being all ended or exited, such as stopping the background running of the application. That is to say, after the application is logged out, the application can be exited or can not be exited, when the application is not exited, the display screen can display the running interface of the application, or the display screen can not display the running interface of the application, at this time, the application can be in a background running state.

[0154] In order to facilitate understanding of the control method provided by the embodiments of the present application, the following will be described in combination with Figures 8 to 14 The application scenarios and graphic user interfaces (GUIs) involved in the present application will be described in detail. Among them, Figures 8 to 14 The processing actions (such as control, response, etc.) or steps involved in the present application can be executed by Figure 1 the computing platform 150 shown in the figure, or can also be executed by the control system described above, for example, can be executed by the user center service unit 430.

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

[0156] As shown in (a) of FIG. 6, the user A is located in the main driver area of the vehicle cabin, and the content displayed by the display screen 201 (i.e., the center screen) can be as shown in (a) of FIG. 6. Figure 8 Figure 8 As shown in (a) of FIG. 6, the content displayed by the display screen 201 (i.e., the center screen) includes a content display area 810 and a function bar 820. Exemplarily, the content display area 810 includes: icons of a plurality of applications, each icon of an application being used to enable an application; a login control 801 (indicating that it is in a login state); and icons of Bluetooth function, Wi-Fi function, and cellular network signal, respectively used to indicate the vehicle Bluetooth on and / or connection state, Wi-Fi on state, and cellular network signal strength. The function bar 820 includes a home icon, a seat control, an air conditioner control, and a volume control, respectively used to control the content display area 810 to display the home page, control the on-off of the seat ventilation and / or adjust the air volume of the seat ventilation, control the on-off of the air conditioner and / or adjust the temperature and heating / cooling state of the air conditioner, adjust the air circulation state in the vehicle, and adjust the volume of the sound device.

[0157] As shown in (b) of FIG. 6, the user B is located in the right area of the second row of the vehicle cabin, and the content displayed by the display screen 204 (i.e., the right entertainment screen of the second row) can be as shown in (b) of FIG. 6. Figure 8 As shown in (b) of FIG. 6, the content displayed by the display screen 204 (i.e., the right entertainment screen of the second row) includes a content display area 830. Exemplarily, the content display area 830 includes: icons of a plurality of applications, each icon of an application being used to enable an application; a login control 801 (indicating that it is in a login state); and icons of Bluetooth function, Wi-Fi function, and cellular network signal, respectively used to indicate the vehicle Bluetooth on and / or connection state, Wi-Fi on state, and cellular network signal strength.

[0158] Figure 8 As shown in (b) of FIG. 6, the content displayed by the display screen 204 (i.e., the right entertainment screen of the second row) includes a content display area 830. Exemplarily, the content display area 830 includes: icons of a plurality of applications, each icon of an application being used to enable an application; a login control 801 (indicating that it is in a login state); and icons of Bluetooth function, Wi-Fi function, and cellular network signal, respectively used to indicate the vehicle Bluetooth on and / or connection state, Wi-Fi on state, and cellular network signal strength. Figure 8 As shown in (b) of FIG. 6, the content displayed by the display screen 204 (i.e., the right entertainment screen of the second row) includes a content display area 830. Exemplarily, the content display area 830 includes: icons of a plurality of applications, each icon of an application being used to enable an application; a login control 801 (indicating that it is in a login state); and icons of Bluetooth function, Wi-Fi function, and cellular network signal, respectively used to indicate the vehicle Bluetooth on and / or connection state, Wi-Fi on state, and cellular network signal strength.

[0159] Figure 8 As shown in (b) of FIG. 6, the content displayed by the display screen 204 (i.e., the right entertainment screen of the second row) includes a content display area 830. Exemplarily, the content display area 830 includes: icons of a plurality of applications, each icon of an application being used to enable an application; a login control 801 (indicating that it is in a login state); and icons of Bluetooth function, Wi-Fi function, and cellular network signal, respectively used to indicate the vehicle Bluetooth on and / or connection state, Wi-Fi on state, and cellular network signal strength.

[0160] ​​​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.

[0161] When the vehicle detects a user long-pressing action on the social application icon 801, it can display the following on the display screen 204: Figure 9 The GUI shown in (a) is shown in the image.

[0162] Figure 9 An example of a GUI provided in an embodiment of this application is shown.

[0163] like Figure 9 As shown in (a), in response to a user's long-press operation on 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 app type, share, and others. When the user's click on the uninstall function 902 is detected, the vehicle can display the following on display screen 204: Figure 9 The GUI shown in (b) is shown in the image.

[0164] like Figure 9 As shown in (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."

[0165] 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.

[0166] Figure 10 An example of a GUI provided in an embodiment of this application is shown.

[0167] like Figure 10 As shown in (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. This function bar 1001 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 following on display screen 201: Figure 10 The GUI shown in (b) is shown in the image.

[0168] like Figure 10 As shown in (b), in response to the user clicking the uninstall function 1002, the vehicle can determine whether the social application deployed on 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".

[0169] 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.

[0170] Figure 11 An example of a GUI provided in an embodiment of this application is shown.

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

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

[0173] 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.

[0174] When a long press operation is detected on the video application icon 1101 on the display screen 204, the display screen 204 can show, for example, the following: Figure 11 The GUI shown in (c) is shown in the image.

[0175] like Figure 11 As shown in (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 a user clicks the uninstall function 1103, the vehicle can display the following on display screen 204: Figure 11 The GUI shown in (d) is shown in the image.

[0176] like Figure 11 As shown in (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 entertainment screen has been deleted. You can also use the video application on the central control screen."

[0177] In the embodiments of this application, when performing the uninstall operation on the instance-type application, if the icon of the instance-type application displayed on the current display screen is not the icon of the last instance-type application, the vehicle can not perform the uninstall operation on the application entity (or the main application) of the instance-type application, but delete the icon of the instance-type application displayed on the display screen. In this way, the user can also use the instance-type application on other display screens displaying the icon of the instance-type application.

[0178] Figure 12 An example of the GUI provided by the embodiments of this application is shown.

[0179] As shown in (a) of FIG. 12, Figure 12 In response to the long-press operation of the user on the icon 1201 of the video application on the display screen 201, the vehicle can display a function bar 1202 including a plurality of functions such as uninstall, change application type, share and others through the display screen 201. When detecting the operation of the user clicking the uninstall function 1203, the vehicle can display the GUI as shown in (b) of FIG. 12 through the display screen 201. Figure 12

[0180] As shown in (b) of FIG. 12, Figure 12 In response to the operation of the user clicking the uninstall function 1203, the vehicle can determine whether the display screen 201 is the only display screen in the cabin deploying the icon of the video application. When determining that the display screen 201 is the only display screen in the cabin deploying the icon of the video application, the vehicle can delete the icon 1201 and perform the uninstall operation on the video application. At the same time, the vehicle can also control the display screen 201 to display the prompt information “video application has been uninstalled”.

[0181] In the embodiments of this application, when performing the uninstall operation on the instance-type application, if the icon of the instance-type application displayed on the current display screen is not the icon of the last instance-type application, the vehicle can not perform the uninstall operation on the application entity (or the main application) of the instance-type application, but delete the icon of the instance-type application displayed on the display screen. In this way, the user can also use the instance-type application on other display screens displaying the icon of the instance-type application.

[0182] The above describes the process of the user performing the uninstall operation on the application on each display screen, and the following describes the process of quickly uninstalling the application by taking the GUI shown in Figures 8 to 12 Figure 13 Figure 14 The above describes the process of the user performing the uninstall operation on the application on each display screen, and the following describes the process of quickly uninstalling the application by taking the GUI shown in

[0183] Figure 13 An example of the GUI provided by the embodiments of this application is shown.

[0184] As shown in (a) of FIG. 12, Figure 13 ​​​As shown in (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. This function bar 1301 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 following on display screen 204: Figure 13 The GUI shown in (b) is shown in the image.

[0185] like Figure 13 As shown in (b), in response to the user clicking the uninstallation 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.

[0186] 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.

[0187] 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.

[0188] Figure 14 An example of a GUI provided in an embodiment of this application is shown.

[0189] like Figure 14 As shown in (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. This function bar 1401 includes multiple functions, such as uninstall, change application type, share, and others. When a user's click on the uninstall function 1402 is detected, the vehicle can display the following on display screen 204: Figure 14 The GUI shown in (b) is shown in the image.

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

[0191] like Figure 14As shown in (b) of FIG. 14, in response to detecting that the user clicks the uninstall function 1402, the vehicle can display a prompt box 1403 on the display screen 204, where the prompt box 1403 includes prompt information "Detecting that two screens in the cabin are deployed with a video application, please select the screen that needs to be uninstalled" and highlights the controls corresponding to the center control screen and the second-row right entertainment screen where the video application is deployed.

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

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

[0194] For example, when detecting that the user clicks the controls corresponding to the center control screen and the second-row right entertainment screen and clicks the confirm control, the vehicle can perform the uninstall operation on the video application. After the uninstall operation on the video application is performed, the icons on the display screen 201 and the display screen 204 are deleted.

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

[0196] S1510, obtaining a first uninstall instruction of a user for a first application on a first screen, the first application being deployed on multiple screens in a cabin, and the multiple screens including the first screen.

[0197] For example, as shown in (a) of FIG. 9, the first uninstall instruction can be an operation of the user clicking the control 902. Figure 9

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

[0199] S1520, in response to the first uninstall instruction, performing an uninstall operation according to a type of the first application, the type of the first application including a clone type or an instance type.

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

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

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

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

[0204] 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.

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

[0206] 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.

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

[0208] 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.

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

[0210] 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.

[0211] For example, the first screen can be as follows: Figure 8 The fourth screen, as shown in (a) above, can be a display screen 201, such as... Figure 8 As shown in (b) of the diagram, the first application on display screen 204 can be a social application. In response to a user's uninstall 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 uninstallation operations on the main application and clone applications of that social application.

[0212] 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.

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

[0214] 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.

[0215] For example, such as Figure 13 As shown, the first interface can be as follows: Figure 13 The GUI shown in (b) 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.

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

[0217] For example, the second instruction can be an operation of a user clicking the control 1305. In response to the operation of the user clicking the control 1305, the vehicle can perform uninstallation of the video application. After the uninstallation of the video application is performed, the icons on the display screen 201 and the display screen 204 are both deleted.

[0218] Optionally, in response to the first uninstallation instruction, the uninstallation operation is performed according to a 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 of a user on the first interface, the second instruction indicating at least one screen of the plurality of screens; and performing the uninstallation operation according to the second instruction.

[0219] For example, the second interface can be a GUI as shown in (b) of FIG. 13, which includes prompt information “Two screens in the cabin are detected to deploy a video application. Please select the screen to be uninstalled” and controls corresponding to the center control screen and the second-row right entertainment screen on which the video application is deployed. Figure 14

[0220] For example, the second instruction can be an operation of a user clicking the control corresponding to the center control screen and clicking a confirm control. In response to the operation of the user clicking the control corresponding to the center control screen and clicking the confirm control, the vehicle can delete the icon of the video application displayed on the display screen 201 and not perform the uninstallation operation of the video application.

[0221] For example, the second instruction can be an operation of a user clicking the control corresponding to the second-row right entertainment screen and clicking a confirm control. In response to the operation of the user clicking the control corresponding to the second-row right entertainment screen and clicking the confirm control, the vehicle can delete the icon of the video application displayed on the display screen 204 and not perform the uninstallation operation of the video application.

[0222] For example, the second instruction can be an operation of a user clicking the control corresponding to the center control screen and the second-row right entertainment screen and clicking a confirm control. In response to the operation of the user clicking the control corresponding to the center control screen and the second-row right entertainment screen and clicking the confirm control, the vehicle can perform the uninstallation operation of the video application. After the uninstallation operation of the video application is performed, the icons on the display screen 201 and the display screen 204 are both deleted.

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

[0224] ​S1601, detecting an operation of uninstalling the application 1 deployed on the display screen 1 in the cabin by the user.

[0225] S1602, determining whether the application 1 is a split-type application.

[0226] For example, if the application 1 is a split-type application, S1603 can be performed; otherwise, S1609 can be performed.

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

[0228] For example, if the application 1 deployed on the display screen 1 is the main application corresponding to the application 1, S1604 can be performed; otherwise, S1605 can be performed.

[0229] S1604, determining whether there is still a split application corresponding to the application 1 that has not been uninstalled.

[0230] For example, if there is still a split application corresponding to the application 1 that has not been uninstalled, S1606 can be performed; otherwise, S1607 can be performed.

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

[0232] For example, if the icon of the application 1 deployed on the display screen 1 is the last icon, S1607 can be performed; otherwise, S1608 can be performed.

[0233] S1606, deleting the icon of the application 1 displayed on the current display screen 1.

[0234] For example, the display screen 1 can be the display screen 201 as shown in (a) of FIG. 1, and the first application can be a social application. In response to an uninstall instruction of the social application displayed on the display screen 201 by the user, when it is determined that the main application corresponding to the social application is deployed on the display screen 1 and the split 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. Figure 8

[0235] S1607, uninstalling the main application corresponding to the application 1.

[0236] For example, the display screen 1 can be the display screen 201 as shown in (a) and (b) of FIG. 1, and the first application can be a social application. In response to an operation of 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 the split application corresponding to the social application is not deployed on other display screens in the cabin (or the split applications of the social application have all been uninstalled), an uninstall operation on the main application corresponding to the social application can be performed. Figure 10 ​​

[0237] S1608, Uninstall the cloned application corresponding to application 1.

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

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

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

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

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

[0243] S1611, Uninstall application 1.

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

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

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

[0247] For example, the display screen 1 can be as follows: Figure 12 As shown in (a) and (b) above, the display screen 201 can be used for video applications. In response to a 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 can be performed on that video application.

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

[0249] For example, the display screen 1 can be as follows: Figure 11The application 1 can be a video application. In response to the operation of the user clicking the control 1103, when 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.

[0250] Figure 17 A schematic block diagram of an application uninstalling apparatus 1700 provided by an embodiment of the present application is shown. The apparatus 1700 comprises: an acquisition unit 1710, configured to acquire a first uninstalling instruction of a user for a first application on a first screen, the first application being deployed on a plurality of screens in a cockpit, the plurality of screens comprising the first screen; and a processing unit 1720, configured to, in response to the first uninstalling instruction, perform an uninstalling operation according to a type of the first application, the type of the first application comprising a clone type or an instance type.

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

[0252] Optionally, the processing unit 1720 is further configured to, in response to acquisition of a second uninstalling instruction of the user for the first application on a second screen, perform the uninstalling operation on the first application, the second screen being a screen of the plurality of screens on which the first application is uniquely deployed.

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

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

[0255] Optionally, the acquisition unit 1710 is further configured to acquire a third uninstalling instruction of the user for the first application on the fifth screen; and the processing unit 1720 is further configured to, in response to the third uninstalling instruction, when the fifth screen is a screen of the plurality of screens on which the icon of the first application is uniquely deployed, uninstall the main application.

[0256] Optionally, the apparatus 1700 further includes: a control unit, configured to control the first screen to display a first interface in response to the first uninstall instruction, the first interface including prompt information for prompting the user to delete an icon of the first application deployed on the first screen or uninstall the first application; a receiving unit, configured to receive a first instruction of the user on the first interface; and the processing unit 1720, configured to perform an uninstall operation according to the first instruction.

[0257] Optionally, the apparatus 1700 further includes: a control unit, configured to control the first screen to display a second interface in response to the first uninstall instruction, the second interface including information of the plurality of screens; a receiving unit, configured to receive a second instruction of the user on the first interface, the second instruction indicating at least one screen of the plurality of screens; and the processing unit 1720, configured to perform an uninstall operation according to the second instruction.

[0258] It should be understood that the division of each unit in the above apparatus is only a logical function division, and all or part of the units can be integrated into one physical entity, or can be physically separated. In addition, the units in the apparatus can be implemented in the form of processor calling software; for example, the apparatus includes a processor, a memory connected to the processor, and instructions stored in the memory, and the processor calls the instructions stored in the memory to implement any one of the above methods or to realize the functions of each unit of the apparatus, wherein the processor is, for example, a general processor such as a CPU or a microprocessor, and the memory is an internal memory of the apparatus or an external memory of the apparatus. Alternatively, the units in the apparatus can be implemented in the form of hardware circuit, and the functions of part or all of the units can be realized by the design of the hardware circuit, which can be understood as one or more processors; for example, in one implementation, the hardware circuit is an ASIC, and the functions of part or all of the units are realized by the design of the logical relationship of elements in the circuit; for example, in another implementation, the hardware circuit is a PLD, and taking an FPGA as an example, it can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by a configuration file, so as to realize the functions of part or all of the units. All units of the above apparatus can be implemented in the form of processor calling software, or all units can be implemented in the form of hardware circuit, or part of the units are implemented in the form of processor calling software, and the remaining part is implemented in the form of hardware circuit.

[0259] In embodiments of the present application, the processor is a circuit with signal processing capability. In one implementation, the processor can be a circuit with instruction reading and running capability, such as a CPU, a microprocessor, a GPU, or a DSP, etc. In another implementation, the processor can implement certain functions through a logic relationship of a hardware circuit, which is fixed or can be reconfigured. For example, the processor is an ASIC or a PLD implemented hardware circuit, such as an FPGA. In the reconfigurable hardware circuit, the processor loads a configuration document to implement the hardware circuit configuration. It can be understood that the processor loads instructions to implement the functions of the above units.

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

[0261] In addition, each unit in the above apparatus can be integrated together or can be independently implemented. In one implementation, these units are integrated together to implement a SoC. The SoC can include at least one processor for implementing any of the above methods or the functions of the units of the apparatus. The at least one processor can be different, such as including a CPU and an FPGA, a CPU and an artificial intelligence processor, a CPU and a GPU, etc.

[0262] Embodiments of the present application also provide an application offloading apparatus. The apparatus includes a processing unit and a storage unit, wherein the storage unit is configured to store instructions, and the processing unit is configured to execute the instructions stored in the storage unit, so that the apparatus performs the methods or steps performed by the above embodiments.

[0263] Optionally, if the apparatus is located in a vehicle, the above processing unit can be Figure 1 the processor 151-15n shown in FIG. 1.

[0264] Embodiments of the present application also provide an application offloading system. The application offloading system can include a computing platform and a plurality of screens. The computing platform can include the above application offloading apparatus 1700.

[0265] Embodiments of the present application also provide a vehicle. The vehicle can include the above application offloading apparatus 1700 or the application offloading system.

[0266] The embodiment of the present application further provides a computer program product, which comprises computer program codes, and when the computer program codes run on a computer, the computer program codes make the computer execute the method in the above embodiment.

[0267] The embodiment of the present application further provides a computer readable medium, which stores program codes, and when the program codes run on a computer, the program codes make the computer execute the method in the above embodiment.

[0268] The embodiment of the present application further provides a chip, which comprises a circuit for executing the noise reduction method in the above embodiment.

[0269] In the implementation process, each step of the above method can be completed by integrated logic circuits of hardware in the processor or instructions in the form of software. The method disclosed in the embodiment of the present application can be directly embodied as hardware processor execution completion or combined execution completion by hardware and software modules in the processor. The software module can be located in a mature storage medium in the art such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable read-only memory, register or the like. The storage medium is located in the memory, and the processor reads the information in the memory and combines the hardware to complete the steps of the above method. To avoid repetition, it will not be described in detail here.

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

[0271] It should also be understood that in various embodiments of the present application, the size of the serial number of each process described above does not mean the execution order, and the execution order of each process should be determined according to its function and inherent logic, and should not constitute any limitation on the implementation process of the embodiment of the present application.

[0272] Those of ordinary skill in the art can realize that the units and algorithm steps of each example described in combination with the embodiments disclosed herein can be realized in electronic hardware or a combination of computer software and electronic hardware. Whether the functions are executed 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 the present application.

[0273] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the above-described system, device and unit can refer to the corresponding process in the foregoing method embodiment, which will not be described here.

[0274] In several embodiments provided in the present application, it should be understood that the disclosed system, device and method can be implemented in other manners. For example, the described device embodiments are merely schematic. The division of the units is merely logical function division. There can be other division manners in actual implementation. For example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the displayed or discussed mutual couplings or direct couplings or communication connections can be indirect couplings or communication connections through some interfaces, devices or units, and can be in electrical, mechanical or other forms.

[0275] The units described as separate components can or can not be physically separate, and the components shown as units can or can not be physical units, i.e., can be located in one place, or can be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the embodiment.

[0276] In addition, each functional unit in the various embodiments of the present application can be integrated into a processing unit, or each unit can be a physically separate unit, or two or more units can be integrated into one unit.

[0277] If the functions are realized in the form of software function units and sold or used as independent products, they can be stored in a computer readable storage medium. Based on this understanding, the technical solutions of the present application can be embodied in the form of a software product, and the computer software product is stored in a storage medium, and includes a number of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and various program code storage media.

[0278] The above is merely specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art can easily think of changes or replacements within the technical scope disclosed in the present application, which should be covered. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. An application offloading method, characterized by, The method comprises: obtaining a first uninstall instruction of a user for a first application on a first screen, the first application being deployed on a plurality of screens in a cockpit, the plurality of screens comprising the first screen; in response to the first uninstall instruction, performing an uninstall operation according to a type of the first application, the type of the first application comprising a clone type; the response to the first uninstall instruction, according to the type of the first application, performing an uninstall operation, comprising: when the first application is a clone application, the first screen is deployed with a main application corresponding to the first application, and a fourth screen is deployed with a second clone application corresponding to the first application, in response to the first uninstall instruction, deleting an icon of the first application on the first screen and not performing an uninstall operation for the main application and the second clone application.

2. The method of claim 1, wherein, The type of the first application also comprises an instance type, and the uninstall operation according to the type of the first application comprises: in response to the first uninstall instruction, when the type of the first application is an instance type, deleting the icon of the first application on the first screen and not performing the uninstall operation on the first application.

3. The method of claim 2, wherein, The method further comprises: in response to obtaining a second uninstall instruction of a user for a first application on a second screen, performing an uninstall operation on the first application, the second screen being the only screen of the plurality of screens on which the first application is deployed.

4. The method of claim 1, wherein, in response to the first uninstall instruction, deleting the icon of the first application on the first screen and not performing the uninstall operation on the first application, comprising: when the type of the first application is a clone type, the first screen is deployed with a first clone application corresponding to the first application, and a third screen is deployed with a main application corresponding to the first application, in response to the first uninstall instruction, deleting the icon of the first application on the first screen and uninstalling the first clone application.

5. The method according to claim 1 or 4, characterized in that, The method further comprises: obtaining a third uninstall instruction of a user for the first application on a fifth screen; when the fifth screen is the only screen of the plurality of screens on which the icon of the first application is deployed, in response to the third uninstall instruction, uninstalling the main application.

6. The method according to any one of claims 1 to 4, characterized in that, The response to the first uninstall instruction, according to the type of the first application, performing an uninstall operation, comprises: in response to the first uninstall instruction, controlling the first screen to display a first interface, the first interface comprising prompt information for prompting the user to delete the icon of the first application deployed on the first screen or uninstall the first application; receiving a first instruction of the user on the first interface; performing the uninstall operation according to the first instruction.

7. The method according to any one of claims 1 to 4, characterized in that, The response to the first uninstall instruction, according to the type of the first application, performing an uninstall operation, comprises: in response to the first uninstall instruction, controlling the first screen to display a second interface, the second interface comprising information of the plurality of screens; receiving a second instruction of the user on the second interface, the second instruction indicating at least one screen of the plurality of screens; performing the uninstall operation according to the second instruction.

8. An application offloading apparatus, characterized by comprising: The method comprises: The acquisition unit is configured to acquire a first uninstall instruction of a user for a first application on a first screen, the first application being deployed on a plurality of screens in a cockpit, and the plurality of screens including the first screen; The processing unit is configured to, in response to the first uninstall instruction, perform an uninstall operation according to a type of the first application, the type of the first application including a clone type; The processing unit is specifically configured to: when the first application is a clone application, the first screen is deployed with a main application corresponding to the first application, and a fourth screen is deployed with a second clone application corresponding to the first application, in response to the first uninstall instruction, deleting an icon of the first application on the first screen and not performing the uninstall operation on the main application and the second clone application.

9. The apparatus of claim 8, wherein, The type of the first application further includes an instance type, and the processing unit is specifically configured to: in response to the first uninstall instruction, when the type of the first application is the instance type, deleting the icon of the first application on the first screen and not performing the uninstall operation on the first application.

10. The apparatus of claim 9, wherein The processing unit is further configured to, in response to acquiring a second uninstall instruction of a user for the first application on a second screen, perform an uninstall operation on the first application, the second screen being a screen of the plurality of screens on which the first application is uniquely deployed.

11. The apparatus of claim 8, wherein, The processing unit is specifically configured to: when the type of the first application is the clone type, the first screen is deployed with a first clone application corresponding to the first application, and a third screen is deployed with a main application corresponding to the first application, in response to the first uninstall instruction, deleting the icon of the first application on the first screen and uninstalling the first clone application.

12. The apparatus of claim 8 or 11, wherein The acquisition unit is further configured to acquire a third uninstall instruction of a user for the first application on a fifth screen; The processing unit is further configured to, in response to the third uninstall instruction, uninstall the main application when the fifth screen is a screen of the plurality of screens on which the icon of the first application is uniquely deployed.

13. The apparatus of any one of claims 8-11, wherein, The apparatus further includes: a control unit configured to, in response to the first uninstall instruction, control the first screen to display a first interface, 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 instruction of the user on the first interface; The processing unit is configured to perform the uninstall operation according to the first instruction.

14. The apparatus of any one of claims 8-11, wherein, The apparatus further includes: a control unit configured to, in response to the first uninstall instruction, control the first screen to display a second interface, the second interface including information of the plurality of screens; a receiving unit configured to receive a second instruction of the user on the second interface, the second instruction indicating at least one screen of the plurality of screens; The processing unit is configured to perform the uninstall operation according to the second instruction.

15. An application offloading apparatus, characterized by comprising: The apparatus further includes: a memory configured to store a computer program; a processor to execute a computer program stored in the memory to cause the apparatus to perform the method of any of claims 1 to 7.

16. An application offload system, comprising: a computing platform comprising the apparatus of any of claims 8 to 15.

17. A vehicle characterized by comprising: the apparatus of any of claims 8 to 15, or the system of claim 16.

18. A computer-readable storage medium, characterized in that, instructions stored thereon, the instructions, when executed by a processor, cause the processor to implement the method of any of claims 1 to 7.

19. A computer program product, characterised in that, the computer program product comprises computer program code to, when run on a computer, cause the computer to implement the method of any of claims 1 to 7.

20. A chip, characterized by the chip comprises circuitry to perform the method of any of claims 1 to 7.

Images