Parking right scheme intelligent recommendation method and system based on multi-dimensional user portrait

Abstract

The application discloses a parking right and interest scheme intelligent recommendation method and system based on a multi-dimensional user portrait, relates to the technical field of parking operation management, and comprises the following steps: collecting parking behavior events, right and interest related events and identity state events, recording event occurrence time and writing time, generating a parking behavior portrait atom according to a parking order number, identifying a post-right and interest backfill event which is written and changes the right and interest state after an order is closed, and constructing an order-right and interest backfill chain; identifying portrait misattribution according to a parking order, a license plate number, a right and interest subject, a right and interest voucher, a station number and a right and interest cancellation rule, and correcting the attribution; and screening and sorting parking right and interest schemes based on the corrected multi-dimensional user portrait. The application can avoid that right and interest records are wrongly attributed to a license plate default user portrait, and improve recommendation accuracy and cancellability.

Description

Technical Field

[0001] This invention relates to the field of parking operation and management technology, and in particular to a method and system for intelligent recommendation of parking rights schemes based on multi-dimensional user profiles. Background Technology

[0002] With the widespread adoption of smart parking systems in commercial complexes, parks, hospitals, office buildings, and urban public parking scenarios, parking management methods are gradually evolving from manual payment, paper payment slips, and single-exit payment to a multi-system collaborative model that includes license plate recognition, paperless billing, mobile payment, automatic deduction, membership rights verification, and consumption discounts. Parking behavior data is typically generated first in the form of license plate number, parking order, parking lot number, entry time, exit time, and billing amount, with the vehicle or parking order as the basic record object.

[0003] In actual parking benefit operations, parking benefits are not entirely generated by the parking management system alone, but are often interconnected with membership systems, consumption systems, invoice systems, payment systems, coupon systems, and manual verification systems. Taking commercial complexes as an example, users may need to provide their license plate number at checkout to accumulate the consumption amount, which can then be used to offset parking time after reaching a certain spending threshold. Alternatively, they may enjoy different free parking durations based on membership level, same-day invoice, or APP membership code. Some scenarios also require verification of the license plate number at the payment machine before leaving, with restrictions on the duration of discounts, the number of daily uses, or the maximum offset limit. These benefit rules indicate that parking benefit data typically exists in the form of member accounts, payment accounts, invoice numbers, coupon numbers, offset application numbers, and benefit verification status. The data source, identification, and writing time may differ from the parking order itself.

[0004] Existing parking benefit recommendations typically match benefits based on membership level, historical parking frequency, spending amount, coupon redemption records, or license plate parking history. This tends to assume a stable and consistent correspondence between license plate number, user account, payment account, and benefit user. However, smart parking platforms face multi-channel, multi-business, and cross-platform data access requirements in actual construction. Different parking systems may also have issues such as inconsistent interfaces, platform incompatibility, and information silos. In this situation, parking orders may be entered into the database by license plate first, while member discounts, payment discounts, consumption invoices, coupon redemption, or supplementary discount records may only be asynchronously filled in after the order is closed. This can easily lead to a misalignment of the profile in the post-filled benefits under license plate anchoring. That is, the system incorrectly classifies the post-filled benefit usage records into the default user profile, historical user profile, or incorrect parking lot profile corresponding to the license plate, resulting in inconsistencies between the parking benefit recommendation results and the actual benefit user, current parking order, and redeemable conditions, thus affecting the accuracy of parking benefit recommendations. Summary of the Invention

[0005] The purpose of this invention is to address the shortcomings of existing technologies where parking behavior data is initially formed using license plates and parking orders, while parking rights data is subsequently asynchronously filled in using member accounts, payment accounts, invoice numbers, coupon numbers, or discount application numbers. This leads to misalignment of user profiles, incorrect merging of rights preferences, and inconsistencies between parking rights recommendations and the actual rights holders and redeemable conditions. The invention proposes an intelligent recommendation method and system for parking rights schemes based on multi-dimensional user profiles.

[0006] To address the problems existing in the prior art, the present invention adopts the following technical solution:

[0007] A smart recommendation method for parking benefits based on multi-dimensional user profiles includes:

[0008] S1. Collect parking behavior events, rights-related events, and identity status events that include parking order closing time, record the event occurrence time and event writing time for each event, and obtain a set of events with dual time stamps;

[0009] S2. Based on the parking behavior events in the dual-time-marked event set, generate parking behavior profile atoms with the parking order number as the main index, and set the profile ownership status;

[0010] S3. Perform atomic matching between the rights-related events and the parking behavior profile, identify subsequent rights-backfilling events whose writing time is later than the closing time of the corresponding parking order and which change the rights status of the corresponding parking order, and form an order-rights-backfilling chain.

[0011] S4. Based on the order-rights backfill chain, verify the consistency between parking order, license plate number, right subject determined by member account or payment account, right certificate determined by invoice number, coupon number or discount application number, station number and right redemption rules, and output profile misalignment marker and candidate right subject set;

[0012] S5. Based on the misalignment marker of the portrait and the set of candidate rights subjects, the affiliation of the parking behavior portrait atom is corrected to obtain the affiliation-corrected parking behavior portrait atom.

[0013] S6. Generate a multi-dimensional user profile based on the affiliation-corrected parking behavior profile.

[0014] S7. Based on the multi-dimensional user profile and the parking benefit scheme library, filter and sort the candidate parking benefit schemes, and output the parking benefit scheme recommendation results.

[0015] Preferably, the parking behavior events include parking order number, license plate number, parking lot number, entry time, exit time, parking duration, billing amount, order status, and parking order closing time; the rights-related events include member account, payment account, invoice number, coupon number, discount application number, rights type, rights amount, free parking duration, rights redemption status, and rights source system; the identity status events include the binding relationship between license plate and member account, the binding relationship between license plate and payment account, membership status, rights validity period, applicable parking lot, and applicable vehicle.

[0016] Preferably, the parking behavior profile atom includes parking order number, license plate number, parking lot number, entry time, exit time, parking duration, billing amount, order status, initial rights status, profile ownership status, and original ownership record; wherein, the profile ownership status includes suspended status, confirmed ownership status, and pending confirmation status, and the original ownership record is at least one of the license plate, member account, payment account, and parking lot ownership information recorded by the parking behavior profile atom before ownership correction; when no member account, payment account, invoice number, coupon number, or discount application number directly associated with the parking order is received when the parking order is generated, the profile ownership status of the parking behavior profile atom is set to suspended status.

[0017] Preferably, forming the order-equity backfill chain includes:

[0018] Match the rights-related events with the parking behavior profile atoms;

[0019] When the rights-related event is directly associated with the parking behavior profile atom through the parking order number, or is associated with the parking behavior profile atom through a combination of at least two types of information among the license plate number, station number, invoice number, member account, payment account, coupon number, and discount application number and verified by the rights verification rules, and the writing time of the rights-related event is later than the departure time or closing time of the corresponding parking order, and the rights-related event changes the rights status, discount amount, free parking duration, verification result, or rights subject of the corresponding parking order, the rights-related event is determined as a post-rights backfilling event;

[0020] Using the parking order number as the main index of the link, the parking behavior profile atoms are connected with the corresponding subsequent rights and interests backfilling events;

[0021] The order-rights backfill chain includes parking order number, license plate number, station number, subsequent rights backfill event, rights holder, rights certificate, and rights cancellation status; wherein, the rights certificate includes invoice number, coupon number, or discount application number.

[0022] Preferably, the consistency verification includes verifying the necessary relationships required by the rights and benefits redemption rules. The necessary relationships include whether the license plate number is consistent, whether the parking lot number is applicable, whether the member account is valid, whether the payment account is corresponding, whether the rights and benefits certificate is valid, whether the vehicles applicable to the rights and benefits match, whether the applicable time period of the rights and benefits covers the current parking order, and whether the rights and benefits redemption rules allow the use of the current parking order.

[0023] Preferably, the image attribution misalignment marker is output when one of the following conditions occurs:

[0024] The member account or payment account corresponding to the post-rights refill event is inconsistent with the member account or payment account in the original attribution record;

[0025] The subsequent rights and interests refill event meets the rights and interests reimbursement rules of the current parking order but does not meet the account, qualification or binding relationship corresponding to the original ownership record;

[0026] The same parking order may correspond to multiple candidate beneficiaries and it is impossible to determine a unique owner based on the beneficiary write-off rules;

[0027] The subsequent rights backfilling event changes the rights status of the parking order, and the rights subject or applicable parking station corresponding to the subsequent rights backfilling event is inconsistent with the original attribution record;

[0028] The applicable site for the rights and interests corresponding to the post-rights backfilling event is inconsistent with the site ownership information in the original ownership record.

[0029] Preferably, the attribution correction of the parking behavior profile atoms includes:

[0030] When there is a subsequent rights-refilling event directly bound to the parking order number in the order-rights-refilling chain, and the member account, payment account, invoice number, coupon number or discount application number corresponding to the subsequent rights-refilling event meets the rights-refund rules of the parking order, the parking behavior profile is atomically attributed to the rights subject corresponding to the subsequent rights-refilling event.

[0031] When there is no direct binding relationship between parking order numbers, but only one candidate rights holder in the candidate rights holder set satisfies all the necessary relationships, the parking behavior profile is atomically assigned to that candidate rights holder;

[0032] When multiple candidate rights holders in the candidate rights holder set meet the necessary relationship and cannot be uniquely assigned, the attribution status of the parking behavior profile atom is set to pending confirmation, and the parking behavior profile atom is prohibited from participating in the recommendation of parking rights schemes that rely on personal historical parking behavior, historical rights usage records, or membership profiles for sorting.

[0033] When the post-rights backfilling event cannot form a valid binding relationship with the parking order, the parking behavior profile atom is kept in a suspended state and is prohibited from being incorporated into the personal user profile.

[0034] Preferably, the multi-dimensional user profile includes a parking frequency profile, a parking duration profile, a parking lot preference profile, a rights usage profile, a membership profile, a rights ownership stability profile, a license plate sharing risk profile, and a redeemable rights profile; wherein, the parking frequency profile is generated from the number of parking orders in the confirmed parking behavior profile atom, the parking duration profile is generated from the parking duration in the confirmed parking behavior profile atom, the parking lot preference profile is generated from the parking lot number and corresponding number of parking sessions in the confirmed parking behavior profile atom, and the rights usage profile is generated from the parking lot number and corresponding number of parking sessions in the confirmed parking behavior profile atom. The system generates the rights type, rights amount, free parking duration, and rights redemption status. The membership profile is generated from the membership status and rights validity period in the confirmed identity status event. The rights ownership stability profile is generated from the correspondence between parking orders, license plate numbers, member accounts, payment accounts, and rights certificates under the same rights holder. The license plate sharing risk profile is generated from different member accounts or different payment accounts associated with the same license plate in different parking orders. The redeemable rights profile is generated from the matching relationship between the current rights holder, current license plate, current parking station, current parking order, and rights redemption rules.

[0035] Preferably, the selection of candidate parking benefit schemes includes:

[0036] The parking benefits scheme database includes benefit scheme number, benefit type, applicable stations, applicable vehicles, applicable benefit subjects, validity period, free parking duration, discount rules, usage limit, payment channel limit, and redemption entry;

[0037] The parking rights scheme that simultaneously meets the following requirements is applicable to the parking lot corresponding to the current parking order, applicable to the license plate or rights holder corresponding to the current parking order, is within the validity period, meets the rights cancellation rules of the current parking order, does not conflict with the subsequent rights backfilling events that have been cancelled or are pending cancellation in the current parking order, and is recommended based on the parking behavior profile atom that has been confirmed to belong.

[0038] Candidate parking benefit schemes are ranked based on parking frequency profile, parking duration profile, parking station preference profile, benefit usage profile, membership profile, benefit ownership stability profile, license plate sharing risk profile, and redeemable benefit profile.

[0039] When the stability profile of the rights attribution indicates that the correspondence between the current parking order, license plate number, member account, payment account and rights certificate is unstable, or the license plate sharing risk profile indicates that the current license plate is associated with different member accounts or different payment accounts, or the corresponding parking behavior profile is in a pending confirmation state, only parking rights schemes that do not rely on personal historical parking behavior, historical rights usage records or membership profiles for sorting and meet the current parking order cancellation conditions will be output.

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

[0041] 1. This invention generates parking behavior profile atoms using parking order numbers as the primary index and sets these atoms to a suspended state before the ownership of rights is confirmed. This avoids the problem of premature solidification of user profiles caused by directly using license plate numbers as the sole basis for profile ownership. Since parking behavior events, rights-related events, and identity status events all record the event occurrence time and event writing time, this invention can identify subsequent rights backfilling events such as member discounts, payment discounts, consumption invoices, coupon redemption, or supplementary discounts that are written after the parking order is closed. By linking parking behavior with subsequent rights records through the order-rights backfilling chain, this invention solves the problems of missing profiles, delayed profiles, and unclear rights ownership caused by asynchronous backfilling of parking behavior by license plate number and rights records by account or voucher.

[0042] 2. This invention further identifies misalignments in the post-rights backfill profile based on the consistency between parking orders, license plate numbers, rights holders, rights certificates, parking lot numbers, and rights redemption rules. It then corrects the attribution of parking behavior profile atoms, ensuring that the confirmed attribution of these atoms is incorporated into the multi-dimensional user profile corresponding to the actual rights holder. Parking rights scheme recommendations no longer rely solely on license plate history records or static membership levels. Instead, they are based on attribution-corrected parking frequency profiles, parking duration profiles, parking lot preference profiles, rights usage profiles, membership profiles, rights attribution stability profiles, license plate sharing risk profiles, and redeemable rights profiles for filtering and sorting. This avoids incorrectly writing others' rights usage preferences into the default license plate user profile, improving the consistency between parking rights recommendation results and the actual rights holder, current parking orders, and rights redemption conditions. This enhances the accuracy, usability, and interpretability of parking rights recommendations. Attached Figure Description

[0043] The accompanying drawings, which are included to provide a further understanding of the invention and form part of this application, illustrate exemplary embodiments of the invention and, together with their description, serve to explain the invention and do not constitute an undue limitation thereof. In the drawings:

[0044] Figure 1This is a flowchart illustrating an intelligent recommendation method for parking rights schemes based on multi-dimensional user profiles, provided in an embodiment of the present invention. Detailed Implementation

[0045] The technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments.

[0046] Example 1: As Figure 1 As shown in the figure, this embodiment provides an intelligent recommendation method for parking benefits based on multi-dimensional user profiles, which can be applied to commercial complexes, park parking lots, hospital parking lots, office building parking lots, public parking lots, or cross-station parking operation platforms; the parking benefits include one or more of the following: free parking time, parking discounts, parking benefits with consumption discounts, membership parking benefits, coupon parking benefits, payment channel parking benefits, monthly card recommendation benefits, single-use card recommendation benefits, and general parking benefits for parking stations;

[0047] The core of this embodiment is that it does not directly use the license plate number as the sole basis for user profile attribution. Instead, after a parking order is formed, it first generates a parking behavior profile atom using the parking order number as the main index. When membership, payment, invoice, coupon or discount application and other rights information are subsequently filled in, the subsequent rights filling event is identified. Based on the consistency between parking order, license plate number, rights subject, rights certificate, station number and rights redemption rules, the attribution of the parking behavior profile atom is corrected. Finally, parking rights schemes are recommended based on the multi-dimensional user profile after attribution correction.

[0048] In this embodiment, the rights holder is the parking rights user determined by the member account or payment account; the rights certificate is rights proof data determined by the invoice number, coupon number, or discount application number; the original attribution record is at least one of the license plate, member account, payment account, and parking lot attribution information recorded by the parking behavior profile atom before attribution correction; the parking behavior profile atom with confirmed attribution refers to a parking behavior profile atom that has been directly bound by the parking order number, or can be uniquely attributed to a certain rights holder after consistency verification between the license plate number, parking lot number, rights holder, rights certificate, and rights verification rules;

[0049] In this embodiment, if a parking behavior profile atom is in a suspended or pending confirmation state, then the parking behavior profile atom will not participate in the recommendation of parking rights schemes that rely on personal historical parking behavior, historical rights usage records, or membership profiles for sorting; if a parking behavior profile atom is in a confirmed ownership state, then the parking behavior profile atom can be used to generate a multi-dimensional user profile of the corresponding rights subject and serve as the basis for recommending parking rights schemes.

[0050] Specifically, it includes the following steps;

[0051] S1. Collect parking behavior events, rights and interests related events, and identity status events to generate a set of events with dual time stamps;

[0052] In this embodiment, the intelligent recommendation system for parking benefits schemes collects data from the parking management system, license plate recognition system, order billing system, membership system, payment system, consumption system, coupon system, and benefits verification system to form parking behavior events, benefits-related events, and identity status events.

[0053] The parking behavior event is used to describe a vehicle parking behavior, and includes at least the parking order number, license plate number, parking lot number, entry time, exit time, parking duration, billing amount, order status, and parking order closing time. The parking order number uniquely identifies a parking order; the license plate number identifies the vehicle entering the parking lot or parking space; the parking lot number identifies the parking lot where the parking order occurred; the entry and exit times determine the parking area; the parking duration is determined by the entry and exit times; the billing amount is the amount due or received in the billing system; the order status indicates whether the parking order is in progress, has been exited, has been paid, has been closed, or is in an abnormal state; and the parking order closing time indicates the time when the parking order is settled or closed in the parking system.

[0054] The rights-related events are used to describe the accounts, vouchers, and redemption information related to parking rights, including at least the member account, payment account, invoice number, coupon number, discount application number, rights type, rights amount, free parking duration, rights redemption status, and rights source system. Specifically, the member account identifies the rights holder in the member system; the payment account identifies the rights holder in the payment channel or payment account; the invoice number identifies the consumption voucher generated by the consumption system; the coupon number identifies the parking rights issued or redeemed by the coupon system; the discount application number identifies the business record of supplementary discount, manual review discount, or online application discount; the rights type indicates whether the rights belong to consumption discount, member free time, coupon deduction, payment channel discount, monthly card discount, single-use card discount, or general parking rights; the rights amount indicates the parking fee discount or deduction amount; the free parking duration indicates the parking time that can be deducted by the rights; the rights redemption status indicates whether the rights have been redeemed, are pending redemption, have failed redemption, or have been revoked; and the rights source system indicates whether the rights-related event originates from the member system, payment system, consumption system, coupon system, manual review system, or other rights system.

[0055] The identity status event is used to describe the status relationship between license plate, account, eligibility, and parking lot access, including at least the binding relationship between license plate and member account, the binding relationship between license plate and payment account, membership status, validity period of rights, applicable parking lots, and applicable vehicles. Specifically, the binding relationship between license plate and member account indicates whether a particular license plate is bound to a particular member account; the binding relationship between license plate and payment account indicates whether a particular license plate is bound to a particular payment account; the membership status indicates whether the member account is valid and whether the membership level meets the conditions for using rights; the validity period of rights indicates the start and end time of the right's usability; the applicable parking lots indicate the range of parking lots where the right can be used; and the applicable vehicles indicate whether the right is restricted to a specific license plate or vehicle.

[0056] For the aforementioned parking behavior events, rights-related events, and identity status events, the system records the event occurrence time and event writing time. The event occurrence time is the actual time when parking, leaving, consumption, payment, cancellation, application, or review occurs. The event writing time is the time when the event is written into the parking rights scheme intelligent recommendation system. By recording the event occurrence time and event writing time, the system can distinguish the order in which parking behaviors occur and the order in which data enters the recommendation system, thereby identifying situations where parking behaviors are entered into the database first and parking rights are filled in later.

[0057] S2. Generate parking behavior profile atoms using the parking order number as the primary index;

[0058] In this embodiment, when the system detects a new parking behavior event from the dual-time-marked event set, it generates a parking behavior profile atom with the parking order number as the main index. The parking behavior profile atom is a temporary profile carrier at the order level, used to temporarily store parking behavior data before the ownership of parking rights is confirmed, rather than directly merging the parking behavior event into the historical user profile corresponding to the license plate number.

[0059] The parking behavior profile includes the parking order number, license plate number, station number, entry time, exit time, parking duration, billing amount, order status, initial rights status, profile ownership status, and original ownership record.

[0060] The initial rights status indicates whether a verifiable rights redemption record already exists when the parking order is generated as an atomic parking behavior profile. If a membership benefit, payment discount, coupon redemption, or consumption discount record directly linked to the parking order already exists when the parking order is generated, the initial rights status is recorded as an existing rights record. If a verifiable rights record has not yet been received when the parking order is generated, the initial rights status is recorded as an unconfirmed rights record.

[0061] The status of the parking behavior profile includes a suspended status, a confirmed status, and a pending status. The suspended status indicates that the parking behavior profile has not yet been confirmed to belong to any rights holder. The confirmed status indicates that the parking behavior profile has been confirmed to belong to a rights holder determined by a member account or payment account. The pending status indicates that there are multiple candidate rights holders or conflicting identity relationships, and the unique ownership cannot be confirmed at the moment.

[0062] The original attribution record is at least one of the license plate, member account, payment account, and parking lot attribution information recorded by the parking behavior profile atom before attribution correction; the original attribution record comes from the license plate historical binding relationship, the last successful cancellation record, the parking lot default member collection rule, the payment account binding relationship, or the initial attribution record formed by the system when the parking order is generated.

[0063] When a parking order is generated but the member account, payment account, invoice number, coupon number, or discount application number directly associated with the parking order is not received, the system sets the image affiliation status of the parking behavior image atom to a suspended state and saves it only as an order-level image atom. At this time, the system does not directly write the parking behavior image atom into the personal user image corresponding to the license plate number to avoid incorrect image affiliation before the parking rights information arrives.

[0064] S3. Identify the subsequent rights and interests refill event and form an order-rights and interests refill chain;

[0065] In this embodiment, when the system receives a rights-related event, it matches the rights-related event with the parking behavior profile atom generated in step S2 to determine whether the rights-related event belongs to a subsequent rights-filling event.

[0066] The matching includes direct matching and combined matching;

[0067] Direct matching refers to establishing a direct association between a rights-related event and a parking behavior profile atom through the parking order number; for example, if a parking order number is explicitly included in a coupon redemption record, consumption discount record, or supplementary discount application record, the system will directly associate the rights-related event with the corresponding parking behavior profile atom.

[0068] Combination matching refers to the process where a rights-related event does not directly contain a parking order number, but can be associated with a parking behavior profile atomically by combining at least two types of information from the following categories: license plate number, parking lot number, invoice number, member account, payment account, coupon number, and discount application number, and after verification by the rights redemption rules. For example, if a consumption discount record contains a license plate number, parking lot number, member account, and invoice number, and the consumption time, consumption location, and applicable rights rules corresponding to the invoice number all meet the redemption conditions of the corresponding parking order, then the system will atomically associate the consumption discount record with the parking behavior profile.

[0069] When an equity-related event meets the following conditions, the system will identify it as a subsequent equity backfilling event:

[0070] First, the rights-related events can be directly linked to the parking behavior profile atom through the parking order number, or can be linked to the parking behavior profile atom through a combination of at least two types of information from the license plate number, station number, invoice number, member account, payment account, coupon number and discount application number, and after being verified by the rights and interests verification rules;

[0071] Second, the time when the rights-related event is written is later than the departure time or closing time of the corresponding parking order; that is, the rights-related event is written into the intelligent recommendation system for parking rights schemes only after the parking order has been left or closed.

[0072] Third, the rights-related event changes the rights status, discount amount, free parking duration, cancellation result, or rights holder of the corresponding parking order; the change in the rights status of the corresponding parking order means that the rights-related event makes the parking order with unused rights become the parking order with used rights, or makes the rights that were originally pending cancellation become the cancellation, or changes the rights holder of the parking order from the holder in the original attribution record to the rights holder corresponding to the subsequent rights backfill event.

[0073] In this embodiment, the following standard formula can be used to determine whether the rights-related event is written later than the parking order closing time:

[0074] ;

[0075] in, Indicates the event write time of the event related to the interests. This indicates the closing time of the corresponding parking order. This indicates the write delay of the equity-related event relative to the closing time of the corresponding parking order; when Furthermore, when the event related to the rights changes the rights status, discount amount, free parking duration, cancellation result, or rights holder of the corresponding parking order, the system will identify the event related to the rights as a subsequent rights backfilling event.

[0076] After identifying the subsequent benefit backfilling event, the system uses the parking order number as the main index of the link, connecting the parking behavior profile atoms with the corresponding subsequent benefit backfilling event to form an order-benefit backfilling chain. The order-benefit backfilling chain includes the parking order number, license plate number, parking lot number, subsequent benefit backfilling event, benefit subject, benefit certificate, and benefit redemption status. Among them, the benefit subject is determined by the member account or payment account; the benefit certificate is determined by the invoice number, coupon number, or discount application number; the benefit redemption status is used to indicate whether the benefit corresponding to the subsequent benefit backfilling event has been redeemed, is pending redemption, has failed redemption, or has been revoked.

[0077] S4. Identify misalignment of vehicle license plate anchoring profiles based on the order-rights backfilling chain;

[0078] In this embodiment, the system verifies the consistency between the parking order, license plate number, the rights holder determined by the member account or payment account, the rights certificate determined by the invoice number, coupon number or discount application number, the station number and the rights redemption rules for the order-rights backfill chain obtained in step S3, so as to identify whether there is a misalignment of the parking behavior profile atom;

[0079] The consistency verification includes verifying the necessary relationships required by the rights and benefits redemption rules; the necessary relationships include: whether the license plate number is consistent, whether the parking lot number is applicable, whether the member account is valid, whether the payment account is corresponding, whether the rights and benefits certificate is valid, whether the applicable vehicle for the rights and benefits matches, whether the applicable time period for the rights and benefits covers the current parking order, and whether the rights and benefits redemption rules allow the use of the current parking order;

[0080] In practice, the system determines the necessary relationships to be verified for each type of right based on the right verification rules in the parking rights scheme library or the rights verification system. For example, for parking rights that can be offset by consumption, the necessary relationships include parking lot number, invoice number, consumption time, license plate number, and member account; for parking rights that can be offset by coupons, the necessary relationships include coupon number, validity period, applicable parking lot, applicable vehicle, and right holder; for parking rights that can be offset by payment channels, the necessary relationships include payment account, payment channel, license plate number, parking lot number, and parking order number.

[0081] The system outputs a misalignment flag for the image attribution when one of the following conditions occurs:

[0082] First, the member account or payment account corresponding to the subsequent rights and benefits backfill event is inconsistent with the member account or payment account in the original attribution record; for example, when a parking order is generated, it is temporarily recorded as member account A based on the license plate history, but the consumption discount record in the subsequent rights and benefits backfill event corresponds to member account B, which poses a risk of misattribution of profile.

[0083] Second, the subsequent rights and benefits backfilling event meets the rights and benefits redemption rules of the current parking order, but does not meet the account, qualification or binding relationship corresponding to the original ownership record; for example, the coupon number in the subsequent rights and benefits backfilling event is applicable to the current parking order and the current license plate, but the member account in the original ownership record has expired or is not bound to the license plate, then there is a risk of misalignment of profile ownership;

[0084] Third, the same parking order may correspond to multiple candidate beneficiaries, and it is impossible to determine the unique ownership based on the beneficiary redemption rules. For example, if the same license plate is associated with multiple member accounts or multiple payment accounts around the same parking order, and multiple candidate beneficiaries meet some necessary relationships, there is a risk of misattribution of the profile.

[0085] Fourth, the subsequent rights backfilling event changes the rights status of the parking order, and the rights holder or applicable venue corresponding to the subsequent rights backfilling event is inconsistent with the original attribution record; for example, if the use of rights is not recorded when the parking order is closed, and the subsequent supplementary offsetting event identifies the rights holder as member account B, while the original attribution record is member account A, then there is a risk of misattribution of profile;

[0086] Fifth, the applicable station for the rights in the subsequent rights backfilling event is inconsistent with the station affiliation information in the original affiliation record; for example, the original affiliation record shows that the license plate mainly belongs to the user profile of station X, but the applicable station for the rights in the subsequent rights backfilling event is station Y, and the rights can only be cancelled at station Y, then there is a risk of station affiliation misalignment.

[0087] When the system outputs the misalignment marker for the portrait, it also outputs a set of candidate rights holders. The set of candidate rights holders includes the rights holders corresponding to member accounts or payment accounts that are associated with the parking behavior portrait atom and satisfy at least a partial necessary relationship. The set of candidate rights holders is directly used in step S5 to correct the portrait atom attribution.

[0088] When determining the set of candidate rights holders, the system forms candidate rights holders based on the member accounts and payment accounts in the order-rights backfilling chain, and verifies the necessary relationship between each candidate rights holder and the current parking order. If a candidate rights holder satisfies all the necessary relationships required by the rights redemption rules, the candidate rights holder is marked as a fully matched candidate rights holder; if a candidate rights holder only satisfies some of the necessary relationships, the candidate rights holder is marked as a partially matched candidate rights holder.

[0089] When there is only one fully matching candidate interest entity in the candidate interest entity set, the system will use that fully matching candidate interest entity as the target interest entity for subsequent attribution correction; when there are two or more fully matching candidate interest entities in the candidate interest entity set, or when there are two or more candidate interest entities that meet the necessary relationships of different categories but cannot establish a direct binding relationship between the parking order number and the parking behavior profile atom, the system will determine that the parking behavior profile atom cannot be uniquely attributed and set the profile attribution status of the parking behavior profile atom to the pending confirmation status; parking behavior profile atoms in the pending confirmation status will not be written into any personal user profile, but will only be saved as order-level records;

[0090] Through the above processing, the system can avoid incorrectly classifying subsequent rights and benefits refill events into a single historical user profile in scenarios where the same license plate is associated with multiple member accounts or multiple payment accounts.

[0091] S5. Correct the attribution of parking behavior image atoms with misattribution.

[0092] In this embodiment, the system corrects the attribution of the corresponding parking behavior image atoms based on the misattribution marker of the image and the set of candidate rights holders;

[0093] When there is a subsequent benefit-filling event directly linked to the parking order number in the order-benefit-filling chain, and the member account, payment account, invoice number, coupon number, or discount application number corresponding to the subsequent benefit-filling event meets the benefit-verification rules of the parking order, the system will atomically assign the parking behavior profile to the benefit subject corresponding to the subsequent benefit-filling event. For example, after a parking order is closed, if the system receives a supplementary discount application that explicitly contains the parking order number, and the member account, invoice number, and license plate number corresponding to the supplementary discount application all meet the verification rules, then the parking behavior profile will atomically assign the parking behavior profile to the benefit subject corresponding to the member account.

[0094] When there is no direct binding relationship between parking order numbers and the candidate rights holders, but only one candidate rights holder in the candidate rights holders set satisfies all the necessary relationships, the system will assign the parking behavior profile atom to that candidate rights holder. For example, if a rights-related event does not carry a parking order number, but its license plate number, station number, member account, invoice number, rights validity period, and applicable vehicle are all consistent with a certain parking behavior profile atom, and only that member account in the candidate rights holders set satisfies all the necessary relationships, then the parking behavior profile atom will be assigned to the rights holder corresponding to that member account.

[0095] When multiple candidate rights holders in the candidate rights holder set meet the necessary relationship and it is impossible to determine a unique affiliation, the system sets the affiliation status of the parking behavior profile atom to a pending confirmation state and prohibits the parking behavior profile atom from participating in the recommendation of parking rights schemes that rely on personal historical parking behavior, historical rights usage records, or membership profiles for sorting; this can avoid incorrectly writing parking behavior into a personal user profile when the rights holders are not unique.

[0096] When a post-event benefit refill event cannot be effectively bound to a parking order, the system maintains the temporary status of the parking behavior profile atom and prohibits the parking behavior profile atom from being incorporated into the personal user profile; the parking behavior profile atom can continue to be saved as an unconfirmed order-level record, but will not be used for personal benefit preference recommendations;

[0097] After the attribution correction is completed, the system updates the attribution status of the parking behavior profile atom; when the sole right holder is confirmed, the attribution status is set to confirmed attribution status; when the sole right holder cannot be determined, the attribution status is set to pending confirmation status; when the subsequent right backfilling event cannot be effectively bound to the parking order, the attribution status remains in the suspended status.

[0098] S6. Generate multi-dimensional user profiles from parking behavior profiles after attribution correction.

[0099] In this embodiment, the system generates multidimensional user profiles based on the parking behavior profile atoms after attribution correction; only parking behavior profile atoms with confirmed attribution status can be used to generate multidimensional user profiles that are sorted based on personal historical parking behavior, historical rights usage records, or membership profiles.

[0100] The multi-dimensional user profile includes parking frequency profile, parking duration profile, station preference profile, rights usage profile, membership profile, rights ownership stability profile, license plate sharing risk profile, and revocable rights profile;

[0101] The parking frequency profile is generated from the number of parking orders in the confirmed parking behavior profile atoms, and is used to represent the parking frequency of the rights holder at each station or time period.

[0102] The parking duration profile is generated from the parking duration in the parking behavior profile atoms that have been confirmed to belong to the rights holder, and is used to represent the short-term parking, long-term parking or stable parking tendency of the rights holder.

[0103] The parking lot preference profile is generated from the parking lot number and corresponding number of parking sessions in the confirmed parking behavior profile atom, and is used to represent the parking lot frequently used by the rights holder;

[0104] The rights usage profile is generated from the rights type, rights amount, free parking duration, and rights redemption status in the confirmed parking behavior profile atom. It is used to represent the rights holder's use of consumption discounts, free membership duration, coupon deductions, payment channel discounts, or general station rights.

[0105] The membership profile is generated from the membership status and rights validity period in the confirmed identity status event, and is used to indicate whether the rights holder is qualified to use specific membership rights;

[0106] The stability profile of ownership is generated atomically from the parking behavior profiles of the same ownership subject that have been confirmed. The system separately counts the set of license plate numbers, payment accounts, ownership certificate source systems and station numbers corresponding to the ownership subject, and compares the license plate number, payment account, ownership certificate source system and station number corresponding to the current parking order with the above sets respectively.

[0107] When the license plate number, payment account, source system of the rights certificate, and station number corresponding to the current parking order have all appeared in the confirmed ownership record of the rights holder, and there is no misalignment mark for the current parking order, the system determines that the current ownership relationship is stable; when any of the license plate number, payment account, source system of the rights certificate, or station number corresponding to the current parking order does not appear in the confirmed ownership record of the rights holder, or there is a misalignment mark for the current parking order, the system determines that the current ownership relationship is unstable.

[0108] The stability profile of the rights attribution is directly used in step S7 to determine whether to output parking rights schemes that rely on personal historical parking behavior, historical rights usage records, or membership profiles for sorting. When the rights attribution relationship is stable, the system allows the use of historical profiles with confirmed attribution to participate in the sorting of parking rights schemes. When the rights attribution relationship is unstable, the system does not use personal historical profiles to participate in the sorting and only outputs parking rights schemes that meet the current parking order cancellation conditions.

[0109] The license plate sharing risk profile is generated from the set of member accounts and payment accounts associated with the same license plate in the parking behavior profile atom with confirmed ownership; the system uses the license plate number as an index to count the number of member accounts and payment accounts associated with the license plate in different parking orders;

[0110] When the same license plate is associated with two or more different member accounts or two or more different payment accounts in different parking orders, the system determines that the license plate has a risk of being shared; when the same license plate is associated with only the same member account and only the same payment account in the parking behavior profile that has been confirmed to belong to the vehicle, the system determines that the license plate does not have a risk of being shared.

[0111] The license plate sharing risk profile is directly used in step S7 to determine whether to restrict parking rights schemes that rely on personal historical parking behavior, historical rights usage records, or membership profiles for ranking. When the current license plate has a license plate sharing risk, the system does not directly use the parking behavior corresponding to that license plate as a stable preference source for a single user profile. When the current license plate does not have a license plate sharing risk, the system allows the confirmed parking behavior profile atoms to be used for the profile generation and rights recommendation ranking of the corresponding rights subject.

[0112] The verifiable rights profile is generated by matching the current rights holder, current license plate, current parking station, current parking order, and rights verification rules. It is used to represent the types of rights and the scope of rights schemes that the current rights holder can actually use under the current parking order.

[0113] S7. Generate parking benefit scheme recommendation results based on multi-dimensional user profiles;

[0114] In this embodiment, based on the multi-dimensional user profile and the parking benefit scheme library, candidate parking benefit schemes are filtered and sorted, and parking benefit scheme recommendation results are output.

[0115] The parking benefits scheme database includes benefit scheme number, benefit type, applicable stations, applicable vehicles, applicable benefit subjects, validity period, free parking duration, discount rules, usage limit, payment channel limit, and redemption entry;

[0116] When the system filters candidate parking benefit schemes, it retains those that simultaneously meet the following conditions:

[0117] First, it applies to the parking lot corresponding to the current parking order; that is, the applicable parking lots for the benefit plan include the parking lot number of the current parking order.

[0118] Second, it applies to the license plate or rights holder corresponding to the current parking order; that is, the rights plan allows the current license plate to be used, or allows the rights holder identified by the current member account or payment account to use it.

[0119] Third, it must be within the validity period; that is, the parking time or the redemption time of the current parking order must fall within the validity period of the rights and benefits plan.

[0120] Fourth, the current parking order must meet the rights and interests redemption rules; that is, the current parking order, license plate number, rights holder, rights certificate, parking lot number, and redemption entry must all meet the redemption conditions stipulated in the rights and interests scheme.

[0121] Fifth, it does not conflict with subsequent benefit redemption events that have already been redeemed or are pending redemption in the current parking order; that is, if a parking benefit that cannot be stacked has already been used in the same parking order, then benefit schemes that conflict with that benefit will no longer be recommended.

[0122] Sixth, the recommendation is based on parking behavior profile atoms that have been confirmed to belong; that is, parking behavior profile atoms in the pending or unconfirmed state are not used as the basis for ranking based on personal historical profiles.

[0123] After selecting candidate parking benefit schemes, the system sorts them according to parking frequency profile, parking duration profile, parking lot preference profile, benefit usage profile, membership profile, benefit ownership stability profile, license plate sharing risk profile, and redeemable benefit profile.

[0124] When ranking candidate parking benefit schemes, the system uses deterministic ranking rules to generate recommended ranking results. Candidate parking benefit schemes that meet the current redeemable benefit profile are ranked before those that do not. Among candidate parking benefit schemes that all meet the current redeemable benefit profile, those with applicable parking lots matching the parking lot preference profile are ranked before those with inconsistent profiles. Among candidate parking benefit schemes with consistent applicable parking lots, those with benefit types matching the types of benefits already confirmed in the benefit usage profile are ranked before those with inconsistent benefit types. Under the same conditions, candidate parking benefit schemes with earlier expiration dates are ranked before those with later expiration dates.

[0125] When the ranking criteria for candidate parking benefit schemes come from the parking behavior profile atoms that have been confirmed to belong to them, the system outputs parking benefit schemes that are ranked based on the individual's historical parking behavior, historical benefit usage records, or membership profile. When the ranking criteria for candidate parking benefit schemes cannot be traced back to the parking behavior profile atoms that have been confirmed to belong to them, the system does not use the individual's historical profile to participate in the ranking, but only outputs the redeemable parking benefit schemes based on the parking lot, license plate, benefit subject, benefit certificate, and benefit redemption rules of the current parking order.

[0126] When the stability profile of rights ownership indicates that the correspondence between the current parking order, license plate number, member account, payment account and rights certificate is stable, and the license plate sharing risk profile indicates that the current license plate is not associated with different member accounts or different payment accounts, and the corresponding parking behavior profile atom is in the confirmed ownership state, the system can output a parking rights scheme that is sorted based on the individual's historical parking behavior, historical rights usage records or membership profile.

[0127] When the stability profile of rights ownership indicates that the correspondence between the current parking order, license plate number, member account, payment account and rights certificate is unstable, or the license plate sharing risk profile indicates that the current license plate is associated with different member accounts or different payment accounts, or the corresponding parking behavior profile is in a pending confirmation state, the system will only output parking rights schemes that do not rely on personal historical parking behavior, historical rights usage records or membership profiles for sorting and meet the current parking order cancellation conditions.

[0128] Output the recommended parking benefit scheme results; the recommended parking benefit scheme results include the recommended benefit scheme number, recommended benefit type, applicable station, applicable license plate or benefit subject, redeemable conditions, recommendation basis, whether there is subsequent benefit backfilling, whether it has been corrected by profile attribution, and recommendation ranking results.

[0129] Through the above steps, this embodiment can avoid incorrectly classifying the parking rights usage records backfilled after the fact into the default user profile, historical user profile, or incorrect parking lot profile corresponding to the license plate, so that the parking rights recommendation results are consistent with the real rights holder, the current parking order, and the rights can be redeemed.

[0130] Example 2: This example uses a parking lot in a commercial complex as an example to illustrate the specific application process of the present invention;

[0131] A commercial complex has a parking lot with the number P001. When a vehicle enters the parking lot, the license plate recognition system identifies the license plate number and the parking management system generates a parking order. The parking order includes the parking order number O001, license plate number V001, parking lot number P001, entry time, exit time, parking duration, billing amount, order status, and parking order closing time.

[0132] After the vehicle leaves and payment is completed, the parking order is closed. At this time, the system has not yet received the member account, payment account, invoice number, coupon number, or discount application number directly associated with parking order O001. Therefore, the system generates a parking behavior profile atom with parking order number O001 as the main index and sets the profile ownership status of this parking behavior profile atom to the suspended state. The system will not directly write this parking behavior profile atom into the historical user profile corresponding to license plate number V001.

[0133] After the vehicle leaves the parking lot, the user submits the consumption invoice at the service desk of the commercial complex or online platform to supplement the parking discount. The consumption system generates invoice number F001, the membership system records member account M002, and the supplementary discount system generates discount application number D001. After the review is approved, the system writes the benefit-related event to the parking benefit scheme intelligent recommendation system. The benefit-related event includes member account M002, invoice number F001, discount application number D001, benefit type as consumption discount, free parking time, benefit redemption status as redeemed, and the benefit source system as the supplementary discount system.

[0134] After receiving the benefit-related event, the system matches it with the parking behavior profile atom. Since the benefit-related event includes license plate number V001, parking lot number P001, member account M002, invoice number F001, and discount application number D001, and the above information can be verified by the benefit redemption rules to correspond to parking order O001, the system establishes an association between the benefit-related event and the parking behavior profile atom. Since the writing time of the benefit-related event is later than the parking order closing time of parking order O001, and the benefit-related event changes the benefit status of parking order O001 from unconfirmed benefit record to redeemed consumption discount benefit, the system identifies the benefit-related event as a post-benefit backfill event.

[0135] Using parking order number O001 as the main index of the chain, the parking behavior profile atoms are connected with the subsequent rights backfilling event to form an order-rights backfilling chain; the order-rights backfilling chain includes parking order number O001, license plate number V001, station number P001, subsequent rights backfilling event, rights subject M002, rights certificates F001 and D001, and rights cancellation status as cancelled.

[0136] Further, the system performs profile attribution misalignment identification. Assume the original attribution record shows license plate number V001 historically corresponding to member account M001, while the subsequent rights-based redemption event corresponds to member account M002. System verification reveals that member account M002's invoice number F001, redemption application number D001, license plate number V001, parking lot number P001, and applicable redemption period all meet the rights redemption rules for the current parking order O001. However, member account M001 in the original attribution record does not meet the account and voucher relationship for this consumption redemption right. Therefore, the system outputs a profile attribution misalignment flag and identifies member account M002 as a candidate rights holder in the candidate rights holder set.

[0137] Since there is a subsequent rights backfilling event in the order-rights backfilling chain that can be effectively bound to parking order O001, and the member account M002, invoice number F001 and discount application number D001 corresponding to the subsequent rights backfilling event all meet the rights reimbursement rules of the parking order, the system will atomically assign the parking behavior profile to the rights subject corresponding to member account M002 and set the profile ownership status to the confirmed ownership status.

[0138] After completing the attribution correction, the system atomically generates a multi-dimensional user profile based on the confirmed attribution parking behavior profile corresponding to member account M002; if member account M002 has multiple confirmed attribution parking orders at station P001 and uses consumption discount rights multiple times, the system records the usage of consumption discount rights in the rights usage profile, records the parking preference for station P001 in the station preference profile, and records the types of parking rights that can be used at the moment in the redeemable rights profile.

[0139] The system filters candidate parking benefit schemes based on multi-dimensional user profiles and a parking benefit scheme library. For example, the parking benefit scheme library includes parking discounts for spending a certain amount, free parking time for members, and parking vouchers for all parking lots. The system then determines whether each of these schemes applies to parking lot P001, license plate number V001 or member account M002, whether it is within the validity period, whether it meets the benefit redemption rules for the current parking order, whether it conflicts with the subsequent benefit backfilling event that has already been redeemed or is pending redemption, and whether the recommendation is based on the confirmed parking behavior profile atoms.

[0140] If the stability profile of the rights ownership of member account M002 shows that the correspondence between it and license plate number V001, payment account and rights certificate is stable, and the license plate sharing risk profile shows that license plate number V001 is not associated with different member accounts or different payment accounts, then the system can sort the candidate parking rights schemes according to the parking frequency profile, parking duration profile, station preference profile, rights usage profile, membership profile and redeemable rights profile, and output the recommended parking rights scheme suitable for member account M002.

[0141] If the system finds that license plate number V001 is associated with two or more different member accounts or two or more different payment accounts, the license plate sharing risk profile indicates that the license plate is at risk of being shared. In this case, even if parking order O001 has a subsequent rights backfill event, the system will not use the parking behavior profile to participate in the recommendation of parking rights schemes that rely on personal historical parking behavior, historical rights usage records or membership profiles for sorting. Instead, it will only output parking rights schemes that meet the current parking order redemption conditions and do not rely on personal historical profile sorting.

[0142] Without performing the attribution correction process of this invention, the consumption discount rights corresponding to parking order O001 will be directly merged into the member account M001 historically associated with license plate number V001 by default. This will cause the system to identify member account M001 as a user with a preference for consumption discount parking rights in subsequent recommendations, and may recommend consumption discount parking rights to member account M001. Since the actual rights subject corresponding to this subsequent rights backfilling event is member account M002, the above processing will cause M002's rights usage preferences to be incorrectly written into M001's user profile.

[0143] After performing the attribution correction process of this invention, the system confirms that parking order O001, license plate number V001, member account M002, invoice number F001, discount application number D001, and station number P001 meet the rights verification rules according to the order-rights backfilling chain, and atomically assigns the parking behavior profile to the rights subject corresponding to member account M002; thus, in subsequent recommendations, the system only recommends consumption discount parking rights based on the confirmed attribution profile of member account M002, and will not write the consumption discount rights into the user profile of member account M001; through the difference in processing before and after attribution correction, it can be directly demonstrated that this invention can avoid misalignment of the subsequent rights backfilling profile under license plate anchoring and improve the consistency between the parking rights recommendation results and the real rights subject;

[0144] As can be seen from the above embodiments, the present invention can identify and correct misalignment of the profile in scenarios where parking orders are generated first by the license plate and the rights information is then filled in by the member account and invoice voucher, thus avoiding the incorrect classification of the parking rights actually used by member account M002 into the profile corresponding to the default account M001 in the license plate history.

[0145] Example 3: This example uses a cross-station parking operation platform as an example for illustration;

[0146] The cross-site parking operation platform manages multiple parking lots. Different parking lots may be connected to different license plate recognition systems, membership systems, payment systems, and coupon systems. Users may use the same license plate at different parking lots, or they may use different membership accounts or payment accounts at different parking lots.

[0147] When a vehicle parks at the first parking lot P101, the parking management system generates a parking order O101, generates a parking behavior profile, and sets it to a suspended state if there is no direct interest-related event. When the user completes the parking fee payment through the payment platform, the payment system generates an interest-related event, which includes the payment account A101, coupon number C101, license plate number V101, and parking lot number P101.

[0148] The user parks again at the second parking lot P102, and the parking management system generates parking order O102, with the license plate number still being V101. If the membership system at the second parking lot refills the membership benefits record after the parking order is closed, the benefit-related event includes member account M102, coupon number C102, license plate number V101, and parking lot number P102. The system recognizes that the writing time of this benefit-related event is later than the parking order closing time of parking order O102, and that this benefit-related event changes the benefit status of parking order O102. Therefore, it is identified as a post-refill benefit event.

[0149] The system creates order-benefit backfill chains for parking orders O101 and O102 respectively, and verifies the consistency between license plate number, beneficiary, beneficiary certificate, parking lot number, and beneficiary redemption rules. For parking order O101, the system determines that payment account A101, coupon number C101, and parking lot number P101 meet the beneficiary redemption rules for parking order O101, and then assigns the parking behavior profile to the beneficiary corresponding to payment account A101. For parking order O102, the system determines that member account M102, coupon number C102, and parking lot number P102 meet the beneficiary redemption rules for parking order O102, and then assigns the parking behavior profile to the beneficiary corresponding to member account M102.

[0150] Since the same license plate number V101 is associated with different stakeholders in different parking orders, the system marks the license plate sharing risk profile as having a risk of license plate sharing when generating multi-dimensional user profiles; for parking orders O101 and O102, the system retains the parking behavior profile atoms after attribution correction, and does not directly merge them into a single user profile based on license plate number V101.

[0151] When recommending parking benefits in the future, if the beneficiary associated with the current parking order can be uniquely identified, and the correspondence between the current parking order, license plate number, beneficiary, benefit certificate, and parking lot number is stable, the system can make recommendations based on the confirmed attribution profile of the beneficiary. If the current parking order can only identify the license plate number V101, but cannot uniquely identify the member account or payment account, the system will not output parking benefit schemes that rely on personal historical parking behavior, historical benefit usage records, or member qualification profiles for sorting, but will only output parking benefit schemes that meet the current parking order redemption conditions.

[0152] In cross-site scenarios, if the system only summarizes parking behavior based on license plate number V101, the rights record of payment account A101 corresponding to parking order O101 and the rights record of member account M102 corresponding to parking order O102 will be merged into the same license plate profile, making it impossible for the system to distinguish the real rights holders corresponding to payment account A101 and member account M102 respectively. After adopting the present invention, the system generates parking behavior profile atoms with parking order O101 and parking order O102 as the main index, and determines the corresponding rights holders of each through the order-rights backfill chain, so that parking order O101 belongs to the rights holder corresponding to payment account A101, and parking order O102 belongs to the rights holder corresponding to member account M102.

[0153] When a new parking order appears that can only identify license plate number V101 but cannot confirm the rights holder, the system identifies the license plate as having a sharing risk profile. Instead of using the license plate's historical profile to directly generate parking rights recommendations based on personal historical preferences, the system only outputs parking rights schemes that meet the current parking order's redemption conditions. This process can prevent cross-site and cross-account rights records from being mistakenly merged into a single user preference.

[0154] Through this embodiment, the present invention can handle the problem of misattribution of vehicle profiles when the same license plate is used across different parking stations, accounts, and rights systems, and avoids the incorrect merging of parking behaviors and rights preferences of different rights holders.

[0155] Example 4: This example provides an intelligent recommendation system for parking benefits based on multi-dimensional user profiles; the system can be deployed on a parking operation platform server, a commercial complex membership operation platform server, a park parking management server, or a cloud-based parking benefits recommendation server; the system includes an event acquisition module, a profile atomic generation module, a post-filling recognition module, a misalignment recognition module, an attribution correction module, a user profile generation module, and a benefits recommendation module;

[0156] The event acquisition module is used to collect parking behavior events, rights-related events, and identity status events, including parking order closing times. It records the occurrence time and write time of each event, resulting in a set of events with dual timestamps. The event acquisition module can receive parking behavior events output by the parking management system, member accounts and membership status output by the membership system, payment accounts and payment discount records output by the payment system, invoice numbers and consumption discount records output by the consumption system, coupon numbers and redemption status output by the coupon system, and rights redemption rules and redemption results output by the rights redemption system through interfaces.

[0157] The portrait atom generation module is used to generate parking behavior portrait atoms based on parking behavior events in the dual-time-marked event set, with the parking order number as the main index, and set the portrait affiliation status. When a parking order is generated, the portrait atom generation module determines whether there is a member account, payment account, invoice number, coupon number, or discount application number directly associated with the parking order. If not, the portrait affiliation status of the parking behavior portrait atom is set to the pending status.

[0158] The post-refilling identification module is used to atomically match rights-related events with parking behavior profiles, identify post-refilling rights events whose writing time is later than the closing time of the corresponding parking order and which change the rights status of the corresponding parking order, and form an order-rights-refilling chain; the post-refilling identification module supports direct association through parking order number, and also supports establishing association through at least two types of information from license plate number, station number, invoice number, member account, payment account, coupon number and discount application number, after verification by rights verification rules;

[0159] The misalignment detection module is used to verify the consistency between parking orders, license plate numbers, the rights holders determined by member accounts or payment accounts, the rights certificates determined by invoice numbers, coupon numbers or discount application numbers, the parking lot numbers, and the rights redemption rules based on the order-rights backfill chain. It outputs a profile misalignment flag and a set of candidate rights holders. The misalignment detection module outputs a profile misalignment flag when it detects that the member account or payment account corresponding to the subsequent rights backfill event is inconsistent with the original ownership record, the subsequent rights backfill event meets the rights redemption rules of the current parking order but does not meet the account relationship corresponding to the original ownership record, there are multiple candidate rights holders for the same parking order and it is impossible to determine a unique ownership, or the rights holder or the rights applicable parking lot corresponding to the subsequent rights backfill event is inconsistent with the original ownership record.

[0160] The attribution correction module is used to correct the attribution of parking behavior profile atoms based on the profile attribution misalignment marker and the candidate rights holder set, resulting in attribution-corrected parking behavior profile atoms. When a unique rights holder can be identified, the attribution correction module assigns the parking behavior profile atom to that rights holder; when a unique rights holder cannot be identified, the profile attribution status is set to pending confirmation; when a subsequent rights backfilling event cannot form a valid binding relationship with a parking order, it remains in a suspended state and is prohibited from being incorporated into the personal user profile.

[0161] The user profile generation module is used to atomically generate multi-dimensional user profiles based on the parking behavior profiles after attribution correction. The multi-dimensional user profiles include parking frequency profiles, parking duration profiles, parking lot preference profiles, rights usage profiles, membership profiles, rights attribution stability profiles, license plate sharing risk profiles, and revocable rights profiles. The user profile generation module only uses the parking behavior profiles with confirmed attribution to atomically generate profile content that is sorted based on personal historical parking behavior, historical rights usage records, or membership profiles.

[0162] When generating a stable ownership profile, the user profile generation module uses the ownership subject as an index to extract the license plate number, payment account, ownership certificate source system, and parking lot number from the confirmed ownership parking behavior profile atoms under that ownership subject, forming a set of license plate numbers, a set of payment accounts, a set of ownership certificate source systems, and a set of parking lot numbers. If the license plate number, payment account, ownership certificate source system, and parking lot number in the current parking order all belong to the above sets, and there is no misalignment marker in the current parking order, the user profile generation module outputs a stable ownership profile indicating a stable ownership relationship; otherwise, it outputs a stable ownership profile indicating an unstable ownership relationship.

[0163] When generating a license plate sharing risk profile, the user profile generation module uses the license plate number as an index to extract the member account and payment account associated with the license plate in the parking behavior profile atom that has been confirmed to belong to the vehicle. When the same license plate is associated with two or more different member accounts or two or more different payment accounts, the module outputs a license plate sharing risk profile indicating that there is a risk of license plate sharing. When the same license plate is associated with only the same member account and only the same payment account, the module outputs a license plate sharing risk profile indicating that there is no risk of license plate sharing.

[0164] The rights and benefits recommendation module is used to filter and sort candidate parking rights and benefits schemes based on multi-dimensional user profiles and parking rights and benefits scheme library, and output parking rights and benefits scheme recommendation results. When filtering candidate parking rights and benefits schemes, the rights and benefits recommendation module determines whether the candidate parking rights and benefits schemes are applicable to the current parking lot, the current license plate or the current rights and benefits subject, whether they are within the validity period, whether they meet the rights and benefits redemption rules of the current parking order, whether they conflict with the subsequent rights and benefits backfilling events that have been redeemed or are pending redemption, and whether the recommendation basis comes from the parking behavior profile atoms that have been confirmed to belong to.

[0165] When the benefits recommendation module sorts candidate parking benefit schemes, it sorts them in the following order: current redeemable benefit profile, parking lot preference profile, benefit usage profile, and expiration date. Specifically, the benefits recommendation module first determines whether a candidate parking benefit scheme meets the current redeemable benefit profile, and then ranks the candidate parking benefit schemes that meet the current redeemable benefit profile first. Next, it determines whether the applicable parking lot of the candidate parking benefit scheme is consistent with the parking lot preference profile, and then ranks the candidate parking benefit schemes that are consistent with the applicable parking lot first. Then, it determines whether the benefit type of the candidate parking benefit scheme is consistent with the benefit type that has been confirmed to be used in the benefit usage profile, and then ranks the candidate parking benefit schemes that are consistent with the benefit type first. If the above judgment results are the same, the candidate parking benefit scheme with the earlier expiration date is ranked first.

[0166] When the stability profile of rights ownership indicates that the correspondence between the current parking order, license plate number, member account, payment account and rights certificate is unstable, or the license plate sharing risk profile indicates that the current license plate is at risk of being shared, or the parking behavior profile is in an unconfirmed state, the rights recommendation module does not use personal historical parking behavior, historical rights usage records or membership profiles for sorting, but only outputs verifiable parking rights schemes based on the current parking order, current license plate, current rights holder, current parking lot and rights redemption rules.

[0167] Example 5: This example also provides an electronic device, which includes a processor, a memory, and a computer program stored in the memory and executable by the processor; when the computer program is executed by the processor, it implements the intelligent recommendation method for parking rights schemes based on multi-dimensional user profiles as described in any one of Examples 1 to 3.

[0168] The processor can be a central processing unit, a graphics processing unit, a digital signal processor, an application-specific integrated circuit, a field-programmable gate array, or other processing units with data processing capabilities; the memory can include volatile memory, non-volatile memory, a database storage unit, or a distributed storage unit; the electronic device can be deployed in a parking operation platform server, a commercial complex membership operation platform server, a park parking management server, a cloud parking benefits recommendation server, or an edge computing device.

[0169] This embodiment also provides a computer-readable storage medium storing a computer program. When the computer program is executed by a processor, it implements the intelligent recommendation method for parking rights schemes based on multi-dimensional user profiles as described in any one of embodiments one to three.

[0170] The method of the present invention can be implemented in software, hardware or a combination of software and hardware through the above-mentioned electronic device or computer-readable storage medium, and applied to parking rights recommendation services of different scales and types.

[0171] The above description is only a preferred embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any equivalent substitutions or modifications made by those skilled in the art within the scope of the technology disclosed in the present invention, based on the technical solution and inventive concept of the present invention, should be covered within the scope of protection of the present invention.

Claims

1. A method for intelligent recommendation of parking benefits schemes based on multi-dimensional user profiles, characterized in that, Includes the following steps: S1. Collect parking behavior events, rights-related events, and identity status events that include parking order closing time, record the event occurrence time and event writing time for each event, and obtain a set of events with dual time stamps; S2. Based on the parking behavior events in the dual-time-marked event set, generate parking behavior profile atoms with the parking order number as the main index, and set the profile ownership status; S3. Perform atomic matching between the rights-related events and the parking behavior profile, identify subsequent rights-backfilling events whose writing time is later than the closing time of the corresponding parking order and which change the rights status of the corresponding parking order, and form an order-rights-backfilling chain. S4. Based on the order-rights backfill chain, verify the consistency between parking order, license plate number, right subject determined by member account or payment account, right certificate determined by invoice number, coupon number or discount application number, station number and right redemption rules, and output profile misalignment marker and candidate right subject set; S5. Based on the misalignment marker of the portrait and the set of candidate rights subjects, the affiliation of the parking behavior portrait atom is corrected to obtain the affiliation-corrected parking behavior portrait atom. S6. Generate a multi-dimensional user profile based on the affiliation-corrected parking behavior profile. S7. Based on the multi-dimensional user profile and the parking benefit scheme library, filter and sort the candidate parking benefit schemes, and output the parking benefit scheme recommendation results.

2. The intelligent recommendation method for parking rights schemes based on multi-dimensional user profiles according to claim 1, characterized in that, The parking behavior events include parking order number, license plate number, parking lot number, entry time, exit time, parking duration, billing amount, order status, and parking order closing time; the rights-related events include member account, payment account, invoice number, coupon number, discount application number, rights type, rights amount, free parking duration, rights redemption status, and rights source system; the identity status events include the binding relationship between license plate and member account, the binding relationship between license plate and payment account, membership status, rights validity period, applicable parking lot, and applicable vehicle.

3. The intelligent recommendation method for parking rights schemes based on multi-dimensional user profiles according to claim 1, characterized in that, The parking behavior profile atom includes parking order number, license plate number, parking lot number, entry time, exit time, parking duration, billing amount, order status, initial rights status, profile ownership status, and original ownership record. The profile ownership status includes suspended status, confirmed ownership status, and pending confirmation status. The original ownership record is at least one of the license plate, member account, payment account, and parking lot ownership information recorded by the parking behavior profile atom before ownership correction. When a parking order is generated but no member account, payment account, invoice number, coupon number, or discount application number directly associated with the parking order is received, the profile ownership status of the parking behavior profile atom is set to suspended status.

4. The intelligent recommendation method for parking rights schemes based on multi-dimensional user profiles according to claim 1, characterized in that, The order-equity backfill chain is formed by: Match the rights-related events with the parking behavior profile atoms; When the rights-related event is directly associated with the parking behavior profile atom through the parking order number, or is associated with the parking behavior profile atom through a combination of at least two types of information among the license plate number, station number, invoice number, member account, payment account, coupon number, and discount application number and verified by the rights verification rules, and the writing time of the rights-related event is later than the departure time or closing time of the corresponding parking order, and the rights-related event changes the rights status, discount amount, free parking duration, verification result, or rights subject of the corresponding parking order, the rights-related event is determined as a post-rights backfilling event; Using the parking order number as the main index of the link, the parking behavior profile atoms are connected with the corresponding subsequent rights and interests backfilling events; The order-rights backfill chain includes parking order number, license plate number, station number, subsequent rights backfill event, rights holder, rights certificate, and rights cancellation status; wherein, the rights certificate includes invoice number, coupon number, or discount application number.

5. The intelligent recommendation method for parking rights schemes based on multi-dimensional user profiles according to claim 1, characterized in that, The consistency verification includes verifying the necessary relationships required by the rights and benefits redemption rules. These necessary relationships include whether the license plate number is consistent, whether the parking lot number is applicable, whether the member account is valid, whether the payment account is corresponding, whether the rights and benefits certificate is valid, whether the applicable vehicle for the rights and benefits matches, whether the applicable time period for the rights and benefits covers the current parking order, and whether the rights and benefits redemption rules allow the use of the current parking order.

6. The intelligent recommendation method for parking rights schemes based on multi-dimensional user profiles according to claim 3, characterized in that, Output the image attribution misalignment flag when one of the following conditions occurs: The member account or payment account corresponding to the post-rights refill event is inconsistent with the member account or payment account in the original attribution record; The subsequent rights and interests refill event meets the rights and interests reimbursement rules of the current parking order but does not meet the account, qualification or binding relationship corresponding to the original ownership record; The same parking order may correspond to multiple candidate beneficiaries and it is impossible to determine a unique owner based on the beneficiary write-off rules. The subsequent rights backfilling event changes the rights status of the parking order, and the rights holder or applicable parking station corresponding to the subsequent rights backfilling event is inconsistent with the original attribution record; The applicable site for the rights and interests corresponding to the post-rights backfilling event is inconsistent with the site ownership information in the original ownership record.

7. The intelligent recommendation method for parking rights schemes based on multi-dimensional user profiles according to claim 1, characterized in that, The attribution correction of the atoms in the parking behavior profile includes: When there is a subsequent rights-refilling event directly bound to the parking order number in the order-rights-refilling chain, and the member account, payment account, invoice number, coupon number or discount application number corresponding to the subsequent rights-refilling event meets the rights-refund rules of the parking order, the parking behavior profile is atomically attributed to the rights subject corresponding to the subsequent rights-refilling event. When there is no direct binding relationship between parking order numbers, but only one candidate rights holder in the candidate rights holder set satisfies all the necessary relationships, the parking behavior profile is atomically assigned to that candidate rights holder; When multiple candidate rights holders in the candidate rights holder set meet the necessary relationship and cannot be uniquely assigned, the attribution status of the parking behavior profile atom is set to pending confirmation, and the parking behavior profile atom is prohibited from participating in the recommendation of parking rights schemes that rely on personal historical parking behavior, historical rights usage records, or membership profiles for sorting. When the post-rights backfilling event cannot form a valid binding relationship with the parking order, the parking behavior profile atom is kept in a suspended state and is prohibited from being incorporated into the personal user profile.

8. The intelligent recommendation method for parking rights schemes based on multi-dimensional user profiles according to claim 1, characterized in that, The multi-dimensional user profile includes parking frequency profile, parking duration profile, parking lot preference profile, rights usage profile, membership profile, rights ownership stability profile, license plate sharing risk profile, and redeemable rights profile. Specifically, the parking frequency profile is generated from the number of parking orders in the confirmed parking behavior profile atoms; the parking duration profile is generated from the parking duration in the confirmed parking behavior profile atoms; the parking lot preference profile is generated from the parking lot number and corresponding number of parking sessions in the confirmed parking behavior profile atoms; and the rights usage profile is generated from the rights in the confirmed parking behavior profile atoms. The system generates the benefit type, benefit amount, free parking duration, and benefit redemption status. The membership profile is generated from the membership status and benefit validity period in the confirmed identity status event. The benefit ownership stability profile is generated from the correspondence between parking orders, license plate numbers, member accounts, payment accounts, and benefit certificates under the same benefit subject. The license plate sharing risk profile is generated from different member accounts or different payment accounts associated with the same license plate in different parking orders. The redeemable benefit profile is generated from the matching relationship between the current benefit subject, current license plate, current parking station, current parking order, and benefit redemption rules.

9. The intelligent recommendation method for parking rights schemes based on multi-dimensional user profiles according to claim 1, characterized in that, Screening candidate parking benefit schemes, including: The parking benefits scheme database includes benefit scheme number, benefit type, applicable stations, applicable vehicles, applicable benefit subjects, validity period, free parking duration, discount rules, usage limit, payment channel limit, and redemption entry; The parking rights scheme that simultaneously meets the following requirements is applicable to the parking lot corresponding to the current parking order, applicable to the license plate or rights holder corresponding to the current parking order, is within the validity period, meets the rights cancellation rules of the current parking order, does not conflict with the subsequent rights backfilling events that have been cancelled or are pending cancellation in the current parking order, and is recommended based on the parking behavior profile atom that has been confirmed to belong. Candidate parking benefit schemes are ranked based on parking frequency profile, parking duration profile, parking station preference profile, benefit usage profile, membership profile, benefit ownership stability profile, license plate sharing risk profile, and redeemable benefit profile. When the stability profile of the rights attribution indicates that the correspondence between the current parking order, license plate number, member account, payment account and rights certificate is unstable, or the license plate sharing risk profile indicates that the current license plate is associated with different member accounts or different payment accounts, or the corresponding parking behavior profile is in a pending confirmation state, only parking rights schemes that do not rely on personal historical parking behavior, historical rights usage records or membership profiles for sorting and meet the current parking order cancellation conditions will be output.

10. A parking rights scheme intelligent recommendation system based on multi-dimensional user profiles, applied to the parking rights scheme intelligent recommendation method based on multi-dimensional user profiles as described in any one of claims 1-9, characterized in that, Specifically, it includes: The event acquisition module is used to collect parking behavior events, rights-related events, and identity status events, including parking order closing times. It records the occurrence time and writing time of each event, resulting in a set of events with dual time stamps. The portrait atom generation module is used to generate parking behavior portrait atoms based on parking behavior events in the dual-time-marked event set, with the parking order number as the main index, and to set the portrait affiliation status. The post-filling identification module is used to atomically match the rights-related events with the parking behavior profile, identify post-rights-filling events whose writing time is later than the closing time of the corresponding parking order and which change the rights status of the corresponding parking order, and form an order-rights-filling chain. The misalignment detection module is used to verify the consistency between parking orders, license plate numbers, rights holders determined by member accounts or payment accounts, rights certificates determined by invoice numbers, coupon numbers or discount application numbers, station numbers and rights redemption rules based on the order-rights backfill chain, and output profile misalignment markers and candidate rights holder sets; The attribution correction module is used to perform attribution correction on the parking behavior profile atom based on the profile attribution misalignment marker and the candidate rights subject set, so as to obtain the attribution-corrected parking behavior profile atom. The user profile generation module is used to generate multi-dimensional user profiles based on the attribution-corrected parking behavior profiles. The benefits recommendation module is used to filter and sort candidate parking benefits schemes based on the multi-dimensional user profile and the parking benefits scheme library, and output the parking benefits scheme recommendation results.

Images