Interface display method and device, vehicle and storage medium

Abstract

The invention provides an interface display method and device, a vehicle and a storage medium, the method is applied to the technical field of vehicles, and the method comprises the following steps: in response to an opening instruction of a target media service, determining a target interface container corresponding to the target media service from an interface container management pool; determining a target data warehouse corresponding to the target media service from a data warehouse management pool, wherein the target data warehouse is configured to obtain content data of the target media service; and displaying a user interface corresponding to the target media service according to the target interface container and the content data of the target media service in the target data warehouse. Based on the scheme of the invention, multiple media services can be connected and maintained at the same time on the basis of dual isolation of an interface container level and a data bin level, and the user experience is effectively improved.

Description

Technical Field

[0001] The present application relates to the field of vehicle technology, and more specifically, to an interface display method, device, vehicle and storage medium in the field of vehicle technology. Background Art

[0002] Some vehicles are equipped with in-vehicle media applications, which usually support multiple media services. The media services may provide music, videos, audiobooks, podcasts, online radio stations, live streaming and other content. In related technologies, in-vehicle media applications generally do not support simultaneous connection to multiple media services. When users switch between different media services or start new media services through operations, the user interface of the original media service will be lost or the data status will be lost, affecting the user experience. Summary of the invention

[0003] The present application provides an interface display method, device, vehicle and storage medium. The method can achieve simultaneous connection and maintenance of multiple media services on the basis of dual isolation at the interface container level and the data warehouse level, thereby effectively improving the user experience.

[0004] In a first aspect, a method for displaying an interface is provided, the method comprising:

[0005] In response to an opening instruction of the target media service, determining a target interface container corresponding to the target media service from an interface container management pool;

[0006] Determine a target data store corresponding to the target media service from the data store management pool, where the target data store is configured to obtain content data of the target media service;

[0007] The user interface corresponding to the target media service is displayed according to the target interface container and the content data of the target media service in the target data bin.

[0008] Through the above solution, on the basis of double isolation at the interface container level and the data warehouse level, it is possible to simultaneously connect and maintain multiple media services. Even if the user switches different media services or starts a new media service through operations, the user interface or data status of the original media service will not be lost, which effectively improves the user experience.

[0009] In combination with the first aspect, in some possible implementations, determining a target interface container corresponding to a target media service from an interface container management pool includes: if a first interface container allocated to the target media service exists among multiple interface containers managed by the interface container management pool, determining the first interface container as the target interface container corresponding to the target media service; if the first interface container allocated to the target media service does not exist among the multiple interface containers managed by the interface container management pool, allocating a target interface container to the target media service in the interface container management pool.

[0010] Through the above scheme, when there is a first interface container assigned to the target media service in the interface container management pool, it is directly determined as the target interface container. When there is no first interface container assigned to the target media service in the interface container management pool, a new target interface container can be dynamically created or assigned to the target media service in the interface container management pool. In this way, it is possible to quickly respond to user needs and ensure that each media service has a corresponding interface container to carry and display its user interface, thereby realizing flexible expansion and management of interface containers.

[0011] In combination with the first aspect and the above-mentioned implementation methods, in some possible implementation methods, a target interface container is allocated to a target media service in an interface container management pool, including: if the total number of interface containers in the interface container management pool reaches a preset first upper limit, a second interface container is determined from multiple interface containers managed by the interface container management pool, and the second interface container is allocated as the target interface container corresponding to the target media service, the second interface container being any interface container among the multiple interface containers; if the total number of interface containers in the interface container management pool does not reach the preset first upper limit, a third interface container is created in the interface container management pool, and the third interface container is allocated as the target interface container corresponding to the target media service.

[0012] Through the above scheme, the preset first upper limit is introduced to refine the allocation strategy of the interface container, which not only ensures the stable operation of the interface container management pool under limited resources, but also realizes efficient resource configuration and optimization of user experience by dynamically adjusting the allocation method of the interface container.

[0013] In combination with the first aspect and the above-mentioned implementation methods, in some possible implementation methods, determining a second interface container from multiple interface containers managed by an interface container management pool includes: determining an interface container to be reset from multiple interface containers managed by the interface container management pool based on a preset least recently used algorithm; and resetting the interface container to be reset to obtain a second interface container.

[0014] Through the above solution, by introducing the LRU algorithm, even when the total number of interface containers in the interface container management pool reaches the preset first upper limit, the existing resources can be effectively used to meet the needs of the target media service while maintaining the continuity of the user experience.

[0015] In combination with the first aspect and the above-mentioned implementation methods, in some possible implementation methods, determining the target data warehouse corresponding to the target media service from the data warehouse management pool includes: if there is a first data warehouse assigned to the target media service among the multiple data warehouses managed by the data warehouse management pool, determining the first data warehouse as the target data warehouse corresponding to the target media service; if there is no first data warehouse assigned to the target media service among the multiple data warehouses managed by the data warehouse management pool, assigning the target data warehouse to the target media service in the data warehouse management pool.

[0016] Through the above scheme, when the first data warehouse corresponding to the target media service exists in the data warehouse management pool, it is directly determined as the target data warehouse, which not only reduces the data loading time, but also ensures the consistency and continuity of the data. When the first data warehouse does not exist in the data warehouse management pool, a new target data warehouse can be flexibly created or allocated in the data warehouse management pool, ensuring that the target media service has exclusive data storage space and meeting the data storage needs of the target media service. In this way, unnecessary waste of resources is avoided and the flexibility and scalability of data management are guaranteed.

[0017] In combination with the first aspect and the above-mentioned implementation methods, in some possible implementation methods, a target data warehouse is allocated to a target media service in a data warehouse management pool, including: if the total number of data warehouses in the data warehouse management pool reaches a preset second upper limit, a second data warehouse is determined from multiple data warehouses managed by the data warehouse management pool, and the second data warehouse is allocated as the target data warehouse corresponding to the target media service, the second data warehouse being any data warehouse among the multiple data warehouses; if the total number of data warehouses in the data warehouse management pool does not reach the preset second upper limit, a third data warehouse is created in the data warehouse management pool, and the third data warehouse is allocated as the target data warehouse corresponding to the target media service.

[0018] Through the above scheme, the preset second upper limit is introduced to refine the data warehouse allocation strategy, which not only ensures the stable operation of the data warehouse management pool under limited resources, but also realizes efficient resource configuration and optimization of user experience by dynamically adjusting the data warehouse allocation method.

[0019] In combination with the first aspect and the above-mentioned implementation methods, in some possible implementation methods, determining a second data warehouse among multiple data warehouses managed by a data warehouse management pool includes: determining a data warehouse to be reset among multiple data warehouses managed by the data warehouse management pool based on a preset least recently used algorithm; resetting the data warehouse to be reset to obtain a second data warehouse.

[0020] Through the above solution, by introducing the LRU algorithm, even when the total number of data bins in the data bin management pool reaches the preset second upper limit, the existing resources can be effectively used to meet the needs of the target media service while maintaining the continuity of the user experience.

[0021] In combination with the first aspect and the above-mentioned implementation methods, in some possible implementation methods, the opening instruction of the target media service is a start instruction of the target media service; in response to the opening instruction of the target media service, the target interface container corresponding to the target media service is determined from the interface container management pool, including: in response to the start instruction of the target media service, connecting to the target media service through a preset media session component; when connected to the target media service, determining the target interface container corresponding to the target media service from the interface container management pool.

[0022] In this embodiment, in response to the start instruction, a connection can be established with the target media service through the media session component. This process not only simplifies the start-up process of the media service, but also improves the response speed and connection stability.

[0023] In a second aspect, an interface display device is provided, the device comprising:

[0024] A first determining unit, configured to determine a target interface container corresponding to the target media service from an interface container management pool in response to an opening instruction of the target media service;

[0025] A second determining unit, configured to determine a target data store corresponding to a target media service from a data store management pool, wherein the target data store is configured to obtain content data of the target media service;

[0026] The display unit is used to display a user interface corresponding to the target media service according to the target interface container and the content data of the target media service in the target data bin.

[0027] In a third aspect, a vehicle is provided, wherein the vehicle comprises:

[0028] A memory for storing executable program codes;

[0029] A processor is used to call and run the executable program code from the memory so that the vehicle executes the method in the above-mentioned first aspect or any possible implementation of the first aspect.

[0030] In a fourth aspect, a computer program product is provided, comprising: a computer program code, which, when executed on a computer, enables the computer to execute the method in the first aspect or any possible implementation of the first aspect.

[0031] In a fifth aspect, a computer-readable storage medium is provided, which stores a computer program code. When the computer program code runs on a computer, the computer executes the method in the above-mentioned first aspect or any possible implementation manner of the first aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] Figure 1 It is a schematic diagram of a scene displayed on an interface provided in an embodiment of the present application;

[0033] Figure 2 It is a schematic diagram of a scene displayed on an interface provided in an embodiment of the present application;

[0034] Figure 3 It is a flowchart of an interface display method provided in an embodiment of the present application;

[0035] Figure 4 This is an example schematic diagram of an interface container management pool provided in an embodiment of the present application;

[0036] Figure 5 This is an example schematic diagram of a data warehouse management pool provided in an embodiment of the present application;

[0037] Figure 6 is an example schematic diagram of the relationship between an interface container and a data bin provided in an embodiment of the present application;

[0038] Figure 7 It is a schematic diagram of a process for determining a target interface container provided by an embodiment of the present application;

[0039] Figure 8 It is a schematic diagram of a process for determining a target interface container provided by an embodiment of the present application;

[0040] Fig. 9 This is an example schematic diagram of resetting an interface container provided in an embodiment of the present application;

[0041] Fig.10 It is a schematic diagram of a process for determining a target data warehouse provided in an embodiment of the present application;

[0042] Fig.11 It is a schematic diagram of a process for determining a target data warehouse provided in an embodiment of the present application;

[0043] Fig.12 This is an example schematic diagram of a data bin reset provided in an embodiment of the present application;

[0044] Fig.13 It is a schematic diagram of a process of connecting to a target media service through a media session component provided by an embodiment of the present application;

[0045] Fig.14 It is a comprehensive flow diagram of an interface display provided in an embodiment of the present application;

[0046] Fig.15 is a structural schematic diagram of an interface display device provided in an embodiment of the present application;

[0047] Fig.16 It is a structural schematic diagram of a vehicle provided in an embodiment of the present application. DETAILED DESCRIPTION

[0048] The technical solution in the present application will be described clearly and in detail below in conjunction with the accompanying drawings. In the description of the embodiments of the present application, unless otherwise specified, " / " means or, for example, A / B can mean A or B: "and / or" in the text is only a description of the association relationship of associated objects, indicating that there can be three relationships, for example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, in the description of the embodiments of the present application, "multiple" means two or more than two.

[0049] In the following, the terms "first" and "second" are used for descriptive purposes only and are not to be understood as suggesting or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of the features.

[0050] See also Figure 1 and Figure 2 , Figure 1 and Figure 2 All of them are schematic diagrams of scenes displayed on an interface provided in an embodiment of the present application. Figure 1 As shown, some vehicles have been equipped with highly integrated in-vehicle media applications, which usually support multiple media services (such as Figure 1 The media services 1 to n are shown, and the media services may provide music, videos, audio books, podcasts, online radio stations, live streaming and other content. The media services can also connect to remote servers in certain situations to obtain and present rich online content data in real time.

[0051] However, in-vehicle media applications generally do not support simultaneous connection to multiple media services. When users switch between different media services or start new media services, the user interface or data status of the original media service will be lost. Figure 2For example, the user interface that was originally displayed is the playback interface of media service 1. During the existence of the playback interface of media service 1, the user starts or switches to media service 2 through relevant operations, and the playback interface of media service 1 is replaced and displayed as the main interface of media service 2. During the existence of the main interface of media service 2, the user starts or switches to media service 1 through relevant operations, and the main interface of media service 2 is replaced and displayed as the main interface of media service 1. It can be seen that since it is impossible to connect and maintain media service 1 and media service 2 at the same time, the main interface of media service 2 cannot switch to the playback interface of media service 1 that was originally displayed. Similarly, the playback progress corresponding to the playback interface of media service 1 will also be lost.

[0052] In the related art, in-vehicle media applications such as Google's native CarMediaApp cannot connect to multiple media services at the same time. Specifically, CarMediaApp realizes communication and interaction with media services through its built-in MediaSession component (one of the media session components). The MediaSession component allows CarMediaApp to establish connections with media services provided by mainstream content providers such as Spotify and TuneIn, so as to obtain and play the content data required by users. But the problem is that CarMediaApp only supports establishing an active session with one media service through the MediaSession component at the same time. This means that when a user decides to switch from the currently playing Spotify music service to TuneIn's online radio station, CarMediaApp must first disconnect from Spotify before establishing a new connection with TuneIn. In this process, the original user interface related to Spotify will be closed or replaced, and all the user's data status such as playback progress, personalized settings, search history, etc. in the service will be lost. The above limitations are mainly due to the design logic of the MediaSession component. In the architecture of CarMediaApp, the MediaSession component is designed as a single session manager, which cannot maintain the session status of multiple media services at the same time. When the user switches media services, the MediaSession component needs to clean up the context information of the current session to make room for the new session.

[0053] Based on the above introduction, if the in-vehicle media application does not support simultaneous connection to multiple media services, then when the user switches different media services or starts a new media service through operations, the user interface of the original media service will be lost or the data status will be lost, affecting the user experience.

[0054] In response to the above problems, the main solutions provided by the embodiments of the present application include: in response to the opening instruction of the target media service, the target interface container corresponding to the target media service can be determined from the interface container management pool, thereby realizing isolation at the interface container level; the target data warehouse corresponding to the target media service can be determined from the data warehouse management pool, thereby realizing isolation at the data warehouse level; finally, the user interface corresponding to the target media service can be displayed according to the content data of the target interface container and the target data warehouse. In this way, on the basis of the dual isolation at the interface container level and the data warehouse level, it is possible to simultaneously connect and maintain multiple media services, and even if the user switches different media services or starts a new media service through operation, the user interface of the original media service will not be lost or the data status will not be lost, thereby effectively improving the user experience.

[0055] based on Figure 1 - Figure 2 The scene shown is shown below. Figure 3 - Fig.14 , the interface display method provided in the embodiment of the present application is introduced in detail.

[0056] See also Figure 3 , Figure 3 The following is a flow chart of an interface display method provided in an embodiment of the present application. Figure 3 As shown, the method of the embodiment of the present application may include the following steps S101-S103.

[0057] S101 , in response to an opening instruction of a target media service, determining a target interface container corresponding to the target media service from an interface container management pool.

[0058] Specifically, the opening instruction of the target media service involved in this embodiment can be a switching instruction of the target media service, or a starting instruction of the target media service. Among them, the switching instruction refers to an instruction for the user to switch from the media service currently being used to another media service, such as switching from Spotify to TuneIn; the starting instruction refers to an instruction for the user to start or restart a certain media service for the first time, such as starting an online radio service that has not been running before. It can be seen that the switching instruction of the target media service refers to an instruction to switch from other media services to the target media service, and the starting instruction of the target media service refers to an instruction to start the target media service for the first time. In one possible implementation, when the opening instruction is a switching instruction, it can be regarded as having been connected to the target media service through the media session component; when the opening instruction is a starting instruction, it can be regarded as not being connected to the target media service through the media session component.

[0059] Users can generate instructions to open the target media service through a variety of operating methods, for example, by clicking physical buttons in the car, such as media control keys, control buttons on the steering wheel, etc.; by clicking virtual controls on the in-vehicle media application interface, such as the switch button for the media service, the start icon for the media service, etc.; through the voice command recognition system, saying the name of the media service to be switched or started; or through the gesture recognition system, making specific gestures to indicate the switching or starting of the media service.

[0060] The interface container management pool involved in this embodiment is a resource pool for managing multiple interface containers. The interface container is a container that carries the user interface of the media service. It is responsible for displaying the content of the media service and receiving user interaction operations. The target interface container corresponding to the target media service refers to the interface container allocated to the target media service in the interface container management pool.

[0061] In response to the opening instruction of the target media service, the target interface container corresponding to the target media service is determined from the interface container management pool. This step can be specifically manifested in two situations: one is to search and determine an existing interface container that matches the target media service from the interface container management pool. This situation usually occurs when the user switches media services, and the interface container of the target media service has been created in the interface container management pool before; the other situation is that when there is no interface container that matches the target media service in the interface container management pool, a new interface container is created as needed and associated with the target media service. This situation usually occurs when the user starts a media service for the first time.

[0062] by Figure 4 For example, Figure 4 This is an example schematic diagram of an interface container management pool provided in an embodiment of the present application. The interface container management pool manages interface container 1 to interface container x, a total of x interface containers. In theory, each interface container in the interface container management pool can be allocated to a specific media service. The interface container allocation module is responsible for allocating the corresponding interface container to a specific media service in the interface container management pool, including executing the above-mentioned step of "determining the target interface container corresponding to the target media service from the interface container management pool".

[0063] S102: Determine a target data store corresponding to a target media service from a data store management pool, where the target data store is configured to obtain content data of the target media service.

[0064] Specifically, the data warehouse management pool involved in this embodiment is a resource pool for managing and storing multiple data warehouses. The data warehouse is a warehouse specifically used to store and manage the content data of a specific media service. It is responsible for providing various data required for the media service, such as music tracks, video streams, audio book chapters, podcast programs, online radio channels, live streaming content, etc. The content data of a media service refers to the specific playable or displayable data provided by the media service, including but not limited to audio files, video files, metadata (such as title, artist, album information), playlists, user preferences, play history, etc. Therefore, the target data warehouse is configured to obtain the content data of the target media service, which means that the target data warehouse is specially set up and configured so as to be able to establish a connection with the target media service and obtain, store and manage the required content data therefrom so as to provide it to the user interface for display or playback when needed.

[0065] Determining the target data warehouse corresponding to the target media service from the data warehouse management pool can be specifically manifested in two situations: one is to search and determine an existing data warehouse that matches the target media service from the data warehouse management pool. This situation usually occurs when the user switches the media service, and the data warehouse of the target media service has been created and stored in the data warehouse management pool before. The other situation is that when there is no data warehouse matching the target media service in the data warehouse management pool, a new data warehouse is created as needed and associated with the target media service. This situation usually occurs when the user starts a media service for the first time, or when the original data warehouse is deleted or unavailable for some reason.

[0066] by Figure 5 For example, Figure 5 This is an example schematic diagram of a data warehouse management pool provided in an embodiment of the present application. The data warehouse management pool manages data warehouse 1 to data warehouse y, a total of y data warehouses. In theory, each data warehouse in the data warehouse management pool can be allocated to a specific media service. The data warehouse allocation module is responsible for allocating the corresponding data warehouse to a specific media service in the data warehouse management pool, including executing the above-mentioned step of "determining the target data warehouse corresponding to the target media service from the data warehouse management pool".

[0067] It should be noted that the interface container management pool and the data warehouse management pool are independent of each other. They manage the creation, storage, retrieval and destruction of interface containers and data warehouses respectively. The life cycle of the interface container in the interface container management pool and the life cycle of the data warehouse in the data warehouse management pool may also be different. That is to say, the creation and destruction of the interface container may be more related to the display and hiding of the user interface, while the creation and destruction of the data warehouse may be more related to the acquisition and storage requirements of the content data of the media service. For example, even if the user switches to another media service, the data warehouse corresponding to the original media service may still be retained in the data warehouse management pool so that its data status can be quickly restored when the user switches back to the media service again. Similarly, even if an interface container is destroyed or hidden, its corresponding data warehouse may continue to exist so that the interface container can be recreated and the corresponding content data can be displayed when needed.

[0068] S103: Display a user interface corresponding to the target media service according to the target interface container and the content data of the target media service in the target data store.

[0069] Specifically, the target interface container provides a space and framework for displaying the target media service user interface. It is responsible for presenting the target media service user interface elements (such as buttons, icons, playback controls, progress bars, etc.) and content (such as music covers, video images, text information, etc.) to the user in an appropriate manner. The target interface container also receives and processes user interaction operations, such as clicks, slides, voice commands, etc., to achieve control of the target media service.

[0070] The content data of the target media service in the target data warehouse provides specific information displayed to the user, including but not limited to audio files, video files, metadata (such as title, artist, album information, number of plays, ratings, etc.), playlists, user preferences, play history, personalized recommendations, etc. The content data of the target media service is obtained and stored by the target data warehouse from the target media service so as to be provided to the target interface container for display or playback when needed.

[0071] According to the target interface container and the content data of the target media service in the target data warehouse, a complete user interface corresponding to the target media service can be constructed and displayed. In this process, the target interface container is responsible for the layout and interaction logic of the interface, while the target data warehouse provides the required content data of the target media service. Through the integration of the two, users can smoothly switch and use different media services while maintaining the independence of the user interface and data status of each media service.

[0072] by Figure 6 For example, Figure 6This is an example schematic diagram of the relationship between an interface container and a data warehouse provided in an embodiment of the present application. Among them, multiple interface containers in the interface container management pool are inherited from the same parent interface container, which is determined by the reuse characteristics of interface containers in the vehicle media application. It can be understood that any interface container in the interface container management pool is consistent with the user interface supported by the parent interface container. Figure 6 As shown in the figure, the interface container supports displaying user interface 1 to user interface m, a total of m user interfaces, which can be a login interface, a main interface, a search interface, a browsing interface, a playback interface, etc. The data warehouse corresponding to the interface container (that is, the interface container and the data warehouse are assigned to the same media service to support the operation of the media service) provides corresponding content data for each user interface of the interface container. For example, the data warehouse provides corresponding content data 1 for user interface data 1 of the interface container, and provides corresponding content data 2 for user interface data 2 of the interface container, and so on.

[0073] In a possible implementation, the execution subject of this embodiment is a vehicle, and steps S101 to S103 are steps integrated into an in-vehicle media application of the vehicle.

[0074] In a possible implementation, the in-vehicle media application runs based on the vehicle's Android operating system, the interface container is a task stack (Task), the user interface is an activity (Activity) instance, and the data warehouse is a repository component. Among them, the task stack is a mechanism for managing Activity instances in the Android operating system, which allows users to switch between multiple Activity instances while maintaining the status and history of each Activity instance. In the in-vehicle media application, each media service can correspond to an independent task stack, so that even if the user switches to other media services, the task stack corresponding to the original media service is still retained in the background, so that it can be restored to the previous state when the user switches back to the media service.

[0075] An Activity instance is a component used to display a user interface in an Android application. It can contain various UI elements, such as buttons, text views, image views, etc., and respond to user interactions. In an in-vehicle media application, each media service can correspond to one or more Activity instances, which are used to display different user interfaces of the media service, such as the main interface, playback interface, and settings interface. By organizing these Activity instances in the corresponding task stack, the isolation and management of interface containers can be achieved.

[0076] The Repository component is a component used to manage data in Android applications. It usually interacts with data sources (such as networks, databases, files, etc.) and provides data to other components of the application. In the in-vehicle media application, each media service can correspond to an independent Repository component to store and manage the content data of the media service, such as audio files, video files, metadata, etc. By organizing these Repository components in the data warehouse management pool, the isolation and management of the data warehouse can be achieved, ensuring the data independence and security of each media service.

[0077] In this embodiment, in response to the opening instruction of the target media service, the target interface container corresponding to the target media service can be determined from the interface container management pool, realizing isolation at the interface container level; the target data warehouse corresponding to the target media service can be determined from the data warehouse management pool, realizing isolation at the data warehouse level; finally, according to the content data of the target media service in the target interface container and the target data warehouse, the user interface corresponding to the target media service can be displayed. In this way, on the basis of dual isolation at the interface container level and the data warehouse level, it is possible to simultaneously connect and maintain multiple media services, and even if the user switches different media services or starts a new media service through operation, it will not cause the user interface of the original media service to be lost or the data status to be lost, effectively improving the user experience.

[0078] See also Figure 7 , provides a schematic diagram of a process for determining a target interface container for an embodiment of the present application, such as Figure 7 As shown, the method of the embodiment of the present application may include the following steps S201-S202, and steps S201-S202 may be used as Figure 3 The illustrated embodiment is a detailed step of "determining a target interface container corresponding to a target media service from an interface container management pool" in step S101.

[0079] S201, if a first interface container allocated to a target media service exists among the multiple interface containers managed by the interface container management pool, determining the first interface container as a target interface container corresponding to the target media service;

[0080] S202: If the first interface container allocated to the target media service does not exist in the multiple interface containers managed by the interface container management pool, allocate a target interface container to the target media service in the interface container management pool.

[0081] Specifically, when determining the target interface container corresponding to the target media service from the interface container management pool, two situations may occur.

[0082] In one case, if the first interface container allocated to the target media service exists in the multiple interface containers managed by the interface container management pool, it means that the target media service has been used by the user before, and its corresponding first interface container is still retained in the interface container management pool. At this time, in order to quickly respond to user needs and avoid the cost of recreating interface containers, the first interface container can be directly determined as the target interface container corresponding to the target media service, so that the user interface of the target media service can be quickly restored and displayed, while maintaining the user's previous usage status and data.

[0083] One of the situations is that the first interface container assigned to the target media service does not exist in the multiple interface containers managed by the interface container management pool. This usually happens when the user first starts or switches to the target media service, and the first interface container has not been assigned to it before. In this case, it is necessary to create a new interface container in the interface container management pool and assign it specifically to the target media service as its corresponding target interface container. Alternatively, a target interface container is assigned to the target media service from the multiple interface containers managed by the interface container management pool. The target interface container will be used to carry and display the user interface of the target media service and receive user interactions. At the same time, the relevant settings and status of the target interface container can also be initialized to ensure that it can correctly display the content of the target media service and respond to user instructions.

[0084] In this embodiment, when there is a first interface container assigned to the target media service in the interface container management pool, it is directly determined as the target interface container, which can not only quickly respond to user needs and reduce interface loading time, but also retain the user's previous usage status and data, and improve the consistency and satisfaction of user experience. When there is no first interface container assigned to the target media service in the interface container management pool, a new target interface container can be dynamically created or assigned to the target media service in the interface container management pool, ensuring that each media service has a corresponding interface container to carry and display its user interface, and realizing flexible expansion and management of interface containers.

[0085] See also Figure 8 , provides a flow chart of determining a target interface container for an embodiment of the present application, such as Figure 8 As shown, the method of the embodiment of the present application may include the following steps S301-S302, and steps S301-S302 may be used as Figure 7 The illustrated embodiment is a detailed step of "allocating a target interface container to the target media service in the interface container management pool" in step S202.

[0086] S301, if the total number of interface containers in the interface container management pool reaches a preset first upper limit, determining a second interface container from among the multiple interface containers managed by the interface container management pool, and allocating the second interface container as a target interface container corresponding to the target media service, the second interface container being any one of the multiple interface containers;

[0087] S302: If the total number of interface containers in the interface container management pool does not reach a preset first upper limit, create a third interface container in the interface container management pool, and allocate the third interface container as a target interface container corresponding to the target media service.

[0088] Specifically, this embodiment introduces a preset first quantity upper limit as a reference for whether a new interface container needs to be created. The preset first quantity upper limit refers to the maximum number of interface containers that can be accommodated or managed by the interface container management pool, which can be set according to factors such as the vehicle's hardware configuration, system resources, and performance requirements to ensure that the number of interface containers is reasonably managed without affecting the system's operating efficiency and user experience.

[0089] If the total number of interface containers in the interface container management pool reaches the preset first upper limit, it means that there are currently insufficient resources or space to create a new interface container. In this case, in order to effectively utilize existing resources and meet user needs, a second interface container can be determined from the multiple interface containers managed by the interface container management pool, and the second interface container can be assigned as the target interface container corresponding to the target media service. It can be understood that the second interface container refers to an interface container that already exists in the interface container management pool but is not currently occupied by any media service, or an interface container that was previously occupied by other media services but can now be replaced or reused. By selecting the second interface container as the target interface container, the overhead of creating a new interface container can be avoided, while ensuring that the target media service has a suitable interface container to display its user interface.

[0090] If the total number of interface containers in the interface container management pool does not reach the preset first upper limit, it means that there are currently sufficient resources or space to create new interface containers. In this case, in order to meet the needs of the target media service, a new third interface container can be created in the interface container management pool, and this third interface container can be assigned as the target interface container corresponding to the target media service. It can be understood that the third interface container refers to a newly created interface container specifically assigned to the target media service, which will be used to carry and display the user interface of the target media service and receive user interaction operations. By creating a new third interface container as the target interface container, it can be ensured that the target media service has an independent and exclusive interface container to display its content, thereby providing a better user experience and interface isolation.

[0091] For example, assume that the preset first upper limit is set to 10 interface containers. When there are already 10 interface containers running in the interface container management pool, the preset first upper limit is reached. At this time, if a new target media service needs to allocate an interface container, you can find an unoccupied or replaceable second interface container in the existing 10 interface containers and allocate it to the new target media service. In this way, there is no need to create a new interface container, thereby saving resources. On the contrary, if there are only 8 interface containers running in the interface container management pool and the preset first upper limit has not been reached, then a new third interface container can be created specifically for carrying and displaying the user interface of the new target media service, ensuring that the new target media service can have an independent and exclusive display space to enhance the user experience.

[0092] In this embodiment, by introducing a preset first upper limit, the allocation strategy of the interface container is refined, and efficient management and utilization of interface container resources are achieved. When the total number of interface containers in the interface container management pool reaches the preset first upper limit, by selecting the existing second interface container as the target interface container, the creation of a new interface container is avoided, system resources are saved, and at the same time, it is ensured that the target media service can quickly obtain display space. When the total number of interface containers does not reach the preset first upper limit, a new third interface container can be flexibly created to meet the display requirements of the target media service, thereby improving the user experience and interface isolation. In this way, not only is the stable operation of the interface container management pool ensured under limited resources, but also by dynamically adjusting the allocation method of the interface container, efficient resource configuration and optimization of user experience are achieved.

[0093] In one embodiment, Figure 7 The step S301 of the illustrated embodiment of “determining a second interface container from among multiple interface containers managed by the interface container management pool” is further refined and may include the following steps:

[0094] Determine an interface container to be reset from a plurality of interface containers managed by the interface container management pool based on a preset least recently used algorithm;

[0095] The interface container to be reset is reset to obtain a second interface container.

[0096] Specifically, the Least Recently Used (LRU) algorithm involved in this embodiment refers to a cache elimination algorithm for managing a cache space of limited size. In the interface container management pool, the LRU algorithm can select an interface container that has not been used for the longest time as the interface container to be reset based on the usage history of the interface container. In a possible implementation, it is implemented by maintaining a usage record or timestamp, and each time an interface container is accessed, its corresponding usage record or timestamp is updated. When it is necessary to select an interface container for reset, the interface container with the oldest usage record or timestamp is searched.

[0097] Based on a preset least recently used algorithm, an interface container to be reset is determined from among the multiple interface containers managed by the interface container management pool, specifically: all interface containers in the interface container management pool are traversed, and the most recent use time or access record of each interface container is checked. Then, based on these use times or access records, an interface container that has not been used for the longest time is selected as the interface container to be reset. It is understandable that the above process may involve comparing the use timestamps of each interface container, or querying a data structure (such as a linked list, a queue, or a priority queue) that records the most recent use of each interface container.

[0098] After determining the interface container to be reset, since the interface container to be reset may still retain the data of the previous media service, in order to reallocate it to the new target media service, the interface container to be reset needs to be reset. During the reset process, it is first necessary to stop the playback or interaction of any media service related to the interface container to be reset, and then clear all cached or temporary data related to the previous media service in the interface container to be reset. This is done to ensure that the new target media service can run in a clean, interference-free environment and will not be affected by the residual data of the previous media service.

[0099] After the interface container to be reset is reset, a second interface container is obtained. This second interface container is a clean, stateless interface container that is ready to receive a new target media service. It can be assigned to the target media service to display the user interface of the target media service and receive user interaction operations.

[0100] by Fig. 9 For example, Fig. 9This is an example schematic diagram of an interface container reset provided in an embodiment of the present application. Among them, the preset first upper limit is 3 interface containers, the existing interface container 1 in the interface container management pool is occupied by media service 1, interface container 2 is occupied by media service 2, and interface container 3 is occupied by media service 3. Media service 4, as the target media service determined based on the open instruction, needs to be allocated a corresponding interface container to media service 4, but the number of interface containers in the interface container management pool has reached the preset first upper limit, and a new interface container can no longer be created. At this time, based on the LRU algorithm, interface container 1 is determined to be the interface container to be reset, then the connection with media service 1 can be disconnected, and interface container 1 can be reset and allocated to media service 4 to realize the recycling and reuse of interface container 1, effectively saving system resources.

[0101] In this embodiment, by introducing the LRU algorithm, even when the total number of interface containers in the interface container management pool reaches the preset first upper limit, existing resources can be effectively used to meet the needs of the target media service while maintaining the continuity of user experience.

[0102] See also Fig.10 , which provides a flow chart of determining a target data warehouse in an embodiment of the present application, such as Fig.10 As shown, the method of the embodiment of the present application may include the following steps S401-S402. Steps S401-S402 may be used as Figure 3 The detailed steps of step S102 of the illustrated embodiment.

[0103] S401, if there is a first data bin allocated to a target media service among the multiple data bins managed by the data bin management pool, determine the first data bin as a target data bin corresponding to the target media service;

[0104] S402: If the first data store allocated to the target media service does not exist in the plurality of data stores managed by the data store management pool, a target data store is allocated to the target media service in the data store management pool.

[0105] Specifically, when determining the target data store corresponding to the target media service from the data store management pool, two situations may occur. These two situations are similar to those in the interface container management pool, but are aimed at the management and allocation of data stores.

[0106] In one case, there is a first data storehouse allocated to the target media service among the multiple data stores managed by the data storehouse management pool, which indicates that the target media service has been used by the user before, and its corresponding first data storehouse is still retained in the data storehouse management pool. At this time, in order to respond quickly and avoid the overhead of recreating the data storehouse, the first data storehouse can be directly determined as the target data storehouse corresponding to the target media service. In this way, the content data of the target media service can be quickly restored and accessed, while maintaining the user's previous data status and usage habits.

[0107] One of the situations is that the first data storehouse assigned to the target media service does not exist in the multiple data stores managed by the data storehouse management pool. This usually happens when the user starts or switches to the target media service for the first time, and the first data storehouse has not been assigned to it before. In this case, it is necessary to create a new data storehouse in the data storehouse management pool and assign it specifically to the target media service as its corresponding target data storehouse. Alternatively, a target data storehouse is assigned to the target media service from the multiple data stores managed by the data storehouse management pool to ensure that it can correctly store, manage and provide the content data of the target media service.

[0108] In this embodiment, when the first data warehouse corresponding to the target media service exists in the data warehouse management pool, it is directly determined as the target data warehouse, which not only reduces the data loading time, but also ensures the consistency and continuity of the data. When the first data warehouse does not exist in the data warehouse management pool, a new target data warehouse can be flexibly created or allocated in the data warehouse management pool, ensuring that the target media service has exclusive data storage space and meeting the data storage needs of the target media service. In this way, unnecessary waste of resources is avoided and the flexibility and scalability of data management are guaranteed.

[0109] See also Fig.11 , which provides a flow chart of determining a target data warehouse in an embodiment of the present application, such as Fig.11 As shown, the method of the embodiment of the present application may include the following steps S501-S502, and steps S501-S502 may be used as Fig.10 The illustrated embodiment is a detailed step of "allocating a target data store to a target media service in the data store management pool" in step S402.

[0110] S501, if the total number of data bins in the data bin management pool reaches a preset second upper limit, determining a second data bin from the multiple data bins managed by the data bin management pool, and allocating the second data bin as a target data bin corresponding to the target media service, the second data bin being any one of the multiple data bins;

[0111] S502: If the total number of data bins in the data bin management pool does not reach the preset second upper limit, create a third data bin in the data bin management pool, and allocate the third data bin as a target data bin corresponding to the target media service.

[0112] Specifically, this embodiment introduces a preset second upper limit as a reference for whether a new data warehouse needs to be created. The preset second upper limit refers to the maximum number of data warehouses that can be accommodated or managed by the data warehouse management pool, which can be set according to factors such as the vehicle's hardware configuration, system resources, performance requirements, and storage requirements to ensure that the number of data warehouses is reasonably managed while maintaining system operation efficiency and user experience.

[0113] If the total number of data warehouses in the data warehouse management pool reaches the preset second upper limit, it means that there are currently insufficient resources or space to create a new data warehouse. In this case, in order to efficiently utilize existing resources and meet user needs, a second data warehouse can be determined from the multiple data warehouses managed by the data warehouse management pool, and this second data warehouse can be assigned as the target data warehouse corresponding to the target media service. It can be understood that the second data warehouse refers to a data warehouse that already exists in the data warehouse management pool but is not currently occupied by any media service, or a data warehouse that was previously occupied by other media services but can now be replaced or reused. By selecting the second data warehouse as the target data warehouse, the resource consumption caused by the creation of a new data warehouse can be avoided, while ensuring that the target media service can have a suitable data warehouse to store and manage its content data.

[0114] If the total number of data warehouses in the data warehouse management pool does not reach the preset second upper limit, it means that there are currently sufficient resources or space to create a new data warehouse. In this case, in order to meet the data storage and management needs of the target media service, a new third data warehouse can be created in the data warehouse management pool, and this third data warehouse can be assigned as the target data warehouse corresponding to the target media service. It can be understood that the third data warehouse refers to a newly created data warehouse specifically assigned to the target media service, which will be used to store and manage the content data of the target media service, such as audio files, video files, metadata, playlists, user preferences, etc. By creating a new third data warehouse as the target data warehouse, it can be ensured that the target media service has an independent and exclusive data storage space, thereby providing better data isolation and user experience.

[0115] For example, suppose that the preset second upper limit is set to 20 data bins. When there are already 20 data bins running in the data bin management pool, the preset second upper limit is reached. At this time, if a new target media service needs to allocate a data bin, an unoccupied or replaceable second data bin can be found in the existing 20 data bins and allocated to the new target media service. In this way, there is no need to create a new data bin, thus saving resources. On the contrary, if there are only 18 data bins running in the data bin management pool and the preset second upper limit has not been reached, then a new third data bin can be created specifically for storing and managing the content data of the new target media service, ensuring that the new target media service can have an independent and exclusive data storage space, thereby improving data management efficiency and user experience.

[0116] In this embodiment, by introducing a preset second upper limit, the allocation strategy of the data warehouse is optimized, and efficient management and utilization of data warehouse resources are achieved. When the total number of data warehouses in the data warehouse management pool reaches the preset upper limit, an existing second data warehouse can be intelligently selected as the target data warehouse, avoiding the creation of a new data warehouse, saving system resources, and ensuring that the target media service can quickly obtain data storage space. When the total number of data warehouses does not reach the preset upper limit, a new third data warehouse can be flexibly created to meet the exclusive storage needs of the target media service, improving the efficiency of data management and user experience. In this way, not only is the stable operation of the data warehouse management pool guaranteed under limited resources, but also by dynamically adjusting the allocation method of the data warehouse, efficient resource configuration is achieved.

[0117] In one embodiment, Fig.11 The step S501 of the illustrated embodiment of “determining a second data store from among multiple data stores managed by the data store management pool” is further refined and may include the following steps:

[0118] Determine a data bin to be reset from among multiple data bins managed by the data bin management pool based on a preset least recently used algorithm;

[0119] The data bin to be reset is reset to obtain a second data bin.

[0120] Specifically, this embodiment adopts the LRU algorithm to manage the data bins in the data bin management pool. For the specific role of the LRU algorithm, please refer to the above embodiment, which will not be described here. The LRU algorithm is used here to select a data bin that has not been used for the longest time as the data bin to be reset based on the usage history of the data bin. This is because, in the data bin management pool, as users continue to switch and use different media services, some data bins may become inactive, and the LRU algorithm can help us identify and process these inactive data bins.

[0121] Based on the preset least recently used algorithm, a data bin to be reset is determined from among the multiple data bins managed by the data bin management pool. The specific implementation method is as follows: traverse all data bins in the data bin management pool and check the most recently used records or timestamps of each data bin. The most recently used records or timestamps of these data bins can be automatically updated by the system each time the data bin is accessed to ensure that they can accurately reflect the usage of the data bin. Next, all data bins are sorted according to these usage records or timestamps, or a data structure (such as a linked list, a queue or a priority queue) that records the most recent usage of each data bin is queried, so as to select a data bin that has not been used for the longest time as the data bin to be reset.

[0122] After determining the data store to be reset, since the data store to be reset may still retain the content data of the previous media service, in order to reallocate it to the new target media service, the data store to be reset needs to be reset. During the reset process, it is first necessary to stop the playback or data interaction of any media service related to the data store to be reset, and then clear all cached data, temporary files or status information related to the previous media service in the data store to be reset. This is done to ensure that the new target media service can run in a clean, undisturbed data environment and will not be affected by the residual data of the previous media service.

[0123] After the data bin to be reset is reset, a second data bin is obtained. This second data bin is a data bin that has been cleared, stateless, and is ready to receive new target media service content data. It can be assigned to the target media service to store and manage the content data of the target media service, such as audio files, video files, metadata, playlists, etc., and provide it to the user interface for display or playback when needed.

[0124] by Fig.12 For example, Fig.12 This is an example schematic diagram of a data bin reset provided in an embodiment of the present application. Among them, the preset second upper limit is 3 data bins, the existing data bin 1 in the data bin management pool is occupied by media service 1, data bin 2 is occupied by media service 2, and data bin 3 is occupied by media service 3. As the target media service determined based on the open instruction, media service 4 needs to be allocated a corresponding data bin, but the number of data bins in the data bin management pool has reached the preset second upper limit, and no new data bins can be created. At this time, based on the LRU algorithm, data bin 1 is determined to be the data bin to be reset, then the connection with media service 1 can be disconnected, and data bin 1 can be reset and allocated to media service 4 to realize the recycling and reuse of data bin 1, effectively saving system resources.

[0125] In this embodiment, by introducing the LRU algorithm to manage the data bins in the data bin management pool, even when the total number of data bins in the data bin management pool reaches the preset second upper limit, the existing resources can be effectively used to meet the data storage and management requirements of the target media service. At the same time, by resetting the inactive data bins to allocate them to the new target media service, the continuity of user experience and the consistency of data can be maintained.

[0126] See also Fig.13 , provides a schematic diagram of a process of connecting a target media service through a media session component according to an embodiment of the present application, wherein the opening instruction of the target media service is a starting instruction of the target media service. Fig.13 As shown, the method of the embodiment of the present application may include the following steps S601-S602, and steps S601-S602 may be used as Figure 3 The detailed steps of step S101 of the embodiment are shown.

[0127] S601, in response to a start instruction of a target media service, connecting to the target media service through a preset media session component;

[0128] S602: When connected to the target media service, determine a target interface container corresponding to the target media service from the interface container management pool.

[0129] Specifically, in this embodiment, the target media service opening instruction is a target media service startup instruction, which means that the user wants to start or restart the target media service for the first time, rather than switching from the currently used media service to the target media service. In this case, a series of operations need to be performed to initialize and start the target media service, including establishing a connection with the target media service, allocating resources, loading necessary data, etc.

[0130] The media session component involved in this embodiment refers to a component used to manage conversations and interactions with media services. It acts as a bridge between the in-vehicle media application and the media service, and is responsible for transmitting instructions, data and information, as well as coordinating operations such as playing, pausing and stopping the media service. The media session component usually provides a rich application programming interface (API) so that the in-vehicle media application can communicate and control the media service. For example, the media session component can be the MediaSession component provided by Google or a component improved on the basis of the MediaSession component, which can support multiple media service types and provide a unified interface to manage these media services.

[0131] In response to the start instruction of the target media service, the target media service is connected through the preset media session component. Specifically, when the start instruction of the target media service is received, the start instruction is first identified and parsed to determine the target media service that the user wants to start. Then, the preset media session component is called and the necessary parameters and information are passed to establish a connection with the target media service. After receiving these parameters and information, the media session component will start to communicate and negotiate with the target media service, including identity verification, resource request, session establishment, etc. Once the connection is successfully established, the media session component will return a status or signal indicating that the connection is successful so as to continue to perform subsequent operations.

[0132] After confirming the connection to the target media service, subsequent steps can be executed to determine the target interface container corresponding to the target media service from the interface container management pool, determine the target data warehouse corresponding to the target media service from the data warehouse management pool, and display the user interface corresponding to the target media service based on the content data of the target media service in the target interface container and the target data warehouse.

[0133] In this embodiment, when a start instruction is received, a connection can be established with the target media service through the media session component. This process not only simplifies the start-up process of the media service, but also improves the response speed and connection stability.

[0134] Based on the above Figure 3 - Fig.13 For the illustrated embodiment, see Fig.14 , Fig.14 It is a comprehensive flow diagram of an interface display provided in an embodiment of the present application.

[0135] In this embodiment, first responding to the opening instruction of the target media service, the type of the opening instruction is determined. If the opening instruction is a start instruction, the target media service is connected through a preset media session component; when connected to the target media service, it is further determined whether there is a first interface container allocated to the target media service in the interface container management pool. If the opening instruction is not a start instruction (it may be a switch instruction), it is directly determined whether there is a first interface container allocated to the target media service in the interface container management pool.

[0136] If the first interface container allocated to the target media service exists in the interface container management pool, the first interface container is determined as the target interface container corresponding to the target media service. If the first interface container allocated to the target media service does not exist in the interface container management pool, it is further determined whether the total number of interface containers in the interface container management pool reaches a preset first upper limit.

[0137] If the total number of interface containers in the interface container management pool reaches the preset first upper limit, a second interface container is determined from the multiple interface containers managed by the interface container management pool, and the second interface container is allocated as the target interface container corresponding to the target media service, and the second interface container is any interface container in the multiple interface containers. If the total number of interface containers in the interface container management pool does not reach the preset first upper limit, a third interface container is created in the interface container management pool, and the third interface container is allocated as the target interface container corresponding to the target media service.

[0138] After determining the target interface container corresponding to the target media service, it is further determined whether there is a first data store allocated to the target media service in the data store management pool.

[0139] If there is a first data bin allocated to the target media service in the data bin management pool, the first data bin is determined as the target data bin corresponding to the target media service. If there is no first data bin allocated to the target media service in the data bin management pool, it is further determined whether the total number of data bins in the data bin management pool reaches a preset second number upper limit.

[0140] If the total number of data bins in the data bin management pool reaches the preset second upper limit, a second data bin is determined from the multiple data bins managed by the data bin management pool, and the second data bin is allocated as the target data bin corresponding to the target media service, where the second data bin is any data bin in the multiple data bins. If the total number of data bins in the data bin management pool does not reach the preset second upper limit, a third data bin is created in the data bin management pool, and the third data bin is allocated as the target data bin corresponding to the target media service.

[0141] After the target data bin corresponding to the target media service is determined, the user interface corresponding to the target media service is displayed according to the target interface container and the content data of the target media service in the target data bin.

[0142] For the effects that can be achieved by this embodiment, please refer to the relevant embodiments of the above-mentioned interface display method, which will not be repeated here.

[0143] Based on the above Figure 1 - Figure 2 The following will combine Fig.15 The interface display device provided in the embodiment of the present application is introduced in detail. It should be noted that: Fig.15 The interface display device is used to execute the present application Figure 3 - Fig.14 For the convenience of explanation, only the part related to the embodiment of the present application is shown. For the specific technical details not disclosed, please refer to the present application. Figure 3 - Fig.14Specifically, the interface display device 800 may include a first determination unit 801, a second determination unit 802, and a display unit 803, as follows:

[0144] The first determining unit 801 is used to determine a target interface container corresponding to the target media service from the interface container management pool in response to an opening instruction of the target media service;

[0145] A second determining unit 802 is configured to determine a target data store corresponding to a target media service from a data store management pool, where the target data store is configured to obtain content data of the target media service;

[0146] The display unit 803 is used to display a user interface corresponding to the target media service according to the target interface container and the content data of the target media service in the target data bin.

[0147] Optionally, in some embodiments, the first determination unit 801 can be used to: if there is a first interface container assigned to the target media service among the multiple interface containers managed by the interface container management pool, then determine the first interface container as the target interface container corresponding to the target media service; if there is no first interface container assigned to the target media service among the multiple interface containers managed by the interface container management pool, then allocate the target interface container to the target media service in the interface container management pool.

[0148] Optionally, in some embodiments, the first determination unit 801 can be used to: if the total number of interface containers in the interface container management pool reaches a preset first upper limit, then determine a second interface container from the multiple interface containers managed by the interface container management pool, and allocate the second interface container as the target interface container corresponding to the target media service, the second interface container being any interface container among the multiple interface containers; if the total number of interface containers in the interface container management pool does not reach the preset first upper limit, then create a third interface container in the interface container management pool, and allocate the third interface container as the target interface container corresponding to the target media service.

[0149] Optionally, in some embodiments, the first determining unit 801 may be used to: determine an interface container to be reset from multiple interface containers managed by the interface container management pool based on a preset least recently used algorithm; and reset the interface container to be reset to obtain a second interface container.

[0150] Optionally, in some embodiments, the second determination unit 802 can be used to: if there is a first data warehouse assigned to the target media service among the multiple data warehouses managed by the data warehouse management pool, determine the first data warehouse as the target data warehouse corresponding to the target media service; if there is no first data warehouse assigned to the target media service among the multiple data warehouses managed by the data warehouse management pool, allocate the target data warehouse to the target media service in the data warehouse management pool.

[0151] Optionally, in some embodiments, the second determination unit 802 can be used to: if the total number of data warehouses in the data warehouse management pool reaches a preset second upper limit, then determine a second data warehouse among the multiple data warehouses managed by the data warehouse management pool, and allocate the second data warehouse as the target data warehouse corresponding to the target media service, the second data warehouse being any data warehouse among the multiple data warehouses; if the total number of data warehouses in the data warehouse management pool does not reach the preset second upper limit, then create a third data warehouse in the data warehouse management pool, and allocate the third data warehouse as the target data warehouse corresponding to the target media service.

[0152] Optionally, in some embodiments, the second determination unit 802 may be used to: determine a data bin to be reset among multiple data bins managed by the data bin management pool based on a preset least recently used algorithm; and reset the data bin to be reset to obtain a second data bin.

[0153] Optionally, in some embodiments, the opening instruction of the target media service is a start instruction of the target media service; the first determination unit 801 can be used to: respond to the start instruction of the target media service, connect to the target media service through a preset media session component; when connected to the target media service, determine the target interface container corresponding to the target media service from the interface container management pool.

[0154] For the effects that can be achieved by this embodiment, please refer to the relevant embodiments of the above-mentioned interface display method, which will not be repeated here.

[0155] See also Fig.16 , which is a schematic diagram of the structure of a vehicle provided in the embodiment of the present application. Fig.16 As shown, the vehicle 900 includes a processor 901 and a memory 902. The processor 901 is electrically connected to the memory 902.

[0156] The processor 901 is the control center of the vehicle 900 and may include one or more processing cores. The processor 901 uses various interfaces and lines to connect various parts of the entire vehicle 900, and executes various functions and processes data of the vehicle 900 by running or calling computer programs stored in the memory 902, and calling data stored in the memory 902, so as to control the vehicle 900 as a whole. Optionally, the processor 901 may be implemented in at least one hardware form of digital signal processing (DSP), field programmable gate array (FPGA), and programmable logic array (PLA). The processor 901 may integrate one or a combination of CPU, graphics processing unit (GPU), modem, etc. Among them, the CPU mainly processes the operating system, user pages, and applications; the GPU is responsible for rendering and drawing display content; and the modem is used to process wireless communications. It is understandable that the above-mentioned modem may not be integrated into the processor 901, but may be implemented separately through a communication chip.

[0157] The memory 902 may be used to store software programs and modules, and the processor 901 executes various functional applications and data processing by running the computer programs and modules stored in the memory 902. The memory 902 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, a computer program required for at least one function, etc.; the data storage area may store data created according to the use of the vehicle 900, etc.

[0158] In addition, the memory 902 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other volatile solid-state storage devices. Accordingly, the memory 902 may also include a memory controller to provide the processor 901 with access to the memory 902.

[0159] In this embodiment, the processor 901 in the vehicle 900 loads instructions corresponding to the processes of one or more computer programs into the memory 902 according to the following steps, and the processor 901 runs the computer program stored in the memory 902 to implement various functions, as follows:

[0160] In response to an opening instruction of the target media service, determining a target interface container corresponding to the target media service from an interface container management pool;

[0161] Determine a target data store corresponding to the target media service from the data store management pool, where the target data store is configured to obtain content data of the target media service;

[0162] The user interface corresponding to the target media service is displayed according to the target interface container and the content data of the target media service in the target data bin.

[0163] Optionally, when executing to determine the target interface container corresponding to the target media service from the interface container management pool, the processor 901 specifically performs: if there is a first interface container allocated to the target media service among the multiple interface containers managed by the interface container management pool, then the first interface container is determined as the target interface container corresponding to the target media service; if there is no first interface container allocated to the target media service among the multiple interface containers managed by the interface container management pool, then the target interface container is allocated to the target media service in the interface container management pool.

[0164] Optionally, when executing the allocation of a target interface container to a target media service in the interface container management pool, the processor 901 specifically performs the following steps: if the total number of interface containers in the interface container management pool reaches a preset first upper limit, then a second interface container is determined from multiple interface containers managed by the interface container management pool, and the second interface container is allocated as the target interface container corresponding to the target media service, where the second interface container is any interface container among the multiple interface containers; if the total number of interface containers in the interface container management pool does not reach the preset first upper limit, then a third interface container is created in the interface container management pool, and the third interface container is allocated as the target interface container corresponding to the target media service.

[0165] Optionally, when the processor 901 determines the second interface container from among the multiple interface containers managed by the interface container management pool, it specifically executes: determining an interface container to be reset from among the multiple interface containers managed by the interface container management pool based on a preset least recently used algorithm; and resetting the interface container to be reset to obtain the second interface container.

[0166] Optionally, when the processor 901 determines the target data warehouse corresponding to the target media service from the data warehouse management pool, it specifically performs: if there is a first data warehouse assigned to the target media service among the multiple data warehouses managed by the data warehouse management pool, the first data warehouse is determined as the target data warehouse corresponding to the target media service; if there is no first data warehouse assigned to the target media service among the multiple data warehouses managed by the data warehouse management pool, the target data warehouse is allocated to the target media service in the data warehouse management pool.

[0167] Optionally, when executing the allocation of a target data warehouse to a target media service in the data warehouse management pool, the processor 901 specifically executes: if the total number of data warehouses in the data warehouse management pool reaches a preset second upper limit, then determining a second data warehouse among the multiple data warehouses managed by the data warehouse management pool, and allocating the second data warehouse as the target data warehouse corresponding to the target media service, the second data warehouse being any data warehouse among the multiple data warehouses; if the total number of data warehouses in the data warehouse management pool does not reach the preset second upper limit, then creating a third data warehouse in the data warehouse management pool, and allocating the third data warehouse as the target data warehouse corresponding to the target media service.

[0168] Optionally, when the processor 901 determines the second data bin among the multiple data bins managed by the data bin management pool, it specifically executes: determining a data bin to be reset among the multiple data bins managed by the data bin management pool based on a preset least recently used algorithm; and resetting the data bin to be reset to obtain the second data bin.

[0169] Optionally, the opening instruction of the target media service is a start instruction of the target media service; when the processor 901 executes in response to the opening instruction of the target media service and determines the target interface container corresponding to the target media service from the interface container management pool, it specifically executes: in response to the start instruction of the target media service, connecting to the target media service through a preset media session component; when connected to the target media service, determining the target interface container corresponding to the target media service from the interface container management pool.

[0170] For the effects that can be achieved by this embodiment, please refer to the relevant embodiments of the above-mentioned interface display method, which will not be repeated here.

[0171] It should be understood that the device provided in the embodiment of the present application is used to execute the above-mentioned interface display method, and thus can achieve the same effect as the above-mentioned implementation method.

[0172] In the case of an integrated unit, the device may include a processing module and a storage module. When the device is applied to a vehicle, the processing module may be used to control and manage the actions of the vehicle. The storage module may be used to support the vehicle in executing relevant program codes, etc.

[0173] The processing module may be a processor or a controller, which may implement or execute various exemplary logic blocks, modules and circuits described in conjunction with the disclosure of this application. The processor may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of digital signal processing (DSP) and a microprocessor, etc. The storage module may be a memory.

[0174] In addition, the device provided in the embodiment of the present application can specifically be a chip, component or module, and the chip may include a connected processor and memory; wherein the memory is used to store instructions, and when the processor calls and executes the instructions, the chip can execute an interface display method provided in the above embodiment.

[0175] An embodiment of the present application also provides a computer-readable storage medium, in which a computer program code is stored. When the computer program code is executed on a computer, the computer executes the above-mentioned related method steps to implement an interface display method provided in the above-mentioned embodiment.

[0176] This embodiment further provides a computer program product. When the computer program product is run on a computer, the computer is caused to execute the above-mentioned related steps to implement an interface display method provided by the above-mentioned embodiment.

[0177] Among them, the device, computer-readable storage medium, computer program product or chip provided in this embodiment is used to execute the corresponding method provided above. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding method provided above, and will not be repeated here.

[0178] Through the description of the above implementation methods, technical personnel in the relevant field can understand that for the convenience and simplicity of description, only the division of the above-mentioned functional modules is used as an example. In actual applications, the above-mentioned functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0179] In the embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of modules or units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another device, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0180] The above contents are only specific implementation methods of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. An interface display method, characterized in that: include: In response to an opening instruction of a target media service, determining a target interface container corresponding to the target media service from an interface container management pool; Determine a target data store corresponding to the target media service from a data store management pool, wherein the target data store is configured to obtain content data of the target media service; A user interface corresponding to the target media service is displayed according to the target interface container and the content data of the target media service in the target data bin.

2. The method according to claim 1, characterized in that The step of determining the target interface container corresponding to the target media service from the interface container management pool includes: If there is a first interface container allocated to the target media service among the multiple interface containers managed by the interface container management pool, determining the first interface container as the target interface container corresponding to the target media service; If the first interface container allocated to the target media service does not exist in the plurality of interface containers managed by the interface container management pool, a target interface container is allocated to the target media service in the interface container management pool.

3. The method according to claim 2, characterized in that The allocating a target interface container to the target media service in the interface container management pool includes: If the total number of interface containers in the interface container management pool reaches a preset first upper limit, a second interface container is determined from among the multiple interface containers managed by the interface container management pool, and the second interface container is allocated as a target interface container corresponding to the target media service, wherein the second interface container is any one of the multiple interface containers; If the total number of interface containers in the interface container management pool does not reach the preset first upper limit, a third interface container is created in the interface container management pool, and the third interface container is allocated as a target interface container corresponding to the target media service.

4. The method according to claim 3, characterized in that The determining of the second interface container from the plurality of interface containers managed by the interface container management pool includes: Determine an interface container to be reset from among the multiple interface containers managed by the interface container management pool based on a preset least recently used algorithm; The interface container to be reset is reset to obtain the second interface container.

5. The method according to claim 1, characterized in that The determining, from a data store management pool, a target data store corresponding to the target media service comprises: If there is a first data bin allocated to the target media service among the multiple data bins managed by the data bin management pool, determining the first data bin as the target data bin corresponding to the target media service; If the first data bin allocated to the target media service does not exist among the plurality of data bins managed by the data bin management pool, a target data bin is allocated to the target media service in the data bin management pool.

6. The method according to claim 5, characterized in that The allocating a target data store to the target media service in the data store management pool includes: If the total number of data bins in the data bin management pool reaches a preset second upper limit, determining a second data bin from the multiple data bins managed by the data bin management pool, and allocating the second data bin as a target data bin corresponding to the target media service, the second data bin being any one of the multiple data bins; If the total number of data bins in the data bin management pool does not reach the preset second upper limit, a third data bin is created in the data bin management pool, and the third data bin is allocated as a target data bin corresponding to the target media service.

7. The method according to claim 6, characterized in that The determining of the second data bin from the plurality of data bins managed by the data bin management pool comprises: Determine a data bin to be reset from among the plurality of data bins managed by the data bin management pool based on a preset least recently used algorithm; The data bin to be reset is reset to obtain the second data bin.

8. The method according to claim 1, characterized in that The opening instruction of the target media service is a starting instruction of the target media service; The step of determining, in response to an opening instruction of a target media service, a target interface container corresponding to the target media service from an interface container management pool comprises: In response to a start instruction of the target media service, connecting to the target media service through a preset media session component; In case of connecting to the target media service, a target interface container corresponding to the target media service is determined from the interface container management pool.

9. An interface display device, characterized in that: include: A first determining unit, configured to determine, in response to an opening instruction of a target media service, a target interface container corresponding to the target media service from an interface container management pool; A second determining unit, configured to determine a target data store corresponding to the target media service from a data store management pool, wherein the target data store is configured to obtain content data of the target media service; The display unit is configured to display a user interface corresponding to the target media service according to the target interface container and the content data of the target media service in the target data bin.

10. A vehicle, characterized in that: include: A memory for storing executable program codes; A processor is used to call and run the executable program code from the memory so that the vehicle executes the method as claimed in any one of claims 1 to 8.

11. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program code, and when the computer program code is executed, the method according to any one of claims 1 to 8 is implemented.

Images