Call link generation method, device, electronic device and computer readable medium
By sending server timestamps to the client and correcting client timestamps, generating a call link starting from the client, the problem of calling links being limited to the server in the existing technology is solved, and the efficiency of client problem positioning is improved and the scope of application of the call link.
Patent Information
- Application Number
- CN202110944101.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2021-08-17
- Publication Date
- 2024-11-15
- Estimated Expiration
- 2041-08-17
AI Technical Summary
Due to the inconsistent time systems of the client and server side, the use scenarios of the calling link are limited to the server side, and the client problems cannot be effectively located, which reduces the problem tracking and positioning efficiency when service calls are errored.
By sending the server's current timestamp notification information to the client, correcting the client's timestamp, and generating the request network delay time, creating a call link starting from the client's basic work unit, expanding the scope of application of the call link.
It realizes that the client problem can be fully positioned when a service call error occurs, and improves the efficiency of problem tracking and positioning and the scope of application of the call link.
Smart Images

Figure CN115914396B_ABST
Abstract
Description
Technical Field
[0001] Embodiments of the present disclosure relate to the field of computer technology, and in particular to a call link generation method, device, electronic device, and computer-readable medium. Background Art
[0002] The call chain can record the relevant data of the entire request chain in order from the client initiating the service request to the end of the service request, so as to facilitate subsequent query analysis, locate system problems or use it for performance optimization. At present, when generating a call chain, the usual method is to uniquely label the current chain at the starting point of the call chain and record the start and end timestamps of each call. When displaying, all calls are associated with unique labels, and the calls are drawn into a call chain.
[0003] However, when the above method is used to generate a call link, the following technical problems often occur:
[0004] First, the key to drawing a call chain is that all systems in the entire chain must use the same time system. Due to the inconsistency of the time systems of the client and the server, the use scenario of the call chain is limited to the server, which makes the application scope of the call chain small. When a service call fails, it is impossible to determine whether there is a problem on the client, which leads to incomplete problem tracking and positioning when a service call fails.
[0005] Second, the usage scenarios of the call link are limited to the server side. When a service call fails, it is impossible to determine whether there is a problem with the client based on the call link. Other complex methods are needed to determine whether there is a problem with the client, which increases the workload of tracking and locating client problems and reduces the efficiency of problem tracking and locating when a service call fails. Summary of the invention
[0006] The content of this disclosure is used to introduce concepts in a brief form, which will be described in detail in the detailed implementation section below. The content of this disclosure is not intended to identify the key features or essential features of the technical solution claimed for protection, nor is it intended to limit the scope of the technical solution claimed for protection.
[0007] Some embodiments of the present disclosure propose a call link generation method, apparatus, electronic device, and computer-readable medium to solve one or more of the technical problems mentioned in the above background technology section.
[0008] In a first aspect, some embodiments of the present disclosure provide a call link generation method, the method comprising: sending a timestamp notification information to a client, wherein the timestamp notification information includes a first current timestamp of a server, and the first current timestamp of a server is a timestamp under a server time base; in response to receiving a data request information sent by the client, generating a request network delay time according to a corrected client timestamp included in the data request information, wherein the corrected client timestamp is a timestamp under a server time base; generating client call information according to the request network delay time; and sending the client call information to a call chain system to create a call chain with a client basic working unit as a starting point of the call chain.
[0009] In a second aspect, some embodiments of the present disclosure provide a call link generating device, the device comprising: a notification unit, configured to send a timestamp notification information to a client, wherein the timestamp notification information comprises a first current timestamp of a server, and the first current timestamp of a server is a timestamp under a server time base; a receiving unit, configured to generate a request network delay time in response to receiving data request information sent by the client, according to a corrected client timestamp included in the data request information, wherein the corrected client timestamp is a timestamp under a server time base; a generating unit, configured to generate client call information according to the request network delay time; and a sending unit, configured to send the client call information to a call chain system to create a call link with a client basic working unit as a starting point of the call chain.
[0010] In a third aspect, some embodiments of the present disclosure provide an electronic device comprising: one or more processors; a storage device on which one or more programs are stored, and when the one or more programs are executed by the one or more processors, the one or more processors implement the method described in any implementation manner of the above-mentioned first aspect.
[0011] In a fourth aspect, some embodiments of the present disclosure provide a computer-readable medium having a computer program stored thereon, wherein when the program is executed by a processor, the method described in any implementation manner of the above-mentioned first aspect is implemented.
[0012] The above-mentioned embodiments of the present disclosure have the following beneficial effects: through the call link generation method of some embodiments of the present disclosure, the application scope of the call link can be expanded to the client, the call link is improved, and it is convenient to track and locate the node where the problem occurs when the service call fails. Specifically, the reason why the use scenario of the call link is limited to the backend system is that the key to the call link being able to be drawn is that all systems on the entire link must use the same time system. Due to the inconsistency of the time systems of the client and the server, the use scenario of the call link is limited to the server, which makes the application scope of the call chain small. When the service call fails, it is impossible to determine whether there is a problem with the client, which leads to incomplete problem tracking and positioning when the service call fails. Based on this, the call link generation method of some embodiments of the present disclosure first sends timestamp notification information to the client. Among them, the timestamp notification information includes the first current timestamp of the server, and the first current timestamp of the server is the timestamp under the server time base. Thus, the first current timestamp of the server can provide data support for generating the corrected client timestamp. Then, in response to receiving the data request information sent by the client, the request network delay time is generated according to the corrected client timestamp included in the data request information. Among them, the above-mentioned corrected client timestamp is a timestamp under the above-mentioned server time reference. Therefore, the server can determine the request network delay time from the client to the server by receiving the corrected client timestamp. Then, according to the above-mentioned request network delay time, the client call information is generated. Therefore, the start timestamp of the client call can be generated according to the request network delay time and added to the client call information. Finally, the above-mentioned client call information is sent to the call chain system to create a call link with the client basic work unit as the starting point of the call chain. Therefore, the call chain system can generate the client basic work unit according to the client call information provided by the server, and use the client basic work unit as the starting point of the call link to create a call link. Also, because the client is added to the call link, the call starting point is moved forward, which makes the application scope of the call link larger, and it can determine whether there is a problem with the client when the service call fails, thereby making the problem tracking and positioning more comprehensive when the service call fails. BRIEF DESCRIPTION OF THE DRAWINGS
[0013] The above and other features, advantages and aspects of the embodiments of the present disclosure will become more apparent with reference to the following detailed description in conjunction with the accompanying drawings. Throughout the accompanying drawings, the same or similar reference numerals represent the same or similar elements. It should be understood that the drawings are schematic and that components and elements are not necessarily drawn to scale.
[0014] Figure 1 is a schematic diagram of an application scenario of the call link generation method of some embodiments of the present disclosure;
[0015] Figure 2 is a flowchart of some embodiments of the call link generation method according to the present disclosure;
[0016] Figure 3 It is a structural schematic diagram of some embodiments of the call link generation device according to the present disclosure;
[0017] Figure 4 It is a schematic diagram of the structure of an electronic device suitable for implementing some embodiments of the present disclosure. DETAILED DESCRIPTION
[0018] Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although certain embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as being limited to the embodiments set forth herein. On the contrary, these embodiments are provided to provide a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are only for exemplary purposes and are not intended to limit the scope of protection of the present disclosure.
[0019] It should also be noted that, for ease of description, only the parts related to the invention are shown in the drawings. In the absence of conflict, the embodiments and features in the embodiments of the present disclosure can be combined with each other.
[0020] It should be noted that the concepts such as "first" and "second" mentioned in the present disclosure are only used to distinguish different devices, modules or units, and are not used to limit the order or interdependence of the functions performed by these devices, modules or units.
[0021] It should be noted that the modifications of "one" and "plurality" mentioned in the present disclosure are illustrative rather than restrictive, and those skilled in the art should understand that unless otherwise clearly indicated in the context, it should be understood as "one or more".
[0022] The names of the messages or information exchanged between multiple devices in the embodiments of the present disclosure are only used for illustrative purposes and are not used to limit the scope of these messages or information.
[0023] The present disclosure will be described in detail below with reference to the accompanying drawings and in conjunction with embodiments.
[0024] Figure 1 It is a schematic diagram of an application scenario of the call link generation method of some embodiments of the present disclosure.
[0025] exist Figure 1In the application scenario, first, the computing device 101 can send a timestamp notification information 103 to the client 102. The timestamp notification information 103 includes the first current timestamp of the server, and the first current timestamp of the server is a timestamp under the server time base. Then, the computing device 101 can generate a request network delay time 105 according to the corrected client timestamp included in the data request information 104 in response to receiving the data request information 104 sent by the client 102. The corrected client timestamp is a timestamp under the server time base. Then, according to the request network delay time 105, generate client call information 106. Finally, send the client call information 106 to the call chain system 107 to create a call link with the client basic working unit as the starting point of the call chain.
[0026] It should be noted that the computing device 101 can be hardware or software. When the computing device is hardware, it can be implemented as a distributed cluster consisting of multiple servers or terminal devices, or as a single server or a single terminal device. When the computing device is embodied as software, it can be installed in the hardware devices listed above. It can be implemented as multiple software or software modules for providing distributed services, or as a single software or software module. No specific limitation is made here.
[0027] It should be understood that Figure 1 The number of computing devices in the embodiment is only illustrative. Any number of computing devices may be provided according to implementation requirements.
[0028] Continue to refer Figure 2 , shows a process 200 of some embodiments of the call link generation method according to the present disclosure. The call link generation method includes the following steps:
[0029] Step 201: Send timestamp notification information to the client.
[0030] In some embodiments, the execution subject (such as Figure 1 The computing device 101 shown in the figure can send timestamp notification information to the client. The timestamp notification information includes the first current timestamp of the server, and the first current timestamp of the server is a timestamp under the server time reference. In practice, the execution subject can send timestamp notification information to the client through service registration and discovery. Therefore, the first current timestamp of the server can provide data support for generating the corrected client timestamp.
[0031] In an optional manner of some embodiments, the execution subject may send the timestamp notification information to the client at a preset time interval. The preset time interval is a pre-set time interval, and the setting of the preset time interval is not limited here.
[0032] Step 202: In response to receiving data request information sent by the client, generate a requested network delay time according to the corrected client timestamp included in the data request information.
[0033] In some embodiments, the above-mentioned execution entity can receive data request information sent by the client, and generate a requested network delay time based on the corrected client timestamp included in the data request information, wherein the above-mentioned corrected client timestamp is a timestamp based on the above-mentioned server time base.
[0034] In an optional manner of some embodiments, the corrected client timestamp is generated by the following steps:
[0035] The first step is to determine a first current timestamp of the client in response to receiving the timestamp notification information.
[0036] The client first current timestamp is a timestamp based on the client time reference. In practice, the following client first current timestamp equation can be generated based on the client first current timestamp, the client initial timestamp and the notification network delay time:
[0037] TC2=TC1+x.
[0038] Wherein, TC2 represents the first current timestamp of the client, TC1 represents the initial timestamp of the client, and x represents the notification network delay time. The initial timestamp of the client is the timestamp under the client time reference corresponding to the first current timestamp of the server. The notification network delay time is the time taken from the server sending the notification information to the client receiving the notification information. The timestamp under the client time reference corresponding to the first current timestamp of the server may be the timestamp obtained after converting the first current timestamp of the server to the client time reference.
[0039] As an example, for ease of understanding, the time format of hours, minutes, and seconds is used instead of the timestamp for illustration. The above TC2 may be 8:00:01. The above client first current timestamp equation: TC2=TC1+x may be expressed as 8:00:01=TC1+x.
[0040] In a second step, the difference between the first current timestamp of the client and the first current timestamp of the server included in the timestamp notification information is determined as a time offset.
[0041] In practice, the following time offset equation can be generated based on the above client first current timestamp equation and the above server first current timestamp equation:
[0042] Offset=TC2-TS1=TC1+x-TS1.
[0043] Among them, Offset represents the above time offset, TC1 represents the above client initial timestamp, TC2 represents the above client first current timestamp, x represents the above notification network delay time, and TS1 represents the above server first current timestamp.
[0044] As an example, for ease of understanding, the time format of hours, minutes and seconds is used instead of the timestamp for illustration. The above TC2 may be 08:00:01, the above TS1 may be 07:59:00, and the above Offset=TC2-TS1=TC1+x-TS1 may be expressed as Offset=08:00:01-07:59:00=TC1+x-07:59:00.
[0045] The third step is to determine a second current timestamp of the client in response to receiving an instruction to send data request information to the server.
[0046] The second current timestamp of the client is a timestamp based on the time reference of the client. In practice, the following equation for the second current timestamp of the client can be generated based on the second current timestamp of the client, the first current timestamp of the client, the initial timestamp of the client, the notification network delay time and the waiting time:
[0047] TC3=TC2+y=TC1+x+y.
[0048] Wherein, TC3 represents the second current timestamp of the client, TC2 represents the first current timestamp of the client, TC1 represents the initial timestamp of the client, x represents the notification network delay time, and y represents the waiting time. The waiting time is the interval between the second current timestamp of the client and the first current timestamp of the client.
[0049] As an example, for ease of understanding, the time format of hours, minutes, and seconds is used instead of the timestamp for illustration. The above TC3 can be 08:00:10, the above TC2 can be 08:00:01, the above y can be 9 seconds, and y can be expressed as 00:00:09. The above TC3=TC2+y=TC1+x+y can be expressed as 08:00:10=08:00:01+00:00:09=TC1+x+00:00:09.
[0050] In the fourth step, the difference between the second current timestamp of the client and the time offset is determined as the corrected client timestamp.
[0051] In practice, the following corrected client timestamp equation can be generated according to the above time offset equation and the above client second current timestamp equation:
[0052] TC3-Offset=(TC1+x+y)-(TC1+x-TS1)=TS1+y.
[0053] Among them, TC3 represents the second current timestamp of the client, Offset represents the time offset, TC3-Offset represents the corrected client timestamp, TS1 represents the first current timestamp of the server, y represents the waiting time, TC1 represents the initial timestamp of the client, and x represents the notification network delay time.
[0054] As an example, for ease of understanding, the time format of hours, minutes, and seconds is used instead of the timestamp for illustration. The above TC3 can be 08:00:10, the above Offset can be 00:01:01, the above TS1 can be 07:59:00, the above y can be 9 seconds, and y can be expressed as 00:00:09. The above TC3-Offset=(TC1+x+y)-(TC1+x-TS1)=TS1+y can be expressed as 08:00:10-00:01:01=(TC1+x+00:00:09)-(TC1+x-07:59:00)=07:59:00+00:00:09.
[0055] In an optional manner of some embodiments, the execution entity may determine a second current timestamp of the server in response to receiving data request information sent by the client.
[0056] The second current timestamp of the server is a timestamp based on the time reference of the server. In practice, the execution subject can generate the following equation of the second current timestamp of the server according to the second current timestamp of the server, the first current timestamp of the server, the notification network delay time, the waiting time and the request network delay time:
[0057] TS4=TS1+x+y+z.
[0058] Among them, TS4 represents the second current timestamp of the server, TS1 represents the first current timestamp of the server, x represents the notification network delay time, y represents the waiting time, and z represents the request network delay time. The request network delay time is the time taken from the client sending the request to the server receiving the request.
[0059] As an example, for ease of understanding, the time format of hours, minutes, and seconds is used instead of the timestamp for illustration. The above TS4 can be 07:59:11, the above TS1 can be 07:59:00, the above y can be 9 seconds, and y can be expressed as 00:00:09. The above TS4=TS1+x+y+z can be expressed as 07:59:11=07:59:00+x+00:00:09+z.
[0060] In an optional manner of some embodiments, the execution entity may determine the difference between the second current timestamp of the server and the corrected client timestamp as the network delay time, wherein the network delay time includes the notification network delay time and the request network delay time.
[0061] In practice, the execution subject may generate the following network delay time equation based on the server second current timestamp equation and the corrected client timestamp equation:
[0062] TS4-(TS1+y)=(TS1+x+y+z)-(TS1+y)=x+z.
[0063] Among them, TS4 represents the second current timestamp of the above-mentioned server, TS1 represents the first current timestamp of the above-mentioned server, x represents the above-mentioned notification network delay time, y represents the above-mentioned waiting time, z represents the above-mentioned request network delay time, and TS4-(TS1+y) represents the above-mentioned network delay time.
[0064] As an example, for ease of understanding, the time format of hours, minutes and seconds is used instead of the timestamp for illustration. The above TS4 can be 07:59:11, the above TS1 can be 07:59:00, the above y can be 9 seconds, and y can be expressed as 00:00:09. The above TS4-(TS1+y)=(TS1+x+y+z)-(TS1+y)=x+z can be expressed as 07:59:11-(07:59:00+00:00:09)=(07:59:00+x+00:00:09+z)-(07:59:00+00:00:09)=x+z.
[0065] Optionally, the execution entity may determine the value of the requested network delay time based on a preset assumption and the network delay time, wherein the network delay time includes the notified network delay time and the requested network delay time, and the assumption may be that the notified network delay time and the requested network delay time are equal.
[0066] In practice, the execution entity may generate the following request network delay time equation based on the network delay time equation:
[0067] (TS4-(TS1+y)) / 2=(x+z) / 2=(2z) / 2=z.
[0068] Wherein, TS4 represents the second current timestamp of the server, TS1 represents the first current timestamp of the server, x represents the notification network delay time, y represents the waiting time, and z represents the request network delay time. Thus, the value of the request network delay time can be determined by assuming that the notification network delay time is equal to the request network delay time.
[0069] As an example, for ease of understanding, the time format of hours, minutes, and seconds is used instead of the timestamp for illustration. The above TS4 can be 07:59:11, the above TS1 can be 07:59:00, the above y can be 9 seconds, y can be expressed as 00:00:09, and the above (TS4-(TS1+y)) / 2=(x+z) / 2=(2z) / 2=z can be expressed as (07:59:11-(07:59:00+00:00:09)) / 2=(x+z) / 2=(2z) / 2=z.
[0070] Therefore, the server can determine the network delay time of the request from the client to the server by receiving the corrected client timestamp.
[0071] Step 203: Generate client call information according to the above request network delay time.
[0072] In some embodiments, the execution subject may generate the client call information according to the request network delay time. In practice, the execution subject may determine the timestamp when the client sends the service request under the server time reference according to the request network delay time, and add the timestamp as the start time of the client call in the call link to the client call information.
[0073] As an example, for ease of understanding, the time format of hours, minutes and seconds is used instead of the timestamp for illustration. The timestamp of the service request sent by the client when the server receives it can be 07:59:11, and the network delay time of the request can be 1 second, and 1 second can be expressed as 00:00:01. The execution entity can determine that the timestamp when the client sends the service request under the server time base is 07:59:11-00:00:01=07:59:10 based on the network delay time of the request 00:00:01, and add the timestamp 07:59:10 as the start timestamp of the client call in the call link to the client call information.
[0074] Therefore, the start timestamp of the client call can be generated according to the request network delay time and added to the client call information.
[0075] Step 204: Send the above client call information to the call chain system to create a call chain with the client basic work unit as the call chain starting point.
[0076] Among them, the above-mentioned client basic work unit is a basic work unit generated by the above-mentioned call chain system according to the above-mentioned client call information. The above-mentioned basic work unit is a call node in the call link. In some embodiments, the above-mentioned execution subject can send the above-mentioned client call information to the call chain system to create a call link with the client basic work unit as the starting point of the call chain. In practice, the above-mentioned execution subject can send the above-mentioned client call information to the call chain system, and the above-mentioned call chain system can generate a client basic work unit according to the received above-mentioned client call information, and use the above-mentioned client basic work unit as the starting point of the call chain to create a call link according to the forwarding path of the service request. Therefore, when a service call fails, it can be determined whether there is a problem with the client based on the call link, which reduces the workload of separately tracking and locating client problems, thereby improving the efficiency of problem tracking and locating when a service call fails.
[0077] Therefore, the call chain system can generate a client basic work unit according to the client call information provided by the server, and use the client basic work unit as the starting point of the call chain to create a call chain.
[0078] The above-mentioned embodiments of the present disclosure have the following beneficial effects: through the call link generation method of some embodiments of the present disclosure, the application scope of the call link can be expanded to the client, the call link is improved, and it is convenient to track and locate the node where the problem occurs when the service call fails. Specifically, the reason why the use scenario of the call link is limited to the backend system is that the key to the call link being able to be drawn is that all systems on the entire link must use the same time system. Due to the inconsistency of the time systems of the client and the server, the use scenario of the call link is limited to the server, which makes the application scope of the call chain small. When the service call fails, it is impossible to determine whether there is a problem with the client, which leads to incomplete problem tracking and positioning when the service call fails. Based on this, the call link generation method of some embodiments of the present disclosure first sends timestamp notification information to the client. Among them, the timestamp notification information includes the first current timestamp of the server, and the first current timestamp of the server is the timestamp under the server time base. Thus, the first current timestamp of the server can provide data support for generating the corrected client timestamp. Then, in response to receiving the data request information sent by the client, the request network delay time is generated according to the corrected client timestamp included in the data request information. Among them, the above-mentioned corrected client timestamp is a timestamp under the above-mentioned server time reference. Therefore, the server can determine the request network delay time from the client to the server by receiving the corrected client timestamp. Then, according to the above-mentioned request network delay time, the client call information is generated. Therefore, the start timestamp of the client call can be generated according to the request network delay time and added to the client call information. Finally, the above-mentioned client call information is sent to the call chain system to create a call link with the client basic work unit as the starting point of the call chain. Therefore, the call chain system can generate the client basic work unit according to the client call information provided by the server, and use the client basic work unit as the starting point of the call link to create a call link. Also, because the client is added to the call link, the call starting point is moved forward, which makes the application scope of the call link larger, and it can determine whether there is a problem with the client when the service call fails, thereby making the problem tracking and positioning more comprehensive when the service call fails.
[0079] Further references Figure 3 As an implementation of the methods shown in the above figures, the present disclosure provides some embodiments of a call link generation device, and these device embodiments are similar to Figure 2 Corresponding to the method embodiments shown, the device can be specifically applied to various electronic devices.
[0080] like Figure 3As shown, the call link generation device 300 of some embodiments includes: a notification unit 301, a receiving unit 302, a generating unit 303 and a sending unit 304. The notification unit 301 is configured to send a timestamp notification information to the client, wherein the timestamp notification information includes a first current timestamp of the server, and the first current timestamp of the server is a timestamp under the server time base; the receiving unit 302 is configured to generate a request network delay time according to the corrected client timestamp included in the data request information in response to receiving the data request information sent by the client, wherein the corrected client timestamp is a timestamp under the server time base; the generating unit 303 is configured to generate client call information according to the request network delay time; and the sending unit 304 is configured to send the client call information to the call chain system to create a call chain with the client basic working unit as the starting point of the call chain.
[0081] It is understood that the units described in the device 300 are similar to those described in the reference Figure 2 Therefore, the operations, features and beneficial effects described above for the method are also applicable to the device 300 and the units contained therein, and will not be described in detail here.
[0082] Reference below Figure 4 , which shows an electronic device (such as Figure 1 A schematic diagram of the structure of the computing device 101)400 is shown. Figure 4 The electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present disclosure.
[0083] like Figure 4 As shown, the electronic device 400 may include a processing device (e.g., a central processing unit, a graphics processing unit, etc.) 401, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 402 or a program loaded from a storage device 408 into a random access memory (RAM) 403. In the RAM 403, various programs and data required for the operation of the electronic device 400 are also stored. The processing device 401, the ROM 402, and the RAM 403 are connected to each other via a bus 404. An input / output (I / O) interface 405 is also connected to the bus 404.
[0084] Typically, the following devices may be connected to the I / O interface 405: an input device 406 including, for example, a touch screen, a touch pad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; an output device 407 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; a storage device 408 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 409. The communication device 409 may allow the electronic device 400 to communicate with other devices wirelessly or by wire to exchange data. Although Figure 4 The electronic device 400 is shown with various devices, but it should be understood that it is not required to implement or possess all the devices shown. More or fewer devices may be implemented or possessed instead. Figure 4 Each block shown in the figure may represent one device, or may represent multiple devices as required.
[0085] In particular, according to some embodiments of the present disclosure, the process described above with reference to the flowchart can be implemented as a computer software program. For example, some embodiments of the present disclosure include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In some such embodiments, the computer program can be downloaded and installed from the network through the communication device 409, or installed from the storage device 408, or installed from the ROM 402. When the computer program is executed by the processing device 401, the above-mentioned functions defined in the method of some embodiments of the present disclosure are executed.
[0086] It should be noted that the computer-readable medium recorded in some embodiments of the present disclosure may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In some embodiments of the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, device or device. In some embodiments of the present disclosure, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, which carries a computer-readable program code. This propagated data signal may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. The computer readable signal medium may also be any computer readable medium other than a computer readable storage medium, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. The program code contained on the computer readable medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, RF (radio frequency), etc., or any suitable combination of the above.
[0087] In some embodiments, the client and the server may communicate using any currently known or future developed network protocol such as HTTP (HyperText Transfer Protocol), and may be interconnected with any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), an internet (e.g., the Internet), and a peer-to-peer network (e.g., an ad hoc peer-to-peer network), as well as any currently known or future developed network.
[0088] The computer-readable medium may be included in the electronic device; or it may exist independently without being assembled into the electronic device. The computer-readable medium carries one or more programs. When the one or more programs are executed by the electronic device, the electronic device: sends a timestamp notification message to the client, wherein the timestamp notification message includes the first current timestamp of the server, and the first current timestamp of the server is a timestamp under the server time base. In response to receiving the data request message sent by the client, a requested network delay time is generated according to the corrected client timestamp included in the data request message, wherein the corrected client timestamp is a timestamp under the server time base. According to the requested network delay time, client call information is generated. The client call information is sent to the call chain system to create a call link with the client basic working unit as the starting point of the call chain.
[0089] Computer program code for performing the operations of some embodiments of the present disclosure may be written in one or more programming languages or a combination thereof, including object-oriented programming languages such as Java, Smalltalk, C++, and conventional procedural programming languages such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).
[0090] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present disclosure. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some implementations as replacements, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs the specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.
[0091] The units described in some embodiments of the present disclosure may be implemented by software or hardware. The units described may also be set in a processor, for example, it may be described as: a processor includes a notification unit, a receiving unit, a generating unit, and a sending unit. The names of these units do not constitute a limitation on the units themselves in some cases, for example, the notification unit may also be described as a "unit for sending timestamp notification information to a client".
[0092] The functions described above herein may be performed at least in part by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), complex programmable logic devices (CPLDs), and the like.
[0093] The above descriptions are only some preferred embodiments of the present disclosure and an explanation of the technical principles used. Those skilled in the art should understand that the scope of the invention involved in the embodiments of the present disclosure is not limited to the technical solutions formed by a specific combination of the above-mentioned technical features, but should also cover other technical solutions formed by any combination of the above-mentioned technical features or their equivalent features without departing from the above-mentioned inventive concept. For example, the above-mentioned features are replaced with the technical features with similar functions disclosed in the embodiments of the present disclosure (but not limited to) and the technical solutions formed.
Claims
1. A call link generation method, comprising: Sending timestamp notification information to the client, wherein the timestamp notification information includes a first current timestamp of the server, and the first current timestamp of the server is a timestamp under a time reference of the server; In response to receiving the data request information sent by the client, generating a requested network delay time according to a corrected client timestamp included in the data request information, wherein the corrected client timestamp is a timestamp under the server time reference; Generate client call information according to the requested network delay time; Sending the client call information to a call chain system to create a call chain with the client basic work unit as the call chain starting point; The corrected client timestamp is generated by the following steps: In response to receiving the timestamp notification information, determining a first current timestamp of the client, wherein the first current timestamp of the client is a timestamp under a client time reference; Determine the difference between the first current timestamp of the client and the first current timestamp of the server included in the timestamp notification information as a time offset; In response to receiving an instruction to send data request information to the server, determining a second current timestamp of the client, wherein the second current timestamp of the client is a timestamp under the client time reference; Determine the difference between the second current timestamp of the client and the time offset as the corrected client timestamp; The step of generating the requested network delay time according to the corrected client timestamp included in the data request information includes: In response to receiving the data request information sent by the client, determining a second current timestamp of the server, wherein the second current timestamp of the server is a timestamp under the time reference of the server; Determine the difference between the second current timestamp of the server and the corrected timestamp of the client as the network delay time, wherein the network delay time includes the notification network delay time and the request network delay time; According to a preset assumption and the network delay time, a value of the requested network delay time is determined, wherein the assumption is that the notified network delay time is equal to the requested network delay time.
2. The method according to claim 1, wherein: The sending of timestamp notification information to the client includes: Send timestamp notification information to the client at preset time intervals.
3. The method according to claim 1, wherein: The client basic working unit is a basic working unit generated by the call chain system according to the client call information.
4. A call link generation device, comprising: A notification unit, configured to send timestamp notification information to the client, wherein the timestamp notification information includes a first current timestamp of the server, and the first current timestamp of the server is a timestamp under a time reference of the server; A receiving unit, configured to generate a requested network delay time according to a corrected client timestamp included in the data request information in response to receiving the data request information sent by the client, wherein the corrected client timestamp is a timestamp under the server time reference; A generating unit, configured to generate client call information according to the request network delay time; A sending unit, configured to send the client call information to a call chain system to create a call chain with the client basic working unit as the starting point of the call chain; The corrected client timestamp is generated by the following steps: In response to receiving the timestamp notification information, determining a first current timestamp of the client, wherein the first current timestamp of the client is a timestamp under a client time reference; Determine the difference between the first current timestamp of the client and the first current timestamp of the server included in the timestamp notification information as a time offset; In response to receiving an instruction to send data request information to the server, determining a second current timestamp of the client, wherein the second current timestamp of the client is a timestamp under the client time reference; Determine the difference between the second current timestamp of the client and the time offset as the corrected client timestamp; The step of generating the requested network delay time according to the corrected client timestamp included in the data request information includes: In response to receiving the data request information sent by the client, determining a second current timestamp of the server, wherein the second current timestamp of the server is a timestamp under the time reference of the server; Determine the difference between the second current timestamp of the server and the corrected timestamp of the client as the network delay time, wherein the network delay time includes the notification network delay time and the request network delay time; According to a preset assumption and the network delay time, a value of the requested network delay time is determined, wherein the assumption is that the notified network delay time is equal to the requested network delay time.
5. An electronic device, comprising: one or more processors; a storage device having one or more programs stored thereon; When the one or more programs are executed by the one or more processors, the one or more processors implement the method according to any one of claims 1 to 3.
6. A computer readable medium having a computer program stored thereon, wherein: When the program is executed by a processor, the method according to any one of claims 1 to 3 is implemented.
Citation Information
Patent Citations
Method and device for time synchronization, time stamping device and trusted time server
CN102739626A
Clock synchronization method and device, computer storage medium and electronic equipment
CN110649984A
Time synchronization method and device
CN110768740A
Time calibration method and device, computer equipment and storage medium
CN112968747A
Using bandwidth measurements to adjust CIR and EIR on a sub-rate link
US20140160945A1
