[go: up one dir, main page]
More Web Proxy on the site http://driver.im/

WO2022028715A1 - Synchronisation temporelle basée sur un réseau dans un système 5g avec horloge gm sur le côté ue - Google Patents

Synchronisation temporelle basée sur un réseau dans un système 5g avec horloge gm sur le côté ue Download PDF

Info

Publication number
WO2022028715A1
WO2022028715A1 PCT/EP2020/072266 EP2020072266W WO2022028715A1 WO 2022028715 A1 WO2022028715 A1 WO 2022028715A1 EP 2020072266 W EP2020072266 W EP 2020072266W WO 2022028715 A1 WO2022028715 A1 WO 2022028715A1
Authority
WO
WIPO (PCT)
Prior art keywords
propagation delay
gnb
clock
synchronization message
tsn
Prior art date
Application number
PCT/EP2020/072266
Other languages
English (en)
Inventor
Rüdiger Halfmann
Rakash SIVASIVA GANESAN
Christian Markwart
Devaki Chandramouli
Kari Juhani Niemela
David KOZIOL
Pilar ANDRÉS MALDONADO
Thomas Haamning JACOBSEN
Peter Rost
Vladimir Vukadinovic
Troels Emil Kolding
Klaus Hugl
Original Assignee
Nokia Solutions And Networks Oy
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nokia Solutions And Networks Oy filed Critical Nokia Solutions And Networks Oy
Priority to PCT/EP2020/072266 priority Critical patent/WO2022028715A1/fr
Publication of WO2022028715A1 publication Critical patent/WO2022028715A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J3/00—Time-division multiplex systems
    • H04J3/02—Details
    • H04J3/06—Synchronising arrangements
    • H04J3/0635—Clock or time synchronisation in a network
    • H04J3/0638—Clock or time synchronisation among nodes; Internode synchronisation
    • H04J3/0658—Clock or time synchronisation among packet nodes
    • H04J3/0661—Clock or time synchronisation among packet nodes using timestamps
    • H04J3/0667—Bidirectional timestamps, e.g. NTP or PTP for compensation of clock drift and for compensation of propagation delays
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J3/00—Time-division multiplex systems
    • H04J3/02—Details
    • H04J3/06—Synchronising arrangements
    • H04J3/0635—Clock or time synchronisation in a network
    • H04J3/0638—Clock or time synchronisation among nodes; Internode synchronisation
    • H04J3/0658—Clock or time synchronisation among packet nodes
    • H04J3/0673—Clock or time synchronisation among packet nodes using intermediate nodes, e.g. modification of a received timestamp before further transmission to the next packet node, e.g. including internal delay time or residence time into the packet
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/28—Flow control; Congestion control in relation to timing considerations
    • H04L47/283—Flow control; Congestion control in relation to timing considerations in response to processing delays, e.g. caused by jitter or round trip time [RTT]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0231—Traffic management, e.g. flow control or congestion control based on communication conditions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W56/00—Synchronisation arrangements
    • H04W56/001—Synchronization between nodes
    • H04W56/0015—Synchronization between nodes one node acting as a reference for the others
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/04—Registration at HLR or HSS [Home Subscriber Server]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J3/00—Time-division multiplex systems
    • H04J3/02—Details
    • H04J3/06—Synchronising arrangements
    • H04J3/0635—Clock or time synchronisation in a network
    • H04J3/0638—Clock or time synchronisation among nodes; Internode synchronisation
    • H04J3/0641—Change of the master or reference, e.g. take-over or failure of the master

Definitions

  • One or more example embodiments relate generally to wireless communications and, more specifically, to Third Generation Partnership Project (3GPP) New Radio (NR), Institute of Electrical and Electronics Engineers (IEEE) time sensitive network (TSN), and (3GPP) time sensitive communications (TSC) technology, and synchronization protocols including, for example, IEEE precision time protocol (PTP) and IEEE generic PTP (gPTP).
  • 3GPP Third Generation Partnership Project
  • NR New Radio
  • IEEE Institute of Electrical and Electronics Engineers
  • TSC time sensitive communications
  • synchronization protocols including, for example, IEEE precision time protocol (PTP) and IEEE generic PTP (gPTP).
  • TSN time sensitive networking
  • IEEE Institute of Electrical and Electronics Engineers
  • a 5G system is integrated with the external TSN network as a logical TSN bridge.
  • the logical TSN bridge includes TSN translator (TT) functionality for interoperation between the TSN and the 5G system (5GS) both for a user plane and a control plane. 5GS-specific procedures in the 5G core and radio access network (RAN) may be hidden from the TSN network.
  • TT TSN translator
  • the 5G system provides TSN ingress and egress ports via the TSN translator functionality at the user equipment (UE) side called device side TT (DS-TT) and via the TSN translator functionality on the 5G Core side called network side TT (NW-TT).
  • UE user equipment
  • NW-TT network side TT
  • TSN provides industrial networks with deterministic delay to handle time sensitive traffic. Time synchronization is important for achieving very low deterministic end-to-end delay and to synchronously perform tasks like cooperative transport of goods.
  • a method of operating a core network (CN) element of a CN of a communications network includes receiving, at the CN element, a synchronization message from a first UE of the communications network, the synchronization message including a time stamp of a grand master (GM) clock; selectively performing, by the CN element, a propagation delay compensation operation on the synchronization message, based on a propagation delay of the first UE and a propagation delay of a second UE; and transmitting the synchronization message to the second UE.
  • GM grand master
  • the selectively performing the propagation delay compensation operation may include determining whether or not to perform the propagation delay compensation operation based on, a difference between the propagation delay of the first UE and the propagation delay of the second UE, and a propagation delay compensation threshold.
  • the selectively performing the propagation delay compensation operation may further include performing the propagation delay operation on the synchronization message in response to determining that the difference between the propagation delay of the first UE and the propagation delay of the second UE is greater than the propagation delay compensation threshold.
  • the received synchronization message may include an ingress timestamp based on a 5G system GM clock.
  • the performing of the propagation delay operation may include compensating the ingress timestamp based on a difference between the propagation delay of the first UE and the propagation delay of the second UE.
  • the performing of the propagation delay operation may include compensating the ingress timestamp by adding, to the ingress timestamp, the difference between the propagation delay of the first UE and the propagation delay of the second UE.
  • the method may further include receiving, at the CN element, the propagation delay of the first UE from a serving next generation Node B (gNB) of the first UE; and receiving, at the CN element, the propagation delay of the second UE from a serving gNB of the second UE.
  • gNB next generation Node B
  • the method may further include receiving, at the CN element, an updated version of the propagation delay of the first UE from the serving gNB of the first UE periodically; and receiving, at the CN element, an updated version of the propagation delay of the second UE from the serving gNB of the second UE periodically.
  • the method may further include sending a propagation delay update request to at least one gNB from among the serving gNB of the first UE and the serving gNB of the second UE; and in response to sending the propagation delay update request, receiving, at the CN element, an updated propagation delay from the at least one gNB.
  • the GM clock may be a time-sensitive networking (TSN) generalized precision time protocol (gPTP) GM clock and the synchronization message may be a gPTP networking message.
  • TSN time-sensitive networking
  • gPTP generalized precision time protocol
  • the GM clock may be a precision time protocol (PTP) GM clock and the synchronization message may be a PTP synchronization message.
  • PTP precision time protocol
  • a method of operating a next generation Node B (gNB) of a communications network includes determining, at the gNB, a propagation delay value of a UE attached to the gNB; and sending the determined propagation delay of the UE to a core network (CN) element of the communications network.
  • gNB next generation Node B
  • the sending may include sending the determined propagation delay to the CN element using next generation application protocol (NGAP) signaling.
  • NGAP next generation application protocol
  • the method may further include receiving, at the gNB, a propagation delay update request from the CN element; and the sending may include sending the determined propagation delay of the UE to the CN element in response to the propagation delay update request.
  • the method may further include iteratively determining new propagation delays of the UE; and for each determined new propagation delay, determining a difference between the new propagation delay and a propagation delay of the UE most recently sent from the gNB to the CN element, and sending the new propagation delay to the CN element in response to determining that the determined difference exceeds a trigger threshold value.
  • a core network (CN) element of a CN of a communications network includes receiving means for receiving, at the CN element, a synchronization message from a first UE of the communications network, the synchronization message including a time stamp of a grand master
  • GM GM clock
  • compensation means for selectively performing a propagation delay compensation operation on the synchronization message, based on a propagation delay of the first UE and a propagation delay of a second UE; and transmitting means for transmitting the synchronization message to the second UE.
  • the selectively performing the propagation delay compensation operation may include determining whether or not to perform the propagation delay compensation operation based on, a difference between the propagation delay of the first UE and the propagation delay of the second UE, and a propagation delay compensation threshold.
  • the selectively performing the propagation delay compensation operation may further include performing the propagation delay operation on the synchronization message in response to determining that the difference between the propagation delay of the first UE and the propagation delay of the second UE is greater than the propagation delay compensation threshold.
  • the received synchronization message may include an ingress timestamp based on a 5G system GM clock.
  • the performing of the propagation delay operation may include compensating the ingress timestamp based on a difference between the propagation delay of the first UE and the propagation delay of the second UE.
  • a next generation Node B (gNB) of a communications network includes determining means for determining, at the gNB, a propagation delay value of a UE attached to the gNB; and sending means for sending the determined propagation delay of the UE to a core network (CN) element of the communications network.
  • gNB next generation Node B
  • a core network (CN) element of a CN of a communications network includes memory storing computer- executable instructions; and a processor configured to execute the computerexecutable instructions such that the CN element is configured to perform operations including receiving, at the CN element, a synchronization message from a first UE of the communications network, the synchronization message including a time stamp of a grand master (GM) clock; selectively performing, by the CN element, a propagation delay compensation operation on the synchronization message, based on a propagation delay of the first UE and a propagation delay of a second UE; and transmitting the synchronization message to the second UE.
  • GM grand master
  • a next generation Node B (gNB) of a communications network includes memory storing computer-executable instructions; and a processor configured to execute the computer-executable instructions such that the gNB is configured to perform operations including for determining, at the gNB, a propagation delay value of a UE attached to the gNB; and sending the determined propagation delay of the UE to a core network (CN) element of the communications network.
  • gNB next generation Node B
  • CN core network
  • FIG. 1 is a diagram illustrating an example operation for performing user equipment (UE)-UE synchronization in a first communications network that includes a time-sensitive network (TSN)- integrated 5G system (5GS) and a UE-side TSN grand master (GM) clock.
  • TSN time-sensitive network
  • 5GS 5G system
  • GM UE-side TSN grand master
  • FIG. 2A illustrates an example embodiment of a network element.
  • FIG. 2B illustrates another example embodiment of a network element.
  • FIG. 3 is a diagram illustrating an example of selectively applying propagation delay compensation in an operation for performing UE-UE synchronization in a second communications network that includes a UE-side (g)PTP GM clock, according to at least some example embodiments.
  • FIG. 4 is a flowchart illustrating a method of operating a communications network to facilitate a UE-UE synchronization operation by using core network (CN)- based selective application of propagation delay compensation, according to at least some example embodiments.
  • CN core network
  • FIG. 5 illustrates a timing accuracy error chart, according to at least some example embodiments.
  • FIG. 6 is a flowchart illustrating a method of operating a network element to facilitate a UE-UE synchronization operation by using CN-based selective application of propagation delay compensation, according to at least some example embodiments.
  • a 5G system (5GS) is serving as a logical TSN bridge (e.g., a 5GS bridge)
  • a logical TSN bridge e.g., a 5GS bridge
  • the clock of the TSN network connected either to a device side TSN translator (DS-TT) or to a network side TSN translator (NW-TT) of the 5GS bridge needs to be synchronized with the clock of the TSN network on NW-TT or DS-TT, respectively of the 5GS bridge.
  • DS-TT device side TSN translator
  • NW-TT network side TSN translator
  • Elements of the 5GS are all synchronized to the 5GS clock.
  • This 5GS clock synchronization can be achieved, for example, by providing a common clock source to gNB and UPF (e.g. GNSS) or by distributing the 5GS clock from one node to other nodes using, for example, the precision time protocol (PTP) in the transport network between UPF and gNB.
  • PTP precision time protocol
  • the synchronization between the UE and other network nodes in the 5GS may be achieved by sending 5GS reference time information from gNB to the UEs using either unicast or broadcast radio resource control (RRC) signaling (e.g., a DLInformationTransfer or system information block 9 (SIB9) message, respectively).
  • RRC radio resource control
  • the (g)PTP message from the TSN node on the network side can be transported to the TSN node on the UE side by adding the residence time within the 5GS bridge to the (g)PTP message time correction field.
  • the residence time is measured by time stamping at the ingress, namely at NW-TT, and at the egress namely, DS-TT. Details of the time synchronization mechanism are discussed, for example, in section 5.27.1 of 3GPP TS 23.501.
  • (g) PTP is used to refer, collectively, to the Institute of Electrical and Electronics Engineers (IEEE) 802. IAS generalized precision time protocol (gPTP) and the IEEE 1588 precision time protocol (PTP).
  • IEEE Institute of Electrical and Electronics Engineers 802. IAS generalized precision time protocol
  • PTP IEEE 1588 precision time protocol
  • propagation delay compensation needs to be applied to the reference time information sent from the gNB to the UE to achieve a synchronization accuracy of no greater than Ips, which may be parameter specified by some specifications and/or TSN-integrated 5GS implementations.
  • Ips may be parameter specified by some specifications and/or TSN-integrated 5GS implementations.
  • the studies have also shown that propagation delay compensation can be beneficial at UE-to-gNB distances of around 100m, but not required. Below UE-to-gNB distances of 100m, the accuracy might deteriorate when using propagation delay compensation.
  • Timing Advance is used for compensation of propagation delay in UL to ensure that the bursts transmitted by different terminals arrive at the correct UL time frame at the base station without overlapping and therefore, UE individual TA offset (TAi) corresponds to 2 times the propagation delay of the corresponding node i (PDi). TA is therefore also a likely candidate for compensating the propagation delay for the purpose of accurate time synchronization.
  • the TA adjustment granularity, TA adjustment accuracy, UE timing error, gNB UL receive timing estimation error and gNB time alignment error are the key contributors. These errors appear due to the fact that the propagation delay between the UE and gNB needs to be estimated. Furthermore, the processing time at the gNB and the UE generally need to be estimated in order to correctly know the time at which the frame is received or transmitted.
  • 3GPP release- 17 addresses a scenario in which the 5GS supports the situation where the working clock (e.g., the grand master (GM)) of a TSN/time- sensitive communications (TSC) device resides behind a UE (at a DS-TT), and one or more other UEs are synchronized to the GM clock.
  • the working clock e.g., the grand master (GM)
  • TSC time- sensitive communications
  • FIG. 1 illustrates an example operation for performing UE-UE synchronization in a first communications network 100 that includes a TSN-integrated 5GS and a UE-side TSN GM clock.
  • FIG. 1 is discussed in greater detail below.
  • the first communications network 100 includes next generation radio access network (NG-RAN) and Third Generation Partnership Project (3GPP) 5G New Radio (NR) radio access technology and is part of a 5GS.
  • the first communications network 100 includes a first UE 125_R connected to a first DS-TT 120_R, a second UE 125_O connected to a second DS-TT 120_O, a gNB 110, and a user plane function (UPF) 135 connected to a NW-TT 130.
  • the first UE 125_R may also be referred to in the present disclosure as the reference UE 125_R or UE_ref.
  • the second UE 125_O may also be referred to in the present disclosure as the other UE 125_O or UE_other.
  • the first communications network 100 may further include a 5GS clock 15 (e.g., a 5GS master or grand master (GM) clock). Further, clocks of 5G elements within the first communications network 100 (i.e., local references 15L to the GM 5GS clock 15 at the first and second UEs 125_R and 125_O, the gNB 110, and/or the UPF 135) may be synchronized to the 5GS GM clock 15.
  • 5GS clock 15 e.g., a 5GS master or grand master (GM) clock
  • clocks of 5G elements within the first communications network 100 i.e., local references 15L to the GM 5GS clock 15 at the first and second UEs 125_R and 125_O, the gNB 110, and/or the UPF 135.
  • the first DS-TT 120_R and second DS-TT 120_O are embodied by the first UE 125_R and second UE 125_O, respectively (e.g., as software/ firmware executed by processors of the first UE 125_R and second UE 125_O and/or circuitry included in the first DS-TT 120_R and second DS-TT 120_O).
  • operations described as being performed by (or with respect to) the first DS-TT 120_R and/or second DS-TT 120_O may be performed by (or with respect to) the first UE 125_R and/or the second UE 125_O, respectively.
  • At least some 5G network elements of the first communications network 100 may be included in a 5GS bridge 160 of the first communications network 100.
  • the 5GS bridge 160 may be connected to TSN nodes including, for example, a first TSN grand master (GM) clock 20, a second TSN GM clock 30, first TSN end stations 150, second TSN end stations 152, and third TSN end stations 140.
  • GM TSN grand master
  • the first TSN GM clock 20 may be a GM clock of a first TSN domain (i.e., TSN Domain 1)
  • the first TSN end stations 150 and third TSN end stations 140 may be end stations of the first TSN domain
  • the second TSN GM clock 30 may be a TSN GM clock of a second TSN domain (i.e., TSN Domain 2)
  • the second TSN end stations 152 may be TSN domain end stations of the second TSN domain.
  • TSN nodes may include local references 20L and/or 30L to the TSN GMs 20 and 30, respectively, which may be synchronized to the TSN GMs 20 and 30.
  • the 5GS bridge 160 includes the first UE 125_R, the first DS-TT 120_R, the second UE 125_O, the second DS-TT 120_G, the gNB 110, the UPF 135 and the NW-TT 130.
  • the 5GS bridge 160 may also be referred in the present disclosure as the TSN bridge 160 or the logical TSN bridge 160. Further, in the example illustrated in FIG.
  • the 5GS bridge 160 is connected to the first TSN GM clock 20 and the second TSN GM clock 30 via the first DS_TT 120_R, connected to the first TSN end stations 150 and second TSN end stations 152 via the NW_TT 130, and connected to the third TSN end stations 140 via the second DS-TT 120_O.
  • a grand master (GM) clock may also be referred to, simply, as GM.
  • the first communications network 100 may further include 5G core (5GC) network elements.
  • the gNB 110 may be connected to an access and mobility management function (AMF) element and/or a session management function (SMF) element.
  • the first communications network 100 may further include long-term evolution (LTE) network elements that are connected to one or more of the gNB 110, the first UE
  • LTE elements include, but are not limited to, LTE radio access technology (RAT) network elements (e.g., evolved universal mobile telecommunications system (UMTS) terrestrial radio access network (E-UTRAN) network elements) such as evolved node Bs (eNBs), and LTE core network elements (e.g., evolved packet core (EPC) network elements) such as mobility management entities (MMEs).
  • RAT radio access technology
  • UMTS evolved universal mobile telecommunications system
  • E-UTRAN terrestrial radio access network
  • LTE core network elements e.g., evolved packet core (EPC) network elements
  • MMEs mobility management entities
  • An example structure which may be used to embody one or more radio network elements (e.g., gNBs, UEs, UPFs etc.) of the first communications network 100 will now be discussed below with respect to FIGS. 2A and 2B.
  • FIG. 2A illustrates an example embodiment of a network element.
  • the network element is a gNB (i.e., gNB 102).
  • the gNB 102 includes: a memory 740; a processor 720 connected to the memory 740; various interfaces 760 connected to the processor 720; and one or more antennas or antenna panels 765 connected to the various interfaces 760.
  • the various interfaces 760 and the antenna 765 may constitute a transceiver for transmitting/ receiving data to /from a UE, a gNB, and/or other radio network element via a plurality of wireless beams.
  • interfaces 760 may also include interfaces for supporting wired communications.
  • the memory 740, processor 720, and interfaces 760 are an example of a central unit (CU) of the gNB 102, and the one or more antennas or antenna panels 765 are an example of a distributed unit (DU) or DUs of the gNB 102.
  • CU central unit
  • DU distributed unit
  • the gNB 102 may include many more components than those shown in FIG. 2 A. However, it is not necessary that all of these generally conventional components be shown in order to disclose the illustrative example embodiment.
  • the memory 740 may be a computer readable storage medium that generally includes a random access memory (RAM), read only memory (ROM), and/or a permanent mass storage device, such as a disk drive.
  • the memory 740 also stores an operating system and any other routines / modules / applications for providing the functionalities of the gNB (e.g., functionalities of a gNB, methods according to example embodiments, etc.) to be executed by the processor 720.
  • These software components may also be loaded from a separate computer readable storage medium into the memory 740 using a drive mechanism (not shown).
  • Such separate computer readable storage medium may include a disc, tape, DVD/CD-ROM drive, memory card, or other like computer readable storage medium (not shown).
  • software components may be loaded into the memory 740 via one of the various interfaces 760, rather than via a computer readable storage medium.
  • the processor 720 may be configured to carry out instructions of a computer program by performing the arithmetical, logical, and input/ output operations of the system. Instructions may be provided to the processor 720 by the memory 740.
  • the various interfaces 760 may include components that interface the processor 720 with the one or more antennas 765, or other input/output components. As will be understood, the various interfaces 760 and programs stored in the memory 740 to set forth the special purpose functionalities of the gNB 102 will vary depending on the implementation of the gNB 102.
  • the interfaces 760 may also include one or more user input devices (e.g., a keyboard, a keypad, a mouse, or the like) and user output devices (e.g., a display, a speaker, or the like).
  • user input devices e.g., a keyboard, a keypad, a mouse, or the like
  • user output devices e.g., a display, a speaker, or the like.
  • the network element of FIG. 2A is illustrated as a gNB, other network elements (e.g., UEs, other radio access and backhaul network elements, network elements embodying one or more of a UPF, AMF, TSN GM clock, TSN end station, DS-TT, NW-TT or the like) may also have the structure of the network element illustrated in FIG. 2A.
  • the memory 740 may store an operating system and any other routines/ modules/ applications for providing the functionalities of the UEs, UPF, AMF, TSN GM clock, TSN end station, DS-TT, NW-TT, etc.
  • any or all of the first UE 125_R, the second UE 125_O, the gNB 110, the UPF 135, the first and second DS-TTs 120_R and 120_O, the NW-TT 130, the first and second TSN GMs 20 and 30, the first TSN end stations 150, the second TSN end stations 152, and/or the third TSN end stations 140 may be embodied by the network element illustrated in FIG.
  • the memory 740 stores computer-executable instructions that, when executed by the processor 720, cause the processor 720 to perform the operations described in the present disclosure as being performed by the first UE 125_R, the second UE 125_O, the gNB 110, the UPF 135, the first DS-TT 120_R, the second DS-TT 120_O, the NW-TT 130, the first and second TSN GMs 20 and 30, the first TSN end stations 150, the second TSN end stations 152, and/or the third TSN end stations 140.
  • FIG. 2B illustrates another example embodiment of a network element.
  • network element 104 includes a determining/ compensation means 210, a transmitting/ sending means 220 and a receiving means 230.
  • the determining/ compensation means 210 is embodied by the processor 720 and memory 740 of FIG. 2A.
  • the transmitting/ sending means 220 is embodied by the communications interfaces 760 and the one or more antennas 765 of FIG. 2A.
  • the receiving means is embodied by the communications interfaces 760 and the one or more antennas 765 of FIG. 2A.
  • the processor 720 and memory 740 are an example of a “determining means”
  • the processor 720 and memory 740 are an example of a “compensation means”
  • the communications interfaces 760 and the one or more antennas 765 are an example of a “transmitting means”
  • the communications interfaces 760 and the one or more antennas 765 are an example of a “sending means.”
  • FIG. 1 illustrates an example of a solution described in 3GPP TR 23.700-20 for performing UE-UE synchronization in a TSN-integrated 5GS with a UE-side GM (i.e., a TSN GM that is behind a UE).
  • a TSN GM e.g., the first TSN GM 20
  • the TSN GM provides a message including a TSN GM timestamp to the DS-TT connected to the reference UE (e.g., the first DS-TT 120_R connected to the first UE 125_R)
  • the message is timestamped with an ingress timestamp (i.e., with respect to the 5GS clock).
  • the message and the ingress timestamp are delivered to the gNB (e.g., gNB 110) and to the UPF (e.g., UPF 135) where the NW-TT (e.g., NW-TT 130) updates its local reference of the TSN GM based on the TSN GM timestamp included in the message.
  • the UPF e.g., UPF 135) is also capable of conducting local switching of the message, timestamping of the message with an ingress timestamp, and delivering the message to an other UE connected to a TSN device being synchronized to the TSN GM (e.g., the second UE 125_O).
  • the DS-TT connected to the other UE adds an egress timestamp to the message as well and can therefore calculate the residence time between the two DS-TT (e.g., the first DS_TT 125_R and the second DS_TT 125_O).
  • the (g)PTP message including a TSN GM timestamp is transported from the UE side TSN node (e.g., the first DS-TT 120_R attached to the first UE 125_R) to the network side TSN node (e.g., NW_TT 130) and the TSN nodes attached to the other UEs (e.g., the second DS-TT 120_O attached to the second UE 125_O).
  • the ingress stamping (i.e., with respect to the 5GS clock) is performed at the DS-TT of the UE providing TSN GM clock (e.g., the first DS-TT 120_R attached to the first UE 125_R) by sending (g)PTP messages
  • the egress stamping (i.e., with respect to the 5GS clock) is performed at the NW-TT or at the DS-TT (sink UEs, i.e. the UEs which receive and ‘consume’ the synchronization information carried in (g)PTP messages).
  • the TSN GM (e.g., first TSN GM 20) resides on the reference UE side (e.g., the first UE 125_R or UE_ref), and this is to be synchronized to another UE (e.g., the second UE 125_O or UE_other), the relative synchronization error introduced by propagation delay compensation (e.g. TA inaccuracies discussed above in section 2) between the two UEs may become nearly twice as large when using propagation delay compensation.
  • the UEs may be located far away from each other and the PD can be quite different.
  • the relative error depends on the difference (APDi) between a propagation delay from gNB (e.g., gNB 110) to UE_ref and a propagation delay from gNB (e.g., gNB 110 or another gNB) to UE_other, and thus, the relative error can be significant.
  • propagation delay compensation may improve the synchronization accuracy, when APDiis large, but may have a small and/or negative impact on synchronization accuracy when APDi is small. If this relationship between synchronization accuracy APDi is not accounted for when determining if propagation delay compensation should be used or not, some specified 3GPP 5GS parameters (e.g., a synchronization accuracy not exceeding Ips) might not be met, or the accuracy may be undesirably poor. Accordingly, it would be advantageous to develop a manner of avoiding poor synchronization accuracy resulting from the misapplication of propagation delay compensation.
  • UE-UE synchronization accuracy may be improved or, alternatively, optimized for situations where a (g)PTP GM (e.g., the first TSM GM 20 and/or second TSM GM 30 in FIG. 1) resides on the UE side.
  • a (g)PTP GM e.g., the first TSM GM 20 and/or second TSM GM 30 in FIG. 1 resides on the UE side.
  • FIG. 3 is a diagram illustrating an example of selectively applying propagation delay compensation in an operation for performing UE-UE synchronization in a second communications network 200 that includes a UE-side (g)PTP GM clock, according to at least one example embodiment.
  • the second communications network 200 includes the first UE 125_R connected to the first DS-TT 120_R, the second UE 125_O connected to the second DS-TT 120_O, the user plane function (UPF) 135 connected to the NW-TT 130, the 5GS bridge 160, the first TSN GM 20, first TSN end stations 150, and third TSN end stations 140.
  • UPF user plane function
  • the second communications network 200 may further include the 5GS clock 15 (e.g., a 5GS GM clock), and clocks of 5G elements within the second communications network 200 (i.e., local references 15L to the GM 5GS clock 15 at the first and second UEs 125_R and 125_O, the gNB 110, and/or the UPF 135) may be synchronized to the 5GS GM clock 15..
  • the UPF 135 and the NW-TT 130 may be implemented by the same network element (e.g., the same network node, computer, server, etc.).
  • the NW-TT 130 may be implemented as part of the UPF 135.
  • UE_ref and UE_other are illustrated in the first communications network 100 in FIG. 1 as being attached to the same serving gNB, gNB 110, in the example of the second communications network 200 illustrated in FIG. 3, UE_ref and UE_other may be respectively attached to separate serving gNBs: first gNB 110_R and second gNB 110_O.
  • first gNB 110_R may also be referred to as the reference gNB or gNB_ref
  • the second gNB 110_O may also be referred to as the other gNB or gNB_other.
  • gNB_ref and gNB_other may each be connected to the UPF 135.
  • UE_ref and UE_other of the second communications network 200 are connected to the same serving gNB, for example, in the manner shown in FIG. 1 with respect to the gNB 110 of the first communications network 100.
  • the operations described with reference to FIGS. 3-5 as being performed by the first gNB 110_R and the operations described with reference to FIGS. 3-5 as being performed by the second gNB 110_O may all be performed by a single serving gNB to which the first gNB 110_R and the second gNB 110_O are attached in common in the second communications network 200.
  • the 5GS bridge 160 includes the first UE 125_R connected to the first DS-TT 120_R, the second UE 125_O connected to the second DS-TT 120_O, the gNB_ref, gNB_other, and the UPF 135 connected to the NW-TT 130.
  • the second communications network 200 may include 5GC elements (e.g., an AMF and/or SMF) and/or LTE elements, in the same manner discussed above with respect to the first communications network 100 of FIG. 1.
  • a 5GC is an example of a CN portion of a 5GS in which the 5GC is included.
  • the second communications network 200 is illustrated as using TSN in the example illustrated in FIG. 3.
  • the second communications network 200 is illustrated as including a 5GS integrated with elements of a TSN network architecture.
  • the UE-side (g)PTP GM clock of the second communications network 200 is implemented by the first TSN GM 20.
  • the second communications network 200 is not limited to using TSN.
  • the second communications network 200 does not use TSN, and the UE-side (g)PTP GM clock of the second communications network 200 is an IEEE 802. IAS gPTP GM clock.
  • the second communications network 200 does not use TSN, and the UE-side (g)PTP GM clock of the second communications network 200 is an IEEE 1588 PTP GM clock.
  • the second communications network 200 when the second communications network 200 is implemented without using TSN , the second communications network 200 does not include the logical TSN bridge 160.
  • FIG. 4 is a flowchart illustrating a method of operating a communications network to facilitate a UE-UE synchronization operation by using core network (CN)- based selective application of propagation delay compensation, according to at least some example embodiments.
  • CN core network
  • the CN 4 illustrates operations and communications of the reference UE UE_ref, the other UE UE_other, the reference gNB gNB_ref, the other gNB gNB_other, and the CN (i.e., the 5GC) of the second communications network 200.
  • the CN may include, for example, the UPF 135/NW- TT 130, and/or other 5GC elements such as the AMF (not illustrated) and/or SMF (not illustrated). Operations described in the present specification (e.g., with reference to FIGS.
  • 4-6 as being performed by the CN (or 5GC) may be performed by a network element included in the CN, such as, for example, the UPF 135, the NW- TT 130, a network element embodying both the UPF 135 and the NW-TT 130, the AMF (not illustrated) and/or SMF (not illustrated).
  • a network element included in the CN such as, for example, the UPF 135, the NW- TT 130, a network element embodying both the UPF 135 and the NW-TT 130, the AMF (not illustrated) and/or SMF (not illustrated).
  • step S410 the CN determines a propagation delay compensation threshold PD_threshold.
  • propagation delay compensation is applied to a UE-UE synchronization operation in communications network 200 when the propagation delay delta (i.e., APDi), which is the delta (i.e., an absolute value of a difference) between PD_other (i.e., the propagation delay of the other UE UE_other) and PD_ref (i.e., the propagation delay of the reference UE UE_ref), is larger than PD_threshold.
  • APDi the propagation delay delta
  • PD_other i.e., the propagation delay of the other UE UE_other
  • PD_ref i.e., the propagation delay of the reference UE UE_ref
  • Determining the propagation delay compensation threshold PD_threshold in step S410 may include the CN reading a previously stored threshold value (e.g., from a memory device internal or external to the CN), or, alternatively, the CN generating a threshold value.
  • PD_threshold may be determined (e.g., offline, before the steps of FIG. 4 begin, by a designer or operator of the second communications network 200 or one or more elements thereof; or, alternatively, during step S410, by the CN) based on time-synchronization error models generated from an empirical analysis of factors including, for example, the error sources that occur as soon as propagation delay compensation is being done.
  • FIG. 5 illustrates a timing accuracy error chart.
  • the timing accuracy error chart plots synchronization errors as a function of APDi both without propagation delay compensation (510) and with propagation delay compensation (520).
  • a suitable PD_threshold would be around 220 ns.
  • PD_threshold may be configured in the CN either by operations, administration and maintenance (0AM) or by internal mechanisms.
  • the CN may generate PD_threshold for the entire communications network 200 or, alternatively, based on aspects of specific gNBs (e.g. configuration parameters such as subcarrier spacing (SCS), bandwidth, manner of implementing timing advance (TA), etc.).
  • SCS subcarrier spacing
  • TA timing advance
  • the CN may generate PD_threshold such that a value of PD_threshold is unique to each pair of ⁇ gNB_ref, gNB_other ⁇ and may further base the generation of PD_threshold on aspects of each UE pair ⁇ UE_ref, UE_other ⁇ , e.g. their UE capabilities or even more current connection conditions.
  • step S420 a (g)PTP node (e.g., a (g)PTP master such as TSN GM 20) connected to UE_ref sends a (g)PTP sync message, which includes a timestamp of the (g)PTP GM clock (e.g., TSN GM 20), to UE_ref (e.g., the first UE 125_R).
  • a (g)PTP node e.g., a (g)PTP master such as TSN GM 20
  • UE_ref e.g., the first UE 125_R
  • step S430 UE_ref appends an ingress timestamp (TSi) to the (g)PTP sync message based on the 5GS GM clock 15 (or a local reference thereof, 15L), and in step S440, UE_ref transmits the (g)PTP sync message to which the TSi has been appended to the CN (e.g., via gNB_ref).
  • step S440 the method proceeds to step S450.
  • step S450 the CN (e.g., the UPF 135 and/or NW-TT 130) uses packet inspection to discover that UE_ref has transmitted a (g)PTP message, e.g. based on the destination of the (g)PTP message.
  • step S460 includes sub steps S462r, S464r, S462o and S464o.
  • gNB_ref determines the propagation delay PD_ref of UE_ref (S462r)
  • gNB_other determines the propagation delay PD_other of UE_other (S464r)
  • PD_ref and PD_other are reported to the CN by the gNB_ref (S464r) and gNB_other (S464o), respectively.
  • gNB_ref and gNB_other determine propagation delay values PF_ref and PD_other, respectively, by estimating the propagation values in accordance with known methods. According to at least some example embodiments, gNB_ref and gNB_other determine and report PD_ref and PD_other to the CN periodically. Alternatively, according to at least some example embodiments, gNB_ref and gNB_other determine and report PD_ref and PD_other to the CN in response to a request from the CN.
  • gNB_ref and gNB_other determine PD_ref and PD_other periodically and report PD_ref and PD_other to the CN in response to a request from the CN.
  • the CN sends a update PD value request to gNB_ref and gNB_other in response to discovering the (g)PTP message in step S450.
  • each gNB determines its corresponding PD value (i.e., PD_ref and PD_other) periodically, each gNB periodically compares its currently determined PD value to a PD value the gNB most recently transferred to the CN, and, when either gNB determines that a difference between its currently determined PD value and its most recently transferred PD value exceeds a desired threshold value, the gNB that determined that the desired threshold value was exceeded is triggered to send its currently determined PD value to the CN.
  • the aforementioned desired threshold value may be referred to as a trigger threshold.
  • a value of the trigger threshold may be determined in accordance with the preferences of a designer or operator of the second communications network 200, for example, based on an empirical analysis on the effects of different values for the trigger threshold on a frequency with which a gNB associated with the trigger threshold sends updated PD values and/or an amount of network traffic created by the PD values sent by the associated gNB.
  • multiple methods of generating and transmitting PD_ref and/or PD_other may be used together.
  • Step S470 will be explained with reference to FIG. 6, which is discussed next below.
  • FIG. 6 is a flowchart illustrating a method of operating a network element to facilitate a UE-UE synchronization operation by using CN-based selective application of propagation delay compensation, according to at least some example embodiments.
  • FIG. 6 will be explained from the perspective of a CN element, which is a network element of the CN of the second communications network 200.
  • the CN element may be any network element of the CN.
  • the CN element may be the UPF 135, the NW-TT 130, or a network element embodying both the UPF 135 and the NW-TT 130.
  • the CN element receives a (g)PTP message including an ingress time stamp (TSi) of the reference UE UE_ref (i.e., the first UE 125_R of the second communications network 200 of FIG. 3).
  • the (g)PTP message may be a SYNC message.
  • the ingress time stamp TSi indicates a time (with respect to the 5GS GM 15L or a local reference thereto 15L) at which the (g)PTP message entered the 5GS bridge 160.
  • the (g)PTP message may include a timestamp of a (g)PTP GM clock (e.g., the first TSN GM 20) for performing a synchronization operation with a (g)PTP slave (e.g., a TSN node’s local reference 20L to the TSN GM 20).
  • a (g)PTP slave e.g., a TSN node’s local reference 20L to the TSN GM 20.
  • step S450 The CN element performs step S450 in the manner described above with reference to FIG. 4. After step S450, the CN element proceeds to step S620.
  • step S620 the CN element receives the propagation delay value of UE_ref, PD_ref, and the propagation delay value of UE_other, PD_other.
  • the CN element receives PD_ref and PD_other in response to the gNB_ref and gNB_other generating and transmitting PD_ref and PD_other in the manner discussed above with reference to step S460 of FIG. 4.
  • the CN element may receive PD_ref and PD_other at the same time, at different times, periodically and/or in respond to a request sent from the CN element to one or both of gNB_ref and gNB_other, depending on the manner in which gNB_ref and gNB_other generate and transmit PD_ref and PD_other.
  • Various manners of generating and transmitting PD_ref and PD_other are discussed above with reference to step S460 of FIG. 4.
  • step S470 of FIG. 4 may include steps S625-S650.
  • the CN element determines if a (g)PTP slave to which the (g)PTP message is being sent is behind an N6 interface or behind a UE (i.e., UE_other). If, in step S625, the CN element determines that the (g)PTP slave is behind an N6 interface (e.g., the (g)PTP slave is behind an element of the CN), the method proceed to step S630.
  • step S630 the CN element captures an egress timestamp (TSe) corresponding to the arrival time of the (g)PTP message at the CN element by, for example, referencing a current time indicated by the CN element’s local reference 15L of to the 5GS GM 15.
  • TSe egress timestamp
  • the CN element applies propagation delay compensation to the residence time of the (g)PTP message.
  • the CN element may apply the propagation delay compensation by updating the residence time of the (g)PTP message based on the ingress time stamp TSi, the egress time stamp TSe, and UE_ref’s propagation delay PD_ref.
  • the CN element may apply the propagation delay compensation by updating the residence time of the (g)PTP message in accordance with the following expression:
  • step S635 the CN element proceeds to step S640.
  • step S640 the CN element transmits the (g)PTP message with the propagation delay compensated residence time to the (g)PTP slave that is the destination of the (g)PTP message and is behind the N6 interface.
  • step S625 the CN element determines that the (g)PTP slave that is the destination of the (g)PTP message is behind UE_other, the method proceeds to step S645.
  • step S645 the CN element performs a comparison operation based PD_ref, PD_other, and PD_threshold. For example, in step S645, the CN element may determine whether a magnitude (e.g., absolute value) of a difference between PD_other and PD_ref is less than PD_threshold in accordance with the following expression:
  • UE_other Based on the results of the comparison operation performed in step S645, UE_other selectively chooses between performing propagation delay compensation operation with respect to the (g)PTP message and not applying propagation delay compensation to the residence time of the (g)PTP message.
  • UE_other proceeds to step S650.
  • the CN element performs a propagation delay compensation operation.
  • the CN element may perform the propagation delay compensation operation by compensating the ingress time stamp (TSi) of the (g)PTP message based on a magnitude (e.g., absolute value) if a difference between PD_other and PD_ref.
  • the CN element may compensate the TSi of the (g)PTP message in accordance with the following expression:
  • step S650 the CN element proceeds to step S640.
  • step S640 the CN element transmits the (g)PTP message with the propagation delay-compensated TSi to the (g)PTP slave that is the destination of the (g)PTP message and is behind UE_other. Because the TSi was compensated in step S650, the residency time will ultimately be compensated when the (g)PTP slave that is the destination of the (g)PTP message uses the compensated TSi to update the residency time of the (g)PTP message based.
  • step S645 determines in step S645 that the magnitude of the difference between PD_other and PD_ref is less than PD_threshold (Y)
  • the CN element proceeds to step S640 without performing a compensation operation on the (g)PTP message.
  • step S640 the CN element transmits the uncompensated (g)PTP message to the (g)PTP slave that is the destination of the (g)PTP message and is behind UE_other.
  • the (g)PTP slave can use the residence time (which is compensated or uncompensated, depending on whether or not propagation delay compensation was performed) and the timestamp of the (g)PTP GM clock (e.g., the first TSN GM 20) included in the (g)PTP message to synchronize the (g)PTP slave, for example, by updating a local reference to the (g)PTP GM clock (e.g., local reference 20L to the first TSN GM 20).
  • a local reference to the (g)PTP GM clock e.g., local reference 20L to the first TSN GM 20.
  • first, second, etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and similarly, a second element could be termed a first element, without departing from the scope of this disclosure.
  • the term "and / or,” includes any and all combinations of one or more of the associated listed items.
  • Such existing hardware may be processing or control circuitry such as, but not limited to, one or more processors, one or more Central Processing Units (CPUs), one or more controllers, one or more arithmetic logic units (ALUs), one or more digital signal processors (DSPs), one or more microcomputers, one or more field programmable gate arrays (FPGAs), one or more System-on-Chips (SoCs), one or more programmable logic units (PLUs), one or more microprocessors, one or more Application Specific Integrated Circuits (ASICs), or any other device or devices capable of responding to and executing instructions in a defined manner.
  • processors Central Processing Units (CPUs), one or more controllers, one or more arithmetic logic units (ALUs), one or more digital signal processors (DSPs), one or more microcomputers, one or more field programmable gate arrays (FPGAs), one or more System-on-Chips (SoCs), one or more programmable logic units (PLUs
  • a process may be terminated when its operations are completed, but may also have additional steps not included in the figure.
  • a process may correspond to a method, function, procedure, subroutine, subprogram, etc.
  • a process corresponds to a function
  • its termination may correspond to a return of the function to the calling function or the main function.
  • the term “storage medium,” “computer readable storage medium” or “non-transitory computer readable storage medium” may represent one or more devices for storing data, including read only memory (ROM), random access memory (RAM), magnetic RAM, core memory, magnetic disk storage mediums, optical storage mediums, flash memory devices and/or other tangible machine-readable mediums for storing information.
  • ROM read only memory
  • RAM random access memory
  • magnetic RAM magnetic RAM
  • core memory magnetic disk storage mediums
  • optical storage mediums optical storage mediums
  • flash memory devices and/or other tangible machine-readable mediums for storing information.
  • computer readable medium may include, but is not limited to, portable or fixed storage devices, optical storage devices, and various other mediums capable of storing, containing or carrying instruction (s) and/or data.
  • example embodiments may be implemented by hardware, software, firmware, middleware, microcode, hardware description languages, or any combination thereof.
  • the program code or code segments to perform the necessary tasks may be stored in a machine or computer readable medium such as a computer readable storage medium.
  • a processor or processors will perform the necessary tasks.
  • at least one memory may include or store computer program code
  • the at least one memory and the computer program code may be configured to, with at least one processor, cause a network element or network device to perform the necessary tasks.
  • the processor, memory and example algorithms, encoded as computer program code serve as means for providing or causing performance of operations discussed herein.
  • a code segment of computer program code may represent a procedure, function, subprogram, program, routine, subroutine, module, software package, class, or any combination of instructions, data structures or program statements.
  • a code segment may be coupled to another code segment or a hardware circuit by passing and/or receiving information, data, arguments, parameters or memory contents.
  • Information, arguments, parameters, data, etc. may be passed, forwarded, or transmitted via any suitable technique including memory sharing, message passing, token passing, network transmission, etc.
  • Some, but not all, examples of techniques available for communicating or referencing the object/ information being indicated include the conveyance of the object/information being indicated, the conveyance of an identifier of the object/information being indicated, the conveyance of information used to generate the object/information being indicated, the conveyance of some part or portion of the object/information being indicated, the conveyance of some derivation of the object/information being indicated, and the conveyance of some symbol representing the object/information being indicated.
  • UEs, base stations, eNBs, RRHs, gNBs, femto base stations, network controllers, computers, Central Units (CUs), ng- eNBs, other radio access or backhaul network elements, or the like may be (or include) hardware, firmware, hardware executing software or any combination thereof.
  • Such hardware may include processing or control circuitry such as, but not limited to, one or more processors, one or more CPUs, one or more controllers, one or more ALUs, one or more DSPs, one or more microcomputers, one or more FPGAs, one or more SoCs, one or more PLUs, one or more microprocessors, one or more ASICs, or any other device or devices capable of responding to and executing instructions in a defined manner.
  • processing or control circuitry such as, but not limited to, one or more processors, one or more CPUs, one or more controllers, one or more ALUs, one or more DSPs, one or more microcomputers, one or more FPGAs, one or more SoCs, one or more PLUs, one or more microprocessors, one or more ASICs, or any other device or devices capable of responding to and executing instructions in a defined manner.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Procédé de fonctionnement d'un élément de cœur de réseau (CN) d'un CN d'un réseau de communication comprenant la réception, au niveau de l'élément de CN, d'un message de synchronisation provenant d'un premier UE du réseau de communication, le message de synchronisation comprenant un horodatage d'une horloge de grand-maître (GM) a(g)PTP ; la réalisation sélective, par l'élément de CN, d'une opération de compensation de retard de propagation sur le message de synchronisation, sur la base d'un retard de propagation du premier UE et d'un retard de propagation d'un second UE ; et la transmission du message de synchronisation au second UE.
PCT/EP2020/072266 2020-08-07 2020-08-07 Synchronisation temporelle basée sur un réseau dans un système 5g avec horloge gm sur le côté ue WO2022028715A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2020/072266 WO2022028715A1 (fr) 2020-08-07 2020-08-07 Synchronisation temporelle basée sur un réseau dans un système 5g avec horloge gm sur le côté ue

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2020/072266 WO2022028715A1 (fr) 2020-08-07 2020-08-07 Synchronisation temporelle basée sur un réseau dans un système 5g avec horloge gm sur le côté ue

Publications (1)

Publication Number Publication Date
WO2022028715A1 true WO2022028715A1 (fr) 2022-02-10

Family

ID=71996018

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2020/072266 WO2022028715A1 (fr) 2020-08-07 2020-08-07 Synchronisation temporelle basée sur un réseau dans un système 5g avec horloge gm sur le côté ue

Country Status (1)

Country Link
WO (1) WO2022028715A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200112867A1 (en) * 2018-10-05 2020-04-09 Qualcomm Incorporated System and methods for rapid round-trip-time measurement distribution
WO2020151806A1 (fr) * 2019-01-22 2020-07-30 Nokia Technologies Oy Mécanismes de synchronisation temporelle pour terminaux sans fil
CN111490841A (zh) * 2020-03-23 2020-08-04 腾讯科技（深圳）有限公司 用于实现时间同步的方法及相关设备
WO2020159426A1 (fr) * 2019-01-31 2020-08-06 Telefonaktiebolaget Lm Ericsson (Publ) Dispositif de transmission, dispositif de réception et procédés mis en oeuvre dans ceux-ci pour gérer une communication

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200112867A1 (en) * 2018-10-05 2020-04-09 Qualcomm Incorporated System and methods for rapid round-trip-time measurement distribution
WO2020151806A1 (fr) * 2019-01-22 2020-07-30 Nokia Technologies Oy Mécanismes de synchronisation temporelle pour terminaux sans fil
WO2020159426A1 (fr) * 2019-01-31 2020-08-06 Telefonaktiebolaget Lm Ericsson (Publ) Dispositif de transmission, dispositif de réception et procédés mis en oeuvre dans ceux-ci pour gérer une communication
CN111490841A (zh) * 2020-03-23 2020-08-04 腾讯科技（深圳）有限公司 用于实现时间同步的方法及相关设备

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "Enhancements for support of time synchronization", vol. RAN WG2, no. Electronic meeting; 20200817 - 20200828, 6 August 2020 (2020-08-06), XP051910844, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG2_RL2/TSGR2_111-e/Docs/R2-2006701.zip R2-2006701 Enhancements for support of time synchronization.docx> [retrieved on 20200806] *
NOKIA ET AL: "Discussion on enhancements for support of propagation delay compensation for accurate time synchronization", vol. RAN WG2, no. Online; 20200817 - 20200828, 6 August 2020 (2020-08-06), XP051910883, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG2_RL2/TSGR2_111-e/Docs/R2-2006922.zip R2-2006922 support of PD compensation for accurate time synchronization.docx> [retrieved on 20200806] *

Similar Documents

Publication Publication Date Title
US11405122B2 (en) 5G system support for conveying TSN time synchronization
CN110324889B (zh) 时钟同步方法、通信装置及通信设备
KR101749202B1 (ko) 타임스탬프를 생성하는 방법, 장치, 그리고 시스템
CN110278065B (zh) 一种补偿时延的方法和设备
WO2009155828A1 (fr) Procédé et système de traitement pour informations de champ de correction
WO2020063535A1 (fr) Procédé et appareil de détermination de temps de référence
WO2020151806A1 (fr) Mécanismes de synchronisation temporelle pour terminaux sans fil
CN110100408B (zh) 交互时间同步报文的方法以及网络装置
WO2018210281A1 (fr) Procédé, dispositif et système de calcul d&#39;écart d&#39;horloge et de réglage d&#39;horloge
WO2019100963A1 (fr) Procédé et dispositif de traitement de communications
WO2018224012A1 (fr) Procédé de transmission d&#39;informations de cellules voisines, procédé de traitement d&#39;informations de cellules voisines, dispositif côté réseau et terminal
US20220360350A1 (en) Method and apparatus for acquiring timestamp of data stream, storage medium, and electronic apparatus
US20220006547A1 (en) Systems and methods for testing time distribution
CN113747512A (zh) 一种通信方法、装置及计算机可读存储介质
WO2020200947A1 (fr) Synchronisation temporelle comprenant la préservation d&#39;une estampille temporelle d&#39;origine
CN113574813B (zh) 用于确定时间信息的无线网络系统的网络实体和方法
Thi et al. IEEE 802.1 TSN time synchronization over Wi-Fi and 5G mobile networks
WO2022027666A1 (fr) Procédé et appareil de synchronisation temporelle
WO2022028716A1 (fr) Synchronisation temporelle basée sur un équipement utilisateur dans 5gs avec horloge gm sur le côté équipement utilisateur
CN103401813B (zh) 一种非对称延迟补偿方法及交换机
WO2022028715A1 (fr) Synchronisation temporelle basée sur un réseau dans un système 5g avec horloge gm sur le côté ue
WO2021097769A1 (fr) Procédé et appareil de synchronisation d&#39;horloge
WO2022063395A1 (fr) Amélioration de la précision de synchronisation avec un temps 5gs commun pour dispositifs de liaison latérale
WO2020171802A1 (fr) Synchronisation pour des communications sensibles au temps (tsc) 5gs à l&#39;aide d&#39;un apprentissage automatique
Schüngel et al. Single message distribution of timing information for time synchronization in converged wired and wireless networks

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20753748

Country of ref document: EP

Kind code of ref document: A1