Application market multi-screen cooperative processing method and device, electronic equipment and storage medium

Abstract

The embodiment of the invention relates to the technical field of Internet of Vehicles, and discloses an application market multi-screen cooperative processing method and device, electronic equipment and a storage medium. The method comprises the following steps: in response to an application market starting instruction of a user, sending a data acquisition request to a network layer based on vehicle machine parameters to acquire total data of an application market; after the total data is acquired, the GreenDao layer is utilized to store the total data in a local vehicle machine; constructing a data list of each vehicle machine screen based on the total data; and monitoring the corresponding data list through the Presenter layer of each vehicle machine screen, so as to render the UI display of the application market based on the data list at least when the data list exists. According to the method, efficient transmission of data can be achieved, it is guaranteed that all vehicle-mounted terminal screens obtain latest data in time, and the consistency and accuracy of UI display of the application market are guaranteed.

Description

Technical Field

[0001] This invention relates to the field of vehicle networking technology, and in particular to a multi-screen collaborative processing method, device, electronic device, and storage medium for the application market. Background Technology

[0002] Currently, in the fields of multi-screen display and application distribution, existing technical solutions still have many shortcomings that need improvement in practical implementation:

[0003] Resource consumption drawbacks of multi-process, multi-screen display: Existing solutions typically employ a multi-process mode for multi-screen display. This mode consumes a lot of memory and CPU resources, which can easily lead to excessive device load and overall performance degradation. Furthermore, when installing app stores on the in-vehicle infotainment system, an app store is installed on each screen, further wasting the system's memory.

[0004] The problem of wasted resources in duplicate storage of Android application packages (APKs): For APK installation packages with the same package name, existing solutions often download and store them repeatedly, which not only causes unnecessary consumption of storage resources, but also increases the additional network bandwidth usage.

[0005] Insufficient synchronization of multi-screen status and operation: In existing multi-screen systems, the page status and user operation of each screen are prone to being out of sync, resulting in poor consistency of user experience during multi-screen interaction.

[0006] Lack of adaptability in multi-screen data distribution: Existing technologies fail to achieve orderly data distribution across multiple screens, which can easily lead to chaotic data transmission and low distribution efficiency, affecting the reliability of data interaction in multi-screen systems. Summary of the Invention

[0007] The purpose of this invention is to provide a method, apparatus, electronic device and storage medium for multi-screen collaboration processing in the application market, so as to at least solve the problems of high resource consumption and poor experience of existing multi-screen collaboration processing solutions in the application market, thereby reducing resource consumption and improving user experience.

[0008] To address the aforementioned technical problems, in a first aspect, the present invention provides a method for multi-screen collaboration in an application market, comprising at least:

[0009] In response to the user's command to open the application market, a data acquisition request is sent to the network layer based on the vehicle system parameters to obtain the full data of the application market;

[0010] After acquiring the full data, the GreenDao layer is used to store the full data locally in the vehicle system.

[0011] A data list for each vehicle infotainment screen is constructed based on the full data.

[0012] The presenter layer of each vehicle screen listens to the corresponding data list so that, at least when the data list exists, the user interface (UI) display of the application market is rendered based on the data list.

[0013] Optionally, the vehicle system parameters include at least one of the following: vehicle system VIN code, ROM version number, and DB version number;

[0014] The full data includes at least one of the following: vehicle screen identifier, display screen location, application ID, application package download address, icon download address, application size, developer information, application description, and application status.

[0015] Optionally, constructing a data list for each vehicle infotainment screen based on the full data specifically includes:

[0016] Set the vehicle infotainment screen identifier as the list key;

[0017] The data list corresponding to the vehicle infotainment screen is constructed based on each of the list primary keys.

[0018] Optionally, after listening to the corresponding data list through the Presenter layer of each of the vehicle infotainment screens, and rendering the user interface (UI) display of the application market based on the data list, at least when the data list exists, the method further includes...

[0019] Set up a UI control manager and use the UI control manager to continuously monitor the state changes of each UI control;

[0020] When the state of any of the UI controls changes, the UI control manager sends a UI control change instruction to each of the vehicle infotainment screens to synchronize the state of the UI controls.

[0021] Optionally, it may also include:

[0022] In response to the self-running state of the vehicle infotainment application, determine whether the self-running state satisfies the pop-up event;

[0023] If the conditions are met, a pop-up window will be triggered, and a synchronized pop-up window marker will be added to the current interface;

[0024] A pop-up manager is established, and the pop-up and the synchronization pop-up marker are synchronized to the application market corresponding to each vehicle screen using the pop-up manager.

[0025] Optionally, after establishing a pop-up manager and using the pop-up manager to synchronize the pop-up and the synchronization pop-up marker to the application market corresponding to each of the vehicle infotainment screens, the method further includes:

[0026] In response to the disappearance of the pop-up event, the pop-up and the synchronized pop-up marker in the application market of each vehicle screen are removed by the pop-up manager.

[0027] Secondly, the present invention also provides an application market multi-screen collaborative processing device, comprising at least:

[0028] The data acquisition module is used to respond to the user's application market opening command, and send a data acquisition request to the network layer based on the vehicle system parameters to obtain the full data of the application market;

[0029] The data storage module is used to store the full data locally in the vehicle system using the GreenDao layer after the full data is acquired.

[0030] The list construction module is used to construct a data list for each vehicle screen based on the full data.

[0031] The UI rendering module is used to listen to the corresponding data list through the Presenter layer of each of the vehicle screens, so as to render the user interface (UI) display of the application market based on the data list, at least when the data list exists.

[0032] Optionally, the vehicle system parameters include at least one of the following: vehicle system VIN code, ROM version number, and DB version number;

[0033] The full data includes at least one of the following: vehicle screen identifier, display screen location, application ID, application package download address, icon download address, application size, developer information, application description, and application status.

[0034] Thirdly, the present invention also provides an electronic device, including a memory and a processor, wherein the memory stores a computer program executable on the processor, and the processor executes the program to implement the steps of the application market multi-screen collaboration processing method described in any of the first aspects.

[0035] Fourthly, the present invention also provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the steps of the application market multi-screen collaboration processing method described in any one of the first aspects.

[0036] The technical solution provided in this embodiment of the invention firstly responds to the user's application market activation command by sending a data acquisition request to the network layer based on the vehicle system parameters to obtain the full data of the application market; further, after obtaining the full data, the GreenDao layer is used to store the full data locally in the vehicle system; further, a data list for each vehicle system screen is constructed based on the full data; finally, the Presenter layer of each vehicle system screen listens to the corresponding data list so that, at least when the data list exists, the user interface (UI) display of the application market is rendered based on the data list.

[0037] Therefore, this invention, on the one hand, constructs a data list for each vehicle infotainment screen based on the full dataset, ensuring accurate matching between data and the screen, avoiding data redundancy, and reducing resource consumption. On the other hand, by monitoring the corresponding data list through the presenter layer of the vehicle infotainment screen, this invention enables efficient data transmission, ensuring that each screen receives the latest data in a timely manner, and guaranteeing the consistency and accuracy of the application market UI display. Attached Figure Description

[0038] Figure 1 This is a flowchart of an application market multi-screen collaboration processing method provided by an embodiment of the present invention;

[0039] Figure 2 This is a data distribution architecture diagram for multi-screen demand transformation provided by an embodiment of the present invention;

[0040] Figure 3 This is a schematic diagram of the structure of an application market multi-screen collaborative processing device provided in an embodiment of the present invention;

[0041] Figure 4 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present invention. Detailed Implementation

[0042] To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0043] The terminology used in the embodiments of this application is for the purpose of describing particular embodiments only and is not intended to limit the application. The singular forms “a,” “said,” and “the” used in the embodiments of this application and the appended claims are also intended to include the plural forms, and “multiple” generally includes at least two unless the context clearly indicates otherwise.

[0044] It should be understood that the term "and / or" used in this article 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. Additionally, the character " / " in this article generally indicates that the preceding and following related objects have an "or" relationship.

[0045] It should be understood that although the terms first, second, third, etc., may be used in the embodiments of this application, these descriptions should not be limited to these terms. These terms are only used to distinguish the descriptions. For example, first may also be referred to as second without departing from the scope of the embodiments of this application, and similarly, second may also be referred to as first.

[0046] Depending on the context, the words “if” or “suppose” as used here can be interpreted as “when” or “in response to determination” or “in response to detection.” Similarly, depending on the context, the phrases “if determination” or “if detection (of the stated condition or event)” can be interpreted as “when determination” or “in response to determination” or “when detection (of the stated condition or event)” or “in response to detection (of the stated condition or event).”

[0047] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that an article or device that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such an article or device. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the article or device that includes said element.

[0048] It should be noted that any symbols and / or numbers present in the specification that are not marked in the accompanying drawings are not reference numerals.

[0049] Figure 1 This is a flowchart of an application market multi-screen collaborative processing method provided by an embodiment of the present invention. This embodiment is at least applicable to application market collaborative processing scenarios in vehicles with multiple in-vehicle screens. This application market multi-screen collaborative processing method can be, but is not limited to, executed by the application market multi-screen collaborative processing device in this embodiment of the present invention as the execution subject. This execution subject can be implemented in software and / or hardware. Figure 1 As shown, the multi-screen collaboration processing method of this application market includes at least the following steps:

[0050] S1. In response to the user's command to open the app store, a data acquisition request is sent to the network layer based on the vehicle's parameters to obtain the full data of the app store.

[0051] In this system, the user can be a passenger. The application market can be the application software market / center within the vehicle's central control unit. The trigger method for opening the application market can be that the user clicks the application market APP icon. The full data can be a large string of AppBean data. In one specific implementation, optionally, the vehicle system parameters include at least one of the following: vehicle system VIN code, ROM version number, and DB version number. The full data includes at least one of the following: vehicle system screen identifier, display screen position, application ID, application package download address, icon download address, application size, developer information, application description, and application status. The vehicle system VIN code is a unique identifier for the vehicle system. The ROM (Read-Only Memory) version number can be the version number of the read-only memory. The DB version number can be the version number of the database. The vehicle system screen identifier can be the ID of the vehicle system screen. The display screen position is used to indicate which multi-screen is being displayed on. The application ID can be the application identifier. The application package download address can be the URL for downloading the APK file. The icon download address can be the URL of the icon. The application size can be the download address of the installation package. Developer information and application description can include a brief introduction, developer information, and other details that describe the application and fully represent all the information about it. Application status can be the app's current state, such as whether it's open, installing, installing, downloading, download progress, and the number of retries in case of network errors. The network layer can be understood as a cloud layer.

[0052] S2. After acquiring all the data, use the GreenDao layer to store all the data locally in the vehicle system.

[0053] Among them, the GreenDAO layer is an open-source, lightweight, and fast ORM framework for Android that maps Java objects to an SQLite database (local to the vehicle's infotainment system). Figure 2 This is a data distribution architecture diagram for multi-screen requirement transformation provided by an embodiment of the present invention. See also: Figure 2 .

[0054] S3. Construct a data list for each vehicle infotainment screen based on the full data.

[0055] The data list can be in the format of a Map.<display,AppBeans> "display" indicates the vehicle infotainment screen number, such as display1, display2, etc. The vehicle infotainment screen can be a central control screen, a passenger-side screen, a rear-seat screen, etc. In another specific implementation, optionally, step S3 specifically includes:

[0056] (3-1) Set the vehicle screen identifier as the list primary key.

[0057] In this context, the primary key of a list can be understood as the identifier of the data list.

[0058] (3-2) Construct the data list corresponding to the vehicle screen based on the primary key of each list.

[0059] In this embodiment, the configuration allows all AppBean data for each screen corresponding to a data list to be displayed.

[0060] S4. Listen to the corresponding data list through the Presenter layer of each vehicle screen, so as to render the user interface (UI) display of the application market based on the data list, at least when the data list exists.

[0061] The Presenter layer is an operation layer used to execute specific functions and perform various data operations. Listening can be synchronous or asynchronous. Steps S1-S4 can be understood as a data distribution transformation process. The Presenter layer specifically includes MainPresenter and AppsPresenter. MainPresenter receives the data list of each AppBean based on the screen ID (screen identifier). AppsPresenter displays the application list for each screen. Different screen IDs are distributed to the corresponding AppBean data list by MainPresenter, and the data is further categorized for display on the homepage, showing the data list under each tab of each screen. UI display relies on... Figure 2 The View layer, or UI display layer, is used to display the data processed by AppsPresenter and to perform various UI displays and interactions. In another specific implementation, after step S4, the method includes:

[0062] (5) Set up the UI control manager and use the UI control manager to continuously monitor the state changes of each UI control.

[0063] Steps (5) and (6) can be understood as the transformation of the application store's state distribution. Before the transformation, there was only one state variable. During the specific transformation, a Map can be introduced to record the installation, uninstallation, and other states of each screen, which is used to synchronize the states of other screens. The state migration changes from a single line to a branching line, that is, one state corresponds to multiple screens. The UI control manager can be AppStateChangeManager, which contains a collection of OnAppStateChangeListener listeners for all screens and all locations. The state changes of UI controls can be displayed using a custom control. Custom controls have multiple states, corresponding to multiple states of the application.

[0064] (6) When the state of any UI control changes, use the UI control manager to send a UI control change instruction to each vehicle screen to synchronize the UI control state.

[0065] Understandably, when the buttons (progressButtons) corresponding to each application on each screen (Display0 and Display1) are initialized, they register listeners with AppStateChangeManager, taking the AppBean itself as input and the screen ID: display. AppStateChangeManager transmits the state change of a specific AppBean on a particular screen to the onStateChange method in the progressButton's listener. onStateChange sends UI control change instructions to each in-vehicle screen, and progressButton is responsible for changing the UI controls on all in-vehicle screens to the corresponding state. The principle of state change can be achieved by using the listener's overridden methods inside progressButton. The listener has two methods: onStateChange and onDownloadProgress, which change the state and progress respectively. When the state changes, such as from "Installing" to "Downloading," the onStateChange method in progressButton will modify the UI to the "Downloading" UI. Similarly, when the download progress changes, the onDownloadProgress method in progressButton will modify the numbers accordingly. It is understandable that this embodiment allows for downloading APK packages with the same package name only once, and installing them on different users, as needed. Therefore, the app download-related status is shared across multiple screens. In this state, the status is distributed to each screen via AppStateChangeManager. Other states, such as the installation state, are distributed to the View layer of the target screen, while other states, such as (installation / uninstallation), are the status of each screen. Thus, this embodiment allows for the installation of the app store app only on the central control screen of the vehicle's infotainment system, and the app store app on the central control screen is synchronized to every other screen, saving the memory space occupied by the app store app itself and further improving the storage space usage of the vehicle's infotainment system. On the other hand, when multiple screens need to download a specific app from the app store, this embodiment allows for downloading and installing the app only once on the central control screen, and then synchronizing the app to all screens, saving data usage. It is understood that at this point, the data and application status of the app store have been updated. If the user operates on the app store or the app store triggers a specific event, the status of the app store on each screen still needs to be synchronized. Therefore, in one specific implementation, the method provided in this embodiment may optionally further include:

[0066] (7-1) In response to the self-running state of the vehicle application, determine whether the self-running state meets the pop-up event.

[0067] The self-running state can be user-initiated actions, such as downloading / canceling a download: AppDownloadManager executes the download and implements the shared state migration of the App, cooperating with AppStateChangeManager to distribute the state to the View layer of each screen; installation / uninstallation: InstallManager sequentially executes the installation / uninstallation of the APK under each screen, and implements the screen state migration of the App, cooperating with AppStateChangeManager to distribute the state to the View layer of the corresponding screen. In addition to keeping the download progress and App state synchronized, pop-ups also need to be synchronized across multiple screens, such as download failures, self-updates, etc. For this purpose, this embodiment introduces GlobalDialogManager and the event bus DisplayEventBus to realize the synchronization of in-app pop-ups on each screen. It can be understood that steps (7-1) and (7-4) can be understood as the process of instruction synchronization modification.

[0068] (7-2) If the conditions are met, a pop-up window will be triggered and a synchronized pop-up window marker will be added to the current interface.

[0069] Specifically, a pop-up event can be a notification that needs to alert the user, such as a download failure or a self-update, and the app store is running in the foreground. It is understandable that pop-ups in other similar scenarios, such as self-update installation prompts or download failures, can be handled using the logic provided in this embodiment, that is, by incorporating global event notifications and global pop-up management based on the page's lifecycle.

[0070] (7-3) Set up a pop-up manager and use the pop-up manager to synchronize pop-ups and synchronized pop-up markers to the application market corresponding to each vehicle screen.

[0071] The synchronized pop-up flag is used to ensure that a pop-up notification is triggered even after the page is restored.

[0072] (7-4) In response to the disappearance of the pop-up event, the pop-up and synchronous pop-up markers in the application market of each vehicle screen are removed through the pop-up manager.

[0073] The technical solution provided in this embodiment firstly responds to the user's application market activation command by sending a data acquisition request to the network layer based on the vehicle's parameters to obtain the full data of the application market; further, after obtaining the full data, the GreenDao layer is used to store the full data locally in the vehicle's system; further, a data list for each vehicle screen is constructed based on the full data; finally, the Presenter layer of each vehicle screen listens to the corresponding data list so that, at least when the data list exists, the user interface (UI) display of the application market is rendered based on the data list.

[0074] Therefore, this embodiment, on the one hand, constructs a data list for each vehicle infotainment screen based on the full dataset, ensuring accurate matching between data and the screen, avoiding data redundancy, and reducing resource consumption. On the other hand, this embodiment, by monitoring the corresponding data list through the presenter layer of the vehicle infotainment screen, achieves efficient data transmission, ensuring that each screen receives the latest data in a timely manner, and guaranteeing the consistency and accuracy of the application market UI display.

[0075] Figure 3 This is a schematic diagram of the structure of an application market multi-screen collaborative processing device provided in an embodiment of the present invention. This embodiment is at least applicable to application market collaborative processing scenarios in vehicles with multiple in-vehicle screens. This application market multi-screen collaborative processing device can be implemented using software and / or hardware. Figure 3 As shown, the multi-screen collaboration processing device for this application market includes at least:

[0076] The data acquisition module 110 is used to respond to the user's application market opening command and send a data acquisition request to the network layer based on the vehicle system parameters to obtain the full data of the application market.

[0077] The data storage module 120 is used to store the full data locally in the vehicle system using the GreenDao layer after the full data is acquired.

[0078] List construction module 130 is used to construct a data list for each vehicle screen based on the full data.

[0079] The UI rendering module 140 is used to listen to the corresponding data list through the Presenter layer of each vehicle screen, so as to render the user interface (UI) display of the application market based on the data list, at least when the data list exists.

[0080] Optionally, the vehicle system parameters include at least one of the following: vehicle system VIN code, ROM version number, and DB version number.

[0081] The full data includes at least one of the following: vehicle screen identifier, display screen location, application ID, application package download address, icon download address, application size, developer information, application description, and application status.

[0082] Optionally, the list construction module 130 is specifically used for:

[0083] Set the vehicle screen identifier as the list primary key. Then, construct a data list for each vehicle screen based on its primary key.

[0084] Optionally, it also includes:

[0085] The state control module 150 is used to set up the UI control manager and continuously monitor the state changes of each UI control using the UI control manager; and, when the state of at least any UI control changes, to send a UI control change instruction to each vehicle screen using the UI control manager to synchronize the UI control state.

[0086] Optionally, it also includes:

[0087] The pop-up control module 160 is used to respond to the self-running state of the vehicle system application, determine whether the self-running state meets the pop-up event; and if the pop-up event is met, trigger the pop-up and add a synchronization pop-up marker to the current interface; and set up a pop-up manager and use the pop-up manager to synchronize the pop-up and synchronization pop-up marker to the application market corresponding to each vehicle system screen.

[0088] Optionally, the pop-up control module 160 is also used for:

[0089] In response to the disappearance of pop-up events, the pop-up manager removes pop-ups and synchronized pop-up markers from the app store on each vehicle infotainment screen.

[0090] The technical solution provided in this embodiment firstly, in response to the user's application market activation command, sends a data acquisition request to the network layer based on the vehicle's parameters through the data acquisition module to obtain the full data of the application market; further, after obtaining the full data, the data storage module uses the GreenDao layer to store the full data locally in the vehicle's system; further, the list construction module constructs a data list for each vehicle screen based on the full data; finally, the UI rendering module listens to the corresponding data list according to the Presenter layer of each vehicle screen, so as to render the user interface (UI) display of the application market based on the data list, at least when the data list exists.

[0091] Therefore, this embodiment, on the one hand, constructs a data list for each vehicle infotainment screen based on the full dataset, ensuring accurate matching between data and the screen, avoiding data redundancy, and reducing resource consumption. On the other hand, this embodiment, by monitoring the corresponding data list through the presenter layer of the vehicle infotainment screen, achieves efficient data transmission, ensuring that each screen receives the latest data in a timely manner, and guaranteeing the consistency and accuracy of the application market UI display.

[0092] This embodiment provides an electronic device. Figure 4 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present invention. See also: Figure 4 The electronic device 1000 includes a processor 1001 and a memory 1002. The memory 1002 stores computer-readable instructions. When the computer-readable instructions are executed by the processor 1001, the steps in any of the above-described application market multi-screen collaborative processing methods are performed. Through the above technical solution, the processor 1001 and the memory 1002 are interconnected and communicate with each other via a communication bus and / or other forms of connection mechanisms (not shown). The memory 1002 stores a processor-executable computer program. When the electronic device 1000 is running, the processor 1001 executes the computer program to perform the application market multi-screen collaborative processing method in any optional implementation of the above embodiments, to at least achieve the following functions: responding to the user's application market opening command, sending a data acquisition request to the network layer based on vehicle parameters to obtain the full data of the application market; after obtaining the full data, storing the full data locally in the vehicle using the GreenDao layer; constructing a data list for each vehicle screen based on the full data; and listening to the corresponding data list through the Presenter layer of each vehicle screen, so as to render the application market's user interface (UI) display based on the data list, at least when the data list exists.

[0093] This embodiment provides a computer-readable storage medium storing a computer program. When executed by a processor, the program implements the application market multi-screen collaborative processing method provided in all embodiments of this application: in response to a user's application market opening command, a data acquisition request is sent to the network layer based on vehicle system parameters to obtain the full data of the application market; after obtaining the full data, the full data is stored locally in the vehicle system using the GreenDao layer; a data list for each vehicle system screen is constructed based on the full data; and the corresponding data list is monitored through the Presenter layer of each vehicle system screen so as to render the application market's user interface (UI) display based on the data list, at least when the data list exists.

[0094] Any combination of one or more computer-readable media may be used. A computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. A computer-readable storage medium can be, for example—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples (a non-exhaustive list) of computer-readable storage media include: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this document, a computer-readable storage medium can be any tangible medium that contains or stores a program that can be used by or in connection with an instruction execution system, apparatus, or device.

[0095] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals may take various forms, including—but not limited to—electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, capable of transmitting, propagating, or transmitting programs for use by or in connection with an instruction execution system, apparatus, or device.

[0096] The program code contained on a computer-readable medium may be transmitted using any suitable medium, including—but not limited to—wireless, wire, optical fiber, RF, etc., or any suitable combination thereof.

[0097] Computer program code for performing the operations of this invention can be written in one or more programming languages ​​or a combination thereof. Programming languages ​​include object-oriented programming languages—such as Java, Smalltalk, and C++—as well as conventional procedural programming languages—such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0098] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for multi-screen cooperation processing in an application market, characterized in that, At least comprising: In response to the user's application market opening instruction, based on the vehicle parameter, the network layer sends a data acquisition request to acquire the full amount of data of the application market; After the full amount of data is acquired, the GreenDao layer is used to store the full amount of data in the vehicle local; Based on the full amount of data, the data list of each vehicle screen is constructed; Through the presenter layer of each vehicle screen, the corresponding data list is listened to, and based on the data list, the user interface UI of the application market is rendered and displayed at least when the data list exists.

2. The application market multi-screen cooperative processing method of claim 1, wherein, The vehicle parameter at least includes one of vehicle VIN code, ROM version number and DB version number; The full amount of data at least includes one of vehicle screen identification, display screen position, application ID, application package download address, icon download address, application size, developer information, application introduction and application state.

3. The application market multi-screen cooperative processing method of claim 1, wherein, The full amount of data is constructed based on the data list of each vehicle screen, specifically including: The vehicle screen identification is set as the list primary key; Based on each list primary key, the data list of the corresponding vehicle screen is constructed.

4. The application market multi-screen cooperative processing method of claim 1, wherein, After the presenter layer of each vehicle screen listens to the corresponding data list, and based on the data list, the user interface UI of the application market is rendered and displayed at least when the data list exists, it further includes Set up a UI control manager, and continuously listen to the state change of each UI control by using the UI control manager; At least when the state of any UI control changes, the UI control manager is used to send a UI control change instruction to each vehicle screen to synchronize the UI control state.

5. The application market multi-screen cooperative processing method of claim 4, wherein, Further comprising: In response to the self-running state of the vehicle application, it is judged whether the self-running state meets the pop-up window event; If it is satisfied, the pop-up window is triggered, and the synchronous pop-up window mark is added to the current interface; Set up a pop-up window manager, and use the pop-up window manager to synchronize the pop-up window and the synchronous pop-up window mark to the application market corresponding to each vehicle screen.

6. The application market multi-screen cooperative processing method of claim 5, wherein, After setting up the pop-up window manager and synchronizing the pop-up window and the synchronous pop-up window mark to the application market corresponding to each vehicle screen by using the pop-up window manager, it further includes: In response to the disappearance of the pop-up window event, the pop-up window and the synchronous pop-up window mark in the application market of each vehicle screen are eliminated by the pop-up window manager.

7. A multi-screen collaborative processing device for the application market, characterized in that, At least comprising: The data acquisition module is used to respond to the user's application market opening instruction, and based on the vehicle parameter, the network layer sends a data acquisition request to acquire the full amount of data of the application market; The data storage module is used to acquire the full amount of data after the full amount of data is acquired, and the GreenDao layer is used to store the full amount of data in the vehicle local; The list construction module is used to construct the data list of each vehicle screen based on the full amount of data; Through the presenter layer of each vehicle screen, the corresponding data list is listened to, and based on the data list, the user interface UI of the application market is rendered and displayed at least when the data list exists. A UI rendering module is configured to listen to the data list corresponding to each car machine screen through a presenter layer of the car machine screen, and render a user interface (UI) of the application market based on the data list at least when the data list exists.

8. The application market multi-screen cooperative processing apparatus of claim 7, wherein, The car machine parameters at least include one of a car machine VIN code, a ROM version number, and a DB version number. The full-amount data at least include one of a car machine screen identifier, a display screen position, an application ID, an application package download address, an icon download address, an application size, developer information, an application brief introduction, and an application state.

9. An electronic device comprising a memory and a processor, said memory storing a computer program operable on said processor, characterized in that, The processor implements the steps of the application market multi-screen cooperative processing method in any one of claims 1 to 6 when executing the program.

10. A computer-readable storage medium having stored thereon a computer program, characterized in that, The computer program implements the steps of the application market multi-screen cooperative processing method in any one of claims 1 to 6 when executed by the processor.

Images