Application deployment method and apparatus, in-vehicle infotainment system, and vehicle

Abstract

The present application provides an application deployment method, an in-vehicle infotainment system, and a vehicle. The method comprises: obtaining a target installation type of a first application when obtaining a first request, wherein the first request is used for requesting installation of the first application, and the target installation type includes a privacy critical type or a rights sharing type; and installing the first application on the basis of the target installation type. The present application can be applied to intelligent vehicles or electric vehicles, improves the flexibility of application deployment and thus improves user experience.

Description

Application deployment methods, devices, vehicle systems and vehicles Technical Field

[0001] This application relates to the field of smart cockpits, and more specifically, to an application deployment method, apparatus, vehicle system, and vehicle. Background Technology

[0002] With the increasing number of screens in vehicle cabins, the way applications are deployed significantly impacts the user experience. When a user chooses to install an application on one screen, the vehicle typically deploys that application on multiple screens; similarly, when a user chooses to uninstall an application on one screen, the vehicle typically uninstalls it on multiple screens. This deployment method is inflexible, resulting in a poor user experience.

[0003] Summary of the Invention

[0004] This application provides an application deployment method, apparatus, vehicle system, and vehicle, which helps to improve the flexibility of application deployment, thereby helping to improve the user experience.

[0005] In a first aspect, an application deployment method is provided, the method comprising: upon obtaining a first request, obtaining a target installation type of a first application, the first request being used to request the installation of the first application, the target installation type including privacy-critical or rights-sharing; and installing the first application according to the target installation type.

[0006] Based on the above technical solution, when a request to install the first application is received, the target installation type of the first application can be obtained. The first application is then installed based on this target installation type. In this way, by selecting a target installation type from either privacy-critical or rights-sharing types, the flexibility of application deployment is improved, thereby enhancing the user experience.

[0007] In some possible implementations, privacy-critical and benefit-sharing models can be categorized based on the application's data privacy requirements.

[0008] For example, an application with a privacy-critical installation type can also be called a clone application, and an application with a rights-sharing installation type can also be called an instance application.

[0009] For example, an application with a privacy-critical installation type refers to an application that requires data isolation. For instance, users do not want data associated with such applications to be accessed or obtained by other users. Privacy-critical applications may include social applications (such as instant messaging applications, social media platforms, etc.), or they may also include e-commerce applications, map navigation applications, etc.

[0010] For example, an application with an installation type of shared benefits refers to an application that does not require data isolation. For instance, the data associated with such applications can be accessed or obtained by other users, such as weather applications. Alternatively, an application with an installation type of shared benefits can also be an application that requires data sharing. For instance, for an application, multiple system accounts (or vehicle system accounts) can share the benefits of the same application account, such as audio and video applications.

[0011] In conjunction with the first aspect, in some implementations of the first aspect, obtaining the target installation type of the first application includes: a control prompting device prompting the user to select from either privacy-critical or rights-sharing; obtaining the user's first input, which is used to indicate the target installation type.

[0012] Based on the above technical solution, a prompting device can guide the user to select a target installation type from either privacy-critical or rights-sharing types. In this way, the target installation type can be obtained based on the user's selection.

[0013] In some possible implementations, the control prompt device prompts the user to select from either privacy-critical or rights-sharing types, including: the control display device displays a first interface that includes prompt information for prompting the user to select the target installation type from either privacy-critical or rights-sharing types.

[0014] In some possible implementations, the method also includes: controlling the prompting device to prompt the user with privacy-critical and rights-sharing information.

[0015] For example, the first application is deployed on multiple screens, and the method includes: a control prompt device prompting the user that if the installation type is selected as privacy-critical, the vehicle will only log in to the account of the first application on the screen where the vehicle account is logged in.

[0016] For example, the first application is deployed on multiple screens, and the method includes: a control prompt device prompts the user that if the installation type is selected as benefit-sharing, the vehicle will log in to the account of the first application on all multiple screens after logging in to the vehicle system account.

[0017] In conjunction with the first aspect, in some implementations of the first aspect, obtaining the target installation type of the first application includes: determining the target installation type based on the type of the first application and a mapping relationship, wherein the mapping relationship includes the correspondence between the application type and the installation type.

[0018] Based on the above technical solution, the target installation type can be determined through mapping relationships. This eliminates the need for users to choose between privacy-critical and benefit-sharing types; the vehicle can adaptively match the installation type corresponding to the type of the first application.

[0019] In some possible implementations, this mapping relationship includes a correspondence between social applications and privacy-critical applications, a correspondence between short video applications and privacy-critical applications, a correspondence between video applications and benefit-sharing applications, and a correspondence between music applications and benefit-sharing applications.

[0020] In conjunction with the first aspect, in some implementations of the first aspect, before obtaining the first request, the method further includes: obtaining the user's input of logging into the first vehicle system account in the vehicle system; wherein, the method further includes: when it is detected that the first vehicle system account has been logged out and the target installation type of the first application is privacy-critical, logging out the first application account logged in on the first application.

[0021] Based on the above technical solution, accounts with privacy-critical applications installed can be automatically logged out when the vehicle's infotainment system account is logged out. This helps prevent user privacy leaks and ensures user privacy security.

[0022] In conjunction with the first aspect, in some implementations of the first aspect, before obtaining the first request, the method further includes: obtaining the user's input of logging into the first vehicle system account in the vehicle system; wherein, the method further includes: when it is detected that the first vehicle system account has been logged out and the target installation type of the first application is a benefit-sharing type, maintaining the first application account logged in on the first application.

[0023] Based on the above technical solution, when the vehicle system account is logged out, the first application account with installed benefit-sharing applications can remain logged in. This allows users to continue using the first application account without compromising their privacy, thus improving the user's driving experience.

[0024] In conjunction with the first aspect, in some implementations of the first aspect, prior to the first application account logged in on the first application, the method further includes: determining that the first application account is a member account.

[0025] Based on the above technical solution, even when the vehicle system account is logged out and the primary application account is a member account, the primary application account can remain logged in. This allows users to continue using the member account without compromising their privacy, thus enhancing the user's driving and riding experience.

[0026] In some possible implementations, determining that the first application account is a member account includes: obtaining an image of the area where the profile picture of the first application account is located; if the image contains information indicating a member account, determining that the first application account is a member account.

[0027] In conjunction with the first aspect, in some implementations of the first aspect, before obtaining the first request, the method further includes: obtaining the user's input when logging into the second vehicle system account in the vehicle system; wherein, the method further includes: when the first application is the first application installed in the vehicle system with a privacy-critical installation type, creating a first data storage area, the first data storage area being the data storage area corresponding to the second vehicle system account; obtaining the first application's request to call data; and accessing the data stored in the first data storage area according to the request to call data.

[0028] Based on the above technical solution, when the first application is the first privacy-critical application installed on the vehicle infotainment system, a first data storage area can be created. During user interaction with the application, saved data can be stored in the first data storage area. When the user uses the first application to access data, they can access the data stored in the first data storage area. This ensures that applications under this vehicle infotainment account can only access this first data storage area and are not allowed to access data storage areas under other vehicle infotainment accounts, thus helping to protect the data privacy of different vehicle infotainment accounts and ultimately ensuring user privacy and security.

[0029] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: obtaining a first input from a user regarding a first application, the first input being used to change the installation type of the first application; in response to the first input, performing an uninstallation operation on the first application and installing the first application according to the changed installation type.

[0030] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: controlling a prompting device to prompt a user to select a plurality of display devices on which the first application is deployed; receiving a second input from the user, the second input being used to indicate at least one of the plurality of display devices; and controlling the display of an icon of the first application on the at least one display device.

[0031] Based on the above technical solution, the vehicle can control the prompting device to guide the user to select the screen where the first application will be deployed. This allows users to choose which screens to deploy the first application according to their needs, improving flexibility in application deployment and enhancing the user's driving experience.

[0032] In conjunction with the first aspect, in some implementations of the first aspect, installing the first application according to the target installation type includes: sending a first request to a server, the first request including an identifier of the target installation type; receiving a first response sent by the server, the first response including an installation package corresponding to the target installation type; and installing the first application according to the installation package.

[0033] Secondly, an application deployment method is provided, the method comprising: receiving a first request sent by a vehicle, the first request being for requesting an installation package of a first application; obtaining the target installation type of the first application, the target installation type including privacy-critical or rights-sharing; and sending the installation package of the first application according to the target installation type.

[0034] Based on the above technical solution, the server can first obtain the target installation type of the first application based on the first request, and then send the installation package corresponding to the target installation type to the vehicle.

[0035] In conjunction with the second aspect, in some implementations of the second aspect, obtaining the target installation type of the first application includes: determining the target installation type based on the type of the first application and a mapping relationship, wherein the mapping relationship includes the correspondence between the application type and the installation type.

[0036] Based on the above technical solution, the target installation type can be determined through mapping relationships. This eliminates the need for users to choose between privacy-critical and rights-sharing types; the server can adaptively match the installation type corresponding to the type of the first application.

[0037] Thirdly, an application deployment apparatus is provided, comprising: an acquisition unit, configured to acquire, upon acquiring a first request, a target installation type of a first application, the first request being used to request the installation of the first application, the target installation type including privacy-critical or rights-sharing; and an installation unit, configured to install the first application according to the target installation type.

[0038] In conjunction with the third aspect, in some implementations of the third aspect, the device further includes: a control unit for controlling the prompting device to prompt the user to select from either the privacy-critical type or the rights-sharing type; and an acquisition unit for acquiring a first input from the user, the first input indicating the target installation type.

[0039] In conjunction with the third aspect, in some implementations of the third aspect, the acquisition unit is specifically used to: determine the target installation type based on the type of the first application and the mapping relationship, wherein the mapping relationship includes the correspondence between the application type and the installation type.

[0040] In conjunction with the third aspect, in some implementations of the third aspect, the acquisition unit is further configured to acquire the user's input of logging into the first vehicle system account in the vehicle system before acquiring the first request; wherein, the device further includes a detection unit and an application account management unit, the application account management unit being configured to log out the first application account logged in on the first application when the detection unit detects that the first vehicle system account has been logged out and the target installation type of the first application is privacy-critical.

[0041] In conjunction with the third aspect, in some implementations of the third aspect, the acquisition unit is further configured to acquire the user's input of logging into the first vehicle system account in the vehicle system before acquiring the first request; wherein, the device further includes a detection unit and an application account management unit, the application account management unit being configured to maintain the first application account logged in on the first application when the detection unit detects that the first vehicle system account has been logged out and the target installation type of the first application is a rights-sharing type.

[0042] In conjunction with the third aspect, in some implementations of the third aspect, the apparatus further includes: a determining unit, configured to determine that the first application account is a member account before maintaining the first application account logged in on the first application.

[0043] In conjunction with the third aspect, in some implementations of the third aspect, the acquisition unit is further configured to acquire the user's input of logging into the second vehicle system account in the vehicle system before acquiring the first request; wherein, the device further includes a data storage area creation unit and a data access unit, the data storage area creation unit being configured to create a first data storage area when the first application is the first application installed in the vehicle system with a privacy-critical installation type, the first data storage area being the data storage area corresponding to the second vehicle system account; the acquisition unit is further configured to: acquire the first application's request to call data; the data access unit is further configured to access the data stored in the first data storage area according to the request to call data.

[0044] In conjunction with the third aspect, in some implementations of the third aspect, the device further includes an uninstallation unit; the acquisition unit is further configured to acquire a first input from a user regarding the first application, the first input being used to change the installation type of the first application; the uninstallation unit is configured to perform an uninstallation operation on the first application in response to the first input; and the installation unit is configured to install the first application according to the changed installation type.

[0045] In conjunction with the third aspect, in some implementations of the third aspect, the device further includes: a control unit for controlling the prompting device to prompt the user to select a plurality of display devices on which the first application is deployed; a receiving unit for receiving a second input from the user, the second input being used to indicate at least one of the plurality of display devices; the control unit is also used to control the display of an icon of the first application on the at least one display device.

[0046] In conjunction with the third aspect, in some implementations of the third aspect, the apparatus further includes: a sending unit for sending a first request to a server, the first request including an identifier of the target installation type; a receiving unit for receiving a first response sent by the server, the first response including an installation package corresponding to the target installation type; wherein the installation unit is used to install the first application according to the installation package.

[0047] Fourthly, an application deployment apparatus is provided, comprising: a receiving unit for receiving a first request sent by a vehicle, the first request being for requesting an installation package of a first application; an obtaining unit for obtaining a target installation type of the first application, the target installation type including privacy-critical or rights-sharing; and a sending unit for sending the installation package of the first application according to the target installation type.

[0048] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the acquisition unit is specifically used to: determine the target installation type based on the type of the first application and the mapping relationship, wherein the mapping relationship includes the correspondence between the application type and the installation type.

[0049] Fifthly, this application provides a vehicle infotainment system configured to include a first type of application and a second type of application. The first type of application includes a first application deployed on a first display device and a second application deployed on a second display device, wherein the user data of the first application and the second application are isolated from each other. The second type of application includes a third application deployed on a third display device and a fourth application deployed on a fourth display device, wherein the third application and the fourth application share the same user data.

[0050] In a sixth aspect, this application provides an application deployment apparatus, which includes a processor and a memory, wherein the memory is used to store instructions, and the processor executes the instructions stored in the memory to cause the apparatus to perform any of the possible methods in the first aspect.

[0051] In a seventh aspect, this application provides an application deployment apparatus, which includes a processor and a memory, wherein the memory is used to store instructions, and the processor executes the instructions stored in the memory to cause the apparatus to perform any of the possible methods in the second aspect.

[0052] Eighthly, this application provides an application deployment system, which includes a computing platform and multiple display devices, wherein the computing platform includes any of the possible devices in the third or sixth aspect, or includes the vehicle-mounted system described in the fifth aspect.

[0053] Ninthly, this application provides a vehicle that includes any one of the possible devices in the third or sixth aspect, or includes the vehicle infotainment system described in the fifth aspect, or includes the system described in the eighth aspect.

[0054] In a tenth aspect, this application provides a server that includes any of the possible devices described in the fourth aspect, or includes the devices described in the seventh aspect.

[0055] In one aspect, this application provides a computer program product comprising: computer program code, which, when executed on a computer, causes the computer to perform any one of the possible methods described in the first or second aspect above.

[0056] It should be noted that the above-mentioned computer program code can be stored in whole or in part on the first storage medium, wherein the first storage medium can be packaged together with the processor or packaged separately from the processor. This application embodiment does not specifically limit this.

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

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

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

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

[0061] In a fourteenth aspect, this application provides a chip system including circuitry for performing any of the possible methods described in the first or second aspect above. Attached Figure Description

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

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

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

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

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

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

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

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

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

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

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

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

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

[0075] Figure 14 is a schematic flowchart of the application deployment method provided in the embodiments of this application;

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

[0077] Figure 16 is a schematic block diagram of the application deployment device provided in an embodiment of this application;

[0078] Figure 17 is another schematic flowchart of the application deployment apparatus provided in the embodiments of this application. Detailed Implementation

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

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

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

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

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

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

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

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

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

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

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

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

[0091] (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.

[0092] (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.

[0093] (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.

[0094] (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.

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

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

[0097] 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'.

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

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

[0100] 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 also 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.

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

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

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

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

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

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

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

[0108] 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:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0154] 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'".

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0170] To facilitate understanding of the control method provided in the embodiments of this application, the application scenarios and graphical user interface (GUI) involved in this application will be described in detail below with reference to Figures 8 to 13. The processing actions (such as control, response, etc.) or steps involved in Figures 8 to 13 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.

[0171] Figure 8 illustrates an example of the GUI provided in this application embodiment. 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 810 and a function bar 820. Exemplarily, the content display area 810 includes: icons of multiple applications, each application icon used to enable an application; a login control 801 (not logged in state) for logging into the vehicle system; and Bluetooth function icons, Wi-Fi function icons, and cellular network signal icons, used to indicate the vehicle's Bluetooth on and / or connection status, Wi-Fi on status, and cellular network signal strength, respectively. The function bar 820 includes a homepage icon, seat controls, air conditioning controls, and volume controls, used to control the content display area 810 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, respectively. When the user clicks on the control 801, the vehicle can display the GUI shown in Figure 8(b) on the display screen 201.

[0172] As shown in Figure 8(b), in response to the user clicking control 801, the vehicle can display a prompt box 802 on the screen. The prompt box 802 includes the message "Please select a login method," a face recognition login control, a QR code login control, an account login control, and a cancel control. When the vehicle detects a user logging in via account, it can display an account login interface on screen 201. User A can enter their account and password on this login interface to log in to their vehicle's infotainment system account; alternatively, the vehicle can capture the user's facial image information using a camera in the cabin. If the facial image information matches the facial image information corresponding to User A's vehicle's infotainment system account, User A can log in to their vehicle's infotainment system account.

[0173] It should be noted that in this embodiment, the camera is only used to determine the user's identity for logging into the vehicle's account, and the acquisition of this information complies with the relevant laws and regulations of the relevant countries and regions. In this embodiment, before the vehicle captures the user's image through the in-cabin camera, it can prompt the user for authorization. After obtaining the user's authorization, the vehicle can capture images inside the cabin through the in-cabin camera and determine the user's identity based on those images.

[0174] As shown in Figure 8(c), after user A logs in with their vehicle infotainment account, control 801 switches from displaying "not logged in" to displaying user A's vehicle infotainment account avatar 803. When the system detects that the user has clicked the app store icon 804, the vehicle can display the GUI shown in Figure 8(d) on display screen 201.

[0175] As shown in Figure 8(d), this GUI is the display interface of the app market. This interface includes a list of popular apps for the week, comprising video apps, games, and social apps, along with installation controls for each app. When a user clicks on the installation control 805 for a social app, the vehicle can display the GUI shown in Figure 8(e) on the display screen 201.

[0176] As shown in Figure 8(e), the GUI includes a prompt box 806 containing the following information: "Please select the installation type of the social application," "Privacy-critical: The system will only log in to your application account on the screen where you log in to your vehicle account," "Benefit-sharing: The system will log in to the application account on all screens where the application is deployed after you log in to your vehicle account," a privacy-critical control 807, and a benefit-sharing control. When the user clicks on the privacy-critical control 807, the vehicle can install the social application and display the GUI shown in Figure 8(f) on the display screen 201.

[0177] As shown in Figure 8(f), in addition to displaying the icons of multiple applications as shown in Figure 8(a), the GUI also displays the icon 808 of a social application.

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

[0179] As shown in Figure 9(a), the login control 901 on the display interface indicates that the current vehicle system account is not logged in. When the user clicks on the control 901, the vehicle can display the GUI shown in Figure 9(b) on the display screen 201.

[0180] As shown in Figure 9(b), in response to a user clicking control 901, the vehicle can display a prompt box 902 on the screen. The prompt box 902 includes the message "Please select a login method," a face recognition login control, a QR code login control, an account login control, and a cancel control. When the vehicle detects a user logging in via account, it can display the account login interface on the screen 201.

[0181] As shown in Figure 9(c), after user A logs in with their vehicle infotainment account, control 901 switches from displaying "not logged in" to displaying user A's vehicle infotainment account avatar 903. When the system detects that the user has clicked on the social application icon 904, the vehicle can display the GUI shown in Figure 9(d) on display screen 201.

[0182] As shown in Figure 9(d), since User A's vehicle infotainment account is already logged in, the social application account corresponding to User A's vehicle infotainment account will also be automatically logged in. At this time, the vehicle can display the social application's interface on the display screen 201, which includes the social application's avatar 905 and chat list.

[0183] In Figure 9(d) above, the social application account logged into is associated with user A's vehicle infotainment account. For example, the social application account is the one that user A logged into most recently when logging into user A's vehicle infotainment account.

[0184] For example, Table 1 shows the accounts of multiple applications associated with User A's vehicle infotainment account.

[0185] Table 1

[0186] For example, when user A logs in with their vehicle infotainment account, the user center service unit 430 can automatically log in to account 1 on the social application deployed on the central control screen.

[0187] The process of selecting the installation type of a social application, as illustrated in Figures 8 and 9, is described above. The process of selecting the screen where the social application should be deployed is described below.

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

[0189] As shown in Figure 10(a), the GUI includes a prompt box 1001 containing the following information: "Please select the installation type of the social application," "Privacy-critical: The system will only log in to your application account on the screen where you log in to your vehicle system account," "Benefit-sharing: The system will log in to the application account on all screens where the application is deployed after you log in to your vehicle system account," a privacy-critical control 1002, and a benefit-sharing control. When the system detects that the user clicks on the privacy-critical control 1002, the vehicle can install the social application and display the GUI shown in Figure 10(b) on the display screen 201.

[0190] As shown in Figure 10(b), the GUI is a display interface for selecting the screen to be deployed. The display interface includes a prompt box 1003, which includes the prompt message "Please select the screen to be deployed" and screen options. The screen options include the central control screen, the passenger entertainment screen, the second-row left-side entertainment screen, and the second-row right-side entertainment screen.

[0191] As shown in Figure 10(c), when the system detects that the user has selected the central control screen and the second-row right-side entertainment screen and clicked the confirmation control 1004, the vehicle can deploy a privacy-critical social application on the central control screen and the second-row left-side entertainment screen.

[0192] The above vehicles can deploy privacy-critical social applications on the central control screen and the second-row left-side entertainment screen, including: the vehicle installs the main application of the social application on the central control screen and the clone application of the social application on the second-row right-side entertainment screen.

[0193] The main application includes the user data and main program segment of the main application, which includes the program associated with the application launch; the clone application includes the user data and clone application, which provides the ability to use the main application.

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

[0195] As shown in Figure 11(a), when the system detects that a user clicks on the social application icon 1101 on the second-row right-side entertainment screen, the vehicle can display the GUI shown in Figure 11(b) on the second-row right-side entertainment screen.

[0196] As shown in Figure 11(b), in response to detecting that a user clicks on icon 1101, the vehicle can display a prompt box 1102 on the entertainment screen on the right side of the second row. The prompt box 1102 includes the prompt message "Please log in to the vehicle system account first", a QR code login control, an account login control, a mobile phone number login control, and a cancel control.

[0197] For example, after detecting that a user has logged into user B's vehicle infotainment account on the second-row right-side entertainment screen, the social application account 4 corresponding to user B's vehicle infotainment account can be automatically logged into the social application deployed on the second-row right-side entertainment screen.

[0198] In one embodiment, if no vehicle system account is logged in on the entertainment screen on the right side of the second row, the system can also prompt the user to log in directly to their social application account when the user clicks on icon 1101.

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

[0200] As shown in Figure 12(a), this GUI is the display interface of the app market. This display interface includes a list of popular apps for the week, which includes video apps, games, and social apps, along with installation controls for each app. When a user clicks on the installation control 1201 for a social app, the vehicle can display the GUI shown in Figure 12(b) on the display screen 201.

[0201] As shown in Figure 12(b), the GUI includes a prompt box 1202 containing the following information: "Please select the installation type of the social application," "Privacy-critical: The system will only log in to your application account on the screen where you log in to your vehicle account," "Benefit-sharing: The system will log in to the application account on all screens where the application is deployed after you log in to your vehicle account," a privacy-critical control, and a benefit-sharing control 1203. When the system detects that the user clicks on the benefit-sharing control 1203, the vehicle can install the video application 2 and display the GUI shown in Figure 12(c) on the display screen 201.

[0202] As shown in Figure 12(c), the GUI is a display interface for selecting the screen to be deployed. The display interface includes a prompt box 1204, which includes the prompt message "Please select the screen to be deployed" and screen options. The screen options include the central control screen, the passenger entertainment screen, the second-row left-side entertainment screen, and the second-row right-side entertainment screen.

[0203] As shown in Figure 12(d), when the system detects that the user has selected the central control screen and the second-row right-side entertainment screen and clicked the confirmation control 1205, the vehicle can deploy the video application 2, which is of the benefit-sharing type, on the central control screen and the second-row left-side entertainment screen.

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

[0205] As shown in Figures 13(a) and (b), when a user's vehicle infotainment account is logged in on the central control screen or the second-row right-side entertainment screen, the account corresponding to video application 2 can also be automatically logged in on video application 2 deployed on both the central control screen and the second-row right-side entertainment screen. Figures 13(a) and (b) show that avatar 1301 is displayed on both the central control screen and the second-row right-side entertainment screen, indicating that the same video application 2 account is logged in on both screens. At this time, both user A and user B can use this video application 2 account to watch videos.

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

[0207] S1410, when obtaining the first request, obtain the target installation type of the first application. The first request is used to request the installation of the first application. The target installation type includes privacy-critical type or rights-sharing type.

[0208] Optionally, obtaining the target installation type of the first application includes: prompting the user to select from privacy-critical or rights-sharing types via a control prompt device; and obtaining the user's first input, which is used to indicate the target installation type.

[0209] For example, as shown in Figure 8(e), when the system detects a user clicking the installation control 805 corresponding to the social application, the vehicle can display a prompt box 806 on the display screen 201. This prompt box 806 includes the following information: "Please select the installation type of the social application," "Privacy-critical: The system will only log in to your application account on the screen where you log in to your vehicle account," "Benefit-sharing: The system will log in to the application account on all screens where the application is deployed after you log in to your vehicle account," a privacy-critical control 807, and a benefit-sharing control. When the system detects a user clicking the privacy-critical control 807, the vehicle can install the social application.

[0210] For example, the first input can be a click action on control 807.

[0211] Optionally, obtaining the target installation type of the first application includes: determining the target installation type based on the type of the first application and a mapping relationship, wherein the mapping relationship includes the correspondence between the application type and the installation type.

[0212] Figure 8 or Figure 12 above illustrates the process of allowing a user to select the installation type of an application by displaying a prompt box on the screen. This embodiment of the application is not limited to this. For example, the vehicle may store the aforementioned mapping relationship. When a user selects to install an application, the installation type of the application can be determined based on the application's type and the mapping relationship.

[0213] For example, Table 2 shows the correspondence between application types and installation types.

[0214] Table 2

[0215] The correspondence shown in Table 2 above is merely illustrative, and the embodiments of this application do not impose specific limitations on it.

[0216] Optionally, the method 1400 further includes: after determining the target installation type based on the type and mapping relationship of the first application, the control prompting device prompts the target installation type of the application.

[0217] For example, when the vehicle detects a user clicking the installation control 805 corresponding to a social application, it can determine that the installation type of the social application is privacy-critical according to Table 2 above. At this time, the vehicle can control the central control screen to display the prompt message "It is recommended that the installation type of the social application be privacy-critical. Privacy-critical: The system will only log in to your application account on the screen where you log in to your vehicle account," and control the confirmation, changing, and canceling of the installation type. When the vehicle detects a user clicking the confirmation control, it can request the installation package corresponding to the privacy-critical social application from the server.

[0218] Optionally, before obtaining the first request, the method 1400 further includes: obtaining the user's input of logging into the first vehicle system account in the vehicle system; wherein, the method further includes: when it is detected that the first vehicle system account has been logged out and the target installation type of the first application is privacy-critical, logging out the first application account logged in on the first application.

[0219] For example, as shown in Figure 9(c), when user A logs out of the vehicle system account, the user center service unit 430 can automatically log out account 1 logged in on the social application deployed on the central control screen.

[0220] Optionally, before obtaining the first request, the method 1400 further includes: obtaining the user's input of logging into the first vehicle system account in the vehicle system; wherein, the method 1400 further includes: when it is detected that the first vehicle system account has been logged out and the target installation type of the first application is a benefit-sharing type, maintaining the first application account logged in on the first application.

[0221] For example, suppose user A's vehicle infotainment account is logged into the central control screen shown in Figure 13(a). Then, when user A's vehicle infotainment account logs out, the account 3 of video application 2 logged into the central control screen and the entertainment screen on the right side of the second row can still remain logged in.

[0222] Optionally, the method 1400 further includes: when the login of the second vehicle system account is detected, controlling multiple screens deploying the first application to automatically log in to the second application account, wherein the second application account is the account of the first application corresponding to the second vehicle system account.

[0223] For example, when user A logs out of their vehicle infotainment account, account 3 of video application 2 logged in on the central control screen and the second-row right-side entertainment screen can remain logged in. When user B logs in with their vehicle infotainment account, the account of video application 2 logged in on the central control screen and the second-row right-side entertainment screen can be switched from account 3 to account 6.

[0224] Optionally, prior to maintaining the first application account logged in on the first application, the method 1400 further includes: determining that the first application account is a member account.

[0225] Optionally, suppose that user A's vehicle infotainment account is logged in on the central control screen shown in Figure 13(a). Then, when user A's vehicle infotainment account logs out, the vehicle can first determine whether account 3 is a member account. If account 3 is a member account, then account 3 of the video application 2 logged in on the central control screen and the entertainment screen on the second row right can remain logged in.

[0226] For example, a vehicle can determine whether an account is a member account based on the image of the area where the account 3's icon is located. For instance, if the area where the account 3's avatar is located includes information indicating a member account, such as "VIP," it can be determined that it is a member account.

[0227] Optionally, before obtaining the first request, the method 1400 further includes: obtaining the user's input when logging into the second vehicle system account in the vehicle system; wherein, the method 1400 further includes: when the first application is the first application installed in the vehicle system with a privacy-critical installation type, creating a first data storage area, the first data storage area being the data storage area corresponding to the second vehicle system account; obtaining the first application's request to call data; and accessing the data stored in the first data storage area according to the request to call data.

[0228] For example, taking user A's vehicle infotainment account as the second vehicle infotainment account, if the social application is the first privacy-critical application installed under user A's vehicle infotainment account, a data storage area can be created for user A's vehicle infotainment account in the user space. For instance, the social application accesses the data sandbox through user A's vehicle infotainment account access path unit to store image a, image b, image c, and video d. More specifically, when a user stores data through a social application, the vehicle can create a reference associated with that data (such as a reference for image a, image b, image c, and video d) and store this reference in user A's vehicle infotainment account access path unit. This reference includes fields associated with user A's vehicle infotainment account. When the application reads the aforementioned data, it can read it through the reference associated with the data. For example, when a user sends a video to a friend through a social application, and requests to read the video in the data sandbox, the video can be read through the video reference stored in user A's vehicle infotainment account access path unit.

[0229] S1420, Install the first application according to the target installation type.

[0230] Optionally, installing the first application according to the target installation type includes: sending a first request to a server, the first request including an identifier of the target installation type; receiving a first response sent by the server, the first response including an installation package corresponding to the target installation type; and installing the first application according to the installation package.

[0231] Optionally, the method 1400 further includes: obtaining a first input from a user for a first application, the first input being used to change the installation type of the first application; in response to the first input, performing an uninstallation operation on the first application and installing the first application according to the changed installation type.

[0232] For example, as shown in Figure 9(c), when a user long-presses icon 904 is detected, the vehicle can display a function box on the central control screen. This function box may include uninstallation options, change installation type options, etc. When the user selects to change the installation type, an uninstallation operation can be performed on a social application with a privacy-critical installation type, and an installation operation can be performed on a social application with a rights-sharing installation type.

[0233] For example, when the vehicle detects that the user selects the option to change the installation type, it can prompt the user to change the installation type of the social application from privacy-critical to benefit-sharing. After the user selects benefit-sharing, the system will log in to the application account on all screens where the application is deployed after logging into the vehicle's account.

[0234] Optionally, the method 1400 further includes: controlling a prompting device to prompt a user to select a plurality of display devices on which the first application is deployed; receiving a second input from the user, the second input being used to indicate at least one of the plurality of display devices; and controlling the display of an icon of the first application on the at least one display device.

[0235] For example, as shown in Figure 10(b), when a user clicks on the privacy-critical control 1002, the vehicle can install the social application and display a prompt box 1003 on the display screen 201. The prompt box 1003 includes the message "Please select the screen to be deployed" and screen options, including the central control screen, the passenger entertainment screen, the second-row left-side entertainment screen, and the second-row right-side entertainment screen. The user can select the screen to which the social application should be deployed as needed.

[0236] Figure 15 shows a schematic flowchart of the application deployment method 1500 provided in an embodiment of this application. The method 1500 can be executed by a server. The method 1500 includes:

[0237] S1510, receive a first request sent by the vehicle, the first request being for requesting the installation package of the first application.

[0238] For example, when a vehicle detects that a user has decided to install a social application, it can send a first request to a server to request the installation package of the social application.

[0239] S1520, Obtain the target installation type of the first application, which includes privacy-critical or rights-sharing types.

[0240] Optionally, obtaining the target installation type of the first application includes: determining the target installation type based on the type of the first application and a mapping relationship, wherein the mapping relationship includes the correspondence between the application type and the installation type.

[0241] For example, the server may store the mapping relationship shown in Table 2 above. The first request may include the identification information of the social application. After receiving the first request, the server can determine whether the installation type of the social application is privacy-critical based on the type of the social application and the above mapping relationship.

[0242] S1530, based on the target installation type, send the installation package of the first application.

[0243] For example, after determining that the installation type of the social application is privacy-critical, the server can send the installation package of the social application with the installation type of privacy-critical to the vehicle.

[0244] Figure 16 shows a schematic block diagram of an application deployment apparatus 1600 provided in an embodiment of this application. The apparatus 1600 includes: an acquisition unit 1610, configured to acquire a target installation type of a first application when acquiring a first request, the first request being used to request the installation of the first application, the target installation type including privacy-critical or rights-sharing; and an installation unit 1620, configured to install the first application according to the target installation type.

[0245] Optionally, the device 1600 further includes: a control unit 1630 for controlling the prompting device to prompt the user to select from either the privacy-critical type or the rights-sharing type; and an acquisition unit 1610 for acquiring a first input from the user, the first input indicating the target installation type.

[0246] Optionally, the acquisition unit 1610 is specifically used to: determine the target installation type based on the type and mapping relationship of the first application, wherein the mapping relationship includes the correspondence between the application type and the installation type.

[0247] Optionally, the acquisition unit 1610 is further configured to acquire the user's input of logging into the first vehicle system account in the vehicle system before acquiring the first request; wherein, the device further includes a detection unit and an application account management unit, the application account management unit being configured to log out the first application account logged in on the first application when the detection unit detects that the first vehicle system account has been logged out and the target installation type of the first application is privacy-critical.

[0248] Optionally, the acquisition unit 1610 is further configured to acquire the user's input of logging into the first vehicle system account in the vehicle system before acquiring the first request; wherein, the device further includes a detection unit and an application account management unit, the application account management unit being configured to maintain the first application account logged in on the first application when the detection unit detects that the first vehicle system account has been logged out and the target installation type of the first application is a rights-sharing type.

[0249] Optionally, the device 1600 further includes a determining unit for determining that the first application account is a member account before maintaining the first application account logged in on the first application.

[0250] Optionally, the acquisition unit 1610 is further configured to acquire the user's input of logging into the second vehicle system account in the vehicle system before acquiring the first request; wherein, the device further includes a data storage area creation unit and a data access unit, the data storage area creation unit is configured to create a first data storage area when the first application is the first application installed in the vehicle system with a privacy-critical installation type, the first data storage area being the data storage area corresponding to the second vehicle system account; the acquisition unit is further configured to: acquire the first application's request to call data; the data access unit is further configured to access the data stored in the first data storage area according to the request.

[0251] Optionally, the device 1600 further includes an uninstallation unit, the acquisition unit 1610 is further configured to acquire a first input from a user regarding the first application, the first input being used to change the installation type of the first application; the uninstallation unit is configured to perform an uninstallation operation on the first application in response to the first input; and the installation unit is configured to install the first application according to the changed installation type.

[0252] Optionally, the device further includes: a control unit 1630 for controlling the prompting device to prompt the user to select a plurality of display devices on which the first application is deployed; a receiving unit for receiving a second input from the user, the second input being used to indicate at least one of the plurality of display devices; the control unit is also used to control the display of an icon of the first application on the at least one display device.

[0253] Optionally, the device further includes: a sending unit for sending a first request to a server, the first request including an identifier of the target installation type; and a receiving unit for receiving a first response sent by the server, the first response including an installation package corresponding to the target installation type; wherein the installation unit 1620 is used to install the first application according to the installation package.

[0254] Figure 17 shows a schematic block diagram of an application deployment apparatus 1700 provided in an embodiment of this application. The apparatus 1700 includes: a receiving unit 1710, configured to receive a first request sent by a vehicle, the first request being for requesting an installation package of a first application; an obtaining unit 1720, configured to obtain the target installation type of the first application, the target installation type including privacy-critical or rights-sharing; and a sending unit 1730, configured to send the installation package of the first application according to the target installation type.

[0255] Optionally, the acquisition unit 1720 is specifically used to: determine the target installation type based on the type and mapping relationship of the first application, wherein the mapping relationship includes the correspondence between the application type and the installation type.

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

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

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

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

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

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

[0262] This application also provides a vehicle infotainment system configured to include a first type of application and a second type of application. The first type of application includes a first application deployed on a first display device and a second application deployed on a second display device, wherein the user data of the first application and the second application are isolated from each other. The second type of application includes a third application deployed on a third display device and a fourth application deployed on a fourth display device, wherein the third application and the fourth application share the same user data.

[0263] This application also provides an application deployment system, which may include a computing platform and multiple screens. The computing platform may include the application deployment device 1600 described above, or the vehicle infotainment system described above.

[0264] This application also provides a vehicle, which may include the application deployment device 1600 or the application deployment system described above.

[0265] This application embodiment also provides a server, which may include the application deployment device 1700 described above.

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

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

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

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

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

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

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

[0273] Those skilled in the art will clearly 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.

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

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

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

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

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

Claims

1. An application deployment method, characterized in that, include: When obtaining the first request, the target installation type of the first application is obtained. The first request is used to request the installation of the first application. The target installation type includes privacy-critical type or rights-sharing type. Install the first application according to the target installation type.

2. The method according to claim 1, characterized in that, The step of obtaining the target installation type of the first application includes: The control prompt device prompts the user to choose between privacy-critical or rights-sharing options; Obtain the user's first input, which indicates the target installation type.

3. The method according to claim 1, characterized in that, The step of obtaining the target installation type of the first application includes: Based on the type and mapping relationship of the first application, the target installation type is determined, wherein the mapping relationship includes the correspondence between the application type and the installation type.

4. The method according to any one of claims 1 to 3, characterized in that, Before obtaining the first request, the method further includes: Obtain the user's input when logging into the vehicle's infotainment system using their first vehicle account; The method further includes: When it is detected that the first vehicle system account has been logged out and the target installation type of the first application is privacy-critical, the first application account logged in on the first application will be logged out.

5. The method according to any one of claims 1 to 3, characterized in that, Before obtaining the first request, the method further includes: Obtain the user's input when logging into the vehicle's infotainment system using their first vehicle account; The method further includes: When it is detected that the first vehicle system account has logged out and the target installation type of the first application is a benefit-sharing type, the first application account that is logged in on the first application is retained.

6. The method according to claim 5, characterized in that, Before maintaining the first application account logged in on the first application, the method further includes: The first application account has been identified as a member account.

7. The method according to any one of claims 1 to 6, characterized in that, Before obtaining the first request, the method further includes: Obtain the user's input when logging into the second vehicle infotainment account in the vehicle infotainment system; The method further includes: When the first application is the first application installed in the vehicle system with a privacy-critical installation type, a first data storage area is created, and the first data storage area is the data storage area corresponding to the second vehicle system account. Obtain the data access request from the first application; According to the call request, the data stored in the first data storage area is accessed.

8. The method according to any one of claims 1 to 7, characterized in that, The method further includes: Obtain the user's first input for the first application, which is used to change the installation type of the first application; In response to the first input, the first application is uninstalled and then reinstalled according to the changed installation type.

9. The method according to any one of claims 1 to 8, characterized in that, The method further includes: The control prompt device prompts the user to select multiple display devices deployed by the first application; Receive a second input from the user, the second input being used to instruct at least one of the plurality of display devices; Control the display of the icon of the first application on the at least one display device.

10. The method according to any one of claims 1 to 9, characterized in that, Installing the first application according to the target installation type includes: Send a first request to the server, the first request including an identifier of the target installation type; Receive a first response sent by the server, wherein the first response includes the installation package corresponding to the target installation type; Install the first application according to the installation package.

11. An application deployment method, characterized in that, include: Receive a first request sent by the vehicle, the first request being used to request the installation package of the first application; Obtain the target installation type of the first application, wherein the target installation type includes privacy-critical or rights-sharing types; Based on the target installation type, send the installation package of the first application.

12. The method according to claim 11, characterized in that, The step of obtaining the target installation type of the first application includes: Based on the type and mapping relationship of the first application, the target installation type is determined, wherein the mapping relationship includes the correspondence between the application type and the installation type.

13. An application deployment device, characterized in that, include: The acquisition unit is used to acquire the target installation type of the first application when acquiring the first request, wherein the first request is used to request the installation of the first application, and the target installation type includes privacy-critical type or rights-sharing type; The installation unit is used to install the first application according to the target installation type.

14. The apparatus according to claim 13, characterized in that, The device further includes: The control unit is used to control the prompting device to prompt the user to choose between the privacy-critical type and the rights-sharing type. The acquisition unit is used to acquire the user's first input, which is used to indicate the target installation type.

15. The apparatus according to claim 13, characterized in that, The acquisition unit is specifically used for: Based on the type and mapping relationship of the first application, the target installation type is determined, wherein the mapping relationship includes the correspondence between the application type and the installation type.

16. The apparatus according to any one of claims 13 to 15, characterized in that, The acquisition unit is further configured to acquire, before acquiring the first request, the user's input of logging into the first vehicle system account in the vehicle system; The device further includes a detection unit and an application account management unit. The application account management unit is used to log out the first application account logged in on the first application when the detection unit detects that the first vehicle system account has logged out and the target installation type of the first application is privacy-critical.

17. The apparatus according to any one of claims 13 to 15, characterized in that, The acquisition unit is further configured to acquire, before acquiring the first request, the user's input of logging into the first vehicle system account in the vehicle system; The device further includes a detection unit and an application account management unit. The application account management unit is used to maintain the first application account logged in on the first application when the detection unit detects that the first vehicle system account has logged out and the target installation type of the first application is a benefit-sharing type.

18. The apparatus according to claim 17, characterized in that, The device further includes: The determining unit is used to determine that the first application account is a member account before maintaining the first application account logged in on the first application.

19. The apparatus according to any one of claims 13 to 18, characterized in that, The acquisition unit is further configured to acquire, before acquiring the first request, the user's input of logging into the second vehicle system account in the vehicle system; The device further includes a data storage area creation unit and a data access unit. The data storage area creation unit is used to create a first data storage area when the first application is the first application installed in the vehicle system with the installation type being privacy-critical. The first data storage area is the data storage area corresponding to the second vehicle system account. The acquisition unit is further configured to: acquire the first application's request to call data; The data access unit is further configured to access the data stored in the first data storage area according to the call request.

20. The apparatus according to any one of claims 13 to 19, characterized in that, The device also includes an unloading unit. The acquisition unit is further configured to acquire a first input from the user for the first application, the first input being used to change the installation type of the first application; The uninstallation unit is used to perform an uninstallation operation on the first application in response to the first input; The installation unit is used to install the first application according to the changed installation type.

21. The apparatus according to any one of claims 13 to 20, characterized in that, The device further includes: A control unit is used to control the prompting device to prompt the user to select multiple display devices deployed by the first application; A receiving unit receives a second input from a user, the second input being used to instruct at least one of the plurality of display devices; The control unit is also configured to control the display of the icon of the first application on the at least one display device.

22. The apparatus according to any one of claims 13 to 21, characterized in that, The device further includes: A sending unit is configured to send a first request to the server, the first request including an identifier of the target installation type; A receiving unit is configured to receive a first response sent by the server, wherein the first response includes an installation package corresponding to the target installation type; The installation unit is used to install the first application according to the installation package.

23. An application deployment device, characterized in that, include: A receiving unit is configured to receive a first request sent by the vehicle, wherein the first request is for requesting the installation package of a first application; The acquisition unit is used to acquire the target installation type of the first application, wherein the target installation type includes privacy-critical type or rights-sharing type. The sending unit is configured to send the installation package of the first application according to the target installation type.

24. The apparatus according to claim 23, characterized in that, The acquisition unit is specifically used for: Based on the type and mapping relationship of the first application, the target installation type is determined, wherein the mapping relationship includes the correspondence between the application type and the installation type.

25. A vehicle infotainment system, characterized in that, The vehicle infotainment system is configured to include both a first type of application and a second type of application. The first type of application includes a first application deployed on a first display device and a second application deployed on a second display device, wherein the user data of the first application and the second application are isolated from each other; The second type of application includes a third application deployed on a third display device and a fourth application deployed on a fourth display device, wherein the third application and the fourth application share the same user data.

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

27. An application deployment device, characterized in that, include: Memory, used to store computer programs; A processor for executing a computer program stored in the memory to cause the device to perform the method as described in claim 11 or 12.

28. A vehicle, characterized in that, Includes the device as described in any one of claims 13 to 22, or the vehicle infotainment system as described in claim 25, or the device as described in claim 26.

29. A server, characterized in that, Includes the apparatus as described in any one of claims 23, 24 and 27.

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

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

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

Images