Information acquisition method, vehicle, and storage medium

Abstract

The application provides an information acquisition method, a vehicle and a storage medium, and belongs to the technical field of car machine system. The method comprises the following steps: after the car machine system is started, an event of a window management service of the car machine system is listened to; when a first event corresponding to a window adding request of a target application in the car machine system is listened to, a first time corresponding to the first event is acquired, the window adding request is used for requesting the window management service to add a window component of the target application, and the window component is used for displaying an associated component of the target application; when a second event corresponding to a window removing request of the target application is listened to, a second time corresponding to the second event is acquired, the window removing request is used for requesting the window management service to remove the window component of the target application; and the use time length information of the target application is determined according to the first time and the second time. According to the application, the accuracy of the use time length information of the target application can be improved.

Description

Technical Field

[0001] This application relates to the field of vehicle infotainment system technology, and more specifically, to an information acquisition method, vehicle, and storage medium in the field of vehicle infotainment system technology. Background Technology

[0002] In in-vehicle infotainment systems based on the Android platform, obtaining the usage time of applications within the system is crucial for optimizing user experience and system performance. One related technology collects usage time information by listening to Activity-related events. However, Activities suffer from drawbacks such as state confusion in multi-screen / split-screen scenarios, inability to perceive non-Activity pages, and failure to determine ownership in multi-screen displays. These limitations make Activity-based usage time acquisition methods unreliable in accurately reflecting actual application usage. Therefore, improving the accuracy of obtaining application usage time information in in-vehicle infotainment systems has become a pressing technical challenge. Summary of the Invention

[0003] This application provides an information acquisition method, a vehicle, and a storage medium, which can improve the accuracy of usage time information of a target application.

[0004] Firstly, an information acquisition method is provided, which includes:

[0005] After the vehicle infotainment system starts up, perform event listening on the window management service of the vehicle infotainment system;

[0006] When the first event corresponding to the window addition request of the target application in the vehicle system is detected, the first moment corresponding to the first event is obtained. The window addition request is used to request the window management service to add the window component of the target application. The window component is used to display the associated components of the target application.

[0007] When the second event corresponding to the window removal request of the target application is detected, the second moment corresponding to the second event is obtained. The window removal request is used to request the window management service to remove the window component of the target application.

[0008] Based on the first and second time points, determine the usage duration information of the target application.

[0009] By utilizing the above solution and the event listening service to implement event listening, it is possible to accurately identify all related components displayed through window components under the target application, thereby reflecting the usage status of the target application and improving the accuracy of the usage duration information of the target application.

[0010] In conjunction with the first aspect, in some possible implementations, the usage duration information of the target application is determined based on the first moment and the second moment, including: determining the first duration information based on the first moment and the second moment; deducting the duration of the first duration information based on the previously acquired invalid duration information to obtain the usage duration information of the target application, wherein the invalid duration information is determined based on the operation information of the vehicle to which the vehicle system belongs between the first moment and the second moment.

[0011] By introducing a mechanism to deduct invalid usage time information, the above scheme can eliminate inaccurate usage time caused by vehicle operating status, thereby making the final usage time information of the target application closer to the actual user situation and improving the objectivity and accuracy of the usage time information.

[0012] In combination with the first aspect and the above implementation methods, in some possible implementation methods, the running information includes speed information, the invalid duration information includes second duration information, and the method further includes: acquiring the vehicle's speed information between the first moment and the second moment; if the speed information indicates that the vehicle's driving speed is greater than a preset speed threshold, then determining the second duration information based on the duration of the driving speed being greater than the preset speed threshold.

[0013] By introducing an invalid duration determination mechanism based on speed information, the above scheme can more accurately identify the periods during which vehicle operating status affects application usage time statistics, and use this as the basis for subsequent duration deduction, making the final determined usage time information more objective and accurate.

[0014] In combination with the first aspect and the above implementation methods, in some possible implementation methods, the operation information also includes operation mode information, and the invalid duration information also includes third duration information. If the speed information indicates that the vehicle's driving speed is greater than a preset speed threshold, then after determining the second duration information based on the duration of the driving speed being greater than the preset speed threshold, the method further includes: if the speed information indicates that the vehicle's driving speed is less than or equal to the preset speed threshold, then obtaining the vehicle's operation mode information; if the operation mode information indicates that the vehicle is in sentry mode, then determining the third duration information based on the duration of the vehicle being in sentry mode.

[0015] The above scheme, by introducing a dual invalid duration determination mechanism based on speed and operating mode information, can more accurately identify the periods during which vehicle operating status affects application usage time statistics. Specifically, using high-speed driving and sentry mode as independent invalid duration determination conditions allows for differentiated deduction strategies for different scenarios, thus making the final determined usage time information more objective and accurate.

[0016] Combining the first aspect and the above implementation methods, in some possible implementation methods, the usage duration information of the target application is obtained by deducting the duration of the first duration information based on the pre-acquired invalid duration information. This includes: if the target application is a first type of application, then the second duration information and the third duration information are deducted from the first duration information to obtain the usage duration information of the target application; if the target application is a second type of application, then the third duration information is deducted from the first duration information to obtain the usage duration information of the target application, wherein the interaction intensity of the first type of application is higher than that of the second type of application.

[0017] By establishing a differentiated deduction strategy linked to the intensity of application interaction, the above approach can more accurately distinguish between real-world usage scenarios and invalid statistical periods. For the first type of application requiring high interaction, both high-speed driving and sentry mode periods are deducted; for the second type of application with low interaction requirements, only sentry mode periods are deducted. This layered processing mechanism based on application characteristics avoids statistical distortion caused by excessive deduction while ensuring the rationality of the deducted periods, thereby significantly improving the match between usage time information and actual user behavior.

[0018] In combination with the first aspect and the above implementation methods, in some possible implementation methods, determining the first duration information based on the first moment and the second moment includes: determining the fourth duration information based on the first moment and the second moment; obtaining the fifth duration information of the target application, wherein the fifth duration information indicates the duration to be compensated generated by the target application before the first moment; and compensating the fourth duration information based on the fifth duration information of the target application to obtain the first duration information.

[0019] The above solution, by introducing a compensation mechanism based on historical data, can effectively solve the problem of interruption in application usage time statistics caused by system anomalies, ensure the continuity and integrity of statistical data, and thus improve the accuracy and reliability of usage time information.

[0020] In combination with the first aspect and the above implementation methods, in some possible implementation methods, before the first moment, the method further includes: when the third event corresponding to the window addition request of the target application is detected, obtaining the third moment corresponding to the third event; based on a preset period, obtaining the system time of the vehicle system and determining the fifth duration information of the target application according to the third moment and the system time; the fifth duration information of the target application is cleared when the fourth event corresponding to the window removal request of the target application is detected.

[0021] The above solution, by establishing a periodic compensation recording mechanism during the display of the target application window, can save usage time data that may be lost due to abnormal system interruptions in real time. Specifically, system-wide time-based data collection based on a preset period ensures the timeliness of the compensation data, while the zeroing operation when the window is removed maintains the statistical accuracy under normal circumstances, effectively solving the problem of data loss caused by system or application crashes.

[0022] In combination with the first aspect and the above implementation methods, in some possible implementation methods, the target application is configured to display the screen projection content of the mobile device connected to the vehicle system. The method further includes: calling a preset interface in the vehicle system to obtain a set of status notifications sent by the mobile device between a first moment and a second moment. The set of status notifications includes the status notifications of each sub-application in the mobile device; and determining the sub-duration information of each sub-application in the usage duration information based on the status notifications of each sub-application.

[0023] By establishing a status notification transmission mechanism between the vehicle system and mobile devices, the actual usage status of each sub-application on the mobile device can be accurately obtained through the above solution. The preset interface ensures the reception of status notifications, while the sub-duration calculation enables refined statistics on the projected content, effectively solving the problem in related technologies that cannot distinguish the usage time of sub-applications on mobile devices. This makes the application usage time statistics in the vehicle-to-vehicle interconnection scenario more comprehensive and accurate.

[0024] Secondly, an information acquisition device is provided, the device comprising:

[0025] The listening unit is used to listen for events related to the window management service of the vehicle infotainment system after the system starts up.

[0026] The first acquisition unit is used to acquire the first moment corresponding to the first event when the first event corresponding to the window addition request of the target application in the vehicle system is detected. The window addition request is used to request the window management service to add the window component of the target application. The window component is used to display the associated components of the target application.

[0027] The second acquisition unit is used to acquire the second moment corresponding to the second event when the second event corresponding to the window removal request of the target application is detected. The window removal request is used to request the window management service to remove the window component of the target application.

[0028] The determination unit is used to determine the usage duration information of the target application based on the first time and the second time.

[0029] Thirdly, a vehicle is provided, characterized in that the vehicle comprises:

[0030] Memory, used to store executable program code;

[0031] A processor is configured to call and run executable program code from the memory, causing the vehicle to perform the methods described in the first aspect or any possible implementation thereof.

[0032] Fourthly, a computer program product is provided, comprising: computer program code, which, when run on a computer, causes the computer to perform the methods described in the first aspect or any possible implementation thereof.

[0033] Fifthly, a computer-readable storage medium is provided that stores computer program code, which, when executed on a computer, causes the computer to perform the methods described in the first aspect or any possible implementation thereof. Attached Figure Description

[0034] Figure 1 This is an example diagram illustrating how to obtain usage duration information based on an Activity, as provided in an embodiment of this application.

[0035] Figure 2 This is a flowchart illustrating an information acquisition method provided in an embodiment of this application;

[0036] Figure 3 This is an example diagram illustrating how to obtain usage duration information based on a Window, as provided in an embodiment of this application.

[0037] Figure 4 This is a schematic diagram of a process for obtaining usage time information by deduction according to an embodiment of this application;

[0038] Figure 5 This is a schematic diagram of a process for obtaining invalid duration information provided in an embodiment of this application;

[0039] Figure 6 This is an example diagram illustrating how to obtain invalid duration information according to an embodiment of this application;

[0040] Figure 7 This is an example diagram illustrating the deduction of invalid duration information provided in an embodiment of this application;

[0041] Figure 8 This is a schematic diagram of a process for obtaining first duration information through compensation, provided in an embodiment of this application;

[0042] Figure 9 This is a schematic diagram of a process for obtaining fifth duration information based on a preset period, provided in an embodiment of this application;

[0043] Figure 10This is an example diagram illustrating how compensation is used to obtain first duration information, as provided in an embodiment of this application.

[0044] Figure 11 This is a schematic diagram of a process for determining sub-duration information provided in an embodiment of this application;

[0045] Figure 12 This is an example diagram illustrating how a notification from a mobile device is determined at a relevant time, as provided in an embodiment of this application.

[0046] Figure 13 This is a schematic diagram of the structure of an information acquisition device provided in an embodiment of this application;

[0047] Figure 14 This is a schematic diagram of the structure of a vehicle provided in an embodiment of this application. Detailed Implementation

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

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

[0050] In Android-based in-vehicle infotainment systems, obtaining usage time data for applications within the system is crucial for optimizing user experience and system performance. Please combine this information with... Figure 1 , Figure 1This is an example illustration of obtaining usage duration information based on Activity, provided in an embodiment of this application. The vehicle system listens for Activity-related events of the application through the relevant interfaces of ActivityManagerService (Activity Management Service). When entering the target application, the relevant interfaces listen for the Activity creation event of the application and store the current system time as the entry time in the storage unit according to the application's package name. When exiting the target application, the relevant interfaces listen for the Activity destruction event of the application and query the storage unit for the corresponding entry time of the application according to the application's package name. Then, the time difference between the current system time and the application's entry time is calculated as the usage duration. Finally, the correspondence between the application's usage duration and package name is saved to the storage unit.

[0051] However, due to the shortcomings of Activities, such as state confusion in multi-screen / split-screen scenarios, inability to perceive non-Activity pages, and failure of ownership determination when displaying multiple screens, the statistical methods based on Activities cannot accurately reflect the actual usage of the application.

[0052] Specifically, regarding the issue of state confusion in multi-screen / split-screen scenarios, with the upgrade of Android system versions, in-vehicle systems support multiple Activities displayed on the screen simultaneously. For example, in split-screen mode, multiple applications each occupy a portion of the screen space. Current solutions rely on ActivityManagerService to listen for events related to a single Activity, which cannot accurately determine the actual usage status when multiple Activities exist simultaneously. When users switch between different split-screen areas, the system cannot effectively distinguish which Activity is actually in use, leading to inaccurate statistical results. Furthermore, in multi-screen display scenarios in automobiles, the driver's screen and the passenger's screen may run different applications simultaneously, making it difficult for Activity-based statistical methods to correctly distinguish application usage on different screens.

[0053] Regarding non-Activity pages that are not perceptible, in-vehicle infotainment systems present interfaces in other forms, such as floating windows for navigation applications and notification bar control interfaces for music players. These interfaces are not implemented through Activity components, and related technical solutions cannot obtain their display status through ActivityManagerService. Furthermore, some system-level functions, such as the screen projection interface for vehicle-to-car connectivity, also bypass the Activity mechanism, causing traditional statistical solutions to fail to cover these important use cases.

[0054] Regarding the failure of attribution determination in multi-screen displays, relevant vehicles are typically equipped with multiple independent displays, each capable of running different applications simultaneously. When related technologies determine application usage status through Activity lifecycle analysis, they cannot distinguish which physical screen the Activity is actually displayed on. For example, when the driver's and passenger's screens simultaneously display different instances of the same application, the system incorrectly merges the usage time of the two screens in its statistics. Similarly, in scenarios where mobile devices are projected onto the vehicle's infotainment system, mobile applications are presented through specific applications on the vehicle's system. Related technologies cannot distinguish the relationship between the mobile device's application and the projected application on the vehicle's system, leading to inconsistent statistical dimensions.

[0055] It is evident that the Activity-based methods for obtaining usage time in related technologies have several shortcomings. Therefore, improving the accuracy of obtaining usage time information for applications in in-vehicle infotainment systems has become an urgent technical problem to be solved.

[0056] To address the aforementioned issues, the solution provided in this application mainly includes: First, establishing an event listening mechanism for the window management service after the vehicle system starts. When a first event corresponding to a window addition request for the target application is detected, the first moment corresponding to the first event is obtained. This window addition request is used to request the window management service to add the window component of the target application to display its associated components. Subsequently, when a second event corresponding to a window removal request for the target application is detected, the second moment corresponding to the second event is obtained. This window removal request is used to request the window management service to remove the window component of the target application. Finally, the usage duration information of the target application is determined based on the time difference between the first moment and the second moment. In this way, by listening to the window management service, all associated components displayed through window components under the target application can be accurately identified, thereby reflecting the usage status of the target application and improving the accuracy of the usage duration information of the target application.

[0057] The following will combine Figure 2 - Figure 12 The information acquisition method provided in the embodiments of this application will be described in detail.

[0058] Please see Figure 2 , Figure 2 This is a flowchart illustrating an information acquisition method provided in an embodiment of this application. Figure 2 As shown, the method in this application embodiment may include the following steps S101-S104.

[0059] S101 listens for events in the window management service of the vehicle infotainment system after the system starts up.

[0060] Specifically, the vehicle infotainment system involved in this embodiment refers to an embedded computer system installed in a vehicle to provide functions such as infotainment, vehicle control, and navigation services. It includes a processor, memory, input / output devices, and an operating system and application software running on a hardware platform. Vehicle infotainment system startup refers to the process from power-on to the completion of initialization and entry into an operable state. The window management service of the vehicle infotainment system refers to a system service used to manage the display of window components in the graphical user interface. Window components refer to visual components used to carry and display application content in the graphical user interface. Event listening refers to the process of obtaining specific events in the window management service in real time through methods such as registering callback functions or message hook mechanisms.

[0061] After the vehicle infotainment system starts up, event listening is performed on the system's window management service. Regarding this step, some possible implementations may include the following technical details: First, after the vehicle infotainment system starts up, an event listener is registered with the window management service to listen for events related to the service. Second, a window addition event refers to the event triggered when the window management service receives a request to add a new window component. Third, a window removal event refers to the event triggered when the window management service receives a request to remove an existing window component. Furthermore, these events may also include necessary information such as the event occurrence time, the target window identifier, and the application identifier.

[0062] S102, when the first event corresponding to the window addition request of the target application in the vehicle system is detected, the first moment corresponding to the first event is obtained. The window addition request is used to request the window management service to add the window component of the target application. The window component is used to display the associated components of the target application.

[0063] Specifically, the target application in this embodiment refers to any one of the multiple applications in the vehicle system that is being monitored; the associated component of the target application refers to the component that needs to be displayed through the window component; the first event refers to the system-level event triggered when the window management service receives the window addition request of the target application.

[0064] In some cases, the target application sends a window add request to the window management service to request the service to add its window component. This request may include the target application's identification information and the attribute information of the window component to be added. Correspondingly, the event listener detects the first event corresponding to the window add request received by the window management service. Further, it obtains the first moment corresponding to the first event, where the first moment refers to the system time recorded by the window management service when processing the target application's window add request, representing the time when the target application's window component begins to display. It is understood that this first moment can be saved to the relevant storage unit of the vehicle's infotainment system and associated with the target application's identification information.

[0065] S103, when the second event corresponding to the window removal request of the target application is detected, the second moment corresponding to the second event is obtained. The window removal request is used to request the window management service to remove the window component of the target application.

[0066] Specifically, the second event involved in this embodiment refers to a system-level event triggered when the window management service receives a window removal request from the target application.

[0067] In some cases, the target application sends a window removal request to the window management service to request the removal of its window components. This window removal request may include the target application's identification information and the attribute information of the window component to be removed. Correspondingly, the event listener detects the second event corresponding to the window removal request received by the window management service. Further, it obtains the second moment corresponding to the second event, where the second moment refers to the system time recorded by the window management service when processing the target application's window removal request, representing the time when the target application's window component ended its display. It is understood that this second moment can be saved to the relevant storage unit of the vehicle's infotainment system and associated with the target application's identification information.

[0068] S104, determine the usage duration information of the target application based on the first time and the second time.

[0069] Specifically, since the first moment and the second moment represent the time points when the target application's window component begins and ends displaying, respectively, the usage duration information of the target application can be determined based on the first moment and the second moment. The usage duration information of the target application refers to the duration data of the target application's window component continuously displayed in the vehicle's infotainment system. This duration data is measured in time units and stored in the vehicle's infotainment system's storage unit, associated with the target application's identification information.

[0070] In some possible implementations, the usage duration information of the target application can be directly obtained by calculating the difference between the second time point and the first time point. Specifically, this involves: retrieving the first and second time points corresponding to the target application's identifier information from the storage unit; subtracting the value of the first time point from the value of the second time point to obtain the time difference; and storing this time difference as the target application's usage duration information in the storage unit. It is understandable that this implementation method is suitable for standard scenarios where duration adjustment is not required.

[0071] In some possible implementations, after calculating the difference between the second time point and the first time point, compensation and / or subtraction processing can be performed to obtain the usage duration information of the target application. Specifically, this includes: retrieving the first time point and the second time point corresponding to the target application identification information from the storage unit; subtracting the value of the first time point from the value of the second time point to obtain the time difference; performing duration compensation processing on the time difference to obtain the compensated time difference; and storing the compensated time difference as the usage duration information of the target application in the storage unit.

[0072] Alternatively, retrieve the first and second time points corresponding to the target application identification information from the storage unit; subtract the value of the first time point from the value of the second time point to obtain the time difference; perform duration subtraction processing on the time difference to obtain the subtracted time difference, and store the subtracted time difference as the usage duration information of the target application in the storage unit.

[0073] Alternatively, retrieve the first and second time points corresponding to the target application identification information from the storage unit; subtract the value of the first time point from the value of the second time point to obtain the time difference; perform duration compensation and deduction processing on the time difference to obtain the compensated and deducted time difference, and store the compensated and deducted time difference as the usage duration information of the target application in the storage unit.

[0074] For a better understanding of this embodiment, please refer to [link / reference]. Figure 3 , Figure 3 This is an example diagram illustrating how to obtain usage time information based on a Window, as provided in this application embodiment. In an in-vehicle infotainment system on the Android platform, the window management service in this embodiment is WindowManagerService, the window component is Window, and the associated components of the target application include Activity and Service. The in-vehicle infotainment system also includes an activity management service ActivityManagerService.

[0075] For example, when the target application enters an Activity, the Activity first completes its own creation process, and then notifies the system to create the Activity and to add a Window. The step of notifying the system to create the Activity is implemented by calling the interface of ActivityManagerService, and the step of notifying the system to add a Window is implemented by sending a Window add request to WindowManagerService. After receiving the Window add request, WindowManagerService triggers an add event, which is captured by a pre-registered listener.

[0076] For example, when the target application exits an Activity, the Activity first performs a destruction process, and then notifies the system to destroy the Activity and remove the Window. The step of notifying the system to destroy the Activity is implemented by calling the interface of ActivityManagerService, and the step of notifying the system to remove the Window is implemented by sending a Window removal request to WindowManagerService. After receiving the Window removal request, WindowManagerService triggers a removal event, which is captured by a pre-registered listener.

[0077] For example, when a Service of the target application needs to display a screen, the Service notifies the system to add a Window by sending a Window add request to the WindowManagerService; after receiving the Window add request, the WindowManagerService triggers an add event, which is captured by a pre-registered listener.

[0078] For example, when a Service of the target application needs to hide the interface, the Service notifies the system to remove the Window by sending a Window removal request to the WindowManagerService; after receiving the Window removal request, the WindowManagerService triggers a removal event, which is captured by a pre-registered listener.

[0079] Understandably, by listening to WindowManagerService to achieve usage duration statistics, the final usage duration information not only reflects the existence of Activities in the target application, but also the existence of Services in the target application, effectively making up for the deficiency in related technologies that non-Activity pages cannot perceive.

[0080] In this embodiment, an event listening mechanism for the window management service is first established after the vehicle system starts. When a first event corresponding to a window addition request for the target application is detected, the first moment corresponding to the first event is obtained. This window addition request is used to request the window management service to add the window component of the target application to display its associated components. Subsequently, when a second event corresponding to a window removal request for the target application is detected, the second moment corresponding to the second event is obtained. This window removal request is used to request the window management service to remove the window component of the target application. Finally, the usage duration information of the target application is determined based on the time difference between the first moment and the second moment. In this way, by listening to the window management service, all associated components displayed through window components under the target application can be accurately identified, thereby reflecting the usage status of the target application and improving the accuracy of the usage duration information of the target application.

[0081] Please see Figure 4 This application provides a flowchart illustrating the process of obtaining usage duration information by deducting data in an embodiment of the present application. Figure 4 As shown, the method in this embodiment may include the following steps S201-S202, and steps S201-S202 may be used as a method for... Figure 2 The detailed steps of step S104 in the illustrated embodiment.

[0082] S201, determine the first duration information based on the first time point and the second time point;

[0083] S202, the first duration information is deducted based on the previously acquired invalid duration information to obtain the usage duration information of the target application. The invalid duration information is determined based on the operation information of the vehicle to which the vehicle system belongs between the first and second moments.

[0084] Specifically, the first duration information involved in this embodiment refers to the duration data calculated based on the first time and the second time; invalid duration information refers to the duration data that does not conform to the actual use scenario, determined based on the vehicle's operating information between the first time and the second time; and operating information refers to parameter data related to vehicle operation.

[0085] Regarding the process of determining the first duration information based on the first and second moments, in some possible implementations, the first and second moments corresponding to the target application can be obtained from the storage unit; the time difference between the second and first moments can be calculated, and this time difference can be stored in the storage unit as the first duration information. Alternatively, in some possible implementations, the first and second moments corresponding to the target application can be obtained from the storage unit; the time difference between the second and first moments can be calculated, duration compensation processing can be performed on this time difference, and the compensated time difference can be stored in the storage unit as the first duration information.

[0086] Regarding the process of deducting time from the first time information based on pre-acquired invalid time information to obtain the target application's usage time information, in some possible implementations, the invalid time information may include one time data to be deducted, and the usage time information of the target application is obtained by deducting this time data from the first time information. In some possible implementations, the invalid time information may include multiple time data to be deducted, and at least one of the multiple time data to be deducted is obtained by deducting at least one of the multiple time data to be deducted from the first time information to obtain the target application's usage time information.

[0087] In this embodiment, by introducing a mechanism to deduct invalid duration information, it is possible to eliminate non-real usage duration caused by vehicle operating status, thereby making the final usage duration information of the target application closer to the actual user usage, and improving the objectivity and accuracy of the usage duration information.

[0088] Please see Figure 5 This application provides a flowchart illustrating the process of obtaining invalid duration information. The running information includes at least speed information, or in addition to running mode information; the invalid duration information includes at least second duration information, or in addition to third duration information. Figure 5 As shown, the method in this application embodiment may further include the following steps S301-S304, wherein steps S303-S304 are optional.

[0089] S301, between the first and second moments, acquires vehicle speed information;

[0090] S302, if the speed information indicates that the vehicle's speed is greater than a preset speed threshold, then determine the second duration information based on the duration during which the speed is greater than the preset speed threshold.

[0091] S303, if the speed information indicates that the vehicle's driving speed is less than or equal to a preset speed threshold, then obtain the vehicle's operating mode information.

[0092] S304, if the operating mode information indicates that the vehicle is in sentry mode, then the third duration information is determined based on the duration during which the vehicle is in sentry mode.

[0093] Specifically, the speed information involved in this embodiment refers to the real-time speed data collected by the vehicle speed sensor and transmitted to the vehicle system during vehicle operation; the preset speed threshold refers to a pre-set critical value used to determine whether the vehicle is in a high-speed driving state, such as 15 km / h; the second duration information refers to the duration data corresponding to the continuous duration of the vehicle's driving speed being greater than the preset speed threshold; the operating mode information refers to data characterizing the vehicle's operating state, such as normal driving mode, sentry mode, energy-saving mode, etc.; sentry mode refers to the safety monitoring mode activated when the vehicle is stationary; and the third duration information refers to the duration data corresponding to the continuous duration of the vehicle being in sentry mode.

[0094] For a better understanding of this embodiment, please refer to the following: Figure 6 Figure 6 This is an example diagram illustrating how to obtain invalid duration information according to an embodiment of this application.

[0095] Regarding the process of acquiring vehicle speed information between the first and second moments, some possible implementations involve: first, the vehicle's infotainment system continuously acquiring speed data uploaded by the vehicle speed sensor at a preset sampling frequency; second, storing the acquired speed data along with its corresponding timestamp in the vehicle's cache; and finally, when it is necessary to calculate invalid duration, retrieving the speed data sequence between the first and second moments from the cache. It is understood that this speed data sequence can reflect all speed changes of the vehicle during the period the target application window is displayed.

[0096] Regarding the process of determining the second duration information based on the duration of the speed exceeding the preset speed threshold if the speed information indicates the vehicle's speed is greater than the preset speed threshold, some possible implementations involve first analyzing the acquired speed data sequence to identify all consecutive time periods where the speed value exceeds the preset speed threshold; secondly, calculating the cumulative duration of these consecutive time periods as the second duration information; and finally, associating and storing the second duration information with the target application's identification information. It is understandable that when a vehicle is traveling at high speed, users are typically focused on driving operations, and the statistical application usage time at this time may not accurately reflect user interaction.

[0097] Regarding the process of obtaining vehicle operating mode information if the speed information indicates that the vehicle's speed is less than or equal to a preset speed threshold, some possible implementations involve first obtaining the current vehicle operating mode status identifier through the vehicle's infotainment system; secondly, parsing the status identifier to determine whether the vehicle is in sentry mode; and finally, storing the operating mode information in association with the corresponding timestamp. It is understood that this step is only performed when the speed does not exceed the preset threshold to avoid unnecessary consumption of system resources.

[0098] Regarding the process of determining the third duration information based on the duration the vehicle is in sentry mode if the operating mode information indicates that the vehicle is in sentry mode, some possible implementations involve first analyzing the change records of the operating mode information to identify the continuous time periods during which the vehicle is in sentry mode; secondly, calculating the cumulative duration of these continuous time periods as the third duration information; and finally, associating and storing the third duration information with the target application's identification information. It is understandable that users are typically not in the vehicle during sentry mode, and the statistical application usage time in this situation may not reflect actual usage.

[0099] Understandably, if the operating mode information indicates that the vehicle is not in sentry mode, the recording of the third duration information will stop. In this case, only the second duration information determined based on the speed information will be retained as invalid duration information. Specifically, when the operating mode information indicates that the vehicle is in any mode other than sentry mode, the system will skip the calculation step of the third duration information and determine the invalid duration information to be deducted only based on the comparison result of the speed information and the preset speed threshold.

[0100] For example, when the first moment corresponding to the window addition request of the target application A is T1, and the second moment corresponding to the window removal request is T2: First, the vehicle speed information sequence V = {v1, v2, ..., vn} is obtained between the first moment T1 and the second moment T2; if it is detected that there are all speed values ​​v > preset speed threshold S (e.g., S = 15 km / h) in the speed information sequence within a continuous time period [t3, t4], then the duration of this time period L1 = t4 - t3 is calculated as the second duration information; if the speed value v ≤ S in the remaining time period, the operating mode information is obtained, and the continuous time period [t5, t6] in the sentry mode of the vehicle is identified, the duration L2 = t6 - t5 is calculated as the third duration information; finally, L1 and L2 are subtracted from the total duration T2 - T1 to obtain the usage time information of the target application A.

[0101] In this embodiment, by introducing a dual invalid duration determination mechanism based on speed information and operating mode information, the impact of vehicle operating status on application usage time statistics can be more accurately identified. Specifically, using high-speed driving and sentry mode as independent invalid duration determination conditions allows for differentiated deduction strategies for different scenarios, thus making the final determined usage time information more objective and accurate.

[0102] In one embodiment, based on Figure 5 The second and third duration information determined in the embodiment are for Figure 4 Step S202 of the illustrated embodiment can be further refined to include the following steps:

[0103] If the target application is a type 1 application, the second and third duration information are subtracted from the first duration information to obtain the usage duration information of the target application.

[0104] If the target application is a second type of application, the third duration information is subtracted from the first duration information to obtain the usage duration information of the target application. The interaction intensity of the first type of application is higher than that of the second type of application.

[0105] Specifically, the interaction intensity involved in this embodiment refers to the frequency and complexity of the application requiring users to perform input operations per unit time; the first type of application refers to the application category with an interaction intensity higher than the preset threshold, such as navigation applications and video playback applications, which require users to frequently perform touch or voice operations to achieve the function; the second type of application refers to the application category with an interaction intensity lower than the preset threshold, which only requires a small amount of user interaction or can run autonomously during operation, such as music playback applications and background download applications.

[0106] For a better understanding of this embodiment, please refer to the following: Figure 7 , Figure 7 This is an example diagram illustrating the deduction of invalid duration information provided in an embodiment of this application. Assuming that multiple applications in the vehicle system are divided into a first type of application and a second type of application, then if the target application is not a first type of application, the target application is a second type of application.

[0107] Regarding the process of subtracting the second and third duration information from the first duration information if the target application is a Type 1 application, some possible implementations involve first querying the interaction intensity classification identifier of the target application from the application attribute database; when the target application is identified as a Type 1 application, retrieving the second and third duration information associated with that target application from the storage unit; then subtracting the sum of the second and third duration information from the first duration information to obtain the usage duration information after deduction; finally, storing the calculation result in association with the target application identifier information. It is understandable that for Type 1 applications with high interaction intensity, usage durations recorded during high-speed vehicle travel or in sentry mode are invalid data and should be completely deducted.

[0108] Regarding the process of subtracting the third duration information from the first duration information if the target application is a second-type application, some possible implementations involve first querying the interaction intensity classification identifier of the target application from the application attribute database; when the target application is identified as a second-type application, retrieving the third duration information associated with that target application from the storage unit; secondly, subtracting the third duration information from the first duration information to obtain the deducted usage duration information; and finally, storing the calculation result in association with the target application identifier information. It is understandable that for second-type applications with low interaction intensity, usage duration statistics only in sentinel mode are invalid data, while users may still interact with the application through non-contact methods such as voice while driving at high speeds, therefore, data for that period is retained.

[0109] In some possible implementations, the criteria for classifying interaction intensity may include: first, counting the number of user operation events of the target application within a preset time period, including touch events, voice command events, and physical button events; second, calculating the operation event density value per unit time; when the density value exceeds a first threshold, it is classified as a first-type application, and when it is below a second threshold, it is classified as a second-type application, where the first threshold is greater than the second threshold. Furthermore, application classification information can be pre-set in the application configuration file of the vehicle system, or dynamically adjusted based on historical interaction data using a machine learning model.

[0110] For example, suppose the target application is a navigation application (a first type of application), with a first time point T1, a second time point T2, and a first duration information of T2-T1. Between the first time point T1 and the second time point T2, the duration for which the vehicle speed exceeds a preset speed threshold S is L1, and the duration for which it is in sentry mode is L2. According to the above scheme, subtracting the second duration information L1 and the third duration information L2 from the first duration information T2-T1 yields the target application's usage duration information as (T2-T1)-L1-L2. If the target application is a music playback application (a second type of application), then only the third duration information L2 is subtracted, resulting in the usage duration information as (T2-T1)-L2. The interaction intensity classification is based on the following criteria: the number of operation events N1 of the navigation application within the preset time period Δt exceeds the first threshold N_high, and the number of operation events N2 of the music playback application is lower than the second threshold N_low (N_high>N_low).

[0111] In this embodiment, by establishing a differentiated deduction strategy associated with the intensity of application interaction, it is possible to more accurately distinguish between real usage scenarios and invalid statistical periods. For the first type of application requiring high interaction, both high-speed driving and sentry mode periods are deducted; for the second type of application with low interaction requirements, only sentry mode periods are deducted. This hierarchical processing mechanism based on application characteristics avoids statistical distortion caused by excessive deduction and ensures the rationality of the deducted periods, thereby significantly improving the matching degree between usage time information and actual user usage.

[0112] Please see Figure 8 This application provides a flowchart illustrating the process of obtaining first duration information through compensation, as shown in the embodiment of the present application. Figure 8 As shown, the method in this embodiment may include the following steps S401-S403, and steps S401-S403 may be used as a method for... Figure 4 The detailed steps of step S201 in the illustrated embodiment.

[0113] S401, determine the fourth duration information based on the first and second time points;

[0114] S402, Obtain the fifth duration information of the target application, which indicates the duration to be compensated generated by the target application before the first moment;

[0115] S403, perform duration compensation on the fourth duration information based on the fifth duration information of the target application to obtain the first duration information.

[0116] Specifically, the fourth duration information involved in this embodiment refers to the initial duration data calculated based on the first time and the second time; the fifth duration information refers to the compensation duration data of the target application before the first time due to abnormal circumstances that resulted in incomplete recording of usage time; duration compensation refers to the process of superimposing the compensation duration data onto the initial duration data.

[0117] For a better understanding of this embodiment, please refer to the following: Figure 10 , Figure 10 This is an example diagram illustrating how compensation is used to obtain first duration information, as provided in an embodiment of this application.

[0118] Regarding the process of determining the fourth duration information based on the first and second moments, in some possible implementations, the first and second moments corresponding to the target application identification information are first retrieved from the vehicle system's storage unit; secondly, the numerical difference between the second and first moments is calculated as the fourth duration information; finally, the fourth duration information is associated with the target application identification information and stored in the storage unit. It can be understood that this fourth duration information represents the complete display cycle of the target application window from addition to removal.

[0119] Regarding the process of obtaining the fifth duration information of the target application, in some possible implementations, the fifth duration information is recorded by the vehicle system before the first moment and can be read from the vehicle system's storage unit. It is understandable that the fifth duration information reflects the display time that the target application did not complete the statistics for during the last abnormal interruption.

[0120] Regarding the process of compensating the fourth duration information based on the fifth duration information of the target application, in some possible implementations, the fourth and fifth duration information corresponding to the target application are first obtained from the storage unit; then, the values ​​of the fourth and fifth duration information are added together to obtain the compensated duration data; finally, the compensated duration data is stored in the storage unit as the first duration information. In some possible implementations, if the fifth duration information has been cleared, the fourth duration information can be directly determined as the first duration information.

[0121] For example, let T1 be the first time point corresponding to the window addition request of the target application, and T2 be the second time point corresponding to the window removal request. First, the fourth duration information, T2-T1, is calculated based on the first time point T1 and the second time point T2. Then, the fifth duration information, Δt, recorded by the target application before the first time point T1, is retrieved from the storage unit. Finally, the fourth duration information T2-T1 is added to the fifth duration information Δt to obtain the compensated first duration information, (T2-T1)+Δt. If the fifth duration information Δt is zero, then T2-T1 is directly used as the first duration information.

[0122] In this embodiment, firstly, a fourth duration information is determined based on the first and second moments. This fourth duration information reflects the basic usage time of the target application within the current statistical period. Then, a fifth duration information generated by the target application before the first moment is obtained. This fifth duration information records the compensation-pending duration of the target application that was not fully recorded in the previous statistical period due to system anomalies or other reasons. Finally, a duration compensation operation is performed between the fifth and fourth duration information to obtain the compensated first duration information. Thus, by introducing a compensation mechanism based on historical data, the problem of interrupted application usage time statistics caused by system anomalies can be effectively solved, ensuring the continuity and completeness of statistical data, thereby improving the accuracy and reliability of usage time information.

[0123] Please see Figure 9 This application provides a flowchart illustrating the process of obtaining fifth duration information based on a preset period, as shown in the embodiment of the present application. Figure 9 As shown, the method in this application embodiment may include the following steps S501-S502, which may be executed before the first moment.

[0124] S501, when the third event corresponding to the window addition request of the target application is detected, the third moment corresponding to the third event is obtained;

[0125] S502, based on a preset period, obtains the system time of the vehicle system and determines the fifth duration information of the target application based on the third time and the system time. The fifth duration information of the target application is cleared when the fourth event corresponding to the window removal request of the target application is detected.

[0126] Specifically, in this embodiment, the third event refers to the system-level event triggered when the window management service receives a window addition request from the target application; the third moment refers to the system moment recorded by the window management service when processing the window addition request from the target application before the first moment; the preset period refers to the time interval set in advance for periodically recording system moments; the system moment refers to the timestamp data of the current operation of the vehicle system; the fourth event refers to the system-level event triggered when the window management service receives a window removal request from the target application; and clearing refers to the operation of resetting the value of the fifth duration information recorded in the storage unit to zero.

[0127] Regarding the process of obtaining the third moment corresponding to the third event when a window add request for the target application is detected, some possible implementations involve first capturing the window add request received by the window management service through a pre-registered event listener; secondly, parsing the target application identifier and window component attribute information contained in the request; and finally, extracting the system time recorded when processing the request from the window management service's logs as the third moment. It can be understood that this third moment represents the time when the target application's window component begins to display and will serve as the base time for subsequent compensation calculations.

[0128] Regarding the process of acquiring the system time of the vehicle system based on a preset period and determining the fifth duration information of the target application based on the third time and the system time, some possible implementations involve first starting a timer to trigger the system time acquisition operation at a preset period (e.g., every minute); secondly, acquiring the current system time of the vehicle system each time it is triggered; then calculating the time difference between the current system time and the third time as a temporary compensation duration; and finally, accumulating and updating the temporary compensation duration with the existing fifth duration information in the storage unit. It is understandable that this periodic recording mechanism ensures that even if a system anomaly occurs, the timestamp data of the most recently recorded data can be retained.

[0129] Regarding the process of resetting the fifth duration information of the target application to zero when the fourth event corresponding to the window removal request of the target application is detected, some possible implementations involve first capturing the window removal request received by the window management service through an event listener; secondly, verifying whether the target application identifier corresponding to the request is consistent with the application identifier associated with the currently recorded fifth duration information; and after verification, resetting the fifth duration information field corresponding to the target application in the storage unit to zero. It is understood that this resetting operation is only performed when the target application exits normally, indicating that its usage time has been fully counted and no compensation is needed.

[0130] For example, when the third event corresponding to the window addition request of the target application occurs, the third moment is recorded as T3; then the system records the current system moment Tn every minute and calculates Tn-T3 as the temporary compensation duration ΔTn; if the system terminates abnormally at moment T4, the last recorded ΔTn is stored as the fifth duration information; when the system recovers and the target application restarts, the fifth duration information ΔTn is read from the storage unit to compensate for the usage duration of the new statistical period; finally, when the target application exits normally and triggers the fourth event, the fifth duration information is cleared to zero.

[0131] In this embodiment, by establishing a periodic compensation recording mechanism during the display of the target application window, usage time data that may be lost due to abnormal system interruptions can be saved in real time. Specifically, system time collection based on a preset period ensures the timeliness of the compensation data, while the zeroing operation when the window is removed maintains the statistical accuracy under normal circumstances, effectively solving the problem of data loss caused by system or application crashes.

[0132] Please see Figure 11 This application provides a flowchart illustrating the process of determining sub-duration information. The target application is configured to display screen-projected content from a mobile device connected to the vehicle's infotainment system. Figure 11 As shown, the method in this application embodiment may further include the following steps S601-S602.

[0133] S601, call the preset interface of the vehicle system to obtain the set of status notifications sent by the mobile device between the first moment and the second moment. The set of status notifications includes the status notifications of each sub-application in the mobile device.

[0134] S602, based on the status notification of each sub-application, determine the sub-duration information of each sub-application in the usage duration information.

[0135] Specifically, the target application involved in this embodiment is configured to display the screen projection content of a mobile device connected to the vehicle infotainment system. This refers to an application instance in the vehicle infotainment system specifically used to display the screen projection of a mobile device. The mobile device refers to a portable computing device such as a smartphone or tablet computer that establishes a data connection with the vehicle infotainment system via wired or wireless means. The preset interface refers to the communication interface in the vehicle infotainment system used to receive status notifications from the mobile device. The status notification set refers to the set of notification messages sent by the mobile device to the vehicle infotainment system between the first and second moments regarding changes in the running status of each sub-application. The sub-application refers to an independent application in the mobile device that displays its content on the vehicle infotainment system via screen projection. The sub-duration information refers to the duration data of each sub-application actually being in the foreground display state on the mobile device.

[0136] For a better understanding of this embodiment, please refer to the following: Figure 12 , Figure 12 This is an example diagram illustrating how a notification based on a mobile device determines the relevant time, as provided in an embodiment of this application.

[0137] Regarding the process of calling a preset interface in the vehicle infotainment system to obtain the set of status notifications sent by the mobile device between the first and second moments, some possible implementations involve first activating the preset interface through the communication link established between the vehicle infotainment system and the mobile device; secondly, the preset interface continuously listens for status notification messages sent by the mobile device and stores the received messages in a cache queue in chronological order; then, all status notification messages between the first and second moments are extracted from the cache queue to form the status notification set. It is understood that each message in this status notification set contains at least a sub-application identifier, a status change type (e.g., entering the foreground / exiting the foreground), and corresponding timestamp information.

[0138] Regarding the process of determining the sub-duration information of each sub-application from the usage duration information based on the status notifications of each sub-application, some possible implementations involve first parsing the status notification sequence of each sub-application in the status notification set to identify the complete display cycle of each sub-application; secondly, for each sub-application, calculating the cumulative duration of all its display cycles as the sub-duration information; and finally, associating and storing the sub-duration information of each sub-application with the usage duration information of the target application. It is understandable that for different sub-application content displayed by the same target application, their usage duration needs to be recorded separately to achieve accurate statistics.

[0139] For example, when the target application is configured to display the screen projection content of the mobile device: First, a communication connection is established between the vehicle system and the mobile device via Bluetooth and Wi-Fi Direct; Second, when sub-application A and sub-application B on the mobile device switch to the foreground, they respectively send status notifications to the vehicle system indicating "sub-application A enters the foreground", "sub-application A exits the foreground", "sub-application B enters the foreground", and "sub-application B exits the foreground"; Then, the vehicle system receives these notifications through a preset interface and records the corresponding time; Finally, the duration of sub-application A and sub-application B displayed in the foreground is calculated as their respective sub-duration information and stored in association with the total usage time information of the target application.

[0140] In this embodiment, by establishing a status notification transmission mechanism between the vehicle system and the mobile device, the actual usage status of each sub-application on the mobile device can be accurately obtained. The preset interface ensures the reception of status notifications, while the sub-duration calculation based on the notification sequence enables refined statistics of the projected content. This effectively solves the problem in related technologies of not being able to distinguish the usage time of mobile device sub-applications, making the application usage time statistics in the vehicle-to-vehicle interconnection scenario more comprehensive and accurate.

[0141] The following will combine Figure 13 The information acquisition device provided in the embodiments of this application will be described in detail. It should be noted that... Figure 13 The information acquisition device in the middle is used to execute this application. Figure 2 - Figure 12 The methods shown in the embodiments are for illustrative purposes only, illustrating the parts relevant to the embodiments of this application. For specific technical details not disclosed, please refer to this application. Figure 2 - Figure 12 The illustrated embodiment. Specifically, the information acquisition device 800 may include a monitoring unit 801, a first acquisition unit 802, a second acquisition unit 803, and a determination unit 804, as detailed below:

[0142] The listening unit 801 is used to listen for events of the window management service of the vehicle system after the vehicle system starts up.

[0143] The first acquisition unit 802 is used to acquire the first moment corresponding to the first event when the first event corresponding to the window addition request of the target application in the vehicle system is detected. The window addition request is used to request the window management service to add the window component of the target application. The window component is used to display the associated components of the target application.

[0144] The second acquisition unit 803 is used to acquire the second moment corresponding to the second event when the second event corresponding to the window removal request of the target application is detected. The window removal request is used to request the window management service to remove the window component of the target application.

[0145] The determining unit 804 is used to determine the usage duration information of the target application based on the first time and the second time.

[0146] Optionally, in some embodiments, the determining unit 804 may be used to: determine first duration information based on a first time moment and a second time moment;

[0147] The usage time information of the target application is obtained by deducting the time from the first time information based on the invalid time information obtained in advance. The invalid time information is determined based on the operation information of the vehicle to which the vehicle system belongs between the first time and the second time.

[0148] Optionally, in some embodiments, the running information includes speed information, and the invalid duration information includes second duration information. The information acquisition device 800 can be used to: acquire the vehicle's speed information between the first moment and the second moment; if the speed information indicates that the vehicle's driving speed is greater than a preset speed threshold, then determine the second duration information based on the duration during which the driving speed is greater than the preset speed threshold.

[0149] Optionally, in some embodiments, the operation information further includes operation mode information, and the invalid duration information further includes third duration information. The information acquisition device 800 can be used to: acquire the vehicle's operation mode information if the speed information indicates that the vehicle's driving speed is less than or equal to a preset speed threshold; and determine the third duration information based on the duration of the vehicle being in sentry mode if the operation mode information indicates that the vehicle is in sentry mode.

[0150] Optionally, in some embodiments, the determining unit 804 may be used to: if the target application is a first type of application, subtract the second duration information and the third duration information from the first duration information to obtain the usage duration information of the target application; if the target application is a second type of application, subtract the third duration information from the first duration information to obtain the usage duration information of the target application, wherein the interaction intensity of the first type of application is higher than that of the second type of application.

[0151] Optionally, in some embodiments, the determining unit 804 may be used to: determine fourth duration information based on a first time and a second time; obtain fifth duration information of the target application, wherein the fifth duration information indicates the duration to be compensated generated by the target application before the first time; and perform duration compensation on the fourth duration information based on the fifth duration information of the target application to obtain first duration information.

[0152] Optionally, in some embodiments, before the first moment, the information acquisition device 800 may be used to: acquire the third moment corresponding to the third event when the third event corresponding to the window addition request of the target application is detected; acquire the system time of the vehicle system based on a preset period and determine the fifth duration information of the target application based on the third moment and the system time; the fifth duration information of the target application is cleared when the fourth event corresponding to the window removal request of the target application is detected.

[0153] Optionally, in some embodiments, the target application is configured to display the screen projection content of the mobile device connected to the vehicle system. The information acquisition device 800 can be used to: call a preset interface in the vehicle system to obtain a set of status notifications sent by the mobile device between a first moment and a second moment, the set of status notifications including the status notifications of each sub-application in the mobile device; and determine the sub-duration information of each sub-application in the usage duration information based on the status notifications of each sub-application.

[0154] For the effects achievable in this embodiment, please refer to the relevant embodiments of the information acquisition method described above, which will not be repeated here.

[0155] Please see Figure 14 This provides a structural schematic diagram of a vehicle according to an embodiment of this application. Figure 14 As shown, the vehicle 900 includes a processor 901 and a memory 902. The processor 901 and the memory 902 are electrically connected.

[0156] The processor 901 is the control center of the vehicle 900 and may include one or more processing cores. The processor 901 connects to various parts of the vehicle 900 via various interfaces and lines. It executes various functions and processes data of the vehicle 900 by running or calling computer programs stored in the memory 902 and by calling data stored in the memory 902, thereby providing overall control of the vehicle 900. Optionally, the processor 901 may be implemented using at least one of the following hardware forms: Digital Signal Processing (DSP), Field Programmable Gate Array (FPGA), and Programmable Logic Array (PLA). The processor 901 may integrate one or more of the following: CPU, Graphics Processing Unit (GPU), and modem. The CPU primarily handles the operating system, user page, and applications; the GPU is responsible for rendering and drawing the displayed content; and the modem handles wireless communication. It is understood that the modem may also not be integrated into the processor 901 and may be implemented separately through a communication chip.

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

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

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

[0160] After the vehicle infotainment system starts up, perform event listening on the window management service of the vehicle infotainment system;

[0161] When the first event corresponding to the window addition request of the target application in the vehicle system is detected, the first moment corresponding to the first event is obtained. The window addition request is used to request the window management service to add the window component of the target application. The window component is used to display the associated components of the target application.

[0162] When the second event corresponding to the window removal request of the target application is detected, the second moment corresponding to the second event is obtained. The window removal request is used to request the window management service to remove the window component of the target application.

[0163] Based on the first and second time points, determine the usage duration information of the target application.

[0164] Optionally, when the processor 901 executes the process of determining the usage duration information of the target application based on the first time and the second time, it specifically performs the following: determining the first duration information based on the first time and the second time; deducting the duration of the first duration information based on the invalid duration information obtained in advance to obtain the usage duration information of the target application, wherein the invalid duration information is determined based on the operating information of the vehicle to which the vehicle system belongs between the first time and the second time.

[0165] Optionally, the running information includes speed information, and the invalid duration information includes second duration information; the processor 901 can also perform the following: between the first moment and the second moment, acquire the vehicle's speed information; if the speed information indicates that the vehicle's driving speed is greater than a preset speed threshold, then determine the second duration information based on the duration during which the driving speed is greater than the preset speed threshold.

[0166] Optionally, the operation information also includes operation mode information, and the invalid duration information also includes third duration information; after executing the action of determining the second duration information based on the duration of the speed exceeding the preset speed threshold if the speed information indicates that the vehicle's driving speed is greater than the preset speed threshold, the processor 901 further executes the following: if the speed information indicates that the vehicle's driving speed is less than or equal to the preset speed threshold, then the vehicle's operation mode information is obtained; if the operation mode information indicates that the vehicle is in sentry mode, then the third duration information is determined based on the duration of the vehicle being in sentry mode.

[0167] Optionally, when the processor 901 performs time deduction on the first time information based on the pre-acquired invalid time information to obtain the usage time information of the target application, it specifically performs the following: if the target application is a first type of application, the second time information and the third time information are deducted from the first time information to obtain the usage time information of the target application; if the target application is a second type of application, the third time information is deducted from the first time information to obtain the usage time information of the target application, wherein the interaction intensity of the first type of application is higher than that of the second type of application.

[0168] Optionally, when the processor 901 executes the process of determining the first duration information based on the first time and the second time, it specifically performs the following: determining the fourth duration information based on the first time and the second time; obtaining the fifth duration information of the target application, wherein the fifth duration information indicates the duration to be compensated generated by the target application before the first time; and performing duration compensation on the fourth duration information based on the fifth duration information of the target application to obtain the first duration information.

[0169] Optionally, before the first moment, the processor 901 also performs the following: when the third event corresponding to the window addition request of the target application is detected, the processor obtains the third moment corresponding to the third event; based on a preset period, the processor obtains the system time of the vehicle system and determines the fifth duration information of the target application according to the third moment and the system time; the fifth duration information of the target application is cleared when the fourth event corresponding to the window removal request of the target application is detected.

[0170] Optionally, the target application is configured to display the screen projection content of the mobile device connected to the vehicle system; the processor 901 also performs the following: calling a preset interface in the vehicle system to obtain a set of status notifications sent by the mobile device between a first moment and a second moment, the set of status notifications including the status notifications of each sub-application in the mobile device; and determining the sub-duration information of each sub-application in the usage duration information based on the status notifications of each sub-application.

[0171] For the effects achievable in this embodiment, please refer to the relevant embodiments of the information acquisition method described above, which will not be repeated here.

[0172] It should be understood that the apparatus provided in this application embodiment is used to perform the above-described information acquisition method, and therefore can achieve the same effect as the above-described implementation method.

[0173] When using an integrated unit, the device may include a processing module and a storage module. When the device is applied to a vehicle, the processing module can be used to control and manage the vehicle's movements. The storage module can be used to support the vehicle in executing relevant program code.

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

[0175] In addition, the device provided in this application embodiment may specifically be a chip, component or module. The chip may include a connected processor and a memory. The memory is used to store instructions. When the processor calls and executes the instructions, the chip can execute an information acquisition method provided in the above embodiment.

[0176] This application also provides a computer-readable storage medium storing computer program code. When the computer program code is run on a computer, the computer executes the aforementioned method steps to implement the information acquisition method provided in the above embodiments.

[0177] This embodiment also provides a computer program product that, when run on a computer, causes the computer to perform the aforementioned related steps to achieve the information acquisition method provided in the above embodiment.

[0178] In this embodiment, the device, computer-readable storage medium, computer program product, or chip are all used to execute the corresponding methods provided above. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods provided above, and will not be repeated here.

[0179] Through the above description of the embodiments, those skilled in the art will understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

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

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

Claims

1. An information acquisition method, characterized in that, The method includes: After the vehicle infotainment system starts up, the window management service of the vehicle infotainment system is monitored for events. When a first event corresponding to a window addition request of a target application in the vehicle system is detected, the first moment corresponding to the first event is obtained. The window addition request is used to request the window management service to add a window component of the target application. The window component is used to display the associated components of the target application. When the second event corresponding to the window removal request of the target application is detected, the second moment corresponding to the second event is obtained. The window removal request is used to request the window management service to remove the window component of the target application. Based on the first time point and the second time point, the usage duration information of the target application is determined.

2. The method according to claim 1, characterized in that, The step of determining the usage duration information of the target application based on the first time point and the second time point includes: Based on the first time point and the second time point, determine the first duration information; The usage time information of the target application is obtained by deducting the first duration information based on the invalid duration information obtained in advance. The invalid duration information is determined based on the operation information of the vehicle to which the vehicle system belongs between the first time and the second time.

3. The method according to claim 2, characterized in that, The operational information includes speed information, the invalid duration information includes second duration information, and the method further includes: Between the first time point and the second time point, the speed information of the vehicle is acquired; If the speed information indicates that the vehicle's speed is greater than a preset speed threshold, then a second duration information is determined based on the duration during which the speed is greater than the preset speed threshold.

4. The method according to claim 3, characterized in that, The operation information also includes operation mode information, and the invalid duration information also includes third duration information. After determining the second duration information based on the duration of the vehicle's speed exceeding the preset speed threshold if the speed information indicates that the vehicle's speed is greater than a preset speed threshold, the process further includes: If the speed information indicates that the vehicle's speed is less than or equal to the preset speed threshold, then the vehicle's operating mode information is obtained. If the operating mode information indicates that the vehicle is in sentry mode, then the third duration information is determined based on the duration during which the vehicle is in sentry mode.

5. The method according to claim 4, characterized in that, The step of deducting time from the first time information based on pre-acquired invalid time information to obtain the usage time information of the target application includes: If the target application is a first type of application, then the second duration information and the third duration information are subtracted from the first duration information to obtain the usage duration information of the target application; If the target application is a second type of application, the third duration information is subtracted from the first duration information to obtain the usage duration information of the target application, and the interaction intensity of the first type of application is higher than that of the second type of application.

6. The method according to claim 1, characterized in that, The step of determining the usage duration information of the target application based on the first time point and the second time point includes: Based on the first time point and the second time point, determine the fourth duration information; Obtain the fifth duration information of the target application, wherein the fifth duration information indicates the duration to be compensated generated by the target application before the first time point; The fourth duration information is compensated for based on the fifth duration information of the target application to obtain the first duration information; The usage time information of the target application is obtained by deducting the time from the first time information based on the previously acquired invalid time information.

7. The method according to claim 6, characterized in that, Prior to the first moment, the method further includes: When a third event corresponding to a window addition request of the target application is detected, the third moment corresponding to the third event is obtained; Based on a preset period, the system time of the vehicle system is obtained, and the fifth duration information of the target application is determined according to the third time and the system time. The fifth duration information of the target application is cleared when the fourth event corresponding to the window removal request of the target application is detected.

8. The method according to claim 1, characterized in that, The target application is configured to display screen-projected content from a mobile device connected to the vehicle infotainment system, and the method further includes: Call the preset interface of the vehicle system to obtain the set of status notifications sent by the mobile device between the first time and the second time, the set of status notifications including the status notifications of each sub-application in the mobile device; Based on the status notifications of each of the sub-applications, the sub-duration information of each sub-application is determined from the usage duration information.

9. A vehicle, characterized in that, include: Memory, used to store executable program code; A processor for calling and running the executable program code from the memory, causing the vehicle to perform the method as described in any one of claims 1 to 8.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer program code that, when executed, implements the method as described in any one of claims 1 to 8.

Images