WO2023151794A1 - Service périphérique de synchronisation à partir d'un ue principal sur pc5 - Google Patents

Service périphérique de synchronisation à partir d'un ue principal sur pc5 Download PDF

Info

Publication number
WO2023151794A1
WO2023151794A1 PCT/EP2022/053235 EP2022053235W WO2023151794A1 WO 2023151794 A1 WO2023151794 A1 WO 2023151794A1 EP 2022053235 W EP2022053235 W EP 2022053235W WO 2023151794 A1 WO2023151794 A1 WO 2023151794A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
timing service
time synchronization
timing
service
Prior art date
Application number
PCT/EP2022/053235
Other languages
English (en)
Inventor
Swaminathan ARUNACHALAM
Devaki Chandramouli
Navin Hathiramani
Pilar ANDRÉS MALDONADO
Thomas Haaning Jacobsen
Ling Yu
Original Assignee
Nokia Technologies 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 Technologies Oy filed Critical Nokia Technologies Oy
Priority to PCT/EP2022/053235 priority Critical patent/WO2023151794A1/fr
Publication of WO2023151794A1 publication Critical patent/WO2023151794A1/fr

Links

Classifications

    • 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

Definitions

  • the present disclosure relates to time synchronization.
  • it relates to time synchronization for UEs using proximity services.
  • PC5 Direct communication between devices (e.g. V2V.V2I)
  • devices e.g. V2V.V2I
  • D2D/ProSE mobile users can use operator authorized spectrum for direct communication using PC5 interface, without the support of infrastructure (RAN).
  • RAN infrastructure
  • a User/UE (Relay UE called “Lead UE”) can provide edge services to other UEs (Remote UEs) who are in its proximity using D2D/ProSE communication. This is shown in Fig. 1.
  • GNSS Global Navigation Satellite System
  • gNB/eNB based synchronization also named RAN based synchronization
  • a UE If a UE becomes a synchronization source (called “SyncRef UE”), it transmits its Synchronization Signal Block (SSB) on PSBCH.
  • SSB Synchronization Signal Block
  • the SLSS ID and l_IC help distinguish whether a SyncRef UE is directly or indirectly synchronized to GNSS or a gNB/eNB.
  • • l_IC also indicates whether the SyncRef UE is either one hop or several hops away from a gNB/eNB or GNSS, where each hop corresponds to another SyncRef UE.
  • the 5G System supports Time Synchronization and Time Sensitive communications for any application.
  • the 5G System architecture enables any Application Function (AF) - in the same or different trust domain - to provide its requirements for QoS, traffic characteristics for QoS scheduling optimization, time synchronization activation and deactivation.
  • AF Application Function
  • the AF If the AF is in a different trust domain from the 5G System, then it provides input via exposure framework, NEF API, to the Time Sensitive Communication Time Synchronization Function (TSCTSF). If the AF is in the same trust domain as the 5G System, then it provides input directly via TSCTSF to PCF.
  • NEF API Exposure framework
  • TSCTSF Time Sensitive Communication Time Synchronization Function
  • the 3GPP network may be integrated in a TSN network to connect one or more end station devices of the TSN network to the remainder of the TSN network, considered as a DN from the 3GPP network’s point of view.
  • the 3GPP network may act like a bridge for the TSN network.
  • the 3GPP network provides an interface NW-TT on the network side (typically at the UPF) to the DN, and an interface DS-TT to the end station device of the TSN network.
  • DS-TT is typically implemented in the UE.
  • ProSe application user ID Layer 2 ID
  • Source User Info Source UE's ProSe Application Layer ID, ProSe Application Layer Group ID
  • Target User Info Target UE's ProSe Application Layer ID
  • Slicing information e.g. Allowed NSSAI
  • DNN Data Network Name
  • APN the UE-to-Network Relay is authorised to access
  • the HPLMN or VPLMN for the UE-to-Network Relay • The HPLMN or VPLMN for the UE-to-Network Relay; Mobility restrictions related information such as CAG cell and TA; Relay UE serving cell information like Cell ID
  • PTP provides a hierarchical master-slave architecture for clock distribution.
  • a time distribution system comprises one or more communication media (network segments), and one or more clocks.
  • An ordinary clock is a device with a single network connection and is either the source (master or leader) of a synchronization reference or destination (slave or follower) for a synchronization reference.
  • a boundary clock has multiple network connections and can accurately synchronize one network segment to another.
  • a synchronization master is selected for each of the network segments in the system.
  • the root timing reference is called the grandmaster.
  • the grandmaster transmits synchronization information to the clocks residing on its network segment.
  • the boundary clocks with a presence on that segment then relay accurate time to the other segments to which they are also connected.
  • PTP is a protocol for time delivery
  • gPTP is a profile of the PTP protocol.
  • a PTP profile is a set of required options, prohibited options, and the ranges and defaults of configurable attributes.
  • gPTP defines a subset of optional/mandatory features of PTP.
  • 5GS internal clock synchronization and (generic) Precision Time Protocol ((g)PTP) time synchronization. These processes can be considered independent from each other, and the gNB only needs to be synchronized to the 5G grandmaster (GM) clock.
  • GM grandmaster
  • the 5G clock is delivered to the UE via referenceTimelnfo IE (over SIB9/RRC) that, together with the estimation of the UE frame boundary (SFN) reference, enables the UE to be absolute time synchronized to the 5G clock.
  • referenceTimelnfo IE over SIB9/RRC
  • (g)PTP messages are transferred via user plane.
  • the TSN translators at the edge of the 5GS support (g)PTP operation to distribute the PTP time domain through NW-TT/DS-TT.
  • the 5G internal system clock shall be made available to DS-TT by the UE and to the UPF/NW-TT via the underlying PTP compatible transport network.
  • PMIC Port Management Information Container
  • UMIC User Node Management Information Container
  • UE, gNB, User Plane Function (UPF), Network-side TT (NW-TT), and Device-side TT (DS-TT) are synchronized with the 5G GM (i.e. the 5G internal system clock) which shall serve to keep these elements synchronized.
  • the source for 5G timing is often GPS (or another GNSS) in the current networks and specifications.
  • GM clock serves as the Grandmaster and it provides time to other clocks on the network. Therefore, GM clock shall provide the best source of time when several sources of time are available.
  • PTP has the Best Master Clock Algorithm (BMCA).
  • the BMCA compares a set of PTP properties (e.g. clock accuracy, GM priority, etc) received in the PTP announce messages provided by the time sources and determines the GM for a PTP domain. As a result, the PTP domain constructs a time-synchronization spanning tree with the GM as the root.
  • the 5GS supports two methods for determining the PTP GM and the time synchronization spanning tree: a) using the BMCA procedure, or b) based on local configuration.
  • the BMCA procedure compares data sets comprising the information of the sources from different PTP instances. For the comparison, it uses the priorities defined, clock identities, clock class, GM accuracy and other parameters (see Table 29 of IEEE Std 1588-2019). As a result of the BMCA, the port states are derived (e.g. the port should be passive, slave or master).
  • the PTP Port states (Table 27 of IEEE Std 1588-2019) may be: initializing, faulty, disabled, listening, pre-master, master, passive, uncalibrated, slave.
  • the NW-TT processes the received Announce messages (from NW- TT port(s) and over user plane from the DS-TT(s)) for BMCA procedure, determines port states within the 5GS, determines the PTP GM, and maintains the Master-Slave hierarchy.
  • the AF can retrieve the 5GS time synchronization capabilities prior to sending a time synchronization service request.
  • Table 1 (extracted from 3GPP TS 23.502, Table 5.2.6.25.6-1) describes the time synchronization capability the 5GS can expose to the AF.
  • 3GPP TS 22.104 has further specific service requirements for time synchronization service and direct device connection or indirect network connection, like:
  • the 5G system shall be able to support clock synchronization (working clock domain) between the UEs within the group of UEs using direct device connection ProSe communication.
  • the 5G system shall be able to support Precision Time Protocol-based (IEEE 802.1AS or another applicable IEEE Std 1588 profile) or 5G sync domain-based clock synchronization among the group of UEs using direct device connection. • The 5G system shall be able to support the sync master of the working clock domain being connected to one of the UEs or being hosted at one of the UEs in the group of UEs using direct device connection.
  • the 5G system shall be able to support a 5GS synchronicity budget for clock synchronization according to TS 22.104 Table 7.2.3.2-1.
  • the sync master and sync device are located at or connected to two UEs which are connected via direct device connection.
  • the 5G system shall be able to support clock synchronization (working clock domain) for UEs using indirect network connection.
  • the 5G system shall be able to support Precision Time Protocol-based (IEEE 802.1AS or another applicable IEEE Std 1588 profile) or 5G sync domain-based clock synchronization for UEs using indirect network connection.
  • IEEE 802.1AS or another applicable IEEE Std 1588 profile
  • 5G sync domain-based clock synchronization for UEs using indirect network connection.
  • the 5G system shall be able to support the sync master of the working clock domain being connected to one of the UEs or being hosted at one of the UEs using indirect network connection.
  • the 5G system shall be able to support a 5GS synchronicity budget for clock synchronization according to TS 22.104 Table 8.2.3.2-1.
  • an apparatus comprising: one or more processors, and memory storing instructions that, when executed by the one or more processors, cause the apparatus to perform: offering a timing service of a first terminal to a second terminal via a direct interface between the first terminal and the second terminal; monitoring if an acceptance of the offer is received from the second terminal; providing the timing service to the second terminal via the direct interface if the acceptance is received.
  • the timing service may include that the first terminal may act as a grandmaster clock.
  • the offering the timing service may comprise additionally indicating at least one of the following capabilities:
  • the instructions when executed by the one or more processors, may further cause the apparatus to perform: providing the timing service via a user plane message or via control plane signalling via the direct interface.
  • the instructions when executed by the one or more processors, may further cause the apparatus to perform: receiving a first time synchronization from a network via a control plane; converting the received first time synchronization into a second time synchronization; providing, as the timing service, the second time synchronization to the second terminal on the user plane.
  • the instructions when executed by the one or more processors, may further cause the apparatus to perform: the converting such that the second time synchronization is corrected for a time difference between the first time synchronization and a timing of a PTP instance to which the second terminal belongs.
  • the timing service may be offered during a discovery procedure.
  • an apparatus comprising: one or more processors, and memory storing instructions that, when executed by the one or more processors, cause the apparatus to perform: monitoring whether a second terminal receives an offer of a timing service of a first terminal via a direct interface between the first terminal and the second terminal; providing an acceptance of the offer to the first terminal if the offer is received; receiving the timing service from the first terminal.
  • the offer of the timing service may include that the first terminal may act as a grandmaster clock, and the instructions, when executed by the one or more processors, may further cause the apparatus to perform selecting the first terminal as the grandmaster clock for the second terminal if the offer of the timing service is received.
  • the offer of the timing service may comprise additionally indicating at least one of the following capabilities:
  • the instructions when executed by the one or more processors, may further cause the apparatus to perform: receiving, as the timing service, a first time synchronization from the first terminal on the control plane of the direct interface; converting the received first time synchronization into a second time synchronization; providing the second time synchronization to an end station.
  • a method comprising: offering a timing service of a first terminal to a second terminal via a direct interface between the first terminal and the second terminal; monitoring if an acceptance of the offer is received from the second terminal; providing the timing service to the second terminal via the direct interface if the acceptance is received.
  • the timing service may include that the first terminal may act as a grandmaster clock.
  • the offering the timing service may comprise additionally indicating at least one of the following capabilities:
  • the method may further comprise: providing the timing service via a user plane message or via control plane signalling via the direct interface.
  • the method may further comprise: receiving a first time synchronization from a network via a control plane; converting the received first time synchronization into a second time synchronization; providing, as the timing service, the second time synchronization to the second terminal on the user plane.
  • the method may further comprise: the converting such that the second time synchronization is corrected for a time difference between the first time synchronization and a timing of a PTP instance to which the second terminal belongs.
  • the timing service may be offered during a discovery procedure.
  • a method comprising: monitoring whether a second terminal receives an offer of a timing service of a first terminal via a direct interface between the first terminal and the second terminal; providing an acceptance of the offer to the first terminal if the offer is received; receiving the timing service from the first terminal.
  • the offer of the timing service may include that the first terminal may act as a grandmaster clock, and the method may further comprise selecting the first terminal as the grandmaster clock for the second terminal if the offer of the timing service is received.
  • the offer of the timing service may comprise additionally indicating at least one of the following capabilities:
  • the method may further comprise: checking whether the second terminal receives more than one offers of the timing service from different first terminals via respective direct interfaces; selecting one of the first terminals as the master clock based on the indicated at least one of the capabilities.
  • the method may further comprise: receiving the timing service via a user plane message or via control plane signaling on the direct interface.
  • the method may further comprise: receiving, as the timing service, a first time synchronization from the first terminal on the control plane of the direct interface; converting the received first time synchronization into a second time synchronization; providing the second time synchronization to an end station.
  • Each of the methods of the third and fourth aspects may be a method of a timing edge service.
  • a computer program product comprising a set of instructions which, when executed on an apparatus, is configured to cause the apparatus to carry out the method according to any of the third and fourth aspects.
  • the computer program product may be embodied as a computer-readable medium or directly loadable into a computer. According to some embodiments of the invention, at least one of the following advantages may be achieved:
  • Fig. 1 shows a basic ProSe configuration
  • Fig. 2 depicts scenario 1 according to some example embodiments of the invention
  • Fig. 3 depicts scenario 2a according to some example embodiments of the invention.
  • Fig. 4 depicts scenario 2b (option i) according to some example embodiments of the invention.
  • Fig. 5 depicts scenario 2b (option ii) according to some example embodiments of the invention.
  • Fig. 6 depicts scenario 2c according to some example embodiments of the invention.
  • Fig. 7 shows a message flow according to some example embodiments of the invention.
  • Fig. 8 shows a flow chart according to some example embodiments of the invention.
  • Fig. 9 shows an apparatus according to an example embodiment of the invention.
  • Fig. 10 shows a method according to an example embodiment of the invention
  • Fig. 11 shows an apparatus according to an example embodiment of the invention
  • Fig. 12 shows a method according to an example embodiment of the invention.
  • Fig. 13 shows an apparatus according to an example embodiment of the invention.
  • the apparatus is configured to perform the corresponding method, although in some cases only the apparatus or only the method are described.
  • RAN based synchronization is an alternative to directly relying on the GPS receivers for achieving the precise time synchronization.
  • GPS signals could be obstructed or GPS could fail due to several reasons - natural disasters, spoofing etc.
  • RAN based synchronization i.e. providing time service through NR
  • the time service may be interrupted when there are wireless coverage issues.
  • time synchronization in WAN and HoT like NR robots in a factory setup
  • HoT like NR robots in a factory setup
  • a UE may include its timing service capability information (especially when it can act as GM) as part of the Discovery procedure over PC5.
  • the UE may indicate its timing service capability information in a control message or a user plane message over the established PC5 interface.
  • a (potential) Lead UE may offer its capability to act as a grand master clock as a timing service to one or more other Remote UEs over PC5 interface.
  • the relay UE that can be a potential lead UE describes to the remote UEs what capabilities it has for time synchronization.
  • the relay UE may include additional information assisting the remote UE in determining the GM UE (e.g. holdover capabilities).
  • remote UEs can receive (g)PTP configuration via PC5.
  • PC5 Physical Network element
  • the relay UE is just transparently forwarding user plane traffic to/from the remote UE.
  • relay UE may act as a proxy to forward PMIC from/to remote UEs via PC5.
  • Relay UE may trigger NAS signaling (on top of the PDU Session established for the remote UE) to forward the PMIC of the remote UE to the 5GC (following Rel-17 PMIC transmission method).
  • the 5GC i.e. TSCTSF
  • TSCTSF can configure remote UE’s (g)PTP operation and keep track of the time synchronization spanning tree including out of coverage UEs.
  • Relay UE may act as a proxy to forward the 5G reference timing information received from the network via SIB9/RRC signaling through PC5.
  • the remote UEs may determine the relay UE that will act as lead UE (what UE should be the GM) during discovery procedure over PC5 or by some dedicated (user plane or control plane) message.
  • the selection of the GM at the remote UE shall preferably be compatible with the time synchronization spanning tree and 5GS PTP instance operation the 5GS may determine for the PTP domain, if available (that is, if (g)PTP time synchronization is configured for UEs via PC5 using PMIC and controlled by the TSCTSF).
  • the forwarded (g)PTP messages and PMIC from the NW-TT towards the remote UE (via the relay UE) preferably dictate (g)PTP operation.
  • IEEE Std 802.1AS i.e. gPTP
  • IEEE Std 802.1AS i.e. gPTP
  • the remote UE may use this information to select, in case of plural potential lead UEs, one of them as the actual lead UE providing GM clock.
  • Lead UE may offer a grand master clock as timing service to Remote UE over PC5. This works even in out of coverage scenario, i.e. where both the lead UE and the remote UE are out of coverage of the network. Note that in the out of coverage scenario, any of the relay UE and the remote UE may become a lead UE. If the remote UE (i.e., the UE not setting up the PC5 link) is the lead UE, it offers a grand master clock as timing service to Relay UE over PC5. The relay UE acting as lead UE can offer its timing service to the other UE in one of the following ways:
  • Lead UE can provide the above mentioned information towards the remote UE either over control plane or user plane. Therefore, different scenarios can be considered for sidelink and time synchronization.
  • different scenarios can be considered for sidelink and time synchronization.
  • UE1 receives from network C-plane synchronization, i.e., based on referenceTimelnfo received from the gNB via SIB9/RRC at the relay UE (UE1).
  • network C-plane synchronization i.e., based on referenceTimelnfo received from the gNB via SIB9/RRC at the relay UE (UE1).
  • Relay UE may perform a conversion of absolute time reference in terms of SIB9 to PC5.
  • Relay UE may act as a proxy to forward the 5G reference timing information received from the network via SIB9/RRC signaling through PC5.
  • Remote UE based on the time synchronization service datasets received during the PC5 discovery phase, may select the best synchronization source (i.e., the lead UE) if plural UEs offer their synchronization services.
  • UE2 is a (g)PTP end station outside the 5GS domain (out of the PTP instance we have in 5GS; e.g. its GM clock may be in another 5GS). That is, UE2 cannot reach its GM clock via 5GS. Accordingly, it synchronizes with the UE1/DS- TT acting as GM (e.g. UE1) if UE1 offers such a service. Since the absolute time of the PtP hierarchy to which UE2 belongs is not known, UE2/DS-TT may receive (g)PTP messages from the GM without any additional timestamping for corrections. Since UE1/DS-TT and UE2/DS-TT are working within PTP domains of separate GM clocks, the 5GS controls operation of UETs DS-TT but it does not control UE2’s DS-TT.
  • GM e.g. UE1
  • UE2/DS-TT may receive (g)PTP messages from the GM without any additional timestamping for corrections. Since UE
  • UE2/DS-TT should preferably perform some corrections based on 5G clock timestamping if it is synchronized with internal 5G clock via the SL link. For example, such synchronization may be achieved using scenario 1 based on C-plane or some other way the UE2 to get absolutely synchronized to 5G clock.
  • UE1/DS-TT may provide 5G clock and SFN reference info when it forwards the (g)PtP message to the UE2/DS-TT.
  • the UE2/DS-TT will be able to compute the absolute timing information for 5G clock in order to perform corrections and determine residence time based on 5G clock time stamping.
  • the residence time is the time the PTP packet spent within the 5GS (a PTP instance).
  • the TT that is the entry point of the PTP instance may perform an ingress timestamping, later, at the egress, TT does another timestamp (egress timestamp), and the residence time within the PTP instance is derived. ii. (Fig.
  • UE1/DS-TT may perform the corrections based on 5G clock (as UE1 has access to 5G clock via llu interface).
  • UE1 may just forward the corrected (g)PTP message to the UE2/DS-TT.
  • UE2 is still inside the 5G PTP instance. Therefore, the 5GS controls UE2’s DS-TT operation (e.g. via PMIC)
  • both UE1 and UE2 are in 5GS coverage. They are (g)PTP end stations (e.g. DS-TTs). As UE2 has coverage, it can sync with the gNB to the 5G clock.
  • the DS-TTs can exchange (g)PTP messages to sync to the vertical clock (i.e. the clock used by the end stations) indirectly via llu interfaces (UL sync process enabled in R17) or directly via PC5 (extension of UL sync from R17 for SL).
  • This scenario may not have a significant impact in 5G specification as PC5 is only used for (g)PTP traffic but still the 5G PTP instance may be configured based on R17 methods.
  • the 5G PTP instance of one of the UEs may be configured via PC5 interface.
  • selection of a lead UE shall be based on the service capabilities, e.g. whether a certain UE acts as GM or slave.
  • Example service capabilities in case of time service are Time Synchronization Accuracy, Holdover capabilities, priority, BMCA, time synchronization source based on SLSS ID employed, etc.
  • Fig. 7 shows an example embodiment of the invention to explain the procedure.
  • UE1 and UE3 offer its capability to act as a GM to UE2.
  • the actions are substantially as follows:
  • Actions 1 and 2 for both UE1 and UE3 In action 1, USER#1(UE1) gets the ProSe/PC5 related identifier and/or application code, to be used in action 2. In action 2, UE1 is authenticated and ProSe/PC5 related parameters are provided to the UE as a lead UE. In this case, the existing ProSe UE-to-NW relay procedure may be reused. USER#3 (UE3) performs actions 1 and 2 correspondingly. UE1 and UE3 are potential lead UEs.
  • Actions 1 and 3 for UE2 USER#2(UE2) performs action 1 in the same way as UE1 and UE3. Instead of action 2, UE2 performs action 3 where ProSe/PC5 related parameters are provided to the UE as a remote UE. 3) Action 4 for both UE1 and UE3: USER#1(UE1) and USER#3(UE3) send the announcing/discovery messages to allow the other UEs in proximity (e.g. UE2) to discover them as providers of time synchronization service following sidelink discovery model A. That is, each of UE1 and UE3 initiates the discovery of other users who are interested in using the application function and are in its proximity by using direct discovery.
  • USER#1 wants to provide time service to other users by using one to one communication over PC5 reference point.
  • UE1 shall provide the Time Synchronization info and Service capabilities as a part of the discovery announcement.
  • the Lead UE could employ the sidelink synchronization signals to inform UEs of the resources and/or type of synchronization it can provide.
  • USER#2(UE2) selects the lead UE based on the configured time synchronization criteria and other factors like signal strength.
  • a Lead/Relay UE selection algorithm is employed by other users (Remote UE/UE2) to decide which lead/relay UE services to exploit. This algorithm is described further below with respect to Fig. 8.
  • UE2 selects UE1 as lead UE. The selection of the lead UE may be continuously repeated, e.g. once in every four discovery periods.
  • Action 6 USER#1(UE1) gets a response from some users (e.g. UE2/Remote UE) who want to use its time service (i.e. selected UE1 as lead UE).
  • some users e.g. UE2/Remote UE
  • time service i.e. selected UE1 as lead UE.
  • USER#1(UE1) i.e. the lead/relay UE selected by
  • the UE2 creates a service user list including the users that sent a response to the discovery message, and checks with an Application Server associated with the application function regarding which of the stated users are authorized to participate in the one to one communication. After checking, the Application Server provides a Service Member List and various information for this service communication including Application Layer Group ID and Destination IP address to the lead UE(UE1). The lead UE(UE1) provides the Application Layer Group ID and Destination Layer-2 ID to other member UEs in the Service Member List (e.g. to UE2).
  • Remote UE selects the Lead UE (Service provider) based on many factors like RSRP of PC5, relay/lead UE capability (e.g.: time synchronization capability), Uu channel condition, etc. According to some example embodiments, this procedure may be enhanced to consider new factors such as timing service availability by the Lead UE.
  • discovery Model A most of the information needed for lead/relay UE selection decision are received in the announcement message of the lead UE (announcing UE). Model A is one of the models for direct discovery.
  • the UE e.g. lead UE in our case
  • the announcing/discovery message can be something like Radiol am here".
  • Another discovery model defines that a UE (e.g. remote UE in the present case) sends a discovery solicitation message and the other UEs (e.g. lead UE) in proximity send the discovery response message to allow the remote UE to discover it.
  • a UE e.g. remote UE in the present case
  • the other UEs e.g. lead UE
  • Fig. 8 shows a method of lead UE selection according to some example embodiments of the invention.
  • a first decision for UEs, it is decided based on the conventional criteria (e.g. radio criteria) if they are candidates as lead UEs. If only one of the UEs is left as a candidate, this UE is selected. If more than 1 candidate remains, it is checked which of the UEs has the TimeSync capability. If only one of these candidates has the TimeSync capability it is selected. If there are more than one remaining candidates, the service performances of the timesync capability (e.g. holdover time, accuracy) are used to order the remaining candidates. The UE with the best performance is selected.
  • the first selection based on conventional criteria may be omitted. I.e., the selection may be performed based on the availability of the timesync service and potentially its performance only.
  • Fig. 9 shows an apparatus according to an example embodiment of the invention.
  • the apparatus may be a terminal (in particular: a UE), such as a UE offering timesync service, or an element thereof.
  • Fig. 10 shows a method according to an example embodiment of the invention.
  • the apparatus according to Fig. 9 may perform the method of Fig. 10 but is not limited to this method.
  • the method of Fig. 10 may be performed by the apparatus of Fig. 9 but is not limited to being performed by this apparatus.
  • the apparatus comprises means for offering 110, means for monitoring 120, and means for providing 130.
  • the means for offering 110, means for monitoring 120, and means for providing 130 may be an offering means, monitoring means, and providing means, respectively.
  • the means for offering 110, means for monitoring 120, and means for providing 130 may be an offerer, monitor, and provider, respectively.
  • the means for offering 110, means for monitoring 120, and means for providing 130 may be a offering processor, monitoring processor, and providing processor, respectively.
  • the means for offering 110 offers a timing service of a first terminal to a second terminal via a direct interface (e.g. PC5) between the first terminal and the second terminal (S110).
  • the means for monitoring 120 monitors if an acceptance of the offer is received from the second terminal (S120). For example, the means for monitoring 120 may monitor if the acceptance is received via the direct interface.
  • the means for providing 130 provides the timing service to the second terminal via the direct interface (S130).
  • the acceptance of S120 may be received on the SL level and/or on the PTP level:
  • the monitoring the acceptance may be detected by two ways: i) using model B SL discovery, the offering (S110) is performed by sending SL discovery solicitation message, the monitoring of acceptance (S120) may be performed by detecting DL discovery response message. After receiving SL discovery response message, the providing (S130) corresponds to setting up SL one-to-one communication link to the peer UE for providing the timing service. ii) using model A SL discovery, the offering (S110) is performed by sending model
  • the acceptance may be monitored (S120) by receiving SL one-to- one communication link establishment request.
  • the providing (S130) may correspond to accepting the connection establishment and providing the timing service via the established communication link.
  • the acceptance may be detected (S120) at the lead UE (master) if it receives PTP requests from the remote UE (slave). That is, in order to use PTP, the slave sends PTP Delay_Request messages and receives the corresponding PTP Delay_Responses from the master.
  • Fig. 11 shows an apparatus according to an example embodiment of the invention.
  • the apparatus may be a terminal (in particular: a UE), such as a UE receiving a timing service, or an element thereof.
  • Fig. 12 shows a method according to an example embodiment of the invention.
  • the apparatus according to Fig. 11 may perform the method of Fig. 12 but is not limited to this method.
  • the method of Fig. 12 may be performed by the apparatus of Fig. 11 but is not limited to being performed by this apparatus.
  • the apparatus comprises means for monitoring 310, means for providing 320, and means for receiving 330.
  • the means for monitoring 310, means for providing 320, and means for receiving 330 may be a monitoring means, providing means, and receiving means, respectively.
  • the means for monitoring 310, means for providing 320, and means for receiving 330 may be a monitor, identifier, and receiver, respectively.
  • the means for monitoring 310, means for providing 320, and means for receiving 330 may be a monitoring processor, providing processor, and receiving processor, respectively.
  • the means for monitoring 310 monitors whether a second terminal receives an offer of a timing service of a first terminal via a direct interface (e.g. PC5) between the first terminal and the second terminal (S310).
  • a direct interface e.g. PC5
  • the means for providing 320 provides an acceptance of the offer to the first terminal (S320). For example, it may provide the acceptance via the direct interface. Then, the means for receiving 330 receives the timing service from the first terminal (S330).
  • S310 to S330 correspond to S110 to S130, respectively, such that the explanations of example implementations of S110 to S130 apply to S310 to S330 correspondingly.
  • Fig. 13 shows an apparatus according to an embodiment of the invention.
  • the apparatus comprises at least one processor 810, at least one memory 820 including computer program code, and the at least one processor 810, with the at least one memory 820 and the computer program code, being arranged to cause the apparatus to at least perform at least the method according to at least one of Figs. 10 and 12 and related description.
  • 5G 5th Generation
  • the invention is not limited to 5G. It may be used in other service based networks providing mobility, too, e.g. in previous of forthcoming generations of 3GPP networks such as 4G, 6G, or 7G, etc. It may be used in non-3GPP mobile communication networks providing proximity services, too.
  • One piece of information may be transmitted in one or plural messages from one entity to another entity. Each of these messages may comprise further (different) pieces of information.
  • Names of network elements, network functions, protocols, and methods are based on current standards. In other versions or other technologies, the names of these network elements and/or network functions and/or protocols and/or methods may be different, as long as they provide a corresponding functionality. If not otherwise stated or otherwise made clear from the context, the statement that two entities are different means that they perform different functions. It does not necessarily mean that they are based on different hardware. That is, each of the entities described in the present description may be based on a different hardware, or some or all of the entities may be based on the same hardware. It does not necessarily mean that they are based on different software. That is, each of the entities described in the present description may be based on different software, or some or all of the entities may be based on the same software. Each of the entities described in the present description may be deployed in the cloud.
  • example embodiments of the present invention provide, for example, a terminal (such as a UE) or a component thereof, an apparatus embodying the same, a method for controlling and/or operating the same, and computer program(s) controlling and/or operating the same as well as mediums carrying such computer program(s) and forming computer program product(s).
  • Implementations of any of the above described blocks, apparatuses, systems, techniques or methods include, as non-limiting examples, implementations as hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.
  • Each of the entities described in the present description may be embodied in the cloud.
  • first X and second X include the options that “first X” is the same as “second X” and that “first X” is different from “second X”, unless otherwise specified.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Synchronisation In Digital Transmission Systems (AREA)

Abstract

Procédé consistant : à offrir un service de synchronisation d'un premier terminal à un second terminal par l'intermédiaire d'une interface directe entre le premier terminal et le second terminal; à surveiller si une acceptation de l'offre est reçue en provenance du second terminal; à fournir le service de synchronisation au second terminal par l'intermédiaire de l'interface directe si l'acceptation est reçue.
PCT/EP2022/053235 2022-02-10 2022-02-10 Service périphérique de synchronisation à partir d'un ue principal sur pc5 WO2023151794A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2022/053235 WO2023151794A1 (fr) 2022-02-10 2022-02-10 Service périphérique de synchronisation à partir d'un ue principal sur pc5

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2022/053235 WO2023151794A1 (fr) 2022-02-10 2022-02-10 Service périphérique de synchronisation à partir d'un ue principal sur pc5

Publications (1)

Publication Number Publication Date
WO2023151794A1 true WO2023151794A1 (fr) 2023-08-17

Family

ID=80684031

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2022/053235 WO2023151794A1 (fr) 2022-02-10 2022-02-10 Service périphérique de synchronisation à partir d'un ue principal sur pc5

Country Status (1)

Country Link
WO (1) WO2023151794A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20230269679A1 (en) * 2022-02-24 2023-08-24 Qualcomm Incorporated Thermal efficient method to maintain cv2x timing

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160212721A1 (en) * 2015-01-16 2016-07-21 Sharp Laboratories Of America, Inc. Method and apparatus for selecting a synchronization signal source for sidelink communcations
US20170142703A1 (en) * 2015-02-06 2017-05-18 Samsung Electronics Co., Ltd. Ue discovery method and system in d2d network
WO2021076029A1 (fr) * 2019-10-18 2021-04-22 Telefonaktiebolaget Lm Ericsson (Publ) Noeud de réseau, premier dispositif sans fil, second dispositif sans fil et procédés associés pour permettre une référence de synchronisation
WO2021226394A1 (fr) * 2020-05-07 2021-11-11 Qualcomm Incorporated Facilitation de la fonctionnalité de synchronisation temporelle au niveau d'un équipement utilisateur

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160212721A1 (en) * 2015-01-16 2016-07-21 Sharp Laboratories Of America, Inc. Method and apparatus for selecting a synchronization signal source for sidelink communcations
US20170142703A1 (en) * 2015-02-06 2017-05-18 Samsung Electronics Co., Ltd. Ue discovery method and system in d2d network
WO2021076029A1 (fr) * 2019-10-18 2021-04-22 Telefonaktiebolaget Lm Ericsson (Publ) Noeud de réseau, premier dispositif sans fil, second dispositif sans fil et procédés associés pour permettre une référence de synchronisation
WO2021226394A1 (fr) * 2020-05-07 2021-11-11 Qualcomm Incorporated Facilitation de la fonctionnalité de synchronisation temporelle au niveau d'un équipement utilisateur

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20230269679A1 (en) * 2022-02-24 2023-08-24 Qualcomm Incorporated Thermal efficient method to maintain cv2x timing

Similar Documents

Publication Publication Date Title
JP6203832B2 (ja) デバイスツーデバイス通信およびプロキシミティサービスのためにデバイス間の距離を決定するための方法および装置
US9369224B2 (en) Clock synchronization method and device
US11576133B2 (en) Timing synchronization of 5G V2X sidelink transmissions
WO2020048393A1 (fr) Procédé et dispositif de coordination de ressources de positionnement, nœud de réseau, terminal et station de base
JP2023100973A (ja) ネットワークノード、ネットワークノードのための方法、ユーザ装置、及びネットワークスライス使用の制御のためのユーザ装置のための方法
CN111436113A (zh) 支持时钟同步的方法及通信设备
JP2022153397A (ja) セルのグローバル識別情報の報告
US20080137595A1 (en) Methods and systems for base station installation in distributed call processing networks
WO2023151794A1 (fr) Service périphérique de synchronisation à partir d'un ue principal sur pc5
US11690031B2 (en) Methods and apparatus for distributing time, frequency, and/or phase information
US20230141032A1 (en) Apparatus and methods for transmission of timing information
US10420048B2 (en) Radio network synchronization of a mobile communication network with a local clock functionality providing a local timing reference for each base station entity
WO2023214383A1 (fr) Mobilité de services de synchronisation sur système de communication cellulaire
EP4165915B1 (fr) Technique de transport d'un message de protocole de temps pour une mise en réseau sensible au temps
WO2021199667A1 (fr) Station de base, système de communication, procédé de communication et support pouvant être lu par ordinateur non transitoire
KR101421523B1 (ko) 네트워크 동기화 시스템 및 네트워크 동기화 방법
WO2023174149A1 (fr) Procédé de synchronisation d'états d'horloge et appareil de communication
US11540053B2 (en) Method of synchronizing pieces of audio equipment
EP2707976B1 (fr) Synchronisation temporelle dans un réseau de communication
WO2024066922A9 (fr) Procédé, appareil et système de transmission d'informations
JP7501698B2 (ja) 基地局及び通信方法
CN113676962B (zh) 切换处理方法、通信设备、目标基站、源基站及终端
EP4325949A1 (fr) Procédé de synchronisation de n uds d'un réseau cellulaire
US20230032067A1 (en) Method and apparatus for acquisition of reliable time in a wireless network
CN117479285A (zh) 通信方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22708819

Country of ref document: EP

Kind code of ref document: A1