A Timing Method and Device for Handling Link Abnormalities

Abstract

An embodiment of the present application provides a timing method and device for coping with link anomalies, which relates to the field of communication technologies, can prevent the phenomenon of dual master clocks in the TSN domain, improve the synchronization accuracy of TSN devices, and reduce the air interface overhead of 5GS. The specific solution is as follows: receiving a first synchronization message from a first terminal device; receiving a second synchronization message from a second terminal device or a server; if the TSN domains to which the first synchronization message and the second synchronization message belong are the same, determining the synchronization message to be forwarded from the first synchronization message and the second synchronization message. Then, if the message to be forwarded is the first synchronization message, the first synchronization message is forwarded and the second synchronization message is filtered. The embodiment of the present application is used in 5GS to improve the timing accuracy of the TSN device timing process.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of communication technologies, and in particular, to a timing method and apparatus for coping with link anomalies. Background Art

[0002] In an industrial control scenario, the control signaling sent by the master node can reach the slave node within a specified time, and the slave node can execute the actions indicated by the control signaling at the specified time point. Therefore, the network in an industrial control scenario is usually a time-sensitive network (TSN).

[0003] TSN can regard the 5th generation mobile networks system (5GS) as a TSN bridge device. The service data packets of TSN can be sent uplink / downlink through 5GS. Moreover, TSN can also regard 5GS as a transparent clock (TC). To ensure the stability and reliability of the time synchronization service, TSN will equip each TSN domain with a primary clock and a backup clock at the same time. Only when the primary clock is damaged or the link has an anomaly, the backup clock becomes effective and starts to publish a synchronization message stream for the entire TSN topology. The protocol stipulates that in each TSN domain, only one time synchronization source is allowed at the same time. When the primary clock is working properly, the TSN device where the primary clock is located publishes a synchronization message stream to the entire TSN topology, and the "clock target" corresponding to the backup clock receives the periodic primary clock signal as a sleep instruction. Once the primary clock fails and the "clock target" does not receive continuous sleep instructions, the backup clock is triggered to be enabled, and the backup clock starts to take over the role of the primary clock and publishes a synchronization message stream to the entire TSN topology.

[0004] That is to say, whether to enable the backup clock is determined by the TSN device with the backup master clock itself. In this case, once the backup clock does not receive consecutive sleep instructions, the backup clock starts by itself. However, this method is prone to the phenomenon of dual master clocks. This is because the backup clock cannot determine whether it is the uplink air interface link on the master clock side or the downlink air interface link on the backup clock side that has problems. Once the uplink air interface link on the master clock side is normal, but the downlink air interface link on the backup clock side is abnormal, the backup clock will erroneously think that the master clock side has a fault and erroneously enable the backup clock to send out the synchronization message stream. And 5GS, as the TC, all its network elements forward the synchronization messages without performing filtering operations such as opening, reading, or identifying, so it will cause the problem of two timing clock signals appearing simultaneously in the TSN. Because errors will be introduced between different clock sources, when the TSN device receives the timing signals from multiple clock sources, the synchronization accuracy of the TSN device may be reduced; at the same time, for 5GS, if multiple redundant timing TSN signals are forwarded simultaneously, it will inevitably increase unnecessary air interface overhead. Summary of the Invention

[0005] An embodiment of the present application provides a timing method and device for coping with link anomalies, which can prevent the phenomenon of dual master clocks in the TSN domain, improve the synchronization accuracy of TSN devices, and reduce the air interface overhead of 5GS.

[0006] To achieve the above object, the embodiments of the present application adopt the following technical solutions:

[0007] In a first aspect, a timing method for coping with link anomalies is provided. This method can be applied to a core network device or a chip in a core network device. The method includes: receiving a first synchronization message from a first terminal device; receiving a second synchronization message from a second terminal device or a server; if the TSN domains to which the first synchronization message and the second synchronization message belong are the same, determine the synchronization message to be forwarded from the first synchronization message and the second synchronization message. Then, if the message to be forwarded is the first synchronization message, forward the first synchronization message and filter the second synchronization message; if the message to be forwarded is the second synchronization message, forward the second synchronization message and filter the first synchronization message. Among them, the core network device can be a UPF.

[0008] In the existing timing scheme, when the backup clock does not receive the sleep instruction sent by the master clock, it is considered that the master clock has a fault. However, the backup clock cannot determine whether it is the uplink air interface link on the master clock side or the downlink air interface on the backup clock side that has problems. Once the air interface link of the master clock is normal but the downlink air interface of the backup clock is abnormal (which can be understood as intermittent), the backup clock will erroneously think that the master clock side has a fault and erroneously enable the backup clock and upload the synchronization message to the UPF, thus affecting the synchronization accuracy of the slave clock.

[0009] In this application, when the core network device receives both the synchronization message of the primary clock and the synchronization message of the backup clock in the same TSN domain, the core network device can determine the synchronization message to be forwarded and the synchronization message to be filtered from the two synchronization messages. That is to say, the core network device determines whether to enable the backup clock by determining the synchronization message to be forwarded at this time. Compared with the prior art where the core network device does not perform operations such as opening and reading on the synchronization message to be forwarded and only forwards the synchronization message, the core network device in this application can determine the synchronization message to be forwarded from the two synchronization messages, which can avoid submitting the two messages to the TSN server or the air interface simultaneously, saving signaling interaction and air interface overhead, and improving the synchronization accuracy of the slave clock.

[0010] In a possible design, the TSN domains to which the first synchronization message and the second synchronization message belong are the same, including: the virtual local area network (VLAN) identifier (VID) carried in the first synchronization message is the same as the VID carried in the second synchronization message, that is, when the VIDs carried in the synchronization messages sent by terminal devices or servers belonging to the same VLAN are the same, the TSN domains to which the synchronization messages belong are the same; or, the sequence number of the TSN domain carried in the header of the first synchronization message is the same as the sequence number of the TSN domain carried in the second synchronization message, that is, the sequence numbers of the TSN domains carried in the synchronization messages of the same TSN domain are the same; or, the address of the first terminal device carried in the first synchronization message and the address of the second terminal device or server carried in the second synchronization message both belong to the TSN domain. This address can be an IP address, a MAC address, etc., and the binding relationship between the address and the TSN domain can be informed to the network device through capability reporting when the terminal device or server establishes a connection with the network device.

[0011] In a possible design, determining the synchronization message to be forwarded from the first synchronization message and the second synchronization message includes: determining the synchronization message to be forwarded in the first synchronization message and the second synchronization message according to the address of the clock carried in the first synchronization message and the address of the clock carried in the second synchronization message.

[0012] Among them, the first synchronization message can correspond to one source address and multiple destination addresses, and the second synchronization message can also correspond to one source address and multiple destination addresses. The source address is the address of the primary clock or the backup primary clock, and the destination address is the address of the slave clock to be time-synchronized. Since the primary clock, the backup clock, and the slave clock can bind fixed IP / MAC addresses when initially accessing the 5GS and report the information of the primary clock and the backup clock and the bound address information to the core network elements (such as UPF / SMF / AMF, etc.), once the UPF receives synchronization messages with two different addresses in the same TSN domain, it can compare the IP / MAC addresses of the synchronization messages in the received TSN domain with the address of the primary clock and the address of the backup clock pre-stored in the TSN domain, so as to determine the synchronization message to be forwarded in the first synchronization message and the second synchronization message.

[0013] According to the above method for determining the synchronization message to be forwarded, in a possible design, the result may be that: the address of the clock carried in the first synchronization message is the address of the primary clock, and the address of the clock carried in the second synchronization message is the address of the backup clock; or, the address of the clock carried in the first synchronization message is the address of the backup clock, and the address of the clock carried in the second synchronization message is the address of the primary clock.

[0014] In a possible design, determining the synchronization message to be forwarded from the first synchronization message and the second synchronization message includes: determining the synchronization message to be forwarded in the first synchronization message and the second synchronization message according to a pre-configured filtering template; where the filtering template includes the information of the primary clock and / or the information of the backup clock.

[0015] That is to say, a filtering template can be pre-configured in the core network device, and some information of the primary clock and / or the information of the backup clock can be set in the template. When synchronization messages of two clocks are received, the information of the clocks carried in the synchronization messages can be compared with the information of the clocks in the filtering template to determine the message for the primary clock and the message for the backup clock in the two synchronization messages.

[0016] In a possible design, the information of the primary clock includes at least one of the source address of the primary clock or the prefix of Internet Protocol Version 6 (IPv6), and the information of the backup clock includes at least one of the destination address of the clock or the prefix of IPv6.

[0017] That is, the address or the prefix of IPv6 of the received synchronization message can be compared with the address or the prefix of IPv6 in the filtering template to determine the message for the primary clock and the message for the backup clock.

[0018] In a possible design, determining the synchronization message to be forwarded from the first synchronization message and the second synchronization message includes: when the time interval between receiving the second synchronization message and receiving the first first synchronization message is a first time period, and the first time period is greater than or equal to a preset time period, determining the first synchronization message as the synchronization message to be forwarded.

[0019] It can be understood that a timer can be maintained in the UPF. Considering that the synchronization messages of the backup clock triggered by mistake are sporadic, therefore, within a period of time after the UPF receives the synchronization message sent by the master clock, the UPF will not receive the synchronization messages sent by other clocks. Therefore, the UPF can introduce a timer dedicated to maintaining the services related to the master clock. Once the UPF receives the first TSN timing message of a node in a certain TSN domain, the timer is started. If the UPF does not receive the TSN messages sent by other nodes within the preset time period, the UPF can consider that the first timing message is sent by the master clock. Correspondingly, the TSN messages sent by other nodes in the same TSN domain received outside the preset time period are considered as the TSN timing messages triggered by mistake, and the UPF performs filtering operations on the timing messages triggered by mistake.

[0020] In a possible design, before determining the synchronization message to be forwarded from the first synchronization message and the second synchronization message, the method further includes: sending the first synchronization message and the second synchronization message to the Access and Mobility Management Function (AMF) network element; receiving the first indication information from the AMF network element, where the first indication information indicates that the first synchronization message and the second synchronization message are legal.

[0021] This is because it is possible that the multiple synchronization messages received by the UPF are malicious attack messages. Therefore, before determining the synchronization message to be forwarded, it is necessary to first determine the legality of the first synchronization message and the second synchronization message.

[0022] In a second aspect, a timing method for coping with link anomalies is provided. The method is applied to an access network device or a chip in the access network device. The method includes: determining that the timing link on the master clock side in the Time-Sensitive Networking (TSN) domain is abnormal; sending a first request information to the TSN domain, where the first request information is used to indicate to replace the master clock of the TSN domain with a backup clock in the TSN domain.

[0023] Among them, the access network device can be a gNB in 5GS. That is to say, the gNB can determine whether the timing link of the primary clock in the TSN domain is abnormal. If it is determined to be abnormal, it can instruct the backup clock to replace the primary clock. Compared with the prior art where 5GS only forwards synchronization messages and does not participate in judging whether the link is abnormal or whether to enable the backup clock, in this application, the gNB in 5GS can be given the role of sensing and indicating the enabling of the backup clock, so that the disconnection problem of the 5G air interface can be solved more quickly and directly, and the risk of timing interruption in the TSN network can be reduced.

[0024] In a possible design, before determining that the timing link on the primary clock side in the Time-Sensitive Networking (TSN) domain is abnormal, the method further includes: receiving first capability information from a first terminal device and second capability information from a second terminal device. The first capability information indicates that a first TSN node connected to the first terminal device has the ability of synchronous timing, and the first TSN node is the primary clock. The second capability information indicates that a second TSN node connected to the second terminal device has the ability of timing, and the second TSN node is the backup clock.

[0025] Among them, the reporting of the capability information by the terminal device can be implemented during the process of establishing or updating the PDU session between the first terminal device and the second terminal device and the access network device. That is, the first terminal device and the second terminal device can send a capability indication to the access network device, and the capability information is included in the capability indication. In this way, the access network device can judge whether the link is abnormal according to the capability information during the subsequent forwarding process of the synchronization message.

[0026] In a possible design, determining that the timing link on the primary clock side in the TSN domain is abnormal includes: if the access network device does not receive a synchronization message from the first terminal device within a preset time period, the access network device determines that the timing link on the primary clock side is abnormal.

[0027] That is to say, a timer can be maintained in the gNB. If the gNB determines that it has not received a synchronization message from the first terminal device within the preset time period of the timer, the gNB can consider that the timing link on the primary clock side is abnormal.

[0028] In a possible design, determining that the timing link on the primary clock side in the TSN domain is abnormal includes: analyzing the factors affecting the signal of the first terminal device through an Artificial Intelligence (AI) module; when the analysis result is that the synchronization message from the first terminal device cannot be received within a preset future time period, determining that the timing link on the primary clock side in the TSN domain is abnormal.

[0029] Exemplarily, the gNB can analyze parameters such as weather forecasts and traffic flows through the AI module, predict factors affecting the UE1 receiving channel such as the air interface channel quality, and determine whether a synchronization message from the first terminal device can be received within a preset future time period. If it is determined that the synchronization message from the first terminal device cannot be received within the preset future time period, the gNB determines that the timing link on the primary clock side is abnormal.

[0030] In a possible design, determining that the timing link on the primary clock side in the Time-Sensitive Networking (TSN) domain is abnormal includes: when receiving second request information from the first terminal device, where the second request information indicates a replacement of the primary clock, determining that the timing link on the primary clock side in the TSN domain is abnormal.

[0031] In this design, the first terminal device can determine whether the primary clock needs to be replaced. If it is determined that replacement is needed, the first terminal device can send a second request message to the gNB indicating the replacement of the primary clock, and the gNB can determine that the timing link on the primary clock side is abnormal based on the second request message. That is to say, the gNB is passively notified of the link abnormality of the primary clock.

[0032] In a possible design, determining that the timing link on the primary clock side in the Time-Sensitive Networking (TSN) domain is abnormal includes: receiving third request information from the second terminal device, where the third request information indicates a replacement of the primary clock; when the third request information is legal, determining that the timing link on the primary clock side in the TSN domain is abnormal.

[0033] In this design, the second terminal device can determine whether the primary clock needs to be replaced. If it is determined that replacement is needed, the second terminal device can send a third request message to the gNB indicating the replacement of the primary clock, and the gNB can determine that the timing link on the primary clock side is abnormal based on the third request message. That is to say, the gNB is passively notified of the link abnormality of the primary clock. Among them, in this design, to avoid the dual-clock phenomenon, when the gNB receives the third request message, it can first determine the legality of the third request message. If it is not an information of malicious attack and the gNB has not received the synchronization message of the primary clock within a certain time period, then the gNB can consider the third request message legal and enable the backup clock.

[0034] In a possible design, sending the first request information to the TSN domain includes: sending the first request information to the second terminal device in the TSN domain. That is, when the gNB determines that the backup clock needs to be enabled, it can send a request to enable the backup clock to the second terminal device on the backup clock side.

[0035] It can be understood that the second terminal device in the second aspect can also be replaced by a server.

[0036] In a third aspect, a timing method for coping with link anomalies is provided. This method is applied to a core network device or a chip in a core network device, and the method includes: determining that the timing link on the master clock side in the Time-Sensitive Networking (TSN) domain is abnormal; sending a first request message to the TSN domain, where the first request message is used to indicate replacing the master clock in the TSN domain with a backup clock in the TSN domain. The core network device can be a User Plane Function (UPF), etc.

[0037] Thus, in the embodiments of this application, when the timing link on the master clock side is abnormal, the role of perceiving and indicating the enabling of the backup clock can be assigned to the UPF in 5G System (5GS), so that the disconnection problem of the 5G air interface can be solved more quickly and directly, and the risk of timing interruption in the TSN network can be reduced.

[0038] In a possible design, before determining that the timing link on the master clock side in the Time-Sensitive Networking (TSN) domain is abnormal, the method further includes: receiving first capability information from a first terminal device and second capability information from a second terminal device. The first capability information indicates that a first Time-Sensitive Networking (TSN) node connected to the first terminal device has the ability of synchronous timing, and the first TSN node is the master clock. The second capability information indicates that a second TSN node connected to the second terminal device has the ability of timing, and the second TSN node is the backup clock.

[0039] Among them, the reporting of the capability information by the terminal device can be implemented during the process of establishing or updating a PDU session between the first terminal device and the second terminal device and the core network device. That is, the first terminal device and the second terminal device can send a capability indication to the core network device, and the capability indication includes the capability information. In this way, the core network device can determine whether the link is abnormal according to the capability information during the subsequent forwarding process of the synchronization message.

[0040] In a possible design, determining that the timing link on the master clock side in the Time-Sensitive Networking (TSN) domain is abnormal includes: if the core network device does not receive a synchronization message from the first terminal device within a preset time period, the core network device determines that the timing link on the master clock side is abnormal.

[0041] That is, a timer can be maintained in the UPF. When the UPF determines that it does not receive a synchronization message from UE1 within the preset time period during which the timer is counting, the UPF can consider that the timing link on the master clock side is abnormal.

[0042] In a possible design, determining that the timing link on the master clock side in the Time-Sensitive Networking (TSN) domain is abnormal includes: receiving a second request message from the first terminal device or the second terminal device, where the second request message indicates replacing the master clock; when the second request message is legal, determining that the timing link on the master clock side in the TSN domain is abnormal. Similar to the gNB, determining that the second request message is legal is to avoid the phenomenon of dual clocks.

[0043] In a possible design, sending the first request message to the TSN domain includes: sending the first request message to a second terminal device in the TSN domain. That is, when the UPF determines that the link on the primary clock side is abnormal, it can send a request message to enable the backup clock to the terminal device on the backup clock side.

[0044] It can be understood that the second terminal device in the third party can also be a server.

[0045] In a fourth aspect, a timing method for dealing with link anomalies is provided. The method is applied to a terminal device and includes: determining that the timing link on the primary clock side in the Time-Sensitive Networking (TSN) domain is abnormal; sending a first request message to a core network device, where the first request message is used to indicate replacing the primary clock in the TSN domain with a backup clock in the TSN domain.

[0046] Thus, in the embodiments of the present application, when the timing link on the primary clock side is abnormal, the terminal device on the primary clock side or the terminal device on the backup clock side in 5GS can be given the role of sensing and indicating the enabling of the backup clock, so as to more quickly and directly solve the disconnection problem of the 5G air interface and reduce the risk of timing interruption in the TSN network.

[0047] In a possible design, before determining that the timing link on the primary clock side in the TSN domain is abnormal, a first capability information is sent to the core network device. The first capability information is used to indicate that the first TSN node connected to the terminal device has the synchronous timing capability and the first TSN node is the primary clock. In this way, when the terminal device determines that the link on the primary clock side is abnormal, the core network device can determine to enable the backup based on the reported capability information and the indication from the terminal device to enable the backup clock.

[0048] In a possible design, determining that the timing link on the primary clock side in the TSN domain is abnormal includes: when no synchronization message from the primary clock is received within a preset time period, determining that the timing link on the primary clock side is abnormal.

[0049] When applied to the terminal device on the primary clock side, if a timer is maintained in the terminal device on the primary clock side, once the terminal device on the primary clock side determines that no synchronization message from the TSN node on the primary clock side is received within the preset time period during the timer timing, the terminal device on the primary clock side considers that the timing link on the primary clock side is abnormal.

[0050] In a possible design, before determining that the timing link on the primary clock side in the TSN domain is abnormal, the method further includes: sending a second capability information to the core network device, where the second capability information indicates that the second TSN node connected to the terminal device has the timing capability and the second TSN node is the backup clock.

[0051] In a possible design, determining that the timing link on the master clock side in the Time-Sensitive Networking (TSN) domain is abnormal includes: when no synchronization message from the master clock of the access network device is received within a preset time period, determining that the timing link on the master clock side is abnormal.

[0052] That is, when applied to the terminal device on the backup clock side, the terminal device on the backup clock side can also maintain a timer. Since the terminal device on the backup clock side needs to periodically receive the sleep instruction of the master clock sent by the gNB and send the sleep instruction to the backup clock so that the backup clock is not enabled, once the terminal device on the backup clock side does not receive the sleep instruction sent by the gNB within the preset time period of the timer timing, the terminal device on the backup clock side determines that the timing link on the master clock side is abnormal.

[0053] It can be understood that the second terminal device in the fourth aspect can also be a server.

[0054] In a fifth aspect, a core network device is provided, including: a transceiver for receiving a first synchronization message from a first terminal device; the transceiver is further configured to receive a second synchronization message from a second terminal device or a server; a processor for determining a synchronization message to be forwarded from the first synchronization message and the second synchronization message if the TSN domains to which the first synchronization message and the second synchronization message belong are the same.

[0055] In a possible design, that the TSN domains to which the first synchronization message and the second synchronization message belong are the same includes: the Virtual Local Area Network (VLAN) identifier (VID) carried in the first synchronization message is the same as the VID carried in the second synchronization message; or, the sequence number of the TSN domain carried in the header of the first synchronization message is the same as the sequence number of the TSN domain carried in the second synchronization message; or, the address of the first terminal device carried in the first synchronization message and the address of the second terminal device or the server carried in the second synchronization message both belong to the TSN domain.

[0056] In a possible design, the processor is configured to: determine the synchronization message to be forwarded in the first synchronization message and the second synchronization message according to the address of the clock carried in the first synchronization message and the address of the clock carried in the second synchronization message.

[0057] In a possible design, the address of the clock carried in the first synchronization message is the address of the master clock, and the address of the clock carried in the second synchronization message is the address of the backup clock; or, the address of the clock carried in the first synchronization message is the address of the backup clock, and the address of the clock carried in the second synchronization message is the address of the master clock.

[0058] In a possible design, the processor is configured to: determine the synchronization packets to be forwarded in the first synchronization packet and the second synchronization packet according to a pre-configured filtering template; wherein, the filtering template includes information of the primary clock and / or information of the backup clock.

[0059] In a possible design, the information of the primary clock includes at least one of the source address of the primary clock or the prefix of Internet Protocol Version 6 (IPv6), and the information of the backup clock includes at least one of the destination address of the clock or the prefix of IPv6.

[0060] In a possible design, the processor is configured to: when the time interval between receiving the second synchronization packet and receiving the first synchronization packet is a first time period, and the first time period is greater than or equal to a preset time period, determine that the first synchronization packet is the synchronization packet to be forwarded.

[0061] In a possible design, the transceiver is further configured to: send the first synchronization packet and the second synchronization packet to an Access and Mobility Management Function (AMF) network element; receive first indication information from the AMF network element, where the first indication information indicates that the first synchronization packet and the second synchronization packet are legal.

[0062] In a sixth aspect, an access network device is provided, including a processor and a transceiver. The processor is configured to determine that the timing link on the primary clock side in a Time-Sensitive Networking (TSN) domain is abnormal; the transceiver is configured to send first request information to the TSN domain, where the first request information is used to indicate replacing the primary clock in the TSN domain with a backup clock in the TSN domain.

[0063] In a possible design, the transceiver is further configured to receive first capability information from a first terminal device and second capability information from a second terminal device. The first capability information indicates that a first TSN node connected to the first terminal device has synchronization timing capability, and the first TSN node is the primary clock. The second capability information indicates that a second TSN node connected to the second terminal device has timing capability, and the second TSN node is the backup clock.

[0064] In a possible design, the processor is configured to: if the access network device does not receive a synchronization packet from the first terminal device within a preset time period, determine that the timing link on the primary clock side is abnormal.

[0065] In a possible design, the processor is configured to: analyze factors affecting the signal of the first terminal device through an Artificial Intelligence (AI) module; when the analysis result is that a synchronization packet from the first terminal device cannot be received within a preset future time period, determine that the timing link on the primary clock side in the TSN domain is abnormal.

[0066] In a possible design, when the transceiver is used to receive second request information from a first terminal device, and the second request information indicates a replacement of the master clock, the processor is used to determine that the timing link on the master clock side in the TSN domain is abnormal.

[0067] In a possible design, when the transceiver is used to receive third request information from a second terminal device, and the third request information indicates a replacement of the master clock; when the third request information is legal, the processor is used to determine that the timing link on the master clock side in the TSN domain is abnormal.

[0068] In a possible design, the transceiver is used to send first request information to a second terminal device in the TSN domain.

[0069] In a seventh aspect, a core network device is provided, including a processor, configured to determine that the timing link on the master clock side in a Time-Sensitive Networking (TSN) domain is abnormal; and a transceiver, configured to send first request information to the TSN domain, where the first request information is used to indicate replacing the master clock of the TSN domain with a backup clock in the TSN domain.

[0070] In a possible design, the transceiver is configured to receive first capability information from a first terminal device and second capability information from a second terminal device, where the first capability information indicates that a first Time-Sensitive Networking (TSN) node connected to the first terminal device has synchronous timing capability and the first TSN node is the master clock, and the second capability information indicates that a second TSN node connected to the second terminal device has timing capability and the second TSN node is the backup clock.

[0071] In a possible design, if the transceiver does not receive a synchronization message from the first terminal device within a preset time period, the processor is used to determine that the timing link on the master clock side is abnormal.

[0072] In a possible design, when the transceiver is used to receive second request information from the first terminal device or the second terminal device, and the second request information indicates a replacement of the master clock; when the second request information is legal, the processor is used to determine that the timing link on the master clock side in the TSN domain is abnormal.

[0073] In a possible design, the transceiver is used to send first request information to a second terminal device in the TSN domain.

[0074] In an eighth aspect, a terminal device is provided, including a processor, configured to determine that the timing link on the master clock side in a Time-Sensitive Networking (TSN) domain is abnormal; and a transceiver, configured to send first request information to a core network device, where the first request information is used to indicate replacing the master clock of the TSN domain with a backup clock in the TSN domain.

[0075] In a possible design, a transceiver is configured to send first capability information to a core network device before determining that a timing link on the master clock side in a Time-Sensitive Networking (TSN) domain is abnormal. The first capability information is used to indicate that a first TSN node connected to a terminal device has synchronous timing capability, and the first TSN node is the master clock.

[0076] In a possible design, a processor is configured to determine that a timing link on the master clock side is abnormal when no synchronization message is received from the master clock within a preset time period.

[0077] In a possible design, a transceiver is configured to send second capability information to a core network device. The second capability information indicates that a second TSN node connected to a terminal device has timing capability, and the second TSN node is a backup clock.

[0078] In a possible design, a processor is configured to determine that a timing link on the master clock side is abnormal when the transceiver does not receive a synchronization message from the master clock of an access network device within a preset time period.

[0079] In a ninth aspect, a communication device is provided for performing the method described in the first aspect and any possible design of the first aspect.

[0080] In a tenth aspect, a communication chip is provided, characterized in that it is configured to perform the method described in the first aspect and any possible design of the first aspect.

[0081] In an eleventh aspect, a computer-readable storage medium is provided, including computer instructions that, when run on an electronic device, cause the electronic device to perform the method described in the first aspect and any possible design of the first aspect.

[0082] In a twelfth aspect, a computer program product is provided that, when run on a computer, causes the electronic device to perform the method described in the first aspect and any possible design of the first aspect.

[0083] In a thirteenth aspect, a communication device is provided for performing the method described in the first aspect and any possible design of the first aspect.

[0084] In a fourteenth aspect, a communication chip is provided, characterized in that it is configured to perform the method described in the second aspect and any possible design of the first aspect, and / or the method described in the second aspect and any possible design of the second aspect, and / or the method described in the third aspect and any possible design of the third aspect, and / or the method described in the fourth aspect and any possible design of the fourth aspect.

[0085] In a fifteenth aspect, there is provided a computer-readable storage medium including computer instructions which, when running on an electronic device, cause the electronic device to execute the methods described in the first aspect and any possible design of the first aspect, and / or the methods described in the second aspect and any possible design of the second aspect, and / or the methods described in the third aspect and any possible design of the third aspect, and / or the methods described in the fourth aspect and any possible design of the fourth aspect.

[0086] In a sixteenth aspect, there is provided a computer program product which, when running on a computer, causes the electronic device to execute the methods described in the first aspect and any possible design of the first aspect, and / or the methods described in the second aspect and any possible design of the second aspect, and / or the methods described in the third aspect and any possible design of the third aspect, and / or the methods described in the fourth aspect and any possible design of the fourth aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0087] Figure 1 FIG. is a schematic diagram of the operation of a TC provided by an embodiment of the present application;

[0088] Figure 2 FIG. is a schematic diagram of 5GS as a bridging device of TSN provided by an embodiment of the present application;

[0089] Figure 3 FIG. is a schematic diagram of the downlink timing synchronization scenario of 5GS as TSN provided by an embodiment of the present application;

[0090] Figure 4 FIG. is a schematic diagram of the uplink timing synchronization scenario of 5GS as TSN provided by an embodiment of the present application;

[0091] Figure 5 FIG. is a schematic diagram of the VLAN data frame structure provided by an embodiment of the present application;

[0092] Figure 6 FIG. is a schematic diagram of the TSN uplink synchronization process of 5GS for TC provided by an embodiment of the present application;

[0093] Figure 7 FIG. is a schematic diagram of the TSN uplink synchronization process of 5GS for TC provided by an embodiment of the present application;

[0094] Figure 8 FIG. is a schematic diagram of the network topology where the primary clock and the backup clock are located provided by an embodiment of the present application;

[0095] Figure 9 FIG. is a schematic diagram of the working principle of the backup clock provided by an embodiment of the present application;

[0096] Figure 10 A schematic diagram of a network architecture provided by an embodiment of the present application;

[0097] Figure 11 A schematic diagram of a combination of nodes where a primary clock and a backup clock are located provided by an embodiment of the present application;

[0098] Figure 12 A schematic diagram of a combination of nodes where a primary clock and a backup clock are located provided by an embodiment of the present application;

[0099] Figure 13 A schematic diagram of a combination of nodes where a primary clock and a backup clock are located provided by an embodiment of the present application;

[0100] Figure 14 A schematic diagram of a timing method flow for dealing with link anomalies provided by an embodiment of the present application;

[0101] Figure 15 A schematic diagram of the process in which a UPF determines a primary clock and a backup clock using a timer provided by an embodiment of the present application;

[0102] Figure 16 A schematic diagram of a timing method flow for dealing with link anomalies provided by an embodiment of the present application;

[0103] Figure 17 A schematic diagram of a timing method flow for dealing with link anomalies provided by an embodiment of the present application;

[0104] Figure 18 A schematic diagram of a timing method flow for dealing with link anomalies provided by an embodiment of the present application;

[0105] Figure 19 A schematic diagram of a timing method flow for dealing with link anomalies provided by an embodiment of the present application;

[0106] Figure 20 A schematic diagram of a timing method flow for dealing with link anomalies provided by an embodiment of the present application;

[0107] Figure 21 A schematic diagram of a timing method flow for dealing with link anomalies provided by an embodiment of the present application;

[0108] Figure 22 A schematic diagram of the structure of a core network device provided by an embodiment of the present application;

[0109] Figure 23 A schematic diagram of the structure of a core network device provided by an embodiment of the present application;

[0110] Figure 24 A schematic diagram of the structure of a core network device provided by an embodiment of the present application. Detailed implementation manners

[0111] For ease of understanding, some explanations of concepts related to the embodiments of the present application are given as examples for reference. As follows:

[0112] TSN domain: It refers to a TSN network with the same synchronous source clock (master clock). There is only one synchronous source clock within the same TSN domain, which sends timing information to the TSN terminals (slave clocks) within the TSN domain. The same TSN terminal may receive data from multiple TSN domains, and the TSN terminal distinguishes the domain to which the TSN data packet belongs by reading the TSN domain ID (domain Identity) in the TSN data packet.

[0113] TSN time synchronization accuracy:

[0114] It refers to the time offset (time difference) between two synchronized clocks at both ends of the TSN domain. In order to achieve the synchronization of the two clocks, the master clock at one end of the TSN domain needs to send a synchronization message to the slave clock at the other end of the TSN domain. The synchronization message contains the master clock time information when the master clock sends the message. 5GS can act as a bridging role (transparent clock) to deliver the synchronization message to the slave clock, and at the same time inform the slave clock of the time delay of the message within 5GS. The slave clock can calculate the current corresponding master clock time information by reading the time information in the message and the delay information of the message transmitted on the link, and complete the synchronization with the master clock. Among them, the accuracy error of the delay information reported by 5GS will affect the TSN time synchronization accuracy.

[0115] Next, the time synchronization in TSN and how 5GS supports TSN will be introduced respectively.

[0116] Time synchronization in TSN:

[0117] In order to support time-based control, TSN devices need to maintain precise synchronization. Currently, the Precision Time Protocol (PTP) (or the Institute of Electrical and Electronics Engineers (IEEE) 1588 protocol) is usually used in TSN to achieve precise time synchronization between TSN devices. The timing signaling used for synchronization between PTP devices in PTP is usually also called PTP message / PTP packet. Therefore, the data transmitted in TSN can be divided into two categories: PTP messages for timing, and data packets related to services (TSN data).

[0118] For time synchronization, a basic type of clock node is defined in PTP: the transparent clock TC. The TC does not need to synchronize time with other devices. The TC has multiple clock ports and forwards PTP messages / PTP packets (carrying the correctionField field) between these ports, correcting the forwarding delay of the PTP messages / PTP packets, but does not synchronize time from any of the ports. As Figure 1 shown, the first clock can forward the clock packet (PTP message / PTP packet) to the second clock through the TC, or can forward the TSN data to the second clock through the TC. When the clock packet passes through the TC, there will be a certain processing delay for the TC to forward the clock packet. The TC can add the residence time of the message / packet at this node to the correction value (correctionField) field of the clock packet when forwarding the clock packet. After receiving the clock packet, the TSN slave node synchronizes its own clock based on the time information therein and the correction value contained in the correctionField field.

[0119] Among them, the header structure of the PTP message can be as shown in Table 1:

[0120] Table 1

[0121]

[0122] 5GS supports TSN:

[0123] Figure 2 Shows a schematic diagram of 5GS as a bridging device of TSN. The service data packets of TSN can be sent upstream / downstream through 5GS. Figure 2 Only the user plane part of 5GS is shown, including user equipment (UE), radio access network (RAN), and user plane function (UPF) network elements. The device that communicates with the UE side in the user plane can be a TSN bridging device or a TSN end station, and a clock is configured in the end station. The device that communicates with the UPF side can be a device in the TSN system. On the other hand, in order for TSN to support the PTP protocol, 5GS needs to be adapted to the PTP protocol. The solution adopted by the 3rd generation partnership project (3GPP) is to regard 5GS as a transparent clock, as Figure 3As shown, for a downlink timing scenario, the PTP message sent by the TSN grand master clock (GM) (which can be located in a TSN server connected to the UPF, for example) can be forwarded by the 5GS to the TSN end station. At the boundary where the 5GS and the TSN are connected, a TSN adapter is required to process messages related to the PTP protocol or TSN service data packets. For example, Figure 3 the user-side TSN adapter (UE TSN translator, UE-TT) (or also known as the device-side TSN Translator, DS-TT) on the UE side and the network-side TSN adapter (network-side TSN translator, NW-TT) on the UPF side in Figure 3 are the corresponding adapters. The DS-TT / NW-TT can be a processing device connected to the UE / UPF or a logical function of the UE / UPF.

[0124] When the transparent clock forwards the PTP message, it needs to correct the dwell time of the message at this node to the correctionField field. In order for the 5GS to obtain the dwell time of the PTP message / PTP packet within the 5GS, it is necessary to ensure the 5G clock synchronization between the UPF and the UE. To ensure the 5G clock synchronization between the UE and the UPF, it is necessary for the UE and the base station (gNodeB, gNB) to achieve clock synchronization, and for the UPF and the gNB to achieve clock synchronization through the PTP protocol. The clock synchronization between the UE and the UPF is ensured by both of them obtaining time from the same clock source (as Figure 3 shown, the gNB and the 5G GM achieve clock synchronization. Further, the UE and the gNB achieve clock synchronization through the air interface synchronization scheme, and the UPF and the gNB achieve clock synchronization through the PTP protocol).

[0125] After all network elements within the 5GS are time synchronized, when the PTP message / PTP packet enters from the UPF side, the NW-TT will stamp the 5G timestamp tin on the PTP message / PTP packet. The 5G time when the DS-TT on the UE side sends out the PTP message / PTP packet is tout. Then the DS-TT adds (tout - tin) to the correctionField field of this PTP message.

[0126] The 5GS supports the uplink timing process:

[0127] The TSN timing scenario can be that the master clock is located outside the UPF and synchronizes the TSN slave nodes connected to the UE side (which can be called the downlink timing scenario), or the master clock is located on the TSN master node connected to the UE side and synchronizes the TSN slave nodes located outside the UPF or the TSN slave nodes connected to other UEs (which can be called the uplink timing scenario). Exemplarily, an uplink timing scenario is as follows Figure 4 shown. The TSN timing message enters the 5GS from UE1, passes through the gNB, UPF, and gNB, and finally is transmitted by UE2 to another TSN terminal station. Similar to Figure 3 the downlink scenario in, it is also necessary to timestamp the TSN timing message at the entrance and exit of the 5GS in the uplink scenario. The main difference is that the entrance and exit of the uplink scenario are UE1 and UE2 respectively, while the entrance and exit of the downlink scenario are UPF and UE respectively.

[0128] Overview of VLAN standard:

[0129] The transmission of some data packets within the TSN needs to comply with the virtual local area network (VLAN) standard. VLAN is a communication technology that logically divides a physical local area network (LAN) into multiple broadcast domains. As Figure 5 shown in the schematic diagram of the VLAN data frame structure. The fields of the data frame can include the destination address, source address, 802.1Q Tag, length / type, data, and frame check sequence (FCS). Among them, the 802.1Q Tag is the official standard of the VLAN. The 802.1Q Tag can include the tag protocol identifier (TPID), priority (PRI), canonical format indicator (CFI), and VID (VLAN ID). Among them, the VID field is used to indicate the VLAN (i.e., the TSN domain ID) to which the data frame belongs, that is, the data frame can only be transmitted within the VLAN to which it belongs. The VLAN ID field is 12 bits in total, and the value range is: 0 to 4095, which can represent 4096 different values. Among them, 0 and 4095 are invalid values, so the common VLAN ID configuration range is 1 to 4094.

[0130] TSN uplink time synchronization process:

[0131] A typical TSN uplink synchronization process with the 5GS as the TC is as Figure 6As shown, this process describes the scenario where the UE provides clock timing for the UPF side. Among them, TSN Node 0 is the clock (master clock) on the UE side, and TSN Node 2 is the clock (slave clock) on the UPF side:

[0132] Step 1: UE1 establishes a protocol data unit session (PDU session) with 5GS, including UE1 passing its own (media access control, MAC) address or port information to the UPF, authentication management function (AMF) network element / session management function (SMF) network element / policy control function (PCF) network element, etc., or passing the MAC address or port information to the application server (AS) and TSN application function (AF) network element, etc. This step is equivalent to establishing a channel among core network elements such as UE1, gNB, and UPF, facilitating the signaling or data interaction among these network elements in subsequent steps.

[0133] Step 2: Determine the best clock in the TSN domain, for example, determine the best clock through the best master clock algorithm (BMCA).

[0134] Step 3: Initiate a PDU session update at both sides of the interface (DS-TT1 and NW-TT) of 5GS.

[0135] Step 4: TSN Node 0 sends a TSN-format synchronization message (including the TSN master clock timestamp, correction field, and rateRatio field, rateRatio = GM clock frequency / local clock frequency) to UE1 in 5GS.

[0136] Step 5: UE1 can convert the received TSN-format synchronization message into a format that can be transmitted within 5GS through DS-TT1. Specifically, it includes adding the delay between TSN Node 0 and DS-TT1 in the correction field, updating the rateRatio, and adding the ingress 5GS timestamp. The ingress 5GS timestamp can be understood as the time when UE1 receives the TSN-format synchronization message.

[0137] Step 6: UE1 sends the converted synchronization message in Step 5 to the UPF. The synchronization message sent to the UPF includes the TSN master clock timestamp, correction field, rateRatio field, and the ingress 5GS timestamp.

[0138] Step 7: The UPF can convert the received 5GS - formatted synchronization message in Step 6 into a TSN - formatted synchronization message for the TSN domain through NW - TT. Specifically, it updates the correction field to the original value of the correction field in Step 6+(egress 5GS time - ingress 5G timestamp)*rateRatio, and discards the ingress 5GS timestamp. The egress 5GS time can be understood as the time when the UPF sends the TSN - formatted synchronization message.

[0139] Step 8: NW - TT sends the TSN - formatted synchronization message converted in Step 7 to the TSN Node2 for the TSNNode2 to perform time synchronization.

[0140] Another typical TSN uplink synchronization process with 5GS as the TC is as Figure 7 shown. This process describes the scenario where UE provides time - of - day for the clock of other UEs. Among them, TSN Node0 is the master clock connected to the UE1 side, TSN Node2 is the backup clock of the other UE side, and TSN Node3 is the slave clock connected to the UE3 side:

[0141] Steps 1 to 6: Similar to the Figure 6 shown TSN uplink synchronization process.

[0142] Steps 6.a / 6.b: Different from the first typical TSN uplink synchronization process, Figure 7 in this process, after the UPF receives the TSN - formatted synchronization message, it does not send the TSN - formatted synchronization message to NW - TT. Instead, it directly performs local conversion, identifies the address to which the TSN - formatted synchronization message needs to be forwarded, and then returns the TSN - formatted synchronization message to the gNB according to this address, instructing the gNB to send the TSN - formatted synchronization message to the UE2 corresponding to the address to be forwarded.

[0143] Steps 7 to 8: Similar to Steps 7 and 8 of the Figure 6 shown TSN uplink synchronization process, with the difference that the execution entity changes from NW - TT to DS - TT2, and the receiver of the TSN - formatted synchronization message becomes UE2.

[0144] PTP time - of - day message synchronization period requirement:

[0145] Since the master clock and each slave clock in the TSN clock domain will drift, it is necessary to perform uplink time synchronization periodically. Generally, the shortest period is 32 ms.

[0146] Currently, the mechanism of backup clock is mentioned in both the IEEE P802.1AS standard and the mainstream industrial Ethernet standard Profinet (for example, redundant hot standby grandmaster). Figure 8 In (a) is the schematic diagram of the network topology where the master clock and the backup clock (backup master clock) are located. Figure 8 In (b) is the schematic diagram of the abnormal master clock link. Figure 8 It can also be understood as the schematic diagram of the working principle of the backup clock as shown in Figure 9 That is, when the original master clock (clock source) works normally, the TSN terminal station where the original master clock is located sends a synchronization message stream to the entire TSN topology network (other TSN terminals), and the "target clock" corresponding to the backup clock receives the periodic original master clock signal as a sleep instruction. Once the original master clock fails (due to reasons such as the failure of the original master clock or the failure of the link on the original master clock side), the "target clock" does not receive continuous time synchronization messages, and then triggers the activation of the backup clock. The backup clock starts to take over the role of the original master clock and sends a synchronization message stream to the entire TSN topology network.

[0147] As mentioned above, when the backup clock starts is determined by the TSN terminal station of the backup clock, but the TSN terminal station of the backup clock cannot determine whether it is a problem with the uplink air interface link on the master clock side or the downlink air interface on the backup clock side. Once the uplink air interface link of the master clock is normal but the downlink air interface of the backup clock has an abnormality (such as intermittent), the backup clock will wrongly think that there is a fault on the master clock side, wrongly activate the backup clock and upload synchronization messages to the UPF, thus affecting the synchronization accuracy of the slave clock and increasing the air interface overhead of 5GS. In addition, currently, the method of electing the master clock and the backup clock by the TSN topology itself has a slow convergence rate and a complex algorithm, and is suitable for a stable topology network built by wired connections. When 5GS is introduced as a bridging device to transmit time synchronization signals for the topology network, due to the instability of the 5G air interface compared with wired connections (link disconnection problems), it is easy to trigger multiple BMCA processes. Therefore, the BMCA process with a slow convergence rate will cause adverse consequences such as delay of clock synchronization messages and deterioration of synchronization accuracy.

[0148] Therefore, the embodiment of the present application provides a time synchronization method for coping with link abnormalities, which can be applied to the process of starting the backup clock to replace the master clock in the TSN.

[0149] In this application, to solve the above problems, when the link on the primary clock side is referred to as the TSN timing link, in one implementation, if the backup clock in the same TSN domain automatically starts without receiving the sleep instruction from the primary clock, when a core network device in 5GS, such as a UPF, receives both the synchronization message from the primary clock and the synchronization message from the backup clock, the UPF can determine the synchronization message to be forwarded and the synchronization message to be filtered from the two synchronization messages, so as to avoid the "dual clock" phenomenon, that is, it can avoid submitting the two messages to the TSN server or the air interface at the same time, saving signaling interaction and air interface overhead, and improving the synchronization accuracy of the slave clock. In addition, in the prior art, the BMCA algorithm selects the primary clock and the backup clock before starting to send the synchronization message stream, and the selection method converges slowly. However, in this application, by enhancing the function of the UPF, during the process of sending the synchronization message stream, it can be determined which synchronization message is to be forwarded and which synchronization message is to be filtered from the synchronization messages of the two clocks received in the same TSN domain, and the clock corresponding to the synchronization message to be forwarded is determined as the primary clock, and the clock corresponding to the synchronization message to be filtered is the backup clock. Therefore, compared with the method of determining the primary clock and the backup clock by the BMCA algorithm with relatively slow convergence, during the process of forwarding the synchronization message stream, the enhanced UPF can directly determine the primary clock and the backup clock according to the synchronization messages of the two clocks received. Therefore, in this application, by the enhanced UPF, the convergence time of selecting the primary clock and the backup clock can be shortened, and the synchronization efficiency can be improved.

[0150] In another implementation, the network element in 5GS (such as the terminal device on the primary clock side, the terminal device on the backup clock side, the base station or the core network device) can determine whether the link on the primary clock side is abnormal. If it is determined to be abnormal, the network element in 5GS can instruct the backup clock to start. On the one hand, the disconnection problem of the 5G air interface can be solved, that is, using the network element in 5G to sense the 5G air interface problem can be faster and more efficient, reducing the risk of timing interruption in TSN, determining the timing of enabling the backup clock in a timely manner, and enabling 5GS to reasonably allocate uplink resources to ensure that the time for enabling the backup clock is less than the synchronization period. On the other hand, compared with the method of selecting the primary clock and the backup clock by the BMCA algorithm with relatively slow convergence before the synchronization message stream starts to be sent, in this application, during the process of starting to send the synchronization message stream, the network element in 5GS can determine whether the link on the primary clock side is abnormal. When it is determined that the link on the primary clock side is abnormal, it can be determined in a timely manner that the primary clock needs to be replaced to start the backup clock. Therefore, in this application, by endowing the network element in 5GS with the method of selecting the backup clock, the convergence time of selecting the backup clock can be made faster, and the synchronization efficiency can be improved.

[0151] Such as Figure 10As shown in the figure, the network architecture of the present application may include a first TSN node where the master clock is located, a second TSN node where the backup clock is located, and 5GS. 5GS may include terminal devices, access network devices, core network devices, etc. The access network device may be a next generation-radio access network (NG-RAN) device, such as a gNB. The core network devices may include UPF, AMF, SMF, etc.

[0152] There can be various different combinations of the nodes where the master clock and the backup clock are located. For example:

[0153] As Figure 11 shown in the figure, the first TSN node where the master clock is located may communicate with a first terminal device (such as UE1) in 5GS, and the second TSN node where the backup clock is located may communicate with a second terminal device (such as UE2) in 5GS. At this time, UE1 may include DS-TT1, UE2 may include DS-TT2, and both UE1 and UE2 may communicate with NG-RAN and core network devices (such as UPF) in 5GS.

[0154] As Figure 12 shown in the figure, the first TSN node where the master clock is located may communicate with UE1 in 5GS, and the second TSN node where the backup clock is located communicates with a server in the TSN system, and this server may also communicate with UPF. At this time, UE1 may include DS-TT, and UPF may include NW-TT.

[0155] As Figure 13 shown in the figure, the first TSN node where the master clock is located may communicate with a server in the TSN, and this server may communicate with UPF. The second TSN node where the backup clock is located may communicate with UE2, and UE2 includes DS-TT, and UPF may include NW-TT.

[0156] It should be noted that UE1 and UE2 may be terminal devices under the same gNB or terminal devices under different gNBs.

[0157] Among them, the terminal device in the embodiment of the present application may be a UE, a mobile station (MS), a mobile terminal (MT), etc., which refers to a device that provides voice and / or data connectivity to users.

[0158] The access network device refers to a radio access network (RAN) node (or device) that connects a terminal to a wireless network, and can also be called a base station.

[0159] The UPF network element is a functional network element of the user plane, mainly responsible for connecting to the external network, which includes the relevant functions of the serving gateway (SGW) and the public data network gateway (PDN-GW) of Long-Term Evolution (LTE), and is mainly responsible for the forwarding of packet data packets, the statistics of charging information, etc.

[0160] The AMF network element is responsible for the access management and mobility management of the terminal. In practical applications, it includes the mobility management function of the mobile management entity (MME) in LTE and adds the access management function.

[0161] The SMF network element is responsible for session management, such as the establishment, modification, release, etc. of sessions of terminal devices (UEs).

[0162] NW-TT / DS-TT: A TSN adapter connected to the UPF / UE, used to process messages related to the PTP protocol or TSN service data packets.

[0163] Applying the above network architecture, the embodiment of the present application provides a timing method for coping with link anomalies, which can be applied to, for example, Figure 11 the network architecture shown, and this method can be applied to core network devices or chips in core network devices. Taking the main clock on one UE side synchronizing the slave clock on another UE side with the core network device being the UPF as an example, as Figure 14 shown, this method may include:

[0164] Steps 151-155 are similar to Steps 1-5 in the synchronization process shown above. Figure 7 shown.

[0165] The embodiment of the present application mainly focuses on the operation process of the core network device (UPF) for multiple TSN synchronization messages. For different placement combinations of the main clock and the backup clock, the behavior of the core network device is the same (because whether the main clock and the backup clock are located on the UE or the TSN server outside the UPF, the timing message of the main clock and the second timing message generated by the mis-triggering of the backup clock will reach the UPF. Therefore, for the UPF, the specific operation behavior is to filter out the mis-triggered timing messages and forward the timing messages of the main clock at the same time). Therefore, the steps before the UPF receives the synchronization message can refer to Steps 1-5 above.

[0166] Step 156, the UPF receives a first synchronization message from the first terminal device.

[0167] The first terminal device may be Figure 11UE1 or UE2 in it. It should be noted that Figure 14 The figure shows a scenario where there is a primary clock (in Node0) on the link side of UE1, a slave clock (in Node3) on the link side of UE3, and another primary clock (in Node2) on the link side of UE2. Figure 14 What is exemplified in it is the first synchronization message sent by the primary clock on the UE1 side, that is Figure 14 In it, the first terminal device in step 156 is UE1.

[0168] The first synchronization message may carry the time information of the primary clock in the TSN domain, or may carry the time information of the backup clock in the TSN domain.

[0169] When the UPF receives the first synchronization message from the first terminal device, the prior art does not perform operations such as opening and reading the first synchronization message. In this application, it is necessary to read the TSN domain ID carried in the first synchronization message. If it is a synchronization message of the TSN domain that is currently performing time synchronization, subsequent processing will continue. If it is not a synchronization message of the TSN domain that is currently performing time synchronization, it will be ignored. In this way, it can prevent the UPF from accidentally filtering out the synchronization messages of other TSN domains and affecting the normal synchronization process of other TSN domains.

[0170] The entity that reads the TSN domain ID here can be the UPF, or the NW-TT connected to the UPF, and the NW-TT then reports the TSN domain ID to the UPF.

[0171] In some embodiments, there are various ways for the UPF to read the TSN domain ID. For example:

[0172] 1) The UPF reads the VID in the first synchronization message (reference can be made to the description in Figure 5 );

[0173] 2) The UPF reads the sequence number of the TSN domain carried in the message header of the first synchronization message: domainNumber (reference can be made to the description in Table 1);

[0174] 3) The UPF reads the address of the first terminal device carried in the first synchronization message. If each terminal device or server is bound to a TSN domain, then the UPF can determine the TSN domain to which the first synchronization message belongs through the address of the terminal device or server. This address can be a MAC address or an internet protocol (IP) address.

[0175] That is to say, the UPF can determine the TSN domain to which the first synchronization message belongs based on the VID, domainNumber, and the address of the first terminal device carried in the first synchronization message.

[0176] In some embodiments, when the UPF receives a TSN message, it needs to first read the source address and destination address carried in the TSN message (see the description in Figure 5 ), so as to determine whether the received TSN message is a timing synchronization message based on the number of the source address and destination address, because the TSN message may also be a TSN service message. Generally speaking, a message with one source address and multiple destination addresses is a timing synchronization message; a TSN message with one source address and one destination address is a service message. For example, the service message is a control signal sent by the TSN server to the TSN robotic arm terminal. That is to say, when the UPF receives the first synchronization message or the second synchronization message, it needs to first determine whether it is a synchronization message.

[0177] Step 157: The UPF receives a second synchronization message from the second terminal device.

[0178] If the above-mentioned first terminal device is UE1, the second terminal device may be UE2 (such as the example in Figure 14 ), or the above-mentioned first terminal device is UE2 and the second terminal device is UE1.

[0179] Similar to step 156, when the UPF receives the second synchronization message, it also needs to perform operations such as opening and reading on the second synchronization message, and read the TSN domain ID of the second synchronization message. The reading method can refer to the description in step 156 above.

[0180] Step 158: If the TSN domains to which the first synchronization message and the second synchronization message belong are the same, the UPF determines the synchronization message to be forwarded from the first synchronization message and the second synchronization message.

[0181] That is to say, if the UPF receives multiple synchronization messages within the same TSN domain, the UPF needs to filter out the synchronization messages caused by mis-triggered operations to ensure that each TSN node within each TSN domain will only receive the clock signal of one synchronization source clock.

[0182] In some embodiments, the implementation manner in which the TSN domains to which the first synchronization message and the second synchronization message belong are the same may include one of the following manners:

[0183] 1) The VID carried in the first synchronization message is the same as the VID carried in the second synchronization message;

[0184] 2) The domainNumber of the TSN field carried in the header of the first synchronization message is the same as the domainNumber of the TSN field carried in the second synchronization message;

[0185] 3) The address of the first terminal device carried in the first synchronization message and the address of the second terminal device carried in the second synchronization message both belong to the same TSN domain. The address can be a MAC address, an IP address, etc.

[0186] Exemplarily, the mapping relationship (or binding information) between the address of the UE and the TSN domain can be informed to the network device by the UE reporting its capabilities when establishing a connection with the network device (such as UPF). Similarly, if the synchronization message is sent by the server, the mapping relationship (or binding information) between the address of the server and the TSN domain can be informed to the network device by the server reporting its capabilities when establishing a connection with the network device.

[0187] In some embodiments, before determining the synchronization message to be forwarded from the first synchronization message and the second synchronization message, the UPF may send the first synchronization message and the second synchronization message to the AMF network element so that the AMF network element can authenticate the first synchronization message and the second synchronization message to determine whether the first synchronization message and the second synchronization message are legal. This is because the synchronization messages received by the UPF may be malicious attack messages.

[0188] If the AMF network element determines that it is legal, the UPF can receive the first indication information from the AMF network element, and the first indication information indicates that the first synchronization message and the second synchronization message are legal.

[0189] After determining that the first synchronization message and the second synchronization message are legal, in order to avoid the double-clock phenomenon, the UPF needs to determine the synchronization message to be forwarded and the synchronization message to be filtered from the first synchronization message and the second synchronization message.

[0190] In some embodiments, the UPF may determine the synchronization message to be forwarded in the first synchronization message and the second synchronization message according to the address of the clock carried in the first synchronization message and the address of the clock carried in the second synchronization message.

[0191] Exemplarily, when both the first synchronization message and the second synchronization message correspond to a source address and multiple destination addresses, the source address is the address of the primary clock or the backup primary clock, and the destination addresses are the addresses of the slave clocks to be time-synchronized. Since the primary clock, the backup clock, and the slave clocks can bind fixed IP / MAC addresses when initially accessing the 5GS and report the information of the primary clock and the backup clock and the bound address information to the core network elements (such as UPF / SMF / AMF, etc.), once the UPF receives synchronization messages with two different addresses in the same TSN domain, it can compare the IP / MAC addresses of the synchronization messages in the received TSN domain with the address of the primary clock and the address of the backup clock pre-stored in the TSN domain, so as to determine the synchronization message to be forwarded among the first synchronization message and the second synchronization message.

[0192] The result may be that the address of the clock carried by the first synchronization message is the address of the primary clock and the address of the clock carried by the second synchronization message is the address of the backup clock; or, the address of the clock carried by the first synchronization message is the address of the backup clock and the address of the clock carried by the second synchronization message is the address of the primary clock. That is to say, the synchronization message to be forwarded is the first synchronization message and the synchronization message to be filtered is the second synchronization message; or, the synchronization message to be forwarded is the second synchronization message and the synchronization message to be filtered is the first synchronization message.

[0193] In some embodiments, the UPF can determine the synchronization message to be forwarded among the first synchronization message and the second synchronization message according to a pre-configured filtering template; wherein, the filtering template includes the information of the primary clock and / or the information of the backup clock.

[0194] The information of the primary clock includes at least one of the source address of the primary clock or the prefix of the Internet Protocol Version 6 (IPv6), and the information of the backup clock includes at least one of the destination address of the clock or the prefix of the IPv6. Wherein, the source address and the destination address can be MAC addresses or IP addresses, etc.

[0195] Exemplarily, the SMF may set a filtering template based on the information of the primary clock reported by the primary clock when accessing the 5GS and / or the information of the backup clock reported by the backup clock when accessing the 5GS. Then, the SMF may configure the filtering template for the UPF so that the UPF can determine the synchronization packets to be forwarded according to the filtering template configured by the SMF. For example, when only the information of at least one primary clock is set in the filtering template, if the clock information carried in the first synchronization packet is the same as one of the information of at least one primary clock in the filtering template, then the UPF determines that the first synchronization packet is a synchronization packet of the primary clock and is the synchronization packet to be forwarded. Correspondingly, the second synchronization packet is the packet to be filtered. When only the information of at least one backup clock is set in the filtering template, if the clock information carried in the first synchronization packet is the same as one of the information of at least one primary clock in the filtering template, then the UPF determines that the first synchronization packet is a synchronization packet of the backup clock and is the synchronization packet to be filtered. Correspondingly, the first synchronization packet is the packet to be forwarded.

[0196] In some embodiments, when the time interval between receiving the second synchronization packet and the first first synchronization packet is a first time period, and the first time period is greater than or equal to a preset time period, it is determined that the first synchronization packet is the synchronization packet to be forwarded.

[0197] It can be understood that a timer can be maintained in the UPF. Considering that the synchronization packets of the mis-triggered backup clock are sporadic, after the primary clock sends a synchronization packet to the UPF, the UPF will not receive synchronization packets sent by other clocks within a period of time. Therefore, the UPF can introduce a timer dedicated to maintaining the services related to the primary clock. Once the UPF receives the first TSN grant message from a node in a certain TSN domain, the timer is started. If the UPF does not receive TSN messages sent by other nodes within the preset time period, the UPF may consider that the first grant message is sent by the primary clock. Correspondingly, the TSN messages sent by other nodes in the same TSN domain received outside the preset time period are considered as mis-triggered TSN grant messages, and the UPF performs filtering operations on the mis-triggered grant messages.

[0198] Thus, as Figure 15As shown, when the UPF first receives the first first synchronization message sent by the UE1, it starts the timer corresponding to the first synchronization message. During a preset time period, if the UPF continuously receives the first synchronization message at equal time intervals, the UPF considers that the first synchronization message is the synchronization message sent by the master clock. If the received synchronization message is outside the preset time period, for example, the second synchronization message is received outside the preset time period, the UPF considers that the second synchronization message is the message sent by the mis-triggered backup clock. If both the first synchronization message sent by the UE1 and the second synchronization message sent by the UE2 are received within the preset time period, the UPF can wait for the next timing cycle to continue to determine whether the first second synchronization message is outside the preset time period. If it is outside the preset time period, the UPF determines that the second synchronization message is the message to be filtered, and so on. Or, if both the first synchronization message sent by the UE1 and the second synchronization message sent by the UE2 are received within the preset time period, the UPF can optionally select one synchronization message as the synchronization message to be forwarded.

[0199] Among them, the timer can be placed in the UPF or in other core network elements, and other core network elements notify the UPF whether the timer times out.

[0200] It should be noted that within the preset time period for the UPF to confirm the synchronization message of the master clock, it is possible to receive multiple synchronization messages from different clock sources. The UPF can maintain dedicated timers for different clock sources respectively. As long as the synchronization message of any clock source first reaches the time threshold requirement of the timer (the UPF continuously receives the clock message of this clock source at equal intervals within a certain time threshold), the UPF determines that the synchronization message of this clock source is the synchronization message of the master clock.

[0201] In some embodiments, the UPF can identify the synchronization message, but does not distinguish whether it is the synchronization message of the master clock or the backup clock. Once the UPF receives the TSN timing messages from two Ethernet addresses / IP addresses / MAC addresses within the same TSN domain, the UPF itself decides which synchronization message to use as the synchronization message to be forwarded, and then always forwards the synchronization messages from this clock source, while filtering the synchronization messages from the other clock source.

[0202] It should be noted that if the UPF does not receive the message from the master clock within a timing period, but receives the message from the backup clock outside the timing period, in this case, it is not necessary to perform the filtering operation of the backup clock, and the synchronization message of the backup clock can be directly forwarded, that is, the backup clock can be directly enabled. For example, the first synchronization message sent by the above UE1 is the message of the master clock, and the second synchronization message sent by UE2 is the message of the backup clock. If the UPF does not receive the first synchronization message sent by UE1 within a timing period, but receives the second synchronization message sent by UE2 outside the timing period, the UPF can directly forward the second synchronization message, that is, directly enable the backup clock on the UE2 side.

[0203] In some embodiments, when the TSN link of the master clock is abnormal and the TSN node where the backup clock is located determines whether to enable the backup clock by itself, for the abnormal TSN link of the master clock, it includes one or a combination of the following faults:

[0204] 1) Internal fault or internal link fault of the TSN master clock;

[0205] 2) Link fault between the TSN master clock and the TSN node (the first TSN node);

[0206] 3) Internal fault of the TSN node;

[0207] 4) Link fault between the first TSN node and the DS-TT connected to UE1;

[0208] 5) Link fault between UE1 and DS-TT (generally, DS-TT is a module inside UE1, and here it can be understood as a circuit module related to DS-TT inside UE1);

[0209] 6) Internal fault of UE1;

[0210] 7) Radio link interruption between UE1 and gNB (NG-RAN);

[0211] 8) Link fault between gNB and UPF;

[0212] 9) Link fault between UPF and NW-TT;

[0213] 10) Wired link fault between NW-TT and the TSN system server;

[0214] 11) Link fault between the TSN system server and the master clock connected to itself;

[0215] Figure 11 The link abnormality range corresponding to the shown network architecture may include the above 1) - 8); Figure 12The link anomaly range corresponding to the shown network architecture may include the above 1) to 8); Figure 13 The link anomaly range corresponding to the shown network architecture may include the above 1), 9), 10) and 11).

[0216] Step 159, the UPF sends a first synchronization message to UE3, or the UPF sends a second synchronization message to UE3.

[0217] Figure 15 Only an example of sending the first synchronization message to UE3 is shown. In this way, Node3 on the link of UE3 can perform time synchronization according to the first synchronization message.

[0218] Through this embodiment, the present application can achieve that when the TSN timing link is abnormal, the core network device UPF can determine the synchronization message to be forwarded and the synchronization message to be filtered from the synchronization messages of the primary clock and the backup clock that is mis-triggered, so as to prevent the double clock phenomenon in the TSN domain, that is, to prevent the situation where the slave clock receives clock signals from two clock sources, and avoid introducing synchronization errors between different clocks and reducing the synchronization accuracy of TSN nodes.

[0219] In the prior art, the UPF does not consider filtering TSN messages in the case of double clocks. Moreover, in the prior art, the primary and backup clocks of each node are deduced by the BMCA algorithm (such as the above step two), rather than predefined. In this embodiment, it is considered that the SMF configures a template for the UPF to filter out the misoperated backup clock. At the same time, it is also considered to enhance the UPF's perception of TSN messages, so that it has the ability to sense and judge whether a TSN message belongs to a timing message and whether it is a synchronization message of the primary clock. Therefore, the embodiments of the present application are different from the prior art, and the gains brought can include:

[0220] 1) Before forwarding the synchronization message, when the UPF receives the synchronization messages of two clocks, it first filters the synchronization messages, and does not need to submit the two messages to the TSN server or the air interface at the same time, saving signaling interaction and air interface overhead. 2) Under the primary and backup clock mechanism, the enhanced UPF can timely determine the synchronization message of the primary clock and the synchronization message of the backup clock, that is, it can determine the primary clock and the backup clock during the sending process of the synchronization message flow. Compared with the currently executed BMCA algorithm with slower convergence before the sending process of the synchronization message flow, the present application can determine the primary clock and the backup clock during the sending process of the synchronization message flow, and the time convergence for determining the primary clock and the backup clock is faster.

[0221] The embodiments of the present application provide a timing method for coping with link anomalies, and this method can be applied to such as Figure 12In the network architecture shown, and this method can be applied to a core network device or a chip in a core network device. Taking the UPF as the core network device and the master clock on one UE side synchronizing the slave clock on another UE side as an example, as Figure 16 shown, this method may include:

[0222] Steps 161-165 are similar to Steps 1-5 in the synchronization process shown above. For specific descriptions, refer to the descriptions of Steps 151-155 above. Figure 6 shown.

[0223] 166. The UPF receives a first synchronization message from a first terminal device.

[0224] The implementation manner of Step 166 is similar to that of Step 156.

[0225] 167. The UPF receives a second synchronization message from a server.

[0226] Figure 16 In, the server in Step 167 is shown as Server 2. In Step 167, the processing of the second synchronization message by the UPF can refer to the description of Step 156 above.

[0227] 168. If the TSN domains to which the first synchronization message and the second synchronization message belong are the same, the UPF determines the synchronization message to be forwarded from the first synchronization message and the second synchronization message.

[0228] In Step 168, the manner in which the UPF determines the synchronization message to be forwarded from the first synchronization message and the second synchronization message can refer to Step 158 above. That is, the processing manner of the second synchronization message sent by the UPF to Server 2 is similar to the processing manner of the second synchronization message sent by the UPF to UE2.

[0229] 169. The UPF sends the first synchronization message to UE3, or the UPF sends the second synchronization message to UE3.

[0230] Figure 16 Only an example of sending the first synchronization message to UE3 is shown.

[0231] The beneficial effects of this embodiment can refer to the beneficial effects of the corresponding embodiment above. Figure 14 corresponding embodiment.

[0232] An embodiment of the present application provides a time synchronization method for coping with link anomalies. This method can be applied to a network architecture as shown in Figure 13 shown, and this method can be applied to a core network device or a chip in a core network device. Taking the UPF as the core network device and the master clock on the server side synchronizing the slave clock on one UE side as an example, as Figure 17 shown, this method may include:

[0233] Steps 171-175 are the same as above Figure 7 Steps 1 to 5 in the synchronization process shown are similar. For details, see the above description of steps 151 to 155.

[0234] 176. UPF receives the first synchronization message from the server.

[0235] Figure 17 In the example, the server in step 176 is shown as server 1. The processing manner of the first synchronization message by the UPF is similar to the implementation manner of step 156.

[0236] 177. UPF receives a second synchronization message from a second terminal device.

[0237] Figure 17 In the example, the second terminal device is shown as UE2. In step 177, the processing of the second synchronization message by the UPF can refer to the description of the above step 156.

[0238] 178. If the TSN domain to which the first synchronization message and the second synchronization message belong is the same, the UPF determines the synchronization message to be forwarded from the first synchronization message and the second synchronization message.

[0239] In step 178, the manner in which the UPF determines the synchronization message to be forwarded from the first synchronization message and the second synchronization message can be referred to the above step 158.

[0240] 179. UPF sends a first synchronization message to UE3, or UPF sends a second synchronization message to UE3.

[0241] Figure 17 Only an example of sending the first synchronization message to UE3 is shown.

[0242] The beneficial effects of this embodiment can be seen in the above Figure 14 Beneficial effects of the corresponding embodiments. Another implementation method of the embodiment of the present application is described below. Compared with the above embodiment, in which the backup clock decides whether to enable the backup clock by itself, this embodiment focuses on assigning the role of whether to enable the backup clock to the network element in the 5GS. That is, the network element in the 5GS is allowed to sense the link abnormality and instruct the backup TSN node to enable the backup clock.

[0243] The embodiment of the present application provides a timing method for dealing with link abnormalities. The method is applied to an access network device or a chip in an access network device. Taking the access network device as a gNB as an example, Figure 18 As shown, Figure 18Taking one of UE1 and UE2 as the primary clock and the other as the backup clock, and taking the clocks in the first TSN node connected to UE1, the clocks in the second TSN node connected to UE2, and the third TSN node as the slave clock as an example, the method includes:

[0244] Step 181, the gNB receives the first capability information from the first terminal device UE1 and the second capability information from the second terminal device UE2. The first capability information indicates that the first time-sensitive network (TSN) node connected to UE1 has the synchronous timing capability, and the first TSN terminal is the primary clock. The second capability information indicates that the second TSN node connected to UE2 has the timing capability, and the second TSN terminal is the backup clock.

[0245] In some embodiments, step 181 may be implemented during the process of establishing or updating a PDU session between UE1 and UE2 and the access network device and the core network device. That is, UE1 may send a capability indication to the access network device and the core network device, and the capability indication includes the first capability information. The implementation of UE2 is similar to that of UE1.

[0246] Step 182, the gNB determines that the timing link on the primary clock side in the TSN domain is abnormal.

[0247] In some embodiments, if the gNB does not receive a synchronization message from UE1 within a preset time period, the access network device determines that the timing link on the primary clock side is abnormal.

[0248] That is to say, a timer may be maintained in the gNB. If the gNB determines that it does not receive a synchronization message from UE1 within the preset time period of the timer, the gNB may consider that the timing link on the primary clock side is abnormal.

[0249] In some embodiments, the gNB may analyze the factors affecting the signal of UE1 through an artificial intelligence (AI) module; when the analysis result is that a synchronization message from UE1 cannot be received within a preset future time period, it is determined that the timing link on the primary clock side in the TSN domain is abnormal.

[0250] Exemplarily, the gNB may analyze parameters such as weather forecasts and traffic flows through the AI module, predict factors affecting the receiving channel of UE1 such as the air interface channel quality, and determine whether a synchronization message from UE1 can be received within a preset future time period. If it is determined that a synchronization message from UE1 cannot be received within the preset future time period, the gNB determines that the timing link on the primary clock side is abnormal.

[0251] In some embodiments, when receiving the second request information from the first terminal device, and the second request information indicates to replace the primary clock, it is determined that the timing link on the primary clock side in the TSN domain is abnormal.

[0252] Exemplarily, a UE connected to the master clock side may determine whether the master clock needs to be replaced. If it is determined that replacement is needed, UE1 may send a second request message to the gNB to indicate replacement of the master clock, and the gNB may determine that the timing link on the master clock side is abnormal based on the second request message.

[0253] In some embodiments, third request information from a second terminal device is received, and the third request information indicates replacement of the master clock; when the third request information is legal and the access network device cannot receive a synchronization message from the first terminal device, it is determined that the timing link on the master clock side in the TSN domain is abnormal.

[0254] Exemplarily, UE2 on the backup clock side may also determine whether the timing link on the master clock side is abnormal. If it is determined to be abnormal, UE2 may also send third request information to the gNB to indicate that the master clock needs to be replaced. When the gNB receives the third request message, it may first determine whether the third request information is legal, because there may be a phenomenon of dual clocks. Therefore, if the gNB cannot receive a synchronization message from UE1 within a preset time period, the gNB determines that the third request information is legal; if the gNB can still receive a synchronization message from UE1 within the preset time period, the gNB may consider the third request information illegal and may be malicious attack information. Then, when the gNB determines that the third request information is legal, the gNB may consider that the timing link on the master clock side is abnormal.

[0255] Step 183: The gNB sends first request information to UE2 in the TSN domain, and the first request information is used to indicate replacing the master clock of the TSN domain with the backup clock in the TSN domain.

[0256] Exemplarily, the gNB may first allocate uplink resources for UE2 and send an indication of resource allocation to the UE through messages such as radio resource control (RRC) or physical downlink control channel (PDCCH), so that UE2 can send a synchronization message of the backup clock on the UE2 side according to the uplink resources. Also, N3 resources need to be reserved between the gNB and the UPF for UE2 to transmit TSN timing messages.

[0257] Step 184: UE2 instructs the second TSN node to enable the backup clock.

[0258] In some embodiments, when the UE2 receives the first request message, it may indicate to the second TSN node to enable the backup clock in the suffix field of the first request message through DS-TT. There can be various ways to implement the structure of the suffix field. For example, the UE2 may add a field of "type-length-value (TLV) type" in the suffix field, which is used to indicate "start the backup clock". After the TLV type field, a "length of TLV" field may also be added to indicate the length information of the suffix field; or, the UE2 may add an "organization Id" field in the suffix field, which is used to indicate starting the backup clock; or, the UE2 may add an "organization subtype" field in the suffix field, which is used to indicate starting the backup clock; or, the UE2 may add 1 octet in the suffix field to indicate starting the backup clock.

[0259] Then, the UE2 may send the first request message with the added suffix field to the second TSN node, and the second TSN node may send a synchronization message to the UPF through the UE2 and the gNB, and the UPF will then send the synchronization message to the third TSN node for time synchronization.

[0260] Thus, in the embodiments of the present application, when the timing link on the primary clock side is abnormal, the role of sensing and indicating the enabling of the backup clock can be assigned to the gNB in the 5GS, so that the disconnection problem of the 5G air interface can be solved more quickly and directly, and the risk of timing interruption in the TSN network can be reduced.

[0261] The embodiments of the present application also provide a timing method for coping with link anomalies. This method is applied to a core network device or a chip in the core network device. Taking the UPF as an example of the core network device, as Figure 19 shown, this method includes:

[0262] Step 191, the UPF receives the first capability information from the first terminal device UE1 and the second capability information from the second terminal device UE2. The first capability information indicates that the first time-sensitive network (TSN) node connected to the UE1 has the synchronization timing capability, and the first TSN terminal is the primary clock. The second capability information indicates that the second TSN node connected to the UE2 has the timing capability, and the second TSN terminal is the backup clock.

[0263] The implementation manner of step 191 may refer to the implementation manner of the gNB in step 181.

[0264] Step 192, the UPF determines that the timing link on the primary clock side in the TSN domain is abnormal.

[0265] In some embodiments, a timer may be maintained in the UPF. When the UPF determines that no synchronization message from UE1 has been received within a preset time period during the timer countdown, the UPF may consider that the timing link on the primary clock side is abnormal.

[0266] In some embodiments, the UPF receives second request information from UE1 or UE2, and the second request information indicates to replace the primary clock; when the second request information is legal, it is determined that the timing link on the primary clock side in the TSN domain is abnormal. Similar to the gNB, determining that the second request information is legal is to avoid the dual clock phenomenon.

[0267] Step 193, the UPF sends first request information to UE2 in the TSN domain, and the first request information is used to indicate to replace the primary clock of the TSN domain with the backup clock in the TSN domain.

[0268] For example, the UPF sends the first request information to UE2 through the gNB.

[0269] Step 194, UE2 instructs the second TSN node to enable the backup clock.

[0270] The implementation manner of step 194 may refer to the above step 184.

[0271] Thus, in the embodiments of the present application, when the timing link on the primary clock side is abnormal, the role of perceiving and indicating the enabling of the backup clock can be assigned to the UPF in the 5GS, so that the disconnection problem of the 5G air interface can be solved more quickly and directly, and the risk of timing interruption in the TSN network can be reduced.

[0272] The embodiments of the present application also provide a timing method for coping with link anomalies. This method is applied to a terminal device or a chip in the terminal device. Taking the UE1 on the primary clock side of this terminal device as an example, as Figure 20 shown, this method includes:

[0273] Step 201, UE1 sends first capability information to the core network device UPF, and the first capability information is used to indicate that the first TSN node connected to UE1 has the synchronous timing capability, and the first TSN node is the primary clock.

[0274] UE2 also sends second capability information to the UPF, and the second capability information indicates that the second TSN node connected to UE2 has the timing capability, and the second TSN node is the backup clock.

[0275] Step 202, UE1 determines that the timing link on the primary clock side in the time-sensitive network TSN domain is abnormal.

[0276] In some embodiments, when UE1 does not receive a synchronization message from the master clock within a preset time period, UE1 determines that the timing link on the master clock side is abnormal. That is, if the clock of the first TSN node connected to UE1 is the master clock and UE1 maintains a timer, once UE1 determines that it has not received a synchronization message from the first TSN node within the preset time period of the timer, UE1 considers that the timing link on the master clock side is abnormal.

[0277] Step 203: UE1 sends a first request message to the core network device UPF. The first request message is used to indicate replacing the master clock in the TSN domain with the backup clock in the TSN domain.

[0278] UE1 can send the first request message to UPF through gNB. For example, UE1 can send the first request message to gNB by sending dedicated signaling such as RRC; or directly indicate gNB to enable the backup clock through a dedicated radio network temporary identity (RNTI) or dedicated uplink resources.

[0279] Step 204: UPF instructs UE2 to start the backup clock.

[0280] Step 205: UE2 instructs the second TSN node to enable the backup clock.

[0281] The implementation manner of step 205 can refer to step 184 above.

[0282] Therefore, in the embodiments of the present application, when the timing link on the master clock side is abnormal, the terminal device UE1 on the master clock side in 5GS can be given the role of sensing and indicating the enabling of the backup clock, so as to more quickly and directly solve the disconnection problem of the 5G air interface and reduce the risk of timing interruption in the TSN network.

[0283] The embodiments of the present application also provide a timing method for coping with link anomalies. This method is applied to a terminal device or a chip in the terminal device. Taking UE2 on the backup clock side as an example of the terminal device, as Figure 21 shown, this method includes:

[0284] Step 211: UE2 sends second capability information to the core network device UPF. The second capability information indicates that the second TSN node connected to the terminal device has timing capability and the second TSN node is the backup clock.

[0285] UE1 also sends first capability information to UPF. The first capability information is used to indicate that the first TSN node connected to UE1 has synchronous timing capability and the first TSN node is the master clock.

[0286] Step 212: UE2 determines that the timing link on the primary clock side in the Time-Sensitive Networking (TSN) domain is abnormal.

[0287] In some embodiments, a timer can be maintained in UE2. Since UE2 needs to periodically receive the sleep command of the primary clock sent by the gNB and send the sleep command to the backup clock so that the backup clock is not enabled, once UE2 does not receive the sleep command sent by the gNB within the preset time period of the timer timing, UE2 determines that the timing link on the primary clock side is abnormal.

[0288] Step 213: UE2 sends a first request message to the core network device, and the first request message is used to indicate replacing the primary clock in the TSN domain with the backup clock in the TSN domain.

[0289] UE2 can send the first request message to the UPF through the gNB to request replacing the primary clock. When the UPF receives the first request message, it needs to first determine whether the first request message is legal. The method for determining whether it is legal can refer to the method for the gNB to determine whether it is legal in the above step 182.

[0290] Step 214: The UPF instructs UE2 to enable the backup clock.

[0291] If the UPF determines that the first request message is legal, the UPF can send an indication to enable the backup clock to UE2. UE2 can indicate enabling the backup clock by sending Radio Resource Control (RRC), a dedicated Radio Network Temporary Identifier (RNTI), a scrambled scheduling request, a buffer status report (BSR), or requesting dedicated uplink resources for transmitting TSN timing messages, etc. to the gNB.

[0292] Step 215: UE2 instructs the second TSN node to start the backup clock.

[0293] The implementation method of step 215 can refer to the above step 184.

[0294] Thus, in the embodiments of the present application, when the timing link on the primary clock side is abnormal, the terminal device UE2 on the backup clock side in 5GS can be given the role of sensing and indicating the enabling of the backup clock, so that the disconnection problem of the 5G air interface can be solved more quickly and directly, and the risk of timing interruption in the TSN network can be reduced.

[0295] It should be noted that Figures 18 - 21 UE1 in the corresponding embodiment can be replaced by server 1, and UE2 can also be replaced by server 2. The difference is that server 1 and server 2 can communicate with the UPF directly without passing through the gNB.

[0296] It can be understood that, in order to implement the above functions, the above core network device includes the corresponding hardware and / or software modules for executing each function. Combining the algorithm steps of each example described in the embodiments disclosed in this article, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed in the manner of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application in combination with the embodiments, but such implementation should not be considered to exceed the scope of the present application.

[0297] In this embodiment, the core network device can be divided into functional modules according to the above method examples. For example, each functional module can be divided corresponding to each function, or two or more functions can be integrated into one processing module. The above integrated module can be implemented in the form of hardware. It should be noted that the division of modules in this embodiment is illustrative, only a logical function division, and there can be other division methods in actual implementation.

[0298] In the case of dividing each functional module corresponding to each function, Figure 22 FIG. shows a possible schematic composition of the core network device 220 involved in the above embodiment, as Figure 22 shown, the core network device 220 may include: a receiving unit 2201, a determining unit 2202, and a sending unit 2203.

[0299] Among them, the receiving unit 2201 can be used to support the core network device 220 to execute the above steps 156, 157, 191, etc., and / or for other processes of the technology described in this article.

[0300] The determining unit 2202 can be used to support the core network device 220 to execute the above steps 158, 192, etc., and / or for other processes of the technology described in this article.

[0301] The sending unit 2203 can be used to support the core network device 220 to execute the above steps 159 and 193, etc., and / or for other processes of the technology described in this article.

[0302] It should be noted that all relevant contents of each step involved in the above method embodiment can be cited in the function description of the corresponding functional module, and will not be repeated here.

[0303] The core network device 220 provided in this embodiment is used to execute the above timing method for coping with link anomalies, so it can achieve the same effect as the above implementation method.

[0304] In the case of adopting an integrated unit, as Figure 23As shown in the figure, the core network device 230 may include a processing module, a storage module, and a communication module. Among them, the processing module may be used to control and manage the actions of the core network device 230. For example, it may be used to support the core network device 230 to execute the steps performed by the above-mentioned determination unit 2202. The storage module may be used to support the core network device 230 to store program codes, data, etc. The communication module may be used to support the core network device 230 to communicate with other devices, such as communicating with radio access devices and terminal devices.

[0305] Among them, the processing module may be a processor or a controller. It may implement or execute various exemplary logic blocks, modules, and circuits described in connection with the disclosure of the present application. The processor may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of digital signal processing (DSP) and a microprocessor, and so on. The storage module may be a memory. The communication module may specifically be a device that interacts with other electronic devices, such as a radio frequency circuit, a Bluetooth chip, a Wi-Fi chip, etc.

[0306] In one embodiment, when the processing module is a processor, the storage module is a memory, and the communication module is a transceiver, the core network device involved in this embodiment may be a UPF with Figure 24 the structure shown.

[0307] In the case of dividing each function into corresponding function modules, a possible composition schematic diagram of the access network device involved in the above embodiment may also refer to the structure of the core network device 220. Similarly, the access network device may include: a receiving unit, a determining unit, and a sending unit.

[0308] Among them, the receiving unit of the access network device may be used to support the access network device to execute the above-mentioned step 181, etc., and / or for other processes of the technology described herein.

[0309] The determining unit 2202 of the access network device may be used to support the access network device to execute the above-mentioned step 182, etc., and / or for other processes of the technology described herein.

[0310] The sending unit 2203 of the access network device may be used to support the access network device to execute the above-mentioned step 183, etc., and / or for other processes of the technology described herein.

[0311] It should be noted that all relevant contents of each step involved in the above method embodiment can be cited in the function descriptions of the corresponding function modules, and will not be elaborated here.

[0312] The access network device provided in this embodiment is used to execute the above-mentioned timing method for coping with link anomalies, so the same effects as those of the above-mentioned implementation method can be achieved.

[0313] In the case of adopting integrated units, the access network device may include a processing module, a storage module, and a communication module. Among them, the processing module can be used to control and manage the actions of the access network device. For example, it can be used to support the access network device to execute the steps performed by the determination unit of the above-mentioned access network device. The storage module can be used to support the access network device to store program codes, data, etc. The communication module can be used to support the access network device to communicate with other devices, such as communicating with the core network device and the terminal device.

[0314] Among them, the processing module of the access network device can be a processor or a controller. It can implement or execute various exemplary logic blocks, modules, and circuits described in combination with the disclosure of this application. The processor of the access network device can also be a combination that realizes computing functions, such as a combination including one or more microprocessors, a combination of DSP and microprocessors, and so on. The storage module of the access network device can be a memory. The communication module of the access network device can specifically be a device that interacts with other electronic devices, such as a radio frequency circuit, a Bluetooth chip, a Wi-Fi chip, etc.

[0315] In one embodiment, when the processing module of the access network device is a processor, the storage module of the access network device is a memory, and the communication module of the access network device is a transceiver, the access network device involved in this embodiment can have a gNB with a Figure 24 structure similar to that shown.

[0316] In the case of dividing each function into corresponding function modules, a possible composition schematic diagram of the terminal device involved in the above embodiment can also refer to the structure of the core network device 220. Similarly, the terminal device may include: a receiving unit, a determining unit, and a sending unit.

[0317] Among them, the receiving unit of the terminal device can be used to support the access network device to execute the sending process of the above-mentioned first terminal device and / or the second terminal device, etc., and / or other processes of the technology described in this article.

[0318] The determining unit of the terminal device can be used to support the access network device to execute the above-mentioned step 202, step 212, etc., and / or other processes of the technology described in this article.

[0319] The sending unit of the terminal device can be used to support the access network device to execute the above-mentioned step 184, step 201, step 203, step 205, step 211, step 213, and step 215, etc., and / or other processes of the technology described in this article.

[0320] It should be noted that all the relevant content of each step involved in the above method embodiments can be cited in the function description of the corresponding functional modules, and will not be elaborated here.

[0321] The terminal device provided in this embodiment is used to execute the above-mentioned timing method for coping with link anomalies, so the same effects as those of the above implementation method can be achieved.

[0322] In the case of adopting an integrated unit, the terminal device may include a processing module, a storage module, and a communication module. Among them, the processing module can be used to control and manage the actions of the terminal device. For example, it can be used to support the terminal device to execute the steps performed by the determination unit of the above terminal device. The storage module can be used to support the terminal device to store program codes and data, etc. The communication module can be used to support the communication of the terminal device with other devices, such as communication with core network devices, access network devices, and TSN devices.

[0323] Among them, the processing module of the terminal device can be a processor or a controller. It can implement or execute various exemplary logic blocks, modules, and circuits described in combination with the disclosed content of this application. The processor of the terminal device can also be a combination that realizes computing functions, such as a combination of one or more microprocessors, a combination of DSP and microprocessors, and so on. The storage module of the terminal device can be a memory. The communication module of the terminal device can specifically be a device for interacting with other electronic devices, such as a radio frequency circuit, a Bluetooth chip, a Wi-Fi chip, etc.

[0324] In one embodiment, when the processing module of the terminal device is a processor, the storage module of the terminal device is a memory, and the communication module of the terminal device is a transceiver, the terminal device involved in this embodiment can have a UE with a Figure 24 structure similar to that shown.

[0325] The embodiment of the present application also provides an electronic device, including one or more processors and one or more memories. The one or more memories are coupled to the one or more processors. The one or more memories are used to store computer program codes, and the computer program codes include computer instructions. When the one or more processors execute the computer instructions, the electronic device executes the above-mentioned related method steps to implement the timing method for coping with link anomalies in the above embodiment.

[0326] The embodiment of the present application also provides a computer storage medium, in which computer instructions are stored. When the computer instructions run on an electronic device, the electronic device executes the above-mentioned related method steps to implement the timing method for coping with link anomalies in the above embodiment.

[0327] Embodiments of the present application also provide a computer program product. When the computer program product runs on a computer, the computer is enabled to execute the above - related steps to implement the time - synchronization method for coping with link anomalies executed by the electronic device in the above embodiments.

[0328] In addition, embodiments of the present application also provide a device, which may specifically be a chip, a component or a module. The device may include a processor and a memory connected to each other. Among them, the memory is used to store computer - executable instructions. When the device runs, the processor may execute the computer - executable instructions stored in the memory, so that the chip executes the time - synchronization method for coping with link anomalies executed by at least one electronic device in each of the above - mentioned method embodiments.

[0329] Among them, the electronic device, computer storage medium, computer program product or chip provided in this embodiment are all used to execute the corresponding methods provided above. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding methods provided above, and will not be elaborated here.

[0330] Another embodiment of the present application provides a system, which may include the above - mentioned core network device, access network device and at least one terminal device, and may be used to implement the above - mentioned time - synchronization method for coping with link anomalies.

[0331] Through the description of the above - mentioned implementation manners, those skilled in the art can understand that, for the convenience and conciseness of description, only the above - mentioned division of each functional module is used as an example for illustration. In actual applications, the above - mentioned functions may be allocated to different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above.

[0332] In several embodiments provided by the present application, it should be understood that the disclosed device and method can be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the modules or units is only a logical functional division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or integrated into another device, or some features can be ignored or not executed. Another point is that the displayed or discussed coupling or direct coupling or communication connection between each other may be through some interfaces. The indirect coupling or communication connection of the device or unit may be in an electrical, mechanical or other form.

[0333] The units described as separate components may or may not be physically separated. The components displayed as units may be one physical unit or multiple physical units, that is, they may be located in one place, or may be distributed to multiple different places. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0334] In addition, in each embodiment of the present application, each functional unit can be integrated into a processing unit, or each unit can exist physically alone, or two or more units can be integrated into one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of a software functional unit.

[0335] If the above-mentioned integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solution of the embodiments of the present application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. The software product is stored in a storage medium and includes several instructions for causing a device (which can be a single-chip microcomputer, a chip, etc.) or a processor to execute all or part of the steps of the methods described in the embodiments of the present application. The aforementioned storage medium includes: various media such as USB flash drives, mobile hard disks, read-only memories (ROMs), random access memories (RAMs), magnetic disks, or optical discs that can store program codes.

[0336] The above content is only the specific implementation manner of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed by the present application, and all of them should be covered by the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A timing method for coping with link anomalies, characterized in that, The method is applied to a core network device or a chip in a core network device, and the method includes: Receiving a first synchronization message from a first terminal device; Receiving a second synchronization message from a second terminal device or a server; Sending the first synchronization message and the second synchronization message to an Access and Mobility Management Function (AMF) network element; Receiving first indication information from the AMF network element, where the first indication information indicates that the first synchronization message and the second synchronization message are legal; If the Time-Sensitive Networking (TSN) domains to which the first synchronization message and the second synchronization message belong are the same, determining a synchronization message to be forwarded from the first synchronization message and the second synchronization message.

2. The method according to claim 1, characterized in that That the TSN domains to which the first synchronization message and the second synchronization message belong are the same includes: The Virtual Local Area Network (VLAN) identifier (VID) carried in the first synchronization message is the same as the VID carried in the second synchronization message; Or, the sequence number of the TSN domain carried in the header of the first synchronization message is the same as the sequence number of the TSN domain carried in the second synchronization message; Or, the address of the first terminal device carried in the first synchronization message and the address of the second terminal device or the server carried in the second synchronization message both belong to the TSN domain.

3. The method according to claim 1 or 2, characterized in that, Determining the synchronization message to be forwarded from the first synchronization message and the second synchronization message includes: Determining the synchronization message to be forwarded from the first synchronization message and the second synchronization message according to the address of the clock carried in the first synchronization message and the address of the clock carried in the second synchronization message.

4. The method according to claim 3, wherein The address of the clock carried in the first synchronization message is the address of the primary clock, and the address of the clock carried in the second synchronization message is the address of the backup clock; or, the address of the clock carried in the first synchronization message is the address of the backup clock, and the address of the clock carried in the second synchronization message is the address of the primary clock.

5. The method according to claim 1 or 2, characterized in that, Determining the synchronization message to be forwarded from the first synchronization message and the second synchronization message includes: Determining the synchronization message to be forwarded from the first synchronization message and the second synchronization message according to a pre-configured filtering template; wherein the filtering template includes information about the primary clock and / or information about the backup clock.

6. The method according to claim 5, wherein The information about the primary clock includes at least one of the source address of the primary clock or the prefix of Internet Protocol Version 6 (IPv6), and the information about the backup clock includes at least one of the destination address of the clock or the prefix of IPv6.

7. The method according to claim 1 or 2, characterized in that, Determining the synchronization message to be forwarded from the first synchronization message and the second synchronization message includes: When the time interval between receiving the second synchronization message and the first received first synchronization message is a first time period, and the first time period is greater than or equal to a preset time period, determining the first synchronization message as the synchronization message to be forwarded.

8. A core network device, characterized in that, including: A transceiver, configured to receive a first synchronization message from a first terminal device; The transceiver is further configured to receive a second synchronization message from a second terminal device or a server; The transceiver is further configured to send the first synchronization message and the second synchronization message to an Access and Mobility Management Function (AMF) network element; receive first indication information from the AMF network element, where the first indication information indicates that the first synchronization message and the second synchronization message are legal; The processor is configured to determine a synchronization message to be forwarded from the first synchronization message and the second synchronization message if the TSN domains to which the first synchronization message and the second synchronization message belong are the same.

9. The core network device according to claim 8, characterized in that, That the TSN domains to which the first synchronization message and the second synchronization message belong are the same includes: the Virtual Local Area Network (VLAN) identifier (VID) carried in the first synchronization message is the same as the VID carried in the second synchronization message; or, the sequence number of the TSN domain carried in the header of the first synchronization message is the same as the sequence number of the TSN domain carried in the second synchronization message; or, the address of the first terminal device carried in the first synchronization message and the address of the second terminal device or the server carried in the second synchronization message both belong to the TSN domain.

10. The core network device according to claim 8 or 9, characterized in that, The processor is configured to: determine the synchronization message to be forwarded from the first synchronization message and the second synchronization message according to the address of the clock carried in the first synchronization message and the address of the clock carried in the second synchronization message.

11. The core network device according to claim 10, characterized in that, The address of the clock carried in the first synchronization message is the address of the master clock, and the address of the clock carried in the second synchronization message is the address of the backup clock; or, the address of the clock carried in the first synchronization message is the address of the backup clock, and the address of the clock carried in the second synchronization message is the address of the master clock.

12. The core network device according to claim 8 or 9, characterized in that, The processor is configured to: determine the synchronization message to be forwarded from the first synchronization message and the second synchronization message according to a pre-configured filtering template; where the filtering template includes information about the master clock and / or information about the backup clock.

13. The core network device according to claim 12, wherein The information about the master clock includes at least one of the source address of the master clock or the prefix of Internet Protocol Version 6 (IPv6), and the information about the backup clock includes at least one of the destination address of the clock or the prefix of IPv6.

14. The core network device according to claim 8 or 9, characterized in that, The processor is configured to: when the time interval between receiving the second synchronization message and receiving the first of the first synchronization messages is a first time period, and the first time period is greater than or equal to a preset time period, determine the first synchronization message as the synchronization message to be forwarded.

15. A communication device, characterized in that, It includes: a processor and a memory connected to each other; where the memory is used to store computer execution instructions, and when the communication device runs, the processor can execute the computer execution instructions stored in the memory so that the communication device executes the method according to any one of claims 1-7.

16. The communication device according to claim 15, wherein The communication device is a chip.

17. A computer-readable storage medium, characterized in that, It includes computer instructions, and when the computer instructions run on an electronic device, the electronic device is caused to execute the method according to any one of claims 1-7 above.

18. A computer program product, characterized in that, When the computer program product runs on a computer, the electronic device is caused to execute the method according to any one of claims 1-7 above.

Images