CN112562100B - User binding method and device - Google Patents
User binding method and device Download PDFInfo
- Publication number
- CN112562100B CN112562100B CN202011437480.XA CN202011437480A CN112562100B CN 112562100 B CN112562100 B CN 112562100B CN 202011437480 A CN202011437480 A CN 202011437480A CN 112562100 B CN112562100 B CN 112562100B
- Authority
- CN
- China
- Prior art keywords
- bound
- parking
- license plate
- plate number
- user
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07B—TICKET-ISSUING APPARATUS; FARE-REGISTERING APPARATUS; FRANKING APPARATUS
- G07B15/00—Arrangements or apparatus for collecting fares, tolls or entrance fees at one or more control points
- G07B15/02—Arrangements or apparatus for collecting fares, tolls or entrance fees at one or more control points taking into account a variable factor such as distance or time, e.g. for passenger transport, parking systems or car rental systems
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
- G07C9/00—Individual registration on entry or exit
- G07C9/20—Individual registration on entry or exit involving the use of a pass
- G07C9/22—Individual registration on entry or exit involving the use of a pass in combination with an identity check of the pass holder
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/0853—Network architectures or network communication protocols for network security for authentication of entities using an additional device, e.g. smartcard, SIM or a different communication terminal
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/0876—Network architectures or network communication protocols for network security for authentication of entities based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
Abstract
The specification discloses a user binding method and device. The method is applied to a server and comprises the following steps: receiving a user binding request, wherein the request carries a driving license image and a user identifier to be bound; obtaining a license plate number to be bound according to the driving license image; determining at least one parking record containing the license plate number to be bound in the pre-acquired parking records containing the license plate number; and if the parking record associated with the to-be-bound user identifier in the determined parking record meets a first preset quantification condition, binding the to-be-bound user identifier and the to-be-bound license plate number.
Description
Technical Field
The embodiment of the specification relates to the technical field of computer application, in particular to a user binding method and device.
Background
Currently, a parking lot may push a notification to a user bound with a vehicle entering or exiting the parking lot over a network for the vehicle. Specifically, the notification may be a payment notification, an entrance notification, or an exit notification.
In the specific binding process, the user can bind the account of the user with the vehicle corresponding to the driving license image by uploading the driving license image in a webpage or a specific application. After the binding is completed, the parking lot can push a notification to the terminal logging in the user account according to the track of the vehicle.
But this binding process may cause problems such as privacy disclosure. For example, after a driving license image of a vehicle owner is acquired by some methods, any user account (non-vehicle-owner account) can be bound with the vehicle of the vehicle owner without permission of the vehicle owner, and a terminal logging in the account can receive a notice pushed by a parking lot for the vehicle of the vehicle owner, so that privacy information such as the whereabouts of the vehicle owner can be mastered.
Disclosure of Invention
In order to solve the above problems, the present specification provides a user binding method and apparatus. The technical scheme is as follows.
A user binding method is applied to a server and comprises the following steps:
receiving a user binding request, wherein the request carries a driving license image and a user identifier to be bound;
obtaining a license plate number to be bound according to the driving license image;
determining at least one parking record containing the license plate number to be bound in the pre-acquired parking records containing the license plate number;
and if the parking record associated with the to-be-bound user identifier in the determined parking record meets a first preset quantification condition, binding the to-be-bound user identifier and the to-be-bound license plate number.
A user binding device is applied to a server and comprises:
a request receiving unit: the system comprises a server and a server, wherein the server is used for receiving a user binding request, and the request carries a driving license image and a user identifier to be bound;
license plate number acquisition unit: the license plate number binding device is used for obtaining a license plate number to be bound according to the driving license image;
a determination unit: the system comprises a server and a server, wherein the server is used for determining at least one parking record containing a license plate number to be bound in the pre-acquired parking records containing the license plate number;
a binding unit: and the system is used for binding the user identifier to be bound and the license plate number to be bound if the parking record associated with the user identifier to be bound in the determined parking records meets a first preset quantification condition.
In the technical scheme, the parking records containing the license plate numbers to be bound are additionally utilized for verification aiming at the users to be bound. If the parking records associated with the identifiers of the users to be bound in the parking records containing the license plates to be bound meet the preset quantitative conditions, the fact that the vehicles to which the license plates to be bound belong are frequently used by the users to be bound in the past can be shown, and the vehicles to which the license plates to be bound belong are actual drivers of the vehicles to which the license plates to be bound belong can be bound. By adding the verification step, whether the user to be bound is an actual driver of the vehicle to which the license plate number to be bound belongs is verified, so that the risk of privacy information leakage is reduced.
Drawings
In order to more clearly illustrate the embodiments of the present specification or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments described in the embodiments of the present specification, and other drawings can be obtained by those skilled in the art according to the drawings.
Fig. 1 is a flowchart illustrating a user binding method provided in an embodiment of the present specification;
FIG. 2 is a flow chart illustrating another user binding method provided by an embodiment of the present specification;
FIG. 3 is a flowchart illustrating another user binding method provided by an embodiment of the present specification;
FIG. 4 is a flowchart illustrating another user binding method provided by an embodiment of the present specification;
fig. 5 is a flowchart illustrating a notification sending method provided in an embodiment of the present specification;
fig. 6 is a schematic structural diagram of a user binding apparatus provided in an embodiment of the present specification;
fig. 7 is a schematic structural diagram of another user binding apparatus provided in an embodiment of the present specification;
fig. 8 is a schematic structural diagram of a notification transmission apparatus provided in an embodiment of the present specification;
fig. 9 is a schematic structural diagram of an apparatus for configuring a method according to an embodiment of the present disclosure.
Detailed Description
In order to make those skilled in the art better understand the technical solutions in the embodiments of the present specification, the technical solutions in the embodiments of the present specification will be described in detail below with reference to the drawings in the embodiments of the present specification, and it is obvious that the described embodiments are only a part of the embodiments of the present specification, and not all the embodiments. All other embodiments that can be derived by one of ordinary skill in the art from the embodiments given herein are intended to be within the scope of protection.
Currently, a parking lot may push a notification to a user bound with a vehicle entering or exiting the parking lot over a network for the vehicle. Specifically, the notification may be a payment notification, an entrance notification, or an exit notification.
The specific process of pushing the notification may include: the parking lot equipment acquires an image of a license plate number on a vehicle driving into or out of the parking lot through the camera device, identifies the license plate number through an image identification technology, and generates a notice according to the license plate number. The type of the notification can be a payment notification, and the payment notification is sent to a user according to the consumption condition of the vehicle in the parking lot; the notification may be an entrance or exit notification, and the notification may be transmitted to the user in response to the entrance or exit of the vehicle in the parking lot.
Since the user binds the license plate number and the user account in advance, the parking lot device can send a notification generated for a certain license plate number to a terminal logged in with the corresponding bound user account through a network.
In the specific binding process, the user can log in a user account in a webpage or a specific application, upload the driving license image and bind the user account with the vehicle corresponding to the driving license image. After the binding is completed, the parking lot can push a notification to the terminal logging in the user account according to the track of the vehicle.
However, the user identity is not actually verified in the binding process, the binding can be performed only by means of the driving license image, the security is low, and problems such as privacy information leakage and the like can be caused.
For example, after a driving license image of a vehicle owner is acquired by some methods, any user account (non-vehicle-owner account) can be bound with the vehicle of the vehicle owner without permission of the vehicle owner, and a terminal logging in the account can receive a notice pushed by a parking lot for the vehicle of the vehicle owner, so that privacy information such as the whereabouts of the vehicle owner can be mastered.
In order to solve the above problems, the present specification provides a user binding method. And aiming at the user needing to bind the license plate number (the user to be bound), additionally utilizing the parking record containing the license plate number needing to be bound (the license plate number to be bound) for verification. If the parking records associated with the identifiers of the users to be bound in the parking records containing the license plates to be bound meet the preset quantitative conditions, the fact that the vehicles to which the license plates to be bound belong are frequently used by the users to be bound to park in the parking lot can be shown, and the users to be bound can be bound by the actual drivers of the vehicles to which the license plates to be bound belong. In the embodiment, whether the user to be bound is the actual driver of the vehicle to which the license plate number to be bound belongs is verified by adding the verification step, so that the risk of privacy information leakage is reduced.
Fig. 1 is a schematic flow chart of a user binding method provided in this specification. The method can be applied to a server and at least comprises the following steps.
S101: a user binding request is received.
The user binding request may be sent by a user through a terminal logged in with a user account, and is used for binding the user account and the license plate number so as to receive a relevant notification of the parking lot.
The user binding request can carry a driving license image and a user identifier to be bound. The driving license image may include a license plate number in the driving license information, and the user identifier may be a user account, or may be another identifier capable of correspondingly acquiring the user account. For example, the user identifier may be an identity card number of the user, and the server may uniquely determine the corresponding user account according to the identity card number of the user.
S102: and obtaining the license plate number to be bound according to the driving license image in the request.
After receiving the user binding request, the server side can verify whether the driving license image in the request is legal or not. The method specifically comprises the following steps: verifying whether the travel license image is altered, verifying whether the travel license information included in the travel license image is correct, verifying whether the travel license included in the travel license image is counterfeit, verifying whether the travel license included in the travel license image is expired, and the like.
Specifically, the verification may be performed by using an image recognition technique, for example, all pieces of driving license information included in the driving license image are recognized based on the image recognition technique, including information such as "number plate number", "vehicle type", "owner", "address", "brand model", "engine number", "vehicle identification code", "registration date", and "certificate issuing date", and these pieces of information may be sent to the public security organization to verify whether the stored corresponding information is satisfied.
After the driving license image in the request is determined to be legal, the license plate number contained in the driving license image can be acquired from the driving license image based on an image recognition technology and is used as the license plate number to be bound.
S103: and determining at least one parking record containing the license plate number to be bound in the pre-acquired parking records containing the license plate number.
The server may obtain the parking records from one or more parking lot devices in advance, or may directly obtain the parking records from the local site when the parking records of one or more parking lots are locally stored. The parking records may be of at least one type, for example, parking records characterizing vehicle entry or parking records characterizing vehicle exit.
In addition, the parking record may include a license plate number. Among the parking records containing the license plate number, the parking record containing the license plate number to be bound acquired in the S102 can be determined. In other words, the parking record of the vehicle to which the license plate number to be bound belongs can be determined from the parking records acquired in advance.
In an alternative embodiment, a fixed number of parking records containing the license plate number to be bound may be determined, so as to facilitate the subsequent step S104 of determining whether the first preset quantification condition is satisfied. Specifically, all parking records containing the license plate number to be bound are determined in the pre-acquired parking records containing the license plate number, and a fixed number of parking records are further determined in all the determined parking records containing the license plate number to be bound.
More specifically, a fixed number of parking records with the parking time closest to the current time may be further determined from all the determined parking records containing the license plate number to be bound. Further, if the determined number of parking records containing the license plate number to be bound is less than a fixed number, the binding may be stopped.
According to the embodiment, the new actual driver of the vehicle can be bound based on the latest parking record conveniently under the condition that the actual driver of the vehicle changes.
S104: and if the parking records related to the user identification to be bound in the determined parking records meet a first preset quantification condition, binding the user identification to be bound and the license plate number to be bound.
Specifically, in the parking records determined in S103 and containing the license plate number to be bound, the number of the parking records associated with the user identifier to be bound is further determined, and whether the number meets the first preset quantification condition is determined.
In other words, it may be determined whether the parking record including the license plate number to be bound and associated with the user identifier to be bound satisfies the first preset quantification condition.
In an alternative embodiment, the parking record associated with the user identification is determined, in particular the parking record associated with the on-line payment record for the parking fee.
For the parking fee corresponding to the parking record of the parking lot, the actual driver of the vehicle may pay in cash or on-line in general. And the user identification used by the user for online payment can be saved in the payment record by using the online payment mode.
For example, if the user performs online payment through the payment application, the user account logged in the payment application may be used as the user identifier and stored in the payment record; and the user carries out online payment through an online bank, and the bank account can be used as the user identifier and stored in the payment record.
Therefore, by determining the parking record associated with the online payment record for the parking fee, the user identification contained in the online payment record can be further determined, thereby determining the parking record associated with the user identification.
And the first preset quantization condition may include: the ratio in the determined parking record is greater than a first preset ratio; and/or the number is greater than the first preset number. Under the condition that the first preset quantification condition is met, the user to be bound can be considered as an actual driver of the vehicle to which the license plate number to be bound belongs.
When specifically judging whether the parking records containing the license plate number to be bound and associated with the user identifier to be bound meet the first preset quantification condition, the number of the parking records containing the license plate number to be bound and associated with the user identifier to be bound can be determined, and then judgment is carried out based on different first preset quantification conditions.
In an alternative embodiment, the first preset quantization condition may be that the number is greater than a first preset number. Correspondingly, after determining the number of the parking records which contain the license plate number to be bound and are associated with the user identifier to be bound, whether the determined number is larger than a first preset number can be further judged.
In another alternative embodiment, the first preset quantifying condition may be that the occupancy in the determined parking record is greater than a first preset occupancy. Correspondingly, after determining the number of the parking records that include the license plate number to be bound and are associated with the user identifier to be bound, the occupancy may be calculated based on the determined number, specifically, the ratio between the determined number and the number of the parking records determined in S103 may be calculated, and it is further determined whether the calculated occupancy is greater than the first preset occupancy.
Based on the method flow, aiming at the user to be bound, the parking record containing the license plate number to be bound is additionally utilized for verification. If the parking records associated with the identifiers of the users to be bound in the parking records containing the license plates to be bound meet the preset quantitative conditions, the fact that the vehicles to which the license plates to be bound belong are frequently used by the users to be bound in the past can be shown, and the vehicles to which the license plates to be bound belong are actual drivers of the vehicles to which the license plates to be bound belong can be bound. By adding the verification step, whether the user to be bound is an actual driver of the vehicle to which the license plate number to be bound belongs is verified, so that the risk of privacy information leakage is reduced.
In addition, as shown in fig. 2, a flow chart of another user binding method provided in this specification is illustrated. The above process flow may also include additional steps. In the case that the parking record associated with the to-be-bound user identifier in the determined parking records in S103 does not satisfy the first preset quantification condition, the parking record including the specified time may be additionally utilized for further determination.
The parking record may further contain a designated time, which may include: an entry time point, an exit time point, or a parking period.
If the position of the user to be bound is within the range near the parking lot at the designated time, the user to be bound can be considered as an actual driver of the vehicle when the vehicle is parked at this time, and whether the user to be bound is bound or not is helped to be subsequently judged. On the contrary, if the vehicle is not within the range near the parking lot, it can be considered that the user to be bound is certainly not the actual driver of the vehicle at the time of the current parking.
For example, in a case where the specified time is the entry time point, the position of the user to be bound at the entry time point may be acquired, and it may be further determined whether the acquired position is within a range near the parking lot; alternatively, in the case where the specified time is a parking period, a plurality of positions of the user to be bound in the parking period may be acquired, and it may be further determined whether or not there is a position within a range near the parking lot.
The method may comprise at least the following steps.
S201: a user binding request is received.
S202: and obtaining the license plate number to be bound according to the driving license image in the request.
S203: and determining at least one parking record containing the license plate number to be bound in the pre-acquired parking records containing the license plate number.
S204: and judging whether the parking record associated with the user identifier to be bound in the determined parking records meets a first preset quantification condition.
If yes, go to S205; if not, S206 is performed.
S205: and binding the user identification to be bound and the license plate number to be bound.
S206: and if the determined parking records meeting the preset position condition simultaneously meet a second preset quantification condition, binding the user identification to be bound and the license plate number to be bound.
Wherein the preset position condition may include: the parking record comprises specified time, and at the specified time, the user position determined based on the user identification to be bound is within a preset range.
In an optional embodiment, the user position is determined based on the to-be-bound user identifier, specifically, the corresponding user account is determined based on the to-be-bound user identifier, and then the position of the terminal where the user account is logged in is obtained and determined as the position of the to-be-bound user.
And the preset range may include: and the distance between the parking lot position corresponding to the parking lot identifier contained in the parking record is smaller than the range of the preset threshold value.
Further, the second preset quantization condition may include: the ratio in the determined parking record is larger than a second preset ratio; and/or the number is greater than a second preset number. And under the condition of meeting the second preset quantification condition, the user to be bound can be considered as the actual driver of the vehicle to which the license plate number to be bound belongs.
In an optional embodiment, since the parking record including the license plate number to be bound and satisfying the preset position condition only indicates that the user to be bound may be an actual driver of the vehicle, the second preset proportion may be greater than the first preset proportion, and the second preset number may be greater than the first preset number, thereby further reducing the risk of privacy disclosure.
For further explanation of the process flow shown in fig. 2, reference may be made to the process flow shown in fig. 1.
Based on the method flow shown in fig. 2, the parking records containing the license plate numbers to be bound are additionally utilized to verify the users to be bound. If the parking records associated with the identifiers of the users to be bound in the parking records containing the license plates to be bound meet the first preset quantification condition, the fact that the vehicles to which the license plates to be bound belong are frequently used by the users to be bound in the past can be shown, and the users to be bound can be bound by the actual drivers of the vehicles to which the license plates to be bound belong. By adding the verification step, whether the user to be bound is an actual driver of the vehicle to which the license plate number to be bound belongs is verified, so that the risk of privacy information leakage is reduced.
If the parking record associated with the identifier of the user to be bound does not satisfy the first preset quantification condition in the parking record containing the license plate number to be bound, in the flow of the method shown in fig. 2, if the parking record satisfying the preset position condition in the parking record containing the license plate number to be bound satisfies the second preset quantification condition at the same time, it can be said that the user to be bound is often near the parking lot when the vehicle to which the license plate number to be bound belongs parks, and is more likely to be the actual driver of the vehicle to which the license plate number to be bound belongs, and can be bound. On the premise of reducing the risk of privacy information disclosure, the method can further facilitate user binding and improve user experience.
In addition, as shown in fig. 3, a flow chart of another user binding method provided in this specification is shown. The process flow shown in fig. 1 described above may also include additional steps. In the case that the parking record associated with the to-be-bound user identifier in the determined parking records in S103 does not satisfy the first preset quantification condition, the parking record including the specified time may be additionally utilized for further determination.
Based on the method flow shown in fig. 2, if the position of the user to be bound is within the range near the parking lot at the designated time, it may be considered that the user to be bound may be an actual driver of the vehicle when the vehicle is parked this time, and it is helpful to subsequently determine whether to bind.
Therefore, the subsequent determination may be performed by using "the parking record associated with the user identifier to be bound in the parking record determined in S103" and "the parking record satisfying the preset position condition in the parking record determined in S103" together.
Since there may be parking records that are associated with the to-be-bound user identifier and satisfy the preset position condition, for convenience of distinction and convenience of description, the parking records associated with the to-be-bound user identifier and the parking records that are not associated with the to-be-bound user identifier and satisfy the preset position condition are collectively referred to as target parking records.
Subsequent determinations may be made using the target parking record, and the method may include at least the following steps.
S301: a user binding request is received.
S302: and obtaining the license plate number to be bound according to the driving license image in the request.
S303: and determining at least one parking record containing the license plate number to be bound in the pre-acquired parking records containing the license plate number.
S304: and judging whether the parking record associated with the user identifier to be bound in the determined parking records meets a first preset quantification condition.
If yes, go to S305; if not, S306 is executed.
S305: and binding the user identification to be bound and the license plate number to be bound.
S306: and if the target parking record in the determined parking records meets a third preset quantification condition, binding the user identification to be bound and the license plate number to be bound.
The target parking record may include: the parking record is associated with the user identifier to be bound, and the parking record is not associated with the user identifier to be bound but meets the preset position condition.
For further explanation of the method sequence shown in fig. 3, reference may be made to the above-described method embodiments.
And the third preset quantization condition may include: the comprehensive weight value determined based on the target parking record is greater than or equal to a preset weight value.
The method for determining the comprehensive weight value may include: adding the product of the number of the parking records associated with the user identifier to be bound and the first weight value and the product of the number of the parking records which are not associated with the user identifier to be bound but meet the preset position condition and the second weight value; and determining a ratio between a sum of the two products and the determined number of parking records as a comprehensive weight value.
Since the parking record containing the license plate number to be bound and meeting the preset position condition can only represent that the user to be bound is probably the actual driver of the vehicle, and the parking record containing the ticket number to be bound and associated with the user identifier to be bound is more credible, the first weight value can be larger than the second weight value.
The specific judging step may include: initializing a weight sum, traversing all determined parking records, and if the current parking record is the parking record associated with the user identifier to be bound, accumulating the current weight sum by a first weight value; and if the current parking record is the parking record which is not associated with the user identifier to be bound but meets the preset position condition, the current weight and the accumulated second weight are obtained. And after traversing is finished, dividing the current weight sum by the number of all the determined parking records to obtain a comprehensive weight value.
If the parking record associated with the user identifier to be bound does not satisfy the first preset quantification condition in the parking record containing the license plate number to be bound, in the flow of the method shown in fig. 3, if the target parking record satisfies the third preset quantification condition in the parking record containing the license plate number to be bound, it can be said that the judgment of factors such as the associated user identifier of the user to be bound and the user position during parking is integrated, and the user to be bound is likely to be the actual driver of the vehicle to which the license plate number to be bound belongs, and can be bound. On the premise of reducing the risk of privacy information disclosure, the method can further facilitate user binding and improve user experience.
In addition, since the verification step is added to verify whether the user to be bound is the actual driver of the vehicle to which the license plate number to be bound belongs, the risk of privacy information disclosure can be reduced, and therefore based on the method flow shown in fig. 1, S104 can be replaced by other verification steps, and the risk of privacy information disclosure can also be reduced. For example, the parking records satisfying the preset position condition among the determined parking records simultaneously satisfy the second preset quantitative condition, or the target parking record among the determined parking records satisfies the third preset quantitative condition.
Fig. 4 is a schematic flow chart of another user binding method provided in this specification. The method can be applied to a server and at least comprises the following steps.
S401: a user binding request is received.
S402: and obtaining the license plate number to be bound according to the driving license image.
S403: and determining at least one parking record containing the license plate number to be bound in the pre-acquired parking records containing the license plate number.
S404: and if the target parking record in the determined parking records meets a third preset quantification condition, binding the user identification to be bound and the license plate number to be bound.
For a detailed explanation of the method sequence shown in fig. 4, reference may be made to the above-described method embodiments.
Based on the method flow shown in fig. 4, the parking records containing the license plate numbers to be bound are additionally utilized for verification aiming at the users to be bound. If the target parking record meets the preset quantitative condition in the parking records containing the license plate number to be bound, the judgment of factors such as the associated user identification of the user to be bound, the position of the user during parking and the like can be explained, and the user to be bound is likely to be the actual driver of the vehicle to which the license plate number to be bound belongs and can be bound. By adding the verification step, whether the user to be bound is an actual driver of the vehicle to which the license plate number to be bound belongs is verified, so that the risk of privacy information leakage is reduced.
Another corresponding method flow for verifying whether the parking records meeting the preset position condition in the determined parking records simultaneously meet the second preset quantification condition may be obtained, and is not described herein again.
For the convenience of understanding, the specification also provides an application method embodiment. Wherein the user identification is a user account of the payment application. The method may comprise at least the following steps.
S501: a user binding request is received. The request carries the license plate number to be bound and the user account number to be bound. The user account may be an account on a payment application.
S502: and obtaining the license plate number to be bound according to the driving license image carried in the request.
S503: and determining at least one parking record containing the license plate number to be bound in the pre-acquired parking records containing the license plate number.
S504: and if the number of the parking records of the user account carried in the association request in the determined parking records is larger than a first preset number, binding the user account and the license plate number to be bound.
Specifically, the user pays a parking fee through the user account on the payment application, so as to generate a parking record associated with a payment record containing the user account, that is, a parking record associated with the user account.
On the basis of the method flow shown in any one of fig. 1 to 4, the present specification further provides a notification sending method, and as shown in fig. 5, a flow diagram of a notification sending method provided by the present specification is provided. The method can be applied to a server, and the server can pre-store the binding relationship between the user identification and the license plate number. The method may comprise at least the following steps.
S601: and receiving the license plate number to be notified and the notification to be transmitted sent from the parking lot equipment.
The parking lot device can obtain the license plate number based on the image recognition technology according to the image shot by the camera device when the vehicle enters or leaves, and further generate the corresponding notice. Specifically, the vehicle may be an entrance notice, an exit notice, or a parking fee payment notice.
S602: and if the binding relationship contains the license plate number to be notified, transmitting the notification to be transmitted to the target terminal.
If the pre-stored binding relationship of the server side contains the license plate number to be notified, the fact that the license plate number to be notified is bound by the user is indicated, and a notification needs to be sent.
The target terminal may specifically be a terminal determined based on the user identifier bound to the license plate number to be notified.
In an alternative embodiment, the target terminal may be a terminal that logs in a user account to which the license plate number to be notified is bound.
In another optional embodiment, the corresponding user account may be determined based on a user identifier (an identity card number, etc.) bound to the license plate number to be notified, and then the terminal logged in with the user account may be determined as the target terminal.
Before the notification is sent to the target terminal, in order to further reduce the risk of privacy disclosure, the user identifier bound to the license plate number to be notified may be verified again, and if the user identifier passes the verification, the notification to be sent may be sent to the target terminal. On the contrary, if the user identifier is not verified, the notification to be sent is not sent to the target terminal, so that the risk of privacy disclosure is reduced.
In the case where the actual driver of the vehicle is changed, the verification process before the notification is transmitted can make it difficult for the new actual driver's whereabouts information to be transmitted to the terminal of the old actual driver, reducing the risk of privacy leakage.
Wherein, the verification can be carried out before the notification needs to be sent each time; or verification is required before sending the notification again at fixed time intervals; after the notification is sent a preset number of times, verification may be required before the notification is sent again.
The specific verification process may refer to the method flow shown in any one of fig. 1-4, for example, S103-S104, S203-S206, S303-S306, or S403-S404.
It should be noted that the method flow is based on the method flow shown in any one of fig. 1 to 4, and therefore, the verification process before the specific binding relationship is stored may refer to the method flow shown in any one of fig. 1 to 4, and the subsequent specific verification process may be the same as or different from the verification process before the binding relationship is stored.
In an alternative embodiment, the specific verification process may include: determining at least one parking record containing the license plate number to be notified in the pre-acquired parking records containing the license plate number; if the parking records associated with the user identification bound with the license plate number to be notified in the determined parking records meet the first preset quantification condition, the verification is passed.
Other verification processes may be obtained correspondingly, and are not described herein again.
Based on the method flow shown in fig. 5, before sending the notification, the user identifier is further verified, so that the risk of privacy disclosure can be further reduced.
In addition to the method embodiments described above, the present specification also provides corresponding apparatus embodiments.
Fig. 6 is a schematic structural diagram of a user binding apparatus provided in this specification. The device can be applied to a server, and at least comprises the following units.
The first request receiving unit 701: for receiving a user binding request. The request can carry the driving license image and the user identification to be bound.
First license plate number acquisition unit 702: and the license plate number binding device is used for obtaining the license plate number to be bound according to the driving license image.
The first determination unit 703: the method is used for determining at least one parking record containing the license plate number to be bound in the pre-acquired parking records containing the license plate number.
The first binding unit 704: and if the parking record associated with the user identifier to be bound in the determined parking record meets a first preset quantification condition, binding the user identifier to be bound and the license plate number to be bound.
Wherein, the first binding unit 704 is further configured to: and if the parking records related to the user identifier to be bound in the determined parking records do not meet a first preset quantification condition, and the parking records meeting a preset position condition in the determined parking records simultaneously meet a second preset quantification condition, binding the user identifier to be bound and the license plate number to be bound.
The first binding unit 704 may also be configured to: and if the parking record associated with the user identifier to be bound in the determined parking record does not meet the first preset quantification condition and the target parking record in the determined parking record meets the third preset quantification condition, binding the user identifier to be bound and the license plate number to be bound. The target parking record may include: the parking record is associated with the user identifier to be bound, and the parking record is not associated with the user identifier to be bound but meets the preset position condition.
The preset position condition may include: the parking record comprises specified time, and at the specified time, the user position determined based on the user identification to be bound is within a preset range. The preset range may include: the distance between the parking lot location corresponding to the parking lot identifier included in the parking record is smaller than the range of the preset distance.
For further explanation of the above-described device embodiments reference may be made to the above-described method embodiments.
Fig. 7 is a schematic structural diagram of another user binding apparatus provided in this specification. The device can be applied to a server, and at least comprises the following units.
The second request receiving unit 801: for receiving a user binding request. The request can carry the driving license image and the user identification to be bound.
The second license plate number obtaining unit 802: and the license plate number binding device is used for obtaining the license plate number to be bound according to the driving license image.
The second determination unit 803: the method is used for determining at least one parking record containing the license plate number to be bound in the pre-acquired parking records containing the license plate number.
The second binding unit 804: and the system is used for binding the user identification to be bound and the license plate number to be bound if the target parking record in the determined parking records meets a third preset quantification condition. The target parking record may include: the parking record is associated with the user identifier to be bound, and the parking record is not associated with the user identifier to be bound but meets the preset position condition.
For further explanation of the above-described device embodiments reference may be made to the above-described method embodiments.
Fig. 8 is a schematic structural diagram of a notification transmission device provided in this specification. The device can be applied to a server, and at least comprises the following units.
Notification reception section 901: the system is used for receiving the license plate number to be notified and the notification to be transmitted sent from the parking lot equipment.
Notification transmission section 902: and the system is used for sending the notice to be sent to the target terminal if the binding relationship contains the license plate number to be notified. The target terminal may be a terminal determined based on the user identity to which the license plate number to be notified is bound.
For further explanation of the above-described device embodiments reference may be made to the above-described method embodiments.
Embodiments of the present specification also provide a computer device, which at least includes a memory, a processor and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement a user binding method as shown in any one of fig. 1-4.
Fig. 9 is a schematic diagram illustrating a more specific hardware structure of a computer device according to an embodiment of the present disclosure, where the computer device may include: a processor 1010, a memory 1020, an input/output interface 1030, a communication interface 1040, and a bus 1050. Wherein the processor 1010, memory 1020, input/output interface 1030, and communication interface 1040 are communicatively coupled to each other within the device via bus 1050.
The processor 1010 may be implemented by a general-purpose CPU (Central Processing Unit), a microprocessor, an Application Specific Integrated Circuit (ASIC), or one or more Integrated circuits, and is configured to execute related programs to implement the technical solutions provided in the embodiments of the present disclosure.
The Memory 1020 may be implemented in the form of a ROM (Read Only Memory), a RAM (Random Access Memory), a static storage device, a dynamic storage device, or the like. The memory 1020 may store an operating system and other application programs, and when the technical solution provided by the embodiments of the present specification is implemented by software or firmware, the relevant program codes are stored in the memory 1020 and called to be executed by the processor 1010.
The input/output interface 1030 is used for connecting an input/output module to input and output information. The i/o module may be configured as a component in a device (not shown) or may be external to the device to provide a corresponding function. The input devices may include a keyboard, a mouse, a touch screen, a microphone, various sensors, etc., and the output devices may include a display, a speaker, a vibrator, an indicator light, etc.
The communication interface 1040 is used for connecting a communication module (not shown in the drawings) to implement communication interaction between the present apparatus and other apparatuses. The communication module can realize communication in a wired mode (such as USB, network cable and the like) and also can realize communication in a wireless mode (such as mobile network, WIFI, Bluetooth and the like).
It should be noted that although the above-mentioned device only shows the processor 1010, the memory 1020, the input/output interface 1030, the communication interface 1040 and the bus 1050, in a specific implementation, the device may also include other components necessary for normal operation. In addition, those skilled in the art will appreciate that the above-described apparatus may also include only those components necessary to implement the embodiments of the present description, and not necessarily all of the components shown in the figures.
Embodiments of the present specification also provide a computer-readable storage medium, on which a computer program is stored, which when executed by a processor implements a user binding method as shown in any one of fig. 1-4.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, 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 disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
From the above description of the embodiments, it is clear to those skilled in the art that the embodiments of the present disclosure can be implemented by software plus necessary general hardware platform. Based on such understanding, the technical solutions of the embodiments of the present specification may be essentially or partially implemented in the form of a software product, which may be stored in a storage medium, such as a ROM/RAM, a magnetic disk, an optical disk, etc., and includes several instructions for enabling a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the methods described in the embodiments or some parts of the embodiments of the present specification.
The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. A typical implementation device is a computer, which may take the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email messaging device, game console, tablet computer, wearable device, or a combination of any of these devices.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the apparatus embodiment, since it is substantially similar to the method embodiment, it is relatively simple to describe, and reference may be made to some descriptions of the method embodiment for relevant points. The above-described apparatus embodiments are merely illustrative, and the modules described as separate components may or may not be physically separate, and the functions of the modules may be implemented in one or more software and/or hardware when implementing the embodiments of the present disclosure. And part or all of the modules can be selected according to actual needs to achieve the purpose of the scheme of the embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.
The foregoing is only a detailed description of the embodiments of the present disclosure, and it should be noted that, for those skilled in the art, many modifications and decorations can be made without departing from the principle of the embodiments of the present disclosure, and these modifications and decorations should also be regarded as protection for the embodiments of the present disclosure.
Claims (14)
1. A user binding method is applied to a server and comprises the following steps:
receiving a user binding request, wherein the request carries a driving license image and a user identifier to be bound;
obtaining a license plate number to be bound according to the driving license image;
determining at least one parking record containing the license plate number to be bound in the pre-acquired parking records containing the license plate number;
and if the parking record associated with the to-be-bound user identifier in the determined parking record meets a first preset quantification condition, binding the to-be-bound user identifier and the to-be-bound license plate number.
2. The method of claim 1, further comprising:
and if the parking records related to the user identifier to be bound in the determined parking records do not meet a first preset quantification condition, and the parking records meeting a preset position condition in the determined parking records simultaneously meet a second preset quantification condition, binding the user identifier to be bound and the license plate number to be bound.
3. The method of claim 1, further comprising:
if the parking record associated with the to-be-bound user identifier in the determined parking record does not meet a first preset quantification condition and the target parking record in the determined parking record meets a third preset quantification condition, binding the to-be-bound user identifier and the to-be-bound license plate number;
the target parking record includes: and the parking records are associated with the user identification to be bound and the parking records which are not associated with the user identification to be bound but meet the preset position condition.
4. The method of claim 3, the third preset quantization condition comprising: the comprehensive weight value determined based on the target parking record is greater than or equal to a preset weight value;
the method for determining the comprehensive weight value comprises the following steps:
adding the product of the number of the parking records associated with the to-be-bound user identifier and a first weight value and the product of the number of the parking records which are not associated with the to-be-bound user identifier but meet a preset position condition and a second weight value;
the ratio between the sum of the two products and the determined number of parking records is determined as a composite weight value.
5. The method according to any one of claims 2-4, the preset position condition comprising: the parking record comprises appointed time, and the user position determined based on the user identification to be bound is within a preset range at the appointed time.
6. The method of claim 5, the preset range comprising: the distance between the parking lot location corresponding to the parking lot identifier included in the parking record is smaller than the range of the preset distance.
7. A user binding method is applied to a server and comprises the following steps:
receiving a user binding request, wherein the request carries a driving license image and a user identifier to be bound;
obtaining a license plate number to be bound according to the driving license image;
determining at least one parking record containing the license plate number to be bound in the pre-acquired parking records containing the license plate number;
if the target parking record in the determined parking records meets a third preset quantification condition, binding the user identification to be bound and the license plate number to be bound;
the target parking record includes: and the parking records are associated with the user identification to be bound and the parking records which are not associated with the user identification to be bound but meet the preset position condition.
8. A notice sending method based on the method of claim 1 or 7 is applied to a server, wherein the server stores the binding relationship between a user identifier and a license plate number; the method comprises the following steps:
receiving a license plate number to be notified and a notification to be transmitted, which are transmitted by parking lot equipment;
if the binding relationship contains the license plate number to be notified, the notification to be transmitted is transmitted to a target terminal; and the target terminal is determined based on the user identification bound by the license plate number to be notified.
9. The method of claim 8, wherein the sending the notification to be sent to a target terminal comprises:
verifying the user identification bound to the license plate number to be notified;
and if the verification is passed, sending the notification to be sent to a target terminal.
10. The method of claim 9, the verifying comprising:
determining at least one parking record containing the license plate number to be notified in the pre-acquired parking records containing the license plate number;
if the parking records related to the user identification bound with the license plate number to be notified in the determined parking records meet a first preset quantification condition, the verification is passed.
11. A user binding device is applied to a server and comprises:
a first request receiving unit: the system comprises a server and a server, wherein the server is used for receiving a user binding request, and the request carries a driving license image and a user identifier to be bound;
a first license plate number acquisition unit: the license plate number binding device is used for obtaining a license plate number to be bound according to the driving license image;
a first determination unit: the system comprises a server and a server, wherein the server is used for determining at least one parking record containing a license plate number to be bound in the pre-acquired parking records containing the license plate number;
a first binding unit: and the system is used for binding the user identifier to be bound and the license plate number to be bound if the parking record associated with the user identifier to be bound in the determined parking records meets a first preset quantification condition.
12. A user binding device is applied to a server and comprises:
a second request receiving unit: the system comprises a server and a server, wherein the server is used for receiving a user binding request, and the request carries a driving license image and a user identifier to be bound;
a second license plate number acquisition unit: the license plate number binding device is used for obtaining a license plate number to be bound according to the driving license image;
a second determination unit: the system comprises a server and a server, wherein the server is used for determining at least one parking record containing a license plate number to be bound in the pre-acquired parking records containing the license plate number;
a second binding unit: the system comprises a user identifier to be bound and a license plate number to be bound, wherein the user identifier to be bound and the license plate number to be bound are bound if a target parking record in the determined parking records meets a third preset quantification condition; the target parking record includes: and the parking records are associated with the user identification to be bound and the parking records which are not associated with the user identification to be bound but meet the preset position condition.
13. A notification sending device based on the device of claim 11 or 12, applied to a server, where the server stores a binding relationship between a user identifier and a license plate number; the notification transmission device includes:
a notification receiving unit: the system comprises a receiving module, a judging module and a display module, wherein the receiving module is used for receiving a license plate number to be notified and a notification to be transmitted which are transmitted by parking lot equipment;
a notification transmission unit: the system comprises a target terminal and a server, wherein the target terminal is used for sending the notice to be sent to the target terminal if the binding relationship contains the license plate number to be notified; and the target terminal is determined based on the user identification bound by the license plate number to be notified.
14. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the method of any one of claims 1 to 10 when executing the program.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011437480.XA CN112562100B (en) | 2020-12-07 | 2020-12-07 | User binding method and device |
| CN202210388035.1A CN114677773A (en) | 2020-12-07 | 2020-12-07 | User binding method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011437480.XA CN112562100B (en) | 2020-12-07 | 2020-12-07 | User binding method and device |
Related Child Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210388035.1A Division CN114677773A (en) | 2020-12-07 | 2020-12-07 | User binding method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112562100A CN112562100A (en) | 2021-03-26 |
| CN112562100B true CN112562100B (en) | 2022-04-19 |
Family
ID=75060395
Family Applications (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210388035.1A Pending CN114677773A (en) | 2020-12-07 | 2020-12-07 | User binding method and device |
| CN202011437480.XA Active CN112562100B (en) | 2020-12-07 | 2020-12-07 | User binding method and device |
Family Applications Before (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210388035.1A Pending CN114677773A (en) | 2020-12-07 | 2020-12-07 | User binding method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (2) | CN114677773A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114677773A (en) * | 2020-12-07 | 2022-06-28 | 支付宝(杭州)信息技术有限公司 | User binding method and device |
Family Cites Families (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2002099681A (en) * | 2000-09-26 | 2002-04-05 | Mitsubishi Electric Corp | Vehicle registration system |
| US20120053998A1 (en) * | 2010-08-24 | 2012-03-01 | Liberty Plugins, Inc. | System and method for providing internet-based vehicle parking registration and reservation |
| US9460623B2 (en) * | 2010-11-22 | 2016-10-04 | International Business Machines Corporation | Parking management |
| CN104954322B (en) * | 2014-03-25 | 2019-10-22 | 腾讯科技（深圳）有限公司 | A kind of binding processing method of account, apparatus and system |
| CN104901933B (en) * | 2014-08-12 | 2016-08-17 | 腾讯科技（深圳）有限公司 | Current voucher distribution method, device, subscriber equipment, application server and system |
| KR101556947B1 (en) * | 2015-03-31 | 2015-10-06 | 파킹클라우드 주식회사 | Parking lot management method, parking lot managing server and parking lot managing system |
| CN107516345A (en) * | 2016-06-15 | 2017-12-26 | 西安艾润物联网技术服务有限责任公司 | Parking fee collective system method and apparatus |
| CN106204770A (en) * | 2016-07-04 | 2016-12-07 | 焦力波 | Fare Collection System is registered in a kind of parking lot automatically |
| CN107393027A (en) * | 2017-06-29 | 2017-11-24 | 台山市金讯互联网络科技有限公司 | A kind of parking lot intelligent parking method and system based on wechat platform |
| CN107590866A (en) * | 2017-08-08 | 2018-01-16 | 阿里巴巴集团控股有限公司 | parking charging method and device |
| CN108389275A (en) * | 2018-02-05 | 2018-08-10 | 杭州安芯科技有限公司 | Internet toll collection system based on handheld device positioning and Car license recognition |
| CN109615716A (en) * | 2018-10-11 | 2019-04-12 | 阿里巴巴集团控股有限公司 | Admission registration, appearance charging method and the device and electronic equipment of the vehicles |
| CN110674527B (en) * | 2019-08-19 | 2023-03-14 | 厦门路桥信息股份有限公司 | Privacy protection method, medium, equipment and device based on owner identity authentication |
| CN114677773A (en) * | 2020-12-07 | 2022-06-28 | 支付宝(杭州)信息技术有限公司 | User binding method and device |
-
2020
- 2020-12-07 CN CN202210388035.1A patent/CN114677773A/en active Pending
- 2020-12-07 CN CN202011437480.XA patent/CN112562100B/en active Active
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114677773A (en) * | 2020-12-07 | 2022-06-28 | 支付宝(杭州)信息技术有限公司 | User binding method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114677773A (en) | 2022-06-28 |
| CN112562100A (en) | 2021-03-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20230177887A1 (en) | Toll payment equipment | |
| US20150186991A1 (en) | Creditor alert when a vehicle enters an impound lot | |
| WO2016081436A1 (en) | Method and system for wireless payment for parking | |
| CN105407127A (en) | Method, apparatus, and system for free sharing of passenger tool resources | |
| CN110136431B (en) | Vehicle sharing method and device | |
| US20190026829A1 (en) | Trading system, provider terminal, user terminal, and node | |
| CN111524383A (en) | Unlicensed vehicle management method and related equipment | |
| CN111199461B (en) | Unmanned vehicle passenger carrying method based on blockchain and unmanned vehicle | |
| KR102430559B1 (en) | Apparatus and method for providing ict-based driver-specific evaluation analysis and reward plaform for two-wheeled vehicle driving | |
| KR102108833B1 (en) | Method, system and computer readable storage medium to manage shared vehicles | |
| CN112562100B (en) | User binding method and device | |
| CN110991837A (en) | Online taxi appointment transaction data processing method, device and system | |
| US11687947B2 (en) | Automatic connected vehicle enrollment | |
| CN110379167B (en) | Method and device for determining running path of vehicle in expressway | |
| CN111382883A (en) | Network appointment vehicle order-receiving authority control method, device and equipment | |
| KR102220268B1 (en) | Device for transmitting and receiving traffic accident information, method for managing traffic accident information and apparatus using the same | |
| CN115329917A (en) | Enhanced contactless vehicle codes | |
| TWI748218B (en) | Road toll collection method, system, device, electronic equipment and computer readable medium | |
| CN108765604B (en) | Shared automobile parking fee settlement method, system and storage medium | |
| CN110660139B (en) | Detection system, method and device for copying and using riding code and terminal equipment | |
| CN112912918B (en) | Method, system and computer readable storage medium for managing a shared vehicle | |
| CN111815327A (en) | Data true checking method and device and electronic equipment | |
| US20210312537A1 (en) | Car sharing system, server and computer readable recording medium | |
| TWI801892B (en) | Mechanical parking system and internet of vehicles interacting method | |
| CN115660763A (en) | Network appointment platform parking method, device, system, electronic equipment and medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| REG | Reference to a national code |
Ref country code: HK Ref legal event code: DE Ref document number: 40047873 Country of ref document: HK |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |