A method and device for ensuring the consistency between the actual driver of an online car-hailing service and the registered driver

Abstract

The present invention discloses a method and device for ensuring the consistency between the actual online car-hailing driver and the registered driver when driving. This method forms a comprehensive identity verification strategy for face recognition of the driver to be verified by judging whether the number of identity verification failures exceeds the failure threshold, querying the first identity verification request of the day, querying whether the previous identity authentication failed, detecting whether the driver to be verified has changed the mobile terminal, and executing the random recognition process in the selection order from top to bottom. It eliminates the traditional single face recognition identity verification for business, is effective and feasible, and improves the accuracy and efficiency of driver identity verification; it also avoids overly frequent face verification, reduces the impact on driving safety, and improves the user experience.

Description

Technical Field

[0001] The present invention belongs to the technical field of online car-hailing identity recognition, and particularly relates to a method and device for ensuring the consistency between the actual driving online car-hailing driver and the registered driver. Background Art

[0002] In recent years, online car-hailing has greatly facilitated people's daily travel. However, there are still many loopholes in the supervision of the online car-hailing market, especially regarding the personal safety of passengers. Since the launch of the online car-hailing platform, safety accidents have occurred frequently. The number of online car-hailing drivers is large, and their identities and vehicle driving records are difficult to screen, distinguish, supervise, and confirm, making it difficult to effectively guarantee the safety of passengers.

[0003] To prevent the safety problems caused by some people posing as drivers, in the prior art, face images are collected through intelligent mobile devices to obtain driver information, and then the driver's identity is determined based on the driver information. Usually, online car-hailing drivers will pre-register personal information on the operation platform and then verify the driver's identity when starting the service on the same day.

[0004] However, the traditional service only has a single face recognition identity verification process, and it cannot well guarantee the effectiveness after verification; overly frequent face verification may affect driving safety and user experience. Therefore, a new driver identity verification method is urgently needed. Summary of the Invention

[0005] The purpose of the present invention is to solve the above technical problems and provide a method and device for ensuring the consistency between the actual driving online car-hailing driver and the registered driver.

[0006] To solve the above problems, the present invention is implemented according to the following technical solutions:

[0007] In a first aspect, the present invention provides a method for ensuring the consistency between the actual driving online car-hailing driver and the registered driver, the method comprising the following steps:

[0008] Receiving an identity verification request sent by a mobile terminal, the identity verification request including the identity information of the driver to be verified and the device information of the mobile terminal;

[0009] Judging whether the number of identity verification failures of the driver to be verified exceeds the failure number threshold, if so, prohibiting the driver to be verified from driving; if not, proceeding to the next step;

[0010] Querying whether the identity verification request is the first identity verification request of the driver to be verified on the same day, if so, executing a face recognition process; if not, proceeding to the next step;

[0011] Query whether the previous identity authentication of the driver to be verified has failed. If so, execute the face recognition process; if not, proceed to the next step;

[0012] According to the device information of the mobile terminal, detect whether the driver to be verified has replaced the mobile terminal. If so, enter face recognition; if not, proceed to the next step;

[0013] Execute a random recognition process, and determine whether to enter face recognition based on the driving data of the driver to be verified.

[0014] Combined with the first aspect, the present invention also provides the first preferred implementation manner of the first aspect. Specifically,

[0015] When the face recognition process determines successful recognition, record the recognition record, and the recognition record includes the device information of the mobile terminal;

[0016] When the face recognition process determines failed recognition, prohibit the driver to be verified from driving out.

[0017] Combined with the first aspect, the present invention also provides the second preferred implementation manner of the first aspect. Specifically, according to the device information of the mobile terminal, detect whether the driver to be verified has replaced the mobile terminal, which specifically includes:

[0018] Retrieve the recognition record of the driver to be verified according to the identity information, and obtain the record information of the previous identity authentication from the recognition record. The record information includes the device information of the previous identity authentication;

[0019] Compare the device information of the current identity authentication with the device information of the previous identity authentication to determine whether the driver to be verified has replaced the mobile terminal.

[0020] Combined with the first aspect, the present invention also provides the third preferred implementation manner of the first aspect. Specifically, execute a random recognition process, and determine whether to enter face recognition based on the driving data of the driver to be verified, which specifically includes:

[0021] Query the previous vehicle return time of the driver to be verified and the corresponding driving duration on the same day;

[0022] Retrieve multiple preset random recognition strategies, where the random recognition strategies are pre-configured with a time threshold interval and a probability value of triggering a face recognition event. The time threshold intervals and probability values of triggering a face recognition event of multiple random recognition strategies are configured according to a preset gradient;

[0023] Identify the time threshold interval where the previous vehicle return time and the driving duration on the same day are located, and match the corresponding random recognition strategy;

[0024] Randomly execute the face recognition process according to the probability value of triggering a face recognition event of the random recognition strategy.

[0025] In combination with the first aspect, the present invention also provides a fourth preferred embodiment of the first aspect. Specifically, the method further includes:

[0026] Receiving an authentication request sent by a mobile terminal;

[0027] Detecting whether the driver to be verified has completed passive face recognition according to the identity information;

[0028] If so, determining whether the number of authentication failure times of the driver to be verified exceeds the failure times threshold;

[0029] If not, executing the passive face recognition process and requesting third-party information according to the identity information;

[0030] Verifying whether the face information of the driver to be verified is consistent with the third-party information. If so, completing the passive face recognition and allowing the driver to be verified to drive; if not, prohibiting the driver to be verified from driving.

[0031] In a second aspect, the present invention also provides a device for ensuring that the actual driving online car-hailing driver is consistent with the registered driver. The device includes:

[0032] A receiving module for receiving an authentication request sent by a mobile terminal, where the authentication request includes the identity information of the driver to be verified and the device information of the mobile terminal;

[0033] A judgment module for judging whether the number of authentication failure times of the driver to be verified exceeds the failure times threshold. If so, prohibiting the driver to be verified from driving; if not, proceeding to the next step;

[0034] A first authentication query module for querying whether the authentication request is the driver's first authentication request of the day. If so, executing the face recognition process; if not, proceeding to the next step;

[0035] A previous authentication query module for querying whether the previous authentication of the driver to be verified has failed. If so, executing the face recognition process; if not, proceeding to the next step;

[0036] A device replacement recognition module for detecting whether the driver to be verified has replaced the mobile terminal according to the device information of the mobile terminal. If so, entering the face recognition; if not, proceeding to the next step;

[0037] A random recognition execution module for executing a random recognition process and judging whether to enter the face recognition according to the driving data of the driver to be verified.

[0038] In combination with the second aspect, the present invention also provides the first preferred implementation manner of the second aspect. Specifically,

[0039] When the face recognition process determines that the recognition is successful, a recognition record is recorded, and the recognition record includes the device information of the mobile terminal;

[0040] When the face recognition process determines that the recognition fails, the driver to be verified is prohibited from driving out.

[0041] In combination with the second aspect, the present invention also provides the second preferred implementation manner of the second aspect. Specifically, the device replacement recognition module detects whether the driver to be verified has replaced the mobile terminal according to the device information of the mobile terminal, specifically including:

[0042] Retrieve the recognition record of the driver to be verified according to the identity information, and obtain the record information of the previous identity authentication from the recognition record. The record information includes the device information of the previous identity authentication;

[0043] Compare the device information of the current identity authentication with the device information of the previous identity authentication to determine whether the driver to be verified has replaced the mobile terminal.

[0044] In combination with the second aspect, the present invention also provides the third preferred implementation manner of the second aspect. Specifically, the random recognition execution module executes a random recognition process and determines whether to enter face recognition according to the driving data of the driver to be verified, specifically including:

[0045] Query the previous vehicle shutdown time of the driver to be verified and the corresponding driving duration on the current day;

[0046] Retrieve multiple preset random recognition strategies. Among them, the random recognition strategies are pre-configured with a time threshold interval and a triggering face recognition event probability value, and the time threshold intervals and triggering face recognition event probability values of the multiple random recognition strategies are configured according to a preset gradient;

[0047] Identify the time threshold interval where the previous vehicle shutdown time and the driving duration on the current day are located, and match the corresponding random recognition strategy;

[0048] Randomly execute the face recognition process according to the triggering face recognition event probability value of the random recognition strategy.

[0049] In combination with the second aspect, the present invention also provides the fourth preferred implementation manner of the second aspect. Specifically, the device includes a passive authentication module, which is used to perform the following steps:

[0050] Receive the identity verification request sent by the mobile terminal;

[0051] Detect whether the driver to be verified has completed passive face recognition according to the identity information;

[0052] If so, determine whether the number of identity verification failures of the driver to be verified exceeds the failure threshold;

[0053] If not, execute the passive face recognition process and request third-party information according to the identity information;

[0054] Verify whether the face information of the driver to be verified is consistent with the third-party information. If so, complete the passive face recognition and allow the driver to be verified to drive; if not, prohibit the driver to be verified from driving.

[0055] Compared with the prior art, the beneficial effects of the present invention are:

[0056] The method for ensuring the consistency between the actual driving online car-hailing driver and the registered driver provided by the present invention includes: receiving an identity verification request sent by a mobile terminal, where the identity verification request includes the identity information of the driver to be verified and the device information of the mobile terminal; determining whether the number of identity verification failures of the driver to be verified exceeds the failure threshold. If so, prohibit the driver to be verified from driving; if not, proceed to the next step; query whether the identity verification request is the first identity verification request of the driver to be verified on the current day. If so, execute the face recognition process; if not, proceed to the next step; query whether the previous identity authentication of the driver to be verified failed. If so, execute the face recognition process; if not, proceed to the next step; according to the device information of the mobile terminal, detect whether the driver to be verified has replaced the mobile terminal. If so, enter the face recognition; if not, proceed to the next step; execute the random recognition process, and determine whether to enter the face recognition according to the driving data of the driver to be verified.

[0057] This method forms a comprehensive identity verification strategy by judging whether the number of identity verification failures exceeds the failure threshold, querying the first identity verification request on the current day, querying whether the previous identity authentication failed, detecting whether the driver to be verified has replaced the mobile terminal, and executing the random recognition process in the order of selection from top to bottom to perform face recognition on the driver to be verified. It eliminates the traditional single face recognition identity verification for business, is effective and feasible, and improves the accuracy and efficiency of driver identity verification; it also avoids overly frequent face verification, reduces the impact on driving safety, and improves the user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0058] The following further details the specific embodiments of the present invention with reference to the drawings, where:

[0059] Figure 1 is a schematic diagram of the application scenario involved in the present invention;

[0060] Figure 2It is a schematic flowchart of the method for ensuring the consistency between the actual driving online car-hailing driver and the registered driver of the present invention;

[0061] Figure 3 It is a schematic diagram of the composition of the device for ensuring the consistency between the actual driving online car-hailing driver and the registered driver of the present invention. Detailed implementation manners

[0062] The following describes the preferred embodiments of the present invention with reference to the accompanying drawings. It should be understood that the preferred embodiments described herein are only used to illustrate and explain the present invention, and are not used to limit the present invention.

[0063] The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only a part of the embodiments of the present invention, rather than all the embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present invention without creative efforts shall fall within the protection scope of the present invention.

[0064] Terms such as "first", "second", "third", "fourth", etc. (if any) in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and do not have to be used to describe a specific order or sequence. It should be understood that such data can be interchanged under appropriate circumstances, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "comprising" and "having" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, product or device comprising a series of steps or units does not have to be limited to those steps or units clearly listed, but may include other steps or units not clearly listed or inherent to these processes, methods, products or devices.

[0065] In order to enable those skilled in the art to use the content of this application, the following implementation manners are given in combination with a specific application scenario, the "online car-hailing scenario". For those skilled in the art, without departing from the spirit and scope of this application, the general principles defined here can be applied to other embodiments and application scenarios. Although this application is mainly described around the "online car-hailing scenario", it should be understood that this is only an exemplary embodiment. This application can be applied to any other means of transportation, which can include taxis, private cars, carpooling, buses, etc., or any combination thereof. This application can also include any service system for online car-hailing.

[0066] Figure 1 It is a schematic diagram of the application scenario related to the present invention. As Figure 1As shown, the method provided by the present invention for ensuring that the actual driver of the online car-hailing service is the same as the registered driver can be applied to the scenario of interaction between the terminal device and the server. Among them, the above terminal device can be installed with an online car-hailing application, that is, an application program (Application, APP) that can provide the function of the online car-hailing service. The above server can be the server corresponding to the online car-hailing application. The above terminal device and the server can communicate through the Internet. Specifically, the above terminal device can be a mobile device, a handheld device, a vehicle-mounted device, a wearable device, a computing device, and various forms of user equipment (User Equipment, UE), mobile station (Mobile Station, MS), and terminal.

[0067] Among them, the server runs the server side of the online car-hailing platform, and the terminal device runs the client side of the online car-hailing platform. The terminal device can be divided into a driver side and a user side. After a passenger uses the user side to issue a travel order on the online car-hailing platform, the driver can use the driver side to undertake the travel order on the online car-hailing platform and provide travel services.

[0068] Generally, an online car-hailing driver will pre-register personal information on the online car-hailing platform and then verify the driver's identity when starting the service on the same day. However, the existing technology only performs face recognition-based identity verification on the driver when starting the service on the same day, only through a single face recognition identity verification process, and after the verification, it cannot well ensure the effectiveness. Illegal personnel let the registered driver complete the identity verification and then replace them to conduct the identity verification on behalf of the registered driver. And overly frequent face verification may affect driving safety, so multiple-frequency verification also affects the user experience and driving safety. Therefore, there is an urgent need for a new driver identity verification method to improve the accuracy and efficiency of driver identity verification.

[0069] Embodiment 1

[0070] Figure 2 It is a flowchart of an embodiment of the method provided by the present invention for ensuring that the actual driver of the online car-hailing service is the same as the registered driver. The execution subject of this embodiment can be a device for ensuring that the actual driver of the online car-hailing service is the same as the registered driver. Specifically, the device can be set in the Figure 1 server shown in a software or hardware manner.

[0071] As Figure 2 shown, the method for ensuring that the actual driver of the online car-hailing service is the same as the registered driver in this embodiment can include:

[0072] S100: Receive an identity verification request sent by the mobile terminal, where the identity verification request includes the identity information of the driver to be verified and the device information of the mobile terminal.

[0073] In one implementation, the driver's identity information includes at least name, mobile phone number, ID card number, and driver's license information, and may also include vehicle information, address, etc. The device information of the mobile terminal, such as a mobile phone, may consist of device model, serial number, device code, etc.

[0074] In a specific implementation, the identity verification request is initiated by the online car-hailing application deployed on the mobile terminal. The events that trigger the identity verification request can be that the driver actively initiates it during operation, such as logging in to the driver account, starting a trip, ending a trip, etc.; or the online car-hailing application autonomously initiates an identity verification operation to the server in specific scenarios. For example, when the driver first uses the online car-hailing application to provide travel services on the same day, such as when logging in to the driver account; when receiving a travel order, such as a relay order, a carpool order, a reservation order, a private car order, etc.; or when triggering a driver service complaint event, a driver reporting event, etc.

[0075] Taking daily travel as an example, the user hails a car through a taxi-hailing software. The whole process nodes of pick-up and drop-off generally include: the driver starts a trip / the passenger places an order / the driver accepts the order / picks up and drops off the passenger, etc. At many important business nodes, such as: the driver listens for orders / the driver goes to pick up the passenger, etc., add checkpoints to check whether the driving driver is consistent with the registered driver. The online car-hailing application autonomously initiates an identity verification operation to the server at the checkpoint. Restrict the subsequent business operations of inconsistent drivers, and at the same time collect identification information for subsequent follow-up management by driver managers, so as to improve safety protection and avoid safety and compliance risks.

[0076] Specifically, the online car-hailing application autonomously initiates an identity verification operation to the server in specific scenarios, which is independently configured by the online car-hailing operation platform to implement identity verification for different business scenarios and ensure user safety in multiple aspects.

[0077] S200: Determine whether the number of identity verification failures of the driver to be verified exceeds the failure times threshold.

[0078] S210: If so, prohibit the driver to be verified from starting a trip.

[0079] S220: If not, proceed to step S300.

[0080] In a specific implementation, the failure times threshold can be configured based on a time period, such as the failure times threshold within a day, such as 5 times a day; the failure times threshold within a week, such as 30 times a week; etc. In another implementation, the failure times threshold can be set based on business scenarios, such as the failure times threshold for different business nodes. For example, the driver listens for orders / 3 times; the driver goes to pick up the passenger / 3 times, or different business scenarios, such as the current carpool service / 5 times, the current private car service / 5 times.

[0081] In one implementation, when the driver authentication fails, a failure record is recorded to obtain the number of driver authentication failures for the driver to be verified. The number of authentication failures is incremented during each verification and reset after a certain period is met.

[0082] S300: Query whether the authentication request is the first authentication request of the day for the driver to be verified.

[0083] S310: If so, execute the face recognition process.

[0084] S320: If not, proceed to step S400.

[0085] Step S300 is a regular verification of the consistency between the personal and identity information of the driver to be verified, while also taking into account the convenient operation when an ordinary driver makes the first trip. When the driver is not making the first trip, step S300 is skipped to improve the driver experience.

[0086] S400: Query whether the previous authentication of the driver to be verified failed.

[0087] S410: If so, execute the face recognition process.

[0088] S420: If not, proceed to step S500.

[0089] After research by the applicant, it is found that there are technical loopholes in the existing identity verification process. If the policy randomly performs identity verification in a completely stateless manner, the driver can bypass the identity verification by continuously trying operations, such as continuously sliding the trip start event without performing identity recognition. Therefore, the core of this step S400 is that if face recognition has been initiated in the past but the driver has not successfully completed it, forced face recognition is required for the current trip start. This prevents the driver from continuously sliding the trip start without performing recognition and bypassing the identity verification process through loopholes.

[0090] In one implementation, when the driver authentication fails or is not completed, a failure record is recorded to obtain the previous authentication failure record of the driver to be verified, thereby implementing the query of the previous authentication result in step S400.

[0091] S500: According to the device information of the mobile terminal, detect whether the driver to be verified has changed the mobile terminal.

[0092] S510: If so, proceed to face recognition.

[0093] S510: If not, proceed to the next step.

[0094] In this embodiment, step S500 is as described in the text. Replacing the mobile device means that the mobile device used by the driver to be verified for face recognition currently is different from the mobile device used for face recognition in the previous time. The applicant found during the service operation that in the scenario of replacing the mobile device, there is a higher probability that a registered driver on the online car-hailing platform uses the mobile device of a "driver for hire" who is not on the online car-hailing platform to perform face recognition, and then allows the latter to drive the vehicle for operation.

[0095] S600: Execute the random recognition process, and determine whether to enter face recognition based on the driving data of the driver to be verified.

[0096] In the above steps, when the face recognition process determines that the recognition is successful, record the recognition record. The recognition record includes the device information of the mobile terminal, and the driver to be verified can smoothly perform corresponding operations, provide travel services, etc. When the face recognition process determines that the recognition fails, prohibit the driver to be verified from driving out.

[0097] The travel health of traditional services highly depends on the verification between the fleet management and the driver. Moreover, after the verification, it cannot be well guaranteed to be effective. However, in the context of highly ensuring the safety of online car-hailing, it should be strictly avoided to delay the handling of drivers' illegal operations. And in the business scenario of online car-hailing, the online car-hailing company often conducts unified management of online car-hailing drivers online, and it is very difficult to monitor each driver in real time. The comprehensive identity verification strategy formed by the organic combination of the above S200 - S600 in this invention, the combination of strategies in a specific order aims to increase the difficulty of drivers' cheating. When the identity verification strategy increases the cheating difficulty and compresses the space for drivers to cheat, which is sufficient to affect the profitability of drivers' cheating, it can achieve the effect of strict enforcement, and avoid non-registered drivers using the accounts of registered drivers to drive out and pick up passengers for operation. At the same time, in step S100, it is preset to initiate identity verification independently at many important business nodes, so as to restrict the subsequent business operations of inconsistent drivers, and at the same time collect recognition information for the subsequent follow-up management of driver managers, thereby improving safety guarantee and avoiding safety and compliance risks.

[0098] This method forms a comprehensive identity verification strategy for face recognition of the driver to be verified by judging whether the number of identity verification failures exceeds the failure threshold, querying the first identity verification request of the day, querying whether the previous identity authentication fails, detecting whether the driver to be verified replaces the mobile terminal, and executing the random recognition process in the selection order from top to bottom. It eliminates the traditional single face recognition identity verification for services, is effective and feasible, and improves the accuracy and efficiency of driver identity verification; it also avoids overly frequent face verification, reduces the impact on driving safety, and improves the user experience.

[0099] In a specific implementation, in step S500, according to the device information of the mobile terminal, it is detected whether the driver to be verified has replaced the mobile terminal, which specifically includes:

[0100] S501: Retrieve the identification record of the driver to be verified according to the identity information, and obtain the record information of the previous identity authentication from the identification record. The record information includes the device information of the previous identity authentication.

[0101] In a specific implementation, the device information of the mobile terminal, such as a mobile phone, can be composed of a device model, a serial number, a device code, etc. To achieve comparison, obtaining the device information of the mobile terminal is an existing technology in this field and will not be elaborated here.

[0102] S502: Compare the device information of the current identity authentication with the device information of the previous identity authentication to determine whether the driver to be verified has replaced the mobile terminal.

[0103] In a specific implementation, in step S600, execute a random identification process, and determine whether to enter the face recognition according to the driving data of the driver to be verified, which specifically includes:

[0104] S601: Query the previous vehicle return time of the driver to be verified and the corresponding driving duration on the same day;

[0105] S602: Retrieve multiple preset random identification strategies. Among them, the random identification strategy is pre-configured with a time threshold interval and a probability value of triggering a face recognition event, and the time threshold intervals and probability values of triggering a face recognition event of multiple random identification strategies are configured according to a preset gradient.

[0106] In an example, 10 random identification strategies can be preset and arranged in order from 1 to 6. For example, the time threshold interval of the first random identification strategy is from 18:00 to 19:00 for the previous vehicle return time and 0 to 8 hours for the driving duration on the same day, and the probability value of triggering a face recognition event is 30%; the time threshold interval of the second random identification strategy is from 19:00 to 20:00 for the previous vehicle return time and 8 to 9 hours for the driving duration on the same day, and the probability value of triggering a face recognition event is 40%; and so on. The time threshold intervals and probability values of triggering a face recognition event from 1 to 10 can be configured with corresponding gradients.

[0107] S603: Identify the time threshold interval where the previous vehicle return time and the driving duration on the same day are located, and match the corresponding random identification strategy;

[0108] S604: Randomly execute the face recognition process according to the probability value of triggering a face recognition event of the random identification strategy.

[0109] Among them, when performing the random execution of the face recognition process, when the face recognition process needs to be executed, the driver needs to authenticate his identity, and only after passing can he drive the vehicle. When the face recognition process is not hit, the driver does not need to authenticate his identity and can drive the vehicle and perform other operations.

[0110] In step S600, by querying the driver's last vehicle return time and the driving duration on the current day, when they exceed a certain time threshold (which can be configured gradiently), the face recognition process is randomly pulled up (corresponding to the above time threshold, the probability can be configured gradiently). When the driving duration is relatively long and does not conform to the normal driving duration, it can be considered as the proxy operation behavior of an unregistered driver.

[0111] Query the driver's last vehicle return time and the driving duration on the current day. When they exceed a certain time threshold (which can be configured gradiently), the face recognition process is randomly pulled up (corresponding to the above time threshold, the probability can be configured gradiently).

[0112] Embodiment 2

[0113] The method for ensuring that the actual driving online car-hailing driver is the same as the registered driver described in this Embodiment 2 is completely the same as the method and principle of Embodiment 1. This Embodiment 2 also provides a method for ensuring that the actual driving online car-hailing driver is the same as the registered driver. The method further includes:

[0114] S100: Receive the identity verification request sent by the mobile terminal;

[0115] S10: Detect whether the driver to be verified has completed passive face recognition according to the identity information;

[0116] S20: If so, determine whether the number of identity verification failures of the driver to be verified exceeds the failure threshold;

[0117] S30: If not, execute the passive face recognition process and request third-party information according to the identity information;

[0118] S40: Verify whether the face information of the driver to be verified is consistent with the third-party information. If so, complete the passive face recognition and allow the driver to be verified to drive the vehicle, and store the face information for use in the face recognition process; if not, prohibit the driver to be verified from driving the vehicle.

[0119] Compared with the prior art, when a driver makes the first trip on an online car-hailing platform, it is determined whether the driver has successfully undergone passive face recognition. If so, steps S200 - S600 are executed. If not, based on information such as the driver's registered name and ID number, passive face recognition is initiated: request information from the Ministry of Public Security to verify whether the current driver's face matches the archived information in the public security database. If the identities are consistent, the driver is allowed to make a trip and the face photo that can currently pass the identity verification is stored for subsequent face recognition (i.e., active recognition / face recognition process). If the identities are inconsistent, an error is prompted and the driver's trip is intercepted.

[0120] Through the above technical means, the data authority of passive recognition, i.e., the subsequent face recognition process, can be ensured, and the cost of subsequent face recognition can be greatly reduced (the cost of active face recognition is lower and there are also many open-source and stable implementation solutions).

[0121] Embodiment 3

[0122] Refer to Figure 3 As shown, Embodiment 3 of the present invention provides a device for ensuring that the actual driver of an online car-hailing vehicle is the same as the registered driver. This device can be deployed in the processor of the server and execute the method for ensuring that the actual driver of an online car-hailing vehicle is the same as the registered driver described above.

[0123] For the device for ensuring that the actual driver of an online car-hailing vehicle is the same as the registered driver described in Embodiment 3 of the present invention, the device includes:

[0124] A receiving module, which is used to receive an identity verification request sent by a mobile terminal, and the identity verification request includes the identity information of the driver to be verified and the device information of the mobile terminal;

[0125] A judgment module, which is used to judge whether the number of identity verification failures of the driver to be verified exceeds the failure times threshold. If so, the driver to be verified is prohibited from making a trip; if not, the next step is entered;

[0126] A first authentication query module, which is used to query whether the identity verification request is the driver to be verified's first identity verification request on the current day. If so, the face recognition process is executed; if not, the next step is entered;

[0127] A previous authentication query module, which is used to query whether the previous identity authentication of the driver to be verified failed. If so, the face recognition process is executed; if not, the next step is entered;

[0128] A device replacement recognition module, which is used to detect whether the driver to be verified has replaced the mobile terminal according to the device information of the mobile terminal. If so, face recognition is entered; if not, the next step is entered;

[0129] A random recognition execution module, which is used to execute a random recognition process and determine whether to enter face recognition based on the driving data of the driver to be verified.

[0130] Specifically, the device replacement recognition module detects whether the driver to be verified has replaced the mobile terminal according to the device information of the mobile terminal, specifically including:

[0131] Retrieve the recognition record of the driver to be verified according to the identity information, and obtain the record information of the previous identity authentication from the recognition record, where the record information includes the device information of the previous identity authentication;

[0132] Compare the device information of the current identity authentication with the device information of the previous identity authentication to determine whether the driver to be verified has replaced the mobile terminal.

[0133] Specifically, the random recognition execution module executes a random recognition process and determines whether to enter face recognition based on the driving data of the driver to be verified, specifically including:

[0134] Query the previous vehicle closing time of the driver to be verified and the corresponding driving duration on the same day;

[0135] Retrieve multiple preset random recognition strategies, where the random recognition strategies are pre-configured with a time threshold interval and a triggering face recognition event probability value, and the time threshold intervals and triggering face recognition event probability values of multiple random recognition strategies are configured according to a preset gradient;

[0136] Identify the time threshold interval where the previous vehicle closing time and the driving duration on the same day are located, and match the corresponding random recognition strategy;

[0137] Randomly execute the face recognition process according to the triggering face recognition event probability value of the random recognition strategy.

[0138] Specifically, the device includes a passive authentication module, which is used to perform the following steps:

[0139] Receive the identity verification request sent by the mobile terminal;

[0140] Detect whether the driver to be verified has completed passive face recognition according to the identity information;

[0141] If so, determine whether the number of identity verification failures of the driver to be verified exceeds the failure number threshold;

[0142] If not, execute the passive face recognition process and request third-party information according to the identity information;

[0143] Verify whether the face information of the driver to be verified is consistent with the third-party information. If so, complete the passive face recognition and allow the driver to be verified to drive the vehicle; if not, prohibit the driver to be verified from driving the vehicle.

[0144] For other structures of the method and device for ensuring the consistency between the actual online car-hailing driver and the registered driver in this embodiment, refer to the prior art.

[0145] The above are only the preferred embodiments of the present invention, and do not impose any formal restrictions on the present invention. Therefore, any modifications, equivalent changes, and decorations made to the above embodiments based on the technical essence of the present invention without departing from the content of the technical solution of the present invention still fall within the scope of the technical solution of the present invention.

Claims

1. A method for ensuring the consistency between the actual online car-hailing driver during driving and the registered driver, characterized in that, The method includes the following steps: Receiving an authentication request sent by a mobile terminal, where the authentication request includes the identity information of the driver to be verified and the device information of the mobile terminal; Judging whether the number of authentication failures of the driver to be verified exceeds the failure threshold. If so, prohibiting the driver to be verified from driving; if not, proceeding to the next step; Querying whether the authentication request is the first authentication request of the driver to be verified on the current day. If so, executing a face recognition process; if not, proceeding to the next step; Querying whether the previous authentication of the driver to be verified failed. If so, executing a face recognition process; if not, proceeding to the next step; Detecting whether the driver to be verified has replaced the mobile terminal according to the device information of the mobile terminal. If so, entering the face recognition process; if not, proceeding to the next step; Executing a random recognition process and judging whether to enter face recognition according to the driving data of the driver to be verified; Among them, the execution of the random recognition process and judging whether to enter face recognition according to the driving data of the driver to be verified specifically includes: Querying the previous vehicle return time of the driver to be verified and the corresponding driving duration on the current day; Retrieving multiple preset random recognition policies, where the random recognition policies are pre-configured with a time threshold interval and a probability value of triggering a face recognition event, and the time threshold intervals and probability values of triggering a face recognition event of the multiple random recognition policies are configured according to a preset gradient; Identifying the time threshold interval where the previous vehicle return time and the current day's driving duration are located, and matching the corresponding random recognition policy; Randomly executing a face recognition process according to the probability value of triggering a face recognition event of the random recognition policy.

2. The method for ensuring that the actual driving online car-hailing driver is consistent with the registered driver according to claim 1, characterized in that: When the face recognition process determines successful recognition, recording the recognition record, where the recognition record includes the device information of the mobile terminal; When the face recognition process determines failed recognition, prohibiting the driver to be verified from driving.

3. The method for ensuring the consistency between the actual online car-hailing driver and the registered driver as claimed in claim 1, wherein Detecting whether the driver to be verified has replaced the mobile terminal according to the device information of the mobile terminal, specifically including: Retrieving the recognition record of the driver to be verified according to the identity information, and obtaining the record information of the previous authentication from the recognition record, where the record information includes the device information of the previous authentication; Comparing the device information of the current authentication with the device information of the previous authentication, and judging whether the driver to be verified has replaced the mobile terminal.

4. The method for ensuring the consistency between the actual online car-hailing driver and the registered driver as claimed in claim 1, characterized in that, The method further includes: Receiving an authentication request sent by a mobile terminal; Detecting whether the driver to be verified has completed passive face recognition according to the identity information; If so, judging whether the number of authentication failures of the driver to be verified exceeds the failure threshold; If not, executing a passive face recognition process and requesting third-party information according to the identity information; Verifying whether the face information of the driver to be verified is consistent with the third-party information. If so, completing passive face recognition and allowing the driver to be verified to drive; if not, prohibiting the driver to be verified from driving.

5. A device for ensuring the consistency between the actual online car-hailing driver and the registered driver, characterized in that, The device includes: A receiving module, which is used to receive the authentication request sent by the mobile terminal, and the authentication request includes the identity information of the driver to be verified and the device information of the mobile terminal; A judging module, which is used to judge whether the number of authentication failures of the driver to be verified exceeds the failure times threshold. If so, the driver to be verified is prohibited from driving; if not, proceed to the next step; A first authentication query module, which is used to query whether the authentication request is the driver to be verified's first authentication request on the current day. If so, execute the face recognition process; if not, proceed to the next step; A previous authentication query module, which is used to query whether the previous authentication of the driver to be verified failed. If so, execute the face recognition process; if not, proceed to the next step; A device replacement recognition module, which is used to detect whether the driver to be verified has replaced the mobile terminal according to the device information of the mobile terminal. If so, enter face recognition; if not, proceed to the next step; A random recognition execution module, which is used to execute the random recognition process and judge whether to enter face recognition according to the driving data of the driver to be verified; Among them, the execution of the random recognition process and judging whether to enter face recognition according to the driving data of the driver to be verified specifically includes: Query the previous vehicle departure time of the driver to be verified and the corresponding driving duration on the current day; Retrieve multiple preset random recognition strategies, where the random recognition strategies are pre-configured with a time threshold interval and a probability value of triggering a face recognition event, and the time threshold intervals and probability values of triggering a face recognition event of multiple random recognition strategies are configured according to a preset gradient; Identify the time threshold interval where the previous vehicle departure time and the current day's driving duration are located, and match the corresponding random recognition strategy; Randomly execute the face recognition process according to the probability value of triggering a face recognition event of the random recognition strategy.

6. The device for ensuring the consistency between the actual driving online car-hailing driver and the registered driver according to claim 5, characterized in that: When the face recognition process determines that the recognition is successful, record the recognition record, and the recognition record includes the device information of the mobile terminal; When the face recognition process determines that the recognition fails, the driver to be verified is prohibited from driving.

7. The device for ensuring the consistency between the actual online car-hailing driver and the registered driver according to claim 5, characterized in that The device replacement recognition module detects whether the driver to be verified has replaced the mobile terminal according to the device information of the mobile terminal, specifically including: Retrieve the recognition record of the driver to be verified according to the identity information, and obtain the record information of the previous authentication from the recognition record, and the record information includes the device information of the previous authentication; Compare the device information of the current authentication with the device information of the previous authentication to judge whether the driver to be verified has replaced the mobile terminal.

8. The device for ensuring the consistency between the actual online car-hailing driver and the registered driver according to claim 5, wherein The random recognition execution module executes the random recognition process and judges whether to enter face recognition according to the driving data of the driver to be verified, specifically including: Query the previous vehicle departure time of the driver to be verified and the corresponding driving duration on the current day; Retrieve multiple preset random recognition strategies, where the random recognition strategies are pre-configured with a time threshold interval and a probability value of triggering a face recognition event, and the time threshold intervals and probability values of triggering a face recognition event of multiple random recognition strategies are configured according to a preset gradient; Identify the time threshold interval where the previous vehicle return time and the driving duration on the current day are located, and match the corresponding random identification strategy; Randomly execute the face recognition process according to the probability value of the face recognition event triggered by the random identification strategy.

9. The device for ensuring the consistency between the actual online car-hailing driver and the registered driver according to claim 5, characterized in that, The device includes a passive authentication module, which is used to execute the following steps: Receive the identity verification request sent by the mobile terminal; Detect whether the driver to be verified has completed passive face recognition according to the identity information; If so, determine whether the number of identity verification failures of the driver to be verified exceeds the failure threshold; If not, execute the passive face recognition process and request third-party information according to the identity information; Verify whether the face information of the driver to be verified is consistent with the third-party information. If so, complete the passive face recognition and allow the driver to be verified to drive the vehicle. If not, prohibit the driver to be verified from driving the vehicle.

Images