Vehicle-mounted aggregation notification method and device based on Android system

Abstract

The invention relates to a vehicle-mounted aggregation notification method and device based on an Android system, and the method comprises the steps: starting a plurality of built-in service modules under the condition that the starting of a vehicle machine is detected; obtaining and processing a notification message of a corresponding channel through each service module; and uniformly managing the processed notification messages through a notification data management module, and aggregating and displaying the notification messages in a notification bar. The flexibility of notification message display can be improved.

Description

Technical Field

[0001] This application relates to the technical field of automobiles, and in particular, to an in-vehicle aggregation notification method and device based on the Android system. Background Art

[0002] With the deep integration of intelligent vehicles and Android intelligent devices, during driving, a driver needs to process notification information from multiple channels, including notifications from the Android system, applications, vehicle fault information, and push information from external service platforms. The system and each application package the data in a Notification class (Android system-level notification) and send it to the Android system, and the Android system displays each notification in the notification bar in chronological order.

[0003] Although the Android system can display notifications sent by multiple applications, the notification display method of the Android system is fixed and cannot be changed, which will cause a series of problems, such as uncontrollable notification message priorities, redundant notification messages, inability to view historical messages, etc., resulting in inflexible display of notification messages. Summary of the Invention

[0004] This application provides an in-vehicle aggregation notification method and device based on the Android system to solve the problem of inflexible display of notification messages.

[0005] In a first aspect, this application provides an in-vehicle aggregation notification method based on the Android system, characterized in that the method includes:

[0006] When detecting that the in-vehicle computer is started, start multiple built-in service modules;

[0007] Obtain and process notification messages of corresponding channels through each of the service modules;

[0008] Unify the management of the processed notification messages through a notification data management module, and aggregately display the notification messages in the notification bar.

[0009] Optionally, unifying the management of the processed notification messages through a notification data management module and aggregately displaying the notification messages in the notification bar includes:

[0010] Convert the processed notification messages into a set data format through the notification data management module;

[0011] Update the existing notification list according to the notification messages after converting the data format, wherein the notification list adopts the set data format;

[0012] Sort the notification messages in the updated notification list according to the set priority order. Among them, the priority order is that the fault notification messages are displayed first, and the Android system messages and cloud push messages are displayed later. The notification messages within the same priority are sorted in the order from the most recent generation time to the oldest;

[0013] Aggregate and display the sorted notification messages in the notification bar.

[0014] Optionally, the service module is an Android service module. Obtaining and processing the notification messages of the corresponding channels through each service module includes:

[0015] When the Android service module is successfully connected to the Android system, obtain the existing Android system messages by calling back the first method;

[0016] When the Android system receives new notification messages, obtain the latest Android system messages by calling back the second method;

[0017] Filter redundant messages from the existing Android system messages and the latest Android system messages according to preset conditions, and send the filtered Android system messages to the notification data management module.

[0018] Optionally, obtaining and processing the notification messages of the corresponding channels through each service module includes:

[0019] When the notification messages in the Android system are deleted, determine the deleted Android system messages by calling back the third method;

[0020] Send the deleted Android system messages to the notification data management module.

[0021] Optionally, the service module is a push service module. Obtaining and processing the notification messages of the corresponding channels through each service module includes:

[0022] When it is detected that the push service module is turned on, obtain the in-vehicle communication identifier sent by the cloud through the push service module, where the in-vehicle communication identifier is the unique identifier for communication between the in-vehicle device and the cloud;

[0023] Call the cloud interface to send the in-vehicle communication identifier, in-vehicle identifier, and currently logged-in account to the cloud;

[0024] Obtain the latest push notifications feedback by the cloud and the historical push notifications corresponding to the currently logged-in account;

[0025] Send the historical push notifications and the latest push notifications to the notification data management module.

[0026] Optionally, the service module is a fault notification module. Obtaining and processing the notification messages of the corresponding channels through each of the service modules respectively includes:

[0027] Listening, through the fault notification module, to the vehicle data sent by the instrument, where each array element in the vehicle data indicates a signal type;

[0028] Determining the fault data by analyzing the flag bits of each array element in the vehicle data, where the flag bits are used to indicate whether a fault has occurred;

[0029] Sending the fault data to the notification data management module.

[0030] Optionally, the Android system messages in the notification bar are cleared according to user operations, while the cloud push messages and fault notification messages in the notification bar cannot be cleared according to user operations.

[0031] In a second aspect, the present application provides an in-vehicle aggregation notification device based on the Android system. The device includes:

[0032] An enabling module, configured to enable multiple built-in service modules when it is detected that the in-vehicle computer is started;

[0033] A processing module, configured to obtain and process the notification messages of the corresponding channels through each of the service modules respectively;

[0034] A management module, configured to uniformly manage the processed notification messages through a notification data management module and aggregately display the notification messages in the notification bar.

[0035] In a third aspect, the present application provides an electronic device, including: at least one communication interface; at least one bus connected to the at least one communication interface; at least one processor connected to the at least one bus; and at least one memory connected to the at least one bus.

[0036] In a fourth aspect, the present application further provides a computer storage medium storing computer-executable instructions, and the computer-executable instructions are used to execute the in-vehicle aggregation notification method based on the Android system described in any one of the above of the present application.

[0037] The above technical solutions provided by the embodiments of the present application have the following advantages compared with the prior art: An application software including multiple service modules and a notification data management module is provided. The multiple service modules can separately process notification messages from multiple channels, and the notification data management module uniformly manages the processed notification messages, which can ensure that the finally displayed notification messages can be adjusted, solving the problem that the notification display method in the prior art is fixed and non-adjustable. The present application can improve the flexibility of notification message display. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] The accompanying drawings herein are incorporated into the specification and form a part of the specification, showing embodiments consistent with the present application and used together with the specification to explain the principles of the present application.

[0039] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the accompanying drawings required for use in the description of the embodiments or the prior art. Obviously, for those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0040] One or more embodiments are exemplarily illustrated by the pictures in the corresponding accompanying drawings. These exemplary illustrations do not constitute a limitation on the embodiments. Elements with the same reference numerals in the drawings represent similar elements. Unless otherwise stated, the drawings in the figures do not constitute a scale limitation.

[0041] Figure 1 It is a flowchart of a method for vehicle-mounted aggregated notifications based on the Android system provided by the embodiments of the present application;

[0042] Figure 2 It is a schematic diagram of the interface of a notification message pop-up window provided by the embodiments of the present application;

[0043] Figure 3 It is a schematic diagram of the interface of a notification floating window provided by the embodiments of the present application;

[0044] Figure 4 It is a sequence diagram of a vehicle-mounted aggregated notification based on the Android system provided by the embodiments of the present application;

[0045] Figure 5 It is a schematic structural diagram of a vehicle-mounted aggregated notification device provided by the embodiments of the present application;

[0046] Figure 6 It is a schematic structural diagram of an electronic device provided by the embodiments of the present application. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0047] To make the objectives, technical solutions and advantages of the embodiments of this application clearer, the technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of this application. Obviously, the described embodiments are some but not all of the embodiments of this application. All other embodiments obtained by those of ordinary skill in the art based on the embodiments in this application without creative efforts shall fall within the scope of protection of this application.

[0048] The following disclosure provides many different embodiments or examples for implementing different structures of this application. To simplify the disclosure of this application, components and settings of specific examples are described below. Of course, they are only examples and are not intended to limit this application. In addition, this application may repeat reference numerals and / or letters in different examples. This repetition is for the purpose of simplification and clarity and does not itself indicate the relationship between the various embodiments and / or settings discussed.

[0049] To solve the problems mentioned in the background art, according to one aspect of the embodiments of this application, an embodiment of a vehicle-mounted aggregation notification method based on the Android system is provided, and this method can be executed by an application software or a plug-in tool.

[0050] The application software in this application includes a notification center service, a notification data management module, and multiple service modules (Android service module, push service module, and fault notification module). The terms used in the embodiments of this application will be explained below. See the following content for details.

[0051] 1. Vehicle-mounted terminal: An intelligent vehicle-mounted device equipped with the Android system or compatible with Android applications, serving as the operating platform of the aggregation notification center.

[0052] 2. Notification center service: The background service of the notification center APP, used to start the Android service module, push service module, and fault notification module, and at the same time respond to the display and interaction of the notification pop-up window.

[0053] 3. Android service module: Inherits the NotificationListenerService (a service of the Android system API), the core service component, used to monitor and obtain Android system notifications, and implement the reception, filtering, and parsing of notifications.

[0054] 4. Android system: The Android native system, the provider of Android notification data, and the sources of these notifications include the Android system, system applications, and third-party applications.

[0055] 5. Push service module: Interacts with the cloud server, used to synchronize the push notifications bound to the vehicle VIN code and user account, and receive the push notifications pushed by the cloud server.

[0056] 6. Cloud Push Server: Push notifications to the notification center application according to different services.

[0057] 7. Fault Notification Module: Communicate with the vehicle instrument, obtain vehicle fault data in real time, convert and display the fault data in the notification center.

[0058] 8. Vehicle Instrument: Vehicle signals are mainly sent by the electronic control unit (ECU, Engine Control Unit) inside the vehicle. After receiving the signals, the instrument processes the data.

[0059] 9. Notification Data Management Module: Receive the notification data passed in by the above three modules (Module 3, Module 5, and Module 7), convert it into a unified notification data format, sort according to the notification priority, classify and display various types of notification information, and cache the final notification list data.

[0060] Next, in combination with specific implementation manners, a vehicle-mounted aggregation notification method provided by an embodiment of the present application based on the Android system will be described in detail. As Figure 1 shown, the specific steps are as follows:

[0061] Step 101: When it is detected that the in-vehicle device is started, start multiple built-in service modules.

[0062] Step 102: Obtain and process the notification messages of the corresponding channels through each service module respectively.

[0063] Step 103: Uniformly manage the processed notification messages through the notification data management module, and aggregately display the notification messages in the notification bar.

[0064] After the user starts the in-vehicle terminal through a physical button or other means, the Android system starts to initialize and load necessary driver programs and services. After the Android system initialization is completed, the SystemUI application starts. SystemUI is a core application in the Android system, responsible for managing interface elements such as the status bar and the notification center. After SystemUI starts, the status bar is also displayed, and the status bar contains the icon of the notification center and the number of unread notifications. After SystemUI starts successfully, it will further start the notification center service. This service is the background service of the notification center APP (the application software in the embodiment of the present application), responsible for managing and displaying all types of notifications. During the startup process of the notification center service, multiple service modules are started in sequence. Among them, different service modules correspond to notification messages of different channels and perform different processing operations to ensure that the notification messages of each channel can be effectively processed.

[0065] Exemplarily, the notification messages of each channel are respectively Android system messages, cloud push messages, and fault notification messages.

[0066] The notification data management module is responsible for the unified management of the processed notification messages and aggregates and displays them in the notification bar. The unified management includes, but is not limited to, deduplication and merging, priority sorting, real-time update, etc.

[0067] Exemplarily, after the in-vehicle computer is turned on, Android system messages, cloud push messages, and fault notification messages are received respectively. One service module filters a large number of Android system messages and only retains the valid messages. Another service module obtains the latest push messages and also obtains historical push messages while obtaining the latest push messages. Another service module obtains the fault notification from the vehicle instrument. Then each server module sends the processed notification messages to the notification data management module. The notification data management module sorts these notification messages and displays the fault notification messages in the front row of the pop-up window, so that the user can notice the fault notification messages in time to ensure driving safety.

[0068] This application provides an application software including multiple service modules and a notification data management module. The multiple service modules can separately process the notification messages from multiple channels, and the notification data management module conducts unified management on the processed notification messages, which can ensure that the notification messages are adjusted before being displayed, solving the problem that the notification display method in the prior art is fixed and non-adjustable. This application can improve the flexibility of the notification message display.

[0069] The service modules in the embodiments of this application include an Android service module, a push service module, and a fault notification module. The notification messages processed by each service module are respectively: Android system messages, cloud push messages, and fault notification messages. Each type of notification message will be explained below.

[0070] Android system messages: Notifications generated by local or third-party application programs relying on the Android system on the in-vehicle computer device, used for the interaction and reminder of applications on the in-vehicle terminal, providing instant information feedback and enhancing the user experience, such as music playing messages or navigation messages, etc.

[0071] Cloud push messages: Personalized and time-sensitive notifications sent by a remote server to the in-vehicle computer device through the push service, such as system updates, maintenance reminders, or points redemption, etc.

[0072] Fault notification messages: Fault information detected by vehicle internal sensors and the ECU and warnings transmitted to the user through the in-vehicle terminal, used to ensure the safe operation of the vehicle, timely discover and handle potential problems, and ensure driving safety, such as engine faults, insufficient tire pressure, or abnormal battery voltage, etc.

[0073] As an alternative implementation, in step 102, for different service modules, the ways to obtain and process the notification messages of corresponding channels are different, and the following describes each service module separately.

[0074] 1. Android service module.

[0075] Obtaining and processing the notification messages of corresponding channels through the Android service module includes the following steps:

[0076] Step S11: When the Android service module is successfully connected to the Android system, obtain the existing Android system messages by calling back the first method;

[0077] Step S12: When the Android system receives new notification messages, obtain the latest Android system messages by calling back the second method;

[0078] Step S13: Filter redundant messages from the existing Android system messages and the latest Android system messages according to preset conditions, and send the filtered Android system messages to the notification data management module.

[0079] The Android service module is a Service (named NotificationService) that inherits from NotificationListenerService. There is a notification manager inside the Android system, which is responsible for managing and displaying the notifications of all applications. When a specific event (such as a new notification arriving or a notification being deleted) occurs, the Android system automatically calls the corresponding callback methods in NotificationListenerService. The Android service module responds to the events by implementing these callback methods and obtains relevant data for processing.

[0080] The main callback methods called by the Android system include the following:

[0081] (1) onListenerConnected(): After the Android service module is connected to the Android system, the Android system calls this method. In this method, the Android service module will call the getActiveNotifications() method to obtain all the existing StatusBarNotification notifications in the current Android system.

[0082] (2) onNotificationPosted(StatusBarNotification sbn): Whenever the Android system receives a new notification, the Android system will call back the onNotificationPosted(StatusBarNotification sbn) method. In this method, the Android service module will obtain the latest Android system message.

[0083] (3) onNotificationRemoved(StatusBarNotification sbn): When an Android system notification is deleted, the Android system will call back the onNotificationRemoved(StatusBarNotification sbn) method, in which the Android service module will determine the deleted Android system message.

[0084] For callback methods (1) and (2), after obtaining the existing Android system messages and the latest Android system messages, the Android service module will filter out redundant messages according to preset conditions. If the filtered messages are not empty, they will be sent to the notification data management module to ensure that the status of the notification center is always synchronized with the Android system and there are no duplicate notifications.

[0085] Among them, the filtered messages include at least two categories, which are explained below respectively.

[0086] 1. Filter out notifications that are not aesthetically pleasing or not designed to meet your requirements.

[0087] In some cases, the Android system will send some functional notifications, such as prompts when USB devices are plugged in and out. The icons of these notifications may not be beautiful enough, and the reminder content does not meet the overall design requirements of the vehicle system. In order to maintain the consistency and beauty of the user experience, such notifications should be filtered out, and new notifications that are more in line with the design specifications should be sent by self-developed applications.

[0088] For this type of notification, the Notification package name (packageName) is checked to determine whether it comes from a system application. If the packageName belongs to an application that comes with the Android system (such as com.android.systemui or other system-level applications), the notification is filtered out.

[0089] 2. Filter the permanent notifications of background services.

[0090] When an application needs to run a certain service in the background for a long time, in order to prevent the service from being killed by the system, a notification is usually resident in the notification bar, and the FLAG_FOREGROUND_SERVICE flag is added to this notification to ensure that the service running in the background for a long time is not terminated by the Android system. However, these notifications often don't make much sense to users. Especially in the in-vehicle environment, there may be a large number of services in the background. If these notifications are displayed in the notification center, important information will be submerged, affecting the user's attention and safety.

[0091] For such notifications, by checking the flag bit (flags) of the Notification, it is judged whether it contains the FLAG_FOREGROUND_SERVICE flag. If the notification contains the FLAG_FOREGROUND_SERVICE flag, then the notification is filtered out to ensure that only the information that is truly meaningful to the user is displayed in the notification center.

[0092] In this application, the resident notifications of the Android background service and some unbeautiful or non-compliant notifications in design are filtered out through the Android service module. These redundant notifications are no longer displayed in the notification bar, and users can view the streamlined and effective notifications in a timely manner to ensure driving safety.

[0093] For the callback method in (3), when the Android service module receives the onNotificationRemoved() callback, it obtains the ID of the removed notification and passes it to the notification data management module, so that the notification data management module can find and remove the corresponding notification according to the incoming notification ID, ensuring that the state of the notification center is consistent with the Android system and updating the UI in real time.

[0094] As an optional implementation manner, after the vehicle fault notification module, Android system messages, and cloud push messages are processed, the notification data management module uniformly manages and displays the processed notification messages, including the following content:

[0095] Step S21: Convert the processed notification messages into a set data format through the notification data management module;

[0096] Step S22: Update the notifications in the existing notification list according to the notification messages after converting the data format, where the notification list uses the set data format;

[0097] Step S23: Sort the notification messages in the updated notification list in the set priority order, where the priority order is that the fault notification messages are displayed first, and the Android system messages and cloud push messages are displayed later. The notification messages within the same priority are sorted in the order from the most recent generation time to the oldest generation time;

[0098] Step S24: Aggregately display the sorted notification messages in the notification bar.

[0099] To ensure that all types of notification messages can be uniformly managed and displayed, the notification data management module first needs to convert notification messages from different sources (such as fault notification messages, Android system messages, cloud push messages) into a unified set data format. This standardized format facilitates subsequent processing and display logic. Exemplarily, the set data format is the Notify data format.

[0100] Each notification message has a unique ID. To ensure that the notifications displayed in the notification center are all the latest, the notification data management module needs to compare the ID of the newly added notification message with the IDs in the existing notification list and perform a deduplication and merging operation to update the notification list in a timely manner.

[0101] To ensure that users can see the most important information first, the notification data management module needs to sort the notification messages according to the set priority order. The sorting rule is to sort by priority first and then by timestamp. The specific sorting rules are as follows:

[0102] Priority order: Fault notification messages are displayed first, followed by Android system messages and cloud push messages.

[0103] Time order: Within the same priority, sort in descending order of the time when the notification was generated.

[0104] After the sorting is completed, the notification data management module calls the API interface of the notification processing service to inform it that the data has been updated, so as to ensure that the notification processing service can obtain the latest notification list and display or refresh it according to the actual situation. After receiving the data update notification, the notification processing service needs to judge the status of the current pop-up window in the notification center (whether the pop-up window is displayed) and decide whether to directly refresh the notification list in the pop-up window or display a new notification floating window according to the status. If the pop-up window is already displayed, directly refresh the notification list in the pop-up window to display the latest notification information; if the pop-up window is not displayed, display a short notification floating window that only shows the latest received notification. The notification floating window automatically closes after being displayed for a period of time (such as 10 seconds) to avoid occupying the user's attention for a long time.

[0105] Figure 2 This is a schematic diagram of the interface of the notification message pop-up window provided by this application. It can be seen that the OTA upgrade and xxx fault have the highest priority and are displayed at the top of the pop-up window, and the background color is gray and cannot be deleted. The remaining notification messages have a lower priority, the background color is white and can be deleted. The notification messages of each priority are sorted according to the timestamp.

[0106] Among them, the notification floating window is a small notification window that is briefly displayed on the screen. It is usually used to display the latest single notification and automatically disappears after a few seconds. Figure 3 It is a schematic diagram of the interface of the notification floating window.

[0107] Among them, the status bar is located at the top of the screen, containing icons such as time, battery level, Wi-Fi signal, etc., and a summary notification icon (usually a small bell with a number). This icon indicates that there are new notifications waiting to be viewed.

[0108] Among them, the notification center pop-up window is a full-screen or partial-screen window that pops up when the user clicks the notification icon in the status bar. It is used to display all unread and important notification information. When the notification center pop-up window is not displayed, it means that there is no expanded pop-up window on the current screen that shows all notifications. In this case, the user can still click the notification icon in the status bar to view all notifications. At this time, the notification center service needs to obtain the latest notification list data (NotifyList) from the notification data management module and display it on the pop-up window of the notification center. This process ensures that users can view all unread and important notification information at any time. The collaboration between the notification center service and the notification data management module also ensures the real-time update and consistency of notification messages.

[0109] In step S22, for Android system messages, there are two ways to update the notification list as follows.

[0110] The Android service module sends the IDs of existing Android system messages and the latest Android system messages to the notification data management module. The notification data management module compares the notification IDs of Android system messages with the notification IDs in the notification list; if there are the same message IDs, the relevant messages in the notification list are overwritten with the Android system messages to ensure that the messages in the notification list are the latest; if there are no same message IDs, the Android system messages are added to the notification list to ensure that the messages in the notification list are the most complete.

[0111] The Android service module sends the deleted Android system messages to the notification data management module. The notification data management module traverses the notification IDs in the notification list to determine whether the deleted notification ID is included. If it is included, the Android system message is removed from the notification list.

[0112] Second, the push service module.

[0113] Obtaining and processing notification messages corresponding to the corresponding channels through the push service module includes the following steps:

[0114] Step S31: When it is detected that the push service module is enabled, obtain the vehicle communication identifier sent by the cloud through the push service module, where the vehicle communication identifier is the unique identifier for communication between the vehicle device and the cloud;

[0115] Step S32: Call the cloud interface to send the vehicle communication identifier, vehicle identifier, and current logged-in account to the cloud;

[0116] Step S33: Obtain the latest push notifications feedback from the cloud and the historical push notifications corresponding to the current logged-in account;

[0117] Step S34: Send the historical push notifications and the latest push notifications to the notification data management module.

[0118] When the in-vehicle terminal starts, the push service module will start automatically. This module is responsible for establishing a connection with the cloud server to ensure that push notifications from the cloud can be received in real time. When the push service module starts for the first time, the cloud push server assigns a unique vehicle communication identifier deviceId to each vehicle device and sends this deviceId to the push service module. The vehicle communication identifier is the unique identifier for communication between the vehicle device and the cloud.

[0119] The system reads the VIN (Vehicle Identification Number) code from the in-vehicle terminal or the vehicle internal system. The VIN code is the unique identifier of the vehicle, which is used to ensure that push messages are accurately sent to the specified vehicle. If the current user has logged in to the in-vehicle terminal, the system will obtain the current logged-in account userId of the user, and the userId is used for personalized push and account association; if the user has not logged in, this step will be skipped and processed after the user logs in.

[0120] The push service module calls the cloud interface to pass the deviceId, VIN code, and userId to the cloud server through the API interface. The cloud server queries and returns the corresponding historical push notifications and the latest push notifications based on these three pieces of data. After receiving the historical push notification data and the latest push notifications, the push service module passes them to the notification data management module for processing. The notification data management module is responsible for converting these push notifications into a unified data format and comparing them with the data in the existing notification list to remove duplicates. The processed new notifications will be merged into the notification list and sorted and displayed according to the set priority order.

[0121] In this application, when the in-vehicle computer is started each time, the unprocessed historical push notifications can be restored, keeping the status of the notification center consistent with the system and also preventing users from missing important historical push notifications. In addition, the embodiments of this application use triple verification of the deviceId, VIN code, and userId to ensure that the push notifications are accurately sent to the specified vehicle and user, enhancing the security and reliability of the system.

[0122] Optionally, the push service module also listens for changes in the user's login status. When it detects that the user switches the logged-in account of the in-vehicle terminal, the push service module will call the cloud interface again, pass the deviceId, VIN code, and the new userId to the cloud server, and obtain the historical push notifications corresponding to the new account. The push service module sends the new userId and the historical push notifications to the notification data management module. The notification data management module clears all the notification data related to the old account, processes and sorts the push notifications of the new account, and then displays them in the notification center pop-up window to ensure that the information of different accounts is not confused. In this application, each time the account is switched, the latest historical push notifications can be synchronized in a timely manner, and each user can see their own push notifications, avoiding the confusion of notifications of different accounts and improving the user experience.

[0123] Optionally, when different services need to push notifications to a specified vehicle or account, different service systems send notification requests to the cloud server through the API interface, attaching the deviceId, VIN code, and userId of the target vehicle. After receiving the notification request, the cloud server locates the target in-vehicle computer device according to the provided identifiers and pushes the notifications to the push service module in real time. After receiving the push notifications, the push service module passes the notification data to the notification data management module. The notification data management module processes, sorts the new notifications, and updates them to the notification center. This application can ensure that the push notifications of different service systems can reach the target in-vehicle computer device in real time and be accurately displayed to the user, improving the user experience.

[0124] Third, the fault notification module.

[0125] The steps of obtaining and processing the notification messages of the corresponding channels through the fault notification module are as follows:

[0126] Step S41: Listen for the vehicle data sent by the instrument through the fault notification module, where each array element in the vehicle data indicates a signal type;

[0127] Step S42: Determine the fault data by analyzing the flag bits of each array element in the vehicle data, where the flag bits are used to indicate whether a fault has occurred;

[0128] Step S43: Send the fault data to the notification data management module.

[0129] The vehicle ECU continuously sends signals of various sensors and systems to the instrument. The instrument receives these signals from the vehicle ECU. On the one hand, through corresponding fault logic processing, it converts the real fault data into fault lights in the instrument. On the other hand, the instrument encapsulates the signals into data packets in the byte[] format and sends them to the fault notification module. The fault notification module registers and listens for vehicle data transmitted from the vehicle instrument through the middleware interface. The byte[] format is as follows:

[0130] [0,1,0,1,0,0,0,0,......1,1,0,0,0,0].

[0131] Each array element in each byte[] represents a specific signal type. For example, the 1st bit: charging signal, the 2nd bit: dipped headlight signal, the 3rd bit: braking system signal, and so on. The flag bit of the array element is used to indicate whether a fault has occurred. The flag bit 0 indicates no fault, and 1 indicates a fault exists.

[0132] By analyzing the flag bits of these array elements bit by bit, the fault notification module can determine which signal types have faults. For example, the above data status indicates that there is no "abnormal charging fault" currently, there is a "dipped headlight fault", and there is no "braking system fault". After the fault notification module determines the fault data, it needs to pass these fault data to the notification data management module for further processing. The notification data management module first converts each fault data into a Notify object containing information such as a fault icon, a fault title, and a fault reminder content, ensuring that each Notify object has a unique identifier for subsequent deduplication and management. Then, it checks whether there is the same fault notification in the notification list to avoid duplicate display. If there is no same notification, it adds the new fault notification to the notification list and removes the resolved fault notification from the notification list.

[0133] The fault notification message will always be kept in the notification bar, displayed at the top and with a gray bottom. If the fault has not disappeared, the fault notification message cannot be cleared, and the user cannot delete this fault notification message unless the notification data management module determines after comparison that the fault has been resolved, and then removes this fault notification message from the notification list, and the fault notification message in the notification center will be synchronously cleared.

[0134] In this application, the fault notification module accurately identifies each fault status by analyzing the array elements bit by bit, ensuring that no fault data is missed or misreported, and the notification data management module provides intuitive and detailed fault reminders, including fault icons, fault titles, and fault contents, enabling users to more intuitively understand the nature of the faults and take corresponding measures.

[0135] As an alternative implementation, in the notification bar, different types of notification messages have different clearing mechanisms. Android system messages can be cleared according to the user's operation, while cloud push messages and fault notification messages cannot be directly cleared according to the user's operation. Especially for fault notifications, due to their important impact on driving safety, they must be always displayed in the notification bar to ensure that users can see the fault information in time, and can only be cleared after the fault disappears. The clearing mechanisms for each type of notification message are described below.

[0136] 1. Clearing of Android system messages.

[0137] When the user clicks or swipes on a certain Android system notification, the notification will be removed from the notification bar. After the notification data management module receives the user's clearing instruction, it removes the corresponding notification object from the notification list. This clearing mechanism follows the native behavior of the Android system, providing a convenient way for users to manage daily notifications. Users can easily clear Android system messages, reducing unnecessary notification interference.

[0138] 2. Non-clearability of cloud push messages and fault notifications.

[0139] The priority of fault notifications is set to the highest to ensure that they are always at the top of the notification list. Fault notification messages will always remain in the notification bar unless the fault status is lifted, ensuring that users can promptly discover and handle potential safety hazards.

[0140] For cloud push messages, whether they disappear depends on the business status, rather than the user's click operation. For example, if a certain business is not completed, the corresponding push notification will continue to be displayed until the user processes it in the specified business. Cloud push messages and fault notifications cannot be easily cleared, ensuring that users do not miss important information, especially to ensure safety in the driving environment.

[0141] The embodiment of this application provides a timing diagram of vehicle-mounted aggregated notifications based on the Android system, as Figure 4 shown, including the following steps.

[0142] 1. The user turns on the in-vehicle terminal.

[0143] The user starts the in-vehicle terminal device, the Android system boots up, the SystemUI application starts, and the notification center service starts. The notification center service will immediately start the following modules: the Android service module, the push service module, and the fault notification module.

[0144] 2. The Android service module.

[0145] The Android notification processing service inherits from NotificationListenerService and is named NotificationService. When the Android system receives a new notification or a notification is deleted, the callback method of NotificationListenerService is triggered.

[0146] onListenerConnected(): After NotificationService is connected to the Android system, the getActiveNotifications() method is called to obtain all currently existing StatusBarNotification notifications, and steps 3 and 4 are executed.

[0147] onNotificationPosted(StatusBarNotification sbn): When the Android system receives a new notification, this method is called back, and steps 3 and 4 are executed.

[0148] onNotificationRemoved(StatusBarNotification sbn): When an Android system notification is deleted, this method is called back, and step 5 is executed.

[0149] 3. Filter StatusBarNotification.

[0150] From the perspective of automotive safe driving, the Android service module filters unnecessary notifications: filters out unseemly notifications (such as when plugging in or unplugging the USB) according to the application package name packageName; filters out notifications of services that run in the background for a long time according to the FLAG_FOREGROUND_SERVICE flag.

[0151] 4. Process valid notifications.

[0152] The Android service module passes the filtered valid notifications to the notification data management module. The notification data management module converts the Notification into the set data format Notify, and compares it with the data in the notification list NotifyList according to the notification ID. If there is the same ID, the notification overwrites the relevant content in the notification list. If there is no same ID, the notification is added to the notification list.

[0153] 5. Update the notification list NotifyList.

[0154] After the Android service module receives onNotificationRemoved(), it passes the ID of the deleted Notification to the notification data management module. The notification data management module traverses the NotifyList to determine whether the notification ID is included. If it is included, the notification is removed from the notification list.

[0155] 6. Sorting of the notification list NotifyList.

[0156] Sort by the priority of fault notifications > normal notifications.

[0157] Fault notifications are displayed at the top, with a gray bottom and cannot be deleted by the user.

[0158] Normal notifications are displayed below the fault notifications, and the user can operate to delete them, such as swiping to delete.

[0159] 7. Display notifications.

[0160] After the notification list is sorted, the notification data management module tells the notification processing service that the data has been updated.

[0161] If the notification center pop-up window is already displayed, directly refresh the pop-up notification list.

[0162] If the notification center pop-up window is not displayed, then display a notification floating window, which only shows the latest received notification, and the floating window will automatically close after 10 seconds.

[0163] 8. Push service module.

[0164] After the push service module is started, it obtains the vehicle VIN code, deviceId, and userId, calls the cloud interface to transmit these data to the cloud server, and obtains the corresponding historical push notifications and the latest push notifications returned by the cloud. The push service module passes the cloud push messages to the notification data management module, and the notification data management module converts them into a set data format, compares them with the data in the notification list to remove duplicates, and finally merges them into the notification list, and executes steps 6 and 7.

[0165] When the in-vehicle device switches accounts, the push service module calls the cloud interface again to obtain the historical push notifications corresponding to the new account. The notification data management module clears the notification data of the previous account, processes the push notifications of the new account, sorts them, and displays them in the notification center pop-up window.

[0166] When different services need to push notifications to a specified vehicle or account, the notification data is transmitted to the cloud server, and the cloud server pushes notifications in real time according to the deviceId, VIN code, and userId passed in by the in-vehicle device. After the in-vehicle device receives the notification, it processes, sorts, and displays it.

[0167] 9. Fault notification module.

[0168] The instrument receives various signals transmitted from the vehicle ECU, processes them through corresponding fault logics, converts them into vehicle data, and transmits the vehicle data to the fault notification module through middleware. The fault notification module analyzes the data to obtain fault data, and sends the fault data to the notification data management module. The notification data management module converts the fault data into a meaningful set data format, including fault icons, fault titles, fault reminder contents, etc., and then de-duplicates the fault notification data and adds it to the notification list, and executes steps 6 and 7.

[0169] 10. Display a pop-up window in the notification center.

[0170] When the pop-up window in the notification center is not displayed, the user clicks the notification icon in the status bar.

[0171] The notification center service obtains the data of the notification list NotifyList from the notification data management module and displays it on the pop-up window in the notification center.

[0172] In this application, all different types of notifications (including regular notifications from the Android system, business notifications pushed from the cloud, and fault notifications of the vehicle itself) will be centrally displayed in a notification pop-up window. Users do not need to switch between different interfaces or applications to view different types of reminder messages. All notifications are integrated together, providing a consistent and convenient viewing experience. Different from traditional Android notifications, even if these notifications are closed or deleted by the user, they will not disappear permanently. The system will retain the data of these notifications, allowing users to view historical notifications at a certain time in the future, ensuring that important information will not be lost due to misoperations. Especially for fault notifications, due to their importance and urgency, users are usually not allowed to easily delete them, and they will be displayed until the problem is solved.

[0173] Exemplarily, when the user receives a new text message (Android notification), a promotion activity push from the cloud (push notification), and a reminder on the dashboard that the engine temperature is too high (fault notification), all these notifications will appear in the same pop-up window. The user can quickly browse and select the notifications to be processed in this pop-up window. For example, the user can first view the details of the fault that the engine temperature is too high and take corresponding measures; then read the content of the text message; and finally decide whether to participate in the promotion activity. Even if the user temporarily closes this pop-up window, the user can still reopen it later to view all previous notifications, including the notifications that have been closed, which helps the user review any important information that may have been missed.

[0174] Based on the same technical concept, this application provides an in-vehicle aggregated notification device based on the Android system, as Figure 5 shown, the device includes:

[0175] An enabling module 501, configured to enable multiple built-in service modules when detecting the startup of the in-vehicle computer;

[0176] A processing module 502, configured to obtain and process notification messages of corresponding channels respectively through each service module;

[0177] A management module 503, configured to uniformly manage the processed notification messages through a notification data management module, and aggregately display the notification messages in a notification bar.

[0178] Optionally, the management module 503 is configured to:

[0179] Convert the processed notification messages into a set data format through the notification data management module;

[0180] Update the existing notification list according to the notification messages after converting the data format, wherein the notification list adopts the set data format;

[0181] Sort the notification messages in the updated notification list according to a set priority order, wherein the priority order is that the fault notification messages are displayed first, the Android system messages and the cloud push messages are displayed later, and the notification messages within the same priority are sorted in the order from the latest generation time to the earliest;

[0182] Aggregately display the sorted notification messages in the notification bar.

[0183] Optionally, the service module is an Android service module, and the processing module 502 is configured to:

[0184] When the Android service module is successfully connected to the Android system, obtain the existing Android system messages through a callback of a first method;

[0185] When the Android system receives new notification messages, obtain the latest Android system messages through a callback of a second method;

[0186] Filter redundant messages from the existing Android system messages and the latest Android system messages according to preset conditions, and send the filtered Android system messages to the notification data management module.

[0187] Optionally, the processing module 502 is configured to:

[0188] When the notification messages in the Android system are deleted, determine the deleted Android system messages through a callback of a third method;

[0189] Send the deleted Android system messages to the notification data management module.

[0190] Optionally, the service module is a push service module, and the processing module 502 is configured to:

[0191] When it is detected that the push service module is turned on, obtain the in-vehicle communication identifier sent by the cloud through the push service module, where the in-vehicle communication identifier is the unique identifier for communication between the in-vehicle device and the cloud;

[0192] Call the cloud interface to send the in-vehicle communication identifier, the in-vehicle identifier, and the currently logged-in account to the cloud;

[0193] Obtain the latest push notifications feedback by the cloud and the historical push notifications corresponding to the currently logged-in account;

[0194] Send the historical push notifications and the latest push notifications to the notification data management module.

[0195] Optionally, the service module is a fault notification module, and the processing module 502 is used for:

[0196] Monitor the vehicle data sent by the instrument through the fault notification module, where each array element in the vehicle data indicates a signal type;

[0197] Determine the fault data by analyzing the flag bits of each array element in the vehicle data, where the flag bits are used to indicate whether a fault has occurred;

[0198] Send the fault data to the notification data management module.

[0199] Optionally, the Android system messages in the notification bar are cleared according to user operations, while the cloud push messages and fault notification messages in the notification bar cannot be cleared according to user operations.

[0200] As Figure 6 shown, an embodiment of the present application provides an electronic device, including a processor 601, a communication interface 602, a memory 603, and a communication bus 604. Among them, the processor 601, the communication interface 602, and the memory 603 complete mutual communication through the communication bus 604.

[0201] The memory 603 is used to store computer programs.

[0202] In an embodiment of the present application, when the processor 601 executes the program stored on the memory 603, it implements the in-vehicle aggregation notification method based on the Android system provided by any one of the foregoing method embodiments.

[0203] An embodiment of the present application also provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, it implements the steps of the in-vehicle aggregation notification method based on the Android system provided by any one of the foregoing method embodiments.

[0204] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed to multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0205] Through the description of the above embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus a general hardware platform, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solution, in essence, or the part that makes contributions to the related technology, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in each embodiment or some parts of the embodiments.

[0206] It should be understood that the terms used herein are for the purpose of describing specific example embodiments only and are not intended to be limiting. Unless the context clearly indicates otherwise, the singular forms "a", "an", and "the" as used herein may also include the plural forms. The terms "comprising", "including", "containing", and "having" are inclusive and thus specify the presence of the stated features, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, steps, operations, elements, components, and / or combinations thereof. The method steps, processes, and operations described herein are not to be construed as necessarily requiring them to be executed in the particular order described or illustrated, unless the execution order is explicitly stated. It should also be understood that additional or alternative steps can be used.

[0207] The above description is only the specific implementation manners of this application, enabling those skilled in the art to understand or implement this application. Various modifications to these embodiments will be obvious to those skilled in the art, and the general principles defined herein can be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application will not be limited to these embodiments shown herein, but rather will be accorded the widest scope consistent with the principles and novel features claimed herein.

Claims

1. A vehicle aggregation notification method based on Android system, characterized in that: The method comprises: When the vehicle is detected to be started, multiple built-in service modules are turned on; Acquire and process the notification message of the corresponding channel respectively through each of the service modules; The processed notification messages are centrally managed through the notification data management module, and the notification messages are aggregated and displayed in the notification bar.

2. The method according to claim 1, characterized in that: The notification data management module manages the processed notification messages in a unified manner and aggregates and displays the notification messages in the notification bar, including: Converting the processed notification message into a set data format through the notification data management module; updating the existing notification list according to the notification message after the data format is converted, wherein the notification list adopts the set data format; Sort the notification messages in the updated notification list according to the set priority order, wherein the priority order is that fault notification messages are displayed first, Android system messages and cloud push messages are displayed later, and notification messages within the same priority are sorted in order from recent to distant according to the time of generation; The sorted notification messages are aggregated and displayed in the notification bar.

3. The method according to claim 1, characterized in that The service module is an Android service module, and obtaining and processing the notification message of the corresponding channel through each service module includes: When the Android service module is successfully connected to the Android system, obtaining an existing Android system message by calling back the first method; When the Android system receives a new notification message, obtaining the latest Android system message by calling back the second method; Redundant message filtering is performed on the existing Android system message and the latest Android system message according to preset conditions, and the filtered Android system message is sent to the notification data management module.

4. The method according to claim 3, characterized in that Acquiring and processing the notification message of the corresponding channel by each of the service modules respectively includes: When the notification message in the Android system is deleted, determining the deleted Android system message by calling back the third method; The deleted Android system message is sent to the notification data management module.

5. The method according to claim 1, characterized in that The service module is a push service module, and obtaining and processing the notification message of the corresponding channel through each of the service modules includes: When it is detected that the push service module is turned on, the vehicle-machine communication identifier sent by the cloud is obtained through the push service module, wherein the vehicle-machine communication identifier is a unique identifier for communication between the vehicle-machine device and the cloud; Calling the cloud interface to send the vehicle computer communication identifier, vehicle computer identifier and current login account to the cloud; Obtain the latest push notification fed back by the cloud and the historical push notifications corresponding to the currently logged-in account; The historical push notifications and the latest push notification are sent to the notification data management module.

6. The method according to claim 1, characterized in that The service module is a fault notification module, and obtaining and processing the notification message of the corresponding channel through each of the service modules includes: Monitoring vehicle data sent by the instrument through the fault notification module, wherein each array element in the vehicle data indicates a signal type; Determine fault data by analyzing a flag bit of each array element in the vehicle data, wherein the flag bit is used to indicate whether a fault occurs; The fault data is sent to the notification data management module.

7. The method according to claim 1, characterized in that The Android system messages in the notification bar are cleared according to user operations, while the cloud push messages and fault notification messages in the notification bar cannot be cleared according to user operations.

8. An Android-based vehicle aggregation notification device, characterized in that: The device comprises: The start module is used to start multiple built-in service modules when the vehicle computer is detected to be started; A processing module, used to obtain and process notification messages of corresponding channels respectively through each of the service modules; The management module is used to uniformly manage the processed notification messages through the notification data management module, and aggregate the notification messages and display them in the notification bar.

9. An electronic device, characterized in that: It includes a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other through the communication bus; Memory, used to store computer programs; A processor, for implementing any of the methods described in claims 1-7 when executing a program stored in a memory.

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

Images