Control method and apparatus, and vehicle

Abstract

A control method and apparatus, and a vehicle. The method comprises: in response to an event of a first user account logging out of an in-vehicle infotainment system of a vehicle, controlling, on the basis of an association relationship between the first user account and applications, the logout of a first group of applications associated with the first user account in the in-vehicle infotainment system, wherein the vehicle comprises one or more display screens, and the first group of applications are deployed on the one or more display screens. The present solution can be applied to the technical field of computers and / or the field of intelligent vehicles such as new energy vehicles and electric vehicles. When a certain user account logs out of the in-vehicle infotainment system, the applications associated with the user account are controlled to be logged out together, eliminating the need for a user to manually log out of the plurality of applications one by one, which facilitates improving the multimedia experience of the user using a vehicle-mounted display screen, facilitates improving the convenience of the user using the applications, and ensures the privacy security of the user.

Description

Control methods, devices and vehicles Technical Field

[0001] This application relates to the field of computer technology, and more specifically, to a control method, apparatus, and vehicle. Background Technology

[0002] As vehicles become more intelligent and connected, vehicle cockpits are gradually evolving into smart cockpits centered on human-machine interaction and featuring multi-screen interaction. However, the multimedia experience offered by in-vehicle displays in current smart cockpits still needs improvement.

[0003] Therefore, a user-friendly display control solution is urgently needed.

[0004] Summary of the Invention

[0005] This application provides a control method, apparatus, and vehicle that helps improve the multimedia experience of users using in-vehicle displays, enhances the convenience of users using applications, and protects user privacy and security.

[0006] In one aspect, a control method is provided that can be executed by a vehicle, for example, by the vehicle's computing platform, or by a chip or circuitry used in the vehicle.

[0007] The method includes: in response to an event that a first user account logs out on the vehicle's infotainment system, controlling the logout of a first group of applications associated with the first user account based on the association between the first user account and applications; wherein the first group of applications includes at least one application, the vehicle includes one or more displays, and the at least one application is deployed on one or more displays.

[0008] It should be noted that controlling the logout of the first group of applications can be understood as controlling the application account to log out of each application in the first group of applications.

[0009] In the above technical solution, when the first user account is detected to have logged out of the vehicle system, controlling at least one application related to the first user account to log out can prevent other users from directly using the aforementioned at least one application, which helps to ensure the user's privacy and security.

[0010] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: controlling at least one application in the first group of applications to exit.

[0011] It's important to note that logging out of an application and exiting an application are not the same. Logging out of an application means logging out of the account used to log into the application, while exiting an application means that all processes related to the application have ended or exited, such as stopping the application from running in the background. In other words, after logging out of an application, the application may or may not exit. If the application does not exit, the screen may display the application's running interface, or the screen may not display the application's running interface, in which case the application can run in the background.

[0012] In the above technical solution, controlling the application to exit after the application logs out helps to save the computing resources and energy required for the application to run.

[0013] In conjunction with the first aspect, in some implementations of the first aspect, the first group of applications includes safety-critical applications, and the method further includes: when the first user account logs out of the vehicle system, if the vehicle is in drive or reverse gear, maintaining the running state of the safety-critical applications.

[0014] In some implementations, safety-critical applications can be applications related to driving safety, such as navigation applications or intelligent driving applications.

[0015] In the above technical solution, when the vehicle is in motion or the intelligent driving application is running, the safety-critical application is not logged out along with the first user account, which helps to ensure the driving safety of the vehicle.

[0016] In conjunction with the first aspect, in some implementations of the first aspect, safety-critical applications include navigation applications or intelligent driving applications, which control the logout and / or exit of safety-critical applications when the vehicle shifts to park.

[0017] In the above technical solution, controlling the logout and / or exit of safety-critical applications when the vehicle is switched to the parking position helps to protect user privacy and security, and can reduce the resources required for the vehicle system to operate.

[0018] In conjunction with the first aspect, in some implementations of the first aspect, if the vehicle is in drive or reverse gear, the user is prompted that the first user account cannot be logged out.

[0019] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: in response to an event of a first user account logging in on the vehicle system, logging in to a second set of applications associated with the first user account based on the association between the first user account and the applications; wherein the second set of applications is deployed on one or more displays, and the second set of applications includes the first set of applications.

[0020] In the above technical solution, when logging into the first user account in the vehicle system, the applications associated with the first user account are also logged in simultaneously, eliminating the need for the user to manually log into multiple applications sequentially. This helps improve the user's multimedia experience when using the in-vehicle display screen and enhances the convenience of logging into applications.

[0021] In conjunction with the first aspect, in some implementations of the first aspect, the second group of applications includes the first type of applications, which are privacy-critical applications.

[0022] In conjunction with the first aspect, in some implementations of the first aspect, privacy-critical applications are those that require data isolation within a single user space.

[0023] In conjunction with the first aspect, in some implementations of the first aspect, one or more displays include a first display, and when a first user account logs into the vehicle system through the first display, a first type of application in the second group of applications is deployed on the first display.

[0024] In some implementations, when the second group of applications are all applications that require data isolation, the second group of applications are all deployed on the first display screen, and are deployed exclusively on the first display screen.

[0025] In the above technical solution, when a user logs into their user account through a display screen of the vehicle's infotainment system, the application account associated with that user account will also log in on that display screen. Furthermore, the application account associated with the user account will not log in on other displays. This helps improve the convenience of user application login and protects the privacy and security of user accounts. For example, the application account can correspond to a privacy-critical application or an application with data isolation requirements.

[0026] In conjunction with the first aspect, in some implementations of the first aspect, one or more displays include a second display, and when a first user account logs into the vehicle system through the second display, the first type of application in the second group of applications is deployed on the second display.

[0027] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: responding to an event that the first user account logs into the vehicle system via the second display screen, controlling the logout of the second set of applications associated with the first user account on the first display screen; and logging into the third set of applications associated with the first user account on the second display screen, wherein the third set of applications is deployed on at least the second display screen.

[0028] In the above technical solution, when the same user account logs into the vehicle system through two displays one after the other, controlling the logout of the application on the first display helps to protect the user's privacy and security, and in turn, controlling the login of the application on the second display helps to improve the user's convenience in using the application.

[0029] In conjunction with the first aspect, in some implementations of the first aspect, the third set of applications is the same as the second set of applications; or, when the first display screen is a safety-critical screen and the second display screen is a non-safety-critical screen, at least one application in the third set of applications is different from the second set of applications; or, when the first display screen is a non-driving safety-critical screen and the second display screen is a safety-critical screen, the third set of applications is a proper subset of the second set of applications.

[0030] In conjunction with the first aspect, in some implementations of the first aspect, the second group of applications also includes a first application and a second application, wherein the first application and the second application are multiple instances of the same application deployed on the third display screen and the fourth display screen respectively, and both the first application and the second application are logged into the first application account, and one or more displays include the third display screen and the fourth display screen.

[0031] Among them, the first application and the second application are applications that do not require data isolation, and one of the third display screen and the fourth display screen can be a display screen that has deployed the first type of application in the second group of applications.

[0032] In the above technical solution, for applications that do not require data isolation, when a user account logs into the vehicle system through a certain display screen, the same application deployed on that display screen and other display screens can be controlled to log in together, so as to facilitate the sharing of the rights and interests of the application account that logs into the application.

[0033] In conjunction with the first aspect, in some implementations of the first aspect, the vehicle system includes a third application associated with a second user account, and the method further includes: logging into the third application in response to an event of the second user account logging into the vehicle system.

[0034] In the above technical solution, when different user accounts log in to the vehicle system through the same display screen, they can use different application accounts to log in to the same application on the display screen, which helps to protect the privacy and security of user accounts.

[0035] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: obtaining a first access request from a fourth application under a first user account, the first access request being used to request reading or writing first data in a first area, the first user account being one of multiple user accounts, each user account being associated with a sub-data storage area, and the multiple sub-data storage areas associated with multiple user accounts belonging to the same user space; when the fourth application is a first type of application, reading or writing the first data through the first sub-data storage area corresponding to the first user account according to the first access request, the multiple sub-data storage areas including the first sub-data storage area.

[0036] In the above technical solution, when multiple user accounts used to log in to the vehicle system are associated with the same user space, for applications with data privacy requirements, storing the data requested by the application in the data storage area through the sub-data storage area can prevent applications under other user accounts from reading the data, thus helping to protect the data privacy and security of each user account.

[0037] In conjunction with the first aspect, in some implementations of the first aspect, the multiple user accounts also include a third user account, which is associated with a second sub-data storage area in the multiple sub-data storage areas. The method further includes: obtaining a second access request from the application of the third user account; and rejecting the second access request when the first data is written through the first sub-data storage area and the second access request is used to request reading the first data.

[0038] In the above technical solution, the application under the second user account cannot read the data stored by the first user account through the first sub-data storage area, which helps to achieve data isolation at the user account level, thereby improving the privacy and security of user data.

[0039] In conjunction with the first aspect, in some implementations of the first aspect, the first group of applications does not include the second type of applications, which are applications that do not require data isolation.

[0040] In the above technical solution, the second type of application does not log out with the first user account, which helps to ensure the continuous sharing of the rights and interests of the second type of application. That is, it does not affect the continuous use of the same second type of application on other displays, which helps to improve the user's car experience.

[0041] Secondly, a control method is provided that can be executed by a vehicle, for example, by the vehicle's computing platform, or by a chip or circuitry used in the vehicle.

[0042] The method includes: in response to an event of a first user account logging into the vehicle's infotainment system, logging into a second set of applications associated with the first user account based on the association between the first user account and applications; wherein the second set of applications includes at least one application, the vehicle includes one or more displays, and the at least one application is deployed on one or more displays.

[0043] In conjunction with the second aspect, in some implementations of the second aspect, the method further includes: in response to an event that the first user account logs out on the vehicle system, controlling the logout of a first group of applications associated with the first user account based on the association relationship between the first user account and application accounts, wherein the second group of applications includes the first group of applications.

[0044] In conjunction with the second aspect, in some implementations of the second aspect, the method further includes: controlling at least one application in the first group of applications to exit.

[0045] In conjunction with the second aspect, in some implementations of the second aspect, the first group of applications includes safety-critical applications, and the method further includes: when the first user account logs out of the vehicle system, if the vehicle is in drive or reverse gear, maintaining the running state of the safety-critical applications.

[0046] In conjunction with the second aspect, in some implementations of the second aspect, safety-critical applications, including navigation applications or intelligent driving applications, are controlled to log out and / or exit when the vehicle shifts to the parking gear.

[0047] In conjunction with the second aspect, in some implementations of the second aspect, if the vehicle is in drive or reverse gear, the user is prompted that the first user account cannot be logged out.

[0048] In conjunction with the second aspect, in some implementations of the second aspect, the first group of applications does not include the second type of applications, which are applications that do not require data isolation.

[0049] In conjunction with the second aspect, in some implementations of the second aspect, the second group of applications includes the first type of applications, which are privacy-critical applications.

[0050] In conjunction with the second aspect, in some implementations of the second aspect, privacy-critical applications are those that require data isolation within a single user space.

[0051] In conjunction with the second aspect, in some implementations of the second aspect, one or more displays include a first display, and when a first user account logs into the vehicle system through the first display, the first type of application in the second group of applications is deployed on the first display.

[0052] In conjunction with the second aspect, in some implementations of the second aspect, one or more displays include a second display, and when the first user account logs into the vehicle system through the second display, the first type of application in the second group of applications is deployed on the second display.

[0053] In conjunction with the second aspect, in some implementations of the second aspect, the method further includes: in response to an event that the first user account logs into the vehicle system via the second display screen, controlling the logout of the second set of applications associated with the first user account on the first display screen; and logging into the third set of applications associated with the first user account on the second display screen, wherein the third set of applications is deployed on at least the second display screen.

[0054] In conjunction with the second aspect, in some implementations of the second aspect, the third set of applications is the same as the second set of applications; or, when the first screen is a safety-critical screen and the second screen is a non-safety-critical screen, at least one application in the third set of applications is different from the second set of applications; or, when the first screen is a non-driving safety-critical screen and the second screen is a safety-critical screen, the third set of applications is a proper subset of the second set of applications.

[0055] In conjunction with the second aspect, in some implementations of the second aspect, the second group of applications also includes a first application and a second application, wherein the first application and the second application are multiple instances of the same application deployed on the third display screen and the fourth display screen respectively, and both the first application and the second application are logged into the first application account, and one or more displays include the third display screen and the fourth display screen.

[0056] In conjunction with the second aspect, in some implementations of the second aspect, the vehicle system includes a third application associated with the second user account, and the method further includes: logging into the third application in response to an event of the second user account logging into the vehicle system.

[0057] In conjunction with the second aspect, in some implementations of the second aspect, the method further includes: obtaining a first access request of a fourth application under a first user account, the first access request being used to request reading or writing first data, each user account being associated with a sub-data storage area, and the multiple sub-data storage areas associated with multiple user accounts belonging to the same user space; when the fourth application is a first type of application, reading or writing the first data through the first sub-data storage area corresponding to the first user account according to the first access request, the multiple sub-data storage areas including the first sub-data storage area.

[0058] In conjunction with the second aspect, in some implementations of the second aspect, the multiple user accounts also include a third user account, which is associated with a second sub-data storage area in the multiple sub-data storage areas. The method further includes: obtaining a second access request from the application of the third user account; and rejecting the second access request when the first data is written through the first sub-data storage area and the second access request is used to request reading the first data.

[0059] Thirdly, a control method is provided that can be executed by a vehicle, for example, by the vehicle's computing platform, or by a chip or circuitry used in the vehicle.

[0060] The method includes: obtaining a first access request for a fourth application under a first user account, the first access request being used to request reading or writing first data, each user account being associated with a sub-data storage area, and the multiple sub-data storage areas associated with multiple user accounts belonging to the same user space; when the fourth application is a first type of application, reading or writing the first data through the first sub-data storage area corresponding to the first user account according to the first access request, the multiple sub-data storage areas including the first sub-data storage area.

[0061] In conjunction with the third aspect, in some implementations of the third aspect, the multiple user accounts also include a third user account, which is associated with a second sub-data storage area in the multiple sub-data storage areas. The method further includes: obtaining a second access request from the application of the third user account; and rejecting the second access request when the first data is written through the first sub-data storage area and the second access request is used to request reading the first data.

[0062] In conjunction with the third aspect, in some implementations of the third aspect, the method further includes: obtaining a third access request from a second type of application under the first user account; and rejecting the third access request when the first data is written through the first sub-data storage area and the third access request is used to request reading the first data.

[0063] In conjunction with the third aspect, in some implementations of the third aspect, the method further includes: obtaining a fourth access request from a fourth application, the fourth access request being used to request the reading of second data, the second data being data stored by a second type of application under the first user account; and reading the second data according to the fourth access request.

[0064] In conjunction with the third aspect, in some implementations of the third aspect, the method further includes: obtaining a fifth access request from a sixth application under the first user account, the fifth access request being used to request reading the first data; when the first data is written through the first sub-data storage area, and the sixth application is an application that needs to pass through the first sub-data storage area when storing data, reading the first data according to the fifth access request.

[0065] In conjunction with the third aspect, in some implementations of the third aspect, in response to an event of a first user account logging into the vehicle's infotainment system, a second set of applications associated with the first user account is logged in based on the association between the first user account and the applications; wherein the second set of applications includes at least one application, the vehicle includes one or more displays, and at least one application is deployed on one or more displays.

[0066] In conjunction with the third aspect, in some implementations of the third aspect, the method further includes: in response to an event that the first user account logs out on the vehicle's infotainment system, controlling the logout of a first group of applications associated with the first user account based on the association between the first user account and application accounts, wherein the second group of applications includes the first group of applications.

[0067] In conjunction with the third aspect, in some implementations of the third aspect, the method further includes: controlling the exit of at least one application in the first group of applications.

[0068] In conjunction with the third aspect, in some implementations of the third aspect, the first group of applications includes safety-critical applications, and the method further includes: when the first user account logs out of the vehicle system, if the vehicle is in drive or reverse gear, maintaining the running state of the safety-critical applications.

[0069] In conjunction with the third aspect, in some implementations of the third aspect, safety-critical applications, including navigation applications or intelligent driving applications, control the logout and / or exit of safety-critical applications when the vehicle shifts to park.

[0070] In conjunction with the third aspect, in some implementations of the third aspect, if the vehicle is in drive or reverse gear, the user is prompted that the first user account cannot be logged out.

[0071] In conjunction with the third aspect, in some implementations of the third aspect, the first group of applications does not include the second type of applications, which are applications that do not require data isolation.

[0072] In conjunction with the third aspect, in some implementations of the third aspect, the second group of applications includes the first type of applications, which are privacy-critical applications.

[0073] In conjunction with the third aspect, in some implementations of the third aspect, privacy-critical applications are those that require data isolation within a single user space.

[0074] In conjunction with the third aspect, in some implementations of the third aspect, one or more displays include a first display, and when a first user account logs into the vehicle system through the first display, the first type of application in the second group of applications is deployed on the first display.

[0075] In conjunction with the third aspect, in some implementations of the third aspect, one or more displays include a second display, and when the first user account logs into the vehicle system through the second display, the first type of application in the second group of applications is deployed on the second display.

[0076] In conjunction with the third aspect, in some implementations of the third aspect, the method further includes: responding to an event that the first user account logs into the vehicle system via the second display screen, controlling the logout of the second set of applications associated with the first user account on the first display screen; and logging into the third set of applications associated with the first user account on the second display screen, wherein the third set of applications is deployed on at least the second display screen.

[0077] In conjunction with the third aspect, in some implementations of the third aspect, the third group of applications is the same as the second group of applications; or, when the first screen is a safety-critical screen and the second screen is a non-safety-critical screen, at least one application in the third group of applications is different from the second group of applications; or, when the first screen is a non-driving safety-critical screen and the second screen is a safety-critical screen, the third group of applications is a proper subset of the second group of applications.

[0078] In conjunction with the third aspect, in some implementations of the third aspect, the second group of applications also includes a first application and a second application. The first application and the second application are multiple instances of the same application deployed on the third display screen and the fourth display screen, respectively, and both the first application and the second application are logged into the first application account. One or more displays include the third display screen and the fourth display screen.

[0079] In conjunction with the third aspect, in some implementations of the third aspect, the vehicle system includes a third application associated with a second user account, and the method further includes: logging into the third application in response to an event of the second user account logging into the vehicle system.

[0080] Fourthly, embodiments of this application provide a control device. This control device may be a device or apparatus with a chip, or a device or apparatus with integrated circuitry. It should be noted that, in this application, the term "control device" can refer to the control device itself, or to a chip, functional module, or integrated circuit within the control device that performs the method provided in this application. This device is used to execute the method provided in any of the first to third aspects. Specifically, the device may include units and / or modules for executing the method provided in any implementation of the first to third aspects.

[0081] When the apparatus is used to perform the method provided in either the first or second aspect, the apparatus may include a processing unit (or processing module). Optionally, the apparatus may further include a transceiver unit (or transceiver module). In some implementations, the transceiver unit includes an acquisition unit, which may be a receiving unit within the transceiver unit.

[0082] When the apparatus is used to perform the method provided by any of the implementations of the third aspect, the apparatus may include an acquisition unit and a processing unit.

[0083] Fifthly, a control device is provided, comprising: a processor for executing a computer program stored in the memory, such that the device performs the method in any of the possible implementations of the first to third aspects described above.

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

[0085] Sixthly, a computer program product is provided, the computer program product comprising: computer program code, which, when executed on a computer or processor, causes the computer or processor to perform the method in any of the possible implementations of the first to third aspects.

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

[0087] In a seventh aspect, a computer-readable storage medium is provided, the computer-readable medium storing instructions that, when executed by a processor, cause the processor to implement the method in any of the possible implementations of the first to third aspects.

[0088] Eighthly, a chip is provided, the chip including circuitry for performing the methods in any of the possible implementations of the first to third aspects described above.

[0089] Ninthly, a vehicle is provided that includes means as in any possible implementation of the fourth or fifth aspect, or the vehicle includes computer-readable storage as in any possible implementation of the seventh aspect, or the vehicle includes a chip as in any possible implementation of the eighth aspect, or the vehicle is loaded with computer program code as in any possible implementation of the sixth aspect.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0104] Figure 13 is another schematic flowchart of the control method provided in the embodiments of this application;

[0105] Figure 14 is another schematic flowchart of the control method provided in the embodiments of this application;

[0106] Figure 15 is a schematic block diagram of the control device provided in an embodiment of this application;

[0107] Figure 16 is another schematic block diagram of the control device provided in the embodiments of this application. Detailed Implementation

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

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

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

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

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

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

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

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

[0116] As mentioned above, the multimedia experience of in-vehicle displays in current smart cockpits still needs improvement. Some vehicles experience lag when switching system accounts, resulting in choppy visuals or long waiting times for users, leading to a poor user experience. Other systems, while not experiencing lag when switching system accounts, offer less convenient and intelligent methods for logging into applications under a single account.

[0117] Therefore, embodiments of this application provide a control method, apparatus, and vehicle that help improve the convenience of users when using the application and ensure user privacy and security.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0204] For example, when a user clicks on the login control 1011, the display screen 201 can be controlled to display a prompt box 1012 as shown in Figure 8(b). The prompt box 1012 includes the prompt message "Please select a login method," as well as a face recognition login control, a QR code login control, an account login control, and a cancel control. When the account login control is clicked, in response to the user's input system account and login password (or verification code), the system account (hereinafter referred to as User A's system account) is controlled to log in to the vehicle system. It is understood that in actual implementation, the user can also choose other methods to log in to the vehicle system. After User A's system account logs in to the vehicle system, the login control can be controlled to display the avatar 1013 associated with User A's system account, as shown in Figure 8(c).

[0205] In some implementations, if a connection has already been established between application account b, the intelligent driving application, and user A's system account when user A logs into the intelligent driving application for the first time using application account b, or when user A logs into the intelligent driving application using application account a, the connection between application account a, the intelligent driving application, and user A's system account can be established in response to user A's login with application account a. This ensures that application account a will also log into the intelligent driving application when user A's system account logs into the vehicle system subsequently. For example, after establishing the connection between application account a, the intelligent driving application, and user A's system account, the display screen 201 can be controlled to display a prompt box 1014 as shown in Figure 8(d). The prompt box 1014 includes the message "The intelligent driving application has been associated. The intelligent driving application will automatically log in the next time you log into the vehicle system."

[0206] In some implementations, before establishing the association between application account a, the intelligent driving application, and user A's system account, the control display 201 displays a prompt box 1015 as shown in Figure 8(e). This prompt box 1015 includes the prompt message "Do you want to set the intelligent driving application to log in with the vehicle system?", and controls for "Yes" and "No". Further, when the "Yes" control is clicked, the association between application account a, the intelligent driving application, and user A's system account is established, and the control display 201 can then display a prompt box 1014 as shown in Figure 8(d). If the "No" control is clicked, the association between application account a, the intelligent driving application, and user A's system account is not established, and subsequently, when user A's system account logs into the vehicle system, application account a does not log in to the intelligent driving application. In some implementations, if no user confirmation is detected within a certain time period (e.g., 5 seconds, 10 seconds, or other duration) starting from the initial display of the prompt box 1015, the association between application account a, the intelligent driving application, and user A's system account is established by default.

[0207] It is understandable that Figures 8(c) to (e) above, using intelligent driving applications as examples, illustrate how to set an application to log in together with the vehicle's infotainment system. In actual implementation, other privacy-critical applications can also be set to log in together with the vehicle's infotainment system. For example, social applications (such as instant messaging applications), map navigation applications (such as navigation applications and high-precision map applications), and other applications with high data privacy requirements (such as stock applications) can all be set to log in together with the vehicle's infotainment system. In actual implementation, benefit-sharing applications can also be set to log in together with the vehicle's infotainment system in response to user actions. In the following description, no special distinction is made between application types.

[0208] Furthermore, when user A logs into the vehicle system with their system account, the application accounts associated with user A's system account are controlled to log into the applications set to log in with the vehicle system. For example, the applications set to log in with the vehicle system include applications a to c, and application accounts 1 to 3 are associated with both user A's system account and applications a to c respectively. Therefore, when user A's system account logs into the vehicle system, application account 1 is controlled to log into application a, application account 2 to application c, and application account 3 to application c. After these applications are logged in, the display screen 201 can be controlled to display a prompt box 1016 as shown in Figure 8(f), which includes the message "All applications associated with the vehicle system have been logged in!".

[0209] Generally, for applications set to log in together with the vehicle's infotainment system, the application account will also log out when the system account logs out of the system. However, as mentioned earlier, in some scenarios, driving-related applications may not log out when the system account logs out of the system; in addition, benefit-sharing applications may also not log out when the system account logs out of the system.

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

[0211] In some implementations, different applications are deployed on different display devices in the vehicle. Therefore, when user A's system account logs into the vehicle's infotainment system through different display devices, the applications logged in on each display device can be different. Figure 9 illustrates a schematic diagram of a GUI for this scenario.

[0212] As shown in Figures 9(a) and (b), the applications deployed on display screens 201 and 204 (i.e., the screen behind the passenger headrest) are different. The applications corresponding to icons 1a to 1e deployed on display screen 201 are set to log in to the vehicle system with user A's system account, and the applications corresponding to icons 1f to 1h deployed on display screen 204 are also set to log in to the vehicle system with user A's system account. When user A is in the driver's seat area, the applications corresponding to icons 1a to 1e log in to the vehicle system along with user A's system account. If user A's system account logs out of the vehicle system on display screen 201, display screen 201 displays a login control 1011 indicating an unlogged-in state, and the applications corresponding to icons 1a to 1e log out as well. Furthermore, when user A's system account logs in to the vehicle system on display screen 204, the login control displayed on display screen 204 shows the avatar 1013 associated with user A's system account, and the applications corresponding to icons 1f to 1h deployed on display screen 204 log in as well.

[0213] It should be noted that the application account used to log in to the stock application on display screen 201 can be the same as the application account used to log in to the stock application on display screen 204, and the application account used to log in to the music application on display screen 201 can be the same as the application account used to log in to the music application on display screen 204.

[0214] In some implementations, when different system accounts log in to the vehicle infotainment system through the same display screen, the applications logged in with the vehicle infotainment system can be different. Figure 10 shows a schematic diagram of a GUI for this scenario.

[0215] As shown in Figure 10(a), when user B's system account logs into the vehicle system via display screen 201, the applications corresponding to icons 1a, 1c, 1d, and 1e deployed on display screen 201 also log in, and the login control displays the avatar 1018 associated with user B's system account. If user A's system account logs into the vehicle system via display screen 204 at this time, the login status of the applications deployed on display screen 204 and the display status of the login control are shown in Figure 10(b). For a detailed description, please refer to the corresponding part of Figure 9(b), which will not be repeated here.

[0216] It is understandable that the application account for the stock application corresponding to login icon 1d is different from the application account for the stock application corresponding to login icon 1h. The two are application accounts associated with user B's system account and application accounts associated with user A's system account, respectively.

[0217] It should be noted that each display screen shown in Figures 9 and 10 may include multiple pages of interface, and each page may include at least one application icon. The interfaces shown in Figures 9 and 10 are only examples of the first page of the interface in each display screen. Other pages of each display screen may also include other applications that can be logged in with the vehicle system. For example, other interfaces of display screen 201 may also include icons of instant messaging applications, etc.

[0218] As mentioned earlier, when applications logged into the vehicle's infotainment system include autonomous driving applications, in certain scenarios, these applications may not log out of the system along with the user account. Figure 11 illustrates a GUI diagram for this scenario.

[0219] For example, when user A's system account logs into the vehicle system from display screen 201, intelligent driving applications are running. For instance, as shown in Figure 11(a), the interface of the application corresponding to the LCC function displays a navigation search component, a virtual driving scene constructed based on perceived environmental information around the vehicle, and the vehicle's real-time speed information. The navigation search component receives the address input by the user and determines navigation information to that address. The virtual driving scene includes the location information of obstacles around the vehicle (such as other vehicles and other traffic participants). Furthermore, icon 1019 displays the following distance (i.e., the distance between the vehicle and the vehicle in front) controlled by the LCC function. Each gray trapezoid in icon 1019 can be understood as a quantitative representation of one unit of following distance. If, during the vehicle's operation under the control of the LCC function, user A's system account is detected to have logged out of the vehicle system, the application corresponding to the LCC function will not log out. As shown in Figure 11(b), the display screen 201 displays the login control 1011 in an unlogged-in state, and the running interface of the application corresponding to the LCC function is not affected by the system account logging out.

[0220] It should be noted that when the same benefit-sharing application (such as a video application) is deployed on multiple displays in a vehicle, if the benefit-sharing application on one display is logged in by the application account, the same benefit-sharing application on other displays will also be logged in by the same application account. The benefit-sharing application may or may not log in with the vehicle's infotainment system. If the benefit-sharing application is logged in with the vehicle's infotainment system, the benefit-sharing application will not log out with the system account when the system account logs out of the vehicle's infotainment system. For this scenario, taking a video application as an example, Figure 12 shows a schematic diagram of a GUI.

[0221] As shown in Figure 12(a), the video application interface currently displayed on screen 201 includes a navigation bar 1021, a video playback bar 1022, and a playback history bar 1023, which are used to display various controls, the video playback interface, and playback history information, respectively. The navigation bar 1021 includes a login control 1024, which allows users to log in or out of the video application using their account. As shown in Figure 12(b), the video application interface currently displayed on screen 204 includes a navigation bar, a video playback bar 1025, and a series selection bar 1026.

[0222] In some implementations, the video application is set to log in along with user A's system account. If the video applications on multiple displays, including displays 201 and 204, are not logged in before user A's system account logs in to the vehicle system via display 201, then when user A's system account logs in to the vehicle system via display 201, the video applications on multiple displays, including displays 201 and 204, will all be logged in by the application account (such as application account A) associated with user A's system account used to log in to the video applications.

[0223] In some implementations, the video application is set to log in along with user A's system account. Before user A's system account logs into the vehicle system via display screen 201, if the video application on multiple displays, including display screens 201 and 204, is already logged in (e.g., logged in by application account B), then when user A's system account logs into the vehicle system via display screen 201, the video application on multiple displays, including display screens 201 and 204, switches to the application account associated with user A's system account used to log in to the video application; that is, the login account for the video application is switched from application account B to application account A. Alternatively, when user A's system account logs into the vehicle system via display screen 201, the video application on multiple displays, including display screens 201 and 204, remains in its original login state, i.e., it is still logged in by application account B. Alternatively, when user A logs into the vehicle system via display screen 201 with their system account, the system can determine whether to switch application accounts based on the benefits of application account A and application account B. For example, if application account A offers more benefits than application account B (e.g., application account A is a VIP account, and application account B is not a VIP account), then the system will switch to application account A to log in to the video application. If application account A offers fewer benefits than application account B, or if the benefits of application account A and application account B are the same, then the system will remain unchanged with application account B logged into the video application. For instance, the style of the login control 1024 differs when the application account is a VIP account compared to when the application account is not a VIP account. Therefore, an image recognition algorithm can be used to identify the login control of the video application, thereby determining whether the logged-in application account is a VIP account.

[0224] It should be noted that for benefit-sharing applications that are not set to log in with the vehicle's infotainment system, when a benefit-sharing application is logged in on one display screen, the same benefit-sharing application deployed on other display screens will also log in. For example, when the aforementioned video application is not set to log in with the vehicle's infotainment system, when logging in to the video application through display screen 201, the video applications on one or more display screens, including display screen 204, will also log in.

[0225] It is understandable that when the same application account logs into video application accounts deployed on different displays within the same time period, the video application accounts on different displays can display different content within the same time period, as shown in Figures 12(a) and (b). Furthermore, when the same application account logs into video applications on multiple displays, some or all of the displays may not display the application's interface.

[0226] The above is just an example of a video application as a benefit-sharing application. In actual implementation, the login and logout operations for other benefit-sharing applications can be referred to the description in the corresponding part of Figure 12.

[0227] It should be noted that Figures 8 to 12 mainly illustrate the operations performed on applications already deployed on the central control screen and the rear right side display screen. In actual implementation, the aforementioned login and logout operations can also be performed on applications already deployed on other screens besides the central control screen and the rear right side display screen.

[0228] Figure 13 shows a schematic flowchart of the control method provided in an embodiment of this application. This method 10 can be executed by the vehicle 100 shown in Figure 1, for example, by the computing platform 150 in the vehicle 100. Alternatively, the method can be executed by the system shown in Figure 4, more specifically, by the user center service unit 430 and the public data service unit 440 shown in Figure 4. The method includes:

[0229] S12, in response to an event that the first user account logs out on the vehicle's infotainment system, controls the first group of applications associated with the first user account to log out based on the association between the first user account and the applications.

[0230] The first group of applications includes at least one application, and the vehicle includes one or more displays, with the at least one application deployed on one or more displays. In some implementations, before executing S12, the method further includes S11: detecting a logout event on the vehicle infotainment system, or obtaining information about the user account that logged out of the vehicle infotainment system.

[0231] For example, the first group of applications includes a first category of applications, which are applications that require data isolation. For example, the first category of applications are privacy-critical applications as described in the foregoing embodiments. More specifically, at least one application may include other applications of the first category besides intelligent driving applications.

[0232] In some implementations, the first group of applications does not include the second type of applications, which are applications that do not require data isolation. For example, the second type of applications can be the rights-sharing applications in the embodiments.

[0233] In some implementations, the first user account can be any of the system account A, system account B, user A's system account, or user B's system account in the aforementioned embodiments, or it can be any other system account used to log in to the vehicle system. Furthermore, the association between the first user account and the application can include the association between the first group of applications and the first user account. This association can be set before executing S12. If the first user account is system account A, then the first group of applications can include at least one application in application group a in the aforementioned method 700. Optionally, the first group of applications can be logged in using one or more application accounts associated with the first user account. In this case, the association between the first user account and the application can further include the association between one or more application accounts and the first user account, which can also be set before executing S12. For more specific implementations of setting the association between the first group of applications and the first user account, and the implementations of setting the association between one or more application accounts and the first user account, please refer to S724 to S726 and the description of the corresponding part of Figure 8, which will not be repeated here.

[0234] In some implementations, after controlling the logout of the first group of applications associated with the first user account, it is also possible to control the logout of at least one application within the first group. The specific meaning of controlling the logout of at least one application can be found in the description in S735 above, and will not be repeated here.

[0235] Figure 14 shows another schematic flowchart of the control method provided in this application embodiment. This method 10' can be executed by the vehicle 100 shown in Figure 1, for example, by the computing platform 150 in the vehicle 100. Alternatively, the method can be executed by the system shown in Figure 4, more specifically, by the user center service unit 430 and the public data service unit 440 shown in Figure 4. The method includes:

[0236] S12', in response to the event of the first user account logging in on the vehicle's infotainment system, logs in to the second set of applications associated with the first user account based on the association between the first user account and the applications.

[0237] The second group of applications includes at least one application, and the vehicle includes one or more displays, with the at least one application deployed on one or more displays.

[0238] In some implementations, before executing S12', the method also includes S11': detecting login events on the vehicle infotainment system, or obtaining information about the user account logged into the vehicle infotainment system.

[0239] For example, the second group of applications includes the first type of applications, which are applications that require data isolation.

[0240] In some implementations, method 10' can be executed before method 10, and the second set of applications in method 10' includes the first set of applications in method 10.

[0241] In some implementations of method 10 or method 10', one or more displays include a first display, and when a first user account logs into the vehicle system through the first display, a first type of application from the second group of applications is deployed on the first display.

[0242] For example, taking display screen 201 as the first display screen and user A's system account as the first user account, the second group of applications may include the applications corresponding to icons 1a to 1e in Figure 9; taking display screen 204 as the first display screen and user A's system account as the first user account as the first user account as the second group of applications may include the applications corresponding to icons 1f to 1h in Figure 9; taking display screen 201 as the first display screen and user B's system account as the first user account as the first user account as the second group of applications may include the applications corresponding to icons 1a, 1c, 1d, and 1e in Figure 9. When user A's system account logs into the vehicle system through the first display screen, the specific implementation of controlling the login of the first group of application accounts to the second group of applications can be found in the descriptions of the corresponding parts of Figures 9 and 10, and will not be repeated here.

[0243] In some implementations of method 10 or method 10', one or more displays include a second display, and when the first user account logs into the vehicle system through the second display, the first type of application in the second group of applications is deployed on the second display.

[0244] In some implementations, the method further includes: in response to an event that a first user account logs into the vehicle system via a second display screen, controlling the logout of a second set of applications associated with the first user account on the first display screen; and logging into a third set of applications associated with the first user account on the second display screen, wherein the third set of applications is deployed on at least the second display screen.

[0245] In some implementations, when all applications in the third group are of the first type, the third group of applications is deployed on the second display screen.

[0246] In some implementations of method 10 or method 10', the third set of applications is the same as the second set of applications; or, when the first display screen is a safety-critical screen and the second display screen is a non-safety-critical screen, at least one application in the third set of applications is different from the second set of applications; or, when the first display screen is a non-driving safety-critical screen and the second display screen is a safety-critical screen, the third set of applications is a proper subset of the second set of applications.

[0247] For example, taking display screen 201 as the first display screen, display screen 204 as the second display screen, and user account A as the system account of user A as an example, the third group of applications can be the applications corresponding to icons 1f to 1h in Figure 10. Taking display screen 204 as the first display screen, display screen 201 as the second display screen, and user account A as the system account of user A as an example, the third group of applications can be the applications corresponding to icons 1a to 1e in Figure 10. For a detailed description of the login and logout status of each application when the first user account logs into the vehicle system via the second display screen, please refer to the description in the corresponding part of Figure 10, which will not be repeated here.

[0248] In some implementations of method 10 or method 10', the second group of applications also includes a first application and a second application, which are the same application deployed on the third display screen and the fourth display screen respectively, and both the first application and the second application are logged in by the first application account, and one or more displays include the third display screen and the fourth display screen.

[0249] For example, the third display screen is the same display screen as the aforementioned first display screen, or the fourth display screen is the same display screen as the aforementioned first display screen. It is understood that the first application and the second application are shared-rights applications. The specific implementation of the first application and the second application logging in together when the first user account logs into the vehicle system can be referred to the description of the corresponding part of Figure 12, and will not be repeated here.

[0250] In some implementations of method 10 or method 10', the first group of applications includes safety-critical applications, and the method further includes: when the first user account logs out of the vehicle system, if the vehicle is in drive or reverse gear, maintaining the running state of the safety-critical applications.

[0251] In some implementations of method 10 or method 10', the safety-critical application includes a navigation application or a smart driving application, and the safety-critical application is logged out and / or exited when the vehicle shifts to park.

[0252] For example, taking a safety-critical application like intelligent driving as an example, a more specific implementation of controlling the logout of intelligent driving applications can be found in the description of the corresponding part of Figure 11, which will not be repeated here.

[0253] In some implementations of method 10 or method 10', if the vehicle is in drive or reverse gear, the user is prompted that the first user account cannot be logged out.

[0254] In some implementations of method 10 or method 10', the second set of applications includes a third application associated with the second user account. The method further includes: after the first user account logs out of the vehicle system and when the second user account logs in to the vehicle system, controlling the second application account to log in to the third application, with the second application account associated with the second user account.

[0255] For example, taking user A's system account as the first user account and user B's system account as the second user account, the third application can be the stock application corresponding to Figure 10. More specific implementation details can be found in the description of the corresponding part of Figure 10, and will not be repeated here.

[0256] In some implementations of method 10 or method 10', the first user account is one of multiple user accounts, each user account is associated with a sub-data storage area, and the multiple sub-data storage areas associated with the multiple user accounts belong to the same user space. The method further includes: obtaining a first access request from a fourth application under the first user account, the first access request being used to request reading or writing first data; and reading or writing the first data through the first sub-data storage area corresponding to the first user account according to the first access request, wherein the multiple sub-data storage areas include the first sub-data storage area.

[0257] For example, multiple user accounts may include the aforementioned vehicle owner system account, authorized system account, etc.; the sub-data storage area may be the access path unit in the aforementioned embodiment; the first data may include data such as pictures, files, and videos.

[0258] In some implementations, the first access request carries the identifier of the first user account, and further, based on the identifier of the first user account, the first data is stored in the first sub-data storage area corresponding to the first user account.

[0259] For example, taking the first user account as the system account of user A in the aforementioned embodiment and the fourth application as the instant messaging application running under user A's system account, the first access request can be a data storage request issued by the instant messaging application running under user A's system account. Further, storing the first data through the first sub-data storage area corresponding to the first user account can be achieved by storing the first data through the access path unit corresponding to user A's system account. For example, when storing the first data, a reference to the first data (such as a field including user A's system account) is created and stored in the access path unit, so that when reading the first data later, it needs to be read through the reference to the first data stored in the access path unit. A more specific implementation of storing the first data can be found in the description of the corresponding part of Figure 6 above, and will not be repeated here.

[0260] In some implementations, the multiple user accounts also include a third user account, which is associated with a second sub-data storage area in the multiple sub-data storage areas. The method further includes: obtaining a second access request from a fifth application of the third user account; and rejecting the second access request when the first data is written through the first sub-data storage area and the second access request is used to request to read the first data.

[0261] In this context, denying the second access request can be understood as refusing to read the first data from the data storage area.

[0262] For example, if the first data is a first type of data, then when the second access request is used to request the reading of the first type of data, the first group of data is read from the data storage area according to the second access request. Each item in the first group of data is first type of data, and the first group of data does not include the first data. When the second access request is used to request the reading of first type of data including the first data, rejecting the second access request can be understood as rejecting the part of the second access request related to reading the first data, but it is still possible to respond to the second access request to read other first type of data besides the first data.

[0263] It should be noted that the fifth application can be a privacy-critical application or a rights-sharing application.

[0264] In some implementations, the method further includes: obtaining a third access request from a second type of application under the first user account; and rejecting the third access request when the first data is written through the first sub-data storage area and the third access request is used to request to read the first data.

[0265] In this context, denying a third access request can be understood as refusing to read the first data from the data storage area.

[0266] For example, if the first data is of type 1, then when a third access request is made to request the reading of the first type of data, a second set of data is read from the data storage area according to the third access request. Each item in the second set of data is of type 1, and the second set of data does not include the first data. When a third access request is made to request the reading of type 1 data including the first data, rejecting the third access request can be understood as rejecting the part of the third access request concerning the reading of the first data, but still being able to respond to the third access request to read other type 1 data besides the first data.

[0267] In some implementations, the method further includes: obtaining a fourth access request from a fourth application, the fourth access request being used to request the reading of second data, the second data being data stored by a second type of application under the first user account; and reading the second data according to the fourth access request.

[0268] In some implementations, the second data is stored in a public storage area, and the second data is read according to a fourth access request, including: when the first user account is authorized to access the public storage area, the second data is read according to the fourth access request.

[0269] For example, the public storage area can be the same as the public storage area in the aforementioned embodiments, used to store data associated with rights-sharing applications. That is, the second data can be data associated with a second type of application, for example, data stored by a second type of application. Specifically, permissions for the first user account to access the public storage area can be set through steps S711 to S713 in the aforementioned embodiments.

[0270] Understandably, when the first user account is not authorized to access the public storage area, the fourth access request from the fourth application is rejected, meaning the fourth application cannot read the data in the public storage area.

[0271] In some implementations, the method further includes: obtaining a fifth access request from a sixth application under a first user account, the fifth access request being used to request reading first data; and when the first data is written through a first sub-data storage area, and the sixth application is an application that needs to access the first sub-data storage area to store data, reading the first data according to the fifth access request.

[0272] It is understandable that the sixth application and the fourth application are of the same type, that is, the sixth application is also a first-type application.

[0273] The control method provided in this application, when a user account logs into the vehicle infotainment system, controls the relevant account to log into a second group of applications within the system, eliminating the need for manual user control and improving user convenience. When the system detects that a first user account has logged out, it controls the relevant application account to log out of at least one application in the second group, helping to ensure user privacy and security.

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

[0275] The control method provided by the embodiments of this application has been described in detail above with reference to Figures 1 to 13. The apparatus provided by the embodiments of this application will now be described in detail below with reference to Figures 15 and 16. It should be understood that the description of the apparatus embodiments corresponds to the description of the method embodiments; therefore, any content not described in detail can be referred to the method embodiments above, and for the sake of brevity, will not be repeated here.

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

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

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

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

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

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

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

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

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

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

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

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

[0288] In some implementations, the aforementioned intelligent driving device can be the vehicle 100 shown in Figure 1.

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

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

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

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

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

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

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

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

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

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

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

Claims

1. A control method, characterized in that, include: In response to an event that the first user account logs out on the vehicle's infotainment system, the system controls the logout of the first group of applications associated with the first user account based on the association between the first user account and the applications. The first group of applications includes at least one application, and the vehicle includes one or more displays, with the at least one application deployed on the one or more displays.

2. The method according to claim 1, characterized in that, The method further includes: Control at least one application in the first group of applications to exit.

3. The method according to claim 1 or 2, characterized in that, The first group of applications includes security-critical applications, and the method further includes: When the first user account logs out of the vehicle system, if the vehicle is in drive or reverse gear, the safety-critical application remains operational.

4. The method according to claim 3, characterized in that, The safety-critical applications include navigation applications or intelligent driving applications. When the vehicle's gear is switched to park, the safety-critical applications are logged out and / or exited.

5. The method according to claim 1 or 2, characterized in that, If the vehicle is in drive or reverse gear, the user will be prompted that the first user account cannot be logged out.

6. The method according to any one of claims 1 to 5, characterized in that, The method further includes: In response to the event of the first user account logging in on the vehicle system, the second group of applications associated with the first user account is logged in according to the association relationship between the first user account and the application. The second group of applications is deployed on the one or more displays, and the second group of applications includes the first group of applications.

7. The method according to claim 6, characterized in that, The second group of applications includes the first category of applications, which are privacy-critical applications.

8. The method according to claim 7, characterized in that, The privacy-critical applications are those that require data isolation within a single user space.

9. The method according to any one of claims 6 to 8, characterized in that, The one or more displays include a first display, and when the first user account logs into the vehicle system through the first display, the first type of application in the second group of applications is deployed on the first display.

10. The method according to claim 9, characterized in that, The one or more displays include a second display, and when the first user account logs into the vehicle system through the second display, the first type of application in the second group of applications is deployed on the second display.

11. The method according to claim 10, characterized in that, The method further includes: In response to an event that the first user account logs into the vehicle system via the second display screen, control the second set of applications associated with the first user account to be logged out on the first display screen; Log in to a third set of applications associated with the first user account on the second display screen, wherein the third set of applications is deployed on at least the second display screen.

12. The method according to claim 11, characterized in that, The third group of applications is the same as the second group of applications; Alternatively, when the first display screen is a safety-critical screen and the second display screen is a non-safety-critical screen, at least one application in the third group of applications is different from the second group of applications; Alternatively, when the first display screen is a non-driving safety-critical screen and the second display screen is a safety-critical screen, the third set of applications is a proper subset of the second set of applications.

13. The method according to any one of claims 6 to 12, characterized in that, The second group of applications also includes a first application and a second application. The first application and the second application are multiple instances of the same application deployed on the third display screen and the fourth display screen, respectively. Both the first application and the second application are logged into the first application account. The one or more display screens include the third display screen and the fourth display screen.

14. The method according to any one of claims 6 to 13, characterized in that, The vehicle infotainment system includes a third application, which is associated with a second user account. The method further includes: In response to the second user account logging into the vehicle system, log into the third application.

15. The method according to any one of claims 1 to 14, characterized in that, The method further includes: Obtain the first access request of the fourth application associated with the first user account. The first access request is used to request to read or write first data. The first user account is one of multiple user accounts in the vehicle system. Each user account is associated with a sub-data storage area, and the multiple sub-data storage areas associated with the multiple user accounts belong to the same user space. When the fourth application is a first type of application, the first data is read or written through the first sub-data storage area corresponding to the first user account according to the first access request, and the plurality of sub-data storage areas include the first sub-data storage area.

16. The method according to claim 15, characterized in that, The plurality of user accounts also includes a third user account, which is associated with a second sub-data storage area within the plurality of sub-data storage areas. The method further includes: Obtain the second access request of the fifth application associated with the third user account; If the first data is written through the first sub-data storage area, and the second access request is used to request to read the first data, the second access request is rejected.

17. The method according to any one of claims 1 to 16, characterized in that, The first group of applications does not include the second category of applications, which are non-privacy-critical applications.

18. A control method, characterized in that, include: In response to an event that a first user account logs in on the vehicle's infotainment system, the system logs in to a second set of applications associated with the first user account, based on the association between the first user account and the applications. The second group of applications includes at least one application, and the vehicle includes one or more displays, with the at least one application deployed on the one or more displays.

19. The method according to claim 18, characterized in that, The method further includes: In response to an event that a first user account logs out on the vehicle infotainment system, based on the association between the first user account and the applications, control the first group of applications associated with the first user account to log out on the vehicle infotainment system, wherein the second group of applications includes the first group of applications.

20. The method according to claim 19, characterized in that, The method further includes: Control at least one application in the first group of applications to exit.

21. The method according to claim 19 or 20, characterized in that, The first group of applications includes security-critical applications, and the method further includes: When the first user account logs out of the vehicle system, if the vehicle is in drive or reverse gear, the safety-critical application remains operational.

22. The method according to claim 21, characterized in that, The safety-critical applications include navigation applications or intelligent driving applications. When the vehicle's gear is switched to park, the safety-critical applications are logged out and / or exited.

23. The method according to claim 19 or 20, characterized in that, If the vehicle is in drive or reverse gear, the user will be prompted that the first user account cannot be logged out.

24. The method according to any one of claims 18 to 23, characterized in that, The first group of applications does not include the second category of applications, which are applications that do not require data isolation.

25. The method according to any one of claims 18 to 24, characterized in that, The second group of applications includes the first category of applications, which are privacy-critical applications.

26. The method according to claim 25, characterized in that, The privacy-critical applications are those that require data isolation within a single user space.

27. The method according to any one of claims 18 to 26, characterized in that, The one or more displays include a first display, and when the first user account logs into the vehicle system through the first display, the first type of application in the second group of applications is deployed on the first display.

28. The method according to claim 27, characterized in that, The one or more displays include a second display, and when the first user account logs into the vehicle system through the second display, the first type of application in the second group of applications is deployed on the second display.

29. The method according to claim 28, characterized in that, The method further includes: In response to an event that the first user account logs into the vehicle system via the second display screen, control the second set of applications associated with the first user account to be logged out on the first display screen; Log in to a third set of applications associated with the first user account on the second display screen, wherein the third set of applications is deployed on at least the second display screen.

30. The method according to claim 29, characterized in that, The third group of applications is the same as the second group of applications; Alternatively, when the first display screen is a safety-critical screen and the second display screen is a non-safety-critical screen, at least one application in the third group of applications is different from the second group of applications; Alternatively, when the first display screen is a non-driving safety-critical screen and the second display screen is a safety-critical screen, the third set of applications is a proper subset of the second set of applications.

31. The method according to any one of claims 18 to 30, characterized in that, The second group of applications also includes a first application and a second application. The first application and the second application are multiple instances of the same application deployed on the third display screen and the fourth display screen, respectively. Both the first application and the second application are logged into the first application account. The one or more display screens include the third display screen and the fourth display screen.

32. The method according to any one of claims 18 to 31, characterized in that, The vehicle infotainment system includes a third application, which is associated with a second user account. The method further includes: In response to the second user account logging into the vehicle system, log into the third application.

33. The method according to any one of claims 18 to 32, characterized in that, The method further includes: Obtain the first access request of the fourth application under the first user account. The first access request is used to request to read or write first data. Each user account is associated with a sub-data storage area, and the multiple sub-data storage areas associated with the multiple user accounts belong to the same user space. When the fourth application is a first type of application, the first data is read or written through the first sub-data storage area corresponding to the first user account according to the first access request, and the plurality of sub-data storage areas include the first sub-data storage area.

34. The method according to claim 33, characterized in that, The plurality of user accounts also includes a third user account, which is associated with a second sub-data storage area within the plurality of sub-data storage areas. The method further includes: Obtain the second access request of the fifth application of the third user account; If the first data is written through the first sub-data storage area, and the second access request is used to request to read the first data, the second access request is rejected.

35. A control device, characterized in that, include: The processing unit is configured to respond to an event in which a first user account logs out on the vehicle's infotainment system, and control the logout of a first group of applications associated with the first user account based on the association between the first user account and the applications. The first group of applications includes at least one application, and the vehicle includes one or more displays, with the at least one application deployed on the one or more displays.

36. The apparatus according to claim 35, characterized in that, The processing unit is also used for: Control at least one application in the first group of applications to exit.

37. The apparatus according to claim 35 or 36, characterized in that, The first group of applications includes safety-critical applications, and the processing unit is further configured to: When the first user account logs out of the vehicle system, if the vehicle is in drive or reverse gear, the safety-critical application remains operational.

38. The apparatus according to claim 37, characterized in that, The safety-critical applications include navigation applications or intelligent driving applications, which control the logout and / or exit of the safety-critical applications when the vehicle shifts to the parking gear.

39. The apparatus according to claim 35 or 36, characterized in that, If the vehicle is in drive or reverse gear, the user will be prompted that the first user account cannot be logged out.

40. The apparatus according to any one of claims 35 to 39, characterized in that, The processing unit is also used for: In response to the event of the first user account logging in on the vehicle system, the second group of applications associated with the first user account is logged in according to the association relationship between the first user account and the application. The second group of applications is deployed on the one or more displays, and the second group of applications includes the first group of applications.

41. The apparatus according to claim 40, characterized in that, The second group of applications includes the first category of applications, which are privacy-critical applications.

42. The apparatus according to claim 41, characterized in that, The privacy-critical applications are those that require data isolation within a single user space.

43. The apparatus according to any one of claims 40 to 42, characterized in that, The one or more displays include a first display, and when the first user account logs into the vehicle system through the first display, the first type of application in the second group of applications is deployed on the first display.

44. The apparatus according to claim 43, characterized in that, The one or more displays include a second display, and when the first user account logs into the vehicle system through the second display, the first type of application in the second group of applications is deployed on the second display.

45. The apparatus according to claim 44, characterized in that, The processing unit is also used for: In response to an event that the first user account logs into the vehicle system via the second display screen, control the second set of applications associated with the first user account to be logged out on the first display screen; Log in to a third set of applications associated with the first user account on the second display screen, wherein the third set of applications is deployed on at least the second display screen.

46. ​​The apparatus according to claim 45, characterized in that, The third group of applications is the same as the second group of applications; Alternatively, when the first display screen is a safety-critical screen and the second display screen is a non-safety-critical screen, at least one application in the third group of applications is different from the second group of applications; Alternatively, when the first display screen is a non-driving safety-critical screen and the second display screen is a safety-critical screen, the third set of applications is a proper subset of the second set of applications.

47. The apparatus according to any one of claims 40 to 46, characterized in that, The second group of applications also includes a first application and a second application. The first application and the second application are multiple instances of the same application deployed on the third display screen and the fourth display screen, respectively. Both the first application and the second application are logged into the first application account. The one or more display screens include the third display screen and the fourth display screen.

48. The apparatus according to any one of claims 40 to 47, characterized in that, The vehicle infotainment system includes a third application, which is associated with a second user account. The processing unit is further configured to: In response to the second user account logging into the vehicle system, log into the third application.

49. The apparatus according to any one of claims 35 to 48, characterized in that, The device further includes an acquisition unit for: Obtain the first access request of the fourth application associated with the first user account. The first access request is used to request to read or write first data. The first user account is one of multiple user accounts in the vehicle system. Each user account is associated with a sub-data storage area, and the multiple sub-data storage areas associated with the multiple user accounts belong to the same user space. The processing unit is further configured to: when the fourth application is a first type of application, read or write the first data through the first sub-data storage area corresponding to the first user account according to the first access request, wherein the plurality of sub-data storage areas include the first sub-data storage area.

50. The apparatus according to claim 49, characterized in that, The plurality of user accounts also includes a third user account, which is associated with a second sub-data storage area within the plurality of sub-data storage areas. The acquisition unit is further configured to: Obtain the second access request of the fifth application associated with the third user account; The processing unit is further configured to: when the first data is written through the first sub-data storage area and the second access request is used to request to read the first data, reject the second access request.

51. The apparatus according to any one of claims 35 to 50, characterized in that, The first group of applications does not include the second category of applications, which are non-privacy-critical applications.

52. A control device, characterized in that, include: The processing unit is configured to respond to an event in which a first user account logs in on the vehicle's infotainment system, and log in to a second set of applications associated with the first user account based on the association between the first user account and the applications. The second group of applications includes at least one application, and the vehicle includes one or more displays, with the at least one application deployed on the one or more displays.

53. The apparatus according to claim 52, characterized in that, The processing unit is also used for: In response to an event that a first user account logs out on the vehicle infotainment system, based on the association between the first user account and the applications, control the first group of applications associated with the first user account to log out on the vehicle infotainment system, wherein the second group of applications includes the first group of applications.

54. The apparatus according to claim 53, characterized in that, The processing unit is also used for: Control at least one application in the first group of applications to exit.

55. The apparatus according to claim 53 or 54, characterized in that, The first group of applications includes safety-critical applications, and the processing unit is further configured to: When the first user account logs out of the vehicle system, if the vehicle is in drive or reverse gear, the safety-critical application remains operational.

56. The apparatus according to claim 55, characterized in that, The safety-critical applications include navigation applications or intelligent driving applications. When the vehicle's gear is switched to park, the safety-critical applications are logged out and / or exited.

57. The apparatus according to claim 53 or 54, characterized in that, If the vehicle is in drive or reverse gear, the user will be prompted that the first user account cannot be logged out.

58. The apparatus according to any one of claims 52 to 57, characterized in that, The first group of applications does not include the second category of applications, which are applications that do not require data isolation.

59. The apparatus according to any one of claims 52 to 58, characterized in that, The second group of applications includes the first category of applications, which are privacy-critical applications.

60. The apparatus according to claim 59, characterized in that, The privacy-critical applications are those that require data isolation within a single user space.

61. The apparatus according to any one of claims 52 to 60, characterized in that, The one or more displays include a first display, and when the first user account logs into the vehicle system through the first display, the first type of application in the second group of applications is deployed on the first display.

62. The apparatus according to claim 61, characterized in that, The one or more displays include a second display, and when the first user account logs into the vehicle system through the second display, the first type of application in the second group of applications is deployed on the second display.

63. The apparatus according to claim 62, characterized in that, The processing unit is also used for: In response to an event that the first user account logs into the vehicle system via the second display screen, control the second set of applications associated with the first user account to be logged out on the first display screen; Log in to a third set of applications associated with the first user account on the second display screen, wherein the third set of applications is deployed on at least the second display screen.

64. The apparatus according to claim 63, characterized in that, The third group of applications is the same as the second group of applications; Alternatively, when the first display screen is a safety-critical screen and the second display screen is a non-safety-critical screen, at least one application in the third group of applications is different from the second group of applications; Alternatively, when the first display screen is a non-driving safety-critical screen and the second display screen is a safety-critical screen, the third set of applications is a proper subset of the second set of applications.

65. The apparatus according to any one of claims 52 to 64, characterized in that, The second group of applications also includes a first application and a second application. The first application and the second application are multiple instances of the same application deployed on the third display screen and the fourth display screen, respectively. Both the first application and the second application are logged into the first application account. The one or more display screens include the third display screen and the fourth display screen.

66. The apparatus according to any one of claims 52 to 65, characterized in that, The vehicle infotainment system includes a third application, which is associated with a second user account. The processing unit is further configured to: In response to the second user account logging into the vehicle system, log into the third application.

67. The apparatus according to any one of claims 52 to 66, characterized in that, The device further includes an acquisition unit for: Obtain the first access request of the fourth application under the first user account. The first access request is used to request to read or write first data. Each user account is associated with a sub-data storage area, and the multiple sub-data storage areas associated with the multiple user accounts belong to the same user space. The processing unit is further configured to: when the fourth application is a first type of application, read or write the first data through the first sub-data storage area corresponding to the first user account according to the first access request, wherein the plurality of sub-data storage areas include the first sub-data storage area.

68. The apparatus according to claim 67, characterized in that, The plurality of user accounts also includes a third user account, which is associated with a second sub-data storage area within the plurality of sub-data storage areas. The acquisition unit is further configured to: Obtain the second access request of the fifth application of the third user account; When the second access request is used to request the reading of the first data, the second access request is rejected.

69. A control device, characterized in that, include: A processor for executing a computer program stored in memory to cause the apparatus to perform the method as described in any one of claims 1 to 34.

70. The apparatus according to claim 69, characterized in that, The device also includes the memory.

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

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

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

74. A vehicle, characterized in that, Includes the apparatus as described in any one of claims 35 to 70, or the computer-readable storage medium as described in claim 71, or the chip as described in claim 72, or the vehicle is equipped with the computer program product as described in claim 73.

Images