Time synchronization method, electronic device, server and storage medium

Abstract

Embodiments of the present invention relate to the field of communications and disclose a time synchronization method, electronic device, server, and storage medium. In the present invention, an air interface message sent by a base station is received and parsed to extract synchronization time information and leap second prediction information from the air interface message. Time synchronization with the base station is performed based on the synchronization time information and leap second prediction information. This method enables the leap second prediction to be acquired in advance. Therefore, based on the synchronization time information and leap second prediction information, time synchronization with the base station can be maintained even when a leap second occurs, thereby improving the accuracy of time synchronization.

Description

Technical Field

[0001] The embodiments of the present invention relate to the field of communications, and in particular to a time synchronization method, electronic equipment, a server, and a storage medium. Background Art

[0002] A leap second is a one-second increment or decrement to UTC (Coordinated Universal Time) at the end of the year, mid-year, or end of the quarter, standardized by the International Bureau of Weights and Measures to keep Coordinated Universal Time (UT) close to UT. Due to the unevenness and long-term slowness of the Earth's rotation, if the difference between UT and International Atomic Time (IAT) exceeds ±0.9 seconds, UTC is adjusted forward by one second (a negative leap second, meaning the last minute is 59 seconds) or backward by one second (a positive leap second, meaning the last minute is 61 seconds).

[0003] Currently, when a 5G terminal device is the target device for time synchronization, it achieves time synchronization through 5G wireless air interface timing. Specifically, the 5G terminal device receives messages from the base station and parses the messages to obtain the synchronization time, thereby achieving time synchronization with the base station. The inventors have discovered that the prior art has at least the following problems: When using 5G wireless air interface timing for time synchronization, the 5G terminal device cannot obtain leap second predictions in advance. After the leap second occurs, the UTC calculated by the 5G terminal device will be incorrect, resulting in inaccurate time synchronization. Summary of the Invention

[0004] The purpose of the embodiments of the present invention is to provide a time synchronization method, electronic equipment, server and storage medium, which improve the accuracy of time synchronization.

[0005] To solve the above technical problems, an embodiment of the present invention provides a time synchronization method, comprising the following steps: receiving an air interface message sent by a base station, and parsing synchronization time information and leap second prediction information from the air interface message; and performing time synchronization with the base station based on the synchronization time information and the leap second prediction information.

[0006] An embodiment of the present invention also provides a time synchronization method, including: receiving a second synchronization message sent by an external clock source, and parsing synchronization time information and leap second prediction information from the second synchronization message; sending an air interface message containing the synchronization time information and the leap second prediction information to a target device, so that the target device can perform time synchronization with the sender of the air interface message based on the synchronization time information and the leap second prediction information.

[0007] An embodiment of the present invention also provides an electronic device, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute the time synchronization method as described above.

[0008] An embodiment of the present invention also provides a server, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute the time synchronization method as described above.

[0009] An embodiment of the present invention further provides a computer-readable storage medium storing a computer program, wherein the computer program implements the above-mentioned time synchronization method when executed by a processor.

[0010] Compared with the prior art, the embodiment of the present invention receives an air interface message sent by a base station and parses the synchronization time information and leap second prediction information from the air interface message. In this way, the leap second prediction can be obtained in advance, so that time synchronization with the base station can be maintained at the moment when a leap second occurs based on the synchronization time information and leap second prediction information, thereby improving the accuracy of time synchronization.

[0011] In addition, the air interface message exists in the form of a protocol message; and parsing the synchronization time information and leap second prediction information from the air interface message includes: parsing a first field and a second field from the protocol message; wherein the first field carries the synchronization time information, and the second field carries the leap second prediction information. Carrying the synchronization time information and leap second prediction information in the first field and the second field of the protocol message is simple and meets the needs of practical applications.

[0012] Furthermore, the protocol message is based on the 38.331 protocol, the first field is an existing field in the protocol message, and the second field is a newly added field. Adding a new second field to the protocol message, which already includes the first field carrying time synchronization information, to carry the leap second prediction message can be achieved with only minor adjustments to the existing protocol message structure, without affecting the content carried by the existing fields in the protocol message, resulting in a low adjustment cost.

[0013] Alternatively, the protocol message is a system information message (SIB9), and the first field and the second field are located within a field of the SIB9 message used to represent time information. Alternatively, the protocol message is a radio resource control (RRC) message, and the first field and the second field are located within a field of the RRC message used to represent reference time information. SIB9 messages are multicast messages, enabling accurate time synchronization of multiple devices simultaneously. RRC messages are unicast messages, enhancing the security of device timing.

[0014] In addition, after parsing the synchronization time information and leap second prediction information from the air interface message, the method further includes: sending a first synchronization message containing the synchronization time information and the leap second prediction information to a downstream device connected to the sender of the first synchronization message, wherein the first synchronization time message is used by the downstream device to synchronize time with the sender based on the synchronization time information and the leap second prediction information. In this way, the downstream device connected to the sender of the first synchronization message can also obtain the leap second prediction in advance. When a leap second occurs, the downstream device can maintain time synchronization with the sender, thereby improving the accuracy of time synchronization.

[0015] In addition, the first synchronization message exists in the form of a serial time code; a first code element preset in the serial time code carries the synchronization time information, and a second code element preset in the serial time code carries the leap second prediction information. The first synchronization message exists in the form of a serial time code, and the serial time code already has the first and second code elements preset, so there is no need to reconstruct the format of the serial time code, and there is essentially no adjustment cost.

[0016] In addition, the serial time code is an IRIG-B code. As a new time synchronization standard, the IRIG-B code has the characteristics of strong anti-interference ability, etc., which can enhance the security of the sender of the first synchronization message when timing the lower-level device. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] One or more embodiments are exemplarily illustrated by pictures in the corresponding drawings. These exemplifications do not constitute limitations on the embodiments. Elements with the same reference numerals in the drawings are represented as similar elements. Unless otherwise stated, the figures in the drawings do not constitute proportional limitations.

[0018] Figure 1 is a flow chart of a time synchronization method according to a first embodiment of the present invention;

[0019] Figure 2 is a schematic structural diagram of the format of the SIB9 message according to the first embodiment of the present invention;

[0020] Figure 32 is a schematic structural diagram of the format of the field domain used to represent reference time information in the RRC message according to the first embodiment of the present invention;

[0021] Figure 4 is a flowchart of a time synchronization method according to a second embodiment of the present invention;

[0022] Figure 5 is a schematic structural diagram of the standard format of the IRIG-B code according to the second embodiment of the present invention;

[0023] Figure 6 is a flowchart of a time synchronization method according to a third embodiment of the present invention;

[0024] Figure 7 It is a schematic structural diagram of the electronic device in the fourth embodiment or the server in the fifth embodiment according to the present invention. DETAILED DESCRIPTION

[0025] In order to make the purpose, technical solutions and advantages of the embodiments of the present invention clearer, the embodiments of the present invention will be described in detail below with reference to the accompanying drawings. However, it will be understood by those skilled in the art that in the embodiments of the present invention, many technical details are provided to enable the reader to better understand the present application. However, even without these technical details and various changes and modifications based on the following embodiments, the technical solutions claimed in the present application can be implemented. The division of the following embodiments is for convenience of description and should not constitute any limitation on the specific implementation of the present invention. The various embodiments can be combined with each other and referenced to each other under the premise that there is no contradiction.

[0026] The first embodiment of the present invention relates to a time synchronization method, which is applied to electronic devices, such as 5G terminals. This embodiment and the following embodiments are described with reference to 5G terminals, but are not limited thereto. The specific process is as follows Figure 1 Shown, including:

[0027] Step 101: Receive an air interface message sent by a base station, and parse the air interface message to obtain synchronization time information and leap second prediction information.

[0028] Specifically, the 5G terminal receives an air interface message sent by the base station, which includes synchronization time information and leap second prediction information, and parses the air interface message to obtain the synchronization time information and leap second prediction information. The air interface message can exist in the form of a cell, a protocol message, etc. The synchronization time information is the current UTC time, and the 5G terminal sets the current UTC time as the local time; the leap second prediction information includes the time when the leap second occurs and the type of leap second. The time when the leap second occurs is generally the last minute of a certain day, and the type of leap second is a positive leap second, i.e., the last minute is 61 seconds, or a negative leap second, i.e., the last minute is 59 seconds, or no leap second, i.e., the last minute is 60 seconds. In one example, the leap second prediction information is an alarm message, which indicates that the local clock has never been synchronized. In one example, the air interface message can also include one of the following information or any combination thereof: daylight saving time information, time zone offset information, leap seconds, etc., where leap seconds refer to the difference between atomic time GPS time and UTC time. In an example, the air interface message may further include one of the following information or any combination thereof: time message type, time reference SFN, uncertainty value, etc.

[0029] In one example, an air interface message exists in the form of a protocol message; parsing the synchronization time information and leap second prediction information from the air interface message includes: parsing a first field and a second field from the protocol message; wherein the first field carries the synchronization time information and the second field carries the leap second prediction information.

[0030] Specifically, the protocol followed by the 5G terminal and the base station determines the format of the protocol message. The 5G terminal parses the first field and the second field from the protocol message. The synchronization time information can be obtained based on the content of the first field. The leap second occurrence time and the type of leap second can be determined based on the content of the second field. The leap second type can be determined by the value of the leap second indicator (leapindicator) in the second field. Different values ​​represent different leap second types. For example, when the value of the leapindicator is 0, it indicates that the leap second type is no leap second. When the value of the leapindicator is 1, it indicates that the leap second type is a positive leap second. When the value of the leapindicator is 2, it indicates that the leap second type is a negative leap second. In one example, the leap second warning information is an alarm information. The alarm information can be determined by the value of the leapindicator in the second field. For example, when the value of the leapindicator is 3, it indicates that it is an alarm information. In one example, the protocol message may also include one or any combination of the following information: daylight saving time information, time zone offset information, leap second, etc. Each type of information occupies a different field of the protocol message. In an example, the protocol message may further include one of the following information or any combination thereof: time message type, time reference SFN, uncertainty value, etc. Each type of information occupies a different field of the protocol message.

[0031] In an example, the protocol commonly followed between the 5G terminal and the base station is a new protocol, the protocol message is a protocol message constructed based on the new protocol, the first field and the second field are both fields in the message constructed based on the new protocol, the first field and the second field can be included in the same protocol message or in different protocol messages; wherein, the new protocol can be constructed by developers according to actual conditions.

[0032] In one example, the protocol message is a protocol message based on the 38.331 protocol, the first field is the original field in the protocol message, and the second field is a newly added field in the protocol message. Specifically, the 38.331 protocol is commonly followed between 5G terminals and base stations. The 38.331 protocol is one of the 38 series in the 3GPP (Third Generation Partnership Project) version, and the 38.331 protocol supports multicast messages and unicast messages. The original fields of the protocol message based on the 38.331 protocol include a first field that carries synchronization time information, and a new second field is added to carry leap second prediction information. The bytes occupied by the second field are set according to actual needs, for example: the bytes occupied by the second field are 2 bytes. The first field and the second field can be included in the same protocol message or in different protocol messages. In an example, the protocol message is a system information message SIB9 (System Information Block 9), and the first field and the second field are in the field domain of the SIB9 message used to represent time information. Specifically, the structural diagram of the format of the SIB9 message is as follows Figure 2 As shown, the fields in the SIB9 message are indicated by sequence numbers 1-11, sequence numbers 1-5 indicate the field domain representing time information, sequence numbers 6-10 indicate the field domain reserved for extension, and sequence number 11 indicates the field domain representing reference time information, wherein sequence number 1 indicates the first field and is the original field, sequence number 2 indicates the second field and is a newly added field, and both the first field and the second field are in the field domain used to represent time information. In an example, as Figure 2 As shown, serial number 3 indicates the third field and is the original field, carrying daylight saving time information, serial number 4 indicates the fourth field and is the original field, carrying time zone offset information, and serial number 3 indicates the fifth field and is the original field, carrying leap second information.

[0033] In one example, the protocol message is a radio resource control message RRC (Radio Resource Control), and the first field and the second field are in the field domain of the RRC message used to represent the reference time information. Specifically, the structural diagram of the format of the field domain used to represent the reference time information in the RRC message is as follows: Figure 3As shown, sequence numbers 1-5 indicate the field domain representing the reference time information in the RRC message, wherein sequence number 1 indicates the first field and is the original field, sequence number 2 indicates the second field and is a newly added field, and both the first field and the second field are in the field domain used to represent the reference time information. In an example, Figure 3 As shown, sequence number 3 indicates the third field and is the original field, carrying the time message type, sequence number 4 indicates the fourth field and is the original field, carrying the time reference SFN, and sequence number 5 indicates the fifth field and is the original field, carrying the uncertainty value.

[0034] Step 102: Perform time synchronization with the base station based on the synchronization time information and leap second prediction information.

[0035] Specifically, since the leap second has not yet occurred when the 5G terminal receives the air interface message including the synchronization time information and leap second prediction information, the 5G terminal sets the current UTC time as the local time and changes the local time according to the normal state to achieve time synchronization with the base station; when the leap second occurs, the correct UTC time is calculated according to the type of leap second, and the time synchronization with the base station can be maintained at the moment the leap second occurs, thereby improving the accuracy of time synchronization. For example, if the leap second occurs in the last minute of June 30, if the leap second type is no leap second, the 5G terminal changes the UTC time in the last minute of June 30 according to "..., 23:59:59, 00:00:00, 00:00:01,...", that is, at 23:59:59 on June 30, it jumps to 00:00:00 on July 1; if the leap second type is positive leap second, the 5G terminal changes the UTC time in the last minute of June 30 according to "..., 23:59:59, 23:59:60, 00 That is, at 23:59:59 on June 30, it first jumps to 23:59:60 on June 30, and then jumps to 00:00:00 on July 1; if the leap second type is a negative leap second, the 5G terminal changes the UTC time in the last minute of June 30 according to “…, 23:59:58, 00:00:00, 00:00:01, …”, that is, at 23:59:58 on June 30, it directly jumps to 00:00:00 on July 1.

[0036] In this embodiment, an air interface message sent by a base station is received, and synchronization time information and leap second prediction information are parsed from the air interface message. This allows the leap second prediction to be acquired in advance, and thus, based on the synchronization time information and leap second prediction information, the time synchronization with the base station can be maintained even when a leap second occurs, thereby achieving accurate time synchronization.

[0037] The second embodiment of the present invention relates to a time synchronization method. The second embodiment is substantially the same as the first embodiment, with the main difference being that a first synchronization message containing synchronization time information and leap second prediction information is also sent to a lower-level device connected to the sender of the first synchronization message. The specific process is as follows: Figure 4 Shown, including:

[0038] Step 201: Receive an air interface message sent by a base station, and parse the air interface message to obtain synchronization time information and leap second prediction information.

[0039] Step 202: Perform time synchronization with the base station based on the synchronization time information and leap second prediction information.

[0040] Steps 201-202 are similar to steps 101-102 and will not be repeated here.

[0041] Step 203: Send a first synchronization message containing synchronization time information and leap second prediction information to a downstream device connected to the sender of the first synchronization message. The first synchronization time message is used by the downstream device to synchronize time with the sender according to the synchronization time information and leap second prediction information.

[0042] Specifically, the sender of the first synchronization message is a 5G terminal. The format of the first synchronization message is a format pre-agreed between the 5G terminal and the downstream device connected to the 5G terminal. The first synchronization message can exist in the form of a message, a serial time code, etc. The 5G terminal constructs the first synchronization message containing synchronization time information and leap second prediction information according to the pre-agreed format and sends it to the downstream device. The downstream device can be a downstream device connected to the 5G terminal in application fields such as smart grids, smart factories, and industrial Internet. For example, in the field of power applications, the downstream device can be a data transfer unit (DTU) and / or a phasor measurement unit (PMU).

[0043] After receiving the first synchronization message sent by the 5G terminal, the lower-level device parses the first synchronization message to obtain synchronization time information and leap second prediction information. The synchronization time information is the current UTC time, and the leap second prediction information includes the time when the leap second occurs and the type of leap second. The lower-level device sets the current UTC time as the local time and changes the local time according to the normal state to achieve time synchronization with the 5G terminal. When a leap second occurs, the lower-level device calculates the correct UTC time based on the leap second type. Even at the time of the leap second, the time synchronization with the 5G terminal can be maintained, achieving accurate time synchronization.

[0044] In one example, the first synchronization message exists in the form of a serial time code; the first code element preset in the serial time code carries the synchronization time information, and the second code element preset in the serial time code carries the leap second prediction information. Specifically, the serial time code has a preset first code element and a second code element reserved therein to carry the synchronization time information and the leap second prediction information, respectively. The 5G terminal writes the synchronization time information into the first code element and writes the leap second prediction information into the second code element. In one example, the serial time code is an IRIG-B code. Regarding the standard format of the IRIG-B code, the structural diagram of the standard format of the IRIG-B code is as follows: Figure 5 As shown, sequence numbers 0-99 indicate symbols. The first symbol includes symbols numbered 1 to 59, which carry synchronization time information. The second symbol includes symbols numbered 60 and 61. Symbol numbered 60 is the leap second notice (LSP) flag, indicating the time when a leap second occurs. It is set to 1 59 seconds before the leap second occurs and to 0 00 seconds after the leap second occurs. If there is no leap second, symbol numbered 60 is always set to 0. Symbol numbered 61 is the leap second (LS) flag, indicating the type of leap second: "0" indicates a positive leap second, and "1" indicates a negative leap second.

[0045] In this embodiment, by sending a first synchronization message containing synchronization time information and leap second prediction information to a downstream device connected to the sender of the first synchronization message, the downstream device can also obtain the leap second prediction in advance. When the leap second occurs, the downstream device can maintain time synchronization with the sender, thereby improving the accuracy of time synchronization.

[0046] The third embodiment of the present invention relates to a time synchronization method, which is applied to a base station. The specific process is as follows: Figure 6 Shown, including:

[0047] Step 301: Receive a second synchronization message sent by an external clock source, and parse the second synchronization message to obtain synchronization time information and leap second prediction information.

[0048] In one example, the external clock source is a satellite clock source. Satellite clock sources are based on the Global Navigation Satellite System (GNSS), including the Global Positioning System (GPS) and the BeiDou Satellite Navigation and Positioning System. A satellite receiver in the system parses satellite messages to obtain synchronized time information and leap second prediction information. It then sends a second synchronization message containing this information to the base station. The base station then parses the second synchronization message to obtain the synchronized time information and leap second prediction information.

[0049] In one example, the external clock source is a network clock source. A network clock source is a clock source connected via a wired connection, such as a 1588 clock source. The protocol used by the network clock source and the base station can be the Precision Time Protocol (PTP) or the Network Time Protocol (NTP). The second synchronization message is in the form of a protocol message.

[0050] Step 302: Send an air interface message containing the synchronization time information and leap second prediction information to a target device, so that the target device can synchronize time with the sender of the air interface message according to the synchronization time information and leap second prediction information.

[0051] Specifically, after receiving the second synchronization message, the base station sends an air interface message containing the synchronization time information and leap second prediction information to the target device according to the agreed period, that is, the sender of the air interface message is the base station, and the air interface message can exist in the form of a message or a cell. In one example, the air interface message exists in the form of a protocol message; sending the air interface message containing the synchronization time information and the leap second prediction information to the target device includes: writing the synchronization time information into the first field in the protocol message, writing the leap second prediction information into the second field in the protocol message, and sending the protocol message to the target device. In one example, the protocol message is a protocol message defined based on a new protocol, and the first field and the second field are both newly added fields in the protocol message. In one example, the protocol message is a protocol message based on the 38.331 protocol, the first field is the original field in the protocol message, and the second field is a newly added field in the protocol message.

[0052] In this embodiment, the base station receives the second synchronization message sent by the external clock source, and can accurately obtain the current synchronization time information and leap second prediction information, and send the air interface message containing the synchronization time information and leap second prediction information to the target device, so that the target device can obtain the leap second prediction in advance, and thus can maintain time synchronization with the base station at the moment when the leap second occurs based on the synchronization time information and leap second prediction information, thereby achieving accurate time synchronization between the target device and the base station.

[0053] The steps of the various methods above are divided only for the purpose of clear description. During implementation, they can be combined into one step or some steps can be split and decomposed into multiple steps. As long as they include the same logical relationship, they are all within the scope of protection of this patent. Adding insignificant modifications or introducing insignificant designs to the algorithm or process without changing the core design of the algorithm and process are all within the scope of protection of this patent.

[0054] A fourth embodiment of the present invention relates to an electronic device, such as Figure 7As shown, it includes: at least one processor 402; and a memory 401 that is communicatively connected to the at least one processor; wherein the memory 401 stores instructions that can be executed by the at least one processor 402, and the instructions are executed by the at least one processor 402 to enable the at least one processor 402 to execute the time synchronization method of embodiment one or embodiment two.

[0055] The fifth embodiment of the present invention relates to a server, which is a server inside a base station, such as Figure 7 As shown, it includes: at least one processor 402; and a memory 401 that is communicatively connected to the at least one processor; wherein the memory 401 stores instructions that can be executed by the at least one processor 402, and the instructions are executed by the at least one processor 402 to enable the at least one processor 402 to execute the time synchronization method of embodiment three.

[0056] Memory 401 and processor 402 are connected using a bus. The bus may include any number of interconnected buses and bridges, connecting one or more processors 402 and various circuits of memory 401. The bus may also connect various other circuits such as peripheral devices, voltage regulators, and power management circuits. These are all well known in the art and, therefore, will not be described further herein. The bus interface provides an interface between the bus and the transceiver. The transceiver may be a single component or multiple components, such as multiple receivers and transmitters, providing a unit for communicating with various other devices over a transmission medium. Data processed by processor 402 is transmitted over a wireless medium via an antenna. Furthermore, the antenna receives data and transmits it to processor 402.

[0057] The processor 402 is responsible for managing the bus and general processing, and may also provide various functions, including timing, peripheral interfaces, voltage regulation, power management, and other control functions. The memory 401 may be used to store data used by the processor 402 when performing operations.

[0058] A sixth embodiment of the present invention relates to a computer-readable storage medium storing a computer program, which implements the above method embodiment when executed by a processor.

[0059] That is, those skilled in the art will understand that all or part of the steps in the above-mentioned embodiments can be implemented by instructing the relevant hardware through a program, which is stored in a storage medium and includes a number of instructions for causing a device (which may be a single-chip microcomputer, chip, etc.) or a processor to execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: 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, etc., various media that can store program code.

[0060] Those skilled in the art will appreciate that the above embodiments are specific embodiments for implementing the present invention, and that in actual applications, various changes may be made thereto in form and detail without departing from the spirit and scope of the present invention.

Claims

1. A time synchronization method, characterized in that: include: receiving an air interface message sent by a base station, and parsing the air interface message to obtain synchronization time information and leap second prediction information; The air interface message exists in the form of a protocol message based on the 38.331 protocol; and parsing the synchronization time information and leap second prediction information from the air interface message includes: Parsing the protocol message to obtain a first field and a second field, wherein the first field carries the synchronization time information, and the second field carries the leap second prediction information; performing time synchronization with the base station according to the synchronization time information and the leap second prediction information; A first synchronization message including the synchronization time information and the leap second prediction information is sent to a lower-level device connected to a sending end of the first synchronization message, wherein the first synchronization time message is used by the lower-level device to perform time synchronization with the sending end based on the synchronization time information and the leap second prediction information.

2. The time synchronization method according to claim 1, wherein: The first field is an original field in the protocol message, and the second field is a newly added field in the protocol message.

3. The time synchronization method according to claim 2, characterized in that: The protocol message is a system information message SIB9, and the first field and the second field are in a field domain of the SIB9 message used to represent time information; Alternatively, the protocol message is a radio resource control message RRC, and the first field and the second field are in a field domain of the RRC message used to represent reference time information.

4. The time synchronization method according to claim 1, wherein: The first synchronization message exists in the form of a serial time code; a first code element preset in the serial time code carries the synchronization time information, and a second code element preset in the serial time code carries the leap second prediction information.

5. The time synchronization method according to claim 4, characterized in that: The serial time code is an IRIG-B code.

6. A time synchronization method, characterized in that: include: receiving a second synchronization message sent by an external clock source, and parsing the second synchronization message to obtain synchronization time information and leap second prediction information; Sending an air interface message including the synchronization time information and the leap second prediction information to a target device, so that the target device performs time synchronization with a sender of the air interface message according to the synchronization time information and the leap second prediction information; Sending a second synchronization message including the synchronization time information and the leap second prediction information to a downstream device connected to a sending end of the second synchronization message, wherein the second synchronization time message is used by the downstream device to perform time synchronization with the sending end according to the synchronization time information and the leap second prediction information; wherein the air interface message exists in the form of a protocol message based on the 38.331 protocol; sending the air interface message including the synchronization time information and the leap second prediction information to the target device includes: The synchronization time information is written into a first field in the protocol message, the leap second prediction information is written into a second field in the protocol message, and the protocol message is sent to a target device.

7. The time synchronization method according to claim 6, characterized in that: The external clock source is a satellite clock source or a network clock source.

8. An electronic device, characterized in that: include: at least one processor; as well as, a memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the time synchronization method according to any one of claims 1 to 5.

9. A server, characterized in that: include: at least one processor; as well as, a memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the time synchronization method according to any one of claims 6 to 7.

10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the time synchronization method according to any one of claims 1 to 5 or the time synchronization method according to any one of claims 6 to 7 is implemented.

Images