Driving reminder push processing method and device

Abstract

The embodiments of the present specification provide a driving reminder push processing method and device, wherein a driving reminder push processing method includes: obtaining vehicle light abnormality information of the driving vehicle uploaded by the on-board equipment of the neighboring vehicle of the driving vehicle; the vehicle light abnormality information is determined by vehicle light abnormality detection based on the collected driving image of the driving vehicle; based on the vehicle identification of the driving vehicle contained in the vehicle light abnormality information, the user account of the user to whom the driving vehicle belongs is queried; based on the login status of the user account, a target push service for pushing reminders to the user; based on the target push service, a driving reminder corresponding to the vehicle light abnormality information is pushed to the user.

Description

[0001] This application is a divisional application of the Chinese invention patent application with the application date of April 13, 2022, application number CN202210384352.6, and name “Driving Reminder Push Processing Method and Device”. Technical Field

[0002] This document relates to the field of data processing technology, and in particular to a driving reminder push processing method and device. Background Art

[0003] With the continuous development of the economy, the number of vehicles is increasing. In the process of traffic information management, the license plate is the identity certificate of the vehicle. Through the license plate, many important information of the vehicle can be detected, such as the user information of the user to whom the vehicle belongs. With the increase in the number of vehicles, more and more vehicles are driving on the road, and more and more requirements are placed on vehicles on the road. Travel safety has also become a focus of increasing concern for users. Summary of the invention

[0004] One or more embodiments of the present specification provide a driving reminder push processing method. The driving reminder push processing method includes: obtaining vehicle light abnormality information of the driving vehicle uploaded by the vehicle-mounted device of the neighboring vehicle of the driving vehicle; the vehicle light abnormality information is determined by vehicle light abnormality detection based on the collected driving image of the driving vehicle. Based on the vehicle identification of the driving vehicle contained in the vehicle light abnormality information, the user account of the user to whom the driving vehicle belongs is queried. According to the login status of the user account, the target push service for pushing reminders to the user is determined. Based on the target push service, the driving reminder corresponding to the vehicle light abnormality information is pushed to the user.

[0005] One or more embodiments of the present specification provide a driving reminder push processing device, including: an information acquisition module, configured to obtain vehicle light abnormality information of the driving vehicle uploaded by the vehicle-mounted device of the neighboring vehicle of the driving vehicle; the vehicle light abnormality information is determined by vehicle light abnormality detection based on the collected driving image of the driving vehicle. An account query module, configured to query the user account of the user to whom the driving vehicle belongs based on the vehicle identification of the driving vehicle contained in the vehicle light abnormality information. A service determination module, configured to determine a target push service for pushing reminders to the user according to the login status of the user account. A reminder push module, configured to push a driving reminder corresponding to the vehicle light abnormality information to the user based on the target push service.

[0006] One or more embodiments of the present specification provide a driving reminder push processing device, including: a processor; and a memory configured to store computer executable instructions, wherein when the computer executable instructions are executed, the processor: obtains vehicle light abnormality information of the driving vehicle uploaded by the vehicle-mounted device of the neighboring vehicle of the driving vehicle; the vehicle light abnormality information is determined by vehicle light abnormality detection based on the collected driving image of the driving vehicle. Based on the vehicle identification of the driving vehicle contained in the vehicle light abnormality information, the user account of the user to whom the driving vehicle belongs is queried. Based on the login status of the user account, a target push service for pushing reminders to the user is determined. Based on the target push service, a driving reminder corresponding to the vehicle light abnormality information is pushed to the user.

[0007] One or more embodiments of the present specification provide a storage medium for storing computer-executable instructions, which implement the following process when executed by a processor: obtaining vehicle light abnormality information of the driving vehicle uploaded by the on-board equipment of the neighboring vehicle of the driving vehicle; the vehicle light abnormality information is determined by vehicle light abnormality detection based on the collected driving image of the driving vehicle. Based on the vehicle identification of the driving vehicle contained in the vehicle light abnormality information, query the user account of the user to whom the driving vehicle belongs. According to the login status of the user account, determine the target push service for pushing reminders to the user. Based on the target push service, push the driving reminder corresponding to the vehicle light abnormality information to the user. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] In order to more clearly illustrate one or more embodiments of the present specification or the technical solutions in the prior art, the drawings required for use in the embodiments or the prior art descriptions are briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in the present specification. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative labor. Figure 1 A processing flow chart of a driving reminder push processing method provided by one or more embodiments of this specification; Figure 2 A first vehicle light characteristic diagram provided for one or more embodiments of this specification; Figure 3 A second vehicle light characteristic diagram provided for one or more embodiments of this specification; Figure 4 A third vehicle light characteristic diagram provided for one or more embodiments of this specification; Figure 5 A fourth vehicle light characteristic diagram provided for one or more embodiments of this specification; Figure 6 A fifth vehicle light characteristic diagram provided for one or more embodiments of this specification; Figure 7 A processing flow chart of a driving reminder push processing method applied to a navigation service push scenario provided by one or more embodiments of this specification; Figure 8 A processing flow chart of a driving reminder push processing method applied to an instant messaging push scenario provided by one or more embodiments of this specification; Fig. 9 A schematic diagram of a driving reminder push processing device provided in one or more embodiments of this specification; Fig.10 A schematic diagram of the structure of a driving reminder push processing device provided in one or more embodiments of this specification. DETAILED DESCRIPTION

[0009] In order to enable those skilled in the art to better understand the technical solutions in one or more embodiments of this specification, the technical solutions in one or more embodiments of this specification will be clearly and completely described below in conjunction with the drawings in one or more embodiments of this specification. Obviously, the described embodiments are only part of the embodiments of this specification, not all of them. Based on one or more embodiments of this specification, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of this document.

[0010] This specification provides an embodiment of a driving reminder push processing method: Reference Figure 1 The driving reminder push processing method provided in this embodiment specifically includes steps S102 to S108.

[0011] Step S102, obtaining vehicle light abnormality information of the driving vehicle uploaded by the vehicle-mounted equipment of the neighboring vehicle.

[0012] The driving reminder push processing method provided in the present embodiment detects the vehicle lights of the driving vehicle through the on-board equipment of the neighboring vehicle, and queries the user account of the user to which the associated driving vehicle belongs based on the vehicle identification of the driving vehicle contained in the vehicle abnormality information of the driving vehicle uploaded by the on-board equipment of the neighboring vehicle to determine the contact method for the user, and then pushes the driving reminder to the user based on the contact method. In this way, the vehicle lights abnormality information of the driving vehicle is detected through the on-board equipment, and then the driving reminder is given to the user to which the driving vehicle belongs, thereby improving the user's perception of the vehicle lights status, and thereby improving the standardization and safety of vehicle driving.

[0013] The driving vehicle described in this embodiment includes a vehicle in a driving state, and the adjacent vehicles include vehicles in a driving state or a stopped state and whose image acquisition range of the on-board device covers the driving vehicle in a driving state; in addition, the adjacent vehicle of the driving vehicle can also be a vehicle that is behind the driving vehicle and whose distance from the driving vehicle is less than a distance threshold; optionally, the adjacent vehicles include: vehicles whose image acquisition range of the on-board device covers the driving position of the driving vehicle. The vehicle light abnormality information is determined by detecting the abnormality of the vehicle light based on the collected driving image of the driving vehicle. The on-board device includes a device that is configured for the adjacent vehicle and is capable of information collection and / or information processing; for example: a driving recorder or a device used to collect information when a vehicle fails. The vehicle lights of the vehicle in this embodiment include the vehicle's clearance lights and brake lights, and can also include the vehicle's turn signal, power light or other lights that represent the vehicle's status.

[0014] In specific implementation, when the driving vehicle is in motion, the neighboring vehicles use the vehicle-mounted equipment configured by the vehicle to take pictures of the surrounding vehicles, and perform vehicle light abnormality detection on the captured driving images of the driving vehicle, so as to determine whether there is any abnormality in the vehicle lights of the driving vehicle. In order to improve the effectiveness of vehicle light abnormality detection, this embodiment combines environmental characteristics to perform vehicle light abnormality detection. Taking environmental brightness characteristics as an example, in an optional implementation provided by this embodiment, the vehicle-mounted equipment of the neighboring vehicle performs vehicle light abnormality detection in the following manner: Determining the ambient brightness characteristics according to the acquisition time point of the driving image; If the vehicle light feature in the driving image does not satisfy the driving condition corresponding to the environmental brightness feature, generating the vehicle light abnormality information based on the vehicle light feature; If the vehicle light feature in the driving image meets the driving condition corresponding to the brightness feature, it is determined that the driving vehicle is in a safe driving state and no processing is performed.

[0015] Specifically, the on-board equipment of the neighboring vehicle captures the image of the driving vehicle to obtain a video stream, and performs vehicle light anomaly detection on each frame of the driving image in the video stream to determine whether there is an abnormality in the vehicle lights of the driving vehicle; in the process of performing vehicle light anomaly detection based on the driving image of any frame in the video stream, first, the ambient brightness characteristics at the acquisition time point are determined according to the acquisition time point of the driving image, and then the driving conditions corresponding to the ambient brightness characteristics are determined, and finally, based on the driving conditions, anomaly detection is performed on the vehicle light characteristics in the driving image to detect whether the vehicle light characteristics meet the driving conditions. If so, no processing is performed; if not, vehicle light anomaly information of the driving vehicle is generated based on the vehicle light characteristics.

[0016] For example, under normal circumstances, after the vehicle's position lights (left position light 201 and right position light 202) are turned on, the vehicle light characteristics are as follows: Figure 2 As shown; the vehicle's clearance lights and brake lights (left brake light 301 and right brake light 302) are turned on, and after superposition, a high-brightness vehicle light feature is formed, and the roof brake light 303 is also on. Figure 3 In abnormal situations, the characteristics of vehicle lights that are not turned on or have low brightness are as follows: Figure 4 As shown, the clearance lamp is not turned on, and the vehicle lamp characteristics of the left brake lamp 301 failure are as follows Figure 5 As shown, the clearance lamp is not turned on, and the vehicle lamp characteristics of the right brake lamp 302 failure are as follows Figure 6 It should be noted that the application displays the brake light and the position light separately in order to better show the abnormal effect. In actual application, the brake light and the position light can be displayed in a superimposed manner.

[0017] Taking the environmental brightness feature as an example, when vehicle c1 is driving, the onboard equipment of vehicle c1 collects a driving image of vehicle c2 which is within the image collection range of vehicle c1. First, the collection time point carried by the driving image is read, and the collection time point is found to be night. It is determined that the environmental brightness feature is black, and the corresponding driving condition is to turn on the clearance lights. It is verified whether the clearance lights of vehicle c2 in the driving image are turned on normally, that is, whether the vehicle lights of vehicle c2 are turned on normally. Figure 2 As shown in the figure, if the clearance lights on both sides of vehicle C2 are turned on, it means that vehicle C2 is driving normally; if the vehicle lights of vehicle C2 are Figure 4 As shown, it is determined that vehicle c2 is not in a safe driving state, and vehicle light abnormality information including "the clearance lights of vehicle c2 are not turned on normally" is generated.

[0018] In addition, in addition to performing vehicle light abnormality detection on the driving vehicle based on the environmental brightness characteristics, in this embodiment, vehicle light abnormality detection can also be performed on the driving vehicle based on other environmental characteristics corresponding to the acquisition time point, for example, environmental layout characteristics (tunnel); if vehicle light abnormality detection is performed based on environmental layout characteristics, the driving image is first identified to determine the environmental layout characteristics of the driving vehicle's environment. If the vehicle light characteristics in the driving image meet the driving conditions corresponding to the environmental layout characteristics, no processing is performed; if the driving conditions corresponding to the environmental layout characteristics are not met, vehicle light abnormality information of the driving vehicle is generated based on the vehicle light characteristics. It should be noted that in the process of performing vehicle light abnormality detection in this embodiment, vehicle light abnormality detection can be performed based on one environmental characteristic, and vehicle light abnormality detection can also be performed based on a combination of multiple environmental characteristics (such as environmental brightness characteristics and environmental layout characteristics), which is not limited in this embodiment.

[0019] In order to further improve the effectiveness of vehicle light abnormality detection, the present embodiment can also perform vehicle light abnormality detection based on vehicle light features in the driving image. For example, the driving image of vehicle c2 collected by the onboard equipment of vehicle c1 is as follows: Figure 5 As shown, based on Figure 5 The vehicle light feature shown in FIG. 1 determines the vehicle light abnormality information including "the left brake light of vehicle c2 is abnormal". If the collected driving image of vehicle c2 is as shown in FIG. Figure 6 As shown, based on Figure 6 The vehicle lamp feature shown generates vehicle lamp abnormality information including "there is an abnormality in the right brake lamp of vehicle c2".

[0020] After obtaining the abnormal vehicle light information of the driving vehicle uploaded by the on-board equipment of the neighboring vehicle, in order to enhance the awareness of the user of the driving vehicle about the abnormal vehicle light information, a driving reminder is sent to the user through the user account associated with the vehicle identification of the driving vehicle. However, the user account of the user of the driving vehicle belongs to the user's privacy to a certain extent. Therefore, if you want to query the associated user account based on the vehicle identification, you need to obtain the user's authorization to ensure the user's privacy security.

[0021] Based on this, in an optional implementation manner provided by this embodiment, after obtaining the abnormal information of the vehicle light, the following operations are performed: Query whether the vehicle identification is associated with a user authorization mark; If yes, then executing the step of querying the user account of the user to whom the driving vehicle belongs based on the vehicle identification of the driving vehicle contained in the vehicle light abnormality information; If not, no action will be taken.

[0022] Specifically, in order to protect user privacy, after obtaining the abnormal vehicle light information of the driving vehicle, first check whether the vehicle identification carried in the abnormal vehicle light information is associated with the user authorization mark. If so, query the user account of the user who drives the vehicle based on the vehicle identification; if not, the user account cannot be obtained because the user is not authorized, and no processing is done.

[0023] It should also be noted that the above-mentioned vehicle light abnormality detection based on the collected driving image of the driving vehicle is performed by the vehicle-mounted equipment of the adjacent vehicle, that is, the vehicle light abnormality information is determined by the vehicle-mounted equipment performing vehicle light abnormality detection on the collected driving image of the driving vehicle; in addition, in this embodiment, the vehicle light abnormality information of the driving vehicle uploaded by the vehicle-mounted equipment of the adjacent vehicle of the driving vehicle can also be replaced by obtaining the driving image of the driving vehicle uploaded by the vehicle-mounted equipment of the adjacent vehicle of the driving vehicle, performing vehicle light abnormality detection on the driving vehicle based on the driving image, and determining the vehicle light abnormality information of the driving vehicle; specifically, obtaining at least one driving image of the driving vehicle collected and uploaded by the vehicle-mounted equipment of the adjacent vehicle of the driving vehicle, and performing vehicle light abnormality detection on the driving vehicle based on the at least one driving image, wherein the process of performing vehicle light abnormality detection on the driving vehicle based on at least one driving image is similar to the process of performing vehicle light abnormality detection by the above-mentioned vehicle-mounted equipment, and this embodiment will not be repeated here. Alternatively, it can also be replaced by obtaining the video stream collected and uploaded by the vehicle-mounted equipment of the adjacent vehicle of the driving vehicle, performing vehicle light detection on the driving vehicle based on each frame of the driving image in the video stream, and determining the vehicle light abnormality information of the driving vehicle.

[0024] Step S104: Based on the vehicle identification of the driving vehicle contained in the vehicle light abnormality information, query the user account of the user to whom the driving vehicle belongs.

[0025] The vehicle identification described in this embodiment includes the license plate number of the driving vehicle; the user account includes the account of the user driving the vehicle to log in to the navigation application, third-party payment application or third-party instant messaging application.

[0026] In specific implementation, in order to promptly deliver the vehicle light abnormality information of the driving vehicle uploaded by the neighboring vehicles to the user of the driving vehicle, when the vehicle light abnormality information of the driving vehicle uploaded by the neighboring vehicles is obtained, at least one user account of the user of the driving vehicle is queried based on the vehicle identification of the driving vehicle contained in the vehicle light abnormality information.

[0027] It should be noted that a vehicle relationship table is maintained, in which information with associations of various vehicles is recorded, including the associations between the vehicle identification, the vehicle factory identification (for example, the vehicle VIN number (Vehicle Identification Number)), the user account of the user to whom the vehicle belongs, and / or the user communication identification (contact information).

[0028] The following only takes the query of a user account as an example to illustrate the targeted push service to the user.

[0029] Step S106, determining a target push service for pushing reminders to the user according to the login status of the user account.

[0030] The login status includes a logged-in state in which the user has logged in to at least one service application and a non-logged-in state in which the user has not logged in to any service application; wherein, in the logged-in state, the login status identifier of the user account is a first status identifier, that is, the first status identifier is a logged-in status identifier; in the non-logged-in state, the login status identifier of the user account is a second status identifier, that is, the second status identifier is a non-logged-in status identifier.

[0031] In order to ensure that driving reminders are pushed effectively and efficiently, and to avoid the situation where the user is unable to receive driving reminders in a timely manner due to reminder pushes through the user account when the user account is not logged in, in this embodiment, after obtaining the user account, the target push service for pushing reminders to the user is determined according to the login status of the user account; specifically, in an optional implementation manner provided by this embodiment, the following method is adopted to implement the determination of the target push service for pushing reminders to the user according to the login status of the user account: Query the login status identifier of the user account in the status record table; If the login status identifier is the first status identifier, query at least one service application that logs in to the user account; determine the target push service in the at least one service application based on the application priority; If the login status identifier is the second status identifier, query the user communication identifier associated with the user account; based on the user's push authorization record for the instant messaging service corresponding to the user communication identifier, use the instant messaging service corresponding to the user communication identifier as the target push service.

[0032] Wherein, the target push service includes navigation service and / or payment service.

[0033] Specifically, the login status identifier of the user account is queried in the status record table. If the login status identifier of the user account is the first status identifier corresponding to the logged-in status, at least one service application of the logged-in user account is queried, and a target push service is determined in at least one service application to push driving reminders based on the target push service; if the login status identifier of the user account is the second status identifier corresponding to the non-logged-in status, the user communication identifier associated with the user account is queried, and the instant messaging service corresponding to the user communication identifier is used as the target push service.

[0034] For example, the vehicle light abnormality information of vehicle c2 including "the left brake light of vehicle c2 is abnormal" uploaded by the vehicle-mounted device of vehicle c1 is obtained. First, based on the vehicle identification of vehicle c2, the user account of the user to which vehicle c2 belongs is queried. After the user account is queried, the login status identification of the user account is queried in the status record table. When the queried login status identification is the logged-in status identification, it is queried that the service applications logged in to the user account include navigation service and payment service. According to the priority of navigation service and payment service, navigation service is determined as the target push service for reminder push to the user; If the queried login status identifier is a non-logged-in status identifier, the contact information of the user associated with the user account is queried, and the SMS service is determined as the target push service.

[0035] It should be noted that the above is only an explanation of the case where there is only one user account queried. If the vehicle identification is associated with multiple user accounts, then when at least one user account is queried, the login status identification of each user account is queried, and at least one login user account with a login status identification as the first status identification is screened out, and the at least one login user account is sorted according to a preset priority, and the first login user account in the sorted account queue is determined as the target user account, and at least one service application logged in to the target user account is queried, and the at least one service application is sorted according to the application priority, and the first service application in the sorted application queue is determined as the target push service.

[0036] Step S108: Pushing a driving reminder corresponding to the vehicle light abnormality information to the user based on the target push service.

[0037] The driving reminder includes a reminder generated based on the vehicle light abnormality information. The driving reminder can be the vehicle light abnormality information itself, or can be a reminder generated including the vehicle light abnormality information, which is not limited in this embodiment.

[0038] In specific implementation, when the target push service is determined, the driving reminder is pushed to the user based on the target push service. With respect to the navigation service and payment service provided above, this embodiment describes the push process of driving reminder based on the navigation service and the payment service respectively.

[0039] (1) The target push service provided above includes a navigation service. In an optional implementation provided in this embodiment, the push of driving reminders is implemented in the following manner: generating the driving reminder based on the vehicle light abnormality information; The driving reminder is sent to the navigation device bound to the user account through the navigation service, so that the navigation device voice broadcasts the driving reminder.

[0040] Specifically, a driving reminder is generated based on the abnormal information of the vehicle lights, and the driving reminder is sent to the navigation device logged in or bound to the user account through the navigation service, so that the navigation device can voice broadcast the driving reminder based on its own voice broadcast function.

[0041] (2) With respect to the above-mentioned target push service including the payment service, in an optional implementation manner provided in this embodiment, the push of driving reminders is implemented in the following manner: generating a driving reminder including the vehicle light abnormality information; A message containing the driving reminder is pushed to the terminal device bound to the user account through the payment service.

[0042] Specifically, a driving reminder containing abnormal information of vehicle lights is generated, and then the driving reminder is sent to the terminal device bound to or logged in to the user account through the payment application, so that the terminal device can push the driving reminder message through the in-station message within the payment service.

[0043] If the user account is not logged in, a driving reminder will be pushed to the user via the instant messaging service.

[0044] It should be noted that the above-mentioned push of driving reminders to users will cause message reminders to users, which will disturb users to a certain extent. Therefore, in order to avoid disturbing users by the push of driving reminders and thus affecting user experience, driving reminders are pushed after the user authorizes the driving reminders. That is, before the driving reminders corresponding to the abnormal vehicle light information are pushed to the user based on the target push service, it is queried whether the user authorizes the reminder push. If so, the driving reminders are pushed to the user based on the target push service; if not, no action is taken.

[0045] The following takes the application of a driving reminder push processing method provided by this embodiment in a navigation service push scenario as an example to further illustrate the driving reminder push processing method provided by this embodiment. Figure 7 , a driving reminder push processing method applied to a navigation service push scenario, specifically includes steps S702 to S716.

[0046] Step S702, obtaining vehicle light abnormality information of the moving vehicle uploaded by the vehicle-mounted equipment of the neighboring vehicle.

[0047] Among them, the neighboring vehicles of the moving vehicle include vehicles whose image acquisition range of the on-board equipment covers the moving vehicle.

[0048] Step S704, querying whether the vehicle identification carried in the vehicle light abnormality information is associated with the user authorization mark; If yes, execute steps S706 to S714; If not, no action will be taken.

[0049] Step S706, querying the vehicle factory identification of the traveling vehicle based on the vehicle identification, and querying the user account associated with the vehicle factory identification.

[0050] Step S708: query the login status identifier of the user account in the status record table.

[0051] Step S710: when the login status identifier is a first status identifier, query at least one service application of the login user account.

[0052] In addition, when the login status identifier is the second status identifier, a driving reminder is pushed based on the instant messaging service.

[0053] Step S712: According to the application priority, the navigation service of the logged-in user account is determined as a target push service for pushing reminders to the owner of the driving vehicle.

[0054] Step S714, determining whether the vehicle owner authorizes the reminder push; If yes, execute step S716; If not, no action will be taken.

[0055] Step S716: Send a driving reminder generated based on the abnormal vehicle light information to the navigation device of the logged-in user account through the navigation service, so that the navigation device can voice broadcast the driving reminder.

[0056] The following takes the application of a driving reminder push processing method provided by this embodiment in an instant messaging push scenario as an example to further illustrate the driving reminder push processing method provided by this embodiment. Figure 8 , a driving reminder push processing method applied to an instant messaging push scenario, specifically includes steps S802 to S816.

[0057] Step S802: Acquire a driving image of the driving vehicle uploaded by an on-board device of a neighboring vehicle of the driving vehicle.

[0058] Step S804, identifying the driving image and obtaining the vehicle light features of the driving vehicle.

[0059] Step S806: Based on the vehicle light features and the environmental features corresponding to the driving image, abnormality detection of the vehicle lights of the driving vehicle is performed.

[0060] Among them, the vehicle light abnormality detection is performed on the driving vehicle, including verifying whether the vehicle light characteristics meet the driving conditions corresponding to the environmental characteristics corresponding to the driving image. If so, no processing is performed; if not, it is determined that there is an abnormality in the vehicle light.

[0061] In addition, the vehicle light abnormality detection of the driving vehicle can also be performed based on the vehicle light characteristics themselves.

[0062] Step S808: If there is an abnormality with the vehicle lights, the user account associated with the vehicle identification of the driving vehicle is queried based on the user authorization mark of the owner of the driving vehicle.

[0063] Step S810, query the login status identifier of the user account in the status record table.

[0064] Step S812: If the login status identifier is a non-logged-in status identifier, read the user communication identifier associated with the user account.

[0065] Step S814, generating a driving reminder based on the vehicle light characteristics.

[0066] Step S816: Push a driving reminder to the car owner via an instant messaging service.

[0067] In addition, if the login status identifier is a logged-in status identifier, a service application based on the logged-in user account pushes a driving reminder to the car owner.

[0068] In summary, the driving reminder push processing method provided in this embodiment uses the image acquisition range of the vehicle-mounted device to cover the driving vehicle's neighboring vehicle's driving image collected by the vehicle-mounted device to perform vehicle light abnormality detection, and according to the vehicle light abnormality information of the driving vehicle determined and uploaded by the vehicle-mounted device of the neighboring vehicle after the vehicle light abnormality detection, in the case where the vehicle identification of the driving vehicle is associated with the user authorization mark, the user account of the owner of the driving vehicle associated with the vehicle identification is queried to ensure the privacy security of the owner; After reading the user account, if it is determined that the user account is logged in, the driving reminder is pushed to the car owner through the service application logged in to the user account, so that the driving reminder reaches the car owner efficiently; and before pushing the driving reminder, verify whether the car owner authorizes the reminder push, and push the driving reminder if it is authorized, so as to avoid disturbing the car owner and affecting the car owner's service experience; in this way, the neighboring vehicles will detect the abnormality of the vehicle lights of the driving vehicle and reach the owner of the driving vehicle in real time, thereby enhancing the driver's perception of the abnormality of the vehicle lights of the driving vehicle and improving driving safety.

[0069] An embodiment of a driving reminder push processing device provided in this specification is as follows: In the above-mentioned embodiment, a driving reminder push processing method is provided, and correspondingly, a driving reminder push processing device is also provided, which is described below with reference to the accompanying drawings.

[0070] Reference Fig. 9 , which shows a schematic diagram of a driving reminder push processing device provided in this embodiment.

[0071] Since the device embodiment corresponds to the method embodiment, the description is relatively simple, and the relevant parts can refer to the corresponding description of the method embodiment provided above. The device embodiment described below is only illustrative.

[0072] This embodiment provides a driving reminder push processing device, including: The information acquisition module 902 is configured to acquire vehicle light abnormality information of the driving vehicle uploaded by the vehicle-mounted device of the neighboring vehicle of the driving vehicle; the vehicle light abnormality information is determined by performing vehicle light abnormality detection based on the collected driving image of the driving vehicle; An account query module 904 is configured to query a user account of a user to which the driving vehicle belongs based on the vehicle identification of the driving vehicle included in the vehicle light abnormality information; A service determination module 906 is configured to determine a target push service for pushing reminders to the user according to the login status of the user account; The reminder push module 908 is configured to push the driving reminder corresponding to the vehicle light abnormality information to the user based on the target push service.

[0073] An embodiment of a driving reminder push processing device provided in this specification is as follows: Corresponding to the driving reminder push processing method described above, based on the same technical concept, one or more embodiments of this specification also provide a driving reminder push processing device, which is used to execute the driving reminder push processing method provided above. Fig.10 A schematic diagram of the structure of a driving reminder push processing device provided in one or more embodiments of this specification.

[0074] A driving reminder push processing device provided in this embodiment includes: like Fig.10As shown, the driving reminder push processing device may have relatively large differences due to different configurations or performances, and may include one or more processors 1001 and memory 1002, and the memory 1002 may store one or more storage applications or data. Among them, the memory 1002 may be a short-term storage or a persistent storage. The application stored in the memory 1002 may include one or more modules (not shown in the figure), and each module may include a series of computer executable instructions in the driving reminder push processing device. Furthermore, the processor 1001 may be configured to communicate with the memory 1002, and execute a series of computer executable instructions in the memory 1002 on the driving reminder push processing device. The driving reminder push processing device may also include one or more power supplies 1003, one or more wired or wireless network interfaces 1004, one or more input / output interfaces 1005, one or more keyboards 1006, etc.

[0075] In a specific embodiment, the driving reminder push processing device includes a memory and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer executable instructions in the driving reminder push processing device, and the one or more programs are configured to be executed by one or more processors, including computer executable instructions for performing the following: Acquire vehicle light abnormality information of the driving vehicle uploaded by the vehicle-mounted equipment of the neighboring vehicle of the driving vehicle; the vehicle light abnormality information is determined by performing vehicle light abnormality detection based on the collected driving image of the driving vehicle; Based on the vehicle identification of the driving vehicle contained in the vehicle light abnormality information, querying the user account of the user to whom the driving vehicle belongs; Determine a target push service for pushing reminders to the user according to the login status of the user account; Based on the target push service, a driving reminder corresponding to the vehicle light abnormality information is pushed to the user.

[0076] An embodiment of a storage medium provided in this specification is as follows: Corresponding to the driving reminder push processing method described above, based on the same technical concept, one or more embodiments of this specification also provide a storage medium.

[0077] The storage medium provided in this embodiment is used to store computer executable instructions, and the computer executable instructions implement the following process when executed by a processor: Acquire vehicle light abnormality information of the driving vehicle uploaded by the vehicle-mounted equipment of the neighboring vehicle of the driving vehicle; the vehicle light abnormality information is determined by performing vehicle light abnormality detection based on the collected driving image of the driving vehicle; Based on the vehicle identification of the driving vehicle contained in the vehicle light abnormality information, querying the user account of the user to whom the driving vehicle belongs; Determine a target push service for pushing reminders to the user according to the login status of the user account; Based on the target push service, a driving reminder corresponding to the vehicle light abnormality information is pushed to the user.

[0078] It should be noted that the embodiment of the storage medium in this specification and the embodiment of the driving reminder push processing method in this specification are based on the same inventive concept. Therefore, the specific implementation of this embodiment can refer to the implementation of the corresponding method mentioned above, and the repeated parts will not be repeated.

[0079] The above is a description of a specific embodiment of the specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0080] In the 1930s, improvements to a technology could be clearly distinguished as hardware improvements (for example, improvements to circuit structures such as diodes, transistors, switches, etc.) or software improvements (improvements to method flows). However, with the development of technology, many of today's method flow improvements can be regarded as direct improvements to hardware circuit structures. Designers almost always obtain the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that an improvement in a method flow cannot be implemented using hardware entity modules. For example, a programmable logic device (PLD) (such as a field programmable gate array (FPGA)) is such an integrated circuit whose logical function is determined by the user's programming of the device. Designers can "integrate" a digital system on a PLD by programming it themselves, without having to ask chip manufacturers to design and produce dedicated integrated circuit chips. Moreover, nowadays, instead of manually making integrated circuit chips, this kind of programming is mostly implemented by "logic compiler" software, which is similar to the software compiler used when developing and writing programs, and the original code before compilation must also be written in a specific programming language, which is called hardware description language (HDL). There is not only one kind of HDL, but many kinds, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language), etc. The most commonly used ones are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also know that it is only necessary to program the method flow slightly in the above-mentioned hardware description languages ​​and program it into the integrated circuit, and then it is easy to obtain the hardware circuit that implements the logic method flow.

[0081] The controller may be implemented in any suitable manner, for example, the controller may take the form of a microprocessor or processor and a computer-readable medium storing a computer-readable program code (e.g., software or firmware) executable by the (micro)processor, a logic gate, a switch, an application-specific integrated circuit (ASIC), a programmable logic controller, and an embedded microcontroller, examples of which include but are not limited to the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320, and the memory controller may also be implemented as part of the control logic of the memory. It is also known to those skilled in the art that, in addition to implementing the controller in a purely computer-readable program code manner, the controller may be implemented in the form of a logic gate, a switch, an application-specific integrated circuit, a programmable logic controller, and an embedded microcontroller by logically programming the method steps. Therefore, such a controller may be considered as a hardware component, and the devices for implementing various functions included therein may also be considered as structures within the hardware component. Or even, the devices for implementing various functions may be considered as both software modules for implementing the method and structures within the hardware component.

[0082] The systems, devices, modules or units described in the above embodiments may be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

[0083] For the convenience of description, the above devices are described in terms of functions and are divided into various units. Of course, when implementing the embodiments of this specification, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0084] It should be understood by those skilled in the art that one or more embodiments of the present specification may be provided as a method, system or computer program product. Therefore, one or more embodiments of the present specification may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present specification may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0085] This specification is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of this specification. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0086] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0087] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0088] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0089] Memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. Memory is an example of a computer-readable medium.

[0090] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined in this article, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0091] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0092] One or more embodiments of the present specification may be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. One or more embodiments of the present specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules may be located in local and remote computer storage media, including storage devices.

[0093] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0094] The above description is only an embodiment of this document and is not intended to limit this document. For those skilled in the art, this document may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of this document should be included in the scope of the claims of this document.

Claims

1. A driving reminder push processing method, comprising: The vehicle-mounted device of the neighboring vehicle of the driving vehicle collects the video stream of the driving vehicle, and determines the driving condition corresponding to the environmental brightness feature according to the collection time point of each frame of the driving image in the video stream; based on the driving condition, the vehicle light feature in the driving image is detected for abnormality to determine the vehicle light abnormality information of the driving vehicle; Based on the vehicle identification of the driving vehicle contained in the vehicle light abnormality information, querying the login status identification of the user account of the user to whom the driving vehicle belongs; If the login status identifier is a logged-in status identifier, query at least one service application that logs into the user account, and determine the payment service as the target push service based on the application priority; Based on the payment service, a driving reminder generated based on the vehicle light abnormality information is sent to the navigation device bound to the user account.

2. The driving reminder push processing method according to claim 1, wherein the neighboring vehicle comprises: The image acquisition range of the vehicle-mounted device covers the vehicle in the driving position where the driving vehicle is located.

3. The driving reminder push processing method according to claim 1, wherein the vehicle-mounted equipment of the neighboring vehicle of the driving vehicle collects the video stream of the driving vehicle, and determines the driving condition corresponding to the environmental brightness feature according to the collection time point of the driving image of each frame in the video stream; after the step of performing abnormality detection on the vehicle light feature in the driving image based on the driving condition to determine the vehicle light abnormality information of the driving vehicle is executed, and before the step of querying the login status identification of the user account of the user to whom the driving vehicle belongs based on the vehicle identification of the driving vehicle contained in the vehicle light abnormality information is executed, it also includes: Query whether the vehicle identification is associated with a user authorization mark; If so, the step of querying the login status identification step of the user account of the user to whom the driving vehicle belongs based on the vehicle identification of the driving vehicle contained in the vehicle light abnormality information is executed.

4. A driving reminder push processing device, comprising: The information acquisition module is configured to collect a video stream of the driving vehicle by an on-board device of a vehicle adjacent to the driving vehicle, and determine a driving condition corresponding to an environmental brightness feature according to a collection time point of each frame of a driving image in the video stream; perform an abnormality detection on a vehicle light feature in the driving image based on the driving condition to determine abnormal vehicle light information of the driving vehicle; An account query module is configured to query a login status identifier of a user account of a user to which the driving vehicle belongs based on the vehicle identifier of the driving vehicle contained in the vehicle light abnormality information; A service determination module is configured to query at least one service application logged into the user account if the login status identifier is a logged-in status identifier, and determine the payment service as a target push service based on the application priority; The reminder push module is configured to send a driving reminder generated based on the vehicle light abnormality information to the navigation device bound to the user account based on the payment service.

5. A driving reminder push processing device, comprising: processor; and a memory configured to store computer executable instructions that, when executed, cause the processor to: The vehicle-mounted device of the neighboring vehicle of the driving vehicle collects the video stream of the driving vehicle, and determines the driving condition corresponding to the environmental brightness feature according to the collection time point of each frame of the driving image in the video stream; based on the driving condition, the vehicle light feature in the driving image is detected for abnormality to determine the vehicle light abnormality information of the driving vehicle; Based on the vehicle identification of the driving vehicle contained in the vehicle light abnormality information, querying the login status identification of the user account of the user to whom the driving vehicle belongs; If the login status identifier is a logged-in status identifier, query at least one service application that logs into the user account, and determine the payment service as the target push service based on the application priority; Based on the payment service, a driving reminder generated based on the vehicle light abnormality information is sent to the navigation device bound to the user account.

6. A storage medium for storing computer executable instructions, wherein the computer executable instructions, when executed by a processor, implement the following process: The vehicle-mounted device of the neighboring vehicle of the driving vehicle collects the video stream of the driving vehicle, and determines the driving condition corresponding to the environmental brightness feature according to the collection time point of each frame of the driving image in the video stream; based on the driving condition, the vehicle light feature in the driving image is detected for abnormality to determine the vehicle light abnormality information of the driving vehicle; Based on the vehicle identification of the driving vehicle contained in the vehicle light abnormality information, querying the login status identification of the user account of the user to whom the driving vehicle belongs; If the login status identifier is a logged-in status identifier, query at least one service application that logs into the user account, and determine the payment service as the target push service based on the application priority; Based on the payment service, a driving reminder generated based on the vehicle light abnormality information is sent to the navigation device bound to the user account.

Images