Method, device, server and storage medium for updating attendance information

Abstract

The present application provides a method, device, server and storage medium for updating sign-in information, which belongs to the field of Internet technology. The method includes: receiving a sign-in request from a first target account; in response to the sign-in request, obtaining first sign-in cumulative information and sign-in time information corresponding to the first target account, the first sign-in cumulative information being obtained by accumulating historical sign-in information of the first target account, and the sign-in time information including the most recent sign-in time of the first target account; updating the first sign-in cumulative information based on the current time and the most recent sign-in time. Since the historical sign-in information of the first target account is accumulated through the first sign-in cumulative information, when the sign-in request of the first target account is received, the first sign-in cumulative information is updated according to the current time and the most recent sign-in time, thereby saving the memory occupied by the sign-in cumulative information of the target account, so the method for updating the sign-in information reduces the memory occupancy rate.

Description

Technical Field

[0001] The present application relates to the field of Internet technology, and in particular to a method, device, server and storage medium for updating sign-in information. Background Art

[0002] At present, many APPs (Applications) have launched sign-in activities, where users can get corresponding rewards by signing in continuously, for example, signing in for three consecutive days can get a chance to win a lottery, etc. Since the number of consecutive sign-in days of the user needs to be determined before the reward is distributed, the user's sign-in information needs to be updated every time the user signs in.

[0003] In the related technology, when a user signs in, the server will create a record information in the cache middleware, which includes the business type, user name and sign-in date. For example, the record information is: "sign: User A: 20200717"; and each time the user signs in, the server will create a record information in the cache middleware.

[0004] However, in the above method, since a record information is created each time the user signs in, and each record information occupies a certain amount of memory, when the user signs in more times, the record information will occupy more memory, so the memory usage of the above update method is high. Summary of the invention

[0005] The embodiment of the present application provides a method, device, server and storage medium for updating sign-in information, which can reduce memory usage. The technical solution is as follows:

[0006] According to one aspect of an embodiment of the present application, a method for updating sign-in information is provided, the method comprising:

[0007] Receiving a sign-in request from a first target account;

[0008] In response to the sign-in request, obtaining first sign-in accumulation information and sign-in time information corresponding to the first target account, wherein the first sign-in accumulation information is obtained by accumulating historical sign-in information of the first target account, and the sign-in time information includes the most recent sign-in time of the first target account;

[0009] The first sign-in accumulation information is updated based on the current time and the most recent sign-in time.

[0010] In a possible implementation, updating the first sign-in accumulation information based on the current time and the most recent sign-in time includes:

[0011] Determine the time interval between the current time and the most recent check-in time;

[0012] Based on the time interval, determine the sign-in status information corresponding to the target account, where the sign-in status information includes one of a continuous sign-in status and a disconnected sign-in status;

[0013] Based on the sign-in status information, the first sign-in accumulation information is updated.

[0014] In another possible implementation, the first check-in accumulation information includes at least the most recent number of consecutive check-ins;

[0015] The updating of the first sign-in accumulation information based on the sign-in status information includes:

[0016] If the target account is in a continuous sign-in state, update the most recent continuous sign-in times;

[0017] If the target account is in a disconnected state, determine the current number of disconnected times, and update the first sign-in accumulation information based on the current number of disconnected times.

[0018] In another possible implementation, the updating the first sign-in accumulation information based on the current number of sign-out interruptions includes:

[0019] The sign-in break mark, the current sign-in break times and the number of consecutive sign-ins after sign-in break are added to the first sign-in cumulative information.

[0020] In another possible implementation, the first sign-in accumulation information further includes a sign-off mark and the number of most recent sign-off times;

[0021] The updating of the first sign-in accumulation information based on the current number of sign-out interruptions includes:

[0022] The most recent number of sign-in breaks is updated to the current number of sign-in breaks, and the number of consecutive sign-ins after sign-in breaks is added to the first sign-in cumulative information.

[0023] In another possible implementation, the method further includes:

[0024] receiving a query request, wherein the query request carries the first target account;

[0025] In response to the query request, the most recent consecutive check-in times are determined from the first check-in cumulative information.

[0026] In another possible implementation, the first sign-in accumulation information further includes a sign-off mark and the number of most recent sign-off times;

[0027] The determining the most recent consecutive sign-in times from the first sign-in accumulated information includes:

[0028] Determine the last text message from the first sign-in accumulated information;

[0029] If the text information is a symbol, it is determined that the most recent consecutive sign-in number is zero; if the text information is a number, it is determined that the number is the most recent consecutive sign-in number.

[0030] In another possible implementation, the time interval is a date interval; and determining the check-in status information corresponding to the target account based on the time interval includes:

[0031] In response to the date interval being one day, determining that the target account is in a continuous sign-in state; in response to the date interval being greater than one day, determining that the target account is in a disconnected sign-in state.

[0032] In another possible implementation, the method further includes:

[0033] The last check-in time of the first target account is updated to the current time.

[0034] According to another aspect of an embodiment of the present application, a method for updating sign-in information is provided, the method comprising:

[0035] Receive a request for a supplementary signature from the second target account;

[0036] In response to the request for making up the sign-in, obtaining second sign-in accumulation information corresponding to the second target account, where the second sign-in accumulation information is obtained by accumulating historical sign-in information of the second target account, and the second sign-in accumulation information includes the last consecutive sign-in times, the most recent sign-in interruption times, and the most recent consecutive sign-in times;

[0037] The second sign-in accumulation information is updated.

[0038] In a possible implementation, the updating the second sign-in accumulation information includes:

[0039] In response to the most recent number of disconnections being greater than one, subtracting one from the most recent number of disconnections;

[0040] In response to the most recent disconnection number being one, the most recent disconnection number and the disconnection flag are deleted, and the most recent continuous sign-in number and the last continuous sign-in number are updated to the sum of the most recent continuous sign-in number and the last continuous sign-in number.

[0041] According to another aspect of an embodiment of the present application, a device for updating sign-in information is provided, the device comprising:

[0042] A first receiving module, configured to receive a sign-in request from a first target account;

[0043] a first acquisition module, configured to acquire, in response to the sign-in request, first sign-in accumulation information and sign-in time information corresponding to the first target account, wherein the first sign-in accumulation information is obtained by accumulating historical sign-in information of the first target account, and the sign-in time information includes a most recent sign-in time of the first target account;

[0044] The first updating module is configured to update the first sign-in accumulation information based on the current time and the most recent sign-in time.

[0045] In a possible implementation, the first update module includes:

[0046] A first determining unit, configured to determine a time interval between the current time and the most recent check-in time;

[0047] A second determining unit is used to determine the sign-in status information corresponding to the target account based on the time interval, where the sign-in status information includes one of a continuous sign-in status and a disconnected sign-in status;

[0048] An updating unit is used to update the first sign-in accumulation information based on the sign-in status information.

[0049] In another possible implementation, the first sign-in cumulative information includes at least the most recent consecutive sign-in number; the updating unit is used to update the most recent consecutive sign-in number if the target account is in a continuous sign-in state; if the target account is in a sign-off state, determine the current sign-off number, and update the first sign-in cumulative information based on the current sign-off number.

[0050] In another possible implementation, the updating unit is configured to add a sign-off mark, the current sign-off number, and the number of consecutive sign-ins after sign-off to the first sign-in cumulative information.

[0051] In another possible implementation, the first sign-in cumulative information also includes a sign-out identifier and the most recent sign-out number; the updating unit is used to update the most recent sign-out number to the current sign-out number, and to add the number of consecutive sign-ins after sign-out to the first sign-in cumulative information.

[0052] In another possible implementation, the device further includes:

[0053] The first receiving module is further configured to receive a query request, wherein the query request carries the first target account number;

[0054] The first determining module is configured to determine the most recent consecutive check-in times from the first check-in cumulative information in response to the query request.

[0055] In another possible implementation, the first sign-in cumulative information also includes a sign-off mark and the most recent sign-off number; the first determination module is further used to determine the last text information from the first sign-in cumulative information; if the text information is a symbol, determine that the most recent continuous sign-in number is zero; if the text information is a number, determine that the number is the most recent continuous sign-in number.

[0056] In another possible implementation, the second determination unit is configured to determine that the target account is in a continuous sign-in state in response to the date interval being one day; and to determine that the target account is in a disconnected sign-in state in response to the date interval being greater than one day.

[0057] In another possible implementation, the first updating module is further configured to update the most recent check-in time of the first target account to the current time.

[0058] According to another aspect of an embodiment of the present application, a device for updating sign-in information is provided, the device comprising:

[0059] A second receiving module, used to receive a request for a supplementary signature from a second target account;

[0060] a second receiving module, configured to obtain, in response to the make-up sign-in request, second check-in cumulative information corresponding to the second target account, where the second check-in cumulative information is obtained by accumulating historical check-in information of the second target account, and the second check-in cumulative information includes the last consecutive check-in number, the most recent check-in interruption number, and the most recent consecutive check-in number;

[0061] The second updating module is used to update the second sign-in accumulation information.

[0062] In one possible implementation, the second updating module is configured to, in response to the most recent number of disconnected sign-ins being greater than one, subtract one from the most recent number of disconnected sign-ins; in response to the most recent number of disconnected sign-ins being one, delete the most recent number of disconnected sign-ins and the disconnected sign-in identifier, and update the most recent number of continuous sign-ins and the last number of continuous sign-ins to the sum of the most recent number of continuous sign-ins and the last number of continuous sign-ins.

[0063] According to another aspect of an embodiment of the present application, a server is provided, comprising: a processor and a memory, wherein the memory stores at least one program code, and the at least one program code is loaded and executed by the processor to implement the operations performed by the method for updating check-in information described in any of the above possible implementations.

[0064] According to another aspect of an embodiment of the present application, a computer-readable storage medium is provided, in which at least one program code is stored. The at least one program code is loaded by a processor and has operations performed to implement the method for updating check-in information described in any possible implementation manner described above.

[0065] According to another aspect of an embodiment of the present application, a computer program product or a computer program is provided, the computer program product or the computer program including a computer program code, the computer program code being stored in a computer-readable storage medium. A processor of a computer device reads the computer program code from the computer-readable storage medium, and the processor executes the computer program code, so that the computer device performs the operations performed by the method for updating the check-in information in any of the above possible implementations.

[0066] The beneficial effects of the technical solution provided by the embodiments of the present application include at least:

[0067] An embodiment of the present application provides a method for updating sign-in information. Since the historical sign-in information of the first target account is accumulated through the first sign-in accumulation information, when the sign-in request of the first target account is received, there is no need to create additional sign-in record information. Instead, the first sign-in accumulation information is updated according to the current time and the most recent sign-in time. In this way, for any first target account, only one sign-in accumulation information needs to be stored, thereby saving the memory occupied by the sign-in accumulation information of the target account. Therefore, the method for updating sign-in information reduces memory usage. BRIEF DESCRIPTION OF THE DRAWINGS

[0068] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0069] Figure 1 It is a schematic diagram of an implementation environment provided by an embodiment of the present application;

[0070] Figure 2 is a flow chart of a method for updating sign-in information provided in an embodiment of the present application;

[0071] Figure 3 is a flow chart of a method for updating sign-in information provided in an embodiment of the present application;

[0072] Figure 4 is a flow chart of a method for updating sign-in information provided in an embodiment of the present application;

[0073] Figure 5 It is a schematic diagram of a check-in information update scheme provided in an embodiment of the present application;

[0074] Figure 6 is a flow chart of a method for updating sign-in information provided in an embodiment of the present application;

[0075] Figure 7 is a flow chart of a method for updating sign-in information provided in an embodiment of the present application;

[0076] Figure 8 It is a structural block diagram of a device for updating sign-in information provided in an embodiment of the present application;

[0077] Fig. 9 It is a structural block diagram of a device for updating sign-in information provided in an embodiment of the present application;

[0078] Fig.10 It is a structural block diagram of a device for updating sign-in information provided in an embodiment of the present application;

[0079] Fig.11 It is a structural diagram of a server provided in an embodiment of the present application. DETAILED DESCRIPTION

[0080] In order to make the objectives, technical solutions and advantages of the present application clearer, the implementation methods of the present application will be further described in detail below in conjunction with the accompanying drawings.

[0081] Figure 1 is a schematic diagram of an implementation environment provided by an embodiment of the present application. Figure 1 , the implementation environment includes a terminal 101 and a server 102.

[0082] The terminal 101 and the server 102 are connected via a wireless or wired network. In addition, a client provided by the server 102 may be installed on the terminal 101, and the user corresponding to the terminal 101 may realize functions such as data transmission and message interaction with the server 102 through the client. The client may be a client including a sign-in function installed on the terminal 101. For example, the client may be a browser, a social application, a game application, a live broadcast application, or a food delivery application.

[0083] The terminal 101 may be a computer, a mobile phone, a tablet computer or other devices. The server 102 may be a server, or a server cluster consisting of several servers, or a cloud computing service center.

[0084] The method for updating the sign-in information can be applied in multiple scenarios.

[0085] For example, in a scenario where coupons are distributed to users based on the number of times the user signs in continuously, a sign-in button is provided in the display interface of the terminal, and the terminal sends a sign-in request to the server in response to the triggering operation of the sign-in button. The server receives the sign-in request and updates the number of consecutive sign-ins of the user based on the method for updating the sign-in information in the embodiment of the present application. The server determines the number of consecutive sign-ins of the user based on the updated cumulative sign-in information, and distributes coupons to the user when the number of consecutive sign-ins of the user reaches a preset number.

[0086] For another example, in a scenario where gold coins are distributed to users according to the number of times the user signs in continuously, a sign-in button is provided in the display interface of the terminal, and the terminal sends a sign-in request to the server in response to the triggering operation of the sign-in button. The server receives the sign-in request and updates the user's cumulative sign-in information based on the sign-in information update method in the embodiment of the present application. The server determines the number of consecutive sign-ins of the user based on the updated cumulative sign-in information, and when the number of consecutive sign-ins of the user reaches a preset number, the gold coins corresponding to the number of consecutive sign-ins are distributed to the user.

[0087] For another example, in a scenario where a user is given a chance to win a lottery when the number of consecutive sign-ins reaches a preset number, a sign-in button is provided in the display interface of the terminal, and the terminal sends a sign-in request to the server in response to the triggering operation of the sign-in button. The server receives the sign-in request and updates the user's cumulative sign-in information based on the method for updating the sign-in information in the embodiment of the present application. The server determines the number of consecutive sign-ins of the user based on the updated cumulative sign-in information, and when the number of consecutive sign-ins of the user reaches the preset number, the user is given a chance to win a lottery.

[0088] Figure 2 is a flow chart of a method for updating sign-in information provided by an embodiment of the present application. Figure 2 , the method for updating the sign-in information includes the following steps:

[0089] 201. Receive a sign-in request from a first target account.

[0090] 202. In response to the sign-in request, obtain first sign-in cumulative information and sign-in time information corresponding to the first target account, where the first sign-in cumulative information is obtained by accumulating historical sign-in information of the first target account, and the sign-in time information includes the most recent sign-in time of the first target account.

[0091] 203. Update the first sign-in cumulative information based on the current time and the most recent sign-in time.

[0092] In a possible implementation, based on the current time and the most recent sign-in time, updating the first sign-in cumulative information includes:

[0093] Determine the time interval between the current time and the most recent check-in time;

[0094] Determine, based on the time interval, sign-in status information corresponding to the target account, where the sign-in status information includes one of a continuous sign-in status and a disconnected sign-in status;

[0095] Based on the sign-in status information, the first sign-in cumulative information is updated.

[0096] In another possible implementation, the first sign-in cumulative information includes at least the most recent consecutive sign-in times;

[0097] Based on the sign-in status information, the first sign-in cumulative information is updated, including:

[0098] If the target account is in a continuous sign-in state, update the most recent continuous sign-in times;

[0099] If the target account is in a disconnected state, determine the current number of disconnections, and update the first sign-in cumulative information based on the current number of disconnections.

[0100] In another possible implementation, based on the current number of sign-off interruptions, updating the first sign-in cumulative information includes:

[0101] Add the sign-off mark, the current sign-off times and the number of consecutive sign-ins after sign-off to the first sign-in cumulative information.

[0102] In another possible implementation, the first sign-in cumulative information further includes a sign-off mark and the number of most recent sign-off times;

[0103] Based on the current number of sign-in breaks, update the first sign-in cumulative information, including:

[0104] Update the most recent sign-in disconnection count to the current sign-in disconnection count, and add the number of consecutive sign-ins after the sign-in disconnection to the first sign-in cumulative information.

[0105] In another possible implementation, the method further includes:

[0106] receiving a query request, the query request carrying a first target account;

[0107] In response to the query request, the most recent number of consecutive check-ins is determined from the first check-in cumulative information.

[0108] In another possible implementation, the first sign-in cumulative information further includes a sign-off mark and the number of most recent sign-off times;

[0109] Determine the most recent consecutive check-in times from the first check-in cumulative information, including:

[0110] Determine the last text message from the first sign-in cumulative information;

[0111] If the text information is a symbol, it is determined that the most recent consecutive check-in times is zero; if the text information is a number, it is determined that the number is the most recent consecutive check-in times.

[0112] In another possible implementation, the time interval is a date interval; based on the time interval, determining the check-in status information corresponding to the target account includes:

[0113] In response to the date interval being one day, the target account is determined to be in a continuous sign-in state; in response to the date interval being greater than one day, the target account is determined to be in a broken sign-in state.

[0114] In another possible implementation, the method further includes:

[0115] Update the last check-in time of the first target account to the current time.

[0116] An embodiment of the present application provides a method for updating sign-in information. Since the historical sign-in information of the first target account is accumulated through the first sign-in accumulation information, when the sign-in request of the first target account is received, there is no need to create additional sign-in record information. Instead, the first sign-in accumulation information is updated according to the current time and the most recent sign-in time. In this way, for any first target account, only one sign-in accumulation information needs to be stored, thereby saving the memory occupied by the sign-in accumulation information of the target account. Therefore, the method for updating sign-in information reduces memory usage.

[0117] Figure 3 is a flow chart of a method for updating sign-in information provided by an embodiment of the present application. Figure 3 , the method for updating the sign-in information includes the following steps:

[0118] 301. Receive a request for a supplementary signature from a second target account.

[0119] 302. In response to the request for a make-up sign-in, obtain second check-in cumulative information corresponding to the second target account, where the second check-in cumulative information is obtained by accumulating historical check-in information of the second target account, and the second check-in cumulative information includes the last consecutive check-in times, the most recent check-in interruption times, and the most recent consecutive check-in times.

[0120] 303. Update the second sign-in cumulative information.

[0121] In a possible implementation, updating the second sign-in accumulation information includes:

[0122] In response to the most recent number of disconnections being greater than one, the most recent number of disconnections being reduced by one;

[0123] In response to the most recent disconnection number being one, the most recent disconnection number and the disconnection flag are deleted, and the most recent continuous sign-in number and the last continuous sign-in number are updated to the sum of the most recent continuous sign-in number and the last continuous sign-in number.

[0124] An embodiment of the present application provides a method for updating sign-in information. Since the second sign-in cumulative information corresponding to the target account is updated each time a sign-in request is received from a target account, only one record information needs to be stored for the same target account, thereby saving the memory occupied by the sign-in cumulative information. Therefore, the method for updating sign-in information reduces memory usage.

[0125] Figure 4 This is a flow chart of a method for updating sign-in information provided in an embodiment of the present application, which is executed by a server. The update method is described by taking a user signing in based on a sign-in button as an example; see Figure 4 , the method for updating the sign-in information includes the following steps:

[0126] 401. The server receives a sign-in request from a first target account.

[0127] In a possible implementation, a client including a sign-in function is installed on the terminal, and a sign-in button is provided in the display interface of the client; the first target account is any registered account on the client, and when the user of the first target account intends to sign in, the sign-in button in the display interface is triggered. Accordingly, this step is: in response to the triggering operation of the sign-in button, the terminal sends a sign-in request to the server, and the sign-in request carries the first target account. The server receives the sign-in request sent by the terminal. Optionally, the first target account includes symbols such as numbers and letters. For example, the first target account is userpin001.

[0128] 402. In response to the sign-in request, the server obtains first sign-in cumulative information and sign-in time information corresponding to the first target account, where the first sign-in cumulative information is obtained by accumulating historical sign-in information of the first target account, and the sign-in time information includes the most recent sign-in time of the first target account.

[0129] In a possible implementation, the server stores a correspondence between the account and the cumulative sign-in information. Accordingly, the process of the server obtaining the first cumulative sign-in information corresponding to the first target account is as follows: the server responds to the sign-in request and determines the first cumulative sign-in information corresponding to the first target account from the correspondence between the account and the cumulative sign-in information based on the first target account. Optionally, the server stores first key information in the cache middleware, and the first key information includes the correspondence between the account and the cumulative sign-in information.

[0130] In the embodiment of the present application, since the correspondence between the account and the sign-in cumulative information is stored through the first key information, when a sign-in request from the first target account is received, it is only necessary to update the first sign-in cumulative information in the first key information without creating new sign-in record information. In this way, for any first target account, only one sign-in cumulative information needs to be stored, thereby saving the memory occupied by the sign-in cumulative information of the target account. Therefore, the method for updating the sign-in information reduces the memory usage.

[0131] In another possible implementation, the check-in request also carries a service identifier and a first function identifier. Multiple first key information are stored in the server. The first key information includes the correspondence between the service identifier, the account number, the function identifier, and the check-in cumulative information. Accordingly, the process of the server obtaining the first check-in cumulative information corresponding to the first target account is as follows: the server responds to the check-in request, and based on the service identifier and the first function identifier, determines multiple first target key information corresponding to the check-in service and the continuous check-in function from multiple first key information; determines the first key information corresponding to the first target account from the multiple first target key information, and obtains the first check-in cumulative information corresponding to the first target account.

[0132] For example, the first key information corresponding to the first target account is: sign:userpin001:day=5, where "sign" indicates the sign-in service, "userpin001" indicates the first target account, "day" indicates the first function identifier corresponding to continuous sign-in, and "5" indicates the number of continuous sign-ins is 5 times.

[0133] In the embodiment of the present application, since the correspondence between the service identifier, account number, function identifier and sign-in cumulative information is stored through the first key information, when a sign-in request from the first target account is received, it is only necessary to update the first sign-in cumulative information in the first key information without creating new sign-in record information. In this way, for any first target account, only one sign-in cumulative information needs to be stored, thereby saving the memory occupied by the sign-in cumulative information of the target account, so the sign-in information updating method reduces the memory occupancy rate.

[0134] In a possible implementation, the server stores a correspondence between the account and the check-in time information. Accordingly, the server obtains the check-in time information corresponding to the first target account as follows: the server responds to the check-in request and determines the check-in time information corresponding to the target account from the correspondence between the account and the check-in time information based on the target account corresponding to the first target account. Optionally, the server stores second key information in the cache middleware, and the second key information includes the correspondence between the account and the check-in time information.

[0135] In the embodiment of the present application, since the correspondence between the account and the check-in time information is stored through the second key information, when the target user corresponding to the account triggers the check-in operation, it is only necessary to update the check-in time information in the second key information without creating new record information. In this way, for a target account, only one check-in time information needs to be stored, thereby saving the memory occupied by the check-in time information and reducing the memory usage rate.

[0136] In another possible implementation, the check-in request also carries a service identifier and a second function identifier. Multiple second key information is stored in the server. The second key information includes the correspondence between the service identifier, account number, function identifier, and check-in time information. Accordingly, the process of the server obtaining the check-in time information corresponding to the first target account is as follows: the server responds to the check-in request, and based on the service identifier and the second function identifier, determines multiple second target key information corresponding to the check-in service and check-in time function from multiple second key information; determines the second key information corresponding to the first target account from the multiple second target key information, and obtains the check-in time information corresponding to the first target account.

[0137] For example, the second key information corresponding to the first target account is: sign:userpin001:lastsignday=20210717. Among them, "sign" represents the sign-in service, "userpin001" represents the first target account, "lastsignday" represents the second function identifier corresponding to the last sign-in time, and "20210717" represents the last sign-in time.

[0138] In an embodiment of the present application, since the correspondence between the service identifier, account number, function identifier and check-in time information is stored through the second key information, when the target user corresponding to the account triggers a check-in operation, it is only necessary to update the check-in time information in the second key information without creating new record information. In this way, for a target account, only one check-in time information needs to be stored, thereby saving the memory occupied by the check-in time information and reducing the memory usage rate.

[0139] It should be noted that the first sign-in cumulative information may include only the number of consecutive sign-ins, or may include the number of consecutive sign-ins, the number of sign-offs, and the sign-off mark. When the first sign-in cumulative information includes only the number of consecutive sign-ins, it means that the first target account has not been sign-offed and has been signing in continuously. When the first sign-in cumulative information includes the number of consecutive sign-ins, the number of sign-offs, and the sign-off mark, it means that the first target account has been sign-offed.

[0140] Another point to note is that see Figure 5 , if the server obtains the first sign-in cumulative information as empty, it is determined that the first target account is signing in for the first time. At this time, the server no longer obtains the sign-in time information of the first target account, and directly creates the first key information and the second key information based on the current sign-in time. Optionally, the first key information includes the correspondence between the first business identifier, the first target account, the first function identifier, and the first sign-in cumulative information; the second key information includes the correspondence between the second business identifier, the first target account, the second function identifier, and the sign-in time information. Among them, the first sign-in cumulative information in the first key information is the number of sign-ins this time "1", and the sign-in time information in the second key information is the current sign-in time. For example, based on the current sign-in time, the first key information created by the server is: sign:userpin001:day=1, and the second key information is: sign:userpin001:lastsignday=20210717.

[0141] 403. The server updates the first sign-in cumulative information based on the current time and the most recent sign-in time.

[0142] In a possible implementation, if the last sign-in time is yesterday, it means that this sign-in is a continuous sign-in, and only the number of continuous sign-ins needs to be updated. If the last sign-in time is not yesterday, it means that there was a sign-in break before this sign-in, and the number of sign-in breaks and the number of continuous sign-ins need to be updated. Accordingly, this step includes the following steps (1) to (3):

[0143] (1) The server determines the time interval between the current time and the most recent check-in time.

[0144] Optionally, the time interval is a date interval. Accordingly, this step is: the server determines a first date corresponding to the current time and a second date corresponding to the most recent sign-in time, and determines the date interval between the current time and the most recent sign-in time based on the first date and the second date.

[0145] Optionally, the time interval is an interval duration. Accordingly, this step is: the server determines a time difference between the current time and the most recent check-in time, and determines the time difference as the interval duration between the current time and the most recent check-in time.

[0146] (2) The server determines the sign-in status information corresponding to the target account based on the time interval, where the sign-in status information includes one of a continuous sign-in status and a disconnected sign-in status.

[0147] In a possible implementation, the time interval is a date interval. Accordingly, this step is: in response to the time interval being no greater than one day, the server determines that the target account is in a continuous sign-in state; in response to the time interval being greater than one day, the server determines that the target account is in a broken sign-in state.

[0148] For example, see Figure 5 If the time interval is not greater than one day and the most recent sign-in time is determined to be yesterday, this indicates that this sign-in is a continuous sign-in; if the time interval is greater than one day and the most recent sign-in time is determined not to be yesterday, this indicates that there was a sign-in break before this sign-in.

[0149] In the embodiment of the present application, the check-in status information of the first target user is determined by date interval, which conforms to the actual application scenario and increases the flexibility of the determined check-in status information.

[0150] In a possible implementation, the time interval is the interval duration. Accordingly, this step is: in response to the interval duration being no greater than the first preset duration, the server determines that the target account is in a continuous sign-in state; in response to the interval duration being greater than the first preset duration, the server determines that the target account is in a disconnected sign-in state. In the embodiment of the present application, the value of the first preset duration is not specifically limited and can be set and modified as needed. For example, the first preset duration can be 4 hours, 5 hours, 6 hours, etc.

[0151] In the embodiment of the present application, the check-in status information of the first target user is determined by the interval duration, and the interval duration is a precise time, thereby increasing the accuracy of the determined check-in status information.

[0152] (3) The server updates the first sign-in accumulation information based on the sign-in status information.

[0153] In this step, the sign-in status information includes one of a continuous sign-in status and a disconnected sign-in status. Different sign-in statuses have different updated contents of the first sign-in accumulated information.

[0154] In one possible implementation, the first sign-in cumulative information includes at least the most recent consecutive sign-in times; accordingly, this step is: if the target account is in a continuous sign-in state, the server updates the most recent consecutive sign-in times; if the target account is in a sign-off state, the server determines the current sign-off times, and updates the first sign-in cumulative information based on the current sign-off times.

[0155] Optional, continue to see Figure 5, the server updates the most recent consecutive sign-in times as follows: the server adds one to the most recent consecutive sign-in times. For example: the most recent consecutive sign-in times is "5", if the target account is in a continuous sign-in state, the server updates the most recent consecutive sign-in times to "6".

[0156] Optionally, the step of the server determining the current number of broken signatures is: the server determines the number of days in the date interval as the number of broken signatures; or determines the ratio of the interval duration to the first preset duration as the number of broken signatures. It should be noted that if the ratio of the interval duration to the first preset duration is an integer, the integer is directly determined as the number of broken signatures; if the ratio of the interval duration to the first preset duration is not an integer, the integer digit is determined as the number of broken signatures.

[0157] In an embodiment of the present application, the server determines the content of the first sign-in cumulative information that needs to be updated based on whether the status of the target account is a continuous sign-in status, thereby ensuring the integrity and accuracy of the updated first sign-in cumulative information.

[0158] In one possible implementation, see Figure 5 , after the last continuous sign-in, the first sign-in cumulative information has not been updated. At this time, the first sign-in cumulative information includes the most recent continuous sign-in times, and the number of sign-ins after sign-ins are required to be supplemented. Accordingly, the server updates the first sign-in cumulative information based on the current sign-in times: the server adds a sign-in break identifier, the current sign-in break times, and the number of continuous sign-ins after sign-ins are broken in the first sign-in cumulative information. Among them, the number of continuous sign-ins after sign-ins are broken is 1.

[0159] For example: the first sign-in cumulative information includes the most recent consecutive sign-in times of "4", and the current sign-in breaks times of 3. The server adds the sign-in break identifier, the current sign-in break times and the number of consecutive sign-ins after the sign-in break to the first sign-in cumulative information, and the updated first sign-in cumulative information is: "4_03_1"; wherein, "0" represents the sign-in break identifier, and the number after the sign-in break identifier represents the sign-in break times; "_" represents a separator, and the sign-in break times and the number of consecutive sign-ins are separated by a separator, and the number of consecutive sign-ins and the sign-in break identifier are separated by a separator; "1" indicates that the number of consecutive sign-ins after the sign-in break is 1 time.

[0160] In the embodiment of the present application, when there is no sign-off information in the first sign-on cumulative information, the sign-off information such as the sign-off mark and the sign-off number are updated to ensure the integrity and accuracy of the updated first sign-on cumulative information.

[0161] In another possible implementation, after the sign-in is disconnected, the first sign-in cumulative information is updated, and at this time, the first sign-in cumulative information also includes the sign-in disconnection identifier and the most recent sign-in disconnection number. Accordingly, the server updates the first sign-in cumulative information based on the current sign-in disconnection number as follows: the server updates the most recent sign-in disconnection number to the current sign-in disconnection number, and adds the number of consecutive sign-ins after the sign-in disconnection to the first sign-in cumulative information. The number of consecutive sign-ins after the sign-in disconnection is 1.

[0162] For example: the first sign-in cumulative information includes the most recent consecutive sign-in times, the sign-off mark and the most recent sign-off times "4_02_", the current sign-off times is 3, the server updates the most recent sign-off times 2 to the current sign-off times 3, and adds the number of consecutive sign-ins after sign-off times 1 to the first sign-in cumulative information, and the updated first sign-in cumulative information is: "4_03_1".

[0163] In an embodiment of the present application, when the first sign-in cumulative information includes sign-off information, the sign-off number is updated to the current sign-off number to ensure the accuracy of the updated sign-off number, thereby improving the completeness and accuracy of the updated first sign-in cumulative information.

[0164] It should be noted that a user may sign in and out of the sign-in multiple times continuously. Accordingly, the number of sign-outs in the first sign-in cumulative information may include multiple numbers, and the number of continuous sign-ins may include multiple numbers. When the first sign-in cumulative information includes multiple information such as the number of sign-outs and the number of continuous sign-ins, the number of sign-outs and the number of continuous sign-ins are separated by a spacing symbol. For example, the first sign-in cumulative information is: 20_01_3_02_1_01_11.

[0165] Another point that needs to be explained is that the server updates the first sign-in cumulative information of the first target account and obtains the updated first sign-in cumulative information. When the server receives the sign-in request of the first target account next time, the first sign-in cumulative information obtained by the server is the first sign-in cumulative information after this update.

[0166] 404. The server updates the last check-in time of the first target account to the current time.

[0167] In the embodiment of the present application, the server updates the first check-in cumulative information of the first target account, and after obtaining the updated first check-in cumulative information, it also updates the most recent check-in time. Figure 5, the server updates the last check-in time of the first target account to the current time and obtains the updated check-in time information. When receiving the check-in request of the first target account again, the check-in time information obtained by the server is the updated check-in time information. For example, the server updates the last check-in time of the first target account to 20210717.

[0168] An embodiment of the present application provides a method for updating sign-in information. Since the historical sign-in information of the first target account is accumulated through the first sign-in accumulation information, when the sign-in request of the first target account is received, there is no need to create additional sign-in record information. Instead, the first sign-in accumulation information is updated according to the current time and the most recent sign-in time. In this way, for any first target account, only one sign-in accumulation information needs to be stored, thereby saving the memory occupied by the sign-in accumulation information of the target account. Therefore, the method for updating sign-in information reduces memory usage.

[0169] It should be noted that when it is necessary to determine the most recent consecutive sign-in times of the first target account, the server may also determine the most recent consecutive sign-in times of the first target account based on the query request of the first target account. Figure 6 The method for updating the sign-in information further includes steps 405 and 406:

[0170] 405. The server receives a query request, where the query request carries the first target account.

[0171] In a possible implementation, a query button is provided in the terminal display interface. Accordingly, this step is: the terminal sends a query request to the server in response to the triggering operation of the query button, and the query request carries the first target account. The server receives the query request sent by the terminal.

[0172] In the embodiment of the present application, the user can independently query the check-in cumulative information based on the query button in the terminal display interface, thereby improving the flexibility of querying information.

[0173] In another possible implementation, a preset query time is stored in the server, and a query request is generated when the current time reaches the preset query time. Accordingly, this step is: in response to the current time reaching the preset query time, the server generates a query request, and the query request carries the first target account. Optionally, the interval between the preset query time and the last query time is a second preset duration. In the embodiment of the present application, the value of the second preset duration is not specifically limited and can be set and modified as needed. For example, the second preset duration can be 12 hours, 24 hours, etc.

[0174] In the embodiment of the present application, the server autonomously queries the user's check-in cumulative information based on a preset query time, thereby improving the intelligence of the query information.

[0175] 406. In response to the query request, the server determines the most recent number of consecutive sign-ins from the first sign-in cumulative information.

[0176] In a possible implementation, the first sign-in cumulative information includes at least the most recent consecutive sign-in times, and the server stores a correspondence between the account and the sign-in cumulative information. Accordingly, the server determines the most recent consecutive sign-in times from the first sign-in cumulative information as follows: the server determines the first sign-in cumulative information corresponding to the first account identifier from the stored correspondence between the account and the sign-in cumulative information based on the first target account, and determines the most recent consecutive sign-in times from the first sign-in cumulative information.

[0177] In another possible implementation, the first sign-in cumulative information includes the most recent consecutive sign-in times, the sign-off mark, and the most recent sign-off times. Accordingly, the step of the server determining the most recent consecutive sign-in times from the first sign-in cumulative information is as follows: the server determines the first sign-in cumulative information corresponding to the first account mark from the correspondence between the stored account and the sign-in cumulative information based on the first target account, and determines the last text information from the first sign-in cumulative information; if the text information is a symbol, the consecutive sign-in times corresponding to the first target account are determined to be zero; if the text information is a number, the number is determined to be the consecutive sign-in times corresponding to the first target account.

[0178] For example, if the second check-in cumulative information is 4_03_ and the last text information is the number "_", then the number of consecutive check-ins corresponding to the second target account is determined to be 0. For another example, if the second check-in cumulative information is 4_03_3 and the last text information is the number "3", then the number "3" is determined to be the number of consecutive check-ins corresponding to the second target account.

[0179] In the embodiment of the present application, since the server directly determines the number of consecutive check-ins corresponding to the target account from the first check-in cumulative information based on the first target account, that is, when determining the number of consecutive check-ins, only one record information needs to be obtained, without extracting multiple record information for calculation, thereby reducing the complexity of determining the number of consecutive check-ins, and thus improving the efficiency of querying the check-in information.

[0180] Figure 7 This is a flow chart of a method for updating sign-in information provided in an embodiment of the present application, which is executed by a server. The updating method is described by taking the example of a user making a make-up sign based on a make-up sign button. Figure 7 , the method for updating the sign-in information includes the following steps:

[0181] 701. The server receives a request for a supplementary signature from a second target account.

[0182] In an embodiment of the present application, when a user has a broken signature, he or she can also obtain a chance to make up the signature by completing relevant operations. For example, completing 30 seconds of web browsing; for another example, completing the download of the XX client, etc. After completing the task-related operations, the terminal displays a make-up signature button on the display interface, and the user can trigger a make-up signature request based on the make-up signature button. Accordingly, this step is: the terminal responds to the triggering operation of the make-up signature button and sends a make-up signature request to the server, and the make-up signature request carries a second target account. The server receives the make-up signature request for the second target account sent by the terminal. Optionally, the second target account is a registered account on the client that has a broken signature.

[0183] 702. In response to the request for supplementary sign-in, the server obtains second sign-in cumulative information corresponding to the second target account, where the second sign-in cumulative information is obtained by accumulating historical sign-in information of the second target account, and the second sign-in cumulative information includes the last consecutive sign-in times and the most recent sign-in interruption times.

[0184] In one possible implementation, the second check-in cumulative information includes the last consecutive check-in number and the most recent check-in number. For example, the second check-in cumulative information is: 4_02_. In another possible implementation, the second check-in cumulative information includes the last consecutive check-in number, the most recent check-in number, and the most recent consecutive check-in number. For example, the second check-in cumulative information is: 4_02_2. The method by which the server obtains the second check-in cumulative information corresponding to the second target account is the same as the method by which the server obtains the first check-in cumulative information corresponding to the first target account in step 301, and will not be repeated here.

[0185] 703. The server updates the second sign-in cumulative information.

[0186] In a possible implementation, the second check-in cumulative information includes the last consecutive check-in number, the last disconnection number, and the last consecutive check-in number. Accordingly, this step is: in response to the last disconnection number being greater than one, the server subtracts one from the last disconnection number; in response to the last disconnection number being one, the server deletes the last disconnection number and the disconnection mark, and updates the last consecutive check-in number and the last consecutive check-in number to the sum of the last consecutive check-in number and the last consecutive check-in number.

[0187] For example, the second sign-in cumulative information is 4_02_2; if the last sign-in interruption number is greater than one, the server will subtract one from the last sign-in interruption number, and the updated second sign-in cumulative information is 4_01_2. Among them, "0" represents the sign-in interruption mark, "_" represents the separator, "1" is the updated sign-in interruption number, "4" is the last consecutive sign-in number, and "2" is the most recent consecutive sign-in number.

[0188] In another possible implementation, the second sign-in cumulative information includes the last consecutive sign-in times and the most recent sign-off times. Accordingly, this step is: in response to the most recent sign-off times being greater than one, the server subtracts one from the most recent sign-off times; in response to the most recent sign-off times being one, the server deletes the most recent sign-off times and the sign-off flag.

[0189] For example, the second check-in cumulative information is 4_02_; if the number of the most recent sign-in interruption is greater than one, the server subtracts one from the number of the most recent sign-in interruption, and the updated second check-in cumulative information is 4_01_. For another example, the second check-in cumulative information is 4_01_; if the number of the most recent sign-in interruption is one, the server deletes the number of the most recent sign-in interruption and the sign-in interruption mark, and the updated second check-in cumulative information is 4.

[0190] One thing that needs to be explained is that when there are multiple sign-off times in the second sign-in cumulative information, the server can update the most recent sign-off time, or determine the sign-off time with the smallest value from multiple sign-off times for update, or update the sign-off time selected by the target account based on the operation of the target account.

[0191] In a possible implementation, the server updates the number of sign-offs selected by the target account based on the operation of the target account in the following specific steps: a highlight button and a gray button are displayed in the display interface of the terminal, wherein the highlight button corresponds to the signed-in date, and the gray button corresponds to the unsigned-in date; in response to the target gray button corresponding to the unsigned-in date being triggered, the terminal sends a sign-on request to the server, and the sign-on request carries the second target account number and the sign-on date. Correspondingly, the server updates the number of sign-offs corresponding to the sign-on date according to the sign-on date.

[0192] In an embodiment of the present application, the server updates the number of sign-off breaks selected by the target account, and the number of sign-off breaks selected by the target account is the number of sign-off breaks that the target account most needs to make up, thereby improving the personalized needs of the method for updating the sign-in information.

[0193] An embodiment of the present application provides a method for updating sign-in information. Since the historical sign-in information of a second target account is accumulated through the second sign-in accumulation information, when a request for a make-up sign-in from the second target account is received, there is no need to create additional sign-in record information. Instead, the second sign-in accumulation information is updated. In this way, for any second target account, only one sign-in accumulation information needs to be stored, thereby saving the memory occupied by the sign-in accumulation information of the target account. Therefore, the method for updating sign-in information reduces memory usage.

[0194] Figure 8 Schematic diagram of a device for updating sign-in information provided in an embodiment of the present application. Figure 8 , the device comprises:

[0195] A first receiving module 801 is used to receive a sign-in request from a first target account;

[0196] A first acquisition module 802 is configured to acquire, in response to the sign-in request, first sign-in accumulation information and sign-in time information corresponding to the first target account, wherein the first sign-in accumulation information is obtained by accumulating historical sign-in information of the first target account, and the sign-in time information includes the most recent sign-in time of the first target account;

[0197] The first updating module 803 is used to update the first sign-in accumulation information based on the current time and the most recent sign-in time.

[0198] In one possible implementation, see Fig. 9 , the first update module 803 includes:

[0199] The first determining unit 8031 ​​is used to determine the time interval between the current time and the most recent check-in time;

[0200] The second determining unit 8032 is used to determine the sign-in status information corresponding to the target account based on the time interval, where the sign-in status information includes one of a continuous sign-in status and a disconnected sign-in status;

[0201] The updating unit 8033 is configured to update the first sign-in accumulation information based on the sign-in status information.

[0202] In another possible implementation, the first sign-in cumulative information includes at least the most recent consecutive sign-in times; the updating unit 8033 is used to update the most recent consecutive sign-in times if the target account is in a continuous sign-in state; if the target account is in a sign-off state, determine the current sign-off times, and update the first sign-in cumulative information based on the current sign-off times.

[0203] In another possible implementation, the updating unit 8033 is configured to add a sign-off mark, a current sign-off number, and a number of consecutive sign-ins after sign-off to the first sign-in cumulative information.

[0204] In another possible implementation, the first sign-in cumulative information also includes a sign-off mark and the most recent sign-off number; the updating unit 8033 is used to update the most recent sign-off number to the current sign-off number, and to add the number of consecutive sign-ins after sign-off to the first sign-in cumulative information.

[0205] In another possible implementation, see Fig. 9 , the device further comprises:

[0206] The first receiving module is further used to receive a query request, where the query request carries a first target account;

[0207] The first determining module 804 is configured to determine the most recent consecutive check-in times from the first check-in cumulative information in response to the query request.

[0208] In another possible implementation, the first sign-in cumulative information also includes a sign-off mark and the most recent sign-off number; the first determination module 804 is further used to determine the last text information from the first sign-in cumulative information; if the text information is a symbol, the most recent consecutive sign-in number is determined to be zero; if the text information is a number, the number is determined to be the most recent consecutive sign-in number.

[0209] In another possible implementation, the second determining unit 8032 is configured to determine that the target account is in a continuous sign-in state in response to the date interval being one day; and determine that the target account is in a disconnected sign-in state in response to the date interval being greater than one day.

[0210] In another possible implementation, the first updating module 803 is further configured to update the most recent check-in time of the first target account to the current time.

[0211] The embodiment of the present application provides a device for updating sign-in information. Since the historical sign-in information of the first target account is accumulated through the first sign-in accumulation information, when the sign-in request of the first target account is received, there is no need to create additional sign-in record information. Instead, the first sign-in accumulation information is updated according to the current time and the most recent sign-in time. In this way, for any first target account, only one sign-in accumulation information needs to be stored, thereby saving the memory occupied by the sign-in accumulation information of the target account. Therefore, the method for updating the sign-in information reduces the memory usage rate.

[0212] Fig.10 Schematic diagram of a device for updating sign-in information provided in an embodiment of the present application. Fig.10 , the device comprises:

[0213] The second receiving module 1001 is used to receive a request for a supplementary signature from a second target account;

[0214] The second receiving module 1002 is used to obtain second check-in cumulative information corresponding to the second target account in response to the check-in request, where the second check-in cumulative information is obtained by accumulating historical check-in information of the second target account, and the second check-in cumulative information includes the last consecutive check-in times, the most recent check-in interruption times, and the most recent consecutive check-in times;

[0215] The second updating module 1003 is used to update the second sign-in accumulation information.

[0216] In one possible implementation, the second update module 1003 is used to, in response to the most recent number of disconnections being greater than one, subtract one from the most recent number of disconnections; in response to the most recent number of disconnections being one, delete the most recent number of disconnections and the disconnection flag, and update the most recent number of consecutive sign-ins and the last number of consecutive sign-ins to the sum of the most recent number of consecutive sign-ins and the last number of consecutive sign-ins.

[0217] The embodiment of the present application provides a device for updating sign-in information. Since the historical sign-in information of the second target account is accumulated through the second sign-in cumulative information, when a request for a make-up sign-in from the second target account is received, there is no need to create additional sign-in record information, but the second sign-in cumulative information is updated. In this way, for any second target account, only one sign-in cumulative information needs to be stored, thereby saving the memory occupied by the sign-in cumulative information of the target account. Therefore, the method for updating sign-in information reduces memory usage.

[0218] It should be noted that: the update device for the sign-in information provided in the above embodiment only uses the division of the above functional modules as an example when updating the sign-in information. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the server is divided into different functional modules to complete all or part of the functions described above. In addition, the update device for the sign-in information provided in the above embodiment and the update method embodiment of the sign-in information belong to the same concept. The specific implementation process is detailed in the method embodiment and will not be repeated here.

[0219] Fig.111 is a schematic diagram of the structure of a server provided in an embodiment of the present application. The server 1100 may have relatively large differences due to different configurations or performances, and may include one or more processors (central processing units, CPU) 1101 and one or more memories 1102, wherein the memory 1102 stores at least one program code, and at least one program code is loaded and executed by the processor 1101 to implement the update method of the check-in information provided in the above-mentioned various method embodiments. Of course, the server may also have components such as a wired or wireless network interface, a keyboard, and an input and output interface for input and output, and the server may also include other components for implementing device functions, which will not be described in detail here.

[0220] An embodiment of the present application further provides a computer-readable storage medium, in which at least one program code is stored. The at least one program code is loaded by a processor and has the function of implementing the operations in the method for updating the check-in information in the above embodiment.

[0221] The embodiment of the present application also provides a computer program product. When the instructions in the computer program product are executed by the processor of the server, the server can execute the method for updating the check-in information in the above-mentioned various method embodiments.

[0222] A person skilled in the art will appreciate that all or part of the steps to implement the above embodiments may be accomplished by hardware or by instructing related hardware through a program, and the program may be stored in a storage medium, which may be a read-only memory, a disk, or an optical disk, etc.

[0223] The above description is only an optional embodiment of the embodiments of the present application and is not intended to limit the embodiments of the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the embodiments of the present application should be included in the protection scope of the present application.

Claims

1. A method for updating sign-in information, characterized in that: The method comprises: Receiving a sign-in request from a first target account; In response to the sign-in request, first sign-in cumulative information and sign-in time information corresponding to the first target account are obtained, wherein the first sign-in cumulative information is obtained by accumulating historical sign-in information of the first target account, and the sign-in time information includes the most recent sign-in time of the first target account, wherein the server stores first key information in the cache middleware, and the first key information includes a corresponding relationship between an account and the first sign-in cumulative information, and for the first target account, only one first sign-in cumulative information is stored; Based on the current time and the most recent sign-in time, only the first sign-in cumulative information in the first key information is updated without creating new first sign-in record information.

2. The method according to claim 1, characterized in that The updating of the first sign-in accumulation information based on the current time and the most recent sign-in time includes: Determine the time interval between the current time and the most recent check-in time; Based on the time interval, determine the sign-in status information corresponding to the target account, where the sign-in status information includes one of a continuous sign-in status and a disconnected sign-in status; Based on the sign-in status information, the first sign-in accumulation information is updated.

3. The method according to claim 2, characterized in that The first check-in cumulative information includes at least the most recent consecutive check-in times; The updating of the first sign-in accumulation information based on the sign-in status information includes: If the target account is in a continuous sign-in state, update the most recent continuous sign-in times; If the target account is in a disconnected state, determine the current number of disconnected times, and update the first sign-in accumulation information based on the current number of disconnected times.

4. The method according to claim 3, characterized in that The updating of the first sign-in accumulation information based on the current number of sign-out interruptions includes: The sign-in break mark, the current sign-in break times and the number of consecutive sign-ins after sign-in break are added to the first sign-in cumulative information.

5. The method according to claim 3, characterized in that: The first sign-in cumulative information also includes a sign-off mark and the number of the most recent sign-off times; The updating of the first sign-in accumulation information based on the current number of sign-out interruptions includes: The most recent number of sign-in breaks is updated to the current number of sign-in breaks, and the number of consecutive sign-ins after sign-in breaks is added to the first sign-in cumulative information.

6. The method according to claim 3, characterized in that The method further comprises: receiving a query request, wherein the query request carries the first target account; In response to the query request, the most recent consecutive check-in times are determined from the first check-in cumulative information.

7. The method according to claim 6, characterized in that The first sign-in cumulative information also includes a sign-off mark and the number of the most recent sign-off times; The determining the most recent consecutive sign-in times from the first sign-in accumulated information includes: Determine the last text message from the first sign-in accumulated information; If the text information is a symbol, it is determined that the most recent consecutive sign-in number is zero; if the text information is a number, it is determined that the number is the most recent consecutive sign-in number.

8. The method according to claim 2, characterized in that: The time interval is a date interval; and determining the check-in status information corresponding to the target account based on the time interval includes: In response to the date interval being one day, determining that the target account is in a continuous sign-in state; in response to the date interval being greater than one day, determining that the target account is in a disconnected sign-in state.

9. The method according to claim 1, characterized in that: The method further comprises: The last check-in time of the first target account is updated to the current time.

10. A method for updating sign-in information, characterized in that: The method comprises: Receive a request for a supplementary signature from the second target account; In response to the request for supplementary sign-in, obtaining second sign-in cumulative information corresponding to the second target account, the second sign-in cumulative information being obtained by accumulating historical sign-in information of the second target account, the second sign-in cumulative information including the last consecutive sign-in times, the most recent sign-in interruption times, and the most recent consecutive sign-in times, wherein the server stores second key information in the cache middleware, the second key information including the correspondence between the account and the second sign-in cumulative information, and only one second sign-in cumulative information is stored for the second target account; Only the second sign-in cumulative information in the second key information is updated without creating new second sign-in record information.

11. The method according to claim 10, characterized in that The updating of the second sign-in accumulated information includes: In response to the most recent number of disconnections being greater than one, subtracting one from the most recent number of disconnections; In response to the most recent disconnection number being one, the most recent disconnection number and the disconnection flag are deleted, and the most recent continuous sign-in number and the last continuous sign-in number are updated to the sum of the most recent continuous sign-in number and the last continuous sign-in number.

12. A server, characterized in that: The server comprises: A processor and a memory, wherein at least one instruction is stored in the memory, and the at least one instruction is loaded and executed by the processor to implement the operation performed by the method for updating the sign-in information according to any one of claims 1 to 11.

13. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores at least one instruction, and the at least one instruction is loaded and executed by the processor to implement the operation performed by the method for updating the check-in information according to any one of claims 1 to 11.

Images