A business processing method, apparatus, electronic device, and computer-readable medium
By identifying account quantity change indicators and calling the unique account exclusion model, the target account for fee reduction is determined and the fee reduction process is executed, which solves the problem that the existing system cannot proactively waive fees for unique accounts and achieves automated fee management that meets regulatory requirements.
Patent Information
- Application Number
- CN202111574893.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2021-12-21
- Publication Date
- 2025-10-31
- Estimated Expiration
- 2041-12-21
AI Technical Summary
The existing system cannot proactively waive the account management fee and annual fee for a single account, resulting in additional charges to customers, which fails to meet regulatory requirements.
By receiving business processing requests, identifying the category of account quantity change indicators, calling the unique account exclusion model to determine whether the account meets the unique account system, identifying the target account for fee reduction, and executing the fee reduction processing.
It enables proactive waiver of account management fees and annual fees for the sole account based on business scenarios, avoiding additional charges to customers and meeting regulatory requirements.
Smart Images
Figure CN114240445B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of data verification technology, and in particular to a business processing method, apparatus, electronic device and computer-readable medium. Background Technology
[0002] As required by regulations, institutions should "proactively" waive account management fees and annual fees for customers' sole accounts opened with them. Current systems lack the function to proactively waive fees for sole accounts; these fees must be manually reduced or waived through bank card fee maintenance and private current account contract information maintenance transactions. Existing functions fail to meet regulatory requirements because they cannot identify whether an account is included in the sole account identification system, cannot automatically identify whether an account under a customer's name is a sole account, and cannot proactively waive account management fees and annual fees for sole accounts, thus incurring additional charges to customers.
[0003] In the process of developing this application, the inventors discovered at least the following problems in the prior art:
[0004] The existing system functions of various institutions do not meet regulatory requirements, and they are unable to proactively waive the account management fee and annual fee for the sole account, thus charging customers additional fees. Summary of the Invention
[0005] In view of this, embodiments of this application provide a business processing method, apparatus, electronic device, and computer-readable medium that can solve the problem that the existing system functions of various institutions do not meet regulatory requirements, cannot proactively waive account management fees and annual fees for unique accounts, and charge customers additional fees.
[0006] To achieve the above objectives, according to one aspect of an embodiment of this application, a business processing method is provided, comprising:
[0007] Receive business processing requests, identify the corresponding accounts and obtain the corresponding account quantity change identifiers, and then identify the category of the account quantity change identifiers;
[0008] Call the preset unique account exclusion model to determine whether the account conforms to the unique account system; otherwise, return a no-processing flag.
[0009] If so, identify the other accounts corresponding to the account, and then determine whether there are any accounts among the other accounts that conform to the unique account system; otherwise, determine the target account for exemption based on the category.
[0010] If so, determine the number of accounts that have already received a reduction in fees among other accounts that conform to the unique account system, and determine the target account for the reduction in fees based on the number and category of the accounts that have already received a reduction in fees;
[0011] Execute the business processing request to process the fee reduction for the target account.
[0012] Optionally, the target account for the tax reduction can be determined based on the category, including:
[0013] In response to the increase in the number of accounts identified as a category, the account is identified as the target account for the tax reduction.
[0014] Optionally, the target account for the tax reduction can be determined based on the category, including:
[0015] If the category is determined to be a decrease in the number of accounts, then the target account for the fee reduction is determined to be null, and a no-processing flag is returned.
[0016] Optionally, the target accounts for tax relief can be determined based on the number and category of accounts that have already received tax relief, including:
[0017] In response to the determination that the category is an increase in the number of accounts and the number of accounts that have been exempted is 0, a prompt message for selecting exempted accounts is returned, the selected exempted account information is received, and then the account corresponding to the exempted account information is determined as the target exempted account;
[0018] If the category is determined to be an increase in the number of accounts and the number of accounts that have already received a discount is greater than 0, then the target discount account is determined to be null and a no-processing flag is returned.
[0019] Optionally, the target accounts for tax relief can be determined based on the number and category of accounts that have already received tax relief, including:
[0020] In response to the determination that the category is a decrease in the number of accounts and the number of accounts that have been exempted is 0, it is determined whether the account included in the unique account system among other accounts is unique. If so, the unique account included in the unique account system among other accounts is determined as the target exemption account; otherwise, the exemption account selection prompt message is returned, the selected exemption account information is received, and the account corresponding to the exemption account information is determined as the target exemption account.
[0021] If the category is determined to be a decrease in the number of accounts and the number of accounts that have already received a discount is greater than 0, then the target account for discount is determined to be null and a flag indicating that no processing is required is returned.
[0022] Optionally, the business processing method also includes:
[0023] Set a reduction / exemption flag for the target account and update the flag regularly.
[0024] Optionally, fees may be waived for the target waiver account, including:
[0025] Remove the target accounts for fee reduction from the list of outstanding annual fees and the list of outstanding small account management fees.
[0026] Optionally, after waiving the fees for the target waiver account, the method may also include:
[0027] Get the timestamp of the contract snapshot table for the day the business processing request is executed;
[0028] Based on the timestamp, we can filter out customers who had account changes on that day and all their personal deposit debit card accounts.
[0029] By removing all personal deposit debit card accounts that do not conform to the unique account system, a list of unique accounts can be obtained.
[0030] Based on the list of unique accounts, the corresponding unique accounts are removed from the list of outstanding annual fees and the list of outstanding small account management fees, and the corresponding unique accounts are marked with an annual fee reduction mark and a small fee reduction mark.
[0031] In addition, this application also provides a business processing apparatus, including:
[0032] The receiving unit is configured to receive business processing requests, determine the corresponding account and obtain the corresponding account quantity change identifier, and then identify the category of the account quantity change identifier;
[0033] The first judgment unit is configured to call the preset unique account exclusion model to determine whether the account conforms to the unique account system; otherwise, it returns a no-processing flag.
[0034] The second judgment unit is configured to determine other accounts corresponding to the account if the condition is met, and then determine whether there is an account among the other accounts that conforms to the unique account system; otherwise, the target exemption account is determined according to the category.
[0035] The target exemption account determination unit is configured to determine the number of exempted accounts among other accounts that conform to the unique account system if it is configured to determine the target exemption account based on the number and category of exempted accounts.
[0036] The execution unit is configured to execute business processing requests to process fee reductions for the target account.
[0037] Optionally, the second decision unit is further configured to:
[0038] In response to the increase in the number of accounts identified as a category, the account is identified as the target account for the tax reduction.
[0039] Optionally, the second decision unit is further configured to:
[0040] If the category is determined to be a decrease in the number of accounts, then the target account for the fee reduction is determined to be null, and a no-processing flag is returned.
[0041] Optionally, the target exemption account determination unit is further configured to:
[0042] In response to the determination that the category is an increase in the number of accounts and the number of accounts that have been exempted is 0, a prompt message for selecting exempted accounts is returned, the selected exempted account information is received, and then the account corresponding to the exempted account information is determined as the target exempted account;
[0043] If the category is determined to be an increase in the number of accounts and the number of accounts that have already received a discount is greater than 0, then the target discount account is determined to be null and a no-processing flag is returned.
[0044] Optionally, the target exemption account determination unit is further configured to:
[0045] In response to the determination that the category is a decrease in the number of accounts and the number of accounts that have been exempted is 0, it is determined whether the account included in the unique account system among other accounts is unique. If so, the unique account included in the unique account system among other accounts is determined as the target exemption account; otherwise, the exemption account selection prompt message is returned, the selected exemption account information is received, and the account corresponding to the exemption account information is determined as the target exemption account.
[0046] If the category is determined to be a decrease in the number of accounts and the number of accounts that have already received a discount is greater than 0, then the target account for discount is determined to be null and a flag indicating that no processing is required is returned.
[0047] Optionally, the service processing apparatus further includes an update unit configured to:
[0048] Set a reduction / exemption flag for the target account and update the flag regularly.
[0049] Optionally, the execution unit is further configured to:
[0050] Remove the target accounts for fee reduction from the list of outstanding annual fees and the list of outstanding small account management fees.
[0051] Optionally, the service processing apparatus further includes a real-time re-examination unit, configured to:
[0052] Get the timestamp of the contract snapshot table for the day the business processing request is executed;
[0053] Based on the timestamp, we can filter out customers who had account changes on that day and all their personal deposit debit card accounts.
[0054] By removing all personal deposit debit card accounts that do not conform to the unique account system, a list of unique accounts can be obtained.
[0055] Based on the list of unique accounts, the corresponding unique accounts are removed from the list of outstanding annual fees and the list of outstanding small account management fees, and the corresponding unique accounts are marked with an annual fee reduction mark and a small fee reduction mark.
[0056] In addition, this application also provides a business processing electronic device, including: one or more processors; and a storage device for storing one or more programs, which, when executed by one or more processors, enable the one or more processors to implement the business processing method described above.
[0057] In addition, this application also provides a computer-readable medium having a computer program stored thereon, which, when executed by a processor, implements the business processing method described above.
[0058] To achieve the above objectives, according to another aspect of the embodiments of this application, a computer program product is provided.
[0059] A computer program product according to an embodiment of this application includes a computer program that, when executed by a processor, implements the business processing method provided in the embodiment of this application.
[0060] One embodiment of the above invention has the following advantages or beneficial effects: This application receives a business processing request, determines the corresponding account and obtains the corresponding account quantity change identifier, and then identifies the category of the account quantity change identifier; it calls a preset unique account exclusion model to determine whether the account conforms to the unique account system, and if not, returns an "no processing required" identifier; if so, it determines other accounts corresponding to the account, and then determines whether there are any accounts among the other accounts that conform to the unique account system, and if not, it determines the target fee reduction account according to the category; if so, it determines the number of already-reduced accounts among the other accounts that conform to the unique account system, and determines the target fee reduction account according to the number of already-reduced accounts and the category; it executes the business processing request to reduce the fees of the target fee reduction account. By implementing corresponding proactive fee reduction strategies based on the private account change scenario, i.e., the category of the account quantity change identifier (whether the number of accounts increases or decreases), and whether it is included in the unique account system and whether there are already-reduced accounts among other accounts, it can determine the target fee reduction account according to the business scenario, proactively waive the account management fee and annual fee of the target fee reduction account (which is also the unique account), and avoid additional charges to customers.
[0061] The further effects of the aforementioned unconventional alternative methods will be explained below in conjunction with specific implementation methods. Attached Figure Description
[0062] The accompanying drawings are provided to better understand this application and do not constitute an undue limitation thereof. Wherein:
[0063] Figure 1 This is a schematic diagram of the main flow of the business processing method according to the first embodiment of this application;
[0064] Figure 2 This is a schematic diagram of the main flow of the business processing method according to the second embodiment of this application;
[0065] Figure 3 This is a flowchart illustrating a scenario where the number of private accounts is increased, based on the business processing method of an embodiment of this application.
[0066] Figure 4 This is a flowchart illustrating a scenario where the number of private accounts is reduced according to the business processing method of an embodiment of this application.
[0067] Figure 5 This is a schematic diagram of the main units of a service processing apparatus according to an embodiment of this application;
[0068] Figure 6 This is an exemplary system architecture diagram to which embodiments of this application can be applied;
[0069] Figure 7 This is a schematic diagram of the structure of a computer system suitable for implementing terminal devices or servers in the embodiments of this application. Detailed Implementation
[0070] The following description, in conjunction with the accompanying drawings, illustrates exemplary embodiments of this application, including various details to aid understanding. These should be considered merely exemplary. Therefore, those skilled in the art should recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of this application. Similarly, for clarity and brevity, descriptions of well-known functions and structures are omitted in the following description. The acquisition, storage, use, and processing of data in the technical solutions of this application all comply with relevant national laws and regulations.
[0071] Figure 1 This is a schematic diagram of the main flow of the business processing method according to the first embodiment of this application, as shown below. Figure 1 As shown, the business processing methods include:
[0072] Step S101: Receive a business processing request, determine the corresponding account and obtain the corresponding account quantity change identifier, and then identify the category of the account quantity change identifier.
[0073] In this embodiment, the execution entity of the business processing method (e.g., a server) can receive business processing requests via wired or wireless connections. The system obtains the account quantity change identifier corresponding to the business processing scenario carried in the business processing request. This quantity change identifier can be, for example, 1, -1, or other numbers or letters. This embodiment does not limit the specific content of the quantity change identifier. For example, the quantity change identifier 1 (or a, b, etc.) can correspond to a category of increased account quantity, and -1 (or 0, -a, etc.) can correspond to a category of decreased account quantity.
[0074] Step S102: Call the preset unique account exclusion model to determine whether the account conforms to the unique account system.
[0075] Unique Account Exclusion Method (Product Blacklist Exclusion, Non-Entity Exclusion). Products that inherently offer discounts but do not occupy the customer's unique discount quota (such as mobile payments, irregularly shaped cards, special social security cards, etc.), wealth cards, private banking cards, and quasi-credit cards are added to the blacklist. This information is then modified by product development and pushed to the customer's information. If the contract attachment type is 02-Family, 05-Single Medium Multiple Card Numbers, 06-Supplementary Card, 14-One Account Multiple Mediums, 25-Sub-Account within Card, and the medium type is 4-Dedicated Account Virtual Card, 9-No Medium, the pushed contract snapshot identifier is assigned the value X-Does not occupy (customer's unique discount quota).
[0076] Unique Account Identification System Methodology: Filter out accounts not included in the Unique Account Identification System based on the following conditions; filter out such products based on the product list not included in the Unique Account Identification System; filter out accounts not belonging to the settlement account product range; filter out electronic accounts without physical media; filter out closed accounts and dormant accounts; filter out ordinary current passbooks whose fund usage is not "general purpose"; filter out free trade zone accounts.
[0077] A unique account means that each user can only have one bank account across all banks. Furthermore, each bank account can only have one bank credit card. Specifically, a unique account means that each user can only open one bank account at a single bank, and under that bank account, only one type of bank card can be opened. The executing entity can invoke a preset unique account exclusion model to verify the uniqueness of the currently changing account. This preset model includes a unique verification procedure. When the relevant information of the currently changing account (such as account name, user ID, etc.) is input into the model, the executing entity can invoke the unique verification procedure to determine whether the currently changing account is the only one in the corresponding bank and whether it has only one type of bank card. If the currently changing account is the only one in the corresponding bank and has only one type of bank card, then the currently changing account conforms to the unique account system; otherwise, it does not.
[0078] Step S103: Otherwise, return the "No Processing Required" flag.
[0079] If the currently changing account does not conform to the unique account system, then as follows: Figure 3 and Figure 4 As shown, the executing entity returns a no-processing flag, does not mark the account with a fee reduction flag, and does not perform any fee reduction processing.
[0080] Step S104: If yes, then determine the other accounts corresponding to the account.
[0081] like Figure 3 and Figure 4 As shown, if the currently changing account conforms to the unique account system, the executing entity can determine other private accounts under the customer's name to which the currently changing account belongs.
[0082] Step S105: Determine whether there are any accounts among the other accounts that conform to the unique account system.
[0083] like Figure 3 and Figure 4 As shown, after determining the other private accounts under the customer's name to which the current changed account belongs, the executing entity can continue to determine whether there are any accounts under the customer's name that conform to the unique account system.
[0084] Step S106: Otherwise, determine the target account for the tax reduction based on the category.
[0085] If none of the customer's other private accounts meet the criteria for a unique account, the target account for fee waiver will be determined based on the category of the account quantity change identifier. The target account for fee waiver is the account for which annual fees and small account management fees will be waived in the future.
[0086] Step S107: If yes, determine the number of accounts that have already been exempted from fees among other accounts that conform to the unique account system, and determine the target exemption account based on the number and category of exempted accounts.
[0087] Exempted Account Rules: For bank cards, both fees must be waived for an account to be considered exempted; waiving only one fee is considered not exempted. For passbooks, only the small-amount fee applies; identification is based on the small-amount fee. A single account is defined by account medium. For combined card / passbook accounts, primary and supplementary cards, and family cards, exemption on any medium is considered fulfilling the single account exemption condition. For exemptions due to contractual relationships (passbook signing identifier, student discounts, personal loan repayments, etc.), if the contractual relationship changes (termination, change of personal loan repayment account), the system should accurately identify whether the current account meets the exemption condition based on the contractual changes. If product-level parameters are set to free, when product parameters are adjusted, the system should accurately identify whether the current account meets the exemption condition based on the parameter adjustments.
[0088] If any of the customer's other private accounts conform to the unique account system, the executing entity can determine the number of accounts that have already been exempted from fees among the other accounts that conform to the unique account system, and determine the target exempted account based on the number of accounts that have already been exempted from fees among the other accounts that conform to the unique account system and the category of the account number change identifier.
[0089] Specifically, the target accounts for tax reduction are determined based on the number and category of accounts that have already received tax reductions, including:
[0090] In response to the determination that the category is a decrease in the number of accounts and the number of accounts that have been exempted is 0, it is determined whether the account included in the unique account system among other accounts is unique. If so, the unique account included in the unique account system among other accounts is determined as the target exemption account; otherwise, the exemption account selection prompt message is returned, the selected exemption account information is received, and the account corresponding to the exemption account information is determined as the target exemption account.
[0091] If the category is determined to be a decrease in the number of accounts and the number of accounts that have already received a discount is greater than 0, then the target account for discount is determined to be null and a flag indicating that no processing is required is returned.
[0092] like Figure 4 As shown, the executing entity can first determine the scenario of changes to private accounts corresponding to the business processing request. For example, scenarios such as closing private deposit and debit card accounts, converting a normal account to a dormant account, and replacing bank cards (where the old card belongs to the unique account system, while the new card does not). These scenarios all correspond to the category of a decrease in the number of accounts. After determining that the currently changed account conforms to the unique account system, the executing entity can obtain other accounts under the customer's name and determine whether these other accounts conform to the unique account system. If they do not conform, the customer information component returns a "no processing required" flag (e.g., null). If they do conform, it further determines whether there are any accounts under the customer's name that have already had their fees reduced. If so (i.e., the number of reduced accounts is greater than 0), the customer information component returns a "no processing required" flag (e.g., null). If not (i.e., the number of reduced accounts is 0), it continues to determine whether there is only one account under the customer's name that conforms to the unique user system. If so, the customer information component returns a reduction flag (e.g., M-reduction). The executing entity adds the reduction flag to the currently changed account based on the returned information. If not, the customer information component returns a prompt message to prompt the customer to select one of the accounts conforming to the unique account system from among the other accounts as the target reduction account, and receives the customer's account selection information. Based on this selection information, the target reduction account is determined. The target reduction account is the identified unique account.
[0093] After identifying a unique account, the executing entity adds a small-amount fee waiver and an annual fee waiver flag to the unique account. This allows the executing entity to perform the maintenance process for the two fees (small-amount fee for personal deposits and annual fee for debit cards) of the personal account. Specifically, when the executing entity detects that the customer information component returns an "M-waiver" flag, it maintains the small-amount fee waiver flag for the personal deposit of the target waiver account (i.e., the unique account) and the annual fee waiver flag for the debit card. When the executing entity detects that the customer information component returns a "no processing required" flag, no processing is required for the target waiver account. When the executing entity detects that the customer information component returns a prompt message, it prompts the teller node to link the fee waiver; batch account opening transactions are not processed. When the executing entity detects that the currently changing account does not conform to the unique account system, no processing is required for the target waiver account.
[0094] Account Closure Service Linkage and Reduction Rules (All accounts refer to the unique account system). For account closure, if the customer has no other accounts under their name, there is no need to process the unique account free service. For account closure, if the customer has an account that has already been exempted from free services, there is no need to process the unique account free service. For account closure, if the customer has only one account that is not exempted from free services, the system will automatically set that account to free. For the closure of an already free account, if the customer has multiple accounts that are not exempted from free services, the system will link to the dedicated trading display account list, and the customer will be asked to select one to receive free services.
[0095] Normal to Dormant Account Linked Fee Reduction Rules (Accounts refer to the single account system). If an account is converted to dormant status and is already set to free service, it will be set to non-free service upon conversion. If a customer has only one normal account that is not yet free of charge when converting an account to dormant status, the system will automatically set that normal account to free service. If a customer has multiple normal accounts that are not yet free of charge when converting an account to dormant status, the customer will be reminded via bulk SMS to apply for free service at our branch. If a customer has a normal account that is already free of charge when converting an account to dormant status, there is no need to process the single account free service.
[0096] Specifically, the business processing methods also include:
[0097] Set a reduction / exemption flag for the target account and update the flag regularly.
[0098] For example, the maintenance of the exemption flag for a unique account (i.e., the target exemption account): The system proactively performs exemption processing for unique accounts. When the account status under a customer's name changes due to account opening / closing, normal account switching to dormant, dormant account switching to normal, or non-operating account switching to normal at the counter and STM channels, the exemption processing for the unique account will be triggered. The executing entity can call the data warehouse component to perform a unique account data screening at the end of each day, obtain the customer account view (all accounts under the customer's name) from the customer information component. If the customer account is a unique account, the exemption status of the account is then obtained from the deposit debit card component. If the warehouse screens out a unique account but does not set an exemption flag, the data is pushed to the customer information, personal deposit, and debit card components. Personal deposits and debit cards will perform small-amount account management fee and annual fee exemptions in batch processing at the end of each day. The customer information will change the account exemption flag to M-Exempt (the exemption flags in the customer information account contract: M-Exempt; N-No Exemption; X-Not Included; Null; 0). The unique account exemption processing is performed through the "Personal Deposit Customer Fee Inquiry and Maintenance" transaction. Due to reasons such as contractual relationships, the account is the only one that is inherently exempt from annual fees and account management fees. Currently, the system does not mark the account as exempt at the account level. This will be optimized to mark the account as a unique account to prevent it from becoming a non-exempt account after the contractual relationship is terminated.
[0099] Step S108: Execute the business processing request to process the fee reduction for the target account.
[0100] Specifically, fee reductions will be applied to the target fee-reduction account, including:
[0101] Remove the target accounts for fee reduction from the list of outstanding annual fees and the list of outstanding small account management fees.
[0102] For example, the target account for fee reduction is the unique account identified. After identifying the unique account, the executing entity can remove the identified unique account from the list of outstanding annual fees and the list of outstanding small account management fees to avoid overcharging and duplicate charges.
[0103] Specifically, after waiving the fees for the target waiver account, the method also includes:
[0104] Obtain the timestamp of the contract snapshot table for the day the business processing request is executed; filter by timestamp to obtain customers with account changes on that day and all personal deposit debit card accounts under the customer's name; remove accounts that do not conform to the unique account system from all personal deposit debit card accounts to obtain a unique account list; based on the unique account list, remove the corresponding unique accounts from the list of outstanding annual fees and the list of outstanding small account management fees, and mark the corresponding unique accounts with annual fee reduction and small fee reduction indicators.
[0105] For example, on the 27th of each month (the 28th is for debit card annual fees) and the 20th of the last day of each quarter (the 21st is for small account management fees), for cases where fees are due the following day and there have been changes to the customer's accounts on that day, a second real-time check is performed at the time of payment to ensure that there are no overcharges or incorrect charges due to time delays. Based on the timestamp of the contract snapshot table on the day the business processing request is executed, customers with account changes on that day are filtered out, and then all personal deposit debit card accounts under that customer's name are filtered out. According to the filtering document, accounts not included in the unique account system are removed, and the unique accounts under the customer's name are filtered out to form a unique account list. Based on the unique account list, the unique accounts are removed from the list of outstanding annual fees and the list of outstanding small account management fees. And the unique accounts are marked with an annual fee reduction mark and a small fee reduction mark.
[0106] This embodiment receives a business processing request, identifies the corresponding account and obtains the corresponding account quantity change identifier, and then identifies the category of the account quantity change identifier; it calls a preset unique account exclusion model to determine whether the account conforms to the unique account system; if not, it returns an "no processing required" identifier; if so, it identifies other accounts corresponding to the account, and then determines whether any of the other accounts conform to the unique account system; if not, it determines the target account for fee reduction based on the category; if so, it determines the number of already-reduced accounts among the other accounts conforming to the unique account system, and determines the target account for fee reduction based on the number of already-reduced accounts and the category; it executes the business processing request to reduce the fees for the target account for fee reduction. By implementing corresponding proactive fee reduction strategies based on the private account change scenario, i.e., the category of the account quantity change identifier (increase or decrease in the number of accounts), whether it is included in the unique account system, and whether there are already-reduced accounts among other accounts, it can determine the target account for fee reduction based on the business scenario and proactively waive the account management fee and annual fee for the target account for fee reduction (which is also the unique account), avoiding additional charges to customers.
[0107] Figure 2 This is a schematic diagram of the main flow of the business processing method according to the second embodiment of this application, as follows: Figure 2 As shown, the business processing methods include:
[0108] Step S201: Receive a business processing request, determine the corresponding account and obtain the corresponding account quantity change identifier, and then identify the category of the account quantity change identifier.
[0109] Step S202: Call the preset unique account exclusion model to determine whether the account conforms to the unique account system.
[0110] Step S203: Otherwise, return the "No Processing Required" flag.
[0111] Step S204: If yes, then determine the other accounts corresponding to the account.
[0112] Step S205: Determine whether there are any accounts among the other accounts that conform to the unique account system.
[0113] Step S206: Otherwise, in response to the determination of an increase in the number of accounts, determine the account as the target relief account.
[0114] like Figure 3 As shown, if the executing entity determines that the current changed account conforms to the unique account system and there are no other accounts under the customer's name that conform to the unique account system, and when the number of accounts is increased, then the current changed account is determined to be the target exemption account, i.e., the unique account.
[0115] Alternatively, proceed to step S207. If the category is determined to be a decrease in the number of accounts, then determine that the target account for the reduction is null and return a no-processing flag.
[0116] like Figure 4 As shown, if the executing entity determines that the current changed account conforms to the unique account system and there are no other accounts under the customer's name that conform to the unique account system, and when it is determined that the number of accounts has decreased, then it is determined that there is no target account for the exemption, and the target account for the exemption is a null value (e.g., null). In this case, no processing is required for the current changed account, and a no-processing flag (e.g., null) is returned.
[0117] Step S208: If yes, determine the number of exempted accounts among other accounts that conform to the unique account system.
[0118] Step S209: In response to determining that the category is "account quantity increases" and the number of accounts with reduced fees is 0, a prompt message for selecting a reduced fee account is returned, the selected reduced fee account information is received, and then the account corresponding to the reduced fee account information is determined as the target reduced fee account. Alternatively, step S210 can be executed.
[0119] In step S210, in response to determining that the category is an increase in the number of accounts and the number of accounts that have already received a discount is greater than 0, the target discount account is determined to be null and a no-processing flag is returned.
[0120] like Figure 3As shown, the executing entity can first determine the scenario of changes to private accounts corresponding to the business processing request. For example, scenarios such as a single opening of a private deposit and debit card account, a batch opening of a private deposit and debit card account, a dormant account turning to normal / non-operating account turning to normal, and a bank card replacement scenario (where the new card belongs to the unique account system, and the old card does not belong to the unique account system). These scenarios all correspond to the category of an increase in the number of accounts. After determining that the currently changed account conforms to the unique account system, the executing entity can obtain other accounts under the customer's name and determine whether these other accounts conform to the unique account system. If they do not conform, the customer information component returns a reduction indicator (e.g., M-Reduction). The executing entity adds the reduction indicator to the currently changed account based on the returned information. If they conform, it further determines whether there are any already reduced accounts among the other accounts under the customer's name. If yes (i.e., the number of already reduced accounts is greater than 0), the customer information component returns a no-processing indicator (e.g., null). If no (i.e., the number of already reduced accounts is 0), the customer information component returns a prompt message to prompt the customer to select one of the other accounts conforming to the unique account system as the target reduction account, and receives the customer's account selection information. Based on this selection information, the target reduction account is determined. The target reduction account is the identified unique account.
[0121] like Figure 3 As shown, after identifying a unique account, the executing entity adds a small-amount fee waiver flag and an annual fee waiver flag to the unique account. This allows the executing entity to perform the maintenance process for the two fees (small-amount fee for personal deposits and annual fee for debit cards) of the personal account. Specifically, when the executing entity detects that the customer information component returns an M-waiver flag, it maintains the small-amount fee waiver flag for the personal deposit of the target waiver account (i.e., the unique account) and maintains the annual fee waiver flag for the debit card. When the executing entity detects that the customer information component returns a no-processing flag, no processing is required for the target waiver account. When the executing entity detects that the customer information component returns a prompt message, it prompts the teller node to link the fee waiver; batch account opening transactions are not processed. When the executing entity detects that the currently changing account does not conform to the unique account system, no processing is required for the target waiver account.
[0122] Account opening service fee reduction rules: For new accounts opened by customers with no other accounts under their name, the system will automatically set the new account as free (including batch account openings); for new accounts opened by customers with multiple non-free accounts under their name, the system will link to the private account fee maintenance transaction display account list, and the customer will be asked to select one for free (excluding batch account openings); for new accounts opened by customers with other free accounts under their name, there is no need to process the single account free service (including batch account openings).
[0123] Rules for linking dormant accounts to normal accounts and non-operating accounts to normal accounts (all accounts refer to the unique account system): When a dormant account is converted to normal, if the customer has no other accounts under their name, the system will automatically set the non-exempt account to be free; when a dormant account is converted to normal, if the customer has an already exempted normal account under their name, there is no need to process the unique account free service; when a dormant account is converted to normal, if the customer still has no other non-exempt accounts under their name, the teller will be prompted to ask the customer to select an account for exemption.
[0124] Step S211: Execute the business processing request to process the fee reduction for the target account.
[0125] This application embodiment receives a business processing request, determines the corresponding account, and obtains the corresponding account quantity change identifier. It then determines whether the account is included in the unique account system based on a preset unique account exclusion method; otherwise, it returns "no processing required." If the account is included, it identifies other accounts corresponding to that account and determines whether any of these other accounts are included in the unique account system. If not, it determines whether the account quantity change identifier corresponds to an increase or decrease in the number of accounts. If the number of accounts increases, it marks the account with a reduction identifier; if the number of accounts decreases, it returns "no processing required." If the account quantity change identifier corresponds to an increase in the number of accounts, it returns "no processing required." If the account quantity change identifier corresponds to a decrease in the number of accounts, it determines whether any of the other accounts included in the unique account system have already been marked with a reduction identifier. If so, it returns "no processing required." Otherwise, if the account quantity change identifier corresponds to an increase in the number of accounts, it returns a reduction account selection prompt; if the account quantity change identifier corresponds to a decrease in the number of accounts, it determines whether any of the other accounts included in the unique account system are unique. If so, it marks the unique other accounts included in the unique account system with a reduction identifier; otherwise, it returns a reduction account selection prompt. This application provides a method for automatic account fee reduction and waiver across all scenarios, a unique account identification system, a method for maintaining unique account fee reduction and waiver flags, and a method for secondary real-time re-verification at the time of account management fee and annual fee collection. This solves the problem of proactively waiving account management fees and annual fees for unique accounts based on business scenarios. Through this unique account identification system, the embodiments of this application can achieve proactive waiver of account management fees and annual fees for unique accounts based on various business scenarios.
[0126] Figure 5 This is a schematic diagram of the main units of a service processing apparatus according to an embodiment of this application. Figure 5 As shown, the business processing device includes a receiving unit 501, a first judgment unit 502, a second judgment unit 503, a target exemption account determination unit 504, and an execution unit 505.
[0127] The receiving unit 501 is configured to receive a service processing request, determine the corresponding account and obtain the corresponding account quantity change identifier, and then identify the category of the account quantity change identifier.
[0128] The first judgment unit 502 is configured to call a preset unique account exclusion model to determine whether the account conforms to the unique account system; otherwise, it returns a no-processing flag.
[0129] The second judgment unit 503 is configured to determine other accounts corresponding to the account if the condition is met, and then determine whether there is an account among the other accounts that conforms to the unique account system; otherwise, determine the target exemption account according to the category.
[0130] The target exemption account determination unit 504 is configured to determine the number of exempted accounts among other accounts that conform to the unique account system if the condition is met, and determine the target exemption account based on the number and category of exempted accounts.
[0131] Execution unit 505 is configured to execute a business processing request to process the fee reduction for the target account.
[0132] In some embodiments, the second determination unit 503 is further configured to: determine the account as the target exemption account in response to determining that the category is an increase in the number of accounts.
[0133] In some embodiments, the second determination unit 503 is further configured to: in response to determining that the category is a decrease in the number of accounts, determine that the target account for tax reduction is null and return an indication that no processing is required.
[0134] In some embodiments, the target exemption account determination unit 504 is further configured to: in response to determining that the category is an increase in the number of accounts and the number of exempted accounts is 0, return exemption account selection prompt information, receive the selected exemption account information, and then determine the account corresponding to the exemption account information as the target exemption account; in response to determining that the category is an increase in the number of accounts and the number of exempted accounts is greater than 0, determine that the target exemption account is a null value and return a no-processing flag.
[0135] In some embodiments, the target exemption account determination unit 504 is further configured to: in response to determining that the category is a decrease in the number of accounts and the number of exempted accounts is 0, determine whether the account included in the unique account system among other accounts is unique; if so, determine the unique account included in the unique account system among other accounts as the target exemption account; otherwise, return exemption account selection prompt information, receive the selected exemption account information, and then determine the account corresponding to the exemption account information as the target exemption account; in response to determining that the category is a decrease in the number of accounts and the number of exempted accounts is greater than 0, determine that the target exemption account is null and return a no-processing flag.
[0136] In some embodiments, the business processing apparatus further includes Figure 5 The update unit, not shown, is configured to set a reduction flag for the target reduction account and update the reduction flag periodically.
[0137] In some embodiments, execution unit 505 is further configured to remove the target waived account from the list of outstanding annual fees and the list of outstanding small account management fees.
[0138] In some embodiments, the business processing apparatus further includes Figure 5 The real-time re-inspection unit (not shown) is configured to: obtain the timestamp of the contract snapshot table on the day the business processing request is executed; filter customers with account changes on the day and all personal deposit debit card accounts under the customer's name based on the timestamp; remove accounts that do not conform to the unique account system from all personal deposit debit card accounts to obtain a unique account list; and remove the corresponding unique accounts from the list of outstanding annual fees and the list of outstanding small account management fees based on the unique account list, and mark the corresponding unique accounts with annual fee reduction and small fee reduction indicators.
[0139] It should be noted that the business processing methods and business processing devices in this application are related in terms of specific implementation content, so repeated content will not be described again.
[0140] Figure 6 An exemplary system architecture 600 is shown that can be applied to the business processing method or business processing apparatus of the embodiments of this application.
[0141] like Figure 6 As shown, system architecture 600 may include terminal devices 601, 602, and 603, a network 604, and a server 605. Network 604 serves as the medium for providing communication links between terminal devices 601, 602, and 603 and server 605. Network 604 may include various connection types, such as wired or wireless communication links or fiber optic cables, etc.
[0142] Users can use terminal devices 601, 602, and 603 to interact with server 605 via network 604 to receive or send messages, etc. Various communication client applications can be installed on terminal devices 601, 602, and 603, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social media platform software, etc. (for example only).
[0143] Terminal devices 601, 602, and 603 can be various electronic devices with business processing screens and support web browsing, including but not limited to smartphones, tablets, laptops, and desktop computers.
[0144] Server 605 can be a server providing various services, such as a backend management server (for example only) that supports business processing requests submitted by users using terminal devices 601, 602, and 603. The backend management server can receive business processing requests, determine the corresponding account and obtain the corresponding account quantity change identifier, and then identify the category of the account quantity change identifier; it calls a preset unique account exclusion model to determine whether the account conforms to the unique account system; otherwise, it returns a no-processing identifier; if so, it determines other accounts corresponding to the account, and then determines whether any of the other accounts conforms to the unique account system; otherwise, it determines the target account for fee reduction based on the category; if so, it determines the number of already-reduced accounts among the other accounts conforming to the unique account system, and determines the target account for fee reduction based on the number of already-reduced accounts and the category; and executes the business processing request to reduce the fees for the target account. By implementing proactive fee waiver strategies based on the category of changes in the number of private accounts (whether the number of accounts increases or decreases), whether they are included in the unique account system, and whether other accounts have already had their fees waived, the system can identify target accounts for fee waivers based on business scenarios and proactively waive account management fees and annual fees for the target accounts (which are also the unique accounts), thus avoiding additional charges to customers.
[0145] It should be noted that the business processing method provided in this application embodiment is generally executed by server 605, and correspondingly, the business processing device is generally set in server 605.
[0146] It should be understood that Figure 6 The number of terminal devices, networks, and servers shown is merely illustrative. Depending on implementation needs, any number of terminal devices, networks, and servers can be included.
[0147] The following is for reference. Figure 7 It shows a schematic diagram of the structure of a computer system 700 suitable for implementing a terminal device according to the embodiments of this application. Figure 7 The terminal device shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of this application.
[0148] like Figure 7 As shown, the computer system 700 includes a central processing unit (CPU) 701, which can perform various appropriate actions and processes based on programs stored in read-only memory (ROM) 702 or programs loaded from storage section 708 into random access memory (RAM) 703. The RAM 703 also stores various programs and data required for the operation of the computer system 700. The CPU 701, ROM 702, and RAM 703 are interconnected via a bus 704. An input / output (I / O) interface 705 is also connected to the bus 704.
[0149] The following components are connected to the I / O interface 705: an input section 706 including a keyboard, mouse, etc.; an output section 707 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 708 including a hard disk, etc.; and a communication section 709 including a network interface card such as a LAN card, modem, etc. The communication section 709 performs communication processing via a network such as the Internet. A drive 710 is also connected to the I / O interface 705 as needed. A removable medium 711, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on the drive 710 as needed so that computer programs read from it can be installed into the storage section 708 as needed.
[0150] Specifically, according to the embodiments disclosed in this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments disclosed in this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 709, and / or installed from removable medium 711. When the computer program is executed by central processing unit (CPU) 701, it performs the functions defined above in the system of this application.
[0151] It should be noted that the computer-readable medium shown in this application can be a computer-readable signal medium or a computer-readable storage medium, or any combination of the two. Computer-readable storage media can be, for example, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to: electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this application, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In this application, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media can also be any computer-readable medium other than computer-readable storage media, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wireless, wire, optical fiber, RF, etc., or any suitable combination thereof.
[0152] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.
[0153] The units described in the embodiments of this application can be implemented in software or hardware. The described units can also be housed in a processor; for example, a processor can be described as including a receiving unit, a first determining unit, a second determining unit, a target exemption account determining unit, and an execution unit. The names of these units do not necessarily limit the specific unit itself.
[0154] In another aspect, this application also provides a computer-readable medium, which may be included in the device described in the above embodiments; or it may exist independently and not assembled into the device. The computer-readable medium carries one or more programs. When the one or more programs are executed by the device, the device receives a service processing request, determines the corresponding account and obtains the corresponding account quantity change identifier, and then identifies the category of the account quantity change identifier; it calls a preset unique account exclusion model to determine whether the account conforms to the unique account system; otherwise, it returns an "no processing required" identifier; if so, it determines other accounts corresponding to the account, and then determines whether any of the other accounts conforms to the unique account system; otherwise, it determines the target account for fee reduction based on the category; if so, it determines the number of already-reduced accounts among the other accounts conforming to the unique account system, and determines the target account for fee reduction based on the number of already-reduced accounts and the category; and it executes the service processing request to reduce the fees of the target account for fee reduction.
[0155] The computer program product of this application includes a computer program that, when executed by a processor, implements the business processing method in the embodiments of this application.
[0156] According to the technical solution of this application embodiment, by determining the category of the change in the number of private accounts (whether the number of accounts increases or decreases), and whether they are included in the unique account system and whether other accounts have already had their fees reduced, the corresponding proactive fee waiver strategy is executed. This enables the determination of the target fee waiver account based on the business scenario, and the proactive waiver of the account management fee and annual fee of the target fee waiver account (which is also the unique account), thus avoiding additional charges to customers.
[0157] The specific embodiments described above do not constitute a limitation on the scope of protection of this application. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can occur depending on design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this application should be included within the scope of protection of this application.
Claims
1. A business processing method, characterized in that, include: The system receives business processing requests, determines the corresponding account change scenario and obtains the corresponding account quantity change identifier, and then identifies the category of the account quantity change identifier. Specifically, the system calls the data warehouse component to perform unique account data screening according to a preset period, obtains the customer account view from the customer information component, and if the customer account is a unique account, it obtains the account's tax reduction status. If the warehouse screens out a unique account but does not set a tax reduction identifier, the system updates the account quantity change identifier. The system calls a preset unique account exclusion model to determine whether the account conforms to the unique account system. If not, it returns a no-processing flag. The preset account exclusion model includes an execution program to verify the uniqueness of the account. When the relevant information of the current changed account is input into the preset unique account exclusion model, the execution entity calls the execution program in the model to verify the uniqueness of the account to determine whether the current changed account is the only account in the corresponding bank and whether there is only one Class I bank card under the current changed account. If so, then identify the other accounts corresponding to the account, and then determine whether there are any accounts among the other accounts that conform to the unique account system; otherwise, determine the target exemption account according to the category. If so, determine the number of accounts that have already received a reduction in fees among other accounts that conform to the unique account system, and determine the target account for the reduction in fees based on the number of accounts that have already received a reduction in fees and the category; Execute the business processing request to reduce or waive the fees for the target account.
2. The method according to claim 1, characterized in that, The process of determining the target account for tax reduction based on the category includes: In response to determining that the category represents an increase in the number of accounts, the account is identified as the target exemption account.
3. The method according to claim 1, characterized in that, The process of determining the target account for tax reduction based on the category includes: In response to determining that the category is a decrease in the number of accounts, the target account for the fee reduction is determined to be null, and a no-processing flag is returned.
4. The method according to claim 1, characterized in that, The step of determining the target account for exemption based on the number of accounts that have already received exemption and the category includes: In response to determining that the category is an increase in the number of accounts and the number of accounts that have already received a discount is 0, a discount account selection prompt is returned, the selected discount account information is received, and then the account corresponding to the discount account information is determined as the target discount account; In response to determining that the category is an increase in the number of accounts and the number of accounts that have already received a discount is greater than 0, the target discount account is determined to be null, and a no-processing flag is returned.
5. The method according to claim 1, characterized in that, The step of determining the target account for exemption based on the number of accounts that have already received exemption and the category includes: In response to determining that the category is a decrease in the number of accounts and the number of accounts that have been exempted is 0, it is determined whether the account included in the unique account system among the other accounts is unique. If so, the unique account included in the unique account system among the other accounts is determined as the target exemption account; otherwise, the exemption account selection prompt information is returned, the selected exemption account information is received, and then the account corresponding to the exemption account information is determined as the target exemption account. In response to determining that the category is a decrease in the number of accounts and that the number of accounts that have already received a discount is greater than 0, the target discount account is determined to be null, and a no-processing flag is returned.
6. The method according to claims 1-5, characterized in that, The method further includes: Set a reduction / exemption identifier for the target account and update the reduction / exemption identifier periodically.
7. The method according to claim 1, characterized in that, The fee reduction process for the target account includes: Remove the target accounts for fee reduction from the list of outstanding annual fees and the list of outstanding small account management fees.
8. The method according to claim 1, characterized in that, After the fee reduction processing is performed on the target account, the method further includes: Obtain the timestamp of the contract snapshot table for the day the business processing request is executed; Based on the timestamp, customers with account changes on that day and all private deposit debit card accounts under those customers are obtained; By removing all private deposit debit card accounts that do not conform to the unique account system, a list of unique accounts is obtained. Based on the list of unique accounts, the corresponding unique accounts are removed from the list of outstanding annual fees and the list of outstanding small account management fees, and the corresponding unique accounts are marked with an annual fee reduction indicator and a small fee reduction indicator.
9. A business processing device, characterized in that, include: The receiving unit is configured to receive business processing requests, determine the corresponding account change scenario and obtain the corresponding account quantity change identifier, and then identify the category of the account quantity change identifier; wherein, according to a preset period, the data warehouse component is called to perform unique account data screening, the customer account view is obtained from the customer information component, if the customer account is a unique account, the account's reduction status is obtained, if the warehouse screens out a unique account but no reduction identifier is set, the account quantity change identifier is updated. The first judgment unit is configured to call a preset unique account exclusion model to determine whether the account conforms to the unique account system. If not, it returns a no-processing flag. The preset account exclusion model includes an execution program to verify the uniqueness of the account. When the relevant information of the current changed account is input into the preset unique account exclusion model, the execution unit calls the execution program in the model to determine whether the current changed account is the only account in the corresponding bank and whether there is only one Class I bank card under the current changed account. The second judgment unit is configured to determine other accounts corresponding to the account if the condition is met, and then determine whether there is an account among the other accounts that conforms to the unique account system; otherwise, the target exemption account is determined according to the category. The target exemption account determination unit is configured to determine the number of exempted accounts among other accounts that conform to the unique account system if the condition is met, and determine the target exemption account based on the number of exempted accounts and the category. The execution unit is configured to execute the business processing request to process the fee reduction for the target account.
10. The apparatus according to claim 9, characterized in that, The second determination unit is further configured to: In response to determining that the category represents an increase in the number of accounts, the account is identified as the target exemption account.
11. The apparatus according to claim 9, characterized in that, The second determination unit is further configured to: In response to determining that the category is a decrease in the number of accounts, the target account for the fee reduction is determined to be null, and a no-processing flag is returned.
12. The apparatus according to claim 11, characterized in that, The target exemption account determination unit is further configured to: In response to determining that the category is an increase in the number of accounts and the number of accounts that have already received a discount is 0, a discount account selection prompt is returned, the selected discount account information is received, and then the account corresponding to the discount account information is determined as the target discount account; In response to determining that the category is an increase in the number of accounts and the number of accounts that have already received a discount is greater than 0, the target discount account is determined to be null, and a no-processing flag is returned.
13. The apparatus according to claim 11, characterized in that, The target exemption account determination unit is further configured to: In response to determining that the category is a decrease in the number of accounts and the number of accounts that have been exempted is 0, it is determined whether the account included in the unique account system among the other accounts is unique. If so, the unique account included in the unique account system among the other accounts is determined as the target exemption account; otherwise, the exemption account selection prompt information is returned, the selected exemption account information is received, and then the account corresponding to the exemption account information is determined as the target exemption account. In response to determining that the category is a decrease in the number of accounts and that the number of accounts that have already received a discount is greater than 0, the target discount account is determined to be null, and a no-processing flag is returned.
14. A business processing electronic device, characterized in that, include: One or more processors; Storage device for storing one or more programs. When the one or more programs are executed by the one or more processors, the one or more processors implement the method as described in any one of claims 1-8.
15. A computer-readable medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the method as described in any one of claims 1-8.
16. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the method as described in any one of claims 1-8.
Citation Information
Patent Citations
Wireless router smart home managing method and wireless router
CN106022758A
Bank self-service screen locking system based on face recognition
CN111862488A