A check-in data management system, method, device, medium, and product
By combining bitmap lists and management service nodes, the efficiency problem of the sign-in data management system under large-scale storage and diverse sign-in formats is solved, achieving efficient and low-cost sign-in data management.
Patent Information
- Application Number
- CN202210896947.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-07-28
- Publication Date
- 2026-11-10
- Estimated Expiration
- 2042-07-28
AI Technical Summary
Existing attendance data management systems consume a large amount of storage space when storing large-scale attendance data, cannot match diverse attendance formats, increase computational burden, and result in high costs due to independent management of different activities.
The system records sign-in data in a bitmap list format, using business identifiers and participant identifiers as key information. The system identifies the target business and target participants through management service nodes, retrieves and updates sign-in data from the data center, and enables diversified sign-in management and universal use.
It reduces the storage space occupied by check-in data, reduces the computing burden, and enables universal check-in data management for different business activities, thereby reducing management costs.
Smart Images

Figure CN115345574B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of computer technology, and in particular to a sign-in data management system, method, device, medium, and product. Background Technology
[0002] With the rapid development of mobile communication technology, the demand for activity check-ins in user-oriented applications is increasing. The platform needs to record and manage the check-in data generated on the application front end for published activities.
[0003] Existing attendance data management implementations often use direct database recording of attendance data. However, this method requires significant storage space, potentially reaching terabyte levels, when dealing with large volumes of attendance data. An improvement could consider distributed storage, such as using key-value pairs with the attendance date as the keyword. However, this approach is only suitable for storing standard attendance data and cannot handle diverse attendance formats. Furthermore, reading this type of data generates multiple I / O operations, increasing the computational burden of attendance data management.
[0004] In addition, existing implementations typically manage attendance data independently for different activities, which requires designing data structures and management functions for each activity, increasing the cost of managing attendance data. Summary of the Invention
[0005] This application provides a check-in data management system, method, device, medium, and product, which can be used universally for different business activities and reduce the management cost of check-in data.
[0006] In a first aspect, embodiments of this application provide a check-in data management system, including: a check-in management layer and a data layer;
[0007] The data layer includes a data center, which stores the sign-in data information corresponding to the participants under each business. Each sign-in data information uses the business identifier and the participant identifier as key information, and records the sign-in identifier data of the corresponding participant in the form of a bitmap list.
[0008] The check-in management layer includes management service nodes, which are used to determine the target business and target participants associated with the received check-in service request, determine the target check-in data information of the target participants under the target business from the data center, and update the target check-in data information using the set check-in management strategy in response to the check-in service request.
[0009] Secondly, embodiments of this application provide a check-in data management method, executed by a management service node in the check-in data management system provided in the first aspect of this application. The check-in data management system further includes a data layer composed of data centers. The method includes:
[0010] Determine the target business and target participants for the received check-in service request;
[0011] From the check-in data stored in the data center, find the target check-in data of the target participants under the target business. Each check-in data uses the business identifier and the participant identifier as key information, and records the check-in identifier data of the corresponding participant in the form of a bitmap list.
[0012] The target check-in data information is updated using the set check-in management strategy in response to the check-in service request.
[0013] Thirdly, embodiments of this application provide a check-in data management device, serving as a management service node in the check-in data management system provided in the first aspect of this application, including:
[0014] One or more processors;
[0015] Storage device for storing one or more programs;
[0016] The one or more programs are executed by the one or more processors, causing the one or more processors to implement the check-in data management method provided in the second aspect of the present application.
[0017] Fourthly, embodiments of this application provide a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the check-in data management method provided in the second aspect of this application.
[0018] Fifthly, embodiments of this application provide a computer program product, which includes a computer program that, when executed by a processor, implements the check-in data management method provided in the second aspect of this application.
[0019] This application discloses a check-in data management system, method, device, medium, and product. The system includes a check-in management layer and a data layer. The data layer includes a data center for storing check-in data information corresponding to participants under each business. Each check-in data information uses a business identifier and a participant identifier as key information, and records the check-in identifier data of the corresponding participant in a bitmap list format. The check-in management layer includes a management service node for determining the target business and target participants associated with a received check-in service request, determining the target check-in data information of the target participants under the target business from the data center, and updating the target check-in data information using a set check-in management strategy to respond to the check-in service request. This technical solution can determine the target business and target participants associated with a check-in service request through the management service node, obtain the check-in data information of the target participants under the target business from the data center of the data layer based on the business identifier of the target business and the participant identifier of the target participants, and update the check-in data information based on the check-in management strategy. Compared to existing technologies that use check-in dates as keywords for distributed storage of check-in data, this technical solution uses target business and target participants as keywords, enabling check-in data management across diverse check-in formats and reducing computational burden. Furthermore, unlike existing technologies that manage check-in data independently for different activities, this solution pre-configures business check-in settings for different business activities. Based on check-in service requests, the target business can be identified, and the check-in data for target participants under that business can be updated. This allows for universal use across different business activities, reducing the cost of managing check-in data.
[0020] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of this application, nor is it intended to limit the scope of this application. Other features of this application will become readily apparent from the following description. Attached Figure Description
[0021] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0022] Figure 1 A structural block diagram of a sign-in data management system provided in Embodiment 1 of this application is given;
[0023] Figure 2 Another structural block diagram of the sign-in data management system provided in Embodiment 1 of this application is given;
[0024] Figure 3 A sample diagram of the core data structure stored in the data center within the sign-in data management system provided in this application is given;
[0025] Figure 4 A flowchart illustrating a sign-in data management method according to Embodiment 2 of this application is provided;
[0026] Figure 5 A diagram illustrating the implementation of the check-in data management system provided in this application, showing how the management service node responds to received check-in service requests, is provided.
[0027] Figure 6 A schematic diagram of the hardware structure of a sign-in data management device provided in Embodiment 3 of this application is given. Detailed Implementation
[0028] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort should fall within the scope of protection of the present application.
[0029] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.
[0030] Example 1
[0031] Figure 1 A structural block diagram of a sign-in data management system provided in Embodiment 1 of this application is given. This system is suitable for managing sign-in data under diverse sign-in scenarios for different business activities, such as... Figure 1 As shown, the event management system includes: a check-in management layer 11 and a data layer 12;
[0032] Data layer 12 includes data center 121, which is used to store the sign-in data information corresponding to the participants under each business. Each sign-in data information uses business identifier and participant identifier as key information and records the sign-in identifier data of the corresponding participant in the form of a bitmap list.
[0033] The check-in management layer 11 includes a management service node 111, which is used to determine the target business and target participants associated with the received check-in service request, determine the target check-in data information corresponding to the target participants under the target business from the data center, and update the target check-in data information using the set check-in management strategy in response to the check-in service request.
[0034] In this embodiment, the provided check-in data management system can be understood as a service support system deployed on the application software's backend server. It is primarily used to manage the responses to check-in service requests generated by clients. Generally, the backend server can be viewed as a distributed system architecture capable of global service deployment. Under this distributed system architecture, the distributed check-in data management system in this embodiment can be constructed by deploying backend service nodes in different regions. Each backend service node participating in the deployment can serve as a management service node 111, constituting the check-in management layer 11.
[0035] It should be noted that the application scenario of the check-in data management system can be described as follows: On the client side of the application software, when a user performs an activity check-in operation, the check-in data management system needs to record and manage the check-in data generated by the user's check-in operation on the application software front end. In actual implementation, this function may involve the management of check-in data under different check-in formats, such as counting the number of times a user checks in for a specific business activity. Considering that using a key-value pair format with the check-in date as the keyword for distributed storage of check-in data, this implementation method can only store regular check-in data and cannot match the management of check-in data under diverse check-in formats. Furthermore, reading check-in data in this record format will generate multiple I / O operations, increasing the computational burden in check-in data management.
[0036] Furthermore, in existing technologies, attendance data is typically managed independently for different activities. This requires designing data structures and management functions for each activity, increasing the cost of attendance data management. The attendance data management system provided in this embodiment, however, primarily enables attendance data management under diverse attendance formats. Simultaneously, it allows for attendance data management for various business activities using the attendance data management system provided in this embodiment.
[0037] The bitmap list is a contiguous binary array (0s and 1s), and elements can be located using the offset. The bitmap list uses the smallest unit, the bit, to set 0s and 1s, representing the value or state of an element. Since the bit is the smallest unit in a computer, using it for storage is very space-efficient, especially suitable for scenarios with large amounts of data and binary statistics. In this embodiment, the key information is composed of `actid` and `uid` concatenated according to certain rules. `actid` represents the business identifier, `uid` represents the participant identifier, and `offset` represents the check-in offset, which solves the problem of large storage space usage for check-in data.
[0038] Specifically, both the check-in management layer 11 and the data layer 12 can be understood as abstract mechanisms for providing check-in data management services. In this embodiment, the check-in management layer 11 can be abstracted as an execution mechanism for a check-in data management service, specifically including management service nodes 111 that can manage check-in data for check-in service requests made by clients. Each management service node 111 can be a computer device serving as a background service node in a distributed system architecture. For the management service layer 11, it mainly manages the check-in data information allocated to it through the management service nodes 111.
[0039] Similarly, in this embodiment, the data layer 12 can also be abstracted as a data management mechanism, which specifically includes data centers 121 deployed in different regions, and the data centers 121 can be integrated on any backend service node in a distributed system architecture. In this embodiment, the data center 121 can be used to store the check-in data information corresponding to the participants under each business. Each check-in data information uses the business identifier and the participant identifier as key information, and records the check-in identifier data of the corresponding participant in the form of a bitmap list. Among them, each business corresponds to a business identifier, and there is a one-to-one correspondence between the business and the business identifier. The participant can be understood as the user participating in the check-in activity. When a check-in service request sent by the client is received, the business involved in the check-in service request can be determined through the business identifier, and then the business check-in configuration information involved in the business can be determined. The participant involved in the check-in service request can be determined through the participant identifier, and then the check-in data information of the target participant under the target business can be determined based on the business identifier and the participant identifier, and recorded as the target check-in data information.
[0040] It is known that the check-in data information corresponding to the participants under different businesses can be stored on different data centers 121 through the idea of load balancing. The management service node 111 in the check-in management layer 11 can establish a connection with each data center 121 in the data layer 12. Thus, after determining the target business and target participants associated with the received check-in service request, the target check-in data information corresponding to the target participants under the target business can be determined from the data center, and the target check-in data information can be updated using the set check-in management strategy.
[0041] It should be noted that in this embodiment, data centers 121 in data layer 12 can be formed by building Codis clusters on backend service nodes in different regions. A Codis cluster can be understood as a distributed database cluster, specifically used for storing massive amounts of data and managing data through interaction with other services, such as performing CRUD operations. The check-in data information corresponding to each participating object under each business on data center 121 can preferably be a Redis check-in data information. Each Redis check-in data information can be recorded based on the business identifier and the participating object identifier. Codis handles request forwarding and non-stop data migration at the underlying level. All of this is transparent to the client; it can be simply considered that Codis is connected to a Redis service with unlimited memory.
[0042] In this embodiment, the management objects corresponding to each management service node 111 in the check-in management layer 11 are preferably check-in service requests sent by the client and allocated to the management service node 111 through the corresponding process. For any management service node 111, it can determine the target business and target participants for the check-in service requests allocated to it, determine the target check-in data information of the target participants under the target business from the data center, and update the target check-in data information using the set check-in management strategy to respond to the check-in service request.
[0043] For example, one implementation of the management service node 111 responding to the check-in service request can be described as follows: The management service node 111 can receive the check-in service request assigned to it by the relevant process for check-in management. Based on the business identifier carried in the check-in service request, the business related to check-in management can be determined, which is referred to as the target business in this embodiment; based on the participant identifier carried when the check-in service request is assigned, the participant related to check-in management can be determined, which is referred to as the target participant in this embodiment; then, the check-in management strategy of the target business can be obtained through interaction with the data center 121 on the data layer 12, and the check-in data information of the target participant under the target business can be obtained, which is referred to as the target check-in data information in this embodiment; further, the target check-in data information is updated according to the determined check-in management strategy to respond to the check-in service request.
[0044] As is known, in existing technologies, check-in data is distributed and stored using key-value pairs with the check-in date as the keyword. To obtain the check-in statistics for a specific participant in a particular business, it is necessary to retrieve the check-in information recorded for each check-in date and then perform statistical aggregation. However, in this embodiment, each check-in data entry uses the business identifier and the participant identifier as key information. By determining the participant identifier, it is only necessary to determine the check-in data information of that participant under that business, without needing to retrieve other data.
[0045] In addition, compared to existing implementations that typically manage check-in data independently for different activities, which requires designing data structures and management functions for each activity, this embodiment stores the check-in data information of participants under each business in the data center. Operational objects of different businesses can interact with the check-in data management system and store business configuration information in the data center. Based on the business identifier, the business check-in configuration information related to that business can be determined.
[0046] It is understood that the response to the check-in service request generated by the client user's check-in operation can be achieved by the management service node on the backend server, which, based on the received check-in service request, determines the target business and the target participants, and then determines the check-in data information of the target participants under the target business on data center 121. The check-in data information is then updated based on the set check-in management policy, thereby responding to the check-in service request.
[0047] The check-in data management system provided in Embodiment 1 of this application can determine the target business and target participants associated with the check-in service request through the management service node. Based on the business identifier of the target business and the participant identifier of the target participants, it retrieves the check-in data information of the target participants under the target business from the data center of the data layer, and updates the check-in data information based on the check-in management strategy. Compared to the prior art, which uses the check-in date as a keyword for distributed storage of check-in data, this technical solution uses the target business and target participants as keywords, enabling check-in data management under diverse check-in formats and reducing computational burden. Furthermore, compared to the prior art, which manages check-in data independently for different activities, this technical solution pre-configures business check-in configuration information for different businesses. Based on the check-in service request, the target business can be determined, and the check-in data information of the target participants under the target business can be updated, enabling universal use for different business activities and reducing the management cost of check-in data.
[0048] Furthermore, Figure 2 Another structural block diagram of the sign-in data management system provided in Embodiment 1 of this application is given, such as... Figure 2 As shown, the system may also include: a service access layer 13;
[0049] The business access layer 13 includes a business access process 131, which is used to obtain the business check-in configuration information submitted by the operation objects of each business and associated with the corresponding business.
[0050] Data center 121 is also used to store the business check-in configuration information corresponding to each business. Each business check-in configuration information records the check-in configuration information with the business identifier as the key information.
[0051] The check-in configuration information includes: check-in cycle information, make-up check-in permission information, check-in start time, and continuous check-in association information.
[0052] In this embodiment, the event management system of the distributed system architecture set up by the backend server also includes a business access layer 13. The business access layer 13 can be abstracted as an interaction mechanism that interacts with the sign-in data management system. Specifically, it includes a business access process 131 that can receive various business sign-in configuration information submitted by the operation objects of each business and associated with the corresponding business. Each business access process 131 can be created on any backend service node under a distributed system architecture.
[0053] For the check-in data management system provided in this embodiment, it can establish a communication connection with the check-in data management system through the business access process 131 in the business access layer 13. Based on the business access process 131, it can obtain the business check-in configuration information submitted by the operation objects of each business and associated with the corresponding business. Then, it can generate a business identifier as key information relative to the obtained check-in configuration information. Finally, the business access process 131 in the business access layer 13 can also interact with each data center 121 on the data layer 12. It can submit the check-in configuration information and the business identifier to the data center 121 so that the check-in configuration information can be stored by the data center 121.
[0054] The service identifier can be a global variable pre-set by the service access layer 13 relative to the check-in configuration information. This global variable can be recorded on the data center 121 of the data layer 12, so that each service access process 131 can accurately generate the corresponding service identifier for each check-in configuration information received.
[0055] In this embodiment, the data center 121 of the data layer 12 can store not only check-in data information but also business check-in configuration information. Each business check-in configuration information can record various check-in configuration information associated with that business, such as check-in cycle information, make-up check-in permission information, check-in start time, and continuous check-in association information. It is understood that the business check-in configuration information can also preferably be a Redis collection, thereby recording each business configuration information associated with the business based on its business identifier.
[0056] In this embodiment, the background service node that serves as the execution carrier of the service access process 131 in the service access layer 13 can be determined based on the client's home region, and can also be used to assign a suitable management service node 111 capable of establishing a communication connection to each service access process 131. Specifically, after receiving the service check-in configuration information associated with the corresponding service submitted by the service operation object, the service access process 131 needs to store the service check-in configuration information in the data center 121.
[0057] Furthermore, the management service node 111 may include:
[0058] The information determination process is used to determine the target business and target participants associated with the check-in service request by analyzing the received check-in service request;
[0059] The information reading process is used to access data center 121, find the business check-in configuration information corresponding to the target business and record it as the target configuration information, and find the target check-in data information corresponding to the target participants under the target business;
[0060] The check-in management process is used to update the target check-in data information based on the target configuration information and the check-in time zone information in the check-in service request.
[0061] In this embodiment, the management service node 111 responds to the received check-in service requests and performs check-in data information management, which is equivalent to interacting with the data layer 12. Specifically, it can update the check-in data information related to the check-in service request to the check-in data information by interacting with the check-in data information stored in the corresponding business and the business check-in configuration information in the data layer 12. In this embodiment, the management service node 111 can respond to each check-in service request assigned to it.
[0062] Understandably, the information determination process is primarily used to analyze received check-in service requests to determine the associated business and participating entities, referred to in this embodiment as the target business and target participating entities. Taking a practical application scenario as an example, when a user has a check-in need on the client side, the client will trigger the generation of a check-in service request, which can be submitted by the client to the management service node 111. On the management service node 111, the assigned check-in service request can first be received by the information determination process and subjected to corresponding analysis and determination operations.
[0063] For the information determination process, it can analyze the request message carrying the business identifier and the participant identifier to determine the business and the participant associated with the check-in service request. Simultaneously, the information reading process created on the management service node 111 can perform relevant information reading operations based on the information determination process. It is mainly used to find the business check-in configuration information corresponding to the target business from the data center 121 of the data layer 12, which is referred to as the target configuration information in this embodiment. At the same time, it searches for the check-in data information of the target participant under the target business from the data center 121 of the data layer 12, which is referred to as the target check-in data information in this embodiment. It can be assumed that the relevant information of the target participant under the target business, such as the current check-in status, business identifier, and participant identifier, already exists in the target check-in data information. The target check-in data information can be considered to include the check-in status associated with the target business and the target participant, but does not yet include the check-in information corresponding to the check-in service request.
[0064] Meanwhile, the check-in management process created on management service node 111 can update the target check-in data information by reading the target check-in data information read by the above information reading process, combined with the read target configuration information and the check-in time zone in the check-in service request.
[0065] It should be noted that, because the check-in service request is associated with related business and participating objects, in order to respond correctly to the check-in service request, it is necessary to consider the check-in start time and check-in period information in the target configuration information, as well as the timestamp of the check-in service request. Therefore, the check-in management process can determine the check-in offset of the check-in service request based on the check-in start time and check-in period information, as well as the timestamp of the check-in service request, and thus update the check-in data information of the target participating objects under the target business, which is denoted as the target check-in data information in this embodiment.
[0066] Furthermore, the check-in management process can be specifically used for:
[0067] Extract the check-in start time and check-in period information from the target configuration information, obtain the timestamp of the received check-in service request, and extract the check-in time zone information from the check-in service request;
[0068] The check-in offset of the check-in service request is determined based on the check-in start time, the received timestamp, the check-in time zone information, and the period duration in the check-in period information.
[0069] Extract the target bitmap list from the target check-in data information, and offset the check-in offset starting from the first bit of the target bitmap list to obtain the target bit after the offset;
[0070] Update the identifier value on the target bit to the set check-in identifier data, and obtain the updated target check-in data information.
[0071] It should be noted that, in order to determine the check-in offset of the check-in service request, it is necessary to calculate the check-in start time, check-in period information, the timestamp of the check-in service request received in the target configuration information, and the check-in time zone information in the check-in service request, and then determine the check-in offset of the check-in service request.
[0072] Specifically, based on the check-in start time in the target configuration information and the check-in timezone information in the check-in service request, the start timestamp of the target business in that check-in timezone can be calculated. For the same business, global user check-in uses the start timestamp as the initial check-in time to ensure consistency across timezones and support check-in across all time zones. The check-in offset of the check-in service request is determined based on the start timestamp, the current timestamp, and the period duration in the check-in period information. The check-in offset is determined by subtracting the start timestamp from the current timestamp and dividing by the period duration.
[0073] Understandably, the bitmap list in the check-in data is used to record check-in status, with each bit indicating whether a check-in has occurred. For example, a value of 1 indicates that a check-in has been completed, while a value of 0 indicates that a check-in has not occurred. Using a bitmap list based on time-series markers offers high read / write and storage efficiency, supports fixed and sliding periods, and meets the requirement of resetting the activity check-in period after a break.
[0074] In this embodiment, after determining the check-in offset of the check-in service request, the target bitmap list is extracted from the target check-in data information. Starting from the first bit in the target bitmap list, the check-in offset is calculated, and the offset bit is obtained, which represents the position of this check-in in the target bitmap list; in this embodiment, this is denoted as the target bit. The flag value on the target bit is updated to the set check-in flag data, obtaining the updated target check-in data information. This step can be implemented based on program code to update the flag value on the target bit, and then the return value can be used to determine whether the check-in was successful. For example, the return value `flag` stores the original value of the storage bit; the return value determines whether the check-in result is successful or a duplicate check-in. The check-in data management system provided in this embodiment supports configurations for different activity businesses, different check-in cycles, and different check-in time zones. Simultaneously, a multi-region high-availability architecture is adopted for deployment, and Codis data is synchronized across data centers and regions through transparent synchronization, ensuring high data availability.
[0075] Furthermore, after updating the target check-in data, the check-in management process can also be used for:
[0076] Determine the current check-in time and current consecutive check-in count of the target participant relative to the target business, and update the check-in management information of the target parameter object under the target business;
[0077] The current check-in result is generated based on the check-in data and check-in management information of the target participants and sent to the client of the target participants.
[0078] The sign-in management information is stored in the data center.
[0079] In this embodiment, after the check-in management process updates the target check-in data information, it can also determine the current check-in time and current consecutive check-in count of the participating object relative to the target business, and update the check-in management information of the target parameter object under the target business based on the current check-in time and current consecutive check-in count. The current check-in result is generated based on the target participating object's check-in data information and check-in management information and sent to the target participating object's client for viewing.
[0080] For example, users can check in for a certain service through a client installed on their mobile phones. After checking in, the user is shown a number of consecutive check-ins and is prompted to recalculate the cycle if they miss a check-in. When the user's consecutive check-in count meets the rules set for the service, the user is rewarded accordingly.
[0081] Based on the above embodiments, the management service node 111 can also be used for:
[0082] Upon receiving a request for a replacement signature service, the system determines the replacement signature business and the participants, and updates the replacement signature data information of the participants under the replacement signature business based on the set replacement signature management policy; the replacement signature data information is stored in data center 121.
[0083] In this embodiment, for a supplementary signature service request, similar to receiving a sign-in service request, the management service node 111 also includes an information determination process, an information reading process, and a supplementary signature management process. The management service node 111 responds to the received supplementary signature service request and performs sign-in data information management, which is equivalent to information interaction with the data layer 12. Specifically, it can update the sign-in data information related to the supplementary signature service request to the sign-in data information by interacting with the sign-in data information stored in the corresponding business and the business sign-in configuration information in the data layer 12. In this embodiment, the management service node 111 can respond to each supplementary signature service request assigned to it.
[0084] Understandably, the information determination process is primarily used to analyze received signature replacement service requests to determine the associated business and participating entities, referred to in this embodiment as the signature replacement business and the signature replacement participating entities. Taking a practical application scenario as an example, when a user has a signature replacement requirement on the client side, the client will trigger the generation of a signature replacement service request, which can be submitted by the client to the management service node 111. On the management service node 111, the assigned signature replacement service request can first be received by the information determination process and subjected to corresponding analysis and determination operations.
[0085] For the information determination process, it can analyze the request message carrying the supplementary signature service identifier and the supplementary signature participant identifier to determine the supplementary signature service request associated with it. Simultaneously, the information reading process created on the management service node 111 can perform relevant information reading operations based on the information determination process. It is mainly used to search for the supplementary signature configuration information corresponding to the supplementary signature service within the data center 121 of the data layer 12, which is denoted as supplementary signature configuration information in this embodiment. Simultaneously, it searches for the check-in data information corresponding to the supplementary signature participant under the supplementary signature service within the data center 121 of the data layer 12, which is denoted as supplementary signature data information in this embodiment. It can be assumed that relevant information about the supplementary signature participant under the supplementary signature service, such as the current check-in status, the supplementary signature service identifier, and the supplementary signature participant identifier, already exists in the supplementary signature data information. The supplementary signature data information can be considered to include the check-in status associated with the supplementary signature service and the supplementary signature participant, but does not yet include the check-in information corresponding to the supplementary signature service request.
[0086] Meanwhile, the check-in management process created on management service node 111 can update the check-in data information by reading the supplementary check-in data information read by the above information reading process, combined with the read supplementary check-in configuration information and the check-in time zone in the supplementary check-in service request.
[0087] It should be noted that, because the supplementary signature service request is associated with the supplementary signature business and the supplementary signature participants, in order to respond correctly to the supplementary signature service request, it is necessary to consider the sign-in start time and sign-in period information in the supplementary signature configuration information, as well as the timestamp of the sign-in service request. Therefore, the supplementary signature management process can determine the sign-in offset of the supplementary signature service request based on the sign-in start time and sign-in period information, as well as the timestamp of the sign-in service request, and thus update the supplementary signature data information.
[0088] This optional embodiment supports the function of making up for missed check-ins. Making up for missed check-ins requires recalculating the check-in period. By backtracking the check-in data, the period and the number of consecutive check-ins can be reset.
[0089] Furthermore, the supplementary signature management process can be specifically used for:
[0090] Extract the check-in start time and check-in period information from the check-in configuration information, obtain the check-in timestamp of the check-in service request, and extract the check-in time zone information from the check-in service request; determine the check-in offset of the check-in service request based on the check-in start time, check-in timestamp, and period duration in the check-in period information; extract the check-in bitmap list from the check-in data information, offset the check-in offset starting from the first bit of the check-in bitmap list, and obtain the offset check-in bit; update the identifier value on the check-in bit to the set check-in identifier data, and obtain the updated check-in data information.
[0091] It should be noted that, in order to determine the check-in offset of the supplementary check-in service request, it is necessary to calculate the check-in start time, check-in period information, supplementary check-in timestamp of the supplementary check-in service request, and check-in time zone information in the supplementary check-in service request in order to determine the check-in offset of the supplementary check-in service request.
[0092] Specifically, based on the check-in start time in the check-in configuration information and the check-in time zone information in the check-in service request, the start timestamp of the check-in service in that check-in time zone can be calculated. Based on the start timestamp, the check-in timestamp, and the period duration in the check-in period information, the check-in offset of the check-in service request is determined.
[0093] In this embodiment, after determining the offset of the make-up signature service request, the make-up signature bitmap list is extracted from the make-up signature data information. Starting from the first bit of the make-up signature bitmap list, the offset is calculated, and the offset bit is obtained, which represents the position of this sign-in in the make-up signature bitmap list. In this embodiment, this is denoted as the make-up signature bit. The identifier value on the make-up signature bit is updated to the set sign-in identifier data, thus obtaining the updated make-up signature data information.
[0094] Furthermore, after updating the supplementary signature data information of the participants in the supplementary signature business, management service node 111 is also used for:
[0095] The check-in management information of the participants in the supplementary check-in service is updated based on the updated supplementary check-in data, and the supplementary check-in results are sent to the clients of the participants.
[0096] In this embodiment, after the management service node 111 completes the update of the supplementary signature data information of the supplementary signature participants under the supplementary signature business, it updates the sign-in management information of the supplementary signature participants under the supplementary signature business according to the updated supplementary signature data information, and sends the supplementary signature result to the client of the supplementary signature participants for the target participants to view.
[0097] Based on the above embodiments, such as Figure 2 As shown, the check-in data management system provided in this embodiment may further include: a consumption service layer 14; the consumption service layer 14 includes a publish / subscribe message node 141, which is used to obtain the check-in update information corresponding to the participants from the data center, and persist the check-in update information to the database after performing message verification processing; wherein, the check-in update information includes updated check-in data information or supplementary check-in data information.
[0098] In this embodiment, the sign-in data management system of the distributed system architecture set up by the backend server also includes a consumption service layer 14. The consumption service layer 14 can be abstracted as an interaction mechanism that interacts with the sign-in data management system. Specifically, it includes a publish-subscribe message node 141 that can obtain the sign-in update information corresponding to the participating object from the data center and persist the sign-in update information to the database after performing message verification processing. The publish-subscribe message node 141 can be created on any backend service node under a distributed system architecture.
[0099] For the check-in data management system provided in this embodiment, it can establish a communication connection with the check-in data management system through the subscription message node 141 in the consumption service layer 14. Based on the subscription message node 141, it can obtain the check-in update information corresponding to the participants from the data center 121, and then perform message verification processing on the check-in update information before finally persisting it to the database. The subscription message node 141 in the consumption service layer 14 can also interact with each data center 121 on the data layer 12. It can obtain the check-in update information corresponding to the participants from the data center 121, perform verification processing on the check-in update information, and persist it to the database.
[0100] The process involves validating the sign-in update information obtained from data center 121, verifying whether essential fields are empty, deduplicating the sign-in update information, and finally persisting the sign-in update information to the database. The message service layer, Kafka, utilizes an efficient and reliable message delivery mechanism—message subscription nodes—for platform-independent data exchange and distributed system integration based on data communication. By providing message delivery and queuing models, it can extend inter-process communication in a distributed environment. Sign-in data is retrieved from the Kafka cluster, and the message data fields are validated for non-emptiness and validity. Then, message deduplication is performed, and finally, the sign-in data information is reported to the database. The message consumption speed can be increased by scaling up consumer instances.
[0101] For example, check-in update information can be persisted to the columnar storage database ClickHouse. ClickHouse supports high-concurrency writes, efficient columnar data compression, and large-volume data reading, and can support peak traffic writes from the check-in system. For data recovery from failures, where large batches of data need to be read at once, ClickHouse storage also provides excellent support. ClickHouse is a columnar database for online analytical processing (OLAP). Columnar databases are well-suited for real-time big data analysis scenarios, characterized by large data volumes and the need to aggregate data along column dimensions. Statistical operations such as column aggregation, counting, and summation are superior to row-based storage. Since the data type of a column is the same, data compression is easier, and selecting a superior compression algorithm for each column significantly increases the compression ratio. This saves disk space and allows for greater cache utilization. ClickHouse fully utilizes disk throughput through compaction and append sequential write features, greatly increasing write throughput. Furthermore, data partitioning and thread parallelism significantly reduce query latency. It uses asynchronous data persistence while supporting high-concurrency writes, efficient compression, and large-volume data queries.
[0102] Understandably, when a user checks in on the activity page, the process in the check-in data management system handles these request events, executes the corresponding logic to write check-in data information to the Codis cluster, and simultaneously writes a check-in record to the Kafka queue. Since synchronizing and persisting data to ClickHouse would be time-consuming, this module decouples itself from the check-in logic using asynchronous writing. It also partitions and consumes messages from Kafka to improve message processing speed. The Codis cluster is used to store the middleware for the check-in service; it is memory-based and offers fast read and write speeds.
[0103] Through the Codis transparent cluster, data from various regions can be synchronized with low latency, ensuring the availability of the global deployment of the check-in data management system. The bitmap list storage structure ensures that the check-in data occupies a small area. Kafka asynchronously processes check-in messages, ensuring the speed of the main process and quickly returning check-in results. The database middleware proxy Myshard supports table partitioning and can support high-concurrency read and write requests. ClickHouse stores data and can display check-in data and business monitoring in real time.
[0104] Based on the above embodiments, the management service node can also be used for:
[0105] Upon receiving a sign-in query request, the system determines the business to be queried and the participants to be queried, and retrieves the sign-in related information of the corresponding business and participants stored in the data center. The sign-in related information includes sign-in data information, business sign-in configuration information, and sign-in management information.
[0106] Based on the set check-in query strategy and check-in related information, the check-in query data that meets the check-in query request is determined and fed back to the client of the participant to be queried.
[0107] The data center stores sign-in information for each participant under each business, including sign-in data, business sign-in configuration information, and sign-in management information. The sign-in data uses business identifiers and participant identifiers as key information, recording the sign-in identifier data of the corresponding participants in a bitmap list format. Each business sign-in configuration record uses the business identifier as key information for sign-in configuration. Sign-in configuration information includes: sign-in cycle information, make-up sign-in permission information, sign-in start time, and continuous sign-in association information. Sign-in management information refers to the sign-in statistics for each participant under each business.
[0108] It is understood that in this embodiment, the management service node 111 updates the check-in data information of the check-in service request to the associated target check-in data information in the data center 121. The target check-in data in the data center 121 records the associated check-in related information for each business and participating object. This embodiment can achieve the querying of check-in related information for any business and any participating object through the management service node 111 in the check-in data management system.
[0109] Specifically, upon receiving a sign-in query request, the request is analyzed to determine the business to be queried and the participants to be queried. Then, based on the business identifier of the business to be queried and the participant identifier of the participants to be queried, the corresponding sign-in related information is retrieved from the data center. The sign-in query request may include query conditions. Based on the set sign-in query strategy and sign-in related information, the sign-in query data that meets the sign-in query request is determined and fed back to the client of the participants to be queried.
[0110] The check-in query request can be configured according to user needs, and no specific restrictions are imposed here. For example, when the management service node 111 receives a query request about a certain business, it can find the matching target check-in data information related to the business on the data center 121, and obtain the check-in status of the queried business from the target check-in data information.
[0111] Alternatively, when the management service node 111 receives a query request about a participant's participation in a certain check-in service, it can find the target check-in data information related to the user under the matching service on the data center 121, and obtain the check-in status of the queried user in the service from the target check-in data information.
[0112] In this embodiment, it can be determined whether it is the first sign-in based on the sign-in offset of the determined sign-in service request. For example, a sign-in offset of 0 indicates the first sign-in. Alternatively, it can be determined whether a participant has participated in the most recent n sign-in records for a certain service. For example, querying the most recent n sign-in records [offset-n, offset], where offset represents the current offset, can be described as follows: obtain the sign-in configuration information for the service, determine the current offset; calculate offset-n, which is the starting offset; use the batch command BITFIELD key GET u63(startOffset+63*i) to obtain a long integer list List. <long>The long integer list is parsed sequentially using bitwise operations to extract the value of each bit, thus obtaining the most recent check-in record.
[0113] You can also query the check-in make-up markers. For example, querying the bitmap of key_mark will give you a list of check-in record make-up markers. To query the total number of check-ins, for example, use the bitmap command: BITCOUNT key 0offset, the return value will be the total number of check-ins.
[0114] The sign-in data management system provided in this embodiment stores sign-in data information corresponding to participants under each business in the data center, and updates the sign-in data information of the target participants under the target business through the management service node. It can also realize effective query of sign-in information when users have the need to query sign-in information.
[0115] To better illustrate the core data structure stored in the data center within the data layer of the sign-in data management system provided in this embodiment, Figure 3 A sample diagram of the core data structure stored in the data center within the sign-in data management system provided in this application is given. For example... Figure 3 As shown, the core data in the data center includes check-in configuration information, user check-in cycle, check-in data information, and supplementary check-in data information. Check-in configuration information includes business identifier, check-in cycle information, consecutive check-in association information, supplementary check-in rights information, and check-in start time. User check-in cycle information includes check-in time zone, current consecutive check-in information, and last check-in time. Check-in data information contains the user's actual check-in status. The check-in data information uses the business identifier and the participant identifier as key information, recording the check-in identifier data of the corresponding participant in the form of a bitmap list. In this example, the key information key is composed of actid and uid concatenated according to certain rules. actid represents the business identifier, uid represents the participant identifier, and offset represents the check-in offset. In the check-in data information, Key = actid_sign_uid is used as the identifier; a bit of 1 indicates that the user has checked in, and a bit of 0 indicates that the user has not checked in. It is understandable that each check-in interval can contain 1 to (n / consecutive+1) periods, where n represents the current consecutive check-in count, and consequent represents the consecutive check-in count set in the check-in configuration information. Additionally, the period is reset after a make-up check-in. The make-up check-in data uses the make-up check-in service identifier and the identifier of the make-up check-in participant as key information, recording the make-up check-in identifier data of the corresponding make-up check-in participant in the form of a bitmap list. In this example, Key = actid_fill_sign_uid is used as the identifier, and a bit of 1 indicates that it is a make-up check-in for the check-in offset.
[0116] To more clearly illustrate the working principle of the sign-in data management system provided in this application embodiment, the following describes the execution steps of the sign-in data management system using the following examples: when a sign-in service request is received, when a supplementary sign-in service request is received, and when a sign-in query request is received.
[0117] When a check-in service request is received:
[0118] 1. The client initiates a check-in service request, which includes the business identifier, the participant identifier, and the user's time zone.
[0119] 2. The check-in data management system calculates the check-in offset, which is the position of this check-in in the bitmap list.
[0120] A. Obtain the user's check-in configuration information;
[0121] B. Calculate the start timestamp based on the check-in start time and the user's time zone;
[0122] C. Calculate the check-in offset based on the start timestamp, current timestamp, and period duration;
[0123] 3. Check if it's the first time checking in: For example, BITPOS key 1[0,offset]. This step is to determine whether to recalculate the user's check-in period.
[0124] 4. Obtain user check-in cycle information and determine whether the check-in time zone parameter has changed.
[0125] 5. Perform check-in and write the check-in flag data to the bitmap list. For example, SETBIT key offset 1. The return value flag is the original value of the stored bit. The check-in result is determined based on the return value, whether the check-in was successful or a duplicate check-in.
[0126] 6. Return the most recent n check-in records [offset-n, offset].
[0127] A. Use the offset-n calculated in step 2 to obtain the startOffset;
[0128] B. Use the batch command BITFIELD key GET u63(startOffset+63*i) to obtain a long integer list. <long>;
[0129] C. Parse the long integer list sequentially using bitwise operations to obtain the value of each bit, thus obtaining the most recent check-in record.
[0130] 7. Update check-in cycle information: Accumulate the number of check-ins and update the last check-in time.
[0131] 8. Return the check-in result and check-in record to the client, and simultaneously send a check-in record to the Kafka message queue asynchronously.
[0132] 9. Report check-in messages for consumer services:
[0133] A. Verify that the required fields in the message are not empty;
[0134] B. Perform deduplication on the messages;
[0135] C. Write the check-in records to ClickHouse.
[0136] When a request for a replacement signature service is received:
[0137] 1'. The client initiates a replacement signature service request, which includes the replacement signature service identifier, the identifier of the replacement signature participant, and the user's time zone.
[0138] 2'. Calculate the offset of the replacement signature, which is the position of the replacement signature in the bitmap list:
[0139] A. Obtain user check-in configuration;
[0140] B. Calculate the start timestamp based on the check-in start time and the user's time zone;
[0141] C. Calculate the offset of the supplementary signature based on the start timestamp, the supplementary signature timestamp, and the period duration.
[0142] 3'. Check if it's the first time checking in: For example, BITPOS key 1[0,offset]. This step is to determine whether to recalculate the user's check-in period.
[0143] 4'. Obtain user check-in cycle information and determine whether the time zone parameter for make-up check-ins has changed.
[0144] 5'. Perform a supplementary check-in, writing the check-in record to the bitmap list: such as SETBIT key offset 1. The return value flag is the original value of the storage bit. Based on the return value, determine whether the check-in result is a successful check-in or a duplicate check-in.
[0145] 6'. Replacement signature mark, writes the replacement signature mark to another bitmap list: SETBIT key_mark offset 1.
[0146] 7'. Reset check-in period information. Missed check-ins may cause changes to the check-in period, so it is necessary to obtain all check-in data for the user and recalculate:
[0147] A. Calculate the latest check-in offset;
[0148] B. Use the batch command BITFIELD key GET u63(latestOffset+63*i) to get the full sign-in list;
[0149] C. Calculate the number of consecutive sign-ins based on the values obtained from A and B;
[0150] D. Update the last check-in time and the number of consecutive check-ins.
[0151] 8'. Return the sign-in result and sign-in record to the client, and simultaneously send a sign-in message to the Kafka queue asynchronously.
[0152] 9'. Consumer service report check-in message:
[0153] A. Verify that the required fields in the message are not empty;
[0154] B. Perform deduplication on the messages;
[0155] C. Write the check-in records to ClickHouse.
[0156] Check attendance records:
[0157] 1”. The upstream service initiates a sign-in query request, which includes the business identifier to be queried, the participant identifier to be queried, and the user's time zone.
[0158] 2”. Obtain business check-in configuration information and user check-in cycle information.
[0159] 3”. Query the most recent n check-in records [offset-n, offset]:
[0160] A. Use the offset-n calculated in step 2 to obtain the startOffset;
[0161] B. Use the batch command BITFIELD key GET u63(startOffset+63*i) to obtain a long integer list. <long>;
[0162] C. Parse the long integer list sequentially using bitwise operations to obtain the value of each bit, thus obtaining the most recent check-in record.
[0163] 4”. Query the sign-in make-up sign-in markers. Following the method in step 3, query the bitmap list of key_mark to obtain the list of sign-in make-up sign-in markers for the sign-in records.
[0164] 5”. To query the total number of check-ins, use the bitmap list command: BITCOUNT key 0offset. The returned value is the total number of check-ins.
[0165] 6”. Return the check-in record to the upstream service.
[0166] Example 2
[0167] Figure 4 A flowchart of a check-in data management method provided in Embodiment 2 of this application is given. This method is applicable to the management of check-in data under the diversified check-in situations of different business activities. Specifically, it can be executed by the management service node of the check-in management layer in the check-in data management system provided in Embodiment 1 of this application. The management service node can preferably be a check-in data management device. The check-in data management system also includes a data layer composed of a data center.
[0168] like Figure 4 As shown in Embodiment 2 of this application, a check-in data management method may specifically include the following steps:
[0169] S201. Determine the target business and target participants for the received check-in service request.
[0170] The sign-in data information, relative to the target participants under the target business, is stored in the data center of the data layer in the sign-in data management system of Example 1, including the target business identifier, the target participant identifier, and sign-in identifier data recorded in the form of a bitmap list.
[0171] In this embodiment, the execution entity of the provided method can be a management service node in the data check-in management system. This embodiment can realize the management of check-in data of participating objects under the business according to the received check-in service request.
[0172] For example, the management service node, acting as the executing entity, can receive check-in service requests, analyze these requests, and thus determine the associated business and participating entities. Taking a real-world application scenario as an example, when a user has a check-in need on the client side, the client will trigger the generation of a check-in service request, which can be submitted by the client to the management service node. On the management service node, the assigned check-in service request can first undergo corresponding analysis and determination operations.
[0173] S202. From the sign-in data stored in the data center, find the target sign-in data corresponding to the target participants under the target business.
[0174] In this embodiment, the data center stores the check-in data information corresponding to each participant under each service. Each check-in data entry uses the service identifier and the participant identifier as key information, and records the check-in identifier data of the corresponding participant in the form of a bitmap list.
[0175] When a check-in service request is received from a client, the business involved in the request can be identified by the business identifier, which is denoted as the target business in this embodiment. The participating object involved in the check-in service request can be identified by the participating object identifier, which is denoted as the target participating object in this embodiment. The check-in data information corresponding to the target participating object under the target business is searched from the check-in data information stored in the data center, and this is denoted as the target check-in data information. The target check-in data information is the check-in data information to be updated.
[0176] S203. Update the target check-in data information using the set check-in management strategy in response to the check-in service request.
[0177] It should be noted that all business-related configuration information is stored in the data center of the check-in data management system provided in Embodiment 1 above. Each business corresponds to business check-in configuration information, and each business check-in configuration information records the check-in configuration information with the business identifier as the key information; wherein, the check-in configuration information includes: check-in cycle information, supplementary check-in permission information, check-in start time, and continuous check-in association information.
[0178] Therefore, when a check-in service request is received, the check-in configuration information associated with the request can be determined through the business identifier, which is denoted as the target configuration information in this embodiment. Furthermore, the check-in data information of the target participants under the target business is updated based on the set check-in management strategy to respond to the check-in service request. This can be described as updating the target check-in data information based on the target configuration information and the check-in time zone information in the check-in service request. This enables check-in data management under diverse check-in formats and allows for universal use across different business activities, avoiding the problem of separate check-in data management for different activities.
[0179] This application provides a check-in data management method in Embodiment 2. This method can determine the target business and target participants associated with a check-in service request through a management service node. Based on the business identifier of the target business and the participant identifier of the target participants, it retrieves the check-in data information of the target participants under the target business from the data center of the data layer, and updates this check-in data information based on a check-in management strategy. Compared to existing technologies that use the check-in date as a keyword for distributed storage of check-in data, this technical solution uses the target business and target participants as keywords, enabling check-in data management for diverse check-in formats and reducing computational burden. Furthermore, compared to existing technologies that manage check-in data independently for different activities, this technical solution pre-configures business check-in configuration information for different businesses. Based on the check-in service request, the target business can be determined, and the check-in data information of the target participants under the target business can be updated. This enables universal use across different business activities and reduces the management cost of check-in data.
[0180] To better illustrate the management of check-in data provided in this embodiment, this embodiment provides an exemplary description from the perspective of a management service node, illustrating its response to a check-in service request and the management of check-in data. It is understood that the check-in data management method provided in this embodiment can also manage check-in data when receiving supplementary check-in service requests and check-in query requests. Here, the process of receiving a check-in service request and responding to it is used as an example for explanation.
[0181] Figure 5 A diagram illustrating the implementation of the check-in data management system provided in this application, showing how the management service node responds to received check-in service requests for check-in data management.
[0182] like Figure 5 As shown in the example diagram, this example diagram includes multiple execution entities involved in the method implementation. Client 31 is the sender of the check-in service request, and management service node 321 in the check-in management layer 32 is the execution entity of this method. In addition, a data center 331 in the data layer 33 stores business check-in configuration information and check-in data information. Meanwhile, a publish-subscribe message node 341 in the consumer service layer 34 interacts with the data center 331.
[0183] Specifically, such as Figure 4 As shown, the implementation process of the check-in data management method is as follows:
[0184] In this example, it is assumed that the operational objects of each business have submitted the business check-in configuration information associated with the corresponding business to the data center.
[0185] S1. The client generates a check-in service request and sends it to the management service node;
[0186] S2. The management service node analyzes the received check-in service requests to determine the target business and target participants associated with the check-in service requests.
[0187] S3. The management service node accesses the data center to find the business check-in configuration information corresponding to the target business and records it as the target configuration information, and to find the target check-in data information corresponding to the target participants under the target business.
[0188] S4. The management service node updates the target check-in data information based on the target configuration information and the check-in time zone information in the check-in service request.
[0189] The steps for updating the target check-in data information based on the target configuration information and the check-in time zone information in the check-in service request can be described as follows: Extract the check-in start time and check-in period information from the target configuration information, obtain the receiving timestamp of the check-in service request, and extract the check-in time zone information from the check-in service request; determine the check-in offset of the check-in service request based on the check-in start time, receiving timestamp, check-in time zone information, and period duration in the check-in period information; extract the target bitmap list from the target check-in data information, offset the check-in offset starting from the first bit of the target bitmap list, and obtain the target bit after offset; update the identifier value on the target bit to the set check-in identifier data to obtain the updated target check-in data information.
[0190] S5. The management service node determines the current check-in time and current consecutive check-in count of the target participant relative to the target business, and updates it to the check-in management information of the target parameter object under the target business.
[0191] S6. The management service node generates the current check-in result based on the check-in data and check-in management information of the target participants and sends it to the client of the target participants.
[0192] S7. The publish / subscribe message node obtains the sign-in update information corresponding to the participants from the data center, and persists the sign-in update information to the database after performing message verification processing.
[0193] Example 3
[0194] Figure 6 A schematic diagram of the hardware structure of a sign-in data management device according to Embodiment 3 of this application is provided. This embodiment of the application provides a sign-in data management device that can serve as a management service node in the sign-in management layer of the sign-in data management system provided in this embodiment.
[0195] like Figure 6 As shown, the check-in data management device 40 includes at least one processor 41 and a memory, such as a read-only memory (ROM) 42 or a random access memory (RAM) 43, communicatively connected to the at least one processor 41. The memory stores computer programs executable by the at least one processor. The processor 41 can perform various appropriate actions and processes based on the computer program stored in the ROM 42 or loaded from storage unit 48 into the RAM 43. The RAM 43 can also store various programs and data required for the operation of the check-in data management device 40. The processor 41, ROM 42, and RAM 43 are interconnected via a bus 44. An input / output (I / O) interface 45 is also connected to the bus 44.
[0196] Multiple components in the check-in data management device 40 are connected to the I / O interface 45, including: an input unit 46, such as a keyboard, mouse, etc.; an output unit 47, such as various types of displays, speakers, etc.; a storage unit 48, such as a disk, optical disk, etc.; and a communication unit 49, such as a network card, modem, wireless transceiver, etc. The communication unit 49 allows the check-in data management device 40 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.
[0197] This application also provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the check-in data management method provided in this application.
[0198] This application also provides a computer program product, which includes a computer program that, when executed by a processor, implements the check-in data management method provided in this application.
[0199] It should be understood that the various forms of processes shown above can be used to rearrange, add, or delete steps. For example, the steps described in this application can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution of this application can be achieved, and this is not limited herein.
[0200] The specific embodiments described above do not constitute a limitation on the scope of protection of this application. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this application should be included within the scope of protection of this application.< / long> < / long> < / long>
Claims
1. A sign-in data management system, characterized in that, include: Check-in management and data layer; The data layer includes a data center, which stores the sign-in data information corresponding to the participants under each business. Each sign-in data information uses the business identifier and the participant identifier as key information, and records the sign-in identifier data of the corresponding participant in the form of a bitmap list. The check-in management layer includes a management service node, which is used to determine the target business and target participants associated with the received check-in service request, determine the target check-in data information of the target participants under the target business from the data center, and update the target check-in data information using a set check-in management strategy in response to the check-in service request. The check-in data management system also includes: a business access layer; The service access layer includes a service access process, which is used to obtain the service check-in configuration information submitted by the operation objects of each service and associated with the corresponding service. The data center is also used to store the business check-in configuration information corresponding to each business. Each business check-in configuration information records the check-in configuration information with the business identifier as the key information. The check-in configuration information includes: check-in cycle information, make-up check-in permission information, check-in start time, and continuous check-in association information.
2. The system according to claim 1, characterized in that, The management service node includes: The information determination process is used to determine the target business and target participants associated with the received check-in service request by analyzing the received check-in service request; The information reading process is used to access the data center, find the business check-in configuration information corresponding to the target business and record it as the target configuration information, and find the target check-in data information corresponding to the target participant under the target business; The check-in management process is used to update the target check-in data information based on the target configuration information and the check-in time zone information in the check-in service request.
3. The system according to claim 2, characterized in that, The check-in management process is specifically used for: Extract the check-in start time and check-in period information from the target configuration information, obtain the receiving timestamp of the check-in service request, and extract the check-in time zone information from the check-in service request; The check-in offset of the check-in service request is determined based on the check-in start time, the received timestamp, the check-in time zone information, and the period duration in the check-in period information. Extract the target bitmap list from the target check-in data information, and offset the check-in offset starting from the first bit of the target bitmap list to obtain the target bit after offset; Update the identifier value on the target bit to the set check-in identifier data to obtain the updated target check-in data information.
4. The system according to claim 2, characterized in that, The check-in management process, after updating the target check-in data information, is further used for: Determine the current check-in time and current consecutive check-in count of the target participant relative to the target business, and update the check-in management information of the target participant under the target business; The current check-in result is generated based on the check-in data and check-in management information of the target participants and sent to the client of the target participants. The check-in management information is stored in the data center.
5. The system according to claim 1, characterized in that, The management service node is also used for: Upon receiving a request for a replacement signature service, the system determines the replacement signature business and the participants in the replacement signature process, and updates the replacement signature data information of the participants in the replacement signature business based on the set replacement signature management strategy. The supplementary signature data is stored in the data center.
6. The system according to any one of claims 1-5, characterized in that, Also includes: Consumer services layer; The consumption service layer includes publish-subscribe message nodes, which are used to obtain the sign-in update information corresponding to the participants from the data center, and persist the sign-in update information to the database after performing message verification processing on the sign-in update information. The check-in update information includes updated check-in data or supplementary check-in data.
7. The system according to any one of claims 1-5, characterized in that, The management service node is also used for: Upon receiving a sign-in query request, the system determines the business to be queried and the participants to be queried, and retrieves the sign-in related information stored in the data center corresponding to the business to be queried and the participants to be queried. The sign-in related information includes sign-in data information, business sign-in configuration information, and sign-in management information. Based on the set check-in query strategy and the check-in related information, the check-in query data that meets the check-in query request is determined and fed back to the client of the participant to be queried.
8. A method for managing attendance data, characterized in that, The method is executed by a management service node in the check-in management layer of the check-in data management system according to any one of claims 1-7, wherein the check-in data management system further includes a data layer composed of data centers, and the method comprises: Determine the target business and target participants for the received check-in service request; From the check-in data stored in the data center, find the target check-in data of the target participants under the target business. Each check-in data uses the business identifier and the participant identifier as key information, and records the check-in identifier data of the corresponding participant in the form of a bitmap list. The target check-in data information is updated using the set check-in management strategy in response to the check-in service request.
9. A check-in data management device, characterized in that, As a management service node of the check-in management layer in the check-in data management system according to any one of claims 1-7, it includes: One or more processors; Storage device for storing one or more programs; The one or more programs are executed by the one or more processors, such that the one or more processors are used to perform the check-in data management method of claim 8.
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 check-in data management method as described in claim 8.
11. A computer program product, characterized in that, The computer program product includes a computer program that, when executed by a processor, implements the check-in data management method according to claim 8.
Citation Information
Patent Citations
Vertical and horizontal two-dimensional Golay coding-based binary operation sign-in method and apparatus
CN108460110A
Business processing method and device, electronic equipment and storage medium
CN113468226A
