A card display method, device and apparatus

Abstract

The application provides a card display method, device and equipment, which is applied to the software technical field and comprises the following steps: when a target display screen in multiple display screens is started, a shared desktop shared by the multiple display screens is acquired, card information of a target card to be displayed by the target display screen is acquired, then the shared desktop is run in the target display screen based on the card information, and the target display screen displays the target card. In the card display method provided by the application, one shared desktop is configured for the multiple display screens of a device, and multiple cards included in the shared desktop can be adapted to each display screen, so that the multiple display screens display the cards based on one shared desktop, which can significantly reduce the workload in the research and development process and improve the research and development efficiency.

Description

Technical Field

[0001] This application relates to the field of software technology, and more specifically, to a card display method, apparatus, and device in the field of software technology. Background Technology

[0002] Currently, all displays include a certain number of widgets in their user interface (UI). These widgets serve as quick access points to applications or services, allowing users to quickly open and use them, and also displaying the latest information about the applications or services, such as weather forecasts and schedule reminders.

[0003] Some devices are equipped with multiple displays. Multiple displays not only allow the device to show more information simultaneously, but also facilitate user operation from different directions and / or positions. However, when a device has multiple displays, a certain number of cards need to be developed for each display during the device development process, which is a significant workload. Summary of the Invention

[0004] This application provides a card display method, apparatus, and device that can reduce the workload in the research and development process of devices with multiple displays.

[0005] In a first aspect, a card display method is provided, applied to a device having multiple displays, the method comprising:

[0006] When a target display screen among the plurality of displays is started, a shared desktop shared by the plurality of displays is obtained, the shared desktop comprising a plurality of cards;

[0007] Obtain card information of at least one target card that the target display screen needs to display; wherein, the target card is a card among the plurality of cards;

[0008] The shared desktop is run on the target display screen based on the card information, so that the target display screen displays the target card.

[0009] In this embodiment, a shared desktop is configured for multiple displays on a device. The shared desktop includes multiple cards that can be adapted to each display. When the target display starts, the shared desktop of the multiple displays is obtained, along with the card information of the target card that needs to be displayed on the target display. Then, based on the card information, the shared desktop is run on the target display, causing the target display to display the target card. For devices with multiple displays, only one shared desktop needs to be developed, along with a certain number of cards for the shared desktop. Compared to developing cards separately for each display, this significantly reduces the workload in the development process and improves development efficiency.

[0010] Furthermore, during later maintenance, only multiple cards within the shared desktop need to be maintained, significantly reducing the workload, difficulty, and cost of maintenance. Additionally, when multiple displays share multiple cards within the shared desktop, the consistency of cards across different displays is improved, thereby enhancing the user experience.

[0011] Optionally, obtaining the card information of at least one target card to be displayed on the target display screen includes: determining whether the target card configuration of the target display screen is included in the at least one pre-stored card configuration; if the target card configuration is included, then obtaining the card information from the target card configuration.

[0012] In this embodiment, card configuration is set for the cards on the display screen, enabling the display screen to create card instances based on the card information in the card configuration during startup, and then display the cards based on the card instances. In this way, the display screen can be flexibly configured to display the cards that need to be shown through the card configuration settings.

[0013] Optionally, after running the shared desktop on the target display screen based on the card information, the method further includes: if a deletion instruction for a first card is received, deleting the card information of the first card included in the target card configuration; wherein the first card is a card among the at least one target card; and / or, if an addition instruction for a second card is received, adding the card information of the second card to the target card configuration; wherein the second card is another card among the plurality of cards besides the target card.

[0014] In this embodiment of the application, when adding and / or deleting cards on the display screen, the card information in the corresponding card configuration of the display screen is updated synchronously, so that the display screen can automatically add and / or delete cards on the next startup, which makes it convenient for users to flexibly set the cards on the display screen according to their needs.

[0015] Optionally, the card information includes the card package name and card instance identifier of the target card. The method further includes: if the target card configuration is not included in the at least one card configuration, then setting a new card instance identifier for each of the multiple cards based on the card instance identifiers of the multiple cards in the at least one card configuration; and creating the target card configuration based on the card package name and the new card instance identifier of each of the multiple cards.

[0016] In this embodiment of the application, when the card configuration of the target display screen is not included in at least one pre-stored card configuration, a card configuration is created for the target display screen based on the card instance identifiers of multiple cards in the pre-stored card configuration. This allows the card configuration to be automatically set for the target display screen when it is first connected to the device.

[0017] Optionally, the card information includes the target card's package name and card instance identifier, and running the shared desktop on the target display screen based on the card information includes: running the shared desktop on the target display screen; and creating a card instance of the target card based on the target card's package name and card instance identifier in the running shared desktop.

[0018] In this embodiment, the card information includes the target card's package name and card instance identifier. When running a shared desktop on the target display screen, a card instance of the target card is created based on the target card's package name and card instance identifier. This allows for the rapid creation of a card instance of the target card in the shared desktop, thereby improving card display efficiency.

[0019] Optionally, the card information includes the package name of the target card, and running the shared desktop on the target display screen based on the card information includes: determining the card instance identifier of a third card; wherein the third card is a card displayed on another display screen that is in operation among the plurality of display screens; running the shared desktop on the target display screen; in the running shared desktop, creating a card instance of the target card based on the package name of the target card, and setting a unique card instance identifier for the card instance; wherein the card instance identifier of the target card is different from the card instance identifier of the third card.

[0020] In this embodiment of the application, based on the card instance identifier of the card displayed on other displays that are in operation among multiple displays, the card instance identifier of the target card is set, and the card instance of the target card is created based on the set card instance identifier. This allows the same card to be displayed on multiple displays based on the card package name.

[0021] Optionally, obtaining the shared desktop of the plurality of displays includes: determining the screen identifier of the target display; and obtaining the shared desktop when it is determined based on the screen identifier that the target display belongs to one of the plurality of displays.

[0022] In this embodiment, before launching the display screen based on the shared desktop, the display screen is verified by the screen identifier of the display screen. After successful verification, the display screen is launched based on the shared desktop, which enables secure management of the device's display screen and improves the device's security.

[0023] Optionally, before running the shared desktop on the target display screen based on the card information, the method further includes: obtaining the desktop attribute configuration of the target display screen; and replacing the desktop attribute configuration of the shared desktop with the desktop attribute configuration of the target display screen.

[0024] In this embodiment, a corresponding desktop attribute configuration is set for the display screen, and the desktop attribute configuration in the shared desktop is replaced by the desktop attribute configuration of the display screen. The desktop in each display screen can be adjusted differently according to the needs.

[0025] Secondly, a card display device is provided, disposed in a device having multiple displays, the device comprising:

[0026] The acquisition module is used to acquire a shared desktop shared by the multiple displays when the target display among the multiple displays is started, the shared desktop including multiple cards;

[0027] The acquisition module is further configured to acquire card information of at least one target card that the target display screen needs to display; wherein, the target card is a card among the plurality of cards;

[0028] The running module is used to run the shared desktop on the target display screen based on the card information, so that the target display screen displays the target card.

[0029] Thirdly, an apparatus is provided, comprising a memory for storing executable program code; and a processor for calling and running the executable program code from the memory, such that the apparatus performs the method in any possible implementation of the first aspect described above.

[0030] Fourthly, a program product is provided, comprising: executable program code, which, when run on a device, causes the device to perform the method in any possible implementation of the first aspect described above.

[0031] Fifthly, a readable storage medium is provided that stores executable program code, which, when run on a device, causes the device to perform the method in any possible implementation of the first aspect described above. Attached Figure Description

[0032] Figure 1 This is a schematic diagram of the composition of a vehicle display system in related technologies;

[0033] Figure 2 This is a schematic diagram of the composition of a vehicle display system provided in an embodiment of this application;

[0034] Figure 3 This is a flowchart illustrating a card display method provided in an embodiment of this application;

[0035] Figure 4 This is a schematic diagram of the structure of a card display device provided in an embodiment of this application;

[0036] Figure 5 This is a schematic diagram of the structure of a device provided in an embodiment of this application. Detailed Implementation

[0037] The technical solutions in this application will be clearly and thoroughly described below with reference to the accompanying drawings. In the description of the embodiments of this application, unless otherwise stated, " / " means "or," for example, A / B can mean A or B. "And / or" in the text is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Furthermore, in the description of the embodiments of this application, "multiple" refers to two or more than two.

[0038] Hereinafter, the terms "first" and "second" are used for descriptive purposes only and should not be construed as implying or suggesting 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 that feature.

[0039] Cards serve as quick access points to applications or services displayed on the user interface. They not only allow users to quickly open and use the application or service, but also display the latest information about the application or service, such as weather forecasts and schedule reminders, enabling users to obtain the content they need without opening the application. Based on these advantages, a certain number of cards are configured in the user interface of each display screen.

[0040] Some devices are equipped with multiple displays. Multiple displays not only allow the device to show more information simultaneously but also facilitate user operation. However, when a device has multiple displays, the development process requires the creation of a certain number of cards for each display, resulting in a significant workload. For example, in vehicles, with the development of vehicle intelligence, the number of in-vehicle displays is increasing. In addition to the central control screen, vehicles may also have passenger screens, ceiling-mounted screens, armrest screens, and head-up displays. Most in-vehicle displays are touchscreens, and for touchscreens, cards and related interactions are almost fundamental requirements; therefore, most in-vehicle displays are equipped with a certain number of cards.

[0041] like Figure 1 As shown, Figure 1This is a schematic diagram of a vehicle display system in related technologies. When a vehicle has displays such as a central control screen, passenger screen, ceiling-mounted screen, and armrest screen, a separate desktop and a certain number of cards need to be developed for each display, resulting in a significant workload. When a vehicle has multiple displays, during the vehicle development phase, not only does a separate desktop need to be developed for each display, but also separate cards need to be developed for each desktop, leading to a large workload and low efficiency. Moreover, during later vehicle maintenance, the cards in each display need to be maintained, increasing both the workload and the difficulty and cost of maintenance. Furthermore, when developing separate cards for desktops of different displays, it is difficult to maintain consistency among the cards across different displays, severely degrading the user experience.

[0042] In this context, "desktop" refers to a desktop application (APP), also known as a desktop launcher. For example, when the device's operating system is Android, the desktop displayed on the screen is the Launcher within the Android system.

[0043] To address the aforementioned technical problems, this application provides a card display method. In this method, a desktop (hereinafter referred to as a shared desktop) is configured for multiple displays on a device. The shared desktop has multiple cards, and the cards in the shared desktop can be adapted to each display. When any one or more displays on the device (hereinafter referred to as target displays) are started, card information of the target cards to be displayed on the target displays is obtained. Based on the card information, the shared desktop is run on the target displays, causing the target displays to display the target cards.

[0044] like Figure 2 As shown, Figure 2 This is a schematic diagram illustrating the composition of a vehicle display system provided in an embodiment of this application. When a vehicle has displays such as a central control screen, passenger screen, ceiling-mounted screen, armrest screen, and head-up display, a shared desktop is developed for multiple displays in the vehicle. Multiple displays share this shared desktop, and only a certain number of cards need to be developed for this shared desktop. Thus, for vehicles with multiple displays, only one shared desktop needs to be developed, along with a certain number of cards for it. Compared to developing cards separately for each display, this significantly reduces the workload during the development process and improves development efficiency.

[0045] Furthermore, during later card maintenance, only multiple cards within the shared desktop need to be maintained, significantly reducing the workload, difficulty, and cost of card maintenance. Simultaneously, when multiple displays share multiple cards within the shared desktop, card consistency across different displays can be improved, thereby enhancing the user experience.

[0046] In this case, when the display screen is controlled by a host computer within the device, the card display method can be executed by the host computer. For example... Figure 2 When the device is a vehicle, the host is the host unit terminal (HUT) in the vehicle. The host terminal is connected to multiple displays. When each display is started, the host terminal can obtain the shared desktop of multiple displays and obtain the card information of at least one target card that the target display needs to display. Then, based on the card information, it controls the shared desktop to run on the target display.

[0047] Furthermore, when the display screen displays autonomously, the card display method can be executed by the display screen. Each display screen (i.e., the target display screen) can obtain the shared desktop of multiple display screens upon startup, and obtain the card information of at least one target card that the target display screen needs to display, and then run the shared desktop based on the card information.

[0048] See Figure 3 , Figure 3 This is a flowchart illustrating a card display method provided in an embodiment of this application.

[0049] like Figure 3 As shown, the method includes the following steps:

[0050] Step 301: When the target display in a multi-display setup starts up, obtain a shared desktop shared across the multi-display setup.

[0051] In this context, the target display screen can be any one or more of multiple displays, and the shared desktop includes multiple cards, which can be understood as the collection of all cards displayed on the multiple displays. For any one or more displays, the display screen can show all the cards on the shared desktop, a portion of the cards on the shared desktop, or none of the cards on the shared desktop, i.e., no cards on the display screen.

[0052] In one implementation, when the card display method is performed by the display screen, the shared desktop can be stored in the host, and each display screen can obtain the shared desktop from the host upon startup. Figure 2 When the device is a vehicle, the shared desktop can be stored in the host terminal. Any one or more of the central control screen, passenger screen, ceiling screen, armrest screen and head-up display (i.e. target display screen) can obtain the shared desktop from the host terminal when the device is started.

[0053] In another implementation, when the card display method is performed by the display screen, the shared desktop can be stored on each display screen. For example... Figure 2The central control screen, passenger screen, ceiling-mounted screen, armrest screen, and head-up display can each store a shared desktop. Each display can access the locally stored shared desktop upon startup. Alternatively, the shared desktop can be stored on one of the displays, for example, the central control screen. When the central control screen (i.e., the target display) starts up, it can access the locally stored shared desktop, and the passenger screen and other displays can access the shared desktop from the central control screen upon startup.

[0054] In one implementation, when the card display method is performed by the host, the shared desktop can be stored on the host. The host can retrieve the locally stored shared desktop when each display is started. Alternatively, the shared desktop can be stored on one of the displays, and the host can retrieve the shared desktop from the display storing the shared desktop when each display is started. Alternatively, the shared desktop can also be stored on a server. When each display is started, the host can establish a communication connection with the server and retrieve the shared desktop from the server.

[0055] It should be understood that the above are merely illustrative examples, and the methods for obtaining a shared desktop may include, but are not limited to, the examples above.

[0056] Step 302: Obtain card information for at least one target card that the target display screen needs to display.

[0057] In one implementation, the target card's card information may include the target card's package name, which is the package name of the card's application in the operating system, used to uniquely identify a card; different cards have different package names. For each display screen, the card information of each card to be displayed on the screen can be pre-configured and stored. When the target display screen starts up, the card information of the target cards pre-configured and stored for the target display screen can be retrieved.

[0058] like Figure 2 If the shared desktop includes cards A, B, C, and D, and only cards A and B need to be displayed on the central control screen, then the card information configured for the central control screen includes the card package name of card A and the card package name of card B.

[0059] For example, when the card display method is executed by a display screen, the card information of the cards to be displayed on each display screen can be stored in the display screen. Taking a central control screen as an example, the card package name of card A and the card package name of card B can be stored in the central control screen. When the central control screen starts, it can obtain the locally stored card package names of card A and card B, at which point card A and card B are the target cards. Alternatively, the card information can also be stored in the host terminal. Taking a central control screen as an example, the card package name of card A and the card package name of card B corresponding to the central control screen can be stored in the host terminal. When the central control screen starts, it can obtain the card package names of card A and card B pre-stored for the central control screen from the host terminal.

[0060] For example, when the card display method is executed by a host in the device, the card information for each card that needs to be displayed on each screen can be stored in the host. Figure 2 As shown, for the central control screen, the host terminal can store the card package name of card A and the card package name of card B. For other displays, the host terminal can store the card information corresponding to those displays. When the central control screen starts up, the host terminal can retrieve the locally stored card package names of card A and card B.

[0061] It should be understood that the above are merely illustrative examples, and the specific methods for obtaining the card information of the target card to be displayed on the target display screen may include, but are not limited to, the examples above.

[0062] Step 303: Run a shared desktop on the target display screen based on the card information so that the target display screen shows the target card.

[0063] In this embodiment, after obtaining the card information of the shared desktop and the target card, the shared desktop can be run on the target display screen based on the card information of the target card. At this time, the shared desktop can display the target card. Referring to the above example, when the card display method is executed by the display screen, when the central control screen starts up, after obtaining the shared desktop and the card package name of card A and card package name of card B, the central control screen can run the shared desktop. Simultaneously, it can create a card instance A of card A in the running shared desktop using the card package name of card A, and a card instance B of card B in the running shared desktop using the card package name of card B, so as to display card A and card B on the central control screen.

[0064] Based on the above example, when the card display method is executed by the host, when the central control screen starts up, after the host terminal obtains the shared desktop and the card package name of card A and card package name of card B, the host can control the central control screen to run the shared desktop. At the same time, it can create card instance A of card A in the running shared desktop using the card package name of card A, and create card instance B of card B in the running shared desktop using the card package name of card B, so as to display card A and card B on the central control screen.

[0065] Optionally, when creating a card instance, a unique card instance identifier can be set for each card instance to distinguish and manage card instances of the same card displayed on different displays through the unique card instance identifier.

[0066] like Figure 2 As shown, both the central control screen and the passenger screen in the vehicle display cards A and B. If the central control screen starts first and the passenger screen starts later, when the central control screen starts, it creates a card instance A1 for card A in the shared desktop running on the central control screen and sets a unique card instance identifier ID1 for card instance A1. It also creates a card instance B1 for card B and sets a unique card instance identifier ID2 for card instance B1. When the passenger screen starts, it creates a card instance A2 for card A in the shared desktop running on the passenger screen and sets a unique card instance identifier ID3 for card instance A2. It also creates a card instance B2 for card B and sets a unique card instance identifier ID4 for card instance B2. Card instance identifiers ID1, ID2, ID3, and ID4 are four different card instance identifiers.

[0067] In this way, cards on different displays can be distinguished and managed based on the card instance identifier of each card instance. For example, if card A needs to be deleted from the central control screen, card instance A1 can be deleted based on its card instance identifier ID1, while card instance A2 is retained.

[0068] In this embodiment, a shared desktop is configured for multiple displays on a device. The shared desktop includes multiple cards that can be adapted to each display. When the target display starts, the shared desktop of the multiple displays is obtained, along with the card information of the target card that needs to be displayed on the target display. Then, based on the card information, the shared desktop is run on the target display, causing the target display to display the target card. For devices with multiple displays, only one shared desktop needs to be developed, along with a certain number of cards for the shared desktop. Compared to developing cards separately for each display, this significantly reduces the workload in the development process and improves development efficiency.

[0069] Furthermore, during later maintenance, only multiple cards within the shared desktop need to be maintained, significantly reducing the workload, difficulty, and cost of maintenance. Additionally, when multiple displays share multiple cards within the shared desktop, the consistency of cards across different displays is improved, thereby enhancing the user experience.

[0070] Optionally, the card information includes the target card's package name and card instance identifier. Based on this card information, a shared desktop is run on the target display, including:

[0071] Run a shared desktop on the target display screen;

[0072] In the running shared desktop, a card instance of the target card is created based on the target card's package name and card instance identifier.

[0073] In one implementation, when configuring and storing card information for the display screen in advance, a unique card package name and a unique card instance identifier can be configured for each card. For example, both the central control screen and the passenger screen display card A and card B. The card information configured for the central control screen includes the card information for card A and the card information for card B. Moreover, the card information for card A includes the card package name and card instance identifier ID1, and the card information for card B includes the card package name and card instance identifier ID2. The card information configured for the passenger screen includes the card information for card A and the card information for card B. Moreover, the card information for card A includes the card package name and card instance identifier ID3, and the card information for card B includes the card package name and card instance identifier ID4.

[0074] When the central control screen starts, the obtained card information includes the card package name and card instance identifier ID1 of card A, and the card package name and card instance identifier ID2 of card B. When running shared desktop in the central control screen, a card instance can be created based on the card package name of card A, and the card instance identifier ID1 can be used as the identifier of the card instance. Similarly, a card instance can be created based on the card package name of card B, and the card instance identifier ID2 can be used as the identifier of the card instance.

[0075] Similarly, when the passenger screen is activated, the obtained card information includes the card package name and card instance identifier ID3 for card A, and the card package name and card instance identifier ID4 for card B. When running the shared desktop in the passenger screen, a card instance can be created based on the card package name of card A, and the card instance identifier ID3 can be used as the identifier of that card instance; similarly, a card instance can be created based on the card package name of card B, and the card instance identifier ID4 can be used as the identifier of that card instance.

[0076] In this embodiment, the card information includes the target card's package name and card instance identifier. When running a shared desktop on the target display screen, a card instance of the target card is created based on the target card's package name and card instance identifier. This allows for the rapid creation of a card instance of the target card in the shared desktop, thereby improving card display efficiency.

[0077] Optionally, the card information includes the target card's package name, and the shared desktop is run on the target display based on the card information, including:

[0078] Determine the card instance identifier of the third card; wherein, the third card is the card displayed on other displays that are in operation among multiple displays;

[0079] Run a shared desktop on the target display screen;

[0080] In the running shared desktop, a card instance of the target card is created based on the target card's card package name, and a unique card instance identifier is set for the card instance; the card instance identifier of the target card is different from the card instance identifier of the third card.

[0081] In one implementation, when the card information only includes the card package name and not the card instance identifier, when creating a card instance of the target card, a unique card instance identifier can be set for the target card based on the card instance identifier of the card displayed on another running display (i.e., the third card) among multiple displays. Then, a card instance is created for the target card based on the card package name and the card instance identifier.

[0082] like Figure 2 As shown, the central control screen and passenger screen in the vehicle are already running. Both the central control screen and passenger screen display cards A and B. Therefore, the third card includes cards A and B. Card A has card instance identifiers ID1 and ID3, and card B has card instance identifiers ID2 and ID4. If the ceiling-mounted screen is activated and running a shared desktop within it, if the ceiling-mounted screen needs to display card A, it can first assign a unique card instance identifier ID5 to the card instance of card A on the ceiling-mounted screen based on card instance identifiers ID1, ID3, ID2, and ID4. Card instance identifier ID5 is different from all of these identifiers. Then, a card instance of card A can be created in the shared desktop running on the ceiling-mounted screen, and card instance identifier ID5 can be set as the card instance identifier for that card instance.

[0083] In this embodiment of the application, based on the card instance identifier of the card displayed on other displays that are in operation among multiple displays, the card instance identifier of the target card is set, and the card instance of the target card is created based on the set card instance identifier. This allows the same card to be displayed on multiple displays based on the card package name.

[0084] Optionally, obtaining card information for at least one target card that the target display screen needs to display includes:

[0085] Determine whether at least one pre-stored card configuration includes the target card configuration for the target display screen;

[0086] If the target card configuration is included, the card information is obtained from the target card configuration.

[0087] In one implementation, for each display screen of the device, a corresponding card configuration can be pre-set for each display screen. The card configuration includes the card package name and card instance identifier of the cards to be displayed on the display screen. Simultaneously, the card configuration for each display screen can be stored based on the screen identifier of the display screen.

[0088] like Figure 2 As shown, card configurations can be set for the central control screen, passenger screen, ceiling-mounted screen, armrest screen, and head-up display. Each display's card configuration includes the card package name and card instance identifier for the cards to be displayed. Taking the central control screen as an example, if card A and card B need to be displayed on the central control screen, the card package name and card instance identifier for card A, and the card package name and card instance identifier for card B, can be set in the central control screen's card configuration. Similarly, corresponding card configurations can be set for other displays. Each card instance identifier is unique across all card configurations. Then, the card configuration for each display can be stored in the host terminal based on the screen identifier of each display.

[0089] When the card display method is executed by the host terminal, upon startup of the target display screen, the host terminal can determine from multiple pre-stored card configurations whether a card configuration for the target display screen (i.e., the target card configuration) is stored, based on the screen identifier of the target display screen. If a target card configuration for the target display screen is pre-stored, the host terminal obtains the card package name and card instance identifier from the target card configuration, and then creates the corresponding card instance in the shared desktop running on the target display screen based on the obtained card package name and card instance identifier. Conversely, if no card configuration for the target display screen is pre-stored, it is determined that no cards need to be displayed on the target display screen, and the shared desktop can be run directly on the target display screen.

[0090] When the card display method is executed by the display screen, upon startup of the target display screen, it can first send a data request, including its screen identifier, to the host terminal. After receiving the data request, if the host terminal determines that a target card configuration corresponding to the screen identifier in the data request exists among multiple card configurations, it sends the target card configuration to the target display screen. Correspondingly, the target display screen obtains the card package name and card instance identifier from the received target card configuration, and then creates the corresponding card instance in the shared desktop running on the target display screen based on the obtained card package name and card instance identifier. Conversely, if no target card configuration corresponding to the screen identifier in the data request exists among multiple card configurations, the host terminal can send a notification message to the target display screen. Correspondingly, upon receiving the notification message, the target display screen determines that it does not need to display cards and can directly run the shared desktop on the target display screen.

[0091] Optionally, the card configuration may only include the card package name of the cards that need to be displayed on the screen. When running a shared desktop on the screen based on the card information in the target card configuration, a card instance is created for the target card, and a unique card instance identifier is created for the target card's card instance based on the card instance identifier of the third card.

[0092] In this embodiment, card configuration is set for the cards on the display screen, enabling the display screen to create card instances based on the card information in the card configuration during startup, and then display the cards based on the card instances. In this way, the display screen can be flexibly configured to display the cards that need to be shown through the card configuration settings.

[0093] Optionally, the card information includes the target card's package name and card instance identifier, and the method may further include:

[0094] If the target card configuration is not included in at least one card configuration, then a new card instance identifier is set for each of the multiple cards based on the card instance identifiers of the multiple cards in at least one card configuration.

[0095] Create the target card configuration based on the card package name of each card in the multiple cards and the new card instance identifier.

[0096] In one implementation, if it is determined that at least one pre-stored card configuration does not include a target card configuration for the target display, all cards present in the shared desktop can be used as target cards. In this case, a new card instance identifier can be set for each target card based on the card instance identifier of each card in other card configurations. Then, a target card configuration can be created for the target display, including the card package name of each card present in the shared desktop, and the new card instance identifier for each card.

[0097] Based on the above example, the shared desktop includes cards A, B, C, and D. When the central control screen starts, if it is determined that the central control screen's card configuration is not included in multiple card configurations, a new card configuration (i.e., the target card configuration) can be created for the central control screen. This card configuration includes the card package names of card A, card B, card C, and card D. Simultaneously, all card instance identifiers included in other card configurations can be obtained. Based on the obtained card instance identifiers, a corresponding card instance identifier is set for the card package names of card A, card B, card C, and card D in the created card configuration. Each card instance identifier is unique and different from the other card instance identifiers.

[0098] Optionally, the device may store screen identifiers for each display screen that the device can connect to. When it is determined that at least one card configuration does not include a target card configuration, it can be determined whether the screen identifier of the target display screen is a pre-stored screen identifier. If the screen identifier of the target display screen is a pre-stored screen identifier, the target display screen is determined to be a valid display screen, and a target card configuration can be created for the target display screen. Conversely, if the screen identifier of the target display screen is not a pre-stored screen identifier, the target display screen is determined to be an invalid display screen, and a target card configuration is not created for the target display screen.

[0099] In this embodiment of the application, when the card configuration of the target display screen is not included in at least one pre-stored card configuration, a card configuration is created for the target display screen based on the card instance identifiers of multiple cards in the pre-stored card configuration. This allows the card configuration to be automatically set for the target display screen when it is first connected to the device.

[0100] Optionally, after running the shared desktop on the target display based on the card information, the method may further include:

[0101] If a deletion instruction for the first card is received, the card information of the first card included in the target card configuration is deleted; wherein, the first card is a card in at least one target card.

[0102] And / or, if an instruction to add a second card is received, the card information of the second card is added to the target card configuration; wherein, the second card is another card among multiple cards besides the target card.

[0103] In one implementation, after the target display screen is powered on, when a user needs to delete a target card (i.e., the first card) displayed on the target display screen, they can input a deletion command through the target display screen. For example, regarding card A displayed on the central control screen, when a user needs to delete card A from the central control screen, they can perform a deletion operation on card A by inputting a deletion command to the central control screen. At this time, the central control screen deletes the card instance of card A from the shared desktop and sends a deletion request to the host terminal, the deletion request including the card package name of card A.

[0104] Correspondingly, after receiving the deletion request, the host terminal can determine the central control screen's card configuration from multiple stored card configurations and delete the card information for card A included in the central control screen's card configuration. Thus, when the central control screen starts up next time, its card configuration will not contain card information for card A, and card A will not be displayed when the central control screen runs shared desktop.

[0105] In one implementation, after the target display screen is powered on, if a user needs to add another card (i.e., a second card) to the target display screen when it is not currently displayed, the user can input an add command into the target display screen. For example, after the central control screen is powered on, if card D needs to be added to the display screen, the user can input an add command into the central control screen through the shared desktop running on the central control screen. The add command includes the card package name of card D. After receiving the add command, the central control screen sets up a card instance for card D based on the card package name of card D included in the add command, and assigns a unique card instance identifier to this card instance. At the same time, the central control screen can send an add request to the host terminal, the add request including the card package name and card instance identifier of card D.

[0106] Correspondingly, after receiving the add request, the host terminal can determine the card configuration of the central control screen from multiple stored card configurations, and add the card information of card D, namely the card package name and card instance identifier of card D, to the card configuration of the central control screen. In this way, when the central control screen starts up next time, the card information of card D is included in the card configuration of the central control screen, so that the central control screen can display card D.

[0107] It should be understood that the above are merely illustrative examples, and the specific input methods for deletion and addition commands may include, but are not limited to, the examples above.

[0108] In this embodiment of the application, when adding and / or deleting cards on the display screen, the card information in the corresponding card configuration of the display screen is updated synchronously, so that the display screen can automatically add and / or delete cards on the next startup, which makes it convenient for users to flexibly set the cards on the display screen according to their needs.

[0109] Optionally, a shared desktop across multiple displays can be acquired, including:

[0110] Determine the screen identifier of the target display screen;

[0111] When the target display is determined to be one of multiple displays based on the screen identifier, the shared desktop is obtained.

[0112] In one implementation, the device can pre-store screen identifiers for each display screen of the connectable device. When the target display screen is started, it can be determined whether the target display screen's screen identifier is a pre-stored screen identifier. If the target display screen's screen identifier is determined to be a pre-stored screen identifier, then the target display screen is determined to be a valid display screen, and a shared desktop can be acquired and run on the target display screen. Conversely, if the target display screen's screen identifier is not a pre-stored screen identifier, then the target display screen is determined to be an invalid display screen, and a shared desktop is not acquired or run on the target display screen.

[0113] like Figure 2 As shown, the screen identifier of each display screen in the vehicle can be pre-stored in the host terminal. When the host terminal detects that any one or more displays screens are activated, it retrieves the screen identifier of the display screen from the display screen. If the screen identifier is determined to be one of at least one pre-stored screen identifiers, the activated display screen is determined to be a valid display screen, and steps 301-203 are executed. If the screen identifier is determined not to be one of at least one pre-stored screen identifiers, the activated display screen is determined to be an invalid display screen, and steps 301-303 are not executed.

[0114] In this embodiment, before launching the display screen based on the shared desktop, the display screen is verified by the screen identifier of the display screen. After successful verification, the display screen is launched based on the shared desktop, which enables secure management of the device's display screen and improves the device's security.

[0115] Optionally, before running the shared desktop on the target display based on the card information, the method may further include:

[0116] Obtain the desktop property configuration of the target display screen;

[0117] Replace the desktop properties configuration of the shared desktop with the desktop properties configuration of the target display.

[0118] Desktop property configuration can include desktop property information such as desktop wallpaper, theme, and the order in which applications are displayed on the desktop, but is not limited to these.

[0119] In one implementation, the shared desktop has a basic desktop attribute configuration. When the shared desktop is running on a display, if the user adjusts the desktop attribute configuration, the device can save the adjusted configuration. The saved configuration can be retrieved the next time the display is started. Then, before running the shared desktop on the target display, the saved configuration can replace the basic desktop attribute configuration in the shared desktop. This preserves the user's adjustments to the desktop attributes, allowing users to customize the desktop on each display according to their needs.

[0120] In another implementation, a separate desktop attribute configuration can be set for each display screen in the device, and the corresponding desktop attribute configuration can be stored in the device. When the target display screen starts up, the desktop attribute configuration of the target display screen can be obtained from at least one pre-stored desktop attribute configuration. Subsequently, before running the shared desktop on the target display screen, the obtained desktop attribute configuration can replace the basic desktop attribute configuration in the shared desktop.

[0121] Furthermore, after running shared desktop on a display, if the user adjusts the desktop properties, the adjusted properties can be saved to the desktop's property configuration. This preserves the user's adjustments to the desktop properties, allowing them to be used to control the desktop properties the next time the display is started.

[0122] In this embodiment, a corresponding desktop attribute configuration is set for the display screen, and the desktop attribute configuration in the shared desktop is replaced by the desktop attribute configuration of the display screen. The desktop in each display screen can be adjusted differently according to the needs.

[0123] See Figure 4 , Figure 4 This is a schematic diagram of the structure of a card display device provided in an embodiment of this application.

[0124] like Figure 4 As shown, the device 400 is disposed in a device having multiple displays, and the device includes:

[0125] The acquisition module 401 is used to acquire a shared desktop shared by the multiple displays when the target display among the multiple displays is started, the shared desktop including multiple cards;

[0126] The acquisition module 401 is further configured to acquire card information of at least one target card that the target display screen needs to display; wherein, the target card is one of the plurality of cards;

[0127] The running module 402 is used to run the shared desktop on the target display screen based on the card information, so that the target display screen displays the target card.

[0128] Optionally, the acquisition module 401 is specifically used to determine whether the target card configuration of the target display screen is included in at least one pre-stored card configuration; if the target card configuration is included, the card information is acquired from the target card configuration.

[0129] Optionally, the device 400 further includes an adjustment module, configured to, after the shared desktop is run on the target display screen based on the card information, delete the card information of the first card included in the target card configuration if a deletion instruction for the first card is received; wherein the first card is a card among the at least one target card; and / or, if a addition instruction for the second card is received, add the card information of the second card to the target card configuration; wherein the second card is another card among the plurality of cards besides the target card.

[0130] Optionally, the card information includes the package name and card instance identifier of the target card. The device 400 further includes a configuration module, configured to, if the target card configuration is not included in the at least one card configuration, set a new card instance identifier for each of the plurality of cards based on the card instance identifiers of the plurality of cards in the at least one card configuration; and create the target card configuration based on the package name and the new card instance identifier of each of the plurality of cards.

[0131] Optionally, the card information includes the target card's package name and card instance identifier, and the running module 402 is specifically used to run the shared desktop on the target display screen; in the running shared desktop, a card instance of the target card is created based on the target card's package name and card instance identifier.

[0132] Optionally, the card information includes the package name of the target card, and the running module 402 determines the card instance identifier of the third card; wherein, the third card is a card displayed on another display screen that is in operation among the plurality of display screens; the shared desktop is run on the target display screen; in the running shared desktop, a card instance of the target card is created based on the package name of the target card, and a unique card instance identifier is set for the card instance; wherein, the card instance identifier of the target card is different from the card instance identifier of the third card.

[0133] Optionally, the acquisition module 401 is specifically used to determine the screen identifier of the target display screen; when it is determined based on the screen identifier that the target display screen belongs to one of the plurality of display screens, the shared desktop is acquired.

[0134] Optionally, the acquisition module 401 is further configured to acquire the desktop attribute configuration of the target display screen before running the shared desktop on the target display screen based on the card information; and replace the desktop attribute configuration of the shared desktop with the desktop attribute configuration of the target display screen.

[0135] Figure 5 This is a schematic diagram of the structure of a device provided in an embodiment of this application.

[0136] For example, such as Figure 5 As shown, the device 500 includes a memory 501 and a processor 502, wherein the memory 501 stores executable program code 5011, and the processor 502 is used to call and execute the executable program code 5011 to perform a card display method.

[0137] Furthermore, embodiments of this application also protect a card display device, which may include a memory and a processor, wherein the memory stores executable program code, and the processor is used to call and execute the executable program code to perform a card display method provided in embodiments of this application.

[0138] This embodiment can divide the device into functional modules based on the above method example. For example, each module can correspond to a separate function, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware. It should be noted that the module division in this embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods.

[0139] It should be noted that all relevant content of each step involved in the above method embodiments can be referenced from the functional description of the corresponding functional module, and will not be repeated here.

[0140] It should be understood that the apparatus provided in this embodiment is used to execute the card display method described above, and therefore can achieve the same effect as the above implementation method.

[0141] When using integrated units, the device may include a processing module and a storage module. When applied to a workpiece, the processing module can be used to control and manage the workpiece's operations. The storage module can be used to support the execution of program code by the workpiece.

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

[0143] In addition, the device provided in the embodiments of this application may specifically be a chip, component or module. The chip may include a connected processor and a memory. The memory is used to store instructions. When the processor calls and executes the instructions, the chip can execute a card display method provided in the above embodiments.

[0144] This embodiment also provides a readable storage medium storing executable program code. When the executable program code is run on the device, the device performs the above-described related method steps to implement a card display method provided in the above embodiment.

[0145] This embodiment also provides a program product that, when run on a device, causes the device to perform the aforementioned steps to implement a card display method provided in the above embodiment.

[0146] In this embodiment, the device, readable storage medium, program product, or chip are all used to execute the corresponding methods provided above. Therefore, the beneficial effects that can be achieved can be referred to the beneficial effects of the corresponding methods provided above, and will not be repeated here.

[0147] Through the above description of the embodiments, those skilled in the art will understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above 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.

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

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

Claims

1. A card display method characterized by comprising: The method is applied to a device with multiple display screens, and the method comprises the following steps: When a target display screen in the multiple display screens is started, a same shared desktop application pre-stored and shared by the multiple display screens is acquired, the shared desktop application comprising multiple cards; It is determined whether a target card configuration of the target display screen is included in at least one pre-stored card configuration; if the target card configuration is included, card information of at least one target card required to be displayed by the target display screen is acquired from the target card configuration; wherein the target card is a card in the multiple cards; The shared desktop application is run in the target display screen; When the card information comprises a card package name and a card instance identifier of the target card, a card instance of the target card is created in the running shared desktop application based on the card package name and the card instance identifier of the target card, so that the target display screen displays the target card; When the card information comprises the card package name of the target card but does not comprise the card instance identifier of the target card, a card instance identifier of a third card is determined; wherein the third card is a card displayed in another display screen in a running state in the multiple display screens; a card instance of the target card is created in the running shared desktop application based on the card package name of the target card, and a unique card instance identifier is set for the card instance, so that the target display screen displays the target card; wherein the card instance identifier of the target card is different from the card instance identifier of the third card.

2. The method of claim 1, wherein, The method further comprises the following steps: If a deletion instruction of a first card is received, the card information of the first card included in the target card configuration is deleted; wherein the first card is a card in the at least one target card; And / or, if an increase instruction of a second card is received, the card information of the second card is added in the target card configuration; wherein the second card is a card other than the target card in the multiple cards.

3. The method of claim 1, wherein, The method further comprises the following steps: If the target card configuration is not included in the at least one card configuration, a new card instance identifier is set for each card in the multiple cards based on the card instance identifiers of the multiple cards in the at least one card configuration respectively; The target card configuration is created based on the card package name and the new card instance identifier of each card in the multiple cards.

4. The method of claim 1, wherein, The acquisition of the same shared desktop application pre-stored and shared by the multiple display screens comprises the following steps: The screen identifier of the target display screen is determined; When it is determined based on the screen identifier that the target display screen belongs to one of the multiple display screens, the shared desktop application is acquired.

5. The method of any one of claims 1-4, wherein, Before the shared desktop application is run in the target display screen, the method further comprises the following steps: The desktop attribute configuration of the target display screen is acquired; The desktop attribute configuration of the target display screen is used to replace the desktop attribute configuration of the shared desktop application.

6. A card display device characterized by comprising: The device is arranged in a device with multiple display screens, and the device comprises the following components: An obtaining module is configured to, when a target display screen in the plurality of display screens is started, obtain a pre-stored shared desktop application that is shared by the plurality of display screens, the shared desktop application including a plurality of cards; The obtaining module is further configured to determine whether a target card configuration of the target display screen is included in at least one pre-stored card configuration, and if the target card configuration is included, obtain card information of at least one target card that needs to be displayed by the target display screen from the target card configuration, wherein the target card is a card in the plurality of cards; An executing module is configured to execute the shared desktop application in the target display screen, and when the card information includes a card package name and a card instance identifier of the target card, create a card instance of the target card based on the card package name and the card instance identifier of the target card in the executed shared desktop application, so that the target display screen displays the target card; when the card information includes the card package name of the target card but does not include the card instance identifier of the target card, determine a card instance identifier of a third card, wherein the third card is a card displayed in another display screen in the plurality of display screens that is in a running state; create a card instance of the target card based on the card package name of the target card in the executed shared desktop application, and set a unique card instance identifier for the card instance, so that the target display screen displays the target card; wherein the card instance identifier of the target card is different from the card instance identifier of the third card.

7. An apparatus, comprising: The device includes: a memory configured to store executable program code; a processor configured to call and execute the executable program code from the memory, so that the device performs the method of any one of claims 1 to 5.

Images