Member grade preservation calculation method and related equipment

Abstract

The invention provides a member level preservation calculation method and related equipment, and relates to the technical field of Internet e-commerce. According to the method, the security calculation automation is realized through a closed-loop process of task automatic generation, multi-source data pulling, rule matching calculation and level state updating. The method comprises the following steps: firstly, generating a target member preservation task comprising a member ID, a current grade and preservation deadline according to a preset member grade preservation period; then extracting basic information, consumption data and point data of the target member in a preservation period from a member database, an order system and a point system to form a complete data set; matching a corresponding preservation rule according to the current grade of the target member, and performing Boolean value calculation on the data set to judge a preservation result; and finally, updating the member grade and the validity period of the target member according to the preservation result, and completing the preservation whole-process processing.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of Internet e-commerce, in particular to a member level maintenance calculation method and related equipment. BACKGROUND

[0002] With the fine development of enterprise member system, member level as the core means to improve user stickiness and consumption willingness, its maintenance management has become a key link of member operation. In the current enterprise-level member management system, member level maintenance mainly relies on the mode of manual periodic verification and fixed rule calculation.

[0003] The operation personnel need to manually select the members to be maintained according to the maintenance period (such as annual), extract the consumption records from the member database or order system, and then judge whether the members meet the maintenance conditions by comparing the maintenance rules. Finally, the member level state is manually updated and the user is notified.

[0004] The formation of such a mode is due to the early business scenario of small number of members and simple maintenance rules. At that time, manual processing can meet the basic needs. However, with the explosive growth of member scale in new energy, retail, service and other industries, and the evolution of maintenance rules to multi-dimensional combination and dynamic period, the traditional mode gradually cannot adapt to the development needs of the business. SUMMARY

[0005] Based on the above problems, the present application provides a member level maintenance calculation method and equipment.

[0006] The embodiments of the present application disclose the following technical solutions:

[0007] In a first aspect, the embodiments of the present application provide a member level maintenance calculation method, which comprises:

[0008] According to the preset maintenance period of the member level, a maintenance task corresponding to the target member is generated; the maintenance task includes member ID, member level and maintenance deadline;

[0009] Pull the data set of the target member within the maintenance period from the member database, order system and credit system; the data set includes basic information, consumption data and credit data;

[0010] Based on the maintenance rule matched with the current member level of the target member, the data set is subjected to Boolean value calculation to obtain a maintenance result;

[0011] According to the maintenance result, the member level and member validity period corresponding to the target member are updated.

[0012] In a possible implementation manner, the updating of the member level and member validity period corresponding to the target member according to the maintenance result comprises:

[0013] If the retention result represents that the target member satisfies the retention rule, keeping the current membership level of the target member and resetting the membership validity period;

[0014] If the retention result represents that the target member does not satisfy the retention rule, updating the membership level and the membership validity period of the target member in combination with the retention strategy.

[0015] In a possible implementation, the retention strategy includes a re-computation strategy and a step-by-step degradation strategy; and the updating the membership level and the membership validity period of the target member in combination with the retention strategy includes:

[0016] If the retention result meets the re-computation strategy, re-computing the membership level of the target member according to the order range and the point range indicated by the re-computation strategy, and resetting the membership validity period;

[0017] If the retention result meets the step-by-step degradation strategy, downgrading the membership level of the target member by one level, and resetting the membership validity period.

[0018] In a possible implementation, the pulling the data set of the target member in the retention period includes:

[0019] When the data set is pulled, if the data set pulling fails, triggering an automatic retry mechanism; the retry number of the automatic retry mechanism is preset as N times; N is an integer greater than or equal to 1;

[0020] If the data set fails to be pulled for N times, marking the retention task as to be manually processed, and recording the failure reason.

[0021] In a possible implementation, after the data set is obtained, the method further includes:

[0022] cleaning and formatting the basic information, the consumption data and the point data, eliminating invalid data and unifying the data format to obtain a standardized data set; the invalid data includes repeated consumption records or records with abnormal point values.

[0023] In a possible implementation, after the retention task is created, the retention task enters a task queue and is marked as to be processed;

[0024] The method further includes:

[0025] monitoring the number of retention tasks in the task queue that are to be processed in real time, and adjusting the number of task processing threads according to the number of the retention tasks that are to be processed;

[0026] in a case where the number of the level-maintenance tasks to be processed is greater than or equal to a preset threshold, increasing the number of processing threads;

[0027] in a case where the number of the level-maintenance tasks to be processed is less than the preset threshold, decreasing the number of processing threads.

[0028] In a possible implementation, the method further includes:

[0029] after updating the member level and the member validity period of the target member, pushing a level-maintenance result to the target member through in-site notification and off-site notification.

[0030] In a second aspect, the embodiments of the present application disclose a member level-maintenance computing device, and the device includes:

[0031] a generating module configured to generate a level-maintenance task corresponding to a target member according to a preset level-maintenance period of a member level; the level-maintenance task includes a member ID, a current level and a level-maintenance deadline;

[0032] an obtaining module configured to pull a data set of the target member in the level-maintenance period from a member database, an order system and a point system; the data set includes basic information, consumption data and point data;

[0033] a computing module configured to perform Boolean value calculation on the data set based on a level-maintenance rule matched by a current member level of the target member to obtain a level-maintenance result;

[0034] an updating module configured to update a member level and a member validity period corresponding to the target member according to the level-maintenance result.

[0035] In a possible implementation, the updating module is specifically configured to, if the level-maintenance result represents that the target member satisfies the level-maintenance rule, maintain the current member level of the target member and reset the member validity period; and if the level-maintenance result represents that the target member does not satisfy the level-maintenance rule, update the member level and the member validity period of the target member in combination with the level-maintenance strategy.

[0036] In a possible implementation, the level-maintenance strategy includes a re-computation strategy and a step-by-step demotion strategy.

[0037] The updating module is specifically configured to, in a case where the level-maintenance result meets the re-computation strategy, re-compute the member level of the target member according to an order range and a point range indicated by the re-computation strategy and reset the member validity period; and in a case where the level-maintenance result meets the step-by-step demotion strategy, lower the member level of the target member by one level and reset the member validity period.

[0038] In a possible implementation, the obtaining module is specifically configured to, when the data set is pulled, trigger an automatic retry mechanism if the data set fails to be pulled; the number of retries of the automatic retry mechanism is preset as N times; N is an integer greater than or equal to 1; if the data set fails to be pulled for N times, the level maintenance task is marked as to be manually processed, and a failure reason is recorded.

[0039] In a possible implementation, after the data set is obtained, the obtaining module is further configured to clean and format the basic information, the consumption data and the integral data, eliminate invalid data and unify data formats to obtain a standardized data set; the invalid data includes repeated consumption records or records with abnormal integral values.

[0040] In a possible implementation, after the level maintenance task is created, the level maintenance task enters a task queue and is marked as to be processed.

[0041] The device further includes a thread management module configured to monitor the number of level maintenance tasks to be processed in the task queue in real time, and adjust the number of task processing threads according to the number of level maintenance tasks to be processed; in a case where the number of level maintenance tasks to be processed is greater than or equal to a preset threshold, the number of processing threads is increased; in a case where the number of level maintenance tasks to be processed is less than the preset threshold, the number of processing threads is reduced.

[0042] In a possible implementation, the updating module is further configured to, after updating the member level and the member validity period of the target member, push the level maintenance result to the target member through in-site notification and off-site notification.

[0043] In a third aspect, the embodiments of the present application disclose a control device, including a processor and a memory, the memory is used for storing programs, instructions or codes, and the processor is used for executing the programs, instructions or codes in the memory to complete the member level maintenance calculation method in any one of the first aspect.

[0044] In a fourth aspect, the embodiments of the present application disclose a computer readable storage medium, characterized in that a computer program is stored, the computer program is loaded by a processor to execute the member level maintenance calculation method in any one of the first aspect.

[0045] The application provides a member level retention calculation method and related equipment. The method realizes retention calculation automation through a closed-loop process of task automatic generation, multi-source data pulling, rule matching calculation, and level state updating. First, according to a preset member level retention period, a target member retention task including a member ID, a current level, and a retention deadline is generated. Then, the basic information, consumption data, and points data of the target member within the retention period are extracted from the member database, the order system, and the points system to form a complete data set. Then, according to the corresponding retention rules matched with the current level of the target member, the data set is calculated to determine the retention result. Finally, the member level and the validity period of the target member are updated according to the retention result, and the whole process of retention is completed. BRIEF DESCRIPTION OF DRAWINGS

[0046] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the drawings needed to be used in the embodiments or the prior art description will be briefly introduced. Obviously, the drawings in the following description are only some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative labor.

[0047] Figure 1 A flowchart of a member level retention calculation method provided by an embodiment of the present application;

[0048] Figure 2 A schematic diagram of a retention task generation provided by an embodiment of the present application;

[0049] Figure 3 A flowchart of a retention calculation provided by an embodiment of the present application;

[0050] Figure 4 A schematic diagram of a member level retention calculation device provided by an embodiment of the present application. DETAILED DESCRIPTION

[0051] In the modern enterprise member management system, member level retention is a key operation link to maintain user stickiness and improve user life cycle value. Currently, the mainstream member level retention management in the industry still relies on manual guidance, and multi-source data needs to be manually integrated. This mode can meet the basic needs in the early business scenarios with fewer members and simple retention rules. However, with the rapid development of retail, e-commerce, and service industries, the enterprise member scale is growing explosively. When facing large-scale members and multi-dimensional rules, the efficiency is low and errors are easy to occur, and there is obvious delay in retention results and level updates.

[0052] To solve the technical problem, the embodiment of the present application provides a member level maintenance calculation method and related equipment. The method realizes the automation of level maintenance calculation through the closed-loop process of task automatic generation, multi-source data pulling, rule matching calculation and level state updating. First, according to the preset member level maintenance period, a target member maintenance task including member ID, current level and maintenance deadline is generated; then the basic information, consumption data and points data of the target member in the maintenance period are extracted from the member database, order system and points system to form a complete data set; then the corresponding maintenance rules are matched according to the current level of the target member, and the data set is calculated by Boolean value to determine the maintenance result; finally, the member level and validity period of the target member are updated according to the maintenance result, and the whole process of maintenance is completed.

[0053] The embodiment of the present application solves the core pain points of the existing artificial maintenance mode. The embodiment of the present application replaces the tedious operation of manual screening of members and manual integration of data through automatic generation of maintenance tasks and automatic pulling of multi-source data, greatly reduces the labor cost, avoids data omission and calculation errors caused by manual operation, and improves the processing efficiency and accuracy of maintenance. And, based on the matching of the current level of the member and the maintenance rules and the Boolean value calculation, it is ensured that the maintenance judgment strictly conforms to the corresponding level standard, and the confusion of rule application is avoided. In addition, the maintenance result is directly related to the level and validity period update, realizing the real-time synchronization of the maintenance result to the member state, solving the problem of level update delay in the traditional mode, ensuring that the member knows the level state in time, and improving the intelligent and standardized level of member management.

[0054] In order to enable the personnel in the technical field to better understand the present application scheme, the technical scheme in the embodiment of the present application will be described clearly and completely in combination with the drawings in the embodiment of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, not all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by the person skilled in the art without creative labor are within the scope of protection of the present application.

[0055] The member level retention calculation method provided by the embodiments of the present application is widely applicable to multi-industry scenarios that require fine member operation, have a large number of members, and have complex retention rules. For example, retail and chain supermarkets can automatically integrate offline POS and online order data, solve the problem of missing scattered consumption record statistics, complete multi-dimensional retention judgment according to the period to improve the retention of high-value members; e-commerce platforms (general e-commerce and vertical e-commerce) can batch process retention tasks for tens of millions or even hundreds of millions of members, quickly respond to dynamically adjusted retention rules during large promotions, and avoid the misissuance of benefits caused by delayed level updates after large promotions; service industries (chain hotels, travel and tourism scenic spots, and chain gyms) can integrate reservation, check-in, or check-in record data to ensure that member level benefits are consistent when consuming across stores and ensure the accuracy of retention in periodic consumption scenarios; financial and payment industries (bank credit card centers and third-party payment platforms) can pull compliant data in an encrypted environment to achieve traceable retention calculation that meets financial regulatory requirements, avoid security risks of manually processing sensitive financial data, and overall meet the core needs of member retention automation, precision, and efficiency in different industries.

[0056] The implementation hardware of the present solution needs to meet the needs of efficient pulling of multi-source data, parallel processing of batch tasks, and secure storage of data. The data acquisition layer hardware can use a data gateway server or an edge acquisition terminal, the computing layer hardware can use a task scheduling computing server cluster or a GPU acceleration card, and the data storage layer hardware can use a relational database server or a distributed file storage system.

[0057] The execution subject of the method can be a server, a desktop computer, or other electronic devices capable of performing calculations. In the following, electronic devices are taken as the execution subject for introduction, see Figure 1 , Figure 1 A flowchart of a member level retention calculation method provided by the embodiments of the present application is shown in the figure. The method includes:

[0058] S101: The electronic device generates a retention task corresponding to a target member according to a pre-set retention period of the member level.

[0059] The retention period of the member level refers to the time range that the enterprise pre-sets for judging whether different levels of members need to be retained according to the member operation strategy. The retention period supports unified configuration, such as all members being set as a retention period of 365 days; the retention period also supports configuration by level, such as a VIP1 member having a retention period of 180 days and VIP2 and above members having a retention period of 365 days. The retention period can be pre-stored in a rule database accessible by the electronic device.

[0060] Target member refers to the member screened by the electronic device, which needs to be judged for the current level maintenance period. Usually, it is the member who has reached the level maintenance period threshold since the last level change time, or the member whose current level validity period is about to expire. The electronic device determines the target member range by screening the level validity period field in the member database.

[0061] Level maintenance task is a task unit generated by the electronic device for the target member, which includes the key information required for level maintenance calculation. The level maintenance task is used to determine which member, at what level, and at what time to complete the level maintenance judgment. The level maintenance task includes member ID, member level, and level maintenance deadline. Member ID is the unique identifier of the member in the system, used to associate multiple system data. Member level refers to the member level at the beginning of the target member's level maintenance period. Level maintenance deadline refers to the last time to complete the level maintenance judgment and update the level, which is calculated by adding the period length to the level maintenance period start time.

[0062] The electronic device preloads the level maintenance period configuration, reads the level maintenance period corresponding to each level from the rule database, and triggers the level maintenance task generation logic at a preset frequency. If the level maintenance period is configured by member level, the electronic device can trigger separately according to the period threshold of different member levels, such as triggering VIP1 member once every 180 days and VIP2 member once every 365 days.

[0063] After triggering the level maintenance task generation logic, the electronic device can access the member database through SQL query statements to screen target members. As an example, the screening condition is "current time ≥ last level change time + level maintenance period - preset buffer period", and members who have been cancelled or frozen are excluded. The buffer period is used to start level maintenance calculation in advance to avoid not being completed before the deadline. For example, if the level maintenance period of VIP2 member is 365 days, the last level change time of a member is January 1, 2023, and the current time is December 25, 2023, there are still 7 days to the end of the period, then the member is screened as a target member.

[0064] The electronic device automatically generates a level maintenance task for each screened target member. The electronic device extracts the member ID and member level of the member from the member database, calculates the level maintenance deadline based on the level maintenance period, and encapsulates the three as structured task data. If there is a special scenario, such as the member upgrading the level during the level maintenance period, the electronic device will read the latest level change record first to ensure that the period and the level match.

[0065] The generated level maintenance task is stored in the task queue, and the electronic device initializes the task state to pending and records the task generation time. The task queue supports prioritizing by member level, such as processing high-level member tasks first, which provides a task scheduling basis for subsequent data pulling and rule calculation steps.

[0066] In the member level maintenance calculation process, the electronic device needs to generate maintenance tasks, monitor the task queue in real time, and dynamically adjust the number of processing threads to ensure efficient processing of maintenance tasks and avoid task backlog or resource waste.

[0067] In a possible implementation, the electronic device monitors the number of maintenance tasks in the task queue in real time, and adjusts the number of task processing threads according to the number of maintenance tasks in the task queue.

[0068] If the number of maintenance tasks in the task queue is greater than or equal to the preset threshold, the electronic device increases the number of processing threads; if the number of maintenance tasks in the task queue is less than the preset threshold, the electronic device reduces the number of processing threads.

[0069] The task queue is a buffer queue for storing maintenance tasks to be processed, such as a Redis-based List structure or a RabbitMQ message queue. All maintenance tasks in the initial state are in the queue in the order of generation time or priority, waiting for the processing thread to call and execute.

[0070] The preset threshold refers to the critical value of the number of tasks in the electronic device that triggers the adjustment of the number of threads. It can be determined by the enterprise according to historical task processing efficiency and hardware resources.

[0071] The number of task processing threads is the number of concurrent threads in the electronic device for executing maintenance tasks. The initial number of threads is usually set to 1-2 times the number of hardware CPU cores, such as 8-core CPU with an initial thread number of 8. The number of threads is adjusted through the thread pool management module of the electronic device.

[0072] The electronic device starts the thread pool management module at the same time, and starts a separate queue monitoring thread. The queue monitoring thread sends a query request to the task queue at a preset frequency to obtain the number of maintenance tasks to be processed. For example, if the task queue is a Redis List, the queue monitoring thread queries the queue length through the LLEN key command, and synchronizes the number of tasks to the thread pool management module in real time.

[0073] After receiving the number of tasks from the monitoring thread, the thread pool management module compares it with the preset threshold. If the number of tasks to be processed is greater than or equal to the preset threshold, it is determined that the task queue is at risk of backlog, and the number of processing threads needs to be increased to improve the concurrent processing capability. The increase in the number of threads is determined according to a preset rule, for example, the current number of threads is increased by 50% each time, and the maximum number of threads in the thread pool is not exceeded to avoid overloading of hardware resources.

[0074] If the number of tasks to be processed is less than a preset threshold, it is determined that the current processing thread is idle. In this case, the number of processing threads should be reduced to save CPU and memory resources. The reduction in the number of threads is also executed according to preset rules, such as reducing the current number of threads by 20% each time, but not less than the core number of threads in the thread pool, to ensure basic processing capacity.

[0075] Based on the assessment results, the thread pool management module adjusts the number of processing threads via the thread pool API. After adjustment, the module records information such as the thread adjustment time, the number of threads before and after the adjustment, and the current number of tasks to be processed, storing this information in the system log for future maintenance personnel to trace the reasons for the adjustment. Simultaneously, the monitoring thread continues to query the task queue at regular intervals to ensure that the task queue is always in a highly efficient processing state.

[0076] like Figure 2 As shown in this embodiment, when providing a membership level retention calculation service, the electronic device can query and parse the level rules to determine the retention period corresponding to each membership level. Then, the electronic device queries the target members who need to undergo level retention calculation and generates retention tasks for the target members. Alternatively, in another implementation, the electronic device can also provide a level upgrade calculation service and generate retention tasks corresponding to level upgrades.

[0077] S102: Electronic devices retrieve the target member's dataset during the retention period from the member database, order system, and points system.

[0078] The member database is a structured database that stores basic member information and serves as the core storage medium for member identity and level information. The member database includes basic data such as each member's member ID, member level, and level change history.

[0079] The order system refers to the business system that records members' consumption transactions. It can store data such as order number, order time, consumption amount, product category and order status. It is the core source of consumption data. Electronic devices use this system to filter the valid consumption records of target members within the retention period.

[0080] The points system refers to a dedicated system for managing the generation, consumption, and balance of member points. It can store data such as the time of point acquisition, the source of points, the value of points, and the validity period of points. It is a key system for extracting points data and ensuring the accuracy of points-related conditions in the calculation of membership level.

[0081] The dataset includes basic information, consumption data, and points data. Basic information includes member IDs.

[0082] After the processing thread of the electronic device obtains the to-be-processed membership level maintenance task from the task queue, the core parameters in the task are disassembled. The membership ID is taken as the unique association identifier for data pulling, the time period indicated by the membership level maintenance period is taken as the time filtering condition, and the data fields to be pulled by each system are determined. The electronic device initiates parallel data requests to the membership database, the order system and the point system through the preset interface adaptation module, so as to avoid efficiency loss caused by serial pulling. After the electronic device obtains the data of multiple systems, the data preprocessing module is started for integration. The integrated data set is stored in the temporary data cache of the electronic device and is associated with the corresponding membership level maintenance task, so as to facilitate direct calling in the subsequent steps. Meanwhile, the electronic device records log information such as data pulling completion time and data pulling time consumption of each system, so as to provide a basis for subsequent task monitoring and exception troubleshooting.

[0083] When the electronic device pulls the data set in step S102, the electronic device can also process the data pulling failure scenario. In one possible implementation, when the electronic device pulls the data set, if the data set pulling fails, an automatic retry mechanism is triggered. The number of retries of the automatic retry mechanism is preset to N times. N is an integer greater than or equal to 1. If the data set fails to be pulled for N times, the membership level maintenance task is marked as to be manually processed, and the failure reason is recorded.

[0084] When the electronic device initiates a data request to the membership database, the order system and the point system, the request timeout time is set synchronously. If no return data is received after the timeout, or a non-business error response such as network connection rejection or system internal error is received, it is determined that the data set pulling fails, and the automatic retry mechanism is triggered immediately.

[0085] The electronic device reads the preset number of retries N from the configuration file and initializes the current retry count to 1. Before each retry, it is first determined whether the current count is ≤N. If yes, the retry is initiated, and the count is incremented by 1 after the retry. In order to avoid high-frequency retries in a short time from increasing the load of the target system, the electronic device can set an exponential backoff interval between two retries, such as 1 second for the first retry, 2 seconds for the second retry, and 4 seconds for the third retry, to balance the retry efficiency and system pressure. If only a single system fails to pull, the electronic device only initiates a retry for the system, without re-pulling other systems that have successfully obtained data, thereby reducing invalid data requests and saving resources.

[0086] If a retry is successful, the automatic retry mechanism is terminated, and the electronic device continues to execute the subsequent data integration process to complete the data set construction according to the normal logic. If the retry count reaches N and the pulling is still unsuccessful, the automatic retry is stopped, and the exception processing is entered. The electronic device updates the state of the membership level maintenance task from to-be-processed to to-be-manually-processed, and transfers the task to a special exception task pool. Meanwhile, the log module records the failure reason and the name of the failed system in detail, and the log information is stored in the persistent log system synchronously, to support subsequent query and traceability.

[0087] To improve the quality of the data set and avoid invalid data interference with the level retention result judgment, the electronic device will also perform data cleaning on the data set after obtaining the data set. The specific process includes:

[0088] The electronic device cleans and formats the basic information, consumption data and points data, eliminates invalid data and unifies the data format to obtain a standardized data set. Invalid data includes duplicate consumption records or records with abnormal points values.

[0089] After the electronic device pulls the data set of the target member, it starts the data cleaning module to eliminate invalid data. For consumption data, the electronic device uses order number as the unique identifier to remove duplicate records and filter non-completed orders through a hash table. For points data, the electronic device sets a reasonable value range according to enterprise points rules, and eliminates abnormal points records and invalid activity points with negative values or exceeding the upper limit. For basic information, the electronic device checks the integrity and format legality of key fields such as member ID and current level, and triggers data re-pulling if the fields are abnormal. If re-pulling fails, it is marked as pending manual processing.

[0090] Then it enters the data formatting stage, mapping field names from different systems to standard names to avoid confusion between formats and fields. Finally, it performs standardization verification to check whether the data set includes key fields such as member ID, cumulative consumption amount and available points to ensure completeness, and verifies the logical consistency of cumulative consumption amount and points summary data. If the verification is passed, the standardized data set is stored in the calculation cache associated with the level retention task ID for subsequent rule calculation; if the verification fails, the task is marked as pending manual processing and the reason is recorded, triggering an alarm notification.

[0091] S103: The electronic device performs Boolean value calculation on the data set based on the level retention rule matched by the target member's current member level to obtain the level retention result.

[0092] Different member levels match different level retention rules, in other words, member level and level retention rule are one-to-one correspondence. The electronic device matches the level retention judgment standard exclusive to the level from the rule database according to the current level of the target member, which is the core basis for level retention calculation. The level retention rule is composed of condition type and logic combination, including order conditions (such as the number of orders with cumulative consumption amount ≥3000 yuan or single consumption ≥500 yuan in the level retention period ≥3) and non-order conditions (such as cumulative available points 2000 points or single activity points ≥500 points in the level retention period), and supports AND / OR logic combination. Rule parameters are pre-configured by operation personnel and stored in the rule database.

[0093] Boolean value calculation refers to that the electronic device compares the corresponding data in the standardized data set against each condition in the retention rules, outputs a binary result of satisfaction or dissatisfaction, and then performs logical operations on the Boolean values of multiple conditions according to the logical combination relationship preset in the rules, to finally obtain a comprehensive judgment result of whether the retention basic requirement is met. It is the core calculation action of associating data with rules.

[0094] The electronic device first initiates a query request to the rule database according to the current level of the target member in the retention task, and obtains the retention rule content corresponding to the level; then starts the rule analysis module to disassemble the structured rule content into condition units and logical relationships.

[0095] The electronic device traverses each condition unit after disassembly, extracts the corresponding field data from the standardized data set, compares it with the condition threshold, and outputs the Boolean value result of the single condition. The electronic device calculates respectively for order conditions and non-order conditions. After completing the Boolean value calculation of each condition, the electronic device records the condition name, the corresponding field value of the data set, the threshold value and the Boolean value result, to provide a basis for subsequent result tracing.

[0096] The electronic device performs logical operations on the Boolean values of all single conditions according to the logical combination relationship preset in the retention rules, to obtain a comprehensive judgment result. If the retention rule only contains a single condition, the Boolean value of the condition is directly taken as the comprehensive result; if the rule contains nested logic, the logical operations are performed in turn according to the nesting level to ensure the accuracy of the logic.

[0097] The electronic device preliminarily determines the retention result according to the comprehensive result of the multi-condition logical operation. If the retention result is True, it is preliminarily determined that the retention basic requirement is met and the retention is successful; if the retention result is False, it is preliminarily determined that the retention basic requirement is not met and the downgrade strategy needs to be executed. Then, the electronic device associates the preliminary retention result, the Boolean value of each condition, the logical operation process and other information with the retention task and stores them to the calculation result cache, and records the rule version number to provide a basis for the subsequent step S104 of retention strategy execution. If a rule parsing error or a missing data field occurs during the operation process, the retention task is marked as a calculation exception, an alarm is triggered and manual intervention is waited.

[0098] S104: The electronic device updates the member level and the member validity period corresponding to the target member according to the retention result.

[0099] The retention result includes two core situations, one is retention success, that is, the member meets the current level retention rule and maintains the existing level; the other is retention failure, that is, the member does not meet the retention rule and needs to adjust the level according to the preset retention strategy, such as being downgraded to the next level or being re-operated to match a new level.

[0100] The electronic device first reads the retention result from the calculation result cache to determine the level adjustment direction. If the retention result is a retention success, the level adjustment scheme is directly determined as maintaining the current level, the level identifier does not need to be changed, and only the validity period needs to be extended. If the retention result is a retention failure, the adjustment mode is further determined according to the retention strategy corresponding to the member level. The electronic device performs the member level and member validity period adjustment operation through the update interface of the member database.

[0101] The calculation of the member validity period needs to be combined with the retention period corresponding to the current level of the member. The electronic device queries the retention period corresponding to the final level of the target member from the rule database; the new validity period is obtained by taking the level update time as the starting time and superimposing the retention period. If the level is permanently valid, the validity period field is set to a preset maximum value. If the member has a level upgrade record within the retention period, the validity period is recalculated based on the retention period corresponding to the upgraded level, and the original validity period is overwritten.

[0102] In one possible implementation, if the retention result indicates that the target member meets the retention rules, the electronic device maintains the current member level of the target member and resets the member validity period. If the retention result indicates that the target member does not meet the retention rules, the electronic device updates the member level and the member validity period of the target member in combination with the retention strategy.

[0103] The retention strategy is a level adjustment rule preset by the enterprise for different member levels when the member does not meet the retention rules. Resetting the member validity period means recalculating and extending the validity period based on the current level corresponding to the retention period, starting from the completion time of this retention calculation, and overwriting the original expiration time to ensure that the member level rights and interests remain valid.

[0104] After the electronic device reads the retention result, it performs member level and validity period updates in different scenarios. If the retention result indicates that the retention rules are met, the electronic device maintains the current level of the target member unchanged, obtains the retention period corresponding to the level from the rule database, and recalculates the validity period starting from the completion time of this retention calculation. If the retention result indicates that the retention rules are not met, the electronic device first queries the retention strategy bound to the current level, and adjusts the member level and updates the member validity period in combination with the retention strategy. After the update is completed, the electronic device synchronizes the latest information to the member center, the right and benefit issuing system, generates a log containing the state before and after the update, the retention result, and the strategy type, and stores it, and updates the retention task state to completed, completing the whole process closed loop.

[0105] In one possible implementation, the retention strategy includes a re-computation strategy and a step-by-step downgrade strategy.

[0106] In the case that the retention result meets the re-calculation strategy, the electronic device recalculates the member level of the target member according to the order range and the point range indicated by the re-calculation strategy, and resets the member validity period. In the case that the retention result meets the step-by-step degradation strategy, the electronic device downgrades the member level of the target member by one level, and resets the member validity period.

[0107] The re-calculation strategy is one of the core types of the retention strategy, which means that when the target member does not meet the retention rule of the current member level, the electronic device does not directly downgrade the level, but reextracts and verifies the corresponding data in the standardized data set according to the order range and the point range preset by the re-calculation strategy, and then traverses the retention rules of all levels of members, matches the highest level that can be met by the actual data of the member, and finally takes the matched level as the retention adjustment rule of the new level of the member. By matching the optimal level with the current actual data, it is avoided to downgrade excessively due to not meeting the retention requirement of the original level, and it is ensured that the level is accurately matched with the actual consumption and point contribution of the member.

[0108] The step-by-step degradation strategy is another core type of the retention strategy, which means that when the target member does not meet the retention rule of the current member level, the electronic device does not need to re-match the retention rules of all levels, but directly downgrades the current level of the member by one level according to the preset level order of the member level system. This strategy does not set additional data verification conditions, and only takes not meeting the retention rule of the original level as the only trigger condition. After degradation, the validity period is reset according to the retention period corresponding to the new level. The rule is simple and the execution is efficient, and it is suitable for operation scenarios that want to encourage members to continue consuming through an explicit degradation mechanism.

[0109] When the electronic device determines that the target member does not meet the retention rule, it first matches the retention strategy corresponding to the current level from the rule database, and performs the update in two categories. If the re-calculation strategy is matched, the electronic device will re-verify the standardized data set according to the order range and the point range preset by the strategy, match the highest level that can be met by the member, and take the level update time as the starting point to reset the validity period according to the retention period of the new level. If the step-by-step degradation strategy is matched, the current level of the member is directly downgraded by one level, and the degradation completion time is taken as the starting point to reset the validity period according to the retention period corresponding to the new level. After the execution of the two strategies, the level and the validity period information of the member database and the associated system are updated synchronously, the strategy execution log is generated, and the task is marked as completed.

[0110] In one possible implementation, after updating the member level and the member validity period of the target member, the electronic device pushes the retention result to the target member through in-site notification and off-site notification.

[0111] The in-station notification refers to a notification mode of pushing the level maintenance result to the target member through an enterprise self-owned platform or system, and the notification is directly displayed on the personal center, message center and other exclusive panels after the member logs in, without relying on external communication channels, so as to ensure that the member can view the notification in time when using the platform service. The out-station notification refers to a notification mode of pushing the level maintenance result to the target member by means of a third-party communication channel, and the core covers the reach scenario when the member does not log in the platform.

[0112] After the electronic device completes the target member level and the effective period update, the notification pushing process is started. The electronic device first generates the standardized notification content according to the level maintenance result, and the notification content clearly contains the current level of the member, the new effective period, the result description and the benefit related prompt, such as the benefit continuation description of the level maintenance success and the upgrade path guidance after the level reduction. Then, the in-station and out-station double-channel pushing is triggered synchronously. The in-station pushes the notification through the platform personal center and the message center and marks the unread state, reminding the member to log in and view the notification. The out-station preferentially sends the short message to the member's reserved mobile phone number. At the same time, for the member who has bound the APP pushing permission, the pop-up window pushing and the public number template message are triggered synchronously, so as to ensure the multi-scene reach. After the pushing is completed, the electronic device records the pushing state, the pushing time and the failure reason of each channel, triggers the re-pushing mechanism for the failed channel, and stores the pushing record and the level maintenance whole process log in association, so as to facilitate the subsequent verification and member consultation response.

[0113] In order to facilitate the understanding of the member level maintenance calculation method provided in the embodiments of the present application, the following will introduce the method in combination with Figure 3 the above-mentioned technical scheme.

[0114] As shown in Figure 3 , after triggering the level maintenance calculation service, the electronic device can query and analyze the level rules to determine the level maintenance period corresponding to each member level. Then, the electronic device executes the level maintenance task in the task queue, and queries the member information of the target member according to the member ID in the level maintenance task, and then obtains the data set of the target member. The electronic device calculates the level maintenance result in combination with the data set and the level maintenance rules, and finally, the electronic device updates the member level and the member effective period of the target member in combination with the level maintenance result and the level maintenance strategy, and records the level log.

[0115] Based on the above-mentioned embodiments, the embodiments of the present application also provide a member level maintenance calculation device, as shown in Figure 4 , the device comprises:

[0116] The generating module 401 is configured to generate the level maintenance task corresponding to the target member according to the preset level maintenance period of the member level; the level maintenance task comprises a member ID, a current level and a level maintenance deadline;

[0117] The acquisition module 402 is configured to pull a data set of the target member in a retention period from a member database, an order system, and a point system; the data set includes basic information, consumption data, and point data;

[0118] The calculation module 403 is configured to perform Boolean value calculation on the data set based on a retention rule matched with a current member level of the target member to obtain a retention result;

[0119] The update module 404 is configured to update a member level and a member validity period corresponding to the target member according to the retention result.

[0120] In a possible implementation, the update module 404 is specifically configured to, if the retention result indicates that the target member satisfies the retention rule, maintain the current member level of the target member and reset the member validity period; and if the retention result indicates that the target member does not satisfy the retention rule, update the member level and the member validity period of the target member in combination with the retention strategy.

[0121] In a possible implementation, the retention strategy includes a re-computation strategy and a step-by-step demotion strategy.

[0122] The update module 404 is specifically configured to, if the retention result meets the re-computation strategy, re-compute the member level of the target member according to an order range and a point range indicated by the re-computation strategy and reset the member validity period; and if the retention result meets the step-by-step demotion strategy, lower the member level of the target member by one level and reset the member validity period.

[0123] In a possible implementation, the acquisition module 402 is specifically configured to, when pulling the data set, trigger an automatic retry mechanism if the data set fails to be pulled; a retry number of the automatic retry mechanism is preset as N times; N is an integer greater than or equal to 1; if the data set fails to be pulled for N times, the retention task is marked as to be manually processed, and a failure reason is recorded.

[0124] In a possible implementation, after the data set is acquired, the acquisition module 402 is further configured to clean and format the basic information, the consumption data, and the point data, eliminate invalid data, and unify a data format to obtain a standardized data set; the invalid data includes repeated consumption records or records with abnormal point values.

[0125] In a possible implementation, the retention task is created and enters a task queue and is marked as to be processed after being created.

[0126] The device also comprises a thread management module, which is configured to monitor the number of the level-keeping tasks in the task queue in real time, and adjust the number of the task processing threads according to the number of the level-keeping tasks in the task queue; increase the number of the processing threads when the number of the level-keeping tasks in the task queue is greater than or equal to a preset threshold; and decrease the number of the processing threads when the number of the level-keeping tasks in the task queue is less than the preset threshold.

[0127] In a possible implementation, the updating module 404 is further configured to, after updating the member level and the member validity period of the target member, push the level-keeping result to the target member through in-site notification and off-site notification.

[0128] Embodiments of the present application further provide a control device. The control device can comprise a memory and a processor. The processor is configured to execute the member level keeping calculation method of any of the above embodiments. The memory can be a random access memory (RAM), a flash memory, a read only memory (ROM), a non-volatile read only memory (Electronic Programmable ROM, EPROM), a register, a hard disk, a removable disk, etc.

[0129] The memory can store computer instructions, and when the computer instructions stored in the memory are executed by the processor, the processor can be configured to execute the member level keeping calculation method. The memory can also store data.

[0130] In the above embodiments, all or part of the embodiments can be implemented by software, hardware, firmware or any combination thereof. When implemented by software, all or part of the embodiments can be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions according to the embodiments of the present application are generated. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center through wired (for example, coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (for example, infrared, wireless, microwave, etc.) mode. The computer readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. integrated with one or more available media. The available media can be magnetic media (for example, floppy disk, hard disk, magnetic tape), or semiconductor media (for example, solid state disk (SSD)) and the like.

[0131] The embodiments of the present application also provide a readable storage medium for storing the method provided by the above embodiments. For example, RAM, flash memory, ROM, EPROM, register, hard disk, removable disk or any other form of storage medium in the art.

[0132] The "first", "second" in the names mentioned in the embodiments of the present application are only used for name identification, and do not represent the first and second in order.

[0133] It should be noted that the embodiments in the specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts of each embodiment can be referred to each other. For the method disclosed in the embodiments, since it corresponds to the product embodiment disclosed in the embodiments, the description is relatively simple, and the relevant parts can be referred to the description of the product embodiment part.

[0134] The foregoing description of the disclosed embodiments enables a person skilled in the art to make or use the application. Modifications of these embodiments will occur to persons of skill in the art, and that the generic principles defined herein can be applied to other embodiments without departing from the spirit or scope of the application. Therefore, the present application is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for calculating a member level retention, characterized by, The method comprises: According to the preset membership level retention period, a target member corresponding retention task is generated; the retention task includes a member ID, a member level, and a retention deadline; From a member database, an order system, and a point system, a data set of the target member within the retention period is pulled; the data set includes basic information, consumption data, and point data; Based on the retention rules matched with the current member level of the target member, a Boolean value calculation is performed on the data set to obtain a retention result; According to the retention result, the member level and the member validity period corresponding to the target member are updated.

2. The method of claim 1, wherein, The method of updating the member level and the member validity period corresponding to the target member according to the retention result comprises: If the target member meets the retention rules, the current member level of the target member is maintained and the member validity period is reset; If the target member does not meet the retention rules, the member level and the member validity period of the target member are updated in combination with the retention strategy.

3. The method of claim 2, wherein, The retention strategy includes a re-computation strategy and a step-down strategy; the updating of the member level and the member validity period of the target member in combination with the retention strategy comprises: If the retention result meets the re-computation strategy, the member level of the target member is recalculated according to the order range and the point range indicated by the re-computation strategy, and the member validity period is reset; If the retention result meets the step-down strategy, the member level of the target member is lowered by one level, and the member validity period is reset.

4. The method of claim 1, wherein, The method of pulling the data set of the target member within the retention period comprises: When pulling the data set, if the data set pulling fails, an automatic retry mechanism is triggered; the number of retries of the automatic retry mechanism is preset to N times; N is an integer greater than or equal to 1; If the data set is failed to be pulled for N times, the retention task is marked as to be manually processed, and the failure reason is recorded.

5. The method of claim 1, wherein, After obtaining the data set, the method further comprises: The basic information, the consumption data, and the point data are cleaned and formatted to eliminate invalid data and unify the data format, and a standardized data set is obtained; the invalid data includes repeated consumption records or records with abnormal point values.

6. The method of claim 1, wherein, The retention task enters a task queue after being created and is marked as to be processed; The method further comprises: The number of retention tasks in the task queue that are to be processed is monitored in real time, and the number of task processing threads is adjusted according to the number of retention tasks that are to be processed; If the number of retention tasks that are to be processed is greater than or equal to a preset threshold, the number of processing threads is increased; If the number of retention tasks that are to be processed is less than the preset threshold, the number of processing threads is reduced.

7. The method of claim 1, wherein, The method further comprises: After updating the member level and the member validity period of the target member, the retention result is pushed to the target member through in-site notification and off-site notification.

8. A member rank maintenance calculation device characterized by comprising: The device comprises: The generating module is configured to generate a level maintenance task corresponding to a target member according to a preset level maintenance period of a member level; the level maintenance task includes a member ID, a current level, and a level maintenance deadline; The obtaining module is configured to pull a data set of the target member within the level maintenance period from a member database, an order system, and a point system; the data set includes basic information, consumption data, and point data; The computing module is configured to perform Boolean value calculation on the data set based on a level maintenance rule matched with the current member level of the target member to obtain a level maintenance result; The updating module is configured to update the member level and a member validity period corresponding to the target member according to the level maintenance result.

9. A control device characterized by comprising: A processor and a memory are included, the memory is used to store programs, instructions or codes, and the processor is used to execute the programs, instructions or codes in the memory to complete the member level maintenance calculation method according to any one of claims 1-7.

10. A computer-readable storage medium, characterized in that, A computer program is stored, and the computer program is loaded by a processor to execute the member level maintenance calculation method according to any one of claims 1-7.

Images