Time calibration method and system applied to client, storage medium and equipment

Abstract

The invention provides a time calibration method and system applied to a client, a storage medium and equipment, and relates to the technical field of computers, and the method comprises the following steps: sending a time calibration request containing a sending timestamp to a back-end server; receiving a time calibration result returned by the back-end server; the back-end server is used for generating the time calibration result according to the sending timestamp; and performing time calibration on local time according to the time calibration result. According to the invention, the back-end server carries out the time calibration according to the sending timestamps uploaded by the clients, thereby avoiding the local time difference of different clients, and avoiding the time difference of different clients caused by network jitter and the like from affecting the network service.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a time calibration method, system, storage medium and device applied to a client. Background Art

[0002] Currently, electronic device applications directly request the countdown time from the backend, and the backend calculates the remaining seconds of the countdown, which is then fed back to the front-end electronic device application. However, in this process, if there is network jitter between the front-end and the back-end, it will directly affect the countdown error of the front-end. Therefore, how to ensure that the time of each front-end does not have a time difference is a technical problem that technicians in this field need to solve urgently. Summary of the invention

[0003] The purpose of this application is to provide a time calibration method applied to a client, a time calibration method applied to a backend server, a time calibration system applied to a client, a computer-readable storage medium and an electronic device, which can solve the time differences between different terminals.

[0004] In order to solve the above technical problems, the present application provides a time calibration method applied to a client, and the specific technical solution is as follows:

[0005] Send a time calibration request including a sending timestamp to the backend server;

[0006] Receiving the time calibration result returned by the back-end server; the back-end server is used to generate the time calibration result according to the sending timestamp;

[0007] The local time is time-calibrated according to the time calibration result.

[0008] Optionally, if the time calibration request is a countdown calibration request and is the first countdown calibration request, the time calibration result includes a countdown deadline timestamp, and accordingly, time calibration of the local time according to the time calibration result includes:

[0009] The countdown time corresponding to the countdown calibration request is calculated according to the sending timestamp, the countdown deadline timestamp and the local timestamp.

[0010] Optionally, if the time calibration request is a countdown calibration request and is not the first countdown calibration request, the time calibration result includes a remaining timestamp, and accordingly, time calibration of the local time according to the time calibration result includes:

[0011] The countdown time corresponding to the countdown calibration request is calculated according to the sending timestamp, the remaining timestamp and the local timestamp.

[0012] The present application also provides a time calibration method applied to a backend server, comprising:

[0013] Receive a time calibration request uploaded by a client that includes a sending timestamp;

[0014] Generate a time calibration result according to the sending timestamp and the local timestamp of the backend server;

[0015] The time calibration result is sent to the client, so that the client performs time calibration according to the time calibration result.

[0016] Optionally, if the time calibration is a countdown calibration request, generating a time calibration result according to the sending timestamp and the local timestamp of the backend server includes:

[0017] The end timestamp at the end of the countdown is calculated according to the sending timestamp and the local timestamp of the backend server.

[0018] Optionally, after receiving the time calibration request including the sending timestamp uploaded by the client, the following is further included:

[0019] Determining whether the time calibration request is a first calibration request;

[0020] If so, record the backend server timestamp when the time calibration request is received;

[0021] If not, the step of calculating the end timestamp at the end of the countdown according to the sending timestamp and the local timestamp of the backend server is executed.

[0022] Optionally, calculating the end timestamp at the end of the countdown according to the sending timestamp and the local timestamp of the backend server includes:

[0023] Obtaining a backend server timestamp when the time calibration request is first received;

[0024] Get the countdown time from the cache queue;

[0025] The backend server timestamp is superimposed with the countdown time as the end timestamp.

[0026] The present application also provides a time calibration system applied to a client, comprising:

[0027] A request sending module, used for sending a time calibration request including a sending timestamp to a backend server;

[0028] A result receiving module, configured to receive the time calibration result returned by the back-end server; the back-end server is configured to generate the time calibration result according to the sending timestamp;

[0029] The time calibration module is used to calibrate the local time according to the time calibration result.

[0030] The present application also provides a computer-readable storage medium having a computer program stored thereon, and the computer program implements the steps of the above-mentioned method when executed by a processor.

[0031] The present application also provides an electronic device, including a memory and a processor, wherein a computer program is stored in the memory, and the processor implements the steps of the above-mentioned method when calling the computer program in the memory.

[0032] The present application provides a time calibration method applied to a client, comprising: sending a time calibration request including a sending timestamp to a backend server; receiving a time calibration result returned by the backend server; the backend server is used to generate the time calibration result according to the sending timestamp; and calibrating the local time according to the time calibration result.

[0033] When executing time calibration, the present application sends a calibration request to the back-end server. After the back-end server generates a time calibration result based on the timestamp included in the time calibration request, the client can perform local time calibration based on the time calibration result fed back by the back-end server. The back-end server performs time calibration based on the sending timestamp uploaded by each client, thereby avoiding local time differences between different clients and preventing time differences between different clients caused by network jitter and other reasons from affecting network services. It can ensure the synchronous triggering of various activities on the client, realize accurate time coordination and unified scheduling execution of client applications, and ensure cross-platform time consistency of client applications.

[0034] The present application also provides a time calibration method applied to a backend server, a time calibration system applied to a client, a computer-readable storage medium and an electronic device, which have the above-mentioned beneficial effects and are not described in detail here. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0036] Figure 1 A flowchart of a time calibration method applied to a client provided in an embodiment of the present application;

[0037] Figure 2A flowchart of a time calibration method applied to a backend server provided in an embodiment of the present application;

[0038] Figure 3 A flowchart of the countdown calibration process provided in an embodiment of the present application;

[0039] Figure 4 A schematic diagram of the structure of a time calibration system applied to a client provided in an embodiment of the present application;

[0040] Figure 5 A schematic diagram of the structure of a time calibration system applied to a backend server provided in an embodiment of the present application;

[0041] Figure 6 A structural diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0042] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0043] The object information involved in this application, including but not limited to the object device information, object personal information, etc., and data, including but not limited to data used for analysis, stored data, displayed data, etc., are all information and data authorized by the object or fully authorized by all parties, and the collection, use and processing of relevant data must comply with the laws, regulations and standards of relevant countries and regions.

[0044] See also Figure 1 , Figure 1 A flowchart of a time calibration method applied to a client provided in an embodiment of the present application, the method comprising:

[0045] S101: Sending a time calibration request including a sending timestamp to a backend server;

[0046] S102: receiving the time calibration result returned by the backend server;

[0047] S103: Perform time calibration on the local time according to the time calibration result.

[0048] The time calibration method applied to the client provided in the embodiment of the present application can be directly applied to the client, and can also be applied to the application software on the client. First, it is necessary to send a time calibration request including a sending timestamp to the back-end server, and the sending timestamp refers to the timestamp when the client or the application software on the client sends the time calibration request to the back-end server. The client described in this embodiment is not limited to devices, but can include ios, android, web, h5, mini-programs and other terminals. Taking a shopping platform as an example, it may be accessed through application software, web browsers and mini-programs. At this time, if the application software, web browser and mini-program on the same mobile phone have different time acquisition methods, they can be regarded as different clients.

[0049] This embodiment does not limit the specific type of the time calibration request, and the time calibration request may be a countdown calibration request or a time synchronization request, etc. Taking the countdown calibration request as an example, since the local time of different clients may be different, or the countdown duration of different clients may be different due to network jitter, in order to solve this problem, the client may send a countdown calibration request to the backend server.

[0050] The backend server generates a time calibration result according to the sent timestamp, and returns it to the client as a response to the time calibration request, so that the client can calibrate the local time according to the time calibration result.

[0051] Following the above example, if the time calibration request is a countdown calibration request, after receiving the time calibration result, the client can calibrate the local countdown according to the time calibration result.

[0052] In a feasible implementation, the backend server may use different calculation methods to generate the time calibration result according to the number of time calibration request requests, and the corresponding client may use different time calibration calculation methods.

[0053] If the countdown calibration request is the first countdown calibration request, the client's countdown is usually not over at this time, then the backend server can calculate the countdown deadline timestamp based on the sending timestamp, that is, the time calibration result includes the countdown deadline timestamp, then the client can calculate the countdown time based on the sending timestamp, countdown timestamp and local timestamp.

[0054] If the countdown calibration request is not the first countdown calibration request, the client has sent a time calibration request to the back-end server at least once. After the back-end server receives the countdown calibration request, the countdown may have actually expired due to network jitter and other reasons. Therefore, the time calibration result generated by the back-end server during time calibration includes the remaining timestamp. After the corresponding client receives the time calibration result, it can calculate the countdown time based on the sending timestamp, the remaining timestamp and the local timestamp. At this time, the countdown time may be 0, indicating that the countdown has expired or ended.

[0055] When executing time calibration, the embodiment of the present application sends a calibration request to the back-end server. After the back-end server generates a time calibration result based on the timestamp included in the time calibration request, the client can perform local time calibration based on the time calibration result fed back by the back-end server. The back-end server performs time calibration based on the sending timestamp uploaded by each client, thereby avoiding local time differences between different clients and preventing time differences between different clients caused by network jitter and other reasons from affecting network services.

[0056] See also Figure 2 , Figure 2 A flowchart of a time calibration method applied to a backend server provided in an embodiment of the present application, the method comprising:

[0057] S201: receiving a time calibration request including a sending timestamp uploaded by a client;

[0058] S202: Generate a time calibration result according to the sending timestamp and the local timestamp of the backend server;

[0059] S203: Send the time calibration result to the client, so that the client performs time calibration according to the time calibration result.

[0060] Compared with the previous embodiment, this embodiment uses the backend server as the implementation subject. In the actual application of this embodiment, communication connections can be established with multiple clients at the same time, and multiple clients or application software running on the clients can be served at the same time. In particular, the same time calibration request of the same application software can be satisfied, such as the time calibration request generated by the countdown activity of the application software.

[0061] In step S202, a time calibration result needs to be generated based on the sending timestamp contained in the time calibration request and the local timestamp of the backend server. Still taking the countdown calibration request as an example, the end timestamp at the end of the countdown can be calculated based on the sending timestamp and the local timestamp of the backend server.

[0062] Specifically, the backend server first obtains the current timestamp. In most programming languages, this can be achieved by calling the corresponding library function, for example, time.time() can be used in Python. Then the sending timestamp is parsed. The sending timestamp is set in the time calibration request uploaded by the client to the backend server, and can usually be a number representing the time. As for the sending timestamp, the backend server can first verify the sending timestamp to ensure that the sending timestamp is accurate. For example, the backend server can verify the client fingerprint information contained in the time calibration request. After the client fingerprint information is verified, the sending timestamp can be trusted. After that, the format of the sending timestamp needs to be parsed, for example, whether it is a UNIX timestamp, that is, the number of seconds starting from UTC (Coordinated Universal Time) on January 1, 1970. It is easy to understand that in order to facilitate the calculation of the end timestamp, the sending timestamp and the local timestamp of the backend server should use the same timestamp format.

[0063] When calculating the end timestamp at the end of the countdown, if the time calibration request is a countdown calibration request, the total duration of the countdown (for example, in seconds) is usually known at this time, and the duration can be added to the sending timestamp to calculate the countdown end timestamp.

[0064] It is also important to note that since the backend server and the client may be in different time zones and may be affected by daylight saving time, time zones and daylight saving time can be further considered to avoid time calculation errors.

[0065] When calculating the end timestamp, add the known countdown duration to the sending timestamp to get the countdown end timestamp.

[0066] As for the backend server, it needs to connect to several clients, so it can determine whether it is the first request for each client. It is easy to understand that the time calibration request initiated by the client should at least contain unique identification characters or feature information (such as client fingerprint), so that the backend server can distinguish the client or application software on the client corresponding to the time calibration request.

[0067] In a feasible implementation manner, after receiving the time calibration request including the sending timestamp uploaded by the client, the backend server may determine whether the time calibration request is the first calibration request;

[0068] If so, record the backend server timestamp when the time calibration request is received;

[0069] If not, the step of calculating the end timestamp at the end of the countdown according to the sending timestamp and the local timestamp of the backend server is executed.

[0070] It should be noted that, as to whether it is the first calibration request, it can be determined first whether it is the same request initiator, and the reference source of the sending timestamp of each initiator can be determined. For example, for time calibration requests initiated by different application software on the same client, since the request initiators of the two requests belong to two different application software, and each uses its own timestamp for software application timing, although they originate from the same client, they can be regarded as the first calibration request. If different application software directly reads the client's own time as the application time, at this time, although the two time calibration requests originate from different clients, they both originate from the client's own sending timestamp, so they can be regarded as the first time calibration request and the second time calibration request initiated by the client successively.

[0071] It should be emphasized that the backend server timestamp when receiving the time calibration request and the local timestamp of the backend server are not the same concept. The former is the local time of the backend server at the moment when the backend server receives the time calibration request uploaded by the client, and the latter is the local time of the backend server when the backend server calculates the end timestamp at the end of the countdown.

[0072] When the time calibration request is a countdown request, it should at least include the countdown duration, such as a countdown of 60 seconds. When the time calibration request is the first calibration request, the backend server records the backend server timestamp when the time calibration request is received. When the time calibration request is a countdown request, it indicates that the countdown has started. When a time calibration request is received from the same initiator subsequently, a different time calibration result generation method will be used.

[0073] After receiving the time calibration request, the backend server may perform the following steps in a feasible implementation:

[0074] The first step is to obtain the backend server timestamp when the time calibration request is received for the first time;

[0075] Step 2: Get the countdown time from the cache queue;

[0076] Step 3: Add the countdown time to the backend server timestamp as the end timestamp.

[0077] The cache queue is used to cache the countdown time calculated when the time calibration request is received for the first time. In addition, the cache queue can also be used to cache the countdown time calculated each time a time calibration request is received subsequently, so that the countdown time calculated last time is obtained from the cache queue when the time calibration request is received next time, and is superimposed with the local timestamp of the backend server to obtain the end timestamp.

[0078] For example, when a time calibration request is received from a client for the first time, its initiation timestamp is t1 and the countdown duration is S seconds;

[0079] At this time, the backend server detects that it is the first calibration request and records the backend server timestamp as T2. At the same time, the calculated deadline timestamp is T2+S, and the deadline timestamp is returned to the client. Thereafter, the client can calculate the countdown based on the initiation timestamp and the deadline timestamp, that is, T2+S- t1 to determine the countdown.

[0080] If a second calibration request is detected, and its initiation timestamp is t2, the timestamp of the backend server when receiving the calibration request is T3, and the last calculated deadline timestamp obtained from the cache queue is T3-t2+T2+S. The remaining time can be determined based on T2+S-T3, and the remaining countdown time is returned to the client. Of course, the backend server can also return other information, such as sending the timestamp as the comparison time of the remaining countdown time and returning it to the client.

[0081] See also Figure 3 , Figure 3 The flowchart of the countdown calibration process provided in the embodiment of the present application takes the client initiating the countdown calibration request as a specific type of time calibration request, which includes the client and the countdown calibration method implemented by the backend server, i.e., the server. The specific process is as follows:

[0082] The client first initiates a request with a sending timestamp to the backend service, and obtains the countdown configuration of the server at the same time. The countdown configuration obtained here refers to the server timestamp of the first request recorded, and the countdown duration obtained from the cache, and the server timestamp of the first request plus the countdown duration is used as the end timestamp.

[0083] The server determines whether the client has entered the countdown.

[0084] If it is not the first calibration request, the countdown is confirmed, the remaining countdown seconds are calculated, added to the timestamp provided by the client, and then returned to the client.

[0085] If it is the first calibration request, that is, it is confirmed that the countdown has not begun, the timestamp calculated by the server is first recorded, and then the client request timestamp plus the countdown seconds are returned to the client.

[0086] The client calculates the remaining seconds of the countdown based on the timestamp returned by the backend minus the local timestamp. If it is less than or equal to 0, the countdown has ended. If it is greater than 0, the countdown can be displayed.

[0087] Depend on Figure 3It can be seen that this embodiment can return the countdown time or the remaining seconds of the countdown through calculation on the server side. Even if there are differences in the local timestamps of each client, the unified calibration of the server side can ensure that the countdown of each client ends at the same time, avoiding differences in the countdown end time of different clients due to differences in local timestamps. This can ensure the synchronous triggering of various activities on the client, realize accurate time coordination and unified scheduling execution of client applications, and ensure cross-platform time consistency of client applications.

[0088] See also Figure 4 , Figure 4 This is a schematic diagram of the structure of a time calibration system applied to a client provided in an embodiment of the present application. The present application also provides a time calibration system applied to a client, including:

[0089] A request sending module, used for sending a time calibration request including a sending timestamp to a backend server;

[0090] A result receiving module, configured to receive the time calibration result returned by the back-end server; the back-end server is configured to generate the time calibration result according to the sending timestamp;

[0091] The time calibration module is used to calibrate the local time according to the time calibration result.

[0092] Based on the above embodiments, as a preferred embodiment, if the time calibration request is a countdown calibration request and it is the first countdown calibration request, the time calibration result includes a countdown deadline timestamp, and accordingly, the time calibration module is a module for calculating the countdown time based on the sending timestamp, the countdown deadline timestamp and the local timestamp.

[0093] Based on the above embodiments, as a preferred embodiment, if the time calibration request is a countdown calibration request and is not the first countdown calibration request, the time calibration result includes a remaining timestamp, and accordingly, the time calibration module is a module for calculating the countdown time corresponding to the countdown calibration request based on the sending timestamp, the remaining timestamp and the local timestamp.

[0094] See also Figure 5 , Figure 5 This is a schematic diagram of the structure of a time calibration system applied to a backend server provided in an embodiment of the present application. The present application also provides a time calibration system applied to a backend server, including:

[0095] A client request receiving module, used for receiving a time calibration request including a sending timestamp uploaded by a client;

[0096] A time calibration calculation module, used to generate a time calibration result according to the sending timestamp and the local timestamp of the back-end server;

[0097] The result sending module is used to send the time calibration result to the client so that the client can perform time calibration according to the time calibration result.

[0098] Based on the above embodiment, as a preferred embodiment, if the time calibration is a countdown calibration request, the time calibration calculation module is a module for calculating the end timestamp when the countdown ends according to the sending timestamp and the local timestamp of the backend server.

[0099] Based on the above embodiments, as a preferred embodiment, it also includes:

[0100] A judgment module is used to judge whether the time calibration request is the first calibration request; and when the judgment result of the judgment module is yes, record the back-end server timestamp when the time calibration request is received; when the judgment result of the judgment module is no, enter the time calibration calculation module.

[0101] Based on the above embodiments, as a preferred embodiment, the time calibration calculation module is a module for performing the following steps:

[0102] Obtaining a backend server timestamp when the time calibration request is received for the first time; obtaining a countdown time from a cache queue; and adding the countdown time to the backend server timestamp as an end timestamp.

[0103] The present application also provides a computer-readable storage medium on which a computer program is stored, and when the computer program is executed, the steps provided in the above embodiment can be implemented. The storage medium may include: a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and other media that can store program codes.

[0104] The present application also provides an electronic device, see Figure 6 , a structural diagram of an electronic device provided in an embodiment of the present application, such as Figure 6 As shown, a processor 1410 and a memory 1420 may be included.

[0105] Among them, the processor 1410 may include one or more processing cores, such as a 4-core processor, an 8-core processor, etc. The processor 1410 may be implemented in at least one hardware form of DSP (Digital Signal Processing), FPGA (Field-Programmable Gate Array), and PLA (Programmable Logic Array). The processor 1410 may also include a main processor and a coprocessor. The main processor is a processor for processing data in the awake state, also known as a CPU (Central Processing Unit); the coprocessor is a low-power processor for processing data in the standby state. In some embodiments, the processor 1410 may be integrated with a GPU (Graphics Processing Unit), which is responsible for rendering and drawing the content to be displayed on the display screen. In some embodiments, the processor 1410 may also include an AI (Artificial Intelligence) processor, which is used to process computing operations related to machine learning.

[0106] The memory 1420 may include one or more computer-readable storage media, which may be non-transitory. The memory 1420 may also include a high-speed random access memory, and a non-volatile memory, such as one or more disk storage devices, flash memory storage devices. In this embodiment, the memory 1420 is at least used to store the following computer program 1421, wherein, after the computer program is loaded and executed by the processor 1410, it can implement the relevant steps in the method performed by the electronic device side disclosed in any of the aforementioned embodiments. In addition, the resources stored in the memory 1420 may also include an operating system 1422 and data 1423, etc., and the storage method may be temporary storage or permanent storage. Among them, the operating system 1422 may include Windows, Linux, Android, etc.

[0107] In some embodiments, the electronic device may further include a display screen 1430 , an input / output interface 1440 , a communication interface 1450 , a sensor 1460 , a power source 1470 , and a communication bus 1480 .

[0108] certainly, Figure 6 The structure of the electronic device shown does not constitute a limitation on the electronic device in the embodiments of the present application. In actual applications, the electronic device may include Figure 6 More or fewer components than shown, or combinations of certain components.

[0109] The various embodiments in the specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the various embodiments can be referred to each other. For the system provided in the embodiment, since it corresponds to the method provided in the embodiment, the description is relatively simple, and the relevant parts can be referred to the method part description.

[0110] Specific examples are used herein to illustrate the principles and implementation methods of the present application, and the description of the above embodiments is only used to help understand the method and core ideas of the present application. It should be pointed out that for ordinary technicians in this technical field, without departing from the principles of the present application, several improvements and modifications can be made to the present application, and these improvements and modifications also fall within the scope of protection of the present application.

[0111] It should also be noted that, in this specification, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the statement "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device including the element.

Claims

1. A time calibration method applied to a client, characterized in that: include: Send a time calibration request including a sending timestamp to the backend server; Receiving the time calibration result returned by the back-end server; The backend server is used to generate the time calibration result according to the sending timestamp; The local time is time-calibrated according to the time calibration result.

2. The time calibration method according to claim 1, characterized in that: If the time calibration request is a countdown calibration request and is the first countdown calibration request, the time calibration result includes a countdown deadline timestamp, and accordingly, time calibration of the local time according to the time calibration result includes: The countdown time corresponding to the countdown calibration request is calculated according to the sending timestamp, the countdown deadline timestamp and the local timestamp.

3. The time calibration method according to claim 1, characterized in that: If the time calibration request is a countdown calibration request and is not the first countdown calibration request, the time calibration result includes a remaining timestamp, and accordingly, time calibration of the local time according to the time calibration result includes: The countdown time corresponding to the countdown calibration request is calculated according to the sending timestamp, the remaining timestamp and the local timestamp.

4. A time calibration method applied to a backend server, characterized in that: include: Receive a time calibration request uploaded by a client that includes a sending timestamp; Generate a time calibration result according to the sending timestamp and the local timestamp of the backend server; The time calibration result is sent to the client, so that the client performs time calibration according to the time calibration result.

5. The time calibration method according to claim 4, characterized in that: If the time calibration is a countdown calibration request, generating a time calibration result according to the sending timestamp and the local timestamp of the backend server includes: The end timestamp at the end of the countdown is calculated according to the sending timestamp and the local timestamp of the backend server.

6. The time calibration method according to claim 5, characterized in that: After receiving the time calibration request uploaded by the client containing the sending timestamp, it also includes: Determining whether the time calibration request is a first calibration request; If so, record the backend server timestamp when the time calibration request is received; If not, the step of calculating the end timestamp at the end of the countdown according to the sending timestamp and the local timestamp of the backend server is executed.

7. The time calibration method according to claim 5, characterized in that: Calculating the end timestamp at the end of the countdown according to the sending timestamp and the local timestamp of the backend server includes: Obtaining a backend server timestamp when the time calibration request is first received; Get the countdown time from the cache queue; The backend server timestamp is superimposed with the countdown time as the end timestamp.

8. A time calibration system applied to a client, characterized in that: include: A request sending module, used for sending a time calibration request including a sending timestamp to a backend server; A result receiving module, configured to receive the time calibration result returned by the back-end server; the back-end server is configured to generate the time calibration result according to the sending timestamp; The time calibration module is used to calibrate the local time according to the time calibration result.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the time calibration method applied to a client as described in claims 1-3, or the time calibration method applied to a backend server as described in any one of claims 4-7 are implemented.

10. An electronic device, characterized in that: It includes a memory and a processor, wherein a computer program is stored in the memory, and when the processor calls the computer program in the memory, it implements the steps of the time calibration method applied to the client as described in claims 1-3, or the time calibration method applied to the back-end server as described in any one of claims 4-7.

Images