Data sharing method and apparatus, and vehicle

Abstract

A data sharing method, which is applied to the field of intelligent cockpits. The method comprises: acquiring information of a first user account, wherein the first user account is one of a plurality of user accounts, the plurality of user accounts are associated with a first data storage area, each user account among the plurality of user accounts is further associated with a sub-data storage area, the sub-data storage area associated with the first user account is a second data storage area, and the first data storage area and the second data storage area belong to a first user space; and in response to obtaining a sharing request for first data under the first user account, storing the first data by means of the first data storage area.

Description

A data sharing method, device, and vehicle

[0001] This application claims the priority of the PCT application filed with the State Intellectual Property Office of China on August 30, 2024, with the application number PCT / CN2024 / 116087 and the invention name "Control Method, Device, and Vehicle", the priority of the PCT application filed with the State Intellectual Property Office of China on August 30, 2024, with the application number 202411222010X and the invention name "Data Access Method, Device, and Vehicle", the priority of the Chinese patent application filed with the State Intellectual Property Office of China on August 30, 2024, with the application number PCT / CN2024 / 116091 and the invention name "Application Deployment Method, Device, and Vehicle", the priority of the Chinese patent application filed with the State Intellectual Property Office of China on August 30, 2024, with the application number 2024112192858 and the invention name "Method, Device, and Vehicle for Application Uninstallation", the priority of the PCT application filed with the State Intellectual Property Office of China on August 30, 2024, with the application number PCT / CN2024 / 116079 and the invention name "Application Deployment Method, Device, In-vehicle System, and Vehicle", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of intelligent cockpits, and more specifically, to a data sharing method, device, and vehicle. Background Art

[0003] With the improvement of vehicle intelligence and networking levels, vehicle cockpits are gradually developing towards intelligent cockpits centered on human-computer interaction and multi-screen linkage. The display screens in current intelligent cockpits may be used by different users at different times. Users may hope that some data is not visible to other users while some data can be seen by other users. How to flexibly store data has become an urgent problem to be solved.

[0004] Summary of the Invention

[0005] This application provides a data sharing method, device, and vehicle, which helps to achieve flexible data storage in the cockpit.

[0006] In a first aspect, this application provides a data sharing method, the method comprising: obtaining information of a first user account, wherein the first user account is one of a plurality of user accounts, the plurality of user accounts are associated with a first data storage area, each user account under the plurality of user accounts is further associated with a sub-data storage area, the sub-data storage area associated with the first user account is a second data storage area, the first data storage area and the second data storage area belong to a first user space; and in response to obtaining a request to share first data under the first user account, storing the first data through the first data storage area.

[0007] Based on the above technical solution, a first user account can be associated with a second data storage area corresponding to that first user account, or it can be associated with first data storage areas corresponding to multiple user accounts. This allows users to flexibly store their data. If a user considers the data to have a high level of privacy, they can store it in the second data storage area. If a user believes the data can be shared with other users, they can store it in the first data storage area.

[0008] In conjunction with the first aspect, in some implementations of the first aspect, before storing the first data through the first data storage area, the method further includes: in response to input that the first data is stored under the first user account, storing the first data through the second data storage area; wherein, storing the first data through the first data storage area includes: in response to obtaining the sharing request, controlling the first data to switch from being stored in the second data storage area to being stored in the first data storage area.

[0009] Based on the above technical solution, when a user obtains the first data, they can save it in a second data storage area corresponding to that first user account. Upon detecting a user's request to share the data, the storage location of the first data can be switched from the second data storage area to the first data storage area. This allows for rapid data sharing and makes it convenient for other users to view the data.

[0010] In conjunction with the first aspect, in some implementations of the first aspect, the plurality of user accounts also includes a second user account, and the method further includes: obtaining a second access request from a first application of the second user account; and when the second access request is used to request the reading of the first data, reading the first data according to the second access request.

[0011] Based on the above technical solution, when a second user account among multiple user accounts wishes to read the first data, its access request can be allowed. In this way, data shared through the first user account can be viewed by other users, enabling rapid data sharing and facilitating access to the data for other users.

[0012] In some possible implementations, the first user account is the account currently logged into the vehicle's infotainment system, and the second user account is the account logged into on the mobile phone. The first data can be data collected by sensors such as cameras outside the vehicle's cabin, allowing other users to easily view real-time shared data from the vehicle via their mobile phones, thus improving the experience when sharing data among multiple users.

[0013] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: obtaining a third access request from a second application under the first user account; when the third access request is used to request the reading of second data, reading the second data, the second data being data shared in the first data storage area through a third user account, the multiple user accounts including the third user account.

[0014] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: obtaining a fourth access request from a third application under the fourth user account, wherein the plurality of user accounts does not include the fourth user account; and rejecting the fourth access request when the fourth access request is used to request to read the first data.

[0015] Based on the above technical solution, when the fourth user account is not included among multiple users, the user can reject the access request if they access the first data through the fourth user account. This prevents unfamiliar users from seeing data in the shared data storage area, thus improving data privacy.

[0016] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: in response to adding input of a fifth user account among the plurality of user accounts, establishing an association between the fifth user account and the first data storage area.

[0017] Based on the above technical solution, when a new user account is added to a pool of multiple user accounts, a relationship can be established between the new user account and the shared data storage area. This allows the new user account to access data shared by other users through the shared data storage area, enabling rapid data sharing and facilitating data access for other users.

[0018] In conjunction with the first aspect, in some implementations of the first aspect, the multiple user accounts are user accounts under the same family group, or the accounts other than the first user account among the multiple user accounts are accounts authorized by the first user account.

[0019] Secondly, this application provides a data access method, the method comprising: controlling one or more displays in a vehicle cabin to display information of a first user space, the first user space including a first set of applications; acquiring a first input from a user, the first input indicating a switch to a preset mode; and responding to the first input, controlling the one or more displays to switch from displaying the first user space to displaying a second user space, the second user space including a second set of applications.

[0020] Based on the above technical solution, before switching to the preset mode, the vehicle's infotainment system can control one or more displays to show the first user space; after switching to the preset mode, it can control one or more displays to show the second user space. By using different user spaces, it is possible to avoid registering unfamiliar user accounts in the first user space when the vehicle is in the preset mode, or arbitrarily saving insecure data in the first user space.

[0021] In some possible implementations, the second user space can be a user space customized by the vehicle owner's account under the first user space.

[0022] In conjunction with the second aspect, in some implementations of the second aspect, the preset mode is a car rental mode or a car borrowing mode.

[0023] In conjunction with the second aspect, in some implementations of the second aspect, the first user space includes information about each of multiple user accounts, and each of the multiple user accounts is associated with a sub-data storage area.

[0024] In conjunction with the second aspect, in some implementations of the second aspect, the method further includes: obtaining input from a user logging into a first user account in the second user space; responding to obtaining a storage request for first data under the first user account, the storage request being used to request storage of the first data; and, based on the storage request, establishing an association between the first user account and a first data storage area and storing the first data through the first data storage area, the first data storage area belonging to the second user space.

[0025] Based on the above technical solution, after logging into the first user account in the second user space, the user can save the first data in the second user space using the first user account. In this way, the data stored in the preset mode is isolated from the first user space, which can prevent insecure data from affecting the first user space, or prevent car rental users from storing a lot of data in the first user space and affecting the data storage capacity of the first user space.

[0026] In conjunction with the second aspect, in some implementations of the second aspect, the method further includes: in response to a second input from a user, deleting the second user space, the second input indicating exit from the preset mode; or, in response to the second input, deleting information of user accounts under the second user space; or, in response to the second input, deleting data in the data storage area associated with each of the multiple user accounts under the second user space.

[0027] In conjunction with the second aspect, in some implementations of the second aspect, in response to a second user input, deleting the user account information in the second user space includes: when the second input indicates a taxi return mode, in response to the second input, deleting the second user space, or deleting the user account information in the second user space.

[0028] Based on the above technical solution, since the car rental model generally involves renting vehicles to renters, this avoids the process of the next renter reorganizing the second user space because they dislike the data of the previous renter in the second user space.

[0029] In conjunction with the second aspect, in some implementations of the second aspect, in response to the second input, deleting data in the data storage area associated with each user account among the multiple user accounts under the second user space includes: when the second input indicates exiting the car rental mode, in response to the second input, deleting data in the data storage area associated with each user account among the multiple user accounts under the second user space.

[0030] Based on the above technical solution, since the car-sharing mode is generally used to lend a vehicle to a friend you know, by deleting the data in the data storage area related to the user account in the second user space when exiting the car-sharing mode, the overall data storage volume of the vehicle system can be reduced, and the cumbersome operation of having to register a system account again when the same friend borrows the car next time can be avoided.

[0031] In conjunction with the second aspect, in some implementations of the second aspect, the method further includes: in response to the second input, uninstalling a third group of applications, which are applications other than the second group of applications installed by the user in the second user space.

[0032] Based on the above technical solution, since the car rental model generally involves renting the vehicle to the renter, this avoids the tedious process of the next renter deleting the application in the second user space because they don't like the application downloaded by the previous renter.

[0033] Thirdly, this application provides an application account login method, the method comprising: in response to an event in which a first user account logs in on a first display screen of a vehicle, logging in on a first group of applications associated with the first user account on the first display screen according to the association relationship between the first user account and applications, and logging in on a second group of applications associated with the first user account on multiple displays other than the first display screen, the first group of applications including privacy-critical applications and / or benefit-sharing applications, the second group of applications including benefit-sharing applications; in response to an event in which a second user account logs in on a second display screen of the vehicle, logging in on a third group of applications associated with the second user account on the second display screen according to the association relationship between the second user account and applications, the third group of applications including privacy-critical applications, the multiple displays including the second display screen.

[0034] Based on the above technical solution, when multiple user accounts log in, the first user account can log in to the application accounts of privacy-critical applications and rights-sharing applications associated with the first user account on the first display screen, and can also log in to the application accounts of rights-sharing applications associated with the first user account on other display screens. After the second user account logs in, it can log in to the application accounts of privacy-critical applications associated with the second user account on the second display screen. This application proposes a mechanism for application account login after multiple user accounts log in, which can avoid conflicts during application account login.

[0035] In conjunction with the third aspect, in some implementations of the third aspect, the second group of applications includes the first application, and the first application is deployed on the second display screen. The method includes: when the account of the first application associated with the first user account is a non-member account and the account of the first application associated with the second user account is a member account, switching the account of the first application deployed on the multiple display screens to the account of the first application associated with the second user account.

[0036] Based on the above technical solution, users in the cabin can conveniently experience the first application with a membership account on various displays, avoiding the need for users to make additional payments when using the first application, and eliminating the need for users to manually switch to a membership account, which helps to improve the user's driving experience.

[0037] In conjunction with the third aspect, in some implementations of the third aspect, the second group of applications includes a second application, which is deployed on the second display screen. The method includes: maintaining the account of the second application deployed on the multiple display screens when the account of the second application associated with the first application account is a member account and the account of the second application associated with the second user account is a non-member account; or maintaining the account of the second application deployed on the multiple display screens when the account of the second application associated with the first application account is a member account and the account of the second application associated with the second user account is a member account.

[0038] In conjunction with the third aspect, in some implementations of the third aspect, the rights-sharing application in the first group of applications includes the third application, or the second group of applications includes the third application. The method further includes: when the third application is not deployed on the second display screen, in response to the user's input to deploy the third application on the second display screen, deploying the icon of the third application on the second display screen and logging in the account of the third application associated with the first user account on the second display screen.

[0039] Based on the above technical solution, after a user deploys a rights-sharing third application that has been previously deployed on other displays on the second display, the user can automatically log in to the account of the third application associated with the first user's account.

[0040] In conjunction with the third aspect, in some implementations of the third aspect, the first group of applications, the second group of applications, and the third group of applications do not include a fourth application, which is a rights-sharing application. The method further includes: in response to user input to deploy the fourth application on the second display screen, installing the fourth application on the second display screen and logging into the account of the fourth application associated with the second user account on the second display screen.

[0041] Based on the above technical solution, after a user deploys a rights-sharing fourth application on the second display screen that has not been previously deployed on other display screens, the user can automatically log in to the application account associated with the second user account.

[0042] In some possible implementations, the method further includes: in response to user input to deploy the fourth application on the first display screen, deploying the icon of the fourth application on the first display screen and logging in the account of the fourth application associated with the second user account on the first display screen.

[0043] In conjunction with the third aspect, in some implementations of the third aspect, the third group of applications does not include the fifth application, which is a privacy-critical application. The method further includes: when the fifth application is deployed on other displays besides the second display among the multiple displays, in response to the user's input to deploy the fifth application on the second display, installing a clone application corresponding to the fifth application on the second display and logging into the account of the fifth application associated with the second user account on the second display; or, when the fifth application is not deployed on other displays besides the second display among the multiple displays, in response to the user's input to deploy the fifth application on the second display, installing the main application corresponding to the fifth application on the second display and logging into the account of the fifth application associated with the second user account on the second display.

[0044] Based on the above technical solution, after a user deploys a privacy-critical fifth application on the second display screen that has not been previously deployed on other display screens, the user can install the main application of the fifth application and automatically log in to the application account associated with the second user account; or, after a user deploys a privacy-critical fourth application on the second display screen that has previously been deployed on other display screens, the user can install a clone application of the fifth application and automatically log in to the application account associated with the second user account.

[0045] Fourthly, a data access method is provided, which can be executed by a vehicle, for example, by the vehicle's computing platform, or by a chip or circuitry used in the vehicle.

[0046] The method includes: obtaining information about a first user account, wherein the first user account is one of multiple user accounts, each user account is associated with a sub-data storage area, and the multiple sub-data storage areas associated with the multiple user accounts belong to the same user space; obtaining a first access request of a first application under the first user account, wherein the first access request is used to request the storage of first data; and storing the first data through the first sub-data storage area corresponding to the first user account according to the first access request, wherein the multiple sub-data storage areas include the first sub-data storage area.

[0047] In some implementations, the first sub-data storage area stores the association between each piece of data and the first user account. The association between each piece of data and the first user account can be a field that includes a data identifier and a first user account identifier. Alternatively, the aforementioned association can also be a field that includes a data identifier, an identifier of the application storing the data, and a first user account identifier.

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

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

[0050] In some implementations, the first data refers to a first type of data. The method further includes: when a second access request is made to request the reading of the first type of data, reading a first set of data from the data storage area according to the second access request, wherein each item in the first set of data is first type of data, and the first set of data does not include the first data itself. The first type of data can be multimedia data, such as images or videos, or it can be data of categories such as files.

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

[0052] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the method further includes: obtaining a third access request from a third application under the first user account, wherein the third application is an application that does not need to go through the first sub-data storage area when storing data; and rejecting the third access request when the third access request is used to request to read the first data.

[0053] In some implementations, the first data is first type of data. The method further includes: when a third access request is made to request the reading of the first type of data, a second set of data is read from the data storage area according to the second access request, wherein each item in the second set of data is first type of data, and the second set of data does not include the first data.

[0054] It should be noted that the second set of data can be the same as the first set of data, or they can be different.

[0055] In some implementations, the first application is a type of application that requires data isolation. The third application is a type of application that does not require data isolation.

[0056] In the above technical solution, the data stored by the first user account through the first sub-data storage area, that is, the data stored by the first type of application under the first user account, cannot be accessed by the second type of application under the first user account. This can avoid the risk of data leakage by the second type of application under the user account through the first sub-data storage area, and help to further improve the privacy and security of user data.

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

[0058] In the above technical solution, the first type of application under the first user account can read the data stored in the public storage area for the second type of application under the first user account. This helps to improve the flexibility of the first type of application in reading and writing data while ensuring data privacy and security, thereby improving the user's application experience.

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

[0060] In the above technical solution, the permission of the first user account can determine whether to respond to the request of the first type of application to read data stored in the public storage area, which helps to further improve data privacy and security. The permissions of the first user account can be determined in response to the user's settings, allowing the user to flexibly modify relevant permissions, which helps to improve the convenience of using the vehicle system and thus improve the user's driving experience.

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

[0062] In some implementations, the fourth application is the first type of application.

[0063] In the above technical solution, the fourth application, which is also a first type of application, can read the first data stored by the first application. This helps to improve the flexibility of the first type of application in reading and writing data while ensuring data privacy and security, thereby improving the user experience of using the application.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0144] In conjunction with the eighth aspect, in some implementations of the eighth 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.

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

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

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

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

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

[0150] In conjunction with the eighth aspect, in some implementations of the eighth 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.

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

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

[0153] In conjunction with the eighth aspect, in some implementations of the eighth 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.

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

[0155] In conjunction with the eighth aspect, in some implementations of the eighth 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.

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

[0157] In conjunction with the eighth aspect, in some implementations of the eighth 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.

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

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

[0160] In conjunction with aspect eight, in some implementations of aspect eight, 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.

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

[0162] In conjunction with the eighth aspect, in some implementations of the eighth 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; and 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.

[0163] In conjunction with the eighth aspect, in some implementations of the eighth 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.

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

[0165] In conjunction with aspect eight, in some implementations of aspect eight, 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.

[0166] Ninthly, 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 a 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.

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

[0168] In conjunction with the ninth aspect, in some implementations of the ninth 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.

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

[0170] In a tenth aspect, an application deployment method is provided, which can be executed by a vehicle, for example, by the vehicle's computing platform, or by a chip or circuitry used in the vehicle.

[0171] The method includes: in response to a first input to a first application displayed on a first display screen of a vehicle, obtaining a first instruction, the first instruction instructing the deployment of the first application on at least one display screen in the vehicle other than the first display screen; and deploying the first application on at least one display screen according to the first instruction.

[0172] In some implementations, the first instruction is generated based on the first input.

[0173] In the above technical solution, the deployment of an application that has been deployed on one or more displays in the vehicle cabin can be flexibly adjusted. For example, the application can be deployed to other displays that have not been deployed, which helps to meet the different application usage needs at different times in the cabin, thereby improving the user experience.

[0174] In conjunction with the tenth aspect, in some implementations of the tenth aspect, deploying the first application on at least one display screen according to the first instruction includes: according to the first instruction, a control prompting device prompts first information, the first information being used to prompt a user to select a display screen on which the first application is to be deployed; and in response to the user's operation of selecting at least one display screen, deploying the first application on at least one display screen.

[0175] In the above technical solution, deploying the first application to the display screen selected by the user can realize personalized customization of application deployment, meet the user's personalized needs, and improve the user's interactive experience during vehicle use.

[0176] In conjunction with the tenth aspect, in some implementations of the tenth aspect, at least one display screen includes a second display screen associated with a first area of ​​the vehicle, and deploying a first application on the at least one display screen according to a first instruction includes: when a user is present in the first area, deploying the first application on the second display screen according to the first instruction.

[0177] The second display screen is the display screen in which the first application has not been deployed before the first instruction is received.

[0178] In the above technical solution, when a redeployment instruction (such as a first instruction) for the first application is detected, the first application can be automatically deployed to the display screen corresponding to the area of ​​the detected user. This eliminates the need for the user to manually select the display screen where the first application needs to be deployed, thus simplifying the user's operation steps and improving the vehicle's intelligence level.

[0179] In conjunction with aspect ten, in some implementations of aspect ten, the type of the first application is a first type or a second type, where the first type indicates that the application needs to be data isolated and the second type indicates that the application does not need to be data isolated; deploying the first application on at least one display screen according to the first instruction includes: deploying the first application on at least one display screen according to the first instruction and the type of the first application.

[0180] In conjunction with the tenth aspect, in certain implementations of the tenth aspect, deploying the first application on at least one display screen according to the first instruction and the type of the first application includes: when the type of the first application is a first type, adding a first icon of the first application to each of the at least one display screen and loading application data of the first application associated with each display screen; when the type of the first application is a second type, adding a second icon of the first application to each of the at least one display screen; wherein the first icon and the second icon are the entry points for the user to use the first application.

[0181] In the above technical solution, different deployment methods are adopted for different types of applications so that the applications can run normally when deployed to other displays.

[0182] In conjunction with the tenth aspect, in some implementations of the tenth aspect, the method further includes: in response to a second input to the first application, obtaining a second instruction indicating a change in the type of the first application; and according to the second instruction, changing the first application from its original type to a target type; wherein the original type is a first type and the target type is a second type; or, the original type is a second type and the target type is a first type.

[0183] In the above technical solution, when the application supports a change in type, the application type can be changed in response to the user's operation, which helps to further improve the flexibility of application deployment.

[0184] In conjunction with aspect ten, in some implementations of aspect ten, changing the first application from its original type to the target type according to the second instruction includes: uninstalling the first application of the original type and deploying the first application of the target type according to the second instruction.

[0185] In conjunction with the tenth aspect, in some implementations of the tenth aspect, deploying the first application on at least one display screen according to the first instruction includes: when the first user account logs into the vehicle's infotainment system via the first display screen, deploying the first application on at least one display screen according to the first instruction; wherein the first user account is the vehicle owner's account, or the first user account is an account authorized by the vehicle owner.

[0186] In the above technical solution, when the account used to log in to the vehicle system is the vehicle owner's account or an account authorized by the vehicle owner, the deployment strategy of the installed applications can be adjusted, which helps to protect the privacy and security of the vehicle.

[0187] In conjunction with the tenth aspect, in some implementations of the tenth aspect, the method further includes: unloading the first application on the first display screen according to the first instruction.

[0188] In the above technical solution, while deploying the first application to at least one display screen other than the first display screen according to the first instruction, the first application on the first display screen can also be uninstalled. When the user does not want to keep the first application on the first display screen, no additional uninstallation operation is required, which helps to further improve the flexibility of application deployment.

[0189] In conjunction with aspect ten, in some implementations of aspect ten, the first application is an application other than a security-critical application.

[0190] In the above technical solution, no interface is provided to change or adjust the deployment location for safety-critical applications, which helps to ensure vehicle safety by preventing changes to the type and / or deployment location of safety-critical applications.

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

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

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

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

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

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

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

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

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

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

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

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

[0203] In conjunction with the eleventh aspect, in some implementations of the eleventh aspect, the response to the first uninstallation command to delete the icon of the first application on the first screen without performing the uninstallation operation on the first application includes: when the type of the first application is a clone, the first clone application corresponding to the first application is deployed on the first screen and the main application corresponding to the first application is deployed on the third screen, the response to the first uninstallation command to delete the icon of the first application on the first screen and uninstall the first clone application.

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

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

[0206] Based on the above technical solution, when the first application is a clone application, and the main application corresponding to the first application is deployed on the first screen in the cockpit and the clone application corresponding to the first application is deployed on the fourth screen, if the user's operation of uninstalling the first application deployed on the first screen is detected, only the icon of the first application displayed on the first screen can be deleted.

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

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

[0209] In conjunction with the eleventh aspect, in some implementations of the eleventh aspect, the response to the first uninstallation instruction, according to the type of the first application, to perform an uninstallation operation includes: responding to the first uninstallation instruction to control the first screen to display a first interface, the first interface including prompt information, the prompt information being used to prompt the user to delete the icon of the first application deployed on the first screen or uninstall the first application; receiving a first instruction from the user on the first interface; and performing the uninstallation operation according to the first instruction.

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

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

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

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

[0214] In a twelfth aspect, this application provides a data sharing apparatus, comprising: an acquisition unit for acquiring information of a first user account, wherein the first user account is one of a plurality of user accounts, the plurality of user accounts are associated with a first data storage area, each user account under the plurality of user accounts is further associated with a sub-data storage area, the sub-data storage area associated with the first user account is a second data storage area, and the first data storage area and the second data storage area belong to a first user space; and a data storage unit for storing the first data through the first data storage area in response to acquiring a sharing request for first data under the first user account.

[0215] In conjunction with the twelfth aspect, in some implementations of the twelfth aspect, the data storage unit is configured to, in response to inputting an input to store the first data under the first user account, store the first data in the second data storage area before storing the first data in the first data storage area; and in response to receiving the sharing request, control the first data to switch from being stored in the second data storage area to being stored in the first data storage area.

[0216] In conjunction with the twelfth aspect, in some implementations of the twelfth aspect, the plurality of user accounts further includes a second user account, the device further includes a data reading unit, and the acquisition unit is further configured to acquire a second access request of the first application of the second user account; the data reading unit is configured to read the first data according to the second access request when the second access request is used to request to read the first data.

[0217] In conjunction with the twelfth aspect, in some implementations of the twelfth aspect, the device further includes a data reading unit, the acquisition unit being configured to acquire a third access request from a second application under the first user account; the data reading unit is further configured to read the second data when the third access request requests to read the second data, the second data being data shared in the first data storage area through a third user account, the plurality of user accounts including the third user account.

[0218] In conjunction with the twelfth aspect, in some implementations of the twelfth aspect, the apparatus further includes a data reading unit, the acquisition unit being configured to acquire a fourth access request from a third application under the fourth user account, wherein the plurality of user accounts does not include the fourth user account; the data reading unit is further configured to reject the fourth access request when the fourth access request is used to request to read the first data.

[0219] In conjunction with the twelfth aspect, in some implementations of the twelfth aspect, the data storage unit is further configured to establish an association between the fifth user account and the first data storage area in response to inputting a fifth user account among the plurality of user accounts.

[0220] In conjunction with the twelfth aspect, in some implementations of the twelfth aspect, the multiple user accounts are user accounts under the same family group, or the accounts other than the first user account among the multiple user accounts are accounts authorized by the first user account.

[0221] In a thirteenth aspect, this application provides an apparatus for switching user spaces, the apparatus comprising: a control unit for controlling one or more displays in a vehicle cabin to display information of a first user space, the first user space including a first set of applications; an acquisition unit for acquiring a first input from a user, the first input indicating a switch to a preset mode; the control unit further comprising, in response to the first input, controlling the one or more displays to switch from displaying the first user space to displaying a second user space, the second user space including a second set of applications.

[0222] In conjunction with aspect thirteen, in some implementations of aspect thirteen, the preset mode is a car rental mode or a car borrowing mode.

[0223] In conjunction with aspect thirteen, in some implementations of aspect thirteen, the first user space includes information about each of a plurality of user accounts, each of which is associated with a sub-data storage area.

[0224] In conjunction with aspect thirteen, in some implementations of aspect thirteen, the apparatus further includes a data storage unit. The acquisition unit is further configured to acquire input from a user logging into a first user account in the second user space. The data storage unit is further configured to respond to a request to acquire storage of first data under the first user account, the storage request being used to request storage of the first data. The data storage unit is further configured to establish an association between the first user account and a first data storage area based on the storage request and to store the first data through the first data storage area, the first data storage area belonging to the second user space.

[0225] In conjunction with the thirteenth aspect, in some implementations of the thirteenth aspect, the device further includes a data deletion unit, which is configured to delete the second user space in response to a second input from a user, the second input indicating exit from the preset mode; or, in response to the second input, delete information of user accounts under the second user space; or, in response to the second input, delete data in the data storage area associated with each of the multiple user accounts under the second user space.

[0226] In conjunction with aspect thirteen, in some implementations of aspect thirteen, the data deletion unit is specifically used to: in response to the second input indicating a taxi return mode, delete the second user space, or delete the user account information under the second user space.

[0227] In conjunction with aspect thirteen, in some implementations of aspect thirteen, the data deletion unit is specifically used to: upon the second input indicating exit from the car rental mode, in response to the second input, delete data in the data storage area associated with each of the multiple user accounts in the second user space.

[0228] In conjunction with the thirteenth aspect, in some implementations of the thirteenth aspect, the apparatus further includes an application uninstallation unit for uninstalling a third set of applications in response to the second input, the third set of applications being applications installed by the user in the second user space other than the second set of applications.

[0229] In a fourteenth aspect, this application provides an application account login device, comprising: an acquisition unit for acquiring an event of a first user account logging in on a first display screen of a vehicle; an application account login unit for, in response to the event of the first user account logging in on the first display screen, logging in a first group of applications associated with the first user account on the first display screen according to the association relationship between the first user account and applications, and logging in a second group of applications associated with the first user account on multiple displays other than the first display screen, wherein the first group of applications includes privacy-critical applications and / or benefit-sharing applications, and the second group of applications includes benefit-sharing applications; the application account login unit is further configured to, in response to an event of a second user account logging in on a second display screen of the vehicle, logging in a third group of applications associated with the second user account on the second display screen according to the association relationship between the second user account and applications, wherein the third group of applications includes privacy-critical applications, and the multiple displays include the second display screen.

[0230] In conjunction with the fourteenth aspect, in some implementations of the fourteenth aspect, the second set of applications includes a first application, the first application is deployed on the second display screen, and the application account login unit is further configured to switch the account of the first application deployed on the multiple display screens to the account of the first application associated with the second user account when the account of the first application associated with the first user account is a non-member account and the account of the first application associated with the second user account is a member account.

[0231] In conjunction with the fourteenth aspect, in some implementations of the fourteenth aspect, the second set of applications includes a second application, the second display screen is deployed with the second application, and the application account login unit is further configured to maintain the account of the second application deployed on the plurality of display screens when the account of the second application associated with the first application account is a member account and the account of the second application associated with the second user account is a non-member account; or, when the account of the second application associated with the first application account is a member account and the account of the second application associated with the second user account is a member account, maintain the account of the second application deployed on the plurality of display screens.

[0232] In conjunction with the fourteenth aspect, in some implementations of the fourteenth aspect, the rights-sharing application in the first group of applications includes a third application, or the second group of applications includes a third application. The application account login unit is further configured to, when the third application is not deployed on the second display screen, respond to the user's input to deploy the third application on the second display screen, deploy the icon of the third application on the second display screen and log in to the account of the third application associated with the first user account on the second display screen.

[0233] In conjunction with the fourteenth aspect, in some implementations of the fourteenth aspect, the first group of applications, the second group of applications, and the third group of applications do not include a fourth application, which is a rights-sharing application. The application account login unit is further configured to respond to user input on deploying the fourth application on the second display screen, install the fourth application on the second display screen, and log in to the account of the fourth application associated with the second user account on the second display screen.

[0234] In conjunction with the fourteenth aspect, in some implementations of the fourteenth aspect, the third group of applications does not include the fifth application, which is a privacy-critical application. The application account login unit is further configured to, when the fifth application is deployed on other displays besides the second display among the plurality of displays, in response to the user's input to deploy the fifth application on the second display, install the corresponding clone application of the fifth application on the second display and log in to the account of the fifth application associated with the second user account on the second display; or, when the fifth application is not deployed on other displays besides the second display among the plurality of displays, in response to the user's input to deploy the fifth application on the second display, install the corresponding main application of the fifth application on the second display and log in to the account of the fifth application associated with the second user account on the second display.

[0235] In a fifteenth aspect, a data access device is provided, comprising an acquisition unit and a processing unit, wherein the acquisition unit is configured to: acquire information of a first user account, the first user account being one of a plurality of user accounts, each of the plurality of user accounts being associated with a sub-data storage area, and the plurality of sub-data storage areas associated with the plurality of user accounts belonging to the same user space; the acquisition unit is further configured to: acquire a first access request of a first application under the first user account, the first access request being used to request the storage of first data; and the processing unit is configured to: store the first data through the first sub-data storage area corresponding to the first user account according to the first access request, the plurality of sub-data storage areas including the first sub-data storage area.

[0236] In conjunction with aspect 15, in some implementations of aspect 15, the multiple user accounts also include a second user account, the second user account being associated with a second sub-data storage area in the multiple sub-data storage areas, and the acquisition unit is further configured to: acquire a second access request of a second application of the second user account; the processing unit is further configured to: reject the second access request when the second access request is used to request to read the first data.

[0237] In conjunction with aspect 15, in some implementations of aspect 15, the acquiring unit is further configured to: acquire a third access request from a third application under the first user account, wherein the third application is an application that does not need to pass through the first sub-data storage area when storing data; the processing unit is further configured to: reject the third access request when the third access request is for requesting to read the first data.

[0238] In conjunction with aspect 15, in some implementations of aspect 15, the acquisition unit is further configured to: acquire a fourth access request from the first application, the fourth access request being for requesting to read second data, the second data being data stored by the third application; the processing unit is further configured to: read the second data according to the fourth access request.

[0239] In conjunction with aspect 15, in some implementations of aspect 15, the second data is stored in a public storage area, and the processing unit is configured to: read the second data according to a fourth access request when the first user account is authorized to access the public storage area.

[0240] In conjunction with aspect 15, in some implementations of aspect 15, the third application is a type 2 application, which is an application that does not require data isolation.

[0241] In conjunction with aspect 15, in some implementations of aspect 15, the acquisition unit is further configured to: acquire a fifth access request from a fourth application under a first user account, the fifth access request being used to request the reading of first data; the processing unit is further configured to: when the fourth application is an application that needs to access the first sub-data storage area to store data, read the first data according to the fifth access request.

[0242] In conjunction with aspect 15, in some implementations of aspect 15, the first application is the first type of application, which is an application that requires data isolation.

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

[0244] When the apparatus is used to perform the method provided in any of the fifth or sixth aspects, the apparatus may include a processing unit (or processing module). Optionally, the apparatus may also include a transceiver unit (or transceiver module). In some implementations, the transceiver unit includes an acquisition unit, which may be a receiving unit within the transceiver unit.

[0245] When the apparatus is used to perform the method provided in any of the seventh aspects, the apparatus may include an acquisition unit and a processing unit.

[0246] In a seventeenth aspect, an application deployment apparatus is provided, the apparatus 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.

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

[0248] In conjunction with the seventeenth aspect, in some implementations of the seventeenth 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.

[0249] In conjunction with the seventeenth aspect, in some implementations of the seventeenth 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.

[0250] In conjunction with the seventeenth aspect, in some implementations of the seventeenth 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.

[0251] In conjunction with the seventeenth aspect, in some implementations of the seventeenth aspect, the apparatus 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.

[0252] In conjunction with the seventeenth aspect, in some implementations of the seventeenth 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.

[0253] In conjunction with the seventeenth aspect, in some implementations of the seventeenth aspect, the apparatus 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.

[0254] In conjunction with the seventeenth aspect, in some implementations of the seventeenth aspect, the apparatus further includes: a control unit for controlling a prompting device to prompt a 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 further configured to control the display of an icon of the first application on the at least one display device.

[0255] In conjunction with the seventeenth aspect, in some implementations of the seventeenth 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.

[0256] Eighteenthly, an application deployment apparatus is provided, the apparatus 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.

[0257] In conjunction with the eighteenth aspect, in some implementations of the eighteenth 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.

[0258] In a nineteenth aspect, an application deployment apparatus is provided, the apparatus including an acquisition unit and a processing unit, wherein the acquisition unit is configured to: acquire a first instruction in response to a first input for a first application displayed on a first display screen of a vehicle, the first instruction instructing the first application to be deployed on at least one display screen in the vehicle other than the first display screen; and the processing unit is configured to: deploy the first application on at least one display screen according to the first instruction.

[0259] In conjunction with the nineteenth aspect, in some implementations of the nineteenth aspect, the processing unit is further configured to: control the prompting device to prompt first information according to the first instruction, the first information being used to prompt the selection of a second display screen for deploying the first application, at least one display screen including the second display screen; the processing unit is configured to: deploy the first application on the second display screen according to the first instruction.

[0260] In conjunction with the nineteenth aspect, in some implementations of the nineteenth aspect, at least one display screen includes a second display screen associated with a first area of ​​the vehicle, and the processing unit is configured to: when a user is present in the first area, deploy a first application on the second display screen according to a first instruction.

[0261] In conjunction with the nineteenth aspect, in some implementations of the nineteenth aspect, the type of the first application is a first type or a second type, where the first type indicates that the application needs to be data isolated and the second type indicates that the application does not need to be data isolated; the processing unit is configured to: deploy the first application on at least one display screen according to the first instruction and the type of the first application.

[0262] In conjunction with the nineteenth aspect, in some implementations of the nineteenth aspect, the processing unit is configured to: when the type of the first application is a first type, add a first icon of the first application to each of the at least one display screen, and load application data of the first application associated with each display screen; when the type of the first application is a second type, add a second icon of the first application to each of the at least one display screen; wherein the first icon and the second icon are entry points for the user to use the first application.

[0263] In conjunction with the nineteenth aspect, in some implementations of the nineteenth aspect, the acquisition unit is further configured to: acquire a second instruction in response to a second input to the first application, the second instruction indicating a change in the type of the first application; the processing unit is further configured to: change the first application from its original type to a target type according to the second instruction; wherein the original type is a first type and the target type is a second type; or, the original type is a second type and the target type is a first type.

[0264] In conjunction with the nineteenth aspect, in some implementations of the nineteenth aspect, the processing unit is used to: unload the first application of the original type and deploy the first application of the target type according to the second instruction.

[0265] In conjunction with the nineteenth aspect, in some implementations of the nineteenth aspect, the processing unit is configured to: when a first user account logs into the vehicle's infotainment system via a first display screen, deploy a first application on at least one display screen according to a first instruction; wherein the first user account is the vehicle owner's account, or the first user account is an account authorized by the vehicle owner.

[0266] In conjunction with the nineteenth aspect, in some implementations of the nineteenth aspect, the processing unit is further configured to: unload the first application on the first display screen according to the first instruction.

[0267] In conjunction with aspect nineteen, in some implementations of aspect nineteen, the first application is an application other than a security-critical application.

[0268] In a twentieth aspect, an application uninstallation apparatus is provided, the apparatus comprising: an acquisition unit for acquiring a first uninstallation instruction from a user for a first application on a first screen, the first application being deployed on multiple screens within a cockpit, the multiple screens including the first screen; and a processing unit for, in response to the first uninstallation instruction, performing an uninstallation operation according to the type of the first application, the type of the first application including a clone or an instance.

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

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

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

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

[0273] In conjunction with the twentieth aspect, in some implementations of the twentieth aspect, the acquiring unit is further configured to acquire a third uninstallation instruction from the user for the first application on the fifth screen; the processing unit is further configured to uninstall the main application in response to the third uninstallation instruction when the fifth screen is the only screen among the plurality of screens where the icon of the first application is deployed.

[0274] In conjunction with the twentieth aspect, in some implementations of the twentieth aspect, the apparatus further includes: a control unit, configured to control the first screen to display a first interface in response to the first uninstallation command, the first interface including prompt information for prompting the user to delete the icon of the first application deployed on the first screen or uninstall the first application; a receiving unit, configured to receive a first command from the user on the first interface; and a processing unit, configured to perform an uninstallation operation according to the first command.

[0275] In conjunction with the twentieth aspect, in some implementations of the twentieth aspect, the apparatus further includes: a control unit for controlling the first screen to display a second interface in response to the first unloading instruction, the second interface including information from the plurality of screens; a receiving unit for receiving a second instruction from a user on the first interface, the second instruction instructing at least one of the plurality of screens; and a processing unit for performing an unloading operation according to the second instruction.

[0276] In a twentieth aspect, 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.

[0277] In a twentieth aspect, this application provides a data processing 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 one of the possible methods in the first to eleventh aspects.

[0278] In a twentieth aspect, this application provides a data processing system, which includes a computing platform and a plurality of display devices, wherein the computing platform includes any one of the possible devices in aspects twelfth to twentieth and twentieth, or includes the vehicle infotainment system described in aspect twenty-one.

[0279] In a twentieth aspect, this application provides a vehicle that includes any one of the possible devices in aspects twelfth to twentieth and twentieth, or includes the vehicle infotainment system described in aspect twenty-one; or includes the system described in aspect twenty-three.

[0280] In a twentieth aspect, this application provides a computer program product comprising: computer program code, which, when run on a computer, causes the computer to perform any one of the possible methods described in the first to eleventh aspects above.

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

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

[0283] In a twentieth aspect, this application provides a chip system including a processor for calling a computer program or computer instructions stored in a memory, so that the processor performs any one of the possible methods described in the first to eleventh aspects above.

[0284] In conjunction with aspect twenty-six, in one possible implementation, the processor is coupled to the memory via an interface.

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

[0286] In a twentieth aspect, this application provides a chip system including circuitry for performing any one of the possible methods described in the first to eleventh aspects above. Attached Figure Description

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

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

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

[0290] Figure 4 is another schematic block diagram of the system architecture provided in the embodiments of this application;

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

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

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

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

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

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

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

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

[0299] Figure 13 is a schematic flowchart of the data access method provided in an embodiment of this application;

[0300] Figure 14 is a schematic diagram of the GUI provided in an embodiment of this application;

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

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

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

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

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

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

[0307] Figure 21 is a schematic diagram of the GUI provided in an embodiment of this application;

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

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

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

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

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

[0313] Figure 27 is a schematic flowchart of the application deployment method provided in an embodiment of this application;

[0314] Figure 28 is another schematic flowchart of the application deployment method provided in the embodiments of this application.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0333] Figure 47 is a schematic flowchart of the application uninstallation method provided in the embodiments of this application.

[0334] Figure 48 is another schematic flowchart of the application uninstallation method provided in the embodiments of this application.

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

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

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

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

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

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

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

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

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

[0344] Figure 58 is a schematic flowchart of the data sharing method provided in an embodiment of this application;

[0345] Figure 59 is another schematic diagram of the data storage architecture provided in the embodiments of this application;

[0346] Figure 60 is a schematic flowchart of the data access method provided in the embodiments of this application;

[0347] Figure 61 is a schematic flowchart of an account login method provided in an embodiment of this application. Detailed Implementation

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

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

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

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

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

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

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

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

[0356] To facilitate understanding of the technical solution of this application, the implementation methods provided by the embodiments of this application are described in detail below with reference to Figures 3 to 61.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0440] To facilitate understanding of the data access method provided in the embodiments of this application, the application scenarios and GUI involved in this application will be described in detail below with reference to Figures 8 to 12. Among them, the processing actions (such as control, response, etc.) or steps involved in Figures 8 to 12 can be executed by the computing platform 150 shown in Figure 1, or they can also be executed by the system shown above. For example, the processing actions related to data reading and writing can be executed by the public data service unit 440.

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

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

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

[0444] In some implementations, an application running under user A's system account stores data via the aforementioned access path unit, and applications running under other system accounts cannot read this data. Figures 9 and 10 illustrate a set of GUIs for this scenario.

[0445] For example, taking an instant messaging application that requires data storage via an access path unit under user A's system account as an example, the display screen 201 can respond to the user's operation and display the interface 1030 of the instant messaging application shown in Figure 9(a). The left column of this interface 1030 is a control bar, which includes an avatar 1031, the avatar of the application account logged into the instant messaging application; the control bar also includes chat controls, contact controls, and file controls, used to control the display of the chat module, contact module, and file module, respectively. The current middle column of interface 1030 shows thumbnails of multiple contacts, and the right column of interface 1030 shows the chat interface with a specific contact. For example, as shown in interface 1030, the instant messaging application receives an image 1032 from contact a. Furthermore, when a long press is detected on image 1032, the control display screen 201 displays the interface shown in Figure 9(b). This interface includes a control bar 1033, which includes an edit control, a forward control, and a save control, used for editing the image, forwarding the image to other contacts, and saving the image, respectively. When the save control is clicked, image 1032 is saved. More specifically, when the save control is clicked, the instant messaging application sends a data storage request to the public data service unit. After the public data service unit authenticates the instant messaging application, it stores image 1032 in the data storage area through the access path unit corresponding to user A's system account. For example, the save path for image 1032 is "user A's system account - instant messaging application - image 1032".

[0446] Optionally, when the image 1032 is successfully saved, the display screen 201 can be controlled to display a prompt bar 1034 as shown in Figure 9(c), which includes the prompt message "Image saved".

[0447] Furthermore, when an application running under User B's system account requests access to the image library, the application cannot obtain the aforementioned image 1032. For example, as shown in Figure 10(a), when User B's system account logs into the vehicle system via display screen 204 (i.e., the screen behind the passenger headrest), the login control on display screen 204 displays the avatar 1018 associated with User B's system account, and the instant messaging application interface displays the avatar 1035 of the application account logged into the instant messaging application by User B's system account. If the user wants to send an image to contact C through the instant messaging application running under User B's system account, they can click the image control 1036 to open the "Images and Videos" section 1037 shown in Figure 10(b), and then select an image from the "Images and Videos" section 1037 to send to contact C. More specifically, when the image control 1036 is detected to be clicked, the instant messaging application sends a data read request to the public data service unit, which is used to read images that the instant messaging application can read. In one example, if the instant messaging application running under User B's system account also needs to store data via the access path unit, then a data read request can be used to request images stored via the access path unit. In another example, if User B's system account is authorized to access the public storage area, then a data read request can also be used to request to read images from the public storage area.

[0448] In some implementations, if the images stored in the public storage area include images 6 and 7, and the applications under user B's system account that need to store data through the access path unit store images 1, 2, 3, 4, 5, and 8, and user B's system account is authorized to access the public storage area, then the public data service unit, in response to the data read request from the instant messaging application running under user B's system account, reads images 1 to 8 from the data storage area and controls the "Images and Videos" column 1037 to display these images for the user to select. That is, when the instant messaging application running under user B's system account requests to read images from the data storage area, it can only read images from the public storage area and images stored by applications under user B's system account that need to store data through the access path unit; it cannot read image 1032 stored by the instant messaging application running under user A's system account. Furthermore, Figure 10 illustrates this using an instant messaging application requesting to read data as an example. In actual implementation, when other applications running under user B's system account request to read data, these applications also cannot read image 1032.

[0449] When an application under User A's system account requests access to the image library via the access path unit, that application can obtain the aforementioned image 1032. For example, taking an instant messaging application running under User A's system account that needs to store data via the access path unit as an example, if other applications under User A's system account that need to store data via the access path unit store images a to d, and User A's system account is authorized to access the public storage area, then as shown in Figure 11(a), when the image control 1038 is detected as clicked, the instant messaging application sends a data read request to the public data service unit. This request is used to read images that the instant messaging application can read. Further, when the public data service unit successfully authenticates the data read request from the instant messaging application running under User A's system account, the public data service unit reads image 1032, images a to d, and images 6 and 7 from the data storage area, and controls the "Images and Videos" column 1039 shown in Figure 11(b) to display these images for the user to select.

[0450] When an application under User A's system account requests access to the image library without needing to store data through the access path unit, the application cannot obtain the aforementioned image 1032. Taking a video application under User A's system account that does not need to store data through the access path unit as an example, as shown in Figure 12(a), the interface of the currently shown video application includes a navigation bar 1021, a video playback bar 1022, and a playback history bar 1023, which are used to display various controls, the video playback interface, and playback history information, respectively. Among them, the navigation bar 1021 includes a login control 1024, which can be used to control the application account to log in or out of the video application, or to change the image associated with the application account that is logged into the video application. For example, if the user long-presses the login control 1024, the display screen 201 can be triggered to display the interface shown in Figure 12(b). This interface includes multiple image selection controls, a close window control, and a confirm control, which are used to select an image, close the interface in Figure 12(b), and confirm that the selected image is the image associated with the application account, respectively. More specifically, upon detecting that the login control 1024 has been clicked, the video application sends a data read request to the public data service unit. This request is used to read images that the video application can read. Further, when the public data service unit successfully authenticates the data read request from the video application running under user A's system account, the public data service unit reads images 6 and 7 from the data storage area and controls the interface shown in Figure 12(b) to display these images for the user to select.

[0451] In some implementations, the scenarios shown in Figures 10 and 11 can occur after the scenario shown in Figure 9, and the scenarios in Figures 10 and 11 can occur within the same time period. That is, when the scenarios shown in Figures 10 and 11 occur, the data stored in the data storage area is the same. However, since some applications under different system accounts store data via access path units, this data cannot be read by applications under other system accounts. Therefore, even if the data stored in the data storage area is the same, the instant messaging application running under user B's system account and the instant messaging application running under user A's system account can read different data. This helps protect the privacy and security of user data. Furthermore, the scenario shown in Figure 12 can also occur after the scenario shown in Figure 9, meaning that in this case, the data storage area includes image 1032, as well as images a to d. However, due to the permission settings of the application in Figure 12, it cannot read image 1032 and images a to d.

[0452] It should be noted that Figures 8 to 12 above use images as an example of data for illustration. In actual implementation, the aforementioned stored or retrieved data can also be other data such as videos or files.

[0453] It should also be noted that the aforementioned applications that need to store data through the access path unit can be privacy-critical applications, while the aforementioned applications that do not need to store data through the access path unit can be rights-sharing applications.

[0454] Figure 13 shows a schematic flowchart of a data access method provided in an embodiment of this application. This method 20 can be applied to the vehicle shown in Figure 1, or it can be executed by any of the systems shown in Figures 3 to 5. More specifically, the method includes:

[0455] S21, obtain the information of the first user account. The first user account is one of multiple user accounts. Each user account is associated with a sub-data storage area. The multiple sub-data storage areas associated with multiple user accounts belong to the same user space.

[0456] For example, multiple user accounts may include the aforementioned vehicle owner system account, authorized system account, etc. The sub-data storage area may be the access path unit in the aforementioned embodiments.

[0457] S22, obtain the first access request of the first application under the first user account. The first access request is used to request the storage of the first data.

[0458] For example, the first data may include data such as images, files, and videos.

[0459] In some implementations, the first application is a first-type application, which is an application that requires data isolation. For example, the first-type application is the privacy-critical application in the aforementioned embodiments.

[0460] S23, based on the first access request, the first data is stored in the first sub-data storage area corresponding to the first user account, and the multiple sub-data storage areas include the first sub-data storage area.

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

[0462] For example, taking the first user account as the system account of user A in the aforementioned embodiment and the first application as the instant messaging application running under user A's system account, the first access request can be a data storage request issued by the instant messaging application running under user A's system account. For example, it can be a data storage request generated in response to the click of the save control in the control bar 1033 shown in Figure 9(b). In this scenario, the first data can be the image 1032 shown in Figure 9(a). Further, storing the first data through the first sub-data storage area corresponding to the first user account can be done by storing the first data through the access path unit corresponding to user A's system account. For example, when storing the first data, a reference to the first data (such as a field including user A's system account) is created and stored in the access path unit so that when reading the first data later, it is necessary to read the first data through the reference to the first data stored in the access path unit. For a more specific implementation of storing the first data, please refer to the description of the corresponding part of Figure 6 and the description of the corresponding part of Figure 9, which will not be repeated here.

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

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

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

[0466] Taking multimedia data as an example, if the second user account is the system account of user B in the aforementioned embodiment, and the second application is the instant messaging application running under user B's system account, then the second access request can be a data read request issued by the instant messaging application running under user B's system account. For example, it could be a data read request generated in response to the clicking of the image control 1036 shown in Figure 10(a). As can be seen from Figure 10(b), in response to the data read request issued by the instant messaging application, the final read data result does not include the first data (such as image 1032), but includes other first-type data besides the first data (such as images 1 to 8). In the aforementioned scenario, images 1 to 8 can be regarded as an example of the first group of data.

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

[0468] In some implementations, the method further includes: obtaining a third access request from a third application under the first user account, wherein the third application is an application that does not need to go through the first sub-data storage area when storing data; and rejecting the third access request when the third access request is used to request to read the first data.

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

[0470] In some implementations, the third application is a type of second-class application, which is an application that does not require data isolation. For example, the second-class application can be a rights-sharing application as described in the foregoing embodiments.

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

[0472] Taking multimedia data as an example, if the first user account is the system account of user A in the aforementioned embodiment, and the third application is a video application running under user A's system account, then the third access request can be a data read request issued by the video application running under user A's system account. For example, it could be a data read request generated in response to the clicking of the login control 1024 shown in Figure 12(a). As can be seen from Figure 12(b), in response to the data read request issued by the video application, the final read data result does not include the first data (such as image 1032), but includes other first-type data besides the first data (such as images 6 and 7). In the aforementioned scenario, images 6 and 7 can be considered as an example of the second set of data. It should be noted that the third application can also be other rights-sharing applications.

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

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

[0475] For example, the public storage area can be the public storage area in the aforementioned embodiments, used to store data associated with rights-sharing applications. That is, the second data can be data associated with a second type of application, for example, the second data can be data stored by a second type of application. Taking the first user account as the system account of user A in the aforementioned embodiments and the first application as an instant messaging application running under user A's system account as an example, the second data can include image 6 and / or image 7 shown in FIG11. In the above scenario, the fourth access request can be a data read request issued by the instant messaging application running under user A's system account, for example, a data read request generated in response to the clicking of the image control 1038 shown in FIG11(a). As can be seen from FIG11(b), in response to the data read request issued by the instant messaging application, the final read data result includes the second data (such as image 6 and / or image 7).

[0476] For example, permissions for a first user account to access the public storage area can be set through S711 to S713 in the foregoing embodiments.

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

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

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

[0480] For example, taking the first user account as the system account of user A in the aforementioned embodiment, and the fourth application as an instant messaging application running under user A's system account, the first application can be any privacy-critical application other than the instant messaging application, and the first application stores at least one of the images a to d shown in FIG11. Therefore, at least one of the images a to d can be considered an example of the first data. In the aforementioned scenario, the fifth access request can be a data read request issued by the instant messaging application running under user A's system account, for example, a data read request generated in response to the clicking of the image control 1038 shown in FIG11(a). As can be seen from FIG11(b), in response to the data read request issued by the instant messaging application, the final read data result includes the first data (such as at least one of the images a to d).

[0481] It should be noted that the type of application involved in this application (such as a privacy-critical application or a rights-sharing application) can be the system default; or it can be set by the user. For example, when deploying the application for the first time, the user can choose the type of application, or the user can change the type of application after the application has been deployed.

[0482] The data access method provided in this application embodiment, when multiple user accounts used to log in to the vehicle system are associated with the same user space, allows applications with data privacy requirements to store the data requested by the application in the data storage area through a sub-data storage area. This can prevent applications under other user accounts from reading the data, thus helping to protect the data privacy and security of each user account.

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

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

[0485] Figure 14 illustrates an example of the GUI provided in this application embodiment. As shown in Figure 14, 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 14(a), including a content display area 1410 and a function bar 1410'. Exemplarily, the content display area 1410 includes: icons for various applications, each application icon being used to enable an application; a login control 1411 (not logged in state) for logging into the vehicle system; and Bluetooth function icons, Wi-Fi function icons, and cellular network signal icons, respectively used to indicate the vehicle's Bluetooth on and / or connection status, Wi-Fi on status, and cellular network signal strength. The function bar 1410' includes a homepage icon, seat controls, air conditioning controls, and volume controls, respectively used to control the content display area 1410 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0503] As shown in Figure 18(a), the video application interface currently displayed on screen 201 includes a navigation bar 1421, a video playback bar 1422, and a playback history bar 1423, which are used to display various controls, the video playback interface, and playback history information, respectively. The navigation bar 1421 includes a login control 1424, which allows users to log in or out of the video application using their account. As shown in Figure 18(b), the video application interface currently displayed on screen 204 includes a navigation bar, a video playback bar 1425, and a series selection bar 1426.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0522] In some implementations, method 2000 can be executed before method 1900, and the second set of applications in method 2000 includes the first set of applications in method 1900.

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

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

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

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

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

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

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

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

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

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

[0533] In some implementations of Method 1900 or Method 2000, the safety-critical applications include navigation applications or intelligent driving applications, and the safety-critical applications are logged out and / or exited when the vehicle shifts to park.

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

[0535] In some implementations of method 1900 or method 2000, if the vehicle is in drive or reverse gear, the user is prompted that the first user account cannot log out.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0556] 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 21 to 26. The processing actions (such as control, response, etc.) or steps involved in Figures 21 to 26 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.

[0557] Figure 21 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 21(a), including a content display area 2110 and a function bar 2120. Exemplarily, the content display area 2110 includes: icons of multiple applications, each application icon being used to activate one application; a login control 2101 (not logged in state) for logging into the vehicle system; and Bluetooth function icons, Wi-Fi function icons, and cellular network signal icons, respectively used to indicate the vehicle's Bluetooth on and / or connection status, Wi-Fi on status, and cellular network signal strength. The function bar 2120 includes a homepage icon, seat controls, air conditioning controls, and volume controls, respectively used to control the content display area 2110 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. When a user clicks on control 2101, the vehicle can display the GUI shown in Figure 21(b) on display screen 201.

[0558] As shown in Figure 21(b), in response to the user's click on control 2101, the vehicle can display a prompt box 2102 on the screen. The prompt box 2102 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's account login operation, 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.

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

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

[0561] As shown in Figure 21(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 2, games, and social apps, along with installation controls for each app. When a user clicks on the installation control 2105 for a social app, the vehicle can display the GUI shown in Figure 21(e) on the display screen 201.

[0562] As shown in Figure 21(e), the GUI includes a prompt box 2106 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 2107, and a benefit-sharing control. When the user clicks on the privacy-critical control 2107, the vehicle can install the social application and display the GUI shown in Figure 21(f) on the display screen 201.

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

[0564] Figure 22 shows an example of a GUI provided in an embodiment of this application.

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

[0566] As shown in Figure 22(b), in response to a user clicking control 2201, the vehicle can display a prompt box 2202 on the screen. The prompt box 2202 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 screen 201.

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

[0568] As shown in Figure 22(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 2205 and chat list.

[0569] The social application account logged into in the social application shown in Figure 22(d) above is associated with user A's vehicle infotainment account. For example, the social application account is the same social application account that user A logged into most recently when logging into user A's vehicle infotainment account.

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

[0571] Table 1

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

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

[0574] Figure 23 shows an example of a GUI provided in an embodiment of this application.

[0575] As shown in Figure 23(a), the GUI includes a prompt box 2301 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 2302, and a benefit-sharing control. When the system detects that the user clicks on the privacy-critical control 2302, the vehicle can install the social application and display the GUI shown in Figure 23(b) on the display screen 201.

[0576] As shown in Figure 23(b), the GUI is a display interface for selecting the screen to be deployed. The display interface includes a prompt box 2303, 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.

[0577] As shown in Figure 23(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 2304, the vehicle can deploy a privacy-critical social application on the central control screen and the second-row left-side entertainment screen.

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

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

[0580] Figure 24 shows an example of a GUI provided in an embodiment of this application.

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

[0582] As shown in Figure 24(b), in response to detecting that a user clicks on icon 2401, the vehicle can display a prompt box 2402 on the entertainment screen on the right side of the second row. The prompt box 2402 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.

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

[0584] In one embodiment, if no vehicle system account is logged in on the entertainment screen on the right side of the second row, the user can be prompted to log in to their social application account directly when the system detects that the user has clicked on icon 2401.

[0585] Figure 25 shows an example of a GUI provided in an embodiment of this application.

[0586] As shown in Figure 25(a), 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 2501 for a social app, the vehicle can display the GUI shown in Figure 25(b) on the display screen 201.

[0587] As shown in Figure 25(b), the GUI includes a prompt box 2502 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 2503. When the system detects that the user clicks on the benefit-sharing control 2503, the vehicle can install the video application 2 and display the GUI shown in Figure 25(c) on the display screen 201.

[0588] As shown in Figure 25(c), the GUI is a display interface for selecting the screen to be deployed. The display interface includes a prompt box 2504, 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.

[0589] As shown in Figure 25(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 2505, 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.

[0590] Figure 26 shows an example of a GUI provided in an embodiment of this application.

[0591] As shown in Figures 26(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 the central control screen and the second-row right-side entertainment screen. As can be seen from Figures 26(a) and (b), avatar 2601 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.

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

[0593] S2710, 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.

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

[0595] For example, as shown in Figure 21(e), when the system detects that a user clicks on the installation control 2105 corresponding to the social application, the vehicle can display a prompt box 2106 on the display screen 201. This prompt box 2106 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 2107, and a benefit-sharing control. When the system detects that a user clicks on the privacy-critical control 2107, the vehicle can install the social application.

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

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

[0598] Figures 21 and 25 above illustrate the process of allowing a user to select the installation type of an application by displaying a prompt box on a 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.

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

[0600] Table 2

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

[0602] Optionally, the method 2700 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.

[0603] For example, when the vehicle detects a user clicking the installation control 2105 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 can also confirm the control, change the installation type control, and cancel the control. When the vehicle detects a user clicking the confirmation control, it can request the installation package corresponding to the social application with the privacy-critical installation type from the server.

[0604] Optionally, before obtaining the first request, the method 2700 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.

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

[0606] Optionally, before obtaining the first request, the method 2700 further includes: obtaining the user's input of logging into the first vehicle system account in the vehicle system; wherein, the method 2700 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.

[0607] For example, suppose user A's vehicle infotainment account is logged into the central control screen shown in Figure 26(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 second row right can still remain logged in.

[0608] Optionally, the method 2700 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.

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

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

[0611] Optionally, suppose that user A's vehicle infotainment account is logged in on the central control screen shown in Figure 26(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.

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

[0613] Optionally, before obtaining the first request, the method 2700 further includes: obtaining the user's input when logging into the second vehicle system account in the vehicle system; wherein, the method 2700 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.

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

[0615] S2720, Install the first application according to the target installation type.

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

[0617] Optionally, the method 2700 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.

[0618] For example, as shown in Figure 22(c), when a user long-presses icon 2204 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.

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

[0620] Optionally, the method 2700 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.

[0621] For example, as shown in Figure 23(b), when a user clicks on the privacy-critical control 2302, the vehicle can install the social application and display a prompt box 2303 on the display screen 201. The prompt box 2303 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.

[0622] Figure 28 shows a schematic flowchart of an application deployment method 2800 provided in an embodiment of this application. The method 2800 can be executed by a server. The method 2800 includes:

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

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

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

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

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

[0628] S2830, based on the target installation type, send the installation package of the first application.

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

[0630] To facilitate understanding of the application deployment scheme provided in the embodiments of this application, the application scenarios and GUI involved in this application will be described in detail below with reference to Figures 29 to 37. The processing actions (such as control, response, deployment, etc.) or steps involved in Figures 29 to 37 can be executed by the computing platform 150 shown in Figure 1, or they can also be executed by the aforementioned system. For example, processing actions related to application deployment can be executed by the desktop launcher.

[0631] Figure 29 illustrates an example of a GUI provided in an embodiment of this application. As shown in Figure 29, 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 29(a), including a content display area 2910 and a function bar 2910'. Exemplarily, the content display area 2910 includes: icons for various applications, each application icon being used to enable an application; a login control 2911 (not logged in state) for logging into the vehicle system; and Bluetooth function icons, Wi-Fi function icons, and cellular network signal icons, respectively used to indicate the vehicle's Bluetooth on and / or connection status, Wi-Fi on status, and cellular network signal strength. The function bar 2910' includes a homepage icon, seat controls, air conditioning controls, and volume controls, respectively used to control the content display area 2910 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.

[0632] In some implementations, when a long press is detected on the video application icon, the display screen 201 can be controlled to display a control bar 3001 as shown in Figure 29(b). The control bar 3001 includes application details controls, application redeployment controls (i.e., "deploy to other screens"), and editing controls, which can be used to display application details, control the deployment of the application to other screens, and edit the application name, respectively.

[0633] For example, when the application redeployment control is detected to be clicked, the video application is deployed to other displays in the vehicle that do not have video applications deployed. For instance, if the vehicle includes displays 201 to 205, and displays 201, 202, and 203 all have video applications deployed, when the application redeployment control is detected to be clicked, the video application is deployed to displays 204 (i.e., the screen behind the passenger headrest) and displays 205.

[0634] Optionally, when the video application has been deployed on another display screen, the display screen 201 can be controlled to display the prompt bar 3002 shown in Figure 29(c), which includes the prompt message "The video application has been deployed to another screen".

[0635] Figure 29(d) and (e) show the content displayed on display screen 204 before and after the video application is redeployed, respectively. It can be seen that after the video application in display screen 201 is deployed to display screen 204, a video application icon 3003 is added to display screen 204.

[0636] It should be noted that the icons shown in Figure 8 are for illustrative purposes only. In actual implementation, the content display area 2910 and the function bar 2910' may display more or fewer icons. For example, when sliding the interface switching component 2911' in the content display area 2910, the content display area 2910 may switch to other interfaces to display icons for other applications. As another example, the content display area 2910 may display some or all of the Bluetooth, Wi-Fi, and cellular network signal icons, or may not display them, depending on the user's settings. Furthermore, the function bar 2910' may display other styles of icons based on the user's settings for seat ventilation and air conditioning status.

[0637] In some implementations, when the application redeployment control is clicked, the user can be prompted to select a display screen to be deployed. For this scenario, Figure 30 shows another set of GUIs provided in this embodiment. As shown in Figure 30(a), the display screen 201 displays a control bar 3004 associated with the navigation application. When the application redeployment control in the control bar 3004 is clicked, the display screen 201 can be controlled to display a control bar 3005 as shown in Figure 30(b). This control bar includes various types of controls, such as a control 3006 for unselectable displays, a control 3007 for selectable displays, a cancel control, a select all control, and a confirm control 3008. The unselectable displays can be displays where the navigation application has already been deployed, or displays where the navigation application cannot be deployed; the cancel control is used to cancel the selection of the already selected displays; the select all control is used to select all selectable displays; and the confirm control 3008 is used to confirm that the application will be deployed to the selected displays. For example, if the control corresponding to the right side of the second row of screens and the confirmation control 3008 are clicked in sequence, the navigation application is deployed on the display screen 204.

[0638] Optionally, when the navigation application has been deployed on the selected display screen, the display screen 201 can be controlled to display the prompt bar 3009 shown in (c) of Figure 30, which includes the prompt message "The navigation application has been deployed to the second row right screen".

[0639] Figure 30(d) and (e) show the content displayed on display screen 204 before and after the navigation application is redeployed. It can be seen that after the navigation application in display screen 201 is deployed to display screen 204, the navigation application icon 3010 is added to display screen 204.

[0640] It should be noted that Figures 29 and 30 are only used as examples of video and navigation applications. In actual implementation, video and navigation applications can be other applications as well. Furthermore, Figure 29 shows application redeployment when the vehicle infotainment system is not logged in, while Figure 30 shows application redeployment when the vehicle infotainment system is logged in with user A's system account (the avatar 2913 displayed by the login control is the image associated with user A's system account). In actual implementation, application redeployment can be performed only when the vehicle owner's system account or authorized system account is logged into the vehicle infotainment system, or only certain applications can support application redeployment when the vehicle infotainment system is not logged in.

[0641] It should also be noted that Figures 29 and 30 show the control of deploying applications already deployed on display screen 201 to other displays in response to user operations on the display screen. In actual implementation, applications already deployed on one display screen can also be deployed to other displays in response to user voice commands. For example, when the voice command "Please deploy the video application to the second row right screen" is detected, the video application is deployed to display screen 204. As another example, when the voice command "Please deploy the navigation application to the second row left screen" is detected, the video application is deployed to display screen 203.

[0642] In some implementations, when the application redeployment control is clicked, the application can be deployed to a display screen in an area of ​​the cockpit where a user is present. For this scenario, Figure 31 illustrates another GUI provided by an embodiment of this application. As shown in Figure 31(a), when the application redeployment control in the control bar 3004 is clicked and a user (e.g., user B) is detected in the second row right-hand area, the navigation application is deployed to the display screen 204 in the second row right-hand area. After deploying the application to the display screen 204, the display screen 201 can be controlled to display the interface shown in Figure 31(b). Furthermore, the content displayed on the display screen 204 before and after the navigation application redeployment is shown in Figures 31(c) and (d), respectively.

[0643] Referring to Figure 31, in some implementations, when there is a user (such as user B) in the right-hand area of ​​the second row and a navigation application has been deployed on the display screen 204, when the user clicks the application redeployment control in the control bar 3004, a control bar for selecting the display screen to deploy the navigation application can be displayed. This control bar can be similar to the control bar 3005 shown in Figure 30(b), except that the screen controls in the right-hand area of ​​the second row in this implementation are unselectable.

[0644] For example, the presence of a user in different areas of a vehicle can be determined based on signals collected by sensors within the vehicle. For instance, pressure sensors are installed under each seat; when the pressure value measured by a sensor under a particular seat is greater than or equal to a preset pressure threshold, it can be determined that a user is present at that seat. Alternatively, one or more cameras are installed in the cabin, and the presence of a user in different areas of the vehicle is determined based on images captured by these cameras. In practical implementation, other methods can also be used to determine whether a user is present in one or more areas of the vehicle.

[0645] In some implementations, certain installed applications do not support redeployment to other displays; for example, safety-critical applications do not support redeployment to other displays. Exemplarily, safety-critical applications may include, but are not limited to, applications capable of implementing functions that affect driving safety, such as APA, AVP, ACC, LCC, NCA, forward collision warning, lane departure warning, lane keeping assist, and rear collision avoidance warning. For this scenario, Figure 32 illustrates another set of GUIs provided in an embodiment of this application. As shown in Figure 32(a), the intelligent driving application deployed on display 201 can be considered an example of a safety-critical application. In one example, when a long press is detected on an intelligent driving application, the display 201 is controlled to display a control bar 3011, which includes application detail controls and edit controls, but does not include application redeployment controls. In another example, when a long press is detected on the intelligent driving application, the control display screen 201 displays a control bar including application detail controls, edit controls, and application redeployment controls; further, when a click is detected on the application redeployment control, the control display screen 201 displays the control bar 3012 shown in Figure 32(b). As shown in Figure 32(b), the controls included in this control bar 3012 are all controls corresponding to non-selectable displays, meaning that the user cannot deploy the intelligent driving application to other displays through the control bar 3012.

[0646] In some implementations, when deploying an application already installed on one display to other displays, the deployment is based on the application's type. The application type can be either a privacy-critical application or a rights-sharing application.

[0647] When an application is a privacy-critical application, deploying it to other displays can involve deploying the application's icon to each of the other displays and loading application data for each display. It's understood that when deploying a privacy-critical application to other displays, the application data loaded for each display is not necessarily all of the application's data. For example, a virtual environment can be created for each display, allowing different application accounts to log in to the same application through different displays within the same time period. This virtual environment is an independent environment for application operation; applications running in different virtual environments do not interfere with each other, ensuring that operation records and data from different applications do not interfere with each other. For instance, if the video application in Figure 29 is a privacy-critical application, the use and operation of the video application deployed on each display do not interfere with each other; the video application on different displays can be logged into by different application accounts and run independently.

[0648] When an application is a benefit-sharing application, deploying the application to other displays can be done by deploying the application's icon to each of those displays. For example, if the video application in Figure 29 is a benefit-sharing application, then when an application account logs into the video application through one display, the video applications on other displays will also be logged into by that application account. Video applications deployed on different displays can play different videos independently, but all video applications on different displays share the same data and permissions.

[0649] In some implementations, when an application is already deployed on one or more displays, the user can change the application type via the application icon displayed on the display. For this scenario, Figure 33 illustrates another set of GUIs provided by an embodiment of this application. As shown in Figure 33(a), when the "Change Application Type" control in the control bar 3004' is clicked, the control display 201 displays a prompt bar 3013 as shown in Figure 33(b). This prompt bar 3013 includes the prompt message "Current application type is type 1, change to type 2?", and controls "Yes", "No", and an exit control 3014. When the "No" control or the exit control 3014 is clicked, the prompt bar 3013 is closed, and the application type change is terminated. When the "Yes" control is clicked, the navigation application is changed from type 1 to type 2. More specifically, changing the navigation application from type 1 to type 2 can be achieved by uninstalling the type 1 navigation application already deployed on each display and deploying the type 2 navigation application on the display where the original navigation application was deployed.

[0650] Optionally, after the application type is changed, the display screen 201 can be controlled to display the prompt bar 3015 shown in Figure 33(c), which includes the prompt message "Navigation application type has been changed to type 2". For example, the aforementioned type 1 can be privacy-critical and type 2 can be benefit-sharing, or type 1 can be benefit-sharing and type 2 can be privacy-critical.

[0651] The above, in conjunction with Figures 29 to 33, illustrates the specific implementation of application redeployment based on operations performed on the icons of already deployed applications. It should be noted that, in actual implementation, the specific controls, content, and forms in the control bars 3001, 3004, 3005, and prompt bar 3013 shown in Figures 29 to 33 may differ from those shown in the figures, and the methods used to trigger the display of control bars 3001, 3004, 3005, and prompt bar 3013 may also differ from those described in the aforementioned embodiments.

[0652] After controlling the redeployment of an application or changing the type of an application through the desktop launcher, relevant information can be sent to the app store to update the application's deployment information and type. The app store is a platform for installing, updating, managing, and uninstalling applications. One or more displays in the vehicle can be deployed with the app store application for user access and / or use. In practice, the app store application may be deployed only on the central control screen.

[0653] In addition to redeploying applications based on operations performed on the icons of already deployed applications, application redeployment can also be controlled through an application store. For this scenario, Figure 34 illustrates another set of GUIs provided in this embodiment. As shown in Figure 34(a), the display screen 201 displays icons for instant messaging applications and application store applications. When a click is detected on the icon of an application store application, the display screen 201 is controlled to display the details page of the application store, specifically interface 3020 as shown in Figure 34(b). This interface 3020 currently displays the management interface for installed applications. Optionally, in response to clicks on the office control, category control, and settings control on the left side of interface 3020, different content can be displayed on the right side of interface 3020. More specifically, the right side of the current interface 3020 displays information about the installed applications, such as the application name (e.g., "Browser"), application type (e.g., "Type 1"), and deployment display (e.g., "Deployed on the main screen"). Furthermore, for each application, interface 3020 also provides a redeployment control 3021 and a change-type control 3022.

[0654] In some implementations, when a click is detected on the redeployment control 3021 corresponding to an application, the application can be deployed to other displays using the deployment methods described in the corresponding parts of Figures 29 to 31. For example, taking a navigation application as an example, when a click is detected on the redeployment control of the navigation application, the navigation application can be deployed to all other displays where no navigation application is deployed; alternatively, the navigation application can be deployed to other displays in areas where users are present; or, a control bar (such as control bar 3005) can be displayed for selecting the display to which the navigation application is to be deployed, and then the navigation application can be deployed to the selected display based on the display of the navigation application selected by the user.

[0655] In some implementations, when the redeployment control 3021 corresponding to a certain application (hereinafter, a video application will be used as an example) is clicked, the display screen 201 can be controlled to display the interface shown in Figure 35. The right side of this interface includes a control bar 3023 for selecting the display screen to which the navigation application is to be deployed. The control bar 3023 includes multiple screen selection controls, a cancel control, a select all control, and a confirm control. Each of the multiple screen selection controls is used to control the deployment of the application to a display screen. The multiple screen selection controls can correspond to all the display screens in the vehicle that can deploy video applications. The functions of the cancel control, select all control, and confirm control can be referred to the description in the previous embodiments, and will not be repeated here. For example, regardless of which display screens the video application was previously deployed on, when the screen selection controls corresponding to the driver's screen, passenger's screen, and second-row right-side screen are clicked, and the confirm control is clicked, the video application is deployed to display screen 201 (i.e., the driver's screen), display screen 202 (i.e., the passenger's screen), and display screen 204 (i.e., the second-row right-side screen).

[0656] It should be noted that during the aforementioned process of redeploying the application based on the operation of the icon of the deployed application, when the application redeployment control is detected to be clicked, the control bar 3023 shown in Figure 35 can also be displayed, thereby responding to the user's operation of clicking one or more screen selection controls to redeploy the application to one or more displays.

[0657] In some implementations, when the type change control 3022 corresponding to a certain application (hereinafter, a video application will be used as an example) is clicked, the display screen 201 can be controlled to display the interface shown in Figure 36(a). This interface includes a prompt bar 3025, which includes the prompt message "Current application type is type 2, change to type 1?", and controls "Yes" and "No". When the control "No" is clicked, the prompt bar 3025 is closed, and the application type change is terminated. When the control "Yes" is clicked, the video application is changed from type to type 1. More specific change methods can be found in the description of the corresponding part of Figure 33, which will not be repeated here. In some implementations, when the control "Yes" is clicked, the display screen 201 can also be controlled to display the interface shown in Figure 36(b). This interface includes a prompt bar 3026, which includes the prompt message "Change the screen where the application is deployed?", and controls "Yes" and "No". When the "No" control is clicked, the application type is changed according to the corresponding part of Figure 33. When the "Yes" control is clicked, the display screen 201 can be controlled to display the interface shown in Figure 35, and then the application can be redeployed according to the method of changing the application deployment screen described in the corresponding part of Figure 35.

[0658] The above, in conjunction with Figures 34 to 36, illustrates the specific implementation of application redeployment through the application store. It should be noted that in actual implementation, the specific interface corresponding to the application store application, and the controls involved in Figures 34 to 36, may differ from those shown in the figures, and the method of triggering the display of each control may also differ from the method described in the aforementioned embodiments.

[0659] In actual implementation, which system accounts can redeploy applications and which system accounts can change application types can be set by the user through the vehicle owner's system account. For example, Figure 37 shows a set of GUIs for setting application deployment permissions. Taking user A's system account as the vehicle owner's system account as an example, when the vehicle owner's system account is logged in, the login control displays avatar 2913. Further, as shown in Figure 37(a), when the login control is detected to be clicked, the control display screen 201 displays the details page of the vehicle system as shown in Figure 37(b). This details page includes the name 3031 of the vehicle owner's system account, the mobile phone number associated with the vehicle owner's system account 3032, and an expansion control 3033. This expansion control 3033 is used to open the settings page to set information such as name and avatar. In addition, this details page may also include a vehicle information card, which includes the vehicle name 3034, vehicle license plate number, and other related information 3035, as well as a vehicle authorization control 3036.

[0660] When the vehicle authorization control 3036 is clicked, the control display screen 201 displays the vehicle authorization details interface as shown in Figure 37(c). This interface includes cards 3037 and 3038. Card 3037 includes basic vehicle information (such as name, license plate number, etc.) and a new authorization control 3039, which is used to authorize unauthorized accounts. Card 3038 includes authorized account information. For example, authorized system accounts include account 1 and account 2, where account 1 has key and control permissions, application management permissions, and vehicle owner service permissions, and account 2 has key and control permissions and vehicle owner service permissions. Card 3038 also includes an expansion control (such as control 3040) for each account.

[0661] When a click is detected on control 3040, the display screen 201 can be controlled to display the authorization information editing interface corresponding to account 1, as shown in Figure 37(d). This interface includes a modify authorization control 3041, a delete authorization control 3042, and an authorization information card 3043 associated with application management. Specifically, the modify authorization control 3041 is used to modify the authorization content for account 1, the delete authorization control 3042 is used to revoke the authorization for account 1, and the authorization informatio...

Claims

1. A data sharing method, characterized in that, include: Obtain information about a first user account, which is one of multiple user accounts. The multiple user accounts are associated with a first data storage area. Each user account under the multiple user accounts is also associated with a sub-data storage area. The sub-data storage area associated with the first user account is a second data storage area. The first data storage area and the second data storage area belong to the first user space. In response to receiving a request to share the first data under the first user account, the first data is stored in the first data storage area.

2. The method according to claim 1, characterized in that, Before storing the first data in the first data storage area, the method further includes: In response to input that stores the first data under the first user account, the first data is stored in the second data storage area; Wherein, storing the first data through the first data storage area includes: In response to the request to receive the sharing request, control the first data to switch from being stored in the second data storage area to being stored in the first data storage area.

3. The method according to claim 1 or 2, characterized in that, The plurality of user accounts also includes a second user account, and the method further includes: Obtain the second access request of the first application of the second user account; When the second access request is used to request the reading of the first data, the first data is read.

4. The method according to any one of claims 1 to 3, characterized in that, The method further includes: Obtain the third access request of the second application under the first user account; When the third access request is used to request the reading of the second data, the second data is read. The second data is data shared in the first data storage area through a third user account, and the plurality of user accounts includes the third user account.

5. The method according to any one of claims 1 to 4, characterized in that, The method further includes: Obtain the fourth access request of the third application under the fourth user account, wherein the plurality of user accounts does not include the fourth user account; When the fourth access request is made to request to read the first data, the fourth access request is rejected.

6. The method according to any one of claims 1 to 5, characterized in that, The method further includes: In response to the input of a fifth user account among the plurality of user accounts, an association is established between the fifth user account and the first data storage area.

7. The method according to any one of claims 1 to 6, characterized in that, The multiple user accounts are user accounts under the same family group, or, among the multiple user accounts, the accounts other than the first user account are accounts authorized by the first user account.

8. A data access method, characterized in that, include: Control one or more displays in the vehicle cabin to display information of a first user space, the first user space including a first set of applications; Obtain the user's first input, which indicates switching to a preset mode; In response to the first input, control the one or more displays to switch from displaying the first user space to displaying the second user space, the second user space including the second set of applications.

9. The method according to claim 8, characterized in that, The preset mode is either a car rental mode or a car borrowing mode.

10. The method according to claim 8 or 9, characterized in that, The first user space includes information about each user account among multiple user accounts, and each user account is associated with a sub-data storage area.

11. The method according to any one of claims 8 to 10, characterized in that, The method further includes: Obtain the user's input when logging into the first user account in the second user space; In response to a storage request for obtaining first data under the first user account, the storage request is used to request the storage of the first data; According to the storage request, an association is established between the first user account and the first data storage area, and the first data is stored through the first data storage area, which belongs to the second user space.

12. The method according to any one of claims 8 to 11, characterized in that, The method further includes: In response to a second user input, the second user space is deleted, whereby the second input indicates exiting the preset mode; or... In response to the second input, delete the user account information under the second user space; or, In response to the second input, delete the data in the data storage area associated with each user account in the multiple user accounts under the second user space.

13. The method according to claim 12, characterized in that, The step of deleting the user account information in the second user space in response to the user's second input includes: When the second input indicates the taxi return mode, in response to the second input, delete the second user space, or delete the user account information under the second user space.

14. The method according to claim 12, characterized in that, In response to the second input, deleting data from the data storage area associated with each user account in the multiple user accounts under the second user space includes: When the second input indicates exiting the car rental mode, in response to the second input, the data in the data storage area associated with each user account in the multiple user accounts under the second user space is deleted.

15. The method according to claim 13, characterized in that, The method further includes: In response to the second input, a third group of applications is uninstalled, which are applications installed by the user in the second user space other than the second group of applications.

16. An account login method, characterized in that, include: In response to an event that a first user account logs in on the first display screen of the vehicle, based on the association between the first user account and the application, a first group of applications associated with the first user account is logged in on the first display screen and a second group of applications associated with the first user account is logged in on multiple displays other than the first display screen. The first group of applications includes privacy-critical applications and / or benefit-sharing applications, and the second group of applications includes benefit-sharing applications. In response to an event of a second user account logging in on a second display screen of the vehicle, a third set of applications associated with the second user account is logged in on the second display screen based on the association between the second user account and applications. The third set of applications includes privacy-critical applications. The plurality of displays includes the second display screen.

17. The method according to claim 16, characterized in that, The second set of applications includes the first application, and the first application is deployed on the second display screen. The method includes: When the account associated with the first application of the first user account is a non-member account and the account associated with the first application of the second user account is a member account, the account of the first application deployed on the multiple displays is switched to the account of the first application associated with the second user account.

18. The method according to claim 16, characterized in that, The second set of applications includes a second application, and the second application is deployed on the second display screen. The method includes: When the account associated with the first application account in the second application is a member account and the account associated with the second user account in the second application is a non-member account, maintain the account of the second application deployed on the plurality of displays; or, When the account of the second application associated with the first application account is a member account and the account of the second application associated with the second user account is a member account, the account of the second application deployed on the multiple displays is maintained.

19. The method according to any one of claims 16 to 18, characterized in that, The first group of applications includes a third application as a shared benefit application, or the second group of applications includes a third application. The method further includes: When the third application is not deployed on the second display screen, in response to the user's input to deploy the third application on the second display screen, the icon of the third application is deployed on the second display screen and the account of the third application associated with the first user account is logged in on the second display screen.

20. The method according to any one of claims 16 to 19, characterized in that, The first group of applications, the second group of applications, and the third group of applications do not include a fourth application, which is a share-sharing application. The method further includes: In response to the user's input to deploy the fourth application on the second display screen, the fourth application is installed on the second display screen and the account of the fourth application associated with the second user account is logged in on the second display screen.

21. The method according to any one of claims 16 to 20, characterized in that, The third group of applications does not include the fifth application, which is a privacy-critical application. The method further includes: When the fifth application is deployed on any of the multiple displays other than the second display, in response to the user's... The input method described above involves deploying the fifth application on the second display screen, installing a clone application corresponding to the fifth application on the second display screen, and logging into the account associated with the fifth application on the second user account on the second display screen; or, When the fifth application is not deployed on any of the multiple displays other than the second display, in response to the user's input to deploy the fifth application on the second display, the main application corresponding to the fifth application is installed on the second display, and the account associated with the fifth application of the second user account is logged in on the second display.

22. A data sharing device, characterized in that, include: The acquisition unit is used to acquire information about a first user account, which is one of a plurality of user accounts. The plurality of user accounts are associated with a first data storage area. Each user account under the plurality of user accounts is also associated with a sub-data storage area. The sub-data storage area associated with the first user account is a second data storage area. The first data storage area and the second data storage area belong to a first user space. The data storage unit is used to store the first data in the first data storage area in response to a request to share the first data under the first user account.

23. The apparatus according to claim 22, characterized in that, The data storage unit is configured to store the first data in the second data storage area in response to inputting the first data storage under the first user account before storing the first data in the first data storage area; In response to the request to receive the sharing request, control the first data to switch from being stored in the second data storage area to being stored in the first data storage area.

24. The apparatus according to claim 22 or 23, characterized in that, The plurality of user accounts also includes a second user account, and the device further includes a data reading unit. The acquisition unit is further configured to acquire a second access request from the first application of the second user account; The data reading unit is used to read the first data according to the second access request when the second access request is used to request the reading of the first data.

25. The apparatus according to any one of claims 22 to 24, characterized in that, The device also includes a data reading unit. The acquisition unit is also used to acquire a third access request of the second application under the first user account; The data reading unit is further configured to read the second data when the third access request requests to read the second data, wherein the second data is data shared in the first data storage area through a third user account, and the plurality of user accounts includes the third user account.

26. The apparatus according to any one of claims 22 to 25, characterized in that, The device also includes a data reading unit. The acquisition unit is further configured to acquire a fourth access request from a third application under the fourth user account, wherein the plurality of user accounts does not include the fourth user account; The data reading unit is further configured to reject the fourth access request when the fourth access request is used to request the reading of the first data.

27. The apparatus according to any one of claims 22 to 26, characterized in that, The data storage unit is further configured to establish an association between the fifth user account and the first data storage area in response to inputting a fifth user account among the plurality of user accounts.

28. The apparatus according to any one of claims 22 to 27, characterized in that, The multiple user accounts are user accounts under the same family group, or, among the multiple user accounts, the accounts other than the first user account are accounts authorized by the first user account.

29. A device for switching user spaces, characterized in that, include: A control unit is used to control one or more displays in the vehicle cabin to display information of a first user space, the first user space including a first set of applications; The acquisition unit is used to acquire the user's first input, which indicates switching to a preset mode. The control unit is further configured to, in response to the first input, control one or more displays to switch from displaying the first user space to displaying a second user space, the second user space including a second set of applications.

30. The apparatus according to claim 29, characterized in that, The preset mode is either a car rental mode or a car borrowing mode.

31. The apparatus according to claim 29 or 30, characterized in that, The first user space includes information about each user account among multiple user accounts, and each user account is associated with a sub-data storage area.

32. The apparatus according to any one of claims 29 to 31, characterized in that, The device also includes a data storage unit. The acquisition unit is also used to acquire the user's input when logging into the first user account in the second user space; The data storage unit is further configured to respond to a request to obtain storage of first data under the first user account, the storage request being used to request storage of the first data; The data storage unit is further configured to establish an association between the first user account and the first data storage area according to the storage request, and to store the first data through the first data storage area, wherein the first data storage area belongs to the second user space.

33. The apparatus according to any one of claims 29 to 32, characterized in that, The device also includes a data deletion unit. The data deletion unit is used to delete the second user space in response to a second input from the user, wherein the second input indicates exiting the preset mode; Alternatively, in response to the second input, delete the user account information under the second user space; Alternatively, in response to the second input, delete the data in the data storage area associated with each user account in the multiple user accounts under the second user space.

34. The apparatus according to claim 33, characterized in that, The data deletion unit is specifically used for: When the second input indicates the taxi return mode, in response to the second input, delete the second user space, or delete the user account information under the second user space.

35. The apparatus according to claim 33, characterized in that, The data deletion unit is specifically used for: When the second input indicates exiting the car rental mode, in response to the second input, the data in the data storage area associated with each user account in the multiple user accounts under the second user space is deleted.

36. The apparatus according to claim 34, characterized in that, The device also includes an application unloading unit. The application uninstallation unit is used to uninstall a third group of applications in response to the second input. The third group of applications consists of applications installed by the user in the second user space other than the second group of applications.

37. An account login device, characterized in that, include: The acquisition unit is used to acquire the event of the first user account logging in on the first display screen of the vehicle; An application account login unit is configured to respond to an event in which the first user account logs in on the first display screen, and based on the association between the first user account and the application, log in to a first group of applications associated with the first user account on the first display screen and log in to a second group of applications associated with the first user account on other displays besides the first display screen among multiple displays. The first group of applications includes privacy-critical applications and / or benefit-sharing applications, and the second group of applications includes benefit-sharing applications. The application account login unit is further configured to respond to an event in which a second user account logs in on the second display screen of the vehicle, and, based on the association between the second user account and the application, log in on the second display screen a third group of applications associated with the second user account, the third group of applications including privacy-critical applications, and the plurality of display screens including the second display screen.

38. The apparatus according to claim 37, characterized in that, The second set of applications includes the first application, and the first application is deployed on the second display screen. The application account login unit is further configured to switch the account of the first application deployed on the plurality of displays to the account of the first application associated with the second user account when the account of the first application associated with the first user account is a non-member account and the account of the first application associated with the second user account is a member account.

39. The apparatus according to claim 37, characterized in that, The second set of applications includes a second application, which is deployed on the second display screen. The application account login unit is further configured to maintain the account of the second application deployed on the plurality of displays when the account of the second application associated with the first application account is a member account and the account of the second application associated with the second user account is a non-member account; or, When the account of the second application associated with the first application account is a member account and the account of the second application associated with the second user account is a member account, the account of the second application deployed on the multiple displays is maintained.

40. The apparatus according to any one of claims 37 to 39, characterized in that, The first group of applications includes a third application, or the second group of applications includes a third application. The application account login unit is further configured to, when the third application is not deployed on the second display screen, respond to the user's input to deploy the third application on the second display screen, deploy the icon of the third application on the second display screen and log in to the account of the third application associated with the first user account on the second display screen.

41. The apparatus according to any one of claims 37 to 40, characterized in that, The first group of applications, the second group of applications, and the third group of applications do not include the fourth application, which is a rights-sharing application. The application account login unit is further configured to, in response to a user's input to deploy the fourth application on the second display screen, install the fourth application on the second display screen and log in to the account of the fourth application associated with the second user account on the second display screen. Number.

42. The apparatus according to any one of claims 37 to 41, characterized in that, The third group of applications does not include the fifth application, which is a privacy-critical application. The application account login unit is further configured to, when the fifth application is deployed on other displays besides the second display among the plurality of displays, in response to user input regarding deploying the fifth application on the second display, install a clone application corresponding to the fifth application on the second display and log in to the account of the fifth application associated with the second user account on the second display; or, When the fifth application is not deployed on any of the multiple displays other than the second display, in response to the user's input to deploy the fifth application on the second display, the main application corresponding to the fifth application is installed on the second display, and the account associated with the fifth application of the second user account is logged in on the second display.

43. A data processing apparatus, characterized in that, include: A processor for executing a computer program stored in memory to cause the apparatus to perform the method as described in any one of claims 1 to 21.

44. The apparatus according to claim 43, characterized in that, The device also includes the memory.

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

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

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

48. A vehicle, characterized in that, Includes the apparatus as described in any one of claims 22 to 44, or the computer-readable storage medium as described in claim 45, or the chip as described in claim 46, or the vehicle is equipped with the computer program product as described in claim 47.

Images