A method, apparatus, and computer-readable storage medium for managing user lifecycles based on business reference relationships.
By configuring preset validity periods, detecting business references, and establishing binding relationships in user group lifecycle management, the lifecycle of user groups is dynamically managed, solving the problems of resource waste and business interruption in existing technologies, and realizing automated lifecycle management and resource optimization.
Patent Information
- Application Number
- CN202611106551.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-07-24
- Publication Date
- 2026-11-17
AI Technical Summary
Existing technologies for user lifecycle management suffer from resource waste and business interruption risks. This is mainly due to the lack of linkage with the actual business cycle, resulting in unreasonable user validity period settings, inaccurate renewal, and a crude cleanup process, leading to waste of computing and storage resources and business risks.
By configuring a preset validity period when creating a user group, detecting business references to establish binding relationships, and responding to renewal check trigger conditions, the lifecycle of user groups can be dynamically managed to achieve automatic renewal and hierarchical cleanup, ensuring that the lifecycle of user groups matches business needs.
It has enabled automated management of the user lifecycle, reduced resource waste and business interruption risks, optimized system resource utilization, and improved operational efficiency and business continuity.
Smart Images

Figure CN123115103A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of data processing technology, and specifically to a method, apparatus, and computer-readable storage medium for managing the lifecycle of a user group based on business reference relationships. Background Technology
[0002] In the context of big data and precision operations, user demographic management systems have become core tools in various industries, including internet, marketing, and e-commerce. By defining and filtering specific user groups, businesses can achieve precise targeting of marketing campaigns, segmented user services, and targeted task scheduling. However, with the growth of business volume and the dramatic increase in the number of user groups, effectively managing the lifecycle of these user groups to control costs and ensure business stability has become a key technical challenge.
[0003] In existing technologies, a common management approach is for operators to manually assign a fixed validity period, such as one month, three months, or one year, when creating user groups. Within this validity period, the system updates the user group data at a preset frequency to ensure timeliness. Once the validity period expires, the system stops updating, regardless of whether the user group is still used by downstream businesses. In this model, the system typically does not record the association between user groups and specific business references; business users need to monitor whether the validity period of the user groups meets their business requirements.
[0004] However, the aforementioned existing technical solutions have significant drawbacks. First, due to the lack of linkage with the actual business cycle, operators often tend to choose the longest available validity period to avoid business interruption. This results in a large number of users who only use the system for a short period of time still having their systems updated for a long time after the business ends, consuming a large amount of computing and storage resources and causing serious cost waste.
[0005] Secondly, fixed validity periods are difficult to match with dynamically changing business needs. On the one hand, if the business cycle exceeds the preset validity period of the user group, the user group data will stop updating or even become invalid, leading to the interruption of business processes that rely on that user group. On the other hand, the system cannot detect whether a user group is still being used effectively. Therefore, when the validity period is about to expire, it cannot make an accurate renewal decision and can only rely on manual communication and manual operation to extend the validity period, which is not only inefficient but also prone to errors due to omissions.
[0006] Furthermore, the existing cleanup process is rather crude when user accounts expire, typically involving either directly deleting all data or retaining it indefinitely without updates. The former can hinder business rollback and problem investigation, while the latter continuously occupies storage resources, making it impossible to achieve refined resource recovery and management. These issues collectively lead to the dilemma of both high system operating costs and business operation risks. Summary of the Invention
[0007] To address the technical problem of resource waste and business interruption risks caused by poor user lifecycle management in existing technologies, this invention provides a user lifecycle management method, apparatus, and computer-readable storage medium based on business referencing relationships. The aim is to achieve a balance between cost control and business continuity by dynamically linking the user lifecycle with its actual business referencing.
[0008] This invention provides a user lifecycle management method based on business reference relationships, comprising: configuring a preset current validity period for the user group when creating the user group; detecting business references for the user group and establishing a binding relationship containing business lifecycle parameters for the business references; responding to a preset renewal check trigger condition and determining whether to extend the current validity period of the user group based on one or more binding relationships associated with the user group; when the current validity period of the user group expires, performing a final reference check and, based on the result of the final reference check, extending the current validity period of the user group or initiating a cleanup process for the user group.
[0009] Optionally, determining whether to extend the current validity period of the user group based on one or more binding relationships associated with the user group specifically includes: Obtain the business lifecycle parameters from all binding relationships associated with the user group; If it is determined that the end time indicated by any business lifecycle parameter is later than the current validity period of the user group, then the current validity period of the user group is updated to the latest time among all end times. If it is determined that there is no end time indicated by any business lifecycle parameter that is later than the current validity period of the user group, then the current validity period of the user group will not be extended.
[0010] Optionally, the cleaning process is a tiered cleaning process.
[0011] Optionally, the tiered cleanup process includes: a first stage of cleaning up temporary data and intermediate calculation results related to the user group; a second stage of retaining the core metadata and reference history of the user group within a preset retention period; and a third stage of deleting all data of the user group after the retention period ends.
[0012] Optionally, the method further includes: when establishing the binding relationship, if the business reference does not provide a business lifecycle parameter, then calculating a temporary business lifecycle parameter based on the business type to which the business reference belongs.
[0013] Optionally, the method further includes: periodically verifying the established binding relationship, and updating and correcting the business lifecycle parameters in the binding relationship according to the actual business status of the business reference.
[0014] Optionally, the method further includes: updating the data of the user group at a preset frequency within the current validity period of the user group; and setting a priority for the update based on the importance of the business reference of the user group.
[0015] Optionally, the preset renewal check trigger condition is the check time when the periodic inspection is completed.
[0016] Optionally, the business lifecycle parameter is the business reference end time.
[0017] The present invention also provides a corresponding management device, comprising: a configuration unit, configured to configure a preset current validity period for the user group when creating the user group; a detection unit, configured to detect business references for the user group and establish a binding relationship including business lifecycle parameters for the business references; a renewal unit, configured to respond to a preset renewal check trigger condition and determine whether to extend the current validity period of the user group based on one or more binding relationships associated with the user group; and a cleanup control unit, configured to perform a final reference check when the current validity period of the user group expires, and selectively extend the current validity period of the user group or initiate a cleanup process for the user group based on the result of the final reference check.
[0018] In addition, the present invention provides a computer-readable storage medium on which a computer program stored is executed by a processor to implement the method described in the present invention.
[0019] Compared with the prior art, the present invention has significant beneficial effects: When creating a user group, a preset current validity period is configured for the user group; business references to the user group are detected, and a binding relationship containing business lifecycle parameters is established for the business reference; in response to a preset renewal check trigger condition, based on one or more binding relationships associated with the user group, it is determined whether to extend the current validity period of the user group; when the current validity period of the user group expires, a final reference check is performed, and based on the result of the final reference check, the current validity period of the user group is extended or a cleanup process for the user group is initiated. Thus, by introducing a default initial validity period and a dynamic renewal mechanism based on business references, this invention fundamentally solves the problem of resource waste caused by users setting excessively long validity periods, and ensures that the validity period of user groups can automatically adapt to business needs, thereby effectively preventing business interruptions. Secondly, by automatically capturing and verifying business reference relationships, the entire process of user group lifecycle management is automated, greatly reducing the cost of manual intervention. Furthermore, the introduced hierarchical cleanup process and update priority mechanism achieve refined management and efficient utilization of system resources, balancing resource recovery efficiency and business backtracking needs when cleaning up expired user groups. Attached Figure Description
[0020] Figure 1 A flowchart illustrating a method for managing the lifecycle of a user based on business reference relationships, provided as an embodiment of the present invention; Figure 2 This is a schematic diagram of a population lifecycle management device based on business reference relationships, provided as an embodiment of the present invention. Detailed Implementation
[0021] To make the objectives, technical solutions, and advantages of this invention clearer, the invention will be further described in detail below with reference to the accompanying drawings. It should be noted that, unless otherwise specified, the embodiments and features described in these embodiments can be combined with each other.
[0022] In the current data-driven operation model, there is a common problem of wasted computing resources and business interruption risks due to poor user group management. This invention proposes an innovative technical approach, the core of which lies in establishing a dynamic and automated lifecycle management mechanism by automatically capturing and analyzing the inherent relationship between user groups and their downstream business references. This mechanism enables the validity period of user groups to automatically adapt to the actual needs of the business, thereby maximizing the conservation of system resources while ensuring business continuity. To clearly explain this solution, the core terms are first defined: User group refers to a specific set of users selected from a massive user base through preset filtering conditions; Current validity period refers to the end point of the time period during which a user group is currently recognized as valid by the system and will be updated; Business reference refers to the behavior of downstream business parties calling user group data; Binding relationship is a data structure that records the relationship between user groups and business references; Business lifecycle parameter is a parameter that characterizes the validity period of the business reference itself.
[0023] Specifically, Figure 1 This is a flowchart illustrating a user lifecycle management method based on business reference relationships, provided as an embodiment of the present invention. Figure 1 As shown, the method includes the following steps: S101. When creating a user group, configure a preset current validity period for the user group; S102. Detect business references for the user group and establish a binding relationship for the business references that includes business lifecycle parameters; S103. In response to a preset renewal check trigger condition, determine whether to extend the current validity period of the user group based on one or more of the binding relationships associated with the user group; S104. When the current validity period of the user group expires, perform a final reference check, and based on the result of the final reference check, extend the current validity period of the user group or initiate a cleanup process for the user group.
[0024] Specifically, refer to Figure 1 First, when creating a user group, a preset current validity period is configured for that user group. This step changes the existing technology's reliance on manual specification or indefinite management, and by setting a reasonable, shorter default validity period (e.g., 1 month), it curbs resource waste caused by users' tendency to choose the longest validity period from the source.
[0025] Next, the system detects business references targeting the user group and establishes a binding relationship for these references, including business lifecycle parameters. This forms the basis for dynamic management. Through standardized interfaces or protocol parsing, the system can automatically identify and record which business (such as marketing campaigns, SMS outreach, etc.) started using the user group, when, and when that business is expected to end. Establishing this binding relationship creates a clear data association between the previously isolated user group and its application scenario, providing a basis for subsequent intelligent decision-making.
[0026] Subsequently, in response to preset renewal check trigger conditions, and based on one or more binding relationships associated with the user group, the system determines whether to extend the current validity period of the user group. This means that the system no longer silently waits for the validity period to expire, but actively and periodically reviews the "use" status of each user group. By analyzing the lifecycle of all related services, the system can accurately determine whether the current validity period is sufficient to cover all service needs, thereby achieving proactive and automated renewal management.
[0027] Finally, when the current validity period of the user group expires, a final reference check is performed. Based on the result of the final reference check, the current validity period of the user group is selectively extended, or a cleanup process for the user group is initiated. This is a key step in closed-loop management, ensuring that at the end of the user group's lifecycle, the system reconfirms that no valid business references depend on the user group, thus making the most appropriate decision. Through the synergistic effect of these four steps, this invention constructs a closed-loop automated management system covering the entire lifecycle from creation, use, renewal to cleanup.
[0028] Based on the above scheme, the specific logic for determining whether to extend the current validity period of the user group is as follows: Obtain the business lifecycle parameters from all binding relationships associated with the user group; if it is determined that any business lifecycle parameter indicates an end time later than the current validity period of the user group, then update the current validity period of the user group to the latest of all end times. In a preferred embodiment, the business lifecycle parameter here is the business reference end time. This design ensures that the validity period of the user group can completely cover the complete cycle of all businesses that depend on it. By taking the maximum value among all end times as the new validity period end, the problem of business interruption caused by the premature expiration of the user group is completely eliminated. For example, if a user group with a current validity period of March 12th is simultaneously referenced by an activity ending on March 20th and a task ending on March 5th, the system will automatically extend its current validity period to March 20th.
[0029] Furthermore, when a user group confirms that renewal is no longer necessary and enters the cleanup process, the cleanup process is preferably a tiered cleanup process. This design abandons the crude "delete and forget" or "permanently retain" approach of existing technologies, and achieves differentiated processing of data of different values. Specifically, the tiered cleanup process may include three stages. The first stage cleans up temporary data and intermediate calculation results related to the user group. This data is usually large in volume and has no long-term retention value; immediate cleanup can quickly release a large amount of storage and computing resources. According to test data on ride-hailing platforms, this can reduce system storage resource usage by 65% and computing resource usage by 55%. The second stage retains the core metadata and reference history of the user group within a preset retention period. Core metadata and reference history are important bases for business review and problem investigation; retaining them for a preset period (e.g., 7 days) provides a valuable backtracking window for operations or data analysts. The third stage, after the retention period ends, deletes all data of the user group, completing the complete recovery of resources. This three-stage design makes the user group offline process smooth and safe.
[0030] To enhance system compatibility and robustness, this invention further includes: when establishing the binding relationship, if the business reference does not provide a business lifecycle parameter, a temporary business lifecycle parameter is calculated based on the business type to which the business reference belongs. For example, for an SMS delivery task without a specified end time, the system can automatically set a temporary end time based on historical experience or configuration rules (such as the standard cycle of 15 days for ride-hailing industry commuter discount reminder SMS delivery tasks). This design enables the invention to be compatible with downstream business systems with incomplete interfaces that cannot actively report lifecycle parameters, greatly expanding its applicability.
[0031] To ensure the accuracy of the binding relationships, this invention also includes: periodically verifying the established binding relationships and updating and correcting the business lifecycle parameters in the binding relationships based on the actual business status referenced by the business. For example, the system can query the actual status of the business system through an interface every hour. If it finds that an activity originally scheduled to end on March 20th ends early on March 15th, the system will immediately correct the end time in the binding relationship. This dynamic verification and correction mechanism ensures the reliable operation of the entire dynamic management system, avoiding invalid or insufficient renewals due to changes in business plans.
[0032] Furthermore, to optimize system resource allocation, this invention also includes: updating the user group's data at a preset frequency within the current validity period of the user group; and prioritizing the updates based on the importance of the user group's business references. For example, user groups referenced by core marketing campaigns can be marked as "high priority," and in daily batch update tasks, the system will prioritize allocating computing resources to them to ensure their data is updated as quickly as possible. This design achieves refined management and efficient utilization of computing resources.
[0033] Regarding the triggering method for renewal checks, the preset triggering condition can be periodic inspection. For example, the system can be configured to perform a comprehensive inspection of all active users every 6 hours. This periodic inspection mechanism ensures the timeliness of renewal operations and is a stable and reliable implementation method.
[0034] Based on the above embodiments, the present invention also provides a population lifecycle management device based on business reference relationships. Figure 2 This is a schematic diagram of a user lifecycle management device based on business reference relationships, provided as an embodiment of the present invention. (Refer to...) Figure 2 The device includes: a configuration unit 21, configured to configure a preset initial validity period for the user group when creating the user group, as the current validity period of the user group; a detection unit 22, configured to detect business references for the user group and establish a binding relationship containing business lifecycle parameters for the business references; a renewal unit 23, configured to respond to a preset renewal check trigger condition and determine whether to extend the current validity period of the user group based on one or more binding relationships associated with the user group; and a cleanup control unit 24, configured to perform a final reference check when the current validity period of the user group expires, and selectively extend the current validity period of the user group or initiate a cleanup process for the user group based on the result of the final reference check.
[0035] In the specific implementation of the device, a data storage module may also be included to persistently store core information about user groups, all established binding relationship information, renewal operation logs, and cleanup process records. Simultaneously, a system management module may be included to provide a configuration interface for system administrators to flexibly adjust key parameters such as preset renewal check trigger conditions, default initial validity period, and retention periods for core data during tiered cleanup. This modular design gives the device good scalability and configurability. The units communicate with each other through an internal data bus or interface. For example, the detection unit stores the established binding relationships in the data storage module, and the renewal unit reads user group information and binding relationship information from the data storage module to make decisions.
[0036] The present invention also provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, enables the implementation of the population lifecycle management method as described in any of the foregoing embodiments. This storage medium can be any type of non-volatile memory. When a computer device loads and executes the program, its internal hardware resources, such as the processor and memory, constitute the logical unit for implementing the functions of the present invention, thereby transforming a general-purpose computer device into a dedicated population lifecycle management device.
[0037] The following description uses a basic embodiment. Assume an operations staff member creates a user group for a "weekend travel discount." The system automatically assigns a preset current validity period upon creation, for example, valid until a certain date one month from now. This design avoids operations staff choosing an excessively long validity period based on intuition, controlling costs from the outset. Subsequently, a two-week "weekend travel ride coupon distribution" marketing campaign begins to utilize this user group. The method of this invention detects this business reference and automatically establishes a binding relationship for it, clearly recording the business lifecycle parameters of the marketing campaign. Under preset renewal check trigger conditions, the system checks and finds that the marketing campaign's end time is later than the user group's current default validity period. Therefore, it automatically triggers a renewal operation, extending the user group's current validity period to match the marketing campaign's end time. When the marketing campaign ends, the user group's current validity period also expires. At this point, the system performs a final reference check to confirm that no other business references depend on this user group. It then initiates a cleanup process for the user group, reclaiming its occupied computing and storage resources, completing closed-loop management of the entire lifecycle.
[0038] Building upon the above embodiments, consider a more complex scenario. Suppose that in addition to the aforementioned marketing campaign, a "weekend travel reminder" SMS message also targets the same user group, but this task did not explicitly specify its end time when it was initiated. In this case, the system will calculate a temporary business lifecycle parameter based on the business type to which the business reference belongs. Simultaneously, the system will periodically verify all established binding relationships. During one verification, the system discovers through an interface query that the SMS message task actually completed ahead of schedule on the second day. The system will immediately update and correct the temporary end time in the binding relationship based on this actual business status. In subsequent renewal checks, the renewal unit will obtain the end times of both the marketing campaign and the SMS task references and select the latest of these two end times as the new current validity period for the user group. This combination of operations ensures the accuracy and dynamic adaptability of renewal decisions.
[0039] When a user group's lifecycle ends and the cleanup process is initiated, it will be conducted in a tiered manner. In the scenario described in this example, the current validity period of the user group expires after both the marketing campaign and SMS tasks have concluded. After the cleanup process is initiated, the first phase immediately cleans up temporary data and intermediate calculation results generated during daily updates of the user group. In the second phase, the system retains the user group's core metadata and its reference history for 7 days for business review. In the third phase, after the 7-day retention period, the system automatically deletes all remaining data for the user group. This tiered cleanup process balances the immediacy of resource recovery with the necessity of business retrospective analysis.
[0040] Consider another example of resource optimization. Assume there are two user groups in the system that are both currently active: Group A is referenced by a core "New Customer First Order Discount" promotion; Group B is referenced by a regular "User Activity Analysis" task. According to the method of this invention, the system prioritizes update tasks based on the importance of the business reference. Therefore, the system prioritizes allocating computing resources to the update task of Group A, ensuring that it is completed before the business uses it. The update task of Group B is then queued with a lower priority. Through this priority scheduling based on business importance, this invention prioritizes the continuity and accuracy of core business operations with limited computing resources, achieving optimized resource allocation.
[0041] The following will be combined with the appendix Figure 1 and attached Figure 2 Taking a ride-hailing platform as an example, a preferred embodiment of the present invention will be fully described. This embodiment will demonstrate the entire process from creation to cleanup of a user group named "2026 Spring Commuter Ride-Hailing Intent Users".
[0042] First, user group creation and default initial validity period configuration. Operations personnel submit requests through the interface, defining the filtering criteria for user groups. Upon receiving the request, the configuration unit automatically generates a unique identifier for that user group and configures a default initial validity period of one month as its current validity period.
[0043] Next, the business reference binding relationships were captured and verified. This user group was referenced by two business parties: one was the "Spring Commuter Coupon Distribution Campaign," with a lifecycle from February 15, 2026 to March 20, 2026; the other was the "Commuter Ride Discount Reminder SMS Delivery Task," which started on February 20, 2026, but did not specify an end time. The detection unit monitored these two business references in real time. For the former, it directly captured and recorded the binding relationship containing a specified end time. For the latter, since no end time was provided, the detection unit deduced a temporary end time of March 7, 2026 based on the business type. Subsequently, the detection unit continuously verified the binding relationships according to a preset 1-hour verification cycle. In one verification, it was found that the SMS delivery task had been completed ahead of schedule on March 5, 2026, so the end time in the corresponding binding relationship was immediately corrected to the actual "2026-03-05."
[0044] Then, dynamic renewal judgment and execution are performed based on the binding relationships. Specifically, the renewal unit operates according to a preset 6-hour inspection cycle. When the inspection reaches the user group, it extracts two binding relationships from the data storage module, with their corrected end times being March 20, 2026 and March 5, 2026, respectively. The renewal unit compares these two times with the user group's current end time and finds that the activity end time (March 20, 2026) is later than the current end time. Therefore, the renewal operation is triggered, the system calculates the maximum value among all referenced end times, namely March 20, 2026, and updates the current validity period of the user group to this date.
[0045] Furthermore, during the regular update phase of the user group, this user group is marked as "high priority" because it is referenced by the core coupon campaign, and is given priority in the allocation of computing resources during daily updates.
[0046] Furthermore, the validity period expires and a tiered cleanup process is implemented. Specifically, when March 20, 2026, the current validity period of a user group expires. The cleanup control unit first performs a final reference check to confirm that all associated business references have ended. After confirming that there are no valid references, the tiered cleanup process is triggered. In the first stage, intermediate calculation results are immediately cleaned up; in the second stage, core metadata and binding relationship records are retained for 7 days; in the third stage, after 7 days, all data for that user group is completely deleted. If any unfinished business references are found during the final reference check, the process returns to step S103, where the renewal unit performs renewal again. Through actual application testing on a ride-hailing platform, the method of this invention reduces the business interruption rate caused by the expiration of user group validity to 0%, while reducing the average daily update cost of user groups by 60%.
[0047] Those skilled in the art will understand that embodiments of the present invention can be provided as methods, systems, or computer program products. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. The above descriptions are merely preferred embodiments of the present invention and are not intended to limit the invention. Various modifications and variations can be made to the present invention by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the scope of protection of the present invention.
Claims
1. A method for managing the lifecycle of users based on business reference relationships, characterized in that, include: When creating a user group, a preset current validity period is configured for the user group; Detect business references targeting the user group and establish binding relationships for the business references that include business lifecycle parameters; In response to a preset renewal check trigger condition, based on one or more of the binding relationships associated with the user group, determine whether to extend the current validity period of the user group; When the current validity period of the user group expires, a final reference check is performed, and based on the result of the final reference check, the current validity period of the user group is extended or the cleanup process for the user group is initiated.
2. The method according to claim 1, characterized in that, The step of determining whether to extend the current validity period of the user group based on one or more binding relationships associated with the user group specifically includes: Obtain the business lifecycle parameters from all binding relationships associated with the user group; If it is determined that the end time indicated by any business lifecycle parameter is later than the current validity period of the user group, then the current validity period of the user group is updated to the latest time among all end times. If it is determined that there is no end time indicated by any business lifecycle parameter that is later than the current validity period of the user group, then the current validity period of the user group will not be extended.
3. The method according to claim 1, characterized in that, The cleanup process is a tiered cleanup process; the tiered cleanup process includes: a first stage, cleaning up temporary data and intermediate calculation results related to the user group; a second stage, retaining the core metadata and reference history of the user group within a preset retention period; and a third stage, deleting all data of the user group after the retention period ends.
4. The method according to claim 1, characterized in that, The method further includes: when establishing the binding relationship, if the business reference does not provide a business lifecycle parameter, then a temporary business lifecycle parameter is calculated based on the business type to which the business reference belongs.
5. The method according to claim 1, characterized in that, The method further includes: periodically verifying the established binding relationship, and updating and correcting the business lifecycle parameters in the binding relationship according to the actual business status of the business reference.
6. The method according to claim 1, characterized in that, The method further includes: updating the data of the user group at a preset frequency within the current validity period of the user group; and setting a priority for the update based on the importance of the business reference of the user group.
7. The method according to claim 1, characterized in that, The preset renewal inspection trigger condition is the time when the periodic inspection is completed.
8. The method according to claim 1, characterized in that, The business lifecycle parameter is the end time of the business reference.
9. A user lifecycle management device based on business reference relationships, characterized in that, include: A configuration unit is used to configure a preset current validity period for a user group when creating the user group; The detection unit is used to detect business references targeting the user group and establish a binding relationship for the business references, including business lifecycle parameters. The renewal unit is used to respond to a preset renewal check trigger condition and determine whether to extend the current validity period of the user group based on one or more of the binding relationships associated with the user group. The cleanup control unit is used to perform a final citation check when the current validity period of the user group expires, and selectively extend the current validity period of the user group or initiate a cleanup process for the user group based on the result of the final citation check.
10. A computer-readable storage 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.
