Vehicle warning notification pushing method, electronic device and vehicle

Abstract

This application provides a vehicle alarm notification push method, electronic device, and vehicle. The method acquires alarm information of a target vehicle and vehicle control session data associated with the target vehicle. When the alarm type in the alarm information is not an unauthorized operation alarm, and an active vehicle control session is confirmed to exist based on the vehicle control session data, the alarm level and vehicle alarm notification are determined according to the alarm information. Based on the alarm level and session user permission information in the active vehicle control session, a first push target and a first push method are determined, and the vehicle alarm notification is pushed to the first push target according to the first push method. This invention utilizes alarm information to distinguish alarm levels and combines the alarm level with the session user permission information of the active vehicle control session for decision analysis, dynamically matching the alarm push target and alarm push method. This achieves accurate push of vehicle alarm notifications in multi-user vehicle usage scenarios and improves the rationality of the push method.

Description

Technical Field

[0001] This application relates to the field of information push technology, and in particular to a vehicle alarm notification push method, electronic device, and vehicle. Background Technology

[0002] With the increasing prevalence of intelligent connected vehicles, the way vehicle alarm information is pushed needs to meet diverse usage scenarios, such as family sharing, chauffeur services, and shared mobility. Currently, regardless of whether the vehicle is being used by the owner or other authorized users (chauffeur, family members, or borrowers), vehicle alarm information is consistently pushed to the owner via an app notification, which is insufficient to meet the needs of multi-user scenarios. On one hand, the owner is disturbed by invalid alarms, while the actual user experiences delayed response due to not receiving timely notifications, resulting in inaccurate targeting of vehicle alarm information in multi-user scenarios. On the other hand, using the same push strategy for vehicle alarms of varying urgency levels leads to over-prompting of low-risk alarms and easy omission of high-risk alarms, making the vehicle alarm information push method unreasonable in multi-user scenarios. Summary of the Invention

[0003] This application provides a vehicle alarm notification push method, electronic device, and vehicle, aiming to improve the problems of inaccurate push targets and unreasonable push methods for vehicle alarm notifications in multi-user vehicle use scenarios.

[0004] A method for pushing vehicle alarm notifications includes: Obtain alarm information of the target vehicle, as well as vehicle control session data associated with the target vehicle; If the alarm type in the alarm information is not an unauthorized operation alarm, and it is confirmed that there is an active vehicle control session based on the vehicle control session data, then the alarm level and vehicle alarm notification shall be determined based on the alarm information. Based on the alarm level and the session user permission information in the active vehicle control session, a first push target and a first push method are determined, and the vehicle alarm notification is pushed to the first push target according to the first push method.

[0005] This invention addresses scenarios where no unauthorized operation alarms have occurred in vehicles. It differentiates alarm levels using alarm information and combines alarm level with session user permission information from active vehicle control sessions for decision analysis. This dynamically matches alarm push targets and push methods, achieving accurate vehicle alarm notification delivery in multi-user scenarios. On one hand, this invention solves the problem of existing technologies failing to distinguish the actual vehicle user through active session detection, avoiding excessive notifications to the vehicle owner and ensuring timely delivery of vehicle alarm notifications to the appropriate users. On the other hand, this invention adapts differentiated alarm push methods for vehicle alarm notifications of different risk levels, reducing alarm interference or omissions, improving the rationality of push methods, and ensuring vehicle safety and user experience in multi-user scenarios.

[0006] Furthermore, after acquiring the alarm information of the target vehicle and the vehicle control session data associated with the target vehicle, the process further includes: If the alarm type in the alarm information is not an unauthorized operation alarm, and it is confirmed according to the vehicle control session data that there is currently no active vehicle control session, the alarm level and vehicle alarm notification shall be determined according to the alarm information. Based on the alarm level, a second push method and a second push target are determined, and the vehicle alarm notification is pushed to the second push target according to the second push method.

[0007] This embodiment addresses scenarios where no unauthorized operation alarm has occurred and there is currently no active vehicle control session. By simply adapting differentiated alarm push methods to vehicle alarm notifications based on different risk levels, it can more quickly determine the appropriate push method and target audience.

[0008] Furthermore, after acquiring the alarm information of the target vehicle and the vehicle control session data associated with the target vehicle, the process further includes: When the alarm type in the alarm information is an unauthorized operation alarm, and it is confirmed according to the vehicle control session data that there is no active vehicle control session, the vehicle alarm notification is determined according to the alarm information, the target vehicle owner is identified as the third push object, and the vehicle alarm notification is pushed to the third push object according to the preset unauthorized alarm method. If the alarm type in the alarm information is an unauthorized operation alarm, and it is confirmed that there is an active vehicle control session based on the vehicle control session data, a vehicle alarm notification is determined based on the alarm information. The target vehicle owner and the session user of the active vehicle control session are identified as the fourth push object, and the vehicle alarm notification is pushed to the fourth push object according to the preset unauthorized alarm method.

[0009] This embodiment establishes a dedicated alarm push method for scenarios involving unauthorized operations, eliminating the need to analyze alarm levels. It simply determines different push targets based on active vehicle control sessions, allowing vehicle owners to promptly understand situations involving unauthorized vehicle permissions and improving vehicle usage safety.

[0010] Further, after acquiring the alarm information of the target vehicle and the vehicle control session data associated with the target vehicle, the process includes: When the vehicle control session status in the vehicle control session data is online login status, and the vehicle control interruption duration in the vehicle control session data exceeds a preset interruption duration threshold, it is confirmed that there is currently an active vehicle control session. If the vehicle control session is offline or the vehicle control interruption duration exceeds a preset interruption duration threshold, it is confirmed that there is currently no active vehicle control session.

[0011] This embodiment judges active vehicle control sessions by combining data from both vehicle control session status and vehicle control interruption duration, accurately identifies the actual user of the current vehicle, provides a basis for decision-making on push targets, ensures that alarm notifications are pushed to the most needed targets, avoids response delays, and improves alarm processing efficiency.

[0012] Furthermore, determining the alarm level based on the alarm information includes: Based on the current alarm type in the alarm information, an alarm level is determined from multiple candidate levels in a preset type level mapping table; each candidate level in the preset type level mapping table is associated with at least one alarm type; the candidate levels include high-risk alarm level, medium-risk alarm level, and low-risk alarm level.

[0013] This embodiment provides a unified and clear classification standard for different alarm types through a preset type-level mapping table, making the alarm handling process more standardized and regulated. At the same time, by clearly defining alarm levels, this embodiment provides a basis for subsequent decisions regarding push targets and push methods, ensuring the rationality of the push strategy.

[0014] Furthermore, the alarm levels include high-risk alarm levels, medium-risk alarm levels, and low-risk alarm levels; the session user permission information includes the session user's alarm receiving permissions and authorization validity period, which are determined by the session user's user type; The step of determining the first push target and the first push method based on the alarm level and the session user permission information in the active vehicle control session includes: When the alarm level is a high-risk alarm level, if the alarm receiving permission includes the high-risk alarm receiving permission and the authorization validity period has not expired, then the target vehicle owner and the session user of the active vehicle control session are determined as the first push object, and the first push method is determined to be vehicle control application notification, SMS notification and telephone notification. When the alarm level is a medium-risk alarm level, if the alarm receiving permission includes the medium-risk alarm receiving permission and the authorization validity period has not expired, then the session user of the active vehicle control session is determined as the first push target, and the first push method is determined to be vehicle control application notification and SMS notification. When the alarm level is a low-risk alarm level, if the alarm receiving permission includes low-risk alarm receiving permission and the authorization validity period has not expired, then the session user of the active vehicle control session is determined as the first push target, and the first push method is determined to be vehicle control application notification.

[0015] This embodiment applies the user permission scope and authorization validity period of the current active vehicle control session to the decision-making of alarm push targets. It reflects a two-dimensional matching mechanism of permissions and sessions under different alarm levels, solves the problem of inaccurate push targets, avoids vehicle owners being disturbed by frequent alarms, and ensures that the authorized person who actually uses the vehicle receives the alarm in a timely manner, thereby improving alarm response efficiency.

[0016] Furthermore, the alarm levels include high-risk alarm levels, medium-risk alarm levels, and low-risk alarm levels; The step of determining the second push method and the second push target based on the alarm level includes: When the alarm level is a high-risk alarm level, the owner of the target vehicle is identified as the second push recipient, and the second push method is determined to be vehicle control application notification, SMS notification, and telephone notification. When the alarm level is a medium-risk alarm level, the owner of the target vehicle is identified as the second push recipient, and the second push method is determined to be a vehicle control application notification. When the alarm level is a low-risk alarm level, the session user of the next active vehicle control session is determined as the second push target, and the second push method is determined to be to push the vehicle control application notification during the next active vehicle control session.

[0017] This embodiment addresses the issue of homogenized push strategies by employing a dynamic decision-making push strategy and multiple selectable push methods to match different alarm levels. High-risk alarms are pushed urgently through multiple parallel channels to avoid omissions. Medium- and low-risk alarms are pushed on demand to reduce information overload and balance security and convenience.

[0018] Furthermore, the alarm levels include high-risk alarm levels, medium-risk alarm levels, and low-risk alarm levels; The step of pushing the vehicle alarm notification to the first push recipient includes: Obtain the push do-not-disturb period corresponding to the first push object, and detect whether the current time point is within the push do-not-disturb period; If the current time is not within the push do-not-disturb period, or if the current time is within the push do-not-disturb period but the alarm level is a high-risk alarm level, the vehicle alarm notification will be pushed to the first push recipient in real time. If the current time is within the push notification do-not-disturb period and the alarm level is a medium-risk alarm level or a low-risk alarm level, the vehicle alarm notification will be pushed to the first push recipient after the push notification do-not-disturb period ends.

[0019] This embodiment avoids users receiving frequent vehicle alarm notifications by determining do-not-disturb periods, reducing unnecessary interference and improving user experience. Users can customize do-not-disturb periods according to their actual needs, reflecting personalized choices and increasing flexibility. For high-risk alarm levels, notifications will still be pushed in real time even during do-not-disturb periods, ensuring that users do not miss important information.

[0020] An electronic device includes a processor and a memory, wherein Memory, used to store computer programs; The processor is used to execute the program stored in the memory to implement the above-mentioned vehicle alarm notification push method.

[0021] A vehicle comprising the aforementioned electronic equipment. Attached Figure Description

[0022] Figure 1 This is a schematic diagram illustrating an application scenario of the vehicle alarm notification push method provided in an embodiment of this application; Figure 2 This is a flowchart illustrating a vehicle alarm notification push method provided in an embodiment of this application; Figure 3 This is a flowchart illustrating step S201 of the vehicle alarm notification push method provided in an embodiment of this application; Figure 4 This is another flowchart illustrating step S201 of the vehicle alarm notification push method provided in an embodiment of this application; Figure 5 This is another flowchart illustrating step S201 in the vehicle alarm notification push method provided in an embodiment of this application; Figure 6 This is a flowchart illustrating step S203 of the vehicle alarm notification push method provided in an embodiment of this application; Figure 7This is a flowchart illustrating step S302 of the vehicle alarm notification push method provided in an embodiment of this application; Figure 8 This is another flowchart illustrating step S203 in the vehicle alarm notification push method provided in an embodiment of this application; Figure 9 This is a structural diagram of the electronic device provided in the embodiments of this application. Detailed Implementation

[0023] To make the technical problems, technical solutions, and beneficial effects solved by this application clearer, the following detailed description is provided in conjunction with embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0024] Terminology Explanation Please refer to this application. Figure 1 The vehicle alarm notification push method is applied to scenarios where communication connections exist between the vehicle, server, and user terminal. The server receives alarm information sent by the vehicle, processes the alarm information to generate alarm notifications, and sends the alarm notifications to the user terminal. In one specific embodiment, the vehicle collects alarm information in real time through data acquisition components, including but not limited to sensors, in-vehicle T-BOX, CAN bus, and vehicle infotainment system. Data transmission between the vehicle and server uses an encryption protocol (such as TLS 1.3) to ensure that the alarm information is not tampered with. The server can be an in-vehicle server integrated into the vehicle or a cloud server. The user terminal is used to receive alarm notifications sent by the server, and the user terminal includes but is not limited to the vehicle owner's APP terminal, a session user APP terminal with remote vehicle control authorization, an SMS terminal, and a voice telephone terminal.

[0025] Specifically, the target vehicle refers to the vehicle for which the vehicle-side determines an alarm needs to be triggered based on specified logic. Alarm information is used to characterize an abnormal or risky situation in the target vehicle. Alarm information includes, but is not limited to, alarm type, alarm time, and target vehicle location; it may also include driving status (stationary or moving), network environment (4G / 5G / WiFi), etc., as needed. Alarm type distinguishes the specific categories of alarms required in different scenarios, including but not limited to anti-theft alarms, abnormal startup, abnormal unlocking, collision alarms, fence crossing, unlocked doors, abnormal tire pressure, low battery, maintenance reminders, device offline, and unauthorized operation alarms. Alarm information can include only one alarm type or multiple alarm types simultaneously (e.g., unlocked doors, abnormal tire pressure, and low battery all occurring at the same time). Since different alarm types may correspond to different push targets and push methods, when alarm information includes multiple alarm types, the server generates a corresponding vehicle alarm notification for each alarm type and pushes it according to its respective push target and push method. Alarm time refers to the exact moment the alarm occurred, accurate to the year, month, day, hour, minute, and second. Target vehicle location refers to the vehicle's geographical location at the time the alarm occurred, which can be represented by latitude and longitude coordinates, specific road names, and mileage markers. Vehicle control session data refers to the interactive record data generated during communication between the target vehicle and the vehicle control application client. The vehicle owner or authorized user can log in to the vehicle control application client using their vehicle control application account to establish a vehicle control session with the target vehicle, enabling remote control operations such as unlocking the vehicle.

[0026] Unauthorized operation alarms refer to alarm types triggered when a user with specified control permissions operates the vehicle beyond their authorized limits. For example, a temporarily authorized user may attempt to start the vehicle even though they only have the permission to unlock it. Vehicle owners can pre-set different user types for authorized users and assign corresponding user permission information to each type. This information includes vehicle control permissions (such as unlocking, starting, and air conditioning control) and alarm receiving permissions (such as whether they can receive alarm notifications at high, medium, and low risk levels), as well as the authorization validity period. Specifically, user types include the vehicle owner, primary authorized users (such as family members), and temporary authorized users (such as designated drivers or shared users). Each authorized user has their own identity information (such as name and mobile phone number) and a vehicle control application account to establish a vehicle control session. That is, each vehicle control session user corresponds to a user type, and different user types correspond to different user permission information. Pre-set unauthorized operation alarm methods refer to pre-defined specific notification push methods used to notify users when an unauthorized operation alarm occurs. Unauthorized operation alarms are a special type of alarm and do not belong to any alarm level. For alarm types other than unauthorized operation alarms, it is necessary to first determine the alarm level corresponding to the alarm type, and then determine the corresponding notification push method according to different alarm levels.

[0027] An active vehicle control session refers to an ongoing and active communication session between the current vehicle and the control application client. Session user permission information refers to the user permission information corresponding to the user in the current vehicle control session. Vehicle control session data can record information such as session ID, login device, login time, vehicle control session status (online or offline), and vehicle control interruption time. The vehicle control session status includes online login status and offline status. Online login status means the user has successfully established a session connection with the target vehicle through authentication. Offline status means the user has not yet established a connection with the target vehicle, or the session is temporarily terminated. Vehicle control interruption duration refers to the interval between the user and the target vehicle after the last session interaction. The preset interruption duration threshold is a pre-set threshold value used to change the current session from active to temporarily terminated. The preset interruption duration threshold can be set to a default value or adjusted as needed, such as a default value of 30 minutes.

[0028] Alarm levels refer to the risk levels categorized according to different alarm types. The number of alarm levels can be adjusted as needed. For example, alarm levels may include three levels: high-risk, medium-risk, and low-risk, also known as Level 1, Level 2, and Level 3 alarms. A preset type-level mapping table is a data table where vehicle owners pre-configure the mapping relationships between different alarm types and alarm levels, stored in a structured data format. Candidate levels refer to the alarm levels pre-set in the preset type-level mapping table that have mapping relationships with different alarm types. In a specific preset type-level mapping table, alarm types mapped to the high-risk alarm level include unauthorized intrusion, stolen vehicle start-up, collision alarm, fence crossing, abnormal engine start-up, and abnormal remote account login (from a different location or with a different device). Alarm types mapped to the medium-risk alarm level include unlocked doors, open windows, abnormal tire pressure, low battery, brake system warning, and low engine oil. Alarm types that are mapped to low-risk alarm levels include maintenance reminders, filter replacement reminders, general vehicle condition inquiry feedback, and charging completion reminders.

[0029] A vehicle alarm notification is a message sent by the server to a designated user's terminal to alert them that a vehicle alarm has occurred. In addition to the alarm type, other information is required when generating a vehicle alarm notification. Specifically, a vehicle alarm notification consists of the alarm type, alarm time, vehicle location, and handling suggestions, with each alarm type corresponding to a specific handling suggestion. For example, a vehicle alarm notification could be: "Your vehicle experienced a fence crossing alarm on [Date] at 15:30. The current location is [City], [District], [Road]. It is recommended to check the remote vehicle control app to confirm the vehicle's status."

[0030] The server pre-establishes a decision rule base. This base represents the rules governing different push targets and methods for vehicle alarm notifications, depending on whether the alarm type in the alarm information includes an unauthorized operation alarm, and whether an active vehicle control session exists. The server analyzes the alarm level and / or the session user permission information in the active vehicle control session based on the decision rule base to determine the push targets and methods for vehicle alarm notifications. Different alarm levels and session user permission information in the active vehicle control session are used. The push target refers to the user actually receiving the vehicle alarm notification, and the push method refers to the actual channel and order in which the vehicle alarm notification is sent. The first push target and first push method refer to the push targets and methods when the alarm type in the alarm information does not include an unauthorized operation alarm and an active vehicle control session exists. The second push target and second push method refer to the push targets and methods when the alarm type in the alarm information does not include an unauthorized operation alarm and no active vehicle control session exists. The third push target refers to the push targets when the alarm type in the alarm information is an unauthorized operation alarm and no active vehicle control session exists. The fourth push target refers to the target audience when the alarm type in the alarm information is an unauthorized operation alarm and there is an active vehicle control session. The decision rule base also includes pre-defined push notification do-not-disturb periods set by vehicle owners and authorized users of different user types. These do-not-disturb periods are specific time periods set by users to pause push notifications (e.g., 23:00-07:00). Specifically, vehicle alarm notifications of high-risk alarm levels and unauthorized operation alarms are not subject to push notification do-not-disturb periods. Furthermore, the decision rule base also includes specific alarm types that vehicle owners can customize to reject notifications, such as rejecting maintenance reminders.

[0031] Push notifications can be sent via one or more of the following methods: vehicle control app notifications, SMS notifications, and phone notifications. Vehicle control app notifications refer to sending notification messages to the user through the vehicle control app client. When multiple push methods are used, there are different priorities among vehicle control app notifications, SMS notifications, and phone notifications; for example, vehicle control app notifications have higher priority than SMS notifications, and SMS notifications have higher priority than phone notifications. The server determines the order of push methods according to priority. If a notification message from a higher-priority push method does not receive a response within a preset time or fails to send, a lower-priority push method is used to continue sending until the message is successfully sent or all push methods fail, at which point the vehicle alarm notification is terminated. Specifically, when the push methods include vehicle control app notifications, SMS notifications, and phone notifications, the server uses vehicle control app notifications to send vehicle alarm notifications to the vehicle owner and obtains the message reading status of the vehicle owner's vehicle control app client. If the message reading status remains unread for 3 minutes, the server uses SMS notifications to send vehicle alarm notifications to the vehicle owner and obtains the SMS sending status. If the SMS sending status is "failed to send," the server uses phone notifications to send vehicle alarm notifications to the vehicle owner. Specifically, the same vehicle alarm notification will not be pushed to the same user repeatedly within 10 minutes.

[0032] This application provides a vehicle alarm notification push method, which is illustrated using an in-vehicle server as an example. Please refer to [link / reference]. Figure 2 This includes the following steps: S201: Obtain the alarm information of the target vehicle, as well as the vehicle control session data associated with the target vehicle; S202: When the alarm type in the alarm information is not an unauthorized operation alarm, and it is confirmed that there is an active vehicle control session based on the vehicle control session data, the alarm level and vehicle alarm notification are determined based on the alarm information. S203: Based on the alarm level and the session user permission information in the active vehicle control session, determine the first push target and the first push method, and push the vehicle alarm notification to the first push target according to the first push method.

[0033] Understandably, the server obtains the target vehicle's alarm information and vehicle control session data. First, the server cleans (e.g., removes abnormal data) and standardizes the format of the raw data in the alarm information to generate structured alarm information. Next, the server determines whether the alarm type in the structured alarm information is an unauthorized operation alarm. If the alarm type is not an unauthorized operation alarm, the server determines the alarm level and vehicle alarm notification based on the alarm information. Then, the server determines whether an active vehicle control session exists based on the vehicle control session data. If an active vehicle control session is confirmed, the server analyzes the alarm level and the session user permission information in the active vehicle control session based on a decision rule base to obtain the first push target and the first push method. Finally, the server pushes the vehicle alarm notification to the first push target according to the first push method.

[0034] This embodiment addresses scenarios where no unauthorized operation alarms have occurred. It differentiates alarm levels using alarm information and combines the alarm level with the session user permission information of active vehicle control sessions for decision analysis. This dynamically matches the alarm push target and alarm push method, achieving accurate vehicle alarm notification delivery in multi-user scenarios. On one hand, this embodiment solves the problem of existing technologies being unable to distinguish the actual user through active session detection, avoiding excessive notifications to the vehicle owner and ensuring timely delivery of vehicle alarm notifications to the appropriate users. On the other hand, this embodiment adapts differentiated alarm push methods for vehicle alarm notifications of different risk levels, reducing alarm interference or omissions, improving the rationality of the push method, and ensuring vehicle safety and user experience in multi-user scenarios.

[0035] In one embodiment, please refer to Figure 3 In step S201, after obtaining the alarm information of the target vehicle and the vehicle control session data associated with the target vehicle, the following steps are also included: S301: When the alarm type in the alarm information is not an unauthorized operation alarm, and it is confirmed according to the vehicle control session data that there is no active vehicle control session, the alarm level and vehicle alarm notification are determined according to the alarm information. S302: Based on the alarm level, determine the second push method and the second push target, and push the vehicle alarm notification to the second push target according to the second push method.

[0036] Understandably, when the alarm type in the alarm information is not an unauthorized operation alarm, if the server confirms based on the vehicle control session data that there is currently no active vehicle control session, it indicates that the server cannot obtain the session user permission information in the active vehicle control session. In this case, the server analyzes the alarm level based on the decision rule base to obtain the second push target and the second push method. Further, the server pushes the vehicle alarm notification to the second push target according to the second push method.

[0037] This embodiment addresses scenarios where no unauthorized operation alarm has occurred and there is currently no active vehicle control session. By simply adapting differentiated alarm push methods to vehicle alarm notifications based on different risk levels, it can more quickly determine the appropriate push method and target audience.

[0038] In one embodiment, please refer to Figure 4 In step S201, after obtaining the alarm information of the target vehicle and the vehicle control session data associated with the target vehicle, the following steps are also included: S401: When the alarm type in the alarm information is an unauthorized operation alarm, and it is confirmed according to the vehicle control session data that there is no active vehicle control session, the vehicle alarm notification is determined according to the alarm information, the target vehicle owner is determined as the third push object, and the vehicle alarm notification is pushed to the third push object according to the preset unauthorized alarm method. S402: When the alarm type in the alarm information is an unauthorized operation alarm, and it is confirmed that there is an active vehicle control session based on the vehicle control session data, a vehicle alarm notification is determined based on the alarm information. The target vehicle owner and the session user of the active vehicle control session are identified as the fourth push object, and the vehicle alarm notification is pushed to the fourth push object according to the preset unauthorized alarm method.

[0039] Understandably, when the alarm information includes unauthorized operation alarms, the server determines whether the alarm information only includes unauthorized operation alarms. If the alarm information only includes unauthorized operation alarms, the server does not need to analyze the alarm level and directly determines the vehicle alarm notification based on the alarm information. Next, the server determines whether there is an active vehicle control session based on the vehicle control session data. For unauthorized operation alarms, the push method is the same regardless of whether there is an active vehicle control session, and the preset unauthorized operation alarm method is used. The specific preset unauthorized operation alarm methods are vehicle control application notification and SMS notification. If it is confirmed that there is no active vehicle control session, the server only identifies the target vehicle owner as the third push target and pushes the vehicle alarm notification to the third push target according to the preset unauthorized operation alarm method. If it is confirmed that there is an active vehicle control session, the target vehicle owner and the session users of the active vehicle control session are both identified as the fourth push target, and the vehicle alarm notification is pushed to the fourth push target according to the preset unauthorized operation alarm method.

[0040] If the alarm information includes not only unauthorized operation alarms but also other alarm types that are not unauthorized operation alarms, then the unauthorized operation alarms will be analyzed separately to determine the push method and push recipients. For alarm information of other types, the process described above for alarms whose alarm type is not an unauthorized operation alarm will be followed. That is, based on the alarm information, the alarm level and vehicle alarm notification will be determined, and it will be further confirmed whether there is an active vehicle control session until the corresponding push method and push recipients are determined through analysis.

[0041] This embodiment establishes a dedicated alarm push method for scenarios involving unauthorized operations, eliminating the need to analyze alarm levels. It simply determines different push targets based on active vehicle control sessions, allowing vehicle owners to promptly understand situations involving unauthorized vehicle permissions and improving vehicle usage safety.

[0042] In one embodiment, please refer to Figure 5 Step S201, that is, after obtaining the alarm information of the target vehicle and the vehicle control session data associated with the target vehicle, includes the following steps: S501: When the vehicle control session status in the vehicle control session data is online login status, and the vehicle control interruption duration in the vehicle control session data exceeds the preset interruption duration threshold, it is confirmed that there is currently an active vehicle control session. S502: When the vehicle control session is offline or the vehicle control interruption duration exceeds a preset interruption duration threshold, confirm that there is currently no active vehicle control session.

[0043] Understandably, when determining whether an active vehicle control session exists based on the vehicle control session data, the server needs to simultaneously check the vehicle control session status and the vehicle control interruption duration. Only when the vehicle control session status in the data is "online login" and the vehicle control interruption duration exceeds a preset interruption duration threshold can an active vehicle control session be confirmed. Otherwise, an active vehicle control session is confirmed to not exist.

[0044] This embodiment judges active vehicle control sessions by combining data from both vehicle control session status and vehicle control interruption duration, accurately identifies the actual user of the current vehicle, provides a basis for decision-making on push targets, ensures that alarm notifications are pushed to the most needed targets, avoids response delays, and improves alarm processing efficiency.

[0045] In one embodiment, step S202, namely determining the alarm level based on the alarm information, includes: Based on the current alarm type in the alarm information, an alarm level is determined from multiple candidate levels in a preset type level mapping table; each candidate level in the preset type level mapping table is associated with at least one alarm type; the candidate levels include high-risk alarm level, medium-risk alarm level, and low-risk alarm level.

[0046] Understandably, when determining the alarm level corresponding to an alarm message, the server queries a preset type-level mapping table based on the current alarm type in the alarm message, and determines the candidate level that has a mapping relationship with the current alarm type as the actual alarm level. The candidate levels in the preset type-level mapping table include high-risk alarm level, medium-risk alarm level, and low-risk alarm level. For each current alarm type in the alarm message, a corresponding alarm level can be found, and the alarm level corresponding to the current alarm type is one of the high-risk, medium-risk, and low-risk alarm levels.

[0047] This embodiment provides a unified and clear classification standard for different alarm types through a preset type-level mapping table, making the alarm handling process more standardized and regulated. At the same time, by clearly defining alarm levels, this embodiment provides a basis for subsequent decisions regarding push targets and push methods, ensuring the rationality of the push strategy.

[0048] In one embodiment, the alarm levels include high-risk alarm levels, medium-risk alarm levels, and low-risk alarm levels; the session user permission information includes the session user's alarm receiving permissions and authorization validity period, which are determined by the session user's user type; please refer to Figure 6 In step S203, namely, determining the first push target and the first push method based on the alarm level and the session user permission information in the active vehicle control session, the following steps are included: S601: When the alarm level is a high-risk alarm level, if the alarm receiving permission includes the high-risk alarm receiving permission and the authorization validity period has not expired, then the target vehicle owner and the session user of the active vehicle control session are determined as the first push object, and the first push method is determined to be vehicle control application notification, SMS notification and telephone notification. S602: When the alarm level is a medium-risk alarm level, if the alarm receiving permission includes the medium-risk alarm receiving permission and the authorization validity period has not expired, then the session user of the active vehicle control session is determined as the first push target, and the first push method is determined to be vehicle control application notification and SMS notification. S603: When the alarm level is a low-risk alarm level, if the alarm receiving permission includes low-risk alarm receiving permission and the authorization validity period has not expired, then the session user of the active vehicle control session is determined as the first push target, and the first push method is determined to be vehicle control application notification.

[0049] Understandably, when the alarm information does not include unauthorized operation alarms and an active vehicle control session exists, the server analyzes the alarm level and the session user permission information in the active vehicle control session based on the decision rule base to determine the specific first push target and the first push method. Specifically, for different alarm levels, if the alarm receiving permissions of the active vehicle control session user include the corresponding alarm level's receiving permissions and the authorization validity period has not expired, then the active vehicle control session user can be the first push target. If the alarm receiving permissions of the active vehicle control session user do not include the corresponding alarm level's receiving permissions or the authorization validity period has expired, then the active vehicle control session user cannot be the first push target. In this case, the server determines the push target and push method according to the process for when there is no active vehicle control session. That is, when the alarm level is a high-risk alarm level, the target vehicle owner is determined as the first push target, and the first push method is determined to be a vehicle control application notification, SMS notification, or telephone notification. When the alarm level is a medium-risk alarm level, the target vehicle owner is determined as the first push target, and the first push method is determined to be a vehicle control application notification. When the alarm level is low-risk, the user of the next active vehicle control session is identified as the first push target, and the first push method is to push the vehicle control application notification during the next active vehicle control session.

[0050] In a specific scenario involving temporary valet parking authorization, the car owner grants the valet a 2-hour temporary access privilege (user type: temporary user; authorization scope: unlocking, starting the vehicle, checking vehicle status, and receiving all notifications) via the vehicle control application client. During the valet's operation, an abnormal tire pressure occurs (medium-risk alarm level). The server detects an active vehicle control session (valet logged in) and that the valet is a temporarily authorized user. The first recipient of the notification is the valet, and the primary notification method is both the vehicle control application notification and an SMS notification. The valet receives the notification via the vehicle control application, promptly pulls over to check the tire pressure, and clicks "Resolved" after completion, with the status synchronized to the server. At this time, the car owner does not receive the alarm, avoiding unnecessary disruption.

[0051] In a specific family-shared scenario, the car owner grants long-term authorization to family members via the vehicle control app (permission scope: full functionality, including receiving medium-to-high-risk alarms). While a family member is driving the vehicle, a maintenance reminder is triggered (low-risk alarm level). The server detects that the currently active authorized user is a family member, and the family member is the first recipient of the notification, via the vehicle control app. After receiving the alarm notification via the vehicle control app, the family member plans to go to the 4S store for maintenance the next day. The car owner does not receive the low-risk alarm and avoids being disturbed.

[0052] This embodiment applies the user permission scope and authorization validity period of the current active vehicle control session to the decision-making of alarm push targets. It reflects a two-dimensional matching mechanism of permissions and sessions under different alarm levels, solves the problem of inaccurate push targets, avoids vehicle owners being disturbed by frequent alarms, and ensures that the authorized person who actually uses the vehicle receives the alarm in a timely manner, thereby improving alarm response efficiency.

[0053] In one embodiment, the alarm levels include high-risk alarm levels, medium-risk alarm levels, and low-risk alarm levels; please refer to... Figure 7 In step S302, namely, determining the second push method and the second push target based on the alarm level, the following steps are included: S701: When the alarm level is a high-risk alarm level, the owner of the target vehicle is identified as the second push target, and the second push method is determined to be vehicle control application notification, SMS notification and telephone notification. S702: When the alarm level is a medium-risk alarm level, the owner of the target vehicle is identified as the second push target, and the second push method is determined to be a vehicle control application notification. S703: When the alarm level is a low-risk alarm level, determine the session user of the next active vehicle control session as the second push target, and determine the second push method as pushing vehicle control application notifications during the next active vehicle control session.

[0054] Understandably, when the alarm information does not include unauthorized operation alarms and there are currently no active vehicle control sessions, the server analyzes the alarm level based on the decision rule base to determine the specific second push target and second push method. Specifically, when the alarm level is high-risk or medium-risk, the target vehicle owner is determined as the second push target. When the alarm level is low-risk, there is no need to push a notification to the target vehicle owner; instead, the session user of the next active vehicle control session is determined as the second push target.

[0055] In a specific unauthorized intrusion alarm scenario, the vehicle is stationary and there is no active vehicle control session, yet an unauthorized intrusion occurs (high-risk alarm level). The server detects no currently active authorized user, and the second push notification target is the vehicle owner. The second push method includes a vehicle control app notification, SMS notification, and phone call notification. The vehicle owner first receives the vehicle control app notification; if it is not read within 5 minutes, the server sends an SMS notification. If the SMS delivery fails, the server triggers a voice call notification. The vehicle owner answers and learns of the vehicle alarm anomaly. At this point, the vehicle owner can remotely lock the vehicle through the vehicle control app client and contact nearby traffic police. After handling the situation, they click "Processed."

[0056] This embodiment addresses the issue of homogenized push strategies by employing a dynamic decision-making push strategy and multiple selectable push methods to match different alarm levels. High-risk alarms are pushed urgently through multiple parallel channels to avoid omissions. Medium- and low-risk alarms are pushed on demand to reduce information overload and balance security and convenience.

[0057] In one embodiment, the alarm levels include high-risk alarm levels, medium-risk alarm levels, and low-risk alarm levels; please refer to... Figure 8 In step S203, namely, pushing the vehicle alarm notification to the first push recipient, the following steps are included: S801: Obtain the push do-not-disturb period corresponding to the first push object, and detect whether the current time point is within the push do-not-disturb period; S802: If the current time is not within the push do-not-disturb period, or if the current time is within the push do-not-disturb period but the alarm level is a high-risk alarm level, the vehicle alarm notification will be pushed to the first push object in real time. S803: When the current time point is within the push do-not-disturb period and the alarm level is a medium-risk alarm level or a low-risk alarm level, wait for the push do-not-disturb period to end before pushing the vehicle alarm notification to the first push recipient.

[0058] Understandably, since different users have their own designated "do not disturb" periods, the server needs to check whether the current time is within the "do not disturb" period for the first push recipient when sending vehicle alarm notifications. Vehicle alarm notifications not currently within the "do not disturb" period are sent directly to the first push recipient. If the current time is within the "do not disturb" period, the alarm level needs to be analyzed. For vehicle alarm notifications with a high-risk alarm level, the server sends them directly to the first push recipient. For vehicle alarm notifications with a medium-risk or low-risk alarm level, the server waits until the "do not disturb" period ends before sending them to the first push recipient. The server uses the same processing method when sending vehicle alarm notifications to the second push recipient. When sending vehicle alarm notifications to the third and fourth push recipients, the server sends them directly, without being bound by the "do not disturb" period.

[0059] This embodiment avoids users receiving frequent vehicle alarm notifications by determining do-not-disturb periods, reducing unnecessary interference and improving user experience. Users can customize do-not-disturb periods according to their actual needs, reflecting personalized choices and increasing flexibility. For high-risk alarm levels, notifications will still be pushed in real time even during do-not-disturb periods, ensuring that users do not miss important information.

[0060] This application also provides a vehicle alarm notification push system, comprising six core modules: alarm information collection, user permission and session management, alarm level assessment, dynamic decision push engine, multi-channel push execution, and push log. The alarm information collection module receives encrypted alarm information. The user permission and session management module acquires and monitors vehicle control session data. The alarm level assessment module assesses alarms at three levels: high-risk, medium-risk, and low-risk, according to rules. The dynamic decision push engine module dynamically determines the push recipients and multi-channel push methods (APP, SMS, voice call, etc.) based on user permission type, authorization validity period, and current vehicle control session status, while also supporting user-defined decision rule bases. The multi-channel push execution module pushes vehicle alarm notifications to the corresponding recipients according to the push method. The push log module records the entire alarm push information chain and supports traceability. The log records include: alarm code ID, alarm type, alarm level, push time, push recipient (user account ID, mobile phone number), push channel, reception status (received, not received), reading status (read, not read), processing status (processed, not processed), and processing time. In a specific embodiment, after receiving the vehicle alarm notification through the vehicle control application client, the user, as the push recipient, clicks the "read" or "processed" button to provide feedback on the status information to the server. The push log records the reception status, reading status, processing status, and corresponding time. Furthermore, if no user handles the high-risk alarm notification within 30 minutes of it being pushed, the server automatically sends an additional voice call to the vehicle owner and generates an "Unprocessed Alarm Reminder" log.

[0061] This application also provides an electronic device 90, please refer to... Figure 9 It includes a memory 910 and a processor 920, wherein the memory 910 is used to store computer programs; and the processor 920 is used to execute the programs stored in the memory 910 to implement the vehicle alarm notification push method described in any embodiment of this application.

[0062] This application also provides a vehicle that includes the aforementioned electronic equipment.

[0063] In this application, "multiple" refers to two or more.

[0064] The terms “first,” “second,” “third,” “fourth,” etc., used in this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence.

[0065] In this application, the term "and / or" 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, or B existing alone. Additionally, in this application, the character " / " generally indicates that the preceding and following related objects have an "or" relationship.

[0066] Unless otherwise specified, all steps in this application may be performed sequentially or randomly. For example, if the method includes steps A and B, it means that the method may include steps A and B performed sequentially, or it may include steps B and A performed sequentially. For example, if the method may also include step C, it means that step C may be added to the method in any order. For example, the method may include steps A, B, and C, or it may include steps A, C, and B, or it may include steps C, A, and B, etc.

[0067] The above description is merely a preferred embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. A vehicle warning notification push method characterized by, include: Obtain alarm information of the target vehicle, as well as vehicle control session data associated with the target vehicle; If the alarm type in the alarm information is not an unauthorized operation alarm, and it is confirmed that there is an active vehicle control session based on the vehicle control session data, then the alarm level and vehicle alarm notification shall be determined based on the alarm information. Based on the alarm level and the session user permission information in the active vehicle control session, a first push target and a first push method are determined, and the vehicle alarm notification is pushed to the first push target according to the first push method.

2. The vehicle alert notification push method of claim 1, wherein, After acquiring the alarm information of the target vehicle and the vehicle control session data associated with the target vehicle, the method further includes: If the alarm type in the alarm information is not an unauthorized operation alarm, and it is confirmed according to the vehicle control session data that there is currently no active vehicle control session, the alarm level and vehicle alarm notification shall be determined according to the alarm information. Based on the alarm level, a second push method and a second push target are determined, and the vehicle alarm notification is pushed to the second push target according to the second push method.

3. The vehicle alarm notification push method according to claim 1, characterized in that, After acquiring the alarm information of the target vehicle and the vehicle control session data associated with the target vehicle, the method further includes: When the alarm type in the alarm information is an unauthorized operation alarm, and it is confirmed according to the vehicle control session data that there is no active vehicle control session, the vehicle alarm notification is determined according to the alarm information, the target vehicle owner is identified as the third push object, and the vehicle alarm notification is pushed to the third push object according to the preset unauthorized alarm method. If the alarm type in the alarm information is an unauthorized operation alarm, and it is confirmed that there is an active vehicle control session based on the vehicle control session data, a vehicle alarm notification is determined based on the alarm information. The target vehicle owner and the session user of the active vehicle control session are identified as the fourth push object, and the vehicle alarm notification is pushed to the fourth push object according to the preset unauthorized alarm method.

4. The vehicle alarm notification push method according to any one of claims 1 to 3, characterized in that, After acquiring the alarm information of the target vehicle and the vehicle control session data associated with the target vehicle, the process includes: When the vehicle control session status in the vehicle control session data is online login status, and the vehicle control interruption duration in the vehicle control session data exceeds a preset interruption duration threshold, it is confirmed that there is currently an active vehicle control session. If the vehicle control session is offline or the vehicle control interruption duration exceeds a preset interruption duration threshold, it is confirmed that there is currently no active vehicle control session.

5. The vehicle alarm notification push method according to claim 1, characterized in that, Determining the alarm level based on the alarm information includes: Based on the current alarm type in the alarm information, an alarm level is determined from multiple candidate levels in a preset type level mapping table; each candidate level in the preset type level mapping table is associated with at least one alarm type; the candidate levels include high-risk alarm level, medium-risk alarm level, and low-risk alarm level.

6. The vehicle alarm notification push method according to claim 1, characterized in that, The alarm levels include high-risk alarm levels, medium-risk alarm levels, and low-risk alarm levels; the session user permission information includes the session user's alarm receiving permissions and authorization validity period, which are determined by the session user's user type; The step of determining the first push target and the first push method based on the alarm level and the session user permission information in the active vehicle control session includes: When the alarm level is a high-risk alarm level, if the alarm receiving permission includes the high-risk alarm receiving permission and the authorization validity period has not expired, then the target vehicle owner and the session user of the active vehicle control session are determined as the first push object, and the first push method is determined to be vehicle control application notification, SMS notification and telephone notification. When the alarm level is a medium-risk alarm level, if the alarm receiving permission includes the medium-risk alarm receiving permission and the authorization validity period has not expired, then the session user of the active vehicle control session is determined as the first push target, and the first push method is determined to be vehicle control application notification and SMS notification. When the alarm level is a low-risk alarm level, if the alarm receiving permission includes low-risk alarm receiving permission and the authorization validity period has not expired, then the session user of the active vehicle control session is determined as the first push target, and the first push method is determined to be vehicle control application notification.

7. The vehicle alarm notification push method according to claim 2, characterized in that, The alarm levels include high-risk alarm levels, medium-risk alarm levels, and low-risk alarm levels; The step of determining the second push method and the second push target based on the alarm level includes: When the alarm level is a high-risk alarm level, the owner of the target vehicle is identified as the second push recipient, and the second push method is determined to be vehicle control application notification, SMS notification, and telephone notification. When the alarm level is a medium-risk alarm level, the owner of the target vehicle is identified as the second push recipient, and the second push method is determined to be a vehicle control application notification. When the alarm level is a low-risk alarm level, the session user of the next active vehicle control session is determined as the second push target, and the second push method is determined to be to push the vehicle control application notification during the next active vehicle control session.

8. The vehicle alarm notification push method according to claim 1, characterized in that, The alarm levels include high-risk alarm levels, medium-risk alarm levels, and low-risk alarm levels; The step of pushing the vehicle alarm notification to the first push recipient includes: Obtain the push do-not-disturb period corresponding to the first push object, and detect whether the current time point is within the push do-not-disturb period; If the current time is not within the push do-not-disturb period, or if the current time is within the push do-not-disturb period but the alarm level is a high-risk alarm level, the vehicle alarm notification will be pushed to the first push recipient in real time. If the current time is within the push notification do-not-disturb period and the alarm level is a medium-risk alarm level or a low-risk alarm level, the vehicle alarm notification will be pushed to the first push recipient after the push notification do-not-disturb period ends.

9. An electronic device, characterized in that, Including processor and memory, among which Memory, used to store computer programs; A processor is configured to execute a program stored in a memory to implement the vehicle alarm notification push method according to any one of claims 1-8.

10. A vehicle, characterized in that, It includes the electronic device as described in claim 9.

Images